GBSS9.0 Feature Parameter Description

GBSS9.
GBSS Feature Parameter Description

Issue Date 08 2011-09-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 08 (2011-09-30)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Contents
Contents
1 Library Information......................................................................................................................1
1.1 Library Overview...............................................................................................................................................2 1.2 Library Changes...............................................................................................................................................20 1.3 Glossary............................................................................................................................................................21 1.3.1 Numerics..................................................................................................................................................22 1.3.2 A..............................................................................................................................................................22 1.3.3 B...............................................................................................................................................................27 1.3.4 C...............................................................................................................................................................30 1.3.5 D..............................................................................................................................................................37 1.3.6 E...............................................................................................................................................................40 1.3.7 F...............................................................................................................................................................43 1.3.8 G..............................................................................................................................................................46 1.3.9 H..............................................................................................................................................................49 1.3.10 I..............................................................................................................................................................52 1.3.11 K............................................................................................................................................................55 1.3.12 L.............................................................................................................................................................56 1.3.13 M............................................................................................................................................................58 1.3.14 N............................................................................................................................................................62 1.3.15 O............................................................................................................................................................65 1.3.16 P.............................................................................................................................................................66 1.3.17 Q............................................................................................................................................................72 1.3.18 R.............................................................................................................................................................72 1.3.19 S.............................................................................................................................................................77 1.3.20 T.............................................................................................................................................................84 1.3.21 U............................................................................................................................................................88 1.3.22 V............................................................................................................................................................89 1.3.23 W...........................................................................................................................................................90 1.3.24 X............................................................................................................................................................91
2 GBSS Feature Parameter Description......................................................................................92

2.1 Tutorial Introduction to Basic Features of GBSS9.0........................................................................................98 2.2 Tutorial Introduction to Optional Features Of GBSS9.0................................................................................104 2.3 2-Antenna Receive Diversity..........................................................................................................................116 2.3.1 Introduction...........................................................................................................................................116 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ii
Contents
2.3.1.1 Scope............................................................................................................................................116 2.3.1.2 Intended Audience........................................................................................................................ 116 2.3.1.3 Change History.............................................................................................................................116 2.3.2 Overview...............................................................................................................................................117 2.3.3 Technical Description............................................................................................................................117 2.3.3.1 Technical Principle.......................................................................................................................117 2.3.3.2 Diversity Combining Algorithms.................................................................................................118 1. MRC.....................................................................................................................................................118 2. ICC........................................................................................................................................................118 3. EICC.....................................................................................................................................................118 2.3.4 Parameters.............................................................................................................................................119 2.3.5 Counters.................................................................................................................................................120 2.3.6 Glossary.................................................................................................................................................120 2.3.7 Reference Documents............................................................................................................................120 2.4 2G/3G Interoperability...................................................................................................................................121 2.4.1 Introduction...........................................................................................................................................121 2.4.1.1 Scope............................................................................................................................................121 2.4.1.2 Intended Audience........................................................................................................................ 121 2.4.1.3 Change History.............................................................................................................................121 2.4.2 Overview...............................................................................................................................................123 2.4.3 Technical Description............................................................................................................................124 2.4.3.1 Measurement of Neighboring UMTS Cells..................................................................................124 2.4.3.2 Common Measurement and Information Exchange Based on Iur-g............................................125 1. Introduction to the Iur-g Interface........................................................................................................125 2. Common Measurement.........................................................................................................................126 3. Information Exchange..........................................................................................................................128 2.4.3.3 2G/3G Inter-RAT Cell Reselection..............................................................................................129 1. Inter-RAT Cell Reselection from UMTS to GSM...............................................................................129 2. Inter-RAT Cell Reselection from GSM to UMTS...............................................................................129 3. Fast 3G Reselection at 2G CS Call Release.........................................................................................131 4. NACC and NC2....................................................................................................................................132 2.4.3.4 2G/3G Inter-RAT Handover.........................................................................................................133 1. Inter-RAT Handover from UMTS to GSM.......................................................................................... 133 2. Inter-RAT Handover from GSM to UMTS.......................................................................................... 133 3. 2G/3G Service Distribution and Load Balancing in Access State.......................................................134 4. Inter-RAT Load-based Handover in Connected State..........................................................................136 2.4.4 Engineering Guidelines.........................................................................................................................136 2.4.5 Parameters.............................................................................................................................................137 2.4.6 Counters.................................................................................................................................................149 2.4.7 Glossary.................................................................................................................................................149 2.4.8 Reference Documents............................................................................................................................149 2.5 2G/3G Interoperability (TDD)........................................................................................................................150 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iii
Contents
2.5.1 Introduction...........................................................................................................................................150 2.5.1.1 Scope............................................................................................................................................150 2.5.1.2 Intended Audience........................................................................................................................150 2.5.1.3 Change History.............................................................................................................................150 2.5.2 Overview...............................................................................................................................................151 2.5.3 Technical Description............................................................................................................................152 2.5.3.1 Measurement of Neighboring UMTS Cells..................................................................................152 2.5.3.2 2G/3G Inter-RAT Cell Reselection..............................................................................................153 1. Inter-RAT Cell Reselection from UMTS to GSM...............................................................................153 2. Inter-RAT Cell Reselection from GSM to UMTS...............................................................................153 3. Fast 3G Reselection at 2G CS Call Release.........................................................................................154 4. NACC and NC2....................................................................................................................................156 2.5.3.3 2G/3G Inter-RAT Handover.........................................................................................................156 1. Inter-RAT Handover from UMTS to GSM..........................................................................................157 2. Inter-RAT Handover from GSM to UMTS..........................................................................................157 3. 2G/3G Inter-RAT Load Handover.......................................................................................................158 4. 2G/3G Inter-RAT Service Handover....................................................................................................158 2.5.3.4 GSM/TD-SCDMA Interoperability Optimization........................................................................159 2.5.3.5 PS GSM and TD-SCDMA Interoperability Optimization...........................................................159 2.5.4 Engineering Guidelines.........................................................................................................................160 2.5.5 Parameters.............................................................................................................................................161 2.5.6 Counters.................................................................................................................................................167 2.5.7 Glossary.................................................................................................................................................167 2.5.8 Reference Documents............................................................................................................................167 2.6 Abis Bypass....................................................................................................................................................167 2.6.1 Introduction...........................................................................................................................................168 2.6.1.1 Scope............................................................................................................................................168 2.6.1.2 Intended Audience........................................................................................................................168 2.6.1.3 Change History.............................................................................................................................168 2.6.2 Overview...............................................................................................................................................169 2.6.3 Technical Description............................................................................................................................170 2.6.3.1 Key Technologies.........................................................................................................................170 2.6.4 Parameters.............................................................................................................................................171 2.6.5 Counters.................................................................................................................................................171 2.6.6 Glossary.................................................................................................................................................171 2.6.7 Reference Documents............................................................................................................................171 2.7 Acoustic Echo Cancellation............................................................................................................................171 2.7.1 Introduction...........................................................................................................................................171 2.7.1.1 Scope............................................................................................................................................172 2.7.1.2 Intended Audience........................................................................................................................172 2.7.1.3 Change History.............................................................................................................................172 2.7.2 Overview...............................................................................................................................................173 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. iv
Contents
2.7.3 Technical Description............................................................................................................................173 2.7.4 Parameters.............................................................................................................................................174 2.7.5 Counters.................................................................................................................................................175 2.7.6 Glossary.................................................................................................................................................175 2.7.7 References.............................................................................................................................................175 2.8 AFC................................................................................................................................................................175 2.8.1 Introduction...........................................................................................................................................175 2.8.1.1 Scope............................................................................................................................................175 2.8.1.2 Intended Audience........................................................................................................................176 2.8.1.3 Change History.............................................................................................................................176 2.8.2 Overview...............................................................................................................................................177 2.8.3 Technical Description............................................................................................................................177 2.8.4 Parameters.............................................................................................................................................178 2.8.5 Counters.................................................................................................................................................178 2.8.6 Glossary.................................................................................................................................................178 2.8.7 Reference Documents............................................................................................................................178 2.9 AMR...............................................................................................................................................................178 2.9.1 Introduction...........................................................................................................................................179 2.9.1.1 Scope............................................................................................................................................179 2.9.1.2 Intended Audience........................................................................................................................179 2.9.1.3 Change History.............................................................................................................................179 2.9.2 Overview...............................................................................................................................................180 2.9.3 Technical Description............................................................................................................................181 2.9.3.1 Inband Signaling...........................................................................................................................181 2.9.3.2 Speech Rate Adjustment...............................................................................................................183 2.9.3.3 Rate Adjustment Threshold Adaptation.......................................................................................185 2.9.3.4 AMR Power Control.....................................................................................................................186 2.9.3.5 Handover......................................................................................................................................186 2.9.3.6 Impact on KPI...............................................................................................................................186 2.9.4 Engineering Guidelines.........................................................................................................................187 2.9.5 Parameters.............................................................................................................................................188 2.9.6 Counters.................................................................................................................................................198 2.9.7 Glossary.................................................................................................................................................198 2.9.8 Reference Documents............................................................................................................................198 2.10 Antenna Frequency Hopping........................................................................................................................199 2.10.1 Introduction.........................................................................................................................................199 2.10.1.1 Scope..........................................................................................................................................199 2.10.1.2 Intended Audience......................................................................................................................199 2.10.1.3 Change History...........................................................................................................................199 2.10.2 Overview.............................................................................................................................................200 2.10.3 Technical Description..........................................................................................................................201 2.10.3.1 Antenna Hopping Selection Algorithm......................................................................................201 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. v
Contents
2.10.3.2 Relation Between Antenna Frequency Hopping and Frequency Hopping.................................202 2.10.4 Parameters...........................................................................................................................................202 2.10.5 Counters...............................................................................................................................................203 2.10.6 Glossary...............................................................................................................................................203 2.10.7 Reference Documents..........................................................................................................................203 2.11 AQM.............................................................................................................................................................203 2.11.1 Introduction.........................................................................................................................................203 2.11.1.1 Scope..........................................................................................................................................203 2.11.1.2 Intended Audience......................................................................................................................203 2.11.1.3 Change History...........................................................................................................................204 2.11.2 Overview.............................................................................................................................................204 2.11.3 Technical Description..........................................................................................................................205 2.11.4 Engineering Guidelines.......................................................................................................................207 2.11.5 Parameters...........................................................................................................................................207 2.11.6 Counters...............................................................................................................................................208 2.11.7 Glossary...............................................................................................................................................209 2.11.8 Reference Documents..........................................................................................................................209 2.12 Assignment and Immediate Assignment......................................................................................................209 2.12.1 Introduction.........................................................................................................................................209 2.12.1.1 Scope..........................................................................................................................................209 2.12.1.2 Intended Audience......................................................................................................................209 2.12.1.3 Change History...........................................................................................................................209 2.12.2 Overview of Assignment and Immediate Assignment........................................................................210 2.12.3 Technical Description..........................................................................................................................210 2.12.3.1 Immediate Assignment...............................................................................................................210 1. Immediate Assignment Procedure........................................................................................................210 2. Immediate Assignment Combination...................................................................................................212 2.12.3.2 Assignment.................................................................................................................................212 1. Assignment Procedure..........................................................................................................................212 2. Assignment Classification....................................................................................................................214 2.12.4 Parameters...........................................................................................................................................218 2.12.5 Counters...............................................................................................................................................221 2.12.6 Glossary...............................................................................................................................................221 2.12.7 Reference Documents..........................................................................................................................221 2.13 Ater Compression Transmission..................................................................................................................221 2.13.1 Introduction.........................................................................................................................................221 2.13.1.1 Scope..........................................................................................................................................221 2.13.1.2 Intended Audience......................................................................................................................222 2.13.1.3 Change History...........................................................................................................................222 2.13.2 Overview.............................................................................................................................................222 2.13.3 Technical Description..........................................................................................................................223 2.13.3.1 Network Topologies...................................................................................................................223 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vi
Contents
1. Network Topology in Non-TC Pool Mode...........................................................................................223 2. Network Topology in TC Pool Mode...................................................................................................224 2.13.3.2 Technologies in Ater Compression Transmission......................................................................225 1. Speech Frame Processing.....................................................................................................................225 2. Packet Multiplexing..............................................................................................................................227 3. Reliability.............................................................................................................................................228 2.13.4 Engineering Guidelines.......................................................................................................................228 2.13.5 Parameters...........................................................................................................................................228 2.13.6 Counters...............................................................................................................................................229 2.13.7 Glossary...............................................................................................................................................229 2.13.8 Reference Documents..........................................................................................................................230 2.14 Automatic Level Control..............................................................................................................................230 2.14.1 Introduction.........................................................................................................................................230 2.14.1.1 Scope..........................................................................................................................................230 2.14.1.2 Intended Audience......................................................................................................................230 2.14.1.3 Change History...........................................................................................................................230 2.14.2 Overview.............................................................................................................................................231 2.14.3 Technical Description..........................................................................................................................232 2.14.4 Parameters...........................................................................................................................................232 2.14.5 Counters...............................................................................................................................................234 2.14.6 Glossary...............................................................................................................................................234 2.14.7 References...........................................................................................................................................234 2.15 Automatic Noise Compensation...................................................................................................................234 2.15.1 Introduction.........................................................................................................................................234 2.15.1.1 Scope..........................................................................................................................................234 2.15.1.2 Intended Audience......................................................................................................................234 2.15.1.3 Change History...........................................................................................................................235 2.15.2 Overview.............................................................................................................................................235 2.15.3 Technical Description..........................................................................................................................235 2.15.4 Parameters...........................................................................................................................................236 2.15.5 Counters...............................................................................................................................................237 2.15.6 Glossary...............................................................................................................................................237 2.15.7 Reference Documents..........................................................................................................................237 2.16 Automatic Noise Restraint............................................................................................................................237 2.16.1 Introduction.........................................................................................................................................237 2.16.1.1 Scope..........................................................................................................................................237 2.16.1.2 Intended Audience......................................................................................................................238 2.16.1.3 Change History...........................................................................................................................238 2.16.2 Overview.............................................................................................................................................239 2.16.3 Technical Description..........................................................................................................................239 2.16.4 Parameters...........................................................................................................................................240 2.16.5 Counters...............................................................................................................................................241 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
2.16.6 Glossary...............................................................................................................................................241 2.16.7 References...........................................................................................................................................241 2.17 BCCH Dense Frequency Multiplexing.........................................................................................................241 2.17.1 Introduction.........................................................................................................................................241 2.17.1.1 Scope..........................................................................................................................................241 2.17.1.2 Intended Audience......................................................................................................................241 2.17.1.3 Change History...........................................................................................................................242 2.17.2 Overview.............................................................................................................................................242 2.17.3 Technical Principles............................................................................................................................243 2.17.4 Engineering Guidelines.......................................................................................................................245 2.17.5 Parameters...........................................................................................................................................245 2.17.6 Counters...............................................................................................................................................247 2.17.7 Glossary...............................................................................................................................................247 2.17.8 Reference Documents..........................................................................................................................247 2.18 BSC Node Redundancy................................................................................................................................248 2.18.1 Introduction.........................................................................................................................................248 2.18.1.1 Scope..........................................................................................................................................248 2.18.1.2 Intended Audience......................................................................................................................248 2.18.1.3 Change History...........................................................................................................................248 2.18.2 Overview.............................................................................................................................................249 2.18.3 Technical Description..........................................................................................................................251 2.18.3.1 Network Topologies...................................................................................................................251 1. Network Topologies on the Abis Interface...........................................................................................251 2. Network Topologies on the A and Gb Interfaces.................................................................................254 3. Network Topology on the Inter-BSC Interface....................................................................................256 2.18.3.2 Fault Detection...........................................................................................................................256 2.18.3.3 Migration of Service Objects......................................................................................................257 1. Dual-Homed OPCs...............................................................................................................................257 2. Dual-Homed BTSs...............................................................................................................................257 3. Dual-Homed Cells and PTP BVC Objects...........................................................................................258 4. Re-Homing Policy of Dual-Homed Service Objects............................................................................258 2.18.3.4 Audit of Dual-Homed Service Objects.......................................................................................259 2.18.3.5 Maintenance of Dual-Homed Service Objects...........................................................................259 2.18.4 Engineering Guidelines.......................................................................................................................259 2.18.5 Parameters...........................................................................................................................................260 2.18.6 Counters...............................................................................................................................................263 2.18.7 Glossary...............................................................................................................................................263 2.18.8 Reference Documents..........................................................................................................................263 2.19 BSS Local Switching....................................................................................................................................263 2.19.1 Introduction.........................................................................................................................................263 2.19.1.1 Scope..........................................................................................................................................264 2.19.1.2 Intended Audience......................................................................................................................264 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. viii
Contents
2.19.1.3 Change History...........................................................................................................................264 2.19.2 Overview.............................................................................................................................................265 2.19.3 Technical Description..........................................................................................................................269 2.19.3.1 Principles....................................................................................................................................269 1. Principles of BSC Local Switching......................................................................................................269 2. Principles of BTS Local Switching......................................................................................................270 2.19.3.2 Procedures Related to BSS Local Switching..............................................................................271 1. Triggering of the BSS Local Switching Call........................................................................................271 2. Restoration of the BSS Local Switching Call......................................................................................275 3. Handover of the BSS Local Switching Call.........................................................................................276 2.19.3.3 Impact on CN Services...............................................................................................................276 2.19.4 Engineering Guidelines.......................................................................................................................278 2.19.5 Parameters...........................................................................................................................................278 2.19.6 Counters...............................................................................................................................................289 2.19.7 Glossary...............................................................................................................................................290 2.19.8 Reference Documents..........................................................................................................................290 2.20 BTS Combined Cabinets and Cabinet Groups.............................................................................................290 2.20.1 Introduction.........................................................................................................................................290 2.20.1.1 Scope..........................................................................................................................................290 2.20.1.2 Intended Audience......................................................................................................................290 2.20.1.3 Change History...........................................................................................................................290 2.20.2 Overview.............................................................................................................................................291 2.20.3 Technical Description..........................................................................................................................292 2.20.3.1 Combined Cabinets and Cabinet Groups of the BTS3012.........................................................292 2.20.3.2 Combined Cabinets and Cabinet Groups of the BTS3006C......................................................293 2.20.3.3 Combined Cabinets and Cabinet Groups of the BTS3002E.......................................................295 2.20.3.4 Hybrid Cabinet Groups of the BTS3012 and the BTS3X..........................................................297 2.20.4 Engineering Guidelines.......................................................................................................................298 2.20.5 Parameters...........................................................................................................................................298 2.20.6 Counters...............................................................................................................................................298 2.20.7 Glossary...............................................................................................................................................298 2.20.8 Reference Documents..........................................................................................................................298 2.21 BTS Ring Topology......................................................................................................................................299 2.21.1 Introduction.........................................................................................................................................299 2.21.1.1 Scope..........................................................................................................................................299 2.21.1.2 Intended Audience......................................................................................................................299 2.21.1.3 Change History...........................................................................................................................299 2.21.2 Overview.............................................................................................................................................300 2.21.3 Technical Description..........................................................................................................................302 2.21.3.1 Networking Modes.....................................................................................................................302 2.21.3.2 Application Scenarios.................................................................................................................303 2.21.3.3 BTS Ring Topology Categories.................................................................................................303 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
2.21.3.4 Switchover Modes......................................................................................................................305 2.21.4 Engineering Guidelines.......................................................................................................................306 2.21.5 Parameters...........................................................................................................................................307 2.21.6 Counters...............................................................................................................................................310 2.21.7 Glossary...............................................................................................................................................310 2.21.8 Reference Documents..........................................................................................................................310 2.22 Cell Broadcast...............................................................................................................................................311 2.22.1 Introduction.........................................................................................................................................311 2.22.1.1 Scope..........................................................................................................................................311 2.22.1.2 Intended Audience......................................................................................................................311 2.22.1.3 Change History...........................................................................................................................311 2.22.2 Overview.............................................................................................................................................312 2.22.3 Technical Description..........................................................................................................................314 2.22.3.1 Technical Principle.....................................................................................................................314 2.22.3.2 Cell Broadcast Messages............................................................................................................316 2.22.3.3 Standard Cell Broadcast.............................................................................................................316 2.22.3.4 Simple Cell Broadcast................................................................................................................318 2.22.4 Parameters...........................................................................................................................................318 2.22.5 Counters...............................................................................................................................................328 2.22.6 Glossary...............................................................................................................................................328 2.22.7 Reference Documents..........................................................................................................................328 2.23 Channel Management...................................................................................................................................328 2.23.1 Introduction.........................................................................................................................................328 2.23.1.1 Scope..........................................................................................................................................328 2.23.1.2 Intended Audience......................................................................................................................328 2.23.1.3 Change History...........................................................................................................................329 2.23.2 Overview.............................................................................................................................................329 2.23.3 Technical Description..........................................................................................................................330 2.23.3.1 Channel allocation procedure.....................................................................................................330 2.23.3.2 Channel Allocation in the Immediate Assignment Procedure....................................................331 2.23.3.3 Channel Allocation in the Assignment Procedure......................................................................331 2.23.3.4 Channel Allocation in the Handover Procedure.........................................................................333 2.23.3.5 Huawei Channel Allocation Algorithm......................................................................................333 1. Channel Priorities.................................................................................................................................334 2. Channel Allocate Strategy....................................................................................................................335 3. Preferentially Allocating Channels on the BCCH TRX to Non-AMR Calls.......................................336 2.23.3.6 Post-Processing of Channel Allocation......................................................................................336 2.23.4 Parameters...........................................................................................................................................336 2.23.5 Counters...............................................................................................................................................342 2.23.6 Glossary...............................................................................................................................................342 2.23.7 Reference Documents..........................................................................................................................342 2.24 Ciphering......................................................................................................................................................343 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. x
Contents
2.24.1 Introduction.........................................................................................................................................343 2.24.1.1 Scope..........................................................................................................................................343 2.24.1.2 Intended Audience......................................................................................................................343 2.24.1.3 Change History...........................................................................................................................343 2.24.2 Overview.............................................................................................................................................344 2.24.3 Technical Description..........................................................................................................................345 2.24.3.1 Kc and Its Generation.................................................................................................................345 2.24.3.2 A5 Ciphering Algorithm.............................................................................................................346 2.24.3.3 Algorithm Selection....................................................................................................................347 2.24.3.4 Signaling Procedure....................................................................................................................348 2.24.3.5 Improvements in A5 Ciphering Algorithm................................................................................349 2.24.3.6 Impact on KPI.............................................................................................................................350 2.24.4 Engineering Guidelines.......................................................................................................................350 2.24.5 Parameters...........................................................................................................................................350 2.24.6 Counters...............................................................................................................................................352 2.24.7 Glossary...............................................................................................................................................352 2.24.8 Reference Documents..........................................................................................................................352 2.25 Discontinuous Transmission and Discontinuous Reception........................................................................353 2.25.1 Introduction.........................................................................................................................................353 2.25.1.1 Scope..........................................................................................................................................353 2.25.1.2 Intended Audience......................................................................................................................353 2.25.1.3 Change History...........................................................................................................................353 2.25.2 Overview.............................................................................................................................................354 2.25.3 Technical Description..........................................................................................................................354 2.25.3.1 DTX............................................................................................................................................354 2.25.3.2 DRX............................................................................................................................................356 2.25.4 Parameters...........................................................................................................................................357 2.25.5 Counters...............................................................................................................................................360 2.25.6 Glossary...............................................................................................................................................360 2.25.7 Reference Documents..........................................................................................................................360 2.26 Dual Carriers in Downlink...........................................................................................................................360 2.26.1 Introduction.........................................................................................................................................360 2.26.1.1 Scope..........................................................................................................................................360 2.26.1.2 Intended Audience......................................................................................................................360 2.26.1.3 Change History...........................................................................................................................361 2.26.2 Overview.............................................................................................................................................361 2.26.3 Technical Description..........................................................................................................................363 2.26.3.1 Channel Allocation Algorithm...................................................................................................363 2.26.3.2 MSRD.........................................................................................................................................364 2.26.4 Engineering Guidelines.......................................................................................................................365 2.26.5 Parameters...........................................................................................................................................365 2.26.6 Counters...............................................................................................................................................367 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
2.26.7 Glossary...............................................................................................................................................367 2.26.8 Reference Documents..........................................................................................................................367 2.27 DTM.............................................................................................................................................................367 2.27.1 Introduction.........................................................................................................................................367 2.27.1.1 Scope..........................................................................................................................................367 2.27.1.2 Intended Audience......................................................................................................................367 2.27.1.3 Change History...........................................................................................................................368 2.27.2 Overview.............................................................................................................................................368 2.27.3 Technical Description..........................................................................................................................369 2.27.3.1 Channel Operation Mode............................................................................................................369 2.27.3.2 DTM Multislot Capability..........................................................................................................370 2.27.3.3 Channel Allocation.....................................................................................................................372 2.27.3.4 Using the Main DCCH to Transmit GPRS Signaling in Dedicated Mode.................................374 2.27.3.5 DTM Services.............................................................................................................................375 2.27.4 Engineering Guidelines.......................................................................................................................379 2.27.5 Parameters...........................................................................................................................................379 2.27.6 Counters...............................................................................................................................................381 2.27.7 Glossary...............................................................................................................................................381 2.27.8 Reference Documents..........................................................................................................................381 2.28 Dynamic Channel Conversion......................................................................................................................382 2.28.1 Introduction.........................................................................................................................................382 2.28.1.1 Scope..........................................................................................................................................382 2.28.1.2 Intended Audience......................................................................................................................382 2.28.1.3 Change History...........................................................................................................................382 2.28.2 Overview.............................................................................................................................................383 2.28.3 Technical Description..........................................................................................................................384 2.28.3.1 Dynamic SDCCH Conversion....................................................................................................384 1. Overview..............................................................................................................................................384 2. Dynamic SDCCH Conversion Decision...............................................................................................384 3. Dynamic SDCCH Conversion Execution.............................................................................................388 4. SDCCH Reversion Decision................................................................................................................389 5. SDCCH Reversion Procedure..............................................................................................................390 6. Impact...................................................................................................................................................390 2.28.3.2 TCH HR/FR Conversion............................................................................................................391 1. Overview..............................................................................................................................................391 2. Rate Adjustment Algorithms for Different Channel Requests.............................................................391 3. TCH HR/FR Conversion Procedures...................................................................................................394 2.28.3.3 Dynamic PDCH Conversion......................................................................................................396 1. Overview..............................................................................................................................................396 2. Dynamic PDCH Conversion Procedure...............................................................................................396 2.28.4 Parameters...........................................................................................................................................399 2.28.5 Counters...............................................................................................................................................401 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xii
Contents
2.28.6 Glossary...............................................................................................................................................401 2.28.7 Reference Documents..........................................................................................................................401 2.29 Easy GSM.....................................................................................................................................................401 2.29.1 Introduction.........................................................................................................................................402 2.29.1.1 Scope..........................................................................................................................................402 2.29.1.2 Intended Audience......................................................................................................................402 2.29.1.3 Change History...........................................................................................................................402 2.29.2 Overview.............................................................................................................................................403 2.29.3 Technical Description..........................................................................................................................404 2.29.3.1 Automatic Frequency Planning of Compact BTS......................................................................404 1. Overview..............................................................................................................................................404 2. Algorithm..............................................................................................................................................405 3. Procedure..............................................................................................................................................405 2.29.3.2 Automatic Frequency Optimization of Compact BTS...............................................................407 1. Overview..............................................................................................................................................407 2. Algorithm..............................................................................................................................................407 2.29.3.3 Automatic Capacity and Coverage Planning of Compact BTS..................................................410 1. Overview..............................................................................................................................................410 2. Algorithm..............................................................................................................................................410 2.29.4 Dependency.........................................................................................................................................411 2.29.5 Engineering Guidelines.......................................................................................................................412 2.29.6 Parameters...........................................................................................................................................413 2.29.7 Counters...............................................................................................................................................415 2.29.8 Glossary...............................................................................................................................................415 2.29.9 Reference Documents..........................................................................................................................415 2.30 EFR...............................................................................................................................................................415 2.30.1 Introduction.........................................................................................................................................415 2.30.1.1 Scope..........................................................................................................................................415 2.30.1.2 Intended Audience......................................................................................................................415 2.30.1.3 Change History...........................................................................................................................416 2.30.2 Overview.............................................................................................................................................416 2.30.3 Technical Description..........................................................................................................................416 2.30.3.1 Improvement of EFR on FR and HR..........................................................................................417 2.30.3.2 TFO.............................................................................................................................................417 2.30.4 Parameters...........................................................................................................................................417 2.30.5 Counters...............................................................................................................................................418 2.30.6 Glossary...............................................................................................................................................418 2.30.7 Reference Documents..........................................................................................................................418 2.31 EGPRS2........................................................................................................................................................419 2.31.1 Introduction.........................................................................................................................................419 2.31.1.1 Scope..........................................................................................................................................419 2.31.1.2 Intended Audience......................................................................................................................419 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
2.31.1.3 Change History...........................................................................................................................419 2.31.2 Overview.............................................................................................................................................420 2.31.3 Technical Description..........................................................................................................................421 2.31.3.1 Modulation Schemes and Coding Schemes................................................................................421 1. EGPRS2-A Modulation Schemes.........................................................................................................421 2. EGPRS2-A Coding Schemes................................................................................................................423 2.31.3.2 Link Quality Control..................................................................................................................424 1. Overview..............................................................................................................................................424 2. Uplink EGPRS2-A Coding Scheme Adjustment Algorithm................................................................425 3. Downlink EGPRS2-A Coding Scheme Adjustment Algorithm...........................................................426 2.31.3.3 EGPRS Level Selection and Switching......................................................................................426 2.31.3.4 Carrier Allocation Algorithm.....................................................................................................427 2.31.3.5 Channel Allocation Algorithm...................................................................................................427 2.31.3.6 Multiplexing of GPRS, EGPRS, and EGPRS2 Capable MSs ...................................................428 2.31.3.7 Data Transmission......................................................................................................................428 2.31.4 Parameters...........................................................................................................................................429 2.31.5 Counters...............................................................................................................................................436 2.31.6 Glossary...............................................................................................................................................436 2.31.7 Reference Documents..........................................................................................................................436 2.32 eMLPP..........................................................................................................................................................436 2.32.1 Introduction.........................................................................................................................................436 2.32.1.1 Scope..........................................................................................................................................437 2.32.1.2 Intended Audience......................................................................................................................437 2.32.1.3 Change History...........................................................................................................................437 2.32.2 Overview.............................................................................................................................................438 2.32.3 Technical Description..........................................................................................................................438 2.32.3.1 A Interface Parameters Involved in eMLPP...............................................................................438 2.32.3.2 Call Establishment Procedure.....................................................................................................439 2.32.3.3 Priority-Based Resource Reservation.........................................................................................440 2.32.4 Parameters...........................................................................................................................................440 2.32.5 Counters...............................................................................................................................................442 2.32.6 Glossary...............................................................................................................................................442 2.32.7 Reference Documents..........................................................................................................................442 2.33 EMR..............................................................................................................................................................442 2.33.1 Introduction.........................................................................................................................................443 2.33.1.1 Scope..........................................................................................................................................443 2.33.1.2 Intended Audience......................................................................................................................443 2.33.1.3 Change History...........................................................................................................................443 2.33.2 Overview.............................................................................................................................................444 2.33.3 Technical Description..........................................................................................................................445 2.33.3.1 Implementation in the BSS.........................................................................................................445 2.33.3.2 Measurement Report Preprocessing...........................................................................................446 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiv
Contents
2.33.3.3 2G/3G Interoperability...............................................................................................................446 2.33.3.4 DTX............................................................................................................................................447 2.33.3.5 Handover and Power Control.....................................................................................................447 2.33.4 Engineering Guidelines.......................................................................................................................448 2.33.5 Parameters...........................................................................................................................................449 2.33.6 Counters...............................................................................................................................................453 2.33.7 Glossary...............................................................................................................................................453 2.33.8 Reference Documents..........................................................................................................................453 2.34 EPLC............................................................................................................................................................453 2.34.1 Introduction.........................................................................................................................................453 2.34.1.1 Scope..........................................................................................................................................453 2.34.1.2 Intended Audience......................................................................................................................453 2.34.1.3 Change History...........................................................................................................................453 2.34.2 Overview.............................................................................................................................................454 2.34.3 Technical Description..........................................................................................................................454 2.34.4 Parameters...........................................................................................................................................456 2.34.5 Counters...............................................................................................................................................456 2.34.6 Glossary...............................................................................................................................................456 2.34.7 Reference Documents..........................................................................................................................456 2.35 Flex Abis.......................................................................................................................................................456 2.35.1 Introduction.........................................................................................................................................457 2.35.1.1 Scope..........................................................................................................................................457 2.35.1.2 Intended Audience......................................................................................................................457 2.35.1.3 Change History...........................................................................................................................457 2.35.2 Overview.............................................................................................................................................458 2.35.3 Technical Description..........................................................................................................................458 2.35.3.1 Networking Configuration..........................................................................................................460 2.35.3.2 Establishment of Transmission Link..........................................................................................460 2.35.3.3 Algorithm for Half-Rate Channel Allocation Triggered by Abis Overload...............................461 2.35.4 Engineering Guidelines.......................................................................................................................463 2.35.5 Parameters...........................................................................................................................................463 2.35.6 Counters...............................................................................................................................................468 2.35.7 Glossary...............................................................................................................................................469 2.35.8 Reference Documents..........................................................................................................................469 2.36 Flex MAIO...................................................................................................................................................469 2.36.1 Introduction.........................................................................................................................................469 2.36.1.1 Scope..........................................................................................................................................469 2.36.1.2 Intended Audience......................................................................................................................469 2.36.1.3 Change History...........................................................................................................................469 2.36.2 Overview.............................................................................................................................................470 2.36.3 Technical Description..........................................................................................................................471 2.36.3.1 Interference on the FH Network.................................................................................................471 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
2.36.3.2 Working Mechanism..................................................................................................................472 2.36.4 Engineering Guidelines.......................................................................................................................473 2.36.5 Parameters...........................................................................................................................................474 2.36.6 Counters...............................................................................................................................................475 2.36.7 Glossary...............................................................................................................................................475 2.36.8 Reference Documents..........................................................................................................................475 2.37 Flow Control.................................................................................................................................................475 2.37.1 Introduction.........................................................................................................................................475 2.37.1.1 Scope..........................................................................................................................................475 2.37.1.2 Intended Audience......................................................................................................................475 2.37.1.3 Change History...........................................................................................................................475 2.37.2 Overview.............................................................................................................................................477 2.37.3 Technical Description..........................................................................................................................478 2.37.3.1 Message Arrival Rate Control....................................................................................................478 2.37.3.2 Flow Control on LAPD Links....................................................................................................478 2.37.3.3 Cell Flow Control.......................................................................................................................483 2.37.3.4 A Interface Flow Control............................................................................................................486 2.37.3.5 Internal Flow Control.................................................................................................................487 2.37.3.6 Flow Control Based on Cell Priority..........................................................................................487 2.37.3.7 3.7 Flow Control Based on Transmission Resource Management State....................................489 2.37.4 Engineering Guidelines.......................................................................................................................491 2.37.5 Parameters...........................................................................................................................................491 2.37.6 Counters...............................................................................................................................................500 2.37.7 Glossary...............................................................................................................................................500 2.37.8 Reference Documents..........................................................................................................................500 2.38 Frequency Hopping......................................................................................................................................501 2.38.1 Introduction.........................................................................................................................................501 2.38.1.1 Scope..........................................................................................................................................501 2.38.1.2 Intended Audience......................................................................................................................501 2.38.1.3 Change History...........................................................................................................................501 2.38.2 Overview.............................................................................................................................................502 2.38.3 Technical Description..........................................................................................................................504 2.38.3.1 Baseband FH...............................................................................................................................504 2.38.3.2 RF FH.........................................................................................................................................505 2.38.3.3 Hybrid FH...................................................................................................................................506 2.38.4 Engineering Guidelines.......................................................................................................................506 2.38.4.1 Limitation of the CA List on FH................................................................................................506 2.38.4.2 Limitation on Frequency Spacing...............................................................................................507 2.38.4.3 Data Configuration Related to FH..............................................................................................508 2.38.5 Parameters...........................................................................................................................................508 2.38.6 Counters...............................................................................................................................................510 2.38.7 Glossary...............................................................................................................................................510 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvi
Contents
2.38.8 Reference Documents..........................................................................................................................510 2.39 Four-Way Receive Diversity........................................................................................................................510 2.39.1 Introduction.........................................................................................................................................510 2.39.1.1 Scope..........................................................................................................................................511 2.39.1.2 Intended Audience......................................................................................................................511 2.39.1.3 Change History...........................................................................................................................511 2.39.2 Overview.............................................................................................................................................512 2.39.3 Technical Description..........................................................................................................................512 2.39.3.1 Technical Principle.....................................................................................................................512 2.39.3.2 Four-Way Receive Diversity Algorithms...................................................................................513 2.39.4 Parameters...........................................................................................................................................515 2.39.5 Counters...............................................................................................................................................516 2.39.6 Glossary...............................................................................................................................................516 2.39.7 Reference Documents..........................................................................................................................516 2.40 GPRS/EGPRS Channel Management..........................................................................................................516 2.40.1 Introduction.........................................................................................................................................516 2.40.1.1 Scope..........................................................................................................................................516 2.40.1.2 Intended Audience......................................................................................................................516 2.40.1.3 Change History...........................................................................................................................516 2.40.2 Overview.............................................................................................................................................518 2.40.3 Technical Description..........................................................................................................................519 2.40.3.1 Classification of PDCHs.............................................................................................................519 2.40.3.2 PDCH Allocation Algorithm......................................................................................................520 1. Overview..............................................................................................................................................520 2. Preprocessing........................................................................................................................................521 3. Algorithm..............................................................................................................................................522 2.40.3.3 Dynamic PDCH Conversion Algorithm.....................................................................................523 1. Overview..............................................................................................................................................523 2. Preprocessing........................................................................................................................................524 3. Algorithm..............................................................................................................................................524 2.40.3.4 Dynamic PDCH Release Algorithm...........................................................................................526 1. Overview..............................................................................................................................................526 2. Algorithm..............................................................................................................................................526 2.40.4 Engineering Guidelines.......................................................................................................................529 2.40.5 Parameters...........................................................................................................................................530 2.40.6 Counters...............................................................................................................................................535 2.40.7 Glossary...............................................................................................................................................536 2.40.8 Reference Documents..........................................................................................................................536 2.41 GPRS/EGPRS Connection Control and Transfer.........................................................................................536 2.41.1 Introduction.........................................................................................................................................536 2.41.1.1 Scope..........................................................................................................................................536 2.41.1.2 Intended Audience......................................................................................................................536 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
2.41.1.3 Change History...........................................................................................................................537 2.41.2 Overview.............................................................................................................................................538 2.41.3 Technical Description..........................................................................................................................539 2.41.3.1 Establishment of an Uplink TBF................................................................................................539 1. Establishment of an Uplink TBF on the CCCH...................................................................................539 2. Establishment of an Uplink TBF on the PCCCH.................................................................................542 3. Establishment of an Uplink TBF on the PACCH.................................................................................542 4. Dynamic Adjustment for Transmission Interval of the RRBP Field....................................................544 2.41.3.2 Enhancement of Extended Uplink TBF Function......................................................................545 1. Early TBF Establishment......................................................................................................................545 2. Sending Dummy Control Block...........................................................................................................545 2.41.3.3 Establishment of a Downlink TBF.............................................................................................546 1. Establishment of a Downlink TBF on the CCCH................................................................................546 2. Establishment of a Downlink TBF on the PCCCH..............................................................................547 3. Establishment of a Downlink TBF on the PACCH..............................................................................547 2.41.3.4 Release of a TBF........................................................................................................................549 1. Release of a Non-Extended Uplink TBF..............................................................................................549 2. Release of an Extended Uplink TBF....................................................................................................550 3. Release of a Downlink TBF.................................................................................................................552 2.41.3.5 Uplink Data Transmission..........................................................................................................552 1. Dynamic Allocation Mode...................................................................................................................553 2. Extended Dynamic Mode.....................................................................................................................553 3. Handling of LLC PDUs and RLC Data Blocks....................................................................................554 4. RLC Mode............................................................................................................................................555 5. Uplink Access Congestion Control......................................................................................................555 2.41.3.6 Downlink Data Transmission.....................................................................................................556 1. Scheduling of Downlink Radio Blocks................................................................................................556 2. Handling of LLC PDUs and RLC Data Blocks....................................................................................556 3. RLC Mode............................................................................................................................................557 4. Downlink Flow Control........................................................................................................................557 5. LLC PDU Lifetime Supervision...........................................................................................................558 6. Flush LL Procedure..............................................................................................................................558 2.41.3.7 Reassignment of a TBF..............................................................................................................559 1. Reassignment of an Uplink TBF..........................................................................................................559 2. Reassignment of a Downlink TBF.......................................................................................................559 3. Reassignment of the Concurrent Uplink and Downlink TBFs (TS Procedure)...................................559 2.41.3.8 Suspend and Resume..................................................................................................................560 1. Suspend.................................................................................................................................................560 2. Resume.................................................................................................................................................560 2.41.4 Parameters...........................................................................................................................................561 2.41.5 Counters...............................................................................................................................................565 2.41.6 Glossary...............................................................................................................................................565 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xviii
Contents
2.41.7 Reference Documents..........................................................................................................................565 2.42 GPRS/EGPRS Link Quality Control............................................................................................................566 2.42.1 Introduction.........................................................................................................................................566 2.42.1.1 Scope..........................................................................................................................................566 2.42.1.2 Intended Audience......................................................................................................................566 2.42.1.3 Change History...........................................................................................................................566 2.42.2 Overview.............................................................................................................................................567 2.42.3 Technical Description..........................................................................................................................568 2.42.3.1 GPRS Coding Scheme Adjustment Algorithm..........................................................................569 2.42.3.2 EGPRS Coding Scheme Adjustment Algorithm........................................................................570 1. Overview..............................................................................................................................................570 2. Uplink EGPRS Coding Scheme Adjustment Algorithm......................................................................571 3. Downlink EGPRS Coding Scheme Adjustment Algorithm.................................................................573 2.42.4 Parameters...........................................................................................................................................574 2.42.5 Counters...............................................................................................................................................581 2.42.6 Glossary...............................................................................................................................................582 2.42.7 Reference Documents..........................................................................................................................582 2.43 GPRS/EGPRS Overview..............................................................................................................................582 2.43.1 Introduction.........................................................................................................................................582 2.43.1.1 Scope..........................................................................................................................................582 2.43.1.2 Intended Audience......................................................................................................................582 2.43.1.3 Change History...........................................................................................................................582 2.43.2 Overview.............................................................................................................................................583 2.43.3 Technical Description..........................................................................................................................584 2.43.3.1 Networking Configuration..........................................................................................................584 1. Overview..............................................................................................................................................584 2. Gb Interface..........................................................................................................................................586 3. Pb Interface...........................................................................................................................................590 2.43.3.2 Definitions..................................................................................................................................593 1. Modulation and Coding Schemes.........................................................................................................593 2. Packet Data Logical Channels..............................................................................................................596 3. Radio Link Control Modes...................................................................................................................599 4. Network Operation Modes...................................................................................................................599 5. Packet System Information...................................................................................................................600 2.43.3.3 System Procedures......................................................................................................................601 1. Packet Access.......................................................................................................................................601 2. Radio Resource Allocation...................................................................................................................602 3. TBF Resource Assignment...................................................................................................................603 4. EGPRS Link Quality Control...............................................................................................................604 5. Paging...................................................................................................................................................605 6. Timing Advance...................................................................................................................................606 7. Flow Control.........................................................................................................................................607 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
8. Packet QoS...........................................................................................................................................608 9. Packet Power Control...........................................................................................................................609 10. Cell Reselection Control.....................................................................................................................609 11. Idle Timeslot Assignment...................................................................................................................610 2.43.4 Parameters...........................................................................................................................................611 2.43.5 Counters...............................................................................................................................................631 2.43.6 Glossary...............................................................................................................................................631 2.43.7 Reference Documents..........................................................................................................................631 2.44 GPRS/EGPRS QoS.......................................................................................................................................631 2.44.1 Introduction.........................................................................................................................................631 2.44.1.1 Scope..........................................................................................................................................631 2.44.1.2 Intended Audience......................................................................................................................632 2.44.1.3 Change History...........................................................................................................................632 2.44.2 Overview.............................................................................................................................................633 2.44.3 Technical Description..........................................................................................................................635 2.44.3.1 PFM Procedures.........................................................................................................................635 1. PFC Establishment Procedure..............................................................................................................635 2. PFC Modification Procedure................................................................................................................636 3. PFC Deletion Procedure.......................................................................................................................638 2.44.3.2 Mapping From R97/R98 QoS Attributes to R99 QoS Attributes...............................................638 2.44.3.3 QoS of Interactive, Background, and BE Services.....................................................................641 2.44.3.4 QoS of Streaming Services.........................................................................................................643 1. GBR Assurance....................................................................................................................................643 2. Resource Preemption............................................................................................................................644 2.44.3.5 QoS of Conversational Services.................................................................................................645 2.44.3.6 QoS of PoC Service....................................................................................................................646 2.44.4 Parameters...........................................................................................................................................647 2.44.5 Counters...............................................................................................................................................652 2.44.6 Glossary...............................................................................................................................................652 2.44.7 Reference Documents..........................................................................................................................652 2.45 Half-Rate Speech..........................................................................................................................................652 2.45.1 Introduction.........................................................................................................................................652 2.45.1.1 Scope..........................................................................................................................................653 2.45.1.2 Intended Audience......................................................................................................................653 2.45.1.3 Change History...........................................................................................................................653 2.45.2 Overview.............................................................................................................................................654 2.45.3 Technical Description..........................................................................................................................654 2.45.3.1 Principles....................................................................................................................................654 2.45.3.2 Channel Allocation on the Um Interface....................................................................................655 2.45.3.3 Channel Allocation on the Abis Interface..................................................................................655 2.45.3.4 TRAU.........................................................................................................................................656 2.45.3.5 AMR HR.....................................................................................................................................656 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xx
Contents
2.45.3.6 DTX............................................................................................................................................656 2.45.3.7 Handover....................................................................................................................................656 2.45.3.8 Power Control.............................................................................................................................656 2.45.3.9 Local Switching..........................................................................................................................656 2.45.3.10 Impact on KPIs.........................................................................................................................657 2.45.3.11 Impact on Equipment................................................................................................................657 2.45.4 Engineering Guidelines.......................................................................................................................657 2.45.5 Parameters...........................................................................................................................................658 2.45.6 Counters...............................................................................................................................................659 2.45.7 Glossary...............................................................................................................................................659 2.45.8 Reference Documents..........................................................................................................................659 2.46 Handover......................................................................................................................................................660 2.46.1 Introduction.........................................................................................................................................660 2.46.1.1 Scope..........................................................................................................................................660 2.46.1.2 Intended Audience......................................................................................................................660 2.46.1.3 Change History...........................................................................................................................660 2.46.2 Overview.............................................................................................................................................663 2.46.3 Technical Description..........................................................................................................................668 2.46.3.1 Measurement Report Processing................................................................................................668 2.46.3.2 Handover Preprocessing.............................................................................................................670 2.46.3.3 Forced Handover........................................................................................................................673 2.46.3.4 Handover Decision Based on Handover Algorithm I.................................................................675 1. Quick Handover....................................................................................................................................675 2. TA Handover........................................................................................................................................677 3. BQ Handover........................................................................................................................................678 4. Rapid Level Drop Handover.................................................................................................................679 5. Interference Handover..........................................................................................................................680 6. Handover Due to No Downlink Measurement Report.........................................................................681 7. Enhanced Dual-Band Network Handover............................................................................................682 8. Load Handover.....................................................................................................................................684 9. Edge Handover.....................................................................................................................................687 10. Fast-Moving Micro Cell Handover....................................................................................................688 11. Inter-Layer Handover.........................................................................................................................690 12. PBGT Handover.................................................................................................................................692 13. AMR Handover..................................................................................................................................693 14. SDCCH Handover..............................................................................................................................694 15. Other Handovers.................................................................................................................................694 2.46.3.5 Handover Decision Based on Handover Algorithm II...............................................................695 1. Quick Handover....................................................................................................................................696 2. TA Handover........................................................................................................................................698 3. BQ Handover........................................................................................................................................699 4. Interference Handover..........................................................................................................................700 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Contents
5. Handover Due to No Downlink Measurement Report.........................................................................701 6. Enhanced Dual-Band Network Handover............................................................................................702 7. Load Handover.....................................................................................................................................705 8. Edge Handover.....................................................................................................................................705 9. Fast-Moving Micro Cell Handover......................................................................................................706 10. Better Cell Handover..........................................................................................................................708 11. Handover Between a Full-Rate TCH and a Half-Rate TCH..............................................................710 12. SDCCH Handover..............................................................................................................................712 13. Other Handovers.................................................................................................................................712 2.46.4 Parameters...........................................................................................................................................712 2.46.5 Counters...............................................................................................................................................754 2.46.6 Glossary...............................................................................................................................................754 2.46.7 Reference Documents..........................................................................................................................754 2.47 Handover Re-establishment..........................................................................................................................755 2.47.1 Introduction.........................................................................................................................................755 2.47.1.1 Scope..........................................................................................................................................755 2.47.1.2 Intended Audience......................................................................................................................755 2.47.1.3 Change History...........................................................................................................................755 2.47.2 Overview.............................................................................................................................................756 2.47.3 Technical Description..........................................................................................................................756 2.47.3.1 Implementation in the BSS.........................................................................................................756 2.47.3.2 Impact on the KPI.......................................................................................................................757 2.47.4 Parameters...........................................................................................................................................757 2.47.5 Counters...............................................................................................................................................758 2.47.6 Glossary...............................................................................................................................................758 2.47.7 Reference Documents..........................................................................................................................758 2.48 High-Speed Signaling...................................................................................................................................758 2.48.1 Introduction.........................................................................................................................................758 2.48.1.1 Scope..........................................................................................................................................758 2.48.1.2 Intended Audience......................................................................................................................759 2.48.1.3 Change History...........................................................................................................................759 2.48.2 Overview.............................................................................................................................................760 2.48.3 Technical Description..........................................................................................................................760 2.48.3.1 Implementation of 2 Mbit/s Signaling Link...............................................................................760 2.48.3.2 Comparison Between 2 Mbit/s Signaling Link and 64 kbit/s Signaling Link............................763 2.48.4 Parameters...........................................................................................................................................764 2.48.5 Counters...............................................................................................................................................764 2.48.6 Glossary...............................................................................................................................................765 2.48.7 Reference Documents..........................................................................................................................765 2.49 Idle Mode Behavior......................................................................................................................................765 2.49.1 Introduction.........................................................................................................................................765 2.49.1.1 Scope..........................................................................................................................................765 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxii
Contents
2.49.1.2 Intended Audience......................................................................................................................765 2.49.1.3 Change History...........................................................................................................................765 2.49.2 Overview.............................................................................................................................................766 2.49.3 Technical Description..........................................................................................................................767 2.49.3.1 Overview....................................................................................................................................767 2.49.3.2 PLMN Selection.........................................................................................................................767 1. Overview..............................................................................................................................................767 2. Automatic PLMN Selection Mode.......................................................................................................768 3. Manual PLMN Selection Mode............................................................................................................768 2.49.3.3 GSM Cell Selection....................................................................................................................768 1. Overview..............................................................................................................................................768 2. Conditions for Normally Camping on a Cell........................................................................................768 3. Cell Selection Criterion........................................................................................................................769 2.49.3.4 GSM Cell Reselection................................................................................................................770 1. Overview..............................................................................................................................................770 2. Conditions for Triggering Cell Reselection..........................................................................................770 3. Cell Reselection Algorithms.................................................................................................................771 2.49.3.5 Location Area Update.................................................................................................................772 1. Overview..............................................................................................................................................772 2. Location Area.......................................................................................................................................774 3. Normal Location Area Update.............................................................................................................774 4. IMSI Attach/Detach..............................................................................................................................774 5. Periodic Location Area Update............................................................................................................774 2.49.3.6 Control Channels........................................................................................................................775 2.49.3.7 Paging.........................................................................................................................................776 1. Overview..............................................................................................................................................776 2. CCCH Configuration and Paging Group Calculation..........................................................................776 3. CS Paging.............................................................................................................................................778 4. PS Paging..............................................................................................................................................778 5. Paging Modes.......................................................................................................................................778 6. Paging Functions..................................................................................................................................779 2.49.3.8 System Information....................................................................................................................780 1. Overview..............................................................................................................................................780 2. System Information Type 1..................................................................................................................781 3. System Information Types 2, 2BIS, 2TER, and 2QUATER................................................................784 4. System Information Type 3..................................................................................................................787 5. System Information Type 4..................................................................................................................789 6. System Information Type 7..................................................................................................................790 7. System Information Type 8..................................................................................................................790 8. System Information Type 13................................................................................................................791 2.49.3.9 Short Message Service Cell Broadcast.......................................................................................792 2.49.3.10 Public Voice Group Call Service..............................................................................................792 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii
Contents
1. Overview..............................................................................................................................................792 2. System Information..............................................................................................................................793 2.49.4 Parameters...........................................................................................................................................794 2.49.5 Counters...............................................................................................................................................812 2.49.6 Glossary...............................................................................................................................................812 2.49.7 Reference Documents..........................................................................................................................812 2.50 Intelligent Power Consumption Decrease....................................................................................................812 2.50.1 Introduction.........................................................................................................................................812 2.50.1.1 Scope..........................................................................................................................................812 2.50.1.2 Intended Audience......................................................................................................................813 2.50.1.3 Change History...........................................................................................................................813 2.50.2 Overview.............................................................................................................................................814 2.50.3 Technical Description..........................................................................................................................816 2.50.3.1 TRX Power Amplifier Intelligent Shutdown..............................................................................816 2.50.3.2 TRX Power Amplifier Intelligent Shutdown on the Timeslot Level.........................................817 2.50.3.3 Intelligent Combiner Bypass......................................................................................................818 2.50.3.4 Intelligent Adjustment of TRX Working Voltage......................................................................819 1. Overview of Intelligent Adjustment of TRX Working Voltage...........................................................819 2. TRX Working Voltage Adjustment......................................................................................................819 3. Multi-Carrier Intelligent Voltage Regulation.......................................................................................821 2.50.3.5 Channel Allocation Algorithms Concerning Power Consumption Decrease.............................822 2.50.3.6 PSU Smart Control.....................................................................................................................823 2.50.3.7 Power Optimization Based on Channel Type.............................................................................823 2.50.3.8 Active Backup Power Control....................................................................................................824 2.50.3.9 Enhanced BCCH Power Consumption Optimization.................................................................825 2.50.3.10 Dynamic Cell Power Off..........................................................................................................826 1. Overview of Dynamic Cell Power Off.................................................................................................826 2. Dynamic Cell Power Off Algorithm....................................................................................................826 3. Dynamic Cell Power On Algorithm.....................................................................................................828 4. Dynamic Cell Power Off and TRX Power Amplifier Intelligent Shutdown........................................829 2.50.4 Parameters...........................................................................................................................................829 2.50.5 Counters...............................................................................................................................................839 2.50.6 Glossary...............................................................................................................................................839 2.50.7 Reference Documents..........................................................................................................................839 2.51 IP BSS...........................................................................................................................................................839 2.51.1 Introduction.........................................................................................................................................839 2.51.1.1 Scope..........................................................................................................................................839 2.51.1.2 Intended Audience......................................................................................................................839 2.51.1.3 Change History...........................................................................................................................840 2.51.2 Overview.............................................................................................................................................842 2.51.3 Technical Description..........................................................................................................................844 2.51.3.1 Protocol Stacks...........................................................................................................................844 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiv
Contents
1. Protocol Stack on the A Interface.........................................................................................................844 2. Protocol Stack on the Abis Interface....................................................................................................844 3. Protocol Stack on the Gb Interface.......................................................................................................845 4. Protocol Stack on the Ater Interface.....................................................................................................846 2.51.3.2 Network Topologies...................................................................................................................847 1. Network Topologies on the A Interface...............................................................................................847 2. Network Topologies on the Abis Interface...........................................................................................850 3. Network Topologies on the Gb Interface.............................................................................................855 4. Network Topologies on the Ater Interface...........................................................................................855 2.51.4 Parameters...........................................................................................................................................855 2.51.5 Counters...............................................................................................................................................859 2.51.6 Glossary...............................................................................................................................................859 2.51.7 Reference Documents..........................................................................................................................859 2.52 IP Transport Architecture Description.........................................................................................................859 2.52.1 Introduction.........................................................................................................................................859 2.52.1.1 Scope..........................................................................................................................................859 2.52.1.2 Intended Audience......................................................................................................................860 2.52.1.3 Change History...........................................................................................................................860 2.52.2 Overview.............................................................................................................................................860 2.52.2.1 Introduction................................................................................................................................860 2.52.2.2 IP Transport Architecture...........................................................................................................861 2.52.3 Overview of IP Transport Architecture...............................................................................................862 2.52.3.1 Introduction................................................................................................................................862 2.52.3.2 Data Link Layer Protocols..........................................................................................................863 1. Ethernet.................................................................................................................................................863 2. VLAN...................................................................................................................................................865 3. Point-to-Point Protocol.........................................................................................................................867 4. Multilink-PPP.......................................................................................................................................868 2.52.3.3 IP.................................................................................................................................................871 1. Datagram Format..................................................................................................................................871 2. IP Address and Routing........................................................................................................................872 3. Layer 2 Networking and Layer 3 Networking......................................................................................874 2.52.3.4 User Datagram Protocol.............................................................................................................875 2.52.3.5 Real-Time Transport Protocol (RTP).........................................................................................877 2.52.3.6 Stream Control Transmission Protocol (SCTP).........................................................................878 2.52.3.7 MTP3-User Adaptation Layer (M3UA).....................................................................................880 2.52.3.8 Signaling Connection Control Part.............................................................................................881 2.52.4 IP Transmission Efficiency Improvement...........................................................................................881 2.52.4.1 Overview....................................................................................................................................881 2.52.4.2 Frame Protocol Multiplexing......................................................................................................882 1. Datagram Format..................................................................................................................................882 2. FP-Mux Principles................................................................................................................................883 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv
Contents
2.52.4.3 Abis-Mux and Ater-Mux............................................................................................................884 2.52.4.4 UDP-Mux...................................................................................................................................885 1. Packet Format.......................................................................................................................................885 2. Working Principles...............................................................................................................................887 2.52.4.5 Header Compression...................................................................................................................888 1. Address and Control Field Compression..............................................................................................888 2. Protocol Field Compression.................................................................................................................888 3. IP Header Compression........................................................................................................................889 2.52.5 IP Clock Synchronization....................................................................................................................889 2.52.5.1 Introduction................................................................................................................................889 2.52.5.2 Clock over IP..............................................................................................................................890 2.52.5.3 IEEE1588 V2..............................................................................................................................891 2.52.5.4 Synchronous Ethernet.................................................................................................................892 2.52.6 Fault Detection Technologies..............................................................................................................892 2.52.6.1 Overview....................................................................................................................................893 2.52.6.2 ETH OAM..................................................................................................................................893 1. IEEE 802.3ah-Based ETH OAM..........................................................................................................894 2. IEEE 802.1ag-Based ETH OAM..........................................................................................................895 2.52.6.3 Bidirectional Forwarding Detection...........................................................................................896 1. Single-Hop Bidirectional Forwarding Detection..................................................................................898 2. Multi-Hop Bidirectional Forwarding Detection...................................................................................899 2.52.6.4 Address Resolution Protocol Detection......................................................................................900 1. Binding Between SBFD/ARP and IPRT..............................................................................................901 2. Application of SBFD/ARP in VRRP Topology...................................................................................901 2.52.6.5 IP Performance Monitoring........................................................................................................902 2.52.7 Networking Reliability........................................................................................................................903 2.52.7.1 Overview....................................................................................................................................903 2.52.7.2 Board Backup.............................................................................................................................904 2.52.7.3 Ethernet Port Backup..................................................................................................................905 2.52.7.4 Ethernet Port Load Sharing........................................................................................................906 2.52.7.5 Route-Based Port Backup and Load Sharing.............................................................................907 2.52.7.6 Ethernet Link Aggregation.........................................................................................................907 1. Prerequesites for Link Aggregation......................................................................................................907 2. Basic Principles of Link Aggregation..................................................................................................907 3. Application of Link Aggregation.........................................................................................................909 2.52.8 IP DHCP..............................................................................................................................................909 2.52.8.1 Dynamic Host Configuration Protocol.......................................................................................910 2.52.8.2 VLAN Detection.........................................................................................................................910 2.52.9 Parameters...........................................................................................................................................911 2.52.10 Counters.............................................................................................................................................937 2.52.11 Glossary.............................................................................................................................................937 2.52.12 Appendix...........................................................................................................................................937 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvi
Contents
2.52.13 Reference Documents........................................................................................................................938 2.53 Latency Reduction........................................................................................................................................939 2.53.1 Introduction.........................................................................................................................................939 2.53.1.1 Scope..........................................................................................................................................939 2.53.1.2 Intended Audience......................................................................................................................939 2.53.1.3 Change History...........................................................................................................................940 2.53.2 Overview.............................................................................................................................................940 2.53.3 Technical Description..........................................................................................................................942 2.53.3.1 RTTI...........................................................................................................................................942 1. Overview..............................................................................................................................................942 2. RTTI TBF Establishment.....................................................................................................................944 3. PDCH Pair Scheduling.........................................................................................................................945 2.53.3.2 FANR..........................................................................................................................................946 1. Overview .............................................................................................................................................946 2. FANR TBF Establishment....................................................................................................................947 3. FANR Procedure..................................................................................................................................947 2.53.4 Parameters...........................................................................................................................................949 2.53.5 Counters...............................................................................................................................................950 2.53.6 Glossary...............................................................................................................................................950 2.53.7 Reference Documents..........................................................................................................................950 2.54 Local Multiple Signaling Points...................................................................................................................950 2.54.1 Introduction.........................................................................................................................................950 2.54.1.1 Scope..........................................................................................................................................950 2.54.1.2 Intended Audience......................................................................................................................951 2.54.1.3 Change History...........................................................................................................................951 2.54.2 Overview.............................................................................................................................................952 2.54.3 Technical Description..........................................................................................................................952 2.54.4 Parameters...........................................................................................................................................953 2.54.5 Counters...............................................................................................................................................954 2.54.6 Glossary...............................................................................................................................................954 2.54.7 Reference Documents..........................................................................................................................954 2.55 Location Service...........................................................................................................................................954 2.55.1 Introduction.........................................................................................................................................954 2.55.1.1 Scope..........................................................................................................................................954 2.55.1.2 Intended Audience......................................................................................................................954 2.55.1.3 Change History...........................................................................................................................955 2.55.2 Overview.............................................................................................................................................956 2.55.3 Technical Description..........................................................................................................................956 2.55.3.1 Overview....................................................................................................................................956 2.55.3.2 Positioning Procedure.................................................................................................................956 2.55.3.3 Location Estimate.......................................................................................................................957 2.55.3.4 Message Format..........................................................................................................................961 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii
Contents
2.55.3.5 Dependency................................................................................................................................963 2.55.4 Parameters...........................................................................................................................................963 2.55.5 Counters...............................................................................................................................................964 2.55.6 Glossary...............................................................................................................................................964 2.55.7 Reference Documents..........................................................................................................................964 2.56 MSC Pool.....................................................................................................................................................964 2.56.1 Introduction.........................................................................................................................................964 2.56.1.1 Scope..........................................................................................................................................964 2.56.1.2 Intended Audience......................................................................................................................965 2.56.1.3 Change History...........................................................................................................................965 2.56.2 Overview.............................................................................................................................................966 2.56.3 Technical Description..........................................................................................................................966 2.56.3.1 Load Balancing in an MSC Pool................................................................................................967 2.56.3.2 Load Balancing Algorithm.........................................................................................................969 2.56.3.3 Load Adjustment in an MSC Pool..............................................................................................971 2.56.4 Engineering Guidelines.......................................................................................................................975 2.56.5 Parameters...........................................................................................................................................975 2.56.6 Counters...............................................................................................................................................978 2.56.7 Glossary...............................................................................................................................................978 2.56.8 Reference Documents..........................................................................................................................978 2.57 Multiband Network.......................................................................................................................................979 2.57.1 Introduction.........................................................................................................................................979 2.57.1.1 Scope..........................................................................................................................................979 2.57.1.2 Intended Audience......................................................................................................................979 2.57.1.3 Change History...........................................................................................................................979 2.57.2 Overview.............................................................................................................................................980 2.57.3 Technical Description..........................................................................................................................981 2.57.3.1 Multiband Network Principles....................................................................................................981 1. Overview of Multiband Network ........................................................................................................982 2. Cell Reselection....................................................................................................................................982 3. Channel Allocation...............................................................................................................................982 4. Handover..............................................................................................................................................982 2.57.3.2 Network Topologies...................................................................................................................983 2.57.3.3 Overview of Enhanced Dualband Network................................................................................986 1. Overview..............................................................................................................................................986 2. Channel Allocation...............................................................................................................................987 3. Handover..............................................................................................................................................987 2.57.4 Engineering Guidelines.......................................................................................................................987 2.57.5 Parameters...........................................................................................................................................988 2.57.6 Counters...............................................................................................................................................989 2.57.7 Glossary...............................................................................................................................................989 2.57.8 Reference Documents..........................................................................................................................989 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxviii
Contents
2.58 Multi-Site Cell..............................................................................................................................................990 2.58.1 Introduction.........................................................................................................................................990 2.58.1.1 Scope..........................................................................................................................................990 2.58.1.2 Intended Audience......................................................................................................................990 2.58.1.3 Change History...........................................................................................................................990 2.58.2 Overview.............................................................................................................................................991 2.58.3 Technical Description..........................................................................................................................992 2.58.3.1 Synchronization of Subsites over the Um Interface...................................................................992 2.58.3.2 Inter-Subsite Handover...............................................................................................................993 2.58.3.3 Coverage Mode...........................................................................................................................994 2.58.4 Engineering Guidelines.......................................................................................................................998 2.58.5 Parameters...........................................................................................................................................999 2.58.6 Counters.............................................................................................................................................1000 2.58.7 Glossary.............................................................................................................................................1000 2.58.8 Reference Documents........................................................................................................................1000 2.59 NACC.........................................................................................................................................................1000 2.59.1 Introduction.......................................................................................................................................1000 2.59.1.1 Scope........................................................................................................................................1000 2.59.1.2 Intended Audience....................................................................................................................1000 2.59.1.3 Change History.........................................................................................................................1000 2.59.2 Overview of NACC...........................................................................................................................1001 2.59.3 Technical Description........................................................................................................................1002 2.59.3.1 Intra-BSC NACC......................................................................................................................1002 2.59.3.2 Inter-BSC NACC......................................................................................................................1004 2.59.3.3 UTRAN-to-GERAN NACC.....................................................................................................1006 2.59.4 Parameters.........................................................................................................................................1007 2.59.5 Counters.............................................................................................................................................1009 2.59.6 Glossary.............................................................................................................................................1009 2.59.7 Reference Documents........................................................................................................................1009 2.60 NC2.............................................................................................................................................................1009 2.60.1 Introduction.......................................................................................................................................1009 2.60.1.1 Scope........................................................................................................................................1009 2.60.1.2 Intended Audience....................................................................................................................1010 2.60.1.3 Change History.........................................................................................................................1010 2.60.2 Overview...........................................................................................................................................1011 2.60.3 Technical Description........................................................................................................................1012 2.60.3.1 Procedure..................................................................................................................................1012 2.60.3.2 Cell Reselection Algorithms.....................................................................................................1013 2.60.3.3 Cell Reselection Type...............................................................................................................1016 2.60.4 Parameters.........................................................................................................................................1017 2.60.5 Counters.............................................................................................................................................1023 2.60.6 Glossary.............................................................................................................................................1023 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix
Contents
2.60.7 Reference Documents........................................................................................................................1023 2.61 Networking Modes.....................................................................................................................................1023 2.61.1 Introduction.......................................................................................................................................1023 2.61.1.1 Scope........................................................................................................................................1023 2.61.1.2 Intended Audience....................................................................................................................1024 2.61.1.3 Change History.........................................................................................................................1024 2.61.2 Overview...........................................................................................................................................1025 2.61.3 Technical Description........................................................................................................................1025 2.61.3.1 Networking Modes...................................................................................................................1025 2.61.3.2 LAPD Multiplexing at Abis Interface......................................................................................1028 2.61.3.3 16 kbit/s LAPD Signaling Link................................................................................................1031 2.61.4 Engineering Guidelines.....................................................................................................................1032 2.61.5 Parameters.........................................................................................................................................1032 2.61.6 Counters.............................................................................................................................................1034 2.61.7 Glossary.............................................................................................................................................1034 2.61.8 Reference Documents........................................................................................................................1034 2.62 PBT.............................................................................................................................................................1034 2.62.1 Introduction.......................................................................................................................................1034 2.62.1.1 Scope........................................................................................................................................1034 2.62.1.2 Intended Audience....................................................................................................................1034 2.62.1.3 Change History.........................................................................................................................1035 2.62.2 Overview...........................................................................................................................................1035 2.62.3 Technical Description........................................................................................................................1036 2.62.3.1 PBT...........................................................................................................................................1036 2.62.3.2 Dynamic PBT...........................................................................................................................1037 2.62.4 Parameters.........................................................................................................................................1038 2.62.5 Counters.............................................................................................................................................1039 2.62.6 Glossary.............................................................................................................................................1039 2.62.7 Reference Documents........................................................................................................................1039 2.63 PICO Automatic Configuration and Planning............................................................................................1040 2.63.1 Introduction.......................................................................................................................................1040 2.63.1.1 Scope........................................................................................................................................1040 2.63.1.2 Intended Audience....................................................................................................................1040 2.63.1.3 Change History.........................................................................................................................1040 2.63.2 Overview...........................................................................................................................................1041 2.63.3 Technical Description........................................................................................................................1044 2.63.3.1 Automatic Frequency Planning................................................................................................1044 1. Overview............................................................................................................................................1044 2. Algorithm............................................................................................................................................1044 2.63.3.2 Automatic CGI and RAI Planning............................................................................................1046 1. Overview............................................................................................................................................1046 2. Algorithm............................................................................................................................................1046 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxx
Contents
2.63.3.3 Automatic Neighboring Cell Planning.....................................................................................1047 1. Overview............................................................................................................................................1047 2. Algorithm............................................................................................................................................1047 2.63.3.4 Automatic BSIC Planning........................................................................................................1049 1. Overview............................................................................................................................................1049 2. Algorithm............................................................................................................................................1049 2.63.4 Engineering Guidelines.....................................................................................................................1049 2.63.5 Parameters.........................................................................................................................................1050 2.63.6 Counters.............................................................................................................................................1052 2.63.7 Glossary.............................................................................................................................................1052 2.63.8 Reference Documents........................................................................................................................1052 2.64 Power Control.............................................................................................................................................1053 2.64.1 Introduction.......................................................................................................................................1053 2.64.1.1 Scope........................................................................................................................................1053 2.64.1.2 Intended Audience....................................................................................................................1053 2.64.1.3 Change History.........................................................................................................................1053 2.64.2 Overview...........................................................................................................................................1055 2.64.3 Technical Description........................................................................................................................1055 2.64.3.1 Principles..................................................................................................................................1055 1. Measurement of Receive Level and Receive Quality.........................................................................1056 2. Power Control Algorithms..................................................................................................................1057 3. Power Control Procedure....................................................................................................................1057 2.64.3.2 Huawei II Power Control Algorithm........................................................................................1059 2.64.3.3 Huawei III Power Control Algorithm.......................................................................................1062 2.64.3.4 Optimized Huawei III Power Control Algorithm.....................................................................1065 2.64.3.5 Functions Related to Power Control.........................................................................................1067 1. Active Power Control.........................................................................................................................1067 2. SAIC Power Control Optimization.....................................................................................................1067 2.64.4 Parameters.........................................................................................................................................1068 2.64.5 Counters.............................................................................................................................................1090 2.64.6 Glossary.............................................................................................................................................1090 2.64.7 Reference Documents........................................................................................................................1090 2.65 PS Handover...............................................................................................................................................1091 2.65.1 Introduction.......................................................................................................................................1091 2.65.1.1 Scope........................................................................................................................................1091 2.65.1.2 Intended Audience....................................................................................................................1091 2.65.1.3 Change History.........................................................................................................................1091 2.65.2 Overview...........................................................................................................................................1092 2.65.3 Technical Description........................................................................................................................1093 2.65.3.1 Handover Decision...................................................................................................................1093 2.65.3.2 Common Intra-BSC Inter-Cell Handover.................................................................................1093 2.65.3.3 Inter-BSC Inter-Cell Handover................................................................................................1096 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxi
Contents
2.65.3.4 2G/3G Inter-RAT Handover.....................................................................................................1096 2.65.4 Parameters.........................................................................................................................................1097 2.65.5 Counters.............................................................................................................................................1099 2.65.6 Glossary.............................................................................................................................................1099 2.65.7 Reference Documents........................................................................................................................1099 2.66 RAN Sharing..............................................................................................................................................1099 2.66.1 Introduction.......................................................................................................................................1099 2.66.1.1 Scope........................................................................................................................................1099 2.66.1.2 Intended Audience....................................................................................................................1099 2.66.1.3 Change History.........................................................................................................................1100 2.66.2 Overview...........................................................................................................................................1100 2.66.3 Technical Description........................................................................................................................1102 2.66.3.1 Networking Scenario Analysis.................................................................................................1102 2.66.3.2 Operation and Maintenance System.........................................................................................1104 2.66.3.3 Network Elements....................................................................................................................1105 2.66.3.4 Functions..................................................................................................................................1106 2.66.4 Engineering Guidelines.....................................................................................................................1108 2.66.5 Parameters.........................................................................................................................................1109 2.66.6 Counters.............................................................................................................................................1111 2.66.7 Glossary.............................................................................................................................................1111 2.66.8 Reference Documents........................................................................................................................1111 2.67 Robust Air Interface Signaling...................................................................................................................1111 2.67.1 Introduction.......................................................................................................................................1111 2.67.1.1 Scope........................................................................................................................................1111 2.67.1.2 Intended Audience....................................................................................................................1111 2.67.1.3 Change History.........................................................................................................................1112 2.67.2 Overview...........................................................................................................................................1112 2.67.3 Technical Description........................................................................................................................1113 2.67.3.1 Repeated Downlink FACCH....................................................................................................1113 1. Overview............................................................................................................................................1113 2. Implementation in the BSS.................................................................................................................1113 3. Impact on the KPI...............................................................................................................................1114 2.67.3.2 Repeated SACCH.....................................................................................................................1114 1. Overview............................................................................................................................................1114 2. Implementation in the BSS.................................................................................................................1114 3. Impact on the KPI...............................................................................................................................1115 2.67.4 Engineering Guidelines.....................................................................................................................1115 2.67.5 Parameters.........................................................................................................................................1115 2.67.6 Counters.............................................................................................................................................1116 2.67.7 Glossary.............................................................................................................................................1116 2.67.8 Reference Documents........................................................................................................................1116 2.68 Semipermanent Connection........................................................................................................................1117 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxii
Contents
2.68.1 Introduction.......................................................................................................................................1117 2.68.1.1 Scope........................................................................................................................................1117 2.68.1.2 Intended Audience....................................................................................................................1117 2.68.1.3 Change History.........................................................................................................................1117 2.68.2 Overview...........................................................................................................................................1118 2.68.3 Technical Description........................................................................................................................1118 2.68.3.1 Semipermanent Connection......................................................................................................1119 2.68.3.2 Implementation of Semipermanent Connection.......................................................................1120 2.68.4 Engineering Guidelines.....................................................................................................................1121 2.68.5 Parameters.........................................................................................................................................1123 2.68.6 Counters.............................................................................................................................................1125 2.68.7 Glossary.............................................................................................................................................1126 2.68.8 Reference Documents........................................................................................................................1126 2.69 SGSN Pool..................................................................................................................................................1126 2.69.1 Introduction.......................................................................................................................................1126 2.69.1.1 Scope........................................................................................................................................1126 2.69.1.2 Intended Audience....................................................................................................................1126 2.69.1.3 Change History.........................................................................................................................1126 2.69.2 Overview...........................................................................................................................................1127 2.69.3 Technical Description........................................................................................................................1129 2.69.3.1 Routing of an MS to an SGSN.................................................................................................1129 2.69.3.2 SGSN Selection Based on Load Balancing Algorithm............................................................1130 2.69.3.3 Load Adjustment in an SGSN Pool..........................................................................................1131 2.69.4 Parameters.........................................................................................................................................1134 2.69.5 Counters.............................................................................................................................................1136 2.69.6 Glossary.............................................................................................................................................1136 2.69.7 Reference Documents........................................................................................................................1136 2.70 Soft-Synchronized Network.......................................................................................................................1136 2.70.1 Introduction.......................................................................................................................................1136 2.70.1.1 Scope........................................................................................................................................1136 2.70.1.2 Intended Audience....................................................................................................................1136 2.70.1.3 Change History.........................................................................................................................1136 2.70.2 Overview...........................................................................................................................................1137 2.70.3 Technical Description........................................................................................................................1140 2.70.3.1 Determining a Pair of Optimal Neighboring Cells...................................................................1140 2.70.3.2 Collecting the Offset Information of BTSs..............................................................................1141 2.70.3.3 Synchronizing Two BTSs.........................................................................................................1142 2.70.3.4 Managing the Synchronization Status of BTSs........................................................................1145 2.70.4 Engineering Guidelines.....................................................................................................................1147 2.70.5 Parameters.........................................................................................................................................1148 2.70.6 Counters.............................................................................................................................................1153 2.70.7 Glossary.............................................................................................................................................1153 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxiii
Contents
2.70.8 Reference Documents........................................................................................................................1153 2.71 TC Pool.......................................................................................................................................................1153 2.71.1 Introduction.......................................................................................................................................1153 2.71.1.1 Scope........................................................................................................................................1154 2.71.1.2 Intended Audience....................................................................................................................1154 2.71.1.3 Change History.........................................................................................................................1154 2.71.2 Overview...........................................................................................................................................1155 2.71.3 Technical Description........................................................................................................................1157 2.71.3.1 Working Principle.....................................................................................................................1157 2.71.3.2 Networking...............................................................................................................................1157 2.71.3.3 Hardware Cabling.....................................................................................................................1160 2.71.3.4 Interface Timeslots...................................................................................................................1163 2.71.3.5 Hardware Management.............................................................................................................1164 2.71.4 Engineering Guidelines.....................................................................................................................1165 2.71.5 Parameters.........................................................................................................................................1166 2.71.6 Counters.............................................................................................................................................1168 2.71.7 Glossary.............................................................................................................................................1168 2.71.8 Reference Documents........................................................................................................................1168 2.72 TFO.............................................................................................................................................................1169 2.72.1 Introduction.......................................................................................................................................1169 2.72.1.1 Scope........................................................................................................................................1169 2.72.1.2 Intended Audience....................................................................................................................1169 2.72.1.3 Change History.........................................................................................................................1169 2.72.2 Overview...........................................................................................................................................1170 2.72.3 Technical Description........................................................................................................................1171 2.72.3.1 TFO Messages..........................................................................................................................1171 2.72.3.2 TFO Frame...............................................................................................................................1172 2.72.3.3 Prerequisites for the TFO Establishment..................................................................................1172 2.72.3.4 TRAU Operating Process in TFO Mode..................................................................................1174 2.72.3.5 DTX and VQE After the TFO Establishment..........................................................................1175 2.72.3.6 TFO Voice Quality Improvement.............................................................................................1175 2.72.4 Parameters.........................................................................................................................................1176 2.72.5 Counters.............................................................................................................................................1179 2.72.6 Glossary.............................................................................................................................................1179 2.72.7 Reference Documents........................................................................................................................1179 2.73 Transmit Diversity......................................................................................................................................1179 2.73.1 Introduction.......................................................................................................................................1179 2.73.1.1 Scope........................................................................................................................................1180 2.73.1.2 Intended Audience....................................................................................................................1180 2.73.1.3 Change History.........................................................................................................................1180 2.73.2 Overview...........................................................................................................................................1181 2.73.3 Technical Description........................................................................................................................1181 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxiv
Contents
2.73.3.1 Transmit Diversity....................................................................................................................1181 2.73.3.2 Dynamic Transmit Diversity....................................................................................................1182 2.73.4 Parameters.........................................................................................................................................1183 2.73.5 Counters.............................................................................................................................................1185 2.73.6 Glossary.............................................................................................................................................1185 2.73.7 Reference Documents........................................................................................................................1185 2.74 TRX Cooperation.......................................................................................................................................1185 2.74.1 Introduction.......................................................................................................................................1185 2.74.1.1 Scope........................................................................................................................................1185 2.74.1.2 Intended Audience....................................................................................................................1185 2.74.1.3 Change History.........................................................................................................................1185 2.74.2 Overview...........................................................................................................................................1186 2.74.3 Technical Description........................................................................................................................1187 2.74.3.1 BCCH TRX Cooperation..........................................................................................................1187 1. BSC-controlled BCCH TRX cooperation..........................................................................................1187 2. BSC-Collaborated BCCH TRX Cooperation.....................................................................................1191 2.74.3.2 Baseband FH TRX Cooperation...............................................................................................1194 2.74.3.3 TRX Channel Cooperation.......................................................................................................1195 2.74.4 Parameters.........................................................................................................................................1197 2.74.5 Counters.............................................................................................................................................1204 2.74.6 Glossary.............................................................................................................................................1204 2.74.7 Reference Documents........................................................................................................................1205 2.75 VGCS/VBS.................................................................................................................................................1205 2.75.1 Introduction.......................................................................................................................................1205 2.75.1.1 Scope........................................................................................................................................1205 2.75.1.2 Intended Audience....................................................................................................................1205 2.75.1.3 Change History.........................................................................................................................1205 2.75.2 Overview...........................................................................................................................................1206 2.75.3 Technical Description........................................................................................................................1207 2.75.3.1 VGCS........................................................................................................................................1207 1. Overview............................................................................................................................................1207 2. Initiation and Establishment of a VGCS Call.....................................................................................1209 3. Reception of a VGCS Call..................................................................................................................1214 4. Release and Seizure of the Uplink of the Group Call Channel..........................................................1214 5. Handover of a VGCS Call..................................................................................................................1215 6. Release of a VGCS Call.....................................................................................................................1218 2.75.3.2 VBS..........................................................................................................................................1218 1. Overview............................................................................................................................................1218 2. Initiation and Establishment of a VBS Call........................................................................................1218 3. Reception of a VBS Call....................................................................................................................1220 4. Handover of a VBS Call.....................................................................................................................1220 5. Release of a VBS Call........................................................................................................................1220 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxv
Contents
2.75.3.3 Delayed Assignment of the VGCS/VBS Channel....................................................................1220 2.75.3.4 Downlink Detection..................................................................................................................1221 2.75.3.5 Initiation of a VGCS Call Through One Channel....................................................................1221 2.75.3.6 Talker Identification.................................................................................................................1222 2.75.3.7 eMLPP in VGCS/VBS.............................................................................................................1222 1. Service Preemption.............................................................................................................................1222 2. Resource Preemption..........................................................................................................................1224 2.75.3.8 Fast VGCS Call........................................................................................................................1224 2.75.3.9 Enhancement of VGCS/VBS....................................................................................................1224 1. Fallback..............................................................................................................................................1225 2. VGCS Resource Check......................................................................................................................1225 2.75.4 Engineering Guidelines.....................................................................................................................1226 2.75.5 Parameters.........................................................................................................................................1226 2.75.6 Counters.............................................................................................................................................1231 2.75.7 Glossary.............................................................................................................................................1231 2.75.8 Reference Documents........................................................................................................................1232 2.76 Voice Quality Index....................................................................................................................................1232 2.76.1 Introduction.......................................................................................................................................1232 2.76.1.1 Scope........................................................................................................................................1232 2.76.1.2 Intended Audience....................................................................................................................1232 2.76.1.3 Change History.........................................................................................................................1232 2.76.2 Overview of VQI...............................................................................................................................1233 2.76.3 Technical Description........................................................................................................................1233 2.76.3.1 Measurement of Voice Quality.................................................................................................1233 2.76.4 Parameters.........................................................................................................................................1235 2.76.5 Counters.............................................................................................................................................1236 2.76.6 Glossary.............................................................................................................................................1236 2.76.7 Reference Documents........................................................................................................................1236 2.77 WB AMR....................................................................................................................................................1236 2.77.1 Introduction.......................................................................................................................................1236 2.77.1.1 Scope........................................................................................................................................1236 2.77.1.2 Intended Audience....................................................................................................................1236 2.77.1.3 Change History.........................................................................................................................1237 2.77.2 Overview...........................................................................................................................................1237 2.77.3 Technical Description........................................................................................................................1238 2.77.3.1 WB AMR Coding and Decoding..............................................................................................1238 2.77.3.2 Speech Rate Adjustment...........................................................................................................1238 2.77.3.3 Rate Adjustment Threshold Adaptation...................................................................................1239 2.77.3.4 Power Control...........................................................................................................................1239 2.77.3.5 TFO...........................................................................................................................................1239 2.77.3.6 DTX..........................................................................................................................................1240 2.77.3.7 WB AMR in A over IP Mode...................................................................................................1240 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxvi
Contents
2.77.3.8 Impact on KPI...........................................................................................................................1240 2.77.4 Engineering Guidelines.....................................................................................................................1241 2.77.5 Parameters.........................................................................................................................................1241 2.77.6 Counters.............................................................................................................................................1245 2.77.7 Glossary.............................................................................................................................................1245 2.77.8 Reference Documents........................................................................................................................1245 2.78 14-Digit Signaling Point Code...................................................................................................................1245 2.78.1 Introduction.......................................................................................................................................1245 2.78.1.1 Scope........................................................................................................................................1245 2.78.1.2 Intended Audience....................................................................................................................1246 2.78.1.3 Change History.........................................................................................................................1246 2.78.2 Overview of 14-Digit Signaling Point Code.....................................................................................1246 2.78.3 Technical Description........................................................................................................................1246 2.78.4 Parameters.........................................................................................................................................1247 2.78.5 Counters.............................................................................................................................................1248 2.78.6 Glossary.............................................................................................................................................1248 2.78.7 Reference Documents........................................................................................................................1248 2.79 2G/3G Co-Transmission by TDM Switching.............................................................................................1249 2.79.1 Introduction.......................................................................................................................................1249 2.79.1.1 Scope........................................................................................................................................1249 2.79.1.2 Intended Audience....................................................................................................................1249 2.79.1.3 Change History.........................................................................................................................1249 2.79.2 Overview of 2G/3G Co-Transmission by TDM Switching...............................................................1249 2.79.3 Technical Description........................................................................................................................1250 2.79.3.1 Principle of Co-Transmission...................................................................................................1250 2.79.3.2 Networking Mode of Co-Transmission....................................................................................1251 2.79.4 Engineering Guidelines.....................................................................................................................1251 2.79.5 Parameters.........................................................................................................................................1251 2.79.6 Counters.............................................................................................................................................1251 2.79.7 Glossary.............................................................................................................................................1251 2.79.8 Reference Documents........................................................................................................................1252 2.80 A Interface Circuit Management ...............................................................................................................1252 2.80.1 Introduction.......................................................................................................................................1252 2.80.1.1 Scope........................................................................................................................................1252 2.80.1.2 Intended Audience....................................................................................................................1252 2.80.1.3 Change History.........................................................................................................................1252 2.80.2 Overview of A Interface Circuit Management..................................................................................1253 2.80.3 Technical Description........................................................................................................................1253 2.80.3.1 Circuit Assignment...................................................................................................................1253 2.80.3.2 Circuit Block.............................................................................................................................1254 2.80.3.3 Circuit Unblock........................................................................................................................1254 2.80.3.4 Group Circuit Block.................................................................................................................1255 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxvii
Contents
2.80.3.5 Group Circuit Unblock.............................................................................................................1256 2.80.3.6 Circuit Unequipped...................................................................................................................1256 2.80.3.7 Circuit Reset.............................................................................................................................1257 2.80.4 Parameters.........................................................................................................................................1258 2.80.5 Counters.............................................................................................................................................1259 2.80.6 Glossary.............................................................................................................................................1259 2.80.7 Reference Documents........................................................................................................................1259 2.81 A Interface Protocol Process......................................................................................................................1259 2.81.1 Introduction.......................................................................................................................................1259 2.81.1.1 Scope........................................................................................................................................1259 2.81.1.2 Intended Audience....................................................................................................................1260 2.81.1.3 Change History.........................................................................................................................1260 2.81.2 Overview of A Interface Protocol Process........................................................................................1260 2.81.3 Technical Description........................................................................................................................1261 2.81.3.1 The Direct Transfer Application Part.......................................................................................1261 2.81.3.2 The BSS Management Application Part...................................................................................1261 2.81.3.3 BSSMAP Procedures................................................................................................................1261 2.81.4 Parameters.........................................................................................................................................1262 2.81.5 Counters.............................................................................................................................................1262 2.81.6 Glossary.............................................................................................................................................1262 2.81.7 Reference Documents........................................................................................................................1262 2.82 A Interface Occupation Rate Monitoring...................................................................................................1262 2.82.1 Introduction.......................................................................................................................................1262 2.82.1.1 Scope........................................................................................................................................1262 2.82.1.2 Intended Audience....................................................................................................................1263 2.82.1.3 Change History.........................................................................................................................1263 2.82.2 Overview of A Interface Occupation Rate Monitoring.....................................................................1263 2.82.3 Technical Description........................................................................................................................1263 2.82.4 Parameters.........................................................................................................................................1264 2.82.5 Counters.............................................................................................................................................1264 2.82.6 Glossary.............................................................................................................................................1264 2.82.7 Reference Documents........................................................................................................................1264 2.83 Adjustment of Adaptive Timing Advance..................................................................................................1265 2.83.1 Introduction.......................................................................................................................................1265 2.83.1.1 Scope........................................................................................................................................1265 2.83.1.2 Intended Audience....................................................................................................................1265 2.83.1.3 Change History.........................................................................................................................1265 2.83.2 Overview of Adjustment of Adaptive Timing Advance....................................................................1265 2.83.3 Technical Description........................................................................................................................1266 2.83.4 Parameters.........................................................................................................................................1267 2.83.5 Counters.............................................................................................................................................1268 2.83.6 Glossary.............................................................................................................................................1268 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxviii
Contents
2.83.7 Reference Documents........................................................................................................................1268 2.84 Ater Interface 4:1 Multiplexing..................................................................................................................1268 2.84.1 Introduction.......................................................................................................................................1268 2.84.1.1 Scope........................................................................................................................................1268 2.84.1.2 Intended Audience....................................................................................................................1268 2.84.1.3 Change History.........................................................................................................................1269 2.84.2 Change History..................................................................................................................................1269 2.84.3 Overview of Ater Interface 4:1 Multiplexing....................................................................................1269 2.84.4 Technical Description........................................................................................................................1270 2.84.5 Engineering Guidelines.....................................................................................................................1271 2.84.6 Parameters.........................................................................................................................................1271 2.84.7 Glossary.............................................................................................................................................1271 2.84.8 Counters.............................................................................................................................................1271 2.84.9 Reference Documents........................................................................................................................1271 2.85 Authentication............................................................................................................................................1271 2.85.1 Introduction.......................................................................................................................................1271 2.85.1.1 Scope........................................................................................................................................1272 2.85.1.2 Intended Audience....................................................................................................................1272 2.85.1.3 Change History.........................................................................................................................1272 2.85.2 Overview of Authentication..............................................................................................................1272 2.85.3 Technical Description........................................................................................................................1273 2.85.3.1 Authentication Principles.........................................................................................................1273 2.85.3.2 Authentication Procedure.........................................................................................................1273 2.85.4 Parameters.........................................................................................................................................1275 2.85.5 Counters.............................................................................................................................................1275 2.85.6 Glossary.............................................................................................................................................1275 2.85.7 Reference Documents........................................................................................................................1276 2.86 Board Switchover.......................................................................................................................................1276 2.86.1 Introduction.......................................................................................................................................1276 2.86.1.1 Scope........................................................................................................................................1276 2.86.1.2 Intended Audience....................................................................................................................1276 2.86.1.3 Change History.........................................................................................................................1276 2.86.2 Overview of Board Switchover.........................................................................................................1277 2.86.3 Technical Description........................................................................................................................1277 2.86.4 Parameters.........................................................................................................................................1278 2.86.5 Counters.............................................................................................................................................1279 2.86.6 Glossary.............................................................................................................................................1280 2.86.7 Reference Documents........................................................................................................................1280 2.87 BSC Cabinet/Subrack Sharing....................................................................................................................1280 2.87.1 Introduction.......................................................................................................................................1280 2.87.1.1 Scope........................................................................................................................................1280 2.87.1.2 Intended Audience....................................................................................................................1280 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxix
Contents
2.87.1.3 Change History.........................................................................................................................1280 2.87.2 Overview of BSC Cabinet/Subrack Sharing.....................................................................................1281 2.87.3 Technical Description........................................................................................................................1281 2.87.3.1 BSC Cabinet Sharing................................................................................................................1281 2.87.3.2 BSC Subrack Sharing...............................................................................................................1282 2.87.4 Parameters.........................................................................................................................................1283 2.87.5 Counters.............................................................................................................................................1283 2.87.6 Glossary.............................................................................................................................................1283 2.87.7 Reference Documents........................................................................................................................1283 2.88 BTS Power Management............................................................................................................................1283 2.88.1 Introduction.......................................................................................................................................1283 2.88.1.1 Scope........................................................................................................................................1284 2.88.1.2 Intended Audience....................................................................................................................1284 2.88.1.3 Change History.........................................................................................................................1284 2.88.2 Overview of BTS Power Management..............................................................................................1284 2.88.3 Technical Description........................................................................................................................1284 2.88.4 Engineering Guidelines.....................................................................................................................1285 2.88.5 Parameters.........................................................................................................................................1286 2.88.6 Counters.............................................................................................................................................1289 2.88.7 Glossary.............................................................................................................................................1289 2.88.8 Reference Documents........................................................................................................................1289 2.89 Call Control................................................................................................................................................1289 2.89.1 Introduction.......................................................................................................................................1290 2.89.1.1 Scope........................................................................................................................................1290 2.89.1.2 Intended Audience....................................................................................................................1290 2.89.1.3 Change History.........................................................................................................................1290 2.89.2 Overview of Call Control..................................................................................................................1290 2.89.3 Technical Description........................................................................................................................1291 2.89.3.1 Call Classification.....................................................................................................................1291 2.89.3.2 Call Release..............................................................................................................................1293 2.89.4 Parameters.........................................................................................................................................1295 2.89.5 Counters.............................................................................................................................................1296 2.89.6 Glossary.............................................................................................................................................1296 2.89.7 Reference Documents........................................................................................................................1296 2.90 Call Reestablishment..................................................................................................................................1297 2.90.1 Introduction.......................................................................................................................................1297 2.90.1.1 Scope........................................................................................................................................1297 2.90.1.2 Intended Audience....................................................................................................................1297 2.90.1.3 Change History.........................................................................................................................1297 2.90.2 Overview of Call Reestablishment....................................................................................................1298 2.90.3 Technical Description........................................................................................................................1298 2.90.3.1 Call Reestablishment Procedure...............................................................................................1298 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xl
Contents
2.90.3.2 MS Mode..................................................................................................................................1300 2.90.4 Parameters.........................................................................................................................................1300 2.90.5 Counters.............................................................................................................................................1300 2.90.6 Glossary.............................................................................................................................................1301 2.90.7 Reference Documents........................................................................................................................1301 2.91 Cell Frequency Scan...................................................................................................................................1301 2.91.1 Introduction.......................................................................................................................................1301 2.91.1.1 Scope........................................................................................................................................1301 2.91.1.2 Intended Audience....................................................................................................................1301 2.91.1.3 Change History.........................................................................................................................1301 2.91.2 Overview of Cell Frequency Scan ....................................................................................................1302 2.91.3 Technical Description........................................................................................................................1302 2.91.4 Engineering Guidelines.....................................................................................................................1303 2.91.5 Parameters.........................................................................................................................................1303 2.91.6 Counters.............................................................................................................................................1304 2.91.7 Glossary.............................................................................................................................................1304 2.91.8 Reference Documents........................................................................................................................1304 2.92 Cell Tracing................................................................................................................................................1304 2.92.1 Introduction.......................................................................................................................................1304 2.92.1.1 Scope........................................................................................................................................1304 2.92.1.2 Intended Audience....................................................................................................................1305 2.92.1.3 Change History.........................................................................................................................1305 2.92.2 Overview of Cell Tracing..................................................................................................................1305 2.92.3 Technical Description........................................................................................................................1305 2.92.4 Engineering Guidelines.....................................................................................................................1306 2.92.5 Parameters.........................................................................................................................................1306 2.92.6 Counters.............................................................................................................................................1306 2.92.7 Glossary.............................................................................................................................................1306 2.92.8 Reference Documents........................................................................................................................1306 2.93 Man Machine Language (MML)................................................................................................................1306 2.93.1 Introduction.......................................................................................................................................1306 2.93.1.1 Scope........................................................................................................................................1307 2.93.1.2 Intended Audience....................................................................................................................1307 2.93.1.3 Change History.........................................................................................................................1307 2.93.2 Overview of Man Machine Language ..............................................................................................1307 2.93.3 Technical Description........................................................................................................................1307 2.93.4 Engineering Guidelines.....................................................................................................................1308 2.93.5 Parameters.........................................................................................................................................1308 2.93.6 Counters.............................................................................................................................................1308 2.93.7 Glossary.............................................................................................................................................1308 2.93.8 Reference Documents........................................................................................................................1309 2.94 Operation & Maintenance System One-Key Recovery..............................................................................1309 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xli
Contents
2.94.1 Introduction.......................................................................................................................................1309 2.94.1.1 Scope........................................................................................................................................1309 2.94.1.2 Intended Audience.................................................................................................................... 1309 2.94.1.3 Change History.........................................................................................................................1309 2.94.2 Overview of Operation & Maintenance System One-Key Recovery................................................1310 2.94.3 Technical Description........................................................................................................................1310 2.94.4 Parameters.........................................................................................................................................1312 2.94.5 Counters.............................................................................................................................................1312 2.94.6 Glossary.............................................................................................................................................1312 2.94.7 Reference Documents........................................................................................................................1312 2.95 Radio Bearer Services................................................................................................................................1312 2.95.1 Introduction.......................................................................................................................................1312 2.95.1.1 Scope........................................................................................................................................1312 2.95.1.2 Intended Audience.................................................................................................................... 1312 2.95.1.3 Change History.........................................................................................................................1312 2.95.2 Overview of Radio Bearer Services..................................................................................................1313 2.95.3 Technical Description........................................................................................................................1313 2.95.3.1 Telephone Service (TS11)........................................................................................................1313 2.95.3.2 Emergency Call Service (TS12)...............................................................................................1314 2.95.3.3 Point To Point Short Message Service (TS21, TS22)..............................................................1315 2.95.3.4 G3 Fax (TS61, TS62)...............................................................................................................1316 2.95.3.5 Bearer Service (CSD)...............................................................................................................1316 2.95.4 Parameters.........................................................................................................................................1317 2.95.5 Counters.............................................................................................................................................1319 2.95.6 Glossary.............................................................................................................................................1319 2.95.7 Reference Documents........................................................................................................................1319 2.96 Radio Link Management............................................................................................................................1319 2.96.1 Introduction.......................................................................................................................................1319 2.96.1.1 Scope........................................................................................................................................1319 2.96.1.2 Intended Audience.................................................................................................................... 1319 2.96.1.3 Change History.........................................................................................................................1319 2.96.2 Overview of Radio Link Management..............................................................................................1320 2.96.3 Technical Description........................................................................................................................1320 2.96.3.1 Link Establishment Indication..................................................................................................1320 2.96.3.2 Link Establishment Request.....................................................................................................1320 2.96.3.3 Link Release Indication............................................................................................................1321 2.96.3.4 Link Release Request...............................................................................................................1321 2.96.3.5 Transmission of a Transparent L3-Message in Acknowledged Mode.....................................1321 2.96.3.6 Reception of a Transparent L3-Message in Acknowledged Mode..........................................1322 2.96.3.7 Transmission of a Transparent L3-Message in Unacknowledged Mode.................................1322 2.96.3.8 Reception of a Transparent L3-Message in Unacknowledged Mode.......................................1322 2.96.3.9 Link Error Indication................................................................................................................1322 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlii
Contents
2.96.4 Engineering Guidelines.....................................................................................................................1323 2.96.5 Parameters.........................................................................................................................................1323 2.96.6 Counters.............................................................................................................................................1327 2.96.7 Glossary.............................................................................................................................................1327 2.96.8 Reference Documents........................................................................................................................1327 2.97 Remote EAC Maintenance.........................................................................................................................1327 2.97.1 Introduction.......................................................................................................................................1328 2.97.1.1 Scope........................................................................................................................................1328 2.97.1.2 Intended Audience....................................................................................................................1328 2.97.1.3 Change History.........................................................................................................................1328 2.97.2 Overview of Remote EAC Maintenance...........................................................................................1328 2.97.3 Technical Description........................................................................................................................1329 2.97.4 Parameters.........................................................................................................................................1330 2.97.5 Counters.............................................................................................................................................1332 2.97.6 Glossary.............................................................................................................................................1332 2.97.7 Reference Documents........................................................................................................................1332 2.98 Remote Upgrade of the BSC&BTS Software............................................................................................1332 2.98.1 Introduction.......................................................................................................................................1333 2.98.1.1 Scope........................................................................................................................................1333 2.98.1.2 Intended Audience....................................................................................................................1333 2.98.1.3 Change History.........................................................................................................................1333 2.98.2 Overview of Remote Upgrade of the BSC&BTS Software..............................................................1333 2.98.3 Technical Description........................................................................................................................1334 2.98.3.1 Typical Network Structure for Remote Software Upgrade......................................................1334 2.98.3.2 Remote Upgrade of BSC Software...........................................................................................1334 1. Procedure for Remote Upgrade of BSC Software..............................................................................1334 2. Characteristics and Specifications of Remote Upgrade of BSC Software.........................................1336 2.98.3.3 Remote Upgrade of BTS Software...........................................................................................1336 1. Procedure for Remote Upgrade of BTS Software..............................................................................1336 2. Characteristics and Specifications of Remote Upgrade of BTS Software.........................................1337 2.98.4 Parameters.........................................................................................................................................1337 2.98.5 Counters.............................................................................................................................................1338 2.98.6 Glossary.............................................................................................................................................1338 2.98.7 Reference Documents........................................................................................................................1338 2.99 Signaling Transport Point(STP).................................................................................................................1338 2.99.1 Introduction.......................................................................................................................................1338 2.99.1.1 Scope........................................................................................................................................1338 2.99.1.2 Intended Audience....................................................................................................................1338 2.99.1.3 Change History.........................................................................................................................1338 2.99.2 Overview of STP...............................................................................................................................1339 2.99.3 Technical Description........................................................................................................................1339 2.99.4 Parameters.........................................................................................................................................1340 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xliii
Contents
2.99.5 Counters.............................................................................................................................................1341 2.99.6 Glossary.............................................................................................................................................1341 2.99.7 Reference Documents........................................................................................................................1341 2.100 Support of Daylight Saving Time.............................................................................................................1341 2.100.1 Introduction.....................................................................................................................................1342 2.100.1.1 Scope......................................................................................................................................1342 2.100.1.2 Intended Audience..................................................................................................................1342 2.100.1.3 Change History.......................................................................................................................1342 2.100.2 Overview of Support of Daylight Saving Time ..............................................................................1342 2.100.3 Technical Description......................................................................................................................1342 2.100.4 Parameters.......................................................................................................................................1343 2.100.5 Counters...........................................................................................................................................1346 2.100.6 Glossary...........................................................................................................................................1346 2.100.7 Reference Documents......................................................................................................................1346 2.101 Supporting Three-Digit MNC..................................................................................................................1346 2.101.1 Introduction.....................................................................................................................................1346 2.101.1.1 Scope......................................................................................................................................1347 2.101.1.2 Intended Audience..................................................................................................................1347 2.101.1.3 Change History.......................................................................................................................1347 2.101.2 Overview of Supporting Three-Digit MNC....................................................................................1347 2.101.3 Technical Description......................................................................................................................1347 2.101.4 Parameters.......................................................................................................................................1348 2.101.5 Counters...........................................................................................................................................1348 2.101.6 Glossary...........................................................................................................................................1348 2.101.7 Reference Documents......................................................................................................................1348 2.102 TCH Re-assignment.................................................................................................................................1348 2.102.1 Introduction.....................................................................................................................................1348 2.102.1.1 Scope......................................................................................................................................1348 2.102.1.2 Intended Audience..................................................................................................................1348 2.102.1.3 Change History.......................................................................................................................1348 2.102.2 Overview of TCH Re-assignment...................................................................................................1349 2.102.3 Technical Description......................................................................................................................1349 2.102.4 Parameters.......................................................................................................................................1351 2.102.5 Counters...........................................................................................................................................1351 2.102.6 Glossary...........................................................................................................................................1351 2.102.7 Reference Documents......................................................................................................................1351 2.103 TRX Management....................................................................................................................................1352 2.103.1 Introduction.....................................................................................................................................1352 2.103.1.1 Scope......................................................................................................................................1352 2.103.1.2 Intended Audience..................................................................................................................1352 2.103.1.3 Change History.......................................................................................................................1352 2.103.2 Overview of TRX Management .....................................................................................................1353 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xliv
Contents
2.103.3 Technical Description......................................................................................................................1353 2.103.3.1 Radio Resource Indication......................................................................................................1353 2.103.3.2 SACCH Filling Information Modification.............................................................................1353 2.103.3.3 Flow Control...........................................................................................................................1354 2.103.3.4 Error Reporting.......................................................................................................................1354 2.103.4 Engineering Guidelines...................................................................................................................1355 2.103.5 Parameters.......................................................................................................................................1355 2.103.6 Counters...........................................................................................................................................1356 2.103.7 Glossary...........................................................................................................................................1356 2.103.8 Reference Documents......................................................................................................................1356 2.104 System Redundancy.................................................................................................................................1357 2.104.1 Introduction.....................................................................................................................................1357 2.104.1.1 Scope......................................................................................................................................1357 2.104.1.2 Intended Audience..................................................................................................................1357 2.104.1.3 Change History.......................................................................................................................1357 2.104.2 Overview.........................................................................................................................................1357 2.104.3 Technical Description......................................................................................................................1358 2.104.4 Engineering Guidelines...................................................................................................................1359 2.104.5 Parameters.......................................................................................................................................1359 2.104.6 Counters...........................................................................................................................................1359 2.104.7 Glossary...........................................................................................................................................1359 2.104.8 Reference Documents......................................................................................................................1359 2.105 Operate System Security Management.....................................................................................................1359 2.105.1 Introduction.....................................................................................................................................1359 2.105.1.1 Scope......................................................................................................................................1359 2.105.1.2 Change History.......................................................................................................................1359 2.105.2 Overview.........................................................................................................................................1360 2.105.3 Technical Description......................................................................................................................1360 2.105.3.1 Operate System Anti-Virus....................................................................................................1360 2.105.3.2 Operate System Security Enhancement..................................................................................1362 2.105.3.3 Operate System Patching .......................................................................................................1363 2.105.4 Engineering Guidelines...................................................................................................................1363 2.105.5 Parameters.......................................................................................................................................1364 2.105.6 Counters...........................................................................................................................................1364 2.105.7 Glossary...........................................................................................................................................1364 2.105.8 Reference Documents......................................................................................................................1364 2.106 BSC/RNC Resource Sharing....................................................................................................................1364 2.106.1 Introduction.....................................................................................................................................1364 2.106.1.1 Scope......................................................................................................................................1364 2.106.1.2 Intended Audience..................................................................................................................1364 2.106.1.3 Change History.......................................................................................................................1364 2.106.2 Overview.........................................................................................................................................1365 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlv
Contents
2.106.3 Technical Description......................................................................................................................1365 2.106.3.1 Control Plane Resource Sharing.............................................................................................1365 2.106.3.2 User Plane Resource Processing.............................................................................................1366 2.106.4 Parameters.......................................................................................................................................1368 2.106.5 Counters...........................................................................................................................................1372 2.106.6 Glossary...........................................................................................................................................1372 2.106.7 Reference Documents......................................................................................................................1372 2.107 Connection with TMA (Tower Mounted Amplifier)...............................................................................1372 2.107.1 Introduction.....................................................................................................................................1372 2.107.1.1 Scope......................................................................................................................................1372 2.107.1.2 Intended Audience..................................................................................................................1372 2.107.1.3 Change History.......................................................................................................................1372 2.107.2 Overview.........................................................................................................................................1373 2.107.3 Technical Description......................................................................................................................1374 2.107.3.1 RF Receiver Channel Attenuation..........................................................................................1374 2.107.3.2 Power Supply for TMA..........................................................................................................1374 2.107.3.3 Monitor TMA.........................................................................................................................1375 2.107.4 Engineering Guidelines...................................................................................................................1376 2.107.5 Parameters.......................................................................................................................................1376 2.107.6 Counters...........................................................................................................................................1376 2.107.7 Glossary...........................................................................................................................................1376 2.107.8 Reference Documents......................................................................................................................1376 2.108 Remote Electrical Tilt...............................................................................................................................1376 2.108.1 Introduction.....................................................................................................................................1376 2.108.1.1 Scope......................................................................................................................................1377 2.108.1.2 Intended Audience..................................................................................................................1377 2.108.1.3 Change History.......................................................................................................................1377 2.108.2 Overview.........................................................................................................................................1377 2.108.3 Technical Description......................................................................................................................1377 2.108.3.1 Operating Principles of RET..................................................................................................1378 2.108.3.2 Operating Principles of Huawei RET.....................................................................................1378 2.108.4 Parameters.......................................................................................................................................1383 2.108.5 Counters...........................................................................................................................................1383 2.108.6 Glossary...........................................................................................................................................1383 2.108.7 Reference Documents......................................................................................................................1383 2.109 TX Diversity and RX Diversity................................................................................................................1383 2.109.1 Introduction.....................................................................................................................................1383 2.109.1.1 Scope......................................................................................................................................1383 2.109.1.2 Intended Audience..................................................................................................................1384 2.109.1.3 Change History.......................................................................................................................1384 2.109.2 Overview of TX Diversity and RX Diversity..................................................................................1384 2.109.2.1 RX Diversity...........................................................................................................................1384 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlvi
Contents
2.109.2.2 TX Diversity...........................................................................................................................1385 2.109.3 Technical Description......................................................................................................................1385 2.109.3.1 RX Diversity...........................................................................................................................1385 2.109.3.2 TX Diversity...........................................................................................................................1386 2.109.4 Engineering Guidelines...................................................................................................................1389 2.109.4.1 RX Diversity...........................................................................................................................1389 2.109.4.2 TX Diversity...........................................................................................................................1389 2.109.5 Parameters.......................................................................................................................................1390 2.109.6 Counters...........................................................................................................................................1390 2.109.7 Glossary...........................................................................................................................................1390 2.109.8 Reference Documents......................................................................................................................1390 2.110 BTS/NodeB Clock....................................................................................................................................1390 2.110.1 Introduction.....................................................................................................................................1390 2.110.1.1 Scope......................................................................................................................................1390 2.110.1.2 Intended Audience..................................................................................................................1390 2.110.1.3 Change History.......................................................................................................................1391 2.110.2 Overview.........................................................................................................................................1391 2.110.3 Technical Description......................................................................................................................1392 2.110.3.1 Synchronization with the Abis/lub Clock...............................................................................1392 2.110.3.2 Synchronization with the GPS Clock.....................................................................................1392 2.110.3.3 Synchronization with the BITS Clock....................................................................................1392 2.110.4 Parameters.......................................................................................................................................1393 2.110.5 Counters...........................................................................................................................................1396 2.110.6 Glossary...........................................................................................................................................1396 2.110.7 Reference Documents......................................................................................................................1396 2.111 BSC/RNC Clock.......................................................................................................................................1397 2.111.1 Introduction.....................................................................................................................................1397 2.111.1.1 Scope......................................................................................................................................1397 2.111.1.2 Intended Audience..................................................................................................................1397 2.111.1.3 Change History.......................................................................................................................1397 2.111.2 Overview.........................................................................................................................................1397 2.111.3 Technical Description......................................................................................................................1398 2.111.3.1 Overview................................................................................................................................1398 2.111.3.2 BSC/RNC Synchronization System Structure........................................................................1399 2.111.3.3 RFN Generation Process........................................................................................................1400 2.111.4 Engineering Guidelines...................................................................................................................1401 2.111.4.1 Configuration of GPS Clock Source......................................................................................1401 2.111.4.2 Configuration of Gb Interface Clock......................................................................................1401 2.111.5 Parameters.......................................................................................................................................1402 2.111.6 Counters...........................................................................................................................................1404 2.111.7 Glossary...........................................................................................................................................1404 2.111.8 Reference Documents......................................................................................................................1404 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlvii
Contents
2.112 14.4 Kbps Circuit Switched Data.............................................................................................................1404 2.112.1 Introduction.....................................................................................................................................1404 2.112.1.1 Scope......................................................................................................................................1404 2.112.1.2 Intended Audience..................................................................................................................1404 2.112.1.3 Change History.......................................................................................................................1405 2.112.2 Overview.........................................................................................................................................1405 2.112.3 Technical Description......................................................................................................................1405 2.112.4 Parameters.......................................................................................................................................1405 2.112.5 Counters...........................................................................................................................................1406 2.112.6 Glossary...........................................................................................................................................1406 2.112.7 Reference Documents......................................................................................................................1406 2.113 Guaranteed Emergency Call.....................................................................................................................1407 2.113.1 Introduction.....................................................................................................................................1407 2.113.1.1 Scope......................................................................................................................................1407 2.113.1.2 Intended Audience..................................................................................................................1407 2.113.1.3 Change History.......................................................................................................................1407 2.113.2 Overview.........................................................................................................................................1407 2.113.3 Technical Description......................................................................................................................1408 2.113.3.1 Preferentially Assigning TCH/F in the Immediate Assignment Phase..................................1408 2.113.3.2 Resource Reservation and Preemption...................................................................................1409 2.113.4 Dependency.....................................................................................................................................1410 2.113.5 Parameters.......................................................................................................................................1410 2.113.6 Counters...........................................................................................................................................1411 2.113.7 Glossary...........................................................................................................................................1411 2.113.8 Reference Documents......................................................................................................................1411 2.114 BTS GPS Synchronization.......................................................................................................................1411 2.114.1 Introduction.....................................................................................................................................1411 2.114.1.1 Scope......................................................................................................................................1412 2.114.1.2 Intended Audience..................................................................................................................1412 2.114.1.3 Change History.......................................................................................................................1412 2.114.2 Overview.........................................................................................................................................1412 2.114.3 Technical Description......................................................................................................................1412 2.114.4 Engineering Guidelines...................................................................................................................1413 2.114.5 Parameters.......................................................................................................................................1413 2.114.6 Counters...........................................................................................................................................1418 2.114.7 Glossary...........................................................................................................................................1418 2.114.8 Reference Documents......................................................................................................................1418 2.115 BTS Test Function....................................................................................................................................1419 2.115.1 Introduction.....................................................................................................................................1419 2.115.1.1 Scope......................................................................................................................................1419 2.115.1.2 Intended Audience..................................................................................................................1419 2.115.1.3 Change History.......................................................................................................................1419 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlviii
Contents
2.115.2 Overview.........................................................................................................................................1420 2.115.3 Technical Description......................................................................................................................1420 2.115.3.1 Site Test..................................................................................................................................1420 2.115.3.2 Baseband Test.........................................................................................................................1420 2.115.3.3 Baseband Idle Timeslot Test..................................................................................................1420 2.115.3.4 TCH Loopback Test...............................................................................................................1420 2.115.3.5 Transmission Performance Test.............................................................................................1420 2.115.3.6 CRC........................................................................................................................................1421 2.115.3.7 BTS Antenna System Connection Detection..........................................................................1421 2.115.3.8 Call Test..................................................................................................................................1421 2.115.3.9 BTS Antenna System Connection Detection..........................................................................1421 2.115.4 Engineering Guidelines...................................................................................................................1421 2.115.5 Parameters.......................................................................................................................................1422 2.115.6 Counters...........................................................................................................................................1425 2.115.7 Glossary...........................................................................................................................................1425 2.115.8 Reference Documents......................................................................................................................1425 2.116 Connection Inter BSC over IP..................................................................................................................1425 2.116.1 Introduction.....................................................................................................................................1425 2.116.1.1 Scope......................................................................................................................................1425 2.116.1.2 Intended Audience..................................................................................................................1425 2.116.1.3 Change History.......................................................................................................................1426 2.116.2 Overview.........................................................................................................................................1426 2.116.3 Technical Description......................................................................................................................1427 2.116.4 Parameters.......................................................................................................................................1428 2.116.5 Counters...........................................................................................................................................1428 2.116.6 Glossary...........................................................................................................................................1428 2.116.7 Reference Documents......................................................................................................................1428 2.117 Encrypted Network Management.............................................................................................................1429 2.117.1 Introduction.....................................................................................................................................1429 2.117.1.1 Scope......................................................................................................................................1429 2.117.1.2 Intended Audience..................................................................................................................1429 2.117.1.3 Change History.......................................................................................................................1429 2.117.2 Overview.........................................................................................................................................1429 2.117.3 Technical Description......................................................................................................................1430 2.117.3.1 Overview................................................................................................................................1430 2.117.3.2 Setting the Connection Policy Between the M2000 ..............................................................1433 2.117.3.3 Setting the SSL Authentication Policy...................................................................................1433 2.117.3.4 Managing the Digital Certificate............................................................................................1434 2.117.3.5 Setting SSL Encryption for FTP.............................................................................................1437 2.117.3.6 Specifications..........................................................................................................................1437 2.117.4 Parameters.......................................................................................................................................1438 2.117.5 Counters...........................................................................................................................................1438 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlix
Contents
2.117.6 Glossary...........................................................................................................................................1438 2.117.7 Reference Documents......................................................................................................................1438 2.118 End-to-End MS Signaling Tracing...........................................................................................................1439 2.118.1 Introduction.....................................................................................................................................1439 2.118.1.1 Scope......................................................................................................................................1439 2.118.1.2 Intended Audience..................................................................................................................1439 2.118.1.3 Change History.......................................................................................................................1439 2.118.2 Overview.........................................................................................................................................1440 2.118.3 Technical Description......................................................................................................................1440 2.118.3.1 Overview................................................................................................................................1440 2.118.3.2 Procedure for End-to-End MS Signaling Tracing on an MOC in a BSC...............................1441 2.118.3.3 Procedure for End-to-End MS Signaling Tracing on an Incoming-BSC Handover Call.......1441 2.118.4 Parameters.......................................................................................................................................1441 2.118.5 Counters...........................................................................................................................................1442 2.118.6 Glossary...........................................................................................................................................1442 2.118.7 Reference Documents......................................................................................................................1442 2.119 Flex Ater...................................................................................................................................................1442 2.119.1 Introduction.....................................................................................................................................1442 2.119.1.1 Scope......................................................................................................................................1442 2.119.1.2 Intended Audience..................................................................................................................1442 2.119.1.3 Change History.......................................................................................................................1443 2.119.2 Overview.........................................................................................................................................1443 2.119.3 Technical Description......................................................................................................................1443 2.119.4 Parameters.......................................................................................................................................1444 2.119.5 Counters...........................................................................................................................................1445 2.119.6 Glossary...........................................................................................................................................1445 2.119.7 Reference Documents......................................................................................................................1445 2.120 TrFO.........................................................................................................................................................1445 2.120.1 Introduction.....................................................................................................................................1445 2.120.1.1 Scope......................................................................................................................................1445 2.120.1.2 Intended Audience..................................................................................................................1445 2.120.1.3 Change History.......................................................................................................................1446 2.120.2 Overview.........................................................................................................................................1446 2.120.3 Technical Description......................................................................................................................1446 2.120.4 Parameters.......................................................................................................................................1447 2.120.5 Counters...........................................................................................................................................1447 2.120.6 Glossary...........................................................................................................................................1447 2.120.7 Reference Documents......................................................................................................................1447 2.121 Forced System Information Sending by OMC.........................................................................................1447 2.121.1 Introduction.....................................................................................................................................1448 2.121.1.1 Scope......................................................................................................................................1448 2.121.1.2 Intended Audience..................................................................................................................1448 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. l
Contents
2.121.1.3 Change History.......................................................................................................................1448 2.121.2 Overview.........................................................................................................................................1448 2.121.3 Technical Description......................................................................................................................1449 2.121.4 Parameters.......................................................................................................................................1449 2.121.5 Counters...........................................................................................................................................1449 2.121.6 Glossary...........................................................................................................................................1450 2.121.7 Reference Documents......................................................................................................................1450 2.122 Performance Management........................................................................................................................1450 2.122.1 Introduction.....................................................................................................................................1450 2.122.1.1 Scope......................................................................................................................................1450 2.122.1.2 Intended Audience..................................................................................................................1450 2.122.1.3 Change History.......................................................................................................................1450 2.122.2 Overview.........................................................................................................................................1451 2.122.3 Technical Description......................................................................................................................1451 2.122.3.1 Overview................................................................................................................................1451 1. Performance Measurement Procedure................................................................................................1452 2. Performance Measurement Management...........................................................................................1454 3. Real-Time Performance Monitoring..................................................................................................1456 2.122.4 Parameters.......................................................................................................................................1457 2.122.5 Counters...........................................................................................................................................1457 2.122.6 Glossary...........................................................................................................................................1457 2.122.7 Reference Documents......................................................................................................................1457 2.123 O&M of BTS............................................................................................................................................1457 2.123.1 Introduction.....................................................................................................................................1457 2.123.1.1 Scope......................................................................................................................................1457 2.123.1.2 Intended Audience..................................................................................................................1457 2.123.1.3 Change History.......................................................................................................................1457 2.123.2 Overview.........................................................................................................................................1458 2.123.3 Technical Description......................................................................................................................1459 2.123.4 Parameters.......................................................................................................................................1460 2.123.5 Counters...........................................................................................................................................1461 2.123.6 Glossary...........................................................................................................................................1461 2.123.7 Reference Documents......................................................................................................................1461 2.124 O&M of BSC............................................................................................................................................1461 2.124.1 Introduction.....................................................................................................................................1461 2.124.1.1 Scope......................................................................................................................................1461 2.124.1.2 Intended Audience..................................................................................................................1461 2.124.1.3 Change History.......................................................................................................................1461 2.124.2 Overview.........................................................................................................................................1462 2.124.3 Technical Description......................................................................................................................1462 2.124.3.1 Basic Architecture..................................................................................................................1462 2.124.3.2 Basic Functions.......................................................................................................................1463 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. li
Contents
1. Configuration Management................................................................................................................1463 2. Performance Management..................................................................................................................1463 3. Alarm Management............................................................................................................................1463 4. Security Management.........................................................................................................................1464 5. O&M of Board....................................................................................................................................1466 6. Tracing and Monitoring......................................................................................................................1466 7. Query of Call Resources.....................................................................................................................1466 8. Maintenance of Interface and Link.....................................................................................................1466 9. Time Synchronization.........................................................................................................................1466 2.124.4 Parameters.......................................................................................................................................1466 2.124.5 Counters...........................................................................................................................................1466 2.124.6 Glossary...........................................................................................................................................1466 2.124.7 Reference Documents......................................................................................................................1467 2.125 Integrated Network Management Interface..............................................................................................1467 2.125.1 Introduction.....................................................................................................................................1467 2.125.1.1 Scope......................................................................................................................................1467 2.125.1.2 Intended Audience..................................................................................................................1467 2.125.1.3 Change History.......................................................................................................................1467 2.125.2 Overview.........................................................................................................................................1468 2.125.3 Technical Description......................................................................................................................1468 2.125.3.1 Integrated Network Management Functions..........................................................................1468 2.125.3.2 Northbound Interface..............................................................................................................1469 2.125.3.3 Network Structure...................................................................................................................1469 2.125.4 Parameters.......................................................................................................................................1470 2.125.5 Counters...........................................................................................................................................1470 2.125.6 Glossary...........................................................................................................................................1470 2.125.7 Reference Documents......................................................................................................................1470 2.126 Reporting the Temperature List of the BTS Equipment Room................................................................1470 2.126.1 Introduction.....................................................................................................................................1471 2.126.1.1 Scope......................................................................................................................................1471 2.126.1.2 Intended Audience..................................................................................................................1471 2.126.1.3 Change History.......................................................................................................................1471 2.126.2 Overview.........................................................................................................................................1471 2.126.3 Technical Description......................................................................................................................1472 2.126.4 Engineering Guidelines...................................................................................................................1472 2.126.5 Parameters.......................................................................................................................................1472 2.126.6 Counters...........................................................................................................................................1474 2.126.7 Glossary...........................................................................................................................................1474 2.126.8 Reference Documents......................................................................................................................1474 2.127 Inventory Management.............................................................................................................................1474 2.127.1 Introduction.....................................................................................................................................1474 2.127.1.1 Scope......................................................................................................................................1474 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lii
Contents
2.127.1.2 Intended Audience..................................................................................................................1474 2.127.1.3 Change History.......................................................................................................................1475 2.127.2 Overview.........................................................................................................................................1475 2.127.3 Technical Description......................................................................................................................1475 2.127.3.1 Principles of the Inventory Management System...................................................................1476 2.127.3.2 Electronic Label......................................................................................................................1477 2.127.4 Engineering Guidelines...................................................................................................................1478 2.127.4.1 Providing Comprehensive Inventory Information..................................................................1478 2.127.4.2 Managing Inventory Information...........................................................................................1479 2.127.4.3 Synchronizing Inventory Data................................................................................................1481 2.127.4.4 Management of the Manually Entered Inventory Data..........................................................1483 1. Adding Inventory Data.......................................................................................................................1483 2. Deleting Inventory Data.....................................................................................................................1484 3. Importing Inventory Data...................................................................................................................1484 2.127.4.5 Modifying Inventory Data......................................................................................................1485 2.127.4.6 Searching For Inventory Data.................................................................................................1486 2.127.4.7 Exporting Inventory Data.......................................................................................................1486 2.127.4.8 Flexible Inventory Northbound Interface...............................................................................1487 2.127.5 Parameters.......................................................................................................................................1487 2.127.6 Counters...........................................................................................................................................1487 2.127.7 Glossary...........................................................................................................................................1487 2.127.8 Reference Documents......................................................................................................................1487 2.128 Maintenance Mode Alarm........................................................................................................................1487 2.128.1 Introduction.....................................................................................................................................1488 2.128.1.1 Scope......................................................................................................................................1488 2.128.1.2 Intended Audience..................................................................................................................1488 2.128.1.3 Change History.......................................................................................................................1488 2.128.2 Overview.........................................................................................................................................1488 2.128.3 Technical Description......................................................................................................................1489 2.128.3.1 Overview................................................................................................................................1489 2.128.3.2 Setting the Maintenance Mode...............................................................................................1489 2.128.3.3 Querying the Maintenance Mode...........................................................................................1493 2.128.3.4 Monitoring Maintenance Mode Alarms.................................................................................1494 2.128.3.5 Enabling the M2000 to Report Maintenance Mode Alarms to the NMS...............................1495 2.128.4 Networking......................................................................................................................................1496 2.128.5 Parameters.......................................................................................................................................1497 2.128.6 Counters...........................................................................................................................................1498 2.128.7 Glossary...........................................................................................................................................1498 2.128.8 Reference Documents......................................................................................................................1498 2.129 Multi-Cell Function..................................................................................................................................1498 2.129.1 Introduction.....................................................................................................................................1498 2.129.1.1 Scope......................................................................................................................................1498 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. liii
Contents
2.129.1.2 Intended Audience..................................................................................................................1498 2.129.1.3 Change History.......................................................................................................................1498 2.129.2 Overview.........................................................................................................................................1499 2.129.3 Technical Description......................................................................................................................1499 2.129.4 Engineering Guidelines...................................................................................................................1499 2.129.5 Parameters.......................................................................................................................................1500 2.129.6 Counters...........................................................................................................................................1500 2.129.7 Glossary...........................................................................................................................................1500 2.129.8 Reference Documents......................................................................................................................1500 2.130 Satellite Transmission...............................................................................................................................1500 2.130.1 Introduction.....................................................................................................................................1500 2.130.1.1 Scope......................................................................................................................................1500 2.130.1.2 Intended Audience..................................................................................................................1500 2.130.1.3 Change History.......................................................................................................................1500 2.130.2 Overview.........................................................................................................................................1501 2.130.3 Technical Description......................................................................................................................1501 2.130.3.1 Network Topologies of Satellite Transmission......................................................................1501 2.130.3.2 Satellite Transmission over the Abis Interface.......................................................................1502 2.130.3.3 Satellite transmission over the A interface.............................................................................1503 2.130.3.4 Satellite transmission over the Ater interface.........................................................................1503 2.130.3.5 Satellite transmission over the Pb interface............................................................................1503 2.130.4 Parameters.......................................................................................................................................1503 2.130.5 Counters...........................................................................................................................................1508 2.130.6 Glossary...........................................................................................................................................1509 2.130.7 Reference Documents......................................................................................................................1509 2.131 NAT Beside OM.......................................................................................................................................1509 2.131.1 Introduction.....................................................................................................................................1509 2.131.1.1 Scope......................................................................................................................................1509 2.131.1.2 Intended Audience..................................................................................................................1509 2.131.1.3 Change History.......................................................................................................................1509 2.131.2 Overview.........................................................................................................................................1510 2.131.3 Technical Description......................................................................................................................1511 2.131.4 Parameters.......................................................................................................................................1511 2.131.5 Counters...........................................................................................................................................1511 2.131.6 Glossary...........................................................................................................................................1511 2.131.7 Reference Documents......................................................................................................................1511 2.132 Radio Common Channel Management.....................................................................................................1511 2.132.1 Introduction.....................................................................................................................................1512 2.132.1.1 Scope......................................................................................................................................1512 2.132.1.2 Intended Audience..................................................................................................................1512 2.132.1.3 Change History.......................................................................................................................1512 2.132.2 Overview.........................................................................................................................................1513 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. liv
Contents
2.132.3 Technical Description......................................................................................................................1513 2.132.3.1 Channel Request by MS.........................................................................................................1513 2.132.3.2 Paging.....................................................................................................................................1514 2.132.3.3 Delete Indication.....................................................................................................................1514 2.132.3.4 CCCH Load Indication...........................................................................................................1515 2.132.3.5 Broadcast Information Modify...............................................................................................1515 2.132.3.6 Short Message Cell Broadcast................................................................................................1515 2.132.3.7 Immediate Assignment...........................................................................................................1515 2.132.3.8 Notification.............................................................................................................................1516 2.132.4 Parameters.......................................................................................................................................1516 2.132.5 Counters...........................................................................................................................................1520 2.132.6 Glossary...........................................................................................................................................1520 2.132.7 Reference Documents......................................................................................................................1521 2.133 Radio Dedicated Channel Management...................................................................................................1521 2.133.1 Introduction.....................................................................................................................................1521 2.133.1.1 Scope......................................................................................................................................1521 2.133.1.2 Intended Audience..................................................................................................................1521 2.133.1.3 Change History.......................................................................................................................1521 2.133.2 Overview.........................................................................................................................................1522 2.133.3 Technical Description......................................................................................................................1522 2.133.3.1 Overview................................................................................................................................1522 2.133.3.2 Channel Activation.................................................................................................................1523 2.133.3.3 Channel Mode Modify............................................................................................................1526 2.133.3.4 Handover Detection................................................................................................................1526 2.133.3.5 Start of Encryption..................................................................................................................1527 2.133.3.6 Measurement Reporting.........................................................................................................1527 2.133.3.7 SACCH Deactivation.............................................................................................................1529 2.133.3.8 Radio Channel Release...........................................................................................................1529 2.133.3.9 MS Power Control..................................................................................................................1530 2.133.3.10 Transmission Power Control................................................................................................1530 2.133.3.11 Connection Failure...............................................................................................................1530 2.133.3.12 SACCH Information Modify................................................................................................1530 2.133.3.13 Talker Detection...................................................................................................................1530 2.133.3.14 Listener Detection.................................................................................................................1531 2.133.4 Engineering Guidelines...................................................................................................................1531 2.133.4.1 Measurement reporting...........................................................................................................1531 2.133.4.2 Channel Mode Modify............................................................................................................1531 2.133.5 Parameters.......................................................................................................................................1531 2.133.6 Counters...........................................................................................................................................1532 2.133.7 Glossary...........................................................................................................................................1532 2.133.8 Reference Documents......................................................................................................................1532 2.134 Security Management...............................................................................................................................1532 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lv
Contents
2.134.1 Introduction.....................................................................................................................................1533 2.134.1.1 Scope......................................................................................................................................1533 2.134.1.2 Intended Audience..................................................................................................................1533 2.134.1.3 Change History.......................................................................................................................1533 2.134.2 Overview.........................................................................................................................................1533 2.134.3 Technical Description......................................................................................................................1534 2.134.3.1 Overview................................................................................................................................1534 2.134.3.2 OMU Operating System Security...........................................................................................1537 1. Anti-Virus Software...........................................................................................................................1537 2. Operating System Enhancement.........................................................................................................1539 2.134.3.3 Data Redundancy Backup......................................................................................................1540 2.134.3.4 User Authentication Failure Timeout Alarm..........................................................................1541 2.134.4 Parameters.......................................................................................................................................1542 2.134.5 Counters...........................................................................................................................................1542 2.134.6 Glossary...........................................................................................................................................1542 2.134.7 Reference Documents......................................................................................................................1542 2.135 OML Backup ...........................................................................................................................................1542 2.135.1 Introduction.....................................................................................................................................1542 2.135.1.1 Scope......................................................................................................................................1543 2.135.1.2 Intended Audience..................................................................................................................1543 2.135.1.3 Change History.......................................................................................................................1543 2.135.2 Overview.........................................................................................................................................1543 2.135.3 Technical Description......................................................................................................................1544 2.135.3.1 OML Backup..........................................................................................................................1544 2.135.4 Parameters.......................................................................................................................................1544 2.135.5 Counters...........................................................................................................................................1545 2.135.6 Glossary...........................................................................................................................................1545 2.135.7 Reference Documents......................................................................................................................1546 2.136 2G/3G Neighboring Cell Automatic Optimization..................................................................................1546 2.136.1 Introduction.....................................................................................................................................1546 2.136.1.1 Scope......................................................................................................................................1546 2.136.1.2 Intended Audience..................................................................................................................1546 2.136.1.3 Change History.......................................................................................................................1546 2.136.2 Overview.........................................................................................................................................1547 2.136.3 Technical Description......................................................................................................................1547 2.136.3.1 Network Topology..................................................................................................................1547 2.136.3.2 Task Creation..........................................................................................................................1548 2.136.3.3 Neighboring Cell Analyzing Algorithm.................................................................................1548 2.136.4 Parameters.......................................................................................................................................1549 2.136.5 Counters...........................................................................................................................................1550 2.136.6 Glossary...........................................................................................................................................1550 2.136.7 Reference Documents......................................................................................................................1551 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lvi
Contents
2.137 Intelligent Shutdown of TRX Due to PSU Failure...................................................................................1551 2.137.1 Introduction.....................................................................................................................................1551 2.137.1.1 Scope......................................................................................................................................1551 2.137.1.2 Intended Audience.................................................................................................................. 1551 2.137.1.3 Change History.......................................................................................................................1551 2.137.2 Overview.........................................................................................................................................1552 2.137.3 Technical Description......................................................................................................................1552 2.137.4 Parameters.......................................................................................................................................1553 2.137.5 Counters...........................................................................................................................................1554 2.137.6 Glossary...........................................................................................................................................1554 2.137.7 Reference Documents......................................................................................................................1554 2.138 License Control for Urgency....................................................................................................................1554 2.138.1 Introduction.....................................................................................................................................1555 2.138.1.1 Scope......................................................................................................................................1555 2.138.1.2 Intended Audience.................................................................................................................. 1555 2.138.1.3 Change History.......................................................................................................................1555 2.138.2 Overview.........................................................................................................................................1555 2.138.3 Technical Description......................................................................................................................1556 2.138.4 Engineering Guidelines...................................................................................................................1556 2.138.5 Parameters.......................................................................................................................................1556 2.138.6 Counters...........................................................................................................................................1557 2.138.7 Glossary...........................................................................................................................................1557 2.138.8 Reference Documents......................................................................................................................1557 2.139 Faulty Management..................................................................................................................................1557 2.139.1 Introduction.....................................................................................................................................1557 2.139.1.1 Scope......................................................................................................................................1557 2.139.1.2 Intended Audience.................................................................................................................. 1558 2.139.1.3 Change History.......................................................................................................................1558 2.139.2 Overview.........................................................................................................................................1558 2.139.3 Technical Description......................................................................................................................1561 2.139.3.1 Fault Handling........................................................................................................................1562 2.139.3.2 Alarm Severity........................................................................................................................1563 2.139.3.3 Alarm Handling......................................................................................................................1564 2.139.4 Parameters.......................................................................................................................................1565 2.139.5 Counters...........................................................................................................................................1565 2.139.6 Glossary...........................................................................................................................................1565 2.139.7 Reference Documents......................................................................................................................1565 2.140 Configuration Management...................................................................................................................... 1565 2.140.1 Introduction.....................................................................................................................................1565 2.140.1.1 Scope......................................................................................................................................1565 2.140.1.2 Intended Audience.................................................................................................................. 1566 2.140.1.3 Change History.......................................................................................................................1566 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lvii
Contents
2.140.2 Overview.........................................................................................................................................1566 2.140.3 Technical Description......................................................................................................................1567 2.140.3.1 Basic Architecture..................................................................................................................1567 2.140.3.2 Basic Flow..............................................................................................................................1568 2.140.3.3 Functional Features.................................................................................................................1569 2.140.4 Parameters.......................................................................................................................................1570 2.140.5 Counters...........................................................................................................................................1570 2.140.6 Glossary...........................................................................................................................................1570 2.140.7 Reference Documents......................................................................................................................1571 2.141 DBS Topology Maintenance....................................................................................................................1571 2.141.1 Introduction.....................................................................................................................................1571 2.141.1.1 Scope......................................................................................................................................1571 2.141.1.2 Intended Audience..................................................................................................................1571 2.141.1.3 Change History.......................................................................................................................1571 2.141.2 Overview.........................................................................................................................................1572 2.141.3 Technical Description......................................................................................................................1572 2.141.4 Parameters.......................................................................................................................................1573 2.141.5 Counters...........................................................................................................................................1573 2.141.6 Glossary...........................................................................................................................................1573 2.141.7 Reference Documents......................................................................................................................1573 2.142 BTS/NodeB Software Management.........................................................................................................1573 2.142.1 Introduction.....................................................................................................................................1573 2.142.1.1 Scope......................................................................................................................................1573 2.142.1.2 Intended Audience..................................................................................................................1573 2.142.1.3 Change History.......................................................................................................................1573 2.142.2 Overview.........................................................................................................................................1574 2.142.3 Technical Description......................................................................................................................1574 2.142.4 Parameters.......................................................................................................................................1575 2.142.5 Counters...........................................................................................................................................1575 2.142.6 Glossary...........................................................................................................................................1575 2.142.7 Reference Documents......................................................................................................................1575 2.143 BTS/NodeB Software USB Download.....................................................................................................1576 2.143.1 Introduction.....................................................................................................................................1576 2.143.1.1 Scope......................................................................................................................................1576 2.143.1.2 Intended Audience..................................................................................................................1576 2.143.1.3 Change History.......................................................................................................................1576 2.143.2 Overview.........................................................................................................................................1576 2.143.3 Technical Description......................................................................................................................1577 2.143.4 Parameters.......................................................................................................................................1577 2.143.5 Counters...........................................................................................................................................1577 2.143.6 Glossary...........................................................................................................................................1577 2.143.7 Reference Documents......................................................................................................................1577 Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lviii
Contents
2.144 BSC/RNC Software Management............................................................................................................1577 2.144.1 Introduction.....................................................................................................................................1578 2.144.1.1 Scope......................................................................................................................................1578 2.144.1.2 Intended Audience..................................................................................................................1578 2.144.1.3 Change History.......................................................................................................................1578 2.144.2 Overview.........................................................................................................................................1578 2.144.3 Technical Description......................................................................................................................1579 2.144.3.1 File Loading Initiated by Boards............................................................................................1579 1. TCS Locally Configured in BM/TC Separated Mode in BSC6900 GSM and BSC6900 GU Systems ................................................................................................................................................................1579 2. TCS Remotely Configured in BM/TC Separated Mode in BSC6900 GSM and BSC6900 GU Systems ................................................................................................................................................................1580 3. BM/TC Combined Mode or A over IP Mode in BSC6900 GSM and BSC6900 GU Systems..........1582 4. BSC6900 UMTS System....................................................................................................................1583 2.144.3.2 Online File Loading................................................................................................................1584 2.144.4 Parameters.......................................................................................................................................1584 2.144.5 Counters...........................................................................................................................................1584 2.144.6 Glossary...........................................................................................................................................1584 2.144.7 Reference Documents......................................................................................................................1584 2.145 License Management................................................................................................................................1585 2.145.1 Introduction.....................................................................................................................................1585 2.145.1.1 Scope......................................................................................................................................1585 2.145.1.2 Intended Audience..................................................................................................................1585 2.145.1.3 Change History.......................................................................................................................1585 2.145.2 Overview.........................................................................................................................................1585 2.145.3 Technical Description......................................................................................................................1586 2.145.4 Parameters.......................................................................................................................................1587 2.145.5 Counters...........................................................................................................................................1587 2.145.6 Glossary...........................................................................................................................................1587 2.145.7 Reference Documents......................................................................................................................1587 2.146 Network Structure.....................................................................................................................................1587 2.146.1 Introduction.....................................................................................................................................1587 2.146.1.1 Scope......................................................................................................................................1588 2.146.1.2 Intended Audience..................................................................................................................1588 2.146.1.3 Change History.......................................................................................................................1588 2.146.2 Overview.........................................................................................................................................1588 2.146.3 Technical Description......................................................................................................................1589 2.146.4 Parameters.......................................................................................................................................1590 2.146.5 Counters...........................................................................................................................................1590 2.146.6 Glossary...........................................................................................................................................1590 2.146.7 Reference Documents......................................................................................................................1590
3 Operation and Maintenance..................................................................................................1591

Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lix
1 Library Information
1
About This Chapter
1.1 Library Overview 1.2 Library Changes 1.3 Glossary
Library Information
Issue 08 (2011-09-30)
1.1 Library Overview

This describes the contents and target groups of all the documents in the library.
Library Structure
Table 1-1 lists all the documents in the library. Table 1-1 Introduction to library structure Document 14.4kbit/s Circuit Description Huawei GBSS supports the transfer of data services on individual speech channels. It supports the transparent transfer of CS-based data services with a rate of 14.4 kbit/s and the non-transparent transfer of CS-based data services with a rate of 14.5 kbit/s. Operators are advised to use the 14.4 kbit/s CS-based data services to meet the requirements of high-speed data services. Huawei GBSS supports both 14-digit signaling point code and 24-digit signaling point code. This conforms to the requirements of different signaling systems, thus facilitating the use of networking in different countries and regions. Two antennas (or two polarization ends of the same polarization antenna) are used to receive signals. The signals received by the two antennas can be combined in different ways to obtain desired signals. With the 2G/3G Co-Transmission by TDM Switching feature, Huawei SingleRAN equipment uses the TDM timeslot cross connection function to enable the SDH to be shared by the GSM traffic and UMTS traffic. For the areas covered by both the GSM network and the UMTS network, 2G/3G interoperability enables traffic to be balanced between GSM and UMTS. In addition, 2G/3G interoperability enables a smooth evolution from GSM to UMTS.
14-Digit Signaling Point Code
2-Antenna Receive Diversity
2G/3G Co-Transmission by TDM Switching
2G/3G Interoperability
Issue 08 (2011-09-30)
Document 2G/3G Interoperability (TDD)
Description For the areas covered by both the GSM network and the UMTS network, 2G/3G interoperability enables traffic to be balanced between GSM and UMTS. In addition, 2G/3G interoperability enables a smooth evolution from GSM to UMTS. This feature enables operators to correctly configure neighboring 2G/3G cells of the GSM serving cell by using the Nastar, a network optimization tool. In this manner, the intraRAT and inter-RAT handover success rates are increased, and the GSM network performance is improved. A Interface Circuit Management improves the network quality by ensuring a high success rate of call establishments and handovers, and providing value-added services for telecom operators in terms of operation, maintenance, and transmission quality. This feature is aimed at ensuring the network quality. With this feature, operators can learn the usage of the circuit resources and TC codes of the A interface in time. A Interface Protocol Process, a basic signaling function stipulated in 3GPP specifications, is supported by Huawei GSM BSS. Abis Bypass is introduced in the network with the chain topology to avoid the problem of service disruption on other BTSs upon the power failure of one BTS. With the Abis Bypass feature, a bypass transmission link is formed within the BTS that is powered off to transfer data to other BTSs following the faulty BTS on the chain. Thus, the power failure of a BTS will not affect the normal services on the subsequent BTSs on the chain. The Acoustic Echo Cancellation (AEC) feature of the BSC is implemented by analyzing the uplink and downlink digital voice signals, searching the acoustic echoes in the uplink voice, and suppressing the acoustic echoes.
2G/3G Neighboring Cell Automatic Optimization
A Interface Circuit Management
A Interface Occupation Rate Monitoring
A Interface Protocol Process
Abis Bypass
Acoustic Echo Cancellation
Issue 08 (2011-09-30)
Document Adjustment of Adaptive Timing Advance
Description This feature is the basis for services between the MS and the BTS such as synchronization and calls. The synchronization of the network can be achieved only after this feature is enabled. Without this feature, all services cannot be properly processed. To solve this problem, Huawei base stations adopt the auto frequency correction (AFC) feature to compensate the Doppler frequency shift, thus ensuring successful high-speed access of the MSs and meeting the requirements of high-speed mobile communication services. AMR enables the BTS and the MS to automatically select an appropriate coding/ decoding rate from the specified ACS according to the interference level in the radio environment. This enhances the antiinterference capability and the speech quality of the wireless communications system. Antenna frequency hopping can provide transmit diversity. With the introduction of antenna frequency hopping, the probability that all bursts within a speech frame are lost is reduced if the bursts are transmitted on different paths. In this manner, the speech quality is ensured. Active queue management (AQM) is an algorithm used to maintain the buffer queue length within an appropriate range by discarding data packets in the buffer queue actively. It increases data throughput and reduces service delay at the price of buffer utilization. AQM applies to scenarios in which bandwidth is limited and congestion may occur. The immediate assignment and assignment procedures are very important for call establishment. Through the immediate assignment procedure, a radio resource (RR) connection is established between the MS and the network. Through the assignment procedure, the MSC assigns a specific TCH to the MS so that a stable connection is established between the MS and the network.
AFC
AMR
Antenna Frequency Hopping
AQM
Assignment and Immediate Assignment
Issue 08 (2011-09-30)
Document Ater Compression Transmission
Description Ater Compression Transmission is a technology in which the TDM transmission network is used on the Ater interface and the IP over PPP over Ch-STM-1 transmission mode is adopted to carry signals. Ater Compression Transmission helps to save transmission bandwidth. The TC (TRAU) of Huawei BSC supports 4:1 multiplexing on the Ater interface. That is, the four timeslots on the E1 of the A interface can be multiplexed onto a timeslot on the Ater interface by means of the TC. In this process, the previous 64 kbit/s PCM frame can be converted into the 16 kbit/s TRAU frame to save the transmission bandwidth. Authentication is a procedure in which the GSM network verifies the validity of the identity of an MS, that is, verifies the validity of the IMSI or TMSI of the MS transmitted over the Um interface. The purpose of authentication is to prevent unauthorized subscribers from accessing the network and to protect the private information of authorized subscribers. ALC adjusts the gain of uplink and downlink digital voice signals every 20 ms and changes the amplitude of digital voice signals in static or dynamic mode. This keeps the voice level of the entire network in a predefined state, prevents the volume fluctuation of the two parties during a call, and reduces interference among the normal calls. Automatic noise compensation (ANC) can adaptively adjust the volume of the voice from the other end when the background noise is loud at the local end. This improves the voice quality, prolongs the average call duration, and increases the operators revenue. Automatic Noise Restraint (ANR) reduces the background noise in the uplink speech signals and improves the SNR and speech intelligibility. Thus, the speech signals are received clearly at the peer end.
Ater Interface 4:1 Multiplexing
Authentication
Automatic Level Control
Automatic Noise Compensation
Automatic Noise Restraint
Issue 08 (2011-09-30)
Document BCCH Dense Frequency Multiplexing
Description The BCCH dense frequency multiplexing technology is applicable to the network with limited frequency resources. With BCCH dense frequency multiplexing, more frequencies are used at the FH layer to increase the frequency efficiency. In daily operations, the active board takes charge of the normal operation of the services and the standby one performs real-time backup for the active board. When the active board is faulty, the services are switched to the standby board automatically. The board switchover feature improves the reliability of the GBSS system, prolongs the MTBF, and prevents service disruption caused by a faulty board. With the BSC Cabinet/Subrack Sharing feature, various devices share the cabinet or subrack. With BSC node redundancy, two BSCs form a redundancy group and work in 1+1 load sharing mode. Each BSC in the redundancy group backs up the configuration data of the primary service objects of the other BSC. BSC node redundancy helps to improve the device and network reliability. This document describes the types, synchronous system structure, and RFN generation process of the BSC/RNC clock. This document describes the BSC/RNC resource sharing, including resource sharing of the control plane and of the user plane. This document describes functions provided by the software management. When BSS local switching is enabled, the speech signals are looped back on the BSS side. Thus, the transmission resources on the Abis and Ater interfaces are saved and the speech quality is improved.
Board Switchover
BSC Cabinet/Subrack Sharing
BSC Node Redundancy
BSC/RNC Clock
BSC/RNC Resource Sharing
BSC/RNC Software Management BSS Local Switching
Issue 08 (2011-09-30)
Document BTS Combined Cabinets and Cabinet Groups
Description BTS combined cabinets and cabinet groups can be used to implement a large-capacity BTS, reduce the number of BTSs required, and save the construction and maintenance costs of BTSs. BTS combined cabinets and cabinet groups are applicable to the areas where the traffic is heavy and the construction and maintenance costs of BTSs are high. The GPS is a round-the-clock satellite navigation system that communicates with a BTS in wireless mode. The GPS provides accurate three-dimensional location, velocity, and time for worldwide users. The BTS GPS Synchronization feature enables a BTS clock to be synchronized with the GPS clock source. BTS power management supports hierarchical power-off and voltage abnormal protection. This feature enhances power management and self-protection of the BTS, thus improving the reliability of the system, prolonging the lifespan of products and serving time of the system. The highlight of the BTS ring topology is that when a connection is broken, the ring automatically breaks into two chains at the break point. In this way, the BTSs that precede and follow the break point can work normally; thus improving the robustness, reliability, and security of the system. BTS test involves site test, baseband test, baseband idle timeslot test, TCH loopback test, transmission performance test, cyclic redundancy check (CRC), and BTS antenna fault detection. This feature facilitates not only the BTS installation and commissioning at the local end, but also the BTS remote management through the NMS and OMC. This document describes the functions, types, and parameter meanings of the BTS/NodeB clock. BTS/NodeB software management provides efficient and accurate software installation, software upgrade, and software version management.
BTS GPS Synchronization
BTS Power Management
BTS Ring Topology
BTS Test Function
BTS/NodeB Clock
BTS/NodeB Software Management
Issue 08 (2011-09-30)
Document BTS/NodeB Software USB Download
Description Users or maintenance personnel can download and activate the MBTS software through USB without using portable computers. Thus, the MBTS can be set up easily and quickly. Call control is a basic feature for the operators to provide the CS speech services. Through the call control procedure, the BSS provides required radio resources and terrestrial circuit to the call so that the CN can complete the call connection procedure. When the MS encounters a radio link failure during the call, the call reestablishment procedure can be used to reestablish the radio link connection so that the original call can proceed. Thus, the call is reestablished quickly after a call drop. This mechanism shortens the call intermission, and thus improves the user experience. The Short Message Service Cell Broadcast (SMSCB) (cell broadcast service for short) refers to the information broadcast service for the MSs in the idle state within a specified area. This feature uses an idle TCH to test uplink receive level of all frequencies of the specified frequency band. Engineers can use the test result to select a proper operating frequency. Cell frequency scan enables operators to assess the current electromagnetic environment without the help of any test devices. It serves as a reference for operators to perform network planning and network optimization. In this manner, cell frequency scan improves the maintenance efficiency and reduces the O costs. This feature traces the signaling of calls in a specific cell. The signaling over the A, Abis, or Um interface can be traced and the signaling of a maximum of 16 calls can be traced at a time. In the radio channel management, many factors are considered to ensure that the most appropriate radio channels are assigned to the radio services.
Call Control
Call Reestablishment
Cell Broadcast
Cell Frequency Scan
Cell Tracing
Channel Management
Issue 08 (2011-09-30)
Document Ciphering
Description The signaling, speech, and data transmitted over the Um interface are ciphered, thus guaranteeing the information security and preventing user information from unauthorized access. This document describes the configuration management feature. The connection inter BSC over IP feature provides a direct transmission path between BSCs and a direct channel for exchanging information between BSCs, which enables the inter-BSC soft-synchronized network and IBCA functions. This document describes the functions and technologies regarding the connection with the tower mounted amplifier (TMA) feature, including the RF RX channel attenuation configuration, power supply configuration,and working status monitoring configuration for the TMA. The Local Maintenance Terminal (LMT) provides topology maintenance for the Distributed Base Station (DBS) and thus facilitates the maintenance operations. The DTX and DRX mechanism can be used to reduce the interference level and improve the system efficiency. Through this mechanism, the wastage of system resources is minimized and an acceptable signal quality is maintained. The DTM technology enables the coexistence of CS services with PS services in the GSM/ EDGE network. In DTM mode, the MS can perform PS services and CS services at the same time. The Dual Carriers in Downlink feature is introduced to increase the downlink data rate of a single user. When two downlink carriers are used, the downlink data rate is doubled, that is, the downlink data rate of the EGPRS system is increased from 473.6 kbit/s to 947.2 kbit/s. Dynamic Channel Conversion enables the conversion of a channel from one type to another based on the actual service requirement in the network.
Configuration Management Connection Inter BSC over IP
Connection with TMA (Tower Mounted Amplifier)
DBS Topology Maintenance
Discontinuous Transmission and Discontinuous Reception
DTM
Dual Carriers in Downlink
Dynamic Channel Conversion
Issue 08 (2011-09-30)
Document Easy GSM
Description After Easy GSM is introduced into a BTS, the BTS has functions such as automatic frequency configuration, planning, and optimization. Thus, the cost of operation and maintenance can be decreased. Compared with FR, EFR optimizes the speech codec algorithm and improves the speech quality, thus improving customer satisfaction. Compared with EGPRS, EGPRS doubles the uplink and downlink data rates in theory. That is, the data rate is increased from about 473.6 kbit/s to about 1 Mbit/s. This helps to meet the data rate requirement of the 3G network. The enhanced Multi-Level Precedence and Preemption service (eMLPP) provides a subscriber segmentation function for operators. By enabling this function, operators can provide different levels of services for subscribers with different priorities. With the introduction of the enhanced measurement report (EMR), better performance of the interoperability between the UMTS network and the GSM network and more measurement information about neighboring cells can be obtained. Compared with the common MR, EMR may contain the information about more neighboring cells. The encrypted network management feature is based on the Secure Socket Layer (SSL) protocol, which allows the M2000 to set up an SSL-based TCP transmission channel between the M2000 server and NEs. This feature ensures the privacy of customers data and reduces the possibility that data be intercepted owning to transmission through plain text. End-to-end MS signaling tracing is a feature based on which the network administrator traces the activities of each NE when an event occurs. Enhanced packet loss concealment (EPLC) prevents the voice quality deterioration caused by frame loss and improves the voice quality. This feature improves the user experience, prolongs the average call duration, and increases the operators revenue.
EFR
EGPRS2
eMLPP
EMR
Encrypted Network Management
End-to-End MS Signaling Tracing
Enhancement Packet Loss Concealment (EPLC)
Issue 08 (2011-09-30)
10
Document Faulty Management Flex Abis
Description This document describes the basic components and functions of the fault management. Flex Abis (Flexible Abis) enables the sharing of the Abis interface transmission resources among different BTSs, cells, and services, and thus improves the resource utilization. Flex Ater is a feature based on which Ater resources are allocated according to the channel type during the call establishment. If TCHFs are allocated on the Um interface, 16 kbit/s timeslots are used on the Ater interface. If TCHHs are allocated on the Um interface, 8 kbit/s timeslots are used on the Ater interface. The Flex MAIO algorithm estimates the interference between channels before allocating an appropriate MAIO to the channel to be assigned, thus ensuring that the channel with the minimum interference is assigned. The BSS performs flow control to reduce the service connections or disable some maintenance functions based on their priorities. This ensures the smooth operation of primary services and enables the BSS to be restored to the normal state within a short period of time. Through Flow Control, the performance and stability of the BSS are improved to a great extent. This feature enables Huawei BSS to support that the system information be sent manually to a certain cell through the BSC and the system information of certain cells be updated manually. This helps the network optimization and maintenance personnel to verify the parameter adjustment. Four-way receive diversity helps to suppress Rayleigh fading and provide better signal quality on the uplink, thus improving the quality of service (QoS). In addition, four-way receive diversity can be used to improve the uplink performance in wide coverage scenarios.
Flex Ater
Flex MAIO
Flow Control
Forced System Information Sending by OMC
Four-Way Receive Diversity
Issue 08 (2011-09-30)
11
Document Frequency Hopping
Description Frequency Hopping achieves the same effects as frequency diversity and interference diversity. Frequency diversity helps to improve the anti-attenuation capability of radio signals. Interference diversity helps to overcome cochannel and adjacent-channel interference, and thus tight frequency reuse patterns can be adopted. With operators increasingly preferring PS services, more and more channel resources on the Um interface are required for PS services. To ensure the quality of CS services and PS services, GPRS/EGPRS Channel Management is introduced to manage all the PDCHs effectively. The GPRS/EGPRS connection control and transfer feature optimizes the TBF establishment and release procedures so that each MS can obtain the best possible data throughput and the MS access time can be shortened. GPRS/EGPRS link quality control is implemented to adjust GPRS/EGPRS coding schemes dynamically according to the radio link quality status during packet data transmission. It enables coding schemes to adapt to the variation of the radio environment, maximizes the data throughput, and increases the data rate and system capacity. GPRS provides a variety of PS services. EDGE increases the data rates of GSM to a great extent to meet the requirements of high-speed data services. GPRS/EGPRS QoS refers to the quality of GPRS/EGPRS services in the GSM EDGE Radio Access Network (GERAN). The emergency call guarantee feature is the enhancement of the emergency call feature. With the emergency call guarantee feature, the setup success rate of emergency calls is improved.
GPRS/EGPRS Channel Management
GPRS/EGPRS Connection Control and Transfer
GPRS/EGPRS Link Quality Control
GPRS/EGPRS Overview
GPRS/EGPRS QoS
Guaranteed Emergency Call
Issue 08 (2011-09-30)
12
Document Half-Rate Service
Description With the increase in the number of subscribers, the GSM spectrum becomes insufficient. The introduction of half-rate speech improves spectrum efficiency and network capacity to a great extent by increasing the number of configurable speech channels and at the same time not affecting the QoS to a great extent. Handover is a basic function of the mobile communications system and it ensures that mobile services are not disrupted. Handover is controlled by the network. When receiving the Error Indication message from the BTS during a handover, the BSC attempts to re-establish the call on the source channel instead of processing it as a call drop. The 2 Mbit/s signaling link, also called highspeed signaling link, is the No.7 signaling link in the SS7 network with a data rate of N x 64 kbit/s (1 N < 32). Here, N indicates the number of timeslots occupied by the high-speed signaling link. The BSC uses the high-speed signaling links when the signaling load of the system is high. Idle mode refers to the mode that an MS is switched on but is not allocated a dedicated channel. An MS in idle mode can access the network and can be reached by the network. GBSS products access Huawei mobile integrated network management system (NMS) iManager M2000 through the integrated network management interface. With the intelligent power consumption decrease technology, the BTS power consumption is decreased by adopting good quality power-saving hardware, advanced RF technologies, and related algorithms. If a BTS uses an AC power input and the PSU is faulty, the power amplifiers of some TRXs are shut down to reduce the power demand of the BTS to ensure the normal operation of the BTS. This document describes the interface message tracing feature.
Handover
Handover Re-establishment
High-Speed Signaling
Idle Mode Behavior
Integrated Network Management Interface
Intelligent Power Consumption Decrease
Intelligent Shutdown of TRX Due to PSU Failure
Interface Message Tracing
Issue 08 (2011-09-30)
13
Document Inventory Management IP BSS
Description This document describes the principles of the inventory management system. This document describes the protocol stacks and network topologies on the BSS-related interfaces. This document describes the IP transport architecture of the BSC6900. The architecture enables IP transport on the interfaces of the GSM and UMTS networks. This document also describes the related transport protocols, IP QoS mechanisms, transmission efficiency improvement mechanisms, and networking reliability. The Latency Reduction feature is based on the RTTI technology and the FANR technology. Reduced latency helps to improve the user experience of the interactive class service and the BE service. The License Control for Urgency feature involves setting and querying the emergency status of license, generating emergency license alarms, and setting the grace protection period switch. This document describes the characteristics and functions of the license management. The feature of local multiple signaling points enables one physical BSC to function as multiple logical BSCs. Each logical BSC has an SS7 signaling point code. The number of messages sent and received within the BSC is reduced when each logical BSC serves as an independent BSC to interact with the MSC. The location service can increase the operator` s revenue. Operators can provide various location services for an MS based on the location of the MS. These location services include weather forecasts, trip scheduling, emergency assistance, stock information, business planning, and transportation information.
IP Transport Architecture Description
Latency Reduction
License Control for Urgency
License Management Local Multiple Signaling Points
Location Service
Issue 08 (2011-09-30)
14
Document Maintenance Mode Alam
Description Maintenance mode alarms are generated by NEs in a network under certain maintenance operations. These alarms such as reset, switchover, and link disconnection alarms, are of high severities and are automatically cleared after the maintenance operations are complete. Man Machine Language (MML) provides daily operation and maintenance to NEs through commands. All the MSCs in the MSC pool implement load balancing and resource sharing for equal distribution of traffic in the MSC pool, thus reducing inter-MSC handovers and providing redundancy. With the introduction of Multiband Network, the characteristics of multiple frequency bands can be optimally used to expand the network capacity. Multi-cell function is a function based on which more than three cells are configured for a single BTS to improve system capacity. Multi-site cell is a feature in which multiple subsites are configured as one cell. This reduces handovers between subsites, increases coverage efficiency, and improves user experience. This feature is applicable to such coverage scenarios as high-speed railways, tunnels, indoor space, and rural areas. NACC can accelerate the packet service access in the target cell, and it shortens the period of packet service disruption during cell reselection. The NAT firewall is deployed between the BSC and the LMT or the M2000 to ensure the network security of the GBSS. The network comprehensively considers factors such as the receive level and load status in the serving cell and in the neighboring cells so that the MS can reselect a proper cell. In this manner, the load in the cells can be balanced. This document describes the principles of star topology, tree topology, and chain topology.
Man Machine Language (MML)
MSC Pool
Multiband Network
Multi-Cell Function
Multi-Site Cell
NACC
NAT Beside OM
NC2
Network Structure
Issue 08 (2011-09-30)
15
Document Networking Modes
Description This describes the main networking modes and two configuration modes of LADP links. Reasonable application of the networking modes ensures good service quality. Huawei provides an O&M platform of the BSS system, which fulfills operators requirement for easy, secure, and effective O&M Huawei BTS O&M system has various operating modes. Through the BTS OMC at the local end or the remote end, O&M can be performed for BTS logical objects or BTS boards. The BTS O&M has powerful functions, facilitates and simplifies the O&M, and reduces the O&M expenditure. OML backup improves the robustness of the BTS. When the working OML is broken because transmission links are faulty, the BTS is not reset and cells are not out of service. This document describes the operate system security management feature. This feature supports the quick recovery of the operating system or the configuration data. It reduces the complexity of the backup and recovery of the operating system or the configuration data of the OMU or the BAM server. It also reduces the time of the service disruption caused by the operation and maintenance. The PBT is a power boost technology. In PBT mode, the two TRXs in the double-transceiver unit are used as one TRX. This document describes the performance management feature, including performance measurement procedure, performance measurement management, and real-time performance monitoring. The PICO Automatic Configuration and Planning feature facilitates quick deployment and flexible adjustment of the network of the operators and relieves the engineers from the relevant configuration workload.
O&M of BSC
O&M of BTS
OML Backup
Operate System Security Management Operation & Maintenance System OneKey Recovery
PBT
Performance Management
PICO Automatic Configuration and Planning
Issue 08 (2011-09-30)
16
Document Power Control
Description After a radio link is established, the BSS controls the transmit power of the MS and BTS. The required QoS, however, must be ensured when the transmit power decreases. PS handover greatly reduces the time delay of cell change and ensures high data throughput in the target cell, thus improving the QoS. This feature provides basic functions for operators to carry on telephone services. Radio common channel management involves the management of common control channels such as PCH, RACH, AGCH, NCH, PPCH, PRACH, and PAGCH. It is a basic feature for the operators to provide CS speech services. Radio dedicated channel management involves the assignment, activation, release, management, and reporting of the dedicated channels such as SDCCH, SACCH, and TCH. These procedures are used to establish, maintain, and release radio links. Radio link management involves nine procedures: link establishment indication, link establishment request, link release indication, link release request, transmission of a transparent L3-message in acknowledged mode, reception of a transparent L3-message in acknowledged mode, transmission of a transparent L3-message in unacknowledged mode, reception of a transparent L3-message in unacknowledged mode, and link error indication. RAN Sharing enables multiple operators to share the network resources on the BSS side but retain their own subscribers and services. This feature provides the environment and power supply monitoring of the equipment room to ensure the physical security. The remote electrical tilt refers to an antenna system whose tilt is controlled electrically.
PS Handover
Radio Bearer Services Radio Common Channel Management
Radio Dedicated Channel Management
Radio Link Management
RAN Sharing
Remote EAC Maintenance
Remote Electrical Tilt
Issue 08 (2011-09-30)
17
Document Remote Upgrade of BSC&BTS Software
Description Remote upgrade of BSC software is a process in which the BSC software is remotely upgraded through the M2000. Multiple BSCs can be upgraded in batches. Remote upgrade of BTS software is a process in which the BTS software is remotely upgraded through the M2000. Multiple BTSs can be upgraded at a time. This feature not only reduces the manpower of the O and check, but also helps operators remotely monitor the temperature in the BTS equipment room. With robust air interface signaling, the signaling link gain is improved by transmitting ACCH frames repeatedly. Satellite transmission uses a satellite for telecommunications and is very useful in remote mountain areas or sparsely populated plains.MOC. This document describes the operate system security management feature. The Semipermanent Connection feature enables some idle E1 timeslots in the BSS to be used as transmission paths for transmitting information such as business hall information, alarm information on the BTS AC power supply, and other maintenance information. Semipermanent Connection helps to optimally utilize the network resources and minimize the operators cost. SGSN Pool enables multiple SGSNs to form an SGSN pool. A BSC belonging to an SGSN pool area is connected to all SGSNs in the SGSN pool. The resources and load are shared by all the SGSNs in the pool, thus balancing the traffic load and reducing inter-SGSN handovers. This feature supports the signaling transfer function based on the SCCP/M3UA, which supports a maximum of 32 STPs, thus meeting the requirements of the operators in terms of the networking mode.
Reporting the Temperature List of the BTS Equipment Room
Robust Air Interface Signaling
Satellite Transmission
Security Management Semipermanent Connection
SGSN Pool
Signalling Transfer Point (STP)
Issue 08 (2011-09-30)
18
Document Soft-Synchronized Network
Description The Soft-Synchronized Network technology converts an asynchronous network into a synchronous network through software upgrade without any changes in the hardware of the existing network. This technology provides a technical support platform for radio network optimization and network performance improvement. In addition, this technology enables operators to introduce new services. Daylight Saving Time is a way of getting more light out of the day by advancing clocks by one hour during the summer. The BSC6900 supports both three-digit and two-digit MNCs. This document describes the system redundancy. The TC Pool feature is implemented by connecting multiple BSCs with the transcoder subrack (TCS) of one BSC. In this manner, all the involved BSCs share the TC resources. TC Pool is especially applicable to the scenario where multiple BSCs with small capacity are deployed. In such a scenario, multiple BSCs with small capacity share the TC resources, thus saving the CAPEX of network deployment. The TCH re-assignment based on which the BSC re-assigns a TCH to the MS after the previous TCH assignment fails and the MS returns to the SDCCH. This feature minimizes the impact on the call continuity caused by the TRX channel fault, and greatly reduces the assignment failures caused by the frequency interference in a cell, and thus minimizes the impact on the call continuity and improve the service quality. Tandem Free Operation (TFO) eliminates one process of encoding and decoding the Transcoder/Adaptor Unit (TRAU) frame, thus improving the speech quality. In transmit diversity mode, the baseband signal of an MS is transmitted on two RF channels. Thus, the signal quality on the downlink is improved, and the impact of Rayleigh Fading on the MS is reduced.
Support of Daylight Saving Time
Supporting Three-Digit MNC System Redundancy TC Pool
TCH Re-assignment
TFO
Transmit Diversity
Issue 08 (2011-09-30)
19
Document TrFO
Description The TrFO feature enables the calling MS and called MS to use the same speech coding, which prevents the repeated coding and decoding during the MS-originated and MS-terminated call procedure. This provides better speech quality for users. The TrFO feature can also save the TC resources. TRX cooperation means that when a TRX in a cell is faulty, the BSC designates another available TRX in the cell to replace the original TRX. TRX management includes the following procedures: radio resource indication, SACCH filling information modification, flow control, and error reporting. The document describes the TX diversity and RX diversity features. This document describes the user signaling tracing feature. The GSM-R provides new features that are unavailable in the original GSM network. Such new features include the Voice Group Call Service (VGCS), Voice Broadcast Service (VBS), and enhanced Multi-Level Precedence and Pre-emption (eMLPP) service. The GSMR can provide diversified voice dispatch services required in the private network. Voice Quality Index (VQI) describes the mapping between the radio transmission performance and the voice quality. The impact of the radio transmission performance on the voice quality can be determined according to VQI. The sampling rate of the Wide Band Adaptive Multi Rate Codec (WB AMR) is 16 kHz, and the speech frequency ranges from 50 Hz to 7 kHz. Compared with AMR, WB AMR has wide speech bandwidth. Thus, WB AMR can provide better speech quality.
TRX Cooperation
TRX Management
TX Diversity and RX Diversity User Signaling Tracing VGCS/VBS
Voice Quality Index
WB AMR
1.2 Library Changes

This describes the changes in the library.
Issue 08 (2011-09-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 20
08 (2011-09-30)
This is the eighth commercial release of GBSS9.0.
07 (2011-08-17)
This is the seventh commercial release of GBSS9.0.
06 (2011-07-08)
This is the sixth commercial release of GBSS9.0.
05 (2010-11-30)
This is the fifth commercial release of GBSS9.0.
04 (2010-07-15)
This is the fourth commercial release of GBSS9.0.
03 (2010-02-10)
This is the third commercial release of GBSS9.0.
02 (2009-09-30)
This is the second commercial release of GBSS9.0.
01 (2009-06-30)
This is the first commercial release of GBSS9.0.
1.3 Glossary
Purpose
This document provides the terms and abbreviations of Huawei BSC documents.
Product Version
The product version related to this document are as follows: Product Name BSC Product Model BSC6900 Product Version V900R011
Intended Audience
The intended audience is as follows:
l l l l l l l l
Network operators Shift operators System engineers Field engineers Network planners BSC installers Site maintainers Administration Engineers
Organization
1.3.1 Numerics
Modulation technique using two amplitude modulated RF (Radio Frequency) carriers 16 Quadrature Amplitude Modulation that are out of phase by 90 degrees. Information transfer is achieved using a mixture of phase and amplitude changes. Since noise also appears as amplitude variations QAM is prone to interference. 16QAM 2 Mbit/s 2G-3G handover See 16 Quadrature Amplitude Modulation Transmission rate of 2048 kbit/s. The 2G/3G interoperability feature enables a mobile station (MS) to be handed over or be reselected to the GSM/UMTS network if the serving cell of the MS is not covered by the GSM/UMTS network or if the communication quality of the MS in a GSM/UMTS cell is bad. High speed signaling link with a data rate of N x 64 kbit/s (1N<32). See Third Generation Partnership Project Transmission rate of 64 kbit/s.
2Mbit/s signaling link 3GPP 64 kbit/s
64 kbit/s signaling link Signaling link with a transmission rate of 64 kbit/s. 8PSK modulation mode 8 Phase Shift Keying modulation mode.
1.3.2 A
A Interface AAL2 ABB Abis Interface Abis MUX The A infterface is the interface between the BSC and the MSC/MGW. It supports the signaling channels and traffic channels of 64 kbit/s. See ATM Adaptation Layer type 2 Abis Bypass Board The Abis interface is the interface between the BSC and the BTS. It is a Huawei internal interface. Abis MUX is a multiplexing technique. In Abis MUX, the transmitting end (BSC or BTS) multiplexes multiple UDPs that meet the multiplexing conditions into one UDP/ IP packet so that these UDPs share one header; then, the receiving end demultiplexes the UDP/IP packet to obtain the original UDPs. In this way, the transmission efficiency is improved.
Issue 08 (2011-09-30)
22
Absolute Radio Frequency Channel Number
Within the spectrum allocated for cellular mobile communications, the radio channels are identified by ARFCN. If the system is operating in FDD (Frequency Division Duplex) mode then the channel number is associated with both the uplink and downlink radio channels. Within the GSM900 spectrum ARFCN 1 to 124 are used. In GSM1800, ARFCN 512 to 885 are used and in GSM1900 ARFCN 512 to 810 are used. See Access Control See Alternating Current The supply of electric power by alternating current. A security mechanism that determines which operations a user, group, service, or computer is authorized to perform on a computer or on a particular object, such as a file, printer, registry key, or directory service object. Access Grant Channel, is used to assign resources to a user requesting access to the network. These resources will include the dedicated channel to be used along with timing advance information. Access Link Control Application Part is a generic name for the transport signalling protocol used to setup and tear down transport bearers. In UMTS the main ALCAP protocol is the AAL2 signalling protocol. Associated Control Channel,The GSM signalling channels associated with a user's traffic channel or dedicated signalling channel. See ACKnowledgement An RRC connected mode where neither DCCH nor DTCH is available. A Layer 2 response by the mobile station or the base station confirming that a signaling message was received correctly. A type of signal processing commonly used in teleconferencing. The Acquisition Indicator Channel is a fixed rate physical channel with a spreading factor of 256 equating to 32Kbps. It is used to carry acquisition indicators which correspond to signatures on the PRACH (Physical Random Access Channel). Active Coding Set Active factor reflects the actual usage of bandwidth. For example, if the active factor is 50, it indicates that the actual usage of bandwidth is 50%. HARQ process to which scheduling grants are applicable, that is, in which scheduled data can be sent. The UE sends CQI through the HS-DPCCH to the NodeB to report the channel quality. The NodeB decides the size of the transport blocks and modulation mode according to the CQI. When the UE is in good radio environment, the transmission can adopt the high order 16QAM modulation mode and large transport blocks to achieve high peak rate. When the UE is in poor radio environment, the transmission can adopt low order QPSK modulation mode and small transport blocks to ensure communication quality.
AC AC AC power supply Access Control
Access Grant Channel
Access Link Control Application Part ACCH ACK Acknowledged Mode ACKnowledgement Acoustic Echo Cancellation Acquisition Indicator Channel ACS Active factor Active process Adaptive Modulation and Coding
Issue 08 (2011-09-30)
23
Adaptive Multi-Rate codec
A codec offering a wide range of data rates. The philosophy behind AMR is to lower the codec rate as the interference increases and thus enabling more error correction to be applied. The AMR codec is also used to harmonize the codec standards amongst different cellular systems. Address Resolution Protocol (ARP) refers to an Internet Protocol (IP) that is used to map an IP address to an MAC address. It allows host computers and routers to determine the data link layer addresses through the ARP request and ARP response. The phenomenon whereby channels are beside one another in the frequency domain may have some spectral overlap, causing impairment and interference. ACI is caused by inadequate filtering, and thus signals in an adjacent channel are leaked to the transmission bandwidth. A reconfigurable optical add-drop multiplexer (ROADM) is a form of optical add-drop multiplexer that adds the ability to remotely switch traffic from a WDM system at the wavelength layer. This allows individual wavelengths carrying data channels to be added and dropped from a transport fiber without the need to convert the signals on all of the WDM channels to electronic signals and back again to optical signals See Asymmetrical Digital Subscriber Line See Acoustic Echo Cancellation Back wastage in the BSCBTSMSBTSBSC acoustic echo loop. Time length of the BSCBTSMSBTSBSC voice loop. RNC 32-port ATM over E1/T1/J1 interface Unit REV:a See Assured Forwarding See Automatic Frequency Control See Automatic Frequency Planing Absolute Grant See Access Grant Channel See Network Assisted GPS See Acquisition Indicator Channel See Alarm Indication Signal Antenna Interface Standards Group Authentication and Key Agreement A pane that displays on the N2000 UMS client. It displays the statistics of current N2000 UMS alarms in different colors. By watching the alarm board, you can monitor the entire network in real-time and know the severity of an alarm and its related statistics. Alarm indication signal (AIS) is a signal transmitted by a system that is part of a concatenated telecommunications system to let the receiver know that some remote part of the end-to-end link has failed at a logical or physical level, even if the system it is directly connected to is still working. See Automatic Level Control The gain values of the downlink voice signal level in the fixed gain mode. The expected level values of the uplink voice signal level in the auto gain mode.
Address Resolution Protocol Adjacent-channel interference
ADM
ADSL AEC AEC back wastage AEC pure delay AEUa AF AFC AFP AG AGCH AGPS AICH AIS AISG AKA Alarm Board
Alarm Indication Signal
ALC ALC FWD Gain ALC Level Expect
Issue 08 (2011-09-30)
24
ALC Mode ALC Rate Adjust ALC RVS Gain ALC VAD Threshold ALCAP Algorithm A5 Allocation Retention Priority ALM Alternating Current AM AMC American Standard Code for Information Interchange AMR AMRC Analog signal
Three gain modes of the ALC are available: pass, fixed, and auto. The gain adjust rate of the uplink voice signal level in the fixed gain mode. The gain values of the uplink voice signal level in the fixed gain mode. The test threshold values of the uplink voice signal level in the auto gain mode. See Access Link Control Application Part Ciphering algorithms specified in the GSM specification: The A5 ciphering algorithms consist of the A5/0, A5/1, A5/2, A5/3, A5/4, A5/5, A5/6, and A5/7 algorithms. It is a QoS attribute that specifies the relative importance compared to other UMTS bearers for allocation and retention of the UMTS bearer. See Alarm Board Current which constantly changes in amplitude, and which reverses direction at regular intervals. See Acknowledged Mode See Adaptive Modulation and Coding American Standard Code for Information Interchange - the standard system for representing letters and symbols. Each letter or symbol is assigned a unique number between 0 and 127. See Adaptive Multi-Rate codec Adaptive Multi-Rate Control algorithm 1. A signal that has a continuous nature rather than a pulsed or discrete nature. Note: Electrical or physical analogies, such as continuously varying voltages, frequencies, or phases, may be used as analog signals. 2. A nominally continuous electrical signal that varies in some direct correlation with another signal impressed on a transducer. Note: For example, an analog signal may vary in frequency, phase, or amplitude in response to changes in physical phenomena, such as sound, light, heat, position, or pressure. Adjacent Node Identifier See Automatic Noise Restraint A device which radiates and/or receives radio signals. When working as a transmitter, it converts high frequency current to electromagnetic waves; when working as a receiver, it coverts electromagnetic waves to high frequency current. A transmission line between an antenna and a transmitter. A component to connect a third party compatible external antenna to improve wireless range. Angular Of Arrival RNC 2-port ATM over channelized Optical STM-1/OC-3 Interface Unit REV:a See Application Protocol Data Unit See Application Program Interface Advanced Phase Lock Advanced Power Module
ANI ANR Antenna
Antenna feeder Antenna port AOA AOUa APDU API APL APM
Issue 08 (2011-09-30)
25
Application Program Interface Application Protocol Data Unit APS ARFCN ARP ARP ARPU ASCII Assignment Failure Association Assured Forwarding
A set of routines, protocols, and tools used when building software applications. A PDU carrying application layer control information and data. See Automatic Protection Switching See Absolute Radio Frequency Channel Number See Allocation Retention Priority See Address Resolution Protocol See Average Revenue Per User See American Standard Code for Information Interchange A message indicating that the channel assignment fails. An association refers to a logical relation (channel) for data transmission which is set up by two SCTP endpoints through the four-way startup handshake mechanism of SCTP. A QoS (Quality of Service) term employed within the DiffServ (Differentiated Services) policy. Assured Forwarding values are set as part of the PHB (Per Hop Behaviour) used by routers. This value is used to determine the degree of reliability a packet should be afforded within the DiffServ domain. Access network SDH transmission Unit A technology that allows more data to be sent over existing copper telephone lines (POTS (Plain Old Telephone Service)). ADSL supports data rates of from 1.5Mbps to 9Mbps when receiving data (known as the downstream rate) and from 16Kbps to 640Kbps when sending data (known as the upstream rate). ADSL requires a special modem. A transmission channel between the GMPS or GEPS and the GTCS. Ater connection path is the transmission path between the GMPS/GEPS and the GTCS. It is used to transmit traffic data and signaling. The Ater interface is the interface between the MPS/EPS subrack and the TCS subrack. It is used to transmit SS7 signaling. AAL2 supports continuous bit rate transmissions, but also solves the problems of packetization delay and efficiency in the use of bandwidth resources. Attach-Detach allowed See Authentication Center A procedure used by a base station to validate a mobile station's identity.
ASU Asymmetrical Digital Subscriber Line
Ater Ater connection path Ater Interface ATM Adaptation Layer type 2 ATT AUC Authentication
Authentication Center A GSM network component which stores information for authenticating mobiles, and encrypting their voice and data transmissions. Authentication Response Authentication Token An 18-bit output of the authentication algorithm. It is used, for example, to validate mobile station registrations, originations and terminations. The Authentication Token is sent in the Authentication Request message to the mobile along with a random number and KSI (Key Set Identifier). The variables within the AUTN are used by the mobile in the authentication process that it conducts with the network.
Issue 08 (2011-09-30)
26
Authentication vector
The UMTS authentication vector uses a quintet of parameters which provides temporary authentication data that enables an VLR or SGSN to engage in UMTS authentication with a particular user. See Authentication Response See Authentication Token A device or circuit that maintains the frequency of an oscillator within the specified limits with respect to a reference frequency. Automatic frequency planning that can shorten the planning period of the large-scale network. ALC, also called automatic gain control (AGC), is a well-known application in communication systems with a given input signal conditioned to produce an output signal as possible, while supporting a wide gain range and controlled gain-reduction and gain recovery characteristics. ANR processes the uplink speech signals after decoding and filters the background noise. Automatic Protection Switching (APS) is the capability of a transmission system to detect a failure on a working facility and to switch to a standby facility to recover the traffic. This term is used by telephone carriers. This term has also become widely used in other industries including consumer Internet services. It is the revenue generated by a customer phone, pager, etc., per month. In mobile telephony, ARPU includes not only the revenues billed to the customer each month for usage, but also the revenue generated from incoming calls, payable within the regulatory interconnection regime.
AUTHR AUTN Automatic Frequency Control Automatic Frequency Planing Automatic Level Control
Automatic Noise Restraint Automatic Protection Switching Average Revenue Per User
1.3.3 B
BA Back Administration Module Backward Sequence Number BAM Band Class Base station Color Code See BCCH Allocation In the OM subsystem, it works as a bridge between the Local Maintenance Terminal (LMT) and the Front Administration Module (FAM). The BSN is used to acknowledge the receipt of signal units by the remote signaling point. See Back Administration Module A set of frequency channels and a numbering scheme for these channels. In the GSM system, this code is transmitted in the SB (Synchronization Burst) and is used in the MS (Mobile Station) to discriminate between cells using the same frequencies during the cell selection and camping on process. The BCC is also used to identify the TSC (Training Sequence Code) to be used when reading the BCCH (Broadcast Control Channel).
Base Station Controller The Base Station Subsystem (BSS) is the section of a GSM network which is responsible for transmitting to and receiving radio signals from the mobile phone. The BSS carries out transcoding of speech channels, allocation of radio channels to mobile phones, paging and many other tasks related to the radio network. Base Station Identification A 16-bit number that identifies a base station pertaining to an NID.
Issue 08 (2011-09-30)
27
Base Station Interface Equipment
When the BTS is connected to a remote BSC, the Abis interface is adopted, and BIE must be used at the BTS and the BSC.
Base Station Subsystem The protocol employed across the A interface in the GSM system. It is used to transport Application Part MM (Mobility Management) and CM (Connection Management) information to and from the MSC (Mobile Switching Centre).The BSS Application Part (BSSAP) is split into two sub application parts, these are: the BSS Management Application Part (BSSMAP) and the Direct Transfer Application Part (DTAP). Base Station Subsystem The Base Station System GPRS Protocol is supported across the Gb interface, its primary GPRS Protocol functions include: 1. the provision by an SGSN (Serving GPRS Support Node) to a BSS (Base Station Subsystem) of radio related information used by the RLC (Radio Link Control) and MAC (Medium Access Control) function. 2.the provision by a BSS to an SGSN of radio related information derived from the RLC/MAC function. 3.the provision of functionality to enable two physically distinct nodes, an SGSN and a BSS, to operate node management control functions. Base Station Subsystem This protocol is also used to convey general BSS (Base Station System) control information between the MSC (Mobile Switching Centre) and the BSS. An example is Management the allocation of traffic channels between the MSC and the BSS. Application Part Base Station System In GSM the Base Station System is a term given to a BSC (Base Station Controller) and the BTS (Base Transceiver Station) associated with it. The number of BTS associated with a BSC is dependent on the manufacturer. Although not mandatory, through interpretation of the Abis interface standard BTS and BSC employed within a BSS will always be supplied by the same manufacturer. The BSS is the physical equipment used to give radio coverage to a determined geographical zone called a cell. Functionally, a BSS is subdivided into BSC and BTS. A Base Transceiver Station terminates the radio interface. It allows transmission of traffic and signaling across the air interface. The BTS includes the baseband processing, radio equipment, and the antenna. This is a code in GSM which is broadcast on the SCH (Synchronization Channel) in order to identify the NCC (Network Color Code) and the BCC (Base Station Color Code). Baseband is a form of modulation in which the information is applied directly onto the physical transmission medium. In baseband frequency hopping, the carrier frequency assigned for the transmitter of the TRX does not participate in frequency hopping and remains unchanged. The transmit frequency hopping is achieved with the switching of baseband signals among different TRXs. The receiver of the TRX, however, must participate in frequency hopping. The carrier frequency assigned for the receiver changes with the carrier frequency used by an MS. The number of carrier frequencies assigned for frequency hopping in a cell cannot exceed the number of TRXs assigned for the cell. This term is used as a common reference to both bearer services and teleservices. See Base station Color Code See Broadcast Control Channel Allocation of frequencies for BCCH transmissions in a cell. See Binary-Coded Data Base Station Control Function
Base Transceiver Station Base transceiver Station Identity Code Baseband Baseband Frequency Hopping
Basic service BCC BCCH BCCH Allocation BCD BCF
Issue 08 (2011-09-30)
28
BCH BER BESP Best effort service BFD BFH Bidirectional Forwarding Detection
Broadcast Channel,a code channel in a Forward CDMA Channel used for transmission of control information and pages from a base station to a mobile station. See Bit Error Rate BTS E1 Surge Protector A service model which provides minimal performance guarantees, allowing an unspecified variance in the measured performance criteria. See Bidirectional Forwarding Detection See Baseband Frequency Hopping Bidirectional Forwarding Detection (BFD) is a simple Hello protocol, similar to the adjacent detection in the route protocol. Two systems periodically send BFD detection messages on the channel between the two systems. If one system does not receive the detection message from the other system for a long time, you can infer that the channel is faulty. Under some conditions, the TX and RX rates between systems need to be negotiated to reduce traffic load. See Base Station Interface Equipment Coded in the binary form used by computers and stored on a suitable medium such as magnetic tape. The number of erroneous bits received divided by the total number of bits transmitted. See Building Integrated Timing Supply System Base station Interface Unit See Broadcast/Multicast Control
BIE Binary-Coded Data Bit Error Rate BITS BIU BMC
Boolean value, Boolean Boolean data has one of only two values, true or false. Boolean values are used in control variable, toggle value structures such as the if statement. BOOTP BootROM See Bootstrap Protocol A writable and erasable storage medium for binary data (machine code). The BootROM software refers to the software bound with hardware. It provides basic device drive function and can be started and updated manually. Bootstrap Protocol is a TCP/IP protocol that enables a network device to discover certain startup information, such as its IP address. Business Operation Support System Baseband Processing Unit The action of transmitting identical traffic on the working and protection channels simultaneously. This downlink channel contains specific parameters needed by a mobile in order that it can identify the network and gain access to it. Typical information includes the LAC (Location Area Code) and RAC (Routing Area Code), the MNC (Mobile Network Code) and BA (BCCH Allocation) list. In the UMTS system, this protocol adapts broadcast and multicast services on the radio interface. See Base Station Identification Universal BBU SubRNCk Backplane type C(2U)
Bootstrap Protocol BOSS BPU Bridge Broadcast Control Channel
Broadcast/Multicast Control BS ID BSBC
Issue 08 (2011-09-30)
29
BSC BSC local switch
See Base Station Controller Indicates that when the caller and the called party of a call are located under the same BSC, voice signals loop from the Abis interface of the BSC to an MS. This means that voice signals are directly switched to the target MS under the BSC instead of through the NSS. The transmission resources of the Ater interface occupied by the call are released, thus saving the transmission resources of the Ater interface.
BSC6000 Local The BSC6000 Local Maintenance Terminal is a component of the LMT software. It Maintenance Terminal adopts GUI to operate and maintain the BSC6000, configure data for the BSC6000, and provide detailed online help. BSIC BSN BSS BSSAP BSSGP BSSGP Virtual Connection BSSMAP BTS BTS local switching See Base transceiver Station Identity Code See Backward Sequence Number See Base Station System See Base Station Subsystem Application Part See Base Station Subsystem GPRS Protocol An end-to-end virtual communication path between remote Network Service user entities. See Base Station Subsystem Management Application Part See Base Transceiver Station When the calling party and called party are served by the same BTS or BTS group, speech signals on the Abis interface loop back to the MS in a BTS or BTS group without passing through the BSC and MSC. The Base Transceiver Station Management (BTSM) is responsible for transferring the RR information (not provided for in the BTS by the RR' protocol) to the BSC. The BS ring network is connected to the BSC for improving the reliability of the network. For details about the BS ring network. See BTS Management
BTS Management BTS ring topology BTSM
Building Integrated In the situation of multiple synchronous nodes or communication devices, one can use Timing Supply System a device to set up a clock system on the hinge of telecom network to connect the synchronous network as a whole, and provide satisfactory synchronous base signals to the building integrated device. This device is called BITS. Busbar BVC An electrical conductor that makes a common connection between several circuits. See BSSGP Virtual Connection
1.3.4 C
C-RNTI C/I ratio CA Cabinet group CAC See Cell RNTI It is the ratio of the strength of a carrier signal to the strength of an interfering signal. Cell Allocation Two or multiple BTS combined cabinets are grouped to serve as one BTS. Call Admission Control
Issue 08 (2011-09-30)
30
Call connection
Completes the establishment and release of various call services, including speech calls, short messages, VGCS/VBS, CS data services, and GPRS/EDGE services. Implements BSSMAP and RR procedures, including system information, paging, immediate assignment, assignment, handover, location update, and A interface circuit management. The set of functions used to process a call. Dropped call rate out of completed sending calls(a sending call drop rate) or out of completed receiving calls(a receiving call drop rate). The CFU service enables the system to transfer incoming calls of a subscriber to the registered FTN or voice mailbox. The call history record (CHR) system is an effective system for quick fault location. It can record and store the faults during calls for each user in a CHR server. If needed you can query the call history records of a specific user on a CHR client to quickly locate the faults. In this kind of test, customers' subjective evaluation is counted as the major factor, to judge the voice quality in the test channels. In the event of a radio link failure, call re-establishment may be attempted (according to the procedure in GSM04.08). Provides the ability to transfer calls from one cordless handset to another or between the base speakerphone and any other registered handset within the system. See Capital Expenditure Money spent to acquire or upgrade physical assets such as buildings and machinery. An analog signal of fixed amplitude and frequency that is combined with a data-carrying signal to produce an output signal suitable for transmitting data. A radio-frequency signal, such as those used with modems and on networks, used to transmit information. A series of components or networks, the output of each of which serves as the input for the next. In a cascading connection, the output of one entity is considered as the input of its next entity. Cascading in this chapter refers to the topology type (chain and tree) of NodeBs.
Call Control Call drop rate Call Forwarding Unconditional Call History Record
Call Quality Test Call re-establishment Call Transfer CAPEX Capital Expenditure Carrier Carrier signal Cascade Cascading
CB Cb Interface CBA CBC CBCH CBE CBQ CBR CBS
See Cell Broadcast The BSC and the CBC communicate with each other over the Cb interface. Cell Bar Access See Cell Broadcast Center See Cell Broadcast Channel Cell Broadcast Entity Cell Bar Qualify See Constant Bit Rate See Cell Broadcast Service
Issue 08 (2011-09-30)
31
CBS SA
A CBS SA is an area where the CBS service is available. Cells have a one-to-one relationship with CBS SAs.
CBT CC CCB CCCH CCP CCS CCTrCH CDMA CDT tRNCing
Cell Broadcast Terminal See Call Control Call Control Block See common Control Channel Communication Control Port See common Channel Signaling Coded Composite Transport Channel See Code Division Multiple Access The CDT tracing (detailed call tracing) is used to trace the following messages: standard interface messages of the UE and messages on the user plane and signaling plane of the UE. See Combining and Distribution Unit Radio network object that can be uniquely identified by a User Equipment from a (cell) identification that is broadcasted over a geographical area from one UTRAN Access Point. A Cell is either FDD or TDD mode. A cell corresponds to a certain radio coverage area. A cell is identified by the Base Station Identity Code (BSIC) or Cell Global Identification (CGI). A cell contains one or several TRX units. Cell breathing refers to the phenomenon that the coverage of the cell varies with the number of users. That is, when the number of users increases, the network load also increases, the coverage of the cell, however, decreases; when the number of users decreases, the network load also decreases, the coverage of the cell, however, increases. The cell broadcast is a Teleservice which enables an Information Provider to submit short messages for broadcasting to a specified area within the PLMN. The Cell Broadcast Centre is the functional entity within the mobile network that is responsible for the generation of cell broadcast information.
CDU Cell
Cell
Cell breathing
Cell Broadcast Cell Broadcast Center
Cell Broadcast Channel Cell Broadcast Channel (CBCH) is a downlink point to multipoint logical channel in a GSM system used to broadcast user information from a service center to mobile stations listening in a given cell area. Cell Broadcast Service Cell Broadcast is designed for simultaneous delivery of messages to multiple users in a specified area.Whereas the Short Message Service (SMS) is a one-to-one and one-to-afew service, Cell Broadcast is one-to-many geographically focused service. It enables messages to be communicated to multiple mobile phone customers who are located within a given part of its network coverage area at the time the message is broadcast. Cell Broadcast is more akin to other mass distribution media such as teletext or Radio Data System (RDS). On Cell Broadcast the GSM operators send different news or data. Often they offer business news, weather forcast and so on.
Issue 08 (2011-09-30)
32
Cell channel
The number of the program channel in a cell. The relation between the cell channels and the program channels is configurable through commands.
Cell Multimedia Broadcast Channel Cell penalty
The CMB bearer on cells, corresponding to the FACH of SCCPCH. It bears different program channels through configurations. If an MS making a call is handed over to a target cell and the handover fails, another handover of the MS to the target cell may be initiated and the handover may fail again. The target cell is penalized in this case. That is, the call is forbidden to be handed over to the target cell within a specified period. When an MS selects a cell as the serving cell, the MS continues to monitor all the BCCH carrier frequencies of the neighbor cells in the cell frequency list indicated by the BCCH system message of the serving cell. The MS compares the reception level in the serving cell and the reception levels of all BCCH carrier frequencies in the cell frequency list. When certain conditions are met, the MS initiates cell reselection to reselect a cell that provides higher quality services. Group RNTI. A newly defined type of UE ID, used in MAC header to identify data on CMBCHs. The cell tracing is used to measure the following two types of messages: common signaling messages on the Iub interface of one or more specified cells and customized messages that contain information about UEs in the cells. An RRC connected mode in which DCCH and, if configured, DTCH are available. DCCH and DTCH are mapped to DCH. An RRC connected mode where neither DCCH nor DTCH is available.
Cell Reselection
Cell RNTI Cell tRNCing
CELL_DCH CELL_PCH
Center (frequency) DA A DA value to the precision of 0.05 ppm that is stored on a static storage and enables value the OCXO to work at 10 MHz within a short period, for example, one month. Each time when the clock module is initialized, the module uses the center DA value as the current DA value before phase-locking and as a criterion for large frequency offset. When exceptions occur to the clock source, the clock module works in free-run mode with the center DA value. After the clock works in locked mode for a period, for example, 7 consecutive days, a new center DA value calculated by weighting the current DA value within this period is written into the storage. Center Processing Unit The CPU is the brains of the computer. Sometimes referred to simply as the processor or central processor, the CPU is where most calculations take place. CES CFU CG Chain Neighbor Cell See Circuit Emulation Service See Call Forwarding Unconditional See Charging Gateway Chain Neighbor Cell is a parameter of the neighbor cell relation property. During the fast movement handover, the MS can be handed over to only the neighbor cells of the serving cell. In addition, the neighbor cells and the serving cell must be configured in chain mode. Generally, the two neighbor cells in the direction of the fast movement of the MS are configured as chain neighbor cells. The configurations depend on the actual conditions.
Issue 08 (2011-09-30)
33
Chanel
A channel is a radio transceiver entity. One timeslot is mapped to one channel. A channel is identified by timeslot data and frequency hopping data. One physical channel is mapped to several logical channels. Element with a GPRS network that consolidates,filters and optimizes CDR (Call Detail Record) prior to their transmission to the Billing Platform. See Call History Record See Circuit Identity Code See Context identifier The Ciphering Key is a variable used in the GSM and GPRS cipher process. A function with which the E1/T1 data can be transmitted through ATM networks. At the transmission end, the interface module packs timeslot data into ATM cells. These ATM cells are sent to the reception end through the ATM network. At the reception end, the interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES technology guarantees that the data in E1/T1 timeslots can be recovered to the original sequence at the reception end. The Circuit Identification Code (CIC) is responsible for assigning a signal to an ISDN or GSM payload channel. The CIC is a 12 bit field in the SS7 protocol. In telecommunications, a circuit switching network is one that establishes a dedicated circuit (or channel) between nodes and terminals before the users may communicate. Each circuit that is dedicated cannot be used by other callers until the circuit is r See Cipher Key Cipher Key Sequence Number Closed Loop Transmit Diversity Mode 1 Jitter of clock source occurs when the clock module detects large frequency offsets continuously for many times. The loss of clock source occurs when the clock module does not detect any pulses of the clock source for a specified interval, for example, 30 seconds. See Connection Management See Compressed mode Cell Multimedia Broadcast See Cell Multimedia Broadcast Channel common Transport Channel Priority Indicator Configuration Management Express Neighbor cells under the same BTS.
Charging Gateway CHR CIC CID Cipher Key Circuit Emulation Service
Circuit Identity Code Circuit Switching
CK CKSN CLD1 Clock source jitter Clock source loss CM CM CMB CMBCH CmCH-PI CME Co-site neighbor cells
Code Division Multiple A technique for spread-spectrum multiple-access digital communications that creates Access channels through the use of unique code sequences. Cold patch A set of files, which are used to overwrite the original files for repairing a deficiency in the software or to add a new feature to a program. The new files take effect after the software is restarted. A cold patch can be installed, uninstalled, or queried. Two or multiple BTS cabinets of the same type are combined to serve as one BTS. Different types of BTS cabinets form a combined group.
Combined cabinet Combined group
Issue 08 (2011-09-30)
34
Combining and Distribution Unit command script
A combiner/divider unit is provided which includes a common output/input port and a plurality of N input/output ports and a plurality of N isolation ports. A command script is a text file. It records a batch of MML commands for a single NE or multiple NEs of the same type. You can execute multiple MML commands by executing a command script. Common Channel Signalling (CCS) is a signalling method where one channel is reserved solely for network management. LNP7, a common channel signaling processing board, is responsible for the processing of SS7 signaling on the A interface. A CCCH is a point-to-multipoint bidirectional control channel. A CCCH is primarily intended to carry signalling information necessary for access management functions. CORBA is the acronym for common Object Request Broker Architecture, OMG's open, vendor-independent architecture and infrastructure that computer applications use to work together over networks. This is a point to multipoint unidirectional channel for the transfer of dedicated user information for all or a group of specified UE (User Equipment).
common Channel Signaling common Channel Signaling Processing Board common Control Channel common Object Request Broker Architecture common Traffic Channel
Complex It is a programmable logic device with complexity between that of FPGAs and PALs, Programmable Logical and architectural features from both. The building block of a CPLD is the macro cell, Device which contains logic implementing disjunctive normal form expressions and more specialized logic operations. Compress The act of reducing the size of a header by removing header fields or reducing the size of header fields. This is done in such a way that a decompressor can re-form the header if its context state is identical to the context state used in compression of the header. Compressed mode Connection Management Connection Request Constant Bit Rate Context In the compressed mode, some timeslots in one or more continuous physical frames do not send data. This mode applies to inter-frequency measurement. A function for the control, provision and maintenance of services offered by the network; for example SMS (Short Message Service), teleservices and location based services. Initiate a request to establish a communication session with a remote system. Constant Bit Rate is a service offered by a network technology such as ATM (Asynchronous Transfer Mode). This is used for real time services such as speech. A bit string that the compressor uses to compress a header and the decompressor uses to decompress a header. It is the uncompressed version of the last header that the compressor sends or the decompressor receives over the link. The context for a packet stream is associated with a CID. In addition, the context for a non-TCP packet stream is associated with a generation. Context identifier A small unique number that identifies the context used to decompress a compressed header. CIDs are carried in full headers or compressed headers.
Issue 08 (2011-09-30)
35
Control Channel Controlling Radio Network Controller Convert Management System
The channel used to transmit digital control information from the base station to a cell phone or vice-versa. The RNC connected to a NodeB is called the CRNC of this NodeB. The Convert Management System is a software item of the LMT software package. It is used to forward the alarm information, the control information, and the status information about the alarm box between the server and the alarm box. The Convert Management System connects to the server through the Ethernet port and communicates with the alarm box through serial ports. In TRX cooperation, the cooperated TRX is an available TRX selected through the TRX cooperation algorithm to replace the original active BCCH TRX. The selected TRX is the new BCCH TRX of the cell. See common Object Request Broker Architecture Connection-Oriented Radio Resource Management See Crystal oscillator The channel composed by two half rate sub-timeslots is called a Couple channel when both sub-timeslots are idle. Connection management Protocol common Pilot Channel See Complex Programmable Logical Device See Center Processing Unit See Call Quality Test See Connection Request See Cyclic Redundancy Code See Controlling Radio Network Controller Cell Reselect Offset An oscillator that produces electrical oscillations at a frequency determined by the physical characteristics of a piezoelectric quartz crystal. See Circuit Switching See Call Transfer See common Traffic Channel A dynamic value written into the DAC by software. During phase locking, the system can adjust the value according to frequency offset until the clock works in locked mode. This value changes with the changes of the signals of the clock source, and it is not stored on a static storage. This instant value is lost after the power-off.
Cooperated TRX
CORBA CORRM COSC Couple CP CPICH CPLD CPU CQT CR CRC CRNC CRO Crystal oscillator CS CT CTCH Current (frequency) DA value
Current active BCCH TRX Cyclic Redundancy Code
Indicates the working BCCH TRX after TRX cooperation. A class of linear error detecting codes which generate parity check bits by finding the remainder of a polynomial division.
Issue 08 (2011-09-30)
36
1.3.5 D
D-BUS DA DAC Data integrity Data Link Connection Identifier Data-BUS Data Agent Digit-Analog Converter The quality of correctness, completeness, wholeness, soundness and compliance with the intention of the creators of the data. The Data Link Connection Identifier identifies an individual user's information stream as well as identifying the connections between terminal equipment and the user equipment. It is possible for multiple DLCI to be supported however; the actual number is implementation specific. The active node transmits the dynamically configured data to the standby node. Daylight Saving Time, an hour earlier than GMT. Distribution Base Station Direct Current Dynamic Channel Configuration Control If the request rate is lower than or equal to this rate, the dynamic allocation algorithm do not work. Dedicated Control Channel See Direct Current Distribution Unit Dedicated Channel See Digital Distribution Frame Digital Data Network See Direct Digital Synthesis De-interleaving: The process of unpermuting the symbols that were permuted by the interleaver. Deinterleaving is performed on received symbols prior to decoding. The areas where terminals cannot transmit signals to a neighboring cell, base station, or repeater. Therefore, in the dead zones, services are unavailable for terminals because the signals between terminals and antennas are blocked by mountains, branches and leaves, or high buildings. The act of restoring the original header. In communications, the means by which a modem converts data from modulated carrier frequencies (waves that have been modified in such a way that variations in amplitude and frequency represent meaningful information) over a telephone line. Data is converted to the digital form needed by a computer to which the modem is attached, with as little distortion as possible. One of a set of destination signalling point polled by the signalling point, the set corresponding to those destination signalling points in the network where congestion is likely to occur. The destination of a message signalling unit (MSU) in network.
Data synchronization Daylight Saving Time DBS DC DCCC DCCC threshold rate DCCH DCDU DCH DDF DDN DDS De-interleaving dead zone
Decompress Demodulation
Destination Signaling Point Destination signalling Point Code
Issue 08 (2011-09-30)
37
Device IP
Device IP refers to the IP address used in the communications between the BSC and other NEs such as the MGW, MSC, and BTS. The device IP serves as the source IP address at the BSC and serves as the destination IP address at the peer NE. The device IP is a virtual IP address. The device IP of an interface board is associated with all the ports on the interface board. All the ports on the interface board can receive and send the packets of device IP. Differential Global Positioning Systems See Dynamic Host Configuration Protocol A compression technique where the compressed value of a header field is the difference between the current value of the field and the value of the same field in the previous header in the same packet stream. By differential coding, the decompressor obtains the value of the field by adding the value in the compressed header to its context.
DGPS DHCP Differential coding
Differentiated Services A service architecture that provides the end-to-end QoS function. It consists of a series of functional units implemented at the network nodes, including a small group of perhop forwarding behaviors, packet classification functions, and traffic conditioning functions such as metering, marking, shaping and policing. DiffServ DiffServ Code Point See Differentiated Services A Differentiated Services (DiffServ) Code Point is a marker in the header of each IP packet that prompts network routers to apply differentiated grades of service to various packet streams. It is specified by the DiffServ policy proposed by the IETF (Internet Engineering Task Force). This allows Internet and other IP-based network service providers to offer different levels of service to customers. A type of equipment used between the transmission equipment and the exchange with transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection, cable patching, and test of loops that transmitting digital signals. The direct current distribution unit that distributes the -48 V DC received from an external power source to relevant components.
Digital Distribution Frame Direct Current Distribution Unit
Direct Digital Synthesis Direct digital synthesis (DDS) is a powerful technique used in the generation of radio frequency signals for use in a variety of applications from radio receivers to signals generators and many more. The technique has become far more widespread in recent years with the advances being made in integrated circuit technology that allow much faster speeds to be handled which in turn enable higher frequency DDS chips to be made. Although often used on its own, Direct Digital Synthesis is often used in conjunction with indirect or phase locked loop synthesizer loops. By combining both technologies it is possible to take advantage of the best aspects of each. In view of the fact that integrated circuits are now widely available, this makes them easy to use. Direct-Sequence Code Division Multiple Access Direct sequence spread spectrum, also known as direct sequence code division multiple access (DS-CDMA), is one of two approaches to spread spectrum modulation for digital signal transmission over the airwaves. In direct sequence spread spectrum, the stream of information to be transmitted is divided into small pieces, each of which is allocated across to a frequency channel across the spectrum. A data signal at the point of transmission is combined with a higher data-rate bit sequence (also known as a chipping code) that divides the data according to a spreading ratio. The redundant chipping code helps the signal resist interference and also enables the original data to be recovered if data bits are damaged during transmission.
Issue 08 (2011-09-30)
38
Disconnected Mode Discontinuous Reception
Disconnected Mode(DM) is transmitted from a secondary station to indicate it is in disconnected mode(non-operational mode). Discontinous Reception (DRX) is a method used in mobile communication to conserve the battery of the mobile device. The mobile device and the network negotiate phases in which data transfer happens. During other times the device turns its receiver off and enters a low power state. Discontinuous transmission (DTX) is a method of momentarily powering-down, or muting, a mobile or portable wireless telephone set when there is no voice input to the set. This optimizes the overall efficiency of a wireless voice communications system. Downlink See Data Link Connection Identifier See Disconnected Mode Dual-density main processing unit of BTS3002E and BTS3006C. Distributed Object-oriented Programmable Realtime Architecture The angle between the direction with maximum radiation and the horizon. The smaller the width of the lobe on the vertical plane, the faster attenuation of signals that deviate from the main beam. In this situation, it will be easier to control the coverage by adjusting the downtilt. To direct the main lobe to the ground, you must adjust the downtilt. Downlink Power Balance See Destination signalling Point Code RNC Data Processing Unit REV:b Directed Retry Decision The role of the drift RNC is to support the serving RNC with radio resources for the mobile terminal connection in cells controlled by the drift RNC. In this kind of test, tests are made to simulate the service for users when they are moving. See Drift Radio Network Controller Drift Radio Network System See Discontinuous Reception Dry contact is a type of passive switch that has two states: open and closed. The two contacts are not distinguished by polarity. Thus, the two contacts can be used interchangeably. The common dry contact signals are the outputs of switches, buttons, sensors, relays, and dry finger pipe. See Direct-Sequence Code Division Multiple Access See DiffServ Code Point Distant Supported Codec Set See Destination Signaling Point See Daylight Saving Time See Drive Test
Discontinuous Transmission DL DLCI DM DMCM DOPRA Downtilt
DPB DPC DPUb DRD Drift Radio Network Controller Drive Test DRNC DRNS DRX Dry contact
DS-CDMA DSCP DSCS DSP DST DT
Issue 08 (2011-09-30)
39
DTCB handover
DTCB handover is a special method of determining the boundary between an overlaid subcell and an underlaid subcell for the enhanced dual-band network. The coverage area of the overlaid subcell is determined through the DTCB threshold, the DTCB hysteresis, and the difference between the signal strength of the serving cell and that of the neighbor cell. Dedicated Traffic Channel See Dual-Tone Multi-frequency Dual-density main processing unit of BTS3012 and BTS3012AE. Coverage Prediction by DT Data See Discontinuous Transmission The BAM has two servers. One BAM server works in active mode and the other works in standby mode. When the active BAM server breaks down because of any hardware fault or irrecoverable software fault, the standby BAM server is switched over to work in active mode and resumes the functions. In mobile phones, dual band refers to functionality that allows a cellphone to support two frequency bands out of the four major GSM (or TDMA) bands. This is important because different countries peg the allowed transmission frequency at different values. In telephone systems, multifrequency signaling in which standard set combinations of two specific voice band frequencies, one from a group of four low frequencies and the other from a group of four higher frequencies, are used. A transmission line device allowing the same antenna to be used for transmission and reception. A transmission equipment used in synchronised digital network to cross connect nx64 kbps channels between 2048 kbps access ports. The DCC can realise unidirectional, bidirectional broadcast, cross connections at 64 kbps, n x 64 kbps, CAS ABCD bits and National space bits. Any channel out of 30 PCM channels in a single stream of 2 MB can be connected to any other channel of any other stream.
DTCH DTMF DTMU DTP DTX Dual BAM servers
Dual-band network
Dual-Tone Multifrequency Duplexer DXC
Dynamic Host Dynamic Host Configuration Protocol (DHCP) is a client-server networking protocol. Configuration Protocol A DHCP server provides configuration parameters specific to the DHCP client host requesting, generally, information required by the host to participate on the Internet network. DHCP also provides a mechanism for allocation of IP addresses to hosts.
1.3.6 E
E-AGCH E-DCH E-DCH active set E-DCH MAC-d flow E-DCH Absolute Grant Channel See Enhanced Dedicated Channel A set of the cells that carry E-DCH for one UE. MAC-es PDUs that carry MAC-d data sharing the same traffic characteristics and that can be multiplexed with MAC-es PDUs of the same type or other MAC-d flows on MACe. E-DCH Dedicated Physical Control Channel E-DCH Dedicated Physical Data Channel E-DCH HARQ Acknowledgement Indicator Channel
E-DPCCH E-DPDCH E-HICH
Issue 08 (2011-09-30)
40
E-RGCH E-TFCI Early Classmark Sending Control Eb/N0
E-DCH Relative Grant Channel E-DCH Transport Format Combination Indicator The early classmark sending control (ECSC) indicates whether the MSs in a cell use early classmark sending. Ratio of bit energy to noise spectral density Desired SNR for demodulating transmit signals. The values in the uplink and in the downlink are different.
Ec/N0
Ratio of received energy per chip to noise spectral density The CPICH Ec/N0 is identical to each RSSI carried by CPICH RSCP/UTRA. Measurement can be performed on the primary CPICH.
ECSC EDGE EDU EF EFR EIa EIb EIR ElectroMagnetic Compatibility
See Early Classmark Sending Control See Enhanced Data rates for GSM Evolution Enhanced Duplexer Unit See Expedited Forwarding See Enhance Full Rate speech codec Electrical Interface A Electrical Interface B See Equipment Identity Register Electromagnetic compatibility is the condition which prevails when telecommunications equipment is performing its individually designed function in a common electromagnetic environment without causing or suffering unacceptable degradation due to unintentional electromagnetic interference to or from other equipment in the same environment. A device that suppresses or reduces the level of EMI/RFI emitted by electrical or electronic equipment. A 32-bit number assigned by the mobile station manufacturer, uniquely identifying the mobile station equipment.
Electromagnetic interface filter Electronic Serial Number
Electrostatic induction The charges on the conductor are redistributed and then generated on the surface in an elctrostatic field. Element Management System EMC EMI EMI filter eMLPP EMS EMU Enhance Full Rate speech codec A system used to manager the network elements. See ElectroMagnetic Compatibility See External Machine Interface See Electromagnetic interface filter See enhanced Multi-Level Precedence and Pre-emption service See Element Management System See Environment Monitoring Unit An alternative voice codec that provides improved voice quality in a GSM network.
Issue 08 (2011-09-30)
41
Enhanced Data rates for GSM Evolution Enhanced Dedicated Channel enhanced Multi-Level Precedence and Preemption service
EDGE allows higher data transmission speeds based on the GSM standard. A new type of dedicated transport channel or an enhancement to an existing type of dedicated transport channel. This service has two parts - precedence and pre emption. Precedence involves assigning a priority level to a call in combination with fast call set-up. Pre-emption involves the seizing of resources, which are in use by a call of a lower precedence, by a higher level precedence call in the absence of idle resources. Pre-emption can also involve the disconnection of an on-going call of lower precedence to accept an incoming call of higher precedence. The Environment Monitoring Unit (EMU) uses sensors to monitor the temperature, humidity, smoke, and intrusion in the environment in real time. The environment can be automatically monitored according to the preset value and alarms are automatically generated when the preset threshold is exceeded. See Erasable Programmable Logic Device The EIR in the GSM system is the logical entity which is responsible for storing in the network the International Mobile Equipment Identities (IMEIs), used in the GSM system. A fully-activated 12.2 kbit/s AMR speech service is called a reference service. The uplink interference raised and the downlink power consumed by the reference service are equal to those by an equivalent user respectively. A programmable logic array designed to perform a user-erasable programmable function. A unit of measurement of telephone traffic. It is equal to one hour of conversation (3,600 seconds or 36 CCS). It also specifies the approximate number of trunks in use; for example, if the traffic in a call center is 8.5 Erlangs in one hour, more than 8 trunks were used in that hour. Indicates the relation among the number of common channels, call loss rate, and traffic volume in busy hours. The ERLANG B is developed from the ERLANG call loss formula. See Extend Signalling Link See Electronic Serial Number European Telecommunication Standards See European Telecommunications Standards Institute Standards-setting body in Europe. Also the standards body responsible for GSM.
Environment Monitoring Unit
EPLD Equipment Identity Register Equivalent number of users Erasable Programmable Logic Device Erlang
ERLANG B
ESL ESN ETS ETSI European Telecommunications Standards Institute Event alarm
Alarm caused by a predefined event, such as congestion, that happens when the equipment is running. The alarm represents an instantaneous status of the system and the status may not be a fault. Some event alarms are generated repeatedly and regularly.
Expedited Forwarding Expedited Forwarding (EF) is a service defined under the Differentiated Services framework. Extend Signalling Link The ESL is responsible for transmitting the Abis timeslot dynamic connection message.
Issue 08 (2011-09-30)
42
Extensible Markup Language
A specification developed by the W3C. XML is a pared-down version of SGML, designed especially for Web documents. It allows designers to create their own customized tags, enabling the definition, transmission, validation, and interpretation of data between applications and between organizations. The extension cabinet in combined cabinets is the cabinet except for the main cabinet in the combined cabinets. The extension cabinet group is the cabinet group except for the main cabinet group. The extension cell can work beyond the value of the maximum Timing Advance (TA), so the coverage radius of a cell is greater than 35 km. The subracks are connected in star topology. The subrack connected to the main subrack is called extension subrack. The interface used between the SMSC System and other computer systems and applications. The logical network between the OMU and the LMT/M2000. It is used to connect the LMT/M2000 to the OM subsystem. The virtual IP address used for the communication between the BAM and the LMT.
Extension cabinet Extension cabinet group Extension cell Extension subRNCk External Machine Interface External network External virtual IP address
1.3.7 F
FABS FACCH FACH FAI FAM FAQ Fast Ethernet port Fast pull-in mode See Flexible Abis Fast Associated Control Channe Forward Access Channel See First Article Inspection See Front Administration Module Frequently Asked Question The port that provides a rate of 100 Mbit/s. When the external reference clock source is operational, the system adjusts its local oscillator by a large step size, depending on the reference clock source. The adjustment aims to enable the system to work in slow pull-in mode as soon as possible. In fast pull-in mode, the frequency offset is compensated with a single step as required to get the system to work in slow pull-in mode or locked mode as soon as possible. Fault alarm Alarm caused by hardware faults, for example, board failure, or by the abnormity of major functions. After handling, a fault alarm can be cleared, upon which the NE reports a recovery alarm. Fault alarms are of higher severity than event alarms. Fan Control Board See Federal Communications Commission Frequency Correction Channel,The frequency correction channel carries information for frequency correction of the mobile station. See Frequency Division Duplex
FCB FCC FCCH FDD
Issue 08 (2011-09-30)
43
FDMA FE FE Federal Communications Commission Feed line
See Frequency Division Multiple Access Fast Ethernet See Fast Ethernet port Federal Communications Commission is a U.S. government agency that supervises, licenses, and controls electronic and electromagnetic transmission standards. 1. A radio frequency transmission line interconnecting an antenna and a transmitter or receiver. 2. For an antenna comprising more than one driven element, a radio frequency transmission Line interconnecting the antenna input and a driven element. See Frame Error Rate Fast Fourier Transform Algorithm RNC packet over electronic 8-port FE or 2-port GE ethernet Interface unit REV:a See Frequency Hopping See Frequency Hopping Bus A client-server protocol which allows a user on one computer to transfer files to and from another computer over a TCP/IP network. Also the client program the user executes to transfer files.
FER FFT FG2a FH FH-BUS File Transfer Protocol
First Article Inspection A First Article Inspection Report is a requirement placed on the supplier by the customer. The report documents and certifies that each first article unit delivered to the buyer was produced and inspected in accordance with the buyers specifications. The report includes all physical, material, and chemical test data associated with the part. These reports are provided to the buyer and kept on file by the supplier for a minimum of seven years or as required by the buyer. Fixed IP address The IP addresses that are permanently bound with the Ethernet adapters of the active and the standby nodes. The fixed IP addresses are used for the heartbeat communication between the nodes. Neither the host nor the LMT can access the fixed IP addresses. Flex Abis Indicates the timeslot assignment mode of the Abis interface. The channel of the Um interface and the timeslot of the Abis interface are not bound any more. The timeslot of the Abis interface is dynamically assigned for each call. Dynamic MAIO Flexible Abis refers to the dynamic binding of transmission resources on the Abis interface and on the Um interface. A set of mechanisms used to prevent the network from being overloaded by regulating the input rate transmissions Fan Environment Monitor See Frame Number A Forced Switch is when the network operator forces the network to use the protection resources instead of the working resources, or vice-versa, regardless of the state of the resources.
Flex MAIO Flexible Abis Flow control FMUA FN Force Switch
Issue 08 (2011-09-30)
44
Forced Soft Handover ForceSHO Forward Sequence Number FP FR Frame Error Rate Frame Number Frame Protocol Frame Relay
In the CELLID+RTT positioning method, the RNC forcibly triggers soft handover by lowering the threshold of 1A event during the positioning. See Forced Soft Handover A field in a signal unit used to identify the transmitted message signal units. See Frame Protocol See Frame Relay The number of frames in error divided by the total. These frames are usually discarded, in which case this can be called the Frame Erasure Rate. The number used to identify a frame. A protocol used in UMTS on the Iur and Iub interfaces to frame channels supported between the SRNC (Serving Radio Network Controller) and UE (User Equipment). Frame relay, also found written as frame-relay, is an efficient data transmission technique used to send digital information quickly and cheaply to one or many destinations from one or many end-points. commonly implemented for voice and data as an encapsulation technique, used between local area networks (LANs) over a wide area network (WAN). Each end-user gets a private line (or leased line) to a frame relay node. An operating condition of a clock in which its local oscillator is not locked to an external synchronization reference, and is using no storage techniques to sustain its accuracy. Frequency division duplex (FDD) is the application of frequency-division multiple access to separate outward and return signals. The uplink and downlink sub-bands are said to be separated by the "frequency offset". Frequency Division Multiple Access is a technique in which multiple users of a radio system are separated in the frequency domain. The repeated switching of frequencies during radio transmission according to a specified algorithm, to minimize unauthorized interception or jamming of telecommunications. When baseband frequency hopping and antenna hopping are enabled, a large amount of data exchange is performed between different TRXs in the cabinet. Frequency hopping bus is introduced to facilitate the data exchange. When the antenna hopping function is realized, each TRX sends the TX frequency, TX ID, and data of the current frame to the frequency hopping bus during timeslot interval. The TRX receives the corresponding frequency and data from the frequency hopping bus, and then configure the RF based on the frequency. Then, the RF sends the data to the MS over the Um interface. When the transmit source of the radio wave is far from the receive party, the wavelength is long and the frequency is low. When the transmit source is close to the receive party, the wavelength is short and the frequency is high. The BTS carrying the serving cell can calculate the frequency offset (indicated by f) through the signals trasmitted by the moving MS. If the absolute value of f is great, you can infer that the MS is moving fast. If f is a positive number, you can infer that the MS is moving toward the BTS. If f is a negative number, you can infer that the MS is moving away from the BTS. A function with which ATM cells are transmitted through some of the 32 E1/T1 timeslots. ATM cells are mapped to some of the E1/T1 timeslots, instead of all of the timeslots. At the peer end, the ATM cell stream is recovered from these E1/T1 timeslots. The timeslots that are unavailable for ATM cell transmission can transmit other information.
Free-run mode Frequency Division Duplex Frequency Division Multiple Access Frequency Hopping Frequency Hopping Bus
Frequency offset
FRNCtional ATM
Issue 08 (2011-09-30)
45
Front Administration Module FS FSN FTP FUC Full header Full-rate version 1 Full-rate version 2 Full-rate version 3
Front Administrator Module, including the switching subsytem and the service processing subsystem. It is also called the main system of RNC. See Force Switch See Forward Sequence Number See File Transfer Protocol Frame Unit Controller An uncompressed header that updates or refreshes the context for a packet stream. It carries a CID. For a non-TCP packet stream, a full header also carries a generation. FR data (with the rate of 13 kbit/s) EFR data (with the rate of 12.2 kbit/s) FAMR data (with the rate ranging from 4.75 to 12.2 kbit/s)
1.3.8 G
GAI Gain (of an antenna) Gateway GPRS Support Node Geographical Area Identifier Ratio of the radiation intensity, in a given direction, to the radiation intensity that would be obtained if the power accepted by the antenna was radiated isotropically. The Gateway GPRS Support Node supports the edge routing function of the GPRS network. To external packet data networks the GGSN performs the task of an IP router. Firewall and filtering functionality, to protect the integrity of the GPRS core network, are also associated with the GGSN along with a billing function. The Gateway Mobile Location Centre contains functionality required to support LCS (LoCation Services). In one PLMN (Public Land Mobile Network), there may be more than one GMLC. The GMLC is the first node an external LCS client accesses in a GSM or UMTS network. The GMLC may request routing information from the HLR (Home Location register) or HSS (Home Subscriber Server). After performing registration authorization, it sends positioning requests to either the VMSC (Visited Mobile Switching Centre), SGSN (Serving GPRS Support Node) or MSC (Mobile Switching Centre) Server and receives final location estimates from the corresponding entity. A type of Mobile Switching Center (MSC), which requests the routing information about a called subscriber and performs interconnection and settlement between networks.
Gateway Mobile Location Center
Gateway Mobile Switching Center
Gaussian Minimum A modulation mode used in the GSM system. In this modulation mode, a Gaussian low Shift-frequency Keying pass premodulation filter is added before the MSK modulator. GMSK improves the spectrum utilization in the digital mobile communication. Gb Interface Gb Interface Processing Unit GBAM GBCR GBIU GBP When the built-in PCU is used, the BSC provides the Gb interface to enable the communication between the BSC and the SGSN. The Gb interface is a GPRS interface which is located between the SGSN (Serving GPRS Support Node) and the PCU (Packet Control Unit). GSM Back Administration Module GSM BSC Control Processing RNCk See Gb Interface Processing Unit Power Requirement for GBR
Issue 08 (2011-09-30)
46
GBR GBSR GByte GCGa GCUa GDOP GDPUC GE GE
See Guaranteed Bit Rate GSM BSC Service Processing RNCk Gigabyte RNC General Clock with GPS Card REV:a RNC General Clock Unit REV:a Geometric Dilution Of Precision GSM Data Processing Unit for CS service Gigabit Ethernet The IEEE standard dubbed 802.3z, which includes support for transmission rates of1 Gbps (gigabit per second)--1,000 Mbps (megabits per second)--over an Ethernet network. GSM E1/T1 High level Data Link Control Unit for aBis GSM E1/T1 Interface Unit for A GSM E1/T1 Interface Unit for aBis GSM E1/T1 Interface Unit for Pb GSM E1/T1 Interface Unit for aTer A mobile data service available to users of GSM mobile phones. It is often described as "2.5G", that is, a technology between the second (2G) and third (3G) generations of mobile telephony. A number that is incremented whenever the context with a specified CID changes. A generation is specific for a non-TCP packet stream and carried by a full or compressed non-TCP header. Each new version of the context with a specified CID is associated with a generation.
GEHUB GEIUA GEIUB GEIUP GEIUT General Packet Radio Service Generation
GENEX U-Net GEPS GEPUG GERAN GEXUB GFGUA GFGUB GFGUG GGCU GGSN GHz GLObal NAvigation Satellite System
The GENEX U-Net is a radio network planning tool developed by Huawei and is widely used in many commercial deployments. GSM Extended Processing SubRNCk GSM E1/T1 Packet Unit for Gb See GSM/EDGE Radio Access Network GSM E1/T1 interface eXtensible Unit for aBis GSM Fast ethernet and Gigabit ethernet Unit for A GSM Fast ethernet and Gigabit ethernet Unit for aBis GSM Fast ethernet and Gigabit ethernet Unit for Gb GSM General Clock Unit See Gateway GPRS Support Node Gigahertz The Global Navigation Satellite System (GLONASS) is based on a constellation of active satellites which continuously transmit coded signals in two frequency bands, which can be received by users anywhere on the earth.
Issue 08 (2011-09-30)
47
Global Positioning System Global System for Mobile communications Global Title GLONASS GMLC GMPS GMSC GMSK GMSK modulation mode GMT GOGUA GOGUB GOIUA GOIUB GOIUP GOIUT GOMU GOPT GoS GOUa GOXUB GPRS
A satellite-based global navigation system that consists of a constellation of 24 satellites in orbit 11,000 nmi above the Earth, several on-station (i.e., in-orbit) spares, and a ground-based control segment. A second generation digital cellular telecommunication system which was first planned in the early 1980s. A global title is a unique address which refers to only one destination, though in practice destinations can change over time. See GLObal NAvigation Satellite System See Gateway Mobile Location Center GSM Main Processing SubRNCk See Gateway Mobile Switching Center See Gaussian Minimum Shift-frequency Keying Gaussion Minimum Shift Keying modulation mode. See Greenwich Meridian Time GSM Optic Gigabit ethernet Unit for A GSM Optic Gigabit ethernet Unit for aBis GSM Optic Interface Unit for A GSM Optic Interface Unit for aBis GSM Optic Interface Unit for Pb GSM Optic Interface Unit for aTer GSM Operation and Maintenance Unit See Local Optical Interface Board See Grade of Service RNC 2-port packet over Optical GE ethernet Interface Unit REV:a GSM Optic interface eXtensible Unit for aBis See General Packet Radio Service
GPRS Tunneling GTP is the defining IP protocol of the GPRS core network. Primarily it is the protocol Protocol for User Plane which allows end users of a GSM or WCDMA network to move from place to place while continuing to connect to the Internet as if from one location at the Gateway GPRS Support Node (GGSN). It does this by carrying the subscriber's data from the subscriber's current Serving GPRS Support Node (SGSN) to the GGSN which is handling the subscriber's session. GPS GPS antenna system GPS Network Synchronization See Global Positioning System A system that provides the GRU suite with the location information of the GPS satellite system and synchronization clock signals. Each BTS is installed with a GPS, which implements the synchronization of the entire network through satellite.
Issue 08 (2011-09-30)
48
Grade of Service
Grade of Service defines the quality of a telephone service in terms of a user receiving a network busy signal.
Graphic User Interface A visual computer environment that represents programs, files, and options with graphical images, such as icons, menus, and dialog boxes on the screen. The user can select and activate these options by pointing and clicking with a mouse or, often, with the keyboard. A particular item (such as a scroll bar) works the same way to the user in all applications, because the graphical user interface provides standard software routines to handle these elements and report the user's actions (such as a mouse click on a particular icon or at a particular location in text, or a key press); applications call these routines with specific parameters rather than attempting to reproduce them from scratch. Greenwich Meridian Time GSCU GSM GSM security context Greenwich Meridian Time GSM Switching and Control Unit See Global System for Mobile communications A state established between a UE and a serving network domain as a result of the execution of GSM AKA. In this state, both ends store GSM security context data. The data consists at least of GSM cipher Kc and cipher key sequence number (CKSN). A GSM radio access network that supports the EDGE (Enhanced Data rates for Global Evolution) modulation technique. It has been specified to connect the A , Gb and Iu interfaces to the CN (Core Network). The architecture allows two BSSs (Base Station Subsystems) to be connected to each other. See Global Title GSM TransCoder SubRNCk GSM Transmission and Timing and Management Unit for BBU GSM TDM switching Network Unit See GPRS Tunneling Protocol for User Plane The minimum bit rate for the RNC to adjust. It is contained in the RAB assignment message that the CN sends to the RNC. See Graphic User Interface GSM eXtensible Processing Unit for Computation service GSM eXtensible Processing Unit for Main service GSM eXtensible Processing Unit for Transmission
GSM/EDGE Radio Access Network
GT GTCS GTMU GTNU GTP-U Guaranteed Bit Rate GUI GXPUI GXPUM GXPUT
1.3.9 H
Half rate traffic The half-rate service is a service where the speech encoding rate is reduced to half of the full-rate speech encoding rate through a new speech coding algorithm. If the half-rate service is enabled, the physical channel carrying the service of one MS is able to bear the services of two MSs. An original configuration is generated in data configuration. This configuration can be dynamically adjusted by the resource management module. HR data (with the rate of 5.6 kbit/s). Reserved for protocols.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 49
Half static Half-rate version 1 Half-rate version 2

Issue 08 (2011-09-30)
Half-rate version 3 Handover Hard Disk
HAMR data (with the rate ranging from 4.75 to 7.4 kbit/s). The transfer of a user's connection from one radio channel to another (can be the same or different cell). A rigid magnetic disk fixed permanently within a drive unit and used for storing computer data. Hard disks generally offer more storage and quicker access to data than floppy disks do. A handover, is the process in which a cellular phone is handed from one cell to the next in order to maintain a radio connection with the network. A hard handover results in the radio connection being broken between the network and the mobile, before a new radio connection is established with the network in the target cell. Hard handovers usually require a change of frequency. The hardware configuration of the BSC in which the GBAM is configured to establish the communications between the BSC and the LMT. The number of BSC cabinets and subracks varies depending on the the capacity requirements of the BSC. The hardware configuration of the BSC in which the GOMU board is configured to establish the communications between the BSC and the LMT. The number of BSC cabinets and subracks varies depending on the the capacity requirements of the BSC. See Hybrid Automatic Repeat Request One HARQ profile consists of a power offset attribute and a maximum number of retransmissions. NodeB HSDPA Baseband processing and Interface unit NodeB HSDPA Supported Baseband Unit Header Compression See Hierarchical Cell Structure See Hard Disk See High-level Data Link Control High speed Digital Subscriber Line Home Environment The heartbeat is messages without responses. Both the active and the standby BAM servers send the heartbeat periodically. The dual-BAM-server system monitors the heartbeat to ensure that the active and the standby BAM servers work in proper status. Huawei Enhanced Radio Technology HSL Foundation Component See Hard Handover This is a term typically used to describe the priority of cells within a mixed environment. That is when Macro, Micro, and Pico cells may be viewed as candidates for cell reselection the priority described by the HCS will be used in the associated calculations. High-Speed Circuit-Switched Data (HSCSD) is circuit-switched wireless data transmission for mobile users at data rates up to 38.4 Kbps.
Hard Handover
Hardware Configuration Type A Hardware Configuration Type B HARQ HARQ profile HBBI HBBU HC HCS HD HDLC HDSL HE Heartbeat
HERT HFC HHO Hierarchical Cell Structure High Speed Circuit Switched Data
Issue 08 (2011-09-30)
50
High Speed Downlink Packet Access
A modulating-demodulating algorithm put forward in 3GPP R5 to meet the requirement for asymmetric uplink and downlink transmission of data services. It enables the maximum downlink data service rate to reach 14.4 Mbit/s without changing the WCDMA network topology. A general-purpose data link control protocol defined by ISO for use on both point-topoint and multipoint (multidrop) data links. It supports full-duplex, transparent-mode operation. It is used extensively in both multipoint and computer networks. See Handover If the reference clock source is faulty (loss or unreasonable offset) during locking, the system starts to work in hold mode. In this mode: l The system works at the frequency (usually the center frequency) before the hold mode is started. The system works in pull-in mode after the reference clock source comes back to normal. The system starts to work in fast pull-in mode to avoid abrupt frequency change if the source is recovered in a few days.
High-level Data Link Control HO Hold mode
l Hot patch
A patch that is used to repair a deficiency in the software or add a new feature to a program without restarting the software and interrupting the service. For the equipment using the built-in system, a hot patch can be loaded, activated, confirmed, deactivated, deleted, or queried. A cell that has high traffic and a large quantity of users High Speed Dedicated Physical Control Channel High Speed Downlink Shared Channel High Speed Physical Downlink Shared Channel High Speed Shared Control Channel See High Speed Circuit Switched Data See High Speed Downlink Packet Access The cells in which the HSDPA related resources are configured, such as HSDPA power resource and HSDPA code resource. The cells through which the HSDPA user's data is transmitted. Each active HSDPA user has only one HSDPA serving cell at one time. High-level Script Language Hopping Sequence Number High Speed Uplink Packet Access See Hyper Text Markup Language
Hot Spot HS-DPCCH HS-DSCH HS-PDSCH HS-SCCH HSCSD HSDPA HSDPA cell HSDPA Serving cell HSL HSN HSUPA HTML
HUAWEI Local HUAWEI Local Maintenance Terminal includes the BSC6000 Local Maintenance Maintenance Terminal Terminal, Site Maintenance Terminal System, Convert Management System, Performance Browser Tool, LMT Service Manager, and Local Maintenance Terminal. It performs the operation and maintenance of the BSC6000. HULP HW
Issue 08 (2011-09-30)
NodeB HSDPA supported Uplink Processing Unit High Way

HW II HW III HWII Channel Allocation Algorithm Hybrid Automatic Repeat Request
It is an algorithm used for channel allocation and power control. It is an algorithm used for power control. In HWI channel allocation algorithm, the channels are assigned by sequence; in HWII channel allocation algorithm, the channels are assigned by priority. A multi-instance Stop-and-Wait (SAW) protocol. The number of HARQ processes is 4 for a 10 ms TTI and 8 for a 2 ms TTI. One HARQ entity handles the hybrid ARQ functionality for one user. One HARQ entity is capable of supporting multiple instances (HARQ process) of stop and wait HARQ protocols. There should be one HARQ process per HS-DSCH per TTI. During retransmission, the UE employs soft combining, that is, it combines soft information from previous transmission attempts with the latest transmission to increase the probability of successful decoding.
Hyper Text Markup Language
Hypertext Mark-up Language (HTML). A Standard Generic Mark-up Language used for WWW documents. Defined by IETF RFC 1866 (Version 2).
1.3.10 I
IAC IASU IBBS ICM ID identity IDNNS IE IEC IFFT IK IMA IMEI IMSI Inactive process Inband signaling Incorrect decompression Intelligent Access Control Isite Access SDH Unit Integrated Backup Battery System Initial Codec Mode See identity The collective aspect of the set of characteristics by which a thing is definitively recognizable or known. Intra Domain NAS Node Selection See Information Element See International Electrotechnical Commission Inverse Fast Fourier Transform Algorithm See Integrity Key See Inverse Multiplexing over ATM See International Mobile Equipment Identity See International Mobile Subscriber Identity HARQ process for which scheduling grants are not applicable, that is, in which scheduled data cannot be sent. It is the signaling transferred by special bits in the speech stream. A situation where a decompressed header is different from the header before compression. Usually, incorrect decompression is due to context mismatch between the compressor and decompressor or due to bit errors during transmission of the compressed header.
Issue 08 (2011-09-30)
52
Information Element
An Information Element is a group of information which may be included within a signalling message or data flow which is sent across an interface. Examples may include QoS (Quality of Service) definitions, setup parameters, user identifiers etc. The initial DA value is the calibrated center frequency DA value preset in a board before its delivery. It is stored on the static storage. When the system is started for the first time, the center frequency DA value is written into the configuration file as the initial DA value. The inner container, containing all the function modules, is the main component of the BTS3001C. It is located in the sun screening covers. A test that is performed to check whether the cabinet is insulated from the earth by measuring the resistance between the cabinet and the earth when the multimeter is set to the megaohm range. This test helps to ensure that the required insulation parts are installed and are intact. Integrated Services Digital Network (ISDN) is comprised of digital telephony and datatransport services offered by regional telephone carriers. ISDN involves the digitization of the telephone network, which permits voice, data, text, graphics, music, video, and other source material to be transmitted over existing telephone wires. The ISDN User Part (ISUP), a key protocol in the SS7/C7 signalling system, defines the protocol and procedures used to set-up, manage, and release trunk circuits that carry voice and data calls over the public switched telephone network (PSTN) between different switches. A 128bit number used to protect the integrity of information passing between the RNC (Radio Network Controller) and the UE (User Equipment) in UMTS . A cell that has partially overlapping coverage with the serving cell and uses a different frequency from that of the serving cell.
Initial DA value
Inner container Insulation test
Integrated Services Digital Network
Integrated Services Digital Network User Part Integrity Key Inter-frequency neighboring cell
Interference Rejection Interference Rejection Combining (ICC) is an improved RF algorithm. It helps increase Combining the anti-interference capability and the speech quality. Interleaving A process of systematically changing the bit sequence of a digital signal, usually as part of the channel coding, in order to reduce the influence of error bursts that may occur during transmission. The logical network between the OMU and the FAM. It is used for the communication between the OMU and the FAM. The virtual IP address used for the communication between the BAM and the host. The International Electrotechnical Commission (IEC) is an international and nongovernmental standards organization dealing with electrical and electronical standards. The International Mobile Equipment Identity (IMEI) is a number unique to every GSM and UMTS mobile phone. It is usually found printed on the phone underneath the battery and can also be found by dialing the sequence *#06# into the phone. In the GSM system, the IMSI is a unique identifier allocated to each mobile subscriber. The IMSI consists of a Mobile Country Code (MCC), a Mobile Network Code (MNC), and a Mobile Station Identification Number (MSIN).
Internal network Internal virtual IP address International Electrotechnical Commission International Mobile Equipment Identity International Mobile Subscriber Identity
Issue 08 (2011-09-30)
53
International Telecommunication Union Internet Protocol
A United Nations agency, one of the most important and influential recommendation bodies, responsible for recommending standards for telecommunication (ITU-T) and radio networks (ITU-R). Internet Protocol is a standardized method of transporting information across the Internet in packets of data. It is often linked to Transmission Control Protocol, which assembles the packets once they have been delivered to the intended location. A table that implements protocol termination and conversion through the transmission interface board.The Interworking tables consist of the uplink table and downlink table.
Interworking
Interworking Function The Interworking Function is used to provide circuit switched data services when connecting a cellular network to a PSTN. It is comprised of rate adapters, modems and fax adapters. Intra-frequency neighboring cell Inverse Multiplexing over ATM A cell that has partially overlapping coverage with the serving cell. In addition, this cell and the serving cell use the same frequency. Inverse Multiplexing over ATM. With this function, the transmisstion end inversely multiplexes the ATM cells on a high speed transport link to multiple low speed ATM circuits, and the reception end combines the low speed ATM circuits back into a high speed logical path. This task is performed to trace a specified number of calls which access a specified cell continuously. The number of calls can be defined when the task is started. The number of calls can be set when the task is started. The messages during the call procedure are traced. IP IP interface board IP over ATM IP Path See Internet Protocol The RNC has three types of IP interface board: WEIE, WFIE, and WFEE. The NodeB has only one such board, that is, the NUTI. Classical IP over ATM protocols are used to carry the IP packets over the ATM transport network. IP path is a logical link with virtual bandwidth. The logical link is carried on the physical link in the IP network. IP path is a mechanism to perform access control for transmission resources. IP performance monitor effectively monitors the transport network by timely and quickly monitoring the QoS of the bearer network. IP performance monitor requires the support of the BSC and the BTS. See IP Performance Monitor IP protocol refers to a protocol suite consisting of a series of standards that enables a data packet to be transmitted to its destination through the Internet. IP protocol provides a connectionless data packet transmission mechanism, shields physical network transmission, addresses IP, and selects routes. IP Security provides a framework of open standards dealing with data confidentiality, integrity, and the authentication between participating hosts. The BSS sends signaling signals and service signals on the all interfaces in the IP network. Internet Protocol Control Protocol
IOS tRNCing
IP Performance Monitor IP PM IP Protocol
IP Security IP Transmission IPCP
Issue 08 (2011-09-30)
54
IPE
In Path Equipment: The IPE can be classified into echo canceller, digital communication multiplexer equipment (DCME), dual tone multi-frequency (DTMF) generator, A-law/ u-law converter, and so forth. See IP over ATM See IP Security The abbreviation of Internet Protocol version 4. IPv4 utilizes a 32bit address which is assigned to hosts. An address belongs to one of five classes (A, B, C, D, or E) and is written as 4 octets separated by periods and may range from 0.0.0.0 through to 255.255.255.255. Each address consists of a network number, an optional subnetwork number, and a host number. The network and subnetwork numbers together are used for routing, and the host number is used to address an individual host within the network or subnetwork. IPv4 addresses may also be represented using CIDR (Classless Inter Domain Routing). The abbreviation of Internet Protocol version 6. IPv6 provides a replacement for IPv4. IPv6 includes support for flow Identity in the packet header, which can be used to identify flows and improve QoS (Quality of Service). IPv6 was formerly known as IPng (next generation). Incremental Redundancy See Interference Rejection Combining See Integrated Services Digital Network See Integrated Services Digital Network User Part See International Telecommunication Union Intra Domain Connection of RAN Nodes to Multiple CN Nodes Iu User Plane Interface between RNC and CBC. See Interworking Function
IPoA IPSec IPv4
IPv6
IR IRC ISDN ISUP ITU Iu Flex Iu UP Iu-BC Interface IWF
1.3.11 K
K byte K byte event Kc Key property Ki KR KVM A general designation of K1 byte and K2 byte in the SDH. A switch event that is recorded in K byte format and to which the APS request is converted. Ciphering key (Kc): It is generated by the GSM authentication center and stored in the MSC/VLR. The Kc is sent to the BTS before the ciphering procedure begins. A property that can uniquely identifies an object example. Individual subscriber authentication key (Ki): The IMSI and Ki are generated and stored in the authentication center and SIM card when a user registers in the GSM network. Kaufman-Roberts algorithm Key/Vision/ Mouse
Issue 08 (2011-09-30)
55
1.3.12 L
L2ML LA LAC LAI LAN LAPB LAPD LAPDm Layer 2 Management Link See Location Area See Location Area Code See Location Area Identity See Local Area Network See Link Access Procedure Balanced Link Access Protocol on the D channel Link Access Protocol on the Dm channel
Large frequency offset Large frequency offset of clock source occurs when the clock module detects that the offset between the frequency of the clock source and the center frequency of the local clock exceeds the specified value, for example, 1 Hz. LCC LCP LCS LCS client Load Congestion Control See Link Control Protocol See Location Service An entity subscribing to LCS and interacting with a LCS server to obtain location information of one or more UEs. It can either interact with UEs or not. In addition to managing the user interface, it is responsible for formatting and displaying data. It can reside in the UE. A software and/or hardware entity offering LCS capabilities. It receives service requests and sends back replies. Load Control Balancing Load Control Load Monitor See Load Reshuffling In computing, the least significant bit (lsb) is the bit position in a binary integer giving the units value, that is, determining whether the number is even or odd. See Local Element Management Layer A six-bit field that defines message length and that is used to differentiate between message signal units, link status signal units, and fill-in signal units. Longest Consecutive Frame Error See Length Indicator
LCS server LDB LDC LDM LDR Least Significant Bit LEML Length Indicator LFE LI
Link Access Procedure Data link protocol in the X.25 protocol stack. LAPB is a bit-oriented protocol derived Balanced from HDLC. X.25 Link Control Protocol Link State Advertisement LLC
Issue 08 (2011-09-30)
In the Point-to-Point Protocol (PPP), the Link Control Protocol (LCP) establishes, configures, and tests data-link Internet connections. The link in LSA is any type of connection between OSPF routers, while the state is the condition of the link. Link Layer Control
LMT
The abbreviation of Local Maintenance Terminal. The LMT is a logical concept. The LMT connects to the external RNC/NodeB network and provides the GUI for the OM of the RNC/NodeB. In the RNC/NodeB OM subsystem, the LMT is the terminal for operators to perform the OM. The LMT application refers to the Huawei Local Maintenance Terminal software. A computer installed with HUAWEI Local Maintenance Terminal The LMT software refers to the Huawei Local Maintenance Terminal software package. It is installed on the LMT PC. See Location Measurement Unit LMU type A LMU type B See Low Noise Amplifier The admission control, such as CS preference TCHH and Adaptive Multi-Rate Control (AMRC), is performed on the load of the newly accessed subscriber. The load reshuffling, such as CS TCHH/TCHF handover and PS downspeeding, is performed on the accessed subscriber. A local area network (LAN) is a computer network covering a local area, like a home, office or small group of buildings such as a college. The performance management console provided by the LMT belongs to the LEML and facilitates general analysis of the data in local network. One physical BSC serves as multiple logical BSCs. Each logical BSC has an SS7 signaling point code and can exchange signaling with the MSC.
LMT application LMT PC LMT Software LMU LMU-A LMU-B LNA Load Reshuffling
Local Area Network Local Element Management Layer Local multiple signaling points of the BSC
Local Optical Interface A single optical interface board integrates with two 622-Mbps optical interfaces and a Board cross-connect module. Local signaling point local time Location Area Location Area Code The local signaling point of the BSC is the signaling point that is assigned to the BSC and is referred to as local originating signaling point. The same as the display time of a local computer. The local time varies according to the time zone. The location Area is defined as an area in which a mobile station may move freely without updating the VLR. The Location Area Code uniquely identifies a LA (Location Area) within a PLMN (Public Land Mobile Network). It may range from 0 to 65,535.
Location Area Identity The Location Area Identity uniquely identifies a LA (Location Area) within any PLMN (Public Land Mobile Network). It is comprised of the MCC (Mobile Country Code), MNC (Mobile Network Code) and the LAC (Location Area Code). Location based application Location information can either be input by users or obtained by UTRAN or UE measurement. Navigation is a typical example of location based application.
Location Measurement In GSM or UMTS a Location Measurement Unit makes radio measurements to support Unit positioning of mobiles. Two categories of measurements are identified, the first identifies measurements specific to one MS (Mobile Station) used to compute its location. The second method provides assistance measurements which is specific to all mobiles in a defined geographic area.
Issue 08 (2011-09-30)
57
Location Service
The LCS, also known as the location based service, is a value-added service used to obtain the location information of a mobile subscriber through the wireless network, and to provide services with the support of the e-map. When the external reference clock source is operational and the offset between the source and the center frequency saved on the system is within 0.2 Hz, the system begins to work in locked mode. In this mode, the system does not adjust the local oscillator, which helps to ensure that the synchronization error between the local oscillator and the upper-level clock source is smaller than 0.05 ppm, as specified by 3GPP protocols.
Locked mode
LOF Logical Port Loopback recovery Loopback test LOS Loss Of Frame
See Loss Of Frame On the IP interface board of the BSC, a physical port can be configured with multiple logical ports with logical bandwidth. A logical port maps one or multiple BTSs. Calls in the local switching state are recovered to the ordinary conversation state. It is usually used for diagnostic purposes to determine if an interface is functioning properly. See Loss Of Signal A condition at the receiver or a maintenance signal transmitted in the PHY overhead indicating that the receiving equipment has lost frame delineation. This is used to monitor the performance of the PHY layer. Loss of signal (LOS) indicates that there are no transitions occurring in the received signal. A special type of electronic amplifier or amplifier used in communication systems to amplify very weak signals captured by an antenna. It is often located very close to the antenna. Low Voltage Differential signalling is a low noise, low power, low amplitude method for high-speed (gigabits per second) data transmission over copper wire. See common Channel Signaling Processing Board See Link State Advertisement See Least Significant Bit See Low Voltage Differential Signal
Loss Of Signal Low Noise Amplifier
Low Voltage Differential Signal LPN7 LSA LSB LVDS
1.3.13 M
M criteria Indicates a criteria that selects only the neighbor cells of which the RX level is higher than the lowest RX level threshold and sorts the qualified cells in the candidate cell list. The serving cell and neighbor cells are sorted based on the RX level. Mobile Allocation See Media Access Control See Media Access Control - common Medium Access Control - dedicated MAC-e Entity (handling E-DCH specific functions)
MA MAC MAC-c MAC-d MAC-e
Issue 08 (2011-09-30)
58
MAC-hs Macro cell MACS MAFU Main cabinet Main cabinet group Main subRNCk MAIO Man-Machine Language Manual Switch MAP Maximum Transfer Unit MB MBMS MBR MBR MCC MCCH MCPPP MCU MDC MDMC MDSP MDT ME Mean Opinion Scores
Medium Access Control for HSDPA Macro cells are outdoor cells with a large cell radius. Maximum number of AMR Codec ModeS Multi-Antenna Filter Unit The main cabinet in combined cabinets is the cabinet that provides transmission interfaces for the combined cabinets. The main cabinet group is the cabinet group that provides reference clocks for the BTS. Generally, each cabinet in the main cabinet group is configured with one or two DTMUs. The subracks are connected in star topology. The subrack located in the center is called main subrack. See Mobile Allocation Index Offset A language designed to facilitate direct user control of a computer. Switchover conducted manually. Mobile Application Part The MTU (Maximum Transmission Unit) is the size of the largest datagram that can be sent over a network. Mega Byte See Multimedia Broadcast Multicast Service See Multiband Report Maximum Bit Rate See Mobile Country Code MBMS point-to-multipoint Control Channel Multi-Class Extension to Multi-link PPP Main Control Unit See Message Discrimination Distribution Monitor and Communication board Mobile Data Service Platform See Message Distribution See Mobile Equipment In voice communications, particularly Internet telephony, the mean opinion score (MOS) provides a numerical measure of the quality of human speech at the destination end of the circuit. The average time between consecutive failures of a piece of equipment. It is a measure of the reliability of the system. The average time that a device will take to recover from a failure.
Mean Time Between Failures Mean Time To Repair
Issue 08 (2011-09-30)
59
Media Access Control
Media Access Control is the lower of the two sublayers of the Data Link Layer. In general terms, MAC handles access to a shared medium, and can be found within many different technologies. For example, MAC methodologies are employed within Ethernet, GPRS, and UMTS etc.
Media Access Control - The MAC-c/sh controls access to common transport channels. common Media Gateway Media Gateway. A logical entity that converts the format of the media of a network to meet the format requirement of another network. It can process audio services, video services and data services, and convert the media format in full duplex mode. In addition, it can play certain audio and video signals, and provide the IVR function and media conference. Message arrival rate indicates the number of specified messages received by the BSC in a unit time. Used to specify the messages that are written to the syslog file.E.g,Critical=0, major=1, minor=2, warning=3, informational=4 Message distribution refers to the delivery of messages to the proper recipient, which conform a work session. Sent from that computer with a request for message route tracking.
Message arrival rate Message Discrimination Message Distribution Message Routing
Message Transfer Part The Message Transfer Part (MTP) is part of the Signalling System 7 (SS7) used for Level 3 communication in Public Switched Telephone Networks. MTP Level 3 provides routing functionality to transport signaling messages through the SS7 network to the requested endpoint. Message Transfer Part Message Transfer Part level 3 broadband provides message routing, discrimination and level 3 broadband distribution (for point to point link only). It also provides signalling link management, load sharing and changeover between links within one link-set. The protocol is a broadband ISDN based protocol used typically in ATM (Asynchronous Transfer Mode) . MGW MICH MM MMC MMCC MMI MML MMSMS MMSS MNC MNS Mobile Allocation Index Offset See Media Gateway MBMS notification Indicator Channel Mobility Management Multimedia Controller Mobility Management Call Control Man Machine Interface See Man-Machine Language Mobility Management Short Message Service Mobility Management Supplement Service See Mobile Network Code Mobile Network Signaling A time delay separating traffic channels. When a GSM (Global System for Mobile Communications) mobile phone is served by a cell that is hopping over a set of frequencies, the separate traffic channels hop over the allocated frequencies according to a hopping sequence number (HSN). The traffic channels with the same HSN hop over the same frequencies in the same order but are separated in time by a mobile allocation index offset (MAIO).
Issue 08 (2011-09-30)
Mobile Country Code
The Mobile Country Code is a three digit number uniquely identifying a given country. It is utilized within the IMSI (International Mobile Subscriber Identity) and LAI (Location Area Identity). Mobile equipment is a component of the MS. When a SIM is placed in a Mobile Equipment (ME), together they become a Mobile Station (MS) which may then register onto a GSM network. Either a two or three digit number used to uniquely identify a given network from within a specified country (MCC (Mobile Country Code)). The MNC is used as part of the IMSI (International Mobile Subscriber Identity) and LAI (Location Area Identity) etc. Short for mobile network code, it consists of two or three digits and identifies a PLMN to which a mobile subscriber belongs. MSC is the switch that serves the UE in its current location for Circuit Switched Services.
Mobile Equipment
Mobile Network Code
Mobile Service Switching Center Server Mobile Station Mobile Station International ISDN Number Mobile Switching Center
A station in the Public Cellular Radio Telecommunications Service intended to be used while in motion or during halts at unspecified points. The number consists of Country Code (CC) and National (significant) mobile number which consists of National Destination Code (NDC) and Subscriber Number (SN). Mobile Switching Center. A logical entity that provides interfaces for interworking with the function entities in a GSM/WCDMA system and the public network. It plays a core role for switch in the GSM/WCDMA system. It provides mobile management and switch to mobile subscribers and sets up communications between mobile subscribers, or between a mobile subscriber and a fixed line subscriber. Mobile Originated Call See Mean Opinion Scores A method for assessing the voice quality by a group of people who answer phones in a room.The ITU-T P.800 defines the assessment of the selected voice samples that adopt the TFO and compression algorithm. The assessment is made by a group of male and female expert audience on certain conditions. The assessment result is the MOS, which is classified into five levels. Level 1 indicates the poorest; Level 5 indicates the best. Multiuser Project Manager
MOC MOS MOS analysis
MPM
MPTY supplementary This supplementary service enables a user to have a multi-connection call, that is, a service simultaneous communication with more than one party. This supplementary service is categorized into two types: three-party service and conference call. MR MRC MRP MRT MS MS-AIS MSC MSC Server Measurement Report Maximum Ratio Combining Multiple Reuse Pattern See Message Routing See Mobile Station See Multiplex Section Alarm Indication signal See Mobile Switching Center See Mobile Service Switching Center Server
Issue 08 (2011-09-30)
61
MSC status
The MSC can be in the administration state and the operation state:In the administration state, data configuration and private message on the A interface can be modified. The administration state can be normal, offload, or inhibited.The operation state indicates the actual status of the CN. The operation state can be available or unavailable. For example, the CN is unavailable when the No.7 signaling link is disconnected and becomes available when the No.7 signaling link is resumed. MBMS point-to-multipoint Scheduling Channel See Mobile Station International ISDN Number See Multiplex Section Protection Message Signaling Unit Maintenance and Test console See Mean Time Between Failures Message Transfer Part See Message Transfer Part Level 3 See Message Transfer Part level 3 broadband See Mean Time To Repair See Maximum Transfer Unit Data are forwarded by multiple uncertain routers before reaching the destination. Multiband Report is the information about six neighbor cells of different bands reported by the MS to the network. This PVC is used to transmit the same data to multiple nodes.
MSCH MSISDN MSP MSU MT MTBF MTP MTP3 MTP3B MTTR MTU Multi-hop Multiband Report Multicast PVC
Multimedia Broadcast The MBMS is a unidirectional point to multipoint bearer service in which data is Multicast Service transmitted from a single source entity to multiple recipients. These services will typically be in the form of streaming video and audio and should not be confused with the Cell Broadcast Service that is currently supported. Multiple IP Addresses on Port Multiple IP addresses can be configured on a physical port. Multiple IP addresses on the same physical port are on equal status. The purpose is to configure multiple IP addresses on a port, thus saving resources on the port.
Multiplex Section AIS is an all-ONES characteristic or adapted information signal. It's generated to replace Alarm Indication signal the normal traffic signal when it signal contains a defect condition in order to prevent consequential downstream failures being declared or alarms being raised.AIS can be identified as. Multiplex Section Protection The function performed to provide capability for switching a signal between and including two MST functions, from a "working" to a "protection" channel.
1.3.14 N
N-PDU NA NACC NACK Network Protocol Data Unit See No Acknowledgment See Network Assisted Cell Change See Negative Acknowledgement
Issue 08 (2011-09-30)
62
Narrowband NAS NBM NC2 NCC NCP NE Near-far interference NECI Negative Acknowledgement Neighboring cell
A signal which occupies only a small amount of space on the radio spectrum the opposite of broadband or wideband. See Non-Access Stratum NodeB Management Module See Network Control Mode 2 See Network Color Code See Network Control Protocol See Network Element Near-far interference occurs when a desirable signal from a far-away user is interfered with by another user close to intended receiver. New Establishment Causes Indication The notification sent by a network device to another network device. It indicates that the network device fails to understand the message or implement a request operation. The neighboring cells of the reference cell confirmed during a UE positioning process. The AGPS positioning method needs no neighboring cells. In CELLID+RTT and OTDOA positioning methods, UEs need to measure signals of the reference cell and the neighboring cells simultaneously to obtain geographic locations of cells for accurate positioning.
Neighboring GSM Cell A cell that is adjacent to the serving cell but belongs to a GSM or GSM/GPRS system. Neighboring GSM cell NEL Network Assisted Cell Change The neighboring GSM cell refers to a cell that is adjacent to the serving cell but belongs to a GSM or GSM/GPRS system. See Network Element Layer Network Assisted Cell Change (NACC) accelerates the cell reselection. This feature minimizes the service interruption time due to the cell reselection.
Network Assisted GPS Assisted Global Positioning System is a technique enabling both mobiles and cellular networks to establish accurate positioning information. The system utilizes both the GPS (Global Positioning System) and the terrestrial cellular network and is one of the LCS (Location Services) methodologies. Network Color Code The group of the three most significant bits of the BSIC is called the Network Colour Code (NCC).
Network Control Mode This describes network controlled cell reselection, which is also referred to as network 2 control mode 2 (NC2). In NC2 mode, the network requests measurement reports from the MS and controls the cell reselection. Network Control Protocol Network Element Network Element Layer This is the program that switches the virtual circuit connections into place, implements path control, and operates the Synchronous Data Link Control (SDLC) link. A Network Element refers to a communication equipment in the network. In the BSC6000 system, the performance management module configured in the OMU board and the performance management module configured in the service processing board belong to the NEL and facilitate collection and preprocessing of data.
Issue 08 (2011-09-30)
63
network layer
The network layer is layer 3 of the seven-layer OSI model of computer networking. The network layer provides routing and addressing so that two terminal systems are interconnected. In addition, the network layer provides congestion control and traffic control. In the TCP/IP protocol suite, the functions of the network layer are specified and implemented by IP protocols. Therefore, the network layer is also called IP layer.
Network Management The network management equipment belongs to the NML that is the upper layer with Layer the M2000. The equipment helps to browse and analyze performance analysis results. Network Management A Network Management System (NMS) is a combination of hardware and software used System to monitor and administer a network. Individual network elements (NEs) in a network are managed by an element management system. Network Subsystem Network System The Network Subsystem is a collection of different functions, linked by standardized interfaces. Information network management system is, by means of information technology, a computer network management system capable of data information, transmission, exchange and distribution.
Network Time Protocol NTP is a protocol designed to synchronize the clocks of computers over a network. NTP version 3 is an internet draft standard, formalized in RFC 1305. NTP version 4 is a significant revision of the NTP standard, and is the current development version, but has not been formalized in an RFC. SNTP (Simple NTP) version 4 is described in RFC 2030. Network to Network Interface NML NMON NMS NNI NNSF No Acknowledgment Non Real-Time Variable Bit Rate This is an internal interface within a network linking two or more elements. See Network Management Layer NodeB MONitor unit See Network Management System See Network to Network Interface Non Access Stratum (NAS) Node Selection Function No acknowledgement is the claim that the issue about which we are concerned has no validity. The nrt-VBR service category is used for connections that transport variable bit rate traffic for which there is no inherent reliance on time synchronisation between the traffic source and destination, but there is a need for an attempt at a guaranteed bandwidth or latency. The Non Access Stratum is a functional layer running between the UE (User Equipment) and the CN (Core Network). The layer supports traffic and signalling messages between the CN and UE. A special LAI. It is coded following the same principles as the common LAIs. Each MSC in the MSC pool must be assigned with a unique non-broadcast LAI, which is used when the MSC is offloaded. A cell that belongs to the E-DCH active set rather than the serving E-DCH RLS and from which the UE can receive one relative grant. The UE can have zero, one, or several nonserving E-DCH RLs. The clock source is normal when no loss, jitter, or large frequency offset occurs. Neighboring Radio Network Controller
Non-Access Stratum
Non-broadcast LAI
Non-serving E-DCH RL or non-serving RL Normal clock source NRNC
Issue 08 (2011-09-30)
64
NRT NRT-VBR NS NSS NTP NULL_NRI
Non-Real-Time See Non Real-Time Variable Bit Rate See Network System See Network Subsystem See Network Time Protocol A special NRI. It is coded following the same priciples as the common NRIs:If an MSC pool with a single operator, the NULL_NRI is unique.When the MOCN is supported, operators have different NULL_NRIs in the MSC pool. Each CN operator has its own unique NULL_NRI. Universal Transport Interface Unit
NUTI
1.3.15 O
Object category A category of objects in the wireless configuration model For instance, the AAL2 path, SAAL link, or cell can be referred to as an object category respectively. Object example An example for an object category For instance, the cell with the ID of 0 is an object example for the object category of cell. OCXO Office Direction Oven Controlled Crystal Oscillator Office direction refers to the number of the peer office equipment. The structure of a telephone number is: office number (composed of three numbers) + internal number (composed of four numbers). The switching system searches the office numner, connects to the office where the office number is located, searches the internal number, and then connect to the subscriber to which the internal number belongs. An office may have more than one office number, which can be referred to as the office direction. Most of the office numbers are adjacent, for example, 733, 734, and 735. See Overload Control Outer Loop Power Control OM-DBG is an internal module of the SPU. It has the following functions: l l l l l l l l OMC OMIP
Issue 08 (2011-09-30)
OLC OLPC OM-DBG
Receiving tasks sent from the BAM Generating filter tables Maintaining the task check between the BAM and the SPU Maintaining the message channels between the trace tasks and the LMT Informing the traffic processing module of the change of trace tasks Providing message channels from the traffic processing module to the BAM or LMT Providing interfaces for reporting data messages of the traffic module Providing interfaces for flow control
See Operation and Maintenance Center IP Address of Operation and Maintenance

OMU Software OMUa OMUCore OMUDaemon OMULocal OOK Open System Interconnection Operating System Operation and Maintenance Center
The OMU software runs on the GBAM/GOMU. It performs the operation and maintenance of the BSC. RNC Operation and Maintenance Unit REV:a Core process of the GBAM/GOMU. It is the OM center of the BSC. Monitoring process of the GBAM/GOMU. It monitors the OMUCore and the OMULocal. Local process of the GBAM/GOMU. It manages the status of the GBAM server and the GOMU. On-Off-Keying A standard description or reference model for how messages should be transmitted between any two points in a telecommunication network. The software that controls the allocation and usage of hardware resources. An Operations and Maintenance Centre is an element within a network management system responsible for the operations and maintenance of a specific element or group of elements. For example an OMC-Radio may be responsible for the management of a radio subsystem where as an OMC-Switch may be responsible for the management of a switch or exchange. However, these will in turn be under the control of a NMC (Network Management Centre) which controls the entire network. Operating Expenditure Indicates the active BCCH TRX configured on the BSC6000 Local Maintenance Terminal by the user in the cell. Orthogonal variable spreading factor (OVSF) is an implementation of Code division multiple access (CDMA) where before each signal is transmitted, the spectrum is spread through the use of a user's code. See Operating System OS tracing is used to trace the messages inside the Operating System (OS). See Open System Interconnection Operating Support System Observed Time Difference Of Arrival An engineering method of improving the usage of resources A means to restrict reverse analog control channel accesses by mobile stations. Mobile stations are assigned one (or more) of sixteen control levels. See Orthogonal Variable Spreading Factor
OPEX Original active BCCH TRX Orthogonal Variable Spreading Factor OS OS tRNCing OSI OSS OTDOA Overbooking Overload Control OVSF
1.3.16 P
P-TMSI P/N criterion PA PACCH See Packet Temporary Mobile Subscriber Identity It is a criteria against which a certain operation is performed when the criteria last within an acceptable statistical period. Power Amplifier Packet Associated Control Channel
Issue 08 (2011-09-30)
66
Packet Control Unit
The packet control unit (PCU) enables the communication between the BSC and the SGSN in the GPRS network. The PCU performs functions such as packet radio resource management and packet call control. The Packet Data Channel is a general term used in GPRS to represent a timeslot given over to the control of GPRS rather than conventional GSM circuit switching. As such, it may carry either signalling or user data GPRS. Packet Data Convergence Protocol is used in UMTS to format the data into a suitable structure prior to transfer over the air interface. Packet Data Protocol is a network protocol used by packet switching external networks to communicate with GPRS (General Packet Radio Services) networks. The packet data service requires intermittent bursts instead of continuous data, for example, the e-mail system. A Packet Data Serving Node is responsible for the establishment, maintenance and termination of a PPP (Point to Point Protocol) session towards the MS (Mobile Station). It may also assign dynamic IP addresses in addition to supporting Mobile IP functionality. It provides a similar function to the GSN (GPRS Support Nodes) found in GSM and UMTS networks. A sequence of packets that have similar headers and share a context. Used as a shorter, more private, mobile identifier. Identifies the system that assigned it, and not directly the MS.Packet-TMSI is allocated by the SGSN and used for GPRS access only.
Packet Data Channel
Packet Data Convergence Protocol Packet Data Protocol Packet Data Service Packet Data Serving Node
Packet stream Packet Temporary Mobile Subscriber Identity
packet timing advanced PTCCH stands for Packet Timing advanced Control Channel. The PTCCH/U is used by control channel an MS to send an access burst in the uplink and the BSS sets the correct timing advance for this MS in packet transfer mode. The PTCCH/D is used to send a refresh message to the MS in the downlink, requesting the MS to refresh the timing advance information. One PTCCH/D can correspond to several PTCCH/Us. Page Indicator Channel A fixed rate (SF=256) physical channel used to carry the Page Indicators (PI). Paging Paging Channel PARC The act of seeking a mobile station when a call has been placed to that mobile station. Downlink only, used to send page requests to Mobile Stations. Platform of Advanced Radio Controller
Issue 08 (2011-09-30)
67
Patch
A patch is composed of one or more changes. After the patch is loaded, some original programs are affected. The realization of the patch technology depends on the patch facture tool first. The patch file is generated based on the target codes created by the compilation of source codes modified by functions. The patch module operates the patch file and implements the management of the patch. Patches have two kinds, that is, hot patches and cold patches. The difference between the hot patches and the cold patches are that the cold patches must load whole software programs. Hot patches can be installed independently and need not install all the system again. Cold patches, however, need install the software of boards again. The upgrade procedure for the cold patches is identical to some software upgrade procedures. The following two patches are describes as follows: l Hot patches, Hot patches are added to the existing version. The hot patches are independent of the server, Install program, or file copying. Thus, the hot patches are software program entities that are installed and uninstalled independently. Cold patches, For some errors that are difficult to modify through the hot patches, you have to load the software of boards again. In this situation, you can use cold patches to solve this problem.
Pb Interface
The Pb interface is a non-standard internal interface between the PCU and the BSC. The implementation of the Pb interface varies from manufacturer to manufacturer. The Pb interface management includes trunk circuit management, packet radio resource management, and packet service access support. Packet Broadcast Control Channel Power Budget Provided Bit Rate The PCU-BSC Interface Signaling Link (PBSL) is the signaling link between the BSC and the PCU. See Power Boost Technology Power Boost Unit Personal Computer Power Control Algorithm Packet common Control Channel Primary common Control Physical Channel See Paging Channel Peripheral Component Interconnect Preemption Capability Indicator Packet Circuit Identity Code See Pulse Coded Modulation Physical common Pilot Channel See Packet Control Unit See Packet Data Channel See Packet Data Convergence Protocol See Power Distribution Frame
PBCCH PBGT PBR PBSL PBT PBU PC PCA PCCCH PCCPCH PCH PCI PCI PCIC PCM PCPICH PCU PDCH PDCP PDF
Issue 08 (2011-09-30)
PDH PDP PDSCH PDSN PDU Performance Browser Tool Periodical granularity Personal Identity Number PEUa PFCU PFPU PH Phase-locked Loop
See Plesiochronous Digital Hierarchy See Packet Data Protocol See Physical Downlink Shared Channel See Packet Data Serving Node See Power Distribution Unit Performance Browser Tool is a software item of the LMT software package. It is used to import and export performance description files for you to view and analyze them. Intervals between flow control decisions. common names for CHV1 and CHV2, respectively. RNC 32-port Packet over E1/T1/J1 Interface Unit REV:a Fan Control Unit Fan Power Unit Physical (layer) A circuit that consists essentially of a phase detector which compares the frequency of a voltage-controlled oscillator with that of an incoming carrier signal or referencefrequency generator; the output of the phase detector, after passing through a loop filter, is fed back to the voltage-controlled oscillator to keep it exactly in phase with the incoming or reference frequency. Per-Hop Behavior The physical downlink shared channel (PDSCH) is used to carry the downlink shared transport channel. This channel carries control information for several users that share the channel. See Page Indicator Channel A very small cell, from tens to hundreds of meters in size. Pico cells are optimized to provide high capacity. See Process Identification Priority Information Element Pilot pollution, i.e., too many hearable pilots, makes it difficult for SHO algorithm to perform properly, and DL transmit power as well as signaling capacity can be wasted for poor decisions and unnecessary active set updates. See Personal Identity Number Frequent handovers between cells due to changes in signal quality or improper parameter settings Ping-pong handover occurs when an MS is handed over back and forth between two cells due to the changes in signal quality or the improper settings of the parameters.
PHB Physical Downlink Shared Channel PICH pico cell PID PIE Pilot pollution
PIN Ping-pong effect Ping-pong handover
Issue 08 (2011-09-30)
69
ping-pong reselection
A cell reselection method for preventing ping-pong in a mobile communications system, comprising the steps of: acquiring first and second duration thresholds and first and second occurrence number thresholds for controlling a cell reselection procedure, the second duration threshold being shorter than the first duration threshold and the second occurrence number threshold being less than the first occurrence number threshold; setting a user equipment (UE) to a high-speed state if the number of cell reselections of the UE to the same cell during the second duration threshold exceeds the second occurrence number threshold; setting the UE to a non-high-speed state if the number of cell changes of the UE during the first duration threshold is equal to or less than the first occurrence number threshold; setting the UE to the high-speed state if the number of cell reselections of the UE to the same cell during the second duration threshold is equal to or less than the second occurrence number threshold and if the number of cell changes of the UE during the first duration threshold exceeds the first occurrence number threshold; selectively performing cell reselection according to a predetermined cell reselection time limit in the non-high-speed state in the UE; and selectively performing cell reselection according to a scaled-down value of the predetermined cell reselection time limit in the high-speed state in the UE.
Plesiochronous Digital The Plesiochronous Digital Hierarchy (PDH) is a technology used in telecommunications networks to transport large quantities of data over digital transport Hierarchy equipment such as fibre optic and microwave radio systems. PLL PLMN Pn PoC See Phase-locked Loop See Public Land Mobile Network Maximum transmit power See Push-to-talk over Cellular
Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates data packets on the network layer. It is located in layer 2 of the IP protocol stack. Polarization antenna A polarization antenna is an antenna measured by aligning the target antenna and the probe antenna and then carrying out the measurement twice when the probe antenna is at 0.degree. and 90.degree. The rate adjustment policy for BE services of the PS domain when the UE is in the CELL_DCH state. The rate can be increased or decreased. The rate adjustment policy for BE services of the PS domain when the UE is in the CELL_DCH state. The state of the UE can be transited to FACH at any time. Port IP is referred to as physical port IP that is used in the communications between the BSC and other NEs such as the MGW, MSC, and BTS. The port IP serves as the source IP address at the BSC and serves as the destination IP address at the peer NE. The port IP is associated with a certain physical port on the interface board, which can receive and send the packets of port IP. This function is used to estimate the geographic locations of UEs. Principles or algorithms that the positioning is based on. RNC 2-port IP over channelized Optical STM-1/OC-3 Interface Unit REV:a PBT can be used to expand the radio coverage of BTSs. Power Distribution Frame. It is a high-current power supply in the equipment room.
Policy A Policy B Port IP
Positioning Positioning method POUa Power Boost Technology Power Distribution Frame
Issue 08 (2011-09-30)
70
Power Distribution Unit Power interface box Power offset attribute
The power distribution unit performs AC or DC power distribution. Demarcation point between the power distribution equipment prepared by the operator and the base station equipment supplied by a vendor. Power offset between E-DPDCH power level and reference E-DPDCH power level of a given E-TFC. Power offset is set to achieve the required QoS in this MAC-d flow when carried alone in a MAC-e PDU and subsequently in the corresponding CCTrCh of E-DCH type.
PPP PPP Multiplexing
See Point-to-Point Protocol The method, PPP Multiplexing, sends multiple PPP encapsulated packets (sub-frames) in a single PPP frame. As a result, the PPP overhead per packet is reduced. It is applicable to transport small packets such as voice and data over slow links. See PPP Multiplexing Point-to-Point Protocol over Ethernet Preemption Recommendation Indicates the frequency band containing the main BCCH frequency in a Co-BCCH cell. An identification number that is automatically assigned to each process when it is created on a Unix-like operating system. Corresponding to one channel of multimedia program source. Corresponding to specific program data. Distinguished by IP address, that is, RNC identifies programs by different destination IP addresses. SDP refers to the session description protocol. The program SDP file stores the program data including the bandwidth and the format of the program, and the port numbers for the audio and video. The data are used for decoding and playing the program. The SDP file is generated by the multimedia controller when the multimedia program is made. The SDP file is saved in the directory of BAM\FTP\SDP.
PPPMUX PPPoE PREC Primary frequency band Process Identification Program channel
Program SDP file
Protection grounding bar PS PSTN PSU PTCCH PTT Public Land Mobile Network Public Switched Telephone Network
A bar connecting the PGND cable of the cabinet so that the cabinet and the earth are in the same equipotential level. Packet Switched See Public Switched Telephone Network Power Supply Unit See packet timing advanced control channel See Push to Talk A public land mobile network may be defined as a number of mobile services switching centre areas within a common numbering plan and a common routing plan. Public Switched Telephone Network. A telecommunications network established to perform telephone services for the public subscribers. Sometimes called POTS.
Issue 08 (2011-09-30)
71
PUC Pulse Coded Modulation Push to Talk
Potential User Control PCM is a Time-Domain Waveform coding method and is defined within CCITT G.711, and ATT 43801. Basically, an analog signal is sampled at a rate of 8000 times per second. In each sample, the amplitude of the signal is assigned (quantized) a digital value. Push to talk (PTT), is a means of instantaneous communication commonly employed in wireless cellular phone services that uses a button to switch a device from voice transmission mode to voice reception mode. The operation of phones used in this way is similar to "walkie talkie" use. Operated in a highly automatic way Compared with the services provided by commonly used mobile phones, the PoC enables a single person to talk to several persons one to one. Preemption Vulnerability Indicator Pulse-Width Modulation
Push-button Push-to-talk over Cellular PVI PWM
1.3.17 Q
QA QoS QPSK QRI Quality of Service Queuing Allowed indicator See Quality of Service See Quaternary Phase Shift Keying Queuing Recommendation Indicator Quality of Service, which determines the satisfaction of a subscriber for a service. QoS is influenced by the following factors applicable to all services: service operability, service accessibility, service maintainability, and service integrity.
Quaternary Phase Shift Quadrature phase shift keying (QPSK) is a method for transmitting digital data across Keying an analog channel. Data bits are grouped into pairs and represented by a unique waveform, called a symbol. Data may be simulated with a pseudo-noise sequence generator. Quintet, UMTS authentication vector Temporary protocol of authentication and key, which enables UMTS AKA function for a certain user in a VLR/SGSN. A quintet consists of five elements: Random Number (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key (IK), and Authentication Token (AUTN).
1.3.18 R
R98 R99 + R99 + ME capable of UMTS AKA A network node or ME that conforms to R97 or R98 specifications. A network node or ME that conforms to specifications of R99 or later releases. Either an R99 + UMTS only ME, an R99 + GSM/UMTS ME, or an R99 + GSM only ME that supports USIM-ME interface.
R99 + ME incapable of An R99 + GSM only ME that does not support USIM-ME interface. UMTS AKA R99 cell RA RAB
Issue 08 (2011-09-30)
The cells in which the HSDPA related resources are not configured. See Routing Area See Radio Access Bearer
RAB index Radio Access Bearer
A number defined by the RNC for a traffic class supported by the RNC. Term used in UMTS to identify the service the AS (Access Stratum) provides to the NAS (Non Access Stratum) for transfer of user data between the UE (User Equipment) and the CN (Core Network).
Radio Access Network The Radio Access Network performs the radio functionality of the network, as well providing the connection to the CN (Core Network). The RAN typically includes a controller (RNC (Radio Network Controller) in 3GPP (Third Generation Partnership Project) and BSC (Base Station Controller) in 3GPP2 (Third Generation Partnership Project 2) and several transmitter/receivers (Node B in 3GPP, BTS (Base Transceiver Station) in 3GPP2). Radio Access Network Radio Access Network Application Part (RANAP) is the Radio Network Layer signaling Application Part protocol used in a UMTS system on the Iu interface. It is responsible for function including the setting up of a RAB (Radio Access Bearer) between the CN (Core Network) and the RNC (Radio Network Controller). Radio Access Technology This indicates the type of radio technology to access the CN (Core Network). Example technologies being UTRA (UMTS Terrestrial Radio Access), CDMA2000?, DECT (Digital Enhanced Cordless Technology), GERAN (GSM EDGE Radio Access Network) etc. The service provided by the Layer 2 for the transfer of user data between UE (User Equipment) and UTRAN (UMTS Terrestrial Radio Access Network). Radio frequency is a type of electric current on a wireless network, which emits an electromagnetic field when alternating current is applied to an antenna. Radio Link Control (RLC) is a link-layer protocol that is responsible for error recovery and flow control. The management performed for the radio links and radio interfaces. This equipment in the RNS is in charge of controlling the use and the integrity of the radio resources.
Radio Bearer Radio Freqency Radio Link Control Radio Link Management Radio Network Controller
Radio Network System The UTRAN (UMTS Terrestrial Radio Access Network) consists of one or more RNS (Radio Network Subsystem). Each RNS control the allocation and the release of specific radio resources to establish a connection between a UE (User Equipment) and the UTRAN. Radio Network Temporary Identifier Radio Resource Radio Resource Control Radio Resource Management RAI A Radio Network Temporary Identifier is a generic term of an identifier for a UE when an RRC connection exists. Following types of RNTI are defined: Cell RNTI (C-RNTI), Serving RNC RNTI (S-RNTI) and UTRAN RNTI (U-RNTI). The resource in radio communication, including the frequncy, time, code, power, space, storage, and links. RRC sublayer executes the integrity protection of both RRC-level and higher layer signalling, by using Integrity Algorithm f9 under the control of the Integrity Key IK (128bits) established during the AKA procedure. Radio Resource Management (RRM) is the planning and scheduling of the air interface resources for the mobile communication system. It manages all air interface resources, such as creating, monitoring, modifying, or removing sites, sectors, or carriers. See Routing Area Identity
Issue 08 (2011-09-30)
73
Raileigh fading Rake receiver
In radio propagation, signals inevitably suffer from short-period amplitude changes. Raileigh fading relates to frequency. In other words, signal fading is frequency-specific. A rake receiver is a radio receiver designed to counter the effects of multipath fading. It does this by using several "sub-receivers" each delayed slightly in order to tune in to the individual multipath components. Each component is decoded independently, but at a later stage combined in order to make the most use of the different transmission characteristics of each transmission path. See Radio Access Network See Radio Access Network Application Part See Random Number A number selected from a known set of numbers in such a way that each number in the set has the same probability of occurrence. This is typically used in the authentication and ciphering process. See Radio Access Technology The conversion from a full-rate channel to a half-rate channel or from a half-rate channel to a full-rate channel. See Radio Bearer RNC Business rack RNC Business Subrack See remote control Remote Control Unit The RTSP (Real Time Streaming Protocol) is a client-server application-level protocol for controlling the delivery of data with real-time properties. It establishes and controls either a single or several time-synchronized streams of continuous media, such as audio and video. It uses transport protocols such as UDP, multicast UDP, TCP, and RTP to deliver the continuous streams. In other words, RTSP acts as a "network remote control" for multimedia servers. Sources of data can include both live data feeds and stored clips.
RAN RANAP RAND Random Number
RAT Rate adjustment RB RBR RBS RC RCU Real Time Streaming Protocol
Real Time Variable Bit Describes services with variable data streams and strict real-time requirements, for Rate example, interactive compressed video (video telephony). Real-time Transfer Protocol Receive diversity RTP, a protocol for end-to-end real-time transmission, provides the RX end with timing and packet serial number for recovering real-time data, and provides communications quality test. The most common type of diversity, where a mobile device uses two physically separate antennas to combine signals from the two antennas to reduce the impact of spatial variations in signal strength and thus increase the average data rate available - sometimes dramatically. The received power on one code after despreading, defined on the pilot symbols. The signal level at a receiver input terminal.
Received Signal Code Power Received signal level
Received signal Quality In a radio system RXQUAL indicates the average signal quality received.
Issue 08 (2011-09-30)
74
Received Signal Strength Indicator
The received wide band power, including thermal noise and noise generated in the receiver, within the bandwidth defined by the receiver pulse shaping filter, for TDD within a specified timeslot. The reference point for the measurement shall be the antenna connector of the UE. The 1+1 recover mode is classified into revertive mode and non-revertive mode. To correct by calculation or adjustment. Redirect tracing is used to trace the print information of the serial ports on the board subsystem. A main cell confirmed during a UE positioning process. Usually it is the cell the UE camps on. During soft handover, it is the cell with the best signals. A reference clock is usually of high stability , accuracy and autonomy and it's frequency can be compared with other clock as a benchmark. An uncompressed header that carries neither a CID nor a generation. Relative humidity may be defined as the ratio of the water vapor density (mass per unit volume) to the saturation water vapor density, usually expressed in percent. This means the relative synchronization difference in the network between two base stations. Remote control is a system of controlling a machine or a vehicle from a distance by using radio or electronic signals. Remote Dadio Unit, is connected to BBU with optical fiber, it can support multi-mode and multi-carrier.
Recover mode Rectification Redirect tRNCing Reference cell Reference clock Regular header Relative Humidity Relative Time Difference remote control Remote Radio Unit
Request For Comments A Request for Comments is a formal document from the IETF (Internet Engineering Task Force). It is the result of committee drafting and subsequent review by interested parties. RFC may be informational in nature. Some RFC may be intended to become Internet standards, then the final version of the RFC becomes the standard and no further comments are permitted. Changes can still occur through subsequent RFC that supersede or build on all or parts of previous RFC. RET Reverse Request RF RF circulator RF Phase-Lock Loop Remote Electrical Tilt A receiving end issues a request to a sender after receiving a request from the sender. See Radio Freqency An RF circulator is a three-port passive device used to control the direction of signal flow in a circuit. Phase Lock Loop is a mechanism whereby timing information is transferred within a data stream and the receiver derives the signal element timing by locking its local clock source to the received timing information. See RF Phase-Lock Loop See Request For Comments RNC Frame Number See Relative Humidity Radio Link See Radio Link Control
RF PLL RFC RFN RH RL RLC
Issue 08 (2011-09-30)
75
RLM RLS RNC RNC RNCAP RNCH RND RNS RNTI Roaming
See Radio Link Management Radio Link Set See Radio Network Controller Routing Area Code Radio Network Control Application Part Random Access Channel Radio Network Dimension See Radio Network System See Radio Network Temporary Identifier The ability for a user to function in a serving network different from the home network. The serving network could be a shared network operated by two or more network operator. Robustness is the ability of a system to maintain function even with changes in internal structure or external environment. The SGSN (Serving GPRS Support Node) in a GPRS system will control one or more RA (Routing Area). It is the responsibility of the mobile to keep the SGSN informed as to its current RA. Routing Areas can be made up on one or more cells. Each Routing Area is given a RAI (Routing Area Identification). The Routing Area Identification is composed of the LAC (Location Area Code) and the RAC (Routing Area Code). It is used for paging and registration purposes. A GPRS mobile will perform a Routing Area Update in the Ready and Standby state. The RAU is triggered when the mobile crosses a RA (Routing Area) boundary, or periodically. The time interval being set by the network. A RAU is also performed when the mobile moves from the Idle to the Standby state. This will typically happen when the mobile is powered on. Radio Quality Indication See Reverse Request See Radio Resource See Radio Resource Control A point-to-point bi-directional connection between RRC peer entities on the UE and the UTRAN sides, respectively. A UE has either zero or one RRC connection. Controlling the RRC state transition with different amount of resources consumed in different states See Radio Resource Management See Remote Radio Unit See Received Signal Code Power Retransmission Sequence Number RNC Switch rack RNC Switch Subrack See Received Signal Strength Indicator
robustness Routing Area
Routing Area Identity Routing Area Update
RQI RR RR RRC RRC connection RRC state control RRM RRU RSCP RSN RSR RSS RSSI
Issue 08 (2011-09-30)
76
RT-VBR RTD RTP RTSP RTT RTWP RUS RV RX RX Diversity RxLev RxQual
See Real Time Variable Bit Rate See Relative Time Difference See Real-time Transfer Protocol See Real Time Streaming Protocol Round Trip Time Received Total Wideband Power Remote Upgrade Service Redundancy Version Reception Receive Diversity See Received signal level See Received signal Quality
1.3.19 S
S-RNTI SA SAAL SAI SAP SBT SCCP SCCPCH SCH SCP SCSI SCTP SCUa SD SDH SDP SDT CES SDU Secondary frequency band Serving RNC RNTI See Service Area See Signaling ATM Adaptation Layer See Service Area Identifier See Service Access Point Smart Bias-Tee See Signaling Connection Control Part Secondary-common Control Physical Channel Synchronization Channel See Service Control Point See Small Computer Systems Interface See Stream Control Transmission Protocol RNC GE Switching and Control Unit REV:a See Signal Degrade See Synchronous Digital Hierarchy See Session Description Protocol Structured Data Transfer for CES. The data in ATM AAL1 cells are assigned to some of the 32 E1 timeslots. See Service Data Unit Indicates the frequency band that does not contain the main BCCH frequency in a CoBCCH cell.
Issue 08 (2011-09-30)
77
Sector
A sector is a sub-area of a cell. All sectors within one cell are served by the same base station. A radio link within a sector can be identified by a single logical identification belonging to that sector. An electronic device used to measure a physical quantity such as temperature, pressure or loudness and convert it into an electronic signal of some kind (e.g a voltage). An identifying number used to designate a block of data, an operation, or part of an operation. A conceptual point where a protocol layer offers access to its services to the layer above or below. A Service Area consists of one or more cells within a given LA (Location Area) and may be used to assist in the delivery of location based services.
Sensor Sequence number Service Access Point Service Area
Service Area Identifier The Service Area Identifier is used to identify an area consisting of one or more cells belonging to the same LA (Location Area). Such an area is called a Service Area and can be used for indicating the location of a UE (User Equipment) to the CN (Core Network). The SAC (Service Area Code) together with the PLMN-Id (Public Land Mobile Network Identifier) and the LAC (Location Area Code) will constitute the Service Area Identifier. SAI = PLMN-Id + LAC + SAC. Service Control Point Service Data Unit Service Factor A physical entity in the intelligent network that implements a service control function. Data transferred between adjacent layers in the protocol stack. Huawei RNC provides OMC configurable parameters Service Factor for Iub overbooking. This factor can be configured for RRC signaling, AMR Voice, CS data, and PS data separately by MML. Service Level Agreement (SLA) refers to an agreement signed by and between the customer and the Service Provider (SP) which stipulates the privilege of the service that the customer subscribes when the traffic of the service is transmitted on the SP's network. The SMAP is the client side of the SMS. It falls into two types: the central equipment room part, and the business terminal management part. The central equipment room part can implement integrated maintenance operation such as service management, system datasheet management and network configuration management. The business terminal SMAP can provide the management operations specific to the service data. Genetic name of all BSC boards except the GBAM server and the GOMU. A cell from which the UE receives absolute grants from the NodeB scheduler. A UE has one serving E-DCH cell.
Service Level Agreement Service Management Access Protocol
Service Management Unit Serving E-DCH cell
Serving E-DCH RLS or A set of cells that contains at least one serving E-DCH cell and from which the UE can serving RLS receive one relative grant and combine it with others. The UE has only one serving EDCH RLS. Serving GPRS Support Serving GPRS Support Node (SGSN) performs mobility and data session management Node for GPRS mobiles. In addition, the SGSN performs ciphering and compression of the data transmitted and the routing of IP Packets. Serving Mobile Location Center The SMLC is either a separate network element or integrated functionality in the BSC (Base Station Controller) that contains the functionality required to support LCS (LoCation Services). The SMLC manages the overall co-ordination and scheduling of resources required for the location of a mobile. It also calculates the final location estimate and estimates the achieved accuracy.
Issue 08 (2011-09-30)
78
Serving Radio Network When a RNC (Radio Network Controller) has a RRC (Radio Resource Control) Controller connection with a UE (User Equipment), it is known as the SRNC for that UE. The SRNC is responsible for the users mobility within the UTRAN and is also the point of connection towards the CN (Core Network). Serving Radio Network It provides a connection to UTRAN for each UE. The SRNS is in charge of the radio System connection between a UE and the UTRAN. Session Description Protocol SDP provides a format for describing the session information such as interfaces where the media must terminate and the type of media formats that can be supported. SDP is normally transported as the message body in the SIP methods already discussed. The structure of the protocol is based around the session and media streams that will be supported in the session. Consequently some of the SDP information relates to the overall session, and is known as session level parameters. This information may include the originator of the session and the time it will commence. The media level parameters on the other hand relate to the individual media streams and include information such as media types, transport protocols and port numbers. The set consists of the AMR codec modes that are contained in the set of supported AMR codec modes and are equal to or larger than the guaranteed bit rate. The modes in this set can be selected by AMRC algorithm.
Set of controllable AMR codec modes
Set of supported AMR The set consists of all the AMR codec modes that can be used for the service transport. codec modes The set is decided by the RNC according to the mode set specified by the RAB assignment. SF SF SFH SFN SFP SGSN Shared Network Area See Signal Fail See Spreading Factor See Synthesized Frequency Hopping See System Frame Number See Small Form-Factor Pluggable See Serving GPRS Support Node A Shared Network Area (SNA) consists of one or more location areas. Different SNAs can be overlapped. A specified UE can only get services in the SNA that allows that UE to connect. In this situation, the access control for specified UEs can be enabled by the system. Shielded Twisted Pair STP is a special kind of copper telephone wiring used in some business installations. An outer covering or shield is added to the ordinary twisted pair telephone wires; the shield functions as a ground. See Soft HandOver
SHO
Short Message Service A service that enables mobile phones to send/receive and enables service providers to send text messages whose length is up to 140 bytes. Short Message Service To allow SMS (Short Message Service) messages to be sent from your mobile phone Centre you will require a SMSC number. This will instruct your mobile phone to send all SMS messages to this centre. The SMSC forwards the short message to the indicated destination. SI SIB
Issue 08 (2011-09-30)
System Information See System Information Block

SIB_POS SID Signal Degrade Signal Fail Signal Noise Ratio
System Information Block Position See Silence Insertion Descriptor SD is a signal indicating the associated data has degraded in the sense that a degraded defect (e.g., dDEG) condition is active. SF is a signal indicating the associated data has failed in the sense that a near-end defect condition (not being the degraded defect) is active. The SNR or S/N (Signal to Noise Ratio) of the amplitude of the desired signal to the amplitude of noise signals at a given point in time. SNR is expressed as 10 times the logarithm of the power ratio and is usually expressed in dB (Decibel). A ratio between the wanted signal power in the channel and the interference in the channel. The exchange of information specifically concerned with the establishment and control of connections, and with management, in a telecommunications network.
Signal to Interference Ratio Signaling
Signaling Process Unit A signaling processing unit is used in producing a prediction signal and comprises three prediction circuits (22, 23, 31) and a selection circuit (24) coupled to the prediction circuits. Signaling ATM Adaptation Layer Signaling Connection Control Part Signaling link Signaling Link Code In ATM (Asynchronous Transfer Mode), the "SAAL (ATM Adaptation Layer for Signalling)" provides reliable transport of signalling messages between peer entities. These signalling messages are carried over a PVC (Permanent Virtual Circuit). The primary function of Signaling Connection Control Part is to provide a means for the transfer of messages between any two signaling points in the same or different SS7 networks. No.7 signaling link, used to connect the signaling points in the SS7 network and to transfer signaling information. A field with certain signaling network management messages, which indicates the particular signaling link to which the message refers among those interconnecting the two involved signaling points. In SS7, each NE is assigned a network identifier, which is a 14-bit signaling point code or a 24-bit signaling code.Within a PLMN, an NE that is assigned a signaling point can be uniquely addressed in the SS7 network and can communicate with other NEs. An SPC refers to a binary code used to uniquely identify a signaling point in a signaling network.
Signaling point
Signaling Point Code
Signaling Radio Bearer The RRC (Radio Resource Control) connection process will establish the RB (Radio Bearer) available for usage by RRC messages on the DCCH (Dedicated Control Channel) and CCCH (common Control Channel). These Radio Bearers are identified as a SRB (Signalling Radio Bearer). Signaling Transfer Point Signaling Transport Optical Carrier (OC) levels from 51.8 Mbps (OC-1) to 9.95 Gbps (OC-192). Signaling Transport (SIGTRAN) refers to a protocol stack for the transport of Switched Circuit Network (SCN) signaling protocols (SS7/C7) over an IP network. SIGTRAN is applied to IP network to support the IP interworking between the traditional narrowband telecommunication network PSTN and wideband network. See Signaling Transport
SIGTRAN
Issue 08 (2011-09-30)
80
Silence Insertion Descriptor SIM Simple Mail Transfer Protocol Simple Network Management Protocol Simple Network Time Protocol Single channel
A frame that conveys information on the acoustic background noise. See Subscriber Identity Module The TCP/IP (Transmission Control Protocol/Internet Protocol) protocol which facilitates the transfer of electronic-mail messages, specifies how two systems are to interact, and the format of messages used to control the transfer of electronic mail. Simple Network Management Protocol is part of the TCP/IP suite and is used to control and manage IP gateways and other network functions. A protocol that is adapted from the Network Time Protocol (NTP) and synchronizes the clocks of computers over the Internet. The channel composed by two half rate sub-timeslots is called a Single channel when one sub-timeslot is occupied while the other is idle.
Single-Hop/Multi-Hop In the IP network, one hop means that a packet arrives at the destination with a route forwarding. Single-hop means that a packet arrives at the destination with the route forwarding that occurs only once. Multi-hop means that a packet arrives at the destination with the route forwarding that occurs several times. SIR Site Maintenance Terminal System SIWF SLA SLC Slow Frequency Hopping Slow pull-in mode See Signal to Interference Ratio Site Maintenance Terminal System is a software item of the LMT software package. It is used for the local maintenance and management of sites. See The Shared InterWorking Function See Service Level Agreement See Signaling Link Code Slow Frequency Hopping is a technique in which the carrier frequency changes using a predetermined hopping pattern. The hopping rate is slower than the bit rate. When the external reference clock source is operational and the offset between the source and the center frequency saved on the system is within 0.4 Hz, the system adjusts the local oscillator with a smaller step size to smoothly switch the system to locked mode. During the slow pull-in phase, the frequency offset is also compensated as required. Small Computer Systems Interface Small Form-Factor Pluggable SMAP SMLC SMS SMSC SMTP SMU SN Small Computer Serial Interface is a standard for computer system communication. commonly used for storage devices and scanners, SCSI is an ANSI (American National Standards Institute) standard. A specification for a new generation of optical modular transceivers. See Service Management Access Protocol See Serving Mobile Location Center See Short Message Service See Short Message Service Centre See Simple Mail Transfer Protocol See Service Management Unit See Sequence number
Issue 08 (2011-09-30)
81
SNA SNMP SNR SNTP Soft HandOver Softer handover
See Shared Network Area See Simple Network Management Protocol See Signal Noise Ratio See Simple Network Time Protocol Soft handover is a category of handover procedures where the radio links are added and abandoned in such manner that the UE always keeps at least one radio link to the UTRAN. A form of handover applicable to CDMA-based networks where the system hands over from one sector of a base station to another using a different spreading code. As it is less complicated than soft handover it is given the name, softer handover. See Synchronous Optical Network RNC initiating an SRNS relocation RNS initiating an SRNS relocation An open loop multi-antenna transmission method adopted in 3G standard. This technique uses the space-time block code at the basestation to combat deep channel fading. See Signaling Point Code In the ATM (Asynchronous Transfer Mode) signalling layers, SSCOP provides mechanisms for the establishment and release of connections and the reliable exchange of signalling information between signalling entities. In the ATM (Asynchronous Transfer Mode) signalling layer the SSCF maps the requirements of the layer above to the requirements of SSCOP (Service Specific Connection Oriented Protocol). Intelligibility of speech information. In the GSM communication system, the versions of the speech coding/decoding algorithms are categorized into full-rate speech versions 1, 2, and 3 and half-rate speech versions 1, 2, and 3. In a CDMA (Code Division Multiple Access) system, the number of chips per data symbol is called the SF (Spreading Factor). The lower the spreading factor the higher the data rate. See Signaling Process Unit RNC Signaling Processing Unit REV:a See Structured Query Language See Signaling Radio Bearer See Serving Radio Network Controller See Serving Radio Network System See Supplementary Service See Special Service Coordinate Function See Special Service Connect Orient Protocol See Synchronous Transport Module-1 Smart TMA
SONET Source RNC Source RNS Space Time Transmit Diversity SPC Special Service Connect Orient Protocol Special Service Coordinate Function Speech intelligibility Speech version
Spreading Factor
SPU SPUa SQL SRB SRNC SRNS SS SSCF SSCOP STM-1 STMA
Issue 08 (2011-09-30)
82
STP STP Stream
See Shielded Twisted Pair See Signaling Transfer Point Stream refer to the directional logical path from one end to anther end in an SCTP link.
Stream Control Streaming Control Transmission Protocol is a reliable transport protocol operating on Transmission Protocol top of IP. It provides acknowledged error free non duplicated transfer of data. STCP also detects data corruption, loss of data and duplication of data by using checksums and sequence numbers. A selective retransmission mechanism is applied to correct loss or corruption of the data. Structured Query Language STTD Sub-board A standardized language for defining and manipulating data in a relational database. See Space Time Transmit Diversity A small board attached to the main board to provide certain functions. There are several types of sub-boards: optical sub-board, E1/T1 sub-board, and clock sub-board. Optical sub-board enables access of optical cables. E1/T1 sub-board enables access of E1/T1 cables. Clock sub-board enables access of timing signals. An IPv6 base header, an IPv6 extension header, an IPv4 header, a UDP header, or a TCP header. A chain of subheaders. A large network can be divided into a number of smaller networks according to a rule, for example, according to different districts. This facilitates the management of the large network. In the topology view, this type of a smaller network is termed subnet. Usually referred to as a SIM card, the SIM (Subscriber Identity Module) is the user subscription to the mobile network. The SIM contains relevant information that enables access onto the subscripted operator's network.
Subheader Subheader chain Subnet
Subscriber Identity Module
Supplementary Service Common capabilities of GSM phones. They are related to real-time and instantaneous telephony services. The GSM system provides three types of services: basic teleservices, bearer services, and supplementary services. Supplementary services are not provided separately and must be offered together with or in association with basic teleservices. Supplementary services include line identification service and call forwarding service. Supplementary service A service which modifies or supplements a basic telecommunication service. Consequently, it cannot be offered to a user as a standalone service. It must be offered together with or in association with a basic telecommunication service. The same supplementary service may be common to a number of basic telecommunication services. Support Switch mode SWM Synchronous Digital Hierarchy Synchronous Optical Network A part used to support and fix a cabinet on the antistatic floor The 1+1 protect mode is classified into unidirectional mode and 1+1 bidirectional mode. SoftWare Management The SDH is a hierarchical set of digital transport structures, standardized for the transport of suitably adapted payloads over physical transmission networks. SONET defines interface standards at the physical layer of the OSI.
Issue 08 (2011-09-30)
83
Synchronous Transport Module-1
An STM is the information structure used to support section layer connections in the SDH. It consists of information payload and Section Overhead (SOH) information fields organized in a block frame structure which repeats every 125 s. The information is suitably conditioned for serial transmission on the selected media at a rate which is synchronized to the network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Higher capacity STMs are formed at rates equivalent to N times this basic rate. STM capacities for N = 4, N = 16 and N = 64 are defined; higher values are under consideration.
Synthesized Frequency A hopping method in which the radios keep synchronized with the transmission frequency of the TDMA frame. In this method a voice call remains associated with one Hopping transmitter. System Frame Number The system frame number is used to uniquely identify a random access. System Information Block The system information elements are broadcast in system information blocks. A system information block groups together system information elements of the same nature.
1.3.20 T
TA Tandem Free Operation Target RNC Target RNS Task per second TBF TBUS TC TCA TCH TCHF TCHH TCU TDM See Timing Advance Tandem Free Operation is the configuration of a connection with two transcoders that support the TFO protocol and whose external coding schemes are compatible, thus enabling compressed speech to pass between them. RNC serving as the target of SRNS relocation RNS serving as the target of SRNS relocation Indicates the task that is performed each second in the system. See Temporary Block Flow Time BUS See Transcoder Traffic Conditioning Agreement See Traffic Channel Full-rate speech channel Half-rate speech channel Temperature Control Unit Technique in which information from multiple channels can be allocated bandwidth on a single wire based on preassigned time slots. Bandwidth is allocated to each channel regardless of whether the station has data to transmit. Compare with ATDM, FDM, and statistical multiplexing. See Time Division Multiple Access See Terminal Equipment Identifier
TDMA TEI
Telecommunication The Telecommunications Management Network is a protocol model defined by ITU-T Management Network for managing open systems in a communications network. An architecture for management, including planning, provisioning, installation, maintenance, operation and administration of telecommunications equipment, networks and services.
Issue 08 (2011-09-30)
84
Temporary Block Flow A TBF is a physical connection used by the two RR peer entities to support the unidirectional transfer of LLC PDUs on packet data physical channels. Temporary Mobile Subscriber Identity Terminal Equipment Identifier Terminal Multiplexer TF restriction TF restriction times TFC TFCI TFCS TFI TFO TFO MESSAGE TFRC TFRC selection The TMSI refers to a temporary MS identifier assigned by the base station when an MS is connected to the network. The TMSI is stored in the VLR and SIM. When the MS is connected to the network, the TMSI is used by the MS to originate or receive calls. Terminal Equipment Identifier. The Terminal Endpoint Identification value used to select an entity for which protocol activity will be monitored or retrieved. This parameter is used only to specify a TEI value at layer 2 for the capture entity. Terminal Multiplexer. The path terminating element (PTE) that acts as a concentrator of E1s as well as other tributary signals. A procedure for changing the TFmax of the transport format set based on the rate restriction coefficient. The number of attempts that TF restriction can be performed. See Transport Format Combination See Transport Format Combination Indicator See Transport Format Combination Set See Transport Format Indicator See Tandem Free Operation The TFO MESSAGE is the in-band signaling used for TFO negotiation between TCs. Transport Format and Resource Combination Selection of an appropriate transport format and resource for the data to be transmitted on HS-DSCH.
The Shared Shared InterWorking Function (SIWF) is a network function that provides interworking InterWorking Function for data/fax calls. SIWF consists of a SIWF Controller (SIWFC) functionality located in MSCs and SIWF Server(s) (SIWFS) located in the PLMN. An SIWFS contains IWF capabilities. An SIWFS can be accessed by several other network nodes e. g. any MSC in the same PLMN. Third Generation Partnership Project THP threshold Tight BCCH An international standardization organization founded in 1998. It consists of telecommunication standardization organizations in multiple countries and areas. Traffic Handling Priority The threshold defines the allowable warp range between the actual counter value and the history average value of the counter. Tight BCCH refer to BCCH Dense Frequency Multiplexing.In tight BCCH frequency reuse mode, the TCHs on the BCCH frequency is assigned to the MSs near the BTS. This decreases the requirements for the BCCH frequency reuse intensity and improves the frequency utilization.
Time Division Multiple A communications technique that uses a common channel (multipoint or broadcast) for Access communications among multiple users by allocating unique time slots to different users. (188) Note: TDMA is used extensively in satellite systems, local area networks, physical security systems, and combat-net radio systems.
Issue 08 (2011-09-30)
85
Time Of Arrival
The reference point for signal arrival time, TOA (Time Of Arrival) is defined as the start point of a time slot. Used for LCS (LoCation Services), and similar to E-OTD (Enhanced - Observed Time Difference) in that the time difference of the signal arriving at different base stations is used to calculate the location of a mobile device. The difference between TOA and E-OTD is that no overlay network is needed for TOA. Mobile networks are currently do not employ these procedures instead cells are synchronized using a common timing reference. Continuously repeating interval of time or a time period in which two devices are able to interconnect. Time Switched Transmit Diversity (TSTD) is a technique utilizing multiple transmit stations to originate the downlink signal and improve performance. The transmit station used is determined by a fixed selection pattern similar to frequency hopping. Symbolic representation for a timer object (e.g., a timer object may have a primitive designated as T-Start Request). Various MAC entities utilize timer entities that provide triggers for certain MAC state transitions. A process for combining signals from several separate slots for transmission in the same direction over a common bearer channel.
Time Slot Time Switched Transmit Diversity Timer
Timeslot multiplex
Timeslot cross function A function that enables crossing of E1/T1 timeslots on the Physical Medium sublayer of the physical layer so as to provide an exchange path between transport devices. For example, timeslots 2, 3, 4, and 5 can be crossed to timeslots 12, 13, 14, and 15 through this function. Timeslot de-multiplex Timeslot Interval Timing Advance TM TMA TMN TMSI TNL TOA TOW tower amplification module A process for separateing signals that have been combined for transmission over a communications channel as a single signal. Hardware interruption every 577 s specified in the GSM 0502 protocol. A signal sent by the BTS to the MS which the MS uses to advance its timings of transmissions to the BTS so as to compensate for propagation delay. See Terminal Multiplexer See tower amplification module See Telecommunication Management Network See Temporary Mobile Subscriber Identity Transport Network Layer See Time Of Arrival Time Of Week A Tower Mounted Amplifier (TMA) is a lower noise amplifier installed close to the antenna, for example, on a tower. It amplifies weak signals from the antenna, thus improving system coverage, enhancing receiver sensitivity and reducing the transmit power of the UE. See Transmit Power Control See Tributary Protect Switch TCH Rate Adjust A logical channel used for the transporting the voice coding information or the user data.
TPC TPS TRA Traffic Channel
Issue 08 (2011-09-30)
86
Training Sequence Code Transceiver Transcoder Transcoder and Rate Adaptor Unit
Used mainly in TDMA (Time Division Multiple Access) systems the training sequence is used to maintain timing and equalize the channel. This helps reduce the impact of ISI (Inter Symbol Interference) and multipath effects. A transmitter and receiver housed together in a single unit and having some circuits in common, often for portable or mobile use. This is an entity that performs a transcoding function for speech channels and RA (Rate Adaptation) for data channels. This is an entity that performs a transcoding function for speech channels and RA (Rate Adaptation) for data channels.
Transmission interface Demarcation point between the transmission equipment prepared by the operator and box the base station equipment supplied by a vendor. Transmit Diversity Transmit Diversity Transmit Power Control Transport Format Combination The transmit diversity is a technology that optimizes the downlink signals by realizing the man-made multi-path. The transmit diversity is a technology that optimizes the downlink signals by realizing the man-made multi-path. Transmit Power Control is a technical mechanism used within some networking devices in order to prevent too much unwanted interference between different wireless networks (e.g. the owner's network and the neighbour's network). A Transport Format Combination is defined as the combination of currently valid Transport Formats on all Transport Channels of an UE, i.e. containing one Transport Format from each Transport Channel.
Transport Format A Transport Format Combination Indicator is a representation of the current Transport Combination Indicator Format Combination. Transport Format Combination Set Transport Format Indicator TRAU TrFO Tributary Protect Switch Triplet, GSM authentication vector TRM TRX TSC TSN TSTD TVM A Transport Format Combination Set is defined as a set of Transport Format Combinations to be used by an UE. A label for a specific Transport Format within a Transport Format Set. See Transcoder and Rate Adaptor Unit Transcoder Free Operation Tributary protection switching, a function provided by the equipment, is intended to protect N tributary processing boards through a standby tributary processing board. Temporary protocol data of authentication and key ,which enables GSM AKA function for a particular user in a VLR/SGSN. A triplet consists of three elements: Random Number (RAND), Signed Response (SRES), and Ciphering Key (Kc). Transmission Resource Management A TRX is a radio transceiver entity. Eight timeslots are mapped to one TRX. See Training Sequence Code Transmission Sequence Number See Time Switched Transmit Diversity Traffic Volume Measurement
Issue 08 (2011-09-30)
87
1.3.21 U
UAP UBFA UBR UBR+ UDT CES UE UE tRNCing United Analysis and Precision Check Universal BBU Fan unit type A(2U) See Unspecified Bit Rate Unspecified Bit Rate Plus Unstructured Data Transfer for CES. The data in ATM AAL1 cells are assigned to the 32 E1 timeslots except timeslot 0 and timeslot 16. See User Equipment The UE tracing consists of the following two types: l UE tracing (on the user plane and the signaling plane) This task is performed to trace the call-related information of a specified UE on the signaling plane and on the user plane during a call. UE tracing (standard interface) This task is performed to trace signaling messages of a specified UE over Iu, Iur, Iub, and Uu interfaces during a call.
l UEA UIA UL UM
UMTS Encryption Algorithm UMTS Integrity Algorithm See Uplink See Unacknowledged Mode
Um Interface Software Um interface software synchronization can convert an asynchronous network into a Synchronization synchronous network. In cooperation with other related techniques, this technique eliminates the random and unpredictable interference and thus enhances the system capacity. Um Interface Synchronization UMTS Um interface synchronization involves software synchronization on the Um interface and synchronization of the entire network through GPS. See Universal Mobile Telecommunications System/Universal Mobile Telecommunication System/Universal Mobile Telecommunication Services
UMTS security context A state established between a UE and a serving network domain as a result of the execution of UMTS AKA. In this state, both sides store UMTS security context data. The data consists of at least UMTS CK, IK and key set identifier (KSI). When CK or IK is converted into Kc to work in a GSM BSS, both sides remain in the UMTS security context state. Unacknowledged Mode The unacknowledged mode is utilized for transfers of cell broadcast messages or for transfers of certain RRC messages. UNI UNI mode See User-Network Interface In UNI mode, an ATM cell is directly carried on a E1/T1 and the bits of the ATM cell are sequentially mapped to the valid timeslots on the E1/T1.
Issue 08 (2011-09-30)
88
Universal Mobile Telecommunications System/Universal Mobile Telecommunication System/Universal Mobile Telecommunication Services
A 3G mobile technology that will deliver broadband information at speeds up to 2Mbit s/sec. Besides voice and data, UMTS will deliver audio and video to wireless devices anywhere in the world through fixed, wireless and satellite systems.
Universal Terrestrial UTRAN is a conceptual term identifying that part of the network which consists of RNCs Radio Access Network and Node Bs between Iu and Uu interfaces. Universal Time Coordinates Unspecified Bit Rate The basis for coordinated distribution of time signals, counted from 0000 at midnight. When an accuracy better than one second is not required, Universal Time can be used to mean UTC (Coordinated Universal Time). No commitment to transmission. No feedback to congestion. This type of service is ideal for the transmission of IP datagrams. In case of congestion, UBR cells are discarded, and no feedback or request for slowing down the data rate is delivered to the sender. RNC 4-port ATM/Packet over Unchannelized Optical STM-1/OC-3c Interface unit REV:a A process running on the GBAM server or the GOMU to implement remote upgrade of the BSC software. An "uplink" is a unidirectional radio link for the transmission of signals from a MS to a base station, from a Mobile Station to a mobile base station or from a mobile base station to a base station. See UTRAN Registration Area An RRC connected mode where neither DCCH nor DTCH is available. A device allowing a user access to network services. ATM Forum specification that defines an interoperability standard for the interface between ATM-based products (a router or an ATM switch) located in a private network and the ATM switches located within the public carrier networks. Also used to describe similar connections in Frame Relay networks. User Services Identity Module See Universal Time Coordinates See Universal Terrestrial Radio Access Network The UTRAN Registration Area is an area covered by a number of cells. The URA is only internally known in the UTRAN.
UOIa Upgrade process Uplink
URA URA_PCH User Equipment User-Network Interface
USIM UTC UTRAN UTRAN Registration Area
1.3.22 V
Value added services VC Trunk VCI Services other than basic telecommunications service for which additional charges may be incurred, for example, VPMN, VOD, and mobile TV See Virtual Container Trunk See Virtual Channel Identifier
Issue 08 (2011-09-30)
89
Virtual Channel Identifier Virtual Container Trunk Virtual IP Address
The identifier in the ATM (Asynchronous Transfer Mode) cell header that identifies to which virtual channel the cell belongs. VC Trunk refers to the logical path formed by some cascaded VCs. The IP address that is used by the active node for the communication between the host and the LMT.
Virtual Path Identifier The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to which VP (Virtual Path) the cell belongs. Virtual Private Network Virtual Router Redundancy Protocol The extension of a private network that encompasses encapsulated, encrypted, and authenticated links across shared or public networks. VPN connections can provide remote access and routed connections to private networks over the Internet. An Internet protocol, provides one or more than one backup route when static routing is used in local area network.
visitor location register Data base connected to one or several mobile service switching centres which contains a copy of information in home location registers for all mobile subscribers present in the cells covered by the centres. VLAN VLR Virtual Local Area Network See visitor location register
Voltage Standing Wave The ratio of the maximum/minimum values of standing wave pattern along a Ratio transmission line to which a load is connected. VSWR value ranges from 1 (matched load) to infinity for a short or an open load. For most base station antennas the maximum acceptable. VPI VPN VQI VRRP VSWR See Virtual Path Identifier See Virtual Private Network Voice Quality Index See Virtual Router Redundancy Protocol See Voltage Standing Wave Ratio
1.3.23 W
Wait To Restore WCDMA WGS84 wideband A transitional state which waits for a predetermined time after a failure has been resolved prior to entering a no request (IDLE) state. See Wideband CDMA World Geographical System 1984 The property of any communications facility, equipment, channel, or system in which the range of frequencies used for transmission is greater than 0.1 % of the midband frequency. An ITU (International Telecommunications Union) standard derived from CDMA (Code Division Multiple Access) technology. General method for speech preprocessing, like Haming window. Overvoltage Protection Board
Wideband CDMA Window WOPB
Issue 08 (2011-09-30)
90
WRBS internal subnet Internal subnet segment of all WCDMA RNC Business Subracks (WRBSs). All boards segment in the WRBSs have the IP addresses in this network segment. WRED WRR WS WTR Weighted Random Early Detection Weighted Round Robin Work Station See Wait To Restore
1.3.24 X
XML XMU XRES See Extensible Markup Language General name for BTS3012 DTMU, BTS3012AE DTMU, BTS3006C DMCM, and BTS3002E DMCM. The abbreviation of Expected Response. In the UMTS authentication process the network sends RAND (Random Number) to the UMTS Subscriber, XRES is the value that the network is looking for to indicate a positive response.
Issue 08 (2011-09-30)
91
2 GBSS Feature Parameter Description
2
Purpose
l l l l l l
About This Chapter
BSS features consist of basic BSS features and optional BSS features. This document describes the following aspects of the BSS features: Change History Overview Technical Description Engineering Guidelines Maintenance Information Reference Documents
Product Version
The following table lists the product versions related to this document. Product Name BSC BTS Product Model BSC6900 BTS3012 BTS3012AE BTS3006C BTS3002E BTS3900 GSM BTS3900A GSM DBS3900 GSM
Issue 08 (2011-09-30)
Product Version Refer to the version information in each feature. Refer to the version information in each feature. Refer to the version information in each feature. Refer to the version information in each feature. Refer to the version information in each feature. Refer to the version information in each feature. Refer to the version information in each feature. Refer to the version information in each feature.
92
Product Name
Product Model BTS3900L GSM
Product Version Refer to the version information in each feature.
Organization
2.1 Tutorial Introduction to Basic Features of GBSS9.0 2.2 Tutorial Introduction to Optional Features Of GBSS9.0 2.3 2-Antenna Receive Diversity 2.4 2G/3G Interoperability 2.5 2G/3G Interoperability (TDD) 2.6 Abis Bypass 2.7 Acoustic Echo Cancellation 2.8 AFC 2.9 AMR 2.10 Antenna Frequency Hopping 2.11 AQM 2.12 Assignment and Immediate Assignment 2.13 Ater Compression Transmission 2.14 Automatic Level Control 2.15 Automatic Noise Compensation 2.16 Automatic Noise Restraint 2.17 BCCH Dense Frequency Multiplexing 2.18 BSC Node Redundancy 2.19 BSS Local Switching 2.20 BTS Combined Cabinets and Cabinet Groups 2.21 BTS Ring Topology 2.22 Cell Broadcast 2.23 Channel Management 2.24 Ciphering 2.25 Discontinuous Transmission and Discontinuous Reception 2.26 Dual Carriers in Downlink 2.27 DTM 2.28 Dynamic Channel Conversion
2.29 Easy GSM 2.30 EFR 2.31 EGPRS2 2.32 eMLPP 2.33 EMR 2.34 EPLC 2.35 Flex Abis 2.36 Flex MAIO 2.37 Flow Control 2.38 Frequency Hopping 2.39 Four-Way Receive Diversity 2.40 GPRS/EGPRS Channel Management 2.41 GPRS/EGPRS Connection Control and Transfer 2.42 GPRS/EGPRS Link Quality Control 2.43 GPRS/EGPRS Overview 2.44 GPRS/EGPRS QoS 2.45 Half-Rate Speech 2.46 Handover 2.47 Handover Re-establishment 2.48 High-Speed Signaling 2.49 Idle Mode Behavior 2.50 Intelligent Power Consumption Decrease 2.51 IP BSS 2.52 IP Transport Architecture Description 2.53 Latency Reduction 2.54 Local Multiple Signaling Points 2.55 Location Service 2.56 MSC Pool 2.57 Multiband Network 2.58 Multi-Site Cell 2.59 NACC 2.60 NC2 2.61 Networking Modes
2.62 PBT 2.63 PICO Automatic Configuration and Planning 2.64 Power Control 2.65 PS Handover 2.66 RAN Sharing 2.67 Robust Air Interface Signaling 2.68 Semipermanent Connection 2.69 SGSN Pool 2.70 Soft-Synchronized Network 2.71 TC Pool 2.72 TFO 2.73 Transmit Diversity 2.74 TRX Cooperation 2.75 VGCS/VBS 2.76 Voice Quality Index 2.77 WB AMR 2.78 14-Digit Signaling Point Code 2.79 2G/3G Co-Transmission by TDM Switching 2.80 A Interface Circuit Management 2.81 A Interface Protocol Process 2.82 A Interface Occupation Rate Monitoring 2.83 Adjustment of Adaptive Timing Advance 2.84 Ater Interface 4:1 Multiplexing 2.85 Authentication 2.86 Board Switchover 2.87 BSC Cabinet/Subrack Sharing 2.88 BTS Power Management 2.89 Call Control 2.90 Call Reestablishment 2.91 Cell Frequency Scan 2.92 Cell Tracing 2.93 Man Machine Language (MML) 2.94 Operation & Maintenance System One-Key Recovery
2.95 Radio Bearer Services 2.96 Radio Link Management 2.97 Remote EAC Maintenance 2.98 Remote Upgrade of the BSC&BTS Software 2.99 Signaling Transport Point(STP) 2.100 Support of Daylight Saving Time 2.101 Supporting Three-Digit MNC 2.102 TCH Re-assignment 2.103 TRX Management 2.104 System Redundancy 2.105 Operate System Security Management 2.106 BSC/RNC Resource Sharing 2.107 Connection with TMA (Tower Mounted Amplifier) 2.108 Remote Electrical Tilt 2.109 TX Diversity and RX Diversity 2.110 BTS/NodeB Clock 2.111 BSC/RNC Clock 2.112 14.4 Kbps Circuit Switched Data 2.113 Guaranteed Emergency Call 2.114 BTS GPS Synchronization 2.115 BTS Test Function 2.116 Connection Inter BSC over IP 2.117 Encrypted Network Management 2.118 End-to-End MS Signaling Tracing 2.119 Flex Ater 2.120 TrFO 2.121 Forced System Information Sending by OMC 2.122 Performance Management 2.123 O&M of BTS 2.124 O&M of BSC 2.125 Integrated Network Management Interface 2.126 Reporting the Temperature List of the BTS Equipment Room 2.127 Inventory Management
2.128 Maintenance Mode Alarm 2.129 Multi-Cell Function 2.130 Satellite Transmission 2.131 NAT Beside OM 2.132 Radio Common Channel Management 2.133 Radio Dedicated Channel Management 2.134 Security Management 2.135 OML Backup 2.136 2G/3G Neighboring Cell Automatic Optimization 2.137 Intelligent Shutdown of TRX Due to PSU Failure 2.138 License Control for Urgency 2.139 Faulty Management 2.140 Configuration Management 2.141 DBS Topology Maintenance 2.142 BTS/NodeB Software Management 2.143 BTS/NodeB Software USB Download 2.144 BSC/RNC Software Management 2.145 License Management 2.146 Network Structure
Issue 08 (2011-09-30)
97
2.1 Tutorial Introduction to Basic Features of GBSS9.0

Purpose: Guide the user to find the GBSS features in the GBSS Feature Documentation quickly. M N E NA Maintenance (No change) New feature in the corresponding release Enhanced feature in the corresponding release Not correlate with the network elements or the features
Feature ID
Description System Improvement
GBS S9.0
Mapping Relationship with FPD
GBFD-1 10000 GBFD-1 10030
GBSS9.0 System Improvement 3GPP Protocol Compliance Radio Service Function
N E
NA NA
GBFD-1 10101 GBFD-1 10201 GBFD-1 10202 GBFD-1 10203 GBFD-1 10204 GBFD-1 10205
Frequency Band Telephone Service (TS11) Emergency Call Service (TS12) Point To Point Short Message Service (TS21, TS22) G3 Fax (TS61, TS62) Bearer Service Mobility Management
M M M M M M
Multiband Network Radio Bearer Services Radio Bearer Services Radio Bearer Services Radio Bearer Services Radio Bearer Services
GBFD-1 10301 GBFD-1 10302 GBFD-1 10303

Issue 08 (2011-09-30)
Location Updating IMSI Detach Paging
M M M
Idle Mode Behavior Idle Mode Behavior Idle Mode Behavior
98
Feature ID GBFD-1 10304 GBFD-1 10601 GBFD-1 10607 GBFD-1 10608 GBFD-1 10401 GBFD-1 10402
Description Authentication HUAWEI I Handover Direct Retry SDCCH Handover Basic Cell Selection Basic Cell Re-selection Connection Management
GBS S9.0 M M M M M M
Mapping Relationship with FPD Authentication Handover Handover Handover Assignment and Immediate Assignment Assignment and Immediate Assignment
GBFD-1 10501 GBFD-1 10502 GBFD-1 10503 GBFD-1 12501
Call Control Assignment and Immediate Assignment Call Reestablishment TCH Re-assignment Radio Resource Management
M M M M
Call Control Assignment and Immediate Assignment Call Reestablishment TCH Re-assignment
GBFD-1 11001 GBFD-1 11002 GBFD-1 11003 GBFD-1 11004 GBFD-1 11005
TRX Management Radio Link Management Radio Common Channel Management Radio Dedicated Channel Management Enhanced Channel Assignment Algorithm Operation and Maintenance
M M M M M
TRX Management Radio Link Management Radio Common Channel Management Radio Dedicated Channel Management Channel Management
MRFD-2 10301
Configuration Management
Configuration Management
Issue 08 (2011-09-30)
99
Feature ID MRFD-2 10302 MRFD-2 10303 MRFD-2 10304 MRFD-2 10305 MRFD-2 10309 MRFD-2 10310 GBFD-1 11202 GBFD-1 11203 GBFD-1 11207 GBFD-1 11210 GBFD-1 16501
Description Performance Management Inventory Management Faulty Management Security Management DBS Topology Maintenance BTS/NodeB Software USB Download O&M of BTS O&M of BSC BTS Test Function Integrated Network Management Interface Man Machine Language (MML) Software Management
GBS S9.0 M M M M M N M M M M M
Mapping Relationship with FPD Performance Management Inventory Management Faulty Management Security Management DBS Topology Maintenance BTS/NodeB Software USB Download O&M of BTS O&M of BSC BTS Test Function Integrated Network Management Interface Man Machine Language (MML)
MRFD-2 10401 MRFD-2 10402 GBFD-1 11213 MRFD-2 10403
BSC/RNC Software Management BTS/NodeB Software Management Remote Upgrade of the BSC&BTS Software License Management GBSS Network Architecture
M E M M
BSC/RNC Software Management BTS/NodeB Software Management Remote Upgrade of the BSC&BTS Software License Management
GBFD-1 11501 GBFD-1 11502
BTS Combined Cabinet BTS Hybrid Cabinet Group
M M
BTS Combined Cabinets and Cabinet Groups BTS Combined Cabinets and Cabinet Groups
Issue 08 (2011-09-30)
100
Feature ID GBFD-1 18801 MRFD-2 10204 MRFD-2 10205 MRFD-2 10206 GBFD-1 18621
Description BSC Cabinet/Subrack Sharing Star Topology Chain Topology Tree Topology Connection Inter BSC over IP System Reliability
GBS S9.0 M M M M M
Mapping Relationship with FPD BSC Cabinet/Subrack Sharing Network Structure Network Structure Network Structure Connection Inter BSC over IP
GBFD-1 11701 GBFD-1 11705 GBFD-1 12301 GBFD-1 11214 GBFD-1 11211 MRFD-2 10101 MRFD-2 10102 MRFD-2 10103 MRFD-2 10104 GBFD-1 17804
Board Switchover GSM Flow Control Remote EAC Maintenance Operation & Maintenance System One-Key Recovery Reporting the Temperature List of the BTS Equipment Room System Redundancy Operate System Security Management Link aggregation BSC/RNC Resource Sharing Intelligent Shutdown of TRX Due to PSU Failure Basic features
M M M M M M M N N N
Board Switchover Flow Control Remote EAC Maintenance Operation & Maintenance System One-Key Recovery Reporting the Temperature List of the BTS Equipment Room System Redundancy Operate System Security Management IP Transport Architecture Description BSC/RNC Resource Sharing Intelligent Shutdown of TRX Due to PSU Failure
GBFD-1 10901 GBFD-1 10801
Adjustment of Adaptive Timing Advance Processing of Measurement Report
M M
Adjustment of Adaptive Timing Advance Handover
Issue 08 (2011-09-30)
101
Feature ID GBFD-1 10802 GBFD-1 11101 GBFD-1 11102 GBFD-1 11901 GBFD-1 16101 GBFD-1 13001 GBFD-1 12401 GBFD-1 11806 GBFD-1 11802 MBFD-2 10801 MBFD-2 10802 GBFD-1 12203 GBFD-1 11301 GBFD-1 14802 GBFD-1 11601 GBFD-1 10703
Description Pre-processing of Measurement Report System Information Sending Forced System Information Sending by OMC Supporting Three-Digit MNC Support of Daylight Saving Time SDCCH Dynamic Adjustment Cell Frequency Scan STP (Signaling Transfer Point) 14-Digit Signaling Point Code Interface Message Tracing User Signaling Tracing Cell Tracing LAPD Multiplexing at Abis Interface Discontinuous Reception (DRX) BTS Power Management Enhanced Power Control Algorithm Interface Features
GBS S9.0 M M M M M M M M M M M M M M M M
Mapping Relationship with FPD Handover Idle Mode Behavior Forced System Information Sending by OMC Supporting Three-Digit MNC Support of Daylight Saving Time Dynamic Channel Conversion Cell Frequency Scan Signalling Transfer Point (STP) 14-Digit Signaling Point Code Interface Message Tracing User Signaling Tracing Cell Tracing Networking Modes Discontinuous Transmission and Discontinuous Reception BTS Power Management Power Control
GBFD-1 11801 GBFD-1 19001
Ater Interface 4:1 Multiplexing Gb Interface Function
M M
Ater Interface 4:1 Multiplexing GPRS/EGPRS Overview
Issue 08 (2011-09-30)
102
Feature ID GBFD-1 11803 GBFD-1 11804 GBFD-1 11805
Description A Interface Circuit Management A Interface Protocol Process A Interface Occupation Rate Monitoring PS Services Features
GBS S9.0 M M M
Mapping Relationship with FPD A Interface Circuit Management A Interface Protocol Process A Interface Occupation Rate Monitoring
GBFD-1 19101 GBFD-1 19102 GBFD-1 19103 GBFD-1 19104 GBFD-1 19105 GBFD-1 19106 GBFD-1 19107 GBFD-1 19108 GBFD-1 19109 GBFD-1 19110 GBFD-1 19111 GBFD-1 19112 GBFD-1 19113 GBFD-1 19115 GBFD-1 19116
Packet Channel Combination Type Packet System Information MS Types MAC Mode RLC Mode Coding Scheme Networking Control Mode Network Operation Mode Support QoS(Best Effort) Access Assignment Paging Timing Advance Update Power Control Packet Uplink Flow Control
M M M M M M M M M M M M M M M
GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview
Issue 08 (2011-09-30)
103
Feature ID GBFD-1 19117
Description Flow Control on Gb Interface Antenna System Solution
GBS S9.0 M
Mapping Relationship with FPD GPRS/EGPRS Overview
MRFD-2 10601 MRFD-2 10602 MRFD-2 10604
Connection with TMA (Tower Mounted Amplifier) Remote Electrical Tilt 2-Antenna Receive Diversity Synchronization Mechanism
M M M
Connection with TMA (Tower Mounted Amplifier) Remote Electrical Tilt TX Diversity and RX Diversity
MRFD-2 10501 MRFD-2 10502
BTS/NodeB Clock BSC/RNC Clock Documentation
M M
BTS/NodeB Clock BSC/RNC Clock
MRFD-2 10701
Documentation
NA
2.2 Tutorial Introduction to Optional Features Of GBSS9.0

Purpose: Guide the user to find the GBSS features in the GBSS Feature Documentation quickly. M N E NA Maintenance (No change) New feature in the corresponding release Enhanced feature in the corresponding release Not correlate with the network elements or the features
Feature ID
Description Coverage enhancement
GBS S9.0
GBFD-1 15901
PBT(Power Boost Technology)
PBT
Issue 08 (2011-09-30)
104
Feature ID GBFD-1 15902 GBFD-1 15903 GBFD-1 18101 GBFD-1 18102
Description Transmit Diversity 4-Way Receiver Diversity Dynamic Transmit Diversity Dynamic PBT(Power Boost Technology) Voice Capacity Improvement
GBS S9.0 M M M M
Mapping Relationship with FPD Transmit Diversity Four-Way Receive Diversity Transmit Diversity PBT
Multi-band Sharing One BSC Enhanced Dual-Band Network Flex MAIO ICC EICC Frequency Efficiency Improvement
M M M M M
Multiband Network Multiband Network Flex MAIO Four-Way Receive Diversity 2-Antenna Receive Diversity
Frequency Hopping (RF hopping, baseband hopping) BCCH Carrier Frequency Hopping Antenna Frequency Hopping BCCH Dense Frequency Multiplexing Support for E-GSM and R-GSM Frequency Band Network Synchronization
E M M M M
Frequency Hopping Frequency Hopping Antenna Frequency Hopping BCCH Dense Frequency Multiplexing Multiband Network
GBFD-1 18201 GBFD-5 10401
Soft-Synchronized Network BTS GPS Synchronization
M M
Soft Synchronized Network BTS GPS Synchronization
Issue 08 (2011-09-30)
105
Feature ID GBFD-1 18606 GBFD-1 18620
Description Clock over IP Clock over IP support 1588V2 Energy Saving
GBS S9.0 E N
Mapping Relationship with FPD IP Transport Architecture Description IP Transport Architecture Description
GBFD-1 17601 GBFD-1 14801 GBFD-1 14803 GBFD-1 11602 GBFD-1 11603 GBFD-1 11604 GBFD-1 11605 GBFD-1 11606 GBFD-1 11608 GBFD-1 11609 GBFD-1 11610 GBFD-1 11611 GBFD-1 11612
HUAWEI III Power Control Algorithm ) Discontinuous Transmission (DTX)-Downlink Discontinuous Transmission (DTX)-Uplink TRX Power Amplifier Intelligent Shutdown TRX Power Amplifier Intelligent Shutdown on Timeslot Level Intelligent Combiner Bypass Active Backup Power Control Power Optimization Based on Channel Type PSU Smart Control Enhanced BCCH Power Consumption Optimization Dynamic Cell Power Off TRX Working Voltage Adjustment Multi-Carrier Intelligent Voltage Regulation Abis Transmission Saving
M M M M M M M M M M N M M
Power Control Discontinuous Transmission and Discontinuous Reception Discontinuous Transmission and Discontinuous Reception Intelligent Power Consumption Decrease Intelligent Power Consumption Decrease Intelligent Power Consumption Decrease Intelligent Power Consumption Decrease Intelligent Power Consumption Decrease Intelligent Power Consumption Decrease Intelligent Power Consumption Decrease Intelligent Power Consumption Decrease Intelligent Power Consumption Decrease Intelligent Power Consumption Decrease
GBFD-1 16701 GBFD-1 17301
16Kbit RSL and OML on A-bis Interface Flex Abis
M M
Networking Modes Flex Abis
Issue 08 (2011-09-30)
106
Description BTS Local Switch Abis Congestion Trigger HR Distribution A Transmission Saving
GBS S9.0 M M
Mapping Relationship with FPD BSS Local Switching Channel Management
GBFD-1 16901 GBFD-1 17701 GBFD-1 16902
Flex Ater BSC Local Switch Ater Compression Transmission Hardware Saving
M M N
Flex Ater BSS Local Switching Ater Compression Transmission
GBFD-1 15702
TrFO Networking Framework
TrFO
GBFD-1 14601
Multi-Cell Function System Reliability
Multi-Cell Function
GBFD-1 17801 GBFD-1 13801 GBFD-1 17401 GBFD-1 19701 GBFD-1 16601 GBFD-1 17802 GBFD-1 13721 GBFD-1 17803 GBFD-1 13725
Ring Topology TRX Cooperation MSC Pool SGSN Pool Abis Bypass Fast Ring Network Switch Robust Air Interface Signalling Abis Transmission Backup BSC Node Redundancy
M M E M M M M M N
BTS Ring Topology TRX Cooperation MSC Pool SGSN Pool Abis Bypass BTS Ring Topology Robust Air Interface Signaling BTS Ring Topology BSC Node Redundancy
Issue 08 (2011-09-30)
107
Description TC Pool OML Backup High Speed Coverage
GBS S9.0 N N
Mapping Relationship with FPD TC Pool OML Backup
GBFD-5 10101 GBFD-5 10102 GBFD-5 10103 GBFD-5 10104
AFC(Automatic Frequency Correction) Fast Move Handover Chain Cell Handover Multi-site Cell 2G/3G Seamless Coverage
M M M M
AFC Handover Handover Multi-site Cell
GSM/WCDMA Interoperability GSM/TD-SCDMA Interoperability GSM/WCDMA Service Based Handover GSM/WCDMA Load Based Handover 2G/3G Cell Reselection Based on MS State Fast 3G Reselection at 2G CS Call Release BTS Satellite Transmission
M M M M M N
2G/3G Interoperability 2G/3G Interoperability (TDD) 2G/3G Interoperability 2G/3G Interoperability 2G/3G Interoperability 2G/3G Interoperability
GBFD-1 13901
Satellite Transmission over Abis Interface BSC Satellite Transmission
Satellite Transmission
GBFD-1 13902 GBFD-1 13903 GBFD-1 13904
Satellite Transmission over A Interface Satellite Transmission over Ater Interface Satellite Transmission over Pb Interface
M M M
Satellite Transmission Satellite Transmission Satellite Transmission
Issue 08 (2011-09-30)
108
Feature ID GBFD-1 13905
Description Satellite Transmission over Gb Interface Big Capacity BSC
GBS S9.0 M
Mapping Relationship with FPD Satellite Transmission
GBFD-1 15201 GBFD-1 15301
High Speed Signaling Local Multiple Signaling Points Maintainability
M M
High-Speed Signaling Local Multiple Signaling Points
GBFD-1 14701 GBFD-1 16401 GBFD-1 16402
Semi-Permanent Connection End-to-End MS Signaling Tracing Maintenance Mode Alarm Power Control Algorithm
M M M
Semipermanent Connection End-to-End MS Signaling Tracing Maintenance Mode Alarm
GBFD-1 17602
Active Power Control Network Security
Power Control
A5/1 and A5/2 Ciphering Algorithm A5/3 Ciphering Algorithm A5/1 Encryption Flow Optimization Encrypted Network Management NAT Beside OM Enhanced Voice Service
M M M M M
Ciphering Ciphering Ciphering Encrypted Network Management NAT Beside OM
GBFD-1 13301 GBFD-1 13401 GBFD-1 13402
Enhanced Full Rate Half Rate Speech Dynamic Adjustment Between FR and HR Cell Broadcast Service
M M M
EFR Half-Rate Service Dynamic Channel Conversion
Issue 08 (2011-09-30)
109
Description Short Message Service Cell Broadcast (TS23) Simplified Cell Broadcast CS General Enhancement
GBS S9.0 M M
Mapping Relationship with FPD Cell Broadcast Cell Broadcast
GBFD-1 15601 GBFD-1 15602 GBFD-1 15603 GBFD-1 15701 GBFD-1 15703 GBFD-1 15704 GBFD-1 16801 GBFD-1 17501 GBFD-1 17101 GBFD-1 15522
Automatic Level Control (ALC) Acoustic Echo Cancellation(AEC) Automatic Noise Restraint (ANR) TFO Automatic Noise Compensation (ANC) Enhancement Packet Loss Concealment(EPLC) Voice Quality Index (Uplink VQI) Enhanced Measurement Report (EMR) BTS power lift for handover Dynamic HR/FR Adaptation AMR Package
M M M E N N M M M M
Automatic Level Control Acoustic Echo Cancellation Automatic Noise Restraint TFO Automatic Noise Compensation Enhancement Packet Loss Concealment (EPLC) Voice Quality Index EMR Handover Handover
AMR FR AMR HR AMR Power Control AMR FR/HR Dynamic Adjustment AMR Wireless Link Timer
M M M M M
AMR AMR AMR Handover AMR
Issue 08 (2011-09-30)
110
Description AMR Coding Rate Threshold Adaptive Adjustment WB AMR PS QoS
GBS S9.0 E N
Mapping Relationship with FPD AMR WB AMR
Streaming QoS(GBR) QoS ARP&THP PS Active Package Management PoC QoS Conversational QoS Cell Reselection of PS Domain
M M M M N
GPRS/EGPRS QoS GPRS/EGPRS QoS AQM GPRS/EGPRS QoS GPRS/EGPRS QoS
GBFD-1 16201 GBFD-1 16301 GBFD-1 19801
Network-Controlled Cell Reselection (NC2) Intra BSC Network Assisted Cell Change (NACC) Packet SI Status GPRS/EGPRS Service
M M M
NC2 NACC NACC
GPRS Network Operation Mode I CS-3/CS-4 EGPRS PDCH Dynamic Adjustment Gb Over FR EGPRS Service Enhancement
M M M M M M
GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Overview GPRS/EGPRS Channel Management GPRS/EGPRS Overview
Issue 08 (2011-09-30)
111
Feature ID GBFD-1 19201 GBFD-1 19202 GBFD-1 19203 GBFD-1 19204 GBFD-1 19205 GBFD-1 19302 GBFD-1 19303 GBFD-1 19501 GBFD-1 19305 GBFD-1 19502 GBFD-1 19503
Description 11-Bit EGPRS Access Packet Assignment Taken Over by the BTS Extended Uplink TBF Dynamically Adjusting the Uplink MCS Coding Dynamically Adjusting the RRBP Frequency Packet Channel Dispatching Load Sharing Adaptive Adjustment of Uplink and Downlink Channels BSS Paging Coordination PS Handover Early TBF Establishment High Speed Data Service
GBS S9.0 M M M M M M M M M N N
Mapping Relationship with FPD GPRS/EGPRS Connection Control and Transfer GPRS/EGPRS Connection Control and Transfer GPRS/EGPRS Connection Control and Transfer GPRS/EGPRS Link Quality Control GPRS/EGPRS Connection Control and Transfer GPRS/EGPRS Channel Management GPRS/EGPRS Channel Management GPRS/EGPRS Channel Management GPRS/EGPRS Overview PS Handover GPRS/EGPRS Connection Control and Transfer
Extended Dynamic Allocation (EDA) MS High Multislot Classes DTM Class11 DTM HMC DTM 14.4kbit/s Circuit Switched Data VIP Service Support
M M M M M M
GPRS/EGPRS Overview GPRS/EGPRS Overview DTM DTM DTM 14.4kbit/s Circuit Switched Data
Issue 08 (2011-09-30)
112
Description Resource Reservation Enhanced Multi Level Precedence and Preemption(EMLPP) Guaranteed Emergency Call Flow Control Based on Cell Priority Terminal Package
GBS S9.0 M M M N
Mapping Relationship with FPD eMLPP eMLPP Guaranteed Emergency Call Flow Control
GBFD-1 18103
Network Support SAIC LCS
Power Control
GBFD-1 15401 GBFD-1 15402 GBFD-1 15403
NSS-Based LCS (Cell ID + TA) BSS-Based LCS (Cell ID + TA) Simple Mode LCS(Cell ID + TA) Abis IP
M M M
Location Service Location Service Location Service
GBFD-1 18601 GBFD-1 18611 GBFD-1 18604
Abis over IP Abis IP over E1/T1 Abis MUX A IP
E N M
IP BSS IP BSS IP Transport Architecture Description
GBFD-1 18602 GBFD-1 18622 GBFD-1 18610
A over IP A IP over E1/T1 UDP MUX for A Transmission Gb IP
E N N
IP BSS IP BSS IP Transport Architecture Description
GBFD-1 18603
Gb over IP IP Enhancement
IP BSS
Issue 08 (2011-09-30)
113
Description IP QOS IP Performance Monitor IP Fault Detection Based on BFD Ethernet OAM PICO Solution Package
GBS S9.0 M M N N
Mapping Relationship with FPD IP Transport Architecture Description IP Transport Architecture Description IP Transport Architecture Description IP Transport Architecture Description
GBFD-5 10601 GBFD-5 10602
PICO Automatic Configuration and Planning PICO Synchronization Easy GSM Solution Package
M M
PICO Automatic Configuration and Planning Please Refer to M2000 documents
GBFD-5 10701 GBFD-5 10702
Compact BTS Automatic Configuration and Planning
Easy GSM Easy GSM
Compact BTS Automatic Capacity M Planning Public Voice Group Call Service
GBFD-5 10301 GBFD-5 10303 GBFD-5 10305 GBFD-5 10306 GBFD-5 10307 GBFD-5 10308 GBFD-5 10309
Public Voice Group Call Service Late Broadcast Channel Assignment Single Channel Group Call Originating Talker Identification Group Call EMLPP Fast Group Call Setup Group Call Reliability Enhancing Public Voice Broadcast Service
M M M M M M M
VGCS/VBS VGCS/VBS VGCS/VBS VGCS/VBS VGCS/VBS VGCS/VBS VGCS/VBS
GBFD-5 10302
Public Voice Broadcast Service
VGCS/VBS
Issue 08 (2011-09-30)
114
Description Late Group Channel Assignment GSM-T Relay Handover
GBS S9.0 M N
Mapping Relationship with FPD VGCS/VBS VGCS/VBS
GBFD-5 10501 GBFD-5 10502
HUAWEI II Handover Handover Re-establishment RAN Sharing
M M
Handover Handover Re-establishment
GBFD-1 18701
RAN Sharing EDGE Evolution
RAN Sharing
MSRD Dual Carriers in Downlink Uplink EGPRS2-A Downlink EGPRS2-A Latency Reduction Perfomance Analysis Toolkit
N N N N N
Dual Carriers in Downlink Dual Carriers in Downlink EGPRS2 EGPRS2 Latency Reduction
GBFD-5 10901
2G/3G Neighboring Cell Automatic Optimization Emergency Communications
2G/3G Neighboring Cell Automatic Optimization
GBFD-5 11001
License Control for Urgency 2G/3G Common Radio Resource Management Based on Iur-g
License Control for Urgency
GBFD-5 11101
Load Based Handover Enhancement on Iur-g 2G/3G Common Transmission
2G/3G Interoperability
GBFD-5 11201
Issue 08 (2011-09-30)

115
Feature ID
Description Paging Capability Improvement
GBS S9.0
GBFD-5 11501
Multiple CCCHs
Radio Common Channel Management
2.3 2-Antenna Receive Diversity

2.3.1 Introduction
2.3.1.1 Scope
This document describes the working principle of 2-antenna receive diversity and the diversity combining algorithms.
2.3.1.2 Intended Audience

It is assumed that users of this document are familiar with GSM basics and have a working knowledge of GSM telecommunication. This document is intended for: l l Personnel working on Huawei GSM products or systems System operators who need a general understanding of this feature
2.3.1.3 Change History

The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the 2-Antenna receive diversity feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows: l l
Issue 08 (2011-09-30)
02(2009-09-30) 01(2009-06-30)
02(2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, the following changes are incorporated: Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
01(2009-06-30)
2.3.2 Overview
In a wireless communications system, the radio signal from the transmitter arrives at the receiver through two or more paths. This phenomenon is called multipath propagation. With multipath propagation, the amplitude, phase, and angle of the received signal change. This phenomenon is called multipath fading. As a result, the quality of the received signal deteriorates. Diversity is one of the techniques used to handle multipath fading in the communications system. It increases the signal-to-noise ratio by superimposing uncorrelated signals. The diversity technique in GSM involves time diversity, frequency diversity, and space diversity. In the case of space diversity, multiple antennas are used at the receiver to receive uncorrelated signals of the same source (superimposition of uncorrelated signals). In engineering implementation, generally two antennas (or two polarization ends of the same polarization antenna) are used to receive signals. The signals received from the two antennas can be combined in different ways to obtain desired signals, for example, Maximal Ratio Combining (MRC), Interference Cancellation Combining (ICC), and Enhanced Interference Rejection Combining (EICC).
2.3.3 Technical Description

2.3.3.1 Technical Principle
The 2-antenna receive diversity technique combines the signals received from the two diverse antennas at the receiving end to mitigate multipath interference. Figure 2-1 shows the working principle of 2-antenna receive diversity.
Issue 08 (2011-09-30)
117
Figure 2-1 Working principle of 2-antenna receive diversity
As shown in Figure 2-1: 1. The signal x(k) arrives at the diverse antennas through two RX channels. The two RX signals are identified as r1(k) and r2(k). After the superimposition of interference and noise, the two RX signals are identified as S1(k) and S2(k). Based on the maximum signal-to-noise ratio criterion, the adaptive combining coefficients W1 and W2 are calculated and the output signal is obtained through the formula: y(k) = W1 x S1(k) + W2 x S2(k).
2.
The combining algorithms consist of the MRC, ICC, and EICC. In Figure 2-1 the two RX channels correspond to the main and diversity RX channels of the TRX. You should set Receive Mode to MAINDIVERSITY(Main Diversity) to enable the 2-Antenna Receive Diversity feature.
2.3.3.2 Diversity Combining Algorithms

?.1. MRC
MRC performs weighted combining on the two signals received by the BTS based on their respective signal-to-noise ratios. This combining method is ideal for situations with little interference and limited noise. It is applicable to wide coverage and overseas coverage.
?.2. ICC
ICC is a multi-antenna combining technique developed from MRC. In tight frequency reuse scenarios the interfering signals received at diverse antennas may come from the same interfering source. Therefore, a certain correlation exists among these interfering signals. ICC uses this correlation when combining the signals of the two antennas to eliminate certain interference. The use of ICC can improve the speech quality and data throughput in situations with strong interference, for example, the network where tight frequency reuse is in place. ICC can suppress the interference within the GSM system and from other systems if correlation exists between the interfering signals received on diverse antennas.
?.3. EICC
EICC is developed from ICC. Generally, the interfering signals received from multiple antennas are both space correlated (among the antennas) and time correlated. The difference between ICC and EICC is that ICC considers only space correlation to eliminate interference whereas EICC considers both space correlation and time correlation to suppress and eliminate interference. EICC is mainly used in high traffic network where tight frequency reuse is in place and in situations where the noise of a single interfering source is limited. The EICC performs better than ICC. You should set EICC Allowed to YES(Yes) to select the EICC algorithm of 2-antenna receive diversity.
NOTE
When EICC Allowed is set to NO(No), the system selects the ICC algorithm by default.
2.3.4 Parameters
This chapter describes the parameters related to 2-Antenna receive diversity. For the meaning of each parameter, see Table 2-1. For the default value, value ranges, and MML commands of each parameter, see Table 2-2. Table 2-1 Parameter description (1) Parameter Description RF receive mode of the TRX. The BTS3012, BTS3012AE, BTS3012II, BTS3006C, and BTS3002E do not support Main Diversity. The DBS3900 GSM and BTS3900 GSM support Four Diversity Receiver and Main Diversity. Whether to enable the EICC algorithm. Enhanced Interference Rejection Combining combines the signals received by multiple antennas to obtain better signals. EICC is mainly used in high traffic network where tight frequency reuse is in place.
Receive Mode
EICC Allowed
Issue 08 (2011-09-30)
119
Table 2-2 Parameter description (2) Paramete r Default Value GUI Value Range INDEPEN DENT (Independ ent Receiver), DIVIDIN G (Dividing Receiver), FOURDI VERSITY (Four Diversity Receiver), MAINDI VERSITY (Main Diversity), NONE (None) Actual Value Range Unit MML Comman d Impact
Receive Mode
NONE
INDEPEN DENT, DIVIDIN G, FOURDI VERSITY , MAINDI VERSITY , NONE
None
SET GTRXDE V (Optional) SET GCELLS OFT (Optional)
TRX
EICC Allowed
NO
NO(No), YES(Yes)
NO, YES
None
Cell
2.3.5 Counters
None.
2.3.6 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
2.3.7 Reference Documents
l l l
Issue 08 (2011-09-30)
3GPP TS 25.101, "User Equipment (UE) radio transmission and reception (FDD)" 3GPP TS 25.211, "Physical channels and mapping of transport channels onto physical channels (FDD)" 3GPP TS 25.306, " UE Radio Access capabilities "
l l l l l l
3GPP TS 25.308, "UTRA High Speed Downlink Packet Access (HSPDA); Overall description" 3GPP TS 25.321, "Medium Access Control (MAC) protocol specification" BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.4 2G/3G Interoperability

2.4.1 Introduction
2.4.1.1 Scope
This document describes the 2G/3G Interoperability feature of Huawei GBSS. It covers the functions of and technologies related to this feature, including measurement of neighboring UMTS cells, inter-radio access technology (inter-RAT) cell reselection, and inter-RAT handover.


The change history provides information on the changes on the 2G/3G Interoperability feature in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the 2G/3G Interoperability feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows:
l l l
03 (2010-02-10) 02 (2009-09-30) 01 (2009-06-30)
03 (2010-08-06)
This is the third commercial release of GBSS9.0. Compared with issue 02 (2009-09-30) of GBSS9.0, issue 03(2010-08-06) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description The following sections are added: Sections 2.4.3.2 Common Measurement and Information Exchange Based on Iur-g, 2.4.3.4.3 2G/ 3G Service Distribution and Load Balancing in Access State, and 2.4.3.4.4 InterRAT Load-based Handover in Connected State Parameter Change The following parameters are added: l 2G Cell UL Basic Congest Thred l 2G Cell UL Overload Congest Thred l 2G Cell DL Basic Congest Thred l 2G Cell DL Overload Congest Thred l Inter-RAT CS Service HO Load Threshold l Load Reselection Receive Threshold l Allow Inter-RAT Load HO in Access State l 2G Load Adjustment Coefficient l CS 2G 3G Load Balance Delta Threshold l Allow Inter-RAT Load HO in Connect State l System Flux Threshold for Load HO l Load HO Threshold l Inter-RAT Load HO RSCP at Start Point l Load HO Bandwidth l Inter-RAT Load HO RSCP Threshold l Inter-RAT Load HO EcNo at Start Point l Inter-RAT Load HO EcNo Threshold Editorial change None. None.
Issue 08 (2011-09-30)
122
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The document organization is optimized. Parameter Change None. None.
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description Section 2.4.3.3.3 Fast 3G Reselection at 2G CS Call Release is added. None. Parameter Change The following parameter is added: l Select 3G Cell After Call Release None.
2.4.2 Overview
The UMTS network and the GSM network will coexist and provide services together for a long time. Therefore, the 2G/3G Interoperability feature is introduced into the BSS. This feature involves inter-RAT reselection and inter-RAT cell handover between GSM and UMTS. 2G/3G interoperability provides a smooth evolution from GSM to UMTS, reducing the CAPEX of operators. For the operator that has both the UMTS network and the GSM network, 2G/3G interoperability enables the GSM network and the UMTS network work to supplement each other, expanding the network coverage and improving the service quality. For example, when a dual-mode MS moves to an UMTS coverage area, it can reselect or be handed over to a GSM cell through 2G/3G interoperability. This improves user experience. For the areas covered by both the GSM network and the UMTS network, 2G/3G interoperability achieves load balance between the GSM network and the UMTS network. For example, when a GSM cell is overloaded, 2G/3G interoperability transfers some calls in the GSM cell to a UMTS cell. This maximizes the network capability. In the areas covered by both the GSM network and the UMTS network, 2G/3G interoperability differentiates the access policy for the GSM network from that for the UMTS network. For
example, the GSM network can be preferentially selected by CS services and the UMTS network can be preferentially selected by PS services. In this way, the GSM network and the UMTS network complement each other.
NOTE
All the MSs involved in this feature are dual-mode MSs.

2.4.3.1 Measurement of Neighboring UMTS Cells
The system information (SI) contains UMTS cell reselection parameters and the list of neighboring UMTS cells, based on which the MS measures the neighboring cell information and performs cell reselection and handover. The SI includes SI 2ter, System Information 2Quater, and Measurement Information. System Information 2ter and System Information 2Quater are sent on the broadcast control channel (BCCH), and Measurement Information is sent on the slow associated control channel (SACCH). Whether System Information 2Quater is sent is controlled by theSupport Sent 2QUATER parameter. The MSs in a GSM cell measures the quality of signals in its neighboring UMTS cells while measuring the level of signals in its neighboring GSM cells. To reduce unnecessary measurements and power consumption of MSs, the BSS uses parameters to control the measurement of neighboring cells. The MSs may perform inter-RAT cell reselection in either idle mode or packet transfer mode, and perform inter-RAT handover in dedicated mode. In addition, operators can set measurement parameters to different values for the MSs in different modes. In idle mode, the MSs determine whether to measure neighboring UMTS cells based on Qsearch I and the receive level of the serving cell. The conditions for triggering the measurement vary with the value of Qsearch I. l l l l If the value of Qsearch I ranges from 0 to 6, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is lower than the value of Qsearch I. If the value of Qsearch I ranges from 8 to 14, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is higher than the value of Qsearch I. If the value of Qsearch I is 7, the MSs always measure the neighboring UMTS cells regardless of the receive level of the serving cell. If the value of Qsearch I is 15, the MSs never measure the neighboring UMTS cells regardless of the receive level of the serving cell.
In packet transfer mode, the MSs in determine whether to measure neighboring UMTS cells based on Qsearch P and the receive level of the serving cell. The conditions for triggering the measurement vary with the value of Qsearch P. l l l If the value of Qsearch P ranges from 0 to 6, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is lower than the value of Qsearch P. If the value of Qsearch P ranges from 8 to 14, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is higher than the value of Qsearch P. If the value of Qsearch P is 7, the MSs always measure the neighboring UMTS cells regardless of the receive level of the serving cell.
Issue 08 (2011-09-30)
If the value of Qsearch P is 15, the MSs never measure the neighboring UMTS cells regardless of the receive level of the serving cell.
In packet transfer mode, the MSs determine whether to measure neighboring UMTS cells based on Qsearch C and the receive level of the serving cell. The conditions for triggering the measurement vary with the value of Qsearch C. l l l l If the value of Qsearch C ranges from 0 to 6, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is lower than the value of Qsearch C. If the value of Qsearch C ranges from 8 to 14, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is higher than the value of Qsearch C. If the value of Qsearch C is 7, the MSs always measure the neighboring UMTS cells regardless of the receive level of the serving cell. If the value of Qsearch C is 15, the MSs never measure the neighboring UMTS cells regardless of the receive level of the serving cell.
Qsearch C is contained in the Measurement Information. After entering the dedicated mode, MSs attempt to obtain Qsearch C from the Measurement Information transmitted on the SACCH. Before obtaining Qsearch C, MSs assigns Qsearch C a value according to the value of Qsearch C Initial transmitted on the BCCH.
2.4.3.2 Common Measurement and Information Exchange Based on Iur-g

?.1. Introduction to the Iur-g Interface
The load information exchanged between GSM and UMTS networks is contained in the information elements (IEs) involved in the handover procedure over the A and Iu interfaces. In this case, unnecessary handover attempts inevitably are performed. With the development of 3GPP specifications, the Iur-g interface between the RNC and the BSC is used to achieve common measurement and information exchange between GSM and UMTS networks. This simplifies the 2G/3G interoperability procedure, shortens the delay caused by handovers, and improves the handover success rate. Figure 2-2 shows the position of the Iur-g interface in the network architecture. Figure 2-2 Position of the Iur-g interface in the network architecture
Issue 08 (2011-09-30)
125
Figure 2-3 shows the protocol stack defined in 3GPP specifications for the Iur-g interface. Figure 2-3 Protocol stack defined for the Iur-g interface
The Iur-g interface has the control plane but not the user plane. The Iur-g interface uses IP transmission, An Iur-g interface is required between the local BSC and a peer RNC for supporting common measurement and information exchange. The Iur-g interface uses the connectionoriented signaling.
?.2. Common Measurement

The common measurement is based on the Iur-g interface and requires connection-oriented signaling. To initialize the common measurement procedure, the source BSC/RNC sends a COMMON MEASUREMENT INITIATION REQUEST message to the target RNC/BSC to request the load information about neighboring cells. The source BSC/RNC then instructs the target RNC/ BSC to periodically report the load information. If the target RNC/BSC supports the common measurement procedure, it responds with a COMMON MEASUREMENT INITIATION RESPOSE message. Figure 2-4 shows the successful common measurement initialization procedure.
Issue 08 (2011-09-30)
126
Figure 2-4 Successful common measurement initialization
If the target RNC/BSC does not support the common measurement procedure, it responds with a COMMON MEASUREMENT INITIATION FAILURE message. Figure 2-5 shows the failed common measurement initialization procedure. Figure 2-5 Failed common measurement initialization
After a common measurement is successfully initialized, the target RNC/BSC periodically sends COMMON MEASUREMENT REPORT messages to the source BSC/RNC to report the load information about neighboring cells. Figure 2-6 shows the common measurement reporting procedure. Figure 2-6 Common measurement reporting procedure
If a neighboring cell is faulty, blocked, removed, or deactivated, the target RNC/BSC sends a COMMON MEASUREMENT FAILURE INDICATION message to the source BSC/RNC, notifying the source BSC/RNC the common measurement procedure fails and is to be terminated. Figure 2-7 shows the failed common measurement.
Issue 08 (2011-09-30)
127
Figure 2-7 Failed common measurement
?.3. Information Exchange

The information exchange procedure is based on the Iur-g interface. During a common measurement procedure, the following information is transmitted over the Iur-g interface between GSM and UMTS networks: load information about 2G and 3G cells, inter-RAT CS service handover support flag for a 2G cell, and inter-RAT PS service handover support flag for a 2G cell. This section uses load information about 2G cells as an example to describe information exchange. l Load status A cell may be in the normal state, the basic congestion state, or the overload congestion state. Table 2-3 describes the rules for determining the load states of 2G cells. Table 2-3 Rules for determining the load states of 2G cells Transmiss ion Direction Uplink If Then the Load Status Is Normal Basic congestion Overload congestion Normal Basic congestion Overload congestion
Uplink load < 2G Cell UL Basic Congest Thred 2G Cell UL Basic Congest Thred Uplink load < 2G Cell UL Overload Congest Thred Uplink load 2G Cell UL Overload Congest Thred
Downlink
Downlink load < 2G Cell DL Basic Congest Thred 2G Cell DL Basic Congest Thred Downlink load < 2G Cell DL Overload Congest Thred Downlink load 2G Cell DL Overload Congest Thred
Inter-RAT CS service handover support flag for a 2G cell When the TCH usage of a 2G cell is greater than or equal to the value of the Inter-RAT CS Service HO Load Threshold parameter or the Inter-RAT In BSC Handover Enable parameter is set to NO(No), the inter-RAT CS service handover support flag is No for the 2G cell. That is, CS services in a 3G cell cannot be handed over to the 2G cell.
Issue 08 (2011-09-30)
128
When the TCH usage of a 2G cell is smaller than the value of the Inter-RAT CS Service HO Load Threshold parameter and the Inter-RAT In BSC Handover Enable parameter is set to YES(Yes), the inter-RAT CS service handover support flag is Yes for the 2G cell. That is, CS services in a 3G cell can be handed over to the 2G cell. l Inter-RAT PS service handover support flag of a 2G cell When the TBF multiplexing rate of a 2G cell is lower than the value of the Load Reselection Receive Threshold parameter, the inter-RAT PS service handover support flag is Yes for the 2G cell. That is, PS services in a 3G cell can be handed over to the 2G cell. When the TBF multiplexing rate of a 2G cell is greater than or equal to the value of the Load Reselection Receive Threshold parameter, PS services in a 3G cell cannot be handed over to the 2G cell.
2.4.3.3 2G/3G Inter-RAT Cell Reselection

2G/3G inter-RAT cell reselection refers to the cell reselection between the GSM network and the UMTS network. Cell reselection is performed mainly by the MS. For MSs in idle mode, 2G/3G interoperability is mainly performed to implement cell reselection. An MS camping on a GSM cell can reselect a UMTS cell. It measures neighboring UMTS cells, and then determines whether to reselect the UMTS cell according to cell reselection parameters. The cell reselection procedure in packet transfer mode is the same as that in idle mode. MSs in packet transfer mode can reselect a UMTS cell for data services through autonomous cell reselection, Network Assisted Cell Change (NACC), or Network Control Mode 2 (NC2). The autonomous cell reselection is performed by the MS without the network intervention. In NACC and NC2, the network instructs the MS to camp on a desired cell through signaling. The Inter-RAT Cell Reselection Enable parameter determines whether cell reselection between GSM and UMTS is enabled. When Inter-RAT Cell Reselection Enable is set to No, the BSS does not send the list of neighboring UMTS cell or inter-RAT cell reselection parameters. Therefore, MSs in a GSM cell cannot reselect a UMTS cell.
?.1. Inter-RAT Cell Reselection from UMTS to GSM

When an MS moves into a GSM coverage area and reselects a GSM cell, the MS initiates a location update in the GSM network. The GSM network processes the location update regardless of whether the MS is from a UMTS cell or from a GSM cell. The BSS processes, the UMTS-to-GSM cell reselection in the same way as the cell reselection with the GSM network.Therefore, this document does not describe the related information.
?.2. Inter-RAT Cell Reselection from GSM to UMTS

An MS in a GSM cell obtains the list of neighboring UMTS cells and cell reselection parameters through System Information 2ter and System Information 2Quater, Based on the list and parameters, the MS measures the neighboring UMTS cells. When the MS is in idle mode or packet transfer mode, the mechanism of cell reselection from the GSM cell to the UMTS cell is the same as that between GSM cells. In the GSM network, inter-RAT cell reselection from a GSM to a UMTS is controlled by FDD Q Offset and FDD Qmin. The MS obtains the lowest receive quality for reselecting a candidate UMTS cell through FDD Qmin. FDD Qmin does not determine the cell reselection from GSM to UMTS directly but guarantees the quality of signals in the candidate UMTS cell. FDD Qmin is the minimum
threshold for Ec/No for UTRAN FDD cell re-selection. If FDD Qmin is set to a higher value, the cell reselection is less likely to occur. If FDD Qmin is set to a lower value, the cell reselection is more likely to occur. FDD Q Offset refers to the signal strength difference between the candidate UMTS cell and the serving GSM cell. This parameter is a key factor for controlling the cell reselection from GSM to UMTS. When FDD Q Offset is set to a small value, the cell reselection condition is easy to meet. In this case, MSs are more likely to reselect the UMTS cell and the number of MSs that camp on the GSM cell reduces. When FDD Q Offset is set to a large value, the cell reselection condition is difficult to meet. In this case, MSs are less likely to reselect the UMTS cell and keep camping on the GSM cells. FDD RSCP Min. is the minimum level threshold of UTRAN cell reselection. During the cell reselection decision from a GSM cell to an FDD cell. this parameter is used to calculate the FDD RSCP threshold of the target cell. If FDD_RSCPmin is broadcast on the serving cell, FDD_RSCP_threshold = FDD_RSCPmin min((P_MAX 21 dBm), 3 dB). If FDD_RSCPmin is not broadcast on the serving cell, Qrxlevmin and Pcompensation are available, FDD_RSCP_threshold = Qrxlevmin + Pcompensation + 10 dB. If FDD_RSCPmin is not broadcast on the serving cell, Qrxlevmin and Pcompensation are not available, the default value of FDD RSCP Min. is used. l l l l P_MAX is the maximum RF output power of the MS (dBm) in UTRAN FDD mode. Qrxlevmin is the minimum required RX level in the UTRAN FDD cell (dBm). Pcompensation is max(UE_TXPWR_MAX_RACH P_MAX, 0) (dB). UE_TXPWR_MAX_RACH is the maximum TX power level an MS may use when accessing the UTRAN FDD cell on RACH (dBm).
For UMTS FDD cells, the measurement results Ec/No and Received Signal Code Power (RSCP) of the Common Pilot Channel (CPICH) are commonly used. The MS initiates the cell reselection from GSM to UMTS if the measurement results meet the following conditions within 5 seconds: CPICH RSCP > RLA_C + FDD Q offset CPICH Ec/No FDD Qmin FDD Qmin_Offset
NOTE
Ec/No refers to the ratio of energy per modulating bit to the noise spectral density, in the UMTS network. It is equivalent to C/I in the GSM network.
CPICH RSCP FDD_RSCP_threshold RLA_C refers to the average receive level. The RSCP of the neighboring UMTS cell must be FDD Q Offset higher than the average receive level of the serving cell and the receive level of every neighboring GSM cell. The cell reselection from GSM to UMTS cannot be triggered 5 seconds within the cell reselection from the UMTS to the GSM. If the cell reselection from GSM to UMTS is triggered 15 seconds within the cell reselection from UMTS to GSM, the value of FDD Q Offset must be increased by 5 dB. If both the requirements for cell reselection from GSM to UMTS and reselection between GSM cells are met, the MS selects the UMTS cell as the target cell.
?.3. Fast 3G Reselection at 2G CS Call Release
Overview
In normal cases, after an MS terminates a call in a GSM cell, it camps on the GSM cell. if a neighboring UMTS cell meets the requirements for cell reselection, the MS camps on the UMTS cell after the cell reselection. Before initiating the UMTS cell reselection, the MS must receive SI and calculate cell reselection parameters. With the Fast 3G Reselection at 2G CS Call Release feature, after an MS terminates a call in a GSM cell, the BSS determines the best neighboring UMTS cell based on the measurement of neighboring UMTS cells Then, The BSS contains the frequency information on the neighboring UMTS cell in a Channel Release message and sends the message to the MS, specifying the UMTS cell that the MS will camp on. In this way, the MS camps on a UMTS cell without calculating cell reselection parameters, thus accelerating cell reselection. In addition, the MS camps on the UMTS cell for a longer period, increasing the revenue of operators in the UMTS network. This feature is effective when Select 3G Cell After Call Release is set to YES.
NOTE
A UMTS cell is classified into the UTRAN FDD cell and the UTRAN TDD cell.
Procedure
Take the case of call termination by the MS as an example. Figure 2-8 shows the cell reselection procedure with an MS-terminated call as an example. Figure 2-8 Cell reselection procedure
1.
After receiving a Release Complete message from the MS, the MSC sends a Clear Command message to the BSC to instruct the BSC to release the occupied resources on the A and Um interfaces. The BSC sends a Channel Release message to the MS to instruct the MS to release the TCH or SDCCH on the Um interface. The Channel Release message may carry the information
2.
Issue 08 (2011-09-30)
element "Cell selection indicator after release of all TCH and SDCCH", which contains the information about the target neighboring UMTS cell. 3. After receiving the Channel Release message, the MS disconnects the uplink signaling link. Then, the MS sends a DISC frame to the BTS to instruct the BTS to release the TCH or SDCCH. After receiving the UA message, the MS switches to the idle mode and initiates cell reselection. If... The Channel Release message contains the information element "Cell selection indicator after release of all TCH and SDCCH", The Channel Release message does not contain the information element "Cell selection indicator after release of all TCH and SDCCH", Then... The MS attempts to camp on the cell indicated in the Channel Release message.
4.
The MS attempts to camp on the cell where the TCH or SDCCH has been released.
5.
If 4 fails, the MS performs a common cell reselection procedure. For details about a common cell reselection procedure, see section 2.4.3.3.2 Inter-RAT Cell Reselection from GSM to UMTS.
Before sending the Channel Release message, the BSC determines whether to carry the information element "Cell selection indicator after release of all TCH and SDCCH" in the message. 1. If Select 3G Cell After Call Release is set to YES, the procedure proceeds to 2. Otherwise, the procedure is complete, and the BSC sends the MS the Channel Release message. which does not carry the information element "Cell selection indicator after release of all TCH and SDCCH". The BSC determines whether an MS supports both GSM and UMTS according to the information contained in the classmark. If the classmark does not indicate the MS capability of supporting the GSM/UMTS, the procedure proceeds to 3. Otherwise, the procedure is complete, and the BSC sends the MS the Channel Release message, which does not carry the information element "Cell selection indicator after release of all TCH and SDCCH". The BSC figures out the best neighboring UMTS cell based on the related measurement report, and then the procedure proceeds to 4. If there is no measurement report or the measurement report does not contain the information about the neighboring UMTS cell, the procedure is complete, and the BSC sends the MS the Channel Release message, which does not carry the information element "Cell selection indicator after release of all TCH and SDCCH". If the measurement report indicates a neighboring UMTS FDD cell, Cell Selection Indicator is set to UTRAN FDD Description. If the measurement report indicates a neighboring UTRAN TDD cell, Cell Selection Indicator is set to UTRAN TDD Description, and the procedure is complete. Meanwhile, the BSC sends the MS the Channel Release message, which contains the information element "Cell selection indicator after release of all TCH and SDCCH".
2.
3.
4.
?.4. NACC and NC2

When MS is in packet transfer mode, Network Assisted Cell Change (NACC) and (Network Control Mode 2) NC2 can be performed for inter-RAT cell reselection. If the Iur-g interface exists between the BSC and RNC, the UMTS-to-GSM NACC procedure is an optimized NACC procedure. In this case, the MS obtains the SI of the target cell directly over the Iur-g interface. For details, see 2.59 NACC and 2.60 NC2.
2.4.3.4 2G/3G Inter-RAT Handover

2G/3G inter-RAT handover involves the handover from GSM to UMTS and the handover from UMTS to GSM. The handover is controlled mainly by the network. For MSs in dedicated mode, 2G/3G interoperability is mainly performed to implement interRAT handover, including emergency handover, better cell handover, inter-RAT load handover, and inter-RAT service handover. Emergency handover refers to the handover that is triggered when the call cannot be processed in the serving cell due to poor coverage or other reasons during the CS service of the dual-mode MS. For example, when an MS making a call in a GSM cell is moving outside the cell, the emergency handover is triggered to avoid call drops. Better cell handover refers to the handover that is triggered when the signal quality of a neighboring cell is better than that of the serving cell. Such handovers provide better service quality and user experience. For example, when the signal quality of a UMTS cell is better than that of the serving GSM cell, MSs in the serving cell can be handed over to the UMTS cell to achieve higher voice quality. Inter-RAT load handover refers to the handover wherein some of the calls in the GSM serving cell are handed over to a UMTS cell or some of the calls in the UMTS serving cell are handed over to a GSM cell due to high load on the serving cell. For an incoming inter-RAT handover to a GSM cell, if the load on the target GSM cell is also high, the target cell rejects the handover to avoid ping-pong handovers. Inter-RAT service handover refers to the handover wherein, the operator can choose the network that the MS will access through the MSC. For a call initiating an access request in a GSM cell, if the MSC indicates that the service handover should be performed, the BSS hands over the call to the UMTS cell. If the MSC indicates that call should not be handed over to a UMTS call, the BSS does not hand over the call to a UMTS cell when a handover is required during the call.
?.1. Inter-RAT Handover from UMTS to GSM

MSs in dedicated mode can be handed over from a UMTS cell to a GSM cell. The handover decision and handover procedure are controlled by the RNC. The BSS considers the incoming handover from UMTS to GSM as a common inter-BSC handover. The parameter Inter-RAT In BSC Handover Enable determines whether inter-RAT handover from UMTS to GSM is enabled. If Inter-RAT In BSC Handover Enable is set to No, the BSS rejects all the requests for the handover from UMTS to GSM.
?.2. Inter-RAT Handover from GSM to UMTS

The parameter Inter-RAT Out BSC Handover Enable determines whether inter-RAT handover from GSM to UMTS is enabled. If Inter-RAT Out BSC Handover Enable is set to NO(No), the BSS rejects all the requests for the handover from GSM to UMTS. In dedicated mode, an MS obtains the list of neighboring UMTS cells and other information from Measurement Information. Then, the MS reports the measurement result to the BSS through the measurement report. After receiving the measurement result, the BSS determines whether to initiate the inter-RAT handover from GSM to UMTS based on the measurement result and the handover algorithm. The inter-RAT handover from GSM to UMTS can be classified into emergency handover and better 3G cell handover. The algorithm for an emergency handover from GSM to UMTS is the same as that for a common emergency handover. For details, see 2.46 Handover. In the GSM network, the parameter Inter-rat HO Preference determines whether the GSM cell or the UMTS cell is preferentially selected as the target cell. l l l When Inter-rat HO Preference is set to Pre_2G_Cell(Preference for 2G cell), the BSC preferentially selects a GSM cell as the target cell. When Inter-rat HO Preference is set to Pre_3G_Cell(Preference for 3G cell), the BSC preferentially selects a UMTS cell as the target cell. When Inter-rat HO Preference is set to Pre_2G_CellThres(Preference 2G cell by thresh), the BSC determines the target cell according to the levels of the neighboring GSM cells and the value of HO Preference Threshold for 2G Cell. If no neighboring GSM cell has a level higher than HO Preference Threshold for 2G Cell, the BSC selects a UMTS cell as the target cell.
Better 3G cell handover can be performed when both Inter-RAT Out BSC Handover Enable and Better 3G Cell HO Allowed are set to YES(Yes). As the measurement result of the UMTS cell can be reported through RSCP or Ec/No, the ways for handover decision differ accordingly. l When the value of FDD REP QUANT is RSCP(RSCP), the better 3G cell handover is triggered if the following condition is met for FDD 3G Better Cell HO Valid Time within FDD 3G Better Cell HO Watch Time. CPICH RSCP > RSCP Threshold for Better 3G Cell HO l When the value of FDD REP QUANT is Ec/N0, the better 3G cell handover is triggered if the following condition is met for FDD 3G Better Cell HO Valid Time within FDD 3G Better Cell HO Watch Time. CPICH Ec/No > Ec/no Threshold for Better 3g Cell HO
?.3. 2G/3G Service Distribution and Load Balancing in Access State
Overview
In the case of co-existence of 2G and 3G networks, operators can provide more diversified services. The QoS-based service distribution feature is introduced to optimize the utilization of resources in 2G and 3G networks. For example, voice services and low-rate data services are distributed to the 2G network, whereas high-rate data services are distributed to the 3G network to achieve high peak throughput. In addition, in the case of co-existence of 2G and 3G networks, the loads in the two networks are different. The 2G/3G load balancing feature is introduced to balance the loads between the
two networks. This helps increase, the system capacity and reduces impact of high load on the system. In this way, the 2G/3G network resources are efficiently used. When an MS (a dual-mode MS) accesses the network from a 2G cell, based on the load in the target 3G cell, the BSC hands over the MS performing high-rate data service to the target 3G cell and retains the low-rate services in the 2G cell. If the MS accesses the network from a 2G cell and the 2G cell is congested, based on the load in the garget 3G cell, the BSC redirects the MS to the target 3G cell.
Related Algorithms
When an MS accesses the network from a 2G cell, the BSC selects an inter-RAT handover algorithm based on the setting of the Allow Inter-RAT Load HO in Access State parameter, if the Inter-RAT Out BSC Handover Enable parameter is set to YES(Yes). l When the Allow Inter-RAT Load HO in Access State parameter is set to CnServicebased(CN Service-based), the BSC performs different processing based on the setting of the Service Handover IE in the ASSIGNMENT REQUEST message received from the Core Network (CN). The details are as follows: If the value of the Service Handover IE is Handover to UTRAN or cdma2000 should be performed, it indicates that the MS should be handed over to a 3G cell. In this case, the BSC selects a target 3G cell from the list of neighboring cells and hands over the MS to the target 3G cell. If the value of the Service Handover IE is Handover to UTRAN or cdma2000 should not be performed, it indicates that a 2G cell should be preferentially selected as the serving cell. In this case, the BSC does not perform the handover from 2G to 3G. If a handover is required during the call, a 2G cell is preferentially selected as the target cell. If the value of the Service Handover IE is Handover to UTRAN or cdma2000 shall not be performed, it indicates that the MS must not be handed over to a 3G cell. In this case, the BSC will not hand over the MS to a 3G cell. Instead, the BSC will select a 2G cell as the target cell if a handover is required. l When the Allow Inter-RAT Load HO in Access State parameter is set to Service-based (Service-based), the BSC removes the candidate 3G cells that experience basic congestion in uplink or downlink and admits the MS to the 2G cell if the MS performs only CS services after accessing the network. When the Allow Inter-RAT Load HO in Access State parameter is set to Load-based (Load-based) and the value of the Service Handover IE is handover to UTRAN or cdma2000 should be performed, the BSC selects a candidate 3G cell that meets the following condition in both uplink and downlink as the target cell. 2G Load Adjustment Coefficient x Current load in the serving 2G cell 10 x load in the neighboring 3G cell 10 x CS 2G 3G Load Balance Delta Threshold 1,000 Then, the BSC selects the best neighboring 3G cell as the target cell and starts the directed retry to the 3G cell. If there is no 3G cell that meets the preceding condition in uplink and downlink, the BSC admits the MS to the 2G cell.
NOTE
If there are no candidate 3G cells or if the directed retry to the target 3G cell fails, the BSC initiates a reassignment procedure in a 2G cell.
When the Allow Inter-RAT Load HO in Access State parameter is set to Dynamic-based (Dynamic Service/Load-based), the BSC selects a proper target cell using the 2G system service distribution algorithm if the load in the serving cell is in the normal state. If the load
Issue 08 (2011-09-30)
in the serving cell is in other states, the BSC selects a target cell using the 2G system load balancing algorithm.
?.4. Inter-RAT Load-based Handover in Connected State
Overview
In the case of co-existence of 2G and 3G networks, there is a possibility that a network is congested due to insufficient resources, whereas the other network has only a light traffic. The inter-RAT load-based handover in connected state feature is introduced to solve this problem. This feature enables the efficient use of the resources in 2G and 3G networks and balances the load between 2G and 3G networks. In this manner, system capacity increases, and the impact of high load on the system is prevented.
Related Algorithms
When the Allow Inter-RAT Load HO in Connect State parameter is set to YES(Yes) and the MS or UE supports inter-RAT handover, an inter-RAT load-based handover in connected state is triggered when the following conditions are met: l l l The CPU usage of the system is smaller than or equal to the value of the System Flux Threshold for Load HO parameter. The current load in the serving cell is greater than or equal to the value of the Load HO Threshold parameter. The value of the Service Handover IE in the ASSIGNMENT REQUEST message received from the CN is not handover to UTRAN or cdma2000 shall not be performed. 2G Load Adjustment Coefficient x Load in the current 2G serving cell 10 x Load in the neighboring 3G cell CS 2G 3G Load Balance Delta Threshold 1000 In the case of an FDD cell, if the FDD REP QUANT parameter is set to RSCP(RSCP), the target 3G cell must meet the following conditions: Inter-RAT Load HO RSCP at Start Point Load HO Bandwidth < CPICH RSCP < Inter-RAT Load HO RSCP at Start Point CPICH RSCP > Inter-RAT Load HO RSCP Threshold l In the case of an FDD cell, if the FDD REP QUANT parameter is set to EcN0(Ec/N0), the target 3G cell must meet the following conditions: Inter-RAT Load HO EcNo at Start Point Load HO Bandwidth < CPICH Ec/No < Inter-RAT Load HO EcNo at Start Point CPICH Ec/No > Inter-RAT Load HO EcNo Threshold If a candidate neighboring 3G cell does not meet the preceding conditions the cell is removed from the list of candidate cells.
NOTE
The candidate neighboring 3G cells must meet the following conditions: l l
If the load information about a neighboring 3G cell is invalid, the neighboring 3G cell is not considered as a candidate cell.
If there is at least one candidate 3G cell that meets the preceding conditions the BSC selects the best candidate cell as the target cell.
2.4.4 Engineering Guidelines

Related Parameters in the System Information

2G/3G interoperability requires the support from MSs. After 2G/3G interoperability is enabled, the early classmark sending function should be enabled so that MSs will report their supporting capabilities as soon as possible. Therefore, it is recommended that Send 3G Class Flag, Classmark Enquiry With 3G Request and ECSC be set toYES(Yes). When setting the inter-RAT cell reselection parameters and handover thresholds, take into account the consistency between GSM parameters and UMTS parameters to avoid ping-pong handovers. The network can control the cell reselection between GSM and UMTS using related parameters in the system information. If the MS is preferred to access UMTS when available, you are advised to set Qsearch I to 7, so that the UMTS cell search is always performed. The value of FDD Q Offset has a great impact on cell reselection. If an MS is preferred to camp on the UMTS, you are advised to change the value of FDD Q Offset to ensure that the actual offset is a negative value.
NOTE
When the value of FDD Q Offset is smaller than 8, the corresponding actual offset is smaller than 0.
Neighboring UMTS Cell Configuration

To enable the 2G/3G interoperability, neighboring UMTS cells must be configured. The UMTS cell can be configured on the BSS side by adding external 3G cells. One GSM cell can be configured with a maximum of 64 neighboring UMTS cells. Those cells can work on three frequencies and a maximum of 32 cells can work in on same frequency. If the UMTS cell is a WCDMA cell, set Utran Cell Type to FDD(FDD).
2.4.5 Parameters
This chapter describes the parameters related to 2G/3G Interoperability. For the meaning of each parameter, see Table 2-4. For the default value, value ranges, and MML commands of each parameter, see Table 2-5. Table 2-4 Parameter description (1) Parameter 2G Cell UL Basic Congest Thred 2G Cell UL Overload Congest Thred 2G Cell DL Basic Congest Thred Description When the uplink load of a cell is larger than the value of this parameter and is smaller than "2G Cell UL Overload Congest Thred", the uplink of the cell is in the basic congestion status. When the uplink load of a cell is greater than the value, the uplink of the cell is in the overload congestion status. When the downlink load of a cell is larger than the value of this parameter and is smaller than "2G Cell DL Overload Congest Thred", the downlink of the cell is in the basic congestion status.
Issue 08 (2011-09-30)
137
Parameter 2G Cell DL Overload Congest Thred Inter-RAT CS Service HO Load Threshold Load Reselection Receive Threshold
Description When the downlink load of a cell is greater than the value, the downlink of the cell is in the overload congestion status. Threshold for setting the flag of accepting inter-RAT CS service handover of a 2G cell When the uplink load or downlink load of the target cell is lower than this threshold, it can accept the MSs from the serving cell due to load reselection. When this parameter is set to Service-based, the inter-RAT handover is triggered on the basis of the service distribution. In this case, the target cell is selected according to the traffic load. When this parameter is set to Load-based, the inter-RAT handover is triggered on the basis of the load balance. In this case, the target cell is selected according to the traffic load on the target cell and the load difference between 2G and 3G cells. When this parameter is set to Dynamic Service/Load based, the target cell is dynamically selected by using the service-based algorithm or the load-based algorithm according to the traffic load on the cell. When this parameter is set to CN Service-based, the inter-RAT handover decision is made on the basis of the service attribute of the core network. When this parameter is set to OFF, no inter-RAT service handover or inter-RAT load handover in the access state is performed. Coefficient used to modulate the load level of a 2G system so that the load level of the 2G system can be compared with that of a 3G system. If the load balance between a 2G cell and a 3G cell is greater than the threshold, load balance is triggered.
Allow Inter-RAT Load HO in Access State 2G Load Adjustment Coefficient CS 2G 3G Load Balance Delta Threshold
Issue 08 (2011-09-30)
138
Parameter
Description System flux thresholds correspond to the system flux obtained based on message packets, CPU load, and FID queuing load. The system flux level is the current flux control level of the system. 0-11: There are 12 flow control levels. Where, 0 indicates the lowest level and 11 indicates the highest level. A load handover is allowed only when the system flux is lower than the value of this parameter. The handover performed over the maximum threshold may have tremendous impacts on the system. Thus, this parameter should not be set to a higher value. 1) The flow control level algorithm for the assigned system messages: [(Average Message Usage - Inner Flow Control Discard Begin Threshold)/(Inner Flow Control Discard All Threshold - Inner Flow Control Discard Begin Threshold) x 100]/10+1 (round-down for division operation). If the value is smaller than Inner Flow Control Discard Begin Threshold, Level 0 is used. If the value is equal to or greater than Inner Flow Control Discard Begin Threshold, the level is calculated. The value range is from 0 to 11. 2) Flow control threshold for the CPU to start to discard the channel access messages and paging messages: 80% . Flow control threshold for the CPU to discard all channel access messages and paging messages: 100% . CPU usage smaller than 80% corresponds to level 0. CPU usage equal to or greater than CPU flow control threshold 80% corresponds to level 2. An increase of 5% means an increase of 2 levels. Level 10 is the highest. The level value can be 0, 2, 4, 6, 8, and 10. The load handover is triggered when the traffic load in a cell is greater than the value of this parameter.
System Flux Threshold for Load HO Load HO Threshold Inter-RAT Load HO RSCP at Start Point
Initial RSCP value of the inter-RAT load-based handover band In the handover algorithm of the first generation, load handovers can be performed only when the receive level of the current serving cell is in the range "Edge HO DL RX_LEV Threshold" to "Edge HO DL RX_LEV Threshold" + "Load HO Bandwidth". In the handover algorithm of the second generation, load handovers can be performed only when the level difference between the neighboring cell and the serving cell is between "Inter-cell HO Hysteresis" - "Load HO Bandwidth" and "Inter-cell HO Hysteresis". Minimum RSCP value of a 3G cell during the load-based GSM-toUMTS handover
Load HO Bandwidth Inter-RAT Load HO RSCP Threshold Inter-RAT Load HO EcNo at Start Point Inter-RAT Load HO EcNo Threshold
Initial EcNo value of the inter-RAT load-based handover band Minimum Ec/No value of a 3G cell during the load-based GSM-toUMTS handover
Issue 08 (2011-09-30)
139
Parameter Select 3G Cell After Call Release Support Sent 2QUATER
Description This parameter specifies whether to allow a mobile phone to preferentially camp on a 3G cell after a call is terminated in the areas covered by both the GSM network and the UMTS network. This parameter specifies whether the SI Type 3 message contains the 2QUATER indicator. This parameter specifies the level threshold for cell reselection in idle mode. In idle mode, if the signal level of the serving cell is below [0, 7] or above [8, 15], the MS starts to search for 3G cells. For example, if this parameter is set to 5 and if the signal level of the serving cell is lower than 5, the MS starts to search for 3G cells; if this parameter is set to 10 and if the signal level of the serving cell is above 10, then the MS starts to search for 3G cells The values of this parameter correspond to the following decibel values: 0: -98 dBm 1: -94 dBm 2: -90 dBm 3: -86 dBm 4: -82 dBm 5: -78 dBm 6: -74 dBm 7: (always), that is, the MS keeps searching for 3G cells 8: -78 dBm 9: -74 dBm 10: -70 dBm 11: -66 dBm 12: -62 dBm 13: -58 dBm 14: -54 dBm 15: (never), that is, the MS does not search for 3G cells This parameter specifies one threshold of the signal level for cell reselection in packet transfer mode. In packet transfer mode, if the signal level of the serving cell is below [0, 7] or above [8, 15], the MS starts to search for 3G cells. For example, if this parameter is set to 5 and if the signal level of the serving cell is lower than 5, the MS starts to search for 3G cells; if this parameter is set to 10 and if the signal level of the serving cell is above 10, then the MS starts to search for 3G cells. The values of this parameter correspond to the following decibel values: 0: -98 dBm 1: -94 dBm 2: -90 dBm 3: -86 dBm 4: -82 dBm 5: -78 dBm 6: -74 dBm 7: (always), that is, the MS keeps searching for 3G cells 8: -78 dBm 9: -74 dBm 10: -70 dBm 11: -66 dBm 12: -62 dBm 13: -58 dBm 14: -54 dBm 15: (never), that is, the MS does not search for 3G cells In connection mode, if the signal level is below [0-7] or above [8-15], the MS starts to search for 3G cells. For example, if this parameter is set to 5 and if the signal level of the serving cell is lower than 5, the MS starts to search for 3G cells; if this parameter is set to 10 and if the signal level of the serving cell is above 10, then the MS starts to search for 3G cells. 0: -98 dBm 1: -94 dBm 2: -90 dBm 3: -86 dBm 4: -82 dBm 5: -78 dBm 6: -74 dBm 7: (always), that is, the MS keeps searching for 3G cells 8: -78 dBm 9: -74 dBm 10: -70 dBm 11: -66 dBm 12: -62 dBm 13: -58 dBm 14: -54 dBm 15: (never), that is, the MS does not search for 3G cells This parameter specifies the threshold of the signal level for cell reselection in connection mode before ""Qsearch C"" is obtained. This parameter specifies whether the reselection from 2G cells to 3G cells is allowed.
Qsearch I
Qsearch P
Qsearch C Qsearch C Initial Inter-RAT Cell Reselection Enable
Issue 08 (2011-09-30)
140
Parameter
Description This parameter specifies one of the thresholds of the signal level for 3G cell reselection. A FDD cell becomes a candidate cell if all the following conditions are met for five consecutive seconds: 1.Receive level of the FDD cell > Average receive level of the current serving cell + "FDD Q offset"; The FDD cell meets the following condition in the case of any neighboring 2G cell: Receive level of the FDD cell > Receive level of any neighboring 2G cell + "FDD Q offset"; 2. Ec/No of the FDD cell > "FDD Qmin" - "FDD Qmin Offset"; 3. Receive level of the FDD cell > "RSCP Threshold"; If multiple FDD cells meet the preceding conditions, the MS reselects the cell with the strongest receive level. See 3GPP TSs 45.008 and 25.304. The values of this parameter correspond to the following decibel values: 0: - (always select a cell if acceptable) 1: -28 dB, 2: -24 dB, ... 15: 28 dB. This parameter specifies one of the parameters for FDD cell reselection. A FDD cell becomes a candidate cell if all the following conditions are met for five consecutive seconds: 1.Receive level of the FDD cell > Average receive level of the current serving cell + "FDD Q offset"; The FDD cell meets the following condition in the case of any neighboring 2G cell: Receive level of the FDD cell > Receive level of any neighboring 2G cell + "FDD Q offset"; 2. Ec/No of the FDD cell > "FDD Qmin" - "FDD Qmin Offset"; 3. Receive level of the FDD cell > "RSCP Threshold"; If multiple FDD cells meet the preceding conditions, the MS reselects the cell with the strongest receive level. See 3GPP TSs 45.008 and 25.304. The values of this parameter correspond to the following decibel values: 0: -20 dB, 1: -6 dB, 2: -18 dB, 3: -8 dB, 4: -16 dB, 5: -10 dB, 6: -14 dB, 7: -12 dB. This parameter specifies whether the handover from 3G cells to 2G cells is allowed. This parameter specifies whether the handover from 2G cells to 3G cells is allowed. When this parameter is set to Pre_2G_CellThres, the BSC preferentially selects a neighboring 3G cell as the handover target cell if the receive level of the neighboring 2G cell that ranks the first in the candidate cell list is equal to or smaller than "HO Preference Threshold for 2G Cell". Otherwise, the BSC preferentially selects a neighboring 2G cell as the handover target cell. If the receive level of the neighboring 2G cell that ranks the first in the candidate cell list is equal to or smaller than this threshold, the BSC preferentially selects a neighboring 3G cell as the handover target cell. Otherwise, the BSC preferentially selects a neighboring 2G cell as the handover target cell. This parameter specifies whether to allow 3G better cell handover algorithm.
FDD Q Offset
FDD Qmin Inter-RAT In BSC Handover Enable Inter-RAT Out BSC Handover Enable
Inter-rat HO Preference
HO Preference Threshold for 2G Cell Better 3G Cell HO Allowed
Issue 08 (2011-09-30)
141
Parameter
Description This parameter specifies whether Ec/No or RSCP is used for the measurement report on a FDD cell. Ec/No stands for the signal-to-noise ratio. RSCP stands for the received signal code power. According to the P/N rule, if the conditions for the handover to a better 3G cell are met for P seconds within N seconds, the handover is triggered. This parameter specifies the number P. The 3G better cell handover is triggered only when the RSCP of a neighboring 3G cell is greater than this threshold for a period of time. According to the P/N rule, if the conditions for the handover to a better 3G cell are met in P of N measurement reports, the handover is triggered. This parameter specifies the number N. The 3G better cell handover can be triggered only when the Ec/No of a neighboring 3G cell is greater than this threshold for a period of time. This parameter specifies whether to allow the inter-RAT load handover in connection mode (after the assignment is complete). If the load of a cell is lower than the value of this parameter, the cell can admit the users handed over from other cells with higher load. Otherwise, the cell rejects such users. When this parameter is set to Open, the BSS decides whether to hand over the current service to the 3G network according to the contents of the "Service Handover" information element in the ASS REQ and HO REQ messages. The early classmark sending control (ECSC) parameter specifies whether the MSs in a cell use early classmark sending. After a successful immediate assignment, the MS sends additional classmark information to the network as early as possible. The additional classmark information mainly contains the CM3 (classmark 3) information. The CM3 (classmark 3) information contains the frequency band support capability of the MS (used for the future channel assignment), power information about each frequency band supported by the MS (used for the handover between different frequency bands), and encryption capability of the MS. This parameter specifies the type of a 3G cell. A cell type can be Frequency Division Duplex (FDD) or Time Division Duplex (TDD). Whether the SI Type 3 message contains the 3G Early Classmark Sending Restriction field. The 3G Early Classmark Sending Restriction field is used to notify the MS of whether the early classmark message contains the 3G classmark message. This parameter is valid for dualmode MSs and is invalid for single-mode MSs.
FDD REP QUANT FDD 3G Better Cell HO Valid Time RSCP Threshold for Better 3G Cell HO FDD 3G Better Cell HO Watch Time Ec/No Threshold for Better 3G Cell HO Allow Inter-RAT Load HO in Connect State Load handover Load Accept Threshold
Service Based Handover Switch
ECSC Utran Cell Type
Send 3G Class Flag
Issue 08 (2011-09-30)
142
Classmark Enquiry With 3G Request
Whether to enable the BSC to include the 3G classmark information element in the Classmark Request message that the BSC forwards from the MSC to an MS.
Table 2-5 Parameter description (2) Parameter Default Value GUI Value Range Actual Value Range Unit MML Comman d SET GCELLH OINTERR ATLDB (Optional) SET GCELLH OINTERR ATLDB (Optional) SET GCELLH OINTERR ATLDB (Optional) SET GCELLH OINTERR ATLDB (Optional) SET GCELLH OINTERR ATLDB (Optional) SET GCELLN C2PARA (Optional) Impact
2G Cell UL Basic Congest Thred 2G Cell UL Overload Congest Thred 2G Cell DL Basic Congest Thred 2G Cell DL Overload Congest Thred Inter-RAT CS Service HO Load Threshold Load Reselection Receive Threshold
90
1~100
1~100
None
BSC
100
1~100
1~100
None
BSC
90
1~100
1~100
None
BSC
100
1~100
1~100
None
BSC
80
1~100
1~100
None
BSC
60
0~100
0~100
per cent
Cell
Issue 08 (2011-09-30)
143
Parameter
Default Value
GUI Value Range Servicebased (Servicebased), Loadbased(Loadbased), Dynamicbased (Dynamic Service/ Load-based), CnServicebased(CN Servicebased), OFF (OFF)
Actual Value Range
Unit
MML Comman d
Impact
Allow InterRAT Load HO in Access State
OFF
{0~4}
None
SET GCELLH OINTERR ATLDB (Optional) SET GCELLH OINTERR ATLDB (Optional) SET OTHSOF TPARA (Optional) SET GCELLH OAD (Optional) SET GCELLH OAD (Optional) SET GCELLH OINTERR ATLDB (Optional) SET GCELLH OAD (Optional)
BSC
2G Load Adjustment Coefficient CS 2G 3G Load Balance Delta Threshold System Flux Threshold for Load HO
10
0~100
0~100
None
BSC
110
0~200
-100~100
per cent
BSC
10
0,8~11
0, 8~11
None
Cell
Load HO Threshold Inter-RAT Load HO RSCP at Start Point
90
0~100
0~100
None
Cell
91
0~91
0~91
dB
BSC
Load HO Bandwidth
25
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
144
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLH OINTERR ATLDB (Optional) SET GCELLH OINTERR ATLDB (Optional) SET GCELLH OINTERR ATLDB (Optional) SET GCELLC CAD (Optional) SET OTHSOF TPARA (Optional)
Impact
Inter-RAT Load HO RSCP Threshold Inter-RAT Load HO EcNo at Start Point Inter-RAT Load HO EcNo Threshold Select 3G Cell After Call Release
30
0~91
0~91
dB
BSC
49
0~49
0~49
dB
BSC
25
0~49
0~49
dB
BSC
NO
NO(No), YES(Yes)
NO, YES
None
Cell
Support Sent 2QUATER
YES
NO(No), YES(Yes)
NO, YES -98, -94, -90, -86, -82, -78, -74, (always), -78, -74, -70, -66, -62, -58, -54, Positive infinity (never)
None
BSC
Qsearch I
15
0~15
None
SET GCELLC CUTRAN SYS (Optional)
Cell
Issue 08 (2011-09-30)
145
Parameter
Default Value
GUI Value Range
Actual Value Range -98, -94, -90, -86, -82, -78, -74, (always), -78, -74, -70, -66, -62, -58, -54, Positive infinity (never) -98, -94, -90, -86, -82, -78, -74, (always), -78, -74, -70, -66, -62, -58, -54, Positive infinity (never)
Unit
MML Comman d
Impact
Qsearch P
15
0~15
None
SET GCELLC CUTRAN SYS (Optional)
Cell
Qsearch C
15
0~15 Use_Qsearch _I(Use Qsearch_I), Always (Always)
None
SET GCELLC CUTRAN SYS (Optional) SET GCELLC CUTRAN SYS (Optional) SET GCELLH OBASIC (Optional) SET GCELLC CUTRAN SYS (Optional) SET GCELLC CUTRAN SYS (Optional)
Cell
Qsearch C Initial Inter-RAT Cell Reselection Enable
Use_Qse arch_I
Use_Qsea rch_I, Always
None
Cell
NO
NO(No), YES(Yes)
NO, YES Negative infinity, -28~28, step: 4 -20, -6, -18, -8, -16, -10, -14, -12
None
Cell
FDD Q Offset
0~15
dB
Cell
FDD Qmin
0~7
dB
Cell
Issue 08 (2011-09-30)
146
Parameter Inter-RAT In BSC Handover Enable Inter-RAT Out BSC Handover Enable
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLH OBASIC (Optional) SET GCELLH OBASIC (Optional) SET GCELLH OUTRAN FDD (Optional) SET GCELLH OUTRAN TDD (Optional) SET GCELLH OUTRAN FDD (Optional) SET GCELLH OUTRAN TDD (Optional) SET GCELLH OUTRAN FDD (Optional) SET GCELLH OUTRAN TDD (Optional) SET GCELLC CUTRAN SYS (Optional)
Impact
NO
NO(No), YES(Yes)
NO, YES
None
Cell
NO
NO(No), YES(Yes) Pre_2G_Cell (Preference for 2G cell), Pre_3G_Cell (Preference for 3G cell), Pre_2G_Cell Thres (Preference 2G cell by thresh)
NO, YES
None
Cell
Inter-rat HO Preference
Pre_2G_ CellThre s
Pre_2G_ Cell, Pre_3G_ Cell, Pre_2G_ CellThres
None
Cell
HO Preference Threshold for 2G Cell
25
0~63
0~63
dB
Cell
Better 3G Cell HO Allowed
NO
NO(No), YES(Yes) RSCP (RSCP), EcN0(Ec/ N0)
NO, YES
None
Cell
FDD REP QUANT
RSCP
RSCP, EcN0
None
Cell
Issue 08 (2011-09-30)
147
Parameter FDD 3G Better Cell HO Valid Time
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d ADD G3GNCE LL (Optional) SET GCELLH OUTRAN FDD (Optional) SET GCELLH OUTRAN TDD (Optional) ADD G3GNCE LL (Optional) SET GCELLH OUTRAN FDD (Optional) SET GCELLH OINTERR ATLDB (Optional) ADD GEXT2G CELL (Optional) ADD GEXT3G CELL (Optional) SET GCELLH OAD (Optional) SET OTHSOF TPARA (Optional)
Impact
1~32
0.5~16, step:0.5
Cell
RSCP Threshold for Better 3G Cell HO FDD 3G Better Cell HO Watch Time Ec/No Threshold for Better 3G Cell HO Allow InterRAT Load HO in Connect State
50
0~63
0~63
dB
Cell
10
1~32
0.5~16, step:0.5
Cell
35
0~49
0~49
dB
Cell
NO
NO(No), YES(Yes)
NO, YES
None
Cell
Load handover Load Accept Threshold Service Based Handover Switch
80
0~100 CLOSE (Close), OPEN(Open)
0~100
per cent
Cell
CLOSE
CLOSE, OPEN
None
BSC
Issue 08 (2011-09-30)
148
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLC CBASIC (Optional) ADD GEXT3G CELL (Mandator y) SET OTHSOF TPARA (Optional) SET OTHSOF TPARA (Optional)
Impact
ECSC
YES
NO(No), YES(Yes)
NO, YES
None
Cell
Utran Cell Type
None
FDD(FDD), TDD(TDD)
FDD, TDD
None
Cell
Send 3G Class Flag
YES
NO(No), YES(Yes)
NO, YES
None
BSC
NO
NO(No), YES(Yes)
NO, YES
None
BSC
2.4.6 Counters
For the counters, see the BSC6900 GSM Performance Counter Reference.
2.4.7 Glossary

l l l l l l l l l
Issue 08 (2011-09-30)
3GPP TS 45.008 Radio subsystem link control 3GPP TS 44.018 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol 3GPP TS 48.008 Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.5 2G/3G Interoperability (TDD)

2.5.1 Introduction
2.5.1.1 Scope
This document describes the 2G/3G Interoperability (TDD) feature of Huawei GBSS. It covers the functions of and technologies related to this feature, including measurement of neighboring UMTS cells, inter-radio access technology (inter-RAT) cell reselection, inter-RAT handover,GSM/TD-SCDMA Interoperability Optimization and PS GSM and TD-SCDMA Interoperability Optimization.


The change history provides information on the changes on the 2G/3G Interoperability (TDD) feature in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the 2G/3G Interoperability (TDD) feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows: l l 02 (2009-09-30) 01 (2009-06-30)
02(2009-09-30)
Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The document organization is optimized. Parameter Change None. None.
01(2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description Section 2.5.3.2.3 Fast 3G Reselection at 2G CS Call Release is added. None. Parameter Change The following parameter is added: l Select 3G Cell After Call Release None.
2.5.2 Overview
The UMTS network and the GSM network will coexist and provide services together for a long time. To facilitate the service provision by both the networks, Huawei introduces 2G/3G interoperability (TDD) into the BSS, This feature involves inter-RAT reselection and inter-RAT cell handover between GSM and UMTS. 2G/3G interoperability (TDD) provides a smooth evolution from GSM to UMTS can be achieved, thus saving the investment. For the operator that has both the UMTS network and the GSM network, 2G/3G interoperability (TDD) enables the GSM network and the UMTS network to complement each other, thus expanding the network coverage and improving the service quality. For example, when a dual-mode MS moves to an area without UMTS coverage, it can reselect or be handed over to a GSM cell through 2G/3G interoperability (TDD). The continous coverage brought by this feature improves the user experience. For the areas covered by both the GSM network and the UMTS network, 2G/3G interoperability (TDD) can be performed to achieve traffic balance between the GSM system and the UMTS system. For example, when the traffic load in a GSM cell is too heavy, 2G/3G interoperability (TDD) can be performed to hand over some calls from the GSM cell to a UMTS cell. In the areas covered by both the GSM network and the UMTS network, 2G/3G interoperability (TDD) differentiates the access policy for the GSM network from that for the UMTS network.
For example, the GSM network can be preferentially selected by CS services and the UMTS network can be preferentially selected by PS services. In this way,the GSM network and the UMTS network complement each other.
NOTE
All the MSs involved in this feature are dual-mode MSs.

2.5.3.1 Measurement of Neighboring UMTS Cells
The system information (SI) contains UMTS cell reselection parameters and the list of neighboring UMTS cells, based on which the MS measures the neighboring cell information and performs cell reselection and handover. The SI includes SI 2ter, System Information 2Quater, and Measurement Information. System Information 2ter and System Information 2Quater are sent on the broadcast control channel (BCCH), and Measurement Information is sent on the slow associated control channel (SACCH). Whether System Information 2Quater is sent is controlled by theSupport Sent 2QUATER parameter. The MSs in a GSM cell measures the quality of signals in its neighboring UMTS cells while measuring the level of signals in its neighboring GSM cells. To reduce unnecessary measurements and power consumption of MSs, the BSS uses parameters to control the measurement of neighboring cells. The MSs may perform inter-RAT cell reselection in either idle mode or packet transfer mode, and perform inter-RAT handover in dedicated mode. In addition, operators can set measurement parameters to different values for the MSs in different modes. In idle mode, the MSs determine whether to measure neighboring UMTS cells based on Qsearch I and the receive level of the serving cell. The conditions for triggering the measurement vary with the value of Qsearch I. l l l l If the value of Qsearch I ranges from 0 to 6, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is lower than the value of Qsearch I. If the value of Qsearch I ranges from 8 to 14, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is higher than the value of Qsearch I. If the value of Qsearch I is 7, the MSs always measure the neighboring UMTS cells regardless of the receive level of the serving cell. If the value of Qsearch I is 15, the MSs never measure the neighboring UMTS cells regardless of the receive level of the serving cell.
In packet transfer mode, the MSs in determine whether to measure neighboring UMTS cells based on Qsearch P and the receive level of the serving cell. The conditions for triggering the measurement vary with the value of Qsearch P. l l l If the value of Qsearch P ranges from 0 to 6, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is lower than the value of Qsearch P. If the value of Qsearch P ranges from 8 to 14, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is higher than the value of Qsearch P. If the value of Qsearch P is 7, the MSs always measure the neighboring UMTS cells regardless of the receive level of the serving cell.
Issue 08 (2011-09-30)
If the value of Qsearch P is 15, the MSs never measure the neighboring UMTS cells regardless of the receive level of the serving cell.
In packet transfer mode, the MSs determine whether to measure neighboring UMTS cells based on Qsearch C and the receive level of the serving cell. The conditions for triggering the measurement vary with the value of Qsearch C. l l l l If the value of Qsearch C ranges from 0 to 6, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is lower than the value of Qsearch C. If the value of Qsearch C ranges from 8 to 14, the MSs measure the neighboring UMTS cells when the receive level of the serving cell is higher than the value of Qsearch C. If the value of Qsearch C is 7, the MSs always measure the neighboring UMTS cells regardless of the receive level of the serving cell. If the value of Qsearch C is 15, the MSs never measure the neighboring UMTS cells regardless of the receive level of the serving cell.
Qsearch C is contained in the Measurement Information. After entering the dedicated mode, MSs attempt to obtain Qsearch C from the Measurement Information transmitted on the SACCH. Before obtaining Qsearch C, MSs assigns Qsearch C a value according to the value of Qsearch C Initial transmitted on the BCCH.
2.5.3.2 2G/3G Inter-RAT Cell Reselection

2G/3G inter-RAT cell reselection refers to the cell reselection between the GSM network and the UMTS network. Cell reselection is performed mainly by the MS. For MSs in idle mode, 2G/3G interoperability is mainly performed to implement cell reselection. An MS camping on a GSM cell can reselect a UMTS cell. It measures neighboring UMTS cells, and then determines whether to reselect the UMTS cell according to cell reselection parameters. The cell reselection procedure in packet transfer mode is the same as that in idle mode. MSs in packet transfer mode can reselect a UMTS cell for data services through autonomous cell reselection, Network Assisted Cell Change (NACC), or Network Control Mode 2 (NC2). The autonomous cell reselection is performed by the MS without the network intervention. In NACC and NC2, the network instructs the MS to camp on a desired cell through signaling. The Inter-RAT Cell Reselection Enable parameter determines whether cell reselection between GSM and UMTS is enabled. When Inter-RAT Cell Reselection Enable is set to No, the BSS does not send the list of neighboring UMTS cell or inter-RAT cell reselection parameters. Therefore, MSs in a GSM cell cannot reselect a UMTS cell.
?.1. Inter-RAT Cell Reselection from UMTS to GSM

When an MS moves into a GSM coverage area and reselects a GSM cell, the MS initiates a location update in the GSM network. The GSM network processes the location update regardless of whether the MS is from a UMTS cell or from a GSM cell. The BSS processes, the UMTS-to-GSM cell reselection in the same way as the cell reselection with the GSM network.Therefore, this document does not describe the related information.
?.2. Inter-RAT Cell Reselection from GSM to UMTS

An MS in a GSM cell obtains the list of neighboring UMTS cells and cell reselection parameters through System Information 2ter and System Information 2Quater. Based on the list and
parameters, the MS measures the neighboring UMTS cells. When the MS is in idle mode or packet transfer mode, the mechanism for cell reselection from a GSM cell to the UMTS cell is the same as that between GSM cells. The GSM network controls the cell reselection from the GSM cell to a UMTS cell through TDD Cell Reselect Diversity. TDD Cell Reselect Diversity indicates the signal strength difference between candidate UMTS cells and the serving GSM cell. This parameter is a key factor for controlling the cell reselection from the GSM cell to the UMTS cell. When TDD Cell Reselect Diversity is set to a small value, the cell reselection condition is easy to meet. In this case, the number of MSs that camp on the GSM cell reduces. When TDD Cell Reselect Diversity is set to a great value, the cell reselection condition is difficult to meet. In this case, the number of MSs that camp on the GSM cell is increases. For the UMTS TDD cell, the measurement quantity to be used is Received Signal Code Power (RSCP) of the Common Pilot Channel (CPICH). If the measurement result meets the following condition within 5s, the MS initiates the cell reselection from GSM to UMTS. If more than one UMTS cell meet the condition, the MS selects a cell with the highest RSCP as the target cell. l CPICH RSCP > RLA_C + TDD Cell Reselect Diversity
In the preceding condition, RLA_C refers to the average receive level. The RSCP of the neighboring UMTS cell must be greater than the sum of the value of TDD Cell Reselect Diversity and the average receive level of the serving cell. In addition, the RSCP of the neighboring UMTS cell must be greater than the sum of the value of TDD Cell Reselect Diversity and the receive level of each GSM neighboring cell. The inter-RAT cell reselection from GSM to UMTS cannot be triggered within 5s after the cell reselection from UMTS to GSM. If the inter-RAT cell reselection from GSM to UMTS is triggered within 15s after the cell reselection from UMTS to GSM, the value of TDD Cell Reselect Diversity must be increased by 5 dB. When the condition for the cell reselection from GSM to UMTS and the condition for the cell reselection between GSM cells are met, the MS selects the UMTS cell as the target cell.
?.3. Fast 3G Reselection at 2G CS Call Release
Overview
In normal cases, after an MS terminates a call in a GSM cell, it camps on the GSM cell. if a neighboring UMTS cell meets the requirements for cell reselection, the MS camps on the UMTS cell after the cell reselection. Before initiating the UMTS cell reselection, the MS must receive SI and calculate cell reselection parameters. With the Fast 3G Reselection at 2G CS Call Release feature, after an MS terminates a call in a GSM cell, the BSS determines the best neighboring UMTS cell based on the measurement of neighboring UMTS cells Then, The BSS contains the frequency information on the neighboring UMTS cell in a Channel Release message and sends the message to the MS, specifying the UMTS cell that the MS will camp on. In this way, the MS camps on a UMTS cell without calculating cell reselection parameters, thus accelerating cell reselection. In addition, the MS camps on the UMTS cell for a longer period, increasing the revenue of operators in the UMTS network. This feature is effective when Select 3G Cell After Call Release is set to YES.
NOTE
A UMTS cell is classified into the UTRAN FDD cell and the UTRAN TDD cell.
Issue 08 (2011-09-30)
154
Procedure
Take the case of call termination by the MS as an example. Figure 2-9 shows the cell reselection procedure with an MS-terminated call as an example. Figure 2-9 Cell reselection procedure
1.
After receiving a Release Complete message from the MS, the MSC sends a Clear Command message to the BSC to instruct the BSC to release the occupied resources on the A and Um interfaces. The BSC sends a Channel Release message to the MS to instruct the MS to release the TCH or SDCCH on the Um interface. The Channel Release message may carry the information element "Cell selection indicator after release of all TCH and SDCCH", which contains the information about the target neighboring UMTS cell. After receiving the Channel Release message, the MS disconnects the uplink signaling link. Then, the MS sends a DISC frame to the BTS to instruct the BTS to release the TCH or SDCCH. After receiving the UA message, the MS switches to the idle mode and initiates cell reselection. If... The Channel Release message contains the information element "Cell selection indicator after release of all TCH and SDCCH", The Channel Release message does not contain the information element "Cell selection indicator after release of all TCH and SDCCH", Then... The MS attempts to camp on the cell indicated in the Channel Release message.
2.
3.
4.
The MS attempts to camp on the cell where the TCH or SDCCH has been released.
Issue 08 (2011-09-30)
155
5.
If 4 fails, the MS performs a common cell reselection procedure. For details about a common cell reselection procedure, see section 2.4.3.3.2 Inter-RAT Cell Reselection from GSM to UMTS.
Before sending the Channel Release message, the BSC determines whether to carry the information element "Cell selection indicator after release of all TCH and SDCCH" in the message. 1. If Select 3G Cell After Call Release is set to YES, the procedure proceeds to 2. Otherwise, the procedure is complete, and the BSC sends the MS the Channel Release message. which does not carry the information element "Cell selection indicator after release of all TCH and SDCCH". The BSC determines whether an MS supports both GSM and UMTS according to the information contained in the classmark. If the classmark does not indicate the MS capability of supporting the GSM/UMTS, the procedure proceeds to 3. Otherwise, the procedure is complete, and the BSC sends the MS the Channel Release message, which does not carry the information element "Cell selection indicator after release of all TCH and SDCCH". The BSC figures out the best neighboring UMTS cell based on the related measurement report, and then the procedure proceeds to 4. If there is no measurement report or the measurement report does not contain the information about the neighboring UMTS cell, the procedure is complete, and the BSC sends the MS the Channel Release message, which does not carry the information element "Cell selection indicator after release of all TCH and SDCCH". If the measurement report indicates a neighboring UMTS FDD cell, Cell Selection Indicator is set to UTRAN FDD Description. If the measurement report indicates a neighboring UTRAN TDD cell, Cell Selection Indicator is set to UTRAN TDD Description, and the procedure is complete. Meanwhile, the BSC sends the MS the Channel Release message, which contains the information element "Cell selection indicator after release of all TCH and SDCCH".
2.
3.
4.
?.4. NACC and NC2

When MS is in packet transfer mode, Network Assisted Cell Change (NACC) and (Network Control Mode 2) NC2 can be performed for inter-RAT cell reselection. If the Iur-g interface exists between the BSC and RNC, the UMTS-to-GSM NACC procedure is an optimized NACC procedure. In this case, the MS obtains the SI of the target cell directly over the Iur-g interface. For details, see 2.59 NACC and 2.60 NC2.

The 2G/3G inter-RAT handover involves the handover from GSM to UMTS and the handover from UMTS to GSM. The handover is controlled mainly by the network. For MSs in dedicated mode, inter-RAT handovers can be performed, including the emergency handover, better cell handover, inter-RAT load handover, and inter-RAT service handover. Emergency handover refers to the handover that is triggered when the call cannot be processed in the serving cell because of poor coverage or other reasons during the CS service of the dualmode MS. For example, when an MS during a call in a GSM cell is moving outside the cell, the emergency handover is triggered to avoid call drops.
Better cell handover refers to the handover that is triggered when the signal quality of a neighboring cell is better than that of the serving cell, so that better service quality and user experience can be achieved. For example, when the signal quality of a UMTS cell is better than that of the serving GSM cell, MSs in the serving cell can be handed over to the UMTS cell to achieve better voice quality. Inter-RAT load handover refers to the handover wherein some calls served by a GSM cell are handed over to a UMTS cell or some of the calls served by a UMTS cell are handed over to a GSM cell because of heavy load in the serving cell. For an incoming inter-RAT handover to a GSM cell, if the traffic load in the target GSM cell is also heavy, the target cell rejects the handover to avoid ping-pong handovers. Inter-RAT service handover refers to the handover wherein the operator can choose the network that the MS will access through the MSC. For a call initiating an access request in a GSM cell, if the MSC indicates that the service handover should be performed, the BSS hands over the call to the UMTS cell. Otherwise, the BSS does not hand over the call to a UMTS cell when a handover is required during the call. When a cell delivers the neighboring TD-SCDMA cell information, MSs supplied by certain manufacturers may be restarted because defects exist in MS chips. To solve the problem, Huawei optimizes GSM/TD-SCDMA interoperability.
?.1. Inter-RAT Handover from UMTS to GSM

MSs in dedicated mode can be handed over from a UMTS cell to a GSM cell. The handover decision and handover procedure are controlled by the RNC. The BSS considers the incoming handover from UMTS to GSM as a common inter-BSC handover. The parameter Inter-RAT In BSC Handover Enable determines whether inter-RAT handover from UMTS to GSM is enabled. If Inter-RAT In BSC Handover Enable is set to No, the BSS rejects all the requests for the handover from UMTS to GSM.
?.2. Inter-RAT Handover from GSM to UMTS

The parameter Inter-RAT In BSC Handover Enable determines whether the inter-RAT handover from GSM to UMTS is enabled. If Inter-RAT In BSC Handover Enable is set to NO(No), the BSS rejects all the requests for the handover from GSM to UMTS and does not select a UMTS cell as the target cell. In dedicated mode, an MS obtains the list of neighboring UMTS cells and other information from the Measurement Information. Then, the MS reports the measurement result to the BSS through the measurement report. After receiving the measurement result, the BSS determines whether to initiate the inter-RAT handover from GSM to UMTS based on the measurement result and the handover algorithm. The inter-RAT handover from GSM to UMTS can be classified into emergency handover and better 3G cell handover. The algorithm for the emergency handover from GSM to UMTS is the same as that for a common emergency handover. For details, see 2.46 Handover. In the GSM network, the parameter Inter-rat HO Preference determines whether the GSM cell or the UMTS cell is preferentially selected as the target cell. l When Inter-rat HO Preference is set to Pre_2G_Cell(Preference for 2G cell), the BSC preferentially selects the GSM cell as the target cell.
Issue 08 (2011-09-30)
l l
When Inter-rat HO Preference is set to Pre_3G_Cell(Preference for 3G cell), the BSC preferentially selects the UMTS cell as the target cell. When Inter-rat HO Preference is set to Pre_2G_CellThres(Preference 2G cell by thresh), the BSC determines the target cell according to the levels of the neighboring GSM cells and the value of HO Preference Threshold for 2G Cell. If no neighboring GSM cell has a level higher than HO Preference Threshold for 2G Cell, the BSC selects a UMTS cell as the target cell.
Better 3G cell handover can be performed only when both Inter-RAT Out BSC Handover Enable and Better 3G Cell HO Allowed are set to YES(Yes). The system performs a handover decision based on the measurement result. l If there is TDD 3G Better Cell HO Valid Time in TDD 3G Better Cell HO Watch Time and the measured value meets the following condition, the better 3G cell handover is triggered. CPICH RSCP > RSCP Threshold for Better 3G Cell HO
?.3. 2G/3G Inter-RAT Load Handover

The parameters Inter-RAT Out BSC Handover Enable and Allow Inter-RAT Load HO in Connect State determine whether inter-RAT load handover is enabled. The algorithm for inter-RAT load handover is the same as that for load handover. For details, see 2.46.3.4.8 Load Handover in 2.46 Handover. The BSC obtains the traffic load on the UMTS cell from the load information contained in the handover request from UMTS to GSM. To avoid the ping-pong handover, the system takes the traffic load on the UMTS cell into consideration when initiating the inter-RAT load handover from GSM to UMTS. If the load on the UMTS cell exceeds Load handover Load Accept Threshold of the external 3G cell, the BSC does not consider that UMTS cell as the target cell.
?.4. 2G/3G Inter-RAT Service Handover

The parameters Inter-RAT Out BSC Handover Enable and Service Based Handover Switch determine whether inter-RAT service handover is enabled. The inter-RAT service handover is processed according to the service handover indication from the MSC. The MSC instructs the BSS whether the service handover should be performed through the Service Handover information element in the Assignment Request or Handover Request. The service handover indication in the Service Handover information element can be of three values: Handover to UTRAN or cdma2000 should be performed, Handover to UTRAN or cdma2000 should not be performed, or Handover to UTRAN or cdma2000 shall not be performed. The BSC handles the handover request as follows: l If the service handover indication is "Handover to UTRAN or cdma2000 should be performed", the BSC selects a UMTS cell from the neighboring cell list as the target cell, and then initiates the handover from GSM to UMTS. If the service handover indication is "Handover to UTRAN or cdma2000 should not be performed", the BSC does not initiate the handover procedure. If a handover is needed during the call, a GSM cell is preferentially selected as the target cell.
Issue 08 (2011-09-30)
158
If the service handover indication is "Handover to UTRAN or cdma2000 shall not be performed", the call is not allowed to be handed over to a UMTS cell. The BSC selects only the GSM cell as the target cell during the whole call.
2.5.3.4 GSM/TD-SCDMA Interoperability Optimization

After the GSM cell is configured with neighboring TD-SCDMA cells, some MSs restart or stop working. This is because these MSs have defects in system information decoding. To solve this problem, Huawei optimizes GSM/TD-SCDMA interoperability. The parameter TDD System Information Optimized Allowed determines whether to enable GSM/TD-SCDMA interoperability optimization. If TDD System Information Optimized Allowed is set to YES(Yes) and the neighboring UMTS cell of the )GSM cell is a TDD cell, the BSS adds a virtual FDD cell description before the TDD cell description when delivering the System Information 2Quater and Measurement Information. In addition, the BSS delivers only the frequency information of the TDD cell in the TDD cell description without scrambling code information. If the GSM cell has multiple neighboring TDD cells with the same frequency and different scrambling codes, the BSS delivers the description of only one cell in the System Information 2Quater and Measurement Information to the MS, that is, these neighboring TDD cells are regarded as one neighboring cell. The neighboring TDD cell of a GSM cell can be configured with a maximum of 16 frequencies.
NOTE
During network planning, different frequencies must be planned for the neighboring TDD cells of each GSM cell. Otherwise, the handover from the GSM cell to the TD-SCDMA cell may fail.
In addition, the parameter TDD MI System INFO Broadcasting Prohibit determines whether the BSS delivers the Measurement Information that contains the neighboring 3G cell information. This prevents faults occurring in some MSs with decoding defects.
2.5.3.5 PS GSM and TD-SCDMA Interoperability Optimization

When the network is not configured with the PBCCH, an MS in packet transfer mode performs the cell reselection procedure in idle mode. During the PS service, if an MS performs autonomous cell reselection from GSM to TDSCDMA, the KPIs may deteriorate after the cell reselection. To solve this problem, the BSC sends the PACKET MEASUREMENT ORDER message to the MS, instructing the MS to filter the neighboring TDD cell list. In this way, the MS in packet transfer mode does not reselect a neighboring TDD cell. l Prohibiting cell reselection from GSM to TD-SCDMA When TDD System Information Optimized Allowed is set to NO(No), the BSC sends the PACKET MEASUREMENT ORDER message to the MS after the PS service access is successful. The cell reselection parameter Qsearch P is set to 15 to prohibit the MS from listening to the neighboring TDD cell list, thus prohibiting the MS from reselecting the neighboring TDD cell. l Modifying parameter settings When the value of TDD MI System INFO Broadcasting Prohibit, Network Control Mode, or Cell Reselection MR Period in Packet Transfer Mode is changed, the BSC sends the PACKET MEASUREMENT ORDER message to all the MSs in packet transfer mode in the cell, instructing the MSs to update the parameter value dynamically.

Related Parameters in the System Information
2G/3G interoperability (TDD) requires the support from MSs. After 2G/3G interoperability (TDD) is enabled, the system should obtain the supporting capability of MSs. Therefore, the early classmark sending function should be enabled so that MSs report their support capability as soon as possible. Therefore, it is recommended that Send 3G Class Flag, Classmark Enquiry With 3G Request and ECSC be set toYES(Yes). When setting the inter-RAT cell reselection parameters and handover thresholds, take into account the consistency between GSM parameters and the UMTS parameters to avoid pingpong handovers. The network can control the cell reselection between GSM and UMTS using related parameters in the system information. If the operator requires that MSs access the UMTS network preferentially in the areas covered by the UMTS network, it is recommended that Qsearch I be set to 7. If Qsearch I be set to 7, so that the UMTS cell searching is performed. The value of TDD Cell Reselect Diversity determines cell reselection. If an MS is expected to camp on the UMTS network, the value of TDD Cell Reselect Diversity should be changed to ensure that the actual offset is a negative value.
NOTE
When the value of TDD Cell Reselect Diversity is smaller than 8, the corresponding actual offset is smaller than 0.
Neighboring UMTS Cell Configuration

Currently, the BSC6900 supports two types of neighboring UMTS cells using different access technologies. One is the neighboring WCDMA cell, a neighboring UMTS cell using FDD, which is called neighboring FDD cell. The other is the neighboring TD-SCDMA cell, a neighboring UMTS cell using TDD, which is called neighboring TDD cell. The neighboring UMTS cells of a cell must be all the neighboring FDD cells or neighboring TDD cells. The neighboring FDD cells and neighboring TDD cells cannot be configured for a GSM cell simultaneously. Before enabling 2G/3G interoperability (TDD), configure neighboring UMTS cells. You can configure the UMTS cell on the BSS side by adding external 3G cells. If the UMTS cell is a TD-SCDMA cell, set Utran Cell Type to TDD(TDD). When GSM/TD-SCDMA interoperability optimization is not enabled, a GSM cell can be configured with a maximum of 64 neighboring TDD cells. These neighboring cells can have a maximum of 3 frequencies, and a maximum of 32 neighboring TDD cells can have the same frequency. When GSM/TD-SCDMA interoperability optimization is enabled, the neighboring TDD cells of a GSM cell can have a maximum of 16 different. In addition, a maximum of 64 neighboring TDD cells can be configured. When GSM/TD-SCDMA interoperability optimization is enabled, the scrambling code information of TD-SCDMA cells is not delivered in the system information. If multiple neighboring TD-SCDMA cells of the GSM cell have the same frequency, the BSS cannot determine the mapping between the measurement information and the neighboring cells. This may cause handover failures easily. Therefore, when GSM/TD-SCDMA interoperability optimization is enabled, a GSM cell should not be configured with neighboring TDD cells that have the same frequency and different scrambling codes.
GSM/TD-SCDMA Interoperability Optimization

To avoid communication failures due to MS chip defects, set both TDD System Information Optimized Allowed and TDD MI System INFO Broadcasting Prohibit to YES(Yes) in the cell configured with neighboring TDD cells.
2.5.5 Parameters
This chapter describes the parameters related to 2G/3G Interoperability (TDD). For the meaning of each parameter, see Table 2-6. For the default value, value ranges, and MML commands of each parameter, see Table 2-7. Table 2-6 Parameter description (1) Parameter TDD 3G Better Cell HO Watch Time Better 3G Cell HO Allowed Better Cell HO Valid Time Cell Reselection MR Period in Packet Transfer Mode Description According to the P/N rule, if the conditions for the handover to a better 3G cell are met in P of N measurement reports, the handover is triggered. This parameter specifies the number N. This parameter specifies whether to allow 3G better cell handover algorithm. According to the P/N rule, if the conditions for the handover to a better cell due to interference are met for P seconds within N seconds, the handover is triggered. This parameter specifies the number P.
Cell reselection measurement report period in packet transmission mode The early classmark sending control (ECSC) parameter specifies whether the MSs in a cell use early classmark sending. After a successful immediate assignment, the MS sends additional classmark information to the network as early as possible. The additional classmark information mainly contains the CM3 (classmark 3) information. The CM3 (classmark 3) information contains the frequency band support capability of the MS (used for the future channel assignment), power information about each frequency band supported by the MS (used for the handover between different frequency bands), and encryption capability of the MS. If the receive level of the neighboring 2G cell that ranks the first in the candidate cell list is equal to or smaller than this threshold, the BSC preferentially selects a neighboring 3G cell as the handover target cell. Otherwise, the BSC preferentially selects a neighboring 2G cell as the handover target cell.
ECSC
Issue 08 (2011-09-30)
161
Parameter
Description When this parameter isset to Pre_2G_CellThres, the BSC preferentially selects a neighboring 3G cell as thehandover target cell if the receive level of the neighboring 2G cell that ranks the firstin the candidate cell list is equal to or smaller than "HO Preference Threshold for 2GCell". Otherwise, the BSC preferentially selects a neighboring 2G cell as the handovertarget cell. This parameter specifies whether the handover from 3G cells to 2G cells is allowed. This parameter specifies whether the handover from 2G cells to 3G cells is allowed. Network control mode for cell reselection of the MS. There are three modes. NC0: normal MS control. The MS shall perform autonomous cell reselection. NC1: MS control with measurement reports. The MS shall send measurement reports to the network and the MS shall perform autonomous cell re-selection. NC2: network control. The MS shall send measurement reports to the network . The MS shall only perform autonomous cell reselection when the reselection is triggered by a downlink signaling failure or a random access failure.When this parameter is set to NC2 and "Support NC2" in "SET GCELLGPRS" is set to "YES", the network side can control the cell reselection for the MS. This parameter specifies the level threshold for cell reselection in idle mode. In idle mode, if the signal level of the serving cell is below [0, 7] or above [8, 15], the MS starts to search for 3G cells. For example, if this parameter is set to 5 and if the signal level of the serving cell is lower than 5, the MS starts to search for 3G cells; if this parameter is set to 10 and if the signal level of the serving cell is above 10, then the MS starts to search for 3G cells. The values of this parameter correspond to the following decibel values: 0: -98 dBm 1: -94 dBm 2: -90 dBm 3: -86 dBm 4: -82 dBm 5: -78 dBm 6: -74 dBm 7: (always), that is, the MS keeps searching for 3G cells 8: -78 dBm 9: -74 dBm 10: -70 dBm 11: -66 dBm 12: -62 dBm 13: -58 dBm 14: -54 dBm 15: (never), that is, the MS does not search for 3G cells This parameter specifies one threshold of the signal level for cell reselection in packet transfer mode. In packet transfer mode, if the signal level of the serving cell is below [0, 7] or above [8, 15], the MS starts to search for 3G cells. For example, if this parameter is set to 5 and if the signal level of the serving cell is lower than 5, the MS starts to search for 3G cells; if this parameter is set to 10 and if the signal level of the serving cell is above 10, then the MS starts to search for 3G cells. The values of this parameter correspond to the following decibel values: 0: -98 dBm 1: -94 dBm 2: -90 dBm 3: -86 dBm 4: -82 dBm 5: -78 dBm 6: -74 dBm 7: (always), that is, the MS keeps searching for 3G cells 8: -78 dBm 9: -74 dBm 10: -70 dBm 11: -66 dBm 12: -62 dBm 13: -58 dBm 14: -54 dBm 15: (never), that is, the MS does not search for 3G cells
Inter-rat HO Preference Inter-RAT In BSC Handover Enable Inter-RAT Out BSC Handover Enable
Network Control Mode
Qsearch I
Qsearch P
Issue 08 (2011-09-30)
162
Parameter RSCP Threshold for Better 3G Cell HO Select 3G Cell After Call Release TDD Cell Reselect Diversity TDD MI System INFO Broadcasting Prohibit TDD System Information Optimized Allowed Utran Cell Type
Description
The 3G better cell handover is triggered only when the RSCP of a neighboring 3G cell is greater than this threshold for a period of time. This parameter specifies whether to allow a mobile phone to preferentially camp on a 3G cell after a call is terminated in the areas covered by both the GSM network and the UMTS network. A TDD cell can become a candidate cell only when the average receive level of the TDD cell is greater than the TDD Cell Reselect Diversity of the serving cell. The value of this parameter corresponds to the following decibel value: 0: negative infinity 1: -28 dB 2: -24 dB ... 15: 28 dB This parameter specifies whether to send the system information MI which contains the 3G neighboring cell information in the TDD neighboring cell. The value YES(YES) indicates that the MI is sent, and the value NO(NO) indicates that the MI is not sent. This parameter specifies whether to optimize the system information 2Quater and MI of the TDD neighboring cell. That is, to add an FDD neighboring cell information before the TDD neighboring cell information to solve the compatibility problem of some dual-mode MSs. This parameter specifies the type of a 3G cell. A cell type can be Frequency Division Duplex (FDD) or Time Division Duplex (TDD). Whether the SI Type 3 message contains the 3G Early Classmark Sending Restriction field. The 3G Early Classmark Sending Restriction field is used to notify the MS of whether the early classmark message contains the 3G classmark message. This parameter is valid for dual-mode MSs and is invalid for single-mode MSs. Whether to enable the BSC to include the 3G classmark information element in the Classmark Request message that the BSC forwards from the MSC to an MS.
Send 3G Class Flag Classmark Enquiry With 3G Request
Table 2-7 Parameter description (2) Parameter Default Value GUI Value Range Actual Value Range Uni t MML Comma nd ADD G3GNCE LL (Optional ) Impact
TDD 3G Better Cell HO Watch Time
10
1~32
0.5~16, step: 0.5
Cell
Issue 08 (2011-09-30)
163
Parameter
Default Value
GUI Value Range
Actual Value Range
Uni t
MML Comma nd SET GCELLH OUTRA NFDD (Optional ) SET GCELLH OUTRA NTDD (Optional ) Cell ADD G2GNCE LL (Optional )
Impact
Better 3G Cell HO Allowed
NO
NO(No), YES(Yes)
NO, YES
Non e
Cell
Better Cell HO Valid Time
1~32 0.48sec (0.48sec), 0.96sec (0.96sec), 1.92sec (1.92sec), 3.84sec (3.84sec), 7.68sec (7.68sec), 15.36sec (15.36sec), 30.72sec (30.72sec), 61.44sec (61.44sec)
0.5~16, step: 0.5
Cell
Cell Reselection MR Period in Packet Transfer Mode
0.96sec
0.48sec, 0.96sec, 1.92sec, 3.84sec, 7.68sec, 15.36sec, 30.72sec, 61.44sec
SET GCELLN WCTRL MSRPAR A (Optional ) SET GCELLC CBASIC (Optional )
Cell
ECSC
YES
NO(No), YES(Yes)
NO, YES
Non e
Cell
Issue 08 (2011-09-30)
164
Parameter
Default Value
GUI Value Range
Actual Value Range
Uni t
MML Comma nd SET GCELLH OUTRA NFDD (Optional ) SET GCELLH OUTRA NTDD (Optional ) SET GCELLH OUTRA NFDD (Optional ) SET GCELLH OUTRA NTDD (Optional ) SET GCELLH OBASIC (Optional ) SET GCELLH OBASIC (Optional ) SET GCELLP SBASE (Optional ) SET GCELLC CUTRAN SYS (Optional )
Impact
25
0~63 Pre_2G_Cell (Preference for 2G cell), Pre_3G_Cell (Preference for 3G cell), Pre_2G_Cell Thres (Preference 2G cell by thresh)
0~63
dB
Cell
Inter-rat HO Preference Inter-RAT In BSC Handover Enable Inter-RAT Out BSC Handover Enable
Pre_2G_C ellThres
Pre_2G_Cell, Pre_3G_Cell, Pre_2G_CellT hres
Non e
Cell
NO
NO(No), YES(Yes)
NO, YES
Non e
Cell
NO
NO(No), YES(Yes)
NO, YES
Non e
Cell
NC0
NC0(NC0), NC1(NC1), NC2(NC2)
NC0, NC1, NC2 -98, -94, -90, -86, -82, -78, -74, (always), -78, -74, -70, -66, -62, -58, -54, Positive infinity(never)
Non e
Cell
Qsearch I
15
0~15
Non e
Cell
Issue 08 (2011-09-30)
165
Parameter
Default Value
GUI Value Range
Actual Value Range -98, -94, -90, -86, -82, -78, -74, (always), -78, -74, -70, -66, -62, -58, -54, Positive infinity(never)
Uni t
MML Comma nd SET GCELLC CUTRAN SYS (Optional ) SET GCELLH OUTRA NFDD (Optional ) SET GCELLH OUTRA NTDD (Optional ) SET GCELLC CAD (Optional ) SET GCELLC CUTRAN SYS (Optional ) SET GCELLC CUTRAN SYS (Optional ) SET GCELLC CUTRAN SYS (Optional )
Impact
Qsearch P
15
0~15
Non e
Cell
RSCP Threshold for Better 3G Cell HO
50
0~63
0~63
dB
Cell
Select 3G Cell After Call Release
NO
NO(No), YES(Yes)
NO, YES
Non e
Cell
TDD Cell Reselect Diversity
0~15
Negative infinity, -28~28, step: 4
dB
Cell
TDD MI System INFO Broadcasting Prohibit
NO
NO(No), YES(Yes)
NO, YES
Non e
Cell
TDD System Information Optimized Allowed
NO
NO(No), YES(Yes)
NO, YES
Non e
Cell
Issue 08 (2011-09-30)
166
Parameter
Default Value
GUI Value Range
Actual Value Range
Uni t
MML Comma nd ADD GEXT3G CELL (Mandato ry) SET OTHSOF TPARA (Optional ) SET OTHSOF TPARA (Optional )
Impact
Utran Cell Type
None
FDD(FDD), TDD(TDD)
FDD, TDD
Non e
Cell
Send 3G Class Flag
YES
NO(No), YES(Yes)
NO, YES
Non e
BSC
NO
NO(No), YES(Yes)
NO, YES
Non e
BSC
2.5.6 Counters
2.5.7 Glossary

l l l l l l l l l 3GPP TS 45.008 Radio subsystem link control 3GPP TS 44.018 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol 3GPP TS 48.008 Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.6 Abis Bypass

2.6.1 Introduction
2.6.1.1 Scope
This document describes the application scenarios and key technologies related to Abis Bypass.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the Abis Bypass feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change
Issue 08 (2011-09-30)
Change Description None.
Parameter Change None.
168
Change Type Editorial change
Change Description The structure of the document is optimized.
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 has no change.
2.6.2 Overview
In the chain topology, if a BTS in the network is powered off or a transmission link is faulty, services on all the BTSs following the faulty BTS or following the faulty transmission link are disrupted. The TMU stops working if the BTS is powered off. For example, in a chain topology without the Abis Bypass as shown in Figure 2-10, if BTS 2 is powered off and its TMU stops working, the services on both BTS 2 and BTS 3 are disrupted. Figure 2-10 Influence of BTS power failure without Abis Bypass
Abis Bypass is introduced in the network with the chain topology to avoid the problem of service disruption on other BTSs upon the power failure of one BTS. With the Abis Bypass feature, a bypass transmission link is formed within the BTS that is powered off to transfer data to other BTSs following the faulty BTS on the chain. Thus, the power failure of a BTS will not affect the normal services on the subsequent BTSs on the chain. For example, in a chain topology with Abis Bypass as shown in Figure 2-11, the bypass board within BTS 2 provides a bypass transmission link if the TMU stops working upon power failure of BTS 2. In this case, only the services on BTS 2 are disrupted without affecting the services on BTS 3.
Issue 08 (2011-09-30)
169
Figure 2-11 Influence of BTS power failure with Abis Bypass
The BSS uses bypass loopback upon power failure to identify whether a failure is due to a faulty transmission link or the BTS power failure.
NOTE
The 3012 series base stations support bypass loopback upon power failure, but the 3900 series base stations do not support this function.

2.6.3.1 Key Technologies Bypass Upon BTS Power Failure
The following description takes the BTS3012 as an example (see Figure 2-12). When the BTS is powered on, switches K1 and K2 are connected to contact 1 and contact 2 respectively. Thus, the data flow goes to the DTMU first. When the BTS is powered off, switches K1 and K2 are connected to contact 1' and contact 2' respectively to form a bypass within the DABB. Figure 2-12 Bypass upon BTS power failure
Loopback Upon BTS Power Failure

In a chain topology as shown in Figure 2-13,
l l
If the transmission link between BTS 1 and BTS 2 is faulty, BTS 2 and all the following BTSs cannot be observed on the BSC. If BTS 2 is powered off, only BTS 2 is not observed on the BSC.
Figure 2-13 Schematic view of the BSS configured with bypass boards
The loopback function upon power failure helps to identify the BTS power failure from the transmission link fault. The function, however, is not applicable to the last BTS on the chain. For the last BTS on the chain, set the DIP switches on its bypass board so that the transmission link through the last BTS is short-circuited when the BTS is powered off. Thus, the loopback test can be performed on the BSC side to locate the fault.
2.6.4 Parameters
None.
2.6.5 Counters
2.6.6 Glossary

This chapter lists the reference documents related to Abis Bypass. l l BSC6900 Feature List BSC6900 Optional Feature Description
2.7 Acoustic Echo Cancellation

2.7.1 Introduction
2.7.1.1 Scope
This document describes acoustic echo cancellation (AEC) feature of Huawei GSM BSS. It covers the function of and technologies mechanisms regarding AEC.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change: refers to the change in the Acoustic Echo Cancellation feature of a specific product version. l Editorial change Editorial change: refers to changes in information that has already been included, or the addition of information that was not provided in the pervious version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30)) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
Issue 08 (2011-09-30)
172
01(2009-06-30)
This is the initial commercial release of GBSS9.0. Compared with 01 (2008-04-30) of GBSS8.1, issue 01(2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
2.7.2 Overview
Echo refers to the phenomenon in which a calling party not only hears the voice from the called party but also hears its own voice when the calling party makes a call to another MS or to a fixed phone. The acoustic isolation feature of some MSs does not comply with the GSM protocol requirements. Therefore, the downlink voice generated by the receiver of the MS enters the transmitter of the MS, mixes with the uplink voice, and then returns to the peer receiver. With the delay of the wireless communication system, the acoustic echo is formed. The acoustic echo exists only in the uplink speech. The AEC feature of the BSC is implemented by the DSP of the DPU board. The DSP of the DPU board analyzes the uplink and downlink digital voice signals, searches the acoustic echoes in the uplink voice, and suppresses the acoustic echoes.

AEC eliminates the uplink acoustic echoes based on the speech signal features. The AEC feature is enabled only when the AEC Switch parameter is set to Open. AEC performs the following operations to eliminate the uplink acoustic echoes: 1. 2. AEC checks the downlink speech signals and stores the downlink speech signal features. AEC searches the stored downlink speech signal features based on the setting of the AEC Echo Path Delay parameter, and then compares the downlink speech signal features with the uplink speech signal features to determine whether acoustic echoes exist in the uplink speech signals. l If acoustic echoes do not exist in the uplink speech signals or the acoustic echoes are much weaker than the uplink speech signals, AEC does not process the uplink speech signals. l If acoustic echoes exist in the uplink speech signals, AEC performs step 3. 3. AEC further analyzes the uplink speech signals based on settings of the parameters AEC Echo Return Loss and AEC SNR Gate. If downlink acoustic echoes exist in the uplink speech signals or there is no uplink speech signal, AEC gradually attenuates the acoustic echoes. If the level of the downlink acoustic echoes in the uplink speech signals reaches AEC Nlp Gate, AEC performs non-linear processing on the speech signals.
Issue 08 (2011-09-30)

NOTE
l The echo generated in the call between an MS and a fixed-line phone is an electric echo. The echo generated in the call between two MSs is an acoustic echo. l If a special transmission mode is used in the network (for example, if the satellite transmission is used over the Abis interface or Ater interface), the round trip time (RTT) in the special transmission mode needs to be estimated and AEC Path Delay (the maximum value for this parameter is 1000 ms) needs to be set. l If the Tandem Free Operation (TFO) feature is enabled at both ends of a call, the AEC feature does not take effect for this call.
2.7.4 Parameters
This chapter describes the parameters related to AEC. For the meaning of each parameter, see Table 2-8. For the default value, value ranges, and MML commands of each parameter, see Table 2-9. Table 2-8 Parameter description (1) Parameter AEC Echo Path Delay AEC Echo Return Loss Description If the echo path is traced, the echo is judged and controlled according to the trace result of the echo path parameters. Otherwise, the echo is judged and controlled according to the recommended value. This parameter is used for echo judgment and control when the echo parameters are not traced. If the local input voltage is lower than the value of this parameter and the remote end transmits the voice signal, the AEC function uses the comfort noise to replace the minor echo. In this case, the speech signals at low level may also be cut. Extra delay due to the transmission line. This parameter should be set according to the actual conditions and is applicable to satellite transmission. This parameter is used to determine whether there are speech signals at the local end. If the local SNR is lower than the value of this parameter, echo control is not performed. This parameter indicates whether the acoustic echo cancellation (AEC) functional switch is on or off.
AEC Nlp Gate
AEC Path Delay
AEC SNR Gate AEC Switch
Table 2-9 Parameter description (2) Parameter Defa ult Value GUI Value Range Actual Value Range Unit MML Command SET TCPARA (Optional) Impact
AEC Echo Path Delay

Issue 08 (2011-09-30)
400
0~600
0~600
ms
Board
174
Parameter
Defa ult Value
GUI Value Range
Actual Value Range
Unit
MML Command SET TCPARA (Optional) SET TCPARA (Optional) SET TCPARA (Optional) SET TCPARA (Optional) SET TCPARA (Optional)
Impact
AEC Echo Return Loss
20
0~60
0~60
dB
Board
AEC Nlp Gate
-50
-60~-35,0
-60~-35, 0
dBm
Board
AEC Path Delay
0~1000
0~1000
ms
Board
AEC SNR Gate
0~15 CLOSE (Close), OPEN (Open)
0~15
dB
Board
AEC Switch
CLOS E
CLOSE, OPEN
None
Board
2.7.5 Counters
None.
2.7.6 Glossary
2.7.7 References
None
2.8 AFC
2.8.1 Introduction
2.8.1.1 Scope
This document describes the application scenarios and technologies related to AFC.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the AFC feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
01 (2009-06-30)
2.8.2 Overview
Due to the frequent use of wireless network, the massive subscriber base has increasingly higher demands on the service quality of the wireless network coverage As the highways and express railways have been widely developed in European and American countries, there is a large market for high-speed access services in these countries. There is also an increasing market in China due to the massive rollout of express railways in recent years. In the high-speed transportation vehicles, the quality of the voice services as well as data services is a serious concern for the operators. In this case, the operators are seeking network solutions for better 2G services over the high-speed transportation system to improve the customer satisfactions. Express railways feature the high speed transportation, whereas high-speed access is always the challenge in the mobile communication field. In addition, the fast movement of the mobile terminals causes serious signal fading and Doppler frequency shift, which restrains the service quality that can be achieved by the operators. In the high-speed movement scenario, the Doppler frequency shift derives random signal fading, which increases the bit error rate (BER). In the GSM system, Doppler frequency shift reduces strength of the signal output by the relators, which affects the calculation of the channel factors. In this case, the GSM receiver may be out of synchronization with the channel model of the received signals, and thus the information cannot be demodulated. The effect of Doppler frequency shift is proportional to the moving speed of the MS and the communication frequency. When the moving speed of the MS reaches 200 km/h or higher, the signal-to-noise ratio (SNR) increases infinitely and may cause call drops or access failures. To solve this problem, Huawei base stations adopt the auto frequency correction (AFC) feature to compensate the Doppler frequency shift, thus ensuring successful high-speed access of the MSs and meeting the requirements of high-speed mobile communication services.

When the MS is moving fast along with the train, Doppler frequency shift occurs on the receive carrier. If the frequency shift is not corrected, the demodulation performance of the receiver deteriorates and the communication may fail. The AFC feature is characterized by the BTS frequency shift correction algorithm against fast movement. With this algorithm, the bit flows on the radio link between the BTS and the fastmoving MS are measured, and the frequency is automatically corrected against the Doppler frequency shift during the fast movement. In an open area, the signals between the BTS and the MS are typically propagated along the direct path or reflection path at a great reflection angle. In this case, the movement of the MS is more likely to incur the Doppler frequency shift in the downlink direction. The frequency shift of the MS receiving the signals is calculated according to the following formula: fd=fc/C x V x cos Here, fc represents the carrier frequency, C represents the electromagnetic wave propagation speed, V represents the MS moving speed, and represents the angle between the MS moving direction and the signal propagation path. If the MS is moving at a speed of 300 km/h on the 1800 MHz frequency band, the maximum frequency shift can be 500 Hz. The AFC function is controlled by Frequency Adjust Switch.
2.8.4 Parameters
This chapter describes the parameters related to AFC. For the meaning of each parameter, see Table 2-10. For the default value, value ranges, and MML commands of each parameter, see Table 2-11. Table 2-10 Parameter description (1) Parameter Description Whether to enable the automatic frequency correction algorithm. This parameter is used for the fast-moving handover algorithm. If the parameter is set to YES, the BTS calculates the speed at which an MS leaves or approaches it, and sends the BSC6900 the calculated speed in an uplink measurement report.
Frequency Adjust Switch
Table 2-11 Parameter description (2) Paramete r Default Value GUI Value Range Actual Value Range Unit MML Comman d SET GCELLO THEXT (Optional) Impact
Frequency Adjust Switch
NO
NO(No), YES(Yes)
NO, YES
None
Cell
2.8.5 Counters
2.8.6 Glossary

This chapter lists the reference documents related to AFC. l l BSC6900 Feature List BSC6900 Optional Feature Description
2.9 AMR
2.9.1 Introduction
2.9.1.1 Scope
This document describes the AMR feature. It describes AMR speech rate adjustment, rate adjustment threshold adaptation, AMR power control,and handover between AMR FR and AMR HR.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the AMR feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with 01 (2009-06-30), issue 02 (2009-09-30) incorporates the changes described in the following table. Change Type Feature change
Issue 08 (2011-09-30)
179
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description 2.9.3.3 Rate Adjustment Threshold Adaptation is optimized. Different power control strategies are used for AMR calls and nonAMR calls. Parameter Change The added parameters are listed as follows: l AMR Downlink Adaptive Threshold Allowed l Allow III Power Control For NonAMR l Allow III Power Control For AMR Editorial change The structure of the document is optimized. None.
2.9.2 Overview
AMR is an adaptive multi-rate voice coding/decoding, which is termed full-rate speech version 3 and half-rate speech version 3 in GSM specifications. AMR enables the BTS and the MS to automatically select an appropriate coding/decoding rate from the specified ACS according to the interference level in the radio environment. This enhances the anti-interference capability and the speech quality of the wireless communication system. AMR is classified into AMR FR and AMR HR. AMR specifies eight speech coding rates. Table 2-12 lists the speech coding rates supported by AMR FR and AMR HR. Table 2-12 AMR speech coding rates Coding Rate 4.75 kbit/s 5.15 kbit/s 5.90 kbit/s 6.70 kbit/s
Issue 08 (2011-09-30)
AMR FR
AMR HR
180
Coding Rate 7.40 kbit/s 7.95 kbit/s 10.2 kbit/s 12.2 kbit/s
NOTE -: not supported : supported
AMR FR
AMR HR -
Note: When Service Type of the BTS is set to IP or HDLC, Huawei BSS supports the AMR coding rate of 7.95 kbit/s. When Service Mode of the BTS is set to TDM, Huawei BSS does not support the AMR HR coding rate of 7.95 kbit/s.
As listed in Table 2-12, the coding rates of 12.2 kbit/s and 10.2 kbit/s are supported by only the AMR FR channel. The other six types of coding rates are supported by both the AMR FR channel and the AMR HR channel. Each ACS contains a maximum of four codec modes. One codec mode corresponds to one speech coding rate. l l For an AMR FR call, the ACS contains a maximum of four speech coding rates of the eight rates listed in Table 2-12. For an AMR HR call, the ACS contains a maximum of four speech coding rates of the six rates listed in Table 2-12.
When AMR is enabled on the network, the BSC selects an ACS and then a codec mode from the ACS during the call establishment or the handover procedure. Meanwhile, the MS and the BTS continuously measure the receive level, receive quality, and C/I ratio. According to the measurement results, the MS and the BTS continuously evaluate the interference level in the radio environment. The BTS then adjusts the speech coding rates of the MS and the BTS according to the evaluated interference level through the inband signaling.

2.9.3.1 Inband Signaling
Inband signaling is a type of signaling through which user data and control information are transmitted on the same channel. In this document, the inband signaling refers to the AMR control information such as the CMR and CMI that is transmitted through certain bits in the header of the Transcoder and Rate Adaptor Unit (TRAU) frame. During a call, the MS and the BTS continuously measure the interference level experienced by the signals and analyze the measurement results. Based on the measurement results, the AMR control information is then exchanged through the inband signaling to enable the BTS to adjust the speech coding rate involved in the ongoing speech service. The AMR control information is transmitted through certain bits in the header of the TRAU frame. The AMR control information can be classified into the following types:
Downlink Codec Mode Request (DL CMR): The DL CMR occupies two bits in the header of the TRAU frame. It is used by the MS to send the recommended DL codec mode to the BTS. Downlink Codec Mode Indication (DL CMI): The DL CMI occupies two bits in the header of the TRAU frame. It is used by the BTS to send the current DL codec mode to the MS. Uplink Codec Mode Command (UL CMC): The UL CMC occupies two bits in the header of the TRAU frame. It is used by the BTS to send the UL codec mode that should be used by the MS to the MS. Uplink Codec Mode Indication (UL CMI): The UL CMI occupies two bits in the header of the TRAU frame. It is used by the MS to send the current UL codec mode to the BTS. Uplink Maximum Codec Mode Command (UL Max CMC): The UL Max CMC occupies three bits in the header of the TRAU frame. To implement AMR codec mode adaptation, a Mode Control Entity is used in both the MS and the BTS, as shown in Figure 2-14. Figure 2-14 AMR codec mode adaptation
As shown in Figure 2-14, the AMR codec mode adaptation procedure is as follows: l Uplink direction 1. 2. 3. 4. l The BTS measures the receive quality of the UL speech and generates the Uplink Measurement (UL MEAS). The Mode Control Entity of the BTS updates the UL CMC based on the UL MEAS generated by the BTS. The BTS instructs the MS to change the UL codec mode through the UL CMC. The MS changes the UL codec mode as indicated by the UL CMC and then sends the UL CMI to the BTS to inform the BTS of the new UL codec mode. The MS measures the receive quality of the DL speech and generates the Downlink Measurement (DL MEAS). The Mode Control Entity of the MS converts the DL
Downlink direction 1.
Issue 08 (2011-09-30)
MEAS into the recommended DL codec mode. Then, the MS sends the recommended DL codec mode to the BTS through the DL CMR. 2. 3. The Mode Control Entity of the BTS updates the DL speech codec mode based on the recommended DL codec mode sent from the MS. The BTS instructs the MS to use the new DL codec mode through the DL CMI.
2.9.3.2 Speech Rate Adjustment

AMR speech rate adjustment is the process that the AMR codec mode of a call on a channel frequently changes to adapt to the variations of the interference level in the radio environment. Each AMR codec mode has an adjustment threshold, which is used to select the codec mode that is best suited to the C/I or BER ratio of the interference level in the radio environment. To avoid the constant changes of the codec mode, the process of hysteresis is introduced. The value of the threshold ranges from 0 to 63. Value 1 indicates 0.5 dB, and value 2 indicates 1 dB. The rest may be deduced by analogy. The value of the hysteresis ranges from 0 to 15. The hysteresis value complements the threshold. Figure 2-15 shows the procedure for AMR codec mode adjustment. Figure 2-15 Procedure for AMR codec mode adjustment
THR_N: AMR Coding Rate adj.thN (1N3)
HYST_N: AMR Coding Rate adj.hystN (1N3)
CODEC_MODE_1: indicates the lowest-bit-rate codec CODEC_MODE_2: indicates the codec mode whose mode bit rate is higher than only that of CODEC_MODE_1 (assume that there is more than one codec mode in the ACS) CODEC_MODE_3: indicates the codec mode whose CODEC_MODE_4: indicates the codec mode whose bit rate is the second highest in the ACS (assume that bit rate is the highest in the ACS (assume that there are there are more than two codec modes in the ACS) four codec modes in the ACS)
Assume that the currently used codec mode is CODEC_MODE_3. As shown in Figure 2-15, when the C/I ratio is greater than THR_3 plus HYST_3, the codec mode is changed to
CODEC_MODE_4; when the C/I ratio is smaller than THR_2, the codec mode is changed to CODEC_MODE_2. The procedure for AMR UL speech rate adjustment is similar to the procedure for AMR DL speech rate adjustment. The AMR UL codec mode is adjusted by the BTS, and the AMR DL codec mode is adjusted by the MS. Figure 2-16 shows the procedure through which the BTS adjusts the AMR UL codec mode. Figure 2-16 Procedure through which the BTS adjusts the AMR UL codec mode
THR_N: AMR UL Coding Rate adj.thN (1N3) HYST_N: AMR UL Coding Rate adj.hystN (1N3)
The procedure through which the BTS adjusts the AMR UL codec mode shown in Figure 2-16 is described as follows: 1. During AMR FR call establishment, AMR Starting Mode[F] specifies which codec mode in AMR ACS[F] should be used to make a call. During AMR HR call establishment, AMR
Issue 08 (2011-09-30)
Starting Mode[H] specifies which codec mode in AMR ACS[H] should be used to make a call. 2. The AMR Rate Control Switch parameter specifies whether the AMR speech rate is adjusted. The setting of this parameter is described as follows: l When this parameter is set to Algorithm I, it indicates that the BSC adjusts the AMR speech rate based on the C/I ratio. l When this parameter is set to Algorithm II, it indicates that the BSC adjusts the AMR speech rate based on the Bit Error Rate (BER). l When this parameter is set to None, it indicates that the AMR rate adjustment is disabled. 3. If the AMR Rate Control Switch parameter is set to Algorithm I or Algorithm II, the AMR codec mode adapts to the change of the radio environment during the call according to the configured threshold and hysteresis. The following description takes the adjustment of the AMR FR codec mode as an example. l The currently used codec mode is CODEC_MODE_1. If the filter value is greater than AMR UL Coding Rate adj.th1[F] plus AMR UL Coding Rate adj.hyst1[F], the peer end needs to adjust the codec mode to CODEC_MODE_2. In other cases, the codec mode remains unchanged. l The currently used codec mode is CODEC_MODE_2. If the filter value is greater than AMR UL Coding Rate adj.th2[F] plus AMR UL Coding Rate adj.hyst2[F], the peer end needs to adjust the codec mode to CODEC_MODE_3. If the filter value is smaller than AMR UL Coding Rate adj.th1[F], the peer end needs to adjust the codec mode to CODEC_MODE_1. In other cases, the codec mode remains unchanged. l The currently used codec mode is CODEC_MODE_3. If the filter value is greater than AMR UL Coding Rate adj.th3[F] plus AMR UL Coding Rate adj.hyst3[F], the peer end needs to adjust the codec mode to CODEC_MODE_4. If the filter value is smaller than AMR UL Coding Rate adj.th2[F], the peer end needs to adjust the codec mode to CODEC_MODE_2. In other cases, the codec mode remains unchanged. l The currently used codec mode is CODEC_MODE_4. If the filter value is smaller than AMR UL Coding Rate adj.th3[F], the peer end needs to adjust the codec mode to CODEC_MODE_3. In other cases, the codec mode remains unchanged. 4. If the codec mode is to be adjusted, the BTS sends a UL CMC to the MS. The procedure for adjusting the UL codec mode by the BTS is complete.
2.9.3.3 Rate Adjustment Threshold Adaptation

Generally, network planning engineers set the ACS, threshold parameters, and hysteresis parameters for a cell according to the evaluation of the radio channel quality. When the radio channel quality keeps changing or the quality evaluation is inaccurate, the parameter settings do not meet the requirements of the speech services in the cell. In this case, the appropriate AMR codec mode cannot be selected for a call, and the quality of the speech services is affected.
The AMR rate adjustment threshold adaptation function enables the BSC to monitor the speech quality in real time and to adaptively modify the threshold parameters. Thus, an appropriate AMR codec mode can always be selected for the call. The principle for uplink adaptive adjustment of the threshold is the same as that for downlink adaptive adjustment of the threshold. When the BSC sends the BTS a channel activation or a speech codec mode modification message, the channel activation or the speech codec mode modification message carries Uplink Long-term FER Upper Threshold, Uplink Long-term FER Lower Threshold, Uplink Long-term FER Target, and Uplink Threshold Adjust Factor, if AMR Uplink Adaptive Threshold Allowed in the cell is set to Yes and the call is an AMR call. On receiving the message, the BTS adaptively adjusts the AMR codec mode for the call. When the BSC sends the BTS a channel activation or a speech codec mode modification message, the channel activation or the speech codec mode modification message carries Downlink Long-term FER Upper Threshold, Downlink Long-term FER Lower Threshold, Downlink Long-term FER Target, and Downlink Threshold Adjust Factor, if AMR Downlink Adaptive Threshold Allowed in the cell is set to Yes and the call is an AMR call. On receiving the message, the BTS adaptively adjusts the AMR codec mode for the call.
2.9.3.4 AMR Power Control

The procedure of power control for AMR calls is similar to that for non-AMR calls. In Huawei II power control algorithm and Huawei III power control algorithm, parameters related to AMR power control are configured separately from those related to non-AMR power control. The AMR calls and non-AMR calls can adopt different power control strategies. For details, see 2.64 Power Control.
2.9.3.5 Handover
The Intra-cell AMR TCHF-TCHH handover algorithm is introduced in both handover algorithm I and handover algorithm II. For details, see the Handover feature. Through the dynamic conversion between AMR HR channels and AMR FR channels, the speech quality and the system capacity are optimally balanced.
NOTE
Before implementing the intra-cell AMR TCHF-TCHH handover algorithm, you must enable the half-rate service and AMR HR.
2.9.3.6 Impact on KPI

The use of AMR has an impact on the KPIs related to the call drop rate, congestion rate, traffic volume, and handover.
Impact on Call Drop Rate

AMR improves the robustness of the AMR speech frame but not the robustness of the SACCH frame (robustness indicates the anti-interference capability of the AMR). Theoretically therefore, AMR does not affect the TCH call drop rate. In practice, however, when AMR is enabled, the TCH call drop rate increases because of the following causes:
As for EFR/FR/HR, the difference between the robustness of the SACCH frame and that of the speech frame is not great. A user in a weak coverage area may hang up the phone because of the poor speech quality. Such a situation is not counted as a call drop. When AMR is enabled, the robustness of the AMR FR speech frame is higher than that of the SACCH frame. Thus, the speech frame in a weak coverage area can be appropriately decoded, and the user will not hang up the phone. The SACCH frame, however, cannot be appropriately decoded. Thus, Radio Link Timeout expires, and a call drop occurs. In this way, the TCH call drop rate increases.
AMR introduces parameters such as AFR Radio Link Timeout, AHR Radio Link Timeout, AFR SACCH Multi-Frames, and AHR SACCH Multi-Frames. You can adjust the values of these parameters to improve the robustness of the SACCH frame, enhance the network coverage performance of AMR, and decrease the call drop rate.
Impact on Congestion Rate

AMR increases the system capacity by decreasing the TCH congestion rate. AMR improves the capacity of the TCHs but not the capacity of the SDCCHs. Thus, AMR cannot decrease the SDCCH congestion rate.
Impact on Traffic Volume

AMR has a strong anti-interference capability. Users in some weak coverage areas where calls fail to be made can make calls after AMR is enabled. The possibility of hangup is reduced. Therefore, the traffic volume is increased.
Impact on Handover
AMR optimizes the speech codec but not the signaling codec. Theoretically therefore, AMR does not significantly affect handover. AMR can, however, expand the radio coverage of the network; therefore, users in weak coverage areas can make calls. As a result, the receive quality carried in the measurement report is poor, and the bad quality handover is triggered. In other words, the number of bad quality handovers may increase after AMR is enabled.

AMR FR has a strong anti-interference capability but cannot increase the system capacity. AMR HR can increase the system capacity but has a poor anti-interference capability compared with AMR FR. To optimally balance the speech quality and the system capacity, Huawei adopts the channel-quality-based channel adaptive adjustment algorithm. The algorithm works in accordance with the following strategies: l l When the system capacity is restricted, an additional half-rate channel can be generated by converting an AMR FR call with good radio signal quality into an AMR HR call. When the radio signal of AMR HR calls is of poor quality, the anti-interference capability of channels can be enhanced by converting AMR HR calls into AMR FR calls.
The application strategies and scenarios of AMR are concluded as follows: l When the system capacity is not restricted and the number of MSs supporting AMR reaches a certain proportion, AMR should be enabled on certain TRXs to improve the speech quality through AMR FR.
Issue 08 (2011-09-30)
l l
When the system capacity is restricted, AMR FR calls should be converted into AMR HR calls on the premise that the network quality is ensured to increase the system capacity. The tight frequency reuse pattern can be applied to the network, considering the strong antiinterference capability of AMR FR.
2.9.5 Parameters
This chapter describes the parameters related to AMR. For the meaning of each parameter, see Table 2-13. For the default value, value ranges, and MML commands of each parameter, see Table 2-14. Table 2-13 Parameter description (1) Parameter Service Type Description Service bearer mode of the BTS Initial coding mode used for full rate AMR calls. The four values 0, 1, 2, and 3 of this parameter respectively represent the lowest, low, high, and highest coding rates in the ACS. This parameter does not take effect in A over IP mode. In A over IP mode, the TC is integrated into the UMG, and the BSC obtains the initial coding mode according to protocols. That is, the BSC does not obtain the initial coding mode according to parameter configuration. Initial coding mode used for half rate AMR calls. The four values 0, 1, 2, and 3 of this parameter respectively represent the lowest, low, high, and highest coding rates in the ACS. This parameter does not take effect in A over IP mode. In A over IP mode, the TC is integrated into the UMG, and the BSC obtains the initial coding mode according to protocols. That is, the BSC does not obtain the initial coding mode according to parameter configuration. Active coding set (ACS)[F], indicates a set of full-rate coding rates currently available for calls. The AMR is a set of multiple speech coding and decoding rates. Modifying the default coding rates will affect speech quality when TrFO or TFO is in use. Active coding set (ACS)[H], indicates set of half-rate coding rates currently available for calls. The AMR is a set of multiple speech coding and decoding rates. Modifying the default coding rates will affect speech quality when TrFO or TFO is in use. Switch for controlling the AMR rate. Value 0 indicates that C/I is used to control the AMR rate. Value 1 indicates that BER is used to control the AMR rate.
AMR Starting Mode[F]
AMR Starting Mode[H]
AMR ACS[F]
AMR ACS[H]
AMR Rate Control Switch
Issue 08 (2011-09-30)
188
Parameter
Description Based on the RQI in the call measurement report, the BTS and MS automatically adjust the current speech coding rate according to the related algorithm. The coding rate adjustment threshold is the threshold of RQI. The RQI indicates the carrier-to-interference ratio (CIR) of the call. If RQI equals 1, the CIR is 0.5 dB; if RQI equals 2, the CIR is 1 dB; and so forth. Since there are multiple coding rates in the ACS, there is an adjustment threshold and an adjustment hysteresis between the neighboring coding rates. Based on the RQI in the call measurement report, the BTS and MS automatically adjust the current speech coding rate according to the related algorithm. The coding rate adjustment threshold is the threshold of RQI. The RQI indicates the carrier-to-interference ratio (CIR) of the call. If RQI equals 1, the CIR is 0.5 dB; if RQI equals 2, the CIR is 1 dB; and so forth. Since there are multiple coding rates in the ACS, there is an adjustment threshold and an adjustment hysteresis between the neighboring coding rates. Based on the RQI in the call measurement report, the BTS and MS automatically adjust the current speech coding rate according to the related algorithm. The coding rate adjustment threshold is the threshold of RQI. The RQI indicates the carrier-to-interference ratio (CIR) of the call. If RQI equals 1, the CIR is 0.5 dB; if RQI equals 2, the CIR is 1 dB; and so forth. Since there are multiple coding rates in the ACS, there is an adjustment threshold and an adjustment hysteresis between the neighboring coding rates. Based on the RQI in the call measurement report, the BTS and MS automatically adjust the current speech coding rate according to the related algorithm. The coding rate adjustment threshold is the threshold of RQI. The RQI indicates the carrier-to-interference ratio (CIR) of the call. If RQI equals 1, the CIR is 0.5 dB; if RQI equals 2, the CIR is 1 dB; and so forth. Since there are multiple coding rates in the ACS, there is an adjustment threshold and an adjustment hysteresis between the neighboring coding rates.
AMR UL Coding Rate adj.th1 [F]
AMR UL Coding Rate adj.hyst1[F]
Issue 08 (2011-09-30)
189
Parameter
Description Based on the RQI in the call measurement report, the BTS and MS automatically adjust the current speech coding rate according to the related algorithm. The coding rate adjustment threshold is the threshold of RQI. The RQI indicates the carrier-to-interference ratio (CIR) of the call. If RQI equals 1, the CIR is 0.5 dB; if RQI equals 2, the CIR is 1 dB; and so forth. Since there are multiple coding rates in the ACS, there is an adjustment threshold and an adjustment hysteresis between the neighboring coding rates. Based on the RQI in the call measurement report, the BTS and MS automatically adjust the current speech coding rate according to the related algorithm. The coding rate adjustment threshold is the threshold of RQI. The RQI indicates the carrier-to-interference ratio (CIR) of the call. If RQI equals 1, the CIR is 0.5 dB; if RQI equals 2, the CIR is 1 dB; and so forth. Since there are multiple coding rates in the ACS, there is an adjustment threshold and an adjustment hysteresis between the neighboring coding rates. Whether to enable the adaptive adjustment function of AMR uplink threshold. After this function is enabled, the BTS estimates the long-term voice quality (indicated by the long-term FER(frame erase rate)) and compares the estimated result with the specified target voice quality. If the estimated result does not conform to the target voice quality, it indicates that the current AMR handover threshold may not be the best for the current radio conditions. In this case, the BSC uses the relevant algorithm to adjust the adaptive threshold according to the relation between the estimated voice quality and the target voice quality. Whether to enable the adaptive adjustment function of AMR downlink threshold. After this function is enabled, the BTS estimates the long-term voice quality (indicated by the long-term FER(frame erase ratio)) and compares the estimated result with the specified target voice quality. If the estimated result does not conform to the target voice quality, it indicates that the current AMR handover threshold may not be the best for the current radio conditions. In this case, the BSC6900 adjust threshold adaptively according to the relation between the estimated voice quality and the target voice quality. Upper voice quality threshold associated with the automatic adjustment of the AMR handover uplink threshold
AMR Uplink Adaptive Threshold Allowed
AMR Downlink Adaptive Threshold Allowed Uplink Long-term FER Upper Threshold
Issue 08 (2011-09-30)
190
Parameter
Description Lower voice quality threshold associated with the automatic adjustment of the AMR handover uplink threshold;The value of this parameter must be smaller than or equal to the value of Uplink Long-term FER Target. Target voice quality value associated with the automatic adjustment of the uplink threshold of AMR handover Target value of the voice quality automatically adjusted through the downlink threshold of AMR handover Factor of uplink threshold adjustment. It indicates the linear relation between the threshold adjustment value and the logarithmic FER. Whether the downlink discontinuous transmission (DTX) function is enabled for full rate (FR) calls. This function is also restricted by the DTX switch in the MSC. If the MSC allows the downlink DTX for calls and the value of this parameter(FRDLDTX) is YES, the downlink DTX is enabled for FR calls of cells. Whether the uplink DTX function is enabled for FR calls. For details, see GSM Rec. 05.08. Uplink DTX is not restricted by the MSC. Shall_Use:An MS will use uplink DTX if it supports uplink DTX. May_Use:An MS will determine whether to use uplink DTX if both the cell and MS support uplink DTX. Shall_NOT_Use:DTX will not be used. Whether the downlink DTX function is enabled for half rate (HR) calls. This function is also restricted by the DTX switch in the MSC. If the MSC allows the downlink DTX for calls and the value of this parameter(HRDLDTX) is YES, the downlink DTX is enabled for HR calls of cells. Whether the uplink DTX function is enabled for HR calls. For details, see GSM Rec. 05.08. Uplink DTX is not restricted by the MSC. Shall_Use:An MS will use uplink DTX if it supports uplink DTX. May_Use:An MS will determine whether to use uplink DTX if both the cell and MS support uplink DTX. Shall_NOT_Use:DTX will not be used. Whether to enable the Tandem Free Operation (TFO) function on the BTS through a CHANNEL ACTIVATION or MODE MODIFY message. This parameter specifies whether to enable the Tandem Free Operation (TFO) function. If the voice quality of an ongoing MS-to-MS call is bad, the TFO function can be enabled to improve end-toend voice quality. The TFO function cannot be used to improve the voice quality of an MS-to-PSTN call.
Uplink Long-term FER Lower Threshold Uplink Long-term FER Target Downlink Long-term FER Target
Uplink Threshold Adjust Factor
FR Use Downlink DTX
FR Uplink DTX
HR Use Downlink DTX
HR Uplink DTX
TFO Switch
Issue 08 (2011-09-30)
191
Parameter
Description Time for disconnecting a call when the MS fails to decode the SACCH. Once a dedicated channel is assigned to the MS, the counter S is enabled and the initial value is set to this parameter value. Each time an SACCH message is not decoded, the counter S decreases by 1. Each time an SACCH message is correctly decoded, the counter S increases by 2. When the counter S is equal to 0, the downlink radio link is considered as failed. Therefore, when the voice or data quality is degraded to an unacceptable situation and it cannot be improved through power control or channel handover, the connection is to be re-established or released. Counter for radio link failures during an AMR full rate call. See the description of "Radio Link Timeout" in "SET GCELLCCBASIC". Counter for radio link failures during an AMR half rate call. See the description of "Radio Link Timeout" in "SET GCELLCCBASIC". Number of SACCH multiframes during an AMR full rate call. See the description of "SACCH Multi-Frames" in "SET GCELLCCBASIC". Number of SACCH multiframes during an AMR half rate call. See the description of "SACCH Multi-Frames" in "SET GCELLCCBASIC". Factor of downlink threshold adjustment. It indicates the linear relation between the threshold adjustment value and the logarithmic FER. Upper voice quality threshold associated with the automatic adjustment of the AMR handover downlink threshold. Lower voice quality threshold associated with the automatic adjustment of the AMR downlink handover threshold. The value of this parameter must be smaller than or equal to the value of Downlink Long-term FER Target.
Radio Link Timeout
AFR Radio Link Timeout
AHR Radio Link Timeout
AFR SACCH Multi-Frames
AHR SACCH Multi-Frames Downlink Threshold Adjust Factor Downlink Long-term FER Upper Threshold
Downlink Long-term FER Lower Threshold
Issue 08 (2011-09-30)
192
Table 2-14 Parameter description (2) Paramete r Default Value GUI Value Range TDM, HDLC, HDLC_H ubBTS, IP Actual Value Range TDM, HDLC, HubBTS, IP Unit MML Comman d Impact
Service Type AMR Starting Mode[F] AMR Starting Mode[H]
TDM
None
ADD BTS (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional)
BTS
0~3
0~3
None
Cell
0 4_75KBIT / S-1&5_15 KBIT/ S-0&5_90 KBIT/ S-1&6_70 KBIT/ S-0&7_40 KBIT/ S-1&7_95 KBIT/ S-0&10_2 KBIT/ S-0&12_2 KBIT/S-1 4_75KBIT / S-1&5_15 KBIT/ S-0&5_90 KBIT/ S-1&6_70 KBIT/ S-0&7_40 KBIT/ S-1&7_95 KBIT/S-0
0~3 4_75KBIT /S~0 5_15KBIT /S~1 5_90KBIT /S~2 6_70KBIT /S~3 7_40KBIT /S~4 7_95KBIT /S~5 10_2KBIT /S~6 12_2KBIT /S 4_75KBIT /S~0 5_15KBIT /S~1 5_90KBIT /S~2 6_70KBIT /S~3 7_40KBIT /S~4 7_95KBIT /S
0~3 4_75KBIT /S, 5_15KBIT /S, 5_90KBIT /S, 6_70KBIT /S, 7_40KBIT /S, 7_95KBIT /S, 10_2KBIT /S, 12_2KBIT /S 4_75KBIT /S, 5_15KBIT /S, 5_90KBIT /S, 6_70KBIT /S, 7_40KBIT /S, 7_95KBIT /S
None
Cell
AMR ACS [F]
None
SET GCELLC CAMR (Optional)
Cell
AMR ACS [H]
None
SET GCELLC CAMR (Optional)
Cell
Issue 08 (2011-09-30)
193
Paramete r
Default Value
GUI Value Range ALG1 (Algorith m I), ALG2 (Algorith m II), NONE (None)
Actual Value Range
Unit
MML Comman d
Impact
AMR Rate Control Switch AMR UL Coding Rate adj.th1[F] AMR UL Coding Rate adj.hyst1 [F] AMR UL Coding Rate adj.th2[F] AMR UL Coding Rate adj.hyst2 [F] AMR UL Coding Rate adj.th3[F] AMR UL Coding Rate adj.hyst3 [F] AMR Uplink Adaptive Threshold Allowed
ALG1
ALG1, ALG2, NONE
None
SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional)
Cell
15
0~63
0~63
dB
Cell
0~15
0~15
None
Cell
19
0~63
0~63
dB
Cell
0~15
0~15
None
Cell
28
0~63
0~63
dB
Cell
0~15
0~15
None
Cell
NO
NO(No), YES(Yes)
NO, YES
None
Cell
Issue 08 (2011-09-30)
194
Paramete r AMR Downlink Adaptive Threshold Allowed Uplink Long-term FER Upper Threshold Uplink Long-term FER Lower Threshold Uplink Long-term FER Target Downlink Long-term FER Target Uplink Threshold Adjust Factor
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional) SET GCELLB ASICPAR A (Optional)
Impact
NO
NO(No), YES(Yes)
NO, YES
None
Cell
60
2~255
2~255
None
Cell
2~255
2~255
None
Cell
2~255
2~255
None
Cell
2~255
2~255
None
Cell
2~255
2~255
None
Cell
FR Use Downlink DTX
YES
NO(No), YES(Yes) May_Use (May Use), Shall_Use (Shall Use), Shall_NO T_Use (Shall not Use)
NO, YES
None
Cell
FR Uplink DTX
Shall_Use
May_Use, Shall_Use, Shall_NO T_Use
None
SET GCELLB ASICPAR A (Optional)
Cell
Issue 08 (2011-09-30)
195
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLB ASICPAR A (Optional)
Impact
HR Use Downlink DTX
YES
NO(No), YES(Yes) May_Use (May Use), Shall_Use (Shall Use), Shall_NO T_Use (Shall not Use) DISABLE (Disable), ENABLE (Enable) 4_Times, 8_Times, 12_Times, 16_Times, 20_Times, 24_Times, 28_Times, 32_Times, 36_Times, 40_Times, 44_Times, 48_Times, 52_Times, 56_Times, 60_Times, 64_Times
NO, YES
None
Cell
HR Uplink DTX
Shall_Use
May_Use, Shall_Use, Shall_NO T_Use
None
SET GCELLB ASICPAR A (Optional) SET GCELLB ASICPAR A (Optional)
Cell
TFO Switch
DISABLE
DISABLE , ENABLE
None
Cell
Radio Link Timeout
52_Times
1920~307 20, step: 480
ms
SET GCELLC CBASIC (Optional)
Cell
Issue 08 (2011-09-30)
196
Paramete r
Default Value
GUI Value Range 4_Times, 8_Times, 12_Times, 16_Times, 20_Times, 24_Times, 28_Times, 32_Times, 36_Times, 40_Times, 44_Times, 48_Times, 52_Times, 56_Times, 60_Times, 64_Times 4_Times, 8_Times, 12_Times, 16_Times, 20_Times, 24_Times, 28_Times, 32_Times, 36_Times, 40_Times, 44_Times, 48_Times, 52_Times, 56_Times, 60_Times, 64_Times
Actual Value Range
Unit
MML Comman d
Impact
AFR Radio Link Timeout
64_Times
1920~307 20, step: 480
ms
SET GCELLC CBASIC (Optional)
Cell
AHR Radio Link Timeout AFR SACCH MultiFrames AHR SACCH MultiFrames Downlink Threshold Adjust Factor
52_Times
1920~307 20, step: 480
ms
SET GCELLC CBASIC (Optional) SET GCELLC CBASIC (Optional) SET GCELLC CBASIC (Optional) SET GCELLC CAMR (Optional)
Cell
48
0~63
0~30240, step:480
ms
Cell
32
0~63
0~30240, step:480
ms
Cell
2~255
2~255
None
Cell
Issue 08 (2011-09-30)
197
Paramete r Downlink Long-term FER Upper Threshold Downlink Long-term FER Lower Threshold
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLC CAMR (Optional) SET GCELLC CAMR (Optional)
Impact
60
2~255
2~255
None
Cell
2~255
2~255
None
Cell
2.9.6 Counters
2.9.7 Glossary

l l l l l l l l l l GSM 05.03: "Digital cellular telecommunications system (Phase 2+); Channel coding" GSM 05.09: "Digital cellular telecommunications system (Phase 2+); Link Adaptation" GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification" GSM 06.90: "Digital cellular telecommunications system (Phase 2+); Adaptive Multi-Rate (AMR) speech transcoding " GSM 06.91: "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frames for Adaptive Multi Rate (AMR) speech traffic channels " GSM 06.92: "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Adaptive Multi-Rate (AMR) speech traffic channels " GSM 06.93: "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Adaptive Multi Rate (AMR) speech traffic channels " GSM 06.94: "Digital cellular telecommunications system (Phase 2+); Voice Activity Detection (VAD) for Adaptive Multi-Rate speech traffic channels " GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification " GSM 08.58: "Digital cellular telecommunications system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 3 specification "
Issue 08 (2011-09-30)
l l l l l l l l
GSM 08.60: "Digital cellular telecommunications system (Phase 2+); In-band control of remote transcoders and rate adaptors for full rate traffic channels " GSM 08.61: "Digital cellular telecommunications system (Phase 2+); In band control of remote transcoders and rate adaptors for half rate traffic channels " BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.10 Antenna Frequency Hopping

2.10.1 Introduction
2.10.1.1 Scope
This document describes the antenna frequency hopping feature. It provides antenna hopping selection algorithm, and relation between antenna frequency hopping and frequency hopping of this feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the antenna frequency hopping feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 remains unchanged.
2.10.2 Overview
During a CS call or a PS data session, a single burst transmitted over the Um interface may be lost due to interference or multipath fading. Thus proper coding and interleaving schemes are adopted in GSM to minimize the impact of interference or multipath fading. If a speech frame is divided into multiple bursts for transmission, the loss of a single burst has minimal impact on the speech quality. Antenna frequency hopping can provide transmit diversity. Antenna frequency hopping can provide transmit diversity. After the antenna frequency hopping is introduced, all the bursts of a speech frame are transmitted on different paths. In this manner, the bursts are unlikely to be lost and the speech quality is ensured. When traffic channels do not participate in frequency hopping or only a small number of frequencies participate in frequency hopping, antenna frequency hopping brings substantial diversity gains without increasing the number of frequencies in a base station. In the case of slow-moving MSs with low coding rates, antenna frequency hopping brings substantial diversity gains. In the case of fast-moving MSs with low coding rates (for example, the MSs are moving along high-speed railways in the coverage area), antenna frequency hopping brings few diversity gains. In the case of high coding rates or no coding, antenna frequency hopping brings negative diversity gains. Antenna frequency hopping provides transmit diversity on the downlink. As shown in Figure 2-17, user data is coded and interleaved to obtain the transmit signal S. S is divided into S1 and
S2, which are then transmitted through different antennas. In this manner, the probability that all the data of a user is lost is reduced. In addition, the anti-attenuation capability of the receiver and the speech quality of the slow-moving MS are improved. The downlink coverage area is also enlarged. Downlink transmit diversity is used to overcome fast fading. Therefore, antenna frequency hopping is mainly applied in propagation scenarios where multipath fading exists, for example, in suburban areas where wide coverage is required. Figure 2-17 Schematic drawing of antenna frequency hopping
With antenna frequency hopping, the system selects some TRXs in the serving cell according to the antenna hopping selection algorithm to transmit the downlink data of a user. Thus, the data of the user is transmitted by different antennas connected to these TRXs. All the TRXs used to transmit the data of the same user form a TRX group. Each TRX in the TRX group has the same transmit power, for example, when all the TRXs serve the underlaid or overlaid subcell of a concentric cell. The antennas that are connected to the TRXs in one TRX group form an antenna hopping set. Each antenna hopping set should have at least two antennas.

2.10.3.1 Antenna Hopping Selection Algorithm
The Cell Antenna Hopping parameter must be set to Yes before antenna frequency hopping is enabled. In addition, the TRX group and TRXHSN must be specified. If radio frequency hopping or no frequency hopping is enabled in the serving cell, the TRX group can contain any TRX in the cell. If baseband frequency hopping is enabled in the serving cell, the TRXs in the TRX group should be the same as those participating in baseband frequency hopping. After the TRX group is configured, each TRX in the TRX group is allocated a TRXIO. The antenna hopping selection algorithm is expressed as follows: TRXI = (S + TRXIO) mod N Here, TRXI indicates the index of a TRX in a TRX group. Its value ranges from 0 to N-1. TRXIO indicates the initial offset of a TRX in a TRX group. Its value ranges from 0 to N-1. N indicates the number of TRXs in a TRX group. FN indicates the number of a TDMA frame and it is broadcast on the SCH. The MS synchronizes with the base station by adjusting the FN (ranging from 0 to 2,715,647). TRXHSN indicates the hopping sequence number (ranging from 0 to 63) of a TRX group.
l l
If TRXHSN is equal to 0, then cyclic frequency hopping is applied and S is equal to FN. If TRXHSN is not equal to 0, S is calculated according to the frequency hopping algorithm. For details of the frequency hopping algorithm, see 3GPP TS 45.002 "Hopping sequence generation."
Based on the obtained TRXI, the system searches the TRX group for a TRX for user data transmission.
2.10.3.2 Relation Between Antenna Frequency Hopping and Frequency Hopping

Antenna frequency hopping can be applied in the cells of the following types: non-frequency hopping, radio frequency hopping, and baseband frequency hopping. When traffic channels do not participate in frequency hopping or only a small number of frequencies participate in frequency hopping, antenna frequency hopping can bring substantial diversity gains. If baseband frequency hopping is enabled in a cell, user data is transmitted by different TRXs except the BCCH TRX. This brings about the same effect as antenna frequency hopping. In baseband frequency hopping, timeslot 0 of the BCCH TRX does not participate in frequency hopping. In a GSM cell, timeslot 0 of the BCCH TRX, however, is used by an MS in idle mode to search for the network or by an MS in dedicated mode to measure the receive level of neighboring cells. If an MS is located in an area where it is difficult to receive the messages from the BCCH TRX or if the antenna connected to the BCCH TRX is damaged, then the MS cannot receive the broadcast control messages from the BCCH TRX properly. Similar to baseband frequency hopping, antenna frequency hopping enables the data of all the timeslots on the BCCH TRX to be transmitted on the antennas connected to all the TRXs in the cell in sequence. This increases the space diversity and optimizes the data reception of the MS from the BCCH TRX. Thus, the network performance is improved.
2.10.4 Parameters
The following describes the parameters related to antenna frequency hopping. For the meaning of each parameter, see Table 2-15. For the default value, value range, and related MML commands of each parameter, see Table 2-16. Table 2-15 Parameter description (1) Parameter Description Whether to enable the TRX to support antenna hopping In a GSM cell, the BCCH broadcasts the frequency, frame number, system information, and paging group. If an MS is in an unfavorable position or the antenna of the main TRX that carries the BCCH fails, the MS receives poor broadcast control signals or even cannot receive any broadcast control message from the BCCH. To avoid such a problem, the antenna hopping function is involved. With this function, the messages transmitted in the main TRX that carries the BCCH are also transmitted on the antennas of all the other TRXs in the cell in turn. This helps the MSs receive quality broadcast control data. This function can be configured only for dual-frequency BTSs.
Cell Antenna Hopping
Issue 08 (2011-09-30)
202
Table 2-16 Parameter description (2) Paramete r Default Value GUI Value Range NO_HPA NT(No), YES_HP ANT (Yes), NONE (None) Actual Value Range Unit MML Comman d Impact
Cell Antenna Hopping
NONE
NO_HPA NT, YES_HP ANT, NONE
None
SET GCELLH OPANT (Optional)
Cell
2.10.5 Counters
None.
2.10.6 Glossary

l l l l l l 3GPP TS 45.002 "Hopping sequence generation" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.11 AQM
2.11.1 Introduction
2.11.1.1 Scope
This document describes active queue management (AQM) algorithm description in the AQM feature.

It is assumed that users of this document are familiar with GPRS basics and have a working knowledge of GPRS telecommunication. This document is intended for: l l Personnel working on Huawei GPRS products or systems System operators who need a general understanding of this feature

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the AQM feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Version
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The template of the document is optimized. Parameter Change None. None.
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with 02 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 has no change.
2.11.2 Overview
Active queue management (AQM) is an algorithm used to maintain the buffer queue length within an appropriate range by discarding data packets in the buffer queue actively. It increases data throughput and reduces service delay at the price of buffer utilization. AQM applies to scenarios in which bandwidth is limited and congestion is likely to occur. AQM not only ensures high link utilization but also reduces the delay of services that require low transfer delay. It also enhances fair utilization of bandwidth among services and increases data throughput. Compared with the wired link bandwidth, the wireless link bandwidth is small. Therefore, the wireless link bandwidth is a bottleneck for end-to-end data transfer. AQM can relieve network congestion due to excessive TCP data streams. When network congestion occurs, AQM discards data packets actively according to the packet discarding policy. After detecting packet loss, the TCP receiver informs the TCP transmitter of the packet loss by using the retransmission acknowledgement mechanism. Then, the TCP transmitter decreases the size of the transmit window according to the congestion control mechanism, thus reducing the transmission rate and relieving network congestion. At present, most data services use the transmission control protocol (TCP) protocol. The TCP protocol, however, has its limitations. When multiple TCP connections are set up at the same time in the communications system, one TCP connection may occupy a high bandwidth, and thus the transfer delay is long for other connections. For example, a user clicks a button on an hyper text transfer protocol (HTTP) web page when file transfer protocol (FTP) downloading is ongoing. In such a case, a long time elapses before the corresponding web page is displayed because the link resource is occupied by the FTP service. If AQM is used, it discards packets of services with excessive traffic flow actively and ensures high link utilization. This decreases the data transmission rate and thus reduces the delay of services that require low transfer delay. This also enhances fair utilization of bandwidth among services. AQM is applicable to interactive services, background services, and best effort (BE)services (namely, services without QoS requirements). It is not applicable to conversational services or streaming services.

Parameters
Before AQM takes effect, you must configure related parameters. That is, you must set AQM Switch to Open to enable AQM. In addition, you must set the following parameters related to AQM according to a specific application scenario: l AQM Congestion Threshold This parameter specifies the lower threshold at which the buffer queue is congested. If the buffer queue length exceeds this threshold, packets are discarded actively. l AQM Maximum Threshold This parameter specifies the upper threshold at which the buffer queue is congested. If the buffer queue length exceeds this threshold, a packet is discarded each time a packet arrives at the queue. l AQM Target Threshold This parameter specifies the target threshold at which the buffer queue is congested. This parameter is used to adjust the interval at which packets are discarded. l
Issue 08 (2011-09-30)
Aqm Ninit
This parameter specifies the initial value of the interval (indicated by N) at which a packet in the buffer queue is discarded. The value of N indicates the frequency at which packets are discarded. If the value of N is large, the frequency of discarding packets is low and thus a fewer number of packets are discarded over a certain period of time. l AQM Packet Discard Interval Lower Threshold This parameter specifies the lower threshold of the interval (indicated by N) at which a packet in the buffer queue is discarded. l AQM Packet Discard Interval Upper Threshold This parameter specifies the upper threshold of the interval (indicated by N) at which a packet in the buffer queue is discarded. l Aqm M This parameter specifies the frequency (indicated by M) of updating the value of N, that is, how many packets are transmitted before the value of N is updated.
AQM Policy for Discarding Packets

AQM is implemented in the BSC. For interactive services, background services, or BE services, AQM manages the buffer queue of downlink LLC PDUs of each MS. The key to the AQM algorithm is the packet discarding policy, which varies according to the AQM algorithm. The packet discarding policy of Huawei AQM algorithm is as follows: l l If the length of the buffer queue is smaller than AQM Congestion Threshold, no packet is discarded. If the length of the buffer queue is greater than AQM Congestion Threshold and smaller than AQM Maximum Threshold, a packet is discarded each time N packets arrive at the queue. If the length of the buffer queue is greater than AQM Maximum Threshold, a packet is discarded each time a packet arrives at the queue. The two methods of discarding packets are tail drop and head drop. The AQM algorithm uses the head drop method.
Based on the relations among the length of the buffer queue, AQM Congestion Threshold, and AQM Target Threshold, the AQM algorithm adjusts the interval at which packets are discarded. The AQM algorithm changes the value of N based on the value of M. The algorithm of adjusting the value of N dynamically is as follows: l If the length of the buffer queue is greater than AQM Target Threshold and smaller than AQM Maximum Threshold, the value of N is decreased by one each time M packets arrive at the queue. Thus, the number of packets that are discarded over a certain period of time increases. When the value of N reaches AQM Packet Discard Interval Lower Threshold, it no longer decreases. If the length of the buffer queue is greater than AQM Congestion Threshold and smaller than AQM Target Threshold, the value of N is increased by one each time M packets arrive at the queue. Thus, the number of packets that are discarded over a certain period of time decreases. When the value of N reaches AQM Packet Discard Interval Upper Threshold, it no longer increases.
Technologies Related to AQM

l Methods of discarding packets AQM supports two methods: head drop and tail drop. In the head drop method, packets at the head of the buffer are discarded when necessary. In the tail drop method, new packets
are discarded when necessary. The response speed in the head drop method is faster than that in the tail drop method. In addition, in the head drop method, packets are not continuously discarded. Thus, Huawei AQM algorithm uses the head drop method. l Service types supported by AQM AQM is applicable to interactive services, background services, and BE services. It is not applicable to conversational services or streaming services. l Upper-layer protocols supported by AQM The logical link control (LLC) layer provides services for the upper-layer sub-network dependent convergence (SNDC), GPRS mobility management (GMM), short message service (SMS), and tunnelling of messages (TOM) protocols. AQM manages only the LLC PDU queues providing services for the SNDC protocol.

AQM is associated with flow control on the Gb interface. AQM and flow control on the Gb interface can coexist but have an impact on each other. The impact between these two features depends on the configuration policy of the operator. If AQM-related thresholds are low, flow control on the Gb interface may be unable to take effect to a certain extent. If the operator considers that flow control on the Gb interface has a higher priority than AQM, AQM-related thresholds can be set to higher values. In this way, AQM takes effect only when severe network congestion occurs.
2.11.5 Parameters
The following describes the parameters related to AQM. For the meaning of each parameter, see Table 2-17. For the default value, value range, and related MML commands of each parameter, see Table 2-18. Table 2-17 Parameter description (1) Parameter AQM Switch AQM switch Congestion threshold of the TBF buffer queue. If the congestion level in the TBF buffer queue exceeds this threshold, whether the packets are discarded actively is determined according to the packet discarding policy. Upper length threshold of the TBF buffer queue. If the length of the TBF buffer queue exceeds this threshold, whether the packets are discarded is determined according to the packet discarding policy. Target threshold of the TBF buffer queue. Lower threshold of the interval for discarding the packets in the TBF buffer queue, that is, the minimum value of N (packet drop interval). Description
AQM Congestion Threshold AQM Maximum Threshold AQM Target Threshold AQM Packet Discard Interval Lower Threshold
Issue 08 (2011-09-30)
207
Parameter AQM Packet Discard Interval Upper Threshold
Description Upper threshold of the interval for discarding the packets in the TBF buffer queue, that is, the maximum value of N (packet drop interval).
Table 2-18 Parameter description (2) Paramete r Default Value GUI Value Range CLOSE (Close), OPEN (Open) Actual Value Range Unit MML Comman d SET BSCPSSO FTPARA (Optional) SET BSCPSSO FTPARA (Optional) SET BSCPSSO FTPARA (Optional) SET BSCPSSO FTPARA (Optional) Impact
AQM Switch AQM Congestio n Threshold AQM Maximum Threshold AQM Target Threshold AQM Packet Discard Interval Lower Threshold AQM Packet Discard Interval Upper Threshold
CLOSE
CLOSE, OPEN
None
BSC
256
1~65535
1~65535
bit
BSC
1024
1~65535
1~65535
bit
BSC
384
1~65535
1~65535
bit
BSC
10
1~65535
1~65535
packet
SET BSCPSSO FTPARA (Optional)
BSC
20
1~65535
1~65535
packet
BSC
2.11.6 Counters
None.
Issue 08 (2011-09-30)
208
2.11.7 Glossary

l l l l l l l 3GPP TS 44.060 "Radio Link Control/Medium Access Control (RLC/MAC) protocol" 3GPP TS 23.107 "Quality of Service (QoS) concept and architecture" 3GPP TS 48.018 "BSS GPRS Protocol (BSSGP)" BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.12 Assignment and Immediate Assignment

2.12.1 Introduction
2.12.1.1 Scope
This document describes the assignment procedure, immediate assignment procedure, and assignment classification.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Assignment and Immediate Assignment feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows: l 01 (2009-11-20)
01(2009-11-20)
2.12.2 Overview of Assignment and Immediate Assignment

When an MS initiates a call or needs to switch from a signaling channel to a TCH, the BSC needs to assign a channel to the MS. When the MS initiates a call, the BSC needs to assign an SDCCH or a TCH (the TCH is used for signaling) according to the specific call establishment cause. This procedure is called immediate assignment. After receiving a channel request from the MS, the MSC sends the BSC an Assignment Request message, instructing the BSC to assign a suitable channel to the MS. The channel to be assigned must meet the requirements of the MSC and MS, such as the channel type, speech version, and MS frequency capability. This procedure is called assignment. The immediate assignment and assignment procedures are very important for call establishment. Proper immediate assignment and assignment algorithms ensure optimal KPIs, thus improving the performance of radio networks. l l Through the immediate assignment procedure, a radio resource (RR) connection is established between the MS and the network. Through the assignment procedure, the MSC assigns a specific TCH to the MS so that a stable connection is established between the MS and the network.
The processing during the immediate assignment and assignment procedures varies based on different conditions. For details, see 2.23 Channel Management.

2.12.3.1 Immediate Assignment
?.1. Immediate Assignment Procedure
The immediate assignment procedure is initiated by an MS, with the purpose of establishing an RR connection between the MS and the network. The immediate assignment procedure is shown in Figure 2-18.
Issue 08 (2011-09-30)
210
Figure 2-18 Immediate assignment procedure
1.
The MS sends a Channel Request message to the BTS on the RACH. After initiating the immediate assignment procedure, the MS always listens to the BCCH and the corresponding CCCH. If the MS does not receive the Immediate Assignment Command message or Immediate Assignment Extended message, it resends the Channel Request message at a specified interval. When the number of times that the Channel Request message is resent exceeds MS MAX Retrans, the immediate assignment procedure fails.
2. 3.
The BTS sends a Channel Required message to the BSC. After the reception of the Channel Required message, the BSC assigns a signaling channel and sends the BTS a Channel Activation message, which carries information elements (IEs) such as Activation Type, Channel Description, Level, and Time Advance (TA). After the reception of the Channel Activation message, if the IEs carried in the message are correct, the BTS turns on the power amplifier on the specified channel to receive uplink messages. At the same time, the BTS sends the BSC a Channel Activation Acknowledge message carrying the absolute frame number, which is used by the BSC to determine Starting Time. The BSC sends the MS an Immediate Assignment Command message, instructing the MS to access the specified channel. The specified channel can be either an SDCCH or a TCH. Huawei BSC supports the immediate assignment of an SDCCH and a TCH at the cell level. The parameter TCH Immediate Assignment specifies whether the immediate assignment of a TCH is supported. The IMMEDIATE ASSIGNMENT COMMAND message can be resent only when Use Imm_Ass Retransmit Parameter is set to Yes and the delay time is within the Max Delay
4.
5.
Issue 08 (2011-09-30)
211
of Imm_Ass Retransmit(ms). When the number of times that the Immediate Assignment Command message is resent exceeds Max Transmit Times of Imm_Ass, the Immediate Assignment Command message is not resent. 6. 7. 8. The MS sends a Set Asynchronous Balanced Mode (SABM) frame on the main DCCH to access the network. The BTS answers with a Unnumbered Acknowledge (UA) frame on the main DCCH. The BTS sends an Establish Indication message to the BSC. The MS may send several Channel Request messages during one RR connection establishment attempt. In this case, the BSS activates multiple signaling channels, whereas the MS uses only one channel. The other channels cannot receive the Establish Indication message from the BTS for a long time. As a result, the BSC releases the channels at expiry of timer T3101.
?.2. Immediate Assignment Combination

Generally, the Immediate Assignment Command message from the BSC to the BTS contains the response to the channel request from only one MS. On the UM interface, however, the response to the Channel Request message are of three types: Immediate Assignment Command, Immediate Assignment Extended, and Immediate Assignment Reject. One Immediate Assignment Extended message contains the contents of the Immediate Assignment Command message (for acknowledgement) sent to two MSs over the Abis interface. One Immediate Assignment Reject message contains the contents of the Immediate Assignment Command message (for rejection) sent to four MSs. Therefore, to improve the message sending efficiency, the BTS encapsulates multiple Immediate Assignment Command messages received from the BSC into one Immediate Assignment Extended or Immediate Assignment Reject message before sending them to MSs. This procedure is called immediate assignment combination. The Wait Indication IE in the Immediate Assignment Reject message from the BSC to the MS carries timer T3122. Upon receiving the Immediate Assignment Reject message, the MS attempts to access the network at expiry of timer T3122.
2.12.3.2 Assignment
?.1. Assignment Procedure
In the assignment procedure, the network assigns a TCH to an MS. The assignment procedure is shown in Figure 2-19.
Issue 08 (2011-09-30)
212
Figure 2-19 Assignment procedure
1.
2.
3.
4.
5.
The MSC sends an Assignment Request message to the BSS based on the service request and then starts timer T10. Upon receiving the Assignment Request message from the MSC, the BSC checks the channel type. If a PS service is requested, the BSC determines whether the requested service is supported according to the setting of the parameter Data Service Allowed. The BSC sends the BTS a Channel Activation message to activate the corresponding terrestrial resources. The message carries IEs such as Activation Type, Channel Description, Level, and TA. Upon receipt of the Channel Activation message, if the IEs carried in the message are correct, the BTS turns on the power amplifier on the specified channel to receive uplink messages. At the same time, the BTS sends the BSC a Channel Activation Acknowledge message carrying the absolute frame number, which is used by the BSC to determine Starting Time. After receiving the Channel Activation Acknowledge message, the BSC sends the Assignment Command message on the signaling channel to the MS and starts timer T3107. The Assignment Command message carries IEs such as Channel Description, Power Command, and Channel Mode. After receiving the Assignment Command message, the MS starts to transmit and receive signaling over the TCH. The MS sends an SABM message to the network over the FACCH
Issue 08 (2011-09-30)
through frame stealing. The SABM frame is the first frame for establishing the asynchronous balanced mode. Compared with the immediate assignment procedure, the assignment procedure does not have layer 3 messages. 6. 7. 8. After receiving the SABM message, the BTS sends a UA frame to the MS over the FACCH. The layer 3 messages are not carried. At the same time, the BTS sends the BSC an ESTABLISH INDICATION message without the layer 3 messages. Then, the BSC responds with a UA frame for acknowledgement. After receiving the UA frame, the MS sends an Assignment Complete message to the network over the FACCH, indicating that the TCH is established successfully. When receiving the Assignment Complete message, the BSC stops timer T3107. In addition, the BSC fills the message with the corresponding information indicated by the parameter A Interface Tag and sends the message to the MSC. Upon receiving the Assignment Complete message, the MSC stops timer T10.
9.
?.2. Assignment Classification

In different scenarios, the assignment procedure may play different roles during the call. The assignment type has certain impacts on allocation and seizure of the network resources. According to the roles of the assignment procedure in the call, the assignment procedure is classified into mobile originating call establishment without OACSU (early assignment), mobile originating call establishment with OACSU (late assignment), mobile originating call establishment with very early assignment, mobile terminating call establishment without OACSU (early assignment), mobile terminating call establishment with OACSU (late assignment), and mobile terminating call establishment with very early assignment.
Mobile Originating Call Establishment Without OACSU (Early Assignment)

Mobile originating call establishment without OACSU (early assignment) refers to the procedure in which the calling MS is assigned a TCH before the call is established. After the immediate assignment is complete, the network sends the MS an Assignment Command message that requests the calling MS to occupy the TCH even if the Altering message is not received. In this case, the ringing tone is generated by the network. The mobile originating call establishment without OACSU (early assignment) procedure is shown in Figure 2-20.
Issue 08 (2011-09-30)
214
Figure 2-20 Mobile originating call establishment without OACSU (early assignment)
Mobile Originating Call Establishment with OACSU (Late Assignment)

In this mode, the network sends the MS an Assignment Command message that requests the calling MS to occupy a TCH only after the network receives the Alerting message from the called party. In this case, the ringing tone is generated by the MS because no TCH is available before the RR connection is established. The mobile originating call establishment with OACSU (late assignment) procedure is shown in Figure 2-21.
Issue 08 (2011-09-30)
215
Figure 2-21 Mobile originating call establishment with OACSU (late assignment)
Mobile Originating Call Establishment with Very Early Assignment

Mobile originating call establishment with very early assignment refers to the procedure in which a TCH instead of an SDCCH is assigned to the calling MS during the immediate assignment procedure. If TCH Immediate Assignment is set to Yes and no SDCCH is available in the serving cell of the calling MS, a TCH is allocated during the immediate assignment procedure. Mobile originating call establishment with very early assignment can speed up connection establishment. The network performs authentication, ciphering, other signaling exchanges, and follow-up call connection procedures on the TCH. In this case, the TCH is used for signaling. Upon receiving the Assignment Request message from the MSC, the BSC changes the TCH
used for signaling to a real TCH through the Mode Modify command. The mobile originating call establishment with very early assignment procedure is shown in Figure 2-22. Figure 2-22 Mobile originating call establishment with very early assignment
Mobile Terminating Call Establishment Without OACSU (Early Assignment)

Mobile terminating call establishment without OACSU (early assignment) refers to the procedure in which the called MS is assigned a TCH before the call is established. Mobile terminating call establishment is initiated by the network sending a Paging Request message. After the immediate assignment procedure is complete, the network sends an Assignment Command message to the called MS to require the MS to occupy a TCH before answering the phone. In this case, the ringing tone is generated by the network. The mobile terminating call establishment without OACSU (early assignment) procedure is shown in Figure 2-20.
Mobile Terminating Call Establishment with OACSU (Late Assignment)

In this mode, the network sends the MS an Assignment Command message that requests the called MS to occupy a TCH only after the network receives the Alerting message. In this case, the ringing tone is generated by the MS because no TCH is available before the RR connection is established. The mobile terminating call establishment with OACSU (late assignment) procedure is shown in Figure 2-21.
Mobile Terminating Call Establishment with Very Early Assignment

Mobile terminating call establishment with very early assignment refers to the procedure in which a TCH instead of an SDCCH is assigned to the called MS during the immediate assignment procedure. If TCH Immediate Assignment is set to Yes and no SDCCH is available in the serving cell of the called MS, a TCH is allocated during the immediate assignment procedure. Mobile terminating call establishment with very early assignment can speed up connection establishment. The network performs authentication, ciphering, other signaling exchanges, and follow-up call connection procedures on the TCH. Upon receiving the Assignment Request message from the network, the BSC changes the TCH used for signaling to a real TCH through the Mode Modify command. The mobile terminating call with very early assignment procedure is shown in Figure 2-22.
2.12.4 Parameters
This chapter describes the parameters related to assignment and immediate assignment. For the meaning of each parameter, see Table 2-19. For the default value, value ranges, and MML commands of each parameter, see Table 2-20. Table 2-19 Parameter description (1) Parameter Description Maximum number of Channel Request messages that can be sent by an MS in an immediate assignment procedure. After the MS initiates the immediate assignment procedure, it always listens to the messages on the BCCH and all the common control channels (CCCHs) in the CCCH group to which the MS belongs. If the MS does not receive Immediate Assignment or Immediate Assignment Extend messages, it retransmits Channel Request messages at a specified interval. If the downlink quality is poor, the MS may send SABM frames to the BTS multiple times. Whether to allow immediate TCH assignment. If this parameter is set to YES, the BSC can assign a TCH immediately when there is no available SDCCH for a channel request. If this parameter is set to NO, the BSC can assign only an SDCCH when processing a channel access request.
MS MAX Retrans
TCH Immediate Assignment
Issue 08 (2011-09-30)
218
Parameter Use IMM ASS Retransmit Parameter
Description Whether the BSC6900 sends immediate assignment retransmission parameters to the BTS Maximum time delay in resending an immediate assignment message. Within the period specified by this parameter, an immediate assignment message can be dispatched and retransmitted. Otherwise, the message is not dispatched or retransmitted. Maximum number of retransmissions of an immediate assignment message. When the value of this parameter is reached, the immediate assignment message is not retransmitted even if the value of "Max Delay of Imm_Ass Retransmit" is not exceeded. Timer for the BSC waiting for an Establish Indication message after sending an Immediate Assignment message. If T3101 expires before the BSC receives an Establish Indication message, the BSS releases the seized SDCCH. Timer carried by the Wait Indication information element when the BSC6900 sends an immediate assignment reject message to an MS. After the MS receives the immediate assignment reject message, the MS reattempts to access the network after the timer expires. Data service supported by the BSC6900. You can set this parameter according to actual requirements. After the BSC6900 delivers an assignment command, the T3107 timer starts. If the BSC6900 receives an assignment complete message within the scheduled time, the T3107 timer stops. If the timer expires, the BSC6900 sends an assignment failure message. Phase tag for GSM protocols supported by the A interface. The value of this parameter is chosen according to the A interface phase tag provided by the MSC.
Max Delay of IMM ASS Retransmit
Max Transmit Times of IMM ASS
T3101
T3122 Data Service Allowed
T3107
A Interface Tag
Table 2-20 Parameter description (2) Paramete r Default Value GUI Value Range 1_Times (1_Times) , 2_Times (2_Times) , 4_Times (4_Times) , 7_Times (7_Times) Actual Value Range Unit MML Command Impac t
MS MAX Retrans
4_Times
1_Times, 2_Times, 4_Times, 7_Times
None
SET GCELLCCBASIC (Optional)
Cell
Issue 08 (2011-09-30)
219
Paramete r TCH Immediate Assignme nt Use IMM ASS Retransmi t Parameter Max Delay of IMM ASS Retransmi t Max Transmit Times of IMM ASS T3101 T3122
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command
Impac t
NO
NO(No), YES(Yes)
NO, YES
None
SET GCELLBASICPA RA(Optional)
Cell
NO
NO(No), YES(Yes)
NO, YES
None
SET GCELLCCTMR (Optional)
Cell
0~254
0~254
ms
SET GCELLCCTMR (Optional) SET GCELLCCTMR (Optional) SET GCELLTMR (Optional) SET GCELLTMR (Optional)
Cell
2 3000 10 NT14_5K -0&NT12 K-1&NT6 K-1&T14 _4K-0&T 9_6K-1& T4_8K-1 &T2_4K1&T1_2K -0&T600_ BITS-0& T1200_75 -0 10000
1~5 500~6000 0 0~255 NT14_5K ~0 NT12K~1 NT6K~2 T14_4K~ 3 T9_6K~4 T4_8K~5 T2_4K~6 T1_2K~7 T600_BIT S~8 T1200_75 500~6000 0
1~5 500~6000 0 0~255
None ms s
Cell Cell Cell
Data Service Allowed T3107
NT14_5K, NT12K, NT6K, T14_4K, T9_6K, T4_8K, T2_4K, T1_2K, T600_BIT S, T1200_75 500~6000 0
None ms
SET GCELLOTHEXT (Optional) SET GCELLTMR (Optional)
Cell Cell
Issue 08 (2011-09-30)
220
Paramete r
Default Value
GUI Value Range GSM_PH ASE_1, GSM_PH ASE_2, GSM_PH ASE_2Plu s
Actual Value Range GSM_PH ASE_1, GSM_PH ASE_2, GSM_PH ASE_2Plu s
Unit
MML Command
Impac t
A Interface Tag
GSM_PH ASE_2
None
SET BSCBASIC (Optional)
BSC
2.12.5 Counters
2.12.6 Glossary

l l l l l l l 3GPP TS 48.008 Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification 3GPP TS 44.018 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.13 Ater Compression Transmission

2.13.1 Introduction
2.13.1.1 Scope
This document describes the network topologies on the Ater interface and the technologies in Ater compression transmission.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Ater compression transmission feature of a specific product version. l Editorial change Editorial change refers to changes in wording or the addition of information that was not described in the earlier version.
Document Issues
The document issues are as follows: l l 02(2009-09-30) 01(2009-06-30)
02(2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30), issue 02 (2009-09-30) incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
01(2009-06-30)
2.13.2 Overview
Ater Compression Transmission is a technology in which the TransCoder Subrack (TCS) of the BSC is located remotely and the IP over PPP over Ch-STM-1 transmission mode is used to carry signals when the Ater interface is in TDM transmission mode. Meanwhile, the techniques such as Ater MUX, PPP MUX, and IP header compression are used for data compression on the Ater interface to increase the transmission efficiency on the Ater interface. Ater Compression Transmission has the following features: l The remote location of the TCS can save the transmission bandwidth by 75%. After the Ater compression transmission function is enabled, an additional 30% transmission bandwidth on the Ater interface can be saved. IP over PPP enables the IP packets to be transmitted over the traditional TDM network. This protects the legacy investment of the operator who owns the TDM transmission resources. If the Abis interface uses the IP/HDLC transmission mode, the Ater compression transmission function does not require a coding/decoding board to convert the Transcoder & Adaptor Unit (TRAU) speech frames to packets. This saves the cost of board configuration.

The TRAU frames are used to carry speech signals in a TDM network; packet TRAU (pTRAU) frames are used to carry signals in IP/HDLC transmission mode. When the Ater compression transmission function is enabled, IP over PPP is used for data transmission. The Ater compression transmission is applied only to the speech signals over the Ater interface whereas the signaling and OM signals are still transmitted in TDM mode. To enable the Ater compression transmission function, set Ater Interface Transfer Mode to IP.
2.13.3.1 Network Topologies

?.1. Network Topology in Non-TC Pool Mode
In the network topology in non-TC pool mode, the speech services between the MPS(Main Processing Subrack)/EPS(Extended Processing Subrack) and the TCS of a BSC are carried in IP over PPP over Ch-STM-1 mode, as shown in Figure 2-23. Figure 2-23 Network topology in non-TC pool mode
Issue 08 (2011-09-30)
223
In Ater compression transmission mode, the MPS/EPS (regarded as the BSC) and TCS are adjacent nodes to each other. You need to configure the adjacent BSC of the TCS by setting Adjacent Node Type to BSC (Ater Interface on BSC) and BSC ID to 0. Meanwhile, configure the adjacent TCS of the BSC by setting Adjacent Node Type to TC(Ater Interface on TC).
?.2. Network Topology in TC Pool Mode

Figure 2-24 shows the network topology in TC pool mode when the user plane on the Ater interface is in IP over PPP mode. Figure 2-24 Network topology in TC pool mode (IP over PPP on the Ater user plane)
Figure 2-25 shows the network topology when both TDM and IP over PPP are used on the user plane of the Ater interface.
Issue 08 (2011-09-30)
224
Figure 2-25 Network topology in TC pool mode (TDM and IP over PPP on the Ater user plane)
In the network topology in TC pool mode, the MPS/EPS (regarded as the BSC) and TCS that support Ater compression transmission are adjacent nodes. You need to configure all the BSCs in the TC pool as the adjacent nodes of the TCS by setting Adjacent Node Type of each BSC to BSC(Ater Interface on BSC) and setting BSC ID of the primary BSC to 0 and BSC ID of every secondary BSC to a non-zero value. Meanwhile, configure the adjacent TCS of each BSC by setting Adjacent Node Type to TC(Ater Interface on TC).
2.13.3.2 Technologies in Ater Compression Transmission

?.1. Speech Frame Processing
The timeslots on the Ater interface consist of timeslots for the Ater signaling link, timeslots for the Ater OML, timeslots for the Ater speech service, and timeslots for the A SS7 signaling link. On the Ater interface, the IP over PPP mode is used to carry speech signals whereas the TDM mode is retained to carry signaling and OM signals. Figure 2-26 shows the timeslots on the Ater interface.
Issue 08 (2011-09-30)
225
Figure 2-26 Timeslots on the Ater interface
In Ater compression transmission mode, the speech signals can be processed in the following ways: l Direct transmission of pTRAU frames from the Abis interface board to the Ater interface board When the Abis interface uses the HDLC or IP transmission mode, the pTRAU frames are directly sent from the Abis interface board to the Ater interface board without further processing of the DPUc board. This reduces the delay of frame processing. Figure 2-27 shows the signal flow. Figure 2-27 Signal flow in the MPS/EPS (Abis over HDLC/IP)
l
Issue 08 (2011-09-30)
Frame format conversion between the Abis interface board and the Ater interface board
When the Abis interface uses the TDM transmission mode, the DPUc board in the MPS/ EPS processes the TRAU frames on the Abis interface and the pTRAU frames on the Ater interface. In addition, the DPUc board can eliminate the jitter and delay in packet arrival when IP/HDLC transmission is used on the Ater interface. Figure 2-28 shows the signal flow. Figure 2-28 Signal flow in the MPS/EPS (Abis over TDM)
Frame format conversion between the Ater interface board and the A interface board In Ater compression transmission mode, the Ater interface board sends the pTRAU frames to the DPUc board for converting the pTRAU frames to PCM frames used on the A interface. In addition, the DPUc board can eliminate the jitter and delay in packet arrival when IP/HDLC transmission is used on the Ater interface, support the downlink DTX function, and compress the silence frames. This improves the transmission efficiency on the Ater interface. Figure 2-29 shows the signal flow. Figure 2-29 Signal flow in the TCS
?.2. Packet Multiplexing

In Ater compression transmission mode, the POUc board works as the Ater interface board in the MPS/EPS/TCS and supports the following packet multiplexing functions: l Ater multiplexing The speech signals on the Ater interface are encapsulated in the same format of pTRAU frames used on the Abis interface. Multiple pTRAU frames are multiplexed into a UDP
packet through the Frame Protocol (FP) multiplexing technology, thus improving the transmission efficiency. l IP header compression The UDP/IP header can be compressed to decrease the packet header overhead, reduce the packet loss, and shorten the period of packet response. l PPP multiplexing Multiple pTRAU frames are multiplexed into a PPP packet to decrease the packet header overhead and thus improve the transmission efficiency. Packet multiplexing can greatly improve the transmission efficiency in Ater compression transmission mode when the timeslot resources are limited. For details of packet multiplexing, see 2.52 IP Transport Architecture Description.
?.3. Reliability
Ater Compression Transmission can improve transmission resource utilization; however, due to the inherent characteristics of IP transmission, more bit errors, jitter, and delay are generated. In addition, IP transmission has more protocol layers than TDM transmission, thus higher reliability is required. Ater Compression Transmission provides high reliability at the physical layer and the data link layer. l l At the physical layer, the active/standby switchover is performed without disrupting services in the case of board fault or optical port fault. At the data link layer, the MLPPP (Multilink PPP) group is configured to achieve PPP link redundancy.
In the case of TC fault, the TC pool function can be enabled.

l l If the core network supports IP transmission, the A over IP mode is recommended. If the core network does not support IP transmission and the Abis interface uses IP/HDLC transmission, then the use of IP transmission on the Ater interface can save the cost of board configuration and Ater transmission resources. Hardware upgrade is required to implement IP transmission on the Ater interface. If the Abis interface uses TDM transmission but the Ater interface uses IP transmission, the configuration cost is increased and the speech quality is degraded. In this case, Ater Compression Transmission is not recommended. When the Ater interface uses IP transmission, the Abis and Ater interfaces can be configured with the same type of interface board to save transmission resources.
2.13.5 Parameters
This chapter describes the parameters related to Ater compression transmission. For the meaning of each parameter, see Table 2-21. For the default value, value ranges, and MML commands of each parameter, see Table 2-22.
Table 2-21 Parameter description (1) Parameter Description Transport mode of the Ater interface. The Ater interface can be in TDM or in IP transport mode. Type of the adjacent node Uniquely identifies a BSC in the TC pool
Ater Interface Transfer Mode Adjacent Node Type BSC ID
Table 2-22 Parameter description (2) Parameter Defau lt Value GUI Value Range Actual Value Range Un it MML Com mand SET BSCB ASIC (Mand atory) Impac t
Ater Interface Transfer Mode
TDM
TDM (TDM), IP (IP) ABIS(Abis Interface), A (A Interface), BSC(Ater Interface on BSC), TC (Ater Interface on TC), IUR_G (IUR_G Interface)
TDM, IP
No ne
BSC
Adjacent Node Type
None
ABIS, A, BSC, TC, IUR_G
No ne
ADD ADJN ODE (Mand atory) ADD ADJN ODE (Mand atory)
Adjace nt node
BSC ID
None
0~15
0~15
No ne
Adjace nt node
2.13.6 Counters
None.
2.13.7 Glossary

l l l l l l l l l RFC1661: The Point-to-Point Protocol (PPP) RFC1990: The PPP Multilink Protocol (ML-PPP) RFC 2686: The Multi-Class Extension to Multi-Link PPP RFC 3153: PPP Multiplexing BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.14 Automatic Level Control

2.14.1 Introduction
2.14.1.1 Scope
This document describes automatic level control (ALC) feature of Huawei GSM BSS. It covers the function of and technologies mechanisms regarding ALC.


Automatic Level Control Change History provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change: refers to the change in the Automatic Level Control feature of a specific product version. l
Issue 08 (2011-09-30)
Editorial change
Editorial change: refers to changes in information that has already been included, or the addition of information that was not provided in the pervious version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30)) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
01(2009-06-30)
This is the initial commercial release of GBSS9.0. Compared with 01 (2008-04-30) of GBSS8.1, issue 01(2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
2.14.2 Overview
In the communication system, the voice level fluctuates according to the mobile terminal and transmission line. That is, different mobile terminals and transmission lines result in different levels of voice fluctuation. This deteriorates the voice quality and adversely affects the user experience. To solve this problem, the Automatic Level Control (ALC) feature is introduced. ALC adjusts the gain of uplink and downlink digital speech signals every 20 ms and changes the amplitude of digital speech signals in static or dynamic mode. This keeps the voice level of the entire network within an appropriate range, prevents volume fluctuation for the two parties during a call, and prevents voice distortion.
ALC keeps the voice level within an appropriate range and improves user experience. As a result, the average call duration in the communication system is prolonged, and the operator's revenue is increased.
NOTE
If the voice volume in the network is stable, you are advised to adopt the default configuration of ALC.

There are three ALC modes: fixed gain mode, fixed level mode, and adaptive level mode. The ALC feature is enabled only when the ALC Switch parameter is set to Open. l Fixed gain mode When the ALC Mode parameter is set to Fixed Gain Mode, the uplink and downlink voice data is sent to the fixed gain module. ALC increases or decreases the amplitude of the voice level according to the predefined ALC Fix Gain. l Fixed level mode When the ALC Mode parameter is set to Fixed Level Mode, the uplink and downlink voice data is sent to the fixed level module. ALC increases or decreases the amplitude of the voice level according to the predefined ALC Fix Target Level to keep the voice level in compliance with the predefined ALC Fix Target Level. l Adaptive level mode When the ALC Mode parameter is set to Adaptive Mode, the uplink and downlink voice data is sent to the adaptive level module. ALC increases or decreases the amplitude of the voice level according to the predefined ALC Min Target Level and ALC Max Target Level to keep the voice level within the range defined by ALC Min Target Level and ALC Max Target Level. Generally, the ALC mode that best suits the actual configuration is adopted to process the uplink and downlink voice data, thus achieving the gain control over the voice data flow.
NOTE
l ALC is effective for both uplink voice level and downlink voice level. Therefore, when the ALC Mode parameter is set to Fixed Gain Mode, the ALC Fix Gain parameter should not be set to a too great value to prevent too high to too low voice level caused by the dual application of ALC. l The ALC Max Gain parameter specifies the maximum gain of the voice level. This parameter is valid only when the ALC Mode parameter is set to Fixed Level Mode or Adaptive Mode. By default, this parameter is set to 6 dB. If the setting of the ALC Max Gain parameter affects the actualization of the target level in the fixed level mode or the adaptive level mode, you are advised to set the ALC Max Gain parameter to the largest possible difference between the voice level and the expected target level. l If the Tandem Free Operation (TFO) feature is enabled during a call, the ALC feature does not take effect for this call.
2.14.4 Parameters
The following describes the parameters related to ALC. For the meaning of each parameter, see Table 2-23. For the default value, value range, and related MML commands of each parameter, see Table 2-24.
Issue 08 (2011-09-30)
232
Table 2-23 Parameter description (1) Parameter ALC Switch ALC Mode ALC Fix Gain ALC Fix Target Level ALC Min Target Level ALC Max Target Level Description Whether to enable the adaptive level control (ALC) function ALC level control mode Fixed gain value in fixed gain mode Target level in fixed level mode Mimumum target level in adaptive ALC mode Maximum target level in adaptive ALC mode
Table 2-24 Parameter description (2) Parameter Default Value GUI Value Range Actual Value Range Unit MML Comma nd SET TCPAR A (Optiona l) Impact
ALC Switch
CLOSE
CLOSE (Close), OPEN (Open) FIXEDLEV EL(Fixed level mode), ADAPTIVE (Adaptive mode), FIXEDGAI N(Fixed gain mode)
CLOSE , OPEN
None
Board
ALC Mode
FIXEDG AIN
FIXED LEVEL , ADAP TIVE, FIXED GAIN
None
SET TCPAR A (Optiona l) SET TCPAR A (Optiona l) SET TCPAR A (Optiona l)
Board
ALC Fix Gain
-12~12
-12~12
dB
Board
ALC Fix Target Level
-18
-23~-4
-23~-4
dBm
Board
Issue 08 (2011-09-30)
233
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comma nd SET TCPAR A (Optiona l) SET TCPAR A (Optiona l)
Impact
ALC Min Target Level
-23
-23~-4
-23~-4
dBm
Board
ALC Max Target Level
-4
-23~-4
-23~-4
dBm
Board
2.14.5 Counters
None.
2.14.6 Glossary
2.14.7 References
The reference is as follows: ITU-T Recommendation G.169, Automatic Level Control Devices, 1999/06
2.15 Automatic Noise Compensation

2.15.1 Introduction
2.15.1.1 Scope
This document describes the automatic noise compensation (ANC) feature of Huawei GBSS. It covers the function of and mechanism regarding this feature.

It is assumed that users of this document are familiar with GSM basics and have a working knowledge of GSM telecommunication. This document is intended for:
l l
Personnel working on Huawei GSM products or systems System operators who need a general understanding of this feature

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change: refers to the change in the automatic noise compensation (ANC) feature of a specific product version. l Editorial change Editorial change: refers to changes in information that has already been included, or the addition of information that was not provided in the pervious version.
Document Issues
01 (2009-09-30)
2.15.2 Overview
In the communication system, when one party of a call is in a noisy environment, this party cannot hear the voice clearly if the volume of the voice from the other party is low. To solve this problem, the Automatic Noise Compensation (ANC) feature is introduced. ANC adaptively raises the volume of the voice from the other end when the background noise is loud at the local end. This improves the ratio of the voice from the other end to the background noise at the local end. In this way, the user at the local end can clearly hear the voice from the other end over the mobile phone, and the voice quality is subjectively improved. ANC can adaptively adjust the volume of the voice from the other end when the background noise is loud at the local end. This improves the voice quality, prolongs the average call duration, and increases the operator's revenue.
NOTE
If the background noise is loud at the peer end of a call, the noise is transmitted to the local end in the downlink speech signals, and ANC may increase the amplitude of the noise in the downlink speech signals. This adversely affects the voice quality at the local end. In this case, you are advised to enable the ANC feature with the Automatic Noise Restraint (ANR) feature at the same time. The ANR feature can reduce the noise in the uplink speech signals.

ANC processes only downlink speech signals. ANC adjusts the gain of downlink digital speech signals according to the uplink input noise level every 20 ms to dynamically change the amplitude of digital speech signals. This keeps the ratio of downlink output voice level to uplink
input noise level in compliance with a predefined value. Thus, the user at the local end can clearly hear the voice from the other end over the mobile phone. The ANC feature is enabled only when the ANC Switch parameter is set to Open. ANC performs the following operations to improve the voice quality: 1. 2. Calculates the noise level in the uplink. Calculates the voice level in the downlink. l If the ratio of the voice level in the downlink to the noise level in the uplink is greater than or qual to ANC Target SNR, ANC does not process the downlink speech signals. l If the ratio of the voice level in the downlink to the noise level in the uplink is lower than ANC Target SNR, ANC adjusts the gain of downlink speech signals until the ratio is equal to ANC Target SNR.
NOTE
l Based on the actual requirements, the gain of the downlink speech signals range from 3 dB to 12 dB. The ANC Max Gain parameter specifies the maximum gain of the downlink speech signals. If the ANC Max Gain parameter is set to a small value, the target ratio of the voice level in the downlink to the noise level in the uplink may be difficult to achieve. If the ANC Max Gain parameter is set to a large value, the user experience may be affected because of the abrupt change in the downlink voice volume. l If the Tandem Free Operation (TFO) feature is enabled during a call, the ANC feature does not take effect for this call.
2.15.4 Parameters
This chapter describes the parameters related to ANC. For the meaning of each parameter, see Table 2-25. For the default value, value range, and related MML commands of each parameter, see Table 2-26. Table 2-25 Parameter description (1) Paramete r ANC Switch ANC Target SNR ANC Max Gain Description
Whether to enable the adaptive noise cancel (ANC) function. The system adjusts the remote input so that the ratio of the remote signal to the local noise is above the value of this parameter. Maximum gain to the signals from the remote end. If the parameter is set to a small value, the target SNR may be restrained when the signal arrives at the local end.
Issue 08 (2011-09-30)
236
Table 2-26 Parameter description (2) Para meter Default Value GUI Value Range CLOSE (Close), OPEN (Open) Actual Value Range Unit MML Comman d SET TCPARA (Optional) SET TCPARA (Optional) SET TCPARA (Optional) Impact
ANC Switc h ANC Target SNR ANC Max Gain
CLOSE
CLOSE, OPEN
None
Board
12
10~30
10~30
dB
Board
3~30
3~30
dB
Board
2.15.5 Counters
None.
2.15.6 Glossary

l l l l l BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.16 Automatic Noise Restraint

2.16.1 Introduction
2.16.1.1 Scope
This document describes automatic noise restraint (ANR) feature of Huawei GSM BSS. It covers the function of and technologies mechanisms regarding ANR.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Automatic Noise Restraint feature of a specific product version. l Editorial change Editorial change refers to changes in information that has already been included, or the addition of information that was not provided in the previous version.
02 (2009-09-30)
This is the first commercial release of GBSS9.0. Compared with 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change
Issue 08 (2011-09-30)
238
2.16.2 Overview
When one party of a call is in a noisy environment, for example, in stations, in plazas, or along busy roads, the noise in the environment is transmitted to the other party of the call through the microphone in the MS. Thus, the other party of the call cannot hear the voice clearly. To solve this problem, the Automatic Noise Restraint (ANR) feature is introduced. ANR reduces the background noise in the uplink speech signals and improves the SNR and speech intelligibility. In this way, the other party of the call can clearly hear the voice.

ANR periodically analyzes the speech signals. Through energy estimation, SNR estimation, sound measurement estimation, and frequency offset estimation of different frequency bands, ANR identifies the background noise and performs filtering based on the identification of the background noise to obtain the time-domain speech signals after noise restraint. The ANR feature is enabled only when the ANR Switch parameter is set to Open. Among the parameters related to ANR, only the ANR Noise Reduction Level parameter needs to be set. Other parameters adopt the default values. The ANR Noise Reduction Level parameter specifies the noise suppression level in the ANR. A high absolute value of this parameter indicates a high noise suppression level. ANR performs the following operations to restrain the noise: 1. The system performs weighting and window processing on the speech signals.
NOTE
In signal processing, a window function is a function that is zero-valued outside of some chosen interval. When another function or a signal (data) is multiplied by a window function, the product is also zerovalued outside the interval: all that is left is the "view" through the window.
2. 3. 4. 5.
The system performs FFT to convert time-domain speech signals into frequency-domain speech signals. The system divides the generated frequency-domain speech signals into 16 frequency bands for energy estimation. The system performs the SNR estimation based on the noise energy of each frequency band. After the SNR estimation, each SNR value is associated with a sound measurement estimation value. The system accumulates the sound measurement estimation values of 16 frequency bands to obtain the sum. The system performs the frequency offset estimation. (1) The transient energy of a frequency band is expressed in the unit of dB.
6.
Issue 08 (2011-09-30)
239
(2) The system compares the transient energy of a frequency band with the mean energy of all frequency bands. (3) The system obtains the frequency offset of each frequency band. The accumulated frequency offset of all the frequency bands is the overall frequency offset estimation.
NOTE
The mean energy of all frequency bands is calculated through a smooth processing method. The smooth coefficient is related to the total energy of current frames and must be calculated for each frame. The smooth method is the method used when dispersed data convert to continuous data.
7. 8.
The signals with a low sound measurement estimation value or a low frequency offset are identified as the noise signals. The system calculates the frequency band gain.
NOTE
The frequency band gain is SNR-related and should not exceed one.
9.
After the noise identification, the frequency-domain speech signals of each frequency band are weighted by the frequency band gain to complete the frequency filtering.
10. The system restores the time-domain speech signals by using the IFFT.
CAUTION
l l If the Tandem Free Operation (TFO) feature is enabled during a call, the ANR feature does not take effect for this call. When using a voice quality test device to perform a test, you are advised to disable ANR to obtain accurate test result.
2.16.4 Parameters
This chapter describes the parameters related to automatic noise restraint. For the meaning of each parameter, see Table 2-27. For the default value, value ranges, and MML commands of each parameter, see Table 2-28. Table 2-27 Parameter description (1) Parameter ANR Switch ANR Noise Reduction Level Description Whether to enable the adaptive noise restrain (ANR) function. This parameter determines the noise depression degree. A large absolute value of this parameter corresponds to a strong depression.
Issue 08 (2011-09-30)
240
Table 2-28 Parameter description (2) Paramete r Default Value GUI Value Range CLOSE (Close), OPEN (Open) Actual Value Range Uni t MML Comman d SET TCPARA (Optional) SET TCPARA (Optional) Impact
ANR Switch ANR Noise Reduction Level
CLOSE
CLOSE, OPEN
Non e
Board
-13
-32~0
-32~0
dB
Board
2.16.5 Counters
None.
2.16.6 Glossary
2.16.7 References
None.
2.17 BCCH Dense Frequency Multiplexing

2.17.1 Introduction
2.17.1.1 Scope
This document describes BCCH dense frequency multiplexing of Huawei GBSS, which is also known as tight BCCH. It covers the function of and mechanism regarding BCCH dense frequency multiplexing, including tight BCCH common channel assignment, tight BCCH handover algorithm, and channel assignment for tight BCCH handover.

l l

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BCCH dense frequency multiplexing feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02(2009-09-30)
01(2009-06-30)
2.17.2 Overview
In a network where the frequency resources are limited, relatively few frequencies at the FH layer are a capacity bottleneck. Increasing the number of frequencies at the FH layer can improve the system capacity. In general, the frequencies planned for a network include BCCH frequencies and TCH frequencies. BCCH frequencies and TCH frequencies adopt different multiplexing modes. For
example, the BCCH frequencies are multiplexed in 4x3 mode, while the TCH frequencies are multiplexed in 1x3 mode. In a network whose frequencies are limited, if the BCCH uses more frequencies, fewer frequencies are available for the TCHs, and thus the system capacity is smaller. BCCH dense frequency multiplexing enables the BCCHs to reuse frequencies more tightly to free more frequencies for non-BCCH TRXs, thus increasing the system capacity. The BCCH dense frequency multiplexing technology is applicable to the network with limited frequency resources. It helps to increase the reusability of BCCH frequencies and reduce the number of frequencies used by the BCCHs. Therefore, more frequencies can be used at the FH layer. BCCH dense frequency multiplexing has the following advantages: l l l l Reduces the number of frequencies occupied by the BCCHs, and improves the spectrum utilization Increases the number of frequencies available for TCHs and for FH, expands the system capacity without adding new hardware, and saves the costs of adding sites and cells Assigns the TCHs on BCCH frequencies to only the MSs near the BTS, thus improving the voice quality because of less uplink interference Reduces random access failures, and improves the access performance
2.17.3 Technical Principles

When BCCH dense frequency multiplexing is adopted, a cell is classified into different logical layers: TCH layer on the BCCH TRX and FH layer, as shown in Figure 2-30. l l The FH layer serves and covers the entire network, including cell edges. The TCH layer on the BCCH frequency, however, covers only the MSs near the BTS to guarantee call access and to reduce interference near the BTS.
Figure 2-30 Logical layers of BCCH dense frequency multiplexing
Issue 08 (2011-09-30)
243
A denser frequency multiplexing pattern tends to increase the interference on the BCCH, therefore, proper channel allocation and handover algorithms are required to allocate the TCHs on the BCCH TRX to the MSs near the BTS. In this way, the restriction of multiplexing density on the BCCH TRX is reduced. The BCCH dense frequency multiplexing consists of: l l l Tight BCCH common channel assignment Tight BCCH handover algorithm Channel assignment for tight BCCH handover
Tight BCCH Common Channel Assignment

During an initial access request or a non-tight BCCH handover, if TIGHT BCCH Switch is set to Yes, a TCH is assigned according to the following principles: l l If a TCH on non-BCCH TRXs is available, the TCH is preferentially assigned to ensure access performance. If all the TCHs on non-BCCH TRXs are occupied, the TCH on the BCCH frequency is assigned.
During the assignment, the TCHs on the BCCH TRX are preferentially assigned if the call meets the following conditions: l l l The uplink receive level is greater than Level Thresh for Assign BCCH Under TBCCH. The uplink receive quality is smaller than Quality Thresh for Assign BCCH Under TBCCH. The load on the non-BCCH TRXs in the cell is higher than Load Threshold for TIGHT BCCH HO.
Tight BCCH Handover Algorithm

When all the TCHs on non-BCCH frequencies are occupied, the signal quality of an MS on the cell edge decreases if the TCH on the BCCH frequency is assigned to the MS. Therefore, if the load on the non-BCCH TRXs exceeds Load Threshold for TIGHT BCCH HO, the MS that is away from the cell edge and whose signal quality is smaller than RX_QUAL Threshold for TIGHT BCCH HO is handed over to the TCH on the BCCH TRX. Thus, the TCHs on the nonBCCH TRX are reserved to ensure the call access performance. The principle of tight BCCH handover algorithm is as follows: During the period specified by TIGHT BCCH HO Watch Time, if the period when tight BCCH handover conditions are met exceeds TIGHT BCCH HO Valid Time, a handover is initiated. Otherwise, no handover is initiated.
Channel Assignment for Tight BCCH Handover

The purpose of tight BCCH handover is to hand over a call near the BTS to the BCCH TRX. Therefore, if the cause of a handover is tight BCCH handover, a TCH on the BCCH TRX is assigned.
Issue 08 (2011-09-30)
244

Recommended Scenarios
In general, the 4x3 mode is used in BCCH frequency planning to guarantee high carrier-tointerference ratios (CIRs) between BCCH frequencies. In this mode, the BCCHs occupy 12 frequencies, thus decreasing the number of frequencies available for frequency hopping. In a network where the frequency resources are limited, the number of frequencies available for frequency hopping is a critical capacity factor. No anti-interference technology such as FH is used on BCCH frequencies. Therefore, if the 3x3 mode is used in BCCH frequency planning, the TCHs on BCCH frequencies have low interference resistance, and the interference in the system is increased. But if a denser frequency multiplexing mode is adopted, the performance of TCHs may decrease badly to an unacceptable level. Enabling BCCH dense frequency multiplexing on the BSC can solve the above problems.
Impact on Other Features

The impact of BCCH dense frequency multiplexing on other features is as follows: l l Concentric cells do not support dense BCCH frequency multiplexing. Multiband networks do not support dense BCCH frequency multiplexing.
Impact on System Performance

If the load of a cell increases, an MS served by a channel on the non-BCCH TRX may be handed over to a channel on the BCCH TRX, thus increasing the number of handovers in the network.
2.17.5 Parameters
This chapter describes the parameters related to BCCH dense frequency multiplexing. For the meaning of each parameter, see Table 2-29. For the default value, value ranges, and MML commands of each parameter, see Table 2-30. Table 2-29 Parameter description (1) Parameter TIGHT BCCH Switch Description Whether to enable the BCCH aggressive frequency reuse algorithm During channel assignment, the assignment of channels on the BCCH TRXs depends on the uplink receive level, quality, and non-BCCH load. The TCHs are preferentially assigned on the BCCH TRXs if the following conditions are met: 1. The uplink receive level after filtering is higher than "Level Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH". 2. The uplink receive quality level after filtering is lower than "Quality Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH". 3. The non-BCCH load is higher than "Intracell Non Main BCCH Load Threshold of TIGHT BCCH".
Level Thresh for Assign BCCH Under TBCCH

Issue 08 (2011-09-30)
Parameter
Description During channel assignment, the assignment of channels on the BCCH TRXs depends on the uplink receive level, quality, and non-BCCH load. The TCHs are preferentially assigned on the BCCH TRXs if the following conditions are met: 1. The uplink receive level after filtering is higher than "Level Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH". 2. The uplink receive quality level after filtering is lower than "Quality Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH". 3. The non-BCCH load is higher than "Intracell Non Main BCCH Load Threshold of TIGHT BCCH". During channel assignment, the assignment of channels on the BCCH TRXs depends on the uplink receive level, quality, and non-BCCH load. The TCHs are preferentially assigned on the BCCH TRXs if the following conditions are met: 1. The uplink receive level after filtering is higher than "Level Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH". 2. The uplink receive quality level after filtering is lower than "Quality Thresh. for Assigning Main BCCH Carrier Channel Under TIGHT BCCH". 3. The non-BCCH load is higher than "Intracell Non Main BCCH Load Threshold of TIGHT BCCH". When an intra-cell TIGHT BCCH handover needs to be performed (handover from the non-BCCH to BCCH), the downlink receive quality must be smaller than the value of this parameter. The P/N criterion must be met for triggering a TIGHTBCCH handover. That is, the TIGHTBCCH handover can be triggered only if P seconds among N seconds meet the triggering conditions. This parameter corresponds to N in the P/N criterion. The P/N criterion must be met for triggering a TIGHT BCCH handover. That is, the TIGHT BCCH handover can be triggered only if P seconds among N seconds meet the triggering conditions. This parameter corresponds to P in the P/N criterion.
Quality Thresh for Assign BCCH Under TBCCH
Load Threshold for TIGHT BCCH HO RX_QUAL Threshold for TIGHT BCCH HO
TIGHT BCCH HO Watch Time
TIGHT BCCH HO Valid Time
Table 2-30 Parameter description (2) Parameter Defau lt Value GUI Value Range Actual Value Range Unit MML Command SET GCELLCHM GBASIC (Optional) SET GCELLCHM GAD (Optional) Impa ct
TIGHT BCCH Switch Level Thresh for Assign BCCH Under TBCCH
OFF
OFF(Off), ON(On)
OFF, ON
None
Cell
30
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
246
Parameter Quality Thresh for Assign BCCH Under TBCCH Load Threshold for TIGHT BCCH HO RX_QUAL Threshold for TIGHT BCCH HO TIGHT BCCH HO Watch Time TIGHT BCCH HO Valid Time
Defau lt Value
GUI Value Range
Actual Value Range
Unit
MML Command
Impa ct
0~7
0~7
None
SET GCELLCHM GAD (Optional) SET GCELLHOA D(Optional) SET GCELLHOA D(Optional) SET GCELLHOB ASIC (Optional) SET GCELLHOB ASIC (Optional)
Cell
80
0~100
0~100
per cent
Cell
0~7
0~7
None
Cell
1~32
0.5~16, step: 0.5
Cell
1~32
0.5~16, step: 0.5
Cell
2.17.6 Counters
None.
2.17.7 Glossary

l l l l l l BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
Issue 08 (2011-09-30)
247
2.18 BSC Node Redundancy

2.18.1 Introduction
2.18.1.1 Scope
This document describes BSC node redundancy of Huawei GBSS. It covers the function of and technology mechanisms regarding BSC node redundancy, including network topologies, fault detection betwwen BSCs, migration of service objects, audit of dual-homed service objects, and maintenance of dual-homed service objects.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BSC node redundancy feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table.
Change Type Feature change Editorial change
Change Description None. The structure of the document is optimized.
Parameter Change None. None.
01 (2009-0630)
2.18.2 Overview
A BSC controls the radio resources of all the BTSs under the BSC. When the BSC is faulty, none of the BTSs under the BSC can access the network because the BSC cannot provide services in its coverage area. Similarly, if the transmission links between the BSC and the core network (CN) are faulty, the BSC is not operational and thus the BSC cannot provide services in its coverage area. To prevent the occurrence of the preceding situations, Huawei provides a BSC node redundancy solution at the BSC level. The BSC node redundancy is a function through which two BSCs form a redundancy group. The two BSCs in a redundancy group work in 1+1 load sharing mode. When one BSC in a redundancy group is faulty or all the signaling links on the A interface are faulty, the other BSC in this group takes over the voice and data services. In this manner, the reliability and robustness of the network are improved, the service disruption time due to BSC failure is reduced, and the quality of service (QoS) is improved. In a redundancy group, each of the two BSCs considers itself as the local BSC and the other as the peer BSC. A service object may be an originating signaling point code (OPC), BTS, cell, neighboring cell, or point-to-point BSSGP virtual connection (PTP BVC). l Normally, a primary service object provides services at the local BSC (the primary BSC) and its configuration data is backed up at the peer BSC (the secondary BSC). A primary service object provides services at the peer BSC only when the local BSC is faulty or when all the signaling links on the A interface of the local BSC are faulty. Similarly, a secondary service object provides services at the peer BSC and its configuration data is backed up at the local BSC. A secondary service object provides services at the local BSC only when the peer BSC is faulty or when all the signaling links on the A interface of the peer BSC are faulty. The primary service object and the secondary service object are collectively called dualhomed service objects. A single-homed service object exists only at one BSC in a redundancy group.
Each BSC in a redundancy group backs up the configuration data of the primary service objects of the other BSC. Normally, each BSC controls its primary service objects and backs up the configuration data of its secondary service objects. When one BSC is faulty, the other BSC can detect the failure automatically. Then, it makes the backup configuration data of the secondary service objects take effect and takes over the services from the faulty BSC. The backup configuration data includes the information about OPCs, BTSs, and cells.
Figure 2-31 shows the networking diagram of BSC node redundancy. Figure 2-31 Networking diagram of BSC node redundancy
BSC node redundancy can be implemented only in an all-IP networking scenario, that is, IP transmission is used on the A, Abis, Gb, and inter-BSC interfaces. The inter-BSC interface is a fault detection and audit channel between the two BSCs in a redundancy group. If the peer BSC detects through the inter-BSC interface that the local BSC is faulty, the peer BSC takes over the control rights of the dual-homed service objects from the local BSC. The service objects that are taken over include OPCs, BTSs, cells, and PTP BVCs. BSC node redundancy is applicable to the following scenarios: l
Issue 08 (2011-09-30)
BSC failure
All the boards of a BSC are faulty or all the A interface boards of a BSC are faulty. l Failure in the signaling links on the A interface All the signaling links on the A interface are faulty. The MML commands ACT GBSCREDGRP and DEA GBSCREDGRP can be executed at the local BSC or peer BSC to enable and disable the BSC node redundancy function respectively. Local BSC ID and Peer BSC ID identify the two BSCs in a redundancy group. BSC Node Redundancy Group Index identifies a redundancy group. The benefits of the BSC node redundancy feature are as follows: l Improved device reliability The BSCs in a redundancy group work in 1+1 load sharing mode. When one BSC in a redundancy group is faulty, the other BSC immediately takes over the services of the faulty BSC. In this manner, the device reliability is improved without reduction of the system capacity. l Improved transmission reliability Cross connections are established between the two BSCs in a redundancy group and the CN. The A interface of one BSC provides redundancy for the A interface of the other BSC in the case that all the signaling links on the A interface of the other BSC are faulty. In this manner, the reliability of the network is improved.

BSC node redundancy is applicable only to an all-IP networking scenario. In such a scenario, IP transmission is used on the A, Abis, Gb, and inter-BSC interfaces.
?.1. Network Topologies on the Abis Interface

A dual-homed BTS can be connected to the primary and secondary BSCs through IP routers according to the IP addresses. Three network topologies are applicable to the Abis interface. l Network topology 1: The telecom operator has an IP bearer network on the Abis interface, and the BTS is located at the remote end of the IP bearer network. The BTS is connected to an optical transceiver in IP over E1/T1 transmission mode. The BSC is connected to the border router on the BSC side in IP over FE/GE transmission mode. Then, the border router on the BTS side is connected to the primary and secondary BSCs according to the IP addresses. See Figure 2-32.
Issue 08 (2011-09-30)
251
Figure 2-32 IP bearer network on the Abis interface and BTS at the remote end of the IP bearer network
Network topology 2: The telecom operator has an IP bearer network on the Abis interface, and the BTS is located at the local end of the IP bearer network. The BTS is connected to the border router on the BTS side in IP over E1/T1 or IP over FE/ GE transmission mode. The BSC is connected to the border router on the BSC side in IP over FE/GE transmission mode. Then, the border router on the BTS side is connected to the primary and secondary BSCs according to the IP addresses. See Figure 2-33.
Issue 08 (2011-09-30)
252
Figure 2-33 IP bearer network on the Abis interface and BTS at the local end of the IP bearer network
Network topology 3: The telecom operator does not have an IP bearer network on the Abis interface. In this scenario, a branch router is required to implement the IP network topology on the Abis interface. The BTS is connected to an optical transceiver in IP over E1/T1 transmission mode. The BSC is connected to the router on the BSC side in IP over FE/GE transmission mode. Then, the intermediate branch router is connected to the primary and secondary BSCs according to the IP addresses. See Figure 2-34. To prevent a single-point failure in the transmission network, the intermediate branch router should support redundancy backup, and the intermediate branch router and the router on the BSC side should be placed in different geographical locations. This ensures that the redundancy function is operational even if an intermediate branch router is faulty.
Issue 08 (2011-09-30)
253
Figure 2-34 No IP bearer network on the Abis interface
?.2. Network Topologies on the A and Gb Interfaces

The two BSCs in a redundancy group can be connected to the NEs in the CN through the A and Gb interfaces according to the IP addresses. The network topology on the A interface is similar to that on the Gb interface. The following takes the A interface as an example to describe the network topologies. Two network topologies are applicable to the A interface. l Network topology 1: The bearer network on the A interface is an FE/GE Ethernet. The BSC is connected to the border router on the BSC side in IP over FE/GE transmission mode. The MSC is connected to the border router on the MSC side in IP over FE/GE transmission mode. Cross connections are established between the BSCs in a redundancy group and the CN. See Figure 2-35.
Figure 2-35 FE/GE Ethernet as the IP bearer network
Network topology 2: The bearer network on the A interface is an SDH or a PDH network. The BSC is connected to the CN through an optical transceiver in IP over E1/T1 transmission mode. See Figure 2-36. Figure 2-36 SDH or PDH network as the IP bearer network
Issue 08 (2011-09-30)
255
?.3. Network Topology on the Inter-BSC Interface

The BSCs in a redundancy group are connected to each other through IP routers. The routes on the inter-BSC interface are of two types: direct route between BSCs in a redundancy group and alternative routes that pass through the routers on the MSC side. Alternative routers help to improve the reliability of inter-BSC fault detection. See Figure 2-37. Figure 2-37 Routes on the inter-BSC interface
The inter-BSC interface is used for two purposes: heartbeat detection and exchange of the information about dual-homed BTSs between the BSCs in a redundancy group. The FG2a/FG2c board should be added to the BSC. This board is used to carry the inter-BSC communication links on the inter-BSC interface.
2.18.3.2 Fault Detection

Fault detection is implemented between two BSCs by checking for the heartbeat signals from the peer end. The information contained in the heartbeat signals includes local BSCID, homing states of the primary service objects, and homing states of the secondary service objects. The heartbeat signals are carried by the signaling channels on the inter-BSC interface. One signaling channel corresponds to one SCTP channel using IP transmission. Each BSC in a redundancy group sends heartbeat signals to the peer BSC at regular intervals specified by Interval for Sending Heartbeat. When one of the following conditions is met, it is regarded that the local BSC is faulty and the local BSC stops sending heartbeat signals to the peer BSC:
l l
The local BSC is faulty. The local BSC detects that the duration of the failure of all the signaling links on the A interface exceeds CN Fault Delay.
When the peer BSC detects that the disruption time of heartbeat signal transmission exceeds Master Service Active Delay or Slave Service Active Delay, the peer BSC considers that the local BSC cannot provide services. Then, the peer BSC takes over the primary service objects from the faulty BSC.
2.18.3.3 Migration of Service Objects

In normal conditions, the two BSCs in a redundancy group manage their own primary service objects. When the local BSC fails to provide services, the peer BSC takes over the control rights of the dual-homed service objects from the local BSC but does not take over the control rights of singlehomed service objects from the local BSC. The sequence of taking over the control rights is as follows: Firstly, the control rights of dual-homed OPCs are taken over. Then, the control rights of the dual-homed BTSs and cells corresponding to the dual-homed OPCs are taken over.
NOTE
If the BSC node redundancy function is disabled after control rights are taken over, the peer BSC automatically releases the control rights of the secondary service objects. The local BSC takes over the control rights of the primary service objects again.
?.1. Dual-Homed OPCs

When the local BSC in a redundancy group works properly, The host type of signalling point of an OPC determines whether the local BSC takes over the OPC. l l l If The host type of signalling point of an OPC is set to PRIMHOST(PRIMHOST), the OPC immediately provides services and the Hosted state of the OPC is YES. If The host type of signalling point of an OPC is set to SLAVEHOST(SLAVEHOST), the OPC does not provide services and the Hosted state of the OPC is NO If The host type of signalling point of an OPC is set to SINGLEHOST (SINGLEHOST), the OPC immediately provides services and the Hosted state of the OPC is YES.
When the local BSC in a redundancy group cannot provide services, the single-homed OPCs of the local BSC cannot provide services either and they become faulty. The peer BSC takes over the dual-homed OPCs from the local BSC. That is, the Hosted state of the secondary OPCs of the peer BSC is changed from NO to YES, and the secondary OPCs of the peer BSC are immediately activated and provide services.
?.2. Dual-Homed BTSs

After dual-homed OPCs are taken over, the dual-homed BTSs corresponding to the dual-homed OPCs are taken over. When the local BSC in a redundancy group works properly, HostType of a BTS determines whether the local BSC takes over the BTS. l If HostType of a BTS is set to PRIMHOST(PRIMHOST), the BTS provides services and the Hosted state of the BTS is Yes.
Issue 08 (2011-09-30)
l l
If HostType of a BTS is set to SLAVEHOST(SLAVEHOST), the BTS does not provide services and the Hosted state of the BTS is No. If HostType of a BTS is set to SINGLEHOST(SINGLEHOST), the BTS provides services and the Hosted state of the BTS is Yes.
For a network topology in BSC node redundancy mode, the following parameters of the dualhomed BTSs of the local BSC should be set: Peer BTS ID, Peer BSC IP, Peer BSC ID, and Peer BSC Mask. The values of these parameters are sent by the local BSC to the BTSs. When the local BSC cannot provide services, the single-homed BTSs of the local BSC do not provide services either and they become faulty; the Hosted state of the secondary BTSs of the peer BSC is changed from No to Yes; the peer BSC takes over the primary BTSs of the local BSC. The procedure for taking over the BTSs from the local BSC is as follows: 1. 2. 3. 4. When the local BSC is faulty, the signaling link between the local BSC and its primary BTS is faulty. According to the IP address of the peer BSC sent by the local BSC, the primary BTS sends a link establishment request to the peer BSC. After the link between the peer BSC and the primary BTS of the local BSC is established, the peer BSC sends a reset command to the BTS. After the BTS is reset, it sends a DHCP request to the peer BSC. The peer BSC sends the BTS a DHCP response message. The message carries the IP address allocated to the BTS and the IP address of the peer BSC. After receiving the two IP addresses, the BTS sends a signaling link establishment request to the peer BSC. After the signaling link is established, the peer BSC sends the related configuration data to the BTS. Then, the BTS is taken over by the peer BSC and starts providing services.
5. 6.
?.3. Dual-Homed Cells and PTP BVC Objects

The homing attributes of the dual-homed OPCs, BTSs, and cells of a BSC in a redundancy group are the same. Therefore, after a dual-homed BTS is taken over by a BSC, the dual-homed cells under the BTS are automatically taken over by the BSC. The homing attributes of PTP BVC objects are the same as those of dual-homed cells. Therefore, after the dual-homed cells under a BTS are taken over by a BSC, the dual-homed PTP BVC objects under the BTS are automatically taken over by the BSC.
?.4. Re-Homing Policy of Dual-Homed Service Objects

When the local BSC in a redundancy group is faulty, the peer BSC takes over the primary service objects from the local BSC. When the local BSC becomes normal, the service objects that are taken over by the peer BSC can switch back to the local BSC according to the re-homing policy specified by ReHost Type: l l If ReHost Type is set to REHOSTRIGHTNOW(ReHostRightNow), service objects switch back to the local BSC immediately after the local BSC becomes normal. If ReHost Type is set to REHOSTDELAY(ReHostDelay), service objects wait for a period specified by ReHostDelayTime after the local BSC becomes normal and then switch back to the local BSC.
Issue 08 (2011-09-30)
If ReHost Type is set to REHOSTWHEN(ReHostWhen), service objects switch back to the local BSC at the time specified by ReHost Absolute Time after the local BSC becomes normal. ReHost Absolute Time must be set in the format of hh:mm:ss.
The procedure for switching back service objects is similar to the procedure for switching the service objects from a faulty BSC to a normal BSC, except the switching is performed in the reverse direction.
2.18.3.4 Audit of Dual-Homed Service Objects

When the two BSCs in a redundancy group work properly, they regularly audit the homing attributes of BTSs and the homing states of service objects of each other. When a BSC detects that the homing attributes of a BTS at the two BSCs are inconsistent, a Dual-Hosted BTS Configuration Error alarm is generated. When a BSC detects that the homing states of a service object at the two BSCs are inconsistent, the following processing may be performed as required: l If the Hosted state of a service object at both the primary and secondary BSCs is No, the primary and secondary BSCs wait for the periods specified by Master Service Active Delay and Slave Service Active Delay respectively. Then, the control rights negotiation procedure is initiated to determine which BSC can obtain the control rights of the service object. If the Hosted state of a service object at both the primary and secondary BSCs is Yes, the primary BSC immediately takes over the control rights of the service object, and the secondary BSC does not take over the control rights of the service object.
2.18.3.5 Maintenance of Dual-Homed Service Objects

A service object is managed by only one BSC at a time. After the control rights of a dual-homed service object are switched from the local BSC to the peer BSC, the local BSC cannot maintain the service object. Therefore, a BSC can maintain the service object whose Hosted state is Yes. This service object can be a primary or secondary service object of the BSC.

A redundancy group consists of only two BSCs and the two BSCs work in 1+1 backup mode. Each BSC in a redundancy group is configured with dual-homed service objects. The sum of the number of single-homed service objects and the number of dual-homed service objects at each BSC cannot exceed the capacity specification of the BSC. The two BSCs in a redundancy group must be connected to the same MSC or MSC pool. The two BSCs in a redundancy group must be connected to the same SGSN or SGSN pool. When service objects are switched or switched back from one BSC to another, services are disrupted. BSC node redundancy is applicable only to an all-IP networking scenario. In such a scenario, IP transmission is used on the A, Abis, Gb, and inter-BSC interfaces. A BTS cannot be directly connected to a BSC in a redundancy group in IP over E1/T1 or IP over FE/GE transmission mode. That is, the BTS must be connected to a BSC in a redundancy group through routers.
A transmission failure on the Abis interface does not trigger the switching of services from one BSC to the other BSC in a redundancy group. The cell broadcast center (CBC) service does not support BSC node redundancy. The built-in PCU supports BSC node redundancy, whereas the external PCU does not. During the upgrade of a BSC, BSC node redundancy should be disabled.
2.18.5 Parameters
This chapter describes the parameters related to BSC node redundancy. For the meaning of each parameter, see Table 2-31. For the default value, value ranges, and MML commands of each parameter, see Table 2-32. Table 2-31 Parameter description (1) Parameter Local BSC ID Peer BSC ID Description Local BSC identity. It identifies a BSC. Peer BSC identity. Index of the BSC Node Redundancy Group. It identifies a BSC redundancy group. The BSC node redundancy is a function through which two BSCs form a redundancy group. The two BSCs in a redundancy group work in 1+1 load sharing mode. When one BSC in a redundancy group is faulty or all the signaling links on the A interface are faulty, the other BSC in this group takes over the voice and data services. In this manner, the reliability and robustness of the network are improved, the service disruption time due to BSC failure is reduced, and the quality of service (QoS) is improved. Time interval for sending a handshake message between BSC6900s. The parameter checks whether the communication among BSCs in a redundancy group is normal. Time delay in the detection of core network interface failure. Within the preset value of this parameter, the BSC6900 continuously detects core network interface failures and then releases the management right of service objects. If no handshake message is received from the peer within the delay, the master service is activated. A master service object provides services at the local BSC and its configuration data is backed up at the peer BSC. A master service object provides services at the peer BSC only when the local BSC is faulty or when all the signaling links on the A interface of the local BSC are faulty.
BSC Node Redundancy Group Index
Interval for Sending Heartbeat
CN Fault Delay
Master Service Active Delay
Issue 08 (2011-09-30)
260
Parameter
Description If no handshake message is received from the peer within the delay, the slave service is activated. A slave service object provides services at the peer BSC and its configuration data is backed up at the local BSC. A slave service object provides services at the local BSC only when the peer BSC is faulty or when all the signaling links on the A interface of the peer BSC are faulty. Indicates the host type of the signalling point. When the BSC node redundancy feature is enabled, the primary BSC and the secondary BSC each must be configured with a signaling point coded in the same mode. The host type of the signaling point of the primary BSC is set to "PRIMHOST", and the host type of the signaling point of the secondary BSC is set to "SLAVEHOST". When the BSC node redundancy feature is disabled, the host type of the signaling point of the BSC is set to "SINGLEHOST". Host type of an IP BTS Identifier of the peer BTS on the homing BSC6900 side IP address of the peer BSC6900 on the homing BSC6900 side Subnet mask of the port IP address at the peer BSC6900. Policy type of re-homing Delay time of re-homing Absolute time of re-homing
Slave Service Active Delay
The host type of signalling point HostType Peer BTS ID Peer BSC IP Peer BSC Mask ReHost Type ReHostDelayTime ReHost Absolute Time
Table 2-32 Parameter description (2) Parameter Defau lt Value GUI Value Range Actual Value Range Unit MML Command SET GBSCREDGRP (Mandatory) SET GBSCREDGRP (Mandatory) SET GBSCREDGRP (Mandatory) Imp act
Local BSC ID
None
0~65534
0~65534
None
BSC
Peer BSC ID BSC Node Redundancy Group Index
None
0~65534
0~65534
None
BSC
None
0~65534
0~65534
None
BSC
Issue 08 (2011-09-30)
261
Parameter Interval for Sending Heartbeat CN Fault Delay Master Service Active Delay Slave Service Active Delay
Defau lt Value
GUI Value Range
Actual Value Range
Unit
MML Command SET GBSCREDGRP (Optional) SET GBSCREDGRP (Optional) SET GBSCREDGRP (Optional) SET GBSCREDGRP (Optional)
Imp act
1~60
1~60
BSC
30
1~60
1~60
Cell
45
1~600
1~600
BSC
300
1~600 SINGLEHO ST (SINGLEHO ST), PRIMHOST (PRIMHOST ), SLAVEHOS T (SLAVEHO ST) SINGLEHO ST(Single Host), PRIMHOST (Primary Host), SLAVEHOS T(Slave Host) 0~2047 None None
1~600
BSC
The host type of signalling point
SINGL EHOS T
SINGLEHOS T, PRIMHOST, SLAVEHOS T
None
ADD OPC (Optional)
SCC P
HostType Peer BTS ID Peer BSC IP Peer BSC Mask
SINGL EHOS T None None None
SINGLEHOS T, PRIMHOST, SLAVEHOS T 0~2047 0.0.0.0~255.2 55.255.255 0.0.0.0~255.2 55.255.255
None None None None
SET BTSIP (Optional) SET BTSIP (Mandatory) SET BTSIP (Mandatory) SET BTSIP (Mandatory)
BTS BTS BTS BTS
Issue 08 (2011-09-30)
262
Parameter
Defau lt Value
GUI Value Range REHOSTRI GHTNOW (ReHostRigh tNow), REHOSTDE LAY (ReHostDela y), REHOSTW HEN (ReHostWhe n)
Actual Value Range
Unit
MML Command
Imp act
ReHost Type
REHO STDE LAY
REHOSTRI GHTNOW, REHOSTDE LAY, REHOSTWH EN
None
SET GREDGRPPRIM HOSTPOLICY (Mandatory) SET GREDGRPPRIM HOSTPOLICY (Mandatory) SET GREDGRPPRIM HOSTPOLICY (Mandatory)
Cell
ReHostDela yTime ReHost Absolute Time
600
1~3600
1~3600
Cell
None
hour, min, sec
00:00:00~23: 59:59
None
Cell
2.18.6 Counters
None.
2.18.7 Glossary

2.19 BSS Local Switching

2.19.1 Introduction
2.19.1.1 Scope
This document describes BSS local switching of Huawei GBSS. It covers the function of and mechanism regarding BSS local switching, including the principles and procedures of the feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BSS local switching feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
Issue 08 (2011-09-30)
264
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description In IP transmission mode, BTS local switching can be performed on calls served by different BTSs in the same local switching area. The structure of the document is optimized. Parameter Change None.
Editorial change
None.
2.19.2 Overview
BSS local switching is classified into BSC local switching and BTS local switching. BSC local switching is triggered when the BSC detects that the calling MS and the called MS of a call are under the same BSC. When BSC local switching is triggered, the speech signals are looped back on the BSC side. In addition, the signaling link on the MSC side is reserved, and the transmission resources on the Ater interface and the TC resources are released. BTS local switching is triggered when the BTS detects that the calling MS and the called MS of a call are under the same BTS, in the same BTS group, or in the same local switching area. When BTS local switching is triggered, the speech signals are looped back on the BTS side, in the BTS group, or in the local switching area. In addition, the signaling link on the MSC side is reserved, and the transmission resources on the Ater interface, the transmission resources on the Abis interface, and the TC resources are released. As shown in Figure 2-38, MS1 (calling MS) and MS2 (called MS) are under the same BSC; MS3 (calling MS) and MS4 (called MS) are under the same BSC. The speech signals are looped back to the MS on the BSC side, thus BSC local switching is triggered, and the transmission resources on the Ater interface are released.
Issue 08 (2011-09-30)
265
Figure 2-38 Loopback of speech signals in BSC local switching
As shown in Figure 2-39, MS1 (calling MS) and MS2 (called MS) are in the same BTS group; MS3 (calling MS) and MS4 (called MS) are under the same BTS. The speech signals are looped back to the MS in the BTS group or on the BTS side, thus BTS local switching is triggered in TDM transmission mode, and the transmission resources on the Ater interface and a certain number of transmission resources on the Abis interface are released.
Issue 08 (2011-09-30)
266
Figure 2-39 Loopback of speech signals in BTS group in BTS local switching
As shown in Figure 2-40, the BTSs are in IP transmission mode. MS1 (calling MS) and MS2 (called MS) are in the same local switching area, and MS3 (calling MS) and MS4 (called MS) are in the same local switching area. The speech signals are looped back to the MS on the IP BTS in the local switching area, thus BTS local switching is triggered and in IP transmission mode, and the transmission resources on the Ater interface and a certain number of transmission resources on the Abis interface are released.
Issue 08 (2011-09-30)
267
Figure 2-40 Loopback of speech signals in local switching area in BTS local switching
BSS local switching reduces the number of transmission resources required by a local call. Thus, when BSS local switching is enabled, the number of transmission resources configured can be reduced, and the cost can also be reduced. In addition, BSS local switching avoids transcoding on the CN side. In this way, it reduces, especially in satellite transmission mode, the transmission delay of speech signals and thus improves the speech quality. BTS local switching and BSC local switching can be enabled independently or simultaneously. BSS local switching can be enabled only when the speech coding rate of the calling MS is the same as the speech coding rate of the called MS. BSS local switching applies to the following scenarios: l Where the calling MS and the called MS of a large number of calls are under the same BSC or BTS BSS local switching applies to the scenario where the calling MS and the called MS of a large number of calls are under the same BSC or BTS. In this way, a large number of transmission resources are saved. l Network in remote areas BSS local switching applies to the remote areas where transmission resources are insufficient to save the transmission resources. l
Issue 08 (2011-09-30)
Temporary coverage or emergent communication requirements

BSS local switching applies to the scenario of a large gathering or capacity expansion to meet the call requirements. BSS local switching has the following benefits: l l When BSS local switching is enabled, the speech signals are looped back on the BSS side. Thus, the transmission resources on the Abis and Ater interfaces are released. When BSS local switching is enabled, the TC resources are released. If the calling MS and the called MS of a large number of calls are under the same BSC, the number of TC resources configured can be reduced, and thus the initial construction cost can be reduced. BSS local switching simplifies speech transcoding, enhances the speech quality, and improves the user experience. To implement BSS local switching, the telecom operator only needs to upgrade the software. The Core Network (CN) need not be reconfigured or modified, and thus the investment of the telecom operator is protected.
l l

2.19.3.1 Principles
?.1. Principles of BSC Local Switching
Figure 2-41 shows BSC local switching. Figure 2-41 BSC local switching
Issue 08 (2011-09-30)
269

NOTE
BSC local switching is performed on the BSS side without involving NEs on the NSS side. In other words, the speech signals are not sent to the MSC. The transmission resources of sections D and E on the MSC side, however, are not released.
After BSC local switching is enabled, the speech signals are looped back to the BTS on the BSC side. In addition, idle frames are sent to the CN through the A interface board. In this way, the transmission resources of section C between the BSC and the TC are released, whereas the circuits occupied on the CN side are not released. As the number of transmission resources required by a call are reduced, the number of transmission resources configured are also reduced. In this way, the cost of network deployment is reduced.
NOTE
In virtual loopback, the BSC does not process the signals received from the CN and sends idle frames to the CN to ensure that the circuits occupied on the CN side are not released. Hence, the purpose of virtual loopback is to ensure that the circuits on the CN side are occupied.
If BSC local switching is only used to save the transmission resources on the Ater interface, BSS Local Switching General Strategy should be set to BSCONLY(BSC Only). If BSC local switching is preferentially used to save the transmission resources on the Abis and Ater interfaces, BSS Local Switching General Strategy should be set to BSCPRIORITY(BSC Priority). If BSS Local Switching General Strategy is set to BSCPRIORITY(BSC Priority), you should also configure Options for BSC Local Switch.
?.2. Principles of BTS Local Switching

When Service Type of the Abis interface is set to TDM, BTS local switching is classified into the local switching under a BTS and the local switching in a BTS group. The local switching under a BTS is considered as the local switching in a BTS group that is comprised of one BTS. In the case of the local switching in a BTS group, the BSC automatically locates the BTS that is the nearest to the calling MS and the called MS and performs loopback on the BTS to save the transmission resources. When Service Type of the Abis interface is set to IP, BTS local switching is classified into the local switching under a BTS and the local switching between IP BTSs in a local switching area. The local switching under a BTS is considered as a special case of the local switching between IP BTSs in a local switching area. Local switching area refers to the area where the BTSs are in IP transmission mode and are connected to the same BSC. In addition, the BTSs in the local switching area can communicate with each other in IP transmission. BTS local switching can be triggered only when the calling MS and called MS of a call are served by the BTS/BTSs in the same local switching area. In a local switching area, the BSC sends the local switching message to the IP BTS. Based on the local switching message received, the IP BTS then changes the destination IP address to the IP address of the destination IP BTS to complete the loopback of the speech signals. Figure 2-42 shows BTS local switching.
Issue 08 (2011-09-30)
270
Figure 2-42 BTS local switching
NOTE
BTS local switching is performed on the BSS side without involving NEs on the NSS side. In other words, the speech signals are not sent to the MSC. The transmission resources of sections D and E on the MSC side, however, are not released.
After BTS local switching is enabled, the speech signals are looped back on the BTS to the MS, and idle frames are sent to the MSC on the A interface. In this case, the transmission resources of section B between the BTS and the BSC and the transmission resources of section C between the BSC and the TC are released, whereas the circuits occupied on the CN side are not released. If BTS local switching is only used to save the transmission resources on the Abis interface, BSS Local Switching General Strategy should be set to BTSONLY(BTS Only). If BTS local switching is preferentially used to save the transmission resources on the Abis and Ater interfaces, BSS Local Switching General Strategy should be set to BTSPRIORITY(BTS Priority). If BSS Local Switching General Strategy is set to BTSPRIORITY(BTS Priority), you should also configure Options for BTS Local Switch. In IP transmission mode, BSC local switching is not supported. In this case, BSS Local Switching General Strategy should be set to BTSONLY(BTS Only).
2.19.3.2 Procedures Related to BSS Local Switching

?.1. Triggering of the BSS Local Switching Call
The triggering of the BSS local switching call involves the following procedures: checking of BSS local switching general strategy, detection of the BSS local switching call, checking of
BSC/BTS local switching strategy, and speech version selection for the BSS local switching call.
Checking of BSS Local Switching General Strategy

After the called party answers the phone or the incoming BSC handover is complete, the BSC determines whether to enable BSC local switching or BTS local switching based on the setting of BSS Local Switching General Strategy. In the following cases, however, BSC local switching or BTS local switching cannot be triggered. l BSS Local Switching General Strategy is set to support BSC local switching. BSC local switching cannot be triggered if either the calling MS or the called MS meets the conditions specified by Avoid Number for BSC n, which here n indicates the rang from 1 to 10. l BSS Local Switching General Strategy is set to support BTS local switching. BTS local switching cannot be triggered if either the calling MS or the called MS meets the conditions specified by Avoid Number for BTS n, which here n indicates the rang from 1 to 10.
NOTE
l Avoid Number for BSC n and Avoid Number for BTS n are optional parameters. l BTS local switching can be triggered only when Support BTS Local Switch of the BTS or of the BTSs in the BTS group is set to YES(Yes).
Detection of the BSS Local Switching Call

If BSS local switching can be triggered, the BSC starts the BSS local switching call detection to detect whether the calling MS and the called MS are under the same BSC.
Checking of BSC/BTS Local Switching Strategy

If the calling MS and the called MS are under the same BSC, the BSC checks the settings of Options for BSC Local Switch or Options for BTS Local Switch to determine whether to trigger local switching. l BSC local switching If Options for BSC Local Switch is set to UNCONDITIONALSTART (Unconditional Start), BSC local switching is always triggered. If Options for BSC Local Switch is set to ATERCONGESTS(Start When Ater Congests), BSC local switching is triggered only when the congestion rate on the Ater interface exceeds Ater Jam Rate for BSC Local Switch. If Options for BSC Local Switch is set to PREFIXNUMBER(Start by Prefix Number), BSC local switching is triggered when either the calling MS or the called MS meets the conditions specified by Prefix Number for BSC n, which here n indicates the rang from 1 to 10. l BTS local switching If Options for BTS Local Switch is set to UNCONDITIONALSTART (Unconditional Start), BTS local switching is always triggered. If Options for BTS Local Switch is set to ABISCONGESTS(Start When Abis Congests), BTS local switching is triggered only when the congestion rate on the Abis interface exceeds Abis Jam Rate for BTS Local Switch.
If Options for BTS Local Switch is set to PREFIXNUMBER(Start by Prefix Number), BTS local switching is triggered when either the called MS or the calling MS meets the conditions specified by Prefix Number for BTS n, which here n indicates the rang from 1 to 10. In IP transmission mode, BTS local switching can be triggered only when the BTS serving the calling MS and the BTS serving the called MS are in the same local switching area.
NOTE
Region Information specifies Whether the BTS serving the calling MS and the BTS serving the called MS are in the same local switching area. If Region Information on the two BTSs is set to the same value, the two BTSs are in the same local switching area.
NOTE
For the BTS that works in IP transmission mode, Options for BTS Local Switch is invalid.
Speech Version Selection for the BSS Local Switching Call

To trigger BSS local switching, the speech coding rate of the calling MS must be the same as the speech coding rate of the called MS. If the speech coding rate of the calling MS is different from the speech coding rate of the called MS, the BSC must adjust the speech coding rate of one MS according to that of the other MS through forced switching. If the adjustment fails, BSS local switching is not triggered. If the AMR feature is enabled, the calling MS and the called MS must use the same speech coding rate. In addition, the speech coding rate must remain unchanged. To select the speech version for a BSS local switching call, you should first identify the speech versions that are supported by both the calling MS and the called MS. You can select the speech version for the call based on the following principles: l If the speech version used by either MS of the call is supported by the other MS, you can select the speech version for the call based on the policies described in Table 2-33. Table 2-33 Policies for speech version selection ACS Consistenc y Full- or Half-Rate Channel Speech Version
AMR
Adjustment Policy The conditions for local switching are met. The speech version need not be adjusted. The speech version need not be adjusted. The local switching can not be enabled.
The AMR feature is enabled on both the calling MS and the called MS.
Consistent
Not involved
Not involved
Inconsistent
Not involved
Not involved
Issue 08 (2011-09-30)
273
AMR
ACS Consistenc y
Full- or Half-Rate Channel
Speech Version
Adjustment Policy Disable the AMR feature. Ensure that the speech coding rate and speech version for one MS are consistent with the speech coding rate and speech version for the other MS. Convert the half-rate channel involved in the call to a full-rate channel. Ensure that the speech coding rate and speech version for one MS are consistent with the speech coding rate and speech version for the other MS. The conditions for local switching are met. The speech version need not be adjusted. Change the speech version for the high-rate MS to the speech version for the lowrate MS.
The AMR feature is enabled on one MS of the call.
Not involved
Not involved
Not involved
Inconsistent The AMR feature is disabled for both the calling MS and the called MS.
Not involved
Same
Not involved
Consistent
Different
NOTE
The same speech coding rate must be used for the calling MS and the called MS when the AMR feature is enabled. If the speech version used by one MS is not supported by the other MS, the AMR feature should be disabled.
If the speech versions used by the two MSs are different and among the two speech versions only one speech version is supported by both MSs, the supported speech version is selected as the target speech version. If neither the speech version used by the calling MS nor the speech version used by the called MS is supported by the other, the highest speech version that is supported both by the calling MS and the called MS is selected as the target version. If both the full-rate speech version and the half-rate speech version are supported, the full-rate version is preferred.
In the case of BSC local switching, if the speech version used by the calling MS is the same as the speech version used by the called MS, the BSC sets up a speech signal link, and the TDM switching is performed in the BSC. After the TDM switching is complete, the BSC releases the redundant resources on the Ater interface.
NOTE
The speech signals are not sent to the MSC, and thus the MSC cannot obtain the information about BSC local switching. To ensure the consistency between the circuit resources on the BSC side and the circuit resources on the MSC side, the BSC does not release the Circuit Identity Code (CIC) circuit.
Issue 08 (2011-09-30)
274
In the case of BTS local switching, if the speech version used by the calling MS is the same as the speech version used by the called MS, the commands sent from the BSC to the BTS varies with the value of Service Type of the Abis interface. l If Service Type of the Abis interface is TDM, the BSC sends a link setup command to the BTS. In this case, the speech signals are looped back on the Abis interface of the BTS or the BTS group. After the loopback is successful, the BSC releases the resources on the Abis and Ater interfaces. If Service Type of the Abis interface is IP, the BSC sends the IWF to the BTS where the local switching needs to be performed. The BTS then locally loops back the speech frames based on the IWF. After the loopback is successful, the BSC releases the resources on the Abis and Ater interfaces.
?.2. Restoration of the BSS Local Switching Call

Restoration of the BSS local switching call refers to the process through which a call in the local switching state is restored to a normal call. The restoration procedure for the BSC local switching call is different from the restoration procedure for the BTS local switching call.
Restoration of the BSC Local Switching Call

When a BSC local switching call is handed over, the target cell may not support local switching or the outgoing BSC handover may fail. In this case, the BSC local switching call should be restored to a normal call before the handover. In other words, the BSC should re-establish the transmission channel on the Ater interface. Thus, the speech signals can be sent on the transmission channel to the MSC and then to the MS. The BSC determines whether to restore a BSC local switching call. No manual intervention or data configuration is required.
Restoration of the BTS Local Switching Call

When a BTS local switching call is handed over, the TRX on which the target channel is located may not support local switching or the handover of a specific type may fail. In this case, the BTS local switching call should be restored to a normal call before the handover. The restoration procedure for a BTS local switching call varies with the setting of Service Type. l When Service Type of the Abis interface is set to TDM, the BSC sends a link setup command to the BTS to re-establish a channel on the Abis interface to transfer the speech signals from the Um interface. In addition, the BSC sets up a transmission channel on the Ater interface. Thus, the speech signals can be sent on the transmission channel to the MSC and then to the MS. When Service Type of the Abis interface is set to IP, the BSC sends a local switching restoration command to the BTS to re-establish the route for the transmission of IP datagrams. In addition, the BSC sets up the transmission channel on the Ater interface. Thus, the speech signals can be sent on the transmission channel to the MSC and then to the MS.
The BSC determines whether to restore a BTS local switching call. No manual intervention or data configuration is required.
Issue 08 (2011-09-30)
275
?.3. Handover of the BSS Local Switching Call
Intra-BSC Handover
The intra-BSC handover of a BSS local switching call is similar to the intra-BSC handover of a normal call. The only difference is that the speech version for the BSS local switching call cannot be changed after the intra-BSC handover. In other words, the speech version for the call after the handover must be the same as the speech version before the handover. This restriction on the speech version may decrease the handover success rate and increase the call drop rate. The call is a BSC local switching call. l If the intra-BSC handover is successful, the BSC local switching call may remain as a BSC local switching call, be converted to a BTS local switching call, or be restored to a normal call, depending on the support capability of the target channel for local switching. If the intra-BSC handover fails, the BSC local switching call remains as a BSC local switching call.
The call is a BTS local switching call. l If the intra-BSC handover is successful, the BTS local switching call may remain as a BTS local switching call, be converted to a BSC local switching call, or be restored to a normal call, depending on the support capability of the target channel for local switching. If the intra-BSC handover fails and the BSC receives a handover detection message before the handover failure message, the BTS local switching call is restored to a normal call. Otherwise, the BTS local switching call remains as a BTS local switching call.
Outgoing BSC Handover

The procedure for the outgoing BSC handover of a BSS local switching call is as follows: 1. 2. The BSC determines whether to initiate an outgoing BSC handover based on the handover algorithm and sends a handover request to the MSC. The MSC receives the handover request and sends a handover command to the BSC. l If the BSC receives the handover command from the MSC, the BSC instructs the peer MS of the handover initiating MS that the call is to be restored to a normal call. This ensures normal speech after the outgoing BSC handover is successful. l If the BSC does not receive the handover command, the BSS local switching call remains as a BSS local switching call. l If the BSC receives a handover failure message from the MS, the BSC instructs the MS initiating the handover that the call is to be restored to a normal call.
2.19.3.3 Impact on CN Services

BSS local switching affects certain services on the CN side, as described in Table 2-34. Table 2-34 Availability of CN services after BSS local switching being enabled Service Ring Back Tone (RBT) service Availability Available Remarks The RBT service is performed before the called MS answers the phone, and thus it is not affected by BSS local switching.
276
Issue 08 (2011-09-30)
Service Call forwarding services
Availability Available
Remarks The call forwarding services are performed before the called MS answers the phone, and thus such services are not affected by BSS local switching. The call restriction supplementary services are performed before the called MS answers the phone and are controlled by the MSC and HLR. Thus, such services are not affected by BSS local switching. The number identification service is performed before the called MS answers the phone, and thus it is not affected by BSS local switching. The USSD is not related to call service, and thus it is not affected by BSS local switching. This service is not related to the switching of the CS speech signals. None. None.
Call restriction supplementary services
Available
Number identification service
Available
Unstructured Supplementary Service Data (USSD) Closed User Group (CUG) Call waiting (CW)/Call hold (CH) Three-party service/ Multi-party service (MPTY) Explicit Call Transfer (ECT) Lawful interception MSC playing the announcement during a call Dual Tone MultiFrequency (DTMF) number receiving during a call Speech service and then fax service Independent billing of BSS local switching
Available
Available Available Available
Available Conditionally available Conditionally available Unavailable
None. This service is available only when the Huawei CN equipment is installed. This service is available only when the Huawei CN equipment is installed. Users who require this service must apply for it. For the users who apply for this service, BSS local switching is not performed. Only the fax service can be performed. The fax service does not trigger BSS local switching. This service is available only when the Huawei CN equipment is installed.
Unavailable
Conditionally available
Issue 08 (2011-09-30)
277
Telecom operators can take the following measures to ensure the availability of those CN services that are affected by BSS local switching. l l To perform those CN services that become unavailable after BSS local switching is enabled, telecom operators can disable BSS local switching. To perform those CN services that are conditionally available after BSS local switching is enabled, telecom operators need to install Huawei CN equipment. When services such as MSC playing the announcement during a call and lawful interception are performed, Huawei MSC instructs Huawei BSC not to perform local switching or instructs Huawei BSC to convert a BSS local switching call to a normal call. When the independent billing of BSS local switching service is performed, Huawei BSC sends a message to the CN whenever Huawei BSC enables or disables BSS local switching. Based on the message sent from the Huawei BSC, the billing center starts or ends the billing of BSS local switching. The preceding measures help reduce the impact of BSS local switching on CN services and thus decrease the application restrictions on BSS local switching.

l In TDM transmission mode, BTS local switching can be performed only after the Flex Abis (a license is required) function is enabled. In IP transmission mode, BTS local switching can be performed on calls served by the same BTS and also on calls served by different IP BTSs in the same local switching area. In A over IP mode, BSS local switching is not supported. In BM/TC combined mode, only BTS local switching is supported. The implementation of BSS local switching may require the cooperation from the MSC. When MSC-Collaborated BSS Local Switching is set to BASIC(Basic Fun) or ENHANCED(Enhanced Fun), it indicates that BSS local switching is controlled by the MSC. The details are as follows: When MSC-Collaborated BSS Local Switching is set to BASIC(Basic Fun) and the MSC does not allow the BSS local switching of a certain call, the BSC does not perform local switching on the call. When MSC-Collaborated BSS Local Switching is set to ENHANCED(Enhanced Fun) and the MSC does not allow the BSS local switching of a certain call, the BSC does not perform local switching on the call; when the MSC allows the BSS local switching of the call, the BSC performs local switching on the call. In addition, the MSC can charge the local switching calls independently. l l l In the sites with combined BTS cabinets, BSS local switching can be enabled only when the BTS software and TRX software both support BSS local switching. BTS local switching and BTS ring topology cannot be enabled for a BTS in parallel. If the calling MS and the called MS are registered on two different MSCs, the BSS local switching is not supported regardless of whether the two MSCs are connected to the same MGW or different MGWs. In HDLC transmission mode, BSS local switching is not supported.
l l l
2.19.5 Parameters
This chapter describes the parameters related to BSS local switching.
For the meaning of each parameter, see Table 2-35. For the default value, value ranges, and MML commands of each parameter, see Table 2-36. Table 2-35 Parameter description (1) Parameter BSS Local Switching General Strategy Description General strategy of the BSS local switching, which includes the BSC local switching and the BTS local switching. The two functions cannot be enabled at the same time. Conditions for enabling the function of BSC local switching. UNCONDITIONALSTART: The function of BSC local switching is enabled without restriction. ATERCONGESTS: The function of BSC local switching is enabled when the congestion rate of the Ater interface exceeds the value of "Ater Cong Thres for BSC LocalSwitch". PREFIXNUMBER: The function of BSC local switching is enabled when the leading digits of the calling or called MSISDN are the preset value of "Prefix Number for BSC (1-10)". Service bearer mode of the BTS. Conditions for enabling the function of BTS local switching. UNCONDITIONALSTART: The function of BTS local switching is enabled without restriction. ABISCONGESTS: The function of BTS local switching is enabled when the congestion rate of the Abis interface exceeds the value of "Abis Cong Thres for BTS LocalSwitch". PREFIXNUMBER: The function of BTS local switching is enabled when the leading digits of the calling or called MSISDN are the preset value of "Prefix Number for BTS (1-10)". Whether to enable the BTS to support local switching If the BTS supports local switching, when the calling and called MSs are both within the BTS or BTS group, the voice signals are looped back to the MSs within the BTS or BTS group instead of being sent over the Abis interface to the BSC and MSC. In this way, the Abis resources between the convergence BTS and the BSC are released and saved. Threshold for enabling the BSC local switching. When the congestion rate at the Ater interface exceeds this threshold, the function is enabled. Threshold for enabling the BTS local switching. When the congestion rate at the Abis interface exceeds this threshold, the BTS local switching is enabled.
Options for BSC Local Switch Service Type
Options for BTS Local Switch
Support BTS Local Switch Ater Jam Rate for BSC Local Switch Abis Jam Rate for BTS Local Switch
Issue 08 (2011-09-30)
279
Parameter
Description Type of the BSS local switching with the cooperation of the MSC. NONSUPPORT: When performing local switching, the BSS need not determine whether the MSC allows an MS to be involved in local switching. BASIC: Assignment request messages and handover request messages sent by the MSC contain a flag indicating whether to allow an MS for local switching. The BSS must identify this flag when performing local switching. ENHANCED: Assignment request messages and handover request messages sent by the MSC contain a flag indicating whether to allow an MS for local switching. The BSS must identify this flag when performing local switching. In addition, when the BSS enables or stops local switching, the BSS sends a local switching enabled or stopped message to the MSC. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BTS local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BTS local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BTS local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BTS local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BTS local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BTS local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BTS local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BTS local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BTS local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BTS local switching function is disabled.
MSC-Collaborated BSS Local Switching Avoid Number for BTS 1 Avoid Number for BTS 2 Avoid Number for BTS 3 Avoid Number for BTS 4 Avoid Number for BTS 5 Avoid Number for BTS 6 Avoid Number for BTS 7 Avoid Number for BTS 8 Avoid Number for BTS 9 Avoid Number for BTS 10
Issue 08 (2011-09-30)
280
Parameter Avoid Number for BSC 1 Avoid Number for BSC 2 Avoid Number for BSC 3 Avoid Number for BSC 4 Avoid Number for BSC 5 Avoid Number for BSC 6 Avoid Number for BSC 7 Avoid Number for BSC 8 Avoid Number for BSC 9 Avoid Number for BSC 10
Description If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is disabled. If the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is disabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled.
Prefix Number for BTS 1
Issue 08 (2011-09-30)
281
Parameter
Description If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled.
Issue 08 (2011-09-30)
282
Parameter
Description If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled.
Prefix Number for BSC 1
Issue 08 (2011-09-30)
283
Parameter
Description If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled. If "Options for BSC Local Switch" is set to PREFIXNUMBER, and the first digits in the MSISDN of the called or calling are the same as the value of this parameter, the BSC local switching function is enabled. For example, if two numbers 135 and 139 are set in the list, and the first three digits in the MSISDN of the called or calling are 135 or 139, the BSC local switching function is enabled.
Issue 08 (2011-09-30)
284
Table 2-36 Parameter description (2) Paramete r Default Value GUI Value Range NEITHER START (Neither Start), BTSPRIO RITY (BTS Priority), BSCPRIO RITY (BSC Priority), BTSONL Y(BTS Only), BSCONL Y(BSC Only) UNCOND ITIONAL START (Unconditi onal Start), ATERCO NGESTS (Start When Ater Congests), PREFIXN UMBER (Start by Prefix Number) TDM, HDLC, HDLC_H ubBTS, IP Actual Value Range Unit MML Comman d Impact
BSS Local Switching General Strategy
NEITHER START
NEITHER START, BTSPRIO RITY, BSCPRIO RITY, BTSONL Y, BSCONL Y
None
SET BSSLS (Optional)
BSC
Options for BSC Local Switch
UNCOND ITIONAL START
UNCOND ITIONAL START, ATERCO NGESTS, PREFIXN UMBER TDM, HDLC, HubBTS, IP
None
SET BSSLS (Optional)
BSC
Service Type
TDM
None
ADD BTS (Optional)
BTS
Issue 08 (2011-09-30)
285
Paramete r
Default Value
GUI Value Range UNCOND ITIONAL START (Unconditi onal Start), ABISCO NGESTS (Start When Abis Congests), PREFIXN UMBER (Start by Prefix Number) NO(No), YES(Yes)
Actual Value Range
Unit
MML Comman d
Impact
Options for BTS Local Switch Support BTS Local Switch Ater Jam Rate for BSC Local Switch Abis Jam Rate for BTS Local Switch
UNCOND ITIONAL START
UNCOND ITIONAL START, ABISCO NGESTS, PREFIXN UMBER
None
SET BSSLS (Optional) SET BTSLSW (Optional) SET BSSLS (Optional) SET BSSLS (Optional)
BSC
NO
NO, YES
None
BTS
90
0~100
0~100
per cent
BSC
90
0~100 NONSUP PORT (Not Support), BASIC (Basic Fun), ENHANC ED (Enhanced Fun)
0~100
per cent
BSC
MSCCollaborat ed BSS Local Switching Avoid Number for BTS 1 Avoid Number for BTS 2
NONSUP PORT
NONSUP PORT, BASIC, ENHANC ED 1~32 characters 1~32 characters
None
ADD GCNNOD E (Optional) SET BSSLS (Optional) SET BSSLS (Optional)
MSC
None
None
None
BSC
None
None
None
BSC
Issue 08 (2011-09-30)
286
Paramete r Avoid Number for BTS 3 Avoid Number for BTS 4 Avoid Number for BTS 5 Avoid Number for BTS 6 Avoid Number for BTS 7 Avoid Number for BTS 8 Avoid Number for BTS 9 Avoid Number for BTS 10 Avoid Number for BSC 1 Avoid Number for BSC 2 Avoid Number for BSC 3 Avoid Number for BSC 4 Avoid Number for BSC 5
Default Value
GUI Value Range
Actual Value Range 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters
Unit
MML Comman d SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional)
Impact
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
Issue 08 (2011-09-30)
287
Paramete r Avoid Number for BSC 6 Avoid Number for BSC 7 Avoid Number for BSC 8 Avoid Number for BSC 9 Avoid Number for BSC 10 Prefix Number for BTS 1 Prefix Number for BTS 2 Prefix Number for BTS 3 Prefix Number for BTS 4 Prefix Number for BTS 5 Prefix Number for BTS 6 Prefix Number for BTS 7 Prefix Number for BTS 8
Default Value
GUI Value Range
Actual Value Range 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters
Unit
MML Comman d SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional)
Impact
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
Issue 08 (2011-09-30)
288
Paramete r Prefix Number for BTS 9 Prefix Number for BTS 10 Prefix Number for BSC 1 Prefix Number for BSC 2 Prefix Number for BSC 3 Prefix Number for BSC 4 Prefix Number for BSC 5 Prefix Number for BSC 6 Prefix Number for BSC 7 Prefix Number for BSC 8 Prefix Number for BSC 9 Prefix Number for BSC 10
Default Value
GUI Value Range
Actual Value Range 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters 1~32 characters
Unit
MML Comman d SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional) SET BSSLS (Optional)
Impact
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
None
None
None
BSC
2.19.6 Counters
2.19.7 Glossary

2.20 BTS Combined Cabinets and Cabinet Groups

2.20.1 Introduction
2.20.1.1 Scope
This document describes the BTS Combined Cabinets and Cabinet Groups feature.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BTS Combined Cabinets and Cabinet Groups feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.20.2 Overview
In heavy-traffic urban areas, telecom operators want to deploy a large-capacity BTS to reduce the number of BTSs and to save the construction and maintenance costs of BTSs. The number of TRXs that can be held by a single BTS cabinet, however, is limited. For example, a single BTS3012 cabinet holds a maximum of 12 TRXs. This means that a single cabinet cannot meet the requirements of telecom operators. To solve this problem, BTS combined cabinets and cabinet groups can be used to increase the capacity. For example, two combined cabinets and three cabinet groups of the BTS3012 support 72 TRXs. BTS combined cabinets and cabinet groups are applicable to the areas where the traffic is heavy and the construction and maintenance costs of BTSs are high. When a single cabinet cannot meet the large capacity requirement, combined cabinets can be used to expand the capacity. If combined cabinets still cannot meet the capacity requirement, cabinet groups can be used to expand the capacity. The BTS combined cabinets are multiple BTS cabinets of the same type that are connected through the signal cables for combined cabinets. The BTS combined cabinets function as one BTS. Among the combined cabinets, one cabinet provides transmission interfaces for the combined cabinets and performs operation and maintenance (OM) on the combined cabinets. This cabinet is called the main cabinet, and all the other cabinets are called extension cabinets. The main control board in the main cabinet is connected to the BSC through a transmission
cable. The main control board receives the traffic signals, signaling, OM signals, and clock synchronization signals from the transmission cable and then distributes the signals to the TRXs in the main cabinet through the internal bus. Meanwhile, the main control board distributes the signals to the TRXs in the extension cabinets through the signal cables for combined cabinets. In this manner, the services and OM of all the TRXs in the combined cabinets are synchronized. The BTS cabinet groups are multiple BTS combined cabinets that are connected through the signal cables for cabinet groups. The BTS cabinet groups function as one BTS. Among the cabinet groups, one cabinet group provides clock synchronization signals and OM signals for all the cabinet groups. This cabinet group is called the main cabinet group, and all the other cabinet groups are called extension cabinet groups. The main control board in the main cabinet of the main cabinet group receives the traffic signals, signaling, OM signals, and clock synchronization signals from the transmission cable. The main control board in the main cabinet of each extension cabinet group, however, extracts only the traffic signals and signaling from the transmission cable. The main control board in the main cabinet of each extension cabinet group obtains the OM signals and clock synchronization signals from the main control board in the main cabinet of the main cabinet group through the signal cables for cabinet groups. In this manner, the services and OM of all the TRXs in the cabinet groups are synchronized. As shown in Figure 2-43, one BTS consists of three cabinet groups, namely, one main cabinet group and two extension cabinet groups; the cabinet groups are connected to each other through the signal cables for cabinet groups. Each cabinet group consists of two cabinets, namely, one main cabinet and one extension cabinet; the cabinets are connected to each other through the signal cables for combined cabinets. Figure 2-43 Combined cabinets and cabinet groups
The capacity that can be expanded by using combined cabinets and cabinet groups, the types of signal cables for combined cabinets and cabinet groups, and the networking modes vary from one BTS type to another.

2.20.3.1 Combined Cabinets and Cabinet Groups of the BTS3012
One BTS3012 cabinet supports a maximum of 12 TRXs. If a synchronous cell needs more than 12 TRXs, combined cabinets can be used. The BTS3012 supports a maximum of 2 combined cabinets and 3 cabinet groups. The combined cabinets and cabinet groups of the BTS3012 support a maximum of 72 TRXs.
Implementation of Combined Cabinets

Figure 2-44 shows the connections of the BTS3012 combined cabinets. Among the combined cabinets of the BTS3012, only the main cabinet needs to be configured with the DTMU. The DTMU is connected to the BSC through a transmission cable and it receives the traffic signals, signaling, OM signals, and clock synchronization signals from the transmission cable. The DTMU, then, distributes the signals to the TRXs in the main cabinet through the internal bus. Meanwhile, the DTMU distributes the signals to the TRXs in the extension cabinet through the signals cables for combined cabinets. In this manner, the services and OM of all the TRXs in the combined cabinets are synchronized. Figure 2-44 Connections of the combined cabinets
Implementation of Cabinet Groups

Figure 2-45 shows the connections of the BTS3012 cabinet groups. The main cabinet in each cabinet group needs to be configured with the DTMU. The DTMU in the main cabinet of the main cabinet group receives the traffic signals, signaling, OM signals, and clock synchronization signals from the transmission cable. The DTMU in the main cabinet of each extension cabinet group, however, extracts only the traffic signals and signaling from the transmission cable. The DTMU in the main cabinet of each extension cabinet group obtains the OM signals and clock synchronization signals from the DTMU in the main cabinet of the main cabinet group through the signal cables for cabinet groups. In this manner, the services and OM of all the TRXs in the cabinet groups are synchronized. Figure 2-45 Connections of the cabinet groups
2.20.3.2 Combined Cabinets and Cabinet Groups of the BTS3006C

One BTS3006C cabinet supports a maximum of six TRXs. If a synchronous cell needs more than six TRXs, combined cabinets can be used. The BTS3006C supports a maximum of six
combined cabinets and does not support cabinet groups. The combined cabinets of the BTS3006C support a maximum of 36 TRXs. The main control board in the BTS3006C is the DMCM, which has two SFP optical ports: SFPA and SFP-B. The two ports are used to connect combined cabinets. They can be used interchangeably. For example, if cabinet 0 needs to be connected to cabinet 1 through an optical cable, the optical cable can be connected to the SFP-A or SFP-B optical port of cabinet 1. As one SFP optical port of cabinet 1 is connected to cabinet 0, the other SFP optical port of cabinet 1 can be connected to any SFP optical port of cabinet 2 if cabinet 1 needs to be connected to cabinet 2. In the case of combined cabinets, the hardware configuration of the BTS3006C main cabinet is the same as that of the BTS3006C extension cabinet. Both the main cabinet and the extension cabinet are configured with the DMCM. The settings of the DIP switches differentiate the main cabinet from the extension cabinet. The combined cabinets can use the chain topology or ring topology.
Implementation of the Combined Cabinets in the Chain Topology

Figure 2-46 shows the connections of the combined cabinets in the chain topology. Cabinet 0 is the main cabinet. The DMCM in the main cabinet is connected to the BSC through a transmission cable. The DMCM receives the traffic signals, signaling, OM signals, and clock synchronization signals from the BSC and then distributes the signals to the TRXs in the main cabinet through the internal bus. Meanwhile, the DMCM distributes the signals to the TRXs in the extension cabinets through the signal cables for combined cabinets. In this manner, the services and OM of all the TRXs in the combined cabinets are synchronized. Figure 2-46 Connections of the combined cabinets in the chain topology
Implementation of the Combined Cabinets in the Ring Topology

Figure 2-47 shows the connections of the combined cabinets in the ring topology. The dual-ring backup technology is adopted. In the ring topology, signals of combined cabinets are transmitted on both the forward ring and the reverse ring. By default, signals are transmitted on the forward ring in the following sequence: cabinet 0, cabinet 1, cabinet 2, cabinet 3, cabinet 4, and cabinet 5. When the transmission on the forward ring is disrupted, the forward ring is automatically switched to the reverse ring and signals are transmitted on the reverse ring in the following sequence: cabinet 0, cabinet 5, cabinet 4, cabinet 3, cabinet 2, and cabinet 1. For combined cabinets, the ring topology is more reliable and robust than the chain topology. Cabinet 0 is the main cabinet. The DMCM in the main cabinet is connected to the BSC through a transmission cable. The DMCM receives the traffic signals, signaling, OM signals, and clock synchronization signals from the BSC and then distributes the signals to the TRXs in the main
cabinet through the internal bus. Meanwhile, the DMCM distributes the signals to the TRXs in the extension cabinets through the signal cables for combined cabinets. In this manner, the services and OM of all the TRXs in the combined cabinets are synchronized. Figure 2-47 Connections of the combined cabinets in the ring topology
2.20.3.3 Combined Cabinets and Cabinet Groups of the BTS3002E

One BTS3002E cabinet supports a maximum of two TRXs. If a synchronous cell needs more than two TRXs, combined cabinets can be used. The BTS3002E supports a maximum of six combined cabinets and does not support cabinet groups. The combined cabinets of the BTS3002E support a maximum of 12 TRXs. The main control board in the BTS3002E is the DMCM, which has two SFP optical ports: SFPA and SFP-B. The two ports are used to connect combined cabinets. They can be used interchangeably. For example, if cabinet 0 needs to be connected to cabinet 1 through an optical cable, the optical cable can be connected to the SFP-A or SFP-B optical port of cabinet 1. As one SFP optical port of cabinet 1 is connected to cabinet 0, the other SFP optical port of cabinet 1 can be connected to any SFP optical port of cabinet 2 if cabinet 1 needs to be connected to cabinet 2. In the case of combined cabinets, the hardware configuration of the BTS3002E main cabinet is the same as that of the BTS3002E extension cabinet. Both the main cabinet and the extension cabinet are configured with the DMCM. The settings of the DIP switches differentiate the main cabinet from the extension cabinet. The combined cabinets can use the chain topology or ring topology.
Implementation of the Combined Cabinets in the Chain Topology

Figure 2-48 shows the connections of the combined cabinets in the chain topology. Cabinet 0 is the main cabinet. The DMCM in the main cabinet is connected to the BSC through a transmission cable. The DMCM receives the traffic signals, signaling, OM signals, and clock synchronization signals from the transmission cable and then distributes the signals to the TRXs
in the main cabinet through the internal bus. Meanwhile, the DMCM distributes the signals to the TRXs in the extension cabinets through the signal cables for combined cabinets. In this manner, the services and OM of all the TRXs in the combined cabinets are synchronized. Figure 2-48 Connections of the combined cabinets in the chain topology
Implementation of the Combined Cabinets in the Ring Topology

Figure 2-49 shows the connections of the combined cabinets in the ring topology. The dual-ring backup technology is adopted. In the ring topology, signals of combined cabinets are transmitted on both the forward ring and the reverse ring. By default, signals are transmitted on the forward ring in the following sequence: cabinet 0, cabinet 1, cabinet 2, cabinet 3, cabinet 4, and cabinet 5. When the transmission on the forward ring is disrupted, the forward ring is automatically switched to the reverse ring and signals are transmitted on the reverse ring in the following sequence: cabinet 0, cabinet 5, cabinet 4, cabinet 3, cabinet 2, and cabinet 1. For combined cabinets, the ring topology is more reliable and robust than the chain topology. Cabinet 0 is the main cabinet. The DMCM in the main cabinet is connected to the BSC through a transmission cable. The DMCM receives the traffic signals, signaling, OM signals, and clock synchronization signals from the BSC and then distributes the signals to the TRXs in the main cabinet through the internal bus. Meanwhile, the DMCM distributes the signals to the TRXs in the extension cabinets through the signal cables for combined cabinets. In this manner, the services and OM of all the TRXs in the combined cabinets are synchronized. Figure 2-49 Connections of the combined cabinets in the ring topology
Issue 08 (2011-09-30)
296
2.20.3.4 Hybrid Cabinet Groups of the BTS3012 and the BTS3X

The BTS3012, BTS30, and BTS312 can form hybrid cabinet groups. The cabinets in the main cabinet group must be the BTS3012 cabinets. The cabinets in extension cabinet groups can be the BTS30 or BTS312 cabinets. Figure 2-50 shows the connections between the BTS3012 main cabinet group and two BTS30 extension cabinet groups. Figure 2-51 shows the connections between the BTS3012 main cabinet group and two BTS312 extension cabinet groups. In the hybrid cabinet groups of the BTS3012 and the BTS30, one extension cabinet group consists of a maximum of 3 combined cabinets; therefore, the hybrid cabinet groups support a maximum of 60 TRXs (one BTS30 cabinet supports a maximum of six TRXs). In the hybrid cabinet groups of the BTS3012 and the BTS312, one extension cabinet group consists of a maximum of 2 combined cabinets; therefore, the hybrid cabinet groups support a maximum of 72 TRXs (one BTS312 cabinet supports a maximum of 12 TRXs). The characteristics and limitations of hybrid cabinet groups are as follows: l Hybrid cabinet groups can have at most two types of cabinets. The cabinets in the main cabinet group must be the BTS3012 cabinets. The cabinets in extension cabinet groups can be the BTS30 or BTS312 cabinets. The TRXs in the cabinets of different types can be configured for one cell. The TRXs serving one cell can be located in the hybrid BTS3012 and BTS30 cabinet groups or in the hybrid BTS3012 and BTS312 cabinet groups. Cabinets of different types of BTSs can be configured as cabinet groups but cannot be combined. That is, the BTS3012 cabinet cannot be combined with the BTS30 or BTS312 cabinet.
Figure 2-50 Connections of hybrid cabinet groups of the BTS3012 and the BTS30
Issue 08 (2011-09-30)
297
Figure 2-51 Connections of hybrid cabinet groups of the BTS3012 and the BTS312

The configuration principles of combined cabinets and cabinet groups are as follows: l l l Minimum number of antennas The number of antennas should be as few as possible to save cost. Minimum number of cabinets The number of cabinets should be as few as possible to save cost. Complete synchronous cell All the TRXs of one synchronous directional cell should be configured in one cabinet to facilitate radio frequency cable connections. Although the TRXs of one synchronous directional cell can be located in two cabinets or cabinet groups, it is not the recommended configuration.
2.20.5 Parameters
None.
2.20.6 Counters
None.
2.20.7 Glossary

This chapter lists the reference documents related to BTS Combined Cabinets and Cabinet Groups. l
Issue 08 (2011-09-30)
BSC6900 Feature List

BSC6900 Basic Feature Description
2.21 BTS Ring Topology

2.21.1 Introduction
2.21.1.1 Scope
This document describes the BTS ring topology feature of Huawei GBSS, it covers the functions of and technologies related to this feature, including networking modes, application scenarios, BTS ring topology categories, and switchover modes. Also, this document describes the impact of BTS ring topology.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BTS ring topology feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02(2009-09-30)
01(2009-06-30)
2.21.2 Overview
Currently, the chain topology and tree topology are widely used. For details, see the 2.61 Networking Modes. In these topologies, transmission resources are saved. When the upperlevel BTS is powered off or the transmission fault occurs, the lower-level BTSs cannot, however, work properly any more. Figure 2-52 shows a chain topology, if the connection at point A is broken, the services of all the BTSs in the chain are disrupted; if the connection at point B is broken, the services of BTS2 are disrupted. Figure 2-52 Chain topology
With large-sale deployment of the GSM network, requirement for maintainability and reliability of the network is high. The BTS ring topology is a special chain or star topology. All the BTSs and the BSC in this topology are connected to form a ring, as shown in Figure 2-53.
Issue 08 (2011-09-30)
300
Figure 2-53 BTS ring topology (1)
When a connection is broken, the BTSs that precede the breakpoint remain in the same topology, and the BTSs that follow the breakpoint form a chain in reverse direction. As shown in Figure 2-54, if the connection at point A is broken, then the BTSs in yellow form a new chain with the BSC. Figure 2-54 BTS ring topology when a connection is broken
For example, when the BTS topology changes from chain showed in Figure 2-52 to ring showed in Figure 2-55, if the connection at point C is broken, the services are not affected; if the connection at point A is broken, the link is switched over to the reverse direction; if the connection at point B is broken, BTS1 still works at the forward link and BTS2 works at the reverse link after the switchover.
Issue 08 (2011-09-30)
301
Figure 2-55 BTS ring topology (2)
NOTE
l Forward link refers to the link that carries the BTS data in the initial configuration of the ring topology. As shown in Figure 2-55, forward link refers to the link that consists of link A, link B, BTS1, and BTS2. Forward direction refers to the direction from the BSC to BTS1 and BTS2 along the forward link. l Reverse link refers to the link that is added between the lowest-level BTS and the BSC in the initial configuration (see link C in Figure 2-55). The reverse link is used when a link (link A or link B) in the forward link is broken. l For a BTS, the link that takes E1 port 0 as the input port is the forward link, and that takes E1 port 1 as the input port is the reverse link.
The highlight of the BTS ring topology is that when a connection is broken, the ring automatically breaks into two chains at the break point. In this way, the BTSs that precede and follow the break point can work normally; thus improving the robustness, reliability, and security of the system. In the chain topology, the network reliability is low; if operators need to improve the network reliability, ring topology is an effective solution. More transmission resources are needed in the ring topology. However, the cost does not increase much since extra transmission resources are reserved for each node in the actual network. But the number of BSC ports that are used is doubled.

2.21.3.1 Networking Modes
There are two networking modes for BTS ring topology. All the BTSs in the ring topology must work in the same transmission mode, that is, TDM transmission mode or HDLC transmission mode. Take the EIUa(Abis) as an example, if there are enough ports on one EIUa(Abis), the links can be connected to one EIUa(Abis), as shown in Figure 2-56. Figure 2-56 BTS ring topology (3)
Issue 08 (2011-09-30)
302
If the ports on one EIUa(Abis) are insufficient, the links can be connected to two EIUas(Abis) in the same BM subrack, as shown in Figure 2-57. Figure 2-57 BTS ring topology (different interface boards in one subrack are used)
2.21.3.2 Application Scenarios

Due to its strong self-healing capability, the ring topology is preferred if transmission links meet the requirements for establishing a ring-topology network, especially in the following scenarios: l l l l Big sites with high traffic volume. In these sites, the disruption of the transmission link will impact the services greatly. Network in multi-level cascading chain topology. The security and reliability of the network is enhanced if ring topology is used. Sites in mountainous areas or isolated islands where the transmission quality is unstable or the maintenance is difficult. The Abis transmission backup is recommended in the areas prone to earthquakes. When the active SDH transmission link is faulty due to a natural disaster, the GBSS automatically switches the terrestrial TDM transmission link over the Abis interface to a backup satellite transmission link, thus maintaining the normal operation of the network.
2.21.3.3 BTS Ring Topology Categories

The BTS ring topology is classified into two types, namely, BTS ring topology I and BTS ring topology II. The difference between the two types is that after transmission disruption, the reverse-link BTS is reinitialized in BTS ring topology I and thus the BTS services are interrupted; whereas the BTS services are not interrupted in BTS ring topology II.
BTS Ring Topology I

In BTS ring topology I, when a BTS is disconnected from the network, the BTS can be connected to the reverse link through automatic switchover. If the transmission is restored to the normal state after the BTS is connected to the reverse link, the link is not switched to the forward direction automatically. You can manually switch over the link to the forward direction. To enable BTS ring topology I, set Config Ring to Yes. Other parameters involved in BTS ring topology I are Ring I Wait Time Before Switch and Ring I Try Rotating Duration Time.
Ring I Wait Time Before Switch is set to avoid the switchover under intermittent link failure. After this parameter is set, the switchover is performed if the OML is not restored after a certain period. Ring I Try Rotating Duration Time is the waiting time for the OML to be set up at another port when the OML setup fails at a port. If both BTS ring topology I and flex Abis are enabled, set Flex Abis Mode to Flex Abis. For details, see 2.35 Flex Abis. When the transmission is normal, the timeslots can be assigned flexibly in both directions. The E1 resources of the forward link and the reverse link are used simultaneously rather than in backup mode, as shown in Figure 2-58. This protects transmission links from congestion and enhances the network resource utilization. Figure 2-58 Simultaneous transmission on the forward link and the reverse link
In BTS ring topology I, Abis transmission backup is supported. This is a solution in emergency scenarios. When the active SDH transmission link is faulty due to a natural disaster, the GBSS automatically switches transmission link to a backup satellite transmission link, thus maintaining the normal operation of the network. This function applies to Abis over TDM scenarios but not to Abis over IP scenarios. Abis transmission backup is an enhanced function added to BTS ring topology. In the normal ring topology, the transmission modes of the forward link and the reverse link are the same. In Abis transmission backup, the transmission modes of the forward link and of the reverse link are different. That is, the forward link uses terrestrial transmission and the reverse link uses satellite transmission, as shown in Figure 2-59. Figure 2-59 Network topology when Abis transmission backup is enabled
Set Transmission Mode to Terrestrial and Satellite. Abis transmission backup is developed on the basis of BTS ring topology I. To enable the Abis transmission backup function, you should
set Config Ring to Yes, and set appropriate values to Ring I Wait Time Before Switch and Ring I Try Rotating Duration Time.
BTS Ring Topology II

BTS ring topology II is optimized on the basis of BTS ring topology I. The difference between the two types is that after transmission disruption, the BTS in the reverse link is reinitialized in BTS ring topology I and thus the services are disrupted, while the services are not disrupted in BTS ring topology II. To enable BTS ring topology II, set Configure Ring II to Yes after BTS ring topology I is enabled. Other parameters are Ring II Wait Time Before Switch, Ring II Try Rotating Duration Time, and Ring II Rotating Penalty Time. Ring II Wait Time Before Switch is set to avoid the switchover under intermittent link failure. After this parameter is set, the switchover is performed if the OML is not restored after a certain period. Ring II Try Rotating Duration Time is the waiting time for the OML to be set up at another port when the OML setup fails at a port. Ring II Rotating Penalty Time is set to avoid the frequent switchover caused by intermittent link failure. After the transmission is switched over to a port and the OML is set up successfully, a switchover cannot be performed within the time specified by this parameter. In addition, set the parameters related to OMLs. The system detects the OMLs status according to the parameters T200, T203, and N200. T200 specifies the value of the retransmission timer. A retransmission timer is started each time a frame is transmitted. When a retransmission timer expires, state transition or other handling measures are performed. T203 specifies the maximum duration for no frame exchange in the link. N200 specifies the maximum retransmission times of the link.
NOTE
The HDLC ring topology is composed of the BTSs that operate in Abis transmission optimization mode. The HDLC ring topology applies only to ring topology II.
2.21.3.4 Switchover Modes Automatic Switchover After Link Disconnection

When a connection in the BTS ring topology is broken, the BTSs that follow the breakpoint automatically form a chain in the reverse direction. The automatic switchover after a connection is broken is a basic function of the BTS ring topology. Normally, all the BTSs in the ring topology form an ordinary forward link. If a connection is broken, all the BTSs that follow the breakpoint automatically form a chain in the reverse direction. When the reverse link is set up, the BTSs are initialized and then start to work. If the forward link is restored to a normal state and the reverse link is broken, the BTSs automatically switch over to the forward link. Before switchover, the BTSs need to wait for a certain period of time specified by Ring I Wait Time Before Switch or Ring II Wait Time Before Switch to prevent the switchover activated by intermittent OML disconnection. When a switchover from a forward link to a reverse link or from a reverse link to a forward link happens, a related alarm is generated.
Manual Switchover After Link Disconnection

When a connection is broken and a reverse link is set up, the BTS link cannot switch over to the forward direction automatically after the transmission in the forward link is restored. The
maintenance personnel, however, can forcibly switch over the link to the forward direction. When the transmission quality in the forward direction is poor, the maintenance personnel can manually switch over the link to the reverse direction. The transmission in the forward and reverse directions must work normally during manual switchover. The BTS is firstly connected to the specified port (port 0 for forward link, port 1 for reverse link); if the connection fails, the BTS is connected to another port. The BTS connections are set up separately to form a ring topology, and the OML of the lower-level BTSs can be set up only after the upper-level BTSs complete the transparent transmission and switching of the timeslot. In this case, the link in the ring cannot be set up at a time. When you switch over multiple BTSs at the same time, some BTSs may be set up in the original direction. Therefore, when you manually switch over the forward link to the reverse link, you must first switch over the highest-level BTS in the reverse direction. After a BTS is successfully connected in the reverse direction and is automatically initialized, you can continue with the next BTS. As shown in Figure 2-60, if the transmission quality of link A is poor, you should manually switch over BTS3, BTS2, and BTS1 in turn. When you switch over the reverse link to the forward link, you must switch over the BTSs form the highest-level to the lowest-level in the forward direction in turn until all the BTSs work in forward direction. As shown in Figure 2-60, if the transmission quality of link A is recovered, you should manually switch over BTS1, BTS2, and BTS3 to the forward link in turn. Figure 2-60 BTS ring topology (4)
NOTE
During manual switchover, the corresponding BTS is reset and related alarms are reported.

Specifications of BTS Ring Topology
Based on the actual physical links, a maximum of five levels of cascaded BTSs can be set up in the ring topology. In TDM transmission and HDLC transmission, port 0 and port 1 of the BTSs are used. The relation between the port number and link direction cannot be changed.
Impact on System Performance

l
Issue 08 (2011-09-30)
BTS ring topology I

If you manually switch over BTS ring topology I, the BTS is reset and thus the services of the BTS are affected. After a connection is broken, the BTSs that follow the break point are initiated and thus the services are affected. If flex Abis is enabled, the preemption of slave 16 kbit/s Abis sub-timeslots of the lowerlevel BTSs is not supported. Abis transmission backup is license-controlled. l BTS ring topology II The time for the switchover from the forward link to the reverse link, that is, from the disconnection of the physical link to the restoration of the RSL, is shorter than eight seconds.

l BTS ring topology I Abis over IP and OML backup are not supported. BTS ring topology I with flex Abis enabled has following limitations: Flex Abis must be enabled in all the BTSs, and only a single E1 link can be configured on the forward and reverse links. Abis bypass is not supported. The LAPD signaling link of 16 kbit/s is not supported. In satellite transmission, services are disrupted in switchover. l BTS ring topology II Abis over IPand OML backup are not supported. Flex Abis and Abis bypass are not supported. Only a single E1 link can be configured on the forward and reverse links. In satellite transmission, services are disrupted in switchover. l HDLC ring topology Hybrid networking of HDLC and TDM is not supported. Secondary link is not supported. The cabinets of the BTS30 or BTS312 cannot be used in cabinet groups. The configuration of exclusive timeslots is supported, but the configuration of monitoring timeslots is not supported. Flex Abis, Abis bypass, local switching, and the LAPD signaling link of 16 kbit/s are not supported. The conversion of the bearing modes, that is, the conversion from the HDLC ring topology to the TDM ring topology, is not supported. Timeslots cannot be manually allocated.
2.21.5 Parameters
This chapter describes the parameters related to BTS ring topology. For the meaning of each parameter, see Table 2-37. For the default value, value ranges, and MML commands of each parameter, see Table 2-38.
Table 2-37 Parameter description (1) Parameter Config Ring Ring I Wait Time Before Switch Ring I Try Rotating Duration Time Description Whether to enable the BTS to support ring networking. IP BTS does not support this parameter. Waiting time before establishing a link in the reverse direction after the transmission of a BTS is disrupted. The BTS repeatedly attempts to connect to port 0 or port 1 after the switchover. If the connection on one port fails within the time specified by this parameter, the BTS tries to connect to another port. Service timeslot assignment mode for the BTS. If this parameter is set to FIX_16K_ABIS, the BSC6900 assigns a fixed Abis transmission timeslot to a TCH. If this parameter is set to FLEX_ABIS, the BSC6900 assigns an Abis transmission timeslot dynamically to a TCH (except the static PDCH) to increase the resource utilization. If this parameter is set to SEMI_ABIS, the BTS to which a TCH belongs assigns a fixed Abis transmission timeslot to the TCH while the upper-level BTS set to FLEX_ABIS assigns an Abis transmission timeslot dynamically to the TCH. This mode applies where old and new BTSs are cascaded. HDLC and IP BTS is not support this parameter. E1 transmission type of the Pb interface. The terrestrial transmission or satellite transmission can be selected. In the areas such as desert and lake where the terrestrial transmission is difficult, the satellite transmission can be used. Ring II function switch. The parameter should be set to "YES" when the ring II function is enabled. To avoid intermittent blinking, the switchover cannot be performed over a certain period of time when the OML is disconnected. That period of time is specified as ring II wait time before switch. If the OML is not established at one port after a period of time, the OML switches to another port and tries to connect to this port. That period of time is called ring II rotating duration time. When the OML is switched to a port where the connection is successfully established, the switchover cannot be performed over a certain period of time, which is specified as ring II rotating penalty time. In this manner, frequent switchover between the ports due to intermittent blinking can be avoided. Timer in the LAPD protocol. The value of the timer indicates the time when the LAPD link waits for the response or acknowledgement frame after sending the command frame. Timer in the LAPD protocol. The value of the timer indicates the maximum duration for no frame exchange in the LAPD link.
Flex Abis Mode
Transmission Mode Configure Ring II Ring II Wait Time Before Switch Ring II Try Rotating Duration Time
Ring II Rotating Penalty Time
T200 T203
Issue 08 (2011-09-30)
308
Parameter
Description System parameter in the LAPD protocol. The value of this parameter specifies the maximum number of times when a frame is retransmitted.
N200
Table 2-38 Parameter description (2) Paramete r Config Ring Ring I Wait Time Before Switch Ring I Try Rotating Duration Time Default Value GUI Value Range NO(No), YES(Yes) Actual Value Range NO, YES Unit MML Comman d ADD BTS (Optional) SET BTSRING ATTR (Optional) SET BTSRING ATTR (Optional) Impact
NO
None
BTS
90
60~300
60~300
BTS
90
60~300 FIX_16K_ ABIS(Fix Abis), FLEX_A BIS(Flex Abis), SEMI_AB IS (Semisolid Abis) TRRS (Terrestria l Transmiss ion), SATEL (Satellite Transmiss ion)
60~300
BTS
Flex Abis Mode
FIX_16K_ ABIS
FIX_16K_ ABIS, FLEX_A BIS, SEMI_AB IS
None
ADD BTS (Optional)
BTS
Transmiss ion Mode
None
TRRS, SATEL
None
ADD PBE1T1 (Optional) SET BTSRING ATTR (Optional)
PBE1T1
Configure Ring II
NO
NO(No), YES(Yes)
NO, YES
None
BTS
Issue 08 (2011-09-30)
309
Paramete r Ring II Wait Time Before Switch Ring II Try Rotating Duration Time Ring II Rotating Penalty Time
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET BTSRING ATTR (Optional) SET BTSRING ATTR (Optional) SET BTSRING ATTR (Optional) SET BTSRING ATTR (Optional) SET BTSRING ATTR (Optional) SET BTSRING ATTR (Optional)
Impact
0~255
0~255
BTS
60
10~255
10~255
BTS
0~255
0~255
BTS
T200
12
6~240
60~2400 (step: 10)
ms
BTS
T203
1~10
1~10
BTS
N200
1~3
1~3
None
BTS
2.21.6 Counters
None.
2.21.7 Glossary

l l l l l
Issue 08 (2011-09-30)
BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.22 Cell Broadcast

2.22.1 Introduction
2.22.1.1 Scope
This document describes the cell broadcast feature of Huawei GBSS. It covers the two technologies related to the cell broadcast, including standard cell broadcast and simple cell broadcast. The document also describes the basic information about cell broadcast messages.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the cell broadcast feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.22.2 Overview
The Short Message Service Cell Broadcast (SMSCB), cell broadcast service (CBS) for short, refers to the information broadcast service for the MSs in the idle state within a specified area known as the cell broadcast area.
NOTE
The cell broadcast area may be comprised of one or more cells, or may be comprised of the entire public land mobile network (PLMN). Individual cell broadcast messages will be assigned their own geographical coverage areas by mutual agreement between the information provider and the telecom operator.
Similar to the point-to-point short message service, the cell broadcast service is a method of sending the text message to the MS. The differences between the point-to-point short message service and the cell broadcast service are as follows: l The point-to-point short message service sends the short message to a specified MS, whereas the cell broadcast service broadcasts the cell broadcast message to all the MSs in the idle state within the cell broadcast area. The point-to-point short message service requires the response from the MS, whereas the cell broadcast service requires no response from the MS. The point-to-point short message service is bi-directional and can be sent by both the network and the MS, whereas the cell broadcast service is unidirectional and can only be sent by the network. In the point-to-point short message service, the message is initiatively sent by the network; in the cell broadcast service, the cell broadcast message is broadcast by the network on the CBCH, and the MS is scheduled to receive the message on the CBCH at a fixed time.
l l
The cell broadcast service provides a message broadcasting mechanism in which the cell broadcast message is broadcast to the MSs within the cell broadcast area. The MS need not respond to the cell broadcast message. Through this mechanism, the telecom operators can provide some feature services, such as weather information, road traffic information, and social commonweal information, for the users. In addition, the cell broadcast service can broadcast data for other services. When the AssistedGPS (A-GPS) location service is performed, for example, the BSC sends the location information to the MS through the cell broadcast service. The cell broadcast service can also provide the Over The Air (OTA) download service. Using fewer resources, these functions of the cell
broadcast service can provide information for the MSs, thus significantly conserving the radio resources. To implement the cell broadcast service on the GSM network, the existing functional units on the GSM network should be modified, and new network functional units should be added. The cell broadcast system consists of the CBE, CBC, BSC, BTS, and MS, as shown in Figure 2-61. Figure 2-61 Structure of the cell broadcast system
The CBE acts as a bridge between the source of the message and the GSM network. It is responsible for the input, encoding, and formatting of the cell broadcast message. The CBC is the scheduling center of the cell broadcast service. The CBC collects the formatted cell broadcast messages from the CBE, stores them, and then transmits the messages to the specified BSC according to the scheduling information for the cell broadcast message. In addition, the CBC is also responsible for the management of the cell broadcast messages being broadcast by the BSC, including the deletion of the out-dated message and the query of the status of the cell and of the cell broadcast message being broadcast. The BSC is responsible for the scheduling and maintenance of the cell broadcast messages being broadcast. In addition, the BSC is also responsible for the maintenance of the CBCH status. The BTS is responsible for the scheduling of the cell broadcast messages over the Um interface. The MS is responsible for the receiving and displaying of the cell broadcast message. To reduce the cost, increase the integration of the BSC, and improve maintainability, the BSC provides a simple cell broadcast system. The simple cell broadcast system is integrated into the BSC. You can enter the cell broadcast information through the data configuration or MML command. Then, the BSC schedules this cell broadcast information to achieve the cell broadcast function. The information type is either text or binary command. Figure 2-62 shows the structure of the simple cell broadcast system.
Issue 08 (2011-09-30)
313
Figure 2-62 Structure of the simple cell broadcast system
Cell broadcast services are classified into the following types: l l l Common public information services, such as weather, news, stock market, exchange rate, and lottery information. Dedicated public information services, such as missing person notice, vehicle navigation information, and mobile service payment reminder. Advertising services, such as shopping mall, restaurant, and cinema information.

To implement cell broadcast, you should configure one CBCH in the cell. The CBCH is a logical channel. It shares a physical channel with the SDCCH. Thus, the configuration mode of the CBCH can be as follows: l l SDCCH/8+CBCH: This configuration mode is generally used in cells that require noncombined BCCH. BCCH+CCCH+SDCCH/4+CBCH: This configuration mode is generally used in cells that require combined BCCH.
To configure SDCCH/8+CBCH, set Channel Type to SDCCH+CBCH; to configure BCCH +CCCH+SDCCH/4+CBCH, set Channel Type to BCCH+CBCH.
Issue 08 (2011-09-30)
314

NOTE
Before setting Channel Type to SDCCH+CBCH, you should also set CCCH Blocks Reserved for AGCH to a value other than zero. If CCCH Blocks Reserved for AGCH is set to zero, the MS need stop listening to the PCH in order to receive the cell broadcast message on the CBCH. This act, however, may lead to the missing of the paging message on the PCH if there is a paging message for the MS. If CCCH Blocks Reserved for AGCH is set to a value other than zero, the MS can receive the cell broadcast message on the CBCH during the scheduling period of the AGCH, and thus the MS does not miss any paging message. You need not set CCCH Blocks Reserved for AGCH to a value other than zero before setting Channel Type to BCCH+CBCH. The SDCCH+CBCH can only be configured on a timeslot from TS0 to TS3 of the carrier. The BCCH +CBCH can only be configured on TS0 of the carrier. If the CBCH is configured on a timeslot that joins in FH, a maximum of only 32 frequencies configured on this timeslot can join in FH due to the restriction of the coding scheme.
The MS can obtain the information about the CBCH configured in the cell from System Information 4 broadcast on the BCCH. Then, the MS can receive the cell broadcast message on the specified CBCH at a fixed time. The BSC sends a cell broadcast message to the BTS through the SMS BROADCAST COMMAND message. The BTS, then, fragments the message into four and broadcasts them one by one over the Um interface on the CBCH, as shown in Figure 2-63. Figure 2-63 Procedure for sending the cell broadcast message
To decrease the power consumption of the MS, the Discontinuous Reception (DRX) function is introduced in the cell broadcast service. After the DRX function is enabled, the BSC always sends a scheduling message before sending the formal cell broadcast message. The scheduling message describes the message to be broadcast on the CBCH. Depending on the scheduling message received, the MS determines the cell broadcast message in which the MS is interested and the specific time to receive it. The MS does not receive the cell broadcast message in which the MS is not interested. To enable the DRX function, you should first set SMCBC DRX to Yes. Then, the CBC can send the scheduling message through the SET DRX primitive.
NOTE
The simple cell broadcast service does not support the DRX function.
Issue 08 (2011-09-30)
315
2.22.3.2 Cell Broadcast Messages

Cell broadcast messages are comprised of pages. A cell broadcast message may contain up to 15 pages. Each page is comprised of 82 octets. The number of characters contained in each page of the cell broadcast message depends on the coding scheme adopted. l l When the cell broadcast message adopts the 7-bit coding scheme, a page of the cell broadcast message may contain up to 93 English characters. When the cell broadcast message adopts the UCS-2 coding scheme, a page of the cell broadcast message may contain up to 41 characters as each character takes up two octets.
The coding scheme is broadcast to the MS through the cell broadcast message. The cell broadcast message uses the Message Identifier to indicate the different sources of the message, such as the weather information and A-GPS location information. The MS can subscribe to the cell broadcast message of a particular Message Identifier. The subscription information is stored on the Subscriber Identity Module (SIM). For the cost-free cell broadcast messages, users can configure whether to receive them on the MS. The charging cell broadcast messages, however, should be set on the SIM by the telecom operator after the signing of the service subscription agreement. When broadcasting the cell broadcast message, the BTS incorporates the Message Identifier to the first fragment of the cell broadcast message. The MS, after receiving the first fragment, extracts the Message Identifier and compares it with that in the subscription information stored on the SIM. If the Message Identifier is the same as that in the subscription information, it indicates that the user subscribes to the message. In this case, the MS continues to receive the other three fragments. During cell broadcast, a cell broadcast message is repeatedly broadcast over the Um interface to ensure that the MS that recently camps on the cell can receive the message. The repeated broadcast of a cell broadcast message, however, causes the MS camping on the cell to receive the cell broadcast message for multiple times. To prevent this situation, the Serial Number is used in the cell broadcast message. The MS determines whether a cell broadcast message is a new message based on the Serial Number of the message. If the cell broadcast message is the same as the one the MS received, the MS will not receive this cell broadcast message. The Serial Number is also carried in the first fragment of the cell broadcast message. The advantages of cell broadcast services are as follows: (1) All MSs (including roaming MSs) around the BTSs capable of sending broadcast messages can receive short messages with the same contents at the same time. (2) A message can be broadcast repeatedly. Therefore, MSs that just enter the broadcast area can receive the message and MSs that have received the message do not receive it again. Compared with the point-to-point short message service, the cell broadcast service is more cost-effective because messages are sent to a large number of MSs in a specified area.
2.22.3.3 Standard Cell Broadcast

When Support Cell Broadcast is set to Support Standard Cell Broadcast, the BSC provides the standard cell broadcast service. In this case, you should specify the CBC information for the connection between the BSC and the CBC. The CBC information to be specified includes BSC IP, BSC Port, BSC GateWay IP, CBC ITF Para, CBC IP, CBC Port, and Mask. Among them, CBC ITF Para is used for interface adaptation when the BSC is connected to the CBC of a different vendor.
A functional BSC is connected to the CBC. Then, the BSC starts to process the primitives sent from the CBC. The main tasks performed by the BSC are as follows: l l l l l l Schedules a cell broadcast message or broadcasts a cell broadcast message to the specified cell as indicated by the Write-Replace primitive. Deletes the cell broadcast messages that are being processed or that have been processed by the BSC as indicated by the Kill primitive. Responds to the cell status query primitive and message status query primitive from the CBC. Responds to the SET DRX primitive, and generates and broadcasts the scheduling messages. Informs the CBC of the cell status after the status of a cell is changed. Deletes the cell broadcast message that is being broadcast in a cell as indicated by the Reset primitive.
The standard cell broadcast service is able to collect and schedule a large number of cell broadcast messages. Therefore, the standard cell broadcast service is recommended. CBC network topology
The cell broadcast system consists of the following parts: l Cell broadcast entity (CBE): A CBE consists of several cell broadcast terminals (CBTs). The CBE is a CBC-related application service responsible for initiating the short message broadcast service. For example, as a content provider, the CBE can function as news radio, traffic radio, financial information radio, and so on. Cell broadcast center (CBC): A CBC is the major part of the cell broadcast system. It is responsible for handling, scheduling, and storing broadcast messages, and for operating, maintaining, and managing the cell broadcast system. A CBC can be connected to multiple CBEs. CBCs are maintained and managed by mobile operators. Base station controller (BSC): A BSC is connected to only one CBC but can be connected to multiple BTSs. The BSC is responsible for storing, scheduling, and transmitting broadcast messages. Base transceiver station (BTS): A BTS is responsible for receiving cell broadcast messages from the BSC and sending these messages to MSs over the Um interface.
Issue 08 (2011-09-30)
Mobile station (MS): An MS is responsible for receiving cell broadcast messages over the Um interface and displaying these messages. MSs can receive broadcast messages only after subscribers enable the function of receiving broadcast messages and activate relevant broadcast channels on the MSs.
2.22.3.4 Simple Cell Broadcast

The simple cell broadcast provides the simple cell broadcast service without the CBC system. The broadcast information includes the cell name, weather information, and social commonweal information. To enable the simple cell broadcast service, you should set Support Cell Broadcast to SPPRTSIMPLE(Support Simple CB). The simple cell broadcast message type is text and binary The simple cell broadcast provides two types of functions: cell name broadcast and cell broadcast. The cell name broadcast enables the BSC to send a one-page-long text message to the MSs in a cell under the BSC. The text message contains the cell name. Thus, when a roaming MS enters a new cell where the simple cell broadcast function is enabled, the MS can obtain and display the cell name. This function equates to the simple location service. The BSC will keep sending the one-page-long message, but MS users can disable this function on the MS to stop the receiving of this message. To enable the cell name broadcast function, you should first set Support Cell Broadcast Name to Yes and then specify parameters such as Broadcast Content (this parameter is set to the cell name by default), Geography Scope, Chan ID, Coding Scheme, and Broadcast Interval. You can also run the ADD GSMSCB command to send a cell broadcast message to the BSC. If you send the cell broadcast message in such a way, you should specify Start Time and End Time of the period during which the cell broadcast message is broadcast. The maximum size of the cell broadcast message that can be sent through the MML command is 15 pages. A cell can save a maximum of 63 pages of cell broadcast messages. In addition, you can run the DSP GSMSCB command to query the cell broadcast messages saved in a cell; you can also run the RMV GSMSCB command to stop the broadcast of a cell broadcast message.
CAUTION
l The simple cell broadcast cannot be used with the cell broadcast provided by the CBC. They are mutually exclusive. l The simple cell broadcast provides only simple cell broadcast services. The standard cell broadcast system is recommended for the dynamic information that is frequently changed.
2.22.4 Parameters
This chapter describes the parameters related to cell broadcast. For the meaning of each parameter, see Table 2-39. For the default value, value ranges, and MML commands of each parameter, see Table 2-40.
Table 2-39 Parameter description (1) Parameter Description In the case of half-rate networking, each TRX maintains high RSL traffic. Therefore, the LAPD signaling link multiplexing ratio at the Abis interface is up to 2:1. In the case of half-rate networking, each E1 supports up to 13 TRXs. If the LAPD signaling links are unmultiplexed, each E1 supports fewer TRXs. BS-AG-BLKS-RES, indicating the number of the CCCH message blocks reserved for the AGCH. After the CCCHs are configured, the value of this parameter indicates the actual seizure rates of the AGCHs and the PCHs over the CCCHs. Whether to support the discontinuous reception mechanism (DRX). To reduce the power consumption, the DRX is introduced into the GSM Specification. MSs supporting the DRX can consume less power to receive interested broadcast messages. This prolongs the service time of MS batteries. BSCs supporting the DRX must send scheduling messages to MSs so that the MSs can use the DRX function. The period occupied by broadcast messages that are contained in a scheduling message is called a scheduling period. In the sending sequence, a scheduling message contain the description of each short message to be broadcasted and the position of each broadcast message in the scheduling period. This parameter specifies whether the BSC6900 supports the cell broadcast function and whether the BSC6900 supports simple cell broadcast or standard cell broadcast. If the BSC6900 supports standard cell broadcast, the BSC6900 should be connected to the CBC. IP address of the BSC. If the connection mode of the BSC and the CBC is to lead cables out of the PIU, the value of this parameter must be the same as the preset IP address of the PIU port. If the connection mode is to lead cables out of the XPU panel, the value of this parameter must be the same as the preset IP address of the XPU panel. Port number used for the communication between the BSC6900 and the CBC Gateway IP address of the BSC6900. When the BSC provides the function of simple cell broadcast, the BSC6900 sends cell broadcast messages through this IP address defined by this parameter.
Channel Type
CCCH Blocks Reserved for AGCH
SMCBC DRX
Support Cell Broadcast
BSC IP BSC Port
BSC GateWay IP
Issue 08 (2011-09-30)
319
Parameter
Description CBC interface parameter, whose setting should be adjusted according to the actual situations. The value of this parameter must be translated into binary digits. The following describes each bit of the value: Bit 0: phase flag. The value 0 indicates phase II+; the value 1 indicates phase II. Bit 1: message type flag. The value 0 indicates littleendian; the value 1 indicates big-endian. Bit 2: whether to carry the number of cells in the cell-list information element. The value 0 indicates that the number of cells is not carried in the cell list information element; the value 1 indicates that the number of cells is carried in the cell list information element. Bit 3: whether to carry a recovery indication. The value 0 indicates the recovery indication is not carried in the restart-indication message; the value 1 indicates that the recovery indication is carried in the restart-indication message. Bit 4: whether the bsc supports repetitive message references. The value 0 indicates that the bsc supports repetitive message references; the value 1 indicates that the bsc does not support repetitive message references. Bit 5: content of the recovery indication in the restart-indication message during the reset procedure. The value 0 indicates that the data is lost; the value 1 indicates that the data is available. IP address of a CBC Port number at the CBC side in the communication with the BSC6900 Subnet mask of the CBC Whether to add a simple cell broadcast message for broadcasting the cell name. This parameter is only used for control broadcasting cell name, not used for control CB service. Contents of a cell broadcast message Geographical coverage of a simple cell broadcast message. You can run "DSP GSMSCB" to query and obtain the information. This parameter, "Code", and "Update" uniquely specify a cell broadcast message. Message Identifier of a simple cell broadcast message. This is a key parameter for adding a simple cell broadcast message. You can use "DSP GSMSCB" to query and obtain the value of this parameter. A key parameter that indicates the coding scheme of a simple cell broadcast message Time interval for a cell broadcast message
CBC ITF Para CBC IP CBC Port Mask
Support Cell Broadcast Name Broadcast Content
Geography Scope
Chan ID Coding Scheme Broadcast Interval
Issue 08 (2011-09-30)
320
Parameter Start Time
Description A key parameter that indicates the date and time when the BSC broadcasts cell messages End date and time of a broadcast message. This is a key parameter for identifying a simple cell broadcast message. You can use "DSP GSMSCB" to query and obtain the value of this parameter.
End Time
Issue 08 (2011-09-30)
321
Table 2-40 Parameter description (2) Paramete r Default Value GUI Value Range TCHFR (TCH Full Rate), TCHHR (TCH Half Rate), SDCCH8 (SDCCH8 ), MBCCH (Main BCCH), CBCCH (Combine d BCCH), BCH (BCH), BCCH_C BCH (BCCH +CBCH), SDCCH_ CBCH (SDCCH +CBCH), PBCCH_P DTCH (PBCCH +PDTCH) , PCCCH_P DTCH (PCCCH +PDTCH) , PDTCH (PDTCH), DPDCH (Dynamic PDCH) Actual Value Range Unit MML Comman d Impact
Channel Type CCCH Blocks Reserved for AGCH
None
TCHFR, TCHHR, SDCCH8, MBCCH, CBCCH, BCH, BCCH_C BCH, SDCCH_ CBCH, PBCCH_P DTCH, PCCCH_P DTCH, PDTCH, DPDCH
None
SET GTRXCH AN (Optional) SET GCELLID LEBASIC (Optional) SET GCELLO THEXT (Optional)
Physical channel
0~7
0~7
None
Cell
SMCBC DRX
Issue 08 (2011-09-30)
YES
NO(No), YES(Yes)
NO, YES
None
Cell
322
Paramete r
Default Value
GUI Value Range NOTSPP RTBC (NotSupp ort CB), SPPRTST ANDARD (SupportSt andard CB), SPPRTSI MPLE (SupportSi mple CB)
Actual Value Range
Unit
MML Comman d
Impact
Support Cell Broadcast
NOTSPP RTBC
NOTSPP RTBC, SPPRTST ANDARD , SPPRTSI MPLE
None
ADD GCNOPE RATOR (Optional) ADD GCBSAD DR (Mandator y) ADD GCBSAD DR (Mandator y) ADD GCBSAD DR (Mandator y) ADD GCBSAD DR (Optional) ADD GCBSAD DR (Mandator y) ADD GCBSAD DR (Mandator y)
BSC
BSC IP
None
None
0.0.0.0~25 5.255.255. 255
None
BSC6900
BSC Port
None
0~65535
0~65535
None
BSC
BSC GateWay IP
None
None
0.0.0.0~25 5.255.255. 255
None
BSC
CBC ITF Para
30
0~63
0~63
None
BSC
CBC IP
None
None
0.0.0.0~25 5.255.255. 255
None
BSC
CBC Port
None
0~65535
0~65535
None
BSC
Issue 08 (2011-09-30)
323
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d ADD GCBSAD DR (Mandator y) SET GCELLS BC (Optional) SET GCELLS BC (Optional) SET GCELLS BC (Optional) ADD GSMSCB (Mandator y) SET GCELLS BC (Optional) ADD GSMSCB (Mandator y)
Impact
Mask Support Cell Broadcast Name
None
None
0.0.0.0~25 5.255.255. 255
None
BSC
NO
NO(No), YES(Yes)
NO, YES
None
Cell
Broadcast Content
Cell name
None LAC_CI (CELL IMME), PLMN (ALL), LAC (LAC), CI (CELL)
1~80 characters
None
Cell
Geograph y Scope
None
LAC_CI, PLMN, LAC, CI
None
Cell
Chan ID
None
0~65535
0~65535
None
Cell
Issue 08 (2011-09-30)
324
Paramete r
Default Value
GUI Value Range GERMAN (GERMA N), ENGLISH (ENGLIS H), ITALIAN (ITALIA N), FRENCH (FRENCH ), SPANISH (SPANIS H), DUTCH (DUTCH), SWEDIS H (SWEDIS H), DANISH (DANISH ), PORTUG UESE (PORTUG UESE), FINNISH (FINNISH ), NORWE GIAN (NORWE GIAN), GREEK (GREEK), TURKISH (TURKIS H), HUNGAR IAN (HUNGA RIAN), POLISH (POLISH) , GB2312 (GB2312),
Actual Value Range GERMAN , ENGLISH , ITALIAN, FRENCH, SPANISH , DUTCH, SWEDIS H, DANISH, PORTUG UESE, FINNISH, NORWE GIAN, GREEK, TURKISH , HUNGAR IAN, POLISH, GB2312, KOI8-R, KOI8-U, KOI8, WINDO WS-1251, ASMO_4 49, WINDO WS-1256, WINDO WS-874, WINDO WS-1253, WINDO WS-1254, WINDO WS-1255, WINDO WS-1257, WINDO WS-1250, WINDO WS-1252, BINARY, UCS2,
Unit
MML Comman d
Impact
Coding Scheme
None
None
SET GCELLS BC (Optional) ADD GSMSCB (Mandator y)
Cell
Issue 08 (2011-09-30)
325
Paramete r
Default Value
GUI Value Range KOI8-R (Cyrillic KOI8-R), KOI8-U (Cyrillic KOI8-U), KOI8 (Cyrillic KOI8), WINDO WS-1251 (Cyrillic Windows) , ASMO_4 49(Arabic ASMO), WINDO WS-1256 (Arabic Windows) , WINDO WS-874 (Thai Windows) , WINDO WS-1253 (Greek Windows) , WINDO WS-1254 (Turkish Windows) , WINDO WS-1255 (Hebrew Windows) , WINDO WS-1257 (Baltic Windows) , WINDO
Actual Value Range
Unit
MML Comman d
Impact
RCS-1, RCS-2, RCS-3, RCS-4, RCS-5
Issue 08 (2011-09-30)
326
Paramete r
Default Value
GUI Value Range WS-1250 (Eastern European Windows) , WINDO WS-1252 (Western European Windows) , BINARY (BINARY ), UCS2 (UCS2), RCS-1 (Reserved Code Scheme 1), RCS-2 (Reserved Code Scheme 2), RCS-3 (Reserved Code Scheme 3), RCS-4 (Reserved Code Scheme 4), RCS-5 (Reserved Code Scheme 5)
Actual Value Range
Unit
MML Comman d
Impact
Broadcast Interval
None
2~3600 year, month, day, hour, min, sec year, month, day, hour, min, sec
2~3600 1970-1-1 00:00:00~ 2538-12-3 1 23:59:59 1970-1-1 00:00:00~ 2538-12-3 1 23:59:59
SET GCELLS BC (Optional) ADD GSMSCB (Mandator y) ADD GSMSCB (Mandator y)
Cell
Start Time
None
None
Cell
End Time
None
None
Cell
Issue 08 (2011-09-30)
327
2.22.5 Counters
2.22.6 Glossary

l l l l l l l l l 3GPP TS 04.12: "Short Message Service Cell Broadcast (SMSCB) Support on the Mobile Radio Interface" 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)" 3GPP TS 27.005: "Use of Data Terminal Equipment - Data Circuit terminating Equipment (DTE-DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.23 Channel Management

2.23.1 Introduction
2.23.1.1 Scope
This document describes the processing procedures of the Huawei channel allocation algorithm in typical scenarios.

It is assumed that users of this document are familiar with GSM basics and have a working knowledge of GSM telecommunication. This document is intended for: l l
Issue 08 (2011-09-30)

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the channel management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.23.2 Overview
Channel management is a feature that manages all the radio channels. It uses the Huawei channel allocation algorithm to allocate a suitable channel to the radio service and to adjust the channel as required. Reasonable channel management guarantees not only the QoS for a single subscriber but also the performance of the entire network. The channel to be allocated can be a Stand-alone Dedicated Control Channel (SDCCH), a Traffic Channel (TCH), or a Packet Data Channel (PDCH).
Each TCH and each SDCCH is assigned a set of priorities. They are allocated in the order of priority on the basis of the current channel resource usage. In this way, an available channel with the highest priority is allocated. In addition, the BSC adjusts the channel rate and converts the channels of different types based on the channel resource usage.
NOTE
This document describes only the channel management in the circuit switched (CS) domain. For the description of the channel management in the packet switched (PS) domain, see 2.40 GPRS/EGPRS Channel Management.
Based on the service requirements and the current cell load, full-rate TCHs (TCH/Fs) or halfrate TCHs (TCH/Hs) are allocated flexibly. This not only meets the communication requirements of the subscribers but also increases the bandwidth efficiency of the radio channels. The number of TCH/Fs and the number of TCH/Hs are flexibly adjusted to strike a balance between network quality and network capacity.
NOTE
For details on the adjustment between TCH/F and TCH/H and the conversion from or to SDCCH, see 2.28 Dynamic Channel Conversion.

2.23.3.1 Channel allocation procedure
The Base Station Controller (BSC) needs to allocate a suitable channel in the following situations: l l l a mobile station (MS) initiates a call (immediate assignment); an MS needs to access a TCH for speech, after a channel for signaling is allocated (assignment); an MS needs to be handed over to another channel (handover, including the intra-BSC handover, inter-BSC handover, and inter-RAT handover).
When the MS initiates a new call, an SDCCH or a TCH has to be allocated according to the call establishment cause. In this case, the TCH is used to carry signaling. After receiving the channel request from the MS, the Mobile Switching Center (MSC) instructs the BSC through the Assignment Request message to allocate a suitable channel to the MS. The channel to be allocated must meet the requirements of the MSC and MS, such as the channel type, speech version, and MS frequency capability. During a call, if the MS has to change from one channel to another due to the receive quality, receive level, timing advance (TA), or load, the BSC needs to allocate a suitable channel to the call. The channel to be allocated must meet the call requirements, such as the requirements for frequency and interference. Within a cell, more than one channel can be chosen. In addition, in different channel allocation procedures, the principles and conditions of selecting a channel are different. Therefore, the Huawei channel allocation algorithm specifies a set of priorities for each channel. When channel allocation is required, the BSC refreshes the priorities based on the channel type required by the call, and then allocates a most suitable channel selected from all the channels that meet the requirements. Figure 2-64 shows the procedure for the Huawei channel allocation algorithm.
Figure 2-64 Channel allocation procedure
2.23.3.2 Channel Allocation in the Immediate Assignment Procedure Immediate Assignment Procedure
In the immediate assignment procedure, the MS sends a Channel Request message to the network. The message contains the information element Establishment Cause. Based on the Establishment Cause, the BSC determines whether to allocate an SDCCH or a TCH. For example, if the Establishment Cause indicates an emergency call , the BSC preferentially allocates a TCH to the call. If the Establishment Cause indicates a paging response, the BSC preferentially allocates an SDCCH to the call.
Pre-Processing of Channel Allocation

In the immediate assignment procedure, the BSC is unaware of the MS frequency capability. To ensure the normal access of the MS, the SDCCH or TCH to be allocated must be in the compatible band of the BCCH. In a multi-band cell, the SDCCHs can be configured in both the compatible and incompatible bands of the BCCH. The BSC preferentially allocates the SDCCH in the compatible band of the BCCH, and then the SDCCH in the incompatible band of the BCCH. In this case, the MS may be allocated a channel in the frequency band that is not supported by the MS, thus causing access failure.
NOTE
The GSM900 band consists of the P-GSM900 band, E-GSM900 band, and R-GSM900 band. The RGSM900 band includes the frequencies in the P-GSM900 and E-GSM900 bands, and the E-GSM900 band includes the frequencies in the P-GSM900 band. If the BCCH TRX is configured in the R-GSM900 band, then the E-GSM900 and P-GSM900 bands are the compatible bands of the BCCH; if the BCCH TRX is configured in the E-GSM900 band, the P-GSM900 band is the compatible band of the BCCH.
2.23.3.3 Channel Allocation in the Assignment Procedure Assignment Procedure

In the assignment procedure, the MSC sends an Assignment Request or Voice Group Call Service(VGCS)/Voice Broadcast Service(VBS) Assignment Request message that contains the
information element Channel Type to the BSC. The Channel Type indicates the type of the required traffic channel (for speech or for data), channel rate, and speech version list. Based on the Channel Type, the BSC allocates a suitable channel to the call.
Pre-Processing of Channel Allocation

When the MSC specifies that the TCH/F or TCH/H is preferred, the BSC allocates a TCH/F or TCH/H to the call based on the following settings of TCH Rate Modify: l TCH Rate Modify is set to No. The BSC uses the channel rate assignment strategy controlled by the MSC. If the MSC specifies that the TCH/F is preferred, a TCH/F is allocated if there is an idle one in the cell and other conditions are met. If the MSC specifies that the TCH/H is preferred, a TCH/H is allocated if there is an idle one in the cell and other conditions are met. l TCH Rate Modify is set to Yes. The BSC uses the optimized strategy to determine the channel rate. That is, the BSC specifies the channel rate based on the channel resource usage. When the channel resource usage is high, that is, the network is busy, a TCH/H is preferably allocated; otherwise, a TCH/F is preferably allocated. If there are sufficient TCH/Fs, TCH/Fs are preferably allocated to guarantee the speech quality, irrespective of whether the MSC specifies the channel rate preferred. If there are insufficient TCH/Fs, TCH/Hs are preferably allocated to guarantee the network capacity, irrespective of whether the MSC specifies the channel rate preferred. If one of the following conditions is met, you can infer that the network is busy. The channel seizure rate exceeds TCH Traffic Busy Threshold.
NOTE
l Channel seizure rate = (number of busy full-rate channels + number of busy half-rate channels/2)/(number of available full-rate channels + number of available half-rate channels/ 2) x 100% l The number of available channels refers to the total number of busy and idle channels. The TCH/F and TCH/H include those that are configured as dynamic PDCHs but are not carrying any packet services.
NOTE
For the Adaptive Multi Rate (AMR) calls, the channel seizure rate exceeds AMR TCH/ H Prior Cell Load Threshold. In a concentric cell, when Load of UL-OL Cells Rate Select Allowed is enabled: For the calls in the overlaid subcell, the channel seizure rate of the overlaid subcell exceeds Tch Traffic Busy Overlay Threshold. For the calls in the underlaid subcell, the channel seizure rate of the underlaid subcell exceeds Tch Traffic Busy Underlay Threshold. When Flex Abis is enabled and TCHH Function Switch is set to Yes, the fixed Abis channel seizure rate exceeds Fix Abis Prior Choose Load Thred and the Flex Abis channel seizure rate exceeds Flex Abis Prior Choose Load Thred. When HR Allocation Flag is set to Open, the Ater resource usage exceeds Congestion Ratio on Ater Resource. To ensure the service quality of the network and to restrict the proportion of half-rate service users in the cell, during the channel allocation procedure, the BSC performs as follows
when a half-rate channel is preferred for the current call (not including the call that requests the half-rate channel only): When the proportion of half-rate service users in the cell exceeds Ratio of TCHH, the system does not allocate a half-rate channel. When the proportion of AMR half-rate service users in the cell exceeds Ratio of AMRHR, the system does not allocate an AMR half-rate channel. When allocating channels, the BSC determines whether to trigger rate adjustment based on the channel usage in the cell. To enable real-time rate adjustment, the channels after rate adjustment are allocated to the current call immediately. Based on the rate of the allocated channel and the speech version capability of the TRX that carries the channel, the BSC selects an appropriate speech version from the speech version list assigned by the MSC. In addition, during channel allocation, if the speech version list specified by the MSC includes the AMR, the BSC preferentially allocates a channel that supports the AMR. For example, the speech version list specified by the MSC includes the full-rate speech versions 3 and 1 and half-rate speech versions 3 and 1. l l l l If the allocated channel is of full rate and the TRX that carries the channel supports the AMR, the BSC selects the full-rate speech version 3, that is, AMR FR. If the allocated channel is of full rate and the TRX that carries the channel does not support the AMR, the BSC selects the full-rate speech version 1, that is, FR. If the allocated channel is of half rate and the TRX that carries the channel supports the AMR, the BSC selects the half-rate speech version 3, that is, AMR HR. If the allocated channel is of half rate and the TRX that carries the channel does not support the AMR, the BSC selects the full-rate speech version 1, that is, HR.
2.23.3.4 Channel Allocation in the Handover Procedure Incoming BSC Handover

For an incoming BSC handover, including the inter-BSC handover and the inter-RAT handover, the channel allocation procedure after the handover is the same as the channel allocation in the assignment procedure. The Handover Request message contains the information element Channel Type. The BSC allocates a suitable channel to the call after handover based on the channel rate and speech version list indicated in the Channel Type. For details, see 2.23.3.3 Channel Allocation in the Assignment Procedure.
Intra-BSC Handover
For an intra-BSC handover, including the intra-cell handover and inter-cell handover, the BSC allocates a new channel to the call to be handed over according to the MS frequency capability, current channel rate and speech version list of the call, channel type and speech version list required by the MSC, and handover cause. For example, if the ongoing call to be handed over supports the AMR, the BSC preferentially allocates a channel that supports the AMR to this call. If an intra-cell handover due to interference is required, the BSC preferentially allocates a channel on other TRXs to this call.
2.23.3.5 Huawei Channel Allocation Algorithm

?.1. Channel Priorities

According to the Huawei channel allocation algorithm, each channel is assigned a set of priorities. The BSC refreshes the priorities according to the TRX attributes, configured frequency, channel type required by the call, and characteristics of the call. During channel allocation, the BSC selects a channel with the highest priority from all the channels that meet the requirements and allocates it to the call. The following priorities are considered during channel allocation: l TRX priority TRX priority is used to preferentially allocate the channel on a TRX with a higher priority. For example, to reduce BTS power consumption, the TRX priority can be set and the channel on the Broadcast Control Channel (BCCH) TRX is preferably allocated to the call. TRX priority is specified by parameters TRX Priority and Allocation TRX Priority Allowed. l Frequency capability priority Frequency capability priority determines the frequency capability of the TRX. In a multiband cell, frequency capability priority is used to allocate the channel on a suitable TRX to the call. For example, if a cell is configured in the P-GSM900 and E-GSM900 bands, the BSC preferentially allocates the channel on the TRX in the E-GSM900 band to the MS that supports this band. This ensures more accesses to the cell and protects the MS that supports only the P-GSM900 band from access failure. l Concentric cell priority In a concentric cell, the concentric cell priority determines whether the channel in the underlaid subcell or overlaid subcell is allocated. l History occupation priority If call drops occur frequently on a channel serving the MS, the history occupation priority can be set to lower the priority of the channel. A channel without occurrence of call drops is preferably allocated, thus reducing the call drop rate. The history occupation priority is specified by History Record Priority Allowed. l Interference priority Interference priority is used to preferentially allocate a channel with lower interference to the call, thus improving the speech quality. The interference priority is specified by Interf. Priority Allowed. l TRX power-saving priority With the increasingly high TRX integration and the adoption of new power-saving technology, the TRXs produced in different periods differ in terms of power-saving. TRX power-saving priority is used to preferentially allocate a channel on an effectively powersaving TRX to the call, thus reducing the power consumption of the BTS. The TRX powersaving priority is specified by Power Priority Allowed. l PS coordination priority In GPRS/EGPRS, an MS can be allocated multiple successive timeslots. When the dynamic conversion between the PDCH and TCH is enabled, the current PDCH and adjacent TCHs are reserved, and other channels are allocated to the call. l
Issue 08 (2011-09-30)
IBCA(Interference Based Channel Allocation) priority

When the Interference Based Channel Allocation (IBCA) is enabled on the BSC, IBCA priority is used to allocate a channel with the lowest interference. l TCH rate priority When the cell supports the TCH/H, the TCH rate priority is used to allocate a channel of suitable rate to the call. For example, if the current call requires a TCH/H, the priority of the TCH/F is lowered and the priority of the TCH/H is raised. l AMR and frequency reuse priority The AMR has a higher anti-interference capability than other speech versions. In a cell with tight frequency reuse, the BCCH TRX is generally configured with the frequency in loose reuse, and other traffic TRXs are configured with frequencies in tight reuse. Therefore, the channel on the BCCH TRX is preferably allocated to the non-AMR call and the channel on the traffic TRX is preferably allocated to the AMR call, thus improving the average speech quality in the entire network. For details of preferentially allocating a channel on the BCCH TRX to the non-AMR call, see 2.23.3.5.3 Preferentially Allocating Channels on the BCCH TRX to Non-AMR Calls.
?.2. Channel Allocate Strategy

The Huawei channel allocation algorithm classifies the channel priorities into four types by the impact on the call. In different application scenarios, you can adjust the order of the priorities to better meet the networking requirements. The four types of priorities are as follows: l Capacity The capacity-related priority consists of the frequency capability priority, concentric cell priority, and TCH rate priority. These priorities mainly have an impact on the cell capacity. l Quality This quality-related priority consists of the history occupation priority, interference priority, IBCA priority, and AMR and frequency reuse priority. These priorities mainly have an impact on the speech quality in the cell. l PS coordination This type of priority refers to the PS coordination priority. It determines the coordination relationship between CS services and PS services in the GSM to guarantee the CS service capacity and PS service capacity in the cell. l Management The management-related priority consists of the TRX priority and TRX power-saving priority. These priorities are used for management purpose. In channel allocation, Channel Allocate Strategy is set to determine the order of the four types of priorities. The BSC defines the following strategies: l Capacity preferred Capacity > quality > PS coordination > management The strategy of capacity preferred is mainly applied to the network with loose frequency reuse. This strategy can increase the network capacity while ensuring the network quality. l Quality preferred Quality > capacity > PS coordination > management
This strategy is mainly applied to the network with tight frequency reuse to improve the network quality. l PS relatively preferred Capacity > PS coordination > quality > management The strategy of PS relatively preferred is applicable to the network with loose frequency reuse. When the capacity requirement takes precedence over the PS service requirement in the network, this strategy is applied. l PS absolutely preferred PS coordination > capacity > quality > management The strategy of PS absolutely preferred is applicable to the network with loose frequency reuse. When the PS service requirement takes precedence over the capacity requirement in the network, this strategy is applied.
NOTE
A > B indicates that channel priorities related to A are compared first, and then the channel priorities related to B.
?.3. Preferentially Allocating Channels on the BCCH TRX to Non-AMR Calls

In a network with tight frequency reuse, loose frequency reuse mode, such as 4 x 3, is generally applied to the BCCH TRX; tight frequency reuse mode, such as 1 x 3, is applied to the traffic TRX. The AMR has a higher anti-interference capability than the non-AMR, including the FR, EFR, and HR. Therefore, if the network supports the AMR and Assign Non-AMR User Loose Fre. Reuse TRX is set to Yes, the channel on the TRX where Frequency Reuse Mode is set to LOOSE, such as the BCCH TRX, is preferably allocated to the MS that does not support the AMR, and the channel on the TRX where Frequency Reuse Mode is set to TIGHT is allocated to MS that supports the AMR. In this way, the average speech quality in the entire network is improved. Frequency Reuse Mode of a TRX is determined in the network planning.
2.23.3.6 Post-Processing of Channel Allocation

After channel allocation, further processing is required on the basis of the allocation result, including selecting the suitable speech version, preemption, queuing, and channel type conversion. The typical scenarios after the processing of channel allocation are as follows: l l l l When the TRX that carries the allocated channel does not support the AMR, the BSC must select the full-rate speech version 1 or 2 for the call. If a call is not allocated a channel and the call supports preemption, the BSC performs preemption for the call. If a call is not allocated a channel and the call supports queuing, the BSC places the call in the queue. If a call requires a TCH/H but is allocated a TCH/F, the BSC must convert the TCH/F to the TCH/H.
2.23.4 Parameters
This chapter describes the parameters related to channel management.
For the meaning of each parameter, see Table 2-41. For the default value, value ranges, and MML commands of each parameter, see Table 2-42. Table 2-41 Parameter description (1) Parameter Description Whether the TCH rate type uses the MSC strategy or BSC strategy. When this parameter is set to NO and the MSC policy is used, the BSC preferentially selects full-rate or half-rate channels based on the rate type carried by the MSC in the assignment or incoming BSC handover request. When this parameter is set to YES and the BSC policy is used, the BSC preferentially selects full-rate or half-rate channels based on the internal load. If the current channel seizure ratio reaches or exceeds this value, the halfrate TCH is assigned preferentially; otherwise, the full-rate TCH is assigned preferentially. Load threshold for assigning half rate channels preferentially. If the current TCH seizure ratio of the cell is greater than this threshold, AMR half rate channels are assigned preferentially.
TCH Rate Modify TCH Traffic Busy Threshold AMR TCH/H Prior Cell Load Threshold Load of ULOL Cells Rate Select Allowed
Whether to enable the BSC to assign half or full rate channels to MSs according to the channel seizure ratio in the overlaid and underlaid subcells The BSC assigns channels in the overlaid subcell to the MS in a concentric cell. If the channel seizure ratio of overlaid subcell is greater than the value of this parameter, half-rate channels are assigned. Otherwise, full-rate channels are assigned. Channel seizure ratio = (Num. of busy TCHF + Num. of busy TCHH/2)/(Num. of available TCHF + Num. of available TCHH /2) x 100%. This parameter is valid for the concentric cell. When the "Allow Rate Selection Based on Overlaid/Underlaid Subcell Load" is set to Yes, the "TCH Traffic Busy Threshold (%)" is invalid for the concentric cell. Threshold for determining that the underlaid subcell is busy. The BSC assigns channels in the underlaid subcell to the MS in a concentric cell. When "Allow Rate Selection Based on Overlaid/Underlaid Subcell Load" is set to YES, half-rate channels are assigned if the channel seizure ratio in the underlaid subcell exceeds the value of this parameter, and full-rate channels are assigned if the channel seizure ratio in the underlaid subcell does not exceed the value of this parameter. This parameter specifies whether to enable the Abis resource adjustment TCHH function. It specifies whether the TCHH is preferentially allocated to the MS by the BSC6900, when Abis resources are insufficient. If the Abis resource load is greater than "Flex Abis Prior Choose Load Thred" or "Fix Abis Prior Choose Abis Load Thred" when the parameter is set to "YES", the BSC6900 preferentially allocates the TCHH to the MS.
Tch Traffic Busy Overlay Threshold
Tch Traffic Busy Underlay Threshold
TCHH Function Switch
Issue 08 (2011-09-30)
337
Parameter
Description This parameter specifies the static Abis resource load threshold. If the static Abis resource load is less than the static Abis resource load threshold, the TCHF is preferentially allocated. Otherwise, whether the TCHF or the TCHH should be preferentially allocated is determined by the dynamic Abis resource load. If the static Abis resource load is greater than the value of "Fix Abis Prior Choose Abis Load Thred" and the dynamic Abis resource load is greater than the value of this parameter, the half-rate channel is preferred. Otherwise, the full-rate channel is preferred. Whether to enable the BSC to assign half rate channels preferentially when the Ater interface is congested Threshold for considering the Ater interface, if congested, the BSC determines whether to assign full or half rate channels preferentially according to the congestion situations at the Ater interface. If the Ater resource usage exceeds this parameter, the Ater interface is considered congested. Maximum ratio of the number of half rate channels to the total number of channels in a cell. When the resource allocation principle is determined by the BSC, no half rate channel can be further assigned if the ratio of the number of half rate channels to the total number of channels in the cell is greater than or equal to the value of this parameter. When the resource allocation principle is not determined by the BSC, radio resource allocation does not depend on the setting of this parameter. Total number of channels = number of half rate channels + number of full rate channels x 2 Maximum ratio of the number of AMR half rate channels to the total number of channels in a cell. When the resource allocation principle is determined by the BSC, no AMR half rate channel can be further assigned if the ratio of the number of AMR half rate channels to the total number of channels in the cell is greater than or equal to the value of this parameter. When the resource allocation principle is not determined by the BSC, radio resource allocation does not depend on the setting of this parameter. Total number of channels = number of half rate channels + number of full rate channels x 2 This parameter specifies the TRX priority in channel assignment. The smaller this parameter is, the higher the TRX priority is. For two TRXs with other conditions identical, channels on the TRX with higher priority are preferentially assigned. This parameter specifies whether the TRX priority is considered during channel assignment. When the parameter is set to YES, the smaller the parameter "TRX Priority" in the command "SET GTRXDEV" is, the higher priority the TRX is. Under other conditions, channels are preferentially allocated from high-priority TRXs.
Fix Abis Prior Choose Load Thred Flex Abis Prior Choose Load Thred HR Allocation Flag
Congestion Ratio on Ater Resource
Ratio of TCHH
Ratio of AMR-HR
TRX Priority
Allocation TRX Priority Allowed
Issue 08 (2011-09-30)
338
Parameter History Record Priority Allowed Interf. Priority Allowed Power Priority Allowed
Description Whether to consider history priority records during channel assignment. If this parameter is set to YES, the history priority records are considered. If this parameter is set to NO, the history priority records are not considered.
Whether to consider interference priorities during channel assignment When this parameter is set to YES, The BSC6900 preferentially uses the TRX with good power-saving performance according to the TRX power priority reported by the BTS. Smaller priority value indicates better power saving quality. If the priority is of a great value, the BTS closes TRXs late. Channel assignment priority of the cell If this parameter is set to CAPABILITY, the factors are listed as follows in a descending order of priority: capacity factors, quality factors, PS cooperation factors, and management factors. If this parameter is set to QUALITY, the factors are listed as follows in a descending order of priority: quality factors, capacity factors, PS cooperation factors, and management factors. If this parameter is set to PSRELATIVELY, the factors are listed as follows in a descending order of priority: capacity factors, PS cooperation factors, quality factors, and management factors. If this parameter is set to PSABSOLUTELY, the factors are listed as follows in a descending order of priority: PS cooperation factors, capacity factors, quality factors, and management factors.
Channel Allocate Strategy Assign NonAMR User Loose Fre. Reuse TRX
Whether to preferentially allocate loose multiplexing frequencies to nonAMR users Frequency multiplexing mode in the TRX. To enable a loose frequency multiplexing mode such as 4x3 multiplexing, set this parameter to LOOSE. To enable a tight frequency multiplexing mode such as 1x3 or 1x1, set this parameter to TIGHT.
Frequency Reuse Mode
Table 2-42 Parameter description (2) Paramete r Defa ult Valu e GUI Value Range Actual Value Range MML Command SET OTHSOFTPAR A(Optional) SET GCELLCHMG AD(Optional) Imp act
Unit
TCH Rate Modify TCH Traffic Busy Threshold

Issue 08 (2011-09-30)
YES
NO(No), YES (Yes)
NO, YES
None
BSC
60
0~100
0~100
per cent
Cell
339
Paramete r AMR TCH/H Prior Cell Load Threshold Load of UL-OL Cells Rate Select Allowed Tch Traffic Busy Overlay Threshold Tch Traffic Busy Underlay Threshold TCHH Function Switch Fix Abis Prior Choose Load Thred Flex Abis Prior Choose Load Thred HR Allocation Flag Congestio n Ratio on Ater Resource
Defa ult Valu e
GUI Value Range
Actual Value Range
Unit
MML Command
Imp act
55
0~99
0~99
per cent
SET GCELLCHMG AD(Optional)
Cell
YES
NO(No), YES (Yes)
NO, YES
None
Cell
70
0~100
0~100
per cent
Cell
60
0~100 NO(NO), YES (YES)
0~100
per cent
SET GCELLCHMG AD(Optional) SET BTSFLEXABIS PARA(Optional)
Cell
NO
NO, YES
None
BTS
80
0~100
0~100
per cent
SET BTSFLEXABIS PARA(Optional)
BTS
80
0~100 Close(Close), Open(Open)
0~100
per cent
SET BTSFLEXABIS PARA(Optional) SET OTHSOFTPAR A(Optional) SET OTHSOFTPAR A(Optional)
BTS
Open
Close, Open
None
BSC
85
80~100
80~100
per cent
BSC
Issue 08 (2011-09-30)
340
Paramete r
Defa ult Valu e
GUI Value Range
Actual Value Range
Unit
MML Command SET GCELLCHMGB ASIC(Optional) SET GCELLCHMGB ASIC(Optional)
Imp act
Ratio of TCHH Ratio of AMR-HR
100
0~100
0~100
per cent per cent
Cell
100
0~100 L0(Level0), L1 (Level1), L2 (Level2), L3 (Level3), L4 (Level4), L5 (Level5), L6 (Level6), L7 (Level7)
0~100
Cell
TRX Priority Allocation TRX Priority Allowed History Record Priority Allowed Interf. Priority Allowed Power Priority Allowed
L0
L0, L1, L2, L3, L4, L5, L6, L7
None
SET GTRXDEV (Optional) SET GCELLCHMG AD(Optional) SET GCELLCHMG AD(Optional) SET GCELLCHMG AD(Optional) SET GCELLCHMG AD(Optional)
TRX
YES
NO(No), YES (Yes)
NO, YES
None
Cell
YES
NO(No), YES (Yes) NO(No), YES (Yes) NO(No), YES (Yes) CAPABILITY (Capability preferred), QUALITY (Quality preferred), PSRELATIVEL Y(PS relatively preferred), PSABSOLUTE LY(PS absolutely preferred)
NO, YES
None
Cell
YES
NO, YES
None
Cell
YES
NO, YES
None
Cell
Channel Allocate Strategy
CAP ABI LIT Y
CAPABILIT Y, QUALITY, PSRELATI VELY, PSABSOLU TELY
None
SET GCELLCHMGB ASIC(Optional)
Cell
Issue 08 (2011-09-30)
341
Paramete r Assign NonAMR User Loose Fre. Reuse TRX Frequency Reuse Mode
Defa ult Valu e
GUI Value Range
Actual Value Range
Unit
MML Command
Imp act
NO LOO SE
NO(No), YES (Yes) LOOSE(Loose), TIGHT(Tight)
NO, YES LOOSE, TIGHT
None
SET GCELLCHMG AD(Optional) SET GTRXDEV (Optional)
Cell
None
TRX
2.23.5 Counters
2.23.6 Glossary

l l l l l TS 29.002: "Digital cellular telecommunications system (Phase 2+); Mobile Application Part (MAP) specification". ISO/IEC 646 (1991): "Information technology-ISO7-bit coded character set for information interchange". GSM 04.18: "Digital cellular telecommunications system (Phase 2+); Mobile Radio Interface Layer 3 specification; Radio Resource Control Protocol". GSM 04.08: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification". GSM 08.06: "Digital cellular telecommunications system (Phase 2+); Signalling transport mechanism specification for the Base Station System Mobile services Switching Centre (BSS MSC) interface". GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile services Switching Centre Base Station System (MSC BSS) interface; Layer 3 specification". GSM 08.51: "Digital cellular telecommunications system (Phase 2+); Base Station Controller Base Transceiver Station (BSC BTS) interface; General aspects". GSM 08.52: "Digital cellular telecommunications system (Phase 2+); Base Station Controller Base Transceiver Station (BSC BTS) interface; Interface principles".
l l l
Issue 08 (2011-09-30)
l l l l l l l l
GSM 08.56: "Digital cellular telecommunications system (Phase 2+); Base Station Controller Base Transceiver Station (BSC BTS) interface; Layer 2 specification". GSM 08.58: "Digital cellular telecommunications system (Phase 2+); Base Station Controller Base Transceiver Station (BSC BTS) interface; Layer 3 specification. BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.24 Ciphering
2.24.1 Introduction
2.24.1.1 Scope
This document describes ciphering of Huawei GBSS. It covers the function of and technology mechanisms regarding this feature, including the ciphering key (Kc) generation, A5 ciphering algorithm, ciphering algorithm selection, signaling procedure, and improvements in A5 ciphering algorithm.


The change history provides information on the changes in the ciphering feature in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the ciphering feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.24.2 Overview
The information ciphered on the Um interface involves signaling, speech, and data. The implementation of ciphering guarantees the information security and prevents user information or conversation contents from unauthorized access. The ciphering procedure is initiated on the network side. The BTS and MS cipher and decipher the information by using the A5 algorithm and the ciphering key (Kc) generated by the A8 algorithm on the basis of the capability of the MS and BTS. Thus, the security of the information on the Um interface is ensured. The Kc is generated by the GSM authentication center (AuC) and stored in the MSC/VLR. The Kc is sent to the BTS before the ciphering procedure begins. The MS and the network adopt the A8 algorithm to generate the Kc by using the same Ki and random number (RAND). A ciphering or deciphering sequence is generated through the A5 algorithm on the basis of the Kc stored in the MS and the network and the frame number from the current pulse stream. The network uses the same ciphering sequence in the uplink and downlink. For each burst, the data is ciphered or deciphered as follows: l l One sequence is used for the MS ciphering and BTS deciphering. The other sequence is used for the BTS ciphering and MS deciphering.
The GSM specifications define the following ciphering algorithms:

l l l l l l l l
A5/0 Ciphering Algorithm A5/1 Ciphering Algorithm A5/2 Ciphering Algorithm A5/3 Ciphering Algorithm A5/4 Ciphering Algorithm A5/5 Ciphering Algorithm A5/6 Ciphering Algorithm A5/7 Ciphering Algorithm
NOTE
A5/0 means no ciphering at all.
A network operator can use the A5 ciphering algorithm only after applying for and being granted with authorization of the 3GPP Organizational Partners. The network operator should use A5/1 or A5/3 ciphering algorithm because the A5/2 ciphering algorithm is deciphered currently. The A5/3 ciphering algorithm is preferred in terms of security. The ciphering algorithms are selected on the basis of the capabilities of the network and MS. The ciphering algorithms to be adopted should be those allowed in the ciphering command delivered by the MSC, allowed in the BSC data configuration, and supported by the MS. The BSC selects the appropriate ciphering algorithms based on the priorities of the algorithms. If the BSS does not support the ciphering algorithms allowed in the ciphering command delivered by the MSC, the ciphering is rejected. The A5 ciphering algorithm provides weak protection for data security. Therefore, the ciphering procedure is optimized on the basis of the characteristics of the Um interface transmission in GSM, thus enhancing transmission security and network bugging defense.

2.24.3.1 Kc and Its Generation
This describes the application and generation of the ciphering key (Kc). The MS and the network use the same Kc for ciphering and deciphering user data. An MS is allocated an International Mobile Station Identity (IMSI) and Ki after it is registered in the GSM network. The MS and the network use the same Ki and RAND. The RAND is generated by the network and sent to the MS. Both the network and the MS use the A8 algorithm to generate the ciphering key Kc. Figure 2-65 shows the generation of the Kc.
Issue 08 (2011-09-30)
345
Figure 2-65 Generation of Kc
2.24.3.2 A5 Ciphering Algorithm

This describes the application of the A5 ciphering algorithm, which is used to generate a pseudorandom sequence. The A5 ciphering algorithm generates a 114-bit ciphering sequence or a 114-bit deciphering sequence based on the 64-bit Kc stored in the MS and the network, and a 22-bit frame number from the current pulse stream. The data ciphering/deciphering is achieved through the Exclusive OR operation between the ciphering/deciphering sequence and the information bit in the ciphered/deciphered data according to the A5 algorithm. The network uses the same ciphering sequence in the uplink and downlink. For each burst, one sequence is used for the MS ciphering and BTS deciphering whereas the other is used for the BTS ciphering and MS deciphering. The ciphering/deciphering on the radio links is performed by the BTS and MS. Figure 2-66 shows the ciphering/deciphering process.
Issue 08 (2011-09-30)
346
Figure 2-66 Ciphering/deciphering process
2.24.3.3 Algorithm Selection

The ciphering algorithms are selected on the basis of the capabilities of the network and MS. The process of selecting the ciphering algorithms is as follows: 1. In the call access procedure, the MS sends an Establish Indication message to the BSC. l If the parameter ECSC in the system information is set to No, the MS reports Classmark 1 or Classmark 2, indicating whether the MS supports A5/1, A5/2, and A5/3 ciphering algorithms. l If the parameter ECSC in the system information is set to Yes, the MS reports Classmark 1, Classmark 2, and Classmark 3, indicating whether the MS supports A5/1, A5/2, A5/3, A5/4, A5/5, A5/6, and A5/7 ciphering algorithms. 2. On receiving the Ciphering Mode Command message from the MSC, the BSC checks the classmarks reported by the MS. If the BSC does not receive Classmark 3, the BSC sends a Classmark Enquiry message to the MS, asking the MS to report Classmark 3. Classmark 3 defines whether an MS supports A5/4, A5/5, A5/6, and A5/7 ciphering algorithms.
The selection of the ciphering algorithms follows the following principles: l l The ciphering algorithms to be adopted should be those allowed in the ciphering command delivered by the MSC, allowed in the BSC data configuration, and supported by the MS. The BSC selects the appropriate ciphering algorithms based on the priorities of the algorithms, and then sends an Encryption Mode Command message to the BTS.
NOTE
The priorities of the ciphering algorithms are decreased from A5/7 to A5/0.
Issue 08 (2011-09-30)
347
CAUTION
l If the BSS does not support the ciphering algorithms specified in the Ciphering Mode Command message, it sends the MSC a Ciphering Mode Reject message with the cause value Ciphering Algorithms Not Supported. l If the MSC requests to change the ciphering algorithms while the BSS has enabled the former ciphering algorithms, the BSS sends a Ciphering Mode Reject message to the MSC.
2.24.3.4 Signaling Procedure

This describes the signaling procedure for ciphering. The ciphering procedure generally applies to location update, service access, and inter-BSC handover. It requests that the BSC and MSC are configured with the ciphering algorithms and that the BTS and MS have the codec capabilities associated with the ciphering algorithms. The application of ciphering algorithms in the radio telecommunications system depends on the radio resources management entity. Figure 2-67 shows the ciphering procedure, which is initiated by the network and executed by the BTS. Figure 2-67 Ciphering procedure
Initiating the Setting of the Ciphering Mode

When the authentication procedure is complete, the MSC sends the BSC a Ciphering Mode Command message, which contains the Kc. The BSC sends a Ciphering Mode Command message to the MS through the BTS. This message indicates whether the ciphering should be performed by the MS and which ciphering algorithm should be used by the MS.
Completing the Setting of the Ciphering Mode

Completing the setting of the ciphering mode involves the following operations: 1. On receiving a valid Ciphering Mode Command message, the MS loads the Kc stored in the SIM card. If the MS receives an invalid Ciphering Mode Command message, the
Issue 08 (2011-09-30)
message is considered erroneous. In this case, the MS sends an RR Status message with the cause value Protocol Error and does no further processing. A valid Ciphering Mode Command message is defined to be one of the following: l One that indicates "start ciphering" and is received by the MS in "not ciphered" mode. l One that indicates "no ciphering" and is received by the MS in "not ciphered" mode. l One that indicates "no ciphering" and is received by the MS in "ciphered" mode. 2. After the MS receives the Ciphering Mode Command message and finishes the ciphering, it begins to send and receive messages in ciphered mode. l If the MS has started certain operations specified in the Ciphering Mode Command message, it sends a Ciphering Mode Complete message to the network. l If the "cipher response" field in the Ciphering Mode Command message is specified "IMEISV request", the MS shall include its IMEI in the Ciphering Mode Complete message. 3. On receiving the Ciphering Mode Complete message from the MS, the network starts information transmission in ciphered mode.
Rejecting the Ciphering Mode

If the BSS does not support the ciphering algorithms specified in the Ciphering Mode Command message, it sends the MSC a Cipher Mode Reject message with the cause value Ciphering Algorithm Not Supported.
2.24.3.5 Improvements in A5 Ciphering Algorithm

This describes the improvements in A5 ciphering algorithm against security problems. The ciphering procedure is optimized on the basis of the characteristics of the Um interface transmission in GSM, and thereby enhances transmission security and network bugging defense. The optimization of the ciphering procedure is achieved from the following aspects: l Fast SDCCH handover is adopted in the MS access process, which increases the difficulty for the intruder to trace the user call. Fast SDCCH handover indicates that the BTS initiates an intra-cell SDCCH handover immediately after sending the ciphering command to the MS. Thus, the subsequent ciphered signaling can be transmitted and received on a new signaling channel. SD Quick HO specifies whether this function is enabled. To avoid incompatibility with the MS, the handover command is sent after the ciphering complete message is received. l The TCH timing handover is introduced to increase the difficulty for the intruder to trace a user. For speech calls, intra-cell handovers are performed at a specified time. TCH Time Handover Switch specifies whether the TCH timing handover is enabled. If TCH Time Handover Switch is set to Yes, the handover timer is started and the length of the timer is TCH Time Handover Period. When TCH Time Handover Period expires, an intra-cell forced handover is performed. l The Hopping Sequence Number (HSN) in the Flex Training Sequence Code (TSC) and Flex Mobile Allocation Index Offset (MAIO) differentiates one TCH from another. Therefore, the characteristics of TCHs are different and an intruder cannot trace other TCHs according to the characteristics of a certain TCH.
Issue 08 (2011-09-30)
Whether to enable the Flex TSC function depends on the setting of Flex TSC Switch. If Flex TSC Switch is set to Yes, the channels join in frequency hopping and each channel is randomly assigned a TSC, ranging from 0 to 7. l After the BTS sends the ciphering command, it stops sending System Information 5, 5bis, and 5ter over the SACCH on the SDCCH. Stop Send SI 5/5bis/5ter after Encrypt specifies whether to stop the sending of system information. If Stop Send SI 5/5bis/5ter after Encrypt is set to Yes, the BTS stops sending System Information 5, 5bis, and 5ter over the SACCH on the SDCCH after sending the ciphering command. Instead, the BTS sends System Information 6 or L2 fill frames. l The dummy bits are randomized. Dummy Bit Randomization Switch specifies whether to randomize the dummy bits. If Dummy Bit Randomization Switch is set to Yes, the BTS randomizes all the 0x2b dummy bits in the signaling and all the dummy bits in L2 fill frames. To avoid incompatibility with the MS, the BTS reserves the initial 0x2b dummy bits when randomizing signaling.
2.24.3.6 Impact on KPI Impact on System Performance

The use of ciphering algorithms in the telecommunications increases the signaling link flow and the access delay of a call. If the BSS does not support a specified ciphering algorithm, call accesses or handovers might fail. In this case, the performance counters such as assignment success rate and handover success rate are affected.

None.

This describes the ciphering algorithms supported currently. Currently, Huawei equipment supports the following ciphering algorithms: A5/1, A5/2, and A5/3. The ciphering algorithms A5/1, A5/2, and A5/3 coexist in the same system and can be flexibly defined through data configuration to meet specific regional requirements. The 3GPP Organizational Partners allow all countries to apply for A5/1 or A5/3 because A5/2 is prone to be decrypted. The A5/3 ciphering algorithm is preferred over other ciphering algorithms in terms of security.
2.24.5 Parameters
This chapter describes the parameters related to ciphering. For the meaning of each parameter, see Table 2-43. For the default value, value range, and related MML commands of each parameter, see Table 2-44.
Issue 08 (2011-09-30)
350
Table 2-43 Parameter description (1) Parameter Description The early classmark sending control (ECSC) parameter specifies whether the MSs in a cell use early classmark sending. After a successful immediate assignment, the MS sends additional classmark information to the network as early as possible. The additional classmark information mainly contains the CM3 (classmark 3) information. The CM3 (classmark 3) information contains the frequency band support capability of the MS (used for the future channel assignment), power information about each frequency band supported by the MS (used for the handover between different frequency bands), and encryption capability of the MS. Whether to enable the SDCCH quick handover test function. If this parameter is set to Yes, the BSC6900 initiates intra-cell SDCCH handover as soon as the MSC issues an encrypted command to the MS. Thus, the forwarding encrypted signaling can be transmitted and received on a new signaling channel. In this way, the network security is improved. This parameter specifies whether to perform periodic intra-cell handover for speech services on TCH. This parameter specifies the interval at which the speech service on a TCH is handed over. Whether to enable the function of the Flex training sequence code (TSC). If the value of this parameter is ON and the BTS supports the Flex TSC function, the BSS dynamically allocates TSCs to hopping frequencies for improving the security of calls. This parameter specifies whether the sending of system information 5, 5bis, and 5ter can be stopped on the SACCH on the SDCCH after the BTS issues a ciphering command. Whether a BTS randomizes the dummy bits in all the signaling messages that the BTS sends to an MS. That is, dummy bits are randomized rather than filled on the basis of 0x2B.
ECSC
SD Quick HO TCH Time Handover Switch TCH Time Handover Period
Flex TSC Switch Stop Send SI 5/5bis/5ter after Encrypt Dummy Bit Randomization Switch
Table 2-44 Parameter description (2) Parameter Defa ult Value GUI Value Range Actual Value Range Unit MML Command SET GCELLCCB ASIC (Optional) Impa ct
ECSC
YES
NO(No), YES (Yes)
NO, YES
None
Cell
Issue 08 (2011-09-30)
351
Parameter
Defa ult Value
GUI Value Range
Actual Value Range
Unit
MML Command SET GCELLSOF T(Optional) SET GCELLSOF T(Optional) SET GCELLSOF T(Optional) SET GCELLSOF T(Optional) SET GCELLSOF T(Optional) SET GCELLSOF T(Optional)
Impa ct
SD Quick HO TCH Time Handover Switch TCH Time Handover Period Flex TSC Switch Stop Send SI 5/5bis/5ter after Encrypt Dummy Bit Randomizati on Switch
OFF
OFF(Off), ON (On) OFF(Off), ON (On)
OFF, ON
None
Cell
OFF
OFF, ON
None
Cell
60
1~600 OFF(Off), ON (On) OFF(Off), ON (On) OFF(Off), ON (On)
1~600
Cell
OFF
OFF, ON
None
Cell
OFF
OFF, ON
None
Cell
OFF
OFF, ON
None
Cell
2.24.6 Counters
2.24.7 Glossary

l l l l l l l 3GPP 48.058: "Base Station Controller - Base Transceiver Station (BSC-BTS) Interface Layer 3 Specification" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
Issue 08 (2011-09-30)
352
2.25 Discontinuous Transmission and Discontinuous Reception

2.25.1 Introduction
2.25.1.1 Scope
This document describes the discontinuous transmission (DTX) and discontinuous reception (DRX). It covers the function of and technology mechanisms regarding this feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change: refers to the change in the discontinuous transmission and discontinuous reception feature of a specific product version. l Editorial change Editorial change: refers to changes in information that has already been included, or the addition of information that was not provided in the previous version.
Document Issues
02(2009-09-30)
01(2009-06-30)
2.25.2 Overview
The Discontinuous Transmission (DTX) and Discontinuous Reception (DRX) mechanism reduces the interference level and improves the system efficiency. Through this mechanism, the wastage of system resources is minimized and an acceptable signal quality is maintained. l DTX When an MS is engaged but no speech signals are transferred, the MS sends only comfort noises periodically to the peer end. The data volume of these comfort noises is smaller than the volume of normal speech data. An MS does not keep transmitting speech signals during a call. Typically, only 40% of the duration of the call is occupied for speech transmission. During the non-speech transmission period, an MS reduces the transmitted data to suppress the interference to other channels and to help reserve system resources. In addition, DTX relieves the workload of the TX module of the MS. The MS can enjoy a longer call duration and standby time. DTX affects only the transmission of TCH frames. l DRX An MS in idle mode detects only the paging channels within a specific paging group. When other paging groups send paging messages to an MS, the MS blocks the receive channel. Each MS is mapped to a paging group, and each paging group is mapped to a paging subchannel in the serving cell. When operating in idle mode, an MS detects the paging messages broadcast by the system only on the mapped paging sub-channel. The MS blocks other paging sub-channels by powering off some hardware of the MS, and this also saves power.

2.25.3.1 DTX
DTX can reduce the transmit power of an MS when the MS does not receive any speech signals. The quality of speech services in the entire radio network is thus improved. DTX involves the following technical aspects:
l l l
Silence Descriptor (SID) frames Voice Activity Detection (VAD) Global measurement and local measurement
When there is no speech signal transmission during a call, the MS sends SID frames to the BTS. The VAD enables the MS to accurately detect speech signals. The principles of SID frames and the VAD are described as follows: l SID frames The noise coding procedure is basically the same as the speech coding procedure. After sampling and quantification, the noise data of every 20 ms is coded into a noise block by a hybrid coder. The noise blocks, each of which is 260 bits in length, are encapsulated as special SID frames. After channel coding, interleaving, encryption, and modulation, the SID frames are sent out through eight continuous bursts. A complete SACCH message block on the TCH consists of four 26 multi-frames (480 ms). To enable the peer end to distinguish between speech frames and SID frames, the eight continuous bursts are always sent at the beginning of the third 26 multi-frame. No message is sent on other frames except for the SACCH of a measurement period.
NOTE
A SID encoded with a 20-ms noise block completes the interleaving process with the last SID and next SID. The first SID frame completes the interleaving process with the voice frame preceding it and the following SID frame. DTX is optional, and uplink DTX is independent of downlink DTX. In a cell, the DTX in the HR coding scheme is independent from the DTX in the FR coding scheme. The uplink DTX and downlink DTX are activated by the system parameters based on the type of traffic channel used by the MS. l The uplink DTX is activated by the parameters either FR Uplink DTX or HR Uplink DTX on the BSC side. l The downlink DTX is activated by the "DTX Flag" in the "Service/BSC Table" on the MSC side and by the parameters FR Use Downlink DTX or HR Use Downlink DTX on the BSC side. DTX is used only for speech transmission and non-transparent data transmission, involving MS and TRAU operations. That is, the uplink DTX depends on the data input of the MS and the downlink DTX depends on the data input of the MSC or TRAU.
VAD When DTX is enabled, the coder must decide whether the current signal is a speech signal or a noise signal. The VAD is designed to help the coder to make the decision. The VAD distinguishes speech signals from noise signals based on a principle that the energy of noise is always lower than that of speech. Based on the power of noise signals, the VAD specifies a threshold for the power of voice signals. Only the power higher than this threshold is defined as voice; otherwise, it is background noise even if voice coexists. The VAD is closely associated with the speech coding algorithm. The VAD compares the energy of filtered signals with the threshold defined by itself, and then decides whether every output frame contains the speech or noise. In addition, VAD provides additional bits to indicate whether or not to transmit the frame. VAD generates a group of thresholds every 20 ms voice block to decide whether the next 20 ms voice block is voice or noise. When background noise is extremely high, VAD may regard the noise signals as voice and send them after encoding.
Two measurement methods are available in the GSM: global measurement and local measurement.
Issue 08 (2011-09-30)
355
Global measurement: measures the receive level and receive quality in 100 timeslots in the whole measurement period (four 26 multiframes except idle frames) and calculates the average value. Local measurement: averages the receive level and receive quality of 12 timeslots, including the eight continuous TCH bursts and the four SACCH bursts carrying measurement reports
To ensure consistency, the BTS and the MS perform the global and local measurements irrespective of whether the UL/DL DTX is activated. Each SACCH measurement report of the BTS and the MS specifies whether the DTX function is applied; therefore, the BSC can select the global measurement or local measurement for decision based on the measurement report.
NOTE
Both types of measurement are applied in the uplink and the downlink irrespective of whether DTX is activated.
2.25.3.2 DRX
In DRX mode, every MS is mapped to a specific paging group. The MS calculates the paging groups based on the IMSI and the CCCH configuration of the serving cell, and then detects the system information sent only from the paging groups. DRX involves the concept of paging group in related GSM protocols. l Paging group In the GSM network, the CCCH includes the AGCH and the PCH. The CCCH can be carried on one or more physical channels. In case of high paging traffic in a location area, one physical timeslot for paging message transmission is insufficient. The GSM protocol allows multiple CCCHs to be configured on the TRX carrying the BCCH. The CCCHs can be configured only on timeslot 0, 2, 4, or 6. The number of CCCH message blocks in a cell reflects the resources that can be used as the AGCH or the PCH in the cell. Table 2-45 lists the mapping between the CCCH configuration and the number of CCCH message blocks in the BCCH multi-frame structure. Table 2-45 Mapping between CCCH configuration and number of CCCH message blocks in the BCCH multi-frame structure CCCH Configuration One physical channel used for CCCH, not combined with SDCCHs One physical channel used for CCCH, combined with SDCCHs Two physical channels used for CCCH, not combined with SDCCHs Three physical channels used for CCCH, not combined with SDCCHs Four physical channels used for CCCH, not combined with SDCCHs Number of CCCH Message Blocks in BCCH Multi-Frame 9 3 18 27 36
Issue 08 (2011-09-30)
356
The value of CCCH Blocks Reserved for AGCH specifies the number of CCCH message blocks used as the AGCH in the BCCH multi-frame structure. Multi-Frames in a Cycle on the Paging CH specifies the scale of BCCH multi-frames that are used by the paging group. The formula for calculating the number of paging groups of the service cells is: Number of paging groups = (CCCH message blocks CCCH Blocks Reserved for AGCH) x Multi-Frames in a Cycle on the Paging CH. l Calculating the paging group The formula for calculating the paging group mapped to the MS is: Paging group = ((IMSI mod 1000) mod (Number of cell paging groups)) div CCCH Blocks Reserved for AGCH The MS calculates the mapped paging group based on the IMSI and the configuration of paging channels in the serving cell, and then calculates the paging sub-channel of the mapped paging group.
2.25.4 Parameters
This chapter describes the parameters related to the DTX and DRX. For the meaning of each parameter see Table 2-46. For the default value, value range, and related MML commands of each parameter, see Table 2-47. Table 2-46 Parameter description (1) Parameter Description Whether the uplink DTX function is enabled for FR calls. For details, see GSM Rec. 05.08. Uplink DTX is not restricted by the MSC. Shall_Use:An MS will use uplink DTX if it supports uplink DTX. May_Use:An MS will determine whether to use uplink DTX if both the cell and MS support uplink DTX. Shall_NOT_Use:DTX will not be used. Whether the uplink DTX function is enabled for HR calls. For details, see GSM Rec. 05.08. Uplink DTX is not restricted by the MSC. Shall_Use:An MS will use uplink DTX if it supports uplink DTX. May_Use:An MS will determine whether to use uplink DTX if both the cell and MS support uplink DTX. Shall_NOT_Use:DTX will not be used. Whether the downlink discontinuous transmission (DTX) function is enabled for full rate (FR) calls. This function is also restricted by the DTX switch in the MSC. If the MSC allows the downlink DTX for calls and the value of this parameter(FRDLDTX) is YES, the downlink DTX is enabled for FR calls of cells. Whether the downlink DTX function is enabled for half rate (HR) calls. This function is also restricted by the DTX switch in the MSC. If the MSC allows the downlink DTX for calls and the value of this parameter (HRDLDTX) is YES, the downlink DTX is enabled for HR calls of cells. BS-AG-BLKS-RES, indicating the number of the CCCH message blocks reserved for the AGCH. After the CCCHs are configured, the value of this parameter indicates the actual seizure rates of the AGCHs and the PCHs over the CCCHs.
FR Uplink DTX
HR Uplink DTX
FR Use Downlink DTX HR Use Downlink DTX CCCH Blocks Reserved for AGCH
Issue 08 (2011-09-30)
Parameter
Description Number of multiframes in a cycle on a paging sub-channel. In fact, this parameter specifies the number of paging sub-channels that a paging channel in a cell is divided into. In an actual network, an MS does not listen to other paging sub-channels but its belonging paging sub-channel only. Refer to GSM Rec. 05.02 and GSM Rec. 05.08. The larger the value of this parameter, the more the number of the paging sub-channels in a cell, and the fewer the number of the users belonging to each paging sub-channel. In this case, the mean uptime of the MS battery can be prolonged. Refer to the computing mode of paging group in GSM 05.02 of GSM Standards. The larger the value of this parameter, however, the larger the time delay of a paging message in a space segment. Thus, the average service performance of the system lowers. Based on the principle of ensuring that overload does not occur to paging channels, you must set this parameter to a value as small as possible. You must regularly measure the overload conditions of the paging channels in a running network and accordingly adjust the value of this parameter properly. A paging message in a location area must be sent in all the cells within this location area at the same time. Therefore, the capacity of a paging channel of each cell in a location area must be the same or nearly the same. The capacity refers to the calculated number of paging sub-channels of each cell.
Multi-Frames in a Cycle on the Paging CH
Table 2-47 Parameter description (2) Parameter Defaul t Value GUI Value Range May_Use (May Use), Shall_Use (Shall Use), Shall_NOT_ Use(Shall not Use) May_Use (May Use), Shall_Use (Shall Use), Shall_NOT_ Use(Shall not Use) Actual Value Range Unit MML Comma nd SET GCELL BASICP ARA (Optiona l) SET GCELL BASICP ARA (Optiona l) SET GCELL BASICP ARA (Optiona l) Impact
FR Uplink DTX
Shall_U se
May_Use, Shall_Use, Shall_NOT_U se
None
Cell
HR Uplink DTX
Shall_U se
May_Use, Shall_Use, Shall_NOT_U se
None
Cell
FR Use Downlink DTX
YES
NO(No), YES(Yes)
NO, YES
None
Cell
Issue 08 (2011-09-30)
358
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
Unit
MML Comma nd SET GCELL BASICP ARA (Optiona l) SET GCELLI DLEBA SIC (Optiona l)
Impact
HR Use Downlink DTX
YES
NO(No), YES(Yes)
NO, YES
None
Cell
0~7 2_M_PERIO D(2 Multiframe Period), 3_M_PERIO D(3 Multiframe Period), 4_M_PERIO D(4 Multiframe Period), 5_M_PERIO D(5 Multiframe Period), 6_M_PERIO D(6 Multiframe Period), 7_M_PERIO D(7 Multiframe Period), 8_M_PERIO D(8 Multiframe Period), 9_M_PERIO D(9 Multiframe Period)
0~7
None
Cell
2_M_P ERIOD
940~4230, step: 470
ms
SET GCELLI DLEBA SIC (Optiona l)
Cell
Issue 08 (2011-09-30)
359
2.25.5 Counters
2.25.6 Glossary

l l l l l l l l l l 3GPP TS 45.002: Multiplexing and multiple access on the radio path 3GPP TS 46.031: Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels 3GPP TS 46.041: Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels 3GPP TS 46.081: Discontinuous Transmission (DTX) for Enhanced Full Rate (EFR) speech traffic channels BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.26 Dual Carriers in Downlink

2.26.1 Introduction
2.26.1.1 Scope
This document describes channel allocation algorithm concerning dual carriers in downlink, and mobile station receiver diversity (MSRD) in the dual carriers in downlink feature.

It is assumed that users of this document are familiar with GPRS basics and have a working knowledge of GPRS telecommunication. This document is intended for: l l
Issue 08 (2011-09-30)
Personnel working on Huawei GPRS products or systems System operators who need a general understanding of this feature

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the in the dual carriers in downlink feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Version
02 (2009-09-30)
01 (2009-06-30)
2.26.2 Overview
The dual carriers in downlink feature is an enhanced solution for downlink packet data rate, in which two downlink carriers are supported and the downlink data rate is doubled, that is, the downlink data rate of the EGPRS system is increased from 473.6 kbit/s to 947.2 kbit/s. Thus, the downlink rate for a single user is improved. Dual Carriers in Downlink, however, requires more channel resources. Therefore, it quite suites the downlink streaming service in cells that have sufficient packet channel resources. With dual carriers in downlink, each MS in the GSM network can be allocated a bandwidth wider than 200 kHz on the Um interface. The number of timeslots received by the MS in a radio
block period is increased. Thus, the downlink rate of the user is improved. Assume that Dual Carriers in Downlink is not supported by the MS and the MS is allocated with four downlink timeslots, as shown in Figure 2-68. In accordance with MCS9, the highest code rate in the EGPRS, the rate of each timeslot is 59.2 kbit/s, and the maximum downlink rate of the MS is 236.8 (59.2 x 4) kbit/s. When Dual Carriers in Downlink is supported by the MS, the MS can receive data of two carriers in a radio block period, as shown in Figure 2-69. In accordance with MCS9, the maximum downlink rate of the MS is 473.6 (59.2 x 8) kbit/s. Figure 2-68 Four timeslots allocated in DL single-carrier mode
Issue 08 (2011-09-30)
362
Figure 2-69 Eight timeslots allocated in DL dual-carrier mode
The channel allocation algorithm of dual carriers in downlink is compatible with algorithm of the packet channel allocation. For details about the algorithm of packet channel allocation, see 2.40 GPRS/EGPRS Channel Management. The difference between the two algorithms lies in that a decision on whether the BSC allocates dual carriers in downlink to the MS is added to the preprocessing of the algorithm of packet channel allocation. The MS enabled with dual carriers in downlink transmits and receives data on two carriers simultaneously. Because the radio link quality on the two carriers are different, the BSC separately adjusts the coding scheme of the two carriers based on the report on radio link quality sent by the MS.

2.26.3.1 Channel Allocation Algorithm
A decision on whether the BSC allocates dual carriers in downlink to the MS is added to the preprocessing of the algorithm of packet channel allocation as follows: l Whether the cell supports dual carriers in downlink If the Support Downlink Dual-Carrier parameter of the cell is set to UNSUPPORT, the BSC does not allocate dual carriers in downlink to the MS. l
Issue 08 (2011-09-30)
Whether the MS supports dual carriers in downlink

Whether the MS supports dual carriers in downlink is determined by whether the field "Multislot Capability Reduction for Downlink Dual Carrier" is carried by the radio access capability of the MS. If the MS does not support dual carriers in downlink, the BSC does not allocate dual carriers in downlink to the MS. l TBF mode of the MS The MS supports dual carrier in downlink only when the TBF mode of the MS is EDGE. If the TBF mode of the MS is GPRS, the BSC does not allocate dual carriers in downlink to the MS. l Current service type of the MS If the current service type of the MS is uplink preferred service or neutral service, the BSC does not allocate dual carriers in downlink to the MS. For details on the service type, see the related descriptions in 2.40.3.2.2 Preprocessing of 2.40 GPRS/EGPRS Channel Management. l QoS type of the current service of the MS If the QoS type of the current service of the MS is streaming service, the BSC will allocate dual carriers in downlink to the MS; if the QoS type of the current service of the MS is Best Effort service, the BSC will allocate dual carriers in downlink to the MS. l Threshold for interoperability between dual carriers in downlink and MSRD When the downlink packet service load of the cell is greater than MSRD PDCH Multiplex Threshold, the downlink throughput of the packet service of the cell cannot be improved even if the MS is enabled with dual carriers in downlink. Thus, the BSC does not allocate dual carriers in downlink to the MS. When the coding scheme of the MS is lower than MSRD MCS Threshold, you can infer that the C/I is low in the area where the MS is located. In this case, the C/I can be greatly improved if MSRD is enabled. Thus, the BSC does not allocate dual carriers in downlink to the MS. The BSC determines as follows whether dual carriers in downlink need to be allocated to the MS after the preprocessing of algorithm of packet channel allocation: l If dual carriers in downlink need to be allocated to the MS, all the available PDCHs in the cell form single-carrier channel groups and dual-carrier channel groups, and all the channel groups are given certain priorities. For details of the weight of the priorities, see 2.40 GPRS/ EGPRS Channel Management. If dual carriers in downlink do not need to be allocated to the MS, the subsequent packet channel allocation algorithm is the same as the common packet channel allocation algorithm. For details about the common packet channel allocation algorithm, see 2.40 GPRS/EGPRS Channel Management.
2.26.3.2 MSRD
The definition of Mobile Station Receive Diversity (MSRD) is as follows: An extra antenna is configured on the MS to improve the downlink receive performance of the MS. Through dualantenna interference elimination, the enhanced channel diversity capability is gained. At the same time, the gaussian minimum shift keying (GMSK) modulation signal obtains the same anti-interference performance as the 8 phase shift keying (8PSK) modulation signal. Thus, the user rate and system capacity are gained. MSRD can effectively improve signal quality and enable the MS to use a higher code rate. l In dense urban areas, such as a senior business district with a good coverage or an indoor area with a poor coverage, MSRD can be used to improve the downlink signal receive quality and a higher code rate is used. In this way, the user data throughput is increased.
Issue 08 (2011-09-30)
Because only the downlink signal receive quality is improved, the interference level of the whole system is not increased. l In common urban areas, suburban areas, and country areas, MSRD can be used to improve the C/I ratio in areas far from the BTS. In this way, the coverage area of the network can be expanded without adding BTSs and the voice quality in the coverage area can be improved.
Dual Carriers in Downlink and MSRD are both enhanced functions in downlink and both require that MS can receive two routes of signals. The Dual Carriers in Downlink function requires the MS to perform baseband processing on the two routes of signals. MSRD, a kind of interference elimination technology, however, can combine two routes of signals into one before the baseband processing. For the MS that has two antennas, Downlink Carriers in Downlink requires that the two antennas receive signals on the two different carriers. MSRD, however, requires that the two antennas receive signals on the same carrier. Thus, the MS cannot be enabled with Dual Carriers in Downlink and MSRD simultaneously. MSRD is a feature on the MS side. The MS that supports MSRD is automatically in MSRD mode if it is not in DL dual-carrier mode. The BSC determines whether the MS in DL dual-carrier mode or in MSRD mode based on the network load and the coding scheme of the MS. When the downlink packet service load of the cell is greater than MSRD PDCH Multiplex Threshold, the downlink packet throughput of the cell cannot be improved even if the MS is assigned with dual carriers in downlink. Thus, the BSC does not allocate dual carriers in downlink to the MS, and the MS is automatically in MSRD mode. When the coding scheme of the MS is lower than MSRD MCS Threshold, you can infer that the C/I is low in the area where the MS is located. In this case, the C/I can be greatly improved if MSRD is used. Thus, the BSC does not allocate dual carriers in downlink to the MS, and the MS is automatically in MSRD mode.

You are advised to enable the Dual Carriers in Downlink feature in cells that have sufficient packet channel resources.
2.26.5 Parameters
The following describes the parameters related to dual carriers in downlink. For the meaning of each parameter, see Table 2-48. For the default value, value range, and related MML commands of each parameter, see Table 2-49. Table 2-48 Parameter description (1) Parameter Support Downlink Dual-Carrier Description Whether the cell supports DLDC.
Issue 08 (2011-09-30)
365
Parameter
Description PDCH Downlink multiplex threshold in the Mobile Station Receiver Diversity (MSRD) mode. When this parameter is set to "80", the MS does not adopt the MSRD mode. When the number of the TBF on the PDCH that is assigned to the MS exceeds this parameter or the coding rate of the PDCH is smaller than the threshold of the coding rate in MSRD mode, the MS is required to adopt the MSRD mode. Threshold of the MS Receiver Diversity (MSRD) mode.
MSRD PDCH Multiplex Threshold MSRD MCS Threshold
Table 2-49 Parameter description (2) Paramete r Default Value GUI Value Range UNSUPP ORT(Not Support), SUPPOR T (Support) Actual Value Range Unit MML Comman d Impact
Support Downlink DualCarrier MSRD PDCH Multiplex Threshold
UNSUPP ORT
UNSUPP ORT, SUPPOR T
None
SET GCELLG PRS (Optional) SET GCELLPS CHM (Optional)
Cell
40
10~80 MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), MCS7 (MCS7), MCS8 (MCS8), MCS9 (MCS9)
10~80
None
Cell
MSRD MCS Threshold
MCS5
MCS1, MCS2, MCS3, MCS4, MCS5, MCS6, MCS7, MCS8, MCS9
None
SET GCELLPS CHM (Optional)
Cell
Issue 08 (2011-09-30)
366
2.26.6 Counters
2.26.7 Glossary

l l l l l l l l l 3GPP 44060 "Radio Link Control/Medium Access Control (RLC/MAC) protocol" 3GPP 45002 "Multiplexing and multiple access on the radio path" 3GPP 45912 "Feasibility study for evolved GSM/EDGE Radio Access Network (GERAN)" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.27 DTM
2.27.1 Introduction
2.27.1.1 Scope
This document describes the definition of dual transfer mode (DTM), channel operation modes, and DTM multislot capability. It also describes the signaling and service bearers in different modes. Based on the evolution of the DTM technology, this document details the channel allocation corresponding to different DTM multislot classes.

Issue 08 (2011-09-30)

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the DTM feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. 2.27.3.1 Channel Operation Mode is added. Parameter Change None. None. None.
01 (2009-06-30)
2.27.2 Overview
With the development of networks, the profit growth point of the operators is turning towards data services. The simultaneous handling of speech service and data service becomes a new demand. Generally, only the class A MS with complex hardware supports speech service and data service simultaneously. However, few manufacturers can provide the class A MS due to its complexity. As defined in 3GPP Technical Specifications, DTM is used to implement simplified
class A operation for an MS, that is, to support simultaneous speech service and data service. After DTM is enabled, the subscribers can send images or browse web pages during a call. In a 3G network, the speech and data services are processed in parallel. In this sense, DTM enables the GSM subscribers to enjoy the services similar to those provided by the 3G network. In addition, the 2G network can complement the 3G network in terms of coverage. After DTM is enabled, the following applications can be introduced to create new revenue streams for GSM operators: l Videophone Subscribers can enjoy uninterrupted data services during a speech service through the Guaranteed Bit Rate (GBR). l Watching or downloading streaming programs During web browsing, speech interaction or call answering is possible. The subscribers may require the CS services while watching streaming programs. When DTM is enabled, CS services can be performed without disrupting the streaming programs. l Sending images or video during a call
Based on the multislot capability of the MS in DTM, the network can allocate different PDCHs on the uplink or downlink to meet different bandwidth requirements. The DTM multislot classes of an MS are classes 5, 6, 9, 10, 11, 31-33, 36-38, and 41-44. DTM can be further classified into the following types: l l DTM An MS supports at least class 5 DTM. Class11 DTM Compared with DTM, class 11 DTM doubles the uplink bandwidth of data services. It is mainly applicable to the uplink preferred services. l HMC DTM Compared with DTM, High Multislot Class (HMC) DTM further improves the uplink and downlink bandwidth of data services. Due to the coexistence of CS and PS services, the requirements for measurement at the physical layer (such as the measurement of timing advance and signal quality) are different. Currently, the CS measurement report is considered. The BSC indicates whether the network supports DTM in system information type 6 (SI6) and SI13. The MS indicates whether it supports DTM in the information elements Classmark 3 and Radio Access Capability.

2.27.3.1 Channel Operation Mode
To perform the CS and PS services simultaneously, two channel operation modes are defined in the protocol: single slot operation and multislot operation. In DTM single slot operation, the MS is assigned a timeslot for both the CS service and the PS service. The channel combination TCH/H+PDCH/H is recommended in the 3GPP TS 23.060. In this channel combination mode, the TCH/H must support AMR speech codec, and the PDCH/
H is exclusively used by an MS on the uplink and downlink. A suitable channel can be provided more easily in single slot operation than in multislot operation. In DTM multislot operation, the CS and PS services are transmitted on different timeslots. The DTM multislot capability of an MS determines the number of PDCHs that can be used by the MS. The channel combination mode recommended by the 3GPP TS 23.060 is TCH/H+PDCH/ F or TCH/F+PDCH/F. The data of multiple MSs can be multiplexed on the PDCH/F but cannot be multiplexed on the PDCH/H. For channel allocation in DTM multislot operation, the DTM multislot capability of an MS must be considered. Generally, the TCH is allocated first, and then PDCHs adjacent to the TCH are allocated.
2.27.3.2 DTM Multislot Capability

The DTM multislot capability is different from the common multislot capability. Different MSs may support different DTM capabilities and thus they need to be communicated to the network so that they can be taken into account for the allocation of radio resources. The DTM multislot capabilities are independent from the currently defined 3GPP TS 45.002 multislot capabilities. When EGPRS is supported, DTM multislot capability for EGPRS operation (applicable also to EGPRS2 operation if supported) is indicated independently from DTM multislot capability for GPRS operation. According to the 3GPP TS 43.055, the DTM multislot classes are classes 5, 6, 9, 10, 11, 31-33, 36-38, and 41-44, and the classes higher than class 31 are called HMC DTM. The higher the DTM multislot classes supported by the MSs and network devices, the higher the uplink and downlink data rates that can be supported. Table 2-50 lists the multislot capabilities corresponding to DTM multislot classes 31-33. Table 2-50 HMC multislot capabilities HMC DTM Maximum Number of Downlink Timeslots Maximum Number of Uplink Timeslots Maximum Number of Concurrent Uplink and Downlink Timeslots 6 6 6
31 32 33
5 5 5
2 3 4
For an MS of multislot class 32 or 33, the extended dynamic allocation (EDA) function must be enabled if the MS requires more than two PDCHs on the uplink.
NOTE
EDA is based on dynamic allocation on the uplink. It enables more uplink timeslots to be allocated to an MS and thus increases the uplink throughput. After the EDA function is enabled, the network allocates multiple uplink timeslots to an MS, and the MS listens to all the PDCHs corresponding to the allocated timeslots. If the MS detects that an uplink state flag (USF) is allocated to itself on an allocated PDCH, the MS can use the uplink blocks corresponding to this PDCH and other allocated PDCHs with larger timeslot numbers. After the EDA function is enabled, a maximum of four uplink PDCHs can be allocated to a single MS. For details about EDA and uplink dynamic allocation, see 2.41.3.5.2 Extended Dynamic Mode and 2.41.3.5.1 Dynamic Allocation Mode respectively.
Issue 08 (2011-09-30)
370
To reduce the length of the coding, incremental support is defined in the protocol, that is, an MS that supports a certain multislot class should support the less restrictive DTM multislot classes. Figure 2-70 shows the maximum number of timeslots for DTM multislot classes 5, 6, 9, 10, and 11. The blue parts indicate the DTM multislot classes, and the arrow indicates the compatibility direction. For example, if an MS supports class 11, the MS can support classes 10, 9, 6, and 5. Figure 2-70 Incremental support of DTM multislot classes
To provide higher data rates for PS services in DTM, the 3GPP defines the HMC DTM. Figure 2-71 shows the maximum timeslot configuration in HMC DTM. Huawei BSC supports HMC DTM classes 31-33. An HMC DTM-capable MS also uses incremental support and supports the DTM multislot classes. For example, an MS of multislot class 33 supports the channel combination for multislot classes 32, 31, 11, 9, and 5.
Issue 08 (2011-09-30)
371
Figure 2-71 Incremental support of HMC DTM
2.27.3.3 Channel Allocation

In DTM, an MS can occupy one TCH and one or more PDCHs simultaneously. The allocation of TCHs and PDCHs should comply with the DTM multislot class defined for the MS. The BSC can allocate the combination of TCH/F+PDCH/F or TCH/F+PDCH/F to the MS. The data of multiple MSs can be multiplexed on one PDCH/F. DTM CS services can adopt all the supported speech coding schemes. The principles for allocating channels to an MS in DTM are as follows: l l l l Full-rate or half-rate channels are allocated for CS services. When all the other conditions are met, a TCH adjacent to the PDCH is preferably allocated. In DTM, the PDCH/F can be shared with other GRPS MSs. The QoS of GPRS/EGPRS services in DTM can be guaranteed.
DTM
When Support DTM is set to Support, the BSC supports multislot classes 5, 6, 9, and 10. Multislot classes 6 and 10 are treated exactly as DTM multislot classes 5 and 9 respectively. Higher multislot classes are treated exactly as DTM multislot class 9. For an MS of DTM multislot class 5, the BSC allocates a maximum of two channels on the uplink or downlink, that is, TCH + 1 PDCH (uplink) + 1 PDCH (downlink). For an MS of DTM multislot class 9, the
BSC allocates a maximum of three channels on the downlink, that is, TCH + 1 PDCH (uplink) + 2 PDCHs (downlink). Regardless of the multislot capability of an MS, the BSC allocates only one PDCH on the uplink for the MS. Figure 2-72 shows the channel allocation. Figure 2-72 Channel allocation in DTM
Class 11 DTM
When Support Class11 DTM is set to Support, an MS of DTM class 11 supports three types of channel combination: channel combination of DTM class 5, channel combination of DTM class 9, and TCH + 1 PDCH (downlink) + 2 PDCHs (uplink). If the EDA function is enabled, the MS also supports the channel combination of TCH + 1 PDCH (downlink) + 2 PDCHs (uplink). An MS of DTM class 11 supports uplink preferred services better. Figure 2-73 shows the channel allocation of DTM class 11. Figure 2-73 Channel allocation of DTM class 11
HMC DTM
The classes higher than class 31 are called HMC DTM. When Support HMC DTM is set to Support, an MS in a call can occupy a maximum of three PDCHs on both the uplink and downlink. That is, the channels allocated to the MS can be TCH + 3 PDCHs (downlink) + 1
PDCH (uplink) or TCH + 1 PDCH (downlink) + 3 PDCHs (uplink). For an MS of DTM multislot class 32 or 33, the EDA function must be enabled if the MS requires more than three PDCHs on the uplink. Figure 2-74 shows the channel allocation of HMC DTM. Figure 2-74 Channel allocation of HMC DTM
2.27.3.4 Using the Main DCCH to Transmit GPRS Signaling in Dedicated Mode
When DTM is supported, the MS can send or receive GPRS signaling (such as GMM signaling generated during cell update or routing area update) in CS dedicated mode. One method to achieve this is that the MS first enters the DTM to establish the uplink TBF and downlink TBF. After transmitting the GPRS signaling, the MS leaves the DTM and enters the dedicated mode again. This method is time consuming and decreases the channel resource usage because PS resources need to be requested first. The other method is to use the main DCCH to transmit the GRPS signaling in dedicated mode. This method can accelerate the GPRS signaling transmission and increase the channel resource usage. When the MS is in dedicated mode, the GPRS signaling is encapsulated as LLC PDU according to the LLC protocols, and then the LLC PDU is sent to the RR protocol entity for processing. The detailed procedure is as follows: l In the uplink, the LLC PDU is inserted in a new Layer 3 message. This Layer 3 message containing the protocol identifier GPRS Transparent Transport Protocol (GTTP) is sent to the BSC on the main DCCH, with the existing Layer 2 mechanisms. The BSC extracts the Temporary Logical Link Identity (TLLI) and the LLC PDU, which are then encapsulated into a BSSGP UL-UNITDATA. In the downlink, when receiving a BSSGP PDU, the BSC can identify whether the PDU contains signaling information. If the length of the LLC PDU meets the requirements and the BSC has an RR connection to the addressed MS with the International Mobile Station Identification Code (IMSI), the GPRS signaling is sent on the main DCCH.
See Figure 2-75.
Issue 08 (2011-09-30)
374
Figure 2-75 Using the main DCCH to transmit GPRS signaling in dedicated mode
The restrictions on using the main DCCH to transmit GPRS signaling in dedicated mode are as follows: l l l The MS must be in dedicated mode rather than in DTM. The main DCCH can transmit the GPRS signaling, but not the GPRS data. The number of LAPDm frames disassembled from the GPRS signaling message must be smaller than a certain value specified by the network. The value is determined by the MAX_LAPDm in SI6. MAX_LAPDm has three bits and its value ranges from 5 to 12. By default, MAX_LAPDm is 5.
2.27.3.5 DTM Services

DTM MS is also called simple class A MS. Compared with the traditional class B MS, the simple class A MS supports DTM besides the dedicated mode, idle mode, packet idle mode, and packet transfer mode. The DTM MS can have CS and PS connections simultaneously. When the enhanced CS establishment and release are not supported, the DTM MS cannot transit between DTM and packet transfer mode, that is, the DTM MS must release the PS resources at CS establishment and release and re-establishes a new TBF. Thus, the PS services are disrupted temporarily. As shown in Figure 2-76, a DTM class A MS can request a PS connection through the signaling channel established for the CS connection to enter the DTM if the MS is in CS dedicated mode. If a DTM class A MS is in packet transfer mode, the MS should release the TBF before it enters the CS dedicated mode. Then, the MS should re-establish a TBF to enter the DTM.
Issue 08 (2011-09-30)
375
Figure 2-76 Conversion between RR modes of class A MS
DTM Establishment
Uplink PS Establishment in Dedicated Mode In dedicated mode, if the BSS and MS support DTM, the MS can send the DTM Request message on the main DCCH to establish the uplink PS connection. If the BSS need not re-allocate CS resources (the original TCHs can be used to carry speech in DTM), it sends a Packet Assignment message to allocate PS resources to the MS. Figure 2-77 Uplink PS establishment in dedicated mode without reallocating CS resources
If the BSS needs to reallocate the CS resources when allocating PS resources (DTM channel allocation is not appropriate due to existing channel distribution), the BSS sends a DTM Assignment Command message on the main DCCH to the MS after reallocating the CS resources. If the MS successfully establishes the new CS connection, it sends an Assignment
Complete message on the new main DCCH. If the MS fails to establish the new CS connection, it sends an Assignment Failure message on the old main DCCH. Figure 2-78 Uplink PS establishment in dedicated mode with CS resources reallocated
Downlink PS Establishment in Dedicated Mode In dedicated mode, if the MS is in the GMM Ready state, the BSS needs to establish a downlink TBF after receiving the downlink PDU from the SGSN. If the BSS need not reallocate the CS resources, it sends a Packet Assignment message on the main DCCH to the MS. If the BSS needs to reallocate the CS resources when allocating PS resources, the BSS sends a DTM Assignment Command message on the new main DCCH to the MS after reallocating the CS resources. If the MS successfully establishes the new CS connection, it sends an Assignment Complete message on the new main DCCH. If the MS fails to establish the new CS connection, it sends an Assignment Failure message on the old main DCCH. The procedure for reestablishing the downlink PS connection between network elements is the same as the procedure for re-establishing the uplink PS connection. Figure 2-79 Downlink PS establishment in dedicated mode and GMM ready state
If the MS is in dedicated mode and GMM standby state, the BSS sends a Packet Notification message on the main DCCH to the MS after receiving the packet paging from the SGSN. The MS sends an LLC frame as a response to the packet paging. The SGSN starts to send the downlink information after receiving the paging response from the MS.
Issue 08 (2011-09-30)
377
Figure 2-80 Downlink PS establishment in dedicated mode and GMM standby state
CS Establishment in Packet Transfer Mode In packet transfer mode, either the MS or the network may initiate a CS connection establishment. In both cases, the packet session must be aborted before the establishment of the CS connection is initiated. The PS connection is then established through the main DCCH of the CS resources.
DTM Release
In DTM, if the CS connection is released, the MS must abandon the PS resources. In the duration of CS services in DTM, if the last TBF is released for an MS, the MS enters the dedicated mode.
Handover in DTM
The decision on when to change the serving cell of a DTM MS is made through the CS measurement report. The handover of the CS call and the cell change for the PS transfer must be performed at the same time. If the DTM handover is not supported, CS handovers may disrupt PS services. In an intra-cell handover, the MS leaves the DTM, enters the dedicated mode on the new CS resource, and may then enter the DTM again. In an inter-cell handover, the MS leaves DTM, enters the dedicated mode in the new cell, reads the system information messages sent on the SACCH, and may then make a cell or RA update and enter the DTM again in the new cell. In DTM, to maintain the continuity of CS and PS services and to protect PS services from disruption, CS handovers are not initiated generally, except for forced handovers, emergency handovers, and fast-moving handovers.
Paging Coordination and Mobility Management

The BSC can control the paging response of an MS through the paging coordination function rather than through the setting of the Network Operation Mode parameter. This enables the MS to enter the DTM to establish CS connection and PS connection simultaneously. l When an MS is in packet transfer mode, the BSC can send the CS Paging message on the PACCH even if the Network Operation Mode parameter is set to Network Operation Mode II or Network Operation Mode III. Thus, the MS does not miss any CS Paging message.
Issue 08 (2011-09-30)
When an MS is in dedicated mode and the system supports DTM, the BSC sends the Packet Notification message on the main DCCH after receiving the PS Paging message. Thus, the MS does not miss any PS Paging message.
If a DTM capable MS is in dedicated mode, it can perform cell update, RA update, and location area (LA) update on the main DCCH so that the load of packet resources is reduced. If LLC PDUs cannot be transmitted on the main DCCH, they are transmitted on TBFs. If a DTM-capable MS is in idle mode, it can perform the combined RA and LA update in Network Operation Mode I when moving from one LA to another. In Network Operation Mode II or Network Operation Mode III, the MS can perform the parallel LA and RA updates. If the RA update is completed first, both the LA update and RA update are performed on the main DCCH because the main DCCH is not released. If the LA update is completed first, the RA Update Accept message needs to be transmitted on the downlink TBF to be established because the main DCCH is released.

Parameter Settings
After a cell is enabled with DTM, it is recommended that the early classmark sending control (ECSC) be set to Yes. If Network Operation Mode of the GPRS attributes is not set to Network Operation Mode I, A Interface Paging Co-ordination Switch should be set to Open so that the network can page the MSs in packet transfer mode successfully.
Function Limitations
Currently, the following functions associated with DTM are not supported: l l l l Single slot operation mode Extended DTM multislot capability Enhanced CS establishment and release DTM handover
To enable DTM, the following conditions must be met: l l l l l DTM requires the support of the BSC, MS, MSC, and SGSN. In addition, the MSC must support the COMMON ID message. DTM is used in built-in PCU configuration mode rather than in external PCU configuration mode. In an extended cell, DTM is not supported due to the limitation of the MS multislot capability. In DTM, call queuing is not supported. In DTM, NC2 is not supported because GPRS measurement reports are not reported.
2.27.5 Parameters
This chapter describes the parameters related to DTM. For the meaning of each parameter, see Table 2-51. For the default value, value ranges, and MML commands of each parameter, see Table 2-52.
Table 2-51 Parameter description (1) Parameter Description Whether to support dual transfer mode (DTM). The DTM allows an MS to use the circuit switching service and the packet switching service at the same time. This function must be supported by the network side. If "Cell Extension Type" in the "ADD GCELL" command or "MOD GCELL" command is set to "Double Timeslot Extension Cell" for a cell, the parameter cannot be set to "SUPPORT". Whether the cell supports the MS with the DTM multi-timeslot capability of class 11 Whether the cell supports the MS with the DTM multi-timeslot capability This parameter is related to the paging channel of the system. There are three network operation modes: network operation mode I, network operation mode II, and network operation mode III. Network operation mode I is used when the system is configured with the Gs interface. Network operation mode II is used when the system is not configured with the Gs interface and the PCCCH is not configured. Network operation mode III is used when the system is not configured with the Gs interface and the PCCCH is configured. The early classmark sending control (ECSC) parameter specifies whether the MSs in a cell use early classmark sending. After a successful immediate assignment, the MS sends additional classmark information to the network as early as possible. The additional classmark information mainly contains the CM3 (classmark 3) information. The CM3 (classmark 3) information contains the frequency band support capability of the MS (used for the future channel assignment), power information about each frequency band supported by the MS (used for the handover between different frequency bands), and encryption capability of the MS. This parameter specifies whether to receive the CS paging request from A interface when the MS uses a PS service. This parameter is used to control the paging collaboration function of A interface of the entire BSC. This parameter specifies whether to forward the paging message of the A interface from the circuit domain to the PS domain .
Support DTM Support Class11 DTM Support HMC DTM
Network Operation Mode
ECSC A Interface Paging Coordination Switch
Table 2-52 Parameter description (2) Parame ter Default Value GUI Value Range UNSUPPO RT(Not Support), SUPPORT (Support) Actual Value Range Unit MML Command Impact
Support DTM
UNSUPP ORT
UNSUPPO RT, SUPPORT
None
SET GCELLGPRS (Optional)
Cell
Issue 08 (2011-09-30)
380
Parame ter
Default Value
GUI Value Range UNSUPPO RT(Not Support), SUPPORT (Support) UNSUPPO RT(Not Support), SUPPORT (Support) NMOI (Network Operation Mode I), NMOII (Network Operation Mode II), NMOIII (Network Operation Mode III) NO(No), YES(Yes)
Actual Value Range
Unit
MML Command
Impact
Support Class11 DTM
UNSUPP ORT
UNSUPPO RT, SUPPORT
None
Cell
Support HMC DTM
UNSUPP ORT
UNSUPPO RT, SUPPORT
None
Cell
Networ k Operati on Mode
NMOII
NMOI, NMOII, NMOIII
None
SET GCELLPSBASE (Optional) SET GCELLCCBASIC (Optional)
Cell
ECSC A Interfac e Paging Coordinati on Switch
YES
NO, YES
None
Cell
CLOSE
CLOSE (Close), OPEN (Open)
CLOSE, OPEN
None
SET BSCPSSOFTPAR A(Optional)
BSC
2.27.6 Counters
2.27.7 Glossary

l l l
3GPP TS 43.055 Dual Transfer Mode (DTM); Stage 2 3GPP TS 44.018 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol 3GPP TS 44.060 General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control / Medium Access Control (RLC/MAC) protocol 3GPP TS 45.002 Multiplexing and multiple access on the radio path 3GPP TS 24.008 Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 3GPP TS 24.007 Mobile radio interface signalling layer 3; General Aspects BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference BSC6900 Hardware Description
l l l l l l l l l l
2.28 Dynamic Channel Conversion

2.28.1 Introduction
2.28.1.1 Scope
This document describes the dynamic SDCCH conversion, dynamic conversion between TCH HR and TCH FR, and dynamic PDCH conversion.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l
Issue 08 (2011-09-30)
Feature change
Feature change refers to the change in the dynamic channel conversion feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.28.2 Overview
Dynamic Channel Conversion enables the conversion of a channel from one type to another based on the actual service requirement in the network. Such a conversion is temporary and triggered by a combination of certain network conditions. The converted channel reverts to the original type when the triggering conditions disappear. Dynamic Channel Conversion involves the conversion between the TCH and the SDCCH, the full-rate TCH and the half-rate TCH, and the TCH and the PDCH. Dynamic SDCCH conversion involves the conversion between the TCHF and the SDCCH, and dynamic PDCH conversion involves the conversion between the TCHF or TCHH and the PDCH. At present, the conversion between the SDCCH and the PDCH is not available. Dynamic Channel Conversion facilitates the channel configuration of the cell and improves the service capability of the cell.

2.28.3.1 Dynamic SDCCH Conversion
?.1. Overview
Dynamic SDCCH conversion is triggered when the requested SDCCH is not allocated to the MS. This procedure involves converting a TCHF to the SDCCH and reverting the SDCCH to the TCHF. Dynamic SDCCH conversion helps to decrease the SDDCH congestion rate in the network and reduce the impact of the initial SDCCH configuration on the system performance. Thus, it reduces the requirement of evaluating the SDCCH demands accurately. The process of converting the TCHF to the SDCCH consists of two phases: SDCCH conversion decision and SDCCH conversion execution. The process of reverting the SDCCH to the TCHF also consists of two phases: SDCCH reversion decision and SDCCH reversion execution. Figure 2-81 shows the complete procedure of dynamic SDCCH conversion. Figure 2-81 Dynamic SDCCH conversion procedure
?.2. Dynamic SDCCH Conversion Decision

The typical decision-making process for dynamic SDCCH conversion consists of three procedures: trigger of the conversion, decision of the conversion, and TCHF channel selection. Dynamic SDCCH conversion can be triggered if the number of idle SDCCHs in the cell is smaller than or equal to the value of Idle SDCCH Threshold N1 or the SDCCH allocation fails during the channel assignment. If the TCHF is converted to the SDCCH after the SDCCH allocation failure, the converted SDCCH is used for the next SDCCH request.
Trigger of Dynamic SDCCH Conversion

Figure 2-82 shows the trigger process of dynamic SDCCH conversion. Figure 2-82 Trigger of dynamic SDCCH conversion
Dynamic SDCCH Conversion Decision

Figure 2-83 shows the decision process of dynamic SDCCH conversion.
Issue 08 (2011-09-30)
385
Figure 2-83 Decision of dynamic SDCCH conversion
After the dynamic SDCCH conversion decision is triggered, the BSC determines whether to allow the conversion based on the following rules. 1. Whether the BSC internal flow control level is 0 If yes, dynamic SDCCH conversion is allowed. Otherwise, it is not allowed. The internal flow control is performed on the basis of the CPU usage. If the CPU usage is less than 65% and no emergency event (for example, massive maintenance operations) occurs, the flow control is not performed, that is, the internal flow control level is 0. 2. 3. Whether SDCCH Dynamic Allocation Allowed is set to Yes If yes, dynamic SDCCH conversion is allowed. Otherwise, it is not allowed. Whether there is another ongoing dynamic SDCCH conversion procedure in the cell If yes, the new conversion procedure is not allowed. Otherwise, it is allowed.
NOTE
Only one dynamic SDCCH conversion procedure can be performed at a time, in a cell.
Issue 08 (2011-09-30)
386
4.
Whether the number of idle SDCCHs in the cell is smaller than or equal to the value of Idle SDCCH Threshold N1 If yes, dynamic SDCCH conversion is allowed. Otherwise, it is not allowed. Whether the number of SDCCHs in the cell plus eight is smaller than or equal to the value of Cell SDCCH Channel Maximum If yes, dynamic SDCCH conversion is allowed. Otherwise, it is not allowed.
NOTE
5.
One TCHF can be converted into eight SDCCHs. Therefore, the total number of SDCCHs after a conversion equals the number of current SDCCHs plus eight.
6.
Whether there are sufficient idle TCHs for the TRXs in the cell If yes, dynamic SDCCH conversion is allowed. Otherwise, it is not allowed. The decision procedure is as follows: (1) The BSC measures the number of idle TCHFs and the number of idle TCHHs in the cell. (2) The BSC determines whether the number of idle TCHHs plus twice the number of TCHFs is greater than eight. If yes, dynamic SDCCH conversion is allowed. Otherwise, the BSC proceeds with 6.3. (3) The BSC determines whether the number of idle TCHHs plus twice the number of TCHFs is greater than twice the number of TRXs in the cell. If yes, dynamic SDCCH conversion is allowed. Otherwise, dynamic SDCCH conversion is not allowed.
7.
Whether there is any qualified TCHF for conversion If yes, dynamic SDCCH conversion is allowed. Otherwise, it is not allowed.
TCHF Selection
After the BSC determines that dynamic SDCCH conversion can be performed, it must select a TCHF for conversion. A qualified TCHF that can be converted to the SDCCH must meet the following requirements: l l l l The channel must be in the available state. The TCHF frequency band and the corresponding BCCH frequency band must be mapped as listed in Table 2-53. The channel must be an initial TCHF or a TCHF that is converted from TCHHs. The number of SDCCHs on the TRX carrying the TCHF cannot exceed eight.
NOTE
If the channel type of a timeslot is SDCCH/8, the timeslot contains eight SDCCHs.
l l
The current cell must have more than one TRX. If the quadruple-transceiver unit (QTRU) board is used, the TCH on the TRX with the minimum number of SDCCHs is preferentially selected.
Issue 08 (2011-09-30)
387
Table 2-53 Mapping between the BCCH frequency band and the TCHF frequency band BCCH Frequency Band P-GSM900M E-GSM900M R-GSM900M DCS1800M PCS1900M GSM850M GSM480M GSM450M TCHF Frequency Band P-GSM900M P-GSM900M or E-GSM900M P-GSM900M, E-GSM900M, or RGSM900M DCS1800M PCS1900M GSM850M GSM480M GSM450M
The TCHF selection varies with the cell type. If... The cell is a common cell Then... The BSC selects any of the qualified TCHFs for dynamic SDCCH conversion. If there exists BCCH channels and non-BCCH channels, the non-BCCH channels are converted firstly. The BSC selects a qualified TCHF in a prioritized order as follows: idle TCHF in the underlaid subcell; busy TCHF in the underlaid subcell; idle TCHF in the overlaid subcell; and busy TCHF in the overlaid subcell. The BSC preferentially selects a qualified idle TCHF in the underlaid subcell. If such an idle TCHF is not found, the BSC selects a qualified busy TCHF.
NOTE The TCHFs in the overlaid subcell of a co-BCCH cell cannot be used for dynamic SDCCH conversion.
The cell is a concentric cell
The cell is a co-BCCH cell
?.3. Dynamic SDCCH Conversion Execution

After selecting a TCHF, the BSC performs the dynamic SDCCH conversion procedure. The dynamic SDCCH conversion procedures vary with the status of the selected TCHF.
Issue 08 (2011-09-30)
388
The selected TCHF is idle. 1. 2. The BSC adjusts the channel attribute from TCHF to SDCCH. The BSC performs different operations based on whether the adjustment of channel attribute is successful. If the adjustment is successful, the BSC adds a dynamic conversion ongoing flag to the cell. If the adjustment fails, the dynamic conversion is terminated. 3. 4. 5. The BSC sends a command to the BTS for adjusting the channel attribute and starts the relevant performance measurement. After receiving the command, the BTS starts converting the channels. After the channels are converted, the BTS sends the State Changed Event Report to the BSC. After receiving the State Changed Event Report, the BSC sets the status of the converted SDCCH/8 to idle and deletes the dynamic conversion ongoing flag. The dynamic TCHF-to-SDCCH conversion is complete.
The selected TCHF is busy. 1. 2. To prevent the services carried on the selected TCHF from being disrupted, the BSC initiates a forced intra-cell handover. The BSC sets the dynamic conversion ongoing flag for the cell and sets the channel status to "TCHF converted to SDCCH, waiting for forced handover response" to prevent the TCHF from being assigned to other services. The BSC performs different operations based on whether a forced handover response is received. If the BSC receives the forced handover response, it determines whether the forced handover is successful. If the forced handover fails, the TCHF is not released and the BSC deletes the dynamic conversion ongoing flag of the cell. The channel conversion is terminated. If the forced handover is successful, the BSC sets the channel status to "Waiting for channel release". When the TCHF becomes idle, the BSC follows the procedure for converting the idle TCHF to the SDCCH. If the BSC does not receive any forced handover response, the BSC deletes the dynamic conversion ongoing flag of the cell. The channel conversion is terminated.
NOTE
3.
The TCH far from the PDTCH is preferentially selected for dynamic SDCCH conversion.
?.4. SDCCH Reversion Decision

After the TCHF is converted to the SDCCH, the SDCCH is reverted to the TCHF if certain conditions are met. The BSC determines to revert the SDCCH to the TCHF if the following conditions are met: l l l
Issue 08 (2011-09-30)
The selected SDCCH/8 channels are converted from a TCHF. One or more of the selected SDCCH/8 channels are idle. The channel selection varies with the type of the cell:
If the cell is not a concentric cell, the SDCCH reversion can be performed when the previous conditions are met. If the cell is a concentric cell, the BSC preferentially selects an SDCCH that meets the previous conditions on the TRX in the overlaid subcell. If there is no appropriate SDCCH in the overlaid subcell, the BSC selects an appropriate SDCCH in the underlaid subcell. l If the QTRU is used, the SDCCH on the timeslot with the maximum number of SDCCHs is preferentially selected.
If the above conditions are not met, the reversion from the SDCCH to the TCHF is not triggered.
?.5. SDCCH Reversion Procedure

If the requirements for SDCCH reversion are met, the BSC performs the SDCCH reversion procedure. The SDCCH reversion procedure lasts less than three seconds. A busy SDCCH/8 channel can also be reverted to the TCHF. Therefore, based on the status of the selected SDCCH/8 channels, the SDCCH reversion procedure is classified into the following types: l If all the selected SDCCH/8 channels are idle, the SDCCH reversion procedure is as follows: 1. 2. 3. 4. l The BSC adjusts the channel attribute from SDCCH to TCHF. The BSC sends a command to the BTS for adjusting the channel attribute and starts the relevant performance measurement. After receiving the command, the BTS starts converting the channels. After the channels are converted, the BTS sends the Status Change Report to the BSC. After receiving the Status Change Report, the BSC sets the status of the converted TCHF to idle. The SDCCH-to-TCHF reversion is complete.
If one or more of the selected SDCCH/8 channels are busy, the SDCCH reversion procedure is as follows: 1. 2. 3. 4. To prevent call disruption on the selected SDCCH/8 channel, the BSC triggers the timer, waiting for the release of channels. The BSC sets the channel status to "SDCCH/8 converted to TCHF, waiting for idle channel" to prevent these channels from being assigned before reversion. If the sub-channels are still busy when the timer expires, they are released forcibly. When all the selected SDCCH/8 channels are idle, the BSC follows the related procedure for reverting the idle SDCCH.
NOTE
Typically, all the SDCCH/8 channels will be idle before the timer expires, because the SDCCH is usually occupied for a very short time.
?.6. Impact
The dynamic SDCCH conversion affects the system performance mainly in the following aspects: l l
Issue 08 (2011-09-30)
The bearer capacity of TCHs in a cell is reduced because TCHFs are converted to SDCCHs. The intra-cell handovers are increased, if busy TCHFs are converted to SDCCHs.
2.28.3.2 TCH HR/FR Conversion

?.1. Overview
Dynamic TCH HR/FR conversion is performed in two cases: when the traffic load is high in a cell, certain full-rate (FR) TCHs are converted to half-rate (HR) TCHs to allow more MSs to access the network; when the traffic load is low, certain half-rate TCHs (TCHHs) are converted to the full-rate TCHs (TCHFs) to provide better speech quality to the MS users. This function is performed by using the TCH HR/FR rate adjustment algorithm. Dynamic TCH HR/FR conversion is performed in real time during the channel allocation. If a connection requires a TCHH but no idle TCHH is available in the cell, the BSC selects a TCHF to convert it into two TCHHs and then allocates one of them to the connection. If a connection requires a TCHF but no idle TCHF is available, the BSC selects a couple channel to convert it into a TCHF and then allocates the TCHF to the connection. If there is no couple channel available in the cell, the BSC selects a single channel, steers the traffic on the peer busy TCHH to another channel, and then combines two idle single channels into a couple channel. Then, the BSC converts the couple channel to a TCHF. The dynamic TCH HR/FR conversion function is enabled when TCH Rate Adjust Allow is set to Yes.
?.2. Rate Adjustment Algorithms for Different Channel Requests

The rate adjustment algorithm varies with different rate of requested channels. The required channel rate is defined in the channel assignment request as follows: l l l TCHF only TCHH only/TCHH preferred TCHF preferred
Figure 2-84 shows the channel assignment procedure when the channel rate type in a channel assignment request is TCHF only. The channel request is accepted in the following situations; otherwise, the channel request is rejected. l l If an idle TCHF is available, the BSC assigns the TCHF directly. If no idle TCHF is available but an idle couple channel is available (One timeslot carries two TCHHs. If both TCHHs are idle, they are called couple channels.), convert couple channels to TCHFs and allocate the TCHFs. If no idle TCHF or idle couple channel is available but an idle single channel is available (One timeslot carries two TCHHs. If one of them is occupied, the idle TCHH is called a single channel, channel fragment, or fragment), the BSC determines whether there is more than one idle and adjustable TCHH in the cell. If there is more than one idle TCHH in the cell, the BSC initiates the intra-cell handover. Then, the BSC converts the couple channel generated from the intra-cell handover to the TCHF and assigns the TCHF accordingly.
Issue 08 (2011-09-30)
391
Figure 2-84 Channel rate adjustment procedure for TCHF only
If the channel rate type in a channel assignment request is TCHH only/TCHH preferred, the channel request is accepted in the following situations; otherwise, the channel request is rejected. Figure 2-85 shows the channel rate adjustment procedure. l l l If an idle single channel is available, the BSC assigns the single channel directly. If no idle single channel is available but an idle couple channel is available, the BSC assigns the idle TCHH of the couple channel. If no idle single channel or couple channel is available but an idle TCHF is available, the BSC converts the TCHF to the couple channel and assigns the idle TCHH of the couple channel.
NOTE
If the BSC assigns single channels preferably, the TCHHs can be utilized optimally with the number of fragments reduced.
Issue 08 (2011-09-30)
392
Figure 2-85 Channel rate adjustment procedure for TCHH only/TCHH preferred
If the channel rate type in a channel assignment request is TCHF preferred, the channel request is accepted when the following requirements are met; otherwise, the channel request is rejected. Figure 2-86 shows the channel rate adjustment procedure. l l l If an idle TCHF is available, the BSC assigns the TCHF directly. If no idle TCHF is available but an idle couple channel is available, the BSC converts the couple channel to the TCHF and then assigns the TCHF. If no idle TCHF or couple channel is available but an idle single channel is available, the BSC determines whether there is more than one idle and adjustable TCHH in the cell. If there is more than one idle TCHH in the cell, the BSC initiates the intra-cell handover. Then, the BSC converts the couple channel generated from the intra-cell handover to the TCHF and assigns the TCHF accordingly. Otherwise, the BSC assigns the idle single channel.
Issue 08 (2011-09-30)
393
Figure 2-86 Channel rate adjustment procedure for TCHF preferred
NOTE
The calls on single channels can be handed over to other channels during the TCHH-to-TCHF conversion only when Enhanced TCH Adjust Allowed is set to Yes.
?.3. TCH HR/FR Conversion Procedures

This describes the TCHF-to-TCHH conversion and the TCHH-to-TCHF conversion.
TCHF-to-TCHH Conversion
1. If there is no TCHH available for a call that requests a TCHH, the channel request is queued. l If the queuing fails, then
For the TCHH-only request, a message is returned, indicating that the channel request fails. For the TCHH-preferred request, a less-preferred channel such as the couple channel or TCHF is allocated. l If the queuing is successful, then The BSC converts a TCHF to a couple channel and adjusts the corresponding channel attributes. Then, it issues the BSC timeslot conversion command, and starts the relevant performance measurement. 2. The BSC issues a channel type adjustment command to the BTS. The BSC timeslot adjustment command or the channel type adjustment command will be sent again upon timeout. On receiving the adjustment command, the BTS starts channel type adjustment. Once the channel type adjustment is complete, the BTS sends the Status Change Report to the BSC. On receiving the Status Change Report from the BTS, the BSC sets the couple channel to the idle state. Thus, the TCHF-to-TCHH conversion is complete. Then, the BSC assigns the converted channel to the call in the queue and starts the measurement of relevant performance statistics.
3. 4.
TCHH-to-TCHF Conversion
1. If a couple channel is available for a call that requests a TCHF, the channel request is queued. l If the queuing fails, then For the TCHF-only request, a message is returned, indicating that the channel request fails. For the TCHF-preferred request, a less-preferred channel such as a couple channel or a single channel is allocated. l If the queuing is successful, then The BSC converts the couple timeslots into a TCHF channel. For details about the subsequent procedures, see TCHF-to-TCHH Conversion. 2. If the single channel is available for a call that requests a TCHF, the channel request is queued. The duration for queuing is set to 5.5 seconds, including the time for adjusting the single channels to the couple channel. l If the queuing fails, then For the TCHF-only request, a message is returned, indicating that the channel request fails. For the TCHF-preferred request, the single channel is allocated. l If the queuing is successful, then The BSC steers the traffic in the busy peer TCHH channel of the single channel to another channel by initiating the forced intra-cell handover regardless of the settings of handover parameters. Different operations are performed based on whether a response to the forced handover is received. If the BSC receives the response to the forced handover, it determines whether the forced handover is successful. If the forced handover fails, the BSC allocates the single channel to another call in the queue and does not release the busy peer TCHH channel. If the forced handover is successful, the channel status is set to Waiting for
Releasing the Channel; when the channel status is Service Idle, the BSC converts the couple channel into a TCHF. If the BSC does not receive any response to the forced handover, the handover failure procedure is triggered.
2.28.3.3 Dynamic PDCH Conversion

?.1. Overview
Dynamic PDCH conversion consists of TCH-to-PDCH conversion and PDCH-to-TCH conversion, wherein the TCH may be the TCHF or TCHH. The process of dynamic PDCH conversion consists of two phases: PDCH conversion decision and PDCH conversion execution. See 2.40 GPRS/EGPRS Channel Management for the detailed information about TCH-to-PDCH conversion. If a TCH request is received when no idle TCH is available and there are PDCHs converted from the TCH in the cell, the BSC initiates the PDCH-to-TCH conversion. This function enables the dynamic balance between the CS load and the PS load, thus reducing the difficulties in planning the PS capacity of the cell. In addition, it lowers the possibility of PDCH waste and thus maximizes the utilization of radio channel resources.
?.2. Dynamic PDCH Conversion Procedure

Dynamic PDCH conversion consists of TCH-to-PDCH conversion and PDCH-to-TCH conversion.
NOTE
The following description is based on the external PCU. If the built-in PCU is configured, then the message interactions between the BSC and the PCU are not needed.
TCH-to-PDCH Conversion
Figure 2-87 shows the TCH-to-PDCH conversion procedure.
Issue 08 (2011-09-30)
396
Figure 2-87 TCH-to-PDCH conversion
1.
If there is no PS traffic channel available when an MS initiates the PS services, the PCU allocates a CS timeslot and retrieves the channel type, usage status, and the "whether PDCH assignment request can preempt the channels of CS services" flag of the timeslot. If the Channel Type of this timeslot is Dynamic PDCH and the flag "whether PDCH assignment request can preempt the channels of CS services" is "Yes", the system proceeds with the following procedures: l If the timeslot allocated by the PCU is idle, the BSC converts the channel on the timeslot to a PDCH, and then sends a message to the PCU indicating that the channel request is successful. l If the timeslot (half-rate or full-rate) allocated by the PCU is busy, the BSC determines whether to initiate the intra-cell handover. The intra-cell handover is not initiated if no idle timeslot is available in the cell or if the channel allocated by the PCU is a TCHH and only one idle timeslot is available in the cell. If an intra-cell handover cannot be initiated, the BSC determines whether the priority of the PS service is higher than that of the CS service.
2.
Issue 08 (2011-09-30)
397
If the priority of the PS service is higher, the BSC releases the channel on the allocated timeslot forcibly and converts the channel to a PDCH. If the priority of the CS service is higher, the BSC sends the request failure message to the PCU. If there are enough idle timeslots in the cell, the BSC initiates an intra-cell handover to steer the traffic on the timeslot to other timeslots. If the BSC initiates an intra-cell handover and the handover is successful, the channel on the allocated timeslot is converted to a PDCH. If the intra-cell handover fails, the BSC determines whether the priority of the PS service is higher. If the priority of the PS service is higher, the BSC releases the channel on the allocated timeslot forcibly and converts the channel to a PDCH. If the priority of the CS service is higher, the BSC sends the request failure message to the PCU.
NOTE
To avoid the triggering of a new intra-cell handover, during the channel conversion, the dynamic PDCH is not switched back and the system does not perform half-rate/full-rate adjustment, queuing or preemption.
If the intra-cell handover times out, the system determines whether the priority of the PS service is higher. If the priority of the PS service is higher, the BSC releases the channel on the allocated timeslot forcibly and converts the channel to a PDCH. If the priority of the CS service is higher, the BSC sends the request failure message to the PCU.
PDCH-to-TCH Conversion
CAUTION
l Factors such as the frequency band and concentric cell attribute are considered during dynamic PDCH-to-TCH conversion. l If the channel requested by the CS call is TCHH only and the TRX carrying the dynamic PDCH to be converted does not support channel rate adjustment, the dynamic PDCH is not converted to the TCH. l The BSC should not assign the dynamic PDCH for the CS services. Figure 2-88 shows the PDCH-to-TCH conversion procedure.
Issue 08 (2011-09-30)
398
Figure 2-88 PDCH-to-TCH conversion
NOTE
l During the dynamic conversion process, the calls are queued. Thus, if a call is placed in the queue before the BSC sends a channel request message to the PCU, the call will not be released until the queue timer expires. l If there is no call in the queue when the PCU releases the PDCH, the BSC converts the PDCH to the TCHF.
2.28.4 Parameters
This chapter describes the parameters related to dynamic channel conversion. For the meaning of each parameter, see Table 2-54. For the default value, value ranges, and MML commands of each parameter, see Table 2-55. Table 2-54 Parameter description (1) Parameter SDCCH Dynamic Allocation Allowed Idle SDCCH Threshold N1
Issue 08 (2011-09-30)
Description Whether to allow SDCCH dynamic allocation, that is, whether to allow dynamic conversion between TCHs and SDCCHs. When the number of idle SDCCH channels in a cell is smaller than or equal to this parameter, the system searches for available TCHs and transforms them into SDCCH channels.
Parameter
Description Maximum number of SDCCHs in the cell. Before converting a TCH into an SDCCH, the BSC compares the number of SDCCHs after the conversion in the cell with "Cell SDCCH Channel Maximum". If the number of SDCCHs after the conversion in the cell exceeds this parameter, the BSC does not convert the TCH into an SDCCH. Whether to allow the cell to dynamically change a channel from full rate to half rate or from half rate to full rate. If this parameter is set to YES, the conversion is allowed; if the parameter is set to NO, the conversion is not allowed and the changed channel is restored to the previous rate mode. In addition, this parameter helps to determine the channel assignment priority. The channels in a TRX that does not allow dynamic adjustment take priority. Whether to enable the cell to centralize two busy half rate TCHs in different timeslots into one timeslot through handover and then to combine the two idle half rate TCHs in the other timeslot into one full rate TCH dynamically Channel type of the timeslot on the TRX. The channel type of timeslot 0 must not be set, because the combined BCCH is configured by default. The channel type of other timeslots can be set to full-rate TCH or half-rate TCH.
Cell SDCCH Channel Maximum
TCH Rate Adjust Allow
Enhanced TCH Adjust Allowed
Channel Type
Table 2-55 Parameter description (2) Paramete r Default Value GUI Value Range Actual Value Range Unit MML Comman d SET GCELLB ASICPAR A (Optional) SET GCELLC HMGBAS IC (Optional) SET GCELLC HMGBAS IC (Optional) Impact
SDCCH Dynamic Allocation Allowed Idle SDCCH Threshold N1 Cell SDCCH Channel Maximum
YES
NO(No), YES(Yes)
NO, YES
None
Cell
0~63
0~63
None
Cell
80
0~255
0~255
None
Cell
Issue 08 (2011-09-30)
400
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GTRXDE V (Optional) SET GCELLC HMGBAS IC (Optional)
Impact
TCH Rate Adjust Allow Enhanced TCH Adjust Allowed
NO
NO(No), YES(Yes)
NO, YES
None
TRX
YES
NO(No), YES(Yes) FULLTC H (FULLTC H), HALFTC H (HALFTC H)
NO, YES
None
Cell
Channel Type
None
FULLTC H, HALFTC H
None
SET BTSCHN FALLBA CK (Mandator y)
BTS
2.28.5 Counters
2.28.6 Glossary

l l l l l l
BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.29 Easy GSM

2.29.1 Introduction
2.29.1.1 Scope
The Easy GSM solution includes the following functions: l l l Automatic Frequency Planning of Compact BTS Automatic Frequency Optimization of Compact BTS Automatic Capacity and Coverage Planning of Compact BTS
This document mainly describes the applicable scenarios and corresponding algorithm procedures of Easy GSM.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the Easy GSM feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30), issue 02 (2009-09-30) incorporates the changes described in the following table.
01 (2009-06-30)
This is the first commercial release of BSS9.0. Compared with issue 01 (2009-04-30) of BSS8.1, issue 01 (2009-06-30) of BSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. None. Parameter Change None. None.
2.29.2 Overview
Compact BTS applies to special application scenarios where the network structure is simple, the BTS is an isolated site, and the cells in such scenarios have few neighboring cells, such as in rural areas. The area where the BTS is located has inconvenient transportation, insufficient power facility, expensive transmission resources, and inadequate experienced maintenance personnel. Therefore, the cost of maintaining the BTS is high. If this type of BTS has such functions as automatic frequency configuration, planning, and optimization, the cost of operation and maintenance can be decreased. Easy GSM implements all these functions so that the automatic deployment of GSM network becomes possible. The function of automatic frequency planning of Compact BTS enables the automatic configuration of device data and service data of the BTS. After the hardware and software of a Compact BTS are installed, a connection between the BTS and the BSC is automatically established. In addition, the device data and service data of the BTS are automatically configured under the control of the BSC and M2000. The frequencies are also automatically configured.
NOTE
l Device data refers to the data configurations related to hardware, such as the board configurations and the parameter configurations related to boards. l Service data refers to the data configurations related to services. For the automatic frequency planning of Compact BTS, the service data mainly refers to the frequency resources.
Generally, the function of automatic frequency planning of Compact BTS applies to discontinuous coverage areas, and the cells in such areas have no neighboring cells.
Before the automatic frequency planning of Compact BTS is available, the operator has to preconfigure data on the controlling BSC of the BTS. Most configuration data, including the device data and service data but excluding the frequency data, can be automatically generated according to the data configuration template on the BSC maintenance terminal. The data that is not preconfigured is automatically configured during the automatic frequency planning of Compact BTS.
NOTE
The transmission-related data, such as the IP address and electronic serial number (ESN) of the BTS, is manually preconfigured.
After the data preconfiguration is complete, the operator resets the BTS to trigger the automatic frequency planning of Compact BTS. The system scans the radio environment of the current network, automatically configures cell parameters, and then starts operating. After the BTS starts operating, the surrounding radio environment may change, and the BTS operating with the automatically configured frequency data cannot provide services with desirable quality. In this case, the BTS automatically performs frequency adjustment and optimization under the control of the BSC and M2000. This process is referred to as the automatic frequency optimization of Compact BTS. In this case, if the function of automatic frequency optimization of Compact BTS is enabled, the system takes statistics on radio signal quality in real time. When the radio signal quality deteriorates to a value smaller than the preset threshold, the system automatically adjusts the frequency allocation to improve the radio signal quality of the BTS. In an application scenario of Compact BTS, the traffic volume is generally not high and a single frequency can meet the traffic requirement. After the BTS operates for a period of time, if the traffic model varies, the traffic volume changes accordingly. The BTS has to adjust the transmit power and the number of frequencies to meet the coverage and capacity requirements. The function of automatic capacity and coverage planning of Compact BTS can solve this problem. With this function, the BTS can take statistics on its traffic volume in real time. Then, based on the traffic volume and the parameter configurations, the BTS determines whether to add frequencies to meet the capacity and coverage requirements. The procedure for adjusting the capacity and coverage is automatically performed on the basis of the parameter configurations. In the case of traffic burst, handover between TCH HR and TCH FR or dynamic channel conversion should be implemented. For details, see 2.46 Handover and 2.28 Dynamic Channel Conversion.
NOTE
All the BTSs mentioned in this document are Compact BTSs.

2.29.3.1 Automatic Frequency Planning of Compact BTS
?.1. Overview
Based on its frequency band capability, the BTS scans the frequencies supported by the telecom operator. Then, the M2000 evaluates the interference on each frequency according to the sorting of the uplink and downlink receive levels. At the same time, the M2000 takes into account the interference between neighboring BTSs and selects a frequency with the minimum interference for the BTS to use.
When neighboring BTSs perform automatic frequency planning of Compact BTS, they may simultaneously contend for the same frequency. To prevent this, the M2000 can implement the mechanism that all the BTSs controlled by the same BSC and the neighboring BTSs are initialized in succession.
?.2. Algorithm
After the BTS performs uplink and downlink frequency scan, it sends the BSC and M2000 the information about the uplink and downlink receive levels of the scanned frequencies. The information then serves as the input of the automatic frequency planning of Compact BTS. Figure 2-89 shows the procedure for the automatic frequency planning algorithm of Compact BTS. Figure 2-89 Procedure for the automatic frequency planning algorithm of Compact BTS
1.
To prevent neighboring BTSs from selecting adjacent frequencies, the system obtains the uplink and downlink receive levels by adding the adjacent-channel interference to the uplink and downlink receive levels reported by the BTS. Based on the obtained uplink and downlink receive levels, the system calculates the interference strength on each frequency and then ranks the interference strength by priority. The system selects the frequency with the lowest interference priority from all the frequencies that can serve as the BCCH frequency. Then, the selected frequency is configured as the BCCH frequency of the current cell. If a BTS is configured with two frequencies, the frequency that has the lowest interference priority and is not adjacent to the BCCH frequency is configured as the TCH frequency.
2. 3.
?.3. Procedure
When the BTS Configuration Mode parameter is set to AUTO(AUTOPLAN) and both CGI and RAC Plan Switch and Freq. and BSIC Plan Switch are set to ON, the automatic frequency planning of Compact BTS is enabled.
NOTE
If either CGI and RAC Plan Switch or Freq. and BSIC Plan Switch is set to OFF, related data should be entered manually.
Figure 2-90 shows the procedure for the automatic frequency planning of Compact BTS. Figure 2-90 Procedure for the automatic frequency planning of Compact BTS
1.
Initializing BTSs in succession For all the BTSs controlled by the same BSC and the neighboring BTSs, only one BTS can be initialized at a time, that is, only one BTS performs the automatic frequency planning of Compact BTS at a time.
Issue 08 (2011-09-30)
406
2.
Uplink and downlink frequency scan The BTS reports its capability, including the supported frequency bands, to the M2000. The BSC reports the mobile country code (MCC) and mobile network code (MNC) to the M2000. According to the information reported by the BTS and BSC, the M2000 determines the frequency bands that should be scanned by the BTS. On the specified frequency bands, the BTS collects the uplink and downlink receive levels of each frequency.
3.
Automatic frequency planning of Compact BTS According to the uplink and downlink frequency scan result reported by the BTS, the M2000 automatically configures the BCCH frequency and TCH frequencies of the BTS.
2.29.3.2 Automatic Frequency Optimization of Compact BTS

?.1. Overview
When the BTS operates normally, the M2000 periodically monitors the frequencies based on the measurement reports from the MS and the measurement results about the uplink interference margin reported by the BTS. Then, the M2000 compares the data obtained through frequency monitoring with the interference proportion threshold and determines whether frequencies should be replaced. If a frequency has to be replaced, the automatic frequency optimization of Compact BTS is performed to select a new frequency based on the result of the latest ranking of interference priorities. The selected frequency must meet the following conditions: It is not adjacent to other frequencies in the cell; it has the lowest interference among all the available frequencies; it is supported by the BTS hardware.
?.2. Algorithm
Figure 2-91 shows the procedure for the automatic frequency optimization algorithm of Compact BTS.
Issue 08 (2011-09-30)
407
Figure 2-91 Procedure for the automatic frequency optimization algorithm of Compact BTS
When the parameter Freq. and BSIC Optimize Switch is set to ON(ON) on the BSC side and Frequency optimization algorithm is selected on the M2000 side, the automatic frequency optimization of Compact BTS is enabled. The procedure for the automatic frequency optimization algorithm of Compact BTS is as follows: 1. Downlink interference measurement Based on the measurement report from the MS, the BSC takes statistics on the interference to the frequency on the downlink. A valid measurement report contains the information
about the uplink receive level, downlink receive level, uplink receive quality, and downlink receive quality. Based on the measurement results, the BSC analyzes the radio coverage and interference in a cell. If it is always the case that the receive level is high but the receive quality is poor, interference may have occurred. If it is always the case that the receive level is low and the receive quality is poor, radio coverage may be insufficient. Based on the ratio of the number of times that the downlink receive level grade and receive quality grade are higher than the specified values to the total number of times that the downlink receive level and receive quality are measured, the system determines whether interference occurs on the downlink channels of the frequency. Downlink interference measurement result can be quantified as a value, which serves as the basis for determining the interference strength on the downlink.
NOTE
l High receive level grade indicates good receive level. l High receive quality grade indicates poor receive quality.
2.
Uplink interference measurement The BSC measures the uplink interference on a frequency. The RF RES IND message from the BTS to the BSC carries the interference margin levels of all the idle channels on a frequency. The BSC takes statistics on all the performance counters based on the channel type (TCHF, TCHH, or SDCCH) and the interference margin levels (1 to 5) carried in the message. In a measurement period, the BSC learns the distribution of the interference margins by dividing the values of the performance counters by the number of sampling times. Generally, if an idle channel falls in interference margin level 4 or 5, the system considers that interference occurs on the channel. Uplink interference measurement result can be quantified as a value, which serves as the basis for determining the interference strength on the uplink.
3.
Automatic frequency optimization of Compact BTS The automatic frequency optimization of Compact BTS is performed in the specified period every day, and the start time of the optimization is specified by Start Time. The automatic frequency optimization of Compact BTS and the adjustment of radio parameters affect the ongoing services. Thus, it is recommended that the automatic frequency optimization be performed when the traffic is light. The automatic frequency optimization of Compact BTS is triggered by any of the following conditions: l The downlink interference measurement value is greater than or equal to the downlink frequency interference proportion threshold, and the total traffic volume in a measurement period is greater than or equal to Traffic threshold of downlink interference decision. l The uplink interference measurement value is greater than or equal to the uplink frequency interference proportion threshold.
4.
Restart of the automatic frequency planning of Compact BTS After the BTS operates for a period of time, the original results of uplink and downlink frequency scan may be quite different from the actual interference. In this case, the BTS has to periodically scan the uplink and downlink frequencies to obtain the latest interference and to provide accurate data for automatic frequency optimization. During the automatic frequency optimization, the automatic frequency planning of Compact BTS is started if the BTS determines that a frequency has to be replaced and if any of the following conditions is met:
Issue 08 (2011-09-30)
409
l Number of frequency replacements Threshold of Freq Change Times l Period between the time of the previous frequency planning and the current time Freq Replanning Period
2.29.3.3 Automatic Capacity and Coverage Planning of Compact BTS

?.1. Overview
The automatic capacity and coverage planning of Compact BTS mainly applies to simple network structure. Initially, the BTS is configured with a single frequency. As the traffic volume increases, the system may activate another frequency by performing the automatic capacity and coverage planning of Compact BTS and distribute transmit power between the two frequencies. During the automatic capacity and coverage planning of Compact BTS, the system monitors the traffic volume in real time. If the traffic volume reaches Start Double-Carrier Load Threshold, adjustment is performed to increase the traffic capacity. Currently, the automatic capacity and coverage planning of Compact BTS applies only to one or two frequencies.
?.2. Algorithm
Figure 2-92 shows the procedure for the automatic capacity and coverage planning algorithm of Compact BTS. When the parameter Capacity and Coverage Optimize Switch is set to ON(ON) on the BSC side and the Coverage optimization algorithm check box is selected on the M2000 side, the automatic capacity and coverage planning of Compact BTS is enabled.
Issue 08 (2011-09-30)
410
Figure 2-92 Procedure for the automatic capacity and coverage planning algorithm of Compact BTS
After the automatic capacity and coverage planning of Compact BTS is enabled, the M2000 measures the average TCH usage in three peak hours during Capacity Expansion Statistical Period. After the measurement, the M2000 compares the average TCH usage with Start Double-Carrier Load Threshold. If the average TCH usage is greater than Start DoubleCarrier Load Threshold, the M2000 automatically configures two frequencies for the cell. After the two frequencies operate normally, the BCCH frequency and the TCH frequency share the transmit power. l If the load on BCCH frequency Threshold of BCCH Load Congestion, and the load on BCCH frequency - the load on TCH frequency Threshold of Load Difference Between BCCH and TCH, then the BTS reduces the transmit power of the BCCH frequency and increases the transmit power of the TCH frequency. If the load on TCH frequency Threshold of TCH Load Congestion, and the load on TCH frequency - the load on BCCH frequency Threshold of Load Difference Between TCH and BCCH, then the BTS reduces the transmit power of the TCH frequency and increases the transmit power of the BCCH frequency.
2.29.4 Dependency
The BTS, BSC, and M2000 should work together to implement Easy GSM. l l The BTS performs radio environment measurement and collects the related information. The M2000 is the major NE to implement the automatic frequency planning and optimization functions. It analyzes and calculates the data reported by the BTS and performs automatic frequency allocation. The BSC transfers the data transmitted between the BTS and the M2000.

The following parameters should be configured on the M2000 to support the automatic frequency planning of Compact BTS: l Operator frequency data This parameter specifies the frequencies that a telecom operator can allocate to BTSs. BTSs select proper BCCH frequencies and TCH frequencies from these frequencies. The operator frequency data consists of the mobile country code (MCC), the mobile network code (MNC), and the start frequency and end frequency of a frequency band. The operator frequency data should be preconfigured. l Base transceiver station identify code (BSIC) data This parameter specifies the ranges of BCCs and NCCs that a telecom operator allows BSCs to use. l Cell global identification (CGI) resource data This parameter specifies the range of CGIs that BSCs allow BTSs to use. This helps BTSs to choose CGIs during the automatic frequency planning of Compact BTS. The CGIs configured on the M2000 are not delivered to the MSC and they are applicable only to the automatic frequency planning of Compact BTS. To ensure that the CGIs obtained through the automatic frequency planning of Compact BTS are valid, you should predefine the value range of the CGIs corresponding to each LAC at the MSC. The value range of the CGIs predefined at the MSC must include the value range of the CGIs configured on the M2000. The following parameters should be configured on the BSC maintenance terminal to support the automatic frequency planning of Compact BTS: l BTS Configuration Mode If a BTS needs to support the automatic frequency planning of Compact BTS, this parameter should be set to AUTO(AUTOPLAN). If a BTS need not support the automatic frequency planning of Compact BTS, this parameter should be set to NORMAL(NORMAL). The default value is NORMAL(NORMAL). l Freq. and BSIC Optimize Switch If a BTS needs to support the automatic frequency optimization of Compact BTS, this parameter should be set to ON(ON). If a BTS need not support the automatic frequency optimization of Compact BTS, this parameter should be set to OFF(OFF). The default value is OFF(OFF). l Capacity and Coverage Optimize Switch If a BTS needs to support the automatic capacity and coverage planning of Compact BTS, this parameter should be set to ON(ON). If a BTS need not support the automatic capacity and coverage planning of Compact BTS, this parameter should be set to OFF(OFF).
Maximum TRX Number This parameter specifies the maximum number of frequencies supported by the automatic frequency planning of Compact BTS. Currently, the maximum number is 2. The default value is 1.
2.29.6 Parameters
This chapter describes the parameters related to Easy GSM. For the meaning of each parameter, see Table 2-56. For the default value, value ranges, and MML commands of each parameter, see Table 2-57. Table 2-56 Parameter description (1) Parameter BTS Configuration Mode CGI and RAC Plan Switch Freq. and BSIC Plan Switch Capacity and Coverage Optimize Switch Freq. and BSIC Optimize Switch Description BTS configuration modes include auto plan mode and normal mode. In auto plan mode, the user can enable the auto planning algorithms and auto optimization algorithms according to the BTS type. In normal mode, the auto planning algorithms and auto optimization algorithms are disabled. If the parameter is set to 1, it indicates that the CGI and RAC data is generated through automatic planning. If the parameter is set to 0, it indicates that the data needs to be manually entered. If this switch is on, it indicates that the frequency and BSIC are generated automatically. If this switch is off, it indicates that the data must be configured manually. Whether to enable the capacity and coverage of the BTS to be automatically optimized according to the actual situation of the incumbent network. Whether to generate the frequency and BSIC by using the automatic optimization algorithm Maximum number of TRXs that can be configured for one cell. For the BTS3900B GSM, when the "Frequency and BSIC Plan Switch" is ON, the "Maximum TRX Number" (one or two, one by default) can be selected. For the BTS3900E GSM, when the "Capacity and Coverage Optimize Switch" is OFF, the "Maximum TRX Number" (one or two, one by default) can be selected.
Maximum TRX Number
Issue 08 (2011-09-30)
413
Table 2-57 Parameter description (2) Paramete r Default Value GUI Value Range AUTO (AUTOPL AN), NORMAL (NORMA L) Actual Value Range Unit MML Comman d SET BTSAUT OPLANC FG (Mandator y) SET BTSAUT OPLANC FG (Optional) SET BTSAUT OPLANC FG (Optional) SET BTSAUT OPLANC FG (Optional) SET BTSAUT OPLANC FG (Optional) ADD BTSAUT OPLAN (Mandator y) SET BTSAUT OPLANC FG (Optional) Impact
BTS Configurat ion Mode
None
AUTO, NORMAL
None
BTS
CGI and RAC Plan Switch
None
OFF (OFF), ON (ON)
OFF, ON
None
Cell
Freq. and BSIC Plan Switch Capacity and Coverage Optimize Switch Freq. and BSIC Optimize Switch
None
OFF (OFF), ON (ON)
OFF, ON
None
Cell
None
OFF (OFF), ON (ON)
OFF, ON
None
BTS
None
OFF (OFF), ON (ON)
OFF, ON
None
Cell
Maximum TRX Number
1~2
1~2
None
Cell
The following parameters are configured on the M2000: l l Operator frequency data BSIC data
Issue 08 (2011-09-30)
414
l l l l l l l l l l l l
CGI resource data Frequency optimization algorithm Coverage optimization algorithm Start Time Threshold of Freq Change Times Freq Replanning Period Start Double-Carrier Load Threshold Threshold of BCCH Load Congestion Threshold of Load Difference Between BCCH and TCH Capacity Expansion Statistical Period Threshold of TCH Load Congestion Threshold of Load Difference Between TCH and BCCH
2.29.7 Counters
2.29.8 Glossary

None.
2.30 EFR
2.30.1 Introduction
2.30.1.1 Scope
This document describes the improvement of EFR on FR and HR.

Issue 08 (2011-09-30)

This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the EFR feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.30.2 Overview
With the development of the GSM network, subscribers have increasing requirements for high speech quality. Thus, enhanced full rate (EFR) is adopted. In comparison to FR, EFR optimizes the speech codec algorithm and improves the speech quality, thus improving the user experience.

2.30.3.1 Improvement of EFR on FR and HR

EFR is implemented on the basis of the Code Excited Linear Prediction (CELP). FR and HR, however, are implemented on the basis of Regular Pulse Excited - Linear Predictive Coder (RPELPC). The differences between CELP and RPE-LPC are as follows: In the CELP model, the excitation signal is a quantified vector. A group of codevectors that are obtained in advance through calculation forms a codebook. For each frame of speech signals, a codevector with the minimum perceptually weighted error is selected from the codebook to serve as the irregular excitation source. In the RPE-LPC model, a regular excitation source such as the sine wave is adopted, and thus the speech lacks clarity. The Speech Version parameter specifies whether to enable EFR. The EFR function can be enabled forcibly on the BSC. That is, when the BSC determines that the circuit pool on the A interface and the MS support the EFR, the BSC can actively selects the EFR as the speech version to improve the speech quality if the speech versions carried in the Assignment Request message do not include the EFR. The parameter Allow Forced EFR in Cell specifies whether the EFR function can be forcibly enabled.
2.30.3.2 TFO
When EFR is enabled, the BTS is not involved in Tandem Free Operation (TFO), but the TFO switch on the BSC side should be turned on. You can set TFO Switch to Open to enable the TFO function.
2.30.4 Parameters
This chapter describes the parameters related to EFR. For the meaning of each parameter, see Table 2-58. For the default value, value ranges, and MML commands of each parameter, see Table 2-59. Table 2-58 Parameter description (1) Parameter Description Speech version configured on the TRX timeslot when the BTS works in fallback mode. When "CHNTYPE" of the TRX timeslot is set to "FULLTCH", value 0 of this parameter indicates FR and value 1 indicates EFR; when "CHNTYPE" of the TRX timeslot is set to "HALFRCH", this parameter is invalid. Whether to enable the Tandem Free Operation (TFO) function on the BTS through a CHANNEL ACTIVATION or MODE MODIFY message. This parameter specifies whether to enable the Tandem Free Operation (TFO) function. If the voice quality of an ongoing MS-to-MS call is bad, the TFO function can be enabled to improve end-to-end voice quality. The TFO function cannot be used to improve the voice quality of an MS-to-PSTN call.
Speech Version
TFO Switch
Issue 08 (2011-09-30)
417
Parameter
Description Whether to forcibly enable the EFR function. When this parameter is set to YES, if both the MS and the BSC6900 support the enhanced full rate (EFR), the BSC6900 forcibly enables the EFR function even if the MSC does not support the function.
Allow Forced EFR in Cell
Table 2-59 Parameter description (2) Parameter Defaul t Value GUI Value Range Actual Value Range Uni t MML Comm and SET BTSCH NFALL BACK (Manda tory) SET GCELL BASIC PARA (Option al) SET GCELL SOFT (Option al) Impact
Speech Version
FR
FR(FR), EFR(EFR)
FR, EFR
Non e
BTS
TFO Switch
DISAB LE
DISABLE (Disable), ENABLE (Enable)
DISABLE, ENABLE
Non e
Cell
Allow Forced EFR in Cell
NO
NO(No), YES(Yes)
NO, YES
Non e
Cell
2.30.5 Counters
2.30.6 Glossary

l l l
Issue 08 (2011-09-30)
GSM 08.08: "Digital cellular telecommunications system (Phase 2+)" GSM 08.58: "Digital cellular telecommunications system (Phase 2+)" GSM 04.08: "Digital cellular telecommunications system (Phase 2+)"
l l l l l l
BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.31 EGPRS2
2.31.1 Introduction
2.31.1.1 Scope
This document describes the modulation scheme, coding scheme, link quality control, carrier allocation algorithm, and channel allocation algorithm in the EGPRS2 feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the EGPRS2 feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Version
The document issues are as follows: l l
Issue 08 (2011-09-30)
02 (2009-09-30) 01 (2009-06-30)
02 (2009-09-30)
01 (2009-06-30)
2.31.2 Overview
Currently, the GSM network is the most widely used cellular communication network in the world. To protect the investment of the operators and to attract more subscribers towards the 3G services, the GSM network needs to support a higher data rate during its evolution to WCDMA and LTE. In this case, the enhanced general packet radio service 2 (EGPRS2) is introduced. The EGPRS2 is evolved from EGPRS. It improves the throughput on the downlink and the uplink in the GSM EDGE Radio Access Network (GERAN). EGPRS2 uses such technologies as high order modulation, high symbol rate (HSR), and Turbo codes to obtain higher uplink and downlink data rates than the EGPRS. EGPRS2 is an evolution of the EGPRS function. By implementing the high order modulation, HSR, and Turbo codes, EGPRS2 obtains higher uplink and downlink data rates than EGPRS. EGPRS2 is classified into EGPRS2-A and EGPRS2-B. l EGPRS2-A: In the downlink direction, EGPRS2-A increases the data rate by using the Turbo codes and 16 quadrature amplitude modulation (16QAM)/32QAM modulation scheme. In the uplink direction, EGPRS2-A increases the data rate by using the 16QAM modulation scheme. In addition, EGPRS2-A uses the gaussian minimum shift keying (GMSK) and 8 phase shift keying (8PSK) modulation schemes to ensure compatibility with the EGPRS. EGPRS2-B: In the downlink direction, EGPRS2-B increases the data rate by using the HSR, Turbo codes, and QPSK/16QAM/32QAM modulation scheme. In the uplink direction, EGPRS2-B increases the data rate by using the HSR and QPSK/16QAM/32QAM modulation scheme. In addition, EGPRS2-B uses the GMSK and 8PSK modulation schemes to ensure compatibility with the EGPRS.
Currently, Huawei GBSC supports only EGPRS2-A. In addition, Huawei GBSC supports EGPRS2-A only when IP/HDLC transmission is adopted on the Abis interface. In theory, EGPRS2-A increases the data rate of the PS services in the downlink and uplink respectively to 1.66 times and 1.3 times of that in EGPRS.
In the downlink, the BTS supports the 16QAM and 32QAM modulation schemes. Thus all PDCHs support EGPRS2-A services. In the uplink, the BTS supports only the 16QAM modulation scheme. Thus not all PDCHs support EGPRS2-A services. The support capability of the uplink EGPRS2-A is restricted by the baseband processing capability of the BTS. That is, the BSC determines the allocation of EGRPS2-A TRXs and channels based on the baseband processing capability reported by the BTS. To ensure compatibility with the GPRS and EGPRS, the BSC supports the multiplexing of GPRS MS and EGPRS MS on the same PDCH channel with the EGPRS2 MS. The BSC allocates the EGPRS level to the MS based on the radio access capability of the MS by sending the EGPRS Level message to the MS through the resource allocation procedure. The BSC also supports the switching between EGPRS levels at the same time. The link quality control algorithm should support EGPRS2-A because new modulation schemes and coding schemes are added to EGPRS2-A. In addition, the radio block format in EGPRS2, coding schemes, retransmission mechanism of radio link control (RLC) data blocks, EGPRS2A assembly of RLC data blocks, and segmentation of logical link control packet data units (LLC PDUs) in EGPRS2-A should be supported during data transmission. The MS should support EGPRS2-A.

2.31.3.1 Modulation Schemes and Coding Schemes
?.1. EGPRS2-A Modulation Schemes
In the downlink direction, EGPRS2-A uses the Turbo codes and 16QAM/32QAM modulation schemes. In the uplink direction, EGPRS2-A uses the convolutional codes and 16QAM modulation scheme. Symbol rate used on EGPRS2-A uplink/downlink is normal symbol rate (NSR). In addition, EGPRS2-A uses the GMSK and 8PSK modulation schemes to ensure compatibility with the EGPRS. Compared with the 8PSK and GMSK, the QAM increases the peak cell rate and average bit rate and features higher anti-interference capability. Compared with the convolutional codes, the Turbo codes increase the average bit rate. In addition, the Turbo codes have a higher error correction capability. The combination of Turbo codes and QAM modulation scheme further increase the peak throughput and C/I gain. Compared with the 8PSK and GMSK, the 16QAM allows lower coding rate (because of the higher modulation bit rate). Thus, the data throughput and C/I gain are increased. Compared with the 16QAM, the 32QAM has higher peak cell rate. Compared with the 8PSK, the 32QAM obtains a channel coding scheme that is more robust than the existing MCS coding scheme. The 16QAM uses four modulation bits to map a symbol. The 16QAM has a total of 16 symbols. The 32QAM uses five modulation bits to map a symbol. The 32QAM has a total of 32 symbols. Figure 2-93 shows the signal constellations of the QAM.
Figure 2-93 Signal constellations of the QAM (left: 16QAM; right: 32QAM)
Table 2-60 lists the peak-average ratios (PARs) of different modulation schemes, PAR is the ratio of the peak power to the average power. . Table 2-60 PARs of different modulation schemes Modulation Scheme 8PSK with 3/8 rotation 16QAM 16QAM with /4 rotation 32QAM PAR (dB) 3.3 5.9 5.3 5.7
NOTE
"8PSK with 3/8 rotation" indicates that each symbol of the 8PSK is rotated in a radian of 3/8 before the pulse is formed. "16QAM with /4 rotation" indicates that each symbol of the 16QAM is rotated in a radian of /4 before the pulse is formed.
The following factors can cause the decrease in the power of signals modulated in the high order modulation scheme: l l An increase in the power back-off of the power amplifier (PA) because the PAR of the high order modulation is high A decrease in the output power of the PA because the requirements of the high order modulation for the EVM counters are higher
In view of the preceding factors, the EGPRS2 transceiver should use the power that is 26 dB less than the average power in the GMSK when sending the signals modulated in the 16QAM or 32QAM. 16QAM Transmitter Power Reduce Level and 32QAM Transmitter Power Reduce Level are set to specify the BTS output power decrease value in 16QAM or 32QAM. Table 2-61 lists the maximum output power decrease value in different modulation schemes.
Issue 08 (2011-09-30)
422
Table 2-61 Maximum output power decrease value in different modulation schemes EGPRS Level EGPRS EGPRS2-A EGPRS2-A Modulation Scheme 8PSK 16QAM 32QAM Output Power Decrease 4 dB 6 dB 6 dB
In the case of Huawei double-transceiver series BTS and distributed BTS, set Diversity Transmitter 16QAM Delay and Diversity Transmitter 32QAM Delay to specify the delay of the diversity signal relative to the main signal in 16QAM and 32QAM so as to increase the RX signal gain of the MS.
?.2. EGPRS2-A Coding Schemes

In the downlink direction, eight coding schemes are introduced to EGPRS2-A: EGPRS2 downlink level A modulation and coding scheme-5 (DAS-5) to DAS-12. These coding schemes are used to transmit downlink RLC data blocks in the EGPRS2-A radio blocks. EGPRS2-A also has the coding schemes modulation and coding scheme-1 (MCS-1) to MCS-4 and MCS-6 to MCS-8 in the downlink direction. MCS-1 to MCS-4 are used to retain the complete structure of the coding scheme family. MCS-6 is used for the retransmission of the RLC data when EGPRS is changed to EGPRS-A. MCS-7 and MCS-8 are used for the multiplexing of the EGPRS MS and EGPRS2-A MS on the PDCH so that the EGPRS MS can decode the USF or PAN in the radio blocks of the downlink EGPRS2-A. In the uplink direction, five coding schemes are introduced to EGPRS2-A: EGPRS2 uplink level a modulation and coding scheme-7 (UAS7)-UAS-11. These coding schemes are used to transmit uplink RLC data blocks in the EGPRS2-A radio blocks. EGPRS2-A also has the coding schemes MCS-1 to MCS-6 are in the uplink direction to retain the complete structure of the coding scheme family. Table 2-62 and Table 2-63 show the relations among the coding scheme, modulation scheme, and data rate per PDCH of the downlink EGPRS2-A and uplink EGPRS2-A respectively. Table 2-62 Relations among the coding scheme, modulation scheme, and data rate per PDCH of the downlink EGPRS2-A Coding Scheme Code Rate Modulati on Scheme RLC Blocks per Radio Block 3 3 2 16QAM NSR 2 Raw Data Within one Radio Block (bits) 1968 1632 1312 1088 Famil y Data Rate per PDCH (kbit/s) 98.4 81.6 65.6 54.4
DAS-12 DAS-11 DAS-10 DAS-9
0.96 0.80 0.64 0.68
32QAM NSR
Bp Ap Bp Ap
Issue 08 (2011-09-30)
423
Coding Scheme
Code Rate
Modulati on Scheme
RLC Blocks per Radio Block 2
Raw Data Within one Radio Block (bits) 896 656 544 448
Famil y
Data Rate per PDCH (kbit/s) 44.8 32.8 27.2 22.4
DAS-8 DAS-7 DAS-6 DAS-5
0.56 0.54 0.45 0.37 8-PSK
B Bp Ap B
1 1 1
NOTE
In the previous table, Code Rate refers to the coding rate when the piggy-backed ack/nack (PAN) field is not carried in radio blocks.
Table 2-63 Relations among the coding scheme, modulation scheme, and data rate per PDCH of the uplink EGPRS2-A Coding Scheme Code Rate Modulati on Scheme RLC Blocks per Radio Block 3 3 2 2 2 Raw Data Within One Radio Block (bits) 1536 1344 1184 1024 896 Famil y Data Rate per PDCH (kbit/s) 76.8 67.2 59.2 51.2 44.8
UAS-11 UAS-10 UAS-9 UAS-8 UAS-7
0.95 0.84 0.71 0.62 0.55
16QAM Normal Symbol Rate (NSR)
Apad1 0 B A Apad1 0 B
NOTE
In the previous table, Code Rate refers to the coding rate when the PAN field is not carried in radio blocks.
2.31.3.2 Link Quality Control

?.1. Overview
The link quality control enables the system to dynamically adapt to the radio transmission environment by changing the modulation scheme and coding scheme during data transmission,
thus improving the link quality and increasing the data throughput. EGPRS uses a set of highefficient link quality control algorithms. The two link quality control modes are link adaptation (LA) and incremental redundancy (IR). For details, see 2.42 GPRS/EGPRS Link Quality Control. The link quality control mechanism of EGPRS2 is nearly the same as that of EGPRS. The link quality control algorithm of EGPRS2, however, should be optimized on the basis of the link quality control algorithm of EGPRS because new modulation schemes and coding schemes are added to EGPRS2. Currently, only the link quality control algorithm of EGPRS2-A is supported, which includes the uplink EGPRS2-A coding scheme adjustment algorithm and downlink EGPRS2-A coding scheme adjustment algorithm.
?.2. Uplink EGPRS2-A Coding Scheme Adjustment Algorithm

The BSC adjusts the uplink EGPRS coding scheme according to the uplink bit error probability (BEP) measurement report sent by the BTS.BEP is the measured value of the EGPRS radio link quality. The link quality measurement is performed at the burst level. The BEP measurement report is carried when the BTS sends uplink data frames or information frames over the Abis interface. The BEP measurement report contains mean of the bit error probability (MEAN_BEP) and coefficient of variation of the bit error probability (CV_BEP). MEAN_BEP is the mean of the calculated and filtered BEP values. CV_BEP is the measured value of the calculated and filtered coefficient variation of the BEP. For details, see 3GPP TS 45.008. Upon receiving the uplink data frame from the BTS, the BSC triggers the uplink EGPRS2-A coding scheme adjustment procedure if the BSC detects the change in the current link quality according to the measurement report. When the BTS cannot decode the uplink radio blocks correctly, it sends the BSC an uplink information frame that carries the BEP measurement report. After receiving the uplink information frame, the BSC triggers the uplink EGPRS2-A coding scheme adjustment procedure. The principles of the uplink EGPRS2-A coding scheme adjustment algorithm are as follows: 1. The BSC determines whether to use the fixed EGPRS2-A coding scheme in the uplink based on the setting of Uplink EGPRS2-A Fixed MCS Type. If the fixed EGPRS2-A coding scheme is used, the uplink coding scheme is specified by Uplink EGPRS2-A Fixed MCS Type. Otherwise, the initial uplink coding scheme is specified by Uplink EGPRS2A Default MCS Type. Later, the BSC adjusts the uplink coding scheme according to the uplink BEP measurement report sent by the BTS. If the non-fixed EGPRS2-A coding scheme is used in the uplink, the BSC filters the uplink BEP measurement report. Then, the uplink EGPRS2-A coding scheme is adjusted according to the filtered MEAN_BEP and CV_BEP. The algorithm is nearly the same as that in EGPRS. For details, see 2.42 GPRS/EGPRS Link Quality Control. The modulation scheme may change during the EGPRS2-A coding scheme adjustment. To enhance the stability of coding scheme adjustment and to prevent ping-pong switchovers of modulation schemes, the leaky bucket algorithm is used when the low order scheme is switched to the high order scheme. The basic principles of the leaky bucket algorithm are as follows: Each time the coding scheme is switched from a low order scheme to a high order scheme between GMSK, 8PSK, and 16QAM, the bucket size increases; each time the coding scheme is adjusted within the low order schemes (relative to the schemes to which the low order scheme is switched), the bucket size decreases. The switching from a low order scheme to a high order scheme is allowed only when the bucket size reaches a specific value.
2.
3.
Issue 08 (2011-09-30)
?.3. Downlink EGPRS2-A Coding Scheme Adjustment Algorithm

The MS periodically measures the downlink quality and filters the measured values to generate the link quality MR of the downlink EGPRS2. The filtering period for the downlink quality measurement is defined by the parameter Bep Period. Then, the BSC broadcasts the system information (SI) that contains the BEP period to the MSs. The link quality MR of the downlink EGPRS2 is carried in the EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message sent by the MS to the BSC. After receiving the EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message, the BSC adjusts the downlink EGPRS2 coding scheme according to the BEP measurement report in the message. The principles of the downlink EGPRS2-A coding scheme adjustment algorithm are as follows: 1. The BSC determines whether to use the fixed EGPRS2-A coding scheme in the downlink based on the setting of Downlink EGPRS2-A Fixed MCS Type. If the fixed EGPRS2-A coding scheme is used, the downlink coding scheme is specified by Downlink EGPRS2A Fixed MCS Type. Otherwise, the initial downlink coding scheme is specified by Downlink EGPRS2-A Default MCS Type. Later, the BSC dynamically adjusts the downlink coding scheme according to the downlink BEP MR sent by the MS. If the non-fixed EGPRS2-A coding scheme is used, the BSC obtains the MEAN_BEP and CV_BEP corresponding to the current modulation mode used by the downlink TBF from the EGPRS PACKET DOWNLINK ACK/NACK TYPE2 message. Then, the BSC adjusts the downlink EGPRS2-A coding scheme according to the MEAN_BEP and CV_BEP using the same algorithm as in the EGPRS. For details, see 2.42 GPRS/EGPRS Link Quality Control.
2.
2.31.3.3 EGPRS Level Selection and Switching

When the MS initiates one phase access, the BSC cannot obtain the radio access capability of the MS, and thus does not know the capability of the MS for supporting EGPRS2 and EGPRS2A. In this case, the EGPRS level is EGPRS by default. Later, if the BSC knows the capability of the MS for supporting EGPRS2-A, the BSC initiates the switching of EGRPS levels.
EGPRS Levels and Selection

EGPRS level consists of EGPRS and EGPRS2-A. Each EGPRS level has its own modulation mode set and coding scheme set, as shown in the following section: l l EGPRS: coding scheme (MCS-1 to MCS-9); modulation mode (GMSK or 8PSK) EGPRS2-A: uplink coding scheme (MCS-1 to MCS-6 or UAS-7 to UAS-11); uplink modulation mode (GMSK, 8PSK, or 16QAM NSR); downlink coding scheme (MCS-1 to MCS-4, MCS-6 to MCS-8, or DAS-5 to DAS-12); downlink modulation mode (GMSK, 8PSK, 16QAM NSR, or 32QAM NSR)
The BSC determines the EGPRS level of the TBF according to the radio access capability of the MS. The EGPRS level of the uplink TBF and that of the downlink TBF are independent of each other. The principles of selecting EGPRS levels are as follows: l l If the MS supports EGPRS, the EGPRS level of the TBF is set to EGPRS. If the MS supports EGPRS2-A in the uplink or downlink direction, the EGPRS level of the TBF in the corresponding direction is set to EGPRS or EGPRS2-A.
After determining the EGPRS level of the TBF, the BSC notifies the MS of the EGPRS level through the PACKET DOWNLINK ASSIGNMENT, PACKET UPLINK ASSIGNMENT, or
PACKET TIMESLOT RECONFIGURE message. Then, the MS uses the specified EGPRS level for the corresponding TBF.
EGPRS Level Switching

1. EGPRS level switching of the uplink TBF In the case of the uplink TBF, the BSC determines the EGPRS level to which the MS needs to switch. If EGPRS level switching is required, the BSC notifies the MS of the new EGPRS level through the PACKET TIMESLOT RECONFIGURE message. 2. EGPRS level switching of the downlink TBF In the case of the downlink TBF, the BSC determines the EGPRS level to which the MS needs to switch. If EGPRS level switching is required, the BSC notifies the MS of the EGPRS level through the PACKET TIMESLOT RECONFIGURE message.
2.31.3.4 Carrier Allocation Algorithm

The BSC allocates the EGPRS2-A carriers according to the baseband capability reported by the BTS. The application scenario of the cell is defined by the parameter Cell Scenario. The BTS optimizes the resource allocation according to the specific cell scenario to improve the overall processing capability. The principles of the EGPRS2-A carrier allocation algorithm are as follows: 1. The BSC calculates the maximum number of EGPRS2-A carriers that the TRX group supports on the basis of the baseband processing capability of the TRX group (reported by the BTS). The baseband processing capability of the TRX group indicates the maximum amount of arithmetic operations required by the baseband algorithm of the multi-carrier module. The BSC determines the uplink EGPRS2-A capability of the TRXs in the TRX group. The TRXs that meet the following conditions are selected to support the uplink EGPRS2-A: (1) The parameter EGPRS2-A determines whether the cell where the TRX is located supports EGPRS2-A. (2) The number of TRXs selected to support the uplink EGPRS2-A is smaller than the maximum number of TRXs that can support the uplink EGPRS2-A. (3) If all the preceding conditions are met, the TRXs are allocated by TRX ID in an ascending order to support the uplink EGPRS2-A. 3. The BTS determines the downlink EGPRS2-A capability of the TRXs in the TRX group. The TRXs that meet the following conditions are selected to support the downlink EGPRS2-A: (1) The parameter EGPRS2-A determines whether the cell where the TRX is located supports EGPRS2-A. (2) The uplink EGPRS2-A capable TRXs are preferentially selected to support the downlink EGPRS2-A. In addition, the uplink EGPRS2-A capable TRXs are allocated by TRX ID in an ascending order to support the downlink EGPRS2-A.
2.
2.31.3.5 Channel Allocation Algorithm

The BSC determines the allocation of TRXs for EGPRS2-A services according to the baseband capability reported by the BTS. If a TRX is allocated to support EGPRS2-A services, all the
channels on the TRX can support EGPRS2-A. The BSC determines whether to allocate the EGPRS2-A channel based on the EGPRS2-A capabilities of the TRX and the MS. The allocation of uplink EGPRS2-A channels must meet the following conditions: 1. 2. The MS supports uplink EGPRS2-A. The TRX carrying the channel supports uplink EGPRS2-A.
The allocation of downlink EGPRS2-A channels is based on the following conditions: 1. 2. The MS supports downlink EGPRS2-A. The TRX carrying the channel supports downlink EGPRS2-A.
If the EGPRS2-A capable MS is allocated a PDCH on the GPRS TRX or a PDCH on the EGPRS TRX, dynamic TCH conversion is triggered on the EGPRS2-A TRX.
2.31.3.6 Multiplexing of GPRS, EGPRS, and EGPRS2 Capable MSs

Huawei EGPRS2-A supports the multiplexing of GPRS, EGPRS, and EGPRS2-A capable MSs on the same PDCH. When GPRS, EGPRS, and EGPRS2-A capable MSs are multiplexed on the same PDCH, the BSC determines the modulation mode and coding scheme of the current downlink radio block according to the radio access capability of the MS so that the MS can correctly decode the USF that is carried in the downlink radio block. Based on the radio support capability of the MS, the BSC restricts the downlink modulation and coding scheme of the radio block as follows: l When the MS specified by the USF supports only the GPRS and the EGPRS level of the downlink TBF is EGPRS, the modulation mode of the current radio block should be GMSK and the coding scheme can be CS-1 to CS-4 or MCS-1 to MCS-4. When the MS specified by the USF supports only the GPRS and the EGPRS level of the downlink TBF is EGPRS2-A, the modulation mode of the current radio block should be GMSK and the coding scheme can be CS-1 to CS-4 or MCS-1 to MCS-4. When the MS specified by the USF supports EGPRS and the EGPRS level of the downlink TBF is EGPRS2-A, the modulation mode of the current radio block can be GMSK or 8PSK and the coding scheme can be CS-1 to CS-4, MCS-1 to MCS-9, or DAS-5 to DAS-7.
For the purpose of synchronization, the BSC sends at least one downlink radio block in which the USF can be correctly decoded by the MS to each MS every 360 ms when scheduling downlink radio blocks. The modulation mode and the coding scheme of that radio block are determined according to the preceding rules. When GPRS and EGPRS2-A capable MSs are multiplexed on the same PDCH, the modulation mode of downlink radio blocks on the PDCH must be GMSK if the uplink radio blocks of the GPRS MS need to be scheduled. In this case, the transmission rate of the downlink data of the EGPRS2-A MS decreases. When the parameter Allow E Down G Up Switch is set to Open, GPRS MS and EGPRS2-A capable MSs can be multiplexed on the same PDCH. For EGPRS and EGPRS2-A capable MSs, they can be multiplexed on the same PDCH without any parameter setting.
2.31.3.7 Data Transmission

EGPRS2 RLC/MAC Radio Block Structure

Table 2-64 shows the structure of the EGPRS2 RLC/MAC radio block. Table 2-64 EGPRS2 RLC/MAC radio block structure RLC/MAC block RLC/MAC header RLC data block 1 RLC data block 2 (conditional) RLC data block 3 (conditional) RLC data block 4 (conditional) PAN (optional)
An EGPRS2 RLC/MAC radio block consists of an RLC/MAC radio block header, one to four RLC data blocks, and a PAN domain (optional). The PAN domain is necessary only when the is supported. An EGPRS2-A RLC/MAC radio block contains one to three RLC data blocks according to the coding scheme. Header type 4 and header type 5 are added for the uplink EGPRS2-A RLC/MAC radio block. Header type 4 is used for the UAS-7, UAS-8, and UAS-9 coding schemes; header type 5 is used for the UAS-10 and UAS-11 coding schemes. Header type 4, header type 5, and header type 10 are added for the downlink EGPRS2-A RLC/ MAC radio block. The existing Header type 2 is used for the DAS-5, DAS-6, and DAS-7 coding schemes; header type 4 is used for the DAS-8 and DAS-9 coding schemes; header type 10 is used for the DAS-10 coding scheme; header type 5 is used for the DAS-11 and DAS-12 coding schemes.
EGPRS2-A RLC Data block Assembly and LLC PDU Segmentation

In the uplink direction, the BSC decodes each uplink EGPRS2-A RLC/MAC radio block into one to three RLC data blocks according to the coding scheme of the radio block. Then, the BSC extracts the RLC data unit from each RLC data block. When the BSN equals V(Q), the BSC assembles the collected RLC data units in the sequence of BSN to form the downlink LLC PDU, and then sends the LLC PDU to the SGSN over the Gb interface. In the downlink direction, the BSC extracts LLC PDUs from the downlink LLC PDU queue and segments each LLC PDU to one to three EGPRS2-A RLC data units according to the determined coding scheme. Then, the BSC encodes the EGPRS2-A RLC data units into EGPRS2-A RLC data blocks. Finally, the BSC assembles the EGPRS2-A RLC data blocks into a complete EGPRS2-A RLC/MAC radio block and sends the radio block to the MS over the Um interface.
EGPRS2-A RLC Data Block Retransmission

The BSC controls the retransmission of downlink EGPRS2-A RLC data blocks. Before retransmitting an RLC data block, the BSC may change the coding scheme of the radio block to ensure that the coding scheme used for retransmission is in the same coding scheme set as the original coding scheme of that radio block. When the EGPRS level changes and the RLC data block needs to be retransmitted, the coding scheme may also need to be changed to ensure that the coding scheme used after EGPRS level changing is in the same coding scheme set as the original coding scheme of that radio block.
2.31.4 Parameters
This chapter describes the parameters related to EGPRS2. For the meaning of each parameter, see Table 2-65. For the default value, value ranges, and MML commands of each parameter, see Table 2-66. Table 2-65 Parameter description (1) Parameter Description 16QAM power attenuation level of all carriers except timeslot 7 on the BCCH TRX. This parameter is required because the power used by the EDGE TRXs must be lower than the average GMSK power to transmit the 16QAM signals within the spectrum specifications. 32QAM power attenuation level of all carriers except timeslot 7 on the BCCH TRX. This parameter is required because the power used by the EDGE TRXs must be lower than the average GMSK power to transmit the 32QAM signals within the spectrum specifications. Delay of transmit diversity when 16QAM is used. Generally, the parameter is applicable to general fading environments. The transmit diversity can generally bring a gain of 3 dB to 5 dB. The fading conditions vary with the MS location; therefore, MSs in a fixed time delay obtain different gains. In addition, the EDGE service coding may be adversely affected. To avoid the preceding cases, the delay of transmit diversity must be configurable and can be set for GMSK and 16QAM respectively. Only the double-transceiver BTSs and the distributed BTSs can be configured with this parameter. For the BTSs of other types, this parameter is set to an invalid value 255. Delay of transmit diversity when 32QAM is used. Generally, the parameter is applicable to general fading environments. The transmit diversity can generally bring a gain of 3 dB to 5 dB. The fading conditions vary with the MS location; therefore, MSs in a fixed time delay obtain different gains. In addition, the EDGE service coding may be adversely affected. To avoid the preceding cases, the delay of transmit diversity must be configurable and can be set for GMSK and 32QAM respectively. Only the double-transceiver BTSs and the distributed BTSs can be configured with this parameter. For the BTSs of other types, this parameter is set to an invalid value 255. Fixed coding scheme that is used on the uplink EGPRS2-A link. If the uplink uses the fixed coding scheme, this parameter can be set to any one in MCS1-6 and UAS7-11. If the uplink uses the dynamic coding scheme, this parameter can be set to UNFIXED.
16QAM Transmitter Power Reduce Level
32QAM Transmitter Power Reduce Level
Diversity Transmitter 16QAM Delay
Diversity Transmitter 32QAM Delay
Uplink EGPRS2-A Fixed MCS Type
Issue 08 (2011-09-30)
430
Parameter
Description Default coding scheme used on the uplink EGPRS2-A link. If the uplink uses the dynamic coding scheme, this parameter specifies the coding scheme that is used for the transmission in initial access. If the uplink uses the fixed coding scheme, the TBF uses the fixed coding scheme. Average period for sending the measurement report over the EGPRS channel Fixed coding scheme that is used on the downlink EGPRS2A link. If the downlink uses the fixed coding scheme, this parameter can be set MSC1-4, MSC7-8 or DAS5-12.. If the downlink uses the dynamic coding scheme, this parameter is set to UNFIXED. Default coding scheme used on the downlink EGPRS2-A link. If the downlink uses the dynamic coding scheme, this parameter specifies the coding scheme that is used for the transmission in initial access. If the downlink uses the fixed coding scheme, the TBF uses the fixed coding scheme. Information about the cell scenario. It needs to be sent to the BTS. Based on the information, the BTS optimizes the allocation of resources. Whether the current cell supports EGPRS2-A Switch specifying whether to allow the downlink EGPRS TBF and the uplink GPRS TBF to share the same channel. On: allow the downlink EGPRS TBF and the uplink GPRS TBF to share the same channel; Off: prohibit the downlink EGPRS TBF and the uplink GPRS TBF sharing the same channel.
Uplink EGPRS2-A Default MCS Type Bep Period
Downlink EGPRS2-A Fixed MCS Type
Downlink EGPRS2-A Default MCS Type
Cell Scenario EGPRS2-A
Allow E Down G Up Switch
Table 2-66 Parameter description (2) Paramete r 16QAM Transmitte r Power Reduce Level 32QAM Transmitte r Power Reduce Level Default Value GUI Value Range Actual Value Range Unit MML Comman d SET GTRXDE V (Optional) SET GTRXDE V (Optional) Impact
0~50
0~50, step: 0.2
dB
TRX
0~50
0~50, step: 0.2
dB
TRX
Issue 08 (2011-09-30)
431
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLB ASICPAR A (Optional) SET GCELLB ASICPAR A (Optional)
Impact
Diversity Transmitte r 16QAM Delay Diversity Transmitte r 32QAM Delay
4~32
0.5~4, step: 1/8
bit
Cell
4~32 MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), UAS7 (UAS7), UAS8 (UAS8), UAS9 (UAS9), UAS10 (UAS10), UAS11 (UAS11), UNFIXE D (UNFIXE D)
0.5~4, step: 1/8
bit
Cell
Uplink EGPRS2A Fixed MCS Type
UNFIXE D
MCS1, MCS2, MCS3, MCS4, MCS5, MCS6, UAS7, UAS8, UAS9, UAS10, UAS11, UNFIXE D
None
SET GCELLE GPRSPA RA (Optional)
Cell
Issue 08 (2011-09-30)
432
Paramete r
Default Value
GUI Value Range MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), UAS7 (UAS7), UAS8 (UAS8), UAS9 (UAS9), UAS10 (UAS10), UAS11 (UAS11)
Actual Value Range
Unit
MML Comman d
Impact
Uplink EGPRS2A Default MCS Type
MCS6
MCS1, MCS2, MCS3, MCS4, MCS5, MCS6, UAS7, UAS8, UAS9, UAS10, UAS11
None
SET GCELLE GPRSPA RA (Optional) SET GCELLE GPRSPA RA (Optional)
Cell
Bep Period
0~10
0~10
None
Cell
Issue 08 (2011-09-30)
433
Paramete r
Default Value
GUI Value Range MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS7 (MCS7), MCS8 (MCS8), DAS5 (DAS5), DAS6 (DAS6), DAS7 (DAS7), DAS8 (DAS8), DAS9 (DAS9), DAS10 (DAS10), DAS11 (DAS11), DAS12 (DAS12), UNFIXE D (UNFIXE D)
Actual Value Range
Unit
MML Comman d
Impact
Downlink EGPRS2A Fixed MCS Type
UNFIXE D
MCS1, MCS2, MCS3, MCS4, MCS7, MCS8, DAS5, , DAS6, DAS7, DAS8, DAS9, DAS10, DAS11, DAS12, UNFIXE D
None
Cell
Issue 08 (2011-09-30)
434
Paramete r
Default Value
GUI Value Range MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS7 (MCS7), MCS8 (MCS8), DAS5 (DAS5), DAS6 (DAS6), DAS7 (DAS7), DAS8 (DAS8), DAS9 (DAS9), DAS10 (DAS10), DAS11 (DAS11), DAS12 (DAS12) COMMO N (COMMO N), MULTIP ATH (MULTIP ATH), INDOOR (INDOOR ), HIGHWA Y (HIGHW AY)
Actual Value Range
Unit
MML Comman d
Impact
Downlink EGPRS2A Default MCS Type
DAS6
MCS1, MCS2, MCS3, MCS4, MCS7, MCS8, DAS5, , DAS6, DAS7, DAS8, DAS9, DAS10, DAS11, DAS12
None
Cell
Cell Scenario
COMMO N
COMMO N, MULTIP ATH, INDOOR, HIGHWA Y
None
SET GCELLB ASICPAR A (Optional) SET GCELLG PRS (Optional)
Cell
EGPRS2A
NO
NO(No), YES(Yes)
NO, YES
None
Cell
Issue 08 (2011-09-30)
435
Paramete r
Default Value
GUI Value Range OPEN (Open), CLOSE (Close)
Actual Value Range
Unit
MML Comman d SET BSCPSSO FTPARA (Optional)
Impact
OPEN
OPEN, CLOSE
None
BSC
2.31.5 Counters
2.31.6 Glossary

l l l l l l l l l l l l l l l l 3GPP TS 44.060: "Radio Link Control/Medium Access Control (RLC/MAC) protocol" 3GPP TS 43.064: "Overall description of the GPRS radio interface; Stage 2" 3GPP TR 45.912: "Feasibility study for evolved GSM/EDGE Radio Access Network (GERAN)" 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2" 3GPP TS 45.008: "Radio subsystem link control" 3GPP TS 45.005: "Radio transmission and reception" 3GPP TS 45.004: Modulation 3GPP TS 25.213: "Spreading and modulation (FDD)" 3GPP TS 25.223: "Spreading and modulation (TDD)" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference GPRS/EGPRS Link Quality Control Parameter Description
2.32 eMLPP
2.32.1 Introduction
2.32.1.1 Scope
This document describes the working principle, A interface parameters, and priority-based resource reservation of eMLPP.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change: refers to the change in the eMLPP feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
Issue 08 (2011-09-30)
437
01 (2009-06-30)
2.32.2 Overview
The Enhanced Multi-Level Precedence and Pre-emption service (eMLPP) is a supplementary service offered by the GSM system. When the eMLPP feature is enabled, the MS with a high priority has advantages in terms of the call setup rate, call completion capability, and service continuity. When TCHs are insufficient, for example, during traffic peak hours, the calls with a higher priority can preempt the resources of the calls with a lower priority. When resources are insufficient, the eMLPP service ensures that the MSs with a high priority use the resources first. If the preempted MSs are not handed over to other channels, for example, if the site is an isolated site, the TCH resources in neighbor cells are insufficient, or the handovers have timed out, the measurement values of the counters related to call drop rate on TCH increase. If the eMLPP feature is enabled, the cooperation from the CN is required to ensure the normal operation of eMLPP services. The eMLPP services consist of two parts: l Fast call setup A call with any priority can use the fast call setup procedure. In the fast call setup procedure, authentication, encryption, and TMSI reassignment are omitted. Thus, the call setup time is reduced. l Queuing and preemption When network resources, including trunk circuits, signaling channels, and traffic channels, are insufficient, the calls with a higher priority are not released, but wait in a queue or even preempt the resources of the calls with a lower priority. The eMLPP service is used to classify calls into groups with different priorities. The calls with a higher priority can enjoy better services, such as channel preemption and fast call setup. The eMLPP service offers a segmentation function for operators. By enabling this function, operators can provide different levels of services for subscribers with different priorities.

2.32.3.1 A Interface Parameters Involved in eMLPP
If Allow EMLPP is enabled, the eMLPP serivces are activated. The A interface parameters that the BSC obtains from the MSC determines the eMLPP. Table 2-67 lists the A interface parameters involved in eMLPP.
Issue 08 (2011-09-30)
438
Table 2-67 A interface parameters involved in eMLPP Parameter Preemption Capability Indicator (PCI) Counter Name Flag bit of preemption Action If PCI allows preemption, that is, PCI = 1, the call can preempt the radio resources of a call with a lower priority. If PVI allows being preempted, that is, PVI = 1, the radio resources of the call can be preempted by a call with a higher priority. According to GSM PHASE2 + specifications, PL has 14 levels. Level 1 is the highest priority and level 14 is the lowest priority. If QA allows queuing, that is, QA = 1, the call can be put into a queue for resource allocation. PIE consists of PCI, PVI, PL, and QA.
Preemption Vulnerability Indicator (PVI)
Flag bit of being preempted
Priority Level (PL)
Priority level
Queuing Allowed indicator (QA)
Queuing indicator
Priority Information Element (PIE)
None
2.32.3.2 Call Establishment Procedure

This describes the procedure for assigning a TCH by the BSC when an MS with a high priority initiates a call or receives a call in a congested cell. 1. The BSC determines whether the cell has an idle TCH. l If the cell has an idle TCH, the BSC assigns the TCH to the high-priority MS. The procedure is complete. l If the cell does not have an idle TCH, go to 2. 2. The BSC checks the PCI of the high-priority MS. l If PCI = 1, go to 3. l If PCI is not 1, the procedure is complete. 3. The BSC searches for the lowest-priority MS whose PVI is 1. l If such an MS is found, go to 4. l If such an MS is not found, go to 5. 4. The BSC triggers the handover of the MS with the lowest priority. l If the handover is successful, go to 6. l If the handover fails, go to 7. 5. The BSC checks the QA of the high-priority MS. l If QA = 1, the high-priority MS queues. Then, go to 8.
l If QA is not 1, the high-priority MS cannot queue. The procedure is complete. 6. The high-priority MS seizes the channel released by the MS that is handed over to a neighbor cell. The procedure is complete.
NOTE
After the low-priority MS is handed over to a neighbor cell, it cannot preempt the resources of an MS with an even lower priority in the neighbor cell.
7. 8.
The channel used by the low-priority MS is released and the high-priority MS seizes this channel. The procedure is complete. The high-priority MS waits in the queue for channel assignment. l If an idle channel is available within half the timing length of the queue timer, the highpriority MS seizes the channel. The procedure is complete. l If the MS waits in the queue for half the timing length of the queue timer and the BSC allows directed retry, a directed retry is triggered. If the directed retry fails, the call is released. The procedure is complete. l If the MS waits in the queue for half the timing length of the queue timer and the BSC does not allow directed retry, the call is released when the queue timer expires. The procedure is complete.
2.32.3.3 Priority-Based Resource Reservation

With priority-based resource reservation, the system reserves a certain number of TCHFs for the high-priority users to ensure their QoS. The half-rate service uses a coding mode different from that of the full-rate service and has a coding rate of 5.6 kbit/s. Thus, after the half-rate service is enabled, the voice quality of the halfrate service drops. The MSs of some low-priority users do not support the half-rate feature. Consequently, in the cells where the half-rate feature is enabled these MSs occupy the TCHFs and have a high voice quality. But the MSs of some high-priority users which support the half-rate feature are allocated TCHHs preferably in the cell where the half-rate feature is enabled and they have a low voice quality. To guarantee the QoS of these high-priority users, the priority-based resource reservation function should be enabled. Configure the priority-based resource reservation function by setting the parameters such as Grade Access Allow, Highest Priority, and Reserved Channel Number so that the TCHFs are reserved for the high-priority users and their service quality is maintained. If the prioritybased resource reservation function is configured, the system allocates the TCHFs to the highpriority users first regardless of the traffic load in the cell.
2.32.4 Parameters
This chapter describes the parameters related to eMLPP. For the meaning of each parameter, see Table 2-68. For the default value, value ranges, and MML commands of each parameter, see Table 2-69.
Issue 08 (2011-09-30)
440
Table 2-68 Parameter description (1) Parameter Description Whether to allow the function of enhanced multi-level precedence and preemption (eMLPP). With the eMLPP function enabled, the network can use different policies such as queuing, preemption, or directed retry based on the priorities of different calls when network resources are occupied. If this parameter is set to YES, when preemption occurs, the MS with the lowest priority initiates a handover, and the MS with a higher priority seizes the idle channel after a handover. If this parameter is set to NO, an MS with a lower priority releases the channel, the MS with a higher priority seizes the idle channel after the release. The eMLPP has up to seven priorities: A, B, 0, 1, 2, 3, and 4. The two highest priorities A and B are internally reserved for local use only. Priorities 0 to 4 can be subscribed by MSs for global use.After the operator configures eMLPP priority mapping (consisting of 14 priority levels) on the MSC, the MSC sends a message containing the mapping to the BSC. The BSC then performs queuing and preemption based on the priority mapping. With the support of the MSC, HLR, and mobile terminal (containing a SIM card), the eMLPP function can be perfectly implemented. Whether to allow hierarchical access and to reserve resources for highpriority MSs Maximum priority level of an MS that can use reserved channel resources. If the priority level of an MS is greater than this parameter, the MS is considered a low-priority MS. If the priority of an MS is equal to or less than this threshold, the MS is considered a high-priority MS. While assigning channels, the BSC ensures that the sum of the number of channels occupied by high-priority users and the number of idle channels reserved for high-priority users is no smaller than this parameter. Every time the BSC assigns channels to a user whose priority is lower than "Highest Priority", it checks whether the sum of the number of channels occupied by users of "Highest Priority" and the number of idle channels is larger than the number of the reserved channels. If yes, the BSC normally assigns channels for the user; if not, the BSC does not assign a TCHF.
Allow EMLPP Grade Access Allow
Highest Priority
Reserved Channel Number
Table 2-69 Parameter description (2) Paramete r Default Value GUI Value Range NO(No), YES(Yes) NO(No), YES(Yes) Actual Value Range Unit MML Command SET GCELLCCBASIC (Optional) SET GCELLCHMGBA SIC(Optional) Impa ct
Allow EMLPP Grade Access Allow

Issue 08 (2011-09-30)
NO
NO, YES
None
Cell
NO
NO, YES
None
Cell
441
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command SET GCELLCHMGBA SIC(Optional) SET GCELLCHMGBA SIC(Optional)
Impa ct
Highest Priority Reserved Channel Number
1~14
1~14
None
Cell
0~190
0~190
None
Cell
2.32.5 Counters
2.32.6 Glossary

l l l l l l 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2". 3GPP TS 22.067: "enhanced Multi Level Precedence and Pre emption service (eMLPP) Stage 1". 3GPP TS 23.011:"Technical realization of supplementary services". 3GPP TS 48.008: "Mobile Switching Centre Base Station System (MSC BSS) interface Layer 3 specification". ITU-T Recommendation Q.85: "Stage 2 description for community of interest supplementary services (clause 3: Multi-Level Precedence and Pre-emption MLPP)". ITU-T Recommendation Q.735: "Stage 3 description for community of interest supplementary services using SS No. 7 (clause 3: Multi-Level Precedence and Pre-emption (MLPP)". 3GPP TS 25,331: "RRC Protocol Specification". 3GPP TS 24.008: "Core Network Protocols - Stage 3". BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
l l l l l l l l
2.33 EMR
2.33.1 Introduction
2.33.1.1 Scope
This document describes the concept, working principle, and preprocessing of enhanced measurement report. It also describes the relation of enhanced measurement report with other features.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the enhanced measurement report(EMR) feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
Issue 08 (2011-09-30)
443
01 (2009-06-30)
2.33.2 Overview
GSM will coexist with UMTS for a long time. To obtain better performance of the interoperability between the UMTS network and the GSM network and to obtain more measurement information about the neighboring cells, a new type of measurement report (MR), that is, the enhanced measurement report (EMR), is introduced. EMR is a new downlink measurement report introduced to 3GPP Release 99. The 3GPP TS 44.018 stipulates that the network should command the MS to report the measurement information on the serving cell and neighboring cells by MR or EMR through Measurement Information (MI) or SI 2quater. Compared with the MR, the EMR provides additional measurement contents as follows: l The EMR uses an optimized coding scheme for neighboring cell information, and thus provides information on more neighboring cells than the MR does. For example, the MR can carry the information on up to 6 neighboring GSM cells while the EMR can provide the information on up to 15 neighboring GSM/WCDMA/TD_SCDMA cells. This ensures better performance for interoperability between GSM and WCDMA/TD-SCDMA and meets the requirement for service continuity. The EMR includes the Bit Error Probability (BEP) for identifying the channel quality. Estimated on a per burst basis, BEP is a comprehensive criteria for reflecting the C/I ratio, signal delay extension, and MS speed. In addition, BEP is coded in five bits while Receive Quality (RXQUAL) in three bits.
NOTE
The RXQUAL value is converted from the Bit Error Ratio (BER).
EMR contains the number of correctly received speech frames for calculating the Frame Erase Ratio (FER). FER is the measurement of the coding/decoding performance of the speech signals while RXQUAL is the measurement of the radio signals. Therefore, FER outperforms RXQUAL in terms of speech quality measurement.
BEP and FER can improve the performance of the algorithms that operate on the basis of the radio signal quality. They can replace the RXQUAL that is commonly used as an indicator of the radio signal quality. In this way, the performance of the power control algorithms and handover algorithms can be improved. Figure 2-94 shows the procedure for sending the EMR.
Figure 2-94 Procedure for sending the EMR

2.33.3.1 Implementation in the BSS
If Measurement Report Type is set to Enhance Measure Report, the System Information MI or SI2quater message carries the information elements (IEs) Measurement Report Type and SCALE_ORDER. If the MS does not receive the MI or SI2quater message, the MS still reports the MR. Only the MS that complies with 3GPP Release 99 supports the EMR. If the MS does not support the EMR, the MS still reports the MR even if the System Information MI or SI2quater message indicates that the MS should report the EMR. In an MR, the measured values of neighboring GSM cells and neighboring UMTS cells are reported separately according to the 2G cell BA2 list and UTRAN FDD cell BA2 list. In an EMR, the measured values of neighboring GSM cells and neighboring UMTS cells are reported together according to the neighboring cell list. In the neighboring cell list, the neighboring GSM cells generally use the smaller index numbers and the neighboring UMTS cells generally use the larger index numbers. Assume that a cell is configured with five neighboring GSM cells and four neighboring UMTS cells. If the MS reports the MR, the neighboring GSM cells use the index numbers 0 to 4 of the neighboring GSM cell table, and the neighboring UMTS cells use the index numbers 0 to 3 of the neighboring UMTS cell table. If the MS reports the EMR, the neighboring GSM cells and neighboring UMTS cells all use the index numbers of a hybrid neighboring GSM/UMTS cell table. In the hybrid neighboring GSM/UMTS cell table, index numbers 0 to 4 are assigned to neighboring GSM cells and index numbers 5 to 8 are assigned to neighboring UMTS cells. When the MS reports the EMR, the RXLEV value of the serving cell and the RXLEV values of the neighboring cells do not follow the mapping relation that RXLEV values 0 to 63 map to -110
dBm to -47 dBm but follow the mapping relation described in the SCALE_ORDER IE in the MI or SI2quater message. The actual signal level can be calculated as follows: l l If SCALE_ORDER is set to +10dB, RXLEV values 0 to 63 map to actual signal levels -100 dBm to -37 dBm. If SCALE_ORDER is set to +0dB, RXLEV values 0 to 63 map to actual signal levels -110 dBm to -47 dBm.
NOTE
To ensure the compatibility with the MR, the mapping relation that the RXLEV values 0 to 63 map to -110 dBm to -47 dBm is used when the MS reports the EMR.
2.33.3.2 Measurement Report Preprocessing

The EMR requires the support from the BTS. When sending the Measurement Result message to the BSC, the BTS checks whether the application of the EMR is successful according to the support capability of the BTS for EMR and the setting of MR.Preprocessing. When the BTS does not support the EMR, and the BSC and the MS support the EMR, one of the following cases may occur if Measurement Report Type is set to Enhance Measure Report: l l If MR.Preprocessing is set to No, the BTS forwards the EMR to the BSC without decoding it. If MR.Preprocessing is set to Yes, the BTS fails to decode the EMR.
When Measurement Report Type is set to Enhance Measure Report and MR.Preprocessing is set to Yes, the BTS processes: l l The uplink EMR in the same way as it processes the uplink MR. The downlink EMR in a way different from the way it processes the downlink MR. The differences lie in the number of 2G neighboring cells and 3G neighboring cells involved in the downlink EMR and the interpolating and filtering of the downlink EMR. The processing of the downlink EMR involves the following filter parameters: Filter Length for SDCCH MEAN_BEP Filter Length for TCH MEAN_BEP Filter Length for SDCCH CV_BEP Filter Length for TCH CV_BEP Filter Length for SDCCH REP_QUANT Filter Length for TCH REP_QUANT Filter Length for SDCCH NBR_RCVD_BLOCK Filter Length for TCH NBR_RCVD_BLOCK
NOTE
When Measurement Report Type is set to Enhance Measure Report and MR.Preprocessing is set to No, the previously listed filter parameters do not take effect during MR processing.
2.33.3.3 2G/3G Interoperability

The EMR is affected by 2G/3G interoperability. l If the System Information MI or SI2quater message does not carry the information about neighboring UMTS cells, the MI or SI2quater message is not controlled by the license of 2G/3G interoperability. If the System Information MI or SI2quater message carries the information about neighboring UMTS cells, the MI or SI2quater message is controlled by the license of 2G/ 3G interoperability.
2.33.3.4 DTX
The EMR indicates whether DTX is used. The signal quality in the EMR uses the FULLSET values and the receive signal level uses RXLEV_VAL irrespective of whether DTX is enabled.
2.33.3.5 Handover and Power Control

The EMR has a great impact on the power control algorithm and the handover algorithm. In the EMR, MEAN_BEP instead of RXQUAL is used to evaluate the radio signal quality. Compared with RXQUAL, BEP has high precision, especially when the radio signal quality is poor. The MEAN_BEP can be used to improve the performance of the algorithms that use RXQUAL to evaluate radio signal quality. Therefore, for all the algorithms that use RXQUAL to evaluate radio signal quality, RXQUAL should be replaced by MEAN_BEP. The parameters related to MEAN_BEP are Filter Length for SDCCH MEAN_BEP and Filter Length for TCH MEAN_BEP. The parameters related to power control remain unchanged. Table 2-70 provides the conversion relation between MEAN_BEP and RXQUAL. The power control algorithm and handover algorithm remain unchanged. Table 2-70 Conversion relation between MEAN_BEP and BER MEAN_BEP 0 1 2 3 4 5 6 7 8 9 10
Issue 08 (2011-09-30)
BER Greater than 0.2512 0.1995-0.2512 0.1585-0.1995 0.1259-0.1585 0.1-0.1259 0.0794-0.1 0.0631-0.0794 0.0501-0.0631 0.0398-0.0501 0.0316-0.0398 0.0251-0.0316
RXQUAL 7 (0-3)
6 (4-6)
5 (7-9)
4 (10-12)
447
MEAN_BEP 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
BER 0.02-0.0251 0.0158-0.02 0.0126-0.0158 0.01-0.0126 0.0079-0.01 0.0063-0.0079 0.005-0.0063 0.004-0.005 0.0032-0.004 0.0025-0.0032 0.002000-0.0025 0.0016-0.002 0.0013-0.0016 0.001-0.0013 0.0008-0.001 0.0006-0.0008 0.0005-0.0006 0.0004-0.0005 0.0003-0.0004 0.0003-0.0003 Smaller than 0.0003
RXQUAL
3 (13-15)
2 (16-18)
1 (19-21)
0 (22-31)

When Measurement Report Type is set to Enhance Measure Report, dynamically changing the setting of MR.Preprocessing or the neighboring relations of 2G/3G cells affects the system. l Measurement Report Type is set to Enhance Measure Report and MR.Preprocessing is set to BTS_Preprocessing(BTS preprocessing). The BTS preprocesses the MR only when it knows the exact information about the neighboring cells. If a neighboring 2G or 3G cell is dynamically added or deleted, the MS making a call in the current cell is forcibly handed over out of the cell. If the handover fails, the system directly releases the call. Thus, the call drop rate increases.
Issue 08 (2011-09-30)
448
Measurement Report Type is set to Enhance Measure Report and MR.Preprocessing is changed to BSC_Preprocessing(BSC preprocessing) from BTS_Preprocessing(BTS preprocessing). The BTS still preprocesses the MR from the MS that has established a call. If a neighboring 2G or 3G cell is dynamically added or deleted, the MS making a call in the current cell is not forcibly handed over out of the cell. The BTS, however, may fail to decode the EMR.
WARNING
When Measurement Report Type is set to Enhance Measure Report, it is recommended that the setting of MR.Preprocessing and the neighboring relations of 2G/3G cells should not be dynamically changed.
2.33.5 Parameters
This chapter describes the parameters related to EMR. For the meaning of each parameter, see Table 2-71. For the default value, value ranges, and MML commands of each parameter, see Table 2-72. Table 2-71 Parameter description (1) Parameter Measurement Report Type Description Type of the measurement report (MR) reported by the MS This parameter indicates that when the MS reports the EMR, it adds the value of this parameter to the received signal level, and then converts the result into the RXLEV value. For details, see GSM Rec. 05.08. If the SCALE_Order reported by the MS is 10 dBm, level values 0-63 map with -100 dBm to -37 dBm. If the SCALE_Order reported by the MS is 0 dBm, level values 0-63 map with -110 dBm to -47 dBm. If the SCALE_Order reported by the MS is Automatic, the MS chooses the least SCALE while ensuring that the MS can report the most strong level. Whether to enable the BTS to preprocess measurement reports. This parameter determines where to conduct power control. For the purpose of accurately reflecting the radio environment of a network, filtering is performed on the measured values in several consecutive measurement reports. This parameter indicates the number of enhanced measurement reports received on a signaling channel used to measure the MEAN_BEP value. For the purpose of accurately reflecting the radio environment of a network, filtering is performed on the measured values in several consecutive measurement reports. This parameter indicates the number of enhanced measurement reports received on a voice channel used to measure the MEAN_BEP value.
449
SCALE_ORDER MR.Preprocessing
Filter Length for SDCCH MEAN_BEP
Filter Length for TCH MEAN_BEP

Issue 08 (2011-09-30)
Parameter
Description Number of enhanced measurement reports (EMRs) sampled for averaging the CV_BEP on the SDCCH. Averaging the CV_BEP in multiple EMRs helps to prevent the incomprehensiveness of a single EMR. Number of enhanced measurement reports (EMRs) sampled for averaging the CV_BEP on the TCH. Averaging the CV_BEP in multiple EMRs helps to prevent the incomprehensiveness of a single EMR. For the purpose of accurately reflecting the radio environment of a network, filtering is performed on the measured values in several consecutive measurement reports. This parameter indicates the number of enhanced measurement reports received on signaling channels used to filter the REP_QUANT value. For the purpose of accurately reflecting the radio environment of a network, filtering is performed on the measured values in several consecutive measurement reports. This parameter indicates the number of enhanced measurement reports received on voice channels used to filter the REP_QUANT value. For the purpose of accurately reflecting the radio environment of a network, filtering is performed on the measured values in several consecutive measurement reports. This parameter indicates the number of enhanced measurement reports received on a signaling channel used to filter the NBR_RCVD_BLOCKS value. For the purpose of accurately reflecting the radio environment of a network, filtering is performed on the measured values in several consecutive measurement reports. This parameter indicates the number of enhanced measurement reports received on a service channel used to filter the NBR_RCVD_BLOCKS value.
Filter Length for SDCCH CV_BEP Filter Length for TCH CV_BEP
Filter Length for SDCCH REP_QUANT
Filter Length for TCH REP_QUANT Filter Length for SDCCH NBR_RCVD_BL OCK Filter Length for TCH NBR_RCVD_BL OCK
Issue 08 (2011-09-30)
450
Table 2-72 Parameter description (2) Paramete r Default Value GUI Value Range EnhMeas Report (Enhanced Measurem ent Report), ComMeas Report (Common Measurem ent Report) ADD0dB (+0dB), ADD10dB (+10dB), Automatic (Automati c) BSC_Prep rocessing (BSC preprocess ing), BTS_Prep rocessing (BTS preprocess ing) BSC_Prep rocessing, BTS_Prep rocessing Actual Value Range Un it MML Command Impac t
Measurem ent Report Type
ComMeas Report
EnhMeas Report, ComMeas Report
No ne
SET GCELLCCUTRAN SYS(Optional)
Cell
SCALE_ ORDER
ADD0dB
ADD0dB, ADD10dB , Automatic
No ne
SET GCELLCCUTRAN SYS(Optional)
Cell
MR.Prepr ocessing Filter Length for SDCCH MEAN_B EP
BTS_Prep rocessing
BSC_Prep rocessing, BTS_Prep rocessing TCH: 0~14880, step:480; SDCCH: 0~14570, step:470
No ne
SET GCELLHOCTRL (Optional)
Cell
0~31
ms
SET GCELLHOFITPEN (Optional)
Cell
Issue 08 (2011-09-30)
451
Paramete r
Default Value
GUI Value Range
Actual Value Range TCH: 0~14880, step:480; SDCCH: 0~14570, step:470 TCH: 0~14880, step:480; SDCCH: 0~14570, step:470 TCH: 0~14880, step:480; SDCCH: 0~14570, step:470 TCH: 0~14880, step:480; SDCCH: 0~14570, step:470 TCH: 0~14880, step:480; SDCCH: 0~14570, step:470 TCH: 0~14880, step:480; SDCCH: 0~14570, step:470 TCH: 0~14880, step:480; SDCCH: 0~14570, step:470
Un it
MML Command
Impac t
Filter Length for TCH MEAN_B EP
0~31
ms
Cell
Filter Length for SDCCH CV_BEP
0~31
ms
Cell
Filter Length for TCH CV_BEP Filter Length for SDCCH REP_QU ANT Filter Length for TCH REP_QU ANT Filter Length for SDCCH NBR_RC VD_BLO CK Filter Length for TCH NBR_RC VD_BLO CK
0~31
ms
Cell
0~31
ms
Cell
0~31
ms
Cell
0~31
ms
Cell
0~31
ms
Cell
Issue 08 (2011-09-30)
452
2.33.6 Counters
2.33.7 Glossary

l l l l l l 3GPP TS 44.018 "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol" BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.34 EPLC
2.34.1 Introduction
2.34.1.1 Scope
This document describes the enhanced packet loss concealment (EPLC) feature of Huawei GBSS. It covers the function of and mechanism regarding this feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows:
Feature change Feature change: refers to the change in the enhanced packet loss concealment (EPLC) feature of a specific product version.
Editorial change Editorial change: refers to changes in information that has already been included, or the addition of information that was not provided in the pervious version.
Document Issues
The document issues are as follows: l 01 (2009-0930)
01 (2009-09-30)
2.34.2 Overview
In the communication system, the bit error of the transmission link may be caused by the mobile terminal, interference between transmission links, or changes in the load of the TRX. When bit error occurs in voice transmission, at least one frame is lost before it arrives at the decoder, and thus the voice quality deteriorates. To solve this problem, the Enhanced Packet Loss Concealment (EPLC) feature is introduced. EPLC predicts the information contained in the lost frame and compensates the lost frame according to the information contained in the normal frame preceding the lost frame and the characteristics of the frames after AMR coding and decoding. In this way, the voice quality is improved. EPLC prevents the voice quality deterioration caused by frame loss and improves the voice quality (the effects of EPLC are better than the effects of the standard AMR algorithm stipulated in the 3GPP protocols). This improves the user experience, prolongs the average call duration, and increases the operator's revenue.

EPLC conceals packet loss by using Algebraic Code Excitation Linear Prediction (ACELP) and Huawei proprietary technique of waveform recovery. It aims to improve the AMR voice quality during the AMR codec process. EPLC extracts the voiceprint of the speaker from the information contained in the received good frames and stores the voiceprint. The stored voiceprint is then constantly fine-tuned based on the subsequent good frames. When frame loss occurs, EPLC predicts and recovers the missing frame using the stored voiceprint. EPLC is a complex packet loss concealment method for noticeable voice quality improvement. The EPLC algorithm is enabled when the EPLC Switch is set to Open. The EPLC algorithm involves three procedures, voiceprint storage and fine-tuning, frame prediction and recovery, and speech signal combination, as shown in Figure 2-95.
Issue 08 (2011-09-30)
454
Figure 2-95 EPLC algorithm
Voiceprint storage and fine-tuning EPLC extracts the voiceprint from the good frames and store it. The extracted voiceprint comprises the LPC coefficient, pitch delay, pitch gain, and codebook gain. After subsequent good frames arrive, EPLC fine-tunes the stored voiceprint. This ensures that the stored voiceprint is faithful enough, as compared with the actual voiceprint of the speaker in terms of frequency, volume, and pitch.
Frame prediction and recovery EPLC predicts and recovers the missing frame by using the stored voiceprint and considering the correlation between the previous frames and subsequent frames of the missing frame.
Speech signal combination The recovered frame is filtered and then combined with the good frames. In this way, the original PCM voice signals are obtained.
The EPLC algorithm is implemented by the DSP of the DPU board. EPLC improves the voice quality without imposing additional requirements on hardware or the complexity of the decoder.
Issue 08 (2011-09-30)
455

NOTE
The EPLC algorithm is incorporated into the decoder. Currently, the EPLC algorithm applies only to the AMR-NB code stream.
2.34.4 Parameters
This chapter describes the parameters related to the EPLC. For the meaning of each parameter, see Table 2-73. For the default value, value ranges, and MML commands of each parameter, see Table 2-74. Table 2-73 Parameter description (1) Parameter EPLC Switch Description Whether to enable the EPLC function.
Table 2-74 Parameter description (2) Param eter Defaul t Value GUI Value Range CLOSE (Close), OPEN (Open) Actual Value Range Unit MML Command Im pac t Boa rd
EPLC Switch
CLOSE
CLOSE, OPEN
Non e
SET TCPARA (Optional)
2.34.5 Counters
None.
2.34.6 Glossary

2.35 Flex Abis

2.35.1 Introduction
2.35.1.1 Scope
This document describes the Flex Abis networking, establishment of Abis transmission links, and algorithm for half-rate channel allocation triggered by Abis overload.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the Flex Abis feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
Issue 08 (2011-09-30)
457
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0, the following changes are incorporated: Change Type Feature change Change Description 2.35.3.3 Algorithm for HalfRate Channel Allocation Triggered by Abis Overload is optimized. Parameter Change The added parameters are listed as follows: l LDR First l LDR Second l LDR Third l LDR Fourth Editorial change The structure of the document is optimized. None.
2.35.2 Overview
In an actual network, not all the BTSs or cells are busy and not both the PS and CS services have a high traffic volume at a specific time. Generally, if the load of one BTS is heavy, the load of other BTSs is light; if the traffic volume of the PS service is high, that of the CS service is low, and vice versa. Flex Abis (Flexible Abis) enables the sharing of the Abis interface transmission resources among different BTSs, cells, and services, and thus improves the resource utilization. Flex Abis is a mode of allocating the Abis interface transmission resources. That is, the Abis interface transmission resources form a resource pool that is shared by the CS service and PS service (including idle timeslots) among different cells and BTSs. The Abis interface transmission resources can be used more effectively when Flex Abis applies to the following cases: l l l Multi-cell large-capacity BTSs Cascaded BTSs EGPRS capable cells

The transmission resources over the Abis interface can be allocated either fixedly or dynamically. l Fixed allocation mode In fixed allocation mode, the channels over the Um interface (including the TCH and static PDCH) are always mapped with the Abis interface transmission resources. That is, the Abis interface transmission resources are occupied even when the Um interface channels are idle. l Dynamic allocation mode In dynamic allocation mode, the Abis interface transmission resources form a pool. The Abis interface transmission resources are allocated to the Um interface channels only when
the channels are occupied. Thus, the Um interface channel resources can be much more abundant than the Abis interface transmission resources, and the Abis interface transmission resources can be fully utilized in different time slices. Flex Abis features the dynamic allocation of Abis interface transmission resources, which improves the utilization of the resources, as shown in Figure 2-96. Figure 2-96 Working principle of Flex Abis
The Flex Abis resource pool consists of all the Abis interface transmission resources, excluding the static PDCH, semipermanent connection timeslots, monitoring timeslots, signaling link timeslots, Abis transmission timeslots in fixed allocation mode, and idle timeslots. The Flex Abis resource pool is shared by the CS service and PS service (including the idle timeslots) among different cells and BTSs. The timeslots in the Flex Abis resource pool are allocated to the TCH and PDCH. The full-rate TCH and PDCH are allocated 16 kbit/s timeslots; whereas the half-rate TCH is allocated the 8 kbit/s timeslot. For details, see 2.23 Channel Management and 2.40 GPRS/EGPRS Channel Management. When the transmission resources are insufficient, the CS service can preempt the timeslots of the PS service. You are advised to enable Flex Abis in the following scenarios to make better use of the Abis interface transmission resources. l l l l
Issue 08 (2011-09-30)
Transmission resources are limited, and the rent for them is very high, for example, in satellite transmission mode. The traffic volume in actual situation is far lower than that in the channel resource planning. The cells that share Abis interface transmission resources have different traffic peak hours. The proportion of PS service users in the cell is high.
2.35.3.1 Networking Configuration

The BSC supports the networking mode of multi-level Flex Abis resource pools among cascaded BTSs. As shown in Figure 2-97, Link1, Link2, and Link3 correspond to the Abis interface transmission links between the BSC and BTS0, between BTS0 and BTS1, and between BTS1 and BTS2 respectively. The transmission over the Abis interface is realized through satellite or one or more E1/T1 cables. The transmission resources on each Abis interface transmission link form a resource pool for the CS service and PS service to share. l The transmission resources on Link1 form Pool0. The resources in Pool0 can be shared by the CS service and PS service on BTS0, BTS1, and BTS2. l l The transmission resources on Link2 form Pool1. The resources in Pool1 can be shared by the CS service and PS service on BTS1 and BTS2. The transmission resources on Link3 form Pool2. The resources in Pool2 can be shared by the CS service and PS service on BTS2. Figure 2-97 Flex Abis network topology
2.35.3.2 Establishment of Transmission Link

If Flex Abis is enabled, the BSC must allocate the Abis interface transmission resources and establish a transmission link between the BSC and the BTS. When a channel on BTS2 is allocated, the BSC must dynamically allocate the Abis interface transmission resources to Link1, Link2, and Link3 for the channel, and instruct BTS0, BTS1, and BTS2 to establish transmission links for the channel, as shown in Figure 2-98. Therefore, the Extended Signaling Link (ESL) must be configured for each Flex Abis capable BTS to carry the signaling. In 64 kbit/s multiplexing mode, the ESL and Operation and Maintenance Link (OML) must be physically multiplexed on the same 64 kbit/s E1 timeslot. To increase the number of ESLs, you are advised to reduce the number of Radio Signaling Links (RSLs) multiplexed with the OML to two by setting the parameter Multiplexing Mode.
Issue 08 (2011-09-30)
460
Figure 2-98 Working principle of Flex Abis
The configuration principles of Multiplexing Mode are as follows: l Generally, the parameter Multiplexing Mode is set to 4:1. When Flex Abis is enabled, the parameter Multiplexing Mode can be set to 5:1 or 6:1 to multiplex five or six RSLs onto one 64 kbit/s timeslot without occupying another 64 kbit/s timeslot. During the initial configuration of a BTS, set Flex Abis Mode to FLEX_ABIS(Flex Abis) or SEMI_ABIS(Semisolid Abis) to enable Flex Abis. After the BTS configuration is complete, set Flex Abis Mode to FLEX_ABIS(Flex Abis) or SEMI_ABIS(Semisolid Abis) to enable Flex Abis, if required.
l l
2.35.3.3 Algorithm for Half-Rate Channel Allocation Triggered by Abis Overload Abis Timeslot Allocation for the TCH
Generally, the resources in the Flex Abis resource pool are allocated to the TCH according to its type. The allocation principles are as follows: l l For a full-rate TCH, the 16 kbit/s Abis timeslot is allocated. For a half-rate TCH, the 8 kbit/s Abis timeslot is allocated.
After Flex Abis is enabled, the Abis interface may experience insufficiency in transmission resources prior to the Um interface. In such a case, the half-rate channel allocation is triggered according to the load of the Abis interface transmission resources to increase the success rate of access. When the proportion of the remaining Abis resources to the total Abis resources is smaller than Congestion remain ratio, the system allocates half-rate channels to newly-accessed MSs if PSDOWN(PS Downspeeding) load control is applied. If CSFHHO(CS TCHF-TCHH HO) load control is applied, the system hands the MSs on the full-rate channels over onto the halfrate channels. In this manner, more MSs can gain access to the network, thus increasing usage efficiency of transmission resources.
When the Abis resource usage drops below the congestion threshold, the system stops PSDOWN (PS Downspeeding) and CSFHHO(CS TCHF-TCHH HO) load control.
NOTE
Congestion threshold is set for controlling usage of the transmission bandwidth. When the threshold is reached, the following methods of load control can be applied. l PSDOWN(PS Downspeeding): PS service rate decrease l CSPH(CS Preference TCHH): Allocation of half-rate channels to newly-accessed MSs requesting CS services l AMRC(AMRC): Limited AMR rate for MSs in CS services l CSFHHO(CS TCHF-TCHH HO): Handover of MSs in CS services from the full-rate channel to the half-rate channel The execution sequence of PSDOWN(PS Downspeeding), AMRC(AMRC), CSPH(CS Preference TCHH), and CSFHHO(CS TCHF-TCHH HO) is specified by the parameters LDR First, LDR Second, LDR Third, and LDR Fourth.
When all the Abis interface transmission resources are occupied, the new CS service can preempt the Abis interface transmission resources of the PS service. For details, see Abis Resources of the PS Service Preempted by the CS Service.
Abis Timeslot Allocation for the PDCH

After Flex Abis is enabled, the transmission resources of the PS service are allocated in the following ways to improve the utilization of transmission resources: l l The BSC allocates a primary link on a per 16 kbit/s sub-timeslot basis. The BSC dynamically allocates secondary links in steps of 16 kbit/s according to the required coding rate of the Um interface.
NOTE
After Flex Abis is enabled, the Abis interface transmission resources can be dynamically allocated without configuring the static PDTCH and Idle TS Count if the actual traffic volume is far lower than the estimated value in network planning. That is, the primary link and secondary link are dynamically allocated to the PS service.
If the traffic volume of the PS service remains low, the configuration of static PDTCH and Idle TS Count is not required. When the CS traffic is heavy, all Abis interface transmission resources may be occupied. In this case, no Abis resource is available for the subsequent PS service. Therefore, when the CS traffic is heavy, some static PDTCHs should be reserved. In addition, the parameter Idle TS Count should be configured to preserve dedicated timeslots for the PS service so that the GPRS or EGPRS service can still be normally processed.
Abis Resources of the PS Service Preempted by the CS Service

The CS service and PS service share the Abis interface transmission resources. The CS service can preempt the resources of PS service on the secondary link (or even the primary link when necessary) in the same-level and lower-level BTSs. In built-in PCU configuration mode, you are advised to set Sublink Resources Preemption Switch and Low-level Sublink Resource Preempt Switch to Yes to allow the CS service to preempt the transmission resources of the PS service on the secondary link in the same-level or lower-level BTSs. In external PCU configuration mode, you are advised to set PCU Support PREEMPT_ABIS_LINK Message to Support to allow the CS service to preempt the
transmission resources of the PS service if the PCU supports the processing of the PREEMPT_ABIS_LINK message.

Configuration of the Cascaded BTSs
l l l If a cascaded BTS is expected to support Flex Abis, the parameter Flex Abis Mode of the upper-level BTS must be set to Flex Abis. If the parameter Flex Abis Mode of a cascaded BTS is set to SemiSolid, Flex Abis Mode of all the lower-level BTSs must be set to SemiSolid. The master cabinet group of the level 1 BTS is connected to the EIUa only through the E1 port of the master cabinet group. The slave cabinet group of the level 1 BTS is cascaded to the EIUa through the internal connections of the master cabinet group or is directly connected to the EIUa through the E1 port of the slave cabinet group. The BTSs are cascaded only through the E1 ports of the master cabinet group. The slave cabinet group is cascaded with the upper-level BTS only through the master cabinet group. The slave cabinet groups in the same BTS cannot be cascaded. Each BTS is cascaded with only one upper-level BTS. One BTS cannot be connected to an upper-level BTS and a EIUa at the same time.
Configuration of BTS combined cabinets and cabinet groups

For the combined cabinets or cabinet groups of the double-transceiver BTS and the BTS that does not support Flex Abis, the suggestions on the configuration are as follows: l The parameter Flex Abis Mode of the Abis interface between the double-transceiver BTS and the BTS that does not support Flex Abis or between the two BTSs that do not support Flex Abis should be set to Fix Abis. The parameter Flex Abis Mode of the Abis interface between the double-transceiver BTS and the BSC or between the double-transceiver BTSs should be set to Flex Abis or SemiSolid.
Other Suggestions on the Configuration

For a Flex Abis enabled BTS, certain timeslots except the permanently allocated timeslots (such as signaling timeslots and monitoring timeslots) on E1 links can be disabled. These disabled timeslots can be used in other transmission modes (such as satellite transmission) or in scenarios where only a few timeslots on an E1 link can be used.
2.35.5 Parameters
This chapter describes the parameters related to Flex Abis. For the meaning of each parameter, see Table 2-75. For the default value, value ranges, and MML commands of each parameter, see Table 2-76.
Issue 08 (2011-09-30)
463
Table 2-75 Parameter description (1) Parameter Description Timeslot multiplexing mode at the Abis interface of the BTS. The BTS supports two multiplexing modes: statistical multiplexing on a 64 kbit/s timeslot and physical multiplexing on a 16 kbit/s timeslot. The first mode is further classified into the following six types: 1:1, 2:1, 3:1, 4:1, 5:1, and 6:1. A BTS supports the following six types of timeslot objects: OML: operation and maintenance link of the BTS. Each BTS has only one OML. In the case of statistical multiplexing on a 64 kbit/s timeslot, the OML works at 64 kbit/s. In this case, the OML can be multiplexed only with the signaling links in the same cabinet group of the BTS. In the case of physical multiplexing on a 16 kbit/s timeslot, the OML works at 16 kbit/s. In this case, the OML uses a 16 kbit/s timeslot. ESL: extended signaling link of the BTS. If the BTS supports Flex Abis, in the case of statistical multiplexing on a 64 kbit/s timeslot, a 64 kbit/s timeslot needs to be assigned to the ESL. In this case, the ESL is always multiplexed with the OML in the 64 kbit/s timeslot. In the case of physical multiplexing on a 16 kbit/s timeslot, no timeslot is assigned to the ESL. In this case, the ESL shares the same timeslot with the OML. RSL: radio signaling layer link in each TRX. Each TRX has one RSL link. In the case of statistical multiplexing on a 64 kbit/s timeslot, the RSL link works at 64kbit/s. In this case, the RSL link can be multiplexed only with the signaling links in the same cabinet group of the BTS. In the case of physical multiplexing on a 16 kbit/s timeslot, the RSL link works at 16 kbit/s. In this case, the RSL link uses a 16 kbit/s timeslot exclusively. TCH: traffic channels in each TRX. The TCH works at 16 kbit/s. Idle: idle timeslots of the BTS. An idle timeslot works at 16 kbit/s. In the case of statistical multiplexing on a 64 kibt/s timeslot, the idle timeslots can be multiplexed only with the TCHs in the same cabinet group onto one 64 kbit/s timeslot. Semi: monitoring timeslots of the BTS. The monitoring timeslots work at 8 kbit/s, 16 kbit/s, 32 kbit/s, and 64 kbit/s. The monitoring timeslots can be multiplexed only with semi-permanent links. A 2048 Mbit/s E1 contains thirty-two 64 kbit/s timeslots. Timeslot 0 is reserved for synchronization and cannot be assigned. Statistical multiplexing means that signaling timeslots are time-division multiplexed in an E1 timeslot, such as the OML and RSL timeslots or the RSL timeslots. For example, in the case of 4:1 multiplexing, one 64 kbit/s timeslot multiplexes one OML and three RSL links or four RSL links of the BTS. The 64 kbit/s timeslot that multiplexes the OML has a multiplexing ratio of up to 4:1 even if the multiplexing ratio exceeds 4:1. HDLC and IP BTS do not support this parameter.
Multiplexing Mode
Issue 08 (2011-09-30)
464
Parameter
Description Service timeslot assignment mode for the BTS. If this parameter is set to FIX_16K_ABIS, the BSC6900 assigns a fixed Abis transmission timeslot to a TCH. If this parameter is set to FLEX_ABIS, the BSC6900 assigns an Abis transmission timeslot dynamically to a TCH (except the static PDCH) to increase the resource utilization. If this parameter is set to SEMI_ABIS, the BTS to which a TCH belongs assigns a fixed Abis transmission timeslot to the TCH while the upper-level BTS set to FLEX_ABIS assigns an Abis transmission timeslot dynamically to the TCH. This mode applies where old and new BTSs are cascaded. HDLC and IP BTS is not support this parameter. First action taken for load control Second action taken for load control Third action taken for load control Fourth action taken for load control Number of idle timeslots. You can configure up to 128 idle timeslots for the BTS at a time. A BTS can be configured with up to 512 idle timeslots. This parameter specifies whether the CS services preempt the sublink resources of PS services. Whether to permit the preemption of lower-level sublink resources. If the value of this parameter is YES, a CS domain service can preempt the sublink resources of the PS domain services on the lower-level BTS of the cascaded BTSs when the CS domain service fails to preempt the sublink of the corresponding level. Whether the PCU supports the PREEMPT_ABIS_LINK message. If the BTS supports the FLEXABIS function, the CS service can preempt the timeslots on the Abis interface used by the PS service. After the preemption occurs, the BSC6900 sends a PREEMPT_ABIS_LINK message to the PCU if the PCU can process the message. If the ratio of available TDM bandwidth is less than or equal to this value, congestion control is triggered.
Flex Abis Mode LDR First LDR Second LDR Third LDR Fourth
Idle TS Count Sublink Resources Preemption Switch
Low-level Sublink Resource Preempt Switch
PCU Support PREEMPT_ABIS_LI NK Message Congestion remain ratio
Issue 08 (2011-09-30)
465
Table 2-76 Parameter description (2) Paramete r Default Value GUI Value Range MODE1_ 1, MODE2_ 1, MODE3_ 1, MODE4_ 1, MODE5_ 1, MODE6_ 1, MODE16 K FIX_16K_ ABIS(Fix Abis), FLEX_A BIS(Flex Abis), SEMI_AB IS (Semisolid Abis) CLOSE (Close), PSDOWN (PS Downspee ding), AMRC (AMRC), CSPH(CS Preference TCHH), CSFHHO (CS TCHFTCHH HO) Actual Value Range MODE1_ 1, MODE2_ 1, MODE3_ 1, MODE4_ 1, MODE5_ 1, MODE6_ 1, MODE16 K Unit MML Comman d Impact
Multiplexi ng Mode
MODE4_ 1
None
ADD BTS (Optional)
BTS
Flex Abis Mode
FIX_16K_ ABIS
FIX_16K_ ABIS, FLEX_A BIS, SEMI_AB IS
None
ADD BTS (Optional)
BTS
LDR First
PSDOWN
CLOSE, PSDOWN , AMRC, CSPH, CSFHHO
None
SET LDR (Optional)
BSC
Issue 08 (2011-09-30)
466
Paramete r
Default Value
GUI Value Range CLOSE (Close), PSDOWN (PS Downspee ding), AMRC (AMRC), CSPH(CS Preference TCHH), CSFHHO (CS TCHFTCHH HO) CLOSE (Close), PSDOWN (PS Downspee ding), AMRC (AMRC), CSPH(CS Preference TCHH), CSFHHO (CS TCHFTCHH HO)
Actual Value Range
Unit
MML Comman d
Impact
LDR Second
AMRC
None
SET LDR (Optional)
BSC
LDR Third
CSPH
None
SET LDR (Optional)
BSC
Issue 08 (2011-09-30)
467
Paramete r
Default Value
GUI Value Range CLOSE (Close), PSDOWN (PS Downspee ding), AMRC (AMRC), CSPH(CS Preference TCHH), CSFHHO (CS TCHFTCHH HO)
Actual Value Range
Unit
MML Comman d
Impact
LDR Fourth
CSFHHO
None
SET LDR (Optional) SET BTSIDLE TS (Mandator y) SET GCELLS OFT (Optional) SET GCELLS OFT (Optional) SET BTSFLEX ABISPAR A (Optional) ADD TRMLOA DTH (Optional)
BSC
Idle TS Count Sublink Resources Preemptio n Switch Low-level Sublink Resource Preempt Switch PCU Support PREEMP T_ABIS_ LINK Message Congestio n remain ratio
None
0~512
0~512
None
BTS
NO
NO(No), YES(Yes)
NO, YES
None
Cell
NO
NO(No), YES(Yes)
NO, YES
None
Cell
NO
NO(NO), YES (YES)
NO, YES
None
BTS
15
0~100
0~100
per cent
BSC6900
2.35.6 Counters
2.35.7 Glossary

2.36 Flex MAIO

2.36.1 Introduction
2.36.1.1 Scope
This document describes the flex mobile allocation index offset (Flex MAIO) feature of Huawei GBSS. It covers the function of and technology mechanisms regarding this feature, including the interference on the frequency hopping (FH) network, principles, and engineering guidelines.


The change history provides information on the changes in the Flex MAIO feature in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Flex MAIO feature of a specific product version.
Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.36.2 Overview
The frequency resources are limited on the GSM network. Therefore, to improve the traffic bearing capability of the network in the case of frequency resource insufficiency is the main concern of operators. If a tight frequency reuse pattern is employed in areas with insufficient frequency resources, especially in cells with 1x1 frequency reuse pattern, co-channel interference or adjacent-channel interference is likely to occur. As a result, the network quality deteriorates. To solve this problem, the Flex MAIO feature is introduced. Flex MAIO is a feature through which the BSC dynamically adjusts the MAIO according to the current interference level of a channel when assigning an MAIO to the channel (note that the BSC assigns an MAIO to only a channel under activation). In this way, the BSC assigns the MAIO with the minimum interference to the channel, and the channel experiences the minimum interference in the BTS. The working mechanisms of the Flex MAIO feature are described as follows:
The BSC estimates the interference between FH channels based on the MAIOs of FH channels and updates the record of the interference of the current channel to other channels after assigning or releasing the channel. During channel assignment, the BSC selects a timeslot, assigns the MAIO with the minimum interference to the timeslot, and then preferentially assigns the channel with the minimum interference. To prevent continuous adjacent-channel interference, the BSC dynamically changes the hopping sequence number (HSN) of the current channel to randomly distribute the interference of the channel to other channels.
The Flex MAIO feature helps in utilizing the frequency resources appropriately in the case of frequency resource insufficiency and minimizes co-channel interference and adjacent-channel interference. In this way, the frequency resources are tightly reused in the BTS, and the traffic bearing capability of the network is increased.

2.36.3.1 Interference on the FH Network Allocation of Frequencies to Channels
When FH is enabled on the network, the carrier frequency changes according to the predefined hopping sequence. When FH is enabled, the mobile allocation index (MAI) of a frequency used by a channel is determined by frame number (FN), MAIO, and hopping sequence number (HSN). The formulas for calculating the MAI are as follows: Assume that there are N frequencies in the mobile allocation (MA). l l When HSN is equal to 0, that is, when cyclic FH is enabled on the network, MAI = (FN + MAIO) mod N. When HSN is not equal to 0, MAI = (FN + MAIO) mod N.
Co-Channel Interference and Adjacent-Channel Interference

The following conclusions can be drawn from the preceding formulas: l When two channels on the same timeslot have the same HSN and MA and there are some adjacent frequencies in the MA, the following cases may occur: Adjacent-channel interference occurs only when two channels on the same timeslot use the adjacent MAIOs. Co-channel interference occurs only when two channels on the same timeslot use the same MAIO. l If two channels use different MAs, the number of frequencies in the MAs and the HSN are the same, and there are adjacent frequencies or the same frequencies between MAs, the following cases may occur: If two channels use adjacent frequencies, and the MAIO difference is the same as the difference between the sequence numbers of the two adjacent frequencies in the MA tables, adjacent-channel interference is produced. For example, MA1 = {1, 6, 9, 11} and MA2 = {2, 4, 6, 8}. The difference between the sequence numbers of the adjacent frequencies in the MA tables are 0 and 1 in the direction of MA1 to MA2. If a channel hops over frequencies
in MA1 and its MAIO is 1, then this channel causes adjacent-channel interference to the channels that hop over frequencies in MA2 and whose MAIO is 1 or 2. The difference between the sequence numbers of the adjacent frequencies in the MA tables are 0 and 3 in the direction of MA2 to MA1. If a channel hops over frequencies in MA2 and its MAIO is 1, then this channel causes adjacent-channel interference to the channels that hop over frequencies in MA1 and whose MAIO is 0 or 1. If two channels use the same frequency, and the MAIO difference is the same as the difference between the sequence numbers of the same frequency in the MA tables, cochannel interference is produced. For example, MA1 = {1, 6, 9, 11} and MA2 = {2, 4, 6, 8}. The difference between the sequence numbers of the same frequency in the MA tables is 1 in the direction of MA1 to MA2. If a channel hops over frequencies in MA1 and its MAIO is 1, then this channel causes co-channel interference to the channels that hop over frequencies in MA2 and whose MAIO is 2. The difference between the sequence numbers of the same frequency in the MA tables is 3 in the direction of MA2 to MA1. If a channel hops over frequencies in MA2 and its MAIO is 1, then this channel causes co-channel interference to the channels that hop over frequencies in MA1 and whose MAIO is 0.
2.36.3.2 Working Mechanism Timeslot Interference Priority

Flex MAIO is a feature through which the BSC assigns an MAIO to a channel on a timeslot based on the interference between channels on the same timeslot. Flex MAIO adds a timeslot interference priority field to the channel assignment priority. The timeslot interference priority field records the level of the interference between the channels on the same timeslot. The interference level is recorded whenever a channel on the timeslot is assigned or released. The timeslot interference priority, however, is not of the highest weight in channel assignment. The timeslot interference priority is higher than the priorities of history occupations, TRXs, and interference but lower than the priorities of TCH rate and Flex Abis. The timeslot interference priority consists of the priorities of co-channel interference in the BTS, of adjacent-channel interference in cells, and of adjacent-channel interference between cells. l The priority of co-channel interference, regardless of the priority of co-channel interference in cells or of co-channel interference between cells, is of the highest weight. Therefore, if an MAIO is already assigned, this MAIO cannot be assigned to channels on the same timeslot in the BTS. In this way, co-channel interference is prevented in the BTS. When a channel is occupied, it may cause co-channel interference or adjacent-channel interference to other channels on the same timeslot in the BTS. In addition, the adjacentchannel interference in cells is stronger than the co-channel interference between cells. The timeslot interference priority field records the interference of all active channels on the timeslots of the BTS to a channel on a timeslot of a cell. Here, active channels refer to not only occupied TCHs but also dynamic or static PDCHs.
The weight of interference priority of a timeslot is updated whenever a channel on the timeslot is assigned or released. The details are described as follows: l The interference in cells is stronger than the interference between cells. Therefore, the value added to the weight of adjacent-channel interference in cells is greater than that added to the weight of co-channel interference between cells.
Issue 08 (2011-09-30)
The adjacent-channel interference of the TCHF is eight times that of the SDCCH/8, and two times that of the TCHH. To differentiate between the interference levels caused by different channels, different values are added to the interference priority weights of different channels. When a TCHF causes adjacent-channel interference to other channels, the adjacentchannel interference weight of each of the other channels is increased by eight. When a TCHH causes adjacent-channel interference to other channels, the adjacentchannel interference weight of each of the other channels is increased by four. When an SDCCH/8 causes adjacent-channel interference to other channels, the adjacent-channel interference weight of each of the other channels is increased by one.
Dynamic Assignment of the MAIO and HSN

The Start Flex MAIO Switch parameter specifies whether to enable Flex MAIO. The HSN Modification Switch parameter specifies whether to enable the dynamic assignment of the HSN. In addition, the HSN Modification Switch parameter can be set to ON only when the Start Flex MAIO Switch parameter is is set to ON. The principles for dynamically assigning the MAIO and HSN are as follows: l If a channel does not join in radio frequency (RF) FH, or the channel type is dynamic PDCH or static PDCH, the MAIO is not updated. The BSC uses the configured data to activate the channel. If there is an active channel on the same frequency and timeslot, and a subchannel on the timeslot is assigned, the BSC uses the HSN and MAIO of the occupied subchannel to activate the channel. If the activated HSN on the timeslot is different from the configured HSN, the BSC uses the activated HSN and the configured MAIO to activate the channel. An unused HSN is dynamically assigned if the following conditions occur: There is no active channel on the same timeslot in the cell. There are active channels on the same timeslot in all neighboring cells in the BTS. The HSNs of the active channels in neighboring cells are the configured HSN. The HSN for activating the channel is a new HSN, and the MAIO for activating the channel is the configured MAIO. If the timeslot interference records are listed by the timeslot number of the channel, configured HSN, and MAIO of the timeslot, and there is interference between channels, an MAIO with the minimum interference is dynamically assigned for channel activation.
l l

The limitations of Flex MAIO are as follows: l l l Activating Flex MAIO does not bring increased gain when baseband FH is used. Therefore, it is recommended not using baseband FH and Flex MAIO together. Only CS services support Flex MAIO. PS services do not support Flex MAIO. The FH data configuration must meet one of the following conditions: When the 1x1 frequency reuse pattern is employed and the BCCH frequency does not join in FH, all the FH channels in the BTS use the same MA and HSN. When the 1x1 frequency reuse pattern is employed and the BCCH frequency joins in FH, all the channels on timeslot 0 in the BTS share the same MA and HSN, for example, MA0 and HSN0, and the channels on other timeslots share the same MA and HSN, for example, MA1 and HSN1.
When the 1x3 frequency reuse pattern is employed and the BCCH frequency does not join in FH, the cells in the BTS use different FH data, but the FH channels in a cell use the same FH data. In addition, The MAs have the same number of frequencies configured. The HSNs are the same. One MA does not contain adjacent frequencies, but the frequencies in two MAs can be adjacent. When the 1x3 frequency reuse pattern is employed and the BCCH frequency joins in FH, the cells in the BTS use different FH data, but the HSN and the number of frequencies in the MA assigned to channels on the same timeslot are the same. In addition, one MA does not contain adjacent frequencies. The MAs assigned to channels on timeslot 0 are different from the MAs assigned to channels on other timeslots in a cell. The channels on other timeslots use the same FH data. l Interference does not exist between one FH channel and one non-FH channel or between two non-FH channels.
2.36.5 Parameters
This chapter describes the parameters related to Flex MAIO. For the meaning of each parameter, see Table 2-77. For the default value, value ranges, and MML commands of each parameter, see Table 2-78 Table 2-77 Parameter description (1) Parameter Description Whether to enable the function of Flex mobile allocation index offset (MAIO). In the tight frequency reuse case of the GSM system, adjacentchannel interference and co-channel interference easily occur between channels. If the frequency hopping function and the Flex MAIO function are enabled in a cell, adjacent-channel or co-channel interference between channels can be reduced partially. Whether dynamic use of HSNs is enabled. If the functions of frequency hopping and Flex MAIO are enabled in a cell and the value of this parameter is ON, adjacent-channel interference between channels can be reduced.
Start Flex MAIO Switch HSN Modification Switch
Table 2-78 Parameter description (2) Parameter Default Value GUI Value Range Actual Value Range Un it MML Command ADD GCELL (Optional) ADD GCELL (Optional) Im pac t Cel l Cel l
Start Flex MAIO Switch HSN Modification Switch
OFF
OFF(Off), ON (On) OFF(Off), ON (On)
OFF, ON
No ne No ne
OFF
OFF, ON
Issue 08 (2011-09-30)
474
2.36.6 Counters
2.36.7 Glossary

l l l l l l l 3GPP TS 05.02:"Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path" 3GPP TS 05.08:"Digital cellular telecommunications system (Phase 2+); Radio subsystem link control" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.37 Flow Control

2.37.1 Introduction
2.37.1.1 Scope
This document describes the functions of and technologies regarding the flow control feature of Huawei GBSS, including message arrival rate control, flow control on link access protocol on the D channel (LAPD) links, cell flow control, A interface flow control, internal flow control, and flow control based on cell priority.


The change history provides information on the changes in the flow control feature in different document versions.
There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the flow control feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description 2.37.3.6 Flow Control Based on Cell Priority is added. Parameter Change The parameters added are as follows: l Support Priority Based Flow Control l VIP Priority l VIP Cell l VIP Share in CPU Rate l VIP Access CPU Rate
2.37.2 Overview
In the BSS construction, the system capacity is dimensioned according to the presupposed traffic volume in the coverage areas. The BSS can process the services normally when the traffic volume does not exceed the dimensioned capacity. The traffic volume, however, surges in cases like galas, disasters, or severe accidents. In such cases, the traffic volume exceeds the dimensioned capacity, thus leading to overload in the BSS. If this problem is not solved, the BSS performance would sharply deteriorate, and the stable operation of the BSS cannot be ensured. To solve this problem, Flow Control is introduced. Flow Control implements the detection and precautionary measures to reduce the risks of the BSS overload. Once the overload occurs, the BSC restricts and controls the incoming services in such ways as prohibiting incoming calls and certain auxiliary functions. In this manner, the load of the BSS quickly restores to the normal state. Flow Control aims at keeping the traffic load within the range of the dimensioned capacity, stabilizing the system operation, and ensuring the highest possible traffic volume. To protect the CPU from the impact of the traffic surge and to prevent the CPU usage from being extremely high for a long while, the BSC controls the message arrival rate by restricting the number of call requests in a certain period of time. The BSC controls the message arrival rate on both the uplink and the downlink. l l On the uplink, the BSC controls the message arrival rate by restricting the number of random access request messages. On the downlink, the BSC controls the message arrival rate by restricting the number of paging messages.
The signaling messages on the LAPD links are passively discarded as a result of the LAPD link congestion. To avoid any risks due to this problem, the BSC performs flow control on the LAPD links according to the occupation of the LAPD queue and the CPU usage. To control the traffic on the LAPD links, the BSC first detects the length of I frame queue related to the LAPD link, and then discards a few messages according to the percentage of the length of I frame queue related to the LAPD links in the total length of I frame queue. To avoid call drops, the BSC discards only the channel request messages and paging messages. When a cell is overloaded, the BSC rejects the call requests from some MSs in the cell to reduce the traffic load of the cell. When the MSC is overloaded, it indicates this to the BSC by sending an OVERLOAD message. On receiving the message, the BSC controls the number of call requests to reduce the traffic load of the MSC. When batch maintenance, batch configuration, or some auxiliary functions, such as signaling tracking on the interfaces are performed, lots of CPU resources are required. To prevent the CPU usage from being excessively high, the BSS disables certain auxiliary functions to ensure the stable operation. To avoid excessively heavy load in the BSS, Huawei does not recommend batch maintenance or batch configuration.
When the BSC is enabled with the Flow Control Based on Cell Priority feature, the BSC preferentially processes the call requests from VIP cells and the paging requests from VIP users on the CN side if the BSC is overloaded. Operators are recommended to enable the Flow Control Based on Cell Priority feature in areas where high-end users are likely to appear, for example, Central Business District (CBD), classy hotels, and airports. In this manner, the call quality of high-end users is ensured, and their service experience is improved. In addition, the service quality of the operator is improved, and the brand image is strengthened.

2.37.3.1 Message Arrival Rate Control
When flow control is performed on the Abis interface to control the message arrival rate, the BSC accepts a specified number of request messages while rejecting all the remaining messages in a message arrival rate control period. On the uplink, the BSC controls the message arrival rate by restricting the number of random access request messages on the Abis interface. On the downlink, the BSC controls the message arrival rate by restricting the number of paging messages on the A interface.
Control of the Arrival Rate of Random Access Request Messages on the Abis Interface
The message arrival rate control on the Abis interface is performed when the parameter CHAN REQ Arrival Control is set to YES(Yes). The BSC monitors the number of random access request messages in real time. If the number of random access request messages exceeds Max CS CHAN REQ Num In Period within a CHAN REQ Statistical Period, the BSC rejects subsequent access requests by discarding the request messages within this period. The BSC, however, accepts random access request messages of paging response.
Control of the Arrival Rate of Paging Messages on the A Interface

The control of the arrival rate of paging messages on the Abis interface is performed when the parameter Paging Arrival Control is set to YES(Yes). The BSC monitors the number of paging messages in real time. If the number of paging messages exceeds MAX Paging Message Number In Period within a Paging Statistical Period, the BSC discards the subsequent paging messages within this period.
2.37.3.2 Flow Control on LAPD Links

When flow control is performed on the LAPD links over the Abis interface, the BSC restricts the number of messages at the earliest stage that greatly affect the traffic volume. The flow control on the LAPD links over the Abis interface enables the BSC to control the number of messages (such as paging messages and random access request messages) sent over the Abis interface according to flow control policies. Thus, the requirements for signaling load on LAPD links and system load are met. This ensures the smooth operation of CS services. On the uplink, the BSC controls the flow on the LAPD links by restricting the arrival rate of random access request messages. On the downlink, the BSC controls the flow on the LAPD
links by restricting the arrival rate of paging messages. For details on the control of the message arrival rate, see 2.37.3.1 Message Arrival Rate Control. The BSC controls the flow on the LAPD links based on the CPU usage.
UL Flow Control
If a large number of random access request messages are sent on the LAPD links over the Abis interface, the traffic volume of the BSS rapidly increases. Thus, the LAPD links are overloaded. UL flow control performed on the LAPD links aims to control the number of messages at the earliest stage to reduce the Control Plane Units (CPUs) resources consumed by the flow control function. All the Control Plane Unit for Service (CPUSs) are considered as a resource pool. In such a case, the BSC controls the number of random access request messages using load-sharing algorithm based on the CPU usage of each CPUD. There are two types of random access requests, that is, the random call access request and the transferred random call access request. l Random call access requests consist of random access requests of calling MSs and random access requests of called MSs, which are generated in the cell to which the CPUS corresponds. Random call requests are transferred from other CPUSs to the current CPUS.
The procedures of BSC handling the random access requests of calling MSs are shown in Figure 2-99.
Issue 08 (2011-09-30)
479
Figure 2-99 Procedures of BSC handling the random access requests of calling MSs
1.
When CPU usage > MOC Access CPU Rate, the BSC transfers the random access requests of calling MSs received by one CPU to another CPUS. The processing procedures are described in 3. Otherwise, the processing procedures described in 2 take place. If the number of the random access requests of calling MSs allowed by the CPU equals to or is larger than one, the CPUS handles the requests to complete the process. Otherwise, the processing procedures described in 3 take place. When CPU usage of the target CPU Share in CPU Rate, the target CPU handles the transferred random access requests of calling MSs to complete the process. Otherwise, the target CPUS discards the transferred requests to complete the process.
2.
3.
Issue 08 (2011-09-30)
480
The processing procedures of the random access requests of called MSs, as shown in Figure 2-100, are similar to those of the random access requests of calling MSs. The difference, however, lies in the parameter MTC Access CPU Rate. Figure 2-100 Procedures of BSC handling the random access requests of called MSs
The procedures of BSC handling the transferred random access request are shown in Figure 2-99 or Figure 2-100.
DL Flow Control
l Flow control depending on the length of I frame queue of the LAPD links If the rate at which the BSC sends messages on the LAPD links is higher than the rate at which the messages on the Abis interface are sent to the BTS, DL messages are accumulated in the I frame queue or are even discarded.
Issue 08 (2011-09-30)
The flow control state is determined depending on the length of I frame queue. The flow control state and flow control policies are as follows: If LAPD links are not overloaded, no message is discarded. If the LAPD links are initially overloaded, the paging messages and second paging messages of short message service (SMS) are discarded. The SMS paging messages refer to the messages that carry the Channel Needed IE information and indicate request for the SDCCH assignment. If the LAPD links are severely overloaded, all paging messages are discarded. The transition of flow control state of the LAPD links is determined by the percentage of length of I frame queue related to the LAPD links in the total length of I frame queue, as well as the specified thresholds. Figure 2-101 describes the transition of flow control state of the LAPD links. Figure 2-101 Transition of flow control state
1 Percentage of length of I frame queue < Flow Control Start Threshold 3 Percentage of length of I frame queue < Flow Control End Threshold l
2 Percentage of length of I frame queue > Flow Control End Threshold 4 Percentage of length of I frame queue > Flow Control Start Threshold
Flow control depending on the flow control level and the service type of the paging messages This function can be applied only when the BSC is connect to the HUAWEI core network product. The BSC controls the flow on the LAPD links based on the CPU usage. The BSC obtains the CPU usage of the boards once every second and compares it with the specified threshold to determine the flow control level, as described in Table 2-79. Table 2-79 Determining the DL flow control level If... CPU usage CPU Usage for Slight Paging FC Then... No flow control is required.
482
Issue 08 (2011-09-30)
If... CPU Usage for Slight Paging FC < CPU usage CPU Usage for Minor Paging FC CPU Usage for Minor Paging FC < CPU usage CPU Usage for Major Paging FC CPU Usage for Major Paging FC < CPU usage CPU Usage for Critical Paging FC CPU usage > CPU Usage for Critical Paging FC
Then... Flow control at the slight level is required. Flow control at the minor level is required. Flow control at the major level is required. Flow control at the critical level is required.
On receiving the paging messages from the MSC, the BSC determines whether to discard them according to the service type and the flow control level. Table 2-80 describes the DL flow control policies. Table 2-80 Determining the DL flow control policies Service Type CS paging Flow Control Level Critical Major, minor, slight, or no flow control PS paging ,SMS paging Secondary paging or entire network paging PS secondary paging, PS entire network paging, SMS secondary paging, or SMS entire network paging Critical or major Minor, slight, or no flow control Critical, major, or minor Slight or no flow control Critical, major, minor or slight No flow control Flow Control Policy Discarding No discarding Discarding No discarding Discarding No discarding Discarding No discarding
2.37.3.3 Cell Flow Control

When the BSC receives a channel request message but no channel is available for assignment, the cell flow control is triggered. Cell flow control is performed to avoid the following cases: l When a large number of MSs send location update requests or channel requests simultaneously, the BSC sends a large number of Immediate Assignment messages or
Issue 08 (2011-09-30)
Immediate Assignment Reject messages to the BTS. Thus, the BTS is overloaded and the transmission queue of AGCHs overflows. l After sending a channel request message, the MS retransmits the channel request message if it does not receive a real-time response from the network. When an Immediate Assignment message is discarded, the MS cannot use the activated SDCCH, which is not released until T3101 of the cell expires. Thus, the SDCCH is wasted.
The cell flow control level is determined by T1 and T2 that are defined in the 3GPP TS 48.058. When the flow control level is 0 after the cell is initiated, it indicates that no flow control is performed. That is, Abis Flow Control Timer 1 (T1) and Abis Flow Control Timer 2 (T2) are stopped. Table 2-81 describes the state transition of Abis Flow Control Timer 1 and Abis Flow Control Timer 2 and the flow control level. Table 2-81 Cell flow control Current State T1 and T2 are stopped. Event No channel is available for use in the current cell. No channel is available for use in the current cell. T1 expires. T2 is running. No channel is available for use in the current cell. T2 expires. Operation The flow control level is increased by one. T1 and T2 are started. The traffic statistics are collected. No action is taken. The flow control level is increased by one. T1 and T2 are started. The flow control level is decreased by one. If the flow control level after the decrease is still greater than 0, T2 will restart. The flow control level is decreased by one. If the flow control level after the decrease is 0, T1 and T2 will stop. Next State T1 and T2 are running.
T1 and T2 are running.
T1 and T2 are running. T2 is running. T1 and T2 are running.
T2 is running.
T1 and T2 are stopped.
Issue 08 (2011-09-30)
484

NOTE
l As specified, there are six cell flow control levels ranging from 0 to 5. l Level 0 indicates that no flow control should be performed. l Level 5 indicates that the flow control at the critical level should be performed. l Abis Flow Control Timer 1 should always be smaller than Abis Flow Control Timer 2.
When the flow control level changes, the BSC modifies MS MAX Retrans and TX-integer in the system information and retransmits the system information. By sending the new system information, the BSC instructs the MS to reduce channel request messages and to lengthen the interval of sending channel request messages. Table 2-82 describes the flow control measures that are taken when the cell flow control level changes. Table 2-82 Cell flow control level Change of Cell Flow Control Level 01 12 23 34 45 54 43 32 21 10 MS MAX Retrans TX-integer
Min(4, initial configuration) Min(2, current value) Min(2, current value) 1 1 1 Min(2, initial configuration) Min(2, initial configuration) Min(4, initial configuration) Initial configuration
If TX-integer is smaller than 4, the flow control level is set to 4. If TX-integer is smaller than 7, the flow control level is set to 7. If TX-integer is smaller than 10, the flow control level is set to 10. If TX-integer is smaller than 13, the flow control level is set to 13. TX-integer is 15. TX-integer is set to Max(13, initial configuration). TX-integer is set to Max(10, initial configuration). TX-integer is set to Max(7, initial configuration). TX-integer is set to Max(4, initial configuration). TX-integer is restored to the initial configuration.
The duration of T3122 specified in the Immediate Assignment Reject message sent by the BSC varies with the cell flow control level. The higher the cell flow control level, the longer the duration of T3122, that is, the MS waits a longer period of time before retransmitting a channel request message.
Issue 08 (2011-09-30)
485
2.37.3.4 A Interface Flow Control

When the MSC is overloaded, it indicates this to the BSC by sending an OVERLOAD message. On receiving the message, the BSC starts the flow control and reduces the load of the MSC by decreasing the services that should be processed by the MSC. The A interface flow control is enabled when A Interface Flow Control Enable is set to YES(Yes). As specified, there are seven flow control levels ranging from 0 to 6. The flow control level is determined by T17 and T18 that are defined in the 3GPP TS 48.008. When the flow control level is 0, it indicates that no flow control is performed. That is, T17 -s (T17) and T18 -s (T18) are stopped. Table 2-83 describes the state transition of T17 -s and T18 -s and the flow control level. Table 2-83 A interface flow control Current State T17 and T18 are stopped. Event The BSC receives an OVERLOAD message from the MSC. The BSC receives an OVERLOAD message from the MSC. T17 expires. T18 is running. The BSC receives an OVERLOAD message from the MSC. T18 expires. Operation The flow control level is increased by one. T17 and T18 are started. None. Next State T17 and T18 are running.
None. The flow control level is increased by one. T17 is started, and T18 is restarted. The flow control level is decreased by one. If the flow control level after the decrease is still greater than 0, T18 will be restarted. The flow control level is decreased by one. If the flow control level after the decrease is 0, T17 and T18 will stop.
T18 is running. T17 and T18 are running.
T18 is running.
If the flow control level is not 0, it indicates that the A interface flow control should be performed. To control the flow on the A interface, the BSC takes control measures on either the Abis interface or on the A interface, which is specified by the parameter A Interface Flow Control Method. On the Abis interface, the BSC restricts the number of access request messages; whereas, on the A interface, the BSC restricts the number of service request messages heading for the MSC. When MSC Pool is not enabled, the BSC controls the flow on the A interface by taking measures on the Abis interface. On receiving the random access request messages, the BSC obtains the
service rejection rate on the basis of the flow control level if the A interface flow control level is above 0. Then, the BSC discards the random access request messages accordingly. The service rejection rates at different flow control levels are specified by the following parameters: A IF FC Service Rate in Level 1, A IF FC Service Rate in Level 2, A IF FC Service Rate in Level 3, A IF FC Service Rate in Level 4, A IF FC Service Rate in Level 5, and A IF FC Service Rate in Level 6. When discarding the random access request messages, the BSC first obtains their access causes, that is, call origination, call termination, location update, and other causes. After that, the BSC determines whether the messages can be discarded according to the access cause. If the messages cannot be discarded, the BSC will not discard the messages. The parameters A IF FC Discard MOC Enable, A IF FC Discard MTC Enable, A IF FC Discard LOC UP Enable, and A IF FC Discard Other Service Enable specify whether the messages with the access cause can be discarded. For example, if A IF FC Discard MOC Enable is set to NO(No), the BSC does not discard the random access request messages with the cause of call origination. When MSC Pool is enabled, the BSC controls the flow on the A interface by taking measures on the A interface. The reason is that overload may occur in one MSC in the MSC pool. If the measures are taken on the Abis interface, the traffic will have to decrease and the capacity of the BSS may get adversely affected. First, the BSC chooses the MSC where the call should be processed according to the working principles of the MSC Pool. Then, the BSC decides on whether the MSC is overloaded. If the corresponding MSC is overloaded, the BSC restricts the number of calls in the same manner as that when the MSC Pool is not enabled. If the corresponding MSC is not overloaded, the BSC does not restrict the number of calls.
2.37.3.5 Internal Flow Control

The maintenance functions and auxiliary functions provided by the BSC, such as signaling tracing on the interfaces and dynamic channel adjustment, consume the CPU resources when they are enabled. When the CPU usage is high, the execution of the functions may deteriorate the performance of the BSS. Therefore, the BSS disables certain functions when the CPU usage exceeds 80%. A higher CPU usage requires more functions to be disabled. As the CPU usage increases, the functions are disabled in the following order: cell frequency scan, common logs, CHR logs, forced handover, handover candidate query, queuing for channel allocation, preemption of radio channels, dynamic conversion of traffic channels, and dynamic conversion between traffic channels and signaling channels. Dynamic conversion of traffic channels and dynamic conversion between traffic channels and signaling channels are disabled when the CPU usage reaches close to 100%.
2.37.3.6 Flow Control Based on Cell Priority

To reduce the impact of flow control on the services of high-end users, Huawei BSC introduces the Flow Control Based on Cell Priority feature. Through this feature, operators can categorize cells into VIP cells and non-VIP cells and assign each cell a priority level. The Flow Control Based on Cell Priority feature is developed on the basis of the flow control algorithm. In this feature, the flow control measures taken by the BSC to process the calls from VIP cells and paging messages to VIP users are different from the flow control measures taken by the BSC to process the calls from non-VIP cells and paging messages to common users. The Flow Control Based on Cell Priority feature is enabled when the Support Priority Based Flow Control parameter is set to YES(Yes). An MS is considered as a VIP user when the eMLPP priority of the MS is greater than or equal to VIP Priority.
A cell is considered as a VIP cell when the VIP Cell parameter is set to YES(Yes).
Flow Control in VIP Cells

When the BSC is enabled with the Flow Control Based on Cell Priority feature, the BSC processes the random access request messages from a VIP cell in the following ways: l Message arrival rate control The BSC does not perform flow control on the random access request messages received from the CS domain of a VIP cell. Specifically, the BSC does not discard a single random access request message from the CS domain and counts every random access request message received from the CS domain of the VIP cell. l PS arrival rate control The BSC does not perform flow control on the random access request messages received from the PS domain of a VIP cell. Specifically, the BSC does not discard a single random access request message from the PS domain and counts every random access request message received from the PS domain of the VIP cell. l A interface flow control The BSC does not perform flow control on the random access request messages received from a VIP cell. Specifically, the BSC does not discard a single random access request message received from the VIP cell. l Control of call forwarding When the usage of a CPU is lower than Share in CPU Rate, the BSC allows this CPU to process the calls forwarded from other busy CPUs. When the usage of a CPU is greater than or equal to Share in CPU Rate but smaller than VIP Share in CPU Rate, the BSC allows this CPU to process only the VIP calls forwarded from other busy CPUs and directly rejects the common calls forwarded from other busy CPUs. When the usage of a CPU is greater than or equal to VIP Share in CPU Rate, the BSC rejects any calls forwarded from other busy CPUs. l Control of call access When the usage of a CPU is smaller than both MOC Access CPU Rate and MTC Access CPU Rate, the BSC allows the CPU to process any call. When the usage of a CPU is greater than or equal to MOC Access CPU Rate but smaller than VIP Access CPU Rate, the BSC allows the CPU to process only calls made by VIP users. When the usage of a CPU is greater than or equal to MTC Access CPU Rate but smaller than VIP Access CPU Rate, the BSC allows the CPU to process only calls addressed to VIP users. When the usage of a CPU is greater than or equal to VIP Access CPU Rate, the BSC forwards the calls made by or addressed to VIP users to other CPUs for processing. When the usage of all CPUs in the system is greater than or equal to VIP Access CPU Rate, the BSC rejects any call. l Cell flow control and internal flow control The cell flow control or internal flow control is irrelevant to the Flow Control Based on Cell Priority feature.
Flow Control on Paging Requests Sent to VIP Users

When the BSC is enabled with the Flow Control Based on Cell Priority feature, the BSC considers that a paging message is to the VIP user only when the eMLPP priority carried in the paging message is greater than or equal to VIP Priority. The BSC processes the paging messages to VIP users in the following ways: l Control of message arrival rate of paging messages The BSC does not perform flow control on paging messages sent to VIP users. Specifically, the BSC does not discard a single paging message and counts every paging message sent to VIP users. l LAPD congestion control The BSC does not perform flow control on paging messages sent to VIP users. Specifically, the BSC does not discard a single paging message and directly forwards the paging message to the BTS. l Cell flow control and internal flow control The cell flow control or internal flow control is irrelevant to the Flow Control Based on Cell Priority feature.
2.37.3.7 3.7 Flow Control Based on Transmission Resource Management State

The allocation and management of all transmission resources are performed by the Main Processing Unit (MPU) of the BSC. When there is a burst of traffic, the CPU usage of the MPU will sharply increase. If the CPU usage remains high for a long period, the board on which the MPU is located will be reset. To solve this problem and ensure the system stability, the CPUS is used to control the number of MSs accessing the network when the traffic volume surges. Timers T1 and T2 are used in the flow control based on transmission resource management state. The BSC adjusts the flow control level based on the state of the timers. When the flow control level is zero, T1 and T2 are not running. Table 2-84 describes the flow control state transition during the flow control based on transmission resource management state. Table 2-84 Flow control state transition during the flow control based on transmission resource management state Current State T1 and T2 are not running. Event The CPUS receives the congestion notification from the MPU. The CPUS receives the congestion notification from the MPU. T1 expires. T2 is running. The CPUS receives the congestion notification from the MPU. No action is taken. The flow control level is increased by one. T1 and T2 are started. Action The flow control level is increased by one. T1 and T2 are started. Next State T1 and T2 are running.
T2 is running. T1 and T2 are running.
Issue 08 (2011-09-30)
489
Current State
Event T2 expires.
Action The flow control level is decreased by one. If the flow control level after the decrease is still greater than 0, T2 will be restarted. The flow control level is decreased by one. If the flow control level after the decrease is 0, T1 and T2 will be stopped.
Next State T2 is running.
NOTE
There are five flow control levels ranging from 0 to 4. l Level 0 indicates that flow control needs not to be performed. l Level 4 indicates that flow control at the critical level needs to be performed. l T1 and T2 are internal timers. The value of T1 must be smaller than that of T2.
Policies of flow control based on transmission resource management state vary with the flow control levels and service types. Table 2-85 describes the flow control rates for different service types at different flow control levels. The flow control rate is the percentage of service requests rejected by the CPUS. The flow control based on transmission resource management state is applicable to only CS services and PS services and is not applicable to signaling services such as location update and short message services. Table 2-85 Policies of flow control based on transmission resource management state Flow Control Level Flow Control Rate (%) Emergency Call and VIP Call MS-originated CS Call and MSterminated CS Call 0 30 70 100 100 Call Reestablishme nt and Group Call 0 70 100 100 100 PS Service
0 1 2 3 4
0 0 0 0 50
0 70 100 100 100
Issue 08 (2011-09-30)
490
When the flow control level is not zero, ongoing services' requests for sublinks will be rejected, and no more transmission resources will be allocated to these services. When the CPU usage of the MPU exceeds 95% or the rate of transmission resources occupied by message blocks exceeds 90%, the MPU rejects all the resource allocation requests to prevent possible failures.

Flow Control greatly contributes to the stable operation of the BSS. Huawei recommends that the Flow Control feature be always enabled in the BSC in normal situations. Huawei also recommends that the parameters CHAN REQ Arrival Control and Paging Arrival Control be always set to YES(Yes). The thresholds of the message arrival rate are specified according to the BSC characteristics and the profound field experience of Huawei. The thresholds should not be modified. Flow Control Start Threshold and Flow Control End Threshold for the LAPD links should be specified according to the actual situation. Huawei recommends that Flow Control Start Threshold be set to 90 and Flow Control End Threshold be set to 80 to avoid sharp fluctuation in the load on the LAPD links. Other thresholds related to the flow control on the LAPD links are specified according to the BSC characteristics and profound field experience of Huawei. The thresholds should not be modified. When MSC Pool is enabled, the parameter A Interface Flow Control Method should be set to A(A). When MSC Pool is not enabled, the parameter A Interface Flow Control Method should be set to ABIS(Abis).
2.37.5 Parameters
The following describes the parameters related to Flow Control. For the meaning of each parameter, see Table 2-86. For the default value, value ranges, and MML commands of each parameter, see Table 2-87. Table 2-86 Parameter description (1) Paramete r A IF FC Discard LOC UP Enable A IF FC Discard MOC Enable A IF FC Discard MTC Enable
Issue 08 (2011-09-30)
Description
Whether to allow flow control for the location update services during the A interface flow control
whether to allow flow control for the mobile-originated services during the A interface flow control
Whether to allow flow control for the mobile-terminated services during the A interface flow control
Paramete r A IF FC Discard Other Service Enable A IF FC Service Rate in Level 1 A IF FC Service Rate in Level 2 A IF FC Service Rate in Level 3 A IF FC Service Rate in Level 4 A IF FC Service Rate in Level 5 A IF FC Service Rate in Level 6 A Interface Flow Control Enable
Description
Whether to allow flow control for the other services including emergency call, call re-establish, and LMU services during the A interface flow control
Rate of discarded services in level 1 of the A interface flow control
Whether to enable the A interface flow control mechanism in the BSC6900 Flow control method used by the BSC6900. Flow control method at the Abis interface: When receiving a channel request message, the BSC6900 begins flow control on the call according to the flow control level of the A interface. Flow control method at the A interface: When establishing an SCCP connection, the BSC6900 begins flow control according to the flow control level of the A interface and releases part of the call. Used along with "Abis Flow Control Timer 2" to control the change in cell flow control levels.When the flow control level in the cell changes, the values of MS MAX Retrans and Tx-integer in the system information are changed accordingly. When immediate assignment fails, the BSC6900 starts T1 and T2.
A Interface Flow Control Method Abis Flow Control Timer 1
Issue 08 (2011-09-30)
492
Paramete r Abis Flow Control Timer 2 CHAN REQ Arrival Control
Description Used along with "Abis Flow Control Timer 1" to control the change in cell flow control levels.When the flow control level in the cell changes, the values of MS MAX Retrans and Tx-integer in the system information are changed accordingly. When immediate assignment fails, the BSC6900 starts T1 and T2.
This parameter indicates whether the arrival of channel request messages is controlled. Statistic period of the arrival rate of channel request messages. Within the preset value of this parameter, the BSC6900 counts the number of channel request messages. Once the current total number of times exceeds the value of the allowable number of channel request messages of CPU0 within the statistic period, the BSC begins to discard subsequent channel request messages until the current time reaches a new "CHAN REQ Statistical Period".
CHAN REQ Statistical Period CPU Usage for Critical Paging FC CPU Usage for Major Paging FC CPU Usage for Minor Paging FC CPU Usage for Slight Paging FC Flow Control End Threshold Flow Control Start Threshold Max CS CHAN REQ Num In Period
Threshold for critical flow control. When the usage of the CPU exceeds the threshold, the CPUS performs critical flow control for paging messages.
Threshold for major flow control. When the usage of the CPU exceeds the threshold, the CPUS performs major flow control for paging messages.
Threshold for minor flow control. When the usage of the CPU exceeds the threshold, the CPUS performs minor flow control for paging messages.
Threshold for slight flow control. When the usage of the CPU exceeds the threshold, the CPUS performs slight flow control for paging messages.
Threshold for stopping RSL flow control. If the occupancy of the LAPD queue is less than this threshold, the BSC6900 stops flow control.
Threshold for starting RSL flow control. If the occupancy of the LAPD queue is greater than this threshold, the BSC6900 starts flow control.
Maximum number of allowable CS domain channel request messages within the value of "CHAN REQ Statistical Period"
Issue 08 (2011-09-30)
493
Paramete r MAX Paging Message Number In Period
Description
Maximum number of paging messages that the BSC can process over the A interface within a measurement period Usage threshold of the CPU for calling access. If the usage of the CPU exceeds the threshold, the calling access request is transferred to other CPU for processing. If the value of this parameter is less than "Share in CPU Rate", the parameter "Share in CPU Rate", "MOC Access CPU Rate" and "MTC Access CPU Rate" will be changed to the Recommended value automatically. Maximum number of Channel Request messages that can be sent by an MS in an immediate assignment procedure. After the MS initiates the immediate assignment procedure, it always listens to the messages on the BCCH and all the common control channels (CCCHs) in the CCCH group to which the MS belongs. If the MS does not receive Immediate Assignment or Immediate Assignment Extend messages, it retransmits Channel Request messages at a specified interval. If the downlink quality is poor, the MS may send SABM frames to the BTS multiple times. Usage threshold of the CPU for called access. If the usage of the CPU exceeds the threshold, the called access request is transferred to other CPU for processing.If the value of this parameter is less than "Share in CPU Rate", the parameter "Share in CPU Rate", "MOC Access CPU Rate" and "MTC Access CPU Rate" will be changed to the Recommended value automatically.
MOC Access CPU Rate
MS MAX Retrans
MTC Access CPU Rate Paging Arrival Control Paging Statistical Period
This parameter indicates whether the arrival of paging messages are controlled.
Measurement period for calculating the arrival rate of paging messages Usage threshold of the CPU for call access from other CPU. If the usage of the CPU exceeds the threshold, the call access request is discarded. If the value of this parameter is greater than "MOC Access CPU Rate" or "MTC Access CPU Rate", the parameter "Share in CPU Rate", "MOC Access CPU Rate" and "MTC Access CPU Rate" will be changed to the Recommended value automatically.
Share in CPU Rate Support Priority Based Flow Control
This parameter specifies whether to support flow control based on priority. When this parameter is set to on, the system preferentially admits the calls initiated by VIP users. T17 timer. When receiving an MSC overload message or a single point congestion message for the first time, the BSC6900 increases the level of the A interface flow control and starts the T17 and T18 timers at the same time. Timers T17 and T18 are set for adjusting the flow control level over the A interface.
T17 -s
Issue 08 (2011-09-30)
494
Paramete r
Description T18 timer. When receiving an MSC overload message or a single point congestion message for the first time, the BSC6900 increases the level of the A interface flow control and starts the T17 and T18 timers at the same time. Timers T17 and T18 are set for adjusting the flow control level over the A interface. Timer for the BSC waiting for an Establish Indication message after sending an Immediate Assignment message. If T3101 expires before the BSC receives an Establish Indication message, the BSS releases the seized SDCCH. Timer carried by the Wait Indication information element when the BSC6900 sends an immediate assignment reject message to an MS. After the MS receives the immediate assignment reject message, the MS reattempts to access the network after the timer expires. Tx-integer (T for short). This parameter specifies the number of timeslots between two transmissions when an MS sends multiple consecutive channel requests. The access algorithm is defined in GSM Rec. 04.08 to reduce the collisions on the RACH and improve the efficiency of the RACH. The algorithm specifies three parameters: Tx-integer (T for short), maximum number of retransmissions (RET), and S related to channel combination. This parameter works with the configuration of the CCCH to determine the parameter S. The relations between this parameter and the configuration of the CCCH are as follows: When this parameter is set to 3, 8, 14, or 50, S is 55 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 3, 8, 14, or 50, S is 41 if the CCCH and SDCCH share a physical channel. When this parameter is set to 4, 9, or 6, S is 76 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 4, 9, or 6, S is 52 if the CCCH and SDCCH share a physical channel. When this parameter is set to 5, 10, or 20, S is 109 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 5, 10, or 20, S is 58 if the CCCH and SDCCH share a physical channel. When this parameter is set to 6, 11, or 25, S is 163 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 6, 11, or 25, S is 86 if the CCCH and SDCCH share a physical channel. When this parameter is set to 7, 12, or 32, S is 217 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 7, 12, or 32, S is 115 if the CCCH and SDCCH share a physical channel. The timeslot for sending messages is a random value from the collection of {0, 1..., MAX(T, 8)-1}. The number of timeslots (excluding the timeslot used to send messages) between two adjacent channel request messages is a random value from the collection of {S, S+1, ..., S+T-1}. When T increases, the interval between two adjacent channel requests increases, and RACH conflicts decrease. When S increases, the interval between two adjacent channel request messages increases, and RACH conflicts decrease, thus improving the usage of AGCH and SDCCH. The access time of the MS, however, is prolonged and the network performance is decreased when T and S increase. Under normal conditions, an appropriate T value should be used to ensure that S is as low as possible, and ensure that AGCH and SDCCH are not overloaded.
T18 -s
T3101
T3122
TX-integer
Issue 08 (2011-09-30)
495
Paramete r
Description This parameter specifies the usage threshold of the CPU for VIP user calls that can be admitted. When the usage of a CPU is greater than this threshold, the new service requests from VIP users are transferred to another CPU for processing. When the usage of all CPUs is greater than this threshold, all new service requests are rejected. Is VIP Cell.The parameter is used for BSC6900 flow control. This parameter specifies the eMLPP priority value corresponding to the VIP call. When the eMLPP(Enhanced Multi-Level Precedence and Pre-emption service) priority value of a user is greater than or equal to the value of this parameter, the user is a VIP user. This parameter specifies the usage threshold of the CPU for VIP user calls that are transferred from other CPUs. When the usage of a CPU is greater than this threshold, the VIP service requests transferred from other CPUs are directly discarded.
VIP Access CPU Rate VIP Cell
VIP Priority VIP Share in CPU Rate
Table 2-87 Parameter description (2) Parameter A IF FC Discard LOC UP Enable A IF FC Discard MOC Enable A IF FC Discard MTC Enable A IF FC Discard Other Service Enable A IF FC Service Rate in Level 1 Defa ult Value GUI Value Range Actual Value Range Unit MML Command Impac t
YES
NO(No), YES (Yes)
NO, YES
None
SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional)
BSC
YES
NO(No), YES (Yes) NO(No), YES (Yes)
NO, YES
None
BSC
YES
NO, YES
None
BSC
YES
NO(No), YES (Yes)
NO, YES
None per cent
SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional)
BSC
0~100
0~100
BSC
Issue 08 (2011-09-30)
496
Parameter A IF FC Service Rate in Level 2 A IF FC Service Rate in Level 3 A IF FC Service Rate in Level 4 A IF FC Service Rate in Level 5 A IF FC Service Rate in Level 6 A Interface Flow Control Enable A Interface Flow Control Method Abis Flow Control Timer 1 Abis Flow Control Timer 2 CHAN REQ Arrival Control CHAN REQ Statistical Period CPU Usage for Critical Paging FC
Defa ult Value
GUI Value Range
Actual Value Range
Unit
MML Command SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCTMR (Optional) SET BSCTMR (Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional)
Impac t
0~100
0~100
per cent per cent per cent per cent per cent
BSC
0~100
0~100
BSC
10
0~100
0~100
BSC
10
0~100
0~100
BSC
10
0~100
0~100
BSC
NO
NO(No), YES (Yes)
NO, YES
None
BSC
ABIS
ABIS(Abis), A(A)
ABIS, A
None
BSC
30
10~255
10~255
BSC
60
10~255 NO(No), YES (Yes)
10~255
BSC
YES
NO, YES
None
BSC
1000
100~600000
100~600000
ms per cent
BSC
90
50~95
50~95
BSC
Issue 08 (2011-09-30)
497
Parameter CPU Usage for Major Paging FC CPU Usage for Minor Paging FC CPU Usage for Slight Paging FC Flow Control End Threshold Flow Control Start Threshold Max CS CHAN REQ Num in Period MAX Paging Message Number In Period MOC Access CPU Rate
Defa ult Value
GUI Value Range
Actual Value Range
Unit
MML Command SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET GTRXFC (Optional) SET GTRXFC (Optional) SET BSCFCPAR A(Optional)
Impac t
85
50~95
50~95
per cent per cent per cent per cent per cent
BSC
80
50~95
50~95
BSC
75
50~95
50~95
BSC
55
0~100
0~100
TRX
85
0~100
0~100
TRX
100
10~800
10~800
None
BSC
220
10~65535
10~65535
None per cent
SET GCELLSOF T(Optional) SET BSCFCPAR A(Optional)
Cell
80
50~95 1_Times (1_Times), 2_Times (2_Times), 4_Times (4_Times), 7_Times (7_Times)
50~95
BSC
MS MAX Retrans MTC Access CPU Rate Paging Arrival Control
4_Tim es
1_Times, 2_Times, 4_Times, 7_Times
None per cent
SET GCELLCCB ASIC (Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional)
Cell
85
50~95
BSC
YES
NO, YES
None
BSC
Issue 08 (2011-09-30)
498
Parameter Paging Statistical Period Share in CPU Rate Support Priority Based Flow Control
Defa ult Value
GUI Value Range
Actual Value Range
Unit
MML Command SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional) SET BSCAITFT MR (Optional) SET BSCAITFT MR (Optional) SET GCELLTM R(Optional) SET GCELLTM R(Optional)
Impac t
1000
100~600000
100~600000
ms per cent
BSC
75
50~95
50~95
BSC
NO
NO(No), YES (Yes)
NO, YES
None
BSC
T17 -s
30
1~300
1~300
BSC
T18 -s
60
1~300
1~300
MSC
T3101
3000
500~60000
500~60000
ms
Cell
T3122
10
0~255 TX_3(3), TX_4(4), TX_5(5), TX_6(6), TX_7(7), TX_8(8), TX_9(9), TX_10(10), TX_11(11), TX_12(12), TX_14(14), TX_16(16), TX_20(20), TX_25(25), TX_32(32), TX_50(50)
0~255
Cell
TX-integer VIP Access CPU Rate
TX_3 2
TX_3, TX_4, TX_5, TX_6, TX_7, TX_8, TX_9, TX_10, TX_11, TX_12, TX_14, TX_16, TX_20, TX_25, TX_32, TX_50
None per cent
SET GCELLIDL EBASIC (Optional) SET BSCFCPAR A(Optional)
Cell
95
50~95
50~95
BSC
Issue 08 (2011-09-30)
499
Parameter
Defa ult Value
GUI Value Range
Actual Value Range
Unit
MML Command ADD GCELL (Optional)
Impac t
VIP Cell
NO
NO(No), YES (Yes) NONE (None), LEVEL4 (User Level 4), LEVEL3 (User Level 3), LEVEL2 (User Level 2), LEVEL1 (User Level 1), LEVEL0 (User Level 0), LEVELB (User Level B), LEVELA (User Level A)
NO, YES
None
Cell
VIP Priority VIP Share in CPU Rate
LEVE L0
NONE, LEVEL4, LEVEL3, LEVEL2, LEVEL1, LEVEL0, LEVELB, LEVELA
None per cent
SET BSCFCPAR A(Optional) SET BSCFCPAR A(Optional)
None
90
50~95
50~95
BSC
2.37.6 Counters
2.37.7 Glossary

l l l l l l
Issue 08 (2011-09-30)
3GPP TS 48.058: Base Station Controller - Base Transceiver Station (BCS-BTS) Interface Layer 3 Specification 3GPP TS 48.008: Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
BSC6900 GSM Performance Counter Reference
2.38 Frequency Hopping

2.38.1 Introduction
2.38.1.1 Scope
This document describes the frequency hopping feature of Huawei GBSS. It covers the function and mechanism of frequency hopping.


The change history provides information on the changes in the frequency hopping feature in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the frequency hopping feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.38.2 Overview
During a call, signals may be interfered when being transmitted over the air interface. Thus, some information may be lost and the transmission quality may deteriorate. To solve this problem, frequency hopping (FH) is introduced into the GSM network. With FH, different bursts are transmitted on different frequencies, but the frequency remains unchanged for each burst. The MS changes frequencies once every TDMA frame, that is, 217 times per second. Figure 2-102 shows the schematic drawing of FH. In the figure, f0, f1, f2, f3, and f4 indicate different frequencies; the shadowed blocks in different colors indicate the speech signals of different calls. Figure 2-102 Schematic drawing of FH
FH is applicable to the TCH, SDCCH, and PDCH. It is not applicable to the BCCH and other common control channels. In FH, a set of frequencies used on a specific timeslot is called an MA list. A maximum of 64 MA lists are allowed in each cell, and one MA list contains a maximum of 64 frequencies. Different timeslots on the same transceiver (TRX) can use the same or different MA lists. The BSC6900 supports three FH modes: baseband FH, radio frequency (RF) FH, and hybrid FH. The parameter Frequency Hopping Mode specifies the FH mode to be used. In baseband FH, each TRX is assigned a fixed frequency. During transmission, bursts are routed to the TRXs of the corresponding frequencies through the bus. In this manner, FH requires the
cooperation of multiple TRXs. A single TRX cannot implement baseband FH. The number of frequencies available for FH depends on the number of hopping TRXs. The non-BCCH timeslots on the BCCH TRX can participate in FH to achieve FH gains. If any TRX is faulty, all the calls that use the MA lists containing the faulty TRX are affected. In RF FH, all the bursts of a call are transmitted on the same TRX, and the TRX determines the frequency to transmit a specific burst according to the hopping sequence number (HSN). Only one TRX is required to implement FH. In addition, the number of frequencies participating in FH is not dependent on the number of TRXs, and it can be greater than the number of TRXs. Each TRX can be configured to hop over a large number of frequencies to obtain the maximum FH gain. The BCCH TRX, however, cannot participate in FH. If some TRXs adopt RF FH and other TRXs adopt baseband FH in a cell, the FH mode in this cell is called hybrid FH. In general, the underlaid subcell of a co-BCCH cell operates on a low frequency band (for example, the GSM900 band or GSM850 band) and it is assigned a small number of frequencies; the overlaid subcell of a co-BCCH cell operates on a high frequency band (for example, the DCS1800 band or PCS1900 band) and it is assigned a large number of frequencies. In addition, a tight frequency reuse pattern is generally applied in the overlaid subcell, and thus the interference is strong. In a co-BCCH cell, the TRXs in the overlaid subcell adopt RF FH, and a large number of frequencies participate in FH to obtain a great FH gain; the TRXs in the underlaid subcell adopt baseband FH so that a small number of frequencies can also implement FH. FH achieves the same effects as frequency diversity and interference diversity. l l Frequency diversity helps improve the anti-attenuation capability and speech quality of the system. Interference diversity helps overcome co-channel and adjacent-channel interference. Therefore, when FH is enabled, a tighter frequency reuse pattern can be adopted to increase the system capacity.
FH Functions in Terms of Frequency Diversity In mobile telecommunications, the radio signals during transmission may vary greatly in a short period due to the impact of Rayleigh fading. This variation is frequency dependent. If the spacing between two frequencies increases, the correlation between the frequencies decreases, and thus the attenuation properties become more independent. In a mobile telecommunications system, the frequency spacing of 200 kHz ensures that the attenuation properties of different frequencies are uncorrelated, and the frequency spacing of 1 MHz completely ensures that the attenuation properties of different frequencies are uncorrelated. With FH, the frequencies for transmitting bursts vary from time to time. This prevents Rayleigh fading from damaging all the bursts of the same MS in the same manner and thus improves the anti-attenuation capability of radio signals. In this sense, FH provides the same functions as frequency diversity. When a fast-moving MS receives two consecutive bursts on the same channel, the location change of the MS is enough to eliminate the correlation of Rayleigh fading. In this case, FH does not bring great gains. For the non-moving or slow-moving MSs in the mobile network, FH is necessary and it brings about a 6.5 dB gain. FH Functions in Terms of Interference Diversity GSM is a frequency-limited system. In an area with heavy traffic, the network capacity is limited because of the interference caused by frequency reuse. In GSM, the carrier-to-interference (C/ I) ratio may vary greatly from call to call in different frequency reuse patterns. The wanted signal level varies with the distance and obstacle factors between the MS and the base station. The interference level depends to a great extent on the co-channel and adjacent-channel interference in neighboring cells.
The system aims to allow as many MSs as possible to gain access. Without FH, if interference occurs on a frequency, the speech quality of the MSs occupying the channels on the frequency may deteriorate. With FH, interference on the frequency is spread across many MSs, that is, the interference is averaged. This improves the network performance. If the number of frequencies participating in FH is great, the impact of interference on a specific call is small, and the antiinterference capability of the network is strong. Interference diversity helps overcome cochannel and adjacent-channel interference. Therefore, when FH is enabled, a tighter frequency reuse pattern can be adopted to increase the system capacity.

2.38.3.1 Baseband FH
In baseband FH, each TRX is assigned a fixed frequency. After a burst is processed by the baseband processing unit, the system determines the frequency to transmit the burst according to the HSN. Then, the burst is routed to the transmitter of the proper frequency through the bus. Different timeslots on a TRX can use different MA lists, but the frequencies in an MA list must be a subset of the fixed frequencies assigned to all the hopping TRXs. Figure 2-103 shows the working principle of baseband FH. Figure 2-103 Working principle of baseband FH
In baseband FH, all the bursts of one call may be transmitted through multiple TRXs, and each TRX uses a fixed frequency to transmit bursts. FH is implemented by routing a burst to the transmitter of a proper frequency through the bus. For example, a call adopts the hopping sequence f0, f1, and f2. During transmission, the bursts adopting f0, f1, and f2 are routed from the baseband processing units to the transmitters of TRX1, TRX2, and TRX3 respectively. In GSM, the frequency of the BCCH must remain unchanged, that is, the BCCH cannot participate in FH. In baseband FH, other channels on the BCCH TRX except the BCCH can participate in FH to obtain FH gains. If other channels on the BCCH TRX participate in FH, it indicates that the BCCH TRX participates in FH. If other channels on the BCCH TRX do not participate in FH, it indicates that the BCCH TRX does not participate in FH. The parameter Frequency Hopping Mode of BCCH TRX specifies whether the BCCH TRX participates in FH.
When the BCCH TRX participates in FH, the MA list for the BCCH timeslot (generally, the BCCH timeslot is timeslot 0 of the BCCH TRX) is different from the MA lists for other timeslots. The MA list for the BCCH timeslot does not contain the frequency assigned to the BCCH TRX. The MA lists for other timeslots can contain the frequency assigned to the BCCH TRX. According to the implementation method of baseband FH, the maximum number of frequencies in an MA list equals the number of hopping TRXs. That is, if the number of hopping TRXs is large, the number of frequencies available for FH is large, and the effect of interference suppression is great. If the BCCH TRX participates in FH, the number of frequencies available for FH increases. This helps to improve the system performance. In baseband FH, all the bursts of one call may be transmitted through multiple TRXs. If any TRX is faulty, FH fails and call drops may occur. The combiner used for baseband FH produces low signal attenuation, and thus the coverage area is large. The number of frequencies available for FH, however, is dependent on the number of TRXs, and accordingly the FH gain is small. Therefore, baseband FH is applicable to the areas where loose frequency reuse patterns are adopted. The purpose of FH is to improve the performance and anti-interference capability of the system.
2.38.3.2 RF FH
In RF FH, each TRX is not assigned a fixed frequency, and different timeslots on one TRX and different TRXs can use different MA lists. The number of frequencies in different MA lists can be different. The number of frequencies in an MA list is not dependent on the number of hopping TRXs. It can exceed the number of hopping TRXs. During transmission, the TRX determines the frequency used to transmit a burst according to the HSN. Then, the burst is transmitted on the frequency. Figure 2-104 shows the working principle of RF FH. In the figure, f0 to fn indicate all the frequencies in an MA list. Figure 2-104 Working principle of RF FH
In comparison to baseband FH, more frequencies can be used in RF FH to obtain greater FH gains. Generally, RF FH improves the performance and anti-interference capability of the system much more than baseband FH. In general, the hybrid combiner is used for RF FH and it produces high signal attenuation. Thus, the coverage area is small. RF FH is applicable to the cells where tight frequency reuse patterns
are adopted. In these cells, co-channel and adjacent-channel interference is strong. Therefore, more frequencies are used in an MA list. The purpose is to obtain great FH gains and to improve the anti-attenuation capability of the system. If the number of frequencies participating in RF FH is greater than four, the system performance is improved significantly. The BCCH frequency must remain unchanged. In RF FH, the transmit frequency of each TRX changes. Therefore, the BCCH TRX cannot participate in RF FH.
2.38.3.3 Hybrid FH
In hybrid FH, some TRXs adopt RF FH and other TRXs adopt baseband FH in a cell. One TRX, however, can adopt either RF FH or baseband FH. For baseband FH, only the frequency assigned to each TRX participates in FH. For RF FH, one TRX can use multiple frequencies. Generally, the number of hopping frequencies is greater than the number of TRXs to obtain sufficient FH gains. If the number of TRXs in a cell is small but the frequencies are sufficient, RF FH can be adopted to improve the system performance. If the number of TRXs in a cell is large but the frequencies are insufficient, baseband FH can be adopted to improve the system performance. In general, hybrid FH is applicable to co-BCCH cells. In the overlaid subcell of a co-BCCH cell, a tight frequency reuse pattern is adopted, and thus the co-channel and adjacent-channel interference is strong. In addition, the overlaid subcell generally operates on the 1800/1900 MHz band, and the frequencies are sufficient. The underlaid subcell of a co-BCCH cell generally operates on the 900/850 MHz band, a loose frequency reuse pattern is adopted, and the frequencies are insufficient. In general, the BCCH is configured in the underlaid subcell. To adapt to these characteristics of the co-BCCH cell, hybrid FH can be adopted. In the overlaid subcell, the TRXs use RF FH and more frequencies are used to improve the anti-interference capability of the system. In the underlaid subcell, the TRXs use baseband FH to improve the system interference, and no additional frequency is required.

2.38.4.1 Limitation of the CA List on FH
An MS learns the information about the frequencies used in a cell according to the cell allocation (CA) list carried in the system information. The frequency information is used during immediate assignment and packet assignment. If FH is enabled in a cell, the BSC informs the MS of the hopping frequencies to be used during immediate assignment through the CA list, that is, these frequencies are to be used on the dedicated signaling channels. This enables the normal processing of immediate assignment. According to the 3GPP protocols, the number of frequencies in a CA list cannot exceed 64. Therefore, during data configuration, ensure that the number of frequencies used on the dedicated signaling channels does not exceed 64. Otherwise, immediate assignment may fail. If the CBCH is configured, the number of frequencies used on the dedicated signaling channels cannot exceed 32. If a large number of frequencies are used in a cell, they can be classified into two types. One type of frequencies is used by the dedicated signaling channels during immediate assignment, and the other type of frequencies is used by traffic channels. These two types of frequencies should be configured separately. The frequencies used by the dedicated signaling channels
should be contained in the CA list of the system information. The frequencies used by traffic channels are not necessarily contained in the CA list.
2.38.4.2 Limitation on Frequency Spacing

The following frequency bands can be used in GSM: GSM850, GSM900 (P-GSM), GSM900 (E-GSM), GSM900 (R-GSM), GSM1800, and GSM1900. Table 2-88 provides the mapping between the frequency bands and the absolute radio frequency channel number (ARFCN) ranges. Table 2-88 Mapping between the frequency bands and the ARFCN ranges Frequency Band GSM850 GSM900 (P-GSM) GSM900 (E-GSM) GSM900 (R-GSM) GSM1800 GSM1900 ARFCN Range ARFCN 128 to ARFCN 251 ARFCN 1 to ARFCN 124 ARFCN 0, ARFCN 975 to ARFCN 1023 ARFCN 955 to ARFCN 974 ARFCN 512 to ARFCN 885 ARFCN 512 to ARFCN 810
When ARFCNs are encoded in a CA list, there is a limitation on the frequency range, that is, frequency spacing should not be too large. If all the frequencies are on the same frequency band, the frequency spacing is equal to the maximum ARFCN minus the minimum ARFCN. For example, the frequency spacing between ARFCN 1 and ARFCN 15 is 14. If the frequencies are on different frequency bands, the frequency spacing is equal to the minimum ARFCN minus the maximum ARFCN plus 1024. For example, the frequency spacing between ARFCN 0 and ARFCN 10 is 1014. The number of frequencies in a CA list is dependent on the frequency spacing. Due to the limitation of coding schemes, if the frequency spacing is large, the number of frequencies that can be contained in a CA list is small. If all the hopping frequencies are on the GSM900 (P-GSM) band, a maximum of 64 frequencies can be configured in a CA list, and the number of frequencies in the CA list is not dependent on the frequency spacing. If the hopping frequencies are on a frequency band rather than the GSM900 (P-GSM) band or are on multiple frequency bands (for example, frequencies in the GSM900/GSM1800 cells), the frequency spacing and the number of frequencies in a cell should meet any of the following requirements. Otherwise, the CA list will not be decoded successfully. l l l l
Issue 08 (2011-09-30)
The frequency spacing is less than 111. The frequency spacing between any two frequencies is greater than 913. The total number of frequencies is smaller than or equal to 16. The total number of frequencies is 17, and ARFCN 0 is to be encoded in the CA list.
l l l
The total number of frequencies is smaller than or equal to 18, and the frequency spacing is greater than 512. The total number of frequencies is smaller than or equal to 22, and the frequency spacing is greater than 768. The total number of frequencies is smaller than or equal to 29, and the frequency spacing is greater than 896.
When configuring hopping frequencies in a cell, pay special attention to the frequency spacing and the number of frequencies. The frequencies used by the dedicated signaling channels during immediate assignment must meet the preceding requirements. Otherwise, the CA list cannot be decoded, and the immediate assignment cannot be performed properly.
2.38.4.3 Data Configuration Related to FH

Different TRXs in the same cell can adopt the same or different MA lists to perform frequency hopping. If different TRXs in the same cell use the same MA list, it is recommended that Channel MAIO of different TRXs should be different. Otherwise, strong interference may occur. If the BSC supports Flex MAIO, it automatically calculates the optimum mobile allocation index offset (MAIO) according to the hopping frequencies being used to obtain the best FH gains. Generally, all the MA lists in a cell can be configured with the same or different HSNs. It is recommended that different cells use different MA lists. If two cells use the same MA lists, it is recommended that different HSNs be configured. TSC should be the same as the corresponding BCC. It should remain unchanged.
2.38.5 Parameters
This chapter describes the parameters related to frequency hopping. For the meaning of each parameter, see Table 2-89. For the default value, value ranges, and MML commands of each parameter, see Table 2-90. Table 2-89 Parameter description (1) Parameter Description This parameter specifies the frequency hopping mode of a cell. When this parameter is set to "NO_FH", all the TRXs of the cell do not join in frequency hopping. When this parameter is set to "BaseBand_FH", the cell is in baseband frequency hopping mode. In this case, there can be TRXs that do not join in frequency hopping on the cell. When this parameter is set to "RF_FH", the cell is in RF frequency hopping mode. In this case, there can be TRXs that do not join in frequency hopping on the cell. When this parameter is set to "Hybrid_FH", the cell is in hybrid frequency hopping. In this case, some TRXs on the cell must join in baseband frequency hopping, some cells on the cell must join in RF frequency hopping, and some cells on the cell must not join in frequency hopping. Frequency hopping mode of the TRX that carries the BCCH
508
Frequency Hopping Mode Frequency Hopping Mode of BCCH TRX

Issue 08 (2011-09-30)
Parameter Channel MAIO
Description Mobile allocation index offset (MAIO) of the channel in the TRX Hopping sequence number (HSN), indicating 64 types of frequency hopping sequences. If this parameter is set to 0, the frequency hopping is performed in sequence. If this parameter is set to a value from 1 to 63, the frequency hopping is performed in a pseudorandom manner, that is a disciplinary random manner. The TSC is short for the Training Sequence Code. The TSC must be the same as the BCC. The delay equalization is performed by using the specified TSC when the MS or BTS receives the signal. The demodulation cannot be received because the delay equalization cannot be performed for the signals with same frequency using different TSCs. This can effectively prevent incorrectly invalid reception, and prevent the co-channel interference. BTS color code. It uniquely identifies different BTSs that are adjacent and use the same TRX.
HSN
TSC BCC
Table 2-90 Parameter description (2) Parameter Defau lt Value GUI Value Range NO_FH (No frequency hopping), BaseBand_ FH (Baseband frequency hopping), RF_FH(RF frequency hopping), Hybrid_F H(Hybrid frequency hopping) Actual Value Range Un it MML Command Impact
Frequency Hopping Mode
NO_F H
NO_FH, BaseBand_FH, RF_FH, Hybrid_FH
No ne
SET GCELLHO PTP (Optional) SET GCELLHO PQUICKSE TUP (Mandatory ) SET GCELLHO PQUICKSE TUP (Mandatory )
Cell
Frequency Hopping Mode of BCCH TRX
None
NO_Hop (No hop), Hop(Hop)
NO_Hop, Hop
No ne
Cell
Issue 08 (2011-09-30)
509
Parameter
Defau lt Value
GUI Value Range
Actual Value Range
Un it
MML Command SET GTRXCHA NHOP (Optional) ADD GCELLMA GRP (Optional) ADD GCELLMA GRP (Optional) ADD GCELLQU ICKSETUP (Optional)
Impact
Channel MAIO
None
0~63
0~63
No ne
Physica l channel
HSN
0~63
0~63
No ne
Cell
TSC
None
0~7
0~7
No ne
Cell
BCC
None
0~7
0~7
No ne
BTS
2.38.6 Counters
None.
2.38.7 Glossary

l l l l l l 3GPP TS 45.002 Multiplexing and multiple access on the radio path 3GPP TS 44.018 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.39 Four-Way Receive Diversity

2.39.1 Introduction
2.39.1.1 Scope
This document describes the working principle and algorithms of four-way receive diversity.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Four-Way receive diversity feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
Issue 08 (2011-09-30)
511
01 (2009-06-30)
2.39.2 Overview
In radio communication environment, the TX signals tend to be affected by the shadow fading, buildings, and landforms. The TX signals from the MS arrive at the BTS through various paths, such as line-of-sight (LOS), reflections, and dispersions. As the MS moves around, Rayleigh fading occurs when the TX signals passing through various ways are combined. To suppress Rayleigh fading, four-way receive diversity is implemented in the TRX board, that is, four receive paths receive the same signal separately. Then, the four RX signals are combined into one according to the specified algorithm. In this way, a strong useful signal is obtained, and the uplink gain is enhanced. To ensure that the diversity antennas receive signals separately from each other, the distance between diversity antennas must be greater than 10 times the radio signal wavelength or the polarization diversity is adopted. Four-way receive diversity helps to suppress Rayleigh fading and provide better signal quality on the uplink, thus improving the quality of service (QoS). In addition, four-way receive diversity can be used to improve the uplink performance in wide coverage scenarios.

Figure 2-105 shows the working principle of four-way receive diversity. The four RX signals (RXM1, RXD1, RXM2, and RXD2) are sent to one carrier in the TRX board. You should set Receive Mode to Four Diversity Receiver to enable four-way receive diversity. The following takes the Double-Transceiver Unit (DTRU) as an example to describe the working principle of four-way receive diversity. With four-way receive diversity, only one carrier in the DTRU is used.
Issue 08 (2011-09-30)
512
Figure 2-105 Working principle of four-way receive diversity
2.39.3.2 Four-Way Receive Diversity Algorithms

There are two types of four-way receive diversity algorithms: Interference Cancellation Combining (ICC) and Maximal Ratio Combining (MRC). MRC does not consider the correlation of interference on the combining diversities. Therefore, MRC is an optimum option in the case of restricted noise and no interference. In the actual network, the interference on different diversity antennas comes from the same interference source. Therefore, the interference has a certain correlation. ICC uses this correlation to eliminate some interference. ICC is a combining algorithm developed on the basis of MRC. MRC can be regarded as a special case of ICC. With four-way receive diversity, superimposed antenna thermal noise and co-channel interference occur when the TX signals arrive at the diversity antennas through different radio paths. Thus, the demodulation performance of the BTS is affected. The noise of the diversity antennas has no correlation, but the co-channel interference has a certain correlation. The ICC algorithm takes into account the correlation between interference signals. In this way, co-channel interference is suppressed, and the demodulation performance of the BTS is improved. See Figure 2-106.
Issue 08 (2011-09-30)
513
Figure 2-106 ICC algorithm
As shown in Figure 2-106, the ICC algorithm procedure is described as follows: 1. Through four receive paths, the signal x(k) arrives at the diversity antennas, marked r1(k), r2(k), r3(k), and r4(k). With interference and noise added, the signals are marked S1(k), S2 (k), S3(k), and S4(k). Based on the maximum signal-to-noise ratio criterion, the adaptive combining coefficients W1, W2, W3, and W4 are calculated and the output signal is obtained through the formula: y(k) = W1 x S1(k) + W2 x S2(k) + W3 x S3(k) + W4 x S4(k).
NOTE
2.
l When W1, W2, W3, and W4 are equal to 1, y(k) is the output signal calculated through the MRC algorithm. l The four receive paths shown in Figure 2-106 correspond to two pairs of main and diversity paths.
Huawei four-way receive diversity algorithms consist of the MRC algorithm and the ICC algorithm with blind detection. The ICC algorithm with blind detection avoids the negative gain obtained by the ICC algorithm in the case of restricted noise and no interference in comparison to the MRC algorithm. The ICC algorithm with blind detection is scenario-adaptive. The choice of the MRC or ICC algorithm for the signal received on each timeslot is made according to the following rules: l l For the interference-restricted scenario, the ICC algorithm is used. For the noise-restricted scenario, the MRC algorithm is used.
The ICC algorithm with blind detection processes useful signals and interference signals based on the maximum signal-to-noise ratio criterion. Therefore, the ICC algorithm features high capability to suppress multipath fading and co-channel interference, and the receiver sensitivity is improved.
Issue 08 (2011-09-30)
514

NOTE
The interference on the signals received by multiple antennas has both spatial correlation and temporal correlation. The ICC algorithm uses only the spatial correlation to eliminate the interference. The enhanced ICC (EICC) algorithm, however, takes into account these two types of interference and constructs the multidimensional combining coefficient matrix to combine the signals according to the maximum signal-tonoise ratio criterion. The EICC algorithm is most applicable to the networks where tight frequency reuse pattern is adopted and the traffic volume is high. Currently, the EICC algorithm supports only two-way receive diversity, namely, main and diversity.
2.39.4 Parameters
This chapter describes the parameters related to Four-Way receive diversity. For the meaning of each parameter, see Table 2-91. For the default value, value ranges, and MML commands of each parameter, see Table 2-92. Table 2-91 Parameter description (1) Parameter Description RF receive mode of the TRX. The BTS3012, BTS3012AE, BTS3012II, BTS3006C, and BTS3002E do not support Main Diversity. The DBS3900 GSM and BTS3900 GSM support Four Diversity Receiver and Main Diversity.
Receive Mode
Table 2-92 Parameter description (2) Parameter Defaul t Value GUI Value Range INDEPEND ENT (Independen t Receiver), DIVIDING (Dividing Receiver), FOURDIV ERSITY (Four Diversity Receiver), MAINDIV ERSITY (Main Diversity), NONE (None) Actual Value Range Uni t MML Comm and Impact
Receive Mode
None
INDEPEND ENT, DIVIDING, FOURDIV ERSITY, MAINDIV ERSITY, NONE
Non e
SET GTRX DEV (Option al)
TRX
Issue 08 (2011-09-30)
515
2.39.5 Counters
None.
2.39.6 Glossary

2.40 GPRS/EGPRS Channel Management

2.40.1 Introduction
2.40.1.1 Scope
This document describes PDCH allocation algorithm, dynamic PDCH conversion algorithm, and dynamic PDCH release algorithm in the GPRS/EGPRS channel management feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l
Issue 08 (2011-09-30)
Feature change
Feature change refers to the change in the GPRS/EGPRS channel management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows: l l l 03 (2010-11-30) 02 (2009-09-30) 01 (2009-06-30)
03 (2010-11-30)
This is the second commercial release of GBSS9.0. Compared with issue 02 (2009-09-30) of GBSS9.0, issue 03 (2010-11-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description A description of 2.40.3.1 Classification of PDCHs and 2.40.4 Engineering Guidelines is optimized. None. Parameter Change None.
Editorial change
None.
02 (2009-09-30)
01 (2009-06-30)
Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 remains unchanged.
2.40.2 Overview
After the GPRS network is deployed, CS services and PS services in the network share channel resources on the Um interface. With operators increasingly preferring PS services, more and more channel resources on the Um interface are required for PS services. At the same time, to ensure the quality of CS services and PS services, the system needs to manage all the PDCHs effectively. GPRS/EGPRS Channel Management consists of the PDCH allocation algorithm, dynamic PDCH conversion algorithm, and dynamic PDCH release algorithm. l l The PDCH allocation algorithm allocates one or more PDCHs in view of various factors. The dynamic PDCH conversion algorithm and dynamic PDCH release algorithm adjust PDCHs properly based on the service requirements and actual network conditions.
GPRS/EGPRS Channel Management ensures not only the services for one user, but also the performance of the entire network. During the PDCH allocation process, the principles and requirements for the BSC to select the final channel group vary according to the scenarios. Thus, the PDCH allocation algorithm defines a priority for each channel group. When the MS requests PDCH allocation, the BSC allocates the channel group with the highest priority to the MS according to the allocation requirement. After the MS is allocated the PDCH, the BSC determines whether to trigger dynamic PDCH conversion based on the PDCH allocation result and the average load on each PDCH in the cell. If it is necessary to trigger dynamic PDCH conversion, the BSC converts one or more dynamic PDCHs whose initial state is full-rate TCH into PDCHs. If the dynamic PDCH in the PDCH state remains idle for a period of time, the BSC converts it back to the full-rate TCH. When no channel resources or Abis resources are available for the CS service, the PDCH preemption procedure is triggered. A dynamic PDCH in the PDCH state is converted into the TCH each time. Figure 2-107 shows the process of GPRS/EGPRS channel management.
Issue 08 (2011-09-30)
518
Figure 2-107 Process of GPRS/EGPRS channel management
NOTE
For details about one phase access on the CCCH/PCCCH, two phase access on the CCCH/PCCCH, downlink TBF establishment on the CCCH/PCCCH, uplink TBF establishment on the PACCH, downlink TBF establishment on the PACCH, and TBF re-assignment/TS procedure, see the 2.41 GPRS/EGPRS Connection Control and Transfer.

2.40.3.1 Classification of PDCHs
Based on the service support capabilities, PDCHs are classified into the following types: l l EGPRS special channel The EGPRS special channel is allocated only for the EGPRS service. EGPRS priority channel The EGPRS priority channel is allocated for the EGPRS service preferentially. When the EGPRS priority channel is not occupied by the EGPRS service, it can be allocated for the GPRS service. l EGPRS normal channel The EGPRS normal channel can be allocated for the EGPRS and GPRS services at the same time.
GPRS channel The GPRS channel is allocated only for the GPRS service.
The EGPRS special channel, EGPRS priority channel, and EGPRS normal channel can be bound with a maximum of four 16 kbit/s Abis timeslots. The GPRS channel can be bound with a maximum of two 16 kbit/s Abis timeslots. These types of PDCHs can be specified by the parameter PDCH Channel Priority Type on the BSC. Based on the channel configuration types, PDCHs are classified into the following types: l Static PDCH The static PDCH carries only PS services. The parameter Channel Type is set to PDTCH, PBCCH+PDTCH, or PCCCH+PDTCH. l Dynamic PDCH The dynamic PDCH carries CS services or PS services depending on the service requirement. It supports only one type of service at the same time. The parameter Channel Type is initially set to TCH Full Rate. Static PDCHs are used by PS services to access the network. Dynamic PDCHs are adjusted based on the cell load. Static PDCHs are configured and dynamic PDCHs are adjusted based on timeslot continuity. This ensures that the requirements for PS rate are met.
2.40.3.2 PDCH Allocation Algorithm

?.1. Overview
When the uplink and downlink TBFs are not established but there is a data transfer request, the MS sends the PDCH request to the BSC for establishing the uplink TBF. The PDCH request sent from the MS is classified into the following types: l One phase access on the CCCH and PCCCH To respond to the PDCH request for one phase access, the BSC allocates one or more PDCHs based on the multislot capability of the MS. l Two phase access on the CCCH and PCCCH To respond to the PDCH request for two phase access, the BSC allocates only one radio block on the PDCH to the MS for the first time. The MS sends the packet resource request in the allocated radio block. For the second time, the BSC allocates one or more PDCHs to the MS based on the multislot capability of the MS. When the BSC receives the downlink LLC PDUs from the SGSN but no uplink or downlink TBF is available, the network sends the Immediate Assignment message on the CCCH or the Packet Downlink Assignment message on the PCCCH to the BSC for establishing the downlink TBF. l l To respond to the Immediate Assignment message on the CCCH, the BSC allocates only one PDCH to the MS. To respond to the Packet Downlink Assignment message on the PCCCH, the BSC allocates one or more PDCHs to the MS based on the multislot capability of the MS.
When the MS is in packet transfer mode, the BSC establishes the uplink or downlink TBF on the PACCH for the MS based on the service requirement. When establishing the uplink or
downlink TBF on the PACCH, the BSC allocates one or more PDCHs to the MS based on the multislot capability of the MS. The uplink or downlink TBF establishment on the PACCH is classified into the following types: l l l l Uplink TBF establishment during uplink TBF transmission Downlink TBF establishment during uplink TBF transmission Uplink TBF establishment during downlink TBF transmission Downlink TBF establishment during downlink TBF transmission
When the MS is in packet transfer mode, the BSC can reallocate the uplink or downlink TBF to the MS based on the service requirement, channel resource change, and multislot capability of the MS. The BSC can also reallocate the uplink and downlink TBFs to the MS at the same time. l l l To reallocate only the uplink TBF, the BSC sends the Packet Uplink Assignment message to the MS. To reallocate only the downlink TBF, the BSC sends the Packet Downlink Assignment message to the MS. To reallocate the uplink and downlink TBFs at the same time, the BSC sends the Packet Timeslot Reconfigure message to the MS.
?.2. Preprocessing
Through PDCH allocation preprocessing, the BSC learns the information about all PDCHs that can be allocated to MSs in the cell and determines the maximum number of uplink and downlink PDCHs. This provides a basis for subsequent PDCH allocation. The BSC learns the information on all PDCHs that can be allocated to MSs in the cell by excluding the following cases: l l If the operating status of the PDCH is unavailable or the channel management status is blocked, the PDCH cannot be allocated. If the number of MSs multiplexed on the PDCH in the uplink x 10 is greater than or equal to PDCH Uplink Multiplex Threshold, the PDCH cannot be allocated for the uplink PS service. If the number of MSs multiplexed on the PDCH in the downlink x 10 is greater than or equal to PDCH Downlink Multiplex Threshold, the PDCH cannot be allocated for the downlink PS service. The GPRS channel cannot be allocated for the EGPRS service. The EGPRS special channel cannot be allocated for the GPRS service. If the EGPRS priority channel is already allocated for the EGPRS service, it cannot be allocated for the GPRS service. When the downlink EGPRS and uplink GPRS services share the EGPRS normal channel, the downlink data blocks on this channel must be modulated with GMSK if the GPRS uplink data blocks require scheduling. This may decrease the EGPRS downlink transmission rate. Thus, the downlink EGPRS and uplink GPRS can share the EGPRS normal channel only when the parameter Allow E Down G Up Switch is set to Open.
l l l l
The BSC collects statistics on service types dynamically for a period of time by monitoring the uplink and downlink traffic volume of an MS regularly. The service types consist of the uplink preferred service, downlink preferred service, and neutral service. The details are as follows: l The BSC monitors the traffic volume of uplink and downlink LLC PDUs of the MS on a regular basis. In a specified monitoring period, if the uplink traffic volume is more than
Issue 08 (2011-09-30)
five times of the downlink traffic volume, the PS service that the MS operates in the next monitoring period is called the uplink preferred service. l The BSC monitors the traffic volume of uplink and downlink LLC PDUs of the MS on a regular basis. In a specified monitoring period, if the downlink traffic volume is more than five times the uplink traffic volume, the PS service that the MS processes in the next monitoring period is called the downlink preferred service. Except the uplink preferred service and downlink preferred service, the PS service that the MS operates in the next monitoring period is called the neutral service.
The BSC determines the maximum number of uplink and downlink channels that can be allocated to the MS according to the following principles: l For the uplink preferred service, the BSC allocates as many uplink channels as possible. If the parameter Support EDA is set to SUPPORT, the BSC allocates more than three uplink channels to the MS based on the radio access capability of the MS. If the parameter Support EDA is set to NOTSUPPORT, the BSC allocates up to two uplink channels to the MS based on the radio access capability of the MS. l For the downlink preferred service, the BSC allocates as many downlink channels as possible. If the parameter Support High Multislot Class is set to SUPPORT, the BSC allocates up to five downlink channels to the MS based on the radio access capability of the MS. Otherwise, the BSC allocates up to four downlink channels to the MS based on the radio access capability of the MS. l For the neutral service, the BSC allocates the uplink and downlink channels in a balance manner. For example, the BSC allocates three downlink channels and two uplink channels to the MS of multislot class 10.
?.3. Algorithm
The PDCH allocation algorithm is based on the priority mechanism. All PDCHs available for allocation in a cell form channel groups, and each channel group is granted a certain priority. The PDCH allocation algorithm determines whether to select a channel group based on the priority of the channel group. The channel group with high priority is allocated preferentially. The PDCH allocation algorithm considers many factors during PDCH allocation. Different factors have different impacts on the priorities of channel groups. The factors are listed as follows in descending order of impact: l MS type (GPRS/EGPRS) If the MS supports GPRS and EGPRS simultaneously, the BSC allocates the EGPRS channel to the MS preferentially. l Band supporting capability of the MS The BSC allocates only the PDCHs in the bands supported by the MS. When the MS accesses the network for the first time, the BSC allocates only the PDCHs in the BCCH band and the bands compatible with the BCCH to the MS if the BSC is unaware of the radio access capability of the MS. The GSM900 bands compatible with the BCCH consist of the P-GSM900 band, E-GSM900 band, and R-GSM900 band. The R-GSM900 band includes the frequencies in the P-GSM900 and E-GSM900 bands, and the E-GSM900 band includes the frequencies in the P-GSM900 band. If the BCCH TRX is configured in the RGSM900 band, the E-GSM900 and P-GSM900 bands are the compatible bands of the BCCH; if the BCCH TRX is configured in the E-GSM900 band, the P-GSM900 band is
the compatible band of the BCCH. Compatible bands of the BCCH are applicable to only GSM900. l Multislot class of the MS When allocating the PDCHs to the MS, the BSC considers the multislot class of the MS. The BSC supports multislot classes 1 to 45. High multislot classes 35 to 45 are treated exactly as low multislot classes 8 to 12 respectively. If the parameter Support High Multislot Class is set to SUPPORT, the BSC supports multislot classes 30 to 34 directly. Otherwise, multislot classes 30 to 34 are treated exactly as multislot classes 8 to 12. l Concentric cell If the MS is in the coverage area of the underlaid subcell, the BSC allocates only the PDCHs in the underlaid subcell to the MS. If the MS is in the coverage area of the overlaid subcell, the BSC allocates the PDCHs in the overlaid subcell to the MS preferentially. l l Number of Abis timeslots bound with the PDCH The BSC allocates the PDCH bound with more Abis timeslots to the MS preferentially. PDCH channel priority type If the MS requires the EGPRS channel, the BSC allocates the EGPRS special channel, EGPRS priority channel, and EGPRS normal channel in descending order of priorities. If the MS requires the GPRS channel, the BSC allocates the GPRS channel, EGPRS normal channel, and EGPRS priority channel in descending order of priorities. l l l l Frequency hopping attribute of the PDCH The BSC allocates the PDCH without frequency hopping to the MS preferentially. Interference level of the PDCH The BSC allocates the PDCH with less interference to the MS preferentially. Whether the PDCH is on the BCCH TRX The BSC allocates the PDCH on the BCCH TRX to the MS preferentially. Timeslot number of the PDCH The BSC allocates the channel group with larger timeslot number to the MS preferentially. The timeslot number of the channel group is the maximum timeslot number of all the channels in the channel group. If the BSC allocates only one channel to the MS, it allocates the channel in the sequence of timeslot numbers 6, 5, 7, 4, 3, 2, 1, and 0.
2.40.3.3 Dynamic PDCH Conversion Algorithm

?.1. Overview
When the PDCH allocation fails, the BSC triggers dynamic PDCH conversion in the cell. If the BSC does not learn the radio access capability of the MS including the multislot capability of the MS, it converts only one PDCH. If the BSC learns the multislot capability of the MS, it converts dynamic PDCHs as required. If the PDCHs allocated to the MS are insufficient, the BSC triggers dynamic PDCH conversion on the TRX to convert A PDCHs. Here, A = Number of required PDCHs - Number of allocated PDCHs. If the average number of multiplexed MSs on the PDCH in a cell exceeds the value of Uplink Multiplex Threshold of Dynamic Channel Conversion/10, dynamic PDCH conversion is
triggered in the cell until the number is smaller than the value of Uplink Multiplex Threshold of Dynamic Channel Conversion/10. If the average number of multiplexed MSs on the PDCH in a cell exceeds the value of Downlink Multiplex Threshold of Dynamic Channel Conversion/10, dynamic PDCH conversion is triggered in the cell until the number is smaller than the value of Downlink Multiplex Threshold of Dynamic Channel Conversion/10. If the EGPRS-capable MS is allocated the GPRS channel and the convertible EGPRS channels are available in the cell, dynamic PDCH conversion is triggered to convert EGPRS channels as required.
?.2. Preprocessing
The PDCH conversion preprocessing is performed to obtain the information about all the convertible dynamic PDCHs in the cell. This provides a basis for the dynamic PDCH conversion. If the parameter PDCH Reforming is set to No, only the idle channels can be regarded as candidate channels to participate in dynamic PDCH ranking. If the parameter PDCH Reforming is set to Yes, both the dynamic PDCHs occupied by CS services and the idle dynamic PDCHs in the TCH state can be regarded as candidate channels to participate in dynamic PDCH ranking. If the dynamic PDCHs to be converted already carry CS services, the CS services must be switched to other channels in advance.
?.3. Algorithm
The dynamic PDCH conversion algorithm is based on the priority mechanism. All the TRXs with convertible dynamic PDCHs in the cell are granted certain priorities. The dynamic PDCH conversion algorithm determines whether to select a TRX based on the priority of the TRX. Table 2-93 lists the conditions for selecting preferable TRXs in descending order of priorities.
NOTE
The factors have different impacts on dynamic PDCH conversion. They are listed in descending order of impacts.
Table 2-93 Conditions for selecting preferable TRXs PRI 1 Conditions for selecting preferable TRXs Whether the power amplifier of the TRX is powered on Concentric cell attribute of the TRX Description If the power amplifier of the TRX is powered on, the TRX is preferred. If the concentric cell attribute of the TRX is consistent with the required one, the TRX is preferred. If the expansion attribute of the TRX is consistent with the required one, the TRX is preferred.
524
Expansion attribute of the TRX
Issue 08 (2011-09-30)
PRI 4 5
Conditions for selecting preferable TRXs Whether the TRX supports EGPRS Number of convertible dynamic PDCHs on the TRX
Description If the TRX supports EGPRS, the TRX is preferred. If the number of convertible dynamic PDCHs on the TRX meets the conversion requirement, the TRX is preferred. If the number of convertible dynamic PDCHs on the TRX does not meet the conversion requirement, the TRX with more convertible dynamic PDCHs has a higher priority.
6 7 8
Number of PDCHs on the TRX Number of static PDCHs on the TRX Maximum number of consecutive convertible dynamic PDCHs on the TRX Frequency hopping attribute of the TRX Interference level of the TRX Whether the TRX is a BCCH TRX
The TRX with more PDCHs has a higher priority. The TRX with more static PDCHs has a higher priority. The TRX with more consecutive convertible dynamic PDCHs has a higher priority. If the TRX is not involved in frequency hopping, the TRX is preferred. The TRX with less interference has a higher priority. If the TRX is a BCCH TRX, the TRX is preferred.
10 11
The method of selecting a TRX according to the conditions listed in Table 2-93 is as follows: 1. All the TRXs in the cell are filtered according to the condition with the highest priority. l If only one TRX meets the condition after filtering, the TRX is selected as the candidate TRX. Then, go to 3. l If multiple TRXs meet the condition, these TRXs are involved in the next round of filtering, as described in 2. l If no TRX meets the condition, all the TRXs are involved in the next round of filtering, as described in step 2. 2. All the TRXs are filtered according to the condition with the priority one level lower. l If only one TRX meets the condition after filtering, the TRX is selected as the candidate TRX. Then, go to 3.
Issue 08 (2011-09-30)
525
l If multiple TRXs or no TRX meets the condition, the operation in 2 is repeated. After the corresponding TRXs are filtered, go to 3. 3. The BSC selects the dynamic PDCHs for conversion in the sequence of timeslot numbers 6, 5, 7, 4, 3, 2, 1, and 0.
NOTE
If the conversion requires channel groups, the BSC selects multiple timeslots for conversion in the sequence of timeslot numbers 6, 5, 7, 4, 3, 2, 1, and 0.
2.40.3.4 Dynamic PDCH Release Algorithm

?.1. Overview
If a dynamic PDCH remains idle for a period of time, the BSC releases it. The idle time is specified by the parameter Timer of Releasing Idle Dynamic Channel. If the dynamic PDCH is occupied again by the PS service before the timer expires, the parameter Timer of Releasing Idle Dynamic Channel is disabled. After all the TBFs on the dynamic PDCH are released, the parameter Timer of Releasing Idle Dynamic Channel is enabled. The CS service preempts the dynamic PDCH when no speech channels are available for allocation. If HDLC transmission or IP transmission is applied to the Abis interface, the CS service also preempts the dynamic PDCH when no Abis transmission resources are available. When the CS service preempts the dynamic PDCH, the band attribute and concentric cell attribute must be taken into account.
?.2. Algorithm
When the dynamic PDCH is released because the CS service preempts it, the factors listed in Table 2-94 must be taken into account. These factors are listed in descending order of priorities. Table 2-94 Factors related to dynamic PDCH release PRI 1 Factor Frequency band Description If the frequency band of the dynamic PDCH is not the one required by the CS service, the dynamic PDCH cannot be preempted.
Issue 08 (2011-09-30)
526
PRI 2
Factor Concentric cell
Description l If the required concentric cell attribute is only underlaid subcell or only overlaid subcell and the position of the dynamic PDCH in the concentric cell does not meet the preemption requirement, the dynamic PDCH cannot be preempted. l If the required concentric cell attribute is underlaid subcell preferred or overlaid subcell preferred and the position of the dynamic PDCH in the concentric cell meets the preemption requirement, the dynamic PDCH is preempted preferentially.
3 4
Whether the dynamic PDCH is idle Number of multiplexed MSs using the dynamic PDCH as the control channel
If the dynamic PDCH is idle, it is preempted preferentially. If the parameter Level of Preempting Dynamic Channel is set to No preempt of CCHs and at least one MS uses the dynamic PDCH as the control channel, the dynamic PDCH cannot be preempted.
Issue 08 (2011-09-30)
527
PRI 5
Factor Number of multiplexed MSs on the dynamic PDCH
Description l If the parameter Level of Preempting Dynamic Channel is set to No preempt of service TCHF and at least one MS occupies the dynamic PDCH, the dynamic PDCH cannot be preempted. l If the parameter Level of Preempting Dynamic Channel is set to Preempt all dynamic TCHFs, the number of dynamic PDCHs used as control channels has a negative correlation with the priority of dynamic PDCH preemption. l If the parameter Level of Preempting Dynamic Channel is set to Preempt all dynamic TCHFs or No preempt of CCHs, the number of multiplexed MSs on the dynamic PDCH has a negative correlation with the priority of dynamic PDCH preemption.
Number of static PDCHs configured on the TRX of the dynamic PDCH
The number of static PDCHs configured on the TRX of the dynamic PDCH has a negative correlation with the priority of dynamic PDCH preemption. The number of PDCHs on the TRX of the dynamic PDCH has a negative correlation with the priority of dynamic PDCH preemption. The BSC releases the GPRS channel, EGPRS normal channel, and EGPRS priority channel in descending order of priorities. The BSC releases the dynamic PDCHs in the sequence of timeslot numbers 0, 1, 2, 3, 4, 7, 5, and 6.
Number of PDCHs on the TRX of the dynamic PDCH
PDCH channel priority type of the dynamic PDCH
Timeslot number of the dynamic PDCH
Issue 08 (2011-09-30)
528
The method of selecting occupied dynamic PDCHs according to the conditions listed in Table 2-94 is as follows: 1. All the occupied dynamic PDCHs in the cell are filtered according to the condition with the highest priority. l If only one occupied dynamic PDCH meets the condition after filtering, the occupied dynamic PDCH is selected as the candidate PDCH. l If multiple occupied dynamic PDCHs meet the condition, these PDCHs are involved in the next round of filtering, as described in 2. l If no occupied dynamic PDCH meets the condition, all the occupied dynamic PDCHs are involved in the next round of filtering, as described in 2. 2. All the occupied dynamic PDCHs are filtered according to the condition with the priority one level lower. l If only one occupied dynamic PDCH meets the condition after filtering, the occupied dynamic PDCH is selected as the candidate PDCH. l If multiple occupied dynamic PDCHs meet the condition, the operation in 2 is repeated until the corresponding occupied dynamic PDCH is selected or the selection fails.

Cell
The maximum number of PDCHs in a cell is restricted by the setting of Maximum Rate Threshold of PDCHs in a Cell. Maximum number of PDCHs in a cell = (Number of static PDCHs + Number of dynamic PDCHs) x Maximum Ratio Threshold of PDCHs in a Cell If the parameter Level of Preempting Dynamic Channel is set to No preempt of CCHs or No preempt of service TCHF, the BSC does not perform dynamic PDCH conversion to reserve idle channel resources for the CS service, thus reducing the impact on the CS service. The number of reserved idle channels is determined by Reservation Threshold of Dynamic Channel Conversion.
TRX
If a TRX is configured with several static PDCHs, it is recommended that the static PDCHs be configured in the sequence of timeslot numbers 6, 5, 7, 4, 3, 2, 1, and 0. This ensures the continuity of timeslots occupied by PDCHs. The setting of PDCH Channel Priority Type should be the same for all the PDCHs on a TRX. If the GPRS and EGPRS services need to be isolated on a TRX, it is recommended that the EGPRS special channel, EGPRS priority channel, EGPRS normal channel, and GPRS channel be configured in the sequence of timeslot numbers 6, 5, 7, 4, 3, 2, 1, and 0. The maximum number of PDCHs on a TRX is determined by Maximum Number of PDCH.
Multiband Network
In a multiband cell, it is recommended that the static PDCH be configured in the BCCH band and the bands compatible with the BCCH.
Concentric Cell
If the parameter Dynamic Channel Conversion Parameter of Concentric Cell is set to Only convert dynamic channel at UL or UL first and convert allowed, it is recommended that the static PDCH be configured in the underlaid subcell. If the parameter Dynamic Channel Conversion Parameter of Concentric Cell is set to Only convert dynamic channel at OL or OL first and convert allowed, it is recommended that the static PDCH be configured in the overlaid subcell. If the BCCH is configured on the TRX in the underlaid subcell, it is recommended that the parameter Dynamic Channel Conversion Parameter of Concentric Cell be set to Only convert dynamic channel at UL. If the BCCH is configured on the TRX in the overlaid subcell, it is recommended that the parameter Dynamic Channel Conversion Parameter of Concentric Cell be set to Only convert dynamic channel at OL.
2.40.5 Parameters
The following describes the parameters related to GPRS/EGPRS channel managementl. For the meaning of each parameter, see Table 2-95. For the default value, value range, and related MML commands of each parameter, see Table 2-96. Table 2-95 Parameter description (1) Parameter Description EGPRS priority type of the channel If this parameter is set to GPRS, the EDGE MSs cannot use this channel. If this parameter is set to EGPRSNORCH, the GPRS and EDGE MSs can use this channel at the same priority. If this parameter is set to EGPRSPRICH, the EDGE MSs have the priority to use this channel. If this parameter is set to EGPRSSPECH, only the EDGE MSs can use this channel. If this parameter is set to NONGPRS, this parameter becomes invalid. Channel type of the timeslot on the TRX. The channel type of timeslot 0 must not be set, because the combined BCCH is configured by default. The channel type of other timeslots can be set to full-rate TCH or half-rate TCH. PDCH uplink multiplex threshold, indicating the maximum TBFs on the uplink PDCH (parameter value/10). We recommand that the value of "Uplink Multiplex Threshold of Dynamic Channel Conversion" should be less than "PDCH Uplink Multiplex Threshold" for triggering converting dynamic channel in time and reducing PDCH multiplex.
PDCH Channel Priority Type
Channel Type
PDCH Uplink Multiplex Threshold
Issue 08 (2011-09-30)
530
Parameter
Description PDCH downlink multiplex threshold, Indicating the maximum TBFs on the downlink PDCH (parameter value/ 10).We recommand that the value of "Downlink Multiplex Threshold of Dynamic Channel Conversion" should be less than "PDCH Downlink Multiplex Threshold" for triggering converting dynamic channel in time and reducing PDCH multiplex. Switch specifying whether to allow the downlink EGPRS TBF and the uplink GPRS TBF to share the same channel. On: allow the downlink EGPRS TBF and the uplink GPRS TBF to share the same channel; Off: prohibit the downlink EGPRS TBF and the uplink GPRS TBF sharing the same channel. Whether to support EDA. Extended dynamic allocation (EDA) enables the MS to be allocated with more timeslots on the uplink, thus improving the uplink rate and helping to transmit large amounts of data on the uplink. Whether to support the high multislot class. High multislot class function enables a single MS to be allocated with a maximum of five timeslots on the uplink or downlink, thus improving the uplink or downlink throughput of a single MS. The BSS supports the MS with high multislot classes from 30 to 34. A maximum of five timeslots on the downlink can be assigned to an MS. If an MS is of the high multislot class 34, a maximum of five timeslots on the uplink can be allocated to the MS. Thus, the uplink and downlink throughput is increased by 25%.The total number of timeslots on the uplink and downlink cannot exceed six. That is, if five timeslots on the downlink are allocated to the MS, then only one timeslot on the uplink can be allocated to the MS. Uplink multiplex threshold of dynamic channel conversion. When the subscriber number on the channel reaches the value (threshold/10), the dynamic channel conversion application is triggered. We recommand that the value of "Uplink Multiplex Threshold of Dynamic Channel Conversion" should be less than "PDCH Uplink Multiplex Threshold" for triggering converting dynamic channel in time and reducing PDCH multiplex. Downlink multiplex threshold of dynamic channel conversion. When the subscriber number on the channel reaches the value (threshold/10), the dynamic channel conversion is triggered. We recommand that the value of "Downlink Multiplex Threshold of Dynamic Channel Conversion" should be less than "PDCH Downlink Multiplex Threshold" for triggering converting dynamic channel in time and reducing PDCH multiplex.
PDCH Downlink Multiplex Threshold
Support EDA
Support High Multislot Class
Uplink Multiplex Threshold of Dynamic Channel Conversion
Downlink Multiplex Threshold of Dynamic Channel Conversion
Issue 08 (2011-09-30)
531
Parameter
Description This parameter must be used together with "Level of Preempting Dynamic Channel" in the following conditions: 1. When "Level of Preempting Dynamic Channel" is set to "No preempt of service TCHF" and "PDCH Reforming" is set to "Yes", the channels for the CS service is released if the CS service fails to be switched to another channel. 2: When "Level of Preempting Dynamic Channel" is set to "Preempt all dynamic TCHFs" or "No preempt of CCHs" and "PDCH Reforming" is set to "Yes", the CS service is switched to the original channel if the CS service fails to be switched to another channel. Time to wait for releasing the dynamic channel after the TBF on the dynamic channel is released. When all the TBFs on the channel are released, the dynamic channel is not released at once. Instead, the timer is started when the channels are idle. Before the timer expires, if new service request is received, the dynamic channel is still occupied and timer is stopped; otherwise, the dynamic channel is released after the timer expired. Mode of preempting the dynamic channel for the CS domain and PS domain. Only the channel configured in the TCH/F mode can be preempted. "Preempt all dynamic TCHFs" indicates the circuit domain can preempt all the dynamic channels. "No preempt of CCHs" indicates the circuit domain can preempt all the dynamic channels except the CCHs. "No preempt of service TCHF" indicates the circuit domain cannot preempt all the dynamic channels of bearer services. Maximum value of the PDCH ratio in a cell. The number of available TCHs and PDCHs in a cell is set to a fixed value. The PDCH ratio is: Number of available PDCHs/(Number of available TCHFs + Number of available static PDCHs). This parameter is used to restrict the PDCH ratio. Maximum number of PDCHs that can be assigned in the TRX Conversion policy of the dynamic channel of the concentric cell
PDCH Reforming
Timer of Releasing Idle Dynamic Channel
Level of Preempting Dynamic Channel
Maximum Rate Threshold of PDCHs in a Cell Maximum Number of PDCH Dynamic Channel Conversion Parameter of Concentric Cell
Issue 08 (2011-09-30)
532
Table 2-96 Parameter description (2) Paramete r Default Value GUI Value Range GPRS (GPRS Channel), EGPRSN ORCH (EGPRS Normal Channel), EGPRSPR ICH (EGPRS Priority Channel), EGPRSSP ECH (EGPRS Special Channel), NONGPR S(NonGPRS Channel) FULLTC H (FULLTC H), HALFTC H (HALFTC H) Actual Value Range Unit MML Comman d Impact
NONGPR S
GPRS, EGPRSN ORCH, EGPRSPR ICH, EGPRSSP ECH, NONGPR S
None
SET GTRXCH AN (Optional)
Physical channel
Channel Type PDCH Uplink Multiplex Threshold PDCH Downlink Multiplex Threshold Allow E Down G Up Switch
None
FULLTC H, HALFTC H
None
SET BTSCHN FALLBA CK (Mandator y) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET BSCPSSO FTPARA (Optional)
BTS
70
10~70
10~70
None
Cell
80
10~160 OPEN (Open), CLOSE (Close)
10~160
None
Cell
OPEN
OPEN, CLOSE
None
BSC
Issue 08 (2011-09-30)
533
Paramete r
Default Value
GUI Value Range NOTSUP PORT (Not Support), SUPPOR T (Support) NOTSUP PORT (Not Support), SUPPOR T (Support)
Actual Value Range
Unit
MML Comman d
Impact
Support EDA
NOTSUP PORT
NOTSUP PORT, SUPPOR T
None
BSC
Support High Multislot Class Uplink Multiplex Threshold of Dynamic Channel Conversio n Downlink Multiplex Threshold of Dynamic Channel Conversio n
NOTSUP PORT
None
BSC
20
10~70
10~70
None
Cell
20
10~80 NO(NO), YES (YES)
10~80
None
SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional)
Cell
PDCH Reforming Timer of Releasing Idle Dynamic Channel
NO
NO, YES
None
Cell
20
10~3600
10~3600
Cell
Issue 08 (2011-09-30)
534
Paramete r
Default Value
GUI Value Range LEVEL0 (Preempt all dynamic TCHFs), LEVEL1 (No preempt of CCHs), LEVEL2 (No preempt of service TCHF)
Actual Value Range
Unit
MML Comman d
Impact
Level of Preemptin g Dynamic Channel Maximum Rate Threshold of PDCHs in a Cell Maximum Number of PDCH
LEVEL0
LEVEL0, LEVEL1, LEVEL2
None
SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GTRXBA SE (Optional)
Cell
30
0~100
0~100
per cent
Cell
0~8 CONVER T0(Only convert at UL), CONVER T1(Only convert at OL), CONVER T2(UL first and convert allowed), CONVER T3(OL first and convert allowed)
0~8
None
TRX
Dynamic Channel Conversio n Parameter of Concentri c Cell
CONVER T0
CONVER T0, CONVER T1, CONVER T2, CONVER T3
None
Cell
2.40.6 Counters
2.40.7 Glossary

l l l l l l l l l l 3GPP TS 44.060 "Mobile Station (MS) - Base Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol" 3GPP TS 44.018 "Base Station System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)" 3GPP TS 45.002 "Radio Access Network; Multiplexing and multiple access on the radio path" 3GPP TS 24.008, 3GPP TS 48.018, and 3GPP TS 48.016 peer layer protocols between the BSS and the SGSN BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.41 GPRS/EGPRS Connection Control and Transfer

2.41.1 Introduction
2.41.1.1 Scope
This document describes the establishment of uplink and downlink temporary block flows (TBFs), enhancement of the extended uplink TBF function, release of a TBF, uplink and downlink data transmission, TBF reassignment, and suspension and resumption of general packet radio service (GPRS)/Enhanced GPRS (EGPRS).

Issue 08 (2011-09-30)

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the GPRS/EGPRS connection control and transfer feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Version
02 (2009-09-30)
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description The following contents are added: 2.41.3.2.1 Early TBF Establishment and 2.41.3.2.2 Sending Dummy Control Block. None. Parameter Change parameter Not Send Dummy Message with Extended Uplink TBF is added.
Editorial change
None.
Issue 08 (2011-09-30)
537
2.41.2 Overview
GPRS/EGPRS connection control indicates the establishment and release of TBFs. GPRS/ EGPRS transfer indicates the transfer of data on TBFs. The purposes of GPRS/EGPRS connection control and transfer are as follows: l l l Optimizes TBF establishment and release procedures to provide the best possible data throughput for subscribers. Provides efficient flow control and scheduling to ensure the data throughput used by subscribers. Reduces the MS access time using the following methods: uplink immediate assignment, takeover of the uplink assignment by the BTS, dynamic adjustment of transmission interval of the relative reserved block period (RRBP) field, delayed release of uplink and downlink TBFs, and extended uplink TBFs.
The connection control part and the transfer part are involved in handling a TBF. The connection control part involves the following functions: l l l l l Establishment of an uplink or downlink TBF Release of an uplink or downlink TBF Data transmission Reassignment of a TBF TBF suspension and resumption
The transfer part involves the following functions: l Scheduling and reception of radio link control (RLC) data blocks, which are assembled intological link control (LLC) packet data units (PDUs), and transmitted to the serving GPRS support node (SGSN) Reception of LLC PDUs from the SGSN and disassembly of LLC PDUs into RLC data blocks Scheduling and transmission of RLC/media access control (MAC) control blocks containing signaling information Downlink flow control
l l l
Establishing different types of TBFs depends on: l l Whether the connection is on the uplink or downlink Whether the channel that controls signaling is packet common control channel (PCCCH), common control channel (CCCH), or PACCH
The PCCCH is packet broadcast control channel (PBCCH) is available in a cell. If no PBCCH is available, the CCCH is used. The PACCH is used only when an uplink or downlink TBF already exists. TBF establishment is classified into uplink TBF establishment and downlink TBF establishment. According to the channel types and access phases, TBF establishment is further classified into: l l l
Issue 08 (2011-09-30)
Establishment of an uplink or downlink TBF on the CCCH Establishment of an uplink or downlink TBF on the PCCCH Establishment of an uplink or downlink TBF on the PACCH

2.41.3.1 Establishment of an Uplink TBF
Before transmitting data, an MS initiates a packet channel request. A packet channel request has the following two access types: one-phase access and two-phase access. l One-phase access: Upon receiving a channel request with the one-phase access type, the BSC allocates radio resources to an MS. The radio resources including temporary flow identity (TFI) and uplink state flag (USF). Two-phase access request, The procedure for a channel request with the two-phase access type is as follows: 1. 2. The BSC allocates only one RLC/MAC block to an MS. The MS transmits a Packet Resource Request message on the assigned radio block. The BSC allocates radio resources (such as TFI and USF) to the MS. The MS starts to transmit data on the assigned radio resources.
The Packet Channel Request message is an 8-bit or 11-bit access burst, and carries only a small amount of information. The Packet Resource Request message, however, is an RLC/MAC signaling packet based on the CS-1 coding scheme. Therefore, it carries more information, including the temporary logical link identifier (TLLI) , multislot capability of an MS, and radio priority.
?.1. Establishment of an Uplink TBF on the CCCH
One-Phase Packet Access on the Uplink CCCH

The procedure for establishing of an uplink TBF using one-phase packet access mode is as follows: 1. 2. If a PCCCH is not configured for a cell, the MS in packet idle mode sends a Channel Request message to the BSC on random access channel (RACH). After receiving the message from the MS, the BSC starts to establish a TBF and notifies whether the MS access request is allowed or rejected. If the access request is allowed, the BSC sends an Immediate Assignment message to the MS on the access grant channel (AGCH). The message contains the USF and TFI of the TBF. It also indicates that one uplink packet channel is allocated for the uplink data transfer. The MS sends the first uplink RLC data block tcontaining the TLLI of the MS to the BSC on the assigned uplink packet channel. After receiving the data block, the BSC responds with a Packet Uplink Ack/Nack(with TLLI) message to complete the contention resolution procedure. The uplink TBF establishment is complete. The BSC responds with a Packet Uplink Ack/Nack(without TLLI) message to acknowledge the reception of the uplink RLC data block.
3.
4.
Figure 2-108 shows the procedure of one-phase packet access on the uplink CCCH.
Issue 08 (2011-09-30)
539
Figure 2-108 One-phase packet access on the uplink CCCH
In the preceding procedure, The Move Immediate Assignment Down to BTS parameter can be set to Support so that the packet uplink immediate assignment function is taken over by the BTS. In this manner, the Immediate Assignment message is sent in advance and the MS access delay is reduced. Currently, the takeover of the packet uplink immediate assignment by the BTS is only available for one-phase access. The procedure for establishing an uplink TBF after the packet uplink immediate assignment function is taken over the BTS is as follows: 1. The BSC sends a Preallocation Uplink TBF Resource Request message to request the BTS to allocate the required resources in advance. Then, the BTS responds with a Preallocation Uplink TBF Resource Acknowledgement message. After receiving a channel request from an MS, the BTS sends an Immediate Assignment message to the MS on the AGCH and schedules uplink data blocks using the preemption mechanism. After receiving the Immediate Assignment message, the MS starts to send data blocks to the BSC. After receiving a Channel Request(assist) message from the BTS, the BSC initiates the procedure for the establishment of an uplink TBF. The BSC and sends an Immediate Assignment(assist) message to the BTS. The establishment of an uplink TBF is complete. Figure 2-109 shows the procedure for establishing an uplink TBF after the packet uplink immediate assignment function is taken over by the BTS.
2.
3.
Issue 08 (2011-09-30)
540
Figure 2-109 Takeover of the packet immediate assignment by the BTS
Both GPRS and EGPRS support one-phase access and two-phase access. One-phase access and the first phase of two-phase access can be 8-bit or 11-bit access. The procedure for 11-bit onephase access on the CCCH is the same as that for 8-bit one-phase access on the CCCH. The access speeds are similar. The difference lies in that the MS multislot capability can be carried in the procedure for 11-bit one-phase access on the CCCH. Generally, an EGPRS-capable MS has the multislot capability. If an EGPRS-capable MS uses one-phase access, it informs the network of its multislot capability during 11-bit one-phase access; if an EGPRS-capable MS uses two-phase access, it informs the network of its multislot capability through a packet resource request, which causes a long access delay. Therefore, set Support 11BIT EGPRS Access to Yes. to ensure that an EGPRS-capable MS can use one-phase access. In comparison with twophase access, the access time of one-phase access can be reduced by 300 ms.
Two-Phase Packet Access on the Uplink CCCH

Two-phase access involves two phases: single radio block access in the first phase and packet access in the second phase. The single radio block access in the second phase allocates a PACCH to an MS for the transmission of the Packet Resource Request(with TLLI) message. The packet access in the second phase allocates packet channels for data transmission. The procedure for the TBF establishment in two-phase access on the uplink CCCH is as follows: 1. 2. If a PCCCH is not configured for a cell, the MS sends a single radio block packet channel request on the RACH to the BTS. Then, the BTS forwards the request to the BSC. The BSC sends a packet uplink immediate assignment message to the MS on the AGCH through the BTS to allocate a single uplink radio block. The BSC does not establish uplink TBFs. The MS sends a Packet Resource Request message on the assigned uplink radio block on the PACCH to the BSC. This message carries the TLLI, access type, and MS routing area code RAC of the MS. based on the MS RAC, the BSC allocates a packet channel to the MS and establishes an uplink TBF. The BSC sends a Packet Uplink Assignment(with TLLI) message containing the TLLI on the same PACCH to complete the contention resolution procedure. This message indicates that an uplink packet channel is allocated for uplink data transmission and contains the USF and TFI of the TBF.
3.
4.
Issue 08 (2011-09-30)
5. 6.
The MS sends uplink data without TLLI on the assigned channel. The establishment of an uplink TBF is complete. The subsequent procedure for two-phase access on the uplink CCCH is the same as that for one-phase access on the uplink CCCH.
Figure 2-110 shows the procedure for two-phase packet access on the uplink CCCH. Figure 2-110 Two-phase packet access on the uplink CCCH
?.2. Establishment of an Uplink TBF on the PCCCH

If a PCCCH is configured for a cell, an MS in packet idle mode initiates an 8-bit/11-bit onephase or two-phase access request on the PRACH If the BSC allows the access, it allocates a packet channel to the MS for the uplink data transmission.
One-Phase Packet Access on the PCCCH

The basic procedure for one-phase packet access on the PCCCH is mostly the same as that for one-phase packet access on the uplink CCCH. The differences of these procedures are as follows: 1. 2. The channel request is initiated over the packet random access channel (PRACH). Uplink assignment instead of immediate assignment is initiated over the packet access grant channel (PAGCH).
Two-Phase Packet Access on the PCCCH

The basic procedure for two-phase packet access on the PCCCH is mostly the same as that for two-phase packet access on the uplink CCCH. The differences of these procedures are as follows: 1. 2. The channel request is initiated over the PRACH. Uplink assignment instead of immediate assignment is initiated over the PAGCH.
?.3. Establishment of an Uplink TBF on the PACCH

The procedure for the establishment of an uplink TBF on the PACCH is as follows: 1. The MS is in packet transfer mode and there is a downlink TBF. If the BSC sets S/P to 1, the MS is requested to send a Packet Downlink Ack/Nack message in the reserved uplink
Issue 08 (2011-09-30)
block to acknowledge the reception of downlink data. The S/P field indicates whether the RRBP field is valid. If the S/P field is set to 1 in the header of a downlink data block, the MS is requested to acknowledge the response. If the S/P field is set to 0, the RRBP field is invalid.The RRBP field indicates the number of Time Division Multiple Access (TDMA) frames the MS needs to wait for before sending uplink RLC data blocks. 2. 3. If the MS has uplink data to transmit, the MS sends a Packet Downlink Ack/Nack(with Channel Request Description) message to the BSC on the PACCH. After receiving the message (the downlink TBF is now in packet transfer mode), the BSC starts the uplink TBF establishment procedure on the downlink. The BSC sends a packet uplink assignment message to the MS on the PACCH, establishes an uplink TBF, and allocates a packet channel to the MS. Contention resolution is not required during the establishment of an uplink TBF on the downlink. The MS sends uplink data blocks without TLLI on the allocated channel. The establishment of an uplink TBF is complete.
4.
Figure 2-111 shows the uplink TBF establishment on the downlink. Figure 2-111 Establishment of an uplink TBF on the downlink
In the preceding procedure, the Move Packet Assignment Down to BTS parameter can be set to Support so that the packet assignment function is taken over by the BTS. In this manner, the packet assignment message is sent by the BTS and the MS access delay is reduced by 100 ms. This improves the subscriber experience and increase the operatorsrevenue. 1. When the previous uplink TBF is to be released (extended uplink TBF not supported), if the BSC sends a Packet Uplink ACK/NACK(FAI=1) message first. The BSC detects that the downlink TBF is in packet transfer mode, the BSC reserves the uplink TBF and preallocates this uplink TBF to the BTS. After receiving a Packet Control ACK message from the MS, the BSC starts the uplink TBF release procedure. The BTS receives a Packet Downlink Ack/Nack(with Channel Request Description) message from the MS. Then, the BTS directly allocates the packet channel by the BSC to the MS and schedules radio resource. After the BTS sends an uplink assignment message to the MS. the MS can upload data blocks. The takeover of packet assignment by the BTS is complete. At the same time, the BTS sends the Packet Downlink Ack/Nack(with Channel Request Description) message to the BSC.
2. 3.
Issue 08 (2011-09-30)
4. 5.
After receiving the message, the BSC starts the uplink TBF establishment on the downlink. The BSC sends a Packet Uplink Assignment message to the MS on the PACCH. The BTS transparently transmits the downlink messages on the PDCH. Therefore, the MS receives the Packet Uplink Assignment message twice. Then, the BSC instead of the BTS takes charge of scheduling uplink data blocks.
Figure 2-112 shows the procedure for uplink TBF establishment on the downlink after the packet uplink assignment function is taken over by the BTS. Figure 2-112 Takeover of packet uplink assignment by the BTS
?.4. Dynamic Adjustment for Transmission Interval of the RRBP Field

Dynamic adjustment for transmission interval of the RRBP field controls that the BSC transmits downlink data with the RRBP field at different intervals depending on whether an uplink TBF exists and whether the downlink TBF release is delayed at an early stage or at a late stage. This accelerates the an uplink TBF establishment on the downlink. l l If an uplink TBF exists or if the downlink TBF release is delayed at a late stage, the BSC transmits the RRBP field at a long interval to save the uplink bandwidth. If an uplink TBF does not exist or if the downlink TBF release is delayed at an early stage, the BSC transmits the RRBP field at a short interval to accelerate the uplink access speed for the MS.
Uplink TBF Existence and RRBP Transmission Interval

During downlink transmission, the BSC periodically sends downlink data blocks with the RRBP field to the MS. The MS responds with a Packet Downlink Ack/Nack message to acknowledge the reception of downlink data. When the MS has uplink data to transmit, it adds a Channel Request information element to the Packet Downlink Ack/Nack message to initiate access. Therefore, if the interval of transmitting the RRBP field is shortened, the MS access speed is increased.
The Packet Downlink Ack/Nack message occupies the uplink bandwidth. If an uplink TBF already exists, increasing the interval of transmitting the RRBP field can reduce the uplink overhead and increase the uplink bandwidth.
Delayed Downlink TBF Release and RRBP Transmission Interval

After transmitting the last downlink RLC data block, the BSC acknowledges the reception of all the previously transmitted downlink data blocks. After the acknowledgment, the BSC does not instruct the MS to release the downlink TBF because the BSC considers that the MS does not receive the last data block. Then, the BSC periodically retransmits the last downlink RLC data block with the RRBP field. After receiving the last downlink RLC data block, the MS responds with a Packet Downlink Ack/Nack message in the related uplink RLC radio block for the RRBP field to maintain the downlink TBF. The downlink TBF release delay is specified by the Release Delay of Downlink TBF parameter. Therefore, when the MS has uplink data to transmit, it immediately sends the BSC a Packet Downlink Ack/Nack message with the Channel Request Description information element. In addition, during delayed downlink TBF release, the disassembled downlink RLC data blocks are directly transmitted in the downlink TBF of which the release is delayed. After downlink data transmission is complete, the MS generally has uplink data to transmit at the early stage of the delayed downlink TBF release. In this case, the transmission interval of the RRBP field should needs to be short. At the late stage of the delayed downlink TBF release, there may not be uplink data for transmission. In this case, the transmission interval of the RRBP field needs to be long.
2.41.3.2 Enhancement of Extended Uplink TBF Function

?.1. Early TBF Establishment
Early TBF establishment described in 3GPP TS 44.060 (Release 7) is an enhanced function of the extended uplink TBF. If the MS supports early TBF establishment, TBFs can be allocated before the MS transmits the actual data, thereby reducing the service access delay. In the two-phase access procedure, the MS sets the EARLY_TBF_ESTABLISHMENT field in the PACKET RESOURCE REQUEST message to notify the BSC of TBF pre-allocation for the MS. After the BSC establishes the TBF, the TBF is not released even if the BSC does not receive any data block from the MS within a specified time. In this case, if the MS has data to transmit later, it can directly send data on that TBF without initiating the TBF establishment procedure. Therefore, the service access delay is reduced. If an uplink TBF needs to be established during downlink packet transmission, the MS sets the EARLY_TBF_ESTABLISHMENT field in the PACKET DOWNLINK ACK/NACK or EGPRS PACKETDOWNLINK ACK/NACK message to notify the BSC of the early TBF establishment. After the TBF is established, the procedure is same as that described above.
?.2. Sending Dummy Control Block

Controlling the sending of the dummy control block that is described in 3GPP TS 44.060 (Release 6) is an enhanced function of extended uplink TBF. This function enables the BSC to notify using system information messages the MS of whether to send the dummy control block when the MS has no other block to transmit in extended TBF mode. If the MS does not send the
dummy control block when it has no other block to transmit to the network in extended TBF mode, the message flow on the Um interface is decreased, this improves the MS and BSC performance and reducs the MS power consumption. The BSC sends a system information message such as PSI1, PSI13, or SI13 with the EXT_UTBF_NODATA parameter to instruct the MS whether to send the PACKET UPLINK DUMMY CONTROL BLOCK message. The value of the EXT_UTBF_NODATA parameter contained in the system information message is dependent on the setting of the cell parameter Not Send Dummy Message with Extended Uplink TBF. If Not Send Dummy Message with Extended Uplink TBF is set to SEND, the MS sends the PACKET UPLINK DUMMY CONTROL BLOCK message to the BSC when it has no other block to transmit. If Not Send Dummy Message with Extended Uplink TBF is set to NOTSEND, the MS does not send the PACKET UPLINK DUMMY CONTROL BLOCK message to the BSC when it has no other block to transmit.
2.41.3.3 Establishment of a Downlink TBF

According to the type of channel for transmitting control signaling, the establishment of a downlink TBF is classified into the establishment of a downlink TBF on the CCCH, PCCCH, and PACCH.
?.1. Establishment of a Downlink TBF on the CCCH

If a PCCCH is not configured for a cell, the BSC needs to establish a downlink TBF for data transmission when it receives a downlink LLC PDU without a downlink TBF from the SGSN. If the MS is in idle mode, the BSC sends a downlink assignment message to the MS on the CCCH. The procedure for the establishment of a downlink TBF on the CCCH is as follows: 1. After receiving a downlink LLC PDU from the SGSN, the BSC inserts the downlink LLC PDU in the LLC PDU queue. The BSC sends the MS an Immediate Assignment message containing the TFI and the TBF start time on the CCCH to allocate a channel to the MS. When the downlink TBF starts, the BSC sends the MS a Packet Polling Request message with TFI on the related PACCH for the downlink TBF if the BSC does not have the timing advance (TA). After receiving this message, the MS responds with a packet control acknowledgement message. Then, the BSC obtains the TA from the packet control acknowledgement message and informs the MS of the TA by sending a Packet Power Control/Timing Advance message. If the channel (indicated in the immediate assignment message) allocated to the MS does not meet the MS multislot capability, the BSC initiates the reassignment of a downlink TBF and sends a packet downlink assignment message to allocate several channels to a TBF. The downlink TBF is successfully established. The BSC starts to send data blocks. The BSC disassembles downlink LLC PDUs into downlink RLC data blocks and sends the data blocks to the MS on the allocated downlink packet channel. The BSC sets S/P to 1 in the downlink RLC data block header. The MS sends a Packet Downlink Ack/Nack message in response to the received downlink RLC data blocks.
2.
3.
4.
Figure 2-113 shows the procedure for the establishment of a downlink TBF on the CCCH.
Issue 08 (2011-09-30)
546
Figure 2-113 Establishment of a downlink TBF on the CCCH
?.2. Establishment of a Downlink TBF on the PCCCH

The procedure for the establishment of a downlink TBF on the PCCCH is similar to that only difference of these procedures is that: the downlink assignment message is sent over the PCCCH for establishment of a downlink TBF on the PCCCH.
?.3. Establishment of a Downlink TBF on the PACCH

During uplink TBF transmission, the MS listens to the PDCH. If certain downlink data needs to be transmitted, the MS sends a Packet Downlink Assignment message on the PACCH. This procedure is referred to as the establishment of a downlink TBF on the uplink. If a downlink TBF is released but the T3192 timer (timer duration specified by the T3192 parameter) does not expire, the MS listens to the PDCH. If certain downlink data needs to be transmitted, the MS sends a downlink assignment message on the PACCH. This procedure is referred to as the establishment of a downlink TBF on the downlink.
Establishment of a Downlink TBF on the Uplink

The procedure for the establishment of a downlink TBF on the uplink is as follows: After receiving a downlink LLC PDU from the SGSN during uplink TBF transmission. the BSC sends the MS a Packet Downlink Assignment(Uplink TFI, S/P = 1) message on the PACCH. The downlink TBF is established. The BSC starts to send RLC data blocks. Figure 2-114 shows the procedure for the establishment of a downlink TBF on the uplink.
Issue 08 (2011-09-30)
547
Figure 2-114 Establishment of a downlink TBF on the uplink
Establishment of a Downlink TBF on the Downlink

The procedure for the establishment of a downlink TBF on the downlink is as follows: 1. During downlink TBF transmission, the BSC sends the MS all the data blocks in the LLC PDU queue. In the last data block, the BSC sets both the final block indicator (FBI) and the S/P to 1. The MS responds with a Packet Downlink Ack/Nack(FAI=1) message. Then, the BSC sets the timer T3192. l If the PBCCH is not configured for a cell, the BSC informs the MS of the value of T3192 using SI13 and PSI13. l If the PBCCH is configured for a cell, the BSC informs the MS of the value of T3192 using PSI1 and PSI13. The MS starts the timer T3192 and the BSC automatically starts the timer T3193. The duration of the timer T3193 is a little shorter than that of the timer T3192. 3. If the previous downlink TBF on the BSC side is released but the BSC receives a downlink LLC PDU from the SGSN before the timer T3193 expires, the BSC directly sends a Packet Downlink Assignment(with Downlink TFI, S/P=1) message on the PACCH carrying the previous downlink TBF. If the previous downlink TBF on the MS side is not released, the MS directly uses this TBF to transmit data after receiving a Packet Downlink Assignment message. A downlink TBF is established. Then, the BSC sends RLC data blocks to the MS and stops the timer T3193.
2.
Figure 2-115 shows the procedure for the establishment of a downlink TBF on the downlink.
Issue 08 (2011-09-30)
548
Figure 2-115 Establishment of a downlink TBF on the downlink
2.41.3.4 Release of a TBF

The TBF release causes are as follows: l l l l No data needs to be transmitted on the uplink or downlink. The timer for delayed uplink TBF release or the timer for delayed downlink TBF release expires. The MS performs a cell reselection to another cell. The cell does not support GPRS/EGPRS any longer. The cell is reinitialized.
The TBF release is classified into uplink TBF release and downlink TBF release. The uplink TBF release supports: non-extended uplink TBF mode and extended uplink TBF mode. l Non-extended uplink TBF mode: When the protocol version supported by an MS is R99 or an earlier version, the MS controls the release of an uplink TBF in either of the following situations: The MS does not carry the radio access capability. The MS carries the radio access capability but the radio access capability is unknown in the BSC. Extended uplink TBF mode: When the protocol version supported by the MS is R4 or a later version, the BSC controls the release of an uplink TBF if the MS carries the radio access capability and the radio access capability is known in the BSC.
?.1. Release of a Non-Extended Uplink TBF

1. 2. The release of a non-extended uplink TBF is initiated by the MS. During uplink TBF transmission, the MS sets count down value (CV) to 0 in the last uplink data block. If the BSC receives all the uplink data blocks, it sends the MS a Packet Uplink Ack/Nack (FAI=1, S/P=1) message. If the BSC receives certain uplink data blocks, it sends the MS
Issue 08 (2011-09-30)
a Packet Uplink Ack/Nack(FAI=0) message, instructing the MS to retransmit the data blocks that are not received. 3. If the MS receives the Packet Uplink Ack/Nack(FAI=1, S/P=1) message, it responds with a Packet Control Ack message. Then, the uplink TBF is properly released.
Figure 2-116 shows the procedure for the release of a non-extended uplink TBF. Figure 2-116 Release of a non-extended uplink TBF
A monitoring mechanism is required to ensure that uplink TBFs on the BSC side can be released if the Packet Control Ack message is lost. 1. After receiving all the RLC data blocks correctly, the BSC sends the MS a Packet Uplink Ack/Nack(FAI=1, S/P=1) message. At the same time, the BSC starts the counter N3103. The maximum value of this counter is specified by Maximum Value of N3103. After receiving a Packet Control Ack message from the MS, the BSC resets the counter N3103 to zero. If the BSC does receive a correct Packet Control Ack message in the related uplink data block, the counter N3103 is incremented by one. If the counter N3103 exceeds its maximum value, the BSC automatically starts the internal timer T3169. After the timer T3169 expires, a TBF is released. Then, the related resources can be reused.
2. 3. 4.
If the MS does not support an extended uplink TBF, the BSC sends the MS a Packet Uplink Ack/Nack message with FAI = 1 after receiving the last uplink RLC data block (CV = 0), instructing the MS to release this uplink TBF. The non-extended uplink TBF is delayed for a period of time before being released. The release delay is specified by Release Delay of Nonextended Uplink TBF. If the BSC needs to establish a downlink TBF during the delay period, the downlink TBF can be established on the uplink TBF that is not released. Therefore, the downlink TBF establishment time is reduced. After the downlink TBF is successfully established, this uplink TBF is automatically released. If the BSC does not need to establish a downlink TBF during the delay period, the MS releases this uplink TBF after the delay period elapses.
?.2. Release of an Extended Uplink TBF

The release of an extended uplink TBF refers to that the BSC instead of the MS controls the release of an uplink TBFC. The transmission of an extended uplink TBF involves two phases: active period and inactive period. When the MS has no data for transmission, the TBF enters the inactive period. When the MS has data for transmission, the TBF enters the active period. After transmitting the uplink data, the MS retains the uplink TBF for a period of time. During this period of time, the MS can directly transmit uplink data (if any) without reestablishing the uplink TBF. Therefore, the overhead of uplink TBF reestablishment is saved and the
transmission delay of uplink data is reduced. This significantly improves the network KPIs, especially for the long-time discontinuous transmission (such as interactive transmission and ping) on the uplink. For example, the ping delay can be reduced by 300 ms. Figure 2-117 shows the procedure for the release of an extended uplink TBF. 1. After receiving the last uplink RLC data block (CV = 0), the BSC does not release the extended uplink TBF immediately. Instead, the BSC sends a Packet Uplink Ack/Nack (FAI = 0) control block. Then, the TBF enters the inactive period. The BSC starts the inactive period timer. The duration of the timer is specified by the Inactive Period of Extended Uplink TBF parameter. The BSC continues to allocate uplink resources to the MS until the inactive period timer expires. The uplink resources are used for the MS to transmit control blocks. During the inactive period, if certain uplink RLC data blocks need to be transmitted, the MS can directly use the uplink TBF that enters the inactive period without establishing a new uplink TBF. The uplink TBF used by the MS automatically enters the active period. If no uplink RLC data block needs to be transmitted, the MS sends a Packet Uplink Dummy Block message to the BSC. When the inactive period elapses, the BSC instructs the MS to release this uplink TBF through a Packet Uplink Ack/Nack message (FAI = 1) if no uplink RLC data block needs to be transmitted. After receiving this message, the MS sends a Packet Control ACK message to the BSC. Then, the uplink TBF is properly released.
2.
3.
Figure 2-117 Release of an extended uplink TBF
Issue 08 (2011-09-30)
551
?.3. Release of a Downlink TBF

1. 2. During downlink TBF transmission, all data in the LLC PDU queue is transmitted. In the last downlink data block, the BSC sets both the final block indicator (FBI) and S/P to 1. If the MS correctly receives all the downlink data blocks, it sends the BSC a Packet Downlink Ack/Nack message with FAI = 1. Otherwise, the MS sends the BSC a Packet Downlink Ack/Nack message with FAI = 0, requesting the BSC to retransmit the data blocks that are not received. After receiving the Packet Downlink Ack/Nack message with FAI = 1, the BSC properly releases the downlink TBF.
3.
Figure 2-118 shows the procedure for the release of a downlink TBF Figure 2-118 Release of a downlink TBF
A monitoring mechanism is required to ensure that the downlink TBF can be released if the Packet Downlink Ack/Nack message is lost. 1. Each time the BSC sets S/P to 1 in the downlink TBF data blocks, the BSC starts the counter N3105. The maximum value of this counter is specified by the Maximum Value of N3105 parameter. If the BSC correctly receives a Packet Downlink Ack/Nack message from the MS, the BSC resets the counter N3105 to zero. If the BSC does not correctly receive a Packet Downlink Ack/Nack message from the MS, the counter N3105 is incremented by one. If the counter N3105 exceeds its maximum value N3105_max, the BSC automatically starts the internal timer T3195. After the timer T3195 expires, the downlink TBF is released.
2. 3. 4.
2.41.3.5 Uplink Data Transmission

One MS can use multiple PDCHs and one PDCH can be shared by multiple MSs. The radio blocks of only one MS, however, can be transmitted on each PDCH in each radio block period. An MS knows the PDCH that carries radio blocks and the radio block containing data to be transmitted on the PDCH by Uplink State Flag (USF), and therefore schedules radio blocks. The scheduling enables, multiple MSs to share one uplink channel. If one PDCH is shared by multiple TBFs, the TBFs are scheduled according to their QoS capabilities. USFs can be allocated in two modes: dynamic allocation mode and extended dynamic mode. In extended dynamic mode, the MS transmitting uplink blocks dose not need to the subsequently allocated channels. Therefore, the MS can use more uplink channels than those in dynamic allocation mode. The extended dynamic mode helps increase the uplink data transmission rate and allows services with a large amount of data to be transmitted on the uplink, improving the user satisfaction. The extended dynamic mode requires support from the MS. The RAC reported by the MS indicates whether the MS supports the GPRS extended dynamic allocation mode or the EGPRS extended dynamic allocation mode.
?.1. Dynamic Allocation Mode

In dynamic allocation mode, an MS identifies the PDCH where radio blocks are allocated by USF. Radio blocks used by an MS are temporarily allocated by the BSC. The uplink resource allocation message or uplink resource reallocation message sent by the BSC contains the number of PDCHs allocated to an MS and the value of corresponding USF on each PDCH. After receiving the message, the MS starts to listen to the USF value in the downlink radio block header of the allocated channel. If the USF value in the downlink radio block header is equal to the allocated USF value, the MS has the rights to use the uplink channel. Then, the MS transmits data blocks on this channel in the next radio block period. USFs are classified into reserved USFs and idle USFs. A reserved USF is a USF value that is not allocated to any GPRS/EGPRS MS and is used to prevent more than one GPRS/EGPRS MS from attempting to transmit data on the same PDCH. Currently, the reserved USF is 7. The BSC informs a GPRS/EGPRS MS that one or more uplink radio blocks have been reserved for it on a particular PDCH. The GPRS/EGPRS MS may have an uplink or downlink TBF, or no TBF at all. When the radio block period elapses, the BSC sends the MS the Reserved USF. Only the MS to which this block has been assigned is allowed to transmit data. l Reserved USFs are used in the following scenarios: The second phase of the two-phase access If a downlink RLC/MAC control block contains a valid RRBP field, the receiving MS uses its reserved block to send a single control message. If the USF granularity is 4, the MS uses its three reserved blocks to send RLC/MAC data blocks or control messages. l Idle USFs are used on the PRACH in the next uplink block period. This PRACH channel is used during the first phase of an establishment procedure. All MSs are allowed to transmit a packet channel request on the PRACH.
A monitoring mechanism is required to ensure that uplink TBFs can be released properly. 1. After starting to allocate a USF to an uplink TBF (an uplink TBF is successfully established), the BSC starts the counter N3101 to check whether the uplink data is received. The maximum value of this counter is specified by the Maximum Value of N3101 parameter. The BSC waits for the MS to transmit uplink data in the reserved RLC uplink block corresponding to the USF. If the MS has uplink RLC blocks for transmission, the BSC resets N3101 to zero. If the MS does not have uplink RLC blocks for transmission, N3101 is incremented by one. If the counter N3101 exceeds its maximum value N3101_max, the TBF is abnormally released.
2.
3.
?.2. Extended Dynamic Mode

In extended dynamic mode, the MS determines the radio blocks to be assigned to multiple PDCHs by USF. The resource assignment mechanism in extended dynamic mode is the same as that in dynamic allocation mode. The number of channels used on the uplink is greater than the number of channels used on the downlink. After receiving the USF value of a channel, the MS transfers data on this channel and on other channels whose channel number is greater than the number of this channel.
If the USF granularity for a downlink USF is 4 and the USF value of timeslot 3 that is assigned to this TBF is 5, the following three timeslots (timeslots 4-to 6) are also assigned to the downlink TBF in the next uplink period, as described in Table 2-97. All the four timeslots may not be allocatedc to this TBF. If one of them is allocated to this TBF, however, the subsequent timeslots are definitely allocated to this TBF. Table 2-97 Extended dynamic mode PDCH Downlink Uplink Timeslot 3 USF=5 Timeslot 4 USF=7 Timeslot 5 USF=7 Timeslot 6 USF=7
NOTE
The symbol indicates that this timeslot is occupied.
All the assignment-related messages contain a list of assigned PDCHs and the related USF value for each PDCH. If the allocated resources do not allow the MS to listen to the USF values for all the allocated PDCHs, the MS listens to according to the following principles: In a data block transfer period, the MS obtains the USFs in all the timeslots from the timeslot to which the MS listens to the current timeslot. For example, if the USF in timeslot 3 to which the MS listens is consistent with the locally saved USF, the MS can transfer data in timeslots 3, 4, 5, and 6. If the USF in timeslot 5 to which the MS listens is consistent with the locally saved USF, the MS can transfer data in timeslots 5, 6, and 7. If the PDCHs on which EGPRS and GPRS services are multiplexed use USF granularity 4, the downlink traffic volume of the EGPRS TBF is increased. A GPRS-capable MS and an EGPRScapable MS use the same PDCH. Therefore, the EGPRS-capable MS uses only radio blocks with the GPRS coding scheme on the downlink. After receiving a downlink radio block, the MS triggers uplink radio block transfer. The EGPRS-capable MS obtains its own USF value from the header of a downlink radio block. l l If the USF granularity is 4, uplink data is transferred on the PDCH in the next four radio block periods. If the USF granularity is 1, uplink data is transferred on the PDCH in the next radio block period.
If the USF granularity is 1, the BSC must send one more downlink radio block with the Gaussian minimum shift-frequency keying (GMSK) coding scheme to trigger the uplink radio block transfer when the EGPRS-capable MS needs to transfer one more uplink radio block. Therefore, the EGPRS downlink bandwidth is adversely affected. If the USF granularity is 4, one downlink radio block triggers four uplink radio blocks. Therefore, the number of downlink radio blocks with the GMSK coding scheme is reduced and the EGPRS downlink bandwidth is slightly affected.
?.3. Handling of LLC PDUs and RLC Data Blocks

RLC data blocks are received on each PDCH. AN RLC data blocks contains transport format indicator (TFI), which indicates the TBF that the RLC data block belongs to. RLC data blocks are numbered sequentially and can be reassembled into LLC PDUs. LLC PDUs consist of one or more RLC data blocks.
?.4. RLC Mode

There are two RLC modes: acknowledged mode and unacknowledged mode. l One-phase access For 8-bit access, only the RLC acknowledged mode is used. For 11-bit access, the RLC unacknowledged mode is used if the EGPRS Packet Channel Request message carries the information element One phase Access Request in RLC unack mode; the RLC acknowledged mode is used if the message does not carry the information element One phase Access Request in RLC unack mode. l The information element Channel Request Description carried in the Packet Resource Request and Packet Downlink Ack/Nack messages from the MS indicates the RLC mode used by the network.
The GPRS/EGPRS MS informs the BSC of which RLC mode is used by sending a Packet Channel Request message or an EGPRS Packet Channel Request message. Then, one-phase access is complete.
RLC Acknowledged Mode

In RLC acknowledged mode, the BSC acknowledges the reception of all the RLC data blocks. The TBF can be released only when the MS acknowledges that all the data blocks are transmitted. This mode ensures the transmission reliability for RLC data blocks. If the BSC does not acknowledge the reception of all the RLC data blocks, the MS retransmits the lost data blocks. After the MS receives all the acknowledgement messages from the BSC, the BSC releases the uplink TBF. If the MS does not receive an acknowledgement message, the MS sets SI set to 1 in the uplink RLC/MAC block after the sliding window stops. After receiving the uplink RLC/MAC block with SI = 1, the BSC retransmits the Packet Uplink Ack/Nack message. The interval of transmitting the Packet Uplink Ack/Nack message with SI set to 1 in the uplink block is shorter than the normal interval of transmitting the Packet Uplink Ack/Nack message.
RLC Unacknowledged Mode

In RLC unacknowledged mode, the BSC also acknowledges the received RLC data blocks but the MS does not need to process acknowledgement messages. In addition, the transmitted data blocks do not need to be acknowledged by the BSC. The TBF can be released immediately after the data transmission is complete. The BSC still sends the MS a Packet Uplink Ack/Nack message periodically, indicating that the network is receiving data properly.
?.5. Uplink Access Congestion Control

If too many MSs request GPRS resources in a cell at the same time, the resources may be insufficient and therefore uplink congestion may occur. Uplink flow control is performed to control the service requests (including paging responses) initiated by MSs. The control of uplink service requests is performed by controlling the number of random accesses on the PRACH/RACH. Uplink flow control may affect the response speed and the network QoS but it helps improve the system capacity. Therefore, it can be used in some suitable situations.
2.41.3.6 Downlink Data Transmission

After a downlink TBF is established, the BSC disassembles the received LLC PDUs into RLC data blocks. The BSC schedules the RLC data blocks and RLC/MAC control blocks at an appropriate time. The RLC data blocks and RLC/MAC control blocks are ranked by priority. For radio blocks on the same channel, the radio block with a higher priority is preferentially transmitted. An RLC/ MAC control block has a higher priority than an RLC data block. If two or more TBFs share one PDCH, the BSC schedules of the RLC data blocks and RLC/MAC control blocks based on the QoS of each TBF.
?.1. Scheduling of Downlink Radio Blocks

Each downlink TBF can be allocated to one or more PDCHs and multiple downlink TBFs can share one PDCH. Each downlink TBF has a radio block queue, which is used to transmit radio blocks to MSs. An RLC/MAC control block has a higher priority than an RLC data block. Radio blocks are transmitted on all the PDCHs that are allocated to the MSs. In RLC acknowledged mode, the radio block that is not acknowledged by an MS is retransmitted or a new radio block is generated. By delaying The BSC delays segmenting LLC PDUs and starts to transmit data until it selects the optimal coding scheme according to the radio environment.
Scheduling of Downlink Radio Blocks

One or more PDCHs can be allocated to each MS. Each PDCHs can carry logical channels such as the PACCH and PDTCH. The next radio block is scheduled immediately after one radio block is transmitted.
Handling for No Radio Block Scheduling

If there is no downlink data for transmission, the BSC sends a Packet Downlink Dummy Block message containing the USF of an MS to perform uplink scheduling.
?.2. Handling of LLC PDUs and RLC Data Blocks

DL-UnitData messages are sent from the SGSN to the BSC over the Gb Interface. Each DLUnitData message contains an LLC PDU and the control information required for the transmission of the LLC PDU on the Um interface. In a TBF, an LLC PDU containing user signaling data has a higher priority than an LLC PDU containing user data. When the GPRS/ EGPRS QoS feature is enabled, LLC PDUs are queued at different priorities. The LLC PDUs are disassembled into RLC data blocks and are then scheduled. For EGPRS, a radio block contains one or two RLC data blocks depending on the MCS coding scheme used. l l In MCS-1 to MCS-6 coding scheme mode, a radio block contains one RLC data block. In MCS-7 to MCS-9 coding scheme mode, a radio block contains two RLC data blocks.
If a downlink TBF is in transfer mode and the LLC PDU queue of this TBF has downlink data, the BSC sends downlink data to the MS. If a downlink TBF is not in transfer mode or the LLC PDU queue of this TBF does not have downlink data, the BSC does not send downlink data to the MS.
?.3. RLC Mode

The RLC mode for a downlink TBF is determined by the QoS attribute for a downlink LLC PDU. Each DL-UnitData message indicates the RLC mode used for data transmission. After sending a certain number of RLC data blocks to a GPRS/EGPRS MS, the BSC sets S/P to 1 in the next radio block to be sent. There are two RLC modes: acknowledged mode and unacknowledged mode.
Acknowledged Mode
In acknowledged mode, the MS returns a Packet Downlink Ack/Nack message to acknowledge the received data message (S/P = 1). This message contains acknowledgement and unacknowledgement information about certain RLC data blocks. The unacknowledged RLC data blocks are rescheduled for downlink transmission. If a radio block contains two RLC data blocks and only one of them is acknowledged, only the unacknowledged RLC data block is retransmitted.
Unacknowledged Mode
In unacknowledged mode, radio blocks are not retransmitted. The following situation, however, is an exception. If the BSC does not receive a downlink acknowledgement message from the MS, the final radio block in a downlink TBF is retransmitted for a specified number of times. This allows the MS to know that the transmission of downlink data is complete.
?.4. Downlink Flow Control

The Gb and Um interfaces have different data transmission rates. because these two interfaces use different physical media and transmission protocols. The data transmission rate on the Gb interface is greater than that on the Um interface. In addition, the downlink data transmission rate on the Um interface is unstable because of various factors, such as the MS multislot capability, radio quality, and available radio channels in a cell. Therefore, the flow control on downlink data is required. The BSC checks the data validity when forwarding downlink LLC PDUs. If the LLC PDUs in the queue exceeds half of the queue capacity, the BSC performs flow control and sends a flow control message over the Gb interface. When the cell is in the normal state, the BSC starts the flow control procedure. The BSC periodically reports the bucket size and bucket flow rate of the cell to the SGSN according to the situation of the radio packet channels in the cell. In addition, the BSC reports the bucket sizes and bucket flow rates of the MSs based on the amount of radio resources occupied by the MSs. The SGSN adjusts the downlink data flow rate of the cell and MSs in real time based on the bucket size and bucket flow rate of the cell and the bucket size and bucket flow rate of the MSs separately. Therefore, downlink data flow is controlled.
NOTE
The bucket size of a cell refers to the maximum packet data storage space that the BSC reserves for the cell. The bucket size varies according to a number of packet channels in the cell. The bucket size of an MS refers to the maximum packet data storage space that the BSC reserves for the MS. The bucket size varies according to a number of channels allocated to the MS. The bucket flow rate refers to the data transmission rate.
Downlink flow control consists of downlink BVC flow control and downlink MS flow control. l
Issue 08 (2011-09-30)
Downlink BSSGP virtual connection (BVC) flow control

The BSC reports to the SGSN the flow control parameters, such as the maximum bucket size and the BVC leak rate. According to the flow control parameters, the SGSN performs flow control to prevent frequent data loss caused by congestion and prevent the transmission disruption caused by insufficient bandwidth. The BSC sends the SGSN a FLOWCONTROL-BVC message, indicating that the cell is ready to receive downlink LLC PDU data. This message includes the buffer size and data flow rate. These are set high enough to accommodate the maximum GPRS traffic volume in the cell. l Downlink MS flow control The BSC reports to the SGSN the flow control parameters, such as the maximum bucket size and the leak rate of the MS. According to the flow control parameters, the SGSN performs flow control to prevent frequent data loss caused by congestion and prevent the transmission disruption caused by insufficient bandwidth. The BSC sends the SGSN a FLOW-CONTROL-BVC message, which contains default flow control parameters for any MS that enters the cell. The SGSN receives from the MS an MS-FLOW-CONTROL message, which contains the corresponding parameters for the MS. The SGSN uses these parameters to perform flow control on each MS. Note that this message is sent at the beginning of TBF establishment. The buffer size and leak rate depend on the multislot capability of the MS and whether the TBF is using GPRS or EGPRS. If the buffer usage or transmission rate varies during the lifetime of the TBF, additional messages can be sent to change the flow control parameters.
?.5. LLC PDU Lifetime Supervision

Each DL-UnitData message contains an LLC PDU lifetime timer, which specifies the queuing duration for each LLC PDU on the BSC side. The BSC first checks how long each LLC PDU has been queued. Then, the BSC disassembles it into RLC data blocks. If the lifetime of an LLC PDU has expired, it is discarded. At the same time, the BSC sends an LLC-Discarded message to the SGSN. Discarding of LLC PDUs due to delay reduces the negative impacts from temporary disruptions in downlink transfer at the RLC layer. Temporary disruptions at the RLC layer may be caused by: l l l l l Preemption of PDCH TBF setup failure Intra-cell handover of SGSN in dual transfer mode (DTM) connection Cell reselection in SGSN during packet transfer Completion of non-enhanced circuit service by MS in DTM connection
When a downlink TBF is abnormally released or a downlink TBF is not successfully established, the LLC PDUs are saved in the downlink buffer for a period of time. After that, if the downlink TBF is successfully established and the LLC PDUs in the buffer are not discarded, the data transmission continues. This makes the temporary disruption unlikely to be noticed by the end user. If the LLC PDU lifetime expires and the downlink TBF is not successfully established, the remaining LLC PDUs in the buffer are discarded. At the same time, the BSC sends an LLCDiscarded message to the SGSN.
?.6. Flush LL Procedure

If an MS processing downlink services moves to a new cell, the SGSN sends a Flush LL message to the BSC. This message indicates whether all the queued LLC PDUs should be discarded or whether they should be transferred to the new cell in which the MS is located.
If the BSC discards all the queued LLC PDUs, the downlink TBF is released. The BSC sends the SGSN a Flush LL Ack message, indicating how many the number of discarded LLC PDUs. If the BSC transfers the queued LLC PDUs to the new cell, the LLC PDUs whose lifetime has expired are first discarded and other LLC PDUs are then transferred to the new cell. Then, the BSC sends the SGSN a Flush LL Ack message, indicating the number of LLC PDUs to be transferred or discarded. The existing TBF is released and a new TBF is established in the new cell.
2.41.3.7 Reassignment of a TBF

A TBF is reassigned when the existing current TBF changes. After reassignment, the number of PDCHs bound to this TBF changes. Reassignment of a TBF involves the reassignment of an uplink TBF, the reassignment of a downlink TBF, and the reassignment of the concurrent uplink and downlink TBFs (TS procedure).
?.1. Reassignment of an Uplink TBF

If the BSC finds a TBF that meets the uplink reassignment condition, the BSC sends the MS a Packet Uplink Assignment message to allocate additional PDCHs without waiting for an acknowledgement message from the MS. After a period of time, the MS continues to transmit data over a new PDCH.
?.2. Reassignment of a Downlink TBF

If the BSC finds a TBF that meets the downlink reassignment condition, the BSC sends the MS a Packet Downlink Assignment message to allocate additional PDCHs without waiting for an acknowledgement message from the MS. After a period of time, the BSC continues to transmit data over a new PDCH.
?.3. Reassignment of the Concurrent Uplink and Downlink TBFs (TS Procedure)
In a TS procedure, the BSC sends the MS a Packet Timeslot Reconfigure message to allocate concurrent uplink and downlink TBFs. This balances the uplink and downlink load. If the channel load becomes imbalanced because of TBF establishment or release, the MS is migrated from channels with high load to channels with low load. This ensures load balancing and increases the data rate per user. The TS procedure adjusts the uplink and downlink channel resources. The TS procedure is initiated to assign the maximum bandwidth resources for uplink data transmission in one of the following situations: the preferred service type is uplink service; the bandwidth allocated to the uplink does not reach the maximum value; the available bandwidth of the system is not less than the maximum bandwidth required on the uplink. The same is the case with the downlink. 1. 2. During channel allocation, the BSC preferentially allocates channels on the TRX with lower load based on the load on different TRXs. This ensures the load balancing among TRXs. The BSC can allocate uplink and downlink TBFs to MSs. The BSC triggers the TS procedure to periodically adjust the channels occupied by the uplink and downlink TBFs. This is to ensure the load balancing among channels. If a PDCH cannot provide sufficient radio blocks for the TBF, the TBF is transferred to a more eligible PDCH. This does not increase the load of a specific TBF but increases the total TBF load on the PDCHs. An existing TBF is migrated from channels with high TBF load to channels with low TBF load.
Issue 08 (2011-09-30)
3.
GPRS and EGPRS channels coexist in the system. If GPRS channels are overloaded, the GPRS MSs are assigned EGPRS channels. When the MSs release GPRS channels, the load on EGPRS channels is taken into account. If the load on GPRS channels decreases, some GPRS MSs are migrated from EGPRS channels to GPRS channels to increase the channel usage and to reduce the impact on EGPRS service.
The procedure for reassigning concurrent uplink and downlink TBFs is as follows: The BSC sends the Ms a Packet Timeslot Reconfigure message to allocate new PDCHs, USFs, and TFIs. After a period of time, the MS continues to transmit data over the new PDCHs. Figure 2-119 shows the procedure for reassigning concurrent uplink and downlink TBFs. Figure 2-119 Reassignment of the concurrent uplink and downlink TBFs
2.41.3.8 Suspend and Resume

When a GPRS-attached class B MS establishes a circuit switched (CS) connection, the BSC initiates the suspend procedure to suspend the GPRS/EGPRS service for the MS and also informs the SGSN of the suspension. When the CS service is complete, the BSC initiates the resume procedure. The resume procedure can be initiated only when the suspend procedure is successful. If the resume procedure is not initiated or fails, the MS performs a routing area update procedure after the CS connection is released to inform the SGSN of the GPRS/EGPRS service resumption.
?.1. Suspend
To suspend a GPRS service, the BSC sends the SGSN a Suspend PDU message to stop the TBFs in scheduling and release them. The SGSN returns a Suspend-Ack PDU/Suspend-Nack PDU message to the BSC. l l If the BSC receives a Suspend-Ack PDU message, the suspend procedure is successfully completed. If the BSC receives a Suspend-Nack PDU message, the CS connection is released the suspend procedure fails.
?.2. Resume
The BSC initiates the resume procedure when a CS service is complete. l If the suspend procedure is successfully complete and the call is released in the same routing area as the one where it was set up, the BSC sends a Resume PDU message to the SGSN. If the SGSN responds with a Resume-Ack PDU message, the GPRS service is successfully resumed. If the SGSN responds with a Resume-Nack PDU message, the GPRS service dose not resume.
If the call is released in a different routing area from the one where it was set up, the network cannot perform the resume procedure for the MS. The MS has to perform routing area update.
2.41.4 Parameters
The following describes the parameters related to GPRS/EGPRS connection control and transfer. For the meaning of each parameter, see Table 2-98. For the default value, value range, and related MML commands of each parameter, see Table 2-99. Table 2-98 Parameter description (1) Parameter Not Send Dummy Message with Extended Uplink TBF Description Whether to send the Dummy message during the deactivated period of the extended uplink TBF. This parameter specifies whether to support the takeover of the packet immediate assignment by the BTS. It is relative to the uplink immediate assignment. To improve the access rate of the MS, the BSS allocates the uplink TBF resources to the BTS in advance. The BTS sends the immediate assignment message to the MS through the resources allocated by the BSC. When receiving the immediate assignment message, the MS can send the data block. The BTS needs to send the assistant channel request to the BSC. When receiving the request, the BSC sends the immediate assignment request to the BTS to complete the TDF setup flow. Whether to support the 11-bit EGPRS access request. Whether to support the function of moving the packet assignment down to the BTS. To improve the access speed of the MS, after the packet assignment is moved down to the BTS, the BSC reserves the uplink resources for the BTS. The BTS obtains the channel request of the MB by analyzing the downlink acknowledgement message sent by the MS. Then the BTS allocates the reserved uplink resources to the MS to move the packet assignment to the BTS.
Move Immediate Assignment Down to BTS Support 11BIT EGPRS Access
Move Packet Assignment Down to BTS
Issue 08 (2011-09-30)
561
Parameter
Description Delay of releasing the downlink TBF. After the last downlink RLC data block is transmitted on the network side and all the transmitted downlink data blocks are received, the MS is not informed to stop this downlink TBF. Instead, the state of the last data block is forcibly set to "not received" and the RRBP flag of the last data block is retransmitted continuously so that the downlink TBF is not released. During the downlink delay release, if the upper layer of the network side needs to transmit downlink data, the downlink RLC block for unpacking can be transmitted in the downlink TBF for delay release. The state of the downlink TBF is changed from delay releasing to downlink transmitting. In addition, the MS must respond to the Packet Downlink Ack/Nack message through the uplink data block of the RRBP to exchange messages with the network side. When the MS needs to send data, the MS can send the uplink request to the network sides through the Packet Downlink Ack/Nack with the channel request description. If this parameter is set to 0, the release delay of downlink TBF is disabled. Duration of releasing the TBF after the MS receives the last data block. When the MS receives the RLC data block containing the flag identifying the last data block and confirms that all the RLC data blocks in the TBF are received, the MS sends the packet downlink acknowledge message containing the last flag acknowledgement and the timer T3192 is started. If the timer T3192 expires, the MS releases the TBF related resources and starts monitoring the paging channel. During TBF releasing, if the MS is the half duplex mode and receives the packet uplink assignment, the MS responds this command. During TBF releasing, if the MS is the half duplex mode and receives no packet uplink assignment message, the MS enters the packet idle mode. If the MS is in the dual transmission mode, the MS enters the special mode. Maximum value of the N3101 counter. When the uplink transmission ends, if the network side receives the last RLC data block, the network side sends an FAI=1 uplink packet acknowledged/unacknowledged message and starts N3103. If the packet control acknowledgement message is not received in the specified time, N3103 is increased on the network side and the uplink packet acknowledged/unacknowledged message is retransmitted. When this counter is overflowed, the timer T3169 is started. After this timer expires, the current TBF is released abnormally.
Release Delay of Downlink TBF
T3192
Maximum Value of N3103
Issue 08 (2011-09-30)
562
Parameter
Description Delay of releasing the non-extended uplink TBF. After receiving the last uplink RLC data block (CountValue=0), the network side sends the message Packet Uplink Ack/Nack with FAI=1 to notify the MS of releasing the uplink TBF. After this parameter is set, the network side notifies the MS of releasing this TBF after specified delay. In this way, the downlink TBF can be established on the unreleased uplink TBF. This uplink TBF is automatically released when the downlink TBF is established or when the delay duration exceeds the time set by the uplink non-extended TBF. If this parameter is set to 0, the release delay of non-extended TBF is disabled. Inactive period of extended uplink TBF. After the network side receives the last uplink RLC data block (CountValue=0) of the MS supporting the extended uplink TBF, the uplink TBF is not released immediately. Instead, the uplink TBF is set to the inactive state. In the inactive period, if the MS needs to transmit the uplink RLC data block, the MS can use the inactive uplink TBF without rebuilding a new uplink TBF. This inactive uplink TBF is switched to the active state automatically. At the end of the inactive period, if the MS does not transmit the uplink RLC data block, the network side sends the message Packet Uplink Ack/Nack to notify the MS of releasing the uplink TBF. When the uplink TBF is inactive, the downlink TBF can be established according to this uplink TBF. 0: disable the function of the extended uplink TBF (this function can be disabled on the BSC side). Maximum value of the N3105 counter. After the downlink TBF is set up successfully, the N3105 is started on the network side. After the downlink RLC data block is added with the RRBP domain on the network side, the valid packet acknowledged message responded by the MS is received in the uplink RLC data block in the RRBP domain. In this case, N3105 is reset. Otherwise, the value of N3105 is increased and the downlink data block of the RRBP is retransmitted. When N3105 is overflowed, T3195 is started. After the timer T3195 expires, the current TBF is released abnormally. Maximum value of the N3101 counter. In the dynamic uplink allocation mode, the network side enables multiple MSs to share the same uplink channel through the USF value in the downlink data block. After the network side allocates the USF to the uplink TBF (the uplink TBF is set up successfully), N3101 is started. The network side waits for the RLC uplink data block sent by the MS. If the RLC uplink data block sent by the MS is valid, N3101 is reset. Otherwise, the value of N3101 is increased on the network side. When this counter is overflowed, the current uplink TBF is released abnormally.
Release Delay of Nonextended Uplink TBF
Inactive Period of Extended Uplink TBF
Issue 08 (2011-09-30)
563
Table 2-99 Parameter description (2) Paramete r Not Send Dummy Message with Extended Uplink TBF Move Immediate Assignme nt Down to BTS Support 11BIT EGPRS Access Move Packet Assignme nt Down to BTS Default Value GUI Value Range SEND (SEND), NOTSEN D (NOTSEN D) NO(Not Support), YES (Support) NO(NO), YES (YES) NO(Not Support), YES (Support) Actual Value Range Unit MML Comman d Impact
SEND
SEND, NOTSEN D
None
SET GCELLPS BASE (Optional) SET GCELLPS OTHERP ARA (Optional) SET GCELLPS BASE (Optional) SET GCELLPS OTHERP ARA (Optional) SET GCELLP RIVATE OPTPAR A (Optional)
Cell
NO
NO, YES
None
Cell
YES
NO, YES
None
Cell
NO
NO, YES
None
Cell
Release Delay of Downlink TBF
2400
0~5000 0ms(0ms), 80ms (80ms), 120ms (120ms), 160ms (160ms), 200ms (200ms), 500ms (500ms), 1000ms (1000ms), 1500ms (1500ms)
0~5000
ms
Cell
T3192
500ms
0ms, 80ms, 120ms, 160ms, 200ms, 500ms, 1000ms, 1500ms
ms
SET GCELLPS BASE (Optional)
Cell
Issue 08 (2011-09-30)
564
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLS TANDAR DOPTPA RA (Optional) SET GCELLP RIVATE OPTPAR A (Optional) SET GCELLP RIVATE OPTPAR A (Optional) SET GCELLS TANDAR DOPTPA RA (Optional) SET GCELLS TANDAR DOPTPA RA (Optional)
Impact
Maximum Value of N3103 Release Delay of Nonextended Uplink TBF Inactive Period of Extended Uplink TBF
2~5
2~5
None
Cell
120
0~300
0~300
ms
Cell
2000
0~5000
0~5000
ms
Cell
10
3~10
3~10
None
Cell
20
8~30
8~30
None
Cell
2.41.5 Counters
2.41.6 Glossary

l
Issue 08 (2011-09-30)
3GPP TS 43.064: Overall description of the GPRS Radio Interface; Stage 2

l l l l l l l l
3GPP TS 48.018: "BSS GPRS Protocol (BSSGP)" 3GPP TS 44.060: "Radio Link Control/Medium Access Control (RLC/MAC) protocol" 3GPP TS 44.018: Radio Resource Control (RRC) protocol BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.42 GPRS/EGPRS Link Quality Control

2.42.1 Introduction
2.42.1.1 Scope
This document describes GPRS coding scheme adjustment algorithm, and EGPRS coding scheme adjustment algorithm in the GPRS/EGPRS link quality control feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the GPRS/EGPRS link quality control feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Version
l l
02 (2009-09-30) 01 (2009-06-30)
02 (2009-09-30)
01 (2009-06-30)
2.42.2 Overview
GPRS/EGPRS link quality control is implemented to adjust GPRS/EGPRS coding schemes dynamically according to the radio link quality during packet data transmission. It enables coding schemes to adapt to the radio environment, maximizes the data throughput, and increases the data rate and system capacity. At present, the GPRS network evolves from the GSM network. Therefore, the system capacity is limited. With an increasing demand for radio data services, the limitation of the GPRS bandwidth becomes a critical issue. In theory, the maximum data rate per timeslot on a GPRS network is 21.4 kbit/s and the rate of eight multiplexed timeslots is up to 171.2 kbit/s. However, the actual rate of a GPRS network is less than the theoretical rate. The reason is as follows: The number of GPRS dedicated channels is limited. The CS services have priority to use the channels that can be converted into GPRS dedicated channels. Moreover, most MSs have limited multislot capability and support only a small number of downlink channels. To resolve the problem of GPRS bandwidth limitation, the EGPRS technology is introduced. In EGPRS, new modulation schemes, coding schemes, and data acknowledgment mechanisms are used to increase the rate per timeslot and per timeslot and the system bandwidth. To increase the rate per timeslot, EGPRS adopts 8 phase shift keying (8PSK). In the 8PSK modulation scheme, absolute phases of signals. indicate symbols. There are eight possible symbols and each symbol represents three bit information. In the GMSK modulation scheme, each symbol represents one bit of information. In theory, the modulation rate for 8PSK is three times that of GMSK. Table 2-100 provides the comparison between GPRS and EGPRS.
Issue 08 (2011-09-30)
567
Table 2-100 Comparison between GPRS and EGPRS Parameter Modulation scheme Chip rate Modulation bit rate Maximum throughput per timeslot Maximum throughput every 8 timeslots GPRS GMSK 270 kbit/s 270 kbit/s 21.4 kbit/s (CS-4) 171.2 kbit/s EGPRS 8PSK/GMSK 270 kbit/s 810 kbit/s 59.2 kbit/s (MCS-9) 473.6 kbit/s
Four coding schemes, CS-1 to CS-4, are defined for GPRS. Each coding scheme has its specific error correction capability and coding rate. Nine modulation and coding schemes, MCS-1 to MCS-9, are defined for EGPRS. EGPRS provides the same functions as GPRS. In addition, EGPRS has higher coding rates. MCS-1 to MCS-4 are modulated with GMSK, and MCS-5 to MCS-9 are modulated with 8PSK. Figure 2-120 shows the coding schemes and maximum throughputs of GPRS and EGPRS. Figure 2-120 Coding schemes and maximum throughputs of GPRS and EGPRS
In different radio link conditions, each coding scheme has its specific throughput. The GPRS/ EGPRS link quality control algorithm adjusts coding schemes dynamically according to the channel quality to achieve the maximum throughput. This algorithm consists of the GPRS coding scheme adjustment algorithm and the EGPRS coding scheme adjustment algorithm.

2.42.3.1 GPRS Coding Scheme Adjustment Algorithm

GPRS supports the GMSK modulation scheme and four coding schemes: CS-1 to CS-4. The number of parity bits that are added during the coding varies according to the coding scheme. Therefore, the anti-interference capability is coding scheme specific. From CS-1 to CS-4, the number of parity bits decreases sequentially; therefore, the anti-interference capability decreases accordingly. The transmission rate and the requirements for the radio environment, however, increase sequentially. When the C/I is the same, CS-4 has the highest block error ratio (BLER), that is, CS-4 requires a relatively high C/I to ensure the same BLER as other coding schemes. In a GPRS network, CS-4 must be used and the C/I must be high to ensure the maximum throughput. Table 2-101 lists the key parameters and theoretical rates of GPRS. Table 2-101 Key parameters and theoretical rates of GPRS Coding Scheme CS-1 CS-2 CS-3 CS-4 Code Rate Radio Block Excluding USF and BCS 181 268 312 428 Coded Bits Data Rate (kbit/s) 9.05 13.4 15.6 21.4
1/2 2/3 3/4 1
456 588 676 456
The GPRS coding scheme adjustment algorithm is described as follows: 1. The BSC determines whether to use a fixed coding scheme based on the setting of Uplink Fixed CS Type or Downlink Fixed CS Type. The initial coding scheme is specified by Uplink Default CS Type or Downlink Default CS Type. In RLC unacknowledged mode, if the current coding scheme is CS-3 or CS-4, the BSC changes it to CS-2. Otherwise, the current coding scheme remains unchanged. In RLC acknowledged mode, the BSC selects a coding scheme based on the mean retransmission rate of RLC data blocks, current coding scheme, and coding scheme conversion threshold. The retransmission rate is the proportion of the number of RLC data blocks that are not received to the total number of RLC data blocks sent in a retransmission rate measurement period. The mean retransmission rate is the filtered retransmission rate. The rules for selecting a coding scheme are as follows: l If the current coding scheme is CS-1 and the uplink or downlink mean retransmission rate is lower than Uplink TBF Threshold from CS1 to CS2 or Downlink TBF Threshold from CS1 to CS2, then the BSC selects CS-2. l If the current coding scheme is CS-2 and the uplink or downlink mean retransmission rate is lower than Uplink TBF Threshold from CS2 to CS3 or Downlink TBF Threshold from CS2 to CS3, then the BSC selects CS-3; if the current coding scheme is CS-2 and the uplink or downlink mean retransmission rate is higher than Uplink TBF Threshold from CS2 to CS1 or Downlink TBF Threshold from CS2 to CS1, then the BSC selects CS-1. l If the current coding scheme is CS-3 and the uplink or downlink mean retransmission rate is lower than Uplink TBF Threshold from CS3 to CS4 or Downlink TBF
2. 3.
Threshold from CS3 to CS4, then the BSC selects CS-4; if the current coding scheme is CS-3 and the uplink or downlink mean retransmission rate is higher than Uplink TBF Threshold from CS3 to CS2 or Downlink TBF Threshold from CS3 to CS2, then the BSC selects CS-2. l If the current coding scheme is CS-4 and the uplink or downlink mean retransmission rate is higher than Uplink TBF Threshold from CS4 to CS3 or Downlink TBF Threshold from CS4 to CS3, then the BSC selects CS-3. 4. If the TBF is released abnormally when counter N3101 reaches the maximum value, the uplink coding scheme must be changed to one providing a lower rate; if the TBF is released abnormally when counter N3105 reaches the maximum value, the downlink coding scheme must be changed to one providing a lower rate. Counter N3101 is specified by Maximum Value of N3101, and counter N3105 is specified by Maximum Value of N3105.
2.42.3.2 EGPRS Coding Scheme Adjustment Algorithm

?.1. Overview
The EGPRS system defines nine coding schemes: MCS-1 to MCS-9. MCS-1 to MCS-4 are modulated with GMSK, and MCS-5 to MCS-9 are modulated with 8PSK. In poor radio environment, the performance of GMSK is better than that of 8PSK. Therefore, EGPRS uses both GMSK and 8PSK modulation schemes. Table 2-102 lists the key parameters and theoretical rates of EGPRS. Table 2-102 Key parameters and theoretical rates of EGPRS Coding Scheme Code Rate Modulation Scheme RLC Blocks per Radio Block (20 ms) 2 2 2 1 Raw Data Within One Radio Block 2 x 592 2 x 544 2 x 448 592 48 + 544 MCS-5 MCS-4 MCS-3 0.37 1.0 0.85 GMSK 1 1 1 448 352 296 48 + 248 296 MCS-2 MCS-1 0.66 0.53 1 1 224 176 B C 11.2 8.8 B C A Family Data Rate (kbit/s)
MCS-9 MCS-8 MCS-7 MCS-6
1.0 0.92 0.76 0.49
8PSK
A A B A
59.2 54.4 44.8 29.6 27.2 22.4 17.6 14.8 13.6
Issue 08 (2011-09-30)
570
The EGPRS transmit power in the 8PSK modulation scheme is different from that in the GMSK modulation scheme. From the perspective of network operation, the EGPRS transceiver must have the same spectrum features as a common transceiver. When sending the signals modulated with 8PSK, the EGPRS transceiver uses the average transmit power that is 2-5 dB less than the average transmit power of the signals modulated with GMSK to meet. the spectrum requirements. The spectrum requirements can be met by setting Cell 8PSK Power Attenuation Grade, whose default value is 0. On the BCCH, the transmit power of the signals modulated with 8PSK can be a maximum of 4 dB less than the average transmit power of the signals modulated with GMSK. In the timeslot before the timeslot of the BCCH or CCCH, the transmit power of the signals modulated with 8PSK can be a maximum of 2 dB less than the average transmit power of the signals modulated with GMSK. To achieve the possible maximum throughput on radio links, EGPRS uses combined link quality control modes: link adaptation (LA) mode and incremental redundancy (IR) mode. Compared with the pure LA mode, the combined mode significantly improves the performance of radio links. The link quality control mode is specified by the Link Quality Control Mode parameter, whose default value is IR. l LA mode In LA mode, the network side adjusts channel coding schemes dynamically according to the link quality to achieve the maximum throughput. The MS measures the downlink quality; the BTS measures the uplink quality. The network side determines an appropriate coding scheme according to the radio link measurement report sent from the MS. For the cells where the signal quality on the Um interface is good, the link quality control mode is generally set to LA. l IR mode In IR mode, the transmitter retransmits data blocks in puncturing-scheme-based code diversity mode instead of in time diversity mode to increase redundancy. The receiver does not discard erroneous packets but stores them and combines and decodes them together with the soft information of the same data block. In this way, the gains of channel coding and time diversity can be obtained at the same time. Therefore, in the case that the channel quality is ensured, the BLER decreases and the throughput increases. For the cells where the signal quality on the Um interface is poor, the transmission performance of radio links is comparatively good. In such a case, the link quality control mode is generally set to IR.
?.2. Uplink EGPRS Coding Scheme Adjustment Algorithm

Depending on whether the BTS supports sending BEP measurement reports to the BSC, the uplink EGPRS coding scheme adjustment algorithm is carried out in the following ways: l When the BTS supports sending BEP measurement reports to the BSC, the BSC adjusts the uplink EGPRS coding scheme according to the uplink BEP measurement reports sent from the BTS. When the BTS does not support sending BEP measurement reports to the BSC, the BSC adjusts the uplink EGPRS coding scheme according to the downlink BEP measurement reports sent from the MS.
The uplink frame from the BTS to the BSC carries the information about whether the BTS supports sending BEP measurement reports to the BSC. Based on this information, the BSC determines the used coding scheme adjustment algorithm.
Issue 08 (2011-09-30)
571
BSC Adjusting the Uplink EGPRS Coding Scheme According to the Uplink BEP Measurement Report Sent from the BTS
When the BTS supports sending BEP measurement reports to the BSC, it sends a BEP measurement report to the BSC in an uplink data frame. When receiving the uplink data frame from the BTS, the BSC triggers the uplink EGPRS coding scheme adjustment procedure if the BSC finds the change in the current link quality according to the measurement report. When the BTS cannot decode the uplink radio blocks correctly, it sends an uplink information frame to the BSC. The uplink information frame carries the BEP measurement report. After receiving the uplink information frame, the BSC triggers the uplink EGPRS coding scheme adjustment procedure. The uplink EGPRS coding scheme adjustment algorithm is described as follows: 1. The BSC determines whether to use the fixed MCS coding scheme in the uplink based on the setting of Uplink Fixed MCS Type. If the fixed MCS coding scheme is used, the uplink coding scheme is specified by Uplink Fixed MCS Type. Otherwise, the uplink initial coding scheme is specified by Uplink Default MCS Type. Later, the BSC adjusts the uplink coding scheme according to the uplink BEP measurement report sent from the BTS. Each time the BSC receives an uplink data frame from the BTS or an uplink information frame generated by the BTS when the BTS cannot decode the radio blocks correctly, the BSC filters the BLER and BEP measurement reports. The BEP measurement reports carried by the uplink frames are related to radio blocks. After filtering the measured BEP values of the radio blocks, the BSC obtains the MEAN_BEP and CV_BEP values on each timeslot. Then, the BSC sums up the MEAN_BEP and CV_BEP values on the timeslots occupied by the TBF to obtain the MEAN_BEP and CV_BEP values of the TBF. At the same time, the BSC adjusts the MEAN_BEP value of the TBF based on the BLER. Based on the MEAN_BEP and CV_BEP values of the uplink TBF, the BSC chooses the required coding scheme in the uplink BEP to coding scheme mapping table. If the current coding scheme is not the required one, the BSC adjusts the current uplink coding scheme. The modulation scheme may change during the coding scheme adjustment. To enhance the stability of coding scheme adjustment and to prevent ping-pong handovers of modulation schemes, the leaky bucket algorithm is used when the coding scheme in GMSK is changed a the one in 8PSK. The basic principles of the leaky bucket algorithm are as follows: Each time the BSC adjusts the coding scheme in GMSK to a one in 8PSK, the bucket size increases; each time the BSC adjusts the coding schemes within GMSK, the bucket size decreases. The adjustment from GMSK to 8PSK is allowed only when the bucket size reaches a specific value.
2.
3.
4.
BSC Adjusting the Uplink EGPRS Coding Scheme According to the Downlink BEP Measurement Report Sent from the MS
When the BTS does not support sending BEP measurement reports to the BSC, the BSC adjusts the uplink EGPRS coding scheme according to the BEP measurement report in the EGPRS PACKET DOWNLINK ACK/NACK message. The uplink EGPRS coding scheme adjustment algorithm is as follows: 1. The BSC determines whether to use the fixed MCS coding scheme in the uplink based on the setting of Uplink Fixed MCS Type. If the fixed MCS coding scheme is used, the uplink coding scheme is specified by Uplink Fixed MCS Type. Otherwise, the uplink initial coding scheme is specified by Uplink Default MCS Type. The BSC adjusts the uplink coding scheme according to the downlink BEP measurement report sent from the MS. After receiving the EGPRS PACKET DOWNLINK ACK/NACK message, the BSC obtains the MEAN_BEP and CV_BEP values of the TBF from the message. Based on the
2.
Issue 08 (2011-09-30)
MEAN_BEP and CV_BEP values of the TBF, the BSC chooses the required coding scheme in the uplink BEP to coding scheme mapping table. If the current coding scheme is not the required one, the BSC adjusts the current uplink coding scheme. 3. When counter N3101 reaches the maximum value and the TBF is released abnormally, a lower-rate coding scheme must be used if the requirement for the signal quality on the Um interface after the coding scheme adjustment is higher than that before the adjustment. Counter N3101 is specified by Maximum Value of N3101.
?.3. Downlink EGPRS Coding Scheme Adjustment Algorithm

The MS measures the downlink quality periodically and filters the measured values to generate a downlink EGPRS channel quality report. The downlink EGPRS channel quality report is carried by the EGPRS PACKET DOWNLINK ACK/NACK message sent from the MS to the BSC. The filtering period of downlink quality measured values is specified by Bep Period. The BSC broadcasts the BEP period in the system information to the MS. After receiving the EGPRS PACKET DOWNLINK ACK/NACK message, the BSC adjusts the downlink EGPRS coding scheme according to the BEP measurement report in the message. When RLC data blocks are not retransmitted, the downlink EGPRS coding scheme adjustment algorithm is described as follows: 1. The BSC determines whether to use the fixed MCS coding scheme in the downlink based on the setting of Downlink Fixed MCS Type. If the fixed MCS coding scheme is used, the downlink coding scheme is specified by Downlink Fixed MCS Type. Otherwise, the downlink initial coding scheme is specified by Downlink Default MCS Type. The BSC adjusts the downlink coding scheme according to the downlink BEP measurement report sent from the MS. After receiving the EGPRS PACKET DOWNLINK ACK/NACK message, the BSC obtains the MEAN_BEP and CV_BEP values of the TBF from the message. The MEAN_BEP and CV_BEP values of the TBF are used for the downlink coding scheme adjustment. Based on the value of the MS OUT OF MEMORY field in the EGPRS PACKET DOWNLINK ACK/NACK message, the downlink coding scheme can be adjusted in the following ways: l If the value of the MS OUT OF MEMORY field is 0, the MS has sufficient memory to perform the IR function. The BSC adjusts the MEAN_BEP value of the TBF based on the BLER. Then, based on the MEAN_BEP and CV_BEP values of the TBF, the BSC chooses the required coding scheme against the downlink BEP to coding scheme mapping table in IR mode. If the current coding scheme is not the required one, the BSC adjusts the current downlink coding scheme. l If the value of the MS OUT OF MEMORY field is 1, the MS has no sufficient memory to perform the IR function. Then, based on the MEAN_BEP and CV_BEP values of the TBF, the BSC chooses the required coding scheme in the downlink BEP to coding scheme mapping table in LA mode. If the current coding scheme is not the required one, the BSC adjusts the current downlink coding scheme. To prevent ping-pong handovers of modulation schemes, the leaky bucket algorithm is triggered when the coding scheme is changed from GMSK to 8PSK. For details of the leaky bucket algorithm, see 2.42.3.2.2 Uplink EGPRS Coding Scheme Adjustment Algorithm. 3. When counter N3105 reaches the maximum value and the TBF is released abnormally, a lower-rate coding scheme must be used if the requirement for the signal quality on the Um interface after the coding scheme adjustment is higher than that before the adjustment. Counter N3105 is specified by Maximum Value of N3105.
2.
For RLC data block retransmission, if the current link quality control mode is IR mode, the RLC data blocks cannot be segmented when the coding scheme needs to be changed during the
retransmission. The BSC needs to choose a coding scheme for retransmission from the segmentation-prohibited retransmission coding scheme table. If the current link quality control mode is LA mode, or the value of the MS OUT OF MEMORY field in the EGPRS PACKET DOWNLINK ACK/NACK message is 1, the RLC data blocks can be segmented when the coding scheme needs to be changed during the retransmission. The BSC needs to choose a coding scheme for retransmission from the segmentation-allowed retransmission coding scheme table.
2.42.4 Parameters
The following describes the parameters related to GPRS/EGPRS link quality control. For the meaning of each parameter, see Table 2-103. For the default value, value range, and related MML commands of each parameter, see Table 2-104. Table 2-103 Parameter description (1) Parameter Description Adjustment mode of the uplink GPRS link coding scheme. If the fixed coding scheme is used, this parameter is a value ranging from CS1 to CS4. If the dynamic coding scheme is used, this parameter is set to UNFIXED. Adjustment mode of the downlink GPRS link coding scheme. If the fixed coding scheme is used, this parameter is set to a value ranging from CS1 to CS4. If the dynamic coding scheme is used, this parameter is set to UNFIXED. Default coding scheme of the uplink GPRS link. If the uplink adopts the dynamic adjustment coding scheme, this parameter can be used to set the coding scheme for transmission during initial access. If the uplink uses the fixed coding scheme, the TBF uses the fixed coding scheme. Coding scheme of the default GPRS downlink. Dynamic adjustment coding: the coding scheme used during initial access transmission. If the downlink uses the fixed coding scheme, the TBF uses the fixed coding scheme. Retransmission threshold when the coding mode of the uplink TBF is changed from CS1 to CS2. When the retransmission rate of the uplink TBF is less than or equal to this threshold, the coding mode of the uplink TBF is changed from CS1 to CS2. Retransmission threshold when the coding mode of the downlink TBF is changed from CS1 to CS2. When the TBF retransmission rate is less than or equals to this value, the coding mode of the TBF is changed from CS1 to CS2. Retransmission threshold when the coding mode of the uplink TBF is changed from CS2 to CS3. When the retransmission rate of the uplink TBF is less than or equal to this threshold, the coding mode of the uplink TBF is changed from CS2 to CS3.
Uplink Fixed CS Type
Downlink Fixed CS Type
Uplink Default CS Type
Downlink Default CS Type Uplink TBF Threshold from CS1 to CS2 Downlink TBF Threshold from CS1 to CS2 Uplink TBF Threshold from CS2 to CS3
Issue 08 (2011-09-30)
574
Parameter Downlink TBF Threshold from CS2 to CS3 Uplink TBF Threshold from CS2 to CS1 Downlink TBF Threshold from CS2 to CS1 Uplink TBF Threshold from CS3 to CS4 Downlink TBF Threshold from CS3 to CS4 Uplink TBF Threshold from CS3 to CS2 Downlink TBF Threshold from CS3 to CS2 Uplink TBF Threshold from CS4 to CS3 Downlink TBF Threshold from CS4 to CS3
Description Retransmission threshold when the coding mode of the TBF is changed from CS2 to CS3. When the downlink TBF retransmission rate is less than or equals to CS2 to CS1, the coding mode of the TBF is changed from CS2 to CS3. Retransmission threshold when the coding mode of the uplink TBF is changed from CS2 to CS1. When the retransmission rate of the uplink TBF is greater than or equal to this threshold, the coding mode of the uplink TBF is changed from CS2 to CS1. Retransmission threshold when the coding mode of the downlink TBF is changed from CS2 to CS1. When the downlink TBF retransmission rate is greater than or equals to this value, the coding mode of the TBF is changed from CS2 to CS1. Retransmission threshold when the coding mode of the uplink TBF is changed from CS3 to CS4. When the retransmission rate of the uplink TBF is less than or equal to this threshold, the coding mode of the uplink TBF is changed from CS3 to CS4. Retransmission threshold when the coding mode of the downlink TBF is changed from CS3 to CS4. When the downlink TBF retransmission rate is less than or equals to this value, the coding mode of the downlink TBF is changed from CS3 to CS4. Retransmission threshold when the coding mode of the uplink TBF is changed from CS3 to CS2. When the retransmission rate of the uplink TBF is greater than or equal to this threshold, the coding mode of the uplink TBF is changed from CS3 to CS2. Retransmission threshold when the coding mode of the TBF is changed from CS3 to CS2. When the TBF retransmission rate is greater than or equals to this value, the coding mode of the TBF is changed from CS3 to CS2. Retransmission threshold when the coding mode of the uplink TBF is changed from CS4 to CS3. When the retransmission rate of the uplink TBF is greater than or equal to this threshold, the coding mode of the uplink TBF is changed from CS4 to CS3. Retransmission threshold when the coding mode of the downlink TBF is changed from CS4 to CS3. When the downlink TBF Retransmission rate is greater than or equals to this value, the coding mode of the TBF is changed from CS4 to CS3.
Issue 08 (2011-09-30)
575
Parameter
Description Maximum value of the N3101 counter. In the dynamic uplink allocation mode, the network side enables multiple MSs to share the same uplink channel through the USF value in the downlink data block. After the network side allocates the USF to the uplink TBF (the uplink TBF is set up successfully), N3101 is started. The network side waits for the RLC uplink data block sent by the MS. If the RLC uplink data block sent by the MS is valid, N3101 is reset. Otherwise, the value of N3101 is increased on the network side. When this counter is overflowed, the current uplink TBF is released abnormally. Maximum value of the N3105 counter. After the downlink TBF is set up successfully, the N3105 is started on the network side. After the downlink RLC data block is added with the RRBP domain on the network side, the valid packet acknowledged message responded by the MS is received in the uplink RLC data block in the RRBP domain. In this case, N3105 is reset. Otherwise, the value of N3105 is increased and the downlink data block of the RRBP is retransmitted. When N3105 is overflowed, T3195 is started. After the timer T3195 expires, the current TBF is released abnormally. Timeslot power attenuation level of the EDGE TRX in 8PSK. The attenuation level ranges from 0 to 50, each of which corresponds to an attenuation of 0.2 dB. When the EDGE TRX sends signals in 8PSK, the transmit power must be lower than the mean power in GMSK. It is applicable to the radio transmission environment to improve the link quality. Link adaptation (LA) indicates adjusting the coding mode of the channel dynamically according to the transmission quality of the link. The link transmission quality is measured by the 8PSK MEAN BEP and 8PSK CV BEP in the Packet EGPRS Downlink Ack/ Nack message sent by the MS. The network side determines the coding mode for data transmission according to the radio measurement report sent by the MS. The cell with the good transmission quality on the air interface is set to the LA mode. Increment redundancy (IR) mode requires the network side retransmit the data block with different punching codes and the MS store the historical error information. The data block is retransmitted through cooperated error correction function. With the IR mode, the transmission quality on the air interface of the cell can be improved. However, the MS must support this IR mode. The cell with the dissatisfied transmission quality on the air interface is set to the LR mode. Coding scheme of the uplink EDGE link. If the uplink uses the fixed coding scheme, this parameter is set to a value ranging from MCS1 to MCS9. If the uplink uses the dynamic adjustment coding scheme, this parameter is set to UNFIXED. Default coding scheme of the uplink EDGE link. If the uplink adopts the dynamic adjustment coding scheme, this parameter can be used to set the coding scheme for transmission during initial access. If the uplink uses the fixed coding scheme, the TBF uses the fixed coding scheme.
Cell 8PSK Power Attenuation Grade
Link Quality Control Mode
Uplink Fixed MCS Type
Uplink Default MCS Type
Issue 08 (2011-09-30)
576
Parameter Bep Period
Description Average period for sending the measurement report over the EGPRS channel. Coding scheme of the downlink EDGE link. If the downlink uses the fixed coding scheme, this parameter is set to a value ranging from MCS1 to MCS9. If the downlink uses the dynamic adjustment coding scheme, this parameter is set to UNFIXED. Default coding scheme of the downlink EDGE link. If the downlink adopts the dynamic adjustment coding scheme, this parameter can be used to set the coding scheme for transmission during initial access. If the downlink uses the fixed coding scheme, the TBF uses the fixed coding scheme.
Downlink Fixed MCS Type
Downlink Default MCS Type
Table 2-104 Parameter description (2) Paramete r Default Value GUI Value Range CS1(CS1), CS2(CS2), CS3(CS3), CS4(CS4), UNFIXE D (UNFIXE D) CS1(CS1), CS2(CS2), CS3(CS3), CS4(CS4), UNFIXE D (UNFIXE D) CS1(CS1), CS2(CS2), CS3(CS3), CS4(CS4) CS1(CS1), CS2(CS2), CS3(CS3), CS4(CS4) Actual Value Range Unit MML Comman d Impact
UNFIXE D
CS1, CS2, CS3, CS4, UNFIXE D
None
SET GCELLPS CS (Optional)
Cell
Downlink Fixed CS Type Uplink Default CS Type Downlink Default CS Type
UNFIXE D
None
SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional)
Cell
CS1
CS1, CS2, CS3, CS4
None
Cell
CS2
CS1, CS2, CS3, CS4
None
Cell
Issue 08 (2011-09-30)
577
Paramete r Uplink TBF Threshold from CS1 to CS2 Downlink TBF Threshold from CS1 to CS2 Uplink TBF Threshold from CS2 to CS3 Downlink TBF Threshold from CS2 to CS3 Uplink TBF Threshold from CS2 to CS1 Downlink TBF Threshold from CS2 to CS1 Uplink TBF Threshold from CS3 to CS4 Downlink TBF Threshold from CS3 to CS4
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional)
Impact
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
10
0~64
0~64
per cent
Cell
10
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
Issue 08 (2011-09-30)
578
Paramete r Uplink TBF Threshold from CS3 to CS2 Downlink TBF Threshold from CS3 to CS2 Uplink TBF Threshold from CS4 to CS3 Downlink TBF Threshold from CS4 to CS3
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLS TANDAR DOPTPA RA (Optional) SET GCELLS TANDAR DOPTPA RA (Optional) SET GCELLB ASICPAR A (Optional) SET GCELLE GPRSPA RA (Optional)
Impact
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
20
8~30
8~30
None
Cell
Maximum Value of N3105 Cell 8PSK Power Attenuatio n Grade Link Quality Control Mode
10
3~10
3~10
None
Cell
0~50
0~50
None
Cell
IR
IR(IR), LA(LA)
IR, LA
None
Cell
Issue 08 (2011-09-30)
579
Paramete r
Default Value
GUI Value Range MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), MCS7 (MCS7), MCS8 (MCS8), MCS9 (MCS9), UNFIXE D (UNFIXE D) MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), MCS7 (MCS7), MCS8 (MCS8), MCS9 (MCS9)
Actual Value Range
Unit
MML Comman d
Impact
UNFIXE D
MCS1, MCS2, MCS3, MCS4, MCS5, MCS6, MCS7, MCS8, MCS9, UNFIXE D
None
Cell
MCS2
None
SET GCELLE GPRSPA RA (Optional) SET GCELLE GPRSPA RA (Optional)
Cell
Bep Period
0~10
0~10
None
Cell
Issue 08 (2011-09-30)
580
Paramete r
Default Value
GUI Value Range MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), MCS7 (MCS7), MCS8 (MCS8), MCS9 (MCS9), UNFIXE D (UNFIXE D) MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), MCS7 (MCS7), MCS8 (MCS8), MCS9 (MCS9)
Actual Value Range
Unit
MML Comman d
Impact
UNFIXE D
None
Cell
MCS6
None
Cell
2.42.5 Counters
Issue 08 (2011-09-30)
581
2.42.6 Glossary

l l l l l l l l l l 3GPP TS 45.008: "Radio subsystem link control" 3GPP TS 44.060: "Radio Link Control/Medium Access Control (RLC/MAC) protocol" 3GPP TS 43.064: "Overall description of the GPRS radio interface; Stage 2" 3GPP TS 45.005: "Radio transmission and reception" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.43 GPRS/EGPRS Overview

2.43.1 Introduction
2.43.1.1 Scope
This document defines the GPRS/EGPRS and describes the networking configuration, definitions, and system procedures involved in the GRPS/EGPRS Overview feature.


This provides information on the changes in different document versions. There are two types of changes, which are defined as follows:
Feature change Feature change refers to the change in the GPRS/EGPRS Overview feature of a specific product version.
Editorial change Editorial change refers to the change in wording or the addition of information that was not provided in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.43.2 Overview
This document describes the General Packet Radio Service (GPRS), which is a type of end-toend packet switched service based on the GSM technology. It supports Gaussian minimum shiftfrequency keying (GMSK) CS-1 to CS-4. The maximum rate of a single channel is 20 kbit/s. GPRS enables a subscriber to send and receive data in end-to-end packet transfer mode and has the following features: l l l l
Issue 08 (2011-09-30)
Makes full use of the existing GSM network infrastructure. Enables efficient use of radio resources. Provides a radio access rate of up to 171.2 kbit/s. Supports standard interfaces.
GPRS provides abundant packet services, for example, mobile Internet access, e-Commerce (eBank and e-Currency), cluster management, remote control/remote measurement, booking system (hotels, theatres, and airplanes), and group services (stock information publication). EDGE consists of the Enhanced GPRS (EGPRS) and the Enhanced Circuit Switched Data (ECSD). l EGPRS is enhanced GPRS. In addition to GMSK, EGPRS also uses the 8 Phase Shift Keying (8PSK) modulation scheme to increase the peak rate of a single channel to 59.2 kbit/s. ECSD is enhanced high-speed circuit switched data (HSCSD). To provide a data rate of 57.6 kbit/s, HSCSD requires four timeslots, but ECSD requires only two timeslots.
NOTE
Huawei BSC supports only EGPRS. Unless otherwise specified, EDGE mentioned in this document indicates EGPRS.
GPRS provides MSs with high-speed packet data services. It prolongs the life expectancy of GSM, enhances the utilization of radio resources. It can smoothly evolve to the 3G network and effectively secure the investment of operators. By using new modulation and coding schemes, EDGE provides data rates about three times that in GPRS on the Um interface and meets the requirements of high-speed data services.

2.43.3.1 Networking Configuration
?.1. Overview
With GPRS support nodes (GSNs) and packet control units (PCUs), the GPRS can be implemented in the GSM system through software upgrade. There are two GPRS networking modes: with external PCUs and with built-in PCUs. The components of in the GPRS network are as follows: l l l l l l l l l l Serving GPRS support node (SGSN) Gateway GPRS support node (GGSN) Border gateway Charging gateway HLR/AUC PCU BSC BTS DNS Firewall
Huawei BSC supports both built-in PCU and external PCU. This enables flexible network deployment according to actual requirements.

NOTE
Built-in PCUs and external PCUs cannot coexist in the BSS.
When built-in PCUs are used for networking, the number of DPUd boards and the number of Gb interface boards are determined by GPRS traffic volume. Figure 2-121 shows the GPRS network topology with built-in PCUs. Figure 2-121 GPRS network topology with built-in PCUs
If external PCUs are used for networking: l l When the GPRS traffic of each BSC is light, multiple BSCs can be connected to one PCU. When the GPRS traffic of a BSC is heavy and one PCU does not meet service requirements, the BSC can be connected to multiple PCUs.
Figure 2-122 shows the GPRS network topology with external PCUs.
Issue 08 (2011-09-30)
585
Figure 2-122 GPRS network topology with external PCUs
?.2. Gb Interface
The Gb interface is an interface between the SGSN and the BSS. Through this interface, the SGSN communicates with the BSS and the MS and performs functions such as packet data transfer, mobility management, and session management. The Gb interface is a standard interface. It is mandatory for the GPRS network. Figure 2-123 shows the protocol stack over the Gb interface.
Issue 08 (2011-09-30)
586
Figure 2-123 Protocol stack over the Gb interface
NS: Network Service LLC: Logical Link Control
BSSGP: Base Station Subsystem GPRS Protocol GMM/SM: GPRS Mobility Management and Session Management
The protocol stack over the Gb interface works as follows: l The physical layer over the Gb interface uses the frame relay (FR) or IP protocol in direct connection or in FR/IP network connection. The physical layer provides communication services for the NS layer. The network service (NS) layer configures and manages network service virtual connections (NSVCs) or network service virtual links (NSVLs), routes uplink data, transmits user plane data, and provides communication services for the BSSGP layer. The NS layer complies with the GSM 08.16 protocol. The BSSGP layer sends and receives signaling and data to/from the LLC layer, performs downward data flow control, and maintains BSSGP virtual connections (BVCs) such as blocking, unblocking, and resetting BVCs. The BSSGP layer complies with the GSM 08.18 protocol.
Management of the Gb Interface

Management of the Gb interface refers to the management of BVC, network service entity (NSE), NSVC, NSVL, bearer channel (BC), and permanent virtual connection (PVC). The BC is an FR bearer channel. It belongs to the physical layer and corresponds to a timeslot group of E1/T1. In the BSC, Frame Relay Protocol Type determines the FR protocol used by the BC. The PVC is a permanent virtual connection for frame relay. It is a logical connection. The PVCs of a BC are distinguished by The Identifier of Data Link Connection(DLCI). The NSE is an end-to-end network service entity at the NS layer. The NSE can manage, block, unblock, and reset its NSVCs or NSVLs. If the underlying links use the FR protocol, Subnet Protocol Type is set to Gb over FR. The NS layer transmits the data of the BSSGP layer on NSVCs.
If the underlying links use the IP protocol, Subnet Protocol Type is set to Gb over IP and Subnetwork Configure Mode is set to Static Configuration or Dynamic Configuration. The NS layer transmits the data of the BSSGP layer on local NSVLs and remote NSVLs.
NOTE
If Subnetwork Configure Mode is set to Static Configuration, the BSC searches a remote NSVL list for the IP path to the SGSN. If Subnetwork Configure Mode is set to Dynamic Configuration, the BSC accesses the Server IP through the specified UDP port No. to obtain the signaling address and port number of the SGSN and then the IP path to the SGSN.
The BVC is a virtual connection between BSSGP entities. There are point-to-point BSSGP virtual connections (PTPBVCs), point-to-multipoint BSSGP virtual connections (PTMBVCs), and signal BSSGP virtual connections (SIGBVCs) between BSSGP entities. The PTPBVC and PTMBVC transmit user data, and the SIGBVC transmits signaling messages. Each NSE is allocated an SIGBVC. The BVC is associated with the NSE through NSE Identifier.
Networking of over the Gb Interface

The networking mode over the Gb interface can be Gb over FR or Gb over IP, which is determined by the protocol used by the physical layer over the Gb interface. l l If the physical layer over the Gb interface uses the FR protocol, the PEUa board must be configured for the BSC. If the physical layer over the Gb interface uses the IP protocol, the PEUa board must be configured for the BSC.
If the Gb interface uses the FR protocol, the BSC and the SGSN can be connected directly or through an FR network. l Direct connection means that the BSC and the SGSN are connected without any intermediate network. Generally, the BSC serves as the data terminal equipment (DTE) and the SGSN serves as the data circuit-terminating equipment (DCE). Figure 2-124 shows the direct connection in Gb over FR mode. Figure 2-124 Direct connection in Gb over FR mode
Figure 2-125 shows the connection between the BSC and the SGSN through the FR network.
Issue 08 (2011-09-30)
588
Figure 2-125 Network connection in Gb over FR mode
If the physical layer of the Gb interface uses the IP protocol, the BSC and the SGSN can be connected directly or through an IP network. l Direct connection in Gb over IP mode means that the BSC and the SGSN are connected without any intermediate IP network. In this connection, switches to provide layer 2 switching services for the BSC and the SGSN. Figure 2-126 shows the direct connection in Gb over IP mode. Figure 2-126 Direct connection in Gb over IP mode
Network connection in Gb over IP mode means that the BSC and the SGSN are connected through an IP network. In this connection, routers provide layer 3 routing services for the BSC and the SGSN. Figure 2-127 shows the network connection in Gb over IP mode. Figure 2-127 Network connection in Gb over IP mode
Compared with FR networking, IP networking greatly increases the bandwidth on the Gb interface and reduces the cost of network construction, operation, and maintenance.
?.3. Pb Interface
The Pb interface is a nonstandard interface between the PCU and the BSC. It is used only with external PCUs. The Pb interface manages shared resources such as cells, packet channels, E1 trunks, and system information between the PCU and the BSC. In addition, the Pb interface supports dynamic channel conversion and network access from the CCCH. The BTS is connected to the PCU through the BSC. The links between the PCU and the BSC consist of signaling links and traffic links. Figure 2-128 shows the protocol stack over the Pb interface. Figure 2-128 Protocol stack over the Pb interface
The protocol stack over the Pb interface works as follows: l Layer 1 is a physical layer, complying with the G.703 standard. It uses E1 timeslots. An E1 link is divided into 128 timeslots, with each having a bandwidth of 16 kbit/s. Four timeslots are used for synchronization. Layer 2 is a data link layer. It uses the LAPD protocol, which is a general data link layer protocol. Layer 2 uses the data transfer services offered by layer 1 and provides connectionoriented or connectionless services to layer 3. The objective of LAPD is to provide reliable end-to-end transmission between layer 3 entities through the physical interface. Layer 3 is the key part for the Pb interface. Layer 3 protocol consists of a series of selfdefined signaling messages. Layer 3 manages information about GPRS resources between the PCU and the BSC and supports dynamic channel conversion between packet-switched (PS) services and circuit-switched (CS) services. In addition, layer 3 enables the MS to access the network from the CCCH and enables the network to transmit PS paging messages on the CCCH. On the BSC side, the Pb interface processing (PbIP) function implements Pb message transfer and Pb interface signaling link (PbSL) selection.
Management of the Pb Interface

Pb interface management is classified into packet circuit identity code (PCIC) circuit management, radio resource management, PS service access support, transmission resource management, and PbSL management.
PCIC circuit management The purpose of PCIC circuit management is to ensure that the PCIC on the BSC side is consistent with that on the PCU side. When requesting a PDCH or dynamic channel conversion, the PCU can be assigned an idle circuit. The procedures related to PCIC circuit management are as follows: PCIC circuit block PCIC circuit unblock PCIC circuit reset These procedures are triggered by a change in the Pb equipment status or by operation and maintenance. The principles of PCIC circuit management are as follows: The BSC records only the maintenance status of PCIC circuits. All messages related to PCIC circuit management are initiated by the BSC. PCIC circuits can be blocked, unblocked, and reset on the PCU side. The status of PCIC circuits on the BSC side is not affected. If a PCIC circuit is blocked on the PCU LocalWS, the BSC cannot unblock this circuit.
Radio resource management Radio resource management on the Pb interface refers to the management of the radio resources only related to PS services. Information about the radio resources of the PCU is obtained from the BSC. The procedure consists of three steps: The cells on the BSC side and those on the PCU side are reset. The radio resource configuration for PS services in each cell is sent by the BSC to the PCU. Packet system information (PSI) is broadcast. CS services and PS services share radio resources, which are allocated on demand. CS services take priority over PS services in resource allocation. Allocation on demand enables the BSC to allocate radio resources between CS services and PS services in real time based on actual requirements. This means a dynamic conversion between TCH and PDTCH. The channel conversion procedures on the Pb interface are classified into the following types: When the PDTCHs are insufficient for PS services, the PCU requests the BSC to convert some TCHs into PDTCHs. The BSC accepts or rejects the request based on the number of available TCHs. If there are many idle TCHs, the BSC accepts the request, performs channel conversion, and instructs the BTS to modify the channel attributes. When the TCHs are insufficient for CS services, the BSC requests the PCU to release some PDTCHs and converts them into TCHs. This request must be accepted to ensure the QoS of CS services. When the PCU finds that there are excessive PDTCHs, it automatically releases the PDTCHs and converts them into TCHs. This ensures the QoS of CS services. The BSC is responsible for allocating TCHs, and the PCU is responsible for allocating PDTCHs. After a TCH is converted into a PDTCH, the PCU determines to allocate or release the PDTCH. The BSC determines to allocate or release the TCH. The status of radio resources on the BSC side must be consistent with that on the PCU side. To ensure the consistency, the BSC needs to notify the PCU of the change in the BTS and the impact of operation and maintenance on the radio resource status. For example, if a packet channel is blocked, the BSC instructs the PCU to update the status of the channel.
l
Issue 08 (2011-09-30)
PS service access support

To support GPRS, System Information 13 (SI13) needs to be broadcast on the BCCH. In addition, SI3 and SI7 need to be modified to include relevant GPRS information such as GPRS Indicator. Based on the system information, the MS decides whether and how to access the network in the serving cell to request PS services. If no PCCCH is configured in the serving cell, the MS requests PS services through a CCCH. The MS can request PS services in one or more of following procedures: MS originated packet access MS terminated packet access Suspension and restoration of PS services of class-B MSs l Transmission management When converting a TCH into a PDTCH, the BSC connects the trunk circuits on the Abis interface with those on the Pb interface. When converting a PDTCH into a TCH, the BSC disconnects the trunk circuits. During packet data transmission, the BSC forwards packets between the BTS and the PCU. Generally, each PDTCH corresponds to a 16 kbit/s timeslot. During data transmission, if the PCU finds that the transmission quality is satisfactory, it can use a more efficient coding scheme, such as CS-3 or CS-4. In this case, the BSC assigns one more 16 kbit/s timeslot to the PDTCH. Therefore, the PDTCH corresponds to a 32 kbit/ s timeslot. l PbSL management A Pb signaling link (PbSL) is an LAPD link. PbSL management involves link load sharing, message transmission, and message reception. If no PCCCH is configured in a cell, disconnection of all PbSLs or recovery of any disconnected PbSL leads to a change in the status of a cell on the PCU side.
Features of the Pb Interface

The Pb interface supports dynamic channel conversion between PS services and CS services. It also enables the MS to access the network from the CCCH. l Supporting dynamic channel conversion between PS services and CS services When the packet traffic is heavy and the speech traffic is light, the PCU requests the BSC to convert some TCHs into PDTCHs. When the speech traffic is heavy, the BSC requests the PCU to release some PDTCHs and converts them back to TCHs. In this process, CS services take priority over PS services to ensure the QoS of CS services. l Supporting the MS to access the network from the CCCH The BTS cannot identify an access request message sent by the MS on the CCCH. Therefore, the BSC needs to analyze this request message. If the message is a packet access request, the BSC forwards it to the PCU. Similarly, the BSC needs to process the immediate assignment message from the PCU before forwarding the message to the BTS. l Maintaining the consistency of various resources and data between the BSC and the PCU The PCU and the BSC are located at two different places, and therefore information about shared resources (such as cells, packet channels, E1 trunks, and system information) must be consistent. The main functions of the Pb interface are resource maintenance and management, such as cell parameter configuration, channel block/unblock, PCIC block/ unblock/resset, PSI parameter configuration, and regular check on resource data. l Sending CS paging messages
Issue 08 (2011-09-30)
592
In network operation mode I, the MSC sends a CS paging message over the Gs interface and Gb interfaces. After receiving the message, the PCU forwards it to the BSC over the Pb interface. Then, the BSC sends the CS paging message on the CCCH. l Supporting the PS service suspension and resumption messages sent by class-B MSs A class-B MS cannot perform CS services and PS services simultaneously. Therefore, after changing from a PS service to a CS service, the MS sends a GPRS suspension request to the BSC. Then, the BSC sends the request to the PCU over the Pb interface for processing. After the CS service is complete, the BSC sends a GPRS resumption request to the PCU over the Pb interface. The processing of this type of messages on the Pb interface improves the system capability to support class-B MSs. l Supporting two transmission modes In addition to terrestrial transmission, the Pb interface supports satellite transmission. If the two transmission modes are used, the BSC and the PCU can be installed in different equipment rooms. This meets the requirement for long distance transmission where one PCU is connected to multiple BSCs.
2.43.3.2 Definitions
?.1. Modulation and Coding Schemes
GPRS uses the GMSK modulation scheme and supports CS-1 to CS-4 coding schemes. EGPRS uses the 8PSK modulation scheme and supports MCS-1 to MCS-9 coding schemes. The peak rate of EGPRS is about three times that in GPRS. Figure 2-129 shows the rates of GPRS channels and those of EGPRS channels. Figure 2-129 Rates of GPRS channels and those of EGPRS channels
Issue 08 (2011-09-30)
593
Modulation Scheme
GMSK uses signal phase changes to represent symbols. Each symbol is mapped to one bit, 0 or 1. 8PSK uses absolute signal phases to represent symbols. Each symbol is mapped to three bits, and there are eight possible symbols. Therefore, the theoretical peak rate on the Um interface in EGPRS is three times that in GPRS. Figure 2-130 shows the I/Q diagrams for GPRS GMSK and EGPRS 8PSK. Figure 2-130 I/Q diagrams for GPRS GMSK and EGPRS 8PSK
In terms of network operation, the transceiver for EGPRS must have the same spectrum features as a common transceiver. Therefore, when sending signals modulated by 8PSK, the transceiver for EGPRS uses the transmit power that is 2-5 dB lower than the average power in GMSK modulation. This is implemented in the BSS by setting the parameter Cell 8PSK Power Attenuation Grade. The default value of this parameter is 0.
CS-1 to CS-4 Coding Schemes in GPRS

GPRS supports four coding schemes: CS-1 to CS-4. Table 2-105 describes the relationship between coding schemes and data rates. Table 2-105 GPRS coding schemes and data rates Coding Scheme CS-1 CS-2 CS-3 CS-4
Issue 08 (2011-09-30)
Rate (kbit/s) 8.0 12.0 14.4 20.0
594
The coding schemes initially used for a GPRS service are specified by Uplink Default CS Type and Downlink Default CS Type. Whether the coding schemes can be dynamically adjusted on the basis of signal qualities during the GPRS service processing is specified by Uplink Fixed CS Type and Downlink Fixed CS Type. If the GPRS coding schemes are allowed to be dynamically adjusted for the uplink and downlink based on signal quality, the coding schemes are adjusted according to the retransmission rate of temporary block flows (TBFs). l If the signal quality for uplink GPRS services is good and the TBF retransmission rate is lower than the predefined threshold, the GPRS coding schemes are adjusted to high-rate coding schemes. The involved parameters are as follows: Uplink TBF Threshold from CS1 to CS2 Uplink TBF Threshold from CS2 to CS3 Uplink TBF Threshold from CS3 to CS4 l If the signal quality for uplink GPRS services is poor and the TBF retransmission rate is higher than the predefined threshold, the GPRS coding schemes are adjusted to low-rate coding schemes. The involved parameters are as follows: Uplink TBF Threshold from CS2 to CS1 Uplink TBF Threshold from CS3 to CS2 Uplink TBF Threshold from CS4 to CS3 l If the signal quality for downlink GPRS services is good and the TBF retransmission rate is lower than the predefined threshold, the GPRS coding schemes are adjusted to high-rate coding schemes. The involved parameters are as follows: Downlink TBF Threshold from CS1 to CS2 Downlink TBF Threshold from CS2 to CS3 Downlink TBF Threshold from CS3 to CS4 l If the signal quality for downlink GPRS services is poor and the TBF retransmission rate is higher than the predefined threshold, the GPRS coding schemes are adjusted to lowspeed coding schemes. The involved parameters are as follows: Downlink TBF Threshold from CS2 to CS1 Downlink TBF Threshold from CS3 to CS2 Downlink TBF Threshold from CS4 to CS3
MCS-1 to MCS-9 Coding Schemes in EGPRS

EGPRS uses different coding schemes to meet the requirements of different PS services. Table 2-106 describes the characteristics of MCS-1 to MCS-9. Table 2-106 EGPRS coding schemes Coding Scheme Modulation Scheme 8PSK Number of Payload Bits in Each Burst 2x592 2x544
Rate (kbit/s)
MCS-9 MCS-8
Issue 08 (2011-09-30)
59.2 54.4
595
Coding Scheme
Modulation Scheme
Number of Payload Bits in Each Burst 2x448 592 544+48
Rate (kbit/s)
MCS-7 MCS-6
44.8 29.6 27.2 22.4 17.6 14.8 13.6 11.2 8.8
MCS-5 MCS-4 MCS-3 GMSK
448 352 296 272+24
MCS-2 MCS-1
224 176
NOTE
For 544 + 48 and 272 + 24 in Table 2-106, 544 and 272 indicate the numbers of significant bits, and 48 and 24 indicate the numbers of padding bits.
The coding schemes initially used for an EGPRS service are specified by Uplink Default MCS Type and Downlink Default MCS Type. Whether the MSC coding schemes can be adjusted during the EGPRS service processing is specified by Uplink Fixed MCS Type and Downlink Fixed MCS Type. If the MCS coding schemes can be adjusted, the BSS notifies the MS of Bep Period when sending system information. The MS calculates the downlink bit error probability (BEP) and notifies the BSS of the result in measurement reports (MRs). Then, the BSS adjusts the uplink and downlink MCS coding schemes based on the downlink BEP.
?.2. Packet Data Logical Channels
Types of Packet Data Logical Channels

According to the 3GPP TS 43.064 specifications, packet data logical channels are classified into packet broadcast control channel (PBCCH), packet common control channel (PCCCH), packet data traffic channel (PDTCH), and packet dedicated control channel (PDCCH). PBCCH: used only in the downlink. The PBCCH is used only for broadcasting the system information specific to packet data. If no PBCCH is available, the BCCH performs this function. PCCCH: carries common control signaling for packet data. PCCCHs are classified into the following types: l l Packet random access channel (PRACH): used only in the uplink. MSs send PDTCH requests on the PRACH. Packet paging channel (PPCH): used only in the downlink. The BSC sends paging messages to MSs on the PPCH. The PPCH uses paging groups to support discontinuous reception (DRX). The PPCH can be used for both CS services and PS services. For CS services,
Issue 08 (2011-09-30)
however, the PPCH is applicable to only class-A and class-B MSs. When an MS works in packet transfer mode, the PACCH can also be used to page the MS for CS services. l Packet access grant channel (PAGCH): used only in the downlink. Allocated resources are transmitted to the MS on the PAGCH before packet transfer.
PDTCH: carries user data in packet transfer mode. an MS operating in multislot mode is allowed to use multiple PDTCHs simultaneously for individual packet transfer. The transmission rate of a single PDTCH ranges from 0 kbit/s to 59.2 kbit/s. All PDTCHs are unidirectional. The PDTCH/ U transmits data from the MS to the GPRS network. The PDTCH/D transmits data from the GPRS network to the MS. After Channel Type of a channel is set during TRX configuration, the channel type can be further specified by PDCH Channel Priority Type: l The PDTCH on an EDGE-supported TRX can be configured as one of the following types: EGPRS dedicated channel: Only EGPRS MSs can use this type of channel. EGPRS Priority Channel: EGPRS MSs have preference to use it. GPRS MSs can use this type of channel if it is idle. When an EGPRS MS requests it, the GPRS MSs that are using it must be handed over to other channels. EGPRS MSs and GPRS MSs cannot use this type of channel simultaneously. EGPRS common channel: Both GPRS MSs and EGPRS MSs can use this type of channel. GPRS channel: Only GPRS MSs use this type of channel. If no EGPRS channel is available in a cell, EGPRS MSs can be provided with only GPRS services. l The PDTCH on an EDGE-unsupported TRX can be configured only as a GPRS channel. The preferred channel types vary with the following service type: l l For GPRS services, the preferred channel types are firstly the GPRS channel, secondly the EGPRS common channel, and thirdly the EGPRS priority channel. For EGPRS services, the preferred channel types are firstly the EGPRS dedicated channel, secondly the EGPRS Priority Channel, and thirdly the EGPRS common Channel.
Therefore, a GPRS MS and an EGPRS MS may use the same EGPRS common channel for uplink transmission and downlink transmission respectively. Such channel multiplexing can be avoided by setting the parameter Allow E Down G Up Switch. To avoid such multiplexing completely, do not configure the EGPRS common channel.
NOTE
The use of a channel depends on the type of the channel. For example, if a channel on an EGPRS-supported TRX is configured as a GPRS Channel, this channel can be used for only GPRS services. The EGPRS dedicated channel can be configured only as static channels. The other three types of channels can be configured as static or dynamic channels.
PDCCHs are classified into packet timing advance control channel (PTCCH) and packet associated control channel (PACCH): l l PTCCH: used to control the timing advance for an MS. PACCH: carries signaling messages, including acknowledgment messages and power control messages. The PACCH also carries resource assignment and reassignment messages, which are used to assign a capacity to a PDTCH or a new PACCH. One or more PDTCHs of an MS share the same PACCH.
Types of Combined Packet Data Logical Channels

Table 2-107 shows the types of combined packet data logical channels.
Table 2-107 Types of combined packet data logical channels Combination Number Combination 1 Combination Type PBCCH + PCCCH + PDTCH + PACCH + PTCCH PCCCH + PDTCH + PACCH + PTCCH Application Condition The cell needs to be configured with the PBCCH. Combination 1 is configured, many MSs camp on the cell, and the traffic on the PCCCH is heavy. None. Description One cell can be configured with only one Combination 1. One cell can be configured with one or more Combination 2.
Combination 2
Combination 3
PDTCH + PACCH + PTCCH
This combination is used to transmit uplink and downlink packet data. One cell can be configured with one or more Combination 3.
NOTE
PCCCH = PPCH + PRACH + PAGCH
If an external PCU is configured, channels are configured as static packet channels, speech channels, and dynamic packet channel. l Static packet channel The static packet channel broadcasts the GPRS PSI and transmit packet data. It cannot be used for CS services. The static packet channel can be configured as PBCCH+PDTCH, PCCCH+PDTCH, or PDTCH. l Speech channel The speech channel is dedicated for CS services. The speech channel includes TCH, BCCH, and SDCCH. l Dynamic packet channel The dynamic packet channel is initially a TCH and can be dynamically converted into a PDCH. If a built-in PCU is configured, no dynamic packet channel needs to be configured. When the parameter Channel Type is set to TCH Full Rate, the parameter PDCH Channel Priority Type must be set. The maximum number of PDCHs in a cell is specified by Maximum Rate Threshold of PDCHs in a Cell. The highest capability of a single PDCH to process PS services in a cell is specified by PDCH Uplink Multiplex Threshold and PDCH Downlink Multiplex Threshold. 1. When PS services are busy and exceed the threshold Uplink Multiplex Threshold of Dynamic Channel Conversion or Downlink Multiplex Threshold of Dynamic Channel Conversion, the BSC converts some available TCHs into PDCHs.
Issue 08 (2011-09-30)
2.
When CS services are busy and they request new TCHs, the BSC converts some PDCHs into TCHs.
In this process, CS services take priority over PS services. Therefore, the QoS of CS services can be ensured. Level of Preempting Dynamic Channel determines whether dynamic channels can be preempted by PS services, and Reservation Threshold of Dynamic Channel Conversion determines the number of dynamic channels that can be preempted by PS channels. For details, see 2.40 GPRS/EGPRS Channel Management.
?.3. Radio Link Control Modes

The radio link control (RLC) layer is responsible for assembling and disassembling LLC PDUs. By using a sliding window protocol, the RLC layer exchanges data with the peer entity in acknowledged or unacknowledged mode. The size of the sliding window for GPRS is 64, and that for EGPRS ranges from 64 to 1,024. In acknowledged mode, each data block in a TBF must be acknowledged by the peer end. If the data block is unacknowledged, it needs to be retransmitted. The TBF is released only after all the data blocks are transmitted and acknowledged. In unacknowledged mode, the data block need not be acknowledged by the peer end. If a data block is lost or contains errors, it is replaced with padding bits. The TBF is released after all the data blocks are transmitted. The BSC supports both RLC acknowledged mode and RLC unacknowledged mode. For uplink data transmission, the BSC determines the RLC mode based on the request from the MS. For downlink data transmission, the BSC determines the RLC mode based on the type of LLC PDUs.
RLC Acknowledged Mode

In RLC acknowledged mode, RLC blocks can be retransmitted. The sender numbers RLC blocks with block serial numbers (BSNs), which are used for retransmission and reassembly. The receiver requests retransmission of RLC blocks using a packet ACK/NACK message.
RLC Unacknowledged Mode

In RLC unacknowledged mode, RLC blocks cannot be retransmitted. During the uplink TBF release procedure, however, the last uplink data block may be retransmitted. The sender numbers RLC blocks with block serial numbers (BSNs), which are used for reassembly. The receiver requests the transmission of other necessary control signals using a packet ACK/NACK message.
?.4. Network Operation Modes

To coordinate the paging of CS services and PS services, three network operation modes are defined for the GPRS network. For details, see the 3GPP TS 23.060 specification.
Network Operation Mode I

Network operation mode I supports the paging coordination on the core network (CN). This function requires the configuration of the Gs interface. For a GPRS-attached MS, the network uses the same paging channel for transmitting PS and CS paging messages. Therefore, the MS needs to monitor only one paging channel. If a PDCH is allocated to the MS, the network can use this PDCH for transmitting CS paging messages to the MS.
Network Operation Mode II

Network operation mode II does not support the paging coordination on the CN. All paging messages are transmitted on the PCH. Therefore, the MS needs to monitor only the PCH. Even if an MS is assigned the PDCH, it monitors CS paging messages still on the PCH.
Network Operation Mode III

Network operation mode III does not support the paging coordination on the CN. All CS paging messages are transmitted on the PCH. If a cell is configured with the PCCCH, PS paging messages are transmitted on the PPCH, and the MS needs to monitor both the PCH and the PPCH. Otherwise, PS paging messages are transmitted on the PCH. Table 2-108 lists the channels on which CS and PS paging messages are transmitted in different network operation modes. Table 2-108 Paging channels in different network operation modes Network Operation Mode I CS Paging Message PS Paging Message Paging Coordination Required
PPCH PCH PACCH
PPCH PCH Not required PCH PPCH PCH
II III
PCH PCH PCH
Not required Not required
The network operation mode is specified by the parameter Network Operation Mode. Usually, the GPRS network is not configured with the Gs interface or PCCCH, and therefore Network Operation Mode is set to Network Operation Mode II. For the CS/PS paging procedures in different network operation modes, see section 2.43.3.3.5 Paging.
?.5. Packet System Information

System information mainly includes the parameters required by the MSs in a cell when accessing the network. If the cell supports GPRS, SI13 is broadcast on the BCCH. If the cell does not support GPRS, SI13 is not broadcast on the BCCH. The PBCCH can be condigured for a cell as required. SI13 includes information about whether the PBCCH is configured. The PBCCH is mainly used to broadcast GPRS PSI. The types of PSI are as follows: l PSI1: including cell selection parameters, PRACH control parameters, power control parameters, and control channel description
Issue 08 (2011-09-30)
l l l l
PSI2: including reference frequencies, cell allocations, GPRS mobile allocations, and PCCCH description PSI3: including BCCH allocations for neighboring cells and cell selection parameters for serving cells and non-serving cells PSI3bis: including BCCH allocations for neighboring cells and cell selection parameters for non-serving cells PSI13: same as SI13 broadcast on the BCCH, including access-related information specific to GPRS cells
PSI1 to PSI3 can be broadcast on the PBCCH or PACCH. PSI13 can be broadcast on only the PACCH. When the PBCCH is available in the cell, PSI13 is not broadcast on the PACCH, but PSI1 is broadcast periodically on the PACCH. When no PBCCH is available in the cell, only PSI13 is broadcast periodically on the PACCH.
2.43.3.3 System Procedures

?.1. Packet Access
Huawei BSC supports the following MS types: Class A MS: indicates the type of MS that can simultaneously perform GPRS and IMSI Attach, and the MS can simultaneously perform GPRS and CS services. Class B MS: indicates the type of MS that can simultaneously perform GPRS and IMSI Attach, but the MS can perform only one type of service at a time. Class C MS: indicates the type of MS that can access only the GSM or GPRS network at a certain time. If the MS needs to support both GPRS and CS services, the services can be only switched over manually and cannot be performed simultaneously. When the MS needs to transmit data, it initiates packet access at the RLC/MAC layer. Based on the service types and the MS capability, the packet access is classified into the following types: l l One-phase packet access Two-phase packet access or a single block packet access
The differences between these access types are as follows: l l For one-phase packet access, the MS is assigned radio resources, such as the TFI, USF, and radio block position list, at a time. For two-phase packet access or a single block packet access, the MS is assigned only one radio block at the first time. After sending a Packet Resource Request message carried by the radio block, the MS is assigned radio resources for the second time. By using the allocated radio resources, such as the TFI, USF, and radio block position list, the MS can start sending data. The resource assignment at the second time is controlled by T3168.
For different types of PS services, the MS uses different packet access modes. Assume that the GPRS MS accesses the network from the CCCH. Then, the packet access modes are described as follows:
If the purpose of packet access is to send user data and the requested RLC mode is unacknowledged mode, the MS requests a single block packet access and attempts a twophase packet access. If the purpose of packet access is to send user data and the requested RLC mode is acknowledged mode, the MS requests a one-phase packet access or a single block packet access. If the purpose of packet access is to send a page response or cell update message or for any other GMM/SM procedure, the MS requests a one-phase packet access. If the purpose of packet access is to send an MR, the MS requests a single block packet access.
l l
The procedure of packet access for EGPRS MSs from the CCCH is controlled by Support 11BIT EGPRS Access. For the detailed procedure, see 2.41 GPRS/EGPRS Connection Control and Transfer. The Packet Channel Request message is an 8-bit or 11-bit access burst, which carries a small amount of information. The number of access burst bits is specified by the parameter Access Burst Type. The 8-bit access burst is recommended because some MSs do not support the 11bit access burst. The Packet Resource Request message is an RLC/MAC signaling packet coded in CS-1. This message carries more information than the Packet Channel Request message. The information includes the temporary logical link identity (TLLI), multislot capability of the MS, and radio priority. This helps resources to the MS. The capability of a cell to support packet access is specified by the parameter Packet Access Priority.
?.2. Radio Resource Allocation
MS Multislot Capability
The MS multislot classes are 1- to 45. The number of PDCHs that can be used by the MSs varies with the multislot classes. For details about the MS on the multislot classes, see the 3GPP TS 45.002 specification. When allocating radio resources to the MS, the BSC must take into account the amount of data to be transmitted by the MS, grade of service (GoS), and available radio channels so that the multislot capability requirement of the MS can be met and radio resources can be fully used. The BSC supports MS high multislot class (HMC) channel allocation. The BSC can allocate a maximum of five uplink or downlink channels to the MS with multislot classes 30 to 33. A maximum of six uplink and downlink channels can be allocated to an MS at the same time. For example, if five timeslots are used in the downlink, only one timeslot can be used in the uplink. For an MS with multislot classes 32- to33, the extended dynamic allocation (EDA) function must be used if the MS requires more than three channels in the uplink. For MSs with multislot classes 34- to45, the BSC maps them to low multislot class capabilities or multislot classes 30- to33, depending on whether the MS supports HMC. The BSC defines three types of preferred services: downlink preferred service, uplink preferred service, and neutral service. If the multislot capability requirement can be met, as many downlink channels as possible should be allocated to the downlink preferred service such as downloading service, and as many uplink channels as possible should be allocated to the uplink preferred service such as uploading service. For the neutral service with the balanced traffic volumes in the uplink and downlink such as ping service, two timeslots are allocated in the uplink if possible.
MAC Mode
The MAC layer defines and allocates the logical channels on the Um interface so that these channels can be shared by several MSs. It also maps the LLC frames to the physical channels. When several MSs attempt to send packet data simultaneously, the MAC layer performs arbitration and provides the contention avoidance, detection, and recovery procedures. The MAC layer also allows an MS to occupy different timeslots of several physical channels. The BSC supports two MAC modes: dynamic allocation and extended dynamic allocation. Dynamic allocation is generally used for the downlink preferred service or neutral service. Extended dynamic allocation is used for the uplink preferred service to increase the uplink throughput. In dynamic allocation mode, the network multiplexes the channel resources of the uplink radio blocks using the Uplink State Flag (USF) of the downlink radio blocks. The BSC supports USF granularity 1 and default USF granularity 4. Only USF granularity 1 is used when the parameter Support USF Granularity 4 Switch is set to Not Support. l l When the BSC uses USF granularity 1, the MS sends an RLC/MAC block in the next radio block period upon detecting an assigned USF value. When the BSC uses USF granularity 4, the MS sends an RLC/MAC block in the next radio block period upon detecting an assigned USF value. If the downlink EGPRS MS and the uplink GPRS MS are multiplexed on the same PDCH, USF granularity 4 can be used to increase the downlink throughput.
In extended dynamic allocation mode, the packet assignment message contains an assigned PDCH list and USF values corresponding to the PDCHs. If the resources allocated by the network do not allow the MS to listen to the USF values on all the assigned PDCHs, the MS listens to the USF values in the following ways: l When the MS receives a USF value in an RLC/MAC block on a PDCH, the MS regards that the related RLC/MAC block on each PDCH following this PDCH in the list is allocated to the MS. Therefore, when allocating an RLC/MAC block on a PDCH to the MS, the network allocates the related RLC/MAC block on each PDCH following this PDCH in the list to the MS. For example, the network allocates a list of timeslots 1, 2, and 3 to the MS. If a USF value is detected in an RLC/MAC block on timeslot 1, the RLC/MAC blocks on timeslots 1, 2, and 3 are allocated to the MS. If a USF value is detected in an RLC/MAC block on timeslot 2, the RLC/MAC blocks on timeslots 2 and 3 are allocated to the MS. In an RLC/MAC block period of data transfer, the MS must listen to the USF values on all the PDCHs from the header to the current PDCH (inclusive) in the PDCH list. For example, if the list contains PDCHs 1, 2, and 3 and the RLC/MAC blocks are being transferred on PDCHs 2 and 3, the MS must listen to the USF values on PDCHs 1 and 2. If the RLC/MAC blocks are being transferred on PDCH 3, the MS must listen to the USF values on PDCHs 1, 2, and 3.
?.3. TBF Resource Assignment

When the network or MS requests to establish a TBF for data transmission, the GSM/GPRS network assigns channels for the TBF or rejects the request based on available network resources and the MS multislot capability. The TBF resource assignment principles are as follows:
Issue 08 (2011-09-30)
603
The BSC allocates TBF resources on the CCCHs, PACCHs, or PCCCHs.The TBF resource assignment is classified into uplink assignment and downlink assignment based on the data transmission direction. In response to the request for establishing a TBF for uplink data transmission from the MS, the BSC sends an Immediate Assignment message on the CCCH or a Packet Uplink Assignment message on the PCCCH to allocate resources to the MS. In response to the request for establishing an uplink TBF during downlink data transmission, the BSC sends a Packet Uplink Assignment message on the PACCH to allocate resources to the MS. Then, the MS transmits data on the allocate channel. In response to the request for establishing a TBF for downlink data transmission, the BSC sends an Immediate Assignment message on the CCCH or a Packet Downlink Assignment message on the PCCCH to allocate resources to the MS. When the MS is transmitting uplink TBF data or during the period specified by T3192, the network must establish a downlink TBF for data transmission. The BSC can send a Packet Downlink Assignment message on the PACCH to allocate resources to the MS. Then, the MS transmits data on the allocate channel. The BSC may reject a request for TBF establishment because of insufficient channel resources or other reasons. The BSC assigns resources on different channels based on the CCCH or PCCCH configuration. In addition, the BSC can perform different assignments such as single block assignment and packet resource assignment based on different access requests, such as Two-Phase Access, One-Phase Access, and Single Block Request.
l l
The BSC supports the following assignment modes. For details, see 2.41 GPRS/EGPRS Connection Control and Transfer. l l l l l Uplink packet resource assignment on the PACCH Downlink packet resource assignment on the PACCH Simultaneous uplink and downlink packet resource assignments on the PACCH Uplink immediate assignment for TBF establishment on the CCCH Downlink immediate assignment for TBF establishment on the CCCH
?.4. EGPRS Link Quality Control

Link quality control enables the system to adapt to the radio environment dynamically by changing the link modulation and coding schemes during data transmission, improving the link quality. EGPRS adopts a set of high-efficiency link quality control algorithms. It defines two link quality control modes: link adaptation (LA) and incremental redundancy (IR). The link quality control mode is set by the parameter Link Quality Control Mode. For the cells where the signal quality on the Um interface is good, this parameter is set to LA. For details on link quality control algorithms, see 2.42 GPRS/EGPRS Link Quality Control.
Basic Principle of LA
In LA mode, the sender selects the best modulation and coding schemes according to the actual radio environment, and the receiver does not need to buffer the received error data blocks.
Basic Principle of IR
In IR mode, the sender uses a coding scheme with high rates but weak data protection for initial data transmission. If the data is received erroneously, the sender retransmits the data by using a different puncturing scheme. The receiver combines the new data with the previously received data and then performs decoding. This process is repeated until the decoding is successful. During uplink data transmission, the system instructs the MS to use the IR mode by including RESEGMENT=0 (segmentation forbidden) in a packet uplink resource assignment message or uplink packet acknowledgment message by default. In IR mode, the receiver should have sufficient memory to save historical information. If the memory is insufficient, the system notifies the MS of memory insufficiency by including RESEGMENT=1 in an UPLINK ACK/ NACK message. During downlink data transmission, if the MS memory is insufficient, the MS sends "MS OUT OF MEMORY" to the network through a downlink ACK/NACK message. Then, the network changes the control mode to LA.
?.5. Paging
In the GPRS/GSM system, paging consists of PS paging and CS paging.
PS Paging
In the GPRS/GSM system, the PS paging procedure is as follows: 1. When the network needs to transmit data to an MS, the SGSN initiates a PS paging to locate the MS. The Packet Paging Request message is sent to the BSC over the Gb interface. l If the PCCCH is configured in the BSC, the Packet Paging Request message is sent on the PPCH. l If no PCCCH is configured in the BSC, the Packet Paging Request message is sent on the PCH. l If the cell supports DTM and the paged MS is in dedicated mode, the BSC can send the PACKET NOTIFICATION message on the DCCH. For details, see 2.27 DTM. 2. After receiving the Packet Paging Request message, the MS initiates the uplink TBF establishment procedure. Then, the MS sends a paging response packet to the BSC over the Um interface. The BSC forwards the paging response packet to the SGSN. After receiving the paging response packet, the SGSN processes it and then starts transmitting downlink data.
Paging Co-ordination
In the GSM network, when a CS call reaches the MSC that the MS belongs to, the MSC determines the registered location area of the MS. Then, the MSC sends the CS paging message to all the BSCs in this location area. If the Gs interface is configured between the SGSN and the MSC and the GPRS/GSM network operates in network operation mode I, the CS paging messages of GSM services can be transmitted on GPRS packet channels. If the MS is attached to the GPRS network, the CS paging messages are sent from the MSC to the SGSN over the Gs interface and then to the PCU over the Gb interface. Then, the PCU determines the channel for sending the paging message according to the following conditions:
l l l
If the MS is assigned the PDCH, the paging message is sent on the PACCH. If no PDCH is assigned to the MS but the PCCCH is configured, the paging message is sent on the PPCH. If no PDCH is assigned to the MS and no PCCCH is configured in the system, the PCU forwards the paging message to the BSC. Then, the BSC sends the paging message to the MS on the PCH.
If the Gs interface is not configured, the CS paging message can be sent only on the PCH. The MS in packet transfer mode, however, listens to messages only on the PACCH. Therefore, the MS does not respond to the CS paging messages on the PCH. Huawei BSC supports the BSS paging coordination function. BSS Paging Co-ordination in basic GPRS attributes and A Interface Paging Co-ordination Switch in basic BSC attributes must be enabled at the same time. After receiving a CS paging message over the A or Gb interface, the BSC checks whether the GPRS service is ongoing on the MS based on the IMSI of the MS in the paging message. If the MS is in packet transfer mode, the BSC sends the paging message to the MS on the PACCH. If the MS is in idle mode, the BSC sends the paging message to the MS on the PCH. In BSS paging coordination mode, the BSC determines whether CS paging messages are sent on the PACCH. In GPRS-capable networks, the paging success rate increases when BSS paging coordination is enabled. After receiving a CS paging message, the MS accesses the network on the RACH to establish a circuit connection. If necessary, the MS initiates the GPRS suspend procedure to suspend the ongoing GPRS service. After the circuit connection is released, the MS resumes the GPRS service.
NOTE
When external PCUs are used, BSS paging coordination is not supported.
?.6. Timing Advance

The GPRS timing advance (TA) procedure is used to extract the correct TA value so that the network can correctly receive the radio blocks from MSs The GPRS TA contains the following two parts: l l Initial TA estimation Continuous TA update
Initial TA Estimation
The BSC estimates an initial TA value based on a single access burst requesting a packet channel. Then, the BSC sends the estimated TA value to the MS using a Packet Uplink Assignment or a Packet Downlink Assignment message. Before the TA value is updated, the MS transmits data in the uplink based on the initial TA.
Continuous TA Update
The MS in packet transfer mode must update the TA value continuously. The TA value is transmitted on the packet timing advance control channel (PTCCH) that is allocated to an MS.
l l
For uplink packet transfer, the BSC sends a Packet Uplink Assignment message to the MS to assign the timing advance index (TAI). For downlink packet transfer, the BSC sends a Packet Downlink Assignment message to the MS to assign the TAI.
TAI specifies the PTCCH to be used by the MS. In the uplink, the MS sends access bursts on the PTCCH specified by the TAI. The BTS extracts the TA value from the received access bursts. The BTS analyzes the TA value and determines a new TA value for each MS that performs continuous TA update on the PDCH. The new TA value is sent to the MS through a downlink signaling message on the PTCCH/D. The BSC can also send the new TA value to the MS using a Packet Power Control/Timing Advance or a Packet Uplink ACK/NACK message on the PACCH.
?.7. Flow Control
Uplink Flow Control

If excessive MSs apply for GPRS resources in a cell or BSC at the same time, the GPRS resources may be insufficient and the uplink may be congested. The uplink flow control manages service requests (including paging response messages) that are initiated by MSs and to delay the responses to these service requests. The uplink service requests can be controlled by controlling random access requests on the PRACH/RACH. The responses to the service requests initiated by MSs can be delayed using the queue indication procedure. To reduce random access requests on the PRACH/RACH, you can extend the random access retransmission interval or prohibit the MSs with certain access classes. Extending the random access retransmission interval affects the response speed and service quality of the system but it helps improve the system capacity. Therefore, it can be used in some suitable situations. Prohibiting the access of MSs with certain classes may affect the system service quality. In addition, Huawei BSC handles overload in a policy based on the service and operation aspects. For different types of overload, Huawei BSC adopts related handling policies. For example, the BSC reduces the load based on priorities in the following way to solve the radio resource overload problem: l l Delays the response to the access request with a low QoS requirement or rejects the access request with a low QoS requirement. Releases the TBF of the MS with a low QoS requirement.
Downlink Flow Control

The BSC supports the downlink flow control of the BVC and MS. It periodically reports associated parameters to the SGSN. The physical media and transmission protocols on the Gb interface are different from those on the Um interface. Therefore, the two interfaces have different data transmission rates. The data transmission rate on the Gb interface is greater than that on the Um interface. In addition, the downlink data rate on the Um interface is subject to various factors, such as the MS multislot capability, radio signal quality, and available radio channels in the cell. Therefore, the data transmission rate is unstable and the downlink flow control is required.
When a cell is in the stable state, the BSC initiates the flow control procedure. Based on the conditions of the radio packet channels in the cell, the BSC periodically reports the bucket size and bucket rate of the cell to the SGSN. In addition, the BSC reports the bucket size and bucket rate of the MS based on the radio resource usage of the MS. The bucket rate refers to the data transmission rate. Based on the reported parameters, the SGSN adjusts the downlink data rates of the cell and each MS to implement downlink flow control. l l The bucket of a cell refers to the maximum volume of packet data that can be stored in the cell. The volume varies with the number of packet channels in the cell. The bucket of an MS refers to the maximum volume of packet data that can be stored in the MS. The volume varies with the number of packet channels assigned to the MS.
?.8. Packet QoS

Packet QoS refers to GPRS/EGPRS QoS, that is, the qualities of GPRS/EGPRS services on the GSM EDGE Radio Access Network (GERAN). The requirements for packet QoS are defined by QoS attributes, including the traffic class, transfer delay, maximum bit rate (MBR), guaranteed bit rate (GBR), traffic handling priority (THP), allocation/retention priority (ARP), and reliability. 3GPP TS 23.107 defines four traffic classes: conversational class, streaming class, interactive class, and background class. Huawei BSC supports the last three classes and provides different QoS for different traffic classes and PS service users. Typical streaming services include real-time streaming video and real-time streaming audio. The streaming class has high requirements for the time sequence and delay variation between information entities (for example, packets) in the stream but a low requirement for transfer delay. Interactive services are traditional data services. Typical interactive services include web browsing, database retrieval, and server access. The interactive class requires a timely response to the request. This class has a certain requirement for the round-trip time (RTT). In addition, this class requires high data accuracy and low bit error rates. Background services are also traditional data services. Typical background services include file download and email. The background class is insensitive to delay, but it requires high data accuracy and low bit error rates. According to the R99 specifications, the BSS and the SGSN can negotiate QoS information through the packet flow management (PFM) procedure during the activation of the MS Packet Data Protocol (PDP) context.
GBR QoS
For a streaming service, such as the push to talk (PoC) service, the BSC dynamically allocates Um resources to the MS based on the radio environment and ensures that the bandwidth is not lower than the GBR. To ensure the real-time performance of the PoC service, the parameters Min. GBR for POC Service and Max. GBR for POC Service specify the required bandwidth, and the parameter Transmission Delay of POC Service specifies the transfer delay. When the Um resources are insufficient, the BSC initiates a packet flow context (PFC) modification procedure. The parameter Support GBR QoS determines whether to support GBR QoS.
Issue 08 (2011-09-30)
608
User QoS
Whether different QoS can be provided for users of different priorities is specified by the parameter Support QoS Optimize. For interactive, background, and Best Effort (BE) services, the BSC sets the radio block budget weight based on the traffic class, ARP, and THP, (THP is considered only for interactive services). The budget weight determines the number of radio blocks that can be allocated to a TBF.BE services refer to the service of which the QoS attributes are not obtained from the BSC or the service of which the traffic class is unknown. The radio resource allocation and scheduling of this type of service are performed on the basis of the best effort policy. The configured radio block budget weight reflects the traffic class priority and the user priority. High-priority traffic classes or users can obtain more radio resources. For more QoS information, see 2.44 GPRS/EGPRS QoS.
?.9. Packet Power Control

The BSC performs uplink open loop control for MS PS services. On the assumption that the uplink and the downlink have the same path loss, the uplink open loop power control enables the MS to adjust the output power based on the receive level. For all the PDCHs allocated to the GPRS/EGPRS MS, the output power is calculated as follows: PCH = min (0 - CH - x (C + 48), PMAX) Where, CH is sent through the RLC/MAC radio block to the MS. For details, see 3GPP TS 44.060. By default, CH is set to the value of GAMMA. 0 is 39 dBm for GSM850 and GSM900, and 36 dBm for DCS1800 and PCS1900. is a system parameter. It is broadcast on the PBCCH or sent through an RLC/MAC control message to the MS. For details, see 3GPP TS 44.018 and 3GPP TS 44.060. By default, is set to the value of ALPHA. C is the filtered receive signal strength. PMAX is the maximum transmit power of the MS permitted in the cell. It can be specified by the cell parameter MS_TXPWR_MAX_CCH. The channel on which the MS measures the receive level for uplink power control is specified by PC_MEAS_CHAN. PC_MEAS_CHAN can be set to BCCH or PDCH.
?.10. Cell Reselection Control
Network Control Modes

There are three GPRS network control modes: network control 0 (NC0), network control 1 (NC1), and network control 2 (NC2). These modes are described as follows: l l
Issue 08 (2011-09-30)
In NC0 mode, the MS performs autonomous cell reselection without sending MRs to the network. In NC1 mode, the MS performs autonomous cell reselection and sends MRs to the network.
In NC2 mode, the network controls cell reselection, and the MS sends MRs to the network.
The network control mode is specified by the parameter Network Control Mode.
MS-Controlled Cell Reselection

The MS periodically measures the downlink receive levels of all the BCCH TRXs of the serving cell and its neighboring cells. In addition, the MS calculates the value of C2 if no PBCCH is configured in the serving cell or calculates the value of C31/C32 if the PBCCH is configured in the serving cell. Based on the calculated value, the MS decides whether to reselect a new serving cell. The cell reselection algorithm enables the MS to be served by a better cell.
Network-Assisted Cell Reselection

Network-assisted cell reselection is also known as network-assisted cell change (NACC). If both the BSC and the MS support NACC, the MS initiates a cell change notification (CCN) procedure, and the BSC sends the system information about the neighboring cells to the MS before the cell reselection. The NACC function accelerates the cell reselection and shortens the service disruption time during the cell reselection. To enable this function, set the cell parameter Support NACC to Yes. For details, see 2.59 NACC.
Network-Controlled Cell Reselection

If the BSC supports NC2, the MS periodically sends MRs to the BSC based on the parameters in the system information broadcast in the cell. After considering factors such as MRs and neighboring cell load, the BSC sends a cell change command to the MS if all conditions are met, instructing the MS to attach an appropriate cell. To enable this function, set the cell parameter Support NC2 to Yes. For details, see 2.60 NC2.
?.11. Idle Timeslot Assignment

The data rate of each timeslot on the Abis interface is 16 kbit/s, but the peak data rate of an EDGE traffic channel is 59.2 kbit/s. Therefore, multiple 16 kbit/s timeslots on the Abis interface need to be mapped onto one traffic channel. Among these timeslots, the first allocated timeslot is called the primary link and the other timeslots are called secondary links. Abis idle timeslots are used as 16 kbit/s timeslots of secondary links for PS services. The Abis idle timeslots of the same BTS can be assigned to any PDCH on any TRX in the same cabinet group, which is specified by Cabinet Group No.. The number of Abis idle timeslots is specified by Idle TS Count. In GPRS, each PDCH requires one additional idle timeslot in the CS-3/CS-4 coding scheme. In EDGE, each PDCH requires a maximum of three additional idle timeslots. In GPRS/EGPRS, different coding schemes require different numbers of Abis links, as shown in Table 2-109. Table 2-109 Coding schemes and required number of Abis links Coding Scheme CS-1 and CS-2 CS-3 to CS-5 MCS-1 and MCS-2
Issue 08 (2011-09-30)
Number of Required Abis Links 1 2 1

610
Coding Scheme MCS-3 to MCS-6 MCS-7 MCS-8 and MCS-9
Number of Required Abis Links 2 3 4
NOTE
l If Service Type on the Abis interface is set to IP or HDLC, no idle timeslot is available for assignment. l If Flex Abis is enabled for the BTS and the CS traffic is light, idle timeslots may not be configured and EDGE services can still operate properly. l If Flex Abis is enabled for the BTS and the CS traffic is heavy, you are advised to configure idle timeslots to prevent the long-time EDGE service failure.
2.43.4 Parameters
This chapter describes the parameters related to GPRS/EGPRS overview. For the meaning of each parameter, see Table 2-110. For the default value, value ranges, and MML commands of each parameter, see Table 2-111. Table 2-110 Parameter description (1) Parameter Frame Relay Protocol Type The Identifier of Data Link Connection Subnet Protocol Type Description Protocol type of the trunk frame. The setting of this parameter must be consistent with the setting at the SGSN side. ID of the data link connection of the NSVC. It is an interworking parameter which must be consistent on the BSC and the peer. Subnet protocol type Configuration mode of the IP subnetwork. Static configuration: fixed local NSVL and remote NSVL parameters through manual configuration; Dynamic configuration: the NSVL parameter obtained through negotiation between the BSC and the SGSN after the local NSVL and SGSN service point are configured manually. Server IP address used on the SGSN side in the IP subnet dynamic configuration procedure Identifies a unique NSE. Timeslot power attenuation level of the EDGE TRX in 8PSK. The attenuation level ranges from 0 to 50, each of which corresponds to an attenuation of 0.2 dB. When the EDGE TRX sends signals in 8PSK, the transmit power must be lower than the mean power in GMSK.
Subnetwork Configure Mode Server IP NSE Identifier Cell 8PSK Power Attenuation Grade
Issue 08 (2011-09-30)
611
Parameter
Description Default coding scheme of the uplink GPRS link. If the uplink adopts the dynamic adjustment coding scheme, this parameter can be used to set the coding scheme for transmission during initial access. If the uplink uses the fixed coding scheme, the TBF uses the fixed coding scheme. Coding scheme of the default GPRS downlink. Dynamic adjustment coding: the coding scheme used during initial access transmission. If the downlink uses the fixed coding scheme, the TBF uses the fixed coding scheme. Adjustment mode of the uplink GPRS link coding scheme. If the fixed coding scheme is used, this parameter is a value ranging from CS1 to CS4. If the dynamic coding scheme is used, this parameter is set to UNFIXED. Adjustment mode of the downlink GPRS link coding scheme. If the fixed coding scheme is used, this parameter is set to a value ranging from CS1 to CS4. If the dynamic coding scheme is used, this parameter is set to UNFIXED. Retransmission threshold when the coding mode of the uplink TBF is changed from CS1 to CS2. When the retransmission rate of the uplink TBF is less than or equal to this threshold, the coding mode of the uplink TBF is changed from CS1 to CS2. Retransmission threshold when the coding mode of the uplink TBF is changed from CS2 to CS3. When the retransmission rate of the uplink TBF is less than or equal to this threshold, the coding mode of the uplink TBF is changed from CS2 to CS3. Retransmission threshold when the coding mode of the uplink TBF is changed from CS3 to CS4. When the retransmission rate of the uplink TBF is less than or equal to this threshold, the coding mode of the uplink TBF is changed from CS3 to CS4. Retransmission threshold when the coding mode of the uplink TBF is changed from CS2 to CS1. When the retransmission rate of the uplink TBF is greater than or equal to this threshold, the coding mode of the uplink TBF is changed from CS2 to CS1. Retransmission threshold when the coding mode of the uplink TBF is changed from CS3 to CS2. When the retransmission rate of the uplink TBF is greater than or equal to this threshold, the coding mode of the uplink TBF is changed from CS3 to CS2. Retransmission threshold when the coding mode of the uplink TBF is changed from CS4 to CS3. When the retransmission rate of the uplink TBF is greater than or equal to this threshold, the coding mode of the uplink TBF is changed from CS4 to CS3. Retransmission threshold when the coding mode of the downlink TBF is changed from CS1 to CS2. When the TBF retransmission rate is less than or equals to this value, the coding mode of the TBF is changed from CS1 to CS2.
Uplink Default CS Type
Downlink Default CS Type Uplink Fixed CS Type
Downlink Fixed CS Type Uplink TBF Threshold from CS1 to CS2 Uplink TBF Threshold from CS2 to CS3 Uplink TBF Threshold from CS3 to CS4 Uplink TBF Threshold from CS2 to CS1 Uplink TBF Threshold from CS3 to CS2 Uplink TBF Threshold from CS4 to CS3 Downlink TBF Threshold from CS1 to CS2
Issue 08 (2011-09-30)
612
Parameter Downlink TBF Threshold from CS2 to CS3 Downlink TBF Threshold from CS3 to CS4 Downlink TBF Threshold from CS2 to CS1 Downlink TBF Threshold from CS3 to CS2 Downlink TBF Threshold from CS4 to CS3
Description Retransmission threshold when the coding mode of the TBF is changed from CS2 to CS3. When the downlink TBF retransmission rate is less than or equals to CS2 to CS1, the coding mode of the TBF is changed from CS2 to CS3. Retransmission threshold when the coding mode of the downlink TBF is changed from CS3 to CS4. When the downlink TBF retransmission rate is less than or equals to this value, the coding mode of the downlink TBF is changed from CS3 to CS4. Retransmission threshold when the coding mode of the downlink TBF is changed from CS2 to CS1. When the downlink TBF retransmission rate is greater than or equals to this value, the coding mode of the TBF is changed from CS2 to CS1. Retransmission threshold when the coding mode of the TBF is changed from CS3 to CS2. When the TBF retransmission rate is greater than or equals to this value, the coding mode of the TBF is changed from CS3 to CS2. Retransmission threshold when the coding mode of the downlink TBF is changed from CS4 to CS3. When the downlink TBF Retransmission rate is greater than or equals to this value, the coding mode of the TBF is changed from CS4 to CS3. Default coding scheme of the uplink EDGE link. If the uplink adopts the dynamic adjustment coding scheme, this parameter can be used to set the coding scheme for transmission during initial access. If the uplink uses the fixed coding scheme, the TBF uses the fixed coding scheme. Default coding scheme of the downlink EDGE link. If the downlink adopts the dynamic adjustment coding scheme, this parameter can be used to set the coding scheme for transmission during initial access. If the downlink uses the fixed coding scheme, the TBF uses the fixed coding scheme. Coding scheme of the uplink EDGE link. If the uplink uses the fixed coding scheme, this parameter is set to a value ranging from MCS1 to MCS9. If the uplink uses the dynamic adjustment coding scheme, this parameter is set to UNFIXED. Coding scheme of the downlink EDGE link. If the downlink uses the fixed coding scheme, this parameter is set to a value ranging from MCS1 to MCS9. If the downlink uses the dynamic adjustment coding scheme, this parameter is set to UNFIXED. Average period for sending the measurement report over the EGPRS channel Channel type of the timeslot on the TRX. The channel type of timeslot 0 must not be set, because the combined BCCH is configured by default. The channel type of other timeslots can be set to full-rate TCH or halfrate TCH.
Downlink Fixed MCS Type Bep Period
Channel Type
Issue 08 (2011-09-30)
613
Parameter
Description EGPRS priority type of the channel If this parameter is set to GPRS, the EDGE MSs cannot use this channel. If this parameter is set to EGPRSNORCH, the GPRS and EDGE MSs can use this channel at the same priority. If this parameter is set to EGPRSPRICH, the EDGE MSs have the priority to use this channel. If this parameter is set to EGPRSSPECH, only the EDGE MSs can use this channel. If this parameter is set to NONGPRS, this parameter becomes invalid. Switch specifying whether to allow the downlink EGPRS TBF and the uplink GPRS TBF to share the same channel. On: allow the downlink EGPRS TBF and the uplink GPRS TBF to share the same channel; Off: prohibit the downlink EGPRS TBF and the uplink GPRS TBF sharing the same channel. Maximum value of the PDCH ratio in a cell. The number of available TCHs and PDCHs in a cell is set to a fixed value. The PDCH ratio is: Number of available PDCHs/(Number of available TCHFs + Number of available static PDCHs). This parameter is used to restrict the PDCH ratio. PDCH uplink multiplex threshold, indicating the maximum TBFs on the uplink PDCH (parameter value/10). We recommand that the value of "Uplink Multiplex Threshold of Dynamic Channel Conversion" should be less than "PDCH Uplink Multiplex Threshold" for triggering converting dynamic channel in time and reducing PDCH multiplex. PDCH downlink multiplex threshold, Indicating the maximum TBFs on the downlink PDCH (parameter value/10).We recommand that the value of "Downlink Multiplex Threshold of Dynamic Channel Conversion" should be less than "PDCH Downlink Multiplex Threshold" for triggering converting dynamic channel in time and reducing PDCH multiplex. Uplink multiplex threshold of dynamic channel conversion. When the subscriber number on the channel reaches the value (threshold/10), the dynamic channel conversion application is triggered. We recommand that the value of "Uplink Multiplex Threshold of Dynamic Channel Conversion" should be less than "PDCH Uplink Multiplex Threshold" for triggering converting dynamic channel in time and reducing PDCH multiplex. Downlink multiplex threshold of dynamic channel conversion. When the subscriber number on the channel reaches the value (threshold/10), the dynamic channel conversion is triggered. We recommand that the value of "Downlink Multiplex Threshold of Dynamic Channel Conversion" should be less than "PDCH Downlink Multiplex Threshold" for triggering converting dynamic channel in time and reducing PDCH multiplex. Mode of preempting the dynamic channel for the CS domain and PS domain. Only the channel configured in the TCH/F mode can be preempted. "Preempt all dynamic TCHFs" indicates the circuit domain can preempt all the dynamic channels. "No preempt of CCHs" indicates the circuit domain can preempt all the dynamic channels except the CCHs. "No preempt of service TCHF" indicates the circuit domain cannot preempt all the dynamic channels of bearer services.
Allow E Down G Up Switch Maximum Rate Threshold of PDCHs in a Cell
PDCH Uplink Multiplex Threshold
PDCH Downlink Multiplex Threshold
Uplink Multiplex Threshold of Dynamic Channel Conversion Downlink Multiplex Threshold of Dynamic Channel Conversion
Level of Preempting Dynamic Channel

Issue 08 (2011-09-30)
Parameter Reservation Threshold of Dynamic Channel Conversion
Description
Number of full-rate TCHs reserved for the CS domain. This parameter is valid only when "Level of Preempting Dynamic Channel" is set to LEVEL1 or LEVEL2. This parameter is related to the paging channel of the system. There are three network operation modes: network operation mode I, network operation mode II, and network operation mode III. Network operation mode I is used when the system is configured with the Gs interface. Network operation mode II is used when the system is not configured with the Gs interface and the PCCCH is not configured. Network operation mode III is used when the system is not configured with the Gs interface and the PCCCH is configured. T3168 is used to set the maximum duration for the MS to wait for the uplink assignment message. After the MS originates the uplink TBF setup request by sending the packet resource request or the channel request in the packet uplink acknowledge message, the timer T3168 is started to wait for the packet uplink assignment message on the network side. If the MS receives the packet uplink assignment message before T3168 expires, T3168 is reset. Otherwise, the MS originates the packet access request for four times. Then the MS regards this as the TBF setup failure. Whether to support the 11-bit EGPRS access request Access pulse type of the PRACH, uplink PTCCH and packet control acknowledge message of the MS. 8bit: 8 bit pulse access mode; 11bit: 11 bit pulse access mode. Access priority of the MS that is allowed to access the cell. The MS sends the packet channel request containing the 2-bit radio priority message. The priority of the 2-bit radio priority message ranges from 1 to 4 in descending order. During the MS access, the BSC compares the radio priority in the channel request with the parameter setting of the cell. If the radio priority equals to the parameter setting of the cell, the BSC sets up the TBF for the channel request.
T3168 Support 11BIT EGPRS Access Access Burst Type
Packet Access Priority Support USF Granularity 4 Switch
Whether to support USF granularity 4
Issue 08 (2011-09-30)
615
Parameter
Description Duration of releasing the TBF after the MS receives the last data block. When the MS receives the RLC data block containing the flag identifying the last data block and confirms that all the RLC data blocks in the TBF are received, the MS sends the packet downlink acknowledge message containing the last flag acknowledgement and the timer T3192 is started. If the timer T3192 expires, the MS releases the TBF related resources and starts monitoring the paging channel. During TBF releasing, if the MS is the half duplex mode and receives the packet uplink assignment, the MS responds this command. During TBF releasing, if the MS is the half duplex mode and receives no packet uplink assignment message, the MS enters the packet idle mode. If the MS is in the dual transmission mode, the MS enters the special mode. It is applicable to the radio transmission environment to improve the link quality. Link adaptation (LA) indicates adjusting the coding mode of the channel dynamically according to the transmission quality of the link. The link transmission quality is measured by the 8PSK MEAN BEP and 8PSK CV BEP in the Packet EGPRS Downlink Ack/Nack message sent by the MS. The network side determines the coding mode for data transmission according to the radio measurement report sent by the MS. The cell with the good transmission quality on the air interface is set to the LA mode. Increment redundancy (IR) mode requires the network side retransmit the data block with different punching codes and the MS store the historical error information. The data block is retransmitted through cooperated error correction function. With the IR mode, the transmission quality on the air interface of the cell can be improved. However, the MS must support this IR mode. The cell with the dissatisfied transmission quality on the air interface is set to the LR mode. Whether to support the paging function of the CS domain of the A interface. Yes: the MS can be called upon paging request on the A interface when handling the PS service; No: the MS cannot be called upon paging request on the A interface when handling the PS service. This parameter is valid only when the "A Interface Paging Co-ordination Switch" in "SET BSCPSSOFTPARA" is set to "Open". This parameter specifies whether to receive the CS paging request from A interface when the MS uses a PS service. This parameter is used to control the paging collaboration function of A interface of the entire BSC. This parameter specifies whether to forward the paging message of the A interface from the circuit domain to the PS domain . Minimum bandwidth of the POC service (push to talk over cellular). The transmission delay of the POC service must be relatively small. The network side must support the function of detecting the POC service type and reduce the delay through related processing to meet the POC service requirement. For the POC service received by the network side, GbrValue in the ABQP must be larger than the minimum bandwidth of the POC service.
T3192
Link Quality Control Mode
BSS Paging Coordination A Interface Paging Coordination Switch
Min. GBR for POC Service
Issue 08 (2011-09-30)
616
Parameter
Description Maximum bandwidth of the POC service (push to talk over cellular). The transmission delay of the POC service must be relatively small. The network side must support the function of detecting the POC service type and reduce the delay through related processing to meet the POC service requirement. For the POC service received by the network side, GbrValue in the ABQP must be lower than the maximum bandwidth of the POC service. Maximum transmission delay of the POC service (push to talk over cellular). The transmission delay of the POC service must be relatively small. The network side must support the function of detecting the POC service type and reduce the delay through related processing to meet the POC service requirement. For the POC service received by the network side, Transfer Delay in the ABQP must be lower than the transmission threshold of the POC service. Obtains the QoS parameter from the Aggregate BSS QoS Profile (ABQP) of packet flow context (PFC) when the MS and the network support the PFC; obtains the QoS parameter from the uplink request originated by the MS or the DL UNITDATA of the SGSN. GBR: guaranteed bit rate. Whether to support QoC optimization. The GSN equipment for the GPRS provides flexible QoS mechanisms for different subscribers. The QoS level is also set during subscription. The QoS control parameters include: service priority, reliability level, delay level, and data throughput level. During QoS negotiation, the MS can apply for one value for each QoS attribute. When receiving the request from the MS, the network must allocate a QoS level to each attribute for each QoS document. The network provides related resources for the negotiated QoS document. Expected signal receiving strength on the BTS side when GPRS dynamic power control is implemented It is used to perform open loop power control. Alpha parameter is used by the MS to calculate the output power PCH of the uplink PDCH. This parameter is used to set the reduced class of the Tx power of the MS, in correspondence with the path loss, when the GPRS dynamic power control is enabled.
Max. GBR for POC Service
Transmission Delay of POC Service
Support GBR QoS
Support QoS Optimize GAMMA
ALPHA
Issue 08 (2011-09-30)
617
Parameter
Description Maximum transmit power level of MSs. As one of the cell reselection parameters in system message 3, this parameter is used to control the transmit power of MSs. For details, see GSM Rec. 05.05. In a GSM900 cell, the maximum power control level of an MS ranges from 0 to 19, corresponding respectively to the following values (unit: dBm): 43, 41, 39, 37, 35, 33, 31, 29, 27, 25, 23, 21, 19, 17, 15, 13, 11, 9, 7, and 5.Generally, the maximum transmit power supported by an MS is level 5 (corresponding to 33 dBm). The minimum transmit power supported by an MS is level 19 (corresponding to 5 dBm). Other transmit power levels are reserved for high-power MSs. In a GSM1800 or GSM1900 cell, the maximum power control level of an MS ranges from 0 to 31, corresponding respectively to the following values (unit: dBm): 30, 28, 26, 24, 22, 20, 18, 16, 14, 12, 10, 8, 6, 4, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 36, 34, and 32. Generally, the maximum transmit power supported by an MS is level 0 (corresponding to 30 dBm). The minimum transmit power supported by an MS is level 15 (corresponding to 0 dBm). Other transmit power levels are reserved for high-power MSs. Channel used for the measured receiving power. It is used to set the measured receiving power level of the channel and control the power of the uplink. Network control mode for cell reselection of the MS. There are three modes. NC0: normal MS control. The MS shall perform autonomous cell re-selection. NC1: MS control with measurement reports. The MS shall send measurement reports to the network and the MS shall perform autonomous cell re-selection. NC2: network control. The MS shall send measurement reports to the network . The MS shall only perform autonomous cell re-selection when the reselection is triggered by a downlink signaling failure or a random access failure.When this parameter is set to NC2 and "Support NC2" in "SET GCELLGPRS" is set to "YES", the network side can control the cell reselection for the MS. Whether to support the network assisted cell change (NACC). The NACC is used in the network control modes NC0, NC1 or NC2. The NACC enables the network to notify the MS of the system information of the neighboring cell when the MS is in the packet transmission state. In this way, the MS can reselect a cell in a shorter time. Whether to support the network control 2 (NC2). The NC2 enables the network side to control the cell reselection for the MS when the MS reports the measurement report of the local cell and the neighboring cell.When this parameter is set to "YES" and "Network Control Mode" in "SET GCELLPSBASE" is set to "NC2", the network side can control the cell reselection for the MS. Number of the cabinet group where the idle timeslot is located. Number of idle timeslots. You can configure up to 128 idle timeslots for the BTS at a time. A BTS can be configured with up to 512 idle timeslots. Service bearer mode of the BTS
MS_TXPWR_M AX_CCH PC_MEAS_CH AN
Support NACC
Support NC2 Cabinet Group No. Idle TS Count Service Type

Issue 08 (2011-09-30)
Table 2-111 Parameter description (2) Paramete r Frame Relay Protocol Type The Identifier of Data Link Connectio n Default Value GUI Value Range Q933 (Q933), ANSI (Ansi) Actual Value Range Unit MML Comman d Impact
Q933
Q933, ANSI
None
ADD BC (Optional)
BC
None
16~1007 GB_OVE R_FR(Gb over FR), GB_OVE R_IP(Gb over IP) STATIC (Static), DYNAMI C (Dynamic)
16~1007
None
ADD NSVC (Mandator y)
NSVC
Subnet Protocol Type Subnetwor k Configure Mode
None
GB_OVE R_FR, GB_OVE R_IP
None
ADD NSE (Mandator y)
NSE
None
STATIC, DYNAMI C 0.0.0.0~25 5.255.255. 255
None
ADD NSE (Optional) ADD NSE (Mandator y)
NSE
Server IP
None
None
None
NSE
Issue 08 (2011-09-30)
619
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d ADD NSE (Mandator y) ADD NSVC (Mandator y) ADD NSVLLO CAL (Mandator y) ADD NSVLRE MOTE (Mandator y) ADD PTPBVC (Mandator y) BLK PTPBVC (Mandator y) SET GCELLB ASICPAR A (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional)
Impact
NSE Identifier Cell 8PSK Power Attenuatio n Grade Uplink Default CS Type Downlink Default CS Type
None
0~65534
0~65534
None
NSE
0~50 CS1(CS1), CS2(CS2), CS3(CS3), CS4(CS4) CS1(CS1), CS2(CS2), CS3(CS3), CS4(CS4)
0~50
None
Cell
CS1
CS1, CS2, CS3, CS4
None
Cell
CS2
CS1, CS2, CS3, CS4
None
Cell
Issue 08 (2011-09-30)
620
Paramete r
Default Value
GUI Value Range CS1(CS1), CS2(CS2), CS3(CS3), CS4(CS4), UNFIXE D (UNFIXE D) CS1(CS1), CS2(CS2), CS3(CS3), CS4(CS4), UNFIXE D (UNFIXE D)
Actual Value Range
Unit
MML Comman d
Impact
UNFIXE D
None
SET GCELLPS CS (Optional)
Cell
Downlink Fixed CS Type Uplink TBF Threshold from CS1 to CS2 Uplink TBF Threshold from CS2 to CS3 Uplink TBF Threshold from CS3 to CS4 Uplink TBF Threshold from CS2 to CS1 Uplink TBF Threshold from CS3 to CS2
UNFIXE D
None
SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional)
Cell
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
10
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
Issue 08 (2011-09-30)
621
Paramete r Uplink TBF Threshold from CS4 to CS3 Downlink TBF Threshold from CS1 to CS2 Downlink TBF Threshold from CS2 to CS3 Downlink TBF Threshold from CS3 to CS4 Downlink TBF Threshold from CS2 to CS1 Downlink TBF Threshold from CS3 to CS2 Downlink TBF Threshold from CS4 to CS3
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional) SET GCELLPS CS (Optional)
Impact
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
10
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
0~64
0~64
per cent
Cell
Issue 08 (2011-09-30)
622
Paramete r
Default Value
GUI Value Range MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), MCS7 (MCS7), MCS8 (MCS8), MCS9 (MCS9) MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), MCS7 (MCS7), MCS8 (MCS8), MCS9 (MCS9)
Actual Value Range
Unit
MML Comman d
Impact
MCS2
None
Cell
MCS6
None
Cell
Issue 08 (2011-09-30)
623
Paramete r
Default Value
GUI Value Range MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), MCS7 (MCS7), MCS8 (MCS8), MCS9 (MCS9), UNFIXE D (UNFIXE D) MCS1 (MCS1), MCS2 (MCS2), MCS3 (MCS3), MCS4 (MCS4), MCS5 (MCS5), MCS6 (MCS6), MCS7 (MCS7), MCS8 (MCS8), MCS9 (MCS9), UNFIXE D (UNFIXE D)
Actual Value Range
Unit
MML Comman d
Impact
UNFIXE D
None
Cell
UNFIXE D
None
Cell
Issue 08 (2011-09-30)
624
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLE GPRSPA RA (Optional)
Impact
Bep Period
0~10 FULLTC H (FULLTC H), HALFTC H (HALFTC H) GPRS (GPRS Channel), EGPRSN ORCH (EGPRS Normal Channel), EGPRSPR ICH (EGPRS Priority Channel), EGPRSSP ECH (EGPRS Special Channel), NONGPR S(NonGPRS Channel) OPEN (Open), CLOSE (Close)
0~10
None
Cell
Channel Type
None
FULLTC H, HALFTC H
None
SET BTSCHN FALLBA CK (Mandator y)
BTS
PDCH Channel Priority Type Allow E Down G Up Switch Maximum Rate Threshold of PDCHs in a Cell
NONGPR S
GPRS, EGPRSN ORCH, EGPRSPR ICH, EGPRSSP ECH, NONGPR S
None
SET GTRXCH AN (Optional) SET BSCPSSO FTPARA (Optional) SET GCELLPS CHM (Optional)
Physical channel
OPEN
OPEN, CLOSE
None
BSC
30
0~100
0~100
per cent
Cell
Issue 08 (2011-09-30)
625
Paramete r PDCH Uplink Multiplex Threshold PDCH Downlink Multiplex Threshold Uplink Multiplex Threshold of Dynamic Channel Conversio n Downlink Multiplex Threshold of Dynamic Channel Conversio n
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional)
Impact
70
10~70
10~70
None
Cell
80
10~160
10~160
None
Cell
20
10~70
10~70
None
Cell
20
10~80 LEVEL0 (Preempt all dynamic TCHFs), LEVEL1 (No preempt of CCHs), LEVEL2 (No preempt of service TCHF)
10~80
None
Cell
Level of Preemptin g Dynamic Channel
LEVEL0
LEVEL0, LEVEL1, LEVEL2
None
Cell
Issue 08 (2011-09-30)
626
Paramete r Reservatio n Threshold of Dynamic Channel Conversio n
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d
Impact
0~8 NMOI (Network Operation Mode I), NMOII (Network Operation Mode II), NMOIII (Network Operation Mode III) 500ms (500ms), 1000ms (1000ms), 1500ms (1500ms), 2000ms (2000ms), 2500ms (2500ms), 3000ms (3000ms), 3500ms (3500ms), 4000ms (4000ms) NO(NO), YES (YES) 8BIT (8BIT), 11BIT (11BIT)
0~8
None
Cell
NMOII
NMOI, NMOII, NMOIII
None
Cell
T3168 Support 11BIT EGPRS Access
500ms
ms
SET GCELLPS BASE (Optional) SET GCELLPS BASE (Optional) SET GCELLPS BASE (Optional)
Cell
YES
NO, YES
None
Cell
Access Burst Type
8BIT
8BIT, 11BIT
None
Cell
Issue 08 (2011-09-30)
627
Paramete r
Default Value
GUI Value Range 0(No packet access), 3 (Packet access of level 1), 4 (Packet access of levels 1-2), 5 (Packet access of levels 1-3), 6 (Packet access of level 1-4) NOTSUP PORT (Not Support), SUPPOR T (Support) 0ms(0ms), 80ms (80ms), 120ms (120ms), 160ms (160ms), 200ms (200ms), 500ms (500ms), 1000ms (1000ms), 1500ms (1500ms)
Actual Value Range
Unit
MML Comman d
Impact
Packet Access Priority
0, 3, 4, 5, 6
None
Cell
Support USF Granularit y 4 Switch
NOTSUP PORT
None
BSC
T3192 Link Quality Control Mode
500ms
ms
SET GCELLPS BASE (Optional) SET GCELLE GPRSPA RA (Optional)
Cell
IR
IR(IR), LA(LA)
IR, LA
None
Cell
Issue 08 (2011-09-30)
628
Paramete r BSS Paging Coordination A Interface Paging Coordination Switch
Default Value
GUI Value Range NO(NO), YES (YES)
Actual Value Range
Unit
MML Comman d SET GCELLPS BASE (Optional)
Impact
YES
NO, YES
None
Cell
CLOSE
CLOSE (Close), OPEN (Open)
CLOSE, OPEN
None
SET BSCPSSO FTPARA (Optional) SET GCELLPS OTHERP ARA (Optional) SET GCELLPS OTHERP ARA (Optional) SET GCELLPS OTHERP ARA (Optional) SET GCELLPS OTHERP ARA (Optional) SET GCELLPS OTHERP ARA (Optional) SET GCELLPS PWPARA (Optional)
BSC
6~120
6~120
None
Cell
Max. GBR for POC Service Transmiss ion Delay of POC Service
16
6~120
6~120
None
Cell
650
250~650 NO(Not Support), YES (Support) NO(Not Support), YES (Support)
250~650
None
Cell
Support GBR QoS
NO
NO, YES
None
Cell
Support QoS Optimize
NO
NO, YES
None
Cell
GAMMA
12
0~31
0~31
None
Cell
Issue 08 (2011-09-30)
629
Paramete r
Default Value
GUI Value Range 0(0.0), 1 (0.1), 2 (0.2), 3 (0.3), 4 (0.4), 5 (0.5), 6 (0.6), 7 (0.7), 8 (0.8), 9 (0.9), 10 (1.0)
Actual Value Range
Unit
MML Comman d
Impact
ALPHA MS_TXP WR_MA X_CCH
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10
None
SET GCELLPS PWPARA (Optional) SET GCELLC CCH (Optional) SET GCELLPS PWPARA (Optional)
Cell
0~19 BCCH (BCCH), PDCH (PDCH) NC0 (NC0), NC1 (NC1), NC2 (NC2)
0~19
None
Cell
PC_MEA S_CHAN
PDCH
BCCH, PDCH
None
Cell
NC0
NC0, NC1, NC2
None
SET GCELLPS BASE (Optional) SET GCELLG PRS (Optional) SET GCELLG PRS (Optional) SET BTSIDLE TS (Mandator y) SET BTSIDLE TS (Mandator y)
Cell
Support NACC
NO
NO(No), YES(Yes)
NO, YES
None
Cell
Support NC2
NO
NO(No), YES(Yes)
NO, YES
None
Cell
Cabinet Group No.
None
0~2
0~2
None
BTS
Idle TS Count
None
0~512
0~512
None
BTS
Issue 08 (2011-09-30)
630
Paramete r
Default Value
GUI Value Range TDM, HDLC, HDLC_H ubBTS, IP
Actual Value Range TDM, HDLC, HubBTS, IP
Unit
MML Comman d
Impact
Service Type
TDM
None
ADD BTS (Optional)
BTS
2.43.5 Counters
2.43.6 Glossary

l l l 3GPP TS 41.061, "General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements" 3GPP TS 43.064, "General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2" 3GPP TS 44.060, "General Packet Radio Service (GPRS); Mobile Station (MS) - Base Station System (BSC) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol" 3GPP TS 44.064, "Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification" BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
l l l l l l
2.44 GPRS/EGPRS QoS

2.44.1 Introduction
2.44.1.1 Scope
This document describes packet flow management (PFM) procedures, QoS of streaming services, QoS of conversational services, and QoS of PoC service in the GPRS/EGPRS QoS feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the GPRS/EGPRS QoS feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Version
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None The template of the document is optimized. Parameter Change None None
Issue 08 (2011-09-30)
632
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description 2.44.3.5 QoS of Conversational Services is added. None Parameter Change The RTTI PDCH Multiplex Threshold parameter is added. None
Editorial change
2.44.2 Overview
GPRS/EGPRS QoS refers to the quality of GPRS/EGPRS services in the GSM EDGE Radio Access Network (GERAN). The quality of service (QoS) is defined by QoS attributes, including the traffic class, transfer delay, maximum bit rate (MBR), guaranteed bit rate (GBR), traffic handling priority (THP), allocation/retention priority (ARP), and reliability in Release 99 (R99). The GPRS/EGPRS QoS feature ensures that the QoS requirements of the GPRS/EGPRS services are met, that is, the requirements of transfer delay, bandwidth, and reliability of the GPRS/ EGPRS services are met. From the perspective of users, guaranteeing the QoS requirements means improving the service experience. From the perspective of telecom operators, the guaranteed QoS brings about the following benefits: l Telecom operators can customize the policies of radio resource allocation based on the QoS attributes. These policies ensure that high-priority users occupy high bandwidth, experience high data rate, and therefore enjoy better QoS. Low-priority users, however, can share limited bandwidth and QoS. Sufficient bandwidth is guaranteed for the streaming services. When radio resources are insufficient, the bandwidth requirements of high-priority users are preferentially met and their service experience is improved. The delay requirements of conversational services and push to talk over cellular (PoC) services are met. Better service experience and diversified value-added services are provided to attract more high-end users. Telecom operators can formulate flexible charging policies.
In R99 QoS, there are four traffic classes: conversational class, streaming class, interactive class, and background class. These traffic classes are identified by their delay sensitive levels. The conversational class is most sensitive to delay whereas the background class is most insensitive to delay. l Typical conversational services are the services for real-time conversations, such as voice over IP (VoIP), Gaming, video phone, and video conferencing tools. The characteristics of conversational services are as follows: The transfer delay should be low; the time sequence and delay variation between information entities (for example, packets) of the stream should be preserved. Typical streaming services are the real-time video stream and real-time audio stream. The characteristics of streaming services are as follows: The time sequence and delay variation
Issue 08 (2011-09-30)
between information entities (for example, packets) of the stream should be preserved; streaming class does not have strict requirements on transfer delay. l The interactive service is a classical data communication scheme. Typical interactive services include web browsing, database retrieval, and server access. One of the characteristics of interactive services is that a timely response to the request is required. Therefore, the round-trip delay time is one of the key attributes. Another characteristic is that the content of the packets should be transferred at a low bit error rate. The background service is another classical data communication scheme. Typical background services include file downloading, background delivery of email, short message service (SMS), and reception of measurement records. The characteristics of background services are as follows: The traffic is insensitive to transfer delay; the content of the packets should be transferred at a low bit error rate.
The PoC service belongs to the streaming class. It is a type of group call service implemented on the GSM network. The PoC service adopts the packet switching technology and it is carried on the GPRS/EGPRS networks. The major functional entities of the PoC service run on the PoC server in the core network (CN). The signaling and speech signals of the PoC service are carried on the GPRS/EGPRS networks in the form of packets and are transparently transferred from the BSS to the CN. In contrast to the packet service, the speech signals of the PoC service require low transfer delay. If the transfer delay is high, user experience is adversely affected. Different traffic classes have different QoS requirements, which are defined by QoS attributes. The QoS attributes are contained in packet flow context (PFC). The BSC negotiates the QoS attributes with the SGSN by performing the PFM procedures. If the MS or the SGSN does not support the PFM procedures, the BSC should map R97/R98 QoS attributes to R99 QoS attributes to support the handling of R97/R98 QoS attributes. In Huawei GPRS/EGPRS QoS feature, the QoS of the following traffic is supported: streaming class, interactive class, background class, conversational class, best effort (BE) service, and PoC service. l In the case of interactive class, background class, and BE service, the BSC configures the radio block budget weight according to the traffic class, ARP, and THP of the QoS attributes. Then, the BSC allocates radio blocks to users based on the radio block budget weight. High-priority users are allocated more radio resources and therefore the available radio bandwidth is high. In Huawei GPRS/EGPRS QoS feature, best effort (BE) service refers to the service whose QoS attributes are not obtained from the BSC or the service whose traffic class is unknown. The radio resource allocation and scheduling of this type of service are performed on the basis of the best effort policy. In the case of streaming class, the BSC allocates radio blocks according to the GBR of the QoS attributes and ensures that the streaming users have sufficient bandwidth. In addition, the BSC supports the preemption of streaming resources. When radio resources are insufficient, high-priority streaming services can preempt the radio blocks of low-priority streaming services. This ensures that high-priority services can use radio resources preferentially. In the case of conversational class, if the MS supports reduced latency, the BSC allocates a PDCH pair in reduced transmission time interval (RTTI) configuration to the conversational service and activates the fast ack/nack reporting (FANR). This minimizes the transfer delay is minimized. The PoC service belongs to the real-time packet services and it has strict requirements on bandwidth and transfer delay. The bandwidth requirement of the PoC service is guaranteed by the GBR mechanism of streaming class. To ensure the low transfer delay requirement of the PoC service, the BSC takes several measures to reduce latency, such as preferentially
Issue 08 (2011-09-30)
scheduling the PoC service, using a low-rate coding scheme, and using the balanced uplink and downlink channel allocation policy.

2.44.3.1 PFM Procedures
PFM procedures, which are used for PFC management, consist of the PFC establishment procedure, PFC modification procedure, and PFC deletion procedure. The PFM procedures are introduced in R99 QoS. The BSC negotiates the QoS attributes with the SGSN by performing the PFM procedures and then stores the negotiated QoS attributes in the PFC. The BSC supports the PFC function only when both Support GBR QoS and PFC Support are set to Yes. The PFC Feature Mode information element in the system information indicates whether the network side supports PFC.
?.1. PFC Establishment Procedure

The PFC establishment procedure is used to establish the PFC for an MS and to specify the QoS attributes for the uplink and downlink data transfer of the MS. The PFC establishment procedure can be initiated by the BSC or the SGSN.
PFC Establishment Procedure Initiated by the BSC

Figure 2-131 shows the PFC establishment procedure initiated by the BSC. Figure 2-131 PFC establishment procedure initiated by the BSC
1.
If the uplink or downlink LLC PDUs transmitted between the MS and the SGSN contain a PFI but the PFC corresponding to the PFI does not exist in the BSC, the BSC sends the SGSN a Download BSS PFC message to request the establishment of the PFC. Before the PFC is established, the BSC transmits uplink and downlink LLC PDUs according to the QoS attributes of BE services. If the BSC does not receive the PFI, it does not send the Download BSS PFC message to the SGSN. In this case, the transmission of uplink and downlink LLC PDUs is based on the QoS attributes of BE services.
Issue 08 (2011-09-30)

NOTE
The QoS attributes of BE services are the R99 QoS attributes that are mapped from the QoS Profile carried in the DL Unitdata message. For details, see 2.44.3.2 Mapping From R97/R98 QoS Attributes to R99 QoS Attributes.
2.
After receiving the Download BSS PFC message, the SGSN sends the BSC a Create BSS PFC message, requesting the BSC to establish a PFC. The Create BSS PFC message contains the ABQP, ARP, PFI, and PFT. After receiving the Create BSS PFC message, the BSC creates a PFC corresponding to the PFI and stores the ABQP, ARP, PFI, and PFT in the PFC. If the BSC successfully creates a PFC, it sends a Create BSS PFC ACK message to the SGSN. The Create BSS PFC ACK message contains the ABQP adjusted in the BSC. If the BSC fails to create a PFC, it sends a Create BSS PFC NACK message to the SGSN.
3.
PFC Establishment Procedure Initiated by the SGSN

Figure 2-132 shows the PFC establishment procedure initiated by the SGSN. Figure 2-132 PFC establishment procedure initiated by the SGSN
After receiving the PDP context activation request from an MS, the SGSN sends the BSC a Create BSS PFC message, requesting the BSC to establish a PFC. For details of the remaining procedure, see PFC Establishment Procedure Initiated by the BSC.
?.2. PFC Modification Procedure

The PFC modification procedure is used to modify the QoS attributes in a PFC. It can be initiated by the BSC or the SGSN.
PFC Modification Procedure Initiated by the BSC

Figure 2-133 shows the PFC modification procedure initiated by the BSC.
Issue 08 (2011-09-30)
636
Figure 2-133 PFC modification procedure initiated by the BSC
1.
When the QoS requirements are not fulfilled because the usage of radio resources changes, for example, when the available radio blocks are insufficient and the GBR should be decreased, the BSC should send the SGSN a Modify BSS PFC message, requesting the SGSN to modify the ABQP. The Modify BSS PFC message contains the aggregate bss qoS profile (ABQP) that is modified in the BSC. ABQP contains the QoS attributes of R97/R98 and R99. After receiving the Modify BSS PFC message, the SGSN sends the BSC a Modify BSS PFC ACK message, containing the ABQP acceptable to the SGSN. If the SGSN accepts the ABQP modified in the BSC, the Modify BSS PFC ACK message contains the modified ABQP. If the SGSN does not accept the ABQP modified in the BSC, the Modify BSS PFC ACK message contains the old ABQP. After receiving the Modify BSS PFC ACK message, the BSC compares the ABQP contained in the Modify BSS PFC ACK message with the ABQP modified in the BSC. If the two ABQPs are the same, the QoS attributes in the PFC are successfully modified and the BSC updates the contents of the PFC with the modified ABQP. If the two ABQPs are different, the old ABQP is still used and the contents of the PFC remain unchanged.
2.
3.
PFC Modification Procedure Initiated by the SGSN

Figure 2-134 shows the PFC modification procedure initiated by the SGSN. Figure 2-134 PFC modification procedure initiated by the SGSN
Issue 08 (2011-09-30)
637
1.
After receiving a PDP context activation, deactivation, or modification request from an MS, if the SGSN finds that the contents of the PFC need to be modified, the SGSN sends the BSC a Create BSS PFC message, requesting the BSC to modify the ABQP in the PFC. The Create BSS PFC message contains the ABQP that is modified in the SGSN. After receiving the Create BSS PFC message, if the PFC exists in the BSC, the BSC obtains the ABQP from the message, updates the ABQP in the PFC, and then sends a Create BSS PFC ACK message to the SGSN; if the PFC does not exist in the BSC, the BSC creates a PFC, stores the ABQP, ARP, PFI, and PFT in the PFC, and then sends a Create BSS PFC ACK message to the SGSN.
2.
?.3. PFC Deletion Procedure

The PFC deletion procedure is used to delete the PFC of a BSC. Huawei GPRS/EGPRS QoS feature supports the PFC deletion procedure initiated by the SGSN but not by the BSC. As specified in the 3GPP TS 23.060 specification, when the BSC does not support the ABQP in the PFC, the BSC can initiate the PFC deletion procedure to request the SGSN to delete or modify the PFC. On the BSC side, when the PFT corresponding to the PFC expires or when the MS terminates the PS services, the BSC deletes the PFC without notifying the SGSN. On the SGSN side, when the SGSN decides to delete the PFC, the SGSN sends the BSC a Delete BSS PFC message, requesting the BSC to delete the PFC. After receiving the Delete BSS PFC message, the BSC deletes the PFC and then sends a Delete BSS PFC ACK message to the SGSN.
PFC Deletion Procedure Initiated by the SGSN

Figure 2-135 shows the PFC deletion procedure initiated by the SGSN. Figure 2-135 PFC deletion procedure initiated by the SGSN
2.44.3.2 Mapping From R97/R98 QoS Attributes to R99 QoS Attributes

In the 3GPP standards, there are two definitions of QoS, one in the R97/R98 and one in the R99. In R99, the definitions of GERAN QoS attributes are the same as the definitions of UTRAN QoS attributes. PFM procedures are introduced into R99 QoS for the BSC and the SGSN to negotiate QoS attributes. In R97/R98 QoS, QoS attributes are negotiated between the MS and the SGSN, and the BSC is not involved in the QoS negotiation. If the MS or the SGSN does not support the PFM procedures, that is, the MS or the SGSN does not support R99 QoS, the BSC needs to map R97/R98 QoS attributes to R99 QoS attributes to support the R97/R98 QoS handling. After R97/R98 QoS attributes are mapped to R99 QoS attributes, the BSC handles R97/R98/R99 QoS attributes in the same manner.
On the BSC side, R99 QoS attributes are negotiated between the BSC and the SGSN through the PFM procedures and are stored in the ABQP of the PFC. Table 2-112 lists R99 QoS attributes. Table 2-112 R99 QoS attributes R99 QoS Attribute Maximum bit rate Delivery order Maximum SDU size SDU format information SDU error ratio Residual bit error ratio Delivery of erroneous SDUs Transfer delay Guaranteed bit rate Traffic handling priority Allocation/Retention priority Source statistic descriptor Signaling indication Conversatio nal Class Y Y Y Y Y Y Y Y Y Y Y Streaming Class Y Y Y Y Y Y Y Y Y Y Y Interactive Class Y Y Y Y Y Y Y Y Y Background Class Y Y Y Y Y Y Y -
NOTE
In the preceding table, "Y" indicates that the attribute is used by the traffic class, and "-" indicates that the attribute is not used by the traffic class.
When the SGSN transmits downlink LLC PDUs to the BSC, the R97/R98 QoS attribute information (QoS Profile) is contained in the DL Unitdata message of the downlink LLC PDUs. Table 2-113 lists the R97/R98 QoS attributes. Table 2-113 R97/R98 QoS attributes R97/R98 QoS Attribute Delay class Reliability class
Issue 08 (2011-09-30)
SGSN Y Y
BSC 639
R97/R98 QoS Attribute Peak throughput Precedence Mean throughput
SGSN Y Y Y
BSC Y Y -
NOTE
In the preceding table, "Y" indicates that the attribute is present in the NE, and "-" indicates that the attribute is not present in the NE.
In the SGSN, there are five R97/R98 QoS attributes; in the BSC, there are only two Peak throughput and Precedence attributes. These two attributes are obtained by the BSC from the SGSN through the QoS Profile information element in the DL Unitdata message. The BSC needs to map these two R97/R98 QoS attributes to the related R99 QoS attributes, that is, R97/R98 Peak throughput to R99 Maximum bit rate, and R97/R98 Precedence to R99 Allocation/ Retention priority. For details of the mapping, see the 3GPP TS 23.107 specification. In R99, the ARP attribute is mainly used for the preemption of streaming class resources. The ARP attribute is not contained in the ABQP and it is transmitted from the SGSN to the BSC through a Create BSS PFC message in the PFM procedure. If the Create BSS PFC message does not contain the ARP attribute, the BSC cannot obtain the R99 QoS attribute ARP. In this case, the BSC needs to map Precedence class of the ABQP to Allocation/Retention priority of R99 QoS. Therefore, the mapping between Precedence and Allocation/Retention priority occurs in the following conditions: l l Mapping between Precedence of R97/R98 QoS and Allocation/Retention priority of R99 QoS Mapping between Precedence class in the ABQP and Allocation/Retention priority of R99 QoS in the case that the ARP attribute does not exist in R99 QoS
As specified in the 3GPP standard, there are 15 priority levels for the ARP attribute. The ARP is limited to priority levels 1, 2, and 3 for GERAN when the Gb bearer service is used. Table 2-114 describes the mapping between ARP, Precedence, and Precedence class. A unified ARP level is defined to support the configuration of the radio block budget weight based on QoS levels. The ARP level can be 1, 2, or 3. The priority attributes of R99 QoS and those of R97/R98 QoS should be mapped to the ARP levels. The mapping between the ARP levels and the priority attributes is as follows: l l l If the negotiated R99 QoS has the ARP attribute, the Priority level of the ARP attribute is mapped to the ARP level. If the negotiated R99 QoS does not have the ARP attribute, the Precedence class in the ABQP is mapped to the ARP level. If the BSC or the SGSN does not support PFC, the Precedence attribute of R97/R98 QoS is mapped to the ARP level.
Issue 08 (2011-09-30)
640
Table 2-114 ARP mapping table Priority Level of ARP ARP Level 1 2 3 R99 QoS with ARP 1 2 3-15 Precedence Class of ABQP R99 QoS Without ARP 1 2 3 Precedence of QoS Profile (R97/R98 QoS) 0 1 2
2.44.3.3 QoS of Interactive, Background, and BE Services

For interactive, background, and BE services, the BSC configures the radio block budget weight according to the traffic class, ARP, and THP of the QoS attributes. Then, the BSC allocates radio blocks to a TBF based on the radio block budget weight. The configured radio block budget weight reflects the traffic priority and the user priority. High-priority traffic classes or users are allocated more radio resources and therefore the available radio bandwidth is high.
Configuring Radio Block Budget Weight

The BSC allocates radio blocks to a TBF based on the radio block budget weight. In one radio block budget period, the number of radio blocks allocated to a TBF is proportional to the corresponding radio block budget weight. The radio block budget weight is configured according to the combination of traffic class, ARP, and THP, which can be described in a configuration table. Here, the THP is used only for interactive class and it has three priority levels; the ARP is used for all traffic classes and it has three priority levels. For the definition of the ARP, see 2.44.3.2 Mapping From R97/R98 QoS Attributes to R99 QoS Attributes. Table 2-115 describes the configuration of radio block budget weight. In this table, the default values are used. Table 2-115 Configuration of radio block budget weight Traffic Class and THP Interactive class THP1 THP2 THP3 Background class BE service ARP Level 1 10 8 6 4 8 ARP Level 2 6 4 3 2 4 ARP Level 3 4 3 2 1 2
The principles of configuring radio block budget weight are as follows: l If different traffic classes have the same ARP level, the traffic classes should have decreasing radio block budget weight according to the order of interactive class, background class, and BE services. For the same traffic class, the radio block budget weight
Issue 08 (2011-09-30)
should be configured according to the ARP level and THP, that is, the radio block budget weight is proportional to the ARP level or THP. l For interactive class, the radio block budget weight is configured according to the ARP level and THP. The configuration principles are as follows: For the interactive services at the same ARP level, the radio block budget weight is proportional to the THP. For the interactive services at the same THP, the radio block budget weight is proportional to the ARP level. The related configuration parameters at the cell level are as follows: THP1-ARP1 Priority Weight, THP1-ARP2 Priority Weight, THP1-ARP3 Priority Weight, THP2-ARP1 Priority Weight, THP2-ARP2 Priority Weight, THP2-ARP3 Priority Weight, THP3ARP1 Priority Weight, THP3-ARP2 Priority Weight, and THP3-ARP3 Priority Weight. l For background class, the radio block budget weight is configured according to the ARP level. The ARP level is proportional to the radio block budget weight. The related configuration parameters at the cell level are Background-ARP1 Priority Weight, Background-ARP2 Priority Weight, and Background-ARP3 Priority Weight. For BE services, the radio block budget weight is configured according to the ARP level. The ARP level is proportional to the radio block budget weight. The related configuration parameters at the cell level are BestEffort-ARP1 Priority Weight, BestEffort-ARP2 Priority Weight, and BestEffort-ARP3 Priority Weight.
Budgeting and Updating the Radio Blocks for Non-GBR TBFs

During the radio resource allocation, the BSC needs to allocate one or more PDCHs to a TBF and then budget the maximum number of radio blocks that can be used by the TBF on each PDCH in one radio block budget period. This number indicates the number of budgeted radio blocks. In a radio block budget period, the number of radio blocks scheduled for a TBF on a PDCH should not exceed the number of budgeted radio blocks. Based on the radio block budget weight, the BSC calculates the number of budgeted radio blocks on a PDCH for interactive class, background class, and BE services. On each PDCH, the number of budgeted radio blocks for a TBF is proportional to the radio block budget weight of the TBF. The formula for calculating the number of budgeted radio blocks for a non-GBR TBF is as follows:
Here, BNi: indicates the number of budgeted radio blocks for No. i non-GBR TBF on the PDCH in a radio block budget period. PWi: indicates the radio block budget weight for No. i non-GBR TBF on the PDCH. PWj: indicates the radio block budget weight for No. j non-GBR TBF on the PDCH. BNtotal: indicates the total number of radio blocks on the PDCH in a radio block budget period.
BNgbr: indicates the total number of radio blocks that have been allocated to GBR TBFs on the PDCH in a radio block budget period. BNr: indicates the number of radio blocks between the current radio block being scheduled and the last radio block of the current multiframe. n: indicates the number of TBFs multiplexed on the PDCH. After allocating radio blocks to non-GBR TBFs, the BSC needs to update the number of budgeted radio blocks if the usage of radio blocks on the PDCH changes. In the following conditions, the BSC should update the number of budgeted radio blocks for each TBF on the PDCH. l l l l The radio block being scheduled currently is the last block in the last multiframe during a radio block budget period. A TBF is created. A TBF is deleted. The state of a TBF changes.
2.44.3.4 QoS of Streaming Services

In the case of streaming class, the BSC allocates radio blocks to users according to the GBR of the QoS attributes and ensures that the data transmission rates meet the requirements of streaming class. If streaming services support resource preemption, high-priority streaming services can preempt the radio blocks of low-priority streaming services when radio resources are insufficient. This ensures that high-priority services can preferentially use radio resources. If streaming services do not support resource preemption, the GBRs are decreased; when radio resources become sufficient, the GBRs are restored to the negotiated values. When the BSC needs to decrease or restore GBRs, it requests the SGSN to modify the GBRs through the PFM procedures.
?.1. GBR Assurance
Budgeting and Updating the Radio Blocks for GBR TBFs

The BSC needs to allocate the radio blocks on one or more PDCHs to a TBF. The number of radio blocks that can be scheduled for a TBF on a PDCH in one radio block budget period should not exceed the number of budgeted radio blocks for the TBF on this PDCH. The number of budgeted radio blocks for a streaming class service is specified by the GBR of the QoS attributes. The BSC calculates the number of budgeted radio blocks for a TBF according to the GBR and the RLC payload of the RLC/MAC radio block corresponding to the current coding scheme. The formula for calculating the number of budgeted radio blocks for a GBR TBF is as follows:
Here, BNi: indicates the number of budgeted radio blocks for GBR TBFi in a radio block budget period. BR(GBRi): indicates the bit rate that is converted from the current GBR of GBR TBFi.
RS(CSi): indicates the RLC payload of the RLC/MAC radio block corresponding to the current coding scheme of GBR TBFi. BBP: indicates the radio block budget period, which equals a five-multiframe period, that is, 1200 ms. K: indicates the redundancy coefficient and its value is 1.1. The value obtained according to the preceding formula is the total number of radio blocks allocated to the GBR TBF on one or more PDCHs. The total number of radio blocks divided by the number of allocated PDCHs equals the number of budgeted radio blocks per PDCH. In one radio block budget period, the ratio of the total number of radio blocks allocated to GBR TBFs to the total number of radio blocks on a PDCH cannot exceed a specified value to reserve radio resources for non-GBR TBFs. In Huawei GPRS/EGPRS QoS feature, the specified value is 80%. That is, when GBR TBFs and non-GBR TBFs are multiplexed on the same PDCH, at least 20% of the radio blocks should be reserved for non-GBR TBFs, and a maximum of 80% of the radio blocks can be used for GBR TBFs. After allocating radio blocks to GBR TBFs, the BSC needs to update the number of budgeted radio blocks if the usage of radio blocks on the PDCH changes. For GBR TBFs and non-GBR TBFs, the methods of updating the number of budgeted radio blocks are the same.
Modifying and Restoring GBRs

l Support for GBR modification When the number of radio resources allocated to a GBR TBF changes or the coding scheme of a GBR TBF changes, the BSC calculates the number of budgeted radio blocks for the GBR TBF on a PDCH based on the GBR and the current coding scheme. If the GBR cannot meet the user requirement because of insufficient radio blocks on the PDCH, the BSC calculates the GBR (the calculated GBR is smaller than the negotiated GBR) based on the number of actually available radio blocks on the PDCH. In addition, the BSC modifies the GBR in the PFC and initiates a PFC modification procedure to request the SGSN to modify the GBR. For details, see 2.44.3.1.2 PFC Modification Procedure. l Support for GBR restoration If the BSC has initiated a PFC modification procedure and the GBR on the BSC side has been decreased, the BSC can restore the GBR in the PFC to the negotiated value and initiate a PFC modification procedure to request the SGSN to modify the GBR when the GBR TBF uses a higher-rate coding scheme. For details, see 2.44.3.1.2 PFC Modification Procedure. When a GBR TBF is released or it uses a higher-rate coding scheme, if one or more PDCHs allocated to this GBR TBF have available radio blocks and the GBR of another GBR TBF on these PDCHs is smaller than the negotiated value, the BSC reallocates radio blocks to the latter GBR TBF and initiates a GBR restoration procedure.
?.2. Resource Preemption

After the Preempt Switch of Streaming Resource parameter is set to Yes, the BSC starts the preemption of streaming resources. The ARP attribute defined in R99 QoS contains the following information: resource allocation priority, resource preemption, and PFC queuing. The information is mainly used for the preemption of streaming resources and for the PFC queuing. Currently, Huawei GPRS/EGPRS QoS feature does not support the PFC queuing of streaming services.
When radio resources are insufficient, high-priority streaming services can preempt the radio resources occupied by low-priority streaming services, This ensurs that the GBR requirements of high-priority services are met. Before performing the preemption of streaming resources, the BSC allocates one or more optimal PDCHs to a user according to the channel allocation algorithm. The streaming preemption weight should be added to the channel allocation algorithm and it is used to specify the priority for allocating PDCHs when radio resources are insufficient during resource preemption. The streaming preemption weight is determined by the preemption trigger type and the number of PDCHs and radio blocks to be preempted. The streaming preemption weight is proportional to the priority for allocating PDCHs. The priorities of preemption trigger type are listed in descending order as follows: l l l l Not trigger preemption Trigger preemption only when PDCHs are insufficient Trigger preemption only when radio blocks are insufficient Trigger preemption when both PDCHs and radio blocks are insufficient
When a TBF supports preemption, the BSC performs the resource preemption algorithm on streaming services if the radio blocks on one or more PDCHs are insufficient or PDCHs are insufficient. On one or more PDCHs of the preempting TBF, the BSC releases one or more preemptable TBFs to meet the GBR and multislot requirements of the preempting TBF. The TBFs to be preempted must meet the following requirements: l l l l The TBFs to be preempted must be preemptable. The ARP of the TBFs to be preempted must be lower than the ARP of the preempting TBF. Among all the preemptable TBFs on one or more PDCHs, the TBF that is being preempted should have the lowest ARP. The number of PDCHs occupied by all the TBFs to be preempted should be greater than or equal to the number of PDCHs required by the preempting TBF to meet the multislot requirement of the preempting TBF. The number of radio blocks occupied by all the TBFs to be preempted should be greater than or equal to the number of radio blocks required by the preempting TBF to meet the GBR requirement of the preempting TBF.
According to the preceding requirements, the BSC performs the following processing: l l If the TBFs to be preempted meet all the preceding requirements, the BSC releases the TBFs to be preempted and then allocates the radio resources to the preempting TBF. If no preemptable TBF meets the previous requirements or the number of available PDCHs after preemption does not meet the multislot requirement, the resource preemption fails and service access requests are rejected. If the number of available PDCHs after preemption meets the multislot requirement but the number of radio blocks to be preempted does not meet the GBR requirement, the BSC calculates the actual available GBR based on the total number of radio blocks occupied by all the preempted TBFs and then modifies the GBR in the PFC. Meanwhile, the BSC initiates a PFC modification procedure to request the SGSN to modify the GBR.
2.44.3.5 QoS of Conversational Services

Conversational services are real-time services and have strict requirements on transfer delay. According to the 3GPP specifications, the transfer delay of conversational services cannot exceed 80 ms. Generally, the end-to-end transfer delay of VoIP services cannot exceed 300 ms to ensure user satisfaction.
With the introduction of RTTI, the round-trip time (RTT) is reduced from 20 ms to 10 ms on both the Um and Abis interfaces. With the introduction of FANR, the reaction time of the MS is minimized even if the link quality on the Um interface is poor. Theoretically, therefore, the requirement of conversational services for transfer delay (80 ms) can be met after RTTI and FANR are introduced. For details of RTTI and FANR, see 2.53 Latency Reduction. If the MS supports reduced latency and if the BSC supports RTTI and FANR, the BSC allocates an RTTI to a conversational service and activates the FANR. In this manner, the delay requirement of the conversational service is met to the maximal degree. If the MS does not support reduced latency or if the BSC does not support RTTI or FANR, the BSC allocates PDCHs in BTTI configuration to a conversational service and does not reject the packet access of the conversational service. The BSC, however, does not ensur the transfer delay required by the conversational service. In addition to RTTI and FANR, the following methods are used to reduce the transfer delay of conversational services: l The radio block scheduling delay is reduced by limiting the channel multiplexing ratio. The parameter RTTI PDCH Multiplex Threshold specifies the PDCH multiplexing threshold in RTTI configuration. The thresholds for both the uplink and downlink multiplexing ratios of the PDCHs in RTTI configuration are specified by RTTI PDCH Multiplex Threshold. If the channel multiplexing ratio of a PDCH in RTTI configuration equals the PDCH multiplexing threshold in RTTI configuration, no more TBFs can be multiplexed on this PDCH. The maximum multiplexing ratio of the PDCH in RTTI configuration is limited. Therefore, the maximum interval of scheduling the radio blocks on the PDCHs in RTTI configuration is limited. As a result, the radio block scheduling delay is limited to an allowable range. l Specific LA/IR algorithms are adopted to reduce RLC data block retransmissions, reducing the transfer delay. A new table about the mapping between the BEP measurement reports and the coding schemes is used for conversational services. When the signal quality on the Um interface is poor, conversational services adopt low-rate coding schemes to reduce data retransmissions and ensure low BEP. The characteristics of Huawei conversational QoS are as follows: l Currently, RTTI and FANR are supported only when IP/HDLC transmission is used on the Abis interface. Therefore, conversational QoS is better ensured in IP/HDLC transmission mode than in other transmission modes. In addition, RTTI and FANR are enabled or disabled simultaneously. Conversational services do not support resource preemption or resource queuing. The RLC unacknowledged mode is not supported in the data transmission of conversational services. Conversational services adopt specific LA/IR algorithms to reduce data retransmissions.
l l
2.44.3.6 QoS of PoC Service

The PoC service is a real-time packet service and has strict requirements on bandwidth and transfer delay. The bandwidth of the PoC service is ensured by the GBR mechanism of streaming class. To meet the low transfer delay requirement of the PoC service, the BSC takes many optimization measures, such as preferentially scheduling the PoC service, using a low-rate coding scheme, and using the policy of balanced channel allocation between uplink and downlink.
The BSC must identify the traffic class before processing the PoC service. According to the current protocols, the BSC cannot learn the PoC traffic class directly from the uplink and downlink packet signaling and it can only roughly determine the PoC traffic class according to the QoS attributes. The method of determining the PoC traffic class is as follows: l l l l The traffic class is the streaming class. Both the uplink and downlink GBRs of QoS attributes are higher than Min. GBR for POC Service but smaller than Max. GBR for POC Service. The transfer delay of QoS attributes is shorter than Transmission Delay of POC Service. The PFI value is not the one reserved for BE services, GPRS mobility management/session management (GMM/SM) signaling, short message service (SMS), or tunnelling of messages (TOM).
If all the preceding conditions are met, the traffic class is considered as the PoC service. To prevent the incorrect identification of the traffic class, telecom operators should configure the following parameters as required: Min. GBR for POC Service, Max. GBR for POC Service, and Transmission Delay of POC Service. The PoC service is of the streaming class. The BSC allocates radio blocks to a PoC service according to the GBR of the streaming class to ensure the GBR for the PoC service. The PoC service has a strict requirement for transfer delay. To meet the low transfer delay requirement, the BSC processes the PoC service as follows: l Adopts a lower-rate coding scheme (for example, the data rate of the coding scheme adopted should not be higher than that of MCS-6) to reduce the bit error rate and retransmission times, thus reducing the transfer delay. Determines the LLC PDU lifetime according to the transfer delay of the QoS attributes. Increases the delay of releasing uplink and downlink TBFs. The priority of scheduling the PoC service is higher than that of scheduling other services. This helps reduce the transfer delay of the PoC service.
l l l
The PoC service runs on concurrent and symmetrical uplink and downlink data flows. Therefore, the BSC adopts the policy of balanced channel allocation between uplink and downlink. Within the multislot capability of an MS, the BSC attempts to allocate the same number of uplink PDCHs and downlink PDCHs to the MS. For example, for an MS of multislot class 10, the following two channel allocation schemes can be used. Channel Allocation Scheme 1 2 Number of Downlink Timeslots 4 3 Number of Uplink Timeslots 1 2 Total Number of Timeslots 5 5
According to the policy of balanced channel allocation between uplink and downlink, the BSC adopts channel allocation scheme 2 for the PoC service.
2.44.4 Parameters
This chapter describes the parameters related to GPRS/EGPRS QoS.
For the meaning of each parameter, see Table 2-116. For the default value, value ranges, and MML commands of each parameter, see Table 2-117. Table 2-116 Parameter description (1) Parameter PFC Support THP1-ARP1 Priority Weight THP1-ARP2 Priority Weight THP1-ARP3 Priority Weight THP2-ARP1 Priority Weight THP2-ARP2 Priority Weight THP2-ARP3 Priority Weight THP3-ARP1 Priority Weight THP3-ARP2 Priority Weight THP3-ARP3 Priority Weight Background-ARP1 Priority Weight Background-ARP2 Priority Weight Background-ARP3 Priority Weight
Issue 08 (2011-09-30)
Description Whether to support packet flow context (PFC). The PFC flow is used to control the QoS of the packet service of the MS. Combination of the THP1 and ARP1 priority in the Interactive service. THP1-ARP1 priority weight determines the number of the budget blocks and the block scheduling priority. Combination of the THP1 and ARP2 priority in the Interactive service. THP1-ARP2 priority weight determines the number of the budget blocks and the block scheduling priority. Combination of the THP1 and ARP3 priority in the Interactive service. THP1-ARP3 priority weight determines the number of the budget blocks and the block scheduling priority. Combination of the THP2 and ARP1 priority in the Interactive service. THP2-ARP1 priority weight determines the number of the budget blocks and the block scheduling priority. Combination of the THP2 and ARP2 priority in the Interactive service. THP2-ARP2 priority weight determines the number of the budget blocks and the block scheduling priority. Combination of the THP2 and ARP3 priority in the Interactive service. THP2-ARP3 priority weight determines the number of the budget blocks and the block scheduling priority. Combination of the THP3 and ARP1 priority in the Interactive service. THP3-ARP1 priority weight determines the number of the budget blocks and the block scheduling priority. Combination of the THP3 and ARP2 priority in the Interactive service. THP3-ARP2 priority weight determines the number of the budget blocks and the block scheduling priority. Combination of the THP3 and ARP3 priority in the Interactive service. THP3-ARP3 priority weight determines the number of the budget blocks and the block scheduling priority. ARP1 priority in the Background service. ARP1 priority weight determines the number of the budget blocks and the block scheduling priority. ARP2 priority in the Background service. ARP2 priority weight determines the number of the budget blocks and the block scheduling priority. ARP3 priority in the Background service. ARP3 priority weight determines the number of the budget blocks and the block scheduling priority.
648
Parameter BestEffort-ARP1 Priority Weight BestEffort-ARP2 Priority Weight BestEffort-ARP3 Priority Weight
Description ARP1 priority in the BE service. ARP1 priority weight determines the number of the budget blocks and the block scheduling priority. ARP2 priority in the BE service. ARP2 priority weight determines the number of the budget blocks and the block scheduling priority. ARP3 priority in the BE service. ARP3 priority weight determines the number of the budget blocks and the block scheduling priority. When the PDCHs are insufficient, the streaming service with high priority can preempt the PDCHs that are seized by the streaming service with low priority. After the PDCH resource preemption, the streaming service with low priority initiates the QoS negotiation with the SGSN. If the QoS negotiation fails, or if all the PDCHs are preempted, then the streaming service with low priority is disrupted. Maximum number of RTTI TBFs that can be multiplexed on the PDCH. A PDCH can be assigned when the number of RTTI TBFs on it is smaller than the value of this parameter. This parameter is valid only when its value is smaller than or equal to "MSRD PDCH DL Multiplexing Threshold". Minimum bandwidth of the POC service (push to talk over cellular). The transmission delay of the POC service must be relatively small. The network side must support the function of detecting the POC service type and reduce the delay through related processing to meet the POC service requirement. For the POC service received by the network side, GbrValue in the ABQP must be larger than the minimum bandwidth of the POC service. Maximum bandwidth of the POC service (push to talk over cellular). The transmission delay of the POC service must be relatively small. The network side must support the function of detecting the POC service type and reduce the delay through related processing to meet the POC service requirement. For the POC service received by the network side, GbrValue in the ABQP must be lower than the maximum bandwidth of the POC service. Maximum transmission delay of the POC service (push to talk over cellular). The transmission delay of the POC service must be relatively small. The network side must support the function of detecting the POC service type and reduce the delay through related processing to meet the POC service requirement. For the POC service received by the network side, Transfer Delay in the ABQP must be lower than the transmission threshold of the POC service.
Preempt Switch of Streaming Resource
RTTI PDCH Multiplex Threshold
Max. GBR for POC Service
Transmission Delay of POC Service
Issue 08 (2011-09-30)
649
Table 2-117 Parameter description (2) Paramete r Default Value GUI Value Range NO(No Support), YES (Support) Actual Value Range Unit MML Comman d Impact
PFC Support THP1ARP1 Priority Weight THP1ARP2 Priority Weight THP1ARP3 Priority Weight THP2ARP1 Priority Weight THP2ARP2 Priority Weight THP2ARP3 Priority Weight THP3ARP1 Priority Weight THP3ARP2 Priority Weight
NO
NO, YES
None
ADD NSE (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional)
NSE
10
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
Issue 08 (2011-09-30)
650
Paramete r THP3ARP3 Priority Weight Backgrou nd-ARP1 Priority Weight Backgrou nd-ARP2 Priority Weight Backgrou nd-ARP3 Priority Weight BestEffort -ARP1 Priority Weight BestEffort -ARP2 Priority Weight BestEffort -ARP3 Priority Weight Preempt Switch of Streaming Resource RTTI PDCH Multiplex Threshold
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS CHM (Optional) SET GCELLPS OTHERP ARA (Optional) SET GCELLPS CHM (Optional) SET GCELLPS OTHERP ARA (Optional)
Impact
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
1~10
1~10
None
Cell
OFF
OFF (OFF), ON (ON)
OFF, ON
None
Cell
30
10~80
10~80
None
Cell
6~120
6~120
None
Cell
Issue 08 (2011-09-30)
651
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLPS OTHERP ARA (Optional) SET GCELLPS OTHERP ARA (Optional)
Impact
Max. GBR for POC Service Transmiss ion Delay of POC Service
16
6~120
6~120
None
Cell
650
250~650
250~650
None
Cell
2.44.5 Counters
2.44.6 Glossary

l l l l l l l l l l l l 3GPP TS 43.064: Overall description of the GPRS Radio Interface; Stage 2 3GPP TS 44.060: Radio Link Control (RLC) / Medium Access Control (MAC) protocol 3GPP TS 23.107: Quality of Service (QoS) concept and architecture 3GPP TS 23.979: Push-to-talk over Cellular (PoC) services; Stage 2 3GPP TS 48.018: BSS GPRS Protocol (BSSGP) 3GPP TS 23.060: General Packet Radio Service (GPRS); Service Description; Stage 2 BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.45 Half-Rate Speech

2.45.1 Introduction
2.45.1.1 Scope
This document describes the working principles of and the channel allocation algorithms regarding the half-rate speech. This document also describes the compatibility between half-rate speech and other features.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the half-rate speech feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
Issue 08 (2011-09-30)
653
01 (2009-06-30)
2.45.2 Overview
With the increase in the number of subscribers, the GSM spectrum becomes insufficient. The introduction of half-rate speech improves spectrum efficiency to a great extent, almost doubles the network capacity, and saves the transmission resources on the Um interface by increasing the number of configurable speech channels and at the same time not affecting the QoS to a great extent. If the full-rate speech codec is used on the Um, Abis, and Ater interfaces, the BSS uses channels of 16 kbit/s for coding and transmission. If the half-rate speech codec is used on the Um, Abis, and Ater interfaces, the BSS uses channels of 8 kbit/s for coding and transmission. Thus, when half-rate speech channels are used, a channel of 6 kbit/s on the terrestrial interface Abis can be used to carry two speech services. In this way, the terrestrial link can be used to carry more traffic volume, and the transmission resources on the Abis interface are saved. According to 3GPP TS 46.002, some modifications are required so that the BSS can support the half-rate speech codec. The modifications involve the Um interface, Abis interface, Ater interface, physical channels, and TRAU. The version of half-rate speech codec is Half-Rate Speech Version 1.

2.45.3.1 Principles
To support half-rate speech, both the MS and the BTS must support GSM Phase 2. Figure 2-136 shows the implementation of half-rate speech on the Um interface. Figure 2-136 Implementation of half-rate speech on the Um interface
The MS performs the following processing on the uplink and downlink:

On the downlink In half-rate mode, the MS decodes only the two odd or even multiframes of the four multiframes.
On the uplink In half-rate mode, the MS encodes only the two odd or even multiframes of the four multiframes, that is, the MS sends only two multiframes.
The BTS performs the following processing on the uplink and downlink: l On the downlink In half-rate mode, the BTS encodes the data on sub-channels 0 and 1, and: For the two multiframes generated from the encoding of the data on sub-channel 0, the BTS transmits them through the even multiframes. For the two multiframes generated from the encoding of the data on sub-channel 1, the BTS transmits them through the odd multiframes. On the Um interface, the modulation scheme in half-rate mode is the same as that in fullrate mode. l On the uplink The BTS does not distinguish between half-rate mode and full-rate mode during multiframe demodulation on the Um interface. The BTS distinguishes between odd multiframes and even multiframes during multiframe decoding. After the decoding, the BTS puts the decoded multiframes onto sub-channels 0 and 1 separately.
NOTE
Figure 2-136 shows sub-channels 0 and 1.
2.45.3.2 Channel Allocation on the Um Interface

Channel management is required during channel allocation, maintenance, adjustment, and release. For details on channel allocation on the Um interface, see 2.23 Channel Management. The BSC allocates full-rate channels or half-rate channels based on the service type, service requirement, and cell load. In addition, the BSC adjusts the proportion between full-rate channels and half-rate channels on the Um interface to meet the requirements of subscribers and improve the usage of radio resources. Thus, the BSC makes a tradeoff between network quality and network capacity. For details, see 2.28 Dynamic Channel Conversion.
2.45.3.3 Channel Allocation on the Abis Interface

The BSC decides whether to adjust full-rate channels and half-rate channels based on the load of the transmission resources on the Abis interface. Thus, when the resources are insufficient, the BSC can change some full-rate channels to half-rate channels in time. For details, see 2.28 Dynamic Channel Conversion. If Flex Abis is enabled in the BSC, the transmission resources on the Abis interface may prove to be insufficient, even before the radio resources on the Um interface are used up. Therefore, triggering half-rate assignment merely based on the resource load on the Um interface in the cell may affect the performance of the entire network. To solve this problem, the BSC uses an algorithm in which half-rate channel allocation is triggered by the load of the Abis interface in the case that TCHH Function Switch is set to Yes. For details, see 2.35 Flex Abis.
2.45.3.4 TRAU
To support half-rate speech, the BSC requires the support of TRAU(Transcoder & Rate Adaptation Unit). Multiple BSS TRAUs can be put into a TC resource pool. The TC resource pool contains the TRAUs, transmission resources on the Ater interface, and transmission resources on the A interface. These resources are shared, without fixed relations between them. The TRAU supports the coding and decoding of full-rate speech, half-rate speech, enhanced full-rate speech, and AMR speech. During a call, any one coding and decoding resource is selected from the resource pool.
2.45.3.5 AMR HR
The half-rate speech codec and the AMR HR speech codec have the same spectrum efficiency. The AMR HR speech codec, however, is more flexible and robust in codec rates. For the differences between the codecs with regard to power control and handover, see 2.64 Power Control and 2.46 Handover.
2.45.3.6 DTX
Discontinuous Transmission (DTX) is an effective method of prolonging MS battery life and reducing radio interference. The use of half-rate speech does not affect the use of DTX. The HR Use Downlink DTX parameter specifies whether to enable DTX for half-rate speech. DTX is enabled for half-rate service only when HR Use Downlink DTX is set to Yes. For details on DTX, see 2.25 Discontinuous Transmission and Discontinuous Reception.
2.45.3.7 Handover
Handover algorithm II includes the decision about AMR or non-AMR speech handover between half-rate channel and full-rate channel. For details, see 2.46 Handover.
2.45.3.8 Power Control

To support half-rate speech, the power control algorithm is adjusted accordingly. Huawei III power control algorithm uses different quality thresholds for different rates. For example, when a call is processed on half-rate channels, the algorithm uses the half-rate quality threshold; when the call is handed over to full-rate channels, the algorithm uses the full-rate quality threshold. For details, see 2.64 Power Control.
2.45.3.9 Local Switching

During a call, one party may use the full-rate speech codec while the other party may use the half-rate speech codec. In such a case, the BSC first changes the half-rate speech codec to the full-rate speech codec and then performs local switching. For details, see 2.19 BSS Local Switching.
2.45.3.10 Impact on KPIs

The main impact of half-rate speech on KPIs is as follows: l l If the full-rate mode is changed to the half-rate mode, the number of occupied timeslots is reduced and thus the interference to the entire network decreases. If the half-rate mode is enabled when the C/I of the entire network is greater than 10 dB, the speech quality of the entire network degrades. When the proportion of the half-rate traffic volume on the entire network increases, the speech quality on the entire network degrades accordingly. If the half-rate mode is enabled when the C/I of the entire network is smaller than 10 dB, the speech quality of the entire network is improved. When the proportion of the half-rate traffic volume on the entire network increases, the speech quality of the entire network is improved accordingly. The enabling of half-rate mode has no obvious impact on relevant KPIs.
2.45.3.11 Impact on Equipment

From a BSC perspective, half-rate speech requires higher processing capability than full-rate speech. In addition, the use of half-rate mode increases the capacity of the system and the CPU usage of the main processor of the BSC slightly.

Multiplexing Ratio of the LAPD Link
If the half-rate mode is enabled in a cell, the recommended multiplexing ratio of the carrier's LAPD link is 2:1, that is, the bandwidth of the LAPD link is 32 kbit/s.
Number of Carriers Supported by Each E1 Link

The number of carriers supported by each E1 link on the Abis interface depends on the network configuration, as described in the following list: l In the case that BTS local switching and Flex Abis are not enabled on the network If the half-rate mode is enabled for all the carriers on an E1 link, a maximum of 13 carriers can be supported by the E1 link. If both half-rate mode and full-rate mode are configured for the carriers on an E1 link, a maximum of 13 to 15 carriers can be supported by the E1 link. l In the case that BTS local switching and Flex Abis are enabled on the network The number of carriers supported by an E1 link depends on the proportion of calls processed through BTS local switching to all calls. Generally, a maximum of 13 to 18 carriers can be supported by an E1 link. l In the case of transmission optimization If the half-rate mode is enabled for all the carriers on an E1 link, a maximum of 20 carriers can be supported by the E1 link.
If both half-rate mode and full-rate mode are configured for the carriers on an E1 link, a maximum of 20 to 24 TRXs can be supported by the E1 link.
2.45.5 Parameters
This chapter describes the parameters related to half-rate speech. For the meaning of each parameter, see Table 2-118. For the default value, value ranges, and MML commands of each parameter, see Table 2-119. Table 2-118 Parameter description (1) Parameter Speech Version Description Speech version supported by a cell. This parameter specifies whether to enable the Abis resource adjustment TCHH function. It specifies whether the TCHH is preferentially allocated to the MS by the BSC6900, when Abis resources are insufficient. If the Abis resource load is greater than "Flex Abis Prior Choose Load Thred" or "Fix Abis Prior Choose Abis Load Thred" when the parameter is set to "YES", the BSC6900 preferentially allocates the TCHH to the MS. Whether the downlink DTX function is enabled for half rate (HR) calls. This function is also restricted by the DTX switch in the MSC. If the MSC allows the downlink DTX for calls and the value of this parameter(HRDLDTX) is YES, the downlink DTX is enabled for HR calls of cells.
TCHH Function Switch HR Use Downlink DTX
Issue 08 (2011-09-30)
658
Table 2-119 Parameter description (2) Paramete r Default Value GUI Value Range FULL_R ATE_VE R1, FULL_R ATE_VE R2, FULL_R ATE_VE R3, HALF_R ATE_VE R1, HALF_R ATE_VE R2, HALF_R ATE_VE R3, FULL_R ATE_VE R5 NO(NO), YES (YES) NO(No), YES(Yes) Actual Value Range Uni t MML Command Impac t
Speech Version TCHH Function Switch HR Use Downlink DTX
FULL_R ATE_VE R1-1&FU LL_RATE _VER2-1 &FULL_ RATE_V ER3-0&H ALF_RA TE_VER1 -1&HALF _RATE_V ER2-0&H ALF_RA TE_VER3 -0&FULL _RATE_V ER5-0
Full_rate_ Ver1, Full_rate_ Ver2, Full_rate_ Ver3, Half_rate_ Ver1, Half_rate_ Ver2, Half_rate_ Ver3, Full_rate_ Ver5
Non e Non e Non e
SET GCELLCCACCES S(Optional) SET BTSFLEXABISPA RA(Optional) SET GCELLBASICPAR A(Optional)
Cell
NO
NO, YES
BTS
YES
NO, YES
Cell
2.45.6 Counters
2.45.7 Glossary

l l l
Issue 08 (2011-09-30)
3GPP TS 46.002 "Half rate speech; Half rate speech processing functions" 3GPP TS 46.006 "Half rate speech; ANSI-C code for GSM half-rate speech codec" 3GPP TS 46.007 "Half rate speech; Test sequences for the GSM half rate speech codec"
l l l l l l l
3GPP TS 46.008 "Half rate speech; Performance Characterization of the GSM Half Rate speech codec" 3GPP TS 46.020 "Half rate speech; Half rate speech transcoding" 3GPP TS 46.021 "Half rate speech; Substitution and muting of lost frames for half rate speech traffic channels" 3GPP TS 46.022 "Half rate speech; Comfort noise aspects for the half rate speech traffic channels" 3GPP TS 46.041 "Half rate speech; Discontinuous Transmission (DTX) for half rate speech traffic channels" 3GPP TS 46.042 "Half rate speech; Voice Activity Detector (VAD) for half rate speech traffic channels" 3GPP TR 46.085 "Subjective tests on the interoperability of the Half Rate / Full Rate / Enhanced Full Rate (HR/FR/EFR) speech codecs, single, tandem and tandem free operation" 3GPP TS 46.001 "Full rate speech; Processing functions" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference BSC6900 Hardware Description
l l l l l l l l
2.46 Handover
2.46.1 Introduction
2.46.1.1 Scope
This document describes the overall procedure of Huawei handover algorithms and the specific handover decisions.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the handover feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows: l l l l 04(2010-11-30) 03(2010-01-20) 02(2009-09-30) 01(2009-06-30)
04(2010-11-30)
This is the fourth commercial release of GBSS9.0. Compared with issue 03 (2010-01-20) of GBSS9.0, issue 04 (2010-11-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description A description of 2.46.3.4.13 AMR Handover is optimized. A description of 2.46.3.4.9 Edge Handover is optimized. A description of 2.46.3.4.11 Inter-Layer Handover is optimized. A description of 2.46.3.4.12 PBGT Handover is optimized. A description of 2.46.3.5.10 Better Cell Handover is optimized. Editorial change None. Parameter Change The parameters added are as follows: l Enhanced Outgoing Cell Handover Allowed l Enhanced Outgoing Cell Handover Offset l Neighboring Cell Penalty Switch l Penalty Stop Level Threshold l Penalty Timer Length l Level Penalty Value on Neighboring Cell
None.
03(2010-01-20)
This is the third commercial release of GBSS9.0. Compared with issue 02 (2009-09-30) of GBSS9.0, issue 03(2010-01-20) of GBSS9.0 incorporates the changes described in the following table.
Change Type Feature change
Change Description A description of SDCCH Handover (Huawei handover algorithm I) and SDCCH Handover (Huawei handover algorithm II) is added. None.
Editorial change
None.
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, the following changes are incorporated: Change Type Feature change Change Description In 2.46.3.4.9 Edge Handover (handover algorithm I) and 2.46.3.5.8 Edge Handover (handover algorithm II), the parameters Edge HO Watch s Time, Edge HO Valid s Time, Edge HO AdjCell Watch s Time, and Edge HO AdjCell Valid s Time are changed. Parameter Change The parameters are changed as follows: l Handover algorithm I Edge HO Watch Time l Handover algorithm II Edge HO Watch Time l Handover algorithm I Edge HO Valid Time l Handover algorithm II Edge HO Valid Time l Edge HO AdjCell Watch Time l Edge HO AdjCell Valid Time Editorial change The structure of the document is optimized. None.
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table.
Issue 08 (2011-09-30)
662
Change Description The description of handover direction forecast during the target cell selection is added in 2.46.3.4.1 Quick Handover.
Parameter Change The parameters added are as follows: l Handover Direction Forecast Enable l Chain Neighbour Cell Type l Handover Direction Forecast Statistic Times l Handover Direction Forecast Last Times
Editorial change
None.
None.
2.46.2 Overview
The GSM network comprises multiple cells with continuous coverage. The handover technique is introduced into the GSM system to enable the users who are in motion to continue with the current call without interruption, thus optimizing the network performance. During a handover, the MS and BTS in service measure the conditions of uplink and downlink radio links respectively, record the measurement results into measurement reports (MRs), and then send the MRs to the BSC. The BSC determines whether to trigger a handover based on the MRs and the actual conditions of the radio network. Huawei handover algorithms (handover algorithm I and handover algorithm II) involve measurement and MR reporting, MR processing, handover decision, and handover execution.
NOTE
Huawei handover algorithms apply to the handovers on TCHs as well as the handovers on SDCCHs.
You can determine the handover algorithm used in a cell through Current HO Control Algorithm. Figure 2-137 shows the procedure for performing Huawei handover algorithms (including handover algorithm I and handover algorithm II).
Issue 08 (2011-09-30)
663
Figure 2-137 Procedure for performing Huawei handover algorithms
Handover Decision Based on Handover Algorithm I

Figure 2-138 shows the procedure of handover decision based on handover algorithm I.
Issue 08 (2011-09-30)
664
Figure 2-138 Procedure of handover decision based on handover algorithm I
In handover algorithm I, five types of handover decisions are defined: l Quick handover (including quick Power BudGet Handover (PBGT) handover and frequency offset handover). Good and stable services can be provided when the voice quality deteriorates during the fast movement of an MS. Quick handover is mainly applicable in the railway scenario. Emergency handover. Emergency handover can ensure the call continuity when the radio condition severely deteriorates. Theoretically, the emergency handover has a bigger deviation than other handovers in terms of the selection of the target cell. In a normal cell, frequent emergency handovers should be avoided. Enhanced dual-band network handover. In an enhanced dual-band network, the resources in the overlaid DCS1800 cell and underlaid GSM900 cell can be shared during the
Issue 08 (2011-09-30)
665
assignment and handover procedures. That is, the calls in the high-traffic GSM900 cell can be handed over to the low-traffic DCS1800 cell to balance traffic. l l Load handover. Load handover enables the system load to be balanced among multiple cells so that the system performance can be ensured. Normal handover. Normal handover ensures good services when an MS is moving.
Figure 2-139 shows the handovers provided in Figure 2-138 and their priorities in handover algorithm I. Figure 2-139 Handover decisions based on handover algorithm I
Issue 08 (2011-09-30)
666
Handover Decision Based on Handover Algorithm II

Figure 2-140 shows the procedure of handover decision based on handover algorithm II. Figure 2-140 Procedure of handover decision based on handover algorithm II
Issue 08 (2011-09-30)
667
In handover algorithm II, three types of handover decisions are defined, as shown in Figure 2-141. Figure 2-141 Handover decisions based on handover algorithm II
Handover Execution
BTS power lift for handover function determines whether the BTS of the serving cell transmits signals at the maximum power during a handover. The BSC maximizes the transmit power of the BTS before sending a handover command to the MS. The BSC does not adjust the BTS power during the handover to ensure the success of the handover.

2.46.3.1 Measurement Report Processing
Measurement report processing involves measurement report interpolation and filtering.
NE Selection for Measurement Report Processing

The processing can be performed either on the BSC side or on the BTS side. l l If MR.Preprocessing is set to No, then the processing is performed on the BSC side. If MR.Preprocessing is set to Yes, then the processing is performed on the BTS side. By setting the parameters Transfer Original MR, Transfer BTS/MS Power Class, and Sent Freq.of preprocessed MR, you can specify the contents of the MRs to be provided and the period during which the MRs are provided. This decreases the signaling traffic on the Abis interface and the traffic volume processed by the BSC.
Data Selection for Measurement Report

The MR can be classified into enhanced MR and normal MR. The parameter Measurement Report Type determines the type to be used. In the MR, the TCH measurement of the serving cell is classified into FULL SET and SUB SET.
Measurement Report Interpolation

The neighboring cell indexes are found on the basis of the BCCH frequencies and BSICs provided by the MS. Then, the uplink and downlink measurement results are obtained from the measurement reports. l l If measurement reports are issued continuously, they are directly added to the measurement report list. If measurement reports are not issued continuously and the number of lost measurement reports is smaller than the value of Allowed MR Number Lost, the system performs operations as follows: For the serving cell, the handover algorithm I performs the linear interpolation for the MRs. The lowest values are applied to the interpolation of MRs by the handover algorithm II according to the protocols; that is, level 0 (-110 dBm) and quality 7 are applied in the interpolation. For the neighboring cell, the lowest value is applied to the lost level value according to the protocols; that is, level 0 (-110 dBm) is applied in the interpolation.
NOTE
If no MR is reported because the RX level in the neighboring cell is too low, level 0 (-110 dBm) is applied in the interpolation.
If measurement reports are not issued continuously and the number of lost measurement reports is greater than the value of Allowed MR Number Lost, the previous measurement reports are discarded. When new measurement reports are issued, calculation is done again.
Measurement Report Filtering

Filtering is performed on measurement reports obtained continuously from the measurement report list. Averaging is performed on uplink/downlink RX level, uplink/downlink RX quality, Timing Advance(TA), Radio Quality Indication(RQI), BTS power, 2G neighboring cell level, and the Common PIlot CHannel(CPICH ), Received Signal Code Power(RSCP), and Ec/No of neighboring 3G cell. The averaging minimizes the effect on the result of handover decision due to sudden changes in the measurement values. Power control compensation needs to be performed for the downlink RX level of the serving cell by the handover algorithm II. If you compare the RX level of the serving cell after the power control with that of all BCCH TRXs of the neighboring cell, there is no mapping between them. In situations where the cells overlap severely, the handover is easily triggered, thus causing the ping-pong handover. After the power control compensation is performed, the RX level of the serving cell can reflect the coverage condition of the BCCH TRX of the serving cell. The power control compensation of the serving cell is performed after the interpolation processing and before the filtering processing. In general, the compensation of power control is calculated by adding the downlink RX level of the serving cell and twice the current downlink transmit Power Level of the BTS. The number of consecutive measurement reports required for filtering is determined by the measurement object and channel type. See Table 2-120 for details.
Issue 08 (2011-09-30)
669
Table 2-120 Parameters related to the number of measurement reports Measurement Object Receive level of the serving cell Quality of the serving cell TA of the serving cell Receive level of the neighboring cell Power of the BTS in the serving cell RQI Channel Type SDCCH TCH SDCCH TCH TCH SDCCH BCCH SDCCH TCH Filter Length for TCH Level TCH Filter Length for TCH Qual Parameter Filter Length for SDCCH Level Filter Length for TCH Level Filter Length for SDCCH Qual. Filter Length for TCH Qual Filter Length for TA TA filter length for SDCCH level Filter Length for Ncell RX_LEV NCell filter length for SDCCH level
If consecutive measurement reports are insufficient, the filtering fails. The handover decision is not performed.
2.46.3.2 Handover Preprocessing Handover Penalty

According to the neighboring cell information in the measurement report and the parameters, the system performs handover preprocessing and adjusts the priorities of the neighboring cells. The handover penalty is performed after successful fast-moving micro cell handover, TA handover, BQ handover, fast-moving micro cell handover, OL subcell to UL subcell handover within an enhanced concentric cell, and after the handover failures. In handover algorithm II, in addition to the situations mentioned above, the handover penalty is also performed after successful or failed load handover and interference handover.
NOTE
In handover decision procedure of handover algorithm II, the handover penalty is performed after the network characteristics adjustment and before the emergency handover decision.
After the quick handover, TA handover, Bad Quality(BQ) handover, or load handover (in handover algorithm II) is successfully performed, the penalty level is subtracted from the actual RX level of the original cell during the penalty period. Table 2-121 lists the parameters related to handover penalty.
Issue 08 (2011-09-30)
670
Table 2-121 Parameters related to handover penalty Handover Quick handover Parameter Quick Handover Punish Time Quick Handover Punish Value TA Handover Penalty Level after TA HO Penalty Time after TA HO BQ Handover Penalty Level after BQ HO Penalty Time after BQ HO Load handover (handover algorithm II) l Penalty Time on Load HO Penalty Value on Load HO
After the fast-moving micro cell handover is successfully performed, penalty is performed on all the neighboring cells of the micro cell. Related parameters are Penalty on Fast Moving HO and Penalty Time on Fast Moving HO. If an MS fails to initiate an intra-cell AMR TCHF to TCHH handover, it cannot initiate another intra-cell AMR TCHF to TCHH handover within Penalty Time after AMR TCHF-H HO Fail. In handover algorithm II, after the interference handover is initiated, this handover is not allowed to be initiated again within Penalty Time on Interfere HO regardless of whether the handover is successful or not. After the OL subcell to UL subcell handover within an enhanced concentric cell is successful, the handover from UL subcell to OL subcell is not allowed within Penalty Time of UtoO HO. After the OL cell to UL cell handover in the enhanced dual-band network is successful, the handover from UL cell to OL cell is not allowed within Inter UL/OL Subcells HO Penalty Time. After the handover fails, different penalties are performed on the target cell based on the causes: If the handover to a neighboring 2G or 3G cell fails, the actual RX level of the target cell is subtracted by Penalty Level after HO Fail for neighboring cell ranking during the penalty.
NOTE
Based on the handover failure cause, the penalty time could be UmPenaltyTimer, RscPenaltyTimer, or CfgPenaltyTimer.
If the OL subcell to UL subcell handover within a concentric cell fails, the handover from OL subcell to UL subcell is not allowed within Penalty Time after OtoU HO Fail. If the UL subcell to OL subcell handover within a concentric cell fails, the handover from UL subcell to OL subcell is not allowed within Penalty Time after UtoO HO Fail.
Basic Ranking
Basic ranking is performed after handover penalty to generate a candidate cell list in descending order taking the following information into account: RX levels of the serving cell and
neighboring cells carried in the MRs, hysteresis, usage of TCHs in the neighboring cells, and so on. l In the case of non-directed retry, if an MS in an external BSC cell occupies an SDCCH and Inter-BSC SDCCH HO ALLowed is set to No, then this cell should be removed from the candidate cell list. In other words, the handover to this external BSC cell is prohibited. If a neighboring 2G cell and the serving cell are controlled by the same BSC and the TCH usage of the neighboring cell is 100%, then the neighboring cell should be removed from the candidate cell list; that is, the handover to this neighboring cell is prohibited. If the downlink RX level of a neighboring 2G cell is lower than the sum of Min DL Level on Candidate Cell and Min Access Level Offset, then the neighboring cell should be removed from the candidate cell list; that is, the handover to this neighboring cell is prohibited. If the uplink RX level of a neighboring 2G cell is lower than the sum of Min UL Level on Candidate Cell and Min Access Level Offset, then the neighboring cell should be removed from the candidate cell list; that is, the handover to this neighboring cell is prohibited. If a neighboring 3G cell is an FDD cell, the cell is processed according to FDD REP QUANT: If FDD REP QUANT is set to Ec/N0, and the Ec/N0 of a neighboring cell is lower than Min Ec/No threshold, the neighboring cell should be removed from the candidate cell list; that is, the handover to this neighboring cell is prohibited. If FDD REP QUANT is set to RSCP, and the RSCP of a neighboring cell is lower than Min RSCP threshold, the neighboring cell should be removed from the candidate cell list; that is, the handover to this neighboring cell is prohibited. l If a neighboring 3G cell is a TDD cell and the RSCP after penalty is lower than the Min RSCP threshold, the neighboring cell should be removed from the candidate cell list; that is, the handover to this neighboring cell is prohibited. Calculate the difference between the downlink RX level of the neighboring cells and the downlink RX level of the serving cell. Based on the difference, rank the neighboring cells in descending order.
Network Characteristics Adjustment

Network characteristics adjustment is a process in which the position of each cell in the candidate cell list is determined based on the related network information. Network characteristics adjustment provides the final candidate cell list for handover decision. After the network characteristics adjustment, the final candidate cell list (including neighboring cells and serving cell) is generated. The candidate cells are ranked in descending order by priority. Then, the handover decision procedure starts. In handover algorithm II, the emergency handover decision is made after the network characteristics adjustment. After the emergency handover decision, Penalty Value on Load HO is subtracted from the level of the original cell within Penalty Time on Load HO if the load handover is successful. The level of the target cell changes after the penalty of load handover; then, the network characteristics needs to be readjusted. In handover algorithm I, all related factors are adjusted in network characteristics adjustment phase; in handover algorithm II, some of the factors are adjusted before the emergency handover decision procedure is initiated.
Forced Handover
If the forced handover is triggered, the subsequent handover decisions are not performed. The purpose of the forced handover is as follows: l l If no TCH is available in the serving cell during the MS access process, the directed retry procedure is performed when Directed Retry is set to Yes. When BTS maintenance is performed, the MSs under control of the related BTS should be handed over to the cells controlled by a functional BTS to ensure that no call drop occurs during BTS maintenance.
The forced handover is classified into these four types: l l l l Outgoing cell handover (direct retry) Outgoing BTS handover Outgoing BSC handover Specified target cell list handover
2.46.3.3 Forced Handover

A forced handover does not require a handover decision. A forced handover is triggered in the following scenarios: l l If no TCH is available in the serving cell which the MS attempts to access and Directed Retry Permitted is set to Yes, the BSC triggers a directed retry procedure. When a BTS is under maintenance, the MSs served by the BTS should be handed over to the cells controlled by a functional BTS. This ensures that no call drop occurs during the BTS maintenance.
Directed Retry
When the MS initiates a call, after the BSC receives an ASSIGN REQ message from the MSC, the BSC determines an assignment mode based on the load of the serving cell.
NOTE
Assignment mode is categorized into normal assignment procedure, mode modification procedure, and directed retry procedure. The commands issued by the BSC vary according to the procedure. l l l For a normal assignment procedure, the BSC activates a channel and issues a channel assignment command. For a mode modification procedure, the BSC issues a mode modification command. For a directed retry procedure, the BSC issues a handover command.
If the serving cell is so overloaded that new calls cannot be admitted or admitting new calls will affect ongoing services, the BSC triggers a directed retry procedure. By using the directed retry, the MS is handed over to the target cell and part of the traffic in the serving cell is distributed to the target cell. This avoids traffic congestion in the serving cell. Figure 2-142 shows the procedure for a directed retry decision.
Issue 08 (2011-09-30)
673
Figure 2-142 Procedure for a directed retry decision
When Assignment Cell Load Judge Enable is set to DISABLE(Disable), the BSC triggers a directed retry procedure after completing basic ranking if the load of the serving cell exceeds 100%. As shown in Figure 2-142, directed retry is categorized into enhanced dual-band network directed retry and normal directed retry.
Enhanced Dual-Band Network Directed Retry

In an enhanced dual-band network, two cells form a group and the MS camps on one of the two cells. After the directed retry is triggered, the MS is handed over to the other cell. For details on the conditions of triggering an enhanced dual-band network directed retry, see sections 3.3.7 "Enhanced Dual-Band Network Handover" and 3.4.6 "Enhanced Dual-Band Network Handover."
Target Cell Selection in a Normal Directed Retry Procedure

The target cell must have the highest priority in the candidate cell list after handover preprocessing. In addition, the target cell must meet the following conditions: l l l l The serving cell does not function as a target cell. Load of the candidate neighboring cells Directed Retry Load Access Threshold In handover algorithm II, serving cell level < receive level of neighboring cells < serving cell level + Directed Retry Handover Level Range. In handover algorithm I, receive level of neighboring cells Min Power Level For Directed Retry.
2.46.3.4 Handover Decision Based on Handover Algorithm I

According to the emergency condition of an MS in the network, the handover decision based on handover algorithm I is made in the following order: quick handover, emergency handover, enhanced dual-band network handover, load handover, and normal handover. Handover decision based on handover algorithm I involves the following procedures: l l Determining whether the serving cell meets the triggering conditions Selecting corresponding candidate cells
In handover algorithm I, Inter-rat HO Preference specifies whether a neighboring 2G cell or a neighboring 3G cell is preferred. l When Inter-rat HO Preference is set to Preference for 2G Cell: A neighboring 2G cell is preferred. If the candidate cell list contains suitable neighboring 3G cells but no suitable neighboring 2G cells, a neighboring 3G cell is selected. l When Inter-rat HO Preference is set to Preference for 3G Cell: A neighboring 3G cell is preferred. If the candidate cell list contains suitable neighboring 2G cells but no suitable neighboring 3G cells, a neighboring 2G cell is selected. l When Inter-rat HO Preference is set to Preference for 2G Cell: If the RX level of a candidate 2G cell is lower than or equal to HO Preference Threshold for 2G Cell, a neighboring 3G cell is preferred. If the triggering conditions of emergency handover are met and there is at least one candidate cell, then the emergency handover timer Min Interval for Emerg. HO is started. Another emergency handover decision can be performed only when Min Interval for Emerg. HO times out.
?.1. Quick Handover

Quick handover aims to increase the handover success rate of an MS moving at a high speed and to ensure the call continuity and low call drop rate. Quick handover applies to the scenario where an MS moves fast along an urban backbone road, a selected route, or a high-speed railroad.
Quick Handover Types

Quick handover consists of frequency offset handover and quick PBGT handover. l
Issue 08 (2011-09-30)
Frequency offset handover

Whether the MS is moving away from the serving cell is determined based on the frequency offset information provided by an MS moving at a high speed. Frequency offset handover decision is made according to the uplink/downlink RX level of the serving cell and the path loss of neighboring cells. l Quick PBGT handover Quick PBGT handover decision is made according to the path loss of neighboring cells. For quick handover, the handover response speed is enhanced by: l l l l Accurately calculating the moving speed of the MS Derestricting the interval between handover decisions Reducing the number of measurement reports for the handover decision Introducing the filtering
Quick Handover Preparation

The preparation for quick handover involves the following aspects: l Frequency offset is decoded from the measurement report. Frequency offset of the MS is obtained from the uplink measurement report that the BTS sends to the BSC. l filtering is performed on the measurement report.
Triggering Conditions
During handover decision, it is first determined whether the triggering conditions of frequency offset handover are met. When the BTS cannot send the frequency offset information or the reported frequency offset information is invalid, quick PBGT handover is triggered, provided that other conditions of frequency offset handover are met. If Quick Handover Enable is set to Yes, the triggering conditions of quick handover are as follows: l The MS is moving away from the serving cell (the frequency offset in the measurement result is a negative value) and the moving speed of the MS is greater than Quick Move Speed Threshold. The filtered uplink level of the serving cell is lower than Quick Handover Up Trigger Level. The compensated downlink level of the serving cell is lower than Quick Handover Down Trigger Level. The path loss of configured chain neighboring cells is lower than the specified threshold of the path loss of the serving cell. In other words, PBGT(n) is greater than or equal to 0.
l l l
The triggering conditions of quick handover are as follows: l If the last three conditions are met simultaneously, the decision is made as follows: If the first condition is met, a frequency offset handover is performed. If the first condition is not met, a quick PBGT handover is performed. l
Issue 08 (2011-09-30)
If all the last three conditions are not met, quick handover is not triggered.
Target Cell Selection

The target cell must be a chain neighboring cell of the serving cell. The target cell can be obtained through the setting of Chain Neighbor Cell. If Handover Direction Forecast Enable is set to Yes, a neighboring cell in the moving direction of the MS is selected preferentially. To forecast the moving direction of the MS, the direction of a chain neighboring cell (A or B) compared with the serving cell is specified by Chain Neighbour Cell Type. If the number of times that the MS is handed over to neighboring cells in the same direction (B for example) is greater than or equal to Handover Direction Forecast Last Times when the handover time reaches Handover Direction Forecast Statistic Times, then the MS is inferred to be moving towards the B direction. Subsequently, the MS is preferentially handed over to the neighboring cell whose Chain Neighbour Cell Type is B.
Limitations
The limitations on quick handover are as follows: l l l The serving cell cannot be selected as the target cell. The candidate cells for quick handover must be chain neighboring cells of the serving cell. After a quick handover is successful, the penalty is performed on the original cell during the penalty time to prevent an immediate handover back to the original cell. The penalty time and penalty value are specified by Quick Handover Punish Time and Quick Handover Punish Value respectively.
?.2. TA Handover
TA handover is a type of emergency handover. The TA handover decision is made according to the TA value reported by the MS. The TA value of a normal cell ranges from 0 to 63 and that of an extended cell ranges from 0 to 229. The TA can be stepped up or down in steps of 553.5 m. The TA value of 63 corresponds to a distance of 35 km.
TA handover is triggered when the following conditions are met: l l TA HO Allowed is set to Yes. Filtered TA value in the measurement report provided by the MS is greater than or equal to TA Threshold.
The TA handover can be triggered only when the preceding two conditions are met simultaneously.
NOTE
From the perspective of the triggering conditions of TA handover, TA can be regarded as a limitation to the size of a cell.

The target cell should have the highest priority in the candidate cell list after handover preprocessing. In addition, the target cell should meet the following conditions:
l l
The serving cell cannot be selected as the target cell. If TA Threshold of a co-site neighboring cell is lower than or equal to the TA Threshold of the serving cell, a handover to the neighboring cell is prohibited.
If the triggering conditions of TA handover are met but the candidate 2G cells are not suitable, the following operations are performed: l If a neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to Yes, and if the MS supports the 2G/3G inter-RAT handover, the 2G/3G inter-RAT handover is performed. If no neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to No, or if the MS does not support the 2G/3G inter-RAT handover, the decision on whether to initiate another type of emergency handover is made.
Limitations
After the TA handover is successful, the penalty is performed on the original cell. During Penalty Time after TA HO, Penalty Level after TA HO is subtracted from the level of the original cell to prevent an immediate handover back to the original cell.
?.3. BQ Handover
BQ handover is a type of emergency handover in which the system makes the decision based on the uplink/downlink RX quality on the Um interface. The RX quality is measured in bit error rate (BER). The BSC measures the quality of a radio link based on the quality class in the measurement report. The probable cause of an increase in BER is that the signal power is too low or the channel interference increases.
If BQ HO Allowed is set to Yes, the triggering conditions of BQ handover are as follows: l l The uplink RX quality is greater than or equal to the uplink RX quality threshold of the serving cell. The downlink RX quality is greater than or equal to the downlink RX quality threshold of the serving cell.
The BQ handover is triggered when either of the preceding conditions is met. The parameters for specifying the uplink and downlink RX quality thresholds are as follows: l For non-AMR calls, the parameter for specifying the uplink RX quality threshold is UL Qual. Threshold and the parameter for specifying the downlink RX quality threshold is DL Qual. Threshold. For AMR FR calls, the parameter for specifying the uplink RX quality threshold is UL Qual. Limit for AMR FR and the parameter for specifying the downlink RX quality threshold is DL Qual. Limit for AMR FR. For AMR HR calls, the parameter for specifying the uplink RX quality threshold is UL Qual. Limit for AMR HR and the parameter for specifying the downlink RX quality threshold is DL Qual. Limit for AMR HR.
Issue 08 (2011-09-30)

The target cell should have the highest priority in the candidate cell list after handover preprocessing. In addition, the target cell should meet the following conditions: l If the target cell is a neighboring cell, the RX level of the target cell must meet the following condition: Filtered downlink RX level of the target cell > Filtered downlink RX level of the serving cell after compensation + (Inter-cell HO Hysteresis of the serving cell configured for the neighboring cell - 64) - (BQ HO Margin 64)
NOTE
In handover algorithm I, if there is only one cell in the candidate cell list and the cell is a neighboring cell, then the preceding condition need not be met.
In handover algorithm I, if there is no neighboring cell, Intracell HO Allowed is set to Yes, and the serving cell is not in the intra-cell handover penalty state, then the MS is handed over to the serving cell. A channel with different frequency band, different frequency, different TRX, or different timeslot is preferred (priority: different frequency band > different frequency > different TRX > different timeslot).
If the triggering conditions of BQ handover are met but the candidate 2G cells are not suitable, the following operations are performed: l If a neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to Yes, and if the MS supports the 2G/3G inter-RAT handover, the 2G/3G inter-RAT handover is performed. If no neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to No, or if the MS does not support the 2G/3G inter-RAT handover, the decision on whether to initiate another type of emergency handover is made.
Limitations
After the BQ handover is successful, the penalty is performed on the original cell. During Penalty Time after BQ HO, Penalty Level after BQ HO is subtracted from the level of the original cell to prevent an immediate handover back to the original cell.
?.4. Rapid Level Drop Handover

Rapid level drop handover is a type of emergency handover. In edge handover and PBGT handover, the mean value filtering and P/N decision methods are not responsive to short-period rapid level drop. Therefore, to solve the rapid level drop problem, the finite impact response filtering can be performed on the original RX level. This filtering method is responsive to the rapid level drop based on the drop slope of the original RX level.
If Rx_Level_Drop HO Allowed is set to Yes, the triggering conditions of rapid level drop handover are as follows: l l Filtered uplink level < Edge HO UL RX_LEV Threshold A1 x C(nt) + A2 x C(nt - t) + A3 x C(nt - 2t) + + A8 x C(nt - 7t) < B Here, A1 indicates Filter Parameter A1, A2 indicates Filter Parameter A2, A3 indicates Filter Parameter A3, A4 indicates Filter Parameter A4, A5 indicates Filter Parameter
A5, A6 indicates Filter Parameter A6, A7 indicates Filter Parameter A7, and A8 indicates Filter Parameter A8. B indicates Filter Parameter B.

The target cell should have the highest priority in the candidate cell list after handover preprocessing. In addition, the target cell should meet the following conditions: l l The target cell has a higher priority than the serving cell. The serving cell cannot be selected as the target cell.
If the triggering conditions of rapid level drop handover are met but the candidate 2G cells are not suitable, the following operations are performed: l If a neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to Yes, and if the MS supports the 2G/3G inter-RAT handover, the 2G/3G inter-RAT handover is performed. If no neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to No, or if the MS does not support the 2G/3G inter-RAT handover, the decision on whether to initiate another type of emergency handover is made.
?.5. Interference Handover

In handover algorithm I, interference handover is a type of emergency handover. Interference handover helps protect the interfered calls and reduce the network interference. It is applicable to scenarios with interference. In handover algorithm I, the difference between interference handover and BQ handover is that in BQ handover the bad quality resulting from both coverage and interference is checked. In interference handover, the bad quality resulting from coverage is not checked.
If Interference HO Allowed is set to Yes, the triggering conditions of interference handover are as follows: l l The filtered value of uplink RX quality is greater than or equal to the specified RX quality threshold at the current uplink RX level. The filtered value of downlink RX quality is greater than or equal to the specified RX quality threshold at the current downlink RX level.
The interference handover is triggered if either of the previous conditions is met. The parameters for specifying the uplink and downlink RX quality thresholds are as follows: l l For non-AMR FR calls, the parameter for specifying the RX quality threshold is Interfere HO Qual. Thresh n for Non-AMR FR, where 1 n 12. For AMR FR calls, the parameters for specifying the RX quality threshold are Interfere HO Qual. Thresh n for Non-AMR FR (1 n 12) and Interfere HO Qual. Thresh Offset for AMR FR. If n = 1, the RX quality threshold is Interfere HO Qual. Thresh 1 for Non-AMR FR.
If 2 n 12, the RX quality threshold is Interfere HO Qual. Thresh n for NonAMR FR + Interfere HO Qual. Thresh Offset for AMR FR.

In handover algorithm I, the target cell should have the highest priority in the candidate cell list. In addition, the target cell should meet the following conditions: l If Intracell HO Allowed is set to Yes and the intra-cell handover penalty timer expires, the serving cell can be selected as the target cell.
NOTE
When a number of consecutive intra-cell handovers occur, Forbidden time after MAX Times is triggered and the intra-cell handover is prohibited in the corresponding period.
If the filtered level of a neighboring cell after handover penalty Inter-layer HO Threshold of the neighboring cell + Adjacent Cell Inter-layer HO Hysteresis - 64, this neighboring cell can serve as the target cell.
If the triggering conditions of interference handover are met but the candidate 2G cells are not suitable, the following operations need to be performed: l If a neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to Yes, and if the MS supports the 2G/3G inter-RAT handover, the 2G/3G inter-RAT handover is performed. If no neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to No, or if the MS does not support the 2G/3G inter-RAT handover, the decision on whether to initiate another type of emergency handover is made.
?.6. Handover Due to No Downlink Measurement Report

Handover due to no downlink measurement report is performed on the basis of the uplink quality. The purpose is to ensure the call continuity and minimize the possibility of call drops. Handover due to no downlink measurement report is generally caused by adverse radio environment on the uplink. In this case, the requirements of the filtering algorithm cannot be met, so other handover decisions cannot be performed.
In handover algorithm I, the triggering conditions of handover due to no downlink measurement report are as follows: l l l l l No Dl Mr.HO Allowed is set to Yes. There is no downlink information in the measurement report of the call. The filtered value of uplink quality is greater than or equal to No Dl Mr.Ul Qual HO Limit. The number of lost downlink MRs is smaller than Cons.No Dl Mr.HO Allowed Limit. For TCH, the number of saved MRs with uplink quality value is greater than Filter Length for TCH Qual; for SDCCH, the number of saved MRs with uplink quality value is greater than Filter Length for SDCCH Qual..
When all the previous conditions are met, the handover due to no downlink measurement report is triggered.

In handover algorithm I, the conditions for selecting the target cell are as follows: l l l The ranked neighboring cells recorded in the last complete measurement report are saved as candidate cells. Preferably a neighboring cell is selected as the target cell. If no neighboring cell is available, the serving cell is selected as the target cell.
?.7. Enhanced Dual-Band Network Handover

Enhanced dual-band network handover is performed based on the traffic volume of the overlaid and underlaid cells and based on the receive level. Enhanced dual-band network handover is classified into the following types: l l l Handover due to high load in the underlaid cell Handover due to low load in the underlaid cell Handover due to MS movement to the border of the overlaid cell
Triggering Conditions of Handover Due to High Load in the Underlaid Cell

The triggering conditions of the handover due to high load in the underlaid cell are as follows: l l l l l l l The two cells are in the enhanced dual-band network and Load HO Allowed is set to Yes. The MS supports the frequency band on which the overlaid cell operates. The handover due to high load in the underlaid cell is performed only on TCHs. The load in the underlaid cell is higher than or equal to UL Subcell General Overload Threshold. The load in the overlaid cell is lower than Inner Cell Serious OverLoad Thred. The system traffic volume is lower than or equal to Subcell HO Allowed Flow Control Level. The current call is within the handover margin. the receive level is greater than or equal to Incoming OL Subcell HO Level TH and smaller than or equal to Incoming OL Subcell HO Level TH + handover margin.
When all the preceding conditions are met, the handover due to high load in the underlaid cell is triggered. If the load of the underlaid subcell in the cell is higher than or equal to UL Subcell Serious Overload Threshold, then the handover margin is adjusted in a period of UL Subcell Load Hierarchical HO Periods subtracted by MOD Step LEN of UL Load HO Period. The step length for handover margin adjustment is specified by Step Length of UL Subcell Load HO.
Triggering Conditions of Handover Due to Low Load in the Underlaid Cell

The triggering conditions of the handover due to low load in the underlaid cell are as follows: l l The load in the underlaid cell is lower than UL Subcell Lower Load Threshold. The system traffic volume is lower than or equal to Subcell HO Allowed Flow Control Level.
Issue 08 (2011-09-30)
The current call is within the handover margin, and the Incoming OL Subcell HO Level TH plus the handover margin is greater than or equal to the receive level, which is also greater than or equal to the Outgoing OL Subcell HO Level TH.
When all the preceding conditions are met, the handover due to low load in the underlaid cell is triggered. If the load of the underlaid subcell is lower than UL Subcell Lower Load Threshold for a specified period, then the handover margin is adjusted in a period of OL Subcell Load Diversity HO Period. The step length for handover margin adjustment is specified by Step Length of OL Subcell Load HO.
Triggering Conditions of Handover Due to MS Movement to the Border of the Overlaid Cell
The triggering conditions of the handover due to MS movement to the border of the overlaid cell are as follows: l l SS(s) < Thdouter SS(u) - SS(n) < ATCB_THRD - ATCB_HYST Here, SS(s): specifies the filtering compensated downlink RX level in the serving cell. Thdouter: specifies Outgoing OL Subcell HO Level TH. SS(u): specifies the downlink level (power compensation is performed on the downlink level based on the measurement) of the underlaid cell where the call is originated. If the SS(u) value cannot be obtained, you can infer that the decision of enhanced dual-band network handover is not performed and the decision condition is met by default. SS(n): The best neighboring cell is the one whose measured BCCH level is the highest among neighboring cells. SS(n) is the signal level of the best neighboring cell that operates on the same frequency band, locates at the same layer, and has the same priority as the underlaid cell but is not co-sited with the underlaid cell. If such a neighboring cell is not available, the value of SS(n) is -110 dBm. ATCB_THRD: specifies Distance Between Boundaries of Subcells. ATCB_HYST: specifies Distance Hysteresis Between Boundaries. Handover due to MS movement to the border of the overlaid cell is triggered if either of the preceding conditions is met.
NOTE
l In the adapter distance to cell border(ATCB) handover algorithm, the border between the overlaid and underlaid cells is determined according to the signal strength of the serving cell and that of neighboring cells. If SS(s) = SS(n), the system considers that the MS is located at the border of the underlaid cell. If SS(s) - SS(n) > ATCB_THRD, the system considers that the MS is located in the coverage area of the overlaid cell. The coverage area of the overlaid cell is determined according to different networking and coverage conditions of the existing network. In addition, the overlaid cell of the serving cells and the overlaid cell of the neighboring cells will not overlap regardless of the distance between BTSs. l The handover margin specifies the range of signal level. In the case of overlaid/underlaid load handover on the enhanced dual-band network, the MSs whose downlink levels are within the handover margin are handed over level by level.

The requirements for target cell selection in the enhanced dual-band network are as follows:
l l l
For the handover due to high load in the underlaid cell, the MS must be handed over to the overlaid cell. For the handover due to low load in the underlaid cell, the MS must be handed over to the underlaid cell. For the handover due to MS movement to the border of the overlaid cell, the MS is handed over to the neighboring cell that ranks first among neighboring cells. The MS should not be handed over to the cell that ranks after the serving cell. Generally, the target cell is the underlaid cell. The target cell can also be another neighboring cell.
Limitations
The limitations on the handover due to high load in the underlaid cell are as follows: l l l If the cell where the call is located is on an enhanced dual-band network, Cell Inner/Extra Property is set to Extra(Extra). The Load HO Allowed parameter should be set. The maximum range of the handover margin is from 63 to Incoming OL Subcell HO Level TH. The MS with the highest receive level is handed over first.
The limitations on the handover due to low load in the underlaid cell are as follows: l l l If the cell where the call is located is on the enhanced dual-band network, Cell Inner/Extra Property is set to Inner(Inner). The Load HO of OL Subcell to UL Subcell parameter should be set. The maximum range of the handover margin is from 63 to Outgoing OL Subcell HO Level TH. The MS with the lowest receive level is handed over first.
The limitations on the handover due to MS movement to the border of the overlaid cell are as follows: l If the cell where the call is located is on the enhanced dual-band network, Cell Inner/Extra Property is set to Inner(Inner).
Impact of the Enhanced Dual-Band Network Handover on the Existing Algorithm

The impact of the enhanced dual-band network handover on the existing algorithm is as follows: l On the enhanced dual-band network, the MS should not be handed over to a cell in the same underlaid/overlaid cell group when the load handovers between the overlaid cell and the underlaid cell (specified by Load HO Allowed and Load HO of OL Subcell to UL Subcell) are allowed. This is to prevent a load handover of a normal cell from colliding with a load handover between the overlaid cell and the underlaid cell on the network. The PBGT handover algorithm may cause inter-cell handover; thus, the MS should not be handed over to the cell in the same group in the case of PBGT handover between cells on the enhanced dual-band network.
?.8. Load Handover

In the network, some cells carry heavy load whereas the overlapping upper-layer cells and the neighboring cells may carry light load. To balance the load of these cells, the load handover is required. In a load handover procedure, some load in heavy-load cells is switched to light-load cells. Meanwhile, the load in neighboring cells is not switched to heavy-load cells.
Load handover can be performed between cells at different layers. Figure 2-143 shows the details.
NOTE
For details about the inter-RAT load handover, see the 2.4 2G/3G Interoperability feature.
Figure 2-143 Load handover between cells
To perform load sharing, increase Edge HO DL RX_LEV Threshold so that the load at the border of a cell is switched to a neighboring cell with light load. Whether a cell carries heavy load or light load is determined by the traffic volume in the cell, that is whether the traffic volume (generally TCH usage) in the cell exceeds the preset threshold. l l If the traffic volume in a cell is greater than Load HO Threshold, you can infer that the load in this cell is heavy. The load handover algorithm needs to be enabled. If the traffic volume in a cell is lower than Load handover Load Accept Threshold, you can infer that the load in this cell is light and the cell can receive load from the heavy-load cells.
Load handover may lead to many handovers. Therefore, the load of the system CPU should be considered before load handover is performed. In other words, the system traffic volume should be taken into account. In addition, to prevent too many MSs from being handed over at a time, load handover is performed step by step. In other words, the edge handover threshold is increased on the basis of Load HO Step Level (CLS_Ramp) and Load HO Step Period (CLS_Period). When the increase in the edge handover threshold equals Load HO Bandwidth (CLS_Offset), the edge handover threshold is not increased any more. See Figure 2-144 for details.
Issue 08 (2011-09-30)
685
Figure 2-144 Load handover
If Load Handover Support is set to Yes, the triggering conditions of load handover are as follows: l l The CPU usage of the system is less than or equal to System Flux Threshold for Load HO. The current load of the serving cell is greater than or equal to Load HO Threshold.

The conditions for selecting the target cell are as follows: l l l Filtered RX level after handover penalty Inter-layer HO Threshold + Adjacent Cell Inter-layer HO Hysteresis - 64 The serving cell cannot be selected as the target cell. If the target cell and the serving cell are in the same BSC, a load handover is performed when the current load of the target cell is lower than Load handover Load Accept Threshold. If the target cell and the serving cell are not in the same BSC, a load handover is performed when the load of the target cell is lower than Load handover Load Accept Threshold and Inter BSC Load Information Allowed is set to Yes.
Examples
The system assigns MSs to different load handover margins based on the downlink RX level. The load handover algorithm is used to hand over the MSs out of a cell step by step. 1. The MSs in load handover margin 1 are handed over to the neighboring cells. Load handover margin 1 specifies the area where the downlink level ranges from Edge HO DL RX_LEV Threshold to the sum of Edge HO DL RX_LEV Threshold and Load HO Step Level. After a Load HO Step Period elapses, the MSs in load handover margin 2 are handed over to the neighboring cells. The load handover margin 2 specifies the area where the downlink level ranges from Edge HO DL RX_LEV Threshold to the sum of Edge HO DL RX_LEV Threshold and (2 x Load HO Step Level).
2.
Issue 08 (2011-09-30)
3.
The load handover stops when the traffic volume in the cell is less than or equal to Load HO Threshold.
The load handover is performed step by step to prevent call drops caused by a sudden increase in CPU load or the congestion in the target cell.
?.9. Edge Handover

Edge handover is performed on the basis of receive level. To trigger an edge handover, the receive level of the target cell should be at least one hysteresis value (specified by Inter-cell HO Hysteresis) greater than the receive level of the serving cell.
If Edge HO Allowed is set to Yes, the triggering conditions of edge handover are as follows: l Either of the following conditions is met. The filtered downlink RX level of the serving cell after compensation is lower than Edge HO DL RX_LEV Threshold. The filtered uplink RX level of the serving cell after compensation is lower than Edge HO UL RX_LEV Threshold. l RX level of the neighboring cell > RX level of the serving cell + Inter-cell HO Hysteresis
An edge handover is triggered when the P/N criterion is met, that is, when the previous conditions are met for Handover Algorithm I Edge HO Valid Time within Handover Algorithm I Edge HO Watch Time.The parameters used for P/N criterion judgment must be configured for the neighboring cells. In different radio conditions, these parameters should be configured differently for the neighboring cells to ensure that an optimal target cell is selected during handover. When both Edge HO Allowed and Enhanced Outgoing Cell Handover Allowed are set to YES(Yes), l l The condition for triggering uplink edge handover is as follows: SS_ULs_f<Tborder_ul+ (Poffset_i-64). The condition for triggering downlink edge handover is as follows: SS_DLs_f<Tborder_dl+ (Poffset_i-64).
Where, SS_ULs_f is the measured uplink TCH level of the neighboring cell after power control compensation and filtering. SS_DLs_f is the measured downlink TCH level of the neighboring cell after power control compensation and filtering. Tborder_ul is the Edge HO UL RX_LEV Threshold configured for the serving cell. Tborder_dl is the Edge HO DL RX_LEV Threshold configured for the serving cell. Poffset_i is the Enhanced Outgoing Cell Handover Offset of the serving cell, which is set for neighboring cell i. After 16-bit ranking, the edge handover conditions should be checked against all neighboring cells that are ranked in front of the serving cell. Uplink and downlink edge handovers are checked independently. If the neighboring cells ranked in front of the serving cell meet the conditions for triggering uplink or downlink edge handover, they can be selected as uplink or downlink edge handover candidates. The final target cell for edge handover is the neighboring cell with the highest 16-bit ranking in the candidate list. Note that both the serving cell and a neighboring cell for edge handover must meet their own P/N criterion.
Figure 2-145 shows the edge handover. Figure 2-145 Edge handover

The target cell should have the highest priority among the candidate cells. In addition, it should meet the following conditions: l l The serving cell cannot be selected as the target cell. After cells are ranked, the target cell must have a higher priority than the serving cell.
A cell becomes the target cell if the previous conditions are met for Edge HO AdjCell Valid Time within Edge HO AdjCell Watch Time. If the triggering conditions of edge handover are met but the candidate 2G cells are not suitable, the following operations are performed: l If a neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to Yes, and if the MS supports the 2G/3G inter-RAT handover, the 2G/3G inter-RAT handover is performed. If no neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to No, or if the MS does not support the 2G/3G inter-RAT handover, the decision on whether to initiate another type of handover is made.
?.10. Fast-Moving Micro Cell Handover

Fast-moving micro cell handover is performed from a micro cell to a macro cell according to the relative speed of an MS so that the number of handovers can be minimized. Fast-moving micro cell handover applies to the following scenarios: l l If an MS is moving fast in a micro cell, it is handed over to a macro cell. To prevent an MS that is moving fast in a macro cell from entering a micro cell, time penalty is performed on the micro cell so that the fast-moving MS camps on the macro cell.
Figure 2-146 shows the fast-moving micro cell handover.
Issue 08 (2011-09-30)
688
Figure 2-146 Fast-moving micro cell handover
If MS Fast Moving HO Allowed is set to Yes, the handover decision procedure of fast-moving micro cell handover is as follows: 1. 2. When the triggering conditions of edge handover or PBGT handover are met, the fastmoving micro cell handover decision is started. When the period during which the MS camps on the serving cell is shorter than MS Fastmoving Time Threshold, the number of cells through which the fast-moving MS passes is incremented by one.
NOTE
The cell counted by the system must locate at a layer lower than layer 4. In other words, it must be a non-Umbrella cell.
3.
When the number of cells that the MS passes in fast movement reaches MS Fast-moving Watch Cells, the fast-moving micro cell handover is triggered if the number of cells that the MS passes in fast movement counted by the system is greater than or equal to MS Fastmoving Valid Cells.

In handover algorithm I, the target cell should have the highest priority among the candidate cells. In addition, the target cell should meet the following conditions: l l The target cell must be at layer 4, that is, Umbrella cell. Filtered RX level of the target cell Inter-layer HO Threshold + Adjacent Cell Interlayer HO Hysteresis - 64
Limitations
After the fast-moving micro cell handover is successful, the penalty is performed on all the neighboring micro cells. During Penalty Time on Fast Moving HO, Penalty on Fast Moving HO is subtracted from the RX level of every neighboring micro cell.
Issue 08 (2011-09-30)
689
Cell Layer and Cell Priority

With Huawei multiband handover algorithm, a proper traffic volume distribution can be realized among multiple frequency bands. Huawei multiband handover algorithm divides cells into four layers, with 16 priorities at each layer. The Layer of the cell parameter specifies at which layer a cell is located. This algorithm is applicable to complex networking scenarios. Figure 2-147 shows the cell layers. Figure 2-147 Cell layers
In Huawei multiband handover algorithm, a GSM network covering a certain area is divided into four layers, which are: l l l l Layer 4: Umbrella cell. The umbrella cells are generally GSM900 cells having the wide coverage feature. It also implements fast MS connection. Layer 3: Macro cell. The macro cells are generally GSM900 cells, which are commonly used in current GSM system and serve majority of subscribers. Layer 2: Micro cell. The micro cells are generally DCS1800 cells having the small coverage feature. They enable capacity expansion. Layer 1: Pico cell. The pico cells are generally DCS1800 cells, which are used in hot spots and blind spots.
The cell at the lower layer has a higher priority. Cell Priority controls handover between cells at the same layer. Each layer has 16 priorities, numbered 1-16 respectively. A high value indicates a low priority. If the cells at the same layer have different priorities, a cell with a lower priority value has a higher priority. Cell Priority along with Layer of the cell determines the priority of a cell. The priority affects the sequence of neighboring cells for handover.
?.11. Inter-Layer Handover

Inter-layer handover is a type of normal handover. It is used to enable the micro cells at low layers (the priority is high) to absorb traffic volume. To balance the traffic volume flexibly and to meet the requirements of different network topologies, the GSM network is divided into several layers. See 2.46.3.4.10 Fast-Moving Micro Cell Handover for details.
If Level HO Allowed is set to Yes, the triggering conditions of inter-layer handover are as follows: l l l The layer at which the target cell is located has a higher priority than the layer at which the serving cell is located. Filtered downlink RX level of the target cell Inter-layer HO Threshold + Adjacent Cell Inter-layer HO Hysteresis - 64 After cells are ranked, the target cell must have a higher priority than the serving cell.
The inter-layer handover is triggered when the P/N criterion is met, that is, the previous conditions are met for Layer HO Valid Time within Layer HO Watch Time. The parameters used for P/N criterion judgment must be configured for the neighboring cells. In different radio conditions, these parameters should be configured differently for the neighboring cells to ensure that an optimal target cell is selected during handover. When the Neighboring Cell Penalty Switch is set to ON(ON), a timer is started when the interlayer handover conditions (including the conditions for making handover decisions and the P/ N criterion) are met, and no handover towards the neighboring cell is triggered this time. Within the Penalty Timer Length, the neighboring cell level after filtering is punished. That is, within the penalty timer length, the neighboring cell level used by the system is equal to the original filtered level minus Level Penalty Value on Neighboring Cell. The Penalty Stop Level Threshold is used for stopping the penalty timer. The penalty timer is stopped if the following formula is or the bad quality handover conditions are met (The level conditions are checked after filtering. If the neighboring cell level after filtering is lower than the Penalty Stop Level Threshold, the penalty timer for the neighboring cell is stopped. The bad quality handover conditions are checked when making bad quality handover decisions. If the uplink or downlink bad quality handover conditions are met, the penalty timers that are started for all the neighboring cells of the serving cell are stopped.). The penalty timer can be started only once, and it cannot be restarted when it expires or the conditions for stopping the penalty timer are met. SS_DLs_f<Tlow_i Where, SS_DLs_f is the filtered BCCH receive level of neighboring cell i. Tlow_i is the Penalty Stop Level Threshold of the serving cell, which is set for neighboring cell i.
CAUTION
In handover algorithm I, the penalty on the neighboring cell level within the value of the penalty timer is effective for all handovers, and any handover towards a punished neighboring cell is difficult within the value of the penalty timer.

The requirements for target cell selection are as follows:
l l l
The triggering conditions are met. The serving cell cannot be selected as the target cell. The target cell has the highest priority in the candidate cell list.
?.12. PBGT Handover

PBGT handover is a type of normal handover.
If PBGT HO Allowed is set to Yes, the triggering conditions of PBGT handover are as follows: l l The target cell and the serving cell are at the same layer and have the same priority. The following condition is met for PBGT Valid Time within PBGT Watch Time: (MIN (MS_TXPWR_MAX, P) RXLEV_DL PWR_DIFF) (MIN (MS_TXPWR_MAX (n), P) RXLEV_NCELL (n)) > PBGT_HO_MARGIN Here, RXLEV_DL: indicates the filtered downlink RX level of the serving cell. MS_TXPWR_MAX: indicates the maximum allowed transmit power of an MS in the serving cell. MS_TXPWR_MAX (n): indicates the maximum allowed transmit power of an MS in neighboring cell n. RxLev_NCELL (n): indicates the downlink receive level in neighboring cell n. PWR_DIFF: indicates the difference between the maximum downlink transmit power in the serving cell due to power control and the actual downlink transmit power in the serving cell. P: indicates the maximum transmit power of an MS. PBGT_HO_MARGIN: indicates the PBGT HO Threshold of the serving cell configured for neighboring cells minus 64. The PBGT handover can be triggered only when all the previous conditions are met. When the Neighboring Cell Penalty Switch is set to YES(Yes), a timer is started when the PBGT handover conditions (including the conditions for making handover decisions and the P/ N criterion) are met, and no handover towards the neighboring cell is triggered this time. Within the Penalty Timer Length, the neighboring cell level after filtering is punished. That is, within the penalty timer length, the neighboring cell level used by the system is equal to the original filtered level minus Level Penalty Value on Neighboring Cell. The Penalty Stop Level Threshold is used for stopping the penalty timer. The penalty timer is stopped if the following formula is or the bad quality handover conditions are met (The level conditions are checked after filtering. If the neighboring cell level after filtering is lower than the Penalty Stop Level Threshold, the penalty timer for the neighboring cell is stopped. The bad quality handover conditions are checked when making bad quality handover decisions. If the uplink or downlink bad quality handover conditions are met, the penalty timers that are started for all the neighboring cells of the serving cell are stopped.). The penalty timer can be started only once, and it cannot be restarted when it expires or the conditions for stopping the penalty timer are met. SS_DLs_f<Tlow_i Where, SS_DLs_f is the filtered BCCH receive level of neighboring cell i. Tlow_i is the Penalty Stop Level Threshold of the serving cell, which is set for neighboring cell i.
CAUTION
In handover algorithm I, the penalty on the neighboring cell level within the value of the penalty timer is effective for all handovers, and any handover towards a punished neighboring cell is difficult within the value of the penalty timer.

The target cell should meet the following conditions: l l l The target cell and the serving cell are at the same layer and have the same priority. The serving cell cannot be selected as the target cell. The target cell has the highest priority in the candidate cell list.
?.13. AMR Handover

The AMR handover in handover I algorithm consists of the AMR TCHF-TCHH handover and AMR TCHH-TCHF handover algorithm. The AMR TCHF-TCHH handover is conducted based on cell load and RQI, whereas the AMR TCHH-TCHF handover is conducted based on RQI. The conversion formula between RQI and C/I is RQI = 2 x C/I.
Triggering Conditions of AMR TCHF-TCHH Handover

The triggering conditions of AMR TCHF-TCHH handover are as follows: l l l l l l Intracell F-H HO Allowed is set to Yes. The target call is an AMR call. The half-rate function must be enabled in the cell where the call is initiated. The full-rate speech version 3 and half-rate speech version 3 must be supported by the cell where the call is initiated. The type of channel specified by the MSC during a call can be changed during a handover. For AMR FR calls, when the parameter AMR TCH/H Prior Allowed is set to ON(On), TCHF-to-TCHH handover is triggered only when the cell load is greater than the value of the parameter AMR TCH/H Prior Cell Load Threshold and the proportion of AMR HR users is smaller than the value of the parameter Ratio of AMR-HR. For AMR FR calls, when the parameter AMR TCH/H Prior Allowed is set to OFF (Off), TCHF-to-TCHH handover is triggered only the proportion of AMR HR users is smaller than the value of the parameter Ratio of AMR-HR. The call occupies the full-rate TCH. The RQI/2 is greater than F2H HO Threshold .
For an AMR FR call, the AMR TCHF-TCHH handover can be performed if the preceding conditions are met for Intracell F-H HO Last Time within Intracell F-H HO Stat Time.
Triggering Conditions of AMR TCHH-TCHF Handover

The triggering conditions of AMR TCHH-TCHF handover are as follows: l
Issue 08 (2011-09-30)
Intracell F-H HO Allowed is set to Yes.

l l l l l
The target call is an AMR call. The half-rate function must be enabled in the cell where the call is initiated. The full-rate speech version 3 and half-rate speech version 3 must be supported by the cell where the call is initiated. The type of channel specified by the MSC during a call can be changed during a handover. The call occupies the half-rate TCH. The RQI/2 is smaller than H2F HO Threshold.
For an AMR HR call, the AMR TCHH-TCHF handover can be performed if the preceding conditions are met for Intracell F-H HO Last Time within Intracell F-H HO Stat Time.

The AMR handover is an intra-cell handover. Therefore, only the serving cell can be selected as the target cell.
?.14. SDCCH Handover

SDCCH handover is a process in which the MS is handed over from an SDCCH to another SDCCH in an immediate assignment. SDCCH handover helps improve the access success rate of the MSs on the edge of the network, thus improving the network QoS. The principle of SDCCH handover is the same as that of TCH handover. Regarding procedure, an SDCCH handover involves measurement and MR reporting, MR processing, handover decision, and handover execution. Whether an SDCCH handover can be performed is controlled by the SDCCH HO Allowed parameter. If an inter-BSC SDCCH handover is required, both SDCCH HO Allowed and InterBSC SDCCH HO ALLowed should be set to YES(Yes). The handover decision algorithm for SDCCH handover is different from that for TCH handover in the following ways: l The algorithms for the following handovers support SDCCH handover: quick handover, TA handover, BQ handover, rapid level drop handover, interference handover, handover due to no downlink measurement report, edge handover, and fastmoving micro cell handover l The algorithms for the following handovers do not support SDCCH handover: enhanced dual-band network handover, load handover, inter-layer handover, PBGT handover, AMR handover, better 3G cell handover, concentric cell handover, and tight BCCH handover
?.15. Other Handovers

Other handovers here refer to better 3G cell handover and tight BCCH handover.
Better 3G Cell Handover

See 2.4 2G/3G Interoperability.
Tight BCCH Handover

See 2.17 BCCH Dense Frequency Multiplexing.
2.46.3.5 Handover Decision Based on Handover Algorithm II

Handover decision based on handover algorithm II is made in the following order: forced handover, emergency handover, intra-cell handover, and inter-cell handover. Handover decision based on handover algorithm II involves the following procedures: l l l Determining whether the serving cell meets the triggering conditions Selecting corresponding candidate cell list for each handover type Performing the comprehensive decision and determining the candidate neighboring cells
The procedure for performing comprehensive decision based on handover results and determining the candidate neighboring cells is as follows: 1. The BSC selects a handover type with the highest priority from all the handovers that can be performed on each neighboring cell. The handover priority is as follows: l Forced handover, emergency handover, and interference handover have a high priority. Figure 2-148 shows the details. Figure 2-148 Handovers with high priority
NOTE
Quick handover is classified into frequency offset handover and quick PBGT handover. Frequency offset handover has a higher priority than quick PBGT handover.
l Intra-cell handover (excluding interference handover) and inter-cell handover have a normal priority. Figure 2-149 shows the details.
NOTE
AMR handover has the same priority as TCHF-TCHH handover.
Issue 08 (2011-09-30)
695
Figure 2-149 Handovers with normal priority
2.
The BSC ranks the candidate cells according to the network characteristics adjustment algorithm and then generates the final candidate cell list. Every neighboring cell in the candidate cell list has its own handover decision. Neighboring 2G cells and neighboring 3G cells are ranked separately. In handover algorithm II, Inter-rat HO Preference specifies whether a neighboring 2G or a neighboring 3G cell is preferred. l When Inter-rat HO Preference is set to Preference for 2G Cell: A neighboring 2G cell is preferred. If the candidate cell list contains suitable neighboring 3G cells but no suitable neighboring 2G cells, a neighboring 3G cell is selected. l When Inter-rat HO Preference is set to Preference for 3G Cell: A neighboring 3G cell is preferred. If the candidate cell list contains suitable neighboring 2G cells but no suitable neighboring 3G cells, a neighboring 2G cell is selected. l When Inter-rat HO Preference is set to Preference for 2G Cell By Threshold: If the RX level of a candidate 2G cell is lower than or equal to HO Preference Threshold for 2G Cell, a neighboring 3G cell is preferred.
NOTE
3.
When a neighboring 3G cell is preferred among the candidate cells, the priority of 3G better cell handover is the lowest.
If the triggering conditions of emergency handover are met and there is at least one candidate cell, then the emergency handover timer Min Interval for Emerg. HO is started. Another emergency handover decision can be performed only when Min Interval for Emerg. HO times out.
?.1. Quick Handover

Quick handover aims to increase the handover success rate of an MS moving at a high speed and to ensure the call continuity and low call drop rate. Quick handover applies to the scenario where an MS moves fast along an urban backbone road, a selected route, or a high-speed railroad.
Quick Handover Types

Quick handover consists of frequency offset handover and quick PBGT handover. l Frequency offset handover Whether the MS is moving away from the serving cell is determined based on the frequency offset information provided by an MS moving at a high speed. Frequency offset handover decision is made according to the uplink/downlink RX level of the serving cell and the path loss of neighboring cells. l Quick PBGT handover Quick PBGT handover decision is made according to the path loss of neighboring cells. For quick handover, the handover response speed is enhanced by: l l l l Accurately calculating the moving speed of the MS Derestricting the interval between handover decisions Reducing the number of measurement reports for the handover decision Introducing the filtering
Quick Handover Preparation

The preparation for quick handover involves the following aspects: l Frequency offset is decoded from the measurement report. Frequency offset of the MS is obtained from the uplink measurement report that the BTS sends to the BSC. l filtering is performed on the measurement report.
During handover decision, it is first determined whether the triggering conditions of frequency offset handover are met. When the BTS cannot send the frequency offset information or the reported frequency offset information is invalid, quick PBGT handover is triggered, provided that other conditions of frequency offset handover are met. If Quick Handover Enable is set to Yes, the triggering conditions of quick handover are as follows: l The MS is moving away from the serving cell (the frequency offset in the measurement result is a negative value) and the moving speed of the MS is greater than Quick Move Speed Threshold. The filtered uplink level of the serving cell is lower than Quick Handover Up Trigger Level. The compensated downlink level of the serving cell is lower than Quick Handover Down Trigger Level. The path loss of configured chain neighboring cells is lower than the specified threshold of the path loss of the serving cell. In other words, PBGT(n) is greater than or equal to 0.
l l l
The triggering conditions of quick handover are as follows: l If the last three conditions are met simultaneously, the decision is made as follows: If the first condition is met, a frequency offset handover is performed.
If the first condition is not met, a quick PBGT handover is performed. l If all the last three conditions are not met, quick handover is not triggered.

The target cell must be a chain neighboring cell of the serving cell. The target cell can be obtained through the setting of Chain Neighbor Cell. If Handover Direction Forecast Enable is set to Yes, a neighboring cell in the moving direction of the MS is selected preferentially. To forecast the moving direction of the MS, the direction of a chain neighboring cell (A or B) compared with the serving cell is specified by Chain Neighbour Cell Type. If the number of times that the MS is handed over to neighboring cells in the same direction (B for example) is greater than or equal to Handover Direction Forecast Last Times when the handover time reaches Handover Direction Forecast Statistic Times, then the MS is inferred to be moving towards the B direction. Subsequently, the MS is preferentially handed over to the neighboring cell whose Chain Neighbour Cell Type is B.
Limitations
The limitations on quick handover are as follows: l l l The serving cell cannot be selected as the target cell. The candidate cells for quick handover must be chain neighboring cells of the serving cell. After a quick handover is successful, the penalty is performed on the original cell during the penalty time to prevent an immediate handover back to the original cell. The penalty time and penalty value are specified by Quick Handover Punish Time and Quick Handover Punish Value respectively.
?.2. TA Handover
TA handover is a type of emergency handover. The TA handover decision is made according to the TA value reported by the MS. The TA value of a normal cell ranges from 0 to 63 and that of an extended cell ranges from 0 to 229. The TA can be stepped up or down in steps of 553.5 m. The TA value of 63 corresponds to a distance of 35 km.
TA handover is triggered when the following conditions are met: l l TA HO Allowed is set to Yes. Filtered TA value in the measurement report provided by the MS is greater than or equal to TA Threshold.
The TA handover can be triggered only when the preceding two conditions are met simultaneously.
NOTE
From the perspective of the triggering conditions of TA handover, TA can be regarded as a limitation to the size of a cell.
Issue 08 (2011-09-30)
698

The target cell should have the highest priority in the candidate cell list after handover preprocessing. In addition, the target cell should meet the following limitations: l l l The serving cell cannot be selected as the target cell. If TA Threshold of a co-site neighboring cell is lower than or equal to the TA Threshold of the serving cell, a handover to the neighboring cell is prohibited. In handover algorithm II, a cell becomes the target cell for TA handover if the previous conditions are met for TA HO Valid Time within TA HO Watch Time.
If the triggering conditions of TA handover are met but the candidate 2G cells are not suitable, the following operations are performed: l If a neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to Yes, and if the MS supports the 2G/3G inter-RAT handover, the 2G/3G inter-RAT handover is performed. If no neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to No, or if the MS does not support the 2G/3G inter-RAT handover, the decision on whether to initiate another type of emergency handover is made.
Limitations
After the TA handover is successful, the penalty is performed on the original cell. During Penalty Time after TA HO, Penalty Level after TA HO is subtracted from the level of the original cell to prevent an immediate handover back to the original cell.
?.3. BQ Handover
BQ handover is a type of emergency handover in which the system makes the decision based on the uplink/downlink RX quality on the Um interface. RX quality is represented by bit error rate (BER). The BSC measures the quality of a radio link based on the quality class in the measurement report. The probable cause of an increase in BER is that the signal power is too low or the channel interference increases.
If BQ HO Allowed is set to Yes, the triggering conditions of BQ handover are as follows: l l The uplink RX quality is greater than or equal to the uplink RX quality threshold of the serving cell. The downlink RX quality is greater than or equal to the downlink RX quality threshold of the serving cell.
The BQ handover is triggered when either of the preceding conditions is met. The parameters for specifying the uplink and downlink RX quality thresholds are as follows: l For non-AMR calls, the parameter for specifying the uplink RX quality threshold is UL Qual. Threshold and the parameter for specifying the downlink RX quality threshold is DL Qual. Threshold.
Issue 08 (2011-09-30)
For AMR FR calls, the parameter for specifying the uplink RX quality threshold is UL Qual. Limit for AMR FR and the parameter for specifying the downlink RX quality threshold is DL Qual. Limit for AMR FR. For AMR HR calls, the parameter for specifying the uplink RX quality threshold is UL Qual. Limit for AMR HR and the parameter for specifying the downlink RX quality threshold is DL Qual. Limit for AMR HR.

The target cell should have the highest priority in the candidate cell list after handover preprocessing. In addition, the target cell should meet the following conditions: l l In handover algorithm II, the serving cell cannot be selected as the target cell. The RX level of target cell must meet the following conditions: The serving cell and the target cell work in the same frequency band. Filtered downlink RX level of the target cell > Filtered downlink RX level of the serving cell after compensation + Inter-cell HO Hysteresis of the serving cell configured for the neighboring cell - BQ HO Margin + 64 The serving cell works in GSM900 and the target cell works in DCS1800. Filtered downlink RX level of the target cell Inter-layer HO Threshold + (Interlayer HO Hysteresis - 64). The serving cell works in DCS1800 and the target cell works in GSM900. There is no constraint on the target cell in this condition. l In handover algorithm II, a cell becomes the target cell for BQ handover if the previous conditions are met for BQ HO Valid Time within BQ HO Watch Time.
If the triggering conditions of BQ handover are met but the candidate 2G cells are not suitable, the following operations are performed: l If a neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to Yes, and if the MS supports the 2G/3G inter-RAT handover, the 2G/3G inter-RAT handover is performed. If no neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to No, or if the MS does not support the 2G/3G inter-RAT handover, the decision on whether to initiate another type of emergency handover is made.
Limitations
After the BQ handover is successful, the penalty is performed on the original cell. During Penalty Time after BQ HO, Penalty Level after BQ HO is subtracted from the level of the original cell to prevent an immediate handover back to the original cell.
?.4. Interference Handover

Interference handover is a type of intra-cell handover in handover algorithm II. Interference handover helps protect the interfered calls and reduce the network interference. It is applicable to scenarios with interference. In handover algorithm II, the BQ handover is a type of emergency handover and the interference handover is a type of intra-cell handover.
If Intracell HO Allowed is set to Yes and Interference HO Allowed is set to Yes, the triggering conditions of interference handover are as follows: l l The filtered value of uplink RX quality is greater than or equal to the specified RX quality threshold at the current uplink RX level. The filtered value of downlink RX quality is greater than or equal to the specified RX quality threshold at the current downlink RX level.
In handover algorithm II, the interference handover is triggered when the previous conditions are met for Interfere HO Valid Time within Interfere HO Static Time. The parameters for specifying the uplink and downlink RX quality thresholds are as follows: l l For non-AMR FR calls, the parameter for specifying the RX quality threshold is Interfere HO Qual. Thresh n for Non-AMR FR, where 1 n 12. For AMR FR calls, the parameters for specifying the RX quality threshold are Interfere HO Qual. Thresh n for Non-AMR FR (1 n 12) and Interfere HO Qual. Thresh Offset for AMR FR. If n = 1, the RX quality threshold is Interfere HO Qual. Thresh 1 for Non-AMR FR. If 2 n 12, the RX quality threshold is Interfere HO Qual. Thresh n for NonAMR FR + Interfere HO Qual. Thresh Offset for AMR FR.

In handover algorithm II, only the serving cell can be selected as the target cell.
Limitations
In handover algorithm II, if an interference handover is initiated, it cannot be initiated again within Penalty Time on Interfere HO regardless of whether the handover is successful.
?.5. Handover Due to No Downlink Measurement Report

Handover due to no downlink measurement report is performed on the basis of the uplink quality. The purpose is to ensure the call continuity and minimize the possibility of call drops. Handover due to no downlink measurement report is generally caused by adverse radio environment on the uplink. In this case, the requirements of the filtering algorithm cannot be met, so other handover decisions cannot be performed.
In handover algorithm II, the triggering conditions of handover due to no downlink measurement report are as follows: l l l
Issue 08 (2011-09-30)
No Dl Mr.HO Allowed is set to Yes. There is no downlink information in the measurement report of the call. The number of lost downlink MRs is smaller than Cons.No Dl Mr.HO Allowed Limit.
For TCH, the number of saved MRs with uplink quality value is greater than Filter Length for TCH Qual; for SDCCH, the number of saved MRs with uplink quality value is greater than Filter Length for SDCCH Qual.. The filtered value of uplink RX quality is greater than or equal to UL Qual. Threshold. For AMR FR calls, the corresponding parameter is UL Qual. Limit for AMR FR. For AMR HR calls, the corresponding parameter is UL Qual. Limit for AMR HR.
When all the previous conditions are met, the handover due to no downlink measurement report is triggered.

In handover algorithm II, the conditions for selecting the target cell are as follows: l l l l The ranked neighboring cells recorded in the last complete measurement report are saved as candidate cells. Only a neighboring cell can serve as the target cell. RX level in neighboring cell > Filtered RX level in serving cell + Inter-cell HO Hysteresis - BQ HO Margin + 64 A neighboring cell serves as the target cell if the previous conditions are met for UL BQ HO Last Time within UL BQ HO Static Time.
?.6. Enhanced Dual-Band Network Handover

Enhanced dual-band network handover is performed based on the traffic volume of the overlaid and underlaid cells and based on the receive level. Enhanced dual-band network handover is classified into the following types: l l l Handover due to high load in the underlaid cell Handover due to low load in the underlaid cell Handover due to MS movement to the border of the overlaid cell
Triggering Conditions of Handover Due to High Load in the Underlaid Cell

The triggering conditions of the handover due to high load in the underlaid cell are as follows: l l l l l l l The two cells are in the enhanced dual-band network and Load HO Allowed is set to Yes. The MS supports the frequency band on which the overlaid cell operates. The handover due to high load in the underlaid cell is performed only on TCHs. The load in the underlaid cell is higher than or equal to UL Subcell General Overload Threshold. The load in the overlaid cell is lower than Inner Cell Serious OverLoad Thred. The system traffic volume is lower than or equal to Subcell HO Allowed Flow Control Level. The current call is within the handover margin, and the Incoming OL Subcell HO Level TH plus the handover margin is greater than or equal to the receive level, which is also greater than or equal to the Incoming OL Subcell HO Level TH.
Issue 08 (2011-09-30)
When all the preceding conditions are met, the handover due to high load in the underlaid cell is triggered. If the load of the underlaid subcell is higher than or equal to UL Subcell Serious Overload Threshold, then the handover margin is adjusted in a period of UL Subcell Load Hierarchical HO Periods subtracted by MOD Step LEN of UL Load HO Period. The step length for handover margin adjustment is specified by Step Length of UL Subcell Load HO.
Triggering Conditions of Handover Due to Low Load in the Underlaid Cell

The triggering conditions of the handover due to low load in the underlaid cell are as follows: l l l The load in the underlaid cell is lower than UL Subcell Lower Load Threshold. The system traffic volume is lower than or equal to Subcell HO Allowed Flow Control Level. The current call is within the handover margin and the receive level is greater than or equal to Outgoing OL Subcell HO Level TH.
When all the preceding conditions are met, the handover due to low load in the underlaid cell is triggered. If the load of the underlaid subcell is lower than UL Subcell Lower Load Threshold for a specified period, then the handover margin is adjusted in a period of OL Subcell Load Diversity HO Period. The step length for handover margin adjustment is specified by Step Length of OL Subcell Load HO.
Triggering Conditions of Handover Due To MS Movement in the Overlaid Subcell

The triggering conditions of the handover due to MS movement in the overlaid subcell are described as follows: l l SS(s) < Thdouter SS(u) - SS(n) < ATCB_THRD - ATCB_HYST Here, SS(s): specifies the filtering compensated downlink RX level in the serving cell. Thdouter: specifies Outgoing OL Subcell HO Level TH. SS(u): specifies the downlink level (power compensation is performed on the downlink level based on the measurement) of the underlaid subcell where the call is originated. If the SS(u) value cannot be obtained, you can infer that the decision of enhanced dualband network handover is not performed and the decision condition is met by default. SS(n): The best neighboring cell is the one whose measured BCCH level is the highest among neighboring cells. SS(n) is the level value of such a optimum neighboring cell that is on the same frequency band, layer, and level with the underlaid subcell but is not co-sited with the underlaid subcell. If such a neighboring cell is not available, the value of SS(n) is -110 dBm. ATCB_THRD: specifies Distance Between Boundaries of Subcells. ATCB_HYST: specifies Distance Hysteresis Between Boundaries. Handover due to MS movement in the overlaid subcell is triggered if either of the preceding conditions is met.

NOTE
l For the ATCB handover algorithm, the boundaries of the overlaid and underlaid subcells are determined according to the relative value between the signal strength of serving cell and that of neighboring cell. When SS(s) is equal to SS(n), the system considers that it is the boundary point of the underlaid subcell. When the value of SS(s) subtracted by SS(n) is greater than ATCB_THRD, it is the coverage area of the overlaid subcell. The coverage area of the overlaid subcell is determined according to different networking and coverage conditions of the existing network. In addition, the overlaid subcell of serving cell and the overlaid subcell of neighboring cells will not overlap regardless of the distance between BTSs. l The handover margin specifies the range of signal level. In the case of overlaid/underlaid load handover on the enhanced dual-band network, the MSs whose downlink levels are within the handover margin are handed over level by level.

The requirements for target cell selection in the enhanced dual-band network are as follows: l l l For the handover due to high load in the underlaid cell, the MS must be handed over to the overlaid cell. For the handover due to low load in the underlaid cell, the MS must be handed over to the underlaid cell. For the handover due to MS movement in the overlaid subcell, the MS must be handed over to the underlaid cell.
Limitations
The limitations on the handover due to high load in the underlaid cell are as follows: l l l If the cell where the call is located is on an enhanced dual-band network, Cell Inner/Extra Property is set to Extra(Extra). The Load HO Allowed parameter should be set. The maximum range of the handover margin is from 63 to Incoming OL Subcell HO Level TH. The MS with the highest receive level is handed over first.
The limitations on the handover due to low load in the underlaid cell are as follows: l l l If the cell where the call is located is on the enhanced dual-band network, Cell Inner/Extra Property is set to Inner(Inner). The Load HO of OL Subcell to UL Subcell parameter should be set. The maximum range of the handover margin is from 63 to Outgoing OL Subcell HO Level TH. The MS with the lowest receive level is handed over first.
The limitations on the handover due to MS movement in the overlaid subcell are described as follows: l The cell where the call is located is on the enhanced dual-band network. Cell Inner/Extra Property is set to Inner(Inner).
Impact of the Enhanced Dual-Band Network Handover on the Existing Algorithm

The impact of the enhanced dual-band network handover on the existing algorithm is as follows: On the enhanced dual-band network, the MS should not be handed over to a cell in the same underlaid/overlaid cell group when the load handovers between the overlaid cell and the
underlaid cell (specified by Load HO Allowed and Load HO of OL Subcell to UL Subcell) are allowed. This is to prevent a load handover of a normal cell from colliding with a load handover between the overlaid cell and the underlaid cell on the network.
?.7. Load Handover

In handover algorithm II, load handover is not decided independently. In handover algorithm II, the load handover decision is made in network adjustment phase. The selection of target cell should be processed by the better cell handover. That is, the load handover is triggered when the triggering conditions of load handover and better cell handover are met simultaneously. See 2.46.3.4.8 Load Handover for the triggering conditions of load handover. See 2.46.3.5.10 Better Cell Handover for the triggering conditions of better cell handover.
?.8. Edge Handover

Edge handover is performed on the basis of receive level. To trigger an edge handover, the receive level of the target cell should be at least one hysteresis value (specified by Inter-cell HO Hysteresis) greater than the receive level of the serving cell.
If Edge HO Allowed is set to Yes, the triggering conditions of edge handover are as follows: l Either of the following conditions is met. The filtered downlink RX level of the serving cell after compensation is lower than Edge HO DL RX_LEV Threshold. The filtered uplink RX level of the serving cell after compensation is lower than Edge HO UL RX_LEV Threshold. l RX level of the neighboring cell > RX level of the serving cell + Inter-cell HO Hysteresis - 64
An edge handover is triggered when the P/N criterion is met, that is, when the previous conditions are met for Handover Algorithm II Edge HO Valid Time within Handover Algorithm II Edge HO Watch Time. The parameters used for P/N criterion judgment must be configured for the neighboring cells. In different radio conditions, these parameters should be configured differently for the neighboring cells to ensure that an optimal target cell is selected during handover. Figure 2-150 shows the edge handover. Figure 2-150 Edge handover
Issue 08 (2011-09-30)
705

The target cell should have the highest priority among the candidate cells. In addition, it should meet the following conditions: l l The serving cell cannot be selected as the target cell. After cells are ranked, the target cell must have a higher priority than the serving cell.
A cell becomes the target cell if the previous conditions are met for Edge HO AdjCell Valid Time within Edge HO AdjCell Watch Time. If the triggering conditions of edge handover are met but the candidate 2G cells are not suitable, the following operations are performed: l If a neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to Yes, and if the MS supports the 2G/3G inter-RAT handover, the 2G/3G inter-RAT handover is performed. If no neighboring 3G cell is available, if Inter-RAT Out BSC Handover Enable is set to No, or if the MS does not support the 2G/3G inter-RAT handover, the decision on whether to initiate another type of handover is made.
?.9. Fast-Moving Micro Cell Handover

Fast-moving micro cell handover is performed from a micro cell to a macro cell according to the relative speed of an MS so that the number of handovers can be minimized. Fast-moving micro cell handover applies to the following scenarios: l l If an MS is moving fast in a micro cell, it is handed over to a macro cell. To prevent an MS that is moving fast in a macro cell from entering a micro cell, time penalty is performed on the micro cell so that the fast-moving MS camps on the macro cell.
Figure 2-151 shows the fast-moving micro cell handover. Figure 2-151 Fast-moving micro cell handover
Issue 08 (2011-09-30)
706
If MS Fast Moving HO Allowed is set to Yes, the handover decision procedure of fast-moving micro cell handover is as follows: 1. 2. When the triggering conditions of edge handover or PBGT handover are met, the fastmoving micro cell handover decision is started. When the period during which the MS camps on the serving cell is shorter than MS Fastmoving Time Threshold, the number of cells through which the fast-moving MS passes is incremented by one.
NOTE
The cells counted by the system must locate at a layer lower than layer 4. In other words, they must be non-Umbrella cells.
3.
When the number of cells that the MS passes in fast movement reaches MS Fast-moving Watch Cells, the fast-moving micro cell handover is triggered if the number of cells that the MS passes in fast movement counted by the system is greater than or equal to MS Fastmoving Valid Cells.

In handover algorithm II, the target cell should have the highest priority among the candidate cells. In addition, the target cell should meet the following conditions: l l l The target cell must be at layer 4, that is, Umbrella cell. Filtered RX level of the target cell Inter-layer HO Threshold + Adjacent Cell Interlayer HO Hysteresis - 64 A neighboring cell serves as the target cell if the previous conditions are met for HCS HO Valid Time within HCS HO Watch Time.
Limitations
After the fast-moving micro cell handover is successful, the penalty is performed on all the neighboring micro cells. During Penalty Time on Fast Moving HO, Penalty on Fast Moving HO is subtracted from the RX level of every neighboring micro cell.
Cell Layer and Cell Priority

Through Huawei multiband handover algorithm, a proper traffic volume distribution can be realized among multiple frequency bands. Huawei multiband handover algorithm divides cells into four layers, with 16 priorities at each layer. The Layer of the cell parameter specifies at which layer a cell is located. This algorithm is applicable to complex networking scenarios. Figure 2-152 shows the cell layers.
Issue 08 (2011-09-30)
707
Figure 2-152 Cell layers
In Huawei multiband handover algorithm, a GSM network covering a certain area is divided into four layers, which are: l l l l Layer 4: Umbrella cell. The umbrella cells are generally GSM900 cells having the wide coverage feature. It also implements fast MS connection. Layer 3: Macro cell. The macro cells are generally GSM900 cells, which are commonly used in current GSM system and serve majority of subscribers. Layer 2: Micro cell. The micro cells are generally DCS1800 cells having the small coverage feature. They enable capacity expansion. Layer 1: Pico cell. The pico cells are generally DCS1800 cells, which are used in hot spots and blind spots.
The cell at the lower layer has a higher priority. Cell Priority controls handover between cells at the same layer. Each layer has 16 priorities, numbered 1-16 respectively. A high value indicates a low priority. If the cells at the same layer have different priorities, a cell with a lower priority value has a higher priority. Cell Priority along with Layer of the cell determines the priority of a cell. The priority affects the sequence of neighboring cells for handover.
?.10. Better Cell Handover

Better cell handover is optimized from inter-layer handover and PBGT handover in handover algorithm I, and performs handover decision based on handover algorithm II.
If Better Cell Handover Enable is set to Yes, the triggering conditions of better cell handover are as follows:
If Pathloss Ho. Enable is set to Yes, pathloss is taken into consideration during the sorting of serving cells and target cells; if Pathloss Ho. Enable is set to No, pathloss is not taken into consideration during the sorting of serving cells and target cells. If the serving cell is in the candidate cell list, then the priorities of the target cells must be higher than the priority of the serving cell after the sorting. If the serving cell is not in the candidate cell list, then the target cells must meet the following conditions: If Load Handover Support is set to NO, or Load Handover Support is set to YES but the load in the serving cell is lower than Load HO Threshold. If the serving cell and the target cells are at the same layer and have the same priority, the following conditions must be met: SS_DL(N) - SS_DL(S) > H - 64 SS_DL(N) indicates the filtered BCCH receive level of a target cell. SS_DL(S) indicates the compensated receive level on the downlink TCH after filtration. H indicates Inter-cell HO Hysteresis of the serving cell over the neighboring cell. Negative handover is a type of better cell handover. When inter-cell HO Hysteresis is set to a value smaller than 64, the value of H 64 is negative. In this case, even if the downlink receive level in a candidate cell is lower than the downlink receive level in the serving cell, a negative handover to the candidate cell can be performed. If the serving cell and the target cells are at different layers but have the same priority, the following conditions must be met: SS_DL(N) T_layer(N) + H_layer(S) SS_DL(N) indicates the filtered BCCH receive level of a target cell. T_layer(N) indicates Inter-layer HO Threshold of the target cell. H_layer(S) indicates Adjacent Cell Inter-layer HO Hysteresis of the serving cell. If Load Handover Support is set to YES and the load in the serving cell is higher than Load HO Threshold, better cell handover can be triggered.
l l
A neighboring cell becomes a target cell if the preceding conditions are met for Better Cell HO Valid Time during Better Cell HO Valid Time.
When both Better Cell Handover Enable and Enhanced Outgoing Cell Handover Allowed are set to YES(Yes), the system selects a better cell as the serving cell of the MS. Reconfigure bit 14 of the serving cell if the following formula is met (set bit 14 to 0 if it is 1 or set bit 14 to 1 if it is 0): SS_DLs_fTlayer-(Hlayer+Poffset_i-64) Where, SS_DLs_f is the measured downlink TCH level of the neighboring cell after power control compensation and filtering. Tlayer is the Inter-layer HO Threshold configured for the serving cell. Hlayer is the Inter-layer HO Hysteresis configured for the serving cell. Poffset_i is the Enhanced Outgoing Cell Handover Offset of the serving cell, which is set for neighboring cell i. Check all neighboring cells, and reconfigure bit 14 of the serving cell for every neighboring cell. Then, compare bit 16 of the serving cell and that of a neighboring cell. If bit 16 of the neighboring cell is smaller than that of the serving cell, the condition for triggering a better cell handover is met. In this case, the neighboring cell is put into the candidate cell list for better handover and the value of bit 14 of the serving cell is recorded. Check all neighboring cells, and rank all neighboring cells in the candidate cell list according to the values of the 16 bits. If bit 14 of the
serving cell in the record is 1, set bit 14 of the serving cell to 1; otherwise, set bit 14 of the serving cell to 0. Then, put the serving cell at the last of the candidate cell list.
NOTE
If Enhanced Outgoing Cell Handover Allowed is set to NO(NO), see 2.46.3.5.8 Edge Handover for details.
When the Neighboring Cell Penalty Switch is set to YES(Yes), a timer is started when the better cell handover conditions (including the conditions for making handover decisions and the P/N criterion) are met, and no handover towards the neighboring cell is triggered this time. Within the Penalty Timer Length, the neighboring cell level after filtering for better cell handover is punished. That is, within the penalty timer length, the neighboring cell level used by the system for 16-bit ranking of better cell handover is equal to the original filtered level minus Level Penalty Value on Neighboring Cell. The Penalty Stop Level Threshold is used for stopping the penalty timer. The penalty timer is stopped if the following formula is met. The penalty timer can be started only once, and it cannot be restarted when it expires or the conditions for stopping the penalty timer are met. SS_DLs_f<Tlow_i Where, SS_DLs_f is the filtered BCCH receive level of neighboring cell i. Tlow_i is the Penalty Stop Level Threshold of the serving cell, which is set for neighboring cell i.
CAUTION
In handover algorithm II, the penalty applied on the neighboring cell level within the Penalty Timer Length is effective for better cell handover and handovers triggered by better cell handover, such as load handover and path loss handover.

The requirements for target cell selection are as follows: l l The serving cell cannot be selected as the target cell. The target cell has the highest priority in the candidate cell list.
?.11. Handover Between a Full-Rate TCH and a Half-Rate TCH

Handover between a full-rate TCH and a half-rate TCH performs decision based on handover algorithm II. Types of handover between a full-rate TCH and a half-rate TCH are as follows: l l AMR TCHF-TCHH handover and non-AMR TCHF-TCHH handover The purpose is to absorb more MSs and to reduce the cell congestion if the cell load is high. AMR TCHH-TCHF handover and non-AMR TCHH-TCHF handover The purpose is to improve the speech quality of the call if the cell load is low.
Triggering Conditions of AMR TCHF-TCHH Handover

If the AMR F-H Ho Allowed is set to Yes, the triggering conditions of AMR TCHF-TCHH handover are as follows:
l l l l l l
Speech Version used by the call is full-rate speech version 3. Downlink path loss of the call AMR F-H Ho Pathloss Threshold + path loss handover margin ATCB of the call AMR F-H Ho ATCB Threshold ATCB handover margin Uplink signal quality of the call AMR F-H Ho Qual. Threshold Downlink signal quality of the call AMR F-H Ho Qual. Threshold The preceding conditions are met for F-H Ho Last Time within F-H Ho Stat. Time.
Triggering Conditions of Non-AMR TCHF-TCHH Handover

If the Non-AMR F-H Ho Allowed is set to Yes, the triggering conditions of non-AMR TCHFTCHH handover are as follows: l l l l l l Speech Version used by the call is full-rate speech version 1 or full-rate speech version 2. Downlink path loss of the call Non-AMR F-H Ho Pathloss Threshold + path loss handover margin ATCB of the call Non-AMR F-H Ho ATCB Threshold ATCB handover margin Uplink signal quality of the call Non-AMR F-H Ho ATCB Threshold Downlink signal quality Non-AMR F-H Ho ATCB Threshold The preceding conditions are met for F-H Ho Last Time within F-H Ho Stat. Time.
Triggering Conditions of AMR TCHH-TCHF Handover

If AMR F-H Ho Allowed is set to Yes or Allow AMR H-F Quality-based HO is set to Yes, the triggering conditions of AMR TCHF-TCHH handover are as follows: l l l l l l Speech Version used by the call is half-rate speech version 3. Downlink path loss AMR H-F Ho Pathloss Threshold ATCB of the call AMR H-F Ho ATCB Threshold Uplink signal quality AMR H-F Ho Qual. Threshold Downlink signal quality of the call AMR H-F Ho Qual. Threshold The AMR TCHH-TCHF handover is triggered if either of the preceding conditions is met for H-F Ho Last Time within H-F Ho Stat. Time and Speech Version is half-rate speech version 3.
Triggering Conditions of Non-AMR TCHH-TCHF Handover

If Non-AMR F-H Ho Allowed is set to Yes or Allow Non-AMR H-F Quality-based HO is set to Yes, the triggering conditions of non-AMR TCHF-TCHH handover are as follows: l l l l l
Issue 08 (2011-09-30)
Speech Version used by the call is half-rate speech version 1. Downlink path loss of the call Non-AMR H-F Ho Pathloss Threshold ATCB of the call Non-AMR H-F Ho ATCB Threshold Uplink signal quality of the call Non-AMR H-F Ho Qual. Threshold Downlink signal quality of the call Non-AMR H-F Ho Qual. Threshold
The non-AMR TCHH-TCHF handover is triggered if either of the preceding conditions is met for H-F Ho Last Time within H-F Ho Stat. Time and Speech Version is half-rate speech version 1.

Only the serving cell can be selected as the target cell of the TCHF-TCHH handover.
?.12. SDCCH Handover

SDCCH handover is a process in which the MS is handed over from an SDCCH to another SDCCH in an immediate assignment. SDCCH handover helps improve the access success rate of the MSs on the edge of the network, thus improving the network QoS. The principle of SDCCH handover is the same as that of TCH handover. Regarding procedure, an SDCCH handover involves measurement and MR reporting, MR processing, handover decision, and handover execution. Whether an SDCCH handover can be performed is controlled by the SDCCH HO Allowed parameter. If an inter-BSC SDCCH handover is required, both SDCCH HO Allowed and InterBSC SDCCH HO ALLowed should be set to YES(Yes). The handover decision algorithm for SDCCH handover is different from that for TCH handover in the following ways: l The algorithms for the following handovers support SDCCH handover: quick handover, TA handover, BQ handover, interference handover, handover due to no downlink measurement report, edge handover, and fast-moving micro cell handover l The algorithms for the following handovers do not support SDCCH handover: enhanced dual-band network handover, load handover, better cell handover, handover between a full-rate TCH and a half-rate TCH, better 3G cell handover, concentric cell handover, and tight BCCH handover
?.13. Other Handovers

Other handovers here refer to better 3G cell handover and tight BCCH handover.
Better 3G Cell Handover

See 2.4 2G/3G Interoperability.
Tight BCCH Handover

See 2.17 BCCH Dense Frequency Multiplexing.
2.46.4 Parameters
This chapter describes the parameters related to handover. For the meaning of each parameter, see Table 2-122. For the default value, value ranges, and MML commands of each parameter, see Table 2-123.
Table 2-122 Parameter description (1) Parameter Current HO Control Algorithm MR.Preprocessing Transfer Original MR Transfer BTS/MS Power Class Sent Freq.of preprocessed MR Measurement Report Type Description Whether to use handover algorithm generation 1 or 2 currently. Whether to enable the BTS to preprocess measurement reports. This parameter determines where to conduct power control. Whether the BTSs send the original measurement reports to the BSC after pre-processing them. When this parameter is set to YES, the BTSs sends the original and pre-processed measurement reports to the BSC. Whether to enable the BTS to transfer BTS/MS power class to the BSC. Frequency at which the BTSs submit pre-processed measurement reports to the BSC. Type of the measurement report (MR) reported by the MS. If the number of measurement reports lost consecutively is no larger than this value, linear interpolation is performed for the values in the lost measurement reports based on the values in the two measurement reports preceding and following the lost measurement reports. Otherwise, the lost measurement reports will be discarded, and the value will be recalculated when new measurement reports arrive. This parameter specifies the transmit power level of the TRX. The greater this parameter is, the smaller the transmit power is. When this parameter is set to "0", the transmit power level of the TRX is the greatest. Each time this parameter increases by one level, the transmit power reduces by 2 dB. For different types of BTSs, the value range of this parameter is different. l BTS3X: 0-10 l BTS3001C: 0-13 l BTS3002C: 0-10 l Double-transceiver BTSs (BTS3012,BTS3012AE,BTS3006C): 0-10 Power Level l DBS3900 GSM, BTS3900 GSM, BTS3900A GSM: 0-10 Level value of the penalty that is performed on the neighboring cells of the cell where a fast-moving MS is located. The neighboring cells must be located at the Macro, Micro, or Pico layer other than the Umbrella layer. Level value of the penalty that is performed on the neighboring cells of the cell where a fast-moving MS is located. The neighboring cells must be located at the Macro, Micro, or Pico layer other than the Umbrella layer.
Allowed MR Number Lost
Penalty on Fast Moving HO
Penalty on MS Fast Moving HO
Issue 08 (2011-09-30)
713
Parameter Penalty Time on Fast Moving HO Penalty Time after AMR TCHF-H HO Fail Penalty Time on Interfere HO Penalty Time of UtoO HO Inter UL/OL Subcells HO Penalty Time
Description Period in which penalty is performed on the neighboring cells of the cell where a fast-moving MS is located. The neighboring cells must be located at the Macro, Micro, or Pico layer but not the Umbrella layer. Within the preset time, no AMR FR-to-HR handover is allowed if the previous FR-to-HR handover fails due to channel unavailability or channel mismatch. Specifies an interval between two consecutive interference handovers. After an MS performs a OL subcell to UL subcell handover successfully, the MS cannot be handed over to the OL subcell again within the value of the parameter. An MS cannot be handed over from the underlaid subcell to the overlaid subcell in this duration after the MS is handed over from the overlaid subcell to the underlaid subcell successfully.
Penalty signal level imposed on a target cell to which the handover fails Penalty Level after due to congestion or poor radio quality. This penalty helps to prevent HO Fail the MS from making a second handover attempt to the target cell. UmPenaltyTimer RscPenaltyTimer CfgPenaltyTimer Penalty Time after OtoU HO Fail Penalty Time after UtoO HO Fail Inter-BSC SDCCH HO ALLowed Min DL Level on Candidate Cell Timer of penalty on a neighboring cell when a handover fails due to faults of air interface connection. Timer for punishing the neighboring cells when handover failures occur due to resource-related causes, such as resources being insufficient. Timer of penalty on a neighboring cell when a handover fails due to faults of data configuration. After an OL subcell to UL subcell handover of an MS fails, the MS does not perform OL subell-UL subcell handovers within the value of the parameter. After an UL subcell to OL subcell handover of an MS fails, the MS does not perform UL subcell to OL subcell handovers within the value of the parameter.
Whether to allow inter-BSC SDCCH handovers. If the downlink received signal level of a neighbor cell is greater than "Min DL Level on Candidate Cell" plus "Min Access Level Offset", the neighbor cell can be listed in the candidate cell queue for handover. Minimum receive level offset. An MS can be handed over to a neighboring cell only when the downlink level of the neighboring cell is greater than the sum of "Min DL level on candidate Cell" and the value of this parameter.
Min Access Level Offset
Issue 08 (2011-09-30)
714
Parameter Min UL Level on Candidate Cell FDD REP QUANT Min Ec/No threshold Min RSCP threshold
Description If the uplink received signal level of a neighbor cell is greater than "Min UL Level on Candidate Cell" plus "Min Access Level Offset", the neighbor cell can be listed in the candidate cell queue for handover. This parameter specifies whether Ec/No or RSCP is used for the measurement report on a FDD cell. Ec/No stands for the signal-to-noise ratio. RSCP stands for the received signal code power. Selects 3G candidate cells. If the measured value of a 3G neighboring cell is lower than this threshold, the 3G neighboring cell will be removed from among the 3G candidate cells. Selects 3G candidate cells. If the measured value of a 3G neighboring cell is lower than this threshold, the 3G neighboring cell will be removed from among the 3G candidate cells. After a load handover succeeds, the BSC punishes the former serving cell during "Penalty Time on Load HO" by subtracting "Penalty Value on Load HO" from the receive level of the former serving cell, thus avoiding ping-pong handovers. After a load handover succeeds, the BSC punishes the former serving cell during "Penalty Time on Load HO" by subtracting "Penalty Value on Load HO" from the receive level of the former serving cell, thus avoiding ping-pong handovers. Whether to enable a directed retry. The directed retry is to hand over an MS to a neighboring cell in the same procedure as the handover. The directed retry is an emergency measure applicable to abnormal traffic peaks in some areas of a radio network. You should not use the directed retry as a major means of solving traffic congestion. If the directed retry always occurs in some areas of a network, consider adjusting the sector and TRX configuration and the network layout. This parameter specifies whether a 2G cell or to a 3G cell is preferentially selected as the target cell for handover. When this parameter is set to Pre_2G_Cell, the BSC preferentially selects a 2G candidate cell as the target cell for handover. When this parameter is set to Pre_3G_Cell, the BSC preferentially selects a 3G candidate cell as the target cell for handover. When this parameter is set to Pre_2G_CellThres, the BSC preferentially selects a neighboring 3G cell as the handover target cell if the receive level of the neighboring 2G cell that ranks the first in the candidate cell list is equal to or smaller than "HO Preference Threshold for 2G Cell". Otherwise, the BSC preferentially selects a neighboring 2G cell as the handover target cell. If the receive level of the neighboring 2G cell that ranks the first in the candidate cell list is equal to or smaller than this threshold, the BSC preferentially selects a neighboring 3G cell as the handover target cell. Otherwise, the BSC preferentially selects a neighboring 2G cell as the handover target cell.
Penalty Value on Load HO
Penalty Time on Load HO
Directed Retry
Inter-rat Ho Preference
Issue 08 (2011-09-30)
715
Parameter Min Interval for Emerg. HO Quick Handover Enable Quick Move Speed Threshold Quick Handover Up Trigger Level Quick Handover Down Trigger Level
Description Minimum interval between two consecutive emergency handovers performed by an MS. During this interval, no emergency handover is allowed. Whether to allow the fast handover algorithm A quick handover can be initiated only if the rate of an MS is higher than this parameter during a certain period of time. Fast handover can be triggered only when the uplink signal level of the serving cell is less than this parameter. Fast handover can be triggered only when the downlink level of the serving cell is less than this parameter. Whether the cell is a chain neighboring cell. The parameter is used in the quick handover algorithm. Quick handover aims to increase the handover success rate of an MS moving at a high speed and to ensure the call continuity and low call drop rate. Quick handover applies to the scenario where an MS moves fast along an urban backbone road, a selected route, or a high-speed railroad. The target cell must be a chain neighboring cell. Handover direction forcast switch. When this parameter is set to YES, the BSC6900 can forecast the handover direction of the call in fast handover so that the best target cell can be selected for handover. This parameter indicates the geographical relationship between the neighboring cell and the serving cell. In the BSC6900, if direction A is selected, then the reverse direction is B. This parameter indicates P in the P/N rule for MS handover direction forcast. P/N rule: Among N handovers, the MS is handed over to Class B chain neighboring cell for successively P times, then the BSC6900 determines that the MS is moving to the Class B chain neighboring cell. This parameter indicates N in the P/N rule for MS handover direction forcast. P/N rule: Among N handovers, the MS is handed over to Class B chain neighboring cell for successively P times, then the BSC6900 determines that the MS is moving to the Class B chain neighboring cell. After the fast handover is successful, the penalty on the original serving cell is performed within the "Quick handover punish time": the receive level of the original serving cell is decreased by "Quick handover punish value", to prevent ping-pong handovers. To avoid ping-pong handover, the received signal of the original serving cell is decreased by "Quick handover punish value" in "Quick handover punish time" after fast handover succeeds.
Chain Neighbor Cell Handover Direction Forecast Enable Chain Neighbour Cell Type Handover Direction Forecast Last Times Handover Direction Forecast Statistic Times
Quick Handover Punish Time Quick Handover Punish Value
Issue 08 (2011-09-30)
716
Parameter
Description Whether to enable the time advance (TA) handover. The TA handover determines whether the timing advance (TA) is higher than the predefined TA threshold. When the TA is higher than the predefined TA threshold, a TA handover is triggered. The TA is calculated based on the distance between the MS and the BTS. The longer the distance is, the greater the TA value is. An emergency handover is triggered when TA is greater than or equal to the value of this parameter. This parameter specifies whether the handover from 2G cells to 3G cells is allowed. After the time advancing handover is successful, the penalty on the original serving cell is performed within the "Penalty Time after TA HO": the receive level of the original serving cell is decreased by "Penalty Level after TA HO", to prevent ping-pong handovers.
TA HO Allowed TA Threshold Inter-RAT Out BSC Handover Enable
Penalty Time after TA HO
After the time advancing handover is successful, the penalty on the original serving cell is performed within the "Penalty Time after TA Penalty Level after HO": the receive level of the original serving cell is decreased by TA HO "Penalty Level after TA HO", to prevent ping-pong handovers. Whether to enable the bad quality (BQ) handover algorithm. Whether to trigger BQ handover depends on the uplink and downlink transmit quality (measured by using BER). If the uplink or downlink BQ exceeds the BQ handover threshold, emergency BQ handover is triggered. The possible causes of BER increase (or quality degradation) include too low signal power and channel interference. An emergency handover due to bad quality is triggered when the uplink receive quality is not smaller than "UL Qual. Threshold". Downlink quality threshold for emergency handover. This parameter is represented as the product of 10 and a quality level that ranges from 0 to 7. The emergency handover can be triggered only when the downlink receive quality of an MS is greater(indicate bad quality) than this threshold. The value of this parameter corresponds to multiplying quality level 0 to 7 by 10. An emergency handover can be triggered only when the uplink receive quality of the MS is greater than the value of this parameter. Downlink quality limit for emergency handover in an AMR full rate call. The value of this parameter corresponds to the quality levels (0 to 7) multiplied by 10. An emergency handover can be triggered only when the downlink reception quality of an MS is higher than the value of this parameter, which indicates a poor quality.
BQ HO Allowed UL Qual. Threshold
DL Qual. Threshold
UL Qual. Limit for AMR FR
DL Qual. Limit for AMR FR
Issue 08 (2011-09-30)
717
Parameter
Description The value of this parameter corresponds to multiplying quality level 0 to 7 by 10. An emergency handover can be triggered only when the uplink receive quality of the MS is greater than the value of this parameter. Downlink quality limit for emergency handover in an AMR half rate call. The value of this parameter corresponds to the quality levels (0 to 7) multiplied by 10. An emergency handover can be triggered only when the downlink reception quality of an MS is higher than the value of this parameter, which indicates a poor quality. Hysteresis value during the handovers between cells, This value is used to suppress ping-pong handovers between cells. If ("downlink level of the neighbor cell after filtering" - "downlink level of the serving cell (after power control compensation)") > ("Inter-cell HO Hysteresis" - "BQ HO Margin" + 64), the BQ handover to the neighbor cell is triggered. This parameter specifies whether the intra-cell handover is enabled. Note: A forced intra-cell handover is not subject to this parameter. After a handover due to bad quality is successful, the penalty on the original serving cell is performed within the "Penalty Time after BQ HO": the receive level of the original serving cell is decreased by "Penalty Level after BQ HO", to prevent ping-pong handovers.
UL Qual. Limit for AMR HR
DL Qual. Limit for AMR HR Inter-cell HO Hysteresis
BQ HO Margin Intracell HO Allowed
Penalty Time after BQ HO
After a handover due to bad quality is successful, the penalty on the original serving cell is performed within the "Penalty Time after BQ Penalty Level after HO": the receive level of the original serving cell is decreased by BQ HO "Penalty Level after BQ HO", to prevent ping-pong handovers. Rx_Level_Drop HO Allowed Edge HO UL RX_LEV Threshold Whether to use the emergency handover algorithm in case the receive level of the MSs drops rapidly, thus preventing call drops. If the UL receive level remains lower than the "Edge HO UL RX_LEV Threshold" for a period, the edge handover is triggered. One of the nine parameters (filter parameters A1 to A8 and filter parameter B) used to configure the filter for determining whether the received signal level drops rapidly. The computation formula is as follows: C1(nt) = A1 x C(nt) + A2 x C(nt-t) + A3 x C(nt-2t) + ... + A8 x C(nt-7t) If C1(nt) is less than B and C(nt) is less than the threshold for edge handover, the signal level is considered dropping rapidly. In the formula, A1 to A8 are filter parameters A1 to A8 minus 10 and B is the negative of filter parameter B. C(nt) indicates the received signal level in the uplink measurement report of the serving cell received at time nt. Setting the filter helps to configure the maximum allowed signal level drop degree.
Filter Parameter A1
Issue 08 (2011-09-30)
718
Parameter
Description One of the nine parameters (filter parameters A1 to A8 and filter parameter B) used to configure the filter for determining whether the received signal level drops rapidly. The computation formula is as follows: C1(nt) = A1 x C(nt) + A2 x C(nt-t) + A3 x C(nt-2t) + ... + A8 x C(nt-7t) If C1(nt) is less than B and C(nt) is less than the threshold for edge handover, the signal level is considered dropping rapidly. In the formula, A1 to A8 are filter parameters A1 to A8 minus 10 and B is the negative of filter parameter B. C(nt) indicates the received signal level in the uplink measurement report of the serving cell received at time nt. Setting the filter helps to configure the maximum allowed signal level drop degree. One of the nine parameters (filter parameters A1 to A8 and filter parameter B) used to configure the filter for determining whether the received signal level drops rapidly. The computation formula is as follows: C1(nt) = A1 x C(nt) + A2 x C(nt-t) + A3 x C(nt-2t) + ... + A8 x C(nt-7t) If C1(nt) is less than B and C(nt) is less than the threshold for edge handover, the signal level is considered dropping rapidly. In the formula, A1 to A8 are filter parameters A1 to A8 minus 10 and B is the negative of filter parameter B. C(nt) indicates the received signal level in the uplink measurement report of the serving cell received at time nt. Setting the filter helps to configure the maximum allowed signal level drop degree. One of the nine parameters (filter parameters A1 to A8 and filter parameter B) used to configure the filter for determining whether the received signal level drops rapidly. The computation formula is as follows: C1(nt) = A1 x C(nt) + A2 x C(nt-t) + A3 x C(nt-2t) + ... + A8 x C(nt-7t) If C1(nt) is less than B and C(nt) is less than the threshold for edge handover, the signal level is considered dropping rapidly. In the formula, A1 to A8 are filter parameters A1 to A8 minus 10 and B is the negative of filter parameter B. C(nt) indicates the received signal level in the uplink measurement report of the serving cell received at time nt. Setting the filter helps to configure the maximum allowed signal level drop degree. One of the nine parameters (filter parameters A1 to A8 and filter parameter B) used to configure the filter for determining whether the received signal level drops rapidly. The computation formula is as follows: C1(nt) = A1 x C(nt) + A2 x C(nt-t) + A3 x C(nt-2t) + ... + A8 x C(nt-7t) If C1(nt) is less than B and C(nt) is less than the threshold for edge handover, the signal level is considered dropping rapidly. In the formula, A1 to A8 are filter parameters A1 to A8 minus 10 and B is the negative of filter parameter B. C(nt) indicates the received signal level in the uplink measurement report of the serving cell received at time nt. Setting the filter helps to configure the maximum allowed signal level drop degree.
Filter Parameter A2
Filter Parameter A3
Filter Parameter A4
Filter Parameter A5
Issue 08 (2011-09-30)
719
Parameter
Description One of the nine parameters (filter parameters A1 to A8 and filter parameter B) used to configure the filter for determining whether the received signal level drops rapidly. The computation formula is as follows: C1(nt) = A1 x C(nt) + A2 x C(nt-t) + A3 x C(nt-2t) + ... + A8 x C(nt-7t) If C1(nt) is less than B and C(nt) is less than the threshold for edge handover, the signal level is considered dropping rapidly. In the formula, A1 to A8 are filter parameters A1 to A8 minus 10 and B is the negative of filter parameter B. C(nt) indicates the received signal level in the uplink measurement report of the serving cell received at time nt. Setting the filter helps to configure the maximum allowed signal level drop degree. One of the nine parameters (filter parameters A1 to A8 and filter parameter B) used to configure the filter for determining whether the received signal level drops rapidly. The computation formula is as follows: C1(nt) = A1 x C(nt) + A2 x C(nt-t) + A3 x C(nt-2t) + ... + A8 x C(nt-7t) If C1(nt) is less than B and C(nt) is less than the threshold for edge handover, the signal level is considered dropping rapidly. In the formula, A1 to A8 are filter parameters A1 to A8 minus 10 and B is the negative of filter parameter B. C(nt) indicates the received signal level in the uplink measurement report of the serving cell received at time nt. Setting the filter helps to configure the maximum allowed signal level drop degree. One of the nine parameters (filter parameters A1 to A8 and filter parameter B) used to configure the filter for determining whether the received signal level drops rapidly. The computation formula is as follows: C1(nt) = A1 x C(nt) + A2 x C(nt-t) + A3 x C(nt-2t) + ... + A8 x C(nt-7t) If C1(nt) is less than B and C(nt) is less than the threshold for edge handover, the signal level is considered dropping rapidly. In the formula, A1 to A8 are filter parameters A1 to A8 minus 10 and B is the negative of filter parameter B. C(nt) indicates the received signal level in the uplink measurement report of the serving cell received at time nt. Setting the filter helps to configure the maximum allowed signal level drop degree. Trend of the received signal level of the cell during a period. This parameter helps to configure the filter for determining whether the received signal level drops rapidly. If this parameter is higher, a more rapid signal level drop is required to trigger the handover due to rapid signal level drop. Whether to allow the interference handover algorithm. Interference handovers are triggered when the receive level is higher than the receive threshold while the transmit quality is lower than the interference handover quality threshold, that is, when the MSs are subject to all kinds of radio interferences. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate.
Filter Parameter A6
Filter Parameter A7
Filter Parameter A8
Filter Parameter B
Interference HO Allowed Interfere HO Qual. Thresh 1 for NonAMR FR
Issue 08 (2011-09-30)
720
Parameter Interfere HO Qual. Thresh Offset for AMR FR Forbidden time after MAX Times
Description For AMR FR voice services, a fixed amount of offset is added to the corresponding grade of the received signal quality for the interference handover of non-AMR FR voice services. Duration in which intra-cell handover is forbidden after the number of consecutive intra-cell handovers reaches the maximum. Intra-cell handover can be conducted again only after this duration. Handover threshold during the handovers between cells on different layers or of different priorities. This value is used to suppress inter-layer ping-pong handovers. Inter-layer handover threshold of the serving cell = "Inter-layer HO threshold" - "Inter-layer HO Hysteresis"; Inter-layer handover threshold of a neighboring cell = "Inter-layer HO Threshold" + "Adjacent Cell Inter-layer HO Hysteresis" - 64. Hysteresis value during the handovers between cells on different layers or of different priorities. This value is used to suppress inter-layer pingpong handovers. Whether to enable the no-downlink measurement report handover algorithm When a certain number of no-downlink measurement reports are received consecutively and the uplink receive quality is no smaller than this parameter, no-downlink measurement report emergency handovers are triggered. No-downlink measurement report emergency handovers choose the inter-cell handover mode preferentially; however, if no candidate cells are available and intra-cell handover is enabled in the current cell, intra-cell handovers are triggered. Decisions of no-downlink measurement report handovers can be made only when the number of consecutive no-downlink measurement reports in the current call is no larger than this parameter. Number of measurement reports sampled for averaging the signal quality on a speech/data channel. Averaging the signal quality in multiple measurement reports helps to avoid a sharp signal quality drop due to Rayleigh fading and to ensure the comprehensiveness of a handover decision. For the purpose of accurately reflecting the radio environment of a network, filtering is performed on the measured values in several consecutive measurement reports. This parameter indicates the number of measurement reports used for the filtering of the signal quality on signaling channels. This parameter is used to determine whether interferences exist on channels. Whether to allow overlay-to-underlay load handovers. When the load of the underlay subcell is higher than this parameter, some of the calls in the underlay subcell will be switched to the overlay subcell, and channels in the overlay subcell will be preferentially assigned to calls initiated in the underlay subcell as well.
Inter-layer HO Threshold Adjacent Cell Inter-layer HO Hysteresis No Dl Mr.HO Allowed
No Dl Mr.Ul Qual HO Limit Cons.No Dl Mr.HO Allowed Limit
Filter Length for TCH Qual
Filter Length for SDCCH Qual. Load HO Allowed UL Subcell General Overload Threshold
Issue 08 (2011-09-30)
721
Parameter Inner Cell Serious OverLoad Thred
Description In an enhanced dual-band network, if the load of the overlay subcell is higher than this parameter, the system cannot initiate an underlay-tooverlay handover. If the current system flow control level is greater than this parameter, the handover between the underlaid and overlaid subcells due to low or high load in the underlaid subcell is not allowed. System flux thresholds correspond to the system flux obtained based on message packets, CPU load, and FID queuing load. The system flux level is the current flux control level of the system. 0-11: There are 12 flow control levels. Where, 0 indicates the lowest level and 11 indicates the highest level. The handover performed over the maximum threshold may have tremendous impacts on the system. Thus, this parameter should not be set to a higher value. 1) The flow control level algorithm for the assigned system messages: [(Average Message Usage - Inner Flow Control Discard Begin Threshold)/(Inner Flow Control Discard All Threshold - Inner Flow Control Discard Begin Threshold) x 100]/10+1 (rounddown for division operation). If the value is smaller than Inner Flow Control Discard Begin Threshold, Level 0 is used. If the value is equal to or greater than Inner Flow Control Discard Begin Threshold, the level is calculated. The value range is from 0 to 11. 2) Flow control threshold for the CPU to start to discard the channel access messages and paging messages: 80% . Flow control threshold for the CPU to discard all channel access messages and paging messages: 100% . CPU usage smaller than 80% corresponds to level 0. CPU usage equal to or greater than CPU flow control threshold 80% corresponds to level 2. An increase of 5% means an increase of 2 levels. Level 10 is the highest. The level value can be 0, 2, 4, 6, 8, and 10. Lower threshold of the overlay level during underlay-to-overlay handovers. When the receive level of an MS is higher than this threshold, the MS can be switched to the overlay subcell. When the load of the underlay subcell is higher than this parameter, the underlay-to-overlay load handover period subtracts a period that equals "Step Length of UL Subcell Load HO" from "UL Subcell Load Hierarchical HO Periods" every second, thus increasing the load handover speed. When the load of the underlay subcell exceeds "UL Subcell General Overload Threshold", all the calls that are using this cell as the serving cell generate handover requests at the same time, which will suddenly increase the load of the BSC and possibly cause congestion in the overlay subcell, thus causing the handovers to fail. To solve this problem, the BSC uses the hierarchical load handover algorithm to gradually switch some of the calls in the underlay subcell to the overlay subcell. This parameter indicates the duration of each handover level. If the underlay load is higher than "UL Subcell Serious Overload Threshold", the underlay-to-overlay handover period subtracts a value that equals this threshold from "UL Subcell Load Hierarchical HO Periods" every second.
Subcell HO Allowed Flow Control Level Incoming OL Subcell HO Level TH
UL Subcell Serious Overload Threshold
UL Subcell Load Hierarchical HO Periods MOD Step LEN of UL Load HO Period
Issue 08 (2011-09-30)
722
Parameter Step Length of UL Subcell Load HO
Description Level step during underlay-to-overlay hierarchical load handovers When the load of the underlay subcell is lower than this parameter, some of the calls in the overlay subcell will be switched to the underlay subcell, and channels in the underlay subcell will be preferentially assigned to channel requests initiated in the overlay subcell as well. Lower threshold of the overlay level during overlay-to-underlay handovers. When the receive level of an MS is higher than this threshold, the MS can be switched to the underlay subcell. Overlay-to-underlay load handovers are performed by levels. This parameter indicates the duration of each level. Level step during overlay-to-underlay hierarchical load handovers Distance between the boundary of the overlaid subcell and the boundary of the underlaid subcell. This parameter specifies the difference between the coverage of the overlaid subcell and the coverage of the underlaid subcell in the concentric cell or dual-frequency network scenario. The boundaries of the overlaid and underlaid subcells are determined according to the relative value between the signal strength of the serving cell and the signal strength of the neighbor cell. Assume that the signal strength of the serving cell is SS(s) and that the signal strength of the neighbor cell is SS(n). If SS(s) = SS(n), the MS is on the boundary of the underlaid subcell. If SS(s) - SS(n) > "Distance Between Boudaries of Subcells", the MS is in the coverage of the overlaid subcell. In the tight BCCH handover algorithm, this parameter specifies the difference between the coverage of the TRX that carries the BCCH and the coverage of the TRX that does not carry the BCCH. The relevant computation is the same as the preceding computation. Hysteresis in the distance between the boundary of the overlaid subcell and the boundary of the underlaid subcell. This parameter helps to adjust "Distance Between Boudaries of Subcells" and thus to prevent pingpong handover between the overlaid and underlaid subcells. Assume that the signal strength of the serving cell is SS(s) and that the signal strength of the neighbor cell is SS(n). If SS(s) - SS(n) < "Distance Between Boudaries of Subcells" - "Distance Hysteresis Between Boudaries", the MS is handed over from the overlaid subcell to the underlaid subcell. This parameter specifies whether a cell is the OL subcell or the UL subcell. This parameter is applied to the enhanced dualband cell.
UL Subcell Lower Load Threshold Outgoing OL Subcell HO Level TH OL Subcell Load Diversity HO Period Step Length of OL Subcell Load HO
Distance Between Boundaries of Subcells
Distance Hysteresis Between Boundaries Cell Inner/Extra Property Load HO of OL Subcell to UL Subcell
Whether to allow underlay-to-overlay load handovers
Issue 08 (2011-09-30)
723
Parameter
Description Threshold for downlink edge handover. If the downlink receive level remains less than this threshold for a period of time, the edge handover is triggered. If the PBGT handover algorithm is enabled, this threshold can be decreased accordingly. If the PBGT handover algorithm is disabled, over-coverage, co-channel interference, and adjacent channel interference may occur when this threshold is set improperly. In addition, to ensure uplink-downlink balance, this threshold needs to be adjusted according to the handover performance statistics and actual network performance. The load handover is triggered when the traffic load in a cell is greater than the value of this parameter. If the load of a cell is lower than the value of this parameter, the cell can admit the users handed over from other cells with higher load. Otherwise, the cell rejects such users. In hierarchical load handovers, starting from "Edge HO DL RX_LEV Threshold", a "Load HO Step Level" is added to the upper handover threshold after every "Load HO Step Period". In this way, all the calls in the current serving cell whose receive level is in the range "Edge HO DL RX_LEV Threshold" to "Edge HO DL RX_LEV Threshold" + "Load HO Bandwidth" are switched to other cells. When the load of a cell reaches or exceeds "Load HO Threshold", all the calls that are using this cell as the serving cell generate handover requests at the same time, which will suddenly increase the load of the processor. Under some circumstances, congestion occurs in the cell, which will result in call drop. To solve this problem, the BSC uses the hierarchical load handover algorithm to control the number of users included in each level of handovers. This parameter indicates the duration of each handover level. In the handover algorithm of the first generation, load handovers can be performed only when the receive level of the current serving cell is in the range "Edge HO DL RX_LEV Threshold" to "Edge HO DL RX_LEV Threshold" + "Load HO Bandwidth". In the handover algorithm of the second generation, load handovers can be performed only when the level difference between the neighboring cell and the serving cell is between "Inter-cell HO Hysteresis" - "Load HO Bandwidth" and "Inter-cell HO Hysteresis". This parameter specifies whether a traffic load-sharing handover is enabled. The load handover helps to reduce cell congestion, improve success rate of channel assignment, and balance the traffic load among cells, thus improving the network performance. The load handover is used as an emergency measure instead of a primary measure to adjust abnormal traffic burst in partial areas. If load handovers occur frequently in a partial area, the cell and TRX configuration of BTSs and the network layout should be adjusted.
Edge HO DL RX_LEV Threshold Load HO Threshold Load handover Load Accept Threshold
Load HO Step Level
Load HO Step Period
Load HO Bandwidth
Load Handover Support
Issue 08 (2011-09-30)
724
Parameter
Description System flux thresholds correspond to the system flux obtained based on message packets, CPU load, and FID queuing load. The system flux level is the current flux control level of the system. 0-11: There are 12 flow control levels. Where, 0 indicates the lowest level and 11 indicates the highest level. A load handover is allowed only when the system flux is lower than the value of this parameter. The handover performed over the maximum threshold may have tremendous impacts on the system. Thus, this parameter should not be set to a higher value. 1) The flow control level algorithm for the assigned system messages: [(Average Message Usage - Inner Flow Control Discard Begin Threshold)/(Inner Flow Control Discard All Threshold - Inner Flow Control Discard Begin Threshold) x 100]/10+1 (round-down for division operation). If the value is smaller than Inner Flow Control Discard Begin Threshold, Level 0 is used. If the value is equal to or greater than Inner Flow Control Discard Begin Threshold, the level is calculated. The value range is from 0 to 11. 2) Flow control threshold for the CPU to start to discard the channel access messages and paging messages: 80% . Flow control threshold for the CPU to discard all channel access messages and paging messages: 100% . CPU usage smaller than 80% corresponds to level 0. CPU usage equal to or greater than CPU flow control threshold 80% corresponds to level 2. An increase of 5% means an increase of 2 levels. Level 10 is the highest. The level value can be 0, 2, 4, 6, 8, and 10. Whether to use external 2G neighboring cells as the target cells of load handovers Whether to enable the edge handover algorithm. When an MS makes a call at the edge of a cell, the call may drop if the received signal level is too low. To avoid such a call drop, the edge handover algorithm is involved. When the uplink signal level of the serving cell is less than "Edge HO UL RX_LEV Threshold" or the downlink signal level of the serving cell is less than "Edge HO DL RX_LEV Threshold", the edge handover is triggered. According to the P/N rule, if the conditions for edge handover are met for P seconds within N seconds, the handover is triggered. This parameter specifies the number P. According to the P/N rule, if the conditions for edge handover are met for P seconds within N seconds, the handover is triggered. This parameter specifies the number N. According to the P/N rule, if a neighbor cell meets the conditions for selecting the neighbor cell for edge handover in P of N measurement reports, the edge handover to the neighbor cell is triggered. This parameter specifies the number P. According to the P/N rule, if a neighbor cell meets the conditions for selecting the neighbor cell for edge handover in P of N measurement reports, the edge handover to the neighbor cell is triggered. This parameter specifies the number N.
System Flux Threshold for Load HO Inter BSC Load Information Allowed
Edge HO Allowed Handover Algorithm I Edge HO Valid Time Handover Algorithm I Edge HO Watch Time
Edge HO AdjCell Valid Time
Edge HO AdjCell Watch Time
Issue 08 (2011-09-30)
725
Parameter MS Fast Moving HO Allowed
Description Whether to enable the fast moving micro-cell handover algorithm. The fast moving micro-cell handover algorithm enables fast moving MSs to switch over to macro-cells, thus reducing the handover times. A time threshold determined based on the radius of a cell and the moving speed of an MS. If the MS crosses the cell in a time period shorter than this threshold, the BSC concludes that the MS quickly passes through the cell. Otherwise, it concludes that the MS slowly passes the cell. This parameter is used in the P/N criteria decision: If an MS quickly passes through N out of P micro-cells lately, the BSC enables the fast moving micro-cell handover algorithm. This parameter corresponds to the N in the P/N criteria. This parameter is used in the P/N criteria decision: If an MS quickly passes through N out of P micro-cells lately, the BSC enables the fast moving micro-cell handover algorithm. This parameter corresponds to the P in the P/N criteria. Layer of the cell. If the layer of the cell is lower, it is more likely that a handover to the cell will be triggered. Whether to allow inter-layer and inter-level handovers. The inter-layer and inter-level handover algorithm is achieved through the setting of different layers and priorities for cells, which switches traffic to cells of a higher precedence (decided by "Layer of the cell" and "Cell priority" together). The triggering of inter-layer handovers must meet the P/N criteria, that is, when the condition for inter-layer handovers is met for a consecutive P seconds during N seconds, an inter-layer handover is triggered. This parameter corresponds to the P in the P/N criteria. The triggering of inter-layer handovers must meet the P/N criteria, that is, when the condition for inter-layer handovers is met for a consecutive P seconds during N seconds, an inter-layer handover is triggered. This parameter corresponds to the N in the P/N criteria. Whether to use the PBGT handover algorithm. PBGT handovers are based on path loss. The PBGT handover algorithm searches in real time for cells that have lower path loss and meet certain system requirements, and decides whether to perform the handovers. To avoid ping-pong handovers, PBGT handovers can occur only on TCHs and among cells on a same layer and a same priority level. The triggering of PBGT handovers must meet the P/N criteria, that is, when the condition for PBGT handovers is met for a consecutive P seconds during N seconds, a PBGT handover is triggered. This parameter corresponds to the P in the P/N criteria.
MS Fast-moving Time Threshold
MS Fast-moving Watch Cells
MS Fast-moving Valid Cells Layer of the cell
Level HO Allowed
Layer HO Valid Time
Layer HO Watch Time
PBGT HO Allowed
PBGT Valid Time
Issue 08 (2011-09-30)
726
Parameter
Description The triggering of PBGT handovers must meet the P/N criteria, that is, when the condition for PBGT handovers is met for a consecutive P seconds during N seconds, a PBGT handover is triggered. This parameter corresponds to the N in the P/N criteria. PBGT handovers to a neighboring cell are allowed only when the downlink level difference between the neighboring cell and the serving cell is larger than this parameter. When the value of this parameter is smaller than 64, handovers to a neighboring cell with a lower level than the current serving cell are allowed. Whether to allow AMR handovers. This parameter has no impact on dynamic non-AMR F-H handovers. Whether to enable the BSC to assign AMR half rate channels preferentially according to the channel types allowed by the MSC and the current TCH seizure ratio of the cell.When this parameter is set to OFF, the load of the serving cell will not be considered in a handover from an AMR full-rate channel to an AMR half-rate channel. Load threshold for assigning half rate channels preferentially. If the current TCH seizure ratio of the cell is greater than this threshold, AMR half rate channels are assigned preferentially. For an AMR call, if the currently occupied channel is a full rate channel and the value of the Radio Quality Indication (RQI) in measurement report divided by 2 is always higher than the threshold set by this parameter, an intra-cell F-H handover is triggered. The triggering of intra-cell F-H handovers must meet the P/N criteria, that is, when the condition for intra-cell F-H handovers is met for P seconds during N seconds, an intra-cell F-H handover is triggered. This parameter corresponds to the P in the P/N criteria. The triggering of intra-cell F-H handovers must meet the P/N criteria, that is, when the condition for intra-cell F-H handovers is met for P seconds during N seconds, an intra-cell F-H handover is triggered. This parameter corresponds to the N in the P/N criteria. For an AMR call, if the currently occupied channel is a half rate channel and the value of the Radio Quality Indication (RQI) in measurement report divided by 2 is always lower than the threshold set by this parameter, an intra-cell H-F handover is triggered. The P/N criterion must be met for triggering a TA handover. That is, the TA handover can be triggered only if P measurement reports among N measurement reports meet the triggering conditions. This parameter corresponds to P in the P/N criterion. The P/N criterion must be met for triggering a TA handover. That is, the TA handover can be triggered only if P measurement reports among N measurement reports meet the triggering conditions. This parameter corresponds to N in the P/N criterion.
PBGT Watch Time
PBGT HO Threshold Intracell F-H HO Allowed
AMR TCH/H Prior Allowed AMR TCH/H Prior Cell Load Threshold
F2H HO Threshold
Intracell F-H HO Last Time
Intracell F-H HO Stat Time
H2F HO Threshold
TA HO Valid Time
TA HO Watch Time
Issue 08 (2011-09-30)
727
Parameter
Description Hysteresis value during the handovers between cells on different layers or of different priorities. This value is used to suppress inter-layer pingpong handovers. Inter-layer handover threshold of the serving cell = "Inter-layer HO threshold" - "Inter-layer HO Hysteresis"; Inter-layer handover threshold of a neighboring cell = "Inter-layer HO threshold" + "Adjacent Cell Inter-layer HO Hysteresis" - 64. According to the P/N rule, if the conditions for emergency BQ handover are met in P of N measurement reports, the handover is triggered. This parameter specifies the number P. According to the P/N rule, if the conditions for emergency BQ handover are met in P of N measurement reports, the handover is triggered. This parameter specifies the number N.
Inter-layer HO Hysteresis BQ HO Valid Time BQ HO Watch Time
The triggering of interference handovers must meet the P/N criteria, that is, when P out of N measurement reports meet the condition for Interfere HO Valid interference handovers, a concentric circle handover is triggered. This Time parameter corresponds to the P in the P/N criteria. The triggering of interference handovers must meet the P/N criteria, that is, when P out of N measurement reports meet the condition for interference handovers, a concentric circle handover is triggered. This parameter corresponds to the N in the P/N criteria. The P/N criterion must be met for triggering a UL BQ handover. That is, the UL BQ handover can be triggered only if P measurement reports among N measurement reports meet the triggering conditions. This parameter corresponds to P in the P/N criterion. The P/N criterion must be met for triggering a UL BQ handover. That is, the UL BQ handover can be triggered only if P measurement reports among N measurement reports meet the triggering conditions. This parameter corresponds to N in the P/N criterion. According to the P/N rule, if the conditions for edge handover are met in P of N measurement reports, the handover is triggered. This parameter specifies the number P. According to the P/N rule, if the conditions for edge handover are met in P of N measurement reports, the handover is triggered. This parameter specifies the number N. According to the P/N rule, if the conditions for the handover to a different micro cell due to fast movement are met in P of N measurement reports, the handover is triggered. This parameter specifies the number P. According to the P/N rule, if the conditions for the handover to a different micro cell due to fast movement are met in P of N measurement reports, the handover is triggered. This parameter specifies the number N.
Interfere HO Static Time
UL BQ HO Last Time
UL BQ HO Static Time Handover Algorithm II Edge HO Valid Time Handover Algorithm II Edge HO Watch Time
HCS HO Valid Time
HCS HO Watch Time
Issue 08 (2011-09-30)
728
Parameter Better Cell Handover Enable Pathloss Ho. Enable Better Cell HO Valid Time Better Cell HO Watch Time AMR F-H Ho Allowed AMR F-H Ho Pathloss Threshold AMR F-H Ho ATCB Threshold
Description Whether to enable the algorithm for the handover to a better cell Whether to perform path loss-based sorting in a better cell handover algorithm According to the P/N rule, if the conditions for the handover to a better cell due to interference are met for P seconds within N seconds, the handover is triggered. This parameter specifies the number P. According to the P/N rule, if the conditions for the handover to a better cell due to interference are met for P seconds within N seconds, the handover is triggered. This parameter specifies the number N. Whether to enable the algorithm for the load-based AMR handover between full rate and half rate Path loss threshold for the AMR handover from full rate to half rate. If the path loss of an AMR full rate call is equal to or less than this threshold, the AMR call is handed over from full rate to half rate. ATCB threshold for the AMR handover from full rate to half rate. If the ATCB of an AMR full rate call is equal to or greater than this threshold, the AMR call is handed over from full rate to half rate. Quality threshold for the AMR handover from full rate to half rate. If the uplink and downlink receive quality levels of an AMR full rate call are equal to or less than this threshold, the AMR call is handed over from full rate to half rate. According to the P/N rule, if the conditions for the handover from full rate to half rate are met for P seconds within N seconds, the handover is triggered. This parameter specifies the number P. According to the P/N rule, if the conditions for the handover from full rate to half rate are met for P seconds within N seconds, the handover is triggered. This parameter specifies the number N. Whether to allow non-AMR voice F-H handover When the path loss value of non-AMR full rate voice is no larger than this parameter, the condition for non-AMR F-H handovers is met. When the ATCB value of non-AMR full rate voice is no smaller than this parameter, the condition for non-AMR F-H handovers is met. Whether to enable the algorithm for the uplink and downlink receive quality based AMR handover from half rate to full rate Path loss threshold for the AMR handover from half rate to full rate. If the path loss of an AMR half rate call is greater than this threshold, the AMR call is handed over from half rate to full rate.
AMR F-H Ho Qual. Threshold
F-H Ho Last Time
F-H Ho Stat. Time Non-AMR F-H Ho Allowed Non-AMR F-H Ho Pathloss Threshold Non-AMR F-H Ho ATCB Threshold Allow AMR H-F Quality-based HO AMR H-F Ho Pathloss Threshold
Issue 08 (2011-09-30)
729
Parameter AMR H-F Ho ATCB Threshold AMR H-F Ho Qual. Threshold
Description ATCB threshold for the AMR handover from half rate to full rate. If the ATCB of an AMR half rate call is less than this threshold, the AMR call is handed over from half rate to full rate. Quality threshold for the AMR handover from half rate to full rate. If the receive quality level of an AMR half rate call is greater than this threshold, the AMR call is handed over from half rate to full rate. According to the P/N rule, if the conditions for the handover from half rate to full rate are met for P seconds within N seconds, the handover is triggered. This parameter specifies the number P. According to the P/N rule, if the conditions for the handover from half rate to full rate are met for P seconds within N seconds, the handover is triggered. This parameter specifies the number N. Whether to trigger non-AMR H-F handovers according to the uplink and downlink receive quality When the path loss value of non-AMR half rate voice is no smaller than this threshold, the condition for non-AMR H-F handovers is met. When the ATCB value of non-AMR half rate voice is no larger than this threshold, the condition for non-AMR H-F handovers is met. Quality threshold for non-AMR H-F handovers. When the receive quality of a user is no smaller than this parameter, the user meets the condition for H-F handovers. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate.
H-F Ho Last Time
H-F Ho Stat. Time Allow Non-AMR H-F Quality-based HO Non-AMR H-F Ho Pathloss Threshold Non-AMR H-F Ho ATCB Threshold Non-AMR H-F Ho Qual. Threshold Interfere HO Qual. Thresh 2 for NonAMR FR Interfere HO Qual. Thresh 3 for NonAMR FR Interfere HO Qual. Thresh 4 for NonAMR FR Interfere HO Qual. Thresh 5 for NonAMR FR Interfere HO Qual. Thresh 6 for NonAMR FR Interfere HO Qual. Thresh 7 for NonAMR FR
Issue 08 (2011-09-30)
730
Parameter Interfere HO Qual. Thresh 8 for NonAMR FR Interfere HO Qual. Thresh 9 for NonAMR FR Interfere HO Qual. Thresh 10 for NonAMR FR Interfere HO Qual. Thresh 11 for NonAMR FR Interfere HO Qual. Thresh 12 for NonAMR FR
Description Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate. Threshold for the interference handover of Non-AMR FR voice services. AMRFR refers to Adaptive Multi-Rate Full Rate. This parameter controls handover between cells at the same layer. Generally, the cells at the same layer are set with the same priority. If the cells at the same layer have different priorities, a cell with a smaller priority value has a higher priority. Whether to adjust the candidate cell queue to give priority to intra-BSC/ MSC handover. K offset used in K sequencing. To reduce ping-pong handovers, the system performs K sorting based on the downlink receive level of the candidate cells. But before doing that, the system subtracts "K Bias" from the actual downlink receive level of the candidate cells. This parameter adjusts "Min RSCP threshold" to enable the selection of 3G candidate cells based on cell priorities. As a performance counter for 3G cells, Ec/No indicates the ratio of the energy per received chip to the spectral noise power density. If the Ec/ No of a 3G neighbor cell is greater than "HOECNOTH3G" plus this parameter, the neighbor cell is listed in the candidate cell queue. This parameter determines whether a cell supports enhanced outgoing cell handover. Level offset configured for the serving cell when an edge handover toward a neighboring cell is triggered. When both Enhanced Outgoing Cell Handover Offset and EDGE HO Allowed are set to YES for a cell, the BSC considers the level offset for the serving cell when triggers an edge handover.
Cell Priority
Co-BSC/MSC Adj
K Bias
RSCP Offset
Ec/No Offset
Enhanced Outgoing Cell Handover Allowed Enhanced Outgoing Cell Handover Offset
Issue 08 (2011-09-30)
731
Parameter
Description This switch determines whether to apply penalty on a neighboring cell when the PBGT or hierarchical handover in handover algorithm I or the better cell handover in handover algorithm II is triggered. This purpose is to prevent a call from being improperly handed over to the neighboring cell. This parameter specifies the level threshold to stop the timer used for applying penalty on a neighboring cell. This parameter specifies the length of the timer used for applying penalty on a neighboring cell. This parameter specifies the level used for applying penalty on a neighboring cell. When this parameter is set to ENABLE, if the cell supports direct retry and the current cell load is equal to or larger than the value of "Cell direct retry forbidden threshold" in "SET GCELLOTHEXT" during the assignment, the BSC6900 continues with the direct retry procedure. When this parameter is set to DISABLE, the current call applies for channels in its own cells. If the application fails, it continues with the direct retry procedure. Threshold of the load in the target cell for the directed retry. Only a cell whose load is lower than or equal to this threshold can be selected as a candicate target cell. Maximum signal level difference between the neighbor cell and the serving cell for triggering directed retry In a direct retry, when the receive level of a neighboring cell is no smaller than this parameter, the neighboring cell can be a candidate cell for the direct retry. The parameter is invalid in handover algorithm II.
Neighboring Cell Penalty Switch
Penalty Stop Level Threshold Penalty Timer Length Level Penalty Value on Neighboring Cell
Assignment Cell Load Judge Enable
Directed Retry Load Access Threshold Directed Retry Handover Level Range Min Power Level For Directed Retry
Issue 08 (2011-09-30)
732
Table 2-123 Parameter description (2) Paramete r Default Value GUI Value Range Actual Value Range Unit MML Command SET GCELLHOBASI C(Optional) HOALGO RITHM1 (Handover algorithm I), HOALGO RITHM2 (Handover algorithm II) BSC_Prep rocessing (BSC preprocess ing), BTS_Prep rocessing (BTS preprocess ing) NO(No), YES(Yes) SET GCELLHOIUO (Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOEMG (Optional) Impact
Current HO Control Algorithm
HOALGO RITHM1
HOALGO RITHM1, HOALGO RITHM2
None
Cell
MR.Prepr ocessing Transfer Original MR Transfer BTS/MS Power Class
BTS_Prep rocessing
BSC_Prep rocessing, BTS_Prep rocessing
None
SET GCELLHOCTRL (Optional) SET GCELLHOCTRL (Optional) SET GCELLHOCTRL (Optional)
Cell
NO
NO, YES
None
Cell
YES
NO(No), YES(Yes)
NO, YES
None
Cell
Issue 08 (2011-09-30)
733
Paramete r
Default Value
GUI Value Range NOreport (Do not report), Twice_ps (Twice every second), Once_ps (Once every second), Once_2s (Once every two second), Once_4s (Once every four second) EnhMeas Report (Enhanced Measurem ent Report), ComMeas Report (Common Measurem ent Report)
Actual Value Range
Unit
MML Command
Impact
Sent Freq.of preprocess ed MR
Once_ps
NOreport, Twice_ps, Once_ps, Once_2s, Once_4s
None
Cell
Measurem ent Report Type Allowed MR Number Lost Power Level Penalty on Fast Moving HO Penalty on MS Fast Moving HO
ComMeas Report
None
SET GCELLCCUTRA NSYS(Optional) SET GCELLHOFITPE N(Optional) SET GTRXDEV (Optional) ADD GEXT2GCELL (Optional) SET GCELLHOAD (Optional)
Cell
4 0
0~31 0~13
0~31 0~13
None None
Cell TRX
30
0~63
0~63
dB
Cell
30
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
734
Paramete r Penalty Time on Fast Moving HO Penalty Time after AMR TCHF-H HO Fail Penalty Time on Interfere HO Penalty Time of UtoO HO Inter UL/ OL Subcells HO Penalty Time Penalty Level after HO Fail UmPenalt yTimer RscPenalt yTimer CfgPenalt yTimer Penalty Time after OtoU HO Fail
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command
Impact
40
0~255
0~255
SET GCELLHOAD (Optional)
Cell
10
0~255
0~255
SET GCELLHOFITPE N(Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOIUO (Optional)
Cell
15
0~255
0~255
Cell
10
0~255
0~255
Cell
0~255
0~255
SET GCELLHOEDBP ARA(Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOIUO (Optional)
Cell
30
0~63
0~63
dB
Cell
10
0~255
0~255
Cell
0~255
0~255
Cell
255
0~255
0~255
Cell
10
0~255
0~255
Cell
Issue 08 (2011-09-30)
735
Paramete r Penalty Time after UtoO HO Fail Inter-BSC SDCCH HO ALLowed Min DL Level on Candidate Cell Min Access Level Offset Min UL Level on Candidate Cell
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command
Impact
40
10~255
10~255
SET GCELLHOIUO (Optional) SET GCELLHOCTRL (Optional) SET GCELLHOBASI C(Optional) ADD G2GNCELL (Optional) SET GCELLHOBASI C(Optional) SET GCELLCCUTRA NSYS(Optional) ADD GEXT3GCELL (Optional) ADD GEXT3GCELL (Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOFITPE N(Optional) SET GCELLBASICP ARA(Optional)
Cell
NO
NO(No), YES(Yes)
NO, YES
None
Cell
10
0~63
0~63
dB
Cell
0~63
0~63
dB
Cell
0~63 RSCP (RSCP), EcN0(Ec/ N0)
0~63
dB
Cell
FDD REP QUANT Min Ec/ No threshold Min RSCP threshold Penalty Value on Load HO Penalty Time on Load HO Directed Retry
RSCP
RSCP, EcN0
None
Cell
10
0~49
0~49
dB
Cell
10
0~63
0~63
dB
Cell
63
0~63
0~63
dB
Cell
10
0~255 NO(No), YES(Yes)
0~255
Cell
YES
NO, YES
None
Cell
Issue 08 (2011-09-30)
736
Paramete r
Default Value
GUI Value Range Pre_2G_C ell (Preferenc e for 2G cell), Pre_3G_C ell (Preferenc e for 3G cell), Pre_2G_C ellThres (Preferenc e 2G cell by thresh)
Actual Value Range
Unit
MML Command
Impact
Inter-rat Ho Preference
Pre_2G_C ellThres
Pre_2G_C ell, Pre_3G_C ell, Pre_2G_C ellThres
None
SET GCELLHOUTRA NFDD(Optional) SET GCELLHOUTRA NFDD(Optional) SET GCELLHOUTRA NTDD(Optional) SET GCELLHOCTRL (Optional) SET GCELLHOBASI C(Optional) SET GCELLHOFAST (Optional)
Cell
HO Preference Threshold for 2G Cell Min Interval for Emerg. HO Quick Handover Enable Quick Move Speed Threshold Quick Handover Up Trigger Level Quick Handover Down Trigger Level
25
0~63
0~63
dB
Cell
0~60
Cell
NO
NO, YES
None
Cell
35
0~600
0~600
m/s
Cell
50
0~63
0~63
dB
SET GCELLHOFAST (Optional)
Cell
50
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
737
Paramete r Chain Neighbor Cell Handover Direction Forecast Enable
Default Value
GUI Value Range NO(No), YES(Yes)
Actual Value Range
Unit
MML Command ADD G2GNCELL (Optional) SET GCELLHOFAST (Optional)
Impact
NO
NO, YES
None
Cell
NO
NO(No), YES(Yes) QUICK_ HO_NCE LL_TYPE _A (QUICK_ HO_NCE LL_TYPE _A), QUICK_ HO_NCE LL_TYPE _B (QUICK_ HO_NCE LL_TYPE _B)
NO, YES
None
Cell
Chain Neighbour Cell Type Handover Direction Forecast Last Times Handover Direction Forecast Statistic Times Quick Handover Punish Time Quick Handover Punish Value
QUICK_ HO_NCE LL_TYPE _A
QUICK_ HO_NCE LL_TYPE _A, QUICK_ HO_NCE LL_TYPE _B
None
ADD G2GNCELL (Optional)
Cell
0~16
0~16
None
Cell
0~16
0~16
None
SET GCELLHOFAST (Optional) ADD GEXT2GCELL (Optional) SET GCELLHOFAST (Optional) ADD GEXT2GCELL (Optional) SET GCELLHOFAST (Optional)
Cell
10
0~255
0~255
Cell
63
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
738
Paramete r
Default Value
Actual Value Range
Unit
MML Command SET GCELLHOBASI C(Optional) SET GCELLHOEMG (Optional) SET GCELLHOBASI C(Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOEMG (Optional) SET GCELLHOEMG (Optional) SET GCELLAMRQU L(Optional) SET GCELLAMRQU L(Optional) SET GCELLAMRQU L(Optional) SET GCELLAMRQU L(Optional) ADD G2GNCELL (Optional)
Impact
TA HO Allowed TA Threshold Inter-RAT Out BSC Handover Enable Penalty Time after TA HO Penalty Level after TA HO BQ HO Allowed UL Qual. Threshold DL Qual. Threshold UL Qual. Limit for AMR FR DL Qual. Limit for AMR FR UL Qual. Limit for AMR HR DL Qual. Limit for AMR HR Inter-cell HO Hysteresis
YES
NO, YES
None
Cell
255
0~255
0~255
bit
Cell
NO
NO(No), YES(Yes)
NO, YES
None
Cell
30
0~255
0~255
Cell
63
0~63
dB
Cell
YES
NO, YES
None
Cell
55
0~70
0~70
None
Cell
55
0~70
0~70
None
Cell
60
0~70
0~70
None
Cell
60
0~70
0~70
None
Cell
55
0~70
0~70
None
Cell
55
0~70
0~70
None
Cell
68
0~127
0~127
dB
Cell
Issue 08 (2011-09-30)
739
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command ADD G2GNCELL (Optional) SET GCELLHOBASI C(Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOFITPE N(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOEMG (Optional) SET GCELLHOEMG (Optional) SET GCELLHOEMG (Optional) SET GCELLHOEMG (Optional) SET GCELLHOEMG (Optional) SET GCELLHOEMG (Optional) SET GCELLHOEMG (Optional)
Impact
BQ HO Margin Intracell HO Allowed Penalty Time after BQ HO Penalty Level after BQ HO Rx_Level _Drop HO Allowed Edge HO UL RX_LEV Threshold Filter Parameter A1 Filter Parameter A2 Filter Parameter A3 Filter Parameter A4 Filter Parameter A5 Filter Parameter A6 Filter Parameter A7
69
0~127
dB
Cell
NO
NO, YES
None
Cell
10
0~255
0~255
Cell
63
0~63
dB
Cell
NO
NO, YES
None
Cell
10
0~63
0~63
dB
Cell
10
0~20
0~20
None
Cell
10
0~20
0~20
None
Cell
10
0~20
0~20
None
Cell
10
0~20
0~20
None
Cell
10
0~20
0~20
None
Cell
10
0~20
0~20
None
Cell
10
0~20
0~20
None
Cell
Issue 08 (2011-09-30)
740
Paramete r Filter Parameter A8 Filter Parameter B Interferen ce HO Allowed Interfere HO Qual. Thresh 1 for NonAMR FR Interfere HO Qual. Thresh Offset for AMR FR Forbidden time after MAX Times
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command SET GCELLHOEMG (Optional) SET GCELLHOEMG (Optional) SET GCELLHOBASI C(Optional)
Impact
10
0~20
0~20
None
Cell
0~200
None
Cell
YES
NO, YES
None
Cell
60
0~70
0~70
None
SET GCELLAMRQU L(Optional)
Cell
0~70
0~70
None
SET GCELLAMRQU L(Optional) SET GCELLHOAD (Optional) ADD GEXT2GCELL (Optional)
Cell
20
1~200
1~200
Cell
Inter-layer HO Threshold Adjacent Cell Interlayer HO Hysteresis No Dl Mr.HO Allowed No Dl Mr.Ul Qual HO Limit
25
0~63
0~63
dB
SET GCELLHOBASI C(Optional) ADD G2GNCELL (Optional) SET GCELLHOEMG (Optional) SET GCELLHOEMG (Optional)
Cell
67
0~127
dB
Cell
NO
NO, YES
None
Cell
50
0~70
0~70
None
Cell
Issue 08 (2011-09-30)
741
Paramete r Cons.No Dl Mr.HO Allowed Limit
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command
Impact
0~64
0~64 TCH: 480~1488 0, step: 480; SDCCH: 470~1457 0, step:470 TCH: 480~1536 0, step: 480; SDCCH: 470~1504 0, step:470
None
SET GCELLHOEMG (Optional)
Cell
Filter Length for TCH Qual
1~31
ms
SET GCELLHOFITPE N(Optional)
Cell
Filter Length for SDCCH Qual. Load HO Allowed UL Subcell General Overload Threshold Inner Cell Serious OverLoad Thred Subcell HO Allowed Flow Control Level Incoming OL Subcell HO Level TH
ms
SET GCELLCHMGA D(Optional) SET GCELLHOEDBP ARA(Optional)
Cell
YES
NO, YES
None
Cell
80
0~100
0~100
per cent
SET GCELLHOEDBP ARA(Optional) SET GCELLHOEDBP ARA(Optional)
Cell
90
0~100
0~100
per cent
Cell
10
0~11
0~11
None
SET GCELLHOEDBP ARA(Optional)
Cell
30
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
742
Paramete r UL Subcell Serious Overload Threshold UL Subcell Load Hierarchic al HO Periods MOD Step LEN of UL Load HO Period Step Length of UL Subcell Load HO UL Subcell Lower Load Threshold Outgoing OL Subcell HO Level TH OL Subcell Load Diversity HO Period Step Length of OL Subcell Load HO
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command
Impact
90
0~100
0~100
per cent
Cell
1~255
1~255
SET GCELLHOEDBP ARA(Optional) SET GCELLHOEDBP ARA(Optional)
Cell
1~255
1~255
Cell
0~63
0~63
dB
Cell
50
0~100
0~100
per cent
Cell
25
0~63
0~63
dB
Cell
10
1~255
1~255
Cell
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
743
Paramete r Distance Between Boundarie s of Subcells Distance Hysteresis Between Boundarie s Cell Inner/ Extra Property Load HO of OL Subcell to UL Subcell Edge HO DL RX_LEV Threshold Load HO Threshold
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command
Impact
10
0~63
0~63
dB
Cell
0~63 Inner (Inner), Extra (Extra)
0~63
dB
Cell
None
Inner, Extra
None
ADD GCELL (Mandatory)
Cell
NO
NO(No), YES(Yes)
NO, YES
None
SET GCELLHOEDBP ARA(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOAD (Optional) ADD GEXT2GCELL (Optional) ADD GEXT3GCELL (Optional) SET GCELLHOAD (Optional) SET GCELLHOAD (Optional) SET GCELLHOAD (Optional) SET GCELLHOAD (Optional)
Cell
20
0~63
0~63
dB
Cell
90
0~100
0~100
None
Cell
Load handover Load Accept Threshold Load HO Step Level Load HO Step Period Load HO Bandwidt h
80
0~100
0~100
per cent
Cell
1~63
1~63
dB
Cell
10
1~255
1~255
Cell
25
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
744
Paramete r Load Handover Support System Flux Threshold for Load HO Inter BSC Load Informatio n Allowed Edge HO Allowed Handover Algorithm I Edge HO Valid Time Handover Algorithm I Edge HO Watch Time Edge HO AdjCell Valid Time Edge HO AdjCell Watch Time MS Fast Moving HO Allowed MS Fastmoving Time Threshold
Default Value
Actual Value Range
Unit
MML Command SET GCELLHOBASI C(Optional)
Impact
NO
NO, YES
None
Cell
10
0,8~11
0, 8~11
None
SET GCELLHOAD (Optional) SET GCELLHOAD (Optional) SET GCELLHOBASI C(Optional)
Cell
NO
NO(No), YES(Yes) NO(No), YES(Yes)
NO, YES
None
Cell
YES
NO, YES
None
Cell
1~32
0.5~16, step:0.5
SET GCELLHOBASI C(Optional)
Cell
1~32
0.5~16, step:0.5
SET GCELLHOBASI C(Optional) ADD G2GNCELL (Optional) ADD G2GNCELL (Optional) SET GCELLHOBASI C(Optional) SET GCELLHOAD (Optional)
Cell
1~32
0.5~16, step:0.5
Cell
1~32
0.5~16, step:0.5
Cell
NO
NO(No), YES(Yes)
NO, YES
None
Cell
15
0~255
0~255
Cell
Issue 08 (2011-09-30)
745
Paramete r MS Fastmoving Watch Cells MS Fastmoving Valid Cells Layer of the cell Level HO Allowed Layer HO Valid Time Layer HO Watch Time PBGT HO Allowed PBGT Valid Time PBGT Watch Time PBGT HO Threshold Intracell F-H HO Allowed AMR TCH/H Prior Allowed
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command
Impact
1~10
1~10
None
SET GCELLHOAD (Optional) SET GCELLHOAD (Optional) ADD GEXT3GCELL (Optional) SET GCELLHOBASI C(Optional) ADD G2GNCELL (Optional) ADD G2GNCELL (Optional) SET GCELLHOBASI C(Optional) ADD G2GNCELL (Optional) ADD G2GNCELL (Optional) ADD G2GNCELL (Optional) SET GCELLHOBASI C(Optional) SET GCELLCHMGA D(Optional)
Cell
1~10
1~10
None
Cell
1, 2, 3, 4 NO(No), YES(Yes)
1, 2, 3, 4
None
Cell
YES
NO, YES 0.5~16, step:0.5 0.5~16, step:0.5
None
Cell
1~32
Cell
Cell
YES
NO, YES 0.5~16, step:0.5 0.5~16, step:0.5
None
Cell
1~32
Cell
1~32
Cell
68
0~127
dB
Cell
YES
NO, YES
None
Cell
ON
OFF(Off), ON(On)
OFF, ON
None
Cell
Issue 08 (2011-09-30)
746
Paramete r AMR TCH/H Prior Cell Load Threshold F2H HO Threshold Intracell F-H HO Last Time Intracell F-H HO Stat Time H2F HO Threshold TA HO Valid Time TA HO Watch Time Inter-layer HO Hysteresis BQ HO Valid Time BQ HO Watch Time Interfere HO Valid Time Interfere HO Static Time
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command
Impact
55
0~99
0~99
per cent
SET GCELLCHMGA D(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) ADD G2GNCELL (Optional) ADD G2GNCELL (Optional) SET GCELLHOBASI C(Optional) ADD G2GNCELL (Optional) ADD G2GNCELL (Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional)
Cell
25
0~39
0~39 0.5~16, step:0.5 0.5~16, step:0.5
None
Cell
1~32
Cell
10
1~32
Cell
12
0~39
0~39 0.5~8, step:0.5 0.5~0.8, step:0.5
None
Cell
1~16
Cell
1~16
Cell
0~63
0~63 0.5~8, step:0.5 0.5~8, step:0.5 0.5~8, step:0.5 0.5~8, step:0.5
dB
Cell
1~16
Cell
1~16
Cell
1~16
Cell
0~16
Cell
Issue 08 (2011-09-30)
747
Paramete r UL BQ HO Last Time UL BQ HO Static Time Handover Algorithm II Edge HO Valid Time Handover Algorithm II Edge HO Watch Time HCS HO Valid Time HCS HO Watch Time Better Cell Handover Enable Pathloss Ho. Enable Better Cell HO Valid Time Better Cell HO Watch Time AMR F-H Ho Allowed AMR F-H Ho Pathloss Threshold
Default Value
GUI Value Range
Actual Value Range 0.5~4, step:0.5 0.5~4, step:0.5
Unit
MML Command ADD G2GNCELL (Optional) ADD G2GNCELL (Optional)
Impact
1~8
Cell
1~8
Cell
1~32
0.5~16, step:0.5
SET GCELLHOBASI C(Optional)
Cell
1~32
0.5~16, step:0.5 0.5~8, step:0.5 0.5~8, step:0.5
SET GCELLHOBASI C(Optional) ADD G2GNCELL (Optional) ADD G2GNCELL (Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) ADD G2GNCELL (Optional) ADD G2GNCELL (Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional)
Cell
1~16
Cell
1~16 NO(No), YES(Yes) NO(No), YES(Yes)
Cell
YES
NO, YES
None
Cell
NO
NO, YES 0.5~16, step:0.5 0.5~16, step:0.5
None
Cell
1~32
Cell
Cell
NO
NO, YES
None
Cell
100
0~255
0~255
dB
Cell
Issue 08 (2011-09-30)
748
Paramete r AMR F-H Ho ATCB Threshold AMR F-H Ho Qual. Threshold F-H Ho Last Time F-H Ho Stat. Time Non-AMR F-H Ho Allowed Non-AMR F-H Ho Pathloss Threshold Non-AMR F-H Ho ATCB Threshold Allow AMR H-F Qualitybased HO AMR H-F Ho Pathloss Threshold AMR H-F Ho ATCB Threshold AMR H-F Ho Qual. Threshold H-F Ho Last Time
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional)
Impact
20
0~255
0~255
dB
Cell
0~7
0~7 0.5~16, step:0.5 0.5~16, step:0.5
None
Cell
1~32
Cell
Cell
NO
NO, YES
None
Cell
95
0~255
0~255
dB
Cell
30
0~255
0~255
dB
Cell
NO
NO(No), YES(Yes)
NO, YES
None
Cell
108
0~255
0~255
dB
Cell
0~255
0~255
dB
Cell
0~7
0~7 0.5~16, step:0.5
None
Cell
1~32
Cell
Issue 08 (2011-09-30)
749
Paramete r
Default Value
GUI Value Range
Actual Value Range 0.5~16, step:0.5
Unit
MML Command SET GCELLHOBASI C(Optional)
Impact
H-F Ho Stat. Time Allow Non-AMR H-F Qualitybased HO Non-AMR H-F Ho Pathloss Threshold Non-AMR H-F Ho ATCB Threshold Non-AMR H-F Ho Qual. Threshold Interfere HO Qual. Thresh 2 for NonAMR FR Interfere HO Qual. Thresh 3 for NonAMR FR Interfere HO Qual. Thresh 4 for NonAMR FR Interfere HO Qual. Thresh 5 for NonAMR FR
1~32
Cell
NO
NO(No), YES(Yes)
NO, YES
None
SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional) SET GCELLHOBASI C(Optional)
Cell
103
0~255
0~255
dB
Cell
14
0~255
0~255
dB
Cell
0~7
0~7
None
Cell
50
0~70
0~70
None
Cell
49
0~70
0~70
None
Cell
48
0~70
0~70
None
Cell
47
0~70
0~70
None
Cell
Issue 08 (2011-09-30)
750
Paramete r Interfere HO Qual. Thresh 6 for NonAMR FR Interfere HO Qual. Thresh 7 for NonAMR FR Interfere HO Qual. Thresh 8 for NonAMR FR Interfere HO Qual. Thresh 9 for NonAMR FR Interfere HO Qual. Thresh 10 for NonAMR FR Interfere HO Qual. Thresh 11 for NonAMR FR Interfere HO Qual. Thresh 12 for NonAMR FR
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command
Impact
46
0~70
0~70
None
Cell
45
0~70
0~70
None
Cell
44
0~70
0~70
None
Cell
43
0~70
0~70
None
Cell
42
0~70
0~70
None
Cell
41
0~70
0~70
None
Cell
40
0~70
0~70
None
Cell
Issue 08 (2011-09-30)
751
Paramete r
Default Value
GUI Value Range PRIOR-1 (Priority-1 ), PRIOR-2 (Priority-2 ), PRIOR-3 (Priority-3 ), PRIOR-4 (Priority-4 ), PRIOR-5 (Priority-5 ), PRIOR-6 (Priority-6 ), PRIOR-7 (Priority-7 ), PRIOR-8 (Priority-8 ), PRIOR-9 (Priority-9 ), PRIOR-10 (Priority-1 0), PRIOR-11 (Priority-1 1), PRIOR-12 (Priority-1 2), PRIOR-13 (Priority-1 3), PRIOR-14 (Priority-1 4), PRIOR-15 (Priority-1 5), PRIOR-16 (Priority-1 6)
Actual Value Range
Unit
MML Command
Impact
Cell Priority
None
PRIOR-1, PRIOR-2, PRIOR-3, PRIOR-4, PRIOR-5, PRIOR-6, PRIOR-7, PRIOR-8, PRIOR-9, PRIOR-10 , PRIOR-11 , PRIOR-12 , PRIOR-13 , PRIOR-14 , PRIOR-15 , PRIOR-16
None
SET GCELLBASICP ARA(Optional)
Cell
Issue 08 (2011-09-30)
752
Paramete r Co-BSC/ MSC Adj
Default Value
Actual Value Range NO, YES
Unit
MML Command SET GCELLHOBASI C(Optional) SET GCELLHOAD (Optional) ADD G3GNCELL (Optional) ADD G3GNCELL (Optional) SET GCELLHOBASI C(Optional)
Impact
YES
None
Cell
K Bias
0~63
0~63
dB
Cell
RSCP Offset Ec/No Offset Enhanced Outgoing Cell Handover Allowed Enhanced Outgoing Cell Handover Offset Neighbori ng Cell Penalty Switch Penalty Stop Level Threshold Penalty Timer Length Level Penalty Value on Neighbori ng Cell
0~63
0~63
dB
Cell
0~49
0~49
dB
Cell
NO, YES NO NO(No), YES(Yes)
None
Cell
64
0~127
0~127
None
Cell
NO 20
NO(No), YES(Yes) 0~63
NO, YES
None
ADD G2GNCELL (Optional) ADD G2GNCELL (Optional) ADD G2GNCELL (Optional) ADD G2GNCELL (Optional)
Cell
0~63
None
Cell
0~255
0~255
Cell
10
0~63
0~63
None
Cell
Issue 08 (2011-09-30)
753
Paramete r Assignme nt Cell Load Judge Enable Directed Retry Load Access Threshold Directed Retry Handover Level Range Min Power Level For Directed Retry
Default Value
GUI Value Range DISABLE (Disable), ENABLE (Enable)
Actual Value Range
Unit
MML Command
Impact
DISABLE
DISABLE , ENABLE
None
SET GCELLCCBASI C(Optional)
Cell
85
0~100
0~100
per cent
SET GCELLCCBASI C(Optional)
Cell
72
0~128
0~128
dB
Cell
16
0~63
0~63
dB
Cell
2.46.5 Counters
2.46.6 Glossary

l l l l l l l l
Issue 08 (2011-09-30)
3GPP TS 08.58 Base Station Controler - Base Transceiver Station (BCS-BTS) Interface Layer 3 Specification 3GPP TS 04.08 Mobile radio interface layer 3 specification BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.47 Handover Re-establishment

2.47.1 Introduction
2.47.1.1 Scope
This document describes the benefits of handover re-establishment and its implementation.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to a change in the handover re-establishment feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.47.2 Overview
In the handover procedure generally, if the BSC does not receive a response from the MS but receives an Error Indication message from the BTS after sending the Handover Command to the MS, the BSC regards that call drop occurs and then initiates the release procedure. After Handover Re-establishment is enabled, the BSC initiates the procedure for re-establishing the connection at the data link layer of the Um interface on the source channel. If the connection reestablishment is successful, the MS resumes the call without a call drop. Handover Re-establishment reduces the call drop rate during handover, thus improving user satisfaction and network KPIs.
NOTE
Handover Re-establishment does not support directed retry.

2.47.3.1 Implementation in the BSS
The implementation of Handover Re-establishment in the BSS is as follows: 1. 2. If the parameter Activate L2 Re-establishment is set to Yes and the BTS TRX supports Handover Re-establishment, the BSC can enable Handover Re-establishment. After receiving the Error Indication message, the BSC determines the phase at which the call is being processed. When the call is waiting for intra-cell handover completion or waiting for inter-cell handover completion, the BSC sends the Establish Request message on the source channel, requesting the BTS to re-establish the connection at the data link layer of the Um interface. 3. 4. After receiving the Establish Request message, the BTS initiates the procedure for reestablishing the connection at the data link layer of the Um interface. The MS cooperates with the BTS to re-establish the connection at the data link layer of the Um interface.
Issue 08 (2011-09-30)
5.
The call is re-assigned to the source channel, and thus the call resumes.
Figure 2-153 shows the signaling procedure of Handover Re-establishment Figure 2-153 Signaling procedure of Handover Re-establishment
2.47.3.2 Impact on the KPI

Enabling Handover Re-establishment may reduce the call drop rate during the handover and assignment procedures.
2.47.4 Parameters
This chapter describes the parameters related to handover re-establishment . For the meaning of each parameter, see Table 2-124. For the default value, value ranges, and MML commands of each parameter, see Table 2-125.
Issue 08 (2011-09-30)
757
Table 2-124 Parameter description (1) Parameter Description Whether to activate the function of L2 re-establishment. If this function is activated, the BSC starts the attempt of L2 re-establishment when the BSC receives an ERR IND message reported by the BTS in a conversation of MSs. If the L2 re-establishment succeeds, the conversation continues; otherwise, a call drop occurs.
Activate L2 Reestablishment
Table 2-125 Parameter description (2) Paramete r Activate L2 Reestablishm ent Default Value GUI Value Range Actual Value Range Unit MML Comman d SET GCELLS OFT (Optional) Impact
NO
NO(No), YES(Yes)
NO, YES
None
Cell
2.47.5 Counters
2.47.6 Glossary

l l l l l BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.48 High-Speed Signaling

2.48.1 Introduction
2.48.1.1 Scope
This document describes the implementation of high-speed signaling links. It also describes the comparison between the high-speed signaling link and the 64 kbit/s signaling link.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the High-Speed Signaling feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 has no change.
2.48.2 Overview
Two types of signaling links are available in the SS7 network: 64 kbit/s signaling link and 2 Mbit/s signaling link. The 2 Mbit/s signaling link, also called high-speed signaling link, is the No.7 signaling link in the SS7 network with a data rate of N x 64 kbit/s (1 N < 32). Here, N indicates the number of timeslots occupied by the high-speed signaling link. The BSC uses the high-speed signaling links when the signaling load of the system is high. The high-speed signaling link has the following features: l l A high-speed signaling link occupies multiple 64 kbit/s timeslots with a transmission rate of N 64 kbit/s (1 N < 32). The electrical features of the high-speed signaling link port comply with the ITU-T G.703 and its frame structure complies with the ITU-T G.704.
NOTE
The naming of the 2 Mbit/s high speed signaling link is specified by the ITU protocols. In actual situations, the maximum data rate of the high-speed signaling link is 1,984 kbit/s.
The BSC uses the high-speed signaling links when the 64 kbit/s signaling links fail to meet the signaling requirements on the A interface due to high traffic volume. The high speed signaling links are used in the following scenarios: l l Some timeslots over a port are used to transmit speech information and the other timeslots are used to transmit signaling information. A telecom operator chooses high-speed signaling links with different data rates based on the load of the signaling links.

2.48.3.1 Implementation of 2 Mbit/s Signaling Link
The TDM interface board of the Ater interface or the A interface (EIUa/OIUa/POUc board) processes the signaling of 2 Mbit/s signaling link based on the MTP2 and MTP1 protocols, whereas the 2G signaling processing board (XPUa/XPUb board) processes the signaling based on the MTP3 protocol.
Processing of No.7 Signaling in the BSC

The No.7 signaling is processed differently for the BSC subracks configured in different modes. l l Figure 2-154 shows the processing of the No.7 signaling in BM/TC separated mode. Figure 2-155 shows the processing of the No.7 signaling in BM/TC combined mode.
Issue 08 (2011-09-30)
760
Figure 2-154 Signaling link on the A interface (BM/TC separated)
1.
In the MPS/EPS, the XPUa/XPUb board processes the signaling based on the MTP3, SCCP, and BSSAP protocols, and then forwards the processed signaling to the EIUa/OIUa/POUc board of the Ater interface in the same subrack or in another subrack through the SCUa board. In the MPS/EPS, the EIUa/OIUa/POUc board processes the signaling based on the MTP2 and MTP1 protocols. Then, the processed signaling is forwarded to the EIUa/OIUa/POUc board in the TCS over the Ater interface. In the TCS, the TNU board performs timeslot-based TDM switching of the signaling, and then transmits the signaling to the EIUa/OIUa/POUc board of the A interface. The signaling is transmitted to the MSC over the A interface.
2.
3. 4.
Figure 2-155 Signaling link on the A interface (BM/TC combined)
1.
In the MPS/EPS, the XPUa/XPUb board processes the signaling based on the MTP3, SCCP, and BSSAP protocols, and then forwards the processed signaling to the EIUa/OIUa/POUc board of the A interface in the same subrack or in another subrack through the SCUa board. The EIUa/OIUa/POUc board of the A interface processes the signaling based on the MTP2 and MTP1 protocols. Then, the signaling is transmitted to the MSC over the A interface.
2.
Issue 08 (2011-09-30)
Configuration Principles
The configuration principles are as follows: l l l l l Do not allocate timeslot 0 to the 2 Mbit/s signaling link. The timeslots allocated to a 2 Mbit/s signaling link can be discontinuous. When you allocate N (1 N < 32) 64 kbit/s timeslots to a 2 Mbit/s signaling link, Huawei recommends that N ranges from 8 to 25. Either 2 Mbit/s signaling link or 64 kbit/s signaling link can be configured for the BSC to communicate with a destination signaling point. For one EIUa/OIUa board, either 2 Mbit/s signaling link or 64 kbit/s signaling link can be configured. When multiple 2 Mbit/s signaling links are configured, they must be of the same bandwidth. The 2 Mbit/s signaling links in a BSC must be of the same bandwidth, thus ensuring load balance between different signaling links. The primary BSC and the secondary BSCs in a TC pool can be configured with 2 Mbit/s signaling links of different bandwidth. The signaling links in the GSM telecommunications system are very important, and thus the reliability of the 2 Mbit/s signaling links must be taken into account. In actual situations, Huawei recommends that at least two signaling links are available in the same signaling point, and that the two signaling links use different E1 or STM-1. When multiple Ater/A interface boards are configured, the signaling links should be allocated to different boards. Determine the signaling mode used between the BSC and MSC before configuring the signaling links in the BSC. Configure the 2 Mbit/s signaling links in the BSC if eight or more 64 kbit/s signaling links are required, considering the signaling transfer capacity between the BSC and MSC. The TS number of the timeslots allocated for a 2 Mbit/s signaling link must be the same between the BSC and the MSC. Configure the E1 port number based on the connection of the E1 cable. The BSC6900 supports the MSC POOL feature, which means that one BSC can be connected to multiple MSCs, MSC servers, or MGWs. In this case, you need to configure the No.7 signaling links according to the proportion of the A interface CICs between the BSC and the MSCs (MSC Servers or MGWs) to the total A interface CICs. Each 2 Mbit/s signaling link can be configured only in one E1 port of the Ater/A interface board. Multiple 2 Mbit/s signaling links can be configured in one E1 port of the Ater/A interface board and occupy different timeslots over the E1 port. If the 2 Mbit/s signaling link on the Ater/A interface board is removed, you need to reset the board before configuring the 64 kbit/s signaling link. If the 64 kbit/s signaling link on the Ater/A interface board is removed, you need to reset the board before configuring the 2 Mbit/s signaling link. A maximum of eight 2 Mbit/s signaling links can be configured in one EIUa/OIUa board. A maximum of 64 signaling links can be configured in one POUc board. The number of signaling link timeslots must not exceed 128.
l l l
l l l
l l l l l l
If the 2 Mbit/s signaling links are configured in the BSC, the MTP3 link management entity of the BSC continuously attempts to establish signaling links. Once the signaling links are successfully established, the signaling messages can be transmitted.
2.48.3.2 Comparison Between 2 Mbit/s Signaling Link and 64 kbit/s Signaling Link
This section compares the 2 Mbit/s signaling link with the 64 kbit/s signaling link in terms of implementation and functions.
Implementation
The implementation differences between the 2 Mbit/s signaling link and the 64 kbit/s signaling link are classified into the following types: l Format of signaling messages The Backward Sequence Number (BSN) and Forward Sequence Number (FSN) in the 64 kbit/s signaling link are 7 bits in length. The BSN and FSN in the 2 Mbit/s signaling link are 12 bits in length, ranging from 0 to 4095. Figure 2-156 shows the formats of the signal units in the 2 Mbit/s signaling link. The Length Indicator (LI) in the 64 kbit/s signaling link is 6 bits in length. The LI in the 2 Mbit/s signaling link is 9 bits in length, ranging from 0 to 511. The 9-bit LI can indicate the 272-octet information field supported by the MTP. Figure 2-156 Formats of the signal units in the 2 Mbit/s signaling link
Error correction methods The 2 Mbit/s signaling link adopts the basic error correction method. This method detects the error signal units by defining the error time segments with flags. The 64 kbit/s signal link adopts the preventive cyclic retransmission method.
l l
The sequence-related messages such as Changeover-Order signal (COO) and ChangeoverAcknowledgement signal (COA) are different in format. The basic buffer capacity in error correction is as follows: The retransmission buffer area at the sending end of the 2 Mbit/s signaling link is 4095 in length, greater than that of the 64 kbit/s signaling link.
Issue 08 (2011-09-30)
763
The buffer area at the receiving end of the 2 Mbit/s signaling link is greater than that of the 64 kbit/s signaling link.
Functions
l Delimitation and alignment of signal units The flag byte (F) can be used to delimit a signal unit. The bit pattern for the flag byte is 01111110. The zero-bit insertion method is applied to ensure that the pattern does not incidentally appear in the signal unit. Loss of alignment occurs when a bit pattern disallowed by the delimitation procedure (more than six consecutive 1 s) is received, or when the allowed length of the signal unit is exceeded. l Acceptance procedure Upon detection of an error signal unit, the acceptance procedure defines the time segment with a flag and starts a counter, which is incremented every time a signal unit error is detected. If the counter exceeds the threshold, the signaling link is defined as invalid. l Error detection The error detection function is performed by means of 16 check bits provided at the end of each signal unit. l Error correction The 2 Mbit/s signaling link adopts the basic error correction method, a noncompelled method in which the positive/negative acknowledgements and the retransmission mechanisms are used to ensure correct transfer of message signal units. Before the positive acknowledgements are received, the transmitted signal units are stored in the transmitting sequence. This mechanism enables that the transmitted but not yet positively acknowledged signal units remain available for retransmission. The transmission of new signal units is temporarily stopped during retransmissions. l l Initial alignment Initial alignment applies to the activation and restoration of a signaling link. Error monitoring Error monitoring is performed when a signaling link is either in the error time segments or in the proving state of the initial alignment procedure. l Flow Control Upon detection of congestion at the receiving end of the signaling link, the flow control mechanism is activated at the receiving end. A certain status signal of the signaling link is sent to the transmitting end, informing the transmitting end of stopping transmitting the signal units already acknowledged. If the congestion is released, acknowledgements of input signal units are resumed by the signaling link. If the congestion persists, the receiving end periodically sends a link status signal unit to the transmitting end of the signaling link. If the congestion period exceeds a predefined threshold, the transmitting end recognizes a signaling link failure and exits the services.
2.48.4 Parameters
None.
2.48.5 Counters
None.
2.48.6 Glossary

This chapter lists the reference documents related to High-Speed Signaling. l l l l ITU_T Q.703, "Specifications of Signalling System No. 7 - Message transfer part signalling link" BSC6900 Feature List BSC6900 Optional Feature Description BSS Reconfiguration Guide
2.49 Idle Mode Behavior

2.49.1 Introduction
2.49.1.1 Scope
This document describes the behavior of the MS in idle mode and of the network. The behavior includes the procedures of public land mobile network (PLMN) selection, cell selection, cell reselection, location area update, paging, and cell broadcast. This document also describes control channels and system information.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Idle Mode Behavior feature of a specific product version. l
Issue 08 (2011-09-30)
Editorial change
Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01 (2009-11-20)
2.49.2 Overview
An MS that is switched on but is not allocated a dedicated channel is defined as an MS in idle mode. An MS in idle mode can access the network and can be reached by the network. When an MS is switched on, it attempts to select a PLMN for registration. The MS selects a PLMN either automatically or manually. In the selected PLMN, the MS searches for a suitable cell and then tunes to the control channel of the selected cell to receive system information. This procedure is called cell selection. The MS in idle mode always attempts to camp on the best cell according to a signal strength based criterion. After the MS camps on a cell, the received signal strength may deteriorate due to interference or MS mobility. In this case, the MS can select another cell to camp on. This procedure is called cell reselection. When a cell selection or cell reselection is complete, the MS camps on the selected cell. After the MS selects a PLMN and finds a suitable cell, the MS must register its current location on the network so that the network knows where to route incoming calls. The MS may move from place to place, and therefore the location changes from time to time. In certain conditions, the MS may initiate a location area update procedure so that the network can locate the MS in real time. When receiving an incoming call, the network searches for the MS and sends the paging message according to the registered location of the MS. The idle mode behavior is managed by the MS and is controlled by the parameters contained in the system information that is broadcast on the BCCH. The idle mode behavior has the following impacts on the network performance and service handling: l Selection of the cell with the best signal strength In the case of cell selection and cell reselection, the MS always attempts to select the cell with the best signal strength to achieve a better QoS. Cell selection and cell reselection are controlled by parameters. By adjusting the settings of these parameters, a cell absorbs MSs in a controlled manner. l Control of the paging load In idle mode, the MS notifies the network of its location whenever the MS changes its location area through the location area update procedure. Then, the network stores the latest location information about the MS. When the network receives an incoming call, it knows in which location area it can page the MS and does not need to page the MS throughout the
service area. This reduces the paging load. If the MS does not respond to the first paging message, the network may send a second paging message. The MS, periodically and when switched on or off, notifies the network of its present status through the location area update procedure. This prevents the network from paging the MS when the MS has been switched off or has left the coverage area. Otherwise, this causes unnecessary load to the system. l Low power consumption In idle mode, the MS discontinuously listens to the system information of the serving cell and performs measurements on neighboring cells to evaluate whether a cell change is required. The MS is in sleep mode in most time. Therefore, the power consumption of the MS is low in idle mode.

2.49.3.1 Overview
In idle mode, the MS continuously measures the transmit signal strength on the BCCH carrier frequencies of the serving cell and neighboring cells to find a suitable cell to camp on. The MS may also register the location information about the selected cell through a location area update procedure as required. After camping on a cell, an MS can: l l l Receive system information from the cell Access the RACH of the cell to initiate a call Receive a paging message from the network when there is an incoming call
The tasks performed by an MS in idle mode can be divided into four procedures. Figure 2-157 illustrates the relations between the four procedures. 1. 2. 3. 4. PLMN selection Cell selection Cell reselection Location area update
Figure 2-157 Relations between the four procedures
2.49.3.2 PLMN Selection

?.1. Overview
The MS will select a PLMN when it is switched on or re-enters the network coverage area. It will attempt to select the last registered PLMN if any exists. When the MS is successfully registered on a PLMN, it shows this PLMN on its screen. The MS is allowed to initiate or receive calls on this PLMN. If there is no last registered PLMN or if the last registered PLMN is
unavailable, the MS will attempt to select another PLMN either automatically or manually, depending on its operating mode. The MS usually operates on its home PLMN. When the MS leaves the coverage area of the home PLMN, it may select another PLMN. If the MS finds a suitable cell to camp on or if a location area update request is accepted, the MS will register on the PLMN. The registration on the PLMN has to be successful in order for the MS to access the network. In the case of national roaming, the MS may select and register on a visited PLMN. In this case, the MS periodically attempts to return to its home PLMN. The time interval between two consecutive attempts is stored in the subscriber identity module (SIM) and is managed by the network operator. In the case of international roaming, the MS may select and register on a visited PLMN. In this case, the MS does not attempt to return to its home PLMN. PLMN selection can be performed in automatic mode or manual mode. l l In automatic mode, the MS selects a PLMN from a PLMN list. The PLMNs in the list are ranked in order of priority. In manual mode, the user selects a PLMN among those indicated by the MS. The user can request the MS to select and register on an available PLMN as required.
?.2. Automatic PLMN Selection Mode

In automatic mode, the MS selects a PLMN that is available and permitted. If there is no last registered PLMN or the last registered PLMN is unavailable, the MS selects a PLMN in the following order: 1. 2. 3. 4. Home PLMN Each PLMN stored in the SIM, in priority order Other PLMNs with receive level above -85 dBm, in random order All other PLMNs in descending order of signal strength
?.3. Manual PLMN Selection Mode

In manual mode, if a registered PLMN or the home PLMN exists, the MS first attempts to select the PLMN. If registration fails or the user starts a PLMN reselection, the MS displays all available PLMNs. The user can then select a desired PLMN, which causes the MS to initiate a registration on this PLMN. If the selected PLMN is forbidden, the MS prompts the user to select another PLMN.
2.49.3.3 GSM Cell Selection

?.1. Overview
When an MS is switched on or enters the network coverage area, it scans all the carrier frequencies permitted by the PLMN and selects a suitable cell to camp on. This procedure is called cell selection.
?.2. Conditions for Normally Camping on a Cell

To perform services normally, an MS must camp on a suitable cell by registering on the PLMN and tuning to the control channel of the cell. Then, the MS can receive system information and
paging messages and initiate calls. A cell is considered suitable when the following conditions are met: l l The cell belongs to the selected PLMN. The cell is not barred.
NOTE
For details about whether a cell is barred, see Table 2-126.
l l
The cell does not belong to a location area included in the list of "forbidden location areas for roaming". The path loss from the MS to the BTS is lower than the preset threshold, that is, C1 must be greater than 0.
?.3. Cell Selection Criterion

C1 indicates the path loss criterion of cell selection. C1 of the serving cell must be greater than 0. It is calculated as follows: l C1 = RXLEV - RXLEV_ACCESS_MIN - MAX((MS_TXPWR_MAX_CCH - P), 0)
In the case of a DCS1800 class 3 MS, C1 is calculated as follows: l C1=RXLEV - RXLEV_ACCESS_MIN - MAX((MS_ TXPWR_MAX_CCH + POWER OFFSET - P), 0)
where: l l l l l RXLEV indicates the average receive level of the MS in the unit of dBm. RXLEV_ACCESS_MIN indicates the minimum receive level (unit: dBm) required for the MS to access the network. It is specified by the RXLEV_ACCESS_MIN parameter. MS_TXPWR_MAX_CCH indicates the maximum transmit power (unit: dBm) allowed for the MS to access the network. It is specified by the MS_TXPWR_MAX_CCH parameter. POWER OFFSET indicates Power Deviation (unit: dBm) of the MS. The setting of the Power Deviation Indication parameter determines whether Power Deviation takes effect. P indicates the maximum output power of the MS in the unit of dBm.
The MS selects a cell to camp on according to the cell selection priority and C1. The selected cell becomes the serving cell. As shown in Figure 2-158, if the two cells have the same cell selection priority, the MS selects Cell1, the one with the higher path loss criterion, as the serving cell. Figure 2-158 Cell selection
Issue 08 (2011-09-30)
769
The cell selection priority is determined by Cell bar qualify and Cell Access Bar Switch, as listed in Table 2-126. Table 2-126 Cell selection priority Cell Selection Priority Cell bar qualify 0 0 1 1 Cell Access Bar Switch 0 1 0 1 Normal Forbidden Low Low Cell Reselection Priority Normal Forbidden Normal Normal
2.49.3.4 GSM Cell Reselection

?.1. Overview
After an MS selects a suitable cell as the serving cell, the MS camps on this cell if there are no changes in other conditions. At the same time, the MS continues to monitor all the BCCH carrier frequencies specified in the neighboring cell frequency list (BA1 list), which is indicated by the system information of the serving cell. For each BCCH carrier frequency, the MS needs to measure the receive level at not less than five sampling points and calculates the average receive level. The total number of sampling points for each BCCH carrier frequency should be the same. In each measurement period, the number of sampling points for each BCCH carrier frequency should also be the same. The six strongest BCCH carrier frequencies need to be updated at least every minute. To save power consumption, the MS needs to measure the receive level of all the carrier frequencies contained in the BA1 list when decoding the messages on the paging subchannel. At the same time, the MS can obtain the BCCH carrier frequencies contained in the BA1 list and some receive level measurement samples of the BCCH carrier frequency of the serving cell. The MS also performs routine measurements on the BCCH carrier frequency of the serving cell. The MS needs to attempt to decode all the system information that is broadcast on the BCCH of the serving cell at least every 30 seconds. The MS needs to decode the data blocks transmitted over the BCCH carrier frequencies of the six strongest neighboring cells at least every five minutes. The data blocks contain the parameters that affect cell reselection. When the MS finds that a new BCCH carrier frequency becomes one of the six strongest BCCH carrier frequencies, it needs to decode the data blocks transmitted over the new BCCH carrier frequency within 30 seconds. The MS also needs to check the Base Station Identity Code (BSIC) of each of the six strongest neighboring cells at least every 30 seconds to ensure that the same cells are being monitored. If another BSIC is detected, the MS considers that the BCCH carrier frequency is a new one. In this case, the MS decodes the data blocks transmitted over this BCCH carrier frequency. In all the preceding conditions, the MS attempts not to disrupt the monitoring of the PCH.
?.2. Conditions for Triggering Cell Reselection

Cell reselection is triggered if any of the following conditions is met:
l l
The C2 value of a certain cell (located in the same location area as the serving cell) is greater than the C2 value of the serving cell for five consecutive seconds. The C2 value of a certain cell (not located in the same location area as the serving cell) is greater than the sum of the C2 value of the serving cell and the value of Cell Reselect Hysteresis Parameters for five consecutive seconds. If a cell reselection was performed 15 seconds earlier, a new cell reselection is not triggered. The serving cell is barred or the serving cell is temporarily barred because of an authentication failure. The MS detects a downlink signaling failure. The occurrence of a downlink signaling failure is controlled by the downlink signaling failure counter. When the MS selects a cell, the counter is initialized to the integer nearest to 90 divided by CCCH Blocks Reserved for AGCH. The counter is increased by one each time the MS successfully decodes a message on its paging subchannel. This counter is decreased by four each time the MS fails to decode a message on its paging subchannel. When the counter becomes zero, it indicates that a downlink signaling failure occurs.
NOTE
l l
For details about the paging subchannel, see 2.49.3.7.2 CCCH Configuration and Paging Group Calculation.
l l
The C1 value of the serving cell is less than 0 for five consecutive seconds. The number of random access attempts exceeds MS MAX Retrans.
?.3. Cell Reselection Algorithms

When the cell reselection conditions are met, the MS selects one neighboring cell as the serving cell. Cell reselection adopts the C2 algorithm. C2 is calculated as follows: l If CELL_RESELECT_PENALTY_TIME is not equal to 31, C2 = C1 + CELL_RESELECT_OFFSET CELL_RESELECT_TEMPORARY_OFFSET x H(CELL_RESELECT_PENALTY_TIME T) l If CELL_RESELECT_PENALTY_TIME is equal to 31, C2 = C1 - CELL_RESELECT_OFFSET The function H(x) is defined as follows: l l If X > 0, H(x) = 0. If X 0, H(x) = 1.
The parameters in the formula are described as follows: l CELL_RESELECT_PENALTY_TIME indicates Cell reselect penalty time. In scenarios such as areas along highways, Cell reselect penalty time must be properly set to avoid frequent cell reselections. l T is a timer and its initial value is 0. When a cell is recorded as one of the six strongest neighboring cells, timer T of the cell is started. When the cell is removed from the list of the six strongest neighboring cells, timer T is reset. l CELL_RESELECT_OFFSET indicates Cell reselect offset. The C2 value can be manually adjusted by setting Cell reselect offset.
CELL_RESELECT_TEMPORARY_OFFSET indicates Cell reselect temporary offset. During the period between the time when timer T is started and the time when the value of timer T reaches Cell reselect penalty time, a negative correction value is applied to C2 based on Cell reselect temporary offset. This prevents a fast moving MS from selecting a micro cell or a small-coverage cell as the serving cell. If Cell reselect penalty time elapses, Cell reselect temporary offset is no longer considered.
NOTE
The preceding three parameters of the C2 algorithm take effect only when Cell Reselect Parameters Indication is set to YES. Otherwise, the values of these parameters are regarded as zero. Then, C2 is equal to C1.
The MS selects a cell to camp on according to the cell reselection priority and C2. The selected cell becomes the serving cell. As shown in Figure 2-159, if the two cells have the same cell reselection priority and the reselection hysteresis and the reselection time meet the specified requirements, the MS selects Cell2, the one with greater C2, as the serving cell. Figure 2-159 Cell reselection
For details about the cell reselection priority, see Table 2-126.
2.49.3.5 Location Area Update

?.1. Overview
When an MS moves from one location area to another, it must register the new location information on the network. That is, when the MS finds that the LAI stored in the SIM is different from the LAI of the serving cell, it must notify the network to update the stored location area information about the MS. This procedure is called location area update.
NOTE
An LAI consists of mobile country code (MCC), mobile network code (MNC), and location area code (LAC). l MCC is specified by the MCC parameter. l MNC is specified by the MNC parameter. l LAC is specified by the Cell LAC parameter.
If cell reselection occurs when an MS in idle mode moves in the same location area, the MS does not notify the network of the cell change. If the two cells before and after cell reselection belong to different location areas, the MS needs to notify the network of the cell change, and this is called "forced registration" in mobile communication.
According to the identifier of location area update, location area updates are classified into three types: normal location area update, IMSI attach/detach, and periodic location area update. The location area update procedures for normal location area update, periodic location area update, and IMSI attach are basically the same, as shown in Figure 2-160. Figure 2-160 Location area update
NOTE
In an immediate assignment procedure, the MS sends the BTS a Channel Request message through the RACH, indicating the access cause "location update".
1.
When the MS initiates a location area update request, an immediate assignment procedure is started. The BTS sends the BSC an Establish Indication message, which contains the content of the Location Updating Request message. The BSC establishes an SCCP link over the A interface. Then, the BSC sends the MSC a Complete Layer3 Information message, which contains the cell global identity (CGI) of the current cell. The MSC responds to the BSC with a Connection Confirm message. The MSC sends the MS a Location Updating Accepted message, indicating that the location area update is successful. If the network rejects the location area update request, it sends a Location Updating Rejected message to the MS. If the TMSI allocation in the case of location area update is enabled on the MSC side, a TMSI Reallocation Complete message is sent to the MSC in the location area update procedure.
2.
3. 4. 5. 6.
Issue 08 (2011-09-30)
7.
The MSC sends the BSC a Clear Command message to start the resource release procedure on the network side.
?.2. Location Area

To determine the location of an MS, the coverage area of each GSM PLMN is divided into multiple location areas. Each location area contains one or more cells. The network stores the location area information about each MS for paging. After receiving an incoming call, the network pages the MS in the corresponding location area instead of in all the cells controlled by the MSC. Each location area is identified by a location area identity (LAI), which is broadcast through the system information over the BCH. The sizes of location areas are key factors that determine the system performance. Location areas have to be properly divided during network planning. l l If the size of a location area is too small, more location area updates will take place. This increases the signaling load. If the size of a location area is too large, a paging message will be sent in all the cells under the location area when the network pages an MS. This increases the load on the PCH and the signaling load on the Abis interface.
Therefore, the planning of location areas is an important task. During division of location areas, ensure that location area updates are reduced to a smallest possible number without causing heavy paging load. This is to prevent a wastage of network resources.
?.3. Normal Location Area Update

When an MS moves from one location area to another, it initiates a normal location area update. A normal location area update is used to update the location information registered on the network by the MS. The Location Update Type information element in the Location Update Request message should indicate that it is a normal location area update.
?.4. IMSI Attach/Detach

The IMSI attach/detach procedure informs the MSC/VLR whether the MS can be reached. The Attach-detach allowed parameter controls whether the network needs to be notified of IMSI attach/detach. l If Attach-detach allowed is set to YES, the MS sends a Location Updating Request (IMSI Attach) message to the network when it is switched on, indicating that the MS is active. After receiving the message, the network updates the state of the MS so that the network can page the MS as required. If Attach-detach allowed is set to YES, the MS sends an IMSI Detach message to the network when it is switched off, indicating that the MS is inactive. After receiving this message, the network will not send paging messages to the MS, thus saving network resources.
?.5. Periodic Location Area Update

When any of the following conditions occurs, the MS loses contact with the network. If the MS is paged in this case, the network sends a paging message to the location area registered by the MS. The paging expires definitely and the system resource is used ineffectively.
l l
When the MS is switched on and moves into a blind area, the network cannot know the current state of the MS but still considers that the MS is attached. When the MS sends an IMSI Detach message to the network, the network may not correctly decode the message due to poor uplink quality. As a result, the network still considers that the MS is attached. When the MS is down accidentally, it loses contact with the network.
To solve these problems, the GSM system implements a certain mechanism, which instructs the MS to automatically report its location information to the network at regular intervals. The mechanism is called periodic location area update. By adopting this mechanism, the network can know in time whether the status of the MS has changed. Periodic location area update is used to periodically notify the network of the MS availability. When the MS sends a Location Update Request message to the network, the Location Update Type information element in the message indicates that it is a periodic location update. The network sends the periodic location update timer value to all the MSs in the cell through the system information over the BCCH. The value is specified by T3212. When this timer expires, the MS automatically sends a location area update request to the network. After the MS performs a cell selection or reselection, it reads T3212 from the system information of the serving cell, starts this timer, and stores the timer on the SIM. When the MS detects that T3212 expires, it automatically sends a location area update request to the network. The signaling procedure of a periodic location area update is the same as the signaling procedure of a normal location area update.
2.49.3.6 Control Channels

The control channels for the MS in idle mode include broadcast channels and Common Control Channels (CCCHs).
NOTE
The Dedicated Control Channels (DCCHs) are used for the MS in dedicated mode and are not described in this document.
Broadcast Channels
Broadcast channels, including Frequency Correction Channel (FCCH), Synchronization Channel (SCH), Broadcast Control Channel (BCCH), and Cell Broadcast Channel (CBCH), are all downlink channels used for sending broadcast messages to the MS. l FCCH The network sends frequency correction signals over the FCCH to the MS. The FCCH enables the MS to synchronize its frequency (with a specified frequency). l SCH The network sends the frame synchronization number and base station identity code over the SCH to the MS. l l BCCH The network sends the common messages related to all its cells over the BCCH to the MS. CBCH The network broadcasts services over the CBCH within a cell. The physical channels used by the CBCH are the same as those used by the SDCCH.
CCCHs
The CCCHs include Paging Channel (PCH), Random Access Channel (RACH), Access Grant Channel (AGCH), and Notification Channel (NCH). l PCH The PCH is a downlink channel. The MS monitors the PCH at certain intervals to determine whether it can receive a call from the MSC. l RACH The RACH is an uplink channel. The MS accesses the network through the RACH and requests the network to assign an SDCCH. l AGCH The AGCH is a downlink channel. The network notifies the MS of the assigned dedicated channel (SDCCH or TCH) through the AGCH. l NCH The NCH is a downlink channel, which is used to notify the MS of Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS) calls.
2.49.3.7 Paging
?.1. Overview
Through the paging process, an MS is instructed to access the network to complete call connection. Different paging algorithms have different paging efficiencies. Huawei GBSS paging algorithm has the following benefits: l Paging capability is one of the criteria that measure the system performance. Huawei GBSS paging algorithm maximizes the paging capability of the system, while maintaining paging efficiency and minimizing paging load. Through reliable paging, Huawei GBSS paging algorithm enables MSs to receive every possible call. This reduces customer complaints and improves customer satisfaction.
?.2. CCCH Configuration and Paging Group Calculation

In the GSM system, the MS reads the information on the CCCH of the serving cell at least once in every 30s. In the downlink, the CCCHs include AGCH and PCH. One CCCH can be carried on one or more physical channels. In the case of high paging traffic in a location area, one physical timeslot for paging message transmission is insufficient. The GSM protocol allows multiple CCCHs to be configured on one TRX carrying the BCCH. The CCCHs can be configured only on timeslot 0, 2, 4, or 6. The number of CCCH message blocks in a cell reflects the resources that can be used by the AGCH or the PCH in the cell. Table 2-127 lists the mapping between the CCCH configuration and the number of CCCH message blocks in a BCCH multiframe.
Issue 08 (2011-09-30)
776
Table 2-127 Mapping between the CCCH configuration and the number of CCCH message blocks in a BCCH multiframe CCCH Configuration The CCCH uses one physical channel exclusively. It does not share this physical channel with the SDCCH. The CCCH uses one physical channel. It shares this physical channel with the SDCCH. The CCCH uses two physical channels exclusively. It does not share these physical channels with the SDCCH. The CCCH uses three physical channels exclusively. It does not share these physical channels with the SDCCH. The CCCH uses four physical channels exclusively. It does not share these physical channels with the SDCCH. Number of CCCH Message Blocks in a BCCH Multiframe 9
18
27
36
In different CCCH configurations, each BCCH multi-frame (containing 51 frames) includes different numbers of CCCH message blocks. The CCCH is shared by the AGCH and the PCH. When messages need to be transmitted on both the PCH and the AGCH, the network prefers the PCH. To prevent the occurrence of message congestion on the AGCH when the traffic on the PCH is high, the network reserves a certain number of message blocks for the AGCH. The BS_AG_BLKS_RES parameter specifies the number of message blocks reserved for messages on the AGCH of the CCCH in a BCCH multi-frame. Each MS (corresponding to an IMSI) belongs to a paging group. Each paging group corresponds to a paging subchannel in a cell. The MS determines its paging group based on its IMSI, and then determines the location of the paging subchannel of its paging group. In the actual network, the MS listens to only its paging subchannel but ignores other paging subchannels. When other paging subchannels are used, part of the MS is even powered off to save power overhead (which is the power supply to the DRX). The BS_PA_MFRMS parameter specifies the number of BCCH multi-frames that form a cycle for the paging subchannels. This parameter determines the number of paging subchannels into which paging channels in a cell are divided. The formula for calculating the number of paging groups is: l l When the CCCH and the SDCCH share one physical channel, the number of paging groups = (3 - BS_AG_BLKS_RES) x BS_PA_MFRAMS. When the CCCH and the SDCCH do not share one physical channel, the number of paging groups = (9 - BS_AG_BLKS_RES) x BS_PA_MFRAMS.
The formula for calculating the paging group mapped to the MS is:
Paging group number = ((IMSI mod 1000) mod (Number of cell paging groups)) div BS_PA_MFRMS
NOTE
For PS services, if the parameter Support SPLIT_PG_CYCLE on CCCH is enabled, the formula for calculating paging groups may be different.
The MS determines the mapped paging group based on the IMSI and the configuration of paging channels in the serving cell, and then determines the paging subchannel of the mapped paging group.
?.3. CS Paging
CS paging messages are transmitted on the PCH. When a call reaches the MSC of the called MS, the MSC determines the area where the MS is located and broadcasts paging messages to all the BSCs in this area. Based on the location area, the BSC determines the cells to which paging messages are sent and performs IMSI-based calculation of the paging group mapped to the MS. The MS in idle mode listens to its paging subchannels. If the IMSI or TMSI contained in the Paging Request message is consistent with its own IMSI or TMSI, the MS sends a Channel Request message to trigger an initial channel assignment procedure, and sends a Paging Response on the assigned channel.
NOTE
The MSC determines whether to use TMSI-based or IMSI-based paging. l If IMSI-based paging is used, the paging message contains the IMSI only. l If TMSI-based paging is used, the paging message contains both TMSI and IMSI. The IMSI is used by the BSC to calculate paging groups.
?.4. PS Paging
The PS paging procedure is similar to the CS paging procedure. During the PS paging procedure, the function of the SGSN is similar to that of the MSC. The paging strategy of the SGSN determines whether the P-TMSI or IMSI is used for paging. The SGSN initiates PS paging when transmitting downlink data to an MS. PS paging messages are carried on the PS paging channels (if configured) or on the PCHs if the PS paging channels are not configured. Only the MS in the STANDBY state can be paged. The SGSN obtains the Routing Area of the MS and sends a paging message to the entire Routing Area.
NOTE
The location information of the MS in the STANDBY state contains only the Routing Area information of the GPRS.
?.5. Paging Modes

Huawei GBSS supports the following standard paging modes: l Common paging mode The MS calculates the mapped paging group based on the IMSI and the configuration of paging channels in the serving cell, and then calculates the paging subchannel of the mapped paging group. Paging messages are sent on only this paging subchannel. l
Issue 08 (2011-09-30)
Complete paging mode

When an MS group is informed that it is in complete paging mode, paging messages of this group may be sent on any PCH of the same timeslot. When the PCH configuration dynamically changes, paging message loss can be avoided. l Spaced paging mode The BSS adds the paging messages of a group to another paging channel to avoid temporary overload. That is, the MS can receive paging messages on paging channel N+2 in spaced paging mode, whereas it receives paging messages on paging channel N in common paging mode.
?.6. Paging Functions

Huawei GBSS supports the paging queue, paging retransmission, paging combination, and paging flow control functions. These functions can effectively improve and guarantee the paging capacity of the BSC. l Paging queue The transmission of paging messages on the Um interface is limited by paging groups. The paging messages of a paging group can be transmitted only on the message blocks to which the paging group is mapped. The BTS implements the paging queue function to wait for opportunities for transmission by temporarily buffering the paging messages received from the BSC. The BTS selects a paging message and transmits it on the corresponding message block whenever an opportunity comes. Paging messages of the same priority follow the rule of "first come, first served (FCFS)". To guarantee the scheduling efficiency for paging messages on the Um interface, the BTS Paging Lifetime parameter specifies the life cycle of a paging queue in the BTS. The setting of this parameter must be consistent with the setting of the paging timer T3113 of the core network. It is recommended that the BTS Paging Lifetime parameter be set to a value that is 1s to 2s shorter than T3113. l Paging retransmission As the message on the downlink CCCH is transferred in unacknowledged mode on the LAPDm layer of the Um interface, there is a risk of message loss. Paging retransmission is used to reduce this risk. Generally, the MSC and BSS provide two levels of retransmission. One level is at the MSC, where paging messages are retransmitted in a long period to handle long interruptions. The other level is at the BTS, where paging messages are retransmitted in a short time and traffic flow on the Abis and A interfaces can be reduced. Huawei BSS supports the paging retransmission function. When the message block has neither paging messages nor immediate assignment messages to be transmitted, the paging messages that have been transmitted on this message block will be retransmitted. The maximum number of paging retransmissions of the same message is specified by the Paging Times parameter. Paging messages on the MSC side are retransmitted at a fixed interval and the paging retransmission is controlled by the parameters on the MSC side. The paging retransmission on the BTS side is implemented by the Paging Times parameter. Paging messages on the BTS side are not retransmitted at a fixed interval but scheduled in the paging queues for retransmission. The paging queues for retransmission have lower priority than normal paging queues. Maximum number of paging message transmissions on the Um interface = Number of pagings configured on the MSC side x Paging Times configured on the BTS side. l Paging combination Paging combination is used to improve the utilization of the Um interface. The Paging Command message sent from the BSC to the BTS contains the information of an MS. The
BTS tries to combine all the Paging Command messages of the MSs belonging to the same paging group, and sends with the Paging Request messages to the MSs. One Paging Request message contains the TMSIs or IMSIs of multiple MSs. One TMSI consists of 3 digits, and one IMSI consists of 15 digits. The length of the Paging Request message is limited. The combination capability depends on whether the combined paging commands use the IMSIbased or TMSI-based paging. The MS determines whether to respond to the paging request by resolving the Mobile Identity field (including the TMSI or IMSI) in the Paging Request message. The protocols specify three paging request types. Their combination modes are as follows: Paging request type 1 One Paging Request message combines one to two Paging Command messages. IMSI IMSI+IMSI IMSI+TMSI/P TMSI/P TMSI/P+TMSI/P Paging request type 2 One Paging Request message combines two to three Paging Command messages. TMSI/P+TMSI/P TMSI/P+TMSI/P+IMSI TMSI/P+TMSI/P+TMSI/P Paging request type 3 One Paging Request message combines four Paging Command messages. TMSI/P+TMSI/P+TMSI/P+TMSI/P The efficiency of paging combination depends on whether TMSI-based or IMSI-based paging is used. l Paging flow control When the paging flow sent by the MSC exceeds the processing capability of the BSS, the BSS controls the flow according to the current network status. The paging flow control function ensures the robustness and normal working of the BSS, the high capability of the BSS to process paging messages, and the smoothness and stability of services. For details about paging flow control, see the 2.37 Flow Control.
2.49.3.8 System Information

?.1. Overview
System information involves main radio network parameters on the Um interface, including network identity parameters, cell selection parameters, system control parameters, and network function parameters. Based on the received system information, an MS can properly select and access a radio network. Then, it can gain access to all types of service provided by the network. System information is classified into the following types: l
Issue 08 (2011-09-30)
Broadcast system information

For an MS in idle mode, the network provides broadcast system information, indicating the location of the MS and the types of service the MS can obtain. Some parameters involved in the broadcast system information control cell reselection of the MS. l Dedicated system information For an MS in dedicated mode, the network provides dedicated system information, part of which controls transmission, power, and handover of the MS. Broadcast system information and dedicated system information are closely associated. The contents of broadcast system information can be the same as those of dedicated system information, whereas the contents of dedicated system information can be different from those of broadcast system information. The reason is that dedicated system information is intended for one MS, but broadcast system information is intended for all MSs in idle mode in a certain cell. BSS system information consists of System Information Types 1, 2, 2BIS, 2TER, 2QUATER, 3, 4, 5, 5BIS, 5TER, 6, 7, 8, 10, and 13.
NOTE
System Information Types 5, 5BIS, 5TER, and 6 are used for only the MSs in dedicated mode. System Information Type 13 contains parameters related to GPRS services. When the cell supports GPRS services, System Information Type 13 is sent on the BCCH.
?.2. System Information Type 1
Functions
System Information Type 1 is sent on the BCCH to provide information about control of the RACH and of the cell allocation (CA).
Contents
Table 2-128 lists the contents of System Information Type 1. Table 2-128 Contents of System Information Type 1 Type SYS INFO 1 Content Cell Channel Desc RACH Control Para SI 1 Rest Octets
The contents of System Information Type 1 are described as follows: l CA list One cell can be configured with a maximum of 64 frequencies. The actual configuration of cell frequencies is subject to the Cell Channel Description, as listed in Table 2-129. The BSC selects a format of cell channel description based on the actual configuration of cell frequencies. The format of cell channel description is defined by octet 2, Format ID (Bit 128, Bit 127, Bit 124, Bit 123, and Bit 122), as listed in Table 2-130.
Table 2-129 Format of cell channel description 8 7 6 5 4 3 2 1 octet 1 Bit 122 Bit 114 Bit 2 Bit 121 Bit 113 Bit 1 octet 2
Cell Channel Description IEI Bit 128 Bit 120 Bit 8 Bit 127 Bit 119 Bit 7 0 Spar e Bit 118 Bit 6 0 Spare Bit 117 Bit 5 Bit 124 Bit 116 Bit 4 Bit 123 Bit 115 Bit 3
octet 3 octet 17
Table 2-130 Format of cell channel description Bit128 0 1 1 1 1 1 Bit127 0 0 0 0 0 0 Bit124 X 0 1 1 1 1 Bit123 X X 0 0 1 1 Bit122 X X 0 1 0 1 Format Notation bit map 0 1024 range 512 range 256 range 128 range variable bit map
Different formats of cell channel description correspond to different numbers of available cell frequencies. Assume that the number of available frequencies for a cell is n (except for duplicate and invalid frequencies) and ARFCN(i) (i=1,,n) represents the Absolute Radio Frequency Channel Number. Then, the numbers of available frequencies for different formats of cell channel description are as follows: Bit map 0 The bit map 0 format is used for GSM900 frequencies. The number of available frequencies is 64 if 1 ARFCN(i) 124. 1024 range If the 1024 range format is used, the number of available frequencies for a cell is equal to or smaller than 16. For a GSM900 cell, 1 ARFCN(i) 124. For a GSM1800 cell, 512 ARFCN(i) 885. 512 range
If the 512 range format is used, the number of available frequencies for a cell is equal to or smaller than 18. The interval between any two ARFCNs must be less than 512. 256 range If the 256 range format is used, the number of available frequencies for a cell is equal to or smaller than 22. The interval between any two ARFCNs must be less than 256. For example, in the 256 range format, ARFCNs 512 and 812 cannot be configured simultaneously. 128 range If the 128 range format is used, the number of available frequencies for a cell is equal to or smaller than 29. The interval between any two ARFCNs must be less than 128. For example, in the 128 range format, ARFCNs 512 and 712 cannot be configured simultaneously. Variable bit map If the variable bit map format is used, the number of available frequencies for a cell is equal to or smaller than 64. The interval between any two ARFCNs must range from 1 to 111. For example, in the variable bit map format, it is allowed to configure 64 frequencies with the ARFCNs 512 to 575 with an increment of 1, but it is not allowed to configure 64 frequencies with the ARFCNs 512 to 638 with an increment of 2.
NOTE
The previously mentioned restrictions are mainly applied to GSM1800 frequencies.
RACH Control Para The RACH Control Para information element contains the following parameters: MS MAX Retrans Tx-integer Cell Access Bar Switch Common Access Control Class and Special Access Control Class The access control class is categorized into classes 0-9 and 11-15. Generally, each GSM MS has an access class, represented by a bit. If this bit is set to 1, MSs of the corresponding class are barred from accessing the current cell. Otherwise, they are allowed to access the cell. Call Reestablishment Forbidden Emergent Call Disable
NOTE
The time interval between two consecutive Channel Request messages sent by an MS is indicated by a random value from {S, S+1,....S+T-1}. The unit of the time interval is TDMA frame. Here, S is subject to the common control channel configuration, which is delivered in System Information Type 3; T is Tx-integer. Table 2-131 lists the relation between S and T. Table 2-131 Relation between S and T Tx-integer 3, 8, 14, 50 4, 9, 16 Non Combined CCCH 55 76 Combined CCCH 41 52
Issue 08 (2011-09-30)
783

Non Combined CCCH 109 163 217
Tx-integer 5, 10, 20 6, 11, 25 7, 12, 32
Combined CCCH 58 86 115
If satellite transmission is used, it is recommended that MS MAX Retrans be set to 4 and TXinteger be set to 32 to reduce the delay caused by satellite transmission.
SI 1 Rest Octets The SI 1 Rest Octets information element has eight bits. It contains spare bits and indication of the PCS1900 and DCS1800.
?.3. System Information Types 2, 2BIS, 2TER, and 2QUATER
Functions
The functions of System Information Types 2, 2BIS, 2TER, and 2QUATER are as follows: l System Information Type 2 is sent on the BCCH to provide information about the RACH control, the NCC Permitted, and the BCCH allocation list (BA1 list) in neighboring cells. Generally, System Information Types 2, 2BIS, and 2TER describe different parts of the BA1 list. The MS reads and decodes the BA1 list and then performs cell reselection in idle mode. A phase 1 MS in GSM900 recognizes only the neighboring cell frequencies described in System Information Type 2 and ignores those described in System Information Types 2BIS and 2TER. l System Information Type 2BIS is sent on the BCCH to provide information about the RACH control and the extension of the BCCH allocation list in the neighboring cells (part of the BA1 list). System Information Type 2BIS is optional. Generally, System Information Type 2 carries the information about a limited number of frequencies that are included in the BA1 list. In this situation, System Information Type 2BIS carries the information about other frequencies that are included in the BA1 list and are on the same frequency band as the frequencies carried by System Information Type 2. System Information Type 2TER is sent on the BCCH to provide information about the extension of BCCH allocation list in neighboring cells (part of the BA1 list). System Information Type 2TER carries the information about the frequencies that are on different bands from the frequencies of the current cell. Only the dual-band MSs read System Information Type 2TER. The GSM900 MSs and the GSM1800 MSs ignore this message. System Information Type 2QUATER provides information about the BCCH allocation in neighboring 3G cells. It is used for the reselection of 3G cells. System Information Type 2QUATER is sent when inter-RAT handover is required and neighboring 3G cells are configured.
In a dual-band network, the Send System Information 2ter parameter specifies whether to send System Information Type 2TER. In a non-dual-band network, the SI 2ter Switch parameter specifies whether to send System Information Type 2TER. The Support Sent 2QUATER parameter specifies whether to send System Information Type 2QUATER.
Contents
Table 2-132 lists the contents of System Information Types 2, 2BIS, 2TER, and 2QUATER. Table 2-132 Contents of System Information Types 2, 2BIS, 2TER, and 2QUATER Type SYS INFO 2 Content Neighbor Cell Desc NCC permitted RACH Control Para SYS INFO 2 BIS Neighbor Cell Desc RACH Control Para SYS INFO 2TER SYS INFO 2QUATER Neighbor Cell Desc. (Extended) SI 2quater Rest Octets
The contents of System Information Types 2, 2BIS, 2TER, and 2QUATER are described as follows: l Neighbor Cell Desc (BA1 list) The Neighbor Cell Description information element provides the ARFCNs of the BCCH carriers in the neighboring cells of the current cell. Currently, Huawei BSS supports a maximum of 32 neighboring cells per cell. Except for bit 5 (BA-IND) and bit 6 (EXT-IND) of octet 2, the Neighbor Cell Description information element is coded in the same way as the Cell Channel Description information element. For details, see the cell channel description in 2.49.3.8.2 System Information Type 1. The extension indication (EXT_IND) is sent in System Information Types 2 and 5. It indicates whether extended neighboring cell frequencies are sent in System Information Types 2BIS and 5BIS. It has one bit. If the EXT_IND bit is set to 0, System Information Types 2 and 5 carry the complete BA list. If the EXT_IND bit is set to 1, System Information Types 2 and 5 carry only part of the BA list. The BA indication (BA_IND) is sent in System Information Types 2 and 5. It has one bit and is used by the MS to discriminate changes in the BA1 or BA2 list. In other words, if the neighboring cell relation and the BA2 list are modified during the conversation, the BA_IND bit in System Information Type 5 should be 1, indicating that the MS needs to decode the neighboring cell frequencies again. l NCC Permitted The NCC Permitted parameter is sent in System Information Types 2 and 6. It has eight bits and provides all the NCCs required by MSs. In other words, if bit N is 0 (0 N 7), the MS does not measure the power level of the cell where the NCC is N, indicating that the MS is not reselected or handed over to the network where the NCC is N. This parameter is mainly used for handover and cell reselection. l RACH Control Para For details about the RACH Control Para information element, see 2.49.3.8.2 System Information Type 1.
Neighbor Cell Desc. (Extended) The Neighbor Cell Desc. (Extended) information element is sent in System Information Types 2TER and 5TER. Except for bit 5 (BA-IND) and bits 6 and 7 (Multiband_Reporting) of octet 2, this information element is coded in the same way as the Cell Channel Description information element. For details, see 2.49.3.8.2 System Information Type 1.
Multiband_Reporting The Multiband_Reporting parameter is sent in System Information Types 2TER and 5TER. It has two bits and is used to request the dual-band MS to report information about neighboring cells of multiple bands. For details, see Table 2-133. Table 2-133 Multiband reporting Multiband Reporting (Two Bits) 0 Meaning The MS reports the measurement results of the top six neighboring cells where the signal strength is the strongest, irrespective of the band used. If there is a neighboring cell that is on a different band from the serving cell and if the MS is allowed to camp on the neighboring cell, the MS reports the measurement results of the neighboring cell. At the other five positions, it reports the measurement results of the neighboring cells that are on the same band as the serving cell. If there are two neighboring cells that are on a different band from the serving cell and if the MS is allowed to camp on the neighboring cells, the MS reports the measurement results of the two neighboring cells. At the other four positions, it reports the measurement results of the neighboring cells that are on the same band as the serving cell. If there are three neighboring cells that are on a different band from the serving cell and if the MS is allowed to camp on the neighboring cells, the MS reports the measurement results of the three neighboring cells. At the other three positions, it reports the measurement results of the neighboring cells that are on the same band as the serving cell.
10
11
SI 2quater Rest Octets The SI 2quater Rest Octets information element contains the following parameters: BA_IND 3G_BA_IND MP_CHANGE_MARK 3G Neighbour Cell Description Index_Start_3G
Issue 08 (2011-09-30)
786
UTRAN FDD DESCRIPTION UTRAN TDD DESCRIPTION 3G MEASUREMENT PARAMETERS Description These parameters belong to the parameters related to external 3G cells.
Functions
System Information Type 3 is sent on the BCCH to provide information about the location area identification, cell identity, RACH control, and parameters related to cell selection. The information is mandatory.
Contents
Table 2-134 lists the contents of System Information Type 3. Table 2-134 Contents of System Information Type 3 Type SYS INFO 3 Content Cell Identity LAI Cell Option (BCCH) Cell Selection Para RACH Control Para SI 3 Rest Octets
The contents of System Information Type 3 are described as follows: l CGI The Cell Global Identity (CGI) consists of the Location Area Identity (LAI) and the Cell CI. The LAI consists of the MCC, MNC, and Cell LAC. System Information Types 3, 4, and 6 contain all or part of the CGI. Upon receiving the system information, the MS decodes the CGI. Based on the MCC and the MNC, the MS determines whether to access the network through this cell and whether the current location area has changed. If the location area has changed, the MS initiates a location area update procedure. l Control Channel Desc The Control Channel Desc information element contains the following parameters: MSC Version Indication The MSC Version Indication parameter indicates when the MSC was released. This parameter has one bit. If the bit is set to 0, the MSC was released in 1998 or earlier. If the bit is set to 1, the MSC was released in 1999 or later. Attach-detach allowed
CCCH-CONF The CCCH-CONF parameter determines the combination mode of the CCCH. The CCCH-CONF has three bits. Table 2-135 describes the meaning of the CCCH-CONF. Table 2-135 Meaning of the CCCH-CONF CCCH-CONF (Three Bits) Number of CCCH Message Blocks in One BCCH Multiframe 9 3 18 27 36 Meaning
000 001 010 100 110 Others
One physical channel used for CCCH, not shared with SDCCHs One physical channel used for CCCH, shared with SDCCHs Two physical channels used for CCCH, not shared with SDCCHs Three physical channels used for CCCH, not shared with SDCCHs Four physical channels used for CCCH, not shared with SDCCHs Reserved
CCCH Blocks Reserved for AGCH Multi-Frames in a Cycle on the Paging CH T3212 l Cell Option (BCCH) The Cell Option (BCCH) information element contains the following parameters: PWRC FR Uplink DTX Radio Link Timeout l Cell Selection Para The Cell Selection Para information element affects the behaviors of an MS after the MS is switched on. It contains the following parameters: Cell Reselect Hysteresis Parameters MS_TXPWR_MAX_CCH RXLEV_ACCESS_MIN Additional reselect parameter indication The Additional reselect parameter indication indicates whether the MS uses C2 during cell reselection. It has one bit. In System Information Type 3, this parameter is meaningless. In System Information Type 4, value 0 of the bit indicates that the SI4 Rest Oct of System Information Type 4 is used to calculate the parameters related to C2; value 1 indicates that the SI4 Rest Oct of System Information Types 7 and 8 are used to calculate the parameters related to C2.
Support Half Rate l l RACH Control Para For details, see 2.49.3.8.2 System Information Type 1. SI 3 Rest Octets The SI 3 Rest Octets information element contains the following parameters: Cell Reselect Parameters Indication Cell bar qualify Cell reselect offset Cell reselect temporary offset Cell reselect penalty time Send System Information 2ter ECSC Support GPRS Support Sent 2QUATER
Functions
System Information Type 4 is sent on the BCCH to provide information about the location area identification, RACH control, cell selection parameters, and CBCH. l l Information about the location area identification, RACH control, cell selection parameters is mandatory. Information about CBCH is optional. It contains the configurations of the CBCH and the related frequency information. It is used when the system supports cell broadcast.
Contents
Table 2-136 lists the contents of System Information Type 4. Table 2-136 Contents of System Information Type 4 Type SYS INFO 4 Content LAI Cell Selection Para RACH Control Para CBCH Channel Desc. (option) CBCH Mobile Allocation (option) SI 4 Rest Octets
The contents of System Information Type 4 are described as follows:

l l l l
Location Area Identification (LAI) For details, see 2.49.3.8.4 System Information Type 3. Cell Selection Para. For details, see 2.49.3.8.4 System Information Type 3. RACH Control Para. For details, see 2.49.3.8.2 System Information Type 1. CBCH Channel Description and CBCH Mobile Allocation (CBCH MA) Both CBCH Channel Description and CBCH MA are optional. If the system supports cell broadcast, CBCH Channel Description indicates the configuration of the CBCH. If the CBCH is in frequency hopping mode, CBCH MA is mandatory.
SI 4 Rest Octets If the cell selection parameter Additional reselect parameter indication is set to No, the SI 4 Rest Octets is used to calculate the value of the cell reselection parameter C2. The SI 4 Rest Octets information element contains the following parameters: Cell Reselect Parameters Indication Cell bar qualify Cell reselect offset Cell reselect temporary offset Cell reselect penalty time
Functions
System Information Type 7 is sent on the BCCH to provide information about cell reselection.
Contents
Table 2-137 lists the contents of System Information Type 7. Table 2-137 Contents of System Information Type 7 Type SYS INFO 7 Content SI 7 Rest Octets
The contents of System Information Type 7 are described as follows: l l SI 7 Rest Octets contains the cell selection and reselection parameters used by the MS. It may also contain the Power Deviation parameter used by the DCS1800 Class 3 MS. The coding scheme of SI 7 Rest Octets is the same as that of SI 4 Rest Octets. For details, see 2.49.3.8.5 System Information Type 4.

This section describes the functions and contents of System Information Type 8.
Functions
System Information Type 8 is mandatory and is sent on the BCCH. It provides information about cell reselection.
Contents
The contents of System Information Type 8 are described as follows: l l SI 8 Rest Octets contains the cell reselection parameters used by the MS. It may also contain the Power Deviation parameter used by the DCS1800 Class 3 MS. The coding scheme of SI 8 Rest Octets is the same as that of SI 4 Rest Octets. For details, see 2.49.3.8.5 System Information Type 4.
Functions
System Information Type 13 provides information about the parameters related to GPRS services. It is sent on the BCCH when GPRS services are supported.
Contents
The SI 13 Rest Octets information element contains the following parameters: l l l l l

Issue 08 (2011-09-30)
RAC RAC contains Routing Area and Routing Area Color Code. Support SPLIT_PG_CYCLE on CCCH Packet Access Priority Network Control Mode PSI1 Repetition Period
In addition, System Information Type 13 also contains parameters such as GPRS Mobile Allocation, GPRS Cell Options, GPRS Power Control Parameters struct, and PBCCH Description struct.
2.49.3.9 Short Message Service Cell Broadcast

The short message service cell broadcast (SMSCB) is a teleservice (TS23) that periodically broadcasts messages to all the MSs in a specified area. Based on different settings, the MS can continuously or discontinuously receive short messages, such as weather forecast and traffic information. The SMSCB allows all the MSs in a specified area to receive short messages. The area may cover one or more cells, or even the entire PLMN. The Cell Broadcast Database (CDB) of the BSC manages and schedules the short messages from the cell broadcast center (CBC). Then, the BSC sends the short messages to the BTS. After that, the BTS broadcasts the messages to all the MSs in a specified area at certain intervals. The CDB receives and stores the short messages, schedules and sends the messages according to a certain algorithm, and responds to the query from the CBC. The MS can receive the messages in DRX mode. That is, the MS can work discontinuously. Through a scheduling message, the BSC notifies the MS that no short message is sent during a particular period. Therefore, the MS needs to receive short messages only in the specified period, thus reducing the power consumption. The SMSCB supports the BTS flow control. That is, the order in which the short messages are sent is scheduled by the CDB, but the messages are actually sent by the BTS. Each TRX of the BTS maintains one message buffer and periodically sends cell broadcast short messages on a specified channel. When the messages are not sent in time, the BTS reports the out-ofsynchronization situation to the BSC through a LOAD IND message. By controlling the BTS flow, the CDB maintains the balance of the cell broadcast system, thus meeting the requirements for sending messages. Huawei BSS also supports simplified cell broadcast. Without a CBC, Huawei simplified cell broadcast feature supports the most commonly used standard cell broadcast services with low equipment costs and low OM costs, thus reducing the operator's CAPEX. For details about the SMSCB, see 2.22 Cell Broadcast.
2.49.3.10 Public Voice Group Call Service

?.1. Overview
The public voice group call service (VGCS) simultaneously provides voice services for a group of MSs in a pre-defined area in half-duplex mode. This area is called the group call area. The network side defines the group call number, group members, and coverage area. The MS who has the permission can dial the group call number to originate a group call. All the group members within the coverage area can be informed to join the group call. During the group call, every relevant cell has a group call channel, in which only the current speaker uses the uplink (group transmission mode) and all the listeners wait in the downlink (group reception mode). One of the group members can press and hold the PTT key on the mobile phone to speak to others. During this period, other members can only listen but cannot talk by pressing PTT. Other group members can speak by pressing PTT only after the speaker releases PTT. When the conversation is complete, the group call originator terminates the call by pressing the on-hook key and then all the group members hang up.
In addition, the VGCS provides dispatcher service. The dispatcher is a special user of the fixed network or the mobile network defined by the network side. The dispatcher has the permission to talk at any time during a group call and originates or terminates a group call authorized by the network side.
NOTE
A VGCS channel is similar to a TCH. When a VGCS or VBS call is established, each cell in the group call area is assigned an A-interface circuit and a radio channel. In the group call area, the listening subscribers of the same VGCS call share the downlink of the channel. The VGCS subscribers preempt the uplink of the channel at different time points. This channel is called the group call channel.
?.2. System Information

The system information related to a group call is classified into System Information Types 1, 6, and 10.
System Information Type 1

When a group call is established, the BSS broadcasts a Notification Command message on the NCH. The NCH is part of the CCCH. System Information Type 1 describes the position of NCH on the CCCH and contains the NCH Occupy Block Number and NCH Start Block parameters. The sum of NCH Occupy Block Number and NCH Start Block must be smaller than or equal to the value of CCCH Blocks Reserved for AGCH. If NCH Occupy Block Number is set to 0, it indicates that the current cell does not support VGCS or VBS. In this case, System Information Type 1 does not provide information about the number of blocks occupied by the NCH or the start block.

If a cell supports VGCS or VBS, the BSC needs to provide the NCH notification list of the current cell, the status of the list, whether the PCH has been adjusted, and some information about VGCS or VBS. If a cell supports Reduced NCH monitoring, an MS determines whether to listen to the NCH according to the Notification List Number (NLN) and the change in the list status. The MS need not listen to the NCH all the time, thus achieving the purpose of power saving.
NOTE
System Information Type 6 is used in dedicated mode only.

System Information Type 10 is used to improve the cell reselection performance of an MS in group reception mode. Through System Information Type 10, only the information about neighboring cells in the same group call area is sent to MSs so that the MSs in group reception mode do not reselect the cell out of the group call area. Thus, call disconnections are minimized. The cell list of a group call area is configured on the MSC side. Different group calls may have different cell lists. The cell list of a group call area is not configured on the BSC side. System Information Type 10 ensures that an MS reselects a cell within the group call area only. This improves the cell reselection performance of the MS. Therefore, when establishing a group call, the BSC indirectly constructs a cell list of the current group call according to the VGCS/VBS Assignment Request message from the MSC. Then, the BSC regards the intersection of the cell list of the current group call and the neighboring cell list of the current cell as the neighboring cell list of the current group call in the current cell. Through System Information Type 10, the
BSC sends the MS the neighboring cell information of the current group call in the current cell. This information is intended as a reference for the MS to perform cell reselection. One cell may belong to different group call areas and two or more group calls may be established in one cell. System Information Type 10 provides the MS in group reception mode with cell reselection information. Therefore, System Information Type 10 can be sent on only the corresponding SACCH of the NCH. The system information contains only the information about the neighboring cells that belong to the same group call area as the current cell.
2.49.4 Parameters
This chapter describes the parameters related to idle mode behaviour. For the meaning of each parameter, seeTable 2-140. For the default value, value ranges, and MML commands of each parameter, see Table 2-141. Table 2-140 Parameter description (1) Parameter Description Minimum received signal level of the MS. This level is reported in the system information. This parameter specifies the minimum receive level of an MS to access the BSS. For details. see GSM Rec. 05.08. The value of this parameter ranges from 0 to 63 (corresponding to -110 dBm to -47 dBm). Maximum transmit power level of MSs. As one of the cell reselection parameters in system message 3, this parameter is used to control the transmit power of MSs. For details, see GSM Rec. 05.05. In a GSM900 cell, the maximum power control level of an MS ranges from 0 to 19, corresponding respectively to the following values (unit: dBm): 43, 41, 39, 37, 35, 33, 31, 29, 27, 25, 23, 21, 19, 17, 15, 13, 11, 9, 7, and 5.Generally, the maximum transmit power supported by an MS is level 5 (corresponding to 33 dBm). The minimum transmit power supported by an MS is level 19 (corresponding to 5 dBm). Other transmit power levels are reserved for high-power MSs. In a GSM1800 or GSM1900 cell, the maximum power control level of an MS ranges from 0 to 31, corresponding respectively to the following values (unit: dBm): 30, 28, 26, 24, 22, 20, 18, 16, 14, 12, 10, 8, 6, 4, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 36, 34, and 32. Generally, the maximum transmit power supported by an MS is level 0 (corresponding to 30 dBm). The minimum transmit power supported by an MS is level 15 (corresponding to 0 dBm). Other transmit power levels are reserved for high-power MSs. If a class 3 MS on the DCS1800 band does not receive the original power command after random access, the power that the MS uses is the MS maximum transmit power level plus the power calculated from the power deviation. For details, see GSM Rec. 05.08. The MS does not receive the original power command after random access. This parameter indicates whether the power deviation is added to the class 3 MS on the DCS1800 band on the basis of the maximum MS transmit power.
Minum Access RXLEV
MS_TXPWR_M AX_CCH
Power Deviation
Power Deviation Indication
Issue 08 (2011-09-30)
794
Parameter
Description Used together with "Cell Bar Access" to decide the priority status of a cell. See GSM Rec. 0408. This parameter does not affect cell reselection but cell selection only. Whether the cell can be added to the reselected candidate cell list. If this parameter is set to "NoPermit", the cell cannot be reselected as the candidate cell for handover. If this parameter is set to "Permit", the cell can be reselected as the candidate cell for handover. Cell reselection hysteresis. This is one of the parameters used for deciding whether to reselect cells in different location areas. This parameter can avoid the increase of network signaling traffic due to frequent location update and reduce the risk of losing paging messages. BS-AG-BLKS-RES, indicating the number of the CCCH message blocks reserved for the AGCH. After the CCCHs are configured, the value of this parameter indicates the actual seizure rates of the AGCHs and the PCHs over the CCCHs. Maximum number of Channel Request messages that can be sent by an MS in an immediate assignment procedure. After the MS initiates the immediate assignment procedure, it always listens to the messages on the BCCH and all the common control channels (CCCHs) in the CCCH group to which the MS belongs. If the MS does not receive Immediate Assignment or Immediate Assignment Extend messages, it retransmits Channel Request messages at a specified interval. If the downlink quality is poor, the MS may send SABM frames to the BTS multiple times. Cell Reselect Penalty Time (PT) is used to ensure the safety and validity of cell reselection because it helps to avoid frequent cell reselection. For details, see GSM Rec. 05.08 and 04.08. Cell Reselect Offset (CRO), indicating a correction of the C2. Proper setting of this parameter can reduce the number of handover times, helpful for assigning an MS to a better cell. In a special case that the PT is 31, the larger the CRO value is, the lower the possibility of handing over an MS to the cell. Generally, do not set the CRO to a value larger than 25 dB. The CRO with a too large value will cause uncertain states in a network. The CRO values of the cells with different priorities in a network are almost the same. Refer to GSM Rec. 05.08 and GSM Rec. 04.08. The setting of this parameter affects only the MSs supporting the protocol of GSM Phase 2 or a later version. Cell Reselect Temporary Offset (TO) indicates the temporary correction of C2. This parameter is valid only within the value specified by "Cell Reselect Penalty Time". For details, see GSM Rec. 05.08 and 04.08. This parameter applies to only GSM Phase II MSs. Cell Reselect Parameters Indication (PI), sent on the broadcast channel, indicates whether "Cell Reselect Offset", "Cell Reselect Temporary Offset" in the "SET GCELLIDLEAD" command, and "Cell Reselect Penalty Time" are used.
Cell Bar Qualify
Cell Access Bar Switch Cell Reselect Hysteresis Parameters CCCH Blocks Reserved for AGCH
MS MAX Retrans Cell Reselect Penalty Time
Cell Reselect Offset
Cell Reselect Temporary Offset Cell Reselect Parameters Indication
Issue 08 (2011-09-30)
795
Parameter MCC MNC
Description Mobile country code. This parameter identifies the country where a mobile subscriber is located, for example, the Chinese MCC is 460. Mobile network code. This parameter identifies the public land mobile network (PLMN) to which a mobile subscriber belongs. Location area code (LAC). MSs can freely move in the local location area with no need of location update. Reasonable local allocation can effectively lighten the signaling load and improve the call completion rate. Can be input in hexadecimal format. The hexadecimal format is H'****, for example, H'1214. Attach-detach Allowed (ATT). If this parameter is set to YES, when an MS is powered off, the network does not process any call connection for the MS as a called party. In this way, the network processing time and resources are saved. This parameter specifies the length of the timer for periodic location update. Number of multiframes in a cycle on a paging sub-channel. In fact, this parameter specifies the number of paging sub-channels that a paging channel in a cell is divided into. In an actual network, an MS does not listen to other paging sub-channels but its belonging paging sub-channel only. Refer to GSM Rec. 05.02 and GSM Rec. 05.08. The larger the value of this parameter, the more the number of the paging sub-channels in a cell, and the fewer the number of the users belonging to each paging sub-channel. In this case, the mean uptime of the MS battery can be prolonged. Refer to the computing mode of paging group in GSM 05.02 of GSM Standards. The larger the value of this parameter, however, the larger the time delay of a paging message in a space segment. Thus, the average service performance of the system lowers. Based on the principle of ensuring that overload does not occur to paging channels, you must set this parameter to a value as small as possible. You must regularly measure the overload conditions of the paging channels in a running network and accordingly adjust the value of this parameter properly. A paging message in a location area must be sent in all the cells within this location area at the same time. Therefore, the capacity of a paging channel of each cell in a location area must be the same or nearly the same. The capacity refers to the calculated number of paging sub-channels of each cell. Whether to support SPLIT_PG_CYCLE on CCCH. The parameter SPLIT_PG_CYCLE is used to define the DRX period. You can specify whether the paging group based on SPLIT_PG_CYCLE is supported on CCCH for the BTS and the MS. Yes: the paging group based on SPLIT_PG_CYCLE is supported on CCCH. No: the paging group based on SPLIT_PG_CYCLE is not supported on CCCH. The NS performs location management based on routing areas during GPRS packet services. Each routing area has a routing area identifier, which is broadcast as a system message.
Cell LAC
Attach-detach Allowed T3212
Support SPLIT_PG_CYC LE on CCCH
RAC
Issue 08 (2011-09-30)
796
Parameter
Description Lifetime of a paging message in the paging queue of the BTS. The setting of this parameter must be consistent with the setting of timer T3113 at the core network; otherwise, the efficiency of paging scheduling over the Um interface is reduced. It is recommended that this parameter be set to a value one to two seconds shorter than timer T3113. The units of this parameter is 250 ms.The actually effective rang of this parameter is 8 to 80 or 255. The corresponding value is N multiplied by 250 milliseconds when this parameter is set to a value N. The calculation rules are as follows: 1) When the parameter value is smaller than 8, the BTS calculates the lifetime of a paging message as 8 multiplied by 250 milliseconds, which is 2 seconds. 2) When the parameter value is between 8 and 80, the BTS calculates the lifetime of a paging message as N multiplied by 250 milliseconds. For example, when the parameter value is 60, lifetime of a paging message is 15 seconds. 3) When the parameter value is between 81 and 254, the BTS calculates the lifetime of a paging message as 80 multiplied by 250 milliseconds, which is 20 seconds. 4) When the parameter value is 255, the lifetime of a paging message is 5 seconds. For the BTS, this parameter is used to determine paging retransmissions. This parameter and the number of paging times configured in the MSC determine the number of paging retransmissions. The total number of paging times is approximately equal to the value of this parameter multiplied by the number of paging times configured in the MSC.
BTS Paging Lifetime
Paging Times
Issue 08 (2011-09-30)
797
Parameter
Description Tx-integer (T for short). This parameter specifies the number of timeslots between two transmissions when an MS sends multiple consecutive channel requests. The access algorithm is defined in GSM Rec. 04.08 to reduce the collisions on the RACH and improve the efficiency of the RACH. The algorithm specifies three parameters: Txinteger (T for short), maximum number of retransmissions (RET), and S related to channel combination. This parameter works with the configuration of the CCCH to determine the parameter S. The relations between this parameter and the configuration of the CCCH are as follows: When this parameter is set to 3, 8, 14, or 50, S is 55 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 3, 8, 14, or 50, S is 41 if the CCCH and SDCCH share a physical channel. When this parameter is set to 4, 9, or 6, S is 76 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 4, 9, or 6, S is 52 if the CCCH and SDCCH share a physical channel. When this parameter is set to 5, 10, or 20, S is 109 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 5, 10, or 20, S is 58 if the CCCH and SDCCH share a physical channel. When this parameter is set to 6, 11, or 25, S is 163 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 6, 11, or 25, S is 86 if the CCCH and SDCCH share a physical channel. When this parameter is set to 7, 12, or 32, S is 217 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 7, 12, or 32, S is 115 if the CCCH and SDCCH share a physical channel. The timeslot for sending messages is a random value from the collection of {0, 1..., MAX(T, 8)-1}. The number of timeslots (excluding the timeslot used to send messages) between two adjacent channel request messages is a random value from the collection of {S, S+1, ..., S+T-1}. When T increases, the interval between two adjacent channel requests increases, and RACH conflicts decrease. When S increases, the interval between two adjacent channel request messages increases, and RACH conflicts decrease, thus improving the usage of AGCH and SDCCH. The access time of the MS, however, is prolonged and the network performance is decreased when T and S increase. Under normal conditions, an appropriate T value should be used to ensure that S is as low as possible, and ensure that AGCH and SDCCH are not overloaded. Level of common access control, used for load control, allowing or forbidding the access of some users of common access levels. This parameter is used for load control. It determines whether the users of special access class are allowed to access the network. Value 1 indicates that access is not allowed. Value 0 indicates that access is allowed. Whether to allow call re-establishment. Burst interference or blind spots due to high buildings may lead to a radio link failure. If a call drop is caused by such a failure, the MS can start call re-establishment to resume the conversation.
TX-integer Common Access Control Class
Special Access Control Class Call Reestablishment Forbidden
Issue 08 (2011-09-30)
798
Parameter
Description Whether to disable emergency calls. For the MSs of access levels 0 to 9, if the value of this parameter is NO, emergency calls are enabled. For the MSs of access levels 11 to 15, emergency calls are disabled only when the relevant access control bit is set to 0 and this parameter is set to YES. Whether the BSC sends the System Information Type 2ter message. Whether the BSC sends a System Information Type 2ter message to a non-dualband cell. When the parameter is set to YES, the cell does not send the System Information Type 2ter message if the cell is not configured with inter-frequency neighboring cells. If the cell is configured with inter-frequency neighboring cells, the cell sends the System Information Type 2ter message. When the parameter is set to NO and "Send System Information 2ter " is set to YES, the cell sends the System Information Type 2ter message. Otherwise, the cell does not send the message. This parameter specifies whether the SI Type 3 message contains the 2QUATER indicator. A set of NCCs of the cells to be measured by the MS. This parameter is an information element (IE) in the system information type 2 and 6 messages. If a bit of the value of this parameter is set to 1, the MS reports the corresponding measurement report to the BTS. The value of this parameter has a byte (eight bits). Each bit maps with an NCC (0~7) and the most significant bit corresponds to NCC 7. If bit N is 0, the MS does not measure the cell level of NCC N. Used for requesting the MS to report the measurement information of neighboring cells in multiple frequency bands. This parameter is carried in the system information 2ter and 5ter. Identity code of a cell, A cell is a wireless coverage area identified by a base station identity code and a global cell identification. Can be input in hexadecimal format. The hexadecimal format is H'****, for example, H'1214. Protocol version of the MSC that is connected to the BSC6900. The supported signaling varies with the protocol versions. Whether an MS uses the calculated value as the final receive level value. The calculated receive level value is the measured receive level value minus the receive level value obtained from the BCCH TRX timeslots. This parameter is a cell option in system messages 3 and 6.
Emergent Call Disable Send System Information 2ter
SI 2ter Switch Support Sent 2QUATER
NCC Permitted
Multi-band report
Cell CI MSC Version Indication
PWRC
Issue 08 (2011-09-30)
799
Parameter
Description Whether the uplink DTX function is enabled for FR calls. For details, see GSM Rec. 05.08. Uplink DTX is not restricted by the MSC. Shall_Use:An MS will use uplink DTX if it supports uplink DTX. May_Use:An MS will determine whether to use uplink DTX if both the cell and MS support uplink DTX. Shall_NOT_Use:DTX will not be used. Time for disconnecting a call when the MS fails to decode the SACCH. Once a dedicated channel is assigned to the MS, the counter S is enabled and the initial value is set to this parameter value. Each time an SACCH message is not decoded, the counter S decreases by 1. Each time an SACCH message is correctly decoded, the counter S increases by 2. When the counter S is equal to 0, the downlink radio link is considered as failed. Therefore, when the voice or data quality is degraded to an unacceptable situation and it cannot be improved through power control or channel handover, the connection is to be re-established or released. Used for notifying MSs where to retrieve relevant parameters during cell reselection. The default value of this parameter is 0 in system message 3 and, has no special significance. In system message 4, if the value of this parameter is 0, it means that the MSs must retrieve the PI parameters and other parameters relevant to cell reselection and the parameters relevant to C2 calculation from the remaining bytes of system message 4.If the value is 1, it means that the MS must retrieve the parameters from the remaining bytes of system message 7 or 8. This parameter determines whether the BSC6900 supports new establishment causes of an MS in the initial access request. This parameter does not affect the half-rate function of cells. The early classmark sending control(ECSC) parameter specifies whether the MSs in a cell use early classmark sending. After a successful immediate assignment, the MS sends additional classmark information to the network as early as possible. The additional classmark information mainly contains the CM3(classmark 3) information. The CM3 (classmark 3) information contains the frequency band support capability of the MS(used for the future channel assignment), power information about each frequency band supported by the MS(used for the handover between different frequency bands), and encryption capability of the MS. Whether the current cell supports GPRS. Routing area color code of the GPRS cell. Access priority of the MS that is allowed to access the cell. The MS sends the packet channel request containing the 2-bit radio priority message. The priority of the 2-bit radio priority message ranges from 1 to 4 in descending order. During the MS access, the BSC compares the radio priority in the channel request with the parameter setting of the cell. If the radio priority equals to the parameter setting of the cell, the BSC sets up the TBF for the channel request.
FR Uplink DTX
Radio Link Timeout
Additional Reselect Parameter Indication
Support Half Rate
ECSC GPRS Routing Area Color Code

Issue 08 (2011-09-30)
800
Parameter
Description Network control mode for cell reselection of the MS. There are three modes. NC0: normal MS control. The MS shall perform autonomous cell re-selection. NC1: MS control with measurement reports. The MS shall send measurement reports to the network and the MS shall perform autonomous cell re-selection. NC2: network control. The MS shall send measurement reports to the network . The MS shall only perform autonomous cell re-selection when the reselection is triggered by a downlink signaling failure or a random access failure.When this parameter is set to NC2 and "Support NC2" in "SET GCELLGPRS" is set to "YES", the network side can control the cell reselection for the MS. Period for sending the packet message PSI. If the period is too long, the message PSI cannot be obtained in realtime. If the period is too short, the message PSI is broadcast frequently, which occupies too much system resources. Number of blocks occupied by the NCH in the group call service. Number of the start block occupied by the NCH in the group call service.
PSI1 Repetition Period NCH Occupy Block Number NCH Start Block
Table 2-141 Parameter description (2) Paramete r Minum Access RXLEV MS_TXP WR_MAX _CCH Power Deviation Power Deviation Indication Cell Bar Qualify Default Value GUI Value Range Actual Value Range MML Command Unit SET GCELLBASICPARA (Optional) SET GCELLCCCH (Optional) SET GCELLCCACCESS (Optional) SET GCELLCCACCESS (Optional) SET GCELLIDLEBASIC (Optional) Impa ct
0~63
0~63
dB
Cell
0~19
0~19
None
Cell
0~3 NO(No), YES (Yes) NO(No), YES (Yes)
0~3
None
Cell
YES
NO, YES
None
Cell
NO
NO, YES
None
Cell
Issue 08 (2011-09-30)
801
Paramete r
Default Value
GUI Value Range Permit (Permit Cell Access), NoPermit (Prohibit Cell Access) 0dB, 2dB, 4dB, 6dB, 8dB, 10dB, 12dB, 14dB
Actual Value Range
MML Command Unit
Impa ct
Cell Access Bar Switch
Permit
Permit, NoPermi t 0dB, 2dB, 4dB, 6dB, 8dB, 10dB, 12dB, 14dB
None
SET GCELLSERVPARA (Optional)
Cell
Cell Reselect Hysteresis Parameters CCCH Blocks Reserved for AGCH
6dB
dB
SET GCELLIDLEBASIC (Optional) SET GCELLIDLEBASIC (Optional)
Cell
0~7 1_Times (1_Times ), 2_Times (2_Times ), 4_Times (4_Times ), 7_Times (7_Times )
0~7
None
Cell
MS MAX Retrans
4_Times
1_Times, 2_Times, 4_Times, 7_Times 0~31. 0 to 30 indicate 20 s to 620 s, and 31 is a reserved value used to redirect the effect of CR0 on C2.
None
Cell
Cell Reselect Penalty Time

Issue 08 (2011-09-30)
0~31
None
SET GCELLIDLEAD (Optional)
Cell
802
Paramete r Cell Reselect Offset Cell Reselect Temporary Offset Cell Reselect Parameters Indication
Default Value
GUI Value Range
Actual Value Range 0~126, step: 2
MML Command Unit SET GCELLIDLEBASIC (Optional)
Impa ct
0~63
dB
Cell
0~7
None
SET GCELLIDLEAD (Optional) SET GCELLIDLEBASIC (Optional) ADD GCNOPERATOR (Mandatory) SET BTSAUTOPLANCFG (Optional) ADD GCELLQUICKSETUP (Mandatory) ADD BTSAUTOPLAN (Mandatory) SET FHO(Mandatory) ADD GEXT3GCELL (Mandatory) ADD GEXT2GCELL (Mandatory)
Cell
YES
NO, YES
None
Cell
MCC
None
None
3 digit
None
ADD GCELL (Mandatory)
Cell
Issue 08 (2011-09-30)
803
Paramete r
Default Value
GUI Value Range
Actual Value Range
MML Command Unit ADD GCNOPERATOR (Mandatory) ADD GCELL (Mandatory) ADD GEXT2GCELL (Mandatory) ADD GEXT3GCELL (Mandatory) SET FHO(Mandatory) ADD BTSAUTOPLAN (Mandatory) SET BTSAUTOPLANCFG (Optional) ADD GCELLQUICKSETUP (Mandatory) ADD GCELL (Mandatory) ADD GCELLQUICKSETUP (Mandatory) SET BTSAUTOPLANCFG (Optional) ADD BTSAUTOPLAN (Mandatory) SET FHO(Mandatory) ADD GEXT3GCELL (Mandatory)
Impa ct
MNC
None
None
2~3 digit
None
Cell
Cell LAC Attachdetach Allowed
None
1~65533, 65535 NO(No), YES (Yes)
1~65533 , 65535
None
ADD GEXT2GCELL (Mandatory) SET GCELLIDLEBASIC (Optional) SET GCELLIDLEBASIC (Optional)
Cell
YES
NO, YES 0~1530, step: 6
None
Cell
T3212
20
0~255
min
Cell
Issue 08 (2011-09-30)
804
Paramete r
Default Value
GUI Value Range 2_M_PE RIOD(2 Multifra me Period), 3_M_PE RIOD(3 Multifra me Period), 4_M_PE RIOD(4 Multifra me Period), 5_M_PE RIOD(5 Multifra me Period), 6_M_PE RIOD(6 Multifra me Period), 7_M_PE RIOD(7 Multifra me Period), 8_M_PE RIOD(8 Multifra me Period), 9_M_PE RIOD(9 Multifra me Period) NO(NO), YES (YES) 0~255
Actual Value Range
MML Command Unit
Impa ct
MultiFrames in a Cycle on the Paging CH Support SPLIT_PG _CYCLE on CCCH RAC
2_M_PE RIOD
940~423 0, step: 470
ms
SET GCELLIDLEBASIC (Optional)
Cell
NO 0
NO, YES 0~255
None None
SET GCELLPSBASE (Optional) ADD GEXT2GCELL (Optional)
Cell Cell
Issue 08 (2011-09-30)
805
Paramete r BTS Paging Lifetime Paging Times
Default Value
GUI Value Range
Actual Value Range
MML Command Unit
Impa ct
255 4
0~255 1~8 TX_3(3), TX_4(4), TX_5(5), TX_6(6), TX_7(7), TX_8(8), TX_9(9), TX_10 (10), TX_11 (11), TX_12 (12), TX_14 (14), TX_16 (16), TX_20 (20), TX_25 (25), TX_32 (32), TX_50 (50)
0~255 1~8
ms None
SET GCELLSOFT (Optional) SET GCELLCCBASIC (Optional)
Cell Cell
TX-integer
TX_32
TX_3, TX_4, TX_5, TX_6, TX_7, TX_8, TX_9, TX_10, TX_11, TX_12, TX_14, TX_16, TX_20, TX_25, TX_32, TX_50
None
SET GCELLIDLEBASIC (Optional)
Cell
Issue 08 (2011-09-30)
806
Paramete r
Default Value L0_FOR BID-0& L1_FOR BID-0& L2_FOR BID-0& L3_FOR BID-0& L4_FOR BID-0& L5_FOR BID-0& L6_FOR BID-0& L7_FOR BID-0& L8_FOR BID-0& L9_FOR BID-0 L11_FO RBID-0 &L12_F ORBID0&L13_ FORBI D-0&L1 4_FOR BID-0& L15_FO RBID-0
GUI Value Range L0_FOR BID, L1_FOR BID, L2_FOR BID, L3_FOR BID, L4_FOR BID, L5_FOR BID, L6_FOR BID, L7_FOR BID, L8_FOR BID, L9_FOR BID L11_FO RBID, L12_FO RBID, L13_FO RBID, L14_FO RBID, L15_FO RBID NO(No), YES (Yes) NO(No), YES (Yes) NO(No), YES (Yes) NO(No), YES (Yes)
Actual Value Range L0_FOR BID, L1_FOR BID, L2_FOR BID, L3_FOR BID, L4_FOR BID, L5_FOR BID, L6_FOR BID, L7_FOR BID, L8_FOR BID, L9_FOR BID L11_FO RBID, L12_FO RBID, L13_FO RBID, L14_FO RBID, L15_FO RBID
MML Command Unit
Impa ct
Common Access Control Class
None
Cell
Special Access Control Class Call Reestablis hment Forbidden Emergent Call Disable Send System Informatio n 2ter SI 2ter Switch
None
SET GCELLCCBASIC (Optional) SET GCELLBASICPARA (Optional) SET GCELLCCBASIC (Optional)
Cell
YES
NO, YES
None
Cell
NO
NO, YES
None
Cell
NO
NO, YES
None
SET OTHSOFTPARA (Optional) SET OTHSOFTPARA (Optional)
BSC
YES
NO, YES
None
BSC
Issue 08 (2011-09-30)
807
Paramete r Support Sent 2QUATER
Default Value
GUI Value Range NO(No), YES (Yes)
Actual Value Range
MML Command Unit
Impa ct
YES SELEC TION0_ PERM-1 &SELE CTION1 _PERM1&SEL ECTIO N2_PER M-1&S ELECTI ON3_P ERM-1 &SELE CTION4 _PERM1&SEL ECTIO N5_PER M-1&S ELECTI ON6_P ERM-1 &SELE CTION7 _PERM1 0
NO, YES
None
SET OTHSOFTPARA (Optional)
BSC
NCC Permitted Multi-band report
SELECT ION0_P ERM, SELECT ION1_P ERM, SELECT ION2_P ERM, SELECT ION3_P ERM, SELECT ION4_P ERM, SELECT ION5_P ERM, SELECT ION6_P ERM, SELECT ION7_P ERM 0~3
SELECT ION0_P ERM, SELECT ION1_P ERM, SELECT ION2_P ERM, SELECT ION3_P ERM, SELECT ION4_P ERM, SELECT ION5_P ERM, SELECT ION6_P ERM, SELECT ION7_P ERM 0~3
None None
SET GCELLIDLEBASIC (Optional) SET GCELLCCBASIC (Optional)
Cell Cell
Issue 08 (2011-09-30)
808
Paramete r
Default Value
GUI Value Range
Actual Value Range
MML Command Unit ADD GCELL (Mandatory) ADD GCELLQUICKSETUP (Mandatory) SET BTSAUTOPLANCFG (Optional) ADD BTSAUTOPLAN (Mandatory) SET FHO(Mandatory) ADD GEXT3GCELL (Mandatory)
Impa ct
Cell CI
None
0~65535 R98_or_ below (R98 or below), R99_or_ above (R99 or above) NO(No), YES (Yes) May_Use (May Use), Shall_Us e(Shall Use), Shall_N OT_Use (Shall not Use)
0~65535
None
ADD GEXT2GCELL (Mandatory)
Cell
MSC Version Indication
R98_or_ below
R98_or_ below, R99_or_ above
None
SET GCELLCCUTRANSY S(Optional) SET GCELLCCCH (Optional)
Cell
PWRC
YES
NO, YES
None
Cell
FR Uplink DTX
Shall_U se
May_Us e, Shall_Us e, Shall_N OT_Use
None
SET GCELLBASICPARA (Optional)
Cell
Issue 08 (2011-09-30)
809
Paramete r
Default Value
GUI Value Range 4_Times, 8_Times, 12_Time s, 16_Time s, 20_Time s, 24_Time s, 28_Time s, 32_Time s, 36_Time s, 40_Time s, 44_Time s, 48_Time s, 52_Time s, 56_Time s, 60_Time s, 64_Time s COMPU L0 (Compul sory 0), COMPU L1 (Compul sory 1), FLEX (Flexible ) NO(No), YES (Yes)
Actual Value Range
MML Command Unit
Impa ct
Radio Link Timeout
52_Tim es
1920~30 720, step: 480
ms
Cell
Additional Reselect Parameter Indication Support Half Rate
FLEX
COMPU L0, COMPU L1, FLEX
None
SET GCELLIDLEAD (Optional) SET GCELLCCCH (Optional)
Cell
NO
NO, YES
None
Cell
Issue 08 (2011-09-30)
810
Paramete r
Default Value
GUI Value Range NO(No), YES (Yes) NO(Not support), SupportA sInnPcu (Support as builtin PCU), SupportA sExtPcu (Support as external Pcu)
Actual Value Range
MML Command Unit
Impa ct
ECSC
YES
NO, YES
None
Cell
GPRS Routing Area Color Code
NO
NO, Support AsInnPc u, Support AsExtPc u
None
SET GCELLGPRS (Mandatory) SET GCELLPSBASE (Optional)
Cell
0~7 0(No packet access), 3 (Packet access of level 1), 4 (Packet access of levels 1-2), 5 (Packet access of levels 1-3), 6 (Packet access of level 1-4) NC0 (NC0), NC1 (NC1), NC2 (NC2)
0~7
None
Cell
0, 3, 4, 5, 6
None
SET GCELLPSBASE (Optional)
Cell
Network Control Mode PSI1 Repetition Period
NC0
NC0, NC1, NC2
None
SET GCELLPSBASE (Optional) SET GCELLPSI1 (Optional)
Cell
1~16
1~16
None
Cell
Issue 08 (2011-09-30)
811
Paramete r NCH Occupy Block Number NCH Start Block
Default Value
GUI Value Range
Actual Value Range
MML Command Unit
Impa ct
0 0
0~7 0~7
0~7 0~7
None None
SET GCELLGSMR (Optional) SET GCELLGSMR (Optional)
Cell Cell
2.49.5 Counters
2.49.6 Glossary

l l l l l l l l l l 3GPP TS 23.122 Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode 3GPP TS 44.018 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol 3GPP TS 45.008 Radio subsystem link control 3GPP TS 43.022 Functions related to Mobile Station (MS) in idle mode and group receive mode BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.50 Intelligent Power Consumption Decrease

2.50.1 Introduction
2.50.1.1 Scope
This document describes the intelligent power consumption decrease feature of Huawei GBSS. It describes the functions and technologies related to this feature, including TRX power amplifier intelligent shutdown, TRX power amplifier intelligent shutdown on the timeslot level, intelligent combiner bypass, intelligent adjustment of TRX working voltage, power supply unit (PSU) smart control, power optimization based on channel type, active backup power control, enhanced BCCH power consumption optimization, and dynamic cell power off.


The change history provides information on the changes in the intelligent power consumption decrease feature in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the intelligent power consumption decrease feature of a specific product version. l Editorial change Editorial change refers to change in wording or the addition of information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change
Issue 08 (2011-09-30)
Change Description None. The document organization is optimized.
813
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description 2.50.3.10 Dynamic Cell Power Off is added. Parameter Change The added parameters are listed as follows: l Enable Turning Off Cell l Dyn. Turning Off Cell Start Time l Dyn. Turning Off Cell Stop Time l Dyn. Turning Off Cell Protection Time l Dyn. Turning Off Cell Busy Channel Num. l Same Coverage Cell Load Threshold l Same Coverage Cell Load Stat. Time Editorial change The document organization is optimized. None.
2.50.2 Overview
To construct a network with a large capacity, wide coverage, and good performance, an operator needs to deploy a large number of BTS sites. Generally, the power consumption of BTS equipment and air-conditioning equipment takes more than 90% of the power consumption of the radio access network. In addition to paying a high cost for power, the operator needs to conform to the social responsibility of energy saving, emission reduction, and environment protection. By introducing the solution of intelligent power consumption decrease to the BSS equipment and adopting the advanced power control algorithm, Huawei can help the operator solve this problem. Intelligent power consumption decrease refers to the solution of decreasing power consumption of the BTS or even in a coverage area useing hardware or software without deteriorating network performance and BTS hardware performance. The BTS site power consumption includes BTS power consumption and air-conditioner power consumption. Once the BTS power consumption decreases, the air-conditioner power consumption decreases accordingly. intelligent power consumption decrease aims to decrease the BTS power consumption. The BTS power consumption includes cabinet power consumption and TRX power consumption, as shown in Figure 2-161.
Figure 2-161 BTS3900 power consumption
NOTE
The power consumption of BTSs of other models is similar to the BTS3900 power consumption.
Cabinet power consumption The cabinet power consumption constitutes a small part of the BTS power consumption. The cabinet power consumption is generated by the TRX supporting system and basic site control and transmission equipment.
TRX power consumption The TRX power consumption constitutes a primary part of the BTS power consumption. The power consumption of TRXs is related to factors such as number of configured TRXs, traffic volume, output power, and working mode. The TRX power consumption includes: Dynamic power consumption of the power amplifier: power consumed by the power amplifier for carrying services. Static power consumption of the power amplifier: power consumed by the static current that ensures the normal operation of the power amplifier. Dynamic power consumption of the power amplifier and static power consumption of the power amplifier constitute the power consumption of the power amplifier. Baseband power consumption: power consumed by Digital Signal Processor (DSP), Field Programmable Gate Array (FPGA), and Central Processing Unit (CPU). Power consumption of the radio frequency (RF) signal: power consumed by the digital intermediate frequency (IF) circuit, Digital-to-Analog/Analog-to-Digital (DA/AD) circuit, and low-power RF signal circuit.
The intelligent power consumption decrease feature decreases the power consumption of the power amplifier, baseband power consumption, and power consumption of the RF signal. Thus, the BTS power consumption is decreased. The technologies involved in the intelligent power consumption decrease are TRX power amplifier intelligent shutdown, TRX power amplifier intelligent shutdown on the timeslot level, intelligent combiner bypass, intelligent adjustment of TRX working voltage, channel allocation algorithms concerning power consumption decrease, Power Supply Unit (PSU) smart control, Discontinuous transmission (DTX), power
control, power optimization based on channel type, enhanced BCCH power consumption optimization, active backup power control, and dynamic cell power off. For details about DTX and power control, see the 2.25.3.1 DTX and the 2.64 Power Control. Intelligent power consumption decrease can save energy, reduce emission, and save capital expenditure (CAPEX) by decreasing the BTS power consumption. In the case of the BTSs with storage battery and other power backups, intelligent power consumption decrease can prolong the serving time of the storage battery and shorten the serving time of the generator. Intelligent power consumption decrease can also prolong the serving time of cells and reduce the number of storage batteries, reducing CAPEX.

2.50.3.1 TRX Power Amplifier Intelligent Shutdown
The TRX power consumption is mainly generated by the power amplifier. When there is no traffic, only static power consumption of the power amplifier is generated, and there is not the dynamic power consumption. When there is traffic, dynamic power consumption is generated. The dynamic power consumption increases with the TRX output power. Generally, a cell is not always in the busy state. When TRX power amplifier intelligent shutdown is enabled, some TRXs carry the traffic in a cell, and the power amplifiers of the TRXs not carrying traffic are shut down. That is, the power amplifiers of the TRXs whose dynamic power consumption is zero are shut down. Thus, the BTS power consumption is decreased. TRX power amplifier intelligent shutdown does not affect network quality. If an MS is alocated channels of TRXs whose power amplifiers are shut down, however, the MS takes a longer time to access the network, because switching on the power amplifiers of the TRXs is time consuming. To minimize the impact of TRX power amplifier intelligent shutdown on the network quality, the parameters Time When the Function Is Enabled and Time When the Function Is Disabled can be specified at the BSC. The traffic volume on weekends and holidays are higher than on weekdays, and the busy hours in weekends and holidays are more than weekdays. You can set Prohibit Power Saving Start Month and Prohibit Power Saving Start Day at the BSC to disable TRX power amplifier intelligent shutdown from the specified date. You can also set Prohibit Power Saving End Month and Prohibit Power Saving End Day so that TRX power amplifier intelligent shutdown is enabled again from the specified date. The TRX whose power amplifiers can be shut down must meet the following conditions: l l l l l The TRX works properly. The maximum operation interval of the TRX is greater than TRX Power-on Protection Time. After the TRX is shut down, an idle SDCCH is available in this cell. There is no PDCH on the TRX. No channel under conversion exists on the TRX.
If TRX power amplifier intelligent shutdown is enabled in a cell, the BSC predicts the number of channels that the cell requires in the next minute based on the historical channel usage when TRX power amplifier intelligent shutdown is allowed. If the number of channels that the cell requires is smaller than that of the available channels after a TRX is shut down, the BSC attempts to shut down a TRX having no PDCH and whose channel usage is the lowest. l
Issue 08 (2011-09-30)
If no channels carried by a TRX are seized, the BSC shuts down the TRX.
l l
If TCHs carried by a TRX are seized, the BSC hands over the services on the TRX to other TRXs, and then shuts down the TRX. If the SDCCH carried by a TRX is seized, the BSC does not shut down the TRX until the SDCCH is released.
The BSC preferentially allocates channels carried on operating TRXs to the MS. If there is no channel available carried by the operating TRX in the cell, the BSC allocates channels carried by the TRX that is shut down to the MS. The BSC instructs the BTS to switch on the power amplifier of the TRX, and then activates the channels carried on the TRX and allocates the channels carried by the TRX to the MS. To speed up channel allocation, the parameter Reserved TCH Number for PA Turning On is configured. When the number of idle TCHs is smaller than the value of this parameter, the BSC instructs the BTS to switch on a TRX that is shut down.
CAUTION
The value of Reserved TCH Number for PA Turning On must be smaller than the number of available TCHs carried on the current BCCH TRX. Baseband power consumption, RF signal power consumption, static TRX power consumption, and dynamic TRX power consumption constitute the power consumption of the TRX board. When the power amplifiers on a TRX board are all shut down, the BTS can shut down the lowpower RF signal circuit of the RF signals to reduce the TRX power consumption. When any of the TRXs on the double-transceiver unit needs to be switched on, the BTS automatically switches on the RF signals. TRX power amplifier intelligent shutdown is a prerequisite for TRX lowpower signal intelligent shutdown. That is, the TRX low-power signals are shut down only after the power amplifiers of the TRX are shut down. You are advised to enable the low-power signal intelligent shutdown feature when the traffic is low, for example, at night. The BSC can control TRX power amplifier intelligent shutdown only when the parameter Allow Dynamic Shutdown of TRX by BSC on the BSC level, the parameter Allow Dynamic Shutdown of TRX on the cell level, and the parameter Allow Dynamic Shutdown of TRX on the TRX level are all set to Yes.
NOTE
Before configuring Allow Dynamic Shutdown of TRX on the TRX, ensure that the TRX meets the following conditions: l The TRX is not on the BCCH. l The PDCH is not available on the TRX. l The antenna hopping is disabled for the TRX.
In a cell enabled with baseband FH or hybrid FH, if all the TRXs in a same baseband FH group meet the requirements for TRX power amplifier intelligent shutdown, all the TRXs in the baseband FH can be shut down. When the TRXs need to be powered on again, the TRXs in the same baseband FH group must be powered on.
2.50.3.2 TRX Power Amplifier Intelligent Shutdown on the Timeslot Level

The optimized double-transceiver unit supports independent control of two power amplifiers. Thus, TRX power amplifier intelligent shutdown on the timeslot level is supported and the power consumption of the power amplifier on the timeslot level is zero. There are eight timeslots in a TRX. If only one timeslot has traffic and the other seven timeslots are idle, the power amplifier is working only in the timeslot with the traffic, and is shut down in the other seven timeslots.
The power amplifier on the double-transceiver unit is switched on or shut down during the time on the timeslot level. In this manner, when timeslots are idle, the power consumption generated by the power amplifier can be reduced during the fixture of offset voltage in the linear area. TRX power amplifier intelligent shutdown on the timeslot level does not affect channel assignment and traffic. Thus, it does not affect on network quality. The power supply of the power amplifier is controlled inside the BTS, and the power amplifier can be switched on or shut down during a common traffic processing procedure. This is achieved by the Huawei technology of high-speed power supply control of power amplifier, where the power amplifier can be switched on or shut down in a very short time (close to 0s). The power amplifier is a field-effect transistor. One of the main factors that affect the life cycle of the field-effect transistor is the high temperature caused by high electrical current. When the power amplifier is shut down, there is no current and the accumulated heat is released. Therefore, when intelligent power amplifier shutdown on the timeslot level is enabled, the lifetime of the power amplifier is extended. TRX power amplifier intelligent shutdown on the timeslot level switches on or shuts down the power amplifier on the timeslot level. When there are idle timeslots, the TRX that cannot be shut down by TRX power amplifier intelligent shutdown can be shut down by using the function of TRX power amplifier intelligent shut down on the timeslot level. Thus, the power consumption of power amplifier can be decreased to the greatest extent. TRX power amplifier intelligent shutdown on the timeslot level is controlled by Allow Turning Off Time Slot, and applies to only the double-transceiver unit.
2.50.3.3 Intelligent Combiner Bypass

Intelligent Combiner Bypass (ICB) applies to double-transceiver unit. When the non-BCCH TRX is idle, the BCCH TRX is in ICB mode with a capacity of one TRX. The lowest voltage is used by power amplifier on the BCCH TRX, and the output power of a single power amplifier on the BCCH TRX is 15 W or 10 W. After Power Burst Technology (PBT) is used on the BCCH TRX, the transmit power on top of the cabinet of the BCCH TRX is the same as that of a single power amplifier, that is, 60 W or 40 W. Take an S4 cell for an example. To meet the coverage requirement of the cell, the output power on the TRX port must be 30 W. Generally, the output power of the TRX is 60 W. After the combination, the output power of both TRXs is 30 W so that the coverage requirement of the cell is met. When the traffic volume is lower than that in S2 cell, the output power of each TRX can be reduced to 15 W if the PBT mode is used, so that the combination output power remains 30 W, as shown in Figure 2-162. In this case, the cell capacity is reduced to S2. The TRX power, however, decreases from 60 W to 15 W. As a result, the power consumption of the TRX and the BTS is greatly decreased.
Issue 08 (2011-09-30)
818
Figure 2-162 ICB principle
Intelligent combiner bypass is controlled by the ICB Allowed parameter. If this parameter is set to Yes, the intelligent combiner bypass feature is enabled. To enable the intelligent combiner bypass feature, set TRX Priority of the TRX that is on the same double-transceiver unit as the BCCH to a low level so that the BCCH TRX is in ICB mode when the cell is idle. In this manner, power consumption is decreased.
NOTE
The TRX Priority parameter is used together with Allocation TRX Priority Allowed. The channel can be assigned based on the TRX priority only when Allocation TRX Priority Allowed is set to Yes.
2.50.3.4 Intelligent Adjustment of TRX Working Voltage

?.1. Overview of Intelligent Adjustment of TRX Working Voltage
The efficiency of TRX power amplifier is related to the transmit power of the TRX power amplifier. When the TRX transmits signals at the maximum transmit power, the TRX power amplifier achieves its full efficiency. When the TRX does not transmit signals at the maximum transmit power, the efficiency of the TRX power amplifier significantly decreases. The TRX power consumption accounts for a large proportion of the BTS power consumption. Thus, when the TRX does not transmit signals at the maximum transmit power, the efficiency of the TRX power amplifier can be improved to reduce the BTS power consumption. Both the TRX Working Voltage Adjustment feature and the Multi-Carrier Intelligent Voltage Regulation feature can, to a certain extent, improve the efficiency of the power amplifier on a TRX that does not transmit signals at the maximum transmit power.
?.2. TRX Working Voltage Adjustment
Overview
To ensure that the TRX transmits signals at the maximum transmit power, the working voltage of the TRX should be high. In practice, however, the TRX does not always transmit signals at
the maximum transmit power. In this case, if the working voltage of the TRX is high, the TRX power consumption is increased. Actually, if the TRX transmits signals at low transmit power, the working voltage of the TRX can be lowered, as a low voltage ensures the normal transmission of signals at low transmit power. When the transmit power of the TRX power amplifier decreases, the working voltage of the TRX can be lowered without decreasing the power gain of the TRX power amplifier. In this way, the power consumption of the TRX power amplifier and the overall power consumption of the BTS are also reduced. Figure 2-163 shows the relation between the transmit power and the power gain. Figure 2-163 Relation between the transmit power and the power gain
Principles
When Adjust Voltage is enabled, the BTS adjusts the working voltage of the TRX according to the pre-defined voltages. When adjusting the working voltage of the TRX, the BTS should consider the following factors: l l Modulation scheme 8 Phase Shift Keying (8PSK) and Gaussian Minimum Shift Frequency Keying (GMSK) Setting of the power type The Power Type parameter specifies the type of power used by the TRX.
Issue 08 (2011-09-30)
820
Take the DTRU board as an example. The DTRU board supports multiple types of power, such as 60 W and 40 W. l l Static power level The Power Level parameter specifies the static power level of the TRX. Frequency bands supported by the TRX GSM900, DCS1800, GSM850, and GSM1900 Note that different TRXs generally have different pre-defined voltages. The TRX determines the maximum transmit power of the TRX power amplifier according to the following data configured on the BSC: transmit power of the carrier, combination of channel types, and the number of carriers configured on the RF channel. After power-on, the BTS adjusts the working voltage of the TRX power amplifier according to the preset voltages if the transmission on the Um interface meet the requirements stipulated by the GSM specifications. This helps to improve the efficiency of the TRX power amplifier and reduce the BTS power consumption. When the setting of the modulation scheme, power type, or static power level for a carrier needs to be modified, the TRX adjusts the working voltage of the TRX power amplifier that serves the carrier. The voltage is adjusted according to the pre-defined voltages. During the voltage adjustment, the system takes certain protective measures to ensure the normal operation of the TRX.
?.3. Multi-Carrier Intelligent Voltage Regulation
Overview
The TRX Working Voltage Adjustment feature enalbes the BTS to adjust the working voltage of the TRX to ensure that the TRX always works at the appropriate voltage. In this feature, the working voltage is adjusted on the basis of the actual settings. In practice, however, the actual conditions of the network are quite complicated and the transmit power of the TRX varies. Therefore, it is impossible for operators to modify the settings of the related parameters in real time. The Multi-Carrier Intelligent Voltage Regulation feature is introduced to dynamically adjust the working voltage of the TRX according to the dynamic changes of the working status of the TRX. By using this feature, the BTS power consumption is significantly reduced. The working voltage of the TRX must be dynamically adjusted according to the downlink load power in the following scenarios: Otherwise, the significant reduction of the BTS power consumption cannot be achieved. Such scenarios are listed as follows: l l l Scenario where the traffic load varies greatly in a day Business areas where the traffic load is heavy on working days but light on weekends and holidays Scenario where the network is just deployed and the traffic load is still light
Principles
The Multi-Carrier Intelligent Voltage Regulation feature enalbes the BTS to measure the downlink transmit power of the TRX in real time. In addition, the BTS adjusts the working voltage of the TRX on the basis of the downlink load power when that the TRX does not transmit signals at the maximum transmit power. The PA Intelligent Adjust Voltage parameter specifies whether to enable the multi-carrier intelligent voltage regulation feature. When the PA Intelligent Adjust Voltage parameter is
enabled, the BTS adjusts the working voltage of the TRX according to the measurement results of the downlink load power to reduce the power consumption. 1. Measurement of downlink load power and analysis of the changes The BTS measures the downlink load power of a carrier in real time and takes a certain number of valid samples in a measurement period. The greatest power value among the samples is considered as the power of the carrier in this measurement period. The sum of the power of the multiple carriers in a TRX is used to obtain the downlink load power of the TRX and its changes. The BTS needs to analyze the changes in the downlink load power and predict the transmit power of the TRX in the next period. To ensure the effectiveness and accuracy of the measurement, the samples from multiple measurement periods are used for calculation. 2. Adjustment of the TRX working voltage The BTS predicts the transmit power of the TRX in the next period based on the measurement results of the downlink load power. In addition, the BTS compares the predicted transmit power with the current transmit power, determines the working voltage of the TRX, and adjusts the working voltage of the TRX accordingly. l Increasing the working voltage of the TRX If the predicted transmit power corresponds to a power level that is higher than the current power level, the BTS immediately adjusts the working voltage of the TRX. Specifically, the BTS adjusts the power level to a level that is one level higher than the power level corresponding to the predicted transmit power. The BTS does not adjust the power level if the power level is already the highest. l Decreasing the working voltage of the TRX If the predicted transmit power corresponds to a power level that is lower than the current power level, the BTS immediately adjusts the working voltage of the TRX. Specifically, the BTS adjusts the power level to a level that is one level lower than the current power level. The BTS does not adjust the power level if the power level is already the lowest.
2.50.3.5 Channel Allocation Algorithms Concerning Power Consumption Decrease

Proper channel allocation helps decrease the BTS power consumption. The channel allocation algorithms concerning intelligent power consumption decrease include preferential allocation of channels on the BCCH TRX and preferential allocation of channels on the TRX with a good power-saving performance.
Preferential Allocation of Channels on the BCCH TRX

Regardless of whether channels on the BCCH TRX are seized, signals are transmitted at full power. When channels carried on the BCCH TRX are seized, normal bursts are transmitted. When channels carried on the BCCH TRX are idle, dummy bursts are transmitted. TRX power amplifier intelligent shutdown on the timeslot level, power control, and DTX cannot be applied to BCCH TRX. With the introduction of preferential allocation of channels on the BCCH TRX, the BSC preferentially allocates channels on the BCCH TRX to the MS to reduce the usage of channels carried by non-BCCH TRXs so that intelligent power consumption decrease can be applied to the non-BCCH TRXs. Preferential allocation of channels on the BCCH TRX is controlled by TRX Priority. The higher the TRX Priority, the lower the priority of channel allocation. Therefore, preferential allocation of channels on the BCCH TRX can be achieved by raising TRX Priority of the non-BCCH TRX.
Preferential Allocation of Channels on the TRX with a Good Power-Saving Performance

With different power-saving performance of various chips, TRXs produced at different periods and of different types have different power-saving capabilities. When there are TRXs with different power-saving performance in a cell, you can preferentially use the TRXs with good power-saving performance and apply power-saving technology to the TRXs with poor powersaving performance to decrease the BTS power consumption. When a TRX is powered on, the TRX reports its power-saving performance to the BSC. The BSC then preferentially allocates the channels on the TRXs with good power-saving performance to the MS. Preferential allocation of channels on the TRXs with good power-saving performance is controlled by Power Priority Allowed.
2.50.3.6 PSU Smart Control

if the external power supply cannot meet the DC -48V requirement for the BTS, you need to configure the BTS power supply system so that the AC 220V can be converted to DC -48V. Power Management Unit (PMU) and PSU constitute the BTS power supply system. The PMU manages the PSU and BTS communication, and the PSU converts the power. To meet the power supply requirement, the PSU is configured in N+1 mode and in accordance with the maximum BTS power consumption. The highter the PSU output power is, the more efficient the power conversion is. In most cases, however, the BTS does not operate with the maximum power consumption, and the PSU is lightly loaded. This leads to low power conversion efficiency (as low as 70%) and shortens the lifetime of the PSU if all the PSUs operate. The PSU smart control feature switches on only the required PSUs and shuts down the redundant PSUs. In this way, the efficiency of the power system is improved and the lifetime of the power system is extended. PSU smart control is implemented by the PMU. The XMU should support intelligent PSU shutdown and deliver the function to the PMU. The XMU is the general name for BTS3900(A) GTMU, DBS3900 GTMU, BTS3012 DTMU, BTS3012AE DTMU, BTS3006C DMCM, and BTS3002E DMCM PSU smart control is controlled by PSU Turning Off Enable.
2.50.3.7 Power Optimization Based on Channel Type

Different channels use different modulation modes. After the Enhanced General Packet Radio Service (EGPRS) feature is introduced to the GSM network, the 8PSK modulation mode is added to the GMSK modulation mode. With the same output power, a higher voltage is required by the TRX power amplifiers in 8PSK modulation mode than in GMSK modulation mode. After power optimization based on channel type is enalbed, the voltage is provided for TRX power amplifiers based on different modulation modes of channels so that the BTS power consumption can be decreased. If all the channels on a TRX are TCHs, the TRX works in GMSK modulation mode, and the TRX power amplifiers are provided with a voltage in accordance with the GMSK modulation mode. If there are static or dynamic PDCHs on the TRX, the TRX works in 8PSK modulation mode, and the TRX power amplifiers are provided with a voltage in accordance with the 8PSK modulation mode, as shown in Figure 2-164.
Figure 2-164 Principle of power optimization based on channel type
NOTE
When there are PDCHs on the TRX, regardless of whether they are static or dynamic, the TRX power amplifiers should be provided with a voltage in accordance with the 8PSK modulation mode. That is, the power optimization based on channel type is not on timeslot level.
Power optimization based on channel type is controlled by PDCH Power Saving Enable.and applies to both to double-transceivers and multi-carrier devices.
2.50.3.8 Active Backup Power Control

If a failure of main power supply occurs, the BTS uses the storage battery as a back up power supply. The battery capacity, however, is limited, and the BSC reduces the power consumption of the BTS by shutting down some TRXs or decreasing the maximum transmit power of the TRX to prolong the battery discharge time. After the main power supply is restored, the BSC sends a command to all the cells to activate the TRXs. The following measures can be taken to reduce the power consumption in the case of the application of backup power supply: l Shutting down the TRX When the main power supply stops, the BSC sends a SHUTDOWN message to all the BTSs with a TRX whose Shut Down Enabled is set to Enable, instructing the BTS to disable the TRX.
NOTE
Generally, the BCCH TRX is not shut down. In some special scenarios, for example, when transmission is maintained in the case of power failure, the BCCH TRX can be shut down. BTS Power-off Lock BCCH determines whether the BCCH TRX shutdown is allowed.
l
Issue 08 (2011-09-30)
Decreasing the transmit power of the TRX

The BTS decreases the transmit power of the TRX according to the configuration parameters issued by the BSC. When the external power supply for the BTS fails, the BTS gradually decreases the maximum transmit power of all enabled TRXs. If the external power supply for the BTS is restored during the transmit power decreasing process or after the transmit power is decreased to the minimum level, all TRXs resume the maximum transmit power. As some BTSs do not support the TRX the transmit power decrease, the BSC provides two types of Backup Power Saving Method. l BYTRX(Turn off TRX) The BSC is solely responsible for shutting down the TRX in the case of the application of backup power supply. When the external power supply for the BTS fails, the BSC shuts down all TRXs whose Shut Down Enabled is set to Enable. l BYPWR(Reduce Backup Power) Decreasing the transmit power consists of shutting down the TRX and gradually decreasing the transmit power. Based on cell coverage, cell capacity, backup duration, and the sequence of decreasing the transmit power, the Backup Power Saving Policy is categorized into three types: BYCOVER(Cover Priority) The procedure is as follows: 1. 2. The BSC shuts down all TRXs that are preset to support shutdown. After Drop Power Start Time[T1] is started, the BTS decreases the transmit power of all enabled TRXs by one level every Drop Power Time Interval[T3].
NOTE
The step between two adjacent power levels is determined by Drop Power Step. The maximum down step of the transmit power of the BTS is determined by Max Drop Power Threshold.
BYCAP(Capability Priority) The operation is as follows: 1. The BTS decreases the TRXs that are not shut down by a level every Drop Power Time Interval[T3].
NOTE
The step between two adjacent power levels is determined by Drop Power Step. The maximum down step of the transmit power of the BTS is determined by Max Drop Power Threshold.
2.
After Shutdown TRX Start Time[T2] is started, the BSC shuts down all TRXs that are preset to support shutdown.
BYSAVING(Saving Priority) The BSC shuts down all the TRXs that are preset to support shutdown. Meanwhile, the BTS decreases the TRXs that are not shut down by one level every Drop Power Time Interval[T3]
2.50.3.9 Enhanced BCCH Power Consumption Optimization

An MS camping on a neighboring cell may not detect the downlink receive level of the BCCH timeslot in the serving cell. To ensure that the MS can measure the receive level of the serving cell properly, the BCCH TRX transmits signals at the maximum transmit power, regardless of
whether the channels on the BCCH TRX are seized. In this manner, the downlink receive levels measured by the MS camping on the neighboring cell are the same. In this case, the power consumption of the BCCH TRX is the highest among all the BTS devices. To lower the power consumption of the BCCH TRX, Huawei introduces enhanced BCCH power consumption optimization, which is used to decrease the power of the non-BCCH timeslots of BCCH TRX. When Power Derating Enabled is set to Yes, and the current time is between Power Derating Start Time and Power Derating End Time, then the transmit power of the idle channels carried on the non-BCCH timeslots of the BCCH TRX is reduced. The reduction range is determined by Power Derating Range. When Power Derating Active Channel Enabled is set to Yes, the transmit power of the occupied channels of the BCCH TRX is also reduced. If power control is applied to the occupied channel and the reduction degree in power control is smaller than the value of Power Derating Range, then degree in power control is used in power reduction. Otherwise, the reduction range depends on Power Derating Range.
NOTE
When the power of the non-BCCH timeslots of BCCH TRX is reduced, the downlink receive level of the cell measured by the MSs on the neighboring cells may be inaccurate. Therefore, use this feature with caution.
2.50.3.10 Dynamic Cell Power Off
?.1. Overview of Dynamic Cell Power Off

In the multiband network, the GSM900 band is used to meet the requirement for network coverage, and the DCS1800 band is used to absorb network traffic. For details about the multiband network, see 2.57 Multiband Network. To reduce the power consumption of the whole network, the Dynamic Cell Power Off feature is introduced to the multiband network. When the traffic volume is low, the power amplifiers of all the TRXs in the DCS1800 cells are shut down and the GSM900 cells provide services for all subscribers. In this way, the power consumption of the whole network is reduced. When the traffic volume increases, the cells that have been shut down are enabled again, meeting the requirement for traffic volume. The dynamic cell power off feature algorithm consists of dynamic cell power off algorithm and dynamic cell power on algorithm. Dynamic Cell Power Off algorithm is controlled by the Enable Turning Off Cell parameter. When Enable Turning Off Cell is set to Enable, the Dynamic Cell Power Off feature is enabled.
?.2. Dynamic Cell Power Off Algorithm

The dynamic cell power off algorithm consists of dynamic cell power off decision and dynamic cell power off execution.
Dynamic Cell Power Off Decision

When Enable Turning Off Cell is set to ENABLE, the BSC determines whether the cell can be powered off if the current time is between Dyn. Turning Off Cell Start Time and Dyn. Turning Off Cell Stop Time and the current date is not the one when TRX power amplifier intelligent shutdown is prohibited.

NOTE
l The period when TRX power amplifier intelligent shutdown is prohibited is determined by the parameters Prohibit Power Saving Start Month, Prohibit Power Saving Start Day, Prohibit Power Saving End Month, and Prohibit Power Saving End Day. For details, see 2.50.3.1 TRX Power Amplifier Intelligent Shutdown. l The value of Dyn. Turning Off Cell Start Time can be later then Dyn. Turning Off Cell Stop Time. In this case, the period when the cell is allowed to be powered off covers more than one day. For example, if Dyn. Turning Off Cell Start Time is set to 23:00 and Dyn. Turning Off Cell Stop Time is set to 06:00, then the period when the cell is allowed to be powered off covers from 23:00 till 06:00 in the next morning. l During the dates when TRX power amplifier intelligent shutdown is prohibited, the cell is not allowed to be powered off, because the TRX is not allowed to be shut down. For example, if the date when TRX power amplifier intelligent shutdown is set to "2009-10-01" and the time is "23:00 till 06:00", then the cell is not allowed to be powered off from 23:00, 30th, September till 06:00, 2nd, October.
Dynamic cell power off can be enabled when the following requirements are met: l The current time is within the period when the cell is allowed to be powered off and the duration from the current time to Dyn. Turning Off Cell Stop Time is greater than Dyn. Turning Off Cell Protection Time. The number of activated channels in the cell (the number of activated TCHs plus the number of occupied PDCHs) is smaller than or equal to Dyn. Turning Off Cell Busy Channel Num.. The load of the same-coverage cell of the current cell is smaller than Same Coverage Cell Load Threshold.
Dynamic Cell Power Off Execution

The BSC determines whether a cell meets the requirements for dynamic cell power off. If the cell meets the requirements, the BSC releases the occupied channels in the cell before powering off the cell. l l If there is neither a call that has been established nor a call that is being established in the cell, then the BSC powers off the cell. If there is a call that has been established or a call that is being established in the cell, then the BSC performs the following operations: If the call occupies a TCH, the BSC attempts to hand over the call to a neighboring cell. If the call occupies an SDCCH, the BSC waits until the call releases the SDCCH. If the call occupies a PDCH, the BSC releases the PDCH. After the BSC releases all the occupied channels in the cell, the BSC performs dynamic cell power off. Figure 2-165 shows the procedure of dynamic cell power off. Figure 2-165 Procedure of dynamic cell power off
Issue 08 (2011-09-30)
827
1. 2. 3.
The BSC sends a message about dynamic cell power off to the BTS. The BTS shuts down the power amplifiers of the TRX in the cell, and then sends an acknowledgement message to the BSC. After the power amplifiers on all the TRXs in the cell are shut down, the BTS sends a status change report to the BSC, informing the BSC of a successful that the cell is power-off.
After the cell is powered off, the BSC stops sending system messages and paging messages to the BTS, and prohibits any call, for example, incoming cell handover, from accessing the network.
?.3. Dynamic Cell Power On Algorithm

When the traffic volume in the cell increases, the cell that has been powered off should be powered on again to meet the requirements for traffic volume. The dynamic cell power on consists of dynamic cell power on algorithm decision and dynamic cell power on execution.
Dynamic Cell Power On Decision

The BSC powers on the cell that has been shut down if any of the following requirements is met: l l The current system time is not between Dyn. Turning Off Cell Start Time and Dyn. Turning Off Cell Stop Time. The BSC checks the load of the same-coverage cell of the cell that has been powered off every second, and the load of the same-coverage cell is higher than Dyn. Turning On Cell Load Threshold for N times indicated by the Same Coverage Cell Load Stat. Time parameter.
NOTE
Cell A and cell B are in the GSM network. If the coverage area of cell A completely covers cell B, then cell A is the same-coverage cell to cell B. Generally, the same-coverage cell exists in the multiband network.
Dynamic Cell Power On Execution

Once the BSC determines that the cell needs to be powered on, the BSC immediately performs dynamic cell power on. Dynamic cell power on is opposite to dynamic cell power off. Figure 2-166 shows the procedure of dynamic cell power on. Figure 2-166 Procedure of dynamic cell power on
Issue 08 (2011-09-30)
828
1. 2. 3.
The BSC sends a message about dynamic cell power on to the BTS. The BTS powers on all the TRXs in the cell, and then sends an acknowledgement message to the BSC. After the TRX carrying the BCCH in the cell is powered on, the BTS sends a status change report to the BSC, informing the BSC of a sucessful cell power-on.
After the cell is powered on, the BSC starts sending system message and paging message to the BTS, and allows calls to access the network.
?.4. Dynamic Cell Power Off and TRX Power Amplifier Intelligent Shutdown
Dynamic cell power off is the enhancement of TRX power amplifier intelligent shutdown. When the cell is enabled with TRX power amplifier intelligent shutdown, all the TRXs except the one carrying the BCCH can be powered off. That is, the cell can keep providing services for subscribers even if the TRXs are shut down. When the cell is enabled with TRX power amplifier intelligent shutdown, all the TRXs in the cell are shut down, and the cell does not provide services for subscribers.
2.50.4 Parameters
This chapter describes the parameters related to intelligent power consumption decrease For the meaning of each parameter, see Table 2-142. For the default value, value ranges, and MML commands of each parameter, see Table 2-143. Table 2-142 Parameter description (1) Parameter Time When the Function Is Enabled Time When the Function Is Disabled Prohibit Power Saving Start Month Prohibit Power Saving Start Day Prohibit Power Saving End Month Prohibit Power Saving End Day Description This parameter specifies the start time for dynamically enabling the TRX Intelligent Shutdown feature each day. This parameter specifies the time for dynamically disabling the TRX Intelligent Shutdown feature each day. This parameter specifies the start month of a period during which the TRX Intelligent Shutdown feature is disabled. This parameter specifies the start date of a period during which the TRX Intelligent Shutdown feature is disabled. This parameter specifies the end month of a period during which the TRX Intelligent Shutdown feature is disabled. This parameter specifies the end date of a period during which the TRX Intelligent Shutdown feature is disabled. This parameter is set to prevent the BSC from frequently enabling or disabling the TRX. After a TRX is powered on, the BSC is not allowed to disable the TRX within the period of time specified by this parameter.
TRX Power-on Protection Time
Issue 08 (2011-09-30)
829
Parameter
Description This parameter specifies the number of idle channels that should be reserved on a cell after the TRX is shut down. When the number of idle channels on a cell is smaller than this threshold, the BSC6900 enables a TRX. This parameter is used to prevent the impact enabling or disabling delay on the efficiency of channel assignment on the cell that is enabled with the TRX Intelligent Shutdown feature. This parameter specifies whether to enable the TRX Intelligent Shutdown feature. Whether to allow the BSC to dynamically shut down the power amplifier of the TRX according to the traffic. Whether to allow the BSC to dynamically shut down the power amplifier of the TRX according to the traffic. This parameter specifies the frequency hopping mode of a cell. When this parameter is set to "NO_FH", all the TRXs of the cell do not join in frequency hopping. When this parameter is set to "BaseBand_FH", the cell is in baseband frequency hopping mode. In this case, there can be TRXs that do not join in frequency hopping on the cell. When this parameter is set to "RF_FH", the cell is in RF frequency hopping mode. In this case, there can be TRXs that do not join in frequency hopping on the cell. When this parameter is set to "Hybrid_FH", the cell is in hybrid frequency hopping. In this case, some TRXs on the cell must join in baseband frequency hopping, some cells on the cell must join in RF frequency hopping, and some cells on the cell must not join in frequency hopping. This parameter specifies whether to allow the BTS to enable the TRX Intelligent Shutdown on Timeslot Level feature. When this parameter is set to YES and the BTS supports this feature, the BTS will periodically report the number of times that the TRX is shut down on the timeslot level. This parameter is used to enable the Intelligent Combiner Bypass (ICB) function on the BCCH TRX of a cell. This parameter specifies whether to allow the cell to enable the ICB function. When this parameter is set to YES, the TCHs on the non-BCCH TRX are preferentially assigned. In this way, the largest possible number of idle TCHs is reserved on the BCCH TRX, and thus the BCCH TRX enters the ICB mode. This parameter specifies the TRX priority in channel assignment. The smaller this parameter is, the higher the TRX priority is. For two TRXs with other conditions identical, channels on the TRX with higher priority are preferentially assigned.
Reserved TCH Number for PA Turning On Allow Dynamic Shutdown of TRX by BSC Allow Dynamic Shutdown of TRX Allow Dynamic Shutdown of TRX
Frequency Hopping Mode
Allow Turning Off Time Slot
ICB Allowed
TRX Priority
Issue 08 (2011-09-30)
830
Parameter
Description This parameter specifies whether the TRX priority is considered during channel assignment. When the parameter is set to YES, the smaller the parameter "TRX Priority" in the command "SET GTRXDEV" is, the higher priority the TRX is. Under other conditions, channels are preferentially allocated from high-priority TRXs. This parameter specifies whether to enable the TRX Working Voltage Adjustment feature. When this parameter is set to YES, the BSC6900 supports the feature where the power amplifier can use different working voltages in different TRX modulation modes. Power type managed by the PMU Transmit power level of the TRX. If this parameter is set greater, the transmit power of the TRX is lower. If this parameter is set to 0, the TRX transmits signals at the highest power. At each level, the power is decreased by 2 dB. This parameter specifies whether the multi-carrier transceiver unit supports the Multi-Carrier Intelligent Voltage Regulation feature. When this parameter is set to YES, the multi-carrier transceiver unit automatically regulates its working voltage according to the power requirements of a service. When this parameter is set to NO, the multi-carrier transceiver unit works at a fixed working voltage.This parameter applies only to BTS3036, BTS3036A, DBS3036, BTS3900 GSM, BTS3900L GSM, BTS3900A GSM, DBS3900 GSM, BTS3900E base stations. For other base stations, this parameter is not displayed and cannot be configured (the fixed value is Null). When this parameter is set to YES, The BSC6900 preferentially uses the TRX with good power-saving performance according to the TRX power priority reported by the BTS. Smaller priority value indicates better power saving quality. If the priority is of a great value, the BTS closes TRXs late. This parameter specifies whether the BTS is allowed to enable the PSU Smart Control feature. When this parameter is set to YES, the BTS automatically enables or disables the PSU according to the traffic volume to improve the efficiency of the PSU. When this parameter is set to NO, the PSUs of the BTS are all working. The following types of BTS support the PSU Smart Control feature: BTS3012AE BTS3900A, BTS3900, DBS3900, and BTS3900L: support the PSU Smart Control feature through the matching APM30. This parameter specifies whether to enable the Power Optimization Based on Channel Type feature. The working voltage of the TRX varies with the modulation mode of the channel. When this parameter is set to YES, the TRX adopts the working voltage according to the modulation mode of the dynamic PDCH.
Allocation TRX Priority Allowed
Adjust Voltage Power Type
Power Level
PA Intelligent Adjust Voltage
Power Priority Allowed
PSU Turning Off Enable
PDCH Power Saving Enable
Issue 08 (2011-09-30)
831
Parameter
Description This parameter specifies whether the BSC6900 automatically shuts down the power amplifier of the TRX to save power when the BTS is powered by batteries after a power failure. This parameter specifies whether the BSC is allowed to shut down the BCCH TRX that is configured as "Shut Down Enabled" to save power after the BSC receives a power failure message from the BTS. When this parameter is set to Yes, the BSC shuts down all the TRXs that are configured as "Shut Down Enabled", including the BCCH TRX, after receiving a power failure message from the BTS. When this parameter is set to No, the BSC shuts down only the non-BCCH TRXs that are configured as "Shut Down Enabled" after receiving a power failure message from the BTS. This parameter specifies the method of saving the BTS backup power. When this parameter is set to "Turn off TRX", the BSC preferentially shuts down some TRXs when the BTS experiences a power failure. When this parameter is set to "Reduce Backup Power", the BSC saves the power according to the configured "Backup Power Saving Policy" when the BTS experiences a power failure. This parameter specifies the backup power saving policy of the BTS. When this parameter is set to "Cover Priority", the BTS shuts down some TRXs, waits for a certain period of time, and then decreases the power of the BCCH TRX. When this parameter is set to "Capability Priority", the BTS decreases the power of the BCCH TRX, waits for a certain period of time, and then shuts down some TRXs. When this parameter is set to "Saving Priority", the BTS shuts down some TRXs and meanwhile decreases the power of the BCCH TRX. This parameter specifies the delay time before decreasing the power of the TRXs. This parameter specifies the interval at which the power of a TRX is continually decreased. This parameter specifies the step by which the power of a TRX is decreased at a time. This parameter specifies the largest step of each TRX power reduction. This parameter specifies the delay time before shutting down the TRXs when the BTS experiences a power failure. This parameter specifies whether to enable the Enhanced BCCH Power Consumption Optimization feature. Generally, the BCCH TRX transmits signals at the maximum transmit power. When this parameter is set to YES, the BSC6900 is allowed to reduce the transmit power of the non-BCCH idle timeslots on the BCCH TRX.
Shut Down Enabled
BTS Power-off Lock BCCH
Backup Power Saving Method
Backup Power Saving Policy Drop Power Start Time [T1] Drop Power Time Interval[T3] Drop Power Step Max Drop Power Threshold Shutdown TRX Start Time[T2]
Power Derating Enabled
Issue 08 (2011-09-30)
832
Parameter Power Derating End Time Power Derating Start Time
Description This parameter specifies the end time of the period during which the power of the non-BCCH timeslots on the BCCH TRX is derated. This parameter specifies the start time of the period during which the power of the non-BCCH timeslots on the BCCH TRX is derated.
This parameter specifies the range of power derating over the nonPower Derating Range BCCH timeslots on the BCCH TRX. Power Derating Active Channel Enabled When this parameter is set to YES, the BSC6900 is allowed to reduce the transmit power of the non-BCCH timeslots on the BCCH TRX. This parameter specifies whether to enable the Dynamic Cell Power Off feature. When this parameter is set to ENABLE, the BSC can disable the cell within the period of time specified by "TURNOFFCELLSTRTIME" and "TURNOFFCELLSTPTIME"; When this parameter is set to DISABLE, the BSC will never disable the cell; When this parameter is set to SLEEP, the BSC will disable the cell unconditionally within "TURNOFFCELLSTRTIME" and "TURNOFFCELLSTPTIME",and enable the cell unconditionally within the other time.Currently, this parameter can be set to SLEEPING only for the BTS3900E. For other base stations, this parameter cannot be set to SLEEPING. This parameter specifies the start time of a period during which the cell is disabled. This parameter specifies the end time of a period during which the cell is disabled. This parameter specifies a period of time during which a cell cannot be enabled or disabled to prevent frequent cell enabling or disabling operations. That is, after a cell is enabled, it cannot be disabled within the period of time specified by this parameter; after a cell is disabled, it cannot be enabled within the period of time specified by this parameter. If the number of channels (including PDCH and TCH) occupied on a cell that can be disabled is lower than this threshold, the procedure for disabling the cell can be triggered. A cell that can be disabled is allowed to be disabled only when the load of the same coverage cell is lower than this threshold for a period. When the load of the same coverage cell is higher than this threshold for a period, the disabled cell is enabled. The BSC6900 checks the load of the same coverage cell of the target cell once a minute. When the number of times in which the load of the same coverage cell is lower than "Same Coverage Cell Load Threshold" is equal to the value of this parameter, the target cell is disabled.
Enable Turning Off Cell Dyn. Turning Off Cell Start Time Dyn. Turning Off Cell Stop Time
Dyn. Turning Off Cell Protection Time Dyn. Turning Off Cell Busy Channel Num. Same Coverage Cell Load Threshold Dyn. Turning On Cell Load Threshold
Same Coverage Cell Load Stat. Time
Issue 08 (2011-09-30)
833
Table 2-143 Parameter description (2) Parameter Time When the Function Is Enabled Time When the Function Is Disabled Defa ult Value GUI Value Range Actual Value Range 00:00~23: 59 00:00~23: 59 JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC Un it MML Command SET BSCDSTPA (Optional) SET BSCDSTPA (Optional) Impact
None
hour, min
No ne No ne
BSC
None
hour, min JAN(Jan.), FEB(Feb.), MAR(Mar.), APR(Apr.), MAY(May), JUN(Jun.), JUL(Jul.), AUG(Aug.), SEP(Sep), OCT(Oct.), NOV(Nov.), DEC(Dec)
BSC
Prohibit Power Saving Start Month Prohibit Power Saving Start Day
None
No ne
ADD BSCDSTPAD ATE (Mandatory) ADD BSCDSTPAD ATE (Mandatory)
BSC
None
1~31 JAN(Jan.), FEB(Feb.), MAR(Mar.), APR(Apr.), MAY(May), JUN(Jun.), JUL(Jul.), AUG(Aug.), SEP(Sep), OCT(Oct.), NOV(Nov.), DEC(Dec)
1~31 JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
No ne
BSC
Prohibit Power Saving End Month Prohibit Power Saving End Day
None
No ne
ADD BSCDSTPAD ATE (Mandatory) ADD BSCDSTPAD ATE (Mandatory)
BSC
None
1~31
1~31
No ne
BSC
Issue 08 (2011-09-30)
834
Parameter TRX Power-on Protection Time Reserved TCH Number for PA Turning On Allow Dynamic Shutdown of TRX by BSC Allow Dynamic Shutdown of TRX Allow Dynamic Shutdown of TRX
Defa ult Value
GUI Value Range
Actual Value Range
Un it
MML Command SET BSCDSTPA (Optional) SET GCELLOTHE XT(Optional) SET BSCDSTPA (Optional) SET GCELLBASIC PARA (Optional) SET GTRXDEV (Optional)
Impact
300
60~3600
60~3600
s No ne
BSC
0~16
0~16
Cell
NO
NO(No), YES (Yes)
NO, YES
No ne
BSC
YES
NO(No), YES (Yes)
NO, YES
No ne
Cell
NO
NO(No), YES (Yes) NO_FH(No frequency hopping), BaseBand_FH (Baseband frequency hopping), RF_FH(RF frequency hopping), Hybrid_FH (Hybrid frequency hopping) NO(No), YES (Yes) NO(NO), YES (YES), NULL (NULL)
NO, YES
No ne
TRX
Frequency Hopping Mode Allow Turning Off Time Slot
NO_F H
NO_FH, BaseBand _FH, RF_FH, Hybrid_F H
No ne No ne
SET GCELLHOPTP (Optional) SET GCELLHOPQ UICKSETUP (Mandatory) SET BSCDSTPA (Optional) SET GCELLBASIC PARA (Optional)
Cell
NO
NO, YES
BSC
ICB Allowed
NO
NO, YES, NULL
No ne
Cell
Issue 08 (2011-09-30)
835
Parameter
Defa ult Value
GUI Value Range L0(Level0), L1(Level1), L2(Level2), L3(Level3), L4(Level4), L5(Level5), L6(Level6), L7(Level7) NO(No), YES (Yes)
Actual Value Range
Un it
MML Command
Impact
TRX Priority Allocation TRX Priority Allowed
L0
L0, L1, L2, L3, L4, L5, L6, L7
No ne No ne
SET GTRXDEV (Optional) SET GCELLCHMG AD(Optional) SET GCELLBASIC PARA (Optional)
TRX
YES
NO, YES
Cell
Adjust Voltage
YES
NO(No), YES (Yes) POWER_48_2 4(48/24 Power Module), POWER_240_ 24(240/24 Power Module)
NO, YES
No ne
Cell
Power Type
POW ER_4 8_24
POWER_ 48_24, POWER_ 240_24
No ne No ne No ne No ne No ne No ne
SET BTSPMUBP (Optional) SET GTRXDEV (Optional) SET BTSOTHPAR A(Optional) SET GCELLCHMG AD(Optional) SET BTSOTHPAR A(Optional) SET GCELLSOFT (Optional) SET GTRXDEV (Optional)
BTS
Power Level PA Intelligent Adjust Voltage Power Priority Allowed PSU Turning Off Enable PDCH Power Saving Enable
0~13 NO(NO), YES (YES) NO(No), YES (Yes) NO(NO), YES (YES) NO(No), YES (Yes) DISABLE (Disable), ENABLE (Enable)
0~13
TRX
NO
NO, YES
BTS
YES
NO, YES
Cell
None
NO, YES
BTS
NO
NO, YES DISABL E, ENABLE
Cell
Shut Down Enabled
ENAB LE
No ne
TRX
Issue 08 (2011-09-30)
836
Parameter
Defa ult Value
GUI Value Range
Actual Value Range
Un it
MML Command SET BTSLOCKBC CH (Mandatory)
Impact
BTS Power-off Lock BCCH
NO
NO(No), YES (Yes) BYTRX(Turn off TRX), BYPWR (Reduce Backup Power) BYCOVER (Cover Priority), BYCAP (Capability Priority), BYSAVING (Saving Priority)
NO, YES
No ne
BTS
Backup Power Saving Method
BYTR X
BYTRX, BYPWR
No ne
SET BTSBAKPWR (Mandatory)
BTS
Backup Power Saving Policy Drop Power Start Time[T1] Drop Power Time Interval [T3] Drop Power Step Max Drop Power Threshold Shutdown TRX Start Time[T2] Power Derating Enabled Power Derating End Time
BYC OVER
BYCOVE R, BYCAP, BYSAVI NG
No ne
SET BTSBAKPWR (Optional) SET BTSBAKPWR (Optional) SET BTSBAKPWR (Optional) SET BTSBAKPWR (Optional) SET BTSBAKPWR (Optional) SET BTSBAKPWR (Optional) SET GCELLOTHE XT(Optional) SET GCELLOTHE XT(Optional)
BTS
0~12
0~12
BTS
10
1~60
1~60
min
BTS
2~10
2~10
dB
BTS
10
0~20
0~20
dB
BTS
0~12
h No ne No ne
BTS
NO
NO, YES 00:00~23: 59
Cell
None
hour, min
Cell
Issue 08 (2011-09-30)
837
Parameter Power Derating Start Time Power Derating Range Power Derating Active Channel Enabled
Defa ult Value
GUI Value Range
Actual Value Range 00:00~23: 59 0~3, Step: 0.2
Un it
MML Command SET GCELLOTHE XT(Optional) SET GCELLOTHE XT(Optional)
Impact
hour, min
No ne
Cell
0~15
dB
Cell
YES
NO(No), YES (Yes) DISABLE (Disable), ENABLE (Enable), SLEEPING (Sleeping)
NO, YES DISABL E, ENABLE, SLEEPIN G
No ne
SET GCELLOTHE XT(Optional)
Cell
Enable Turning Off Cell Dyn. Turning Off Cell Start Time Dyn. Turning Off Cell Stop Time Dyn. Turning Off Cell Protection Time Dyn. Turning Off Cell Busy Channel Num. Same Coverage Cell Load Threshold Dyn. Turning On Cell Load Threshold
None
No ne
SET GCELLDYNT URNOFF (Mandatory) SET GCELLDYNT URNOFF (Optional) SET GCELLDYNT URNOFF (Optional) SET GCELLDYNT URNOFF (Optional) SET GCELLDYNT URNOFF (Optional) SET GCELLDYNT URNOFF (Optional) SET GCELLDYNT URNOFF (Optional)
Cell
HOUR, MINUTE
00:00~23: 59
No ne
Cell
HOUR, MINUTE
00:00~23: 59
No ne
Cell
0~255
0~255
min
Cell
0~8
0~8
No ne
Cell
50
0~100
0~100
per cent
Cell
80
0~100
0~100
per cent
Cell
Issue 08 (2011-09-30)
838
Parameter Same Coverage Cell Load Stat. Time
Defa ult Value
GUI Value Range
Actual Value Range
Un it
MML Command SET GCELLDYNT URNOFF (Optional)
Impact
1~16
1~16
No ne
Cell
2.50.5 Counters
2.50.6 Glossary

2.51 IP BSS
2.51.1 Introduction
2.51.1.1 Scope
This document describes the protocol stacks and network topologies on the BSS-related interfaces.

It is assumed that users of this document are familiar with GSM basics and have a working knowledge of GSM telecommunication. This document is intended for: l
Issue 08 (2011-09-30)
Personnel working on Huawei GSM products or systems

System operators who need a general understanding of this feature

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the IP BSS feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The IP BSS is split into two documents: IP Transport Architecture Description and IP BSS Parameter Description. The structure of the documents is optimized. Parameter Change None. None.
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table.
Issue 08 (2011-09-30)
840
Change Description The added contents are listed as follows: l IP transport technologies. l Ater over IP. l IEEE1588 V2 clock synchronization solution.
Parameter Change The added parameters are listed as follows: l Subrack No. l Slot No. l Check Index l IP MUX Type l Max subframe length[byte] l Maximum Frame Length[byte] l FPTIMER[ms] l Service Type l Adjacent Node ID l Sender UDP MUX Mode l Receive UDP MUX Mode l MP type l MC PRI number l MP flake size l Borrow DevIP l Peer IP address l PPP Mux l Check type l Min interval of BFD packet send [ms] l Min interval of BFD packet receive [ms] l detect multiplier of BFD packet l Whether affect the port swapping l ARP packet time-out[100ms] l ARP packet resend times l Inter Sync Period[Day] l Inter Sync Start Time[Hour] l Inter Sync Start Time[Minute] l Clock Protocol Type
l A over IP, Abis over IP, Gb over IP, Dependency, and Maintenance Information are modified. Editorial change None.
None.
None.
Issue 08 (2011-09-30)
841
2.51.2 Overview
IP BSS is a radio transmission solution with which the signaling and traffic signals on the A, Abis, Gb, and Ater interfaces are transmitted by using IP technology. IP BSS has the following advantages: l l l l The major advantages of IP transmission are high bandwidth and low cost, thus making it easy for telecom operators to introduce new services as required. IP transmission caters to the requirements of high-bandwidth data services and keeps pace with the evolution to all-IP, thus reducing the cost of network evolution. Both the transport network and the operation and maintenance (OM) network of signaling and traffic signals adopt IP transmission. Thus, the network OM cost is reduced. The packet switching technique of the IP network is used to multiplex transmission resources. Compared with TDM transmission, IP transmission utilizes the transmission resources more effectively and helps reduce the capital expenditure (CAPEX) and operating expense (OPEX) of the bearer network. After IP transmission is applied on the interfaces, resource pool can be implemented in the MSC, SGSN, and BSC, thus improving the network reliability and enhancing the telecom operator's brand recognition. The network element (NE) resources in the pool are shared. This increases the NE usage, reduces the telecom operator's investment in the MSC, SGSN, and BSC, and facilitates the configuration and OM. After IP transmission is applied on the A interface, the MGW takes over the TC function, which was performed by the BSC earlier. IP transmission performs voice coding/decoding one time less than TDM transmission. After TrFO is introduced, IP transmission performs voice coding/decoding two times less than TDM transmission. A over IP maintains pace with the trend of GSM/UMTS convergence. IP BSS keeps pace with the trend towards common transmission and bearer of the 2G and 3G networks.
The extensive use of IP technology has made the IP equipment affordable and the IP bandwidth easily accessible. The implementation of IP BSS maintains pace with the trend towards flat network, thus reducing the network construction cost and facilitating the network maintenance. Figure 2-167 shows the network topology of IP BSS.
Issue 08 (2011-09-30)
842
Figure 2-167 Network topology of IP BSS
According to the interface, IP BSS is classified into the following: l A over IP In A over IP mode, signaling and speech signals are transmitted over the A interface by using the IP technology. On the A interface, the signaling plane uses the SCCP/M3UA/ SCTP/IP protocol stack and the user plane uses the RTP/UDP/IP protocol stack for transmission. The function of transcoding from TRAU to PCM is taken over by the MGW. l Abis over IP In Abis over IP mode, signaling and speech signals are transmitted over the Abis interface by using the IP technology. On the Abis interface, the signaling plane uses the LAPD over UDP/IP protocol stack and the user plane uses the PTRAU over UDP/IP protocol stack for transmission. l Gb over IP In Gb over IP mode, signaling and PS signals are transmitted over the Gb interface by using IP technology. The BSSGP/NS/UDP/IP protocol stack is used on the Gb interface for transmission. l Ater over IP
Issue 08 (2011-09-30)
843
In Ater over IP mode, speech signals are transmitted over the Ater interface by using the IP technology. On the Ater interface, the user plane uses IP over PPP for transmission, and the signaling plane uses the traditional TDM mode for transmission. According to the network planning, different network topologies are applied on the interfaces to meet the actual requirements. The active/standby, load sharing, and link detection mechanisms are adopted to ensure the networking reliability. In addition, various QoS mechanisms are employed to achieve high QoS in IP transmission.

2.51.3.1 Protocol Stacks
?.1. Protocol Stack on the A Interface
A over IP supports two transmission modes: IP over FE/GE and IP over E1/T1/Ch-STM-1. The IP protocol version adopted is IPv4. On the A interface, the signaling plane uses the M3UA/SCTP/IP protocol stack to carry signaling, and the user plane uses the RTP/UDP/IP protocol stack to carry speech signals, as shown in Figure 2-168. Figure 2-168 Protocol stack for A over IP
?.2. Protocol Stack on the Abis Interface

Abis over IP supports two transmission modes: IP over FE/GE and IP over E1/T1/Ch-STM-1. The IP protocol version adopted is IPv4.
After Abis over IP is applied, the signaling plane uses the LAPD over UDP/IP protocol stack to carry signaling and the user plane uses the PTRAU over UDP/IP protocol stack to carry speech signals, as shown in Figure 2-169. Figure 2-169 Protocol stack for Abis over IP
?.3. Protocol Stack on the Gb Interface

Gb over IP supports only IP over FE/GE and does not support IP over E1/T1/Ch-STM-1. The IP protocol version adopted is IPv4. In Gb over IP, the physical layer uses the FE/GE transmission , the sub NS layer of the NS protocol complies with the IP protocol, and the upper layer of the NS protocol complies with the BSSGP protocol, as shown in Figure 2-170.
Issue 08 (2011-09-30)
845
Figure 2-170 Protocol stack for Gb over IP
?.4. Protocol Stack on the Ater Interface

Ater over IP supports IP over PPP over E1/T1/Ch-STM-1 and does not support IP over FE/GE. The IP protocol version adopted is IPv4. Currently, the Huawei Ater interface supports IP over Ch-STM-1 and does not support IP over E1/T1. In Ater over IP, the physical layer uses the Ch-STM-1 optical transmission, the user plane uses the PTRAU/UDP/IP protocol stack, and the signaling plane uses the LAPD/HDLC/TDM protocol stack. Figure 2-171 shows the protocol stack on the Ater interface. Figure 2-171 Protocol stack on the Ater interface
Issue 08 (2011-09-30)
846

?.1. Network Topologies on the A Interface
A over IP supports three network topologies: layer 2 network topology, layer 3 network topology, and direct connection.
Layer 2 Network Topology

The layer 2 network topology is applicable only to the FE/GE transmission mode. Figure 2-172 shows the layer 2 network topology (through switches). Figure 2-172 Layer 2 network topology
In the layer 2 network topology, it is recommended that the Ethernet ports work in active/standby mode to ensure network reliability. To configure the Ethernet ports to work in active/standby mode, enter the ADD ETHREDPORT command, and then specify Subrack No., Slot No., and Port No. for both the active and standby boards. The layer 2 network topology has the following advantages: l l l l
Issue 08 (2011-09-30)
Provides a large-capacity bandwidth and a reliable transmission bearer Meets the requirements for the bearer network in the future GSM evolution Reduces the impact of data burst on the network Supports flexible networking on a large scale
Layer 3 Network Topology

The layer 3 network topology is applicable only to the FE/GE transmission mode. Figure 2-173 shows the layer 3 network topology (through routers). Figure 2-173 Layer 3 network topology
To save the FE/GE port resources and facilitate operation and maintenance (OM), the A interface board supports multiple IP addresses on a single port. One FE/GE port can be configured with a maximum of six IP addresses. This is mainly applicable to the layer 3 (IP layer) network topology. In this network topology, the routers separate the signaling from the traffic data by transmitting them by using different IP addresses. Thus, the signaling and the traffic data are distributed to different virtual private networks (VPNs) on the IP network, as shown in Figure 2-174. Figure 2-174 Layer 3 network topology with multiple IP addresses on one port
Issue 08 (2011-09-30)
848
In the layer 3 network topology, it is recommended that the Ethernet ports work in active/standby mode to ensure network reliability. The layer 3 network topology has the following advantages: l l l l Provides a large-capacity bandwidth and a reliable transmission bearer Meets the requirements for the bearer network in future GSM evolution Reduces the impact of data burst on the network Supports flexible networking on a large scale
Direct Connection
There are two direct connection scenarios: IP over FE/GE and IP over E1/T1/Ch-STM-1. In the case of IP over E1/T1/Ch-STM-1, it is recommended that the BSC and the CN not be connected through routers. Figure 2-175, Figure 2-176, and Figure 2-177 show the network topologies for direct connections. Figure 2-175 Network topology for direct connection (IP over FE/GE)
Figure 2-176 Network topology for direct connection (IP over E1/T1/Ch-STM-1)
Issue 08 (2011-09-30)
849
Figure 2-177 Network topology for direct connection through PDH/SDH network (IP over E1/ T1/Ch-STM-1)
In the case of direct connection in IP over E1/T1/Ch-STM-1, it is recommended that the interface boards work in active/standby mode to ensure network reliability. The network topology for direct connection has the following advantages: l l High reliability, low network construction cost, and easy maintenance High QoS and easy-to-control call admission
?.2. Network Topologies on the Abis Interface

The network topologies for IP over FE/GE on the Abis interface support three transmission modes: MSTP, layer 2/3 (IP) data network, and satellite/microwave link. In these transmission modes, the BSC provides FE/GE ports and the BTS provides FE ports. The network topologies for IP over E1/T1 on the Abis interface support cascaded and noncascaded BTSs. In the case of cascaded BTSs or non-cascaded BTSs, the BSC provides E1/T1 ports, and the BTS provides E1/T1 ports.
NOTE
The Abis interface supports IP over E1/T1/Ch-STM-1. Currently, the BTS does not support IP over ChSTM-1; therefore, only IP over E1/T1 is described in this document.
Network Topologies for IP over FE/GE

l MSTP-based network topology (see Figure 2-178) Figure 2-178 MSTP-based network topology
In the case of the MSTP-based network topology, it is recommended that the Ethernet ports work in active/standby mode to ensure reliability.
This network topology has the following advantages: It is applicable to the network operators that have established an SDH or MSTP network. The BTS provides a transmission bandwidth of up to 100 Mbit/s over the FE port. This facilitates BTS upgrade and capacity expansion and enables quick deployment of data services for the BTS. The VC trunk function provided by the MSTP network enables two VC trunk links to be established between the BTS and the BSC, one transmitting real-time traffic data and the other transmitting non-real-time traffic data. l Network topologies based on layer 2 data network and layer 3 (IP layer) data network (see Figure 2-179 and Figure 2-180)
Figure 2-179 Network topology based on layer 2 data network
Figure 2-180 Network topology based on layer 3 data network
In the case of the network topologies based on layer 2 data network and layer 3 data network, it is recommended that the Ethernet ports work in active/standby mode to ensure reliability. These two network topologies have the following advantages: The data network can provide large-capacity bandwidth and reliable transmission for the Abis interface.
The data network supports the evolution from the GSM network to the IP network. l Satellite/Microwave-link-based network topology In the case of the network topologies based on satellite/microwave links, it is recommended that the Ethernet ports work in active/standby mode to ensure reliability. The star network topology of satellite earth stations (station + substation) can be used. In this network topology, multiple BTSs can be connected to the BSC through one station, as shown in Figure 2-181. Figure 2-181 Satellite-link-based star network topology
The mesh network topology of satellite earth stations can be used because it is flexible. See Figure 2-182. Figure 2-182 Satellite-link-based mesh network topology
The network topology of microwave stations can be used, as shown in Figure 2-183.
Issue 08 (2011-09-30)
852
Figure 2-183 Microwave-link-based network topology
Network Topologies in IP over E1/T1

l Network topologies for non-cascaded BTSs Figure 2-184 shows the network topology for IP over E1/T1 (direct connection between BTS and BSC). When the BTS is connected to the BSC through the SDH/PDH network, they are regarded as directly connected. Figure 2-184 Network topology for IP over E1/T1 (direct connection between BTS and BSC)
Figure 2-185 shows the network topology for IP over E1/T1 (connection of BTS and BSC through a router).
Issue 08 (2011-09-30)
853
Figure 2-185 Network topology for IP over E1/T1 (connection of BTS and BSC through router)
In Abis over IP mode, it is recommended that the BTS connect to the BSC through FE ports. If the BTS does not provide FE ports, it is recommended that the BTS be connected to the router through E1/T1 ports and then the router be connected to the BSC through FE/ GE ports. l Network topologies for cascaded BTSs Figure 2-186 shows the network topology for cascaded BTSs. Figure 2-186 Network topology for IP over E1/T1
The PPP links are segmented between BTSs. The intermediate BTSs route and forward the traffic of lower-level BTSs.
Currently, the hybrid cascading network topology of PPP and TDM is not supported.
?.3. Network Topologies on the Gb Interface

After Gb over IP is applied, the signals between the BSC and the SGSN are transmitted over the IP network where routers are used to provide layer 3 routing services for the BSC and SGSN. As a result of IP application, the bandwidth on the Gb interface increases and the OM cost decreases. In the case of Gb over IP, it is recommended that the Ethernet ports work in active/standby mode to ensure reliability. Figure 2-187 shows the network topology for Gb over IP. Figure 2-187 Network topology for Gb over IP
?.4. Network Topologies on the Ater Interface

Figure 2-188 shows the network topology for Ater over IP. Figure 2-188 Network topology for Ater over IP
The speech services between the MPS/EPS and the TCS are transmitted through IP over PPP. The SDH/PDH network continues to be the transport network in TDM mode. The signaling links and OM links between the MPS/EPS and the TCS continue to be carried in TDM mode. After Ater over IP is applied, the PPP compression and Ater Mux technologies are adopted, thus improving the bandwidth efficiency and reducing the OM cost of transmission over the Ater interface.
2.51.4 Parameters
This chapter describes the parameters related to IP BSS. For the meaning of each parameter, see Table 2-144. For the default value, value ranges, and MML commands of each parameter, see Table 2-145.
Table 2-144 Parameter description (1) Parameter Slot No. Description Number of the slot for the BSC board that connects to the DXX. Number of the E1 port. For the BTS3012, BTS3012AE, and BTS3012 II, the number can be a value from 0 to 7. For other BTSs, the number can be a value from 0 to 3. Number of the subrack.
Port No. Subrack No.
Table 2-145 Parameter description (2) Parameter Defaul t Value GUI Value Range Actu al Valu e Ran ge Uni t MML Command Im pa ct
Slot No. Port No.
None None
0~27 0~7
0~27 0~7
Non e Non e
ADD DXXCONNECT (Mandatory) STR TRANSPERFTST (Mandatory)
BS C6 900 No ne
Issue 08 (2011-09-30)
856
Parameter
Defaul t Value
GUI Value Range
Actu al Valu e Ran ge
Uni t
MML Command
Im pa ct
SWP BRD(Mandatory) STR BKP(Mandatory) CMP BRDAREA (Optional) ULD LOGTOOMU (Mandatory) STR CPUUSAGETST (Mandatory) ULD RSTINFO (Mandatory) ADD BRD(Mandatory) SET PWRPARA (Mandatory) SET FANSPEED (Mandatory) SET SCUPORT (Mandatory) ADD EMU (Mandatory) SET ALMPORT (Mandatory) DLD TCFILE (Mandatory) SET XPUPORT (Mandatory) ADD XPUVLAN (Mandatory) SET MPUBIND (Mandatory) LOD FAN(Optional) SET DPUBRDTYPE (Mandatory) CMP BRDVER (Optional) SYN BRDAREA (Optional) Subrack No. None 0~11 0~11 Non e COL FAMLOG (Mandatory) No ne
Issue 08 (2011-09-30)
857
Parameter
Defaul t Value
GUI Value Range
Uni t
MML Command
Im pa ct
CMP LICENSE (Optional) FMT DATA(Optional) CMP TBLDATA (Mandatory) SET CFGDATAINEFFECTIVE(Mandatory) SET CFGDATAEFFECTIV E(Optional) SET MSPCMD (Mandatory) SET E1T1LOP (Mandatory) LOP E1T1(Mandatory) STR E1T1TST (Mandatory) SET OPTLOP (Mandatory) PING IP(Mandatory) TRC IPADDR (Mandatory) SWP ETHPORT (Mandatory) SET QUEUEMAP (Mandatory) SET E1T1(Mandatory) SET MSP(Mandatory) ADD TSCROSS (Mandatory) ADD DEVIP (Mandatory) ADD IPRT(Mandatory) SET OPT(Mandatory) SET COPTLNK (Mandatory) SET ETHPORT (Mandatory)
Parameter
Defaul t Value
GUI Value Range
Uni t
MML Command
Im pa ct
ADD ETHREDPORT (Mandatory) ADD PPPLNK (Mandatory) ADD MPGRP (Mandatory)
2.51.5 Counters
2.51.6 Glossary

2.52 IP Transport Architecture Description

2.52.1 Introduction
2.52.1.1 Scope
This document describes the IP transport architecture of the BSC6900. The architecture enables IP transport on the interfaces of the GSM and UMTS networks. This document also describes the related transport protocols, IP QoS mechanisms, transmission efficiency improvement mechanisms, and network reliability.
Read the following documents for more information about the IP transport architecture: l l l IP RAN Parameter Description: provides the overview, network topologies, interface protocols, and parameters of the IP RAN feature for the UMTS network. IP BSS Parameter Description: provides the overview, network topologies, interface protocols, and parameters of the IP BSS feature for the GSM network. Co-IP Transmission Parameter Description: provides the overview, network topologies, interface protocols, and parameters of the Iub and Abis Co-IP Transmission feature.

This document is intended for: l l Persons who dimension and plan the GSM or UMTS transport network Persons who configure and manage the GSM or UMTS transport network
It is assumed that the reader has a basic knowledge of transport networks and data communications, as well as a basic knowledge of the WCDMA RAN and GSM BSS.

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the IP transport architecture description feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01 (2009-09-30)
2.52.2 Overview
2.52.2.1 Introduction
With the development and wide use of IP technology, the application of IP technology to wireless communications networks has become a necessary trend. In 3GPP R5, IP transport is introduced to the radio access network (RAN) of UMTS, and the corresponding feature is called IP RAN.
From 3GPP R4 onwards, IP transport is gradually introduced to the RAN of GSM, and the corresponding feature is called IP BSS. If the IP technology is applied in the RAN, the data bearer capability of the transport network is drastically improved, reducing the capital expenditure (CAPEX) and operating expense (OPEX). In addition, the IP transport network can carry the data of multiple radio access technology (RAT) networks, which meets the long-term evolution requirements of operators.
2.52.2.2 IP Transport Architecture

The BSC6900 is a multi-mode base station controller for the GSM and UMTS networks and it supports the IP transport architecture, as shown in Figure 2-189 The architecture provides IP transport bearer services for the GSM BSS and UMTS RAN. Transport Resource Management (TRM) provides transmission resource management functions to ensure transmission quality and improve transmission resource utilization. For details about TRM, see the TRM Parameter Description. Figure 2-189 IP transport architecture
The IP transport architecture consists of the following functional modules: l IP transport protocols To support IP RAN and IP BSS, the BSC6900 uses a set of transport protocols. These protocols have a bottom-up design and implement the IP transmission bearers in the RAN, as defined in 3GPP technical specifications. For details, see 2.52.3 Overview of IP Transport Architecture. l IP transmission efficiency improvement The multiplexing and header compression technologies reduce the packet header overhead. In this manner, the utilization of IP transmission bandwidth is increased. For details, see 2.52.4 IP Transmission Efficiency Improvement. l IP clock synchronization Layer 1 of the IP network cannot provide clock synchronization. Instead, clock synchronization solutions, such as clock over IP, IEEE1588 V2, or synchronous Ethernet, can provide. For details, see 2.52.5 IP Clock Synchronization. l IP QoS The BSC6900 provides the following mechanisms to ensure IP quality of service (QoS): admission control, overload and congestion control, backpressure-based congestion control, Differentiated Service Code Point (DSCP) configuration, and Virtual Local Area
Network (VLAN) priority configuration. For details about these mechanisms, see the Transmission Resource Management Feature Parameter Description. l IP fault detection The BSC6900 provides the following mechanisms to detect transmission faults and performance deterioration between the transmitting and receiveing ends and in the intermediate network: ETH Operation, Administration, and Maintenance (ETH OAM), Address Resolution Protocol (ARP), Bidirectional Forwarding Detection (BFD), and IP performance monitoring (IP PM). For details, see 2.52.6 Fault Detection Technologies. l Network reliability The BSC6900 provides the following mechanisms to improve the reliability of the IP transport network: board backup, Ethernet port backup, Ethernet port load sharing, and Ethernet link aggregation. For details, see 2.52.7 Networking Reliability. l IP DHCP IP Dynamic Host Configuration Protocol (DHCP) is used for the Iub and Abis interfaces. It enables the BSC6900 to automatically allocate network addresses and establish OM channels for NodeBs for BTSs. For details, see 2.52.8 IP DHCP.
2.52.3 Overview of IP Transport Architecture

To support IP RAN and IP BSS, the BSC6900 uses a set of transport protocols, as shown in Figure 2-190. These protocols have a bottom-up design and implement the IP transmission bearers in the RAN, as defined in 3GPP technical specifications.
NOTE
The application layer shown in Figure 2-190 refers to the radio network layer of the interfaces in GSM and UMTS networks. It is not described in this document.
Figure 2-190 IP transport protocol architecture
Issue 08 (2011-09-30)
862
The IP transport architecture consists of three parts: l Fundamental protocol part The fundamental protocol part contains the common underlying protocols for the control plane and user plane. It is the basis for the communications between the BSC6900 and the peer end. The fundamental protocol part consists of physical layer protocols, data link layer protocols, Internet Protocol (IP), and User Datagram Protocol (UDP). The data link layer protocols include Ethernet protocols and derived VLAN, Point-to-Point Protocol (PPP) and derived PPPMux, as well as Multilink-PPP (MLPPP) and derived Multi-Class PPP (MCPPP). l Control plane part The control plane part and the fundamental protocol part work together to provide transport bearer services for the radio network layer of the control planes of the GSM and UMTS interfaces. The control plane consists of the Stream Control Transmission Protocol (SCTP), MTP3User Adaptation Layer (M3UA), Signaling Connection Control Part (SCCP), Link Access Procedure on the D channel (LAPD), as well as Mapping and Transfer between LAPD entity and Service entity (MTLS). l User plane part The user plane part and the fundamental protocol part work together to provide transport bearer services for the radio network layer of the user planes of the GSM and UMTS interfaces. The user plane consists of the Real-time Transport Protocol (RTP) and the User plane of GPRS Tunneling Protocol (GTP-U). The following sections describe the related transport protocols in the IP transport architecture.
2.52.3.2 Data Link Layer Protocols

The data link layer is the second layer of the TCP/IP protocol stack. Based on the physical layer, the data link layer provides reliable data transmission for the network layer. The data link layer protocols contained in the IP transport architecture are classified into the following two types: l l Local area network (LAN) protocols: Ethernet and VLAN. Wide area network (WAN) protocols: PPP, PPPMux, MLPPP, and MCPPP.
?.1. Ethernet
Currently, Ethernet is the most widely used data link layer technology for a LAN. The BSC6900 supports Ethernet over the Iub, Iur, and Iu interfaces of a UMTS network or over the Abis, A, and Gb interfaces of a GSM network.
Frame Format
Ethernet has many frame formats. The Ethernet II frame format is defined in RFC894, as shown in Figure 2-191. The IEEE 802.3 frame format is defined in RFC1042, as shown in Figure
2-192. The main difference between the two frame formats is the last field of the frame header: The last field of the Ethernet II frame header is Type whereas the last field of the IEEE 802.3 frame header is Length. The BSC6900 supports the transmission of frames in Ethernet II format and the reception of frames in IEEE 802.3 or Ethernet II format. Figure 2-191 Ethernet II frame format
Figure 2-192 IEEE 802.3 frame format
The fields shown in Figure 2-191 and Figure 2-192 are described as follows: l l l l l Destination MAC address: specifies the Media Access Control (MAC) address of the device that receives frames. Source MAC address: specifies the MAC address of the device that transmits frames. (Ethernet II) Type: indicates upper-layer protocol type carried by an Ethernet II frame. For example, 0x0800 signifies an IP payload. (IEEE 802.3) Length: indicates the size of the payload in the Ethernet frame. Data: indicates the upper-layer protocol data encapsulated in an Ethernet frame. The upperlayer protocol data is usually an IP packet. The size of the data field is limited. The minimum size of the Payload field is 46 bytes and the maximum size (that is, the size of the maximum transmission unit, MTU) is 1,500 bytes. if the size of the actual data is smaller than 46 bytes, the Payload field is padded. If the size of the upper-layer protocol packet exceeds the size of the MTU, the packet is segmented. FCS: indicates the frame check sequence field Verified using the cyclic redundancy check (CRC). If the receiving end detects an error during the frame check, the frame is discarded.
The related parameters of the BSC6900 are as follows: l

Issue 08 (2011-09-30)
Board type and Port type: specify the type of an interface board and a port respectively.
l l
Auto negotiation: specifies whether an Ethernet port supports auto-negotiation. MTU[Byte]: The default value of the MTU is 1,500 bytes.
MAC Address
In the OSI reference model, the data link layer consists of the LLC sublayer and the MAC sublayer. The MAC address is also called physical address, hardware address, or link address. It is used at the MAC sublayer to uniquely identify a device. The MAC address is burned into the hardware before delivery. During communications, the physical layer identifies a host by its MAC address. A 48-bit MAC address is usually represented by 12 hexadecimal digits separated by dots. The MAC address consists of two parts: l l Manufacturer identifier: first 24 bits, assigned by the Ethernet address management organization Serial number: last 24 bits, assigned by the manufacturer
Figure 2-193 shows an example of the MAC address. Figure 2-193 Example of the MAC address
?.2. VLAN
VLAN is a data exchange technology derived from the traditional LAN. VLAN allows LAN devices to be logically grouped into multiple network segments to implement virtual workgroups. The hosts within the same VLAN can communicate with each other through VLAN switches. The hosts in different VLANs are separated from each other and they communicate with each other only through routers. A VLAN is a broadcast domain, that is, a host in a VLAN can receive the broadcast packets from the other hosts in the same VLAN but cannot receive any broadcast packets from other VLANs. VLAN provides the following advantages: l l l Suppresses broadcast storms Improves transmission security Provides differentiated services
Frame Format
The VLAN frame format is defined in IEEE 802.1Q. In comparison with a standard Ethernet frame, a four-byte VLAN tag is added to the VLAN frame header, as shown in Figure 2-194.
Figure 2-194 VLAN frame format
The fields of the VLAN tag are described as follows: l l l TPID: tag protocol identifier. If a VLAN frame complies with IEEE 802.1Q, TPID is permanently set to 0x8100. VLAN priority: specifies the priority of a VLAN frame. The priority ranges from 0 to 7. Ethernet provides differentiated services according to the VLAN priority field. Canonical Format Indicator (CFI): specifies the format of a frame that is exchanged between the bus Ethernet and a Fiber Distributed Data Interface (FDDI) or between the bus Ethernet and a token ring network. VLAN ID: specifies the ID of a VLAN to which a frame is to be sent. Each VLAN is identified by a VLAN ID.
The related parameters of the BSC6900 are as follows: l VLAN ID: specifies the identifier of a VLAN. The VLAN ID mapping relation ships should be preconfigured for the BSC6900 to determine the ID of a VLAN frame. The BSC6900 supports two VLAN ID configuration modes based on the VLAN ID mapping relationship: Configuring VLAN ID according to the mapping relationship between the next hop IP address and the VLAN ID The related parameters are Next Hop IP address and VLAN ID . Configuring VLAN ID according to the mapping relationship among the SCTP link, IP path, and VLAN ID The related parameters are SCTP link No., IP path ID, and VLAN ID . l VLAN Priority : specifies the priority of a VLAN frame.
The VLAN ID configuration modes supported by the BSC6900 interfaces are described as follows: l Interfaces of a GSM network The A and Abis interfaces support both of the VLAN ID configuration modes.
The Gb interface supports only configuring VLAN ID configuration according to the mapping relationship between the next hop IP address and the VLAN ID. The Ater interface does not support VLAN. l Interfaces of a UMTS network The Iub, Iu, and Iur interfaces support both of the VLAN ID configuration modes.
?.3. Point-to-Point Protocol

PPP is a data link layer protocol, which is commonly used in a WAN. PPP is designed to encapsulate and transmit datagrams of various network layer protocols over point-to-point links. These network layer protocols include IP, Internetwork Packet Exchange (IPX), and AppleTalk. The BSC6900 supports the PPP protocol on the Iub, Iu, and Iur interfaces of a UMTS network and on the Abis, A, and Ater interfaces of a GSM network.
Frame Format
The PPP frame format is defined in RFC1661, as shown in Figure 2-195. Figure 2-195 PPP frame format
The fields of a PPP frame are described as follows: l l l l l Flag: indicates the start or end of a frame. This field is set to a fixed value. Address: This field is set to a fixed value. Control: This field is set to a fixed value. Protocol: specifies the type of the protocol encapsulated by the Information field. For example, 0x0021 indicates that an IP datagram is encapsulated. Information (also known as payload): contains the upper-layer protocol datagram encapsulated by a PPP frame. The size of the Information field varies and the maximum size is specified by the maximum receive unit (MRU). The MRU is negotiable during the PPP link establishment. If the MRU is not negotiated, the default size is 1,500 bytes. FCS: frame check sequence field.
The related parameters of the BSC6900 are as follows: l l Board type: specifies the type of the interface board that carries a PPP link. E1T1 port No. and Bearing time slot: specify the port number and the timeslot number respectively of the E1/T1 link that carries the PPP link. The two parameters should be specified only when the PEUa, POUa, or POUc board is used. A PPP link can be carried on only one of the E1/T1 links of the BSC6900. It can be carried on all the timeslots of an E1/T1 link, that is, timeslot 1 through timeslot 31 of an E1 link, or timeslot 1 through
Issue 08 (2011-09-30)
timeslot 24 of a T1 link, with the bandwidth of each timeslot being 64 kbit/s. A PPP link can also be carried on some of the timeslots of an E1/T1 link. In this case, it is called Fractional IP. After being transmitted through a timeslot cross connection device on the intermediate transport network, the PPP link can be carried on only one of the E1/T1 links. l l PPP link No.: specifies the number of a PPP link. It uniquely identifies a PPP link on an interface board. Local IP address, Peer IP address, and Subnet mask: specify the local IP address, peer IP address, and subnet mask respectively of a PPP link. The device IP address can also be used as the local IP address of a PPP link to save the IP address resources. To use the device IP address as the local IP address, set the Borrow DevIP parameter to Yes and then specify the Borrowed device IP address parameter. CRC check mode: specifies the size of the FCS field.
PPPMux
PPPMux is a technology through which multiple PPP payloads (also called PPPMux subframes) are assembled into a single PPP frame (also called a PPPMux frame) to reduce the overhead per PPP subframe and improve the bandwidth utilization of PPP links. PPPMux is applicable to scenarios where short packets such as speech and data are transmitted over low-speed links. For long packets, PPPMux cannot improve the transmission efficiency to a large extent but it increases the transmission delay. Therefore, using PPPMux to transmit long packets is not recommended. The PPPMux frame format is defined in RFC3153. The Information field of a PPPMux frame consists of a one-byte PPPMux identifier (set to 0x59) and multiple subframes. The subframes are separated by separators. The BSC6900 supports PPPMux on the Iub, Iur, and Iu interfaces of a UMTS network and on the Ater interface of a GSM network. The related parameters of the BSC6900 are as follows: l l PPP mux: specifies whether a PPP link supports the PPPMux function. PPP mux max sub-frame length: specifies the maximum size of a PPPMux subframe. If the size of a PPPMux subframe exceeds the value of this parameter, the subframe is directly transmitted without being multiplexed. PPP mux max mux-frame length: specifies the maximum size of a PPPMux frame. PPP mux framing out-time[us]: specifies the maximum time waiting for multiplexing. If the waiting time exceeds the value of this parameter, the PPPMux frame is transmitted without being added more PPPMux subframes.
l l
?.4. Multilink-PPP
MLPPP (also called MP) is an extension of the PPP protocol. It is a data link layer protocol that exists between PPP and the network layer.
Data Transmission Mechanism

MLPPP is a technology through which multiple PPP physical links (also called MLPPP sublinks) are combined into one logical link. MLPPP fragments network layer packets and then transmits the fragmented packets over MLPPP sublinks. In this manner, the bandwidth, data transmission rate, and throughput increase. In addition, the transmission delay is reduced.
Figure 2-196 shows the MLPPP data transmission mechanism. Figure 2-196 MLPPP data transmission mechanism
Frame Format
The MLPPP frame format is defined in RFC1990. The MLPPP frame has two formats: long sequence number and short sequence number, as shown in Figure 2-197 and Figure 2-198 respectively. Figure 2-197 Long sequence number
Issue 08 (2011-09-30)
869
Figure 2-198 Short sequence number
The fields of the MLPPP frame header are described as follows: l l B: Beginning fragment bit (one bit). This field indicates whether an MLPPP frame is the beginning fragment of a PPP frame. E: Ending fragment bit (one bit). This field indicates whether an MLPPP frame is the last fragment of a PPP frame.
The related parameters of the BSC6900 are as follows: l MLPPP group: Board type: specifies the type of the interface board that carries an MLPPP link. MP Group No.: specifies an MLPPP group within an interface board. MP type: specifies whether the type of an MLPPP group is MLPPP or MCPPP. Local IP address, Subnet mask, and Peer IP address: specifies the local IP address, subnet mask, and peer IP address respectively of an MLPPP group. The device IP address can also be used as the local IP address of an MLPPP group to save the IP address resources. To use the device IP address as the local IP address, set the Borrow DevIP parameter to Yes and then specify the Borrowed device IP address parameter. MP flake size: specifies the size of an MLPPP fragment. MLPPP fragments network layer packets according to the value of this parameter. Both MLPPP and MCPPP support the fragmentation function. l MLPPP link: E1T1 port No.. and Bearing time slot: specifies the E1/T1 port number and the bearer timeslot respectively of the PEUa, POUa, or POUc board that carries a PPP link. PPP sub-link No.: identifies an MLPPP link on an interface board. MP Group No.: specifies the MLPPP group to which an MLPPP link belongs. CRC check mode: specifies the size of the FCS field.
Issue 08 (2011-09-30)
870
Multi-Class PPP
MCPPP (also called MC) is an extension of MLPPP. Compared with MLPPP, MCPPP provides service priorities. High-priority packets can interrupt the transmission of low-priority packets. The MCPPP frame format is defined in RFC2686. When adding an MLPPP group on the BSC6900 side, set the MP type parameter to MLPPP or MCPPP. l If this parameter is set to MCPPP, the MLPPP group transmits data to the peer end according to the MCPPP protocol. In addition, the MC PRI number parameter needs to be specified, which indicates the number of priorities supported by an MCPPP group. If this parameter is set to MLPPP, the MLPPP group transmits data to the peer end according to the MLPPP protocol.
The default setting, MCPPP, is recommended.
2.52.3.3 IP
IP is a primary protocol at the network layer. The IP protocol supports a universal packet format, that is, IP datagram. The IP datagram masks the differences in implementation at the data link layer and enables network interworking. Other protocols, such as TCP, UDP, Internet Control Message Protocol (ICMP), and Internet Group Management Protocol (IGMP) in the TCP/IP protocol stack, transmit data in the IP datagram format. The IP protocol is an unreliable and connectionless data packet protocol. It provides functions such as IP addressing, routing, IP datagram fragmentation, and IP datagram reassembly.
?.1. Datagram Format

At the transmission end, the IP layer receives the source data packet (for example, a UDP message) from the upper layer. Then, the IP layer determines whether to fragment the data packet according to the MTU of the data link layer. The data after being fragmented is called segment. Data packets or segments are encapsulated into IP datagrams as payload in a fixed format. Later, IP datagrams are transmitted to the data link layer and then transmitted over over the Internet. At the reception end, the IP layer receives data from the data link layer, reassembles the payload to obtain the original data packet, and then transmits the data to the upper layer for further processing. An IP datagram is divided into two pieces: the header and the payload. The header contains addressing and control fields, whereas the payload carries the data to be sent over the Internet. Figure 2-199 shows the IP datagram format. Figure 2-199 IP datagram format
Issue 08 (2011-09-30)
871
The fields of the IP datagram are described as follows: l l Version: contains the IP version number. For example, 4 indicates IPv4. Internet Header Length (IHL): specifies the size of an IP datagram header. The minimum size of the IP datagram header is 20 bytes (excluding the size of the Options field), and the maximum size is 60 bytes (including the size of the Options field). TOS: specifies the service type. Of the eight bits occupied by the TOS field, three bits specify the priority (obsolete now) of the IP datagram, four bits specify the optional service type (minimum delay, maximum throughput, maximum reliability, and minimum cost), and one bit is permanently set to 0. Total Length: specifies the total size of an IP datagram. Identification: identifies a datagram sent by a host. The value of this field is common to all fragments belonging to a particular message. This field is used by the reception end to reassemble messages without accidentally mixing fragments from different messages. Flags: specifies whether the current data is the last fragment of an IP datagram and whether fragmentation is allowed. This field is used to fragment and reassemble datagrams. Fragment Offset: specifies the position of a fragment in an IP datagram. This field is used to fragment and reassemble datagrams. TTL (Time to Live): specifies how long an IP datagram is allowed to exist on a network, in terms of router hops. Each router decreases the value of the TTL field by one before transmitting it. When the value of TTL becomes zero, the IP datagram is discarded. Meanwhile, an ICMP packet is sent to the transmission end. Protocol: specifies the upper-layer protocol type carried in an IP datagram, which can be TCP, UDP, ICMP, or IGMP. Header Checksum: contains the checksum on the header of an IP datagram. Source IP Address: specifies the source IP address of an IP datagram. Destination IP Address: specifies the destination IP address of an IP datagram. Options: specifies whether measures such as error correction, measurement, and security are taken. The field size varies from 1 byte to 40 bytes, depending on the selected items. Padding may be added to ensure that the field size is a multiple of four. Data: specifies the data to be transmitted in an ip datagram. The data can beeither an entire higher-layer message or a message fragment.
l l
l l l
l l l l l
?.2. IP Address and Routing

The following describes IP address types, subnet mask, and IP routing of a BSC6900.
IP Address
An IP address uniquely identifies a host or router port on the Internet. An IP address consists of the network part and the host part. The network part uniquely identifies a network or a subnet, and the host part uniquely identifies a host on a subnet. In the IP transport architecture, four IP address types are used, as described in Table 2-146.
Issue 08 (2011-09-30)
872
Table 2-146 Four IP address types IP Address Eth Port IP address PPP link/MLPPP link IP address Description Each Ethernet port must be configured with at least one IP address. Each PPP link/ MLPPP link must be configured with one IP address, which can be the device IP address. (Optional) Device IP address indicates the IP address of an IP interface board. Several Ethernet ports can be bound to form an Eth Trunk port. One Eth Trunk port must be configured with at least one IP address.
Device IP address Eth Trunk IP address
NOTE The Eth Port IP address, PPP link IP address, and MLPPP link IP address are collectively called the port IP address. CAUTION All the IP addresses of the BSC6900 cannot be on the same network segment.
Figure 2-200 shows the distribution of four types of IP addresses on an IP interface board. Figure 2-200 Distribution of four types of IP addresses on an IP interface board
The four IP address types use the standard IP addresses defined in the IP protocol. The IP protocol also defines some special IP addresses. For example, an IP address with all 0s in the host part indicates a network segment IP address. which identifies a subnet. All the hosts on the same subnet have the same subnet mask and network segment IP address.
Subnet Mask
A network device uses a subnet mask to differentiate between the network part and the host part in an IP address. The subnet mask has the same structure as an IP address. All 1s are the network part and all 0s are the host part.
Generally, the length of a subnet mask is used to indicate the subnet mask. The length of a subnet mask is in decimal form and represents the number of 1s in the subnet mask. For example, the length of the subnet mask 11111111.11111111.11111111.11000000 is 26. The subnet mask can also be represented in the "IP address/length of subnet mask" form. For example, "10.161.161.7/26" means that the length of the subnet mask is 26 and the IP address is 10.161.161.7. The related parameters of the BSC6900 are described as follows: l l Subnet mask: specifies the subnet mask at the local end. This parameter is used to configure the device IP address and port IP address at the local end. Peer subnet mask: specifies the subnet mask at the peer end. This parameter is used to configure the IP address at the peer end.
IP Routing
IP Routing is an umbrella term for a set of protocols that determine the path that data follows to travel across multiple networks from its source to its destination. The related parameters of the BSC6900 are as follows: l l Destination IP address: specifies the destination IP address, which can be a host IP address or a network segment IP address. Destination address mask: specifies the destination subnet mask. The AND operation is performed on the destination IP address and the subnet mask. The operation result determines the scope of the destination IP addresses. Forward route address: specifies the IP address of the next hop of a route. Priority: specifies the priority of a route. When multiple routes to the same subnet are configured, these routes can be classified into the following types according to the setting of the Priority parameter: Active and standby routes: indicate routes that can reach the same subnet but have different priorities. Equivalent routes: indicate routes that can reach the same subnet and have the same priority. In load sharing mode, equivalent routes must be configured. If multiple routes to the same subnet are configured, the system uses the route whose subnet mask is long by default. If two routes have subnet masks of the same length, the system uses the route with a higher priority by default .
l l
?.3. Layer 2 Networking and Layer 3 Networking

According to the data switching technology, IP networking is classified into layer 2 networking and layer 3 networking.
Layer 2 Networking
In layer 2 networking, all the network devices are located on the same network segment, data is switched by a layer 2 device (for example, a LAN switch), and IP routes do not need to be configured. Figure 2-201 shows layer 2 networking.
Figure 2-201 Layer 2 networking
In layer 2 networking, VLAN can be used to separate broadcast domains, suppress broadcast storm, improve transmission security, and provide differentiated services.
Layer 3 Networking
In layer 3 networking, the network devices are located on different network segments, data is switched by a layer 3 device (for example, a router), and IP routes must be configured. Figure 2-202 shows layer 3 networking. Figure 2-202 Layer 3 networking
2.52.3.4 User Datagram Protocol

User Datagram Protocol (UDP) is used to transmit user data stream. UDP operates over the network layer and is an unreliable and connectionless transport layer protocol. UDP is mainly used to perform conversion between network data streams and UDP datagrams. At the transmission end, UDP encapsulates network data streams into datagrams and then transmits the datagrams. At the reception end, UDP de-encapsulates datagrams to obtain the original data.
UDP Datagram Format

Figure 2-203 shows the UDP datagram format. Figure 2-203 UDP datagram format
The fields of the UDP datagram are described as follows: l l l l Source Port and Destination Port: specify the type of upper-layer application at the source end and destination end respectively. Length: indicates the number of bytes in the UDP header and Data fields. Checksum: contains the checksum on the UDP header and Data fields. Data: specifies the data to be received by the destination application. The size of this field is variable.
IP Path
In the IP transport architecture, UDP data streams are carried over IP paths. An IP path is a logical entity that is established for the UDP transmission resources of devices. It enables two communication ends to provide admission bandwidth, flow control, and differentiated services. The related parameters of the BSC6900 are as follows: l Local IP address (IPADDR): specifies the IP address of an IP path on the BSC6900 side. This IP address is used for data transmission on the user plane. The local IP address can be the port IP address or device IP address. Peer IP address (PEERIPADDR): specifies the IP address of an IP path at the peer end. This IP address is used for data transmission on the user plane. The peer IP address can be a host IP address or a network segment IP address, as shown in Figure 2-204. Peer subnet mask (PEERMASK):: specifies the subnet mask at the peer end. The default value of this parameter is 255.255.255.255, which indicates that there is only one peer IP address for an IP path. If there are multiple peer IP addresses for an IP path, the value of this parameter needs to be configured. IP path type (PATHT): specifies the type of an IP path. IP paths of different types can be configured between both parties in a communication to carry the service data of different types. For details about the mapping between the IP path types and the service types, see TRM Parameter Description.
Issue 08 (2011-09-30)
Forward Bandwidth (TXBW): specifies the admission bandwidth of an IP path in the transmission direction. For details, see the Transmission Resource ManagementFeature Parameter Description. Backward Bandwidth (RXBW): specifies the admission bandwidth of the IP path in the reception direction. For details about the admission bandwidth, see the Transmission Resource ManagementFeature Parameter Description.
Figure 2-204 shows an example, in which the peer IP addresses of an IP path are network segment IP addresses. Figure 2-204 Example of setting the peer IP addresses of an IP Path
In this example, an IP path is configured between the BSC6900 and the SGSN, and the IP path has three IP addresses on the SGSN side. Peer IP address and Peer subnet mask of the IP path need to be set to the network segment IP address and the subnet mask respectively, for example, 20.10.10.0/28. When planning the subnet at the peer end, reserve some IP addresses so that no more configuration is required on the BSC6900 side when some new IP addresses are added to the subnet.
2.52.3.5 Real-Time Transport Protocol (RTP)

RTP is specially designed for transmitting Internet multimedia data. RTP is usually used in combination with UDP to transmit real-time data. UDP is responsible for transmitting datagrams, but it does not ensure the timing sequence of datagram transmission. RTP adds fields such as Timestamp and Sequence Number to the datagrams to provide timing information and implement streaming synchronization. RTP, however, does not provide reliable transmission mechanisms, flow control, or congestion control. Figure 2-205 shows the RTP datagram format. Figure 2-205 RTP datagram format
Issue 08 (2011-09-30)
877
The fields of the RTP datagram are described as follows: l l l l l l l l V: specifies the RTP version. P: specifies whether padding is added to datagram tail. X: specifies whether an Extension header exists between the standard header and the payload data. CC: specifies the number of CSRC identifiers that follow a fixed header. M: specifies a marker. PT: specifies the payload type. The transmission end uses this field to indicate the coding scheme used at the reception end. Sequence Number: specifies the number of an RTP datagram. The Sequence Number is increased by one each time an RTP datagram is sent. Timestamp: specifies the time when an RTP datagram is sent. The Timestamp and Sequence Number fields are used by the reception end to sequentially play back received RTP datagrams. SSRC Identifier: identifies the synchronization source. CSRC Identifier: identifies the contributing source of the payload in an RTP datagram. Payload: specifies the payload.
l l l
2.52.3.6 Stream Control Transmission Protocol (SCTP)

SCTP provides connection-oriented reliable transmission between two SCTP end by establishing an SCTP association. SCTP is a transport layer protocol designed to transmit signaling. SCTP meets the requirements of high-performance transmission by implementing the following mechanisms: l l l l l l Multi-homing Multi-streaming Initiation protection Message framing Configurable unordered delivery Graceful shutdown
An SCTP link is a connection between two SCTP end. It is identified by the combination of the local IP address, local SCTP PORT No. peer SCTP PORT No., and peer IP address. The following describes the SCTP link transmission mode and multi-homing.
SCTP Link Transmission Mode

Two ends of an SCTP link work in server/client mode. The client sends a link initiation request, and the server starts the listening port to listen to the request from the client. On the Iub interface, the BSC6900 must be configured as the server of an SCTP link. On the Iu and Iur interfaces, it is recommended that the BSC6900 be configured as the client. On the A interface, the BSC6900 is always configured as the client and therefore manual configurations are not required.
The BSC6900 parameter related to SCTP is Signalling link mode, which can be set to SERVER or CLIENT.
Multi-Homing
In the case of multi-homing, both ends of an SCTP link are bound with multiple IP addresses. Therefore, redundancy transmission paths exist between the two SCTP ends. If a path is faulty, data can be transmitted on another path. This improves the fault tolerance capability. On the BSC6900 side, a single SCTP link is bound with a maximum of two IP addresses. If an SCTP link is bound with two IP addresses on the BSC6900 side, the peer end must also be bound with two IP addresses. On the BSC6900 side, a single SCTP link is bound with a maximum of two IP addresses. If an SCTP link is bound with two IP addresses on the BSC6900 side, the peer end must also be bound with two IP addresses. The BSC6900 supports SCTP multi-homing on the Iub, Iu, and Iur interfaces of a UMTS network and on the A interface of a GSM network. The related parameters of the BSC6900 are as follows: l Local IP address and port First local IP address: When SCTP multi-homing is not used, this parameter specifies the IP address of an SCTP link on the BSC6900 side. When SCTP multi-homing is used, this parameter in combination with First destination IP address specifies the main path of an SCTP link. Second local IP address: specifies the second IP address of an SCTP link on the BSC6900 side. This parameter is set only when SCTP multi-homing is used. Local SCTP port No.: specifies the local port number of an SCTP link. This parameter is set only when the BSC6900 functions as the client. When the BSC6900 functions as the server, the two local IP addresses correspond to the same SCTP port. , which is specified by NBAP service listening port No. on the Iub interface and by M3UA serviceM3UA service listening port No. on the Iu and Iur interfaces.. l Peer IP address and port First destination IP address: When SCTP multi-homing is not used, this parameter specifies the peer (that is, NodeB in the case of Iub) IP address of an SCTP link. When SCTP multi-homing is used, this parameter in combination with First local IP address specifies the main path of an SCTP link. Second destination IP address: specifies the second peer IP address of an SCTP link. This parameter is set only when SCTP multi-homing is used. Destination SCTP port No.: specifies the peer port number of an SCTP link. l Cross IP address available flag: specifies whether the cross path of an SCTP link is available.
Figure 2-206 shows SCTP multi-homing.
Issue 08 (2011-09-30)
879
Figure 2-206 SCTP multi-homing
As shown in Figure 2-206, the SCTP link between the server and the client adopts multi-homing, and each end point has two IP addresses. Thus, there are a maximum of four paths: Path 1 (between IP 1 and IP 3), Path 2 (between IP 1 and IP 4), Path 3 (between IP 2 and IP 3), and Path 4 (between IP 2 and IP 4). Assume that IP 1 and IP 3 are the first IP addresses at both ends of the SCTP link. Then, Path 1 is the main path, Path 2 and Path 3 are the cross paths, and Path 4 is the standby path. Generally, SCTP messages are transmitted over the main path. If the main path is unavailable, SCTP end points detect whether other paths are available by sending heartbeat messages. If another path is available, the SCTP messages are transmitted over that path. The Cross IP address available flag parameter specifies whether the cross paths are available. If this parameter is set to UNAVAILABLE, the cross paths are disabled and only the main and standby paths can be used.
2.52.3.7 MTP3-User Adaptation Layer (M3UA)

The M3UA protocol is the user adaptation protocol for MTP3 or MTP-3b. It provides primitivebased communication services for MTP3 users on an IP network and for MTP3 users (on the signaling gateway) at a network edge. M3UA enables the interworking between TDM-based SS7 and IP. M3UA provides connectionless services. The data configurations for M3UA and MTP-3b are similar. The local and destination entities of M3UA can be considered as the originating signaling point (OSP) and destination signaling point (DSP) respectively of SS7. The related parameters of the BSC6900 are as follows: l l l Local entity No.: identifies a local entity. Destination entity No.: identifies a destination entity. Local entity type and Destination entity type: specify the local entity type and the destination entity type respectively. The local entity type can be M3UA_ASP or M3UA_IPSP. The destination entity type can be M3UA_SGP, M3UA_IPSP, M3UA_SS7SP, or M3UA_SP. For details about ASP, SGP, IPSP, and SS7SP, see RFC4666. Routing Context: specifies the route context of the M3UA local entity in the ADD M3LE command or the route context of the M3UA destination entity in the ADD M3DE command. For details, see RFC4666. Signalling link set index: uniquely identifies a signaling link set within the BSC6900. Signalling link mask: specifies the signaling link mask corresponding to an M3UA link set. It is used for the M3UA link load sharing. In the value of this parameter, the number
l l
Issue 08 (2011-09-30)
of 1s (represented by n) determines the maximum number (2n) of links for load sharing. For example, B0000 indicates that a maximum of one (20) link is used for load sharing; B0001 and B1000 indicate that a maximum of two (21) links are used for load sharing. The additional links are not used for load sharing. The AND operation between this value and the value of the Signalling route mask parameter in the ADD N7DPC command must be equal to 0. l Traffic mode: specifies the traffic mode of an M3UA link set. Currently, the value of this parameter can be M3UA_OVERRIDE_MOD or M3UA_LOADSHARE_MOD. For details about the two modes, see RFC4666. Work mode: specifies the working mode of an M3UA link set. The value of this parameter can be M3UA_ASP or M3UA_IPSP. For details about ASP and IPSP, see RFC4666. PENDING timer: specifies the value of the PENDING timer for an M3UA link set. Signaling link ID: uniquely identifies a signaling link within a signaling link set (specified by the Signalling link set index parameter). SCTP link No.: specifies the SCTP link that carries an M3UA link. Signalling link priority: specifies the priority of a signaling link. Value 0 indicates the highest priority. Initial bearing traffic active tag: specifies the initial bearer flag of an M3UA link. The value of this parameter can be M3UA_MASTER_MOD or M3UA_SLAVE_MOD. For details about the bearer flag, see RFC4666. Route priority : specifies the priority of a route. Value 0 indicates the highest priority.
l l l l l l
2.52.3.8 Signaling Connection Control Part

SCCP provides additional functions for MTP-3b and M3UA. It enables the SS7 signaling points to transmit circuit-related messages and non-circuit-related messages. SCCP supports connection-oriented and connectionless services and provides address resolution. In the IP transport architecture, SCCP is used on the Iu, Iur, and A interfaces to transmit RANAP, RNSAP, and BSSMAP messages respectively. Messages related to a single user are transmitted in connection-oriented mode, and other messages are transmitted in connectionless mode. SCCP performs addressing according to the Destination Point Code (DPC) and the Subsystem Number (SSN). Both communication parties use the SSN to identify the upper-layer application, such as RANAP or RNSAP. The parameters of the BSC6900 are as follows: l OSP index : uniquely identifies an OSP in an SS7 signaling network. For the BSC6900 GU, two OSPs can be configured. One OSP is configured for the GSM BSC and the other for the UMTS RNC. DSP index : uniquely identifies a DSP in an SS7 signaling network.
2.52.4 IP Transmission Efficiency Improvement

2.52.4.1 Overview
With the development of communication services and an increase in device capacity, more and more data flow is transmitted over each interface. This results in a requirement for transmission efficiency improvement to increase the bandwidth utilization.
The BSC6900 provides IP transmission efficiency improvement mechanisms based on protocol characteristics, as shown in Figure 2-207. Figure 2-207 IP transmission efficiency improvement mechanisms
The following sections describe the IP transmission efficiency improvement mechanisms.
2.52.4.2 Frame Protocol Multiplexing

Frame Protocol Multiplexing (FP-Mux) encapsulates multiple FP PDUs into one FP-Mux packet, reducing the UDP/IP/L2/L1 header transmission overhead and resulting in improved transmission efficiency. FP-Mux has the following characteristics: l The implementation is simple. FP-Mux requires the support of only the transmission end and the reception end. The intermediate transport equipment does not need to support FPMux. FP-Mux significantly improves the transmission efficiency but increases the transmission delay. FP-Mux is not an open standard.
l l
FP-Mux applies to the user plane of the IP-based Iub interface.
?.1. Datagram Format

Figure 2-208 shows the format of an IP datagram that uses FP-Mux. The multiplexed IP datagram has the following characteristics: l l l The FP PDUs in one FP-Mux frame share the IP and UDP headers and must have the same source IP address, destination IP address, and DSCP. One FP-Mux frame can carry the data for multiple users. The FP-Mux header specifies the size and owner of each FP PDU. The UDP header contains a fixed source UDP port number. The number indicates that this packet is an FP-Mux frame and therefore requires demultiplexing at the reception end.
Issue 08 (2011-09-30)
Figure 2-208 FP-Mux IP packet format
The fields of an FP-Mux IP packet are described as follows: l l l User Identifier: specifies the owner of an FP PDU. Length Indicator: specifies the size of an FP PDU. FP PDU: is the payload of an FP subframe.
FP-Mux significantly improves the transmission efficiency. use the speech service as an example. The size of each speech datagram is 41 bytes, and the total size of the IP and UDP headers is 28 bytes. If FP-Mux is not used, the size of the IP datagram is 69 bytes (28 bytes + 41 bytes). If FP-Mux is used, the transmission efficiency is improved, because the ratio of the UDP data size to the IP datagram size increases from 60% to 70% or even to 90% when the number of FP subframes in the FP-Mux frame increases. The ratio equals (41 x n) divided by (28 + 41 x n), where n is a natural number. However, when the size of the IP datagram increases, the transmission delay also increases. The related parameters of the BSC6900 are as follows: l l l l IP MUX Type: specifies whether the FP-Mux function is enabled on the BSC6900 side. When this parameter is set to FPMUX, the FP-Mux function is enabled. Max subframe length[byte]: specifies the maximum size of an FP subframe. If the size of an FP frame exceeds the value of this parameter, the FP subframe is not multiplexed. Maximum Frame Length[byte]: specifies the maximum size of an FP-Mux frame. Maximum Delay Time[ms]: specifies the maximum time that the system waits before sending the multiplexed data. If the waiting time exceeds the value of this parameter, the system immediately sends the multiplexed data to prevent a too long delay.
?.2. FP-Mux Principles

The prerequisites for enabling the FP-Mux function are as follows: l l Both the BSC and the BTS support the FP-Mux function. The data related to the FP-Mux function is configured on both the BSC and BTS sides.
Figure 2-209 shows the working principles of FP-Mux at the transmission end.
Figure 2-209 Buffering and multiplexing performed at the transmission end
The transmission end buffers the user data (FP PDUs) and encapsulates the data into FP-Mux frames according to specific multiplexing conditions. Then, the FP-Mux frame is sent to the UDP layer. The multiplexing conditions are as follows: l l l If the size of an FP PDU exceeds Max subframe length[byte], the FP PDU is not multiplexed but directly sent to the UDP layer. If the size of an FP-Mux frame reaches Maximum Frame Length[byte], the FP-Mux frame is sent to the UDP layer without multiplexing more FP PDUs. If the value of the timer reaches Maximum Delay Time[ms], the FP-Mux frame is sent to the UDP layer without multiplexing more FP PDUs.
After receiving the FP-Mux frames in sequence, the reception end demultiplexes the frames to obtain the original data and perform service processing.
2.52.4.3 Abis-Mux and Ater-Mux

The datagram format and working principle of Abis-Mux and Ater-Mux are the same as those of FP-Mux. For details, see 2.52.4.2 Frame Protocol Multiplexing. The difference among Abis-Mux, Ater-Mux, and FP-Mux is that they apply to different interfaces. Abis-Mux applies only to the user plane of the IP-based Abis interface. Ater-Mux is applicable only to the user plane of the IP-based Ater interface. The BSC6900 parameters related to the Abis-Mux function are as follows: l l IP MUX Type: specifies whether the Abis-Mux function is enabled on the BSC6900 side. When this parameter is set to AbisMux, the Abis-Mux function is enabled. Max Subframe Length: specifies the maximum size of an Abis-Mux subframe. If the size of an Abis-Mux subframe exceeds the value of this parameter, the Abis-Mux subframe is not multiplexed. Maximum Frame Length: pecifies the maximum size of an Abis-Mux frame. Time Out: specifies the maximum time that the system waits before sending the multiplexed data. If the waiting time exceeds the value of this parameter, the system immediately sends the multiplexed data to prevent a too long delay. Service Type: specifies the type of service for which multiplexing is performed. The service type can be CS speech service, CS data service, PS service with a high priority, and PS service with a low priority.
l l
The BSC6900 parameters related to the Ater-Mux function are as follows:

IP MUX Type: When this parameter is set to AterMux, the Ater-Mux function is enabled on the BSC6900 side.
2.52.4.4 UDP-Mux
UDP Multiplexing (UDP-Mux) is a transport bearer multiplexing technology, which is defined in 3GPP TR 29.814. It is also called RTP-Mux. This technology enables multiple RTP packets to be multiplexed in one UDP packet, reducing the overhead of the UDP/IP/L2/L1 header and increasing the transmission efficiency. UDP-Mux has the following characteristics: l The implementation is simple. UDP-Mux requires support only at the transmission end and the reception end. The intermediate transport equipment does not need to support UDPMux. UDP-Mux significantly improves the transmission efficiency but increases the transmission delay. UDP-Mux is an open standard.
l l
UDP-Mux applies to the user planes of the IP-based Iu-CS and A interfaces.
?.1. Packet Format

UDP-Mux has two multiplexing modes: l Multiplexing mode 1: In this mode, the RTP header is multiplexed without being compressed. The size of an RTP header is 12 bytes. Figure 2-210 shows the IP datagram format with the RTP header uncompressed. l Multiplexing mode 2: In this mode, the RTP header is compressed and then multiplexed.The field that remains unchanged during a call is removed from the RTP header, and only the variable Sequence Number and Timestamp fields are reserved. Therefore, the size of the RTP header after compression is 3 bytes for a UMTS network and 4 bytes for a GSM network. Figure 2-211 shows the IP datagram format with the RTP header compressed. Figure 2-210 IP datagram format with the RTP header uncompressed
Issue 08 (2011-09-30)
885
Figure 2-211 IP datagram format with the RTP header compressed
The fields of the IP multiplexing datagram are described as follows. l l T: specifies whether an RTP header is compressed. Value 0 indicates that the RTP header is not compressed, and value 1 indicates that the RTP header is compressed. Mux ID: is used in combination with the Source ID field to identify a user plane connection. The value of this field is equal to the destination UDP port number of the RTP packet divided by two. Length indicator: specifies the size of a multiplexed RTP packet, including the size of the RTP header and payload. This field indicates the location where the next multiplexed packet starts. R: reserved extension bit. This field is set to 0. Source ID: is used in combination with the Mux ID field to identify a user plane connection. The value of this field is equal to the source UDP port number of the RTP packet divided by two. Sequence Number: specifies the sequence number of an RTP datagram. Timestamp: specifies the time when an RTP datagram is sent. Payload Type: specifies the payload type.
l l
l l l
The UDP-Mux packet has the following characteristics: l l l The RTP packets in one UDP-Mux packet share the IP and UDP headers and must have the same source IP address, destination IP address, and DSCP. A single UDP-Mux packet can carry the data of different users. The Multiplex header specifies the size and owner of each RTP packet. The UDP header includes a fixed source UDP port number, which indicates that the packet is a UDP-Mux packet. Therefore, demultiplexing is required at the reception end.
As shown in Figure 2-210 and Figure 2-211, when k RTP packets are multiplexed into one UDP packet, the IP packet overhead is reduced. When the RTP header is not compressed, an overhead of (23 x k 28) bytes is saved. When the RTP header is compressed, an overhead of (32 x k 28) bytes is saved. In addition, the total layer 2 and layer 1 header overhead decreases
with the reduction of the number of packets. As a result, the multiplexing efficiency is significantly improved. For detailed analysis, see 3GPP TR 29.814. The related parameters of the BSC6900 are as follows: l Parameters for enabling the UDP-Mux function. IP MUX Type: specifies whether the UDP-Mux function is enabled on the BSC6900 side. When this parameter is set to UDPMUX, the UDP-Mux function is enabled. Sender UDP MUX Mode: specifies the UDP Mux mode of the BSC6900 when it transmits data. The value of this parameter can be NORTPCOMP or RTPCOMP.If this parameter is set to NORTPCOMP, the BSC6900 supports the UDP-Mux function with uncompressed RTP headers when transmitting data. If this parameter is set to RTPCOMP, the BSC6900 supports the UDP-Mux function with compressed RTP headers when transmitting data. Receive UDP MUX Mode: specifies the UDP Mux mode of the BSC6900 when it receives data. The value of this parameter can be NORTPCOMP or RTPCOMP.If this parameter is set to NORTPCOMP, the BSC6900 supports the UDP-Mux function with uncompressed RTP headers when receiving data. If this parameter is set to RTPCOMP, the BSC6900 supports the UDP-Mux function with compressed RTP headers when receiving data. l Max subframe length[byte]: specifies the maximum size of an RTP packet that can be multiplexed. If the size of an RTP packet exceeds the value of this parameter, the RTP packet is not multiplexed but is directly transmitted. Maximum Frame Length[byte]: specifies the maximum size of a UDP-Mux packet. If the size of a UDP-Mux packet exceeds the value of this parameter, the packet is transmitted without being added with more packets. Maximum Delay Time[ms]: specifies the maximum time that the system waits before sending the multiplexed data. If the waiting time exceeds the value of this parameter, the system immediately sends the multiplexed data to prevent a too long delay.
?.2. Working Principles

The prerequisites for enabling the UDP-Mux function are as follows: l l Both the BSC and the MGW support the UDP-Mux function. The data related to the UDP-Mux function is configured on both the BSC and MGW sides.
Figure 2-212 shows the working principle of UDP-Mux at the transmission end. Figure 2-212 Buffering and multiplexing performed at the transmission end
Issue 08 (2011-09-30)
887
The transmission end buffers the user data and encapsulates multiple RTP packets into one UDPMux packet according to specific multiplexing conditions. The multiplexing conditions are as follows: l l If the size of a UDP-Mux packet reaches Maximum Frame Length[byte], the UDP-Mux packet is sent without being multiplexed with more RTP packets. If the value of the timer reaches Maximum Delay Time[ms], the UDP-Mux packet is sent without being multiplexed with more RTP packets.
After receiving the UDP-Mux packets in sequence, the reception end demultiplexes the packets to obtain the original data and performs service processing.
2.52.4.5 Header Compression

Header compression is used to reduce the frame header overhead on PPP links and to improve bandwidth efficiency. Header compression requires the point-to-point support of both the transmission and reception ends. The BSC6900 supports the following types of header compression: l l l Address and Control Field Compression (ACFC) Protocol Field Compression (PFC) IP Header Compression (IPHC)
Contrary to multiplexing technologies, header compression applies to the scenarios where the transmission bit error rate on the interfaces is high. The BSC6900 supports header compression on the Iub, Iur, and Iu interfaces of a UMTS network and on the A and Ater interfaces of a GSM network. The following describes the three header compression methods.
?.1. Address and Control Field Compression

ACFC is defined in RFC1661 and is used to compress the address and control fields of PPP and MLPPP frames. The size of the address and control fields in both the PPP and MLPPP frame headers is two bytes, and these two fields have fixed values. Therefore, the two fields can be compressed. For details about the PPP frame format, see section 2.52.3.2.3 Point-to-Point Protocol. For details about the MLPPP frame format, see 2.52.3.2.4 Multilink-PPP. When a link is established, the transmission and reception ends negotiate link attributes, including whether to use ACFC. If both ends determine to use ACFC, the address and control fields are omitted in subsequent frames. If the Address and control field compress parameter of the BSC6900 is set to Enable, the BSC6900 supports ACFC and the two ends of the link negotiate whether to use ACFC. If this parameter is set to Disable, the BSC6900 does not support ACFC.
?.2. Protocol Field Compression

PFC is defined in RFC1661 and is used to compress the protocol field of PPP and MLPPP frames. The two-byte Protocol field of a PPP or MLPPP frame specifies the type of protocol encapsulated in the Information field. For example, 0x0021 indicates that an IP datagram is encapsulated. The
value of the protocol type assigned is usually less than 256, which can be represented by one byte. Therefore, the protocol field of most frames can be compressed to one byte. The least significant bit of the Protocol field in a PPP or MLPPP frame specifies whether PFC is used. Value 0 indicates that the Protocol field is not compressed, and value 1 indicates that the Protocol field is compressed. If the Protocol field compress parameter of the BSC6900 is set to Enable, the BSC6900 supports PFC and the two ends of the link negotiate whether to use PFC. If this parameter is set to Disable, the BSC6900 does not support PFC.
?.3. IP Header Compression

IPHC is defined in RFC2507 and RFC3544. It is used to compress the IP/UDP/RTP header over PPP links. IPHC improves bandwidth utilization in the following ways: l The header can be classified into two types: fixed fields and variable fields. In IPHC, the fixed fields are only included in some packets and omitted in other packets, whereas the variable fields are represented in less bytes for each packet.. When a PPP link is established, both parties in a communication send packets with complete headers to establish the header context before they can send packets with compressed headers. With the header context, complete headers can be retrieved from the compressed headers.
The Head compress parameter of the BSC6900 specifies whether the IP header of a PPP or MLPPP link is compressed. l l If this parameter is set to No_HC, the BSC6900 does not support IPHC. If this parameter is set to UDP/IP_HC, the BSC6900 supports UDP and IP header compression, and the two ends of the link negotiate whether to compress the UDP and IP headers at link establishment. If this parameter is set to RTP/UDP/IP_HC, the BSC6900 supports UDP, RTP, and IP header compression, and the two ends of the link negotiate whether to compress the UDP, RTP, and IP headers at link establishment.
2.52.5 IP Clock Synchronization

In a communication system, clock synchronization is a key factor to ensure the reliable and errorfree transmission of speech and data. With the wide application of IP technologies in the communication system, clock synchronization becomes more and more complex. Currently, three IP clock synchronization solutions are available: l l l Clock over IP IEEE1588 V2 Synchronous Ethernet
The following sections describe the three IP clock synchronization solutions. For details about the parameter settings, see the IPCLK1000 product documents and the BTS product documents.
2.52.5.2 Clock over IP

The clock over IP solution is based on the server/client architecture. The clock synchronization process is as follows: 1. 2. The IP clock server obtains the reference clock source from other devices, such as the Global Positioning System (GPS) or Building Integrated Timing Supply System (BITS). According to the Huawei proprietary standard, the IP clock server encapsulates the clock synchronization signals into IP datagrams and then transmits these datagrams to the IP clock client through the IP network. The IP clock client processes the IP datagrams to obtain the local clock that meets its clock accuracy requirement.
3.
The IP clock server can be Huawei IPCLK1000. The Huawei base stations provide the IP clock client function. If a base station does not support the IP clock client function, the IPCLK1000 can be configured as the IP clock client. Figure 2-213 shows a typical networking of the clock over IP solution. Figure 2-213 Typical networking of the clock over IP solution
You can also deploy two IPCLK1000s in the network to improve reliability. If one IPCLK1000 is faulty or the intermediate network is faulty, the base stations can obtain clock signals from the other IPCLK1000. The transmission of IP datagrams requires a specific bandwidth. In addition, the clock over IP solution has specific requirements for the delay, jitter, and packet loss rate on the intermediate network. If the QoS of the intermediate network cannot be ensured, the IPCLK1000 can be deployed near the base station (as shown in Figure 2-213, the IPCLK1000 is deployed at the same site as the router). This enables the IPCLK1000 to provide clock signals directly for the base stations nearby, reducing the dependence on the quality of the intermediate network. The clock over IP solution adopts the server/client architecture, making the network deployment flexible. One IP clock server can provide reference clock signals for hundreds of base stations. Compared with other solutions such as GPS, the clock over IP solution saves the costs for equipment investment. The intermediate transport equipment only forwards IP timing packets, and therefore the clock over IP solution does not require the support of intermediate transport equipment.
2.52.5.3 IEEE1588 V2
The IEEE1588 V2 solution uses the same server/client architecture as the clock over IP solution. In the IEEE1588 V2 solution, the IPCLK1000 acts as the server, and the Huawei base station is embedded with the synchronization client. The clock over IP solution and the IEEE1588 V2 solution differ with respect to the clock synchronization procedure and the frame format. As for the frame format, the clock over IP solution complies with the Huawei proprietary standard, whereas the IEEE1588 V2 solution complies with the IEEE1588 V2 standard. The IEEE1588 V2 standard defines frequency synchronization and time synchronization. Currently, the BSC6900 implements only frequency synchronization. Compared with the clock over IP solution, the IEEE1588 V2 solution requires a lower bandwidth on the intermediate network, supports the interworking between devices of different manufacturers, and enables the evolution towards time synchronization in the future. The IEEE1588 V2 solution supports two modes: unicast and multicast. In unicast mode, clock links are established between the clock server and each BTS; the clock server transmits clock packets to each BTS, as shown in Figure 2-214. In multicast mode, clock links are established between the clock server and a set of BTSs; the clock server transmits clock packets to each set of BTSs instead of a single BTS, as shown in Figure 2-215 Therefore, transmission bandwidth in the intermediate network is saved in multicast mode, and accordingly the CAPEX is reduced. Figure 2-214 Unicast in the IEEE1588 V2 solution
Figure 2-215 Multicast in the IEEE1588 V2 solution
Issue 08 (2011-09-30)
891
2.52.5.4 Synchronous Ethernet

Synchronous Ethernet is defined in ITU-T G.8262. The synchronous Ethernet solution has the same basic principles as SDH and PDH network clock synchronization. That is, a higher-level device encodes clock signals into serial data bit streams and a lower-level device receives the serial data bit streams from the physical layer to extract and trace the higher-level clock. Figure 2-216 shows the synchronous Ethernet solution. The intermediate device (for example, the Hub NodeB of the UMTS network) that has the synchronous Ethernet function can obtain the clock source in several ways. After obtaining the synchronous clock, the intermediate device distributes the clock signals to other base stations. Figure 2-216 Synchronous Ethernet solution
The synchronous Ethernet solution has the following advantages: l l l The clock is extracted from the physical layer and is not related to upper layer services. Therefore, the interworking performance is satisfactory. The clock recovery quality is relatively good and immune to packet loss and jitter. The transmission of clock signals in the synchronous Ethernet solution requires a lower bandwidth in comparison to the transmission of clock signals in the IEEE1588 V2 solution.
The synchronous Ethernet solution, however, has the following disadvantages: l l l This solution does not support time synchronization. The 10 Mbit/s Ethernet does not support the synchronous Ethernet function. All the intermediate transport equipment must support the synchronous Ethernet function. Otherwise, clock signals cannot be distributed to lower-level devices.
2.52.6 Fault Detection Technologies

2.52.6.1 Overview
There are a number of Ethernet fault detection mechanisms for improving network reliability. These mechanisms appear at different layers in the Ethernet protocol stack, as shown in Figure 2-217. The Ethernet fault detection mechanisms are physical detection, Ethernet Operation, Administration, and Maintenance (ETH OAM), Bidirectional Forwarding Detection (BFD), Address Resolution Protocol (ARP), and IP Performance Monitoring (PM). Figure 2-217 shows the fault detection mechanisms supported by different protocol layers. Figure 2-217 Fault detection mechanisms supported by different protocol layers
2.52.6.2 ETH OAM

The ETH OAM provides end-to-end and point-to-point Ethernet link OAM functions. Currently, it complies with IEEE 802.1ag and IEEE 802.3ah. As shown in Figure 2-218, the ETH OAM protocol is located between the MAC sublayer and the LLC sublayer. The ETH OAM has the following advantages: l The bandwidth occupied by ETH OAM is limited. Being a low-rate protocol, the ETH OAM protocol only has a small impact on the user data flows. Generally, EHT OAM has only a minor impact on the link capacity. By using the MAC address, the ETH OAM packets are processed only at the MAC sublayer. Therefore, other Ethernet layers are not affected.
Figure 2-218 Position of ETH OAM on a network
Issue 08 (2011-09-30)
893
?.1. IEEE 802.3ah-Based ETH OAM

The point-to-point ETH OAM solution is based on the IEEE 802.3ah protocol. It is oriented to the user side instead of to the network side.
Application Scenarios
When IEEE 802.3ah-based ETH OAM is used, the local end and the peer end must be connected without any intermediate switches. This solution is mainly applicable to the management of Ethernet links between BTSs/NodeBs, between BSC6900s, between BSC6900 and a BTS/ NodeB, and between BSC6900/BTS/NodeB and transport equipment.
NOTE
In this document, BTS refers to the base station of a GSM network, and NodeB refers to the base station of a UMTS network.
Figure 2-219 An example application scenario of IEEE 802.3ah based link fault detection
Data Configurations
The network equipment connected to BSC6900 must support the IEEE 802.3ah-based ETH OAM. There must not be any intermediate equipment between BSC6900 and the interconnected network equipment. To enable link monitoring and fault detection of IEEE 802.3ah-based ETH OAM, configure the BSC6900 as follows: l Run the ACT ETHOAMAH command to set the PDU Send Prid[ms] parameter. This parameter specifies the fault report period based on the IEEE 802.3ah protocol.
Issue 08 (2011-09-30)
l l
Run the ACT ETHOAMAH command to set the PDU Pkt Len[Byte] parameter. This parameter specifies the size of an OAM PDU based on the IEEE 802.3ah protocol. Run the ACT ETHOAMAH command to set the time window and threshold of each link according to the IEEE 802.3ah protocol. The related parameters are as follows: Err Frmae Event Prid[s] Err Frmae Event Para Err Frmae Cyc Event Prid Err Frame Cyc Event Para Err Frmae Sec Event Prid[s] Err Frame Sec Event Para
?.2. IEEE 802.1ag-Based ETH OAM

The IEEE 802.1ag-Based ETH OAM performs end-to-end detection on a per maintenance domain (MD) basis. This facilitates the maintenance of the Ethernet connection. Maintenance end points (MEPs) are created at both ends of an MD to define the range of the MD. In other positions of the MD, maintenance intermediate points (MIPs) are created as required. By monitoring the MEPs and MIPs, it is possible to learn the network status and identify faults. The management level field in the ETH OAM frame is used to implement hierarchical management. If the level of an OAM frame is higher than the MP level, the MP transparently transmits the OAM frame. If the level of an OAM frame is lower than the MP level, the MP directly discards the OAM frame. If the level of an OAM frame is equal to the MP level, the MP responds according to the message type or terminates the OAM frame. The IEEE 802.1ag-Based ETH OAM provides three functions: connectivity check (CC), loopback (LB), and link tracking (LT). l CC: The IEEE 802.1ag protocol supports unidirectional CC. The source MEP sends a connectivity check message (CCM) frame periodically. When the destination MEP receives the CCM frame, it starts the CC function. If the destination MEP does not receive a CCM frame from the source MEP within a specified time (3.5 times the CCM transmission interval), the destination MEP reports CC_LOS alarms repeatedly until the link becomes normal and the destination MEP receives a CCM frame from the source MEP. LB: The source MEP sends a loopback message (LBM) frame to an MIP or MEP. At the same time, the source MEP starts a timer. The destination MP returns a loopback reply (LBR) frame, after reception of the LBM frame. If the source MEP does not receive the LBR frame before the timer expires, the loopback fails. Note that only an MEP can initiate an LB test. Both an MIP and an MEP can function as the destination end in an LB test. LT: The source MEP sends a link trace message (LTM) frame to the destination MEP. At the same time, the source MEP starts a timer. When an MIP belonging to the MD receives the LTM frame, it forwards the frame to the destination MEP and at the same time sends a link trace reply (LTR) frame to the source MEP. After the destination MEP receives the LTM frame, it terminates the frame and sends an LTR frame to the source MEP. If the source MEP receives the LTR frame from the destination MEP, the LT test is successful. BSC6900 performs a link trace test by running the TRC MAC command.
Application Scenarios
The IEEE 802.1ag-Based ETH OAM applies to the scenarios where BTSs are cascaded. The application scenarios of ETH OAM in IP transmission are shown in Figure 2-220. The BTS/
NodeB, BSC6900, and transport equipment are deployed to implement the IEEE 802.1ag-Based ETH OAM. All devices in the MD must support forwarding or transparent transmission of ETH OAM PDUs. Figure 2-220 Examples of application scenarios of IEEE 802.1ag based link fault detection
Data Configurations
The network equipment that is interconnected to BSC6900 must support the IEEE 802.1agBased ETH OAM. Run the ACT ETHCC command to set the BSC6900 parameters related to the IEEE 802.1agBased ETH OAM. If the interconnected equipment is a GSM BTS, you also need to run the ACT BTSETHCC command to set the parameters of the BTS. As shown in Figure 2-221, gives an example, where the local end and the peer end are configured in the same MD. In the MD, two maintenance associations MA1 and MA2 are created. LPort1, LPort2, and RPort7 are located in MA1; LPort8 and RPort1 are located in MA2. LPort1, LPort2, and LPort8 can work as the MEPs of the local end, and RPort1 and RPort7 can work as the MEPs of the peer end. Figure 2-221 Example of MEP configuration
2.52.6.3 Bidirectional Forwarding Detection

Network equipment requires that the communication faults between adjacent systems be detected quickly. If a fault occurs, a substitute link can be established quickly or the data can be switched over to other links. Bidirectional Forwarding Detection (BFD) is a method of quickly detecting link faults. The BFD protocol is a type of high-speed independent Hello protocol. It is used to detect the transmission accuracy of Ethernet, Multiprotocol Label Switching (MPLS), common routing encapsulation, and IP Security Protocol (IPSec) tunnel. BFD can detect faults and trigger fault isolation within tens of milliseconds, minimizing service losses. When a fault is detected, a port switchover or IP rerouting is triggered through BFD. This prevents packet losses and call drops and therefore improves network communication reliability. BFD can detect faults quickly without adding too much extra load. BFD messages can be considered heartbeat messages. If the system transmits several BFD messages but receives no acknowledgment messages, it considers the link faulty. Figure 2-222 shows the BFD state machine, which indicates BFD state transitions. To simplify the illustration, the Admin Down state is excluded. In this figure, the notion in each rectangle indicates a session state and the notion on each arc indicates the state (specified by the state field in the BFD control message received) of the peer system or the expiry of the timer. Figure 2-222 BFD state machine
Down indicates that the BFD session has stopped or has just started. Init indicates that the peer system is in communication. Up indicates that the BFD session has been set up successfully. The BFD protocol is a handshake protocol. BFD messages are periodically transmitted based on the negotiation result to monitor the link connectivity. If the system does not receive any BFD message from the peer system for a long time, it considers the link disconnected. Figure 2-223 shows the BFD message exchange when the link is disconnected.
Issue 08 (2011-09-30)
897
Figure 2-223 BFD message exchange when the link is disconnected
After a BFD session is set up, the system periodically transmits BFD control messages in asynchronous BFD mode. If the peer system receives BFD control messages within the detection time shown in Figure 2-223, it considers that the BFD session is in the UP state. Otherwise, it considers that the session is in the DOWN state. There are two types of BFD: single-hop BFD (SBFD) and multi-hop BFD (MBFD). The BSC6900 supports BFD on the A, Abis, Gb, Iub, Iu, and Iur interfaces. The parameters related to BFD are as follows: l l l l l The Subrack No., Slot No., and Check Index parameters for the interface board uniquely specify a detection object. The Check type parameter specifies the detection type. It can be set to SBFD, MBFD, or ARP. The Check mode parameter specifies whether the detection is performed on the active port, standby port, or independent port. The Port No. and Peer IP address parameters specify the IP address pair of a BFD session. The Min interval of BFD packet send [ms] and Min interval of BFD packet receive [ms] parameters should be set during the BFD session negotiation to negotiate a capability with the peer end. The Detect multiplier of BFD packet parameter specifies the number of packets that the local end does not receive from the peer end before a BFD session is declared to be down.
?.1. Single-Hop Bidirectional Forwarding Detection

SBFD is applicable only to the direct connection where the IP addresses of both ends are on the same network segment. Its characteristics are as follows: l l SBFD must be started at both ends simultaneously. The detection duration of the two ends must be similar. The port status is associated with the detection status. If a fault is detected, a port switchover is triggered and the routes whose next hop is the detected address are deleted. Then, the upper layer selects other available routes. Independent port detection is supported.
Currently, the BSC6900 supports only the asynchronous mode and detection of the active port; it does not support simultaneous detection of active and standby ports. If an SBFD session is down during SBFD, the BSC6900 automatically disables the routes whose next-hop IP address is the peer IP address of this failed SBFD session. If SBFD is configured to be applicable only to the active port and the Whether affect the port swapping parameter is set to YES, an SBFD link fault triggers a port switchover. Otherwise, an SBFD link fault does not trigger a port switchover, but the availability of the related routes is affected. SBFD requires that both the BSC6900 and the devices connected to the BSC6900 support the BFD protocol.
?.2. Multi-Hop Bidirectional Forwarding Detection

MBFD can perform end-to-end indirect-connection link detection across several layer 3 devices. Its characteristics are as follows: l l MBFD must be started at both ends simultaneously. The detection duration of the two ends must be similar. The port status is not associated with the MBFD detection status. Instead, the status of the routes configured for MBFD is associated with the MBFD detection status. After a fault is detected, the routes configured for this MBFD become unavailable and the upper layer selects other available routes. Both the device IP address and the port IP address of the interface board can serve as the local IP address of MBFD. The peer IP address of MBFD, however, cannot be on the same network segment as any local IP address.
Currently, the BSC6900 supports only the asynchronous mode. If an MBFD session is down during MBFD, the BSC6900 disables the routes configured for this failed BFD session. The status of other routes is not affected and a port switchover is not triggered. In this case, packets are forwarded by other routes and IP rerouting is achieved. MBFD requires the peer equipment to support the BFD protocol. MBFD is a type of end-to-end fault detection. It is used to detect the connectivity of the link between the source IP address and the destination IP address. For the BSC6900, the source IP address of MBFD can be the device IP address or Ethernet port IP address of a board to be detected. The source and destination IP addresses can also be the IP addresses of other network devices to be detected. The ADD IPRTBIND/ADD IPPATHBIND commands can be used to specify the binding relationship between MBFD and a certain IP route or IP path. Once the binding relationship is specified, the IP route or IP path configured for the MBFD is found unavailable if MBFD detects a fault.
2.52.6.4 Address Resolution Protocol Detection

The working principle of Address Resolution Protocol (ARP) detection is similar to that of SBFD detection. ARP detection uses the ARP mechanism, where the local end sends an ARP request to the peer end and determines the link connectivity according to the ARP response from the peer end. The BSC6900 sends an ARP request to the network periodically. The destination of the request is the peer address to be detected. The BSC6900 determines the link connectivity based on whether it receives an ARP response from the destination. If the BSC6900 receives an ARP response from the destination, it considers the link normal. If the BSC6900 does not receive any ARP responses from the destination for certain consecutive periods, it considers the link faulty. ARP detection is applicable only to the direct connection where the IP addresses of both ends are on the same network segment. ARP detection can be used as an alternative when the peer equipment does not support BFD detection. If BFD detection is supported, however, it is preferentially to be used as it is a fast bidirectional detection mechanism.
NOTE
ARP messages are broadcast messages. If the BSC6900 and the Layer 3 devices are directly connected, broadcast storms will not occur. If the BSC6900 and the layer 3 devices are not directly connected, broadcast storms are likely to occur.
The characteristics of ARP detection are as follows: l l ARP detection is independent of the peer equipment. The detection can be started by a single end. The port status is associated with the detection status. If a fault is detected, a port switchover is triggered and the routes whose next hop is the detected address are deleted. Then, the upper layer selects other available routes. Independent port detection is supported. In board backup mode, detection of active port and simultaneous detection of active and standby ports are supported. When the active and standby ports are detected simultaneously, the port IP addresses cannot be on the same network segment.
l l
The differences between ARP detection and BFD detection are as follows: l l l ARP detection needs a longer time to detect a fault than BFD detection. BFD detection requires support from both ends of the link whereas ARP detection does not. In the case of ARP detection, the corresponding routes become unavailable if the link is faulty. In such a case, a port switchover can be triggered through parameter configurations. This is similar to SBFD detection.
ARP detection and SBFD detection are used for the following purposes: l l To detect link connectivity between the BSC6900 and the gateway under the existence of routers To detect link connectivity between the BSC6900 and the peer equipment (generally referred to as CN equipment) when the BSC6900 and the peer equipment are directly connected
With respect to parameter configurations, the ARP packet time-out[100ms] and ARP packet resend times parameters must be configured for ARP detection. ARP packet time-out [100ms] specifies the interval for the BSC6900 to send an ARP detection packet. ARP packet
resend times specifies the number of consecutive response packets that are not received by the BSC6900 before the ARP link is considered faulty. The BSC6900 supports ARP detection on the A, Abis, Gb, Iub, Iu, and Iur interfaces. The parameters related to ARP detection are as follows: l l Peer IP address: specifies the destination IP address for BFD or ARP detection. Backup port IP address: This parameter specifies the IP address of the standby Ethernet port. The standby Ethernet port detects faults at the physical layer and to start ARP detection to detect faults at higher layers. In the case of ARP detection, the IP address of the standby port must be on different network segments from that of the active port. Backup port mask: specifies the subnet mask of the standby port where ARP detection is enabled. Check type: specifies the detection type. It can be set to SBFD, MBFD, or ARP. The VRRP does not support BFD detection. Therefore, in VRRP topology, ARP detection is recommended. Check mode: This parameter specifies the detection mode. If this parameter is set to PRIMARY, it indicates that detection is performed on the active port. If this parameter is set to STANDBY, it indicates that detection is performed on the standby port. If this parameter is set to INDEPENDENT, it indicates that detection is performed on the independent port.
l l
?.1. Binding Between SBFD/ARP and IPRT

When SBFD/ARP detection is performed, each SBFD/ARP detection task must be bound with an IP route (IPRT). For each pair of source and destination IP addresses, only one SBFD/ARP detection task can be started. In this case, the source IP address must be the port IP address, and the destination IP address must be on the same network segment as the source IP address. If detection is started at an independent port or an active port, the route whose next hop is the destination IP address is automatically selected as the detected route. SBFD/ARP detection started at the active port is classified into key detection and common detection. If key detection detects a fault in the active port and does not detect a fault in the standby port, a port switchover is triggered. Common detection does not trigger a switchover. l l If a fault is found through the detection started at the independent port, you can infer that the routes configured for the detection are faulty. If a fault is found through the detection started at the active port and a port switchover is not triggered, you can infer that the routes configured for the detection are faulty. If a fault is detected and a port switchover is triggered, the route is switched to the standby port.
?.2. Application of SBFD/ARP in VRRP Topology

In the case of VRRP, a master router is selected from routers according to specified criteria. The master router forwards data packets and uses its virtual MAC address as the SBFD/ARP source address for the host to respond. Other routers function as backup routers. The master router communicates with backup routers by sending VRRP multicast packets periodically, so that the backup routers know the status of the master router in real time. Normally, backup routers do not forward the data packets that are sent to the virtual MAC address. If the master router fails and the backup router does not receive VRRP messages within a specified time, the backup
router takes over the services handled by the master router. In this manner, the communications continuity and reliability are ensured. Figure 2-224 shows the VRRP topology. Figure 2-224 VRRP topology
In this topology, the BSC6900 uses VRRP IP2 (virtual IP address) as the next-hop IP address for communication. Note that VRRP IP2 cannot be used as the source or destination IP address for SBFD detection because of the existence of routers. In this case, only key ARP detection can be used to detect the link connectivity between IP1 and VRRP IP2. In addition, common SBFD detection can be used to detect the connectivity of the communication link, with IP1 (port IP address) used as the source IP address and IP3/IP4 (port IP address of the router) used as the destination IP address. At the same time, the router starts to detect the BSC6900. Therefore, the router can perform VRRP switchover in case of link faults. Furthermore, the BSC6900 knows whether VRRP IP2 is faulty and then determines whether to switch over the port connected to the router.
2.52.6.5 IP Performance Monitoring

IP performance monitoring (IP PM) detects the QoS of the IP transport network. The QoS detection of the IP transport network provides a basis for flow control and admission control after the introduction of IP transport. The IP PM function effectively monitors the transport network by detecting the QoS of the intermediate transport network in a fast and timely manner. IP PM uses forward monitoring (FM) and backward reporting (BR) mechanisms to detect delay, jitter, and packet loss. Figure 2-225 shows the operating principle of IP PM. Figure 2-225 Operating principle of IP PM
Issue 08 (2011-09-30)
902
The operating principle of IP PM is as follows: 1. 2. 3. End A (for example, the BSC6900) periodically sends end B (for example, the BTS/NodeB) an FM message, indicating the number of packets transmitted by end A. After receiving the FM message, end B responds to end A with a BR message, indicating the number of received packets. End A collects statistics on delay, jitter, and packet loss rate related to the reception of the BR message.
IP PM enables the measurement of QoS indicators, such as delay, jitter, and packet loss rate of a certain IP link between the BSC6900 and the BTS/NodeB. IP PM uses a Huawei proprietary protocol and requires support from both the BSC6900 and the BTS/NodeB. IP PM is performed on a per IP path basis. The Adjacent Node ID and IP path ID parameters specify the IP path where IP PM is to be performed.
2.52.7 Networking Reliability

2.52.7.1 Overview
To ensure reliability in IP networks and provide reliable end-to-end data communications, the BSC6900 implements the following reliability mechanisms: l l l l l Board backup Ethernet port backup Ethernet port load sharing Route-based port backup and load sharing Ethernet link aggregation
Different networking reliability mechanisms are applicable to IP interface ports of different types, as described in Table 2-147. 2.52.12 Appendix describes the reliability mechanisms supported by different interface boards. Table 2-147 Reliability mechanisms supported by different interface boards Port FE/GE ports Reliability Mechanism Supported Board backup Ethernet port backup Ethernet port load sharing Ethernet link aggregation Route-based port backup and load sharing E1/T1/Ch-STM-1 ports Board backup
The following sections describe the network reliability mechanisms.


NOTE
For details about board backup, Ethernet port backup, and Ethernet port load sharing, see the BSC6900 Technical Description.
2.52.7.2 Board Backup

Board backup applies to all IP interface boards. When adding a board, configure board backup by setting the Backup parameter to YES. In IP over FE/GE or IP over PPP over E1/T1 transmission mode, all the IP interface boards of the BSC6900 can work in active/standby mode. Below is a board backup example when the IP over PPP over E1/T1 transmission mode is used. The E1/T1 ports of the active and standby boards are connected through Y-shaped cables. Only the E1/T1 port of the active board transmits and receives IP packets; the E1/T1 port of the standby board is used only for link detection. The standby board does not process services but saves the PPP link status, negotiation session information, and some user data of the active board. In this case, renegotiation is not required during an active/standby switchover, preventing service interruption. When the active board becomes faulty but the standby board is normal, a switchover is performed between the active and standby boards.
NOTE
When multiple E1/T1 links are configured between the BSC6900 and the interconnected network element (NE), these E1/T1 links are generally bound together to form an MLPPP link to achieve high reliability and efficiency. In this case, the failure of a single E1 link only causes the reduction of transmission bandwidth, without interrupting the ongoing services.
Figure 2-226 shows the networking for board backup in IP over PPP over E1/T1 transmission mode. Figure 2-226 Networking for board backup in IP over PPP over E1/T1 transmission mode
In IP over PPP over Ch-STM-1 transmission mode, the interface boards of the BSC6900 can work in active/standby mode in a similar way as described previously. The active and standby boards connect to the optical transport equipment at the peer end through optical cables. When the working channel becomes faulty, the BSC6900 negotiates with the optical transport
equipment on the protection channel according to the MSP protocol to switch the services to the protection channel. In this manner, MSP switching is implemented.
2.52.7.3 Ethernet Port Backup

Ethernet port backup is based on the board backup mechanism. The Ethernet ports on the active and standby boards are configured to work in active/standby mode. In Ethernet port backup mode, the active port transmits and receives data and processes services; the standby port does not process services and it is used only for link detection. Ethernet port backup is independent of the board backup mechanism, that is, the active port can be on the active board or on the standby board. Link detection is performed between the active/standby port and the interconnected equipment by using ARP, BFD, or physical layer detection. For details about fault detection, see 2.52.6 Fault Detection Technologies. When the active link is found faulty but the standby link is normal, or when the active port is found faulty but the standby port is normal, a switchover is performed between the active and standby ports. To configure the Ethernet port backup of the BSC6900, start to configure board backup (for details about how to configure board backup, see 2.52.7.2 Board Backup). Then, enter the ADD ETHREDPORT command and set the parameters Subrack No., Slot No, and Port No. to specify the active and standby Ethernet ports. Figure 2-227 shows the networking for Ethernet port backup. In this case, data configuration is not required for the standby port. After an active/standby port switchover is performed, the original standby port automatically uses the data configuration of the original active port. Figure 2-227 Reliability networking for Ethernet port backup
In this situation, the active and standby FE/GE ports of the BSC6900 are connected to the two Provider Edges (PEs), which connect to the IP network. The two PEs provide redundancy protection on the data transmitted between the BSC6900 and the PEs by using the Virtual Router Redundancy Protocol (VRRP). One PE connects to the other through two GE ports. The links between the PEs use the link aggregation group (LAG) to increase link bandwidth and improve link stability. The active and standby FE/GE ports of the BSC6900 share one IP address,
represented by IP1-0. On the PE side, the active and standby FE/GE ports of the BSC6900 are configured on the same VLAN and use the same VRRP IP address, represented by IP1-1.
NOTE
l If the distance between the BSC6900 and the PEs is greater than or equal to 100 m, it is recommended that the GE optical ports of the GOUa boards be used to connect the BSC6900 to the PEs. l If the distance between the BSC6900 and the PEs is less than 100 m, it is recommended that the FE/ GE electrical ports of the FG2a boards be used to connect the BSC6900 to the PEs.
2.52.7.4 Ethernet Port Load Sharing

When using the Ethernet port backup mechanism, only one port works and therefore the port utilization is low. To improve the port utilization, Ethernet port load sharing can be used. In load sharing mode, two ports work simultaneously and both can receive and transmit packets. Service data is shared between the ports. This reduces the risk that one port is busy but the other port is idle, improving transmission efficiency. This operation mode, however, does not provide redundancy protection for data transmission. Therefore, if one port fails, the transmission bandwidth will decrease. Ethernet port load sharing is based on the board backup mechanism. Use the ADD IPRT command to add the corresponding IP route. In Ethernet port load sharing mode, service data is transmitted through two ports. When either of the ports or links is faulty, all service data is transmitted and received through the other port, and therefore the services are still processed normally. In load sharing mode, a port failure will not result in a port switchover. Figure 2-228 shows the networking for Ethernet port load sharing. Figure 2-228 Networking for Ethernet port load sharing
The two FE/GE ports on the active and standby boards use different IP addresses IP1-0 and IP2-0, which are on different network segments. The PE is configured with two IP addresses corresponding to IP1-0 and IP2-0, namely, IP1-1 and IP2-1. Two routes from IP1-0 and IP2-0 respectively to the destination IP address are configured; the next hops of the two routes are IP1-1 and IP2-1 respectively; the two routes are configured with the same Priority. In this manner, the two ports work in load sharing mode, and the data from the BSC6900 to the destination IP address is transmitted over the two routes in load sharing mode.
Issue 08 (2011-09-30)
906

NOTE
l The two ports of the BSC6900 working in load sharing mode can be connected to one PE or two PEs. l If the distance between the BSC6900 and the PEs is greater than or equal to 100 m, it is recommended that the GE optical ports of the GOUa boards be used to connect the BSC6900 to the PEs. l If the distance between the BSC6900 and the PEs is less than 100 m, it is recommended that the FE/ GE electrical ports of the FG2a boards be used to connect the BSC6900 to the PEs.
2.52.7.5 Route-Based Port Backup and Load Sharing

Intra-board route-based port backup is implemented by configuring multiple routes to the same destination IP address. The priorities of the routes vary, depending on the next-hop IP address. Intra-board route-based load sharing is implemented by configuring multiple routes to the same destination IP address. The priorities of the routes are the same, but the next-hop IP addresses are different. Route-based port backup and route-based load sharing require the interface board to work in independent mode. Use the ADD IPRT command to add the corresponding IP routes. For details about the route configuration, see 2.52.7.4 Ethernet Port Load Sharing.
2.52.7.6 Ethernet Link Aggregation

In compliance with the IEEE 802.3ad protocol, link aggregation enables multiple physical links to be bound to form a logical link. That is, multiple links are aggregated to form a link aggregation group (LAG), which can be considered as an independent link in an upper-layer application perspective. Ethernet link aggregation increases transmission bandwidth and improves reliability and enables user data to be transmitted over multiple links. When an Ethernet port in a link aggregation group becomes faulty, services are not interrupted.
?.1. Prerequesites for Link Aggregation

If the BSC6900 is configured with an LAG, the interconnected peer equipment must also support link aggregation and there must not be any intermediate equipment between the interconnected equipment and the BSC6900. When the BSC6900 is configured with an LAG, the links in the link aggregation group must have the same attributes. For the BSC6900, both the links of the active and standby boards and the links within one board can be aggregated. It is recommended that the board backup mechanism be used to implement link aggregation.
NOTE
Currently, the BTS does not support link aggregation. Therefore, link aggregation cannot be implemented over the Abis interface.
?.2. Basic Principles of Link Aggregation

Based on the IEEE 802.3ad protocol, the Link Aggregation Control Protocol (LACP) provides a method of dynamically aggregating or deaggregating links. The local end exchanges information with the peer end by sending Link Aggregation Control Protocol Data Units (LACPDUs).
LACP is located at the link aggregation sublayer, which belongs to the data link layer. As shown in Figure 2-229, the link aggregation sublayer is an optional sublayer between the MAC client sublayer and the MAC sublayer. Figure 2-229 Position of the link aggregation sublayer in the TCP/IP reference model
In the LACP protocol, the two ends of a link are called Actor and Partner respectively. By exchanging LACPDUs, the two ends notify each other of the information about the system priority, system MAC address, port priority, port number, and operation key. After receiving the information, the peer end compares it with the stored information related to other ports to choose an aggregation port. The two ends negotiate with each other about the links that can be bound to form an aggregation group and about the time when a link can be put into the group. The BSC6900 supports manual aggregation and static aggregation. l Manual aggregation In manual aggregation mode, the system is not allowed to automatically add or delete a port from an aggregation group. An aggregation group must contain at least one port. If an aggregation group contains only one port, the port can be removed from the aggregation group only by deleting the aggregation group. In manual aggregation mode, the LACP protocol is not enabled for the ports, and the local end determines the ports to be aggregated. l Static aggregation In static aggregation mode, the system is not allowed to automatically add or delete a port from an aggregation group. The system automatically enables the LACP protocol for the ports in a static aggregation group. When a static aggregation group is deleted, the ports in the group form one or more dynamic LACP aggregations, and the LACP protocol remains enabled. Users are not allowed to disable the LACP protocol for the ports in a static aggregation group. Compared with manual aggregation, static aggregation has the following characteristics: The ports in a static aggregation group are aggregated according to the manual configuration data and communicate with each other according to the LACP protocol to determine whether the manually aggregated ports can be aggregated. The attributes of all the ports in an aggregation group must be the same in both manual aggregation and static aggregation. Multiple ports negotiate with each other according to the LACP protocol to form a logical port and share the same IP address. This IP address also serves as the IP address of the link aggregation group and is specified by the Local IP address parameter. The ports in a link aggregation group share one IP address.
The aggregation mode is specified by the Aggregation Mode parameter. To enable the aggregation group function, configure the BSC6900 as follows: l l l l Run the ADD ETHTRK command to add a link aggregation group and set the Trunk No.. parameter. Run the ADD ETHTRKLNK command to add a link to the aggregation group and set the Trunk Link No.. parameter. Run the ADD ETHTRKIP command to configure the IP address for the link aggregation group. Run the SET ETHPORT command to configure the attributes of the ports in the link aggregation group.
?.3. Application of Link Aggregation

When the BSC6900 is interconnected to the Optical Switch Node (OSN), link aggregation can be performed on the FE/GE ports to increase transmission bandwidth and improve reliability. The BSC6900 supports link aggregation on the FE/GE ports of the active and standby boards. After the links are aggregated, the corresponding FE/GE ports share a Virtual MAC (VMAC) and an IP address. Figure 2-230 illustrates link aggregation performed on GE ports. Figure 2-230 Link aggregation performed on GE ports
To use the link aggregation group for transmission, both the BSC6900 and the interconnected equipment must support link aggregation. The links in the link aggregation group can work properly only after the aggregation group is successfully negotiated.
2.52.8 IP DHCP
2.52.8.1 Dynamic Host Configuration Protocol

The Dynamic Host Configuration Protocol (DHCP) dynamically provides the terminal with configuration information such as the IP address. DHCP can allocate IP addresses automatically and establish OM channels for IP RAN and IP BSS. The BSC6900 allocates the planned IP address and port number to the BTS/NodeB automatically by using the DHCP mechanism and reports the information related to the BSC6900 to the BTS/NodeB through DHCP information exchange. This substitutes local configuration operation and therefore facilitates network deployment. The DHCP involves the following characteristics: l l l l Works in client/server mode. When receiving a request from the client, the server responds with information such as the IP address, gateway address, and DNS server address. Simplifies IP address management. Provides centralized IP address management. Complies with RFC2131 and RFC2132.
The DHCP procedure has a DHCP server and a DHCP client, as shown in Figure 2-231. In the following example, the BSC6900 functions as the DHCP server, and the BTS/NodeB functions as the DHCP client. The BTS/NodeB can obtain the IP address dynamically. Figure 2-231 DHCP procedure
The DHCP procedure is described as follows: 1. 2. 3. 4. The BTS/NodeB sends a DHCP DISCOVER message to search for the BSC6900. The BSC6900 sends configuration information such as the IP address to the BTS/NodeB using DHCP OFFER messages. The BTS/NodeB selects an IP address from the received DHCP OFFER messages and then responds with a DHCP REQUEST message. The BSC6900 sends a DHCP ACK message to the BTS/NodeB.
2.52.8.2 VLAN Detection

The VLAN detection procedure is as follows: When a base station starts to operate, it does not have the current VLAN information. Therefore, messages cannot be sent over the layer 2 network in the DHCP phase and the base station cannot obtain the IP address. As a result, the base station cannot operate normally. In this situation, the BSC6900 or the intermediate transport equipment must send the base station an ARP message that carries correct VLAN information. After receiving the ARP message, the base station records the VLAN ID and includes it in the DHCP message. Then, the base station
sends the DHCP message (DHCP DISCOVER) to the DHCP server through the layer 2 network. The DHCP server responds with an acknowledgement message. In this manner, the base station obtains the correct IP address and establishes a signaling link to the BSC6900. To implement VLAN detection on the BSC6900 side, the mapping between the IP address and the VLAN must be configured. l l In layer 2 networking, this IP address is the communication IP address of the base station, and the VLAN ID must be supported by the layer 2 network. In layer 3 networking, this IP address is the next-hop IP address of the port IP address of the BSC6900, and the VLAN ID (identifies the VLAN between the BTS/NodeB and the layer 3 devices) must be supported by the layer 2 devices.
For UMTS, the STR NODEBDETECT command is used to enable the VLAN detection function so that the detection based on a single NodeB and on multiple NodeBs is supported. The BSC6900 periodically sends the VLAN ID to the NodeBs. Therefore, when a NodeB is added or a faulty NodeB is restored, the NodeB can automatically obtain its VLAN ID from the BSC6900. For GSM, the BTS Detect Switch can be set to OPEN to enable the VLAN detection function.
2.52.9 Parameters
This chapter describes the parameters related to IP transport architecture description. For the meaning of each parameter, see Table 2-148. For the default value, value ranges, and MML commands of each parameter, see Table 2-149. Table 2-148 Parameter Description (1) Parameter Subrack No. Description Number of the subrack Whether to compress the address and control fields. If this parameter is set to ENABLE, the address and control area compression is enabled. If this parameter is set to DISABLE, the address and control area compression is disabled. Uniquely identifies an adjacent node Retransmission times upon ARP timeout. When the ARP request times exceeds the retransmission time without a response, the ARP/BFD detection failure alarm is reported. This may trigger the port or board switchover. ARP packet timeout time
Address and control field compress Adjacent Node ID
ARP packet resend times ARP packet timeout[100ms]
Issue 08 (2011-09-30)
911
Parameter
Description Whether the self-negotiation mode is adopted 1. When the FG2 board is used and the port type is GE, the self-negotiation mode must be adopted. 2. If the self-negotiation mode is adopted, the FE port rate, working mode and flow control mode must be in accordance with the negotiation result. If the self-negotiation mode is not adopted, the FE port rate, working mode and flow control mode must be specified. Make sure that the specified attributes are the same as that of the peer. Otherwise, transmission failure must be incurred. 3. If the selfnegotiation mode is adopted on the local system, the peer must use the self-negotiation mode. IP address of the backup port Mask of the backup port Timeout times of the BFD packet. If several consecutive BFD packets are not received, the BFD session is set to the DOWN state. Whether to use the device IP address as the local IP address. When this parameter is set to "YES", the device IP address is used as the local IP address of the PPP link. When this parameter is set to "NO", the device IP address is not used as the local IP address of the PPP link. In this case, you need to reconfigure the local IP address of the PPP link. Board type Board type Board type BTS detection switch. If the parameter is set to "CLOSE", the function of detecting the BTS is disabled. If the parameter is set to "OPEN", the function of detecting the BTS is enabled. When the function of detecting the BTS is enabled, the BSC6900 performs addressing according to the BTS IP address and sends the UDP packet carrying the VLANID to the BTS. Detection index. The index is a unique value ranging from 0 to 511 if it is not specified. Type of the detection that is performed between the BSC and the gateway.
Auto negotiation Backup port IP address Backup port mask Detect multiplier of BFD packet
Borrow DevIP Board type. Board type Board type
BTS Detect Switch Check Index Check type
Issue 08 (2011-09-30)
912
Parameter
Description The field indicates whether the cross-connect path is available. When the cross-path is available, a maximum of four IP paths exists. The four IP paths are the IP path between the first local IP address and the first peer IP address, the IP path between the first local IP address and the second peer IP address, the IP path between the second local IP address and the first peer IP address, and the IP path between the second local IP address and the second peer IP address. When the cross-path is unavailable, a maximum of two IP paths exists. The two IP paths are the IP path between the first local IP address and the first peer IP address and the IP path between the second local IP address and the second peer IP address. The destination entity number uniquely identifies a destination entity. Device IP address of the interface board used by the PPP link. The DSP index uniquely identifies a DSP. Number of the E1T1 port for bearing the PPP link Number of the E1T1 port for bearing the PPP link Destination IP address Subnet mask Type of the M3UA local entity. For details about the ASP and IPSP, see RFC4666. M3UA_ASP: suggested to use when there is a signaling transfer point (STP) between the local entity and the destination entity M3UA_IPSP: suggested to use when there is no signaling transfer point (STP) between the local entity and the destination entity CRC verification mode CRC verification mode Maximum time of delay for multiplexing. This parameter is used for the system to send the multiplexed data. If the time for buffering the data exceeds this value, the system does not wait for the multiplexing of other packets. In this way, the overlong delay can be prevented. MP segment size,the length of packet should be bigger or equel with it. Local IP address of the MP group IP address of the next hop Local IP address of the MP group
Cross IP address available flag Destination entity No. Borrowed device IP address DSP index E1T1 port No. E1T1 port No. Destination IP address Destination address mask
Local entity type CRC check mode CRC check mode
Maximum Delay Time[ms] MP flake size Local IP address Next Hop IP address. Local IP address
Issue 08 (2011-09-30)
913
Parameter Head compress Head compress
Description Compression function of the IP header of the PPP link Compression function of the IP header of the PPP link Aggregation mode. When this parameter is set to static aggregation, the LACP protocol is activated; otherwise, the LACP protocol is deactivated. The local entity number uniquely identifies a local entity. Initial bearing tag of the M3UA link. This parameter can be set to either active mode or standby mode. For details about the relevant bearer tag, see the the parameter "Traffic mode" of the "ADD M3LKS". Signaling link mask corresponding to the M3UA link set. It is used for the M3UA link load sharing. In the value, the number of 1s (represented by n) determines the maximum number (2) of links for the load sharing. For example, B0000 indicates that up to one link is used for the load sharing, B0001 and B0002 indicate that up to two links are used for the load sharing. The additional links are not used for the load sharing. The AND operation between this value and " signaling route mask " in the "ADD N7DPC" is equal to 0. Local IP address of the MP group Local IP address of the MP group Identifies the first local IP address that communicates with the peer end. When it is set to 0, it is invalid. This IP address must be first configured on the corresponding interface board. Identifies the second local IP address that communicates with the peer end. When it is set to 0, it is invalid. This IP address must be first configured on the corresponding interface board. Local SCTP port number Number of the M3UA service listening port Subnet mask of the MP group Subnet mask of the MP group Maximum multiplexing frame length. The value of this parameter cannot be less than the maximum PPPMUX sub-frame length (MUXMAXSFL). This parameter can be associated with the maximum segment length of the MP to control whether to segment the multiplexed MP. To enable the PPPMUX, the number of sub-frames must be more than or equal to 2. The following condition must be met: wMuxMaxSfL <= ( wMuxMfl-8 )/2.
Aggregation Mode Local entity No. Initial bearing traffic active tag
Signalling link mask Local IP address Local IP address
First local IP address Second local IP address Local SCTP port No. M3UA service listening port No. Subnet mask Subnet mask Maximum Frame Length[byte]
PPP mux max muxframe length
Issue 08 (2011-09-30)
914
Parameter
Description Maximum PPPMUX sub-frame length. If the PPP frame length is larger than this value, the PPPMUX multiplexing is performed. The value of this parameter cannot be larger than the maximum multiplexed frame length wMuxMfl. To enable the PPPMUX, the number of sub-frames must be more than or equal to 2. The following condition must be met: wMuxMaxSfL <= ( wMuxMfl-8 )/2 Number of MC priorities. This parameter is valid when the MP group type is MC. Minimum interval at which two BFD packets are received. Minimum interval between sent BFD packets SCTP link work mode. Server mode: BSC6900 starts the listening and waits for the peer to send the SCTP-INIT message. Client mode: BSC6900 actively sends the SCTP-INIT message. Working mode of a port. When this parameter is set to CHECK_ON_STANDBY_PORT, the connectivity check is performed on the standby port. When this parameter is set to CHECK_ON_INDEPENDENT_PORT, the connectivity check is performed on the independent port. When this parameter is set to CHECK_ON_PRIMARY_PORT, the connectivity check is performed on the active port. Number of an MLPPP group on a BTS. It is unique in a BTS. The scope of the number of th MLPPP group in the BTS3900 series is 0~1. MP type Maximum transmission unit Maximum waiting duration when the MUX operation is performed for the sub-frame over the PPPMUX link IP packet multiplexing type Number of the NBAP service listening port Next hop IP path ID Type of the IP path Pending timer of the M3UA link set The peer IP address should not be the same as the local address. The peer IP address should not be the same as the local address.
PPP mux max subframe length MC PRI number Min interval of BFD packet receive [ms] Min interval of BFD packet send [ms] Signalling link mode
Check mode MLPPP Group No. MP type MTU[Byte] PPP mux framing out-time[us] IP MUX Type NBAP service listening port No. Forward route address IP path ID IP path type PENDING timer Peer IP address Peer IP address
Issue 08 (2011-09-30)
915
Parameter Peer IP address First destination IP address Second destination IP address Peer IP address Peer subnet mask Destination SCTP port No. Protocal field compress Protocol field compress
Description The peer IP address should not be the same as the local address. First destination IP address. The invalid value is 0. Second destination IP address. The invalid value is 0. The peer IP address should not be the same as the local address. Subnet mask of the peer IP Destination SCTP port number Compression flag of the PPP link protocol domain Compression flag of the PPP link protocol domain Maximum multiplexing frame length. The length of the multiplexed packet must not exceed the maximum multiplexing frame length. If the length of the multiplexed packet exceeds the maximum multiplexing frame length, the packet is transferred without being added with new subframes. The frame length refers to the payload, excluding the IP/UDP header. Ethernet port PPP link number PPP link number Whether to enable the PPP frame multiplexing function. If this parameter is set to ENABLE, the PPP frame multiplexing function is enabled. If this parameter is set to DISABLE, the PPP frame multiplexing function is disabled. Route priority. The highest priority is represented by 0. Priority of the signaling link. 0 indicates the highest priority. A lowpriority link carries services only when the high-priority link is faulty. Route priority. The boards FG2a, GOUa, UOIa(IP), FG2c, and GOUc support the configuration of routes with different priorities. Suppose two or more routes are configured and their addresses and masks are the same, and the addresses of the next hops and priorities. These routes can be configured in the active and standby mode. When the route with higher priority is available and only this route is valid, the system switches to the route with lower priority once the route with higher priority fails. Ethernet port type Whether to back up the data of the board
Maximum Frame Length Port No. PPP link No. PPP sub-link No.
PPP mux Route priority Signalling link priority
Priority Port type Backup

Issue 08 (2011-09-30)
Parameter
Description Routing context. The routing context identifies a specified route. If the routing context is to be configured, its value must be negotiated between the two ends. Receive bandwidth of IP path SCTP link number of XPU board. This number identifies an SCTP link uniquely. To identify an signaling link set index uniquely. ID of an M3UA link in the specified link set Signaling route load sharing. In the value, the number of 1s (represented by n) determines the maximum number (2) of routes for the load sharing. For example, B0000 indicates that up to one route is used for the load sharing, B0001 and B1000 indicate that up to two routes are used for the load sharing. The additional routes are not used for the load sharing. The AND operation between this value and " signaling link mask " in the link set is equal to 0. Slot number for running this command Uniquely identifies an OSP Service type of the IP interface board. The service type can be CS speech, CS data, PS high priority, or PS low priority. Maximum sub-frame length. This parameter indicates the maximum sub-frame length for multiplexing. If the length of a sub-frame exceeds this value, the sub-frame is not multiplexed. Maximum sub-frame length. The data stream to be multiplexed on the same multiplexing channel must be of the same type, and the length of the packet before multiplexing cannot exceed the maximum subframe length. If the length of a packet exceeds the maximum subframe length, the packet is transmitted without being multiplexed. Longest waiting time for multiplexing When the multiplexed packet is no longer added with new data and the timer expires, the multiplexed packet is transmitted directly. This parameter is determined by the number of multiplexed packets. When the number of multiplexed packets increases, the value of this parameter increases.
Routing Context backward bandwidth SCTP link No. Signalling link set index Signaling link ID
Signalling route mask Main Board Logic slot No. OSP index Service Type Max subframe length[byte]
Max Subframe Length
Time Out
Issue 08 (2011-09-30)
917
Parameter
Description Traffic mode of the M3UA link set. At present, only the active/standby and load sharing mode is available. If the M3UA links in the link set work in overriding mode, only one link in the link set works in the active mode, and all other links work in the standby mode. In this case, only the active link carries traffic, and the standby links do not carry any traffic. When the active link is faulty, the standby link with the highest priority is automatically activated to take over as the active link. If the M3UA links in the link set work in load-sharing mode, all the M3UA links in the link set work in active mode and carry traffic. Port number of the aggregation member aggregation group number Bearer E1T1 port timeslot Bearer E1T1 port timeslot Transmit bandwidth of IP path UDP multiplexing mode of the receiving party. The mode that does not support the function of compressing the RTP header indicates that the receiving party supports the UDP MUX RTP header but not the function of compressing the RTP header. The mode that supports the function of compressing the RTP header indicates that the receiving party supports both the UDP MUX RTP header and the function of compressing the RTP header. UDP multiplexing mode of the sending party. If the mode that does not support the function of compressing the RTP header indicates that the sending party supports the UDP MUX RTP header but not the function of compressing the RTP header. The mode that supports the function of compressing the RTP header indicates that the sending party supports both the UDP MUX RTP header and the function of compressing the RTP header. VLANID of the IP address of the specified next hop Whether to trigger an active/standby port switchover. If this parameter is set to YES, an active/standby port switchover is triggered when a fault is detected on the active port. If this parameter is set to NO, an active/standby port switchover is not triggered when a fault is detected on the active port. Working mode of the M3UA link set, including M3UA_ASP and M3UA_IPSP. For details about the ASP and IPSP, see the RFC4666. VLAN priority
Traffic mode Trunk Link No. Trunk No. Bearing time slot Bearing time slot forward bandwidth
Receive UDP MUX Mode
Sender UDP MUX Mode VLAN ID.
Whether affect the port swapping Work mode VLAN Priority
Issue 08 (2011-09-30)
918
Table 2-149 Parameter Description (2) Parameter Defaul t Value GUI Value Range Actual Value Range U ni t MML Command Im pa ct
SWP BRD(Mandatory) STR BKP(Mandatory) CMP BRDAREA (Optional) ULD LOGTOOMU (Mandatory) STR CPUUSAGETST (Mandatory) ULD RSTINFO (Mandatory) ADD BRD(Mandatory) SET PWRPARA (Mandatory) SET FANSPEED (Mandatory) SET SCUPORT (Mandatory) ADD EMU(Mandatory) SET ALMPORT (Mandatory) DLD TCFILE (Mandatory) SET XPUPORT (Mandatory) ADD XPUVLAN (Mandatory) SET MPUBIND (Mandatory) LOD FAN(Optional) SET DPUBRDTYPE (Mandatory) CMP BRDVER (Optional) SYN BRDAREA (Optional) COL FAMLOG (Mandatory) N on e CMP LICENSE (Optional) FMT DATA(Optional) No ne
Subrack No.
None
0~11
0~11
Issue 08 (2011-09-30)
919
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
U ni t
MML Command
Im pa ct
CMP TBLDATA (Mandatory) SET CFGDATAINEFFECTIVE(Mandatory) SET CFGDATAEFFECTIV E(Optional) SET MSPCMD (Mandatory) SET E1T1LOP (Mandatory) LOP E1T1(Mandatory) STR E1T1TST (Mandatory) SET OPTLOP (Mandatory) PING IP(Mandatory) TRC IPADDR (Mandatory) SWP ETHPORT (Mandatory) SET QUEUEMAP (Mandatory) SET E1T1(Mandatory) SET MSP(Mandatory) ADD TSCROSS (Mandatory) ADD DEVIP (Mandatory) ADD IPRT(Mandatory) SET OPT(Mandatory) SET COPTLNK (Mandatory) SET ETHPORT (Mandatory) ADD ETHREDPORT (Mandatory) ADD PPPLNK (Mandatory)
Issue 08 (2011-09-30)
920
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
U ni t
MML Command
Im pa ct
ADD MPGRP (Mandatory) Address and control field compress Disable (Disable), Enable (Enable) N on e ADD PPPLNK (Optional) ADD MPGRP(Optional) ADD ADJNODE (Mandatory) ADD IPPATH(Mandatory) ADD ADJMAP (Mandatory) PP P lin k Ad jac ent no de Et her net por t Et her net por t Et her net por t No ne Et her net por t Cu rre nt BF D ses sio n
Enable
Disable, Enable
Adjacent Node ID
None
0~4599
0~4599
N on e
ARP packet resend times
3~10
3~10
N on e
STR IPCHK(Optional)
ARP packet time-out [100ms]
3~10
3~10
m s
STR IPCHK(Optional)
Auto negotiation Backup port IP address
None
ENABLE, DISABLE
ENABLE, DISABLE 0.0.0.0~255. 255.255.255
N on e N on e
SET ETHPORT (Optional)
None
None
STR IPCHK(Optional)
Backup port mask
None
None
0.0.0.0~255. 255.255.255
N on e
STR IPCHK(Optional)
Detect multiplier of BFD packet
3~10
3~10
N on e
STR IPCHK(Optional)
Issue 08 (2011-09-30)
921
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
U ni t N on e
MML Command
Im pa ct M P gro up Et her net por t BS C6 90 0 BS C6 90 0
Borrow DevIP
None
NO(NO), YES(YES) FG2a, GOUa, FG2c, GOUc
NO, YES FG2a, GOUa, FG2c, GOUc
ADD PPPLNK (Mandatory) ADD MPGRP(Mandatory)
Board type.
None
N on e N on e N on e N on e N on e N on e
SET ETHPORT (Mandatory)
Board type
None
PEUa, POUc
PEUa, POUc
ADD MPGRP (Mandatory)
Board type
None
PEUa, POUc CLOSE (CLOSE), OPEN (OPEN)
PEUa, POUc
ADD MPLNK (Mandatory)
BTS Detect Switch
CLOSE
CLOSE, OPEN
SET BTSOTHPARA (Optional)
BT S No ne No ne
Check Index
None
0~511 SBFD, ARP, MBFD UNAVAI LABLE (UNAVAI LABLE), AVAILAB LE (AVAILA BLE)
0~511 SBFD, ARP, MBFD
STR IPCHK(Optional) STR IPCHK (Mandatory)
Check type
None
Cross IP address available flag
UNAV AILAB LE
UNAVAIL ABLE, AVAILABL E
N on e
ADD SCTPLNK (Optional) ADD M3DE (Mandatory) ADD M3RT(Mandatory) ADD M3LKS (Mandatory)
SC TP lin k BS C6 90 0
Destination entity No.
None
0~186
0~186
N on e
Issue 08 (2011-09-30)
922
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
U ni t N on e
MML Command
Im pa ct BS C6 90 0
Borrowed device IP address
None
None
0.0.0.0~255. 255.255.255
ADD PPPLNK (Mandatory) ADD MPGRP(Mandatory) ADD N7DPC (Mandatory) ADD MTP3RT(Mandatory) ADD MTP3LKS (Mandatory) ADD M3DE(Mandatory) ADD GCNNODE (Mandatory) ADD GEXTSMLC (Mandatory)
DSP index
None
0~186
0~186 0~31 (PEUa), 0~251(E1 of POUc), 0~335(T1 of POUc)
N on e
SC CP
E1T1 port No.
None
0~335
N on e N on e N on e N on e
ADD MPLNK(Optional)
M P lin k PP P lin k IP rou te IP rou te
E1T1 port No. Destination IP address Destination address mask
None
0~335
0~335 0.0.0.0~255. 255.255.255 0.0.0.0~255. 255.255.255
ADD PPPLNK (Optional)
None
None
ADD IPRT(Mandatory)
None
None M3UA_A SP (M3UA_A SP), M3UA_IP SP (M3UA_I PSP) None (None), 16bit (16bit), 32bit (32bit)
ADD IPRT(Mandatory)
Local entity type
None
M3UA_AS P, M3UA_IPS P
N on e
ADD M3LE(Mandatory)
SC CP
CRC check mode

Issue 08 (2011-09-30)
16bit
None, 16bit, 32bit
N on e
ADD MPLNK(Optional)
M P lin k
923
Parameter
Defaul t Value
GUI Value Range None (None), 16bit (16bit), 32bit (32bit)
Actual Value Range
U ni t
MML Command
Im pa ct
CRC check mode Maximum Delay Time [ms]
16bit
None, 16bit, 32bit
N on e m s
PP P lin k No ne M P gro up M P gro up BS C6 90 0 M P gro up
1~30
1~30
ADD IPMUX(Optional)
MP flake size
256
128~1024
128~1024
by te N on e N on e N on e
ADD MPGRP(Optional)
Local IP address
None
None
0.0.0.0~255. 255.255.255
Next Hop IP address.
None
None
0.0.0.0~255. 255.255.255
ADD VLANID (Mandatory)
Local IP address
None
None No_HC (No_HC), UDP/ IP_HC (UDP/ IP_HC), RTP/UDP/ IP_HC (RTP/ UDP/ IP_HC)
0.0.0.0~255. 255.255.255
Head compress
UDP/ IP_HC
No_HC, UDP/ IP_HC, RTP/UDP/ IP_HC
N on e
ADD MPGRP(Optional)
M P gro up
Issue 08 (2011-09-30)
924
Parameter
Defaul t Value
GUI Value Range No_HC (No_HC), UDP/ IP_HC (UDP/ IP_HC), RTP/UDP/ IP_HC (RTP/ UDP/ IP_HC) STATIC_ LACP, MANUAL _AGGRE GATION
Actual Value Range
U ni t
MML Command
Im pa ct
Head compress
UDP/ IP_HC
No_HC, UDP/ IP_HC, RTP/UDP/ IP_HC STATIC_L ACP, MANUAL_ AGGREGA TION
N on e
ADD MPGRP(Optional)
M P gro up Et her net por t BS C6 90 0
Aggregation Mode
None
N on e N on e
ADD ETHTRK (Mandatory) ADD M3LE(Mandatory) ADD M3DE (Mandatory)
Local entity No.
None
0~186 M3UA_M ASTER_ MOD (M3UA_ MASTER _MOD), M3UA_SL AVE_MO D (M3UA_S LAVE_M OD)
0~186
Initial bearing traffic active tag
M3UA_ MASTE R_MO D
M3UA_MA STER_MO D, M3UA_SL AVE_MOD
N on e
ADD M3LNK(Optional)
BS C6 90 0
Issue 08 (2011-09-30)
925
Parameter
Defaul t Value
GUI Value Range B0000 (B0000), B0001 (B0001), B0010 (B0010), B0011 (B0011), B0100 (B0100), B0101 (B0101), B0110 (B0110), B0111 (B0111), B1000 (B1000), B1001 (B1001), B1010 (B1010), B1011 (B1011), B1100 (B1100), B1101 (B1101), B1110 (B1110), B1111 (B1111)
Actual Value Range
U ni t
MML Command
Im pa ct
Signalling link mask
B1111
B0000, B0001, B0010, B0011, B0100, B0101, B0110, B0111, B1000, B1001, B1010, B1011, B1100, B1101, B1110, B1111
ADD M3LKS(Optional)
SC CP M P gro up M P gro up SC TP lin k
Local IP address
None
None
0.0.0.0~255. 255.255.255
Local IP address
None
None
0.0.0.0~255. 255.255.255
First local IP address
None
None
0.0.0.0~255. 255.255.255
ADD SCTPLNK (Mandatory)
Issue 08 (2011-09-30)
926
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
U ni t N on e N on e N on e N on e N on e by te
MML Command
Im pa ct SC TP lin k SC TP lin k SC TP lin k M P gro up M P gro up No ne PP P lin k PP P lin k M P gro up Et her net por t
Second local IP address
None
None
0.0.0.0~255. 255.255.255
ADD SCTPLNK (Optional)
Local SCTP port No. M3UA service listening port No.
None
1024~655 35
1024~65535
2905
1024~655 35
1024~65535
SET SCTPSRVPORT (Optional)
Subnet mask
None
None
0.0.0.0~255. 255.255.255
Subnet mask Maximum Frame Length[byte] PPP mux max muxframe length PPP mux max subframe length
None
None
0.0.0.0~255. 255.255.255
1031
24~1031
24~1031
ADD IPMUX(Optional)
256
1~1500
1~1500
by te
64
1~746
1~746
by te N on e
MC PRI number Min interval of BFD packet receive [ms]
None
4,8
4, 8
ADD MPGRP(Optional)
100
10~1000
10~1000
m s
STR IPCHK(Optional)
Issue 08 (2011-09-30)
927
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
U ni t
MML Command
Im pa ct Et her net por t
Min interval of BFD packet send [ms]
100
10~1000 SERVER (SERVER MOD), CLIENT (CLIENT MOD) CHECK_ ON_INDE PENDEN T_PORT, CHECK_ ON_PRIM ARY_PO RT, CHECK_ ON_STA NDBY_P ORT
10~1000
m s
STR IPCHK(Optional)
Signalling link mode
None
SERVER, CLIENT
N on e
SC TP lin k
Check mode
None
CHECK_O N_INDEPE NDENT_P ORT, CHECK_O N_PRIMAR Y_PORT, CHECK_O N_STAND BY_PORT
N on e
STR IPCHK(Optional) ADD BTSMPGRP (Mandatory) ADD BTSMPLNK (Mandatory) IMP BTSMPGRP (Mandatory) IMP BTSMPLNK (Mandatory)
No ne
MLPPP Group No.
None
0~3
0~3
N on e N on e
BT S M P gro up Et her net por t M P gro up
MP type
MCPPP
MLPPP, MCPPP
MLPPP, MCPPP
ADD MPGRP(Optional)
MTU[Byte] PPP mux framing outtime[us]
None
256~1650
256~1650
by te
SET ETHPORT (Optional)
1000
1~1500
1~1500
ls
Issue 08 (2011-09-30)
928
Parameter
Defaul t Value
GUI Value Range UDPMUX , ABISMU X, ATERMU X
Actual Value Range
U ni t
MML Command
Im pa ct
IP MUX Type M3UA service listening port No. Forward route address
None
UDPMUX, ABISMUX, ATERMUX
ADD IPMUX (Mandatory)
No ne SC TP lin k IP rou te IP pat h
None
1024~655 35
1024~65535 0.0.0.0~255. 255.255.255
SET SCTPSRVPORT (Optional)
None
None
ADD IPRT(Mandatory) ADD IPPATH (Mandatory)
IP path ID
None
0~65535 QoS(QoS), BE(BE), AF11 (AF11), AF12 (AF12), AF13 (AF13), AF21 (AF21), AF22 (AF22), AF23 (AF23), AF31 (AF31), AF32 (AF32), AF33 (AF33), AF41 (AF41), AF42 (AF42), AF43 (AF43), EF(EF) 1~10
0~65535
IP path type PENDING timer
None 5
QoS, BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42, AF43, EF 1~10
N on e s
ADD IPPATH(Optional) ADD M3LKS(Optional)
IP pat h SC CP
Issue 08 (2011-09-30)
929
Parameter
Defaul t Value
GUI Value Range
Actual Value Range 0.0.0.0~255. 255.255.255 0.0.0.0~255. 255.255.255 0.0.0.0~255. 255.255.255
U ni t N on e N on e N on e N on e N on e N on e N on e N on e N on e N on e by te
MML Command
Im pa ct IP pat h IP pat h IP pat h SC TP lin k SC TP lin k IP pat h IP pat h SC TP lin k PP P lin k M P lin k BT S
Peer IP address Peer IP address Peer IP address First destination IP address Second destination IP address Peer IP address Peer subnet mask Destination SCTP port No. Protocal field compress Protocol field compress Maximum Frame Length
None
None
ADD IPPATH (Mandatory) ADD IPPATH (Mandatory) ADD IPPATH (Mandatory)
None
None
None
None
None
None
0.0.0.0~255. 255.255.255
None
None
0.0.0.0~255. 255.255.255 0.0.0.0~255. 255.255.255 0.0.0.0~255. 255.255.255
ADD SCTPLNK (Optional) ADD IPPATH (Mandatory)
None 255.255 . 255.255
None
None
ADD IPPATH(Optional)
None
1024~655 35 Disable (Disable), Enable (Enable) Disable (Disable), Enable (Enable)
1024~65535
Enable
Disable, Enable
Enable
Disable, Enable
ADD MPGRP(Optional) ADD BTSABISMUXFLOW (Optional)
1031
24~1031
24~1031
Issue 08 (2011-09-30)
930
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
U ni t
MML Command
Im pa ct
SET ETHPORT (Optional) 0~7(FG2a), 0~1(GOUa), 0~11 (FG2c), 0~3 (GOUc) ADD ETHREDPORT (Mandatory) N on e N on e N on e N on e N on e N on e N on e ADD ETHIP (Mandatory) ADD ETHMEP (Mandatory) Et her net por t PP P lin k M P lin k M P gro up SC CP No ne IP rou te Et her net por t Bo ard BS C6 90 0
Port No.
None
0~11
PPP link No.
None
0~499
0~499
PPP sub-link No.
None
0~499 Disable (Disable), Enable (Enable)
0~499
ADD MPLNK(Optional) ADD PPPLNK (Optional) ADD MPGRP(Optional) ADD MTP3RT (Optional) ADD M3RT (Optional) ADD MTP3LNK (Optional) ADD M3LNK(Optional)
PPP mux Route priority Signalling link priority
Disable
Disable, Enable
0~99
0~99
0~99 HIGH, LOW
0~99 HIGH, LOW
Priority
None
ADD IPRT(Mandatory)
Port type
None
FE, GE YES (YES), NO (NO)
FE, GE
N on e N on e N on e
SET ETHPORT (Mandatory)
Backup
None
YES, NO
ADD BRD(Mandatory)
Routing Context
429496 7295
0~429496 7295
0~42949672 95
ADD M3LE(Optional) ADD M3DE(Optional)
Issue 08 (2011-09-30)
931
Parameter
Defaul t Value
GUI Value Range 1~300000 0
Actual Value Range
U ni t kb it/ s N on e
MML Command
Im pa ct IP pat h SC TP lin k
backward bandwidth
None
1~3000000
ADD IPPATH (Mandatory) ADD SCTPLNK (Mandatory) ADD M3LNK(Mandatory) ADD M3RT (Mandatory)
SCTP link No.
None
0~1199
0~1199
Signalling link set index
None
0~186
0~186
N on e N on e
ADD M3LKS (Mandatory) ADD M3LNK (Mandatory)
BS C6 90 0 BS C6 90 0
Signaling link ID
None
0~15
0~15
ADD M3LNK (Mandatory)
Issue 08 (2011-09-30)
932
Parameter
Defaul t Value
GUI Value Range B0000 (B0000), B0001 (B0001), B0010 (B0010), B0011 (B0011), B0100 (B0100), B0101 (B0101), B0110 (B0110), B0111 (B0111), B1000 (B1000), B1001 (B1001), B1010 (B1010), B1011 (B1011), B1100 (B1100), B1101 (B1101), B1110 (B1110), B1111 (B1111) 0,2,4,8,10, 12,14,16,1 8,20,22,24, 26
Actual Value Range
U ni t
MML Command
Im pa ct
Signalling route mask Main Board Logic slot No.
B0000
B0000, B0001, B0010, B0011, B0100, B0101, B0110, B0111, B1000, B1001, B1010, B1011, B1100, B1101, B1110, B1111 0, 2, 4, 8, 10, 12, 14, 16, 18, 20, 22, 24, 26
N on e N on e N on e
ADD N7DPC(Optional) SWP ETHPORT (Mandatory) ADD ETHREDPORT (Mandatory) ADD OPC(Mandatory) ADD N7DPC (Mandatory) ADD M3LE(Mandatory)
SC CP
None
No ne
OSP index
None
0~4
0~4
SC CP
Issue 08 (2011-09-30)
933
Parameter
Defaul t Value
GUI Value Range CSVOICE (CS Voice), CSDATA (CS Data), PSHIGHP RI(PS High PRI), PSLOWP RI(PS Low PRI)
Actual Value Range
U ni t
MML Command
Im pa ct
Service Type Max subframe length[byte] Max Subframe Length
None
CSVOICE, CSDATA, PSHIGHPR I, PSLOWPRI
N on e by te by te m s
ADD BTSABISMUXFLOW (Mandatory)
BT S No ne BT S BT S
352
16~1023
16~1023
ADD IPMUX(Optional) ADD BTSABISMUXFLOW (Optional) ADD BTSABISMUXFLOW (Optional)
352
16~1023
16~1023 5~200 (step: 0.1)
Time Out
200
5~200 M3UA_O VERRIDE _MOD (Active/ Standby Mode), M3UA_L OADSHA RE_MOD (Load Sharing Mode)
Traffic mode
M3UA_ LOADS HARE_ MOD
M3UA_OV ERRIDE_M OD, M3UA_LO ADSHARE _MOD 0~7(FG2a), 0~1(GOUa), 0~11 (FG2c), 0~3 (GOUc)
N on e
ADD M3LKS(Optional)
SC CP Et her net por t
Trunk Link No.
None
0~11
N on e
ADD ETHTRKLNK (Mandatory) ADD ETHTRK (Mandatory)
Trunk No.
None
0~11
0~7(FG2a), 0~1(GOUa), 0~11 (FG2c), 0~3 (GOUc)
N on e
ADD ETHTRKLNK (Mandatory) ADD ETHTRKIP (Mandatory)
Et her net por t
Issue 08 (2011-09-30)
934
Parameter
Defaul t Value
GUI Value Range TS1, TS2, TS3, TS4, TS5, TS6, TS7, TS8, TS9, TS10, TS11, TS12, TS13, TS14, TS15, TS16, TS17, TS18, TS19, TS20, TS21, TS22, TS23, TS24, TS25, TS26, TS27, TS28, TS29, TS30, TS31
Actual Value Range
U ni t
MML Command
Im pa ct
Bearing time slot
None
TS1, TS2, TS3, TS4, TS5, TS6, TS7, TS8, TS9, TS10, TS11, TS12, TS13, TS14, TS15, TS16, TS17, TS18, TS19, TS20, TS21, TS22, TS23, TS24, TS25, TS26, TS27, TS28, TS29, TS30, TS31
N on e
ADD MPLNK (Mandatory)
M P lin k
Issue 08 (2011-09-30)
935
Parameter
Defaul t Value
GUI Value Range TS1, TS2, TS3, TS4, TS5, TS6, TS7, TS8, TS9, TS10, TS11, TS12, TS13, TS14, TS15, TS16, TS17, TS18, TS19, TS20, TS21, TS22, TS23, TS24, TS25, TS26, TS27, TS28, TS29, TS30, TS31 1~300000 0 NORTPC OMP, RTPCOM PP NORTPC OMP, RTPCOM P
Actual Value Range
U ni t
MML Command
Im pa ct
Bearing time slot forward bandwidth Receive UDP MUX Mode
None
TS1, TS2, TS3, TS4, TS5, TS6, TS7, TS8, TS9, TS10, TS11, TS12, TS13, TS14, TS15, TS16, TS17, TS18, TS19, TS20, TS21, TS22, TS23, TS24, TS25, TS26, TS27, TS28, TS29, TS30, TS31
N on e kb it/ s N on e N on e N on e N on e
ADD MPLNK (Mandatory) ADD IPPATH (Mandatory)
M P lin k IP pat h
None
1~3000000 NORTPCO MP, RTPCOMP NORTPCO MP, RTPCOMP
None
ADD IPMUX (Mandatory)
No ne
Sender UDP MUX Mode
None
ADD IPMUX (Mandatory) ADD IPPATH (Mandatory) ADD VLANID(Mandatory)
No ne BS C6 90 0
VLAN ID. Whether affect the port swapping
None
2~4094
2~4094
None
NO(NO), YES(YES)
NO, YES
STR IPCHK(Optional)
No ne
Issue 08 (2011-09-30)
936
Parameter
Defaul t Value
GUI Value Range M3UA_A SP (M3UA_A SP), M3UA_IP SP (M3UA_I PSP)
Actual Value Range
U ni t
MML Command
Im pa ct
Work mode
M3UA_ ASP
M3UA_AS P, M3UA_IPS P
N on e N on e
ADD M3LKS(Optional)
SC CP BS C6 90 0
VLAN Priority
None
0~7
0~7
SET DSCPMAP (Optional)
2.52.10 Counters
2.52.11 Glossary
2.52.12 Appendix
To implement IP RAN, IP interface boards need to be configured on the BSC6900 and BTS/ NodeB. For details about the IP interface boards, see the hardware description document of each network element. Table 2-150 lists the IP interface boards of the BSC6900. Table 2-150 IP interface boards of the BSC6900 Board Name PEUa POUa Port Type E1/T1 E1/T1 Port Number 031 E1 ports: 0125 T1 ports: 0167 UOIa Unchannelized STM-1/OC-3C optical port Ch-STM-1/ OC-3C optical port 03 Board backup Reliability Mode Supported Board backup Board backup
POUc
03
Board backup
Issue 08 (2011-09-30)
937
Board Name FG2a
Port Type FE/GE electrical port
Port Number FE electrical ports: 07 GE electrical ports: 0 and 1 (correspond to FE ports 0 and 3)
Reliability Mode Supported Board backup/Port backup/ Ethernet load sharing/Ethernet link aggregation/Route-based port backup and route-based load sharing
GOUa
GE optical port
GE optical ports: 01
Board backup/Port backup/ Ethernet load sharing/Ethernet link aggregation/Route-based port backup and route-based load sharing Board backup/Port backup/ Ethernet load sharing/Ethernet link aggregation/Route-based port backup and route-based load sharing Board backup/Port backup/ Ethernet load sharing/Ethernet link aggregation/Route-based port backup and route-based load sharing
FG2c
FE/GE electrical port
FE electrical ports: 011 GE electrical ports: 03
GOUc
GE optical port
GE optical ports: 03

l l l l l 3GPP TR23.107: Quality of Service (QoS) concept and architecture 3GPP TR25.933: IP transport in UTRAN 3GPP TS 48.103: Base Station System - Media GateWay (BSS-MGW) interface; User plane transport mechanism 3GPP TS 48.008: Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification IEEE 802.1Q: Virtual LANs, defines the operation of Virtual LAN (VLAN) Bridges that permit the definition, operation and administration of Virtual LAN topologies within a Bridged LAN infrastructure. IEEE 802.1ag: Connectivity Fault Management IEEE 802.3ah: Ethernet in the first mile IETF DRAFT (02-2002): SS7 MTP3-User Adaptation Layer (M3UA) IP CLK1000 product documentation RFC894: A Standard for the Transmission of IP Datagrams over Ethernet Networks RFC1042: A Standard for the Transmission of IP Datagrams over IEEE 802 Networks
l l l l l l
Issue 08 (2011-09-30)
l l l l l l l
RFC1661: The Point-to-Point Protocol (PPP), provides a standard method for transporting multi-protocol datagrams over point-to-point links RFC1662: PPP in HDLC-link Framing, describes the use of HDLC-like framing for PPP encapsulated packets RFC1889(01/1996): RTP: A Transport Protocol for Real Time Applications RFC1990: The PPP Multilink Protocol (ML-PPP), describes a method for splitting, recombining and sequencing datagrams across multiple logical data links RFC2131: Dynamic Host Configuration Protocol RFC2132: DHCP Options and BOOTP Vendor Extensions RFC2686: The Multi-Class Extension to Multi-link PPP (MC-PPP), describes extensions that allow a sender to fragment the packets of various priorities into multiple classes of fragments, allowing high-priority packets to be sent between fragments of lower priorities RFC3153: PPP Multiplexing (PPPmux), describes a method to reduce the PPP framing overhead used to transport small packets over low bandwidth links. RFC3309 (09/2002): Stream Control Transmission Protocol (SCTP) Checksum Change TRM Parameter Description BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
l l l l l l l l l
2.53 Latency Reduction

2.53.1 Introduction
2.53.1.1 Scope
This document describes reduced transmission time interval (RTTI) temporary block flow (TBF) establishment, PDCH pair scheduling, fast ack/nack reporting (FANR) TBF establishment and FANR procedure in the latency reduction feature.

Issue 08 (2011-09-30)

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the latency reduction feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Version
02 (2009-09-30)
01 (2009-06-30)
2.53.2 Overview
Latency reduction is an important aspect in the development of the GERAN. The conversational class service in the GERAN, for example, VoIP and Gaming, is highly latency-sensitive. The end-to-end latency of the VoIP service should not exceed 300 ms to ensure user satisfaction. In addition, the frame error rate (FER) of the VoIP service should not exceed 2%. When the actual FER is higher than 2%, retransmission can be performed to lower the FER if the latency allows retransmission. A reduced latency can also improve the user experience for the interactive class service and the BE service. The Latency Reduction feature is based on the RTTI technology and the FANR technology.
RTTI is a technology based on which two timeslots are combined to transmit one radio block (consisting of four bursts) on the Um interface, as shown in Figure 2-232. On each timeslot, a 10-ms radio block is used. The data that is originally contained in four bursts is transmitted through two consecutive TDMA frames on the two timeslots on the Um interface. In addition, the two timeslots can be either contiguous or non-contiguous. Figure 2-232 Working principles of RTTI
The RTTI technology reduces the latency on the Um interface, and thus the Round Trip Time (RTT) in the access network is reduced. Theoretically, the RTT is reduced from 130 ms (in BTTI transmission mode) to 60 ms (in RTTI transmission mode), and the latency of a single retransmission is reduced from 185 ms (in BTTI transmission mode) to 95 ms (in RTTI transmission mode). The BTTI of the radio block is 20 ms. In BTTI transmission mode, a radio block is transmitted on a PDCH in four consecutive TDMA frames in one radio block period. The RTTI of the radio block is 10 ms. In RTTI transmission mode, a radio block is transmitted on two PDCHs in either the first two or the last two frames of any specified radio block period. FANR is a technology based on which an efficient ACK/NACK reporting mechanism is introduced to reduce the latency during the assembling of RLC data blocks into LLC PDUs. The RTTI technology reduces only the transmission latency. In the current ACK/NACK reporting mechanism, when an RLC data block is lost or erroneous, a message cannot be sent immediately to the sender to request retransmission, and thus latency occurs during the assembling of RLC data blocks into LLC PDUs. After the FANR technology is employed, the BSC can timely report an error in the RLC data block and request retransmission. In this way, the latency during the assembling of RLC data blocks into LLC PDUs is reduced, and the signaling overhead is reduced. Figure 2-233 shows the working principles of the FANR technology. Figure 2-233 Working principles of FANR
Issue 08 (2011-09-30)
941
The Latency Reduction feature is based on the following technologies: l l RTTI FANR
The Latency Reduction feature requires the support from the MS. The MS indicates its reduced latency capability in the information elements (IEs) Mobile Station Classmark 3 and Radio Access Capability. In addition, the MS can also indicate its reduced latency capability in the cause value "One Phase Access Request by Reduced Latency MS" of the 11-bit one phase access request message EGPRS Packet Channel Request. An MS must support the RTTI technology and the FANR technology at the same time. The Latency Reduction feature can only be enabled in cells that support EDGE. In addition, to enable this feature, you need to set the Support Reduced Latency Capability parameter to Support.

2.53.3.1 RTTI
?.1. Overview
To reduce the end-to-end latency and improve user satisfaction, the 3GPP GERAN determines the target of latency reduction. That is, in non-ideal radio environment, the first access latency for the MS must be shorter than 450 ms, and the RTT after access must be shorter than 100 ms. The internal latency of the BTS or the BSC ranges from 5 ms to 10 ms. The latency on the Gb interface is considered as a part of the latency of the core network (CN). In this way, the latency of the access network mainly consists of the reaction time of the MS, the latency on the Um interface, and the latency on the Abis interface. The latency on the Um interface and that on the Abis interface are equal to TTI. Therefore, reducing TTI can effectively reduce the latency of the access network. As shown in Figure 2-234, RTTI is a technology based on which two timeslots, that is, two PDCHs, are combined to transmit one radio block (consisting of four bursts) on the Um interface. On each timeslot, a 10-ms radio block is used. The data that is originally contained in four bursts is transmitted through two consecutive TDMA frames on the two timeslots on the Um interface. In addition, the two timeslots can be either contiguous or non-contiguous. The PDCH i and PDCH j shown in Figure 2-234 form a pair, termed PDCH pair. Figure 2-234 RTTI transmission mode
Issue 08 (2011-09-30)
942
The TBF transmitted in BTTI transmission mode is termed BTTI TBF. The TBF transmitted in RTTI transmission mode is termed RTTI TBF. To enable the multiplexing of the RTTI TBF and the BTTI TBF onto the same physical channel, 3GPP TS 44.060 defines two Uplink State Flag (USF) modes, namely: BTTI USF mode and RTTI USF mode. The USFs on a downlink PDCH pair are transmitted in the same mode. When a channel is simultaneously multiplexed by the RTTI TBF and the BTTI TBF, the BTTI USF mode must be configured. When a channel transmits only RTTI TBFs, the RTTI USF mode is configured for the uplink RTTI TBF. Currently, the BSC does not support the multiplexing of RTTI TBFs and BTTI TBFs onto the same channel. l BTTI USF mode In BTTI USF mode, the USFs are transmitted through four consecutive TDMA frames on either PDCH of the downlink PDCH pair. The MS listens to the USFs. When: 1. The USFs transmitted on the first PDCH of the downlink PDCH pair correspond to the TBF, as shown in Figure 2-235, it indicates that the MS can upload one or four radio blocks (note that the number of radio blocks depends on the granularity of the USF). The MS can upload the radio blocks in the first 10 ms of the next radio block period or in the first 10 ms of the radio block period after the next. The USFs transmitted on the second PDCH of the downlink PDCH pair correspond to the TBF, as shown in Figure 2-235, it indicates that the MS can upload one or four radio blocks (note that the number of radio blocks depends on the granularity of the USF). The MS can upload the radio blocks in the second 10 ms of the next radio block period or in the second 10 ms of the radio block period after the next.
2.
Figure 2-235 BTTI TBF mode
RTTI USF mode In RTTI USF mode, the USFs are transmitted through two consecutive TDMA frames on the downlink PDCH pair. The MS listens to the USFs. When: 1. The USFs transmitted in the first 10 ms of a radio block period on the downlink PDCH pair correspond to the TBF, as shown in Figure 2-236, it indicates that the MS can upload one or four radio blocks (note that the number of radio blocks depends on the granularity of the USF). The MS can upload the radio blocks in the second 10 ms of this radio block period or in the second 10 ms of the next radio block period. The USFs transmitted in the second 10 ms of a radio block period on the downlink PDCH pair correspond to the TBF, as shown in Figure 2-236, it indicates that the MS can upload one or four radio blocks (note that the number of radio blocks depends on the granularity of the USF). The MS can upload the radio blocks in the first 10 ms of the next radio block period or in the first 10 ms of the radio block period after the next.
2.
Issue 08 (2011-09-30)
Figure 2-236 RTTI TBF mode
After the RTTI technology is employed, the USF is not pre-coded in the header of the control signaling coded according to the CS-1 coding scheme, but coded together with data. Therefore, the MS must receive all the data before decoding the USF. If the control signaling coded according to the CS-1 coding scheme is sent to the MS through 10-ms data blocks, then the traditional MS, that is, the MS that does not have the reduced latency capability, cannot obtain the USF because the traditional MS reads the channel every 20 ms. Therefore, in BTTI USF mode, the control signaling must be coded according to the protocol-stipulated MCS-0 coding scheme.
?.2. RTTI TBF Establishment

When an MS with the reduced latency capability initiates the conversational class service or the Push to talk over Cellular (PoC) service, the BSC attempts to establish the RTTI TBF for the MS. When attempting to establish the uplink TBF or downlink TBF for the MS, the BSC may not know the service type and capability of the MS. In this case, the BSC assigns the TBF to a channel in BTTI transmission mode rather than a PDCH pair in RTTI transmission mode. After obtaining the service type and capability of the MS, the BSC initiates the channel re-assignment procedure and assigns the TBF to a PDCH pair. For details on the Quality of Service (QoS) negotiation procedure of the conversational class service and the detection procedure of the PoC service, see 2.44 GPRS/EGPRS QoS. If the MS sends the 11-bit one phase access request message, EGPRS PACKET CHANNEL REQUEST, with the cause value "One Phase Access Request by Reduced Latency MS" on the CCCH, the BSC receives the message and establishes the uplink RTTI TBF through the Immediate Assignment message. In the assignment command relative to the uplink TBF, the BSC specifies whether the MS should transmit data in RTTI transmission mode or in BTTI transmission mode. When the MS transmits data in RTTI transmission mode, the BSC should specify the PDCH pair and the USF mode (BTTI or RTTI) for the TBF. In the assignment command relative to the downlink TBF, the BSC specifies whether the MS should transmit data in RTTI transmission mode or in BTTI transmission mode. When the MS transmits data in RTTI transmission mode, the BSC should specify the PDCH pair for the TBF. Two PDCHs form a PDCH pair by following the default rules defined in the related protocol. To be specific, timeslots 0 and 1 form a pair; timeslots 2 and 3 form a pair; timeslots 4 and 5 form a pair; timeslots 6 and 7 form a pair. The BSC assigns the same TTI mode to the uplink and downlink TBFs of an MS. In other words, uplink and downlink TBFs of an MS are transmitted in either RTTI transmission mode or BTTI transmission mode.
The BSC assigns a PDCH pair based on the following rules: l l The PDCH pair on a TRX that was configured with PDCH pairs is preferentially assigned. The multiplexing of the PDCH pair must be lower than RTTI PDCH Multiplex Threshold to ensure that the latency of the service carried in RTTI TBF is short. When RTTI PDCH Multiplex Threshold is set to a great value, an excessive number of RTTI TBFs are multiplexed onto a PDCH, and the RTT latency is increased. When RTTI PDCH Multiplex Threshold is set to a small value, the utilization of PDCH channel resources is not efficient. The PDCH pair is assigned on the basis of priority. The PDCH pair of the highest priority is assigned preferentially. The following lists the priority of the PDCH pairs in descending order: PDCH pair formed by timeslots 6 and 7, PDCH pair formed by timeslots 4 and 5, PDCH pair formed by timeslots 2 and 3, and PDCH pair formed by timeslots 0 and 1.
?.3. PDCH Pair Scheduling

PDCH pair scheduling refers to the scheduling of resources for the MSs multiplexed onto the same PDCH pair. Currently, the BSC does not support the multiplexing of RTTI TBFs and BTTI TBFs onto the same channel. Thus, only the scheduling in RTTI USF mode needs to be achieved. The scheduling of PDCH pairs in RTTI transmission mode differs from the scheduling of channels in BTTI transmission mode in the following aspects: l The scheduling time interval of the PDCH pairs is 10 ms. The scheduling objects are uplink PDCH pairs and downlink PDCH pairs. The scheduling blocks include RLC data blocks as well as control messages such as System Information PSI13 messages and paging messages. The Block Sequence Numbers (BSNs) of the RLC/MAC data blocks remain unchanged. The sub-block number, a or b, determines whether the RLC/MAC data block is transmitted in the first 10 ms or the last 10 ms of a specified radio block period.
Figure 2-237 Format of a 52 frames multiframe transmitted on a PDCH Pair
If the PDCHs in a cell are all occupied by BTTI TBFs, a PDCH is preempted for the transfer of the RTTI TBF. The BTTI TBFs on the preempted BTTI PDCH must be released before an RTTI TBF is assigned to the PDCH.
When either PDCH of a PDCH pair is faulty, all RTTI TBFs carried on the PDCH pair need to be released. The normal PDCH of the PDCH pair works as an independent PDCH and transmits signals in BTTI transmission mode. When CS services preempt the channels occupied by PS services, the channels in BTTI transmission mode are released before PDCH pairs.
2.53.3.2 FANR
?.1. Overview
In the current packet transfer mode, the BSC periodically sends the RRBP Poll message in the downlink direction to the MS to query the reception of downlink data. The MS, on receiving the message, sends the Packet DL Ack/Nack message to the BSC, informing the BSC of the reception of downlink data. In addition, the BSC sends the Packet UL Ack/Nack message in the downlink direction at certain times to inform the MS of the reception of uplink data. Figure 2-238 shows an example of a polling period of 12 RLC data blocks. In the downlink direction, the latency between a RLC data block loss on the MS side and the acknowledgment of the loss on the BSC side takes150 ms to 250 ms. Such a long latency is unacceptable for latency-sensitive services, such as PoC and VoIP. The cause of such a long latency is described as follows: In RLC acknowledged mode, the LLC layer sends the data from the application layer in sequential order. In this case, the RLC layer detects an RLC data block loss only after the transmission is complete. Figure 2-238 Current mechanism of ACK/NACK message reporting for downlink transmission
The current mechanism of ACK/NACK message reporting has two limitations, which are described as follows: 1. When a fault is detected, a message concerning the fault cannot be immediately sent. This problem exists in both the uplink and the downlink. In the downlink, there is a polling process. The entire ACK/NACK control block is sent to report block reception. Thus, the reaction time tends to be long and the channel resources utilization is not efficient.
2.
Issue 08 (2011-09-30)
The FANR technology is introduced to improve the mechanism of ACK/NACK message reporting. The FANR technology provides two event-based improvement methods, which are described as follows: l l When the receiver detects that an RLC data block is lost or is erroneous, the receiver can immediately send an ACK/NACK message to the sender to request retransmission. Uplink/downlink data block carrying ACK/NACK message This is achieved by sending the reception state of the ACK/NACK message together with the data block. In this way, the response speed is increased, and the signaling overhead is reduced. The Piggy-backed Ack/Nack (PAN) field inserted in the uplink/downlink EGPRS RLC/MAC data block indicates the reception of the data carried in the TBF in the reverse direction. In addition, there is a PAN indicator (PANI) in the header of the RLC/MAC data block. The PANI indicates whether the current RLC/MAC data block includes the PAN field. The PAN field is classified into the time-based FANR and SSN-based FANR. The timebased FANR is used to report the reception of only uplink TBF. Through time-based FANR, the BSC does not inform the MS of the BSN of the erroneous block, instead it notifies the MS that the data block in a certain radio block period on a certain channel is erroneous. Based on the information provided by the BSC, the MS identifies the BSN of the erroneous data block. The SSN-based FANR is used to report the reception of both uplink TBF and downlink TBF. Through the SSN-based FANR, the data block includes the ACK/NACK message. In addition, the ACK/NACK message includes the BSN, which is used as the index of the RLC data block. Huawei BSC supports only the SSN-based FANR. Therefore, after the FANR technology is employed, the receiver can timely report an error in the RLC data block and request retransmission. In this way, the latency during the assembling of RLC data blocks into LLC PDUs is reduced, and the signaling overhead is reduced.
?.2. FANR TBF Establishment

When the BSC assigns the RTTI TBF to an MS that has the reduced latency capability, the BSC forcibly enables the FANR technology. When the MS does not have the reduced latency capability or when the MS has the reduced latency capability but the number of PDCH pairs is insufficient or RTTI PDCH Multiplex Threshold is exceeded, the BSC assigns the BTTI TBF. The BSC enables the FANR technology by including two FANR-related IEs in the immediate assignment, packet assignment, and packet timeslot reassignment messages relative to the uplink TBF. The two IEs indicate: l l Whether the FANR technology is enabled for the uplink TBF. Whether the MS reports the reception of the downlink data through time-based FANR or SSN-based FANR in the case that the FANR technology is enabled. Currently, Huawei BSC supports only the SSN-based FANR.
The BSC also includes two FANR-related IEs in the messages relative to the downlink TBF. The two IEs indicate: l l Whether the FANR technology is enabled for the downlink TBF. Whether the MS uses the event-based ACK/NACK message reporting mechanisms in the case that the FANR technology is enabled.
?.3. FANR Procedure

ACK/NACK Information Reporting Mechanism

The FANR technology provides two ACK/NACK message reporting mechanisms, which are described as follows: l Polled Fast Ack/Nack Reporting In the downlink direction, when the RLC layer of the BSC sends data to an MS that is assigned the uplink FANR TBF, the BSC can trigger the FANR procedure by polling. Specifically, the BSC includes a valid CES/P field in the header of the downlink RLC/ MAC data block to the MS. l Event-based Fast Ack/Nack Reporting For details, see 2.53.3.2.1 Overview under 2.53.3.2 FANR.
FANR Procedure for the Transmission of Uplink TBF

The event-based fast Ack/Nack reporting mechanism is supported by default to report the reception of uplink data. In addition, the earlier ACK/NACK message reporting mechanisms, such as BSC periodically sending an UPLINK Ack/Nack message to report the reception of uplink data, are still retained. When an uplink data block is lost or is erroneous, the BSC can include the SSN-based PAN field in the EGPRS RLC data block or EGPRS2 RLC data block of the downlink TBF if there are FANR TBFs on the downlink PDCH or PDCH pair that the MS listens to. When an uplink data block is lost or is erroneous, the BSC sends EGPRS UPLINK ACK/NACK message on the control channel if there is no FANR TBF on the downlink PDCH or PDCH pair that the MS listens to. When the FANR procedure is enabled for the transmission of uplink TBF, the BSC includes the SSN-based PAN field in the related data block and then appropriately increases the transmission interval of EGPRS UPLINK ACK/NACK messages. The coding schemes of the first data block with the PAN field and of the retransmitted data block with the PAN field are restricted by the following conditions: 1. For the downlink data blocks with the FANR procedure enabled, if the applied coding scheme is MCS-9 or MCS-4, the coding scheme of the first data block with the PAN field must be MCS-8 or MCS-3. If the sender requires an RLC data block to be retransmitted according to the coding scheme MCS-9 (the PAN field is included in the retransmitted data block), the retransmitted data block must use the coding scheme MCS-6. If the sender requires an RLC data block to be retransmitted according to the coding scheme MCS-4 (the PAN field is included in the retransmitted data block, and fragmentation is allowed), the retransmitted data block must use the coding scheme MCS-1. If the sender requires an RLC data block to be retransmitted according to the coding scheme MCS-4 (the PAN field is included in the retransmitted data block, and fragmentation is not allowed), the retransmitted data block cannot carry the PAN field.
2.
FANR Procedure for the Transmission of Downlink TBF

After sending a Poll message to the MS, the BSC either requests the MS to include the PAN field in the uplink data block to report the reception of downlink data or requests the MS to send the DOWNLINK ACK/NACK message to report the reception of downlink data. If the MS reports the reception of downlink data through the PAN field in the uplink data block, the uplink
data block must be assigned to the TBF. When deciding on the polling method, the BSC considers the following factors: 1. 2. An adequate number of Bit Error Probability (BEP) MRs are sent for downlink LA/IR decision. For details, see 2.42 GPRS/EGPRS Link Quality Control. When the BSC detects that the MS has no uplink data to transmit during the configuration of the RRBP field, the BSC requests the MS to send the DOWNLINK ACK/NACK message. In this case, the MS can carry more ACK/NACK information. The uplink/downlink data block carrying ACK/NACK message reporting mechanism should be used whenever possible to improve transmission efficiency and save bandwidth. When the BSC requests the MS to adopt event-based fast Ack/Nack reporting mechanism, the BSC may reduce the transmission interval of the RRBP field according to the reporting of ACK/NACK message in the uplink.
3. 4.
2.53.4 Parameters
The following describes the parameters related to latency reduction. For the meaning of each parameter, see Table 2-151. For the default value, value range, and related MML commands of each parameter, see Table 2-152. Table 2-151 Parameter description (1) Parameter Support Reduced Latency Capability Description Cell supports reduced latency capability. This parameter is used to reduce the latency during the transmission, thus improving the user experience for conversational services. Maximum number of RTTI TBFs that can be multiplexed on the PDCH. A PDCH can be assigned when the number of RTTI TBFs on it is smaller than the value of this parameter. This parameter is valid only when its value is smaller than or equal to "MSRD PDCH DL Multiplexing Threshold".
RTTI PDCH Multiplex Threshold
Table 2-152 Parameter description (2) Paramete r Default Value GUI Value Range UNSUPP ORT(Not Support), SUPPOR T (Support) Actual Value Range Unit MML Comman d Impact
Support Reduced Latency Capability
UNSUPP ORT
None
SET GCELLG PRS (Optional)
Cell
Issue 08 (2011-09-30)
949
Paramete r RTTI PDCH Multiplex Threshold
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLPS CHM (Optional)
Impact
30
10~80
10~80
None
Cell
2.53.5 Counters
2.53.6 Glossary

l l 3GPP TS 43.064: "General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2" 3GPP TS 44.060: "General Packet Radio Service(GPRS); Mobile Station(MS)-Base Station System (BSC) interface; Radio Link Control/Medium Access Control(RLC/MAC) protocol" 3GPP TR 45912-720: "Feasibility study for evolved GSM/EDGE Radio Access Network (GERAN)" 3GPP TS 45.003: "Radio Access Network; Channel coding" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
l l l l l l l l
2.54 Local Multiple Signaling Points

2.54.1 Introduction
2.54.1.1 Scope
This document describes the Local Multiple Signaling Points feature.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Local Multiple Signaling Points feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.54.2 Overview
The feature of local multiple signaling points enables one physical BSC to function as multiple logical BSCs. Each logical BSC has an SS7 signaling point code. After signaling links are established between a logical BSC and the MSC, the logical BSC serves as an independent BSC and works with the MSC to process services. You can configure the location area of each logical BSC by implementing the local multiple signaling points feature to properly distribute the traffic volume to the logical BSCs. The number of messages sent and received within the BSC is reduced when each logical BSC serves as an independent BSC to interact with the MSC.

Background Information
According to GSM SS7 protocols, a maximum of 16 narrowband signaling links that work at 64 kbit/s or 16 high-speed signaling links can be configured between the MSC and the BSC. These signaling links are used to transmit service signaling. If narrowband signaling links are required, up to sixteen 64 kbit/s SS7 signaling links can be configured on the A interface. If the capacity of a BSC is large, the load of signaling links on the A interface is heavy. Thus, narrowband signaling links cannot meet the traffic requirements. Then, one physical BSC serves as multiple logical BSCs. As a local signaling point, each logical BSC can be considered as an independent BSC and it carries a certain traffic volume. Multiple pairs of signaling points take over the traffic volume that is previously carried by one pair of signaling points (the MSC and one physical BSC). The multiple pairs of signaling points can be the MSC and logical BSC 1, the MSC and logical BSC 2, ..., the MSC and logical BSC n. A maximum of 16 signaling links can be configured between each pair of signaling points. Assume that there are N local signaling points. The ratio of the traffic volume on the signaling links between each pair and the total traffic volume is 1:N. The load of signaling links on the A interface is minimized. In addition, when one physical BSC serves as multiple logical BSCs, the stability of the BSC and MSC increases. When one logical BSC is faulty, the services carried by the other logical BSCs are not affected.
Functions
In the GSM SS7, signaling messages are transmitted on the signaling links between two signaling points (the BSC and the MSC). If E1 transmission is adopted on the A interface, the data transfer rate on each timeslot is 64 kbit/s. Each SS7 narrowband signaling link on the A interface uses only one 64 kbit/s timeslot. Based on the traffic volume on the A interface, several SS7 signaling links need to be configured to carry service signaling between the BSC and the MSC. Thus, the traffic load on each signaling link meets the specified requirements ensuring the security and reliability of signaling transmission. According to the SS7 protocols, each SS7 signaling link between a pair of signaling points has a unique signaling link code. The SLC has four bits. This field determines the number of signaling links between a pair of signaling points cannot exceed 16.
Figure 2-239 Signaling links between the BSC and the MSC
For a BSC of large capacity, more than 16 narrowband signaling links on the A interface are required to meet the requirements of traffic volume and the load on the signaling links. Local multiple signaling points of the BSC can be used to increase the signaling links between the BSC and the MSC. In case the total traffic volume is not increased, the load of each signaling link is decreased. Assume that one physical BSC serves as two logical BSCs (BSC 1 and BSC 2). Figure 2-240 shows the connections of local multiple signaling points. Figure 2-240 Connections of local multiple signaling points
2.54.4 Parameters
This chapter describes the parameters related to Local Multiple Signaling Point. For the meaning of each parameter, see Table 2-153. For the default value, value ranges, and MML commands of each parameter, see Table 2-154. Table 2-153 Parameter description (1) Parameter Signalling link code Description ID of an MTP3 link in a specified link set.
Issue 08 (2011-09-30)
953
Table 2-154 Parameter description (2) Param eter Defa ult Valu e GUI Value Range Actual Value Range Unit MML Comman d ADD MTP3LN K (Mandato ry) Impact
Signalli ng link code
None
0~15
0~15
None
TRX
2.54.5 Counters
2.54.6 Glossary

This chapter lists the reference documents related to Local Multiple Signaling Points. l l l l BSC6900 Feature List BSC6900 Optional Feature Description BSS Reconfiguration Guide BSC6900 GSM Performance Counter Reference
2.55 Location Service

2.55.1 Introduction
2.55.1.1 Scope
This document describes the Location Service feature.

l l

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Location Service feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30)) of GBSS9.0, issue 02 (2009-09-30) of BSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
01(2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change
Issue 08 (2011-09-30)
955
2.55.2 Overview
The GSM LoCation Service (LCS) enables the positioning of an MS based on the timing advance (TA) and the longitude and latitude of the GSM BTS. Although the positioning is not highly accurate, it can meet the current requirements of customers in the mobile communications market. LCS enables the network to provide various services for an MS based on the location of the MS. These services include weather forecasts, trip scheduling, emergency assistance, stock information, business planning, and transportation condition forecasts. The simple LCS can locate a user based on the information obtained from the single-user message tracing.

2.55.3.1 Overview
The GSM LoCation Service (LCS) enables the positioning of an MS based on the timing advance (TA) and the longitude and latitude of the GSM BTS. Although the positioning is not highly accurate, it can meet the current requirements of customers in the mobile communications market. LCS is implemented through the interactions between the Serving Mobile Location Center (SMLC) and the LCS client. The Location Estimate indicates the location area of the MS to be positioned and it is generated by the SMLC. The SMLC is a software and hardware entity providing the LCS. It is located in the BSC. The SMLC receives a service request from the MSC, determines whether the cell supports LCS, and then responds to the service request. The interaction messages transmitted between the BSC and the MSC are of two types: l l Perform Location Request message from the MSC to the BSC Perform Location Response message from the BSC to the MSC
The LCS client is a software and hardware entity that obtains the location information about one or more MSs by interacting with the SMLC. To obtain location information, the LCS client subscribes to LCS from the SMLC. LCS enables the network to provide various services for an MS based on the location of the MS. These services include weather forecasts, trip scheduling, emergency assistance, stock information, business planning, and transportation condition forecasts. The simple LCS can locate a user based on the information obtained from the single-user message tracing.
2.55.3.2 Positioning Procedure

The SMLC is located in the BSC. Figure 2-241 shows the LCS procedure. Figure 2-241 LCS procedure when the SMLC is located in the BSC
1. 2. l l
After receiving an LCS request from an MS, the MSC sends a Perform Location Request message to the BSC. After receiving the Perform Location Request message, the BSC responds as follows: If the serving cell of the MS does not support LCS, the BSC does not send any response message to the MSC. If the serving cell of the MS supports LCS but does not support the location algorithm required by the MSC, the BSC sends the MSC a Perform Location Response message with the cause value Position Method Failure.
NOTE
As shown in Figure 2-241, if the BSC successfully processes a request, it sends a Perform Location Response message to the MSC; if the BSC fails to process the request, it sends a Perform Location Abort message to the MSC.
If the serving cell of the MS supports both LCS and the required location algorithm, the BSC determines the related information according to the data configuration and TA. The BSC, then, sends a Perform Location Response message to the MSC.
2.55.3.3 Location Estimate

The Location Estimate indicates the possible area in which the MS is located by using a certain shape. According to the related protocols, location information can be represented by seven shapes, including Ellipsoid Point, Ellipsoid point with uncertainty circle, Polygon, and Ellipsoid Arc. The Huawei BSC uses the CELL+TA positioning method. Location Estimate is represented by Ellipsoid Arc, as shown in Figure 2-242.
Issue 08 (2011-09-30)
957
Figure 2-242 Location information represented by Ellipsoid Arc
: offset angle between the first defining radius : angle between the first defining radius and of the ellipsoid arc and the north, that is, the second defining radius, that is, Included Antenna Azimuth Angle. Angle. r1: inner radius Point(o): coordinates of a location point(o), identified by the longitude and latitude of the location point r2: uncertainty radius
NOTE
If r1 = 0, the arc is a sector. If = 0 and = 360, the arc is a circle, which represents an omnidirectional cell.
The Location Estimate is generated by the SMLC and indicates the location area of the positioning target. Location Estimate is contained in the Perform Location Response message. Figure 2-243 shows the code of Location Estimate represented by Ellipsoid Arc.
Issue 08 (2011-09-30)
958
Figure 2-243 Code of Location Estimate represented by Ellipsoid Arc
Table 2-155 Description of the code of Location Estimate represented by Ellipsoid Arc Name S Description Bit value 0 = North Bit value 1 = South
Issue 08 (2011-09-30)
959
Name Degrees of latitude
Description Latitude of Point(o), as shown in Figure 2-242. N = [X x 223/90], where [ ] indicates that the decimal number is removed and only the integer is retained. The value of N ranges from 0 to 223 - 1. In the formula, N is the code of the latitude, and X is the absolute value of the actual latitude. The value of X ranges from 0 to +90. N has 24 bits, namely, bit 0 to bit 23, where bits 0 through 22 are value bits and bit 23 is a sign bit.
NOTE When X = 90, the value of N is 223 - 1.
Degrees of longitude
Longitude of Point (o), as shown in Figure 2-242. N = [X x 224/360], where [ ] indicates that the decimal number is removed and only the integer is retained. The value of N ranges from -223 to 2231. In the formula, N is the code of the longitude, and X is the absolute value of the actual longitude. The value of X ranges from -180 to +180. N has 24 bits, namely, bit 0 to bit 23, and is represented by two's complement.
NOTE When X = 180, the value of N is 223 - 1.
Inner radius
r1, as shown in Figure 2-242. N = [R/5], where [ ] indicates that the decimal number is removed and only the integer is retained. In the formula, N is the code of the inner radius, and X is the actual value of the inner radius. N has 16 bits, namely, bit 0 to bit 15.
Uncertainty radius
r2, as shown in Figure 2-242. r = C x ((1 + x)k - 1), where C = 10 and x = 0.1. In the formula, K is the code of the uncertainty radius, and r is the actual value of the uncertainty radius. K has seven bits, namely, bit 0 to bit 6. The value of K ranges from 0 to 127.
Offset angle
, as shown in Figure 2-242. N = [a/2], where [ ] indicates that the decimal number is removed and only the integer is retained. The value of N ranges from 0 to 180. In the formula, N is the code of the angle, and a is the actual value of the angle. N has eight bits, namely, bit 0 to bit 7.
Issue 08 (2011-09-30)
960
Name Included angle
Description , as shown in Figure 2-242. N = [a/2], where [ ] indicates that the decimal number is removed and only the integer is retained. The value of N ranges from 0 to 180. In the formula, N is the code of the angle, and a is the actual value of the angle. N has eight bits, namely, bit 0 to bit 7.
Confidence
Possibility that an MS is located in the area represented by Ellipsoid Arc. K is the code of the confidence and has seven bits, namely, bit 0 to bit 6. The value of K ranges from 0 to 100.
NOTE
The sum of r1 and r2 is determined by the tilt of the antenna and the Antenna Altitude Int Part and Latitude Decimal Part. The value of r1 is determined by TA.
2.55.3.4 Message Format

This describes the information elements (IEs) of the two messages transmitted between the BSC and the MSC. Table 2-156 describes the IEs of the Perform Location Request message from the MSC to the BSC, where n indicates the number of bytes. Table 2-156 Description of the IEs of the Perform Location Request message Information Element Message Type Location Type Description Message type Contains location information and positioning method. Cell ID MS classmark 3 Type of LCS client Channel that is assigned to the current service Transmission Direction Both Both Length (Bytes) 1 3-n
Cell Identifier Classmark Information Type 3 LCS Client Type Chosen Channel
Both Both Both Both
5-10 3-14 3-n 2
Issue 08 (2011-09-30)
961
Information Element LCS Priority
Description Priority of LCS. Level 0 is the highest priority, and level 1 is the normal priority.
Transmission Direction Both
Length (Bytes) 3-n
LCS QoS
QoS of LCS. The Both parameters related to LCS QoS include horizontal precision and vertical precision. GPS assistance data Protocol data unit at the BSS LAPD layer From the MSC to the BSS Both
3-n
GPS Assistance Data APDU
3-n 3-n
Table 2-157 describes the IEs of the Perform Location Response message from the BSC to the MSC, where n indicates the number of bytes. Table 2-157 Description of the IEs of the Perform Location Response message Information Element Message Type Location Estimate Description Message type Location information about an MS Positioning data, including the resolution and positioning method Deciphering keys, including the encryption identifier, current deciphering key, and deciphering key of the next data frame Cause of LCS Transmission Direction Both Both Length (Bytes) 1 3-22
Positioning Data
Both
3-n
Deciphering Keys
From the BSS to the MSC
3-n
LCS Cause
Both
3-n
Issue 08 (2011-09-30)
962
2.55.3.5 Dependency
The positioning precision depends on the following factors: l l l Angles of antennas in a cell: Directional antennas have higher positioning precision than omnidirectional antennas. Moving speed of the LCS client: The positioning precision is inversely proportional to the moving speed of the LCS client. Precision of the location data configured in a cell.
NOTE
An MS can be positioned in a sector area that has a radius of 500 meters (that is, the distance corresponding to one TA) by using the Cell+TA positioning method if the following conditions are met: The location of the MS remains unchanged; the transmission quality of radio signals is good; the data configuration of a cell is correct.
2.55.4 Parameters
The following describes the parameters related to LCS. For the meaning of each parameter, see Table 2-158. For the default value, value range, and related MML commands of each parameter, see Table 2-159. Table 2-158 Parameter description (1) Parameter Antenna Azimuth Angle Description Size of the azimuth angle of the cell antenna Included angle formed by the major lobe azimuths of the antennas in two cells under one BTS. A major lobe azimuth is measured from the due north to the direction of the cell antenna in a clockwise rotation. Integer part of the antenna altitude Decimal value when the latitude where a cell is located is indicated in the format of degree
Included Angle Antenna Altitude Int Part Latitude Decimal Part
Table 2-159 Parameter description (2) Parameter Default Value GUI Value Range Actual Value Range Unit MML Command SET GCELLLC S(Optional) SET GCELLLC S(Optional) Impac t
Antenna Azimuth Angle
360
0~360
0~360
degree
Cell
Included Angle
Issue 08 (2011-09-30)
360
0~360
0~360
degree
Cell
963
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command SET GCELLLC S(Optional) SET GCELLLC S (Mandatory )
Impac t
Antenna Altitude Int Part
40
0~6553
0~6553
Cell
Latitude Decimal Part
None
None
1~5 characters
degree
Cell
2.55.5 Counters
2.55.6 Glossary

l l l l l l l 3GPP TS 23.032 Universal Geographical Area Description (GAD) BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.56 MSC Pool

2.56.1 Introduction
2.56.1.1 Scope
This document describes MSC pool of Huawei GBSS. It covers the function of and mechanism regarding this feature, including the implementation of the load balancing and load sharing algorithm in an MSC pool.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the MSC pool feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.56.2 Overview
An MSC pool is a group of MSCs handling the traffic from an MSC pool area. A BSC in an MSC pool area is connected to each MSC in the MSC pool. All the MSCs in the MSC pool share load and resources implementing load balancing, reducing inter-MSC handovers improving network reliability. As shown in Figure 2-244, MSC 1, MSC 2, and MSC 3 constitute an MSC pool, and location area 1 (LA1), LA2, LA3, and LA4 constitute an MSC pool area. Figure 2-244 MSC pool area configuration
As shown in Figure 2-244, one BSC can be connected to multiple MSCs in an MSC pool at the same time. In this manner, the traffic from the BSC can be evenly distributed to these MSCs according to the network resource identifiers (NRIs) or the load balancing principle. A MSC pool area is the service area of one or more radio access network (RAN) nodes. It consists of one or more LAs. All the LAs served by one BSC or BTS must belong to the same MSC pool area. If different MSC pool areas overlap each other, one LA can belong to more than one MSC pool area. Within an MSC pool area, an MS may roam without changing the serving MSC. The LAs in an MSC pool area can be served by one or more MSCs. For example, the calls in LA1 can be evenly distributed to MSC 1, MSC 2, and MSC 3. When an MS in an ongoing call roams in the MSC pool area, no inter-MSC handover is required. The MSC pool is implemented according to the 3GPP TS 23.236 and has the following benefits: l l l All the MSCs in the MSC pool share load and resources increasing the core network (CN) capacity and reducing the equipment investment. When an MSC in the MSC pool is faulty or when an MSC is added to or removed from the MSC pool, the subscribers in the MSC pool area are not affected, improving reliability. Logically, all the MSCs in one MSC pool are regarded as one MSC. Therefore, the interMSC handovers and the signaling between the MSCs and the home location register (HLR) are reduced, improving the network performance.

2.56.3.1 Load Balancing in an MSC Pool

In a non-MSC-pooled case, one BSC is connected to only one MSC. During a call establishment procedure, the BSC sends a Connect Request message to the MSC. In a MSC-pooled case, however, one BSC is connected to multiple MSCs in the MSC pool. During a call establishment procedure, if the call is not dedicated to a specific MSC, the BSC sends the Connect Request message to all the MSCs to evenly distribute traffic among the MSCs in the MSC pool. The load balancing procedure is controlled by the BSC according to the MS identity and MSC administrative state reported by the MS. l If the layer 3 service establishment indication message from an MS carries the temporary mobile subscriber identity (TMSI) that contains an NRI, and MSC Administrable State for the MSC corresponding to the NRI is NORMAL(Normal), then the BSC sends a Connect Request message to the MSC. If the layer 3 service establishment indication message from an MS carries the TMSI that contains an NRI, and MSC Administrable State the MSC corresponding to the NRI is UNAVAIL(Unavailable), then the BSC randomly selects one MSC whose MSC Administrable State is NORMAL(Normal) and whose operational state is Available according to the load balancing algorithm and sends a Connect Request message to the selected MSC. If the layer 3 service establishment indication message from an MS carries the TMSI that a NULL_NRI, the BSC randomly selects one MSC whose MSC Administrable State is NORMAL(Normal) and the operational state is Available according to the load balancing algorithm and then sends a Connect Request message to the selected MSC. If the layer 3 service establishment indication message from an MS carries the TMSI or international mobile equipment identity (IMEI), the BSC randomly selects one MSC whose MSC Administrable State is NORMAL(Normal) and the operational state is Available according to the load balancing algorithm and then sends a Connect Request message to the selected MSC.
Figure 2-245 shows the MSC selection during a call establishment procedure. Figure 2-245 MSC selection during a call establishment procedure
When the MSC pool feature is enabled on the BSC side, the TMSI allocation function must be enabled on the MSC side and the TMSI that the MSC allocates to an MS must contain the NRI.

NOTE
l The MSC administration state can be Normal, Offload, or Unavailable. l In the Normal state, new access requests and the accepted access requests can be handled normally. l In the Offload state, new access requests are rejected, but the accepted access requests can be handled normally. l In the Unavailable state, new access requests are rejected, and the accepted access requests are not handled. l The MSC operational state can be Available or Unavailable. l The Available state indicates that both the MSC and the communication between the BSC and the MSC are normal. l The Unavailable state indicates that the MSC or the communication between the BSC and the MSC is abnormal.
Selecting an MSC Based on NRI

An NRI identifies an MSC in the MSC pool. It is contained in the TMSI and starts from bit 23, as shown in Figure 2. The NRI size ranges from 1 bit to 10 bits, as shown in Figure 2-246. Figure 2-246 Position of the NRI field in the TMSI
A NULL_NRI is a special NRI, which is coded in the same manner as an NRI. A NULL_NRI does not identify a specific MSC. Instead, it indicates that the traffic from an MS should be redistributed to a new MSC. The new MSC state should be Normal and Available. The NULL_NRI is specified by MSC NULL-NRI Value. l l In a single-operator CN, the operator there has a unique NULL_NRI. In a multi-operator core network (MOCN), each CN operator has a unique NULL_NRI.
The number of MSCs in an MSC pool can be changed by setting Length of NRI in TMSI. Length of NRI in TMSI must be set to the same value for all the MSCs in one MSC pool. In the case of two overlapping pool areas, Length of NRI in TMSI must be set to the same value for all the MSCs in the two MSC pools. The mapping between the NRIs and the MSCs can be defined according to the NRI and DPC Route Index table. One NRI is assigned to a specific MSC, and one MSC can have multiple NRIs. Adding or deleting a mapping between an NRI and a MSC means that the MSC is added to or removed from an MSC pool. If the MSC pool feature is enabled on the BSC side, the BSC selects an MSC from the MSC pool based on the NRI contained in the TMSI. When an MS uses the TMSI to perform location update or call access, the BSC determines the MSC by decoding NRI contained in the TMSI and querying the mapping between the NRI and the MSC. l If the NRI value is MSC NULL-NRI Value, the BSC selects one MSC whose MSC Administrable State is NORMAL(Normal) and the operational state is Available according to the load balancing algorithm.
Issue 08 (2011-09-30)
If the corresponding MSC is not found, the operational state of the MSC is Unavailable, or the MSC Administrable State is UNAVAIL(Unavailable), the BSC selects one MSC whose MSC Administrable State is NORMAL(Normal) and the operational state is Available according to the load balancing algorithm.
Selecting an MSC Based on international mobile subscriber identity (IMSI) or IMEI

When an MS uses the IMSI or IMEI to access the network, the BSC distributes the traffic from the MS to an MSC according to the load balancing algorithm. l If the Complete Layer 3 Information message sent by the MS carries the IMSI, the BSC distributes the traffic from the MS to an MSC according to the load balancing algorithm. The MS can request services such as call establishment, location update, paging response, call re-establishment, RR initialization, and IMSI detach. If the Complete Layer 3 Information message sent by the MS carries the IMEI, the BSC distributes the traffic from the MS to an MSC according to the load balancing algorithm. The MS can request services such as an emergency call.
2.56.3.2 Load Balancing Algorithm Available MSC Capacity

l If an MSC supports the private message transmission between the MSC and a BSC, Available MSC capacity = MSC Available Capability<K User number> configured on the BSC - (Total MSC capacity in the private message - Available MSC capacity in the private message) l If an MSC does not support the private message transmission between the MSC and a BSC, Available MSC capacity = MSC Available Capability<K User number> configured at the BSC
Load Balancing Algorithm

The BSC implements the load balancing algorithm among MSCs in any of the following conditions: l l l No MSC is specified in the MS identity, that is, the MS carries NULL_NRI. The specified MSC is unreachable. The specified is in the Unavailable state.
The BSC selects an MSC according to the state and available capacity of the MSC to ensure the load balancing among MSCs. The BSC calculates the load sharing proportion of each MSC and the value range of V based on MSC Available Capability<K User number>, the operational state, and the administration state of each MSC. Table 2-160 describes the mapping between the value ranges of V and MSCs in an MSC pool. Here, the MSC pool consists of MSC 1, MSC 2, and MSC 3.
Issue 08 (2011-09-30)
969
Table 2-160 Mapping between the value ranges of V and MSCs MSC Available Capability<K User number> 400 300 300 Load sharing proportio n 40.0% 30.0% 30.0%
MSC ID MSC1 MSC2 MSC3
MSC State Normal and Available Normal and Available Normal and Available
Value Range of V 000-399 400-699 700-999
Calculating the value of V is the core of the load balancing algorithm. Value V can be calculated by using OTHERALG(MS ID Algorithm) or RANDOMALG(Random Algorithm). The load balancing algorithm is specified by the MSC Pool Load Balancing Algorithm Select parameter. l OTHERALG(MS ID Algorithm) If the Non-Access Stratum (NAS) message from an MS carries the IMSI or IMEI, the BSC calculates the value of V according to the formula (IMSI/10) mod 1000 or (IMEI/10) mod 1000. Then, the BSC selects an MSC according to the (V, MSC) mapping table. The (V, MSC) mapping table is generated by the BSC based on the state and available capacity of each MSC in the MSC pool. According to this algorithm, the traffic load of an MSC is related to the distribution of the IMSI or IMEI. This cannot fully achieve load balancing. l RANDOMALG(Random Algorithm) If the NAS message from an MS carries the IMSI, IMEI, or NULL_NRI, the BSC selects a random number from 0 to 999 as the value of V. Then, the BSC determines the serving MSC according to the (V, MSC) mapping table. The two algorithms differ in the methods of calculating the value of V but have the same method of selecting an MSC based on the value of V.
CAUTION
If RANDOMALG(Random Algorithm) is used, and if the Layer 3 Service Establishment Indication message from the MS carries the IMSI, the TMSI allocation function must be enabled on the MSC side because the mapping between IMSIs and MSCs is uncertain. l If the TMSI allocation function is not enabled on the MSC side, the BSC distributes a call from the MS to an MSC randomly. In this manner, the call establishment may fail because the data about the MS is not available in the VLR of another MSC. l If the TMSI allocation function is enabled on the MSC side, the MS preferentially uses the TMSI to initiate a call. In this manner, the call can be established successfully.
Issue 08 (2011-09-30)
970
2.56.3.3 Load Adjustment in an MSC Pool Load Adjustment When an MSC is Added to or Removed from an MSC Pool
When an MSC is added to an MSC pool, the BSC automatically adjusts the load sharing proportion proportion of each MSC in the MSC pool. Assume that MSC4 with a capacity of 300 users is added to the MSC pool. Compared with the original mapping between value V and MSC described in Table 2-160 in 2.56.3.2 Load Balancing Algorithm, the mapping is updated, as described in Table 2-161. Table 2-161 Mapping between the value ranges of V and MSCs when MSC 4 is added Load sharing proportio n 30.8% 23.1% 23.1% 23.0%
MSC ID MSC1 MSC2 MSC3 MSC4
MSC Capacity (Number of Users) 400 300 300 300
MSC State Normal and Available Normal and Available Normal and Available Normal and Available
Value Range of V 000-307 308-538 539-769 770-999
NOTE
Load sharing proportion of the last MSC = 1 - Sum of load sharing proportion proportions of the remaining MSCs
When an MSC is removed from an MSC pool, the BSC needs to delete it from the mapping table. Assume that MSC3 is deleted from Table 2-161. In this case, the mapping between the value ranges of V and MSCs is updated, as described in Table 2-162. Table 2-162 Mapping between the value ranges of V and MSCs when MSC 3 is removed Load Sharing Proportio n 40.0% 30.0% 30.0%
MSC Capacity (Number of Users) 400 300 300
Value Range of V 000-399 400-699 700-999
Issue 08 (2011-09-30)
971
Load Adjustment When the MSC State Changes

When the state of an MSC in the MSC pool changes, the BSC redistributes the traffic of this MSC to the other MSCs in the MSC pool according to the load sharing proportionproportion of each MSC. If the operational state of an MSC becomes Unavailable, or if the operational state of an MSC is Available but the administration state is OFFLOAD(Offload) or UNAVAIL (Unavailable), the BSC deletes the MSC from the mapping table and updates the load sharing proportionproportion. For example, if the administration state of MSC 2 in Table 2-162 is changed to OFFLOAD (Offload), the mapping between the value ranges of V and MSCs is updated, as described in Table 2-163. Table 2-163 Mapping between value V and MSC when the administration state of MSC 2 becomes Offload Load sharing proportio n 57.1% 0 42.9%
MSC Capacity (Number of Users) 400 300 300
MSC State Normal and Available Offload and Available Normal and Available
Valu Range of V 000-570 -571-999
If the administration state of an MSC in the MSC pool is changed to OFFLOAD(Offload), the traffic of this MSC is redistributed to the other MSCs in the same MSC pool. Assume that MS 1 is originally attached to MSC 1. After the administration state of MSC 1 is changed to OFFLOAD(Offload), the procedure for redistributing the traffic from MS1 is as follows: l MS 1 that is attached to MSC 1 in the Offload state initiates a call. 1. Before the call is established, MSC 1 reassigns a TMSI named TMSI1 to MS1. The value of the NRI is NULL_NRI and the value of the LAI is Non-broadcast LAI.
NOTE
A non-broadcast LAI is a special LAI. It is coded in the same manner as an LAI. l Each MSC in the MSC pool must be assigned a unique non-broadcast LAI, which is used when the MSC is offloaded. l Each MSC in the MSC pool must know the non-broadcast LAIs of other MSCs in the same MSC pool. In the case of MS traffic redistribution, the target MSC obtains the relevant data, such as the IMSI of the MS, from the offloaded MSC based on the non-broadcast LAI. l The non-broadcast LAI is invisible to the BSC.
2.
After the call is terminated, MS1 immediately initiates a location update procedure if it finds that the LAI sent by MSC 1 is different from the LAI of the serving cell.
Issue 08 (2011-09-30)
972
3.
If the BSC decodes the TMSI in the location update message reported by MS 1 and finds that the value of the NRI in TMSI 1 is NULL_NRI, the BSC distributes MS 1 to another MSC according to the load balancing algorithm. The MSC assigns a new TMSI named TMSI 2 to MS 1.
4. l
If MS 1 does not initiate a call for a long period, the BSC redistributes MS 1 to an MSC through a periodical location update procedure. 1. 2. 3. 4. In the location update procedure, MS1 reports TMSI1 to the BSC, which then distributes MS1 to MSC1 accordingly. MSC1 assigns TMSI2 to MS1. The NRI value in TMSI2 is NULL_NRI and the LAI value in the TMSI Reallocation Command is Non-broadcast LAI. If MS1 finds that the LAI in the TMSI Reallocation Command is different from the LAI of the serving cell, MS 1 initiates a location update procedure again. If MSC1 is in OFFLOAD(Offload) state and the NRI value in TMSI2 is NULL_NRI, the BSC distributes MS 1 to another MSC.
If MS 1 is powered off for a long period, it initiates a location update procedure immediately after being powered on. 1. 2. 3. If MSC1 is still in OFFLOAD(Offload) state, MS1 is redistributed according to the preceding location update procedure. If the administration state of MSC1 becomes NORMAL(Normal), MS1 is still attached to MSC1 and is not redistributed. After MSC1 is offloaded, the administration state of MSC1 must be set to NORMAL (Normal). Otherwise, new MSs cannot register in MSC1.
If Huawei MSC and Huawei BSC are interconnected, the administration state of the MSC need not be configured on the BSC side. Instead, the MSC periodically broadcasts its administration state in Huawei private messages. The BSC adjusts the load sharing proportion according to the current administration state of each MSC in the MSC pool. When MSC Administrable State is changed from NORMAL(Normal to OFFLOAD(Offload) or UNAVAIL(Unavailable), the BSC automatically redistributes some traffic from the MSC to other MSCs. In this manner, the MSC is offloaded. The MSC can query its current administration state saved on the BSC side. If the MSC considers that the query result is abnormal, it sends a configuration message to the BSC to reset its administration state.
Load Adjustment When the MSC Capacity Is Changed

When no MSC is added to or removed from an MSC pool and the state of each MSC in the MSC pool remains unchanged, the actual load and available capacity of each MSC may vary greatly from time to time. If the load of an MSC in the MSC pool varies with the traffic volume, you can adjust the actual load of the MSC by changing the value of MSC Available Capability<K User number>. If Huawei MSC and Huawei BSC are interconnected, the capacity adjustment procedure is performed automatically. That is, each MSC in the MSC pool periodically broadcasts the occupied capacity to all the BSCs in the MSC pool area using Huawei private messages. Huawei private message carries the information on the total capacity and available capacity of an MSC. The BSC automatically redistributes traffic according to the changed load sharing proportion. If an MSC is overloaded, the BSC automatically redistributes some traffic from the MSC to other MSCs to implement load balancing.
If the capacity of MSC 2 in Table 2-160 in 2.56.3.2 Load Balancing Algorithm is changed to 400, the mapping between the value ranges of V and MSCs is updated, as described in Table 2-164. Table 2-164 Mapping between value V and MSC when the capacity of MSC 2 is changed MSC Available Capability<K User number> 400 400 300 Load Sharing Proportio n 36.4% 36.4% 27.2%
MSC ID MSC 1 MSC 2 MSC 3
Value Range of V 000-363 364-727 728-999
NOTE
The MSC dynamically notifies the BSC of its current capacity, and the mapping between the value ranges of V and MSCs is updated accordingly.
If the BSC uses the MSC available capacity carried in the private message as the parameter for the load balancing algorithm, the available capacity of an MSC in the MSC pool can be calculated according to the following formula: Available MSC capacity = MSC Available Capability<K User number> configured on the BSC side - (Total MSC capacity in the private message - MSC available capacity in the private message) If MSC Available Capability<K User number> configured on the BSC side is much less than the total MSC capacity in the private message, the calculated result may be equal to or less than 0. In this case, the MSC capacity is considered as 0. The Receive MSC Configuration Message Timer parameter specifies the duration of the timer for the MSC in the MSC pool to broadcast its available capacity.
NOTE
By default, the period for broadcasting the private message is one hour. The period can be set on the NSS side.
IMSI Paging Processing

If a paging request message delivered by an MSC carries the IMSI and the paging response message from the MS also carries the IMSI, the BSC must forward the paging response message to the MSC to ensure the normal handling of the call. l When the paging request message from an MSC carries only the IMSI, the BSC must forward the paging response to the MSC if it receives a paging response from the MS within the specified period. When the paging request message from an MSC carries the TMSI, the BSC may not send the paging response to the source MSC. Instead, the BSC identifies the MSC to which the
Issue 08 (2011-09-30)
MS has gained access according to the NRI in the TMSI and then sends the paging response to the corresponding MSC. In the case that a CS paging message is received over the Gb interface, the procedure for handling the paging is the same as the procedure described earlier. To support the routing of the CS paging request message in this way, the BSC must be configured with the MSC ID parameter to identify the MSC.

l l l l To implement the MSC pool feature, a license is required and MSC Pool Function Enabled must be set to Yes on the BSC side. The MSC connected to the BSC must support the MSC Pool feature. When the MSC pool feature is enabled on the BSC side, the MSC must support the TMSI allocation function if the BSC usesthe random algorithm. If the BSC supports the MSC pool feature, the following data configurations on the BSC side must be the same as those on the MSC and MGW sides: Length of NRI in TMSI and NRI Value MSC NULL-NRI Value MSC Available Capability<K User number>, MNC, MSC ID, and MSC Administrable State
2.56.5 Parameters
This chapter lists the parameters related to MSC pool. For the meaning of each parameter, see Table 2-165. For the default value, value ranges, and MML commands of each parameter, see Table 2-166. Table 2-165 Parameter description (1) Parameter MSC Administrab le State Length of NRI in TMSI MSC NULL-NRI Value MSC Available Capability< K User number> Description Administrative state of the MSC. This parameter is valid only when the MSC pool function is enabled. It is set according to the actual operating state of the MSC. A call accesses the MSC only when this parameter is set to NORMAL. Number of bits occupied by the Network Resource Identifier in the TMSI. NRI specifies a CN node in the MSC pool. Special NRI(Network Resource Identifier) that is coded together with common NRIs. This parameter is used to indicate that the BSC routes the service initiated by the MS to the MSC in non OFFLOAD state.
Available capacity of the MSC. This parameter is valid only when the MSC pool function is enabled. It is set according to the actual capacity of the MSC.
Issue 08 (2011-09-30)
975
Parameter MSC Pool Load Balancing Algorithm Select Receive MSC Configuratio n Message Timer MSC ID
Description Type of load balancing algorithm of the MSC Pool. Generally, the BSC6900 chooses an MSC according to the obtained network resource indication (NRI). In some cases, however, the BSC6900 cannot do so. Instead, the BSC6900 chooses a target MSC according to a load balancing algorithm.
If the BSC6900 receives the configuration data about all the connected MSCs before the timer expires, the BSC6900 concludes that the configuration data is valid. Used to uniquely identify an MSC Whether to enable the MSC pool function on the BSC6900. The MSC pool function enables up to 32 MSCs to provide services for mobile subscribers in a BSC6900. With the MSC pool function, one BSC6900 can be connected to multiple MSCs and the services in the BSC6900 are shared to each MSC in all MSC pools. Network resource indication that specifies a CN node in the MSC pool Mobile network code. This parameter identifies the public land mobile network (PLMN) to which a mobile subscriber belongs.
MSC Pool Function Enabled NRI Value MNC
Table 2-166 Parameter description (2) Parameter Default Value GUI Value Range OFFLOAD (Offload), NORMAL (Normal), UNAVAIL (Unavailable) Actual Value Range Uni t MML Command Im pac t
MSC Administrable State
NORM AL
OFFLOAD , NORMAL, UNAVAIL
Non e
ADD GCNNODE (Optional) ADD GCNOPERA TOR (Mandatory) ADD GCNOPERA TOR (Optional) ADD GCNNODE (Optional)
MS C
Length of NRI in TMSI
1~10
1~10
Non e
BS C
MSC NULLNRI Value MSC Available Capability<K User number>
0~1023
0~1023
Non e Non e
BS C MS C
1800
0~65535
0~65535
Issue 08 (2011-09-30)
976
Parameter
Default Value
GUI Value Range RANDOMAL G(Random Algorithm), OTHERALG (MS ID Algorithm)
Actual Value Range
Uni t
MML Command
Im pac t
MSC Pool Load Balancing Algorithm Select Receive MSC Configuration Message Timer
RANDO MALG
RANDOM ALG, OTHERAL G
Non e
ADD GCNOPERA TOR (Optional) ADD GCNOPERA TOR (Optional) ADD GCNNODE (Mandatory) ADD GCNOPERA TOR (Optional) ADD NRIMSCMA P(Mandatory)
MS C
1~15
1~15
min Non e
BS C MS C
MSC ID MSC Pool Function Enabled
None
0~4095
0~4095
NO
NO(No), YES (Yes)
NO, YES
Non e Non e
BS C BS C
NRI Value
None
0~1023
0~1023
Issue 08 (2011-09-30)
977
Parameter
Default Value
GUI Value Range
Actual Value Range
Uni t
MML Command ADD GCNOPERA TOR (Mandatory) ADD GCELL (Mandatory) ADD GEXT2GCE LL (Mandatory) ADD GEXT3GCE LL (Mandatory) SET FHO (Mandatory) ADD BTSAUTOP LAN (Mandatory) SET BTSAUTOP LANCFG (Optional) ADD GCELLQUIC KSETUP (Mandatory)
Im pac t
MNC
None
None
2~3 digit
Non e
Cell
2.56.6 Counters
2.56.7 Glossary

l l l l l
Issue 08 (2011-09-30)
3GPP TS 23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference
l l
BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.57 Multiband Network

2.57.1 Introduction
2.57.1.1 Scope
This document describes the functions of and technologies regarding multiband network and enhanced dual-band network, including cell reselection, channel allocation, handover, and network topologies.


The change history provides information on the changes on the Multiband Network feature in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Multiband Network feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02(2009-09-30)
Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
01(2009-06-30)
2.57.2 Overview
A multiband network comprises the networks of different frequency bands. In a multiband network, the BSC should support the cell reselection and handover of MSs between different frequency bands. The following network topologies are applicable to a multiband network: l Independent MSC network topology The network of each frequency band has an independent MSC, and different networks are connected through the MSCs. l Co-MSC independent BSC network topology The network of each frequency band has an independent BSC, and different networks are connected through the same MSC. l Co-BSC network topology The network of each frequency band has independent cells, and these cells are connected to the same BSC. Table 2-167 describes the mapping between the frequency band and the absolute radio frequency channel number (ARFCN). Table 2-167 Mapping between the frequency band and the ARFCN Frequency Band P-GSM900 band E-GSM900 band
Issue 08 (2011-09-30)
Uplink Frequency Fl(n) = 890 + 0.2 x n 890-915 MHz Fl(n) = 890 + 0.2 x n
Downlink Frequency Fu(n) = Fl(n) + 45 935-960 MHz Fu(n) = Fl(n) + 45
ARFCN 1 n 124
0 n 124
980
Frequency Band
Uplink Frequency Fl(n) = 890 + 0.2 x (n 1024) 880-915 MHz
Downlink Frequency
ARFCN 975 n 1023
925-960 MHz Fu(n) = Fl(n) + 45
0 n 124 955 n 1023
R-GSM900 band
Fl(n) = 890 + 0.2 x n Fl(n) = 890 + 0.2 x (n 1024) 876-915 MHz
921-960 MHz Fu(n) = Fl(n) + 95 1805-1880 MHz Fu(n) = Fl(n) + 80 1930-1990 MHz Fu(n) = Fl(n) + 45 869-894 MHz
512 n 885
DCS1800 band
Fl(n) = 1710.2 + 0.2 x (n 512) 1710-1785 MHz
PCS1900 band
Fl(n) = 1850.2 + 0.2 x (n 512) 1850-1910 MHz
512 n 810
GSM850 band
Fl(n) = 824.2 + 0.2 x (n 128) 824-849 MHz
128 n 251
Two or more frequency bands can be combined into the same GSM network. The most common combination is P-GSM900 with DCS1800 and GSM850 with PCS1900. The combination between DCS1800 and PCS1900 is not possible because frequencies in DCS1800 overlap with frequencies in PCS1900. The radio waves on different frequency bands have different path loss characteristics. If the transmit power is the same, the propagation distance of the radio wave from a low frequency band is longer than that of the radio wave from a high frequency band. For P-GSM900 and DCS1800, the number of frequencies available in DCS1800 is three times the number of frequencies available in P-GSM900, and thus DCS1800 can be used to provide additional capacity. In a dualband network of P-GSM900 and DCS1800, the characteristics of the two frequency bands can be optimally used to expand the network capacity. Huawei BSC supports the enhanced dualband network. The purpose is to optimally share radio resources between P-GSM900 and DCS1800 and to enable the MS to measure the receive level of the two frequency bands.

2.57.3.1 Multiband Network Principles
Issue 08 (2011-09-30)
981
?.1. Overview of Multiband Network

In a multiband network, the MS and BSS should provide additional functions to support cell reselection and handover between cells of different frequency bands. These functions are as follows: l l l Broadcasting system information 2ter and 5ter Indication of the frequency band support capability of the MS Measuring the neighboring cells of different frequency bands and reporting the measurement results
?.2. Cell Reselection

When the cells operating on different frequency bands are adjacent, cell reselection between these cells is necessary. To support cell reselection, the BSC needs to broadcast system information 2ter, informing a multiband MS of the neighboring cells on the frequency bands rather than the serving band. Then, the MS measures the receive level of the neighboring cells and decides whether to reselect a neighboring cell according to the cell reselection algorithm.
?.3. Channel Allocation

In a co-BCCH cell, in a cell of the enhanced dualband network, or in a cell that is configured with frequencies in P-GSM900, E-GSM900, and R-GSM900, the BSC allocates a channel to an MS only when the MS supports the corresponding frequency band. For example, there is a frequency with ARFCN 975 available in E-GSM900. If the MS supports only P-GSM900, the BSC does not allocate ARFCN 975 to the MS. If the MS supports E-GSM900, the BSC may allocate ARFCN 975 to the MS. The Classmark 3 information element (IE) specifies the frequency band support capability of the MS. From the Classmark 3 IE, the BSC obtains the frequency band support capability of the MS so as to allocate an appropriate channel. If the BSC does not obtain the Classmark 3 IE from the MS during channel allocation, the BSC regards that the MS supports only the frequency band that is compatible with the BCCH frequency. In this case, the BSC allocates the MS a channel on the frequency band compatible with the BCCH frequency. The switch ECSC should be turned on so that the BSC can obtain the frequency band support capability of the MS at the earliest. After the switch is turned on, the BSC broadcasts system information 3, instructing the MS to report the Classmark 3 IE at the earliest after access. In this way, the MS need not wait for the Classmark Enquiry message from the network before reporting the Classmark 3 IE. The channel allocation method described above is applicable only during the assignment phase. During the immediate assignment phase, an SDCCH compatible with the BCCH frequency is assigned preferentially.
?.4. Handover
When the MS moves from one cell on a frequency band to another cell on a different frequency band during a call, a handover is performed if the MS supports multiple frequency bands. To support the handover, the BSC and MS should provide the following functions: l System information broadcasting During a call, the BSS informs the MS of the information about neighboring cells through system information 5 and 5bis. If any neighboring cell operates on a frequency band rather
than the serving band, the BSS needs to broadcast system information 5ter. System information 5ter carries the information about the neighboring cells of other frequency bands. l Multi-band report After receiving system information 5, 5bis, and 5ter, the MS measures the signal strength of the neighboring cells specified in the system information and then sends the measurement results to the BSS through measurement reports (MRs). One MR contains the information about a maximum of six neighboring cells. If all the neighboring cells measured by the MS operate on the same frequency band, the MS reports the measurement results of the six strongest neighboring cells to the BSS. If the neighboring cells measured by the MS operate on different frequency bands, the number of neighboring cells on other frequency bands reported by the MS is specified by the parameter Multi-band report. The setting of this parameter is as follows: If Multi-band report is set to 0, the MS reports the six strongest neighboring cells irrespective of the frequency bands used in the cells. If Multi-band report is set to 1, the MS reports the strongest neighboring cell on a different frequency band to the BSC. The remaining positions in the MR are used for the neighboring cells of the serving band. If Multi-band report is set to 2, the MS reports the two strongest neighboring cells on different frequency bands to the BSC. The remaining positions in the MR are used for the neighboring cells of the serving band. If Multi-band report is set to 3, the MS reports the three strongest neighboring cells on different frequency bands to the BSC. The remaining positions in the MR are used for the neighboring cells of the serving band. The BSC informs the MS of the value of Multi-band report through system information 2ter and 5ter. After receiving the MR from the MS, the BSC decides whether a handover should be performed. For details of the handover algorithms and procedures, see the handover feature.

There are three types of network topologies for a multiband network: independent MSC, coMSC independent BSC, and co-BSC. The first two types are referred to as independent network topology, and the third type is referred to as hybrid network topology.
Independent MSC Network Topology

In an independent MSC network topology, the GSM850 band, GSM900 band, DCS1800 band, and GSM1900 band use different MSCs. Figure 2-247 shows the independent MSC network topology in which the commonly used GSM900 band and DCS1800 band are applied.
Issue 08 (2011-09-30)
983
Figure 2-247 Independent MSC network topology
The characteristics of independent MSC network topology are as follows: l l l l l l l No impact on the existing network Convenient for network planning and data configuration, thus facilitating network deployment Heavy load of signaling links due to frequent inter-BSC handovers and location updates Meeting long-term capacity expansion requirements Convenient for network management and service development Requiring cooperation between equipment from different vendors Big investment of network deployment at an early stage, but lowest average investment per user
With all these features, the independent MSC network topology is more efficient than the hybrid network topology in the long run.
Co-MSC Independent BSC Network Topology

In a co-MSC independent BSC network topology, the GSM850 band, GSM900 band, DCS1800 band, and GSM1900 band use the same MSC but different BSCs. Figure 2-248 shows the coMSC independent BSC network topology in which the commonly used GSM900 band and DCS1800 band are applied.
Issue 08 (2011-09-30)
984
Figure 2-248 Co-MSC independent BSC network topology
The characteristics of co-MSC independent BSC network topology are as follows: l l l l l l Possible impact on the existing network. Re-planning NSS is required, and network deployment is somewhat difficult. Inconvenient for capacity expansion and network evolution. Small investment of network deployment at an early stage, and lower average investment per user. Competition among equipment vendors is introduced, which helps reduce equipment investment and improve the quality of service (QoS). Multiple BSCs cooperate with each other, and network security is guaranteed.
Co-BSC Network Topology

In a co-BSC network topology, the GSM850 band, GSM900 band, DCS1800 band, and GSM1900 band use the same BSC, or multiband BTSs are connected to the same BSC. Figure 2-249 shows the co-BSC network topology in which the commonly used GSM900 band and DCS1800 band are applied.
Issue 08 (2011-09-30)
985
Figure 2-249 Co-BSC network topology
The characteristics of co-BSC network topology are as follows: l l l l l Possible huge impact on the existing network. The impact is inversely proportional to the capacity of the BSC. Re-planning NSS and BSS is required, and network deployment is difficult. Inconvenient for capacity expansion and network evolution. Inconvenient for service deployment. Competition among equipment manufacturers cannot be introduced. It is difficult to cut down investment and improve QoS.
2.57.3.3 Overview of Enhanced Dualband Network

?.1. Overview
The enhanced dualband network is an improvement on the existing dualband network. It is implemented as follows: physically, two single-band cells are located at the same layer and have the same priority but different coverage areas; logically, the two cells serve as neighboring cells of each other and form a cell group, namely, one overlaid cell and one underlaid cell. The enhanced dualband network algorithm enables channel sharing and load balancing between the two cells in the cell group.
NOTE
For details about cell layers and priorities, see Cell Layer and Cell Priority in 2.46.3.4.10 Fast-Moving Micro Cell Handover.
The handover decision for the overlaid cell and the underlaid cell in the cell group is based on the MR. Figure 2-250 shows the cell structure of the enhanced dualband network.
Figure 2-250 Cell structure of the enhanced dualband network
?.2. Channel Allocation

When an MS attempts to access the enhanced dualband network, the BSC allocates a channel to the MS according to the following principles: l When the MS in the underlaid cell attempts to access the network, the BSC should determine whether the receive level of the MS is higher than or equal to the minimum access level of the overlaid cell if the load in the underlaid cell is higher than UL Subcell General Overload Threshold. If the receive level of the MS is higher than or equal to the minimum access level of the overlaid cell, and the load in the overlaid cell does not exceed the specified threshold, the BSC assigns the MS a channel in the overlaid cell and initiates a directed retry procedure to hand over the MS to the overlaid cell. Otherwise, the BSC assigns a channel in the underlaid cell to the MS. If congestion occurs in the underlaid cell, the queuing procedure and preemption procedure are initiated. If no channel is available in the underlaid cell, the MS performs cell reselection. l When the MS in the overlaid cell attempts to access the network, the BSC assigns the MS a channel in the underlaid cell preferentially if the load in the underlaid cell is lower than UL Subcell Lower Load Threshold. Otherwise, the BSC assigns a channel in the overlaid cell to the MS. If congestion occurs in the overlaid cell, the queuing procedure and preemption procedure are initiated. If no channel is available in the overlaid cell, the MS performs cell reselection.
?.3. Handover
The handover algorithms for an enhanced dualband network are of two types: handover algorithm I and handover algorithm II. For details, see 2.46.3.4.7 Enhanced Dual-Band Network Handover of 2.46.3.4 Handover Decision Based on Handover Algorithm I and 2.46.3.5.6 Enhanced Dual-Band Network Handover of 2.46.3.5 Handover Decision Based on Handover Algorithm II in the Handover feature.

The principles of distributing traffic between different frequency bands in a multiband network are as follows:
l l l
In the initial stage of network deployment, the DCS1800 cells should absorb traffic as much as possible. In hot spots, the DCS1800 network should provide continuous coverage. When the number of multiband MSs reaches a certain level, different frequency bands should share the traffic to reduce handovers and improve QoS.
The telecom operator can implement different traffic control strategies by adjusting related parameters in real time. The traffic control strategies also depend on the MS state. The detailed strategies are as follows: l When an MS performs cell selection after being powered on or performs cell reselection in standby state, system parameters can be set in a way that a DCS1800 cell has a high priority. Therefore, the DCS1800 cell tends to be the serving cell of a multiband MS, and the MS tends to camp on the DCS1800 cell before a call is established. During a call establishment procedure, the traffic distribution can be adjusted through directed retry. During an ongoing call, the traffic should be distributed to the DCS1800 cell of low layer and high priority as much as possible. Handovers can be performed between the cells of different frequency bands for optimal traffic distribution.
l l l
2.57.5 Parameters
This chapter describes the parameters related to multiband network. For the meaning of each parameter, see Table 2-168. For the default value, value ranges, and MML commands of each parameter, see Table 2-169. Table 2-168 Parameter description (1) Paramete r Description The early classmark sending control (ECSC) parameter specifies whether the MSs in a cell use early classmark sending. After a successful immediate assignment, the MS sends additional classmark information to the network as early as possible. The additional classmark information mainly contains the CM3 (classmark 3) information. The CM3 (classmark 3) information contains the frequency band support capability of the MS (used for the future channel assignment), power information about each frequency band supported by the MS (used for the handover between different frequency bands), and encryption capability of the MS. Used for requesting the MS to report the measurement information of neighboring cells in multiple frequency bands. This parameter is carried in the system information 2ter and 5ter. When the load of the underlay subcell is higher than this parameter, some of the calls in the underlay subcell will be switched to the overlay subcell, and channels in the overlay subcell will be preferentially assigned to calls initiated in the underlay subcell as well.
ECSC Multiband report UL Subcell General Overload Threshold

Issue 08 (2011-09-30)
Paramete r UL Subcell Lower Load Threshold
Description
When the load of the underlay subcell is lower than this parameter, some of the calls in the overlay subcell will be switched to the underlay subcell, and channels in the underlay subcell will be preferentially assigned to channel requests initiated in the overlay subcell as well.
Table 2-169 Parameter description (2) Parameter Default Value GUI Value Range NO (No), YES (Yes) Actual Value Range Unit MML Command Impact
ECSC Multi-band report UL Subcell General Overload Threshold UL Subcell Lower Load Threshold
YES
NO, YES
None
SET GCELLCCBA SIC(Optional) SET GCELLCCBA SIC(Optional) SET GCELLHOED BPARA (Optional) SET GCELLHOED BPARA (Optional)
Cell
0~3
0~3
None
Cell
80
0~100
0~100
per cent
Cell
50
0~100
0~100
per cent
Cell
2.57.6 Counters
2.57.7 Glossary

l l 3GPP TS 04.08: "Mobile radio interface layer 3: specification" 3GPP TS 05.05: "Digital cellular telecommunication system (Phase 2+); Radio transmission and reception"
Issue 08 (2011-09-30)
l l l l l l l
3GPP TS 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.58 Multi-Site Cell

2.58.1 Introduction
2.58.1.1 Scope
This document describes the definition and coverage mode of the multi-site cell, synchronization of subsites over the Um interface, and inter-subsite handover.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the multi-site cell feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
l l
01 (2009-09-30) Draft (2009-05-30)
01 (2009-09-30)
2.58.2 Overview
With the development of economy, the mobile telecommunication technology has touched all aspects of social life. People are increasingly relying on mobile telecommunication technology, thus demanding for a better quality of mobile services. Nowadays, technologies and solutions for large-scale network coverage in outdoor scenarios are well developed. On the other hand, advanced solutions and technologies are still under further optimization for the network coverage in scenarios such as the high-speed railway lines, tunnels, indoor space, and rural areas. Therefore, the multi-site cell feature, a burgeoning technology, is introduced. The multi-site cell feature is a function through which multiple subsites are configured as one cell logically. This feature effectively promotes the QoS in the coverage areas, and greatly reduces the handovers between cells in certain scenarios such as high-speed railway lines and tunnels, thus significantly improving user experience. A subsite physically consists of one or more Remote Radio Units (RRUs), and provides the network coverage in a certain area. When the multi-site cell feature is applied, the cell coverage is expanded through the mergence of the continuous coverage areas provided by multiple adjacent subsites. The hardware configuration and cell-level configuration (for example, the number of TRXs and frequencies) for each subsite involved must be the same. To apply to complex coverage areas along the high-speed railway lines and tunnels, the architecture of Huawei distributed base station (DBS), known as Base Band Unit (BBU) + RRU, is adopted for the development of the multi-site cell feature. Thus, the multi-site cell feature is also called multi-RRU cell. The multi-site cell feature is a function based on which the multiple subsites that communicate with the same BBU are logically configured as one cell. In a multi-site cell, a BBU supports a maximum of six subsites, and each subsite supports a maximum of six TRXs. Figure 2-251 shows the logical networking in a multi-site cell. Figure 2-251 Logical networking in a multi-site cell
Issue 08 (2011-09-30)
991
All the subsites in a multi-site cell must be synchronized over the Um interface so that the transmission and reception of user data in each burst can be synchronized. In a multi-site cell, only one primary subsite is configured for cell management and service control. To configure a subsite as the primary one, set the parameter Is Main Local Group to YES. The remaining subsites in the multi-site cell function as secondary subsites, which are controlled by the primary one to perform functions such as TRX selection and channel activation. The board carrying TRXs can be configured only in the primary subsite. The board that does not carry TRXs can be configured in secondary subsites. If you need to associate a TRX configured in the primary subsite with an idle path configured in the secondary subsite, set the parameter Sub-Location Group TRX Board Pass No. as required. Before removing a TRX, you need to check whether the TRX is bound to a board configured in the secondary subsite. If yes, you need to remove the binding between the TRX and the board. When an MS accesses the multi-site cell, each subsite measures the signal-to-noise ratio (S/N) of the uplink signals and reports the filtered value to the primary subsite. Based on the reported values, the primary subsite selects the secondary subsite with the best S/N as the serving subsite. As an MS moves around, each subsite continuously measures the S/N of the uplink signals and reports the filtered value to the primary subsite for inter-subsite handover decision. When the primary subsite detects that the S/N reported by a neighboring subsite is better than that reported by the serving subsite, a handover is triggered between the subsites. When an MS is handed over from one subsite to another, the connection is established in the target subsite before the MS is disconnected from the current subsite. In this manner, a seamless handover is achieved without service disruption, thus ensuring the QoS. When an MS moves quickly from the coverage area of one subsite to that of another, the handover takes place between subsites instead of cells. Thus, the frequency of handover is decreased. Moreover, excessive overlapping areas for successful handovers are not necessary. Thus, the valid coverage area provided by each subsite is enlarged, and the coverage efficiency of the multi-site cell is improved.

2.58.3.1 Synchronization of Subsites over the Um Interface
The multiple subsites in a multi-site cell must be synchronized over the Um interface. To synchronize the frames transmitted from each subsite, the BBU automatically determines the transmission latency between itself and each subsite, and then sends the related parameters to the corresponding subsite to adjust and offset the latency over the optical cable. Thus, the transmission and reception of user data in each burst can be synchronized, as shown in Figure 2-252.
Issue 08 (2011-09-30)
992
Figure 2-252 Synchronization over the Um Interface
2.58.3.2 Inter-Subsite Handover

When an MS accesses the network, each subsite measures the S/N of the uplink signals and reports the filtered value to the primary subsite. Figure 2-253 is shown as an example. Based on the reported value, the primary subsite selects the subsite configured with RRU1 as the serving subsite, because the S/N of the uplink signals received by RRU1 is the best. As an MS moves from P0 to P1, each subsite continuously measures the S/N of the uplink signals and reports the filtered value to the primary subsite. A handover will be triggered if the primary subsite detects that the S/N reported by RRU2 is better than that reported by RRU1. During the handover from RRU1 to RRU2, the MS is served by both RRU1 and RRU2, thus preventing the ongoing services from being disrupted. The MS is disconnected from RRU1 after being connected to RRU2.
Issue 08 (2011-09-30)
993
Figure 2-253 Handover
2.58.3.3 Coverage Mode

The multi-site cell feature is applicable to network coverage in certain scenarios such as the high-speed railway lines, tunnels, indoor space, and rural areas.
High-Speed Railway Lines

Generally, the coverage area along a high-speed railway line is in the shape of a stripe. To deploy the network along the high-speed railway line and expand the network coverage, you need to select appropriate antennas, considering the distance between the DBS sites and the railway line. To deploy a private network along the high-speed railway line, the DBS sites should be located close to the railway line. A narrow-beam antenna (azimuth of 30 degree) with high gain is preferred in a DBS site deployed along a straight railway line. Such an antenna provides the satisfactory network coverage and receive level of an MS, and causes less interference to the public network nearby. Alternatively, a wide-beam antenna (azimuth of 65 degree) is required in a DBS site deployed along a winding railway line where large number of buildings are located. Such an antenna reduces the impacts of shadow effect, and improves diffraction of radio waves. To deploy a public network, the DBS sites should be located at the distance of about 500 m from the railway line. A wide-beam antenna (azimuth of 65 degree) is preferred in this case. The radio waves from such an antenna can penetrate through the windows of a train at a large angle of incidence, thus reducing the penetration loss and Doppler shift. In either of the preceding cases, you are advised to deploy the DBS sites alternatively at both sides of a railway line so that users can receive the network signals anywhere inside a train.
There are two coverage modes, namely, two-RRU bidirectional mode and single-RRU bidirectional mode, as shown in Figure 2-254. In two-RRU bidirectional mode, each BBU is configured with two subsites (each consists of one RRU), and each subsite is configured with an antenna radiating radio signals along the high-speed railway lines. In single-RRU bidirectional mode, each BBU along the railway line is configured with one subsite, and the subsite is configured with two antennas radiating the radio signals from a 2-output power divider. Figure 2-254 Network coverage in Two-RRU and Single-RRU bidirectional modes Two-RRU bidirectional mode Single-RRU bidirectional mode
Tunnels
Network coverage in tunnels can be implemented through the deployment of distributed antennas or leakage coaxial cables. To achieve the best coverage with lowest cost, you are advised to deploy distributed antennas in short tunnels and route leakage coaxial cables in middle and long tunnels. l Short tunnels A short tunnel, which is generally within 300 m, is characterized by short coverage distance and low traffic volume.Figure 2-255 shows the network coverage in such a scenario. Therefore, you need to deploy distributed antennas only at tunnel mouths. This facilitates capacity expansion, and simplifies device maintenance. In the case that an MS moves quickly across a short tunnel, handovers may fail due to insufficient overlapping coverage area. To rectify this defect, the multi-site cell feature must be applicable to both inside and outside the tunnel.
Figure 2-255 Network coverage in a short tunnel
Issue 08 (2011-09-30)
995
Middle and long tunnels A middle or long tunnel, generally longer than 300 m, is not fully covered by the network when distributed antennas are deployed only at the tunnel mouths. Figure 2-256 shows the network coverage in such a scenario. To propagate the radio signals across the tunnel, you are advised to deploy more distributed antennas or route leakage coaxial cables in the tunnel. The requirement of the overlapping coverage distance (for example, 694 m) for successful handovers, however, is too strict to be satisfied when an MS moves quickly (for example, at a speed of 250 km/h) across a middle or long tunnel. When the distributed antennas are used, coverage signals in the overlapping coverage area cannot vary smoothly due to the insufficient coverage provided by a single antenna. Instead, the leakage coaxial cable can be used for smooth signal variation. This solution, however, is not economical, because excessive overlapping coverage areas lead to the waste of network resources. Therefore, the multi-site cell feature is required in actual applications regardless of the coverage solution adopted. Huawei recommends that you route leakage coaxial cables for successful handovers inside the tunnels. Figure 2-256 Network coverage in a middle and long tunnel Deployment of distributed antennas Routing leakage coaxial cables
Indoor Space
Distributed antennas are used for network coverage in indoor space. Figure 2-257 shows the network coverage in such a scenario. The signals from the DBS are distributed evenly inside a building through the antenna system including the feeder, power divider, coupler, and antenna. The signal source or relay devices are located in the equipment room, basement, or weak-current cable shaft. The weak-current cables from different floors are routed along the dedicated shaft. The antenna is installed in the space between floors. In the case of network coverage in an elevator, the feeder, antenna, and related accessories are installed against the walls inside the elevator shaft. To compensate for the insufficient transmit power of the signal source in the case of indoor coverage, an active device such as the trunk amplifier or repeater is required for signal relay. The multi-site cell feature, however, takes the place of the relay devices, thus decreasing the interference introduced by active devices, increasing the uplink and downlink sensitivities of the DBS, improving network coverage, stabilizing the network monitoring, and simplifying the maintenance.
Issue 08 (2011-09-30)
996
Figure 2-257 Deployment of distributed antennas
Rural Areas
The DBS (BBU+RRU) with the multi-site cell feature is applicable to the network coverage in rural areas. Figure 2-258 shows the network coverage in such a scenarioIf insufficient coverage in some areas is caused by certain factors, for example, rough topography, subsites, instead of new DBSs, can be configured remotely to serve blind spot areas or enhance the network coverage. The DBS is deployed in the central village, as shown in the following figure. Thus, the network signals are transmitted in the entire village and its neighboring areas. At the same time, extra subsites are deployed remotely among the neighboring villages to expand the coverage in the surrounding areas with weak signals.
Issue 08 (2011-09-30)
997
Figure 2-258 Deployment of a DBS and extra subsites
In the case of low traffic, the multi-site cell feature facilitates the improvement of TRX usage. In the case of high traffic, the multi-site cell is split into two or more, that is, each subsite works independently, thus expanding the capacity smoothly. In this manner, no extra devices and operators are required on site.

l Each CPRI port of the BBU supports cascaded RRUs of three levels. To ensure the consistency of latency in data transmission, Huawei recommends that the RRUs be configured within a distance of 40 km from the BBU. A multi-site cell supports a maximum of six subsites, and each subsite supports a maximum of six TRXs. In the case that the GRRU/MRRU is used, Huawei recommends that a maximum of four TRXs be configured considering that the transmit power should be at an appropriate level. If six TRXs are configured, Huawei recommends that two GRRUs/MRRUs be configured for each subsite. In the configuration of the primary subsite, you are advised to choose the first-level CPRIcascaded subsite that is closest to the BBU. Generally, the RRU acting as the primary subsite should be placed at the same physical site as the BBU. The RRU communicates with the BBU through the CPRI0 port on the GTMU board. The RRUs acting as the primary subsite and secondary subsites must be of the same type, that is, DRRU, GRRU, or MRRU.
l l
Issue 08 (2011-09-30)
998
In the case of the network coverage along the high-speed railway lines, you are advised to disable power control and DTX for the TRXs configured in each subsite to ensure a high success rate of handovers between subsites. As the physical location of each subsite varies, you are advised to adjust the transmit power of each subsite according to the actual conditions, thus decreasing the network interference. You can also set the receive level of the TRXs of each subsite. In the case of coverage along the railway lines, you are advised to deploy the antennas of adjacent subsites at a distance of not longer than 3 km. Huawei recommends that star topology be applied to the BBU and the subsites to ensure the network reliability. For example, when a BBU supports six subsites, each subsite is connected to the BBU in a star network, and communicates with the BBU through a CPRI port on the GTMU board. The TRXs configured on the same subsite can be cascaded.
l l
2.58.5 Parameters
The following describes the parameters related to multi-site cell. For the meaning of each parameter, see Table 2-170. For the default value, value range, and related MML commands of each parameter, see Table 2-171. Table 2-170 Parameter description (1) Parameter ID Description Whether this location group is the main location group. If the value is Yes, this location group is the main location group. If the value is No, this location group is the slave location group. TRX board pass number in the sub-location group to which the TRX of the main location group is bound.
Is Main Local Group Sub-Location Group TRX Board Pass No.
Table 2-171 Parameter description (2) Paramete r Default Value GUI Value Range Actual Value Range Unit MML Comman d ADD BTSLOC GRP (Mandator y) ADD BTSBIND LOCGRP (Mandator y) Impact
Is Main Local Group SubLocation Group TRX Board Pass No.
None
NO(NO), YES (YES)
NO, YES
None
BTS
None
0~7
0~7
None
TRX
Issue 08 (2011-09-30)
999
2.58.6 Counters
None.
2.58.7 Glossary

l l l l l l l BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BBU3900 GSM Hardware Description DBS3900 GSM Installation BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.59 NACC
2.59.1 Introduction
2.59.1.1 Scope
This document describes intra-BSC network assisted cell change (NACC), inter-BSC NACC , and universal terrestrial radio access network to GSM EDGE radio access network (UTRANto-GERAN) NACC in the NACC feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows:
l l
Feature change Feature change refers to the change in the NACC feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Version
02 (2009-09-30)
01 (2009-06-30)
2.59.2 Overview of NACC

NACC, which is short for Network Assisted Cell Change, functions as follows: In NC0/NC1 mode and packet transfer mode, if an MS determines to perform cell reselection, it requests the system information (SI) about the target cell from the BSC. Then, the BSC sends the requested SI through the Cell Change Notification (CCN) procedure. Based on the SI obtained from the BSC, the MS accelerates the PS service access in the target cell, thus shortening the period of PS service disruption during the cell reselection. NACC is generally combined with PACKET SI STATUS. The PACKET SI STATUS procedure is initiated if the MS does not obtain the complete SI about the target cell through the NACC procedure. The combination of these two procedures ensures the normal operation of the PS services, thus reducing the service delay and avoiding any service disruption. An NACC procedure consists of two parts:
l l
When the cell reselection conditions are met, the MS requests the BSC to provide the SI about the target cell through the CCN procedure before the cell reselection. Based on the SI obtained from the BSC, the MS accelerates the initial PS service access in the target cell during the cell reselection.
The MS can initiate an NACC procedure only when an autonomous cell reselection is triggered. In NC0/NC1 mode and packet transfer mode, any of the following events can trigger an NACC procedure: l The path loss criterion C1 indicates that the path loss of the serving cell is too high, that is, the value of the path loss criterion C1 is smaller than 0. The path loss criterion C1 represents the amount of path loss in a cell reselection decision. The MS detects a neighboring cell with stronger signals than the serving cell. In this case, the cell reselection criterion C2 or C32 must be followed. The cell reselection criterion C2 considers the cell reselection offset and cell reselection penalty based on the path loss criterion C1. The cell reselection criterion or cell ranking criterion C32 is the GPRS cell reselection algorithm. The criterion C32 considers the GPRS cell reselection offset, GPRS cell reselection penalty, and cell priority based on the path loss criterion C1. Receiving the downlink signaling fails. The upper application indicates that the authentication procedure fails.
l l
In the GPRS Mobility Management (GMM) Standby state, the MS initiates an autonomous cell reselection regardless of the NC mode but does not initiate an NACC procedure. In dual transfer mode, the MS does not perform any autonomous cell reselection or network-controlled cell reselection and does not initiate any NACC procedure. The cell reselection is controlled by the handover procedure in the CS domain on the network side. NACC is classified into intra-BSC NACC, inter-BSC NACC, and UTRAN-to-GERAN NACC. The GERAN-to-UTRAN NACC is not supported because it is not defined in the 3GPP specifications. The NACC function is enabled through the settings of Support NACC and Network Control Mode. If the serving cell and the target cell are under the same BSC when the MS initiates an NACC procedure, the NACC procedure is an intra-BSC NACC procedure. If they are under different BSCs, the NACC procedure is an inter-BSC NACC procedure. If the serving cell is under an RNC whereas the target cell is under a BSC, the NACC procedure is a UTRAN-toGERAN NACC procedure. When the Iur-g interface does not exist between the UTRAN and GERAN, the UTRAN-to-GERAN NACC procedure is the same as an inter-BSC procedure. In this situation, the BSC is required to support the RIM procedure over the Gb interface. When the Iur-g interface exists between the UTRAN and GERAN, the SI is sent over the Iur-g interface and the RIM procedure over the Gb interface is not required.

2.59.3.1 Intra-BSC NACC
During a cell reselection, NACC is generally combined with PACKET SI STATUS. The NACC procedure enables the MS to obtain the SI about the target cell before the cell reselection. If the SI is not obtained completely, the PACKET SI STATUS procedure enables the MS to obtain the complete SI after the cell reselection. Thus, the combination of NACC and PACKET SI STATUS enables the MS to obtain the complete SI about the target cell. PACKET PSI STATUS,
however, is not supported on the PBCCH because the BSC cannot obtain the PSI of the target cell if the PBCCH is configured in the target cell. Figure 2-259 shows an intra-BSC NACC procedure. Figure 2-259 Intra-BSC NACC procedure
The dashed lines in Figure 2-259 indicate optional procedures. An intra-BSC NACC procedure is described as follows: 1. When an MS determines to initiate an autonomous cell reselection, it enters the CCN mode if the conditions of starting the CCN are met. Then, instead of changing the cell immediately, the MS sends the BSC a PACKET CELL CHANGE NOTIFICATION message, requesting the SI about the target cell. After the reception of the PACKET CELL CHANGE NOTIFICATION message, the BSC sends the MS a PACKET NEIGHBOUR CELL DATA message, containing SI1, SI3, and SI13 about the target cell. Then, the BSC sends the MS a PACKET CELL CHANGE CONTINUE message, instructing the MS to proceed with the cell reselection. After the reception of the PACKET NEIGHBOUR CELL DATA message, the MS saves the SI contained in this message. After the MS receives the PACKET CELL CHANGE CONTINUE message, it changes from the CCN mode to the NC0/NC1 mode and continues with the cell reselection. After the MS changes the cell, it uses the SI about the target cell in the initial PS service access procedure. If the target cell supports the PACKET SI STATUS procedure, that is, the PACKET SI parameter for the target cell is set to Yes, and if the MS does not obtain the complete SI about the target cell after the MS reselects the target cell, the MS sends the BSC a PACKET SI STATUS message, requesting the required SI about the serving cell.
2.
3.
4. 5.
Issue 08 (2011-09-30)
6.
After the reception of the PACKET SI STATUS message, the BSC sends the MS a PACKET SERVING CELL DATA message, containing the required SI about the serving cell. After the reception of the PACKET SERVING CELL DATA message, the MS saves the SI contained in this message. With all SI about the serving cell, the MS can ensure normal operation of the PS services, thus reducing the service delay and avoiding any service disruption.
7.
When the MS is in CCN mode, the BSC cannot change the target cell that the MS determines to reselect by sending a PACKET CELL CHANGE ORDER message.
2.59.3.2 Inter-BSC NACC

The inter-BSC NACC procedure over the Um interface is identical to an intra-BSC NACC procedure. For details, see 2.59.3.1 Intra-BSC NACC. The difference is that the RIM procedure must be supported over the Gb interface in the case of an inter-BSC NACC procedure. That is, the parameter RIM Support of the corresponding NSE must be configured on the BSC side. Before an MS initiates an NACC procedure, the source BSC obtains the SI about the target cell from the target BSC. During the NACC procedure, the MS obtains the SI about the target cell directly from the source BSC, thus accelerating the PS service access in the target cell. Figure 2-260 shows an inter-BSC NACC procedure. The dashed lines indicate optional procedures. Figure 2-260 Inter-BSC NACC procedure
The RIM procedure used in the inter-BSC and UTRAN-to-GERAN NACC is of the following two types:
l l
SI request procedure: This procedure is initiated by the source BSC, requesting the SI of the target BSC. SI update procedure: This procedure is initiated by the target BSC, instructing the source BSC to update the SI about the target cell.
SI Request Procedure
Figure 2-261 SI request procedure
1.
When the serving cell controlled by the source BSC is activated and the transmission link over the Gb interface is set up, the source BSC sends a RAN-INFORMATION-REQUEST (Multiple Report) message to the target BSC through the SGSN to request the setup of the RIM association and to request the SI about the target cell if the serving cell is configured with external neighboring cells and the RIM association between the serving cell and the target cell is not set up. A RIM association is an association between a cell in the target BSC and a cell in the source BSC that requests the application information about the target cell. A RIM association is identified by the ID of the cell in the source cell, ID of the cell in the target cell, and ID of the RIM application. After the target BSC receives the RAN-INFORMATION-REQUEST (Multiple Report) message, it sends the source BSC a RAN-INFORMATION (Multiple Report-Initial) message, containing the information about the established RIM association and the SI (including SI1, SI3, and SI13) about the target cell. After the reception of the RAN-INFORMATION (Multiple Report-Initial) message, the source BSC saves the information about the existing RIM association and the SI about the target cell. The SI about the target cell is used in the subsequent NACC procedure.
2.
3.
Issue 08 (2011-09-30)
1005
SI Update Procedure
Figure 2-262 SI update procedure
1.
After the RIM association is set up, the target BSC sends the source BSC a RANINFORMATION (Multiple Report) message, containing the updated SI (including SI1, SI3, and SI13) about the target cell if the SI is changed. After the reception of the RAN-INFORMATION (Multiple Report) message, the source BSC updates the SI about the target cell and sends a RAN-INFORMATION-ACK message to the target BSC. The SI about the target cell is used in the subsequent NACC procedure.
2.
2.59.3.3 UTRAN-to-GERAN NACC

The UTRAN-to-GERAN NACC procedure is classified into the normal NACC procedure and the optimized NACC procedure according to whether the Iur-g interface exists.
Normal NACC Procedure

If no Iur-g interface exists between the UTRAN and the GERAN, the UTRAN-to-GERAN NACC procedure is a normal NACC procedure, which is identical to an inter-BSC NACC procedure. For details, see 2.59.3.2 Inter-BSC NACC.
Optimized NACC Procedure

If the Iur-g interface exists between the UTRAN and the GERAN, the UTRAN-to-GERAN NACC procedure is an optimized NACC procedure. In this case, the UE obtains the SI about the target cell directly over the Iur-g interface without negotiating with the SGSN. Figure 2-263 shows an optimized NACC procedure.
Issue 08 (2011-09-30)
1006
Figure 2-263 Optimized NACC procedure
The NACC procedure is started by setting Allow Info Exchange at Iur-g and Info Exchange Content. Before a UE performs the optimized NACC procedure, the RNC sends the BSC an INFORMATION EXCHANGE INITIATION REQUEST message over the Iur-g interface, requesting the SI about the target cell. Then, the BSC responds with the INFORMATION EXCHANGE RESPONSE message. During the optimized NACC procedure, the UE directly obtains the SI about the target cell saved in the RNC, thus accelerating the PS service access in the target cell.
2.59.4 Parameters
The following describes the parameters related to NACC. For the meaning of each parameter, see Table 2-172. For the default value, value range, and related MML commands of each parameter, see Table 2-173. Table 2-172 Parameter description (1) Paramete r Description Whether to support the network assisted cell change (NACC). The NACC is used in the network control modes NC0, NC1 or NC2. The NACC enables the network to notify the MS of the system information of the neighboring cell when the MS is in the packet transmission state. In this way, the MS can reselect a cell in a shorter time. Network control mode for cell reselection of the MS. There are three modes. NC0: normal MS control. The MS shall perform autonomous cell re-selection. NC1: MS control with measurement reports. The MS shall send measurement reports to the network and the MS shall perform autonomous cell re-selection. NC2: network control. The MS shall send measurement reports to the network . The MS shall only perform autonomous cell re-selection when the reselection is triggered by a downlink signaling failure or a random access failure.When this parameter is set to NC2 and "Support NC2" in "SET GCELLGPRS" is set to "YES", the network side can control the cell reselection for the MS.
Support NACC
Issue 08 (2011-09-30)
1007
Paramete r
Description Whether the cell supports the PACKET SI STATUS flow. In the PACKET SI STATUS flow, the MS sends the Packet PSI/SI Status message to indicate that the MS has stored the system message. The network side sends the Packet Serving Cell Data message to notify the MS of the system message not stored. Whether to support RAN information management (RIM). IN the RIM procedure, RANs(Radio Access Network) can exchange messages through the core network.
PACKET SI RIM Support Allow Info Exchange at Iur-g Info Exchange Content
Whether to support the bidirectional information exchange procedure on the Iurg interface.
Information exchange content to be supported.
Table 2-173 Parameter description (2) Paramete r Default Value GUI Value Range Actual Value Range Unit MML Comman d SET GCELLG PRS (Optional) Impact
Support NACC
NO
NO(No), YES(Yes) NC0 (NC0), NC1 (NC1), NC2 (NC2)
NO, YES
None
Cell
NC0
NC0, NC1, NC2
None
SET GCELLPS BASE (Optional) SET GCELLG PRS (Optional)
Cell
PACKET SI
NO
NO(No), YES(Yes) NO(No Support), YES (Support) NO(No Support), YES (Support)
NO, YES
None
Cell
RIM Support Allow Info Exchange at Iur-g
NO
NO, YES
None
ADD NSE (Optional) ADD GNRNC (Optional)
NSE
NO
NO, YES
None
BSC
Issue 08 (2011-09-30)
1008
Paramete r
Default Value
GUI Value Range CELLCA PCLASS, NACCRE LATED
Actual Value Range CELLCA PCLASS, NACCRE LATED
Unit
MML Comman d ADD GNRNC (Mandator y)
Impact
Info Exchange Content
CELLCA PCLASS
None
BSC
2.59.5 Counters
2.59.6 Glossary

l l l l l l l l l l l l 3GPP TS 45.008: "Radio subsystem link control" 3GPP TS 44.060: "Radio Link Control (RLC) / Medium Access Control (MAC) protocol" 3GPP TS 43.064: "Overall description of the GPRS Radio Interface; Stage 2" 3GPP TS 44.018: "BSS GPRS Protocol (BSSGP)" 3GPP TS 44.901: "External Network Assisted Cell Change (NACC)" 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive mod" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.60 NC2
2.60.1 Introduction
2.60.1.1 Scope
This document describes network control mode 2 (NC2) procedure, cell reselection algorithms, and cell reselection type in the NC2 feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the NC2 feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Version
02 (2009-09-30)
01 (2009-06-30)
Compared with 02 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 has no change.
2.60.2 Overview
Network Control Mode 2 (NC2) indicates network-controlled cell reselection. In the NC2 mode and GPRS Mobility Management (GMM) Ready state, the MS periodically sends packet measurement reports to the BSC. In the GMM Ready state, the MS is attached to the GPRS network and an Mobility Management (MM) context is established between the MS and the SGSN. The MS can not only receive paging messages and downlink signaling but also transmit and receive packet data. The BSC determines whether to perform cell reselection according to the packet measurement report from the MS and the current load in the serving cell and in the neighboring cell. If a cell reselection is required, the BSC sends the Packet Cell Change Order message to instruct the MS to reselect the target cell. Compared with the autonomous cell reselection of the MS, the network-controlled cell reselection comprehensively considers such factors as the received signal level and load status in the serving cell and the neighboring cell so that the MS can reselect a proper cell. In this way, the loads in the cells can be balanced. In NC2 mode, any of the following events triggers a network-controlled cell reselection. l l l The MS signal strength keeps falling, and a neighboring cell with greater signal strength exists. The MS signal quality keeps deteriorating, and a neighboring cell with better signal quality exists. The serving cell of the MS is overloaded, and a neighboring cell with lighter load and greater signal strength exists.
In NC2 mode, any of the following events triggers an autonomous cell reselection rather than a network-controlled cell reselection. l l l l Downlink signaling reception fails. Attempts to access the network fail. Visits to the serving cell are inhibited. The path loss rule C1 indicates that the path loss of the serving cell is too high, that is, the value of the path loss rule C1 is smaller than 0. Path loss rule C1 is used to indicate the amount of path loss in a cell reselection decision.
In the GMM Standby state, the MS is attached to the GPRS network and an MM context is established between the MS and the SGSN. The MS can receive paging messages and downlink signaling but cannot transmit or receive packet data. The MS initiates autonomous cell reselection regardless of the NC mode. In Dual Transfer Mode (DTM) mode, the MS does not perform any autonomous cell reselection or network-controlled cell reselection. Cell reselection is controlled by the CS domain handover procedure at the network side. The BSC supports NC2 only in packet transfer mode. NC2 in packet idle mode is not supported. l NC2 in packet idle mode After an MS in packet idle mode completes the packet/immediate assignment procedure on the PCCCH/CCCH, it periodically sends packet measurement reports to the BSC through the PCCCH/CCCH. The period of sending packet measurement reports is determined by the Cell Reselection MR Period in Packet Idle Mode parameter. Through the PCCCH/CCCH, the BSC sends the Packet Cell Change Order message to the MS to instruct the MS to implement cell reselection and execute an NC2 procedure in packet idle mode.
NC2 in packet transfer mode An MS in packet transfer mode periodically sends packet measurement reports to the BSC through the PACCH. The period of sending packet measurement reports is determined by the Cell Reselection MR Period in Packet Transfer Mode parameter. Through the PACCH, the BSC sends the Packet Cell Change Order message to the MS to instruct the MS to implement cell reselection and execute an NC2 procedure in packet transfer mode.
The NC2 feature support intra-BSC cell reselection, inter-BSC cell reselection, and GSM-toUTRAN cell reselection. During an NC2 procedure, the cell reselection can be accelerated.

2.60.3.1 Procedure
If the cell configuration parameter Support NC2 is set to YES(Yes) and Network Control Mode is set to nc2(nc2), NC2 is enabled. If the Support NACC parameter is set to YES (Yes), the cell reselection procedure in NC2 can be accelerated. Figure 2-264 shows the cell reselection in NC2. Figure 2-264 Cell reselection in NC2
Issue 08 (2011-09-30)
1012
1. 2.
An MS in the GMM Ready state periodically sends Packet Measurement Report messages or Packet Enhanced Measurement Report messages to the BSC. After receiving the packet measurement report, the BSC processes the measurement results. According to the NC2 cell reselection algorithm, the BSC determines whether to perform a cell reselection and the target cell for reselection. If the BSC determines to initiate a cell reselection, it sends the Packet Cell Change Order message to the MS to instruct the MS to reselect the specified target cell. If the Support NACC parameter is set to YES(Yes), the BSC needs to send Packet Neighbour Cell Data message containing the system information of the target cell to the MS before sending the Packet Cell Change Order message to the MS so that the cell reselection can be accelerated. If a cell reselection fails, the MS sends the Packet Cell Change Failure message to the BSC. After receiving this message, the BSC subtracts Cell Penalty Level from the received signal level of the target cell.
3.
4.
2.60.3.2 Cell Reselection Algorithms

The NC2 cell reselection algorithms are the urgent reselection algorithm, load reselection algorithm, and normal reselection algorithm. The priority-based sequence of these algorithms in descending order is urgent reselection algorithm, load reselection algorithm, and normal reselection algorithm. The Cell Urgent Reselection Allowed, Cell Load Reselection Allowed, and Cell Normal Reselection Allowed parameters are used to enable or disable the urgent reselection, load reselection, and normal reselection algorithm respectively. When the NC2 Load Reselection Switch parameter is set to Support, the load of the GSM candidate cells under the same BSC is considered during cell reselection. When the NC2 Load Reselection Switch parameter is set to NotSupport, the load of the candidate cells is not considered during cell reselection. The NC2 Load Broadcast Period parameter specifies the interval at which a cell broadcasts its current load to its neighboring cells under the same BSC.
Urgent Reselection Algorithm

Urgent reselection is based on the receive quality. Based on the receive quality of the radio link on the Um interface, the BSC determines whether a cell reselection must be performed. The receive quality or bit error rate (BER) indicates the receive quality on the radio link. If the BER increases, the possible cause is that the signal level is too low or there is interference on the channel. In this case, the BSC instructs the MS to reselect a neighboring cell with higher signal level. In a measurement period of the receive quality, if the MS receive quality deterioration ratio is greater than Cell Rx Quality Worsen Ratio Threshold, urgent reselection is started. MS receive quality deterioration ratio indicates the ratio of times of bad MS downlink quality to number of downlink quality measurement reports. In an urgent reselection, the cell with the highest priority is selected as the target cell from the candidate cell list. The priority of a cell is determined by the received signal level and the characteristics information such as cell type, cell priority, and support of EDGE, about the cell. When the NC2 Load Reselection Switch parameter is set to Support, the characteristics information about a cell also includes the load of the GSM candidate cells under the same BSC. A candidate neighboring cell must meet any of the following conditions:
l l
Receive level of the candidate neighboring GSM cell > Max (Receive level of the serving cell, Cell Reselection Level Threshold) + Cell Reselection Hysteresis Measured ratio of energy per modulating bit to the noise spectral density (Ec/No) of the neighboring Frequency Division Duplex (FDD) cell > PS FDD Ec/No Quality Threshold, or measured Received Signal Code Power (RSCP) of the neighboring FDD cell > PS FDD RSCP Quality Threshold. Measured RSCP of the neighboring Time Division Duplex (TDD) cell > PS TDD RSCP Quality Threshold. When the NC2 Load Reselection Switch parameter is set to Support, the candidate neighboring cell under the same BSC must not be congested.
l l
When a cell reselection fails, a penalty must be applied to the target cell. If the time of the penalty applied to the target cell is within Cell Penalty Duration, Cell Penalty Level is subtracted from the received signal level of the target cell. If the received signal level of the target cell is smaller than Cell Penalty Level, the received signal level of the target cell should be set to 0.
Load Reselection Algorithm

In the network, the load in some cells are heavy, whereas the load in other cells are light. To balance the load in these cells, load reselection is performed. In a load reselection procedure, some MSs in heavy-loaded cells are directed to light-loaded cells. In addition, the MSs in neighboring cells should not be reselected to heavy-loaded cells. Figure 2-265 shows the cell load reselection mode. Figure 2-265 Load reselection
To determine the traffic load of a cell, compare the channel multiplexing rate with the predefined threshold: l If the average channel multiplexing rate of a cell is higher than Load Reselection Start Threshold, the traffic load in the cell is heavy, and the load reselection algorithm should be enabled. If the average channel multiplexing rate of a cell is lower than Load Reselection Receive Threshold, the traffic load in the cell is light and some loads in heavy-loaded cells can be redirected to this cell.
In load reselection mode, an MS with too high signal levels cannot be reselected to a neighboring cell. By setting Load Reselect Level Threshold, only the MS whose signal level is lower than Load Reselect Level Threshold can be reselected to a neighboring cell. When the serving cell
is overloaded and the received signal level in this cell is lower than Load Reselect Level Threshold, a cell load reselection is triggered. In a load reselection, the cell with the highest priority is selected as the target cell from the candidate cell list. The priority of a cell is determined by the received signal level and the characteristics information such as cell type, cell priority, and support of EDGE, about the cell. When the NC2 Load Reselection Switch parameter is set to Support, the characteristics information about a cell also includes the load of the GSM candidate cells under the same BSC. A candidate neighboring cell must meet any of the following conditions: l l l l Receive level of the candidate neighboring GSM cell > Max (Receive level of the serving cell, Cell Reselection Level Threshold) + Cell Reselection Hysteresis Measured Ec/No of the neighboring FDD cell > PS FDD Ec/No Quality Threshold, or Measured RSCP of the neighboring FDD cell > PS FDD RSCP Quality Threshold. Measured RSCP of the neighboring TDD cell > PS TDD RSCP Quality Threshold. When the NC2 Load Reselection Switch parameter is set to Support, the candidate neighboring cell under the same BSC must not be congested.
When a cell reselection fails, a penalty must be applied to the target cell. If the time of the penalty applied to the target cell is within Cell Penalty Duration, Cell Penalty Level is subtracted from the received signal level of the target cell. If the received signal level of the target cell is smaller than Cell Penalty Level, the received signal level of the target cell should be set to 0.
Normal Reselection Algorithm

Normal reselection is based on the received signal level. When the conditions of urgent reselection and load reselection are not met, normal reselection is started to direct the MS to a neighboring cell with higher signal strength if the received signal level of the serving cell is lower than Cell Reselection Level Threshold for a period of time. The P/N criterion should be met before normal reselection is started. That is, in Normal Cell Reselection Watch Period, if the number of times that the received signal level of the serving cell is lower than Cell Reselection Level Threshold reaches Normal Cell Reselection Worsen Level Threshold, normal reselection is started. The parameters used for P/N criterion judgment must be configured for the neighboring cells. In different radio conditions, these parameters should be configured differently for the neighboring cells to ensure that an optimal target cell is selected during handover. In a normal reselection, the cell with the highest priority is selected as the target cell from the candidate cell list. The priority of a cell is determined by the received signal level and the characteristics information such as cell type, cell priority, and support of EDGE, about the cell. When the NC2 Load Reselection Switch parameter is set to Support, the characteristics information about a cell also includes the load of the GSM candidate cells under the same BSC. A candidate neighboring cell must meet any of the following conditions: l l l l Receive level of the candidate neighboring GSM cell > Max (Receive level of the serving cell, Cell Reselection Level Threshold) + Cell Reselection Hysteresis Measured Ec/No of the neighboring FDD cell > PS FDD Ec/No Quality Threshold, or Measured RSCP of the neighboring FDD cell > PS FDD RSCP Quality Threshold. Measured RSCP of the neighboring TDD cell > PS TDD RSCP Quality Threshold. When the NC2 Load Reselection Switch parameter is set to Support, the candidate neighboring cell under the same BSC must not be congested.
When a cell reselection fails, a penalty must be applied to the target cell. If the time of the penalty applied to the target cell is within Cell Penalty Duration, Cell Penalty Level is subtracted from
the received signal level of the target cell. If the received signal level of the target cell is smaller than Cell Penalty Level, the received signal level of the target cell should be set to 0.
2.60.3.3 Cell Reselection Type

Based on reselected target cell, each NC2 cell reselection algorithm contains three NC2 cell reselection types: intra-BSC cell reselection, inter-BSC cell reselection, and GSM-to-UTRAN cell reselection.
Intra-BSC Cell Reselection

For the intra-BSC cell reselection, the serving cell and the target cell are controlled by the same BSC. In the list of candidate cells, the target cell is selected by priority of the cell. The selected target cell is the one that has the highest priority in the list.
Inter-BSC Cell Reselection

For the inter-BSC cell reselection, the serving cell and the target cell are controlled by different BSCs and are both GSM cells. For the inter-BSC cell reselection, the priority of the external neighboring GSM cells should be lowered. The priority of the external neighboring GSM cells must be lower than that of the internal neighboring cells, which equals the received signal level of the external neighboring GSM cell minus an external cell reselection offset. This external cell reselection offset equals MAX(2, Cell Reselection Hysteresis/2). The protocol does not allow a BSC to obtain the information about the load in an external neighboring cell. This means that the load in an external neighboring cell is unknown during a cell load reselection. Therefore, all external neighboring cells are treated as cells without congestion.
GSM-to-UTRAN Cell Reselection

A GSM-to-UTRAN cell reselection is an NC2 cell reselection in which the serving cell is a GSM cell, and the target cell is a UTRAN cell. The target cell can be either a WCDMA cell or a TDSCDMA cell. For the GSM-to-UTRAN cell reselection, the 3G measurement reports and the 2G/3G cell priority strategy should be processed. In the inter-RAT cell reselection, if the list of candidate cells contains both 2G cell and 3G cell, the 2G/3G Cell Reselection Strategy determines which cell is selected as the candidate cell. If 2G/3G Cell Reselection Strategy is set to 2G(Preference for 2G Cell), the 2G cell is preferred as the target cell. If 2G/3G Cell Reselection Strategy is set to 3G(Preference for 3G Cell), the 3G cell is preferred as the target cell. A neighboring 3G cell can be selected from the list of candidate cells only when the quality of the measurement reports from the neighboring 3G cell is greater than the 3G cell reselection quality threshold. During the cell reselection, a cell with the highest priority is selected from the list of candidate cells and is regarded as the target cell. For a neighboring FDD cell, both the RSCP measurement quality type and the Ec/No measurement quality type are supported. For a neighboring TDD cell, the RSCP measurement quality type is supported. The protocol does not allow a BSC to obtain information about the load in an external neighboring 3G cell. This means that the load in an external 3G neighboring cell is unknown during a cell load reselection. Therefore, all external neighboring 3G cells are treated as cells without congestion.
2.60.4 Parameters
The following describes the parameters related to NC2. For the meaning of each parameter, see Table 2-174. For the default value, value range, and related MML commands of each parameter, see Table 2-175. Table 2-174 Parameter description (1) Parameter Cell Reselection MR Period in Packet Idle Mode Cell Reselection MR Period in Packet Transfer Mode Description Cell reselection measurement report period in packet idle mode. Cell reselection measurement report period in packet transmission mode. Whether to support the network control 2 (NC2). The NC2 enables the network side to control the cell reselection for the MS when the MS reports the measurement report of the local cell and the neighboring cell.When this parameter is set to "YES" and "Network Control Mode" in "SET GCELLPSBASE" is set to "NC2", the network side can control the cell reselection for the MS. Network control mode for cell reselection of the MS. There are three modes. NC0: normal MS control. The MS shall perform autonomous cell re-selection. NC1: MS control with measurement reports. The MS shall send measurement reports to the network and the MS shall perform autonomous cell reselection. NC2: network control. The MS shall send measurement reports to the network . The MS shall only perform autonomous cell re-selection when the reselection is triggered by a downlink signaling failure or a random access failure.When this parameter is set to NC2 and "Support NC2" in "SET GCELLGPRS" is set to "YES", the network side can control the cell reselection for the MS. Whether to support the network assisted cell change (NACC). The NACC is used in the network control modes NC0, NC1 or NC2. The NACC enables the network to notify the MS of the system information of the neighboring cell when the MS is in the packet transmission state. In this way, the MS can reselect a cell in a shorter time. When the cell reselection failure message is received or the load cell reselection is initiated, the "Cell Penalty Level" is subtracted from the receive level of the target cell to avoid that cell reselection failure occurs repeatedly or that multiple MSs are reselected to the same target cell. This parameter is valid only within "Cell Penalty Duration".
Support NC2
Support NACC
Cell Penalty Level
Issue 08 (2011-09-30)
1017
Parameter
Description Whether to allow cell urgent reselection. If this parameter is set to PERMIT and [NC2 Load Reselection Switch is set to Support, the load of the target cell is involved in the algorithm for NC2 cell reselection. Whether to allow the cell load reselection. If this parameter is set to PERMIT and "NC2 Load Reselection Switch" is set to Support, the load of the target cell is involved in the algorithm for NC2 cell reselection. Whether to allow the cell normal reselection. If this parameter is set to PERMIT and "NC2 Load Reselection Switch" is set to Support, the load of the target cell is involved in the algorithm for NC2 cell reselection. Whether to involve the load of the target cell in the algorithm for NC2 cell reselection. If this parameter is set to Support, the load of the target cell is involved in the algorithm for NC2 cell reselection. Intervals that the BSC broadcasts a cell's traffic load to its neighbor cells. The uplink load and downlink load indicate the traffic situation of a cell. The uplink load = number of uplink TBFs carried on all PDCHs in a cell / total number of PDCHs in a cell x ("PDCH Uplink Multiplex Threshold"/10) x 100%. The downlink load = number of downlink TBFs carried on all PDCHs in a cell / total number of PDCHs in a cell x ("PDCH Downlink Multiplex Threshold"/10) x 100%. The number of times that the downlink transmission quality of the MS is lower than the transmission quality threshold of the MS ("EDGE GMSK Quality Threshold", "EDGE 8PSK Quality Threshold", or "GPRS Quality Threshold" by TBF type) is calculated accumulatively. When the rate of the accumulated value to the number of received measurement reports on the downlink transmission quality (Packet Downlink Ack/Nack message) is greater than or equal to the value of this parameter, the emergency reselection is triggered. Minimum receive level for a neighbor cell to become a candidate cell during cell reselection. When the receive level of the serving cell is lower than the value of this parameter, it indicates that the normal cell reselection level is bad. In this case, the parameter value is used for the calculation of the times of the occurrence of bad normal cell reselection level. Indicating that during cell reselection, the level of the target cell should meet the following condition: Level of target cell > [MAX (level of serving cell, "Cell Reselection Level Threshold") + "Cell Reselection Hysteresis"]. In this way, pingpong handovers do not occur.
Cell Urgent Reselection Allowed
Cell Load Reselection Allowed
Cell Normal Reselection Allowed
NC2 Load Reselection Switch
NC2 Load Broadcast Period
Cell Rx Quality Worsen Ratio Threshold
Cell Reselection Level Threshold
Cell Reselection Hysteresis
Issue 08 (2011-09-30)
1018
Parameter PS FDD Ec/No Quality Threshold PS FDD RSCP Quality Threshold PS TDD RSCP Quality Threshold
Description Minimum Ec/No of the 3G FDD cell candidate. Minimum RSCP of the 3G FDD cell candidate. Minimum RSCP quality threshold that the TDD 3G candidate cell must reach. Penalty duration for cell reselection. Cell penalty can be performed only in this duration. When this parameter is set to a greater value, the MS cannot reselect a cell for a longer time in the case of reselection failure or reselection due to load. The penalty timer is shorter when this parameter is set to a smaller value. When the uplink load or downlink load of the cell exceeds this threshold, the load reselection decision is made. When the uplink load or downlink load of the target cell is lower than this threshold, it can accept the MSs from the serving cell due to load reselection. Threshold for allowing the MS to reselect a cell during load reelection. When the receive level of the serving cell is lower than this threshold, the load reselection is triggered. The number of received Packet Measurement Report messages on the receive level of the serving cell is measured continuously. When the statistical value is greater than or equal to the value of this parameter, the normal reselection decision is made. If the number of times when the receive level of the serving cell within "Normal Cell Reselection Watch Period" is lower than "Cell Reselection Level Threshold" is greater than the value of this parameter, the normal cell reselection is triggered. This parameter specifies whether a 2G cell or 3G cell is selected in the inter-RAT cell reselection procedure.
Cell Penalty Duration Load Reselection Start Threshold Load Reselection Receive Threshold Load Reselect Level Threshold
Normal Cell Reselection Watch Period
Normal Cell Reselection Worsen Level Threshold 2G/3G Cell Reselection Strategy
Issue 08 (2011-09-30)
1019
Table 2-175 Parameter description (2) Paramete r Default Value GUI Value Range 0.48sec (0.48sec), 0.96sec (0.96sec), 1.92sec (1.92sec), 3.84sec (3.84sec), 7.68sec (7.68sec), 15.36sec (15.36sec) , 30.72sec (30.72sec) , 61.44sec (61.44sec) 0.48sec (0.48sec), 0.96sec (0.96sec), 1.92sec (1.92sec), 3.84sec (3.84sec), 7.68sec (7.68sec), 15.36sec (15.36sec) , 30.72sec (30.72sec) , 61.44sec (61.44sec) Actual Value Range Unit MML Comman d Impact
Cell Reselectio n MR Period in Packet Idle Mode
15.36sec
SET GCELLN WCTRL MSRPAR A (Optional)
Cell
Cell Reselectio n MR Period in Packet Transfer Mode
0.96sec
SET GCELLN WCTRL MSRPAR A (Optional) SET GCELLG PRS (Optional)
Cell
Support NC2
NO
NO(No), YES(Yes) NC0 (NC0), NC1 (NC1), NC2 (NC2)
NO, YES
None
Cell
NC0
NC0, NC1, NC2
None
Cell
Issue 08 (2011-09-30)
1020
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLG PRS (Optional) SET GCELLN C2PARA (Optional) SET GCELLN C2PARA (Optional) SET GCELLN C2PARA (Optional) SET GCELLN C2PARA (Optional) SET BSCPSSO FTPARA (Optional) SET BSCPSSO FTPARA (Optional) SET GCELLN C2PARA (Optional) SET GCELLN C2PARA (Optional) SET GCELLN C2PARA (Optional)
Impact
Support NACC Cell Penalty Level Cell Urgent Reselectio n Allowed Cell Load Reselectio n Allowed Cell Normal Reselectio n Allowed
NO
NO(No), YES(Yes)
NO, YES
None
Cell
30
0~63 FORBID (Forbid), PERMIT (Permit) FORBID (Forbid), PERMIT (Permit) FORBID (Forbid), PERMIT (Permit) NotSuppo rt(Not Support), Support (Support)
0~63
None
Cell
PERMIT
FORBID, PERMIT
None
Cell
PERMIT
FORBID, PERMIT
None
Cell
PERMIT
FORBID, PERMIT NOTSUP PORT, SUPPOR T
None
Cell
NC2 Load Reselectio n Switch NC2 Load Broadcast Period Cell Rx Quality Worsen Ratio Threshold Cell Reselectio n Level Threshold Cell Reselectio n Hysteresis
NOTSUP PORT
None
BSC
1~10
1~10
BSC
30
0~100
0~100
per cent
Cell
15
0~63
0~63
None
Cell
0~63
0~63
None
Cell
Issue 08 (2011-09-30)
1021
Paramete r PS FDD Ec/No Quality Threshold PS FDD RSCP Quality Threshold PS TDD RSCP Quality Threshold Cell Penalty Duration Load Reselectio n Start Threshold Load Reselectio n Receive Threshold Load Reselect Level Threshold Normal Cell Reselectio n Watch Period Normal Cell Reselectio n Worsen Level Threshold
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d ADD GEXT3G CELL (Optional) ADD GEXT3G CELL (Optional) ADD GEXT3G CELL (Optional) SET GCELLN C2PARA (Optional) SET GCELLN C2PARA (Optional) SET GCELLN C2PARA (Optional) SET GCELLN C2PARA (Optional) SET GCELLN C2PARA (Optional)
Impact
10
0~49
0~49
dB
Cell
10
0~63
0~63
None
Cell
10
0~63
0~63
None
Cell
10
0~255
0~255
Cell
85
0~100
0~100
per cent
Cell
60
0~100
0~100
per cent
Cell
40
0~63
0~63
None
Cell
10
1~32
1~32
None
Cell
1~32
1~32
None
SET GCELLN C2PARA (Optional)
Cell
Issue 08 (2011-09-30)
1022
Paramete r
Default Value
GUI Value Range 2G (Preferenc e for 2G Cell), 3G (Preferenc e for 3G Cell)
Actual Value Range
Unit
MML Comman d
Impact
2G/3G Cell Reselectio n Strategy
2G
2G, 3G
None
SET GCELLN C2PARA (Optional)
Cell
2.60.5 Counters
2.60.6 Glossary

l l l l l l l l l l 3GPP TS 45.008: "Radio subsystem link control" 3GPP TS 44.060: "Radio Link Control (RLC) / Medium Access Control (MAC) protocol" 3GPP TS 43.064: "Overall description of the GPRS Radio Interface; Stage 2" 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive mod" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.61 Networking Modes

2.61.1 Introduction
2.61.1.1 Scope
This document describes the networking modes, LAPD multiplexing at Abis interface, and 16 kbit/s LAPD signaling link.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the networking modes feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of BSS8.1, issue 01 (2009-06-30) of GBSS9.0 has no change.
2.61.2 Overview
Networking mode refers to the mode of connections between the BTS and the BSC. The networking mode can be star, chain, tree, or ring networking mode. In actual engineering scenarios, a combination of the networking modes is usually applied. Reasonable application of the networking modes can greatly reduce the investment in the transmission equipment while providing satisfactory service quality. An operator can select an appropriate networking mode according to the actual equipment and transmission. The BSC supports flexible networking modes over the Abis interface: star, chain, tree, and ring. l Star networking mode The star networking mode applies to common scenarios, especially densely populated areas such as urban areas. l Chain networking mode The chain networking mode applies to sparsely populated areas in the strip-like terrain, such as areas along highways and railway tracks. l Tree networking mode The tree networking mode applies to areas where network structures, BTS distribution, and subscriber distribution are complicated, such as the overlapping areas between the largescale coverage and the hot spot or between the large-scale coverage and the small-scale coverage. l Ring networking mode The ring networking mode applies to common scenarios. Due to its strong self-healing capability, the ring networking mode is preferably applied so long as the transmission links meet the networking requirements. The Link Access Protocol on the D Channel (LAPD) link has two configuration modes: LAPD multiplexing at Abis interface and 16 kbit/s LAPD signaling link. All the signaling links of a BTS can be configured in only one mode.

2.61.3.1 Networking Modes Star Networking Mode
In star networking mode, each BTS is directly connected to the BSC and the BTS is not connected to other BTSs. The star networking mode is the most common networking mode. It is typically used in the densely populated areas, such as cities. Figure 2-266 shows the star networking mode.
Issue 08 (2011-09-30)
1025
Figure 2-266 Star networking mode
Advantages: l l l l l Simple networking Easy engineering Convenient maintenance Flexible capacity expansion High network reliability
Disadvantages: Compared with other networking modes, the star networking mode requires more transmission cables. In the case of small-capacity BTS, the transmission resource usage of the star networking mode is low. To solve this problem, the timeslot cross connection device can be used.
Chain Networking Mode

In chain networking mode, BTSs are cascaded on a chain. Each BTS on the chain processes its own timeslots and transparently transmits the signals on the timeslots of the lower-level BTSs. Figure 2-267 shows the chain networking mode. Figure 2-267 Chain networking mode
The chain networking mode applies to sparsely populated areas in strip-like terrain, such as areas along highways and railway tracks. If the star networking mode is used in this scenario, transmission resources may be wasted. To avoid the waste, the chain networking mode can be applied. Advantages:
The chain networking mode can reduce the cost of transmission equipment and engineering construction and save the rent for the transmission links. Disadvantages: l l l The reliability of the transmission link is poor because the signal transmission passes through multiple nodes. A faulty BTS may affect the normal operation of its lower-level BTSs. The number of cascading levels must not exceed five.
Tree Networking Mode

In tree networking mode, a BTS is connected to more than one lower-level BTS. The tree networking mode is actually a combination of the chain and star networking modes. Figure 2-268 shows the tree networking mode. Figure 2-268 Tree networking mode
The tree networking mode has the characteristics of the star and chain networking modes. It has a higher reliability than the chain networking mode but a lower reliability than the star networking mode. Advantages: The tree networking mode requires less transmission cables than the star networking mode. Disadvantages: l In tree networking mode, the signal transmission passes through multiple nodes; therefore, the transmission reliability is relatively low, the engineering construction is difficult, and it is not convenient to maintain. A faulty BTS may affect the normal operation of its lower-level BTSs. Capacity expansion is difficult because it may require major modification to the network structure. The number of cascading levels must not exceed five.
l l l
Issue 08 (2011-09-30)
Ring Networking Mode

The ring networking mode is a special chain or star networking mode. Several BTSs form a chain, and the lowest-level BTS is connected to the BSC, thus forming a ring. If there is a breaking point on the ring, the BTSs that precede the break point remain unchanged in networking mode whereas the BTSs that follow the break point form a new chain connection in the reverse direction. For details, see 2.21 BTS Ring Topology. Figure 2-269 shows the ring networking mode. Figure 2-269 Ring networking mode
The ring networking mode applies to common scenarios. Due to its strong self-healing capability, the ring topology is preferably applied so as long transmission is permitted. Advantages: The ring networking mode has a strong self-healing capability. If the E1 link at a point is broken, a new chain connection can be formed without affecting the ongoing services. Disadvantages: There is always a transmission link segment that does not transmit any data.
2.61.3.2 LAPD Multiplexing at Abis Interface

LAPD multiplexing refers to the multiplexing of the LAPD signaling on the E1 timeslots over the Abis interface. The BSC supports six n:1 (n <= 6) 64 kbit/s multiplexing modes: 1:1, 2:1, 3:1, 4:1, 5:1, and 6:1. The multiplexing of the LAPD signaling can increase the transmission link utilization on the Abis interface and reduce the cost of the operator. In n:1 E1 timeslot multiplexing mode, the speech rate is 16 kbit/s (full rate) or 8 kbit/s (half rate) and four full-rate (or eight half-rate) speech channels occupy one 64 kbit/s E1 timeslot; the rate of the signaling link is 64 kbit/s, and n signaling timeslots occupy one 64 kbit/s E1 timeslot. The Abis interface board (EIUa/OIUa) in the BSC implements the 64 kbit/s switching of all the timeslots. A EIUa or OIUa in the BSC can support more than one multiplexing mode at the same time. Signals can be transparently transmitted between cascaded BTSs; therefore, an E1 link can also support multiple multiplexing modes, as shown in Figure 2-270.
Figure 2-270 Application of multiple multiplexing modes
As shown in Figure 2-270, the four E1 links are A0, A1, A2, and A3. Assume that the multiplexing modes of BTS0, BTS1, BTS2, and BTS3 are 1:1, 1:2, 1:3, and 1:4 respectively. Then, there are four multiplexing modes on the EIUa/OIUa. l l l l There are four multiplexing modes on A0. There are two multiplexing modes on A1: 2:1 and 4:1. There is one multiplexing mode on A2: 3:1. There is one multiplexing mode on A3: 4:1.
Suggestions on Selecting the Multiplexing Mode When the TRX supports the half rate feature, the 2:1 multiplexing ratio is recommended. If all the TRXs are in full rate, the 4:1 or higher multiplexing ratio is recommended. The LAPD multiplexing mode is specified by Multiplexing Mode. Constraints of the Multiplexing Mode The multiplexing mode is not affected by the local switching and the Flex Abis function, which use the ESL signaling link. Estimation Method of the Multiplexing Mode The formula is as follows: BTS multiplexing mode = 64 (kbit/s) x 1024 (bit/kbit) x the valid load proportion on the Lapd/ 8 (bit/byte)/the bandwidth of the RSL The BTS multiplexing mode is an integral number rounded down from the preceding calculation result. For example, if the preceding calculation result is 2.6, the multiplexing mode is 2:1.
WARNING
If 16 kbit/s signaling links are used over the Abis interface, the Abis interface is not multiplexed. In this case, you do not need to calculate the multiplexing mode using the preceding formula because the multiplexing mode is permanently 1:1. In the preceding formula, l l
Issue 08 (2011-09-30)
64 indicates that the bandwidth of each Lapd link is 64 kbit/s. 1024 indicates that each kbit consists of 1024 bits.
l l l
8 indicates that each byte consists of 8 bits. The valid load proportion on the Lapd ranges from 70% to 75%. The RSL bandwidth equals to the number of average messages in a busy time divided by 3600. Where, Average messages in a busy time = (a x (Bytes of the messages in busy hours + Bytes of the messages during a handover + Bytes of the messages in a measurement report in busy hours) + b x Bytes of the messages in a location update in busy hours + c x Bytes of the short messages sent and received by an MS in busy hours + d x Average bytes of the messages in a paging in busy hours) x Number of subscribers supported by each TRX Bytes of the messages in busy hours = Number of originated calls in busy hours x Average bytes of the messages in an MS-originated call + Number of terminated calls in busy hours x Average bytes of the messages in an MS-terminated call Bytes of the messages in a handover = Number of times of the intra-BSC handover x Average bytes of the messages in an intra-BSC handover + Number of times of the inter-BSC handover x Average bytes of the messages in an inter-BSC handover Bytes of the messages in a measurement report in busy hours = (Number of originated calls in busy hours + Number of terminated calls in busy hours) x Average number of measurement reports of a call x Average bytes in a measurement report Bytes of the messages in a location update in busy hours = Number of location updates in busy hours x Average bytes of the messages in a location update Bytes of the short messages sent and received by an MS in busy hours = Number of short messages sent in busy hours x Average bytes of a short message sent by an MS + Number of short messages received in busy hours x Average bytes of a short message received by an MS Average bytes of the messages in a paging in busy hours = (Number of terminated calls in busy hours + Number of short messages received in busy hours + Average retransmissions for paging) x Average bytes of the messages in a paging Number of subscribers supported by each TRX = Traffic volume of the BSC/Traffic volume per MS in busy hours/Number of TRXs configured in a BSC Average number of measurement reports of a call = Average length of a call/0.5 The parameters a, b, c, and d are defined on the basis of the BSC6900 performance test. The following table lists the parameter proportions. Service Type a. Call (Without Paging) 100% b. Location Update C. Short Messages (Without Paging) 80% d. Paging
Proportion
60%
1%
The traffic volume and the number of carriers in a BSC can be calculated according to the actual situation. If the related data is not available, you can use the data contained in BSC6900 specifications to perform an alternative calculation according to the following formula: Number of subscribers supported by each TRX = Traffic volume of the BSC/Traffic volume of each user in a busy time/Number of carriers in the BSC
Where, the traffic volume of the BSC is 13,000 Erl and the carriers in the BSC is 2,048. The typical traffic model parameters are listed in the following table. Parameter Traffic volume per MS in busy hours Typical Value 1 0.02 Typical Value 2 0.02
2.61.3.3 16 kbit/s LAPD Signaling Link

When the function of the 16 kbit/s LAPD signaling link (OML and RSL) is enabled, each signaling link occupies only 16 kbit/s bandwidth at the physical layer, saving the transmission resources on the Abis interface. The multiplexing mode of the 16 kbit/s LAPD signaling link can be specified by Multiplexing Mode. The typical application scenarios are as follows: l l When the capacity of the BTS is low, such as O1 or O2, the 16 kbit/s LAPD signaling link can be used to minimize the transmission resources required over the Abis interface. The rent for the satellite transmission resources is very high. The 16 kbit/s LAPD signaling link can save bandwidth. Therefore, it can be used in satellite transmission mode.
The function of 16 kbit/s LAPD signaling link supports the following: l l l Each RSL timeslot and each OML timeslot occupy a 16 kbit/s sub-timeslot respectively. The 16 kbit/s signaling timeslot and the traffic timeslot can be configured in one 64 kbit/s timeslot on the Abis interface. The signaling timeslots of different BTSs can be distributed in one 64 kbit/s timeslot.
Disadvantages: The bandwidth of each signaling link is limited to 16 kbit/s; therefore, for the TRX with high traffic volume, data loss due to RSL congestion may occur. When the half-rate service is enabled in the TRX, the use of 16 kbit/s signaling service may result in insufficient bandwidth. Constraints: l l The BTS that uses the 16 kbit/s LAPD signaling link supports the tree networking mode; however, all the BTSs in the tree topology must use the 16 kbit/s LAPD signaling link. If the BTS that uses the 16 kbit/s LAPD signaling link supports the Abis bypass function, the OMLs and RSLs distributed (not multiplexed) on a 64 kbit/s timeslot must be distributed on one 64 kbit/s timeslot with the timeslot number unchanged in the E1 links of other cascaded BTSs. The 16 kbit/s LAPD signaling link cannot be configured in ring networking mode. When Flex Abis is enabled in the BTS, ESL signaling links are used by the Flex Abis. In the 16 kbit/s physical multiplexing mode, Flex Abis uses the same timeslots as the OML.
l l
Issue 08 (2011-09-30)
1031

Configuration Principles of the Star Networking Mode
l Any BTS in Time Division Multiplexing (TDM) transmission mode is directly connected to the EIUa or OIUa in the BSC through one or more E1 links without the need of other transit BTSs. Any BTS in transmission optimization mode is directly connected to the GEHUB in the BSC through one or more E1 links without the need of other transit BTSs. Any BTS in IP transmission mode is connected to a router or switch through an FE port without the transit of other BTSs.
l l
Configuration Principles of the Chain Networking Mode

The chain networking mode is classified into single-link cascading mode and multi-link cascading mode. l l Single-link cascading mode: used when the number of cascaded BTSs is smaller than 5 and the total number of TRXs is smaller than 15. Multi-link cascading mode: used when the number of cascaded BTSs is smaller than 5 and the total number of TRXs is greater than 15. A BTS can provide up to eight E1 ports; therefore, a maximum of eight primary and secondary links can be configured in multi-link cascading mode.
NOTE
l The 3012 and 3900 series base stations can be configured with a bypass board to bypass the E1 signals when the BTS is powered off, thus ensuring the reliability of the entire chain network. l If a BTS is at the lowest level in a chain network, the bypass board can perform the loopback test on the transmission link when the BTS is powered off. The result of the loopback test can be used for identifying the fault.
Configuration Principles of the Tree Networking Mode

l l l If the BTS directly connected to the EIUa/OIUa is in single-link cascading mode, a maximum of 15 TRXs can be configured on this root BTS. If the BTS directly connected to the EIUa/OIUa is in multi-link cascading mode, the maximum number of TRXs on this root BTS depends on the number of E1 timeslots. For the BTSs in transmission optimization mode, the upper-level BTS provides transparent transmission of timeslot signals for the lower-level BTSs.
Configuration Principles of the Ring Networking Mode

l l Compared with the other networking modes, the ring networking mode requires an extra port on the EIUa/OIUa or GEHUB for each ring. A maximum of five BTSs can be cascaded on a ring. Each BTS on the ring can have the bypass BTS and they are connected in tree networking mode. Along the connection from the bypass BTS on the ring to the BSC, the number of cascaded BTSs must not exceed five. According to the physical bearer, the BTSs in only TDM or HDLC transmission mode can form a ring network.
2.61.5 Parameters
This chapter describes the parameters related to networking modes.
For the meaning of each parameter, see Table 2-176. For the default value, value ranges, and MML commands of each parameter, see Table 2-177. Table 2-176 Parameter description (1) Parameter Description Timeslot multiplexing mode at the Abis interface of the BTS. The BTS supports two multiplexing modes: statistical multiplexing on a 64 kbit/s timeslot and physical multiplexing on a 16 kbit/s timeslot. The first mode is further classified into the following six types: 1:1, 2:1, 3:1, 4:1, 5:1, and 6:1. A BTS supports the following six types of timeslot objects: OML: operation and maintenance link of the BTS. Each BTS has only one OML. In the case of statistical multiplexing on a 64 kbit/s timeslot, the OML works at 64 kbit/s. In this case, the OML can be multiplexed only with the signaling links in the same cabinet group of the BTS. In the case of physical multiplexing on a 16 kbit/s timeslot, the OML works at 16 kbit/s. In this case, the OML uses a 16 kbit/s timeslot. ESL: extended signaling link of the BTS. If the BTS supports Flex Abis, in the case of statistical multiplexing on a 64 kbit/s timeslot, a 64 kbit/s timeslot needs to be assigned to the ESL. In this case, the ESL is always multiplexed with the OML in the 64 kbit/s timeslot. In the case of physical multiplexing on a 16 kbit/s timeslot, no timeslot is assigned to the ESL. In this case, the ESL shares the same timeslot with the OML. RSL: radio signaling layer link in each TRX. Each TRX has one RSL link. In the case of statistical multiplexing on a 64 kbit/s timeslot, the RSL link works at 64kbit/s. In this case, the RSL link can be multiplexed only with the signaling links in the same cabinet group of the BTS. In the case of physical multiplexing on a 16 kbit/s timeslot, the RSL link works at 16 kbit/s. In this case, the RSL link uses a 16 kbit/s timeslot exclusively. TCH: traffic channels in each TRX. The TCH works at 16 kbit/s. Idle: idle timeslots of the BTS. An idle timeslot works at 16 kbit/s. In the case of statistical multiplexing on a 64 kibt/s timeslot, the idle timeslots can be multiplexed only with the TCHs in the same cabinet group onto one 64 kbit/s timeslot. Semi: monitoring timeslots of the BTS. The monitoring timeslots work at 8 kbit/s, 16 kbit/ s, 32 kbit/s, and 64 kbit/s. The monitoring timeslots can be multiplexed only with semi-permanent links. A 2048 Mbit/s E1 contains thirty-two 64 kbit/s timeslots. Timeslot 0 is reserved for synchronization and cannot be assigned. Statistical multiplexing means that signaling timeslots are time-division multiplexed in an E1 timeslot, such as the OML and RSL timeslots or the RSL timeslots. For example, in the case of 4:1 multiplexing, one 64 kbit/s timeslot multiplexes one OML and three RSL links or four RSL links of the BTS. The 64 kbit/s timeslot that multiplexes the OML has a multiplexing ratio of up to 4:1 even if the multiplexing ratio exceeds 4:1. HDLC and IP BTS do not support this parameter.
Multiplexing Mode
Issue 08 (2011-09-30)
1033
Table 2-177 Parameter description (2) Parameter Defau lt Value GUI Value Range MODE1_1, MODE2_1, MODE3_1, MODE4_1, MODE5_1, MODE6_1, MODE16K Actual Value Range MODE1_1, MODE2_1, MODE3_1, MODE4_1, MODE5_1, MODE6_1, MODE16K Un it MML Com mand Impac t
Multiplexing Mode
MODE 4_1
No ne
ADD BTS (Optio nal)
BTS
2.61.6 Counters
None.
2.61.7 Glossary

l l l l BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.62 PBT
2.62.1 Introduction
2.62.1.1 Scope
This document describes the Power Boost Technology (PBT) feature and the dynamic PBT feature.

l l

This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the PBT feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.62.2 Overview
In GSM networks with wide coverage, the improvement of uplink and downlink transmit power is of great importance. The PBT is a power boost technology. In PBT mode, the two TRXs in the double-transceiver unit are used as one TRX. After modulation and DA conversion, one signal output is divided
into two RF signals. These two signals are amplified and then combined to form one signal. As the two signals are aligned in phase, the transmit power is amplified and the downlink signal strength is increased. In dynamic PBT mode, the timeslots corresponding to the two TRXs of a double-transceiver unit are set to PBT mode, and other timeslots are set to non-PBT mode. After the timeslots in PBT mode are released, they can be set to non-PBT mode. Dynamic PBT makes full use of idle timeslots and improves the signal strength in areas with weak coverage, such as at cell edges, indoors, or in cars. Based on actual network conditions, adjustments can be made to maintain the balance between capacity and coverage. Dynamic PBT is mainly applicable to concentric cells. In a concentric cell, when the downlink coverage in the overlaid subcell is restricted, continuous coverage is impossible. In this case, the TRX utilization is low if PBT is adopted.

2.62.3.1 PBT
In PBT mode, one signal is divided into two signals. The two signals are amplified and then combined to form one signal. After that, the two signals are superposed in the same phase and with the same frequency. Thus, the transmit power is almost doubled. Figure 2-271 shows the working principle of PBT. Figure 2-271 Working principle of PBT
The signal from TRX0 is divided into two signals by a divider. Then, the two signals enter RF units TX1 and TX2 respectively. After being amplified by the RF units, the two signals are combined by the combiner. Then, the combined RF signal is transmitted through the TX1 port. When PBT is enabled, the uplink coverage may be insufficient if the uplink signals are not amplified or the uplink receiver sensitivity is not improved. This may lead to imbalance between the uplink coverage and the downlink coverage. Thus, one of the following measures should be taken to improve the receive quality of uplink signals. l l
Issue 08 (2011-09-30)
Configuring Four-Way Receive Diversity Configuring a tower mounted amplifier (TMA)

The TMA is a low-noise amplifier module that is mounted on a tower. After receiving uplink signals from the antenna, the TMA amplifies the signals and then transmits them to the feeder. Thus, the receiver sensitivity of the BTS is improved and the UL coverage is expanded. In addition, when the TMA is used, the transmit power of an MS is reduced and the speech quality is improved.
2.62.3.2 Dynamic PBT

Dynamic PBT is timeslot-based. Normally, two TRXs in a double-transceiver unit work independently. If required, the two channels of the same timeslot number on the two TRXs work as a channel group. That is, the two channels can be converted into a channel group, and the channel group into two independent channels. This balances cost, capacity, and coverage. Dynamic PBT increases resource utilization and assists in expanding the coverage.
NOTE
When the double-transceiver unit works in dynamic PBT mode, the channels with the same timeslot number on the two TRXs of the same double-transceiver unit form a PBT channel group. The two channels must be TCHs (TCHF or TCHH). The channel with a smaller TRX number is the primary channel, and the other channel is the secondary channel. The primary channel and the secondary channel are the channels with the same timeslot number on one double-transceiver unit. BCCHs, SDCCHs, PDCHs, and CBCHs cannot form a channel group. They can only be used as independent channels.
During channel assignment, the BSC searches for the optimal channels. After dynamic PBT is enabled, the BSC determines whether the optimal channels can form a PBT channel group if the PBT channel group should be assigned. If a PBT channel group can be formed, the BSC blocks the secondary channel. Then, the BSC assigns the channel group to the call. If the optimal channels cannot form a channel group, the BSC regards the channels as independent channels. If the optimal channels can form a channel group but one of them is occupied by a call, the BSC attempts to hand over the call to another channel. After the channel turns idle, a channel group is formed and then assigned to the call. In dynamic PBT mode, the downlink-limited handover decision algorithm is added to determine whether the downlink signal strength is limited. If the downlink signal strength is limited and the serving cell supports dynamic PBT, the call is handed over to an available channel group. If one of the two channels with the same timeslot number on one double-transceiver unit is occupied by the call, the call on the other channel should be handed over to another idle channel. When the downlink signal strength is increased to a certain level, the PBT channel group is not required. The BSC divides the channel group into two independent channels and maintains the call on the primary channel. At the same time, the BSC releases the secondary channel to increase the capacity of the cell.
NOTE
After dynamic PBT is enabled, the BSC reserves most possible channel pairs that can form channel groups during the assignment of normal independent channels.
With dynamic PBT used in the overlaid subcell, the coverage of the overlaid subcell is expanded through the handover of calls in the vicinity of the edge to the overlaid subcell. This helps to balance the traffic in the overlaid subcell and that in the underlaid subcell and also increase the success rate of handover from the underlaid subcell to the overlaid subcell. Dynamic PBT is a software solution. That is, the hardware connections of the BTS in dynamic PBT are the same as those in PBT, and only the software needs to be upgraded.
2.62.4 Parameters
This chapter describes the parameters related to PBT. For the meaning of each parameter, see Table 2-178. For the default value, value ranges, and MML commands of each parameter, see Table 2-179. Table 2-178 Parameter description (1) Parameter Description RF send mode of the TRX. The BTS3006C and BTS3002E do not support Wide Band Combining, Power Booster Technology, DPBT, or Transmitter Independent or Combining. The DBS3900 GSM GRRU does not support Wide Band Combining, Transmitter Independent or Combining, Power Booster Technology, or DPBT. The BTS3900 GSM and BTS3900A GSM do not support Transmitter Independent or Wide Band Combining.
Send Mode
Issue 08 (2011-09-30)
1038
Table 2-179 Parameter description (2) Param eter Defa ult Valu e GUI Value Range Actual Value Range Unit MML Comman d Impact
Send Mode
NON E
NOCOMB (No Combinatio n), PBT (PBT), WBANDC OMB (Wideband Combinatio n), DIVERSIT Y(Transmit Diversity), DDIVERSI TY (Dynamic Transmit Diversity), DPBT (DPBT), DTIC (Transmit Independen cy or Combinatio n), NONE (none)
NOCOMB, PBT, WBANDCO MB, DIVERSITY, DDIVERSIT Y, DPBT, DTIC, NONE None
SET GTRXDE V (Optional)
TRX
2.62.5 Counters
None.
2.62.6 Glossary

l l l
Issue 08 (2011-09-30)
BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide
l l
BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.63 PICO Automatic Configuration and Planning

2.63.1 Introduction
2.63.1.1 Scope
This document describes the automatic planning of frequencies, CGI and RAI, neighboring cells, and BSIC of the PICO BTS.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the PICO Automatic Configuration and Planning feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-04-30)
2.63.2 Overview
The PICO BTS is a type of BTS with a small footprint and low power consumption and supplements the coverage of macro BTSs and micro BTSs in many ways. For example, it can be placed in a blind spot under an outdoor BTS to fulfill the coverage; it can aid a compact BTS for load sharing and in special coverage scenarios (for example, indoor coverage); it can also be interpolated with the existing macro BTSs. Typically, the PICO BTS is used to provide indoor coverage or coverage within small enterprises. The PICO BTS communicates with the BSC through ADSL or Ethernet connections. The PICO BTS supports the plug and play (PnP) feature. Therefore, you only need to connect the transmission cables and the power supply cable to the PICO BTS. This simplifies the network planning and saves the labor resources. The PnP feature of the PICO BTS involves automatic configuration of the device data, service data, and some of the transmission parameters.
NOTE
l Device data refers to data configurations related to hardware, for example, board configurations and parameter configurations related to boards. l Service data refers to data configurations related to services. Here, it mainly involves the parameters related to frequency allocation.
Before installing the PICO BTS, you need to configure some of the transmission parameters, for example, the mapping between the equipment serial number (ESN) and the IP address of the PICO BTS on the BSC side. Then, install the PICO BTS at the required place. When the PICO BTS is powered on, it automatically establishes the connection to the BSC, and completes the configuration of the device data and service data under the control of the BSC and M2000. After that, the PICO BTS can provide services directly without further configuration. That is, you need not configure the frequencies or neighboring cells. The PICO Automatic Configuration and Planning feature facilitates quick deployment and flexible adjustment of the network of the operators and reduces the related configuration workload of engineers. To achieve PICO Automatic Configuration and Planning, you need to complete the preconfiguration on the BSC where the PICO BTS belongs. Most of the device data and service data can be preconfigured automatically according to the template on the BSC maintenance console. The frequencies, Base Station Identity Code (BSIC), Cell Global Identity (CGI),
Routing Area Identification (RAI), neighboring relations, and other data related to frequency planning, however, is configured in the PICO automatic configuration and planning stage. After configuring the data of the PICO BTS, you can reset the PICO BTS to start PICO Automatic Configuration and Planning. The system scans the radio resources in the network, automatically configures cell parameters, and then starts operating. PICO Automatic Configuration and Planning requires the cooperation of the BTS, BSC, and M2000. l l l The BTS measures the radio electromagnetic environment and collects the relevant statistics. The M2000 analyzes the data reported by the BTS and configures the frequencies, CGI, RAI, and neighboring relations automatically. The BSC transfers the data between the BTS and the M2000.
Figure 2-272 shows the PICO Automatic Configuration and Planning procedures.
Issue 08 (2011-09-30)
1042
Figure 2-272 PICO Automatic Configuration and Planning procedures
1.
Sequential BTS initialization The PICO BTSs under automatic configuration and planning must be initialized in sequence in the same BSC.
2.
Uplink and downlink frequency scanning The PICO BTS reports its capability, including the supported frequency band, to the M2000. The BSC reports the mobile country code (MCC) and mobile network code (MNC) to the M2000. According to the information reported by the BTS and BSC, the M2000 determines the frequency bands that should be scanned by the BTS. The BTS measures the uplink and downlink receive levels on the available frequencies in the specified frequency band. Then, it informs the M2000 of the scanned frequencies and the measured uplink and downlink receive levels at these frequencies.
Issue 08 (2011-09-30)
1043
3.
Automatic frequency planning According to the downlink frequency scan result reported by the BTS, the M2000 automatically configures the BCCH frequency and TCH frequencies for the PICO BTS.
4.
Automatic CGI and RAI planning The M2000 matches the CGI and RAI of the BCCH frequency in the downlink frequency scan result reported by the BTS with the LAI of the BSC. Then, the M2000 sorts the receive levels and determines the CGIs and RAI of the cells under the PICO BTS based on the sorted receive levels.
5.
Automatic neighboring cell planning According to the downlink frequency scan result reported by the BTS, the M2000 automatically configures the bidirectional neighboring relations between the PICO BTS and a neighboring BTS.
6.
Automatic BSIC planning According to the downlink frequency scan result reported by the BTS, the M2000 automatically configures the BSIC of the PICO BTS.

2.63.3.1 Automatic Frequency Planning
?.1. Overview
The BTS scans the frequencies in the supported frequency band. Then, the M2000 evaluates the interference on each frequency according to the sorting of the uplink and downlink receive levels. At the same time, the M2000 considers the neighboring relations between adjacent BTSs and selects a frequency with the minimum interference to be used by the BTS. To prevent adjacent BTSs from contending for the same frequency during the frequency planning, the M2000 initializes the BTSs under the BSC one by one.
?.2. Algorithm
When BTS Configuration Mode is set to Auto Plan Mode and Freq. and BSIC Optimize Switch is set to ON on the BSC side, the automatic frequency planning of the PICO BTS is enabled. After the PICO BTS scans the uplink and downlink frequencies, it informs the BSC and M2000 of the scanned frequencies and the measured uplink and downlink receive levels at these frequencies. Then, the M2000 performs the automatic frequency planning of the PICO BTS based on the information reported by the BTS. Figure 2-273 shows the procedure for automatic frequency planning of the PICO BTS.
Issue 08 (2011-09-30)
1044
Figure 2-273 Procedure for automatic frequency planning
1.
To prevent neighboring BTSs from selecting adjacent frequencies, the M2000 obtains the uplink and downlink receive levels by adding the adjacent-channel interference to the uplink and downlink receive levels reported by the BTS. Based on the obtained receive levels, the M2000 calculates the interference priority of each frequency. If a frequency has a low interference priority, it causes low interference to other frequencies. Of all the available BCCH frequencies, the M2000 selects the frequency with the lowest interference priority and configures it as the BCCH frequency of the current cell. If a BTS is configured with two transceivers, the frequency that has the lowest interference priority and is not adjacent to the BCCH frequency is configured as the TCH frequency.
2.
3.
In actual application, two PICO BTSs may have overlapping areas but cannot detect each other. In this case, their cells cannot be configured as neighboring cells of each other automatically. The automatic frequency planning, however, is based on the neighboring relations and measurement result. In this case, there may be two consequences: handover or cell reselection is impossible between these two PICO BTSs; the same frequency may be allocated to these two PICO BTSs, leading to co-channel interference in the overlapping area. To prevent this problem, you need to add the neighboring relations in the Adjacent Pico table on the M2000. During the automatic frequency planning, the M2000 searches the table and prevents the simultaneous initialization of two adjacent PICO BTSs to avoid allocating the same frequency to these PICO BTSs. Thus, co-channel interference can be prevented. During the automatic neighboring cell planning, the M2000 forcibly defines the bidirectional handover between cells of two adjacent PICO BTSs. Thus, the cells of the two PICO BTSs can be automatically configured as the neighboring cells of each other, regardless of whether the two PICO BTSs can detect each other.
Issue 08 (2011-09-30)
1045
If the adjacent PICO data is not configured, the automatic planning of frequencies and neighboring relations is not affected. The performance of the automatic planning, however, can be improved if you configure the information about the adjacent PICO BTSs. Table 2-180 Adjacent Pico BSC Name BTS ID BTS Name Adjacent BSC Name Adjacent BTS ID Adjacent BTS Name
2.63.3.2 Automatic CGI and RAI Planning

?.1. Overview
The PICO BTS scans the available frequencies and receive levels and reports them to the M2000. The M2000 matches the CGIs and RAIs of the BCCH frequencies contained in the information reported by the BTS with the LAIs available in the BSC. It then selects the CGI and RAI for the PICO BTS based on the receive levels.
?.2. Algorithm
The automatic CGI and RAI planning is initiated when CGI and RAC Plan Switch is set to ON on the BSC. Figure 2-274 shows the procedure for automatic CGI and RAI planning. Figure 2-274 Procedure for automatic CGI and RAI planning
Issue 08 (2011-09-30)
1046
1.
The M2000 analyzes the LAIs of all neighboring cells detected by the PICO BTS, filters out the LAIs of the cells that do not belong to the same BSC as the PICO BTS, and then selects the LAI of the cell with the highest downlink receive level as the LAI of the cell of the PICO BTS. Then, the PICO BTS sequentially assigns the available CIs defined in the CGI Resource table to its cell. To implement automatic CGI and RAI planning, you need to configure the CGI Resource table in advance on the M2000. In the CGI Resource table, you need to define a CI segment for each LAC under the BSC. These CIs are then allocated to the cells in sequence. Table 2-181 CGI Resource BSC Name MCC MNC LAI Start CI End CI
2.
3.
The RAC of the neighboring cell with the highest downlink receive level is selected as the RAC of the cell of the PICO BTS.
The CGI of a PICO cell is identified by the combination of LAI and CI, and the RAI of a PICO cell is identified by the combination of LAI and RAC. When the LAI and CI are determined, the CGI allocation is complete. When the LAI and RAC are determined, the RAI allocation is complete.
2.63.3.3 Automatic Neighboring Cell Planning

?.1. Overview
The PICO BTS scans the available uplink and downlink frequencies and receive levels and reports them to the M2000. The M2000 selects a suitable cell as the neighboring cell of the cell of the PICO BTS according to the scanned downlink receive level.
?.2. Algorithm
The automatic neighboring cell planning is initiated when Neighbor Cell Plan Switch is set to ON on the BSC. Figure 2-275 shows the procedure for automatic neighboring cell planning.
Issue 08 (2011-09-30)
1047
Figure 2-275 Procedure for automatic neighboring cell planning
1.
Assume that there are M adjacent cells defined in the Adjacent Pico table. The M adjacent cells are added to the neighboring cell list of the PICO BTS. Then, the top N cells with the highest downlink receive levels on the BCCH frequency are added to the neighboring cell list of the cell of the PICO BTS. Here, the sum of N and M should be less than or equal to 32. The neighboring relations are bidirectional. That is, when a cell of the PICO BTS (cell A) is configured with a neighboring cell (cell B) automatically, cell A is also configured as the neighboring cell of cell B. Before the configuration of the bidirectional neighboring relations, the BSIC is allocated to the cell of the PICO BTS according to the automatic BSIC planning algorithm.
2.
If the cell of the PICO BTS and the neighboring cells are controlled by different M2000 devices or network management devices from different manufacturers, you need to configure the neighboring relations manually.
The PICO BTS scans the uplink and downlink frequencies only in a single frequency band. Thus, the neighboring cells must be on the same frequency band as the cell of the PICO BTS. For example, if the PICO BTS supports the GSM900 frequency band, it cannot plan a cell on the GSM1800 frequency band as the neighboring cell automatically.
2.63.3.4 Automatic BSIC Planning

?.1. Overview
After the PICO BTS completes automatic planning of the frequencies, CGI, RAI, and neighboring relations, it creates its own neighboring cell list. To create the bidirectional handover relations, the PICO BTS also adds itself to the neighboring cell lists of its neighboring cells. Consequently, the data in the neighboring cell list, BA1 table, and BA2 table of the involved neighboring cells is changed. The M2000 allocates a suitable BSIC to the cell of the PICO BTS based on the automatic BSIC planning algorithm, the BCCH frequency of the cell, and the BCCH frequencies and BSICs of the neighboring cells. The automatic BSIC planning is based on the result of the automatic planning of neighboring cells, frequencies, and CGI and RAI.
?.2. Algorithm
The automatic BSIC planning is initiated when Freq. and BSIC Optimize Switch is set to ON on the BSC. Before automatic BSIC planning, you need to configure the BSIC Resource data in advance. The BSIC Resource data defines the BSIC range for each BSC. Table 2-182 BSIC Resource MCC MNC BSC Name Start NCC End NCC Start BCC End BCC
When a PICO BTS is under automatic BSIC planning, the M2000 determines the BSIC range according to the MCC and MNC of the BSC that controls the PICO BTS. Then, the M2000 selects a suitable BSIC for the PICO BTS, wherein the selected BSIC must be unique to the PICO BTS.

The following parameters should be configured on the M2000 before the PICO BTS starts the automatic frequency planning: l Operator Frequency data Specifies the frequencies that a telecom operator can allocate to BTSs. BTSs select proper BCCH frequencies and TCH frequencies from these frequencies. The operator frequency data consists of the MCC, the MNC, and the start frequency and end frequency of a frequency band.
The operator frequency data should be preconfigured. l l BSIC data Specifies the ranges of MCCs and NCCs that a telecom operator allocates to BSCs. CGI resource data Specifies the range of CGIs that are available in all BSCs in the MSC area. This helps the system to allocate CGIs to a PICO BTS that is under the automatic frequency planning. The CGIs configured on the M2000 are not delivered to the MSC and they are applicable only to the automatic frequency planning of the PICO BTS. To ensure that the CGIs obtained through the automatic frequency planning of the PICO BTS are valid, predefine the value range of the CGIs corresponding to each LAC at the MSC. The value range of the CGIs predefined at the MSC must include the value range of the CGIs configured on the M2000. l Adjacent Pico Specifies the information about the adjacent PICO BTSs. If the data about the adjacent PICO is not configured, the automatic planning of frequencies and neighboring relations is not affected. The performance of the automatic planning, however, can be improved if you configure the data about the neighboring PICO BTSs. Therefore, you are advised to configure it in advance. The following parameters should be configured on the LMT before the PICO BTS starts the automatic frequency planning: l Configuration Mode To enable the automatic frequency planning of a PICO BTS, set this parameter to Auto Plan Mode. Otherwise, set it to Normal Mode. The default setting is Normal Mode. l CGI and RAC Plan Switch To enable the automatic CGI and RAC planning of a BTS, set this parameter to ON. Otherwise, set it to OFF. The default setting is OFF. l Freq. and BSIC Optimize Switch To enable the automatic frequency and BSIC planning of a BTS, set this parameter to ON. Otherwise, set it to OFF. The default setting is OFF. l Neighbor Cell Plan Switch To enable the automatic neighboring cell planning of a BTS, set this parameter to ON. Otherwise, set it to OFF. The default setting is OFF. l Maximum TRX Number This parameter specifies the maximum number of TRXs supporting the automatic frequency planning in a PICO BTS. Currently, the maximum value is 2. The default value is 1.
2.63.5 Parameters
This chapter describes the parameters related to PICO Automatic Configuration and Planning.For the meaning of each parameter, see Table 2-183. For the default value, value ranges, and MML commands of each parameter, see Table 2-184.
Issue 08 (2011-09-30)
1050
Table 2-183 Parameter description (1) Parameter Description BTS configuration modes include auto plan mode and normal mode. In auto plan mode, the user can enable the auto planning algorithms and auto optimization algorithms according to the BTS type. In normal mode, the auto planning algorithms and auto optimization algorithms are disabled. Whether to generate the frequency and BSIC by using the automatic optimization algorithm. When this switch is on, it indicates that the data of the adjacent cell is generated automatically. When this switch is off, it indicates that these data must be configured manually. If the parameter is set to 1, it indicates that the CGI and RAC data is generated through automatic planning. If the parameter is set to 0, it indicates that the data needs to be manually entered. Maximum number of TRXs that can be configured for one cell. For the BTS3900B GSM, when the "Frequency and BSIC Plan Switch" is ON, the "Maximum TRX Number" (one or two, one by default) can be selected. For the BTS3900E GSM, when the "Capacity and Coverage Optimize Switch" is OFF, the "Maximum TRX Number" (one or two, one by default) can be selected.
BTS Configuration Mode Freq. and BSIC Optimize Switch
Neighbor Cell Plan Switch
Maximum TRX Number
Table 2-184 Parameter description (2) Paramete r Default Value GUI Value Range AUTO (AUTOPL AN), NORMAL (NORMA L) Actual Value Range Unit MML Comman d SET BTSAUT OPLANC FG (Mandator y) SET BTSAUT OPLANC FG (Optional) Impact
BTS Configurat ion Mode Freq. and BSIC Optimize Switch
None
AUTO, NORMAL
None
BTS
None
OFF (OFF), ON (ON)
OFF, ON
None
Cell
Issue 08 (2011-09-30)
1051
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET BTSAUT OPLANC FG (Optional) SET BTSAUT OPLANC FG (Optional) ADD BTSAUT OPLAN (Mandator y) SET BTSAUT OPLANC FG (Optional)
Impact
Neighbor Cell Plan Switch
None
OFF (OFF), ON (ON)
OFF, ON
None
Cell
None
OFF (OFF), ON (ON)
OFF, ON
None
Cell
Maximum TRX Number
1~2
1~2
None
Cell
The following parameters are configured on the M2000: l l l l Operator Frequency data BSIC data CGI resource data Adjacent Pico
2.63.6 Counters
None.
2.63.7 Glossary

l l l
Issue 08 (2011-09-30)
BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference
2.64 Power Control

2.64.1 Introduction
2.64.1.1 Scope
This document describes the functions of and technologies regarding the power control feature of Huawei GBSS, including Huawei II power control algorithm, Huawei III power control algorithm, Single Antenna Interference Cancellation (SAIC) power control optimization, and active power control.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Power Control feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows: l l l l 04 (2010-09-08) 03 (2010-02-10) 02 (2009-09-30) 01 (2009-06-30)
04 (2010-09-08)
This is the fourth commercial release of GBSS9.0.
Compared with issue 03 (2010-02-10), issue 04 (2010-09-08) incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description Information related to FH gain in Huawei III Power Control algorithm is deleted. The information of the document is optimized. Parameter Change None.
None.
03 (2010-02-10)
This is the third commercial release of GBSS9.0. Compared with issue 02 (2009-09-30) of GBSS9.0, issue 03 (2010-01-20) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description A description of Optimized Huawei III Power Control Algorithm is added. Parameter Change The parameters added are as follows: l Power Control Switch l III Power Control Optimized Enable l III UL Filter Adjust Factor l III DL Filter Adjust Factor l III UL RexLev Protect Factor l III DL RexLev Protect Factor l III UL RexQual Protect Factor l III DL RexQual Protect Factor Editorial change None. None.
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change
Issue 08 (2011-09-30)
1054
01 (2009-06-30)
2.64.2 Overview
Power Control is used to control the transmit power of the MS and BTS during a connection. The desired QoS, however, must be ensured when the transmit power is decreased. The benefits of Power Control are as follows: l Decrease in interference After Power Control is enabled, signals received by the MS and BTS remains stable without compromising the signal quality, and C/I is increased. l Decrease in power consumption When the transit power of the MS and BTS decreases, the maximum standby and speech time of the MS will increase, and less electrical power will be required by the BTS. If the BTS is powered by storage batteries, frequent recharging is not required.

2.64.3.1 Principles
Power Control aims to improve the QoS over the Um interface. After Power Control is enabled, the transmit power of the MS and BTS is adjusted according to the comprehensive decision made by the BSS. The decision on power adjustment is made on the basis of the specified thresholds, receive level and receive quality on uplink and downlink reported by the BTS. Based on the receive level and receive quality in the measurement report, the BSS determines the transmit power of the MS and BTS through the power control algorithm. Power Control is performed to achieve the desired QoS with minimum possible transmit power. The reduction in the transmit power of the MS or BTS leads to the decrease in adjacent channel interference and power consumption. There are two types of Power Control: l Uplink Power Control Uplink Power Control is used to adjust the transmit power of the MS, so that the receive signal strength of the BTS remains stable, and adjacent channel interference and MS power consumption are decreased.
Downlink Power Control Downlink Power Control is used to adjust the transmit power of the BTS, so that the receive signal strength of the MS remains stable, and adjacent channel interference and BTS power consumption are decreased.
Uplink Power Control and downlink Power Control adopt the same algorithms, although different parameters are involved. Unless otherwise specified, the algorithms described in this document apply to both uplink Power Control and downlink Power Control. Figure 2-276 shows the procedure of Power Control. Figure 2-276 Procedure of Power Control
As shown in Figure 2-276, the procedure of Power Control is as follows: 1. 2. The MS/BTS measures the receive level and receive quality and then forwards the information to the BTS/BSC through measurement reports (MRs). The BSS calculates the suitable transmit power of the MS or BTS using the algorithms and then decides whether Power Control should be performed. If yes, the BSS sends the decision to the MS/BTS through an MS Power Control/BS Power Control message. The MS/BTS transmits signals at the power specified in the message.
3.
?.1. Measurement of Receive Level and Receive Quality

The MS/BTS measures the receive level and receive quality and then reports the information to the BTS/BSC through MRs. The MRs can be processed at the BSC or BTS, which is specified by MR.Preprocessing. If MR.Preprocessing is set to Yes, the MRs are processed at the BTS. The contents and processing period of MRs from the BTS to the BSC are specified by Transfer Original MR, Transfer BS/MS Power Class, and Sent Freq.of preprocessed MR. Therefore, the signaling flow over the Abis interface and the load of the BSC can be controlled.
If the BTS sends the original MRs, the BSC performs MR interpolation and filtering. If the BTS sends the preprocessed MRs, the BTS performs Power Control decision. The original MRs trigger Power Control at the BSC, whereas the preprocessed MRs trigger Power Control at the BTS. The Power Control procedure at the BTS is similar to that at the BSC. Here, the Power Control performed by the BSC is taken as an example: The BSC processes the information in the MRs according to the Measurement Report Type. The BSC obtains the measurement results associated with the serving cell and neighboring cells from the MRs sent by the BTS. The measurement values in the MRs are classified into FULL SET and SUB SET. FULL SET indicates the measurement value when signals are transmitted continuously. SUB SET indicates the measurement value when discontinuous transmission (DTX) is adopted. The MRs from the MS and BTS indicate whether the DTX is adopted. For details on the DTX, see the 2.25.3.1 DTX feature. If the measurement report indicates that DTX is adopted, then the measurement value of SUB SET is selected; otherwise, the measurement value of FULL SET is selected.
?.2. Power Control Algorithms

Huawei algorithms for Power Control consist of Huawei II Power Control algorithm, Huawei III Power Control algorithm, and optimized Huawei III Power Control algorithm. These algorithms which differ in the purpose of power control and the process of decision-making. The process of the optimized Huawei III Power Control algorithm is the same as the process of Huawei III Power Control algorithm. Huawei II Power Control algorithm involves the following aspects: l l l l l l l MR compensation Prediction filtering Dual-threshold Power Control algorithm Variable Power Control step Adaptive Power Control Adjustment of the upper threshold of signal strength in the case of bad signal quality Separate configuration of the adjustment step for uplink and downlink Power Control
Compared with Huawei II Power Control algorithm, Huawei III Power Control algorithm has the following new functions: l l l l l Exponential filtering and slide-window filtering Interpolation optimization Comprehensive decision based on receive level and receive quality Different thresholds for different speech version types Consideration of impact of frequency hopping (FH) gain on receive quality
?.3. Power Control Procedure

The uplink power control procedure is different from the downlink power control procedure. The downlink power control procedure is that when the BTS receives the BS POWER CONTROL message sent by the BSC, the BTS transmits signals at the power specified in the message.
The uplink power control procedure involves three SACCH MR periods. In the first period, the BTS sends the MS a power control command message. In the second period, the MS performs the power adjustment. In the third period, the MS notifies the BTS of the adjusted power. Figure 2-277 shows the procedure of Power Control. Figure 2-277 Uplink power control procedure
During the three SACCH MR periods that are defined by the parameter PC Interval, the procedure of Power Control is as follows:
NOTE
The default value of PC Interval is 3. The value indicates the following three MR periods. You are advised to accept the default value, because a value smaller than 3 leads to excessively frequent performance of Power Control, and a value greater than 3 leads to delayed performance of Power Control.
1.
The first SACCH MR period The BTS sends a power and TA adjustment command in the SACCH header. On receiving the command, the MS starts to perform Power Control in the second MR period.
2.
The second SACCH MR period The MS adjusts its transmit power as follows: l If the power is adjusted in steps of 16 dB, one MR period (104 frames or 480 ms) is required for the power adjustment process. l If the power is adjusted in steps of 32 dB, two MR periods are required for the power adjustment process.
NOTE
The maximum rate for an MS to adjust its power is 2 dB every 13 frames or 60 ms.
3.
The third SACCH MR period The current transmit power, which is the power level of the last burst in the previous SACCH MR period, is saved and is reported to the BTS in the next MR on the uplink SACCH.
Issue 08 (2011-09-30)
1058
2.64.3.2 Huawei II Power Control Algorithm

Huawei II Power Control algorithm involves MR compensation, prediction filtering, and calculation of adjustment step based on receive level and receive quality, as shown in Figure 2-278. Figure 2-278 Procedure of Huawei II Power Control algorithm
1.
MR Processing The MR processing in Huawei II Power Control algorithm involves the following stages: (1) MR interpolation If the latest MR received by the BSC is not in continuous relation with those buffered in the queue and the number of lost MRs does not exceed Allowed MR Number Lost, the MR interpolation is performed. The value of MS transmit power (MSPwr) missing from the MRs is not interpolated. In such a case, MR filtering is not affected, and Power Control procedure proceeds normally. (2) MR compensation While determining whether to perform Power Control, the BSC performs weighted filtering on the receive level and receive quality in certain history MRs. The MRs may be obtained by the BTS or MS at varying transmit power. To ensure the accuracy of the receive level and receive quality for filtering, their values in the history MRs that are obtained at a transmit power different from the current power must be compensated. If the currently interpolated MRs and the compensated MRs are filtered
Issue 08 (2011-09-30)
1059
together, the decision on Power Control can be more effective. MR compensation is performed when the parameter MR. Compensation Allowed is set to Yes. The MR compensation is calculated as follows: l If the power level in the MR from the MS or BTS is higher than that in the previous MR, it indicates that the power is decreased. In such a case, the BSS subtracts the decreased power of the MS or BTS from the uplink or downlink receive level in all the MRs (decreased power level x 2 dBm). l If the power level in the MR from the MS or BTS is lower than that in the previous MR, it indicates that the power is increased. In such a case, the BSS adds the increased power of the MS or BTS to the uplink or downlink receive level in all the MRs (increased power level x 2 dBm).
NOTE
The MR compensation applies only to the receive level, but not to the receive quality.
(3) Discarding of MRs in the initial phase of connection In the initial phase of connection, the BSC does not perform Power Control due to the huge fluctuation of data in the MRs. Huawei II Power Control algorithm discards the first four MRs, which are not involved in MR filtering. (4) MR filtering The decision on Power Control is made on the basis of the average filtering value in the history MRs, which is the reference value of the current receive level. The number of MRs involved in the filtering process is specified by Filter Length for UL RX_LEV/Filter Length for DL RX_LEV and Filter Length for UL Qual./Filter Length for DL Qual.. Due to the interval between the Power Control decision and power adjustment, the history MRs cannot accurately indicate the radio conditions or provide receive level and receive quality in real time when power adjustment is performed. Therefore, the prediction filtering is adopted to minimize the impact of the delay on power adjustment. In the prediction filtering of MR, the BSC performs weighted filtering on some sampling MRs. Generally, the interval between Power Control decision and power adjustment is three MRs. Prediction filtering can ensure the accuracy by predicting the subsequent zero to three MRs. The number of sampling MRs is specified by UL MR. Number Predicted/DL MR. Number Predicted. After filtering the predicted MRs and the interpolated and compensated MRs (or interpolated but no compensated MRs), the BSC makes a decision on Power Control. After the prediction filtering function is enabled, the MRs, on which Power Control decision is based, can accurately indicate the radio conditions when power adjustment is performed. Thus, the delay in power adjustment can be minimized.
NOTE
The prediction filtering applies only to the receive level. Mean-value filtering is applied when Filter Length for UL RX_LEV/Filter Length for DL RX_LEV is less than 5 or UL MR. Number Predicted/DL MR. Number Predicted is 0.
2.
Power Control Decision The Power Control decision in Huawei II Power Control algorithm involves the following stages: (1) Calculation of power adjustment step based on receive level (RxLev) l When RxLev < UL RX_LEV Lower Threshold/DL RX_LEV Lower Threshold, the power should be increased. The formula is as follows:
Issue 08 (2011-09-30)
1060
Power adjustment step = min{|(UL RX_LEV Upper Threshold/DL RX_LEV Upper Threshold + UL RX_LEV Lower Threshold/DL RX_LEV Lower Threshold) 2 - RxLev|, MAX Up Adj. PC Value by RX_LEV} l When RxLev > UL RX_LEV Upper Threshold/DL RX_LEV Upper Threshold, the power should be decreased. The poorer the receive quality, the more sensitive the level adjustment. Therefore, the BSS adjusts the receive quality when decreasing the power based on RxLev. In Huawei II Power Control algorithm, receive quality is classified into three quality zones (0, 1-2, 3). The maximum step of power adjustment on downlink is different for the three quality zones. The step is specified by MAX Down Adj.Value Qual.Zone 0/MAX Down Adj.Value Qual.Zone 1/MAX Down Adj.Value Qual.Zone 2. The adjustment step is calculated according to receive quality only when the power is decreased according to RxLev. The formula is as follows: Power adjustment step = min{|(UL RX_LEV Upper Threshold/DL RX_LEV Upper Threshold + UL RX_LEV Lower Threshold/DL RX_LEV Lower Threshold) 2 - RxLev|, MAX Down Adj.Value Qual.Zone 0/MAX Down Adj.Value Qual.Zone 1/MAX Down Adj.Value Qual.Zone 2}
NOTE
The symbol | indicates absolute value.
(2) Calculation of power adjustment step based on receive quality (RxQual) l When RxQual UL Qual. Lower Threshold/DL Qual. Lower Threshold, the power should be increased. The adjustment step is specified by MAX Up Adj. PC Value by Qual.. The power can be increased only when RxLev + MAX Up Adj. PC Value by Qual. UL RX_LEV Upper Threshold/DL RX_LEV Upper Threshold. The value of UL Qual. Bad UpLEVDiff/DL Qual. Bad UpLEVDiff must be increased when RxQual UL Qual. Bad Trig Threshold/DL Qual. Bad Trig Threshold, so as to ensure the increase in power when RxQual is poor. l When RxQual < UL Qual. Upper Threshold/DL Qual. Upper Threshold, the power should be decreased. The adjustment step is specified by MAX Down Adj. PC Value by Qual.. The power can be decreased only when RxLev - MAX Down Adj. PC Value by Qual. UL RX_LEV Lower Threshold/DL RX_LEV Lower Threshold. (3) Calculation of power adjustment step based on both RxLev and RxQual To ensure the stability of power adjustment, both AdjStep_Lev and AdjStep_Qual should be taken into consideration. For details, see Table 2-185. Table 2-185 Comprehensive decision on power adjustment RxQual RxLev Decrease AdjStep_Lev Decrease AdjStep_Qual Decrease Max (AdjStep_lev, AdjStep_Qual) Increase AdjStep_Lev Increase AdjStep_Lev No adjustment Decrease AdjStep_Qual
Issue 08 (2011-09-30)
1061
RxQual
RxLev Decrease AdjStep_Lev Increase AdjStep_Lev Increase Max (AdjStep_lev, AdjStep_Qual) Increase AdjStep_Lev No adjustment Increase AdjStep_Qual No adjustment
Increase AdjStep_Qual No adjustment
No adjustment
Decrease AdjStep_Lev
Corresponding to Table 2-185, Figure 2-279 shows the power adjustment. Figure 2-279 Power adjustment
NOTE
The procedure of Power Control for AMR calls is the same as that for non-AMR calls; however, different parameters are involved. For details, see 2.9.3.4 AMR Power Control of the AMR feature.
2.64.3.3 Huawei III Power Control Algorithm

Huawei III Power Control algorithm involves MR interpolation, MR filtering, and calculation of adjustment step, as shown in Figure 2-280.
Figure 2-280 Procedure of Huawei III Power Control algorithm
1.
MR Processing When Huawei III Power Control algorithm is applied, a fixed number of MRs are discarded during the initial access of the MS to the network to prevent the impact of inaccurate MRs on the algorithm. The number of discarded MRs is specified by SdMrCutNum and TchMrCutNum.
NOTE
If active Power Control is enabled, the MRs are not discarded.
The MR processing in Huawei III Power Control algorithm involves the following stages: (1) MR interpolation l Interpolation is applied to the values missing from the MRs. The missing level value is replaced with the value in the last MR. The missing quality value is always replaced with 7. l The value of MS/BTS transmit power missing from the MRs is not interpolated. In such a case, MR filtering is not affected, and Power Control procedure proceeds normally. l The interpolation is not performed in the case that the measurement results are lost. l If the number of continuously lost MRs is greater than the value of MRMissNumber, the BSC stops Power Control procedure. The procedure will resume when a new MR is received. (2) MR filtering
MR filtering in Huawei III Power Control algorithm involves exponential filtering and slide-window filtering, instead of mean-value filtering in Huawei II Power Control algorithm. In the process of calculation, receive quality is converted into C/I. In MR filtering, exponential filtering and slide-window filtering are performed on C/I and receive level in succession. The measurement value obtained through the filtering is used to decide whether Power Control is performed. In Huawei III Power Control algorithm, the filtering period is specified by the parameters UL(DL)RexLevExponentFilterLen, UL(DL) RexQualExponentFilterLen, UL(DL)RexLevSlideWindow, and UL(DL) RexQualSlideWindow.
NOTE
In this document, the UL(DL) means two separate parameter prefixes. For example, UL(DL) RexLevExponentFilterLen means ULRexLevExponentFilterLen and DLRexLevExponentFilterLen.
2.
Power Control Decision Power Control decision in Huawei III Power Control algorithm involves the following stages: First, the gain of the channels on the Um interface is obtained through calculation. Then, the adjustment step is calculated on the basis of the gain, RxLev, and RxQual after the filtering. The calculated step will be checked to determine whether it exceeds the maximum step allowed. If it is within the specified range, Power Control is performed. (1) Decision on whether Power Control should be performed When UL(DL)RexLevHighThred RxLev UL(DL)RexLevLowThred, and UL**RexQualHighThred Rex or DL**RexQualHighThred RxQual UL**RexQualLowThred or DL**RexQualLowThred, Power Control is not required. Otherwise, the calculation of the adjustment step starts.
NOTE
In Huawei III Power Control algorithm, different quality level thresholds are set for different speech coding schemes. The symbol ** represents Full-rate Service (FS), Half-rate Service (HS), AMR Full-rate Service (AFS), or AMR Half-rate Service (AHS).
In decision-making phase, if the current call is an AMR call and Allow III Power Control For AMR is set to off, then power control is not applied to this call. If the current call is a non-AMR call, and Allow III Power Control For Non-AMR is set to off, then power control is not applied to this call. If the user closes these two switches during the call, then the BSC changes the power level of the current call to level 0 (2) Calculation of adjustment step l Calculation of BTS Power Control step The Power Control adjustment step is calculated according to RxLev and RxQual in every adjustment period specified by the parameter PwrCtrlDLAdjPeriod. The formula is as follows: Step(k) = {DLRexLevAdjustFactor x (BsTxMaxPower g(k) SThr) + DLRexQualAdjustFactor x (qa_filtered(k) QThr)} If step(k) > 0, the result is taken as 0. l Calculation of MS Power Control step The Power Control adjustment step is calculated according to RxLev and RxQual in every adjustment period specified by the parameter PwrCtrlDLAdjPeriod. The formula is as follows:
Step(k) = {ULRexLevAdjustFactor x (MsTxMaxPower g(k) SThr) + ULRexQualAdjustFactor x (qa_filtered(k) QThr)} If step(k) > 0, the result is taken as 0. The parameters involved in the previous formulas are interpreted as follows: l SThr = (UL(DL)RexLevHighThred/DLRexLevHighThred + UL(DL) RexLevLowThred/DLRexLevLowthred) 2 l QThr = (UL**RexQualHighThred/DL**RexQualHighThred + UL**RexQualLowThred/DL**RexQualLowThred) 2 l BsTxMaxPower indicates the maximum transmit power allowed by the TRX that carries the call and is specified by the parameter Power Level. l MsTxMaxPower = Min(maximum transmit power supported by the MS, maximum transmit power allowed in the cell). l g(k) indicates the radio channel gain calculated by Huawei III Power Control algorithm. l qa_filtered(k) indicates the measurement results after the filtering. The maximum value of step(k) is specified by the parameter ULMAXDownStep/ ULMAXUpStep, so that excessive adjustment is prevented. If step(k) exceeds the maximum value, the specified maximum value is adopted as the adjustment step.
2.64.3.4 Optimized Huawei III Power Control Algorithm

The process of the optimized Huawei III Power Control algorithm is the same as the process of Huawei III Power Control algorithm. The optimized Huawei III Power Control algorithm involves MR processing, MR filtering, calculation of the power control step, and power control execution. The optimized Huawei III Power Control algorithm takes effect when Power Control Switch is set to PWR3(Power control III) and III Power Control Optimized Enable is set to YES(Yes). This section describes the improvements of the optimized Huawei III Power Control algorithm on Huawei III Power Control algorithm. l MR power control compensation MR power control compensation aims to compensate the receive level and receive quality so that they reach the measured values at the maximum transmit power. In the optimized Huawei III Power Control algorithm, the receive level and receive quality reported through the MR are compensated. Subsequently, the receive level after compensation and the receive quality after compensation are used as inputs for MR filtering. l Dual-coefficient MR filtering algorithm The optimized Huawei III Power Control algorithm adopts the exponential filtering algorithm and MR filtering adopts the dual-coefficient filtering algorithm. The dualcoefficient filtering algorithm concerns the receive level and the receive quality. This algorithm has a strong correlation with the filtering period K and the filter adjustment factor FiltAdjustFactor. The values of K and FiltAdjustFactor vary with the measured receive level and receive quality: The value of K depends on ULRexLevExponentFilterLen/ DLRexLevExponentFilterLen and ULRexQualExponentFilterLen/ DLRexQualExponentFilterLen.
The value of FiltAdjustFactor maps III UL Filter Adjust Factor/III DL Filter Adjust Factor,he filter length can be adjusted based on III UL Filter Adjust Factor/III DL Filter Adjust Factor.
NOTE
l In this section, the symbol / separates two independent parameters. For example, "ULRexLevExponentFilterLen/DLRexLevExponentFilterLen" indicates ULRexLevExponentFilterLen or DLRexLevExponentFilterLen. ULRexLevExponentFilterLen and DLRexLevExponentFilterLen take effect in uplink power control and downlink power control respectively. l In Huawei III Power Control algorithm, different quality level thresholds are set for different speech coding schemes. The symbol ** in this section represents Full-rate Service (FS), Halfrate Service (HS), AMR Full-rate Service (AFS), or AMR Half-rate Service (AHS).
In the dual-coefficient exponential filtering algorithm, the filter response rate increases when the radio propagation environment deteriorates. In this case, the filter length is K. The rate of increasing the filtering value decreases when the radio propagation environment becomes better. In this case, the filter length is K*FiltAdjustFactor. l Calculation of the power control step The power control step of the optimized Huawei III Power Control algorithm is calculated on the basis of two step factors: step1(k) and step2(k). step1(k) is determined by RexLev Protect Factor, RexQual Protect Factor, STarget, and QTarget. The calculation formula is as follows: step1(k) = - {RexLev Protect Factor * (ca_filtered(k) - SThr) + RexQual Protect Factor * (qa_filtered(k) - QThr)} Where, RexLev Protect Factor indicates III UL RexLev Protect Factor/III DL RexLev Protect Factor. ca_filtered(k) indicates the measured receive level after the filtering. SThr = ("ULRexLevHighThred/DLRexLevHighThred"+"ULRexLevLowthred/ DLRexLevLowthred")/2. RexQual Protect Factor indicates III UL RexQual Protect Factor/III DL RexQual Protect Factor. qa_filtered(k) indicates the measured receive quality after the filtering. QThr = ("UL ** Rex Qual. Upper Threshold/DL ** Rex Qual. Upper Threshold" + "UL ** Rex Qual.Lower Threshold/DL ** Rex Qual.Lower Threshold")/2. step2(k) is determined by RexLev Adjust Factor, Rex Qual.Adjust Factor, STarget, and QTarget. The calculation formula is as follows: step2(k) = - {sfactor * (ca_filtered(k) - SThr) + qfactor * (qa_filtered(k) - QThr)} Where, sfactor indicates ULRexLevAdjustFactor/DLRexLevAdjustFactor. ca_filtered(k) indicates the measured receive level after the filtering. SThr = ("ULRexLevHighThred/DLRexLevHighThred"+"ULRexLevLowthred/ DLRexLevLowthred")/2. qfactor indicates ULRexQualAdjustFactor/DLRexQualAdjustFactor. qa_filtered(k) indicates the measured receive quality after the filtering. QThr = ("UL ** Rex Qual. Upper Threshold/DL ** Rex Qual. Upper Threshold"+"UL ** Rex Qual.Lower Threshold/DL ** Rex Qual.Lower Threshold")/2.
The step factor step(k) is determined according to the formula step(k) = max(step1(k), step2 (k)). Subsequently, based on this step factor, power control adjustment is performed. If step (k) is greater than 0, then step(k) is equal to 0, that is, transmit power is not adjusted.
2.64.3.5 Functions Related to Power Control

?.1. Active Power Control
Power Control is used to control the transmit power of the MS and BTS during a connection. For better results of Power Control, the MS and BTS should transmit signals at a proper power instead of the maximum power when the connection is initially established. To achieve this, Active Power Control should be enabled. Active Power Control enables the immediate performance of Power Control after an MS successfully gains access to the network or a handover is successfully performed in the BSC. In such a case, the BSC can control the uplink and downlink power promptly. Therefore, both the BTS and the MS transmit signals at a proper power. Active Power Control aims to reduce the system interference, improve the QoS, and decrease the power consumption of both the BTS and MS. Active Power Control is enabled when the parameter Power Forecast Allowed is set to Yes.
Active Power Control During the Access of an MS

The procedure of active Power Control during the initial access of an MS is as follows: 1. The BSC acquires the uplink and downlink path loss on the basis of the receive level in the MR of the MS on the signaling channel, transmit power of MS and BTS, and parameters Double Antenna Gain, Combiner Loss, and Path Loss of Different Frequency Band. Based on the uplink and downlink path loss and the parameters Expected UL RX_LEV and Expected DL RX_LEV, the BSC estimates the transmit power that the BTS and MS should adopt on the assigned traffic channel. The MS adopts the previously-mentioned power as the transmit power when it is initially assigned with a traffic channel, thus reducing the initial transmit power.
2.
3.
Active Power Control During Inner-BSC Handover

The procedure of active Power Control during inner-BSC handover is as follows: 1. The BSC acquires the uplink and downlink path loss on the basis of the level of the BCCH in the target cell, transmit power of MS and BTS, and value of Path Loss of Different Frequency Band. Based on the uplink and downlink path loss and the parameters Expected UL RX_LEV and Expected DL RX_LEV, the BSC estimates the transmit power that the BTS and MS should adopt on the channel of the target cell. The MS adopts the previously-mentioned power as the transmit power when it gains access to the target cell, thus reducing the transmit power during the access.
2.
3.
?.2. SAIC Power Control Optimization

Single Antenna Interference Cancellation (SAIC) is used to reduce the impact of interference on the reception of downlink signals through a signal processing technology.
An MS enabled with SAIC has improved ability of anti-interference. After SAIC is enabled, the thresholds for BTS/MS Power Control are adjusted to improve the radio performance of the BSS. SAIC is enabled when the parameters SAIC Allowed and Switch for BTS Supporting SAIC PC Adjust are set to Yes. The strategies for threshold adjustment are as follows: l When Huawei II Power Control algorithm is applied, the value of Power Control threshold Adjust for SAIC is added to that of DL Qual. Upper Threshold and DL Qual. Lower Threshold. When Huawei III Power Control algorithm is applied, the value of Power Control threshold Adjust for SAIC is deducted from that of DL**RexQualHighThred and DL**RexQualLowThred.
NOTE
** indicates FS (full rate), HS (half rate), AFS (AMR full rate), or AHS (AMR half rate).
2.64.4 Parameters
This chapter describes the parameters related to power control. For the meaning of each parameter, see Table 2-186. For the default value, value ranges, and MML commands of each parameter, see Table 2-187. Table 2-186 Parameter description (1) Parameter Allow III Power Control For AMR Allow III Power Control For NonAMR Description Whether to enable the III power control algorithm for AMR calls. If enabled, power control is performed on AMR calls. Whether to enable the III power control algorithm for Non-AMR calls. If enabled, power control is performed on Non-AMR calls. If the number of measurement reports lost consecutively is no larger than this value, linear interpolation is performed for the values in the lost measurement reports based on the values in the two measurement reports preceding and following the lost measurement reports. Otherwise, the lost measurement reports will be discarded, and the value will be recalculated when new measurement reports arrive. Combined loss used to estimate the downlink power during assignment Number of downlink measurement reports that the BSC predicts. The BSC takes a while to confirm the power control effect of a power control command. Thus, the BSC makes a power control decision based on a measurement report that lags behind the changes in the receive level and quality instead of reflecting the real-time radio environment. As a result, the power control is late. To prevent late power control to a certain degree, the power control algorithm involves a measurement report prediction filter. The BSC can sample several downlink measurement reports in a short time and then weigh them to predict future N measurement reports. This parameter specifies the number N.
Allowed MR Number Lost Combiner Loss
DL MR. Number Predicted
Issue 08 (2011-09-30)
1068
Parameter
Description During downlink power control, if the downlink receive quality level is equal to or greater than "DL Qual, bad Trig Threshold", "DL RX_LEV Upper Threshold" is increased by "DL Qual. Bad UpLEVDiff" to further increase the expected downlink power level. During downlink power control, if the downlink receive quality level is equal to or greater than "DL Qual, bad Trig Threshold", "DL RX_LEV Upper Threshold" is increased by "DL Qual. Bad UpLEVDiff" to further increase the expected downlink power level. Quality level threshold for increasing downlink signal power. If the BTS transmits signals at a quality level greater than this threshold, the BSC increases the power of the BTS. If (downlink receive level + "MAX Up Adj. PC Value by Qual.") > "DL RX_LEV Upper Threshold", the BSC does not adjust the transmit power. Quality level threshold for decreasing downlink signal power. If the BTS transmits signals at a quality level less than this threshold, the BSC decreases the power of the BTS. If (downlink receive level - "MAX Down Adj. PC Value by Qual.") < "DL RX_LEV Lower Threshold", the BSC does not adjust the transmit power. Lower threshold for downlink signal strength If the downlink received signal level is less than this threshold, a power increase is computed. Then, the power is increased by the least of the power increase, "MAX Up Adj. PC Value by RX_LEV", and "MAX Up Adj. PC Value by Qual.". Power increase = ("DL RX_LEV Upper Threshold" + "AMR DL RX_LEV Lower Threshold")/2 - downlink received signal level Upper threshold for downlink signal strength If the downlink received signal level is greater than this threshold, a power decrease is computed. Then, the power is decreased by the least of the power decrease, maximum power adjustment step allowed by the quality zone to which the received signal quality belongs, and "MAX Down Adj. PC Value by Qual.". Power decrease = downlink received signal level - ("DL RX_LEV Upper Threshold" + "AMR DL RX_LEV Lower Threshold")/2 The maximum power adjustment step allowed by the quality zone is chosen from "MAX Down Adj.Value Qual.Zone 0", "MAX Down Adj.Value Qual.Zone 1", and "MAX Down Adj.Value Qual.Zone 2" according to the quality zone. If the downlink receive quality level of an AMR full rate call is greater than this parameter, the call needs to undergo Huawei power control generation III. If the downlink receive quality level of an AMR full rate call is smaller than this parameter, the call needs to undergo Huawei power control generation III. If the downlink receive quality level of an AMR half rate call is greater than this parameter, the call needs to undergo Huawei power control generation III.
DL Qual. Bad Trig Threshold
DL Qual. Bad UpLEVDiff
DL Qual. Lower Threshold
DL Qual. Upper Threshold
DL RX_LEV Lower Threshold
DL RX_LEV Upper Threshold DLAFSRexQual HighThred DLAFSRexQual LowThred DLAHSRexQual HighThred
Issue 08 (2011-09-30)
1069
Parameter DLAHSRexQual LowThred
Description If the downlink receive quality level of an AMR half rate call is smaller than this parameter, the call needs to undergo Huawei power control generation III. Upper quality threshold for Huawei power control generation III on a full rate call. If the downlink receive quality level of a full rate call is greater than this threshold, the call needs to undergo Huawei power control generation III. Lower quality threshold for Huawei power control generation III on a full rate call. If the downlink receive quality level of a full rate call is smaller than this threshold, the call needs to undergo Huawei power control generation III. Upper quality threshold for Huawei power control generation III on a half rate call. If the downlink receive quality level of a half rate call is greater than this threshold, the call needs to undergo Huawei power control generation III. Lower quality threshold for Huawei power control generation III on a half rate call. If the downlink receive quality level of a half rate call is smallter than this threshold, the call needs to undergo Huawei power control generation III. This parameter specifies the downlink signal strength factor multiplied by 10 during the calculation of the downlink power control step. The downlink signal strength factor is a coefficient indicating how much the signal strength is considered during the calculation of the downlink power control step. Length of the exponential filter for downlink signal strength. A single measurement report may not reflect the actual network situations accurately. Therefore, the BSC needs to filter the measured values in several successive measurement reports to reflect the radio environment. Upper receive level threshold for downlink power control. If the downlink receive level is greater than this threshold, the power of the downlink signal needs to be decreased. Lower receive level threshold for downlink power control. If the downlink receive level is smaller than this threshold, the power of the uplink signal needs to be increased. Length of the slide window filter for downlink signal strength. A single measurement report may not reflect the actual network situations accurately. Therefore, the BSC needs to filter the measured values in several successive measurement reports to reflect the radio environment. This parameter specifies the downlink quality level factor multiplied by 10 during the calculation of the downlink power control step. The downlink quality level factor is a coefficient indicating how much the quality level is considered during the calculation of the downlink power control step.
DLFSRexQualHighThred
DLFSRexQualLowThred
DLHSRexQualHighThred
DLHSRexQualLowThred
DLRexLevAdjus tFactor
DLRexLevExponentFilterLen DLRexLevHighThred DLRexLevLowt hred
DLRexLevSlideWindow
DLRexQualAdju stFactor
Issue 08 (2011-09-30)
1070
Parameter
Description Length of the exponential filter for downlink signal quality. A single measurement report may not reflect the actual network situations accurately. Therefore, the BSC needs to filter the measured values in several successive measurement reports to reflect the radio environment. Length of the slide window filter for downlink signal quality. A single measurement report may not reflect the actual network situations accurately. Therefore, the BSC needs to filter the measured values in several successive measurement reports to reflect the radio environment. Dual-antenna gain used to estimate the downlink power during assignment Received signal strength at an MS expected in power forecast, which helps to compute the initial transmit power of the BTS Received signal strength at the BTS expected in power forecast, which helps to compute the initial transmit power of an MS Number of measurement reports sampled for averaging downlink signal quality. A single measurement report may not reflect the actual network situations accurately. Therefore, the BSC needs to average the measured values in several successive measurement reports to reflect the radio environment. Number of measurement reports sampled for averaging downlink signal strength. A single measurement report may not reflect the actual network situations accurately. Therefore, the BSC needs to average the measured values in several successive measurement reports to reflect the radio environment. When the network receives measurement reports, the measurement values in several straight measurement reports are filtered to reflect the radio operating environment for the sake of accuracy. This parameter specifies the number of measurement reports sampled for filtering the uplink signal quality. When the network receives measurement reports, in consideration of the accuracy of a single measurement report, the measurement values in certain measurement reports are filtered to represent the radio operating environment. This parameter specifies the number of measurement reports sampled for filtering the uplink signal strength. Filter adjustment factor for downlink power control. Setting this parameter high helps to smooth the filtered values and to reduce the impact of poor measurement reports on the filtered values. Setting this parameter low helps to draw the filtered values close to the actual values and to heighten the power control effect. A power control step cannot exceed the step computed according to "III DL RexLev Protect Factor" and "III DL RexQual Protect Factor". A power control step cannot exceed the step computed according to "III DL RexLev Protect Factor" and "III DL RexQual Protect Factor".
DLRexQualExp onentFilterLen
DLRexQualSlide Window Double Antenna Gain Expected DL RX_LEV Expected UL RX_LEV
Filter Length for DL Qual.
Filter Length for DL RX_LEV
Filter Length for UL Qual.
Filter Length for UL RX_LEV
III DL Filter Adjust Factor III DL RexLev Protect Factor III DL RexQual Protect Factor
Issue 08 (2011-09-30)
1071
Parameter III DL RexQual Protect Factor III Power Control Optimized Enable
Description A power control step cannot exceed the step computed according to "III DL RexLev Protect Factor" and "III DL RexQual Protect Factor".
Whether to enable the optimized power control algorithm III Filter adjustment factor for uplink power control. If this parameter is set to a large value, the filtered values become smooth, thus reducing the impact of poor measurement reports on the filtered values. If this parameter is set to a small value, the filter values are close to the actual ones and thus the power control speed is increased. Signal strength factor for the protective limitation on calculating the uplink power control adjustment step. The calculated step value cannot exceed the step value that is obtained on the basis of the signal strength protection factor and the signal quality protection factor. Signal strength factor for the protective limitation on calculating the uplink power control adjustment step. The calculated step value cannot exceed the step value that is obtained on the basis of the signal strength protection factor and the signal quality protection factor. Step of downward power adjustment according to the quality of the received signals Huawei power control algorithm II divides three quality zones according to the quality of the receive signals. When the power is downwardly adjusted according to the level, the maximum downward adjustment step can vary according to the quality of the received signals. This parameter specifies the maximum step of downward power adjustment when the quality of the received signals falls into quality zone 0. Huawei power control algorithm II divides three quality zones according to the quality of the receive signals. When the power is downwardly adjusted according to the level, the maximum downward adjustment step can vary according to the quality of the received signals. This parameter specifies the maximum step of downward power adjustment when the quality of the received signals falls into quality zone 1. Huawei power control algorithm II divides three quality zones according to the quality of the receive signals. When the power is downwardly adjusted according to the level, the maximum downward adjustment step can vary according to the quality of the received signals. This parameter specifies the maximum step of downward power adjustment when the quality of the received signals falls into quality zone 2. Step of upward power adjustment according to the quality of the received signals
III UL Filter Adjust Factor
III UL RexLev Protect Factor
III UL RexQual Protect Factor MAX Down Adj. PC Value by Qual.
MAX Down Adj.Value Qual.Zone 0
MAX Down Adj.Value Qual.Zone 2 MAX Up Adj. PC Value by Qual.
Issue 08 (2011-09-30)
1072
Parameter MAX Up Adj. PC Value by RX_LEV Measurement Report Type
Description Step of upward power adjustment according to the quality of the received signals Type of the measurement report (MR) reported by the MS Whether power control algorithm II allows measurement report compensation. When making a power control decision, the BSC retrieves a certain number of history measurement reports and performs weighted filtering on the receive level values and receive quality values in these reports, which may be obtained when different transmit powers were used by BTSs or MSs. To ensure that correct receive level values and receive quality values are used in filtering, you must compensate the receive level values and receive quality values in history measurement reports obtained when transmit powers different than the current one were used. Whether to enable the BTS to preprocess measurement reports. This parameter determines where to conduct power control. When the number of the lost measurement reports exceeds this parameter during a power control period, the power control stops. Transmission loss difference between radio frequencies on different bands Minimum interval between two consecutive power control commands Whether to enable power control algorithm II or power control algorithm III Adjustment step of the downlink signal quality threshold in power control algorithm II for MSs that support SAIC. The network side uses a lower downlink signal quality threshold for SAIC-supported MSs in power control, thus lowering the transmit power of the corresponding BTS and reducing the interferences in the whole network. Adjustment step of the downlink signal quality threshold in power control algorithm II for MSs that support SAIC. The network side uses a lower downlink signal quality threshold for SAIC-supported MSs in power control, thus lowering the transmit power of the corresponding BTS and reducing the interferences in the whole network. Whether to allow active power control. If this parameter is set to YES, the system performs power forecast in the process of initial access assignment or service channel activation during intra-BSC handovers, and sends the forecast initial power information to the BTSs through channel activation messages. In this way, the MSs and BTSs can adjust the transmit power. If this parameter is set to NO, the system does not perform power forecast, and the MSs and BTSs choose the maximum transmit power.
MR. Compensation Allowed MR.Preprocessin g MRMissNumber Path Loss of Different Frequency Band PC Interval Power Control Switch
Power Control Threshold Adjust for SAIC
Power Forecast Allowed
Issue 08 (2011-09-30)
1073
Parameter
Description This parameter specifies the transmit power level of the TRX. The greater this parameter is, the smaller the transmit power is. When this parameter is set to "0", the transmit power level of the TRX is the greatest. Each time this parameter increases by one level, the transmit power reduces by 2 dB.For different types of BTSs, the value range of this parameter is different.BTS3X: 0-10BTS3001C: 0-13BTS3002C: 0-10Doubletransceiver BTSs (BTS3012,BTS3012AE,BTS3006C): 0-10DBS3900 GSM, BTS3900 GSM, BTS3900A GSM: 0-10. Minimum interval between two consecutive downlink power control commands Whether an MS supports the SAIC function Maximum number of discarded MRs allowed on the SDCCH in a power control period Frequency at which the BTSs submit pre-processed measurement reports to the BSC Whether to specify "Power Control threshold Adjust for SAIC" in the MML command "SET GCELLPWR3" Maximum number of discarded MRs allowed on the TCH in a power control period Whether to enable the BTS to transfer BTS/MS power class to the BSC Whether the BTSs send the original measurement reports to the BSC after pre-processing them. When this parameter is set to YES, the BTSs sends the original and pre-processed measurement reports to the BSC. After the BSC delivers the power control command, it should wait for a certain period before affirming the effect of the power control. Therefore, the MR that power control decision is based on cannot accurately reflect the radio environment during the power adjustment, but misses the latest changes of the receive level and receive quality of the MS. Thus, the power adjustment is delayed. To compensate the delay of power adjustment, the power control algorithm implements the prediction and filtering function. In other words, the BSC samples several uplink measurement reports, performs weighted filtering, and predicts N measurement reports from the current time onwards in a short period. This parameter determines the number of uplink measurement reports predicted by the BSC. In other words, the value of this parameter equals to the previous number N. In the case of power control, when the uplink receive quality is not smaller than "UL Qual. Bad Trig Threshold", the actual "UL RX_LEV Upper Threshold" is increased by "UL Qual. Bad UpLEVDiff".
Power Level PwrCtrlDLAdjP eriod SAIC Allowed SdMrCutNum Sent Freq.of preprocessed MR Switch for BTS Supporting SAIC PC Adjust TchMrCutNum Transfer BTS/ MS Power Class Transfer Original MR
UL MR. Number Predicted UL Qual. Bad Trig Threshold
Issue 08 (2011-09-30)
1074
Parameter UL Qual. Bad UpLEVDiff
Description In the case of power control, when the uplink receive quality is not smaller than "UL Qual. Bad Trig Threshold", the actual "UL RX_LEV Upper Threshold" is increased by "UL Qual. Bad UpLEVDiff". The MS transmit power is increased only when the quality level of the MS transmit signal is greater than the value of the parameter. If (the uplink receive level + MAX Up Adj. PC Value by Qual) is greater than "UL RX_LEV Upper Threshold", the MS transmit power is not adjusted. The MS transmit power is decreased only when the quality level of the MS transmit signal is smaller than the value of the parameter. If (the uplink receive level - MAX Up Adj. PC Value by Qual) is smaller than "UL RX_LEV Lower Threshold", the MS transmit power is not adjusted. When the uplink receive level is below the threshold, Huawei II power control is performed. When the uplink receive level reaches the threshold, Huawei II power control is performed. Current call is an AMR full-rate call, and when the uplink receive quality is greater than the threshold, Huawei III power control is performed. Current call is an AMR full-rate call, and when the uplink receive quality is lower than the threshold, Huawei III power control is performed. Current call is an AMR half-rate call, and when the uplink receive quality is greater than the threshold, Huawei III power control is performed. Current call is an AMR half-rate call, and when the uplink receive quality is lower than the threshold, Huawei III power control is performed. Current call is a full-rate call, and when the uplink receive quality is greater than the threshold, Huawei III power control is performed. Current call is a full-rate call, and when the uplink receive quality is lower than the threshold, Huawei III power control is performed. Current call is a half-rate call, and when the uplink receive quality is greater than the threshold, Huawei III power control is performed. Current call is a half-rate call, and when the uplink receive quality is lower than the threshold, Huawei III power control is performed. Maximum permissible adjustment step when the BSC decreases the uplink transmit power Maximum permissible adjustment step when the BSC increases the uplink transmit power This parameter specifies the uplink signal strength factor multiplied by 10 during the calculation of the uplink power control step. The uplink signal strength factor is a coefficient indicating how much the signal strength is considered during the calculation of the uplink power control step.
UL Qual. Lower Threshold
UL Qual. Upper Threshold UL RX_LEV Lower Threshold UL RX_LEV Upper Threshold ULAFSRexQual HighThred ULAFSRexQual LowThred ULAHSRexQual HighThred ULAHSRexQual LowThred ULFSRexQualHighThred ULFSRexQualLowThred ULHSRexQualHighThred ULHSRexQualLowThred ULMAXDownSt ep ULMAXUpStep
ULRexLevAdjus tFactor
Issue 08 (2011-09-30)
1075
Parameter
Description When the network receives measurement reports, the measurement values in several straight measurement reports are filtered to reflect the radio operating environment for the sake of accuracy. This parameter specifies the number of measurement reports sampled for exponent filtering of the uplink signal strength. When the uplink receive level reaches the threshold, Huawei III power control is performed. When the uplink receive level is lower than the threshold, Huawei III power control is performed. When the network receives measurement reports, the measurement values in several straight measurement reports are filtered to reflect the radio operating environment for the sake of accuracy. This parameter specifies the number of measurement reports sampled for slide-window filtering of the uplink signal strength. This parameter specifies the uplink quality level factor multiplied by 10 during the calculation of the uplink power control step. The uplink quality level factor is a coefficient indicating how much the quality level is considered during the calculation of the uplink power control step. When the network receives measurement reports, the measurement values in several straight measurement reports are filtered to reflect the radio operating environment for the sake of accuracy. This parameter specifies the number of measurement reports sampled for exponent filtering of the uplink signal quality. When the network receives measurement reports, the measurement values in several straight measurement reports are filtered to reflect the radio operating environment for the sake of accuracy. This parameter specifies the number of measurement reports sampled for slide-window filtering of the uplink signal quality.
ULRexLevExponentFilterLen ULRexLevHighThred ULRexLevLowT hred
ULRexLevSlideWindow
ULRexQualAdju stFactor
ULRexQualExp onentFilterLen
ULRexQualSlide Window
Table 2-187 Parameter description (2) Parameter Default Value GUI Value Range OFF(Not Allowed) , ON (Allowed ) Actual Value Range Unit MML Com mand SET GCEL LPWR 3 (Optio nal) Impact
Allow III Power Control For AMR
ON
OFF, ON
None
Cell
Issue 08 (2011-09-30)
1076
Parameter
Default Value
GUI Value Range OFF(Not Allowed) , ON (Allowed )
Actual Value Range
Unit
MML Com mand SET GCEL LPWR 3 (Optio nal) SET GCEL LHOFI TPEN (Optio nal) SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR BASIC (Optio nal)
Impact
Allow III Power Control For NonAMR
ON
OFF, ON
None
Cell
Allowed MR Number Lost
0~31
0~31
None
Cell
Combiner Loss
45
0~100
0~10, step:0.1
dB
Cell
DL MR. Number Predicted
0~3
0~3
None
Cell
DL Qual. Bad Trig Threshold
0~7
0~7
None
Cell
DL Qual. Bad UpLEVDiff
10
0~63
0~63
dB
Cell
DL Qual. Lower Threshold
0~7
0~7
None
Cell
Issue 08 (2011-09-30)
1077
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Com mand SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal)
Impact
DL Qual. Upper Threshold
0~7
0~7
None
Cell
DL RX_LEV Lower Threshold
28
0~63
0~63
dB
Cell
DL RX_LEV Upper Threshold
45
0~63
0~63
dB
Cell
DLAFSRexQualHighThred
14
1~30
1~30
dB
Cell
DLAFSRexQualLowThred
14
1~30
1~30
dB
Cell
DLAHSRexQualHighThred
16
1~30
1~30
dB
Cell
DLAHSRexQualLowThred
16
1~30
1~30
dB
Cell
Issue 08 (2011-09-30)
1078
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Com mand SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal)
Impact
DLFSRexQualHighThred
16
1~30
1~30
dB
Cell
DLFSRexQualLowThred
16
1~30
1~30
dB
Cell
DLHSRexQualHighThred
18
1~30
1~30
dB
Cell
DLHSRexQualLowThred
18
1~30
1~30
dB
Cell
DLRexLevAdjustFactor
0~10
0~10 TCH: 0~9120, step:480; SDCCH: 0~8930, step:470
None
Cell
DLRexLevExponentFilterLen
0~19
ms
Cell
DLRexLevHighThred
20
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
1079
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Com mand SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR BASIC (Optio nal)
Impact
DLRexLevLowthr ed
20
0~63
0~63 TCH: 480~9600 , step:480; SDCCH: 470~9400 , step:470
dB
Cell
DLRexLevSlideWindow
1~20
ms
Cell
DLRexQualAdjust Factor
0~10
0~10 TCH: 0~9120, step:480; SDCCH: 0~8930, step:470 TCH: 480~9600 , step:480; SDCCH: 470~9400 , step:470
None
Cell
DLRexQualExponentFilterLen
0~19
ms
Cell
DLRexQualSlideWindow
1~20
ms
Cell
Double Antenna Gain
30
0~255
0~25.5, step:0.1
dB
Cell
Expected DL RX_LEV
30
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
1080
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Com mand SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal)
Impact
Expected UL RX_LEV
30
0~63
0~63 TCH: 480~9600 , step:480; SDCCH: 470~9400 , step:470 TCH: 480~9600 , step:480; SDCCH: 470~9400 , step:470 TCH: 480~9600 , step:480; SDCCH: 470~9400 , step:470 TCH: 480~9600 , step:480; SDCCH: 470~9400 , step:470
dB
Cell
Filter Length for DL Qual.
1~20
ms
Cell
Filter Length for DL RX_LEV
1~20
ms
Cell
Filter Length for UL Qual.
1~20
ms
Cell
Filter Length for UL RX_LEV
1~20
ms
Cell
III DL Filter Adjust Factor
1~10
1~10
None
Cell
III DL RexLev Protect Factor
0~100
0~100
None
Cell
Issue 08 (2011-09-30)
1081
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
Impact
III DL RexQual Protect Factor
55
0~100
0~100
None
Cell
III DL RexQual Protect Factor
55
0~100
0~100
None
Cell
III Power Control Optimized Enable
NO
NO(No), YES (Yes)
NO, YES
None
Cell
III UL Filter Adjust Factor
1~10
1~10
None
Cell
III UL RexLev Protect Factor
0~100
0~100
None
Cell
III UL RexQual Protect Factor
75
0~100
0~100
None
Cell
MAX Down Adj. PC Value by Qual.
0~4
0~4
dB
Cell
Issue 08 (2011-09-30)
1082
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Com mand SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal)
Impact
0~30
0~30
dB
Cell
0~30
0~30
dB
Cell
0~30
0~30
dB
Cell
MAX Up Adj. PC Value by Qual.
0~32
0~32
dB
Cell
MAX Up Adj. PC Value by RX_LEV
0~32 EnhMeas Report (Enhance d Measure ment Report), ComMea sReport (Commo n Measure ment Report)
0~32
dB
Cell
Measurement Report Type
ComMeas Report
None
SET GCEL LCCU TRAN SYS (Optio nal)
Cell
Issue 08 (2011-09-30)
1083
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Com mand SET GCEL LPWR 2 (Optio nal)
Impact
MR. Compensation Allowed
YES
NO(No), YES (Yes) BSC_Pre processin g(BSC preproces sing), BTS_Pre processin g(BTS preproces sing)
NO, YES
None
Cell
MR.Preprocessing
BTS_Prep rocessing
BSC_Prep rocessing, BTS_Prep rocessing
None
SET GCEL LHOC TRL (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR BASIC (Optio nal)
Cell
MRMissNumber
1~255
1~255
None
Cell
Path Loss of Different Frequency Band
79
0~255
0~25.5, step:0.1 TCH: 480~7200 , step:480; SDCCH: 470~7050 , step:470
dB
Cell
PC Interval
1~15 PWR2 (Power control II), PWR3 (Power controlIII )
ms
Cell
Power Control Switch
PWR3
PWR2, PWR3
None
SET GCEL LPWR BASIC (Optio nal)
Cell
Issue 08 (2011-09-30)
1084
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Com mand SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR BASIC (Optio nal) SET GTRX DEV (Optio nal)
Impact
0~2
0~2
None
Cell
0~2
0~2
None
Cell
Power Forecast Allowed
NO
NO(No), YES (Yes)
NO, YES
None
Cell
Power Level
0~13
0~13 TCH: 480~1224 00, step: 480; SDCCH: 470~1198 50, step: 470
None
TRX
PwrCtrlDLAdjPeri od
0~255
ms
SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR 3 (Optio nal)
Cell
SAIC Allowed
NO
NO(No), YES (Yes)
NO, YES
None
Cell
SdMrCutNum
0~5
0~5
None
Cell
Issue 08 (2011-09-30)
1085
Parameter
Default Value
GUI Value Range NOreport (Do not report), Twice_ps (Twice every second), Once_ps (Once every second), Once_2s (Once every two second), Once_4s (Once every four second)
Actual Value Range
Unit
MML Com mand
Impact
Sent Freq.of preprocessed MR
Once_ps
None
SET GCEL LHOC TRL (Optio nal) SET GCEL LSOF T (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LHOC TRL (Optio nal) SET GCEL LHOC TRL (Optio nal)
Cell
Switch for BTS Supporting SAIC PC Adjust
OFF
OFF (Off), ON (On)
OFF, ON
None
Cell
TchMrCutNum
0~10
0~10
None
Cell
Transfer BTS/MS Power Class
YES
NO(No), YES (Yes)
NO, YES
None
Cell
Transfer Original MR
NO
NO(No), YES (Yes)
NO, YES
None
Cell
Issue 08 (2011-09-30)
1086
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
MML Com mand SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR 2 (Optio nal) SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR BASIC (Optio nal) SET GCEL LPWR BASIC (Optio nal)
Impact
UL MR. Number Predicted
0~3
0~3
None
Cell
UL Qual. Bad Trig Threshold
0~7
0~7
None
Cell
UL Qual. Bad UpLEVDiff
0~63
0~63
dB
Cell
UL Qual. Lower Threshold
0~7
0~7
None
Cell
UL Qual. Upper Threshold
0~7
0~7
None
Cell
UL RX_LEV Lower Threshold
18
0~63
0~63
dB
Cell
UL RX_LEV Upper Threshold
30
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
1087
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
Impact
ULAFSRexQualHighThred
14
1~30
1~30
dB
Cell
ULAFSRexQualLowThred
14
1~30
1~30
dB
Cell
ULAHSRexQualHighThred
16
1~30
1~30
dB
Cell
ULAHSRexQualLowThred
16
1~30
1~30
dB
Cell
ULFSRexQualHighThred
16
1~30
1~30
dB
Cell
ULFSRexQualLowThred
16
1~30
1~30
dB
Cell
ULHSRexQualHighThred
18
1~30
1~30
dB
Cell
Issue 08 (2011-09-30)
1088
Parameter
Default Value
GUI Value Range
Actual Value Range
Unit
Impact
ULHSRexQualLowThred
18
1~30
1~30
dB
Cell
ULMAXDownSte p
1~30
1~30
dB
Cell
ULMAXUpStep
1~30
1~30
dB
Cell
ULRexLevAdjustFactor
0~10
0~10 TCH: 0~9120, step:480; SDCCH: 0~8930, step:470
None
Cell
ULRexLevExponentFilterLen
0~19
ms
Cell
ULRexLevHighThred
18
0~63
0~63
dB
Cell
ULRexLevLowTh red
18
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
1089
Parameter
Default Value
GUI Value Range
Actual Value Range TCH: 0~9120, step:480; SDCCH: 0~8930, step:470
Unit
MML Com mand SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal) SET GCEL LPWR 3 (Optio nal)
Impact
ULRexLevSlideWindow
1~20
ms
Cell
ULRexQualAdjust Factor
0~10
0~10 TCH: 0~9120, step:480; SDCCH: 0~8930, step:470 TCH: 0~9120, step:480; SDCCH: 0~8930, step:470
None
Cell
ULRexQualExponentFilterLen
0~19
ms
Cell
ULRexQualSlideWindow
1~20
ms
Cell
2.64.5 Counters
2.64.6 Glossary

l l l l l
Issue 08 (2011-09-30)
3GPP TS 04.08: "Mobile radio interface layer 3: specification" 3GPP TS 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide
l l l
BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.65 PS Handover
2.65.1 Introduction
2.65.1.1 Scope
This document describes the common intra-BSC inter-cell handover procedure, inter-BSC intercell handover procedure, and 2G/3G inter-RAT handover procedure.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the PS handover feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of information that was not provided in the earlier version.
Document Issues
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, the following changes are incorporated:
Change Description None. 2.65.3.4 2G/3G Inter-RAT Handover is added.
01 (2009-06-30)
2.65.2 Overview
The IP-based services, such as VoIP, PoC, and Gaming, have high requirements for time delay in the case of cell reselection. As there is an ever increasing number of subscribers to the IPbased services, a solution for minimizing time delay is in great demand. To achieve the minimum possible time delay, Huawei introduces the PS Handover feature that can allocate radio resources to the MS in the target cell before the cell reselection is performed. Thus, the delay is shortened to no more than 150 ms. In addition, the PS Handover feature considers factors such as signal level and load of the neighboring cells before cell reselection is performed. This ensures a high success rate of the PS handover and great data throughput in the target cell, thus improving the QoS. A PS handover is triggered by the Packet Cell Change Notification message sent by the MS or by the NC2 cell reselection algorithm. If the triggering conditions of the PS handover are not met, cell reselection is performed. After reselecting the target cell, the MS initiates a cell update procedure. If the triggering conditions of the PS handover are met, a PS handover is performed. In this case, radio resources are allocated in the target cell before the MS initiates a cell update procedure in the source cell. The BSC delivers the MS data in the source cell and target cell simultaneously, thus ensuring that services are not disrupted during cell update. Currently, DTM handover is not supported. In DTM, the BSC makes handover decisions according to CS services. For details, see 2.46 Handover. CS handovers may disrupt PS services. With respect to the BSC, PS handovers can be classified into the following types: l Common intra-BSC inter-cell handover The source cell and the target cell belong to the same BSC but to different RAs or NSEs. For details, see Packet-switched handover for GERAN A/Gb mode; Stage 2 l Inter-BSC inter-cell handover The source cell and the target cell belong to different BSCs. Inter-BSC inter-cell handovers include 2G/3G inter-RAT handovers. Inter-RAT handover means that the source cell and target cell belong to the systems of different radio access technologies, for example, the 2G network and the 3G network. Both the common intra-BSC inter-cell handover and the inter-BSC inter-cell handover involve three procedures: handover decision, handover preparation, and handover execution. The
handover decision conditions of a common intra-BSC inter-cell handover are the same as those of an inter-BSC inter-cell handover.

2.65.3.1 Handover Decision
The following conditions must be met before a PS handover is performed: l The MS supports the PS handover. The radio access capability reported by the MS contains the PS handover field, which specifies whether the MS supports the PS handover. l l The license of the BSC supports the PS handover. The BSC supports the PS handover. The settings of the parameters should meet any of the following requirements: Support NACC is set to YES, Network Control Mode is set to NC0 or NC1, and PS Handover Support is set to YES. Support NC2 is set to YES, Network Control Mode is set to NC2, and PS Handover Support is set to YES. l The SGSN supports the PS handover. The Extended Feature Bitmap field is added to the BVC RESET and BVC RESET ACK messages transmitted over the Gb interface between the SGSN and the BSC. This field specifies whether the NSE supports the PS handover. If the BVC RESET or BVC RESET ACK message received from the SGSN does not contain the Extended Feature Bitmap field or if the Extended Feature Bitmap field indicates that the PS handover is not supported, it is regarded that none of the cells under the NSE of the SGSN supports the PS handover. That is, the source cell does not support the PS handover. Otherwise, all the cells under the NSE of the SGSN support the PS handover, that is, the source cell supports the PS handover. Through the preceding negotiation procedure, the BSC determines whether the SGSN supports the PS handover. l l Both the BSC and the SGSN support the Packet Flow Context (PFC) procedure. Any of the following handover triggering conditions is met: The MS operating in NC0 or NC1 mode sends the BSC a Packet Cell Change Notification message, which contains the information on the target cell. If the target cell is a neighboring 2G cell, a PS handover procedure is initiated. If the target cell is a neighboring 3G FDD cell and Support Out Inter-RAT Inter-Cell PS Handover is set to SUPPORT, a PS handover procedure is also initiated. Currently, a PS handover to a neighboring 3G TDD cell is not supported. The MS operating in NC2 mode sends MRs to the BSC. The BSC selects the target cell of the PS handover according to the NC2 cell reselection algorithm. If the target cell is a neighboring 2G cell, a PS handover procedure is initiated. If the target cell is a neighboring 3G FDD cell and Support Out Inter-RAT Inter-Cell PS Handover is set to SUPPORT, a PS handover procedure is also initiated. Currently, a PS handover to a neighboring 3G TDD cell is not supported.
2.65.3.2 Common Intra-BSC Inter-Cell Handover

Handover Preparation
Figure 2-281 shows the procedure for the preparation of a common intra-BSC inter-cell handover. Figure 2-281 Procedure for the preparation of a common intra-BSC inter-cell handover
1.
The MS in the source cell sends a PS Handover Required message to the SGSN. The message contains the following information elements (IEs): old TLLI, handover cause, source cell identifier, target cell identifier, transparent container (containing the radio access capability of the MS, paging mode, global TFI, whether to request the system information of the target cell) from the source BSC to the target BSC, and active PFC list (containing the PFI of each PFC). After receiving the PS Handover Required message, the SGSN determines the handover type (intra-SGSN handover, inter-SGSN handover, or inter-RAT handover) according to the target cell identifier and checks whether the routing area is changed. If the routing area remains unchanged, the SGSN sends the target BSC a PS Handover Request message. The message contains the following IEs: TLLI, IMSI, handover cause, source cell identifier, target cell identifier, transparent container from the source cell to the target cell, and PFC list to be created. If the routing area changes, the SGSN allocates a new P-TMSI to the MS and generates a new TLLI based on the P-TMSI before sending a PS Handover Request message to the target cell. After receiving the PS Handover Request message, the target cell creates the MS context and requests the uplink channel resources. In addition, the target cell obtains its own system information and creates the transparent container from the target BSC to the source BSC. The BSC sends the SGSN a PS Handover Request Acknowledge message. The message contains the following IEs: TLLI, successfully created PFC list, and transparent container (including the PS handover command and the system information of the target cell) from the target cell to the source cell. Then, the BSC prepares to receive downlink LLC PDUs. When the SGSN receives the PS Handover Request Acknowledge message, the resource
2.
3.
4.
Issue 08 (2011-09-30)
allocation for the MS in the target cell is complete. At this time, the PS handover preparation phase ends and the PS handover execution phase begins.
Handover Execution
Figure 2-282 shows the procedure for the execution of a common intra-BSC inter-cell handover. Figure 2-282 Procedure for the execution of a common intra-BSC inter-cell handover
1. 2.
The SGSN sends downlink LLC PDUs to the MS through the source cell. After receiving the PS Handover Request Acknowledge message, the SGSN sends subsequent LLC PDUs to the target cell according to the QoS. The BSC sends downlink data to the MS on the allocated radio channels. At this time, the MS still camps on the source cell. The SGSN sends a PS Handover Required Acknowledge message to the BSC. The message contains the following information elements: TLLI, successfully created PFC list, and transparent container (including the handover command and the system information of the target cell) from the target BSC to the source BSC. Before sending the PS Handover Required Acknowledge message to the BSC, the SGSN can suspend the downlink data transmission of any PDP context according to the QoS. The BSC suspends the downlink data transmission and then sends a PS Handover Command message to the MS. After sending the message, the BSC resumes the downlink data transmission until no LLC PDU needs to be transmitted or the PFC is released. After receiving the PS Handover Command message, the MS stops data reception in the source
3.
4.
Issue 08 (2011-09-30)
cell and meanwhile suspends the uplink data transmission. After receiving the PS Handover Command message, the MS processes the uplink data as follows: l In the case of a PFC with an ongoing handover, all the uplink data packets that are not transmitted are buffered according to the QoS levels. l Subsequent uplink data packets are buffered according to the QoS levels. l The MS can discard uplink data packets during the link disruption period to meet the real-time requirements. 5. On the radio channels allocated in the handover preparation phase, the MS sends the BSC a PS Handover Access message through four access bursts. The message contains the reference information on the handover. Based on the reference information in the PS Handover Access message from the MS, the BSC determines whether to send the MS a Packet Physical information message. If the PS Handover Command message does not contain the TA, the BSC sends a Packet Physical information message containing the TA to the MS. If the PS Handover Command message contains the TA, the BSC does not send a Packet Physical information message to the MS. The MS determines whether the routing areas of the source cell and target cell are the same. If they are the same, the MS sends a Cell Update message to the SGSN. If they are different, the MS sends a Routing Area Update Request message to the SGSN. After the target cell successfully receives the first uplink data block, the BSC sends the SGSN a PS Handover Complete (containing the TLLI and IMSI) message, notifying the SGSN that the MS is handed over to the target cell. The MS starts to send uplink data packets.
6.
7.
8.
9.
10. After receiving the PS Handover Complete message, the SGSN instructs the BSC to delete the PFC corresponding to the source cell. After receiving the Delete BSC PFC message from the SGSN, the BSC deletes the corresponding PFC and TBF and releases the radio resources. Then, the BSC starts to receive data from the MS in the target cell.
2.65.3.3 Inter-BSC Inter-Cell Handover

On the BSC side, the procedures for handover preparation and handover execution in an interBSC inter-cell handover are the same as those in a common intra-BSC inter-cell handover. The procedures on the core network (CN) side, however, are different. For details about the procedures on the BSC side, see 2.65.3.2 Common Intra-BSC Inter-Cell Handover. For details about the procedures on the CN side, see 3GPP TS 43.129 Packet-switched handover for GERAN A/Gb mode; Stage 2.

2G/3G inter-RAT handovers can be classified into inter-RAT handovers from GSM to UMTS and inter-RAT handovers from UMTS to GSM. Inter-RAT handover from GSM to UMTS is a handover in which the mobile terminal is handed over from a GSM cell to a UMTS cell. InterRAT handover from UMTS to GSM is a handover in which the mobile terminal is handed over from a UMTS cell to a GSM cell. If a PS handover from a GSM cell to a UMTS cell is required, Support Out Inter-RAT InterCell PS Handover should be set to SUPPORT. If a PS handover from a UMTS cell to a GSM cell is required, Support In Inter-RAT Inter-cell PS Handover should be set to SUPPORT. On the BSC side, the preparation procedure for an inter-RAT handover from GSM to UMTS is the same as that for a common intra-BSC inter-cell handover. The difference is that the PS
Handover Required message in an inter-RAT handover from GSM to UMTS contains the transparent container from the source BSC to the target RNC. The execution procedure for an inter-RAT handover from GSM to UMTS is the same as that for a common intra-BSC inter-cell handover. The difference is that the PS Handover Required Acknowledge message in an interRAT handover from GSM to UMTS contains the transparent container from the target RNC to the source BSC. For details, see 2.65.3.2 Common Intra-BSC Inter-Cell Handover. On the BSC side, the preparation and execution procedures for an inter-RAT handover from UMTS to GSM is the same as those for a common intra-BSC inter-cell handover. For details, see 2.65.3.2 Common Intra-BSC Inter-Cell Handover. On the CN side, the procedures for a 2G/3G inter-RAT handover are different from those for a common intra-BSC inter-cell handover. For details, see 3GPP TS 43.129 Packet-switched handover for GERAN A/Gb mode; Stage 2. For details about 2G/3G inter-RAT handover, see 2.4.3.4 2G/3G Inter-RAT Handover of 2.4 2G/3G Interoperability.
2.65.4 Parameters
The following describes the parameters related to PS handover. For the meaning of each parameter, see Table 2-188. For the default value, value range, and related MML commands of each parameter, see Table 2-189. Table 2-188 Parameter description (1) Parameter Description Whether to support the network assisted cell change (NACC). The NACC is used in the network control modes NC0, NC1 or NC2. The NACC enables the network to notify the MS of the system information of the neighboring cell when the MS is in the packet transmission state. In this way, the MS can reselect a cell in a shorter time. Network control mode for cell reselection of the MS. There are three modes. NC0: normal MS control. The MS shall perform autonomous cell re-selection. NC1: MS control with measurement reports. The MS shall send measurement reports to the network and the MS shall perform autonomous cell re-selection. NC2: network control. The MS shall send measurement reports to the network . The MS shall only perform autonomous cell re-selection when the reselection is triggered by a downlink signaling failure or a random access failure.When this parameter is set to NC2 and "Support NC2" in "SET GCELLGPRS" is set to "YES", the network side can control the cell reselection for the MS. Whether to support PS Handover(PS HO). The PS HO is used to reduce the interval of the cell reselection of the MS. Whether to support the network control 2 (NC2). The NC2 enables the network side to control the cell reselection for the MS when the MS reports the measurement report of the local cell and the neighboring cell.When this parameter is set to "YES" and "Network Control Mode" in "SET GCELLPSBASE" is set to "NC2", the network side can control the cell reselection for the MS.
Support NACC
Network Control Mode PS Handover Support
Support NC2
Issue 08 (2011-09-30)
Parameter Support Out Inter-RAT InterCell PS Handover Support In InterRAT Inter-cell PS Handover
Description Whether support Out Inter-RAT Inter-Cell PS Handover. The MS in the BSC local cell can be handed over to the UMTS cell through PS handover algorithm. Whether to support In Inter-RAT Inter-cell PS Handover. The MS in the UMTS cell can be handed over to the BSC local cell through PS handover algorithm.
Table 2-189 Parameter description (2) Paramete r Default Value GUI Value Range Actual Value Range Unit MML Comman d SET GCELLG PRS (Optional) Impact
Support NACC
NO
NO(No), YES(Yes) NC0 (NC0), NC1 (NC1), NC2 (NC2) NO(No Support), YES (Support)
NO, YES
None
Cell
Network Control Mode PS Handover Support
NC0
NC0, NC1, NC2
None
Cell
NO
NO, YES
None
ADD NSE (Optional) SET GCELLG PRS (Optional)
NSE
Support NC2 Support Out InterRAT InterCell PS Handover Support In Inter-RAT Inter-cell PS Handover
NO
NO(No), YES(Yes) UNSUPP ORT(Not Support), SUPPOR T (Support) UNSUPP ORT(Not Support), SUPPOR T (Support)
NO, YES
None
Cell
UNSUPP ORT
None
Cell
UNSUPP ORT
None
Cell
Issue 08 (2011-09-30)
1098
2.65.5 Counters
2.65.6 Glossary

l l l l l l l l l l l 3GPP TS 43.129: Packet-switched handover for GERAN A/Gb mode; Stage 2 3GPP TS 48.018: BSC GPRS Protocol (BSCGP) 3GPP TS 44.060: Radio Link Control/Medium Access Control (RLC/MAC) protocol BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference NACC Parameter Description NC2 Parameter Description
2.66 RAN Sharing

2.66.1 Introduction
2.66.1.1 Scope
This document describes the networking scenarios, operation and maintenance system, and related network elements (NEs) for RAN sharing.

Issue 08 (2011-09-30)

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the RAN Sharing feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.66.2 Overview
With the increasingly fierce competition in the radio communications market, reducing the operation expenditure (OPEX) becomes a major concern for operators during network deployment. Network deployment in different phases has different characteristics. In the initial phase, there are only a few subscribers, and thus the investment recovery period is long. In the later phase, with the introduction of new technologies, the original equipment may be replaced and thus equipment resources are wasted. In addition, network deployment has limitations in
different areas. In urban areas, difficult site acquisition and complex site construction increase the OPEX. In rural areas, the equipment utilization is likely to be low, though site construction is relatively easy. It will be desirable if operators at different phases of network deployment can share network resources, thus maximizing the capital utilization. To achieve this, RAN Sharing is introduced. The network resources mainly refer to the sites, transmission resources, feeders, base stations, and base station controllers. RAN Sharing supports the coexistence of shared resources with non-shared resources. Some resources in an operational network may be exclusive to an operator while others can be shared among several operators. For example, all the resources under a certain BTS belong to a specific operator and other operators cannot use these resources, whereas the resources under another BTS may be used by multiple operators. RAN Sharing enables multiple operators to share the network resources on the BSS side while keeping their own subscribers and services. Technically, RAN Sharing is a technology using which a set of physical GBSS equipment is split into multiple subsets of logical GBSS equipment. In this way, the same set of physical GBSS equipment can be shared by multiple operators to cover the same area. Operators have their respective frequency resources. Therefore, different operators can use different cells under the same BTS, but a cell belongs to only one operator. When an MS in a cell accesses the network, the BSC determines the operator to which the MS belongs and routes the MS to the core network (CN) of the operator. The services involved in RAN Sharing include both CS and PS services. According to the mapping between the CNs and the cells, the GBSS equipment routes the services in a cell to a specific CN for processing. For mature operators, RAN Sharing makes it possible to reuse the equipment. For new operators, RAN Sharing enables them to enter the market quickly and decreases the network deployment period. That is, RAN Sharing enables operators to save OPEX, share network resources, and thus achieve a win-win situation. The benefits of RAN Sharing are as follows: l l l RAN Sharing helps save the CAPEX and OPEX. Multiple operators share networks to achieve maximum network coverage. RAN Sharing enables new operators to quickly deploy network and increase the market share.
Figure 2-283 shows the RAN Sharing networking.
Issue 08 (2011-09-30)
1101
Figure 2-283 RAN Sharing networking
In the current networking mode of RAN Sharing, the CN is not shared by operators. Each Mobile Switching Center (MSC) or Serving GPRS Support Node (SGSN) belongs to only one operator.

2.66.3.1 Networking Scenario Analysis Coexistence of BSC Supporting RAN Sharing with BSC Not Supporting RAN Sharing Under Full Coverage
As shown in Figure 2-284, operator A and operator B have independent coverage areas. In addition, they achieve full coverage in other areas through the shared GBSS network equipment. Through the configuration of neighboring cells, an MS of operator A can be handed over from a cell under BSC A to a cell of operator A under shared BSC 1 or BSC 2; an MS of operator B can be handed over from a cell under BSC B to a cell of operator B under shared BSC 1 or BSC 2.
Issue 08 (2011-09-30)
1102
Figure 2-284 Coexistence of shared BSCs with non-shared BSCs under full coverage
Coexistence of BSC Supporting RAN Sharing with 3G Network

As shown in Figure 2-285, operator A and operator B have independent 3G networks. In some areas, the GSM network is still required to complement the 3G network coverage. Operator A and operator B share the 2G network equipment to reduce the operation costs. Operator A can ensure the service continuity of an MS in its own network. The same situation applies to operator B. In this networking scenario, 3G network operators who do not have 2G network equipment can lease equipment from 2G network operators to complement the 3G network coverage. Figure 2-285 Coexistence of shared BSC with 3G network
Coexistence of Full Coverage Network with Partial Coverage Network

As shown in Figure 2-286, the GSM network of operator A provides full coverage, whereas the GSM network of operator B provides only partial coverage. To achieve full coverage, operator B must use the equipment shared by operator A and enable the handover between cells of its own network and cells of operator A's network. In this networking scenario, an MS of operator B can access the network of operator A through handover or cell reselection and use the A interface resources of operator A. When moving to the area covered by the networks of operator A and operator B, the MS can return to operator B's cell and use the network resources of operator B.
In this case, both operator A and operator B should set Handover Between Operators Allow to Yes and configure neighboring relations between their cells. Figure 2-286 Coexistence of full coverage network with partial coverage network
2.66.3.2 Operation and Maintenance System

RAN sharing enables a maximum of four operators to share the same radio access network while keeping their independent core networks (CNs). The shared GBSS equipment uses the same primary operation and maintenance system, which performs integrated management of al the resources under the GBSS equipment. The primary operation and maintenance system can be connected to the network management systems of different operators through the northbound interface. Through its own network management system, an operator can perform the following operations on a per cell basis: setting the cell-level parameters, enabling or disabling the celllevel features, and performing the cell-level performance management, log management, and alarm management. Non-cell-level parameter settings and performance management are performed through the primary operation and maintenance system. Figure 2-287 shows the operation and maintenance network structure after RAN sharing is introduced. Figure 2-287 Operation and maintenance network structure after RAN sharing is introduced
Issue 08 (2011-09-30)
1104
In RAN sharing mode, operators are classified into two types. The type of operator is specified by Operator Type. l Primary operator The primary operator has the administrative rights to operate and maintain the system. The operator is responsible for adding secondary operators and configuring the function parameters for the secondary operators. Operator Index of the primary operator must be set to 0. l Secondary operator The primary operator must be specified before RAN Sharing is enabled at the BSC. In addition, all the resources of the BSC belong to the primary operator.When Support RAN Sharing is set to Yes, a secondary operator can be added to the shared GBSS equipment, and the related resources can be allocated to the secondary operator. Before setting Support RAN Sharing to No, you should delete the information about all secondary operators. A maximum of three secondary operators are supported. The value of Operator Index for a secondary operator ranges from 1 to 3. Each operator is identified by a unique PLMN ID, that is, MCC + MNC. On the shared GBSS equipment, operators can also be identified by Operator Name.
2.66.3.3 Network Elements MSC

In RAN Sharing mode, one MSC belongs to only one operator, which is identified by Operator Name. Each MSC is identified by DSP name corresponding to only one Operator Name. Currently, one operator has only one MSC.
SGSN
In RAN Sharing mode, one SGSN belongs to only one operator. Each SGSN is identified by SGSN Node ID corresponding to only one Operator Name. Currently, one operator has only one SGSN.
PCU
In RAN Sharing mode, one external PCU belongs to only one operator. One operator, however, can have multiple external PCUs. Each external PCU is identified by PCU Name or PCU No. corresponding to only one Operator Name.
BTS
In RAN Sharing mode, the BTS is the lowest-level NE shared by operators. If the primary operator does not share its BTS with a secondary operator, it can set Sharing Allow to No to have the sole use of the BTS. Before setting Sharing Allow to No, ensure that all the cells under the BTS belong to the primary operator.
Cell
In RAN Sharing mode, one cell belongs to only one operator. Each cell is identified by Cell Name or Cell Index corresponding to only one Operator Name. When changing the operator of a cell, delete the neighboring relations of this cell if it is configured with neighboring cells. If a cell is an external cell and the corresponding BTS does not adopt RAN Sharing, this cell can only be a neighboring cell of the primary operator's cells. If a cell is an external cell and the corresponding BTS adopts RAN Sharing, the cell is identified by Cell Name or Cell Index corresponding to only one Operator Name. Two cells belonging to different operators cannot be configured as enhanced dualband cells.
2.66.3.4 Functions System Information Broadcast

One cell belongs to only one operator. Therefore, the system information broadcast on the BCCH of the cell carries the information about the PLMN of only the operator to which the cell belongs. The MSs of different operators listen to the system information and determine the cell that they can access according to the PLMN carried in the system information.
Paging
When the CN initiates a paging, the paging area can be a cell, a location area, or the whole coverage area of the BSC. In RAN Sharing mode, the paging message sent by the CN of a specific operator is broadcast in only the cells of this operator.
Call Access
When an MS attempts to access the network, the BSC determines the operator based on the cell on which the MS camps and routes the MS to the operator's CN.
Handover
RAN Sharing supports a handover from the 2G cell of one operator to the 2G or 3G cell of another operator. If Handover Between Operators Allow is set to Yes in both the originating cell and the target cell, the MS can be handed over between the two cells, though these two cells belong to different operators. If an MS is handed over between two cells of two operators under the same BSC, the inter-BSC handover procedure is performed, and outgoing BSC handover signaling and incoming BSC handover signaling can be traced on the A interface. If Handover Between Operators Allow is set to No, a cell can have unidirectional or bidirectional neighboring relations with all the other cells belonging to the same operator. If Handover Between Operators Allow is set to Yes, a cell of this operator can have unidirectional or bidirectional neighboring relations with all the cells belonging to another operator of which Handover Between Operators Allow is also set to Yes.
Cell Broadcast
A cell broadcast center (CBC) can be either owned by an operator or shared by multiple operators. The relation between a CBC and an operator is specified by CBC INDEX and OP INDEX SET. A maximum of four CBCs can be connected to a BSC where RAN Sharing is enabled. If RAN Sharing is enabled and Support Cell Broadcast is set to SPPRTSTANDARD(Support Standard CB), different operators can use different CBCs. In this case, the BSC is connected to multiple CBCs. Before changing Support Cell Broadcast from SPPRTSTANDARD (Support Standard CB) to another value, delete the relation between the operator and the CBC. Each operator provides cell broadcast short message services in its cells.
Flow Control
The flow control in the BSC is performed on a per BSC basis.
Local Switching
The local switching function is performed on a per BSC basis.
Abis Transmission Resources

If Flex Abis, HDLC transmission optimization, or IP transmission is applied on the Abis interface, the Abis interface transmission resources are shared among cells on a first-come, firstserved basis.
Functions That Can Be Separately Controlled by Operators

Operators can control certain functions separately by setting the parameters at different levels. l l l l TRX-level parameters: Different TRXs have different TRX-level parameters. Operators can control the related functions separately by setting different TRX-level parameters. Cell-level parameters: Different cells have different cell-level parameters. Operators can control the related functions separately by setting different cell-level parameters. BSC-level parameters: The BSC-level parameters take effect for the networks of all operators. MSC-level parameters: The settings of some A interface parameters depend on the settings of the corresponding parameters on the MSC side. Operators can set different parameters on the MSC side for proper interconnection. Operator-level parameters: Different operators have different operator-level parameters.
Table 2-190 Functions related to RAN Sharing Functions Multi-transceiver unit in PBT transmit mode Multi-transceiver unit in transmit diversity mode Multi-transceiver unit
Issue 08 (2011-09-30)
Effective Level TRX TRX TRX

1107
Functions Multi-transceiver unit in four-way receive diversity Dynamic PBT Dynamic Transmit Diversity eMLPP 2G/3G Interoperability GBR QoS TCH HR/FR Adaptation NACC NC2 Network Operation Mode I Packet Power Control 2G/3G Inter-RAT Load Handover Extended Cell BSS Local Switching Soft-Synchronized Network A over IP Abis Transmission Optimization Flow Control Location Service Cell Broadcast
Effective Level TRX TRX TRX Cell Cell Cell Cell Cell Cell Cell Cell Cell Cell BSC BSC BSC BSC BSC MSC Operator
NOTE
For details of PBT, see 2.62 PBT. For details of transmit diversity, see 2.73 Transmit Diversity. For details of four-way receive diversity, see 2.39 Four-Way Receive Diversity.

The limitations on RAN Sharing are as follows: l l
Issue 08 (2011-09-30)
RAN Sharing supports a maximum of four operators, including the primary operator. RAN Sharing supports a maximum of four CBCs.
l l
With or without RAN Sharing, the DPC of the SS7 signaling and the total number of SGSNs remain unchanged. Operators must adopt the same configuration mode (BM/TC separated, BM/TC combined, or A over IP) in their networks. As a result, operators must adopt the same transmission mode (TDM or IP) on the A interface. The MSCs of RAN-Sharing operators must use the same type of bit rate for signaling link. The equipment of all RAN-Sharing operators must be connected to the same M2000, and the information about all alarms and performance counters can be viewed on the M2000. Such information is not displayed on a per operator basis. The BSC clock of one operator is used as the reference clock for all the other BSCs of RAN-Sharing operators. Operators must ensure the clock synchronization among the MSCs. If an NSE and a cell belong to different operators, a PTP BVC cannot be configured between them. The operation and maintenance or dynamic modification of data configuration by one operator may affect the services of other operators. The DPUa is shared among operators. All the PCUs must be external PCUs or built-in PCUs. In the case of external PCU, each PCU should be exclusively used by an operator.
l l
l l l l
2.66.5 Parameters
This chapter describes the parameters related to RAN Sharing. For the meaning of each parameter, see Table 2-191. For the default value, value ranges, and MML commands of each parameter, see Table 2-192. Table 2-191 Parameter description (1) Parameter Handover Between Operators Allow Description Whether to allow handover between different operators. If the BSC6900 supports RAN sharing, MSs in a cell of this operator can be handed over to a cell of other operators, or vice versa. Whether to support RAN Sharing.RAN sharing refers to the technique that the GBSS equipment is categorized into multiple logical GBSS equipment, thus operators can share the GBSS equipment to cover the same area. Name of the operator. This parameter uniquely identifies an operator. Whether to allow sharing. Operator index set to which the CBC belongs. Primary operator or secondary operator. Primary operator is an operator that provides equipment, whereas secondary operator is an operator that leases equipment. Index of the operator.
Support RAN Sharing Operator Name Sharing Allow OP INDEX SET
Operator Type Operator Index
Issue 08 (2011-09-30)
1109
Table 2-192 Parameter description (2) Paramete r Handover Between Operators Allow Support RAN Sharing Default Value GUI Value Range Actual Value Range Unit MML Command Impac t
NO
NO(No), YES(Yes) NO(No), YES(Yes)
NO, YES
None
ADD GCNOPERATOR (Optional) SET BSCBASIC (Optional) ADD GCNNODE (Mandatory) ADD GCNOPERATOR (Mandatory) ADD GCELL(Optional) ADD GEXTSMLC (Mandatory) ADD GEXT2GCELL (Optional) ADD GEXT3GCELL (Optional) ADD NSE(Mandatory) ADD SGSNNODE (Mandatory) ADD NRISGSNMAP (Mandatory) ADD PCU(Mandatory) SET BTSSHARING (Optional)
BSC
NO
NO, YES
None
BSC
Operator Name Sharing Allow
None
None NO(NO), YES (YES) OPINDE X0, OPINDE X1, OPINDE X2, OPINDE X3 PRIM (Primary Operator), SEC (Secondar y Operator)
0~255 characters
None
BSC
NO
NO, YES OPINDE X0, OPINDE X1, OPINDE X2, OPINDE X3
None
BTS
OP INDEX SET
None
None
ADD GCBSADDR (Mandatory)
BSC
Operator Type
None
PRIM, SEC
None
ADD GCNOPERATOR (Mandatory)
BSC
Issue 08 (2011-09-30)
1110
Paramete r Operator Index
Default Value
GUI Value Range 0~3
Actual Value Range 0~3
Unit
MML Command CMP LICENSE (Optional)
Impac t
None
None
None
2.66.6 Counters
2.66.7 Glossary

l l l l l l BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.67 Robust Air Interface Signaling

2.67.1 Introduction
2.67.1.1 Scope
This document describes the implementation of Repeated Downlink FACCH and Repeated SACCH and impacts of Repeated Downlink FACCH and Repeated SACCH on KPIs.

Issue 08 (2011-09-30)

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the robust air interface signaling feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.67.2 Overview
On the network with tight frequency reuse and poor radio transmission performance, the messages sent through the FACCH frames or the SACCH frames may be lost because of the high bit error rate on the Um interface. To solve this problem, the Robust Air Interface Signaling feature is introduced. Based on this feature, FACCH frames and SACCH frames are repeatedly sent to improve the anti-interference performance of the FACCH link and SACCH link and to increase the possibility of successfully receiving the signaling messages by the MS and BSC. Robust Air Interface Signaling provides the following functions:
Repeated Downlink FACCH When the receive quality in the downlink measurement report is lower than the specified threshold, the BTS determines whether to retransmit the FACCH frames if the MS supports the Repeated Downlink FACCH function. The repeated transmission of downlink FACCH frames increases the possibility of successfully receiving the signaling messages by the MS.
Repeated SACCH If the BTS fails to decode the SACCH frame correctly, it instructs the MS to retransmit the last SACCH frame if the MS supports the Repeated SACCH function. If the MS fails to decode the SACCH frame correctly, it instructs the BTS to retransmit the last SACCH frame.
The signaling messages are sent through stolen frames. Thus, this feature slightly affects the voice quality. When the radio quality is poor, repeated transmission of signaling messages in the downlink can reduce call drops caused by decoding failure; repeated transmission of signaling messages in the uplink can increase the accuracy of the handover decision and power control decision of the BSC by increasing the possibility of correctly decoding the uplink measurement reports. Robust Air Interface Signalling brings the following benefits: l Repeated transmission of FACCH frames improves the FACCH link performance of the common MS by 2 dB and the FACCH link performance of the MS in R6 version by 4 dB to 5 dB. Repeated transmission of SACCH frames improves the SACCH link performance of the common MS by 4 dB to 5 dB. The improvement in the FACCH and SACCH performance reduces call drops and increases the accuracy of the handover decision and power control decision of the BSC.
l l

2.67.3.1 Repeated Downlink FACCH
?.1. Overview
During a call process, many messages must be sent on the FACCH, for example, messages in the Voice Group Call Service(VGCS) notification procedure, Dual Tone Multi-Frequency (DTMF) protocol control procedure, and handover procedure. Especially for the handover command in the handover procedure, it must be received and correctly decoded by the MS so that the handover can be performed successfully because it contains the description of the target cell and the encryption information of the current service. After the Repeated Downlink FACCH function is enabled, the BTS retransmits the downlink FACCH frame to the MS to increase the probability of correctly transmitting messages on the downlink FACCH.
?.2. Implementation in the BSS

The implementation of Repeated Downlink FACCH in the BSS is as follows:
1. 2.
The parameter Repeated Downlink FACCH is set to Yes so that the cell supports Repeated Downlink FACCH. When activating the full-rate channel or half-rate channel, the BTS obtains the Repeated ACCH Capability bit information from the MS by decoding the Repeated ACCH Capability in the Channel Active information element, that is, the capability of the MS to support Robust Air Interface Signaling.
NOTE
If the value of Repeated ACCH Capability bit is 0, the BSS can retransmit only the FACCH command frame.
3.
The BTS compares the receive quality contained in the downlink measurement report with the Repeated Downlink FACCH Threshold to determine whether to retransmit the FACCH frame.
?.3. Impact on the KPI

The impact of Repeated Downlink FACCH on the KPI is as follows: l When the C/I ratio is low or fluctuates greatly, Repeated Downlink FACCH helps reduce call drops due to the failure of the MS in decoding the handover command and improve the handover success rate. Repeated Downlink FACCH has little impact on voice quality.
2.67.3.2 Repeated SACCH

?.1. Overview
The AMR FR speech frame is more robust than the SACCH frame. Therefore, if the AMR function is enabled, before user hook-on due to poor voice quality, call drops may occur because of a signaling transmission failure on the SACCH. After Repeated SACCH is enabled, the MS or BTS may retransmit the SACCH frame, thus increasing the success rate of message transmission to the peer end. Repeated SACCH applies to the scenarios where the AMR function is enabled.
NOTE
After the AMR function is enabled, the call drop rate on the TCH may increase. For details, see 2.9.3.6 Impact on KPI in 2.9 AMR.
?.2. Implementation in the BSS

The implementation of Repeated SACCH in the BSS is as follows: 1. 2. The parameter Repeated SACCH is set to Yes so that the cell supports Repeated SACCH. When activating the full-rate channel or half-rate channel, the BTS obtains the capability of the MS to support Robust Air Interface Signaling by decoding the Repeated ACCH Capability in the Channel Active information element. Repeated SACCH is triggered in the following case:
3.
Issue 08 (2011-09-30)
l If the BTS fails to decode the SACCH frame correctly, it sets the SACCH Repetition Order(SRO) in the downlink SACCH to 1 and instructs the MS to retransmit the last SACCH frame. l If the MS fails to decode the SACCH frame correctly, it sets the SACCH Repetition Request(SRR) in the uplink SACCH frame to 1 and requests the BTS to retransmit the message on the SACCH. Table 2-193 lists the values of the SRR and SRO. Table 2-193 Values of the SRR and SRO Value 0 1 Description Repeated SACCH not required Repeated SACCH required
?.3. Impact on the KPI

The impact of Repeated SACCH on the KPI is as follows: l l l Repeated SACCH reduces call drops due to timeout of the radio link timer. Repeated SACCH increases the possibility of correctly interpreting the uplink measurement reports, thus increasing the accuracy of handover decision. Enabling Repeated SACCH when the C/I ratio is low makes power control more effective.

Repeated Downlink FACCH
Repeated Downlink FACCH applies to the scenarios where the tight frequency reuse pattern is used and the bit error rate on the Um interface is high.
Repeated SACCH
Repeated SACCH applies to the scenarios where the AMR function is enabled.
2.67.5 Parameters
This chapter describes the parameters related to robust air interface signaling. For the meaning of each parameter, see Table 2-194. For the default value, value ranges, and MML commands of each parameter, see Table 2-195.
Issue 08 (2011-09-30)
1115
Table 2-194 Parameter description (1) Parameter Repeated Downlink FACCH Repeated Downlink FACCH Threshold Repeated SACCH Description When the cell supports Repeated Downlink FACCH, the BTS enables the repeated transmission of FACCH frames if the measured downlink quality is higher than "Repeated Downlink FACCH Threshold". If the cell supports the Repeated Downlink FACCH function and the measured downlink quality is lower than the downlink quality threshold, the BTS enables the repeated transmission of FACCH frames. When the cell supports Repeated Downlink SACCH, the BTS enables the repeated transmission of SACCH frames if the measured downlink quality is higher than the downlink quality threshold.
Table 2-195 Parameter description (2) Paramete r Repeated Downlink FACCH Repeated Downlink FACCH Threshold Repeated SACCH Default Value GUI Value Range NO(No), YES(Yes) Actual Value Range Uni t MML Command SET GCELLCCBASIC (Optional) SET GCELLCCBASIC (Optional) SET GCELLCCBASIC (Optional) Impact
NO
NO, YES
Non e
Cell
0~7
Non e Non e
Cell
NO
NO, YES
Cell
2.67.6 Counters
2.67.7 Glossary

l 3GPP TS 44.001 "Mobile Station - Base Station System (MS - BSS) Interface General Aspects and Principles"
Issue 08 (2011-09-30)
l l l l l l l l l l l l l
3GPP TS 44.003 "Mobile Station - Base Station System (MS - BSS) interface Channel structures and access capabilities" 3GPP TS 44.004 "Layer 1 General requirements" 3GPP TS 44.005 "Data Link (DL) layer General aspects" 3GPP TS 24.007 "Mobile radio interface signalling layer 3; General aspects" 3GPP TS 44.018 "Mobile radio interface layer 3 specification; Radio Resource Control Protocol" 3GPP TS 45.002 "Multiplexing and multiple access on the radio path" 3GPP TS 48.056 "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 2 specification" 3GPP TS 48.058 "Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 3 specification" BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.68 Semipermanent Connection

2.68.1 Introduction
2.68.1.1 Scope
This document describes the definition of semipermanent connection and its implementation.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l
Issue 08 (2011-09-30)
Feature change
Feature change refers to the change in the semipermanent connection feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.68.2 Overview
The semipermanent link enables some of the idle E1 timeslots in the BSS system to be used to provide transmission paths for subscribers. The paths are used to transmit information such as business hall information, alarm information on the BTS AC power supply, and other maintenance information. When the telecom operator needs to transmit some data from one terminal in the BSS system to another terminal and the data does not have a high requirement for the transmission bandwidth, the idle transmission resources in the BSS system can be configured as the semipermanent link for transferring these data. The semipermanent link enables telecom operators to fully utilize the network resources and minimize the operation cost.

In certain situations, the telecom operator may require the BSS to provide semipermanent connections for transmitting information such as business hall information, alarm information on the BTS AC power supply, and other maintenance information.
Figure 2-288 shows a semipermanent connection between the BTS and the A interface. A semipermanent connection consists of the following links: l l l Monitoring timeslot between the Ater interface board in the BM subrack and the BTS Ater connection path between the BM subrack and the TC subrack (transmission path between the MPS/EPS and the TCS, used for traffic and signaling transmission) Semipermanent link between the Ater interface board in the GTCS and the A interface
Figure 2-288 Semipermanent connection in the BSS
In the BSS, semipermanent link and monitoring timeslot are collectively called semipermanent connection. l The semipermanent link refers to the link configured on both sides of the TNUa board. That is, the BSC interface boards work as the input and output of the semipermanent connection, and the TNUa board performs information exchange. The monitoring timeslot refers to the link between the BSC interface board and the BTS.
NOTE
Based on actual requirements, the input port and output port can be different ports on the same interface board.
2.68.3.1 Semipermanent Connection

The components involved in a semipermanent connection are the transparent transmission interface board (that is, any interface board supporting TDM switching), TNUa, Abis interface board, and BTS interface board. In traditional TDM transmission mode, the BSS must reserve a timeslot (the timeslot is not used to transmit traffic signals or signaling) on the transparent transmission interface board, on the TNUa, on the Abis interface board, and on the E1 link between the Abis interface board and the BTS interface board to establish a semipermanent connection from the BTS to the A interface. The BSS connects the reserved timeslots one by one to form a connection path. Figure 2-289 takes the EIUa as an example to show a semipermanent connection. Figure 2-289 Semipermanent connection (in TDM transmission mode)
Issue 08 (2011-09-30)
1119
In Abis transmission optimization mode, the physical links are established by connecting a timeslot on one port of the PEUa to a timeslot on another port, and then by using E1 cables to connect the ports of the PEUa and EIUa. Other links in Abis transmission optimization mode are established in the same way as in TDM transmission mode. Figure 2-290 shows a semipermanent connection in Abis transmission optimization mode. Figure 2-290 Semipermanent connection (in Abis transmission optimization mode)
NOTE
l The PEUa is the BSC interface board that supports Abis transmission optimization. l The transparent transmission interface board is only responsible for transparently transmitting signals. It can be configured as an output-only board, an input-only board, or a board for both input and output. All interface boards that support TDM transmission can serve as transparent transmission interface boards.
2.68.3.2 Implementation of Semipermanent Connection

This describes the implementation of Semipermanent Connection in different physical entities.
Implementation of Semipermanent Connection in the Interface Board

The connection between the E1 timeslot of the BSC interface board and the high way (HW) timeslot of the TNUa is pre-established by the BSC without manual configuration. The BSC interface board supports semipermanent links of the following data rates: 8 kbit/s, 16 kbit/s, 32 kbit/s, and 64 kbit/s. Semipermanent links cannot be configured between the MPS/EPS and the TCS.
Implementation of Semipermanent Connection in the BTS

The BTS interface board can transparently transmit the monitoring timeslot signals from one port to any other port. In addition, the BTS interface board can transparently transmit the monitoring timeslot signals to the incoming E1 timeslot of a lower-level BTS. In this manner, the semipermanent connection of cascaded BTSs is implemented.
Implementation of Semipermanent Connection in the TNUa

A connection is established between the timeslot of the semipermanent connection on one BSC interface board and the input port on the TNUa. In addition, another connection is established between the timeslot of the semipermanent connection on another BSC interface board and the output port on the TNUa. The TNUa establishes a connection between these connections based on relevant timeslots. Thus, a semipermanent connection is established between the transparent transmission interface board and another interface board or a BTS.
After the semipermanent connection is configured, timeslot cross connection equipment should be installed at both ends of the physical link. The equipment extracts the required timeslots to transmit signals.

Configuring a Monitoring Timeslot
This describes how to configure a BTS monitoring timeslot on the BSC. The parameters InBSC Subrack No., In-BSC Slot No., In-BSC Port No., In-BSC Timeslot No., and In-BSC Sub Timeslot No. specify the subrack number, slot number, port number, timeslot number, and sub-timeslot of the BSC interface board to which the central monitoring device is connected. The parameters Out-BTS Port No., Out-BTS Timeslot No., and Out-BTS Sub Timeslot No. specify the port number, timeslot number, and sub-timeslot number of the BTS to which the monitoring device is connected. You can set the parameter Time Slot Rate according to the actual bandwidth requirement. Figure 2-291 shows the typical signal flow of a monitoring timeslot. Figure 2-291 Typical signal flow of a monitoring timeslot
The BSS supports four data rates of BTS monitoring timeslots: 8 kbit/s, 16 kbit/s, 32 kbit/s, and 64 kbit/s. The default data rate of a BTS monitoring timeslot is 64 kbit/s. l l l l If the data rate of a BTS monitoring timeslot is 64 kbit/s, In-BSC Sub Timeslot No. and Out-BTS Sub Timeslot No. must be set to 0. If the data rate of a BTS monitoring timeslot is 32 kbit/s, In-BSC Sub Timeslot No. and Out-BTS Sub Timeslot No. must be set to 0 or 4. If the data rate of a BTS monitoring timeslot is 16 kbit/s, In-BSC Sub Timeslot No. and Out-BTS Sub Timeslot No. must be set to 0, 2, 4, or 6. If the data rate of a BTS monitoring timeslot is 8 kbit/s, In-BSC Sub Timeslot No. and Out-BTS Sub Timeslot No. can be set to any allowable values.
The BSC interface board connected to the central monitoring device can be any type of interface board in the MPS/EPS. The inner-BSC path corresponding to the monitoring timeslot is
automatically specified by the BSC. On the Abis interface, the system automatically allocates an idle timeslot to transmit the monitoring signals.
NOTE
Configuring a BTS monitoring timeslot may reset the BTS. It is recommended that the BTS monitoring timeslot be preconfigured.
Configuring a Semipermanent Link

You can configure a semipermanent link between the BSC interface boards. The parameter Semipermanent Link Index identifies a semipermanent link. You can set the parameter Semipermanent Link Rate according to the actual bandwidth requirement. The parameters InBSC Subrack No., In-BSC Slot No., In-BSC Port No., In-BSC Timeslot No., and In BSC Start Timeslot No. determine the timeslot configurations at one end of a semipermanent link. The parameters Out BSC Subrack No., Out BSC Slot No., Out BSC Port No. and Out BSC Start Timeslot No. determine the timeslot configurations at the other end of the semipermanent link. Figure 2-292 shows the typical signal flow of a semipermanent link. Figure 2-292 Typical signal flow of a semipermanent link
The BSS supports four data rates of semipermanent links: 8 kbit/s, 16 kbit/s, 32 kbit/s, and 64 kbit/s. The default data rate of a semipermanent link is 64 kbit/s. l l l l If the data rate of a semipermanent link is 64 kbit/s, In BSC Start Timeslot No. and Out BSC Start Timeslot No. must be set to 0. If the data rate of a semipermanent link is 32 kbit/s, In BSC Start Timeslot No. and Out BSC Start Timeslot No. must be set to 0 or 4. If the data rate of a semipermanent link is 16 kbit/s, In BSC Start Timeslot No. and Out BSC Start Timeslot No. must be set to 0, 2, 4, or 6. If the data rate of a semipermanent link is 8 kbit/s, In BSC Start Timeslot No. and Out BSC Start Timeslot No. can be set to any allowable values.
Issue 08 (2011-09-30)
1122

NOTE
l The semipermanent link must be configured between the same type of subracks. That is, both the subracks must be the MPS/EPS or TCS, and a semipermanent link cannot be configured between the MPS/EPS and the TCS. l The semipermanent link must be configured on the interface boards. The input port and output port of a semipermanent link cannot be the same. l If an E1 link is configured with a 16 kbit/s LAPD signaling link, the data rate of the semipermanent link on this E1 link must be 16 kbit/s.
2.68.5 Parameters
This chapter describes the parameters related to semipermanent connection. For the meaning of each parameter, see Table 2-196. For the default value, value ranges, and MML commands of each parameter, see Table 2-197. Table 2-196 Parameter description (1) Parameter In-BSC Subrack No. In-BSC Slot No. In-BSC Port No. In-BSC Timeslot No. Description In-BSC6900 subrack No. of the monitoring timeslot. In-BSC6900 slot No. of the monitoring timeslot. In-BSC6900 port No. of the monitoring timeslot. In-BSC6900 timeslot No. of the monitoring timeslot. In-BSC6900 sub-timeslot No. of the monitoring timeslot. If the added monitoring timeslot works at 64 kbit/s, the subtimeslots are numbered from 0. If the added monitoring timeslot works at 32 kbit/s, the sub-timeslots are numbered from 0 or 4. If the added monitoring timeslot works at 16 kbit/s, the sub-timeslots are numbered from 0, 2, 4, or 6. If the added monitoring timeslot works at 8 kbit/s, the subtimeslots are numbered from any value among 0 to 7. Number of the outgoing port of the BTS where the monitoring timeslot is located. Number of the timeslot on the outgoing port of the BTS. Number of the sub-timeslot on the outgoing port of the BTS. Rate of the monitoring timeslot. Incoming BSC6900 start timeslot number. Outgoing BSC6900 subrack number. Outgoing BSC6900 slot number. Outgoing BSC6900 port number. Outgoing BSC6900 start timeslot number.
In-BSC Sub Timeslot No. Out-BTS Port No. Out-BTS Timeslot No. Out-BTS Sub Timeslot No. Time Slot Rate In BSC Start Timeslot No. Out BSC Subrack No. Out BSC Slot No. Out BSC Port No. Out BSC Start Timeslot No.
Issue 08 (2011-09-30)
1123
Table 2-197 Parameter description (2) Parameter Defau lt Value GUI Value Range Actual Value Range Un it MML Com mand ADD BTSM ONIT ORTS (Mand atory) ADD BTSM ONIT ORTS (Mand atory) ADD BTSM ONIT ORTS (Mand atory) ADD BTSM ONIT ORTS (Mand atory) ADD BTSM ONIT ORTS (Mand atory) ADD BTSM ONIT ORTS (Mand atory) ADD BTSM ONIT ORTS (Mand atory) Impac t
In-BSC Subrack No.
None
0~11
0~11
No ne
BTS
In-BSC Slot No.
None
0~27
0~27
No ne
BTS
In-BSC Port No.
None
0~335
0~335
No ne
BTS
In-BSC Timeslot No.
None
1~31
1~31
No ne
BTS
In-BSC Sub Timeslot No.
None
0~7
0~7
No ne
BTS
Out-BTS Port No.
None
0~23
0~23
No ne
BTS
Out-BTS Timeslot No.
None
1~31
1~31
No ne
BTS
Issue 08 (2011-09-30)
1124
Parameter
Defau lt Value
GUI Value Range
Actual Value Range
Un it
MML Com mand ADD BTSM ONIT ORTS (Mand atory) ADD BTSM ONIT ORTS (Mand atory) ADD SEMIL INK (Mand atory) ADD SEMIL INK (Mand atory) ADD SEMIL INK (Mand atory) ADD SEMIL INK (Mand atory) ADD SEMIL INK (Mand atory)
Impac t
Out-BTS Sub Timeslot No.
None
0~7
0~7
No ne
BTS
Time Slot Rate
None
8K(8K), 16K(16K), 32K(32K), 64K(64K)
8K, 16K, 32K, 64K
kbi t/s
BTS
In BSC Start Timeslot No.
None
0~255
0~255
No ne
BSC
Out BSC Subrack No.
None
0~11
0~11
No ne
BSC
Out BSC Slot No.
None
0~27
0~27
No ne
BSC
Out BSC Port No.
None
0~335
0~335
No ne
BSC
Out BSC Start Timeslot No.
None
0~255
0~255
No ne
BSC
2.68.6 Counters
None.
Issue 08 (2011-09-30)
1125
2.68.7 Glossary

l l l l BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.69 SGSN Pool

2.69.1 Introduction
2.69.1.1 Scope
This document describes routing of an MS to an SGSN, SGSN selection based on load balancing algorithm, and load adjustment in an SGSN Pool in the SGSN Pool feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the SGSN pool feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Version
l l
02 (2009-09-30) 01 (2009-06-30)
02 (2009-09-30)
01 (2009-06-30)
2.69.2 Overview
SGSN Pool, also known as Gb Flex, enables multiple SGSNs to form a SGSN pool. A BSC belonging to an SGSN pool area is connected to all SGSNs in the related SGSN pool. The resources and load are shared by all the SGSNs in the pool, thus balancing the traffic load and reducing inter-SGSN handovers. According to 3GPP 23.236-630, the functions of SGSN Pool are as follows: l l When more SGSN capacity is required, the SGSNs can be added without the replanning of the radio network. Therefore, a lot of configuration efforts can be avoided. The SGSN Pool feature supports SGSN redundancy. If an SGSN in the SGSN pool is faulty, the remaining SGSNs will keep serving the MSs located within the SGSN pool area. In a non-pooled case, the complete SGSN service area is lost in case of an SGSN failure. An SGSN in the SGSN pool serves all the routing areas (RAs) in the SGSN pool area. This means that no inter-SGSN RA update is needed, because an MS is registered in the same SGSN as long as it is located within the SGSN pool area. This increases the QoS of GPRS for the end-user. The capacity dimensioning for an SGSN pool can be made according to the busy hour traffic of the whole SGSN pool area. This is in contrast to a non-pooled case where each SGSN has to be dimensioned according to the busy hour traffic of the area served by the specific SGSN. As the busy hour traffic may occur at different time for different SGSNs, more SGSN capacity may be needed in total for the non-pooled case. Therefore, SGSN Pool helps to improve network capacity and save capital expenditure (CAPEX).
An SGSN pool is defined as a group of SGSNs serving MSs in one SGSN pool area. A BSC belonging to an SGSN pool area is connected to all SGSNs in the related SGSN pool. As shown
in Figure 2-293, SGSN1, SGSN2, and SGSN3 form SGSN Pool1, and BSC1, BSC2, and BSC5 form SGSN Pool Area1; whereas, SGSN4, SGSN5, and SGSN6 form SGSN Pool2, and BSC2, BSC3, and BSC6 form SGSN Pool Area2. Figure 2-293 SGSN Pool networking topology
An SGSN pool area consists of one or more RAs. All the RAs served by one BSC must belong to the same SGSN pool area. RA21 and RA22, as shown in Figure 2-293, belong to both SGSN Pool Area1 and SGSN Pool Area2, that is, overlapping SGSN pool areas. All the SGSNs in an SGSN pool share the responsibility of handling all the MSs in all the RAs of the SGSN pool area. One or more SGSNs in the pool may in addition serve BSCs outside this SGSN pool area. As shown in Figure 2-293, SGSN6 serves RA41 and RA42 of BSC4 that are not in the SGSN pool area. SGSN Pool is enabled when the parameter Allow SGSN Pool is set to Yes. If the SGSN Pool feature is enabled at the BSC, the P-TMSI reassignment function must be enabled at the SGSN. Each MS can be registered in any SGSN within the SGSN pool. Once an MS is registered in an SGSN, the SGSN assigns a 4-bit packet temporary mobile subscriber identity (P-TMSI) to the MS to uniquely identify the MS within the SGSN pool area. The network resource identifier (NRI) of the SGSN is contained in the P-TMSI. The MS converts the P-TMSI into the temporary logical link identifier (TLLI). When the MS accesses the network, it informs the BSC of the TLLI (containing the NRI). Then, the MS is routed to the correct SGSN by the BSC based on the NRI contained in the TLLI. The MS is served by the same SGSN as long as it stays within the SGSN pool area. The key technology of the SGSN Pool feature is the SGSN selection based on the load balancing algorithm.

2.69.3.1 Routing of an MS to an SGSN Routing of an MS with a TLLI Containing the network resource identifier (NRI)
Figure 2-294 shows the structure of a P-TMSI or TLLI (containing the NRI). The P-TMSI is assigned to the MS by the SGSN. Figure 2-294 Position of the NRI in the TLLI
The NRI field in a P-TMSI or TLLI is from bit 23 to bit 14. A maximum of 1024 NRIs can be defined by setting the NRI length to the maximum length of 10 bits. If the NRI is less than 10 bits, the most significant bit of the NRI is always stored in bit 23. For example, if the NRI length is set to 4, a maximum of 16 NRIs can be defined in the pool. In this case, the NRI is defined by bits 20-23 of the TLLI. The NRI length is specified by the parameter SGSN NRI Length. One NRI Value corresponds to only one SGSN in an SGSN pool; therefore, the NRIs must be set in all SGSNs and BSCs related to the SGSN pool. l l l One SGSN may correspond to multiple NRIs and must be assigned at least one NRI. The NRI length must be the same in all SGSNs and BSCs related to an SGSN pool. In case of overlapping SGSN pool areas, the NRI length must be the same in all SGSNs and BSCs related to the different SGSN pools.
The mapping relation between the NRI and SGSN Node ID can be configured on the Web LMT. If an MS accessing the network carries the TLLI containing the NRI, the BSC extracts the NRI from the TLLI and routes the MS to an SGSN according to the mapping relation between the NRI and the SGSN. l l If the SGSN is in normal state, the BSC always routes the MS to the corresponding SGSN. If the SGSN is faulty, SGSN Management Status is Prohibited, or the corresponding SGSN is unavailable, the BSC routes the MS to a normal SGSN in the same SGSN pool based on the load balancing algorithm. If the null-NRI is contained in the TLLI, it indicates that the MS must be routed to another SGSN. In this case, the BSC routes the MS to a normal SGSN in the same SGSN pool based on the load balancing algorithm.
Issue 08 (2011-09-30)
Routing of an MS With a TLLI Not Containing the NRI

l When an MS accesses the network for the first time, it generates a random TLLI and sends it to the BSC. The TTLI does not contain the NRI. Then, the BSC routes the MS to an SGSN in normal state according to the load balancing algorithm. When an MS belonging to one SGSN pool area accesses another SGSN pool area through the first RA update, the BSC extracts the NRI from the TTLI. Since the NRI does not correspond to any SGSN serving the new SGSN pool area, the BSC routes the MS to an SGSN in normal state according to the load balancing algorithm.
CAUTION
An NRI used in one SGSN pool must not be reused in neighboring pools. For example, when an MS that is registered in SGSN Pool Area1 of SGSN Pool1 accesses SGSN Pool Area2 of SGSN Pool2, the BSC routes the MS to an SGSN serving SGSN Pool Area2 according to the NRI. If the NRI configuration of the two SGSN pools is the same, the BSC routes the MS to the SGSN corresponding to the NRI in SGSN Pool2. This may lead to overload in the SGSN and load imbalance in the SGSN Pool2.
2.69.3.2 SGSN Selection Based on Load Balancing Algorithm SGSN Capacity

The capacity of the SGSN in each SGSN pool is specified by the parameter Configure Capacity<K User Number> set at the BSC.
Load Balancing Algorithm

The BSC calculates the load sharing ratio of each SGSN and the range of a random value V based on the capacity and SGSN Management Status of each SGSN. The value range of SGSN Management Status is Normal, Unload, and Prohibited. The load sharing ratio of the SGSNs in normal state is calculated. Value V is calculated through the random number algorithm. The BSC calculates the load sharing ratio of each SGSN in normal state according to the capacity of each SGSN. The load sharing ratio of each SGSN indicates the proportion of the capacity of one SGSN to the capacity of all SGSNs in the pool. The ratio is accurate to the third decimal place; therefore, the range of value V is from 0 to 999. The BSC obtains value V through the random number algorithm and selects a serving SGSN based on the mapping relation between value V and SGSN, to ensure the load balance in the SGSN pool. Table 2-198 describes the mapping relation between value V and SGSN for an SGSN pool. Here, the SGSN pool consists of SGSN1 with a capacity of 400 users, SGSN2 with a capacity of 300 users, and SGSN3 with a capacity of 300 users.
Issue 08 (2011-09-30)
1130
Table 2-198 Mapping relation between value V and SGSN SGSN Capacity (Number of Users) 400 300 300 SGSN State Normal Normal Normal Load Sharing Ratio 40.0% 30.0% 30.0%
SGSN ID SGSN1 SGSN2 SGSN3
Range of Value V 000-399 400-699 700-999
For example, if value V is 404, the BSC selects SGSN2 as the serving node; if value V is 100, the BSC selects SGSN1 as the serving node.
2.69.3.3 Load Adjustment in an SGSN Pool Load Adjustment When an SGSN Is Added to or Removed from the SGSN Pool
When a new SGSN is added to the SGSN pool, the BSC automatically adjusts the load sharing ratio of each SGSN. For example, SGSN4 with a capacity of 300 users is added to the SGSN pool. Compared with the original mapping relation between value V and SGSN shown in Table 2-198 in 2.69.3.2 SGSN Selection Based on Load Balancing Algorithm, the mapping relation is renewed, as shown in Table 2-199. Table 2-199 Mapping relation between value V and SGSN when SGSN4 is added SGSN Capacity (Number of Users) 400 300 300 300 SGSN State Normal Normal Normal Normal Load Sharing Ratio 30.8% 23.1% 23.1% 23.0%
SGSN ID SGSN1 SGSN2 SGSN3 SGSN4
Range of Value V 000-307 308-538 539-769 770-999
Load sharing ratio of the last SGSN = 1 - sum of load sharing ratio of each remaining SGSN When an SGSN is removed from the SGSN pool, the BSC also automatically adjusts the load sharing ratio of each remaining SGSN. If SGSN3 in Table 2-199 is removed from the SGSN pool, the mapping relation between value V and SGSN is renewed, as shown in Table 2-200.
Issue 08 (2011-09-30)
1131
Table 2-200 Mapping relation between value V and SGSN when SGSN3 is removed SGSN ID SGSN1 SGSN2 SGSN4 SGSN Capacity (Number of Users) 400 300 300 SGSN State Normal Normal Normal Load Sharing Ratio 40.0% 30.0% 30.0%
Range of Value V 000-399 400-699 700-999
Load Adjustment When the SGSN Capacity Is Changed

When all the SGSNs stay in the SGSN pool and are in normal state, the BSC automatically adjusts the load sharing ratio of each SGSN if the capacity of one or more SGSNs is changed. If the capacity of SGSN2 in Table 2-198 in 2.69.3.2 SGSN Selection Based on Load Balancing Algorithm is changed from 300 to 400, the mapping relation between value V and SGSN is renewed, as shown in Table 2-201. Table 2-201 Mapping relation between value V and SGSN when the capacity of an SGSN is changed SGSN Capacity (Number of Users) 400 400 300 SGSN State Normal Normal Normal Load Sharing Ratio 36.4% 36.4% 27.2%
Range of Value V 000-363 364-727 728-999
The range of value V is changed from 400-699 in Table 2-200 to 364-727 in Table 2-201.
Load Adjustment When an SGSN Is Faulty

When an SGSN is faulty, the BSC adjusts the load sharing ratio of each normal SGSN and routes the MSs registered in the faulty SGSN to a normal SGSN in the pool. If SGSN2 in Table 2-201 is faulty, the mapping relation between value V and SGSN is renewed, as shown in Table 2-202. Table 2-202 Mapping relation between value V and SGSN when SGSN2 is faulty SGSN ID SGSN1
Issue 08 (2011-09-30)
SGSN Capacity (Number of Users) 400
SGSN State Normal
Load Sharing Ratio 57.1%
Range of Value V 000-570

1132
SGSN ID SGSN2 SGSN3
SGSN Capacity (Number of Users) 400 300
SGSN State Faulty Normal
Load Sharing Ratio 0 42.9%
Range of Value V -571-999
Load Adjustment When an SGSN Is Unloaded

If SGSN Management Status of an SGSN in the pool is set to Unload, the BSC adjusts the load sharing ratio of each normal SGSN and routes the MSs registered in the unloaded SGSN to a normal SGSN in the pool. For example, if SGSN2 in the SGSN pool consisting of SGSN1, SGSN2, and SGSN3 is faulty, the MSs registered in SGSN2 are routed to SGSN1 or SGSN3. In this case, the NRI contained in the P-TMSI is changed. The changed NRI in the P-TMSI corresponds to SGSN1 or SGSN3; therefore, the BSC does not route the MSs back to SGSN2 even if SGSN2 resumes to normal state. This may lead to overload in SGSN1 or SGSN3 and imbalance in the SGSN pool. In this case, SGSN Management Status of SGSN1 or SGSN 3 should be set to Unload. If SGSN Management Status of SGSN1 in Table 2-201 is set to Unload, the mapping relation between value V and SGSN is renewed, as shown in Table 2-203. Table 2-203 Mapping relation between value V and SGSN when SGSN1 is unloaded SGSN Capacity (Number of Users) 300 400 300 Load Sharing Ratio 0 57.1% 42.9%
SGSN State Unloaded Normal Normal
Range of Value V -000-570 571-999
After SGSN Management Status of SGSN1 is set to Unload, the MSs registered in SGSN1 are reassigned P-TMSIs. l If an MS sends a request for the PS service, the P-TMSI is reassigned as follows: 1. 2. 3. 4. l 1. Before the connection is established, SGSN1 assigns the MS P-TMSI1 in which NRI is NULL_NRI and routing area identity (RAI) is Non-broadcast RAI. The MS initiates RA update immediately on receiving the non-broadcast RAI. The BSC extracts the null-NRI from TLLI1 and routes the MS to a normal SGSN according to the load balancing algorithm. The SGSN reassigns a P-TMSI to the MS. In the periodic RA update, the MS sends TLLI1 to the BSC. Then, the BSC routes the MS to SGSN1.
When an MS remains standby for a long time, the P-TMSI is reassigned as follows:
Issue 08 (2011-09-30)
2. 3. 4.
SGSN1 assigns P-TMSI2 containing the null-NRI and sends the non-broadcast RAI to the MS. The MS immediately initiates RA update on receiving the non-broadcast RAI. When SGSN Management Status of SGSN1 is Unload and null-NRI is contained in TLLI2, the BSC routes the MS to a normal SGSN according to the load balancing algorithm. The SGSN reassigns a P-TMSI to the MS.
5. l
After an MS is powered off for a long time, it immediately initiates RA update when it is powered on. In this case, the P-TMSI is reassigned according to the status of SGSN1. If SGSN Management Status of SGSN1 is Unload, the MS is reassigned a P-TMSI. The reassignment procedure is the same as that for an MS being standby for a long time. If SGSN Management Status of SGSN1 is Normal, SGSN1 continues to serve the MS and the MS is not reassigned a P-TMSI.
After the load is balanced in the SGSN pool, the SGSN Management Status of SGSN1 must be set to Normal. Otherwise, subsequent MSs cannot be registered in SGSN1.
2.69.4 Parameters
The following describes the parameters related to SGSN pool. For the meaning of each parameter, see Table 2-204. For the default value, value range, and related MML commands of each parameter, see Table 2-205. Table 2-204 Parameter description (1) Parameter Description Whether to enable the SGSN pool function. With SGSN pool, a BSC6900 is connected to multiple SGSNs in the pool, and load balancing and resource sharing between these SGSNs are allowed. In this manner, the PS services are processed by the SGSNs in the SGSN pool in the most efficient way. This reduces inter-MSC handovers and node redundancy backup. Length of the NRI(Network Resource Identifier) or NULL-NRI. The length determines the maximum value of the NRI and NULL-NRI. Uniquely identifies a node of SGSN, with the specified operator name Identifies the mapping relation from the NRI to the SGSN uniquely with the operator name. Administrative state of the SGSN. The value "ALLOW" indicates that the SGSN can handle the PS services normally. The value "UNISTALL" indicates that the SGSN does not permit new PS services to access the network and the ongoing PS services are not affected. The value "DENY" indicates that the SGSN denies all PS services.
Allow SGSN Pool
SGSN NRI Length SGSN Node ID NRI Value
SGSN Management Status
Issue 08 (2011-09-30)
1134
Parameter Configure Capacity<K User Number>
Description Available capacity of the SGSN
Table 2-205 Parameter description (2) Paramete r Default Value GUI Value Range Actual Value Range Unit MML Comman d ADD GCNOPE RATOR (Optional) ADD GCNOPE RATOR (Mandator y) ADD NSE (Mandator y) ADD SGSNNO DE (Mandator y) ADD NRISGSN MAP (Mandator y) ADD NRISGSN MAP (Mandator y) Impact
Allow SGSN Pool
NO
NO(No), YES(Yes)
NO, YES
None
BSC
SGSN NRI Length
1~10
1~10
None
BSC
SGSN Node ID
None
0~4095
0~4095
None
NSE
NRI Value
None
0~1023 UNISTAL L (Uninstall) , ALLOW (Allow), DENY (Deny)
0~1023
None
BSC
SGSN Managem ent Status Configure Capacity< K User Number>
ALLOW
UNISTAL L, ALLOW, DENY
None
ADD SGSNNO DE (Optional) ADD SGSNNO DE (Optional)
BSC
1800
0~65535
0~65535
None
BSC
Issue 08 (2011-09-30)
1135
2.69.5 Counters
2.69.6 Glossary

l l l l l l l 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes " BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.70 Soft-Synchronized Network

2.70.1 Introduction
2.70.1.1 Scope
This document describes the soft-synchronized network feature of Huawei GBSS. It covers the function of and technologies regarding the soft-synchronized network feature, including determining a pair of optimal neighboring cells, collecting the offset information of BTSs, synchronizing two BTSs, and managing the synchronization status of BTSs.


The change history provides information on the changes in the soft-synchronized network feature in different document versions.
There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the soft-synchronized network feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.70.2 Overview
The existing GSM networks are asynchronous networks. The BTSs are asynchronous with each other. That is, the frame number (FN) and symbol offsets of the BTSs are different, as shown in Figure 2-295. In an asynchronous network, especially in the case of tight frequency reuse, the co-channel interference and adjacent-channel interference are uncontrollable and unpredictable because timeslots on different TRXs overlap randomly.
NOTE
The symbol offset is the time difference of a timeslot in a BTS relative to the same timeslot in the other BTS.
Issue 08 (2011-09-30)
1137
Figure 2-295 FN and symbol offsets of BTSs in an asynchronous network
NOTE
x, y and z indicate the FNs.
It is a common approach in the telecommunications industry that each BTS is installed with a GPS. Thus, the BTS can obtain GPS signals through the satellite to achieve the synchronization of the entire network. This approach, however, has the following limitations: l l Each BTS must be installed with a GPS, and the GPS must be maintained on a regular basis, thus increasing the equipment cost and operational expenditure. The GPS signals are unstable indoors because of obstruction of walls and limitation to indoor cabling. Therefore, it is difficult to solve the synchronization problem in the case of indoor coverage.
Huawei GBSS adopts the innovative Soft-Synchronized Network technology. That is, the FNs and symbol offsets of the BTSs are adjusted by means of software to synchronize timeslots in the frames. In this case, the BTSs use the planned FNs and symbol offsets to achieve synchronization, as shown in Figure 2-296. Figure 2-296 FN and symbol offsets of BTSs in a synchronous network
NOTE
x indicates the FN. m and n indicate the FN offsets.
When Site Synchronization Method is set to AISS(Air Interface Software Sync), SoftSynchronized Network is enabled. Soft-Synchronized Network consists of four procedures, as shown in Figure 2-297.
Issue 08 (2011-09-30)
1138
Figure 2-297 Principle of Soft-Synchronized Network
NOTE
The dashed line indicates that related procedures may be initiated during the BTS synchronization status management. The solid line indicates that the procedures must be performed in sequence.
The key task of Soft-Synchronized Network is to collect the offset information of two BTSs at the same time. Before collecting the offset information of BTSs, the BSC must determine the neighboring relations between BTSs and a pair of optimal neighboring cells. The synchronization adjustment between BTSs is the basic procedure of Soft-Synchronized Network. Soft-Synchronized Network supports synchronization between BTSs not only under a BSC but also under multiple BSCs when Support BSC AISS is set to YES(YES). When SoftSynchronized Network is used to perform inter-BSC synchronization, an IP link must be added between BSCs for transferring offset information. The Soft-Synchronized Network technology converts an asynchronous network into a synchronous network through software upgrade without any hardware change in the existing network. Thus, the equipment cost is not increased. This technology provides a technical support platform for radio network optimization and network performance improvement. In addition, this technology makes it possible for operators to introduce new services and thus improve revenue generation.

2.70.3.1 Determining a Pair of Optimal Neighboring Cells
Before collecting the offset information of the BTSs, the BSC must determine a pair of optimal neighboring cells. The methods of determining a pair of optimal neighboring cells vary according to the application scenarios of Soft-Synchronized Network.
Under a BSC
Before determining a pair of optimal neighboring cells, the BSC must determine the neighboring relations between BTSs. The neighboring relations between BTSs can be configured manually or calculated by the BSC. The calculation method is as follows: The BSC calculates the distance between every two BTSs to be synchronized with the reference BTS in the BSC, calculates the distance between each BTS to be synchronized and every other BTS to be synchronized, and then determines the neighboring relations between every two BTSs.
NOTE
The reference BTS is generally located in the central coverage area of the network. The FNs of the TRXs in this BTS are references for calculating the FN offset of other BTSs to be synchronized. The symbol offset of the TRXs in this BTS is 0.
After the neighboring relations between the BTSs are determined, the BSC performs calculation to determine a pair of optimal neighboring cells. That is, the BSC chooses two cells that are the closest to each other and in which the antenna azimuths face each other as a pair of optimal neighboring cells. The BSC then stores the information about the pair of optimal neighboring cells for future use in offset information collection. Set Reinitialize Neighbour Cell Table in the ADD AISSCFG command to YES(YES) to enable the BSC to calculate a pair of optimal neighboring cells.
NOTE
If the BSC calculates a pair of optimal neighboring cells automatically, the LCS parameters such as NS Latitude, WE Longitude, and Antenna Azimuth Angle must be modified.
Under Different BSCs

Run the ADD EXTNCELL command to choose two neighboring cells at the border of the coverage areas of two BSCs as a pair of optimal neighboring cells. The two neighboring cells belong to the two BSCs respectively. Generally, a pair of neighboring cells configured belong to the controlling BSC and the collaborative BSC respectively. You can set BSC Inner Cell Index or BSC Inner Cell Name to specify the cell under the controlling BSC, set Adjacent BSC DPC to specify the collaborative BSC, and set BSC Adjacent Cell Index or BSC Adjacent Cell Name to specify the cell under the collaborative BSC.
NOTE
The controlling BSC is relative to the collaborative BSC. During the synchronization between BSC A and the reference BSC, the reference BSC is the controlling BSC, and BSC A is the collaborative BSC. During the synchronization between BSC A and lower-level BSC B, BSC A is the controlling BSC, and BSC B is the collaborative BSC. The reference BSC is generally located in the central coverage area of several BSCs. It serves as the start point of Soft-Synchronized Network between BSCs.
Issue 08 (2011-09-30)
1140
2.70.3.2 Collecting the Offset Information of BTSs

To implement BTS synchronization, the BSC must collect the offset information of BTSs.
Collecting the Offset Information of BTSs Under a BSC

To collect the offset information of BTSs under a BSC, the MS sends an AB to the BTSs. Then, the BSC obtains the information about the FN offsets and symbol offsets of the BTSs. The time synchronization of the BTSs is performed on the basis of the obtained information. See Figure 2-298. Figure 2-298 Intra-BSC offset information collection
As shown in Figure 2-298, x and y indicate the FNs. The procedure for collecting the offset information of BTSs is as follows: 1. 2. 3. 4. The BSC chooses an MS in the overlapping area of BTS1 and BTS2. The MS sends an AB to the BTSs. After receiving the AB, BTS1 and BTS2 report the AB reception time to the BSC. Based on the AB reception time reported by BTS1 and BTS2 and the symbol offset of the BTSs on the Um interface, the BSC calculates the FN offset and the symbol offset in the frame.
NOTE
The symbol offset of the BTSs on the Um interface is the symbol offset of the BSC plus the symbol offset of each BTS.
CAUTION
Ensure that there are MSs in the overlapping area of BTS1 and BTS2 and that BTS1 has reserved channel resources. When configuring the synchronization task, you should set the time, at which the traffic is light, for collecting the offset information.
Issue 08 (2011-09-30)
1141
Collecting the Offset Information of BTSs Under Different BSCs

To synchronize the BTSs under different BSCs, the FN offsets and symbol offsets in the frames between the BSCs must be collected. The offset information of two optimal neighboring BTSs under different BSCs is collected in the same way as intra-BSC offset information collection, as shown in Figure 2-299. Figure 2-299 Inter-BSC offset information collection
As shown in Figure 2-299, X and Y indicate the FNs.

NOTE
To implement offset information collection and adjustment between the BSCs, a communication port must be added between the BSCs. The information can be transported between the BSCs through the IP-based inter-BSC communication mechanism.
2.70.3.3 Synchronizing Two BTSs

Synchronization between BTSs is the key technology of Soft-Synchronized Network.
Under a BSC
The system synchronizes every two BTSs under a BSC until all the BTSs under the BSC are synchronized. In this example, BTS1 acts as a reference BTS, and the FN and offset of BTS1 remains unchanged. The FN and offset of BTS2 is adjusted according to the FN offset and symbol offset calculated by the BSC to synchronize BTS2 with BTS1. See Figure 2-300.
Issue 08 (2011-09-30)
1142
Figure 2-300 Synchronization between BTSs
As shown in Figure 2-300, x and y indicate the FNs, and m is the planned FN offset. The synchronization procedure is as follows: 1. 2. FN synchronization: The FN of BTS2 is adjusted to the FN of BTS1 plus the FN offset so that the FN of BTS2 synchronizes with the FN of BTS1. Offset synchronization: The offset of BTS2 is adjusted to the same value as that of BTS1.
NOTE
l The planned FN offset and symbol offset in a BSC are specified by the parameters Frame Offset [Frame No] and In Frame Bit Offset [1/8 bit] in the MOD BTSEXCURSION command respectively. l During the BTS synchronization, call drops may occur. Therefore, when configuring the synchronization task, ensure that the synchronization is performed when the traffic is light.
The synchronization between the BTSs under a BSC is performed through hierarchical synchronization, as shown in Figure 2-301. Figure 2-301 Synchronizing the BTSs under a BSC
Issue 08 (2011-09-30)
1143
1. 2.
The BSC takes BTS1 as a reference BTS to synchronize the BTSs in the first circle, for example, BTS2-BTS7 shown in Figure 2-301, around BTS1. The BSC takes each BTS in the first circle as a reference BTS to synchronize two neighboring BTSs in the second circle. If BTS2 is used as a reference BTS, two neighboring BTSs of BTS2, for example, BTS8 and BTS9 shown in Figure 2-301, are synchronized. The other BTSs under the BSC are synchronized in the same way.
NOTE
3.
If subnets with independent coverage areas exist in the BSC, assign the BTSs to different synchronization areas manually. Set a reference BTS in each synchronization area so that the BSC can perform synchronization in multiple synchronization areas simultaneously. This increases the efficiency of BTS synchronization under the entire BSC.

The synchronization between BTSs under different BSCs is similar to that under a BSC. To synchronize BTSs under different BSCs, a BSC is configured as the reference BSC and the other BSCs as collaborative BSCs. Then, the collaborative BSCs are synchronized with the reference BSC, as shown in Figure 2-302. Figure 2-302 Synchronizing the BTSs under different BSCs
The procedure of inter-BSC synchronization is as follows: 1. 2. 3. 4. 5. The reference BSC synchronizes all the BTSs under its coverage. The reference BSC acts as a controlling BSC. It calculates the FN offset and symbol offset of a collaborative BSC, and then sends the offset information to the collaborative BSC. After receiving the offset information, the collaborative BSC synchronizes all the BTSs under its coverage. If the collaborative BSC has lower-level BSCs, it acts as a controlling BSC to synchronize the lower-level BSCs. Steps 1 through 4 are repeated until all the BTSs under the BSCs in the entire network are synchronized.
NOTE
l The planned FN offset and symbol offset between BSCs are specified by the parameters Frame Offset [Frame No] and In Frame Bit Offset [1/8 bit] in the SET BSCSYNCOFF command respectively. l If there are several collaborative BSCs under a controlling BSC, all of them must be synchronized with the controlling BSC.
Issue 08 (2011-09-30)
1144
2.70.3.4 Managing the Synchronization Status of BTSs

The BTS synchronization status management consists of synchronization process management and synchronization status monitoring. Though the synchronization tasks can be initiated through the same command, the method of managing the synchronization status of BTSs under a BSC is different from the method of managing the synchronization status of BTSs under different BSCs.
Under a BSC
Figure 2-303 shows the synchronization process management and synchronization status monitoring. Figure 2-303 Synchronization process management
The BTS synchronization status management under a BSC consists of four types of status: l l l l Information to be collected Before initial synchronization, all the BTSs are in the this state. Collection in progress The BSC starts collecting the offset information of the BTSs. Information collected The offset information collected is stored in the OMU. Synchronization completed After the synchronization information is collected, the BTSs start adjusting the FNs and offsets. After the adjustment, the BTSs are in this state. If an event causing loss of synchronization occurs, for example, BTS reset, BTS clock unlocked, or other causes, the BTS state is changed to "Information to be collected." In such a case, the synchronization of the corresponding BTSs with the network is initiated again. The BTS synchronization status management under a BSC is performed by adding or modifying the Soft-Synchronized Network task through MML commands. The parameter AISS Task Index uniquely identifies a Soft-Synchronized Network task. The parameter Reference BTS Index specifies the reference BTS. The parameters Offset Information Collection Start Time and Offset Information Collection End Time specify the time for collecting offset information. The parameters Offset Time Adjustment Start Time and Offset Time
Adjustment End Time specify the time for adjusting synchronization. The parameters BSC Interior Clock Synchronize Protect Time and Immediate Initial Adjust After Site Reset Enable are related to offset information collection after reset.

To control and manage the inter-BSC synchronization process easily, four types of synchronization status are used to identify the status of the collaborative BSC, as shown in Figure 2-304. Figure 2-304 Managing the synchronization status of the collaborative BSC
The synchronization status management of the collaborative BSC has four types of status: l l Information to be collected Before initial synchronization, all the BTSs are in this state. Collection in progress The controlling BSC instructs the collaborative BSC to collect the offset information of the BTSs. l Information collected After collecting the offset information, the collaborative BSC sends it to the controlling BSC. l Synchronization completed The collaborative BSC and the controlling BSC are in this state.
Issue 08 (2011-09-30)
1146

NOTE
The implementation of inter-BSC Soft-Synchronized Network is based on intra-BSC Soft-Synchronized Network. The controlling BSC is responsible for controlling the synchronization status of the BTSs under the controlling BSC and the synchronization status of the collaborative BSC. One controlling BSC may have multiple collaborative BSCs. Thus, one controlling BSC may be responsible for controlling the synchronization status of multiple collaborative BSCs at the same time. Frequent synchronization adjustment may lead to BTS reset, so the collaborative BSC can initiate the intraBSC synchronization adjustment only after the inter-BSC synchronization information collection is complete. If the communication between the BSCs fails, or inter-BSC synchronization information collection cannot be started normally, the collaborative BSC performs intra-BSC synchronization adjustment forcibly.
The BTS synchronization status management under different BSCs is performed by adding or modifying the Soft-Synchronized Network task through MML commands. The parameter Base BSC specifies the reference BSC. The parameter Control BSC DPC specifies the controlling BSC. The parameters BSC Offset Information Collection Start Time and BSC Offset Information Collection End Time specifies the time for collecting the offset information of BTSs under different BSCs. The parameters Immediate Initial Adjust After Site Reset Enable is related to offset information collection after reset.

Impact on Network Performance
After an asynchronous network is converted into a synchronous network through SoftSynchronized Network, the network performance may be affected because the parameter properties and radio environment are changed if network planning is not performed. For example, the voice quality degrades, and the call drop rate on the TCH increases. The details are as follows: l In an asynchronous frequency hopping network, co-channel interference or adjacentchannel interference is generated randomly because the FNs of BTSs are different. After synchronization, however, co-channel interference or adjacent-channel interference may be generated continuously. The BSIC decoding efficiency and neighboring cell searching efficiency of the MS may be reduced because the FNs and symbol offsets are aligned in a synchronous network. Therefore, the handover performance of the MS is affected. After network synchronization, the SACCH frames on the TCH are aligned. All the MSs in the entire network send SACCH frames at the same time, thus increasing the interference on the SACCH and the probability of call drops on radio links.
Therefore, after the synchronization task is performed, you must perform network optimization and adjust the settings of radio parameters. From the perspective of the entire network coverage, Huawei BSS cannot be synchronized with BTSs of other vendors even after Um interface synchronization is realized among all Huawei BTSs. In addition, at the border of a synchronous network, the network performance cannot reach the optimum level because of the interference of other asynchronous BTSs.
Configuration Rules
The license is required for the implementation of Soft-Synchronized Network.
You can configure parameters related to Soft-Synchronized Network only by running MML commands on the local maintenance terminal. To make best use of the Soft-Synchronized Network technology, comply with the following rules: l l l The Soft-Synchronized Network technology is applicable to the tight frequency reuse scenario. The distance between BTSs should be shorter than 900 m. A distance of shorter than 800 m is recommended. The network using the Soft-Synchronized Network technology should be planned in an continuous coverage area. That is, under a BSC, the continuous coverage area can be regarded as a to-be-synchronized area. When the Soft-Synchronized Network technology is used in dual-band networks, the networks operating at different bands should be separated for synchronization. The BTSs operating at 900 MHz are grouped together for synchronization, and the BTSs operating at 1800 MHz are grouped together for synchronization. If concentric cells exist in a network, collect synchronization information of underlaid subcells. If BTSs with GPS antennas exist in the network, it is recommended that you set these BTSs as reference BTSs to shorten the synchronization time of the entire network.
l l
2.70.5 Parameters
This chapter describes the parameters related to soft-synchronized network. For the meaning of each parameter, see Table 2-206. For the default value, value ranges, and MML commands of each parameter, see Table 2-207. Table 2-206 Parameter description (1) Parameter Description Site synchronization method. AISS stands for the airinterface soft synchronization method, and GPS stands for the GPS synchronization method. Whether the Um interface software synchronization between BSCs is supported Whether to re-initialize the neighboring cell pair for software synchronization Whether the cell is located in the south latitude or north latitude This parameter is used to select the location of a cell, east or west longitude. Size of the azimuth angle of the cell antenna Index of the cell in the BSC Name of the cell in the BSC
1148
Site Synchronization Method Support BSC AISS Reinitialize Neighbour Cell Table NS Latitude WE Longitude Antenna Azimuth Angle BSC Inner Cell Index BSC Inner Cell Name
Issue 08 (2011-09-30)
Parameter Adjacent BSC DPC BSC Adjacent Cell Index BSC Adjacent Cell Name Frame Offset [Frame No] In Frame Bit Offset [1/8 bit] AISS Task Index Reference BTS Index Offset Information Collection Start Time Offset Information Collection End Time Offset Time Adjustment Start Time Offset Time Adjustment End Time
Description The destination signaling point (DSP) of the adjacent BSC must be an Iur-g DSP. Index of the cell in the adjacent BSC Name of the cell in the adjacent BSC Frame offset of the BTS clock. Bit offset in the frame of the BTS clock Unique identifier of the Um interface software synchronization task The reference BTS must support the Um interface software synchronization. Start time for collecting the offset information End time for collecting the offset information Start time for adjusting the offset time End time for adjusting the offset time Value of the timer for synchronization between BSCs. If a BSC fails to synchronize with the control BSC before the timer expires, the BSC starts to synchronize the BTSs under its control. Whether to adjust the offset time immediately after the BTS is reset Whether the BSC is a reference BSC DPC of the control BSC Start time for collecting the inter-BSC offset information End time for collecting the inter-BSC offset information
BSC Interior Clock Synchronize Protect Time Immediate Initial Adjust After Site Reset Enable Base BSC Control BSC DPC BSC Offset Information Collection Start Time BSC Offset Information Collection End Time
Issue 08 (2011-09-30)
1149
Table 2-207 Parameter description (2) Parameter Defaul t Value GUI Value Range AISS(Air Interface Software Sync), GPS (GPS Synchroniza tion) NO(NO), YES(YES) NO(NO), YES(YES) North_latitu de(North latitude), South_latitu de(South latitude) East_Longit ude(East Longitude), West_Longi tude(West Longitude) Actual Value Range Uni t MML Command Impact
Site Synchronizati on Method Support BSC AISS Reinitialize Neighbour Cell Table
AISS
AISS, GPS
Non e Non e Non e
SET BTSOTHP ARA (Optional) ADD AISSCFG (Mandatory) ADD AISSCFG (Mandatory)
BTS BSC690 0 BSC690 0
NO
NO, YES
None
NO, YES
NS Latitude
None
North_latitude, South_latitude
Non e
SET GCELLLCS (Optional)
Cell
WE Longitude Antenna Azimuth Angle
None
East_Longitud e, West_Longitu de
Non e degr ee
SET GCELLLCS (Optional) SET GCELLLCS (Optional) ADD EXTNCEL L (Mandatory) ADD EXTNCEL L (Mandatory)
Cell
360
0~360
0~360
Cell
BSC Inner Cell Index
None
0~2047
0~2047
Non e
BSC690 0
BSC Inner Cell Name
None
None
1~64 characters
Non e
BSC690 0
Issue 08 (2011-09-30)
1150
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
Uni t
MML Command ADD EXTNCEL L (Mandatory) COL BSCSYNCI NFO (Mandatory) ADD EXTNCEL L (Mandatory) ADD EXTNCEL L (Mandatory) SET BTSEXCU RSION (Mandatory) SET BSCSYNC OFF (Mandatory) SET BTSEXCU RSION (Mandatory) SET BSCSYNC OFF (Mandatory)
Impact
Adjacent BSC DPC BSC Adjacent Cell Index BSC Adjacent Cell Name
None
1~16777215
1~16777215
Non e
BSC690 0
None
2048~5047
2048~5047
Non e
BSC690 0
None
None
1~64 characters
Non e
BSC690 0
Frame Offset [Frame No]
None
-2715647~2 715647
-2715647~271 5647
Non e
BSC690 0
In Frame Bit Offset [1/8 bit]
None
-10000~100 00
-10000~10000
Non e
BSC690 0
Issue 08 (2011-09-30)
1151
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
Uni t
MML Command ADD AISSCFG (Mandatory) ADD NCELL (Mandatory) COL SYNCINFO (Mandatory) SET BTSEXCU RSION (Mandatory) SET BSCSYNC OFF (Mandatory) COL BSCSYNCI NFO (Mandatory) ADD AISSCFG (Mandatory) ADD AISSCFG (Optional) ADD AISSCFG (Optional) ADD AISSCFG (Optional) ADD AISSCFG (Optional) ADD AISSCFG (Optional)
Impact
AISS Task Index Reference BTS Index Offset Information Collection Start Time Offset Information Collection End Time Offset Time Adjustment Start Time Offset Time Adjustment End Time BSC Interior Clock Synchronize Protect Time
None
0~7
0~7
Non e Non e
BSC690 0 BSC690 0
None
0~2047
0~2047
None
hour, min
hour{0~23} min{0~59}
Non e
BSC690 0
None
hour, min
hour{0~23} min{0~59} hour{0~23} min{0~59} hour{0~23} min{0~59}
Non e Non e Non e
BSC690 0 BSC690 0 BSC690 0
None
hour, min
None
hour, min
0~60
0~60
BSC690 0
Issue 08 (2011-09-30)
1152
Parameter Immediate Initial Adjust After Site Reset Enable
Defaul t Value
GUI Value Range
Actual Value Range
Uni t
MML Command ADD AISSCFG (Optional) ADD AISSCFG (Mandatory) ADD AISSCFG (Mandatory) ADD AISSCFG (Optional) ADD AISSCFG (Optional)
Impact
NO
NO(NO), YES(YES) NO(NO), YES(YES)
NO, YES
Non e Non e Non e
BSC690 0 BSC690 0 BSC690 0
Base BSC Control BSC DPC BSC Offset Information Collection Start Time BSC Offset Information Collection End Time
None
NO, YES
None
1~16777215
1~16777215
None
hour, min
hour{0~23} min{0~59}
Non e
BSC690 0
None
hour, min
hour{0~23} min{0~59}
Non e
BSC690 0
2.70.6 Counters
None.
2.70.7 Glossary

2.71 TC Pool
2.71.1 Introduction
2.71.1.1 Scope
This document describes TC pool of Huawei GBSS. It covers the function of and technologies mechanisms regarding TC pool, including working principle, networking, hardware cabling, hardware management. The document also describes the engineering guidelines to the feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the TC pool feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
Issue 08 (2011-09-30)
1154
01 (2009-0630)
2.71.2 Overview
Huawei GBSS allows other BSCs to connect to the transcoder subracks (TCSs) of a certain BSC so that these BSCs share the TC resources. Thus, the TCSs form a TC pool. When Service mode is set to SEPARATE(Separate), the TC resources exist in the remote TCSs. l In non-TC-pool mode, the TCSs belong to and process the CS services of their respective BSCs. These TCSs are not associated. Thus, the TC resources cannot be shared among multiple BSCs. This leads to inefficient use of the TC resources especially in the scenario where multiple BSCs with small capacity are deployed. In TC pool mode, one to four TCSs of the primary BSC compose the TC pool. The TC resources in the TC pool can be shared among the primary BSC and the secondary BSCs, which work in loading sharing mode, as shown in Figure 2-305.
NOTE
l The primary BSC performs the configuration and maintenance of the TC resources in a TC pool. It is unique in a TC pool area. The TCSs that form the TC pool belong to the primary BSC. l The secondary BSCs, configured with only the Basic Modules (BMs), share the TC resources in a TC pool with the primary BSC.
Figure 2-305 Allocation of the TC resources in the TC pool
Issue 08 (2011-09-30)
1155
The primary BSC and the secondary BSCs are connected to the TC pool over the Ater interface, and the TC pool is connected to the MSC over the A interface. Figure 2-306 shows the typical networking of a TC pool. Figure 2-306 Typical networking of a TC pool
The primary BSC performs the configuration and maintenance of the TCSs in the TC pool whereas the secondary BSCs share the TC resources in the TC pool. The TC Pool feature is subject to the parameter Is Support Tc Pool. The feature is applicable only to the BSCs whose Service mode is set to SEPARATE(Separate). The benefits of the TC Pool feature are as follows: l Flexible networking The TC Pool feature supports E1/T1 and Ch-STM-1 transmission modes on the Ater interface. In addition, one Ater interface board can be connected to multiple BSCs in the same transmission mode. Thus, the networking is flexible. l Reduced cost for network deployment The TC Pool feature enables multiple BSCs with small capacity to share the TC resources, thus reducing the cost for network deployment. l High reliability The data processing unit (DPU) boards in the TC Pool work in load sharing mode. In this manner, the impact of the failure of one DPU board on the services is reduced. This makes the network highly reliable.
NOTE
The DPU board performs the conversion and forwarding of the voice formats and the voice coding/ decoding. The Data Processing Unit REV:a (DPUa) and Data Processing Unit REV:c (DPUc) boards are collectively referred to as the DPU boards in this document.
Issue 08 (2011-09-30)
1156

2.71.3.1 Working Principle
When a BSC in the TC pool area sends a call request to a TCS, the working principle of the TC pool is as follows: 1. The TC pool allocates an A interface CIC based on ID of BSC in TC Pool of the BSC and the A interface timeslots. The TC pool finds the A interface CIC specified in the connection establishment request message from the A interface CICs of the BSCs specified by ID of BSC in TC Pool. 2. The TC pool allocates a TC device for the call based on the load balance algorithm. The TC pool manages all the TC devices in the TCS and monitors the load of each device in real time. When allocating the TC device, the TC pool allocates the device with the lowest load to the call at the TCS where the A interface CICs are located. If all the devices in the TCS operate at the maximum load, the TC pool allocates the TC device in other TCSs to the call. 3. The TC pool selects the Ater transmission channel according to ID of BSC in TC Pool of the BSC. The TC pool allocates idle Ater transmission channels to the BSC in the TC pool specified by ID of BSC in TC Pool. 4. After the call connection channel (A interfaceTC deviceAter interface) is established, the TCS returns a call establishment success message to the BSC.
2.71.3.2 Networking
The TC Pool feature can adjust the networking mode flexibly based on different physical transmission modes. The Ater interface, which connects the BSCs to the TC pool, supports the E1/T1 and Ch-STM-1 transmission modes. In addition, it supports the TDM or Ater transmission compression (IP over point-to-point protocol (PPP)) modes on the user plane. The A interface, which connects the TC pool to the MSC, supports the E1/T1 and Ch-STM-1 transmission modes. The primary BSC and secondary BSCs are connected to the MSC through the TCSs. The resources on the A interface can be carried in TDM mode. Figure 2-307 shows the TC pool networking when the TDM mode is used on the user plane over the Ater interface. In this scenario, the Ater interface supports the E1/T1 and Ch-STM-1 transmission modes.
Issue 08 (2011-09-30)
1157
Figure 2-307 TC pool networking (TDM used on the user plane over the Ater interface)
Figure 2-308 shows the TC pool networking when the IP over PPP mode is used on the user plane over the Ater interface. In this scenario, the Ater interface supports the Ch-STM-1 transmission mode. Figure 2-308 TC pool networking (IP over PPP used on the user plane over the Ater interface)
Issue 08 (2011-09-30)
1158
Figure 2-309 shows the TC pool networking when both the TDM and the IP over PPP modes are used on the user plane over the Ater interface. In this scenario, the Ater interface supports the E1/T1 and Ch-STM-1 transmission modes. Figure 2-309 TC pool networking (both TDM and IP over PPP used on the user plane over the Ater interface)
NOTE
For one BSC, only one transmission mode (TDM or IP over PPP) can be used over the Ater interface.
As shown in Figure 2-310, the timeslots on the Ater interface are as follows: l Speech service timeslot When the TDM mode is used on the user plane over the Ater interface, the speech frames are TRAU frames. When the IP over PPP mode is used on the user plane over the Ater interface, the speech frames are pTRAU frames. Only the speech service timeslots on the Ater interface can be carried in Ater transmission compression mode. l Signaling timeslot The Ater signaling timeslots are carried over the Ater signaling link. The Ater signaling timeslots can be carried only in TDM mode. l OM timeslot The Ater OM timeslots are carried on the OM links between the primary BSC and the TC pool. The Ater OM timeslots can be carried only in TDM mode. l A interface SS7 signaling timeslot The SS7 signaling is transparently transmitted to the Ater interface over the A interface SS7 signaling timeslots through the semipermanent connection.
Figure 2-310 Timeslots on the Ater interface
NOTE
When the Ater transmission compression mode is used on the user plane over the Ater interface, the BMs of the BSC and the TCSs in the TC pool must be configured as adjacent nodes. For details about the Ater transmission compression mode, see 2.13 Ater Compression Transmission.
As shown in Figure 2-311, the timeslots on the A interface are as follows: l l Speech service timeslot A interface SS7 signaling timeslot The SS7 signaling timeslots are carried on the SS7 signaling link on the A interface. The SS7 signaling is transparently transmitted to the Ater interface over the A interface SS7 signaling timeslots through the semipermanent connection. Figure 2-311 Timeslots on the A interface
Is Main BSC and ID of slave BSC in TC Pool determine whether the resources carried over the Ater and A interfaces belong to the primary BSC or a secondary BSC.
NOTE
ID of slave BSC in TC Pooll is required for only the secondary BSC.
2.71.3.3 Hardware Cabling

In TC pool mode, the user plane of the Ater interfaces of different BSCs can use the TDM or IP over PPP transmission mode. In addition, the Ater interface of the same BSC can use only one
transmission mode. Three types of hardware cabling are provided between the BM in the BSC in the TC pool area and the TCS in the TC pool. When the Ater interfaces of all the BSCs in the TC pool area use the TDM mode, the cabling between the BMs and the TCSs is shown in Figure 2-312. To improve the network reliability, the BMs can be evenly connected to the TCSs in the TC pool. Figure 2-312 Cabling between the BM and the TCS (TDM used over the Ater interface)
When the Ater interfaces of all the BSCs in the TC pool area use the IP over PPP mode, the cabling between the BMs and the TCSs is shown in Figure 2-313. In this case, multiple optical interfaces on the same POUc board in the BM can be connected to the optical interface of the same POUc board in the TCS. The multiple optical interfaces on the same POUc board in the TCS, however, can be connected to multiple BSCs.
Issue 08 (2011-09-30)
1161
Figure 2-313 Cabling between the BM and the TCS (IP over PPP used over the Ater interface)
When the Ater interfaces of some BSCs use the IP over PPP mode whereas those of other BSCs use TDM mode, the cabling between the BMs and the TCSs is shown in Figure 2-314. In the case of the BSC with the Ater interface in IP over PPP mode, multiple optical interfaces on the same POUc board in the BM can be connected to the optical interface of the same POUc board in the TCS. In the case of the BSC with the Ater interface in TDM mode, each BM can be evenly connected to all the TCSs in the TC pool.
Issue 08 (2011-09-30)
1162
Figure 2-314 Cabling between the BM and the TCS (both the TDM and IP over PPP modes used over the Ater interface)
2.71.3.4 Interface Timeslots

The timeslots on the Ater interface are as follows: l Ater speech service timeslots When the user plane on the Ater interface uses the TDM mode, speech frames function as TRAU frames. When the user plane on the Ater interface uses the IP over PPP mode, speech frames function as pTRAU frames. Only Ater speech service timeslots use Ater transmission compression. l Ater signaling timeslots Ater signaling timeslots are carried by Ater signaling links. Ater signaling timeslots can be carried only in TDM mode. l
Issue 08 (2011-09-30)
Ater Operation and Maintenance (OM) timeslots

Ater OM timeslots are carried by the OM links between the primary BSC and the TC pool. Ater OM timeslots are generally carried in TDM mode. l A interface SS7 signaling timeslots SS7 signaling is transparently transmitted to the Ater interface over the A interface SS7 signaling timeslots through the semipermanent connection.
NOTE
When the user plane on the Ater interface uses the IP over PPP mode, the BM and TC subracks of the BSC must be configured as adjacent nodes. For details, see the IP BSS Feature Parameter Description. The Ater over IP mode has not been put into commercial use. If the Ater over IP mode is required onsite, submit the onsite solutions to Huawei headquarters for evaluation and testing.
The timeslots on the A interface are as follows: l l A interface speech service timeslots A interface SS7 signaling timeslots
A interface SS7 signaling timeslots are carried by SS7 signaling links on the A interface. SS7 signaling is transparently transmitted to the Ater interface over the A interface SS7 signaling timeslots through the semipermanent connection. The Is Main BSC parameter determines whether the resources carried over the Ater and A interfaces belong to the primary BSC.
NOTE
The BSC ID parameter is set only when Is Main BSC is No. BSC ID determines which secondary BSC these resources belong to.
2.71.3.5 Hardware Management Hardware Involved in TC Pool

The hardware involved in a TC pool is one to four TCSs of the main BSC. The boards configured in the TCSs are as follows: l l l The boards that carry the TC resources are DPUa, DPUb, and DPUc. The A interface boards are EIUa, OIUa, and POUc. Ater interface board The Ater interface boards in TDM mode are EIUa, OIUa, and POUc. The Ater interface board in Ater transmission compression mode is POUc. l l The TDM switching network board is TNUa. The GE switching network and control board is SCUa.
The boards that carry the TC resources work in load sharing mode. Therefore, the N+1 redundancy configuration is recommended. This ensures reliability of the network, because the service is not affected even if one board is faulty.
Hardware Management
The main BSC performs the configuration and maintenance on the TCSs in the TC pool through the OM link on the Ater interface. The functions are as follows: l Hardware configuration Configuration of the cabinet and boards.
l l l
Status management Management of the TCS status Alarm management Management of the faults and alarms on the TCS Operation and maintenance Manual blocking, unblocking and query of the boards in the TCS
The secondary BSCs cannot perform the configuration and maintenance on the TCSs and can only query the usage of the TC resources.

l l l l l The setting of TC CRC Allowed must be consistent on the primary BSC and the secondary BSCs. The BSCs connected to the same TC pool must share the same clock source. The TC Pool feature applies only to BSCs in BM/TC separated mode. The feature cannot be enabled in BSCs in BM/TC combined mode or in A over IP transmission mode. The TC Pool feature supports various voice coding schemes, such as FR, EFR, HR, AMR, and WB-AMR. In TC pool networking mode, E1/T1 (TDM) and STM-1 (TDM) transmission modes are supported over the A interface, and E1/T1 (TDM) and STM-1 (TDM or IP over PPP) transmission modes are supported over the Ater interface. If the transmission modes are the same on the Ater interface, different E1/T1 ports on an Ater interface board in a TC subrack (TCS) can be connected to different BSCs in the TC pool area. If the transmission modes are the same on the A interface, different E1/T1 ports on an A interface board in a TCS can be connected to different MSCs or MGWs. In the case of upgrade, the primary BSC must be upgraded first. When the software version of the secondary BSCs is earlier than that of the primary BSC or when the primary BSC is faulty, the TC pool can continue to provide services for the secondary BSCs. One BSC can be connected to only one TC pool. If IP over PPP is used over the Ater interface, a pair of POUc boards of the BSC can be connected to only a pair of POUc boards of the same TCS. The TC Pool function cannot be used in BM/TC combined configuration mode or A over IP mode. That is, the TC Pool function can be used only in BM/TC separated configuration mode, even if the TC subrack and BM subrack of a BSC are located at the same place. In addition, the Ater interface boards, Ater signaling link, and Ater OM link must be configured. TC resources form a TC pool. Therefore, services are not affected if a board or DSP is faulty. Only the primary BSC configures, maintains, and manages TCSs. A interface CICs for secondary BSCs are configured on the primary BSC. TC data is unavailable on secondary BSCs. Therefore, data configuration status can only be checked manually. If NBAMR TFO Switch is set to ENABLE for the cells managed by secondary BSCs, TFO Switch must also be enabled for TCSs in the primary BSC. The number of Ater connection paths configured on secondary BSCs must be equal to that configured on the primary BSC. In addition, the Ater connection path indexes must be the
l l
l l l
l l
l l
Issue 08 (2011-09-30)
same on the primary and secondary BSCs. Otherwise, periodic synchronization messages between the secondary BSCs and the TCSs in the primary BSC will occupy Ater RSL bandwidths. l l l A TC subrack can be shared by multiple BSCs. A TC Pool can be connected to a maximum of 16 BSCs. A TC Pool can provide a maximum of 23,040 CS (voice) channels. A TC Pool supports all speech versions in non-TC Pool mode.
2.71.5 Parameters
This chapter describes the parameters related to TC pool. For the meaning of each parameter, see Table 2-208. For the default value, value ranges, and MML commands of each parameter, see Table 2-209. Table 2-208 Parameter description (1) Parameter Service mode Description Service mode of the BSC6900. This parameter specifies configuration mode of subracks. Whether to support the TC pool function. The TC Pool feature is implemented by connecting the maim processing subracks (MPSs) and extended processing subracks (EPSs) in multiple BSC6900s to the transcoder subracks (TCSs) of one BSC6900. In this manner, all the involved BSC6900s share the TC resources, and the shared TC resources form a TC Pool. The TC Pool feature is applicable to only the BSC6900s whose "Service mode " is set to SEPARATE.
Is Support Tc Pool ID of slave BSC in TC Pool ID of BSC in TC Pool Is Main BSC TC CRC Allowed BM/TC config flag Adjacent Node Type BSC ID BSC Flag
ID of the BSC that supports the TC pool function. ID of the BSC at the other end of the link. In non-TC pool scenario, this parameter specifies the ID of the primary BSC. In TC pool scenario, this parameter specifies the ID of the BSC that is at the other end of the link. Whether a BSC in the TC pool is the primary BSC This parameter specifies the cyclic redundancy check (CRC) switch, which can be set to On or Off. The value of this parameter determines whether check is performed on the TRAU frame between the BSC6900 and the BTS. The configuration flag specifies the operation is on the BM or TC. Type of the adjacent node Uniquely identifies a BSC in the TC pool It indicates whether the A interface E1/T1 is the primary BSC6900 or secondary BSC6900.
Issue 08 (2011-09-30)
1166
Table 2-209 Parameter description (2) Paramete r Default Value GUI Value Range SEPARA TE (Separate), TOGETH ER (Together) , AIP(AIP) Actual Value Range Unit MML Comman d Impact
Service mode
SEPARA TE
SEPARA TE, TOGETH ER, AIP
None
SET BSCBASI C (Optional) SET BSCBASI C (Optional) SET BSCBASI C (Mandator y) ADD ATERE1T 1 (Mandator y) ADD ATERSL (Mandator y) ADD SEMILIN K (Mandator y) SET BSCBASI C (Mandator y) SET BSCBASI C (Optional) ADD ATERE1T 1 (Mandator y)
BSC
Is Support Tc Pool
NO
NO(No), YES(Yes)
NO, YES
None
BSC
ID of slave BSC in TC Pool
None
1~15
1~15
None
BSC
ID of BSC in TC Pool
None
0~15
0~15
None
E1/T1 link
Is Main BSC
None
NO(No), YES(Yes)
NO, YES
None
BSC
TC CRC Allowed
ON
OFF(Off), ON(On) CFGBM (BM), CFGTC (TC)
OFF, ON
None
BSC
BM/TC config flag
None
CFGBM, CFGTC
None
E1/T1 link
Issue 08 (2011-09-30)
1167
Paramete r
Default Value
GUI Value Range ABIS (Abis Interface), A(A Interface), BSC(Ater Interface on BSC), TC(Ater Interface on TC), IUR_G (IUR_G Interface)
Actual Value Range
Unit
MML Comman d
Impact
Adjacent Node Type
None
ABIS, A, BSC, TC, IUR_G
None
ADD ADJNOD E (Mandator y) ADD ADJNOD E (Mandator y) BLK ACIC (Mandator y) ADD AE1T1 (Mandator y)
Adjacent node
BSC ID
None
0~15 MAINBS C(MAIN BSC), SUBBSC (SUB BSC)
0~15
None
Adjacent node
BSC Flag
None
MAINBS C, SUBBSC
None
E1/T1 link
2.71.6 Counters
2.71.7 Glossary

l l l l l
Issue 08 (2011-09-30)
BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
BSC6900 GSM Performance Counter Reference
2.72 TFO
2.72.1 Introduction
2.72.1.1 Scope
This document describes the TFO messages, TFO frame format, prerequisites for the TFO establishment, TRAU operating process in TFO mode, impact of TFO establishment on DTX and VQE, and TFO voice quality improvement.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the TFO feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description 2.72.3.3 Prerequisites for the TFO Establishment, 2.72.3.5 DTX and VQE After the TFO Establishment, and 2.72.3.6 TFO Voice Quality Improvement are added. The structure of the document is optimized. Parameter Change The added parameters are listed as follows: l Speech version l TFO Option Switch l Is RATSCCH Function Enabled None.
Editorial change
2.72.2 Overview
Tandem Operation is a process in which the speech signal of an MS-to-MS call is transcoded twice, as shown in Figure 2-315. Tandom Operation degrades the speech quality. In this case, the PCM code stream is transmitted on the A interface. Figure 2-315 Tandem Operation
To improve the quality of speech signals, Tandem Free Operation (TFO) is introduced to pass by the TC decoder when the originating MS and the terminating MS use the same speech version. The speech signal is coded at the originating MS and decoded at the terminating MS, and is transparently transmitted between the TCs at the two ends. Thus, the process of encoding and decoding by the TC is eliminated to improve the quality of the speech signal.
Figure 2-316 shows the TFO in which the speech signals are transparently transmitted between two MSs. Figure 2-316 TFO
After a TFO connection is successfully established, the TFO module inserts the TFO frame into the PCM code stream on the A interface according to a specific format. A TFO frame is the speech frame transmitted in stealing mode between TCs after TFO is successfully established. The peer TC searches the data received on the A interface for the TFO frame, converts the TFO frame into a TRAU frame (TRAU frame refers to the voice data transmitted between the BTS and the TC), and then sends the TRAU frame to the Abis interface. A TFO message is the inband signaling used for TFO negotiation between TCs. The TFO message is mainly used to exchange the parameter configurations concerning the TFO modules of the calling party and the called party in the TFO negotiation phase. The parameters involved are Speech Version, AMR ACS[F], AMR ACS[H], and AMR ACS[WB]. If the parameter configurations meet the requirement for establishing TFO, the TFO connection is established. TFO messages are transmitted in bit spacing scheme. For details, see 2.72.3.1 TFO Messages. You can enable the TFO function by setting TFO Switch to ENABLE.

2.72.3.1 TFO Messages
The TFO messages, transmitted in bit spacing scheme, are classified into the following types: TFO_REQ messages, TFO_ACK messages, IS_IPE messages, and other messages.
Classification of TFO Messages

l TFO_REQ messages A TFO_REQ message is used to request the activation of the TFO feature. It contains the activated speech version, activated AMR Family codec, supported speech version, and supported AMR Family codec. In Huawei GBSS, AMR family codec consists of FR AMR, HR AMR, and WB AMR. l TFO_ACK messages A TFO_ACK message is an acknowledgement to a TFO_REQ command. The activated speech version, activated AMR Family codec rate set, supported speech version, and supported AMR Family codec are contained in the TFO_ACK messages. l
Issue 08 (2011-09-30)
IS_IPE messages
The IS_IPE messages are classified into TFO_FILL messages, FO_TRANS messages, and TFO_NORMAL messages. TFO_FILL messages refer to the messages requesting the IPE to transparently transmit TFO messages. TFO_TRANS messages refer to the messages requesting the IPE to transparently transmit TFO frame messages. TFO_NORMAL messages refer to the messages requesting the IPE to restore normal processing. l Other messages TFO_DUP messages are used for a quick TFO connection establishment between the activated TC path and the peer TC path when a handover occurs. TFO_SYL messages, which indicate that the TFO frame is lost, are usually used for a quick TFO connection establishment when a handover occurs.
Transmission of TFO Messages

TFO messages are transmitted in bit spacing scheme. Specifically, TFO messages are used to replace the least significant bit in the first byte of every 16 PCM bytes. In this way, the impact on speech quality is minimized.
2.72.3.2 TFO Frame

Though the structure of the TFO frame is the similar to that of the TRAU frame, the two frames use different transmission modes. For details, see the 3GPP TS 48.060 and 3GPP TS 48.061. The TFO frame occupies the two least significant bits (LSBs) of the 8-bit PCM frame. The other six bits are still used for transmitting the decoded speech signals. That is, the decoder of the TRAU continues working even after TFO is activated. On receiving the TRAU frame on the Abis interface, the decoder performs decoding and A-law/ law conversion on the TRAU frame, and generates new data on the A interface by combining the six most significant bits of the TRAU frame with the TFO frame. The TFO frame is detailed as follows: l In the case of FR, EFR, FR_AMR, and WB_AMR, the two LSBs of each PCM frame are used to transmit the TFO frame, and the other six bits of each PCM frame are used to transmit the compressed PCM data. In the case of HR_AMR, the second LSB of each PCM frame is used to transmit the TFO frame, and some LSBs of the PCM frames are used to transmit the synchronization subframe. Other LSBs and the six most significant bits of the PCM frames are still used to transmit the PCM data that is compressed according to the A/ law. For HR, the LSB of the PCM is used to transmit the TFO frame, and the other seven bits are used to transmit the PCM data compressed according to the A/ law.
2.72.3.3 Prerequisites for the TFO Establishment

In TFO negotiation phase, the parameters of the TFO modules of the calling party and called party are exchanged through the TFO message. The related parameters are Speech Version and any of the following three parameters: AMR ACS[F], AMR ACS[H], and AMR ACS[WB]. TFO can be established only when the parameters meet the following requirements:
l l
The speech version of the calling party is compatible with that of the called party. The Local Active Codec Set (LACS) and Distant Active Codec Set (DACS) meet the requirements of contiguity rule and high mode rule.
The Speech Version of the Calling Party is Compatible with That of the Called Party
If the TFO module determines that the speech version of the calling party is not compatible with that of the called party after the TFO message negotiation, you can enable the TFO Option Switch to enable the function of speech version optimization. The TFO module chooses the optimal common speech version from the common speech versions of both LACS and DACS, requests the BSC to initiate intra-cell handovers, updates the speech version, and adapts itself to the TFO establishment. Table 2-210 describes the compatibility between the speech versions and priorities of the speech versions. Table 2-210 TFO compatibility and speech versions Speech Version WB AMR FR AMR HR AMR EFR FR HR WB AMR 1 FR AMR 2 4 HR AMR 4 5 EFR 3 FR 6 HR 7
The voice quality level is inversely proportional to the speech quality. The lower the voice quality level, the higher the voice quality. TFO can be established between the FR AMR and HR AMR. "-" indicates that TFO cannot be established between speech versions.
NOTE
TFO speech version optimization is an optional function of TFO. When TFO speech version optimization is enabled, handovers in the GSM system may increase.
The LACS and DACS Meet the Requirements of Contiguity Rule and High Mode Rule
If TFO is established with the AMR Family Codec, the setting of AMR ACS[F], AMR ACS [H], or AMR ACS[WB] at both the BSCs should meet the requirements of contiguity rule and high mode rule. Contiguity rule: The Optimized Active Codec Set (OACS) must be a contiguity set of the LACS and DACS, and must contain the lowest rates of the LACS and DACS. LACS is the Local Active Codec Set, DACS is the Distant Active Codec Set, and OACS is the active codec set after TFO is established.
High mode rule: The highest mode in the OACS is not lower than one mode below the minimum of the highest modes of both ACS. If the requirements of the two rules are not met, you can set Is RATSCCH Function Enabled to ENABLE to enable TFO AMR Family ACS optimization. In this way, the requirement for AMR Family TFO establishment is met through the dynamic change of the ACS of the current call. l If one end supports ACS optimization and the other end does not, then: The end that supports ACS optimization dynamically changes the ACS to the codec rate of the peer end. l If the two ends support ACS optimization, then: The optimal ACS is calculated based on the supported codec set, robustness, and voice quality, and then the TFO is established. Robustness is the capability of a system to continue function effectively even with changes in internal structure or external environment.
NOTE
When the LACS is the same as the DACS, the contiguity rule and high mode rule are met. AMR Family TFO ACS optimization is an optional function of TFO. You can change the active codec sets at the two ends so that they meet the requirements of contiguity rule and high mode rule. Thus the requirement for TFO establishment is met. WB AMR does not support ACS optimization.
2.72.3.4 TRAU Operating Process in TFO Mode

This describes the TRAU operating processes in ideal and abnormal cases.
TRAU Operating Process in Idea Case (Simple Mode)

1. 2. The TRAU is activated and the encoder and decoder are turned on at the same time. The TRAU turns on the TFO module, sends a TFO_REQ message to the MSC, and checks on the A interface whether there is a TFO_REQ or TFO_ACK message sent by the remote end. After the TFO message negotiation, the TFO determines whether the speech version at the two BSC ends is compatible with the active code family. If the speech version at the two BSC ends is compatible with the active code family, the TRAU starts uplink TFO. That is, the TRAU starts to send the TFO frame, and embeds the TTFO_TRANS message in the TFO frame to control the transparent transmission of the TFO frame by the IPE. After the TFO frame is received from the remote end on the A interface, the TFO is established. The TRAU starts downlink TFO, that is, replaces the TRAU frame with the TFO frame on the A interface. In this way, the TC is passed by and TFO is realized. Thus, the voice quality is improved. The TRAU turns off the decoder and TFO protocol processor.
3.
4.
5.
Handling in Abnormal Cases

l After the TC channel is activated, the TRAU sends TFO_REQ messages continuously. If there is no response when the number of TFO_REQ messages exceeds the threshold defined in TS 28.062, the TRAU stops sending TFO messages but continues monitoring the TFO messages on the A interface until the TC channel is released.
Issue 08 (2011-09-30)
l l
If the speech versions of the TC at the two ends do not match, the TRAU aborts the establishment of TFO links and restores normal operation. If the LACS (Local Active Codec Set) and DACS do not meet the requirements of contiguity rule and highest mode rule, the TRAU aborts the establishment of TFO and restores normal working mode. If error codes are generated when the TFO frame or TFO message is transmitted, the bit synchronization and CRC are affected. As a result, the peer TC cannot receive the TFO frame or TFO message. Loss of TFO frame synchronization bit In normal cases, the loss of TFO frame synchronization is mainly caused by an instant channel handover. The TRAU, however, cannot obtain the information about channel handover. Therefore, if there is loss of TFO frame synchronization, that is, if the TFO Frame cannot be found, the TRAU does not quit the TFO activation status, but tries to establish a connection with the remote TRAU through the TFO_SYL message. The remote TRAU responds with the TFO_DUP message. If the connection is established within a specified period, the call is retained in the current state; otherwise, the local TRAU considers that TFO is disconnected and quits the TFO status.
2.72.3.5 DTX and VQE After the TFO Establishment Impact of TFO Establishment on DTX
After TFO is established, the downlink TC code does not exist. Therefore, the codec of the downlink DTX is categorized into non-AMR Family codec and AMR Family codec. l Non-AMR Family codec After TFO is established, the TFO replaces the Bad Frame Indication (BFI) with the Silence Descriptor (SID) if the uplink DTX is enabled and the downlink DTX is disabled. In other scenarios, the TFO transparently transmits the TFO frame, converts the received TFO frame into TRAU frame, and sends the TRAU frame to the MS at the receiving end. l AMR Family codec The TC transparently transmits the TFO frame, converts the received TFO frame to TRAU frame, and sends the TRAU frame to the MS at the receiving end. Then, the BTS processes the DTX on the Um interface.
Impact of TFO Establishment on VQE

After TFO is established, the TCs at the two ends are passed by. Therefore, the function of Voice Quality Enhancement (VQE) is also passed by. The TRAU, however, still provides the function of echo detection. When the TFO Option Switch is enabled, TFO is forcibly disabled if any echo is detected to ensure that the voice quality does not deteriorate.
2.72.3.6 TFO Voice Quality Improvement

Speech codec is a compression process that deteriorates the voice quality. With TFO enabled, one codec is eliminated. In this way, the voice quality is improved. The codec with a lower rate deteriorates the voice quality to a small extent. Therefore, the voice quality of AMR, EFR, FR, and HR is improved to a great extent after TFO is enabled.
For WB_AMR, in A over TDM mode, the sampling frequency of the PCM code stream must be decreased to 8 kHz before being sent over the A interface. The spectrum information on speech signals thus suffers a loss. In this case, the speech quality of a WB AMR call is worse than the speech quality of an AMR FR call. After TFO is established, the PCM code stream decrease can be passed by. In this way, the spectrum information on speech signals retains and the speech quality is improved.
2.72.4 Parameters
This chapter describes the parameters related to TFO. For the meaning of each parameter, see Table 2-211. For the default value, value ranges, and MML commands of each parameter, see Table 2-212. Table 2-211 Parameter description (1) Parameter Speech Version Description Speech version supported by a cell. Whether to enable the Tandem Free Operation (TFO) function on the BTS through a CHANNEL ACTIVATION or MODE MODIFY message. This parameter specifies whether to enable the Tandem Free Operation (TFO) function. If the voice quality of an ongoing MS-to-MS call is bad, the TFO function can be enabled to improve end-to-end voice quality. The TFO function cannot be used to improve the voice quality of an MS-to-PSTN call. Active coding set (ACS)[WB], indicates a set of wide-band coding rates currently available for calls. The AMR is a set of multiple speech coding and decoding rates. Modifying the default coding rates will affect speech quality when TrFO or TFO is in use. Active coding set (ACS)[F], indicates a set of full-rate coding rates currently available for calls. The AMR is a set of multiple speech coding and decoding rates. Modifying the default coding rates will affect speech quality when TrFO or TFO is in use. Active coding set (ACS)[H], indicates set of half-rate coding rates currently available for calls. The AMR is a set of multiple speech coding and decoding rates. Modifying the default coding rates will affect speech quality when TrFO or TFO is in use. AEC is an important measure to improve the speech quality. If the AEC works for a consecutive time that is longer than the value of this parameter, the TFO function is closed to provide a better speech quality. This parameter specifies whether the RATSCCH function is enabled during the call establishment procedure. RATSCCH is used to dynamically reconfigure the rate set of AMR while on a call. This parameter maps the versions of base stations.
TFO Switch
AMR ACS[WB]
AMR ACS[F]
AMR ACS[H]
TFO Option Switch
Is RATSCCH Function Enabled
Issue 08 (2011-09-30)
1176
Table 2-212 Parameter description (2) Parameter Defaul t Value FULL_ RATE_ VER1-1 &FULL _RATE _VER21&FUL L_RAT E_VER 3-0&H ALF_R ATE_V ER1-1& HALF_ RATE_ VER2-0 &HALF _RATE _VER30&FUL L_RAT E_VER 5-0 GUI Value Range Actual Value Range Uni t MML Comm and Impact
Speech Version
FULL_RATE _VER1, FULL_RATE _VER2, FULL_RATE _VER3, HALF_RATE _VER1, HALF_RATE _VER2, HALF_RATE _VER3, FULL_RATE _VER5
Full_rate_Ver 1, Full_rate_Ver 2, Full_rate_Ver 3, Half_rate_Ver 1, Half_rate_Ver 2, Half_rate_Ver 3, Full_rate_Ver 5
Non e
SET GCELL CCACC ESS (Option al) SET GCELL BASIC PARA (Option al)
Cell
TFO Switch
DISAB LE 6_60KB IT/ S-1&8_ 85KBIT / S-1&12 _65KBI T/S-1
DISABLE, ENABLE
Non e
Cell
AMR ACS[WB]
6_60KBIT/S, 8_85KBIT/S, 12_65KBIT/S
0~7
Non e
SET GCELL CCAM R (Option al)
Cell
Issue 08 (2011-09-30)
1177
Parameter
Defaul t Value 4_75KB IT/ S-1&5_ 15KBIT / S-0&5_ 90KBIT / S-1&6_ 70KBIT / S-0&7_ 40KBIT / S-1&7_ 95KBIT / S-0&10 _2KBIT / S-0&12 _2KBIT /S-1 4_75KB IT/ S-1&5_ 15KBIT / S-0&5_ 90KBIT / S-1&6_ 70KBIT / S-0&7_ 40KBIT / S-1&7_ 95KBIT /S-0
GUI Value Range
Actual Value Range
Uni t
MML Comm and
Impact
AMR ACS[F]
4_75KBIT/ S~0 5_15KBIT/ S~1 5_90KBIT/ S~2 6_70KBIT/ S~3 7_40KBIT/ S~4 7_95KBIT/ S~5 10_2KBIT/ S~6 12_2KBIT/S
4_75KBIT/S, 5_15KBIT/S, 5_90KBIT/S, 6_70KBIT/S, 7_40KBIT/S, 7_95KBIT/S, 10_2KBIT/S, 12_2KBIT/S
Non e
SET GCELL CCAM R (Option al)
Cell
AMR ACS[H]
4_75KBIT/ S~0 5_15KBIT/ S~1 5_90KBIT/ S~2 6_70KBIT/ S~3 7_40KBIT/ S~4 7_95KBIT/S
4_75KBIT/S, 5_15KBIT/S, 5_90KBIT/S, 6_70KBIT/S, 7_40KBIT/S, 7_95KBIT/S
Non e
SET GCELL CCAM R (Option al) SET TCPAR A (Option al)
Cell
TFO Option Switch
OFF
OFF(Off), ON (On)
OFF, ON
Non e
Board
Issue 08 (2011-09-30)
1178
Parameter
Defaul t Value
GUI Value Range
Actual Value Range
Uni t
MML Comm and SET GCELL CCAM R (Option al)
Impact
Is RATSCCH Function Enabled
DISAB LE
DISABLE, ENABLE
Non e
Cell
2.72.5 Counters
None.
2.72.6 Glossary

l l l l l l l l l l 3GPP 02.53 "Digital cellular telecommunication system (Phase 2+); Tandem Free Operation (TFO) of Speech Codecs; Service Description; Stage 1" 3GPP 03.53 "Digital cellular telecommunication system (Phase 2+); Tandem Free Operation (TFO) of Speech Codecs; Service Description; Stage 2" 3GPP 48.060 "In-band control of remote transcoders and rate adaptors for full rate traffic channels" 3GPP 48.061 "In band control of remote transcoders and rate adaptors for half rate traffic channels" 3GPP 28.062 "Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.73 Transmit Diversity

2.73.1 Introduction
2.73.1.1 Scope
This document describes transmit diversity and dynamic transmit diversity.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the transmit diversity feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02(2009-09-30)
01(2009-06-30)
Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 has no change.
2.73.2 Overview
In the radio propagation environment, transmit signals may be adversely affected by buildings and other obstacles. Transmit signals arrive at the receiving end in various ways, such as perpendicular incidence, reflections, and scattering. As the MS moves around, Rayleigh fading occurs because the transmit signals traveling through various paths are combined. Rayleigh fading leads to rapid fluctuation of the signal amplitude. Therefore, the signal quality is severely affected. Shadow fading and Rayleigh fading severely degrade the quality of received signals. The two types of fading are the major factors that result in the vulnerable radio link of the mobile communications. Transmit diversity can help to improve the quality of the signals received by the MS and reduce the effect of multipath fading. When Transmit Diversity is enabled, one baseband signal is transmitted through two RF channels. The combined signals in the multipath transmission are optimized. Thus, the impact of Rayleigh fading on the MS is reduced. In transmit diversity mode, the baseband signal of an MS is transmitted on two RF channels. As there is no correlation between the two antennas, the problems of dramatic change of signal level and QoS decrease due to multipath propagation are solved, thus improving the downlink coverage. Transmit Diversity improves the downlink signal quality, thus meeting the demanding requirements for radio communications in certain cases. In dynamic transmit diversity mode, the corresponding timeslots of the two TRXs in one doubletransceiver unit are set to transmit diversity, and other timeslots are set to non-transmit diversity. After the timeslots in transmit diversity mode are released, they can be set to non-transmit diversity. Dynamic Transmit Diversity makes full use of idle timeslots and improves the signal strength in areas with weak coverage, such as at cell edges, indoors, or in cars. Based on actual network conditions, adjustments can be made to achieve the balance between capacity and coverage. The resource utilization is increased and good quality services can be provided if required. The gain of Transmit Diversity is high in scenarios where multipath effects are evident. In scenarios where few obstacles exist (such as grassland and sea), Transmit Diversity may result in insignificant diversity gain.

2.73.3.1 Transmit Diversity
The two TRXs of the double-transceiver unit transmit the data of the same user, but there is delay or phase difference between the two transmit channels. When the output power of the two TRXs remains unchanged, 3 dB of transmit gain is achieved as the power superposes over the Um interface and doubles. In addition, a maximum of 1.5 dB of diversity gain can be achieved in various multipath environment. Therefore, when Transmit Diversity is enabled, 3 dB to 4.5 dB of downlink gain can be achieved. Figure 2-317 shows the working principles of Transmit Diversity enabled in a doubletransceiver unit. The signal from TRX0 is divided into two signals by the divider. Then, the two signals enter RF units TX1 and TX2 respectively. The signals are amplified by the RF units and then transmitted to the radio channels by the antenna.
Figure 2-317 Working principles of Transmit Diversity
2.73.3.2 Dynamic Transmit Diversity

Dynamic Transmit Diversity mainly applies to concentric cells. If the downlink coverage in the overlaid subcell is restricted, continuous coverage is impossible, and the capacity of the underlaid subcell is low. Thus, the underlaid subcell may be congested, whereas the overlaid subcell is idle. In transmit diversity mode, only one TRX in a double-transceiver unit is used, and the TRX utilization is low. Dynamic Transmit Diversity is timeslot-based. Normally, two TRXs in a double-transceiver unit work independently. The two channels with the same timeslot number on the two TRXs can work as a channel group if required. That is, the two channels can be converted into a channel group, and the channel group into two independent channels. This balances cost, capacity, and coverage.
NOTE
When a double-transceiver unit works in dynamic transmit diversity mode, the channels with the same timeslot number on the two TRXs in one double-transceiver unit form a transmit diversity channel group. The two channels must be TCHs (TCHF or TCHH). The channel with a smaller TRX number is the primary channel, and the channel with a greater TRX number is the secondary channel. The primary channel and the secondary channel are the channels with the same timeslot number on one double-transceiver unit. BCCHs, SDCCHs, PDCHs, and CBCHs cannot form a channel group. They can only be used as independent channels.
During channel assignment, the BSC searches for the optimal channels. After dynamic Transmit Diversity is enabled, the BSC determines whether the optimal channels can form a transmit diversity channel group if the transmit diversity channel group should be assigned. If a transmit diversity channel group can be formed, the BSC blocks the secondary channel. Then, the BSC assigns the channel group to the call. If the optimal channels cannot form a channel group, the BSC regards the channels as independent channels. If the optimal channels can form a channel group but one of them is occupied by a call, the BSC attempts to hand over the call to another channel. After the channel turns idle, a channel group is formed and then assigned to the call. In dynamic transmit diversity mode, the downlink-limited handover decision algorithm is added to determine whether the downlink signal strength is limited. If the downlink signal strength is limited and the serving cell supports dynamic transmit diversity, the call is handed over to an available channel group. If one of the two channels with the same timeslot number on one doubletransceiver unit is occupied by the call, the call on the other channel should be handed over to another idle channel.
When the downlink signal strength is increased to a certain level, the transmit diversity channel is not required. The BSC divides the channel group into two independent channels and maintains the call on the primary channel. At the same time, the BSC releases the secondary channel to increase the capacity of the cell.
NOTE
After dynamic Transmit Diversity is enabled, the BSC reserves most possible channel pairs that can form channel groups when assigning common independent channels.
With dynamic Transmit Diversity enabled in the overlaid subcell, the coverage of the overlaid subcell is expanded through the handover of calls in the vicinity of the edge to the overlaid subcell. This helps to balance the traffic between the overlaid subcell and that in the underlaid subcell. Dynamic Transmit Diversity is a software solution. That is, the hardware connections of the BTS in dynamic transmit diversity mode are the same as those in transmit diversity mode, and only the software needs to be upgraded.
2.73.4 Parameters
This chapter describes the parameters related to transmit diversity. For the meaning of each parameter, see Table 2-213. For the default value, value ranges, and MML commands of each parameter, see Table 2-214. Table 2-213 Parameter description (1) Parameter Description RF send mode of the TRX. The BTS3006C and BTS3002E do not support Wide Band Combining, Power Booster Technology, DPBT, or Transmitter Independent or Combining. The DBS3900 GSM GRRU does not support Wide Band Combining, Transmitter Independent or Combining, Power Booster Technology, or DPBT. The BTS3900 GSM and BTS3900A GSM do not support Transmitter Independent or Wide Band Combining. Cell type. Currently, the fast BTS construction is available for only GSM900 and DCS1800 cells.
Send Mode Cell Type
Issue 08 (2011-09-30)
1183
Table 2-214 Parameter description (2) Parameter Defa ult Valu e GUI Value Range NOCOM B(No Combina tion), PBT (PBT), WBAND COMB (Wideba nd Combina tion), DIVERS ITY (Transmi t Diversity ), DDIVER SITY (Dynami c Transmit Diversity ), DPBT (DPBT), DTIC (Transmi t Independ ency or Combina tion), NONE (none) GSM900 (GSM90 0), DCS180 0 (DCS180 0) Actual Value Range U nit MML Command Impact
Send Mode
NON E
NOCOM B, PBT, WBAND COMB, DIVERS ITY, DDIVER SITY, DPBT, DTIC, NONE
No ne
SET GTRXDEV (Optional)
TRX
Cell Type
None
GSM900 , DCS180 0
No ne
ADD GCELLQUI CKSETUP (Mandatory)
Cell
Issue 08 (2011-09-30)
1184
2.73.5 Counters
None.
2.73.6 Glossary

2.74 TRX Cooperation

2.74.1 Introduction
2.74.1.1 Scope
This document describes BCCH TRX cooperation, baseband FH TRX cooperation, and TRX channel cooperation.


This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the TRX cooperation feature of a specific product version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.74.2 Overview
TRX cooperation means that when a TRX in a cell is faulty, the BSC designates another available TRX in the cell to replace the original TRX. TRX cooperation is categorized into the following types: l BCCH TRX cooperation When the main BCCH TRX fails, the BSC selects a normal TRX as the new main BCCH TRX according to the TRX cooperation algorithm to ensure that the cell is functional. When the fault on the original main BCCH TRX is rectified, the BSC can switch the main BCCH back to the original TRX. l Baseband FH TRX cooperation Baseband FH TRX cooperation is a function enabled by the BSC when a TRX involved in FH is faulty in a cell whose Frequency Hopping Mode is set to BaseBand_FH(Baseband frequency hopping). In such a case, the BSC removes the faulty TRX from the FH group,
whereas other TRXs in the FH group remain BaseBand_FH(Baseband frequency hopping). l TRX channel cooperation When the physical TRX board or channel bound to a logical TRX fails, the BTS binds the logical TRX to a normal TRX board or channel, thus ensuring that the logical TRX works normally. TRX cooperation ensures that the cell works normally when faults occur on the TRXs in the cell.
NOTE
From the time of service disruption due to TRX failure to the time of service recovery after TRX cooperation, the system determines whether TRX cooperation is required, hands over the calls in the faulty cell to another cell, and re-initializes the cell. TRX cooperation is not triggered within a certain period after the cell is initialized. The period is determined by Aiding Delay Protect Time. By default, Aiding Delay Protect Time is set to 15 minutes.

2.74.3.1 BCCH TRX Cooperation
When the main BCCH TRX in a cell is unavailable, the BSC designates another available TRX in the cell to replace the original main BCCH TRX, thus ensuring that the cell is functional. When the fault in the original main BCCH TRX is rectified, the BSC can switch the main BCCH back to the original TRX. BCCH TRX cooperation involves the following: l l l l BCCH TRX cooperation BCCH TRX switchback BSC-controlled BCCH TRX cooperation BSC-collaborated BCCH TRX cooperation
BCCH TRX cooperation can be classified into the following types by the initiator:
?.1. BSC-controlled BCCH TRX cooperation

BSC-controlled BCCH TRX cooperation means that the BSC controls BCCH TRX cooperation without involving the BTS. BSC-controlled BCCH TRX cooperation involves the following: l l BSC-Controlled BCCH TRX Cooperation BSC-Controlled BCCH TRX Switchback
BSC-Controlled BCCH TRX Cooperation

BCCH TRX cooperation is triggered when the BTS reports the status change message regarding the following: l l The operating status of the current main BCCH is DISABLED. The availability status of the current main BCCH must be one of those listed in Table 2-215.
Issue 08 (2011-09-30)
Table 2-215 Availability status and meaning Availability Status POWER_OFF FAILED NOT_INSTALLED_REAL DEPENDENCY Description Indicates that the equipment is powered off. Indicates that the equipment fails. Indicates that the equipment is not installed. Indicates that the equipment is unavailable because of other faulty equipment.
The cell ID in the BCCH TRX cooperation message is used to identify the cell where BCCH TRX cooperation is performed. BCCH TRX cooperation can be performed concurrently in different cells. The process of BCCH TRX cooperation is as follows: 1. When a cell satisfies the conditions for BCCH TRX cooperation, the BSC starts a protection timer with the duration as one minute.
NOTE
The 1-minute protection timer can avoid TRX cooperation caused by unstable TRX status.
2.
After the protection timer expires, the BSC checks whether the cell satisfies the conditions for TRX cooperation again. l If the cell satisfies the conditions, the BSC forcibly hands over all the calls in the cell and starts a 10-second timer. l If the cell does not satisfy the conditions, the BSC terminates the process of TRX cooperation.
3. 4.
After all the calls in the cell are handed over or the 10-second timer expires, the BSC selects an available TRX in the cell to replace the original main BCCH TRX. The BSC initializes the cell and sends the new configuration data to the BTS. In addition, the BSC exchanges the configuration data of the original main BCCH TRX with the configuration data of the cooperating TRX. Then, BCCH TRX cooperation is complete.
BSC-Controlled BCCH TRX Switchback

After the BCCH TRX cooperation, if the fault on the original main BCCH TRX in the cell is rectified, BCCH TRX switchback is performed. The configuration data of the two TRXs involved in TRX cooperation is adjusted, and the initial configuration data of the cell is restored. The process of BCCH TRX switchback is reverse to that of BCCH TRX cooperation. The differences between them are the triggering conditions and processing. TRX switchback is controlled by TRX Aiding Function Control. BCCH TRX switchback is triggered when the BTS reports a status change message indicating that the operating status of the original main BCCH is DISABLED. The cell ID in the BCCH TRX switchback message is used to identify the cell where BCCH TRX switchback is performed. BCCH TRX switchback can be performed concurrently in different cells. If the triggering conditions are satisfied, BCCH TRX switchback is performed. Finally, the initial configuration data before TRX cooperation is restored.
Algorithm for Selecting the Cooperating TRX

The TRX boards to which each logical TRX belongs differ in the frequency band and Power Type; therefore, selection of a cooperating TRX should satisfy certain conditions. l Mandatory conditions The original main BCCH TRX and the candidate TRX must be in the same BTS cabinet group. The TRX board bound to the original main BCCH TRX can exchange the frequency with the TRX board bound to the candidate TRX. The exchanged frequencies must belong to the frequency band supported by the TRX board. If the original main BCCH TRX or the candidate TRX is connected to the Power Boost Unit (PBU), the PBU must support the exchanged frequencies. The antenna feeder boards connected to the original main BCCH TRX and candidate TRX must support the exchanged frequencies. The antenna feeder boards include the Combing and Distribution Unit (CDU), Enhanced Duplexer Unit (EDU), DualDuplexer Unit for DTRU BTS (DDPU), Filter Combiner Unit for DTRU BTS (DFCU), and Filter Combiner Unit for DTRU BTS (DFCB). Besides the preceding conditions, the DFCU and DFCB must meet the requirements for the Absolute Radio Frequency Channel Number (ARFCN) difference. The requirements are as follows: For the frequencies on the 900/850 MHz band, the ARFCN difference must be at least 3. For the frequencies on the 1800/1900 MHz band, the ARFCN difference must be at least 2. The QTRU(Quadruple-Transceiver Unit) adopts the power sharing technology; therefore, the maximum power can be set to different values when the numbers of logical TRXs bound to the QTRU are different. If the TRX board of the original main BCCH TRX or the candidate TRX is a QTRU, the power of the TRX after BCCH TRX cooperation cannot be greater than the maximum power of the QTRU. l Condition for Selecting Preferable TRXs In a cell, multiple candidate TRXs may satisfy the mandatory conditions. These candidate TRXs are filtered to select an optimum cooperating TRX with the minimum impact on services. Table 2-216 lists the conditions for selecting preferable TRXs. The priorities of the conditions decrease from the top down. Table 2-216 Conditions for selecting preferable TRXs PRI 1 Condition for Selecting Preferable TRXs HW_Concentric Attribute Description The candidate TRX with the same concentric attribute as that of the original main BCCH TRX is preferably selected. That is, they are in an underlaid subcell or an overlaid subcell.
Issue 08 (2011-09-30)
1189
PRI 2
Condition for Selecting Preferable TRXs QTRU bandwidth
Description If the original main BCCH TRX or the candidate TRX is bound to a QTRU, the candidate TRX that meets the bandwidth requirement of every carrier frequency of the QTRU after frequency exchange is preferably selected. If neither the original main BCCH TRX nor the candidate TRX is bound to a QTRU, the condition is considered as satisfied.
Support of EDGE
The candidate TRX that has the same capability in supporting the EDGE as the original main BCCH TRX is preferably selected. That is, both of them support the EDGE or neither of them supports the EDGE. The candidate TRX that is the same as the original main BCCH TRX in the RF Receive Mode and Send Mode is preferably selected. If neither of the original main BCCH TRX nor the candidate TRX supports the RF Receive Mode and Send Mode, this condition is considered as satisfied.
RF send and receive modes of the TRX
CBCH configuration
The candidate TRX that is not configured with the CBCH is preferably selected. The candidate TRX that is not configured with the PDCH is preferably selected.
PDCH configuration
Do as follows to select the cooperating TRX based on the conditions listed in Table 2-216: 1. Apply the condition with the highest priority to filter all the non-main BCCH TRXs in the cell. l If only one logical TRX satisfies the condition after filtering, the logical TRX is selected as the cooperating TRX.
Issue 08 (2011-09-30)
1190
l If multiple logical TRXs satisfy the condition, these logical TRXs are used in the next round of filtering, as described in step 2. l If no logical TRX satisfies the condition, all logical TRXs are used in the next round of filtering, as described in step 2. 2. Apply the condition with the priority one level lower to filter the logical TRXs available for further filtering. l If only one logical TRX satisfies the condition after filtering, the logical TRX is selected as the cooperating TRX. l If multiple logical TRXs or no logical TRX satisfies the condition after filtering, repeat step 2. l If multiple logical TRXs satisfy the condition of the lowest priority, select any one of these logical TRXs as the cooperating TRX.
?.2. BSC-Collaborated BCCH TRX Cooperation

BSC-collaborated BCCH TRX cooperation is performed by the BSC and the BTS. The fundamentals are the same as those of BSC-controlled BCCH TRX cooperation. The difference between them is that the BTS initiates BCCH TRX cooperation and selects the cooperating TRX in BSC-collaborated BCCH TRX cooperation. The BSC only exchanges the configuration data of the original main BCCH TRX with the configuration data of the cooperating TRX upon the cooperation request of the BTS. BSC-collaborated BCCH TRX cooperation involves the following: l l BSC-collaborated BCCH TRX cooperation BSC-collaborated BCCH TRX switchback
BSC-Collaborated BCCH TRX Cooperation

The triggering conditions of BSC-collaborated BCCH TRX cooperation are the same as those of BSC-controlled BCCH TRX cooperation. When the BTS detects that the main BCCH satisfies the following conditions, BCCH TRX cooperation is triggered: l l The operating status of the current main BCCH is DISABLED. The availability status of the current main BCCH must be one of those listed in Table 2-217. Table 2-217 Availability status and meaning Availability Status POWER_OFF FAILED NOT_INSTALLED_REAL DEPENDENCY Meaning Indicates that the equipment is powered off. Indicates that the equipment fails. Indicates that the equipment is not installed. Indicates that the equipment is unavailable because of other faulty equipment.
The process of BSC-collaborated BCCH TRX cooperation is as follows:

1.
When a cell satisfies the conditions for BSC-collaborated BCCH TRX cooperation, the BTS starts a protection timer with the duration as two minutes.
NOTE
2. 3.
After the protection timer expires, the BTS sends a request to the BSC for forcibly handing over all the calls in the cell and starts a 10-second timer. After the handovers of all the calls in the cell are complete or the 10-second timer expires, the BTS selects a functional cooperating TRX in the cell and sends a TRX cooperation request to the BSC. The BSC initializes the cell and delivers the new configuration data to the BTS. In addition, the BSC exchanges the configuration data of the original main BCCH TRX with the configuration data of the cooperating TRX. Then, BCCH TRX cooperation is complete.
4.
BSC-Collaborated BCCH TRX Switchback

After BSC-collaborated BCCH TRX cooperation, if the fault on the original main BCCH TRX in the cell is rectified, BSC-collaborated BCCH TRX switchback is performed. The configuration data of the two TRXs involved in TRX cooperation is adjusted, and the initial configuration data of the cell is restored. The process of BCCH TRX switchback is reverse to that of BCCH TRX cooperation. The differences between them are the triggering conditions and processing. TRX switchback is controlled by TRX Aiding Function Control. The triggering conditions of BSC-collaborated BCCH TRX switchback are as follows: l l l The BTS detects that the operating status of the original main BCCH is ENABLED. TRX Aiding Function Control is set to TRX Aiding Not Allowed. The triggering conditions of TRX cooperation are not satisfied after dynamic configuration. If the main BCCH TRX is still faulty after BCCH TRX switchback, BCCH TRX cooperation is triggered again.
If the triggering conditions are satisfied, BCCH TRX switchback is performed. The process of BCCH TRX switchback is reverse to that of BCCH TRX cooperation. Finally, the initial configuration data before TRX cooperation is restored.

The TRX boards to which each logical TRX belongs differ in the frequency band and Power Type; therefore, selection of a cooperating TRX should satisfy certain conditions. l Mandatory conditions The original main BCCH TRX and the candidate TRX must have the same power type. The original main BCCH TRX and the candidate TRX must be the same in the RF Receive Mode and Send Mode. After TRX cooperation, the frequencies of the original main BCCH TRX must belong to the frequency band of the board that carries the candidate TRX. After TRX cooperation, the frequencies of the original main BCCH TRX must meet the bandwidth requirements of the board that carries the candidate TRX. The bandwidth consists of the tributary output bandwidth and the board input bandwidth. l
Issue 08 (2011-09-30)
Conditions for selecting preferable TRXs

In a cell, multiple candidate TRXs may satisfy the mandatory conditions. These candidate TRXs are filtered to select an optimum cooperating TRX with the minimum impact on services. Table 2-218 lists the conditions for selecting preferable TRXs. The priorities of the conditions decrease from the top down. Table 2-218 Conditions for selecting preferable TRXs Priority 1 Condition Diversity Meaning The candidate TRX that is the same as the original main BCCH TRX in the RF Receive Mode and Send Mode is preferably selected. If the Send Mode of the RF TRX is set to Diversity Transmitter, the candidate TRX whose diversity can work normally after TRX cooperation is preferably selected. 2 Frequency band The candidate TRX whose frequencies are on the frequency band of the board that carries the original main BCCH TRX is preferably selected. The candidate TRX whose frequencies meet the bandwidth requirement of the board that carries the original main BCCH TRX is preferably selected. The candidate TRX that is not configured with the CBCH is preferably selected. The candidate TRX that is not configured with the PDCH is preferably selected.
Bandwidth
CBCH configuration
PDCH configuration
Do as follows to select the cooperating TRX based on the conditions listed in Table 2-218: 1. Apply the condition with the highest priority to filter all the non-main BCCH TRXs in the cell. l If only one logical TRX satisfies the condition after filtering, the logical TRX is selected as the cooperating TRX. l If multiple logical TRXs satisfy the condition, these logical TRXs are used in the next round of filtering, as described in step 2. l If no logical TRX satisfies the condition, all logical TRXs are used in the next round of filtering, as described in step 2.
2.
Apply the condition with the priority one level lower to filter the logical TRXs available for further filtering. l If only one logical TRX satisfies the condition after filtering, the logical TRX is selected as the cooperating TRX. l If multiple logical TRXs or no logical TRX satisfies the condition after filtering, repeat step 2. l If multiple logical TRXs satisfy the condition of the lowest priority, select any one of these logical TRXs as the cooperating TRX.
2.74.3.2 Baseband FH TRX Cooperation

Baseband FH TRX cooperation is a function enabled by the BSC when a TRX involved in FH is faulty in a cell whose Frequency Hopping Mode is set to BaseBand_FH(Baseband frequency hopping) or RF_FH(RF frequency hopping). In such a case, the BSC removes the faulty TRX from the FH group, whereas other TRXs in the FH group remain BaseBand_FH (Baseband frequency hopping). After the fault is rectified, the BSC enables the TRX to join the FH group and involve in baseband FH again. Baseband FH TRX cooperation involves the following: l l Baseband FH TRX Cooperation Baseband FH TRX Switchback
Baseband FH TRX Cooperation

Baseband FH TRX cooperation can be performed only in baseband FH cell when any of the following conditions is satisfied: l l BCCH TRX cooperation is performed in the cell. The BTS reports the status change message indicating that the operating status of the TRX involved in baseband FH is DISABLED and the availability status of the TRX involved in baseband FH is one of those listed in Table 2-219. Table 2-219 Availability status and meaning Availability Status POWER_OFF FAILED NOT_INSTALLED_REAL DEPENDENCY Description Indicates that the equipment is powered off. Indicates that the equipment fails. Indicates that the equipment is not installed. Indicates that the equipment is unavailable because of other faulty equipment.
The cell ID in the baseband FH TRX cooperation message is used to identify the cell where baseband FH TRX cooperation is performed. Baseband FH TRX cooperation can be performed concurrently in different cells. The process of baseband FH TRX cooperation is as follows: 1. When a cell satisfies the conditions for baseband FH TRX cooperation, the BSC starts a protection timer with the duration as one minute.
Issue 08 (2011-09-30)

NOTE
2.
After the protection timer expires, the BSC checks whether the cell satisfies the conditions for TRX cooperation again. l If the cell satisfies the conditions, the BSC forcibly hands over all the calls in the cell and starts a 10-second timer. l If the cell does not satisfy the conditions, the BSC terminates the process of TRX cooperation.
3.
After all the calls in the cell are handed over or the 10-second timer expires, the BSC removes the frequency of the faulty TRX from the MA list and adjusts the MAIO of other TRXs in the FH group. Meanwhile, other TRXs in the FH group remain BaseBand_FH (Baseband frequency hopping). The BSC initializes the cell and sends new configuration data to the BTS.
4.
Baseband FH TRX Switchback

When the faults in the baseband FH TRX in the cell are rectified, the BSC reverts the FH mode of the cell to Baseband FH. TRX switchback is controlled by TRX Aiding Function Control. If some faulty TRXs in a baseband FH group are restored, the system takes actions according to the setting of the parameter Switchback Policy of Baseband FH Mutual Aid. If the parameter is set to ALL(All), the system performs baseband FH TRX switchback after all the faulty TRXs in the FH group are restored. If the parameter is set to PART(Part), the system performs baseband FH TRX switchback after any of the faulty TRXs in the FH group is restored. After the switchback, the FH group remains in the state of baseband FH TRX cooperation. In such a case, the FH group contains only the TRXs in the normal state. The faulty TRXs remain NO_FH (No frequency hopping). After all the faulty TRXs are restored, the fault is rectified. The process of baseband FH TRX switchback is reverse to that of baseband FH TRX cooperation. The differences between them are the triggering conditions and processing. Baseband FH TRX switchback can be performed only in the baseband FH cell and is triggered by the required status change message reported from the BTS. The object in the baseband FH TRX switchback message must be of the BT level and must be the TRX involved in the baseband FH. The operating status of the original baseband FH TRX must be ENABLED. The cell ID in the baseband FH TRX switchback message is used to identify the cell where baseband FH TRX switchback is performed. Baseband FH TRX switchback can be performed concurrently in different cells.
2.74.3.3 TRX Channel Cooperation

When the physical TRX board or channel bound with a logical TRX fails, the BTS binds the logical TRX to a normally working TRX board or channel, thus ensuring that the logical TRX works normally. In TRX channel cooperation, the parameters of the logical TRX are not changed; however, the physical TRX board or channel bound to the logical TRX is changed. If the physical TRX board or channel that is bound to the logical TRX of the main BCCH fails, the BTS can also perform TRX channel cooperation to ensure that the logical TRX works normally. Therefore, TRX channel cooperation can implement the functions of BCCH TRX cooperation. TRX channel cooperation is performed by the BTS independently without the BSC. TRX channel cooperation involves the following:
l l
TRX channel cooperation TRX channel switchback
TRX Channel Cooperation

The triggering condition of TRX channel cooperation is the same as that of BSC-collaborated BCCH TRX cooperation. If the original main BCCH TRX has the LAPD alarm or is manually blocked, TRX channel cooperation is not performed.
TRX Channel Switchback

The triggering condition of TRX channel switchback is the same as that of BSC-collaborated BCCH TRX switchback.

If no TRXs on the board meet the requirements for BCCH TRX cooperation, a TRX on the antenna tributary is bound to the TRX on the tributary of the main BCCH TRX, thus ensuring that the main BCCH TRX can work normally. The algorithm for selecting a TRX on the board is the same as the algorithm for selecting the cooperating TRX in BSC-collaborated BCCH TRX cooperation. The algorithm of the cooperation between the TRX on the antenna tributary and the TRX on the tributary of the main BCCH TRX is described as follows: l Mandatory conditions The 3G TRX is not configured on the tributary of the original main BCCH TRX and the candidate tributary. The tributary of the original main BCCH TRX and the candidate tributary must belong to the same cell. The board of the tributary that carries the original main BCCH TRX is the same as the board of the candidate tributary in the frequency band. The number of TRXs configured on the candidate tributary must be the same as the number of TRXs configured on the tributary of the main BCCH TRX. The cooperating TRX must meet the requirement of the candidate tributary for the maximum output power. l Conditions for selecting preferable TRXs Multiple channels or boards may satisfy the mandatory conditions. These channels or boards are filtered to select an optimum channel or board as the cooperating channel or board based on the conditions listed in Table 2-220. The priorities of the conditions decrease from the top down.
Issue 08 (2011-09-30)
1196
Table 2-220 Conditions for selecting preferable channels or boards Priority 1 Condition for Selecting Preferable TRXs Meaning
Bandwidth of the original main The original main BCCH TRX BCCH TRX should meet the bandwidth requirement of the board after TRX channel cooperation. Bandwidth of the cooperating channel The cooperating channel should meet the bandwidth requirement of the board that carries the original main BCCH TRX after TRX channel cooperation. If the RF Send Mode of the logical TRX bound to the original main BCCH is Diversity Transmitter, the diversity should meet the bandwidth requirement of the cooperating channel after TRX channel cooperation. If the RF Send Mode of the cooperating channel is Diversity Transmitter, the diversity should meet the bandwidth requirement of the cooperating channel after TRX channel cooperation.
Diversity bandwidth when the RF Send Mode of the logical TRX bound to the original main BCCH is Diversity Transmitter
Diversity bandwidth when the RF Send Mode of the cooperating channel is Diversity Transmitter
2.74.4 Parameters
This chapter describes the parameters related to TRX cooperation. For the meaning of each parameter, see Table 2-221. For the default value, value ranges, and MML commands of each parameter, see Table 2-222.
Issue 08 (2011-09-30)
1197
Table 2-221 Parameter description (1) Parameter Description This parameter specifies the frequency hopping mode of a cell. When this parameter is set to "NO_FH", all the TRXs of the cell do not join in frequency hopping. When this parameter is set to "BaseBand_FH", the cell is in baseband frequency hopping mode. In this case, there can be TRXs that do not join in frequency hopping on the cell. When this parameter is set to "RF_FH", the cell is in RF frequency hopping mode. In this case, there can be TRXs that do not join in frequency hopping on the cell. When this parameter is set to "Hybrid_FH", the cell is in hybrid frequency hopping. In this case, some TRXs on the cell must join in baseband frequency hopping, some cells on the cell must join in RF frequency hopping, and some cells on the cell must not join in frequency hopping. Delay time for mutual-aid detection on a cell after the cell is initialized. When the cell initialization has just finished, the cell is in an unstable state. Mutual-aid detection at this time may cause a wrong decision. Therefore, this parameter is used for specifying proper delay. Whether TRX mutual aid is enabled for the BSC6900. TRX mutual aid is classified into main BCCH mutual aid and baseband frequency hopping (FH) mutual aid. If main BCCH mutual aid is enabled, the BSC6900 can switch a faulty main BCCH TRX over to a functional TRX in the cell. When the original main BCCH TRX recovers, it can be switched back based on the parameter setting. If baseband FH mutual aid is enabled, the BSC6900 can remove a faulty TRX from the baseband FH group to ensure the proper FH. The removed TRX will not participate in frequency hopping. When the removed TRX recovers, the BSC6900 determines whether to switch the TRX back to the baseband FH group according to the value of the "Switchback Policy of Baseband FH Mutual Aid" parameter. If the parameter is set to TRXAid_NotAllow, TRX mutual aid is not allowed. If the parameter is set to AllowReForbid, TRX mutual aid is allowed, but TRX switchback is not allowed. If the parameter is set to AllowReImmed, TRX mutual aid is allowed, and the faulty TRX is switched back immediately when conditions for TRX switchback are met. If the parameter is set to AllowReCheckRes, TRX mutual aid is allowed, and the faulty TRX is switched back when conditions for TRX switchback are met in the specified resource check period. Maximum power supported by the TRX. The macro BTSs and BTS3002C mini BTS support different power types. If this parameter is not set, the actual power type of the TRX board is used.
Frequency hopping mode
Aiding Delay Protect Time
TRX Aiding Function Control
Power Type
Issue 08 (2011-09-30)
1198
Parameter
Description RF receive mode of the TRX. The BTS3012, BTS3012AE, BTS3012II, BTS3006C, and BTS3002E do not support Main Diversity. The DBS3900 GSM and BTS3900 GSM support Four Diversity Receiver and Main Diversity. RF send mode of the TRX. The BTS3006C and BTS3002E do not support Wide Band Combining, Power Booster Technology, DPBT, or Transmitter Independent or Combining. The DBS3900 GSM GRRU does not support Wide Band Combining, Transmitter Independent or Combining, Power Booster Technology, or DPBT. The BTS3900 GSM and BTS3900A GSM do not support Transmitter Independent or Wide Band Combining. Mutual-aid changeback policy of baseband frequency hopping (FH). If multiple TRXs in a baseband FH group are faulty and changeback is needed after mutual aid of the baseband FH TRXs occurs: If you choose ALL, mutual-aid changeback is implemented after all the TRXs in the FH group recover; if you choose PART, as long as any of the faulty TRXs recovers, it is changed back at once and added to the FH group.
Receive Mode
Send Mode
Switchback Policy of Baseband FH Mutual Aid
Table 2-222 Parameter description (2) Paramete r Default Value GUI Value Range NO_FH (No frequency hopping), BaseBand _FH (Baseband frequency hopping), RF_FH (RF frequency hopping), Hybrid_F H(Hybrid frequency hopping) Actual Value Range Unit MML Comman d Impact
Frequency hopping mode Aiding Delay Protect Time

Issue 08 (2011-09-30)
NO_FH
NO_FH, BaseBand _FH, RF_FH, Hybrid_F H
None
SET GCELLH OPTP (Optional) SET GCELLH OPQUIC KSETUP (Mandator y) SET GCELLS OFT (Optional)
Cell
15
1~60
1~60
min
Cell
1199
Paramete r
Default Value
GUI Value Range TRXAid_ NotAllow (TRX Aiding Not Allowed), AllowReF orbid (Allowed & Recover Forbidden ), AllowReI mmed (Allowed & Recover Immediate ly), AllowReC heckRes (Allowed & Recover When Chk Res)
Actual Value Range
Unit
MML Comman d
Impact
TRX Aiding Function Control
AllowReC heckRes
TRXAid_ NotAllow, AllowReF orbid, AllowReI mmed, AllowReC heckRes
None
SET GCELLC CACCES S (Optional)
Cell
Issue 08 (2011-09-30)
1200
Paramete r
Default Value
GUI Value Range 80W (80W), 63W (63W), 60W (60W), 55W (55W), 50W (50W), 45W (45W), 40W (40W), 31W (31W), 30W (30W), 27W (27W), 26W (26W), 25W (25W), 24W (24W), 21W (21W), 20W (20W), 19W (19W), 18W (18W), 17W (17W), 16W (16W), 15W (15W), 14W (14W), 13_3W (13.3W), 13W (13W), 12_5W (12.5W),
Actual Value Range 80W, 63W, 60W, 55W, 50W, 45W, 40W, 31W, 30W, 27W, 26W, 25W, 24W, 21W, 20W, 19W, 18W, 17W, 16W, 15W, 14W, 13_3W, 13W, 12_5W, 12W, 11_5W, 11W, 10W, 9_5W, 9W, 8_5W, 8W, 7_5W, 7W, 6_5W, 6W, 5_5W, 5W, 4_5W, 4W, 3_7W, 3_1W, 3W, 2_5W, 2W, 200mW, DEFAUL T
Unit
MML Comman d
Impact
Power Type
DEFAUL T
None
TRX
Issue 08 (2011-09-30)
1201
Paramete r
Default Value
GUI Value Range 12W (12W), 11_5W (11.5W), 11W (11W), 10W (10W), 9_5W (9.5W), 9W(9W), 8_5W (8.5W), 8W(8W), 7_5W (7.5W), 7W(7W), 6_5W (6.5W), 6W(6W), 5_5W (5.5W), 5W(5W), 4_5W (4.5W), 4W(4W), 3_7W (3.7W), 3_1W (3.1W), 3W(3W), 2_5W (2.5W), 2W(2W), 200mW (200mW), DEFAUL T(Default)
Actual Value Range
Unit
MML Comman d
Impact
Issue 08 (2011-09-30)
1202
Paramete r
Default Value
GUI Value Range INDEPEN DENT (Independ ent Receiver), DIVIDIN G (Dividing Receiver), FOURDI VERSITY (Four Diversity Receiver), MAINDI VERSITY (Main Diversity), NONE (None)
Actual Value Range
Unit
MML Comman d
Impact
Receive Mode
NONE
INDEPEN DENT, DIVIDIN G, FOURDI VERSITY , MAINDI VERSITY , NONE
None
TRX
Issue 08 (2011-09-30)
1203
Paramete r
Default Value
GUI Value Range NOCOM B(No Combinati on), PBT (PBT), WBAND COMB (Wideban d Combinati on), DIVERSI TY (Transmit Diversity), DDIVERS ITY (Dynamic Transmit Diversity), DPBT (DPBT), DTIC (Transmit Independe ncy or Combinati on), NONE (none)
Actual Value Range
Unit
MML Comman d
Impact
Send Mode Switchbac k Policy of Baseband FH Mutual Aid
NONE
NOCOM B, PBT, WBAND COMB, DIVERSI TY, DDIVERS ITY, DPBT, DTIC, NONE
None
SET GTRXDE V (Optional) SET GCELLC CACCES S (Optional)
TRX
ALL
ALL(All), PART (Part)
ALL, PART
None
Cell
2.74.5 Counters
2.74.6 Glossary
Issue 08 (2011-09-30)
1204

2.75 VGCS/VBS
2.75.1 Introduction
2.75.1.1 Scope
This document describes the technologies related to VGCS/VBS, eMLPP in VGCS/VBS, and enhancement of VGCS/VBS in the GSM-R system.


This section provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to a change in the VGCS/VBS feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows: l
Issue 08 (2011-09-30)
02(2009-09-30)
01(2009-06-30)
02 (2009-09-30)
This is the second commercial release of GBSS9.0. Compared with issue 01 (2009-06-30) of GBSS9.0, issue 02 (2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Change Description The co-networking application scenario of GSM-R services and traditional GSM services is added. For details, see 2.75.4 Engineering Guidelines. The structure of the document is optimized. Parameter Change The added parameters are listed as follows: l Support Paging Message from Trunking MSC None.
Editorial change
01(2009-06-30)
This is the first commercial release of GBSS9.0. Compared with issue 01 (2009-04-30) of GBSS8.1, issue 01 (2009-06-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. None. Parameter Change None. None.
2.75.2 Overview
Compared with the traditional GSM system, the Railways Global System for Mobile communication (GSM-R) has new features, such as the Voice Group Call Service (VGCS), Voice Broadcast Service (VBS), and enhanced Multi-Level Precedence and Pre-emption (eMLPP) service. The GSM-R can provide diversified voice dispatch services required in the private network. l VGCS A VGCS call is a half-duplex group call that is established in a predefined area for multiple service subscribers to participate in. Simply, VGCS is a service where several persons talk and more persons listen. l
Issue 08 (2011-09-30)
VBS
VBS is a service where one person talks and several persons listen (no limitation on the number of listeners). The difference between VGCS and VBS is that only the initiator is allowed to talk during a VBS call and other members are always in the listening state. l eMLPP The eMLPP service provides seven priorities (A, B, 0-4). The GSM-R system is a digital railway dispatching communications system, which is used for the communication between the train dispatcher and the train drivers. Other independent and parallel radio systems, such as the flat shunting communications system, tunnel radio system, and maintenance radio system can be integrated into the GSM-R system to form a functionally mature integration system. In addition, the GSM-R transmission can be used to establish a general railway communications system on the basis of Auto Trail Control (ATC). The GSMR radio interface supports the maximum speed of 500 km/h, so GSM-R can be used for highspeed trains. If the core network of the traditional GSM network cannot be replaced, GSM-R services can be forwarded through the BSC of the traditional GSM network. In this manner, the network investment is reduced and the network construction is simplified.

2.75.3.1 VGCS
?.1. Overview
A VGCS call is a half-duplex group call that is established in a predefined area for multiple service subscribers to participate in. For better understanding of VGCS/VBS, key concepts related to VGCS/VBS are described as follows: l Group call channel The group call channel is similar to the traffic channel (TCH). When a VGCS or VBS call is established, each cell in the group call area is assigned an A-interface circuit and radio channel. In the group call area, the listening subscribers of the same VGCS call share the downlink of the channel. The VGCS subscribers preempt the uplink of the channel at different time points. This channel is called the group call channel. l l Group call member Any service subscriber or dispatcher participating in an ongoing VGCS call. Notification channel (NCH) The NCH is included in the BCCH. Similar to the paging channel, the NCH is used to broadcast the notification messages. During a VGCS or VBS call, the notification messages are periodically sent on the NCH so that the MS entering the group call area can join the call. l l
Issue 08 (2011-09-30)
Call initiator The service subscriber that initiates a VGCS or VBS call is called the call initiator. Talker
At a specific time, only one group call member is allowed to talk over the uplink of the group call channel. This group call member is called the talker. After the talker releases the channel, other group call members preempt the uplink of the channel. l Listener Except the talker, other group call members share and listen to the downlink of the group call channel. These group call members are called the listeners. l Group call area (GCA) Predefined in the network, the GCA is composed of one cell or a cluster of cells. The minimum unit of a GCA is a cell. l Group call reference If the group call members contain a mobile terminal, the group call reference consists of the 5-bit (decimal coding) GCA ID and the 3-bit (decimal coding) group ID. The group call reference is used for the dispatching terminal to initiate a VGCS call. If the group call members are only fixed-line terminals, the group call reference is the wired group call number. l Dispatcher The dispatcher is the group call member that is entitled to service dispatching. A dispatcher can be a mobile or fixed-line terminal. Each VGCS or VBS call has a maximum of five dispatchers. The dispatchers can participate in the call through the dedicated channel established by the network. l Anchor MSC/Relay MSC If a GCA covers several MSCs, the MSC responsible for call management is called the anchor MSC and the other MSCs are called the relay MSCs. The anchor MSC is responsible for the establishment of all the connections, including the connections to the specified cells under the MSC, to the related relay MSCs, and to the dispatchers. The anchor MSC also distributes speech signals. Only one link is required between each relay MSC and the anchor MSC. Each relay MSC distributes the downlink speech signals to all the cells under the MSC. l Notification response If the following conditions are met, the MS assigns this cell the group call channel by starting the notification response procedure: First, the cell is not assigned the group call channel. Second, the cell has a VGCS subscriber or a VGCS subscriber is reselected to the cell from another cell. Third, the NCH notification message does not contain the channel description. Fourth, a VGCS subscriber needs to join the VGCS call. The members of a VGCS call are classified into dispatchers and service subscribers. l Dispatcher A VGCS call has a maximum of five dispatchers, which can be fixed-line or mobile subscribers. In a VGCS call, dispatchers participate in the speech conversation through a dedicated channel that is established by the network. l Service subscriber Mobile subscriber that subscribes to the VGCS. In a VGCS call, a destination service subscriber participates in the speech conversation through the voice group call channel in the group call area. In a VGCS call, only one service subscriber and a maximum of five dispatchers are allowed to talk simultaneously at any specific time. A listening service subscriber can participate in the speech conversation by requesting the seizure of the uplink of the group call channel (by pressing
the PTT key). The seizure of the uplink of the group call channel is performed on a first-come, first-served basis. In other words, the service subscriber that seizes the uplink first has the right to talk. Other service subscribers can request the seizure of the uplink only when the uplink is idle. A dispatcher has a dedicated channel. Therefore, a dispatcher can participate in the speech conversation at any time without seizing the uplink. A service subscriber is allowed to establish a call to a group of subscribers that belong to a predefined service area and group ID. During the call, all the dispatchers can talk and all the service subscribers seize one uplink channel. The service area can be made up of a certain cells belonging to one or more MSCs. During the call, each cell involved has a group call channel, where the uplink is available for only the current talker (group transmit mode) and the downlink available for all the listeners to camp on (group receive mode). The notification messages are broadcast on the notification channel (NCH).
?.2. Initiation and Establishment of a VGCS Call

The establishment of a VGCS call can be initiated by a service subscriber or dispatcher.
Initiation of a VGCS Call

A dispatcher initiates a VGCS call by dialing "Prefix + Group call reference" (Prefix identifies a VGCS call). A service subscriber initiates a VGCS call in the group call area by dialing the group ID. For a VGCS call initiated by a service subscriber, the group call area is uniquely identified by the dialed group ID and the cell where the calling service subscriber is located. The prerequisites for a service subscriber to initiate a VGCS call are as follows: l l l l The group ID is stored in the SIMs of the MSs of the calling and destination service subscribers and the group ID is activated. The calling service subscriber has subscribed to the VGCS that corresponds to the group ID in the HLR. The group call register (GCR) is configured with VGCS data (including VGCS type, VGCS reference, and cell list). The calling service subscriber initiates a call in the group call area.
The prerequisites for a dispatcher to initiate a VGCS call are as follows: l l The anchor MSC is configured with the prefix of the VGCS call. The anchor MSC is configured with the dispatcher ID and the dispatcher has the right to originate a call.
Establishment and Notification of a VGCS Call

After receiving a VGCS request, the MSC queries the group information in the GCR based on the group ID and the ID of the cell where the VGCS call is initiated. Then, the MSC assigns dedicated channels to the initiator and assigns group call channels to the cells in the group call area. The BSC establishes a group call channel in each cell of the group call area and sends the notification message (including group call reference and group call channel description) on the NCH. At the same time, the BSC assigns the initiator the dedicated channel. Figure 2-318 shows the VGCS call establishment procedure.
Figure 2-318 VGCS call establishment procedure
The previous procedure is described as follows: 1. 2. 3. The MS sends the BSS a Channel Request message on the RACH. After receiving the Channel Request message, the BSC assigns signaling channels and sends a Channel Activation message to the BTS. After receiving the Channel Activation message, the BTS turns on the power amplifier on the specified channel if the channel type is correct. Then, the BTS starts to receive messages on the uplink and sends a Channel Activation Acknowledge message to the BSC. The BSS sends an Immediate Assignment Command message to the MS. On the Um interface, this message is transmitted over the AGCH. The MS sends an SABM frame on the SDCCH. The BSS responds with a UA frame on the SDCCH.
4. 5. 6.
Issue 08 (2011-09-30)
7. 8. 9.
The BTS sends the BSC an Establish Indication message, containing the cause for MS access. The BSS establishes an SCCP connection on the A interface and sends the MSC a Complete Layer3 Information message. The MSC responds to the BSC with a Connection Confirm message.
10. The MSC responds to the MS with a CM Service Accept message. 11. The MS of the calling service subscriber sends a Setup message on the SDCCH. 12. After receiving the Setup message, the MSC sends the BSC an Assignment Request message, requesting the assignment of traffic channels (TCHs). 13. After receiving the Assignment Request message, the BSC sends the BTS a Channel Activation message. 14. After receiving the Channel Activation message, the BTS sends the BSC a Channel Activation Acknowledge message. 15. The BSC sends the MS an Assignment Command message to assign the MS a dedicated TCH. 16. The MSC sends the BSC a VGCS Setup message to establish a VGCS call control connection. The uplink management messages are transmitted on the connection. This connection is not released until the call is complete. 17. The BSC sends the MSC a VGCS Setup Acknowledge message to acknowledge the establishment of the VGCS call control connection. 18. The MSC sends each cell in this group call area a VGCS Assignment Request message, requesting the establishment of the group call channel. The message contains the group call reference. 19. After receiving the VGCS Assignment Request message, the BSC sends the BTS a Channel Activation message to establish the group call channel. 20. After receiving the Channel Activation message, the BTS sends the BSC a Channel Activation Acknowledge message. 21. The BSC sends the MS a Notification Command message, indicating that the group call channel is established successfully. At the same time, the BSC responds to the MSC with a VGCS Assignment Result message. 22. At the same time, the dedicated TCH between the MS and the network is established. 23. The BSC sends the MSC an Assignment Complete message. 24. After receiving the Assignment Complete message, the MSC sends the MS a Connect message, indicating that the VGCS call connection is successfully established. 25. At the same time, the BSC sends the MSC a Clear Request message, requesting the release of CC connection on the A interface. 26. The MSC sends the BSC a Clear Command message to release the CC connection on the A interface. 27. At the same time, the BSC releases the SDCCH occupied during the establishment of the VGCS call.
Issue 08 (2011-09-30)
1211

NOTE
If the channel establishment mode in the VGCS Assignment Request message is immediate establishment of group call channel, the BSC assigns a TCH as the group call channel. Then, the BSC sends on the NCH and FACCH a notification message that contains group call channel description. After detecting the notification message, the MS is automatically switched to listen on the group call channel. If the channel establishment mode in the VGCS Assignment Request message is delayed establishment of group call channel, the BSC directly responds to the MSC with a VGCS Assignment Complete message. Then, the BSC sends on the NCH and FACCH a notification message that does not contain group call channel description. After detecting the notification message, the MS initiates the notification response procedure.
Assignment of Group Call Channels and Power Control

The listening service subscribers share the downlink of the group call channel. No dedicated channel is available between a listening service subscriber and the network. The channel request message is not aimed at specific subscribers, so the information such as the TA, receive level, handover-related data, MS capability, MS mode in the message is invalid. To ensure that all the service subscribers can join the VGCS call, such a channel should be preferentially assigned during the channel assignment: The frequency band of the channel is compatible with the frequency band where the main BCCH is located. If a cell is configured as the concentric cell, the group call channel should be preferentially assigned in the underlaid subcell. When the VGCS Channel Assign in Channel Enable parameter of a cell is enabled, the group call channel can also be assigned in the overlaid subcell if the underlaid subcell is congested. As a result, however, some MSs whose working frequency band is incompatible with the frequency band of the overlaid subcell cannot receive VGCS calls. The listening service subscribers share the downlink of the group call channel. Therefore, power control cannot be performed on the downlink and signals are always transmitted at the maximum transmit power. On the uplink, however, power control can be performed.
Handing Over the Initiator from the Dedicated Channel to the Group Call Channel as a Talker
When a VGCS call is established, the system assigns a dedicated channel for the initiator to talk. After the group call channel of the cell is successfully assigned, the MSC assigns the initiator the group call channel to continue talking through the SCCP connection on the dedicated channel. If the MSC does not support the assignment of the group call channel to the initiator as a talker, the initiator occupies the dedicated channel all the time. The MSC instructs the BSC to assign the group call channel to the initiator as a listener only when the initiator stops talking by releasing the PTT key. Figure 2-319 shows the procedure for handing over the initiator from the dedicated channel to the group call channel as a talker.
Issue 08 (2011-09-30)
1212
Figure 2-319 Handing over the initiator from the dedicated channel to the group call channel as a talker
The previous procedure is described as follows: 1. When a VGCS call is initiated, the initiator talks over the dedicated channel. If the MSC supports the assignment of the group call channel to the initiator as a talker, the MSC sends the BSC an assignment request message (containing the Talker Flag parameter), instructing the BSC to assign the group call channel to the initiator as a talker. After receiving the assignment request message, the BSC preferentially assigns the group call channel if the cell is not assigned the group call channel. After the channel assignment is successful, the BSC instructs the BTS to activate the uplink and downlink of the group call channel. If the cell is assigned the group call channel, the BSC instructs the BTS to activate only the uplink of the group call channel. After the group call channel is successfully activated, the BTS sends the BSC a Channel Activate Acknowledge message. After receiving the Channel Activate Acknowledge message, the BSC sends the MS an Assignment Command message over the dedicated channel. After receiving the Assignment Command message, the MS is switched to the group call channel to continue talking according to the channel information in the message. Then, the MS sends the BSS an assignment complete message. After receiving the assignment complete message from the MS over the group call channel, the BSC sends the MSC an assignment complete message. At the same time, the BSC sends the MSC a Clear Request message through the dedicated channel that is established during the call initiation. After receiving the Clear Request message from the BSC, the MSC responds with a Clear Command message, instructing the BSC to release the dedicated channel.
2.
3. 4. 5.
6.
7.
Issue 08 (2011-09-30)
8.
After receiving the Clear Command message from the MSC, the BSC starts the local release procedure and releases the radio resources and A interface resources from the dedicated channel.
?.3. Reception of a VGCS Call

The destination subscriber (receiver of the call) refers to the destination service subscriber identified by the called group ID or the dispatcher in the group call area. Generally, a service subscriber participates in the speech conversation through the common group call channel that is established by the network in the group call area; a dispatcher participates in the speech conversation through the dedicated channel established by the network. After entering the group call area, the service subscriber obtains the configuration information about the NCH by listening to the system information. After receiving the corresponding group call notification through the NCH, the service subscriber converts into the destination service subscriber. The MS of the service subscriber can join the group call only when the SIM of the MS stores the corresponding group ID. The destination service subscriber that leaves the group call area ceases to be a destination subscriber. The procedure for establishing a connection to the destination dispatcher is the same as the procedure for establishing a normal point-to-point connection to the called party. The anchor MSC addresses the dispatcher based on the number of the destination dispatcher and then establishes a dedicated connection to the dispatcher. After a VGCS call is established, all the dispatchers can talk and a group call channel is established in each cell of the group call area. The group call channel is a common channel, so all the service subscribers in the cell listen to this channel. A service subscriber or a dispatcher can leave the group call without affecting the ongoing VGCS call. The members that leave the VGCS call can return to the call by dialing the group ID.
?.4. Release and Seizure of the Uplink of the Group Call Channel
After the talk is complete, the VGCS subscriber can release the uplink of the group call channel by pressing the PTT key. The MSC can limit the talking duration of a subscriber by requesting the BSC to release the uplink of the group call channel. After the uplink of the group call channel is released, other subscribers can request to be the talker by preempting the uplink.
Uplink Release
The uplink release involves the following: assigning group call channel to the initiator as a listener, talker releasing the uplink, and BSC releasing the uplink. l Assigning group call channel to the initiator as a listener When the initiator seizes the dedicated channel, the MSC instructs the BSC to assign the group call channel to the initiator as a listener if the talk is complete and the uplink is released. l Talker releasing the uplink The talker stops talking and the BSC releases the uplink of the group call channel. At the same time, the BSC informs the MSC that the uplink of the group call channel is released. Then, the MSC informs other BSCs of the release of the uplink. Thus, other subscribers can request to be the talker by preempting the uplink. l
Issue 08 (2011-09-30)
BSC releasing the uplink

During an ongoing VGCS call, if the MSC requires that the uplink of the group call channel be released because of the limitation on the talking duration of a subscriber, the MSC instructs the BSC to release the uplink. Then, the BSC releases the uplink and instructs the talker to stop talking.
Uplink Seizure
For the VGCS, any subscriber can request to talk. At a specific time, however, only one subscriber (except dispatchers) can talk. If a service subscriber wants to talk, the service subscriber must seize the uplink of the group call channel by pressing the PTT key. The VGCS subscriber can request to seize the uplink of the group call channel only when the uplink is idle. If the group call area covers the cells of several BSCs, the MSC should inform other BSCs that the uplink of the group call channel is seized when the subscriber served by one BSC successfully seizes the uplink.
?.5. Handover of a VGCS Call

The handover of a VGCS call involves the handover upon the seizure of dedicated channel by the initiator and the handover upon the seizure of group call channel by the talker.
VGCS Call Handover Decision

When the VGCS subscriber performs handover decision as a talker, the neighbor cells should be filtered. Only the neighbor cells in the same group call area can be the candidate cells. If a VGCS call is handed over to a cell beyond the group call area, the MSC directly clears the call. Thus, the handover fails.
Handover upon the Seizure of Dedicated Channel by the Initiator

If the initiator seizes the dedicated channel, the following cases are available: l In the case of an intra-BSC handover, the BSC reassigns a dedicated channel to the initiator in the target cell. The handover procedure is the same as the normal point-to-point call handover procedure. In the case of an inter-BSC handover, the MSC determines whether to assign a dedicated channel in the target cell or to hand over the VGCS call to the group call channel of the target cell. If the MSC requests the BSC to establish a new connection on the A interface and to send a Handover Request message through the connection, the BSC should reassign the dedicated channel. The handling procedure is the same as that in the incoming BSC handover of a point-to-point call. If the MSC sends a Handover Request message through the resource controlling SCCP connection that corresponds to the target cell, the VGCS call is handed over to the group call channel of the target cell. The handling procedure is the same as that in the incoming inter-BSC handover of the talker of the VGCS call.
Handover upon the Seizure of Group Call Channel by the Talker

The handover upon the seizure of group call channel by the talker is classified into intra-BSC handover and inter-BSC handover. The intra-BSC handover is classified into intra-cell handover and inter-cell handover.
Intra-BSC handover Intra-cell handover If the BSC determines that the handover upon the seizure of group call channel by the talker is an intra-cell handover, the BSC initiates an outgoing BSC handover. After receiving a handover request from the BSC, the MSC sends a Handover Request message to hand over the talker to the dedicated channel. The handling procedure is the same as the procedure for the inter-BSC handover of the talker. Inter-cell handover When the talker moves from one cell to another cell under the same BSC in the same group call area, the procedure for the intra-BSC inter-cell handover upon the seizure of group call channel by the talker is triggered. Figure 2-320 shows the procedure for the intra-BSC inter-cell handover upon the seizure of group call channel by the talker.
Figure 2-320 Procedure for the intra-BSC inter-cell handover upon the seizure of group call channel by the talker
The procedure for the intra-BSC inter-cell handover upon the seizure of group call channel by the talker is similar to the normal call procedure. The difference is that the
VGCS call handover is performed only between the cells in the group call area. If the target cell is beyond the group call area, the MS is handed over to the dedicated TCH of the target cell. After receiving a Handover Perform message, the MSC, however, finds that the target cell is beyond the group call area and then clears the uplink of the group call channel forcibly. l Inter-BSC handover If the talker moves to the cell under another BSC in the same group call area, or if an intracell handover is performed, the procedure for the inter-BSC handover upon the seizure of group call channel by the talker is triggered. Figure 2-321 shows the procedure for the inter-BSC handover upon the seizure of group call channel by the talker. Figure 2-321 Procedure for the inter-BSC handover upon the seizure of group call channel by the talker
Issue 08 (2011-09-30)
1217
The procedure for the inter-BSC handover upon the seizure of group call channel by the talker is similar to the normal call procedure. The differences are as follows: After the handover is complete, the MSC sends the original BSC a Handover Succeed message instead of Clear Command message. The VGCS call handover is performed only between the cells in the group call area. If the target cell is beyond the group call area, the MS is handed over to the dedicated TCH of the target cell. During the handover, if the MSC finds that the target cell is beyond the group call area, the MSC clears the uplink of the group call channel forcibly.
?.6. Release of a VGCS Call

A VGCS call can be released by the calling service subscriber, calling dispatcher, or network. Among the service subscribers, only the calling service subscriber can release the VGCS call. Other service subscribers cannot release the VGCS call, but they can leave the call, without affecting the ongoing call. The calling service subscriber can leave or terminate the call. After the calling dispatcher hangs up the phone, the VGCS call is released. During a VGCS call, if no dispatcher is connected to the network or no service subscriber seizes the uplink channel in the predefined period, the MSC automatically releases the call.
2.75.3.2 VBS
?.1. Overview
The VBS is similar to the VGCS. The difference is that only the initiator is allowed to talk during a VBS call and other members are always in the listening state. The members of a VBS call are classified into dispatchers and service subscribers. l Dispatcher A VBS call has a maximum of five dispatchers, which can be fixed-line or mobile subscribers. In a VBS call, dispatchers participate in the speech conversation through a dedicated channel that is established by the network. l Service subscriber A mobile subscriber that subscribes to the VBS is called a service subscriber. In a VBS call, a destination service subscriber participates in the speech conversation through the voice broadcast channel in the group call area. The calling dispatcher is allowed to establish a call to a group of subscribers that belong to a predefined service area and group ID. During the call, only the initiator is allowed to talk and other dispatchers and service subscribers are only allowed to listen. The service area can be made up of cells belonging to one or more MSCs. During the call, each cell involved has a voice broadcast channel, where the uplink is available for only the current talker (group transmit mode) and the downlink available for all the listeners to camp on (group receive mode). The notification messages are broadcast on the notification channel (NCH).
?.2. Initiation and Establishment of a VBS Call

The establishment of a voice broadcast service (VBS) call can be initiated by a service subscriber or dispatcher.
Initiation of a VBS Call

A dispatcher initiates a VBS call by dialing "Prefix + Broadcast call reference" (Prefix identifies a VBS call). A service subscriber initiates a VBS call in the group call area by dialing the group ID. For a service subscriber initiated VBS call, the group call area is uniquely identified by the dialed group ID and the cell where the calling service subscriber is located. The prerequisites for a service subscriber to initiate a VBS call are as follows: l l l l The group ID is stored in the SIMs of the MSs of the calling and destination service subscribers and the group ID is activated. The calling service subscriber has subscribed to the VBS that corresponds to the group ID in the HLR. The GCR is configured with VBS data (including VBS type, VBS reference, and cell list). The calling service subscriber initiates a call in the group call area.
The prerequisites for a dispatcher to initiate a VBS call are as follows: l l The anchor MSC is configured with the prefix of the VBS call. The anchor MSC is configured with the dispatcher ID and the dispatcher has the right to originate a call.
Establishment and Notification of a VBS Call

After receiving a VBS request, the MSC queries the group information in the GCR based on the group ID and the ID of the cell where the VBS call is initiated. Then, the MSC assigns a dedicated channel to the initiator and assigns voice broadcast channels to the cells in the group call area. The BSC establishes a voice broadcast channel in each cell of the group call area and sends the notification message (including broadcast call reference and voice broadcast channel description) on the NCH. At the same time, the BSC assigns the initiator the dedicated channel.
Assignment of Voice Broadcast Channels and Power Control

The listening service subscribers share the downlink of the voice broadcast channel. No dedicated channel is available between a listening service subscriber and the network. The channel request message is not aimed at specific subscribers, so the information such as the TA, receive level, handover-related data, MS capability, MS mode in the message is invalid. To ensure that all the service subscribers can join the VBS call, such a channel should be preferentially assigned during the channel assignment: The frequency band of the channel is compatible with the frequency band where the main BCCH is located. If a cell is configured as the attribute of concentric cell, the voice broadcast channel should be preferentially assigned in the underlaid subcell. When the VGCS Channel Assign in Channel Enable parameter of a cell is enabled, the voice broadcast channel can also be assigned in the overlaid subcell if the underlaid subcell is congested. As a result, however, some MSs that are incompatible with the overlaid subcell frequency band cannot receive VBS calls. The listening service subscribers share the downlink of the voice broadcast channel. Therefore, power control cannot be performed on the downlink and signals are always transmitted at the maximum transmit power. On the uplink, however, power control can be performed.
Issue 08 (2011-09-30)
1219
Assigning the Initiator a Dedicated Channel and Then the Voice Broadcast Channel as a Talker
When a VBS call is established, the system assigns a dedicated channel for the initiator to talk. After the voice broadcast channel is successfully assigned, the MSC assigns the voice broadcast channel for the initiator to continue talking through the SCCP connection on the dedicated channel. If the MSC does not support the assignment of the voice broadcast channel to the initiator as a talker, the initiator occupies the dedicated channel all the time. The MSC instructs the BSC to assign the group call channel to the initiator only when the initiator stops talking by releasing the PTT key. In this case, the initiator becomes a listener.
?.3. Reception of a VBS Call

The handling procedure for the reception of a VBS call is the same as that for the reception of a VGCS call. See 2.75.3.1.3 Reception of a VGCS Call.
?.4. Handover of a VBS Call

The handling procedure for the handover of a VBS call is the same as that for the handover of a VGCS call. See 2.75.3.1.5 Handover of a VGCS Call.
?.5. Release of a VBS Call

The handling procedure for the release of a VBS call is the same as that for the release of a VGCS call. See 2.75.3.1.6 Release of a VGCS Call.
2.75.3.3 Delayed Assignment of the VGCS/VBS Channel

Delayed assignment of the VGCS channel (also referred to as group call channel)/VBS channel (also referred to as voice broadcast channel) indicates the following: When a VGCS/VBS call is established, no radio channels are assigned. If the cell has a VGCS/VBS subscriber, the subscriber sends a Channel Request message to the network after receiving a notification message. Then, the network assigns the VGCS/VBS channel to this cell through the notification response procedure. If the assignment of the VGCS/VBS channel is delayed when a VGCS/VBS call is established, the radio channel resources can be saved effectively and the congestion rate of the radio channel can be decreased. When a VGCS/VBS call is established, the MSC indicates the following methods of assigning the radio channel in the VGCS/VBS assignment request message: l l l The VGCS/VBS channel is assigned in a delayed manner. The VGCS/VBS channel is assigned in an immediate manner and the VGCS/VBS channel cannot be released until the VGCS/VBS call is complete. The VGCS/VBS channel is assigned in an immediate manner and the VGCS/VBS channel can be released before the VGCS/VBS call is complete.
For the immediate assignment of the VGCS/VBS channel, the BSC should assign the A-interface circuits and establish the group call channel. After the group call channel is successfully
established, a notification message with channel description is sent in the cell. The VGCS subscriber enters this cell and receives information through the VGCS/VBS channel. For the delayed assignment of the VGCS/VBS channel, the BSC only assigns the A-interface circuits without establishing the VGCS/VBS channel. A notification message without channel description is sent in the cell. If a VGCS/VBS subscriber enters this cell, the VGCS/VBS channel is established through the notification response procedure without affecting the ongoing services.
2.75.3.4 Downlink Detection

Downlink detection is a process in which the BSC detects whether the current cell has a VGCS subscriber in the predefined period after the group call channel is successfully assigned. If the group call area is large, some cells may not have a VGCS subscriber in a certain period. The downlink detection can save radio resources. When a call is established, the BSS starts the downlink detection procedure after the group call channel is successfully assigned if the MSC requests the BSS to assign the group call channel immediately and if the BSS is allowed to release the group call channel during the VGCS call. l l If the BSC detects that the current cell does not have a VGCS subscriber in the predefined period, the BSC directly releases the group call channel. If the BSC detects that the current cell has a VGCS subscriber, the BSC reserves the group call channel.
After a VGCS call is established, the downlink detection is started and the cell involved in the VGCS call is queried. If the cell has a VGCS subscriber, the subscriber returns an acknowledge message to the BSC. If the cell does not have a VGCS subscriber, the BSC performs repeated detection based on the Download Test Resend Interval. If the BSC does not receive an acknowledge message from a VGCS subscriber after the number of retransmissions reaches the Download Test Resend Number, the BSC releases the group call channel in the cell to save the channel resources. After the group call channel is released, the BSS sends a notification message (without channel description) in the cell. If a VGCS subscriber enters this cell, the group call channel is reactivated through the notification response procedure without affecting the ongoing services.
2.75.3.5 Initiation of a VGCS Call Through One Channel

During VGCS call initiation, the initiator does not seize a dedicated channel; instead, the network regards the initiator as a talker and assigns the initiator a group call channel to establish the VGCS call. Thus, the dedicated channels can be saved. Whether to initiate a VGCS call through only one channel is determined by the MSC. The MSC sends the BSC an assignment request message over the A interface, instructing the BSC to assign a group call channel to the talker. Compared with the normal VGCS call initiation, the initiation of a VGCS call through only one channel saves TCHs and A-interface circuits. The initiation of a VGCS call through only one channel, however, takes more time because the network has to establish a group call channel before assigning the group call channel to the initiator. The procedure for initiating a VGCS call through only one channel is similar to the normal VGCS call initiation procedure. The differences are as follow:
Issue 08 (2011-09-30)
1221
When a VGCS call is initiated through only one channel, the MSC delivers an assignment request message after a VGCS call is established. The message indicates that the initiator should be assigned the group call channel. Therefore, no dedicated channel is assigned. The initiator accesses the group call channel and sends an assignment complete message over the channel.
2.75.3.6 Talker Identification

Talker identification is a process in which the information about the talking subscriber is sent to listening subscribers when a VGCS subscriber talks on the uplink of the group call channel. When a VGCS call is initiated, the network sends the information about the initiator to the listening subscribers. When a VGCS subscriber talks on the uplink of the group call channel, the network sends the information about the talking subscriber to the listening subscribers. After a listening subscriber receives the information, the information can be displayed on the terminal screen in real time. If no subscriber is talking, the ID of the talking subscriber is not displayed on the terminal screens of listening subscribers.
2.75.3.7 eMLPP in VGCS/VBS

The eMLPP service provides seven priorities (A, B, 0-4). During call establishment or handover, a group or MS with high priority can be preferentially assigned radio resources or preempt the radio resources seized by an MS with low priority. The priorities (from the highest to the lowest) are as follows: l l l l l l l A(highest,for network internal use) B(for network internal use) 0(for subscription) 1(for subscription) 2(for subscription) 3(for subscription) 4(lowest, for subscription)
Priorities A and B are the highest priorities, and are used for only network maintenance. Priorities A and B are meaningful for the local MSC. In the areas out of the control of the local MSC, priorities A and B are regarded as priority 0. Other priorities are applicable globally and can be used in different networks. Before the VGCS attribute data of a VGCS/VBS call is obtained, the priority of the call is determined according to the priority of the calling service subscriber. After the VGCS attribute data of a VGCS/VBS call is obtained, the priority of the call is determined according to the priority of the group specified in the GCR. For details of the eMLPP function, see 2.32 eMLPP. The application of eMLPP in VGCS/VBS is described here.
?.1. Service Preemption

During an ongoing call, if a new call is initiated, the system determines whether to accept the new call based on the priorities of these two calls.
Preemption of a Point-to-Point Call by a VGCS Call

Assume the following: Subscribers A and B are making a point-to-point call and the priority of the call is BA; a VGCS call P to which subscriber A has subscribed is initiated and the priority of the call is PA. Based on the PA, FACCH Send Notification Msg Indication, and Send FACCH Notification Priority, the BSC determines whether to send the notification message of the VGCS call P on the FACCH of a certain cell in the group call area. l If the FACCH Send Notification Msg Indication is set to Yes and PA is higher than Send FACCH Notification Priority, the BSC sends the notification message of the VGCS call P on the FACCH of the cell. When subscriber A detects the new VGCS call, it determines whether to terminate the ongoing point-to-point call to participate in the VGCS call. If the FACCH Send Notification Msg Indication is set to Yes and PA is lower than Send FACCH Notification Priority, or if the FACCH Send Notification Msg Indication is set to No, the BSC sends the notification message of the VGCS call only on the NCH. In this case, subscriber A is in an ongoing call; therefore, it does not listen to the NCH and thus cannot detect the new VGCS call.
Preemption of a VGCS Call by Another VGCS Call

Subscriber A is a service subscriber of groups G1 and G2. The priority of G1 is P1 and the priority of G2 is P2. A VGCS call to group G1 is initiated. Then, a VGCS call to group G2 is initiated. The principles of the preemption between the VGCS calls are as follows: l If the FACCH Send Notification Msg Indication is set to Yes and P2 is higher than Send FACCH Notification Priority, the BSC sends the notification message of the VGCS call to G2 on the FACCH of the cell. When subscriber A detects the VGCS call to G2, it determines whether to terminate the ongoing VGCS call to G1 so that it can participate in the new VGCS call to G2. If the FACCH Send Notification Msg Indication is set to Yes and P2 is lower than Send FACCH Notification Priority, or if the FACCH Send Notification Msg Indication is set to No, the BSC sends the notification message of the VGCS call to G2 only on the NCH. In this case, subscriber A cannot detect the VGCS call to G2.
Preemption of a VGCS Call by a Point-to-Point Call

Subscriber A is a service subscriber to group G and the priority of group G is P. A VGCS call to group G is initiated. Then, subscriber B makes a call to subscriber A and the priority of the call is BA. The MSC delivers the paging message to subscriber A and the priority is BA. l If the FACCH Send Paging Msg Indication is set to Yes and BA is higher than Send FACCH Paging Priority, the BSC sends the paging message on the FACCH of the cell. When subscriber A detects the paging message, it determines whether to terminate the ongoing VGCS call so that it can respond to the paging message. If the FACCH Send Paging Msg Indication is set to Yes and BA is lower than Send FACCH Paging Priority, or if the FACCH Send Paging Msg Indication is set to No, the BSC sends the paging message only on the PCH. In this case, subscriber A is in group receive mode; therefore, it does not listen to the PCH and thus cannot receive the paging message.
Issue 08 (2011-09-30)
1223
?.2. Resource Preemption

If network resources (such as processing capability, signaling channels, and traffic channels) are insufficient, calls with high priorities do not release network resources. In this case, new calls with high priorities can queue or even preempt the resources seized by calls with low priorities. The preemption of network resources by VGCS calls is the same as that by point-to-point calls. If the VGCS IM Preemption Enable parameter is set to Yes, the channel of the subscriber that is preempted is directly released. If this parameter is set to No, the subscriber that is preempted is handed over to another cell.
2.75.3.8 Fast VGCS Call

To initiate a fast VGCS call, an MS sends an Immediate Setup message to request the establishment of the VGCS call. To initiate a normal VGCS call, the MS first sends a CM Service Request message to request the establishment of an MM connection. After the MM connection is established, the MS sends a Setup message to request the establishment of the VGCS call. In a fast VGCS call establishment procedure, the MS sends an Immediate Setup message (containing Classmark, Group ID, and MS identity) to request the establishment of an MM connection and a VGCS call. This saves the duration for initiating a VGCS call. The fast VGCS call establishment procedure is similar to the normal VGCS call establishment procedure. The difference between the two procedures are as follow: l l The MS sends an Immediate Setup message to request the establishment of an MM connection and a VGCS call. After receiving the Immediate Setup message, the MSC establishes the MM connection and then initiates a VGCS call establishment procedure.
2.75.3.9 Enhancement of VGCS/VBS

Enhancement of VGCS/VBS consists of fallback and VGCS resource check. l Fallback If the requirement for service continuity is high, the fallback function is provided in the BTS coverage area when the BTS is out of service because of transmission failure. l VGCS resource check Periodical VGCS resource checks are performed on the BSC and BTS to eliminate inconsistent VGCS calls. At present, the VGCS resource check function can be used to solve the problem that a VGCS call exists on the BTS side but does not exist on the BSC side. The fallback function takes effect quickly and effectively during emergencies, such as emergency service, disaster relief, first aid, and emergency evacuation. The fallback function is mandatory for Public Access Mobile Radio (PAMR) networks. When the BSS system malfunctions, the following condition may occur: A VGCS call is terminated but the BTS periodically sends the notification message. Thus, an MS responds repeatedly, but it cannot join the VGCS call. If the periodical VGCS resource check is performed on the BSC and BTS, the following case can be avoided: A VGCS call exists on the BTS side but does not exist on the BSC side.
?.1. Fallback
In fallback mode, if a VGCS call is configured in the BTS, the BTS initiates the VGCS call once transmission is disrupted. Subscribers can seize the uplink but cannot abort the VGCS call. If a VGCS call is not configured in the BTS, subscribers can initiate VGCS calls. The features of the fallback function are as follows: l l l l l l l The disruption and recovery of transmission links are automatically detected. After the BTS enters the fallback mode, the MS keeps communicating with the network. After a transmission link is disrupted, the network initiates the previously configured VGCS call. Subscribers automatically participate in the group. A subscriber can become the talking subscriber in the group. The talking duration of a subscriber can be limited so that resources are optimally allocated. In the case of multiple cells under a BTS, the BTS can initiate cross-cell VGCS calls.
The parameters related to the fallback function can be configured on the Local Maintenance Terminal. These parameters are as follows: l l l l l l l l l FallBack Function Enable FallBack Start Time FallBack Stop Time No VGCS Call Time Uplink Max Length Channel Type Group Call Num 1 Group Call Num 2 Speech Version
?.2. VGCS Resource Check

The BSC adopts the periodical check mechanism. This avoids CPU overload in the case that the BSC suddenly receives a large number of VGCS check messages. The setting of the Group Call Check parameter determines whether to enable the VGCS resource check function. The procedure for VGCS resource check is as follows: 1. 2. 3. After the timer for VGCS check expires, the BSC sends the BTS a VGCS resource check message through the RSL link of the BCCH TRX. After receiving the VGCS resource check message, the BTS sends the BSC a list of ongoing VGCS calls in the cells under the BTS. Based on the list of ongoing VGCS calls reported by the BTS and the group call reference table in the BSC, the BSC performs consistency check. If a VGCS call does not exist in the group call reference table, the BSC sends the BTS a notification message, instructing the BTS to abort the VGCS call. If none of the cells under the BTS has VGCS calls, the BTS does not send any message to the BSC.
4.
Issue 08 (2011-09-30)

If the core network of the traditional GSM system cannot be replaced with the GSM-R core network, GSM-R services and traditional GSM services can be processed in the same network. That is, the BSC implements the function of forwarding GSM-R services. Figure 2-322 shows the co-networking of GSM-R services and traditional GSM services. Figure 2-322 Co-networking of GSM-R services and traditional GSM services
The BSC is connected to both the public MSC and the cluster MSC, and the two MSCs are independent of each other. Whether the public MSC supports MSC Pool has no impact on the cluster MSC. One BSC can be shared by multiple operators. Each operator has only one cluster MSC. The co-networking solution does not affect the total number of signaling points supported by the BSC. Support Paging Message from Trunking MSC must be set to YES to enable the BSC to forward GSM-R services.
2.75.5 Parameters
This chapter describes the parameters related to VGCS/VBS. For the meaning of each parameter, see Table 2-223. For the default value, value ranges, and MML commands of each parameter, see Table 2-224. Table 2-223 Parameter description (1) Parameter VGCS Channel Assign in Channel Enable Description Whether the assignment of channels in overlaid subcells is enabled for the VGCS service in the case of underlaid subcell congestion. Generally, only the channels in underlaid subcells can be assigned to the VGCS service.
Issue 08 (2011-09-30)
1226
Parameter Download Test Resend Interval
Description Interval for resending downlink test messages Number of times of the BSC6900 resending downlink test messages after the downlink test function is enabled. If the BSC6900 does not receive any response message from the MS at the preset interval, the BSC6900 releases the relevant voice group call service (VGCS) channel. Whether to allow sending notification messages on the FACCH. If the value of this parameter is YES, an MS engaged in a point-topoint call can receive a notification message for a group call. You can interrupt the existing call and join the group call. Priority of the notification message transmission on the FACCH. From high to low, the priorities are A, B, 0, 1, 2, 3, 4 and No Priority. No Priority is the lowest. When the priority of the group call is higher than or equal to the value specified by this parameter, the notification message is sent on the FACCH. Priority of the paging message transmission on the FACCH. From high to low, the priorities are A, B, 0, 1, 2, 3, 4 and No Priority. No Priority is the lowest. When the priority of the group call is higher than the value specified by this parameter, the paging message is sent on the FACCH. Whether direct preemption of the channels of other services is enabled for the VGCS service. If the value of this parameter is NO, a handover is performed for the call whose channel is preempted. If the value is YES, calls on the preempted channel are directly released. Whether to enable the fallback function for the BTS Time for which the BTS waits to start the fallback function after the OML is interrupted. With this parameter, the BTS does not start the fallback function when the OML is interrupted transiently. Time for which the BTS waits to stop the fallback function after the OML is set up. With this parameter, the BTS does not stop the fallback function when the OML is set up transiently. If the BTS works in fallback mode and uplink VGCS connection is idle for a period specified by this parameter, the BTS disables the VGCS connection automatically. This parameter is valid only for user-originated VGCS calls and is invalid for fixed VGCS calls. Maximum time in which a user uses the uplink of its VGCS call continuously when the BTS works in fallback mode
Download Test Resend Number FACCH Send Notification Msg Indication
Send FACCH Notification Priority
Send FACCH Paging Priority
VGCS IM Preemption Enable Fallback Function Enable
Fallback Start Time
Fallback Stop Time
No VGCS Call Time Uplink Max Length
Issue 08 (2011-09-30)
1227
Parameter
Description Channel type of the timeslot on the TRX. The channel type of timeslot 0 must not be set, because the combined BCCH is configured by default. The channel type of other timeslots can be set to full-rate TCH or half-rate TCH. Number of the VGCS call that the BTS originates in the timeslot in the TRX in fallback mode. This parameter is represented in decimal, such as 10000569. If this parameter is set to 100000000, the channel is not configured with any fixed group call. Number of the VGCS call that the BTS originates in the timeslot in the TRX in fallback mode. This parameter is represented in decimal, such as 10000569. If this parameter is set to 100000000, the channel is not configured with any fixed group call. Speech version configured on the TRX timeslot when the BTS works in fallback mode. When "CHNTYPE" of the TRX timeslot is set to "FULLTCH", value 0 of this parameter indicates FR and value 1 indicates EFR; when "CHNTYPE" of the TRX timeslot is set to "HALFRCH", this parameter is invalid. Whether the BSC forwards the paging message from the trunking MSC to the MS. When this parameter is set to YES, the BSC forwards the paging message from the trunking MSC to the MS and forwards the corresponding paging response from the MS to the trunking MSC.
Channel Type
Group Call Num 1
Group Call Num 2
Speech Version
Support Paging Message from Trunking MSC
Table 2-224 Parameter description (2) Paramete r VGCS Channel Assign in Channel Enable Download Test Resend Interval Download Test Resend Number Default Value GUI Value Range Actual Value Range Unit MML Comman d SET GCELLG SMR (Optional) SET GCELLG SMR (Optional) SET GCELLG SMR (Optional) Impact
YES
NO(No), YES(Yes)
NO, YES
None
Cell
0~255
0~255
Cell
1~255
1~255
None
Cell
Issue 08 (2011-09-30)
1228
Paramete r FACCH Send Notificatio n Msg Indication
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET GCELLG SMR (Optional)
Impact
NO
NO(No), YES(Yes) NoPriority (No Priority), Priority4 (Priority 4), Priority3 (Priority3) , Priority2 (Priority 2), Priority1 (Priority 1), Priority0 (Priority 0), PriorityB (Priority B), PriorityA (Priority A)
NO, YES
None
Cell
Send FACCH Notificatio n Priority
NoPriority
NoPriority , Priority4, Priority3, Priority2, Priority1, Priority0, PriorityB, PriorityA
None
SET GCELLG SMR (Optional)
Cell
Issue 08 (2011-09-30)
1229
Paramete r
Default Value
GUI Value Range NoPriority (No Priority), Priority4 (Priority 4), Priority3 (Priority3) , Priority2 (Priority 2), Priority1 (Priority 1), Priority0 (Priority 0), PriorityB (Priority B), PriorityA (Priority A)
Actual Value Range
Unit
MML Comman d
Impact
Send FACCH Paging Priority VGCS IM Preemptio n Enable Fallback Function Enable
NoPriority
NoPriority , Priority4, Priority3, Priority2, Priority1, Priority0, PriorityB, PriorityA
None
SET GCELLG SMR (Optional) SET GCELLG SMR (Optional) SET BTSFALL BACK (Optional) SET BTSFALL BACK (Optional) SET BTSFALL BACK (Optional) SET BTSFALL BACK (Optional)
Cell
YES
NO(No), YES(Yes)
NO, YES
None
Cell
NO
NO(No), YES(Yes)
NO, YES
None
BTS
Fallback Start Time
240
60~600
60~600
BTS
Fallback Stop Time
120
60~300
60~300
BTS
No VGCS Call Time
30
10~255
10~255
BTS
Issue 08 (2011-09-30)
1230
Paramete r
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d SET BTSFALL BACK (Optional)
Impact
Uplink Max Length
30
10~255 FULLTC H (FULLTC H), HALFTC H (HALFTC H)
10~255
BTS
Channel Type
None
FULLTC H, HALFTC H
None
SET BTSCHN FALLBA CK (Mandator y) SET BTSCHN FALLBA CK (Mandator y) SET BTSCHN FALLBA CK (Mandator y) SET BTSCHN FALLBA CK (Mandator y)
BTS
Group Call Num 1
None
0~100000 000
0~100000 000
None
BTS
Group Call Num 2
None
0~100000 000
0~100000 000
None
BTS
Speech Version Support Paging Message from Trunking MSC
FR
FR(FR), EFR(EFR)
FR, EFR
None
BTS
NO
NO(No), YES(Yes)
NO, YES
None
ADD GCNNOD E (Optional)
BSC6900
2.75.6 Counters
2.75.7 Glossary

l l l l l l l l l l l l l 3GPP TS 42.068 V4.2.0 (Stage 1) 3GPP TS 43.068 V4.6.0 (Stage 2) 3GPP TS 42.069 V4.2.0 (Stage 1) 3GPP TS 43.069 V4.5.0 (Stage 2) 3GPP TS 03.67 V7.2.0 3GPP TS 48.008 V4.10.0 3GPP TS 48.058 V4.1.0 3GPP TS 44.018 V4.23.0 BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.76 Voice Quality Index

2.76.1 Introduction
2.76.1.1 Scope
This document describes voice quality indexing (VQI) feature of Huawei GSM BSS. It covers the function of and technologies mechanisms regarding VQI.


Voice Quality Index Change History provides information on the changes between different document versions. There are two types of changes, which are defined as follows:
Feature change Feature change refers to a change in the voice quality index feature of a specific product version.
Editorial change Editorial change refers to a change in information that has already been included, or the addition of information that was not provided in the previous version.
Document Issues
01(2009-09-30)
This is the first commercial release of GBSS9.0. Compared with 01 (2009-04-30) of GBSS8.1, issue 01(2009-09-30) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change Editorial change Change Description None. The structure of the document is optimized. Parameter Change None. None.
2.76.2 Overview of VQI

The voice quality index (VQI) feature provides a direct method of measuring the voice quality of the radio network. By measuring the uplink VQI and downlink VQI, the voice quality of the network is quantified, which provides a reference for future network optimization. The VQI establishes the mapping between the radio network performance and voice quality. The VQI value, which helps learn the voice quality, is calculated based on the parameters related to the radio quality of the uplink/downlink speech signals. The MOS analysis method is applied in VQI to measure the voice quality. The MOS is used to assess the quality of the middle-rate and low-rate voice coding. The MOS value ranges from 1 to 5. Based on the MOS analysis method, Huawei further divides the voice quality into 11 levels. The VQI is obtained through the analysis of the BER, FER, LFE, and CODE of the uplink/downlink speech signal. In this manner, the voice quality is quantified to facilitate the identification of the voice problem and network optimization.

2.76.3.1 Measurement of Voice Quality
Obtaining the VQI Information

This describes the measurement of the voice quality. The VQI classifies the voice quality into 11 levels. During a call, the VQI score of each level is counted and the average VQI score is measured. The average VQI score is used as the performance counter for assessing the voice quality of the TRX carrying this call. In each call, when the parameter Report Speech Quality is enabled, the BTS receives the customized extended measurement reports every five measurement report periods (within 2.4 seconds). The uplink measurement reports contain the short-time VQI information.
NOTE
The VQI information reported in five measurement report periods is called the short-time VQI information.
Classification of VQI Scores

The MOS analysis method is applied in VQI to measure the voice quality. MOS is used to assess the quality of the middle-rate and low-rate voice codec modes. The MOS score ranges from 1 to 5. l l l l l 5: Excellent 4: Good 3: Fair 2: Poor 1: Unsatisfactory
Measurement of Voice Quality

The methods of measuring VQI voice quality are as follows: l Voice quality levels Based on the score range of the MOS analysis method, the voice quality is further classified into 11 levels for measuring performance, as listed in Table 2-225. Table 2-225 Voice quality levels Level Initial level Level 1 Level 2 Level 3 Level 4 Level 5 Level 6 Level 7 Level 8
Issue 08 (2011-09-30)
Description voice quality < 0.5 0.5 < voice quality < 1.0 1.0 < voice quality < 1.5 1.5 < voice quality < 2.0 2.0 < voice quality < 2.5 2.5 < voice quality < 3.0 3.0 < voice quality < 3.5 3.5 < voice quality < 4.0 4.0 < voice quality < 4.5
Level Level 9 Level 10 l
Description 4.5 < voice quality < 5.0 voice quality > 5.0
Measurement of long-time VQI scores The long-time VQI score is the sum of all short-time VQI scores during a call. In each call, the number of short-time VQI scores of each level and the total short-time VQI scores are measured, and then the average VQI score is measured according to the total long-time VQI scores and the number of VQI scores. When a call is released, the number of VQI scores of each level and the average VQI score are output to the CHR and used as the counters of the voice quality of the TRX carrying this call. If the VQI is used to collect statistics of voice quality, the voice quality of the HR TRX and the voice quality of the FR TRX must be measured respectively. The type of the TRX does not affect the counters.
NOTE
l To avoid floating-point calculation when the VQI performance is measured, the VQI score is multiplied by 50 and then the result is converted into an integer. The integer is sent to the BSC. After receiving the VQI score, the BSC forwards the score to the M2000 for processing. The M2000 divides the value by 50 and then obtains the average short-time VQI score. l After receiving the VQI scores, the BSC divides the scores by 50 and then obtains the scores ranging from 0 to 5.1. The BSC measures the performance information with the scale as 0.5 scores. That is, the number of measurement reports with the VQI score range as 00.5 indicates the number of measurement reports with the VQI score smaller than 0.5. Other levels are measured in the same way.
2.76.4 Parameters
For the meaning of each parameter related to the voice quality index feature, see Table 2-226. For the default value, value range, and related MML commands of each parameter, see Table 2-227. Table 2-226 Parameter description (1) Parameter Description Whether to allow the BTS to report the voice quality index (VQI). If this parameter is set to Report, the BTS reports the VQI. The BSC6900 collects the traffic statistics on a per VQI basis. There are 11 levels of speech quality. If the level is lower, the speech quality is better. The traffic related to AMR and nonAMR is measured separately, and thus the speech quality is monitored. If this parameter is set to Not report, the BTS will not report the VQI.
Report Speech Quality
Issue 08 (2011-09-30)
1235
Table 2-227 Parameter description (2) Parameter Defaul t Value GUI Value Range NO(Not report), YES (Report), NONE (None) Actual Value Range Uni t MML Command Im pac t
Report Speech Quality
NO
NO, YES, NONE
Non e
SET GCELLOTHBAS IC (Optional)
Cell
2.76.5 Counters
2.76.6 Glossary

None.
2.77 WB AMR
2.77.1 Introduction
2.77.1.1 Scope
This document describes the WB AMR feature. It describes WB AMR speech coding/decoding, rate adjustment threshold adaptation, WB AMR power control, enabling Tandem Free Operation (TFO) and Discontinuous Transmission (DTX) in the case of WB AMR.

Issue 08 (2011-09-30)

This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the WB AMR feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2009-09-30)
01 (2009-06-30)
2.77.2 Overview
The sampling frequency of the traditional narrowband speech signals is 8 kHz, and the speech frequency ranges from 200 Hz to 3400 Hz. With the development of communication technologies, users have higher requirements for speech quality. The narrowband speech signals, however, cannot always meet users' requirements for speech quality. Wide Band Adaptive Multi Rate Codec (WB AMR) is introduced to provide high-grade speech quality. The sampling frequency of WB AMR is 16 kHz, and the speech frequency ranges from 50 Hz to 7 kHz. Compared with AMR, WB AMR has wide high frequency extension and low frequency extension. Thus, WB AMR can provide better speech quality. In the GSM system, WB AMR specifies five speech coding rates. In addition, WB AMR occupies only full-rate channels.
Currently, Huawei WB AMR supports only one Active Codec Set (ACS). The ACS contains three speech coding rates: 6.60 kbit/s, 8.85 kbit/s, and 12.65 kbit/s. The BSC automatically selects an appropriate speech coding rate from the ACS. Table 2-228 lists the speech coding rates supported by WB AMR. Table 2-228 WB AMR speech coding rates Coding Rate 6.60 kbit/s 8.85 kbit/s 12.65 kbit/s 15.85 kbit/s 23.85 kbit/s
NOTE -: not supported : supported
WB AMR -
WB AMR corresponds to full-rate speech version 5. That is, WB AMR is enabled only when Speech Version is set to FULL_RATE_VER5.

2.77.3.1 WB AMR Coding and Decoding Coding
The sampling frequency of the Pulse Code Modulation (PCM) code stream on the A interface is 8 kHz, whereas the sampling frequency of WB AMR is 16 kHz. WB AMR takes samples of the speech data before coding it. In addition, WB AMR raises the sampling frequency of the PCM code stream that is decompressed according to the A-law or -law to 16 kHz before coding it.
Decoding
After decoding, the sampling frequency of the PCM code stream is 16 kHz. The standard sampling frequency of the PCM code stream on the A interface, however, is 8 kHz. Therefore, the sampling frequency of the decoded PCM code stream needs to be decreased and compressed according to A-law or -law before being sent over the A interface.
2.77.3.2 Speech Rate Adjustment

WB AMR speech rate adjustment refers to the process in which the AMR codec mode of a call on a channel frequently changes to adapt to the variations of the interference level in the radio environment.
Each WB AMR codec mode has an adjustment threshold, which is used to select the codec mode that best suits the C/I ratio of the interference level in the radio environment. To avoid the constant changes of the codec mode, the hysteresis is introduced. The value of the threshold ranges from 0 to 63. Value 1 indicates 0.5 dB, and value 2 indicates 1 dB. The rest may be deduced by analogy. The value of the hysteresis ranges from 0 to 15. The hysteresis value complements the threshold. AMR Starting Mode[WB] specifies the initial WB AMR codec mode used for a call. The speech rate adjustment policy of WB AMR is the same as the speech rate adjustment policy of AMR. For details, see 2.9.3.2 Speech Rate Adjustment. The parameters related to WB AMR speech rate adjustment are listed as follows: l l l l l l l l AMR UL Coding Rate adj.th1[WB] AMR UL Coding Rate adj.hyst1[WB] AMR DL Coding Rate adj.hyst1[WB] AMR DL Coding Rate adj.th1[WB] AMR UL Coding Rate adj.th2[WB] AMR UL Coding Rate adj.hyst2[WB] AMR DL Coding Rate adj.hyst2[WB] AMR DL Coding Rate adj.th2[WB]
2.77.3.3 Rate Adjustment Threshold Adaptation

The WB AMR rate adjustment threshold adaptation function enables the BSC to monitor the speech quality in real time and to adaptively modify the threshold parameters. Thus, an appropriate WB AMR codec mode can always be selected for the call. For details, see 2.9.3.3 Rate Adjustment Threshold Adaptation.
2.77.3.4 Power Control

The procedure of power control for WB AMR calls is similar to the procedure of power control for AMR calls. For details, see 2.9.3.4 AMR Power Control.
2.77.3.5 TFO
Due to the high sampling frequency, WB AMR can provide more spectrum information on speech signals. The spectrum information, however, is partially lost on the A interface due to the decrease of the sampling frequency to 8 kHz. This affects the quality of services provided by WB AMR. To save the spectrum information on speech signals, after a WB AMR call is established, the TC forcibly initiates TFO negotiation. If the calling MS and called MS of the WB AMR call both support TFO, TFO can be performed. The TFO Message is transmitted in fixed bit spacing on the A interface. Specifically, the TFO Message is used to replace the least significant bit in the first byte of every 16 PCM bytes. In this way, the impact on speech quality is reduced to a negligible level. Messages that are transmitted in fixed bit spacing can only be transmitted on a 16 kbit/s subchannel. The TFO Frame and TFO Message are transmitted without coding or decoding. When the TFO Frame and TFO Message are transmitted over the A interface, the sampling frequency need not decrease. In this way, the spectrum information on speech signals can be saved and the speech quality can be ensured. Figure 2-323 shows the working mechanism of TFO.
Figure 2-323 Working mechanism of TFO
The frame format used on the A interface is described as follows: The first six high bits carry the PCM frame, and the last two low bits carry the TFO Frame and TFO Message. After TFO is performed, the TC combines the 48 kbit/s PCM frame compressed according to A-law or -law with 16 kbit/s TFO Frame and TFO Message. The TC then sends them over the A interface to the Core Network (CN). In the downlink, the TC extracts the TFO Frame and TFO Message from the last two low bits, converts the TFO Frame and TFO Message to the TRAU frame, and sends the TRAU frame. The transmission of the TRAU frame does not involve decoding. For details on TFO negotiation, see 2.72 TFO.
2.77.3.6 DTX
The DTX used for WB AMR calls is the same as that used for AMR FR calls. FR Use Downlink DTX and FR Uplink DTX specify whether to enable downlink DTX and uplink DTX for FR calls. WB AMR does not occupy HR channels. Thus, HR Use Downlink DTX and HR Uplink DTX are invalid for WB AMR. When TFO is performed for the calling MS and called MS, the downlink TRAU frames at the local end are the uplink TRAU frames at the peer end. In this case, the DTX enabled at the local end does not take effect. The downlink DTX at the local end can be used only when the uplink DTX at the peer end is used. For details, see 2.25 Discontinuous Transmission and Discontinuous Reception.
2.77.3.7 WB AMR in A over IP Mode

In A over IP mode, the BSC does not perform coding or decoding, and the Media Gateway (MGW) performs the functions of the TC. In this case, the BSS performs coding and decoding only on channels.
2.77.3.8 Impact on KPI

The coding and decoding of WB AMR calls require a large number of resources. Thus, when WB AMR is enabled, the number of speech paths supported by the BSC is reduced in A over TDM mode. In addition, like AMR, WB AMR also has an impact on the call drop rate, congestion rate, handover-related KPIs, and traffic volume. For details, see 2.9.3.6 Impact on KPI.

WB AMR can be enabled in areas where a large number of MSs support WB AMR. For details, see 2.9.4 Engineering Guidelines. Note that WB AMR does not occupy HR channels.
2.77.5 Parameters
This chapter describes the parameters related to WB AMR. For the meaning of each parameter, see Table 2-229. For the default value, value ranges, and MML commands of each parameter, see Table 2-230. Table 2-229 Parameter description (1) Parameter Speech Version Description Speech version supported by a cell. Initial coding mode used for broadband AMR calls. The three values 0, 1 and 2 of this parameter respectively represent the lowest, low and highest coding rates in the ACS. This parameter does not take effect in A over IP mode. In A over IP mode, the TC is integrated into the UMG, and the BSC obtains the initial coding mode according to protocols. That is, the BSC does not obtain the initial coding mode according to parameter configuration. Whether the downlink discontinuous transmission (DTX) function is enabled for full rate (FR) calls. This function is also restricted by the DTX switch in the MSC. If the MSC allows the downlink DTX for calls and the value of this parameter(FRDLDTX) is YES, the downlink DTX is enabled for FR calls of cells. Whether the uplink DTX function is enabled for FR calls. For details, see GSM Rec. 05.08. Uplink DTX is not restricted by the MSC. Shall_Use:An MS will use uplink DTX if it supports uplink DTX. May_Use:An MS will determine whether to use uplink DTX if both the cell and MS support uplink DTX. Shall_NOT_Use:DTX will not be used. Whether the downlink DTX function is enabled for half rate (HR) calls. This function is also restricted by the DTX switch in the MSC. If the MSC allows the downlink DTX for calls and the value of this parameter (HRDLDTX) is YES, the downlink DTX is enabled for HR calls of cells. Whether the uplink DTX function is enabled for HR calls. For details, see GSM Rec. 05.08. Uplink DTX is not restricted by the MSC. Shall_Use:An MS will use uplink DTX if it supports uplink DTX. May_Use:An MS will determine whether to use uplink DTX if both the cell and MS support uplink DTX. Shall_NOT_Use:DTX will not be used. Switch for controlling the AMR rate. Value 0 indicates that C/I is used to control the AMR rate. Value 1 indicates that BER is used to control the AMR rate.
AMR Starting Mode[WB]
FR Use Downlink DTX
FR Uplink DTX
HR Use Downlink DTX
HR Uplink DTX AMR Rate Control Switch
Issue 08 (2011-09-30)
1241
Parameter TFO Option Switch
Description AEC is an important measure to improve the speech quality. If the AEC works for a consecutive time that is longer than the value of this parameter, the TFO function is closed to provide a better speech quality. Based on the RQI in the call measurement report, the BTS and MS automatically adjust the current speech coding rate according to the related algorithm. The coding rate adjustment threshold is the threshold of RQI. The RQI indicates the carrier-to-interference ratio (CIR) of the call. If RQI equals 1, the CIR is 0.5 dB; if RQI equals 2, the CIR is 1 dB; and so forth. Since there are multiple coding rates in the ACS, there is an adjustment threshold and an adjustment hysteresis between the neighboring coding rates. Based on the RQI in the call measurement report, the BTS and MS automatically adjust the current speech coding rate according to the related algorithm. The coding rate adjustment threshold is the threshold of RQI. The RQI indicates the carrier-to-interference ratio (CIR) of the call. If RQI equals 1, the CIR is 0.5 dB; if RQI equals 2, the CIR is 1 dB; and so forth. Since there are multiple coding rates in the ACS, there is an adjustment threshold and an adjustment hysteresis between the neighboring coding rates. Based on the RQI in the call measurement report, the BTS and MS automatically adjust the current speech coding rate according to the related algorithm. The coding rate adjustment threshold is the threshold of RQI. The RQI indicates the carrier-to-interference ratio (CIR) of the call. If RQI equals 1, the CIR is 0.5 dB; if RQI equals 2, the CIR is 1 dB; and so forth. Since there are multiple coding rates in the ACS, there is an adjustment threshold and an adjustment hysteresis between the neighboring coding rates.
AMR UL Coding Rate adj.th1[F]
Issue 08 (2011-09-30)
1242
Table 2-230 Parameter description (2) Parameter Def ault Val ue FUL L_R ATE _VE R1-1 &FU LL_ RAT E_V ER21&F ULL _RA TE_ VER 3-0& HAL F_R ATE _VE R1-1 &H ALF _RA TE_ VER 2-0& HAL F_R ATE _VE R3-0 &FU LL_ RAT E_V ER50 GUI Value Range Actual Value Range U ni t MML Command Impact
Speech Version
FULL_ RATE_ VER1, FULL_ RATE_ VER2, FULL_ RATE_ VER3, HALF_ RATE_ VER1, HALF_ RATE_ VER2, HALF_ RATE_ VER3, FULL_ RATE_ VER5
Full_rat e_Ver1, Full_rat e_Ver2, Full_rat e_Ver3, Half_rat e_Ver1, Half_rat e_Ver2, Half_rat e_Ver3, Full_rat e_Ver5
N on e N on e
SET GCELLCCA CCESS (Optional) SET GCELLCCA MR (Optional)
Cell
AMR Starting Mode[WB]
0~2
0~2
Cell
Issue 08 (2011-09-30)
1243
Parameter
Def ault Val ue
GUI Value Range NO (No), YES (Yes) May_U se(May Use), Shall_U se(Shall Use), Shall_N OT_Use (Shall not Use) NO (No), YES (Yes) May_U se(May Use), Shall_U se(Shall Use), Shall_N OT_Use (Shall not Use) ALG1 (Algorit hm I), ALG2 (Algorit hm II), NONE (None) OFF (Off), ON(On)
Actual Value Range
U ni t
MML Command
Impact
FR Use Downlink DTX
YES
NO, YES
N on e
SET GCELLBAS ICPARA (Optional)
Cell
FR Uplink DTX HR Use Downlink DTX
Shall _Use
May_U se, Shall_U se, Shall_N OT_Use
N on e N on e
SET GCELLBAS ICPARA (Optional) SET GCELLBAS ICPARA (Optional)
Cell
YES
NO, YES
Cell
HR Uplink DTX
Shall _Use
May_U se, Shall_U se, Shall_N OT_Use
N on e
SET GCELLBAS ICPARA (Optional)
Cell
AMR Rate Control Switch TFO Option Switch AMR UL Coding Rate adj.th1[F]
ALG 1
ALG1, ALG2, NONE OFF, ON
N on e N on e
SET GCELLCCA MR (Optional) SET TCPARA (Optional) SET GCELLCCA MR (Optional)
Cell
OFF
Board
15
0~63
0~63
dB
Cell
Issue 08 (2011-09-30)
1244
Parameter
Def ault Val ue
GUI Value Range
Actual Value Range
U ni t
MML Command
Impact
AMR UL Coding Rate adj.th2[F] AMR UL Coding Rate adj.th3[F]
19
0~63
0~63
dB
SET GCELLCCA MR (Optional) SET GCELLCCA MR (Optional)
Cell
28
0~63
0~63
dB
Cell
2.77.6 Counters
2.77.7 Glossary

l l l l l l l l 3GPP TS 28.062 "Inband Tandem Free Operation (TFO) of speech codecs; Service description; Stage 3" 3GPP TS 48.060 "In-band control of remote transcoders and rate adaptors for full rate traffic channels" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.78 14-Digit Signaling Point Code

2.78.1 Introduction
2.78.1.1 Scope
This document describes the benefits of the 14-digit signaling point code (SPC) feature and the principle of implementing this feature in Huawei GSM BSS.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the 14-Digit Signaling Point Code feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows: l 01(2010-01-20)
01(2010-01-20)
2.78.2 Overview of 14-Digit Signaling Point Code

In an SS7 network, each device is regarded as a signaling point (SP), and each SP has a unique signaling point code (SPC). SPs communicate with each other through SPC. The SPC coding modes vary from one country/area to another. Generally, three coding modes are available, namely, 14-bit, 16-bit, and 24-bit modes. Huawei BSC6900 supports all SPC modes. The 14-digit signaling point code feature provides the following benefits: l l This feature conforms to the requirements of different signaling systems, thus facilitating the use of networking in different countries and areas. The equipment transferred to areas using different coding modes can still be used.

In the signaling network, an SP communicates with other SPs through the SPC. The 24-bit SPC is applied in China since 1990. It is also called uniform or one-layer coding scheme. This scheme
specifies that all the SPs of the SS7 signaling network in China use 24-bit SPC. According to the actual situation, 24-bit SPC is classified into three signaling zones in terms of the structure. That is, eight bits for codes of main signaling zone, eight bits for codes of sub-signaling zone, and eight bits for signaling point codes. The 14-bit SPC is widely used in the world. The code capacity of 14-bit SPC is 16,384 codes. 14-bit SPC is classified into three parts: macro area code, zone code, and signaling point code. Figure 3-1 shows the coding principle of the 14-bit SPC. Figure 2-324 The coding principle of the 14-bit SPC
NML: three bits, for identifying the macro area K-D: eight bits, for identifying the zone area in the macro area or the regional network CAB: three bits, for identifying geographic position or the SP in the regional network
To facilitate the management of the signaling network, the CCITT specifies in Rec. Q705 that the international signaling network and other national signaling networks should be independently deployed. Therefore, the SPCs are also independent. In Rec. Q708, the plan of the international SPC is specified. In addition, the national SPCs can be determined by the administrative department according to the actual situations of each country. Each country can adopt 14-bit SPC or 24-bit SPC as required. The value range of the SPC is as follows: 24-bit SPC: 0x1-0xFFFFF1; 14-bit SPC: 0x1-0x03FF1. Huawei BSC6900 supports two SPC input modes: inputting the whole number or inputting divided number. The SPC input mode is determined by the OSP code[Whole Number] parameter or the OSP code[Divided Number] parameter. To enable 14-digit SPC, set the OSP code bits parameter to BIT14(BIT14).
2.78.4 Parameters
This chapter describes the parameters related to the 14-Digit Signaling Point Code feature. For the meaning of each parameter, see Table 2-231. For the default value, value ranges, and MML commands of each parameter, see Table 2-232. Table 2-231 Parameter description (1) Parameter Description As an integer, the OSP code can be expressed by a decimal digit or a hexadecimal digit. If the OSP code is expressed by a hexadecimal digit, H' is added before the number. Number of bits contained in the signaling point code.
OSP code[Whole Number] OSP code bits

Issue 08 (2011-09-30)
Parameter OSP code[Divided Number]
Description OSP code expressed in the form of segments 8-8-8, see the parameter "Signal point data format" of the "ADD OPC".
Table 2-232 Parameter description (2) Parameter Defau lt Value GUI Value Range Actual Value Range 1~16383 (BIT14), 1~65535 (BIT16), 1~16777215 (BIT24) Unit MML Command Im pac t
OSP code [Whole Number]
None
1~16777215 BIT14 (BIT14), BIT16 (BIT16), BIT24 (BIT24)
None
ADD OPC (Optional)
SC CP
OSP code bits OSP code [Divided Number]
None
BIT14, BIT16, BIT24 1~11 characters
None
ADD OPC (Mandatory) ADD OPC (Optional)
SC CP SC CP
None
None
None
2.78.5 Counters
None.
2.78.6 Glossary

l l l l l BSC6900 Feature List BSC6900 Basic Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
Issue 08 (2011-09-30)
1248
2.79 2G/3G Co-Transmission by TDM Switching

2.79.1 Introduction
2.79.1.1 Scope
This document describes the application scenario, principles, and networking of the 2G/3G CoTransmission by TDM Switching feature.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the 2G/3G Co-Transmission by TDM Switching feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.79.2 Overview of 2G/3G Co-Transmission by TDM Switching

With the 2G/3G Co-Transmission by TDM Switching feature, Huawei SingleRAN equipment uses the TDM timeslot cross connection function to enable the SDH to be shared by the GSM traffic and UMTS traffic. The GSM data flow involves TDM frames, which are carried on the
timeslots of an E1 link. The UMTS data flow involves ATM cells or IP packets. In UTRAN, the ATM cells or IP packets are mapped onto multiple E1 timeslots by using the fractional ATM or fractional IP function to implement the data transmission in TDM mode. This feature is applied to the initial phase of the 2G/3G co-deployment scenario, where Huawei SingleRAN solution is used. In the initial phase, services are comprised of 2G voice service and few 3G data service, and the bandwidth of transmission network is limited. The use of this feature can reduce the operational expenditure (OPEX) during network deployment.

2.79.3.1 Principle of Co-Transmission
Figure 2-325 shows the principle of the 2G/3G Co-Transmission by TDM Switching feature. Figure 2-325 Principle of the 2G/3G Co-Transmission by TDM Switching feature
Currently, only the TDM timeslots over the Abis interface can be shared between the 2G and 3G networks. Figure 2-326 shows the 2G/3G co-transmission by TDM switching over the Abis interface. The 2G data is transmitted on some E1 timeslots and the 3G data is transmitted on the remaining timeslots by using the fractional ATM or fractional IP technique. In this scheme, the BTS implements the timeslot cross connection through the backplane. On the BSC/RNC side, an external timeslot cross connection device DXX demultiplexes timeslots. Then, the DXX is connected to the BSC and RNC through different E1 cables. Figure 2-326 2G/3G co-transmission by TDM switching on the Abis interface
Issue 08 (2011-09-30)
1250
Huawei SingleRAN solution is based on the TDM co-transmission. Currently, only the TDM frames of 2G services and ATM cells or IP packets of 3G services can be shared on the TDM timeslots over the Abis interface. The BTS obtains clock signals from the E1 cable, and then sends the clock signals to the NodeB through the backplane. In this manner, the NodeB obtains steady clock signals from the BTS.
2.79.3.2 Networking Mode of Co-Transmission

Figure 2-327 shows the networking mode of 2G/3G co-transmission by TDM switching. Figure 2-327 Networking mode of 2G/3G co-transmission by TDM switching
Owning to the limitation on the OM link at the BTS, the OML must be configured on TS 31 of port 0 E1 at the BTS. Thus, in TDM co-transmission mode, the E1 cable is routed from the BTS. Normally, the 2G network provides the 3G network with the transmission channels for TDM timeslot switching.

Generally, the 2G network is deployed earlier than the 3G network in actual application. Thus, it is recommended that the BTS provide timeslot switching channels for the NodeB. It is not recommended that timeslot demultiplexing be performed on the BSC or RNC side. Normally, the timeslot cross connection device DXX closest to the BSC/RNC demultiplexes 2G and 3G timeslots, and then transmits the 2G and 3G timeslots to the BSC and RNC separately over two E1 cables. In this manner, the performance of multiplexing TDM transmission resources is maximized.
2.79.5 Parameters
None.
2.79.6 Counters
None.
2.79.7 Glossary

2.80 A Interface Circuit Management

2.80.1 Introduction
2.80.1.1 Scope
This document describes the A Interface Circuit Management functional area. It provides an overview of the main functions and goes into details regarding A Interface Circuit Management.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the A Interface Circuit Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-12)
01(2010-01-12)
2.80.2 Overview of A Interface Circuit Management

A Interface Circuit Management improves the network quality by ensuring a high success rate of call establishments and handovers, and providing value-added services for telecom operators with regard to operation, maintenance, and transmission quality. Huawei GBSS provides operators with the function of circuit management through the LMT, which facilitates operators to remotely perform operation and maintenance on the TC, such as locating faults on the TC. Circuit management helps improve the efficiency of and reduce the investment on operation and maintenance on the TC. Huawei GBSS supports A interface circuit management regardless of whether the TC is locally or remotely configured. Huawei GBSS also supports the blocking and unblocking of a single terrestrial circuit or group terrestrial circuits in the case of operations on the LMT or a device fault. The BSC re-sends BLOCK, UNBLOCK, GROUP BLOCK, GROUP UNBLOCK, and RESET CIRCUIT messages to the MSC if the BSC does not receive an acknowledgement message from the MSC within the timer set at the BSC. In addition, the function of circuit unequipped is supported. A Interface Circuit Management, which involves circuit assignment, circuit block, circuit unblock, group circuit block, group circuit unblock, circuit unequipped, and circuit reset, controls the operation and maintenance on a single circuit or on the entire PCM group circuits for the terrestrial circuit equipment. A Interface Circuit Management applies to only the TDM network.

2.80.3.1 Circuit Assignment
During a call or handover procedure, the MSC carries the information about requested resource (s) in the Assignment Request or Handover Request Message. If the requested resource(s) is/are for speech or data, it may also indicate the terrestrial circuit that is used between the MSC and BSS. The BSC assigns and occupies the A interface circuit as indicated in the signaling from the MSC. If the A interface circuit is successfully assigned and occupied, the BSC sends the MSC a message, indicating that the A interface circuit assignment is complete. If the A interface circuit indicated by the MSC is unavailable or blocked at the BSC, the BSC sends the MSC a message, indicating that the A interface circuit assignment fails. In addition, the BSC informs the MSC that the A interface circuit is unavailable in the circuit block procedure. If the A interface circuit indicated by the MSC does not exist at the BSC, the BSC sends the MSC a message, indicating that the A interface circuit assignment fails. In addition, the BSC informs the MSC that the A interface circuit does not exist in the circuit unequipped procedure.
2.80.3.2 Circuit Block

In the circuit block procedure, the BSC sends the MSC a BLOCK message, indicating that the circuit at the BSS is unavailable. The BLOCK message contains the Circuit Identification Code (CIC) that identifies the circuit over the A interface. In this way, the state of the circuit at the BSC and that of the circuit at the MSC are consistent. Figure 2-328 shows the procedure for circuit block. Figure 2-328 Procedure for circuit block
Through circuit block, the circuit at the BSS and that at the MSC are blocked at the same time. The procedure for circuit block can be triggered by running the BLK ACIC command and setting Operation Mode to BYCICVALUE in the case of circuit assignment, handover, or device fault. The BSC sends BLOCK ACK messages to the MSC repeatedly at an interval until the BSC receives a BLOCK ACK message from the MSC. The interval can be set by setting T1 in the SET BSCTMR command. The circuit at the BSC is blocked even if the BSC does not receive any BLOCK ACK message from the MSC. The circuit is blocked after a call ends. Therefore, circuit block does not affect the circuit on call.
2.80.3.3 Circuit Unblock

In the circuit unblock procedure, the BSC sends the MSC a message, informing the MSC of the latest circuit state at the BSC, when a fault is rectified or a circuit becomes available at the BSC. The UNBLOCK message contains a CIC that identifies the circuit over the A interface. Figure 2-329 shows the procedure for circuit unblock.
Issue 08 (2011-09-30)
1254
Figure 2-329 Procedure for circuit unblock
Through circuit unblock, the blocked circuit at the BSC becomes idle. The procedure for circuit unblock can be triggered by running the UBL ACIC command and settingOperation Mode to BYCICVALUE on the LMT. The BSC sends UNBLOCK messages to the MSC repeatedly at an interval until the BSC receives an UNBLOCK ACK message from the MSC. The interval can be set by setting T1 in the SET BSCTMR command. The circuit at the BSC is idle even if the BSC does not receive any UNBLOCK ACK message from the MSC.
2.80.3.4 Group Circuit Block

Group circuit block is used when multiple A interface circuits need to be blocked at the same time. The GROUP BLOCK message contains multiple CICs that identify the circuits over the A interface. Figure 2-330 shows the procedure for group circuit block. Figure 2-330 Procedure for group circuit block
Through group circuit block, multiple A interface circuits can be blocked at the same time. The procedure for group circuit unblock can be triggered by running the BLK ACIC command and
setting Operation Mode to BYCICRANGE on the LMT. Group circuit block applies to only GSM Phase II and GSM Phase II Plus. The BSC sends GROUP BLOCK messages to the MSC repeatedly at an interval until the BSC receives a GROUP BLOCK ACK message from the MSC. The interval can be set by setting T20 in the MOD BSCTMR command. The circuits at the BSC are blocked even if the BSC does not receive any GROUP BLOCK ACK message from the MSC. The circuits are blocked after a call ends. Therefore, group circuit block does not affect the circuits on call.
2.80.3.5 Group Circuit Unblock

Group circuit unblock is used when multiple A interface circuits need to be unblocked at the same time. The GROUP UNBLOCK message contains multiple CICs that identify the circuits over the A interface. Figure 2-331 shows the procedure for group circuit unblock. Figure 2-331 Procedure for group circuit unblock
Through group circuit unblock, multiple A interface circuits can be unblocked at the same time. The procedure for group circuit unblock can be triggered by running the UBL ACIC command and setting Operation Mode to BYCICRANGE on the LMT. Group circuit unblock applies to only GSM Phase II and GSM Phase II Plus. The BSC sends GROUP UNBLOCK messages to the MSC repeatedly at an interval until the BSC receives a GROUP UNBLOCK ACK message from the MSC. The interval can be set by setting T20 in the SET BSCTMR command. The circuits at the BSC are idle even if the BSC does not receive any GROUP UNBLOCK ACK message from the MSC.
2.80.3.6 Circuit Unequipped

The BSC sends the MSC an UNEQUIPPED CIRCUIT message if the required circuit indicated by the MSC does not exist in the following processes: l l
Issue 08 (2011-09-30)
Circuit block Circuit unblock

l l l l
Circuit reset Circuit assignment Incoming-BSC handover BSC reset
Figure 2-332 shows the procedure for circuit unequipped. Figure 2-332 Procedure for circuit unequipped
Through the circuit unequipped procedure, the BSC notifies the MSC that the indicated circuit does not exist and therefore the MSC should not use the circuit. The BSC triggers the circuit unequipped procedure in any circuit-associated procedure as long as the BSC receives a message that carries the information element (IE) about unequipped circuit from the MSC. Circuit unequipped is applicable only to GSM Phase II and GSM Phase II Plus. There is no acknowledgement message in response to the UNEQUIPPED CIRCUIT message in the circuit unequipped procedure. In addition, the BSC sends the UNEQUIPPED CIRCUIT message to the MSC only once.
2.80.3.7 Circuit Reset

After part of a system fails, for example, the SCCP link is released abnormally, the circuit at the BSC or MSC can be restored through circuit reset. If a circuit is idle after the SCCP link is released abnormally, the BSC sends a RESET CIRCUIT message to the MSC. Figure 2-333 shows the procedure for circuit reset initiated by the BSC. Figure 2-333 Procedure for circuit reset
Issue 08 (2011-09-30)
1257
After receiving a RESET CIRCUIT message from the BSC, the MSC removes all the calls on the circuit and sets the circuit to idle, and then sends a RESET CIRCUIT ACK message to the BSC. If the BSC does not receive the RESET CIRCUIT ACK message from the MSC, it re-sends a RESET CIRCUIT message to the MSC only once every interval. The interval can be set by setting T19 in the SET BSCTMR command. The circuit at the BSC is idle even if the BSC does not receive any RESET CIRCUIT ACK message from the MSC. The procedure for circuit reset can be triggered by running the RST ACIC command on the LMT.
2.80.4 Parameters
This chapter describes the parameters related to A Interface Circuit Management. For the meaning of each parameter, see Table 2-233. For the default value, value ranges, and MML commands of each parameter, see Table 2-234. Table 2-233 Parameter description (1) Parameter Description Timer for waiting for a single A-interface circuit blocking or unblocking answer. The BSC6900 starts this T1 timer after sending a single A-interface circuit blocking or unblocking message. If the BSC6900 does not receive a blocking or unblocking answer from the MSC before this timer expires for the first time, the BSC6900 resends the single A-interface circuit blocking or unblocking message to the MSC. If the timer expires for the second time, the BSC6900 reports an alarm for BSC circuit blocking or unblocking failure. Timer for waiting for an A-interface circuit reset answer. The BSC6900 starts this timer after sending an A-interface circuit reset message. When this timer expires for the first time, the BSC6900 resends the circuit reset message to the MSC. If this timer expires for the second time, the BSC6900 reports an alarm for BSC circuit resetting failure. Timer for waiting for an A-interface circuit group blocking or unblocking answer. After sending a CIC group blocking/ unblocking message over the A interface, the BSC6900 starts the timer T20. If the BSC6900 fails to receive a response from the MSC before the first expiry of T20, the BSC6900 resends the CIC group blocking/unblocking message. If no response is received before the second expiry of T20, the system reports the BSC Unable to Block Group Circuits or BSC Unable to Unblock Group Circuits alarm. It is one key filed of identifying A interface CIC status and indicates the alignment mode of A interface circuit.
T1
T19
T20 Operation Mode
Issue 08 (2011-09-30)
1258
Table 2-234 Parameter description (2) Parameter Defau lt Value 30 30 30 GUI Value Range Actual Value Range 1~300 1~300 1~300 Unit MML Command SET BSCTMR (Optional) SET BSCTMR (Optional) SET BSCTMR (Optional) Imp act
T1 T19 T20
1~300 1~300 1~300 BYCICRAN GE(BY CIC RANGE), BYCICVAL UE(BY CIC VALUE)
s s s
BSC BSC BSC
Operation Mode
None
BYCICRAN GE, BYCICVAL UE
None
BLK ACIC (Mandatory)
E1/ T1 link
2.80.5 Counters
2.80.6 Glossary

2.81 A Interface Protocol Process

2.81.1 Introduction
2.81.1.1 Scope
The A Interface Protocol Process feature involves the processing of the DTAP and BSSMAP protocols. This document describes the basic concepts of DTAP and BSSMAP and related procedures.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the A Interface Protocol Process feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-12)
2.81.2 Overview of A Interface Protocol Process

A Interface Protocol Process, a basic signaling function stipulated in 3GPP specifications, is supported by Huawei GSM BSS. The processing of A interface signaling and protocol of Huawei GSM BSS is compliant with international standard protocols, and thus Huawei GSM BSS equipment can interconnect with the MSC from other vendors. Telecom operators can compare the MSCs from different vendors and invite bids accordingly, thus avoiding monopolization and reducing operation expenditure (OPEX). The underlying transport mechanism defined to carry signaling information between the BSS and the MSC is the Message Transfer Part (MTP), and the Signaling Connection Control Part (SCCP) of Signalling System No.7.
The MTP and SCCP are used to support communication between the MSC and the conceptual entities within the BSS, the BSS Application Part (BSSAP). The BSS Application Part is split into two sub application parts as follows: l l The Direct Transfer Application Part (DTAP); The BSS Management Application Part (BSSMAP).

2.81.3.1 The Direct Transfer Application Part
The Direct Transfer Application Part (DTAP) is used to transfer call control and mobility management messages between the MSC and the MS. l Mobility management (MM) messages consist of the messages related to the authentication, CM service request, identification request, IMSI detach, location update, MM status, and TMSI re-assignment. Call control (CC) messages consist of the messages related to the alerting, call proceeding, connection, establishment, modification, release, disconnection, notification, status query, and DTMF startup.
The DTAP information in these messages is not interpreted by the BSS.
2.81.3.2 The BSS Management Application Part

The BSSMAP supports all the procedures between the MSC and the BSS that require interpretation and processing of information related to single calls, and resource management.
2.81.3.3 BSSMAP Procedures

This sub-clause describes the procedures used in the BSS Management Application Part. There are the following main procedures: Assignment Blocking Reset Handover required indication Handover resource allocation Handover execution Handover candidate enquiry Release Paging Flow control Classmark update
Cipher mode control Trace invocation Initial MS message Queuing indication Data link control SAPI not equal to 0 Reset circuit Location Aquisition Connectionless Information Transfer Common ID
2.81.4 Parameters
None.
2.81.5 Counters
None.
2.81.6 Glossary

l l BSC6900 Feature List BSC6900 Basic Feature Description
2.82 A Interface Occupation Rate Monitoring

2.82.1 Introduction
2.82.1.1 Scope
This document describes the A Interface Occupation Rate Monitoring feature of Huawei GSM BSS. It provides an overview of the functions and mechanisms regarding the A Interface Occupation Rate Monitoring feature.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the A Interface Occupation Rate Monitoring feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.82.2 Overview of A Interface Occupation Rate Monitoring

This feature monitors the real-time status and usage of the circuits on the A interface and TC resources through performance measurement. This feature is important for ensuring the network quality. It provides the following benefits for the operators: l l Operators can learn the usage of the circuit resources of the A interface in time, thus providing a basis for the system capacity expansion. Operators can know about the distribution status of the circuit resources of the A interface in time, coordinate the configuration of transmission resources among networks, and add, reduce, and re-allocate the transmission resources on the basis of the usage of resources, thus reducing the network operation cost. Operators can find the defects of the network planning, thus improving the principles and methods of the existing network planning.

This feature is implemented through performance measurement of the BSC.
This feature monitors the usage of the circuits on the A interface and TC resources in different states through performance measurement of the BSC. The monitoring result helps the operator to be well-informed about the usage of present resources. The counters used in this feature are classified into following types: l Counters for the timeslot usage on the A interface These counters provide the occupation times, occupation duration, and work status of each timeslot (TS1 to TS31) in the trunk circuit over the A interface. These counters are helpful to A interface circuit troubleshooting. l Counters for the circuit resources on the A interface These counters provide the circuits in faulty, idle, uninstalled, maintenance, blocked, busy, and peer-uninstalled state. If the A interface circuits are in various states, the number of corresponding circuits in each state is measured and the results are provided in the sequence of local-uninstalled, busy, maintenance (faulty and blocked), faulty, peer-uninstalled, blocked, and idle. l Counters for TC resources in the BM and TC subracks These counters provide the number of faulty, idle, busy, maintenance, and prohibited TC resources in the BM and TC subracks. If the TC resources are in various states, the respective number of TC resources in each state are measured and the results are provided in the sequence of busy, maintenance (faulty and blocked), faulty, blocked and idle.
NOTE
In TC pool mode, the TC resources can be differentiated by their BSC IDs. The main BSC calculates all TC resources in all TC subracks. TC resources that are in the maintenance (faulty and blocked), faulty, blocked, and idle state in TC subracks belong to the main BSC; whereas the TC resources that are in the busy state in TC subracks belong to their respective BSCs. The secondary BSCs calculate the TC resources in their respective BM subracks.
2.82.4 Parameters
None.
2.82.5 Counters
2.82.6 Glossary

l l l
Issue 08 (2011-09-30)
BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM Performance Counter Reference.
2.83 Adjustment of Adaptive Timing Advance

2.83.1 Introduction
2.83.1.1 Scope
The A Interface Protocol Process feature involves the processing of the DTAP and BSSMAP protocols. This document describes the basic concepts of DTAP and BSSMAP and related procedures.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Adjustment of Adaptive Timing Advance feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-12)
2.83.2 Overview of Adjustment of Adaptive Timing Advance

In the GSM system, an uplink is a radio link for transmitting signals from an MS to a BTS whereas a downlink is for transmitting signals from a BTS to an MS. The Time Division Multiple
Access (TDMA) frame of an uplink is performed three bursts later than that of a downlink, that is, about 1730 s. Transmission delay between the MS and the BTS, however, changes due to MS mobility. To compensate for transmission delay jitter, the MS must transmit signals to the BTS by a certain time period in advance. The time period is referred to as a Timing Advance (TA). An MS in dedicated mode must transmit signals in an appropriate TA. Otherwise, there is no synchronization between the MS and the BTS . In the GSM system, adjustment of adaptive timing advance is applied to ensure that each MS in dedicated mode uses an appropriate TA. Thus, the signals transmitted by the MSs that have different distances from the BTS can arrive at the BTS in sequence to avoid signal conflict and MS intervention.

By means of adjustment of adaptive timing advance, the TA offset of an MS can be reduced to +1 or -1 time length of a symbol. In the GSM system, TDMA technology is applied over the Um interface. Each MS must transmit signals in the assigned timeslot, and the BTS must receive the signals in the corresponding timeslot. Figure 2-334 shows the delay offset of signals received by the BTS when the MS is traveling away from position P1, to P2, and then to P3. It is assumed that the MS originally occupies timeslot 1 (TS1). That is, the signals transmitted by the MS are expected to arrive at the BTS in TS1, as shown in Figure 2-334. When the MS is close to the BTS, the transmission delay is short, and the BTS can receive signals from the MS right in TS1. When the MS travels away from the BTS, the transmission delay is prolonged and the signals transmitted by the MS may arrive at the BTS in a later TS if the TA is not adjusted. For example, as shown in Figure 2-334, when the MS moves to P3, some signals from the MS arrive in TS2. These signals are overlapped by the signals from other MSs and also arrive in TS2, and thus they cannot be decoded appropriately. Figure 2-334 Signal reception with TA unchanged
To avoid this problem, the base station subsystem (BSS) monitors the required transmission time of each signal from the MS to the BTS and notifies the moving MS of TA adjustment. Then, the MS transmits signals with the adjusted TA. This ensures that all signals from the MS can be received by the BTS in TS1, as shown in Figure 2-335. A TA value ranges from 0 s to 233 s. The TA value affects the radio coverage of cells.
Figure 2-335 Signal reception with adjusted TA
In the GSM system, the TA value is an integer ranging from 0 to 63. It refers to the time required for transmitting 0- to 63-bit data. If the TA value is 0, the MS need not transmit signals in advance; if the TA value is 63, there is a maximum distance between the MS and the BTS , that is, approximately 35 km. If the MS transmits signals at a distance greater than 35 km, the signals arrive at the BTS in the next timeslot and cannot be decoded appropriately. Through adjustment of adaptive timing advance, the TA offset of the MS can be reduced to +1 or -1 time length of a symbol. By setting Max TA, the BSC can specify the maximum TA value of MSs in each cell. It is recommended that Max TA of MSs in common cells be set to 62.
2.83.4 Parameters
This chapter describes the parameters related to Adjustment of Adaptive Timing Advance. For the meaning of each parameter, see Table 2-235. For the default value, value ranges, and MML commands of each parameter, see Table 2-236. Table 2-235 Parameter description (1) Parameter Description This parameter specifies the actual coverage area of a cell. After receiving the channel request message or handover access message, the BTS determines whether the channel assignment or handover is performed in the cell by comparing the TA and the value of this parameter. The value of this parameter is determined by that of "Cell Extension Type" in the "ADD GCELL" command.
Max TA
Issue 08 (2011-09-30)
1267
Table 2-236 Parameter description (2) Parameter Defau lt Value GUI Value Range Actual Value Range Unit MML Command SET GCELLBASICP ARA(Optional) Imp act
Max TA
62
0~255
0~255
None
Cell
2.83.5 Counters
2.83.6 Glossary

l l l l l l 3GPP TS 45.002: "Multiplexing and multiple access on the radio path" BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 GSM Performance Counter Reference
2.84 Ater Interface 4:1 Multiplexing

2.84.1 Introduction
2.84.1.1 Scope
This document describes the principles of Ater Interface 4:1 Multiplexing.

Issue 08 (2011-09-30)


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Ater Interface 4:1 Multiplexing feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-12)
2.84.2 Change History

The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Ater Interface 4:1 Multiplexing feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-12)
2.84.3 Overview of Ater Interface 4:1 Multiplexing

The transmission cost is very high in network deployment. Operators seek suitable technologies to decrease the required transmission bandwidth, therefore reducing the transmission cost. In addition, the transmission quality must be guaranteed.
To achieve this purpose, Ater interface multiplexing is introduced and the BM/TC separated mode is applied. That is, multiplexing on the Ater interface is implemented when the TC is configured on the MSC side. In this manner, the transmission cost is reduced significantly. Huawei BSC supports 4:1 multiplexing on the Ater interface through the TC (TRAU). That is, the four timeslots on the E1 of the A interface can be multiplexed onto a timeslot on the Ater interface through the TC. In this process, the previous PCM frame of 64 kbit/s can be converted into the TRAU frame of 16 kbit/s, and therefore reducing the required transmission bandwidth.

In the telephone exchange network, the voice coding scheme is Pulse Code Modulation (PCM) and the rate is 64 kbit/s. According to GSM specifications, PCM must be applied on the A interface. To save the radio channel resources, data transmission between the MS and the BTS adopts the voice coding scheme RPE-LTP or CELP whose rate is 13 kbit/s (16 kbit/s for transmission) or other coding schemes with an even lower rate(for example, 8 kbit/s). If a call service attempts to be set up between the MS and the MSC, the voice codec is converted from 13 kbit/s codec to 64 kbit/s codec. The voice codec conversion is implemented in the TC (TRAU) unit. Before the conversion, the voices are exchanged and transmitted on the 16-kbit/s channels in the BSC. The Ater interface is an internal interface between the TC processing unit and the service processing module (BM). Figure 2-336 shows the interfaces between network elements (NEs). Figure 2-336 Interfaces between NEs
On the Ater interface, Huawei BSC supports 4:1 multiplexing. That is, the four timeslots on the E1 of the A interface can be multiplexed onto a timeslot on the Ater interface. Figure 2-337 shows 4:1 multiplexing on the Ater interface. Figure 2-337 multiplexing on the Ater interface
On the Ater interface, Huawei BSC supports the multiplexing of four voice channels to an E1 timeslot of 64 kbit/s. When the TC subrack is configured on the MSC side, the remote transmission resource can be saved by 75%.
Huawei introduces a new feature of resource pool and integrates it into the BSC. With this feature, links on the Ater interface work in resource pool mode and can be inconsistent with the CICs on the A interface. This improves the network reliability. The resources on the Ater interface involve the timeslots of 16 kbit/s and 8 kbit/s. When a call connection is established, according to the service type, the Ater timeslots of 16 kbit/s are used if the TCHs/F are allocated on the Um interface; the Ater timeslots of 8 kbit/s are used if the TCHs/H are allocated on the Um interface. In this way, the resources on the Ater interface can be fully utilized and more than 75% of resources can be saved.

Huawei provides a flexible networking solution for operators. That is, the TC can be configured on either the BSC side or the MSC side. Ater Interface 4:1 Multiplexing can be used together with TC pool. Ater Interface 4:1 Multiplexing can be used on the TDM-based A interface but not on the IPbased A interface. The transmission resources on the TDM-based Ater interface are planned to occupy 25% of the total interface transmission capacity.
2.84.6 Parameters
None.
2.84.7 Glossary
2.84.8 Counters

l l l 3GPP TS 48.002: "Base Station System - Mobile-services Switching Centre (BSS - MSC) interface; Interface principles" BSC6900 Feature List BSC6900 Basic Feature Description
2.85 Authentication
2.85.1 Introduction
2.85.1.1 Scope
This document describes the function and purpose of authentication, authentication procedures, and handling of successful and failed authentication on the network side.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Authentication feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-12)
2.85.2 Overview of Authentication

Authentication is a procedure in which the GSM network verifies the validity of the identity of an MS, that is, verifies the validity of the International Mobile Subscriber Identity (IMSI) or Temporary Mobile Subscriber Identity (TMSI) transmitted over the Um interface. Authentication aims to prevent unauthorized subscribers from accessing the network and to protect the private information of authorized subscribers. The functions of authentication are as follows: l l To check whether the MS is authorized to access the network To provide parameters that enable the MS to calculate a new ciphering key
The authentication procedure is always initiated and controlled by the network.


2.85.3.1 Authentication Principles
The network initiates the authentication procedure in the following situations: l l l l The MS requests to change the subscriber information restored in VLR or HLR. Service access is initiated. For example, when the MS originates a call, the MS is called, activated, or deactivated, or the supplementary service is initiated. The MS accesses the network for the first time after the MSC/VLR restarts. The ciphering key Kc on the network does not match that on the MS.
The authentication procedure uses an authentication triplet, namely, RAND, Kc, and SERS. The authentication triplet is calculated in the authentication center (AUC) of the GSM network. When registering in a GSM network, each subscriber is assigned a Mobile Station International ISDN Number (MSISDN) and an IMSI. The IMSI is written into the SIM through a SIM writer. The SIM writer also generates an authentication parameter Ki, which is stored in the SIM and the authentication center . The IMSI and Ki are permanent information. A pseudo-random number generator is used in the AUC to generate an unpredictable pseudo random number RAND. In the AUC, the RAND and Ki are used to generate a signed response (SRES) through algorithm A3 and to generate a ciphering key Kc through algorithm A8. The three parameters RAND, Kc, and SERS constitute an authentication triplet, which is stored as part of the subscriber data in the HLR. Generally, the AUC sends five groups of authentication triplets to the HLR at one time. The HLR automatically stores them. The HLR can store ten groups of authentication triplets. Upon request, the HLR sends five groups of authentication triplets to the MSC/VLR at one time. The MSC/VLR uses the authentication triplets one by one. When only two groups are remaining, the MSC/VLR requests the HLR for new authentication triplets again. The network initiates an authentication procedure by sending an Authentication Request message to the MS and starts timer T3260. The Authentication Request message carries a 128bit RAND, which is used to calculate the values of the authentication response parameters. This message also carries the Ciphering Key Sequence Number (CKSN) assigned to the ciphering key. Upon receiving the Authentication Request message, the MS calculates the SRES required by the Authentication Response message and the new ciphering key Kc. After writing the new ciphering key Kc and the CKSN into the SIM, the MS sends an Authentication Response message to the network. Upon receiving the Authentication Response message, the network stops timer T3260 and checks whether the Authentication Response message is valid.
2.85.3.2 Authentication Procedure Authentication Success

Figure 2-338 shows a successful authentication procedure.
Issue 08 (2011-09-30)
1273
Figure 2-338 Authentication Success
l l
The Authentication Request message carries a 128-bit RAND and a Ciphering Key Sequence Number (CKSN). The Authentication Response message carries an SRES, which is calculated on the basis of the RAND and Ki through algorithm A3.
The network compares the stored SRES with the SRES carried in the Authentication Response message. If the SRESs are the same, the authentication is successful. After the authentication succeeds, subsequent procedures, for example, the ciphering procedure, are initiated.
Authentication Failure
If the authentication fails, that is, if the Authentication Response message is invalid, the network may distinguish between the following two ways of identification used by the MS. If the TMSI is used, the network initiates the identification procedure. l l If the IMSI provided by the MS differs from that in the network, the network restarts the authentication procedure. If the IMSI provided by the MS is the expected one, the network responds with an Authentication Reject message.
If the IMSI is used, the network responds with an Authentication Reject message.
Issue 08 (2011-09-30)
1274
Figure 2-339 Authentication Failure
After sending an Authentication Reject message to the MS, the network releases all the existing MM connections and restarts an RR connection release procedure. Upon receiving the Authentication Reject message, the MS sets the roaming flag to prohibited and deletes the information such as TMSI, LAI, and ciphering key. If the Authentication Reject message is received when the MS is in the IMSI Detach Initiated state, timer T3220 will be stopped after the RR connection is released. The MS, if possible, starts the local release procedure after the normal release procedure is complete or timer T3220 expires. If it is not possible, for example, during IMSI detachment at MS power-off, the RR sublayer on the MS side is aborted. If the Authentication Reject message is received in any other state, the MS aborts any MM connection establishment or call re-establishment procedure, stops timer T3210 or T3230, releases all the MM connections, starts timer T3240, enters the Wait For Network Command state, and waits for the release of the RR connection. If the RR connection is not released after timer T3240 expires, the MS aborts the RR connection. In both cases, either after an RR connection release triggered by the network or after an RR connection abort requested by the MS, the MS enters the NO IMSI state, which is a sub-state of the MM Idle state.
2.85.4 Parameters
None.
2.85.5 Counters
None.
2.85.6 Glossary

l l l l l 3GPP TS 24.008 3GPP TS 42.009 3GPP TS 43.020 BSC6900 Feature List BSC6900 Basic Feature Description
2.86 Board Switchover

2.86.1 Introduction
2.86.1.1 Scope
This document describes the Board Switchover feature of Huawei GSM BSS. It provides an overview of the main functions and working principles regarding the Board Switchover feature.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Board Switchover feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
Issue 08 (2011-09-30)
01(2010-01-20)
01(2010-01-20)
2.86.2 Overview of Board Switchover

Telecommunication systems play an important role in the economy of a nation In the telecommunication system, the reliability and availability of telecommunication equipment are of vital importance. Huawei GBSS provides the 1+1 backup solution for all boards (except for the boards that are designed to work in the resource pool mode). That is, the boards are configured in the active/standby mode, and a switchover can be performed between the active and standby boards when the active board is faulty. The active/standby mode for BSC boards improves the reliability of the GBSS system, prolongs the Mean Time Between Failures (MTBF), and prevents service disruption caused by a faulty board. In the case of the boards that work in the active/standby mode, the active board processes services, and the standby board performs real-time backup for the active board. When the active board becomes faulty, the system automatically performs a switchover. After the switchover, the standby board takes over the role of the active board and processes services. Under this circumstance, the switchover between the active and standby boards ensures the normal operation of the system. There are two types of switchovers, namely, automatic switchover and manual switchover. An automatic switchover is triggered by the system if the active board is faulty. A manual switchover is performed by the maintenance engineer on the LMT. The maintenance engineer sends an immediate switchover command to the system, which then instructs the related boards through a dedicated maintenance module to perform a switchover if the switchover is allowed. To ensure a successful switchover, the following conditions must be met: l l The standby board is available and works normally. No major or critical alarm is reported.
After the standby board is switched over to the active state, the previously active board will be automatically reset. If the previously active board restarts normally, it is switched over to the standby state. The BSC boards that support the board switchover feature include the SCUa, TNUa, GCUa, GCGa, and all types of XPU boards and interface boards. The DPU boards do not support the board switchover feature, because the DPU boards are designed to work in the resource pool mode.

When an automatic switchover is triggered or a manual switchover is performed, the active and standby boards are switched over. Figure 2-340 shows the working principle of the board switchover.
Issue 08 (2011-09-30)
1277
Figure 2-340 Working principle of the board switchover
There is a logical circuit between an active board and a standby board. Through the logical circuit, one can query whether a board serves as the active board or the standby board and whether the corresponding standby board or the corresponding active board is present. In addition, the logical circuit can be used to perform a switchover. Under normal conditions, there is a service channel between the active board and other boards. The service channel carries all services processed by the active board. The active and the standby boards are connected through a backup channel. Through the backup channel, the standby board synchronizes itself with the active board. In this manner, the standby board can always obtain the latest data and maintain the consistency with the active board. When an automatic switchover is triggered or a manual switchover is performed, the active and standby boards are switched over. In such a case, the previously standby board takes over the role of the active board, and the previously active board is reset. After taking over the role of the active board, the previously standby board starts data configuration according to the backup data. The data configuration includes the configuration of chips, transmission channels, operating system, and upper-level software. The switchover does not affect the other boards that are connected to the previously active board. There is also an operation channel between the active and standby boards. This channel is not shown in the preceding figure.
2.86.4 Parameters
This chapter describes the parameters related to the Board Switchover feature. For the meaning of each parameter, see Table 2-237. For the default value, value ranges, and MML commands of each parameter, see Table 2-238. Table 2-237 Parameter description (1) Parameter Backup Slot No. Description Whether to back up the data of the board. Number of the slot.
Issue 08 (2011-09-30)
1278
Table 2-238 Parameter description (2) Parameter Defau lt Value None GUI Value Range YES(YES), NO(NO) Actual Value Range YES, NO Unit MML Command ADD BRD (Mandatory) SWP BRD ADD BTSAUTOPLA N SET PSCELLTODSP ADD NSVLLOCAL ADD NSVC ADD BC STR FRPORTLOOP SET BFDPROTOSW SET MSP SET MSPCMD CMP TBLDATA SYN BRDAREA LOD BRD ADD BRD SET TCTYPE SET DPUBRDTYPE SET MPUBIND ADD XPUVLAN SET XPUPORT SET CLK ULD RSTINFO CMP BRDAREA Slot No. None 0~27 0~27 None STR BKP Non e Im pac t Boa rd
Backup
None
2.86.5 Counters
None.
Issue 08 (2011-09-30)
1279
2.86.6 Glossary

2.87 BSC Cabinet/Subrack Sharing

2.87.1 Introduction
2.87.1.1 Scope
This document describes the implementation principles and functions of the BSC Cabinet/ Subrack Sharing feature.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BSC Cabinet/Subrack Sharing feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
01(2010-01-20)
2.87.2 Overview of BSC Cabinet/Subrack Sharing

With the BSC Cabinet/Subrack Sharing feature, various devices share the cabinet or subrack. Thus, the network is more integrated and the maintenance of the access network and the core network is unified. This reduces the space occupied by the equipment, thus saving the investments at an early stage and reducing the maintenance costs.
NOTE
The implementation of the BTS cabinet sharing scheme is determined by the actual traffic volume on the network, transmission networking, and proportions of the call services of the local users.

2.87.3.1 BSC Cabinet Sharing
Huawei BSC/TC/MGW adopts Huawei N68E-22 cabinet, the design of which complies with the IEC 60297 and IEEE standards. Huawei BSC allows the BSC, TC, and MGW to share one N68E-22 cabinet, thus reducing the equipment space and the costs. Figure 2-341 shows the BSC cabinet sharing. Figure 2-341 BSC cabinet sharing
Issue 08 (2011-09-30)
1281

NOTE
Huawei soft handover products consist of MSC server (MSS) and MGW. The MSS is responsible for controlling calls and signaling, and the MGW is responsible for switching and transmission of the actual services.
The networking in the case of BSC cabinet sharing can adopt the distributed architecture by placing the MSS in the center of the urban areas and placing the MGW in locations closer to the radio access network. In this manner, when the calling party and the called party are controlled by the same MGW, the switching can be completed within the MGW without using the MSS. Thus, the transmission resources between the BSC and the MGW are saved. Figure 2-342 shows the networking for BSC cabinet sharing. Figure 2-342 Networking for BSC cabinet sharing
2.87.3.2 BSC Subrack Sharing

In the version later than GBSS8.0, the PCU is integrated in the DPUd, and the BSC, DPUc, and DPUd are placed in the same subrack. In this manner, the BSC, TC, and PCU share the same subrack. That is, the CS services and PS services are implemented in the same subrack. One cabinet can provide the CS and PS services of 2048 TRXs. In this manner, the system is more integrated, and the equipment space and the operation and maintenance costs are reduced. Figure 2-343 shows the BSC subrack sharing.
Issue 08 (2011-09-30)
1282
Figure 2-343 BSC subrack sharing
2.87.4 Parameters
None.
2.87.5 Counters
None.
2.87.6 Glossary

l l l l l BSC6900 N68E-22 Cabinet Installation Guide BSC6900 GSM Installation Guide GBSS9.0 BSC6900 Feature List GBSS9.0 BSC6900 Basic Feature Description BSC6900 GSM Initial Configuration Guide
2.88 BTS Power Management

2.88.1 Introduction
2.88.1.1 Scope
This document describes the BTS Power Management feature. It mainly covers the two basic functions provided by the BTS Power Management feature, that is, hierarchical power-off and voltage abnormal protection.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BTS Power Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.88.2 Overview of BTS Power Management

BTS Power Management supports hierarchical power-off and voltage abnormal protection. The BTS Power Management feature enhances power management and self-protection of the BTS, thus improving the reliability of the system and prolonging the lifespan of products and the serving time of the system. With this feature, the BTS stability is improved, thus improving the Quality of Service (QoS). In addition, the O cost for the BTS is reduced, thus indirectly increasing the revenue of operators.

The BTS hierarchical power-off function takes effect when the mains supply is not available. This function aims at reducing the power consumption of the BTS equipment and thus extends
the discharge time of the battery. In addition, the BTS hierarchical power-off function can also prevent over-discharging of the battery. The BTS hierarchical power-off function also takes effect when the working environment in the BTS cabinet is severe, for example, when the temperature inside the BTS cabinet exceeds the predefined thresholds or when the Voltage Standing Wave Ratio (VSWR) exceeds the limits by a huge margin. In such cases, the system automatically shuts down the Power Amplifiers (PAs) for some TRXs to reduce the heat consumption.
Hierarchical power-off
When mains supply is not available, the BTS hierarchical power-off function is performed to reduce the power consumption and extend the discharge time of the battery. In this case, the system automatically blocks all TRXs, except the BCCH TRX. This is called a soft shutdown. When the capacity of the battery drops to the preset value, the system automatically shuts down all the TRXs to prevent over-discharging of the battery. This is called a hard shutdown. You can configure whether or not to use the automatic power. The hierarchical power-off function especially suits the cascaded BTSs. When the mains power of the upper-level BTS is disconnected and the mains power of the lower-level BTS is normal, this function can be used to prolong the working time of the transmission module of the upper-level BTS to reduce the impact on the lower-level BTS.
Voltage abnormal protection

When the working environment is severe or the temperature regulation unit does not work properly, the TMU shuts down the PAs for some TRXs to reduce the heat consumption if the temperature inside the cabinet exceeds the predefined thresholds. This prevents any negative impact on the system. If the TRX is faulty or the VSWR exceeds the limits by a huge margin, the TRX becomes out-of-service and is shut down. The PA for the TRX is also shut down. This is performed to minimize the possibility of absolute damage. You can configure whether or not to use this function and the related parameters. In this manner, the flexibility of the system is improved.

This chapter provides engineering guidelines regarding the configuration of the BTS Power Management feature.
Support of Hierarchical Power-off

The SET BTSAPMUBP command is executed on the LMT to enable the hierarchical poweroff function. Note that the Board Parameter Configuration Enabled parameter must be set to YES(YES) to enable the configuration of other parameters. The Hierarchical Power-off Config. Enabled parameter is set to YES(YES), which indicates that the hierarchical poweroff function is enabled. The Load Shutdown Voltage parameter is set to 440, which is the threshold of the battery capacity. When the battery capacity drops to a value smaller than 440, a hard shutdown is performed. Note that the Load Shutdown Voltage parameter is set to 475 when the Power System Type parameter is set to SC48200(SC48200), and that the Load Shutdown Voltage parameter is always set to 4294967295 (equals to the hexadecimal number FFFFFFFF) and cannot be modified when the Power System Type parameter is set to EPS4815 (EPS4815). One is advised to set the Load Shutdown Voltage parameter to 440 when the Power System Type parameter is set to values other than SC48200(SC48200) and EPS4815 (EPS4815). The Load Shutdown Flag parameter is set to ENABLE(ENABLE), which indicates that the hard shutdown function is validated.
Support of Voltage Abnormal Protection

The SET BTSAPMUBP command is executed on the LMT to enable the voltage abnormal protection function. Note that the Board Parameter Configuration Enabled parameter must be set to YES(YES) to enable the configuration of other parameters. The High Temp Load Power Offparameter is set to YES(YES), which indicates that the PA for the TRX will be shut down when the temperature rises to a high value. The Shutdown Temperature parameter is set to 52, which indicates that the PA for the TRX is shut down only when the temperature inside the cabinet reaches 52C. The PA is automatically shut down when the VSWR far exceeds the limits or the TRX is faulty. Therefore, the PA shutdown function does not need to be configured for these two cases.
2.88.5 Parameters
This chapter describes the parameters related to the the Power Management feature. For the meaning of each parameter, see Table 2-239. For the default value, value ranges, and MML commands of each parameter, see Table 2-240. Table 2-239 Parameter description (1) Parameter Description Whether to allow the configuration of alarm parameters. The value "YES" indicates that the configuration is allowed, and the value "NO" indicates that the configuration is not allowed. If the parameter is set to "YES", all the other parameters are reset to the default values in this command. In multi-mode scenario, the value of this parameter in one mode must be the same as the value of the corresponding parameter in another mode. Whether to enable the configuration of power system parameters. In multi-mode scenario, the value of this parameter in one mode must be the same as the value of the corresponding parameter in another mode. Load power-off voltage threshold. If "Load Shutdown Flag" is set to "Enable" and the load voltage is lower than the value of this parameter, the load is automatically powered off. In multi-mode scenario, the value of this parameter in one mode must be the same as the value of the corresponding parameter in another mode. Whether "Shutdown Voltage" is valid. In multi-mode base station scenario, the value of this parameter in different modes must be the same for the same multi-mode base station. When the temperature of the BTS cabinet is greater than the value of this parameter, the TRX is powered off.
Board Parameter Configuration Enabled
Hierarchical Power-off Config. Enabled
Load Shutdown Voltage
Low Voltage Shutdown Flag Temp Of High Temp. Load Power Off
Issue 08 (2011-09-30)
1286
Parameter
Description High temperature threshold for triggering power shutdown of the battery. If the power shutdown upon battery high temperature is enabled and the battery temperature is higher than the value of this parameter, the battery is automatically powered off. In multi-mode scenario, the value of this parameter in one mode must be the same as the value of the corresponding parameter in another mode.
Shutdown Temperature
Issue 08 (2011-09-30)
1287
Table 2-240 Parameter description (2) Parameter Defau lt Value GUI Value Range Actual Value Range Unit MML Command SET BTSFMUABP (Mandatory) SET BTSUSCUBP (Mandatory) SET BTSDDPUBP (Mandatory) SET BTSPSUFP (Mandatory) SET BTSDTMUBP (Mandatory) SET BTSDPMUBP (Mandatory) SET BTSDOMUBP (Mandatory) SET BTSDHEUBP (Mandatory) SET BTSDEMUBP (Mandatory) SET BTSDATUBP (Mandatory) SET BTSAPMUBP (Mandatory) Board Parameter Configuratio n Enabled SET BTSPMUBP (Mandatory) NO(NO), YES(YES) SET BTSNFCBBP (Mandatory) Im pac t
None
NO, YES
None
BTS
Issue 08 (2011-09-30)
1288
Parameter
Defau lt Value
GUI Value Range
Actual Value Range
Unit
MML Command SET BTSAPMUBP (Optional)
Im pac t
Hierarchical Power-off Config. Enabled Load Shutdown Voltage Low Voltage Shutdown Flag Temp Of High Temp. Load Power Off
NO
NO(NO), YES(YES)
NO, YES 35.0~55.6 (step: 0.1)
None
SET BTSDPMUBP (Optional) SET BTSAPMUBP (Optional) SET BTSAPMUBP (Optional) SET BTSAPMUBP (Optional) SET BTSAPMUBP (Optional)
BTS
None
350~556 DISABLE (DISABLE), ENABLE (ENABLE)
BTS
ENAB LE
DISABLE, ENABLE
None degre e Celsi us degre e Celsi us
BTS
65
50~70
50~70
BTS
Shutdown Temperature
53
40~70
40~70
BTS
2.88.6 Counters
None.
2.88.7 Glossary

2.89 Call Control

2.89.1 Introduction
2.89.1.1 Scope
Call control provides the MS with radio resources and terrestrial circuits for making a call and helps the MSC during the whole call handling process. This document describes the call clarifications and the corresponding call procedures.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the Call Control feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.89.2 Overview of Call Control

Call control is a basic feature for an operator to provide the CS services. With call control, the BSS provides the MS with radio resources and terrestrial circuits for making a call and helps the MSC during the entire call handling process. BSS supports the mobile-originated call (MOC), mobile-terminated call (MTC), and emergency call. With specific resource management algorithms and control functions, the BSC provides transport channels for the transmission of call control signaling between the MS and MSC by setting up the radio resource (RR) connections.
During the call control process, the BSS supports priority-based handling. For example, the emergency call has a higher priority than a common call, and thus the emergency call can obtain the required resources preferentially than common calls. Concerning the BSC, call control involves mainly the allocation of radio channel resources, the allocation of A interface resources in cooperation with the MSC, and release of traffic channels. The basic call processes are as follows: l l l l l MOC MTC Emergency call MS-initiated call release Network-initiated call release

2.89.3.1 Call Classification MOT
With regard to assignment, MOT is classified into the following three types: l l l Early assignment Late assignment Very early assignment
The selection of early assignment and late assignment is determined by the MSC. The very early assignment is determined by the BSS, based on the usage of radio resources.
NOTE
For details about early assignment, late assignment, and very early assignment, see the Assignment and Immediate Assignment Feature Parameter Description.
MTC
MTC is a process through which the network assigns the traffic channel to a called MS. For detailed descriptions of MTC procedure, see 3GPP TS24.008, TS24.080, TS48.008, TS44.018, and TS48.058.
NOTE
The Paging message can be transmitted directly from the MSC to the BSC over the A interface or from the SGSN to the BSC over the Gb interface.Figure 2-344 shows the MTC procedure.
Issue 08 (2011-09-30)
1291
Figure 2-344 MTC procedure
Emergency Call
Emergency call is performed by users in emergency situations to contact the outside world. It is critical for users in emergency situations. For example: l An MS in an emergency can call a specific number for the maximum help free of charge. The emergency call is allowed even if the MS is out of service or the telephone charge is overdue. An MS in an emergency can have a higher level of access priority when dialing an emergency call. The MS can contact the emergency department even in a congested cell.
Issue 08 (2011-09-30)
1292
The emergency call procedure is similar to the MOC procedure, except that the EMERGENCY_CALL_SETUP message is used instead of the Setup message.
2.89.3.2 Call Release Overview

In terms of the network element (NE) that initiates the procedure, call release is classified into MS-originated call release and network-initiated call release.
MS-Initiated Call Release

The MS can initiate call release if necessary (for example, the user hangs up) after accessing the network normally. Figure 2-345 shows the procedure of MS-initiated call release.
Issue 08 (2011-09-30)
1293
Figure 2-345 Procedure of MS-initiated call release
The procedure of MS-initiated call release is describes as follows: 1. 2. After the call is completed and the calling party hangs up, the calling MS sends a Disconnect message to the MSC and starts timer T305. This message carries the cause of the release. On receiving the Disconnect message from the MS, the MSC responds with a Release message and starts timer T308. In addition, the MSC sends a Disconnect message to the called party. On receiving the Release message from the MSC, the MS stops timer T305, releases the MM connection, and then sends a Release Complete to the MSC.
3.
Issue 08 (2011-09-30)
4.
On receiving the Release Complete message from the MS, the MSC stops timer T308, releases the MM connection, and sends a Clear Command message to the BSC to instruct the BSC to release the occupied resources on the A and Um interfaces. The BSC sends a Channel Release message to the MS, instructing the MS and BTS to release the logical channel over the Um interface, and starts timer T3109. This message carries the RR cause. On receiving the Channel Release message, the MS disconnects the uplink signaling link. Then, the MS sends a DISC frame to the BTS to notify the BTS that the logical channel is released. The BTS sends a UA frame to the MS. On receiving the UA frame, the MS returns to the CCCH and enters the idle state. The BSC sends a Deactivate SACCH message to the BTS to instruct the BTS to deactivate the SACCH. On receiving the DISC frame, the BTS sends a Release Indication message to the BSC, indicating that the MS has released the logical channel over the Um interface. The BSC stops timer T3109 and starts timer T3111.
5.
6.
7. 8. 9.
10. After timer T3111 expires, the BSC sends an RF Channel Release message to the BTS to release the RF channel over the Um interface. The timer T3111 is used to reserve some time for connection disconnection confirmation. 11. The BTS sends an RF Channel Release Acknowledge message to the BSC, indicating that the RF channel over the Um interface is released and can be allocated to other calls. 12. The BSC sends a Clear Complete message to the MSC. 13. The MSC sends an RLSD message to the BSC to release the SCCP link. 14. The BSC sends an RLC message to the MSC, indicating that the SCCP link is released. The conclusion from the previous procedure is as follows: l l Step (1) through Step (3) are concerned with call connection release. Step (4) through Step (14) are concerned with radio resource release.
After the connections at the CC and MM layers are released successfully, the MSC sends a Clear Command message to the BSC to release the SCCP link. This message carries the cause of the call release, for example, "Handover Successful" or "Call Control". If the call release is caused by failure of A interface message transmission, radio link failure, or device failure, the BSC sends a Clear Request message to the MSC, and then the MSC sends a Clear Command message to the BSC.
Network-Initiated Call Release

The network initiates call release due to certain reasons, after the MS has accessed the network. The procedure of network-initiated call release is similar to Figure 2-345, except that the messages in Step (1) through Step (3) are transparently transmitted in reverse.
2.89.4 Parameters
This chapter describes the parameters related to the Call Control feature. For the meaning of each parameter, see Table 2-241. For the default value, value ranges, and MML commands of each parameter, see Table 2-242.
Table 2-241 Parameter description (1) Parameter Description This timer is used to set the time of waiting for a ReleaseIndication message after a ChannelRelease message is sent. If the timer expires, the channel is deactivated. Timer for delaying a connection release. This parameter is used for delaying the channel deactivation after the active signaling link is broken. The purpose is to reserve some time for the disconnection that may be repeated. After receiving a REL IND message sent by the BTS, the BSC6900 starts the timer. When the timer expires, the BSC6900 stops the timer and sends the BTS an RF CHAN REL message.
T3109
T3111
Table 2-242 Parameter description (2) Parameter Defau lt Value GUI Value Range Actual Value Range Unit MML Command SET GCELLTMR (Optional) SET GCELLTMR (Optional) Im pac t
T3109
27000
4000~33000
4000~33000
ms
Cell
T3111
1000
500~60000
500~60000
ms
Cell
2.89.5 Counters
2.89.6 Glossary

l l l l 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3" 3GPP TS 24.080: "Mobile radio Layer 3 supplementary service specification; Formats and coding" 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol" 3GPP TS 48.008: "Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification"
Issue 08 (2011-09-30)
l l l
3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC-BTS) Interface; Layer 3 specification" BSC6900 Feature List BSC6900 Basic Feature Description
2.90 Call Reestablishment

2.90.1 Introduction
2.90.1.1 Scope
This document describes the call reestablishment procedure, and MS mode of the call reestablishment.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Call Reestablishment feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.90.2 Overview of Call Reestablishment

When the MS encounters a radio link failure during the call, the call reestablishment procedure can be used to reestablish the radio link connection so that the original call can proceed. This mechanism shortens the call intermission, and thus improves the user experience.

2.90.3.1 Call Reestablishment Procedure
The parameter Call Reestablishment Forbidden specifies whether to enable call reestablishment. When the MS encounters a radio link failure during the call, the call reestablishment procedure can be used to reestablish the radio link connection so that the original call can proceed. Call reestablishment may occur in a new cell or a new location area. If a cell supports call reestablishment, the starting of a call reestablishment attempt depends on the calling status of the cell. After the call reestablishment is started, the MSC starts the encryption and assignment procedures. Then, the MSC checks whether the calling status and attaching status of the MS are correct. If the calling status and attaching status of the MS are correct, the call is reestablished. During the call reestablishment, the MS cannot return to the IDLE state. Thus, the MS cannot perform location update when its source cell and target cell for call reestablishment are in different location areas. After the ongoing call is complete, the MS can perform location update. The call reestablishment procedure is controlled by the MSC. The BSC sets up channels and forwards layer 3 messages. Figure 2-346 shows the call reestablishment procedure.
Issue 08 (2011-09-30)
1298
Figure 2-346 Call reestablishment procedure
1. 2. 3. 4.
Step 1 through step 4 in Figure 3-1 show the release of radio channel resources. The procedure of resource release in call reestablishment is the same as that in normal calls. Step 5 through step 9 in Figure 3-1 show the procedure of immediate assignment and seizure of signaling channels. Step 10 and step 11 in Figure 3-1 show the encryption procedure. Step 12 and step 11 in Figure 3-1 show the assignment procedure.
The call reestablishment procedure starts from step 5. The call reestablishment mechanism differs according to the NE that first detects radio link failures. l When the MS detects a radio link failure, the MS sends the Channel Request message with the cause value Call re-establishment in its selected cell (either the current cell or a new cell).When the timer at the BTS side expires, the previous channel resources are released by the BSC. The timer is specified by the parameter TREESTABLISH. If the parameter TREESTABLISH is set to a too great value, the radio resources for callHuawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1299
Issue 08 (2011-09-30)
reestablishment-enabled cells are retained for a long time. This results in network congestion in busy hours. l When the BTS detects a radio link failure, it sends the Connection Failure Indication message with the cause value Radio Link Failure to the BSC. On receiving the message, the BSC releases related radio resources and waits for the MS to initiate call reestablishment.
2.90.3.2 MS Mode
During the call reestablishment, the MS cannot return to the IDLE state. Thus, the MS cannot perform location update when its source cell and target cell for call reestablishment are in different location areas. After the ongoing call is complete, the MS can perform location update.
2.90.4 Parameters
This chapter describes the parameters related to the Call Reestablishment feature. For the meaning of each parameter, see Table 2-243. For the default value, value ranges, and MML commands of each parameter, see Table 2-244. Table 2-243 Parameter description (1) Parameter Description Whether to allow call re-establishment. Burst interference or blind spots due to high buildings may lead to a radio link failure. If a call drop is caused by such a failure, the MS can start call re-establishment to resume the conversation. Call reestablishment timer.
Call Reestablishment Forbidden TREESTABLISH
Table 2-244 Parameter description (2) Parameter Defau lt Value GUI Value Range Actual Value Range Unit MML Command Im pac t
Call Reestablish ment Forbidden TREESTAB LISH
YES
NO(No), YES(Yes)
NO, YES
None
SET GCELLBASICP ARA(Optional) SET GCELLTMR (Optional)
Cell
15000
5000~40000
5000~40000
ms
Cell
2.90.5 Counters
None.
2.90.6 Glossary

l l l l l l l l l 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3" 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol" 3GPP TS 48.008: "Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification" 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC-BTS) Interface; Layer 3 specification" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.91 Cell Frequency Scan

2.91.1 Introduction
2.91.1.1 Scope
This document describes the cell frequency scan feature. It covers the functions and algorithms regarding cell frequency scan.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows:
Feature change Feature change refers to the change in the Cell Frequency Scan feature of a specific product version.
Document Issues
01(2010-01-20)
2.91.2 Overview of Cell Frequency Scan

Cell frequency scan is a feature through which a specific frequency is scanned by using a certain channel to obtain the uplink signal levels on the frequency. Cell frequency scan provides references for engineers to select proper frequencies. The interference of each frequency is an important reference for network optimization. The BSC performance statistics function provides the statistics on the uplink interference, through which one can understand the interference of the wireless environment of the cell. Analyzing only the uplink interference statistics, however, has the following limitations: l l One can obtain the interference of only the configured frequencies. One cannot detect the interference sources.
Through cell frequency scan, all the frequencies on a frequency band can be scanned. You can also set the parameters of specified sites, cells, and frequencies to perform the specific measurements. Cell frequency scan enables maintenance engineers to test the interference in uplink without the help of any test devices. This helps maintenance engineers to understand the interference of uplink frequencies and helps network planning engineers to correctly configure frequencies. Cell frequency scan enables operators to assess the current electromagnetic environment without the help of any test devices. It serves as a reference for operators to perform network planning and network optimization. In this manner, cell frequency scan improves the maintenance efficiency and reduces the O&M costs.

Cell frequency scan is the procedure to obtain the current, minimum, maximum, and mean values of the main and diversity signal levels by periodically detecting the uplink receive levels of a specified frequency. The scan is performed on an idle frame of a TCH in the target cell. Generally, when a BSC assigns a TCH, the TCH on the TRX that carries the BCCH is preferentially used to perform the cell frequency scan. The main receive levels and diversity receive levels on the uplink are reported separately. The results of the uplink frequency scan of each frequency contain multiple measurement values.
When the parameter Frequency Scan Result Type is set to MainDiversity(MainDiversity), the results of the uplink frequency scan contain the current, minimum, maximum, and mean values of the main signal levels and diversity signal levels. When the parameter Frequency Scan Result Type is set to MaximumMeanValue(MaximumMeanValue), the results of the uplink frequency scan contain the maximum, and mean values of the uplink receive level In practical applications, scanning 50 frequencies takes about one minute. In a cell frequency scan task, there are a maximum of 124 frequencies to be scanned. Therefore, scanning all the frequencies takes about three minutes. As the uplink frequency scan is performed on an idle frame, the uplink receive levels of synchronous cells cannot be obtained in practical scenarios. The parameter Interfere Band Stat Algorithm Type determines the interference band statistics algorithm used when the frequency scanning function is enabled To accurately measure and determine interference bands, one can refer to the BSC counters in BTS Management Measurement and Channel Measurement of Measurement of GSM Cell Performance in the BSC6900 GSM Performance Counter Reference.

The limitations of cell frequency scan are as follows: l l l Cell frequency scan requires an idle TCH. Cell frequency scan cannot be performed when an RF hopping loopback test is being performed. Cell frequency scan cannot be performed when an empty frame test is being performed.
2.91.5 Parameters
This chapter describes the parameters related to the Cell Frequency Scan feature. For the meaning of each parameter, see Table 2-245. For the default value, value ranges, and MML commands of each parameter, see Table 2-246. Table 2-245 Parameter description (1) Parameter Description Type of a scanning result in the period from the start of a frequency scanning task to the reporting of the scanning result. Frequency scanning refers to the scanning of an uplink receive level of a cell frequency. The scanning result reflects the strength of frequency signals received by the cell. Type of an interference band statistics algorithm used when the frequency scanning function is enabled. The interference band statistics algorithm I uses pair average, and the interference band statistics algorithm II uses linear average.
Frequency Scan Result Type
Interfere Band Stat Algorithm Type
Issue 08 (2011-09-30)
1303
Table 2-246 Parameter description (2) Parameter Defau lt Value GUI Value Range MainDiversit y (MainDiversi ty), MaximumMe anValue (MaximumM eanValue) INTBANI (INTBANI), INTBANII (INTBANII) Actual Value Range Unit MML Command Im pac t
Frequency Scan Result Type Interfere Band Stat Algorithm Type
Maxim umMe anValu e
MainDiversit y, MaximumMe anValue
None
SET GCELLSOFT (Optional) SET GCELLSOFT (Optional)
Cell
INTB ANII
INTBANI, INTBANII
None
Cell
2.91.6 Counters
2.91.7 Glossary

l l l l BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM Performance Counter Reference BSC6900 GSM LMT User Guide
2.92 Cell Tracing

2.92.1 Introduction
2.92.1.1 Scope
This document describes the functions and relevant technical mechanism of the Cell Tracing feature of Huawei GBSS.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the Cell Tracing feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.92.2 Overview of Cell Tracing

With the Cell Tracing feature, the signaling of a maximum of 16 users over the A interface, Abis interface, or Um interface of a specified cell can be traced at a time. The BSC determines whether to perform signaling tracing according to the configured cell number and the number of users. The Cell Tracing feature follows the first-in first-tracing principle.

When handling the voice-related problems, especially the problems related to the signaling procedure and performance, you need to analyze the signaling over the A interface, Abis interface, or Um interface. The common method is drive test (DT) or dialing test. Together with the traced data obtained by the signaling tracer, the signaling can be analyzed. This process, however, is very complex and expensive. The cell tracing log facilitates the location of the network problem. You can directly trace calls in the existing network, thus saving the cost of the DT and dialing test for locating the problem. Compared with the A interface tracing, Abis interface tracing, or Um tracing function, the cell tracing function enables the simultaneous tracing of the signaling over the A interface, Abis
interface, and Um interface in a window. Compared with the single user tracing function, the cell tracing function can directly trace the signaling of a maximum of 16 users in a cell without specifying the user ID. The cell tracing procedure is as follows: 1. 2. Start the Cell Tracing function on the M2000. The BSC traces the calls of the specified cell. A maximum of 16 users in the cell can be traced at a time. The Cell Tracing feature follows the first-in first-tracing principle. After a tracing task is started, the first 16 calls that gain access to the network in the cell to be traced are traced. If a call is complete, a new call is traced.
NOTE
You can choose the cells to be traced on the basis of the CELLID. The GBSC supports the saving and reviewing of the traced logs. You can also choose to trace only the signaling on the A interface, Abis interface, or the Um interface.

The limitations of Cell Tracing are as follows: l l l A maximum of 16 users can be traced at a time on the M2000. The signaling over the A interface, Abis interface, or Um interface can be traced. The start time and end time of the function can be set.
2.92.5 Parameters
None.
2.92.6 Counters
None.
2.92.7 Glossary

2.93 Man Machine Language (MML)

2.93.1 Introduction
2.93.1.1 Scope
This document describes the Man Machine Language (MML). It provides an overview of the main functions and goes into details regarding MML control.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Man Machine Language (MML) feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.93.2 Overview of Man Machine Language

MML commands are used for NE operation and maintenance. The BSS supports NE operation and maintenance by running MML commands on the M2000 or LMT. In daily operation and maintenance, MML is more effective than GUI. You can configure and maintain multiple NEs by running MML scripts or performing multiple operations on one NE. MML improves maintenance efficiency, reduces the possibility of improper manual operations, and greatly reduces O&M costs of operators.

l The MML command supports the following operation modes: Entering MML commands and parameters directly.
Entering MML commands and parameters through the GUI. Providing the MML batch processing function. Many MML commands are written in a file. The LMT reads the MML commands in the file and executes these commands automatically. Recording the MML commands and saving the results of the execution of the MML commands automatically. Recording operations in the operation logs. l The MML command supports the following operations: Configuring data, including the devices, transmission, and BTS data using MML commands. Supporting configuration management. That is, you can allocate user rights for configuration using MML commands. Performing alarm maintenance functions such as browsing, querying, and manually clearing alarms, configuring environment alarms, and shielding alarms using MML commands. Maintaining BSC devices, transmission devices, signaling links, and interfaces. That is, by using the MML commands, you can maintain the BSC and transmission devices, such as status query and board switchover. Maintaining BTS boards and TRXs. Supporting log management. You can collect and query logs such as operation logs, host logs, and OMU logs. Performing security management functions such as adding, deleting, and modifying user information, managing user rights, and querying operation logs. Performing software management functions such as upgrading the BSC software, BTS software, patches, and maintaining the BIOS and license. Supporting time management through MML commands, such as setting time zone, specifying DST, and adding or deleting time synchronization server.

The BSS supports NE operation and maintenance by running MML commands on the M2000 or LMT. If you run MML commands on the M2000, you need to install the M2000 client and connect it to the server. If you run MML commands on the LMT, you need to enter the IP address of the LMT on the browser and then to log in to the LMT.
2.93.5 Parameters
None.
2.93.6 Counters
None.
2.93.7 Glossary

l l l BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM MML Reference
2.94 Operation & Maintenance System One-Key Recovery

2.94.1 Introduction
2.94.1.1 Scope
This document describes the Operation & Maintenance System One-Key Recovery feature of Huawei GSM BSS. It provides an overview of the functions and mechanisms regarding the Operation & Maintenance System One-Key Recovery feature.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Operation & Maintenance System One-Key Recovery feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
Issue 08 (2011-09-30)
01(2010-01-20)
01(2010-01-20)
2.94.2 Overview of Operation & Maintenance System One-Key Recovery

The software that runs on the OMU board includes the Dopra Linux operating system and the OMU applications. When the Dopra Linux operating system on the OMU board is corrupted, the OMU applications are corrupted, or the operating system on the OMU board is switched from non-Dopra Linux to Dopra Linux, on-site engineers need to manually recover the operating system, the OMU applications, or perform the operating system switchover. Such manual operations entail very complicated steps. In addition, such manual operations may even disrupt the ongoing services of the BSC. The Operation & Maintenance System One-Key Recovery feature is introduced to solve this problem. This feature reduces the complexity of the backup and recovery of the operating system and of the configuration data of the OMU board. In addition, it minimizes the duration of service disruption caused by the operation & maintenance operations.

This chapter describes how to implement the Operation & Maintenance System One-Key Recovery feature. The USB creator (U_creator_eng.exe tool) is used to create the USB disk for installing the Dopra Linux operating system and the OMU applications. The USB installation disk is plugged into the USB port on the OMU board. The OMU board is then reset. Five to ten minutes later, the operating system or OMU applications on the OMU board are recovered. Note that the operating system, OMU applications, and the respective configuration information must be stored onto the USB installation disk during the creation of the USB installation disk. Then, Bootstrap scripts are generated on the USB installation disk to facilitate the start-up of the OMU board through the USB installation disk. The Bootstrap scripts first install the Dopra Linux operating system and configure the information for the operating system. Then, the Bootstrap scripts install the OMU applications and configure the information for the OMU applications. Figure 2-347 shows the OMU board software recovery process.
Issue 08 (2011-09-30)
1310
Figure 2-347 OMU board software recovery process
When the operating system on the existing OMU boards is switched from non-Dopra Linux to Dopra Linux, the USB creator is used to obtain the configuration information, especially the network configuration information, the OMU applications configuration information, and the network element (NE) confirmation information, of the OMU board whose operating system is to be switched. Based on the information obtained, the USB creator creates a USB installation disk for installing the Dopra Linux operating system. Then, the USB installation disk is plugged into the USB port on the OMU board. The OMU board is then reset. Five to ten minutes later, the switchover of the operating system is complete.
Issue 08 (2011-09-30)
1311
2.94.4 Parameters
None.
2.94.5 Counters
None.
2.94.6 Glossary

l l l BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM OMU Administration Guide
2.95 Radio Bearer Services

2.95.1 Introduction
2.95.1.1 Scope
This document describes the functions and principles of Huawei Global System for Mobile communications (GSM) Base Station Subsystem (BSS) radio bearer services, which includes telephone service (TS11), emergency call service (TS12), point to point short message service (TS21, TS22), G3 fax (TS61, TS62), and bearer service (CSD).


Feature change Feature change refers to the change in the Radio Bearer Services feature of a specific product version.
Document Issues
01(2010-01-20)
2.95.2 Overview of Radio Bearer Services

GSM is a multi-service system, which provides multiple types of communication services for subscribers based on their requirements. Generally, GSM services are classified into speech services and data services. Speech services transmit voices, and data services transmit data information such as pictures, faxes, and files. In addition to these traditional services, GSM also provides new services such as the short message service. Huawei GSM BSS provides mainly the following basic radio services: l l l l l Telephone Service (TS11) Emergency Call Service (TS12) Point To Point Short Message Service (TS21, TS22) G3 Fax (TS61, TS62) Bearer Service (CSD)
NOTE
The GSM radio services described in this document do not cover supplementary services and intelligent network services.

2.95.3.1 Telephone Service (TS11) Overview
Telephone service is a basic speech service specified in GSM specifications. It is also one of the basic speech service functions provided by operators. The excellent speech service provided by Huawei BSS provides the following benefits: l l Better user experience Improved brand image, sustainable growth of operation gains, and everlasting competitive strength
Issue 08 (2011-09-30)
Telephone Service
Telephone service (TS11) is a basic function of the GSM equipment. It is also a basic service provided by Huawei GSM BSS. The telephone service is classified into mobile-originated calls (MOC) and mobile-terminated calls (MTC).The speech calls can be made not only between MSs within a GSM Public Land Mobile Network (PLMN), but also between a PLMN MS and a subscriber of Public Switched Telephone Network (PSTN) or other communication networks. In the BSS, the transcoder & rate adaptation unit (TRAU) is responsible for the speech conversion between the GSM speech coding and the 64 kbit/s pulse code modulation (PCM) coding. If the speech coding schemes specified in optional features are not activated for a common call, the full rate speech coding is adopted by default. The coding scheme is selected according to the value of Speech Version before setting up a voice call.
2.95.3.2 Emergency Call Service (TS12) Overview

Huawei GSM BSS supports the emergency call service (TS12) specified in GSM specifications and provides higher priority for the emergency call service. The emergency call service is of great importance to subscribers in emergencies. As defined in 3GPP, the emergency call services are statutory and mandatory in most networks. An emergency call takes precedence over a common call. A priority mechanism is implemented to provide fast and reliable access of emergency calls even when the network is in heavy load. l l During an emergency, the subscriber can dial the specified emergency service number free of charge for assistance even if the MS is out of service or the telephone charge is overdue. The emergency call service takes precedence over other services in accessing the network. Even located in congested cells, the subscriber can contact the aid agencies by dialing the emergency service number.
Emergency Call
The Emergent Call Disable parameter specifies whether to enable the emergency call service. The emergency call takes precedence over common calls. Compared with common calls, the procedure of the emergency call is simplified to accelerate the call establishment and to ensure a higher call establishment success rate. For example, during the immediate assignment procedure, a TCH/F can be assigned directly so that an emergency call can be quickly and easily allocated with radio resources. Different from the procedure of the common MOC, the Emergency Setup message is used in the emergency call to substitute the Setup message.
Guaranteed Emergency Call

In some special situations such as in an earthquake, tsunami, or flood, the network may be congested. Therefore, the emergency call services may not be guaranteed owning to insufficient resources.
The emergency call guarantee feature is the enhancement of the emergency call feature. With the emergency call guarantee feature, the setup success rate of emergency calls is improved to the greatest extent. Thus, provision of communications is ensured in disaster relief activities. The following mechanisms are implemented to provide the emergency call guarantee feature: l l Preferentially assigning TCH/F to emergency calls in the immediate assignment phase Resource Reservation and Preemption
For details, see the Guaranteed Emergency Call.
2.95.3.3 Point To Point Short Message Service (TS21, TS22) Overview

The point-to-point short message service is more and more widely used in daily life and work. As a value-added service, the short message service complements the non-diversified mobile speech services of the GSM. This feature provides the following benefits: l l l The point-to-point short message service meets the subscribers' increasingly diversified data service requirements. The point-to-point short message service has become an increasingly important source of operators' revenue and makes the operators' profit more diversified. The point-to-point short message service can be provided as the service provider (SP) service to enrich the operating of the operators.
NOTE
The short message here refers to the one that is transmitted through SS7 signaling. The short message service implemented in the PS domain is not included. The PS short message is a function mainly implemented by the serving GPRS support node (SGSN). The PS short message is treated as a common data service on the BSC side.
Point To Point Short Message Service

Mobile-terminated (MT) point-to-point short message service (TS11) and mobile-originated (MO) point-to-point short message service (TS12) specified in GSM specifications are basic functions of the GSM equipment. They are also basic services provided by Huawei GSM BSS. The point-to-point short message service can be used to exchange information in plain text. With this service, the subscribers can exchange simple information with each other and the operators can send service promotion information and sale information. Both the short message service center (SMC) and the MS can initiate the point-to-point short message service. The BSS supports the sending and receiving of the short messages. On receiving the signaling of a short message from the MSC, the BSS forwards the short message to the MS. In turn, on receiving a short message from the MS, the BSS forwards the short message to the MSC. The Short Message Downlink Disabled parameter specifies whether the DL short messages to a specific cell can be sent. This ensures that adequate radio resources are reserved for normal calls. The Short Message Uplink Disabled parameter specifies whether the UL short messages from a specific cell can be sent. This ensures that adequate radio resources are reserved for normal calls.
2.95.3.4 G3 Fax (TS61, TS62) Overview

The G3 fax feature is a value-added mobile data service that allows MSs to send and receive the voice fax. The G3 fax feature complements the non-diversified mobile speech services of the GSM. This feature provides the following benefits: l l This feature enables the MS to receive and send fax any time any where and meets the diversified requirements of the subscribers. This feature enables operators to provide mobile fax service to extend the service range and the source of revenue.
G3 Fax
TS61 refers to the G3 alternate voice and fax services and TS62 refers to the G3 automatic voice and fax services. TS61 and TS62 services specified in GSM specifications are basic functions of the GSM equipment. They are also basic services provided by Huawei GSM BSS. With the TS61 and TS62 services, the MS can send and receive the voice fax in the format of switching coding information files. The fax service is realized through other upper-layer protocols. Therefore, the BSS provides the lower-layer connection but does not process the upper-layer services. The main device required by this feature is deployed in the MSC. The Data Service Allowed parameter specifies the supported data service. Set this parameter according to actual requirements.
2.95.3.5 Bearer Service (CSD) Overview

GSM supports the traditional circuit switched data (CSD) services and the data services of multiple rates. Data services are more and more widely used in daily life and work. As a value-added mobile data service, the CSD service complements the non-diversified mobile speech services of the GSM. With the CSD service, the MS can connect to the operators' data network or even to the Internet. This feature provides the following benefits: l l l l The CSD service meets the subscribers' increasingly diversified data service requirements. The CSD service also enables the subscribers to connect to external networks. The CSD service has become an increasingly important source of operators' revenue and makes the operators' profit more diversified. Operators can provide diversified services on the data platform of CSD to attract more subscribers, thereby reaping more profit. Unlike general packet radio service system (GPRS), CSD does not require the change of the existing BSS hardware. Instead, CSD can be implemented directly in the existing system without adding the packet control unit (PCU) device or hardware and software. This reduces the space required by the equipment room and facilitates the management of the equipment room. Moreover, the CSD increases the choices of data services.
Issue 08 (2011-09-30)
Service Description
Huawei GSM BSS supports various bearer services specified in GSM specifications. The GSM BSS provides the lower-layer connection but does not process the upper-layer services. The bearer service can be used in low-rate data service applications. Huawei GSM BSS supports the following bearer services: l l l l l l l l l l l l l l l l l l l l l BS21 asynchronous duplex circuit data service, transparent/non-transparent, 300 bit/s BS22 asynchronous duplex circuit data service, transparent/non-transparent, 1200 bit/s BS23 asynchronous duplex circuit data service, transparent/non-transparent, 1200/75 bit/ s BS24 asynchronous duplex circuit data service, transparent/non-transparent, 2400 bit/s BS25 asynchronous duplex circuit data service, transparent/non-transparent, 4800 bit/s BS26 asynchronous duplex circuit data service, transparent/non-transparent, 9600 bit/s BS31 synchronous duplex circuit data service, transparent/non-transparent, 1200 bit/s BS32 synchronous duplex circuit data service, transparent/non-transparent, 2400 bit/s BS33 synchronous duplex circuit data service, transparent/non-transparent, 4800 bit/s BS34 synchronous duplex circuit data service, transparent/non-transparent, 9600 bit/s BS41 PAD access service, asynchronous circuit, transparent/non-transparent, 300 bit/s BS42 PAD access service, asynchronous circuit, transparent/non-transparent, 1200 bit/s BS43 PAD access service, asynchronous circuit, transparent/non-transparent, 1200/75 bit/ s BS44 PAD access service, asynchronous circuit, transparent/non-transparent, 2400 bit/s BS45 PAD access service, asynchronous circuit, transparent/non-transparent, 4800 bit/s BS46 PAD access service, asynchronous circuit, transparent/non-transparent, 9600 bit/s BS51 packet access service, 2.4 kbit/s, synchronous, UDI, non-transparent BS52 packet access service, 4.8 kbit/s, synchronous, UDI, non-transparent BS53 packet access service, 9.6 kbit/s, synchronous, UDI, non-transparent BS61 alternate speech/data service, transparent/non-transparent BS81 speech followed by data service
NOTE
Bearer services BS23 and BS43 are applicable to the MOC only. In BS23 and BS43 services, the data rate of 75 bit/s is applicable to the uplink and the data rate of 1200 bit/s is applicable to the downlink.
2.95.4 Parameters
This chapter describes the parameters related to the Radio Bearer Services feature. For the meaning of each parameter, see Table 2-247. For the default value, value ranges, and MML commands of each parameter, see Table 2-248. Table 2-247 Parameter description (1) Parameter Data Service Allowed Description Data service supported by the BSC6900. You can set this parameter according to actual requirements.
1317
Issue 08 (2011-09-30)
Parameter Emergent Call Disable
Description Whether to disable emergency calls. For the MSs of access levels 0 to 9, if the value of this parameter is NO, emergency calls are enabled. For the MSs of access levels 11 to 15, emergency calls are disabled only when the relevant access control bit is set to 0 and this parameter is set to YES. Whether to prohibit sending point-to-point short messages. If necessary, this parameter is used for controlling whether to send downlink short messages from a specific cell so as to ensure sufficient radio channel resources for normal calls. This parameter specifies whether the transmission of point-topoint short messages is disabled. If necessary, the transmission of the uplink short messages in a specific cell can be disabled so that sufficient radio channels can be seized by normal calls.
Short Message Downlink Disabled
Short Message Uplink Disabled
Table 2-248 Parameter description (2) Paramet er Data Service Allowed Default Value NT14_5K -0&NT12 K-1&NT6 K-1&T14 _4K-0&T 9_6K-1& T4_8K-1 &T2_4K1&T1_2K -0&T600 _BITS-0 &T1200_ 75-0 NO GUI Value Range NT14_5K~0 NT12K~1 NT6K~2 T14_4K~3 T9_6K~4 T4_8K~5 T2_4K~6 T1_2K~7 T600_BITS~8 T1200_75 Actual Value Range NT14_5K, NT12K, NT6K, T14_4K, T9_6K, T4_8K, T2_4K, T1_2K, T600_BIT S, T1200_75 MML Command SET GCELLOTHE XT(Optional) Impac t Cell
Unit None
Emergen t Call Disable Short Message Downlin k Disabled Short Message Uplink Disabled
NO(No), YES (Yes) NO(No), YES (Yes)
NO, YES
None
SET GCELLCCBA SIC(Optional) SET GCELLCCAD (Optional)
Cell
NO
NO, YES
None
Cell
NO
NO(No), YES (Yes)
NO, YES
None
SET GCELLCCAD (Optional)
Cell
Issue 08 (2011-09-30)
1318
2.95.5 Counters
2.95.6 Glossary

l l l l l l l 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3" 3GPP TS 24.080: "Mobile radio Layer 3 supplementary service specification; Formats and coding" 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol" 3GPP TS 48.008: "Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification" 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC-BTS) Interface; Layer 3 specification" BSC6900 Feature List BSC6900 Basic Feature Description
2.96 Radio Link Management

2.96.1 Introduction
2.96.1.1 Scope
This document describes radio link management.


The change history provides information on the changes between different document versions.
There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Radio Link Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-12)
2.96.2 Overview of Radio Link Management

Radio link management involves nine procedures: link establishment indication, link establishment request, link release indication, link release request, transmission of a transparent L3-message in acknowledged mode, reception of a transparent L3-message in acknowledged mode, transmission of a transparent L3-message in unacknowledged mode, reception of a transparent L3-message in unacknowledged mode, and link error indication.

This chapter describes the nine procedures involved in radio link management.
2.96.3.1 Link Establishment Indication

This procedure is used by the BTS to indicate to the BSC that a layer 2 link on the radio path has been established in multi-frame mode at the initiative of an MS. The BSC can use this indication to set up an SCCP connection to the MSC. Upon reception of a SABM frame on a link on an active channel, the BTS sends an ESTablish INDication message to the BSC. The message contains the contents of the information field of the SABM frame if present. The procedure is used in all establishment cases, for all channels and all SAPIs.
2.96.3.2 Link Establishment Request

This procedure is used by the BSC to request the establishment of a link layer connection in multi-frame mode on the radio path.
The procedure is started by the BSC sending an ESTablish REQuest message to the BTS. The BTS then establishes the link by sending an SABM frame. Upon reception of the acknowledgement (UA-frame) from the MS, the BTS sends an ESTablish CONFirm message to the BSC. In case of a failure, the BTS sends a RELease INDication and an ERRor INDication message to the BSC (see GSM 04.06).
2.96.3.3 Link Release Indication

This procedure is used by the BTS to indicate to the BSC that a link layer connection on the radio path has been released at the initiative of an MS. When receiving a DISC frame on a link layer connection in multi-frame mode, the BTS sends a RELease INDication message to the BSC. If the link layer is in idle mode, the BTS will send a DM frame to the MS but does not notify the BSC.
2.96.3.4 Link Release Request

This procedure is used by the BSC to request the release of a link layer connection on the radio path. The procedure is started by the BSC sending a RELease REQuest message to the BTS. The BTS then sends a DISC frame to the MS. When it has received the acknowledgement (UA or DM frame), the BTS sends a RELease CONFirm message to the BSC. If the BTS has repeated the DISC frame N200 times, the BTS sends a RELease INDication and an ERRor INDication message to the BSC (see GSM 04.06).
2.96.3.5 Transmission of a Transparent L3-Message in Acknowledged Mode

This procedure is used by the BSC to request the sending of an L3 message to the MS in acknowledged mode.
The BSC sends a DATA REQuest message to the BTS. The message contains the complete L3 message to be sent in acknowledged mode.
2.96.3.6 Reception of a Transparent L3-Message in Acknowledged Mode

This procedure is used by the BTS to indicate the reception of an L3 message in acknowledged mode. The BTS sends a DATA INDication message to the BSC. The message contains the received L3 message.
2.96.3.7 Transmission of a Transparent L3-Message in Unacknowledged Mode

This procedure is used by the BSC to request the sending of an L3 message to the MS in unacknowledged mode. The BSC sends a UNIT DATA REQuest message to the BTS. The message contains the L3 message to be sent to the MS in unacknowledged mode.
2.96.3.8 Reception of a Transparent L3-Message in Unacknowledged Mode

This procedure is used by the BTS to indicate the reception of an L3 message in unacknowledged mode. The BTS sends a UNIT DATA INDication message to the BSC. The message contains the received L3 message.
2.96.3.9 Link Error Indication

This procedure is used by the BTS to indicate an abnormal case such as the following.
l l l l
A protocol error as specified in GSM 04.06, subclauses 5.6.4, 5.7.3 and annex G; A link layer failure, that is, the repetition of an I-frame N200 times without an acknowledgement; Repetition of an SABM or DISC frame N200 times without an acknowledgement; Reception of an SABM frame in multi-frame established state.
When such an event has occurred, the BTS notifies the BSC by sending an ERROR INDication message containing the relevant cause information.
The principle of ERROR INDICATION is as follows: 1. The N(R) in the I or S frame received by LAPDm must meet the following requirement: V(A)=<N(R)=<V(S).the frame sequence is considered erroneous. In this case, an error indication message is reported, with the cause value "sequence error (0x07)." If the DM frame received by the BTS is not the expected one, the BTS reports an error indication message, with the cause value "unsolicited DM response (0x04)." If the BTS does not receive a response message from the MS after transmitting the I frame for several times (specified by the parameter N200), the BTS reports an error indication message, with the cause value "RLM Cause: 1 timer T200 expired (N200+1) times (0x01)." Take the full-rate TCH as an example, the default time is T200 x (N200 + 1) = 5 x 50 x (34 + 1) = 8,750 ms.
2. 3.
The parameters T200 and N200 can be set on the LMT. Based on the function and state of links, different parameters need to be configured. The involved parameters are T200 SDCCH, T200 FACCH/F, T200 FACCH/H, T200 SACCH TCH SAPI0, T200 SACCH TCH SAPI3, T200 SACCH SDCCH, T200 SDCCH SAPI3, Use LAPDm N200, N200 of Establish, N200 of Release, N200 of SACCH, N200 of SDCCH, N200 of FACCH/Half rate, and N200 of FACCH/Full Rate.

This chapter provides engineering guidelines regarding the configuration of Radio Link Management. If T200 is set to a very small value, timer T200 expires before an acknowledgement message is received from the peer end. In this case, the link is considered faulty, and thus data transmission fails. If N200 is set to a very small value, the number of retransmissions is reduced. As a result, the transmission success rate is reduced. If T200 and N200 are set to very great values, channels are occupied when links are faulty. In this case, resources are wasted. Default values are set for these parameters on the Huawei BSC LMT. Therefore, manual configuration is not required generally.
2.96.5 Parameters
This chapter describes the parameters related to the Radio Link Management feature. For the meaning of each parameter, see Table 2-249. For the default value, value ranges, and MML commands of each parameter, see Table 2-250.
Table 2-249 Parameter description (1) Parameter T200 SDCCH Description This parameter specifies the timeout value of timer T200 used for the SDCCH over the Um interface. T200 prevents the data link layer from deadlock during data transmission. The data link layer transforms the physical link that is vulnerable to errors into a sequential non-error data link. The entities at the two ends of this data link use the acknowledgement retransmission mechanism. Each message must be confirmed by the peer end. In unknown cases, both ends are waiting if a message is lost. At this time, the deadlock of the system occurs. Therefore, the transmit end must establish a timer. When the timer expires, the transmit end regards that the receive end does not receive the message and then the transmit end retransmits the message. The number of retransmissions is determined by N200. T200 and the N200 ensure that the data link layer sequentially transmits data and that the transmission is free from errors. This parameter specifies the expiry value of timer T200 used for the FACCH/TCHF over the Um interface. For the function of timer T200 and the effect of the parameter, see the description of "T200 SDCCH". This parameter specifies the expiry value of timer T200 used for the FACCH/TCHH over the Um interface. For the function of timer T200 and the effect of the parameter, see the description of "T200 SDCCH". This parameter specifies the expiry value of timer T200 used for the SACCH over the Um interface when the TCH supports SAPI0 services. For the function of timer T200 and the effect of the parameter, see the description of "T200 SDCCH". This parameter specifies the expiry value of timer T200 used for the SACCH over the Um interface when the TCH supports SAPI3 services. For the function of timer T200 and the effect of the parameter, see the description of "T200 SDCCH". This parameter specifies the expiry value of timer T200 used for the SACCH on the SDCCH. For the function of timer T200 and the effect of the parameter, see the description of "T200 SDCCH". This parameter specifies the expiry value of timer T200 when the SDCCH supports SAPI3 services. For the function of timer T200 and the effect of the parameter, see the description of "T200 SDCCH". Whether the BSC6900 sends the LAPDm N200 parameter to the BTS. If this parameter is set to YES, the BSC sends the LAPDm N200 parameter. If this parameter is set to NO, the BSC6900 does not send the LAPDm N200 parameter.
T200 FACCH/F
T200 FACCH/H
T200 SACCH TCH SAPI0
T200 SACCH SDCCH
T200 SDCCH SAPI3
Use LAPDm N200
Issue 08 (2011-09-30)
1324
Parameter N200 of Establish
Description Error control is performed on the I frame sent over the LAPDm layer between the BTS and MS. If the MS detects errors in an I frame, the BTS should resend the I frame. This parameter indicates the maximum number of retransmissions of the I frame. For the function of N200 and the effect of the parameter, see the description of "T200 SDCCH". Error control is performed on the I frame sent over the LAPDm layer between the BTS and MS. If the MS detects errors in an I frame, the BTS should resend the I frame. This parameter indicates the maximum number of retransmissions of the I frame during the multi-frame release. For the function of N200 and the effect of the parameter, see the description of "T200 SDCCH". Error control is performed on the I frame sent over the LAPDm layer between the BTS and MS. If the MS detects errors in an I frame, the BTS should resend the I frame. This parameter indicates the maximum number of retransmissions of the I frame on the SACCH. For the function of N200 and the effect of the parameter, see the description of "T200 SDCCH". Error control is performed on the I frame sent over the LAPDm layer between the BTS and MS. If the MS detects errors in an I frame, the BTS should resend the I frame. This parameter indicates the maximum number of retransmissions of the I frame on the SDCCH. For the function of N200 and the effect of the parameter, see the description of "T200 SDCCH". Error control is performed on the I frame sent over the LAPDm layer between the BTS and MS. If the MS detects errors in an I frame, the BTS should resend the I frame. This parameter indicates the maximum number of retransmissions of the I frame on the FACCH (a half-rate channel). For the function of N200 and the effect of the parameter, see the description of "T200 SDCCH". Error control is performed on the I frame sent over the LAPDm layer between the BTS and MS. If the MS detects errors in an I frame, the BTS should resend the I frame. This parameter indicates the maximum number of retransmissions of the I frame on the FACCH (a full-rate channel). For the function of N200 and the effect of the parameter, see the description of "T200 SDCCH".
N200 of Release
N200 of SACCH
N200 of SDCCH
N200 of FACCH/Half Rate
N200 of FACCH/Full Rate
Issue 08 (2011-09-30)
1325
Table 2-250 Parameter description (2) Parameter ID T200 SDCCH Defau lt Value 60 GUI Value Range 1~255 Actual Value Range 5~1275, step: 5 Un it ms MML Command SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional)
Impact Cell
T200 FACCH/F
50
1~255
5~1275, step: 5
ms
Cell
T200 FACCH/H
50
1~255
5~1275, step: 5
ms
Cell
150
1~255
10~2550, step: 10
ms
Cell
200
1~255
10~2550, step: 10
ms
Cell
T200 SACCH SDCCH
60
1~255
10~2550, step: 10
ms
Cell
T200 SDCCH SAPI3
60
1~255
5~1275, step: 5
ms
Cell
Use LAPDm N200
OFF
OFF(Off), ON(On)
OFF, ON
No ne
Cell
N200 of Establish
5~254
5~254
No ne
Cell
N200 of Release
5~254
5~254
No ne
Cell
Issue 08 (2011-09-30)
1326
Parameter ID N200 of SACCH
Defau lt Value 5
GUI Value Range 5~254
Actual Value Range 5~254
Un it No ne
MML Command SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional) SET GCELLCC TMR (Optional)
Impact Cell
N200 of SDCCH
23
23~254
23~254
No ne
Cell
N200 of FACCH/Half Rate N200 of FACCH/Full Rate
29
29~254
29~254
No ne
Cell
34
34~254
34~254
No ne
Cell
2.96.6 Counters
2.96.7 Glossary

l l l l l l l 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BCS-BTS) Interface Layer 3 Specification" 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link (DL) layer specification" BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference BSC6900 GSM Performance Counter Reference
2.97 Remote EAC Maintenance

2.97.1 Introduction
2.97.1.1 Scope
This document describes the function and the technical principles of the remote Environment Alarm Chest (EAC) maintenance feature.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Remote EAC Maintenance feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.97.2 Overview of Remote EAC Maintenance

With the increasingly fierce competition in the radio communications market and changes in the requirement on environment and power supply monitoring, operators needs to ensure the physical security of equipment rooms. The EAC board is an effective solution to this problem by monitoring the environment and power supply in equipment rooms. The Environment Monitor Unit (EMU) board, as an enhanced EAC board, is applicable to the GSM, CDMA, and WCDMA indoor BTS. It monitors the environment (through temperature, humidity, water, and smoke sensors), illegal intrusion (through infrared and door status sensors), and power supply.
You can query the value of the sensors through the TMU board, or you can set reporting thresholds for the sensors, that is, when the value of a sensor exceeds the preset threshold, the EMU reports an alarm.

The monitoring system implemented by the EMU board has the following advantages: l l l l Provides the voltage detection for a single power input. The voltage alarm threshold can be set by the TMU. Provides the temperature, humidity, smoke, water, illegal intrusion, and power supply detection. Provides reverse connection protection for power cable connectors. Provides dual-input power port. If the 24D12 power module is used, the 24 V power system (power range: 18 V to 36 V) is supported. If the 48D12 power module is used, the -48 V power system (power range: -36 V to -72 V) is supported. l l l l l l Provides the port for the 12V DC/24V DC current type (4 mA to 20 mA) temperature and humidity sensors. Provides four routes of analog input sensors. The sensor can be of either voltage type (0 V to 5 V) or current type (4 mA to 20 mA). The sensor type can be set through DIP switches. Provides ports for 32 routes (S1+/S1- to S32+/S32-) of Boolean value inputs. The dry contact mode and the OC mode Boolean value input are supported. Provides six output control ports for external Boolean signals of the relay node type. Provides two RS485 ports for the communication with the TMU. Provides two LEDs on the front panel: RUN and ALM. Table 2-251 describes the LEDs on the EMU front panel. Table 2-251 LEDs on the EMU front panel Board Status Unregistered Normal Detectable faults exist MCU collapsed RUN (Green) Blinks at 4 Hz Blinks at 0.5 Hz Blinks at 0.5 Hz Other status ALM (Red) Off Off Blinks at 0.5 Hz
The EMU board has the following advantages: l l High reliability: hot backup is applied for both the power supply and the circuits. Wide voltage support range: 27 V system: 18 V to 36 V. -48 V system: -36 V to -72 V. l l
Issue 08 (2011-09-30)
Wide temperature detecting range: -20C to +80C Jumper not required: all settings are specified through DIP switches.
External lightning arrester not required for power cables and other circuits: internal lightning protection circuits in the EMU can meet the requirements of the indoor BTS.
2.97.4 Parameters
This chapter describes the parameters related to the Remote EAC Maintenance feature. For the meaning of each parameter, see Table 2-252. For the default value, value ranges, and MML commands of each parameter, see Table 2-253. Table 2-252 Parameter description (1) Parameter Description Whether to allow the configuration of alarm parameters. The value "YES" indicates that the configuration is allowed, and the value "NO" indicates that the configuration is not allowed. If the parameter is set to "YES", all the other parameters are reset to the default values in this command. In multi-mode scenario, the value of this parameter in one mode must be the same as the value of the corresponding parameter in another mode. Whether to enable the special analog alarm. In multi-mode scenario, the value of this parameter in one mode must be the same as the value of the corresponding parameter in another mode. Whether to enable the special alarm switch. In multi-mode scenario, the value of this parameter in one mode must be the same as the value of the corresponding parameter in another mode. Level specifications of special Boolean value alarms. Two specifications are available: high level and low level. By default, only alarms of the door status sensor are low level, and alarms of the water sensor, smoke sensor, and infrared sensor are high level. In multi-mode scenario, the value of this parameter in one mode must be the same as the value of the corresponding parameter in another mode.
Special Analog Alarm Enabled
Special Alarm Switch Enabled
Special Alarm Switch Valid Vol. Level
Issue 08 (2011-09-30)
1330
Table 2-253 Parameter description (2) Parameter Defau lt Value GUI Value Range Actual Value Range Unit MML Command SET BTSFMUABP (Mandatory) SET BTSUSCUBP (Mandatory) SET BTSDDPUBP (Mandatory) SET BTSPSUFP (Mandatory) SET BTSDTMUBP (Mandatory) SET BTSDPMUBP (Mandatory) SET BTSDOMUBP (Mandatory) SET BTSDHEUBP (Mandatory) SET BTSDEMUBP (Mandatory) SET BTSDATUBP (Mandatory) SET BTSAPMUBP (Mandatory) Board Parameter Configuratio n Enabled SET BTSPMUBP (Mandatory) NO(NO), YES(YES) SET BTSNFCBBP (Mandatory) Im pac t
None
NO, YES
None
BTS
Issue 08 (2011-09-30)
1331
Parameter
Defau lt Value
GUI Value Range 48VDISABL E, RES0, RES1, RES2, TSDISABLE D, HSDISABLE D, RES3, RES4 WIDISABLE , SMDISABL E, IMDISABLE , GMDISABL E WILOW, SMLOW, IMLOW, GMLOW
Actual Value Range 48VDISABL E, RES0, RES1, RES2, TSDISABLE D, HSDISABLE D, RES3, RES4 WIDISABLE , SMDISABL E, IMDISABLE , GMDISABL E WILOW, SMLOW, IMLOW, GMLOW,
Unit
MML Command
Im pac t
Special Analog Alarm Enabled
None
None
SET BTSDEMUBP (Optional)
BTS
Special Alarm Switch Enabled Special Alarm Switch Valid Vol. Level
None
None
BTS
None
None
BTS
2.97.5 Counters
None.
2.97.6 Glossary

2.98 Remote Upgrade of the BSC&BTS Software

2.98.1 Introduction
2.98.1.1 Scope
This document describes the application scenarios and network structure for remote upgrade of the BSC and BTS software in GBSS9.0.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Remote Upgrade of the BSC&BTS Software feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.98.2 Overview of Remote Upgrade of the BSC&BTS Software

Remote upgrade of BSC software is a process in which the BSC software is remotely upgraded through the M2000. Multiple BSCs can be upgraded in batches. Remote upgrade of BTS software is a process in which the BTS software is remotely upgraded through the M2000. Multiple BTSs can be upgraded at a time. Remote software upgrade can be implemented through an automatic upgrade procedure on the GUI. This facilitates the upgrade and improves the reliability of upgrade. Remote software upgrade not only avoids inconvenient local maintenance, for example, in a remote area, but also shortens the time of service disruption due to system upgrade by upgrading multiple network
elements (NEs) at a time. Remote software upgrade can be performed automatically and multiple NEs can be upgraded at a time. Thus, the working efficiency of maintenance personnel is improved, and the upgrade cost is reduced.

2.98.3.1 Typical Network Structure for Remote Software Upgrade
Figure 2-348 shows a typical network structure for remote upgrade of the BSC and BTS software in GBSS9.0. Figure 2-348 Typical network structure for remote upgrade of the BSC and BTS software in GBSS8.1
2.98.3.2 Remote Upgrade of BSC Software

Huawei BSS supports remote upgrade of the host software and OMU software of the BSC through the M2000.
?.1. Procedure for Remote Upgrade of BSC Software

Figure 2-349 shows the procedure for remote upgrade of BSC software.
Issue 08 (2011-09-30)
1334
Figure 2-349 Procedure for remote upgrade of BSC software
This procedure is described as follows: l Prepare for the upgrade. The preparation involves applying for a new license, collecting the information about the site, performing the NE health check, and preparing files for the upgrade. l l Start the upgrade client through the M2000. Download the upgrade package from the M2000 to the OMU. Configure the basic information about the upgrade. The basic information includes the upgrade type, OMU IP address, and administrator password for the OMU. l Perform pre-upgrade. The pre-upgrade involves backing up data, checking the environment information, and preupgrading the OMU software and data. l l Perform upgrade. The upgrade involves upgrading the OMU version and restarting the host. Verify whether the upgrade is successful. The verification involves checking the network health and verifying services. The purpose of network health check is to check the resource usage and state of NEs. The purpose of service verification is to verify whether services are processed properly after the upgrade. l
Issue 08 (2011-09-30)
Perform version rollback.

If the version or patch is found faulty after the version upgrade or patch installation, version rollback must be performed.
?.2. Characteristics and Specifications of Remote Upgrade of BSC Software

The remote upgrade of the BSC software can be the combination of version upgrade and patch installation. A maximum of 10 BSCs can be upgraded remotely at a time.
2.98.3.3 Remote Upgrade of BTS Software

The BTS software supports one-key upgrade and automatic upgrade. l l In a one-key upgrade, maintenance personnel load and activate the BTS software through the M2000. In an automatic upgrade, the BSC automatically upgrades the BTS software according to the BTS software version information configured by the maintenance personnel. Automatic upgrade does not require manual operation.
?.1. Procedure for Remote Upgrade of BTS Software

Figure 2-350 shows the procedure for remote upgrade of BTS software. Figure 2-350 Procedure for remote upgrade of BTS Software
Issue 08 (2011-09-30)
1336
This procedure is described as follows: l l l l l l l Upload the software. Upload the BTS software upgrade package to the M2000. Download the software. Download the BTS software from the M2000 to the BSC OMU. Select the BTS. Select the BTS to be upgraded. Select the version of BTS. Select the BTS version to be upgraded. Load the BTS. Load the BTS software to the target BTS. Activate the software. Activate the new software version of the BTS. Then, restart the BTS. Check whether the upgrade is successful. After the upgrade, check the NE version, state, and alarms and check whether services are processed properly after the upgrade. l Perform version rollback. If the version or patch is found faulty after the version upgrade or patch installation, version rollback must be performed.
?.2. Characteristics and Specifications of Remote Upgrade of BTS Software

The remote upgrade of BTS software has the following characteristics: l l l l l l l l l l l l Efficient software installation and upgrade Check of software and hardware compatibility, which ensures a successful software installation and upgrade Version management, for example, query of the software and hardware version Automatic data conversion during software upgrade Improvement of the software download efficiency and expansion of OM channel bandwidth during software upgrade Support of software download based on data configuration Support of the batch download and activation of BTS software The specifications of remote upgrade of BTS software are as follows: In a one-key upgrade, multiple BTSs under one or more BSCs can be upgraded through the M2000. A maximum of 500 BTSs can be upgraded simultaneously through the M2000. If more than 500 BTSs need to be upgraded, the M2000 upgrades these BTSs in batches, with not more than 500 BTSs in each batch. A maximum of 100 BTSs under one BSC can be upgraded simultaneously through the M2000. If more than 100 BTSs under one BSC need to be upgraded, the BSC upgrades these BTSs in batches, with not more than 100 BTSs in each batch.
2.98.4 Parameters
None.
2.98.5 Counters
None.
2.98.6 Glossary

2.99 Signaling Transport Point(STP)

2.99.1 Introduction
2.99.1.1 Scope
This document describes the benefits of the signalling transfer point (STP) feature and the principle of implementing this feature in Huawei GSM BSS.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Signaling Transport Point(STP) feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.99.2 Overview of STP

With the development of mobile communications, the networking modes of the core network (CN), transport network, and access network are more flexible. Huawei GSM BSS supports the STP feature to meet the requirements of operators with regard to the networking mode. The STP feature enables the transfer of signaling messages between signaling points. Huawei BSC6900 supports the STP feature to meet the requirements of operators for flexible networking. l l Implements the signaling transfer between the MSC and the BSC through the MGW, thus separating the signaling plane from the user plane. Implements different levels of transmission security, thus ensuring the security of the core services in an efficient way and reducing the transmission cost.

Huawei BSC6900 supports the SCCP/M3UA/MTP3-based signaling transfer over the A interface. Through this feature, the BSC can be connected to the MSC through the signaling transfer of the MGW, thus providing more transmission networking modes. Figure 2-351 Typical networking between the BSC and the CN
Issue 08 (2011-09-30)
1339
The BSC is physically connected to the MGW, and a signaling route is configured between the BSC and the MSC server. The MGW is configured as an STP at the BSC, that is, the MGW acts as an STP and transfers signaling messages from the BSC to the MSC. The followings will instruct to configure the STP. l l TDM transmission When adding the MGW as a destination signaling point, set DSP code[Whole Number] to the signaling point code of the MGW, DSP type to STP, and DSP bear type to MTP3. When adding the MSC as the destination signaling point, set DSP code[Whole Number] to the signaling point code of the MSC, DSP type to A, and DSP bear type to MTP3. l l IP transmission When adding the MGW as a destination signaling point. In this step, set DSP code[Whole Number] to the signaling point code of the MGW, DSP type to STP, and DSP bear type to M3UA. When adding the MSC as a destination signaling point. In this step, set DSP code[Whole Number] to the signaling point code of the MSC, DSP type to A, and DSP bear type to M3UA. Currently, Huawei BSC6900 supports a maximum of 32 STPs.
2.99.4 Parameters
This chapter describes the parameters related to the Signaling Transport Point(STP) feature. For the meaning of each parameter, see Table 2-254. For the default value, value ranges, and MML commands of each parameter, see Table 2-255. Table 2-254 Parameter description (1) Parameter DSP type Description DSP type. STP: indicates the signaling transfer point. A: indicates the signaling point of the A interface control signaling plane. IUR_G: indicates the signaling point of the base station controller that is connected to the BSC. LB: indicates the signaling point of the LB interface. DSP bearer type. MTP3: indicates that the lower layer bearer is the MTP3 used in ATM/TDM scenario; M3UA: indicates that the lower layer bearer is the M3UA used in IP scenario; MTP3_M3UA: indicates that the lower layer bearer is the MTP3 and M3UA used in ATM/TDM/IP scenario. As an integer, the DSP code can be expressed by a decimal digit or a hexadecimal digit. If the DSP code is expressed by a hexadecimal digit, H' is added before the number.
DSP bear type
DSP code[Whole Number]
Issue 08 (2011-09-30)
1340
Table 2-255 Parameter description (2) Defau lt Value None GUI Value Range STP(STP), A(A), IUR_G (IUR_G), LB(LB) MTP3 (MTP3), M3UA (M3UA), MTP3_M3 UA(MTP3 and M3UA) 1~1677721 5 Actual Value Range STP, A, IUR_G, LB MML Comman d ADD N7DPC (Mandator y) ADD N7DPC (Mandator y) Impac t SCCP
Parameter DSP type
Unit None
DSP bear type
None
MTP3, M3UA, MTP3_M3UA
None
SCCP
DSP code [Whole Number]
None
1~16383 (BIT14), 1~65535 (BIT16), 1~16777215 (BIT24)
None
ADD N7DPC (Mandator y)
SCCP
2.99.5 Counters
None.
2.99.6 Glossary

l l l l l l 3GPP TS 43.903: "A-interface over IP Study" BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.100 Support of Daylight Saving Time

2.100.1 Introduction
2.100.1.1 Scope
This document describes the Support of Daylight Saving Time functional.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Support of Daylight Saving Time feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.100.2 Overview of Support of Daylight Saving Time

Daylight Saving Time (DST) is a way of obtaining more light during the day by advancing clocks by one hour in summer. The reason DST works is because it saves energy due to less artificial light needed during the evening hours. Clocks are set one hour ahead to standard time in the spring and one hour back to standard time in the autumn.

Huawei BSS supports the DST, which can be configured and queried to meet the requirements of the countries where the daylight saving time is applied. The BSS can set and query the time
zone and DST change rules on the M2000 or LMT. When daylight saving time is enabled, Huawei BSS reports time with the flag "DST", for example, 2009-06-01 08:00 DST. By applying the DST change rules, you can select the date configuration, week configuration, or hybrid configuration. l l l Date configuration indicates that the DST starts from or ends on a certain date in a certain month. Week configuration indicates that the DST starts from or ends on a certain day of a certain week in a certain month. Hybrid configuration indicates that the DST starts from or ends on a certain day after a certain date in a certain month.
2.100.4 Parameters
This chapter describes the parameters related to the Support of Daylight Saving Time feature. For the meaning of each parameter, see Table 2-256. For the default value, value ranges, and MML commands of each parameter, see Table 2-257. Table 2-256 Parameter description (1) Parameter DaylightSave StartType Description Whether daylight saving time has to be used. Type of the start date. "WEEK" indicates that the start date is a weekday. "DATE" indicates that the start date is a month day. "DATEWEEK" indicates the start date is expressed by a combination of weekday and month day. Month in which DST starts. Start date of the daylight saving time (DST). Sequence of the start week of DST. Weekday on which DST starts. Start of DST. Type of the end date. "WEEK" indicates that the end date is a weekday. "DATE" indicates that the end date is a month day. "DATEWEEK" indicates the end date is expressed by a combination of weekday and month day. Month on which DST ends. End date of the daylight saving time. Sequence of the end week of DST. Weekday on which DST ends. End time of DST. Offset to DST, namely, the adjustment to time.
Start month Start date Start week sequence Start week StartTime EndType
End month End date End week sequence End week EndTime AdjustMethod
Issue 08 (2011-09-30)
Table 2-257 Parameter description (2) Paramet er Daylight Save StartTyp e Defau lt Value NO None GUI Value Range NO(NO), YES (YES) DATE(Input with date), WEEK(Input with week), DATEWEEK (Input with date and week) JAN(January), FEB(February), MAR(March), APR(April), MAY(May), JUN(June), JUL (July), AUG (August), SEP (September), OCT(October), NOV (November), DEC (December) 1~31 Actual Value Range YES, NO DATE, WEEK, DATEWE EK Uni t Non e Non e MML Command SET TZ (Optional) SET TZ (Mandatory )
Impact BSC6900 BSC6900
Start month
None
JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Non e
SET TZ (Mandatory )
BSC6900
Start date
None
1~31
SET TZ (Mandatory ) SET TZ (Mandatory )
BSC6900
Start week sequence
None
FIRST(First), SECOND (Second), THIRD(Third), FOURTH (Fourth), LAST (Last)
FIRST, SECOND, THIRD, FOURTH, LAST
Non e
BSC6900
Issue 08 (2011-09-30)
1344
Paramet er Start week
Defau lt Value None
GUI Value Range SUN(Sunday), MON (Monday), TUE (Tuesday), WED (Wednesday), THU (Thursday), FRI (Friday), SAT (Saturday) HOUR, MIN, SEC DATE(Input with date), WEEK(Input with week), DATEWEEK (Input with date and week) JAN(January), FEB(February), MAR(March), APR(April), MAY(May), JUN(June), JUL (July), AUG (August), SEP (September), OCT(October), NOV (November), DEC (December) 1~31
Actual Value Range SUN, MON, TUE, WED, THU, FRI, SAT
Uni t Non e
MML Command SET TZ (Mandatory )
Impact BSC6900
StartTim e EndType
None
HOUR, MIN, SEC DATE, WEEK, DATEWE EK
Non e Non e
BSC6900
None
BSC6900
End month
None
JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC
Non e
SET TZ (Mandatory )
BSC6900
End date
None
1~31
BSC6900
End week sequence
None
FIRST(First), SECOND (Second), THIRD(Third), FOURTH (Fourth), LAST (Last)
FIRST, SECOND, THIRD, FOURTH, LAST
Non e
BSC6900
Issue 08 (2011-09-30)
1345
Paramet er End week
Defau lt Value None
GUI Value Range SUN(Sunday), MON (Monday), TUE (Tuesday), WED (Wednesday), THU (Thursday), FRI (Friday), SAT (Saturday) HOUR, MIN, SEC -120~-1,1~120
Actual Value Range SUN, MON, TUE, WED, THU, FRI, SAT
Uni t Non e
MML Command SET TZ (Mandatory )
Impact BSC6900
EndTime
None
HOUR, MIN, SEC -120~-1, 1~120
Non e min
BSC6900
AdjustM ethod
None
BSC6900
2.100.5 Counters
None.
2.100.6 Glossary

l l l l l BSC6900 Feature List BSC6900 Basic Feature Description GSM BSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference
2.101 Supporting Three-Digit MNC

2.101.1.1 Scope
This document describes the system principle of Supporting Three-Digit Mobile Network Code (MNC).


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Supporting Three-Digit MNC feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.101.2 Overview of Supporting Three-Digit MNC

Huawei BSC starting from BSC6000V900R008 supports three-digit MNC. The BSC6900 supports both three-digit and two-digit MNCs. The BSC6900 meets the networking requirement of countries where the MNC consists of three digits.

The MNC consists of two or three digits. For Personal Communications System operating in the 1,900MHz band (PCS1900) for network access, federal regulation mandates that a three-digit MNC will be used. With the three-digit MNC, the number of networks that can be described increases from a maximum of 100 to a maximum of 1000. A network operator, however, may decide to use only two digits in the MNC in the LAI over the radio interface.
Mobile equipment compliant with earlier versions of 3GPP specifications may be unable to identify the three-digit MNC format of the LAI, and therefore be unable to register in a network broadcasting the LAI in this format.
2.101.4 Parameters
None.
2.101.5 Counters
None.
2.101.6 Glossary

l l l l l 3GPP TS 24.008: Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 3GPP TS 23.003: Numbering, addressing and identification BSC6900 Feature List BSC6900 Basic Feature Description
2.102 TCH Re-assignment

2.102.1.1 Scope
This document describes the concept, benefits, and procedure of TCH re-assignment.


The change history provides information on the changes between different document versions.
There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the TCH Re-assignment feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.102.2 Overview of TCH Re-assignment

TCH re-assignment is a process through which the BSC re-assigns a TCH to the MS, after the assignment of a TCH to the MS fails and the MS returns to the SDCCH. TCH re-assignment has the following benefits: l l Reducing the impact on call maintenance due to failure of a TRX channel in the cell and avoiding the failure of the call in the first dialing attempt accordingly. Reducing the assignment failures due to interference on certain frequencies in the cell and avoiding the impact on call maintenance accordingly. Improving QoS for users.

The triggering of TCH re-assignment is determined by the parameter Allow Reassign. On receiving an Assignment Request message from the MSC during call setup, the BSC assigns a TCH for a call, and then sends an Assignment Command message to the MS. If the MS fails to access the TCH for certain reasons, such as co-channel interference, and returns to the SDCCH, the BSC does not immediately send an Assignment Failure message to the MSC. Instead, the BSC assigns another TCH for the call and the MS. If the second assignment succeeds, the BSC sends an Assignment Complete message to the MSC; otherwise, the BSC sends an Assignment Failure message to the MSC. Figure 2-352 shows the TCH re-assignment procedure.
Issue 08 (2011-09-30)
1349
Figure 2-352 TCH re-assignment procedure
1.
On receiving the Assignment Failure message from the MS, the BSC stops timer T3107. After internal processing, the BSC sends a Channel Activation message to the BTS, and waits for the Channel Activation Acknowledge message from the BTS. To avoid deterioration of QoS due to interference, TRX channel failure, or engineering mishandling, a TCH either on the same frequency band or on a different frequency band can be assigned during TCH re-assignment. The frequency band is determined by the parameter Frequency Band of Reassign.
2. 3.
On receiving the Channel Activation Acknowledge message from the BTS, the BSC proceeds with internal handling. The BSC uses the SDCCH, which has not been released, to send an Assignment Command message to the MS, and waits for the Establish Indication message from the MS.
Issue 08 (2011-09-30)
4. 5. 6. 7. 8.
The MS sends SABM frames to the BTS to access the network, through the FACCH as indicated in the Assignment Command message. The BTS makes a response by sending UA frames to the MS, through the FACCH. The BTS sends an Establish Indication message to the BSC. After accessing the network through the traffic channel, the MS sends an Assignment Complete message to the MSC, through the FACCH. After both the radio traffic channel and the terrestrial circuit are successfully established, the BSC sends an Assignment Complete message to the MSC, through the occupied TCH. At this stage, the call is regarded to be in conversation state.
2.102.4 Parameters
This chapter describes the parameters related to the TCH Re-assignment feature. For the meaning of each parameter, see Table 2-258. For the default value, value ranges, and MML commands of each parameter, see Table 2-259. Table 2-258 Parameter description (1) Parameter Description Whether to re-assign the radio channels on a different band or on the same band. This can help minimize the decrease in service quality due to interference, faulty TRX paths, or faulty project constructions.
Frequency Band of Reassign
Table 2-259 Parameter description (2) Parameter Defau lt Value GUI Value Range Same_Band (Same Band), Diff_Band (Different Band) Actual Value Range Unit MML Command Imp act
Frequency Band of Reassign
Diff_B and
Same_Band, Diff_Band
None
SET GCELLCCAD (Optional)
Cell
2.102.5 Counters
2.102.6 Glossary

l l l l l l l l
3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3" 3GPP TS 44.018: "Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol" 3GPP TS 48.008: "Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification" 3GPP TS 48.058: "Base Station Controller - Base Transceiver Station (BSC-BTS) Interface; Layer 3 specification" BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM Performance Counter Reference BSC6900 GSM MML Reference
2.103 TRX Management

2.103.1.1 Scope
This document describes the functions and technologies regarding the TRX management feature of Huawei GBSS. TRX management includes the following procedures: radio resource indication, SACCH filling information modification, flow control, and error reporting.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the TRX Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.103.2 Overview of TRX Management

TRX Management involves the following procedures: l l l l The radio resource indication procedure is used to notify the BSC of the interference levels on idle channels on a TRX. The SACCH filling information modification procedure is triggered by the BSC to notify the BTS of the new information to be used as filling information on SACCHs. The flow control procedure is used for flow control to prevent CCCH overload, ACCH overload, and processor overload. The error reporting procedure is triggered by the BTS to report detected errors if they cannot be reported by any other procedure.

2.103.3.1 Radio Resource Indication
In this procedure, the BTS notifies the BSC of the interference levels on idle channels of a TRX. The interference signals are classified into five interference levels according to the strength of interference signals. The TRX determines the current interference level based on the average interference signal level and the interference band threshold of each interference level. Then through the RF RESource INDication message, TRX reports the interference level for each channel that is idle (not active) in the entire measurement period to the BSC. The rate at which the RF RESource INDication messages are sent and the interference band threshold of each interference level are set by O&M.
2.103.3.2 SACCH Filling Information Modification

In this procedure, the BSC notifies the BTS of the new information to be used as filling information on SACCHs.
The BSC sends a SACCH FILLing message to the BTS. This message contains the new broadcast information to be used as filling information on downlink SACCH.
2.103.3.3 Flow Control

In this procedure, flow control is implemented, to protect TRX processor, downlink CCCH, and ACCH from being overloaded. The BTS notifies the BSC of overload by sending an OVERLOAD message. This message contains the value of the following possible causes: l l l CCCH overload; ACCH overload; Processor overload.
2.103.3.4 Error Reporting

If the detected errors cannot be reported by any other procedure, this procedure is initiated by the BTS to report the errors through the following messages: l l l CHANNEL ACTIVATION NACK in the case of channel activation; MODE MODIFY NACK in the case of the change in channel mode; ERROR REPORT in other cases.
When a TRX detects the reception of an erroneous message, it sends an ERROR REPORT message with a cause value to the BSC. To identify the type of messages, Message Type, Channel Number, and Link Identifier must be included in the error report messages. Note that a complete message, for example, the message CHANNEL ACTIVATION NACK+CHANNEL ACTIVATION, includes all the required information.
Issue 08 (2011-09-30)
1354

The related parameters for the radio resource indication procedure must be configured on the BSC. You are advised to set these parameters as follows: l l l l l l l Radio Resource Report Period is set to 10. Interference Band Threshold 0 is set to 110. Interference Band Threshold 1 is set to 105. Interference Band Threshold 2 is set to 98. Interference Band Threshold 3 is set to 92. Interference Band Threshold 4 is set to 87. Interference Band Threshold 5 is set to 85.
The strength of the current interference is determined on the basis of the preset Interference band thresholds and is reported to the BSC. Then, the BSC compares the number of occupied channels with the number of idle channels in the measurement report and the radio resource indication to determine whether a handover is required. In this manner, the speech quality can be ensured.
2.103.5 Parameters
This chapter describes the parameters related to the TRX Management feature. For the meaning of each parameter, see Table 2-260. For the default value, value ranges, and MML commands of each parameter, see Table 2-261. Table 2-260 Parameter description (1) Parameter Radio Resource Report Period Description Interval for sending the radio resource indication messages. The TRX reports the interference level for each of the channels that have been idle for the whole measurement period. This parameter is used by a BTS to inform the BSC6900 of the interference levels on idle channels of a TRX. For details, see GSM Rec. 08.58 and 08.08. Threshold used for interference measurement. The BSS measures the uplink quality of the radio channels occupied by MSs, and calculates and reports the interference on each of the idle channels. This helps the BSC6900 to assign channels. According to the strength of interference signals, the interference signals are classified into five interference levels. The values of these levels are called interference band thresholds. The BTS determines the current interference level based on these thresholds, and then reports a radio resource indication message to the BSC6900. The BSC6900 compares the busy and idle channels reported in the measurement report and in the radio resource indication message to determine whether to perform a handover. The interference band statistics result provides reference for threshold setting and interference analysis. For details, see GSM Rec. 08.08 and GSM Rec. 08.58.
Interference Band Threshold 0 Interference Band Threshold 1 Interference Band Threshold 2 Interference Band Threshold 3 Interference Band Threshold 4 Interference Band Threshold 5
Issue 08 (2011-09-30)
1355
Table 2-261 Parameter description (2) Defau lt Value 10 GUI Value Range 0~255 Actual Value Range 0~255 Uni t s MML Command SET GCELLCCCH (Optional) SET GCELLOTHEX T(Optional) SET GCELLOTHEX T(Optional) SET GCELLOTHEX T(Optional) SET GCELLOTHEX T(Optional) SET GCELLOTHEX T(Optional) SET GCELLOTHEX T(Optional)
Parameter Radio Resource Report Period Interference Band Threshold 0 Interference Band Threshold 1 Interference Band Threshold 2 Interference Band Threshold 3 Interference Band Threshold 4 Interference Band Threshold 5
Impact Cell
110
48~115
48~115
Non e Non e Non e Non e Non e Non e
Cell
105
48~115
48~115
Cell
98
48~115
48~115
Cell
92
48~115
48~115
Cell
87
48~115
48~115
Cell
85
48~115
48~115
Cell
2.103.6 Counters
2.103.7 Glossary

l l l l l
Issue 08 (2011-09-30)
3GPP TS 08.58: "Base Station Controller-Base Transceiver Station(BSC-BTS) interface;Layer3 specification" BSC6900 GSM MML Reference BSC6900 GSM Performance Counter Reference BSC6900 Feature List BSC6900 Basic Feature Description
2.104 System Redundancy

2.104.1.1 Scope
This document describes the system redundancy (MRFD-210101 System Redundancy) feature of the SRAN system.

It is assumed that users of this document are familiar with GSM/UMTS basics and have a working knowledge of GSM/UMTS telecommunication. This document is intended for: l l Personnel working on Huawei GSM/UMTS products or systems System operators who need a general understanding of this feature

The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the System Redundancy feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.104.2 Overview
The System Redundancy feature provides the reliability designs such as the active/standby mode, load sharing, and redundancy configuration, thus improving the system reliability.

To ensure the reliable operation of the system, the SRAN system adopts the reliability designs such as the active/standby mode, load sharing, and redundancy configuration. l Load sharing In the resource pool mode, the load sharing is performed among processing units in the pool. When one or multiple processing units are faulty, the ongoing services are disrupted, and new services requests are allocated to other normal processing units in the resource pool. l Active/standby mode In the active/standby mode, the active board processes services while the standby board acts as a backup of the active one. When the active board is faulty or needs to be replaced, the services can be switched over to the standby board to ensure the normal operation of services. There are two types of switchover. One is automatic switchover. An automatic switchover is triggered by the system in the case that the active board is faulty. The other is manual switchover. A manual switchover is performed by maintenance engineers on the LMT. Maintenance engineers use the immediate switchover command to switch over the active and standby boards. To ensure a successful active/standby switchover, the following conditions must be met: 1. 2. The standby board must work normally. No major or critical alarm is reported.
When the standby board is switched over to the active state, the previously active board will be reset automatically. If this board restarts normally, it is switched over to the standby state. For the interface board, the board backup mode is adopted. Some interface boards also support the standard backup modes specified in 3GPP specifications, such as MSP 1+1 or MSP 1:1. When detecting that the board is faulty, the system re-establishes the transmission links for the ongoing services on the standby board through an active/standby switchover. When detecting that the active channel is damaged, the system enables the ongoing services to be transmitted through the standby channel through an active/standby switchover. l Redundancy configuration Redundancy configuration can be applied to the following units: boards, transmission interfaces, power, and fans. The software version and important data configuration file are backed up to ensure that the system works normally even if an exception occurs in the file or data. For the BSC/RNC, the signaling processing system and service processing system of the .SRAN system are designed to work in resource pool mode. There are five independent system-level resource pools, which are used to process the GSM CS, GSM PS, GSM signaling, UMTS user plane, and UMTS signaling services respectively. The service processing boards of the BSC/RNC also work in the resource pool mode. That is, load sharing is performed in the resource pool. The other boards work in the active/standby mode. That is, the boards of the same type configured in two neighboring slots work in the active/standby mode. Huawei BTS/NodeB supports the board-level backup. Two boards of the same type work in the active/standby mode. When the active board is faulty, a switchover is performed between the active and standby boards to switch over the services to the standby board.

Different boards support different reliability modes. The details are as follows: l l l l l l Service processing boards support only the loading sharing in the resource pool mode. Signaling processing boards support only the active/standby mode. Switching boards support only the active/standby mode. Clock boards support only the active/standby mode. Interface boards support both the active/standby mode and the independent mode. Operation and maintenance boards support both the active/standby mode and the independent mode.
2.104.5 Parameters
None.
2.104.6 Counters
None.
2.104.7 Glossary

None.
2.105 Operate System Security Management

2.105.1.1 Scope
This document describes the operate system security management feature of Huawei SRAN (MRFD-210102 Operate System Security Management). It covers the functionality of and technologies regarding this feature. 8

Feature change Feature change refers to the change in the Operate System Security Management feature of a specific product version.
Document Issues
01(2010-01-20)
2.105.2 Overview
As the operation and maintenance unit of the BSC6900, the OMU is mainly responsible for the operation and maintenance function of the BSC6900. The OMU supports the three operate systems: Windows, Suse Linux, and Dopra Linux. The OMU works as an information exchange bridge between BSC6900 and the outside world, and at the same time the OMU becomes an entrance for security risks. In accordance with the security risks of the operate system on the OMU, the measures such as anti-virus, system security enhancement, and system patching are taken to improve the security level of the operate system. In different scenarios, there are different operate systems. l When BSC6810 is upgraded to BSC6900, Windows in BSC6810 can keep functioning in BSC6900 or Windows can be switched to Dopra Linux through a tool for switching operate systems. When BSC6000 is upgraded to BSC6900, Suse Linux in BSC6000 can keep functioning in BSC6900 or Suse Linux can be switched to Dopra Linux through a tool for switching operate systems.
When BSC6900 is newly built in an office, the default operate system on the OMU is Dopra Linux.

2.105.3.1 Operate System Anti-Virus
As widely used operate systems, Windows and Suse Linux on the OMU are confronted with increasing network virus attack and malicious network attack. The security problem of the operate system is thus triggered. BSC6900 provides an anti-virus solution for the entire network of mobile system operation and maintenance, including providing integrated anti-virus software and virus protection policies to the OMU installed with Suse Linux or Windows. Dopra Linux is an operate system customized by Huawei and thus involves no anti-virus software.
For Suse Linux Before installing the anti-virus software, refer to the Anti-Virus Software Installation Guide provided by Huawei. Huawei OMU supports the anti-virus software deployment: Trend Micro Control Manager (TMCM) + ServerProtect for Linux2.5.
TMCM TMCM is web-based management control console. TMCM provides centralized monitoring of anti-virus products and service in the entire network. TMCM manages the gateway, mail server, file server, Trend Micro products and service, and third-party antivirus and security products. The TMCM server can connect to the Internet, download the latest virus feature codes, and upgrade the BSC6900 that is in the charge of the TMCM server and is based on Suse Linux.
ServerProtect for Linux Trend Micro ServerProtect for Linux 2.5 (TMSP) provides comprehensive and real-time protection to enterprise servers. It protects the servers against internal or external virus propagation, spy software, and other threats. TMSP provides centralized scanning of virus/ malicious threats, update on virus feature codes, reporting of events, and configuration. Huawei BSC6900 supports TMSP, which monitors BSC6900 and protects it against virus.
For Windows Installing OfficeScan is recommended. OfficeScan is the enterprise network version of the virus defense software for mainstream desktop system provided by Trend Micro. As verified through strict testing by Huawei, OfficeScan is compatible with the OMU. If operators hope to use other virus defense software such as Symantec and McAfee, they need to purchase the software on their own. Huawei can aid them in installing the software. The software needs to be tested for compatibility before its use.
Issue 08 (2011-09-30)
1361
In addition to software installation, a separate server for virus feature codes and upgrade needs to be deployed in the demilitarized zone (DMZ) of the operation and maintenance network. The server is responsible for obtaining the latest virus feature codes or upgrade packet from the Internet. The anti-virus server in the internal network of operation and maintenance, for example, Officescan7 Server is not connected to the Internet directly. Instead, the anti-virus server is upgraded by being connected to the server for virus feature codes and upgrade in the DMZ. After the anti-virus server is upgraded, the equipment in the entire network automatically upgrades virus feature codes and upgrade packets. In this way, the defense of the BSC6900 is upgraded and viruses are monitored and managed.
2.105.3.2 Operate System Security Enhancement

Generally, security holes and hidden danger exist in operate systems. These security holes and hidden danger are vulnerable to malicious attack on the operate system by local or remote attackers. Consequently, operate systems and related software are damaged and normal operation of operate systems is affected. Considering the hidden security danger mentioned above, Huawei provides operate system security enhancement solutions for Windows, Suse Linux, and Dopra Linux. By customizing the network visit, network security, system service, and system installation of the operate systems, Huawei effectively improves the anti-virus and anti-attack capability of the system, strengthens the fault-free operation capability of the system, and improves the overall service level of the network. l For Windows and Suse Linux The operate system security enhancement tools for Windows and Suse Linux are SetWin and SetSuse respectively. Through security customization policies, the operate systems are protected against attacks and the security of the operate systems is strengthened. The applications of the security customization policies include: Executing policies Operators can execute one or several policies simultaneously. The execution results are recorded in a log file. Rolling back policies
After executing policies, operators can roll back to the configuration state before execution or customize execution policy anew. Operators can recover the executed policies. Generating a backup point Operators can store the current state of policies in a file and create a backup point for the policy settings. Storing configuration Operators can store the current state of policy configuration. Exporting configuration Operators can export the current policy configuration to a file. Importing configuration Operators can import files containing policy configuration information to the system so that the system has the same configuration. Importing original configuration files Operators can import the configuration files of SetWin or SetSuse in earlier versions. Loading the configuration file anew The operate system tool includes a configuration file. If operators run the command of loading the configuration file anew, the operate system loads the configuration file anew. l For Dopra Linux Customized by Huawei, Dopra Linux integrates multiple security policies such as basic security, system service security, file and directory security, core security, system visit authentication, account and password security, security auditing, and additional security. The security of the operate system is thus improved greatly.
2.105.3.3 Operate System Patching

Patches for the operate system consist of the basic patch and incremental patch. The basic patch for the previous year is released once a year and the incremental patch for the current year is released periodically. The BSC6900 is installed with the basic patch on the OMU before delivery. The operating equipment in the existing network installs patches in time according to patch release notifications from Huawei. The BSC6900 provides local patching and remote patching. l Local patching By connecting the local maintenance terminal directly to the OMU, operators can log in to the OMU operate system for operation. Patches are installed for the operate system of only one OMU at a time. l Remote patching In remote patching, operators install patches for the operate system on the OMU by using upgrade tools through the local network. Remote patching enables operators to install patches for the operate system of a batch of OMUs. The service ability is thus improved.

The anti-virus software for Windows and Suse Linux needs to be purchased. Dopra Linux does not involve anti-virus software for the moment.
The operate system security enhancement tools for Windows and Suse Linux are SetWin and SetSuse respectively. For Dopra Linux, the security enhancement function is integrated.
2.105.5 Parameters
None.
2.105.6 Counters
None.
2.105.7 Glossary

None.
2.106 BSC/RNC Resource Sharing

2.106.1.1 Scope
This document describes the BSC/RNC resource sharing feature (MRFD-210104 BSC/RNC Resource Sharing). It mainly describes the function and technical mechanism related to BSC/ RNC resource sharing, including resource sharing of the control plane and of the user plane.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l
Issue 08 (2011-09-30)
Feature change
Feature change refers to the change in the BSC/RNC Resource Sharing feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.106.2 Overview
The BSC/RNC Resource Sharing feature is classified into user plane resource sharing and control plane resource sharing. Based on the load sharing mechanism applied to the boards in the same subrack or the boards in other subracks, the MBSC implements the control plane resource sharing and user plane resource sharing in the BSC/RNC, thus improving the resource utilization in the system. Control plane resource sharing is used to share the CPU usage and memory. When the CPU usage of a certain control plane unit (CP unit) is too high or when the memory of a certain CP unit is insufficient, a new call is transferred to other CP units with low load. The MBSC implements the dynamic resource sharing based on the resource pool and load sharing in the BSC/RNC. If a certain user plane unit (UP unit) is overloaded, a new service is transferred to other UP units with low load.

2.106.3.1 Control Plane Resource Sharing
Figure 2-353shows the control plane resource sharing.
Issue 08 (2011-09-30)
1365
Figure 2-353 Control plane resource sharing
The control plane resource sharing is categorized into the following situations: l l When most calls arrive and the load of the CP unit is low, calls are directly processed on the CP unit, as the red arrow in the preceding figure shows. When calls arrive and the load of the CP unit is too high, calls are transferred to the corresponding MPU. Then, the MPU selects a proper control plane processing unit and forwards calls to this unit for processing. If the loads of all the control plane processing units are too high, the MPU selects a proper control plane processing unit controlled by other MPUs for processing calls, as the blue arrows in the preceding figure show. The green arrows in the preceding figure show the load collection and balancing process of the MPU.
The parameters CtrlPlnSharingOutThd, CtrlPlnSharingOutOffset, MaxCAPSMidLoad, SharingOutCAPSMidLoad, and MaxCAPSLowLoad are used to set the RNC oriented control plane load sharing.
2.106.3.2 User Plane Resource Processing

The service processing of the user plane in the BSC/RNC is implemented on the DSPs in the DPUb/DPUc/DPUd/DPUe board. Resource allocation and release are implemented under the control of the MPU. Therefore, the user plane resource sharing of each MPU in the entire system needs to be implemented through the interaction and collaboration with other MPUs.
Figure 2-354 User plane resource pool model
When any DSP in the MBSC has the capability to process user plane services, the user plane resources of this DSP can be allocated through the DSP resource pool controlled by the MPU and the inter-subrack load sharing mechanism if there are requests for user plane resources in the system. Figure 2-355 shows the user plane resource allocation. Figure 2-355 User plane resource allocation
The user plane resource allocation is categorized into the following situations:
When calls arrive, the UP unit requests user plane resources from the corresponding MPU, if the load of the user plane controlled by this MPU is low, the UP units with the lowest load are directly allocated to these calls (as the blue arrows in the preceding figure show). When calls arrive, the UP unit requests user plane resources from the corresponding MPU, if the user plane controlled by this MPU is overloaded, the MPU selects a proper UP unit controlled by other MPUs for call processing (as the green arrows in the preceding figure show).
The parameters UserPlnSharingOutThd and UserPlnSharingOutOffset are used to set the RNC oriented user plane load sharing.
2.106.4 Parameters
This chapter describes the parameters related to the Support of BSC/RNC Resource Sharing feature. Table 2-262 Parameter description Parameter ID CtrlPlnSharingOutThd NE BSC6900 MML SET UCTRLPLNSHAR EPARA(Optional) Description Meaning: Forwarding threshold of control plane load sharing. When the CPU usage is between the sharing threshold and overload threshold, and call number in each second reaches "SharingOutCAPSMidLoad", new arrival call attempts will be shared out to other UMTS CPUS. GUI Value Range: 0~100 Actual Value Range: 0~1, step:0.01 Unit: per cent Default Value: None
Issue 08 (2011-09-30)
1368
Parameter ID CtrlPlnSharingOutOffset
NE BSC6900
MML SET UCTRLPLNSHAR EPARA(Optional)
Description Meaning: The sharing offset should be added to the target subrack or subsystem. This parameter is used for preferable selection of the homing subrack and homing subsystem during call forwarding. GUI Value Range: 1~10 Actual Value Range: 0.01~0.1, step:0.01 Unit: per cent Default Value: None
MaxCAPSMidLoad
BSC6900
SET UCTRLPLNSHAR EPARA(Optional)
Meaning: Maximum numbers of incoming calls in one second when the load exceeds the forwarding threshold. When the CPU usage is between the sharing out threshold and overload threshold, and call number in one second reaches the threshold, new arrival call attempts will be shared out to other UMTS CPUS and none will be shared in this UMTS CPUS. GUI Value Range: 0~255 Actual Value Range: 0~255 Unit: None Default Value: None
Issue 08 (2011-09-30)
1369
Parameter ID SharingOutCAPSMidLoad
NE BSC6900
Description Meaning: Numbers of incoming calls to be shared when the load exceeds the forwarding threshold. When the CPU usage is between the sharing out threshold and overload threshold, and number of incoming calls in each second reaches the threshold, new arrival call attempts will be shared out to other UMTS CPUS. GUI Value Range: 0~255 Actual Value Range: 0~255 Unit: None Default Value: None
Issue 08 (2011-09-30)
1370
Parameter ID MaxCAPSLowLoad
NE BSC6900
Description Meaning: Maximum numbers of incoming calls in one second when the load is lower than the forwarding threshold. When the CPU usage is lower than the sharing out threshold and overload threshold, and call numbers in each second reach the threshold, new arrival call attempts will be shared out to other UMTS CPUS and none will be shared in this UMTS CPUS. GUI Value Range: 0~255 Actual Value Range: 0~255 Unit: None Default Value: None
UserPlnSharingOutThd
BSC6900
SET UUSERPLNSHAR EPARA(Optional)
Meaning: Percentage of User Plane Sharing Out threshold GUI Value Range: 50~100 Actual Value Range: 50~100 Unit: per cent Default Value: None Meaning: Percentage of User Plane Sharing Out Offset GUI Value Range: 5~20 Actual Value Range: 5~20 Unit: per cent Default Value: None
UserPlnSharingOutOffset
BSC6900
SET UUSERPLNSHAR EPARA(Optional)
Issue 08 (2011-09-30)
1371
2.106.5 Counters
None.
2.106.6 Glossary

None.
2.107 Connection with TMA (Tower Mounted Amplifier)

2.107.1.1 Scope
This document describes the functions and technologies regarding the connection with the tower mounted amplifier (TMA) feature of Huawei BSS/RAN (MRFD-210601 Connection with TMA (Tower Mounted Amplifier)), including the RF RX channel attenuation configuration, power supply configuration, and working status monitoring configuration for the TMA.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Connection with TMA (Tower Mounted Amplifier) feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.107.2 Overview
Installed on the tower top, a TMA is a device for amplifying uplink signals. As an optional component of the antenna system, the TMA compensates for the feeder loss caused by a long feeder to improve the uplink sensitivity and converge. In a network whose uplink coverage is limited, the TMA can be installed to improve the RX sensitivity and expand the cell radius, thus reducing the number of BTSs and minimizing investments. BTSs power and control the TMA. Huawei BTS provides the TMA with 1013 V output voltage. When a major alarm related to the TMA is reported, the BTS automatically sets the attenuation value of the RX channel to 0. After the alarm is cleared, the BTS automatically restores the attenuation value of the RX channel to the configured value. The RET control signals, power supply, and RF signals of the TMA are transmitted through the feeder. This facilitates operation and maintenance. The smart Bias Tee (SBT) powers the TMA through the feeder and provides the RCU with control signals. Huawei BTS also supports dual-TMA. Dual-TMA indicates that each TMA contains two pairs of RX/TX branches. Each sector needs to be configured with only one TMA. Each TMA also contains a low noise amplifier (LNA) for monitoring alarms. The functions of the two pairs of RX/TX branches of a TMA are the same, which are as follows: The RX channel has two RX filters and one LNA. When the input DC is faulty, the LNA is automatically ignored. The Bias Tee is configured on the BTS side of the TMA. The Bias Tee of a smart TMA (STMA) is referred to as an SBT. The Bias Tee can distinguish the combined signals of RF signals and DC signals, power the LNA, and provide the RCU with RET control signals. The TX channel contains a TX filter, as shown in Figure 2-356.
Issue 08 (2011-09-30)
1373
Figure 2-356 Working principle of the TMA

2.107.3.1 RF Receiver Channel Attenuation
The TMA can improve both the uplink RX gain and the RX sensitivity. When the BTS measures the uplink RX level, the measurement result must reflect the actual radio environment. Therefore, the TMA gain must be compensated reversely on the RF RX channel to ensure that the RX quality is improved and the RX level reflects the actual radio environment when the BTS measures the uplink RX level. When the TMA is configured, users need to set the RF RX channel attenuation of the RF antenna interface and the RX channel corresponding to the TRX to obtain the TMA gain according to the actual requirement. For the BTS, you can run the MML command SET BTSRXUBP to specify whether the TMA is installed on the antenna system, and set the attenuation factor for the TMA. For the NodeB, you can run the MML command ADD ALD to add the TMA for the antenna line device (ALD), run the MML command SET TMAMODE to set the work mode of the TMA, run the MML command SET TMAGAIN to set the gain of the TMA, and run the MML command SET RXATTEN to set the attenuation of the RX channel.
2.107.3.2 Power Supply for TMA

The TMA needs to be powered by the BTS/NodeB through the RF feeder: l For the BTS, RXU board types such as the RRU3008, RRU3908, GRFU, and MRFU can directly provide power for the TMA. The DRFU, however, does not directly provide power for the TMA. Instead, it needs to be installed with a GATM board to provide power for the TMA. You can run the MML command SET BTSRXUBP/SET BTSDATUBP to enable the power switch.
Issue 08 (2011-09-30)
For the NodeB, the ALD provides power for the TMA. You can run the MML command SET ALDPWRSW to enable the power switch.
2.107.3.3 Monitor TMA

The working status of the TMA can be determined according to the status of the feeding current on the TMA. The methods of reflecting the working status of the TMA through the feeding current vary according to TMAs. Users need to configure feeder boards for TMAs according to the actual TMA feature configuration. There are three alarm modes: MODE1 has only one type of alarm whose alarm severity is critical, and the alarm current threshold is fixed and greater than the normal working current; MODE2 has two types of alarms whose alarm severities are critical and warning, and the alarm current is fixed and greater than the normal working current; MODE 3 has two types of alarms whose alarm severities are critical and warning, and the warning alarm current is periodical pulse current, while the critical alarm current is fixed. Figure 2-357 Power supply current chart corresponding to MODE1
Figure 2-358 Power supply current chart corresponding to MODE2
Issue 08 (2011-09-30)
1375
Figure 2-359 Power supply current chart corresponding to MODE3
When the power switch is set to ON, you need to set the current alarm threshold: l l For the BTS, you can run the MML command SET BTSRXUBP/SET BTSDATUBP to set the current alarm threshold. For the NodeB, you can run the MML command SET ALDRPWRSW to set the current alarm threshold.

Users need to determine whether to install the TMA according to the actual project requirements. In a network whose uplink coverage is limited, the TMA can be installed to improve the RX sensitivity and expand the cell radius, thus reducing the number of BTSs and minimizing investments.
2.107.5 Parameters
None.
2.107.6 Counters
None.
2.107.7 Glossary

None.
2.108 Remote Electrical Tilt

2.108.1.1 Scope
The remote electrical tilt (RET, corresponding to MRFD-210602 Remote Electrical Tilt) refers to an antenna system whose tilt is controlled electrically.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the RET feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.108.2 Overview
This document describes a solution for remote adjustment of the antenna tilt.

After an antenna is installed, the tilt of the antenna needs to be adjusted for the purpose of network optimization. With the RET feature, the phases of signals that reach the elements of the array antenna can be adjusted through electrical control, so as to change the vertical pattern of the antenna. The tilt of the RET antenna can be adjusted after the system is powered on and be monitored in real time. In this way, precise adjustment of the antenna tilt can be achieved. The RET feature provides the following benefits:
The RET antennas at more than one site can be remotely adjusted at the same time. Therefore, the efficiency of adjusting the antenna tilt is improved and the cost of network optimization is reduced. The adjustment of RET antennas can be performed irrespective of weather conditions. It is easy to adjust the RET antennas at the sites that are difficult to reach.
l l
The operating principles of RET are described in this chapter.
2.108.3.1 Operating Principles of RET

The tilt of the RET antenna can be adjusted remotely. The phase shifter of the antenna can be controlled by the stepper motor outside or inside the antenna. You can adjust the antenna tilt after the system is powered on and monitor the tilt in real time. Therefore, the precise remote adjustment of the antenna tilt can be achieved. Figure 2-360 shows the operating principles of the RET antenna. Figure 2-360 Operating principles of the RET antenna
The Remote Control Unit (RCU) is the driving motor of the phase shifter of the RET antenna. The RCU receives and executes the control commands from the MBTS to drive the stepper motor. A pulling bar connects the stepper motor and the phase shifter. When the stepper motor is triggered, the pulling bar moves and then the phase of the phase shifter changes through the gears. In this situation, the phase of each element of the array antenna changes regularly. Then, the direction of the main beam of the antenna changes accordingly. Thus, the antenna tilt is adjusted.
2.108.3.2 Operating Principles of Huawei RET

Huawei MBTS supports the following types of RET antenna connection: l Directly connect the RET through multicore cables: It is applicable when the distance between the RRU and the RCU is shorter than 20 meters.
Issue 08 (2011-09-30)
Figure 2-361 DBS Station connect the RET Antenna directly
Connect the RET via SBT: It is applicable when the distance between the RRU and the RCU is longer than 20 meters and the TMA is not used in the system.
Figure 2-362 DBS Station connect the RET Antenna via SBT
Issue 08 (2011-09-30)
1379
Figure 2-363 BTS Station connect the RET Antenna via SBT
Connect the RET together with the STMA: It is applicable when the distance between the RRU and the RCU is longer than 20 meters and the TMA is required by the system.
Figure 2-364 DBS Station connect the RET Antenna together with STMA
Issue 08 (2011-09-30)
1380
Figure 2-365 BTS Station connect the RET Antenna together with STMA
The MBTS supplies the DC power to the stepper motor and communicates with it through the AISG interface on the motor. In the Huawei RET solution, the RET antenna can be controlled remotely or locally through a command sent from the M2000 or LMT respectively. When directly connect the RET through multicore cables, the process of RET antenna control is as follows: 1. 2. The M2000 or LMT issues the control command to the BBU, and then the BBU sends the command to the RRU. The RRU modulates the control command into RS485 signals and then transmits the signals from the RS485 port to the RCU through the control cable.
When connect the RET via the SBT, the process of RET antenna control is as follows: 1. 2. 3. The M2000 or LMT issues the control command to the BBU, and then the BBU sends the command to the RRU. The RRU modulates the control command into On-Off-Keying (OOK) signals and then transmits the signals and the DC power from the RF port to the SBT. The SBT demodulates the OOK signals into RS485 signals and then transmits the signals and part of the DC power to the RCU.
When conect the RET together with STMA, the process of RET antenna control is as follows:
1. 2. 3.
The M2000 or LMT issues the control command to the BBU, and then the BBU sends the command to the RRU. The RRU modulates the control command into OOK signals and then transmits the signals and the DC power from the RF port to the STMA. The STMA demodulates the OOK signals into RS485 signals and then transmits the signals and part of the DC power to the RCU.
The Huawei RET solution supports the RET cascading control. Several cascaded RET antennas can be controlled by the signals coming from the same control cable. The cascading solution helps save the cost of the SBTs.
The Huawei RET solution also supports the 2G/3G RET cascading control. 3G RET antennas can be cascaded with 2G RET antennas. When they are cascaded, the tilts of the 2G RET antennas can be controlled on the OMC for 3G, and the tilts of the 3G RET antennas can also be controlled on the OMC for 2G. The cascading helps save the cost of SBTs and STMAs when the 2G and 3G RET antennas are installed at the same place.
Issue 08 (2011-09-30)
1382
2.108.4 Parameters
None.
2.108.5 Counters
2.108.6 Glossary

None.
2.109 TX Diversity and RX Diversity

2.109.1.1 Scope
This document describes the TX diversity and RX diversity feature and related functions on which TX Diversity and RX Diversity is based, and furthermore provides parameters associated with this feature.


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the TX Diversity and RX Diversity feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.109.2 Overview of TX Diversity and RX Diversity

2.109.2.1 RX Diversity
Radio waves are subject to multipath propagation as a result of reflection and diffraction. The signals on radio channels reach the receiver through multiple paths. If the signals are combined by the receiver, fading can be reduced to a great extent. Receive (RX) diversity is a radio reception technology that aims to reduce signal fading and interference. Based on this technology, multiple frequencies of one signal source or one frequency of multiple receivers and antennas can be monitored. RX diversity can be used to promote the UL receiver performance of the NodeB. When the feature is enabled, one signal is received by multiple antennas. From the signals received by the antennas, the receiver selects signals with relatively great strength and combines them into one
signal, thus reducing the fading. In this manner, better UL receiver sensitivity and expanded UL coverage of the NodeB can be achieved, which decreases the investment cost of operators. RX diversitycapable NodeBs do not require additional equipment to support the feature. The channel resources involved in 2-way RX diversity (MRFD-210604 2-Way Antenna Receive Diversity) are twice the channel resources involved in 1-way reception, and channel resources involved in 4-way RX diversity (WRFD-010209 4-Antenna Receive Diversity) are twice the channel resources involved in 2-way RX diversity.
2.109.2.2 TX Diversity
Transmit (TX) diversity (WRFD-010203 Transmit Diversity) is a technology based on which signals are transmitted to the receiver in space redundancy mode through multiple independent antennas or an antenna array. When the technology is applied, the signal fading can be reduced. In scenarios where NodeBs in TX diversity mode are deployed, signals are transmitted to UEs from different NodeBs or from different antennas of one NodeB. As the signals are not correlated, RAKE RX diversity-capable UEs can receive the signals and combine them together. Thus, the system performance can be significantly improved. TX diversity enables the NodeB to provide twice the quantity of RF DL channel resources compared with a non-TX diversity NodeB, and effectively improves the reception performance of the UE. TX diversity can improve UE performance especially in scenarios where multipath effect is insignificant and the UE moves at a low speed. With TX diversity, the DL capacity and coverage of the NodeB can be remarkably improved when the QoS is ensured. In such cases, the CAPEX and OPEX can be cut down. UEs that are capable of RX diversity are required to implement TX diversity.

2.109.3.1 RX Diversity RAKE Receiver
In WCDMA, channel bandwidth is much higher than the flat fading bandwidth of the channel. The modulation technology in the WCDMA system adopts spreading codes that bear correlation and is different from the modulation technology in other systems that require equalization algorithm to help eliminate interference between symbols. Therefore, the latency spreading that occurs on radio channels is considered as signal retransmission. If the latency between signals on different paths exceeds the length of a chip, the RAKE receiver will consider the signals as irrelevant noises. In such cases, the latency equalization is not required. To efficiently extract useful information from signals on multipaths, the RAKE receiver improves the signal-to-noise ratio (SNR) of the signals by collecting the signals through correlators and combining the signals together. Figure 2-366 shows the operating principle of a RAKE receiver. First, the channel estimator estimates the channel condition using pilot symbols. Then, the phase rotator removes the information of channel condition from the received symbols. Then, the latency equalization compensates for the time-lag between the symbols of the received signals on each path. Finally, the RAKE combiner accumulates the symbols after channel compensation. In this manner, the fading is reduced, and a combined signal accumulated from signals on multipaths is generated. The matched filter shown in Figure 3-1 is used to detect and update the latency information of
the multipaths on the current channel and to ensure that the signal strength of the RAKE receiver always reaches its maximum. Figure 2-366 Operating principle of the RAKE receiver
The RAKE receiver is adopted in WCDMA to receive radio signals. It uses several sub-receivers to individually process signals on multipaths. The signals are individually decoded and then combined together. In this manner, the transport channels are fully utilized, and the multipath fading is reduced. This helps increase the SNR or Eb/No in a multipath environment.
2.109.3.2 TX Diversity
TX diversity in WCDMA is of two types, that is, open loop TX diversity and closed loop TX diversity.
Open Loop TX Diversity

Open loop TX diversity is categorized into Time Switched Transmit Diversity (TSTD) and Space Time Transmit Diversity (STTD). Huawei NodeBs mainly adopt the STTD mode. l Time Switched TX Diversity TSTD applies only to synchronization channels (SCHs). In TSTD, the transmission is switched between different antennas at a specified interval, as shown in Figure 2-367.
Issue 08 (2011-09-30)
1386
Figure 2-367 Transmit structure of SCHs in TSTD mode
In Figure 2-367, Cp indicates Primary Synchronization Code (PSC) and csi,k indicates Secondary Synchronization Codes (SSC), where i (= 0, 1, , 63) indicates number of the scrambling code groups, and k (= 0, 1, , 14) indicates the slot number. In even-numbered slots, both PSC and SSC are transmitted through antenna 1. In odd-numbered slots, both PSC and SSC are transmitted through an antenna 2. TSTD is the simplest TX diversity mode in WCDMA. The manner in which UEs receive TSTD signals in TX diversity scenario is the same as the manner in which UEs receive signals in a non-TX diversity scenario. Thus, the UE needs to detect whether the TSTD is applied. l Space Time TX Diversity STTD uses the space-time block code at the NodeB to reduce deep channel fading. Channel coding, rate matching, and interleaving are performed similar to non-diversity mode. Figure 2-368 and Figure 2-369 show two STTD encoders. In QPSK modulation mode, the STTD encoder works on four symbols, that is, b0, b1, b2, and b3, as shown in Figure 2-368. Figure 2-368 STTD encoder in QPSK modulation mode
In 16QAM modulation mode, STTD works on blocks of eight consecutive symbols, that is, b0, b1, b2, b3, b4, b5, b6, and b7, as shown in Figure 2-369.
Issue 08 (2011-09-30)
1387
Figure 2-369 STTD encoder in 16QAM modulation mode
Closed Loop TX Diversity

In closed loop TX diversity mode, the UE periodically reports the estimated value of optimal transmit power (referred to as feedback in the WCDMA system) on the UL DPCCH, and the NodeB adjusts the TX power based on the feedback and transmits signals at the adjusted TX power. There are two modes in closed loop TX diversity, that is, mode 1 and mode 2. In mode 1, the NodeB adjusts only the phase on the DL physical channel. In mode 2, the NodeB adjusts both the phase and the amplitude on the DL physical channel. Huawei NodeBs mainly adopt mode 1. Figure 2-370 shows the operating principle of closed loop TX diversity. Figure 2-370 Receiver and transmitter in closed loop TX diversity mode
The UE periodically calculates the weights according to the information obtained from pilot signals. The weights are quantified and then sent to the NodeB on the reverse control channel. The NodeB adjusts the TX power according to the feedback weights so that the UE can receive signals at the highest RX power. If the feedback mechanism in closed loop TX diversity mode adequately tracks the conditions of the DL channels, the maximum SNR in closed loop TX diversity mode can be greater than that in STTD mode.
Issue 08 (2011-09-30)
1388
Generally, closed loop TX diversity provides the greatest possible gain when the UE moves at a low speed. Open loop TX diversity, however, boosts the performance of the UE that moves at a high speed and provides less gain when the UE moves at a low speed.

2.109.4.1 RX Diversity
Huawei NodeBs support both RX diversity and non-RX diversity. In RX diversity mode, the NodeB can be configured with 2 antennas (2-way), or 4 antennas (4-way) through the parameter Antenna Magnitude. If Antenna Magnitude is set to 1, non-RX diversity is configured. RX diversity-capable NodeBs do not require additional equipment to support the feature. The channel resources involved in 2-way RX diversity are twice the channel resources involved in 1-way reception, and channel resources involved in 4-way RX diversity are twice the channel resources involved in 2-way RX diversity. The number of RX channels depends on the settings of the antenna connectors on top of the cabinet. l If Antenna Magnitude is set to 1, then the NodeB is in non-RX diversity mode. In this case, only Antenna Channel No.1, the associated cabinet number, and the subrack number need to be set. If Antenna Magnitude is set to 2, then the NodeB is in 2-way RX diversity mode. In this case, Antenna Channel No.1, Antenna Channel No.2, the cabinet number, and the subrack number associated with each antenna need to be set. If Antenna Magnitude is set to 4, then the NodeB is in 4-way RX diversity mode. In this case, Antenna Channel No.1, Antenna Channel No.2, Antenna Channel No.3, Antenna Channel No.4, the cabinet number, and the subrack number associated with each antenna need to be set.
The number of RX antennas is associated with Work Mode, that is, the demodulation mode of NodeB. The following demodulation modes are available: 2-Channel Demodulation Mode (DEM_2_CHAN), 4-Channel Demodulation Mode (DEM_4_CHAN), and Economical 4Channel Demodulation Mode (DEM_ECON_4_ CHAN). In economical 4-channel demodulation mode, signals from UEs that access the network are processed in 2-channel demodulation mode while signals for demodulation are processed in 4channel demodulation mode. NodeBs in economical 4-channel demodulation mode support a maximum coverage radius of 200 km, while NodeBs in 4-channel demodulation mode support a maximum coverage radius of only 30 km.
2.109.4.2 TX Diversity STTD

The parameter STTD support indicator is used to specify whether a cell supports STTD. If a cell is configured to support the STTD mode, ensure that the associated local cell on the NodeB side supports TX diversity. The parameter STTD indicator specifies whether the SCCPCH supports STTD.
Closed Loop TX Diversity

The parameter CP1 support indicator is used to specify whether a cell supports closed loop TX diversity mode 1 (CP1). If a cell is configured to support the CP1 mode, ensure that the
associated local cell on the NodeB side supports TX diversity. If the cell supports the TX diversity mode, set DPCH Tx Diversity Mode and FDPCH Tx Diversity Mode to specify the preferential TX diversity modes adopted on the DPCH and HS-PDSCH, as these two physical channels support both STTD and CP1. l l DPCH Tx Diversity Mode indicates the preferential TX diversity mode for the DPCH. FDPCH Tx Diversity Mode indicates the preferential TX diversity mode for the HSPDSCH.
In the case of closed loop TX diversity, 3GPP defines two modes of reporting closed loop feedback information, that is, j+1 and j+2. The modes are set through the parameters: Closed loop time adjust mode. l l In j+1 mode, the feedback information of timeslot j is reported after (j+1) mod15 timeslots. In j+2 mode, the feedback information of timeslot j is reported after (j+2) mod15 timeslots.
2.109.5 Parameters
None.
2.109.6 Counters
2.109.7 Glossary

None.
2.110 BTS/NodeB Clock

2.110.1.1 Scope
This document describes the functions, types, and parameter meanings of the BTS/NodeB clock (MRFD-210501 BTS/NodeB Clock).

It is assumed that users of this document are familiar with GSM/UMTS basics and have a working knowledge of GSM/UMTS telecommunication. This document is intended for:
l l
Personnel working on Huawei GSM/UMTS products or systems System operators who need a general understanding of this feature

The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BTS/NodeB Clock feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.110.2 Overview
The synchronization of the MBTS clock provides the basis for the frame synchronization. The MBTS obtains the reference clock source through the clock synchronization for the internal frame synchronization. The MBTS supports three clock synchronization modes: synchronization with the Abis/lub clock, synchronization with the GPS clock, and synchronization with the BITS clock. In addition, the MBTS internal clock can work in free-run mode to temporarily provide a stable reference clock source for the MBTS. In compliance with the 3GPP specifications, the frequency stability of the master clock of the MBTS must be between 0.05 ppm and +0.05 ppm. The MBTS can work in multiple clock synchronization modes to adapt to different clock networking modes. The MBTS supports three clock synchronization modes: synchronization with the Abis clock, synchronization with the GPS clock, and synchronization with the BITS clock. In addition to the preceding three synchronization modes, the MBTS internal clock can work in free-run mode. The Oven Controlled X-tal Oscillator (OCXO) with a high precision works as the master clock of the MBTS. The OCXO can ensure the normal operation of the MBTS for up to 90 days. The internal clock can be synchronized with the transmission network without using the auxiliary equipment, thus reducing the cost. In addition, the precision of the synchronized clock meets the requirements for the radio transmission network and frequencies. The internal clock can be synchronized with the transmission network without using the auxiliary equipment, thus reducing the cost. In addition, the precision of the synchronized clock meets the requirements for the radio transmission network and frequencies.

2.110.3.1 Synchronization with the Abis/lub Clock
The clock source of the MBTS is synchronized with the line clock sources of its upper-level NE such as the MBSC. The synchronization with the Abis clock (also termed the BSC tracing clock) is enabled by setting Clock Type to TRCBSC_CLK(Trace BSC Clock). In this clock synchronization mode, the BTS receives the clock signals from the NE at the upper layer from the E1/T1 port (this mode is supported only in E1/T1 transmission mode). The number of the E1/T1 port need not be configured because the BTS obtains the clock signals from the E1/T1 port where the OML is configured for the BTS clock synchronization.
2.110.3.2 Synchronization with the GPS Clock

The synchronization with the GPS clock is enabled by setting Clock Type to TRCGPS_CLK. In this clock synchronization mode, the GPS clock serves as the clock source of the BTS, and a GPS satellite card is required. In the case of a DBS3900/BTS3900/BTS3900A, the USCU needs to be configured and the parameter Board Parameter Configuration Enabled must be set to YES(YES). The meanings of the parameters relevant to this clock synchronization mode are as follows: GPS or Glonass: Specifies whether the GPS clock or the Glonass clock serves as the clock source when two satellite cards are used. GPS Antenna Delay: Specifies the length of the feeder cable, which connects the GPS satellite card and the antenna. The actual delay of the signals transmitted on the feeder can be calculated according to the length of the feeder cable, thus improving the timing accuracy of the GPS satellite card. Antenna Power Supply Switch: Specifies whether to supply power to the GPS antenna. When the GPS antenna requires the power supply, this parameter is set to SENDPOWER(Send Power). When the GPS antenna does not require the power supply, this parameter is set to NOPOWER(No Power). The GPS clock signals are processed and synchronized as follows: The GPS antenna receives the GPS satellite signals at 1575.42 MHz and then sends the signals to the GPS satellite card. After processing the signals, the GPS satellite card sends the signals from the USCU to the main control board of the BTS. The main control board then synchronizes the clock signals with the BTS clock signals. A GPS antenna can simultaneously trace up to eight satellites.
2.110.3.3 Synchronization with the BITS Clock

The synchronization with the BITS clock is enabled by setting Clock Type to TRCGPS_CLK. In this clock synchronization mode, the external BITS clock serves as the clock source of the BTS. In the case of a DBS3900/BTS3900/BTS3900A, the USCU must be configured. The BITS clock signals are processed and synchronized as follows:
The BITS clock output port is connected to the BITS clock input port on the USCU. The master clock module of the BTS performs phase locking and frequency dividing to the received clock signals so that the input clock signals become the signals required by the BTS.
2.110.4 Parameters
This chapter describes the parameters related to the BTS/NodeB Clock feature. For the meaning of each parameter, see Table 2-263. For the default value, value ranges, and MML commands of each parameter, see Table 2-264. Table 2-263 Parameter description (1) Parameter Clock Type Description Clock mode of the BTS. If this parameter is set to INT_CLK, the BTS does not track any external clock. The internal high precision clock works in free-run mode. If this parameter is set to TRCBSC_CLK, the BTS tracks the clock signals received from the BSC. If this parameter is set to EXCLK, the BTS tracks the clock signals received from the external input clock. If this parameter is set to IP_TIME, the BTS shakes hands through the IP network with the IP clock server for synchronization. If this parameter is set to IP_TRANSFER, the BTS extracts the clock from an E1 when there is not an IP clock after the BTS upgrades the transmission mode from E1 transmission to IP transmission. If this parameter is set to TRCGPS_CLK, the BTS extracts the clock through the DGPS from the GPS. If this parameter is set to UM_CLK, the BTS keeps pace with the signals broadcast on the downlink main BCCH of a neighboring BTS. If this parameter is set to PEER_CLK, the multimode BTS(GSM) keeps pace with the signals that the other mode offer. Whether to allow the configuration of alarm parameters. The value ""YES"" indicates that the configuration is allowed, and the value ""NO"" indicates that the configuration is not allowed. If the parameter is set to ""YES"", all the other parameters are reset to the default values in this command. In multi-mode scenario, the value of this parameter in one mode must be the same as the value of the corresponding parameter in another mode. Synchronization clock adopted when two satellite cards are used together. GPS:Trace GPS only. GLONASS:Trace GLONASS only. GPSGlonass:Trace GPS and GLONASS. Length of the feeder cable. The GPS satellite card is connected to the antenna through feeder cables. The transmission delay on the feeder cable can be calculated on the basis of the length of the feeder cable, thus increasing the timing accuracy of the satellite card. Power supply switch of the GPS antenna feeder
GPS or Glonass
GPS Antenna Delay
Antenna Power Supply Switch
Issue 08 (2011-09-30)
1393
Table 2-264 Parameter description (2) Paramet er Clock Type Default Value None GUI Value Range INT_CLK (Internal Clock), TRCBSC_CLK (Trace BSC Clock), EXTSYN_CLK (External Sync clock), IP_TIME (IP Clock), IP_TRANSFER (Trace Transport Clock), TRCGPS_CLK (Trace GPS Clock), UM_CLK (Um Clock), PEER_CLK(Peer Clock) Actual Value Range INT_CLK , TRCBSC _CLK, EXTSYN _CLK, IP_TIME, IP_TRAN SFER, TRCGPS _CLK, UM_CLK , PEER_CL K MML Comman d SET BTSCLK (Mandator y) Impa ct BTS
Unit None
Issue 08 (2011-09-30)
1394
Paramet er Board Paramete r Configur ation Enabled
Default Value None
Actual Value Range YES,NO
Unit None
MML Comman d SET BTSFMU ABP (Mandator y) SET BTSNFCB BP (Mandator y) SET BTSPMU BP (Mandator y) SET BTSAPM UBP (Mandator y) SET BTSDATU BP (Mandator y) SET BTSDEM UBP (Mandator y) SET BTSDHEU BP (Mandator y) SET BTSDOM UBP (Mandator y) SET BTSDPM UBP (Mandator y) SET BTSDTM UBP (Mandator y) SET BTSPSUF P (Mandator y) SET BTSDDPU BP (Mandator
Impa ct BTS
Issue 08 (2011-09-30)
1395
Paramet er
Default Value
GUI Value Range
Actual Value Range
Unit
MML Comman d y) SET BTSUSCU BP (Mandator y)
Impa ct
GPS or Glonass
GPS
GPS(GPS), GLONASS (Glonass), GPSGlonass (GPSGlonass)
GPS, GLONAS S, GPSGlon ass
None
SET BTSDGPS BP (Optional) SET BTSUSCU BP (Optional)
BTS
GPS Antenna Delay
0~1000
0~1000
BTS
Antenna Power Supply Switch
NOPOWER
SENDPOWER (Send Power), NOPOWER(No Power)
SENDPO WER, NOPOW ER
None
BTS
2.110.5 Counters
None.
2.110.6 Glossary

None.
2.111 BSC/RNC Clock

2.111.1.1 Scope
This document describes the types, synchronous system structure, and RFN generation process of the BSC/RNC clock (MRFD-210502 BSC/RNC Clock).


The change history provides information on the changes between different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BSC/RNC Clock feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.111.2 Overview
The BSC/RNC clock supports five types of clock sources. All the clock sources support 1+1 backup, clock source management, clock status query, and line clock maintenance. The clock
source backup function can eliminate the impact on the services when the primary clock becomes invalid.

2.111.3.1 Overview
The BSC/RNC clock provides reliable clock sources for the BSC/RNC to meet the requirements of the clock precision defined in the 3GPP specifications. Every type of clock source supports 1+1 backup. The BSC/RNC clock subsystem consists of the clock processing board GCUa/GCGa and the clock processing unit in each subrack. The external reference clock signals are transmitted to the GCUa/GCGa. After a phase lock on the GCUa/GCGa, the clock signals are changed to 8 KHz clock signals. The signals are then transmitted to the SCUa in the same subrack through the backplane and to the SCUa in the EPS through clock signal cables. Then, the 8 KHz clock signals on the SCUa are transmitted to other boards in the same subrack through the backplane. When the clock source is faulty, the BSC/RNC reports the related alarms and starts the 1+1 backup scheme to ensure the normal operation of the system. The BSC/RNC clock sources are as follows: l BITS clock BITS clock is categorized into the following types: 2 MHz, 2 Mbit/s, and 1.5 Mbit/s clocks. The 2 MHz and 2 Mbit/s clocks use E1 clock signals, whereas the 1.5 Mbit/s clock uses T1 clock signals. BITS clock has two input modes, that is, BITS0 and BITS1. The two input modes correspond to the two input ports (CLKIN0 and CLKIN1) on the GCUa/GCGa. The parameters REF2MCLKSW1 and REF2MCLKSW2 are used to enable the switch of 2M BITS clock. l Line clock extracted from the A/Iu interface The line clock signals are transmitted to the GCUa/GCGa through the A/Iu interface and are changed to 8 kHz clock signals. Then, clock signals are transmitted to the GCUa/GCGa through the backplane in the MPS. The clock signals have two input modes, that is, LINE0 and LINE1. The parameters BACK8KCLKSW1 and BACK8KCLKSW2 are used to enable the switch of backplane LINE clock. l GPS clock The GPS clock uses the 1PPS signals extracted from the global positioning system (GPS). The GCGa is embedded with the GPS card. Through the satellite antenna interface on the GCGa, clock signals can be received from the GPS. l 8 kHz clock provided by the external clock source The 8 kHz standard clock is obtained from the external device through the COM1 port on the GCUa/GCGa. l Clock generated by the local oscillator The BSC uses the clock generated by the local oscillator if no clock is configured. You can run the MML command ADD CLKSRC to configure the parameter SRCT to set the clock source type. The BSC/RNC has the clock control setting functions such as the clock source management, clock status query, and line clock maintenance. The BSC/RNC uses only clock source
during operation. The clock source has three operating modes, that is, automatic mode, manual mode, and self-oscillation mode. l Automatic mode Users need not specify the clock source. The system can automatically select the clock source with the highest priority. l Manual mode Users need to specify the clock source and the system cannot automatically switch the clock source to other clock sources (even if the current specified clock source is faulty). l Self-oscillation mode The self-oscillation mode is the initial operating mode of the BSC/RNC clock. You can run the MML command SET CLKMODE to configure the parameter MODE to set the clock mode.
2.111.3.2 BSC/RNC Synchronization System Structure

The clock synchronization system consists of the clock board, subrack backplane, inter-subrack clock cables, and clock module of each board. Figure 2-371 shows the structure of the clock synchronization system. Figure 2-371 Structure of the clock synchronization system
The clock board of the BSC6900 consists of the GCUa and GCGa. The BSC6900 can configure either the GCUa or the GCGa according to the clock type. You can run the MML command SET CLKTYPE to configure the parameter CLKTYPE to set the type of a clock board. If the interface board where clock signals are extracted from the CN is in the MPS, clock signals can be directly transmitted to the clock board through LINE0/LINE1 on the backplane in the MPS or through the 2 MHz clock output port (using the clock signal cable) on the panel of the interface board.
If the interface board where clock signals are extracted from the CN is in the EPS, clock signals can be transmitted to the clock board in the MPS through only the 2 MHz output port on the panel of the interface board. If the interface board where clock signals are extracted from the CN is in the TCS, clock signals are transmitted to the Ater interface board through the backplane, and transmitted to the Ater interface board in the MPS through the inter-subrack cable of the Ater interface, and then transmitted to the clock board through the channels on the backplane in the MPS. When the CS clock and PS clock are not obtained from the same clock source, the Gb interface board can extract clock signals either from the backplane in the subrack or from the CN side provided that the BSC6900 is configured with the Gb interface board. When extracting clock signals from the CN side, the Gb interface board cannot be shared by other interfaces. If the CS clock and the PS clock have different clock sources, the parameter REFUSELOCALCLK need to be set to YES, and then the CS clock can use the clock source of the PS clock. Figure 2-372 shows the clock cable connections between the clock board in the MPS and the SCUa in the EPS when the BSC6900 is configured with the active and standby clock boards and active and standby SCUa boards. Figure 2-372 Structure of the clock synchronization system
The active and standby clock boards in the MPS are connected to the active and standby SCUa boards in the EPS through the Y-shaped clock cable. This connection mode can ensure the normal operation of the system clock even if the single-point failure occurs among the clock cable, Yshaped clock cable, and SCUa. In addition, the Y-shaped clock cable can ensure the normal operation of the SCUa when the active and standby clock boards are switched over. In the MPS, clock signals are transmitted from the clock board to the SCUa in the subrack through the channels on the backplane. In this case, the Y-shaped clock cable is not required.
2.111.3.3 RFN Generation Process

The RNC frame number (RFN) is used for the RNC node synchronization. The RFN is contained in the node synchronization frame that the RNC sends to the NodeB. Figure 2-373 shows the RFN generation and reception process and takes the GCUa as an example.
Issue 08 (2011-09-30)
1400
Figure 2-373 RFN generation and reception process
The GCUa/GCGa in the MPS transmits 1PPS signals and time synchronization packets to the SCUa boards in this subrack and other subracks, and then transmits signals to other boards in the subrack through the SCUa. The boards generate the required RFN signals according to the received 1PPS signals and time synchronization packets. 1PPS signals can be generated on the GCUa/GCGa. If the clock board is the GCGa, GPS signals can be extracted from the GPS card to generate 1PPS signals that are synchronous with the satellite signals.

2.111.4.1 Configuration of GPS Clock Source
If the clock source is the GPS, the GCUa must be configured. The clock source configuration command is as follows: ADD CLKSRC: SRCGRD=3, SRCT=GPS; The GCUa configuration command is as follows: SET CLKTYPE: CLKTYPE=GCUa
2.111.4.2 Configuration of Gb Interface Clock

In special 2G networking scenarios, if the CS clock is not synchronized with the PS clock, the Gb interface clock needs to be configured as the SGSN node-locked clock. The configuration command is as follows:
SET CLK: SRT=MPS, SN=0, BT=PEUa, REF2MCLKSRC=0, REF2MCLKSRCBAK=0, REFUSELOCALCLK=YES;

NOTE
Only the PEUa whose logical type is FR supports the local clock.
2.111.5 Parameters
The following describes the parameters related to BSC/RNC Clock feature. Table 2-265 Parameter description Parameter ID REF2MCLK SW1 NE BSC690 0 MML SET CLK (Optional) Description Meaning: Switch of panel BITS1(2M) GUI Value Range: OFF(OFF), ON(ON) Actual Value Range: OFF, ON Unit: None Default Value: OFF REF2MCLK SW2 BSC690 0 SET CLK (Optional) Meaning: Switch of panel BITS2(2M) GUI Value Range: OFF(OFF), ON(ON) Actual Value Range: OFF, ON Unit: None Default Value: OFF BACK8KCL KSW1 BSC690 0 SET CLK (Optional) Meaning: Switch of backplane LINE1 GUI Value Range: OFF(OFF), ON(ON) Actual Value Range: OFF, ON Unit: None Default Value: OFF BACK8KCL KSW2 BSC690 0 SET CLK (Optional) Meaning: Switch of backplane LINE2 GUI Value Range: OFF(OFF), ON(ON) Actual Value Range: OFF, ON Unit: None Default Value: OFF
Issue 08 (2011-09-30)
1402
Parameter ID SRCT
NE BSC690 0
MML ADD CLKSRC (Mandatory)
Description Meaning: Type of the clock source. GUI Value Range: BITS1-2MHZ(2MHZ Building Integrated Timing Supply system 1), BITS2-2MHZ(2MHZ Building Integrated Timing Supply system 2), BITS1-2MBPS (2MBPS Building Integrated Timing Supply system 1), BITS2-2MBPS(2MBPS Building Integrated Timing Supply system 2), 8KHZ (8KHZ), GPS(Globe Positioning System), LINE1_8KHZ(8KHZ line1), LINE2_8KHZ (8KHZ line2), BITS1-T1BPS(T1BPS Building Integrated Timing Supply system 1), BITS2-T1BPS(T1BPS Building Integrated Timing Supply system 2) Actual Value Range: BITS1-2MHZ, BITS2-2MHZ, BITS1-2MBPS, BITS2-2MBPS, GPS, 8KHZ, LINE1_8KHZ, LINE2_8KHZ, BITS1-T1BPS, BITS2-T1BPS Unit: None Default Value: None
MODE
BSC690 0
SET CLKMODE (Mandatory)
Meaning: Working mode of the system clock. Working modes of the system clock are as follows: (1) MANUAL: In this mode, you must specify a clock source and prevent the switching of the clock source. (2) AUTO: In this mode, you do not need to specify a clock source and the system automatically selects the clock source with the highest priority. (3) FREE: In this mode, the crystal oscillator of GCU board is used. GUI Value Range: MANUAL(Manual Handover), AUTO(Auto Handover), FREE (Free-run) Actual Value Range: MANUAL, AUTO, FREE Unit: None Default Value: AUTO
CLKTYPE
BSC690 0
SET CLKTYPE (Mandatory)
Meaning: Type of the clock board GUI Value Range: GCUa, GCGa Actual Value Range: GCUa, GCGa Unit: None Default Value: None
Issue 08 (2011-09-30)
1403
Parameter ID REFUSELO CALCLK
NE BSC690 0
MML SET CLK (Optional)
Description Meaning: Whether to use SGSN clock source.Only the Gb interface board needs to set this parameter. If the SGSN clock and the MSC clock have different clock sources, the MSC clock must use the clock source of the SGSN clock. If the two clocks use the same clock source, this parameter does not need to be set. GUI Value Range: NO(NO), YES(YES) Actual Value Range: NO, YES Unit: None Default Value: NO
2.111.6 Counters
None.
2.111.7 Glossary

None.
2.112 14.4 Kbps Circuit Switched Data

2.112.1.1 Scope
This document describes the 14.4 kbit/s circuit switched data feature.

Issue 08 (2011-09-30)


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the 14.4 Kbps Circuit Switched Data feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.112.2 Overview
Carrying data services in the CS domain enables operators to provide more services and increase the revenue. Huawei GSM BSS supports the transfer of PS services on individual speech channels with a high rate of 14.4 kbit/s for transparent data services or 14.5 kbit/s for non-transparent data services. This rate is higher than the common rate of Circuit Switched Data (CSD) services. In this manner, the user experience is improved.

To support this feature, the MSC must support the data service of 14.4 kbit/s on a single timeslot. On the BSC side, select NT14.5K and T 14.4K from the Data service Allowed parameter to support 14.5 kbit/s non-transparent data services and 14.4 kbit/s transparent data services. When an MS initiates a CSD service at a rate of 14.4 kbit/s, the MSC notifies the BSC about the service in the assignment message. The BSC then assigns a TCHF to the MS for the call.
2.112.4 Parameters
This chapter describes the parameters related to 14.4 kbit/s Circuit Switched Data. For the description of each parameter, see Table 2-266. For the default value, value ranges, and MML commands of each parameter, see Table 2-267.
Table 2-266 Parameter description (1) Parameter Data Service Allowed Description Data service supported by the BSC6900. You can set this parameter according to actual requirements.
Table 2-267 Parameter description (2) Paramet er Data Service Allowed Default Value NT14_5K-0 &NT12K-1 &NT6K-1& T14_4K-0& T9_6K-1&T 4_8K-1&T2 _4K-1&T1_ 2K-0&T600 _BITS-0&T 1200_75-0 GUI Value Range NT14_5K~0 NT12K~1 NT6K~2 T14_4K~3 T9_6K~4 T4_8K~5 T2_4K~6 T1_2K~7 T600_BITS~ 8 T1200_75 Actual Value Range NT14_5K, NT12K, NT6K, T14_4K, T9_6K, T4_8K, T2_4K, T1_2K, T600_BIT S, T1200_75 MML Command SET GCELLOTH EXT (Optional) Impac t Cell
Unit None
2.112.5 Counters
2.112.6 Glossary

l l l l l l l
Issue 08 (2011-09-30)
3GPP TS 48.020: Rate adaption on the Base Station System - Mobile-services Switching Centre (BSS-MSC) interface 3GPP TS 48.008: Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification 3GPP TS 44.021 Rate adaption on the Mobile Station - Base Station System (MS-BSS) interface BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM MML Reference BSC6900 GSM Parameter Reference
2.113 Guaranteed Emergency Call

2.113.1.1 Scope
This document describes Guaranteed Emergency Call feature of Huawei Global System for Mobile communications (GSM) Base Station Subsystem (BSS).


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Guaranteed Emergency Call feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-12)
2.113.2 Overview
The emergency call service is of great importance to subscribers in emergencies. As defined in 3GPP, the emergency call services are statutory and mandatory in most networks. An emergency
call takes precedence over a common call. A priority mechanism is implemented to provide fast and reliable access of emergency calls even when the network has a heavy load. In some special situations such as earthquake, tsunami, or flood, the network may be congested. Therefore, the emergency call services may not be guaranteed owing to insufficient resources. The emergency call guarantee feature is the enhancement of the emergency call feature. With the emergency call guarantee feature, the success rate of setting up emergency calls is improved to the greatest extent. Thus, provision of communications is ensured during disaster relief activities. The following mechanisms are implemented to provide the emergency call guarantee feature: l l Preferentially assigning TCH/F to emergency calls in the immediate assignment phase Resource reservation and preemption

2.113.3.1 Preferentially Assigning TCH/F in the Immediate Assignment Phase
To ensure that the MS originates an emergency call in the shortest duration, it is recommended that the BSC assign the TCH/F to the MS as early as possible. In the immediate assignment phase, the MS that originates an emergency call sends the Channel Request message to the BTS. The value of the Establishment Cause IE in the message is Emergency Call. If there is an idle TCH/F, the BSC preferentially assigns the TCH/F to the MS for emergency call. In the assignment phase, upon receiving the Assignment Request message from the MSC, the BSC changes the TCH/F used for signaling to a real TCH through the Mode Modify command. Figure 2-374 shows the process of preferentially assigning TCH/F.
Issue 08 (2011-09-30)
1408
Figure 2-374 Process of preferentially assigning TCH/F
2.113.3.2 Resource Reservation and Preemption

If there is no TCH/F available for the emergency call in the immediate assignment phase, the BSC assigns an SDCCH to the MS. To ensure that the emergency call has TCH/F in the assignment phase, the BSC reserves TCH/ F for the MS or allows the MS to preempt the resources seized by the call with a lower priority. When the value of parameter Max Channel Num Reserved for EC is greater than 0, the BSC reserves TCH/F for the emergency call. When the value of parameter Emergency Call Preemption Permitted is ON, the BSC allows the MS to preempt the resources seized by the call with a lower priority. The number of TCHs/TCFs reserved for emergency calls cannot exceed the value of Max Channel Num Reserved for EC. l TCHs that are normally released If a TCH/F is normally released when the MS applies for TCH/F in the assignment phase, the BSC assigns the TCH/F to the MS for emergency call. l Preempted TCHs for the call with a low priority If there is no TCH/F available for the emergency call in the assignment phase, upon receiving the Establish Indication message, the BSC determines whether to allow the MS to preempt the TCH/F from low-priority calls according to the setting of Emergency Call Preemption Permitted.
When the timer Timer of Reserved TCH for EMC expires, the reserved TCHs that are not assigned to the emergency call are released for normal services. In this manner, normal services are not affected. It is advised that the value of Max Channel Num Reserved for EC should not be set to a very great value.
2.113.4 Dependency
l l l The Guaranteed Emergency Call feature is license-controlled. When no TCH is available, emergency calls can preempt resources of low-priority subscribers only when their resources can be preempted. The MSC must be enabled with the eMLPP function.
2.113.5 Parameters
This chapter describes the parameters related to guaranteed emergency call. For the description of each parameter, see Table 2-268. For the default value, value ranges, and MML commands of each parameter, see Table 2-269. Table 2-268 Parameter description (1) Parameter Emergency Call Preemption Permitted Priority of Emergency Call Description If this parameter is set to ON, the BSC initiates a TCHF preemption when receiving a link establishment indication from an MS in an emergency call. Priority level of an emergency call. If this parameter is set to 15, the functions of reserving TCHs for emergency calls and preempting TCHs are not enabled. If the two functions need to be enabled, set this parameter to a value from 1 to 14. If the value of "Emergency Call Preemption Permitted" is ON, this parameter can also be used for TCH preemption. The value 1 means the highest priority and 14 means the lowest. Maximum number of TCH channels reserved for emergency call users. The TCHs reserved for the emergency call are assigned to the user during the service assignment. If the TCHs are not assigned to the emergency call within a period, the TCHs are released from the reservation queue.
Max Channel Num Reserved for EC Timer of Reserved TCH for EMC
Issue 08 (2011-09-30)
1410
Table 2-269 Parameter description (2) Default Value OFF GUI Value Range OFF(Off), ON(On) Actual Value Range OFF, ON Uni t Non e MML Command SET GCELLCC AD (Optional) SET GCELLCC AD (Optional) SET GCELLCH MGBASIC (Optional) SET GCELLTM R(Optional)
Parameter Emergency Call Preemption Permitted Priority of Emergency Call
Impact Cell
15
1~15
1~15
Non e
Cell
Max Channel Num Reserved for EC Timer of Reserved TCH for EMC
0~190
0~190
Non e
Cell
15
1~30
1~30
Cell
2.113.6 Counters
2.113.7 Glossary

l l l 3GPP TS 44.018 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol 3GPP TS 44.018 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol 3GPP TS 48.008 Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification
2.114 BTS GPS Synchronization

2.114.1.1 Scope
This document describes the principles and data configuration regarding clock synchronization between the BTS and the Global Positioning System (GPS).


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BTS GPS Synchronization feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.114.2 Overview
The GPS is a round-the-clock satellite navigation system that communicates with a BTS in wireless mode. The GPS provides accurate three-dimensional location, velocity, and time for worldwide users. The BTS GPS Synchronization feature enables a BTS clock to be synchronized with the GPS clock source. After the BTS is synchronized with the GPS, the error of the frame synchronization over the Um interface is smaller than one bit. Therefore, the frequency utilization is increased and the interference is decreased in the wireless network.

To receive GPS clock signals, the DBS3900, BTS3900, and BTS3900A must be configured with a Universal Satellite card and Clock Unit (USCU) to provide external time synchronization source for the GTMU so as to implement clock synchronization over the entire network.
The GPS antenna receives the GPS satellite signals at a rate of 1575.42 MHz and then transmits them to the GPS card. The GPS card processes the signals to obtain the GPS absolute time and precise 1PPS pulse signals. The BTS clock circuit traces the 1PPS pulse signals to obtain the reference clock and then obtains various clock signals based on the reference clock. The USCU transmits the various clock signals to the GTMU. The GTMU then uses the clock signals to implement clock synchronization of the BTS. Each BTS in the network adjusts the frame number based on the absolute frame number calculated from the GPS absolute time that is received by the BTS software.

To ensure the normal operation of the USCU, the parameter Board Parameter Configuration Enabled must be set to YES(Yes) to enable the parameter configuration of the USCU. If the parameter GPS or Glonass is set to GPS(GPS), the BTS traces the GPS clock signals. The parameter Antenna Power Supply Switch specifies whether to turn on the power supply switch of the GPS antenna. If the GPS antenna requires power supply, this parameter needs to be set to SENDPOWER(Send Power). If the GPS antenna does not require power supply, this parameter needs to be set to NOPOWER(No Power). Currently, the GPS antennas of all Huawei BTSs do not support power supply. The parameter GPS Antenna Delay specifies the length of a GPS feeder. The GPS card is connected to the antenna through the GPS feeder. The transmission delay over the feeder can be evaluated on the basis of the length of the GPS feeder. This helps to improve the time accuracy of the GPS card. After the parameters related to the USCU are set, the clock trace mode of the BTS needs to be modified so that the USCU of the BTS can perform GPS clock synchronization. If the parameter Clock Type is set to TRCGPS_CLK(Trace GPS Clock),the BTS extracts the clock signals from the GPS through the DGPS.
2.114.5 Parameters
This chapter describes the parameters related to BTS GPS Synchronization. For the description of each parameter, see Table 2-270. For the default value, value ranges, and MML commands of each parameter, see Table 2-271. Table 2-270 Parameter description (1) Parameter GPS or Glonass Description Synchronization clock adopted when two satellite cards are used together. GPS:Trace GPS only. GLONASS:Trace GLONASS only. GPSGlonass:Trace GPS and GLONASS. Length of the feeder cable. The GPS satellite card is connected to the antenna through feeder cables. The transmission delay on the feeder cable can be calculated on the basis of the length of the feeder cable, thus increasing the timing accuracy of the satellite card. Power supply switch of the GPS antenna feeder. In multi-mode scenario, the value of this parameter in this mode must be the same as the value of the corresponding parameter in another mode.
1413
GPS Antenna Delay
Antenna Power Supply Switch Board Parameter Configuration Enabled
Issue 08 (2011-09-30)
Parameter Clock Type
Description Clock mode of the BTS. If this parameter is set to INT_CLK, the BTS does not track any external clock. The internal high precision clock works in free-run mode. If this parameter is set to TRCBSC_CLK, the BTS tracks the clock signals received from the BSC. If this parameter is set to EXCLK, the BTS tracks the clock signals received from the external input clock. If this parameter is set to IP_TIME, the BTS shakes hands through the IP network with the IP clock server for synchronization. If this parameter is set to IP_TRANSFER, the BTS extracts the clock from an E1 when there is not an IP clock after the BTS upgrades the transmission mode from E1 transmission to IP transmission. If this parameter is set to TRCGPS_CLK, the BTS extracts the clock through the DGPS from the GPS. If this parameter is set to UM_CLK, the BTS keeps pace with the signals broadcast on the downlink main BCCH of a neighboring BTS. If this parameter is set to PEER_CLK, the multimode BTS(GSM) keeps pace with the signals that the other mode offer.
Table 2-271 Parameter description (2) Paramet er GPS or Glonass Default Value GPS GUI Value Range GPS (GPS), GLONAS S (Glonass), GPSGlon ass (GPSGlon ass) 0~1000 Actual Value Range GPS, GLONASS, GPSGlonass MML Command SET BTSDGPS BP (Optional) SET BTSUSCU BP (Optional) SET BTSDGPS BP (Optional) SET BTSUSCU BP (Optional)
Unit None
Impact BTS
GPS Antenna Delay
0~1000
BTS
Issue 08 (2011-09-30)
1414
Paramet er Antenna Power Supply Switch
Default Value NOPOW ER
GUI Value Range SENDPO WER (Send Power), NOPOW ER(No Power)
Actual Value Range SENDPOWE R, NOPOWER
Unit None
MML Command SET BTSDGPS BP (Optional) SET BTSUSCU BP (Optional)
Impact BTS
Issue 08 (2011-09-30)
1415
Paramet er Board Paramete r Configur ation Enabled
Default Value None
Actual Value Range NO, YES
Unit None
MML Command SET BTSFMUA BP (Mandatory ) SET BTSNFCB BP (Mandatory ) SET BTSPMUB P (Mandatory ) SET BTSAPMU BP (Mandatory ) SET BTSDATU BP (Mandatory ) SET BTSDEMU BP (Mandatory ) SET BTSDHEU BP (Mandatory ) SET BTSDOMU BP (Mandatory ) SET BTSDPMU BP (Mandatory )
Impact BTS
Issue 08 (2011-09-30)
1416
Paramet er
Default Value
GUI Value Range
Actual Value Range
Unit
MML Command SET BTSDTMU BP (Mandatory ) SET BTSPSUFP (Mandatory ) SET BTSDDPU BP (Mandatory ) SET BTSUSCU BP (Mandatory )
Impact
Issue 08 (2011-09-30)
1417
Paramet er Clock Type
Default Value None
GUI Value Range INT_CLK (Internal Clock), TRCBSC _CLK (Trace BSC Clock), EXTSYN _CLK (External Sync clock), IP_TIME (IP Clock), IP_TRAN SFER (Trace Transport Clock), TRCGPS _CLK (Trace GPS Clock), UM_CLK (Um Clock), PEER_CL K(Peer Clock)
Actual Value Range INT_CLK, TRCBSC_CL K, EXTSYN_CL K, IP_TIME, IP_TRANSF ER, TRCGPS_CL K, UM_CLK, PEER_CLK
Unit None
MML Command SET BTSCLK (Mandatory )
Impact BTS
2.114.6 Counters
2.114.7 Glossary

l l
Issue 08 (2011-09-30)
BSC6900 Feature List BSC6900 Optional Feature Description

l l l
GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference
2.115 BTS Test Function

2.115.1.1 Scope
BTS test involves site test, baseband test, baseband idle timeslot test, TCH loopback test, transmission performance test, cyclic redundancy check (CRC), and BTS antenna fault detection.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BTS Test Function feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.115.2 Overview
All operators are concerned about a quick and easy location of BTS problems and faulty BTS modules. The OMC at the local end provided by Huawei BSS enables local BTS test, and the OMC at the remote end enables remote and centralized BTS test. This facilitates not only the BTS installation and commissioning at the local end, but also the BTS remote management through the NMS and OMC. BTS test involves site test, baseband test, baseband idle timeslot test, TCH loopback test, transmission performance test, CRC, and BTS antenna fault detection.

2.115.3.1 Site Test
In the site test, the board hardware is tested. The boards can be TMU board, TRX, and CDU. The hardware test enables early detection and recovery of hardware failure.
2.115.3.2 Baseband Test

Baseband test involves BIU loopback test and TRX self-test. In the BIU loopback test, the timeslot transmission of the TRX signaling channel on the BTS DBUS is tested. The TRX sends the signaling channel data to the signaling timeslot of the BTS DBUS. After the loopback through the TMU, the TRX receives the data sent by the TRX itself. The TRX compares the data with the original data, and then reports the BER to obtain the link quality of the signaling channel on the BTS DBUS. In the TRX self-test, the running status of the TRX is tested.
2.115.3.3 Baseband Idle Timeslot Test

During the network optimization, manually set the network to maximum interference mode to obtain the maximum interference of the entire network. This is achieved by sending the dummy burst on all idle timeslots of a specific area. In the test start command, set the test time to 1 to 24 hours. The test can be stopped automatically by software or stopped manually on the LMT.
2.115.3.4 TCH Loopback Test

TCH loopback test involves BIU loopback test and TRX RF self-loop test. In the BIU loopback test, the timeslot transmission of the TRX TCH on the BTS DBUS is tested. The TRX sends the TCH data to the traffic timeslot of the BTS DBUS. After the loopback through the TMU, the TRX receives the data sent by the TRX itself. The TRX compares the data with the original data, and then reports the BER to obtain the link quality of the TCH on the BTS DBUS. In the TRX RF self-loop test, the quality of the RX channel and TX channel of the TRX is tested. TRX RF self-test is carried out by the digital signal processing unit in the TRX. Through the baseband processing unit and the loopback of the RF unit, the data is transmitted through baseband processing unit again and returned to the digital signal processing unit. The digital signal processing unit compares the data with the original data and reports the BER to obtain the quality information regarding the TX and RX channels.
2.115.3.5 Transmission Performance Test

In a transmission performance test, the transmission performance of the E1 port specified by the BTS is tested. The transmission performance information regarding a specified TMU board can
be learned quickly through the E1 loopback test. Two types of Loop Back Mode are available: E1 Loopback and Timeslot Loopback. When E1 Loopback is selected, all the timeslots of a specified E1 port are tested. When Timeslot Loopback is selected, the number of the timeslot should be specified because only one timeslot can be tested in a test.
2.115.3.6 CRC
Operators decide whether to adopt CRC for the transmission between the BTS and the BSC.
2.115.3.7 BTS Antenna System Connection Detection

This function is used for the deployment and cutover of the BTS and for the troubleshooting of the BTS antenna system. The function involves the call test and antenna system intermodulation detection.
2.115.3.8 Call Test

You can enable the call of a specified MS to perform traverse handover on the channels in a cell through the Site Maintenance System and the BSC host. Thus, the BTS can test the channels and then report the test result to the Site Maintenance System through the BSC. The test result is saved as a file for the analysis by tools. The following issues can be tested: incorrect connection of the antenna system, main and diversity, uplink and downlink balance, one-way audio, and no audio.
2.115.3.9 BTS Antenna System Connection Detection

Interference on each frequency band is detected through the frequency band scanning. Before starting the frequency scanning, set StartTime, Duration Hour, and Freq Band List.

This chapter provides engineering guidelines regarding the configuration of BTS Test Function. l l l Site Test. The site test enables early detection and recovery of hardware failure. Baseband Test The baseband test provides the data about the signaling link quality on the BTS DBUS. Baseband Idle Timeslot Test During the network optimization phase, manually configure the network to be in maximum interference mode so as to obtain the maximum interference in the entire network. The maximum interference can be obtained by performing the baseband idle timeslot test. l TCH Loopback Test The TCH loopback test is performed to learn about the QoS of the transmission and reception channels in the BTS. l Transmission Performance Test The transmission performance test is performed to provide data about the transmission performance of the specified E1 port of the BTS so as to rapidly determine the transmission performance of the specified TMU. l
Issue 08 (2011-09-30)
CRC
CRC is performed to check the consistency between the configuration data on the OMU and the configuration data on the active SCU/XPU board. Before starting CRC, set Subrack No, Slot No, and Subsystem No. l BTS Antenna System Connection Detection This function is performed for the deployment and cutover of the BTS and for the troubleshooting of the BTS antenna system.
2.115.5 Parameters
This chapter describes the parameters related to BTS Test Function. For the description of each parameter, see Table 2-272. For the default value, value ranges, and MML commands of each parameter, see Table 2-273. Table 2-272 Parameter description (1) Parameter Test Mode Description This parameter is valid to DRFU only. When this parameter is set to NON_FDR(NON_FDR), only the VSWR of the point where the VSWR on the antenna path is maximum (hereinafter referred to as fault point) is reported. When this parameter is set to FDR(FDR), both the VSWR of the fault point and the distance from the fault point to the port on top of the cabinet are reported. Duration for starting the TRX idle timeslot test. This parameter specifies the transmit power level of the TRX. The greater this parameter is, the smaller the transmit power is. When this parameter is set to "0", the transmit power level of the TRX is the greatest. Each time this parameter increases by one level, the transmit power reduces by 2 dB. For different types of BTSs, the value range of this parameter is different. BTS3X: 0-10 BTS3001C: 0-13 BTS3002C: 0-10 Double-transceiver BTSs (BTS3012,BTS3012AE,BTS3006C): 0-10 DBS3900 GSM, BTS3900 GSM, BTS3900A GSM: 0-10. Type of the object. Self-loop type. The precautions are as follows: 1. If the self-loop type is set to "E1SELFLOOP" and the BTS type is BTS3002C, BTS3001C, or BTS3001CP, the transmission board type can be set to only "Active TMU/MMU/IOMU/DOMU". If the BTS type is BTS3006C or BTS3002E, the transmission board type cannot be set to "Active/Standby TMU". 2. If the self-loop type is set to "IASUSELFLOOP", only 3002C, 3006C, 3002E support IASU self loop type, and when the BTS type is BTS3002C, the transmission board type can be set to only "Active DOMU". Type of the transmission board. Loopback mode.
1422
Duration Hour Power Level
Object Type Self Loop Type
Transmission Board Type Loop Back Mode

Issue 08 (2011-09-30)
Parameter Port No. Test Timeslot StartTime Freq Band List
Description Port number in IASU mode. For the BTS3002C, the port number cannot be set to "E1PORT3". Test timeslot. Start of DST. List of frequency bands.
Table 2-273 Parameter description (2) Default Value None GUI Value Range NON_FDR (NON_FDR) , FDR(FDR) Actual Value Range NON_FD R, FDR MML Comma nd STR BTSVS WRTST (Optional ) STR TRXBU RSTTST (Mandato ry) SET GTRXD EV (Optional ) STR TRXBU RSTTST (Mandato ry) STR TRANSP ERFTST (Mandato ry)
Parameter Test Mode
Unit None
Impact None
Duration Hour
None
1~24
1~24
None
Power Level
0~13
0~13
None
TRX
Object Type
None
BYCELL(By CELL), BYTRX(By TRX) E1SELFLO OP(E1 Self Loopback), IASUSELFL OOP(IASU Self Loopback)
BYCELL, BYTRX
None
None
Self Loop Type
None
E1SELFL OOP, IASUSEL FLOOP
None
None
Issue 08 (2011-09-30)
1423
Parameter Transmission Board Type
Default Value None
GUI Value Range ACTIVE (ACTIVE TMU/MMU/ IOMU/ DOMU), ACTIVEST ANDBY (ACTIVE/ STANDBY TMU), SLAVE1 (SLAVE TMU1/ DOMU1), SLAVE2 (SLAVE TMU2/ DOMU2), UTRP (UTRP) E1(E1 Loopback), TIMESLOT (Timeslot Loopback) E1PORT0 (E1 PORT0), E1PORT1 (E1 PORT1), E1PORT2 (E1 PORT2), E1PORT3 (E1 PORT3), OPTICALP ORT0 (OPTICAL PORT0), OPTICALP ORT1 (OPTICAL PORT1) 0~31
Actual Value Range ACTIVE, ACTIVES TANDBY , SLAVE1, SLAVE2, UTRP
Unit None
MML Comma nd STR TRANSP ERFTST (Mandato ry)
Impact None
Loop Back Mode
None
E1, TIMESL OT
None
STR TRANSP ERFTST (Mandato ry) STR TRANSP ERFTST (Mandato ry)
None
Port No.
None
E1PORT0 , E1PORT1 , E1PORT2 , E1PORT3 , OPTICAL PORT0, OPTICAL PORT1
None
None
Test Timeslot
None
0~31
None
STR TRANSP ERFTST (Mandato ry)
None
Issue 08 (2011-09-30)
1424
Parameter StartTime
Default Value None
GUI Value Range HOUR, MIN, SEC 0~1023
Actual Value Range HOUR, MIN, SEC 0~1023
Unit None
MML Comma nd SET TZ (Mandato ry) SET GCELLF REQSC AN (Optional )
Impact BSC69 00 Cell
Freq Band List
None
None
2.115.6 Counters
2.115.7 Glossary

l l l l l BSC6900 Feature List BSC6900 Basic Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference
2.116 Connection Inter BSC over IP

2.116.1.1 Scope
This document describes the Connection Inter BSC over IP feature of Huawei GSM BSS. It provides an overview of the functions and mechanisms regarding the Connection Inter BSC over IP feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Connection Inter BSC over IP feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.116.2 Overview
IP technology is characterized by wide bandwidth, easy accessibility, high efficiency, and low cost. IP technology is increasingly used in the mobile network. The Connection Inter BSC over IP feature provides an IP-based connection between BSCs for information exchange. The TDM-based inter-BSC communication is hard to implement, because the information exchanged between BSCs must be forwarded by the MSC through the A interface. The Connection Inter BSC over IP feature enables operators to use the IP network for inter-BSC interconnection so that the BSCs can communicate with each other directly. Note that the Connection Inter BSC over IP feature supports only the signaling exchange between BSCs. It does not support the exchange of voice services or data services between BSCs. The Connection Inter BSC over IP feature applies to the scenarios where inter-BSC signaling exchange is required. For example, when the inter-BSC soft-synchronized network or the interBSC Interference Based Channel Allocation (IBCA) feature is enabled, the Connection Inter BSC over IP feature is enabled to obtain the radio resource information about multiple BSCs, including the frequency offset, interference, and load, thus facilitating resource sharing between different BSCs.

The Connection Inter BSC over IP feature is enabled only when the DSP type parameter is set to IUR_G(IUR_G) in the case of IP transmission. The IP-based inter-BSC connection is implemented through IP routers. Figure 2-375 shows the network structure for IP-based inter-BSC connection. Figure 2-375 Network structure for IP-based inter-BSC connection
The interface between BSCs uses the protocol stack for the Iur-g interface. The transport layer for this interface is the same as the transport layer for the Iur-g interface. The radio network layer carries the BSC signaling, which are transmitted in the form of customized messages. Figure 2-376 shows the protocol stack for the interface between BSCs. For details, see 3GPP TS 43.903. Figure 2-376 Protocol stack for the interface between BSCs
The BSC must be configured with interface boards that support IP transmission. The interface boards that support IP transmission provide FE and GE ports, which comply with the IPv4
protocol. When configuring the SS7 signaling point at one BSC, one must set the DSP type parameter to IUR_G(IUR_G).
2.116.4 Parameters
This chapter describes the parameters related to the Connection Inter BSC over IP feature. For the description of each parameter, see Table 2-274. For the default value, value ranges, and MML commands of each parameter, see Table 2-275. Table 2-274 Parameter description (1) Paramete r DSP type Description DSP type. STP: indicates the signaling transfer point. A: indicates the signaling point of the A interface control signaling plane. IUR_G: indicates the signaling point of the base station controller that is connected to the BSC. LB: indicates the signaling point of the LB interface.
Table 2-275 Parameter description (2) Paramet er DSP type Defaul t Value None GUI Value Range STP(STP), A (A), IUR_G (IUR_G), LB (LB) Actual Value Range Uni t MML Comman d ADD N7DPC (Mandator y)
Impact SCCP
STP, A, IUR_G, LB Non e
2.116.5 Counters
2.116.6 Glossary

l l l l l
Issue 08 (2011-09-30)
3GPP TS 43.903: A-interface over IP Study BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference
2.117 Encrypted Network Management

2.117.1.1 Scope
This document describes the encrypted network management feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Encrypted Network Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.117.2 Overview
Introduction
The encrypted network management feature is based on the Secure Socket Layer (SSL) protocol, which allows the M2000 to set up an SSL-based TCP transmission channel between the M2000 server and an NE. With the rapid development of radio networks, telecom operators have higher requirements for the security of OM transmission. Thus, data encryption on OM channels has become a basic feature of telecommunications products. The encryption on OM transmission channels is applied in scenarios such as remote maintenance and data transmission between the LMT and NEs. The encryption on GBSS OM transmission channels provides customers with the following benefits: l l l Ensuring the security and confidentiality of data transmission over OM channels Ensuring the privacy of customers' data Reducing the possibility that data be intercepted during transmission through plain text

2.117.3.1 Overview
During the data transmission between the M2000 and an NE, most of the data is transmitted in the form of data files such as performance data file, log file, configuration data file, and version and batch data file. If data files are transmitted in traditional transmission mode (plain text), they are subject to exposure to unauthorized parties. With the encrypted network management feature, an SSL-based transmission channel is set up between the M2000 server and an NE before a TCP link is established. Data is transmitted over the encrypted channel. Figure 2-377shows the encrypted network management feature. Figure 2-377 Encrypted network management
SSL is a protocol that guarantees the security of data transmission. The SSL protocol is applied between the application layer and the transport layer. It provides the following functions:
l l l
Data encryption Identity authentication Data integrity check
The SSL protocol provides secure data transmission to upper-layer applications such as WEB service, FTP, and Telnet. The transmission between the M2000 and a BSC supports both normal connection and SSLbased connection. To ensure the security of data transmission between the M2000 and a BSC, it is recommended that SSL-based connection be used.
Figure 2-378shows the flowchart of establishing SSL-based connection between the M2000 and a BSC.
Issue 08 (2011-09-30)
1431
Figure 2-378 Flowchart of establishing SSL-based connection between the M2000 and a BSC
Figure 2-379shows the flowchart of establishing FTP connection between the M2000 and a BSC.
Issue 08 (2011-09-30)
1432
Figure 2-379 Flowchart of establishing FTP connection between the M2000 and a BSC
Through SSL, the M2000 implements the following functions: l l l l Setting the connection policy between the M2000 and a BSC Setting the SSL authentication policy Managing the digital certificates of NEs Setting the SSL encryption for FTP
2.117.3.2 Setting the Connection Policy Between the M2000 Connection Type
The connection types are as follows: l l Common connection By default, the connection between the M2000 and a BSC is in common mode. SSL-based connection The SSL protocol is adopted to ensure the security of data transmission between the M2000 and the BSC. After a BSC is created and accesses the M2000, users can enable the SSLrelated functions of the BSC on the M2000 client.
Setting the SSL Connection Policy

Users can set the SSL connection policy between the M2000 and the BSC on the M2000 client.
2.117.3.3 Setting the SSL Authentication Policy

The SSL authentication policy determines whether the ID authentication is performed when the BSC is connected to the M2000 through SSL. Through the ID authentication, the M2000 determines whether the information is sent to the correct BSC, thus ensuring the secure transmission of information. The prerequisites for setting the SSL authentication policy are as follows:
l l l
The certificate is already configured on the M2000. For details on how to configure the certificate, see section Managing the Digital Certificate. The authentication policy becomes valid only when an SSL connection is set up between the M2000 and the BSC. The digital certificate is issued to the BSC and has been activated.
Table 2-276describes the parameters for the SSL authentication policy. Table 2-276 Parameter description Parameter NE name OMC authenticates NEs NE authenticates the OMC Describes Name of an NE. Whether the M2000 authenticates the BSC when the SSL connection is set up between the M2000 and the BSC. Whether the BSC authenticates the M2000 when SSL connection is set up between the M2000 and the BSC.
NOTE
The modes of SSL connections between the M2000 and NEs are as follows: l l l Anonymous: do not select either of the two options. Unidirectional authentication: select either of the two options, that is, the OMC authenticates NEs or NE authenticates the OMC. Bidirectional authentication: select both the options.
2.117.3.4 Managing the Digital Certificate

The digital certificate is abbreviated to certificate. It is essential to the PKI. The certificate is a segment of data that contains the user ID information, user public key information, and the digital signature of the CA. The current certificate conforms to the X.509 standard and has the following contents: l l l l l l l Version number of the certificate Serial number of the certificate ID of the signature algorithm Name of the issuing authority Validity period Certificate owner Public key of the certificate
M2000 Certificate
By default, the M2000 is not configured with a digital certificate. If users need to use a certificate, they need to apply for a certificate from the certification authority (CA) and then manually configure the certificate for the M2000 server.

NOTE
The CA that applies for the M2000 certificate must be the one that applies for the NE certificate.
NE Certificate
The certificates of the BSC are managed by the M2000. Users can import, configure, and query certificates. Table 2-277describes the certificates used by the BSC. Table 2-277 Certificates used by the BSC Certificate Type Root certificate Description The root CA is the first issuing authority of the public key system. It is the source of all the trust and uses its private key for signature. The certificate issued by the root CA for itself is the root certificate. The root CA can create certificates for other CAs. It can also create certificates for other computers, users, or services. Users can trace the root certificates of most certificatebased applications through the certificate chain. The digital certificate with a public key. To ensure that the public key certificate is correct, the public key certificate requires the signature of the CA. Part of the private key. To ensure the security of the private key file, users must encrypt the private key file. This means that only the person who knows the password of the private key can use it. In case that the private key of an entity in PKI is stolen, the public key certificate matching the stolen key must be added to the certificate revocation list (CRL) and set to invalid. If a certificate owner has ended the relation with an organization, the corresponding public key certificate must be added to the CRL. To verify the public key, users must obtain the public key of the CA that issues the certificate of the private key. Then, users can check the signature on the certificate. The identity of a public key certificate should be authenticated by the CA of the upper level. The process for authenticating a public key becomes an iterative process. As a result, a certificate chain is formed, which ends at the root certificate.
Public key certificate Private key file CRL
Certificate chain
Table 2-278describes the naming rules of BSC certificates. Table 2-278 Naming rules of BSC certificates Certificate Type Root certificate
Issue 08 (2011-09-30)
Naming Rules NE name_RootCA_Date.XXX
1435
Certificate Type Public key certificate Private key file CRL
Naming Rules NE name_ClientCer_Date.XXX NE name_ClientPrivKey_Date.XXX NE name_CRLFile_Date.XXX
NOTE
l The root certificate, public key certificate file, and private key file are mandatory for issuing NE certificates. l XXX refers to the format of a certificate. For details on the formats of certificates supported by NEs, see Table 2-279.
Table 2-279 Formats of certificates that are issued to the BSC and supported by the M2000 Certificate Type Root certificate Public key certificate Private key file Certificate chain CRL Format .cer, .crt, .pem, .pfx, .p12 .cer, .crt, .pem, .pfx, .p12 .pem, .pfx, .p12 .pem .cer, .crt, .crl, .pem
NOTE
l The certificates used by the M2000 and the BSC must be requested in the same CA. l A password is generated along with the NE private key. Therefore, users need to provide the password when the M2000 issues the certificate to the BSC. l If the BSC certificate is not issued by the root CA, a certificate chain file is required.
Importing BSC Certificates

Users can create tasks on the M2000 client to download and activating BSC certificates. After the tasks are created, the M2000 executes the tasks to issue the certificates to the BSC and activate the certificates.
NOTE
l The M2000 server automatically deletes certificate files after it successfully issues the files. l To protect digital certificates from being illegally copied, it is advised that users delete the certificate files saved on the local M2000 client after they are backed up. l When importing certificates for a BSC, ensure that the imported certificates consist of the root certificate, public key certificate, and private key file.
Issue 08 (2011-09-30)
1436
When the BSC communicate normally with the M2000, users can issue a certificate to the relevant BSC by creating a task for creating certificates on the M2000 client.
Querying NE Certificates
When the connection between the BSC and the M2000 server requires an identity authentication, the associated digital certificates must exist on the BSC. Users can query the digital certificates used by the BSC on the M2000 client.
NOTE
On the NE, only a set of activated digital certificates exist. When querying certificates, users can query only the names of the certificates used by the BSC.
2.117.3.5 Setting SSL Encryption for FTP

The FTP connection between the M2000 and the BSC is based on SSL. Users can encrypt the FTP of the M2000 to transmit files in encrypted mode.
NOTE
l The FTPS encryption is anonymous. l The settings and authentication mode of the SSL connection policy are not applicable to the FTPS policy. The two policies are mutually exclusive.
2.117.3.6 Specifications
If both communication parties adopt SSL to transmit data, the communication performance degrades by 20% to 60%.Table 2-280 and Table 2-281list the hardware configuration of the server and client. Table 2-280 Hardware of a server Item Server CPU Operating system RAM Logs LAN Configuration Sun Fire V440 1.59 GHz x 2 Solaris 10 4 GB 100 Mbit/s
Table 2-281 Hardware of a client Item Client CPU

Issue 08 (2011-09-30)
Configuration Windows XP Pentium 3.0 GHz, dual core

Item Operating system RAM Logs LAN
Configuration Windows XP 512 MB 100 Mbit/s
Table 2-282 and Table 2-283 list the data transmission performance in TCP mode and SSL mode when the hardware configuration listed in Table 2-280 and Table 2-281 is used. Table 2-282 Transmission performance in TCP mode Data Size (MB) 5 10 100 Time (s) 0.145439 0.256535 2.505977 CPU Usage (%) 1.77777778 4.33333333 17.4615385 Used RAM (MB) 9.10222 10.24 32.29538
Table 2-283 Transmission performance in SSL mode Data Size (MB) 5 10 100 Time (s) 0.291336 0.5687 5.771667 CPU Usage (%) 8.2 18.75 29.9500 Used RAM (MB) 13.82400 21.76 56.832
2.117.4 Parameters
None.
2.117.5 Counters
2.117.6 Glossary

l l l
M2000 Commissioning Guide M2000 Administrator Guide M2000 Operator Guide
2.118 End-to-End MS Signaling Tracing

2.118.1.1 Scope
This document describes the End-to-End MS Signaling Tracing functional area. It provides an overview of the main functions and goes into details regarding End-to-End MS Signaling Tracing control functions.


The change history provides information on the changes in different document versions.
Document and Product Versions

There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the End-to-End MS Signaling Tracing feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.118.2 Overview
End-to-end MS signaling tracing is a function based on which the network administrator traces the activities of each NE when an event occurs. It becomes increasingly difficult to locate service faults in MSs because the communications network becomes more and more complicated. Users can detect the section where the fault occurs only when the information about the whole process of the MS is collected. By using the end-toend MS signaling tracing function, the system can completely record the service activities of an MS and then locate the section where the fault occurs. The recorded information covers all the NEs involved in the service. If the traced objects are reasonably defined, valid location information can be obtained without using a large amount of processing and transmission resources of the system in the whole tracing process.

2.118.3.1 Overview
A task of end-to-end MS signaling tracing on NEs is created on the M2000. When the MS is processing services, the NEs record the MS signaling and other information about the MS; when the MS stops processing services, the NEs send the MS signaling and information to the M2000 in the form of tracing file. The M2000 interprets and summarizes the tracing files and sends the files to the MS. The following figure shows the end-to-end MS signaling tracing procedure.
The end-to-end MS signaling tracing is activated at the MSC. The procedure for end-to-end MS signaling tracing on an MOC is triggered through the MSC_INVOKE_TRACE message, and the procedure for end-to-end MS signaling tracing on an incoming-BSC handover call is triggered through the BSC_INVOKE_TRACE message.
The BSC supports end-to-end MS signaling tracing only when Support End-to-end User Tracing Function is set to YES(Yes).
2.118.3.2 Procedure for End-to-End MS Signaling Tracing on an MOC in a BSC

The function of end-to-end MS signaling tracing is activated by the MSC. If the CM_Service_Req message received from the MS indicates that end-to-end signaling tracing is required, the MSC sends an MSC_INVOKE_TRACE message to the BSC. On receiving the message, the BSC starts end-to-end signaling tracing. The MSC_INVOKE_TRACE message contains such information as tracing ID and type of the information to be recorded. The BSC then records the associated signaling in the end-to-end tracing file according to the information. The end-to-end tracing file is saved in .tmf format on the BSC6900 LMT. Users can view the file through the interface tracing function on the BSC6900 LMT. After the call ends, the BSC sends the end-to-end tracing file to the M2000 through FTP. The M2000 interprets and then displays a report on the M2000 client.
2.118.3.3 Procedure for End-to-End MS Signaling Tracing on an Incoming-BSC Handover Call

When end-to-end MS signaling tracing is performed on a call in the source BSC and the call is to be handed over to the target BSC, then the source BSC sends a BSC_INVOKE_TRACE message to the MSC, which then forwards the message to the target BSC. On receiving the BSC_INVOKE_TRACE message, the target BSC starts end-to-end MS signaling tracing. The source BSC sends the end-to-end tracing file to the M2000. When the call in the target BSC ends, the target BSC sends the end-to-end tracing file to the M2000. Then, the M2000 combines the two tracing files, interprets them, and displays a report on the M2000 client.
2.118.4 Parameters
his chapter describes the parameters related to End-to-End MS Signaling Tracing. For the description of each parameter, see Table 2-284. For the default value, value ranges, and MML commands of each parameter, see Table 2-285. Table 2-284 Parameter description (1) Parameter Support End-to-end User Tracing Function Description Whether to enable end-to-end user tracing for the BSC. If this parameter is set to YES, the BSC starts end-to-end user tracing after the BSC receives the MSC Invoke Trace or BSS Invoke Trace message from the MSC.
Issue 08 (2011-09-30)
1441
Table 2-285 Parameter description (2) Paramet er Support End-toend User Tracing Function Default Value NO GUI Value Range NO(No), YES(Yes) Actual Value Range NO, YES MML Comman d SET OTHSOF TPARA (Optional)
Unit None
Impact BSC
2.118.5 Counters
2.118.6 Glossary

l l l l l 3GPP TS 12.08 BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference
2.119 Flex Ater

2.119.1.1 Scope
This document describes the application scenario, principle, and resource management regarding Flex Ater.

l l

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the Flex Ater feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.119.2 Overview
Flex Ater is a function based on which Ater resources are allocated according to the channel type during the call establishment. If TCHFs are allocated on the Um interface, 16 kbit/s timeslots are used on the Ater interface. If TCHHs are allocated on the Um interface, 8 kbit/s timeslots are used on the Ater interface. This feature effectively reduces the transmission investment on the Ater interface in remote TC networking. When the TCHHs account for 30% in the system, the Flex Ater-capable network saves the Ater transmission resources by up to 15%.

The Ater interface is an internal interface between the MPS/EPS and the TCS in the Huawei BSS equipment. With this feature, the Ater resources are classified into 16 kbit/s timeslots and 8 kbit/s timeslots. The BSC allocates the Ater resources according to the channel type during the call establishment. If TCHFs are allocated on the Um interface, 16 kbit/s timeslots are used on the Ater interface. If TCHHs are allocated on the Um interface, 8 kbit/s timeslots are used on the Ater interface. Thus, the Ater resources are fully utilized. The Ater resources of Huawei BSC are classified into 16 kbit/s Ater resource pool and 8 kbit/s Ater resource pool. If TCHFs are allocated on the Um interface, 16 kbit/s Ater resources are allocated; if TCHHs are allocated on the Um interface, 8 kbit/s Ater resources are allocated. The BSC not only allocates and manages the resources in the pools but also adjusts the allocation of Ater resources between the two pools according to the remains in each pool.Figure 2-380 shows the Flex Ater.
Figure 2-380 Flex Ater
The BSC balances the 16 kbit/s Ater resources and 8 kbit/s Ater resources according to the traffic model. If either type of resources is insufficient, the BSC dynamically adjusts the Ater resources. If the 16 kbit/s timeslots are insufficient, two consecutive 8 kbit/s timeslots are combined into one 16 kbit/s timeslot. Similarly, if the 8 kbit/s timeslots are insufficient, one 16 kbit/s timeslot is divided into two 8 kbit/s timeslots. In addition, the user can query the number of 16 kbit/s timeslots and the number of 8 kbit/s timeslots and the usage of these timeslots on the Ater interface by running the DSP ATERTS command. When this feature is enabled and the transmission resources on the Ater interface are insufficient, the BSC preferentially allocates TCHHs to alleviate the congestion, thus increasing the system capacity. Flex Ater can be enabled by setting Switch of 8K on Ater to YES(Yes).
2.119.4 Parameters
This chapter describes the parameters related to Flex Ater. For the description of each parameter, see Table 2-286. For the default value, value ranges, and MML commands of each parameter, seeTable 2-287. Table 2-286 Parameter description (1) Parameter Switch of 8K on Ater Description Whether to enable the BSC to use a 8 kbit/s timeslot to transmit 8 kbit/s data at the Ater interface.
Issue 08 (2011-09-30)
1444
Table 2-287 Parameter description (2) Paramet er Switch of 8K on Ater Default Value YES GUI Value Range NO(No), YES (Yes) Actual Value Range NO, YES MML Comman d SET OTHSOF TPARA (Optional) Impa ct BSC
Unit None
2.119.5 Counters
2.119.6 Glossary

l l l l l BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference
2.120 TrFO
2.120.1.1 Scope
This document describes the benefits of the transcoder free operation (TrFO) feature and the principle of implementing this feature in Huawei GSM BSS.

Issue 08 (2011-09-30)


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l l Feature change Feature change refers to the change in the TrFO feature of a specific product version. Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.120.2 Overview
In the traditional MS-MS call process where the Tandem Free Operation (TFO) or TRanscoder Free Operation (TrFO) is not adopted, the speech signal is coded at the calling MS, transmitted on the Um interface, and then decoded at the first Transcoder & Rate Adaptation Unit (TRAU). The decoded Pulse Code Modulation (PCM) data steam is transmitted on the 64 kbit/s link to the second TRAU for coding and is then transmitted on the Um interface to the called MS for decoding. In the MS-MS call process, the coding and decoding are continually performed twice. This degrades the speech quality. The TrFO feature enables the calling MS and called MS to use the same speech coding/decoding scheme. Thus, the speech signal is coded at the calling MS and decoded at the called MS only once. The TrFO feature reduces the negative impact on the speech signals due to repeated coding and decoding, thus improving the signal quality and the user experience. In addition, with the TrFO feature, the TRAU is not needed, thus saving the TC resources. The TrFO feature is implemented in only scenarios where IP is applied over the A interface.

TrFO supporting of the BSC
In the GSM network, the coding capability of each cell can be dynamically configured. The coding scheme of the Um interface is determined by the BSS. When implementing TrFO, the MSC server selects the speech versions supported by the cells where the calling MS and called MS are located based on the coding capability of the cells. Then, the MSC sets the expected speech version to a highest priority. In this way, the TrFO can be successfully implemented.
To support the TrFO feature, the BSC must implement the following functions: 1. The BSC sends the Complete Layer 3 Information message carrying the "BSC Supported Codec List" IE to the MSC, informing the MSC of the coding schemes (FR/HR/EFR/ AMR_NB/AMR_WB) supported by the cell. The BSC selects the speech versions according to the Preferred Codec List carried in the assignment request from the MSC. For the established calls, the MSC sends the INTERNAL HANDOVER ENQUIRY message carrying the specified Speech Codec to the BSC to trigger the intra-BSC handover.
2. 3.
Differences between TrFO and TFO

Both TrFO and TFO use the speech compression in the MSC. Both features improve the QoS by avoiding repeated code conversions during the MS-MS call. The two features, however, are different from each other. TFO is activated, deactivated, and controlled by the TRAU after a call is established. When detecting that the same coding/decoding scheme is used by the encoder and decoder, the TRAU activates the TFO for compressed speech transmission. TrFO, however, does not require the TRAU. It uses OutofBand Transcoder Control (OoBTC) to negotiate the coding/decoding scheme of both the calling MS and called MS before the call is established. Then, the compressed speech is transmitted after the call is established. If the requirement for TrFO is not met, it takes some time to configure the TRAU for restoring the PCM coding/decoding. Without the TRAU, the call fails. In the case of the TFO, however, the PCM coding is used immediately when the requirement for TFO is not met. In this manner, the speech quality is not affected.
2.120.4 Parameters
None.
2.120.5 Counters
2.120.6 Glossary

l l l l l l 3GPP TS 43.903: A-interface over IP Study BSC6900 Feature List BSC6900 Optional Feature Description GBSS Reconfiguration Guide BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference
2.121 Forced System Information Sending by OMC

2.121.1.1 Scope
This document describes the Forced System Information Sending by OMC feature of Huawei GSM BSS. It provides an overview of the functions and mechanisms regarding the Forced System Information Sending by OMC feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Forced System Information Sending by OMC feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.121.2 Overview
System information plays an important role in network tuning, MS behavior control, and network optimization. Forced System Information Sending by OMC is a feature through which the system is made to send system information to a certain cell and the MSs camping on the cell. The Forced System Information Sending by OMC feature helps in network troubleshooting. When a problem occurs on the network, maintenance engineers can identify the problem by
viewing the system information manually sent. Maintenance engineers can also adjust the parameters and verify the parameter adjustment for specific cells in real time, thus facilitating network optimization. Therefore, this feature enables operators to improve the network quality, provide better services to subscribers, and improve the user satisfaction.

System information carries main radio network parameters on the Um interface, including network identity parameters, cell selection parameters, system control parameters, and network function parameters. A proper system information mechanism is essential to a network of high quality. In Huawei GBSS, system information can either be sent autonomously or be sent manually. When a problem occurs on the network, maintenance engineers can identify the problem by viewing the system information manually sent. In the case of network optimization, the system information on the Abis interface is traced. Through the traced system information, one can obtain, analyze, and verify the parameter configuration of system information. Note that the parameter configuration of system information can be immediately obtained through the system information manually sent. Figure 2-381 shows the network architecture for the Forced System Information Sending by OMC feature. Figure 2-381 Network architecture for the Forced System Information Sending by OMC feature
The SND GCELLSYSMSG command is executed on the LMT to manually send system information. Note that the cell to which the system information is to be sent must be specified. The BSC then sends the system information to the specified cell and the MSs camping on the cell. Based on the received system information, an MS can properly select and access a radio network. Then, the MS can fully use the services provided by the network and well cooperate with the network.
2.121.4 Parameters
None.
2.121.5 Counters
2.121.6 Glossary

l l l BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM MML Command Reference
2.122 Performance Management

2.122.1.1 Scope
This document describes the performance management feature of Huawei SRAN (MRFD-210302 Performance Management). It covers the functions and technical mechanisms regarding Performance Management, including performance measurement procedure, performance measurement management, and real-time performance monitoring.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Performance Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
01(2010-01-20)
2.122.2 Overview
Performance management involves the periodical collection, gathering, saving, inspection, and analysis of the counters regarding management objects, resource bearer functions, and features, thereby helping operators understand the overall conditions of the network. This feature enables operators to identify and rectify a problem at the earliest possible time, and thereby optimizes the network. Performance management provides an efficient method for monitoring network performance. Through the measurable performance data collected, operators can understand the overall conditions of the network and, identify and rectify a problem at the earliest possible time. This feature facilitates problem rectification and network optimization. The performance management feature provided by Huawei is applicable to both the Base Station Subsystem (BSS) and the Radio Access Network (RAN).

2.122.3.1 Overview
The performance management feature provides operators with a method for managing the measurable performance data.Figure 2-382 shows the working mechanism of the performance management feature. Figure 2-382 Working mechanism of the performance management feature
NMS: short for Network Management System. The NMS may be from another vendor or be developed by the operator. It analyzes the counters regarding the network layer. The
Issue 08 (2011-09-30)
NMS is interconnected with Huawei Element Management System (EMS) through the northbound interface (NBI). l Tool: The tool used here is Huawei Nastar, which is a network optimization tool. Huawei Nastar monitors the network through the performance data provided by Network Elements (NEs), compares the network performance after the network swapping with that before the network swapping, and analyzes the growing trend of the network. Huawei Nastar is interconnected with the EMS and the NE through proprietary interfaces. LMT: short for Local Maintenance Terminal. The LMT enables operators to view the performance calculation results in the ineffective mode. The LMT is connected to the NE through a file interface. EMS: short for Element Management System. The EMS is used to operate and maintain NEs. The functions of the EMS are mainly implemented by its performance management module, that is, the PFM. The main functions of the PFM module are as follows: configuration of NE performance measurement, query of performance measurement results, real-time monitoring of performance measurement, and management of performance data, performance alarm, custom counters, and performance data reporting. Huawei EMS is connected to a base station controller through a Man Machine Language (MML) interface. Over the MML interface, files regarding performance management are transmitted in accordance with the FTP protocol. NE: short for Network Element. NEs collect performance measurement data, generate performance measurement results, and report performance measurement results. A base station reports its performance data to the connected base station controller through the Abis or the Iub interface. The base station controller collects the performance data of the connected base stations, generates the performance measurement results, and reports the results to the EMS.
In conclusion, the EMS (M2000) creates a performance measurement task and sends the requirements of the measurement task (including time to perform the measurement and the measurement report period) to the NEs. The NEs collect the performance data in accordance with the requirements, gather the performance data, generate performance measurement results, and report the results to the EMS.
?.1. Performance Measurement Procedure

The performance measurement procedure involves measurement registration, generating performance measurement results, reporting performance measurement results, and saving the results to the database. Figure 3-2 shows the performance measurement procedure. The performance measurement results may sometimes fail to be reported to the EMS due to a system failure or network break-off. In such cases, the automatic compensated collection or the manual compensated collection function of the M2000 can be used to obtain the performance measurement results from NEs. After being saved to the database, the performance measurement results can be exported through the NBI of the M2000, and be submitted to the NMS for further analysis. Figure 2-383 shows the performance measurement procedure.
Issue 08 (2011-09-30)
1452
Figure 2-383 Performance measurement procedure
1.
Measurement registration The measurement objects, counters, and measurement report periods are set and saved on the M2000 client. The M2000 client generates a performance measurement task based on the saved information, activates the task, and sends the task to NEs.
2.
Generating performance measurement results The main control operation&maintenance module of a NE receives the performance measurement task sent from the M2000, parses the measurement requirements, including the counters to be measured and the measurement report period, and updates the measurement requirements. In addition, the main control operation&maintenance module sends the information regarding the measurement report period and non-default measurement objects to the service boards for re-registration. The service boards collect the performance measurement data, generate the original performance measurement results, and send the results to the main control operation&maintenance module. The main control operation&maintenance module receives the performance measurement results sent from the service boards and gather them together. Then, the main control operation&maintenance module calculates the values of counters based on the predefined formulas. At the same time, the main control operation&maintenance module receives the performance measurement results that are sent on a short measurement report period basis and sends the performance measurement results to the upper-level NE on a long measurement report period basis.
3.
Issue 08 (2011-09-30)
Reporting performance measurement results

The main control operation&maintenance module responds to the related M2000 command and sends the performance measurement results to the M2000. 4. Saving performance measurement results to the database The M2000 obtains the performance measurement results, parses the performance counters needed, and saves the performance counters to the database. In cases where performance measurement results fail to be reported to the M2000, the automatic compensated collection or the manual compensated collection function of the M2000 is used to obtain the performance measurement results from NEs. l Automatic compensated collection Automatic compensated collection is a function through which the M2000 automatically obtains the performance measurement results from NEs. The M2000 obtains the performance measurement results from NEs through the related command. This function is implemented only when NEs are disconnected from the NMS or when the performance service function of the M2000 is unavailable and no performance measurement results are reported for a period of time. l Manual compensated collection Manual compensated collection is also called measurement result synchronization. Through the manual compensated collection function, one manually runs the measurement result synchronization command on the M2000 client to obtain the performance measurement result during a specified period of a measurement item being measured.
?.2. Performance Measurement Management

Performance measurement can be manually stopped or restored. Both the base station and the base station controller provide an interface to connect with the M2000. The base station and the base station controller collect the performance measurement data in accordance with the measurement requirements, and send the performance measurement results to the M2000. The measurement results for all performance counters can be calculated and reported. The measurement report period can be customized. NEs can report the performance measurement results for all performance counters. The performance data for counters that are reported per common measurement report period is reported to the EMS, which then saves the performance data according to tasks. The performance data for counters that are reported per short measurement report period or long measurement report period is first converted to performance measurement results according to the measurement requirements, and then sent to the EMS. The measurement report period can be customized. A counter can be reported on the basis of a short period, a common period, or a long period. A short period can be 5 minutes or 15 minutes, and operators can choose either as the measurement report period. A common period can be 30 minutes or 60 minutes, and operators can choose either as the measurement report period. A long period lasts 1,440 minutes. Operators can flexibly choose a measurement report period for NEs. In addition, operators can choose different measurement report periods for different counters. Performance measurement can be classified into three categories: default performance measurement, non-default performance measurement, and real-time performance measurement. l
Issue 08 (2011-09-30)
Default performance measurement

NEs automatically measure all measurement objects of default performance measurement. A default performance measurement task supports three types of measurement report periods. The details are as follows: Common measurement report period. The common measurement report period for a default performance measurement task can be 30 minutes or 60 minutes. Operators can choose a proper measurement report period through the EMS. Short measurement report period: The short measurement report period for a default performance measurement task can be 5 minutes or 15 minutes. Operators can choose a proper measurement report period through the EMS. Long measurement report period: The long measurement report period for a default performance measurement task is 24 hours. One is not allowed to add or delete a default measurement object through the EMS. l Non-default performance measurement NEs measure the measurement objects of non-default performance measurement. Nondefault performance measurement is defined because the measurement of all objects involves a great amount of data processing. Thus, only the specified objects are measured at certain periods. A great number of measurement objects are considered as non-default performance measurement. One can add or delete a non-default measurement object through the EMS. l Real-time performance measurement In real-time performance measurement, NEs measure certain objects on a short measurement report period basis to monitor the changes in performance data in real time. Generally, only counters regarding Key Performance Indicators (KPIs) are measured in real time, and the measurement period is one minute. A real-time performance measurement task is started or cancelled on the EMS. The data collected during real-time performance measurement is reported to the EMS. Through performance measurement, key counters and other counters can be measured. The key counters are used to generate the KPIs which are defined by the EMS. The KPIs are initialized immediately after the base station controller and the base station are started. KPIs, related original counters, and formulas can be added, modified, and deleted on the EMS. One can also add counters that indicate certain network performance as required. The UMTS network supports the following performance measurements: l l l l l l l l Cell Neighboring cell Inter-RAT neighboring cell RNC overall ATM transport IP transport Standard interface NE hardware
The GSM network supports the following performance measurements:(Performance measurements classified into the following types according to measurement objects) l l l
Issue 08 (2011-09-30)
BSC Cell TRX

l l l l l l
Neighboring cell Relationship(Performance measurements classified into the following types according to UE status) Paging Call procedure Sending Measurement report Waiting for channel allocation Measurement of incoming and outgoing inter-cell handovers This measurement provides data about the incoming and outgoing inter-cell handovers. The collected measurement data helps operators to adjust the parameters regarding intercell handovers, therefore optimizing network quality.
Enhanced performance measurement can be classified into the following categories:
Undefined neighboring cell measurement This measurement provides Base Transceiver Station Identity Code (BSIC), BCCH frequency, average signal strength, number of measurement reports (MRs) of neighboring cells that are included in the BA list but not included in the neighboring cell relation table. The collected measurement data assists operators in network adjustment and network optimization.
Defined neighboring cell measurement This measurement provides BSIC, BCCH frequency, average signal strength, number of MRs of the defined neighboring cells. The collected measurement data assists operators in network adjustment and network optimization.
Uplink and downlink balance measurement This measurement provides the data about the balance between uplink TCH performance and downlink TCH performance. The uplink and downlink balance level is calculated for the uplink receive level and the downlink receive level. The collected measurement data assists operators in network adjustment and network optimization.
Call drop measurement his measurement provides the average receive level and average receive quality in uplink and in downlink and also the average TA value in the case of SDCCH call drops and TCH call drops. The collected measurement data assists operators in network adjustment and network optimization.
Base station out-of-service measurement Together with M2000, this measurement provides the performance data regarding base station out-of-service, including the start time of base station out-of-service, end time of base station out-of-service (or service restoration time), and the duration of base station out-of-service.
?.3. Real-Time Performance Monitoring

Through real-time performance monitoring, the network is monitored in real time, and the monitoring result is displayed in tabular and graphical forms. Real-time performance monitoring facilitates troubleshooting, drive tests (DTs), and network optimization. A real-time performance monitoring task is managed by the LMT for the BSC and the BTS. The monitoring data is displayed in curve and is automatically stored in a file for later review. The following items can be monitored in real time: l
Issue 08 (2011-09-30)
Equipment performance, including CPU usage, and clock source quality

l l l l
Connection performance, including Signal-to-Interference Ratio (SIR) measurement and UE transmit power Cell performance, including PCPICH transmit power and number of UEs in the cell Link performance, including IMA group performance and UNI link performance Service performance, including RF performance, uplink channel scanning, and resource occupancy
2.122.4 Parameters
None.
2.122.5 Counters
2.122.6 Glossary

None.
2.123 O&M of BTS

2.123.1.1 Scope
This document describes the O&M of BTS feature. It provides an overview of the main functions and mechanisms regarding the O&M of BTS feature.


There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the O&M of BTS feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.123.2 Overview
BTS is an important part of the Base Station Subsystem (BSS). Operators must deploy a large number of BTS sites to construct a network with wide coverage and good performance. In addition, operators must frequently perform O&M operations on the BTS sites to ensure the normal operation of the network. The cost of O&M operations is very high. The O&M of BTS feature is introduced to solve this problem. With this feature, operators can operate and maintain logical objects at the remote end or boards on the local site. The BTS logical objects include site, cell, baseband, channel, TRX, and timeslot. Huawei O&M of BTS feature is characterized by powerful functions, easy and simplified O&M, and low O&M costs. The benefits of the O&M of BTS feature are as follows: l l Flexible operations enable operators to perform the O&M at either the local end or the remote end. Unlike the independent O&M for each site, the O&M system provided by Huawei GBSS simplified the manual operations and reduces the O&M costs because Huawei GBSS supports the centralized O&M for BTSs controlled by one BSC. The remote O&M system helps operators promptly identify and solve a problem in BTS operation, thereby reducing the Operational expenditure (OPEX). O&M of multiple BTSs O&M of cell O&M of baseband O&M of channel O&M of TRX O&M of BTS hardware Flexible OML configuration
The O&M of BTS feature supports the following functions: l l l l l l l

Issue 08 (2011-09-30)

All O&M functions can be implemented either at the remote end or at the local end, thereby improving the maintenance flexibility. The general O&M of the logical object is performed at the remote end. In the case of hardware replacement, all O&M can be performed on the local site. l O&M of multiple BTSs The BTSO&M involves the following operations: query, loading, and activation of software versions; query of site attributes; query of the usage of different resources; transmission performance test; reset in levels; environment monitoring; alarm shielding; query of ring networking parameters. This function reduces the workload of maintenance engineers and also the possibility of improper operations, particularly in the case of operations on a large-scale network. Huawei GBSS supports four types of O&M operations for multiple BTSs: fault query, software version query, manual loading of software, and software activation. l O&M of cell O&M of cell involves the following operations: cell attribute query, cell administrative state change, cell system information sending, and forced inter-cell handover. The forced inter-cell handover provided by the BSC is a forced handover with or without a specified target cell. The BSC selects a target cell based on the Measurement Reports (MRs) received to ensure a successful handover. The forced inter-cell handover is used to hand over the MSs with ongoing voice services in a cell to another cell before the BTS maintenance to prevent call drop caused by BTS maintenance. l O&M of baseband O&M of baseband involves the following operations: query of baseband attributes, reset in levels for baseband, query and change of baseband administrative state, and baseband test. l O&M of channel. O&M of channel involves the following operations: query of channel attributes, query and change of channel administrative state, forced channel handover, and related O&M of channel. l O&M of TRX. O&M of TRX involves the following operations: O&M of TRX administrative state, query of TRX attributes, and automatic frequency correction. l O&M of BTS hardware O&M of BTS hardware involves board specific operations such as query, maintenance, and reset of the BTS boards. One can select specific boards on the O&M system to query information such as software information and hardware information, extended power information. In addition, one can reset boards and query board alarms through the O&M system. One can also set the clock for certain boards through the O&M system. In addition, by checking the operating status of the boards displayed on the LMT, one can be fully aware of the state of the BTS. l Flexible OML configuration In the case of fixed OML configuration, the OML must be configured on timeslot 31 of E1 or timeslot 24 of T1. Any timeslot other than timeslot 31 on the E1 of the upper-level BTS can be allocated to the OML of the lower-level BTSs. This type of configuration meets the requirement in most cases but not in the case of swapping. The OML cannot be configured for the BTS in the case of swapping where the OML of the BTS to be swapped is configured on a timeslot that is different from the timeslot assigned by Huawei GBSS.
This problem can be solved through flexible OML configuration. When the Parameter OML Detection Switch is set to ON, flexible OML configuration is enabled. Before putting the BTS into operation, one configures the data on the BSC side to reserve the E1 timeslots to be used by other transmission devices. During the configuration of OML for the BTS, the OMLs of the BTS and its lower-level BTSs are configured on the timeslots other than those reserved ones, that is the OML can be configured flexibly through the parameter Time Slot No. and Sub Timeslot No.. In this way, the normal operation of the BTS and other transmission devices is ensured.
2.123.4 Parameters
This chapter lists the parameters related to MSC pool. For the meaning of each parameter, see Table 2-288. For the default value, value ranges, and MML commands of each parameter, see Table 2-289. Table 2-288 Parameter description (1) Parameter OML Detection Switch Description If OML Detection Switch is set to OFF, then the OML timeslot automatic detection is not supported. In this case, the OML is carried on the default timeslots. If OML Detection Switch is set to ON, then the OML timeslot automatic detection is supported. In this case, you can run the "SET BTSOMLTS" command to allocate the OML to the specified timeslots. Number of the timeslot on the port. Number of the sub-timeslot on the port.
Time Slot NO. Sub Timeslot No.
Table 2-289 Parameter description (2) Paramet er OML Detection Switch Time Slot NO. Sub Timeslot No. Default Value None GUI Value Range OFF(OFF), ON(ON) Actual Value Range OFF, ON MML Command SET BTSOMLDET ECT (Mandatory) SET BTSOMLTS (Mandatory) SET BTSOMLTS (Mandatory)
Unit None
Impact BSC6900
None
1~31
1~31
None
BTS
None
0(0), 2(2), 4(4), 6(6)
0, 2, 4, 6 None
BTS
Issue 08 (2011-09-30)
1460
2.123.5 Counters
2.123.6 Glossary

l l l l BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference
2.124 O&M of BSC

2.124.1.1 Scope
This document describes the O&M of BSC feature. It covers the functionality of and technologies regarding this feature. This document also includes the architecture and working principle of the O&M of BSC feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the O&M of BSC feature of a specific product version. l
Issue 08 (2011-09-30)
Editorial change
Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-09-30)
2.124.2 Overview
Huawei provides an O&M platform of the BSS system, which fulfills operators' requirement for easy, secure, and effective O&M. The O&M of BSC feature provides the following functions: l l l l l Secure and reliable configuration management Accurate and effective alarm management Comprehensive counter report Flexible and configurable signaling and user message tracing and commissioning Classified log management

2.124.3.1 Basic Architecture
The O&M subsystem can be used to configure, maintain, and manage the entire BSC system. Figure 2-384 shows the basic architecture of O&M of BSC.
Issue 08 (2011-09-30)
1462
Figure 2-384 Basic architecture of O&M of BSC
2.124.3.2 Basic Functions

The graphical interface makes the O&M of BSC feature easy to understand and easy to use. O&M of BSC mainly provides the following functions: configuration management, performance management, alarm management, security management, O&M of board, tracing and monitoring, query of call resources, maintenance of interface and link, and time synchronization.
?.1. Configuration Management

Huawei provides an O&M platform of the BSS system. With O&M of BSC, configuration data can be securely and accurately transmitted to service boards and take effect. For details, see the Configuration Management Feature Parameter Description.
?.2. Performance Management

With performance management for the BSC devices, operators can be well aware of the usage of resources (available resources and occupied resources). By the usage of resources, they can adjust their network and devices and prepare for capacity expansion.For details, see the Performance Management Feature Parameter Description.
?.3. Alarm Management

With BSC alarm management, operators can monitor the operating status of the BSC to obtain fault information in real time and take appropriate measures. Alarm management provides the following functions: l l
Issue 08 (2011-09-30)
Alarm filtering The BSC can filter the repetitive fault alarms, recovery alarms, and event alarms. Alarm shielding
One can shield an alarm by alarm ID. One can also shield a specific alarm or all alarms of a cell, BTS, or board by setting alarm shielding conditions, thus reducing the number of reported derivative alarms. l Alarm prompting The BSC can notify operators of fault alarms by Email, icon flash, phone, short message, terminal sound, audible and visual indication of an alarm box. l Alarm information processing One can browse alarm information in real time, query history alarm information, and handle alarms based on the handling suggestions available from the online help of the BSC. The BSC can store 100, 000 entries of history alarm information generated in the past 90 days.
Alarm Management Mechanism

The alarm management process consists of alarm generation, alarm reporting, and alarm handling. Figure 2-385 shows the alarm management process of the BSC. Figure 2-385 Alarm management process of the BSC
Each board detects alarms and reports them to the OMU automatically. The OMU divides these alarms into different levels and sends them to the LMT or the M2000 server. You can handle these alarms and manage the alarm information on the LMT or the M2000 client. The alarm management module of the OMU provides the following functions: l Alarm storage The alarm management module of the OMU stores the alarms reported by each board in the OMU alarm database. l Alarm handling The alarm management module of the OMU processes the operation commands from the LMT or the M2000 client. These commands include querying active alarms, querying alarm logs, and modifying alarm configuration items.
?.4. Security Management

The BSC security management involves authority management, log management, and inventory management.
Issue 08 (2011-09-30)
1464
Authority Management
The BSC authority management regulates the operation authority of the users (LMT users or M2000 users) that log in to the OMU of the BSC. The users that log in to the BSC are classified into the following types: l Domain users: These user accounts are created, changed, authenticated, and authorized on the M2000. Domain users can manage the BSC after logging in to it through the LMT or after logging in to the M2000 server through the M2000 client. Internal users: There are two default accounts for these users: admin and guest. The user with the account admin is a super-user who has all the operation rights. The user with the account guest only can query data. You cannot delete or modify the two accounts. External users: The external users are created, modified, authenticated, and authorized by the super-user admin or by external users who have corresponding rights. External user accounts are classified into five levels. The user accounts at different levels belong to different functional group. The users can perform only the operations defined in their functional groups. The OMU verifies and controls the operation authority of the external users.
Security management also includes operation time management for NEs. It specifies the operation time of users by date, week, and time segment. One can carry out operations only in the predefined time.
Log Management
Log management records and saves the operations performed by an operator and the running information of the BSC. It also helps in analyzing and locating faults.
Inventory Management
Inventory management provides/enables centralized and effective management for network asset information and key configuration data. In addition, inventory management is a process in which the BSC inventory information files and BTS inventory information files are exported and uploaded. Using this function provided by the M2000, you can learn the physical and logical configurations of the BSC and BTS. NEs report an inventory information file to the inventory management system through related interfaces. This file includes information of the following types: l l l l l l l l l l l l
Issue 08 (2011-09-30)
Equipment basic information Connection information Module information Configuration information Peer equipment information Board version information Cabinet information Subrack information Electronic labels of boards Slot information Port information Antenna information
?.5. O&M of Board

O&M of board involves reset and switchover of boards, monitoring of CPU and DSP, and reset of subracks or the system. You can perform different operations to solve the problems or maintain the system in different situations.
?.6. Tracing and Monitoring

The BSC can trace interface signaling, user signaling messages and system messages. System monitoring involves monitoring and offline browsing of the CPU/DSP usage. A maximum of four objects can be monitored in a task. Multiple monitoring tasks can be performed at the same time. Monitoring of the CPU/DSP usage enables the users to learn about the system load in real time.
?.7. Query of Call Resources

Based on the IMSI or other information about a subscriber provided by the maintenance personnel, the system queries all the resources the subscriber uses in the GSM BSS. These resources include the BTS, sector, TRX, circuits on the Abis interface, Ater interface inside the BSC, A interface, TC resources, and boards. All the information helps maintenance personnel quickly locate problems and faults.
?.8. Maintenance of Interface and Link

Maintenance of interface and link involves the management of LAPD link, SS7 link, and the trunk circuit on each interface. It includes the operations such as querying the status of the LAPD link, SS7 link, and trunk circuit, changing the status of trunk circuit, blocking and unblocking the LAPD link and SS7 link.
?.9. Time Synchronization

Huawei BSC implements the time synchronization with the upper-level NMS through the OMU to complete the synchronization of all NEs managed by a centralized NMS. The OMU distributes the synchronized clock to all the BSC boards to synchronize all the elements of the system. By means of powerful maintenance functions, the maintenance personnel can quickly get familiar with the BSC LMT and master the usage of Huawei equipment to maintain Huawei GSM BSS in a simple and efficient way.
2.124.4 Parameters
None.
2.124.5 Counters
2.124.6 Glossary

2.125 Integrated Network Management Interface

2.125.1.1 Scope
This document describes the functions provided by the integrated network management interface.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Integrated Network Management Interface feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.125.2 Overview
GBSS products access Huawei mobile integrated network management system (NMS) iManager M2000 through the integrated network management interface. The iManager M2000 is a complete set of network management solution launched by Huawei. At the same time, iManager M2000 provides the standard CORBA interface to its upper-level NMS to solve the access problems in the construction of multilevel NMS. iManager M2000 can satisfy the requirements of different operators to implement centralized entire-network management of Huawei mobile equipment.

2.125.3.1 Integrated Network Management Functions
Huawei iManager M2000 mobile NMS has the following functions: l The centralized configuration management function can control the configuration information of the entire network in centralized mode, directly show the configuration information and navigation information, and provide configuration query and browsing, graphical display of subracks and boards, and the configuration data statistics reports. The centralized fault management function can display the operation status of the entire network and provide functions such as real-time alarm indication, alarm acknowledgement/ de-acknowledgement, alarm shielding, alarm work card distribution, alarm correlation analysis, and alarm query. The alarm correlation analysis can reduce redundant reporting of alarm information, so that the maintenance personnel can locate the fault quickly and accurately. The centralized performance management function provides the operation performance data of the network equipment, including the performance item management, graphical display of data, performance alarm setting and other useful functions such as statistics, summarization, and conditional query of the measurement results. The system supports the functions of vector map zooming and accurate NE locating, provides theme maps to display the alarm and performance information of the equipment on the real-time basis, and displays the alarm status of individual NEs and links on the realtime basis through NE icon alarm indicators. Centralized user interface tracing provides functions such as subscriber tracing, interface tracing, and signaling tracing. The system provides powerful intelligent report tool which allows users to customize the report design. In addition, it provides several performance and configuration report templates. Several report output modes are available so that users can obtain the system data for various operations and maintenance. The system features high security. In the system, flexible management of the user rights can be implemented by dividing NEs into subnets, setting the entire-network manager, subnet manager, and entire-network/subnet ordinary users. Illegal access to the network can be avoided through the ID authentication upon user login and logout. Meanwhile, to enhance the data security, the system also provides the data backup and restoration functions, and encrypts the data before transmission. The system can monitor the login users and display the status of each user in the real-time log.
l l
Issue 08 (2011-09-30)
The system provides standard CORBA interface to the upper-level network management system and secondary development interfaces for the third-party software.
2.125.3.2 Northbound Interface

Huawei iManager M2000 mobile NMS has the following northbound interface: l CORBA interface The standard CORBA interface is adopted between iManager M2000 and the upper-level NMS to access the upper-level NMS. l Message/File mode interface iManager M2000 also opens message/file mode interfaces to the upper-level NMS. The specific interfaces opened are as follows: the Sybase database interface provided by the centralized configuration module, the centralized performance module to the upper-level NMS, and the third-party alarm interface provided by the centralized alarm module to the upper-level NMS. l MML interface The MML interface is adopted for the MSC/SSP/IP (128 modules), cBSC/cBTS, cMSC, and SGSN to access iManager M2000 to implement the centralized operation and maintenance. l BIN interface The BIN interface mode is adopted for the MSC/SSP/IP (32 modules), HLR, BSC and cHLR to access iManager M2000 to implement the centralized operation and maintenance. l SNMP interface The combined BIN and SNMP interface is adopted for the PCU and GGSN to access iManager M2000 to implement the centralized operation and maintenance.
2.125.3.3 Network Structure

iManager M2000 consists of the M2000 server, PC terminals and related network equipment. The TCP/IP protocol is adopted for the communication between the iManager M2000 server, PC terminals and various NE equipment to realize the interconnection among equipment, operating systems and topology structures of different types. Figure 2-386 shows the networking of Huawei iManager M2000.
Issue 08 (2011-09-30)
1469
Figure 2-386 Networking of iManager M2000
2.125.4 Parameters
None.
2.125.5 Counters
2.125.6 Glossary

l l l BSC6900 Feature List BSC6900 Basic Feature Description M2000 System Description
2.126 Reporting the Temperature List of the BTS Equipment Room

2.126.1.1 Scope
This document provides an overview of the main functions and goes into details regarding the Reporting the Temperature List of the BTS Equipment Room feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Reporting the Temperature List of the Reporting the Temperature List of the BTS Equipment Room feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.126.2 Overview
With this feature, the temperature in the BTS equipment room can be reported to the BSC at specified intervals in a specific period. In this way, operators learn about the temperature in the equipment room, without entering the equipment room. This feature not only reduces the manpower of the O&M and check, but also helps operators remotely monitor the temperature in the BTS equipment room. In addition, the air conditioner can be remotely adjusted according to the actual situation. In this way, the energy consumption can be reduced and operators achieve the aim of becoming green operators. This feature also
helps find security problems, such as the abnormal temperature change, fire, and exogenetic damage in advance.

Temperature detection is performed by the environment monitoring unit (EMU). The EMU collects the information about the temperature and humidity and then reports the analog values to the GTMU. The GTMU then reports the values to the BSC. In addition, the information about temperature and humidity is displayed on the site maintenance terminal. The EMU does not report the information about the temperature and humidity to the BSC unless the BSC sends a temperature reporting request to the BTS. When the temperature and humidity detection function is started, the user can set the period of reporting the temperature in the equipment room by setting the parameters Monitor Period and Monitor Time. The site maintenance terminal displays whether the reporting of the temperature information of the BTS equipment room is started successfully. The temperature information is reported to the BSC. On the M2000 client, users can download the files of the temperature in the equipment room from the OMU through FTP. In addition, users can also query the temperature information of the equipment room on the M2000 client and save the query results.

To remotely monitor the temperature in the BTS equipment room, run the STR BTSRACKTEMPMON command. In this step, specify BTS Index and Monitor Time, and set Monitor Period to a proper value. When the monitoring period expires, run the DSP BTSENVSTAT command to query the current temperature in the BTS equipment room. The parameter BTS Index specifies the BTS equipment room to be monitored. To stop the remote monitoring of the temperature in the BTS equipment room, run the STP BTSRACKTEMPMON command.
2.126.5 Parameters
This chapter describes the parameters related to Reporting the Temperature List of the BTS Equipment Room. For the description of each parameter, see Table 2-290. For the default value, value ranges, and MML commands of each parameter, see Table 2-291. Table 2-290 Parameter description (1) Parameter Monitor Period Monitor Time Demu Configure Information Subrack No. Description Monitoring period. Monitoring duration. Whether multiple DEMUs are configured. Subrack number of the BSC6900 board that is connected to the DXX.
Issue 08 (2011-09-30)
Parameter Slot No. Result list format
Description Slot number of the BSC6900 board that is connected to the BTS. Query results can be displayed vertically or horizontally.
Table 2-291 Parameter description (2) Defa ult Value None GUI Value Range 30MINS (30 Minutes), 60MINS (60 Minutes), 120MINS (120 Minutes), 240MINS (240 Minutes) 1~1440 Actual Value Range 30MINS, 60MINS, 120MINS, 240MINS MML Command STR BTSRACKTE MPMON (Mandatory)
Parameter Monitor Period
Unit None
Imapct None
Monitor Time
None
1~1440
STR BTSRACKTE MPMON (Mandatory) SET BTSENVAL M (Mandatory) ADD DXXCONNE CT (Mandatory) ADD DXXCONNE CT (Mandatory)
None
Demu Configure Information Subrack No.
None
YES (Configure ), NO(Not Configure) 0~11
YES, NO
None
None
None
0~11
None
BSC690 0
Slot No.
None
0~27
0~27
None
BSC690 0
Issue 08 (2011-09-30)
1473
Parameter Result list format
Defa ult Value HORI ZONT AL
GUI Value Range HORIZON TAL (HORIZO NTAL), VERTICA L (VERTICA L)
Actual Value Range HORIZON TAL, VERTICA L
Unit None
MML Command CMP TBLDATA (Optional)
Imapct None
2.126.6 Counters
2.126.7 Glossary

2.127 Inventory Management

2.127.1.1 Scope
This document describes the principles of the inventory management system (MRFD-210303 Inventory Management). This document includes the feature architecture, basic flow, and primary functions.

It is assumed that users of this document are familiar with GSM/UMTS basics and have a working knowledge of GSM/UMTS telecommunication.
This document is intended for: l l Personnel working on Huawei GSM/UMTS products or systems System operators who need a general understanding of this feature

The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Maintenance Mode Alarm feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.127.2 Overview
Deployed in the M2000, the inventory management system obtains the inventory information from the managed network elements (NEs) through various interfaces. With the inventory management feature, the M2000 provides the centralized management of the information about the physical assets and versions of the devices on the network, thus providing the operator with a uniform and easy method of inventory management. For example, the feature helps the operator to manage the remaining assets or trace the information about the faulty board such as the batch number. The inventory management feature includes the following functions: l l l Collection, summary, and storage of the information about the physical assets and versions GUI-based management, such as display of the inventory data, query by condition, and modification, import, export, and synchronization of the inventory data Collection of the inventory information of the entire network in the format of .xml and reporting of the information to the third-party integrated inventory (assets) management system

The inventory management feature implements integrated and effective management of the information about the physical assets and logical configuration of the entire network.
During routine operation and maintenance, through the inventory management system, the user can query the information about the software and patch version of the equipment and learn about the information about the physical devices and logical configuration (such as a cell). The inventory management system is applied in the following scenarios: l When a device is faulty and the hardware needs to be replaced, the maintenance personnel can obtain the hardware specifications and the place for storing the spare part. This helps the maintenance personnel to carry the appropriate spare part to exchange the faulty hardware on site. As the network devices are aging during the operation, the inventory management system can provide precautions to exchange the device when the normal service life of the device ends. The inventory management system can provide timely and accurate data for service decision in the scenarios such as the fault diagnosis and processing and the system upgrade and expansion. Deployed in the M2000, the inventory management system obtains the inventory information from the managed NEs through various interfaces. Part of the inventory information is manually entered through the inventory management system or imported through other files.
2.127.3.1 Principles of the Inventory Management System

Figure 2-387 shows the procedure for synchronizing the physical information in the device file.
Issue 08 (2011-09-30)
1476
Figure 2-387 Procedure for synchronizing the physical information in the device file
The synchronization procedure is as follows: l l l The M2000 provides the GUI for the user to trigger the device file synchronization. The M2000 server performs file synchronization with the BSC through the FTP. The file name and NE ID are specified and provided by the M2000. Part of the synchronized data serves as the inventory management data and is recoded in the inventory database of the M2000.
2.127.3.2 Electronic Label

The electronic label identifies the object code in the form of electronic data. The electronic label is applied in the make and buy hardware device of Huawei. The inventory management system automatically triggers the query of the electronic labels when triggering the NE to export the device file. Then, the queried electric labels are filled in the corresponding fields in the .xml format. The electric label provided by Huawei includes the following contents: l l
Issue 08 (2011-09-30)
BoardType BarCode
l l l l l l l
Item Description Manufactured VendorName (Huawei) IssueNumber CLEICode BOM
Figure 2-388 shows the interaction between the electronic label and the inventory management system. Figure 2-388 Interaction between the electronic label and the inventory management system (taking the BTS as an example)
The interaction procedure is as follows: l The inventory management system automatically triggers the query of the electronic labels when the BTS exports the device file. Then, the queried electric labels are filled in the corresponding fields in the .xml format. The synchronized inventory information, including the electric label information, is stored in the inventory database of the M2000.

2.127.4.1 Providing Comprehensive Inventory Information
The inventory management system of the M2000 provides the inventory management function for the physical objects and logical objects on the entire network.
l l
The physical objects include racks, frames, slots, boards, ports, and antennas. The logical objects include software/patch, cells (optional), and TRXs (optional).
In addition, the inventory management system manages the manually entered data. The inventory data that cannot be exported is imported to the M2000. The inventory management system provides abundant asset attributes to help the user to obtain the origin, batch number, and number of the legacy boards on the existing network. This facilitates the management of the assets and the tracing of the faults. Figure 2-389 shows the GUI of the inventory management on the M2000. Figure 2-389 GUI of the inventory management
The inventory management system supports the following NE types: BSC6810, BSC6800, CBSC, BSC6000, NodeB3812, SGSN, UAG, HLR, MSC Server, MGW, GGSN80, NodeB3806, NodeB3806A, NodeB3802C, PCU, NodeB3812E, DBS3836, NodeB3836, NodeB3836A, NodeB3836AE, DBS3900 WCDMA, BTS3900 WCDMA, BTS3900A WCDMA, BTS3900AE WCDMA, MSCe, DBS3800, NodeB3812A, NodeB3812AE, ICS, TGW1000, DBS3900 WiMAX, CHLR-SC, CHLR-DC, and pBTS3701.
2.127.4.2 Managing Inventory Information

The inventory management system on the M2000 provides the user with complete graphical interfaces, thus helping the user to directly query the inventory information of the assets on the existing network. The graphical interface clearly lists the data hierarchy, as shown in Figure 2-390.
Issue 08 (2011-09-30)
1479
Figure 2-390 Hierarchy of the NE inventory types of the BSC6000
The inventory data is classified into physical data and logical data. The physical data includes the data about the rack, frame, board, port, and slot. The logical data includes the data about the software version. The BSC6000BTS is a special device and is not a real NE on the M2000. Thus, it is displayed by using a virtual node on the GUI, as shown in Figure 2-391.
Issue 08 (2011-09-30)
1480
Figure 2-391 Inventory hierarchy of the BSC6000BTS
2.127.4.3 Synchronizing Inventory Data

The inventory data synchronization refers to the synchronization of the inventory data in the NE file to the database of the M2000 so that the data of the NE is consistent with the data in the database of the M2000. The synchronization is classified into manual synchronization and periodic synchronization. l Manual synchronization Multiple graphical inventory data synchronization tasks are supported. In addition, one task can involve multiple NEs, as shown in Figure 2-392. l Periodic synchronization When the NE file data is changed, the data can be synchronized to the database of the M2000 when the set inventory management period expires, as shown in Figure 2-393 and Figure 2-394.
Issue 08 (2011-09-30)
1481
Figure 2-392 Manual synchronization involving multiple NEs
Figure 2-393 Common Parameters tab page
Issue 08 (2011-09-30)
1482
Figure 2-394 Extended Parameters tab page
2.127.4.4 Management of the Manually Entered Inventory Data

When a device cannot automatically report the inventory data, you can manually enter the data. The manually entered data is stored in the database of the M2000 but is not delivered to the NE.
?.1. Adding Inventory Data

You can manually enter the inventory data in the following ways: l l l Adding the nodes of the inventory types in batches (the file in .csv and .xml formats are supported) Adding a piece of inventory data at the MOC inventory type node Importing the file in .xml format at the NE node
All the newly entered inventory data is displayed in green on the GUI, as shown in Figure 2-395.
Issue 08 (2011-09-30)
1483
Figure 2-395 New inventory data
?.2. Deleting Inventory Data

You can manually delete the manually entered data (including the data of the subnodes). The data reported by the NE cannot be deleted manually, as shown in Figure 2-396. Figure 2-396 Deleting the manually entered inventory data
?.3. Importing Inventory Data

The inventory data can be imported at the NE node or the MOC inventory type node. l l At the NE node, the data file in only the .xml format can be imported. At the MOC inventory type node, the data file in both the .xml format and the .csv format can be imported.
Issue 08 (2011-09-30)
2.127.4.5 Modifying Inventory Data

For the inventory data reported by the NE, the DateOfLastService of the rack, frame, slot, port, and board can be modified, as shown in Figure 2-397. Figure 2-397 Modifiable fields in the data reported by the NE
For the manually entered data, all the key attribute values (marked by *) cannot be modified, as shown in Figure 2-398. Figure 2-398 Figure 2 Unmodifiable fields in the manually entered data
Issue 08 (2011-09-30)
1485
2.127.4.6 Searching For Inventory Data

When you search for the inventory data, both the data reported by the NE and the manually entered data are displayed on the GUI, as shown in Figure 2-399. Figure 2-399 Searching for inventory data
2.127.4.7 Exporting Inventory Data

The overall inventory data (including the inventory data reported by the NE and the manually entered data) or only the manually entered inventory data can be exported. The inventory data can be exported manually or periodically, as show in Figure 2-400 and Figure 2-401. Figure 2-400 Exporting the inventory manually
Issue 08 (2011-09-30)
1486
Figure 2-401 Exporting the inventory data periodically
2.127.4.8 Flexible Inventory Northbound Interface

The inventory management system can periodically or manually export the inventory data file in the .xml format for the northbound interface. The third-party inventory management system or the NMS can obtain the file in the .xml format through the FTP. The setting of objects and filtering conditions specific to the northbound interface is supported. Thus, the user can preset the assets to be provided and the filtering condition. In this manner, the inventory data that meets the conditions are exported, and then provided for the third-party inventory management system for analysis.
2.127.5 Parameters
None.
2.127.6 Counters
2.127.7 Glossary

None.
2.128 Maintenance Mode Alarm

2.128.1.1 Scope
This document describes the principles and application scenarios of the maintenance alarm management feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Inventory Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.128.2 Overview
When a network is under certain maintenance operations such as construction, expansion, upgrade, or commissioning, some NEs may report a large number of alarms. These alarms are automatically cleared after the maintenance operations are complete. Huawei GBSS9.0 provides the maintenance mode alarm feature to enable you to manage these alarms. This avoids the impacts of such alarms on normal network monitoring and improves network OM efficiency. l Basic Concepts Related to Maintenance Mode Alarms Maintenance mode: The maintenance mode of an NE specifies whether the NE is under maintenance such as construction, expansion, upgrade, or commissioning. Users can
set the maintenance mode of an NE. The maintenance mode of an NE can be released by users or by the M2000. By default, NEs are in normal status, which indicates that no maintenance operation is performed on the NEs. Maintenance mode alarms: The alarms reported by NEs when a network is under certain maintenance operations. These alarms such as reset, switchover, and link disconnection alarms, are of high severities and are automatically cleared after the maintenance operations are complete. To avoid these alarms from affecting normal network monitoring, the M2000 defines all the alarms reported during NE maintenance as maintenance mode alarms and provides a mechanism, through which users can manage these alarms. l Principles of the Maintenance Mode Alarm Feature After the maintenance mode alarm feature is applied, NEs set different identifiers for normal mode alarms and maintenance mode alarms, and then report them to the M2000. Figure 2-402 shows the flowchart of reporting alarms. According to the identifiers, the M2000 adopts a special mechanism for handling maintenance mode alarms. That is, the M2000 does not display maintenance mode alarms by default. Therefore, to monitor maintenance mode alarms, you need to set the conditions for filtering them first. In this case, engineers can concentrate on normal mode alarms. They can also concentrate on maintenance mode alarms to monitor the maintenance progress and status as required. Figure 2-402 Principle diagram of the maintenance mode alarm feature

2.128.3.1 Overview
The maintenance mode alarm feature involves the functions of setting the maintenance mode, monitoring maintenance mode alarms, querying the maintenance mode, and reporting maintenance mode alarms to the NMS through northbound interfaces. This section describes the maintenance mode alarm functions and the GUI display.
2.128.3.2 Setting the Maintenance Mode Function Description

The function of setting the maintenance mode enables users to set an NE to enter or exit the maintenance mode. Table 2-292 describes this function.
Table 2-292 Setting maintenance mode Function Setting an NE to enter the maintenance mode When to Be Used l Users can preset maintenance mode and its duration according to the maintenance plan before maintaining an NE. l During the maintenance of the NE, users can change the maintenance mode of the NE and the duration according to the maintenance progress. Impact When an NE is in maintenance mode, all alarms reported by the NE to the M2000 are identified as maintenance mode alarms. By default, the M2000 does not display maintenance mode alarms. This helps users concentrate on monitoring the normal mode alarms that are generated due to NE faults. Thus, the monitoring efficiency is improved. Users can monitor the reported alarms through the alarm monitoring function. For details about this function, see section 3.3 "Monitoring Maintenance Mode Alarms." Setting an NE to exit the maintenance mode l Automatic: When the preset end time of the maintenance mode reaches, the NE exits the maintenance mode automatically. l Manual: If maintenance operations are finished before the preset end time, users can set the NE to enter the normal mode in the window for setting the maintenance mode. After an NE exits the maintenance mode, the M2000 handles alarms according to the normal handling mechanism. Method Users can set the maintenance mode of multiple NEs at a time. l Users can set an NE to enter the maintenance mode through the M2000 client or by editing a data configuration file. l Users can set an NE to exit the maintenance mode through the M2000 client.
Issue 08 (2011-09-30)
1490
Users can set maintenance mode on the M2000 GUIs. Users can also view information about the maintenance mode in the Maintenance Mode Alarm Filter window. For details about the function of querying the maintenance mode, see
Mechanism for Handling Alarms

According to the maintenance modes, NEs identify the alarms that are generated in different modes and then report them to the M2000. An NE can be in only one mode at a certain point of time. For details about the mechanisms for identifying alarms when the NE mode changes, see Table 2-293. The mechanism for handling maintenance mode alarms is as follows: l l By default, maintenance mode alarms are not displayed on the M2000 alarm monitoring window. Users need to operate the alarms by using a special method. The function of setting an alarm correlation rule is not supported.
Except for the differences, the mechanisms for handling maintenance mode alarms and normal mode alarms are the same. The functions such as setting remote notification, redefining alarm severities, and setting rules for shielding alarms are supported. Table 2-293 Mechanisms for identifying alarms Alarm Identifier Before the Mode Change The generated alarms are identified as normal mode alarms. Alarm Identifier After the Mode Change l The generated alarms are identified as maintenance mode alarms. l The generated alarms are identified as normal mode alarms. l Some maintenance mode alarms are not cleared when an NE changes from maintenance mode to normal mode. In this case, the NE clears these alarms, assigns new serial numbers (SNs) to them but retains their original reporting time, and then reports the alarms as normal mode alarms to the M2000 again.
Mode Change From normal mode to maintenance mode
From maintenance mode to normal mode
The generated alarms are identified as maintenance mode alarms.
Mode Change From maintenance mode A to maintenance mode B
Alarm Identifier Before the Mode Change The generated alarms are identified as the maintenance mode alarms of mode A.
Alarm Identifier After the Mode Change l The generated alarms are identified as the maintenance mode alarms of mode B. l Some maintenance mode alarms are not cleared when an NE changes from maintenance mode A to maintenance mode B. In this case, the NE clears these alarms, assigns new SNs to them but retains their original reporting time, and then reports the alarms as the maintenance mode alarms of mode B to the M2000 again.
Requirements on Operation Rights

If an NE is in maintenance mode, it does not report maintenance mode alarms to the NMS. Thus, the operation rights related to the maintenance mode alarm feature must be strictly controlled. By default, only user admin and the users in the user group Administrators have the operation rights on the maintenance mode alarm feature.
GUI Display
l l l To set an NE to enter the maintenance mode, select the corresponding maintenance mode such as Install, Upgrade, Expand, or Testingfrom the Device Status drop-down list box. To set an NE to exit the maintenance mode, select Normal from the Device Status dropdown list box. Start Time must be later than the current time. Otherwise, setting the maintenance mode of an NE fails.
Figure 2-403 shows the Set Maintenance Mode Alarm Filter window.
Issue 08 (2011-09-30)
1492
Figure 2-403 Set Maintenance Mode Alarm Filter window
2.128.3.3 Querying the Maintenance Mode

The alarms that are reported by an NE in maintenance mode are identified as maintenance mode alarms. The M2000 provides a special mechanism for handling such alarms. Users can learn the maintenance mode of an NE by using the function of querying the maintenance mode.
Function Description
Users can query the maintenance mode of one or more NEs to learn the device type, device status, start time and end time of the maintenance, and device description. By default, an NE is in normal mode, which indicates that no maintenance operations are performed on the NE. After querying the maintenance mode, users can save the query results as a file for future use.
NOTE
The device type of an NE can be physical device or logical unit. A logical unit is a device type dedicated and mapped to a base station. It exists in the base station controller (BSC) and helps the controller to manage the base station.
The query results of the maintenance mode of different NEs are displayed in different ways on the GUI. For details, see Table 2-294.
Issue 08 (2011-09-30)
1493
Table 2-294 Display of query results NE GBTS Display Mode A record is displayed. Reason The GBTS comprises of a physical device and a logical unit, and it communicates with the M2000 through the BSC. The BSC is a physical device.
GBSC
A record is displayed.
GUI Display
Figure 2-404 shows the Query Maintenance Mode Alarm Filter dialog box. Figure 2-404 Query Maintenance Mode Alarm Filter dialog box
2.128.3.4 Monitoring Maintenance Mode Alarms

By default, the M2000 does not display the maintenance mode alarms reported by an NE that is in maintenance mode. Users can monitor the maintenance progress by monitoring maintenance mode alarms reported by the NE.
Function Description
The M2000 provides various alarm-related operations, which enable users to quickly detect, locate, and rectify network or device faults. By default, maintenance mode alarms are not displayed in the operation results. Therefore, users need to set the conditions for filtering the maintenance mode alarms before performing relevant operations on these alarms.

NOTE
The mechanisms for handling maintenance mode alarms and for handling normal mode alarms are the same except that maintenance mode alarms do not support the correlation rule and that special filtering conditions need to be set. For details about alarm-related operations, see the M2000 Operator Guide.
GUI Display
Figure 2-405 shows the Filter and Advance dialog boxes. Users need to set the Special Status parameter in the Advance dialog box to ensure that the corresponding maintenance modes are included in the special status. Figure 2-405 Filter and Advance dialog boxes
2.128.3.5 Enabling the M2000 to Report Maintenance Mode Alarms to the NMS
By default, the M2000 does not report maintenance mode alarms to the NMS. If users need to monitor maintenance mode alarms through the NMS, they can enable the M2000 to report maintenance mode alarms to the NMS through northbound interfaces. For details about this function, see Table 2-295.
Issue 08 (2011-09-30)
1495
Table 2-295 Enabling the M2000 to report maintenance mode alarms to the NMS Function Enabling the M2000 to report maintenance mode alarms to the NMS When to Be Used l In the network planning stage, users need to determine whether maintenance mode alarms are reported to the NMS. If maintenance mode alarms need to be reported to the NMS, enable the M2000 to report maintenance mode alarms to the NMS when the M2000 is connected to the NMS. l If users need to adjust the policy for reporting maintenance mode alarms after the M2000 is connected to the NMS, change the relevant settings on the M2000. Impact If this function is enabled, the NMS can receive the maintenance mode alarms of all NEs. Otherwise, the NMS can receive only the normal mode alarms of the NEs.
NOTE After this function is enabled, users need to restart relevant services.
Method For details about the operations, see the corresponding northbound interface development guide. The setting is applied to all NEs, including the NEs that are added subsequently.
2.128.4 Networking
Figure 2-406 shows the typical networking mode of the maintenance mode alarm feature. Figure 2-406 Typical networking mode of the maintenance mode alarm feature
Issue 08 (2011-09-30)
1496
All the alarms in a GBSS network are reported to the M2000 through the BSC. The maintenance mode of the BSC and BTSs are saved in the BSC. Upon receiving the alarms reported by BTSs, the BSC identifies whether the alarms are maintenance mode alarms according to the identifiers saved in the BSC. After users run MML commands to set the maintenance mode of BTSs, the commands are sent to the BSC and executed on the BSC side.
2.128.5 Parameters
For the description of each parameter related to the maintenance mode alarm feature, see Table 2-296. For the default values, value ranges, and MML commands, see Table 2-297. Table 2-296 Parameter (1) Parameter Start Time Description Start time of the maintenance mode of an NE. The format is MM/DD/ YYYY HH:MM:SS. If Start Time is not selected, infer that the NE enters the maintenance mode immediately. End Time Device Status Device Description End time of the maintenance mode of an NE. The format is MM/DD/ YYYY HH:MM:SS. The maintenance mode of an NE. Users can select a maintenance mode from the Device Status drop-down list box. Description of the device that enters the maintenance mode.
Table 2-297 Parameter (2) Parameter Start Time Default Value Current time GUI Value Range Any time between the current time and 23:59 on 2038-12-31. Actual Value Range Any time between the current time and 23:59 on 2038-12-31. Any time between the current time and 23:59 on 2038-12-31. It must be later than the start time. Normal, Install, Expand, Upgrade, and Test. Unit None Impact Maintenan ce mode of the NE
End Time
An hour later than the current time
Any time between the current time and 23:59 on 2038-12-31. It must be later than the start time.
None
Maintenan ce mode of the NE
Device Status
Normal
Normal, Install, Expand, Upgrade, and Test.
None
Maintenan ce mode of the NE
Issue 08 (2011-09-30)
1497
Parameter Device Description
Default Value N/A
GUI Value Range A character string less than or equal to 60 characters.
Actual Value Range A character string less than or equal to 60 characters.
Unit None
Impact Maintenan ce mode of the NE
2.128.6 Counters
2.128.7 Glossary

2.129 Multi-Cell Function

2.129.1.1 Scope
This document describes the multi-cell function.


There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Multi-Cell Function feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.129.2 Overview
Multi-cell function is a function based on which more than three cells (12 at most) are configured for a single BTS to improve system capacity. Multi-cell function meets the requirement of various networking scenarios, especially the dual-band networking. Multi-cell function helps save the CAPEX.

In some special scenarios, more than three cells are required for a single BTS. In a GSM900/ DCS1800 dual-band network, the configurations of GSM900 Sx/x/x and DCS1800 Sy/y/y are usually required: In this case, six cells are required for the BTS. In Huawei GBSS, one BTS supports up to 12 cells and meets the requirements of special networking scenarios, especially the dual-band networking. This saves the CAPEX.

This chapter provides engineering guidelines regarding the configuration of multi-cell function. To enable the multi-cell function, perform the following steps: 1. 2. 3. 4. 5. 6. 7. 8. 9.
Issue 08 (2011-09-30)
Run the ADD BTSRXUCHAIN command to add an RXU chain. Run the ADD BTSRXUBRD command to add an RXU board. Run the ADD GCELL command to add a GSM cell. Run the ADD GCELLFREQ command to add frequencies to the GSM cell. Run the ADD GTRX command to add a TRX. Run the ADD TRXBIND2PHYBRD command to bind the TRX to the BTS board. Run the ACT GCELL command to activate the GSM cell. After the cell configuration is complete, perform a dial test. If the call gets through, the cell is established. To deactivate or remove the cell, perform the following steps:
10. Run the DEA GCELL command to deactivate the GSM cell 11. Run the RMV GCELL command to remove the GSM cell.
2.129.5 Parameters
None.
2.129.6 Counters
2.129.7 Glossary

2.130 Satellite Transmission

2.130.1.1 Scope
This document introduces the Satellite Transmission feature of Huawei GSM Base Station Subsystem (BSS) and describes the function and principle of satellite transmission, including satellite transmission over A, Abis, Ater, Pb, and Gb interfaces.


There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Satellite Transmission feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.130.2 Overview
Satellite transmission uses a satellite for telecommunications and is very useful in remote mountain areas or sparsely populated plains. MOC. Aiming at characteristics of satellite transmission, Huawei BSS solves the problems such as delay, jitter, and bit error in satellite transmission through the optimization of signaling procedures and the adjustment of relevant timers.
NOTE
The delay in satellite transmission may worsen the performance counters such as call drop rate, handover success rate, and assignment success rate.
Huawei BSS supports simultaneous satellite transmission over multiple interfaces, including l l l l l Satellite transmission over A interface Satellite transmission over Ater interface Satellite transmission over Abis interface Satellite transmission over Pb interface Satellite transmission over Gb interface

2.130.3.1 Network Topologies of Satellite Transmission
Huawei BSS supports satellite transmission over multiple interfaces. Satellite transmission over the Abis interface is widely used. The networking of satellite transmission over the Abis interface often uses star topology. Figure 2-407 shows a typical networking of satellite transmission.
NOTE
The principle of satellite transmission over the Abis interface, Ater interface, Pb interface, and Gb interface is the same as that over Abis interface.
Issue 08 (2011-09-30)
1501
Figure 2-407 Typical networking of satellite transmission
The satellite communication is composed of a communications satellite and earth stations. MTC procedure. The communications satellite is usually a geosynchronous satellite, which orbits the equator. The satellite orbits in the same direction as that of the earth rotation. It takes the same time for the satellite to orbit the earth for one circle and the earth to rotate on its own axis for one circle. The satellite is composed of the control system, communication system (antennas and repeaters), telemeter system, power supply system, and temperature control system. The earth station is composed of the antenna system, transceiver, channel terminal (modem), communication control system, and power supply system. l The earth station generally used for satellite transmission is a large international or European standard communication station, which features high data rate, large aperture, and high cost. User data converges on the earth station through the terrestrial communication network for communication with the satellite. The Very Small Aperture Terminal (VSAT) is an earth station that constitutes a private network. In the VSAT, subscribers under different BTSs use their separate earth stations for communication. The VSAT features lower cost, smaller aperture, and more flexible deployment.
2.130.3.2 Satellite Transmission over the Abis Interface

Satellite transmission mainly differs from common terrestrial transmission in the delay problem. Radio wave travels at the speed of light and the satellite is about 80,000 km away from the earth. The unidirectional transmission delay in satellite transmission thus is about 270 ms and the round-trip delay is about 540 ms. Satellite transmission may cause problems such as delay, jitter, and bit error, so common GSM equipment does not support satellite transmission. Based on the characteristics of satellite transmission, the BSC6900 adjusts accordingly by sending configuration requirements to the LAPD and the BTS. By sending transmission mode to the BTS, the BSC6900 enables the BTS
to internally differentiate transmission mode and implement control at the link level. The details are as follows: l Processing of the LAPD During the processing of the LAPD, the timer length is prolonged and the value of the sliding window is increased to eliminate the impact of transmission delay. When satellite transmission is chosen, the sliding window automatically updates its value to the corresponding value of satellite transmission and users can modify the value as practically required. l TRAU frame adjustment The adjustment algorithm of TRAU frames is changed from adjustment at a fixed period to adaptive adjustment. l Operating mode of the BTS clock To work with satellite transmission, the BSC supports the internal clock of the BTS in compliance with GSM protocol requirements of clock precision. l BTS supporting satellite transmission Huawei BTS supports satellite transmission and automatically updates data on the link layer according to the transmission mode requirement sent from the BSC.
2.130.3.3 Satellite transmission over the A interface

On the BSC6900, the transmission mode of the MTP3 link over the A interface supports satellite transmission. When satellite transmission over A interface is used, data on the control panel over the A interface updates automatically to eliminate the impact of long delay in satellite transmission.
2.130.3.4 Satellite transmission over the Ater interface

In BSC6900, the transmission mode of the signaling link over the Ater interface supports satellite transmission. When satellite transmission over the Ater interface is used, the timer length of the signaling link over the Ater interface automatically prolongs and the value of the sliding window can be modified as practically required to adapt to the delay in satellite transmission.
2.130.3.5 Satellite transmission over the Pb interface

The link layer on the Pb interface adopts the Link Access Procedure-D channel (LAPD) protocol. The processing of the LAPD over the Pb interface is the same as that over the Abis interface.
2.130.4 Parameters
This chapter describes the parameters related to satellite transmission. For the description of each parameter, see Table 2-298. For the default value, value ranges, and MML commands of each parameter, see Table 2-299.
Issue 08 (2011-09-30)
1503
Table 2-298 Parameter description (1) Parameter Transmission Mode Description The Ater signaling link operates in the terrestrial transmission or satellite transmission mode. In the areas such as desert and lake where the terrestrial transmission is difficult, the satellite transmission can be used. Satellite flag. Clock mode. Size of the RSL LAPD window. Whether to allow SDCCH dynamic allocation, that is, whether to allow dynamic conversion between TCHs and SDCCHs. This parameter specifies the timeout value of timer T200 used for the SDCCH over the Um interface. T200 prevents the data link layer from deadlock during data transmission. The data link layer transforms the physical link that is vulnerable to errors into a sequential non-error data link. The entities at the two ends of this data link use the acknowledgement retransmission mechanism. Each message must be confirmed by the peer end. In unknown cases, both ends are waiting if a message is lost. At this time, the deadlock of the system occurs. Therefore, the transmit end must establish a timer. When the timer expires, the transmit end regards that the receive end does not receive the message and then the transmit end retransmits the message. The number of retransmissions is determined by N200. T200 and the N200 ensure that the data link layer sequentially transmits data and that the transmission is free from errors. This parameter specifies the expiry value of timer T200 used for the SACCH on the SDCCH. For the function of timer T200 and the effect of the parameter, see the description of "T200 SDCCH". This parameter specifies the expiry value of timer T200 when the SDCCH supports SAPI3 services. For the function of timer T200 and the effect of the parameter, see the description of "T200 SDCCH".
Satellite flag Clock Mode RSL LAPD Window Size SDCCH Dynamic Allocation Allowed T200 SDCCH
T200 SACCH SDCCH
T200 SDCCH SAPI3
Issue 08 (2011-09-30)
1504
Parameter MS MAX Retrans
Description Maximum number of Channel Request messages that can be sent by an MS in an immediate assignment procedure. After the MS initiates the immediate assignment procedure, it always listens to the messages on the BCCH and all the common control channels (CCCHs) in the CCCH group to which the MS belongs. If the MS does not receive Immediate Assignment or Immediate Assignment Extend messages, it retransmits Channel Request messages at a specified interval. If the downlink quality is poor, the MS may send SABM frames to the BTS multiple times. T3168 is used to set the maximum duration for the MS to wait for the uplink assignment message. After the MS originates the uplink TBF setup request by sending the packet resource request or the channel request in the packet uplink acknowledge message, the timer T3168 is started to wait for the packet uplink assignment message on the network side. If the MS receives the packet uplink assignment message before T3168 expires, T3168 is reset. Otherwise, the MS originates the packet access request for four times. Then the MS regards this as the TBF setup failure. Duration of releasing the TBF after the MS receives the last data block. When the MS receives the RLC data block containing the flag identifying the last data block and confirms that all the RLC data blocks in the TBF are received, the MS sends the packet downlink acknowledge message containing the last flag acknowledgement and the timer T3192 is started. If the timer T3192 expires, the MS releases the TBF related resources and starts monitoring the paging channel. During TBF releasing, if the MS is the half duplex mode and receives the packet uplink assignment, the MS responds this command. During TBF releasing, if the MS is the half duplex mode and receives no packet uplink assignment message, the MS enters the packet idle mode. If the MS is in the dual transmission mode, the MS enters the special mode.
T3168
T3192
Issue 08 (2011-09-30)
1505
Parameter BS_CV_MAX
Description This parameter is used to set the parameter BS_CV_MAX for MS countdown. This parameter is used for the MS to calculate the CV. This parameter also determines the duration of the timer T3198. When the MS sends one uplink RLC data block, the receiving state of this data block is set to Pending and the timer T3198 is started. If the MS receives the packet uplink acknowledge before the timer T3198 expires, the MS updates the receiving state of each uplink RLC data block according to the bit map in the message. If the timer T3198 of the RLC data block in the Pending state expires, the MS sets the receiving state of this data block to Nack and retransmits the data bloc.
Table 2-299 Parameter description (2) Default Value TRRS GUI Value Range TRRS (Terrestrial Transmission ), SATEL (Satellite Transmission ) NO (NO),YES (YES) Actual Value Range TRRS, SATEL MML Command ADD ATERSL (Optional) ADD ATERCONS L(Optional) NO, YES None ADD MTP3LNK (Optional) MTP3 link
Parameter Transmissi on Mode
Unit None
Impact ATERCO NSL
Satellite flag
NO
Issue 08 (2011-09-30)
1506
Parameter Clock Mode
Default Value None
GUI Value Range INCLK (Internal Clock), BSCCLK (Trace BSC Clock), EXCLK (External Synchro Clock), IPCLK(IP Clock), TRANSCLK (Trace Trans Clock), GPSCLK (Trace GPS Clock), UMCLK (Um Clock), PEERCLK (PEER Clock) 0~96
Actual Value Range INCLK, BSCCL K, EXCLK , IPCLK, TRANS CLK, GPSCL K, UMCL K, PEERC LK
Unit None
MML Command SET BTSCLKPA RA (Mandatory)
Impact None
RSL LAPD Window Size SDCCH Dynamic Allocation Allowed T200 SDCCH
0~96
None
SET BTSLAPDW S(Optional) SET GCELLBAS ICPARA (Optional) SET GCELLCCT MR (Optional) SET GCELLCCT MR (Optional) SET GCELLCCT MR (Optional)
BTS
YES
NO(No), YES(Yes)
NO, YES
None
Cell
60
1~255
5~1275, step: 5
ms
Cell
T200 SACCH SDCCH T200 SDCCH SAPI3
60
1~255
10~255 0, step: 10 5~1275, step: 5
ms
Cell
60
1~255
ms
Cell
Issue 08 (2011-09-30)
1507
Default Value 4_Times
GUI Value Range 1_Times (1_Times), 2_Times (2_Times), 4_Times (4_Times), 7_Times (7_Times) 500ms (500ms), 1000ms (1000ms), 1500ms (1500ms), 2000ms (2000ms), 2500ms (2500ms), 3000ms (3000ms), 3500ms (3500ms), 4000ms (4000ms) 0ms(0ms), 80ms(80ms), 120ms (120ms), 160ms (160ms), 200ms (200ms), 500ms (500ms), 1000ms (1000ms), 1500ms (1500ms) 0~15
Actual Value Range 1_Times , 2_Times , 4_Times , 7_Times 500ms, 1000ms, 1500ms, 2000ms, 2500ms, 3000ms, 3500ms, 4000ms
Unit None
MML Command SET GCELLCCB ASIC (Optional)
Impact Cell
T3168
500ms
ms
SET GCELLPSB ASE (Optional)
Cell
T3192
500ms
ms
Cell
BS_CV_M AX
10
0~15
None
Cell
2.130.5 Counters
2.130.6 Glossary

2.131 NAT Beside OM

2.131.1.1 Scope
This document describes the NAT Beside OM feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the NAT Beside OM feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
This is the first commercial release of GBSS9.0
2.131.2 Overview
With this feature, the Network Address Translation (NAT) firewall is deployed on the LMT side and the M2000 side to maintain the network security without affecting the normal connections between devices. Firewall is a basic technology to ensure the network security. The NAT firewall protects the internal network by hiding the internal network address through the NAT technology. In this manner, the network security is enhanced. According to the actual requirements, the customer can deploy the NAT firewall as follows: l l Deploy the NAT firewall on the M2000 to protect the M2000 against the attack from the network. Deploy the NAT firewall on the LMT so that multiple LMTs on the same network segment are connected to the BSC by using the same IP address, thus saving the public network IP resources.
To guarantee the network security of the GBSS system, the NAT firewall needs to be deployed between the BSC and the LMT or the M2000. The NAT technology converts the IP address in the IP header to another IP address. Through the NAT firewall, the IP address and port number in the IP packet of the network device are changed. The BSC and LMT/M2000 are interconnected. When one side initiates the connection, the connection cannot be normally set up because the new IP address and port number of the other side are unknown. Figure 2-408 Networking mode of NAT Beside OM
The NAT conversion is performed in the following scenarios: l The connection setup request is sent by the M2000 to the BSC. In this case, the M2000 uses a BSC IP address after NAT conversion to set up the connection to the BSC.
Issue 08 (2011-09-30)
If the BSC needs to set up an FTP connection to the M2000, the M2000 provides the IP address of the M2000 server after NAT conversion to the BSC through an MML command. Then, the BSC sets up a connection to the M2000 by using the IP address of the M2000 server after NAT conversion. When the M2000 works as a time synchronization server for the BSC. In this case, the BSC configures the IP address of the M2000 server after NAT conversion as the IP address of the time synchronization server.

Configuring the NAT Table
This feature consists of two phases: configuring the NAT table and converting IP address. Users must first prepare the NAT table, and then import the NAT table to the M2000 database by using the import tool of the M2000. Before importing the new NAT table, the import tool clears the original NAT table automatically. During the NAT table import, the M2000 checks the validity of the IP address. l l If the NAT table is null, the table is labeled "<null>" in the database. If the data in the NAT table is invalid, the table is labeled "invalid" in the database.
Implementing IP Address Conversion

Before setting up a connection to the BSC, the M2000 sends the original IP address and the visit mode (from M2000 to BSC or from BSC to M2000) to the NAT interface. After the IP address is converted based on the NAT table, the converted IP address is used for the connection. If the NAT table is not configured, the M2000 connects to the BSC by using the original IP address.
2.131.4 Parameters
None.
2.131.5 Counters
2.131.6 Glossary

l l l BSC6900 Feature List BSC6900 Optional Feature Description M2000 Commissioning Guide
2.132 Radio Common Channel Management

2.132.1.1 Scope
This document describes signaling procedures, such as channel request by MS and assignment. It also describes common channel management.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Radio Common Channel Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
02 (2010-07-15)
This is the second commercial release of GBSS9.0. Compared with issue 01(2010-01-20) of GBSS9.0, issue 02 (2010-07-15) of GBSS9.0 incorporates the changes described in the following table. Change Type Feature change
Issue 08 (2011-09-30)
Change Description Multiple CCCHs is added.
1512
01 (2010-01-20)
2.132.2 Overview
Radio common channel management involves the management of common control channels such as PCH, RACH, AGCH, NCH, PPCH, PRACH, and PAGCH. Radio common channel management is a basic feature for the operators to provide CS speech services. l Common control channels Common control channels include PCH, RACH, AGCH, NCH, PPCH, PRACH, and PAGCH. Paging Channel (PCH): Downlink channel. The MS listens to the PCH at intervals to determine whether there is a call request from the MSC. Random Access Channel (RACH): Uplink channel: The MS accesses the network through the RACH and requests the network to assign an SDCCH. Access Grant Channel (AGCH): Downlink channel. The network informs the MS of the assigned dedicated channel (SDCCH or TCH) through the AGCH. Notification Channel (NCH): Downlink channel, used for voice group call service (VGCS) and voice broadcast service (VBS). Packet Paging Channel (PPCH): Downlink channel. The MS listens to the PPCH at intervals to determine whether there is a packet request from the SGSN. Packet Random Access Channel (PRACH): Uplink channel. The MS requests network access through the PRACH. l Radio common channel management The radio common channel management procedures involve the signaling procedures of MS access and assignment, and also the resource management of the common channel. The involved procedures are Channel Request by MS, Paging, Delete Indication, CCCH Load Indication, Broadcast Information Modify, Short Message Cell Broadcast, Immediate Assignment, and Notification.

2.132.3.1 Channel Request by MS
The procedure is initiated by a TRX upon detection of a random access from an MS (CHANNEL REQUEST message from MS). The TRX then sends a CHANNEL REQUIRED message to the BSC containing the Request Reference parameter (random number selected by the MS plus some low order bits of the TDMA frame number for the access) and the measured delay of the Access Burst. The number of access conflicts on RACHs during MS access can be reduced by adjusting the values of TX-integer and MS MAX Retrans, thus increasing the RACH utilization.
2.132.3.2 Paging
This procedure is used to request the paging of one mobile station on a given paging subchannel. The paging of an MS is initiated by the BSC sending a PAGING COMMAND message to the BTS. The message contains the MS identity (TMSI or IMSI), the paging population number of the MS, optionally an indication for the MS about which combination of channels will be needed for the subsequent transaction related to the paging and optionally an indication of the eMLPP priority of the call. The PAGING REQUEST messages to be sent on the radio path are built and sent by the BTS. The parameter CCCH Blocks Reserved for AGCH determines the CCCH usage for the AGCH and the PCH and thus affects the system performance and the paging response time of MSs. The parameter Multi-Frames in a Cycle on the Paging CHdetermines the paging response delay and the MS power consumption. The paging success rate can be improved by setting Paging Times to a proper value.
In common cases, one cell is configured with one BCCH physical channel, which is configured on timeslot 0 of the BCCH TRX. The feature of Multiple CCCHs also allows one to configure timeslots 2, 4, and 6 of the BCCH TRX as BCCH physical channels. These BCCH physical channels can be divided into the BCCH, PCH, and AGCH in the downlink, and the RACH in the uplink. Messages sent on the BCCH logical channel are exactly the same no matter they are sent on timeslots 0, 2, 4, or 6. Messages sent on the PCH, AGCH, and RACH, however, can be different on timeslots 0, 2, 4, and 6. Thus, more messages can be sent on the PCH, AGCH, and RACH, and configuring multiple BCCH physical channels expands the CCCH capacity. The BSC broadcasts the configured number of CCCHs to the MS in system information type 3 messages. The MS determines on which timeslot to monitor the paging message based on its IMSI. Uplink BCCH physical channels are all RACHs, so configuration of multiple CCCHs increases the number of RACHs in the cell. Thus, Multiple CCCHs also improves the random access capability of the cell.
2.132.3.3 Delete Indication

This procedure is used by the BTS to indicate that due to overload on the downlink CCCH, an IMMEDIATE ASSIGN COMMAND has been deleted. For that purpose , the BTS sends a DELETE INDICATION message to the BSC.
2.132.3.4 CCCH Load Indication

This procedure is used by a BTS to inform the BSC of the load on a particular CCCH timeslot. The CCCH LOAD INDICATION message is sent regularly from the BTS to the BSC if the load exceeds some value set by O&M. The sending rate is also set by O&M.
2.132.3.5 Broadcast Information Modify

This procedure is used by the BSC to indicate to the BTS the new information to be broadcast on BCCH. For that purpose, the BSC sends a BCCH INFORMATION message to the BTS.
2.132.3.6 Short Message Cell Broadcast

Short Message Service Cell Broadcast messages are sent to the BTS as SMS BROADCAST COMMAND messages. With the SMS BROADCAST COMMAND mode of operation, the BSC can request the broadcast of a complete Cell Broadcast message. The BSC handles the queuing, repetition and transmission of the messages taking the capacity of the CBCHs (basic and extended channel [see 3GPP TS 45.002]) into account. The BSC is responsible for the segmentation of the SMS Cell Broadcast messages on the Radio interface:
2.132.3.7 Immediate Assignment

This procedure is used by the BSC to request the transmission of an IMMEDIATE ASSIGN Message on downlink CCCH. To initiate the immediate assign, the BSC sends an IMMEDIATE
ASSIGN COMMAND message. The message contains the complete immediate assign message as defined in 3GPP TS 44.018 (IMMEDIATE ASSIGNMENT or IMMEDIATE ASSIGNMENT REJECT)with the "Page Mode" element set to the value "no change". The IMMEDIATE ASSIGNMENT REJECT message is either sent by the BTS as received in the IMMEDIATE ASSIGN COMMAND message or built by the BTS from the contents of two or more IMMEDIATE ASSIGN COMMAND messages. For the latter case the BTS may consider request references with identical contents within the same message as duplicates and all but one may be suppressed.
2.132.3.8 Notification
This procedure is used to request that notification be performed by the BTS. The BSC indicates the exact action required by the BTS in the command indicator. The NOTIFICATION messages to be sent on the radio path are built and sent by the BTS. The BSC manages the NCH DRX information whereas the BTS manages the scheduling of the messages on the NCH.
If the BTS for some reason cannot perform the notification commanded by the BSC, then the BTS should return an ERROR REPORT message with the relevant cause value.
2.132.4 Parameters
This chapter describes the parameters related to Radio Common Channel Management. For the description of each parameter, see Table 2-300. For the default value, value ranges, and MML commands of each parameter, see Table 2-301.
Issue 08 (2011-09-30)
1516
Table 2-300 Parameter description (1) Parameter RTTI PDCH Multiplex Threshold Description Maximum number of RTTI TBFs that can be multiplexed on the PDCH. A PDCH can be assigned when the number of RTTI TBFs on it is smaller than the value of this parameter. This parameter is valid only when its value is smaller than or equal to "MSRD PDCH DL Multiplexing Threshold". Tx-integer (T for short). This parameter specifies the number of timeslots between two transmissions when an MS sends multiple consecutive channel requests. The access algorithm is defined in GSM Rec. 04.08 to reduce the collisions on the RACH and improve the efficiency of the RACH. The algorithm specifies three parameters: Tx-integer (T for short), maximum number of retransmissions (RET), and S related to channel combination. This parameter works with the configuration of the CCCH to determine the parameter S. The relations between this parameter and the configuration of the CCCH are as follows: When this parameter is set to 3, 8, 14, or 50, S is 55 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 3, 8, 14, or 50, S is 41 if the CCCH and SDCCH share a physical channel. When this parameter is set to 4, 9, or 6, S is 76 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 4, 9, or 6, S is 52 if the CCCH and SDCCH share a physical channel. When this parameter is set to 5, 10, or 20, S is 109 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 5, 10, or 20, S is 58 if the CCCH and SDCCH share a physical channel. When this parameter is set to 6, 11, or 25, S is 163 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 6, 11, or 25, S is 86 if the CCCH and SDCCH share a physical channel. When this parameter is set to 7, 12, or 32, S is 217 if the CCCH and SDCCH do not share a physical channel. When this parameter is set to 7, 12, or 32, S is 115 if the CCCH and SDCCH share a physical channel. The timeslot for sending messages is a random value from the collection of {0, 1..., MAX(T, 8)-1}. The number of timeslots (excluding the timeslot used to send messages) between two adjacent channel request messages is a random value from the collection of {S, S+1, ..., S+T-1}. When T increases, the interval between two adjacent channel requests increases, and RACH conflicts decrease. When S increases, the interval between two adjacent channel request messages increases, and RACH conflicts decrease, thus improving the usage of AGCH and SDCCH. The access time of the MS, however, is prolonged and the network performance is decreased when T and S increase. Under normal conditions, an appropriate T value should be used to ensure that S is as low as possible, and ensure that AGCH and SDCCH are not overloaded.
TX-integer
Issue 08 (2011-09-30)
1517
Description Maximum number of Channel Request messages that can be sent by an MS in an immediate assignment procedure. After the MS initiates the immediate assignment procedure, it always listens to the messages on the BCCH and all the common control channels (CCCHs) in the CCCH group to which the MS belongs. If the MS does not receive Immediate Assignment or Immediate Assignment Extend messages, it retransmits Channel Request messages at a specified interval. If the downlink quality is poor, the MS may send SABM frames to the BTS multiple times. BS-AG-BLKS-RES, indicating the number of the CCCH message blocks reserved for the AGCH. After the CCCHs are configured, the value of this parameter indicates the actual seizure rates of the AGCHs and the PCHs over the CCCHs. Number of multiframes in a cycle on a paging sub-channel. In fact, this parameter specifies the number of paging subchannels that a paging channel in a cell is divided into. In an actual network, an MS does not listen to other paging subchannels but its belonging paging sub-channel only. Refer to GSM Rec. 05.02 and GSM Rec. 05.08. The larger the value of this parameter, the more the number of the paging sub-channels in a cell, and the fewer the number of the users belonging to each paging sub-channel. In this case, the mean uptime of the MS battery can be prolonged. Refer to the computing mode of paging group in GSM 05.02 of GSM Standards. The larger the value of this parameter, however, the larger the time delay of a paging message in a space segment. Thus, the average service performance of the system lowers. Based on the principle of ensuring that overload does not occur to paging channels, you must set this parameter to a value as small as possible. You must regularly measure the overload conditions of the paging channels in a running network and accordingly adjust the value of this parameter properly. A paging message in a location area must be sent in all the cells within this location area at the same time. Therefore, the capacity of a paging channel of each cell in a location area must be the same or nearly the same. The capacity refers to the calculated number of paging subchannels of each cell. For the BTS, this parameter is used to determine paging retransmissions. This parameter and the number of paging times configured in the MSC determine the number of paging retransmissions. The total number of paging times is approximately equal to the value of this parameter multiplied by the number of paging times configured in the MSC.
Paging Times
Issue 08 (2011-09-30)
1518
Table 2-301 Parameter description (2) Default Value 30 GUI Value Range 10~80 Actual Value Range 10~80 MML Comman d SET GCELLPS CHM (Optional) SET GCELLID LEBASIC (Optional)
Parameter RTTI PDCH Multiplex Threshold TX-integer
Unit None
Imapct Cell
TX_32
TX_3(3), TX_4(4), TX_5(5), TX_6(6), TX_7(7), TX_8(8), TX_9(9), TX_10(10), TX_11(11), TX_12(12), TX_14(14), TX_16(16), TX_20(20), TX_25(25), TX_32(32), TX_50(50) 1_Times (1_Times), 2_Times (2_Times), 4_Times (4_Times), 7_Times (7_Times) 0~7
TX_3, TX_4, TX_5, TX_6, TX_7, TX_8, TX_9, TX_10, TX_11, TX_12, TX_14, TX_16, TX_20, TX_25, TX_32, TX_50 1_Time s, 2_Time s, 4_Time s, 7_Time s 0~7
None
Cell
MS MAX Retrans
4_Times
None
SET GCELLCC BASIC (Optional)
Cell
None
SET GCELLID LEBASIC (Optional)
Cell
Issue 08 (2011-09-30)
1519
Parameter Multi-Frames in a Cycle on the Paging CH
Default Value 2_M_PERI OD
GUI Value Range 2_M_PERI OD(2 Multiframe Period), 3_M_PERI OD(3 Multiframe Period), 4_M_PERI OD(4 Multiframe Period), 5_M_PERI OD(5 Multiframe Period), 6_M_PERI OD(6 Multiframe Period), 7_M_PERI OD(7 Multiframe Period), 8_M_PERI OD(8 Multiframe Period), 9_M_PERI OD(9 Multiframe Period) 1~8
Actual Value Range 940~42 30, step: 470
Unit ms
MML Comman d SET GCELLID LEBASIC (Optional)
Imapct Cell
Paging Times
1~8
None
SET GCELLCC BASIC (Optional)
Cell
2.132.5 Counters
2.132.6 Glossary

l l l l l l l 3GPP TS 48.058 V7.0.0 3GPP TS 45.058 3GPP TS 44.018 BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference
2.133 Radio Dedicated Channel Management

2.133.1.1 Scope
This document describes procedures such as channel activation, channel mode modify, and handover detection involved in radio dedicated channel management.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Radio Dedicated Channel Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
01(2010-01-12)
2.133.2 Overview
Radio dedicated channel management involves the assignment, activation, release, management, and reporting of dedicated channels such as SDCCH, SACCH, and TCH. These procedures work together to establish, maintain, and release radio links.

2.133.3.1 Overview
Radio dedicated channel management involves the assignment, activation, release, management, and reporting of dedicated channels such as SDCCH, SACCH, and TCH. The involved procedures are as follows: l Channel activation Through this procedure, the BSC instructs the BTS to activate a dedicated channel for an MS. After this channel is activated, the BSC assigns this channel to the MS through an Immediate Assign, Assign Command, Channel Release (with a channel description), or Handover Command message. l Channel mode modification Through this procedure, the BSC instructs the BTS to change the mode of an activated channel. l Handover detection This procedure is used between the target BTS and the target BSC to detect the access of the MS that is handed over. l l Start of encryption This procedure is used to initiate the encryption procedure specified by GSM TS 04.08. Measurement reporting This procedure consists of the mandatory basic measurement reporting procedure and the optional measurement reporting procedure with pre-processing. Through these two procedures, the BTS reports to the BSC all the parameters related to handover decision. l SACCH deactivation Through this procedure, the BSC deactivates the related SACCH of a TRX according to the requirements of the channel release procedure specified by GSM TS 04.08. l Radio channel release Through this procedure, the BSC instructs the BTS to release a radio channel that is not in use. l MS power control Through this procedure, the BSS controls the transmit power of the MS that uses an activated channel. The MS power control decision must be implemented on the BSC and can be implemented on the BTS.
Transmission power control Through this procedure, the BSS controls the transmit power of the activated channel on the TRX. Transmission power control must be implemented on the BSC and can be implemented on the BTS.
Connection failure Through this procedure, the BTS informs the BSC that an activated dedicated channel is disconnected.
SACCH information modification Through this procedure, the BSC instructs the BTS to change the filling information (system information) on an SACCH.
Talker detection During a VGCS call, on receiving the Talker uplink access message from the MS on the idle uplink VGCS channel, the BTS generates a VGCS UPLINK GRANT message on the activated dedicated channel and reports to the BSC the detected MS access delay.
Listener detection When there is no listener in the cell, the dedicated radio downlink channel allocated to the VGCS/VBS needs to be released in time to improve the resource utilization. The BSC periodically broadcasts the uplink free message in the cell. After all the listeners receive this message, a Talker uplink access message is sent to the BTS on the idle uplink VGCS channel. The BTS generates a VGCS UPLINK GRANT message and sends this message to the BSC over the activated dedicated channel. In addition, the BTS sends a listener detection message to the BSC, informing the BSC of the MS access delay.
2.133.3.2 Channel Activation

This procedure is used to activate a channel at the BTS for an MS which later will be commanded to this channel by an IMMEDIATE ASSIGN, ASSIGN COMMAND, NOTIFICATION, CHANNEL RELEASE (with a Channel description), or HANDOVER COMMAND message. In the handover case, the procedure is used between the target BSC and the target BTS to activate a channel for a subsequent handover from the old BTS.
Signaling Procedure
The BSC determines what channel will be used and starts up that channel at the BTS by sending a CHANNEL ACTIVATION message to the relevant TRX. This message contains the reason for the activation (immediate assignment, assignment, asynchronous/synchronous handover), the identification of the channel to be used (channel no), and a complete description of the channel (full/half rate, speech/data, coding/rate adaptation, hopping sequence, encryption key etc.). If the Encryption Information field is present, the activation is done with ciphering active. If the Encryption information element is not present, activation is done without ciphering. After activating the channel as requested, the TRX responds with the CHANNEL ACTIVATION ACKNOWLEDGE message. This message contains the current frame number at the BTS. The frame number is used by the BSC to determine the Starting Time parameter to be included in the following assignment message to the MS. (A suitable number has to be added to current frame number to take all possible signaling delays into account).
If the TRX for some reason cannot activate the resource as requested by the CHANNEL ACTIVATION message, the TRX shall return a CHANNEL ACTIVATION NEGATIVE ACKNOWLEDGE message with the most appropriate cause value. Possible cause values may be: l l l l O&M intervention (for example, channel blocked); resource not available (for example, speech coder, encryption device); equipment failure; channel already activated.
In the handover case, the procedure is initiated by the target BSC when this BSC receives the HANDOVER REQUEST message from the MSC (or autonomously by the BSC for BSC internal handover). The BSC sends a CHANNEL ACTIVATION message to the relevant TRX. The message contains the Handover Reference value which can be used by the BTS to check the Handover Access from the MS. After activation of the channel, the TRX responds with a CHANNEL ACTIVATION ACKNOWLEDGE message containing the current frame number at the BTS. The BSC can then determine the Starting Time parameter to be included in the HANDOVER REQUEST ACKNOWLEDGE message to the MSC (and the HANDOVER COMMAND message to the MS).
Issue 08 (2011-09-30)
1524
Activation for Intra-Cell Channel Change

This activation precedes the Immediate Assignment and Assignment procedures. The Timing Advance element must be included in the CHANNEL ACTIVATION message. The BTS activates the channel and starts transmission and reception on the main channel in the indicated mode. Ciphering is started if so indicated in the encryption information. The reception and transmission on SACCH is also started immediately. If the BSC and/or MS power elements and/or the Physical Context element are present, the reception and transmission processes and the L1-header of SACCH are initialized accordingly.
Activation for Asynchronous Handover

BTS starts transmission immediately on the main channel in the indicated mode and with encryption if so indicated. If the MS Power element is present the BTS may start transmission also on the SACCH. When receiving a correct access burst with the correct handover reference, BTS starts the normal reception process on the main channel in the indicated mode and starts receiving (and sending if not started earlier) on SACCH. Deciphering is started if so indicated. The handover detection procedure towards BSC is also started.
Activation for Synchronous Handover

The BTS starts transmission immediately on the main channel in the indicated mode and with encryption if so indicated. If the MS Power and Timing Advance element are present, the BTS needs to start transmission also on SACCH with the timing advance and MS power control parameters indicated. If only the MS power element is present, the BTS may start transmission also on the SACCH. When receiving a correct access burst with the correct handover reference, the BTS starts the normal reception process on the main channel in the indicated mode, with deciphering applied if so indicated, and starts receiving (and sending if not started earlier) on SACCH. The handover detection procedure towards the BSC is also started. Alternatively, the reception of a correctly decoded frame from the MS on the main channel, in the indicated mode and deciphering applied if so indicated, allows the start of sending on SACCH (if not already started) and starts the handover detection procedure towards the BSC.
NOTE
The activation for synchronous handover can be used for pseudo synchronized handover.
Issue 08 (2011-09-30)
1525
2.133.3.3 Channel Mode Modify

This procedure is used by the BSC to request a change of the channel mode and/or a change between uni-directional and bi-directional channel types of an active channel. The BSC initiates the procedure by sending a MODE MODIFY message to the BTS. The message contains the new mode to be used. After having changed to the new mode, the BTS responds with a MODE MODIFY ACKNOWLEDGE message to the BSC.
If the TRX for some reason cannot modify the channel as requested in the MODE MODIFY message, the TRX shall return a MODE MODIFY NEGATIVE ACKNOWLEDGE message with the most appropriate cause value.
2.133.3.4 Handover Detection

This procedure is used between the target BTS and BSC when a handed over MS accesses the new BTS. The procedure is initiated by the BTS upon detection of an MS on a channel activated for handover. In case of an asynchronous handover, the BTS builds the PHYSICAL INFORMATION message as specified in 3GPP TS 44.018, sends the message to the MS in unacknowledged mode on the main signaling link, and starts timer T3105. A HANDOVER DETECTION message is sent to the BSC. This message contains the measured delay of the access burst. If the timer expires before the reception of a correctly decoded frame from the MS, the BTS repeats the PHYSICAL INFORMATION message to the MS as specified in 3GPP TS 44.018. If the PHYSICAL INFORMATION message has been repeated Ny1 times without a correctly decoded frame being received from the MS, the BTS needs to send a CONNECTION FAILURE message to the BSC with the cause value "handover access failure". In case of a synchronous handover, the BTS only sends a HANDOVER DETECTION message to the BSC (no PHYSICAL INFORMATION message sent to the MS). If the handover detection is based on the detection of an handover access burst with the correct handover reference, the measured delay of the access burst is included in the HANDOVER DETECTION message.
Issue 08 (2011-09-30)
1526
2.133.3.5 Start of Encryption

This procedure is used to start encryption according to the procedure defined in 3GPP TS 44.018. The procedure is initiated by the BSC upon reception of the CIPHER MODE COMMAND message from the MSC (see 3GPP TS 48.008). The BSC sends the ENCRYPTION COMMAND message to the relevant TRX and channel. The message contains all information required to select and load the user data and encryption device with the appropriate key and also the complete Ciphering Mode Command message to be sent to the MS. After receipt of this message, the TRX sends the CIPHERING MODE COMMAND message to the MS in unciphered form and starts deciphering. The start of deciphering and the sending of the CIPHERING MODE COMMAND message to the MS must be done simultaneously. When receiving the CIPHering MODe CoMmanD, the MS starts both the decryption and encryption and sends the CIPHERING MODE COMPLETE message. The TRX starts the encryption upon reception of any correct layer 2 frame which is received after starting of the decryption.
If the TRX for some reason can not perform the encryption as requested in the ENCRYPTION COMMAND, the TRX shall return an ERROR REPORT message, for example, with the cause "Encryption algorithm not implemented".
2.133.3.6 Measurement Reporting

These procedures are used to report to the BSC all parameters and measurement results required by the BSC for handover requirement decision. The MS measures downlink received signal level and quality from the serving cell and received signal level from surrounding cells as defined in 3GPP TS 45.005 and 3GPP TS 45.008. The measurement results are reported in MEASUREMENT REPORT messages sent in every SACCH block (every 480 ms). The TRX measures the received signal level and the quality on the uplink of the current channel. The averaging period is one SACCH block period (same as the basic period for the MS). These measurements made by the MS and the TRX form the basic raw data for the handover algorithms
in the BSC/MSC. The procedure to be used for this basic measurement reporting is defined in sub-clause Basic Measurement Reporting. In addition, the BTS and the BSC may optionally support some pre-processing in the BTS of these basic measurements. The additional and optional procedures required to support this preprocessing are defined in sub-clause 3.6.2 Measurement pre-processing.
Basic Measurement Reporting

This procedure is used by the BTS to report the results of the basic radio measurements made by the MS and TRX according to 3GPP TS 45.008 and 3GPP TS 45.005. The TRX reports all these measurements in MEASUREMENT RESULT messages to the BSC. If an uplink SACCH block does not contain a MEASurement REPort from the MS (for example, when it sends a short message), only the uplink measurement results are included with an indication that the MS measurements are missing.
Measurement pre-processing
These procedures are included to support some pre-processing in the BTS of radio measurement data. When used, they may replace the basic procedure defined in sub-clause 3.6.1 Basic Measurement Reporting. l Pre-processing configuration This procedure is used by the BSC to modify the pre-processing parameters according to the reported communication conditions (e.g. degradation of the communication). This procedure is enabled after setting the parameter MR.Preprocessingto BTS_Preprocessing. In order to change the parameters, the BSC sends a PREPROCESS CONFIGURE message to the BTS.
Issue 08 (2011-09-30)
1528
Pre-processed measurement reporting This procedure is used by the BTS to report the results of measurement pre-processing. To report the results, the BTS sends a PREPROCESSED MEASUREMENT RESULT message to the BSC. The interval of reporting the results is specified by the parameter Sent Freq.of preprocessed MR.
2.133.3.7 SACCH Deactivation

This procedure is used by the BSC to deactivate the SACCH at the BTS according to the Channel Release procedure defined in 3GPP TS 44.018. When sending the CHANNEL RELEASE message to the MS, the BSC also sends the DEACTIVATE SACCH message to the BTS to deactivate the SACCH.
2.133.3.8 Radio Channel Release

This procedure is used by the BSC to release a radio channel which is no longer needed. When an activated radio channel is no longer needed, the BSC sends an RF CHANNEL RELEASE message to the relevant TRX and channel. After having released the addressed resources, the BTS sends an RF CHANnel RELease ACKnowledge to the BSC.
2.133.3.9 MS Power Control

For details, see the Power Control Feature Parameter Description.
2.133.3.10 Transmission Power Control

For details, see the Power Control Feature Parameter Description.
2.133.3.11 Connection Failure

This procedure is used by the BTS to indicate to the BSC that an active connection has been broken (e.g. due to a radio link failure as defined in 3GPP TS 45.008). When the BTS detects that a connection has been broken, the BTS sends a CONNECTION FAILURE INDICATION message to the BSC with the most proper cause value. Some possible cause values are: l l radio link failure (as defined in 3GPP TS 45.008); hardware failure (for example, transcoder failure);
After receiving a CONNECTION FAILURE INDICATION message from the BTS, the BSC sends a CLEAR REQUEST message to the MSC, requesting the MSC to release the related radio resources.
2.133.3.12 SACCH Information Modify

This procedure is used by the BSC to modify the SACCH filling information (System Information) sent on an individual SACCH channel. For this purpose, the BSC sends a SACCH INFO MODIFY message to the BTS. The SACCH filling information as given in the SACCH INFO MODIFY message is used on the indicated channel until the channel is released or the information is changed by another SACCH INFO MODIFY message.
2.133.3.13 Talker Detection

For details, see the VGCS/VBS Feature Parameter Description.
2.133.3.14 Listener Detection

For details, see the VGCS/VBS Feature Parameter Description.

This chapter provides engineering guidelines regarding the configuration of Radio Dedicated Channel Management. The following radio channel management procedures are mandatory for the establishment, maintenance, and release of radio links and are not controlled by parameters: channel activation, channel mode modify, handover detection, start of encryption, deactivate SACCH, radio channel release, connection failure, and SACCH information modify. For details about the MS power control and transmission power control procedures, see the Power Control Feature Parameter Description. For details about the talker detection and listener detection procedures, see the VGCS/VBS Feature Parameter Description.
2.133.4.1 Measurement reporting

If the BTS preprocesses the measurement reports before sending them to the BSC, then the number of measurement report messages from the BTS to the BSC is reduced. In this way, the RSL bandwidth required over the Abis interface is reduced. If the RSL multiplexing ratio over the Abis interface is high, for example, 1:4, that is, four RSLs are multiplexed on one 64 kbit/s link, it is recommended that the measurement reports be preprocessed by the BTS. When measurement reports are preprocessed by the BTS, the MS power control and transmission power control procedures are processed at the BTS because the power control algorithms used by the BTS and BSC are the same. Thus, the load on the BSC is reduced. When the load on the BSC is heavy, preprocessing measurement reports by the BTS is recommended. MSs cannot be handed over in time because it takes some time for the BTS to preprocess the measurement reports.
2.133.4.2 Channel Mode Modify

The channel mode modify procedure is a basic procedure for implementing radio link management and is not controlled by parameters.
2.133.5 Parameters
This chapter describes the parameters related to radio dedicated channel management. For the description of each parameter, see Table 2-302. For the default value, value ranges, and MML commands of each parameter, see Table 2-303. Table 2-302 Parameter description (1) Parameter MR.Preprocessing Sent Freq.of preprocessed MR
Issue 08 (2011-09-30)
Description Whether to enable the BTS to preprocess measurement reports. This parameter determines where to conduct power control. Frequency at which the BTSs submit pre-processed measurement reports to the BSC.
1531
Table 2-303 Parameter description (2) Default Value BTS_Pr eprocess ing GUI Value Range BSC_Preprocessing(BSC preprocessing), BTS_Preprocessing(BTS preprocessing) NOreport(Do not report), Twice_ps (Twice every second), Once_ps (Once every second), Once_2s (Once every two second), Once_4s (Once every four second) Actual Value Range BSC_Prepr ocessing, BTS_Prepr ocessing Un it No ne MML Command SET GCELLHO CTRL (Optional) Impa ct Cell
Parameter MR.Preproces sing
Sent Freq.of preprocessed MR
Once_ps
No ne
SET GCELLHO CTRL (Optional)
Cell
2.133.6 Counters
2.133.7 Glossary

l l l l l l 3GPP TS 45.058 3GPP TS 44.018 BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Reference
2.134 Security Management

2.134.1.1 Scope
This document describes the security management feature (MRFD-210305 Security Management) involved in the BSC6900 operation and maintenance (O&M).


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Security Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.134.2 Overview
The security management feature of the BSC6900 involves: l l l l
Issue 08 (2011-09-30)
User security Security of OMU operating system Data redundancy backup User authentication failure timeout alarm

2.134.3.1 Overview
User security involves measures such as user management, rights management, and log management taken for ensuring the legal user login, secure operations, and log recording.
User Management
The BSC6900 supports multi-user operations. To log in to the BSC6900, a user must enter the user name and password, through which the BSC6900 identifies the user. The users of the BSC6900 consist of local users and domain users. l Local users Refer to the accounts (including the default local account admin) only managed by the BSC6900 LMT. The users of this type can log in to the BSC6900 LMT during the BSC6900 installation and during the disconnection from the M2000. l l Domain users Refer to the accounts managed by the M2000. The accounts of this type are created, changed, authenticated, and authorized by the M2000. After domain users are authorized, they can manage the BSC6900 by logging in to the BSC6900 LMT or by logging in to the M2000 server through the M2000 client.
A user logs in to the BSC6900 through the LMT or Telnet and sends the login information. Then, the BSC6900 determines whether the user adopts the domain account according to the domain information contained in the login information. If the domain account is adopted, the BSC6900 forwards the user's request for login to the M2000. After receiving the authentication request from the BSC6900, the M2000 determines the authentication through an internal mechanism and sends the authentication results back to the BSC6900. If the authentication is successful, the user rights information list is contained in the authentication results. describes the mapping between user levels and command groups Table 2-304 Mapping between user levels and command groups Level Guest Rights Browsing the data Command Group G_0 Function Used to query the system information such as users, command groups, logs, NTP, EMS, and time zones Used to query data configuration; consisting of the MML commands of the LST type Used to query the alarm information
1534
G_2
G_4
Issue 08 (2011-09-30)
Level
Rights
Command Group G_6
Function Used to query the performance data such as a result file or a task file Used to query the equipment information such as equipment status; consisting of the MML commands of the DSP type Used to query the information about base stations such as the attributes and boards of base stations Used to perform the performance file management, for example, to activate a performance task file or upload a performance result file Used to perform the equipment management, for example, to reset, block, unblock, or switch over a board. Used to trace and monitor the signal flow on the control plane and user plane, for example, to query a tracing task or create/delete/start a tracing task Used to modify device panels Used to perform the BSC6000 software management such as patch management
G_8
G_13
User
Browsing the data and performing the system O&M
G_7
G_9
G_10
G_11 G_12
Issue 08 (2011-09-30)
1535
Level
Rights
Command Group G_14
Function Used to perform base station management such as base station software management or base station resetting Used to configure data, for example, to configure the data for a new cell Used to perform alarm management, for example, to clear an alarm or set the alarm severity Used to perform the system information management, for example, to manage a user, set the time zone, set the daylight saving time (DST), or perform batch configuration
Operator
Browsing the data, performing the system O&M, and performing the data configuration on the equipment
G_3
G_5
Administrator
Having the highest rights, that is, browsing the data, performing the system O&M, performing the data configuration on the equipment, and performing user management
G_1
Custom
The rights of users at this level are defined by the administrators according to the command groups required by the users.
Log Management
Log management records and saves the operations performed by users and security and running information of the BSC6900. It enables users to audit logs. describes the types of logs that are recorded when the BSC6900 is running. Table 2-305 Types of log information Type Running log Operation log Security log Description Records the information about the operating status of the system. The information is used to analyze and locate faults. Records the information about operation and maintenance performed by users, including operations through binary commands. Records the information about the operations affecting the system security such as the information about the change of user password.
Issue 08 (2011-09-30)
1536
The log management provides the following functions: l l Saving log files Users can save the log information to the OMU by setting the log recording parameters. Uploading log files Users can upload log files on the OMU to a specified FTP server by setting the uploading parameters. l Querying log files Users can view the specified log information saved on the OMU by setting the query conditions. l Saving the logs stored in the buffer to the log file by force Users can obtain the latest log information by saving the logs stored in the buffer to the log file. l Saving and browsing operation logs and security logs on the M2000 Users can browse the operation logs and security logs of the BSC6000 on the M2000 interface.
2.134.3.2 OMU Operating System Security

The operation and maintenance unit (OMU) of the BSC6900 can be used in the following operating systems: Windows, Suse Linux, and Dopra Linux. The OMU, serving as the interface between the BSC6000 and other NEs, is vulnerable to security risks. Thus, measures such as anti-virus software installation, system enhancement, and system patch installation are taken to improve security of the operating system. The operating system varies with the scenarios: l When the BSC6810 is upgraded to the BSC6900, you can continue to use the Windows operating system in the BSC6900, or switch the Windows operating system to the Dopra Linux operating system by using an operating system switchover tool. When the BSC6000 is upgraded to the BSC6900, you can continue to use the Suse Linux operating system in the BSC6900, or switch the Suse Linux operating system to the Dopra Linux operating system by using an operating system switchover tool. When a new BSC6900 is deployed, the OMU uses the Dopra Linux operating system by default.
?.1. Anti-Virus Software

The Windows and Suse Linux operating systems are faced with increasing network virus attacks and malicious network attacks. Thus, the security of the operating systems is threatened. The BSC6900 provides the anti-virus solution to the entire mobile operation and maintenance (OM) network. The solution involves installing the anti-virus software on the OMU in the Suse Linux and Windows operating systems and providing anti-virus policies. The Dopra Linux operating system is customized for Huawei and thus does not involve the anti-virus software. l Anti-virus software for the Suse Linux operating system For the installation of the anti-virus software, refer to the Anti-Virus Software Installation Guide provided by Huawei. Currently, the TrendMicro Control Manager (TMCM) + TrendMicro ServerProtect for Linux 2.5(TMSP) can be installed.
TMCM TMCM, a Web-based management control console, provides a uniform platform to monitor the anti-virus products and services on the entire network. The TMCM manages the gateway, mail server, file server, and desktop computers, Trend Micro products and services, AND third-party anti-virus products. The TMCM can be connected to the Internet to download the latest virus feature codes and provides the hosts using the Suse Linux operating system with upgrade services under the supervision of the TMCM.
ServerProtect for Linux TMSP provides a real-time and comprehensive protection for enterprise servers from being infected with viruses, spyware, and other threats internally or externally. TMSP provides centralized scanning of viruses or malicious attacks, updating of feature codes, and reporting and configuration of events. Huawei BSC6900 supports the installation of the TMSP software, which provides the BSC6900 with the virus monitoring and protection functions.
Anti-virus software for the Windows operating system For the Windows operating system, the OfficeScan software is recommended. The OfficeScan software, provided by TrendMicro, is the mainstream software that provides comprehensive security protection for the corporate desktop. Having passed the strict compatibility tests of Huawei, Officescan7.0 is compatible with the OMU. If you want to use other anti-virus software such as Symantec and McAfee, you need to purchase them separately. The software, however, must pass the compatibility test of Huawei.
Issue 08 (2011-09-30)
1538
A virus code upgrade server is deployed independently in the Demilitary Zone (DMZ) of the OM network. The server obtains the latest virus code or upgrade package from the Internet. The anti-virus server (such as Officescan7.0 Server) on the OM network is upgraded through a direct connection to the virus code upgrade server in the DMZ instead of a direct connection to the Internet. After the anti-virus server is upgraded, the virus code and upgrade package of the equipment on the entire network is upgraded automatically, thus implementing protection upgrade and virus monitoring management.
?.2. Operating System Enhancement

Generally, the operating system has security holes and potential security risks. These security holes and potential risks are prone to be exploited by the local or remote attackers to attack the operating system maliciously. As a result, the operating system and the relevant software are damaged, thus affecting the normal operation of the operating system. To prevent these risks, Huawei provides the operating system enhancement scheme for the Windows, Suse Linux, and Dopra Linux operating systems. In the scheme, the network access, network security, system services, and system installation are customized. In this manner, the anti-virus and anti-attack capabilities of the operating system are improved and the probability that the system runs normally is enhanced, thus improving the service quality of the entire network. l Windows and Suse enhancement Windows and Suse Linux are enhanced by using the SetWin and SetSuse respectively. By using the customized security policy, the operating system is protected from being attacked. Thus, the security of the operating system is enhanced. The application of the security policy includes the following parts: Executing the policy: You can execute a single policy or multiple policies simultaneously and then write the execution results into the log file. Rolling back the policy:
After the policy is executed, if you need to return to the configuration status before the policy is executed or re-customize the policy, you can resume the executed policy. Generating backup time: You can store the current status of the policy into the log file and create the backup time for the policy to be rolled back. Saving the configuration: You can store the current policy configuration status. Exporting the configuration: You can export the current policy configuration to the log file. Importing the configuration: You can import the saved log file that contains the policy configuration information in the system so that the system has the same configuration. Importing the original configuration file: You can import the configuration of the SetWin or SetSuse of an earlier version. Reloading the configuration file: The operating system tool carries one configuration file. After you reload the configuration file, the operating system will reload the configuration file. l Dopra Linux enhancement The Dopra Linux operating system is customized for Huawei. The operating system integrates multiple security polices including basic security, system service security, file/ directory security, core security, system access authentication authorization, account/ password security, security audit, and extra security functions, which significantly improves the security of the operating system.
Operating System Patch

Operating system patches are classified into basic patches and incremental patches. The basic patches of the previous year are issued annually, and the incremental patches of the current year are issued on schedule. Before the BSC6900 is delivered, the basic patches of the year are already installed on the OMU. The operating devices on the existing network install the patches according to the patch issuance notice of Huawei. The BSC6900 supports local patch installation and remote patch installation. l Local patch installation The LMT is connected to the OMU. You can log in to the OMU operating system to install patches. The patch can be installed for one OMU at a time. l Remote patch installation The patch for the OMU operating system is installed by using the upgrade tool through the local area network. In this installation mode, you can install patches on multiple OMUs, thus improving the serviceability.
2.134.3.3 Data Redundancy Backup

When the OMUa of the BSC6900 is damaged and must be replaced with a new OMUa, you need to back up the data on the damaged OMUa and restore the backup data to the new OMUa. In addition, you need to periodically back up the OMU data during the routine maintenance of the equipment.
In the case of database crash or upgrade failure, you can use the omu_backup_linker tool provided by the OMU and the backup data to restore the data. With the function of periodic or manual backup of the configuration data of the BSC6900 on the M2000, you can manually download the configuration data from the M2000 to the BSC6900 and restore the configuration data when the configuration data is abnormal or the system is down and needs to be recovered.
Backup/Restoration of the BSC6900 Data

You can use the omu_backup_linker tool to back up or restore the OMU configuration data, alarm data, and performance data. You can use the omu_backup_linker tool to restore the data of only the active OMU in dual-OMU mode. Otherwise, the OMU data may be lost. l Start the omu_backup_linker tool Start the omu_backup_linker tool on the OMU. Log in to the active OMU in dual-OMU mode, and then start the omu_backup_linker tool. l Back up the system data Back up the BSC6900 configuration data, performance data, and alarm data manually through MML commands or the backup/restoration tool. l Restore the system data Restore the system data from the data backup file by using the omu_backup_linker tool. The system data consists of configuration data, performance data, and alarm data. The restoration of the BSC6900 system data may interrupt the BSC6900 O&M After the system data is restored, the data on the OMU may be inconsistent with that on the boards. This may greatly affect the ongoing services. Thus, you are advised to restore the data around 00:00 a.m. when the traffic is low.
Backup/Restoration of Configuration Data on the M2000

l Backing up configuration data The process of backing up the data is as follows: The M2000 sends the configuration data backup command to the BSC6000. The BSC6900 generates the latest configuration data file and uploads the file to the M2000 server. Then, the M2000 saves the configuration data file of the BSC6900. By default, the file can be saved for 30 days. You can also set the days for saving the file. The data can be backed up periodically or manually. You can set the period for backing up the data. l Restoring configuration data The process of restoring the BSC6900 configuration data is as follows: When the BSC6900 configuration data is abnormal or the BSC6900 is down and is then recovered , you can download the configuration data from a specified backup file on the M2000 to the BSC6900 and restore the BSC6900 configuration data.
2.134.3.4 User Authentication Failure Timeout Alarm

This function is used to notify the administrator that a user may attempt to log in to the BSC6900 by using the account and password of another user. If the number of authentication failures reaches the specified number, the system reports an authentication failure timeout alarm. This function consists of the following sub-functions:
Setting the authentication failure parameters The administrator can run the SET PWDPOLICY command to set the authentication failure parameters. Maximum Retry Times When the number of authentication failures reaches the value of this parameter, the system automatically locks the account and reports a security alarm. Auto Unlock Time If an account is locked, the user can continue to log into the BSC6900 when the account is automatically unlocked after the period specified by this parameter. Reset Interval of Account Lock Counter If the duration of authentication failures is longer than the interval specified by this parameter, it is considered that login failures are discontinuous.
Locking and unlocking the user in the case of authentication failures If the number of consecutive authentication failures of a user reaches the number specified by the administrator, the system automatically locks the user and then unlocks the user after the automatic unlocking time is reached. The administrator can also unlock the user in advance by running the ULK USR command.
2.134.4 Parameters
None.
2.134.5 Counters
2.134.6 Glossary

l l l l l BSC GOMU Administration Guide GBSS Reconfiguration Guide M2000 Commissioning Guide M2000 User Guide M2000 Operator Guide
2.135 OML Backup

2.135.1.1 Scope
This document provides an overview of OML backup and describes its technical principles.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the OML Backup feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.135.2 Overview
The OML is the operation and maintenance link between the BSC and the BTS. When the OML is faulty, the BTS cannot work. With this feature, two OMLs can be configured on two independent E1s (one for each). When the active OML is faulty, the BTS uses the standby OML. Thus, the BTS and cells can continue working without being out of service due to transmission fault or port fault. OML backup improves the robustness of the BTS. When the working OML is broken because transmission links are faulty, the BTS is not reset and cells are not out of service. Compared with the ring topology that requires twice the amount of resources, this feature requires only a few timeslots. In addition, configuration of the OMLs on two E1s can ensure stable operation of the BTS with little consumption of transmission resources.

2.135.3.1 OML Backup
When Configure Backup OML is set to YES(Yes), OML backup is started. The BSC configures one OML on port 0 and one OML on port 1, and one OML is set up successfully by default. The BTS attempts to re-establish an OML only when the BTS is reset or the OML that has been successfully set up becomes faulty. If the OML that has been successfully set up becomes faulty, the BTS automatically switches over to the other port and sets up an OML on the port after a period specified by Wait Time before OML Switch. Wait Time before OML Switch specifies how long the BTS waits before it switches over to the other port after the working OML becomes faulty. This prevents frequent switchovers caused by OML fault. If the OML is set up successfully, the BSC triggers an OML switchover to the other port. If the OML fails to be set up, the BTS continues to attempt to set up an OML on the port until the time specified by Try Switching Duration Time expires, and then attempts to set up an OML on the faulty port. Try Switching Duration Time specifies the maximum time in which the BTS attempts to set up an OML after switching over the active and standby OMLs. If the BTS fails to set up the OML within the period specified by Try Switching Duration Time, the BTS switches over the active and standby OMLs again. After the OML switchover, the RSL, TCH, idle timeslot, and monitoring timeslot are not switched over. That is, for port 0 and port 1, if the transmission link or port where the working OML is located is faulty, all the TRX, channels, idle timeslots, and monitoring timeslots configured on this port become unavailable. The TRX, channels, idle timeslots, and monitoring timeslots on the normal port, however, are still available. Thus, the BTS and cells can continue to work without being out of service. This feature is supported by the BTS in TDM and HDLC transmission modes. This feature is not supported by the BTS in IP transmission mode.
2.135.4 Parameters
This chapter describes the parameters related to OML backup. For the description of each parameter, see Table 2-306. For the default value, value ranges, and MML commands of each parameter, see Table 2-307.
Issue 08 (2011-09-30)
1544
Table 2-306 Parameter description (1) Parameter Configure Backup OML Description This parameter specifies whether to configure the backup OML. When YES is configured in the BTS, an OML is configured in timeslot 31 of port 0 and port 1 respectively. The links are established on the two ports in turn after the BTS is reset. Once the OML is established on a port, it is always used unless the BTS is reset or the OML is disconnected. If the established OML is disconnected, the BTS automatically switches the OML over to another port to re-establish the OML. Time for which the BTS waits to swap the OML after the OML is interrupted. With this parameter, the BTS does not swap the OML when the OML is interrupted transiently. Maximum time in which the BTS attempts to set up the OML after swapping the main and backup OMLs. If the BTS fails to set up the OML within this time, the BTS swaps the main and backup OMLs again.
Wait Time before OML Switch
Try Switching Duration Time
Table 2-307 Parameter description (2) Default Value NO GUI Value Range NO(No), YES (Yes) 30~300 Actual Value Range NO, YES Uni t Non e s MML Command SET BTSOMLBACK UP(Optional) SET BTSOMLBACK UP(Optional) SET BTSOMLBACK UP(Optional)
Parameter Configure Backup OML Wait Time before OML Switch Try Switching Duration Time
Impact BTS
90
30~300
BTS
90
30~300
30~300
BTS
2.135.5 Counters
2.135.6 Glossary

2.136 2G/3G Neighboring Cell Automatic Optimization

2.136.1.1 Scope
This document describes the benefits of the 2G/3G Neighboring Cell Automatic Optimization feature and the principle of implementing this feature in Huawei GSM BSS.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the 2G/3G Neighboring Cell Automatic Optimization feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
01(2010-01-20)
2.136.2 Overview
The 2G network must be compatible with the 3G network to support the roaming and handover between GSM and UMTS. Operators need to provide continuous and high-quality services in the boundary of different systems to avoid call drops of moving MSs. In traditional conditions, inter-RAT neighboring cells are configured on the basis of drive tests and analysis, which is time-consuming and labor-consuming, and the test result is incomprehensive owning to the limitations of drive tests. A tool is required to check the interRAT neighboring cell configuration automatically based on the data analysis to improve the efficiency and accuracy. Together with the Nastar network optimization tool, Huawei GSM BSS can analyze the 2G/3G neighboring cell configuration based on numerous measurement reports (MRs) from MSs, show the analysis result on the map, and find out missing or redundant 3G neighboring cells for the GSM serving cell. Configuring appropriate 3G neighboring cells according to the Nastar analyzing result helps to improve the inter-RAT handover success rate and reduce the call drop rate, thus improving the GSM network quality and the user experience. This document introduces the 2G/3G Neighboring Cell Automatic Optimization feature from the following aspects: l l l Network topology Task creation Neighboring cell analyzing algorithm

2.136.3.1 Network Topology
This feature should be supported by the MS, BSC, M2000, and Nastar. To implement this feature, create a corresponding task on the Nastar. Figure 2-409 shows the network topology of this feature.
Issue 08 (2011-09-30)
1547
Figure 2-409 Network topology of 2G/3G neighboring cell automatic optimization
2.136.3.2 Task Creation

The procedure for creating a 2G/3G neighboring cell automatic optimization task is as follows: 1. Create an end-to-end task on the Nastar and set the following basic information: task name, OSS name, NE name, NE type, start time for the measurement, end time for the measurement, Measurement Period, Measurement Step, Frequency List and scrambling code of the 3G neighboring cell to be measured, and NeighborCell Interfere Level Thresh 0 to NeighborCell Interfere Level Thresh 7. The Nastar sends the task to the M2000, the M2000 then sends the task information to the BSC through a MML command. After receiving the command, the BSC performs the measurement and generate a result. The BSC updates the BA2 one time in each measurement period. The BSC adds UMTS cells (frequency + scrambling code) into the BA2 (the number of newly-added cells is the same as the measurement step), and then sends the updated BA2 to MSs through System Information (SI). Then, MSs report the level of 3G neighboring cells through MRs. The BSC collects MRs from MSs, and then sends the data to the M2000. The Nastar obtains the measurement files, configuration data, and counter values from the M2000, and then provides the optimization suggestion after analysis. The 2G/3G neighboring cell analysis results are shown in the map directly. Together with the engineering parameters, the analysis result helps the network optimization engineers figuring out the missing and abundant 2G/3G neighboring cells.
2.
3.
4. 5. 6.
2.136.3.3 Neighboring Cell Analyzing Algorithm

Neighboring cell analyzing algorithm is used for determining missing or abundant cells. The algorithm grades and sorts 3G neighboring cells on the basis of the absolute level, relative level, and number of MRs of the 2G serving cell and 3G neighboring cells. A greater score indicates a higher priority. Then, the algorithm determines the missing or redundant cells according to the priority.
The algorithm for determining the missing cell is as follows: If a cell is not configured as the neighboring cell but the priority of the cell is greater than the advised number of neighboring cells, the cell is considered as the missing neighboring cell.
The algorithm for determining the redundant cell is as follows: If a cell is configured as the neighboring cell but the priority of the cell is smaller than the advised number of neighboring cells, the cell is considered as the redundant neighboring cell.
2.136.4 Parameters
This chapter lists the parameters related to 2G/3G Neighboring Cell Automatic Optimization. For the description of each parameter, see Table 2-308. For the default value, value ranges, and MML commands of each parameter, see Table 2-309. Table 2-308 Parameter description (1) Parameter Frequency List Description List of the frequencies to be measured. This parameter is represented as a character string where the IDs of the TRXs to be measured are separated by &, such as 1&124&956. Neighboring cell interference level threshold 0. Neighboring cell interference level threshold 1. Neighboring cell interference level threshold 2. Neighboring cell interference level threshold 3. Neighboring cell interference level threshold 4. Neighboring cell interference level threshold 5. Neighboring cell interference level threshold 6. Neighboring cell interference level threshold 7. Measurement period for each frequency group. Number of frequencies measured in each group (excluding the frequencies in the original BA table).
NeighborCell Interfere Level Thresh 0 NeighborCell Interfere Level Thresh 1 NeighborCell Interfere Level Thresh 2 NeighborCell Interfere Level Thresh 3 NeighborCell Interfere Level Thresh 4 NeighborCell Interfere Level Thresh 5 NeighborCell Interfere Level Thresh 6 NeighborCell Interfere Level Thresh 7 Measurement Period Measurement Step
Issue 08 (2011-09-30)
1549
Table 2-309 Parameter description (2) Default Value None 0 GUI Value Range None 0~127 Actual Value Range 1~800 characters 0~127 Uni t Non e dB MML Command STR NCS (Mandatory) SET OTHSOFTPA RA(Optional) SET OTHSOFTPA RA(Optional) SET OTHSOFTPA RA(Optional) SET OTHSOFTPA RA(Optional) SET OTHSOFTPA RA(Optional) SET OTHSOFTPA RA(Optional) SET OTHSOFTPA RA(Optional) SET OTHSOFTPA RA(Optional) STR NCS (Mandatory) STR NCS (Mandatory)
Parameter Frequency List NeighborCell Interfere Level Thresh 0 NeighborCell Interfere Level Thresh 1 NeighborCell Interfere Level Thresh 2 NeighborCell Interfere Level Thresh 3 NeighborCell Interfere Level Thresh 4 NeighborCell Interfere Level Thresh 5 NeighborCell Interfere Level Thresh 6 NeighborCell Interfere Level Thresh 7 Measurement Period Measurement Step
Impact BSC BSC
60
0~127
0~127
dB
BSC
64
0~127
0~127
dB
BSC
68
0~127
0~127
dB
BSC
72
0~127
0~127
dB
BSC
74
0~127
0~127
dB
BSC
76
0~127
0~127
dB
BSC
80
0~127
0~127
dB
BSC
None None
1~48 1~32
15~720, step:15 1~32
min Non e
BSC BSC
2.136.5 Counters
2.136.6 Glossary

2.137 Intelligent Shutdown of TRX Due to PSU Failure

2.137.1.1 Scope
This document describes the feature of the intelligent shutdown of TRX due to PSU failure.This feature applies to only the scenario where the BTS uses the AC power input.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Intelligent Shutdown of TRX Due to PSU Failure feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
Issue 08 (2011-09-30)
01(2010-01-12)
01(2010-01-12)
2.137.2 Overview
In the scenario where the BTS uses the AC power input, the power supply unit (PSU) converts the AC power into the DC power to provide power supply for the boards of a BTS. Generally, multiple PSUs are required to provide sufficient electricity for a BTS. The PSUs work in the parallel connection. If one or several PSUs are faulty, the load of the PSUs that work properly increases. As a result, all PSUs may stop working due to overcurrent protection, and thus all the services processed on the BTS are disrupted. To prevent such a problem, the function of the intelligent shutdown of TRX due to PSU failure is introduced to Huawei GSM BSS. With this function, when one or several PSUs are faulty, the BTS shuts down the power amplifiers of the TRXs that consume excessive electricity, based on the power supply capability of the PSUs that work properly. In this manner, the rest of TRXs continue to work normally, thus minimizing the impact of service disruption.

When some PSUs are faulty, the PSUs that work properly cannot provide the BTS with sufficient power. In this case, the BTS shuts down the power amplifiers of some TRXs to reduce the power consumption of a site. Thus, the TRXs whose power amplifiers are still powered on can work normally. When an alarm regarding the PSU fault is reported, the BTS calculates the number of TRXs whose power amplifiers need to be shut down on the basis of the power supply capability of the PSUs that work properly. This ensures that the power consumption of the BTS does not exceed the power supply capability supported by the remaining PSUs after the power amplifiers of some TRXs are shut down. The principle of the intelligent shutdown of TRX due to PSU failure is described as follows: The BTS calculates the power supply capability of the PSUs that work properly according to the PSU type and quantity and calculates the power consumption of the BTS according to the TRX type and quantity. Then, the BTS shuts down the power amplifiers of some TRXs by comparing the difference between the power supply capability and the power consumption. When Tran. Cabinet Configured is set to CONFIG, the power consumption of the transmission cabinet needs to be considered for the calculation of BTS power consumption. After the power amplifiers of some TRXs are shut down, the power consumption of the BTS is expected not to exceed the power supply capability of the PSUs that work properly. When the BTS determines the TRXs whose power amplifiers need to be shut down, the following factors are considered: 1. 2. The TRX whose Is Main BCCH TRX is set to NO is preferentially selected. The TRX whose TRX Board Type is set to a multi-carrier TRX board type is preferentially selected.
NOTE
The multi-carrier TRX boards consist of the MRRU, MRFU, GRRU, and GRFU.
3.
The operation of the TRX processing the GSM services is preferentially ensured by setting Service Priority Policy to GSM_PRIOR.
After determining the TRXs whose power amplifiers need to be shut down, the BTS reports the information to the BSC. On receipt of the information, the BSC does not assign new services to
the TRXs whose power amplifiers are to be shut down. After all the services carried on these TRXs are released normally, the BTS shuts down the power amplifiers of the TRXs. When the faulty PSUs recover, the BTS immediately reports the information to the BSC. Then, the BSC powers on the TRXs whose power amplifiers are shut down
2.137.4 Parameters
This chapter describes the parameters related to intelligent shutdown of TRX due to PSU failure. For the description of each parameter, see Table 2-310. For the default value, value ranges, and MML commands of each parameter, see Table 2-311. Table 2-310 Parameter description (1) Parameter Is Main BCCH TRX Service Priority Policy Tran. Cabinet Configured Description Whether to enable the TRX to carry the main BCCH in the cell. The parameter specifies which type of service TRXs should be preferentially processed when the PSU is faulty. Whether to configure the transmission cabinet. The BTS uses this parameter to calculate the number of TRXs to be shut down. Type of the TRX board bound to the TRX.
TRX Board Type
Table 2-311 Parameter description (2) Paramet er Is Main BCCH TRX Service Priority Policy Default Value NO GUI Value Range NO(No), YES (Yes) GSM_PRIOR (GSM Traffic Prior), UMTS_PRIO R(UMTS Traffic Prior) NOT_CONFI G(NOT CONFIGURE D), CONFIG (CONFIGURE D) Actual Value Range NO, YES MML Command ADD GTRX (Optional) SET BTSPSUFP (Optional) Impac t TRX
Unit None
GSM_PR IOR
GSM_PRI OR, UMTS_PR IOR
None
BTS
Tran. Cabinet Configur ed
NOT_CO NFIG
NOT_CO NFIG, CONFIG
None
SET BTSPSUFP (Optional)
BTS
Issue 08 (2011-09-30)
1553
Paramet er TRX Board Type
Default Value None
GUI Value Range TRX(TRX), TRU(TRU/ DTRU), QTRU (QTRU), DRRU (DRRU), DRFU (DRFU), MRRU (MRRU), MRFU (MRFU), GRFU (GRFU), GRRU (GRRU), BTS3900B (BTS3900B), BTS3900E (BTS3900E)
Actual Value Range TRX, TRU, QTRU, DRRU, DRFU, MRRU, MRFU, GRFU, GRRU, BTS3900B , BTS3900E
Unit None
MML Command ADD TRXBIND2PH YBRD (Mandatory)
Impac t TRX
2.137.5 Counters
2.137.6 Glossary

l l l l l BSC6900 Feature List BSC6900 Basic Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference BSC6900 Performance Counter Reference
2.138 License Control for Urgency

2.138.1.1 Scope
This document describes the License Control for Urgency feature.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the License Control for Urgency feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.138.2 Overview
With this feature, telecom operators can temporarily withdraw the license limitation in the case of a sudden increase in traffic volume due to natural disasters, holidays, or a faulty BSC in the BSC Pool scenario. For each release version of BSC6900, the operation personnel have three chances to enable this feature. The validity period is seven days each time. After the License Control for Urgency feature takes effect, the system enters the grace protection period. In this manner, the resource control items are set to the maximum capacity. The values of function control switches, however, remain unchanged.

Overview
The License Control for Urgency feature involves setting and querying the emergency status of license, generating emergency license alarms, and setting the grace protection period switch.
Enabling the License Control for Urgency Feature

In natural disasters such as earthquake and snow disaster, telecom operators can temporarily withdraw the license limitation so that the BSC6900 can be used effectively to optimum capacity. This feature is license based. Telecom operators need to purchase a license to enable the feature. The validity period of this feature is seven days. After the three chances are used up, the feature becomes unavailable. Users can run the SET LICENSECTRL command to enable this feature.
Disabling the License Control for Urgency Feature

o exit the emergency license control mode, run the SET LICENSECTRL command and set Grace Protection Period Switch to OFF(OFF). Alternatively, wait till the system to automatically exit the emergency license control mode after seven days.
Querying the Information About the Feature

Run the LST LICENSECTRL command to query the information about the feature such as whether the feature is enabled, remaining chances to use the feature, and remaining days to use the feature if the feature is enabled.
Generating Alarms During the Grace Protection Period

After the feature is enabled, the system generates an event alarm every day at specified time, notifying uses of the remaining days to use the feature.
Resetting the Grace Protection Period

After a release version is upgraded, the system is reset and the chances to withdraw the license limitation become three. The upgrade of C version and patches does not change the chances.

In the case of the GSM network, users need to purchase BBOM 81201059 License Control for Urgency Function(per TRX). This feature is available only when the license of the system is properly installed or when the license is restricted.
2.138.5 Parameters
This chapter describes the parameters related to license control for urgency. For the description of each parameter, see Table 2-312. For the default value, value ranges, and MML commands of each parameter, see Table 2-313.
Table 2-312 Parameter description (1) Parameter Grace Protection Period Switch Description Grace Protection Period Switch determines whether to enter the grace protection period.
Table 2-313 Parameter description (2) Paramet er Grace Protectio n Period Switch Default Value None GUI Value Range ON(ON), OFF (OFF) Actual Value Range ON, OFF MML Comman d SET LICENSE CTRL (Mandator y) Impa ct BSC6 900
Unit None
2.138.6 Counters
2.138.7 Glossary

l l l l BSC6900 Feature List BSC6900 Optional Feature Description BSC6900 GSM Parameter Reference BSC6900 GSM MML Command Reference
2.139 Faulty Management

2.139.1.1 Scope
This document describes the basic components and functions of the fault management (MRFD-210304 Faulty Management).


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Faulty Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.139.2 Overview
The fault management feature supports auto monitoring of the network devices. The operator can learn the actual status of the network through the alarm list and log. In addition, the operator can manually enable the board test function, which can help the operator to quickly locate the faulty board. Figure 2-410 shows how fault management processes alarms and events in an integrated manner.
Issue 08 (2011-09-30)
1558
Figure 2-410 Fault management model for the NE's
The fault management feature involves the following NEs: BTS, NodeB, BSC6900, and M2000. The BTS is responsible for collecting the alarms of the devices and some services of the BTS. The BSC6900 then processes the alarms and reports the alarm messages to the M2000. The NodeB is responsible for collecting the alarms of the devices and some services of the NodeB and reporting the alarm messages to the M2000. The BSC6900 is responsible for collecting, processing, generating, and then reporting the alarms of the BSC6900 and some services to the M2000. Figure 2-411 shows the fault management system of the SRAN.
Issue 08 (2011-09-30)
1559
Figure 2-411 Fault management system of the SRAN
The BTS/NodeB in the SRAN consists of the BBU, TRX, electromechanical monitoring device, and antenna system. The faults of the devices are collected on the BBU. Then, the fault/alarm mapping, correlation processing, and fault processing are performed. Figure 2-412 shows the fault management system of the BTS/NodeB in the SRAN. Figure 2-412 Fault management system of the BTS/NodeB in the SRAN
Issue 08 (2011-09-30)
1560
The BSC6900 consists of the OMU, SCU, service processing unit, and electromechanical monitoring device. The faults of the devices are collected on the OMU. Then, the fault/alarm mapping, correlation processing, and fault processing are performed, and the fault is reported to the M2000. Figure 2-413 shows the fault management system of the BSC6900 in the SRAN. Figure 2-413 Fault management system of the BSC6900 in the SRAN

The fault management feature involves the following functions: automatic system test, fault detection, fault processing, and fault monitoring. These functions enable operators to learn about network faults in time and then take proper measures to avoid service interruption. Figure 2-414 shows the process of fault management.
Issue 08 (2011-09-30)
1561
Figure 2-414 Process of fault management
2.139.3.1 Fault Handling

The specific functions of the fault management feature are described as follows: l Fault detection The fault detection unit reports the detected fault to the fault management system. Then, the fault management system processes the fault, maps the fault to the alarm, and reports the alarm to the operation and maintenance center (OMC) or local maintenance terminal (LMT). The fault detection varies with hardware and software. The faults can be detected at all levels, including TRXs, ports, channels, boards, BTSs/NodeBs, cells, links, and signaling. l Fault collection The main control board of the SRAN collects and processes the fault information reported by various fault detection units. The SCU of the BSC6900 collects and processes the fault information reported by various fault detection units. l Fault fluctuation/intermittence filtering Filtering at the fault level and alarm level are performed. Firstly, the level-1 filtering of the fault fluctuation/intermittence is performed by the fault detection unit of the board on the basis of the service reliability. Then, the OMU of the BSC6900 or the main control unit of the BTS performs the level-2 filtering of the alarms displayed to the users. The BSC suppresses the faulty intermittence that lasts for a short time by using a delay threshold. The BSC performs intermittence filtering on only the alarms that exceeds the threshold. Then, the BSC performs follow-up filtering on the alarms.
Fault log Fault logs are classified into local fault logs (supported by the BTS/NodeB in the SRAN) and central fault logs. The local fault logs are used for fault analysis after the faulty boards are returned. The logs are recorded in the local nonvolatile storage space. The central fault logs record the fault information of the entire system. Therefore, Huawei engineers can use the fault information recorded in the central fault logs to globally analyze the fault. The central fault logs are also recorded in the local nonvolatile storage space.
l l
Fault processing Fault processing includes fault status management, fault isolation, and fault self-recovery. Fault/alarm mapping The fault/alarm mapping is another core processing of the fault management system. The fault/alarm mapping aims at separating the device-oriented fault from the user-oriented alarm. Therefore, only the comprehensible alarm information is displayed to the user. The fault information is used by Huawei engineers to locate the internal component and code, whereas the alarm information, which is the analysis result of the fault, is used by the user to rectify the fault. In this manner, the user does not need to pay attention to the details about the fault and only identifies the processable unit. During the fault/alarm mapping, the internal fault information is mapped to comprehensible alarms. Faults and alarms can be in one-to-one or many-to-one mapping relation.
2.139.3.2 Alarm Severity

Alarms have different severities. They are classified into: l Critical Critical alarms affect ongoing services. They must be cleared immediately whenever they are reported. l Major Major alarms affect ongoing services. They must be cleared immediately during working hours. l Minor Minor alarms do not affect ongoing services. They must be cleared when required to prevent severer faults. l Warning Warning alarms may affect ongoing services. They must be monitored regularly.
2.139.3.3 Alarm Handling

l Alarm box management (supported by the BSC6900) Alarm box management reports critical and major alarms to the alarm box with beeps and lights, which prompts users to handle faults in time. Table 2-314 describes the LEDs on the board panel. Table 2-314 Description of the LEDs on the board panel Nam e RUN Color Green Remar ks LED indicati ng the operatin g status of a board Description Steady on: The board is supplied with power but it is faulty. Steady off: The board is not supplied with power or it is faulty. Blinking at 0.5 Hz (on for 1s and off for 1s): The board is running normally. Blinking at 4 Hz: The board is being loaded. Blinking at 0.25 Hz: The board is being tested. ALM Red LED indicati ng the alarm status LED indicati ng the active/ standby state of a board Steady off: There is no fault. Steady on (or blinking at a high frequency): An alarm is reported, indicating that the board becomes faulty. On: The board is in active state. Off: The board is in standby state. On Steady off Normal State Blinking at 0.5 Hz
ACT
Green
Alarm correlation display After a fault occurs, a parent alarm and child alarms may be reported. Parent alarm A parent alarm contains the root cause of a fault. Child alarm A child alarm contains the information of the fault caused by the root cause specified in the parent alarm. If users expect the alarms to be suppressed, the sequence number of the parent alarm is carried by the child alarms. For example, alarm A (child alarm) is caused by alarm B (parent alarm). The sequence number of alarm B is carried by alarm A. Then, the maintenance personnel can directly clear alarm B. This prevents repeated trouble ticket processing.
Issue 08 (2011-09-30)
1564
Common alarm (supported by only the BTS/NodeB in the SRAN) The SRAN supports both the GSM system and the UMTS system. The common alarms detected by both the GSM system and the UMTS system are displayed in either the GSM system or the UMTS system. This prevents repeated trouble ticket processing.
BTS alarm synchronization The BSC6900 synchronizes the BTS alarms to the BSC by using the alarm synchronization check command and querying the active alarms. Then, based on the alarm synchronization check command, the BSC6900 updates the alarm record and synchronizes the record with that on the M2000.
Alarm severity change Before a fault alarm is cleared, the alarm severity and part of the information in the fault location information can be changed. The alarm with changed information must be reported again.
User-defined alarm The name, severity, and network management type of an alarm can be customized. In addition, user-defined alarms can be filtered smoothly. For details on user-defined alarms, see the engineering alarms described in the GBSS Reconfiguration Guide.
2.139.4 Parameters
None.
2.139.5 Counters
2.139.6 Glossary

None.
2.140 Configuration Management

2.140.1.1 Scope
This document describes the configuration management feature (MRFD-210301 Configuration Management). It covers the functionality of this feature and technologies regarding this feature. This document includes the feature architecture, basic flow, and primary functions.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Configuration Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.140.2 Overview
Huawei provides the uniform configuration management of the MBSC for the BSS system and the RAN system. With configuration management, configuration data can be securely and accurately transmitted to service boards and can then take effect. The configuration management can work in the following modes: l Configuration management at network level: The network management system (NMS) is used for configuration management at network level. The NMS is a management system in which network devices from different vendors can be configured and managed through the northbound interface (NBI) of the Element Management System (EMS) in a centralized manner. With the NMS, differences between the network devices from different vendors are shielded. This reduces the amount of technical staff and improves the efficiency of network planning and adjustment. Centralized configuration management at NE level: In this mode, multiple NEs provided by the same vendor can be configured and managed in a centralized manner.
Single configuration management at NE level: In this mode, a single NE is configured and managed. This process involves data check, consistency check, service validation management, and configuration rollback.

2.140.3.1 Basic Architecture
Configuration management is a feature through which operators can configure and manage their NEs in different level-based modes. In this way, network management is simplified. Figure 2-415 shows the basic architecture of configuration management. Figure 2-415 Basic architecture of configuration management
NMS: short for Network Management System. The NMS may be from another vendor or be developed by the operator. It is used for network configuration and is interconnected with Huawei EMS through the NBI.EMS: short for Element Management System. The EMS is used to operate and maintain NEs. The configuration management module in the EMS acts as a transport path through which the NMS can transmit correct information to the NEs. The EMS provides the following functions: data management in current and planned area, data import and export, data integrity check and automatic recovery, data modification and transmission in batch, inter-RAT neighboring cell management, and site swapping. In addition, the graphic user interface (GUI) design makes the EMS easy for configuration management. TOOL: Tools for data configuration and network optimization. These tools can be developed for custom use based on the programmable interfaces of the EMS or NEs, thus simplifying network management. LMT: short for Local Maintenance Terminal. You can use MML commands directly or on the GUI of the LMT to operate and maintain a single NE. You do not need to install or upgrade the LMT. This improves the O&M efficiency. NE: short for Network Element. An NE provides the service logic for configuration management and validates data configuration.
2.140.3.2 Basic Flow

Configuration management can be used for network initial installation, network deployment, capacity expansion, and network adjustment. Therefore, its basic flow must involve the following procedures: network planning and data preparation, data configuration, configuration data transmission for service validation, and live network data collection or comparison between the planned data and the live network data or KPIs. Figure 2-416 shows the basic flow of configuration management. Figure 2-416 Basic flow of configuration management
Network Planning and Data Preparation

In this procedure, project, hardware, and network configuration data must be exported based on site survey and network planning. Note that the site survey and network planning must fulfill the requirements of network initial installation, network deployment, capacity expansion, and network adjustment.
Data Configuration
Based on network planning, data is configured by means of the EMS or the NE-oriented single configuration management system. Huawei provides multiple functions for configuration
management in the EMS and the NE-oriented single configuration management system to improve the efficiency of data configuration.
Configuration Data Transmission for Service Validation

In this procedure, configuration data is transmitted to NEs by means of the EMS or the NEoriented single configuration management system, to validate the related services. Before the services are validated, data consistency check and validity check are performed in the EMS or the NE-oriented single configuration management system. The services can be validated only when the checks are passed. Otherwise, the incorrect data must be modified.
Live Network Data Collection or Comparison Between the Planned Data and the Live Network Data or KPIs
Huawei provides comprehensive NBI solutions for configuration management. With the NBI, you can collect the configuration data and related KPIs to compare them with the planned data. If network performance does not meet your expectation, you can perform the configuration management flow from network planning and data preparation again.
2.140.3.3 Functional Features

Huawei provides an efficient, secure, and level-based configuration management system to fulfill the requirements of operators in different scenarios.
Level-Based Configuration Management System

l Multiple and comprehensive northbound interface solutions: These solutions are the supplement of the NMS in which network devices from different vendors can be configured and managed in a centralized manner. Configuration management in the centralized EMS and on a single NE: Operators can select either of the configuration management modes for the network deployment. Programmable data sources: Configuration data can be imported from or exported to an .xml or .csv file by means of the EMS. MML commands and configuration data can be imported from or exported to a file in the NE configuration management system. Tools for advanced development can be interconnected with and integrated into the EMS. Flexible configuration modes: Data can be configured on GUIs or through MML commands. It can also be configured by importing related files or data templates. This simplifies the data configuration. Operators can determine to perform the instant or scheduled configuration management with the scheduled task function.
l l
Scenario-Specific Configuration Management System

l Current and planned data areas for configuration management in the NMS: The data for network initialization, network establishment, capacity expansion, and network adjustment can be planned in the planned area. In this way, the live network data and ongoing services are not affected. Configuration script made in ineffective mode: Configuration scripts can be exported. After being modified, these configuration scripts can be imported in batch, and then the new configuration scripts will take effect. Effective and ineffective configuration on the NE: After data configuration, the related services can be validated in real time. Alternatively, the configuration data is validated only
Issue 08 (2011-09-30)
on the OMU but the related services are not validated in real time. The real-time service validation is applicable to the cases such as network establishment, network adjustment, and capacity expansion. The non-real-time service validation is applicable to the cases such as network initial installation and site upgrade.
Secure Configuration Management System

l l l Right authentication for configuration management. Configuration log query and check. Configuration data backup and recovery: Backup files can be used to recover the OMU database when the system becomes faulty. Backup files can be stored on the local terminal or on the network. Data configuration rollback: If the network performance does not reach your expectation or the network becomes faulty after you modify the configuration data, you can roll back the configuration. In this way, the system becomes operational as soon as possible. Both single-step rollback and multiple-step rollback are supported. Pre-assessment of the impact on ongoing services: Before the MML command is executed on the LMT, the system checks whether the ongoing services will be affected. If the ongoing services are affected, a message is displayed to inform the operator of the effect. Complete data check mechanism. The following checks are provided: Data validity check: Configuration data can be validated only after data validity check. If errors occur during the check, the system stops the execution of related operations or commands, and reports the error information. Data consistency check: In this check, the system ensures the data consistency between the active OMU and the standby OMU and the data consistency between the OMU and the service board. This check can be performed at the time set by the system or by user sending the related command. If this check is performed at the time set by the system, an alarm is reported automatically when any inconsistency is detected. If this check is performs by user sending the related command, you can check the result on the LMT.
Flexible and Easy Network Access Methods for Configuration

You can perform the configuration management on the LMT or in the NMS. The configuration management for a single NE can be performed on the LMT through the browser. You do not need to upgrade the LMT client.
2.140.4 Parameters
None.
2.140.5 Counters
2.140.6 Glossary

None.
2.141 DBS Topology Maintenance

2.141.1.1 Scope
The Local Maintenance Terminal (LMT) provides topology maintenance for the Distributed Base Station (DBS) and thus facilitates the maintenance operations (MRFD-210309 DBS Topology Maintenance).


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the DBS Topology Maintenance feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.141.2 Overview
The DBS topology maintenance feature provides convenient Operation and Maintenance (OM) functions for the distributed base station, thereby reducing the OM expenditure of the operators.

The distributed base station supports the automatic scan of the RRU topology. The LMT provides the topology maintenance for the distributed base station. The functions supported by this feature are as follows: l l l The topology of the distributed base station is displayed in a visualized way. Different colors are used to indicate the status of each BBU, RRU, and CRPI link. The BBU or RRU can be selected directly on the display for maintenance.
Figure 2-417 UMTS NodeB topology
Figure 2-418 GSM BTS topology
Issue 08 (2011-09-30)
1572
2.141.4 Parameters
None.
2.141.5 Counters
2.141.6 Glossary

None.
2.142 BTS/NodeB Software Management

2.142.1.1 Scope
BTS/NodeB software management (MRFD-210402 BTS/NodeB Software Management) provides efficient and accurate software installation, software upgrade, and software version management.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BTS/NodeB Software Management feature of a specific product version.
Document Issues
01(2010-01-20)
2.142.2 Overview
With software management, operation and maintenance can be performed remotely on BTSs and NodeBs in batches. This helps save the cost of local maintenance and increase maintenance efficiency. The remote operation and maintenance are mainly performed on the M2000. The remote upgrade of the BTS software consists of the following steps: 1. 2. 3. The BTS software is downloaded from the M2000 to the BSC. The BSC loads the BTS software to the BTS. The BSC activates the software on the BTS.
After the BTS software is downloaded from the M2000 to the BSC, two upgrade modes are applicable: one-click upgrade and automatic upgrade. l l In one-click mode, maintenance personnel load and activate the BTS software on the M2000. In automatic upgrade mode, maintenance personnel need to only set the BTS version information before the upgrade. Then, based on the version information, the BSC controls the upgrade without human intervention.
The remote upgrade of NodeBs in batches consists of the following steps: 1. 2. 3. The NodeB software package is uploaded to the M2000 server. The NodeB software package is downloaded to NodeBs. The NodeB software is activated.
For details about data configuration, see the related initial configuration guide. For details about upgrades, see the related upgrade guide.

The BTS/NodeB software management feature enables the operator to remotely manage the software installation and upgrade of the MBTS. This feature supports enhanced functions such as automatic change of the signaling bandwidth, software download based on the configuration, software download resumption, download and activation of software in batches, and hot patching.
The BTS/NodeB software management feature provides efficient and accurate software installation, software upgrade, and software version management. The operator can perform the following operations through MML commands: l l l l Efficient and correct installation and upgrade of the software Check on compatibility of the software and hardware versions to ensure successful software installation and upgrade Version management, for example, the hardware and software version check Automatic data conversion during the software upgrade
The process for upgrading the software of the MBTS is as follows: 1. 2. 3. The software package is downloaded from the M2000 to the MBTS through the OM (Operation and Maintenance) channel. The software activation command is executed on the M2000 client. The MBTS automatically loads the software to the corresponding board and switches over the active and standby directories on the MBTS.
The enhancement features of the MBTS software management are as follows: l UBR/UBR+(Unspecified Bit Rate Plus) is supported on the OM channel. When the traffic is heavy, the OM channel rate is fixed at 64 kbit/s. When the traffic is light, the OM channel bandwidth is automatically increased to achieve higher software downloading efficiency. Software download based on the configuration can reduce 30% of the software package and shorten the download time. When a board is added, the system downloads only the software of the board, to improve the download efficiency. If the network recovers in 24 hours after the network breakdown, the system supports software download resumption to prevent repeated software download. Each time, the automatic software download and activation can be performed on a maximum of 500 MBTSs in a batch. The default value is 50 MBTSs in one batch. Hot patching without resetting the MBTS is supported to minimize the negative impact on the traffic.
l l l
2.142.4 Parameters
None.
2.142.5 Counters
2.142.6 Glossary

None.
2.143 BTS/NodeB Software USB Download

2.143.1.1 Scope
Users or maintenance personnel can download and activate the MBTS software through USB without using portable computers (MRFD-210310 BTS/NodeB Software USB Download). Thus, the MBTS can be set up easily and quickly.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BTS/NodeB Software USB Download feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.143.2 Overview
With the BTS/NodeB software USB download feature, the software upgrade does not require the transmission on the Abis or Iub interface. Therefore, the upgrade time is shortened, and the
MBTS can be set up quickly with a low cost. In addition, maintenance personnel need not get to sites in person, because they can perform software commissioning remotely.

The 3900 series MBTSs provide USB ports, through which the host software can be downloaded. After the MBTS hardware is installed, the system automatically upgrades the software when the USB disk is inserted. This feature enables the software upgrade to be performed through the USB disk without using a portable computer. With this feature, the software upgrade is independent of Abis/Iub transmission. Therefore, the upgrade time is shortened, and the MBTS can be set up quickly with a low cost. After the software is activated and the system begins to operate, hardware faults can be detected on the basis of the indicators on the BBU panel so that the faults can be rectified in the shortest time. In addition, the maintenance personnel need not get to sites in person, because they can perform software commissioning remotely. l When upgrading the BTS software through the USB disk, pay attention to the following situation: The upgrade is not performed within three minutes after the BTS starts up. That is because the BTS attempts to connect to the BSC within the three minutes, instead of using the predefined configuration file. After the three minutes elapse, the BTS determines that it cannot connect to the BSC and starts the upgrade by using the pre-defined configuration file. l When upgrading the NodeB software through the USB disk, pay attention to the following situations: If the USB disk stores the NodeB software only, the software is upgraded automatically. If the USB disk stores the data configuration file only, the file is automatically downloaded.
2.143.4 Parameters
None.
2.143.5 Counters
2.143.6 Glossary

None.
2.144 BSC/RNC Software Management

2.144.1.1 Scope
This document describes functions provided by the software management feature (MRFD-210401 BSC/RNC Software Management) and focuses on the principles of file loading initiated by boards.


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the BSC/RNC Software Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.144.2 Overview
Huawei MBSC supports the uniform software management of BSS and RAN, thus facilitating the remote management of the MBSC software and improving the efficiency of software upgrade and data downloading. With this feature, users can implement the following operations on the M2000. l
Issue 08 (2011-09-30)
Querying the software version and its status

l l l
Uploading, downloading, and activating the program files, patch files, and license files Using the OMU of the MBSC as the FTP server and transmitting files such as program files and patch files between the FTP server and FTP client Using the MBSC as the transmission medium to transmit files between the M2000 and the MBTS
In addition, users can manage the programs, patches, licenses, data, and logs through the Web LMT.

2.144.3.1 File Loading Initiated by Boards
In the BSC6900 GSM and BSC6900 GU systems, the TCS is available in TC remote configuration mode. In the BSC6900 UMTS system, however, only the EPS/MPS is available. In addition, in the GSM and GU systems, the loading processes vary with the subrack combination mode and the TCS position.
?.1. TCS Locally Configured in BM/TC Separated Mode in BSC6900 GSM and BSC6900 GU Systems
Figure 2-419 shows the loading process when the TCS is locally configured in BM/TC separated mode in the BSC6900 GSM and BSC6900 GU systems. Figure 2-419 Loading process
Issue 08 (2011-09-30)
1579
OMUa in effective mode 1. 2. After being started, a board broadcasts the BOOTP request message. After receiving the BOOTP request message from the board, the OMUa writes the load key, IP address, and version information into the BOOTP acknowledgement message and then sends the message to the board. After receiving the BOOTP acknowledgement message, the board loads the program files and data files according to the load key. The loading is complete. After being started, a board broadcasts the BOOTP request message. If no response is returned after 30s, the SCUa in the MPS loads the program files and data files from the Flash. After loading the program files and data files, the SCUa in the MPS processes the BOOTP request messages from other boards in the MPS and from the SCUa in the EPS/TCS. After loading the program files and data files, the SCUa in the EPS/MPS processes the BOOTP request messages from other boards in the EPS/MPS. After receiving the acknowledgement messages, all other boards in the MPS/EPS/ TCS load the program files and data files from the Flash. The loading is complete.
3. 4. l 1. 2. 3.
OMUa not started or in ineffective mode
4. 5. 6.
?.2. TCS Remotely Configured in BM/TC Separated Mode in BSC6900 GSM and BSC6900 GU Systems
When the TCS is remotely configured in BM/TC separated mode in the BSC6900 GSM and BSC6900 GU systems, the Ater interface serves as the loading channel between the BM subrack and the TC subrack. Figure 2-420 shows the loading process.
Issue 08 (2011-09-30)
1580
Figure 2-420 Loading process
OMUa in effective mode 1. 2. After being started, a board broadcasts the BOOTP request message. After receiving the BOOTP request message from the board, the OMUa writes the load key, IP address, and version information into the BOOTP acknowledgement message and then sends the message to the board. After receiving the BOOTP acknowledgement message, the board in the MPS/EPS loads the program files and data files according to the load key. After completing the loading, the Ater interface board in the MPS serves as the agent of the Ater interface board in the TCS and forwards the BOOTP request and acknowledgement messages from the Ater interface board in the TCS. After completing the loading, the Ater interface board in the TCS serves as the agent of other boards in the TCS and forwards the BOOTP request and acknowledgement messages from other boards. After receiving the BOOTP acknowledgement messages, other boards in the TCS load the program files and data files according to the load key. The loading is complete.
3. 4.
5.
6. 7. l
OMUa not started or in ineffective mode 1. After being started, a board broadcasts the BOOTP request message.
Issue 08 (2011-09-30)
2. 3.
If no response is returned after 30s, the SCUa in the MPS loads the program files and data files from the Flash. After loading the program files and data files, the SCUa in the MPS processes the BOOTP request messages from other boards in the MPS and from the SCUa in the EPS. After loading the program files and data files, the SCUa in the EPS processes the BOOTP request messages from other boards in the EPS. After receiving the BOOTP acknowledgement messages, other boards in the EPS load the program files and data files according to the load key. After completing the loading, the Ater interface board in the MPS serves as the agent of the Ater interface board in the TCS and forwards the BOOTP request and acknowledgement messages from the Ater interface board in the TCS. After completing the loading, the Ater interface board in the TCS serves as the agent of other boards in the TCS and forwards the BOOTP request and acknowledgement messages from other boards. After receiving the acknowledgement messages, all other boards in the TCS load the program files and data files from the Flash. The loading is complete.
4. 5. 6.
7.
8. 9.
?.3. BM/TC Combined Mode or A over IP Mode in BSC6900 GSM and BSC6900 GU Systems
Figure 2-421 shows the loading process in BM/TC combined mode or A over IP mode in the BSC6900 GSM and BSC6900 GU systems. Figure 2-421 Loading process
OMUa in effective mode 1. 2. After being started, a board broadcasts the BOOTP request message. After receiving the BOOTP request message from the board, the OMUa writes the load key, IP address, and version information into the BOOTP acknowledgement message and then sends the message to the board.
Issue 08 (2011-09-30)
3. 4. l 1. 2. 3.
After receiving the BOOTP acknowledgement message, the board loads the program files and data files according to the load key. The loading is complete. After being started, a board broadcasts the BOOTP request message. If no response is returned after 30s, the SCUa in the MPS loads the program files from the Flash. After loading the program files and data files, the SCUa in the MPS processes the BOOTP request messages from other boards in the MPS and from the SCUa in the EPS. After loading the program files and data files, the SCUa in the EPS processes the BOOTP request messages from other boards in the EPS. After receiving the acknowledgement messages, all other boards in the MPS/EPS load the program files and data files from the Flash. The loading is complete.
OMUa not started or in ineffective mode
4. 5. 6.
?.4. BSC6900 UMTS System

Figure 2-422 shows the loading process in the BSC6900 UMTS system. Figure 2-422 Loading process
If the OMUa is in online mode, the loading process is as follows: 1. 2. After being started, a board broadcasts the BOOTP request message. After receiving the BOOTP request message from the SCUa, the OMUa writes the load key, IP address, and version information into the BOOTP acknowledgement message and sends the message to the SCUa. After receiving the BOOTP acknowledgement message, the SCUa loads the program files and data files according to the load key. After completing the loading, the SCUa in the MPS processes the BOOTP request messages from other boards in the MPS and from the SCUa in the EPS.
3. 4.
Issue 08 (2011-09-30)
5. 6. 7. l 1. 2. 3. 4. 5. 6.
After loading the program files and data files, the SCUa in the EPS processes the BOOTP request messages from other boards in the EPS. After receiving the BOOTP acknowledgement message, other boards load the program files and data files according to the load key. The loading is complete. After being started, a board broadcasts the BOOTP request message. If no response is returned after 30s, the SCUa in the MPS loads the program files and data files from the Flash. After completing the loading, the SCUa in the MPS processes the BOOTP request messages from other boards in the MPS and from the SCUa in the EPS. After loading the program files and data files, the SCUa in the EPS processes the BOOTP request messages from other boards in the EPS. After receiving the BOOTP acknowledgement messages, all other boards in the MPS/ EPS load the program files and data files according to the load key. The loading is complete.
If the OMUa is in not stated or in offline mode, the loading process is as follows:
2.144.3.2 Online File Loading

The MBSC supports the online loading of the program files, data files, and DSP files. In addition, the file name and number of the loaded software can be dynamically adjusted. When a version is upgraded or a patch is installed, the files to be loaded are indicated by the new version list delivered by the OMU. l l In the case of the EPS/MPS, the OMU directly downloads the files to the board through the FTP and then writes them to the Flash. In the case of the remote TCS, the OMU synchronizes the files to the memory file system of the SCU in the remote central TCS, notifies the board to download the files from the SCU of the remote central TCS, and then writes them to the Flash.
2.144.4 Parameters
None.
2.144.5 Counters
2.144.6 Glossary

None.
2.145 License Management

2.145.1.1 Scope
This document describes the characteristics and functions of the license management (MRFD-210403 License Management).


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the License Management feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.145.2 Overview
The license management controls the overall capability (capacity and functions) of the authorized services of the authorized NEs (MBSC, BTS, and NodeB). The license management is implemented through the software. To use certain enhanced functions and services, users have
to purchase specific licenses. In this way, users can flexibly choose the network functions and capacity applicable to a specific phase to protect the investment to the maximum extent. In addition, the system capacity expansion is simplified. The MBSC and the BTS share one license file. The NodeB uses its own license file. The characteristics of the license management of the MBSC and the BTS are as follows: l l l l The license file is directly downloaded to the OMU or downloaded from the M2000 to the OMU. The license file takes effect after being activated. The license can be used within one MBSC but not between the MBSCs. All the NodeBs under one RNC share one license file, which records the license information about all NodeBs under the RNC. The license information is distributed on the M2000. The distribution results are sent to the NodeB from the M2000.
The characteristics of the NodeB license management are as follows:
The license information can be assigned to each NodeB on the M2000. But the total number of licenses cannot exceed the number recorded in the license file, and the license cannot be used between RNCs.

When the license file is abnormal or the system capacity exceeds the license restriction, the system enters the trial period (60 days).When the trial period expires, the system runs with the default minimum configuration, that is, configuration of three TRXs, Edge, half rate, and AMR. The license management is as follows: l Uploading, downloading, activating, querying, or deleting the license file Users can perform the preceding operations through MML commands. Users upload and download the license file to the M2000 or NE through FTP. The license file cannot be activated in one of the following conditions: The product name, the equipment serial number (ESN), or the version in the license file is incorrect; the verification of the license key fails. Users can choose whether to specify the file name when querying the license file information. If users specify the file name, detailed information is queried. If users do not specify the file name, the list of all license files saved on the NE is queried. Users can delete the unnecessary license files on the NE. The license file in use cannot be deleted. l l Querying the license usage Users can query the usage of the license file through MML commands. Querying the ESN Huawei requires that the ESN be contained in the license file. Thus, users must provide the ESN when applying for the license file. The license file cannot be activated if the ESN in the license file is different from the actual ESN. l Setting and querying the license emergency state Users can release the license control during emergencies such as snowstorms or earthquakes so that the system enters the license emergency state. In this way, the BSC6900 runs with the maximum capacity to meet the requirements of increasing capacity during emergencies. This function is license-controlled, and thus users have to purchase the corresponding license to set or query the license emergency state.
The setting is incremented by one each time the license is set to the emergency state (each setting lasts for seven days). A maximum of three emergency states can be set. Users can manually exit from the emergency state through MML commands. Alternatively, users wait for seven days so that the system automatically exits from the emergency state. Users can query whether the system is in the license emergency state through MML commands. In the license emergency state, users can query the remaining days of the emergency state. In addition, users can query the times that the current system can be set to the license emergency state through MML commands. l Setting and querying the threshold for pre-warning the license overload Users can set and query the threshold for pre-warning the license overload through MML commands. If the load of resource items controlled by the license exceeds the preset threshold, the system triggers the Number of Resources Used Reaching Alarm Threshold Specified by License alarm. l Checking the consistency of the license data on the BAM and FAM To facilitate the problem location, users can check whether the license data on the BAM is consistent with that on the FAM through MML commands. If the license data is inconsistent, re-activate the license file or reset the board where the data inconsistency exists. l l Setting and querying the distribution of the license shared by multiple operators This function is only supported in the UMTS network. Checking the license control items and configuration data In the GSM network, users can check whether the control items of optional features in the license file are consistent with the configuration data through MML commands. Only the optional features authorized by the license can be enabled through configuration. If unauthorized features are used, the system enters the configuration-limited state.
2.145.4 Parameters
None.
2.145.5 Counters
2.145.6 Glossary

None.
2.146 Network Structure

2.146.1.1 Scope
This document describes the principles of star topology, tree topology, and chain topology. This section describes the following features: l l l MRFD-210204 Star Topology MRFD-210205 Chain Topology MRFD-210206 Tree Topology


The change history provides information on the changes in different document versions. There are two types of changes, which are defined as follows: l Feature change Feature change refers to the change in the Network Structure feature of a specific product version. l Editorial change Editorial change refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
01(2010-01-20)
2.146.2 Overview
The network structure is classified into star topology, tree topology, and chain topology according to the ways of connecting the MBSCs and MBTSs. The star topology is a traditional structure characterized by simple networking, high link reliability, and low maintenance cost. In a star topology, each MBTS is directly connected to the MBSC through a transmission link.
The chain topology is a traditional structure, with which the timeslot switching function of the MBTS enables the timeslots of an MBTS to be shared by the lower-level MBTSs for transmission. Thus, the transmission cost for timeslot switching devices is reduced. In this topology, the MBTSs can be connected in chains. The tree topology is a traditional structure applicable to the microwave transmission network. With this feature, the timeslot switching function of the MBTS enables the timeslots of an MBTS to be shared by the lower-level MBTSs for transmission. Thus, the transmission cost for timeslot switching device is reduced. In this topology, the MBTSs can be connected in trees.

Star Topology
The star topology is applied to urban areas, especially densely populated areas. In a star topology, each MBTS is directly connected to the MBSC through a transmission link. The MBTSs are mutually independent. Thus, the network architecture is simple. Generally, this topology is suitable for sites of large configuration.
Chain Topology
The chain topology is used along highways or railways and in sparsely populated areas. It can significantly save the transmission resources. In some cases, multiple E1 links can be used for transmission in a chain topology. The number of levels of MBTSs in a chain topology should not exceed five.
Tree Topology
The tree topology is used in large and sparsely populated areas. The tree topology has a lower demand for the transmission cables than the star topology. Compared with the star topology, the transmission reliability is lower and the construction and maintenance are more complicated because signals pass through many nodes. In addition, the fault in a MBTS may affect the normal operation of its lower-level MBTSs. Capacity expansion is difficult because it may involve great effort in modifying the network architecture. The tree topology applies to areas in which the subscriber distribution is complicated.
Issue 08 (2011-09-30)
1589
In the tree topology, the MBTS obtains the clock signals by locking the upper-level network. Each phase-lock may affect the quality of clock signals. Therefore, the number of levels of MBTSs should not exceed five.
2.146.4 Parameters
None.
2.146.5 Counters
2.146.6 Glossary

None.
Issue 08 (2011-09-30)
1590
3 Operation and Maintenance
Operation and Maintenance
Issue 08 (2011-09-30)
1591

GBSS9.0 Feature Parameter Description

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

GBSS9.0 Feature Parameter Description

Загружено:

Авторское право:

Доступные форматы

GBSS9.

GBSS Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

GBSS Feature Parameter Description

2 GBSS Feature Parameter Description......................................................................................92

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description

GBSS Feature Parameter Description