BSS Feature Description (V900R008C01 - 02)

HUAWEI BSC6000 Base Station Subsystem V900R008
BSS Feature Description
Issue Date INTERNAL
02 2008-06-30
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.
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:
Copyright Huawei Technologies Co., Ltd. 2008. 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 the property of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
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 the statements, information, and recommendations in this document do not constitute a warranty of any kind, express or implied.
HUAWEI BSC6000 Base Station Subsystem BSS Feature Description
Contents
Contents
1 BSS Feature Description...........................................................................................................1-1 2 Channel Management...............................................................................................................2-1
2.1 Overview.........................................................................................................................................................2-2 2.2 Availability......................................................................................................................................................2-3 2.3 Technical Description.....................................................................................................................................2-4 2.3.1 Channel Assignment Procedure.............................................................................................................2-5 2.3.2 Pre-Processing of Channel Assignment.................................................................................................2-6 2.3.3 Channel Assignment Algorithms...........................................................................................................2-7 2.3.4 Processing After Channel Assignment...................................................................................................2-9 2.4 Implementation..............................................................................................................................................2-10 2.4.1 Configuring Channel Assignment Algorithm Parameters...................................................................2-10 2.4.2 Configuring Call Control Parameters...................................................................................................2-14 2.4.3 Examples: Configuring Channel Management....................................................................................2-16 2.5 Maintenance Information..............................................................................................................................2-18 2.6 References.....................................................................................................................................................2-25
3 Combined BTS Cabinets..........................................................................................................3-1

3.1 Overview.........................................................................................................................................................3-2 3.2 Availability......................................................................................................................................................3-3 3.3 Technical Description.....................................................................................................................................3-4 3.3.1 Combined Cabinets and Cabinet Groups of the BTS3012.....................................................................3-4 3.3.2 Combined Cabinets and Cabinet Groups of the BTS3006C..................................................................3-6 3.3.3 Hybrid Cabinet Groups of the BTS3012 and the BTS3X......................................................................3-8 3.4 Capabilities......................................................................................................................................................3-9 3.5 Implementation................................................................................................................................................3-9 3.5.1 Installing the Hardware of Combined BTS Cabinets.............................................................................3-9 3.5.2 Configuring Combined BTS Cabinets.................................................................................................3-22 3.6 Maintenance Information..............................................................................................................................3-38 3.7 References.....................................................................................................................................................3-39
4 Flow Control................................................................................................................................4-1
4.1 Overview.........................................................................................................................................................4-2 4.2 Availability......................................................................................................................................................4-2 4.3 Impact..............................................................................................................................................................4-4 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd i
Contents
4.4 Technical Description.....................................................................................................................................4-4 4.4.1 Flow Control Measures..........................................................................................................................4-4 4.4.2 Flow Control Algorithms.......................................................................................................................4-5 4.5 Implementation..............................................................................................................................................4-21 4.5.1 Configuring Flow Control....................................................................................................................4-21 4.6 Maintenance Information..............................................................................................................................4-23 4.7 References.....................................................................................................................................................4-24
5 Multiband Network...................................................................................................................5-1
5.1 Overview.........................................................................................................................................................5-2 5.2 Availability......................................................................................................................................................5-3 5.3 Technical Description.....................................................................................................................................5-4 5.3.1 Mapping Between ARFCN and Frequency...........................................................................................5-5 5.3.2 Frequency Assignment for TRXs...........................................................................................................5-6 5.3.3 Multiband Channel Assignment.............................................................................................................5-7 5.3.4 Frequency Band Features.......................................................................................................................5-8 5.3.5 Multiband Network Topology..............................................................................................................5-10 5.3.6 Technical Principles.............................................................................................................................5-12 5.3.7 Traffic Guiding Strategy......................................................................................................................5-17 5.3.8 Enhanced Dual-Band Network.............................................................................................................5-18 5.4 Implementation..............................................................................................................................................5-19 5.4.1 Configuring the Multiband Network....................................................................................................5-20 5.4.2 Verifying the Multiband Network........................................................................................................5-25 5.4.3 Deactivating the Multiband Network...................................................................................................5-25 5.4.4 Configuring the Enhanced Dual-Band Network..................................................................................5-26 5.5 Maintenance Information..............................................................................................................................5-28 5.6 References.....................................................................................................................................................5-31
6 Power Control.............................................................................................................................6-1
6.1 Overview.........................................................................................................................................................6-2 6.2 Availability......................................................................................................................................................6-3 6.3 Technical Description.....................................................................................................................................6-4 6.3.1 Classification..........................................................................................................................................6-4 6.3.2 Procedure for Power Control..................................................................................................................6-6 6.3.3 Huawei II Power Control Algorithm......................................................................................................6-7 6.3.4 Huawei III Power Control Algorithm..................................................................................................6-13 6.4 Capabilities....................................................................................................................................................6-16 6.5 Implementation..............................................................................................................................................6-16 6.5.1 Activating Power Control.....................................................................................................................6-16 6.5.2 Configuring Power Control..................................................................................................................6-18 6.6 Maintenance Information..............................................................................................................................6-21 6.7 References.....................................................................................................................................................6-23
7 Handover......................................................................................................................................7-1
ii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Contents
7.1 Overview.........................................................................................................................................................7-2 7.2 Availability......................................................................................................................................................7-4 7.3 Technical Description.....................................................................................................................................7-5 7.3.1 Handover Preprocessing.........................................................................................................................7-6 7.3.2 Handover Decision Algorithm.............................................................................................................7-11 7.4 Implementation..............................................................................................................................................7-27 7.4.1 Configuring the Handover....................................................................................................................7-27 7.4.2 Configuring Power Boost Before Handover........................................................................................7-37 7.5 Maintenance Information..............................................................................................................................7-38 7.6 References.....................................................................................................................................................7-65
8 2G/3G Interoperability..............................................................................................................8-1
8.1 Overview.........................................................................................................................................................8-2 8.2 Availability......................................................................................................................................................8-4 8.3 Technical Description.....................................................................................................................................8-5 8.3.1 System Messages Involved in Cell Reselection.....................................................................................8-5 8.3.2 Inter-RAT Measurement in Cell Reselection.........................................................................................8-6 8.3.3 Better 3G Cell Handover........................................................................................................................8-7 8.3.4 2G/3G Inter-RAT Cell Reselection........................................................................................................8-7 8.3.5 Types of 2G/3G Inter-RAT Handovers..................................................................................................8-9 8.3.6 2G/3G Inter-RAT Handover Procedure.................................................................................................8-9 8.3.7 Algorithms of 2G/3G Inter-RAT Handovers.......................................................................................8-11 8.4 Capabilities....................................................................................................................................................8-12 8.5 Implementation..............................................................................................................................................8-12 8.5.1 Configuring 2G/3G Interoperability.....................................................................................................8-12 8.5.2 Reconfiguring 2G/3G Interoperability.................................................................................................8-22 8.6 Maintenance Information..............................................................................................................................8-25 8.7 References.....................................................................................................................................................8-30
9 Message Tracing.........................................................................................................................9-1
9.1 Overview.........................................................................................................................................................9-2 9.2 Availability......................................................................................................................................................9-3 9.3 Impact..............................................................................................................................................................9-4 9.4 Technical Description.....................................................................................................................................9-5 9.4.1 Message Tracing Procedure...................................................................................................................9-5 9.4.2 Signaling Tracing...................................................................................................................................9-6 9.4.3 User Tracing...........................................................................................................................................9-7 9.5 Capabilities......................................................................................................................................................9-7 9.6 Implementation................................................................................................................................................9-7 9.6.1 Configuring Message Tracing................................................................................................................9-8 9.7 Maintenance Information..............................................................................................................................9-29 9.8 References.....................................................................................................................................................9-30
10 EFR............................................................................................................................................10-1
Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd iii
Contents
10.1 Overview.....................................................................................................................................................10-2 10.2 Availability..................................................................................................................................................10-2 10.3 Technical Description.................................................................................................................................10-3 10.3.1 EFR Call Establishment Procedure....................................................................................................10-3 10.3.2 EFR Call Signaling Procedure...........................................................................................................10-4 10.4 Implementation............................................................................................................................................10-5 10.4.1 Configuring EFR................................................................................................................................10-6 10.5 Maintenance Information............................................................................................................................10-7 10.6 References...................................................................................................................................................10-8
11 AMR..........................................................................................................................................11-1
11.1 Overview.....................................................................................................................................................11-2 11.2 Availability..................................................................................................................................................11-3 11.3 Technical Description.................................................................................................................................11-5 11.3.1 AMR Call...........................................................................................................................................11-6 11.3.2 AMR Voice Rate Adjustment............................................................................................................11-9 11.3.3 Algorithm for AMR Intra-Cell Handover Between AMR Full-Rate and AMR Half-Rate.............11-12 11.3.4 AMR Power Control........................................................................................................................11-14 11.3.5 AMR Channel Assignment..............................................................................................................11-15 11.3.6 Impact on KPI..................................................................................................................................11-16 11.4 Capabilities................................................................................................................................................11-17 11.5 Implementation..........................................................................................................................................11-17 11.5.1 Suggestions on AMR Configuration................................................................................................11-17 11.5.2 Configuring AMR............................................................................................................................11-18 11.5.3 Verifying AMR................................................................................................................................11-27 11.5.4 Disabling AMR................................................................................................................................11-29 11.6 Maintenance Information..........................................................................................................................11-32 11.7 References.................................................................................................................................................11-40
12 Half-Rate Service....................................................................................................................12-1
12.1 Overview.....................................................................................................................................................12-2 12.2 Availability..................................................................................................................................................12-3 12.3 Impact..........................................................................................................................................................12-4 12.4 Technical Description.................................................................................................................................12-5 12.4.1 Channel Rate Assignment Strategies.................................................................................................12-6 12.4.2 Rate Adjustment Algorithms..............................................................................................................12-7 12.4.3 Priority-Based Resource Reservation...............................................................................................12-16 12.4.4 Estimation of the Number TCHFs and TCHHs in a Cell.................................................................12-16 12.5 Capabilities................................................................................................................................................12-18 12.6 Implementation..........................................................................................................................................12-18 12.6.1 Suggestions for Configuring the Half-Rate Service.........................................................................12-18 12.6.2 Configuring the Half-Rate Service...................................................................................................12-27 12.6.3 Verifying the Half-Rate Service.......................................................................................................12-32 12.6.4 Enabling the Function of Reserving Priority Resources..................................................................12-36 iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Contents
12.6.5 Disabling the Half-Rate Service.......................................................................................................12-38 12.7 Maintenance Information..........................................................................................................................12-39 12.8 References.................................................................................................................................................12-41
13 Automatic Level Control.......................................................................................................13-1

13.1 Overview.....................................................................................................................................................13-2 13.2 Availability..................................................................................................................................................13-3 13.3 Technical Description.................................................................................................................................13-3 13.4 Capabilities..................................................................................................................................................13-4 13.5 Implementation............................................................................................................................................13-4 13.5.1 Configuring ALC...............................................................................................................................13-4 13.6 Maintenance Information............................................................................................................................13-6 13.7 References...................................................................................................................................................13-6
14 Acoustic Echo Cancellation..................................................................................................14-1

14.1 Overview.....................................................................................................................................................14-2 14.2 Availability..................................................................................................................................................14-2 14.3 Technical Description.................................................................................................................................14-3 14.4 Implementation............................................................................................................................................14-4 14.4.1 Configuring Acoustic Echo Cancellation...........................................................................................14-4 14.5 Maintenance Information............................................................................................................................14-5 14.6 References...................................................................................................................................................14-5
15 Cell Broadcast.........................................................................................................................15-1
15.1 Overview.....................................................................................................................................................15-2 15.2 Availability..................................................................................................................................................15-2 15.3 Technical Description.................................................................................................................................15-4 15.3.1 Cell Broadcast System.......................................................................................................................15-4 15.3.2 Simplified Cell Broadcast System......................................................................................................15-6 15.4 Implementation............................................................................................................................................15-7 15.4.1 Configuring Cell Broadcast................................................................................................................15-7 15.4.2 Configuring Simplified Cell Broadcast............................................................................................15-13 15.5 Maintenance Information..........................................................................................................................15-19 15.6 References.................................................................................................................................................15-21
16 Ciphering.................................................................................................................................16-1
16.1 Overview.....................................................................................................................................................16-2 16.2 Availability..................................................................................................................................................16-3 16.3 Impact..........................................................................................................................................................16-5 16.4 Technical Description.................................................................................................................................16-5 16.4.1 Kc and Its Generation.........................................................................................................................16-5 16.4.2 A5 Ciphering Algorithm....................................................................................................................16-6 16.4.3 Selection of Ciphering Algorithms....................................................................................................16-7 16.4.4 Signaling Ciphering Procedure..........................................................................................................16-8 16.5 Capabilities..................................................................................................................................................16-9 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd v
Contents
16.6 Implementation............................................................................................................................................16-9 16.6.1 Configuring Ciphering.......................................................................................................................16-9 16.6.2 Reconfiguring Ciphering..................................................................................................................16-12 16.6.3 Disabling Ciphering.........................................................................................................................16-13 16.7 Maintenance Information..........................................................................................................................16-15 16.8 References.................................................................................................................................................16-15
17 Frequency Hopping...............................................................................................................17-1
17.1 Overview.....................................................................................................................................................17-2 17.2 Availability..................................................................................................................................................17-2 17.3 Impact..........................................................................................................................................................17-4 17.4 Technical Description.................................................................................................................................17-4 17.4.1 Principle of Frequency Hopping........................................................................................................17-4 17.4.2 Category of Frequency Hopping........................................................................................................17-6 17.4.3 Frequency Hopping Algorithms.........................................................................................................17-7 17.5 Capabilities..................................................................................................................................................17-9 17.6 Implementation............................................................................................................................................17-9 17.6.1 Changing None FH to RF FH..........................................................................................................17-10 17.6.2 Changing None FH to Baseband FH................................................................................................17-18 17.6.3 Changing RF FH to Baseband FH....................................................................................................17-25 17.6.4 Changing Baseband FH to RF FH....................................................................................................17-34 17.6.5 Changing RF FH to None FH..........................................................................................................17-43 17.6.6 Changing Baseband FH to None FH................................................................................................17-51 17.7 Maintenance Information..........................................................................................................................17-57 17.8 References.................................................................................................................................................17-57
18 eMLPP......................................................................................................................................18-1
18.1 Overview.....................................................................................................................................................18-2 18.2 Availability..................................................................................................................................................18-3 18.3 Impact..........................................................................................................................................................18-4 18.4 Technical Description.................................................................................................................................18-5 18.4.1 A Interface Parameters Involved in eMLPP.......................................................................................18-5 18.4.2 Call Establishment Procedure............................................................................................................18-6 18.5 Capabilities..................................................................................................................................................18-7 18.6 Implementation............................................................................................................................................18-7 18.6.1 Configuring eMLPP...........................................................................................................................18-7 18.6.2 Verifying eMLPP.............................................................................................................................18-10 18.6.3 Disabling eMLPP.............................................................................................................................18-12 18.7 Maintenance Information..........................................................................................................................18-15 18.8 References.................................................................................................................................................18-16
19 GPRS.........................................................................................................................................19-1
19.1 Overview.....................................................................................................................................................19-2 19.2 Availability..................................................................................................................................................19-4 vi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Contents
19.3 Impact..........................................................................................................................................................19-5 19.4 Technical Description.................................................................................................................................19-6 19.4.1 GPRS Networking..............................................................................................................................19-7 19.4.2 MAC Mode........................................................................................................................................19-9 19.4.3 RLC Mode..........................................................................................................................................19-9 19.4.4 Network Operation Mode...................................................................................................................19-9 19.4.5 Quality of Service.............................................................................................................................19-10 19.4.6 TBF Assignment..............................................................................................................................19-14 19.4.7 GPRS/GSM Paging Function...........................................................................................................19-15 19.4.8 GPRS Timing Advance....................................................................................................................19-16 19.4.9 Flow Control....................................................................................................................................19-17 19.4.10 Dynamic Conversion Between TCH and PDCH...........................................................................19-17 19.4.11 Packet Access.................................................................................................................................19-18 19.4.12 Packet System Information............................................................................................................19-19 19.4.13 Measurement Reports.....................................................................................................................19-19 19.4.14 Performance Management..............................................................................................................19-19 19.4.15 Power Control................................................................................................................................19-19 19.4.16 Coding Schemes.............................................................................................................................19-20 19.4.17 Gb Interface....................................................................................................................................19-21 19.4.18 Pb Interface....................................................................................................................................19-24 19.5 Capabilities................................................................................................................................................19-29 19.6 Implementation..........................................................................................................................................19-30 19.6.1 Configuration Principles (with Built-in PCU).................................................................................19-30 19.6.2 Configuring GPRS (with Built-in PCU)..........................................................................................19-31 19.6.3 Verifying GPRS (with Built-in PCU)..............................................................................................19-37 19.6.4 Configuration Principles (with External PCU)................................................................................19-46 19.6.5 Configuring GPRS (with External PCU).........................................................................................19-46 19.6.6 Verifying GPRS (with External PCU).............................................................................................19-54 19.7 Maintenance Information..........................................................................................................................19-59 19.8 References.................................................................................................................................................19-74
20 EGPRS......................................................................................................................................20-1
20.1 Overview.....................................................................................................................................................20-2 20.2 Availability..................................................................................................................................................20-3 20.3 Impact..........................................................................................................................................................20-4 20.4 Technical Description.................................................................................................................................20-4 20.4.1 8PSK Modulation Mode.....................................................................................................................20-5 20.4.2 EGPRS Transmit Power.....................................................................................................................20-6 20.4.3 MCS-1 to MCS-9 Coding Schemes...................................................................................................20-6 20.4.4 Link Quality Control..........................................................................................................................20-8 20.4.5 Types of Preferred EGPRS Channels.................................................................................................20-8 20.4.6 CCCH 11Bit EGPRS Access.............................................................................................................20-9 20.4.7 Assignment of Idle Timeslots............................................................................................................20-9 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd vii
Contents
20.5 Capabilities................................................................................................................................................20-10 20.6 Implementation..........................................................................................................................................20-11 20.6.1 Configuring EGPRS (with Built-in PCU)........................................................................................20-11 20.6.2 Configuring EGPRS (with External PCU).......................................................................................20-14 20.7 Maintenance Information..........................................................................................................................20-17 20.8 References.................................................................................................................................................20-27
21 Co-BCCH Cell.........................................................................................................................21-1
21.1 Overview.....................................................................................................................................................21-2 21.2 Availability..................................................................................................................................................21-4 21.3 Impact..........................................................................................................................................................21-5 21.4 Technical Description.................................................................................................................................21-6 21.4.1 GSM900/DSC1800 Co-BCCH Cell Channel Assignment................................................................21-6 21.4.2 GSM900/DCS1800 Co-BCCH Cell Handover..................................................................................21-7 21.5 Capabilities..................................................................................................................................................21-8 21.6 Implementation............................................................................................................................................21-9 21.6.1 Configuration Principles....................................................................................................................21-9 21.6.2 Preparations for the Configuration...................................................................................................21-10 21.6.3 Risk Analysis of the Configuration Scenarios.................................................................................21-11 21.6.4 Configuring the Co-BCCH Cell.......................................................................................................21-16 21.6.5 Deactivating the Co-BCCH Cell......................................................................................................21-23 21.7 Maintenance Information..........................................................................................................................21-24 21.8 References.................................................................................................................................................21-27
22 Satellite Transmission...........................................................................................................22-1
22.1 Overview.....................................................................................................................................................22-2 22.2 Availability..................................................................................................................................................22-2 22.3 Impact..........................................................................................................................................................22-4 22.4 Technical Description.................................................................................................................................22-4 22.4.1 Network Topologies of Satellite Transmission..................................................................................22-4 22.4.2 Satellite Transmission on the Abis Interface......................................................................................22-5 22.4.3 Satellite Transmission on the Pb Interface.........................................................................................22-6 22.4.4 Satellite Transmission on the Gb Interface........................................................................................22-6 22.5 Implementation............................................................................................................................................22-7 22.5.1 Configuring Satellite Transmission on the Ater Interface..................................................................22-7 22.5.2 Configuring Satellite Transmission on the A Interface....................................................................22-10 22.5.3 Configuring Satellite Transmission on the Abis Interface...............................................................22-13 22.5.4 Configuring Satellite Transmission on the Pb Interface..................................................................22-18 22.5.5 Configuring Satellite Transmission on the Gb Interface..................................................................22-19 22.6 Maintenance Information..........................................................................................................................22-20 22.7 References.................................................................................................................................................22-20
23 TRX Cooperation....................................................................................................................23-1
23.1 Overview.....................................................................................................................................................23-2 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Contents
23.2 Availability..................................................................................................................................................23-3 23.3 Impact..........................................................................................................................................................23-4 23.4 Technical Description.................................................................................................................................23-5 23.4.1 BCCH TRX Cooperation...................................................................................................................23-5 23.4.2 Description of the Baseband FH TRX Cooperation...........................................................................23-7 23.4.3 TRX Cooperation Algorithm.............................................................................................................23-9 23.5 Implementation..........................................................................................................................................23-13 23.5.1 Configuring TRX Cooperation.........................................................................................................23-13 23.6 Maintenance Information..........................................................................................................................23-15 23.7 References.................................................................................................................................................23-16
24 Cell Frequency Scan..............................................................................................................24-1

24.1 Overview.....................................................................................................................................................24-2 24.2 Availability..................................................................................................................................................24-2 24.3 Impact..........................................................................................................................................................24-3 24.4 Technical Description.................................................................................................................................24-4 24.5 Capabilities..................................................................................................................................................24-4 24.6 Implementation............................................................................................................................................24-4 24.6.1 Configuring Cell Frequency Scan......................................................................................................24-5 24.7 Maintenance Information............................................................................................................................24-5 24.8 References...................................................................................................................................................24-6
25 High-Speed Signaling...........................................................................................................25-1
25.1 Overview.....................................................................................................................................................25-2 25.2 Availability..................................................................................................................................................25-3 25.3 Impact..........................................................................................................................................................25-3 25.4 Technical Description.................................................................................................................................25-4 25.4.1 Implementation...................................................................................................................................25-4 25.4.2 Comparison Between 2 Mbit/s Signaling Link and 64 kbit/s Signaling Link...................................25-6 25.5 Capabilities..................................................................................................................................................25-8 25.6 Implementation............................................................................................................................................25-8 25.6.1 Configuring High-Speed Signaling Links..........................................................................................25-8 25.6.2 Verifying High-Speed Signaling Links............................................................................................25-11 25.6.3 Disabling High-Speed Signaling links.............................................................................................25-12 25.7 Maintenance Information..........................................................................................................................25-13 25.8 References.................................................................................................................................................25-15
26 Local Multiple Signaling Point...........................................................................................26-1

26.1 Overview.....................................................................................................................................................26-2 26.2 Availability..................................................................................................................................................26-3 26.3 Impact..........................................................................................................................................................26-3 26.4 Technical Description.................................................................................................................................26-4 26.5 Capabilities..................................................................................................................................................26-5 26.6 Implementation............................................................................................................................................26-6 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd ix
Contents
HUAWEI BSC6000 Base Station Subsystem BSS Feature Description 26.6.1 Configuring Local Multiple Signaling Point......................................................................................26-6
26.7 Maintenance Information............................................................................................................................26-9 26.8 References.................................................................................................................................................26-10
27 Semipermanent Link.............................................................................................................27-1
27.1 Overview.....................................................................................................................................................27-2 27.2 Availability..................................................................................................................................................27-2 27.3 Technical Description.................................................................................................................................27-3 27.3.1 Connections of Semipermanent Link.................................................................................................27-4 27.3.2 Implementation of Semipermanent Link............................................................................................27-5 27.4 Capabilities..................................................................................................................................................27-6 27.5 Implementation............................................................................................................................................27-6 27.5.1 Configuring a Semipermanent Link...................................................................................................27-6 27.5.2 Configuring a Monitoring Timeslot...................................................................................................27-8 27.5.3 Verifying a Semipermanent Link.......................................................................................................27-9 27.6 Maintenance Information..........................................................................................................................27-11 27.7 References.................................................................................................................................................27-11
28 Discontinuous Transmission and Discontinuous Reception........................................28-1

28.1 Overview.....................................................................................................................................................28-2 28.2 Availability..................................................................................................................................................28-2 28.3 Technical Description.................................................................................................................................28-3 28.3.1 DTX....................................................................................................................................................28-4 28.3.2 DRX...................................................................................................................................................28-5 28.4 Capabilities..................................................................................................................................................28-6 28.5 Implementation............................................................................................................................................28-6 28.5.1 Configuring DTX...............................................................................................................................28-6 28.5.2 Configuring DRX...............................................................................................................................28-9 28.6 Maintenance Information..........................................................................................................................28-10 28.7 References.................................................................................................................................................28-11
29 Location Service......................................................................................................................29-1
29.1 Overview.....................................................................................................................................................29-2 29.2 Availability..................................................................................................................................................29-2 29.3 Technical Description.................................................................................................................................29-3 29.3.1 Concepts.............................................................................................................................................29-3 29.3.2 Location Service Processing Procedure.............................................................................................29-4 29.3.3 Location Estimate...............................................................................................................................29-4 29.3.4 Message Format.................................................................................................................................29-8 29.4 Capabilities..................................................................................................................................................29-9 29.5 Implementation............................................................................................................................................29-9 29.5.1 Configuring Location Service..........................................................................................................29-10 29.5.2 Configuring Simple Location Service..............................................................................................29-13 29.6 Maintenance Information..........................................................................................................................29-15 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Contents
29.7 References.................................................................................................................................................29-15
30 TFO............................................................................................................................................30-1
30.1 Overview.....................................................................................................................................................30-2 30.2 Availability..................................................................................................................................................30-3 30.3 Impact..........................................................................................................................................................30-4 30.4 Technical Description.................................................................................................................................30-4 30.4.1 TFO Messages....................................................................................................................................30-5 30.4.2 TFO Frame.........................................................................................................................................30-5 30.4.3 TRAU Operating Process in TFO Mode............................................................................................30-6 30.4.4 Realization of TFO.............................................................................................................................30-7 30.5 Capabilities..................................................................................................................................................30-7 30.6 Implementation............................................................................................................................................30-7 30.6.1 Configuring TFO................................................................................................................................30-7 30.6.2 Verifying TFO..................................................................................................................................30-10 30.7 Maintenance Information..........................................................................................................................30-12 30.8 References.................................................................................................................................................30-13
31 PBT............................................................................................................................................31-1
31.1 Overview.....................................................................................................................................................31-2 31.2 Availability..................................................................................................................................................31-2 31.3 Impact..........................................................................................................................................................31-4 31.4 Technical Description.................................................................................................................................31-4 31.5 Capabilities..................................................................................................................................................31-7 31.6 Implementation............................................................................................................................................31-8 31.6.1 Configuring PBT................................................................................................................................31-8 31.6.2 Configuring Dynamic PBT..............................................................................................................31-11 31.7 Maintenance Information..........................................................................................................................31-15 31.8 References.................................................................................................................................................31-16
32 Transmit Diversity.................................................................................................................32-1
32.1 Overview.....................................................................................................................................................32-2 32.2 Availability..................................................................................................................................................32-2 32.3 Technical Description.................................................................................................................................32-4 32.4 Implementation............................................................................................................................................32-6 32.4.1 Cable Connections (Transmit Diversity)............................................................................................32-6 32.4.2 Configuring Transmit Diversity.......................................................................................................32-10 32.4.3 Configuring Dynamic Transmit Diversity.......................................................................................32-11 32.5 Maintenance Information..........................................................................................................................32-14 32.6 References.................................................................................................................................................32-15
33 Four-Way Receive Diversity................................................................................................33-1

33.1 Overview.....................................................................................................................................................33-2 33.2 Availability..................................................................................................................................................33-2 33.3 Technical Description.................................................................................................................................33-3 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xi
Contents
33.4 Capabilities..................................................................................................................................................33-5 33.5 Implementation............................................................................................................................................33-6 33.5.1 Installing Hardware (Four-Way Receive Diversity)..........................................................................33-6 33.5.2 Configuring Four-Way Receive Diversity.........................................................................................33-9 33.6 Maintenance Information..........................................................................................................................33-10 33.7 References.................................................................................................................................................33-10
34 SDCCH Dynamic Adjustment............................................................................................ 34-1

34.1 Overview.....................................................................................................................................................34-2 34.2 Availability..................................................................................................................................................34-2 34.3 Impact..........................................................................................................................................................34-3 34.4 Technical Description.................................................................................................................................34-4 34.4.1 SDCCH Dynamic Adjustment Procedure..........................................................................................34-4 34.4.2 SDCCH Dynamic Adjustment Decision............................................................................................34-5 34.4.3 SDCCH Dynamic Adjustment Algorithms........................................................................................34-9 34.4.4 SDCCH Switchback Decision..........................................................................................................34-12 34.4.5 SDCCH Switchback Procedure........................................................................................................34-14 34.5 Implementation..........................................................................................................................................34-15 34.5.1 Configuring SDCCH Dynamic Adjustment.....................................................................................34-15 34.6 Maintenance Information..........................................................................................................................34-17 34.7 References.................................................................................................................................................34-18
35 NACC........................................................................................................................................35-1
35.1 Overview.....................................................................................................................................................35-2 35.2 Availability..................................................................................................................................................35-2 35.3 Technical Description.................................................................................................................................35-4 35.4 Implementation............................................................................................................................................35-6 35.4.1 Configuring NACC............................................................................................................................35-6 35.5 Maintenance Information............................................................................................................................35-8 35.6 References...................................................................................................................................................35-8
36 NC2............................................................................................................................................36-1
36.1 Overview.....................................................................................................................................................36-2 36.2 Availability..................................................................................................................................................36-2 36.3 Technical Description.................................................................................................................................36-3 36.4 Implementation............................................................................................................................................36-5 36.4.1 Configuring NC2................................................................................................................................36-5 36.4.2 Configuring the External PCU...........................................................................................................36-7 36.5 Maintenance Information..........................................................................................................................36-11 36.6 References.................................................................................................................................................36-12
37 Streaming QoS........................................................................................................................37-1
37.1 Overview.....................................................................................................................................................37-2 37.2 Availability..................................................................................................................................................37-3 37.3 Impact..........................................................................................................................................................37-4 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Contents
37.4 Technical Description.................................................................................................................................37-4 37.4.1 Establishment of PFC.........................................................................................................................37-5 37.4.2 Modification of PFC...........................................................................................................................37-6 37.4.3 Deletion of PFC..................................................................................................................................37-7 37.4.4 GBR-Supported Uplink TBF Establishment Procedure.....................................................................37-7 37.4.5 GBR-Supported Downlink TBF Establishment Procedure................................................................37-8 37.4.6 Resources Reallocation Due to Changes of Uplink and Downlink Codec Modes............................37-8 37.4.7 Resources Reallocation Due to Changes of PFC...............................................................................37-8 37.5 Implementation............................................................................................................................................37-9 37.5.1 Configuring Streaming QoS...............................................................................................................37-9 37.5.2 Verifying Streaming QoS.................................................................................................................37-11 37.6 Maintenance Information..........................................................................................................................37-12 37.7 References.................................................................................................................................................37-12
38 Packet Performance Improvement......................................................................................38-1

38.1 Overview.....................................................................................................................................................38-2 38.2 Availability..................................................................................................................................................38-3 38.3 Technical Description.................................................................................................................................38-5 38.3.1 EGPRS Access of 11-Bit Messages on the CCCH............................................................................38-5 38.3.2 Extended Uplink TBF........................................................................................................................38-6 38.3.3 Takeover of the Packet Immediate Assignment by the BTS..............................................................38-7 38.4 Capabilities..................................................................................................................................................38-8 38.5 Implementation............................................................................................................................................38-8 38.5.1 Configuring Packet Performance Improvement.................................................................................38-8 38.5.2 Verifying Packet Performance Improvement.....................................................................................38-9 38.6 Maintenance Information..........................................................................................................................38-10 38.7 References.................................................................................................................................................38-10
39 Flex Abis...................................................................................................................................39-1
39.1 Overview.....................................................................................................................................................39-2 39.2 Availability..................................................................................................................................................39-3 39.3 Impact..........................................................................................................................................................39-4 39.4 Technical Description.................................................................................................................................39-4 39.4.1 Abis Resources Load-Triggered Half-Rate Assignment Algorithm..................................................39-7 39.4.2 Abis Resources Preempted by the CS Services from the PS Services...............................................39-8 39.5 Implementation............................................................................................................................................39-8 39.5.1 Configuration Suggestions.................................................................................................................39-8 39.5.2 Configuring Flex Abis......................................................................................................................39-10 39.5.3 Configuring an Exclusive Timeslot..................................................................................................39-17 39.6 Maintenance Information..........................................................................................................................39-19 39.7 References.................................................................................................................................................39-21
40 MSC Pool.................................................................................................................................40-1
40.1 Overview.....................................................................................................................................................40-2 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xiii
Contents
40.2 Availability..................................................................................................................................................40-3 40.3 Technical Description................................................................................................................................. 40-4 40.3.1 Typical Topology...............................................................................................................................40-5 40.3.2 TMSI Carrying NRI...........................................................................................................................40-6 40.3.3 Load Balancing Algorithm.................................................................................................................40-7 40.3.4 NAS Node Selection (TMSI).............................................................................................................40-8 40.3.5 NAS Node Selection (IMSI/IMEI).................................................................................................... 40-8 40.3.6 IMSI Paging Processing.....................................................................................................................40-8 40.3.7 Load Reassignment............................................................................................................................40-9 40.3.8 Message Processing on the A Interface............................................................................................40-10 40.4 Capabilities................................................................................................................................................40-11 40.5 Implementation..........................................................................................................................................40-11 40.5.1 Configuring MSC Pool (in A Interface over TDM Mode)..............................................................40-11 40.5.2 Configuring MSC Pool (in A Interface over IP Mode)....................................................................40-18 40.5.3 Verifying MSC Pool.........................................................................................................................40-26 40.6 Maintenance Information..........................................................................................................................40-27 40.7 References.................................................................................................................................................40-27
41 BTS Ring Topology................................................................................................................41-1

41.1 Overview.....................................................................................................................................................41-2 41.2 Availability..................................................................................................................................................41-3 41.3 Impact..........................................................................................................................................................41-5 41.4 Technical Description................................................................................................................................. 41-6 41.4.1 Automatic Switchover During Link Disconnection...........................................................................41-6 41.4.2 Manual Switchover During Link Disconnection............................................................................... 41-6 41.4.3 Types of BTS Ring Topology............................................................................................................41-7 41.4.4 BTS HDLC Ring Topology............................................................................................................... 41-8 41.5 Implementation............................................................................................................................................41-9 41.5.1 Recommended Configuration of BTS Ring Topology...................................................................... 41-9 41.5.2 Configuring BTS Ring Topology.....................................................................................................41-10 41.5.3 Changing Non-Ring Topology to Ring Topology...........................................................................41-16 41.5.4 Verifying BTS Ring Topology.........................................................................................................41-18 41.5.5 Deleting a BTS from Ring Topology...............................................................................................41-20 41.5.6 Manually Switching over BTS Ring Topology................................................................................41-21 41.6 Maintenance Information..........................................................................................................................41-22 41.7 References.................................................................................................................................................41-23
42 Remote Upgrade.....................................................................................................................42-1
42.1 Overview.....................................................................................................................................................42-2 42.2 Availability..................................................................................................................................................42-3 42.3 Technical Description................................................................................................................................. 42-4 42.3.1 Remote Upgrade Modes.....................................................................................................................42-5 42.3.2 Remote Upgrade Procedures..............................................................................................................42-6 42.4 Implementation............................................................................................................................................42-8 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Contents
42.4.1 Precautions for Remote Upgrade.......................................................................................................42-8 42.4.2 Getting Ready for Remote Upgrade...................................................................................................42-8 42.4.3 Creating a Network Element Object................................................................................................42-10 42.4.4 Uploading the Software and Data....................................................................................................42-11 42.4.5 Performing Remote Upgrade...........................................................................................................42-13 42.5 Maintenance Information..........................................................................................................................42-17 42.6 References.................................................................................................................................................42-18
43 APS............................................................................................................................................43-1
43.1 Overview.....................................................................................................................................................43-2 43.2 Availability..................................................................................................................................................43-4 43.3 Technical Description.................................................................................................................................43-5 43.3.1 APS Mode..........................................................................................................................................43-6 43.3.2 Prerequisites for APS.........................................................................................................................43-6 43.3.3 APS Policy.........................................................................................................................................43-6 43.3.4 APS Categories..................................................................................................................................43-8 43.3.5 APS Process.....................................................................................................................................43-11 43.3.6 Other Features of APS......................................................................................................................43-12 43.4 Implementation..........................................................................................................................................43-13 43.4.1 Typical Network Topologies over Optical Ports..............................................................................43-13 43.4.2 Configuring APS..............................................................................................................................43-14 43.4.3 Verifying APS..................................................................................................................................43-17 43.4.4 Deactivating APS.............................................................................................................................43-17 43.5 Maintenance Information..........................................................................................................................43-17 43.6 References.................................................................................................................................................43-18
44 BSC Local Switching.............................................................................................................44-1

44.1 Overview.....................................................................................................................................................44-2 44.2 Availability..................................................................................................................................................44-3 44.3 Impact..........................................................................................................................................................44-5 44.4 Technical Description.................................................................................................................................44-5 44.4.1 Initiation of BSC Local Switching Call.............................................................................................44-6 44.4.2 Recovery of BSC Local Switching Call.............................................................................................44-8 44.4.3 Handover of BSC Local Switching Call............................................................................................44-8 44.5 Implementation............................................................................................................................................44-9 44.5.1 Configuring BSC Local Switching....................................................................................................44-9 44.5.2 Verifying BSC Local Switching......................................................................................................44-14 44.6 Maintenance Information..........................................................................................................................44-16 44.7 References.................................................................................................................................................44-19
45 BTS Local Switching..............................................................................................................45-1

45.1 Overview.....................................................................................................................................................45-2 45.2 Availability..................................................................................................................................................45-4 45.3 Impact..........................................................................................................................................................45-5 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xv
Contents
45.4 Technical Description.................................................................................................................................45-6 45.4.1 Initiation of BTS Local Switching Call..............................................................................................45-6 45.4.2 Recovery of BTS Local Switching Call.............................................................................................45-9 45.4.3 Handover of BTS Local Switching Call............................................................................................ 45-9 45.5 Implementation..........................................................................................................................................45-10 45.5.1 Configuring BTS Local Switching...................................................................................................45-10 45.5.2 Verifying BTS Local Switching.......................................................................................................45-16 45.6 Maintenance Information..........................................................................................................................45-18 45.7 References.................................................................................................................................................45-21
46 Dynamic MAIO......................................................................................................................46-1
46.1 Overview.....................................................................................................................................................46-2 46.2 Availability..................................................................................................................................................46-3 46.3 Technical Description................................................................................................................................. 46-4 46.3.1 Dynamic MAIO Channel Assignment...............................................................................................46-4 46.3.2 Assignment Principle for Dynamic MAIO and HSN.........................................................................46-5 46.4 Capabilities..................................................................................................................................................46-6 46.5 Implementation............................................................................................................................................46-6 46.5.1 Precautions for Configuring Dynamic MAIO....................................................................................46-6 46.5.2 Configuring Dynamic MAIO.............................................................................................................46-7 46.5.3 Verifying Dynamic MAIO.................................................................................................................46-9 46.6 Maintenance Information..........................................................................................................................46-11 46.7 References.................................................................................................................................................46-11
47 Antenna Hopping...................................................................................................................47-1
47.1 Overview.....................................................................................................................................................47-2 47.2 Availability..................................................................................................................................................47-3 47.3 Technical Description................................................................................................................................. 47-4 47.3.1 Hopping Bus.......................................................................................................................................47-4 47.3.2 Antenna Hopping Algorithm..............................................................................................................47-5 47.4 Implementation............................................................................................................................................47-7 47.4.1 Configuring Antenna Hopping...........................................................................................................47-7 47.4.2 Verifying Antenna Hopping...............................................................................................................47-9 47.5 Maintenance Information..........................................................................................................................47-10 47.6 References.................................................................................................................................................47-10
48 Voice Quality Index...............................................................................................................48-1

48.1 Overview.....................................................................................................................................................48-2 48.2 Availability..................................................................................................................................................48-3 48.3 Technical Description................................................................................................................................. 48-4 48.3.1 Principle of Voice Quality Index....................................................................................................... 48-4 48.3.2 Measurement of Voice Quality..........................................................................................................48-5 48.4 Implementation............................................................................................................................................48-7 48.4.1 Configuring Voice Quality Index.......................................................................................................48-7 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Contents
48.4.2 Verifying Voice Quality Index...........................................................................................................48-9 48.5 Maintenance Information..........................................................................................................................48-11 48.6 References.................................................................................................................................................48-12
49 Automatic Noise Restraint...................................................................................................49-1

49.1 Overview.....................................................................................................................................................49-2 49.2 Availability..................................................................................................................................................49-2 49.3 Technical Description.................................................................................................................................49-3 49.4 Implementation............................................................................................................................................49-4 49.4.1 Configuring ANR...............................................................................................................................49-4 49.5 Maintenance Information............................................................................................................................49-5 49.6 References...................................................................................................................................................49-5
50 Intelligent Power Consumption Decrease........................................................................50-1

50.1 Overview.....................................................................................................................................................50-2 50.2 Availability..................................................................................................................................................50-3 50.3 Technical Description.................................................................................................................................50-4 50.3.1 Intelligent Power Consumption Decrease Configured with the TRX Module..................................50-5 50.3.2 Intelligent Power Consumption Decrease Not Configured with the TRX Module...........................50-6 50.3.3 Intelligent Shutdown of the TRX Power Amplifier...........................................................................50-6 50.3.4 Intelligent Shutdown of the TRX Power Amplifier and Channel Assignment..................................50-7 50.4 Implementation............................................................................................................................................50-7 50.4.1 Configuring Intelligent Power Consumption Decrease.....................................................................50-7 50.5 Maintenance Information..........................................................................................................................50-11 50.6 References.................................................................................................................................................50-11
51 BCCH Dense Frequency Multiplexing..............................................................................51-1

51.1 Overview.....................................................................................................................................................51-2 51.2 Availability..................................................................................................................................................51-2 51.3 Impact..........................................................................................................................................................51-3 51.4 Technical Description.................................................................................................................................51-3 51.5 Implementation............................................................................................................................................51-5 51.5.1 Recommended Configuration of Tight BCCH Frequency Reuse......................................................51-5 51.5.2 Configuring Tight BCCH Frequency Reuse......................................................................................51-6 51.5.3 Disabling Tight BCCH Frequency Reuse........................................................................................51-10 51.6 Maintenance Information..........................................................................................................................51-12 51.7 References.................................................................................................................................................51-12
52 Intra BSC Soft-Synchronized Network.............................................................................52-1

52.1 Overview.....................................................................................................................................................52-2 52.2 Availability..................................................................................................................................................52-3 52.3 Impact..........................................................................................................................................................52-4 52.4 Technical Description.................................................................................................................................52-4 52.4.1 Collecting the Offset Information Between BTSs.............................................................................52-5 52.4.2 Synchronizing Two BTSs..................................................................................................................52-5 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xvii
Contents
HUAWEI BSC6000 Base Station Subsystem BSS Feature Description 52.4.3 Synchronizing the Entire Network.....................................................................................................52-6 52.4.4 Managing the Synchronization Status of BTSs..................................................................................52-7
52.5 Capabilities..................................................................................................................................................52-7 52.6 Implementation............................................................................................................................................52-7 52.6.1 Recommended Configuration of Um Interface Software Synchronization.......................................52-8 52.6.2 Configuring Um Interface Software Synchronization........................................................................52-8 52.6.3 Verifying Um interface Software Synchronization............................................................................52-9 52.6.4 Disabling Um Interface Software Synchronization............................................................................52-9 52.7 Maintenance Information............................................................................................................................52-9 52.8 References...................................................................................................................................................52-9
53 Interface over IP......................................................................................................................53-1

53.1 Overview.....................................................................................................................................................53-2 53.2 Availability..................................................................................................................................................53-5 53.3 Impact..........................................................................................................................................................53-6 53.4 Technical Description.................................................................................................................................53-6 53.4.1 A over IP............................................................................................................................................53-7 53.4.2 Abis over IP......................................................................................................................................53-10 53.4.3 Gb over IP........................................................................................................................................53-13 53.5 Capabilities................................................................................................................................................53-14 53.6 Implementation..........................................................................................................................................53-14 53.6.1 Configuring A over IP......................................................................................................................53-15 53.6.2 Configuring Abis over IP.................................................................................................................53-17 53.6.3 Configuring Gb over IP....................................................................................................................53-19 53.7 Maintenance Information..........................................................................................................................53-19 53.8 References.................................................................................................................................................53-21
54 Abis Transmission Optimization........................................................................................54-1

54.1 Overview.....................................................................................................................................................54-2 54.2 Availability..................................................................................................................................................54-3 54.3 Impact..........................................................................................................................................................54-4 54.4 Technical Description.................................................................................................................................54-4 54.4.1 HDLC over E1/T1..............................................................................................................................54-5 54.4.2 HDLC Channel...................................................................................................................................54-6 54.4.3 HubBTS..............................................................................................................................................54-7 54.4.4 Service Bearer on the BSC Signaling Plane and User Plane.............................................................54-8 54.4.5 HDLC Setup on the BTS Maintenance Plane and Service Plane.......................................................54-8 54.4.6 Procedure for Transmitting the BTS Uplink Data.............................................................................54-9 54.4.7 Procedure for Transmitting the BTS Downlink Data.......................................................................54-11 54.4.8 Resource Allocation on the Abis Interface.......................................................................................54-13 54.5 Implementation..........................................................................................................................................54-13 54.5.1 Configuration Principles of the HDLC Channel..............................................................................54-14 54.5.2 Configuring Abis Transmission Optimization or HubBTS..............................................................54-14 54.6 Maintenance Information..........................................................................................................................54-27 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Contents
54.7 References.................................................................................................................................................54-28
Issue 02 (2008-06-30)
xix
Figures
Figures
Figure 2-1 Channel assignment procedure...........................................................................................................2-5 Figure 2-2 BSC attributes...................................................................................................................................2-11 Figure 2-3 Set Other Parameter dialog box........................................................................................................2-12 Figure 2-4 Setting channel management parameters..........................................................................................2-13 Figure 2-5 Setting advanced channel management parameters......................................................................... 2-14 Figure 2-6 Set Other Parameter dialog box........................................................................................................2-15 Figure 2-7 Setting call control parameters......................................................................................................... 2-16 Figure 2-8 Setting Allocation TRX Priority Allowed dialog box......................................................................2-17 Figure 2-9 Configure TRX Attributes-TRX1 dialog box...................................................................................2-18 Figure 3-1 Connections of combined cabinets.....................................................................................................3-5 Figure 3-2 Connections of cabinet groups...........................................................................................................3-6 Figure 3-3 Connections of combined cabinets and cabinet groups......................................................................3-7 Figure 3-4 Connections of combined cabinets in chain topology........................................................................3-7 Figure 3-5 Connections of combined cabinets in ring topology..........................................................................3-8 Figure 3-6 Connections of two cabinet groups.................................................................................................. 3-11 Figure 3-7 Connections of three cabinet groups.................................................................................................3-13 Figure 3-8 Connections of three hybrid cabinet groups.....................................................................................3-16 Figure 3-9 Site Device Attributes dialog box.....................................................................................................3-24 Figure 3-10 Binding logical TRX dialog box.................................................................................................... 3-25 Figure 3-11 Set Antenna Feeder Property dialog box........................................................................................3-25 Figure 3-12 Configure Cell TRX dialog box..................................................................................................... 3-26 Figure 3-13 Add or Delete Site Chain dialog box..............................................................................................3-26 Figure 3-14 Add Site Slave Chain dialog box....................................................................................................3-27 Figure 3-15 Configure Connections between Cabinet Groups dialog box.........................................................3-28 Figure 3-16 Site Device Attributes dialog box...................................................................................................3-29 Figure 3-17 Binding logical TRX dialog box.................................................................................................... 3-30 Figure 3-18 Set Antenna Feeder Property dialog box........................................................................................3-30 Figure 3-19 Configure Cell TRX dialog box..................................................................................................... 3-31 Figure 3-20 Add or Delete Site Chain dialog box..............................................................................................3-31 Figure 3-21 Add Site Slave Chain dialog box....................................................................................................3-32 Figure 3-22 Configure Connections between Cabinet Groups dialog box.........................................................3-33 Figure 3-23 Site Device Attributes dialog box...................................................................................................3-34 Figure 3-24 Binding logical TRX dialog box.................................................................................................... 3-35 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xxi
Figures
Figure 3-25 Set Antenna Feeder Property dialog box........................................................................................3-35 Figure 3-26 Configure Cell TRX dialog box.....................................................................................................3-36 Figure 3-27 Add or Delete Site Chain dialog box..............................................................................................3-36 Figure 3-28 Add Site Slave Chain dialog box....................................................................................................3-37 Figure 3-29 Configure Connections between Cabinet Groups dialog box.........................................................3-38 Figure 4-1 Relations between the OM flow control levels and the flow control thresholds..............................4-18 Figure 4-2 Configuring flow control data..........................................................................................................4-21 Figure 4-3 Configuring BSC timer.....................................................................................................................4-22 Figure 4-4 Configuring software parameters.....................................................................................................4-22 Figure 4-5 Configuring TRX attributes..............................................................................................................4-23 Figure 5-1 Frequency band bit for channel priority.............................................................................................5-8 Figure 5-2 Independent MSC networking mode................................................................................................5-10 Figure 5-3 Co-MSC/independent BSC networking mode.................................................................................5-11 Figure 5-4 Co-BSC networking.........................................................................................................................5-12 Figure 5-5 Enhanced dual-band cell...................................................................................................................5-18 Figure 5-6 Add New Cell dialog box.................................................................................................................5-20 Figure 5-7 Set Cell Attributes dialog box..........................................................................................................5-21 Figure 5-8 Set Cell Frequency dialog box..........................................................................................................5-22 Figure 5-9 Configure TRX Attributes dialog box..............................................................................................5-22 Figure 5-10 Set Idle Parameter dialog box.........................................................................................................5-23 Figure 5-11 Set Call Control Parameter dialog box...........................................................................................5-24 Figure 5-12 Set Handover Parameter dialog box...............................................................................................5-25 Figure 5-13 Configuring cell attributes..............................................................................................................5-27 Figure 5-14 Configuring data for the enhanced dual-band network..................................................................5-28 Figure 6-1 Procedure for Power Control..............................................................................................................6-7 Figure 6-2 Procedure for Huawei II Power Control Algorithm...........................................................................6-8 Figure 6-3 Procedure for Huawei III power control algorithm..........................................................................6-14 Figure 6-4 Set Cell Attributes dialog box..........................................................................................................6-17 Figure 6-5 Set Other Parameter dialog box........................................................................................................6-18 Figure 6-6 Set Cell Attributes dialog box..........................................................................................................6-19 Figure 6-7 Set Power Control Parameter dialog box.........................................................................................6-20 Figure 6-8 Setting Huawei II power control parameters....................................................................................6-21 Figure 6-9 Setting Huawei power control parameters...................................................................................6-21 Figure 7-1 Handover decision..............................................................................................................................7-6 Figure 7-2 Load handover..................................................................................................................................7-20 Figure 7-3 Load handover..................................................................................................................................7-21 Figure 7-4 Edge handover..................................................................................................................................7-22 Figure 7-5 Fast-moving micro cell handover.....................................................................................................7-23 Figure 7-6 Cell layer...........................................................................................................................................7-24 Figure 7-7 Set Adjacent Relation Property dialog box......................................................................................7-28 Figure 7-8 Set Cell Attributes dialog box..........................................................................................................7-29 Figure 7-9 Set Handover Parameter dialog box.................................................................................................7-30 xxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Figures
Figure 7-10 Set Handover Parameter dialog box...............................................................................................7-31 Figure 7-11 Filter/penalty data configuration.....................................................................................................7-31 Figure 7-12 Cell handover data configuration....................................................................................................7-32 Figure 7-13 Emergency handover parameters configuration.............................................................................7-33 Figure 7-14 Quick handover parameters configuration......................................................................................7-36 Figure 7-15 Set Cell Attributes dialog box........................................................................................................7-37 Figure 7-16 Set Other Parameter dialog box......................................................................................................7-38 Figure 8-1 Flow chart of the reselection of a dual-mode MS from a GSM cell to a WCDMA cell....................8-8 Figure 8-2 Procedure of the GSM-to-WCDMA handover in the CS domain....................................................8-10 Figure 8-3 Set Cell Attributes dialog box..........................................................................................................8-14 Figure 8-4 Set Handover Parameter dialog box.................................................................................................8-15 Figure 8-5 Configure 3G External Cell dialog box............................................................................................8-16 Figure 8-6 Set Adjacent Relation Property dialog box......................................................................................8-17 Figure 8-7 Configuring UTRAN FDD handover data.......................................................................................8-18 Figure 8-8 Setting UTRAN system message parameters...................................................................................8-19 Figure 8-9 Delete 3G External Cell dialog box..................................................................................................8-23 Figure 8-10 Configure 3G External Cell dialog box..........................................................................................8-24 Figure 8-11 Configure 3G External Cell Attributes dialog box.........................................................................8-25 Figure 9-1 Trace BSSAP Message on the A Interface dialog box.......................................................................9-8 Figure 9-2 Trace SCCP Message on the A Interface dialog box.......................................................................9-10 Figure 9-3 Trace MTP2 Message on the A Interface dialog box.......................................................................9-11 Figure 9-4 Trace MTP3 Message on the A Interface dialog box.......................................................................9-12 Figure 9-5 Trace SCTP Message on the A Interface dialog box........................................................................9-13 Figure 9-6 Trace M3UA Message on the A Interface dialog box......................................................................9-14 Figure 9-7 Trace RSL Message on the Abis Interface dialog box.....................................................................9-15 Figure 9-8 Trace OML Message on the Abis Interface dialog box....................................................................9-16 Figure 9-9 Trace ESL Message on the Abis Interface dialog box.....................................................................9-17 Figure 9-10 Trace EML Message on the Abis Interface dialog box..................................................................9-18 Figure 9-11 Trace LAPD Message on the Abis Interface dialog box................................................................9-19 Figure 9-12 Trace Application Message on the Pb Interface dialog box...........................................................9-20 Figure 9-13 Trace LAPD Message on the Pb interface dialog box....................................................................9-21 Figure 9-14 Trace Message on the Um Interface dialog box.............................................................................9-22 Figure 9-15 Trace User Message dialog box......................................................................................................9-23 Figure 9-16 Trace the Message at the BSC-CBC Interface dialog box.............................................................9-24 Figure 9-17 Trace PS PTP Message on the Gb Interface dialog box.................................................................9-25 Figure 9-18 Trace PS SIG Message on the Gb Interface dialog box.................................................................9-26 Figure 9-19 Trace PS Message on the Um Interface dialog box........................................................................9-27 Figure 9-20 Manage Trace Task dialog box.......................................................................................................9-28 Figure 9-21 Manage Trace File dialog box........................................................................................................9-29 Figure 10-1 EFR call establishment procedure..................................................................................................10-4 Figure 10-2 EFR call signaling procedure.........................................................................................................10-5 Figure 10-3 Setting Cell Attributes dialog box..................................................................................................10-6 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xxiii
Figures
Figure 10-4 Setting advanced call control parameters.......................................................................................10-7 Figure 11-1 AMR call establishment procedure................................................................................................11-7 Figure 11-2 Procedure for determining the AMR speech version.....................................................................11-8 Figure 11-3 Procedure for codec mode adjustment..........................................................................................11-10 Figure 11-4 Adjusting uplink codec modes by the BTS..................................................................................11-11 Figure 11-5 Flow Chart of Algorithm for AMR Intra-Cell Handover Between AMR Full-Rate and AMR HalfRate ...................................................................................................................................................................11-14 Figure 11-6 Configuring A interface tag of the BSC.......................................................................................11-19 Figure 11-7 Set Cell Attributes dialog box...................................................................................................... 11-20 Figure 11-8 Setting Call Control Parameter dialog box...................................................................................11-21 Figure 11-9 Setting advanced call control parameters.....................................................................................11-22 Figure 11-10 Configuring parameters associated with AMR full-rate calls.................................................... 11-22 Figure 11-11 Configuring parameters associated with full-rate and half-rate handover in AMR cells...........11-23 Figure 11-12 Setting power control parameters...............................................................................................11-24 Figure 11-13 Configuring AMR power control parameters in a cell...............................................................11-25 Figure 11-14 Set Channel Parameter dialog box..............................................................................................11-26 Figure 11-15 Configuring AMR channel management parameters in a cell....................................................11-27 Figure 11-16 Trace User Message dialog box..................................................................................................11-28 Figure 11-17 Trace User Message window......................................................................................................11-28 Figure 11-18 Displayed result..........................................................................................................................11-29 Figure 11-19 Configuring A interface tag of the BSC.....................................................................................11-30 Figure 11-20 Setting the cell attributes............................................................................................................ 11-31 Figure 11-21 Setting advanced call control parameters...................................................................................11-32 Figure 12-1 Implementation of half-rate service on the Um interface...............................................................12-5 Figure 12-2 Channel rate adjustment procedure for TCHF only.......................................................................12-9 Figure 12-3 Channel rate adjustment procedure for TCHH only/TCHH preferred.........................................12-10 Figure 12-4 Channel rate adjustment procedure for TCHF preferred..............................................................12-11 Figure 12-5 TCHH-to-PDCH adjustment procedure....................................................................................... 12-13 Figure 12-6 TCHH-to-PDCH adjustment procedure....................................................................................... 12-15 Figure 12-7 Set Cell Attributes dialog box...................................................................................................... 12-29 Figure 12-8 Set Call Control Parameter dialog box.........................................................................................12-30 Figure 12-9 Configure TRX Attributes dialog box..........................................................................................12-31 Figure 12-10 Device attributes.........................................................................................................................12-32 Figure 12-11 Monitor Channel Status(1) dialog box....................................................................................... 12-33 Figure 12-12 Half-rate channel status.............................................................................................................. 12-33 Figure 12-13 Modifying administrative state...................................................................................................12-34 Figure 12-14 Set Cell Attributes dialog box.................................................................................................... 12-35 Figure 12-15 Set Channel Parameter dialog box..............................................................................................12-36 Figure 12-16 Set Cell Attributes dialog box.................................................................................................... 12-37 Figure 12-17 Set Channel Parameter dialog box..............................................................................................12-38 Figure 12-18 Configure TRX Attributes dialog box........................................................................................12-39 Figure 13-1 Configuring the ALC switch..........................................................................................................13-5 Figure 14-1 Configuring the AEC switch..........................................................................................................14-4 xxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Figures
Figure 15-1 Structure of the Cell Broadcast System..........................................................................................15-4 Figure 15-2 Structure of the simplified cell broadcast system...........................................................................15-6 Figure 15-3 Adding GXPUMs...........................................................................................................................15-8 Figure 15-4 Configuring GXPUM attributes (1)................................................................................................15-8 Figure 15-5 Configuring GXPUM attributes (2)................................................................................................15-9 Figure 15-6 Configuring cell broadcast attributes............................................................................................15-10 Figure 15-7 TRX attribute configuration wizard..............................................................................................15-11 Figure 15-8 Configuring TRX attributes..........................................................................................................15-12 Figure 15-9 Adding GXPUMs.........................................................................................................................15-13 Figure 15-10 Configuring GXPUM attributes (1)............................................................................................15-14 Figure 15-11 Configuring GXPUM attributes (2)............................................................................................15-14 Figure 15-12 Configuring simple cell broadcast attributes..............................................................................15-15 Figure 15-13 TRX attribute configuration wizard............................................................................................15-16 Figure 15-14 Configuring TRX attributes........................................................................................................15-17 Figure 15-15 Set Cell Attributes dialog box....................................................................................................15-18 Figure 15-16 Setting other parameters.............................................................................................................15-19 Figure 16-1 Generation of Kc............................................................................................................................16-6 Figure 16-2 Ciphering/deciphering flow............................................................................................................16-7 Figure 16-3 Ciphering procedure.......................................................................................................................16-8 Figure 16-4 Set Cell Attributes dialog box......................................................................................................16-10 Figure 16-5 Setting call control parameters.....................................................................................................16-11 Figure 16-6 Configuring BSC attributes..........................................................................................................16-12 Figure 16-7 Set Cell Attributes dialog box......................................................................................................16-13 Figure 16-8 Modifying ciphering algorithms...................................................................................................16-14 Figure 17-1 Attenuation model..........................................................................................................................17-5 Figure 17-2 Flow of frequency hopping algorithms..........................................................................................17-8 Figure 17-3 Configuring Cells Attributes dialog box......................................................................................17-13 Figure 17-4 Selecting a cell..............................................................................................................................17-13 Figure 17-5 Set Cell Attributes dialog box......................................................................................................17-14 Figure 17-6 Set Cell Attributes dialog box......................................................................................................17-15 Figure 17-7 Configuring FH attributes.............................................................................................................17-16 Figure 17-8 Selecting the RF FH mode............................................................................................................17-16 Figure 17-9 Configuring cell MA group attributes..........................................................................................17-17 Figure 17-10 Configuring Cells Attributes dialog box....................................................................................17-20 Figure 17-11 Selecting a cell............................................................................................................................17-20 Figure 17-12 Set Cell Attributes dialog box....................................................................................................17-21 Figure 17-13 Set Cell Attributes dialog box....................................................................................................17-22 Figure 17-14 Configuring FH attributes...........................................................................................................17-23 Figure 17-15 Selecting the baseband FH mode................................................................................................17-23 Figure 17-16 Configuring cell MA group attributes........................................................................................17-24 Figure 17-17 Configuring Cells Attributes dialog box....................................................................................17-27 Figure 17-18 Selecting a cell............................................................................................................................17-27 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xxv
Figures
Figure 17-19 Set Cell Attributes dialog box....................................................................................................17-28 Figure 17-20 Set Cell Attributes dialog box.................................................................................................... 17-29 Figure 17-21 Configuring FH attributes...........................................................................................................17-30 Figure 17-22 Information box..........................................................................................................................17-30 Figure 17-23 Reconfiguring FH attributes.......................................................................................................17-31 Figure 17-24 Configuring TRX attributes........................................................................................................17-31 Figure 17-25 Assigning a frequency to TRX 2................................................................................................17-32 Figure 17-26 Assigning frequencies completed...............................................................................................17-32 Figure 17-27 Configuring attributes of baseband FH...................................................................................... 17-33 Figure 17-28 Configuring cell MA group attributes........................................................................................17-33 Figure 17-29 Configuring Cells Attributes dialog box.................................................................................... 17-37 Figure 17-30 Selecting a cell............................................................................................................................17-37 Figure 17-31 Set Cell Attributes dialog box.................................................................................................... 17-38 Figure 17-32 Set Cell Attributes dialog box.................................................................................................... 17-39 Figure 17-33 Configuring FH attributes...........................................................................................................17-40 Figure 17-34 Changing to none FH mode........................................................................................................17-40 Figure 17-35 Configuring attributes of RF FH................................................................................................ 17-41 Figure 17-36 Configuring cell MA group attributes........................................................................................17-42 Figure 17-37 Configuring Cells Attributes dialog box.................................................................................... 17-45 Figure 17-38 Selecting a cell............................................................................................................................17-45 Figure 17-39 Set Cell Attributes dialog box.................................................................................................... 17-46 Figure 17-40 Set Cell Attributes dialog box.................................................................................................... 17-47 Figure 17-41 Configuring FH attributes...........................................................................................................17-48 Figure 17-42 Information box..........................................................................................................................17-48 Figure 17-43 Reconfiguring FH attributes.......................................................................................................17-49 Figure 17-44 Configuring TRX attributes........................................................................................................17-49 Figure 17-45 Assigning a frequency to TRX 2................................................................................................17-50 Figure 17-46 Assigning frequencies completed...............................................................................................17-50 Figure 17-47 Configuring Cells Attributes dialog box.................................................................................... 17-53 Figure 17-48 Selecting a cell............................................................................................................................17-53 Figure 17-49 Set Cell Attributes dialog box.................................................................................................... 17-54 Figure 17-50 Set Cell Attributes dialog box.................................................................................................... 17-55 Figure 17-51 Configuring FH attributes...........................................................................................................17-56 Figure 17-52 Changing to none FH mode........................................................................................................17-56 Figure 18-1 Set Cell Attributes dialog box........................................................................................................18-8 Figure 18-2 Setting Allow EMLPP...................................................................................................................18-9 Figure 18-3 Check the Compatibility of Parameters and Site Versions dialog box.........................................18-10 Figure 18-4 Set Cell Attributes dialog box...................................................................................................... 18-11 Figure 18-5 Setting Allow EMLPP.................................................................................................................18-12 Figure 18-6 Set Cell Attributes dialog box...................................................................................................... 18-13 Figure 18-7 Setting Allow EMLPP.................................................................................................................18-14 Figure 18-8 Check the Compatibility of Parameters and Site Versions dialog box.........................................18-15 xxvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Figures
Figure 19-1 GPRS network topology with built-in PCUs..................................................................................19-8 Figure 19-2 GPRS network topology with external PCUs.................................................................................19-8 Figure 19-3 Protocol stack of the Gb interface................................................................................................19-22 Figure 19-4 Gb over FR point-to-point direct connection...............................................................................19-23 Figure 19-5 Gb over FR network connection...................................................................................................19-24 Figure 19-6 Gb over IP direct connection........................................................................................................19-24 Figure 19-7 Gb over IP network connection....................................................................................................19-24 Figure 19-8 Protocol stack of the Pb interface.................................................................................................19-25 Figure 19-9 Configure BSC Attributes dialog box..........................................................................................19-32 Figure 19-10 Add SGSN window....................................................................................................................19-34 Figure 19-11 Set Cell Attributes dialog box....................................................................................................19-35 Figure 19-12 Configure Site Idle Timeslot dialog box....................................................................................19-36 Figure 19-13 Configure TRX Attributes tab page............................................................................................19-37 Figure 19-14 Configure BSC Attributes dialog box........................................................................................19-38 Figure 19-15 BSC Attributes tab page.............................................................................................................19-39 Figure 19-16 NSE tab page..............................................................................................................................19-40 Figure 19-17 BC tab page................................................................................................................................19-41 Figure 19-18 NSVC tab page...........................................................................................................................19-42 Figure 19-19 PTPBVC tab page.......................................................................................................................19-43 Figure 19-20 Local NSVL Identifier tab page.................................................................................................19-44 Figure 19-21 Remote NSVL Identifier tab page..............................................................................................19-45 Figure 19-22 Configure BSC Router dialog box..............................................................................................19-46 Figure 19-23 Configure BSC Attributes dialog box........................................................................................19-47 Figure 19-24 Add PCU dialog box...................................................................................................................19-48 Figure 19-25 Add Board dialog box.................................................................................................................19-49 Figure 19-26 Add Pb Interface E1/T1 dialog box............................................................................................19-50 Figure 19-27 Add Pb Signaling Link dialog box.............................................................................................19-51 Figure 19-28 Set Cell Attributes dialog box....................................................................................................19-52 Figure 19-29 Configure Site Idle Timeslot dialog box....................................................................................19-53 Figure 19-30 Configure TRX Attributes tab page............................................................................................19-54 Figure 19-31 Configure BSC Attributes dialog box........................................................................................19-55 Figure 19-32 BSC Attributes tab page.............................................................................................................19-56 Figure 19-33 View PCU dialog box.................................................................................................................19-57 Figure 19-34 View Pb Signaling Link dialog box...........................................................................................19-58 Figure 19-35 Pb Interface E1 tab page.............................................................................................................19-59 Figure 20-1 I/Q relations for the modulation and demodulation in GSM and EDGE.......................................20-5 Figure 20-2 Rates of GPRS channels and those of EDGE channels..................................................................20-7 Figure 20-3 Configure Site Idle Timeslot dialog box......................................................................................20-12 Figure 20-4 Set Other Parameter dialog box....................................................................................................20-13 Figure 20-5 Channel Attributes tab page.........................................................................................................20-14 Figure 20-6 Configure Site Idle Timeslot dialog box......................................................................................20-15 Figure 20-7 Set Other Parameter dialog box....................................................................................................20-16 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xxvii
Figures
Figure 20-8 Channel Attributes tab page.........................................................................................................20-17 Figure 21-1 Add New Cell dialog box.............................................................................................................21-16 Figure 21-2 Set Cell Attributes dialog box .....................................................................................................21-18 Figure 21-3 Set Cell Frequency dialog box......................................................................................................21-19 Figure 21-4 Configure TRX Attributes dialog box (1)....................................................................................21-19 Figure 21-5 Configure TRX Attributes dialog box (2)....................................................................................21-20 Figure 21-6 Set Call Control Parameter dialog box.........................................................................................21-21 Figure 21-7 Set Handover Parameter dialog box (1)........................................................................................21-22 Figure 21-8 Set Handover Parameter dialog box (2)........................................................................................21-23 Figure 22-1 Typical networking of satellite transmission..................................................................................22-5 Figure 22-2 Add Ater Connection Path dialog box............................................................................................22-8 Figure 22-3 Add Ater Signaling Link dialog box..............................................................................................22-9 Figure 22-4 Configuring timeslot.......................................................................................................................22-9 Figure 22-5 Adding A interface E1/T1............................................................................................................22-10 Figure 22-6 Adding an SS7 signaling link.......................................................................................................22-11 Figure 22-7 Configuring timeslot.....................................................................................................................22-12 Figure 22-8 Configuring MTP3 parameters.....................................................................................................22-13 Figure 22-9 Configuring site attributes (1).......................................................................................................22-14 Figure 22-10 Site Attributes.............................................................................................................................22-15 Figure 22-11 Set Cell Attributes dialog box....................................................................................................22-16 Figure 22-12 Set Idle Parameter dialog box (1)...............................................................................................22-17 Figure 22-13 Configuring Call Control Parameters.........................................................................................22-18 Figure 22-14 Adding Pb interface E1/T1.........................................................................................................22-19 Figure 23-1 Principles for assessing the priority of the candidate TRX..........................................................23-12 Figure 23-2 Set Cell Attributes dialog box......................................................................................................23-14 Figure 23-3 Setting advanced call control parameters.....................................................................................23-15 Figure 24-1 Configure Frequency Scan dialog box...........................................................................................24-5 Figure 25-1 Sigaling link on the A interface (BM/TC separated)......................................................................25-4 Figure 25-2 Signaling link on the A interface (BM/TC combined)...................................................................25-5 Figure 25-3 Formats of the signal units in the 2 Mbit/s signaling link..............................................................25-7 Figure 25-4 Configuring an SS7 signaling link..................................................................................................25-9 Figure 25-5 Adding an SS7 signaling link (MTP2).........................................................................................25-10 Figure 25-6 Adding an SS7 signaling link (MTP3).........................................................................................25-11 Figure 25-7 Viewing SS7 signaling links.........................................................................................................25-12 Figure 25-8 Removing SS7 signaling links......................................................................................................25-13 Figure 26-1 Signaling links between the BSC and the MSC.............................................................................26-5 Figure 26-2 Connections of local multiple signaling points..............................................................................26-5 Figure 26-3 Configure SS7 Signaling Point dialog box.....................................................................................26-7 Figure 26-4 Add OSP dialog box.......................................................................................................................26-7 Figure 26-5 Configure SS7 Signaling Point dialog box.....................................................................................26-8 Figure 26-6 Add a DSP......................................................................................................................................26-8 Figure 26-7 Configure Subrack-OSP Mapping dialog box................................................................................26-9 xxviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Figures
Figure 27-1 Semipermanent link in the BSS system (in TDM transport mode)................................................27-4 Figure 27-2 Semipermanent link in the BSS system (in Abis transport optimization mode)............................27-4 Figure 27-3 Configuring a semipermanent link (2)............................................................................................27-7 Figure 27-4 Configuring a semipermanent link (3)............................................................................................27-7 Figure 27-5 Configuring site monitor timeslot (3).............................................................................................27-8 Figure 27-6 Configuring site monitor timeslot (4).............................................................................................27-9 Figure 27-7 View E1/T1 dialog box.................................................................................................................27-10 Figure 27-8 Ater Interface E1/T1.....................................................................................................................27-11 Figure 28-1 Set Cell Attributes dialog box........................................................................................................28-8 Figure 28-2 Set Cell Attributes dialog box........................................................................................................28-9 Figure 28-3 Setting Cell Attributes dialog box................................................................................................28-10 Figure 29-1 Processing procedure of location service.......................................................................................29-4 Figure 29-2 Location information represented by Ellipsoid Arc.......................................................................29-5 Figure 29-3 Coding of the Location Estimate represented by Ellipsoid Arc.....................................................29-6 Figure 29-4 Configuring the LCS Support Control parameter.........................................................................29-11 Figure 29-5 Set Cell Attributes dialog box...................................................................................................... 29-12 Figure 29-6 Set Other Parameter dialog box....................................................................................................29-13 Figure 29-7 Trace User Message dialog box....................................................................................................29-14 Figure 29-8 Trace User Message window........................................................................................................29-15 Figure 30-1 Tandem operation...........................................................................................................................30-2 Figure 30-2 TFO.................................................................................................................................................30-2 Figure 30-3 Configuring GDPUC/GDPUX attributes.......................................................................................30-8 Figure 30-4 Configuring GDPUC attributes......................................................................................................30-9 Figure 30-5 Configuring the TFO feature..........................................................................................................30-9 Figure 30-6 Querying DSP resources...............................................................................................................30-11 Figure 30-7 Querying DSP channel/link state..................................................................................................30-12 Figure 31-1 Working principle of PBT in the DTRU........................................................................................31-5 Figure 31-2 Installing the TMA.........................................................................................................................31-6 Figure 31-3 Connections between the DTRU (type A) and the DDPU in PBT mode.......................................31-9 Figure 31-4 Connections between the DTRU (type B) and the DDPU in PBT mode.....................................31-10 Figure 31-5 Configuring TRX attributes..........................................................................................................31-11 Figure 31-6 Set Cell Attributes dialog box...................................................................................................... 31-13 Figure 31-7 Set Channel Parameter dialog box................................................................................................31-14 Figure 31-8 Configuring TRX attributes..........................................................................................................31-15 Figure 32-1 Transmit diversity...........................................................................................................................32-5 Figure 32-2 Cable connections between the DTRU and the DDPU in transmit diversity mode.......................32-7 Figure 32-3 cable connections between the DDPM and the DDRM in the BTS3006C in transmit diversity mode. .............................................................................................................................................................................32-8 Figure 32-4 cable connections between the DDPM and the DDRM in the BTS3002E in transmit diversity mode .............................................................................................................................................................................32-9 Figure 32-5 Cable connections in the DBS3900 GSM in transmit diversity mode.........................................32-10 Figure 32-6 Setting DTRU transmit diversity mode........................................................................................32-11 Figure 32-7 Set Cell Attributes dialog box...................................................................................................... 32-12 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xxix
Figures
Figure 32-8 Set Channel Parameter dialog box................................................................................................32-13 Figure 32-9 Configure TRX Attributes dialog box..........................................................................................32-14 Figure 33-1 Working principles of the four-way receive diversity....................................................................33-4 Figure 33-2 ICC algorithm.................................................................................................................................33-5 Figure 33-3 Connection between the DTRU and the DDPU in four-way receive diversity mode....................33-7 Figure 33-4 Setting DTRU four-way receive diversity mode..........................................................................33-10 Figure 34-1 SDCCH dynamic adjustment procedure.........................................................................................34-5 Figure 34-2 Procedure for triggering the SDCCH dynamic adjustment decision..............................................34-6 Figure 34-3 Procedure for the SDCCH dynamic adjustment decision...............................................................34-8 Figure 34-4 Procedure for selecting a TCHF when the TRX is selected.........................................................34-11 Figure 34-5 Procedure for the SDCCH switchback decision...........................................................................34-14 Figure 34-6 Set Cell Attributes dialog box......................................................................................................34-16 Figure 34-7 Set Channel Parameter dialog box................................................................................................34-17 Figure 35-1 Starting NACC...............................................................................................................................35-4 Figure 35-2 Starting NACC and SI Status.........................................................................................................35-5 Figure 35-3 Set Cell Attributes dialog box (NACC)..........................................................................................35-7 Figure 36-1 Cell load reselection mode (1)........................................................................................................36-4 Figure 36-2 Cell load reselection mode (2)........................................................................................................36-5 Figure 36-3 Set Cell Attributes dialog box (NC2).............................................................................................36-6 Figure 36-4 Parameters related to System Information of logical cells.............................................................36-7 Figure 36-5 Configuration successful................................................................................................................36-9 Figure 36-6 Cell dynamic configuration window..............................................................................................36-9 Figure 36-7 Setting NC2 mode (2)...................................................................................................................36-10 Figure 36-8 Setting NC2 mode (2)...................................................................................................................36-10 Figure 36-9 Setting NC2 mode result window.................................................................................................36-11 Figure 37-1 PFC establishment procedure initiated by the BSS........................................................................37-6 Figure 37-2 PFC establishment procedure initiated by the SGSN.....................................................................37-6 Figure 37-3 PFC modification procedure initiated by the BSS..........................................................................37-7 Figure 37-4 PFC deletion procedure initiated by the SGSN..............................................................................37-7 Figure 38-1 Procedure for EGPRS access of 11-bit messages on the CCCH....................................................38-5 Figure 38-2 Procedure for the extended uplink TBF..........................................................................................38-7 Figure 38-3 Procedure for the takeover of the packet immediate assignment by the BTS................................38-8 Figure 39-1 Principle of Flex Abis.....................................................................................................................39-5 Figure 39-2 Flex Abis network topology...........................................................................................................39-6 Figure 39-3 Abis resources load-triggered half-rate assignment procedure......................................................39-7 Figure 39-4 Configuration of BTS combined cabinets and cabinet groups.....................................................39-10 Figure 39-5 Add New Site dialog box..............................................................................................................39-12 Figure 39-6 Set Cell Attributes dialog box......................................................................................................39-13 Figure 39-7 Setting other parameters...............................................................................................................39-14 Figure 39-8 Setting call control parameters.....................................................................................................39-15 Figure 39-9 Setting channel management parameters......................................................................................39-16 Figure 39-10 Configuring the Flex Abis attribute of a BTS............................................................................39-17 xxx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Figures
Figure 39-11 Set Exclusive Timeslot dialog box.............................................................................................39-18 Figure 39-12 Browse Timeslot on the ports on site dialog box....................................................................... 39-19 Figure 40-1 Typical topology of the MSC pool.................................................................................................40-6 Figure 40-2 Position of the NRI in the TMSI....................................................................................................40-7 Figure 40-3 Configuring an SS7 signaling point..............................................................................................40-12 Figure 40-4 Adding the DSP............................................................................................................................40-13 Figure 40-5 Configuring A interface E1/T1.....................................................................................................40-14 Figure 40-6 Adding A interface E1/T1............................................................................................................ 40-14 Figure 40-7 Configuring MSC pool parameters...............................................................................................40-15 Figure 40-8 Configuring the NRI and DPC route............................................................................................40-16 Figure 40-9 Adding the NRI and DPC route....................................................................................................40-16 Figure 40-10 Configuring the Null-NRI and DPC route..................................................................................40-17 Figure 40-11 Adding the Null-NRI and DPC route.........................................................................................40-17 Figure 40-12 Configuring the M3UA destination entity..................................................................................40-19 Figure 40-13 Adding the M3UA destination entity......................................................................................... 40-19 Figure 40-14 Configuring the M3UA link set..................................................................................................40-20 Figure 40-15 Adding the M3UA link set......................................................................................................... 40-20 Figure 40-16 Configuring the M3UA route.....................................................................................................40-21 Figure 40-17 Adding the M3UA route.............................................................................................................40-21 Figure 40-18 Configuring the M3UA link.......................................................................................................40-22 Figure 40-19 Adding the M3UA link...............................................................................................................40-23 Figure 40-20 Configuring MSC pool parameters.............................................................................................40-23 Figure 40-21 Configuring the NRI and DPC route..........................................................................................40-24 Figure 40-22 Adding the NRI and DPC route..................................................................................................40-25 Figure 40-23 Configuring the Null-NRI and DPC route..................................................................................40-25 Figure 40-24 Adding the Null-NRI and DPC route.........................................................................................40-26 Figure 41-1 BTS ring topology (1).....................................................................................................................41-2 Figure 41-2 BTS ring topology (2).....................................................................................................................41-2 Figure 41-3 Transmission in the forward and reverse directions.......................................................................41-7 Figure 41-4 Add New Site dialog box (TDM).................................................................................................41-11 Figure 41-5 Set Rev Info dialog box (1).......................................................................................................... 41-11 Figure 41-6 Add Site dialog box (1)................................................................................................................ 41-12 Figure 41-7 Site Attributes dialog box.............................................................................................................41-13 Figure 41-8 Configuring parameters related to BTS ring topology II..............................................................41-14 Figure 41-9 Add New Site dialog box (HDLC)...............................................................................................41-15 Figure 41-10 Set Rev Info dialog box (2)........................................................................................................ 41-15 Figure 41-11 Add Site dialog box (2).............................................................................................................. 41-16 Figure 41-12 Configure Site Attributes dialog box..........................................................................................41-17 Figure 41-13 Site Attributes dialog box...........................................................................................................41-18 Figure 41-14 Maintain Ring Network dialog box............................................................................................41-19 Figure 41-15 Delete Site dialog box.................................................................................................................41-20 Figure 41-16 Maintain Ring Network dialog box............................................................................................41-22 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xxxi
Figures
Figure 42-1 Architecture of remote upgrade......................................................................................................42-5 Figure 42-2 Procedure for upgrading the entire system in dual-OMU mode.....................................................42-7 Figure 42-3 Create Topo Object dialog box.....................................................................................................42-11 Figure 42-4 Selecting general parameters........................................................................................................42-12 Figure 42-5 Selecting the software...................................................................................................................42-12 Figure 42-6 Selecting general parameters........................................................................................................42-13 Figure 42-7 Selecting the upgrade version.......................................................................................................42-14 Figure 42-8 Upgrade wizard.............................................................................................................................42-15 Figure 43-1 APS priorities.................................................................................................................................43-7 Figure 43-2 Process of APS state transition.......................................................................................................43-8 Figure 43-3 Bidirectional switch mode............................................................................................................43-11 Figure 43-4 Network topology with the BSC directly connected to the MSC.................................................43-14 Figure 43-5 Network topology with the BSC connected to the MSC through an optical transceiver.............43-14 Figure 43-6 Network topology with the BSC connected to the MSC through the electrical port converted by an optical transceiver.............................................................................................................................................43-14 Figure 43-7 Configuring APS attributes..........................................................................................................43-16 Figure 44-1 BSC local switching diagram.........................................................................................................44-2 Figure 44-2 Configuring DSP..........................................................................................................................44-10 Figure 44-3 Modifying DSP.............................................................................................................................44-11 Figure 44-4 BSS General Strategy...................................................................................................................44-12 Figure 44-5 BSC Local Switching Prefix Start................................................................................................44-13 Figure 44-6 BSC Local Switching Prefix Close..............................................................................................44-14 Figure 44-7 Query result..................................................................................................................................44-15 Figure 44-8 Query result..................................................................................................................................44-16 Figure 45-1 BTS local switching diagram.........................................................................................................45-2 Figure 45-2 Configuring DSP..........................................................................................................................45-11 Figure 45-3 Modifying DSP.............................................................................................................................45-11 Figure 45-4 General Strategy of the BSS Local Switching..............................................................................45-12 Figure 45-5 Prefix to start BTS local switch....................................................................................................45-13 Figure 45-6 Segment to avoid BTS local switch..............................................................................................45-14 Figure 45-7 Configuring site attributes (2).......................................................................................................45-15 Figure 45-8 Configuring the Flex Abis attribute of a BTS..............................................................................45-16 Figure 45-9 Querying single user resources.....................................................................................................45-17 Figure 45-10 Querying single user resources...................................................................................................45-18 Figure 46-1 Set Cell Attributes dialog box........................................................................................................46-8 Figure 46-2 Configuring Flex MAIO channel management parameters in a cell..............................................46-9 Figure 46-3 Tracing User Messages.................................................................................................................46-10 Figure 46-4 Result of tracing user messages....................................................................................................46-10 Figure 46-5 Viewing Messages........................................................................................................................46-11 Figure 47-1 Position of the hopping bus in the BTS..........................................................................................47-5 Figure 47-2 Procedure for transmitting the data in antenna hopping.................................................................47-6 Figure 47-3 Procedure for receiving the data in antenna hopping.....................................................................47-7 Figure 47-4 Set Cell Attributes dialog box........................................................................................................47-8 xxxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
Figures
Figure 47-5 Configure Cell Antenna Hopping dialog box.................................................................................47-9 Figure 48-1 VQI model......................................................................................................................................48-4 Figure 48-2 Principle of rectifying the VQI model............................................................................................48-5 Figure 48-3 Set Cell Attributes dialog box........................................................................................................48-8 Figure 48-4 Set Other Parameter dialog box......................................................................................................48-9 Figure 48-5 Trace User Message dialog box....................................................................................................48-10 Figure 48-6 Result of tracing the user message................................................................................................48-10 Figure 48-7 Message explanation.....................................................................................................................48-11 Figure 49-1 Configuring the ANR switch..........................................................................................................49-5 Figure 50-1 Triger Saving Power Function tab page.........................................................................................50-9 Figure 50-2 Set Cell Attributes dialog box......................................................................................................50-10 Figure 50-3 Configure TRX Attributes dialog box..........................................................................................50-11 Figure 51-1 Logical layers of tight BCCH frequency reuse...............................................................................51-4 Figure 51-2 Set Cell Attributes dialog box........................................................................................................51-7 Figure 51-3 Set Channel Parameter dialog box..................................................................................................51-8 Figure 51-4 Set Handover Parameter dialog box...............................................................................................51-9 Figure 51-5 Cell HO Data tab page..................................................................................................................51-10 Figure 51-6 Set Cell Attributes dialog box......................................................................................................51-11 Figure 51-7 Set Channel Parameter dialog box................................................................................................51-12 Figure 52-1 Collecting the offset information....................................................................................................52-5 Figure 52-2 Synchronization of BTSs................................................................................................................52-6 Figure 52-3 Synchronizing the entire network...................................................................................................52-6 Figure 52-4 Synchronization task management.................................................................................................52-7 Figure 53-1 Network topology for A over IP (direct connection)......................................................................53-7 Figure 53-2 Network topology for A over IP (layer 2 network through switches)............................................53-8 Figure 53-3 Network topology for A over IP (layer 3 network through routers)...............................................53-8 Figure 53-4 Reliability of the network topologies for A over IP.......................................................................53-9 Figure 53-5 Protocol stack scheme for A over IP..............................................................................................53-9 Figure 53-6 MSTP-based IP network topology...............................................................................................53-11 Figure 53-7 Data network-based IP network topology....................................................................................53-11 Figure 53-8 Satellite link-based IP network topology (star network topology)...............................................53-12 Figure 53-9 Satellite link-based IP network topology (mesh network topology)............................................53-12 Figure 53-10 Protocol stack scheme for Abis over IP......................................................................................53-13 Figure 53-11 Network topology for Gb over IP...............................................................................................53-13 Figure 53-12 Protocol stack scheme for Gb over IP........................................................................................53-14 Figure 53-13 Configure BSC Attributes dialog box........................................................................................53-15 Figure 54-1 System networking for HDLC over E1/T1 ....................................................................................54-6 Figure 54-2 HDLC channel model.....................................................................................................................54-7 Figure 54-3 Networking of the HubBTS............................................................................................................54-7 Figure 54-4 Procedure for transmitting the BTS uplink data...........................................................................54-10 Figure 54-5 Procedure for transmitting the BTS downlink data......................................................................54-12 Figure 54-6 Resource allocation on the Abis interface....................................................................................54-13 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xxxiii
Figures
Figure 54-7 Add Site dialog box (1)................................................................................................................54-17 Figure 54-8 Add New Site dialog box..............................................................................................................54-18 Figure 54-9 Add Site dialog box (2)................................................................................................................54-19 Figure 54-10 Add Site dialog box (3)..............................................................................................................54-19 Figure 54-11 Adding a cell...............................................................................................................................54-20 Figure 54-12 Add Site dialog box (4)..............................................................................................................54-20 Figure 54-13 Add Site dialog box (5)..............................................................................................................54-21 Figure 54-14 Site Device Attributes dialog box...............................................................................................54-22 Figure 54-15 Set antenna feeder property dialog box......................................................................................54-23 Figure 54-16 Setting antenna feeder attributes.................................................................................................54-23 Figure 54-17 Binding Logical TRX dialog box...............................................................................................54-24 Figure 54-18 Add Site dialog box (6)..............................................................................................................54-25 Figure 54-19 Set Cell Attributes dialog box....................................................................................................54-26
xxxiv
Issue 02 (2008-06-30)
Tables
Tables
Table 2-1 NEs involved in channel management.................................................................................................2-3 Table 2-2 GBSS products and software versions.................................................................................................2-4 Table 2-3 Counters related to channel management...........................................................................................2-18 Table 2-4 Interference band measurement per TRX..........................................................................................2-19 Table 2-5 Channel assignment request measurement per cell............................................................................2-20 Table 2-6 Channel assignment success measurement per TRX.........................................................................2-20 Table 2-7 Channel assignment failure measurement per cell.............................................................................2-22 Table 2-8 Channel assignment concentric cell measurement per cell................................................................2-23 Table 2-9 Channel assignment queue measurement per cell..............................................................................2-25 Table 3-1 NEs involved in combined BTS cabinets.............................................................................................3-3 Table 3-2 GBSS products and software versions.................................................................................................3-3 Table 3-3 Settings of SW8 on the DCSU in the main cabinet...........................................................................3-11 Table 3-4 DIP switch SW1 on the DCMB in cabinet groups.............................................................................3-12 Table 3-5 DIP switch SW8 on the DCMB in cabinet groups.............................................................................3-12 Table 3-6 DIP switch SW11 on the DCMB in cabinet groups...........................................................................3-12 Table 3-7 Setting of the RACK DIP switches....................................................................................................3-15 Table 3-8 Setting of SW1 on the DCSU in the BTS3012..................................................................................3-17 Table 3-9 Setting of SW11 on the DCSU in the BTS3012................................................................................3-17 Table 3-10 Settings of SW2SW5 on the DCSU in the BTS3012.....................................................................3-17 Table 3-11 Setting of SW8 on the DCSU in the BTS3012................................................................................3-17 Table 3-12 Settings of SW9 and SW10 on the DCSU in the BTS3012.............................................................3-18 Table 3-13 Setting of S1 on the CMB in the BTS30..........................................................................................3-18 Table 3-14 Setting of S1 on the CMB in the BTS312........................................................................................3-18 Table 3-15 Setting of S2 on the CMB in the BTS30 or BTS312.......................................................................3-19 Table 3-16 Setting of S3 on the CMB in the BTS30 or BTS312.......................................................................3-19 Table 3-17 Setting of S4 on the CMB in the BTS30 or BTS312.......................................................................3-19 Table 3-18 Setting of S5 on the CMB in the BTS30 or BTS312.......................................................................3-20 Table 3-19 Settings of S1 and S3 on the TRB in the BTS312...........................................................................3-20 Table 3-20 Settings of S5 and S6 on the TRB in the BTS312...........................................................................3-21 Table 3-21 Settings of S1 and S2 on the TRB in the BTS30.............................................................................3-21 Table 3-22 Setting of the DIP switch on the PWB in the BTS30......................................................................3-21 Table 3-23 Setting of the DIP switch on the PWB in the BTS312....................................................................3-22 Table 3-24 Alarms related to combined BTS cabinets.......................................................................................3-38 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xxxv
Tables
HUAWEI BSC6000 Base Station Subsystem BSS Feature Description Table 4-1 NEs involved in flow control...............................................................................................................4-3 Table 4-2 GBSS products and software versions.................................................................................................4-3 Table 4-3 Transition of the flow control states...................................................................................................4-11 Table 4-4 Cell flow control level........................................................................................................................4-12 Table 4-5 Mapping between the cell flow control level and the length of timer T3122....................................4-13 Table 4-6 Auxiliary functions related to the internal flow control levels...........................................................4-14 Table 4-7 Default proportions of messages discarded under different flow control levels................................4-15 Table 4-8 Default proportions of messages discarded under different flow control levels................................4-17 Table 4-9 Mapping between the service type and the service priority...............................................................4-19 Table 4-10 Mapping between the service priority and the congestion level......................................................4-20 Table 4-11 Alarms related to flow control.........................................................................................................4-23 Table 4-12 Counters related to flow control.......................................................................................................4-24 Table 5-1 NEs involved in the multiband network...............................................................................................5-3 Table 5-2 GBSS products and software versions.................................................................................................5-3 Table 5-3 Mapping between the ARFCN and the frequency...............................................................................5-5 Table 5-4 Range of ARFCN supported by each type of TRX..............................................................................5-6 Table 5-5 Cell selection/reselection priority......................................................................................................5-15 Table 5-6 Alarms related to the multiband network...........................................................................................5-28 Table 5-7 Incoming internal inter-cell handover measurement per cell.............................................................5-29 Table 5-8 Outgoing internal inter-cell handover measurement per cell.............................................................5-29 Table 5-9 Incoming external inter-cell handover measurement per cell............................................................5-30 Table 5-10 Outgoing external inter-cell handover measurement per cell and dual-band handover measurement per cell.......................................................................................................................................................................5-31 Table 6-1 NEs involved in power control............................................................................................................6-3 Table 6-2 GBSS products and software versions.................................................................................................6-3 Table 6-3 Static power level.................................................................................................................................6-6 Table 6-4 Dynamic power level...........................................................................................................................6-6 Table 6-5 Comprehensive power control decision table......................................................................................6-9 Table 6-6 Counters related to power control......................................................................................................6-22 Table 7-1 NEs involved in handover....................................................................................................................7-4 Table 7-2 GBSS products and software versions.................................................................................................7-4 Table 7-3 Parameters related to the number of measurement reports..................................................................7-7 Table 7-4 Parameters related to the number of measurement reports..................................................................7-8 Table 7-5 Counters related to handover.............................................................................................................7-39 Table 8-1 NEs involved in 2G/3G interoperability..............................................................................................8-4 Table 8-2 GBSS products and software versions.................................................................................................8-4 Table 8-3 Performance counters related to 2G/3G interoperability...................................................................8-26 Table 9-1 NEs involved in message tracing.........................................................................................................9-3 Table 9-2 GBSS products and software versions.................................................................................................9-3 Table 9-3 Parameters on the Trace BSSAP Message on the A Interface dialog box...........................................9-9 Table 9-4 Parameters on the Trace SCCP Message on the A Interface dialog box...........................................9-10 Table 9-5 Parameters on the Trace MTP2 Message on the A Interface dialog box...........................................9-11 Table 9-6 Parameters on the Trace MTP3 Message on the A Interface dialog box...........................................9-12
xxxvi
Issue 02 (2008-06-30)
Tables
Table 9-7 Parameters on the Trace SCTP Message on the A Interface dialog box............................................9-13 Table 9-8 Parameters on the Trace M3UA Message on the A Interface dialog box..........................................9-14 Table 9-9 Parameters on the Trace RSL Message on the Abis Interface dialog box.........................................9-15 Table 9-10 Parameters on the Trace OML Message on the Abis Interface dialog box......................................9-16 Table 9-11 Parameters on the Trace ESL Message on the Abis Interface dialog box.......................................9-17 Table 9-12 Parameters on the Trace EML Message on the Abis Interface dialog box......................................9-18 Table 9-13 Parameters on the Trace LAPD Message on the Abis Interface dialog box....................................9-19 Table 9-14 Parameters on the Trace Application Message on the Pb Interface dialog box...............................9-20 Table 9-15 Parameters on the Trace LAPD Message on the Pb interface dialog box........................................9-21 Table 9-16 Parameters on the Trace Message on the Um Interface dialog box.................................................9-22 Table 9-17 Parameters on the Trace User Message dialog box..........................................................................9-23 Table 9-18 Parameters on the Trace the Message at the BSC-CBC Interface dialog box.................................9-24 Table 9-19 Parameters on the Trace PS PTP Message on the Gb Interface dialog box.....................................9-25 Table 9-20 Parameters on the Trace PS SIG Message on the Gb Interface dialog box.....................................9-26 Table 9-21 Parameters on the Trace PS Message on the Um Interface dialog box............................................9-27 Table 9-22 Parameters on the Manage Trace Task dialog box..........................................................................9-28 Table 9-23 Parameters on the Manage Trace File dialog box............................................................................9-29 Table 10-1 Network elements involved in EFR.................................................................................................10-2 Table 10-2 GBSS products and software versions.............................................................................................10-3 Table 10-3 Counters involved in EFR................................................................................................................10-7 Table 11-1 NEs involved in AMR......................................................................................................................11-4 Table 11-2 GBSS products and software versions.............................................................................................11-4 Table 11-3 Comparison table.............................................................................................................................11-6 Table 11-4 Mapping between AMR codec modes and voice codec rates..........................................................11-9 Table 11-5 Assignment measurement per cell.................................................................................................11-32 Table 11-6 Intra-cell handover measurement per cell......................................................................................11-33 Table 11-7 RQI measurement based on TA per TRX......................................................................................11-33 Table 11-8 AMR service measurement per cell...............................................................................................11-37 Table 11-9 AMR channel status measurement per cell....................................................................................11-39 Table 11-10 RQI measurement per TRX.........................................................................................................11-39 Table 12-1 NEs involved in half-rate service.....................................................................................................12-3 Table 12-2 GBSS products and software versions.............................................................................................12-3 Table 12-3 High-traffic scenarios.....................................................................................................................12-19 Table 12-4 Low-traffic scenarios.....................................................................................................................12-19 Table 12-5 Configuration principles in the urban network..............................................................................12-19 Table 12-6 Configuration principles in the suburb network.............................................................................12-21 Table 12-7 Impact of adjusting parameters......................................................................................................12-23 Table 12-8 Counters related to the half-rate service.........................................................................................12-39 Table 13-1 NEs related to ALC..........................................................................................................................13-3 Table 13-2 GBSS products and software versions.............................................................................................13-3 Table 14-1 NEs related to AEC..........................................................................................................................14-3 Table 14-2 GBSS products and software versions.............................................................................................14-3 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xxxvii
Tables
HUAWEI BSC6000 Base Station Subsystem BSS Feature Description Table 15-1 NEs involved in cell broadcast.........................................................................................................15-2 Table 15-2 NEs involved in cell broadcast.........................................................................................................15-3 Table 15-3 GBSS products and software versions.............................................................................................15-3 Table 16-1 NEs involved in ciphering................................................................................................................16-3 Table 16-2 GBSS products and software versions.............................................................................................16-3 Table 16-3 Counters related to ciphering.........................................................................................................16-15 Table 17-1 NEs involved in frequency hopping.................................................................................................17-3 Table 17-2 GBSS products and software versions.............................................................................................17-3 Table 17-3 Parameters related to frequency hopping algorithms.......................................................................17-7 Table 17-4 Explanation list of the Table............................................................................................................17-9 Table 17-5 Data to be negotiated and planned for changing none FH to RF FH.............................................17-10 Table 17-6 Example of the data negotiated and planned for changing none FH to RF FH.............................17-11 Table 17-7 Data to be negotiated and planned before you change none FH to baseband FH..........................17-18 Table 17-8 Example of the data negotiated and planned for changing none FH to baseband FH...................17-18 Table 17-9 Data to be negotiated and planned before you change RF FH to baseband FH.............................17-25 Table 17-10 Example of the data negotiated and planned for changing RF FH to baseband FH....................17-26 Table 17-11 Data to be negotiated and planned before you change baseband FH to RF FH...........................17-35 Table 17-12 Example of the data negotiated and planned for changing baseband FH to RF FH....................17-35 Table 17-13 Data to be negotiated and planned before you change RF FH to none FH..................................17-43 Table 17-14 Example of the data negotiated and planned for changing RF FH to none FH...........................17-43 Table 17-15 Data to be negotiated and planned before you change baseband FH to none FH........................17-51 Table 17-16 Example of the data negotiated and planned for changing baseband FH to none FH.................17-52 Table 17-17 Alarms..........................................................................................................................................17-57 Table 18-1 NEs involved in eMLPP ..................................................................................................................18-3 Table 18-2 GBSS products and software versions.............................................................................................18-4 Table 18-3 A interface parameters involved in eMLPP.....................................................................................18-5 Table 18-4 Counters related to eMLPP............................................................................................................18-15 Table 19-1 NEs involved in GPRS.....................................................................................................................19-4 Table 19-2 GBSS products and software versions.............................................................................................19-5 Table 19-3 Network operation modes..............................................................................................................19-10 Table 19-4 Requirements of the reliability class for protocol layers................................................................19-12 Table 19-5 Peak throughput classes.................................................................................................................19-12 Table 19-6 Mean throughput classes................................................................................................................19-13 Table 19-7 GPRS coding schemes and data rates............................................................................................19-20 Table 19-8 Alarms related to internal PCUs....................................................................................................19-59 Table 19-9 Alarms related to external PCUs....................................................................................................19-60 Table 19-10 Counters related to internal PCUs................................................................................................19-60 Table 19-11 Counters related to external PCUs...............................................................................................19-73 Table 20-1 NEs Involved in EDGE....................................................................................................................20-3 Table 20-2 GBSS products and software versions.............................................................................................20-3 Table 20-3 Modulation bits and corresponding symbols...................................................................................20-6 Table 20-4 Modulation and coding schemes in EDGE......................................................................................20-7
xxxviii
Issue 02 (2008-06-30)
Tables
Table 20-5 Coding schemes and number of required Abis links.....................................................................20-10 Table 20-6 Alarms related to the built-in PCU.................................................................................................20-17 Table 20-7 Alarms related to the external PCU...............................................................................................20-18 Table 20-8 Counters related to the built-in PCU..............................................................................................20-18 Table 20-9 Counters related to the external PCU.............................................................................................20-25 Table 21-1 Data in ERLANG B.........................................................................................................................21-2 Table 21-2 NEs involved in Co-BCCH cell.......................................................................................................21-4 Table 21-3 GBSS products and software versions.............................................................................................21-4 Table 21-4 Risk analysis in common scenarios................................................................................................21-11 Table 21-5 Counters related to the Co-BCCH cell...........................................................................................21-24 Table 22-1 NEs involved in satellite transmission.............................................................................................22-3 Table 22-2 GBSS products and software versions.............................................................................................22-3 Table 23-1 NEs involved in TRX cooperation...................................................................................................23-3 Table 23-2 GBSS products and software versions.............................................................................................23-4 Table 23-3 Availability status and meaning.......................................................................................................23-6 Table 23-4 Availability status and meaning.......................................................................................................23-8 Table 23-5 Conditions of the BCCH TRX cooperation and recovery of the original BCCH TRX.................23-10 Table 23-6 Conditions of the baseband FH TRX cooperation and recovery of the original baseband FH TRX ...........................................................................................................................................................................23-10 Table 23-7 Parameters in assessing the priority of the candidate TRX............................................................23-12 Table 23-8 Alarms related to TRX cooperation...............................................................................................23-15 Table 23-9 Counters related to TRX cooperation............................................................................................23-16 Table 24-1 NEs involved in cell frequency scan................................................................................................24-2 Table 24-2 GBSS products and software versions.............................................................................................24-3 Table 25-1 NEs involved in high-speed signaling links.....................................................................................25-3 Table 25-2 GBSS products and software versions.............................................................................................25-3 Table 25-3 Alarms related to high-speed signaling links.................................................................................25-14 Table 25-4 Counters related to high-speed signaling links..............................................................................25-14 Table 26-1 NEs involved in local multiple signaling point................................................................................26-3 Table 26-2 GBSS products and software versions.............................................................................................26-3 Table 27-1 NEs involved in semipermanent link...............................................................................................27-3 Table 27-2 GBSS products and software versions.............................................................................................27-3 Table 28-1 NEs involved in DTX and DRX......................................................................................................28-3 Table 28-2 GBSS products and software versions.............................................................................................28-3 Table 28-3 Relation between CCCH configuration and number of CCCH message blocks in the BCCH multiframe structure.....................................................................................................................................................28-5 Table 29-1 NEs involved in location service......................................................................................................29-2 Table 29-2 GBSS products and software versions.............................................................................................29-3 Table 29-3 Description of coding for the Location Estimate represented by Ellipsoid Arc..............................29-6 Table 29-4 Perform Location Request message.................................................................................................29-8 Table 29-5 Perform Location Response message...............................................................................................29-9 Table 30-1 NEs involved in TFO.......................................................................................................................30-3 Table 30-2 GBSS products and software versions.............................................................................................30-4 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xxxix
Tables
HUAWEI BSC6000 Base Station Subsystem BSS Feature Description Table 31-1 NEs involved in PBT.......................................................................................................................31-3 Table 31-2 GBSS products and software versions.............................................................................................31-3 Table 31-3 GBSS products and software versions.............................................................................................31-3 Table 31-4 Output power of the BTS3012/BTS3012AE in PBT mode.............................................................31-7 Table 31-5 Output power of the DBS3900 GSM in PBT mode.........................................................................31-7 Table 31-6 Alarms............................................................................................................................................31-15 Table 32-1 NEs involved in transmit diversity...................................................................................................32-2 Table 32-2 GBSS products and software versions.............................................................................................32-3 Table 32-3 GBSS products and software versions.............................................................................................32-3 Table 32-4 Alarms related to transmit diversity...............................................................................................32-14 Table 33-1 Network elements involved in the four-way receive diversity........................................................33-2 Table 33-2 GBSS products and software versions.............................................................................................33-3 Table 33-3 ICC gain relative to the MRC gain..................................................................................................33-6 Table 33-4 Description of ports on the DTRU...................................................................................................33-7 Table 33-5 Description of ports on the DDPU...................................................................................................33-8 Table 33-6 Alarms related to four-way receive diversity.................................................................................33-10 Table 34-1 NEs involved in SDCCH dynamic adjustment................................................................................34-3 Table 34-2 GBSS products and software versions.............................................................................................34-3 Table 34-3 Mapping between the frequency band where the BCCH is located and the frequency band supported by the TCHF........................................................................................................................................................34-9 Table 34-4 Counters related to SDCCH dynamic adjustment..........................................................................34-17 Table 35-1 NEs involved in NACC....................................................................................................................35-3 Table 35-2 NEs involved in NACC....................................................................................................................35-3 Table 35-3 GBSS products and software versions.............................................................................................35-3 Table 35-4 GBSS products and software versions.............................................................................................35-3 Table 36-1 NEs involved in NC2.......................................................................................................................36-2 Table 36-2 NEs involved in NC2.......................................................................................................................36-3 Table 36-3 GBSS products and software versions.............................................................................................36-3 Table 36-4 GBSS products and software versions.............................................................................................36-3 Table 36-5 Description of the parameters related to System Information of logical cells.................................36-8 Table 36-6 Counters related to NC2.................................................................................................................36-11 Table 37-1 NEs involved in streaming QoS.......................................................................................................37-3 Table 37-2 NEs involved in streaming QoS.......................................................................................................37-3 Table 37-3 GBSS products and software versions.............................................................................................37-3 Table 37-4 GBSS products and software versions.............................................................................................37-4 Table 38-1 NEs involved in the packet performance improvement...................................................................38-3 Table 38-2 GBSS products and software versions.............................................................................................38-4 Table 38-3 GBSS products and software versions.............................................................................................38-4 Table 38-4 GBSS products and software versions.............................................................................................38-4 Table 39-1 NEs involved in Flex Abis...............................................................................................................39-3 Table 39-2 GBSS products and software versions.............................................................................................39-3 Table 39-3 Alarms related to Flex Abis...........................................................................................................39-19 Table 39-4 Counters related to Flex Abis.........................................................................................................39-20
xl
Issue 02 (2008-06-30)
Tables
Table 40-1 NEs involved in the MSC pool........................................................................................................40-4 Table 40-2 GBSS products and software versions.............................................................................................40-4 Table 40-3 Alarms related to the MSC pool.....................................................................................................40-27 Table 41-1 NEs involved in BTS ring topology.................................................................................................41-3 Table 41-2 GBSS products and software versions supporting BTS ring topology .......................................41-4 Table 41-3 GBSS products and software versions supporting BTS ring topology .......................................41-4 Table 41-4 Parameter configuration of BTS ring topology in good-quality transmission..........................41-10 Table 41-5 Parameter configuration of BTS ring topology in poor-quality transmission...........................41-10 Table 42-1 NEs involved in remote upgrade......................................................................................................42-3 Table 42-2 GBSS products and related versions................................................................................................42-3 Table 42-3 List of downloaded files...................................................................................................................42-9 Table 43-1 NEs involved in APS.......................................................................................................................43-4 Table 43-2 NEs involved in APS.......................................................................................................................43-4 Table 43-3 GBSS products and software versions.............................................................................................43-4 Table 43-4 GBSS products and software versions.............................................................................................43-5 Table 43-5 Composition of K1 byte...................................................................................................................43-9 Table 43-6 Description of the first four bits in K1 byte.....................................................................................43-9 Table 43-7 Composition of K2 byte.................................................................................................................43-10 Table 43-8 K2 byte status code........................................................................................................................43-10 Table 43-9 Alarms related to APS....................................................................................................................43-18 Table 44-1 NEs involved in BSC local switching..............................................................................................44-4 Table 44-2 GBSS products and software versions.............................................................................................44-4 Table 44-3 Policies for selecting a speech version for local switching..............................................................44-7 Table 44-4 Counters related to BSC local switching.......................................................................................44-16 Table 45-1 NEs involved in BTS local switching..............................................................................................45-4 Table 45-2 GBSS products and software versions.............................................................................................45-4 Table 45-3 Policies for selecting a speech version for local switching..............................................................45-7 Table 45-4 Performance counters pertaining to BTS local switch...................................................................45-18 Table 46-1 NEs involved in dynamic MAIO.....................................................................................................46-3 Table 46-2 GBSS products and software versions.............................................................................................46-3 Table 47-1 NEs involved in antenna hopping....................................................................................................47-3 Table 47-2 GBSS products and software versions.............................................................................................47-3 Table 47-3 Alarms related to antenna hopping................................................................................................47-10 Table 48-1 NEs involved in VQI........................................................................................................................48-3 Table 48-2 GBSS products and software versions.............................................................................................48-3 Table 48-3 Voice quality levels..........................................................................................................................48-6 Table 48-4 Counters.........................................................................................................................................48-12 Table 49-1 NEs related to ANR.........................................................................................................................49-3 Table 49-2 GBSS products and software versions.............................................................................................49-3 Table 50-1 NEs involved in intelligent power consumption decrease...............................................................50-3 Table 50-2 GBSS products and software versions.............................................................................................50-3 Table 51-1 NEs involved in tight BCCH frequency reuse.................................................................................51-3 Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd xli
Tables
HUAWEI BSC6000 Base Station Subsystem BSS Feature Description Table 51-2 GBSS products and software versions.............................................................................................51-3 Table 52-1 NEs involved in Um interface software synchronization.................................................................52-3 Table 52-2 GBSS products and software versions.............................................................................................52-4 Table 53-1 NEs involved in interface over IP....................................................................................................53-5 Table 53-2 GBSS products and software versions.............................................................................................53-6 Table 53-3 Mapping between protocol layer and QoS mechanism..................................................................53-10 Table 53-4 Alarms related to interface over IP................................................................................................53-20 Table 53-5 Counters related to interface over IP..............................................................................................53-20 Table 54-1 NEs involved in the Abis transmission optimization.......................................................................54-3 Table 54-2 GBSS products and software versions.............................................................................................54-3 Table 54-3 Example of the data negotiated and planned for adding a BTS.....................................................54-15 Table 54-4 Alarms related to Abis transmission optimization.........................................................................54-27 Table 54-5 Performance counters related to Abis transmission optimization..................................................54-27
xlii
Issue 02 (2008-06-30)
1 BSS Feature Description
1
Basic Feature and Optional Feature
l
BSS Feature Description
This document describes the features of Huawei BSC6000 in terms of overview, availability, technical description, capabilities, implementation, maintenance information, and references.
Basic feature It refers to the feature that Huawei BSS equipment must provide. Optional feature It refers to the feature that Huawei BSS equipment supports while the operator must buy a license from Huawei to enable it.
List of Features
The following table lists the features supported by Huawei BSS equipment. Feature 2 Channel Management 3 Combined BTS Cabinets 4 Flow Control 5 Multiband Network 6 Power Control 7 Handover 8 2G/3G Interoperability 9 Message Tracing 10 EFR 11 AMR 12 Half-Rate Service 13 Automatic Level Control
Issue 02 (2008-06-30)
Type Basic feature Basic feature Basic feature Optional feature Basic feature Basic feature Optional feature Basic feature Optional feature Optional feature Optional feature Optional feature
1-1
Feature 14 Acoustic Echo Cancellation 15 Cell Broadcast 16 Ciphering 17 Frequency Hopping 18 eMLPP 19 GPRS 20 EGPRS 21 Co-BCCH Cell 22 Satellite Transmission 23 TRX Cooperation 24 Cell Frequency Scan 25 High-Speed Signaling 26 Local Multiple Signaling Point 27 Semipermanent Link 28 Discontinuous Transmission and Discontinuous Reception 29 Location Service 30 TFO 31 PBT 32 Transmit Diversity 33 Four-Way Receive Diversity 34 SDCCH Dynamic Adjustment 35 NACC 36 NC2 37 Streaming QoS 38 Packet Performance Improvement 39 Flex Abis 40 MSC Pool 41 BTS Ring Topology 42 Remote Upgrade
Type Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Basic feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Basic feature
1-2
Issue 02 (2008-06-30)
Feature 43 APS 44 BSC Local Switching 45 BTS Local Switching 46 Dynamic MAIO 47 Antenna Hopping 48 Voice Quality Index 49 Automatic Noise Restraint 50 Intelligent Power Consumption Decrease 51 BCCH Dense Frequency Multiplexing 52 Intra BSC Soft-Synchronized Network 53 Interface over IP 54 Abis Transmission Optimization
Type Basic feature Optional feature Optional feature Optional feature Optional feature Optional feature Optional feature Basic feature Optional feature Optional feature Optional feature Optional feature
Feature Structure
The following table lists the structure of BSS Feature Description. Topic Overview Availability Impact Technical Description Capabilities Implementation Maintenance Information References Content Describes the definition and purpose of the feature. Lists the software and hardware required for the feature. Describes the negative impact of the feature on the system and other features. Describes the technical details of the feature. Describes the benefits after the implementation of the feature. Describes the precautions, principles, and steps for configuring the feature. Describes the alarms and counters related to the feature. Describes the protocols related to the feature.
Issue 02 (2008-06-30)
1-3
Related Documents
The following lists the documents to which you can refer while using BSS Feature Description.
l l l l l l l l
BSC LMT User Guide BSC Product Description BTS3012 Hardware Description BTS3012 Product Description BTS3012AE Hardware Description BTS3012AE Product Description BTS3006C Hardware Description BTS3006C Product Description
1-4
Issue 02 (2008-06-30)
2 Channel Management
2
About This Chapter
Channel Management
2.1 Overview This describes the significance of channel management in radio networks. A reasonable channel management guarantees not only the service of one user but also the performance of the entire network. 2.2 Availability This lists the NEs and software required for the implementation of channel management. 2.3 Technical Description This describes the management of different radio channel types in the GSM/GPRS. The channel management covers all the phases associated with a radio channel, such as establishment, maintenance, adjustment, and release. 2.4 Implementation This describes how to configure channel assignment algorithm parameters and call control parameters. 2.5 Maintenance Information This lists the counters related to channel management. 2.6 References
Issue 02 (2008-06-30)
2-1
2.1 Overview
This describes the significance of channel management in radio networks. A reasonable channel management guarantees not only the service of one user but also the performance of the entire network.
Definition
Channel management covers all the phases associated with a radio channel, such as establishment, maintenance, adjustment, and release. Radio channel management takes into account the following factors: channel interference, channel configuration, history record, traffic distribution, transmit power of the MS, and the priority of the TRX. The most appropriate radio channel is assigned on the basis of a specific calling event and environment. The channels to be managed consist of the SDCCH, TCH, and PDCH. The TCH and SDCCH are assigned by priority. That is, the system assigns a channel with highest priority based on the usage of the resources, and then adjusts or converts the channel based on the actual situation.
Purposes
Radio channel management achieves the management of different types of radio channels. An appropriate channel is assigned to the radio service based on HWII channel allocation algorithm and the consideration of different factors. At the same time, channels are adjusted properly. Radio channel management not only ensures the services for one user, but also ensures the performance counters in the entire network. The TCH/F or TCH/H can be flexibly assigned on the basis of the service requirement and the loading conditions in the cell. This not only meets the communication requirements of the subscribers but also utilizes the radio channel bandwidth to full extent. The flexible adjustment of TCH/Fs and TCH/Hs can meet the balance between network quantity and network capacity.
NOTE
For details on the adjustment of the TCH/Fs and TCH/Hs, refer to 12 Half-Rate Service. For details on the adjustment of the SDCCH, refer to 34 SDCCH Dynamic Adjustment.
Terms
Term couple channel HWII Channel Allocation Algorithm MA Definition The channel comprising two half-rate sub-timeslots is called a couple channel when both sub-timeslots are idle. In HWI channel allocation algorithm, the channels are assigned by sequence; in HWII channel allocation algorithm, the channels are assigned by priority. It indicates the carrier frequencies within a cell that are involved in frequency hopping.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
2-2
Term single channel
Definition A timeslot comprises two half-rate sub-timeslots. When one sub-timeslot is occupied and the other sub-timeslot is idle, the idle sub-timeslot is called the single channel. Enhanced Multi-Level Precedence and Preemption service
eMLPP
Acronyms and Abbreviations

Acronyms and Abbreviations AMR BCCH DTX eMLPP GPRS MA Full Spelling Adaptive Multi Rate Broadcast Control Channel Discontinuous Transmission (mechanism) enhanced Multi-Level Precedence and Pre-emption service General Packet Radio Service Mobile Allocation
2.2 Availability
This lists the NEs and software required for the implementation of channel management.
NEs Involved
Table 2-1 describes the NEs involved in channel management. Table 2-1 NEs involved in channel management MS NOTE
l -: not involved l : involved
BTS
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 2-2 lists the versions of GBSS products that support channel management.
Issue 02 (2008-06-30)
2-3
Table 2-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM BTS3X BTS3002C BTS3001C Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases G3BTS32.30000.01.1130 and later releases G3BTS36.30000.02.0820 and later releases G3BTS34.30000.07.0301 and later releases
Miscellaneous
None
2.3 Technical Description

This describes the management of different radio channel types in the GSM/GPRS. The channel management covers all the phases associated with a radio channel, such as establishment, maintenance, adjustment, and release. 2.3.1 Channel Assignment Procedure This describes the channel assignment procedure. When a type of service requires the occupation of the SDCCH or TCH, the channel assignment procedure is triggered. 2.3.2 Pre-Processing of Channel Assignment This describes the pre-processing of channel assignment. The information received from preprocessing, such as the channel request cause and channel type, is used as the input for the channel assignment algorithm. 2.3.3 Channel Assignment Algorithms This describes channel assignment algorithms. Channel assignment algorithms consist of the channel rate assignment strategies and the HWII channel allocation algorithm. 2.3.4 Processing After Channel Assignment This describes the postprocessing after the allocation of an optimal channel or candidate channel fails.
2-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd Issue 02 (2008-06-30)
2.3.1 Channel Assignment Procedure

This describes the channel assignment procedure. When a type of service requires the occupation of the SDCCH or TCH, the channel assignment procedure is triggered. HWII channel allocation algorithm is adopted for the selection of a most appropriate channel, which is labeled with a priority level. The calling events and environment, such as intra-cell handover, concentric cell handover, frequency bands, data rate, channel interference, channel priority, channel occupation record, and traffic load of the TRXs, should be taken into account. Channel assignment has a flexible radio channel conversion mechanism and implements the following dynamic channel conversions according to the user policy:
l l l
Dynamic conversion between the TCH/F and the TCH/H Dynamic conversion between the TCH/F or TCH/H and the PDCH Dynamic conversion between the TCH/F and the SDCCH
HWII channel allocation algorithm features load-sharing, enabling the channels to be meanly allocated on the TRXs, timeslots, and sub-timeslots. This not only reduces the co-channel and adjacent channel interference but also avoids the risk of carrying calls on certain TRXs. Figure 2-1 shows the channel assignment procedure. Figure 2-1 Channel assignment procedure
Immediate assignment request
Assignment request
Handover command
Pre-processing of channel assignment
HWII channel allocation algorithm
Is channel assignment successful? No Processing after channel assignment
Yes
End
Issue 02 (2008-06-30)
2-5
The channel assignment procedure is as follows: 1. Assign channels. The SDCCH assignment procedure consists of immediate assignment SDCCH procedure, intra-cell handover, intra-BSC handover, and incoming BSC handover. The TCH assignment procedure consists of immediate assignment TCH procedure, intracell handover, intra-BSC handover, and incoming BSC handover. The following describes the channel assignment procedures.
l
Immediate assignment procedure In a service procedure such as MS-originated call, MS-terminated call, or location update when a channel request message from the MS is received, the BSC initiates the SDCCH assignment procedure (early assignment or late assignment) or TCH assignment procedure (very early assignment).
TCH assignment procedure In an MS-originated or MS-terminated call procedure when the assignment request message from the MSC is received, the TCH assignment procedure is triggered.
Intra-cell handover procedure When the target cell receives an incoming cell handover request from the source cell, the procedure for assigning the SDCCH (SDCCH handover) or TCH (TCH handover) is triggered.
Intra-BSC handover procedure When the target cell receives an incoming cell handover request from the source cell, the procedure for assigning the SDCCH (SDCCH handover) or TCH (TCH handover) is triggered.
Incoming BSC handover procedure When an incoming BSC handover request is received, the procedure for assigning the SDCCH (SDCCH handover) or TCH (TCH handover) is triggered.
2.
After the channel assignment procedure is triggered, the BSC collects information for subsequent channel assignments. This process is called pre-processing of channel assignment. After the pre-processing of channel assignment, the BSC assigns an appropriate channel for this channel request based on the channel assignment algorithm configured for the cell where an MS is located. The channel assignment algorithm is called HWII channel allocation algorithm. After channels are assigned by the BSC based on the channel assignment algorithm, the following two situations may occur:
l l
3.
4.
An appropriate channel is assigned. No appropriate channel is assigned due to reasons such as congestion.
5.
If there is no appropriate channel to be assigned, the BSC will attempt the operations associated with channel assignment, such as queuing and preemption.
2.3.2 Pre-Processing of Channel Assignment

This describes the pre-processing of channel assignment. The information received from preprocessing, such as the channel request cause and channel type, is used as the input for the channel assignment algorithm.
Pre-Processing of Channel Assignment in an Immediate Assignment Procedure

After receiving an immediate channel assignment request, the BSC the BSC obtains the information such as the cause for the channel request, the type of the required channel, and the concentric attributes of the cell where the MS is located. When all the SDCCHs in the cell are busy and the TCH Immediate Assignment of the cell is set to Yes, the BSC assigns the TCH to the immediate channel assignment request. In addition, the BSC takes statistics about the performance counters based on the requirements for the channel rate. If the cell where the MS is located is a concentric cell, the BSC takes statistics about the performance counters based on the concentric cell attributes of the requested channel.
Pre-Processing of Channel Assignment in an Assignment Procedure

After receiving an assignment request message from the MSC, the BSC performs the following operations: 1. 2. 3. Interpret the assignment request message to obtain the type of the assigned channels, the type of rate, and the information on the allowed speech versions. Take statistics about the performance counters for the assignments in different rates and for different access reasons. Based on the channel type and the service type in a channel assignment and an assignment request, check whether the subsequent assignment procedure is normal assignment, mode modification, or direct retry and whether all the aspects are consistent. Then, take statistics about the performance counters.
Pre-Processing of Channel Assignment in a Handover Procedure

After the related module of the BSC receives a handover request, the BSC performs the following operations: 1. 2. Take statistics about the related performance counters in the handover request. Interpret the channel request (caused by the handover) message to obtain the requested channel type, handover reasons, and the information on the priority, on interference bands, on MS receive level, on punished TRX channel, on the MS mode, and on the support capability of frequency bands, and on whether AMR is supported.
2.3.3 Channel Assignment Algorithms

This describes channel assignment algorithms. Channel assignment algorithms consist of the channel rate assignment strategies and the HWII channel allocation algorithm.
Channel Rate Assignment Strategies

The following lists the two channel rate assignment strategies available at present:
l
Channel rate assignment strategy controlled by the MSC If TCH Rate Modify is set to No, the BSC adopts the channel rate assignment strategy controlled by the MSC.
Channel rate assignment strategy controlled by the BSC If TCH Rate Modify is set to Yes, the BSC adopts the channel rate assignment strategy controlled by the BSC.
By default, the channel rate assignment strategy controlled by the BSC is used.
Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 2-7
The channel rate assignment strategy controlled by the MSC is described as follows:
l
If the type of the assigned channel required by the MSC is TCH/F only or TCH/H only, only the channel that meets the channel rate requirement can be assigned. If the type of the assigned channel required by the MSC is TCH/F preferable and other conditions are met, the TCH/Fs are assigned when TCH/Fs are available in a cell. If the type of the assigned channel required by the MSC is TCH/H preferable and other conditions are met, the TCH/Hs are assigned when TCH/Hs are available in a cell.
NOTE
If channels are assigned on the basis of the assignment rate of the MSC, the network capacity and the MS speech quality are difficult to be optimal. To assign channels based on the MSC assignment, the channel rate assignment strategy controlled by the MSC is generally used for an interconnection test on the A interface.
The channel rate assignment strategy controlled by the BSC is the optimized channel rate assignment strategy controlled by the MSC. It is described as follows:
l
If the type of the assigned channel required by the MSC is TCH/F only or TCH/H only, only the channel that meets the channel rate requirement can be assigned. If the type of the assigned channel required by the MSC is TCH/F preferable or TCH/H preferable, the TCH/Fs are assigned preferably to ensure the voice quality when there are many idle TCH/Fs. If there are only a few idle TCH/Fs, the TCH/Hs are assigned preferably to ensure the network capacity.
HWII Channel Allocation Algorithm

HWII channel allocation algorithm is adopted for the selection of a most appropriate channel, which is labeled with a priority level. The queuing of the different factors has different impact on the comprehensive priority. The comprehensive priority of a channel can be calculated when different factors are taken into account. The channel allocation algorithm decides whether to assign a channel based on its comprehensive priority. If the priority value of a channel is larger, the priority of the channel is lower, and this channel is more difficult to be assigned. If the priority value is smaller, the priority of the channel is higher, and this channel is more likely to be assigned. The channel allocation priority consists of a 4-byte low priority, a 2-byte MAIO medium priority, and a 4-byte high priority. The weight of the three priorities is as follows: low priority < medium priority < high priority. HWII channel allocation algorithm categorizes the factors affecting channel assignment into the following types:
l l l l
Capacity Quality PS coordination Management
HWII channel allocation algorithm defines four different types of Channel Assignment Strategies. Based on the channel assignment strategies, the importance of each factor affecting channel assignment is listed as follows:
l
Capacity with a higher priority

2-8
Capacity > quality > PS coordination > management

l
Quality with a higher priority Quality > capacity > PS coordination > management PS coordination with a relatively higher priority Capacity > PS coordination > quality > management PS coordination with an absolutely higher priority PS coordination > capacity > quality > management
Where, A > B indicates that A has a greater weight than B during channel assignment.
2.3.4 Processing After Channel Assignment

This describes the postprocessing after the allocation of an optimal channel or candidate channel fails. The processing made after the channel allocation varies with the channel request phases.
l
In the immediate assignment phase, the postprocessing involves the dynamic adjustment between TCH and the SDCCH, and the dynamic adjustment between the TCH and the PDCH. In non-immediate assignment phases, the postprocessing involves the dynamic adjustment between the TCH and the SDCCH, the dynamic adjustment between the TCH and the PDCH, the channel preemption, and the channel queuing.
Channel Preemption
The BSC can allocate the channels based on their priorities. The MS with a high priority can preempt the channel of the MS with a low priority if the channel preemption indication allows. There are two situations associated with preemption when the system configuration differs.
l
Direct preemption In the same cell, the MS with high priority can preempt the channel of the MS with low priority. To do this, the system first initiates a channel release procedure to release the channel of the low-priority MS, and then assigns the channel to the high-priority MS. If the Allow eMLPP is set to No, direct preemption is performed.
eMLPP preemption Before the preemption of a high-priority MS over a low-priority MS is made, the system first attempts to hand over the low-priority MS to a neighbor cell and, if the handover fails, the system initiates the channel release procedure. If the Allow eMLPP is set to Yes, eMLPP preemption is performed.
Channel Queuing
The BSC channel assignment supports channel queuing. Channel queuing applies to continuous assignment and handover. The decision whether to allow queuing is made by the MSC in the assignment request or handover request. If no radio channels is available, the BSC arranges the channel requests in a queue. In this way, the BSC can assign TCHs for the MSs in queue within an acceptable period as soon as possible.
Issue 02 (2008-06-30)
2-9
2.4 Implementation
This describes how to configure channel assignment algorithm parameters and call control parameters. 2.4.1 Configuring Channel Assignment Algorithm Parameters This describes how to configure the channel assignment algorithm parameters on the BSC6000 Local Maintenance Terminal. 2.4.2 Configuring Call Control Parameters This describes how to configure call control parameters on the BSC6000 Local Maintenance Terminal. 2.4.3 Examples: Configuring Channel Management This describes how to configure channel management on the BSC6000 Local Maintenance Terminal.
2.4.1 Configuring Channel Assignment Algorithm Parameters

This describes how to configure the channel assignment algorithm parameters on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 Configure the channel rate assignment strategies. 1. On the BSC6000 Local Maintenance Terminal, right-click the root node on the Management Tree tab page and select Configure BSC Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 2-2.
2-10
Issue 02 (2008-06-30)
Figure 2-2 BSC attributes
2. 1. 2. 3.
Click the Software Parameters tab and set TCH Rate Modify. On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page and select Configure Cell Attributes from the shortcut menu. In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 2-3.
Step 2 Configure HWII channel allocation algorithm.
Issue 02 (2008-06-30)
2-11
Figure 2-3 Set Other Parameter dialog box
4.
Click Channel Management. A dialog box is displayed, as shown in Figure 2-4. Set Channel Assignment Strategies.
2-12
Issue 02 (2008-06-30)
Figure 2-4 Setting channel management parameters
5.
Click Advanced. A dialog box is displayed, as shown in Figure 2-5.
Issue 02 (2008-06-30)
2-13
Figure 2-5 Setting advanced channel management parameters
6.
Finish the parameter settings in Figure 2-5, and then click OK to return to the previous dialog box.
----End
2.4.2 Configuring Call Control Parameters

This describes how to configure call control parameters on the BSC6000 Local Maintenance Terminal.
Context
If the channel allocation fails, the operations such as direct retry, reassignment, and preemption should be performed. The relevant parameters are Allow Reassign and Allow eMLPP.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page and select Configure Cell Attributes from the shortcut menu. Step 2 In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. Step 3 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 2-6.
2-14
Issue 02 (2008-06-30)
Step 4 Click Call Control. A dialog box is displayed, as shown in Figure 2-7. Set Allow Reassign and Allow eMLPP.
Issue 02 (2008-06-30)
2-15
Figure 2-7 Setting call control parameters
Step 5 Click OK to return to the previous dialog box for parameter modification until the modification is complete. ----End
2.4.3 Examples: Configuring Channel Management

This describes how to configure channel management on the BSC6000 Local Maintenance Terminal.
Context
This example describes how to enable Allocation TRX Priority Allowed and how to adjust the configuration of TRX Priority. Take cell 2F_BTS30 and TRX1 as examples. Allocation TRX Priority Allowed is set to Yes and TRX Priority is set toLevel1.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click 2F_BTS30 on the Management Tree tab page and select Configure Cell Attributes from the shortcut menu.
Step 2 In the displayed dialog box, double-click 2F_BTS30 in the Cell view list box to add it to the Selected cells list box. Step 3 Click Next. A dialog box is displayed. Step 4 In the Cells to be set list box, select 2F_BTS30, and then click Set Cell Properties. A dialog box is displayed. Step 5 Click Channel Management. The Set Channel Parameter dialog box is displayed. Step 6 Click Advanced. The HWII Channel Assignment and Radio Channel Control tab page is displayed. Step 7 Set Allocation TRX Priority Allowed to Yes, as shown in Figure 2-8. Figure 2-8 Setting Allocation TRX Priority Allowed dialog box
Step 8 Click OK to complete the settings of Allocation TRX Priority Allowed. Step 9 Select 2F_BTS30 on the Management Tree tab page. Right-click TRX1, and then select Configure TRX Attributes from the shortcut menu. Step 10 In the displayed dialog box, click Set TRX Attributes. Step 11 In the displayed dialog box, click Device Attributes. Step 12 Set the TRX Priority to Level1, as shown in Figure 2-9.
Issue 02 (2008-06-30)
2-17
Figure 2-9 Configure TRX Attributes-TRX1 dialog box
Step 13 Click OK to return to the previous dialog box to continue modifying TRX Priority until the modification is complete. ----End
2.5 Maintenance Information

This lists the counters related to channel management.
Alarms
None.
Counters
Table 2-3, Table 2-4, Table 2-5, Table 2-6, Table 2-7, Table 2-8, and Table 2-9 list the counters related to channel management. Table 2-3 Counters related to channel management Counter CA310 CA311 R4419B
2-18
Description Assignment Requests Assignment Commands Measurement of Completed Assignments

Counter A3127A CA314 A3157A
Description Assignment Failure Measurement Mode Modify Commands Measurement of Failed Mode Modify Attempts
Table 2-4 Interference band measurement per TRX Counter S4210A S4219A S4210B S4219B AS4200A AS4200B AS4200C AS4200D AS4200E AS4207A AS4207B AS4207C AS4207D AS4207E AS4208A AS4208B AS4208C AS4208D AS4208E Description Uplink Interference Indication Messages (SDCCH) Uplink Interference Indication Messages (TCH) Downlink Interference Indication Messages (SDCCH) Downlink Interference Indication Messages (TCH) Mean Number of SDCCHs in Interference Band 1 Mean Number of SDCCHs in Interference Band 2 Mean Number of SDCCHs in Interference Band 3 Mean Number of SDCCHs in Interference Band 4 Mean Number of SDCCHs in Interference Band 5 Mean Number of TCHFs in Interference Band 1 Mean Number of TCHFs in Interference Band 2 Mean Number of TCHFs in Interference Band 3 Mean Number of TCHFs in Interference Band 4 Mean Number of TCHFs in Interference Band 5 Mean Number of TCHHs in Interference Band 1 Mean Number of TCHHs in Interference Band 2 Mean Number of TCHHs in Interference Band 3 Mean Number of TCHHs in Interference Band 4 Mean Number of TCHHs in Interference Band 5
Issue 02 (2008-06-30)
2-19
Table 2-5 Channel assignment request measurement per cell Counter R3100A R3107B R3100C R3100D R3100E Description Channel Assignment Requests in Immediate Assignment Procedure (SDCCH) Channel Assignment Requests in Assignment Procedure (TCHF) Channel Assignment Requests in Internal IntraCell Handover Procedure (SDCCH) Channel Assignment Requests in Incoming Internal Cell Handover Procedure (SDCCH) Channel Assignment Requests in Incoming External Inter-Cell Handover Procedure (SDCCH) Channel Assignment Requests (SDCCH) Channel Assignment Requests (TCHF) Channel Assignment Requests (TCHH) Channel Assignment Requests (TCH)
CR3100 CR3107 CR3108 CR3109
Table 2-6 Channel assignment success measurement per TRX Counter R4110A R4117A R4118A R4117B R4118B R4110C R4117C R4118C Description Successful Channel Assignments in Immediate Assignment Procedure (SDCCH) Successful Channel Assignments in Immediate Assignment Procedure (TCHF) Successful Channel Assignments in Immediate Assignment Procedure (TCHH) Successful Channel Assignments in Immediate Assignment Procedure (TCHF) Successful Channel Assignments in Immediate Assignment Procedure (TCHH) Successful Channel Assignments in Internal IntraCell Handover Procedure (SDCCH) Successful Channel Assignments in Internal IntraCell Handover Procedure (TCHF) Successful Channel Assignments in Internal IntraCell Handover Procedure (TCHH)
2-20
Issue 02 (2008-06-30)
Counter R4110D R4117D R4118D R4110E
Description Successful Channel Assignments in Incoming Internal Cell Handover Procedure (SDCCH) Successful Channel Assignments in Incoming Internal Cell Handover Procedure (TCHF) Successful Channel Assignments in Incoming Internal Cell Handover Procedure (TCHH) Successful Channel Assignments in Incoming External Inter-Cell Handover Procedure (SDCCH) Successful Channel Assignments in Incoming External Inter-Cell Handover Procedure (TCHF) Successful Channel Assignments in Incoming External Inter-Cell Handover Procedure (TCHH) Successful Channel Assignments in Immediate Assignment Procedure (SDCCH) Successful Channel Assignments in Immediate Assignment Procedure (TCHF) Successful Channel Assignments in Immediate Assignment Procedure (TCHH) Successful Channel Assignments in Immediate Assignment Procedure (TCHF) Successful Channel Assignments in Immediate Assignment Procedure (TCHH) Successful Channel Assignments in Internal IntraCell Handover Procedure (SDCCH) Successful Channel Assignments in Internal IntraCell Handover Procedure (TCHF) Successful Channel Assignments in Internal IntraCell Handover Procedure (TCHH) Successful Channel Assignments in Incoming Internal Cell Handover Procedure (SDCCH) Successful Channel Assignments in Incoming Internal Cell Handover Procedure (TCHF) Successful Channel Assignments in Incoming Internal Cell Handover Procedure (TCHH) Successful Channel Assignments in Incoming External Inter-Cell Handover Procedure (SDCCH)
R4117E R4118E R4110A R4117A R4118A R4117B R4118B R4110C R4117C R4118C R4110D R4117D R4118D R4110E
Issue 02 (2008-06-30)
2-21
Counter R4117E R4118E CR4110 CR4117 CR4118 CR4119
Description Successful Channel Assignments in Incoming External Inter-Cell Handover Procedure (TCHF) Successful Channel Assignments in Incoming External Inter-Cell Handover Procedure (TCHH) Successful Channel Assignments (SDCCH) Successful Channel Assignments (TCHF) Successful Channel Assignments (TCHH) Successful Channel Assignments (TCH)
Table 2-7 Channel assignment failure measurement per cell Counter R3120A Description Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Immediate Assignment Procedure (SDCCH) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Immediate Assignment Procedure (TCHF) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Immediate Assignment Procedure (TCHH) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Assignment Procedure (TCHF) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Assignment Procedure (TCHH) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Internal Intra-Cell Handover Procedure (SDCCH) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Internal Intra-Cell Handover Procedure (TCHF) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Internal Intra-Cell Handover Procedure (TCHH) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Incoming Internal Inter-Cell Handover Procedure (SDCCH)
R3127A
R3128A
R3127B
R3128B
R3120C
R3127C
R3128C
R3120D
2-22
Counter R3127D
Description Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Incoming Internal Inter-Cell Handover Procedure (TCHF) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Incoming Internal Inter-Cell Handover Procedure (TCHH) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Incoming external Inter-Cell Handover Procedure (SDCCH) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Incoming external Inter-Cell Handover Procedure (TCHF) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) in Incoming external Inter-Cell Handover Procedure (TCHH) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) (SDCCH) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) (TCHF) Channel Assignment Failures (All Channels Busy or Channels Unconfigured) (TCHH)
R3128D
R3120E
R3127E
R3128E
CR3120 CR3127 CR3128
Table 2-8 Channel assignment concentric cell measurement per cell Counter R3200 R3201 R3202 R3203 R3202B R3203B Description Channel Assignment Requests (Underlaid Subcell Only) Channel Assignment Requests (Overlaid Subcell Only) Channel Assignment Requests (Underlaid Subcell Preferred) Channel Assignment Requests (Overlaid Subcell Preferred) TCH Assignment Requests (Underlaid Subcell Preferred) TCH Assignment Requests (Overlaid Subcell Preferred)
Issue 02 (2008-06-30)
2-23
Counter R3202D
Description Channel Assignment Requests in Incoming Internal Inter-Cell Handover Procedure (TCH) (Underlaid Subcell Preferred) Channel Assignment Requests in Incoming Internal Inter-Cell Handover Procedure (TCH) (Overlaid Subcell Preferred) Channel Assignment Requests in Incoming External Inter-Cell Handover Procedure (TCH) (Underlaid Subcell Preferred) Channel Assignment Requests in Incoming External Inter-Cell Handover Procedure (TCH) (Overlaid Subcell Preferred) Channel Assignment Overflows (TCH) (Underlaid Subcell Preferred) Channel Assignment Overflows (TCH) (Overlaid Subcell Preferred) Channel Assignment Overflows in Incoming Internal Inter-Cell Handover Procedure (TCH) (Underlaid Subcell Preferred) Channel Assignment Overflows in Incoming Internal Inter-Cell Handover Procedure (TCH) (Overlaid Subcell Preferred) Channel Assignment Overflows in Incoming External Inter-Cell Handover Procedure (TCH) (Underlaid Subcell Preferred) Channel Assignment Overflows in Incoming External Inter-Cell Handover Procedure (TCH) (Overlaid Subcell Preferred) Channel Assignment Overflows in Underlaid Subcell (SDCCH) Channel Assignment Overflows in Overlaid Subcell (SDCCH) Channel Assignment Overflows in Underlaid Subcell (TCHF) Channel Assignment Overflows in Overlaid Subcell (TCHF) Channel Assignment Overflows in Underlaid Subcell (TCHH) Channel Assignment Overflows in Overlaid Subcell (TCHH)
R3203D
R3202E
R3203E
R3222B R3223B R3222D
R3223D
R3222E
R3223E
R3225G R3224G R3225H R3224H R3225I R3224I
2-24
Issue 02 (2008-06-30)
Counter R3225J R3224J R3224K
Description Channel Assignment Overflows in Underlaid Subcell (TCH) Channel Assignment Overflows in Overlaid Subcell (TCH) Failed Handovers from Underlaid Subcell to Overlaid Subcell due to Busy Channels in Overlaid Subcell Failed Handovers from Overlaid Subcell to Underlaid Subcell due to Busy Channels in Underlaid Subcell
R3225K
Table 2-9 Channel assignment queue measurement per cell Counter R3130 R3134 R3135 R3136 R3137 R3138 AR3131 AR3133 CR313C Description Maximum Queue Length Failed Queuing Attempts due to Queue Overflow Queuing Requests Failed Queuings (Preemption) Failed Queuings (Queuing Timer Expired) Failed Queuings (Dynamic Adjustment Timed Out) Mean Queue Length Mean Queuing Duration Failed Queuing Attempts
2.6 References
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".
Issue 02 (2008-06-30)
2-25
l
GSM 08.06: "Digital cellular telecommunications system (Phase 2+); Signaling transport mechanism specification for the Base Station System Mobile services Switching Center (BSS MSC) interface". GSM 08.08: "Digital cellular telecommunications system (Phase 2+); Mobile services Switching Center 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 (Phase2+); Base Station Controller Base Transceiver Station (BSC BTS) interface; Interface principles". GSM 08.56: "Digital cellular telecommunications system (Phase2+); Base Station Controller Base Transceiver Station (BSC BTS) interface; Layer 2 specification". GSM 08.58: "Digital cellular telecommunications system (Phase2+);Base Station Controller Base Transceiver Station (BSC BTS) interface; Layer 3 specification.
2-26
Issue 02 (2008-06-30)
3 Combined BTS Cabinets
3
About This Chapter
Combined BTS Cabinets
3.1 Overview This describes the combined BTS cabinets. In combined BTS cabinets, multiple BTSs of the same type are combined to serve as one BTS to expand capacity. 3.2 Availability This lists the NEs and software required for the implementation of combined BTS cabinets. 3.3 Technical Description This describes the technical aspects of combined BTS cabinets. Multiple BTS cabinets of the same type are connected through the signal cables for combined cabinets to serve as one BTS. Multiple compatible BTS cabinets are connected through the signal cables for cabinet groups to serve as one BTS. 3.4 Capabilities This describes the number of TRXs and cabinets that are supported by combined cabinets and cabinet groups. 3.5 Implementation This describes how to install the hardware of combined BTS cabinets and configure the parameters of BTS combined cabinets. 3.6 Maintenance Information This lists the alarms and counters related to combined BTS cabinets. 3.7 References None.
Issue 02 (2008-06-30)
3-1
3.1 Overview
This describes the combined BTS cabinets. In combined BTS cabinets, multiple BTSs of the same type are combined to serve as one BTS to expand capacity.
Definition
The combined BTS cabinets refer to the function where multiple BTS cabinets of the same type are connected through the signal cables for combined cabinets to serve as one BTS. The BTS cabinet groups refer to the function where multiple compatible BTS cabinets are connected through the signal cables for cabinet groups to serve as one BTS.
NOTE
The TRX mutual aid and the idle timeslot assignment cannot be performed across cabinet groups.
Purposes
A single cabinet has a limited capacity. For example, one BTS3012 cabinet holds a maximum of 12 TRXs (not configured with QTRUs), and one BTS3006C cabinet holds a maximum of 6 TRXs. The area with high traffic volumes requires a large capacity BTS. If one BTS cannot meet the capacity requirements, combined cabinets or cabinet groups should be used to expand capacity. For example, the combination of two BTS3012 cabinets forms one cabinet group and supports 24 TRXs. Three cabinet groups support 72 TRXs.
Terms
Terms Combined cabinets Main cabinet Extension cabinet Cabinet group Main cabinet group Extension cabinet group Combined group Definition Two or multiple BTS cabinets of the same type are combined to serve as one BTS. The main cabinet in combined cabinets is configured with the main control board. The extension cabinet in combined cabinets is the cabinet except for the main cabinet in the combined cabinets. Two or multiple BTS combined cabinets are grouped to serve as one BTS. The main cabinet group provides the clock source for the BTS. The extension cabinet group is the cabinet group except for the main cabinet group. Different types of BTS cabinets form a combined group.
3-2
Issue 02 (2008-06-30)

None.
3.2 Availability
This lists the NEs and software required for the implementation of combined BTS cabinets.
NEs Involved
Table 3-1 lists the NEs involved in combined BTS cabinets. Table 3-1 NEs involved in combined BTS cabinets MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 3-2 describes the versions of GBSS products that support combined BTS cabinets. Table 3-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012A E BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM DTRU QTRU Version V900R008C01 and later releases BTS3000V100R001C02 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases Not supported Not supported Not supported
Issue 02 (2008-06-30)
3-3

NOTE
l l l
The DBS3900 GSM, BTS3900 GSM, and BTS3900A GSM are distributed base stations. They support 72 TRXs, and thus combined BTS cabinets or BTS cabinet groups are not required. All the double-transceiver BTSs support combined BTS cabinets and BTS cabinet groups. This document takes the BTS3012 and the BTS3006C in TDM transmission mode as an example. A single BTS3012 cabinet without QTRUs supports a maximum of 12 TRXs. If all the TRX boards in a single BTS3012 cabinet are QTRUs, the cabinet supports a maximum of 36 TRXs. This document takes the BTS3012 cabinet without QTRUs as an example.
Miscellaneous
l l
Only the BTS3012 and BTS3012AE support the IP transmission mode. Only the BTS3012, BT3012AE, BTS3006C, and BTS3002E support Abis transmission optimization. Only the BTS3012 and BTS3012AE support HubBTS.

This describes the technical aspects of combined BTS cabinets. Multiple BTS cabinets of the same type are connected through the signal cables for combined cabinets to serve as one BTS. Multiple compatible BTS cabinets are connected through the signal cables for cabinet groups to serve as one BTS. 3.3.1 Combined Cabinets and Cabinet Groups of the BTS3012 This describes the combined cabinets and cabinet groups of the BTS3012. One BTS3012 cabinet can hold a maximum of 12 TRXs (not configured with QTRUs). If a synchronous cell has more than 12 TRXs, combined cabinets should be used. The BTS3012 supports up to 2 combined cabinets and 3 cabinet groups. Through the combined cabinets and cabinet groups of the BTS3012, a maximum of 72 TRXs are supported. 3.3.2 Combined Cabinets and Cabinet Groups of the BTS3006C This describes the combined cabinets and cabinet groups of the BTS3006C. A BTS3006C cabinet can hold a maximum of six TRXs. If a synchronous cell has more than six TRXs, combined cabinets should be used. The BTS3006C supports up to 3 combined cabinets and 2 cabinet groups. It supports a maximum of six cabinets and therefore 36 TRXs. 3.3.3 Hybrid Cabinet Groups of the BTS3012 and the BTS3X This describes the hybrid cabinet groups between the BTS3012 and the BTS30 or between the BTS3012 and the BTS312.
3.3.1 Combined Cabinets and Cabinet Groups of the BTS3012

This describes the combined cabinets and cabinet groups of the BTS3012. One BTS3012 cabinet can hold a maximum of 12 TRXs (not configured with QTRUs). If a synchronous cell has more than 12 TRXs, combined cabinets should be used. The BTS3012 supports up to 2 combined cabinets and 3 cabinet groups. Through the combined cabinets and cabinet groups of the BTS3012, a maximum of 72 TRXs are supported.
3-4
Issue 02 (2008-06-30)

NOTE
If the BTS3012 configured with QTRUs is used for combined cabinets, the number of TRXs in a single cabinet should not exceed 24. In this situation, the implementation of combined cabinets and cabinet groups is similar to that for the BTS3012 configured with DTRUs. The BTS3012AE does not support combined cabinets. The implementation of cabinet groups for the BTS3012AE is similar to that for the BTS3012. For the Abis transmission optimization BTS, the implementation of combined cabinets and cabinet groups is the same as that in TDM scheme. For HubBTS, the implementation of combined cabinets is the same as that in TDM scheme. In terms of cabinet groups, the extension cabinet group is connected to the DPTU in the main cabinet of the main cabinet group through E1 cables. Then, the DPTU is connected to the BSC through E1 cables. Compared with the implementation of combined cabinets and cabinet groups in TDM scheme, that for the IP transmission BTS has the following differences:
l l l
l l l
No site chains are required between the BTS and the BSC. The cabinets in a cabinet group are connected with E1 cables. The extension cabinet group is connected to the DPTU in the main cabinet of the main cabinet group through E1 cables. Then, the FE port on the DPTU is connected to the BSC through Ethernet cables.
Implementation of Combined Cabinets

Figure 3-1 shows the connections of combined cabinets. Figure 3-1 Connections of combined cabinets
Signal cable for combined cabinets
Main cabinet
Extension cabinet
In the BTS3012 combined cabinets, only the main cabinet is configured with the DTMU. When configuring the BTS combined cabinets, adhere to the following principles:
l
Least antennas The number of antennas should be as few as possible. Least cabinets The number of cabinets should be as few as possible. Complete synchronous cell All the TRXs of one synchronous directional cell should be configured in one cabinet.
Implementation of Cabinet Groups

Figure 3-2 shows the connections of BTS3012 cabinet groups.
Issue 02 (2008-06-30)
3-5
Figure 3-2 Connections of cabinet groups

Signal cables for cabinet groups
Main cabinet
Extension cabinet
Main cabinet
Extension cabinet
Main cabinet
Extension cabinet
Extension cabinet group 1
Main cabinet group
NOTE
As shown in Figure 3-2, the signal cables for combined cabinets are used to transmit control signals, data signals, and clock signals between the main cabinet and the extension cabinet. The signal cables for cabinet groups are used to transmit the control signals and clock signals between the main cabinet group and the extension cabinet group.
3.3.2 Combined Cabinets and Cabinet Groups of the BTS3006C

This describes the combined cabinets and cabinet groups of the BTS3006C. A BTS3006C cabinet can hold a maximum of six TRXs. If a synchronous cell has more than six TRXs, combined cabinets should be used. The BTS3006C supports up to 3 combined cabinets and 2 cabinet groups. It supports a maximum of six cabinets and therefore 36 TRXs.
NOTE
The hardware 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 main cabinet is differentiated from the extension cabinet by the settings of the DIP switches. The combined cabinets and cabinet groups of the BTS3002E are similar to those of the BTS3006C. For the Abis transmission optimization BTS, the implementation of combined cabinets and cabinet groups is the same as that in TDM scheme.
l l
Implementation of Combined Cabinets

The DMCM in the BTS3006C cabinet has two SFP optical ports: SFP-A and SFP-B. These two ports are used to connect combined cabinets and cabinet groups. They can be used without differentiation. For example, if the SFP-A port is connected to cabinet A in combined cabinets or in a cabinet group, the SFP-B port can be connected to cabinet B in the same combined cabinets or in the same cabinet group. Alternatively, if the SFP-B port is connected to cabinet A in combined cabinets or in a cabinet group, the SFP-A port can be connected to cabinet B in the same combined cabinets or in the same cabinet group. When configuring the BTS combined cabinets, adhere to the following principles:
l
Least antennas The number of antennas should be as few as possible. Least cabinets The number of cabinets should be as few as possible. Complete synchronous cell
3-6
All the TRXs of one synchronous directional cell should be configured in one cabinet.
Implementation of Cabinet Groups

The BTS3006C supports up to 3 combined cabinets and 2 cabinet groups, a maximum of six cabinets, and 36 TRXs, as shown in Figure 3-3. Figure 3-3 Connections of combined cabinets and cabinet groups
Cabinet 0 Cabinet 1 Cabinet 2
Cabinet 3
Cabinet 4
Cabinet 5
Three combined cabinets and two cabinet groups
The combined cabinets and cabinet groups in chain topology and in ring topology are as follows:
l
Combined cabinets in chain topology Cabinet 0 is connected to cabinet 1 through an optical cable. The optical cable can be connected to the SFP-A optical port or SFP-B optical port. As one SFP optical port of cabinet 1 is connected to cabinet 0, the other SFP optical port of cabinet 1 is connected to any SFP optical port of cabinet 2. as shown in Figure 3-4. Figure 3-4 Connections of combined cabinets in chain topology
Cabinet 0 S F P S F P S F P Cabinet 1 S F P S F P Cabinet 2 S F P S F P Cabinet 3 S F P
Combined cabinets in ring topology Dual-ring backup technology is used for combined cabinets in ring topology. In ring topology, signals of combined cabinets are transmitted both on eastward ring and on westward ring By default, signals are transmitted through the eastward ring in the following sequence: cabinet 0, cabinet 1, cabinet 2, cabinet 3, cabinet 4, and cabinet 5. The eastward ring is marked by solid lines shown in Figure 3-5. When the transmission on the eastward ring is disrupted, the eastward ring is automatically switched to the westward ring and signals are transmitted on the westward ring, as marked by dotted lines shown in Figure 3-5. When the transmission on the westward ring is disrupted, the westward ring is automatically switched to the eastward ring if the eastward ring is restored. If the eastward ring is not restored, the ring topology is automatically switched over to the star topology. For combined cabinets, the ring topology is more reliable and robust than the chain topology or star topology.
Issue 02 (2008-06-30)
3-7
Figure 3-5 Connections of combined cabinets in ring topology

Cabinet 0 S F P S F P S F P Cabinet 1 S F P S F P Cabinet 2 Cabinet 2 S F P S F P Cabinet 3 Cabinet 3 S F P
Cabinet 5 S F P S F P S F P
Cabinet 4 S F P
3.3.3 Hybrid Cabinet Groups of the BTS3012 and the BTS3X

This describes the hybrid cabinet groups between the BTS3012 and the BTS30 or between the BTS3012 and the BTS312. The hybrid cabinet groups have the following functions and restrictions:
l
The cabinets in the hybrid cabinet groups can be the BTS3012 cabinet and BTS30 cabinet, or can be the BTS3012 cabinet and BTS312 cabinet. The BTS3012 can form hybrid cabinet groups with the BTS of another type and cannot be combined with the BTS of another type. 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. That is, hybrid cabinet groups can have at most two types of cabinets. In a hybrid cabinet group, the BTS30 or BTS312 can be configured with all types of boards except the ABB bypass board. All the alarms generated by the BTS30 and BTS312 can be reported properly. The software of the boards in the BTS30 and BTS312 can be loaded and activated through the BTS3012. The BTS3012 supports the 32 kbit/s timeslot assignment of the BTS30 and BTS312. The DTMUs and TRXs in the BTS30 or BTS312 cabinet should be of G3BTS32V302R006C01 or later releases that support the 32 kbit/s timeslot assignment. The EAC module can be configured in the BTS30 or BTS312 cabinet in the extension cabinet group. That is, the original environment alarm system can be used. The software version of the DTMU in the BTS30 or BTS312, however, must be G3BTS32V302R006C01 or later releases to support the EAC. When the EAC module is configured in the main cabinet of an extension cabinet group, the DEMU and EAC-2 cannot be configured in the main cabinet of the extension cabinet group. The DTRUs and TRXs in different cabinet groups can be configured for one cell. After the BTS3012 cabinet forms hybrid cabinet groups with the BTS30 or BTS312, the type of the hybrid cabinet groups is BTS3012. Different types of BTSs can form combined groups and cannot form combined cabinets.
l l
l l
3-8
Issue 02 (2008-06-30)
CAUTION
When configuring hybrid cabinet groups of the BTS3012 and the BTS3X, you should ensure that the DTMU in the extension cabinet group is upgraded to the correct software version. At present, the BTS3012 does not support optical transmission.
3.4 Capabilities
This describes the number of TRXs and cabinets that are supported by combined cabinets and cabinet groups.
Combined Cabinets and Cabinet Groups of the BTS3012

One BTS3012 cabinet can hold up to 12 TRXs. The BTS3012 supports up to two combined cabinets and three cabinet groups. Through the combined cabinets and cabinet groups of the BTS3012, a maximum of 72 TRXs are supported.
Combined Cabinets and Cabinet Groups of the BTS3006C

One BTS3006C cabinet can hold up to six TRXs. The BTS3006C supports up to 3 combined cabinets and 2 cabinet groups, and therefore 36 TRXs.
Hybrid Cabinet Groups of the BTS3012 and the BTS3X

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. If the cabinets in the extension cabinet groups are the BTS30 cabinets, each extension cabinet group can be configured with three cabinets. If the cabinets in the extension cabinet groups are the BTS312 cabinets, each extension cabinet group can be configured with two cabinets.
3.5 Implementation
This describes how to install the hardware of combined BTS cabinets and configure the parameters of BTS combined cabinets. 3.5.1 Installing the Hardware of Combined BTS Cabinets This describes how to connect the main cabinet with the extension cabinet and connect the main cabinet group with the extension cabinet group. 3.5.2 Configuring Combined BTS Cabinets This describes how to configure the combined cabinets and cabinet groups of the BTS3012, the combined cabinets and cabinet groups of the BTS3006C, and the hybrid cabinet groups of the BTS3012 and the BTS3X on the BSC6000 Local Maintenance Terminal.
3.5.1 Installing the Hardware of Combined BTS Cabinets

This describes how to connect the main cabinet with the extension cabinet and connect the main cabinet group with the extension cabinet group.
Issue 02 (2008-06-30)
3-9
3.5.1.1 Connecting BTS3012 Combined Cabinets This describes how to connect the main cabinet with the extension cabinet through the signal cable for combined cabinets. 3.5.1.2 Connecting Two BTS3012 Cabinet Groups This describes how to connect the main cabinet group with the extension cabinet group through the signal cables for cabinet groups. 3.5.1.3 Connecting Three BTS3012 Cabinet Groups This describes how to connect the main cabinet group with two extension cabinet groups through the signal cables for cabinet groups. 3.5.1.4 Connecting Combined Cabinets and Cabinet Groups of the BTS3006C This describes how to configure the combined cabinets and cabinet groups of the BTS3006C through optical cables. 3.5.1.5 Connecting Hybrid Cabinet Groups of the BTS3012 and the BTS3X This describes how to connect the BTS3012 main cabinet group with two BTS30 or BTS312 extension cabinet groups through the signal cables for cabinet groups.
Connecting BTS3012 Combined Cabinets

This describes how to connect the main cabinet with the extension cabinet through the signal cable for combined cabinets.
Context
For the Abis transmission optimization BTS, HubBTS, and IP transmission BTS, the connection for combined cabinets is the same as that in TDM scheme.
Procedure
Step 1 Check that the cable connections in the main cabinet and in the extension cabinet are the same as those in a single cabinet that serves as a BTS. Step 2 Connect the cable for combined cabinets on the DCCU in the main cabinet to the CC_OUT port (output port of combined cabinets). Step 3 Connect the cable for combined cabinets on the DCCU in the extension cabinet to the CC_IN port (input port of combined cabinets). Step 4 Use the signal cable for combined cabinets to connect the DCF port on the DCSC on top of the main cabinet to the DCF port on the DCSC on top of the extension cabinet. The DCF port is the port for combined cabinets. Step 5 Connect the lightning protection failure alarm cable of the main cabinet to the S1+S1- port on the DSAC on top of the main cabinet. Step 6 Connect the lightning protection failure alarm cable of the extension cabinet to the S2+S2- port on the DSAC on top of the main cabinet. Step 7 Connect the main cabinet to the extension cabinet through the PGND cable to achieve an equipotential connection. Step 8 Set DIP switch SW8 on the DCSU in the main cabinet by referring to Table 3-3.
Table 3-3 Settings of SW8 on the DCSU in the main cabinet Cabinet Main cabinet SW8-4 ON SW8-3 ON SW8-2 ON SW8-1 ON
Step 9 Set the DIP switches on other boards by referring to Checking the DIP Switches of the BTS3012. ----End
Connecting Two BTS3012 Cabinet Groups

This describes how to connect the main cabinet group with the extension cabinet group through the signal cables for cabinet groups.
Context
For the Abis transmission optimization BTS, HubBTS, and IP transmission BTS, you need to connect the cables associated with the DPTU. Connect the transfer cable on the DCCU panel to an E1 port on the DPTU. The connections of other cables are the same as those in TDM scheme. Figure 3-6 shows the connections of two cabinet groups. Figure 3-6 Connections of two cabinet groups
Main cabinet
Extension cabinet
Main cabinet
Extension cabinet
Main cabinet group
Procedure
Step 1 Connect the cables for BTS3012 combined cabinets and set the DIP switches on the DTMU and DCSU in each group of combined cabinets by referring to 3.5.1.1 Connecting BTS3012 Combined Cabinets. Step 2 Use the signal cables for cabinet groups to connect the CKB1 port on the DCSC in the main cabinet of the main cabinet group to the CKB1 port on the DCSC in the main cabinet of the extension cabinet group. Step 3 Set DIP switches SW2, SW3, SW4, and SW5 on the DCMB in the main cabinet of each cabinet group to ON. Step 4 Set DIP switches SW2, SW3, SW4, and SW5 on the DCMB in the extension cabinet of each cabinet group to OFF.
Step 5 Set DIP switches SW1, SW8, and SW11 on the DCMBs in the main cabinet group and extension cabinet group by referring to Table 3-4, Table 3-5, and Table 3-6. Table 3-4 DIP switch SW1 on the DCMB in cabinet groups Cabinet Main cabinet in the main cabinet group Extension cabinet in the main cabinet group Main cabinet in the extension cabinet group Extension cabinet in the extension cabinet group SW1-4 ON SW1-3 ON SW1-2 ON SW1-1 ON
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
OFF
Table 3-5 DIP switch SW8 on the DCMB in cabinet groups Cabinet Main cabinet in the main cabinet group Main cabinet in the extension cabinet group SW8-4 ON SW8-3 ON SW8-2 ON SW8-1 ON
ON
ON
OFF
OFF
Table 3-6 DIP switch SW11 on the DCMB in cabinet groups Cabinet Main cabinet in the main cabinet group Extension cabinet in the main cabinet group
3-12
SW11-4 ON
SW11-3 ON
SW11-2 ON
SW11-1 ON
OFF
OFF
OFF
OFF
Issue 02 (2008-06-30)
Cabinet Main cabinet in the extension cabinet group Extension cabinet in the extension cabinet group
SW11-4 ON
SW11-3 ON
SW11-2 ON
SW11-1 ON
OFF
OFF
OFF
OFF
Step 6 Set the DIP switches on other boards by referring to Checking the DIP Switches of the BTS3012. Step 7 Connect the E1 cables of the extension cabinet group to idle E1 ports in the main cabinet group or to the idle ports on the GEIUB in the BSC. ----End
Connecting Three BTS3012 Cabinet Groups

This describes how to connect the main cabinet group with two extension cabinet groups through the signal cables for cabinet groups.
Context
For the Abis transmission optimization BTS, HubBTS, and IP transmission BTS, you need to connect the cables associated with the DPTU. Connect the transfer cable on the DCCU panel to an E1 port on the DPTU. The connections of other cables are the same as those in TDM scheme. Figure 3-7 shows the connections of three cabinet groups. Figure 3-7 Connections of three cabinet groups
Main cabinet
Extension cabinet
Main cabinet
Extension cabinet
Main cabinet
Extension cabinet
Main cabinet group
Issue 02 (2008-06-30)
3-13
Procedure
Step 1 Connect the cables for BTS3012 combined cabinets and set relevant items (except for the DIP switches on the DCSU) by referring to 3.5.1.1 Connecting BTS3012 Combined Cabinets. Step 2 Use the signal cable for cabinet groups to connect the CKB1 port on the DCSC in the main cabinet of the main cabinet group to the CKB1 port on the DCSC in the main cabinet of extension cabinet group 1. Step 3 Use the signal cable for cabinet groups to connect the CKB2 port on the DCSC in the main cabinet of the main cabinet group to the CKB1 port on the DCSC in the main cabinet of extension cabinet group 2. Step 4 Set the DIP switches on all the boards in each cabinet by referring to 3.5.1.2 Connecting Two BTS3012 Cabinet Groups. Step 5 Connect the E1 cables of the extension cabinet group to idle E1 ports in the main cabinet group or to the idle ports on the GEIUB in the BSC. ----End
Connecting Combined Cabinets and Cabinet Groups of the BTS3006C

This describes how to configure the combined cabinets and cabinet groups of the BTS3006C through optical cables.
Context
For the Abis transmission optimization BTS, the implementation of combined cabinets and cabinet groups is the same as that in TDM scheme. The hardware of the BTS3006C extension cabinet is the same as that of the BTS3006C main cabinet. In the combined cabinets and cabinet groups of the BTS3006C, the main cabinet is differentiated from the extension cabinet by the settings of the DIP switches.
Procedure
Step 1 Use an optical cable to connect the SFP optical port on the DMCM in one cabinet with the SFP optical port on the DMCM in another cabinet. Step 2 Set the DIP switches for the combined cabinets and cabinet groups of the BTS3006C. When configuring the combined cabinets and cabinet groups of the BTS3006C, you can configure the main cabinet, extension cabinet, main cabinet group, and extension cabinet group by setting the DIP switches. The DIP switches on the BTS3006C cabinet are RACK DIP switches. Table 3-7 lists the setting of the RACK DIP switches for the combined cabinets and cabinet groups of the BTS3006C.
3-14
Issue 02 (2008-06-30)
Table 3-7 Setting of the RACK DIP switches Bits on the RACK DIP Switch 4 ON 3 ON 2 ON 1 ON Cabinet 0, the main cabinet in the main cabinet group Cabinet 1, the extension cabinet in the main cabinet group Cabinet 2, the extension cabinet in the main cabinet group Cabinet 3, the main cabinet in the extension cabinet group Cabinet 4, the extension cabinet in the extension cabinet group Cabinet 5, the extension cabinet in the extension cabinet group Description
ON
ON
ON
OFF
ON
ON
OFF
ON
ON
ON
OFF
OFF
ON
OFF
ON
ON
ON
OFF
ON
OFF
----End
Connecting Hybrid Cabinet Groups of the BTS3012 and the BTS3X

This describes how to connect the BTS3012 main cabinet group with two BTS30 or BTS312 extension cabinet groups through the signal cables for cabinet groups.
Context
Figure 3-8 shows the connections of three hybrid cabinet groups.
Issue 02 (2008-06-30)
3-15
Figure 3-8 Connections of three hybrid cabinet groups

Main cabinet
Extension cabinet
Main cabinet
Extension cabinet
Main cabinet
Extension cabinet
Main cabinet group
The main cabinet in the main cabinet group is connected to the BSC through an E1 cable. The main cabinet in each extension cabinet group is connected to the main cabinet in the main cabinet group or is directly connected to the BSC through an E1 cable. The main cabinets in the extension cabinet groups cannot be directly connected with the upper-level BTS (Data configuration does not support the connection). If the cabinets in the extension cabinet groups are the BTS30 cabinets, each extension cabinet group can be configured with three cabinets. The cabinets in extension cabinet group 1 are numbered from 3 to 5; and the cabinets in extension cabinet group 2 are numbered from 6 to 8. If the cabinets in the extension cabinet groups are the BTS312 cabinets, each extension cabinet group can be configured with two cabinets. The cabinets in extension cabinet group 1 are numbered from 2 to 3; and the cabinets in extension cabinet group 2 are numbered from 4 to 5.
Procedure
Step 1 Use the signal cable for cabinet groups to connect the CKB1 port on top of the main cabinet in the main cabinet group to the CKB1 port on top of the main cabinet in extension cabinet group 1. Step 2 Use the signal cable for cabinet groups to connect the CKB2 port on top of the main cabinet in the main cabinet group to the CKB1 port on top of the main cabinet in extension cabinet group 2. Step 3 Connect all the cabinets in the three cabinet groups through PGND cables to achieve an equipotential connection. Step 4 Set the DIP switches for the combined cabinets and cabinet groups.
l
Set the DIP switches on the BTS3012 cabinets of the main cabinet group. The BTS3012 cabinets should be configured in the main cabinet group. The settings of the cabinet groups are performed through the DIP switches on each DCSU of the BTS3012 cabinets in the main cabinet group. The DCSU has 14 DIP switches: SW1SW14. SW6 and SW7 are E1 impedance selection switches. SW12SW14 are reserved.
SW1 and SW11 are used for setting the main cabinet, extension cabinet, and matching terminal, as listed in Table 3-8 and Table 3-9.
3-16
Issue 02 (2008-06-30)
Table 3-8 Setting of SW1 on the DCSU in the BTS3012 Position Main cabinet in the main cabinet group Extension cabinet in the main cabinet group SW1 ON for all bits OFF for all bits
Table 3-9 Setting of SW11 on the DCSU in the BTS3012 Position Main cabinet in the main cabinet group of three cabinet groups Other positions SW11 OFF for all bits ON for all bits
SW2 and SW5 are used for setting the main cabinet, extension cabinet, and matching terminal, as listed in Table 3-10. Table 3-10 Settings of SW2SW5 on the DCSU in the BTS3012 Position Main cabinet in the main cabinet group Extension cabinet in the main cabinet group SW2, SW3, SW4, and SW5 ON for all bits OFF for all bits
SW8 is used to set the number of a cabinet. In cabinet groups, SW8 on each main cabinet should be set; SW8 on each extension cabinet need not be set and can retain the default setting (ON for all bits), as listed in Table 3-11. Table 3-11 Setting of SW8 on the DCSU in the BTS3012 Position Bits on SW8 1 Main cabinet in the main cabinet group Extension cabinet in the main cabinet group 2 3 4
ON for all bits ON for all bits (default setting before delivery)
SW9 and SW10 are used to set the cabinet type, as listed in Table 3-12.
Issue 02 (2008-06-30)
3-17
Table 3-12 Settings of SW9 and SW10 on the DCSU in the BTS3012 Position Main cabinet in the main cabinet group Extension cabinet in the main cabinet group SW9 and SW10 ON for all bits Default setting
Set the DIP switches on the BTS30 or BTS312 cabinets of the extension cabinet group. In hybrid cabinet groups, the DIP switches on the following boards in the BTS30 or BTS312 should be set for cabinet groups:

Common module backplane (CMB) Time distribution unit (TDU) Transceiver backplane (TRB) Power supply backplane (PWB) Settings of the DIP switches on the CMB
S1 is used to set the number of a cabinet, as listed in Table 3-13 and Table 3-14. Table 3-13 Setting of S1 on the CMB in the BTS30 BTS30 Bits on S1 1 Main cabinet in extension cabinet group 1 Extension cabinet 1 in extension cabinet group 1 Extension cabinet 2 in extension cabinet group 1 Main cabinet in extension cabinet group 2 Extension cabinet 1 in extension cabinet group 2 Extension cabinet 2 in extension cabinet group 2 ON ON ON ON ON OFF 2 ON OFF OFF OFF OFF ON 3 OFF ON ON OFF OFF ON 4 OFF ON OFF ON OFF ON
Table 3-14 Setting of S1 on the CMB in the BTS312 BTS30 Bits on S1 1 Main cabinet in extension cabinet group 1
3-18
2 ON
3 OFF
4 ON
ON
Issue 02 (2008-06-30)
BTS30
Bits on S1 1 2 ON OFF OFF 3 OFF ON ON 4 OFF ON OFF
Extension cabinet in extension cabinet group 1 Main cabinet in extension cabinet group 2 Extension cabinet in extension cabinet group 2
ON ON ON
S1 is used to set CBUS1 and CBUS2, as listed in Table 3-15. Table 3-15 Setting of S2 on the CMB in the BTS30 or BTS312 BTS30/BTS312 Bits on S2 1 Main cabinet in the extension cabinet group Extension cabinet in the extension cabinet group OFF OFF 2 OFF OFF 3 ON OFF 4 ON OFF
S3 is used to set DBUS1 and DBUS2, as listed in Table 3-16. Table 3-16 Setting of S3 on the CMB in the BTS30 or BTS312 BTS30/BTS312 Bits on S3 1 Main cabinet in the extension cabinet group Extension cabinet in the extension cabinet group ON OFF 2 ON OFF 3 ON OFF 4 ON OFF
S4 is used to set CBUS3, as listed in Table 3-17. Table 3-17 Setting of S4 on the CMB in the BTS30 or BTS312 BTS30/BTS312 Bits on S4 1 Main cabinet in the extension cabinet group ON 2 ON 3 ON 4 ON
Issue 02 (2008-06-30)
3-19
BTS30/BTS312
Bits on S4 1 2 OFF 3 OFF 4 OFF
Extension cabinet in the extension cabinet group
OFF
S5 is used to set the BTS type, as listed in Table 3-18. Table 3-18 Setting of S5 on the CMB in the BTS30 or BTS312 BTS Type Bits on S5 1 BTS30 BTS312 ON ON 2 ON ON 3 ON ON 4 ON OFF
Settings of the DIP switches on the TDU
Settings of the DIP switches on the TRB in the BTS312 The DIP switches on the TRB must be configured in pairs: S1 and S3, S2 and S4, S5 and S6.
S1 and S3 indicate the cabinet number: 07, as listed in Table 3-19. Table 3-19 Settings of S1 and S3 on the TRB in the BTS312 BTS312 Bits on S1 and S3 F_ID3 ID6 Main cabinet in extension cabinet group 1 Extension cabinet in extension cabinet group 1 Main cabinet in extension cabinet group 2 Extension cabinet in extension cabinet group 2 ON ON ON ON F_ID2 ID5 ON ON OFF OFF F_ID1 ID4 OFF OFF ON ON F_ID0 ID3 ON OFF ON OFF
S2 and S4 indicate the subrack number. S5 and S6 are the switches for the matching impedance of the clock bus, as listed in Table 3-20.
3-20
Issue 02 (2008-06-30)
Table 3-20 Settings of S5 and S6 on the TRB in the BTS312 BTS312 Subrack 0 (the lowest subrack) Miscellaneous S5 and S6 ON for all bits OFF for all bits
Settings of the DIP switches on the TRB in the BTS30 As listed in Table 3-21, S1 indicates the subrack number (08) of the TRX, and S2 indicates the subrack number (08) of the CDU. Table 3-21 Settings of S1 and S2 on the TRB in the BTS30 BTS312 Bits on S1 ID6 Bits on S2 F_ID3 Main cabinet in extension cabinet group 1 Extension cabinet 1 in extension cabinet group 1 Extension cabinet 2 in extension cabinet group 1 Main cabinet in extension cabinet group 2 Extension cabinet 1 in extension cabinet group 2 Extension cabinet 2 in extension cabinet group 2 ON ON ON ON ON OFF F_ID2 ON OFF OFF OFF OFF ON F_ID1 OFF ON ON OFF OFF ON F_ID0 OFF ON OFF ON OFF ON ID5 ID4 ID3
Setting of the DIP switch on the PWB The DIP switch on the PWB indicates the number of a cabinet, as listed in Table 3-22 and Table 3-23. Table 3-22 Setting of the DIP switch on the PWB in the BTS30 BTS30 Bits on the DIP switch 4 Main cabinet in extension cabinet group 1 Extension cabinet 1 in extension cabinet group 1 OFF OFF 3 OFF ON 2 ON OFF 1 ON OFF
Issue 02 (2008-06-30)
3-21
BTS30
Bits on the DIP switch 4 3 ON ON ON OFF 2 OFF ON ON OFF 1 ON OFF ON OFF
Extension cabinet 2 in extension cabinet group 1 Main cabinet in extension cabinet group 2 Extension cabinet 1 in extension cabinet group 2 Extension cabinet 2 in extension cabinet group 2
OFF OFF OFF ON
Table 3-23 Setting of the DIP switch on the PWB in the BTS312 BTS312 Bits on the DIP switch 4 Main cabinet in extension cabinet group 1 Extension cabinet in extension cabinet group 1 Main cabinet in extension cabinet group 2 Extension cabinet in extension cabinet group 2 OFF OFF OFF OFF 3 OFF OFF ON ON 2 ON ON OFF OFF 1 OFF ON OFF ON
----End
3.5.2 Configuring Combined BTS Cabinets

This describes how to configure the combined cabinets and cabinet groups of the BTS3012, the combined cabinets and cabinet groups of the BTS3006C, and the hybrid cabinet groups of the BTS3012 and the BTS3X on the BSC6000 Local Maintenance Terminal. 3.5.2.1 Configuring Combined Cabinets and Cabinet Groups of the BTS3012 This describes how to configure TRXs, site chains, and internal connections on the BSC6000 Local Maintenance Terminal. 3.5.2.2 Configuring Combined Cabinets and Cabinet Groups of the BTS3006C This describes how to configure TRXs, site chains, and internal connections on the BSC6000 Local Maintenance Terminal. 3.5.2.3 Configuring Hybrid Cabinet Groups of the BTS3012 and the BTS3X This describes how to configure TRXs, site chains, and internal connections on the BSC6000 Local Maintenance Terminal.
Configuring Combined Cabinets and Cabinet Groups of the BTS3012

This describes how to configure TRXs, site chains, and internal connections on the BSC6000 Local Maintenance Terminal.
Context
In the BTS3012 combined cabinets and cabinet groups, the numbers of the TRXs are as follows:
l l l l l l
Main cabinet in the main cabinet group: 011 Extension cabinet in the main cabinet group: 1223 Main cabinet in extension cabinet group 1: 2435 Extension cabinet in extension cabinet group 1: 3647 Main cabinet in extension cabinet group 2: 4859 Extension cabinet in extension cabinet group 2: 6071
When the first TRX is added to a specified cabinet group, the cabinet group is automatically added. For example, assume that a BTS has only one cabinet, which is the main cabinet in the main cabinet group. If a TRX that is numbered 12 is added, the extension cabinet in the main cabinet group is added automatically. If a TRX that is numbered 24 is added, the main cabinet in extension cabinet group 1 is added automatically.
Procedure
Step 1 Add a TRX. 1. 2. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target cell, and then select Add TRX from the shortcut menu. In the displayed dialog box, select the target BTS and click Set Site Device. A dialog box is displayed, as shown in Figure 3-9.
Issue 02 (2008-06-30)
3-23
Figure 3-9 Site Device Attributes dialog box
3.
Right-click the target DTRU, and then select Configure Board Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 3-10.
3-24
Issue 02 (2008-06-30)
Figure 3-10 Binding logical TRX dialog box
4. 5.
Select the check box in front of Trx No., and set the Assigned Cell. Then, click OK. The dialog box shown in Figure 3-9 is updated. Double-click DDPU. A dialog box is displayed, as shown in Figure 3-11. Figure 3-11 Set Antenna Feeder Property dialog box
6. 7.
Select Downlink Tributary and configure the related parameters. Then, click OK. The dialog box shown in Figure 3-9 is updated. In the dialog box shown Figure 3-9, click OK to return to the upper-level menu. Then, select the target cell and click Set Cell TRX. A dialog box is displayed, as shown in Figure 3-12.
Issue 02 (2008-06-30)
3-25
Figure 3-12 Configure Cell TRX dialog box
8. 9.
Select the added TRX and configure TRX Attributes and Cell Frequency. Click OK. The upper-level menu is displayed.
10. Click Finish to complete the TRX addition. Step 2 Add site chains. 1. 2. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target site, and then select Add or Delete Site Chain from the shortcut menu. Select the target site. Then click Add or Delete Chain. A dialog box is displayed, as shown in Figure 3-13. Figure 3-13 Add or Delete Site Chain dialog box
3-26
Issue 02 (2008-06-30)
3.
Click New Port. A dialog box is displayed, as shown in Figure 3-14. Figure 3-14 Add Site Slave Chain dialog box
4.
Select the target port and click OK.
Step 3 Add internal connections. When configuring a cabinet group, you have to configure the internal connection of the site. When configuring the internal connection, adhere to the following principles:
l l
Two cabinet groups should be connected to each other in one-to-one port connection mode. Signals should be transmitted from the main cabinet group to each extension cabinet group. At least one connection should be established between the main cabinet group and each extension cabinet group.
To display the internal connection configuration dialog box, you can choose either of the following ways:
l
When adding a TRX, you must configure the internal connection of cabinet groups if the new TRX is added to a new cabinet group. In the Add TRX dialog box, click Set Site Device. The Site Device Attributes dialog box is displayed. Click Site Inner Connection to display the configuration dialog box. In the dialog box shown in Figure 3-13, click Site Inner Connection to display the configuration dialog box.
Figure 3-15 shows the dialog box for configuring internal connections.
Issue 02 (2008-06-30)
3-27
Figure 3-15 Configure Connections between Cabinet Groups dialog box
1. 2. 3.
Click the Out-Port list box and select an output port. Click the In-Port list box and select an input port. Repeat 3.1 to configure multiple internal connections. Click OK. The configuration is complete.
NOTE
l l l
The Out-Port and In-Port list boxes list all the idle ports on the main cabinet group and on the extension cabinet group respectively. The ports for internal connections are determined by the main control boards in the BTS cabinets. To delete an internal connection, click the connection, and then select None from the In-Port list box.
----End
Configuring Combined Cabinets and Cabinet Groups of the BTS3006C

Context
In the BTS3006C combined cabinets and cabinet groups, the numbers of the TRXs are as follows:
l l l l l
Main cabinet in the main cabinet group: 05 Extension cabinet 1 in the main cabinet group: 611 Extension cabinet 2 in the main cabinet group: 1217 Main cabinet in extension cabinet group 1: 1823 Extension cabinet 1 in extension cabinet group 1: 2429
When the first TRX is added to a specified cabinet group, the cabinet group is automatically added. For example, assume that a BTS has only one cabinet, which is the main cabinet in the main cabinet group. If a TRX that is numbered 12 is added, the extension cabinet in the main cabinet group is added automatically. If a TRX that is numbered 24 is added, the main cabinet in extension cabinet group 1 is added automatically.
Procedure
3. 4.
Right-click the target slot, and then choose Add Board > TRU from the shortcut menu. Double-click the added TRU and set the Assigned Cell, as shown in Figure 3-17.
Issue 02 (2008-06-30)
3-29
5.
Click OK to return to the dialog box shown in Figure 3-16. Then, double-click DDPM. A dialog box is displayed, as shown in Figure 3-18. Figure 3-18 Set Antenna Feeder Property dialog box
6. 7.
3-30
Issue 02 (2008-06-30)
8. 9.
Issue 02 (2008-06-30)
3-31
3.
4.
l l
l
3-32
Issue 02 (2008-06-30)
NOTE
The Out-Port and In-Port list boxes list all the idle ports on the main cabinet group and on the extension cabinet group respectively. The ports for internal connections are determined by the main control boards in the BTS cabinets.
1. 2.
Click the Out-Port list box and select an output port. Click the In-Port list box and select an input port. Click OK. The configuration is complete.
NOTE
To delete an internal connection, click the connection, and then select None from the In-Port list box.
----End
Configuring Hybrid Cabinet Groups of the BTS3012 and the BTS3X

Context
In the hybrid combined cabinets and cabinet groups of the BTS3012, the numbers of the TRXs are as follows:
l l l l l l
Main cabinet in the main cabinet group: 011 Extension cabinet in the main cabinet group: 1223 Main cabinet in extension cabinet group 1: 2435 Extension cabinet in extension cabinet group 1: 3647 Main cabinet in extension cabinet group 2: 4859 Extension cabinet in extension cabinet group 2: 6071
When the first TRX is added to a specified cabinet group, the cabinet group is automatically added. For example, assume that a BTS has only one cabinet, which is the main cabinet in the main cabinet group. If a TRX that is numbered 12 is added, the extension cabinet in the main cabinet
group is added automatically. If a TRX that is numbered 24 is added, the main cabinet in extension cabinet group 1 is added automatically.
Procedure
3.
Right-click the target DTRU, and then select Configure Board Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 3-24.
3-34
4. 5.
Select the check box in front of Trx No., and set the Assigned Cell. Then, click OK. The dialog box shown in Figure 3-23 is updated. Double-click DDPU. A dialog box is displayed, as shown in Figure 3-25. Figure 3-25 Set Antenna Feeder Property dialog box
6. 7.
Issue 02 (2008-06-30)
3-35
8. 9.
3-36
Issue 02 (2008-06-30)
3.
4.
l l
l
Issue 02 (2008-06-30)
3-37
NOTE
The Out-Port and In-Port list boxes list all the idle ports on the main cabinet group and on the extension cabinet group respectively. The ports for internal connections are determined by the main control boards in the BTS cabinets.
1. 2.
Click the Out-Port list box and select an output port. Click the In-Port list box and select an input port. Click OK. The configuration is complete.
NOTE
To delete an internal connection, click the connection, and then select None from the In-Port list box.
----End

This lists the alarms and counters related to combined BTS cabinets.
Alarms
Table 3-24 lists the alarms related to combined BTS cabinets. Table 3-24 Alarms related to combined BTS cabinets Alarm ID 4154 4156 4158 4170 4184
3-38
Alarm Name TRX Main Clock Alarm TRX Slave Clock Alarm DBUS Alarm Frame or TS Number Alarm TRX Clock Critical Alarm
Alarm ID 4186 4708 4714 4716 4718 4780 4804 4842 4844 4858 4860
Alarm Name Phase-Lock Loop Critical Alarm Clock Reference Abnormal Alarm E1 Local Alarm E1 Remote Alarm AIS Alarm BTS3012 cabinet 1 arrester alarm Slave DTMU TDMA CLK Alarm BTS3012 Cabinet 3 Arrester Alarm BTS3012 Cabinet 4 Arrester Alarm BTS3012 Cabinet 6 Arrester Alarm BTS3012 Cabinet 7 Arrester Alarm
Counters
None.
3.7 References
None.
Issue 02 (2008-06-30)
3-39
4 Flow Control
4
About This Chapter
Flow Control
4.1 Overview This describes flow control. The flow control function enables the BSS to decrease the access traffic flow and to provide good quality services. 4.2 Availability This lists the NEs, software, and other conditions required for the implementation of flow control. 4.3 Impact This describes the impact of flow control on system performance and on other features. 4.4 Technical Description This describes the causes, measures, and algorithms related to flow control. 4.5 Implementation This describes how to configure flow control. 4.6 Maintenance Information This lists the alarms and counters related to flow control. 4.7 References
Issue 02 (2008-06-30)
4-1
4 Flow Control
4.1 Overview
This describes flow control. The flow control function enables the BSS to decrease the access traffic flow and to provide good quality services.
Definition
When the system traffic flow or the system load exceeds the design specifications, the BSS system performs flow control to reduce the service connections or to disable some OM functions based on priorities. This ensures the smooth operation of primary services and enables the system to restore to the normal state within a short period of time. Flow control can be classified into two types:
l
Traffic flow control Traffic flow control is an overload precaution. The traffic flow control function enables the system to retain large traffic volume and ensures the stable running of the system.
System congestion control System congestion control is an overload protection measure. The system congestion control function enables the system to control the message arrival rate when the system is overloaded. Thus, the system load is reduced.
Purposes
The purpose of flow control is as follows:
l l l
The BSC runs normally and provide services. The BSC provides optimal services. The BSC provides differentiated services based on the QoS policies.
Terms
Term Message arrival rate Definition Message arrival rate indicates the number of specified messages received by the BSC in a unit time.

None
4.2 Availability
This lists the NEs, software, and other conditions required for the implementation of flow control.
NEs Involved
Table 4-1 lists the NEs involved in flow control.
4 Flow Control
Table 4-1 NEs involved in flow control MS

NOTE
l : NEs not involved l : involved
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 4-2 lists the versions of GBSS products that support flow control. Table 4-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
The realization of flow control requires the cooperation of the MSC and the BTS.
l
The MSC can process Overload messages and Load Indication messages on the A interface. The MSC can process Overload messages and Load Indication messages sent by the BSC according to the 3GPP 48008 protocol. When the BSC is overloaded, the MSC should reduce the number of messages sent to the BSC.
The BTS can process the Overload, CCCH Load Indication, and CBCH Load Indication messages on the Abis interface. When the BTS is overloaded, it can send the BSC flow control messages (such as Overload messages and CCCH Load Indication messages), indicating the load conditions of the BTS.
Issue 02 (2008-06-30)
4-3
4 Flow Control
4.3 Impact
This describes the impact of flow control on system performance and on other features.
Impact on System Performance

Flow control requires the real-time measurement of the system load. The measurement has impacts on the system performance.
Impact on Other Features

Flow control has the following impacts on other features:
l
When the flow control takes effect, some system OM functions may be forbidden and some service flow may be controlled. For example, debug logs cannot be outputted, or some tracing messages may be limited. When the flow control takes effect, some functions cannot be used. For example, the SDCCH dynamic adjustment function is forbidden. When the flow control takes effect, the BSC may discard some access request messages, such as access request messages from MSs, paging messages, and incoming BSC handover request messages.

This describes the causes, measures, and algorithms related to flow control. 4.4.1 Flow Control Measures This describes why the BSS performs flow control and the flow control measures taken by the BSC. 4.4.2 Flow Control Algorithms This describes the flow control algorithms involved in flow control.
4.4.1 Flow Control Measures

This describes why the BSS performs flow control and the flow control measures taken by the BSC. The causes that lead to system overload are as follows:
l
Internal causes Internal causes such as OM in batches or internal exceptions may increase system processing loads or exhaust key system resources.
External causes Excessive traffic flow from other NEs may lead to the BSS overload. For example, the MSC sends a large number of paging messages within a short period of time, or a large number of MSs send or resend access request messages simultaneously. All this increases the traffic flow and processor load of the BSC and exhausts key system resources. Thus, the BSS system is overloaded.
4-4
Issue 02 (2008-06-30)
4 Flow Control
The BSC takes various flow control measures to decrease the system load. This ensures the smooth processing of primary services and enables the system to restore the normal state within a short period of time. The BSC has the following flow control measures:
l l l l l l l l
4.4.2.1 Flow Control of Message Arrival Rates 4.4.2.2 Flow Control on LAPD Links 4.4.2.3 Traffic Flow Control on the Um Interface 4.4.2.4 Cell Flow Control 4.4.2.5 Inner Flow Control 4.4.2.7 OM Flow control 4.4.2.8 Abis Resource Access Control 4.4.2.9 Congestion Backpressure Mechanism
4.4.2 Flow Control Algorithms

This describes the flow control algorithms involved in flow control. 4.4.2.1 Flow Control of Message Arrival Rates This describes the flow control of message arrival rates. The flow control of message arrival rates enables the BSC to process only a certain number of messages in a measurement period. 4.4.2.2 Flow Control on LAPD Links The flow control on LAPD links refers to controlling the number of messages sent over the LAPD links on the Abis interface. 4.4.2.3 Traffic Flow Control on the Um Interface The traffic flow on the Um interface is controlled by the BSC based on the load reports sent by the BTS. 4.4.2.4 Cell Flow Control This describes cell flow control. Each cell has a state machine for cell flow control. The flow control of one cell is independent of the other cells. 4.4.2.5 Inner Flow Control This describes the inner flow control of the BSS. The BSC performs flow control on crucial system resources, such as the CPU usage. This ensures that the primary services run normally and the BSS gradually restores the normal capacity and load when the traffic flow exceeds the capacity and flow specifications. 4.4.2.6 Flow Control Between the GTCS and the GMPS/GEPS Flow control should be started when the channels between the GTCS and the GMPS/GEPS are overloaded. 4.4.2.7 OM Flow control This describes the OM flow control. The GOMU/GBAM and service boards determine whether to perform OM or whether to send OM messages to other boards based on relevant information. 4.4.2.8 Abis Resource Access Control When allocating the bandwidth resources on the Abis interface, the BSC determines the service priority in accordance with the service type, and then determines the ratio of the access resources to be discarded on the basis of the service priority and congestion level.
4 Flow Control
4.4.2.9 Congestion Backpressure Mechanism This describes the congestion backpressure mechanism. When congestion occurs, the BSS performs different operations on PS services or CS services to decrease the congestion rate on the Abis interface.
Flow Control of Message Arrival Rates

This describes the flow control of message arrival rates. The flow control of message arrival rates enables the BSC to process only a certain number of messages in a measurement period. The BSC is overloaded when it receives a large number of paging messages from the MSC or a large number of random access request messages from MSs within a short period. These paging messages or access request messages increase the BSC load, exhaust key system resources, thus overloading the BSC. In this case, the BSC controls the message arrival rates of the paging messages on the A interface and those of the random access request messages on the Abis interface. Huawei flow control algorithms are classified into Huawei I flow control algorithm and Huawei II flow control algorithm. These two types of algorithms use different methods to control message arrival rates. Compared with Huawei I flow control algorithm, Huawei II flow control algorithm performs flow control based on the cause of random access request messages and the service type of paging messages. This ensures the normal operation of major services even if there are a large number of random access requests or paging messages.
NOTE
In one BSC, only one type of flow control algorithm is used.
Huawei I Flow Control Algorithm

The BSC monitors in real time the paging messages on the A interface and the random access request messages on the Abis interface, and calculates in real time the message arrival rates. Then, the BSC determines whether to start flow control based on the message arrival rates.
l
If the calculated message arrival rate is slower than the configured message arrival rate, the system does not start the flow control based on the message arrival rate. If the calculated message arrival rate in a specified unit time is faster than the configured maximum message arrival rate, the system directly discards the subsequent messages.
For the paging messages on the A interface, you can enable the flow control function to control the paging message arrival rate by setting Start Pg Arrival Ctrl. In addition, you can determine the number of paging messages that can be received within a Pg State Period (ms) by setting Pg Max Message Number In Period. For details on the flow control of the random access request messages received by the BSC, refer to Huawei II Flow Control Algorithm.
NOTE
The BSC does not discard the random access request messages that are responded by the called party. Instead, the random access request messages of this type are taken as examples to calculate the message arrival rate. The BSC determines whether to discard the global paging messages and the second paging messages according to the flow control strategies. These discarded messages are not included in the calculation of message arrival rate.
4-6
Issue 02 (2008-06-30)
4 Flow Control
Huawei II Flow Control Algorithm

For Huawei II flow control algorithm, paging messages and random access request messages are classified on the basis of the service type and access cause respectively, and flow control is performed on the basis of service type. Huawei II flow control algorithm can be enabled by setting Allow G2 Flow Control Algorithm.
l
Control of the arrival rate of paging messages on the A interface The BSC performs flow control on paging messages at two levels.
Flow control of message arrival rates by location area The BSC calculates in real time the number of paging messages in each location area. Within a Pg State Period(ms), if the number of paging messages in a location area received by the BSC exceeds the Pg Max Message Number In Period, the BSC directly discards the excessive paging messages.
Flow control of message arrival rates by cell For the flow control of the arrival rate of the paging messages on the A interface, the paging messages are classified into the following types:

Speech paging Packet paging Short message paging Second paging
Based on the transmit capacity of the Um interface, the BSC calculates the acceptable number of paging messages sent on the A interface and allocates these messages to the four types of paging services proportionally. In a specified period of time, the acceptable number of each type of paging messages sent on the A interface is called the resource quota for this type of paging services. The paging resource quota is allocated per cell. Based on the number of paging messages of each type within the Pg State Period (ms), the BSC dynamically allocates the resources. This enables the optimal use of the system resources.
l
Control of the arrival rate of random access request messages on the Abis interface The BSC performs flow control on random access request messages on the basis of PS services and CS services.
For the PS services, if the number of PS access request messages within a Channel Request Stat Period(ms) exceeds the Channel Request PS Domain Average Message Number of CPU0 In Period, the PS service request is rejected. CS services are classified into the following types on the basis of the access reason:

MOC (MS-originated call) MTC (MS-terminated call) OTHER
Each type of services is allocated specific call resources. The total resources of the three types equal the available resources of the BSC. Based on the number of CS access request messages of each type within the Pg State Period(ms), the BSC dynamically allocates the resources. This enables the optimal use of the system resources. If the number of CS access request messages within a Channel Request Stat Period(ms) exceeds the Channel Request CS Domain Average Message Number of CPU0 In Period, the CS service request is rejected.
4 Flow Control
If the cause is of type MTC, such as paging response, emergency call, call reestablishment, and location update, the method of controlling the message arrival rate is as follows: 1. 2. 3. 4. If there are available resources for type MTC, the call request is accepted. If there are no available resources for type MTC, the resources for type OTHER are assigned. If there are no available resources for type OTHER, the resources for type MOC are assigned. If there are no available resources for type OTHER, the call request is rejected.
If the cause is of type MOC, the strategy of controlling the message arrival rate is as follows:

If there are available resources for type MOC, the call request is accepted. If there are no available resources for type OTHER, the call request is rejected.
If the cause of an random access request message is of type OTHER, the strategy of controlling the message arrival rate is as follows:

If there are available resources for type OTHER, the call request is accepted. If there are no available resources for type OTHER, the call request is rejected.
Flow Control on LAPD Links

The flow control on LAPD links refers to controlling the number of messages sent over the LAPD links on the Abis interface. The flow control on 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 on the Abis interface according to flow control strategies. Thus, the requirements for signaling load and BSC load on LAPD links are met. This ensures the smooth operation of call services. The DL flow control on LAPD links refers to controlling the arrival rate of paging messages. The UL flow control on LAPD links refers to controlling the arrival rate of random access request messages. For details on controlling the arrival rate of messages, refer to 4.4.2.1 Flow Control of Message Arrival Rates. The BSC controls the flow on the LAPD links based on the CPU usage.
DL Flow Control
If the rate at which the messages are sent to the LAPD link in the BSC is higher than the rate at which the BSC sends the messages on the LAPD link to the Abis interface, DL messages are buffered in the I frame queue or are even discarded. Therefore, the size of the messages in the I frame queue should be calculated to determine whether to start flow control. The principles of enabling or disabling the flow control function are as follows:
l
If the ratio of the occupied I frame queues on the LAPD link is higher than Flow Control Start Threshold, the flow control function is enabled. By default, the Flow Control Start Threshold is set to 90%. That is, if the ratio of the occupied I frame queues on the LAPD link is higher than 90%, all paging messages are discarded. If the ratio of the occupied I frame queues on the LAPD link is lower than or equal to Flow Control End Threshold, the flow control function is disabled. By default, the Flow Control Start Threshold is set to 60%. That is, if the ratio of the occupied I frame queues on the LAPD link is lower than or equal to 60%, no paging messages are discarded.
4-8
4 Flow Control
If a great number of paging messages are processed by only one CPU on the GXPUT, the CPU may fail because of overload. Therefore, the BSC determines the flow control level on the basis of the CPU usage. The strategies of flow control are as follows:
l
If CPU Occupied Rate Threshold of XPUT's Paging Flow Control in Slight Congestion (%) < CPU usage CPU Occupied Rate Threshold of XPUT's Paging Flow Control in Minor Congestion (%), the BSC performs the slight flow control on paging messages. If CPU Occupied Rate Threshold of XPUT's Paging Flow Control in Minor Congestion (%) < CPU usage CPU Occupied Rate Threshold of XPUT's Paging Flow Control in Major Congestion (%), the BSC performs the minor flow control on paging messages. If CPU Occupied Rate Threshold of XPUT's Paging Flow Control in Major Congestion (%) < CPU usage CPU Occupied Rate Threshold of XPUT's Paging Flow Control in Critical Congestion (%), the BSC performs the major flow control on paging messages. If CPU usage > CPU Occupied Rate Threshold of XPUT's Paging Flow Control in Critical Congestion (%), the BSC performs the critical flow control on paging messages.
The BSC determines the ratio of discarded paging messages on the preceding flow control levels according to Flow Control Ratio of XPU's CS/PS Paging (%) and Flow Control Ratio of XPU's Other Paging (%).
UL Flow Control
If a large number of random access request messages are sent on the LAPD links on the Abis interface, the traffic flow of the system is sharply increased. Thus, the LAPD links are overloaded. The BSC controls the arrival rate of random access request messages sent from the BTS, and determines the flow control levels based on the CPU usage. The flow control strategies are as follows:
l
If CPU Occupied Rate Threshold of XPUT's Channel Required Flow Control in Slight Congestion (%) < CPU usage CPU Occupied Rate Threshold of XPUT's Channel Required Flow Control in Minor Congestion (%), the BSC performs the slight flow control on random access request messages. If CPU Occupied Rate Threshold of XPUT's Channel Required Flow Control in Minor Congestion (%) < CPU usage CPU Occupied Rate Threshold of XPUT's Channel Required Flow Control in Major Congestion (%), the BSC performs the minor flow control on random access request messages. If CPU Occupied Rate Threshold of XPUT's Channel Required Flow Control in Major Congestion (%) < CPU usage CPU Occupied Rate Threshold of XPUT's Channel Required Flow Control in Critical Congestion (%), the BSC performs the major flow control on random access request messages. If CPU usage > CPU Occupied Rate Threshold of XPUT's Channel Required Flow Control in Critical Congestion (%), the BSC performs the critical flow control on random access request messages.
The BSC determines the ratio of discarded random access request messages on the preceding flow control levels according to Flow Control Ratio 1 of XPU's Channel Required(%), Flow Control Ratio 2 of XPU's Channel Required(%), and Flow Control Ratio 3 of XPU's Channel Required(%).
4 Flow Control
Traffic Flow Control on the Um Interface

The traffic flow on the Um interface is controlled by the BSC based on the load reports sent by the BTS.
TRX Overload
When a TRX in the BTS is overloaded, the following procedure is initiated: 1. 2. The BTS sends an Overload message to the BSC with the cause value Processor Overload and the overloaded TRX. On receiving the Overload message, the BSC starts the internal timer and sets the state of the overloaded TRX to the overload state. In this case, the BSC stops assigning the SDCCHs and TCHs of the TRX. It also stops the SDCCH dynamic adjustment and reconversion.
l
If the TRX runs normally after the internal timer expires, the BSC can perform channel assignment and SDCCH dynamic adjustment. If the internal timer does not expire (the TRX is in the overload state) and the BSC again receives an Overload (processor overload) message related to the TRX, the BSC restarts the internal timer and sets the TRX to the overload state.
Paging Channel Overload

The network can locate a called MS by paging the MS in its location area. Then, the MS requests access to the network. If many paging messages are sent on the Um interface, PCHs may be overloaded. In this case, the following procedure is initiated: 1. 2. The BTS sends the BSC a CCCH Overload Indication message, indicating that the PCHs of the current cell are overloaded. On receiving the CCCH Overload Indication message, the BSC sends an Overload message to the MSC with the overload cause CCCH Overload. The Overload message also indicates the overloaded cell. After receiving the Overload message, the MSC reduces paging messages sent to the BSC.
NOTE
3.
The flow control related to paging channel overload is a basic function of the BSS and does not require data configurations.
Cell Broadcast Channel Overload

The BSC supports the cell broadcast short message function. Cell broadcast short messages are sent on the CBCHs. Based on the loads of the CBCHs, the BTS sends the CBCH Load Indication messages to the BSC. The CBCH Load Indication messages indicate whether the CBCH is overloaded or underloaded.
l
If the CBCHs of the current cell are overloaded, the BSC does not send cell broadcast messages to the cell within a period of N x 1.883 seconds so that the load on the CBCHs is reduced. Where, N is the delay value that is indicated in the CBCH Load Indication message, and 1.883 indicates the minimum interval (with a unit of seconds) between two consecutive broadcast messages in a cell. If the CBCHs of the current cell are underloaded and the CBCH Load Indication message indicates the number N, the BSC determines how many cell broadcast messages can be
4-10
4 Flow Control
sent. Assume that N is the number of cell broadcast messages that can be sent to the current cell, M is the number of cell broadcast messages that need to be sent, and S = Min {M, N}. The number of cell broadcast messages that can be sent by the BSC to the BTS is S.
NOTE
The flow control related to cell broadcast messages does not require data configurations, but requires the BSC to support cell broadcast short messages.
Cell Flow Control

This describes cell flow control. Each cell has a state machine for cell flow control. The flow control of one cell is independent of the other cells. If there is no channel available for assignment after the BSC receives a channel request message, the BSC triggers the cell flow control. Cell flow control is performed to avoid the following situations:
l
When a large number of MSs simultaneously send location update requests or channel requests, the BSC sends a large number of Immediate Assignment messages or Immediate Assignment Reject messages to the BTS. Thus, the BTS is overloaded and the transmission queue of AGCHs overflows. 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 timer T3101 of the cell expires. Thus, the SDCCH is wasted.
The cell flow control function uses double timers to adjust the flow control level. The double timer mechanism is described in the 3GPP 48058 protocol. When a cell is initialized, the flow control level of the cell is zero and the flow control state is Idle state. Abis Flow Control Timer 1 (timer T1) and Abis Flow Control Timer 2 (timer T2) are not running. Table 4-3 describes the transition of the flow control states. Table 4-3 Transition of the flow control states Current State Idle state Event A cell has no channel available for assignment. The current cell has no available channel. Timer T1 expires. Timer T2 is running. The current cell has no available channel. Operation The flow control level is increased by one. Timers T1 and T2 are started. The traffic statistics are performed. No action is performed. The flow control level is increased by one. Start timers T1 and T2. Next State Timers T1 and T2 are running.
Timers T1 and T2 are running.
Timers T1 and T2 are running. Timer T2 is running. Timers T1 and T2 are running.
Issue 02 (2008-06-30)
4-11
4 Flow Control
Current State
Event Timer T2 expires.
Operation The flow control level is decreased by one but still greater than 0. Timer T2 is restarted. The flow control level is decreased by one and reaches 0.
Next State Timer T2 is running.
Idle state
NOTE
Cell flow control has six levels: 0 to 5.

l l
Level 0 indicates the normal state. Level 5 indicates the most serious flow control state.
Abis Flow Control Timer 1 (timer T1) should be shorter than Abis Flow Control Timer 2 (timer T2).
When the flow control level changes, the BSC modifies the parameters MS MAX Retrans and Tx-integer in the system information and retransmits the system message. The new system message requests the MS to reduce channel request messages and to increase the interval of sending channel request messages. Table 4-4 describes the flow control measures that are taken when the cell flow control level changes. Table 4-4 Cell flow control level Adjustment of Cell Flow Control 01 12 23 34 45 54 43 MS MAX Retrans Tx-integer(RACH Timeslot (equals to a TDMA frame, 4.615ms)) If Tx-integer is smaller than 4, set the flow control level to 4. If Tx-integer is smaller than 7, set the flow control level to 7. If Tx-integer is smaller than 10, set the flow control level to 10. If Tx-integer is smaller than 13, set the flow control level to 13. Tx-integer = 15. The flow control level is Max(13, initial configuration). The flow control level is Max(10, initial configuration).
Min(4, initial configuration) Min(2, current value) Min(2, current value) 1 1 1 Min(2, initial configuration)
4-12
Issue 02 (2008-06-30)
4 Flow Control
Adjustment of Cell Flow Control 32 21 10
MS MAX Retrans
Tx-integer(RACH Timeslot (equals to a TDMA frame, 4.615ms)) The flow control level is Max(7, initial configuration). The flow control level is Max(4, initial configuration). Reset to initial configuration.
Min(2, initial configuration) Min(4, initial configuration) Initial configuration
The length of timer 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 is, the higher the length of timer T3122 is. That is, the duration that the MS waits before retransmitting a channel request message increases with the increase in the cell flow control level. Table 4-5 lists the mapping between the cell flow control level and the length of timer T3122. Table 4-5 Mapping between the cell flow control level and the length of timer T3122 Cell Flow Control Level 0 1 2 3 4 Length of Timer T3122 (Unit : Second) 10 30 90 130 170
Inner Flow Control

This describes the inner flow control of the BSS. The BSC performs flow control on crucial system resources, such as the CPU usage. This ensures that the primary services run normally and the BSS gradually restores the normal capacity and load when the traffic flow exceeds the capacity and flow specifications.
Inner Flow Control Mechanism

The BSC monitors the usage of key system resources in real time, performs calculation, and compares the calculation results with thresholds. In this way, the BSC determines the current flow control level and the proportion of random access request messages and paging messages that should be discarded. You can determine whether to enable the inner flow control function by setting Inner Flow Control Allowed. The inner flow control levels are calculated on the basis of probability and are classified into 12 levels: levels 0 through 11.
l
Level 0 indicates that inner flow control is not performed.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 4-13
Issue 02 (2008-06-30)
4 Flow Control
l
Level 11 indicates the most serious flow control.
The BSS limits some auxiliary functions based on the inner flow control levels, as listed in Table 4-6. Table 4-6 Auxiliary functions related to the internal flow control levels Control Item Flow Control Level Levels 01 Cell Frequency Scan Normal information print Normal log Call resource check Call details Performing forced handovers Switching candidate query Channel allocation queue function Radio resource indication processing (interference band) Call preemption Channel conversion Conversion between traffic channel and signaling channel Levels 23 Inhibit Inhibit Inhibit Inhibit Inhibit Levels 45 Inhibit Inhibit Inhibit Inhibit Inhibit Inhibit Levels 6-7 Inhibit Inhibit Inhibit Inhibit Inhibit Inhibit Inhibit Levels 8-9 Inhibit Inhibit Inhibit Inhibit Inhibit Inhibit Inhibit Inhibit Inhibit Leve ls 10 11 Inhibi t Inhibi t Inhibi t Inhibi t Inhibi t Inhibi t Inhibi t Inhibi t Inhibi t Inhibi t Inhibi t Inhibi t
Inhibit -
Flow Control Between the GTCS and the GMPS/GEPS

The procedure for the flow control between the GTCS and the GMPS/GEPS is as follows:
4-14
Issue 02 (2008-06-30)
4 Flow Control
1.
You can enable congestion control of the GTCS by setting Flow Control Flag between BM and TC. If the GTCS detects that the GSCU is overloaded, flow control is performed within the period of Flow Control Timer Length Between BM and TC(ms). After receiving the response message of a resource request, the BSC updates the flow control level between the GTCS and the GMPS/GEPS and processes subsequent calls according to the congestion level indicated by the message.
l
2.
If the current flow control level is 0 or an emergency call is being made, the flow control is not performed. If the current flow control level is not 0 and no emergency call is being made, the flow control level (slight/minor/major/critical) is determined according to the CPU usage of the GSCU in the GTCS or according to the resource usage of the GTCS. Then, a proportion of messages are discarded according to the flow control level. The default proportions of messages that are discarded under different flow control levels are as follows:
If CPU Ratio of SCU of TC in Slight Congestion (%) CPU usage of the GSCU in the GTCS < CPU Ratio of SCU of TC in Minor Congestion (%), the BSC starts the slight flow control. If CPU Ratio of SCU of TC in Minor Congestion (%) CPU usage of the GSCU in the GTCS < CPU Ratio of SCU of TC in Major Congestion (%), the BSC starts the minor flow control. If CPU Ratio of SCU of TC in Major Congestion (%) CPU usage of the GSCU in the GTCS < CPU Ratio of SCU of TC in Critical Congestion (%), the BSC starts the minor flow control. If the CPU usage of the GSCU in the GTCS CPU Ratio of SCU of TC in Critical Congestion(%), the BSC starts the critical flow control.
NOTE
In addition, the flow control level can be determined according to the resource usage of the GTCS. That is, if the resource usage of the GTCS > Major Flow Control Ratio of TC (%), the major flow control of the GTCS is started.
Table 4-7 lists the default proportions of messages that are discarded under different flow control levels. Table 4-7 Default proportions of messages discarded under different flow control levels Flow Control Level Slight Proportions of Messages Discarded The ratio of discarded MSoriginated calls to total MS-originated calls is 40% and the ratio of discarded MS-terminated calls to total MSterminated calls is 30%. Parameter Table mask of Slight Level Flow Control Between BM and TC
Issue 02 (2008-06-30)
4-15
4 Flow Control
Flow Control Level Minor
Proportions of Messages Discarded The ratio of discarded MSoriginated calls to total MS-originated calls is 50% and the ratio of discarded MS-terminated calls to total MSterminated calls is 40%. The ratio of discarded MSoriginated calls to total MS-originated calls is 60%, and the ratio of discarded MS-terminated calls to total MSterminated calls is 50%. The ratio of discarded MSoriginated calls to total MS-originated calls is 70% and the ratio of discarded MS-terminated calls to total MSterminated calls is 60%.
Parameter Table Mask of Minor level Flow Control Between BM and TC
Major
Table Mask of Major Level Flow Control Between BM and TC
Critical
Table Mask of Critical Level Flow Control Between BM and TC
NOTE
The discarded messages under flow control are resource request messages. The corresponding calls cannot request resources from the GTCS side, so these calls are released.
3.
When the duration is higher than the Flow Control Timer Length Between BM and TC (ms), the BSC clears the flow control information recorded by the CPU in the GTCS.
Flow Control Between the GTCS and the GMPS/GEPS

Flow control should be started when the channels between the GTCS and the GMPS/GEPS are overloaded. The procedure for the flow control between the GTCS and the GMPS/GEPS is as follows: 1. 2. When the GTCS detects that its GSCU is overloaded, the BSC starts the congestion control of the GTCS. After receiving the response message of a resource request, the BSC updates the flow control level between the GTCS and the GMPS/GEPS and processes subsequent calls according to the congestion level indicated in the message. Meanwhile, the BSC starts the timer for the flow control between the TC subrack and the BM subrack.
NOTE
You can set Flow Control Timer Length Between BM and TC on the BSC6000 Local Maintenance Terminal.
4-16
Issue 02 (2008-06-30)

l
4 Flow Control
If the current flow control level is 0 or an emergency call is in progress, the flow control is not performed. If the current flow control level is not 0 and no emergency call is in progress, a proportion of messages are discarded according to the configured flow control level (slight/minor/ major/critical) between the GTCS and the GMPS/GEPS. Table 4-8 lists the default proportions of messages that are discarded under different flow control levels. Table 4-8 Default proportions of messages discarded under different flow control levels Flow Control Level Slight Proportions of Messages Discarded The ratio of discarded MS-originated calls to total MS-originated calls is 40% and the ratio of discarded MS-terminated calls to total MS-terminated calls is 30%. The ratio of discarded MS-originated calls to total MS-originated calls is 50% and the ratio of discarded MS-terminated calls to total MS-terminated calls is 40%. The ratio of discarded MS-originated calls to total MS-originated calls is 60% and the ratio of discarded MS-terminated calls to total MS-terminated calls is 50%. The ratio of discarded MS-originated calls to total MS-originated calls is 70% and the ratio of discarded MS-terminated calls to total MS-terminated calls is 60%.
Minor
Major
Critical
NOTE
The discarded messages under flow control are resource request messages. The corresponding calls cannot request resources from the GTCS side, so these calls are released.
3.
After the timer for the flow control between the TC subrack and the BM subrack expires, the flow control information recorded by the CPU in the GTCS is cleared.
The parameters of the internal flow control are as follows:

l l l l l l l l l
Flow Control Flag Between BM and TC Table mask of Slight Level Flow Control Between BM and TC Table mask of Minor level Flow Control Between BM and TC Table Mask of Major Level Flow Control Between BM and TC Table Mask of Critical Level Flow Control Between BM and TC Flow Control Timer Length Between BM and TC CPU Ratio of SCU of TC in Slight Congestion CPU Ratio of SCU of TC in Minor Congestion CPU Ratio of SCU of TC in Major Congestion
Issue 02 (2008-06-30)
4 Flow Control
l l
CPU Ratio of SCU of TC in Critical Congestion Major Flow Control Ration of TC
OM Flow control
This describes the OM flow control. The GOMU/GBAM and service boards determine whether to perform OM or whether to send OM messages to other boards based on relevant information. The system monitoring processes monitor in real time key system resources such as the CPU usage and system message resources in the GOMU/GBAM and service boards, and then calculate the usage of these resources and the flow control level of each board. Then, based on these flow control levels, flow control is performed on messages, such as log messages and signaling tracing messages. The flow control levels of the GOMU/GBAM and each service board are broadcast to other boards through periodical message broadcasts. A board determines whether to perform OM or send OM messages to other boards based on its flow control level and the flow control levels of other boards received from periodical message broadcasts. By default, the OM flow control of the BSC uses hierarchical flow control and has multiple flow control thresholds (ThSt). For each flow control level, the BSC performs relevant operations.
l
If the value of a flow control source is smaller than ThSt1, the flow of the flow control source is not controlled. If the value of a flow control source is greater than ThStn, all the flow control sources are discarded. If the value of a flow control source is between ThSt1 and ThStn, the flow of the flow control source is controlled based on its flow control level.
Figure 4-1 shows the relations between the OM flow control levels and the flow control thresholds. Figure 4-1 Relations between the OM flow control levels and the flow control thresholds
Flow control level 5 4 3 2 1 0 ThSt1 ThStn Flow control source
When the flow control level reaches level 2, the BSC controls the flow of the signaling tracing messages.

NOTE
4 Flow Control
The ThSt is an internal parameter.
Abis Resource Access Control

When allocating the bandwidth resources on the Abis interface, the BSC determines the service priority in accordance with the service type, and then determines the ratio of the access resources to be discarded on the basis of the service priority and congestion level. When HDLC transmission is used on the Abis interface, the system determines the channel congestion level based on the bandwidth available on the Abis interface. The resource administration module calculates the bandwidth each time the resources are allocated. When the available bandwidth is lower than the left bandwidth defined in a congestion level, the congestion level is set to a corresponding congestion level. When allocating the bandwidth resources on the Abis interface, the BSC determines the service priority in accordance with the service type, and then determines the ratio of the access resources to be discarded on the basis of the service priority and congestion level. You can manually configure the service priority but cannot configure the ratio of the access resources to be discarded. Table 4-9 lists the mapping between the service type and the service priority. For details on the parameters related to the service priority, refer to Abis Congestion Control. Table 4-10 lists the mapping between the service priority and the congestion level. Table 4-9 Mapping between the service type and the service priority Type of Service Service Priority CS Preferred MS-originated calls MS-terminated calls Emergency calls VBS VGCS Supplementary services Call re-establishment Intra-BSC handover Incoming BSC handover PS services Other services 1 1 0 13 13 15 6 3 10 5 15 PS Preferred 1 1 0 13 13 15 6 3 10 1 15
Issue 02 (2008-06-30)
4-19
4 Flow Control
Table 4-10 Mapping between the service priority and the congestion level Service Priority 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Congestion Level 1 10 10 12 12 13 13 14 14 16 16 18 20 22 24 26 28 2 20 20 22 22 24 24 26 26 28 28 30 32 34 36 38 40 3 50 50 52 52 54 54 56 56 58 58 60 62 64 66 68 70 4 70 70 72 74 74 76 76 78 78 79 80 81 82 83 84 85 5 80 80 82 82 84 84 86 86 88 88 90 92 94 96 98 100
NOTE
As listed in Table 4-10, the value in a cell at the crossing point of the service priority row and the congestion level column indicates the numerator of the percentage of the access resources to be discarded to the total access resources. For example, the percentage in service priority 5 and at congestion level 4 is 76%.
If access control is enabled, the resource administration module obtains the ratio of access resources to be discarded by service priority and congestion level according to the mapping listed in Table 4-10. Then, based on the ratio, the resource requests from some calls are rejected.
Congestion Backpressure Mechanism

This describes the congestion backpressure mechanism. When congestion occurs, the BSS performs different operations on PS services or CS services to decrease the congestion rate on the Abis interface. When the IP or HDLC transmission is used over the Abis interface, the BSC obtains the transmission traffic situation over the Abis interface by cell. If one TRX in a cell is congested, the BSC regards that the cell is congested. When congestion occurs, the BSC performs different operations on CS services and PS services.

l
4 Flow Control
For subsequent CS calls, the BSC preferentially allocates half-rate channels. If only fullrate channels are available in the congested cell, the BSC converts the full-rate channels into half-rate channels, and then allocates these half-rate channels. This helps relieve the congestion on the Abis interface. For PS services, the BSC performs the following operations:

Notifying the SGSN of congestion Reducing the downlink GPRS data rate and the number of additional timeslots to alleviate the congestion on the Abis interface
4.5 Implementation
This describes how to configure flow control. 4.5.1 Configuring Flow Control This describes how to configure flow control on the BSC6000 Local Maintenance Terminal.
4.5.1 Configuring Flow Control

This describes how to configure flow control on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click BSC6000 and choose Configure BSC Attributes from the shortcut menu. A dialog box is displayed. Set relevant parameters in the following manner:
l
Click the Flow Control Data tab, and then set parameters, as shown in Figure 4-2.
Figure 4-2 Configuring flow control data
Issue 02 (2008-06-30)
4-21
4 Flow Control
l
Click the BSC Timer tab. Set the parameters, as shown in Figure 4-3.
Figure 4-3 Configuring BSC timer
Click the Software Parameters tab. Set the flow control data of the GTCS, as shown in Figure 4-4.
Figure 4-4 Configuring software parameters
4-22
Issue 02 (2008-06-30)
4 Flow Control
Step 2 Set Flow Control Start Threshold and Flow Control End Threshold. 1. 2. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target TRX and then choose Configure TRX Attributes from the shortcut menu. In the TRX view list box, select the TRX whose attributes are to be modified. Then, click Set TRX Attributes. A dialog box is displayed. Click the RSL Setting tab, as shown in Figure 4-5. Set Flow Control Start Threshold and Flow Control End Threshold. Figure 4-5 Configuring TRX attributes
3.
Click OK to return to the upper-level menu until the configuration is complete.
----End

This lists the alarms and counters related to flow control.
Alarms
Table 4-11 lists the alarms related to flow control. Table 4-11 Alarms related to flow control ID 201
Issue 02 (2008-06-30)
Description Internal Flow Control Level Changed

4 Flow Control
ID 202 101 21001
Description Internal Flow Control Released MSC Overload LAPD Link Congestion
Counters
Table 4-12 lists the counters related to flow control. Table 4-12 Counters related to flow control Specification L3188H L3188I L3188J L3188K A530 A531 A532 L3188B L3188C L3188D L3188E L3188F Meaning Increases of Flow Control Levels Decreases of Flow Control Levels Ignored Trigger Events Highest Level Delays SM Pagings Discarded on LAPD Link CS Pagings Discarded on LAPD Link PS Pagings Discarded on LAPD Link MSG CCCH LOAD IND (RACH) Messages Sent on Abis Interface MSG CCCH LOAD IND (PCH) Messages Sent on Abis Interface PACKET CCCH LOAD IND Messages Sent on Abis Interface MSG ABIS OVERLOAD (CCCH OVERLOAD) Messages Sent on Abis Interface MSG ABIS OVERLOAD (PROCESSOR OVERLOAD) Messages Sent on Abis Interface
4.7 References
l
3GPP 48.058 Base Station Controller - Base Transceiver Station (BCS-BTS) Interface Layer 3 Specification 3GPP 48.008 Mobile Switching Centre - Base Station system (MSC-BSS) Interface Layer 3 Specification
4-24
5 Multiband Network
5
About This Chapter
Multiband Network
5.1 Overview This describes the definition of the multiband network and purposes of applying the multiband network. The multiband network features multiple frequency bands in one network, which increases the utilization ratio of radio frequency resources. 5.2 Availability This lists the NEs, software, and other conditions required for the implementation of the multiband network. 5.3 Technical Description The multiband network allows the BSC to manage multiple frequency bands and enables the operator to extend the frequency band. Thus, the utilization of frequency resources can be improved. 5.4 Implementation This describes how to configure, verify, and deactivate the multiband network. 5.5 Maintenance Information This lists the alarms and counters related to the multiband network. 5.6 References
Issue 02 (2008-06-30)
5-1
5 Multiband Network
5.1 Overview
This describes the definition of the multiband network and purposes of applying the multiband network. The multiband network features multiple frequency bands in one network, which increases the utilization ratio of radio frequency resources.
Definition
A multiband network consists of the networks of different frequency bands. Huawei GSM BSS supports the following types of multiband networks:
l l
GSM850 band + GSM900 band + DCS1800 band GSM850 band + GSM900 band + PCS1900 band
The most commonly used multiband networks are the dual-band networks that are GSM900 band + DCS1800 band, and GSM850 band + PCS1900 band.
NOTE
l l l
The GSM900 band is the most widely used frequency band in the GSM network. The GSM900 band consists of the P-GSM900, E-GSM900, and R-GSM900. DCS1800 band and PCS1900 band have many frequencies in common, so the two frequency bands cannot constitute a multiband network.
Purposes
The multiband network allows the BSC to manage multiple frequency bands and enables the frequency band extension. The introduction of extended frequency bands of E-GSM and R-GSM effectively relieves the insufficiency of radio frequency resources.
Terms
None.

Acronyms and Abbreviations BCCH BA CM ECSC MBR CBQ CBA
5-2
Full Spelling Broadcast Control Channel BCCH Allocation Classmark Early Classmark Sending Control Multiband Report Cell Bar Qualify Cell Bar Access
Issue 02 (2008-06-30)
5 Multiband Network
Acronyms and Abbreviations CDU PBU
Full Spelling Combining and Distribution Unit Power Boost Unit
5.2 Availability
This lists the NEs, software, and other conditions required for the implementation of the multiband network.
NEs Involved
Table 5-1 lists the NEs involved in the multiband network. Table 5-1 NEs involved in the multiband network MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 5-2 lists the versions of GBSS products that support the multiband network. Table 5-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM
Issue 02 (2008-06-30)
Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R004C02 and later releases BTS3000V100R002C01 and later releases BTS3000V100R004C02 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases
5-3
5 Multiband Network
Product BTS3900A GSM
Version BTS3000V100R008C02 and later releases
Miscellaneous
The multiband network requires the MS to support corresponding multiple bands. The MS supporting a single frequency band can also gain access to the multiband network, but camps only on the corresponding frequency band in the multiband network. Huawei GSM BSS supports GSM900 band, DCS1800 band, PCS1900 band, and GSM850 band. Huawei GSM BSS does not support GSM450 band or GSM480 band. In terms of cell, Huawei GSM BSS supports GSM900/DCS1800 Co-BCCH cell, and does not support GSM850/PCS1900 Co-BCCH cell.

The multiband network allows the BSC to manage multiple frequency bands and enables the operator to extend the frequency band. Thus, the utilization of frequency resources can be improved. 5.3.1 Mapping Between ARFCN and Frequency This describes the mapping between the ARFCN and the frequency. A multiband network consists of the networks of different frequency bands. Each frequency band has the corresponding range of ARFCN. 5.3.2 Frequency Assignment for TRXs This describes the frequency assignment for TRXs. The TRXs configured on the BTS must support related frequency bands to enable a multiband network. 5.3.3 Multiband Channel Assignment This describes the multiband channel assignment. In channel assignment, the multiband channel assignment considers the capability of the MS and the channel itself to support the frequency bands. The channel assignment strategy depends on the practical application. 5.3.4 Frequency Band Features This describes the features of frequency bands. The performance of a network can be improved with a proper networking mode based on the features of different frequency bands. 5.3.5 Multiband Network Topology This describes the multiband networking mode. The networking mode for a multiband network is of three types: independent MSC networking, Co-MSC/independent BSC networking, and Co-BSC networking. The former two types are referred to as independent networking, and the latter one is referred to as hybrid networking. 5.3.6 Technical Principles This describes the technical principles related to the multiband network. Based on the principles, you need to correctly configure related parameters at the network enabling stage to ensure the performance of the multiband network. 5.3.7 Traffic Guiding Strategy
5 Multiband Network
This describes the traffic guiding strategy of the multiband network. To meet the increasing requirements on high capacity and quality of the multiband network, the DCS1800 band is required to absorb or share the traffic volume at a maximum extent. 5.3.8 Enhanced Dual-Band Network This describes the enhanced dual-band network that is an improvement on the existing dualband network. In the enhanced dual-band network, two co-sited cells with different coverage areas are logically formed into a cell group. One is an overlaid subcell and the other is an underlaid subcell. The enhanced dual-band network algorithm enables the channel resource sharing and the cell load balance between the two cells in a cell group.
5.3.1 Mapping Between ARFCN and Frequency

This describes the mapping between the ARFCN and the frequency. A multiband network consists of the networks of different frequency bands. Each frequency band has the corresponding range of ARFCN. There are eight frequency bands available for the multiband network. Table 5-3 lists the mapping between the Absolute Radio Frequency Channel Number (ARFCN) and the frequency in each frequency band. Table 5-3 Mapping between the ARFCN and the frequency Frequency Band P-GSM900 band Uplink Frequency Fl(n) = 890 + 0.2 x n 890-915 MHz E-GSM900 band Fl(n) = 890 + 0.2 x n Fl(n) = 890 + 0.2 x (n 1024) 880-915 MHz R-GSM900 band Fl(n) = 890 + 0.2 x n Fl(n) = 890 + 0.2 x (n 1024) 876-915 MHz 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 GSM850 band Fl(n) = 824.2 + 0.2 x (n 128) 824-849 MHz
Issue 02 (2008-06-30)
Downlink Frequency Fu(n) = Fl(n) + 45 935-960 MHz Fu(n) = Fl(n) + 45
ARFCN 1 n 124
0 n 124 975 n 1023
925-960 MHz Fu(n) = Fl(n) + 45
0 n 124 955 n 1023
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
512 n 810
128 n 251
5-5
5 Multiband Network
Frequency Band GSM450 band
Uplink Frequency Fl(n) = 450.6 + 0.2 x (n 259) 450.4-457.6 MHz
Downlink Frequency Fu(n) = Fl(n) + 10 460.4-467.6 MHz Fu(n) = Fl(n) + 10 488.8-496 MHz
ARFCN 259 n 293
GSM480 band
Fl(n) = 479 + 0.2 x (n 306) 478.8-486 MHz
306 n 340
NOTE
In Table 5-3, n indicates the Absolute Radio Frequency Channel Number and the frequency is in unit of MHz. Fl(n) indicates the uplink frequency corresponding to n. On the uplink frequency, the MS sends signals to the BTS. Fu(n) indicates the downlink frequency on which the BTS sends signals to the MS.
For frequency band division, you still need to keep the following in mind:
l
The E-GSM900 band, R-GSM900 band, and P-GSM900 band are in the same frequency band without adjacent frequencies. The E-GSM extended band refers to the band that does not contain the P-GSM band. The R-GSM extended band refers to the band that does not contain the E-GSM band.
l l
Huawei DFCU/DFCB that operates over DCS1800 is categorized into the high frequency model and the low frequency model based on the operating frequency band. Each model covers a bandwidth of 50 MHz..
l l
The operating frequency band of the high frequency DFCU/DFCB is 1830-1880 MHz. The operating frequency band of the low frequency DFCU/DFCB is 1805-1855 MHz.
5.3.2 Frequency Assignment for TRXs

This describes the frequency assignment for TRXs. The TRXs configured on the BTS must support related frequency bands to enable a multiband network. Table 5-4 lists the range of ARFCN supported by each type of TRX. Table 5-4 Range of ARFCN supported by each type of TRX TRX PTRX ETRX RTRX DTRX PETR
5-6
Range of ARFCN 1 n 124 0 n 124, or 975 n 1023 0 n 124, or 955 n 1023 512 n 885 512 n 810
5 Multiband Network
TRX EETR RETR DETR TRX
Range of ARFCN 128 n 251 0 n 124, or 955 n 1023 512 n 885 The TRX converts to PTRX or DTRX based on frequencies. The TRX helps the system decide the frequency band support for TRX mutual aid.
NOTE For the candidate TRX selection in TRX mutual aid, the frequencies of the source TRX must be interchangeable with those of the target TRX. That is, the TRX, CDU, and PBU of the target/source TRX must support all the frequencies configured for the source/target TRX.
5.3.3 Multiband Channel Assignment

This describes the multiband channel assignment. In channel assignment, the multiband channel assignment considers the capability of the MS and the channel itself to support the frequency bands. The channel assignment strategy depends on the practical application.
Channel Assignment Mode

Based on HW II channel allocation algorithm, the multiband channel assignment mode selects the channel of a frequency band within a cell according to the BCCH carrier frequency and the frequency bands supported by the MS. In a channel assignment procedure, the system decides the capability of every channel to support the MS based on the MS classmark. Then, the system preferentially assigns the channel on the band outside of the band intersection to the MS. That is, the DCS1800 band has the highest priority level and the GSM900 band has the lowest priority level. This ensures that the common frequency bands are allocated to the low-end MSs and the network capacity is maximized. For an MS that supports the E-GSM band, if the available channels are carried on the P-GSM band and the E-GSM extended band, the channel on the E-GSM extended band is preferentially assigned to the MS. The band intersection, P-GSM band, is assigned to other MSs with weak band supporting capability.
Channel Assignment Strategies

In a channel assignment procedure, the system decides the capability of every channel to support the MS based on the MS classmark. The details are as follows.
l
If the MS classmark 3 is valid, the system decides the capability based on the MS classmark 3. If the MS classmark 3 is invalid, the band supported by the MS is updated to the band where the BCCH is carried.
For example, the BCCH is carried on the E-GSM extended band. When the MS classmark 3 is invalid, the band supported by the MS becomes the E-GSM extended band. Because the E-GSM extended band contains the P-GSM band, the MS supports the P-GSM band at the same time. The BSC filters the unqualified channels and assigns the channel with the highest priority level to the MS.
5 Multiband Network
The priority level of a channel consists of four bytes with one bit indicating one frequency band. The bit corresponding to the frequency band that the channel is carried on is set to 1. See Figure 5-1. Figure 5-1 Frequency band bit for channel priority
TCH priority TCH/Band_P TCH/Band_E TCH/Band_R
... ... ... ...
P 1 0 0
E 0 1 0
R 0 0 1
850 0 0 0
450 0 0 0
480 0 0 0
1900 0 0 0
1800 0 0 0
... ... ... ...
The greater the bit value is, the lower the priority level of the corresponding channel is. For example, if an MS supports the R-GSM band, the TCH carried on the P-GSM, E-GSM or RGSM band can be assigned to the MS. Based on the channel priority, which is R-GSM > E-GSM > P-GSM, the TCH carried on the R-GSM band is preferentially assigned to the MS. The band carrying the TCH is determined by the TRX, and the band of the TRX is determined by the assigned frequency. For example, the assigned frequency for RTRX is in the P-GSM band, and therefore the TCH on RTRX is carried on the P-GSM band. In the case of immediate assignment, the system assigns the channel for the MS based on the frequency band where the BCCH is carried.
5.3.4 Frequency Band Features

This describes the features of frequency bands. The performance of a network can be improved with a proper networking mode based on the features of different frequency bands.
NOTE
l l l
The features of the PCS1900 band are similar to those of the DCS1800 band. The features of the GSM850 band are similar to those of the GSM900 band. The GSM850 band and the GSM900 band feature strong penetration and wide coverage. The features of the GSM850 band are in opposition to those of the DCS1800 band.
Due to the previously mentioned points, only the features of the DCS1800 band are described as below.
Propagation Features of the DCS1800 Band

The working frequency of the DCS1800 band is twice that of the GSM900 band. Therefore, there are following differences in propagation loss between the DCS1800 band and the GSM900 band:
l
In Line of Sight (LOS), the propagation loss of the DCS1800 band is 6 dB greater than that of the GSM900 band. Out of LOS, the propagation loss of the DCS1800 band is 10 dB greater than that of the GSM900 band.
5-8

l
5 Multiband Network
In a building, the propagation loss of the DCS1800 band is 5-17 dB greater than that of the GSM900 band (associated with the materials of the building).
Fast fading of the 1800 MHz band unfavorably affects the network coverage, which directly degrades the network performance. In terms of the diffraction capability of the electromagnetic wave, the 900 MHz band outperforms the 1800 MHz band.
Coverage Requirements for DCS1800 Band

The coverage of the DCS1800 band is applied to two applications:
l
Outdoor coverage This application is easily implemented with small distance between BTSs. If necessary, add the equipment supporting the DCS1800 band at the original GSM900-band site, and add BTSs at suitable places.
Indoor coverage To ensure a good indoor coverage of the DCS1800 band, Huawei recommends that the distance between BTSs in downtown be less than 1 km, with 500-800 m preferably.
Coverage Modes of DCS1800 Band

The network coverage of the DCS1800 band in a multiband network is of three modes, which are complete continuous coverage, continuous coverage in hot spots, and sparse coverage in hot spots. The features are listed as follows:
l
Complete continuous coverage
High traffic-absorbing capability, few inter-layer handover, and high network performance Easy frequency planning, network optimization, and traffic distribution control Site deployment once for all, stepwise capacity expansion for TRXs based on requirements, and convenient construction and maintenance Huge investment, and difficulty in selecting all the sites at a time Limited traffic-absorbing capability, and frequent multiband handover High requirements for locating traffic hot spots Irregular BTS distribution, which causes difficulty in frequency planning and network optimization Difficulty in construction and maintenance Site construction in densely-populated areas with stepwise coverage and investment efficiency Low traffic-absorbing capability, and frequent multiband handover High requirements for locating traffic hot spots Irregular BTS distribution, which causes difficulty in frequency planning and network optimization Difficulty in construction and maintenance Small initial investment
Continuous coverage in hot spots

Sparse coverage in hot spots

Issue 02 (2008-06-30)
5 Multiband Network
5.3.5 Multiband Network Topology

This describes the multiband networking mode. The networking mode for a multiband network is of three types: independent MSC networking, Co-MSC/independent BSC networking, and Co-BSC networking. The former two types are referred to as independent networking, and the latter one is referred to as hybrid networking.
Independent MSC Networking

In independent MSC networking mode, the GSM850 band, GSM900 band, DCS1800 band, and GSM1900 band use different MSCs respectively. Figure 5-2 shows this networking mode where the commonly used GSM900 band and the DCS1800 band are applied. Figure 5-2 Independent MSC networking mode
BTS MS BTS BSC
GSM900M MSC/VLR 1
OMC
EIR
SMC
HLR/AUC
BTS MS BTS BSC DCS1800M MSC/VLR 2
The features of independent MSC networking mode are as follows:

l l
No impact on the existing network. Convenient for network planning and data configuration. The network deployment becomes easy. Frequent inter-office handovers and location updates burden the signaling links. Requirements are met for capacity expansion in the long term. Convenient for network management and service development. Cooperation of equipment from different manufacturers is required. The initial investment of network deployment is relatively huge. But the average investment on a user is the lowest.
l l l l l
Due to the previously mentioned features, the independent MSC networking mode outperforms the hybrid networking mode in the long term.
5 Multiband Network
Co-MSC/Independent BSC Networking

In Co-MSC/independent BSC networking mode, the GSM850 band, GSM900 band, DCS1800 band, and GSM1900 band use the same MSC but different BSCs. Figure 5-3 shows this networking mode where the commonly used GSM900 band and the DCS1800 band are applied. Figure 5-3 Co-MSC/independent BSC networking mode
GSM900M MS
BTS BSC1 BTS OMC MSC/VLR SMC HLR/AUC EIR
DCS1800M MS
BTS BSC2 BTS
The features of Co-MSC/independent BSC networking mode are as follows:

l l l l
Certain Impact on the existing network. NSS re-planning is required. The network deployment is difficult. Inconvenient for capacity expansion and network evolvement. The initial investment of network deployment is relatively small. The average investment on a user is relatively low. The competition among candidate equipment manufacturers is introduced, which helps reduce the investment and improve the service quality. The independent BSC has backup and the network security is guaranteed.
Co-BSC Networking
In Co-BSC networking mode, the GSM850 band, GSM900 band, DCS1800 band, and GSM1900 band use the same BSC, or, the multiband BTSs are connected to the BSC. Figure 5-4 shows this networking mode where the commonly used GSM900 band and the DCS1800 band are applied.
Issue 02 (2008-06-30)
5-11
5 Multiband Network
Figure 5-4 Co-BSC networking
BTS
MS
BTS
BSC1
BTS
OMC MSC/VLR
EIR
BTS
SMC
HLR/AUC
MS
BTS
BSC2
BTS
GSM900M
DCS1800M
GSM900M/DCS1800M
The features of Co-BSC networking mode are as follows:

l
Possible huge impact on the existing network. The impact may be very serious in case of a small-capacity BSC. NSS re-planning and BSS re-planning are required. The network deployment is difficult. Inconvenient for capacity expansion and network evolvement. Inconvenient for service development. The competition among candidate equipment manufacturers cannot be introduced. It is difficult to cut down the investment and improve the service quality.
l l l l
5.3.6 Technical Principles

This describes the technical principles related to the multiband network. Based on the principles, you need to correctly configure related parameters at the network enabling stage to ensure the performance of the multiband network.
MS Classmark
In the GSM system, MS classmark indicates the service capability, supported bands, power capability, and encryption capability of an MS. MS classmark is of three types, namely, Classmark 1, Classmark 2, and Classmark 3. The information contained in Classmark 3 is for multiband applications. The equipment in a multiband network is required to support related handling of MS classmark. The network learns the capabilities of an MS by querying the MS classmark. Alternatively, the network sets ECSC to require the MS to report its classmark after the link establishment.
5 Multiband Network
Huawei GSM equipment supports the functions such as early classmark sending control (ECSC), and handling of Classmark 3.
BCCH Allocation Table

In the GSM system, the BCCH Allocation (BA) table is a list of BCCH frequencies of all the neighbor cells. The network sends the MS the BA table in system information, enabling network compatibility for the MSs. Thus, the MSs can access the multiband network and perform handover successfully. The BA table is of the following two types:
l
2G BA1 Table 2G BA1 Table lists the neighbor cells for the MS in idle mode. 2G BA1 Table is sent in system information type 2, 2bis, and 2ter, which are regularly broadcast by the network on the SACCH to all MSs for cell reselection in idle mode.
2G BA2 Table 2G BA2 Table lists the neighbor cells for the MS in busy mode. 2G BA2 Table is sent in system information type 5, 5bis, and 5ter, which are regularly broadcast by the network on the SACCH to all MSs for handover in busy mode.
While the MS is in busy mode, the MS cannot extract parameters related to neighbor cells from system information type 2, 2bis, and 2ter. Instead, the MS in busy mode extracts the BA table from system information type 5, 5bis, and 5ter, which are regularly broadcast on the SACCH, to ensure the handover procedure. The BA table in system information type 5, 5bis, and 5ter can be identical with or different from that in system information type 2, 2bis, and 2ter, depending on the specific network conditions. The settings of the BA table should be based on network design requirements and actual neighbor cells. Otherwise, the network performance may be degraded. Improper handover, improper cell reselection, or even unsuccessful handover may occur.
CAUTION
The number of neighbor cells in every BA table should be less than 32.
System Information Support to Multiband Network

The network sends the MS system information (system information type 2, 2bis, 2ter, 5, 5bis, and 5ter), enabling network compatibility for the MSs. Thus, the MSs can access the multiband network and perform handover successfully. Huawei 900/1800 system implements full compatibility handling on Phase I and Phase II GSM900 MSs, Phase I and Phase II DCS1800 MSs, and multiband MSs. The system supports system information type 2, 2bis, 2ter, 5, 5bis, and 5ter. The details are as follows:
l
The inter-band frequencies in the neighbor cell list are sent in system information type 2ter and 5ter for the multiband MSs.
Issue 02 (2008-06-30)
5 Multiband Network
l
The intra-band frequencies of GSM900 cells can be encoded in bit map mode in system information type 2 and 5. The Phase I MSs identify only the codes in bit map mode. Thus, the Phase I GSM900 MSs are applicable in the GSM900 cells. After the encoding, the intra-band frequencies in the DCS1800 cells cannot be sent on one BA table. Therefore, the codes of the intra-band frequencies are sent in system information type 2 and 5, and system information type 2bis and 5bis respectively. System information type 2bis/5bis is for single-band DCS1800 MSs and multiband MSs. The equipment in a multiband network is required to support system information type 2ter and 5ter.
ECSC (Early Classmark Sending Control)

ECSC indicates whether the network requires the MS to report MS classmark information (containing Classmark 3) as early as possible. Huawei recommends that you set the parameter as follows:
l l
In a single-band network, set ECSC to 0. In a multiband network, set ECSC to 1 to reduce the signaling traffic.
ECSC is sent in system information type 3.
MBR (Multiband Report)

MBR is the information about six neighbor cells of different bands reported by the MS to the network. The details are as follows:
l
In a single-band network, the MS reports the measurement results of six best neighbor cells within a band. In a multiband network, the signal strength and the frequency band are required in the measurement reports sent by the MS. The purpose is to enable the MS to camp on a certain band preferentially when a handover occurs.
In a multiband network, the propagation loss of the DCS1800 band is greater than that of the GSM900 band. Thus, no DCS1800 cells exist in the list of six best neighbor cells reported by the MS. As a result, the traffic volume absorbed by the DCS1800 network becomes decreased. Through the parameter setting of MBR, the network can require the multiband MS to send the Multi Band Reports of neighbor DCS1800 cells. With different values of MBR, the MS can report the information about neighbor cells of different bands as required when the MS reports the Multi Band Reports of the six best neighbor cells to the network.
Cell Selection
While in idle mode, an MS implements the cell selection and reselection procedures. The network can control these procedures to balance the distribution of traffic volume. When an MS is switched on, it performs cell selection to specify a cell to camp on. The principles of cell selection are as follows:
l l
Preferentially select the cell that is accessible and has high priority. In case the equal priority, select the cell with the highest value of C1. C1 of the selected cell must be greater than zero.
5-14

NOTE
5 Multiband Network
C1 is defined by the formula C1 = RXLEV - RXLEV-ACCESS-MIN - MAX((MS_TXPWR_MAX_CCH - P), 0)).

l l l
The parameter RXLEV indicates the receive level of a neighbor cell that is reported by the MS. For details about RXLEV-ACCESS-MIN, refer to the parameter RXLEV_ACCESS_MIN. For details about MS_TXPWR_MAX_CCH, refer to the parameter MS_TXPWR_MAX_CCH.
In a multiband network, the propagation loss of the DCS1800 band is greater than that of the GSM900 band. To enable the MS to access a DCS1800 cell, set Cell_Bar_Qualify (CBQ) and Cell_Bar_Access (CBA) to control the cell priority. Table 5-5 lists the cell priority for cell selection and reselection. Table 5-5 Cell selection/reselection priority Cell_Bar_Qu alify 0 0 1 1 Cell_Bar_ Access 0 1 0 1 Cell Selection Normal Forbidden Low Low Cell Reselection Normal Forbidden Normal Normal
Generally, the settings of cell selection are as follows:

l l
GSM900 cell: Cell_Bar_Qualify = 1, Cell_Bar_Access = 0. DCS1800 cell: Cell_Bar_Qualify = 0, Cell_Bar_Access = 0.
Because the signal strength in a DCS1800 cell is usually weaker than that in a GSM900 cell, the priority of the DCS1800 cell is set to Normal, and the priority of the GSM900 cell is set to Low. Thus, a multiband MS preferentially selects the DCS1800 cell.
Cell Reselection
Upon completion of cell selection, the MS camps on the selected cell and starts to measure the receive levels of BCCH carriers for the six strongest non-serving carriers. In addition, the MS extracts various system information and control messages from the six best neighbor cells. When certain conditions are met, an MS leaves the serving cell and camps on another cell. This procedure is called cell reselection. The conditions for cell reselection include many factors such as cell priority, cell accessibility, and radio channel quality. The reselection criterion C2 indicates the channel quality standard. The value of C2 is defined by the following formula:
l l
If PT < 31, C2 = C1 + CRO(2dB) - TO x H (PT - T). If PT = 31 (all 1s), C2 = C1 - CRO(2dB).

Issue 02 (2008-06-30)
5 Multiband Network
NOTE
The meaning of function H(x) is:

l l
If x < 0, (PT - T < 0), H(x) = 0. If x 0, (PT - T 0), H(x) = 1.
The principle for cell reselection is to select the cell with the highest value of C2 as the serving cell. The value of C2 is equal to C1 plus an additional offset parameter. The offset parameter is used to enable the MS to preferentially camp on certain cells or to hinder the MS from camping on certain cells. The purpose is to balance the traffic volume. PI (Cell Reselect Parameters Indication) notifies the MS whether to use C2 as the parameter of cell reselection and whether associated parameters in the C2 formula exist. The parameters in the C2 formula are as follows (except C1):
l
CRO(2dB) : an offset applied to the C2 reselection criterion. TO (Cell Reselect Temporary Offset): an temporary offset to the C2 reselection criterion. This offset is valid only for a certain duration. The duration is specified by PT.
l l
PT(s) Timer T (internal parameter) The initial value is zero. When a cell is placed by the MS on the list of six strongest carriers, T is started from zero for the cell with an accuracy of a TDMA frame (about 4.62 ms). When the cell is removed by the MS from the list of six strongest carriers, T for the cell is reset.
PI and associated parameters in the C2 formula can be obtained from system information type 4, 7, and 8. ACS notifies the MS of the location to extract associated parameters for cell reselection. The details are as follows:
l
If the MS finds that the value of C2 for a neighbor cell (being in the same location area as the serving cell) exceeds the value of C2 for the serving cell for a period of 5 seconds, the MS initiates a cell reselection and camps on the neighbor cell. If the MS finds that the value of C2 for a neighbor cell (being in a different location area) exceeds the value of C2 for the serving cell by at least CELL_RESELECT_HYSTERESIS dB as defined by the BCCH data from the current serving cell, for a period of 5 seconds, the MS initiates a cell reselection and camps on the neighbor cell.
CAUTION
Cell reselection caused by C2 does not take place if there is a cell reselection within the previous 15 seconds.
Parameter Reconfiguration for Cell Reselection

To ensure the network performance, you need to reconfigure certain parameters for cell reselection based on the practical application.

l
5 Multiband Network
For a cell with high traffic volume or with low service quality, try to prevent the MSs from camping on the cell. The parameter settings are recommended as follows:
Set PT(s) to 31 and reduce the value of C2 for the cell, making it difficult for an MS to camp on the cell. In addition, properly set CRO(2dB). In this case, C2 = C1 - CRO(2dB). A high value of CRO(2dB) indicates that it is difficult for an MS to camp on the cell.
For a cell with small traffic volume or with low equipment utilization ratio, try to enable the MS to camp on the cell. The parameter settings are recommended as follows:
Properly set CRO(2dB). In this case, C2 = C1 + CRO(2dB) - TO x H (PT(s) - T). A high value of CRO(2dB) indicates that it is easy for an MS to camp on the cell. The CRO(2dB) can be set in the range 0 dB to 20 dB. Set TO to be equal to or slightly higher than CRO(2dB). Set PT(s) to 0 (20 seconds) or 1 (40 seconds).
For a cell with medium traffic volume, set CRO(2dB) to 0 and therefore C2 is equal to C1. No offset is applied to C2.
CAUTION
l
The value of the CRO(2dB) should always be less than 25 dB to avoid any uncertainties to the network. The parameter settings are cell-specific. The value of C2, however, is closely associated with neighbor cells. Therefore, the relation between the serving cell and neighbor cells must be considered for parameter configuration.
5.3.7 Traffic Guiding Strategy

This describes the traffic guiding strategy of the multiband network. To meet the increasing requirements on high capacity and quality of the multiband network, the DCS1800 band is required to absorb or share the traffic volume at a maximum extent.
Principles of the Traffic Guiding Strategy

The principles of the traffic guiding strategy are as follows:
l
In initial stage of network construction, the DCS1800 cells should absorb the traffic volume as much as possible. In hot spots of the DCS1800 network, continuous coverage should be implemented. When the number of multiband users reaches a certain level, every band should share the traffic volume to reduce handovers.
l l
The telecom operator can implement different traffic control strategies by adjusting related parameters in real time. The traffic control strategy also depends on the MS state. The channel assignment strategies include:
l
While in idle mode, an MS implements the cell selection and cell reselection procedures. When these procedures are performed, system parameters can be set to make a DCS1800 cell have a high priority or a favorable comparison value of the neighbor cell measurement.
Issue 02 (2008-06-30)
5 Multiband Network
Therefore, the DCS1800 cell tends to be the serving cell of multiband users, and the MS tends to camp on the DCS1800 cell before the call establishment procedure.
l
While an MS is in a call establishment procedure, the traffic volume assignment can be adjusted through directed retry. While an MS is in conversation mode, cell layer and cell level are set to make the traffic volume flow to the DCS1800 cell with low layer and high level. In additional, multiband traffic handover is used to maintain the balance of the cell traffic load.
Cell Selection and Reselection

C1 indicates the quality of the radio channel. A high value of C1 indicates a good channel quality. Set CRO, TO, and PT. Then, calculate the value of C2. C2 is used for cell reselection to specify the target cell. Through the above parameter configuration, you can make C2 of the DCS1800 cell higher than that of the GSM900 cell. Therefore, even if the signal strength of the DCS1800 cell is weaker than that of the GSM900 cell, the MS can still reselect the DCS1800 cell.
NOTE
For details about the calculation for C1 and C2, refer to 5.3.6 Technical Principles.
5.3.8 Enhanced Dual-Band Network

This describes the enhanced dual-band network that is an improvement on the existing dualband network. In the enhanced dual-band network, two co-sited cells with different coverage areas are logically formed into a cell group. One is an overlaid subcell and the other is an underlaid subcell. The enhanced dual-band network algorithm enables the channel resource sharing and the cell load balance between the two cells in a cell group. The handover decision for the overlaid subcell and the underlaid subcell in the cell group is based on the MR. Figure 5-5 shows the cell structure of the enhanced dual-band network. Figure 5-5 Enhanced dual-band cell
Cell group Cell A Overlaid subcell Cell B Underlaid subcell Cell group
Cell A Overlaid subcell Cell B Underlaid subcell
Distance
Optimized Assignment for Access

In the case of the MS access to the underlaid subcell, the BSC determines whether the RX level of the MS is equal to or higher than the overlaid subcell level when the underlaid subcell load is higher than UL Subcell General OverLoad Threshold(%). If the RX level of the MS is equal to or higher than the overlaid subcell level and if the overlaid subcell load does not
5 Multiband Network
overflow, the BSC assigns to the MS the channel in the overlaid subcell and hands over the MS to the overlaid subcell through a directed retry procedure. Otherwise, the MS is assigned with the channel in the underlaid subcell.
l
If the congestion occurs in the underlaid subcell, the queuing and preemption procedures are performed. If the MS still cannot be assigned with a channel, the MS performs a cell reselection.
In the case of the MS access to the overlaid subcell, the BSC preferentially assigns to the MS the channel in the underlaid subcell when the underlaid subcell load is lower than UL Subcell Lower Load Threshold(%). Otherwise, the MS is assigned with the channel in the overlaid subcell.
l
If the congestion occurs in the overlaid subcell, the queuing and preemption procedures are performed. If the MS still cannot be assigned with a channel, the MS performs a cell reselection.
Handover due to High Underlaid Subcell Load

When the underlaid subcell load is higher than UL Subcell General OverLoad Threshold (%), a certain number of users should be handed over to the overlaid subcell for the load balance. Thus, the cell capacity is maximized. The MSs near the BTS are preferentially handed over to the overlaid subcell to suppress the overlaid inter-cell interference. This also minimizes the occurrences of handovers from the overlaid subcell to the underlaid subcell due to the movement of users.
Handover due to Low Underlaid Subcell Load

When the underlaid subcell load is lower than UL Subcell Lower Load Threshold(%), the MSs far away from the BTS should be handed over to the underlaid subcell to improve the channel utilization in the underlaid subcell and to suppress the interference of the overlaid subcell to other cells.
Call Movement Handover in the Overlaid Subcell

For the call on the edge of the overlaid subcell, a call drop tends to occur if the handover is not performed on the MS. Call movement handover enables the MS to be handed over to the best candidate cell (ranked first in the BA table) that is not necessarily the underlaid subcell in the cell group.
5.4 Implementation
This describes how to configure, verify, and deactivate the multiband network. 5.4.1 Configuring the Multiband Network This describes how to configure the multiband network on the BSC6000 Local Maintenance Terminal. 5.4.2 Verifying the Multiband Network This describes how to verify the multiband network. You can check whether an MS uses the multiband function during a call. 5.4.3 Deactivating the Multiband Network
5 Multiband Network
This describes how to deactivate the multiband network on the BSC6000 Local Maintenance Terminal. 5.4.4 Configuring the Enhanced Dual-Band Network This describes how to configure the enhanced dual-band network on the BSC6000 Local Maintenance Terminal.
5.4.1 Configuring the Multiband Network

This describes how to configure the multiband network on the BSC6000 Local Maintenance Terminal.
Prerequisite
The TRXs configured for the BTS support corresponding frequency bands.
Procedure
Step 1 Add a cell. 1. 2. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target BTS and then choose Add Cell from the shortcut menu. In the displayed dialog box, select the target BTS in the Cell View list box, and then click Add Cell. A dialog box is displayed, as shown in Figure 5-6. Specify related parameters of the new cell and Frequency Band.
NOTE
The cell bands supported by Huawei BSC are GSM900, DCS1800, GSM900&DCS1800, PCS1900, and GSM850. The P-GSM900 band, E-GSM900 band, and R-GSM900 band are referred to as the GSM900 band.
Figure 5-6 Add New Cell dialog box
Step 2 Configure the cell attributes. 1. 2. 3.

5-20
Click OK in Figure 5-6 to return to the Add Cell dialog box. Select the new cell in the Cell View list box, and then click Next. Click Set Cell Properties. A dialog box is displayed, as shown in Figure 5-7.
5 Multiband Network
Set Cell Layer and Cell Priority. Figure 5-7 Set Cell Attributes dialog box
4.
Click Frequency Config. A dialog box is displayed, as shown in Figure 5-8. Select proper frequencies for the new cell.
Issue 02 (2008-06-30)
5-21
5 Multiband Network
Figure 5-8 Set Cell Frequency dialog box
5. 6.
Click OK to return to the dialog box shown in Figure 5-7. Click TRX Config. In the displayed dialog box, click the Frequecy Attributes tab and then double-click a frequency in the Available Frequencies list box to add the frequency to the Assigned Frequencies list box. See Figure 5-9. Figure 5-9 Configure TRX Attributes dialog box
7.
Click OK to return to the dialog box shown in Figure 5-7. The frequency assignment is complete.
5-22
Issue 02 (2008-06-30)
5 Multiband Network
Step 3 Set parameters related to the multiband network. 1. In the dialog box shown in Figure 5-7, click Idle Mode. In the displayed dialog box, click Advanced and then click the Idle Parameter tab. See Figure 5-10. Set the parameters such as Cell_Bar_Access, Cell_Bar_Qualify, CRH, PI, NCC Permitted, CRO (2dB), ACS, TO, and PT(s). Figure 5-10 Set Idle Parameter dialog box
2. 3.
Click OK to return to the dialog box shown in Figure 5-7. Click Call Control in the dialog box shown in Figure 5-7. A dialog box is displayed, as shown in Figure 5-11. Set ECSC and MBR.
Issue 02 (2008-06-30)
5-23
5 Multiband Network
Figure 5-11 Set Call Control Parameter dialog box
4. 5.
Click OK to return to the dialog box shown in Figure 5-7. Click Handover Data in Figure 5-7. A dialog box is displayed, as shown in Figure 5-12. Set the handover parameters related to the multiband network.
5-24
Issue 02 (2008-06-30)
5 Multiband Network
Figure 5-12 Set Handover Parameter dialog box
6.
After the parameter setting is complete, click OK to return to the upper-level menus until the whole operation is complete.
----End
5.4.2 Verifying the Multiband Network

This describes how to verify the multiband network. You can check whether an MS uses the multiband function during a call.
Procedure
Step 1 Use an MS supporting multiple bands to perform dialing tests, moving around within the coverage area of the BTS. Step 2 Check the serving cells and call accesses of the MS in different coverage area of the BTS. ----End
5.4.3 Deactivating the Multiband Network

This describes how to deactivate the multiband network on the BSC6000 Local Maintenance Terminal.
5 Multiband Network
Context
To adjust the frequency bands supported by a cell, you need to delete the cell, and then configure new frequency bands and network parameters based on requirements.
Procedure
Step 1 Delete the existing cell. 1. 2. 3. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target cell and then choose Delete Cell from the shortcut menu. Double-click the target cell in the Cell View list box to add the cell to the Cells to be deleted list box. Click Finish. The deletion is complete.
Step 2 Add a cell and configure parameters related to the new cell. For details, refer to the operations in GUI mode in 5.4.1 Configuring the Multiband Network. ----End
5.4.4 Configuring the Enhanced Dual-Band Network

This describes how to configure the enhanced dual-band network on the BSC6000 Local Maintenance Terminal.
Context
The procedure for configuring the enhanced dual-band network is the same as that for 5.4.1 Configuring the Multiband Network.
Procedure
Step 1 Configure the enhanced dual-band cell. When you configure the cell attributes, set Cell Type to Enhance Dual Band cell, as shown in Figure 5-13.
5-26
Issue 02 (2008-06-30)
5 Multiband Network
Figure 5-13 Configuring cell attributes
Step 2 Configure the handover data for the enhanced dual-band network. Click Handover Data as shown in Figure 5-13. A dialog box is displayed. Click Advanced and then select the Enhance dual band data tab to configure the handover data, as shown in Figure 5-14.
Issue 02 (2008-06-30)
5-27
5 Multiband Network
Figure 5-14 Configuring data for the enhanced dual-band network
----End

This lists the alarms and counters related to the multiband network.
Alarms
Table 5-6 lists the alarms related to the multiband network. Table 5-6 Alarms related to the multiband network Alarm ID 2180 2302 2586 3580 4168 5314 Alarm Name TRX Band Mismatch ARFCN CDU Band Mismatch ARFCN Alarm PBU Band Mismatch ARFCN Alarm DRU Band Mismatch ARFCN Alarm ARFCN TRX Type Mismatch CDU Band Mismatch ARFCN Alarm
Counters
Table 5-7, Table 5-8, Table 5-9, and Table 5-10 list the performance counters related to the multiband network.
5 Multiband Network
Table 5-7 Incoming internal inter-cell handover measurement per cell Counter H3200Y H3200Z H3209Y H3209Z H3210Y H3210Z H3217Y H3217Z H3220Y H3220Z H3229Y H3229Z Description Incoming Internal Inter-Cell Handover Requests (SDCCH) (900/850-1800/1900) Incoming Internal Inter-Cell Handover Requests (SDCCH) (1800/1900-900/850) Incoming Internal Inter-Cell Handover Requests (TCH) (900/850-1800/1900) Incoming Internal Inter-Cell Handover Requests (TCH) (1800/1900-900/850) Incoming Internal Inter-Cell Handover Responses (SDCCH) (900/850-1800/1900) Incoming Internal Inter-Cell Handover Responses (SDCCH) (1800/1900-900/850) Incoming Internal Inter-Cell Handover Responses (TCHF) (900/850-1800/1900) Incoming Internal Inter-Cell Handover Responses (TCHF) (1800/1900-900/850) (Failed Incoming Internal Inter-Cell Handovers (SDCCH) (900/850-1800/1900) (Failed Incoming Internal Inter-Cell Handovers (SDCCH) (1800/1900-900/850) (Failed Incoming Internal Inter-Cell Handovers (TCH) (900/850-1800/1900) (Failed Incoming Internal Inter-Cell Handovers (TCH) (1800/1900-900/850)
Table 5-8 Outgoing internal inter-cell handover measurement per cell Counter H3101Y H3101Z H3111Y H3111Z Description Outgoing Internal Inter-Cell Handover Requests (Directed Retry) (900/850-1800/1900) Outgoing Internal Inter-Cell Handover Requests (Directed Retry) (1800/1900-900/850) Outgoing Internal Inter-Cell Handover Commands (Directed Retry) (900/850-1800/1900) Outgoing Internal Inter-Cell Handover Commands (Directed Retry) (1800/1900-900/850)
Issue 02 (2008-06-30)
5-29
5 Multiband Network
Counter H3121Y H3121Z
Description Failed Outgoing Internal Inter-Cell Handovers (Directed Retry) (900/850-1800/1900) Failed Outgoing Internal Inter-Cell Handovers (Directed Retry) (1800/1900-900/850)
Table 5-9 Incoming external inter-cell handover measurement per cell Counter H3400Y H3400Z H3409Y H3409Z H3410Y H3410Z H3417Y H3417Z H3418Y H3418Z H3420Y H3420Z H3429Y H3429Z Description Incoming External Inter-Cell Handover Requests (SDCCH) (900/850-1800/1900) Incoming External Inter-Cell Handover Requests (SDCCH) (1800/1900-900/850) Incoming External Inter-Cell Handover Requests (TCH) (900/850-1800/1900) Incoming External Inter-Cell Handover Requests (TCH) (1800/1900-900/850) Incoming External Inter-Cell Handover Responses (SDCCH) (900/850-1800/1900) Incoming External Inter-Cell Handover Responses (SDCCH) (1800/1900-900/850) Incoming External Inter-Cell Handover Responses (TCHF) (900/850-1800/1900) Incoming External Inter-Cell Handover Responses (TCHF) (1800/1900-900/850) Incoming External Inter-Cell Handover Responses (TCHH) (900/850-1800/1900) Incoming External Inter-Cell Handover Responses (TCHH) (1800/1900-900/850) Failed Incoming External Inter-Cell Handovers (SDCCH) (900/850-1800/1900) Failed Incoming External Inter-Cell Handovers (SDCCH) (1800/1900-900/850) Failed Incoming External Inter-Cell Handovers (TCH) (900/850-1800/1900) Failed Incoming External Inter-Cell Handovers (TCH) (1800/1900-900/850)
5-30
Issue 02 (2008-06-30)
5 Multiband Network
Table 5-10 Outgoing external inter-cell handover measurement per cell and dual-band handover measurement per cell Counter H3301Y H3301Z H3311Y H3311Z H3321Y H3321Z K3170 K3173 Description Outgoing External Inter-Cell Handover Requests (Directed Retry) (900/850-1800/1900) Outgoing External Inter-Cell Handover Requests (Directed Retry) (1800/1900-900/850) Outgoing External Inter-Cell Handover Commands (Directed Retry) (900/850-1800/1900) Outgoing External Inter-Cell Handover Commands (Directed Retry) (1800/1900-900/850) Failed Outgoing External Inter-Cell Handovers (Directed Retry) (900/850-1800/1900) Failed Outgoing External Inter-Cell Handovers (Directed Retry) (1800/1900-900/850) Dual-Band Handover Requests Successful Dual-Band Handovers
5.6 References
l
GSM 04.08 "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification"
GSM 05.05 (prETS 300 577) "Radio transmission and reception" GSM 05.08 (prETS 300 578) "Radio subsystem link control"
Issue 02 (2008-06-30)
5-31
6 Power Control
6
About This Chapter
Power Control
6.1 Overview This describes the definition and purposes of the power control. Power control is used to control the transmit power on radio links to improve transmission quality and reduce channel interference. 6.2 Availability This lists the NEs and software required for the implementation of power control. 6.3 Technical Description This describes the technical aspects of the power control, such as classification, procedure, and algorithm of the power control. 6.4 Capabilities None 6.5 Implementation This describes how to activate and configure the power control. 6.6 Maintenance Information This describes the counters related to power control. 6.7 References
Issue 02 (2008-06-30)
6-1
6 Power Control
6.1 Overview
This describes the definition and purposes of the power control. Power control is used to control the transmit power on radio links to improve transmission quality and reduce channel interference.
Definition
Power control is an important method for radio link control. The BSC decides whether the transmit power required by the MS and the BTS should be adjusted, based on the expected value, measurement reports on uplink/downlink receive level and receive quality sent by the BTS. The principles of power control are as follows:
l
If receive level or receive quality is higher than the expected value, the power is reduced to some extent. If receive level or receive quality is lower than the expected value, the power is increased to some extent. Improve the accuracy and effectiveness of the power control on the overall basis of receive level and receive quality.
Purposes
Power control is used to control the transmit power required by MS or BTS while maintaining the quality of the radio links. When the transmit power levels of the MS or BTS are minimized, interference to co-channel users is reduced.
Terms
Terms Call connection Definition 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 procedure, including system information, paging, immediate assignment, assignment, handover, location update, and A interface circuit management. Maximum transmit power
Pn

Acronyms and Abbreviations MS BSC
6-2
Full Spelling Mobile Station Base Station Controller
Issue 02 (2008-06-30)
6 Power Control
Acronyms and Abbreviations MR BTS CIR FS HS
Full Spelling Measure report Base Transceiver Station Carrier to Interference Ratio Full-rate Speech Half-rate Speech
6.2 Availability
This lists the NEs and software required for the implementation of power control.
NEs Involved
Table 6-1 lists the NEs involved power control. Table 6-1 NEs involved in power control MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 6-2 lists the versions of GBSS products that support power control. Table 6-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C
Issue 02 (2008-06-30)
Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases
6-3
6 Power Control
Product BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM
Version BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
None

This describes the technical aspects of the power control, such as classification, procedure, and algorithm of the power control. 6.3.1 Classification This describes the classification of power control. The power control is classified into uplink power control and downlink power control, namely, MS power control and BTS power control. 6.3.2 Procedure for Power Control This topic describes the procedure of power control. The procedure consists of three measurement report 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. 6.3.3 Huawei II Power Control Algorithm This describes the procedure and features of Huawei II power control algorithm. 6.3.4 Huawei III Power Control Algorithm This describes the procedure and features of Huawei power control algorithm.
6.3.1 Classification
This describes the classification of power control. The power control is classified into uplink power control and downlink power control, namely, MS power control and BTS power control. 6.3.1.1 Power Control for MS This describes the power control for the MS. If the transmit power of the MS is controlled properly, the BTS can maintain stable receive levels and the co-channel interference is minimized. 6.3.1.2 Power Control for BTS This describes the power control for the BTS. If the transmit power of the BTS is controlled properly, the MS can maintain stable receive levels, the co-channel interference is minimized, and the power consumption of the BTS is reduced.
6-4
Issue 02 (2008-06-30)
6 Power Control
Power Control for MS

This describes the power control for the MS. If the transmit power of the MS is controlled properly, the BTS can maintain stable receive levels and the co-channel interference is minimized. The MS power control is performed at two phases: initial adjustment phase and stable adjustment phase. The differences of power control between the initial adjustment phase and the stable adjustment phase lie in the expected uplink receive level and receive quality, and filter length. Moreover, only downward power adjustment is performed at the initial adjustment phase. 1. Initial adjustment phase Initial adjustment takes place when a call connection is established. When a call connection occurs, the MS accesses to the network at the power set by MS_TXPWR_MAX_CCH. If the MS does not support a power level, it transmits at the proximate supported power level. As the BTS supports multiple calls simultaneously, it must minimize the receive level of a new call to ensure the quality of other calls. In addition, the strong interference from one cell has impacts on the QoS of the calls in other cells. For the classmark 3 MS that supports DCS1800, the MS accesses to the network with the power set by MS_TXPWR_MAX_CCH and Power Deviation when a call connection occurs. If the filtered level is lower than the expected level, power control is not performed. If the filtered level is not lower than the expected level, power control is performed according to the following regulations:
l
Power to be decreased = (initial power expected initial power) x compensation factor of UL path loss Power after adjustment = current power power to be decreased
The purpose of power adjustment in the initial phase is to decrease the transmit power of the MS as soon as possible until measurement reports on stable transmit power are obtained. Then, the MS can adjust its transmit power based on the power control algorithms for stable power adjustment. 2. Stable adjustment phase After the MS accesses to the network and the call lasts for a certain duration, and after the BTS receives a certain number of UL measurement reports, the BTS performs interpolation and filtering to obtain the actual UL receive level and receive quality, which are compared with the standard UL receive level and receive quality. According to the power control algorithms, the BTS calculates the power level that the MS should adjust. If the calculated power level is different from the transmit power of the MS and meets application restrictions (such as the step restrictions of power adjustment, the restrictions of the transmit power range for the MS), the BTS sends a power control command to the MS. The UL power adjustment enables the actual UL receive level and receive quality to be close to the standard UL receive level and receive quality. The purpose of interpolation and filtering is to handle the lost measurement reports and to ensure the stability of power control algorithms.
Power Control for BTS

This describes the power control for the BTS. If the transmit power of the BTS is controlled properly, the MS can maintain stable receive levels, the co-channel interference is minimized, and the power consumption of the BTS is reduced.
6 Power Control
The power control for BTS is optional. The principle of the power control for BTS is similar to that of the power control for MS. The power control for BTS, however, is performed at only one phase: stable adjustment phase. When the received measurement reports are insufficient for filtering, power control is not performed. Only when sufficient measurement reports are received, the power control for BTS is performed. The power control for the BTS consists of static power control and dynamic power control.
l
Static power control The static power has 11 levels numbered from 0 to 10. The difference between two adjacent static power levels is 2 dBm. For example, the maximum transmit power of the BTS is 46 dBm, and the power values corresponding to the static power levels are listed as Table 6-3. Table 6-3 Static power level Static Power Level Power (dBm) 0 46 1 44 2 42 3 40 4 38 5 36 6 34 7 32 8 30 9 28 10 26
NOTE
You can set the static power level by setting the Power Level.
l
Dynamic power control Dynamic power control refers to the fine tuning on power based on static power control. Based on a certain static power (Pn) as the maximum value, the dynamic power has 15 levels with the step 2 dBm by tuning the static power value downwards. Table 6-4 lists the dynamic power values in case that Pn is equal to 42. Table 6-4 Dynamic power level Dynam ic Power Level Power (dBm)
0 4 2
1 4 0
2 3 8
3 3 6
4 3 4
5 3 2
6 3 0
7 2 8
8 2 6
9 2 4
1 0 2 2
1 1 2 0
1 2 1 8
1 3 1 6
1 4 1 4
1 5 1 2
NOTE
When the maximum dynamic power cannot meet the requirements, the static power level should be accordingly adjusted to increase the maximum dynamic power Pn.
6.3.2 Procedure for Power Control

This topic describes the procedure of power control. The procedure consists of three measurement report periods. In the first period, the BTS sends the MS a power control command
6 Power Control
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 6-1 shows the procedure for the power control. Figure 6-1 Procedure for Power Control
SACCH is sent in the 12th frame of the 26 multiframe SA 0 SACCH MR period: 4x26=104 frames (480 ms) SA 3 SA 0 SA 1 SA2 SA 3
SA 1 SA 2 SA 3 SA 0 SA 1 SA 2 MS starts to use new power and TA
BTS sends power control and TA command in the header of SACCH
MS starts to send the MR in previous multiframe
MS receives SACCH message block
MS starts to construct the header of new SACCH to report the new TA and power control information
BTS receives the MR
1.
The first measurement report period The BTS sends a power adjustment and TA command in the SACCH header. On receiving the command, the MS starts to perform power control in the second measurement report period.
2.
The second measurement report period The MS starts to perform power control as follows:
l
If the adjustment step is set to 16 dB, 104 frames (480 ms, a measurement report period) are required for the power adjustment. If the step is set to 32 dB, two measurement report periods are required for the power adjustment.
NOTE
The MS changes to the new level at a maximum rate of one nominal 2 dB power control step every 13 frames (60 ms).
3.
The third measurement report period The current transmit power (actually used by the MS for the last burst of the previous SACCH period) is saved and is reported to the BTS in the next SACCH uplink measurement report.
6.3.3 Huawei II Power Control Algorithm

This describes the procedure and features of Huawei II power control algorithm. 6.3.3.1 Procedure for Huawei II Power Control Algorithm This describes the procedure for Huawei II power control algorithm, including MR compensation, prediction filtering, adjusting the power step based on the receive level/quality, and power control performance.
6 Power Control
6.3.3.2 Features of Huawei II Power Control Algorithm This describes the features of Huawei II power control algorithm. The features include MR compensation, prediction filtering, dual-threshold power control algorithm, variable step power control, adaptive power control, bad quality signal strength upper threshold adjustment, and detachment of uplink and downlink power control.
Procedure for Huawei II Power Control Algorithm

This describes the procedure for Huawei II power control algorithm, including MR compensation, prediction filtering, adjusting the power step based on the receive level/quality, and power control performance. Figure 6-2 shows the procedure for Huawei II power control algorithm. Figure 6-2 Procedure for Huawei II Power Control Algorithm
Start
Compensate MRs (Compensate level)
MR prediction filtering
Calculate power adjustment step based on receive level Calculate power adjustment step based on receive quality Calculate power adjustment step based on both receive level and receive quality
Perform power control
End
1.
6-8
Power control based on the receive level

6 Power Control
If UL/DL RX_LEV Upper Threshold < UL/DL receive level < UL/DL RX_LEV Lower Threshold, power control is not required. If the condition is not met, power control is required.
l
If the receive level is less than UL/DL RX_LEV Lower Threshold, the power needs to be increased. Power increment = (upper threshold + lower threshold)/2 receive level. If the value exceeds the value of MAX Up Adj. PC Value by RX_LEV, take the value of MAX Up Adj. PC Value by RX_LEV instead.
If the receive level is greater than UL/DL RX_LEV Upper Threshold, the power needs to be decreased. Power decrement = receive level (upper threshold + lower threshold)/2. This value must be within the maximum power control range of the corresponding quality zone. If the value exceeds the range, take the maximum value instead.
2.
Power control based on the receive quality If UL/DL Qual Upper Threshold < UL/DL receive quality < UL/DL Qual Lower Threshold, power control is not required. If the condition is not met, power control is required.
l
If the receive quality is equal to or greater than UL/DL Qual Lower Threshold, the power needs to be increased. Power increment = MAX Up Adj. PC Value by Qual If the receive quality is less than UL/DL Qual.Upper Threshold, the power needs to be decreased. Power decrement = MAX Down Adj. PC Value by Qual
NOTE
The level adjusted on the basis of the receive quality is a definite value, while the level adjusted on the basis of the receive level is calculated using a formula.
3.
Comprehensive power control decision Table 6-5 describes the comprehensive power control decision. Table 6-5 Comprehensive power control decision table Level and Quality Good level and good quality Good level and poor quality Good level and normal quality Poor level and good quality Poor level and poor quality Power Control Based on Receive Level AdjStep_Lev Power Control Based on Receive Quality AdjStep_Qul Comprehensive Power Control MAX (AdjStep_Lev,AdjStep _Qul) No action AdjStep_Lev AdjStep_Lev MAX(AdjStep_Lev, AdjStep_Qul)
6-9
AdjStep_Lev AdjStep_Lev AdjStep_Lev AdjStep_Lev
AdjStep_Qul No action AdjStep_Qul AdjStep_Qul
Issue 02 (2008-06-30)
6 Power Control
Level and Quality Poor level and normal quality Normal level and good quality Normal level and poor quality Normal level and normal quality
Power Control Based on Receive Level AdjStep_Lev No action No action No action
Power Control Based on Receive Quality No action AdjStep_Qul AdjStep_Qul No action
Comprehensive Power Control AdjStep_Lev AdjStep_A AdjStep_B No action
The parameters in the table are described as follows:

l
AdjStep_Lev Adjusting the receive level AdjStep_Qul Adjusting the receive quality No action No adjustment AdjStep_A
When Uplink (Downlink) receive level AdjStep_Qul < UL/DL RX_LEV Lower Threshold, AdjStep_A = 0. Power control is not required. When Uplink (Downlink) receive level AdjStep_Qul UL/DL RX_LEV Upper Threshold, AdjStep_A = AdjStep_Qul.
The purpose is to avoid unnecessary power control in case of normal level and good quality. If the power is adjusted in case of normal level and good quality, the level becomes poor and another power control procedure is required. Thus, power control is performed frequently.
l
AdjStep_B
When AdjStep_Qul + Uplink (Downlink) receive level > UL/DL RX_LEV Upper Threshold, AdjStep_B = UL/DL RX_LEV Upper Threshold UL/DL receive level. Thus, the adjusted level does not exceed the level upper threshold. When AdjStep_Qul + UL/DL receive level UL/DL RX_LEV Lower Threshold, AdjStep_B = AdjStep_Qul.
The purpose is to avoid unnecessary power control in case of normal level and poor quality. If the power is adjusted in case of normal level and poor quality, the level becomes good and another power control procedure is performed. Thus, power control is performed frequently.
NOTE
In Table 6-5, indicates increasing power, and indicates decreasing power.
6-10
Issue 02 (2008-06-30)
6 Power Control
Features of Huawei II Power Control Algorithm

This describes the features of Huawei II power control algorithm. The features include MR compensation, prediction filtering, dual-threshold power control algorithm, variable step power control, adaptive power control, bad quality signal strength upper threshold adjustment, and detachment of uplink and downlink power control.
MR Compensation
During power control decision, the BSC performs weighted filtering on the values of the received level and of the received quality in several history measurement reports. The measurement reports may be obtained by the BTS/MS at different transmit power. To ensure the accuracy of the values for filtering, the values in the history measurement reports that are obtained at a different transmit power from the current power must be compensated. If the currently interpolated MRs and the compensated MRs are filtered together, the power control decision can be more effective. You can set the MR.Compensation Allowed to determine whether measurement report compensation is performed. The measurement report compensation is calculated as follows:
l
If the reported power level of the MS (BTS) is greater than last time (that is, power level decreases), the uplink (downlink) receive level in all the MR is subtracted from the variation value of the power of the MS (BTS) (variation of power level x 2 dBm). If the reported power level of the MS (BTS) is lower than last time (that is, power level increases), the uplink (downlink) receive levels in all the MRs are added by the variation value of the power of the MS (BTS) (added power level x 2 dBm).
NOTE
The measurement report compensation is for level instead of quality.
Prediction Filtering
The power control decision is performed based on the average filter value in history measurement reports. That is, the average filter value is used as a reference for the current receive level. There is an interval between power control decision and power adjustment, which delays the power adjustment. Therefore, prediction filtering is added. The principle of prediction filtering is that the variation of receive level and receive quality maintains continuity in a short period of time. Prediction filtering samples N MRs, applies weighting filter to them, and gives prediction on 03 MRs from the current time onwards. Generally, the interval between power control decision and power adjustment is three MRs (about 1.5s). Prediction filtering can ensure the accuracy of prediction. Power control decision is implemented by filtering the predicted MR along with the interpolated MR or compensated MR. Prediction filtering enables the MR that power control decision is based on to accurately reflect the radio environment when power adjustment occurs. Thus, the hysteresis for power adjustment can be minimized.
NOTE
Power control algorithm is applied only to the receive level. If the filter length is less than 5 or the number of predicted MRs is 0, the mean value filtering is applied.
Issue 02 (2008-06-30)
6-11
6 Power Control
Dual-Threshold Power Control Algorithm

Power control is used for the purpose of achieving good speech quality with low receive level. Because of the radio link instability and external interference, the transmit power cannot be too low. Therefore, Huawei adopts the strategy of dual-threshold power control algorithm. Dualthreshold power control algorithm adopts the following strategies:
l
Adjusting the power step based on the receive level The threshold of the receive level is set to a dual threshold. Variable step for power control is used for fast and accurate power control. The current receive quality is also considered for determining power adjustment step.
Adjusting the power step based on the receive quality The changing of receive quality is related to interference. The major interference in GSM is the co-channel interference during frequency reuse. When the power of a call is increased, co-channel interference is exerted on another call. The following case should be avoided: If the power of the first call is increased, the interference in a second call is enhanced so that the receive quality of the second call gets poor. To get a better quality, the transmit power of the second call may be increased. By analogy, the group effect may occur. The threshold of the receive quality is also set to a dual threshold. If the receive quality is within the threshold band, adjusting the transmit power is not required. If the receive quality is beyond the threshold band, adjusting the transmit power is required. For the power adjustment caused by quality-related reasons, use a fixed step to avoid oscillation.
Adjusting the power control based on the receive level and receive quality The effect on power control of both level and quality is considered. On one hand, the requirements of both level and quality are met to the maximum extent. On the other hand, in case difference or opposite requirements for level and quality, the stability of the algorithm should be fully considered to prevent an unstable adjustment procedure.
Variable Step Power Control

Variable step power control is achieved according to the following regulations:
l
When the difference between the current level and quality and the expected level and quality is big, adjust power with long step. When the difference between the current level and quality and the expected level and quality is small, adjust power with short step.
Adaptive Power Control

Adaptive power control changes the power control strategy based on the communication environment, making the power control effective and stable. The adaptive power control consists of the following two elements:
l
Automatically changing the maximum variable step of the power control based on the communication environment. Adopting corresponding power control strategy based on the communication environment.
Bad Quality Signal Strength Upper Threshold Adjustment

When you use the dual-threshold power control algorithm, do as follows:

l
6 Power Control
When the receive quality is higher than the UL/DL QUAL.Bad Trig Threshold, increase the UL/DL RX_LEV Upper Threshold value and add UL/DL Qual.Bad UpLEVDiff. When the receive quality is good, set the UL/DL RX_LEV Upper Threshold to a small value to reduce the transmit power of the BTS and MS. When the receive quality is bad, set the UL/DL RX_LEV Upper Threshold to a great value to improve the speech quality.
Detachment of Uplink and Downlink Power Control

The detached configuration of power control step in upward and downward directions enables flexible and fast power control based on the actual situation on the network. When the uplink (downlink) signal quality or the receive quality becomes poor immediately, the upward power control can be performed quickly. Thus call drop can be avoided.
6.3.4 Huawei III Power Control Algorithm

This describes the procedure and features of Huawei power control algorithm. 6.3.4.1 Procedure for Huawei III Power Control Algorithm This describes the procedure for Huawei III power control algorithm, including processing lost measurement reports, filtering, calculating FH gain, calculating power adjustment step based on the FH gain, and performing power control. 6.3.4.2 Features of Huawei III Power Control Algorithm This describes the features of Huawei III power control algorithm. Based on Huawei power control algorithm, Huawei III power control algorithm has the following enhancements: exponential filtering, interpolation optimization, comprehensive decision, different thresholds, and FH gain.
Procedure for Huawei III Power Control Algorithm

This describes the procedure for Huawei III power control algorithm, including processing lost measurement reports, filtering, calculating FH gain, calculating power adjustment step based on the FH gain, and performing power control. Figure 6-3 shows the procedure for Huawei power control algorithm.
Issue 02 (2008-06-30)
6-13
6 Power Control
Figure 6-3 Procedure for Huawei III power control algorithm
Start
Process lost MRs (Interpolation optimization) Process MR filtering (Exponential filtering and slide window filtering)
Calculate FH gain
Calculate power adjustment step based on FH gain
Perform power control
End
1.
Power control decision In Huawei power control algorithm, the power control decision is based on signal level and signal quality. The conditions for power control decision are as follows:
l
Whether the UL/DL receive level ranges from HWIII UL/DL RexLev Upper Threshold and HWIII UL/DL RexLev Lower Threshold. Whether the sum of UL/DL receive quality and HWIII MA FreqHop Gain ranges from HWIII UL/DL FS/HS/AFS/AHS Rex Qual.Upper Threshold and HWIII UL/ DL FS/HS/AFS/AHS Rex Qual. Lower Threshold.
If both the receive level and the receive quality range from the upper thresholds and the lower thresholds, the power control is not required and the power control step remains unchanged.
6-14
Issue 02 (2008-06-30)

NOTE
6 Power Control
l l
The power control decision on the BTS and the power control decision on the MS are implemented simultaneously. You can obtain the HWIII MA FreqHop Gain from the frequency hopping gain table based on the number of MA frequencies. If there are more than eight MA frequencies, obtain the receive quality gain when the number of MA frequencies equals eight. The step of Huawei power control algorithm indicates the offset value between the transmit power of the BTS or MS and the maximum transmit power, instead of the actual value of the offset to be adjusted. This is where the difference between the Huawei power control algorithm and the Huawei power control algorithm lies.
2.
BTS/MS power control performance The power control adjustment step is generated based on receive quality and receive level in each HWIII Up Link/Down Link Power Control Adjust Period. The step range needs to be restricted as follows to prevent excessive adjustment:
l l
The adjustment step must not exceed the HWIII UL MAX UpStep/DownStep. If the generated step does not equal the last step, the BSC sends to the BTS/MS a power control command to adjust the power level of the BTS/MS.
Features of Huawei III Power Control Algorithm

This describes the features of Huawei III power control algorithm. Based on Huawei power control algorithm, Huawei III power control algorithm has the following enhancements: exponential filtering, interpolation optimization, comprehensive decision, different thresholds, and FH gain.
Exponential Filtering
Exponential filtering accelerates the processing rate for the filtering based on the MRs. To calculate the filtered signal level (quality), the exponential filtering applies the weighted average method to the signal level (quality) in the MR of this time with the signal level (quality) in the last MR. The weighted coefficient is calculated based on HWIII UL/DL Rex Qual. Exponent Filter Length and HWIII UL/DL RexLev Exponent Filter Length.
Interpolation Optimization
Interpolation optimization is used for the lost values in the MR. Interpolation optimization uses the signal levels in the last MR for the lost signal levels and uses a constant value 7 for the lost signal quality values.
NOTE
If the number of continuously lost MRs is greater than HWIII Number of lost MRs allowed, the BSC stops the power control procedure until it receives an MR.
Comprehensive Decision
Different power control algorithms use different methods for the comprehensive decision based on the receive level and quality. Huawei power control algorithm uses the dual-threshold (level and quality) method and divides the coverage area into smaller areas for separate comprehensive decisions. Huawei power control algorithm uses an universal decision formula that comprehends the receive level and quality. Thus, the rate of the power control decision is accelerated.
6 Power Control
Different Thresholds
Huawei power control algorithm uses different quality thresholds for different rates. Different rate coding schemes have different requirements for CIR. When half-rate channels are seized, half-rate quality threshold is used; when full-rate SDCCHs are seized, full-rate quality threshold is used. At present, only the speech services are considered. The quality threshold for CS data services uses either the full-rate or half-rate threshold based on the type of the occupied channel.
FH Gain
With the FH gain, the BTS can detects the frame error rate (FER) of the speech coding. Therefore, the speech quality is significantly improved.
6.4 Capabilities
None
6.5 Implementation
This describes how to activate and configure the power control. 6.5.1 Activating Power Control This describes how to activate the power control on the BSC6000 Local Maintenance Terminal. 6.5.2 Configuring Power Control This describes how to configure the power control on the BSC6000 Local Maintenance Terminal.
6.5.1 Activating Power Control

This describes how to activate the power control on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page. Then, choose Configure Cell Attributes. Step 2 In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. Step 3 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 6-4.
6-16
Issue 02 (2008-06-30)
6 Power Control
Figure 6-4 Set Cell Attributes dialog box
Step 4 Click Other Attributes. A dialog box is displayed. Click Advanced, and then select the Public Channel Control tab, as shown in Figure 6-5. Set the PWRC to Yes.
Issue 02 (2008-06-30)
6-17
6 Power Control
Step 5 Click OK to return to the upper-level menu until the configuration is complete. ----End
6.5.2 Configuring Power Control

This describes how to configure the power control on the BSC6000 Local Maintenance Terminal.
Procedure
6-18
Issue 02 (2008-06-30)
6 Power Control
Step 4 Click Power Control. A dialog box is displayed, as shown in Figure 6-7. Set the Power Control Algorithm Switch to Huawei Power Contrl or Huawei Power Contrl.
Issue 02 (2008-06-30)
6-19
6 Power Control
Figure 6-7 Set Power Control Parameter dialog box
Step 5 Click Advanced. The dialog box for setting the advanced power control parameters is displayed. To set the parameters, do as follows:
l
If the Power Control Algorithm Switch is set to Huawei Power Contrl, set the parameters by referring to HW II Power Control, as shown in Figure 6-8.
6-20
Issue 02 (2008-06-30)
6 Power Control
Figure 6-8 Setting Huawei II power control parameters
If the Power Control Algorithm Switch is set to Huawei Power Contrl, set the parameters by referring to HW III Power Control, as shown in Figure 6-9.
Figure 6-9 Setting Huawei power control parameters

This describes the counters related to power control.
6 Power Control
Alarms
None
Counters
Table 6-6 lists the counters related to the power control. Table 6-6 Counters related to power control Counter S3230A S3230B S3231A S3231B S3240 S3241 AS3240 AS3241 H330D H330C AS325B AS325A H330B H330A AS326B AS326A S327B S327A RS327B RS327A Description Number of Power Control Increase Messages Sent to MS Number of Power Control Decrease Messages Sent to MS Number of Power Control Increase Messages Sent to BTS Number of Power Control Decrease Messages Sent to BTS MS Power Rank BTS Power Rank Mean Power Rank of MS Mean Power Rank of BTS Downlink Signal Strength Uplink Signal Strength Mean Strength of Downlink Signals Mean Strength of Uplink Signals Downlink Signal Quality Uplink Signal Quality Mean Quality of Downlink Signals Mean Quality of Uplink Signals Number of Times (Maximum Downlink Transmit Power) Number of Times (Maximum Uplink Transmit Power) Ratio of Maximum Downlink Power Duration (%) Ratio of Maximum Uplink Power Duration (%)
6-22
6 Power Control
Counter TS327B TS327A S3280 S3281 S329 AS3280
Description Duration of Maximum Downlink Power Duration of Maximum Uplink Power Distance Between MS and BTS Maximum Distance Between MS and BTS Number of Power Control Messages Mean Distance Between MS and BTS
6.7 References
l
GSM 04.08 Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification
GSM 05.08 (prETS 300 578) Radio subsystem link control
Issue 02 (2008-06-30)
6-23
7 Handover
7
About This Chapter
Handover
7.1 Overview This describes handover. Controlled by the network, handover is a basic function of the mobile communications system. Handover ensures the continuity of mobile services. 7.2 Availability This describes the availability of handover. The realization of handover depends on the cooperation of relevant NEs and software. 7.3 Technical Description This describes Huawei handover algorithm from a technical perspective. As a whole, Huawei handover algorithm is composed of handover preprocessing and handover decision. 7.4 Implementation This describes how to configure the handover and the power boost before handover. 7.5 Maintenance Information This lists the performance counters related to handover. 7.6 References The references indicate the documents about handover from the related standard organizations.
Issue 02 (2008-06-30)
7-1
7 Handover
7.1 Overview
This describes handover. Controlled by the network, handover is a basic function of the mobile communications system. Handover ensures the continuity of mobile services.
Definition
Handover is a process in which a conversation can be sustained when an MS moves from one cell to another in order to meet the requirement of network management.
Purposes
As a method of radio link control, handover enables an MS to keep a conversation sustainable when the MS travels across different cells. In addition, handover can optimize the overall performance of the system through the adjustment of traffic volume by means of parameters.
Terms
Terms Ping-pong handover Co-site neighbor cells Raileigh fading Chain neighbor cell Definition 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. Neighbor cells under the same BTS.
In radio propagation, signals inevitably suffer from short-period amplitude changes. Raileigh fading relates to frequency. In other words, signal fading is frequency-specific. Chain neighbor cell is a parameter of the neighbor cell relation property. During the quick 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. ATCB 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 ATCB_THRD, the ATCB_HYST, and the difference between the signal strength of the serving cell and that of the neighbor cell.
ATCB handover
7-2
Issue 02 (2008-06-30)
7 Handover
Terms Frequency offset
Definition 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 transmitted 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. In FH mode, the different frequencies set refers to a certain FH group. In nonFH mode, the different frequencies set refers to a certain frequency. The enhanced measurement report is a new downlink measurement report, reported by the MS. Compared with the normal measurement report, some new measurements are added, such as BER, FER, and so on. The enhanced measurement report provides the measurement information of up to 15 neighbor GSM/WCDMA cells, whereas the normal measurement report provides the measurement information of 6 neighbor GSM cells at most. The FULL SET refers to the signal RX level and quality of TCH channels when the BTS performs full power emission. The SUB SET refers to the signal RX level and quality of TCH channels in DTX mode. Ec/No means Signal Noise Ratio in WCDMA. It maps with C/I in GSM.
Different frequencie s set Enhanced measurem ent report
FULL SET SUB SET Ec/N0

Acronyms and Abbreviations MS BSC MR BQ TA BSIC BER BCCH AMR ATCB RQI Full Spelling Mobile Station Base Station Controller Measure report Bad Quality Timing Advance Base Station Identity Code Bit Error Ratio Broadcast Control CHannel Adaptive Multi Rate Adapter Distance To Cell Border Radio Quality Indication
Issue 02 (2008-06-30)
7-3
7 Handover
Acronyms and Abbreviations RSCP CPICH PBGT
Full Spelling Received Signal Code Power Common Pilot Channel Power Budget Handover
7.2 Availability
This describes the availability of handover. The realization of handover depends on the cooperation of relevant NEs and software.
NEs Involved
Table 7-1 lists the network elements involved in handover. Table 7-1 NEs involved in handover MS
NOTE
l : NEs not involved l : involved
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 7-2 lists the versions of GBSS products that support handover. Table 7-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM
7-4
Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases
Issue 02 (2008-06-30)
7 Handover
Product BTS3900 GSM BTS3900A GSM
Version BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
None

This describes Huawei handover algorithm from a technical perspective. As a whole, Huawei handover algorithm is composed of handover preprocessing and handover decision.
Handover Preprocessing
Handover preprocessing consists of the following contents:
l l l l l l
Handover Preparation Handover Penalty Neighbor Cell Sorting Network Characteristic Adjustment Forced handover processing Power boost before HO enabled
Handover Decision
Handover decision is categorized into the following types:
l
Quick handover (consisting of quick PBGT handover and frequency offset handover). Good services can be provided when the speech quality deteriorates during the fast movement of an MS. Quick handover is mainly applicable to the railway scenario. Emergency handover. Emergency handover can keep a call sustainable when the radio environment severely deteriorates. Theoretically, the emergency handover algorithm produces greater error in evaluating the target cell than that produced by other handover algorithms. In normal cell, frequent emergency handovers should be avoided. Enhanced dual-band network handover. In an enhanced dual-band network, the resources in the overlaid 1800M subcell and underlaid 900M subcell can be shared during the assignment and handover procedures. That is, the calls in the high-traffic 900M subcell can be moved to the low-traffic 1800M subcell to achieve traffic balance. Load handover. Load handover can enable the load of system traffic to be shared so that the deterioration of local counters is minimized. General handover. General handover can ensure good services when an MS is moving.
Figure 7-1 shows the priority and handover algorithm of each type of handover decision:
7 Handover
Figure 7-1 Handover decision

Quick handover
Emergency handover TA handover Interference handover Quick level drop handover Bad quality handover
Enhanced dual-band network handover Load handover
General handover Edge handover Fast-moving micro cell handover Inter-layer (better cell) handover PBGT handover AMR handover Better 3G cell handover TIGHT BCCH handover algorithm
7.3.1 Handover Preprocessing

This describes handover preprocessing. Based on the neighbor cell information and configured parameters in the measurement report, the system performs handover preprocessing and adjusts the priority of a neighbor cell.
Measurement Report
The BSC decodes neighbor cell information from the measurement report. The processing can be performed either on the BSC side or on the BTS side.
l
If MR.Preprocessing is set to No, then the processing is performed on the BSC side.
7-6

NOTE
7 Handover
MR.Preprocessing is set to No by default.

l
If MR.Preprocessing is set to Yes, then the processing is performed on the BTS side. By setting the parameters Transfer Original MR, Transfer BS/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. In this way, the signaling throughput on the Abis interface and the usage of the BSC can be decreased.
The MR can be classified into enhanced MR and normal MR, the parameter Report Type determines which type is used. In the MR, the TCH measurement of the serving cell is classified into FULL SET and SUB SET. The parameter DtxMeasUsed determines whether the DTX is used during measurement when the MS and BTS report MRs. According to the BCCH frequencies and BSIC reported by an MS, the corresponding neighbor cell index is detected. Then the uplink part and downlink part of the measurement report is read.
l
If measurement reports are issued continuously, they are directly interposed in the measurement report queue. If measurement reports are issued discontinuously and the number of lost measurement reports is smaller than Allowed M.R Number Lost, the system performs operations as follows:

For the serving cell, the MRs are linear interpolated. For the neighbor cell, the lowest values are applied to the lost measurement values according to the protocols; that is, level 0 (-110 dBm) is applied in interpolation.
NOTE
The same method is applied in the condition that no MR due to low RX level in the neighbor cell.
l
If measurement reports are issued discontinuously and the number of lost measurement reports is greater than Allowed M.R Number Lost, the previous measurement reports are discarded. When new measurement reports arrive, calculation is performed again.
Filtering treatment is performed on measurement reports, that is, a number of consecutive measurement reports are obtained from the queue. Averaging treatment is performed on uplink/ downlink RX level, uplink/downlink RX quality, TA, RQI, BTS power, 2G neighbor cell level, and the CPICH, RSCP, and Ec/No of 3G neighbor cell. The averaging treatment minimizes the effect of abrupt changes in individual measurement report values on the result of handover decision. The number of consecutive measurement reports needed in filtering is different according to the measurement object and channel type, as listed in Table 7-3. Table 7-3 Parameters related to the number of measurement reports Measurement Object Receive level of the serving cell Channel Type SDCCH TCH Parameter Filter Length for SDCCH Level Filter Length for TCH Level
Issue 02 (2008-06-30)
7-7
7 Handover
Measurement Object Quality of the serving cell TA of the serving cell Receive level of the neighbor cell Power of the BTS in the serving cell RQI
Channel Type SDCCH TCH BCCH TCH TCH
Parameter Filter Length for SDCCH Qual Filter Length for TCH Qual Filter Length for TA Filter Length for Ncell RX_LEV Filter Length for TCH Level Filter Length for TCH Qual
If consecutive measurement reports are insufficient, you can infer that filtering fails. Then handover decision is not performed.
Quick Handover Preparation

The preparation of quick handover involves the following main aspects:
l
Frequency offset is decoded from the measurement report. Frequency offset of the MS is obtained from the uplink measurement report from the BTS by the BSC.
filtering is performed to the measurement report.
Handover Penalty
The handover penalty is performed in the following conditions: quick handover succeeds, TA emergency handover succeeds, BQ emergency handover succeeds, quick micro cell handover succeeds, OL subcell to UL subcell handover within an enhanced concentric cell succeeds, and handover failure.
l
After the quick handover, TA emergency handover, or BQ emergency handover is successful, the actual RX level of the old cell is subtracted with related value during the penalty. Table 7-4 lists the related parameters. Table 7-4 Parameters related to the number of measurement reports Handov er Quick handover TA Handove r Parameter Quick Handover Punish Time(s) Quick Handover Punish Value Penalty Level after TA HO Penalty Time after TA HO(s)
7-8
Issue 02 (2008-06-30)
7 Handover
Handov er BQ handover
Parameter Penalty Level after BQ HO Penalty Time after BQ HO(s)
After the quick micro cell handover is successful, penalty is performed on all the neighbor cells of the micro cell. Related parameters are Penalty on Fast Moving HO and Penalty Time on Fast Moving HO(s). After the OL subcell to UL subcell handover within an enhanced concentric cell is successful, the call handover from OL subcell to UL subcell is not allowed within Penalty Time of UtoO HO(s). After the OL subcell to UL subcell handover in the enhanced dual-band network is successful, the call handover from OL subcell to UL subcell is not allowed within Inter UL And OL Subcells HO Penalty Time(s). After the handover fails, different penalties are performed to the target cell according to different causes:
If the handover to a neighbor 2G or 3G cell fails, the actual RX level of the target cell is decreased by Penalty Level after HO Fail for neighbor cell queuing during the penalty.
NOTE
According to the cause of handover failure,the penalty time can be classified into three types:UmPenaltyTimer,RscPenaltyTimer,andCfgPenaltyTimer.
If the OL subcell to UL subcell handover within an enhanced concentric cell fails, the call handover from OL subcell to UL subcell is not allowed within Penalty Time after OtoU HO Fail(s). If the UL subcell to OL subcell handover within an enhanced concentric cell fails, the call handover from UL subcell to OL subcell is not allowed within Penalty Time after UtoO HO Fail(s).
Neighbor Cell Basic Queuing

The purpose of neighbor cell basic queuing is to produce the candidate cell list with the following information taken into account after handover penalty: RX level of the serving cell and neighbor cells contained in the MRs, hysteresis, usage of TCHs in the neighbor cells, and so on.
l
In non-direct retry situation, if an MS in a BSC external cell occupies an SDCCH and InterBSC SDCCH HO ALLowed is set to No, then the cell should be removed from the candidate cell list; that is, the handover to the BSC external cell is prohibited. If a neighbor 2G cell is in the same BSC with the serving cell and the TCH usage of the neighbor cell is 100%, then the neighbor cell is removed from the candidate cell list; that is, the handover to this neighbor cell is prohibited. If the downlink RX level of a neighbor 2G cell is lower than the sum of Min DL Power on HO Candidate Cell and NCell Interf Type, then the neighbor cell should be removed from the candidate cell list; that is, the handover to this neighbor cell is prohibited. If the uplink RX level of a neighbor cell is lower than the sum of Min UP Power on HO Candidate Cell and NCell Interf Type, then the neighbor cell should be removed from the candidate cell list; that is, the handover to this neighbor cell is prohibited.
Issue 02 (2008-06-30)
7 Handover
l
If a 3G neighbor cell is an FDD cell, the cell is processed according to the FDD REP QUANT:
If FDD REP QUANT is set to Ec/N0, then if the Ec/N0 of the cell is less than Min Ec/ No Threshold, the neighbor cell should be removed from the candidate cell list; that is, the handover to this neighbor cell is prohibited. If FDD REP QUANT is set to RSCP, then if the RSCP of the cell is less than Min RSCP Threshold, the neighbor cell should be removed from the candidate cell list; that is, the handover to this neighbor cell is prohibited.
If a 3G neighbor cell is a TDD cell, and if the RSCP of the cell is less than Min RSCP Threshold, then the neighbor cell should be removed from the candidate cell list; that is, the handover to this neighbor cell is prohibited. Calculate the difference between the downlink RX level of the neighbor cells and the downlink RX level of the serving cell. Based on the difference, sort the neighbor cells in a descending order.
Network Characteristic Adjustment

Network characteristic adjustment is a process in which the position of each cell is determined in the queue of candidate cells based on the related network information. Network characteristic adjustment provides the final list of candidate cells for handover decision. After the network characteristic adjustment, the candidate cells (consisting of neighbor cells and serving cell) are sorted in descending order by priority. Then the handover decision procedure starts.
Forced Handover
If the forced handover is triggered, the subsequent handover decision is not performed. Purpose of the forced handover:
l
If no TCH is available in the serving cell during the MS access process, the direct retry procedure is performed when Direct 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 drops occur during BTS maintenance.
The forced handover is categorized into the following four types:

l l l l
Outgoing cell handover (directed retry) Outgoing BTS handover Outgoing BSC handover Specified cell list handover
Power Boost Before Handover

When the MS is in a corner, the level may decrease swiftly. At this time, the handover may be triggered. Then, the power control algorithm may fail to adjust the MS and BTS power, thus causing the MS fails to receive the handover command and call drops. By quickly adjusting the BTS transmit power to the maximum level before sending the handover command to the MS and shielding the BTS power control function during the handover, that is,
7 Handover
keep the maximum BTS transmit power during the handover, a high handover success rate is ensured. Power boost before handover can be controlled through Power boost before HO enabled or not.
7.3.2 Handover Decision Algorithm

This describes the handover decision algorithm. After measurement reports are preprocessed, the handover decision procedure starts. According to the emergency condition of an MS in the network, the handover decision algorithm performs decision in the following order: quick handover, emergency handover, enhanced dual-band handover, load handover, and then general handover. The handover decision consists of the following two steps:
l l
Determines whether the serving cell meets the triggering conditions. Selects the candidate cells.
The candidate cells is selected based on Inter-RAT HO Preference:

l
When Inter-RAT HO Preference is set to Pre_2G_Cell: If there is no eligible neighbor 2G cell but with eligible neighbor 3G cells, then the 3G cell is selected.
When Inter-RAT HO Preference is set to Pre_3G_Cell: The 3G cell is preferred. When Inter-RAT HO Preference is set to Pre_2G_CellThres: If the RX level of 2G candidate cell is smaller than or equal to HO Preference Threshold for 2G Cell, then the 3G cell is preferred.
If the emergency handover conditions are met and the number of candidate cells is not zero, then the emergency handover timer Min Interval for Emerg.HOs is started. Another emergency handover can be decided only when Min Interval for Emerg.HOs expires.
Quick Handover
This describes quick handover. The 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 urban backbone roads, selected routes, and high-speed railroads.
Quick Handover Types

Quick handover consists of frequency offset handover and quick PBGT handover.
l
Frequency offset handover According to the frequency offset information reported by an MS moving at a high speed, whether the MS is far from the serving cell is determined. Frequency offset handover decision is performed according to the uplink/downlink level of the serving cell and the path loss of the neighbor cell.
Quick PBGT handover Quick PBGT handover decision is performed according to the path loss of the neighbor cell.
Issue 02 (2008-06-30)
7-11
7 Handover
For quick handover, the handover response speed is enhanced through the following ways:
l l l l
Accurately calculating the moving speed of the MS Derestricting the interval between handover precisions Reducing the number of measurement reports for the handover decision Introducing the filtering
Triggering Condition
Whether the conditions of frequency offset handover are met is determined during handover decision. When the BTS cannot report the frequency offset information or the reported frequency offset information is invalid, fast PBGT handover is triggered if the other conditions of frequency offset handover are met. If the Quick Handover Enable is set to Yes, the triggering conditions of quick handover are as follows:
l
The MS is far from the serving cell (the frequency offset in the measurement result message is a negative value) and the moving speed of the MS is higher than Quick Move Speed Thres. The uplink level of the serving cell after filtering is lower than Quick Handover Up Trigger Level. The downlink level of the serving cell after compensation is lower than Quick Handover Down Trigger Level. The path loss of the configured chain neighbor cell is smaller than a certain threshold of the path loss of the serving cell. In other words, PBGT(n) is equal to or greater than 0.
The triggering decisions of quick handover are as follows:

l
If the last three conditions are met, the decision is performed 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.
If not all the last three conditions are met, quick handover is not triggered.
Target Cell Selection

The target cell must be a chain neighbor cell of the serving cell. The target cell can be obtained through the setting of Chain Neighbor Cell.
Limitations
The limitations on quick handover are as follows:
l l
The target cell cannot serve as the serving cell. The candidate cells for quick handover must be chain neighbor cells of the serving cell. Each cell can be configured with a maximum of three chain neighbor cells. After quick handover is successful, penalty is performed on the originating cell during the penalty time to prevent an immediate switchback to the cell. The penalty time and penalty value depend on Quick Handover Punish Time and Quick Handover Punish Value respectively.
7-12
7 Handover
TA Handover
This describes TA handover. TA handover is a kind of emergency handover. TA handover performs handover decision based on the TA value reported by an MS. The TA value of an ordinary cell ranges from 0 to 63. The TA value of the underlaid subcell in a double-timeslot cell ranges from 0 to 229. The step of each bit is 553.5 m. If the TA value is set to 63, you can infer that the distance is 35 km.
TA handover is triggered when the following conditions are met:
l l
TA HO Allowed is set to Yes. Filtered TA value reported by the MS through measurement reports is greater than or equal to TA Threshold.
The TA handover can be triggered only when all the previous conditions are met.
NOTE
From the perspective of the triggering condition for TA handover, TA can be regarded as a criterion for limiting the size of a cell.

A target cell should be the cell with the highest priority among the queue of sorted candidate cells after preprocessing. In addition, the target cell should meet the following limitations:
l l
The target cell cannot serve as the serving cell. If the TA Threshold of a co-site neighbor cell lower than or equal to the TA Threshold of the serving cell, a handover to the cell is forbidden. After the TA handover succeeds, penalty is performed on the source cell. During Penalty Time after TA HO(s), the Penalty Level after TA HO is subtracted from the level of the source cell to avoid an immediate handover back to the source cell.
If the triggering conditions of TA handover are met, and there is no 2G candidate cell, the following operation is performed:
l
If a neighbor 3G cell is available, the 2G/3G inter-RAT handover is performed when Outgoing-RAT HO Allowed is set to Yes and the MS supports the 2G/3G inter-RAT handover. If no neighbor 3G cell is available, or Outgoing-RAT HO Allowed is set to No, or the MS does not support the 2G/3G inter-RAT handover, then the decision on another emergency handover type is performed.
BQ Handover
This describes BQ handover. BQ handover is a kind of emergency handover. BQ handover performs decision based on the uplink/downlink RX quality on the Um interface. The RX quality is measured in bit error ratio (BER). The BSC measures the quality of a radio link based on the quality class in the measurement report. The probable reason for an increase in BER is that the signal power is too low or the channel interference becomes great.
7 Handover
If BQ HO Allowed is set to Yes, the triggering conditions of BQ handover are as follows:
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 if either of the previous conditions is met. The configuration parameters for uplink and downlink RX quality threshold are as follows:
l
For non-AMR calls, the configuration parameters for uplink RX quality threshold is UL Qual. Threshold, the configuration parameters for downlink RX quality threshold is DL Qual. Threshold. For AMR calls, the configuration parameters for uplink RX quality threshold is ULQuaLimitAMRFR, the configuration parameters for downlink RX quality threshold is DLQuaLimitAMRFR. For AMR HR calls, the configuration parameters for uplink RX quality threshold is ULQuaLimitAMRHR, the configuration parameters for downlink RX quality threshold is DLQuaLimitAMRHR.

A target cell should be the cell with the highest priority in the list of sorted candidate cells after the preprocessing procedure. In addition, the target cell should meet the following limitations:
l
If the target cell is a neighbor cell, the RX level of the target cell must meet the following formula: Filtered downlink RX level of the neighbor cell > Filtered downlink RX level of the serving cell + Min Access Level Offset of the serving cell configured for the neighbor cell - Chain Neighbor Cell
NOTE
If there is only one cell in the candidate cell queue and the cell is a neighbor cell, then no such requirement is needed.
l
If there is no neighbor cell, Intracell HO Allowed is set to Yes, and the serving cell is not in intra-cell handover penalty state, then the MS is handed over to the serving cell. A channel with different frequency band, different frequencies set, different TRX, or different timeslot is preferred (priority: different frequency band > different frequencies set > different TRX > different timeslot).
After the BQ handover succeeds, penalty is performed on the source cell. During the Penalty Time after BQ HO(s), the Penalty Level after BQ HO is subtracted from the level of the source cell to avoid an immediate handover back to the source cell. If the triggering conditions of BQ handover are met, and there is no 2G candidate cell, the following operation is performed:
l
If a neighbor 3G cell is available, the 2G/3G inter-RAT handover is performed when Outgoing-RAT HO Allowed is set to Yes and the MS supports the 2G/3G inter-RAT handover.
7-14

l
7 Handover
If no neighbor 3G cell is available, or Outgoing-RAT HO Allowed is set to No, or the MS does not support the 2G/3G inter-RAT handover, then the decision on another emergency handover type is performed.
Rapid Level Drop Handover

This describes rapid level drop handover. Rapid level drop handover is a kind of emergency handover. If the mean value filtering and P/N decision methods are used in edge handover and PBGT handover, responses to short-period rapid level drop are insensitive. Therefore, targeting the rapid level drop, you can perform finite impact response (FIR) filtering on the original RX level signals. This filtering method is responsive to the rapid level drop based on the drop slope of the original RX level signals.
Triggering Conditions
If Rx_Level_Drop HO Allowed is set to Yes, the triggering conditions of rapid level drop handover are as follows:
l
If the measurement reports that the BSC received are pre-processed, the flag bit in the measurement report will be used for handover decision directly. If the measurement reports that the BSC received are not pre-processed, then the rapid level drop handover is triggered when the corresponding specifications between original RX level, Edge HO UL RX_LEV Threshold, Filter Parameter A1A8, and Filter Parameter B are met.
The rapid level drop handover is triggered if either of the previous conditions is met.

A target cell should be the cell with the highest priority in the list of sorted candidate cells after the preprocessing procedure. In addition, the target cell should meet the following limitations:
l l
The target cell has a higher priority than the serving cell. The MS cannot be handed over to the serving cell.
If the triggering conditions of rapid level drop handover are met, and there is no 2G candidate cell, the following operation is performed:
l
Interference Handover
This describes interference handover. Interference handover is a kind of emergency handover. Interference handover protects the interfered calls and reduce the network interference by detecting scenarios where the calls are interfered.
7 Handover
The difference between interference handover and BQ handover is that the BQ handover detects the bad quality caused both by coverage and interference. The interference handover does not detect the bad quality caused coverage.
If the Interference HO Allowed is set to Yes, the triggering conditions of interference handover are as follows:
l l
The uplink RX quality after filtering is greater than or equal to the RX quality threshold supposed in current uplink RX level The downlink RX quality after filtering is greater than or equal to the RX quality threshold supposed in current downlink RX level
The interference handover is triggered if either of the previous conditions is met. The configuration parameters for uplink and downlink RX quality threshold are as follows:
l
For non-AMR FR calls, the configuration parameters for RX quality threshold are RXQUAL1n, where 1 n 12. For AMR FR calls, the configuration parameters for RX quality threshold are RXQUALn (1 n 12) and RXLEVOff.

When n = 1, the RX quality threshold is RXQUAL1. When 2 n 12, the RX quality threshold is RXQUALn + RXLEVOff.

A target cell should have the highest priority among the candidate cells. In addition, a target cell should meet the following conditions:
l
If Intracell HO Allowed is set to Yes and if the intra-cell handover penalty timer expires, then the serving cell can be the target cell.
NOTE
When a number of consecutive handovers occur, Forbidden time after MAX Times is triggered, the intra-cell handover is forbidden for a corresponding period.
l
If the filtered level of a neighbor cell Inter-layer HO Threshold of the neighbor cell + Adjacent Cell Inter-layer HO Hysteresis-64, the neighbor cell can serve as a target cell.
If the triggering conditions of interference handover are met, and there is no 2G candidate cell, the following operation is performed:
l
No Downlink Measurement Report Handover

This describes no downlink measurement report handover. The handover performs handover decision based on the uplink quality to keep a call sustainable and to minimize the possibility of call drops.
7 Handover
The no downlink measurement report handover is generally caused by poor radio environment on the uplink. In this case, the requirements of the filtering algorithm cannot be met, so other handover algorithms cannot be triggered.
The triggering conditions of no downlink measurement report handover are as follows:
l l l
No Dl Mr.HO Allowed is set to Yes. The measurement report of the call does not have downlink part currently. The value of the uplink quality after filtering treatment 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.
l l
When all the previous conditions are met, the no downlink measurement report handover is triggered.

The selection conditions for target cell are as follows:
l
The sorted neighbor cells recorded in the last complete measurement report are saves as candidate cells. The MS is preferably handed over to a neighbor cell. If there is no neighbor cell, the MS is handed over to the serving cell.
l l
Enhanced Dual-Band Network Handover

This describes enhance dual-band network handover, which is a handover decision based on the traffic volume of the overlaid and underlaid subcells and on the level quality. Enhanced dual-band network handover is classified into the following:
l l l
Handover due to high underlaid subcell load Handover due to low underlaid subcell load Call movement handover in the overlaid subcell
The triggering conditions of the handover due to high underlaid subcell load are as follows:
l
The load of the underlaid subcell in the cell is higher than or equal to UL Subcell General Overload Threshold. The load of the overlaid subcell in the cell is lower than Inner Cell Serious OverLoad Thred. The system flow is not higher than Allowed Flow Control Level of UL And OL Subcell HO. The current call is within the handover margin that allows handover.
Issue 02 (2008-06-30)
7 Handover
When all the previous conditions are met, the handover due to high underlaid subcell load is triggered. If the load of the underlaid subcell in the cell is higher than or equal to UL Subcell Serious Overload Threshold, then Handover Period = UL Subcell Load Hierarchical HO Period Modified Step Length of UL Load HO Period, and Step Length of UL Subcell Load HO remains the same. The triggering conditions of the handover due to low underlaid subcell load are as follows:
l
The load of the underlaid subcell in the cell is lower than UL Subcell Lower Load Threshold. The system flow is not higher than Allowed Flow Control Level of UL And OL Subcell HO. The current call is within the handover margin that allows handover.
When all the previous conditions are met, the handover due to high underlaid subcell load is triggered. The triggering conditions of the call movement handover in the overlaid subcell are as follows:
l l
SSserving < Thdouter SS(u) - SS(n) < ATCB_THRD - ATCB_HYST The handover in the overlaid subcell is triggered if either of the previous conditions is met.
SSserving: indicates the compensated downlink RX level in the serving cell after filtration. Thdouter: indicates Outgoing OL Subcell HO level Threshold. SS(u): indicates the downlink level (power compensation is performed on the downlink level based on 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 dual-band network handover is not performed and the decision condition is met by default. SS(n): The optimum neighbor cell is a cell, the measured value of whose BCCH level is the greatest, among the neighbor cells. The optimum neighbor cell is on the same frequency band, layer, and level with the underlaid subcell. The cell, however, is not co-sited with the underlaid subcell. SS(n) is the value of such a cell. If such a cell is unavailable, the value of SS(n) is 110 dBm. ATCB_THRD: indicates Distance Between Boudaries of UL And OL Subcells. ATCB_HYST: indicates Distance Hysterisis Between Boudaries of UL And OL Subcells.
NOTE
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 the neighbor cell. When SS(s) = SS(n), the system considers that it is the boundary point of the underlaid subcell. When SS(s) - SS(n) > ATCB_THRD, it is the coverage area of the overlaid subcell. The coverage area of the overlaid subcell is determined according to the different networking and coverage conditions of the existing network. In addition, the overlaid subcell of the serving cell and the overlaid of the neighbor cell will never overlap no matter how the distance between the BTSs changes. The handover zone indicates the level range. In the case of overlaid/underlaid load handover on the enhanced dual-band network, the handover is performed level by level and the MS whose downlink level is within the handover zone is handed over.
7-18
Issue 02 (2008-06-30)
7 Handover

The target cell selection has the following restrictions:
l
For the handover due to high underlaid subcell load, the MS can be handed over to only the overlaid subcell. For the handover due to low underlaid subcell load, the MS can be handed over to only the underlaid subcell. For the call movement handover in the overlaid subcell, the MS is handed over to the neighbor cell that ranks first among the neighbor cells. The MS cannot be handed over to the cell that ranks behind the serving cell. The target cell is generally the underlaid subcell. It can also be other neighbor cells.
Limitations
The limitations on the handover due to high underlaid subcell load are as follows:
l
The cell where the call is located is on the enhanced dual-band network. The HW_Concentric Attribute is set to Underlay cell. The Load HO From UL Subcell to OL Subcell Allowed parameter is set. The maximum range of the handover zone is 63 to Incoming OL Subcell HO level Threshold. The handover starts from the high level.
l l
The limitations on the handover due to low underlaid subcell load are as follows:
l
The cell where the call is located is on the enhanced dual-band network. The HW_Concentric Attribute is set to Overlay cell. The Load HO of OL Subcell to UL Subcell Enabled parameter is set. The maximum range of the handover zone is 63 to Outgoing OL Subcell HO level Threshold. The handover starts from the low level.
l l
The limitations on call movement handover in the overlaid subcell are as follows:
l
The cell where the call is located is on the enhanced dual-band network. The HW_Concentric Attribute is set to Overlay cell.
Effect of the Enhanced Dual-Band Network Handover on the Existing Algorithm

The effect of the enhanced dual-band network handover on the existing algorithm is as follows:
l
On the enhanced dual-band network, to prevent the common load handover from colliding with the handover between OL subcell and UL subcell on the network, for the common load handover of the cells on the network, the MS cannot be handed over to the cell in the same group when the load handover switches between the overlaid subcell and the underlaid subcell on the network (Load HO From UL Subcell to OL Subcell Allowed and Load HO of OL Subcell to UL Subcell Enabled) are enabled. Because the PBGT handover algorithm may cause inter-cell handover, the MS cannot be handed over the cell in the same group in the case of PBGT handover between the cells on the enhanced dual-band network.
Issue 02 (2008-06-30)
7-19
7 Handover
Load Handover
This describes load handover. In the network, some cells have heavy loads, but the overlapped upper-layer cells and the neighbor cells have light loads. To balance the loads of these cells, load handover is required. In a load handover procedure, some loads in heavy-load cells are handed over to light-load cells. In addition, the loads in neighbor cells should not be handed over to heavy-load cells. The load handover is only for the 2G inter-cell handover and cannot be used for 2G -> 3G handover. Load handover can be performed in cells at different layers. Load sharing, however, can be performed in only one BSC. Figure 7-2 shows the load handover. Figure 7-2 Load handover
A cell with a heavy load A cell with a light load A cell with a heavy load A cell with a light load A cell with a light load A cell with a heavy load A cell with a light load
To perform load sharing, increase Edge HO DL RX_LEV Threshold so that the traffic on the edge of a cell is handed over to a neighbor cell with light load. The traffic load of a cell can be determined through the ratio of the traffic flow (generally TCH usage) of the cell to the preset threshold. If the traffic flow of a cell is greater than the Load HO Threshold, you can infer that the traffic load of this cell is heavy. The load handover algorithm needs to be enabled. If the traffic flow of a cell is smaller than the Load Req. on Candidate Cell, you can infer that the traffic load of this cell is light and the cell can receive loads from the heavy-load cells. Load handover may trigger many handovers, so you should consider the load of the system CPU before triggering load handover. In other words, you should consider the system traffic level before triggering load handover. 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 increases based on Load HO Step Level (CLS_Ramp) and Load HO Step Period (CLS_Period). The increase stops until the increased volume equals Load HO Bandwidth (CLS_Offset), as shown in Figure 7-3.
7-20
Issue 02 (2008-06-30)
7 Handover
Figure 7-3 Load handover

Load handover band Border of normal handover
Cell A
Cell B
CONF_HO_RXLEV+CLS_Offset
CONF_HO_RXLEV CONF_HO_RXLEV+CLS_Ramp
If the Load HO Allowed is set to Yes, the triggering conditions of load handover are as follows:
l
The CPU usage of the system is smaller 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.

l
Filtered RX level after penalty Inter-layer HO Threshold + Adjacent Cell Inter-layer HO Hysteresis-64. The MS cannot be handed over to the serving cell. If the target cell is in the same BSC with the source cell, then the current load of the target cell is lower than Load Req.on Candidate Cell. If the target cell is not in the same BSC with the source cell, then the load handover occurs when the target cell is not 100% occupied.
l l
Examples
The system assigns MSs to different load handover bands based on the downlink RX level. The load handover algorithm performs handover on the cell so that the MS is handed over out of the cell step by step. 1. The MSs in load handover band 1 are handed over to the neighbor cells. Load handover band 1 refers to the area where the downlink level ranges from Edge HO DL RX_LEV Threshold to Edge HO DL RX_LEV Threshold + Load HO Step Level. After one Load HO Step Period, the MSs in load handover band 2 are handed over to the neighbor cells. Load handover band 2 refers to the area where the downlink level ranges from Edge HO DL RX_LEV Threshold to Edge HO DL RX_LEV Threshold + (2 x Load HO Step Level). The load handover stops when the flow of the cell is less than or equal to Load HO Threshold.
2.
3.
Issue 02 (2008-06-30)
7 Handover
Load handover uses the step-by-step outgoing handover mode so that the possibility of a sharp increase in CPU load is eliminated and the occurrence of call drops due to congested target cell is avoided.
Edge Handover
This describes edge handover. Based on level, edge handover is a kind of general handover. If edge handover is triggered, the level of the target cell should be at least one hysteresis value (Inter-cell HO Hysteresis) higher than the level of the serving cell.
If Fringe HO Allowed is set to Yes, the triggering conditions of edge handover are as follows:
l
One of the following conditions is met.
The filtered downlink RX level of the serving cell is smaller than Edge HO DL RX_LEV Threshold The filtered uplink RX level of the serving cell is smaller than Edge HO UL RX_LEV Threshold
The RX level of neighbor cell is greater than the sum of the RX level of serving cell and Inter-cell HO Hysteresis.
The edge handover is triggered when the P/N criterion is met, that is, the previous conditions are met for Edge HO Valid Time(s) during Edge HO Watch Time(s). Figure 7-4 shows the edge handover. Figure 7-4 Edge handover
Cell 1 Cell 2
-97 dBm
-85 dBm

l l
The MS cannot be handed over to the serving cell. After the sorting, the target cell must have a higher priority than the serving cell.
A cell can become a target cell if the previous conditions are met for Edge HO AdjCell Valid Time(s) during Edge HO AdjCell Watch Time(s). If the triggering conditions of edge handover are met, and there is no 2G candidate cell, the following operation is performed:

l
7 Handover
If a neighbor 3G cell is available, the 2G/3G inter-RAT handover is performed when Outgoing-RAT HO Allowed is set to Yes and the MS supports the 2G/3G inter-RAT handover. If no neighbor 3G cell is available, or Outgoing-RAT HO Allowed is set to No, or the MS does not support the 2G/3G inter-RAT handover, then the decision on another handover type is performed.
Fast-Moving Micro Cell Handover

This describes fast-moving micro cell handover. In fast-moving micro cell handover mode, the handover from a micro cell to a macro cell is performed 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
If an MS in the micro cell moves relatively fast, then the MS is handed over to a macro cell. To prevent the 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 7-5 shows the fast-moving micro cell handover. Figure 7-5 Fast-moving micro cell handover
Umbrella cell Micro cell
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 a serving cell is shorter than MS Fastmoving Time Threshold, the number of cells that the MS passes in fast movement counted by the system is added by one.
NOTE
The cell counted by the system must locates at a layer smaller than layer 4. In other words, the cell must be non-Umbrella cell.
3.
When the number of cells that the MS passes in fast movement reaches MS Fast-moving Watch Cells, if the number of cells that the MS passes in fast movement counted by the
Issue 02 (2008-06-30)
7 Handover
system is greater than or equal to MS Fast-moving Valid Cells, the fast-moving micro cell handover is triggered.

l
The number of the layer where a target cell is located must be layer 4. In other words, a target cell must be an Umbrella cell. Filtered RX level of a target cell Inter-layer HO Threshold + Adjacent Cell Interlayer HO Hysteresis-64. After the sorting, the target cell must have the highest priority.
Limitations
After the fast-moving micro cell handover is successful, penalty is performed on all the neighbor micro cells. During Penalty Time on Fast Moving HO(s), Penalty on MS Fast Moving HO is subtracted from the RX level of neighbor micro cells.
Cell Layer and Cell Hierarchy

Through the multiband handover algorithm developed by Huawei, a proper traffic volume distribution can be realized among multiple frequency bands. Huawei multiband handover algorithm divides cells into four layers with 16 hierarchies in each layer. Thus, the cells are grouped by Layer of the Cell and are applicable for complex networking modes. Figure 7-6 shows the cell layers. Figure 7-6 Cell layer
GSM900 Umbrella Cell GSM900 Macro Cell DCS1800 Micro Cell GSM900 GSM900 GSM900 GSM900 DCS1800 DCS1800 Layer 2 GSM900 GSM900 Layer 3 Layer 4
DCS1800 Pico Cell
DCS1800
DCS1800
DCS1800 Layer 1
In the multiband handover algorithm developed by Huawei, a GSM network covering a certain area is divided into four layers, which are described as follows.

l
7 Handover
Layer 4: Umbrella cell. The umbrella cell is generally a GSM900 cell with wide coverage. This type of cell is used for coverage and fast MS connection. Layer 3: Macro cell. The macro cell is generally composed of GSM900 cells. This type of cell is most commonly used in the current GSM system, serving the majority of users. Layer 2: Micro cell. The micro cell is generally composed of DCS1800 cells with small coverage. This type of cell is used for capacity expansion, relieving the insufficiency of frequency resources. Layer 1: Pico cell. The pico cell is generally composed of DCS1800 cells. This type of cell is used in hot spots and blind spots.
The cell in the low layer has a high priority.
Inter-Layer (Better Cell) Handover

This describes inter-layer (better cell) handover. Inter-layer (better cell) handover is a kind of general handover to enable the cells in lower layer level (with great layer level value) to absorb traffic. To balance the traffic volume flexibly and to meet the requirements of different topology modes, the GSM network is divided into several layers. For details, refer to 7.3.2.10 Fast-Moving Micro Cell Handover.
If Level HO Allowed is set to Yes, the triggering conditions of inter-layer handover are as follows:
l
The target cell camps on the lower layer than the serving cell, that is, the priority level of the target cell is higher than that of the serving cell. Filtered downlink RX level of the target cell Inter-layer HO Threshold + Adjacent Cell Inter-layer HO Hysteresis-64. After the sorting, 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(s) during Layer HO Watch Time(s).

l l l
The triggering conditions are met. The serving cell cannot serve as the target cell. Among the sorted candidate cells after the preprocessing procedures, the target cell has the highest priority.
PBGT Handover
This describes power budget (PBGT) handover. The PBGT handover is a kind of general handover.
7 Handover
If the 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 in the same hierarchy. The downlink level meets the following formula for PBGT Valid Time(s) during PBGT Watch Time(s): (MIN(MS_TXPWR_MAX,P) RXLEV_DL PWR_DIFF) (MIN(MS_TXPWR_MAX (n),P) RXLEV_NCELL(n)) > PBGT_HO_MARGIN The parameters are described as follows:
RXLEV_DL: It indicates the downlink receive level in the serving cell after the filtering treatment. If the enhanced concentric cell function is enabled in the serving cell, the value indicates the downlink receive level in the serving cell that serves as the neighbor cell, that is, the downlink receive level of BCCH TRXs. MS_TXPWR_MAX: It indicates the maximum transmit power of an MS permitted in the serving cell. MS_TXPWR_MAX (n): It indicates the maximum transmit power of an MS permitted in neighbor cell n. RxLev_NCELL (n): It indicates the downlink receive level in neighbor cell n. PWR_DIFF: It 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: It indicates the maximum transmit power capability of an MS. PBGT_HO_MARGIN: It is the difference between the PBGT HO Threshold of the serving cell and 64.
The PBGT handover can be triggered only when all the previous conditions are met.

A target cell should meet the following conditions:
l l l
The target cell and the serving cell are at the same layer and in the same hierarchy. The serving cell cannot serve as the target cell. Among the sorted candidate cells after the preprocessing procedures, the target cell has the highest priority.
Other Handovers
This describes other handovers, which consist of AMR handover and better 3G cell handover.
AMR Handover
Refer to 11 AMR.
Better 3G Cell Handover

Refer to 8 2G/3G Interoperability.
7 Handover
TIGHT BCCH Handover Algorithm

Refer to 51 BCCH Dense Frequency Multiplexing.
7.4 Implementation
This describes how to configure the handover and the power boost before handover. 7.4.1 Configuring the Handover This describes how to configure handover on the BSC6000 Local Maintenance Terminal. 7.4.2 Configuring Power Boost Before Handover This describes how to configure power boost before handover on the BSC6000 Local Maintenance Terminal.
7.4.1 Configuring the Handover

This describes how to configure handover on the BSC6000 Local Maintenance Terminal.
Context
Before configuring the parameters related to the handover decision algorithm, you need to configure the relation between neighbor cells. On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page. Then, select Set Adjacent Relation Property on the shortcut menu. A dialog box is displayed, as shown in Figure 7-7.
Issue 02 (2008-06-30)
7-27
7 Handover
Figure 7-7 Set Adjacent Relation Property dialog box
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page. Then, select Configure Cell Attributes. Step 2 In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. Step 3 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 7-8.
7-28
Issue 02 (2008-06-30)
7 Handover
Step 4 Click Handover Data. A dialog box is displayed, as shown in Figure 7-9.
Issue 02 (2008-06-30)
7-29
7 Handover
Step 5 Click Advanced. A dialog box is displayed as shown in Figure 7-10. You can set corresponding parameters.
7-30
Issue 02 (2008-06-30)
7 Handover
Measurement report preprocessing Preprocessing of a measurement report consists of interpolation and filtering. Figure 7-11 shows the parameter configuration.
Figure 7-11 Filter/penalty data configuration
The parameters are as follows:

Allowed M.R Number Lost Filter Length for TCH Level Filter Length for TCH Qual
Issue 02 (2008-06-30)
7 Handover
l
Filter Length for SDCCH Level Filter Length for SDCCH Qual Filter Length for Ncell RX_LEV Filter Length for TA
Handover Penalty The handover penalty consists of handover failure penalty, BQ handover penalty, TA handover penalty, fast movement handover penalty, penalty of fast movement handover from a micro cell to a macro cell, and concentric cell handover penalty. Figure 7-11 and Figure 7-10 show the parameter configuration. The parameters are as follows:

Penalty Allowed Penalty Level after HO Fail Penalty Level after BQ HO RscPenaltyTimer UmPenaltyTimer CfgPenaltyTimer Penalty Time after BQ HO(s) Penalty Level after TA HO Penalty Time after TA HO(s) Penalty Time after AMR TCHF-H HO Fail(s)
Neighbor Cell Queuing The neighbor cell queuing consists of basic cell queuing and adjustment based on network characteristics. Figure 7-10, Figure 7-7, and Figure 7-12 show the parameter configuration.
Figure 7-12 Cell handover data configuration


l
7 Handover
Min DL level on Candidate Cell Min UP Power on HO Candidate Cell Min Access Level Offset Layer of the Cell Cell Priority Load HO Threshold Load Req.on Candidate Cell Inter-layer HO Threshold Inter-layer HO Hysteresis
TA Handover Configuration of TA handover parameters is shown in Figure 7-9 and Figure 7-13.
Figure 7-13 Emergency handover parameters configuration

l
TA HO Allowed TA Threshold
BQ Handover Configuration of BQ handover parameters is shown in Figure 7-9 and Figure 7-13. The parameters are as follows:

BQ HO Allowed DL Qual. Threshold UL Qual. Threshold DLQuaLimitAMRFR ULQuaLimitAMRFR

Issue 02 (2008-06-30)
7 Handover
l
DLQuaLimitAMRHR ULQuaLimitAMRHR
Rapid Level Drop Handover Configuration of rapid level drop handover parameters is shown in Figure 7-9 and Figure 7-13. The parameters are as follows:

Rx_Level_Drop HO Allowed Filter Parameter A1A8 Filter Parameter B
Interference Handover Configuration of interference handover parameters is shown in Figure 7-9 and Figure 7-13. The parameters are as follows:

Interference HO Allowed RXQUAL1 RXQUAL2 RXQUAL3 RXQUAL4 RXQUAL5 RXQUAL6 RXQUAL7 RXQUAL8 RXQUAL9 RXQUAL10 RXQUAL11 RXQUAL12 RXLEVOff
No Downlink Measurement Report Handover Figure 7-13 and Figure 7-13 show the configuration of no downlink measurement report handover parameters. The parameters are as follows:

No Dl Mr.HO Allowed No Dl Mr.Ul Qual HO Limit Cons. No Dl Mr. HO Allowed Limit
Load Handover Figure 7-9 and Figure 7-12 show the configuration of load handover parameters. The parameters are as follows:

Load HO Allowed System Flux Threshold for Load HO Load HO Threshold

7-34

l
7 Handover
Load Req.on Candidate Cell Load HO Bandwidth Load HO Step Period Load HO Step Level
Edge Handover Figure 7-9 shows the configuration of edge handover parameters. The parameters are as follows:

Fringe HO Allowed Edge HO AdjCell Watch Time(s) Edge HO AdjCell Watch Time(s) Edge HO UL RX_LEV Threshold Edge HO DL RX_LEV Threshold Edge HO Watch Time(s) Edge HO Valid Time(s)
Fast-Moving Micro Cell Handover Configuration of the parameters of the fast-moving micro cell handover from a micro cell to a macro cell is shown in Figure 7-9 and Figure 7-12. The parameters are as follows:

MS Fast Moving HO Allowed MS Fast-moving Watch Cells MS Fast-moving Valid Cells MS Fast-moving Time Threshold
Inter-Layer Handover Configuration of inter-layer handover parameters is shown in Figure 7-7 and Figure 7-12. The parameters in the previous dialog boxes are listed in Neighbor cell queuing.
PBGT Handover Configuration of PBGT handover parameters is shown in Figure 7-7 and Figure 7-9. The parameters are as follows:

PBGT HO Threshold PBGT HO Allowed PBGT Watch Time(s) PBGT Valid Time(s)
Quick handover Configuration of fast movement handover parameters is shown in Figure 7-9 and Figure 7-14.

Quick Handover Enable Quick Handover Up Triger Level(dB) Quick Handover Down Triger Level(dB) Quick Move Speed Thres(m/s) Quick Handover Static Time(0.5s)
Issue 02 (2008-06-30)
7 Handover

Quick Handover Last Time (0.5s) Serving Cell Filter Length MR Number Neighbor Cell Filter Length MR Number Quick Handover Punish Time Ignore Measurement Report Number Quick Handover Offset(dB) Quick Handover Punish Value(dB) Quick Handover Punish Time(s) Chain Neighbor Cell
NOTE
For the setting of Chain Neighbor Cell, refer to Figure 7-7.
Figure 7-14 Quick handover parameters configuration
AMR Handover Refer to 11 AMR. Better 3G Cell Handover Refer to 8 2G/3G Interoperability. Data Configuration of the Neighbor Cell Data configuration of neighbor cell is shown in Figure 7-7. The parameters are as follows:

Min Access Level Offset PBGT HO Threshold Adjacent Cell Inter-layer HO Hysteresis
----End
7 Handover
7.4.2 Configuring Power Boost Before Handover

This describes how to configure power boost before handover on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page. Then, select Configure Cell Attributes. Step 2 In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. Step 3 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 7-15. Figure 7-15 Set Cell Attributes dialog box
Issue 02 (2008-06-30)
7-37
7 Handover
Step 4 Click Other Attributes. A dialog box is displayed, as shown in Figure 7-16. Set Power Boost before HO enabled or not. Figure 7-16 Set Other Parameter dialog box
Step 5 Click OK. The configuration is complete. ----End

This lists the performance counters related to handover.
Alarms
None
Counters
Table 7-5 lists the counters related to handover.
7 Handover
Table 7-5 Counters related to handover Counter H3000 H3009 H3010 H3017 H3018 H3020 H3029 H3020A H3029A H302B H302G H3020C H3027Cb H3028Cb H3027Ca H3028Ca H302Da Description Internal Intra-Cell Handover Requests (SDCCH) Internal Intra-Cell Handover Requests (TCH) Internal Intra-Cell Handover Commands (SDCCH) Internal Intra-Cell Handover Commands (TCHF) Internal Intra-Cell Handover Commands (TCHH) Failed Internal Intra-Cell Handovers (SDCCH) Failed Internal Intra-Cell Handovers (TCH) Failed Internal Intra-Cell Handovers (Channel Unavailable) (SDCCH) Failed Internal Intra-Cell Handovers (Channel Unavailable) (TCH) Failed Internal Intra-Cell Handovers (Terrestrial Resource Request Failed) Failed Internal Intra-Cell Handovers (A Interface Failure) Failed Internal Intra-Cell Handovers (Timer Expired) (SDCCH) Failed Internal Intra-Cell Handovers (Timer Expired) (TCHF) (Signaling Channel) Failed Internal Intra-Cell Handovers (Timer Expired) (TCHH) (Signaling Channel) Failed Internal Intra-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel) Failed Internal Intra-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Unspecified) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Channel Unacceptable) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Timer Expired)
H302Db
H302Dc
Issue 02 (2008-06-30)
7 Handover
Counter H302Dd
Description Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, No Activity on the Radio Path) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Preemptive Release) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Handover Failed, Timing Advance out of Range) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Channel Mode Unavailable) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Frequency Unavailable) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Call Already Cleared) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Semantically Incorrect Message) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Invalid Mandatory Information) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Message Type Non-existent or Not Implemented) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Message Type Not Compatible with Protocol State) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Conditional IE Error) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (No Cell Allocation Available) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Protocol Error Unspecified) Failed Internal Intra-Cell Handovers (Reconnection to Old Channels) (Other Causes)
H302De
H302Df
H302Dg
H302Dh
H302Di
H302Dj
H302Dk
H302Dl
H302Dm
H302Dn
H302Do
H302Dp
H302Dq
7-40
Issue 02 (2008-06-30)
7 Handover
Counter H3002 H3001 H3012 H3011 H3022A H3021A H3022M H3021M H3003A H3003B H3004A H3004B H3013A H3013B H3014A H3014B H3023A H3023B H3024A
Description Internal Intra-Cell Handover Requests (Underlay to Overlay) Internal Intra-Cell Handover Requests (Overlay to Underlay) Internal Intra-Cell Handover Commands (Underlay to Overlay) Internal Intra-Cell Handover Commands (Overlay to Underlay) Failed Internal Intra-Cell Handovers (Channel Unavailable) (Underlay to Overlay) Failed Internal Intra-Cell Handovers (Channel Unavailable) (Overlay to Underlay) Failed Internal Intra-Cell Handovers (Other Causes) (Underlay to Overlay) Failed Internal Intra-Cell Handovers (Other Causes) (Overlay to Underlay) Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHF-TCHH) Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHH-TCHF) Internal Intra-Cell Handover Requests (Dynamic Conversion, TCH-SDCCH) Internal Intra-Cell Handover Requests (Dynamic Conversion, SDCCH-TCH) Internal Intra-Cell Handover Commands (Dynamic Conversion, TCHF-TCHH) Internal Intra-Cell Handover Commands (Dynamic Conversion, TCHH-TCHF) Internal Intra-Cell Handover Commands (Dynamic Conversion, TCH-SDCCH) Internal Intra-Cell Handover Commands (Dynamic Conversion, SDCCH-TCH) Failed Internal Intra-Cell Handovers (Dynamic Conversion, TCHF-TCHH) Failed Internal Intra-Cell Handovers (Dynamic Conversion, TCHH-TCHF) Failed Internal Intra-Cell Handovers (Dynamic Conversion, TCH-SDCCH)
Issue 02 (2008-06-30)
7-41
7 Handover
Counter H3024B H3055A H3055B H3005A H3005B H3015A H3015B H3025A H3025B H3040 H3047 H3048 H3200W H3200X H3200Y H3200Z H3209W H3209X H3209Y
Description Failed Internal Intra-Cell Handovers (Dynamic Conversion, SDCCH-TCH) Internal Intra-Cell Handovers Not Initiated (AMR) (TCHF-TCHH) Internal Intra-Cell Handovers Not Initiated (AMR) (TCHH-TCHF) Internal Intra-Cell Handover Requests (AMR) (TCHF-TCHH) Internal Intra-Cell Handover Requests (AMR) (TCHH-TCHF) Internal Intra-Cell Handover Commands (AMR) (TCHF-TCHH) Internal Intra-Cell Handover Commands (AMR) (TCHH-TCHF) Failed Internal Intra-Cell Handovers (AMR) (TCHF-TCHH) Failed Internal Intra-Cell Handovers (AMR) (TCHH-TCHF) Internal Intra-Cell Handover Detection Messages Received by BSC (SDCCH) Internal Intra-Cell Handover Detection Messages Received by BSC (TCHF) Internal Intra-Cell Handover Detection Messages Received by BSC (TCHH) Incoming Internal Inter-Cell Handover Requests (SDCCH) (900/850-900/850) Incoming Internal Inter-Cell Handover Requests (SDCCH) (1800/1900-1800/1900) Incoming Internal Inter-Cell Handover Requests (SDCCH) (900/850-1800/1900) Incoming Internal Inter-Cell Handover Requests (SDCCH) (1800/1900-900/850) Incoming Internal Inter-Cell Handover Requests (TCH) (900/850-900/850) Incoming Internal Inter-Cell Handover Requests (TCH) (1800/1900-1800/1900) Incoming Internal Inter-Cell Handover Requests (TCH) (900/850-1800/1900)
7-42
Issue 02 (2008-06-30)
7 Handover
Counter H3209Z H3210W H3210X H3210Y H3210Z H3217W H3217X H3217Y H3217Z H3218W H3218X H3218Y H3218Z H3220W H3220X H3220Y H3220Z H3229W H3229X
Description Incoming Internal Inter-Cell Handover Requests (TCH) (1800/1900-900/850) Incoming Internal Inter-Cell Handover Responses (SDCCH) (900/850-900/850) Incoming Internal Inter-Cell Handover Responses (SDCCH) (1800/1900-1800/1900) Incoming Internal Inter-Cell Handover Responses (SDCCH) (900/850-1800/1900) Incoming Internal Inter-Cell Handover Responses (SDCCH) (1800/1900-900/850) Incoming Internal Inter-Cell Handover Responses (TCHF) (900/850-900/850) Incoming Internal Inter-Cell Handover Responses (TCHF) (1800/1900-1800/1900) Incoming Internal Inter-Cell Handover Responses (TCHF) (900/850-1800/1900) Incoming Internal Inter-Cell Handover Responses (TCHF) (1800/1900-900/850) Incoming Internal Inter-Cell Handover Responses (TCHH) (900/850-900/850) Incoming Internal Inter-Cell Handover Responses (TCHH) (1800/1900-1800/1900) Incoming Internal Inter-Cell Handover Responses (TCHH) (900/850-1800/1900) Incoming Internal Inter-Cell Handover Responses (TCHH) (1800/1900-900/850) Failed Incoming Internal Inter-Cell Handovers (SDCCH) (900/850-900/850) Failed Incoming Internal Inter-Cell Handovers (SDCCH) (1800/1900-1800/1900) Failed Incoming Internal Inter-Cell Handovers (SDCCH) (900/850-1800/1900) Failed Incoming Internal Inter-Cell Handovers (SDCCH) (1800/1900-900/850) Failed Incoming Internal Inter-Cell Handovers (TCH) (900/850-900/850) Failed Incoming Internal Inter-Cell Handovers (TCH) (1800/1900-1800/1900)
Issue 02 (2008-06-30)
7-43
7 Handover
Counter H3229Y H3229Z H3220A H3229A H322B H322D H322G H3220C H3227Cb H3228Cb H3227Ca H3228Ca H3240 H3247 H3248 H3100W
Description Failed Incoming Internal Inter-Cell Handovers (TCH) (900/850-1800/1900) Failed Incoming Internal Inter-Cell Handovers (TCH) (1800/1900-900/850) Failed Incoming Internal Inter-Cell Handovers (No Channel Available) (SDCCH) Failed Incoming Internal Inter-Cell Handovers (No Channel Available) (TCH) Failed Incoming Internal Inter-Cell Handovers (Terrestrial Resource Request Failed) Failed Incoming Internal Inter-Cell Handovers (Reconnection to Old Channels) Failed Incoming Internal Inter-Cell Handovers (A Interface Failure) Failed Incoming Internal Inter-Cell Handovers (Timer Expired) (SDCCH) Failed Incoming Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Signaling Channel) Failed Incoming Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Signaling Channel) Failed Incoming Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel) Failed Incoming Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel) Incoming Internal Inter-Cell Handover Detection Messages Received by BSC (SDCCH) Incoming Internal Inter-Cell Handover Detection Messages Received by BSC (TCHF) Incoming Internal Inter-Cell Handover Detection Messages Received by BSC (TCHH) Outgoing Internal Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry) (900/850-900/850) Outgoing Internal Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing Internal Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry) (900/850-1800/1900)
H3100X
H3100Y
7-44
7 Handover
Counter H3100Z
Description Outgoing Internal Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry) (1800/1900-900/850) Outgoing Internal Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry) (900/850-900/850) Outgoing Internal Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing Internal Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry) (900/850-1800/1900) Outgoing Internal Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry) (1800/1900-900/850) Outgoing Internal Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry) (900/850-900/850) Outgoing Internal Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing Internal Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry) (900/850-1800/1900) Outgoing Internal Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry) (1800/1900-900/850) Outgoing Internal Inter-Cell Handover Requests (Directed Retry) (900/850-900/850) Outgoing Internal Inter-Cell Handover Requests (Directed Retry) (1800/1900-1800/1900) Outgoing Internal Inter-Cell Handover Requests (Directed Retry) (900/850-1800/1900) Outgoing Internal Inter-Cell Handover Requests (Directed Retry) (1800/1900-900/850) Outgoing Internal Inter-Cell Handover Command (SDCCH) (Excluding Directed Retry) (900/850-900/850) Outgoing Internal Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry) (1800/1900-1800/1900)
H3107W
H3107X
H3107Y
H3107Z
H3108W
H3108X
H3108Y
H3108Z
H3101W H3101X H3101Y H3101Z H3110W
H3110X
Issue 02 (2008-06-30)
7 Handover
Counter H3110Y
Description Outgoing Internal Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry) (900/850-1800/1900) Outgoing Internal Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry) (1800/1900-900/850) Outgoing Internal Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry) (900/850-900/850) Outgoing Internal Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing Internal Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry) (900/850-1800/1900) Outgoing Internal Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry) (1800/1900-900/850) Outgoing Internal Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry) (900/850-900/850) Outgoing Internal Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing Internal Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry) (900/850-1800/1900) Outgoing Internal Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry) (1800/1900-900/850) Outgoing Internal Inter-Cell Handover Commands (Directed Retry) (900/850-900/850) Outgoing Internal Inter-Cell Handover Commands (Directed Retry) (1800/1900-1800/1900) Outgoing Internal Inter-Cell Handover Commands (Directed Retry) (900/850-1800/1900) Outgoing Internal Inter-Cell Handover Commands (Directed Retry) (1800/1900-900/850)
H3110Z
H3117W
H3117X
H3117Y
H3117Z
H3118W
H3118X
H3118Y
H3118Z
H3111W H3111X
H3111Y H3111Z
7-46
Issue 02 (2008-06-30)
7 Handover
Counter H3120W
Description Failed Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry) (900/850-900/850) Failed Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry) (1800/1900-1800/1900) Failed Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry) (900/850-1800/1900) Failed Outgoing Internal Inter-Cell Handovers (SDCCH) (Excluding Directed Retry) (1800/1900-900/850) Failed Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry) (900/850-900/850) Failed Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry) (1800/1900-1800/1900) Failed Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry) (900/850-1800/1900) Failed Outgoing Internal Inter-Cell Handovers (TCHF) (Excluding Directed Retry) (1800/1900-900/850) Failed Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry) (900/850-900/850) Failed Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry) (1800/1900-1800/1900) Failed Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry) (900/850-1800/1900) Failed Outgoing Internal Inter-Cell Handovers (TCHH) (Excluding Directed Retry) (1800/1900-900/850) Failed Outgoing Internal Inter-Cell Handovers (Directed Retry) (900/850-900/850) Failed Outgoing Internal Inter-Cell Handovers (Directed Retry) (1800/1900-1800/1900)
H3120X
H3120Y
H3120Z
H3127W
H3127X
H3127Y
H3127Z
H3128W
H3128X
H3128Y
H3128Z
H3121W H3121X
Issue 02 (2008-06-30)
7-47
7 Handover
Counter H3121Y H3121Z H312A H312B H312G H3120C
Description Failed Outgoing Internal Inter-Cell Handovers (Directed Retry) (900/850-1800/1900) Failed Outgoing Internal Inter-Cell Handovers (Directed Retry) (1800/1900-900/850) Failed Outgoing Internal Inter-Cell Handovers (No Channel Available) Failed Outgoing Internal Inter-Cell Handovers (Terrestrial Resource Request Failed) Failed Outgoing Internal Inter-Cell Handovers (A Interface Failure) Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (SDCCH) (Excluding Directed Retry) Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Signaling Channel) Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Signaling Channel) Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHF) (Traffic Channel) Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (TCHH) (Traffic Channel) Failed Outgoing Internal Inter-Cell Handovers (Timer Expired) (Directed Retry) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Unspecified) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Channel Unacceptable) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Timer Expired) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, No Activity on the Radio Path) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Preemptive Release)
H3127Cb H3128Cb H3127Ca H3128Ca H3121C H312Da
H312Db
H312Dc
H312Dd
H312De
7-48
Issue 02 (2008-06-30)
7 Handover
Counter H312Df
Description Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Handover Failed, Timing Advance out of Range) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Channel Mode Unavailable) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Frequency Unavailable) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Call Already Cleared) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Semantically Incorrect Message) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Invalid Mandatory Information) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Message Type Non-existent or Not Implemented) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Message Type Not Compatible with Protocol State) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Conditional IE Error) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (No Cell Allocation Available) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Protocol Error Unspecified) Failed Outgoing Internal Inter-Cell Handovers (Reconnection to Old Channels) (Other Causes) Outgoing Internal Inter-Cell Handover Requests (Uplink Quality) Outgoing Internal Inter-Cell Handover Requests (Downlink Quality) Outgoing Internal Inter-Cell Handover Requests (Uplink Strength)
H312Dg
H312Dh
H312Di
H312Dj
H312Dk
H312Dl
H312Dm
H312Dn
H312Do
H312Dp
H312Dq H310A H310B H310C
Issue 02 (2008-06-30)
7 Handover
Counter H310D H310E H310F H310G H310H H310I H310J H310L H311A H311B H311C H311D H311E H311F H311G H311H H311I H311J H311L
Description Outgoing Internal Inter-Cell Handover Requests (Downlink Strength) Outgoing Internal Inter-Cell Handover Requests (Timing Advance) Outgoing Internal Inter-Cell Handover Requests (Better Cell) Outgoing Internal Inter-Cell Handover Requests (Load) Outgoing Internal Inter-Cell Handover Requests (Rapid Level Drop) Outgoing Internal Inter-Cell Handover Requests (MSC Intervention) Outgoing Internal Inter-Cell Handover Requests (OM Intervention) Outgoing Internal Inter-Cell Handover Requests (Other Causes) Outgoing Internal Inter-Cell Handover Commands (Uplink Quality) Outgoing Internal Inter-Cell Handover Commands (Downlink Quality) Outgoing Internal Inter-Cell Handover Commands (Uplink Strength) Outgoing Internal Inter-Cell Handover Commands (Downlink Strength) Outgoing Internal Inter-Cell Handover Commands (Timing Advance) Outgoing Internal Inter-Cell Handover Commands (Better Cell) Outgoing Internal Inter-Cell Handover Commands (Load) Outgoing Internal Inter-Cell Handover Commands (Rapid Level Drop) Outgoing Internal Inter-Cell Handover Commands (MSC Intervention) Outgoing Internal Inter-Cell Handover Commands (OM Intervention) Outgoing Internal Inter-Cell Handover Commands (Other Causes)
7-50
Issue 02 (2008-06-30)
7 Handover
Counter H3122A H3122B H3122C H3122D H3122E H3122F H3122G H3122H H3122I H3122J H3122L H3400W H3400X H3400Y H3400Z H3409W H3409X H3409Y H3409Z
Description Failed Outgoing Internal Inter-Cell Handovers (Uplink Quality) Failed Outgoing Internal Inter-Cell Handovers (Downlink Quality) Failed Outgoing Internal Inter-Cell Handovers (Uplink Strength) Failed Outgoing Internal Inter-Cell Handovers (Downlink Strength) Failed Outgoing Internal Inter-Cell Handovers (Timing Advance) Failed Outgoing Internal Inter-Cell Handovers (Better Cell) Failed Outgoing Internal Inter-Cell Handovers (Load) Failed Outgoing Internal Inter-Cell Handovers (Rapid Level Drop) Failed Outgoing Internal Inter-Cell Handovers (MSC Intervention) Failed Outgoing Internal Inter-Cell Handovers (OM Intervention) Failed Outgoing Internal Inter-Cell Handovers (Other Causes) Incoming External Inter-Cell Handover Requests (SDCCH) (900/850-900/850) Incoming External Inter-Cell Handover Requests (SDCCH) (1800/1900-1800/1900) Incoming External Inter-Cell Handover Requests (SDCCH) (900/850-1800/1900) Incoming External Inter-Cell Handover Requests (SDCCH) (1800/1900-900/850) Incoming External Inter-Cell Handover Requests (TCH) (900/850-900/850) Incoming External Inter-Cell Handover Requests (TCH) (1800/1900-1800/1900) Incoming External Inter-Cell Handover Requests (TCH) (900/850-1800/1900) Incoming External Inter-Cell Handover Requests (TCH) (1800/1900-900/850)
Issue 02 (2008-06-30)
7-51
7 Handover
Counter H3410W H3410X H3410Y H3410Z H3417W H3417X H3417Y H3417Z H3418W H3418X H3418Y H3418Z H3420W H3420X H3420Y H3420Z H3429W H3429X H3429Y
Description Incoming External Inter-Cell Handover Responses (SDCCH) (900/850-900/850) Incoming External Inter-Cell Handover Responses (SDCCH) (1800/1900-1800/1900) Incoming External Inter-Cell Handover Responses (SDCCH) (900/850-1800/1900) Incoming External Inter-Cell Handover Responses (SDCCH) (1800/1900-900/850) Incoming External Inter-Cell Handover Responses (TCHF) (900/850-900/850) Incoming External Inter-Cell Handover Responses (TCHF) (1800/1900-1800/1900) Incoming External Inter-Cell Handover Responses (TCHF) (900/850-1800/1900) Incoming External Inter-Cell Handover Responses (TCHF) (1800/1900-900/850) Incoming External Inter-Cell Handover Responses (TCHH) (900/850-900/850) Incoming External Inter-Cell Handover Responses (TCHH) (1800/1900-1800/1900) Incoming External Inter-Cell Handover Responses (TCHH) (900/850-1800/1900) Incoming External Inter-Cell Handover Responses (TCHH) (1800/1900-900/850) Failed Incoming External Inter-Cell Handovers (SDCCH) (900/850-900/850) Failed Incoming External Inter-Cell Handovers (SDCCH) (1800/1900-1800/1900) Failed Incoming External Inter-Cell Handovers (SDCCH) (900/850-1800/1900) Failed Incoming External Inter-Cell Handovers (SDCCH) (1800/1900-900/850) Failed Incoming External Inter-Cell Handovers (TCH) (900/850-900/850) Failed Incoming External Inter-Cell Handovers (TCH) (1800/1900-1800/1900) Failed Incoming External Inter-Cell Handovers (TCH) (900/850-1800/1900)
7-52
Issue 02 (2008-06-30)
7 Handover
Counter H3429Z H3401B H3401C H3401D
Description Failed Incoming External Inter-Cell Handovers (TCH) (1800/1900-900/850) Incoming External Inter-Cell Handover TCH Requests (TCHF Only) Incoming External Inter-Cell Handover TCH Requests (TCHH Only) Incoming External Inter-Cell Handover TCH Requests (TCHF Preferred,Channel Type Unchangeable) Incoming External Inter-Cell Handover TCH Requests (TCHH Preferred, Channel Type Unchangeable) Incoming External Inter-Cell Handover TCH Requests (TCHF Preferred, Channel Type Changeable) Incoming External Inter-Cell Handover TCH Requests (TCHH Preferred, Channel Type Changeable) Incoming External Inter-Cell Handover TCH Requests (TCHF or TCHH, Channel Type Unchangeable) Incoming External Inter-Cell Handover TCH Requests (TCHF or TCHH, Channel Type Changeable) Failed Incoming External Inter-Cell Handovers (Invalid Message) Failed Incoming External Inter-Cell Handovers (No Channel Available) (SDCCH) Failed Incoming External Inter-Cell Handovers (No Channel Available) (TCH) Failed Incoming External Inter-Cell Handovers (CIC Unavailable) Failed Incoming External Inter-Cell Handovers (CIC Allocated) Failed Incoming External Inter-Cell Handovers (Terrestrial Resource Request Failed) Failed Incoming External Inter-Cell Handovers (Clear Commands Sent By MSC)
H3401E
H3401G
H3401H
H3401F
H3401I
H342I H3420A H3429A H342E H342F H342B H342H
Issue 02 (2008-06-30)
7-53
7 Handover
Counter H3420C H3429Cb H3429Ca H3440 H3447 H3448 H3300W
Description Failed Incoming External Inter-Cell Handovers (Timer Expired) (SDCCH) Failed Incoming External Inter-Cell Handovers (Timer Expired) (TCH) (Signaling Channel) Failed Incoming External Inter-Cell Handovers (Timer Expired) (TCH) (Traffic Channel) Incoming External Inter-Cell Handover Detection Messages Received by BSC (SDCCH) Incoming External Inter-Cell Handover Detection Messages Received by BSC (TCHF) Incoming External Inter-Cell Handover Detection Messages Received by BSC (TCHH) Outgoing External Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry) (900/850-900/850) Outgoing External Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing External Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry) (900/850-1800/1900) Outgoing External Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry) (1800/1900-900/850) Outgoing External Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry) (900/850-900/850) Outgoing External Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing External Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry) (900/850-1800/1900) Outgoing External Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry) (1800/1900-900/850) Outgoing External Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry) (900/850-900/850)
H3300X
H3300Y
H3300Z
H3310W
H3310X
H3310Y
H3310Z
H3317W
7-54
Issue 02 (2008-06-30)
7 Handover
Counter H3317X
Description Outgoing External Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing External Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry) (900/850-1800/1900) Outgoing External Inter-Cell Handover Commands (TCHF) (Excluding Directed Retry) (1800/1900-900/850) Outgoing External Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry) (900/850-900/850) Outgoing External Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing External Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry) (900/850-1800/1900) Outgoing External Inter-Cell Handover Commands (TCHH) (Excluding Directed Retry) (1800/1900-900/850) Outgoing External Inter-Cell Handover Commands(Directed Retry) (900/850-900/850) Outgoing External Inter-Cell Handover Commands (Directed Retry) (1800/1900-1800/1900) Outgoing External Inter-Cell Handover Commands (Directed Retry) (900/850-1800/1900) Outgoing External Inter-Cell Handover Commands(Directed Retry) (1800/1900-900/850) Failed Outgoing External Inter-Cell Handovers (SDCCH) (900/850-900/850) Failed Outgoing External Inter-Cell Handovers (SDCCH) (1800/1900-1800/1900) Failed Outgoing External Inter-Cell Handovers (SDCCH) (900/850-1800/1900) Failed Outgoing External Inter-Cell Handovers (SDCCH) (1800/1900-900/850) Failed Outgoing External Inter-Cell Handovers (TCHF) (900/850-900/850)
H3317Y
H3317Z
H3318W
H3318X
H3318Y
H3318Z
H3311W H3311X
H3311Y H3311Z H3320W H3320X H3320Y H3320Z H3327W
Issue 02 (2008-06-30)
7-55
7 Handover
Counter H3327X H3327Y H3327Z H3328W H3328X H3328Y H3328Z H3321W H3321X H3321Y H3321Z H330A H330B H330C H330D H330E H330F H330G H330H
Description Failed Outgoing External Inter-Cell Handovers (TCHF) (1800/1900-1800/1900) Failed Outgoing External Inter-Cell Handovers (TCHF) (900/850-1800/1900) Failed Outgoing External Inter-Cell Handovers (TCHF) (1800/1900-900/850) Failed Outgoing External Inter-Cell Handovers (TCHH) (900/850-900/850) Failed Outgoing External Inter-Cell Handovers (TCHH) (1800/1900-1800/1900) Failed Outgoing External Inter-Cell Handovers (TCHH) (900/850-1800/1900) Failed Outgoing External Inter-Cell Handovers (TCHH) (1800/1900-900/850) Failed Outgoing External Inter-Cell Handovers (Directed Retry) (900/850-900/850) Failed Outgoing External Inter-Cell Handovers (Directed Retry) (1800/1900-1800/1900) Failed Outgoing External Inter-Cell Handovers (Directed Retry) (900/850-1800/1900) Failed Outgoing External Inter-Cell Handovers (Directed Retry) (1800/1900-900/850) Outgoing External Inter-Cell Handover Requests (Uplink Quality) Outgoing External Inter-Cell Handover Requests (Downlink Quality) Outgoing External Inter-Cell Handover Requests (Uplink Strength) Outgoing External Inter-Cell Handover Requests (Downlink Strength) Outgoing External Inter-Cell Handover Requests (Timing Advance) Outgoing External Inter-Cell Handover Requests (Better Cell) Outgoing External Inter-Cell Handover Requests (Load) Outgoing External Inter-Cell Handover Requests (Rapid Level Drop)
7-56
Issue 02 (2008-06-30)
7 Handover
Counter H330I H330J H330L H331A H331B H331C H331D H331E H331F H331G H331H H331I H331J H331L H3322A H3322B H3322C H3322D H3322E
Description Outgoing External Inter-Cell Handover Requests (MSC Intervention) Outgoing External Inter-Cell Handover Requests (OM Intervention) Outgoing External Inter-Cell Handover Requests (Other Causes) Outgoing External Inter-Cell Handover Commands (Uplink Quality) Outgoing External Inter-Cell Handover Commands (Downlink Quality) Outgoing External Inter-Cell Handover Commands (Uplink Strength) Outgoing External Inter-Cell Handover Commands (Downlink Strength) Outgoing External Inter-Cell Handover Commands (Timing Advance) Outgoing External Inter-Cell Handover Commands (Better Cell) Outgoing External Inter-Cell Handover Commands (Load) Outgoing External Inter-Cell Handover Commands (Rapid Level Drop) Outgoing External Inter-Cell Handover Commands (MSC Intervention) Outgoing External Inter-Cell Handover Commands (OM Intervention) Outgoing External Inter-Cell Handover Commands (Other Causes) Failed Outgoing External Inter-Cell Handovers (Uplink Quality) Failed Outgoing External Inter-Cell Handovers (Downlink Quality) Failed Outgoing External Inter-Cell Handovers (Uplink Strength) Failed Outgoing External Inter-Cell Handovers (Downlink Strength) Failed Outgoing External Inter-Cell Handovers (Timing Advance)
Issue 02 (2008-06-30)
7-57
7 Handover
Counter H3322F H3322G H3322H H3322I H3322J H3322L H332Ka H332Kb
Description Failed Outgoing External Inter-Cell Handovers (Better Cell) Failed Outgoing External Inter-Cell Handovers (Load) Failed Outgoing External Inter-Cell Handovers (Rapid Level Drop) Failed Outgoing External Inter-Cell Handovers (MSC Intervention) Failed Outgoing External Inter-Cell Handovers (OM Intervention) Failed Outgoing External Inter-Cell Handovers (Other Causes) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (OM Intervention) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Equipment Failure) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (No Radio Resource Available) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Requested Terrestrial Resource Unavailable) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (BSS not Equipped) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Invalid Cell) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Requested Transcoding/Rate Adaption Unavailable) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Circuit Pool Mismatch) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Requested Speech Version Unavailable) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Ciphering Algorithm not Supported)
H332Kc
H332Kd
H332Ke H332Kf H332Kg
H332Kh
H332Ki
H332Kj
7-58
Issue 02 (2008-06-30)
7 Handover
Counter H332Kk
Description Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Terrestrial circuit already allocated) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Invalid Message) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Protocol Error between BSS and MSC) Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Other Causes) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Unspecified) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Channel Unacceptable) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Timer Expired) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, No Activity on the Radio Path) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Preemptive Release) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Handover Failed, Timing Advance out of Range) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Channel Mode Unavailable) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Frequency Unavailable) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Call Already Cleared) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Semantically Incorrect Message)
H332Kl H332Km
H332Kn H332Da
H332Db
H332Dc
H332Dd
H332De
H332Df
H332Dg
H332Dh
H332Di
H332Dj
Issue 02 (2008-06-30)
7-59
7 Handover
Counter H332Dk
Description Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Invalid Mandatory Information) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Message Type Non-existent or Not Implemented) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Message Type Not Compatible with Protocol State) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Conditional IE Error) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (No Cell Allocation Available) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Protocol Error Unspecified) Failed Outgoing External Inter-Cell Handovers (Reconnection to Old Channels) (Other Causes) Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent By MSC) (Radio Interface Message Failure) Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent By MSC) (Radio Interface Failure) Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent By MSC) (OM Intervention) Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent By MSC) (Equipment Failure) Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent By MSC) (Preemption) Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent By MSC) (Invalid Message) Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent By MSC) (Protocol Error between BSS and MSC)
H332Dl
H332Dm
H332Dn
H332Do
H332Dp
H332Dq H332Ha
H332Hb
H332Hc
H332Hd
H332He H332Hf
H332Hg
7-60
Issue 02 (2008-06-30)
7 Handover
Counter H332Hh H332G H3320L H3327Lb H3328Lb H3327La H3328La H3321L H3320C H3327Cb H3328Cb H3327Ca H3328Ca H3321C H3303 H3313 H3323 H3307W
Description Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent By MSC) (Other Causes) Failed Outgoing External Inter-Cell Handovers (A Interface Failure) Failed Outgoing External Inter-Cell Handovers (T7 Expiry) (SDCCH) Failed Outgoing External Inter-Cell Handovers (T7 Expiry) (TCHF) (Signaling Channel) Failed Outgoing External Inter-Cell Handovers (T7 Expiry) (TCHH) (Signaling Channel) Failed Outgoing External Inter-Cell Handovers (T7 Expired) (TCHF) (Traffic Channel) Failed Outgoing External Inter-Cell Handovers (T7 Expired) (TCHH) (Traffic Channel) Failed Outgoing External Inter-Cell Handovers (T7 Expired) (Directed Retry) Failed Outgoing External Inter-Cell Handovers (T8 Expiry) (SDCCH) (Excluding Directed Retry) Failed Outgoing External Inter-Cell Handovers (T8 Expiry) (TCHF) (Signaling Channel) Failed Outgoing External Inter-Cell Handovers (T8 Expiry) (TCHH) (Signaling Channel) Failed Outgoing External Inter-Cell Handovers (T8 Expired) (TCHF) (Traffic Channel) Failed Outgoing External Inter-Cell Handovers (T8 Expired) (TCHH) (Traffic Channel) Failed Outgoing External Inter-Cell Handovers (T8 Expired) (Directed Retry) Outgoing External Inter-Cell Handover Requests (Different Signaling Points) Outgoing External Inter-Cell Handover Commands (Different Signaling Points) Failed Outgoing External Inter-Cell Handovers (Different Signaling Points) Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry) (900/850-900/850)
Issue 02 (2008-06-30)
7-61
7 Handover
Counter H3307X
Description Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry) (900/850-1800/1900) Outgoing External Inter-Cell Handover Requests (TCHF) (Excluding Directed Retry) (1800/1900-900/850) Outgoing External Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry) (900/850-900/850) Outgoing External Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry) (1800/1900-1800/1900) Outgoing External Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry) (900/850-1800/1900) Outgoing External Inter-Cell Handover Requests (TCHH) (Excluding Directed Retry) (1800/1900-900/850) Outgoing External Inter-Cell Handover Requests (Directed Retry) (900/850-900/850) Outgoing External Inter-Cell Handover Requests (Directed Retry) (1800/1900-1800/1900) Outgoing External Inter-Cell Handover Requests (Directed Retry) (900/850-1800/1900) Outgoing External Inter-Cell Handover Requests (Directed Retry) (1800/1900-900/850) Cell Incoming Handover Requests Failed Cell Incoming Handovers (Congestion) Failed Cell Incoming Handovers (Other Causes) Cell Outgoing Handover Commands (Uplink Quality) Cell Outgoing Handover Commands (Downlink Quality) Cell Outgoing Handover Commands (Uplink Strength)
H3307Y
H3307Z
H3308W
H3308X
H3308Y
H3308Z
H3301W H3301X H3301Y H3301Z H380 H382A H382M H371A H371B H371C
7-62
Issue 02 (2008-06-30)
7 Handover
Counter H371D H371E H371F H371G H371H H371I H371J H371L H372A H372B H372C H372D H372E H372F H372G H372H H372I H372J H372L S3300C S3301C
Description Cell Outgoing Handover Commands (Downlink Strength) Cell Outgoing Handover Commands (Timing Advance) Cell Outgoing Handover Commands (Better Cell) Cell Outgoing Handover Commands (Load) Cell Outgoing Handover Commands (Rapid Level Drop) Cell Outgoing Handover Commands (MSC Intervention) Cell Outgoing Handover Commands (OM Intervention) Cell Outgoing Handover Commands (Other Causes) Failed Cell Outgoing Handovers (Uplink Quality) Failed Cell Outgoing Handovers (Downlink Quality) Failed Cell Outgoing Handovers (Uplink Strength) Failed Cell Outgoing Handovers (Downlink Strength) Failed Cell Outgoing Handovers (Timing Advance) Failed Cell Outgoing Handovers (Better Cell) Failed Cell Outgoing Handovers (Load) Failed Cell Outgoing Handovers (Rapid Level Drop) Failed Cell Outgoing Handovers (MSC Intervention) Failed Cell Outgoing Handovers (OM Intervention) Failed Cell Outgoing Handovers (Other Causes) Number of MRs during Handover Initiation (Uplink Receive Level Rank = 0) Number of MRs during Handover Initiation (Uplink Receive Level Rank = 1)
Issue 02 (2008-06-30)
7-63
7 Handover
Counter S3302C S3303C S3304C S3305C S3306C S3307C S3310C S3311C S3312C S3313C S3314C S3315C S3316C S3317C AS330C AS331C AS330A AS332A AS330B
Description Number of MRs during Handover Initiation (Uplink Receive Level Rank = 2) Number of MRs during Handover Initiation (Uplink Receive Level Rank = 3) Number of MRs during Handover Initiation (Uplink Receive Level Rank = 4) Number of MRs during Handover Initiation (Uplink Receive Level Rank = 5) Number of MRs during Handover Initiation (Uplink Receive Level Rank = 6) Number of MRs during Handover Initiation (Uplink Receive Level Rank = 7) Number of MRs during Handover Initiation (Uplink Receive Quality Rank = 0) Number of MRs during Handover Initiation (Uplink Receive Quality Rank = 1) Number of MRs during Handover Initiation (Uplink Receive Quality Rank = 2) Number of MRs during Handover Initiation (Uplink Receive Quality Rank = 3) Number of MRs during Handover Initiation (Uplink Receive Quality Rank = 4) Number of MRs during Handover Initiation (Uplink Receive Quality Rank = 5) Number of MRs during Handover Initiation (Uplink Receive Quality Rank = 6) Number of MRs during Handover Initiation (Uplink Receive Quality Rank = 7) Mean Uplink Receiving Level during Handover Initiation Mean Uplink Receive Quality during Handover Initiation Mean Uplink Receive Level during Concentric Cell Handover Initiation (Overlay to Underlay) Mean Downlink Receive Level during Concentric Cell Handover Initiation (Overlay to Underlay) Mean Uplink Receive Level during Concentric Cell Handover Initiation (Underlay to Overlay)
7-64
Issue 02 (2008-06-30)
7 Handover
Counter AS332B AS334A AS334B
Description Mean Downlink Receive Level during Concentric Cell Handover Initiation (Underlay to Overlay) Mean Timing Advance during Concentric Cell Handover Initiation (Overlay to Underlay) Mean Timing Advance during Concentric Cell Handover Initiation (Underlay to Overlay)
7.6 References
The references indicate the documents about handover from the related standard organizations. The references are as follows:
l l
GSM 08.58 GSM 04.08
Issue 02 (2008-06-30)
7-65
8 2G/3G Interoperability
8
About This Chapter
2G/3G Interoperability
8.1 Overview This describes 2G/3G interoperability. The 2G/3G interoperability refers to the cell reselection and handovers between the GSM network and the WCDMA network. The 2G/3G interoperability also refers to the interactions between the GSM network and other 3G network. 8.2 Availability This lists the NEs and software required for the implementation of 2G/3G interoperability. 8.3 Technical Description This describes the 2G/3G interoperability technique, including the handover type, handover procedure, handover algorithm, and cell reselection. 8.4 Capabilities None 8.5 Implementation This describes how to configure 2G/3G interoperability and reconfigure 2G/3G interoperability. 8.6 Maintenance Information This lists the performance counters related to 2G/3G interoperability. 8.7 References
Issue 02 (2008-06-30)
8-1
8.1 Overview
This describes 2G/3G interoperability. The 2G/3G interoperability refers to the cell reselection and handovers between the GSM network and the WCDMA network. The 2G/3G interoperability also refers to the interactions between the GSM network and other 3G network.
Definition
The 2G/3G interoperability feature enables an MS to be handed over to or reselected to the GSM network if the serving cell of the MS is not covered by the WCDMA network or if the communication quality of the MS in a WCDMA cell is poor. In addition, an MS can be handed over to or reselected to the WCDMA network if the MS requires data services. When a dual-mode MS re-accesses the WCDMA network, or the MS detects that the communication quality in a WCDMA cell is better than that in a GSM cell, the MS can be handed over to or reselected to the WCDMA network if the handover or cell reselection conditions are met. Then, the MS can use the abundant services provided by the WCDMA network.
Purposes
Some problems arise at the early stage of deploying the WCDMA network. For example, the WCDMA network coverage is insufficient, and the WCDMA network needs to be optimized. Therefore, the WCDMA network will coexist with the GSM network for a long time. In this case, 2G/3G interoperability such as handovers and cell reselection ensures the continuity and availability of services. The purposes of 2G/3G interoperability are as follows:
l
Coverage Extension When an MS moves at the edge of the WCDMA network, the MS can access the GSM network. Radio coverage is thus extended.
Capacity Extension If an area is covered by the GSM network and WCDMA network, speech services are handled in the GSM network and data services are handled in the WCDMA network. This optimizes the network utilization, extends the overall capacity of the networks, and reduces the investment on constructing the networks.
Terms
Terms Cell penalty Definition If an MS making a call is handed over to a target cell and the handover fails, another handover attempt may be initiated and the handover may fail again. The target cell is penalized in this case. That is, the MS is forbidden to be handed over to the target cell within a specified period. 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.
Ping-pong handover
8-2
Issue 02 (2008-06-30)
Terms Cell Reselection
Definition 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 receive level of the serving cell with the receive levels of all BCCH carriers in the cell frequency list. When certain conditions are met, the MS initiates cell reselection to reselect a cell that provides higher quality services.

Acronyms and Abbreviation s 3GPP BCC BCCH BSC BSIC BSS CN CS CPICH FDD GPRS GSM HCS LMT PS RAN RNC RSCP SGSN SRNS Full Spelling
Third Generation Partnership Project Base Transceiver Station (BTS) Color Code Broadcast Control Channel Base Station Controller Base transceiver Station Identity Code Base Station System Core Network Circuit Switched Common Pilot Channel Frequency Division Duplex General Packet Radio Service Global System for Mobile communications Hierarchical Cell Structure Local Maintenance Terminal Packet Switched Radio Access Network Radio Network Controller Received Signal Code Power Serving GPRS Support Node Serving Radio Network System
Issue 02 (2008-06-30)
8-3
8.2 Availability
This lists the NEs and software required for the implementation of 2G/3G interoperability.
NEs Involved
Table 8-1 describes the NEs involved in 2G/3G interoperability. Table 8-1 NEs involved in 2G/3G interoperability MS
NOTE
BTS
BSC
MSC
PCU
SGSN
GGSN
HLR
Software Releases
Table 8-2 describes the versions of GBSS products that support 2G/3G interoperability. Table 8-2 GBSS products and software versions Product MSC BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM BTS3X BTS3002C Version R99 and later releases V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases G3BTS32.30000.04.1130 and later releases G3BTS36V306R002C05 and later releases
8-4
Issue 02 (2008-06-30)
Miscellaneous
To implement 2G/3G interoperability, the following is required:
l
MS The MS must be a dual-mode MS, which supports the GSM and WCDMA network. The MS must support bidirectional (2G to 3G and 3G to 2G) cell reselection and handovers.
Network 2G/3G interoperability requires the support of the BSS and NSS. The NSS and BSS must support inter-RAT cell selection, cell reselection, location update procedures, flow control during inter-RAT handovers, handover decisions, and handover signaling procedures.

This describes the 2G/3G interoperability technique, including the handover type, handover procedure, handover algorithm, and cell reselection. 8.3.1 System Messages Involved in Cell Reselection This describes the system information involved in cell reselection: SI2quater, SI2ter, and SI3. 8.3.2 Inter-RAT Measurement in Cell Reselection This describes the inter-RAT measurement of WCDMA signals in cell reselection. 8.3.3 Better 3G Cell Handover The better 3G cell handover better supports the handover from a GSM cell to a WCDMA cell. 8.3.4 2G/3G Inter-RAT Cell Reselection This describes the reselection of the dual-mode MS from a GSM cell to a WCDMA cell. 8.3.5 Types of 2G/3G Inter-RAT Handovers This describes the classification of 2G/3G inter-RAT handovers in terms of handover directions and handover decisions.
8.3.1 System Messages Involved in Cell Reselection

This describes the system information involved in cell reselection: SI2quater, SI2ter, and SI3.
l
The system message SI2quater is added. The SI2quater contains the information about the cell reselection, measurement, and report. The SI2quater has only one SI2quater Reset Octets IE in addition to the message header on the Um interface. The total length of the SI2quater is 23 bytes, the same as that of other SI2. The time and methods of sending the SI2quater are the same as those of the SI2, SI2bis, and SI2ter messages. The SI2quater contains the following parameters related to the reselection between 2G/3G systems:

Qsearch I FDD Q Offset FDD Qmin Qsearch P
The SI2quater message uses the following parameters to describe the external neighbor cells of the 3G system:

DL UARFCN Scrambling Code Diversity

NOTE
The UTRAN FDD Cell BA1 Table contains another two parameters NCELL No. and User Input FDD. The two parameters are not contained in SI2quater.
l
The system information SI2ter is modified. The SI2 and SI2bis provide only the list of neighbor GSM cells of the cell that an MS is camped on. After supporting the interoperability between the GSM and the WCDMA networks, the MS needs to obtain the WCDMA neighbor cell list of the cell it is camped on. Compared with the SI2ter in GSM 04.08, in 3GPP TS 04.18, the 3G neighbor cell frequency reselection parameter is added to the SI2ter. Therefore, in protocol 3GPP 04.18, the mode of writing the SI2ter needs to be changed. The SI2ter sent by the BSC to the BTS in 3GPP TS 04.18 is different from that in GSM 04.08. The differences are as follows:

In GSM 04.08, the Rest Octets IE in the SI2ter contains four idle bytes. In 3GPP TS 04.18, the length of the Rest Octets IE does not change, but the Rest Octets IE contains the information about the 3G cell reselection. Because of the limitation on the number of bytes, the IE of each SI2ter in 3GPP TS 04.18 contains the information about only one 3G neighbor cell frequency. The information about the 3G neighbor cell frequency can be applied to the configuration of 3G external neighbor cells.
The system information SI3 is modified. In 3GPP TS 04.18, the following contents are added to the Rest Octet IE in the SI3:
Instruction on whether the SI2quater exists:
If the FDD neighbor data is configured in the UTRAN FDD Cell BA1 Table, set Support Send 2 QUATER Flag to Yes. If the BSC supports the 2G/3G interoperability and the Inter-System Handover Enable is set to Yes, the SI3 carries the SI2quater indication when Support Send 2 QUATER Flag is set to Yes. If the Report Type is set to Enhanced Measurement Report, SI3 carries the SI2quater indication.
Instruction on whether the MS needs to report the WCDMA Classmark Change message When the BSC sends the SI3 to the MS, the Send 3G Class Flag tells the MS whether the early classmark message sent by the BSC contains the 3G classmark information. If the network requires the classmark 3 information, you are advised to set Send 3G Class Flag to Yes. In this way, the MS can quickly report the required classmark information and the query for the network can be omitted.
8.3.2 Inter-RAT Measurement in Cell Reselection

This describes the inter-RAT measurement of WCDMA signals in cell reselection. In the hybrid network between the GSM and the WCDMA, if the serving cell of the dual-mode MS is a GSM cell, the MS measures the inter-RAT WCDMA signals when reading the level of the GSM neighbor cell. When the dual-mode MS in CS domain is idle, set the Qsearch I. This parameter determines whether to start the inter-RAT measurement.
NOTE
When the MS is in PS domain, set the Qsearch P. This parameter determines whether to start the interRAT measurement.
8-6
Issue 02 (2008-06-30)
If the 3G cell reselection list (composed of the SI2ter and SI2quarter) contains only one FDD frequency, the MS can identify and reselect a new FDD frequency in the WCDMA cell within 30 seconds. Each new FDD added to the 3G cell resection list requires more reselection time of 30 seconds. If the same FDD frequency is added, the reselection time does not increase. A dual-mode MS can monitor up to 64 WCDMA cells (depending on the capability of the MS). An FDD cell has up to three FDD frequencies and each frequency supports up to 32 cells.
8.3.3 Better 3G Cell Handover

The better 3G cell handover better supports the handover from a GSM cell to a WCDMA cell.
Requirements for Trigging Better 3G Cell Handover

If a handover is triggered and if the Outgoing-RAT HO Allowed is set to Yes, then the conditions for triggering the better 3G cell handover are as follows:
l l
The 3G better cell exists. The Better 3G Cell HO Allowed is set to Yes.
NOTE
If the target better 3G cell is a TDD cell, then set the TDD 3G Better Cell HO Allowed to Yes.

The requirements for target cell selection are as follows:
l l l
The target cell is FDD cell. The MS supports FDD. Either of the following requirements is met according to the value of the FDD REP QUANT:
If the FDD REP QUANT is set to RSCP, the FDD RSCP value after filtering is greater than the RSCP Threshold for Better 3G Cell HO. If the FDD REP QUANT is set to Ec/NO, the FDD RSCP value after filtering is greater than the Ec/NO Threshold for Better 3G Cell HO.
P/N criterion is met. Assume that P indicates 3G Better Cell HO Watch Time (s) and N indicates 3G Better Cell HO Valid Time (s).
8.3.4 2G/3G Inter-RAT Cell Reselection

This describes the reselection of the dual-mode MS from a GSM cell to a WCDMA cell. Figure 8-1 shows the reselection of the dual-mode MS from a GSM cell to a WCDMA cell.
Issue 02 (2008-06-30)
8-7
Figure 8-1 Flow chart of the reselection of a dual-mode MS from a GSM cell to a WCDMA cell
Start
No
Is the License obtained? Yes
No
Is Out-going RAT HO Allowed set to Yes? Yes Does the signal level of the serving cell meet the requirement of threshold of searching for a 3G cell?
No
Yes No Is RSCP > RLA_C + Qoffset and does the condition last for more five seconds? Yes
No
Is CPICH Ec/No > FDD_Qmin and does the condition last for more than five seconds? Yes The cell reselection is complete.
End
In Figure 8-1, Qoffset indicates the FDD Q Offset and FDD_Qmin indicates FDD Qmin. The flow chart is detailed as follows: 1. Obtain and then activate the license of the 2G/3G interoperability.
8-8
Issue 02 (2008-06-30)
2.
Set Outgoing-RAT HO Allowed to Yes. Thus, the threshold of searching for 3G cells is satisfied.
l l
If the MS is in idle mode, the threshold is Qsearch I. If the MS is in packet mode, the threshold is Qsearch P.
3.
If 3G cell reselection list consisting of SI2ter and SI2quarter in the system information of the GSM cell contains the FDD, the WCDMA cell that meets the following conditions within five seconds can be the reselection cell:
l l
RSCP > RLA_C + FDD Q Offset CPICH Ec/No > FDD Qmin
NOTE
If the interval between two reselections is less than 15 seconds, the value of FDD Q Offset is increased by 5dB at the second reselection.
The FDD Q Offset and FDD Qmin are carried in the BCCH broadcast of the serving cell. If more than one WCDMA cell meets the previous requirements, the MS selects the cell with the strongest RSCP.
8.3.5 Types of 2G/3G Inter-RAT Handovers

This describes the classification of 2G/3G inter-RAT handovers in terms of handover directions and handover decisions. Based on handover directions, 2G/3G inter-RAT handovers can be classified into the following types:
l l
GSM-to-WCDMA handover WCDMA-to-GSM handover

NOTE
This document describes only the GSM-to-WCDMA handover.
Based on handover decisions, GSM-to-WCDMA handovers can be classified into the following types:
l l
OM forced handover Emergency handover

TA Handover BQ Handover Rapid Level Drop Handover Interference Handover Edge Handover Better 3G Cell Handover
Normal handover

Some handover types do not support 2G/3G inter-RAT handovers. These handover types are the load handover, hierarchical handover, PBGT handover, concentric cell handover, and fast movement handover.
8.3.6 2G/3G Inter-RAT Handover Procedure

This describes the procedure of a GSM-to-WCDMA handover in the CS domain.
If a GSM cell has a neighbor WCDMA cell, the measurement control information is sent in the system information. The dual-mode MS performs inter-RAT measurement in idle timeslots and reports the measurement results. The BSC decides whether to start an inter-RAT handover based on the measurement results. The GSM uses the time division multiple access (TDMA) technique, and the inter-RAT measurement is performed in idle timeslots. Therefore, the GSM need not support the compressed mode. Figure 8-2 shows the signaling procedure of the GSM-to-WCDMA handover. Figure 8-2 Procedure of the GSM-to-WCDMA handover in the CS domain
UE Node B RNC Target CN (3G) MSC (2G)
1.HANDOVER REQUIRED 2.PREPARE HANDOVER 3.RELOCATION REQUEST 4.RELOCATION REQUEST ACK 5.PREPARE HANDOVER RESPONSE 7.INTER-SYSTEM TO AUTRANHANDOVER COMMAND 8.RELOCATION DELECT 6.HANDOVER COMMAND
BSC
9.DCCH:HANDOVER COMPLETE
10.RELOCATION COMPLETE 11.SEND END SIGNAL REQUEST 12.CLEAR COMMAND 13.CLEAR COMPLETE 14.SEND END SIGNAL RESPONSE
Before the handover, the MS camps on a GSM cell. 1. 2. 3. 4. Based on the measurement results, the GSM network decides to hand over the MS to the WCDMA network. The BSC sends a Handover Required message to the GSM MSC. The GSM MSC sends a Prepare Handover message on the E interface to the WCDMA CN. The WCDMA CN sends a Relocation Request message to the target RNC. When the WCDMA UTRAN is ready for the handover, the RNC sends a Relocation Request ACK message to the WCDMA CN.
8-10
Issue 02 (2008-06-30)
5. 6. 7.
The WCDMA CN sends a Prepare Handover Response message on the E interface to the GSM MSC. The GSM MSC sends a Handover Command message to the BSC. Through the established radio connection, the BSC sends the MS an Inter-System to UTRAN Handover Command message, requesting the MS to perform a GSM-to-WCDMA handover. When detecting the MS, the RNC sends a Relocation Detect message to the WCDMA CN. After being handed over to the WCDMA (hard handover) network, the MS sends a Handover Complete message to the RNC.
8. 9.
10. The RNC sends the WCDMA CN a Relocation Complete message to report that the handover is complete. 11. After detecting that the MS camps on the WCDMA network, the WCDMA CN sends the GSM MSC a Send End Signal Request message, requesting the GSM MSC to release the GSM resources used by the MS. 12. After receiving the message, the GSM MSC sends the BSC a Clear Command message, requesting the BSC to release relevant resources. 13. After releasing relevant resources, the GSM BSC sends a Clear Complete message to the GSM MSC. 14. The GSM MSC responds to the WCDMA CN. The handover procedure is complete.
8.3.7 Algorithms of 2G/3G Inter-RAT Handovers

This describes the algorithms used in different phases of the 2G/3G inter-RAT handover procedure. The handover procedure and related algorithms are as follows: 1. 2. Handover Preparation On receiving the measurement result, the BSC performs interpolation and filtering. Cell penalty
l
Handover penalty assumes that when a handover fails, the cause of the handover failure lasts for a period and the cause can be eliminated. After being interpolated and filtered, the information on neighbor WCDMA cells in the measurement report can serve as the basis for deciding a handover and power control. Before handover decision, penalty is required to reduce further attempts of handover to a neighbor WCDMA cell where a previous handover fails. During the penalty, a penalty value is subtracted from the signal level of the neighbor WCDMA cell. For details, refer to Penalty Level after HO Fail. The sorting of neighbor cells uses the M and K rules in the Huawei handover algorithms. First distinguish the 3G cell, an FDD cell or a TDD cell.
3.
Basic sorting of neighbor cells

l
For an FDD cell: Determine the value of the FDD REP QUANT: RSCP or Ec/N0:
If the value is RSCP and the RSCP value after penalty is smaller than the Min RSCP Threshold, the system removes the cell from the candidate list and forbids handover to the cell.
Issue 02 (2008-06-30)
If the value is Ec/N0 and the Ec/N0 value after penalty is smaller than the Min Ec/No Threshold, the system removes the cell from the candidate list and forbids handover to the cell.
For a TDD cell: The TDD cell can only report the RSCP value. If the RSCP value after penalty is smaller than the Min RSCP Threshold, the system removes the cell from the candidate list and forbids handover to the cell.
4.
Network Characteristic Adjustment The candidate WCDMA handover cells in the measurement report should be sorted based on the receive levels and layers of the neighbor WCDMA cells. This ensures that the MS is handed over to the neighbor WCDMA cell that has the highest priority.
5.
Handover decision
l
Some 2G/3G inter-RAT handovers such as OM forced handovers, TA handovers, bad quality handovers, rapid level drop handovers, interference handovers, and edge handovers use the same handover decision algorithms as the GSM handovers. Based on the characteristics of WCDMA cells, a 3G better cell handover algorithm is used to support GSM-to-WCDMA handovers.
6.
Handover execution Based on the result of handover decision and the setting of the Inter-RAT HO Preference parameter, the BSC selects a neighbor GSM cell or a neighbor WCDMA cell to initiate a handover procedure.
8.4 Capabilities
None
8.5 Implementation
This describes how to configure 2G/3G interoperability and reconfigure 2G/3G interoperability. 8.5.1 Configuring 2G/3G Interoperability This describes how to configure 2G/3G interoperability on the BSC6000 Local Maintenance Terminal. 8.5.2 Reconfiguring 2G/3G Interoperability This describes how to add, delete, and modify a 3G external cell. It also describes how to modify 3G system message parameters and 2G/3G inter-RAT handover parameters.
8.5.1 Configuring 2G/3G Interoperability

This describes how to configure 2G/3G interoperability on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows:
1.
When applying for the 2G/3G interoperability license, ensure that Whether to activate intersystem handover & reselection under Function control items in BSC6000V900R008 Exceptional Commercial License Application Template is set to 1. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Procedure
Step 1 Configure the parameter Inter-System Handover Enable. Inter-System Handover Enable is used to control the inter-system handover and the intersystem cell reselection.
l
If Inter-System Handover Enable is set to Yes, both inter-system handover and intersystem cell reselection are allowed. If Inter-System Handover Enable is set to No, both inter-system handover and inter-system cell reselection are not allowed.
NOTE
When the 2G/3G handover function is enabled, you are advised to enable ECSC so that the system can get the classmark information of the MS with the least delay.
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target cell, and then choose Configure Cell Attributes from the shortcut menu. The Configuring Cell Attributes dialog box is displayed. Double-click the target cell in the Cell view list box to add it to the Selected cells list box. Click Next. The Configuring Cells Attributes dialog box is displayed. In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 8-3.
2. 3. 4.
Issue 02 (2008-06-30)
8-13
5.
Click Handover Data. A dialog box is displayed, as shown in Figure 8-4. Set Inter-System Handover Enable to Yes.
8-14
Issue 02 (2008-06-30)
Step 2 Configure a 3G external cell. 1. On the Management Tree tab page of theBSC6000 Local Maintenance Terminal, rightclick 3G External Cells and choose Add 3G External Cell from the shortcut menu. The Add 3G External Cell dialog box is displayed. Click Add ExtCell. A dialog box is displayed, as shown in Figure 8-5.
2.
Issue 02 (2008-06-30)
8-15
Figure 8-5 Configure 3G External Cell dialog box
3. 4. 5.
Configure the 3G external cell parameters and click OK. The upper-level dialog box is displayed. Click Finish. Under 3G External Cells on the Management Tree tab page, the newly added 3G external cell is displayed. To modify the parameters of the newly added 3G external cell, right-click it, and then choose Configure 3G External Cell from the shortcut menu. On the Management Tree tab page of theBSC6000 Local Maintenance Terminal, rightclick a cell under the BSC6000 root node, and then choose Configure Adjacent Cell from the shortcut menu. The Configuring Adjacent Cells dialog box is displayed. Add the cell in the Cell view area to the Selected cells area. Click Next. The Configuring Adjacent Cells dialog box is displayed. Select a cell from the Cells to be set area and click Set Adjacent Cells. A dialog box is displayed, as shown in Figure 8-6.
Step 3 Configure adjacent cells. 1.
2. 3. 4.
8-16
Issue 02 (2008-06-30)
Figure 8-6 Set Adjacent Relation Property dialog box
NOTE
If 3G External Cells are selected, the cells can be added to only the Single Directional Adjacent Cells list box.
Step 4 Configure parameters related to 2G/3G inter-RAT handovers. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick a cell under the BSC6000 root node, and then choose Configure Cell Attributes from the shortcut menu. The Configuring Cell Attributes dialog box is displayed. Double-click the target cell in the Cell view list box to add it to the Selected cells list box. Click Next. The Configuring Cells Attributes dialog box is displayed. In the Cells to be set area, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 8-3. Click Handover Data. A dialog box is displayed, as shown in Figure 8-4. Click Advanced, and then click the UTRAN FDD HO Data tab, as shown in Figure 8-7.
2. 3. 4. 5. 6.
Issue 02 (2008-06-30)
8-17
Figure 8-7 Configuring UTRAN FDD handover data
7.
Set the parameters and click OK. The parameters are described as follows:
l
Inter-RAT HO Preference:
If this parameter is set to Preference for 2G Cell, the BSC first selects the target handover cell from the 2G candidate cells. If this parameter is set to Preference for 3G Cell, the BSC first selects the target handover cell from the 3G candidate cells. If this parameter is set to Preference for 2G By Threshold, and if the receive level of the first candidate cell among 2G candidate cells is smaller than or equal to the HO Preference Threshold for 2G Cell, the 3G cell handover is preferred; otherwise, the 2G cell handover is preferred. If Inter-RAT HO Preference is set to Preference for 2G By Threshold, and if the receive level of the candidate cell of highest priority among 2G candidate cells is smaller than or equal to the HO Preference Threshold for 2G Cell, the 3G cell handover is preferred. If Inter-RAT HO Preference is set to Preference for 2G By Threshold, and if the receive level of the candidate cell of highest priority among 2G candidate cells is greater than the HO Preference Threshold for 2G Cell, the 2G cell handover is preferred.
HO Preference Threshold for 2G Cell:
RSCP Threshold for Better 3G CELL HO: If Inter-System Handover Enable is set to Yes and Better 3G Cell HO Allowed is also set to Yes, a better 3G cell handover is triggered when the RSCP of an adjacent 3G cell is greater than RSCP Threshold for Better 3G CELL HO.
Ec/No Threshold for Better 3G CELL HO: If Inter-System Handover Enable is set to Yes and Better 3G Cell HO Allowed is also set to Yes, a better 3G cell handover is triggered when the Ec/No of an adjacent 3G cell is greater than Ec/No Threshold for Better 3G CELL HO.
8-18
Issue 02 (2008-06-30)

l
3G Better Cell HO Watch Time(s): This parameter indicates the measurement time of the 3G better cell handover algorithm. 3G Better Cell HO Valid Time(s): This parameter indicates the valid time of the 3G better cell handover algorithm. During the decision of the 3G better cell handover algorithm, a 3G better cell handover is initiated only when the period during which the 3G cell signals satisfy the conditions of the 3G better cell handover algorithm is greater than the 3G Better Cell HO Valid Time within the 3G Better Cell HO Watch Time.
Better 3G Cell HO Allowed: This parameter indicates whether the better 3G cell handover algorithm is allowed.
If Better 3G Cell HO Allowed is set to Yes, it indicates that better 3G cell handover algorithm is allowed. If Better 3G Cell HO Allowed is set to No, it indicates that better 3G cell handover algorithm is not allowed.
Step 5 Configure 3G system message parameters. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick a cell under the BSC6000 root node, and then choose Configure Cell Attributes from the shortcut menu. The Configuring Cell Attributes dialog box is displayed. Double-click the target cell in the Cell view list box to add it to the Selected cells list box. Click Next. The Configuring Cells Attributes dialog box is displayed. In the Cells to be set area, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 8-3. Click Call Control. The Set Call Control Parameter dialog box is displayed. Click Advanced, and then click the UTRAN System Message tab, as shown in Figure 8-8.
2. 3. 4. 5. 6.
Figure 8-8 Setting UTRAN system message parameters
7.
Set the parameters and click OK. The parameters are described as follows:
Issue 02 (2008-06-30)
8-19
l
MSC Version Indication: This parameter indicates the protocol version of the MSC that is networked with the BSC. The supported signaling varies with the protocol versions.
If the GSM BSC accesses the GSM MSC, set MSC Version Indication to R98 or below. If the GSM BSC is connected to the UMTS MSC, set MSC Version Indication to R99 or above.
Report Type: This parameter indicates the type of the measurement report. Serving Band Reporting: This parameter indicates the number of cells that meet the following conditions: The cell is in the current service band; the cell is in the best cell list.
Qsearch I: This parameter indicates the level threshold for cell reselection in idle mode. In idle mode, if the parameter is set within the range [0,7] and the signal level in the serving cell is lower than the threshold, the MS starts to search for 3G cells; if the parameter is set within the range [8,15] and the signal level in the serving cell is higher than the threshold, 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 below 5, then 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.
Qsearch C Initial: This parameter indicates the threshold of level for cell reselection in CS connection mode before the BTS obtains the Qsearch C, Always or Qsearch I.
NOTE
Always means that the threshold for searching for 3G cells is not specified; that is, the MS always searches for 3G cells regardless of the receive level of the serving cell.
l
FDD Q Offset: A 3G cell can become a candidate cell only when the average receive level of the 3G cell is FDD Q Offset greater than the average receive level of the serving cell.
FDD REP QUANT: Ec/N0 indicates the Signal Noise Ratio in WCDMA, which is equivalent to C/I in GSM; RSCP indicates the Received Signal Code Power.
FDD MULTIRAT Reporting: This parameter indicates the number of UTRAN FDD cells that should be contained in a measurement report.
FDD Qmin: This parameter indicates one of the level threshold for the reselection of 3G cells. A 3G cell can be a candidate cell in cell reselection only when the receive level of the 3G cell is greater than FDD_Qmin.
Qsearch P: This parameter indicates the level threshold for cell reselection in packet mode. In packet mode, if the parameter is set within the range [0,7] and the signal level in the serving cell is lower than the threshold, the MS starts to search for 3G cells; if the parameter is
8-20
Issue 02 (2008-06-30)
set within the range [8,15] and the signal level in the serving cell is higher than the threshold, the MS starts to search for 3G cells. For example:
3G Search PRIO: This parameter indicates whether the MS is allowed to search for a 3G cell when the BISC must be decoded.
Invalid BSIC Reporting: This parameter indicates whether a cell with invalid BISC is allowed in the measurement report.
SCALE_ORDER: This parameter indicates that when the MS reports the EMR, it adds this parameter to the received signal level, and then converts the result into the RXLEV value. Value range: +0 dBm, +10 dBm, Automatic
If the SCALE_Order reported by the MS is 10dBm, 0-63 with 0 indicating -100 dBm and 63 indicating -37 dBm. If the SCALE_Order reported by the MS is 0dBm, 0-63 with 0 indicating -110 dBm and 63 indicating -47 dBm. If the SCALE_Order reported by the MS is Automatic, the MS chooses the least SCALE that is able to report the most robust level.
Qsearch C: This parameter indicates the level threshold for cell reselection in CS connection mode. In CS connection mode, if the parameter is set within the range [0,7] and the signal level in the serving cell is lower than the threshold, the MS starts to search for 3G cells; if the parameter is set within the range [8,15] and the signal level in the serving cell is higher than the threshold, the MS starts to search for 3G cells. For example:
NOTE
By default, 2G/3G inter-RAT reselection and handovers are disabled. To enable 2G/3G interRAT cell reselection and handovers, set Qsearch I and Qsearch C to 7.
l
900 Reporting Offset: This parameter indicates the reporting offset for GSM900 cells. When sorting the GSM900 cells by priority based on the frequency band, it is recommended that you first add the value of this parameter to the receive level of the GSM900 cell in the measurement report.
900 Reporting Threshold: This parameter indicates the reporting threshold for GSM900 cells. The measurement report is valid only when the receive level of the GSM900 cell in the measurement report is greater than the value of this parameter. After the measurement report is filtered, the GSM900 cell is sorted by priority.
1800 Reporting Offset:

Issue 02 (2008-06-30)
This parameter indicates the reporting offset for DCS1800 cells. When sorting the DCS1800 cells by priority based on the frequency band, it is recommended that you first add the value of this parameter to the receive level of the DCS1800 cell in the measurement report.
l
1800 Reporting Threshold: This parameter indicates the reporting threshold for DCS1800 cells. The measurement report is valid only when the receive level of the DCS1800 cell in the measurement report is greater than the value of this parameter. After the measurement report is filtered, the DCS1800 cell is sorted by priority.
FDD Reporting Offset: This parameter indicates the reporting offset for 3G cells. When sorting the priorities of 3G cells based on the frequency band, it is recommended that you first add the value of this parameter to the receive level of the 3G cell in the measurement report.
FDD Reporting Threshold: This parameter indicates the reporting threshold for 3G cells. The measurement report is valid only when the receive level of the 3G cell in the measurement report is greater than the value of this parameter. After the valid measurement report is filtered, the 3G cell is sorted by priority.
----End
8.5.2 Reconfiguring 2G/3G Interoperability

This describes how to add, delete, and modify a 3G external cell. It also describes how to modify 3G system message parameters and 2G/3G inter-RAT handover parameters.
Procedure
Step 1 Add a 3G external cell. For details, refer to Step 2 in 8.5.1 Configuring 2G/3G Interoperability. Step 2 Delete a 3G external cell. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target 3G external cell, and then choose Delete 3G External Cell from the shortcut menu, as shown in Figure 8-9.
8-22
Issue 02 (2008-06-30)
Figure 8-9 Delete 3G External Cell dialog box
2. 3. 1.
Select the target cell in the External cell list area, and then add it to the Cells to be deleted list box. Click Finish. The configuration is complete. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick 3G External Cells and choose Configure 3G External Cell from the shortcut menu. The Configure 3G External Cell dialog box is displayed. Select the target cell in the External cell list area, and then add it to the Selected cells list box. Click Next. A dialog box is displayed, as shown in Figure 8-10.
Step 3 Modify a 3G external cell.
2. 3.
Issue 02 (2008-06-30)
8-23
Figure 8-10 Configure 3G External Cell dialog box
4.
Click Set ExtCell Attributes. A dialog box is displayed, as shown in Figure 8-11. Set the parameters.
8-24
Issue 02 (2008-06-30)
Figure 8-11 Configure 3G External Cell Attributes dialog box
5. 6.
Click OK to return to the dialog box shown in Figure 8-10. Click Finish. The configuration is complete.
Step 4 Modify 3G system message parameters. For details, refer to Step 5 in 8.5.1 Configuring 2G/ 3G Interoperability. Step 5 Modify 2G/3G inter-RAT handover parameters. For details, refer to Step 4 in 8.5.1 Configuring 2G/3G Interoperability. ----End

This lists the performance counters related to 2G/3G interoperability.
Alarms
None
Counters
Table 8-3 lists the performance counters related to 2G/3G interoperability.
Table 8-3 Performance counters related to 2G/3G interoperability Counter H3600 H3609 H3610 H3617 H3618 H3620 H3627 H3628 H362J H3620A H3629A H362E H362F H362B H362H H3620C H3629Cb Description Incoming Inter-RAT Inter-Cell Handover Requests (SDCCH) Incoming Inter-RAT Inter-Cell Handover Requests (TCH) Incoming Inter-RAT Inter-Cell Handover Responses (SDCCH) Incoming Inter-RAT Inter-Cell Handover Responses (TCHF) Incoming Inter-RAT Inter-Cell Handover Responses (TCHH) Failed Incoming Inter-RAT Inter-Cell Handovers (SDCCH) Failed Incoming Inter-RAT Inter-Cell Handovers (TCHF) Failed Incoming Inter-RAT Inter-Cell Handovers (TCHH) Failed Incoming Inter-RAT Inter-Cell Handovers (Invalid Message) Failed Incoming Inter-RAT Inter-Cell Handovers (No Channel Available) (SDCCH) Failed Incoming Inter-RAT Inter-Cell Handovers (No Channel Available) (TCH) Failed Incoming Inter-RAT Inter-Cell Handovers (CIC Unavailable) Failed Incoming Inter-RAT Inter-Cell Handovers (CIC Allocated) Failed Incoming Inter-RAT Inter-Cell Handovers (Terrestrial Resource Request Failed) Failed Incoming Inter-RAT Inter-Cell Handovers (Clear Commands Sent By MSC) Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired) (SDCCH) Number of Failed Inter-RAT Incoming Cell Handovers (Timer Expired) (TCH) (Signaling Channel) Failed Incoming Inter-RAT Inter-Cell Handovers (Timer Expired) (TCH) (Traffic Channel)
H3629Ca
8-26
Issue 02 (2008-06-30)
Counter H3500 H3507 H3508 H3510 H3517 H3518 H3520 H3527 H3528 H352Da
Description Outgoing Inter-RAT Inter-Cell Handover Requests (SDCCH) (Excluding Directed Retry) Outgoing Inter-RAT Inter-Cell Handover Requests (TCHF) Outgoing Inter-RAT Inter-Cell Handover Requests (TCHH) Outgoing Inter-RAT Inter-Cell Handover Commands (SDCCH) (Excluding Directed Retry) Outgoing Inter-RAT Inter-Cell Handover Commands (TCHF) Outgoing Inter-RAT Inter-Cell Handover Commands (TCHH) Failed Outgoing Inter-RAT Inter-Cell Handovers (SDCCH) (Excluding Directed Retry) Failed Outgoing Inter-RAT Inter-Cell Handovers (TCHF) Failed Outgoing Inter-RAT Inter-Cell Handovers (TCHH) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Unspecified) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Channel Unacceptable) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, Timer Expired) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Abnormal Release, No Activity on the Radio Path) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Preemptive Release) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Handover Failed, Timing Advance out of Range) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Channel Mode Unavailable)
H352Db
H352Dc
H352Dd
H352De
H352Df
H352Dg
Issue 02 (2008-06-30)
8-27
Counter H352Dh
Description Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Frequency Unavailable) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Call Already Cleared) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Semantically Incorrect Message) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Invalid Mandatory Information) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Message Type Non-existent or Not Implemented) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Message Type Not Compatible with Protocol State) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Conditional IE Error) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (No Cell Allocation Available) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Protocol Error Unspecified) Failed Outgoing Inter-RAT Inter-Cell Handovers (Reconnection to Old Channels) (Other Causes) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (OM Intervention) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Equipment Failure) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (No Radio Resource Available) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Requested Terrestrial Resource Unavailable) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (BSS not Equipped)
H352Di
H352Dj
H352Dk
H352Dl
H352Dm
H352Dn
H352Do
H352Dp
H352Dq H352Ka H352Kb H352Kc
H352Kd
H352Ke
8-28
Counter H352Kf H352Kg
Description Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Invalid Cell) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Requested Transcoding/Rate Adaption Unavailable) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Circuit Pool Mismatch) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Requested Speech Version Unavailable) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Ciphering Algorithm not Supported) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Terrestrial circuit already allocated) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Invalid Message) Failed Outgoing Inter-RAT Inter-Cell Handovers (Handover Request Rejected) (Protocol Error between BSS and MSC) Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent By MSC) (Radio Interface Message Failure) Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent By MSC) (Radio Interface Failure) Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent By MSC) (OM Intervention) Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent By MSC) (Equipment Failure) Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent By MSC) (Preemption) Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent By MSC) (Invalid Message)
H352Kh
H352Ki
H352Kj
H352Kk
H352Kl H352Km
H352Ha
H352Hb
H352Hc
H352Hd
H352He H352Hf
Issue 02 (2008-06-30)
8-29
Counter H352Hg
Description Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent By MSC) (Protocol Error between BSS and MSC) Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent By MSC) (Other Causes) Failed Outgoing Inter-RAT Inter-Cell Handovers (A Interface Failure) Failed Outgoing Inter-RAT Inter-Cell Handovers (T7 Expired) Failed Outgoing Inter-RAT Inter-Cell Handovers (T8 Expired)
H352Hh H352G H352L H352C
8.7 References
l
3GPP TS 23.122 "Non Access Stratum functions related to Mobile Station (MS) in idle mode" 3GPP TS 24.008 "Mobile radio interface layer 3 specification; Core Network Protocols Stage 3"
8-30
Issue 02 (2008-06-30)
9 Message Tracing
9
About This Chapter
Message Tracing
9.1 Overview This describes the tracing of interface messages, link messages, and user messages for troubleshooting. 9.2 Availability This lists the NEs and software required for the implementation of message tracing. 9.3 Impact This describes the impact of message tracing on system performance and other features. 9.4 Technical Description This describes the message tracing procedure, signaling tracing, and user tracing. 9.5 Capabilities None 9.6 Implementation This describes how to configure message tracing. 9.7 Maintenance Information None. 9.8 References None
Issue 02 (2008-06-30)
9-1
9 Message Tracing
9.1 Overview
This describes the tracing of interface messages, link messages, and user messages for troubleshooting.
Definition
There are two types of message tracing: signaling tracing and user message tracing.
l
Signaling tracing involves the message tracing on the interfaces, such as A interface and Abis interface, and the message tracing on the links, such as MTP2 and LAPD. User tracing: indicates to trace the messages and status of the specified user's CM procedure.
Purposes
With the signaling messages traced on the LMT, you can troubleshoot the problems such as NE interconnection without using an external signaling tracing device.
Terms
Term OML Definition Operation and maintenance link, used to transmit the operation and maintenance information between the BSC and the BTS Radio signaling link, used for flow management and to transmit the signaling between the BTS and the BSC and that on the Um interface Base station subsystem application part: It transfers L3 signaling messages on the A interface. The BSSAP comprises the direct transfer application part (DTAP) and the base station subsystem management application part (BSSMAP). Signaling plane information transmitted between the BSC and the SGSN when the built-in PCU is used User plane information transmitted between the BSC and the SGSN when the built-in PCU is used Information transmitted between the BTS and the MS in PS domain Information transmitted between the BSC and the BTS in PS domain
RSL
BSSAP
GB SIG
GB PTP
PS UM PS Abis
9-2
Issue 02 (2008-06-30)
9 Message Tracing

Acronyms and Abbreviations GBAM LMT ESL IMSI TMSI MSISDN IMEI BVCI NSEI Full Spelling GSM Back Administration Module Local Maintenance Terminal Extend Signalling Link International Mobile Subscriber Identity International Mobile Station Identity Mobile Station International ISDN Number International Mobile Station Equipment Identity BSSGP Virtual Connection Identifier Network Service Entity Identifier
9.2 Availability
This lists the NEs and software required for the implementation of message tracing.
NEs Involved
Table 9-1 describes the NEs involved in message tracing. Table 9-1 NEs involved in message tracing MS
NOTE
l : not involved l : involved
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 9-2 describes the versions of GBSS products that support message tracing. Table 9-2 GBSS products and software versions Product BSC
Issue 02 (2008-06-30)
Version BSC6000 V900R008C01 and later releases

9-3
9 Message Tracing
Product BTS BTS3012 DTRU QTRU BTS3012A E BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM DTRU QTRU
Version BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 BTS3000V100R008C02 BTS3000V100R008C02
Miscellaneous
To make the full use of system resources and ensure the normal running of services, the BSC has the following restrictions on message tracing:
l
Up to 64 tasks can be created at the same time with up to 16 objects for each task. Up to 5 tasks can be created at the same time for message tracing such as GB PTP, PS UM, and PS Abis. Trace the messages by priority. The BSC regulates the signal flow associated with message tracing when the traffic is high.
9.3 Impact
This describes the impact of message tracing on system performance and other features.

The traced messages can either be reported or be saved on the server. Saving the traced messages on the server occupies lots of system resources, and thus is not recommended when there is large number of messages to be traced. Initiating many tracing tasks when the traffic volume is high occupies lots of system resources and has a great impact on the system performance. Thus, do not start many tracing tasks unless necessary. After a tracing task is complete, end this task immediately. Close a message tracing window on the BSC6000 Local Maintenance Terminal or Local Maintenance Terminal to end a tracing task.

The impact of this feature on other features is as follows:
l
This feature does not affect the functions of other features.

9-4

l
9 Message Tracing
This feature is effective when the BSC traced service module runs normally and bears services.

This describes the message tracing procedure, signaling tracing, and user tracing. 9.4.1 Message Tracing Procedure This describes the messaging tracing procedure with the cooperation of the BSC6000 Local Maintenance Terminal, server, and service modules. 9.4.2 Signaling Tracing This describes the signaling tracing associated with links and interfaces. 9.4.3 User Tracing This describes message tracing associated with a user. You can start the user tracing by IMSI, TMSI, MSISDN, or IMEI, and the call information associated with the user is displayed on the BSC6000 Local Maintenance Terminal.
9.4.1 Message Tracing Procedure

This describes the messaging tracing procedure with the cooperation of the BSC6000 Local Maintenance Terminal, server, and service modules. The basic procedures associated with a tracing task involve the following: establishing a tracing task, filtering and sending the tracing message packet, and deleting a tracing task.
Establishing a Tracing Task

1. The user specifies the tracing conditions on the BSC6000 Local Maintenance Terminal, and then issues command to the service module in order to create a tracing task. On receiving the command, the service module creates a tracing task on the BSC6000 Local Maintenance Terminal to record the information contained in the message packets that are used to create a tracing task. The server checks whether the tracing handle that matches the tracing conditions exists.
l
2.
If the matched tracing handle exists, an association between the tracing task and the tracing handle is established. The procedure is complete. If the matched tracing handle does not exist, a tracing handle is created for the establishment between the tracing task and this new tracing handle. Then, go to 3.
3.
When a new tracing handle is created, the server requires the service module to register the tracing handle. The service module records this tracing handle and locates the message that matches the tracing conditions, and then sends the tracing handle to the message. The server sends the event notice that a tracing task is created to all the modules subscribing to the tracing task creation event through the platform message center interface. The server sends the newly created task number to the BSC6000 Local Maintenance Terminal. Then, the BSC6000 Local Maintenance Terminal starts to receive and process messages, and maintain this task based on this task number.
4. 5.
Issue 02 (2008-06-30)
9-5
9 Message Tracing
Filtering and Sending the Tracing Message Packet

1. 2. The service module provides the information including the message content, tracing type, tracing handle and filter parameters to the tracing control module. The tracing control module processes the tracing tasks associated with the tracing handles. It checks whether the combination and filtering conditions are met. If the conditions are met, the tracing control module sends message packets to a corresponding tracing widow; otherwise, the tracing control module discards the message.
Deleting a Tracing Task

1. 2. The BSC6000 Local Maintenance Terminal initiates the deletion of a tracing task. The BSC deletes the task according to the task number provided by the BSC6000 Local Maintenance Terminal, and cancels the association between the task and the tracing handle.
l l
If the tracing handle has no association with other tasks, this tracing handle is released. If the tracing handle still has the association with other tasks, this tracing handle is saved.
3.
The service module is notified to stop sending messages to the tracing handle and the BSC6000 Local Maintenance Terminal is notified that the tracing task is deleted.
9.4.2 Signaling Tracing

This describes the signaling tracing associated with links and interfaces. There are two types of signaling tracing in terms of signaling location:
l
Signaling tracing on links This signaling tracing type involves the tracing of signaling on one link. The filtering conditions are associated with the physical location and logical number of the link. The links to be traced consist of the MTP2 link on the A interface, the LAPD link on the Abis interface, and the LAPD link on the Pb interface.
Signaling tracing on the interfaces This signaling tracing type involves the tracing of on the application layers. The filtering conditions are associated with the objects such as BTS and cell. The messages consist of the BSSAP messages on the A interface, RSL and OML messages on the Abis interface, messages on the application layer of the Pb interface, GB PTP messages in built-in PCU mode, GB SIG messages in built-in PCU mode, PS UM messages in built-in PCU mode, and PS Abis messages in built-in PCU mode.
The signaling tracing supports the following functions:

l l
Messages filtering: The filtering conditions vary with message types. Tracing mode selection: The traced result can either be reported directly or be saved on the server. Tracing result saved locally: If the direct report tracing mode is selected, you can save the tracing result in the local PC in file formats. Scheduled tracing: If the server is selected to save the tracing result, you can specify the start and end time to initiate the message tracing.
9-6
Issue 02 (2008-06-30)
9 Message Tracing
9.4.3 User Tracing

This describes message tracing associated with a user. You can start the user tracing by IMSI, TMSI, MSISDN, or IMEI, and the call information associated with the user is displayed on the BSC6000 Local Maintenance Terminal. The user tracing supports the following functions:
l
Interfaces to be traced: You can trace the user messages on the A interface, Abis interface, and Um interface. Specific user identity: You can trace the user messages by IMSI, TMSI, MSISDN, IMEI, or by a channel. After any of the previous conditions is selected, the host automatically sends the messages associated with the specified condition to the BSC6000 Local Maintenance Terminal.
The traced user messages comprise those associated with the specific user identities and those involved in the same call procedure with these messages. The messages associated with the specific user identities are as follows:
l l l l l
CM Service Request Setup Paging Handover Request Ciphering Mode Complete
It is unknown whether these messages contain the user identification information. Thus, only when the message that contains the user identification information is traced, the messages belong to the same procedure as the traced message are traced. After a user tracing task is started, the BSC6000 Local Maintenance Terminal sends the messages associated with this tracing to the service module. The service module decodes the signaling messages that contain the specific user identities, and decides whether to initiate the user tracing according to the decoded user identities. You can trace the user messages on the A, Abis, and Um interfaces simultaneously or independently. The messages traced over multiple interfaces can be displayed on the same window on the BSC6000 Local Maintenance Terminal.
9.5 Capabilities
None
9.6 Implementation
This describes how to configure message tracing. 9.6.1 Configuring Message Tracing This describes how to configure message tracing on the BSC6000 Local Maintenance Terminal.
9 Message Tracing
9.6.1 Configuring Message Tracing

This describes how to configure message tracing on the BSC6000 Local Maintenance Terminal.
Context
Five PS-domain tracing tasks that deal with different information can be performed simultaneously.
Procedure
Step 1 Select the Trace & Monitor tab page on the BSC6000 Local Maintenance Terminal. The Trace & Monitor page displays all the message tracing types supported by the BSC. Step 2 Double-click the type of the message to be traced and the message tracing window is displayed. Step 3 Set the filtering conditions such as the Tracing Mode, tracing object, Tracing Time (Save on Server should be selected as the tracing mode), uplink and downlink Color, and Save File (Report should be selected as the tracing mode), and then click OK. The message tracing window is displayed and message tracing starts.
l
Trace BSSAP messages on the A interface. Figure 9-1 shows the Trace BSSAP Message on the A Interface dialog box.
Figure 9-1 Trace BSSAP Message on the A Interface dialog box
Table 9-3 lists the parameters on the Trace BSSAP Message on the A Interface dialog box.
9-8
Issue 02 (2008-06-30)
9 Message Tracing
Table 9-3 Parameters on the Trace BSSAP Message on the A Interface dialog box Parameter Message type DPC Site Candidate Cells Selected Cells Tracing Mode Tracing Time Save File Description The available message types are BSSMAP Message, DTAP Message, PAGING Message, and Other Message. Indicates the destination signaling point code of the current BSC. Lists the BTSs configured on the BSC. You can select a BTS to be traced. Lists the cells configured in the selected site. You can select the cells to be traced. Lists the cells selected from the candidate cells for message tracing. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace SCCP messages on the A interface. Figure 9-2 shows the Trace SCCP Message on the A Interface dialog box.
Issue 02 (2008-06-30)
9-9
9 Message Tracing
Figure 9-2 Trace SCCP Message on the A Interface dialog box
Table 9-4 lists the parameters on the Trace SCCP Message on the A Interface dialog box. Table 9-4 Parameters on the Trace SCCP Message on the A Interface dialog box Parameter Tracing Type Location Tracing Mode Tracing Time Save File Description The available tracing types are Tracing SCCP message by DPC, Tracing SCCP user message, and Tracing MTP3 primal message. You can specify a network segment by the NI, OPC, and DPC. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace MTP2 messages on the A interface. Figure 9-3 shows the Trace MTP2 Message on the A Interface dialog box.
9-10
Issue 02 (2008-06-30)
9 Message Tracing
Figure 9-3 Trace MTP2 Message on the A Interface dialog box
Table 9-5 lists the parameters on the Trace MTP2 Message on the A Interface dialog box. Table 9-5 Parameters on the Trace MTP2 Message on the A Interface dialog box Parameter Message type Location Tracing Mode Tracing Time Save File Description The available message types are LSSU Message and MSU Message. You can specify a link by setting the Subrack, Slot, and Link No.. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace MTP3 messages on the A interface. Figure 9-4 shows the Trace MTP3 Message on the A Interface dialog box.
Issue 02 (2008-06-30)
9-11
9 Message Tracing
Figure 9-4 Trace MTP3 Message on the A Interface dialog box
Table 9-6 lists the parameters on the Trace MTP3 Message on the A Interface dialog box. Table 9-6 Parameters on the Trace MTP3 Message on the A Interface dialog box Parameter Message type Tracing Type Location Tracing Mode Tracing Time Save File Description The available message types are SNM, SLT, SCCP, MT, and L2_CHANGE. You can choose one of the three tracing types, namely, Tracing by Link, Tracing by Link Set, and Tracing by DPC. Specify the Subrack No., XPU Slot No., CPU No., CIU Slot No., and Link No.. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace SCTP messages on the A interface. Figure 9-5 shows the Trace SCTP Message on the A Interface dialog box
9-12
Issue 02 (2008-06-30)
9 Message Tracing
Figure 9-5 Trace SCTP Message on the A Interface dialog box
Table 9-7 lists the parameters on the Trace SCTP Message on the A Interface dialog box. Table 9-7 Parameters on the Trace SCTP Message on the A Interface dialog box Parameter Message type Location Tracing Mode Tracing Time Save File Description The available message types are CTRL, DATA, and HB. Specify the Subrack No., XPU Slot No., CPU No., and Link No.. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace M3UA messages on the A interface. Figure 9-6 shows the Trace M3UA Message on the A Interface dialog box.
Issue 02 (2008-06-30)
9-13
9 Message Tracing
Figure 9-6 Trace M3UA Message on the A Interface dialog box
Table 9-8 lists the parameters on the Trace M3UA Message on the A Interface dialog box. Table 9-8 Parameters on the Trace M3UA Message on the A Interface dialog box Parameter Message type Location Tracing Mode Tracing Time Save File Description The available message types are MGN, TR, SSNM, ASPTM, ASPSM, and RKM. Specify the Subrack No., XPU Slot No., CPU No., and Link No.. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace RSL messages on the Abis interface. Figure 9-7 shows the Trace RSL Message on the Abis Interface dialog box.
9-14
Issue 02 (2008-06-30)
9 Message Tracing
Figure 9-7 Trace RSL Message on the Abis Interface dialog box
Table 9-9 lists the parameters on the Trace RSL Message on the Abis Interface dialog box. Table 9-9 Parameters on the Trace RSL Message on the Abis Interface dialog box Parameter Message type Description The available message types are DCM(Measure Result), DCM (Others), CCM(Channel Request), CCM(Paging), CCM(Others), RLM, and TRXM. You can start the message tracing by TRX or by cell. The sites, cell, and TRXs can be selected in the drop-down lists. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Filtering Condition Tracing Mode Tracing Time Save File
Color
Issue 02 (2008-06-30)
9-15
9 Message Tracing
l
Trace OML messages on the Abis interface. Figure 9-8 shows the Trace OML Message on the Abis Interface dialog box.
Figure 9-8 Trace OML Message on the Abis Interface dialog box
Table 9-10 lists the parameters on the Trace OML Message on the Abis Interface dialog box. Table 9-10 Parameters on the Trace OML Message on the Abis Interface dialog box Parameter Message type Candidate Sites Selected Sites Tracing Mode Tracing Time Save File Description The available message types are Common Message and O&M Message. This area lists all the candidate sites to be traced. Indicates the sites to be traced. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace ESL messages on the Abis interface. Figure 9-9 shows the Trace ESL Message on the Abis Interface dialog box.
9-16
Issue 02 (2008-06-30)
9 Message Tracing
Figure 9-9 Trace ESL Message on the Abis Interface dialog box
Table 9-11 lists the parameters on the Trace ESL Message on the Abis Interface dialog box. Table 9-11 Parameters on the Trace ESL Message on the Abis Interface dialog box Parameter Message type Candidate Sites Selected Sites Tracing Mode Tracing Time Save File Description The available message types are Common Message and O&M Message. This area lists all the candidate sites to be traced. Indicates the sites to be traced. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace EML messages on the Abis interface. Figure 9-10 shows the Trace EML Message on the Abis Interface dialog box.
Issue 02 (2008-06-30)
9-17
9 Message Tracing
Figure 9-10 Trace EML Message on the Abis Interface dialog box
Table 9-12 lists the parameters on the Trace EML Message on the Abis Interface dialog box. Table 9-12 Parameters on the Trace EML Message on the Abis Interface dialog box Parameter Message type Location Tracing Mode Tracing Time Save File Description The available message types are Common Message and O&M Message. Indicates the location of the link to be traced. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace LAPD messages on the Abis interface. Figure 9-11 shows the Trace LAPD Message on the Abis Interface dialog box.
9-18
Issue 02 (2008-06-30)
9 Message Tracing
Figure 9-11 Trace LAPD Message on the Abis Interface dialog box
Table 9-13 lists the parameters on the Trace LAPD Message on the Abis Interface dialog box. Table 9-13 Parameters on the Trace LAPD Message on the Abis Interface dialog box Parameter Link Type Location Tracing Mode Tracing Time Save File Description The available link types are RSL, OML, EML, and ESL. You can specify the RSL link by TRX and the OML link by site. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace application messages on the Pb interface. Figure 9-12 shows the Trace Application Message on the Pb Interface dialog box.
Issue 02 (2008-06-30)
9-19
9 Message Tracing
Figure 9-12 Trace Application Message on the Pb Interface dialog box
Table 9-14 lists the parameters on the Trace Application Message on the Pb Interface dialog box. Table 9-14 Parameters on the Trace Application Message on the Pb Interface dialog box Parameter Message type Site Candidate Cells Selected Cells Tracing Mode Tracing Time Save File Description The available message types are PAGING Message, CONFUSION Message, PCIC Check Message, and other Message. This area lists all the candidate sites to be traced. Indicates all the cells in a site. Indicates the cells to be traced. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace LAPD messages on the Pb interface. Figure 9-13 shows the Trace LAPD Message on the Pb Interface dialog box.
9-20
Issue 02 (2008-06-30)
9 Message Tracing
Figure 9-13 Trace LAPD Message on the Pb interface dialog box
Table 9-15 lists the parameters on the Trace LAPD Message on the Pb interface dialog box. Table 9-15 Parameters on the Trace LAPD Message on the Pb interface dialog box Parameter Selection Mode Description You can specify a Pbsl either by selecting the PCU name or selecting the port number, timeslot number, and sub timeslot on the board where the link locates or directly inputting the Pbsl number. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Tracing Mode Tracing Time Save File
Color
Issue 02 (2008-06-30)
9 Message Tracing
Trace messages on the Um interface. Figure 9-14 shows the Trace Message on the Um Interface dialog box.
Figure 9-14 Trace Message on the Um Interface dialog box
Table 9-16 lists the parameters on the Trace Message on the Um Interface dialog box. Table 9-16 Parameters on the Trace Message on the Um Interface dialog box Parameter Filtering Condition Description You can start the message tracing by TRX or by cell. The Site area lists all the BTS sites controlled by the BSC and the TRX area lists all the TRXs within a BTS site. The Candidate Cells area lists the cells available within a specified site and the Selected Cells area lists the cells to be traced. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Tracing Mode Tracing Time Save File
Color
9-22
Issue 02 (2008-06-30)

l
9 Message Tracing
Trace user messages. Figure 9-15 shows the Trace User Message dialog box.
Figure 9-15 Trace User Message dialog box
Table 9-17 lists the parameters on the Trace User Message dialog box. Table 9-17 Parameters on the Trace User Message dialog box Parameter Interface Type User Tracing Mode Tracing Time Save File Description The available interface types are A Interface, Abis Interface, and Um Interface. You can trace the messages of a user by its IMSI, TMSI, MSISDN, IMEI, or by the channel occupied by the user. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace messages at the BSC-CBC interface. Figure 9-16 shows the Trace the Message at BSC-CBC Interface.
Issue 02 (2008-06-30)
9-23
9 Message Tracing
Figure 9-16 Trace the Message at the BSC-CBC Interface dialog box
Table 9-18 lists the parameters on the Trace the Message at the BSC-CBC Interface dialog box. Table 9-18 Parameters on the Trace the Message at the BSC-CBC Interface dialog box Parameter Tracing Mode Tracing Time Save File Description The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace PS PTP messages on the Gb interface. Figure 9-17 shows the Trace PS PTP Message on the Gb Interface dialog box.
9-24
Issue 02 (2008-06-30)
9 Message Tracing
Figure 9-17 Trace PS PTP Message on the Gb Interface dialog box
Table 9-19 lists the parameters on the Trace PS PTP Message on the Gb Interface dialog box. Table 9-19 Parameters on the Trace PS PTP Message on the Gb Interface dialog box Parameter Tracing Type Cell NSEI+BVCI Tracing Mode Tracing Time Save File Description The available tracing types are Tracing by Cell and Tracing by NSEI+BVCI. When tracing messages by cell, specify the Site and Cell. When tracing messages by NSEI+BVCI, specify the NSEI and BVCI. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace PS SIG messages on the Gb interface. Figure 9-18 shows the Trace PS SIG Message on the Gb Interface dialog box.
Issue 02 (2008-06-30)
9-25
9 Message Tracing
Figure 9-18 Trace PS SIG Message on the Gb Interface dialog box
Table 9-20 lists the parameters on the Trace PS SIG Message on the Gb Interface dialog box. Table 9-20 Parameters on the Trace PS SIG Message on the Gb Interface dialog box Parameter Location Tracing Mode Tracing Time Save File Description Specify the NSEI. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Trace PS messages on the Um interface. Figure 9-19 shows the Trace PS Message on the Um Interface dialog box.
9-26
Issue 02 (2008-06-30)
9 Message Tracing
Figure 9-19 Trace PS Message on the Um Interface dialog box
Table 9-21 lists the parameters on the Trace PS Message on the Um Interface dialog box. Table 9-21 Parameters on the Trace PS Message on the Um Interface dialog box Parameter Message type Tracing Condition Location Tracing Mode Tracing Time Save File Description The available message types are DUMMY, SYS, NULL, and DATA. Specify the way to perform message tracing: TRX or Cell. Specify the site and TRX or the site and cell based on the Tracing Condition. The available options are Report and Save on Server. The tracing time can be specified when Save on GOMU is selected as the tracing mode. This parameter determines, when Report is selected as the tracing mode, whether to save the traced messages locally and if so in which directory the messages should be saved. Indicates the color of the traced messages to be displayed on the BSC6000 Local Maintenance Terminal. Two types of messages can be specified: uplink messages and downlink messages.
Color
Manage tracing task. Figure 9-20 shows the Manage Trace Task dialog box.
Issue 02 (2008-06-30)
9-27
9 Message Tracing
Figure 9-20 Manage Trace Task dialog box
Table 9-22 lists the parameters on the Manage Trace Task dialog box. Table 9-22 Parameters on the Manage Trace Task dialog box Parameter Common Setting Time Setting Description Set Interface Type, Tracing Mode, Task Status, and Create Method. You can manage the tracing tasks by setting a period during which the tracing tasks are performed.
Manage traced file. Figure 9-21 shows the Manage Trace file dialog box.
9-28
Issue 02 (2008-06-30)
9 Message Tracing
Figure 9-21 Manage Trace File dialog box
Table 9-23 lists the parameters on the Manage Trace File dialog box. Table 9-23 Parameters on the Manage Trace File dialog box Parameter Query Setting Upload Setting Description Specify the File Name of the file to be traced. The parameters you can set are Path, Retry Time(s), Zipped, and Delete Ater Upload.
Review message tracing. If the traced messages are saved in the file format on the disk, you can open the file to view the messages through the review tracing function. Double-click Reviewing Tracing and select the message tracing file to be opened. The file is displayed in a new window.
Step 4 Close the message tracing dialog box to complete the message tracing. ----End

None.
Alarms
None
Counters
None
9 Message Tracing
9.8 References
None
9-30
Issue 02 (2008-06-30)
10 EFR
10
About This Chapter
10.1 Overview This describes the definition and purposes of EFR. 10.2 Availability This lists the NEs and software required for the implementation of EFR.
EFR
10.3 Technical Description This describes the EFR call establishment procedure and the EFR call signaling procedure. 10.4 Implementation This describes how to configure EFR. 10.5 Maintenance Information This lists the counters related to EFR. 10.6 References
Issue 02 (2008-06-30)
10-1
10 EFR
10.1 Overview
This describes the definition and purposes of EFR.
Definition
Enhanced Full Rate (EFR) is a speech codec mode.
Purposes
EFR can greatly improve the speech quality.
Terms
None.

Acronyms and Abbreviations CELP EFR TDMA Full Spelling Code Excited Linear Prediction Enhanced Full Rate Time Division Multiple Access
10.2 Availability
This lists the NEs and software required for the implementation of EFR.
NEs Involved
Table 10-1 lists the network elements involved in EFR. Table 10-1 Network elements involved in EFR MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 10-2 lists the software versions of GBSS products that support EFR.
10 EFR
Table 10-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012A E BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM BTS3X BTS3002C BTS3001C DTRU QTRU Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases All releases All releases Not supported
Miscellaneous
None.

This describes the EFR call establishment procedure and the EFR call signaling procedure. 10.3.1 EFR Call Establishment Procedure This describes the EFR call establishment procedure. 10.3.2 EFR Call Signaling Procedure This describes the EFR call signaling procedure.
10.3.1 EFR Call Establishment Procedure

This describes the EFR call establishment procedure. During the call establishment, the BSC determines, considering the type of the actually assigned channels to the call, whether the latest speech version contained in the Assignment Request message from the MSC supports the EFR. If the latest speech version supports the EFR, the call is an EFR call. In other cases, it is a common call. Figure 10-1 shows the EFR call establishment procedure.
10 EFR
Figure 10-1 EFR call establishment procedure

Start
The speech version contained in the Assignment Request message is EFR
Considering the type of actually assigned channels, the BSC determines whether the latest speech version in the message supports the EFR?
No
Common call (FR)
Yes EFR call
End
The EFR uses the CELP linear codec scheme to improve the speech quality. The EFR is implemented through the GDPUX software of the BSC and the DSP software of the BTS. The BSC host software and OMC software provide certain auxiliary functions. When the EFR is applied, the transmission rate of speech signals on the Um interface is 12.2 kbit/s.
10.3.2 EFR Call Signaling Procedure

This describes the EFR call signaling procedure. Figure 10-2 shows the EFR call signaling processing procedure.
10-4
Issue 02 (2008-06-30)
10 EFR
Figure 10-2 EFR call signaling procedure

MS BTS BSC Assignment Request (1)
Channel Activation (2)
MSC
Start T10
Channel Activation Acknowledge Assignment Command Main DCCH Start T3107 SABM FACCH Establishment Indication
UA FACCH
Assignment Complete (3) FACCH Stop T3107 Assignment Complete Stop T10
1.
The MS sends the MSC a Setup message to indicate whether the MS supports EFR. Based on the service type of the call, the MSC sends an Assignment Request message carrying the speech version to the BSC. The BSC checks whether the call supports EFR based on the settings of the Speech Versions and the speech version carried in the delivered Assignment Request message. If the call supports EFR, the BSC sends a Channel Activation message carrying the full-rate speech version 2 (EFR) to the BTS. After the BTS responds with a Channel Activation Acknowledge message, the BSC sends an Assignment Command message carrying the full-rate speech version 2 (EFR) in the channel mode to the MS. The MS reports an Assignment Complete message to the BSC, and the BSC sends the Assignment Complete message to the MSC. The EFR call is established.
2.
3.
10.4 Implementation
This describes how to configure EFR. 10.4.1 Configuring EFR This describes how to configure EFR on the BSC6000 Local Maintenance Terminal.
Issue 02 (2008-06-30)
10-5
10 EFR
10.4.1 Configuring EFR

This describes how to configure EFR on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page, and then selectConfigure Cell Attributes. Step 2 Double-click the target cell in the Cell view list box to add it to the Selected cells list box. Step 3 Click Next. Step 4 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 10-3. Figure 10-3 Setting Cell Attributes dialog box
Step 5 Click Call Control.

10 EFR
Step 6 Click Advanced, select the Access Control tab, and then set Speech Version to Support Fullrate Version 2, as shown in Figure 10-4. Figure 10-4 Setting advanced call control parameters
Step 7 Click OK. ----End

This lists the counters related to EFR.
Alarms
None.
Counters
Table 10-3 lists the counters involved in EFR. Table 10-3 Counters involved in EFR Counter A3167B S3115 S4552 Meaning Speech Version 2 Completed Assignments (Excluding Directed Retry) (TCHF) Number of Uplink Frames Among the EFR Frames in the Customized MR of Cell Number of Uplink Frames Among the EFR Frames in the Customized MR
Issue 02 (2008-06-30)
10 EFR
Counter S4553
Meaning Number of Downlink Frames Among the EFR Frames in the Customized MR
10.6 References
l l l
GSM08.08 v7.6.1 : Digital cellular telecommunications system (Phase 2+) GSM08.58 v7.4.1 : Digital cellular telecommunications system (Phase 2+) GSM04.08 v7.8.0 : Digital cellular telecommunications system (Phase 2+)
10-8
Issue 02 (2008-06-30)
11 AMR
11
About This Chapter
AMR
11.1 Overview AMR is a new codec technique like EFR, FR, and HR. It adjusts uplink/downlink codec modes and the speech rates according to the conditions met on the Um interface. Thus, the speech quality and the system capacity can be optimally balanced. 11.2 Availability This lists the NEs and software required for the implementation of AMR. In addition, some special requirements are listed. 11.3 Technical Description AMR is an adaptive multi-rate speech codec algorithm. Thus the interference resistance capability and the speech quality in the wireless communication system can be improved. 11.4 Capabilities This describes the functions supported by AMR and the limitations on AMR. 11.5 Implementation This describes how to configure, verify, and deactivate AMR. 11.6 Maintenance Information This lists the counters related to AMR. 11.7 References
Issue 02 (2008-06-30)
11-1
11 AMR
11.1 Overview
AMR is a new codec technique like EFR, FR, and HR. It adjusts uplink/downlink codec modes and the speech rates according to the conditions met on the Um interface. Thus, the speech quality and the system capacity can be optimally balanced.
Definition
AMR is an adaptive multi-rate speech codec algorithm, which is termed full-rate speech version 3 and half-rate speech version 3 in GSM specifications. This algorithm enables a BTS and an MS to select an appropriate codec rate automatically as the interference on the radio network changes so that the interference resistance performance and the speech quality of the wireless communication system can be improved. AMR is applicable to the speech service in the wireless communication system and is not applicable to the CS service or PS service.
Purposes
In the wireless communication system, the higher the speech codec rate is, the more speech feature information is carried in the code stream. Thus the redundant information in the code stream is less.
l
The more the speech feature information is carried in the code stream, the higher the speech fidelity is. The less the redundant information in the code stream is, the more interference-sensitive the code stream becomes. In a poor wireless communication environment, bit errors occur easily and the speech frames may get lost. Thus, voices may be intermittent.
With the increase of the codec rate, more redundant information is carried in the code stream. Thus, the code stream is less sensitive to interference and the continuity of voice can be improved. With AMR, the BTS and the MS can evaluate the interference in the radio network based on the detected parameters such as receive level, receive quality, and carrier-to-interference ratio, and then adjust the codec rate accordingly.
Terms
Terms HW II HW III Inband signaling Definition It is an algorithm used for channel allocation and power control. It is an algorithm used for power control. It uses part of the transmission bandwidth of the TRAU frame (speech frame) to transmit signaling information. The CMC, CMR, and CMI involved in this feature are transmitted through part of the bits of the TRAU frame header.
11-2
Issue 02 (2008-06-30)
11 AMR
Terms P/N criterion
Definition It is a criterion against which a certain operation is performed when the criterion lasts within an acceptable statistical period. It is the ratio of the strength of a carrier signal to the strength of an interference signal. In the GSM communication system, the versions of the speech codec algorithms are categorized into full-rate speech versions 1, 2, and 3 and half-rate speech versions 1, 2, and 3. It is the ability of a system to maintain functions even with changes in internal structure or external environment. Robustness can be functionally categorized into stability robustness and performance robustness.
C/I ratio Speech Version
Robustness

Acronyms and Abbreviations AMR ACS C/I CMC CMR CMI FR HR RATSCCH RQI Full Spelling Adaptive Multi-Rate Active Codec Set Carrier to Interference ratio Codec Mode Command Codec Mode Request Codec Mode Indication Full Rate Half Rate Robust AMR Traffic Synchronized Control Channel Radio Quality Indication
11.2 Availability
This lists the NEs and software required for the implementation of AMR. In addition, some special requirements are listed.
Issue 02 (2008-06-30)
11-3
11 AMR
NEs Involved
Table 11-1 lists the NEs involved in AMR. Table 11-1 NEs involved in AMR MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Version
Table 11-2 lists the versions of GBSS products that support AMR. Table 11-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3X BTS3002E BTS3006C BTS3012 DTRU QTRU BTS3012 AE BTS3036 BTS3036A DBS3036 DTRU QTRU Version V900R008C01 and later releases G3BTS32V302R002C06 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C01 and later releases
NOTE
If the BTS software versions do not meet the mapping requirements, call establishment failure, no audio, or handover failure may occur.
Miscellaneous
The following requirements must be met when you use AMR:

l l l l l
11 AMR
The speech version permitted by the MSC supports AMR. The license is available for the BSC. The BSC can be configured with AMR. The cell is configured with full-rate speech version 3 or half-rate speech version 3, or both. The MS supports AMR.
NOTE
The MSC determines whether the MS supports AMR based on the Setup message (bearer capability IE) reported by the MS.

AMR is an adaptive multi-rate speech codec algorithm. Thus the interference resistance capability and the speech quality in the wireless communication system can be improved. AMR allows the BTS and the MS to adjust the codec rate based on the measured parameters, such as receive level, receive quality, and C/I ratio. An appropriate codec rate can be obtained with the configuration of the AMR call control parameters in the BSC and the adjustment of the parameters in the MS through the Um interface. In this algorithm, the codec mode of AMR is adjusted through the logical control unit and inband signaling of the BTS and MS.
l
On the BTS side, there are two logical units: downlink mode control unit (DL-Mode Ctrl) and uplink mode control unit (UL-Mode Ctrl). There are two logical units control the downlink and uplink codec mode separately. On the MS side, there is one logical unit called downlink mode request generating unit (DL-Req.Gen). This logical unit generates the downlink codec mode request command. Uplink direction 1. The UL-Mode Ctrl in the BTS compares the value of uplink quality indication with a certain threshold, and a Codec Mode Command (CMC) is generated. The CMC indicates the uplink codec mode to be used. The CMC is sent to the MS side through inband signaling. The MS is notified to adjust the codec mode. After receiving the CMC, the MS adjusts the codec mode to a new mode. The DL-Mode Ctrl in the BTS compares the value of downlink quality indication with a certain threshold, and a Codec Mode Request (CMR) is generated. The CMR indicates the downlink codec mode to be used. The CMR is sent to the DL-Mode Ctrl of the BTS side through inband signaling for controlling the downlink codec mode. After receiving the CMR, the BTS comprehensively considers the restrictions on the network side, and then adjusts the downlink codec mode.
The procedure for AMR codec mode adjustment is as follows:

l
2. 3.
l
Downlink direction 1.
2. 3.
The CMI in uplink and downlink directions is used to notify the peer end of the currently used codec mode of this end. Thus the peer end performs decoding accordingly. Table 11-3 shows the comparison between the CMI and the codec mode and the comparison between the CMR and the codec mode. HR AMR can use only mode 0 through mode 5.
11 AMR
Table 11-3 Comparison table CMI 0 1 2 3 4 5 6 7 CMR 0 1 2 3 4 5 6 7 Codec Mode AMR 4,75 kbit/s AMR 5,15 kbit/s AMR 5,90 kbit/s AMR 6,70 kbit/s (PDC-EFR) AMR 7,40 kbit/s (TDMA-EFR) AMR 7,95 kbit/s AMR 10,2 kbit/s AMR 12,2 kbit/s (GSM-EFR)
NOTE
Huawei GSM BSS equipment does not support mode 5 for HR AMR currently. Mode 5 indicates the AMR codec mode at a rate of 7.95 kbit/s.
11.3.1 AMR Call

This describes the AMR call establishment procedure, determination of the AMR speech version, incoming inter-BSC handover, outgoing inter-BSC handover, and intra-BSC handover.
AMR Call Establishment Procedure

Figure 11-1 shows the flow chart of the AMR call establishment procedure.
11-6
Issue 02 (2008-06-30)
11 AMR
Figure 11-1 AMR call establishment procedure

Start
MSC checks: Does an MS support AMR? Y BSC receives an assignment request from the MSC.
Does the license allow the BSC to use the AMR? Y Is the A interface tag PHASE 2+? Y Assign to the AMR TRX or not? Y Deliver AMR service parameters to the BTS and MS to establish AMR calls.
N Non-AMR call
End
The procedure for establising AMR calls is as follows: 1. 2. 3. 4. The MSC determines whether an MS supports AMR based on the capability of the MS, service type of a call, and speech version supported by the MSC. The MSC determines the speech version set allowed by the call, and then sends the speech version set to the BSC through the Assignment Request message. The BSC determines whether AMR can be used based on whether the license allows the BSC to use AMR and whether the A interface tag is PHASE 2+. If TRXs that support AMR are assigned, the BSC sends the AMR service parameters to the BTS and MS. The AMR call is established. If TRXs that do not support AMR are assigned, the non-AMR call is established.
Determination of the AMR Speech Version

Figure 11-2 shows the procedure for determining the AMR speech version.
Issue 02 (2008-06-30)
11-7
11 AMR
Figure 11-2 Procedure for determining the AMR speech version
Start
BSC receives the assignment request or handover request from the MSC. BSC saves the speech version list set allowed by the MSC. With the speech version set carried in the Assignment Request message and the speech versions supported by the cell, the alternative speech versions are decided. With the channel types actually assigned, the speech version with highest priority is selected as the resulting speech version for use. End
The procedure for determining the AMR speech version is as follows: 1. The MSC determines the speech version set allowed by the call, and then sends the speech version set to the BSC through the Assignment Request message. The BSC saves the speech version set allowed by the MSC. With the speech version set carried in the Assignment Request message and the speech versions supported by the cell, the alternative speech versions are decided. With the alternative speech versions and the channel types actually assigned, the speech version with highest priority is selected as the final speech version for use.
2. 3.
Incoming Inter-BSC Handover Procedure

The incoming inter-BSC handover procedure is as follows: 1. 2. 3. 4. 5. The MSC determines whether an MS supports AMR based on the capability of the MS, service type of a call, and speech version supported by the MSC. The MSC determines the speech version set allowed by the call, and then sends the speech version set to the BSC through the incoming inter-BSC handover request message. With the speech version set carried in the assignment request message and the speech versions supported by the cell, the alternative speech versions are decided. With the alternative speech versions and the channel types actually assigned, the speech version with highest priority is selected as the final speech version for use. If an AMR speech version is selected, the BSC sends the AMR service parameters to the BTS through a channel activation message. On receiving the channel activation acknowledgment from the BTS, the BSC sends a handover request acknowledgment to the MSC. The BSC then sends the AMR service parameters to the MS through an assignment command.
11-8
11 AMR
Outgoing Inter-BSC Handover Procedure

In the outgoing inter-BSC handover procedure, the BSC sends a handover request message to the MSC based on the handover decision algorithm. This message contains the speech version used by the current call.
Intra-BSC Handover Procedure

In the intra-BSC handover procedure, the BSC determines to initialize an intra-BSC handover based on the BSC handover decision algorithm. According to the saved assignment requests or the speech version set carried in the incoming BSC handover request, a final speech version is determined with the method adopted by the assignment procedure. In an AMR call, the BSC sends the AMR service parameters to the BTS through a channel activation message and to the MS through a handover command.
11.3.2 AMR Voice Rate Adjustment

This describes AMR voice rate adjustment. AMR supports the full-rate voice codec mode and the half-rate voice codec mode. Table 11-4 describes the rate types that are supported by the two modes. Table 11-4 Mapping between AMR codec modes and voice codec rates Codec Mode AMR full-rate codec mode Supported Voice Coding Rate Type 12.2 kbit/s (GSM EFR) 10.2 kbit/s 7.95 kbit/s 7.40 kbit/s 6.70 kbit/s 5.90 kbit/s 5.15 kbit/s 4.75 kbit/s AMR half-rate codec mode 7.95 kbit/s 7.40 kbit/s (IS136 EFR) 6.70 kbit/s 5.90 kbit/s 5.15 kbit/s 4.75 kbit/s
NOTE
Currently, the AMR half rate of Huawei GSM BSS does support the codec mode of 7.95 kbit/s.
The AMR codec mode is selected according to ACS. The Active Codec Set ACS contains one to four codec modes. One to three threshold values and hysteresis values accompany the ACS. These values are used to generate CMC and CMR for UL-Mode Ctrl and DL-Req. Gen. All
11 AMR
these configuration parameters (ACS, threshold, and hysteresis) are sent through high-layer signaling when a call is established. These configuration parameters can be modified during the handover. Figure 11-3 shows the principle for adjusting AMR codec modes. Figure 11-3 Procedure for codec mode adjustment
C/I CODEC_ MODE_4 THR_3 + HYST_3 = THR_MX_Up(3) THR_3 CODEC_MODE_3 THR_2 + HYST_2 = THR_MX_Up(2) THR_2 CODEC_MODE_2 THR_1 + HYST_1 = THR_MX_Up(1) CODEC_MODE_1 THR_1 = THR_MX_Dn(2) = THR_MX_Dn(3) = THR_MX_Dn(4)
THR_N: AMR Coding Rate adj.thN (1N3)
HYST_N: AMR Coding Rate adj.hystN (1N3)
As seen from Figure 11-3, assume that the active codec mode is CODEC_MODE_3. When C/ I is greater than THR_3+HYST_3, the codec mode is switched to CODEC_MODE_4; when C/ I is smaller than THR_2, the codec mode is switched to CODEC_MODE_2. The AMR codec mode is adjusted by the BTS and the MS. Figure 11-4 shows the procedure for adjusting uplink codec modes by the BTS.
11-10
Issue 02 (2008-06-30)
11 AMR
Figure 11-4 Adjusting uplink codec modes by the BTS

Start
Select the initial AMR codec rate. N
Enable AMR rate adjustment algorithm? Y Perform filtering for C/I or BER data.
Filtering value >(THR_N+HYST_N)? N Filtering value <THR_N? N Keep the codec rate unchanged. Configure the codec mode command. Y
MS must use the AMR codec rate with a higher level.
MS must use the AMR codec rate with a lower level.
End
THR_N: AMR UL Coding Rate adj.thN (1N3) HYST_N: AMR UL Coding Rate adj.hystN (1N3)
The previous process is described as follows: 1. 2. During AMR call establishment, AMR Starting Mode(F) or AMR Starting Mode(H) determines which codec mode in AMR ACS(F) or AMR ACS(H) is used to make a call. AMR rate control switch controls whether the AMR voice rate is adjusted. The rated settings are described as follows:
l
If AMR rate control switch is set to Algorithm I, it indicates that the BSC adjusts the AMR rate based on C/I. If AMR rate control switch is set to Algorithm II, it indicates that the BSC adjusts the AMR rate based on BER. If AMR rate control switch is set to None, it indicates that the AMR rate ajustment is not enabled.
3.
If AMR rate control switch is set to Algorithm I or Algorithm II,the uplink/downlink code mode is adjusted according to the configured threshold and hysteresis parameters with the change of radio environment during communication. The following part takes the adjustment of the AMR full-rate coding mode as an example.
Issue 02 (2008-06-30)
11 AMR
l
For mode 1,
If channel quality is greater than AMR UL Coding Rate adj.th1(F) plus AMR UL Coding Rate adj.hyst1(F), it is required that the peer end adjusts the transmission mode to 2. For other cases, the transmission mode is not adjusted. If channel quality is greater than AMR UL Coding Rate adj.th2(F) plus AMR UL Coding Rate adj.hyst2(F), it is required that the peer end adjusts the transmission mode to 3. If channel quality is smaller than AMR UL Coding Rate adj.th1(F), it is required that the peer end adjusts the tranmission mode to 1. For other cases, the transmission mode is not adjusted. If channel quality is less than AMR UL Coding Rate adj.th3(F) plus AMR UL Coding Rate adj.hyst3(F), it is required that the peer end adjusts the transmission mode to 4. If channel quality is less than AMR UL Coding Rate adj.th2(F), it is required that the peer end adjusts the tranmission mode to 2. For other cases, the transmission mode is not adjusted. If channel quality is less than AMR UL Coding Rate adj.th3(F), it is required that the peer end adjusts the tranmission mode to 3. For other cases, the transmission mode is not adjusted.
For mode 2,
For mode 3,
For mode 4,
The adjustment process of the AMR half-rate codec mode is similar to the adjustment process of the AMR full-rate codec mode.
11.3.3 Algorithm for AMR Intra-Cell Handover Between AMR FullRate and AMR Half-Rate
This describes the characteristics associated with the handover between AMR full-rate and AMR half-rate . The algorithm involved is an RQI-based handover decision algorithm targeted for the AMR call.
Functional Switches
The AMR intra-cell handover between AMR full-rate and AMR half-rate is determined by Intracell F-H HO Allowed.
Restriction
The AMR intra-cell handover between AMR full-rate and AMR half-rate is subject to the following conditions:
l
The decision for AMR intra-cell handover between AMR full-rate and AMR half-rate is initiated for only AMR calls. The AMR half-rate service must be enabled in the cell where the call is located.
11-12

l
11 AMR
Both full-rate speech version 3 and half-rate speech version 3 must be supported by the cell where the call is located. The type of the channel specified by the MSC during a call can be changed during a handover. For full-rate AMR calls, if the AMR TCH/H Prior Allowed is enabled, a handover is allowed only when the cell load is greater than the AMR TCH/H Prior Cell Load Threshold. For half-rate AMR calls, there is no such a limitation.
Measurement Report
For AMR calls, the BTS measures the uplink carrier-to-interference ratio and converts it into RQI. Then, the BTS sends the RQI to the BSC through the measurement report. The conversion formula between RQI and C/I is: RQI = 2 x 10 x log ((C/I)/16). The value ranges from 0 to 72 with a unit of 0.5 dB.
Decision Algorithms
The algorithm for AMR intra-cell handover between AMR full-rate and AMR half-rate follows the P/N criterion. In a statistical period (indicated by Intracell F-H HO Last Time), if the determination conditions are met for a period (indicated by Intracell F-H HO Start Time), a handover can be performed.
l
For an AMR call, when AMR full-rates are seized and the call is within the Intracell F-H HO Last Time, the handover from AMR full-rate to AMR half-rate is triggered if the RQI of the call is greater than the F2H HO th in a certain period. For an AMR call, when AMR half-rates are seized and the call is within the Intracell FH HO Last Time, the handover from AMR half-rate to AMR full-rate is triggered if the RQI of the call is greater than the H2F HO th in a certain period.
Figure 11-5 shows the algorithm procedure of AMR intra-cell handover between AMR full-rate and AMR half-rate.
Issue 02 (2008-06-30)
11-13
11 AMR
Figure 11-5 Flow Chart of Algorithm for AMR Intra-Cell Handover Between AMR Full-Rate and AMR Half-Rate
Start
RQI checks whether to trigger the AMRhandover? Y Is the P/N criterion met? Y N Does the current call seize the full rate? Y Is channel seizure ratio greater than the AMR traffic busy threshold? Y Trigger the handover from full rate to half rate.
Trigger the handover from half rate to full rate
Do not perform the handover.
End
Handover Procedure
The procedure for the AMR intra-cell handover between AMR full-rate and AMR half-rate is the same as the procedure for common handover. The cause value is 0x1F.
Handover Parameter
The recommended configurations of the AMR call handover parameters are as follows:
l l l l
The value of Intracell F-H HO Last Time is 4. The value of Intracell F-H HO Start Time is 5. The value of F2H HO th is 20. The value of H2F HO th is 10.
11.3.4 AMR Power Control

The power control parameters for AMR calls and non-AMR calls are separated. Through the settings of the AMR power control parameters, the AMR power is controlled. In HW II BTS power control algorithm and BSC power control algorithm, the BSC can control the AMR calls and the non-AMR calls through the settings different power control parameters.
11 AMR
The MSs that support AMR and those that do not support AMR co-exist in the network. Thus, the interference resistance capabilities of MSs on the network are imbalanced. To minimize the difference of interference resistance capabilities between MSs, the separation of the power control parameters for AMR calls and non-AMR calls function is achieved in Huawei products. Different power control thresholds are set for AMR calls and non-AMR calls. Generally, an AMR call has lower power transmission than a non-AMR call through the adjustment to power control parameters. The configuration of power control parameters for the AMR call conforms to the following principles:
l
Set the values of AMR UL RX_LEV Upper Threshold, AMR UL RX_LEV Lower Threshold, AMR DL RX_LEV Upper Threshold, and AMR DL RX_LEV Lower Threshold to be less than the values of the UL RX_LEV Upper Threshold, UL RX_LEV Lower Threshold, DL RX_LEV Upper Threshold, and DL RX_LEV Lower Threshold non-AMR call parameters. Set the values of AMR ULQual.Upper Threshold, AMR UL Qual. Lower Threshold, AMR DL Qual. Upper Threshold, and AMR DL Qual. Lower Threshold to be greater than the values of the UL Qual. Upper Threshold, UL Qual. Lower Threshold, DL Qual. Upper Threshold, and DL Qual. Lower Threshold non-AMR call parameters. The configurations of other power control parameters remain consistent with those of the non-AMR call.
With the higher robustness than that of the common speech codec, the AMR speech codec can achieve better performance when the C/I ratio is lower than the normal value. Thus in HW III BSC power control algorithm, the AMR power control differs from the common speech codec power control on the setting of the quality threshold parameter. In HW III BSC power control algorithm, the quality control thresholds are set for FR AMR and HR AMR calls. The parameters are as follows:
l l l l l l l l
HwIII UL AFS Rex Qual.Upper Threshold(dB) HwIII UL AFS Rex Qual.Lower Threshold(dB) HwIII UL AHS Rex Qual.Upper Threshold(dB) HwIII UL AHS Rex Qual.Lower Threshold(dB) HwIII DL AFS Rex Qual.Upper Threshold(dB) HwIII DL AFS Rex Qual.Lower Threshold(dB) HwIII DL AHS Rex Qual.Upper Threshold(dB) HwIII DL AHS Rex Qual. Lower Threshold(dB)
Control the power according to the values of the preceding parameters and the HW III BSC power control algorithm. For details, see 6.3.4 Huawei III Power Control Algorithm.
11.3.5 AMR Channel Assignment

The AMR channel assignment can be controlled through parameter setting. The principle for assigning AMR channels is as follows:
l
HR AMR has similar performance in speech quality to that of FR. However, the occupied radio bandwidth on the Um interface is just half that of FR. Therefore, HR AMR can increase the system capacity effectively. When the AMR TCH/H Prior Allowed is set to Yes, and an AMR dual-rate call arrives, the AMR channel assignment is as follows:
Issue 02 (2008-06-30)
11 AMR
If the usage of traffic channels of the cell is greater than the AMR TCH/H Prior Cell Load Threshold, AMR HR channels are preferentially assigned. On other occasions, AMR FR channels are preferentially assigned.
NOTE
Only when TCH Rate Modify is set to Yes,whether HR resources or FR resources are assigned to the MS is determined based on traffic volume.
l
Because the AMR function is TRX-level, the TRXs that support AMR and the TRXs that do not support AMR may co-exist in one cell. To fully use AMR resources and provide better services, the channel resources on the AMR TRXs are assigned first for the AMR call and the channel resources on the non-AMR TRXs are assigned first for the Non-AMR call. If the number of TRXs occupied by AMR users exceeds the number of AMR TRXs allowed by license, the AMR calls should be assigned to the TRXs that carry the AMR calls temporarily to ensure that the number of TRXs occupied by AMR users does not exceed the threshold allowed by license.
11.3.6 Impact on KPI

The AMR has an impact on call drop rate, congestion rate, handover-related counters, and traffic volume.
Impact on Call Drop Rate

AMR improves the robustness of the AMR speech frame instead of the robustness of the SACCH frame. Therefore, theoretically, AMR has no impact on TCH Call Drop Rate. In practice, however, when the AMR is used, the TCH Call Drop Rate increases. The reasons are as follows:
l
As for EFR/FR/HR, the difference between the robustness of the SACCH signaling frame and the robustness of the SACCH speech frame is not great. When the speech quality is poor in the region where the signal is poor, the user may hang up the phone. This is not countered as call drop. When the AMR is used, the robustness of the AMR FR speech frame is higher than the robustness of the SACCH signaling frame. Thus, the speech frame in the region where the signal quality is poor can be correctly decoded. The user does not hang up the phone. The SACCH signaling frame, however, cannot be correctly decoded. Thus, the Radio Link Timeout expires and a call drop is generated. Therefore, the TCH Call Drop Rate increases.
Set the AFR Radio Link Timeout, AHR Radio Link Timeout, AFR SACCH MultiFrames, and AHR SACCH Multi-Frames to greater values to improve the robustness of the SACCH, improve the network coverage performance of the AMR, and reduce the call drop rate.
Impact on Congestion Rate

AMR can increase the system capacity. Therefore, AMR can effectively reduce the TCH Congestion Rate. However, AMR can improve only the capacity of TCHs instead of signaling channels. Therefore, AMR cannot reduce the SDCCH Congestion Rate.
Impact on Handover
AMR optimizes the speech not the signaling. Therefore, AMR does not have great impact on handover counters theoretically. However, because AMR can increase the width and depth of
11 AMR
network coverage, users in weak coverage areas can make calls. The receive quality in the measurement report is poor and the bad quality handover is triggered. Therefore, the number of bad quality handovers may increase after AMR is enabled.
Impact on Traffic Volume

ARM has good interference resistance ability. User in some weak coverage areas where calls fail to be made can make calls in ARM codec mode. The possibility of hangup by users is reduced. Therefore, AMR increases the TCH Traffic Volume of the network.
11.4 Capabilities
This describes the functions supported by AMR and the limitations on AMR. AMR provides the following functions:
l
Supporting quality-based intra-cell handover between the full-rate AMR TCH and the halfrate TCH. Supporting different power control strategies for AMR calls and non-AMR calls. Supporting setting ACS, codec rate adjustment threshold and hysteresis, and initial codec rate on a per cell basis.
l l
The limitations on AMR are as follows:

l
The activated ACS can be changed during the handover but cannot be changed when a channel is in use. AMR does not support the features such as TFO, RATSCCH, and pre-handover.
11.5 Implementation
This describes how to configure, verify, and deactivate AMR. 11.5.1 Suggestions on AMR Configuration During the AMR configuration, the FR AMR and HR AMR characteristics help improve the speech quality and network capacity. 11.5.2 Configuring AMR This describes how to configure AMR on the BSC6000 Local Maintenance Terminal. 11.5.3 Verifying AMR This describes how to verify AMR on the BSC6000 Local Maintenance Terminal. 11.5.4 Disabling AMR This describes how to disable AMR by activating the license, configuring the A interface flag, and configuring the speech version supported by the cell.
11.5.1 Suggestions on AMR Configuration

During the AMR configuration, the FR AMR and HR AMR characteristics help improve the speech quality and network capacity. FR AMR has a good interference resistance capability but cannot improve the system capacity. HR AMR can improve the system capacity but has poor interference resistance capability
11 AMR
compared with the FR AMR. To keep the speech quality and system capacity in optimal balance state, Huawei brings forward the channel adaptive adjustment algorithm that is based on the channel quality. The adjustment policies are as follows:
l
When the system capacity is restricted, an additional idle HR channel is generated if an FR AMR call that has good radio signal quality is converted into an HR AMR call. The interference resistance capability of channels can be enhanced if an HR AMR call that has poor radio signal quality is converted into an FR AMR call.
NOTE
The channel adjustment between HR AMR and FR AMR is achieved according to the intra-cell handover procedure.
Based on the features of AMR, the application strategies and scenarios of AMR are concluded as follows:
l
When the system capacity is not restricted, use the features of AMR to improve the call quality. In this scenario, if the AMR calls reach a certain proportion, enable AMR for some TRXs. Use FR AMR to improve the speech quality. When the capacity is restricted, use the features of AMR to improve the network capacity with the prerequisite of ensuring good call quality.
When using the AMR capacity gain for capacity expansion, apply tight frequency reuse based on the high interference resistance capability of AMR. Apply the HR AMR to enable a certain proportion of HR channels to improve the network capacity.
11.5.2 Configuring AMR

This describes how to configure AMR on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. Ensure that in the BSC6000V900R008 Exceptional Commercial License Application Template, the Resource number column corresponding to the Number of TRXs supporting AMR in the License control items column is filled with the actual number of TRXs that support AMR. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Context
With Huawei MSC, the BSC should be configured with full-rate speech version 3, half-rate speech version 3, or both. For detailed configuration, refer to the user manuals related to Huawei MSC.
Procedure
Step 1 Set the A interface Tag to GSM_PHASE_2+. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then select Configure BSC Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 11-6.
11-18
11 AMR
Figure 11-6 Configuring A interface tag of the BSC
2.
On the Basic Data tab page, set the A Interface Tag to GSM_PHASE_2+.
Step 2 Set the speech version in a cell to full-rate speech version 3 or half-rate speech version 3. 1. On the BSC6000 Local Maintenance Terminal, right-click the target cell on the Management Tree tab page, and then select Configure Cell Attributes from the shortcut menu. In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the displayed dialog box, click Set Cell Properties. A dialog box is displayed, as shown in Figure 11-7.
2. 3.
Issue 02 (2008-06-30)
11-19
11 AMR
4.
In the Advanced Attributes area, click Call Control. A dialog box is displayed, as shown in Figure 11-8.
11-20
Issue 02 (2008-06-30)
11 AMR
Figure 11-8 Setting Call Control Parameter dialog box
5.
Issue 02 (2008-06-30)
11-21
11 AMR
Figure 11-9 Setting advanced call control parameters
6.
On the Access Control tab page, set Speech Version to Support Full-rate Version 3. If the cell supports half rate, set this parameter to Support Half-rate Version 3 at the same time.
Step 3 Configure the AMR call processing parameters. In Figure 11-9, configure the parameters associated with the full-rate and half-rate channels on the AMR Call Control tab page, as shown in Figure 11-10. Figure 11-10 Configuring parameters associated with AMR full-rate calls
11-22
Issue 02 (2008-06-30)

NOTE
11 AMR
One to four coding rates in AMR ACS (F) and AMR ACS (H) of Figure 11-10 can be selected. You can select different algorithms by setting AMR Rate Control Switch. Through AFR radio link timeout and AHR radio link timeout, set the duration of the radio link timeout time.
Step 4 Configure parameters associated with full-rate and half-rate handover in AMR cells. 1. In Figure 11-7, click Handover Data. A dialog box is displayed, as shown in Figure 11-11. Set the parameters Intracell F-H HO Allowed. Figure 11-11 Configuring parameters associated with full-rate and half-rate handover in AMR cells
2.
Set Intracell F-H HO Start Time(s), Intracell F-H HO Last Time(s), F2H HO th, and H2F HO th.
Step 5 Configure the AMR power control parameters in a cell. 1. On the page shown in Figure 11-7, click Power Control. A dialog box is displayed, as shown in Figure 11-12. Set Power Control Algorithm Switch to Huawei II Power Control Algorithm or Huawei III Power Control Algorithm.
Issue 02 (2008-06-30)
11-23
11 AMR
Figure 11-12 Setting power control parameters
2.
11-24
Issue 02 (2008-06-30)
11 AMR
Figure 11-13 Configuring AMR power control parameters in a cell
3.
Based on the value of Power Control Algorithm Switch, click the Huawei II Power Control Algorithm or Huawei III Power Control Algorithm tab, and set the parameters related to the AMR power control.
Step 6 Configure the AMR channel management parameters in a cell. 1. In Figure 11-7, click Channel Management. A dialog box is displayed, as shown in Figure 11-14.
Issue 02 (2008-06-30)
11-25
11 AMR
Figure 11-14 Set Channel Parameter dialog box
2.
11-26
Issue 02 (2008-06-30)
11 AMR
Figure 11-15 Configuring AMR channel management parameters in a cell
3.
On the HWII Channel Assignment and Radio Channel Control tab page, set the parameters AMR TCH/H Prior Allowed and AMR TCH/H Prior Cell Load Threshold.
Step 7 If a BTS site supports AMR, but its software does not AMR, you should acquire the qualified BTS software versions according to the requirements listed in GBSS products and software versions. For details, see Maintaining the BTS. Otherwise, the configuration of AMR fails. ----End
11.5.3 Verifying AMR

This describes how to verify AMR on the BSC6000 Local Maintenance Terminal.
Prerequisite
l l
The BSC6000 Local Maintenance Terminal is started normally. The communication between the BSC and the BTS is normal.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, click the Trace and Monitor tab. On the tab page, choose Trace > Trace User Message. Double-click it. A dialog box is displayed, as shown in Figure 11-16.
Issue 02 (2008-06-30)
11-27
11 AMR
Step 2 Set parameters in the Interface Type, Tracing Mode, and Color areas. Set the IMSI, TMSI, MSISDN, IMEI, or Channel of the user to be traced. Click OK to start tracing. The result is displayed, as shown in Figure 11-17. Figure 11-17 Trace User Message window
Step 3 Select the area where the CHANNEL ACTIVATION (CHANNEL ACTIVATION are displayed in two places in the dialog box. You need select the one near the ASSIGNMENT
11 AMR
COMPLETE.) exists, and then double-click the area. A dialog box is displayed, as shown in Figure 11-18. Figure 11-18 Displayed result
If the value of the speech-coding-algor is gsm-speech-coding-algorithm-version(3), you can infer that AMR is applied. Otherwise, AMR is not applied. ----End
11.5.4 Disabling AMR

This describes how to disable AMR by activating the license, configuring the A interface flag, and configuring the speech version supported by the cell.
Prerequisite
The AMR is activated.
Procedure
l None of the cells controlled by the BSC supports AMR if the BSC uses the licenses that do not support AMR. 1. Obtain the license. The license is required to not support AMR. Ensure that the value of Number of TRXs supporting AMR in the license file is 0. For how to obtain the license, see Downloading the BSC License. Activate the license that does not support AMR. For the detailed procedure, see Activating the BSC License.
2. l
Set the A Interface Tag to GSM_PHASE_1 or GSM_PHASE_2. None of the cells controlled by the BSC supports AMR in this case. 1. On the BSC6000 Local Maintenance Terminal, right-click the BSC6000 on the Management Tree tab page. Choose Configure BSC Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 11-19.
Issue 02 (2008-06-30)
11 AMR
Figure 11-19 Configuring A interface tag of the BSC
2. l
On the Basic Data tab page, set A Interface Tag to GSM_PHASE_1 or GSM_PHASE_2.
Disable full-rate speech version 3 and half-rate speech version 3 so that the cell does not support AMR. 1. On the BSC6000 Local Maintenance Terminal, right-click the target cell on the Management Tree tab page, and then choose Configure Cell Attributes from the shortcut menu. In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the displayed dialog box, click Set Cell Properties. A dialog box is displayed, as shown in Figure 11-20.
2. 3.
11-30
Issue 02 (2008-06-30)
11 AMR
Figure 11-20 Setting the cell attributes
4.
Click Call Control, and then click Advanced in the displayed page. A dialog box is displayed, as shown in Figure 11-21.
Issue 02 (2008-06-30)
11-31
11 AMR
Figure 11-21 Setting advanced call control parameters
5. 6. ----End
On the Access Control tab page, adjust Speech Version so that the Value is not Support Full-rate Version 3 or Support Half-rate Version 3. Click OK to disable AMR.

This lists the counters related to AMR.
Alarms
None.
Counters
The counters related to AMR are listed in the following table. Table 11-5 Assignment measurement per cell Specification A3167A A3168C Description Speech Version 3 Completed Assignments (Excluding Directed Retry) (TCHF) Speech Version 3 Completed Assignments (Excluding Directed Retry) (TCHH)
11-32
Issue 02 (2008-06-30)
11 AMR
Table 11-6 Intra-cell handover measurement per cell Specification H3055A H3055B H3005A H3005B H3015A H3015B H3025A H3025B CH3035A CH3035B TH3035A TH3035B Description Internal Intra-Cell Handovers Not Initiated (AMR) (TCHF-TCHH) Internal Intra-Cell Handovers Not Initiated (AMR) (TCHH-TCHF) Internal Intra-Cell Handover Requests (AMR) (TCHF-TCHH) Internal Intra-Cell Handover Requests (AMR) (TCHH-TCHF) Internal Intra-Cell Handover Commands (AMR) (TCHF-TCHH) Internal Intra-Cell Handover Commands (AMR) (TCHH-TCHF) Failed Internal Intra-Cell Handovers (AMR) (TCHF-TCHH) Failed Internal Intra-Cell Handovers (AMR) (TCHH-TCHF) Successful Internal Intra-Cell Handovers (AMR) (TCHF-TCHH) Successful Internal Intra-Cell Handovers (AMR) (TCHH-TCHF) Success Rate of Internal Intra-Cell Handover (AMR) (TCHF-TCHH) Success Rate of Internal Intra-Cell Handover (AMR) (TCHH-TCHF)
Table 11-7 RQI measurement based on TA per TRX Specification S4400D S4401D S4402D S4403D S4404D S4405D S4406D
Issue 02 (2008-06-30)
Description RQI (TA = 0) RQI (TA = 1) RQI (TA = 2) RQI (TA = 3) RQI (TA = 4) RQI (TA = 5) RQI (TA = 6)
11-33
11 AMR
Specification S4407D S4408D S4409D S4410D S4411D S4413D S4414D S4415D S4416D S4417D S4418D S4419D S4420D S4421D S4422D S4423D S4424D S4425D S4426D S4427D S4428D S4429D S4430D S4432D S4434D S4436D S4438D S4440D S4445D S4450D
Description RQI (TA = 7) RQI (TA = 8) RQI (TA = 9) RQI (TA = 10) RQI (TA = 11) RQI (TA = 13) RQI (TA = 14) RQI (TA = 15) RQI (TA = 16) RQI (TA = 17) RQI (TA = 18) RQI (TA = 19) RQI (TA = 20) RQI (TA = 21) RQI (TA = 22) RQI (TA = 23) RQI (TA = 24) RQI (TA = 25) RQI (TA = 26) RQI (TA = 27) RQI (TA = 28) RQI (TA = 29) RQI (TA = 30 or 31) RQI (TA = 32 or 33) RQI (TA = 34 or 35) RQI (TA = 36 or 37) RQI (TA = 38 or 39) RQI (TA = 40 or 44) RQI (TA = 45 or 49) RQI (TA = 50 or 54)
11-34
Issue 02 (2008-06-30)
11 AMR
Specification S4455D S4463D S4400C S4401C S4402C S4403C S4404C S4405C S4406C S4407C S4408C S4409C S4410C S4411C S4412C S4413C S4414C S4415C S4416C S4417C S4418C S4401C S4419C S4420C S4400C S4421C S4422C S4423C S4424C S4425C
Description RQI (TA = 55 or 63) RQI (TA greater than 63) MRs with RQI (TA = 0) MRs with RQI (TA = 1) MRs with RQI (TA = 2) MRs with RQI (TA = 3) MRs with RQI (TA = 4) MRs with RQI (TA = 5) MRs with RQI (TA = 6) MRs with RQI (TA = 7) MRs with RQI (TA = 8) MRs with RQI (TA = 9) MRs with RQI (TA = 10) MRs with RQI (TA = 11) MRs with RQI (TA = 12) MRs with RQI (TA = 13) MRs with RQI (TA = 14) MRs with RQI (TA = 15) MRs with RQI (TA = 16) MRs with RQI (TA = 17) MRs with RQI (TA = 18) MRs with RQI (TA = 1) MRs with RQI (TA = 19) MRs with RQI (TA = 20) MRs with RQI (TA = 0) MRs with RQI (TA = 21) MRs with RQI (TA = 22) MRs with RQI (TA = 23) MRs with RQI (TA = 24) MRs with RQI (TA = 25)
Issue 02 (2008-06-30)
11-35
11 AMR
Specification S4426C S4427C S4428C S4429C S4430C S4432C S4434C S4436C S4438C S4440C S4445C S4450C S4455C S4463C AS4400D AS4401D AS4402D AS4403D AS4404D AS4405D AS4406D AS4407D AS4408D AS4409D AS4410D AS4411D AS4412D AS4413D AS4414D AS4415D
Description MRs with RQI (TA = 26) MRs with RQI (TA = 27) MRs with RQI (TA = 28) MRs with RQI (TA = 29) MRs with RQI (TA = 30-31) MRs with RQI (TA = 32-33) MRs with RQI (TA = 34-35) MRs with RQI (TA = 36-37) MRs with RQI (TA = 38-39) MRs with RQI (TA = 40-44) MRs with RQI (TA = 45-49) MRs with RQI (TA = 50-54) MRs with RQI (TA = 55-63) MRs with RQI (TA greater than 63) Mean RQI (TA = 0) Mean RQI (TA = 1) Mean RQI (TA = 2) Mean RQI (TA = 3) Mean RQI (TA = 4) Mean RQI (TA = 5) Mean RQI (TA = 6) Mean RQI (TA = 7) Mean RQI (TA = 8) Mean RQI (TA = 9) Mean RQI (TA = 10) Mean RQI (TA = 11) Mean RQI (TA = 12) Mean RQI (TA = 13) Mean RQI (TA = 14) Mean RQI (TA = 15)
11-36
Issue 02 (2008-06-30)
11 AMR
Specification AS4416D AS4417D AS4418D AS4419D AS4420D AS4421D AS4422D AS4423D AS4424D AS4425D AS4426D AS4427D AS4428D AS4429D AS4430D AS4432D AS4434D AS4436D AS4438D AS4440D AS4445D AS4450D AS4455D AS4463D
Description Mean RQI (TA = 16) Mean RQI (TA = 17) Mean RQI (TA = 18) Mean RQI (TA = 19) Mean RQI (TA = 20) Mean RQI (TA = 21) Mean RQI (TA = 22) Mean RQI (TA = 23) Mean RQI (TA = 24) Mean RQI (TA = 25) Mean RQI (TA = 26) Mean RQI (TA = 27) Mean RQI (TA = 28) Mean RQI (TA = 29) Mean RQI (TA = 30-31) Mean RQI (TA = 32-33) Mean RQI (TA = 34-35) Mean RQI (TA = 36-37) Mean RQI (TA = 38-39) Mean RQI (TA = 40-44) Mean RQI (TA = 45-49) Mean RQI (TA = 50-54) Mean RQI (TA = 55-63) Mean RQI (TA greater than 63)
Table 11-8 AMR service measurement per cell Specification A0401A A0401B Description Request Times of Full Rate Speech Version 1 Request Times of Full Rate Speech Version 2
Issue 02 (2008-06-30)
11-37
11 AMR
Specification A0401C A0402A A0402B A0402C A0409A A0409B A0409C A0409D A0409E A0409F A0409G M0121A M0121B A0409H A0409I A0409J A0409K A0409L A0409M A0409N A0409P
Description Request Times of Full Rate Speech Version 3 Request Times of Half Rate Speech Version 1 Request Times of Half Rate Speech Version 2 Request Times of Half Rate Speech Version 3 Number of Speech Version Messages Call Proportion of Full Rate Speech Version 1 Call Proportion of Full Rate Speech Version 2 Call Proportion of Full Rate Speech Version 3 Call Proportion of Half Rate Speech Version 1 Call Proportion of Half Rate Speech Version 2 Call Proportion of Half Rate Speech Version 3 Full Rate AMR Service Channel Call Drop Times Half Rate AMR Service Channel Call Drop Times Full Rate TCH Successful Occupancy Times (Signaling Channel) Full Rate AMR TCH Successful Call Occupancy Times (Service Channel) Full Rate AMR TCH Successful Handover Occupancy Times (Service Channel) Half Rate TCH Successful Occupancy Times (Signaling Channel) Half Rate AMR TCH Successful Call Occupancy Times (Service Channel) Half Rate AMR TCH Successful Handover Occupancy Times (Service Channel) Full Rate AMR Call Drop Ratio Half Rate AMR Call Drop Ratio
11-38
Issue 02 (2008-06-30)
11 AMR
Table 11-9 AMR channel status measurement per cell Specification R3551C R3552C AR3551C AR3552C Description Number of Busy AMR Traffic Channels (TCHF) Number of Busy AMR Traffic Channels (TCHH) Traffic Volume of AMR TCHFs Traffic Volume of AMR TCHHs
Table 11-10 RQI measurement per TRX Specification S4400E S4401E S4402E S4403E S4404E S4405E S4406E S4407E S4408E S4409E S4410E S4411E S4412E S4413E S4414E S4415E S4416E S4417E S4418E S4419E S4420E
Issue 02 (2008-06-30)
Description MRs with RQI=0-1 MRs with RQI=1-2 MRs with RQI=2-3 MRs with RQI=3-4 MRs with RQI=4-5 MRs with RQI=5-6 MRs with RQI=6-7 MRs with RQI=7-8 MRs with RQI=8-9 MRs with RQI=9-10 MRs with RQI=10-11 MRs with RQI=11-12 MRs with RQI=12-13 MRs with RQI=13-14 MRs with RQI=14-15 MRs with RQI=15-25 MRs with RQI=25-35 MRs with RQI=35-45 MRs with RQI=45-55 MRs with RQI Greater than 55 Ratio of RQI=0-1
11-39
11 AMR
Specification S4421E S4422E S4423E S4424E S4425E S4426E S4427E S4428E S4429E S4430E S4431E S4432E S4433E S4434E S4435E S4436E S4437E S4438E S4439E
Description Ratio of RQI=1-2 Ratio of RQI=2-3 Ratio of RQI=3-4 Ratio of RQI=4-5 Ratio of RQI=5-6 Ratio of RQI=6-7 Ratio of RQI=7-8 Ratio of RQI=8-9 Ratio of RQI=9-10 Ratio of RQI=10-11 Ratio of RQI=11-12 Ratio of RQI=12-13 Ratio of RQI=13-14 Ratio of RQI=14-15 Ratio of RQI=15-25 Ratio of RQI=25-35 Ratio of RQI=35-45 Ratio of RQI=45-55 Ratio of RQI Greater Than 55
11.7 References
l
GSM 05.03 V7.3.1 : "Digital cellular telecommunications system (Phase 2+); Channel coding" GSM 05.09 V7.7.1 : "Digital cellular telecommunications system (Phase 2+); Link Adaptation" GSM 04.08 V7.21.0: "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification" GSM 06.90 V7.2.1 : "Digital cellular telecommunications system (Phase 2+); Adaptive Multi-Rate (AMR) speech transcoding " GSM 06.91 V7.1.1 : "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frames for Adaptive Multi Rate (AMR) speech traffic channels "
11-40
Issue 02 (2008-06-30)

l
11 AMR
GSM 06.92 V7.1.1 : "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Adaptive Multi-Rate (AMR) speech traffic channels " GSM 06.93 V7.5.0 : "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Adaptive Multi Rate (AMR) speech traffic channels " GSM 06.94 V7.1.1 : "Digital cellular telecommunications system (Phase 2+); Voice Activity Detection (VAD) for Adaptive Multi-Rate speech traffic channels " GSM 08.08 V7.7.0 : "Digital cellular telecommunications system (Phase 2+); Mobileservices Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification " GSM 08.58 V7.4.1 : "Digital cellular telecommunications system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 3 specification " GSM 08.60 V7.3.0 : "Digital cellular telecommunications system (Phase 2+); In-band control of remote transcoders and rate adaptors for full rate traffic channels " GSM 08.61 V7.3.0 : "Digital cellular telecommunications system (Phase 2+); In band control of remote transcoders and rate adaptors for half rate traffic channels "
Issue 02 (2008-06-30)
11-41
12 Half-Rate Service
12
About This Chapter
Half-Rate Service
12.1 Overview The use of a new speech codec algorithm in half-rate service improves the bearer capability, of the network, provided that the network resources remain unchanged. 12.2 Availability This lists the NEs, software, and licenses required for the implementation of half-rate service. 12.3 Impact This describes the impact of half-rate service on system performance. 12.4 Technical Description This describes the technical aspects of half-rate service. The half-rate service divides the multiframes transmitted on the Um interface into two categories for two MSs, one of which receives the even multiframes while the other receives the odd multiframes. 12.5 Capabilities BSC6000V900R008C01 supports up to 2048 TRXs that can provide half-rate services. 12.6 Implementation This describes how to configure half-rate services, verify half-rate services, enable the function of reserving priority resources, adjust half-rate services, and disable half-rate services. 12.7 Maintenance Information This lists the counters related to the half-rate service. 12.8 References None
Issue 02 (2008-06-30)
12-1
12.1 Overview
The use of a new speech codec algorithm in half-rate service improves the bearer capability, of the network, provided that the network resources remain unchanged.
Definition
The half-rate service is a service where the speech encoding rate is reduced to half of the fullrate 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.
Purposes
If the half-rate service is enabled, the number of users supporting speech services in the system is doubled without the addition of TRXs. Thus, the frequency reuse rate is enhanced. The network operators can fully utilize the network resources and minimize the operation cost.
Terms
Terms Couple channel Definition One timeslot carries two idle TCHHs. In this case, the two TCHHs are called the couple channel. One timeslot carries an occupied TCCH and an idle TCHH. In this case, the idle TCHH is called the single channel, also called the channel fragment or fragment directly. Full-rate speech channel Half-rate speech channel The conversion from a TCHF to a TCHH or from a TCHH to a TCHF is called rate adjustment. Half-rate speech algorithm operating at 5.6 kbit/s Reserved for future use Half-rate AMR speech algorithm operating at 4.75-7.4 kbit/s Full-rate speech algorithm operating at 13 kbit/s Enhanced full-rate speech algorithm operating at 12.2 kbit/s
Issue 02 (2008-06-30)
Single channel
TCHF TCHH Rate adjustment
Half-rate version 1 Half-rate version 2 Half-rate version 3 Full-rate version 1 Full-rate version 2
12-2
Terms Full-rate version 3 C/I ratio
Definition Full-rate AMR speech algorithm operating at 4.75-12.2 kbit/s It is the ratio of the strength of a carrier signal to the strength of an interfering signal.

Acronyms and Abbreviations AMR EFR FR HR Full Spelling Adaptive Multi-Rate Enhanced Full Rate Full Rate Half Rate
12.2 Availability
This lists the NEs, software, and licenses required for the implementation of half-rate service.
NEs Involved
Table 12-1 lists the NEs involved in half-rate service. Table 12-1 NEs involved in half-rate service MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 12-2 lists the versions of GBSS products that support half-rate service. Table 12-2 GBSS products and software versions Product BSC
Issue 02 (2008-06-30)
Version BSC6000 V900R008C01 and later releases

12-3
Product BTS BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM BTS3X BTS3002C BTS3001C
Version BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases G3BTS32.30000.01.1130 and later releases G3BTS36.30000.02.0820 and later releases G3BTS34.30000.07.0301 and later releases
Miscellaneous
Half-rate service is available when the license is obtained. To enable a specified number of TRXs providing half-rate service, the license that supports the TRX quantity must be obtained.
12.3 Impact
This describes the impact of half-rate service on system performance.

The impact of half-rate service on system performance is as follows:
l
If the TCHFs are configured as TCHHs, the interference on the entire network is decreased as the number of occupied timeslots are reduced. If the half-rate service is enabled when the C/I ratio of the entire network is greater than 10 dB (the C/I is favorable), the voice quality of the entire network is decreased. The higher proportion of the half-rate traffic volume in the entire network, the sharper the voice quality in the entire network is decreased. If the half-rate service is enabled when the C/I ratio of the entire network is smaller than 10 dB (the C/I is unfavorable), the voice quality of the entire network is increased. The higher proportion of the half-rate traffic volume in the entire network, the sharper the voice quality in the entire network is increased. The half-rate service has no obvious impact on relevant KPIs.
12-4

None

This describes the technical aspects of half-rate service. The half-rate service divides the multiframes transmitted on the Um interface into two categories for two MSs, one of which receives the even multiframes while the other receives the odd multiframes. Figure 12-1 shows the implementation of half-rate service on the Um interface. Figure 12-1 Implementation of half-rate service on the Um interface
Sub-timeslot 0 TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS 0 2 4 6 8 10 SACCH TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS HS 13 15 17 19 21 23 12
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS TCH/HS 1 3 5 7 9 11 14 16 18 20 22 24 Sub-timeslot 1
SACCH HS 25
For the MS, the processing on the uplink and downlink is as follows:
l
Downlink direction With half-rate service, the MS decodes only the two odd or even multiframes of the four multiframes.
Uplink direction With half-rate service, the MS sends only the two odd or even multiframes of the four multiframes.
For the BTS, the processing on the uplink and downlink is as follows:
l
Downlink direction With half-rate service, the BTS encodes only the data on sub-timeslots 0 and 1.
The BTS transmits, on the even multiframes, the two multiframes generated from the encoding of the data on sub-timeslot 0. The BTS transmits, on the odd multiframes, the two multiframes generated from the encoding of the data on sub-timeslot 1.
The half-rate service uses the same modulation mode on the Um interface as the full-rate service.
l
Uplink direction With half-rate service, the BTS demodulates every multiframe on the Um interface and performs balance calculation without distinguishing between full-rate and half-rate. When decoding the multiframes, the BTS decodes the mean and odd frames and then puts the multiframes on sub-timeslots 0 and 1 respectively.
Issue 02 (2008-06-30)
12-5
NOTE
Figure 12-1 shows the subtimeslots 0 and 1.
12.4.1 Channel Rate Assignment Strategies If the half-rate service is enabled, the BSC selects different channel assignment algorithms based on the channel assignment strategies in the data configuration after the BSC receives an Assignment Request message from the MSC. 12.4.2 Rate Adjustment Algorithms The rate adjustment is triggered during the channel assignment process. Thus, it is a real-time approach for rate adjustment. 12.4.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. 12.4.4 Estimation of the Number TCHFs and TCHHs in a Cell In some situations, the network operators need to estimate the number of TCHFs and TCHHs available in a cell.
12.4.1 Channel Rate Assignment Strategies

If the half-rate service is enabled, the BSC selects different channel assignment algorithms based on the channel assignment strategies in the data configuration after the BSC receives an Assignment Request message from the MSC. The following lists the two channel rate assignment strategies available at present:
l l
Channel rate assignment strategy controlled by the MSC Channel rate assignment strategy controlled by the BSC
For details about the channel rate assignment strategies, refer to 2.3.3 Channel Assignment Algorithms. In channel assignment algorithms, the system determines to assign half-rate channels or fullrate channels based on the traffic volume of the network. If one of the following conditions occurs, you can infer that the network is busy:
l
The channel seizure ratio exceeds the TCH Traffic Busy Threshold.
NOTE
Channel seizure ratio = (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% Here, full-rate or half-rate channels contain the dynamic PDCHs that do not carry any packet services.
l
For the AMR calls, the channel seizure ratio exceeds the AMR TCH/H Prior Cell Load Threshold. In a concentric cell, when the Allow Rate Selection Based on Overlaid/Underlaid Subcell Load is enabled:
For the calls in the overlaid subcell, the channel seizure ratio of the overlaid subcell exceeds Busy Threshold of TCH Traffic in Overlaid Subcell. For the calls in the underlaid subcell, the channel seizure ratio of the underlaid subcell exceeds TCH Traffic Busy Underlay Threshold.
For the Flex Abis, when the Abis Resource Adjustment TCHH Function Switch is enabled, the fixed Abis channel seizure ratio exceeds the Fix Abis Prior Choose Abis
12-6
Load Thred(%) and the Flex Abis channel seizure ratio exceeds the Flex Abis Prior Choose Abis Load Thred(%).
l
When the HR Allocation Flag while Ater Resource Congested is enabled, the Ater resource usage ratio exceeds Congestion Ratio on Ater Resource(%).
If the network is busy, half-rate channels are assigned preferably. If the network is not busy, full-rate channels are assigned preferably. When assigning the channels, the system determines whether to trigger rate adjustment based on the channel usage in the cell. To enable real-time rate adjustment, the channels obtained through a rate adjustment process are assigned to the current calls immediately. In conclusion, the principles for radio resource assignment are as follows:
l
When the network is not busy, full-rate channels are assigned preferably to ensure speech quality. When the network is busy, half-rate channels are assigned preferably to ensure that more users can gain access to services. For half-rate calls, the single channels are assigned preferably so that the half-rate channels are utilized optimally and the fragments are minimized. To optimize the resource usage, the channels on the TRXs that are not qualified for rate adjustment should be assigned first so that the channels on the TRXs that are qualified for rate adjustment are reserved for future use, as long as the current channel rate scheme meets the service requirements.
NOTE
Set TCH Rate Modify to Yes. In this case, when the BSC channel assignment strategy is selected the half-rate channels or full-rate channels are assigned depending on the network traffic.
12.4.2 Rate Adjustment Algorithms

The rate adjustment is triggered during the channel assignment process. Thus, it is a real-time approach for rate adjustment. The rate adjustment consists of the following:
l l l l
Adjustment from the TCHH to the TCHF Adjustment from the TCHF to the TCHH Adjustment from the PDCH to the TCHH Adjustment from the TCHH to the PDCH
The TCHF/TCHH rate adjustment procedure is triggered when the type of the channel to be requested is TCHH only, TCHH preferred, TCHF only, or TCHF preferred. After the TCH Rate Adjust Allow is set to Yes, for the channels that are not requested for in the immediate assignment procedure or the handover channel requests not caused by the dynamic adjustment of other channels, the following adjustment principles are applied:
l
If the MS is allocated a TCHF as no TCHH is available upon request, the adjustment from TCHF to TCHH is triggered. If the MS is allocated a TCHH as no TCHF is available upon request, the adjustment from TCHH to TCHF is triggered. The handover may also be triggered. If no channel is available for allocation in the cell, the BSC may request the PCU for a channel conversion from the PDCH to the TCH.
Issue 02 (2008-06-30)
l
When the PCU requests for a channel and the configuration type of the channel is a dynamic PDCH, the TCHH is converted to the PDCH if the current channel type is TCHH. The channel that configured as dynamic PDCH works as PDCH when carrying PS services. If the BSC requests the PCU for a channel conversion from the PDCH to the TCH, the PCU releases the channel. If the call requests the TCHF only, the system converts the channel to the TCHF; otherwise, the system converts the channel to the TCHH and assigns the channel to a call in the queue.
12.4.2.1 Rate Adjustment Algorithms for Different Channel Request Types Rate adjustment algorithms vary with the types of rates for requested channels. 12.4.2.2 TCHF-TCHH Adjustment Procedures This describes the TCHF-to-TCHH adjustment and the TCHH-to-TCHF adjustment. 12.4.2.3 TCHH-PDCH Adjustment Procedures This describes the TCHH-to-PDCH adjustment and the PDCH-to-TCHH adjustment.
Rate Adjustment Algorithms for Different Channel Request Types

Rate adjustment algorithms vary with the types of rates for requested channels. There are three types of channel rates available in a channel assignment request:
l l l
TCHF only TCHH only/TCHH preferred TCHF preferred
If the channel rate type in a channel assignment request is TCHF only, the channel request is accepted when the following requirements are met; otherwise, the channel request is rejected. Figure 12-2 shows the channel rate adjustment procedure.
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 into the TCHF and then assigns the TCHF. If no idle TCHF and idle couple channel are available but an idle single channel is available, the BSC determines whether there are more than one idle adjustable TCHHs in the cell. If there are more than one idle TCHHs 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 rejects the channel assignment request.
12-8
Issue 02 (2008-06-30)
Figure 12-2 Channel rate adjustment procedure for TCHF only

Start
TCHF only requested
Whether there are TCHFs? No Whether there are appropriate couple channels? No Whether there are more than one TCHH? No Request rejected
Yes
Yes
Convert all the couple channels into the TCHFs
Yes
Initiate an intra-cell handover, and then convert all the couple channels generated after the handover into the TCHFs
Assign TCHF
End
If the channel rate type in a channel assignment request is TCHH only/TCHH preferred, the channel request is accepted when the following requirements are met; otherwise, the channel request is rejected. Figure 12-3 shows the channel rate adjustment procedure.
l l
If an idle single channel is available, the BSC assigns the single channel directly. If no idle single is available but an idle couple channel is available, the BSC assigns the idle TCHH of the couple channel. If no idle single channel and couple channel are available but an idle TCHF is available, the BSC converts the TCHF into the couple channel and assigns the idle TCHH of the couple channel.
NOTE
If the BSC assigns the channels of single channels preferably, the half-rate channels can be utilized optimally and fragments minimized.
Issue 02 (2008-06-30)
12-9
Figure 12-3 Channel rate adjustment procedure for TCHH only/TCHH preferred
Start
TCHH requested
Whether there are appropriate single channels? No Whether there are appropriate couple channels? No Whether there are appropriate TCHF? No Channels fail to be assigned
Yes
Yes
Yes
Convert the TCHFs into the couple channels
Assign the TCHHs
End
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 12-4 shows the channel rate adjustment procedure.
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 into the TCHF and then assigns the TCHF. If no idle TCHF and idle couple channel are available but an idle single channel is available, the BSC determines whether there are more than one idle adjustable TCHHs in the cell. If there are more than one idle TCHHs 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.
12-10
Issue 02 (2008-06-30)
Figure 12-4 Channel rate adjustment procedure for TCHF preferred

Start
TCHF preferred requested
Whether there are appropriate TCHFs? No Whether there are appropriate couple channels? No
Yes
Yes
Convert all the couple channels into the TCHFs
Whether there are more than one TCHHs?
Yes
Initiate an intra-cell handover and convert the couple channels formed after the handover into the TCHFs
No Assign the TCHHs Assign the TCHFs
End
NOTE
Only when Enhanced TCH Adjust Allowed is set to Yes, the calls on single channels can be handed over to other channels and then an adjustment is triggered when a TCHH is converted into a TCHF.
TCHF-TCHH Adjustment Procedures

This describes the TCHF-to-TCHH adjustment and the TCHH-to-TCHF adjustment.
TCHF-to-TCHH Adjustment
1. If the MS is not allocated resources for its channel request, the channel request is placed in a queue, the duration for a second channel request attempt is defined by the parameter Timer of Waiting Channel Adjust (ms). By default, the timer is three seconds in length.
l
Queuing fails
Issue 02 (2008-06-30)

For the TCHH only request, a failure message is returned. For the TCHH preferred request, the second preferred channel such as the couple channel or TCHF is allocated.
Queuing succeeds The BSC turns a TCHF into two couple channels, sets the channel attributes as required, initiates the configuration command of adjusting the timeslots, starts Timer of Waiting BMRC Response (ms), and takes related performance measurement. If Flex Abis is enabled, go to 2 and take related performance measurement.
2.
After adjusting the timeslots, the BSC issues a channel attribute adjustment command to the BTS. If the BSC timeslot adjustment command and the channel type type adjustment command expire, the BSC resends the adjustment commands. On receiving the adjustment command, the BTS starts channel type adjustment and, upon completion of the channel type adjustment, sends the Status Change Report to the BSC. On receiving the Status Change Report from the BTS, the BSC sets the couple channel obtained through channel type adjustment to the idle state and the channel adjustment is complete. Then, the BSC assigns the channel to the current call in the queue and takes related performance measurement.
3. 4.
TCHH-to-TCHF Adjustment
1. If the current channel is a couple channel, the channel request is placed in a queue, the duration for waiting for the queuing is defined by the parameter Timer of Waiting Channel Adjust (ms). By default, the timer is three seconds in length.
l
Queuing fails

For the TCHF only request, a failure message is returned. For the TCHF preferred request, the second preferred channel such as the couple channel or single channel is allocated.
Queuing succeeds The BSC converts two couple channels into a TCHF. For details about the subsequent procedures, refer to TCHF-to-TCHH Adjustment. If Flex Abis is not enabled, the BSC initiates the configuration command of adjusting the timeslots, notifies the BTS of the completion of channel conversion, and performs related performance measurement.
2.
If the requested channel is a single channel, the BSC places the channel request in a queue, as long as the conditions are met. The duration for queuing is set to 5.5 seconds as the defragmentation takes a long time.
l
Queuing fails

For the TCHF only request, a failure message is returned. For the TCHF preferred request, the single channel is allocated.
Queuing succeeds The system initiates a forced intra-cell handover on the occupied TCHH of the single channel (the handover is not controlled by the related configuration of handover) and initiates Timer of Waiting CRDLC HO Responses (s), reserving sufficient time for the intra-cell handover. Different operations are performed based on whether a forced handover response is received.
12-12
Issue 02 (2008-06-30)
If a forced handover response is received, the BSC stops the Timer of Waiting CRDLC HO Responses (s) and determines whether the forced handover succeeds. If the forced handover fails, the BSC searches in the queue for an appropriate call to be allocated this single. The other occupied TCHH is not released. If the forced handover succeeds, the channel status is set to Waiting for Releasing the Channel; when the channel status is set to Service Idle, the BSC converts the couple channel into the TCHF. If a forced handover response is not received but the Timer of Waiting CRDLC HO Responses (s) expires, the handover fails. A handover failure procedure is performed.
TCHH-PDCH Adjustment Procedures

This describes the TCHH-to-PDCH adjustment and the PDCH-to-TCHH adjustment.
TCHH-to-PDCH Adjustment
Figure 12-5 shows the TCHH-to-PDCH adjustment procedure. Figure 12-5 TCHH-to-PDCH adjustment procedure
Start
The PCU specifies a CS timeslot
No
Does the timeslot meet the adjustment requirements?
Yes Is the timeslot idle? No No Does the system initiate an intra-cell handover? Yes No Is the intra-cell handover successful? Yes Yes
No The channel assignment fails
Is the priority of the PS service is higher than that of the CS service?
Yes The channel ssignment succeeds
End
Issue 02 (2008-06-30)
12-13
1.
When an MS initiates the PS services, the PCU specifies a CS timeslot if there is no PS traffic channel, and then obtains the current channel type, usage state, and the flag "whether PDCH assignment request can preempt the channels of CS services". If the Channel Type of this timeslot is set to Dynamic PDCH and the flag "whether PDCH assignment request can preempt the channels of CS services" is set to "Yes", proceed as follows:
l
2.
If the timeslot specified by the PCU is idle, the system converts the channel on the timeslot to PDCH, and then the BSC sends the message that the channel request succeeded to the PCU. If the timeslot specified by the PCU is busy, the cell initiates an intra-cell handover, that is the timeslot integration. The timeslot can be either a full-rate timeslot or a halfrate timeslot. (1) Before initiating the intra-cell handover, the system determines whether there are enough idle timeslots in the current cell. The determination rules are as follows:
If there is no idle timeslots including full-rate and half-rate timeslots in the current cell, the intra-cell handover is not performed. If the channel requested by the PCU is a half-rate channel and there is only one idle timeslot available in the cell (including full-rate and half-rate), the intracell handover is not initiated. If the system cannot initiate an intra-cell handover, the system determines whether the priority of the PS service is higher than that of the CS service.
If the priority of the PS service is high, the system releases the channel on the specified timeslot forcibly and converts the channel to PDCH. If the priority of the CS service is higher, the system sends the request failure message to the PCU.
(2) If there are enough idle timeslots in the current cell, the system initiates the intracell handover, that is the timeslot integration. The timeslots can be either full-rate timeslots or half-rate timeslots.
If the system initiates an intra-cell handover and the handover succeeds, the channel on the specified timeslot is converted to PDCH. If the intra-cell handover fails, the system determines whether the priority of the PS service is higher.
NOTE
To avoid new intra-cell handover is triggered during the channel conversion of an intracell handover, the dynamic PDCH is not switched back and the system does not perform half-rate/full-rate adjustment, and queuing and preemption.
(3) If there is no enough timeslots in the current cell, the system determines whether the priority of the PS service is higher.
(4) If the intra-cell handover expires, the system determines whether the priority of the PS service is higher.
PDCH-to-TCHH Adjustment
CAUTION
l
The BSC requests that the dynamic PDCH converted by the PCU must meet the requirements of the CS calls. Thus the factors such as the frequency bands and concentric cells should be considered during the conversion. If the type of the assigned channel required by the CS calls is half rate TCH only and the BSC determines that the rate adjustment is not supported by the TRX where one of the dynamic PDCHs to be converted is located, the BSC does not request the PCU to convert the dynamic PDCH. The BSC should not assign the dynamic PDCH for the CS services. The priority of channels contains the dynamic PDCH bit. If the initial configuration type is a dynamic PDCH, the bit that indicates the priority of channel type is set to 1. That is, the priority is low. In other similar conditions, as the weight of dynamic PDCH is heavier, the priority is lower.
Figure 12-6 shows the PDCH-to-TCHH adjustment procedure. Figure 12-6 TCHH-to-PDCH adjustment procedure
Start
The BSC sends the channel request to the PCU
No
Does the BSC receive the acknowledgement of the channel request? No
Yes Half rate TCH preferable and the TCH Rate Adjust Allow is set to Yes?
Enable the TCH Req Suspend Interval timer
Yes
Covert the PDCH to TCHF
Conver the PDCH to TCHH
The channel assignment fails
The channel assignment succeeds
End
Issue 02 (2008-06-30)
12-15
1.
When no available channels can be assigned to the CS calls, the BSC sends the channel request message to the PCU. The BSC requests the PDCH to convert to the half-rate channel and puts the current calls in a queue. After the BSC receives the acknowledgement of the channel request, it performs operations as follows:
l
2.
If the CS calls request full-rate channels or the TCH Rate Adjust Allow is set to No, the system converts PDCH to TCHF. If the CS calls request half rate TCH preferable or the TCH Rate Adjust Allow is set to Yes, the system converts PDCH to TCHH.
3.
After receiving the reject message of the channel request, the BSC enables the TCH Req Suspend Interval.
NOTE
The dynamic adjustment approach uses the queuing mechanism. Thus, if the 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 queuing expires. If there is no call in the queue when the PCU releases the PDCH, the system converts the PDCH to the TCHF.
12.4.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 different codec mode as the full-rate service and has a codec rate of 5.6 kbit/s. Thus, after the half-rate service is enabled, the voice quality drops as compared to the full-rate service. The MSs of some low-end subscribers 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. However, the MSs of some high-end subscribers 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-end subscribers, 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-end subscribers 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.
12.4.4 Estimation of the Number TCHFs and TCHHs in a Cell

In some situations, the network operators need to estimate the number of TCHFs and TCHHs available in a cell. The estimation of the number of TCHFs and TCHHs in a cell paves the way for the proper configuration of the TCHFs and TCHHs in the cell. Also, with the estimated proportion between the TCHFs and TCHHs you can set the TCH Traffic Busy Threshold more accurately. If TCH Rate Adjust Allow is enabled for all the TRXs in a cell, the TCHFs and TCHHs in the cell can operate in such a balanced way that the services are distributed evenly on the channels.
12-16
Issue 02 (2008-06-30)
Available Information
Suppose that the traffic volume in a cell is 1 Erl, the call loss rate allowed by the network operator is B%, and the number of channels required in the cell is n. If the number of TRXs in the cell is m, then number of the traffic timeslots available in the cell is a and the number of TCHs available in the cell is in the range [a, 2a].
Rules
Providing the traffic volume (1 Erl) and the allowed call loss rate (B%), the number of channels required in the cell (n) can be calculated according to the Erlang B table. The following rules apply:
l
If n <= a, all the traffic channels in the cell can be configured as TCHFs. TCH Traffic Busy Threshold can be set to 100. If the AMR exists, set AMR TCH/H Prior Cell Load Threshold to 99. The dual-rate MSs always select the TCHFs.
If 2a > n > a, the number of TCHFs (f) configured in the cell must meet the condition, that is, f + 2 (a-f) > n (f = [2a-n]). Other timeslots are configured with TCHHs. Set TCH Traffic Busy Threshold to 100 x [2a-n]/a. If the AMR exists, AMR TCH/H Prior Cell Load Threshold is set to be smaller than 100 x [2a-n]/a. When the traffic volume in the cell is large, the dual-rate MSs select the TCHHs.
If n >= 2a, one TCH can be configured as one or two TCHFs and other channels are configured as TCHHs. Huawei also recommends that the capacity of the cell be expanded. The TCHFs are configured for the MSs that support only TCHFs. In this case, the call loss rate is greater than B%. TCH Traffic Busy Threshold is set to 0. If the AMR exists, the AMR TCH/H Prior Cell Load Threshold is set to 0. The dual-rate MSs always select the TCHHs.
Examples
Suppose that a cell has two TRXs and the cell is configured with one BCCH and two SDCCHs. According to the Erlang B table, when the traffic volume is X the number of channels required in the cell is 10. The number of channels that can be configured as TCHs in the cell is 13 (2 x 8 - 3). Because 13 > 10, all the channels in the cell can be configured as TCHFs. TCH Traffic Busy Threshold can be set to 100. The AMR TCH/H Prior Cell Load Threshold is set to 9. According to the Erlang B table, when the traffic volume in the cell is Y the number of channels required in the cell is 17 and the number of TCHs required is 13. Because 13 x 2 > 17 > 13, the number of TCHFs to be configured in the cell is 9 (2 x 13 - 17) and other channels should be configured as TCHHs. TCH Traffic Busy Threshold is set to 70 (100 x [2 x 13 - 17]/13) (AMR TCH/H Prior Cell Load Threshold must be smaller than TCH Traffic Busy Threshold). Based on ERLANG B, if the traffic volume in the cell is Z, the number of configured channels is 28 and the number of channels that can be used as TCHs in the cell is 13. Because 28 > 13 x 2, all the channels in the cell should be configured as TCHHs. At the same time, Huawei recommends that a user should perform an expansion. The TCH Traffic Busy Threshold is set to 0 and the AMR TCH/H Prior Cell Load Threshold is set to 0.
Issue 02 (2008-06-30)
12-17
NOTE
The method of configuring the full-rate and half-rate channels described previously is simple. The support capability of MSs for the full-rate and half-rate channels and the channel assignment strategies are not considered. In fact, the call loss rate in a cell is related to these factors. Therefore, Huawei recommends that the method described previously be used as a rough estimation method. You need adjust the settings of TCH Traffic Busy Threshold and AMR TCH/H Prior Cell Load Threshold based on the traffic volume.
12.5 Capabilities
BSC6000V900R008C01 supports up to 2048 TRXs that can provide half-rate services.
12.6 Implementation
This describes how to configure half-rate services, verify half-rate services, enable the function of reserving priority resources, adjust half-rate services, and disable half-rate services. 12.6.1 Suggestions for Configuring the Half-Rate Service This describes the suggestions for configuring the half-rate service, which can help improve the network performance. 12.6.2 Configuring the Half-Rate Service This describes how to configure the half-rate service on the BSC6000 Local Maintenance Terminal. 12.6.3 Verifying the Half-Rate Service The means for verifying the half-rate service differ, depending on the channel type configured for the TRX. 12.6.4 Enabling the Function of Reserving Priority Resources This describes how to enable the function of reserving priority resources on the BSC6000 Local Maintenance Terminal. 12.6.5 Disabling the Half-Rate Service This describes how to disable the half-rate service on the BSC6000 Local Maintenance Terminal.
12.6.1 Suggestions for Configuring the Half-Rate Service

This describes the suggestions for configuring the half-rate service, which can help improve the network performance.
Definitions of the Scenarios

The scenarios for applying the half-rate service are complex and are generally classified into two categories:
l
High-traffic scenarios Table 12-3 describes the scenarios classified by inter-BTS distance.
12-18
Issue 02 (2008-06-30)
Table 12-3 High-traffic scenarios Type Urban Network Feature Description Entire network of the capital or the metropolis. Such network features continuous coverage, abundant frequency resources, and mean distribution of traffic among the BTSs. Such network features discontinuous coverage and mean distribution of frequency resources and BTS locations. Remarks The average distance between the BTSs is within 800 meters and the traffic volume of the BSC is higher than 500 Erl. The average distance between the BTSs is between 800 and 1500 meters and the traffic volume of the BSC is higher than 300 Erl.
Suburb network
Low-traffic scenarios Table 12-4 describes the scenarios classified by function combination. Table 12-4 Low-traffic scenarios Type Scenario 1 Scenario 2 Scenario 3 Scenario 4 Feature Description Networking by concentric cells, AMR not enabled Networking by common cells (non-concentric cells), AMR not enabled Networking by concentric cells, AMR enabled Networking by common cells (non-concentric cells), AMR enabled
Configuration Principles
Table 12-5 describes the configuration principles in the urban network. Table 12-5 Configuration principles in the urban network Urban Network Configurable Parameters TCH Rate Modify Low-Traffic Scenarios Scenari o1 Yes Scenari o2 Yes Scenari o3 Yes Scenario 4 Yes Remarks
Issue 02 (2008-06-30)
12-19
Urban Network Configurable Parameters Enhanced TCH Adjust Allowed
Low-Traffic Scenarios Scenari o1 Yes Scenari o2 Yes Scenari o3 Yes Scenario 4 Yes
Remarks
Huawei recommends that you set this parameter to Yes for all the scenarios except for those have a high requirement on delay. The parameter is configured to keep a balance between the voice quality and the traffic capacity. Thus, you must take account of both voice quality and traffic capacity when configuring this parameter. You need to set a low value for this parameter if the overlaid subcell is severely congested. You need to set a low value for this parameter if the underlaid subcell is severely congested. Huawei recommends that you set this parameter to Yes if AMR is enabled.
TCH Traffic Busy Threshold
50%
60%
Busy Threshold of TCH Traffic in Overlaid Subcell
50%
60%
Tch Triffic Busy Underlay Threshold
50%
60%
AMR TCH/H Prior Allowed
No
No
Yes
Yes
12-20
Issue 02 (2008-06-30)
Urban Network Configurable Parameters AMR TCH/H Prior Cell Load Threshold
Low-Traffic Scenarios Scenari o1 Scenari o2 Scenari o3 40% Scenario 4 40%
Remarks
The AMR call has a higher antiinterference performance over the common call. A lower value should be set for this parameter than that for the TCH Traffic Busy Threshold. However, the parameters such as TCH Traffic Busy Threshold, Busy Threshold of TCH Traffic in Overlaid Subcell, and Tch Triffic Busy Underlay Threshold should also be taken into account.
Table 12-6 describes the configuration principles in the suburb network. Table 12-6 Configuration principles in the suburb network Suburb network Configurable Parameters TCH Rate Modify Enhanced TCH Adjust Allowed Low-Traffic Scenarios Scenari o1 Yes Yes Scenari o2 Yes Yes Scenari o3 Yes Yes Scenario 4 Yes Yes Huawei recommends that you set this parameter to Yes for all the scenarios except for those have a high requirement on delay. Remarks
Issue 02 (2008-06-30)
12-21
Suburb network Configurable Parameters TCH Traffic Busy Threshold
Low-Traffic Scenarios Scenari o1 Scenari o2 60% Scenari o3 Scenario 4 70%
Remarks
The suburb network can have a higher requirement on quality than the urban network. Thus, Huawei recommends that you set a higher value for this parameter. You need to set a low value for this parameter if the overlaid subcell is severely congested. The suburb network can have a higher requirement on quality than the urban network. Thus, Huawei recommends that you set a higher value for this parameter.
70%
70%
50%
50%
You need to set a low value for this parameter if the underlaid subcell is severely congested. The suburb network can have a higher requirement on quality than the urban network. Thus, Huawei recommends that you set a higher value for this parameter.
No
No
Yes
Yes
Huawei recommends that you set this parameter to Yes if AMR is enabled.
12-22
Issue 02 (2008-06-30)
Suburb network Configurable Parameters AMR TCH/H Prior Cell Load Threshold
Low-Traffic Scenarios Scenari o1 Scenari o2 Scenari o3 50% Scenario 4 50%
Remarks
The AMR call has a higher antiinterference performance over the common call. A lower value should be set for this parameter than that for the TCH Traffic Busy Threshold. However, the parameters such as TCH Traffic Busy Threshold, Busy Threshold of TCH Traffic in Overlaid Subcell, and Tch Triffic Busy Underlay Threshold should also be taken into account.
Table 12-7 describes the impact of adjusting parameters on the network. Table 12-7 Impact of adjusting parameters Configurable Parameters Impact of Parameter Adjustment TCH Congestion Rate (All Channels Busy) TCH Traffic Volume Voice Quality
TCH Rate Modify Enhanced TCH Adjust Allowed
Issue 02 (2008-06-30)
12-23
Configurable Parameters
Impact of Parameter Adjustment
TCH Congestion Rate (All Channels Busy) If the TCH Traffic Busy Threshold is increased and if the cell becomes congested after the halfrate service is enabled, the TCH Congestion Rate (All Channels Busy) increases. Note this symptom applies only to the cells experiencing congestion. If the TCH Traffic Busy Threshold is decreased and if the cell becomes congested after the halfrate service is enabled, the TCH Congestion Rate (All Channels Busy) decreases. Note this symptom applies only to the cells experiencing congestion.
TCH Traffic Volume
Voice Quality
TCH Traffic Busy Threshold
If the TCH Traffic Busy Threshold is decreased, the MSs can occupy the TCHHs more easily and thus more traffic volume is allowable. However, the traffic volume is halfrate TRXs dependent. If the TCH Traffic Busy Threshold is increased, the MSs can occupy the TCHFs more easily and a better voice quality is thus achieved. If the TCH Traffic Busy Threshold is set to 100%, the cell is allocated all TCHFs without TCHHs. If the TCH Traffic Busy Threshold is set to 0%, the TCHHs are allocated preferably. However, if the MS only supports full-rate, the system allocates the TCHF without affecting the call occupancy.
If the TCH Traffic Busy Threshold is increased and the traffic in the cell increases, the cell becomes congested and the TCH Traffic Volume decreases. If the TCH Traffic Busy Threshold is decreased and the traffic in the cell increases, the congestion in the cell becomes alleviated and the TCH Traffic Volume increases.
If the TCH Traffic Busy Threshold is increased, the proportion of the calls occupying the TCHFs increases and the voice quality is improved. If the TCH Traffic Busy Threshold is decreased, the proportion of the calls occupying the TCHHs increases and the voice quality is decreased.
12-24
Issue 02 (2008-06-30)
TCH Congestion Rate (All Channels Busy) The adjustment of the Busy Threshold of TCH Traffic in Overlaid Subcell has the similar impact on the TCH Congestion Rate (All Channels Busy) as that of the TCH Traffic Busy Threshold. The adjustment of this parameter applies to the overlaid subcell of the concentric cell.
TCH Traffic Volume
Voice Quality
The adjustment of the Busy Threshold of TCH Traffic in Overlaid Subcell has the similar effect as that of the TCH Traffic Busy Threshold The adjustment of this parameter applies to the overlaid subcell of the concentric cell.
The adjustment of the Busy Threshold of TCH Traffic in Overlaid Subcell has the similar impact on the TCH Traffic Volume as that of the TCH Traffic Busy Threshold. The adjustment of this parameter applies to the overlaid subcell of the concentric cell.
The adjustment of the Busy Threshold of TCH Traffic in Overlaid Subcell has the similar impact on the voice quality as that of the TCH Traffic Busy Threshold The adjustment of this parameter applies to the overlaid subcell of the concentric cell.
Issue 02 (2008-06-30)
12-25
TCH Congestion Rate (All Channels Busy) The adjustment of the Tch Triffic Busy Underlay Threshold has the similar impact on the TCH Congestion Rate (All Channels Busy) as that of the TCH Traffic Busy Threshold. The adjustment of this parameter applies to the underlaid subcell of the concentric cell.
TCH Traffic Volume
Voice Quality
The adjustment of the Tch Triffic Busy Underlay Threshold has the similar effect as that of the TCH Traffic Busy Threshold The adjustment of this parameter applies to the underlaid subcell of the concentric cell.
The adjustment of the Tch Triffic Busy Underlay Threshold has the similar impact on the TCH Traffic Volume as that of the TCH Traffic Busy Threshold. The adjustment of this parameter applies to the underlaid subcell of the concentric cell. -
The adjustment of the Tch Triffic Busy Underlay Threshold has the similar impact on the voice quality as that of the TCH Traffic Busy Threshold The adjustment of this parameter applies to the underlaid subcell of the concentric cell.
12-26
Issue 02 (2008-06-30)
TCH Congestion Rate (All Channels Busy) The adjustment of the AMR TCH/H Prior Cell Load Threshold has the similar impact on the TCH Congestion Rate (All Channels Busy) as that of the TCH Traffic Busy Threshold.
TCH Traffic Volume
Voice Quality
AMR TCH/H Prior Cell Load Threshold
The adjustment of the AMR TCH/H Prior Cell Load Threshold has the similar effect as that of the TCH Traffic Busy Threshold.
The adjustment of the AMR TCH/H Prior Cell Load Threshold has the similar impact on the TCH Traffic Volume as that of the TCH Traffic Busy Threshold.
The adjustment of the AMR TCH/H Prior Cell Load Threshold has the similar impact on the voice quality as that of the TCH Traffic Busy Threshold.
12.6.2 Configuring the Half-Rate Service

This describes how to configure the half-rate service on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. In the License control items of the BSC6000V900R008 Exceptional Commercial License Application Template, locate the Number of TRX supporting half-rate row and specify a value in the cell corresponding to the Resource number column. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Context
The number of half-rate TRXs carried on each E1 link over the Abis interface varies in different network configurations:
l
When BTS local switching and Flex Abis are not enabled in the network:
If the half-rate functionality is enabled in all the TRXs carried on the E1 link, a maximum of 13 TRXs can be carried on the E1 link. If the TRXs carried on the E1 link operate in hybrid mode, a maximum of 13-15 TRXs can be carried on the E1 link.
Issue 02 (2008-06-30)
l
When BTS local switching and Flex Abis are enabled in the network: The number of TRXs supported by the E1 link depends on the proportion of calls processed in BTS local switching mode. Generally, a maximum of 13-18 TRXs can be carried on the E1 link.
When the transmission-optimized BTS is used:
If the half-rate functionality is enabled in all the TRXs carried on the E1 link, a maximum of 20 TRXs can be carried on the E1 link. If the TRXs carried on the E1 link operate in hybrid mode, a maximum of 20-24 TRXs can be carried on the E1 link.
Procedure
Step 1 Configure the Speech Version for the half-rate service. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page. Then, select Configure Cell Attributes from the shortcut menu. In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 12-7.
12-28
Issue 02 (2008-06-30)
4.
Click Call Control. In the displayed dialog box, click Advanced. A dialog box is displayed, as shown in Figure 12-8. On the Access Control tab page, set Speech Version to Support Half-rate Version 1.
Issue 02 (2008-06-30)
12-29
5.

NOTE
The BSC supports three half-rate speech versions, namely Support Half-rate Version 1, Support Half-rate Version 2, and Support Half-rate Version 3. The parameter Support Half-rate Version 2 underSpeech Version is reserved.
Step 2 Set Channel Type of the TRX to TCH Half Rate.

NOTE
Adhere to the following principles when configuring the channel type:

l l
To configure a channel as a TCHH fixedly, set its Channel Type to TCH Half Rate. To configure a channel as a TCHF fixedly or as a dynamic channel, set its Channel Type to TCH Full Rate.
To enable the half-rate service of the TRX that is not configured with TCHHs, you must enable TCH Rate Adjust Allow.
To configure the Channel Type of a TRX to TCH Half Rate, do as follows: 1. 2. In the Assigned TRXs area shown in Figure 12-7, select a TRX to be adjusted and click TRX Config. In the displayed dialog box, select the Channel Attributes tab page, as shown in Figure 12-9. Select the channel number in the Channel No. area and select TCH Half Rate in the Channel Type drop-down list.
12-30
Issue 02 (2008-06-30)
Figure 12-9 Configure TRX Attributes dialog box
3.
Step 3 If the TRX does not have the channels whose Channel Type are set to TCH Half Rate except the TCH Full Rate channels, set the parameter TCH Rate Adjust Allow so that the TRX supports half-rate services.
NOTE
For a TRX whose TCH Rate Adjust Allow is not enabled, channels on the TRX are assigned preferably. Therefore, the channels on the TRXs that support the rate adjustment can be reserved for further use and the resources are thus used maximally.
1. 2.
In the Assigned TRXs area shown in Figure 12-7, select a TRX to be adjusted and click TRX Config. In the displayed dialog box, select the Device Attributes tab page, as shown in Figure 12-10. Set TCH Rate Adjust Allow to Yes.
Issue 02 (2008-06-30)
12-31
Figure 12-10 Device attributes
3.
----End
12.6.3 Verifying the Half-Rate Service

The means for verifying the half-rate service differ, depending on the channel type configured for the TRX.
Procedure
Step 1 The TRX is configured with TCHHs. 1. On the BSC6000 Local Maintenance Terminal, right-click a TRX on the Management Tree tab page. Select Monitor Channel Status from the shortcut menu. A dialog box is displayed, as shown in Figure 12-11.
12-32
Issue 02 (2008-06-30)
Figure 12-11 Monitor Channel Status(1) dialog box
2.
Click Start. If a channel shown in Figure 12-12 is found, you can infer that the TRX supports the half-rate service. Figure 12-12 Half-rate channel status
Step 2 The TRX is configured with only TCHFs. 1. 2. Use an MS that supports the half-rate service to lock a frequency in the cell where the TRX is located. On the BSC6000 Local Maintenance Terminal, right-click the TRX on the Management Tree tab page. Select Monitor Channel Status from the shortcut menu. A dialog box is displayed, as shown in Figure 12-11. Click Start and view the channel status. On the BSC6000 Local Maintenance Terminal, right-click the cell where the TRX is located on the Management Tree tab page. Then, select Modify Administrative State. A dialog box is displayed, as shown in Figure 12-13.
3. 4.
Issue 02 (2008-06-30)
12-33
Figure 12-13 Modifying administrative state
5. 6.
Block all the other TCHs in the cell where the TRX is located so that the speech service initiated by the MS only takes up the TCH carried on the TRX. As shown in Figure 12-14, click Channel Management. A dialog box is displayed.
12-34
Issue 02 (2008-06-30)
7.
In the displayed dialog box, click Advanced a dialog box is displayed, as shown in Figure 12-15.
Issue 02 (2008-06-30)
12-35
8. 9.
Select the HWII Channel Assignment and Radio Channel Control tab. On the tab page, set TCH Traffic Busy Threshold to 0. Click OK. The configuration of parameters is complete.
10. Initiate a new speech service in the cell. 11. View Figure 12-11 to check whether the latest occupied channel on the TRX is a TCHH. If the channel is a TCHH, you can infer that the TRX supports the half-rate service. ----End
12.6.4 Enabling the Function of Reserving Priority Resources

This describes how to enable the function of reserving priority resources on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. In the License control items of the BSC6000V900R008 Exceptional Commercial License Application Template, locate the Whether or not to activate the Channel Reserved function row and set its resource number to 1. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page. Then, select Configure Cell Attributes from the shortcut menu. Step 2 In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next.
Step 3 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 12-16. Figure 12-16 Set Cell Attributes dialog box
Step 4 Click Channel Management. A dialog box is displayed, as shown in Figure 12-17. Set Grade Access Allow to Yes, Highest Priority to 1, and Reserved Channel Number to 3.
Issue 02 (2008-06-30)
12-37
12.6.5 Disabling the Half-Rate Service

This describes how to disable the half-rate service on the BSC6000 Local Maintenance Terminal.
Prerequisite
If the half-rate service is not required in the whole office, a license that does not provide the half-rate service should be applied for the office. For details on activating the license, refer to Activating the BSC License.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target TRX and then select Configure TRX Attributes from the shortcut menu. Step 2 In the TRX view list box, select the TRX whose attributes are to be modified. Then, click Set TRX Attributes. A dialog box is displayed, as shown in Figure 12-18.
1. 2.
On the Channel Attributes tab page, select the channel in the Channel No. area whose Channel Type is TCH Half Rate and then set its channel type to TCH Full Rate. On the Device Attributes set TCH Rate Adjust Allow to No.

This lists the counters related to the half-rate service.
Alarms
None
Counters
Table 12-8 lists the counters related to the half-rate service. Table 12-8 Counters related to the half-rate service Counter H3023A Description Failed Internal Intra-Cell Handovers (Dynamic Conversion, TCHF-TCHH)
Issue 02 (2008-06-30)
Counter H3023B H3003A H3003B H3013A
Description Failed Internal Intra-Cell Handovers (Dynamic Conversion, TCHH-TCHF) Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHF-TCHH) Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHH-TCHF) Internal Intra-Cell Handover Commands (Dynamic Conversion, TCHF-TCHH) Internal Intra-Cell Handover Commands (Dynamic Conversion, TCHH-TCHF) Success Rate of Internal Intra-Cell Handover (Dynamic Conversion, TCHF-TCHH) Success Rate of Internal Intra-Cell Handover (Dynamic Conversion, TCHH-TCHF) Successful Internal Intra-Cell Handovers (Dynamic Conversion, TCHF-TCHH) Successful Internal Intra-Cell Handovers (Dynamic Conversion, TCHH-TCHF) Channel Conversion Requests (TCHFTCHH) Successful Channel Conversions (TCHH-TCHF) Channel Conversion Requests (TCHHTCHF) Successful Channel Conversions (TCHH-TCHF) Number of Successful Channel Conversions (PDCH to TCHH) Number of Successful Channel Conversions (TCHH to PDCH)
H3013B
TH3033A
TH3033B
CH3033A
CH3033B
R3505A R3525A R3505B R3525B R3529A R3522A
12-40
Issue 02 (2008-06-30)
12.8 References
None
Issue 02 (2008-06-30)
12-41
13 Automatic Level Control
13
About This Chapter
Automatic Level Control
13.1 Overview This describes the Automatic Level Control (ALC), which keeps the voice level of the entire network in a predefined state and avoids the volume fluctuation of two parties during a call. 13.2 Availability This lists the NEs and software required for the implementation of automatic level control. 13.3 Technical Description This describes the three modes associated with ALC, namely, pass mode, fixed mode, and auto mode. 13.4 Capabilities This describes the capabilities of ALC in different modes. 13.5 Implementation This describes how to configure ALC. 13.6 Maintenance Information None. 13.7 References
Issue 02 (2008-06-30)
13-1
13.1 Overview
This describes the Automatic Level Control (ALC), which keeps the voice level of the entire network in a predefined state and avoids the volume fluctuation of two parties during a call.
Definition
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.
Purposes
The fluctuation of voice signal levels in the communication system, which is caused by the changes of terminals and transmission lines, affects the call quality. Surveys indicate that if the voice signal level can be kept in a suitable range, the average call duration in the communication system will be longer. This brings higher revenues for the operators. The ALC function of the BSC is embedded in the DSP of the GDPUX/GDPUC and the calculation load is thus reduced. This implementation prevents the distortion of voice when the voice signal level is automatically adjusted.
NOTE
If the voice volume in the network is stable, Huawei recommends using the default configurations for the ALC.
Terms
Terms ALC RVS Gain ALC VAD Threshold ALC Mode ALC Level Expect ALC FWD Gain ALC Rate Adjust Definition 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 Three gain modes of the ALC are available: pass, fixed, and auto The expected level values of the uplink voice signal level in the auto gain mode The gain values of the downlink voice signal level in the fixed gain mode The gain adjust rate of the uplink voice signal level in the fixed gain mode
13-2
Issue 02 (2008-06-30)

Acronyms and Abbreviations ALC Full Spelling Automatic Level Control
13.2 Availability
This lists the NEs and software required for the implementation of automatic level control.
NEs Involved
Table 13-1 lists the NEs related to ALC. Table 13-1 NEs related to ALC MS NOTE
BTS -
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 13-2 lists the versions of GBSS products that support ALC. Table 13-2 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
None.

This describes the three modes associated with ALC, namely, pass mode, fixed mode, and auto mode.
l
Pass mode
Issue 02 (2008-06-30)
When the ALC Mode is set to Pass, the uplink and downlink voice data is input into the pass module. The ALC does not make any adjustment for the data. The output of data does not change.
l
Fixed mode When the ALC Mode is set to Fixed, the uplink and downlink voice data is input into the fixed gain module. The ALC enlarges or reduces the range of voice signal level according to the preset ALC FWD Gain and ALC RVS Gain.
Auto mode When the ALC Mode is set to Auto, the downlink voice data is input into the fixed gain module, while the uplink voice data is input into the auto gain module.
Based on the configuration, process the uplink and downlink voice according to one of the previous three modes to realize the gain control over voice data flow.
CAUTION
l
The auto gain mode is valid for the uplink voice. The downlink voice is processed according to the fixed gain mode. ALC FWD Gain is corresponded to the downlink fixed gain, while the ALC RVS Gain is corresponded to the uplink fixed gain.
13.4 Capabilities
This describes the capabilities of ALC in different modes. The capabilities of ALC are listed as follows:
l
In the pass mode, the ranges of the uplink and the downlink voice keep the same as the original range. In the fixed mode, the ranges of the uplink and downlink voice can be adjusted to 1/44 times of the original range. In the auto mode, the range of the downlink voice can be adjusted to 1/44 times of the original range, while the range of the uplink voice can be adjusted from 30 dB to 10 dB.
13.5 Implementation
This describes how to configure ALC. 13.5.1 Configuring ALC This describes how to configure ALC on the BSC6000 Local Maintenance Terminal.
13.5.1 Configuring ALC

This describes how to configure ALC on the BSC6000 Local Maintenance Terminal.
13-4
Issue 02 (2008-06-30)
Procedure
l Configure the Fixed mode. 1. On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click a GDPUC or a GDPUX and choose Configure Board Attributes from the shortcut menu. In the displayed dialog box, set Load Key, and then click Next. In the displayed dialog box, select Configure All and set ALC Mode to Fixed, as shown in Figure 13-1. Keep the defaulted value 6 for ALC FWD Gain and ALC RVS Gain. You can raise the voice by setting the value to 12 or reduce the value by setting the value to 0 with integer numbers. Figure 13-1 Configuring the ALC switch
2. 3.
Configure the Auto mode. In Figure 13-1, select Configure All, and set the ALC Mode to Auto.
NOTE
Keep the defaulted value 6 for ALC FWD Gain. You can raise the voice by setting the value to 12 or reduce the value by setting the value to 0 with integer numbers. Keep the defaulted value 10, 50, and 10 for the three parameters ALC Rate Adjust, ALC Level Expect, and ALC VAD Threshold respectively.
Configure the Pass mode. In Figure 13-1, select Configure All, and set the ALC Mode to Pass.
NOTE
No parameters in the pass mode need to be adjusted.
----End
Postrequisite
Feel the volume changes before and after the ALC configuration.

None.
Alarms
None.
Counters
None.
13.7 References
ITU-T Recommendation G.169, Automatic Level Control Devices, 1999/06
13-6
Issue 02 (2008-06-30)
14 Acoustic Echo Cancellation
14
About This Chapter
Acoustic Echo Cancellation
14.1 Overview This describes Acoustic Echo Cancellation (AEC). AEC is used to reduce or remove the acoustic echo reflected from the MS. 14.2 Availability This lists the NEs and software required for the implementation of AEC. 14.3 Technical Description This describes the technical aspects of AEC, which eliminates the uplink acoustic echoes based on the voice signal features. 14.4 Implementation This describes how to configure the AEC feature. 14.5 Maintenance Information None. 14.6 References
Issue 02 (2008-06-30)
14-1
14.1 Overview
This describes Acoustic Echo Cancellation (AEC). AEC is used to reduce or remove the acoustic echo reflected from the MS.
Definition
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. Due to the delay of the wireless communication system, the acoustic echo is generated. The acoustic echo exists only in the uplink speech.
Purposes
The AEC feature of the BSC is implemented by the DSP of the GDPUX/GDPUC. The DSP of the GDPUX/GDPUC analyzes the uplink and downlink digital voice signals, searches the acoustic echoes in the uplink voice, and suppresses the acoustic echoes.
Terms
Terms AEC back wastage AEC pure delay Definition Return loss in the BSCBTSMSBTSBSC acoustic echo loop Duration of the BSCBTSMSBTSBSC voice loop

Acronyms and Abbreviations AEC Full Spelling Acoustic Echo Cancellation
14.2 Availability
This lists the NEs and software required for the implementation of AEC.
NEs Involved
Table 14-1 lists the NEs related to AEC.
Table 14-1 NEs related to AEC MS NOTE

BTS -
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 14-2 lists the versions of GBSS products that support AEC. Table 14-2 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases

This describes the technical aspects of AEC, which eliminates the uplink acoustic echoes based on the voice signal features. The processing procedure of AEC is as follows: 1. 2. The AEC checks the downlink voice signals and stores the features of the downlink voice signals. The AEC searches the stored features of the downlink voice signals based on the parameter AEC Pure Delay. The AEC compares the features of the downlink voice signals with the features of the uplink voice signals to determine whether acoustic echoes are in the uplink voice signals.
l
If acoustic echoes do not exist in the uplink voice signals or the acoustic echoes are much weaker than the normal voice signals, the AEC does not process the uplink voice signals. If acoustic echoes exist in the uplink voice signals, see 3.
3.
The AEC further analyzes the uplink voice signals based on the parameter AEC Back Wastage. If downlink acoustic echoes exist in the uplink voice signals or there is no uplink voice signal, the AEC gradually attenuates the acoustic echoes.
Issue 02 (2008-06-30)
14-3
CAUTION
l
The echo generated in the call from an MS to a fixed phone is an electric echo; the echo generated in the call from one MS to another MS is an acoustic echo. The AEC feature may cause discontinuous voice during a call when the two parties speak at the same time. If there is no obvious acoustic echo in the network, you are advised to disable the feature.
14.4 Implementation
This describes how to configure the AEC feature. 14.4.1 Configuring Acoustic Echo Cancellation This describes how to configure AEC on the BSC6000 Local Maintenance Terminal.
14.4.1 Configuring Acoustic Echo Cancellation

This describes how to configure AEC on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click a GDPUC or a GDPUX and select Configure Board Attributes from the shortcut menu. Step 2 In the displayed dialog box, set Load Key, and then click Next. Step 3 In the displayed dialog box, select Configure All and set AEC switch to Open, as shown in Figure 14-1. Adopt the defaulted values for other parameters. Figure 14-1 Configuring the AEC switch
14-4
Issue 02 (2008-06-30)

NOTE
In HDLC networking mode, if Speech Version is set to Support Full-rate Version 1, then you are advised to set AEC Pure Delay to141 in order to further reduce the downlink flow.
Step 4 Click Finish. The AEC is configured. ----End
Postrequisite
Check whether the acoustic echo is eliminated and whether the call is normal.

None.
Alarms
None.
Counters
None.
14.6 References
None.
Issue 02 (2008-06-30)
14-5
15 Cell Broadcast
15
About This Chapter
Cell Broadcast
15.1 Overview This describes cell broadcast. Cell broadcast refers to the broadcast of messages in a specified area, such as one or several cells, or even the entire PLMN. 15.2 Availability This lists the NEs, software, and other conditions required for the implementation of cell broadcast. 15.3 Technical Description This describes the technical aspects of cell broadcast. As a service provided by the GSM network, the cell broadcast system consists of the CBC, BSC, BTS, and MS. It receives and stores short messages, schedules and sends short messages, responds to the query from the CBC, and controls the BTS flow. Simplified cell broadcast provides simplified cell broadcast services without the CBC system. 15.4 Implementation This describes how to configure cell broadcast and simplified cell broadcast. 15.5 Maintenance Information This lists the alarms and counters related to cell broadcast. 15.6 References
Issue 02 (2008-06-30)
15-1
15 Cell Broadcast
15.1 Overview
This describes cell broadcast. Cell broadcast refers to the broadcast of messages in a specified area, such as one or several cells, or even the entire PLMN.
Definition
As a special service provided by the GSM network, cell broadcast enables downlink messages to be sent on the CBCH to a specified coverage area of the radio network. All the MSs in the area can receive the messages and the cell broadcast does not require responses. Simplified cell broadcast provides the simplified cell broadcast services without the CBC system. The broadcast information includes the cell name, weather forecast, and social commonweal information.
Purposes
Through cell broadcast, the mobile network operators can provide special services for users. Compared with the point-to-point short message service, the cell broadcast service provides an effective and economical method to send messages to a large number of MSs in a specified area.
Terms
None.

Acronyms and Abbreviations CBC CBS Full Spelling Cell Broadcast Center Cell Broadcast System
15.2 Availability
This lists the NEs, software, and other conditions required for the implementation of cell broadcast.
NEs Involved
Table 15-1 lists the NEs involved in cell broadcast. Table 15-1 NEs involved in cell broadcast MS
15-2
BTS
BSC
CBC
MGW -
SGSN -
GGSN -
HLR -
Issue 02 (2008-06-30)
15 Cell Broadcast
MS
NOTE
BTS
BSC
CBC
MGW
SGSN
GGSN
HLR
Table 15-2 lists the NEs involved in simplified cell broadcast. Table 15-2 NEs involved in cell broadcast MS
NOTE
BTS
BSC
CBC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 15-3 lists the versions of GBSS product that support cell broadcast and simplified cell broadcast. Table 15-3 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Issue 02 (2008-06-30)
15-3
15 Cell Broadcast
Miscellaneous
To enable cell broadcast, you must install the hardware and software of the Cell Broadcast Center (CBC) and install the corresponding networking equipment.

This describes the technical aspects of cell broadcast. As a service provided by the GSM network, the cell broadcast system consists of the CBC, BSC, BTS, and MS. It receives and stores short messages, schedules and sends short messages, responds to the query from the CBC, and controls the BTS flow. Simplified cell broadcast provides simplified cell broadcast services without the CBC system. 15.3.1 Cell Broadcast System This describes the cell broadcast system. The cell broadcast system consists of the CBC, BSC, BTS, and MS. and provides functions such as message storage and maintenance/data configuration of the entire cell broadcast system. 15.3.2 Simplified Cell Broadcast System This describes the simplified cell broadcast system. The simplified cell broadcast provides simplified cell broadcast services without the CBC system. The broadcast information includes the cell name, weather forecast, and social commonweal information.
15.3.1 Cell Broadcast System

This describes the cell broadcast system. The cell broadcast system consists of the CBC, BSC, BTS, and MS. and provides functions such as message storage and maintenance/data configuration of the entire cell broadcast system.
Structure of the Cell Broadcast System

Figure 15-1 shows the structure of the cell broadcast system. Figure 15-1 Structure of the Cell Broadcast System
BTS
CBC
BSC
MS
BTS
In the cell broadcast system, the CBC communicates with the BSC through the standard TCP/ IP-based Ethernet interface.
15 Cell Broadcast
Functions of the Cell Broadcast System

The functions of the cell broadcast system are as follows:
l l l l
Receiving and Storing Short Messages Scheduling and Sending Short Messages Responding to CBC Queries Controlling the BTS Flow
Receiving and Storing Short Messages

The cell broadcast processing module on the GXPUM receives and stores the cell broadcast short messages from the CBC. The following are three types of commands for the cell broadcast processing module to process the received broadcast messages:
l
Receive the new broadcast short message When receiving this command, the cell broadcast processing module adds the new message into the broadcast short message database.
Delete the old short message or the short message that is already broadcast. When receiving this command, the cell broadcast processing module deletes the message from the broadcast short message database.
Replace the old broadcast short message with the new broadcast short message When receiving this command, the cell broadcast processing module deletes the old message from the broadcast short message database and then adds the new message into the database. If deleting the old message fails, the new message cannot be added.
Scheduling and Sending Short Messages

The cell broadcast processing module must meet the requirement for sending each cell broadcast short message, and sends the short message to a specified area. If multiple cell broadcast short messages need to be sent in a cell, the cell broadcast processing module calculates the sequence for sending the cell broadcast short messages in the cell based on its message scheduling algorithm. Then, the cell broadcast processing module sends these cell broadcast short messages to the BTS in strict order.
Responding to CBC Queries

When storing and sending a broadcast short message, the cell broadcast processing module records the following information:
l l l
Completion of sending a cell broadcast short message Number of broadcast short messages sent from each cell Status of the broadcast channel in each cell
Based on the requirements of the BSS and operators, the CBC queries and monitors the cell broadcast system, and then adjusts and optimizes the BSS to ensure the proper operation of the BSS. When a cell fails, the BSC reports the fault to the CBC. The CBC suspends the broadcast of the short messages in the cell.
15 Cell Broadcast
NOTE
In the process of cell broadcast, the cell broadcast processing module determines whether the cell is faulty based on only the CBCH status. When the CBCH fails, the cell broadcast processing module regards the cell as faulty.
Controlling the BTS Flow

The cell broadcast processing module schedules the sequence of sending the cell broadcast short messages. The BTS sends the cell broadcast short messages. Each TRX of the BTS maintains one message buffer and periodically sends the cell broadcast short message on a specified channel. When the cell broadcast processing module is not synchronous with the transmission of the cell broadcast short messages by the BTS, the BTS reports the out-of-sync to the BSC through a LOAD IND message. There are two situations:
l
If a TRX does not have sufficient time to transmit the excessive cell broadcast short messages, the cell broadcast processing module requests the TRX to suspend the transmission. If a TRX receives few cell broadcast shorting messages, the cell broadcast processing module requests the TRX to transmit some cell broadcast short messages immediately.
By controlling the flow of the cell broadcast short messages from the BTS, the cell broadcast processing module can balance the cell broadcast system and meet the requirements for transmitting the cell broadcast short messages.
15.3.2 Simplified Cell Broadcast System

This describes the simplified cell broadcast system. The simplified cell broadcast provides simplified cell broadcast services without the CBC system. The broadcast information includes the cell name, weather forecast, and social commonweal information.
Structure of the Simplified Cell Broadcast System

Figure 15-2 shows the structure of the simplified cell broadcast system. Figure 15-2 Structure of the simplified cell broadcast system
M2000
BTS
BSC
MS
LMT
BTS
Functions of the Simplified Cell Broadcast System

The functions of the simplified cell broadcast system are as follows:

l l l
15 Cell Broadcast
Broadcasting the cell name (or any character string) Sending a specified message in a specified period Suspending the ongoing transmission of the cell broadcast message
As shown in Figure 15-2, the parameters for simplified cell broadcast and the cell name to be broadcast can be configured on the BSC6000 Local Maintenance Terminal. The cell broadcast messages are transmitted through the MML commands of the M2000. In the BSC, the GBAM/ GOMU forwards the commands of the M2000 and the simplified cell broadcast data configured on the BSC6000 Local Maintenance Terminal to the GXPUM. The GXPUM then sends the cell broadcast messages to the BTS.
CAUTION
l
The simplified cell broadcast cannot be used with the cell broadcast provided by the CBC. They are mutually exclusive. The simplified cell broadcast provides only simple cell broadcast functions. For the message with frequently changed contents, the standard CBC system is required.
15.4 Implementation
This describes how to configure cell broadcast and simplified cell broadcast. 15.4.1 Configuring Cell Broadcast This describes how to configure cell broadcast on the BSC6000 Local Maintenance Terminal with the cooperation of the GBAM and the CBC operating system. 15.4.2 Configuring Simplified Cell Broadcast This describes how to configure simplified cell broadcast on the BSC6000 Local Maintenance Terminal and add simplified broadcast messages to a cell through the MML client.
15.4.1 Configuring Cell Broadcast

This describes how to configure cell broadcast on the BSC6000 Local Maintenance Terminal with the cooperation of the GBAM and the CBC operating system.
Procedure
Step 1 Configure the GXPUM. 1. On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click slot 8 in the GMPS. In the displayed dialog box, select Add Board. A dialog box is displayed, as shown in Figure 15-3.
Issue 02 (2008-06-30)
15-7
15 Cell Broadcast
Figure 15-3 Adding GXPUMs
2. 3. 4.
Select GXPUM, and then click Finish. Right-click the GXPUM and choose Configure Board Attributes from the shortcut menu. Set Load Key in the dialog box that is displayed. Click Next. A dialog box is displayed, as shown in Figure 15-4.
Figure 15-4 Configuring GXPUM attributes (1)
5.
Select the corresponding port, and then click Next. A dialog box is displayed, as shown in Figure 15-5.
15-8
15 Cell Broadcast
6.
Set the parameters of the GXPUM port as required.

NOTE
For details about the parameters of the GXPUT attributes, refer to GXPUM port attributes.
Step 2 Configure BSC attributes. 1. 2. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and choose Configure BSC Attributes from the shortcut menu. On the Basic Data tab page, select Support Cell Broadcast, and then set it to support standard cell broadcast, as shown in Figure 15-6.
Issue 02 (2008-06-30)
15-9
15 Cell Broadcast
Figure 15-6 Configuring cell broadcast attributes
3.
Set CBC IP, CB Interface IP, BSC Gateway, and CB Interface Port.
NOTE
CB Interface IP is the IP Address of External Network set in the GXPUM attribute settings.
Step 3 Configure TRX attributes. 1. On the BSC6000 Local Maintenance Terminal, right-click a TRX on the Management Tree tab page. Choose Configure TRX Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 15-7.
15-10
Issue 02 (2008-06-30)
15 Cell Broadcast
Figure 15-7 TRX attribute configuration wizard
2.
Select a TRX, click Configure TRX Attributes and then click the Channel Attributes tab on the dialog box that is displayed. Select a corresponding channel number on the tab page. Then, change the main BCCH to BCCH+CBCH, or change SDCCH8 to SDCCH +CBCH, as shown in Figure 15-8.
Issue 02 (2008-06-30)
15-11
15 Cell Broadcast
Figure 15-8 Configuring TRX attributes
Step 4 Configure the route of the CBC server. 1. 2. Log in to the CBC operating system as the system administrator. Specify the IP address of the CBC.
NOTE
The IP address of the CBC must be identical with the IP address that is set in the Configure BSC Attributes dialog box.
l l
If the CBC and the server are on the same network segment, the following operations are not required. If the CBC and the server are not on the same network segment, the following operations must be performed.
3. 4. 5.
Choose Start > Run. The Run text box is displayed. Enter the cmd command. The cmd.exe screen is displayed. Enter the route information. Enter the command route add xxx.xxx.xxx.xxx mask 255.255.255.255 yyy.yyy.yyy.yyy. xxx.xxx.xxx.xxx indicates the external IP address of the cell broadcast service; yyy.yyy.yyy.yyy indicates the IP address of the router.
NOTE
The external IP address of the cell broadcast service must be identical with the IP Address of External Network set in Configure the GXPUM.
6.
After the setting is complete, enter the ping xxx.xxx.xxx.xxx command to check whether the communication between the CBC and the BSC is normal. If the communication is normal, the setting succeeds.
15-12
15 Cell Broadcast
xxx.xxx.xxx.xxx indicates the external IP address of the cell broadcast service.

NOTE
The ping command is run to check whether the communications of the CBC is normal. The service checking of the CBC is not involved.
----End
15.4.2 Configuring Simplified Cell Broadcast

This describes how to configure simplified cell broadcast on the BSC6000 Local Maintenance Terminal and add simplified broadcast messages to a cell through the MML client.
Procedure
Step 1 Configure the GXPUM. 1. On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click slot 8 in the GMPS. In the displayed dialog box, select Add Board. A dialog box is displayed, as shown in Figure 15-9.
Figure 15-9 Adding GXPUMs
2. 3. 4.
Select GXPUM, and then click Finish. Right-click the GXPUM and choose Configure Board Attributes from the shortcut menu. Set Load Key in the dialog box that is displayed. Click Next. A dialog box is displayed, as shown in Figure 15-10.
Issue 02 (2008-06-30)
15-13
15 Cell Broadcast
5.
Select the corresponding port, and then click Next. A dialog box is displayed, as shown in Figure 15-11.
6.
Set the parameters of the GXPUM port as required.

NOTE
For details about the parameters of the GXPUT attributes, refer to GXPUM port attributes.
Step 2 Configure BSC attributes.

15 Cell Broadcast
1. 2.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and choose Configure BSC Attributes from the shortcut menu. On the Basic Data tab page, select Support Cell Broadcast, and then set it to Support Simple Cell Broadcast, as shown in Figure 15-12.
Figure 15-12 Configuring simple cell broadcast attributes
Step 3 Configure TRX attributes. 1. On the BSC6000 Local Maintenance Terminal, right-click a TRX on the Management Tree tab page. Choose Configure TRX Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 15-13.
Issue 02 (2008-06-30)
15-15
15 Cell Broadcast
Figure 15-13 TRX attribute configuration wizard
2.
Select a TRX, click Configure TRX Attributes and then click the Channel Attributes tab on the dialog box that is displayed. Select a corresponding channel number on the tab page. Then, change the main BCCH to BCCH+CBCH, or change SDCCH8 to SDCCH +CBCH, as shown in Figure 15-14.
15-16
Issue 02 (2008-06-30)
15 Cell Broadcast
Step 4 Configuring simple cell broadcast names 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page. Then, choose Configure Cell Attributes. Double-click the target cell in the Cell view list box to add it to the Selected cells list box. Click Next. In the displayed dialog box, select the target cell from the Cells to be set list box, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 15-15.
Issue 02 (2008-06-30)
15-17
15 Cell Broadcast
4.
Click Other Attributes. In the displayed dialog box, click Advanced. On the SBC Parameters tab page, set Support Cell Broadcast Name to Yes, as shown in Figure 15-16.
15-18
Issue 02 (2008-06-30)
15 Cell Broadcast
Figure 15-16 Setting other parameters
Step 5 Add simplified cell broadcast messages to a cell through the operation Add Cell Broadcast Short Message Service(ADD SMSCB) on the Local Maintenance Terminal.
NOTE
You can query the simplified cell broadcast messages through the operation List Cell Broadcast Status (LST SMSCB).
----End

This lists the alarms and counters related to cell broadcast.
Alarms
Alarm ID 102 Alarm Name Disrupted Connection with the CBC
Counters
Counter AL0484 L0457 L0458 L0459
Issue 02 (2008-06-30)
Description Mean Capacity of BSC Message Library WRITE-REPLACE Requests Received by BSC KILL Requests Received by BSC STATUS-CBCH-QUERY Requests Received by BSC
15 Cell Broadcast
Counter L0460 L0461 L0462 L0463 L0464 L0465 L0466 L0467 L0468 L0469 L0470 L0471 L0472 L0473 L0474 L0475 L0476 L0477 L0478 L0479 L0481 L0482 L0483
Description STATUS-MESSAGE-QUERY Requests Received by BSC SET-DRX Requests Received by BSC RESET Requests Received by BSC REPORT Responses to WRITE-REPLACE Requests REJECT Responses to WRITE-REPLACE Requests REPORT Responses to KILL Requests REJECT Responses to KILL Requests REPORT Responses to STATUS-CBCH-QUERY Requests REJECT Responses to STATUS-CBCH-QUERY Requests REPORT Responses to STATUS-MESSAGE-QUERY Requests REJECT Responses to STATUS-MESSAGE-QUERY Requests REPORT Responses to SET-DRX Requests REJECT Responses to SET-DRX Requests RESTART-INDICATION Requests Sent from BSC REJECT Responses to RESTART-INDICATION Requests FAILURE-INDICATION Requests Sent from BSC CBCH Loading Indications Received by BSC (Overflow) CBCH Loading Indications Received by BSC (Underflow) WRITE-REPLACE Requests (WRITE Requests) Received by BSC REPORT Responses to WRITE-REPLACE Requests (WRITE Requests) WRITE-REPLACE Requests (REPLACE Requests) Received by BSC REPORT Responses to WRITE-REPLACE Requests (REPLACE Requests) REJECT Responses to WRITE-REPLACE Requests (REPLACE Requests)
15-20
Issue 02 (2008-06-30)
15 Cell Broadcast
Counter L0486
Description Disruptions of the BSC-CBC Connection
15.6 References
l
GSM 03.41 V5.9.1:"Digital cellular telecommunications system (Phase 2+); Channel coding" GSM 03.49 V7.0.0:"Digital cellular telecommunications system (Phase 2+); Link Adaptation"
Issue 02 (2008-06-30)
15-21
16 Ciphering
16
About This Chapter
Ciphering
16.1 Overview This describes the ciphering mechanism, which guarantees the communications security on the Um interface of the GSM system. 16.2 Availability This lists the NEs and software required for the implementation of ciphering. 16.3 Impact This describes the impact of ciphering on system performance. 16.4 Technical Description This describes how the user information is secured with the ciphering of signaling, voice, and data on the Um interface. 16.5 Capabilities This describes the ciphering algorithms supported at present. 16.6 Implementation This describes how to configure, reconfigure, and disable ciphering. 16.7 Maintenance Information This lists the alarms and counters related to ciphering. 16.8 References
Issue 02 (2008-06-30)
16-1
16 Ciphering
16.1 Overview
This describes the ciphering mechanism, which guarantees the communications security on the Um interface of the GSM system.
Definition
The GSM specifications define eight 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.
The ciphering setting procedure is initiated on the network side. The capabilities of the MS and BTS must be taken into account for the selection of appropriate ciphering algorithms. The MS and BTS cipher and decipher information by using the ciphering algorithms. Thus, the information transmitted on the Um interface is secured.
Purposes
As an important feature in the GSM, ciphering improves the security of information exchanged between the MS and the BTS. The information ciphered on the Um interface involves signaling, speech, and data. The implementation of ciphering guarantees the information security and prevents user information from unauthorized access.
Terms
Terms Kc Ki Definition 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. 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. Ciphering algorithms defined by GSM specifications.
A5
16-2
Issue 02 (2008-06-30)
16 Ciphering

Acronyms and Abbreviations TMSI IMSI RRM Full Spelling Temporary Mobile Subscriber Identifier International Mobile Station Identity Radio Resource Management
16.2 Availability
This lists the NEs and software required for the implementation of ciphering.
NEs Involved
Table 16-1 describes the NEs involved in ciphering. Table 16-1 NEs involved in ciphering MS
NOTE
BTS
BSC
MSC/ VLR
AUC
SGSN
GGSN
HLR
Software Releases
Huawei BSS3.1 and all later versions support A5/1 and A5/2 ciphering algorithms. BSS7.0 and double-transceiver BTSs support A5/1, A5/2, and A5/3 ciphering algorithms. All the products comply with the GSM standards specified by the ETSI and China. Table 16-2 lists the versions of GBSS products that support ciphering. Table 16-2 GBSS products and software versions Version Product BSC BTS BSC6000 BTS301 2 DTRU A5/1 Ciphering Algorithm A5/2 Ciphering A5/3 Ciphering Algorithm Algorithm
V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R00 1C07 and later releases
16-3
Issue 02 (2008-06-30)
16 Ciphering
Version Product QTRU BTS301 2AE DTRU A5/1 Ciphering Algorithm A5/2 Ciphering A5/3 Ciphering Algorithm Algorithm
BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R00 1C07 and later releases
QTRU BTS3006C
BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R00 1C07 and later releases BTS3000V100R00 1C07 and later releases
BTS3002E
BTS3900 GSM BTS3900A GSM DBS3900 GSM BTS3001C
BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C01 and later releases G3BTS34.30000. 81.0301 and later releases G3BTS36.30000. 01.0820A and later releases G3BTS32.30000. 00.1130 and later releases G3BTS32.30000. 00.1130 and later releases G3BTS32.30000. 00.1130 and later releases G3BTS34.30000 .03.0301A and later releases G3BTS36.30000 .02.0820 and later releases G3BTS32.30004 .01.1130 and later releases G3BTS32.30004 .01.1130 and later releases G3BTS32.30004 .01.1130 and later releases Not supported at present Not supported at present Not supported at present Not supported at present Not supported at present BTS3000V100R00 1C07 and later releases
BTS3002C
BTS30
BTS312
BTS3006A
BTS3012A
G3BTS32V302R002C06 and later releases
Miscellaneous
A telecom operator cannot use the A5 ciphering algorithm until the telecom operator applies for and is granted with authorization of the 3GPP Organizational Partners.
16 Ciphering
As the A5/2 ciphering algorithm is deciphered at present, the 3GPP Organizational Partners allow all countries to apply for A5/1 or A5/3 algorithm. A telecom operator should use A5/1 or A5/3 ciphering algorithm. The A5/3 ciphering algorithm is preferred in terms of security.
16.3 Impact
This describes the impact of ciphering on system performance.

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

None.

This describes how the user information is secured with the ciphering of signaling, voice, and data on the Um interface. 16.4.1 Kc and Its Generation This describes the application and generation of the ciphering key (Kc). 16.4.2 A5 Ciphering Algorithm This describes the application of the A5 ciphering algorithm, which is used to generate a pseudorandom sequence. 16.4.3 Selection of Ciphering Algorithms This describes the selection of the ciphering algorithms with the capabilities of the network and MS taken into account. 16.4.4 Signaling Ciphering Procedure This describes the initialization of the signaling procedure for ciphering. The signaling 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.
16.4.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/deciphering of user data. An MS is allocated with an IMSI and Ki once it is registered in the GSM network. The MS and the network use the same Ki and RAND, which are generated by the network and sent to the MS. Then, the ciphering Kc is generated with the A8 algorithm. Figure 16-1 shows the generation of the Kc.
16 Ciphering
Figure 16-1 Generation of Kc

The network side MS AUC Random number
Ki
Ki
A8 algorithm
A8 algorithm
store the cipher key
store the cipher key
16.4.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 serial number or a 114-bit deciphering serial number 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 on the basis of the A5 ciphering algorithm and the Exclusive OR operation of the information bit in the ciphered or deciphered data. The network uses the same ciphering serial number in the uplink and downlink. For each burst, one sequence is used for the MS ciphering and BTS deciphering while the other sequence is used for the BTS ciphering and MS deciphering. The ciphering/deciphering on the radio links is performed by the BTS and MS. Figure 16-2 shows the ciphering/deciphering process.
16-6
Issue 02 (2008-06-30)
16 Ciphering
Figure 16-2 Ciphering/deciphering flow

Sender Kc Frame number (TDMA) Kc Receiver Frame number (TDMA)
A5 algorithm Encryption serial number
A5 algorithm Decryption serial number
Modulo 2 minus 1
Modulo 2 plus 1
Data that is not encrypted
Data that is not encrypted
16.4.3 Selection of Ciphering Algorithms

This describes the selection of the ciphering algorithms with the capabilities of the network and MS taken into account. The selection of ciphering algorithms involves the following operations: 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 not enabled, the MS reports Classmark 1 and Classmark 2, indicating whether the MS supports A5/1, A5/2, and A5/3 ciphering algorithms. If the parameter ECSC in the system information is enabled, 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 Cipher Mode Command message from the MSC, the BSC checks the classmarks reported by the MS. If the BSC does not receive Classmark 3, which defines whether an MS supports A5/4, A5/5, A5/6, and A5/7 ciphering algorithms, the BSC sends a Classmark Enquiry message to the MS, asking the MS to report Classmark 3.
When selecting the ciphering algorithms, adhere to the following principles:

l
The common ciphering algorithms must be built with the following: ciphering algorithms specified in the ciphering command issued by the MSC, ciphering algorithms configured in the BSC, and ciphering algorithms supported by the MS. The BSC selects the appropriate ciphering algorithms from the common ciphering algorithms, and then sends a Cipher Mode Command message to the BTS.
NOTE
The priorities of the ciphering algorithms are decreased from A5/7 to A5/0.
Issue 02 (2008-06-30)
16-7
16 Ciphering
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. 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.
16.4.4 Signaling Ciphering Procedure

This describes the initialization of the signaling procedure for ciphering. The signaling 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 16-3 shows the ciphering procedure, which is initiated by the network and executed by the BTS. Figure 16-3 Ciphering procedure
MS BTS BSC
Ciphering Mode Command(1)
MSC
Ciphering Mode Command(3) SDCCH Ciphering Mode Complete(4) SDCCH
Encryption Mode Command(2)
Ciphering Mode Complete(5)
Setting the Ciphering Mode

On completing the authentication procedure, 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 if yes which ciphering algorithms should be used.
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 ciphering key (Kc) stored on the SIM card into the mobile equipment. The Ciphering Mode Command message received in other cases is considered erroneous. In this case, the MS sends an RR Status message with the cause Protocol Error and takes no further actions. A valid Ciphering Mode Command message is defined to be one of the following:

l
16 Ciphering
One that indicates "start ciphering" and is received by the MS in the "not ciphered" mode. One that indicates "no ciphering" and is received by the MS in the "not ciphered" mode. One that indicates "no ciphering" and is received by the MS in the "ciphered" mode.
l l
2.
After the MS receives the Ciphering Mode Command message and finishes the ciphering, it begins to send and receive messages in the ciphering 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. If the "cipher response" field of the cipher response information element in the Ciphering Mode Command message specified "IMEISV request" the MS shall include its IMEISV in the Ciphering Mode Complete message.
3.
On receiving the Ciphering Mode Complete message from the MS, the network starts information transmission in the ciphering mode.
16.5 Capabilities
This describes the ciphering algorithms supported at present. Presently, Huawei equipment supports the following ciphering algorithms: A5/1, A5/2, and A5/3. The ciphering algorithms A5/1, A5/2, and A5/3 can be configured flexibly to meet specific regional requirements. As A5/2 is prone to be decrypted, the 3GPP Organizational Partners allow all countries to apply for A5/1 or A5/3. The A5/3 ciphering algorithm is preferred over other ciphering algorithms in terms of security.
16.6 Implementation
This describes how to configure, reconfigure, and disable ciphering. 16.6.1 Configuring Ciphering This describes how to configure ciphering on the BSC6000 Local Maintenance Terminal. 16.6.2 Reconfiguring Ciphering This describes how to configure ciphering on the BSC6000 Local Maintenance Terminal. 16.6.3 Disabling Ciphering This describes how to disable ciphering on the BSC6000 Local Maintenance Terminal.
16.6.1 Configuring Ciphering

This describes how to configure ciphering on the BSC6000 Local Maintenance Terminal.
Context
Take configuring the A5/3 ciphering algorithm as an example. The BSC and MSC should be configured first.
Issue 02 (2008-06-30)
16-9
16 Ciphering
Procedure
Step 1 Configure ciphering data in the BSC. 1. 2. 3. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target cell and then choose Configure Cell Attributes . In the displayed dialog box, select the target cell in the Cell view list box to add the cell to the Selected cells list box. Click Next. In the displayed dialog box, click Set Cell Properties. A dialog box is displayed, as shown in Figure 16-4.
4.
In the Advanced Attributes area, click Call Control. A dialog box is displayed, as shown in Figure 16-5.
16-10
Issue 02 (2008-06-30)
16 Ciphering
5.
Set ECSC to Yes.

NOTE
ECSC is optional. You are advised to set ECSC to Yes to save network resources.
6. 7. 8. 9.
Click OK to return to the dialog box shown in Figure 16-4. Select A5/0 and A5/3 in the Encryption Algorithm check box. Click OK to complete the configuration. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and choose Configure BSC Attributes from the shortcut menu. Set the A Interface Tag to GSM_PHASE_2 or GSM_PHASE_2+, as shown in Figure 16-6.
Issue 02 (2008-06-30)
16-11
16 Ciphering
Figure 16-6 Configuring BSC attributes
Step 2 Configure A5/0 and A5/3 in the MSC. ----End
16.6.2 Reconfiguring Ciphering

This describes how to configure ciphering on the BSC6000 Local Maintenance Terminal.
Context
Take adjusting the ciphering algorithm from A5/1 to A5/3 as an example.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell and then choose Configure Cell Attributes. Step 2 In the displayed dialog box, select the target cell in the Cell view list box to add the cell to the Selected cells list box. Click Next. Step 3 In the displayed dialog box, click Set Cell Properties. A dialog box is displayed, as shown in Figure 16-7.
16-12
Issue 02 (2008-06-30)
16 Ciphering
Step 4 Clear A5/1 and select A5/3 in the Encryption AlgorithmEncryption Algorithm check box. Step 5 Click OK to complete the configuration. ----End
16.6.3 Disabling Ciphering

This describes how to disable ciphering on the BSC6000 Local Maintenance Terminal.
Context
Take disabling the A5/3 ciphering algorithm as an example.
Issue 02 (2008-06-30)
16-13
16 Ciphering
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell and choose Configure Cell Attributes from the shortcut menu. Step 2 In the displayed dialog box, select the target cell in the Cell view list box to add the cell to the Selected cells list box. Click Next. Step 3 In the displayed dialog box, click Set Cell Properties. A dialog box is displayed, as shown in Figure 16-8. Figure 16-8 Modifying ciphering algorithms
Step 4 Clear A5/3 in the Encryption Algorithm check box. Step 5 Click OK to complete the configuration. ----End
16 Ciphering

This lists the alarms and counters related to ciphering.
Alarms
None.
Counters
Table 16-3 lists the counters related to ciphering. Table 16-3 Counters related to ciphering Counter H332KJ Description Failed Outgoing External Inter-Cell Handovers (Handover Request Rejected) (Ciphering Algorithm not Supported)
16.8 References
3GPP 48058 Base Station Controller - Base Transceiver Station (BSC-BTS) Interface Layer 3 Specification
Issue 02 (2008-06-30)
16-15
17 Frequency Hopping
17
About This Chapter
Frequency Hopping
17.1 Overview This describes the definition of frequency hopping and the purposes of applying it in the GSM. Frequency hopping allows the transmit frequencies to vary within the allocated frequency spectrum based on a sequence. The frequency hopping has the features such as resistence to interference, anti-attenuation, and high security. 17.2 Availability This lists the NEs and software required for the implementation of frequency hopping. 17.3 Impact This describes the impact of frequency hopping on voice quality and data services. 17.4 Technical Description The frequency hopping technique can help decrease the influence of Rayleigh attenuation and increase the interference resistance of the system. 17.5 Capabilities This describes the capabilities of frequency hopping. The signal gain achieved through frequency hopping is generally 23 dB. 17.6 Implementation This describes how to configure frequency hopping. 17.7 Maintenance Information This lists the alarms related to frequency hopping. 17.8 References
Issue 02 (2008-06-30)
17-1
17.1 Overview
This describes the definition of frequency hopping and the purposes of applying it in the GSM. Frequency hopping allows the transmit frequencies to vary within the allocated frequency spectrum based on a sequence. The frequency hopping has the features such as resistence to interference, anti-attenuation, and high security.
Definition
A carrier frequency with hopping feature can hop to any frequency within a specified frequency band based on a sequence. Frequency hopping minimizes the interference on a radio channel from a single interference source. Thus, it is widely used in telecommunications system because it has the features such as resistance to interference, anti-attenuation, and high security.
Purposes
The application of frequency hopping in the GSM enhances the resistance to interference and increases the capacity of the system.
Terms
None.

Acronyms and Abbreviations SFH SFH BFH FER CA FN MAIO HSN MA Full Spelling Slow Frequency Hopping Synthesized Frequency Hopping Baseband Frequency Hopping Frame Error Rate Cell Allocation Frame Number Mobile Allocation Index Offset Hopping Sequence Number Mobile Allocation
17.2 Availability
This lists the NEs and software required for the implementation of frequency hopping.
NEs Involved
Table 17-1 lists the NEs involved in frequency hopping. Table 17-1 NEs involved in frequency hopping MS
NOTE
BTS
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 17-2 lists the versions of GBSS products that support frequency hopping. Table 17-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012A E BTS3006C BTS3002E BTS3900 GSM BTS3900A GSM DBS3900 GSM BTS312 BTS30 BTS3012A BTS3006A BTS3002C DTRU QTRU Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C01 and later releases G3BTS32.30000.00.1130 and later releases G3BTS32.30000.00.1130 and later releases G3BTS32V302R002C06 and later releases G3BTS32.30000.00.1130 and later releases G3BTS36.30000.01.0820A and later releases
Issue 02 (2008-06-30)
17-3
Miscellaneous
None
17.3 Impact
This describes the impact of frequency hopping on voice quality and data services.
Impact on Voice Quality

The introduction of frequency diversity gain and interference averaging in the frequency hopping mode can effectively improve voice quality. On frequency-restricted networks, the application of frequency hopping can help simplify frequency planning and improve system capacity.
Impact on Data Services

Frequency hopping technique has a negative impact on the network, especially in the high data rate schemes such as CS3, CS4, and MCS5MCS-9. Therefore, Huawei recommends that you do not enable frequency hopping in such case.
NOTE
If a cell requires the support of the data services and the configuration of the frequency hopping and if the number of frequencies allocated to the cell is greater than 16, then all the TRXs that configured with the PDCHs should use the same MA.

None

The frequency hopping technique can help decrease the influence of Rayleigh attenuation and increase the interference resistance of the system. 17.4.1 Principle of Frequency Hopping Frequency hopping is a technique that allows the carrier frequency to hop within a wide band based on a sequence. It has the features such as resistance to interference and anti-attenuation. 17.4.2 Category of Frequency Hopping Frequency hopping can be classified into slow frequency hopping and fast frequency hopping in terms of hopping speed. Also, radio frequency FH and baseband FH are defined in terms of implementation of the TRX. 17.4.3 Frequency Hopping Algorithms In frequency hopping, the frequency used by each timeslot is determined by the frequency hopping algorithms.
17.4.1 Principle of Frequency Hopping

Frequency hopping is a technique that allows the carrier frequency to hop within a wide band based on a sequence. It has the features such as resistance to interference and anti-attenuation. With the hopping of the frequencies, the signal fluctuation due to multipath propagation is minimized. The result is the same as frequency diversity. In mobile telecommunications, the
radio signals in transmission might vary abruptly in a short period due to the impact of Rayleigh attenuation. The radio signals vary according to the frequency. As the difference of frequencies increases, the attenuation becomes more independent. Take the frequency band allocated for mobile telecommunications for example. Basically, 200 kHz of frequency spacing can guarantee the irrelevancy of attenuation within the frequencies, while 2 MHz of frequency spacing can fully guarantee the irrelevancy of attenuation within the frequencies. The application of frequency hopping prevents all the bursts that carry the bits within one speech frame from being damaged by Rayleigh attenuation in the same manner, and improves the antiattenuation and interference resistance capacities of speech frames, as shown in Figure 17-1. Figure 17-1 Attenuation model
Level for receiving signals
Distance
The frequency hopping technique has the following features:

l
The signal gain achieved through frequency hopping is concerned with the environment, especially with the moving speed of an MS.
When the MS moves at a high speed, the location change of any two bursts within a channel can reduce the effect caused by the Rayleigh attenuation. Thus the frequency hopping gain is small. For a large number of slowly moving MSs, frequency hopping causes great gain.
The signal gain achieved through frequency hopping is also concerned with the available frequencies. As the number of frequencies decreases, the signal gain also decreases. Actually, frequency hopping is a pseudo frequency spreading technique; that is, the signal gain achieved through frequency hopping is equal to the signal gain after the frequency band that carries the valid signals is spread. When the signal gain achieved through frequency hopping is tested, different C/I ratios are specified for the frequencies allocated for a transmitter in the case that Frame Error Rate (FER) is the same. The difference between these C/I ratios is the signal gain achieved through frequency hopping.
Frequency hopping reduces the correlation with the interference along the transmission path. This prevents all the bursts that contain the bits from being damaged by the interference in the same manner.
The application of error-correction codec and interleaving techniques enables a receiver to reassemble the original data from the received data stream.
Issue 02 (2008-06-30)
If the interference is narrowband distributed, frequency hopping can achieve some signal gain. If the interference is broadband distributed and all the bursts are damaged, the original data cannot be reassembled and no signal gain is achieved.
NOTE
The interference is generally narrowband distributed in the existing networks.
In the frequency hopping mode, there might be cases where the Bit Error Rate (BER) increases, whereas you feel that the speech quality is improved. The speech quality is improved because the Frame Error Rate (FER) specification is improved when the BER increases.
17.4.2 Category of Frequency Hopping

Frequency hopping can be classified into slow frequency hopping and fast frequency hopping in terms of hopping speed. Also, radio frequency FH and baseband FH are defined in terms of implementation of the TRX. The GSM system requires that a carrier frequency remains unchanged during a burst period. Thus, the frequency hopping in GSM is a slow frequency hopping. In terms of time, frequency hopping is classified into the following types:
l
Frame frequency hopping In frame frequency hopping, the carrier frequencies change with every TDMA frame while the carrier frequency assigned for the eight timeslots of the TDMA frame remains unchanged. The BCCH TRX does not use the frequency hopping mechanism in this mode.
Timeslot frequency hopping In timeslot frequency hopping, the carrier frequency changes with every timeslot of a TDMA frame.
In terms of TRX implementation, frequency hopping is classified into the following types:
l
RF FH In RF frequency hopping, the carrier frequencies for the transmitter and receiver of TRX participate in frequency hopping. The carrier frequencies assigned for frequency hopping in a cell are specified by the hopping sequence. The number of carrier frequencies assigned for frequency hopping can exceed the number of TRXs assigned for the cell.
Baseband FH 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 switch 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. The TCHs carried on the BCCH TRX can also take part in frequency hopping.
You can set the FH Mode of the TRX to select a frequency hopping category. Irrespective of the frequency hopping mode adopted on the network, the carrier frequency assigned for the transmitter of the TRX and that assigned for the receiver of the TRX must remain consistent in terms of the MS. The carrier frequency assigned for each burst can change.

NOTE
In RF frequency hopping, the carrier frequency assigned for the transmitter of the TRX varies with each burst. Thus, the tuning of the RF front-end device must match the varying speed of the carrier frequencies. An alternative broadband device can be used in this case. The DFCU (cavity combiner) is a narrowband combiner and its tuning speed cannot keep up with the varying speed of the carrier frequencies assigned for the TRX. Thus, only baseband frequency hopping, instead of RF frequency hopping, can be used for the DFCU.
17.4.3 Frequency Hopping Algorithms

In frequency hopping, the frequency used by each timeslot is determined by the frequency hopping algorithms. Table 17-3 describes the parameters related to the frequency hopping algorithms. Table 17-3 Parameters related to frequency hopping algorithms Parameter Cell Allocation table (CA) TDMA Frame Number (FN) Mobile Allocation table (MA) Description CA table collects all the ARFCNs assigned for the cells. FN is broadcast on the SCH. The MS synchronizes with the BTS by monitoring the FN (02715647). MA is a subset of CA. It is a frequency sequence set used for the MS frequency hopping. The MA table comprises N frequency sequences, where 1 N 64. FH Group No. is the group number in the MA table. It is used to distinguish the frequency hopping groups. MAI specifies an element in the MA table. In other words, the carrier frequency actually used is specified by the MAI. In mobile telecommunications, the radio frequency sequence adopted on the Um interface is an element in the MA table. MAIO is an initial offset of the MAI. It is used to prevent multiple channels from gaining access to one TRX at the same time. The corresponding parameter is MAIO. The carrier frequencies hop along the time, controlled by a sequence called HSN. One hopping sequence is a queue of the N carrier frequencies (MA) computed through frequency hopping algorithms, given the HSN, MAIO, and FN. Different channels allocated on different timeslots can use the same hopping sequence. Different channels allocated on the same timeslots of the same cell use different MAIOs.
NOTE HSN=0 means cyclic hopping and HSN0 means pseudorandom hopping.
Mobile Allocation Index (MAI) (0 to N-1) Mobile Allocation Index Offset (MAIO) (0 to N-1)
Hopping Sequence Number (HSN) (063)
In Table 17-3, MAI = (S + MAIO) MOD N, where S is computed from FN and HSN.
l l
If HSN=0, then S=FN. If HSN0, then S is computed through the frequency hopping algorithms.
Figure 17-2 shows the flow associated with the frequency hopping algorithms. Figure 17-2 Flow of frequency hopping algorithms
MAI (m0~mN-1) MAIO (0~N-1) NBIN bit FN T3(0~50) 6bit HSN (0~63) 6bit FN T1(0~2047) 11bit T1R= T1 MOD 64
6bit
FN T2(0~25) 5bit Represent in 7 bit 7bit
XOR 6bit
Addition
7bit Look-up Table 7bit Addition 8bi t M'=M mod 2^NBIN NBIN bit N M'<N Y
T=T3 mod 2^NBIN NBIN bit
S=(M'+T) mod N
NBIN bit
S=M'
MAI=(S+MAIO) mod N NBIN bit RFCN=MA(MAI)

T1: Time parameter, from 0 to 2047 (11 bits) T3: Time parameter, from 0 to 50 (6 bits) NBIN: INTEGER (log2N+1) XOR: Bit-wise exclusive or of 8 bit binary operands T2: Time parameter, from 0 to 25 (5 bits) ^: raised to the power of Table: table of 114 integer numbers
Table 17-4 describes the Table shown in Figure 17-2.
17-8
Issue 02 (2008-06-30)
Table 17-4 Explanation list of the Table Addr ess 000-0 09 010-0 19 020-0 29 030-0 39 040-0 49 050-0 59 060-0 69 070-0 79 080-0 89 090-0 99 100-1 09 110-1 13 Content 48 0 101 80 55 87 82 77 117 16 91 129 98 64 47 34 111 19 58 108 114 49 15 99 63 25 118 127 75 3 40 122 4 7 21 17 1 81 85 13 38 68 107 37 90 79 24 123 36 76 18 6 109 110 32 60 43 119 46 95 59 56 89 71 26 5 66 52 61 39 78 124 96 57 112 33 106 121 53 22 93 102 23 86 103 29 31 92 42 113 84 105 94 104 54 12 11 8 62 51 120 9 65 73 100 2 74 88 45 67 126 72 97 70
17.5 Capabilities
This describes the capabilities of frequency hopping. The signal gain achieved through frequency hopping is generally 23 dB. The uplink and downlink signal gain achieved through frequency hopping is symmetrical. The signal gain achieved through frequency hopping varies a little with that of the antennas having diversity receiver feature. Generally, the signal gain achieved through frequency hopping is regarded as 23 dB.
17.6 Implementation
This describes how to configure frequency hopping.
17.6.1 Changing None FH to RF FH This describes how to change the FH mode of a cell from none FH to RF FH to achieve frequency reuse, interference averaging, or network optimization. 17.6.2 Changing None FH to Baseband FH This describes how to change the FH mode of a cell from none FH to baseband FH to achieve frequency reuse, interference averaging, or network optimization. 17.6.3 Changing RF FH to Baseband FH This describes how to change the FH mode of a cell from RF FH to baseband FH to achieve frequency reuse, interference averaging, or network optimization. 17.6.4 Changing Baseband FH to RF FH This describes how to change the FH mode of a cell from baseband FH to RF FH to achieve frequency reuse, interference averaging, or network optimization. 17.6.5 Changing RF FH to None FH This describes how to change the FH mode of a cell from RF FH to None FH to achieve frequency reuse, interference averaging, or network optimization. 17.6.6 Changing Baseband FH to None FH This describes how to change the FH mode of a cell from baseband FH to None FH to achieve frequency reuse, interference averaging, or network optimization.
17.6.1 Changing None FH to RF FH

This describes how to change the FH mode of a cell from none FH to RF FH to achieve frequency reuse, interference averaging, or network optimization. Scenario Impact Network optimization After the FH mode of a cell is changed, the cell is reset and the cell services are affected.
NEs InvolvedBSC and BTS
Prerequisite
l l l
The LMT runs properly. The communication between the LMT and the BSC is normal. The communication between the BTS and the BSC is normal.
Preparation
Table 17-5 lists the data to be negotiated and planned before you change none FH to RF FH. Table 17-5 Data to be negotiated and planned for changing none FH to RF FH Category FH mode Description FH has three modes: RF FH, Baseband FH, and None FH. Source Network planning
17-10
Issue 02 (2008-06-30)
Category TRXs Frequencies
Description The cell must be configured with at least two TRXs. The number of frequencies in a cell must be greater than the number of TRXs joining in FH.
Source Network planning Network planning
Table 17-6 lists the data to be negotiated and planned for changing none FH to RF FH. Table 17-6 Example of the data negotiated and planned for changing none FH to RF FH Category FH mode TRXs Original Configuration Data None FH
l l l l l l l l l l l l l
Target Configuration Data RF FH (HSN = 1, MAIO = 0, 1, 2)

TRX 0 TRX 1 TRX 2 TRX 3 TRX 4 TRX 5 TRX 6 TRX 7 TRX 8 TRX 9 TRX 10 TRX 11 TRX 12
Issue 02 (2008-06-30)
17-11
Category Frequencies
Original Configuration Data

l
Target Configuration Data

l
Frequencies of cell 3012-1:

MA of cell 3012-1:

0 10 13 16 19
l
0 10 13 16 19 11 14 17 20 12 15 18 21

MA of cell 3012-2:

11 14 17 20
l

MA of cell 3012-4:

12 15 18 21
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click the target cell. Choose Configure Cell Attributes. A dialog box is displayed, as shown in Figure 17-3.
17-12
Issue 02 (2008-06-30)
Figure 17-3 Configuring Cells Attributes dialog box
Step 2 Add the cell from the Cell view list box to the Selected cells list box, as shown in Figure 17-4. Figure 17-4 Selecting a cell
Step 3 Click Next. A dialog box is displayed, as shown in Figure 17-5.
Issue 02 (2008-06-30)
17-13
Step 4 Select 3012-1 from the Cells to be set list box, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 17-6.
17-14
Issue 02 (2008-06-30)
Step 5 Click Frequency Hopping. A dialog box is displayed, as shown in Figure 17-7.
Issue 02 (2008-06-30)
17-15
Figure 17-7 Configuring FH attributes
Step 6 Select RF FH from the FH Mode drop-down list. A dialog box is displayed, as shown in Figure 17-8. Figure 17-8 Selecting the RF FH mode
17-16
Issue 02 (2008-06-30)

NOTE
l l l
Under normal conditions, retain the default settings of the other parameters. The MAIO of each TRX in the same FH group must be unique. Otherwise, the TCH assignment fails. The value of the MAIO must not exceed the number of frequencies in the FH group.
Step 7 Click Configure MA Group. A dialog box is displayed, as shown in Figure 17-9. Figure 17-9 Configuring cell MA group attributes
NOTE
l l l l
Under normal conditions, retain the default settings of the parameters. In RF FH mode, one cell is usually configured with only one MA group. One cell must have only one HSN. The TSCand BCC must be the same.
Step 8 Click OK to finish the configuration of cell MA group attributes and return to the dialog box shown in Figure 17-8. Step 9 Click OK to finish the configuration of FH attributes and return to the dialog box shown in Figure 17-6. Step 10 Click OK to finish the changing of the FH mode of cell 3012-1 and return to the dialog box shown in Figure 17-5. Step 11 In the dialog box shown in Figure 17-5, select 3012-2. Repeat the previous steps to change the FH mode.
NOTE
The procedure for changing the FH mode of cell 3012-2 or cell 3012-4 is the same as that of cell 3012-1.
Issue 02 (2008-06-30)
17-17
Step 12 After the FH mode is changed, click Finish in the dialog box shown in Figure 17-5. ----End
17.6.2 Changing None FH to Baseband FH

This describes how to change the FH mode of a cell from none FH to baseband FH to achieve frequency reuse, interference averaging, or network optimization. Scenario Impact Network optimization After the FH mode of a cell is changed, the cell is reset and the cell services are affected.
Prerequisite
l l l
Preparation
Table 17-7 lists the data to be negotiated and planned before you change none FH to baseband FH. Table 17-7 Data to be negotiated and planned before you change none FH to baseband FH Category FH mode TRXs Frequencies Description FH has three modes: RF FH, Baseband FH, and None FH. The cell must be configured with at least two TRXs. The number of frequencies in a cell must be greater than the number of TRXs joining in FH. Source Network planning Network planning Network planning
Table 17-8 lists the data negotiated and planned for changing none FH to baseband FH. Table 17-8 Example of the data negotiated and planned for changing none FH to baseband FH Category FH mode Original Configuration Data None FH Target Configuration Data Baseband FH (HSN = 1, MAIO = 0, 1, 2)
17-18
Issue 02 (2008-06-30)
Category TRXs


l l l l l l l l l l l l l l
TRX 0 TRX 1 TRX 2 TRX 3 TRX 4 TRX 5 TRX 6 TRX 7 TRX 8 TRX 9 TRX 10 TRX 11 TRX 12 Frequencies of cell 3012-1:

TRX 0 TRX 1 TRX 2 TRX 3 TRX 4 TRX 5 TRX 6 TRX 7 TRX 8 TRX 9 TRX 10 TRX 11 TRX 12 MA of cell 3012-1:

Frequenci es
0 10 13 16 19
l
0 10 13 16 19 11 14 17 20 12 15 18 21

MA of cell 3012-2:

11 14 17 20
l

MA of cell 3012-4:

12 15 18 21
Procedure
Issue 02 (2008-06-30)
17-19
17-20
Issue 02 (2008-06-30)
Issue 02 (2008-06-30)
17-21
17-22
Issue 02 (2008-06-30)
Step 6 Select Baseband FH from the FH Mode drop-down list. A dialog box is displayed, as shown in Figure 17-15. Figure 17-15 Selecting the baseband FH mode
Issue 02 (2008-06-30)
17-23
NOTE
l l
Under normal conditions, retain the default settings of the other parameters. During this operation, a dialog box is displayed, asking you to decide whether to allow the BCCH frequency to participate in baseband FH. Select Yes.
NOTE
l l
Under normal conditions, use the default settings. Under normal conditions, one cell is configured with only one MA group. In baseband FH mode, if the BCCH frequency participates in baseband FH, at lease two MA groups must be configured: One MA group contains the BCCH frequency, and the other MA group does not contain the BCCH frequency. By default, two MA groups meeting the previous requirement are configured. To configure other types of MA groups, set Configure MA Group. One cell must have only one HSN. The TSCand BCC must be the same.
l l
Step 8 Click OK to finish the configuration of cell MA group attributes and return to the dialog box shown in Figure 17-15.
NOTE
A message box is displayed, indicating that if the FH mode is changed to baseband FH, TRX Aiding Function Control will be automatically set to Allowed & Recover When Check Res. Click OK to confirm the modification.
Step 9 Click OK to finish the configuration of FH attributes and return to the dialog box shown in Figure 17-13.
Step 10 Click OK to finish the changing of the FH mode of cell 3012-1 and return to the dialog box shown in Figure 17-12. Step 11 In the dialog box shown in Figure 17-12, select 3012-2. Repeat the previous steps to change the FH mode.
NOTE
17.6.3 Changing RF FH to Baseband FH

This describes how to change the FH mode of a cell from RF FH to baseband FH to achieve frequency reuse, interference averaging, or network optimization. Scenario Impact Network optimization After the FH mode of a cell is changed, the cell is reset and the cell services are affected.
Prerequisite
l l l
Preparation
Table 17-9 lists the data to be negotiated and planned before you change RF FH to baseband FH. Table 17-9 Data to be negotiated and planned before you change RF FH to baseband FH Category FH mode TRXs Frequencies Description FH has three modes: RF FH, Baseband FH, and None FH. The cell must be configured with at least two TRXs. The number of frequencies in a cell must be greater than the number of TRXs joining in FH. Source Network planning Network planning Network planning
Table 17-10 lists the data negotiated and planned for changing RF FH to baseband FH.
Table 17-10 Example of the data negotiated and planned for changing RF FH to baseband FH Category FH mode TRXs Original Configuration Data RF FH (HSN = 1, MAIO = 0, 1, 2)
Target Configuration Data Baseband FH (HSN = 1, MAIO = 0, 1, 2)



Frequencies
0 10 13 16 19
l
0 10 13 16 19 11 14 17 20 12 15 18 21
MA of cell 3012-2:

MA of cell 3012-2:

11 14 17 20
l
MA of cell 3012-4:

MA of cell 3012-4:

12 15 18 21
Procedure
Issue 02 (2008-06-30)
17-27
17-28
Issue 02 (2008-06-30)
Issue 02 (2008-06-30)
17-29
Step 6 Select None FH from the FH Mode drop-down list. An information box is displayed, as shown in Figure 17-22. Figure 17-22 Information box
NOTE
Before changing the FH mode of a cell from RF FH to baseband FH or from baseband FH to RF FH, you must set the FH mode of the cell to None FH.
Step 7 Click OK. A dialog box is displayed, as shown in Figure 17-23.
17-30
Issue 02 (2008-06-30)
Figure 17-23 Reconfiguring FH attributes
NOTE
You need to reassign frequencies for all the TRXs except the TRX carrying the BCCH.
Step 8 Double-click TRX 2. A dialog box is displayed, as shown in Figure 17-24. Figure 17-24 Configuring TRX attributes
Step 9 Select a frequency from the Available Frequencies list box and add it to the Assigned Frequencies list box, as shown in Figure 17-25.
Figure 17-25 Assigning a frequency to TRX 2
Step 10 Click OK. TRX 2 is assigned a frequency. Use the same method to assign frequencies 13, 16, and 19 to TRX 4, TRX 6, and TRX 8 respectively. Figure 17-26 shows the dialog box after the frequencies are assigned. Figure 17-26 Assigning frequencies completed
Step 11 Select Baseband FH from the FH Mode drop-down list. A dialog box is displayed, as shown in Figure 17-27.

NOTE
During this operation, a dialog box is displayed, asking you to decide whether to allow the BCCH frequency to participate in baseband FH. Select Yes.
Figure 17-27 Configuring attributes of baseband FH
NOTE
Under normal conditions, retain the default settings of the other parameters.
Issue 02 (2008-06-30)
17-33
NOTE
Under normal conditions, if the BCCH frequency participates in baseband FH, at lease two MA groups must be configured: One MA group contains the BCCH frequency, and the other MA group does not contain the BCCH frequency. By default, two MA groups meeting the previous requirement are configured. To configure other types of MA groups, set Configure MA Group. One cell must have only one HSN. The TSCand BCC must be the same.
l l
Step 13 Click OK to finish the configuration of cell MA group attributes and return to the dialog box shown in Figure 17-22. Step 14 Click OK to finish the configuration of FH attributes and return to the dialog box shown in Figure 17-20. Step 15 Click OK to finish the changing of the FH mode of cell 3012-1 and return to the dialog box shown in Figure 17-19. Step 16 In the dialog box shown in Figure 17-19, select 3012-2 and change the FH mode of 3012-2 from RF FH to Baseband FH using the same method as changing the FH mode of cell 3012-1.
NOTE
The procedure for changing the FH mode of cell 3012-4 from RF FH to Baseband FH is the same as that for changing the FH mode of cell 3012-1.
Step 17 After changing the FH modes of cells 3012-1, 3012-2, and 3012-4, click Finish in the dialog box shown in Figure 17-19. ----End
17.6.4 Changing Baseband FH to RF FH

This describes how to change the FH mode of a cell from baseband FH to RF FH to achieve frequency reuse, interference averaging, or network optimization. Scenario Impact Network optimization After the FH mode of a cell is changed, the cell is reset and the cell services are affected.
Prerequisite
l l l
Preparation
Table 17-11 lists the data to be negotiated and planned before you change baseband FH to RF FH.
17-34
Issue 02 (2008-06-30)
Table 17-11 Data to be negotiated and planned before you change baseband FH to RF FH Category FH mode TRXs Frequencies Description FH has three modes: RF FH, Baseband FH, and None FH. The cell must be configured with at least two TRXs. The number of frequencies in a cell must be greater than the number of TRXs joining in FH. Source Network planning Network planning Network planning
Table 17-12 lists the data negotiated and planned for changing baseband FH to RF FH. Table 17-12 Example of the data negotiated and planned for changing baseband FH to RF FH Category FH mode TRXs Original Configuration Data Baseband FH (HSN = 1, MAIO = 0, 1, 2)
Target Configuration Data RF FH (HSN = 1, MAIO = 0, 1, 2)

Issue 02 (2008-06-30)
17-35
Category Frequencies

l

l
MA of cell 3012-1:

MA of cell 3012-1:

0 10 13 16 19
l
0 10 13 16 19 11 14 17 20 12 15 18 21
MA of cell 3012-2:

MA of cell 3012-2:

11 14 17 20
l
MA of cell 3012-4:

MA of cell 3012-4:

12 15 18 21
Procedure
17-36
Issue 02 (2008-06-30)
Issue 02 (2008-06-30)
17-37
17-38
Issue 02 (2008-06-30)
Issue 02 (2008-06-30)
17-39
Step 6 Select None FH from the FH Mode drop-down list. A dialog box is displayed, as shown in Figure 17-34. Figure 17-34 Changing to none FH mode
NOTE
Before changing the FH mode of a cell from RF FH to baseband FH or from baseband FH to RF FH, you must set the FH mode of the cell to None FH.
17-40
Issue 02 (2008-06-30)
Step 7 Select RF FH from the FH Mode drop-down list. A dialog box is displayed, as shown in Figure 17-35. Figure 17-35 Configuring attributes of RF FH
NOTE
l l l
Under normal conditions, retain the default settings of the other parameters. The MAIO of each TRX in the same FH group must be unique. Otherwise, the TCH assignment fails. The value of the MAIO must not exceed the number of frequencies in the FH group.
Step 8 Click Configure MA Group. A dialog box is displayed, as shown in Figure 17-36.
Issue 02 (2008-06-30)
17-41
Figure 17-36 Configuring cell MA group attributes
NOTE
l l l l
Under normal conditions, retain the default settings of the parameters. In RF FH mode, one cell is usually configured with only one MA group. One cell must have only one HSN. The TSCand BCC must be the same.
NOTE
Under normal conditions, one cell is configured with only one MA group.
Step 9 Click OK to finish the configuration of cell MA group attributes and return to the dialog box shown in Figure 17-34. Step 10 Click OK to finish the configuration of FH attributes and return to the dialog box shown in Figure 17-32. Step 11 Click OK to finish the changing of the FH mode of cell 3012-1 and return to the dialog box shown in Figure 17-31. Step 12 In the dialog box shown in Figure 17-31, select 3012-2. Repeat the previous steps to change the FH mode.
NOTE
17-42
Issue 02 (2008-06-30)
17.6.5 Changing RF FH to None FH

This describes how to change the FH mode of a cell from RF FH to None FH to achieve frequency reuse, interference averaging, or network optimization. Scenario Impact Network optimization After the FH mode of a cell is changed, the cell is reset and the cell services are affected.
Prerequisite
l l l
Preparation
Table 17-13 lists the data to be negotiated and planned before you change RF FH to none FH. Table 17-13 Data to be negotiated and planned before you change RF FH to none FH Category FH mode TRXs Frequencies Description FH has three modes: RF FH, Baseband FH, and None FH. The cell must be configured with at least two TRXs. The number of frequencies in a cell must be greater than the number of TRXs joining in FH. Source Network planning Network planning Network planning
Table 17-14 lists the data negotiated and planned for changing RF FH to none FH. Table 17-14 Example of the data negotiated and planned for changing RF FH to none FH Category FH mode Original Configuration Data RF FH (HSN = 1, MAIO = 0, 1, 2) Target Configuration Data None FH
Issue 02 (2008-06-30)
17-43
Category TRXs




Frequencies
0 10 13 16 19
l
0 10 13 16 19 11 14 17 20 12 15 18 21
MA of cell 3012-2:


11 14 17 20
l
MA of cell 3012-4:


12 15 18 21
Procedure
17-44
Issue 02 (2008-06-30)
Issue 02 (2008-06-30)
17-45
17-46
Issue 02 (2008-06-30)
Issue 02 (2008-06-30)
17-47
Step 6 Select None FH from the FH Mode drop-down list. An information box is displayed, as shown in Figure 17-42. Figure 17-42 Information box
17-48
Issue 02 (2008-06-30)
Figure 17-43 Reconfiguring FH attributes
NOTE
You need to reassign frequencies for all the TRXs except the TRX carrying the BCCH.
Step 8 Double-click TRX 2. A dialog box is displayed, as shown in Figure 17-44. Figure 17-44 Configuring TRX attributes
Step 9 Select a frequency from the Available Frequencies list box and add it to the Assigned Frequencies list box, as shown in Figure 17-45.
Figure 17-45 Assigning a frequency to TRX 2
Step 10 Click OK. TRX 2 is assigned a frequency. Use the same method to assign frequencies 13, 16, and 19 to TRX 4, TRX 6, and TRX 8 respectively. Figure 17-46 shows the dialog box after the frequencies are assigned. Figure 17-46 Assigning frequencies completed
Step 11 Click OK to finish the configuration of FH attributes and return to the dialog box shown in Figure 17-40.
Step 12 Click OK to finish changing the FH mode and return to the dialog box shown in Figure 17-39. Step 13 Select 3012-2 from the Cells to be set list box and modify the FH mode of cell 3012-2 by using the same method as modifying the FH mode of cell 3012-1.
NOTE
The procedure for changing the FH mode of cell 3012-4 is the same as that for changing the FH mode of cell 3012-1.
17.6.6 Changing Baseband FH to None FH

This describes how to change the FH mode of a cell from baseband FH to None FH to achieve frequency reuse, interference averaging, or network optimization. Scenario Impact Network optimization After the FH mode of a cell is changed, the cell is reset and the cell services are affected.
Prerequisite
l l l
Preparation
Table 17-15 lists the data to be negotiated and planned before you change baseband FH to none FH. Table 17-15 Data to be negotiated and planned before you change baseband FH to none FH Category FH mode TRXs Frequencies Description FH has three modes: RF FH, Baseband FH, and None FH. The cell must be configured with at least two TRXs. The number of frequencies in a cell must be greater than the number of TRXs joining in FH. Source Network planning Network planning Network planning
Table 17-16 lists the data to be negotiated and planned for changing baseband FH to none FH.
Table 17-16 Example of the data negotiated and planned for changing baseband FH to none FH Category FH mode TRXs Original Configuration Data Baseband FH (HSN = 1, MAIO = 0, 1, 2)
Target Configuration Data None FH



Frequencies
0 10 13 16 19
l
0 10 13 16 19 11 14 17 20 12 15 18 21
MA of cell 3012-2:


11 14 17 20
l
MA of cell 3012-4:


12 15 18 21
Procedure
Issue 02 (2008-06-30)
17-53
17-54
Issue 02 (2008-06-30)
Issue 02 (2008-06-30)
17-55
Step 6 Select None FH from the FH Mode drop-down list. A dialog box is displayed, as shown in Figure 17-52. Figure 17-52 Changing to none FH mode
Step 7 Click OK to finish the configuration of FH attributes and return to the dialog box shown in Figure 17-50. Step 8 Click OK to finish the changing of the FH mode of cell 3012-1 and return to the dialog box shown in Figure 17-49. Step 9 Select 3012-2 from the Cells to be set list box and modify the FH mode of cell 3012-2 by using the same method as modifying the FH mode of cell 3012-1.
17-56
Issue 02 (2008-06-30)

NOTE
The procedure for changing the FH mode of cell 3012-4 is the same as that for changing the FH mode of cell 3012-1.

This lists the alarms related to frequency hopping.
Alarms
Table 17-17 lists the alarms related to frequency hopping. Table 17-17 Alarms Alarm ID 403 404 Alarm Name Baseband FH Mutual Aid in a Cell Switchback after Baseband FH Mutual Aid in a Cell
Counters
None.
17.8 References
GSM 05.02 / ETS 300 908 Multiplexing and multiple access on the radio path
Issue 02 (2008-06-30)
17-57
18 eMLPP
18
About This Chapter
eMLPP
18.1 Overview This describes eMLPP. The eMLPP is used for the quick establishment of a call when an MS accesses the network. When the network resources are insufficient, eMLPP enables the MS to wait in a queue and to preferentially seize call resources. 18.2 Availability This describes the availability of eMLPP. The realization of eMLPP depends on the cooperation of the appropriate network elements, software, parameters, and license. 18.3 Impact This describes the impact of eMLPP on system performance. 18.4 Technical Description This describes the technical aspects of eMLPP. When an MS with a high priority initiates a call, the MSC sets the parameters related to the A interface based on the user class information that is received from the HLR. The call with a high priority is established based on these parameters. 18.5 Capabilities None. 18.6 Implementation This describes how to configure, verify, and deactivate the eMLPP. 18.7 Maintenance Information This lists the alarms and counters related to eMLPP. 18.8 References
Issue 02 (2008-06-30)
18-1
18 eMLPP
18.1 Overview
This describes eMLPP. The eMLPP is used for the quick establishment of a call when an MS accesses the network. When the network resources are insufficient, eMLPP enables the MS to wait in a queue and to preferentially seize call resources.
Definition
The enhanced Multi-Level Precedence and Preemption service (eMLPP) is a supplementary service offered by the GSM system. When the eMLPP is available, 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, in peak working hours, the call with a higher priority can preempt the resources of the call with a lower priority. The eMLPP service consists of the following:
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. This can reduce the call setup time.
Queuing and preemption When network resources, including trunk circuits, signaling channels, and traffic channels, are insufficient, the call with a higher priority is not released, but waits in a queue or even preempts the resources of the call with a lower priority.
Purposes
The eMLPP service is used to classify calls into groups with different priorities. The call with a higher priority can receive better services, such as channel preemption and fast call setup. The eMLPP service offers a segmentation function for operators. Operators can use this function to provide different levels of services for users with different priorities.
Terms
Terms eMLPP PL PCI PVI QA PREC QRI PIE
18-2
Definition Enhanced multi-level precedence and pre-emption service Priority level Preemption capability indicator Preemption vulnerability indicator Queuing allowed indicator Preemption recommendation indicator Queuing recommendation indicator Priority information element
18 eMLPP
Terms License
Definition License for equipment running

Acronyms and Abbreviations eMLPP PCI PVI PL QA PIE PREC QRI LMT TCH TCHF TCHH SDCCH Full Spelling enhanced Multi-Level Precedence and Preemption service Preemption Capability Indicator Preemption Vulnerability Indicator Priority Level Queuing Allowed indicator Priority Information Element Preemption Recommendation Queuing Recommendation Indicator Local Maintenance Terminal Traffic Channel Traffic CHannel Full rate Traffic CHannel Half rate Stand-alone Dedicated Control Channel
18.2 Availability
This describes the availability of eMLPP. The realization of eMLPP depends on the cooperation of the appropriate network elements, software, parameters, and license.
NEs Involved
Table 18-1 lists the NEs involved in eMLPP. Table 18-1 NEs involved in eMLPP MS BTS BSC MSC MGW SGSN GGSN HLR
Issue 02 (2008-06-30)
18-3
18 eMLPP
MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 18-2 lists the versions of GBSS products that support eMLPP. Table 18-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM BTS3X BTS3002C BTS3001C BTS24 Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases G3BTS32.30000.01.1130 and later releases G3BTS36.30000.03.0820 and later releases G3BTS34.30000.07.0301 and later releases G3BTS24.20000.07.1111 and later releases
Miscellaneous
In addition, the eMLPP service is available under the following conditions:
l l
An appropriate license for eMLPP is obtained and the license is activated. The eMLPP feature is enabled in the cell.
18.3 Impact
This describes the impact of eMLPP on system performance.
18 eMLPP

When resources are insufficient, the eMLPP service ensures that the MS with a high priority uses 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 counters related to Call Drop Ratio on TCH increase.

None.

This describes the technical aspects of eMLPP. When an MS with a high priority initiates a call, the MSC sets the parameters related to the A interface based on the user class information that is received from the HLR. The call with a high priority is established based on these parameters. 18.4.1 A Interface Parameters Involved in eMLPP This lists the A interface parameters involved in eMLPP. The A interface parameters that the BSC obtains from the MSC determine the eMLPP. 18.4.2 Call Establishment Procedure This describes the procedure for assigning a TCH by the BSC. The BSC assigns a TCH when an MS with a high priority initiates a call or receives a call in a congested cell.
18.4.1 A Interface Parameters Involved in eMLPP

This lists the A interface parameters involved in eMLPP. The A interface parameters that the BSC obtains from the MSC determine the eMLPP. Table 18-3 lists the A interface parameters involved in eMLPP. Table 18-3 A interface parameters involved in eMLPP Parameter PCI Meaning Flag bit of preemption Description If PCI allows preemption (PCI = 1), the call can preempt the radio resources of the call with a lower priority. If PVI allows being preempted (PVI = 1), the radio resources of the call can be preempted by the call with a higher priority.
PVI
Flag bit of being preempted
Issue 02 (2008-06-30)
18-5
18 eMLPP
Parameter PL
Meaning Priority level
Description According to the GSM PHASE2+ protocol, PL has 14 levels. Level 1 represents the highest priority and level 14 represents the lowest priority. If QA allows queuing (QA = 1), the call can queue. PIE consists of PCI, PVI, PL, and QA.
QA PIE
Queuing indicator None.
18.4.2 Call Establishment Procedure

This describes the procedure for assigning a TCH by the BSC. The BSC assigns a TCH 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. If the cell does not have an idle TCH, go to 2. If PCI = 1, go to 3. If PCI is not 1, the procedure is complete. If such an MS is found, go to 4. If such an MS is not found, go to 5. If the handover is successful, go to 6. If the handover fails, go to 7. If QA = 1, the high-priority MS queues. Then, go to 8. If QA is not 1, the high-priority MS cannot queue. The procedure is complete.
2.
The BSC determines the PCI of the high-priority MS.

l l
3.
The BSC searches for the lowest-priority MS whose PVI is 1.

l l
4.
The BSC triggers the handover of the MS with the lowest priority.
l l
5.
The BSC determines the QA of the high-priority MS.

l l
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.
18-6
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
18 eMLPP
If an idle channel is available within half of the timing length of the queue timer, the high-priority MS seizes the channel. The procedure is complete. If the MS waits in the queue for half of 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. If the MS waits in the queue for half of 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.
18.5 Capabilities
None.
18.6 Implementation
This describes how to configure, verify, and deactivate the eMLPP. 18.6.1 Configuring eMLPP This describes how to enable and configure eMLPP on the BSC6000 Local Maintenance Terminal. 18.6.2 Verifying eMLPP This describes how to verify eMLPP on the BSC6000 Local Maintenance Terminal. 18.6.3 Disabling eMLPP This describes how to disable eMLPP on the BSC6000 Local Maintenance Terminal.
18.6.1 Configuring eMLPP

This describes how to enable and configure eMLPP on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license of NC2 is applied and activated. To apply for and activate the license, do as follows: 1. In BSC6000V900R008 Exceptional Commercial License Application Template, set Whether to activate the eMLPP function or not under License control items to 1. The value 1 indicates that this function is enabled. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell, and then choose Configure Cell Attributes from the shortcut menu. The Configuring Cell Attributes dialog box is displayed. Step 2 Double-click the target cell in the Cell view list box to add it to the Selected cells list box. Step 3 Click Next. The Configuring Cells Attributes dialog box is displayed.
18 eMLPP
Step 4 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 18-1. Figure 18-1 Set Cell Attributes dialog box
Step 5 Click Call Control. A dialog box is displayed, as shown in Figure 18-2.
18-8
Issue 02 (2008-06-30)
18 eMLPP
Figure 18-2 Setting Allow EMLPP
Step 6 Set Allow EMLPP to Yes. Step 7 Click OK. A dialog box is displayed, as shown in Figure 18-3.
Issue 02 (2008-06-30)
18-9
18 eMLPP
Figure 18-3 Check the Compatibility of Parameters and Site Versions dialog box
Step 8 Click Yes to return to the previous dialog box, as shown in Figure 18-1. Step 9 Click OK to return to the Set Cell Attributes dialog box. Step 10 Click Finish. The eMLPP feature is configured. ----End
18.6.2 Verifying eMLPP

This describes how to verify eMLPP on the BSC6000 Local Maintenance Terminal.
Context
You can use the MML mode instead of GUI mode to check whether the license of eMLPP is used.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell, and then choose Configure Cell Attributes from the shortcut menu. The Configuring Cell Attributes dialog box is displayed. Step 2 Double-click the target cell in the Cell view list box to add it to the Selected cells list box. Step 3 Click Next. The Configuring Cells Attributes dialog box is displayed. Step 4 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 18-4.
18-10
Issue 02 (2008-06-30)
18 eMLPP
Issue 02 (2008-06-30)
18-11
18 eMLPP
l l
If Allow EMLPP shown in Figure 18-5 is set to Yes, eMLPP is enabled in the cell. If Allow EMLPP shown in Figure 18-5 is set to No, eMLPP is disabled in the cell.
----End
18.6.3 Disabling eMLPP

This describes how to disable eMLPP on the BSC6000 Local Maintenance Terminal.
Context
If you want to disable eMLPP in the entire BSC, apply for the license that does not support eMLPP. To activate the license, refer to Activating the BSC License. If you want to disable eMLPP in a cell, modify the cell attributes. The procedure is as follows:
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell, and then choose Configure Cell Attributes from the shortcut menu. The Configuring Cell Attributes dialog box is displayed.
18 eMLPP
Step 2 Double-click the target cell in the Cell view list box to add it to the Selected cells list box. Step 3 Click Next. The Configuring Cells Attributes dialog box is displayed. Step 4 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 18-6. Figure 18-6 Set Cell Attributes dialog box
Issue 02 (2008-06-30)
18-13
18 eMLPP
Step 6 Set Allow EMLPP to No. Step 7 Click OK. A dialog box is displayed, as shown in Figure 18-8.
18-14
Issue 02 (2008-06-30)
18 eMLPP
Figure 18-8 Check the Compatibility of Parameters and Site Versions dialog box
Step 8 Click Yes to return to the previous dialog box, as shown in Figure 18-6. Step 9 Click OK to return to the Set Cell Attributes dialog box. Step 10 Click Finish. The eMLPP feature is disabled. ----End

This lists the alarms and counters related to eMLPP.
Alarms
None.
Counters
After eMLPP is enabled, the call drop rate may increase because the high-priority MSs may preempt the resources of the low-priority MSs. The existing BSC6000 performance counters include the counters of preemption and queuing. Table 18-4 lists the counters related to eMLPP. Table 18-4 Counters related to eMLPP Counter R3134 R3135
Issue 02 (2008-06-30)
Description Failed Queuing Attempts due to Queue Overflow Queuing Requests

18 eMLPP
Counter R3136 R3137 R3138 H332He
Description Failed Queuings (Preemption) Failed Queuings (Queuing Timer Expired) Failed Queuings (Dynamic Adjustment Timed Out) Failed Outgoing External Inter-Cell Handovers (Clear Commands Sent By MSC) (Preemption) Failed Outgoing Inter-RAT Inter-Cell Handovers (Clear Commands Sent By MSC) (Preemption) Successful Channel Assignments in Immediate Assignment Procedure (SDCCH) Successful Channel Assignments in Immediate Assignment Procedure (TCHF) Successful Channel Assignments in Immediate Assignment Procedure (TCHH) Successful Channel Assignments in Immediate Assignment Procedure (TCHF) Successful Channel Assignments in Immediate Assignment Procedure (TCHH) Failed Queuing Attempts Call Drops due to Forced Handover (SDCCH) Call Drops due to Forced Handover (TCHF) (Signaling Channel) Call Drops due to Forced Handover (TCHF) (TCH) Call Drops due to Forced Handover (TCHH) (Signaling Channel) Call Drops due to Forced Handover (TCHH) (TCH)
H352He
R4110A
R4117A R4118A
R4117B R4118B
CR313C M305 M345 M315 M355 M325
18.8 References

l
18 eMLPP
3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP); Stage 2". 3GPP TR 21.905: "3G Vocabulary". 3GPP TS 22.101: "UMTS Service Principles". 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 23.068: "Voice Group Call Service (VGCS) Stage 2". 3GPP TS 23.069: "Voice Broadcast Service (VBS) Stage 2". 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 25.431: "UTRAN Iu Interface RANAP Signalling". 3GPP TS 24.008: "Core Network Protocols - Stage 3".
l l l
l l l l
l l l
Issue 02 (2008-06-30)
18-17
19 GPRS
19
About This Chapter
19.2 Availability This lists the NEs and software required for the implementation of GPRS.
GPRS
19.1 Overview This introduces the general packet radio service (GPRS), which is a type of end-to-end packet switched (PS) services based on the GSM technology.
19.3 Impact This describes the impacts of GPRS on system performance and on other features. 19.4 Technical Description This describes the technical aspects of GPRS, such as the media access control (MAC) mode, radio link control (RLC) modes, network operation modes, and quality of service (QoS). 19.5 Capabilities This describes the capabilities of the GPRS network in the cases of built-in PCUs and external PCUs. 19.6 Implementation The implementation of GPRS involves configuring and verifying GPRS in two scenarios, namely, GPRS with internal PCUs and GPRS with external PCUs. 19.7 Maintenance Information This describes the alarms and counters related to GPRS. 19.8 References This describes the reference documents related to GPRS.
Issue 02 (2008-06-30)
19-1
19 GPRS
19.1 Overview
This introduces the general packet radio service (GPRS), which is a type of end-to-end packet switched (PS) services based on the GSM technology.
Definition
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
GPRS makes full use of the existing GSM network infrastructure. GPRS enables efficient use of radio resources. GPRS provides a radio access rate of up to 171.2 kbit/s. GPRS supports standard interfaces.
GPRS provides abundant packet services, for example, mobile Internet access, e-commerce (such as e-bank and e-currency), cluster management, remote control/remote measurement, booking system (for hotels, theatres, and airplanes), and group call based services (such as stock information publication).
Purposes
GPRS provides MSs with high-speed packet services. It prolongs the life expectancy of a GSM system, enhances the utilization of radio resources, and extends the third generation mobile communication market. GPRS can smoothly evolve to the 3G network and thus effectively protect the investment.
Terms
Terms PTCCH Definition PTCCH stands for Packet Timing advanced Control Channel. The PTCCH/U is used by 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. PoC stands for Push-to-talk over Cellular. Compared with the services provided by commonly used mobile phones, the PoC enables a single person to talk to several persons one to one.
PoC
19-2
Issue 02 (2008-06-30)
19 GPRS

Acronyms and Abbreviations ARP BC BSN BSSGP BVC CCCH FR GBR GMSK GPRS GSN IP MAC NS NSE NSVC NSVL PACCH PDCH PCCCH PCIC PDP PFC PFM PoC PTCCH PTMBVC PTPBVC Full Spelling Allocation/Retention Priority Bearer Channel Block Sequence Number Base Station System GPRS Protocol BSSGP Virtual Connection Common Control Channel Frame Relay Guaranteed Bit Rate Gaussian Minimum Shift Keying General Packet Radio Service GPRS Support Node Internet Protocol Media Access Control Network Service Network Service Entity Network Service Virtual Connection Network Service Virtual Link Packet Associated Control Channel Packet Data Channel Packet Common Control Channel Packet Circuit Identity Code Packet Data Protocol Packet Flow Context Packet Flow Modify Push-to-talk over Cellular Packet Timing advanced Control Channel Point-To-Multipoint BSSGP Virtual Connection Point-To-Point BSSGP Virtual Connection
Issue 02 (2008-06-30)
19-3
19 GPRS
Acronyms and Abbreviations PVC QoS RA RLC SIGBVC TA TAI TBF THP TLLI USF
Full Spelling Permanent Virtual Connection Quality of Service Routing Area Radio Link Control Signal BSSGP Virtual Connection Timing Advance Timing Advance Index Temporary Block Flow Traffic Handling Priority Temporary Logical Link Identity Uplink State Flag
19.2 Availability
This lists the NEs and software required for the implementation of GPRS.
NEs Involved
Table 19-1 lists the NEs involved in GPRS. Table 19-1 NEs involved in GPRS MS
NOTE
BTS
BSC
MSC -
PCU
SGSN
GGSN
HLR
Software Releases
Table 19-2 lists the versions of GBSS products that support GPRS.
19-4
Issue 02 (2008-06-30)
19 GPRS
Table 19-2 GBSS products and software versions Product BSC BTS BSC6000 BTS30 BTS312 BTS3012A BTS3001C BTS3002C BTS3002E BTS3006C BTS3012 DTRU QTRU BTS3012 AE DTRU QTRU Version V900R008C01 and later releases All releases All releases All releases All releases All releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C01 and later releases
BTS3900 GSM BTS3900A GSM DBS3900 GSM
Miscellaneous
None.
19.3 Impact
This describes the impacts of GPRS on system performance and on other features.

Adding packet services to the BSC decreases the performance of voice services. The detailed reasons are as follows:
l
Packet services use the speech channels on the Um interface. Thus, the capability to carry voice services is decreased. On the Abis interface, idle timeslots need to be allocated for the CS-3 or CS-4 coding mode of packet services. Thus, the number of TRXs over E1 is decreased.

The parameter EDGE Support can be set only after the parameter GPRS Support is set.
19 GPRS

This describes the technical aspects of GPRS, such as the media access control (MAC) mode, radio link control (RLC) modes, network operation modes, and quality of service (QoS). 19.4.1 GPRS Networking This describes the network topologies of GPRS. By introducing GPRS support nodes (GSNs) and pack control units (PCUs) and upgrading the software, the GSM system can implement GPRS. The network topologies are categorized into two types: one with built-in PCUs and the other with external PCUs. 19.4.2 MAC Mode The Medium Access Control (MAC) mode is a dynamic allocation mode. It multiplexes channel resources by allocating the uplink radio block through the USF of the downlink radio block. 19.4.3 RLC Mode This describes the RLC acknowledged mode and the RLC unacknowledged mode, both of which are supported by the BSS. 19.4.4 Network Operation Mode This describes three network operation modes, which are used by the GPRS network to coordinate the paging of voice services and packet services. 19.4.5 Quality of Service This describes the flexible QoS mechanism provided by GPRS for different services and different subscribers. 19.4.6 TBF Assignment This describes the assignment of temporary block flow (TBF). When the network or an MS requests the establishment of TBF to transmit data, the GPRS network assigns channel resources for data transmission or refuses the request based on the network resources status and the multislot capability of the MS. 19.4.7 GPRS/GSM Paging Function This describes packet paging and paging co-ordination in the GPRS/GSM system. 19.4.8 GPRS Timing Advance This describes the timing advance (TA) procedure, which is used to extract the correct TA value so that the MS can transmit radio data blocks in the uplink. 19.4.9 Flow Control This describes GPRS flow control. The PCU provides data flow control over the downlink and periodically reports relevant parameters to the SGSN. 19.4.10 Dynamic Conversion Between TCH and PDCH This describes the dynamic conversion between Traffic Channel (TCH) and Packet Data Channel (PDCH). To reduce the impact of GPRS services on GSM voice services, Huawei GPRS BSS supports the dynamic conversion between TCH and PDCH. 19.4.11 Packet Access This describes the packet access technology. The RLC/MAC layer of an MS initiates a packet channel request when the MS needs to transmit data. 19.4.12 Packet System Information
19-6
Issue 02 (2008-06-30)
19 GPRS
Packet system information refers to the packet system information on the Broadcast Control Channel (BCCH), Packet Broadcast Control Channel (PBCCH), and Packet Associated Control Channel (PACCH). 19.4.13 Measurement Reports This describes UL measurement reports supported by GPRS. 19.4.14 Performance Management Performance management refers to statistical measurement and analysis of network performance, through which network problems can be located and solved. Performance management ensures that the network is operating normally. 19.4.15 Power Control This describes open loop power control performed by the BSS on the GPRS packet service. 19.4.16 Coding Schemes The GPRS coding schemes consist of CS-1, CS-2, CS-3, and CS-4. 19.4.17 Gb Interface The built-in PCU is a component of the BSC. The external interfaces of the BSC include the Gb interface but exclude the Pb interface. 19.4.18 Pb Interface This describes the Pb interface, which is a non-standard internal interface between the PCU and the BSC. The implementation of the Pb interface varies from manufacturer to manufacturer.
19.4.1 GPRS Networking

This describes the network topologies of GPRS. By introducing GPRS support nodes (GSNs) and pack control units (PCUs) and upgrading the software, the GSM system can implement GPRS. The network topologies are categorized into two types: one with built-in PCUs and the other with external PCUs. The components of the GPRS network are as follows:
l l l l l l l l l l l
Serving GPRS support node (SGSN) Gateway GPRS support node (GGSN) SGSN OM center (OMC-G) Border gateway Charging gateway HLR/AUC PCU BSC BTS DNS Firewall
Huawei BSC supports both built-in PCU and external PCU. GPRS features flexible networking modes. It can be deployed according to actual requirements.
NOTE
Built-in PCU and external PCU cannot coexist.
Issue 02 (2008-06-30)
19-7
19 GPRS
When built-in PCUs are used for networking, the number of GDPUP boards and Gb interface boards is determined by GPRS traffic. Figure 19-1 shows the GPRS network topology with built-in PCUs. Figure 19-1 GPRS network topology with built-in PCUs
PSTN MSC Abis BTS BSC A Gs Gb Gb BTS BSC PDN SGSN Gr Gn GGSN Gc HLR
Abis
When external PCUs are used for networking, consider the following two cases:
l
When the GPRS traffic volume of each BSC is low, multiple BSCs can be connected to one PCU. When the GPRS traffic volume of a BSC is high and one PCU cannot meet service requirements, multiple PCUs can be connected to the BSC.
Figure 19-2 shows the GPRS network topology with external PCUs. Figure 19-2 GPRS network topology with external PCUs
PSTN MSC Abis BTS BSC A A Pb Abis Pb Pb PCU BTS BSC Pb Gb PDN Gb SGSN Gs Gr Gn GGSN Gc HLR
PCU
19-8
Issue 02 (2008-06-30)
19 GPRS
19.4.2 MAC Mode

The Medium Access Control (MAC) mode is a dynamic allocation mode. It multiplexes channel resources by allocating the uplink radio block through the USF of the downlink radio block. The BSS supports USF granularity 1 and USF granularity 4. USF granularity 4 is supported by default. You can disable USF granularity 4 by setting the Support USF Granularity 4 Switch parameter.
l
When the BSS supports USF granularity 1, the MAC mode dynamically allocates uplink data blocks through the USF. When the BSS supports USF granularity 4, the MAC mode allocates multiplexing channel resources to the GPRS MS in the uplink and to the EGPRS MS in the downlink.
19.4.3 RLC Mode

This describes the RLC acknowledged mode and the RLC unacknowledged mode, both of which are supported by the BSS.
RLC Acknowledged Mode

In RLC acknowledged mode, RLC data blocks can be retransmitted. The sender numbers RLC data blocks with block serial numbers (BSNs) for retransmission and reassembly. The receiver sends packet ACK/NACK messages to request the retransmission of RLC data blocks.
RLC Unacknowledged Mode

In RLC unacknowledged mode, RLC data blocks cannot be retransmitted. During the release of UL TBF, however, the last UL data block may be retransmitted. The sender numbers RLC data blocks with block serial numbers (BSNs) for reassembly. The receiver sends packet ACK/NACK message to request the transmission of other necessary control signals.
19.4.4 Network Operation Mode

This describes three network operation modes, which are used by the GPRS network to coordinate the paging of voice services and packet services.
Network Operation Mode I

Network operation mode I supports the paging co-ordination function through the Gs interface. For a GPRS-attached MS, the network sends PS paging messages and CS paging messages on one channel. Thus, the MS needs to monitor only one paging channel. If a PDCH is assigned to the MS, the network can send the MS CS paging messages on the PDCH.
Network Operation Mode II

Network operation mode III does not support the paging co-ordination function. All paging messages are transmitted on PCHs. MSs need to monitor only PCHs. Even if an MS is assigned with a PDCH, the MS monitors PCHs for CS paging messages.
Issue 02 (2008-06-30)
19-9
19 GPRS
Network Operation Mode III

Network operation mode III does not support the paging co-ordination function. All CS paging messages are transmitted on PCHs. If a cell is configured with PCCCHs, PS paging messages are transmitted on PPCHs, and MSs need to monitor both PCHs and PPCHs. Table 19-3 lists the channels over which the network sends CS paging messages and PS paging messages to MSs in these network operation modes. Table 19-3 Network operation modes Network Operation Modes CS Paging Message GPRS Paging Message Combined Paging
PPCH PCH PACCH
PPCH PCH No PCH PPCH PCH
Yes
PCH PCH PCH
No No
The network operation mode can be set through the parameter Network Operation Mode. If the GPRS network is not configured with the Gs interface and PCCCHs, set Network Operation Mode to Network Operation Mode .
19.4.5 Quality of Service

This describes the flexible QoS mechanism provided by GPRS for different services and different subscribers.
PS QoS
The BSC processes different services according to their priorities. The guaranteed bit rate (GBR) service has the highest priority, then the allocation/retention priority (ARP) service and the traffic handling priority (THP) service, and finally other services.
l
GPRS supports the GBR, and thus it can support the streaming service and push-to-talk over cellular (PoC) service. Whether to support the streaming QoS can be set through the parameter Support Gbr Qos.
For an MS supporting the GBR, the allocation of resources is based on the bandwidth negotiated between network and MS. For an MS not supporting the GBR, the allocation of resources is performed in best effort (BE) mode.
The PCU dynamically allocates Um interface resources to the MS based on the radio environment so that the bandwidth of the MS is permanently equal to or greater than the GBR. To guarantee the real-time performance of the PoC service, Min. GBR for POC Service and Max. GBR for POC Service are used for providing the required bandwidth,
19 GPRS
and Transmission Delay of POC Service is used for controlling the transmission delay. When there are no sufficient Um resources, the PCU notifies the SGSN of the situation.
l
GPRS supports the ARP and THP, and thus it can support the interactive service. In the case that the Packet Flow Modify (PFM) procedure is activated, if the PCU can obtain the correct packet flow context (PFC) and the service is of interactive class, then
If the PFC includes the ARP field but excludes the THP field, the processing priority is determined by the ARP field. The priority may be 1, 2, or 3. The processing capabilities for different ARP priorities can be set through ARP1 Priority Weight, ARP2 Priority Weight, and ARP3 Priority Weight. If the PFC includes the THP field but excludes the ARP field, the processing priority is determined by the THP field. The priority may be 1, 2, or 3. The processing capabilities for different THP priorities can be set through THP1 Priority Weight, THP2 Priority Weight, and THP3 Priority Weight. If the PFC includes both the ARP field and the THP field, the processing priority is determined by the two fields. In any other cases, the BE mode is used.
The background service has the lowest priority. The weight of the bandwidth that can be occupied by this service is set through Background Service Priority Weight.
Subscriber QoS
Whether to provide different QoS schemes for different subscribers can be set through Support QoS Optimize. When registering with the GPRS network, the user can reserve the default QoS script. During a packet service, the MS can request a QoS mechanism different from the default one. The negotiation procedure is as follows: 1. 2. 3. 4. In the Packet Data Protocol (PDP) context activation procedure, the MS negotiates the QoS script with the network. During the negotiation, the MS requests a value for each QoS attribute, including the default value stored in the HLR for registration. The network assigns a value for each QoS attribute based on available GPRS resources. The network provides appropriate resources to support the negotiated QoS.
Each PDP context is associated with an independent network QoS script. QoS is defined by the following attributes:
l
Priority level The GPRS network defines priority levels 1, 2, and 3. For uplink transmission, priority levels 1, 2, and 3 map to radio priorities 2, 3, and 4 respectively. The priority level of radio interface signaling is 1.
Delay class There are four delay classes: 1, 2, 3, and 4. The network should support at least delay class 4, where the best effort mode is used.
Reliability class As listed in Table 19-4, the reliability class is determined by the GTP, LLC and RLC transmission modes together.
Issue 02 (2008-06-30)
19-11
19 GPRS
Table 19-4 Requirements of the reliability class for protocol layers Reliab ility Class 1 GTP Mod e Ackn owled ged mode Unac knowl edged mode Unac knowl edged mode Unac knowl edged mode Unac knowl edged mode LLC Frame Mode Ackno wledge d mode Ackno wledge d mode Unack nowle dged mode Unack nowle dged mode Unack nowle dged mode LLC Protecti on Mode Protecte d mode
RLC Mode Acknow ledged mode Acknow ledged mode Acknow ledged mode Unackno wledged mode Unackno wledged mode
Type of Service Non-real-time services, sensitive to error, data loss not allowed
Protecte d mode
Non-real-time services, sensitive to error, occasional data loss allowed Non-real-time services, sensitive to error, data loss able to be processed Real-time services, sensitive to error, data loss able to be processed Real-time services, insensitive to error, data loss able to be processed
Protecte d mode
Protecte d mode
Unprote cted mode
For real-time services, the QoS configuration has requirements for delay class and throughput class. The format of an LLC data frame is Header + Information + FCS. In protected mode, FCS protects H0eader and Information. In unprotected mode, FCS protects Header and the data contained in the first byte of Information.
l
Peak throughput class Peak throughput refers to the number of bytes per second at reference points R and Gi. The peak throughput class defines the maximum data rate in each PDP context. The duration of the peak throughput, however, is determined by the data capability of the MS and the conditions of available radio resources. Peak throughput has no correlation with delay class. The delay class defines the transmission delay of each packet on the GPRS network. There are nine peak throughput classes, as listed in Table 19-5. Table 19-5 Peak throughput classes Peak Throughput Class 1 2 Peak Throughput (Unit: Bytes/Second) 1000 (8 kbit/s) 2000 (16 kbit/s)
19-12
Issue 02 (2008-06-30)
19 GPRS
Peak Throughput Class 3 4 5 6 7 8 9
Peak Throughput (Unit: Bytes/Second) 4000 (32 kbit/s) 8000 (64 kbit/s) 16000 (128 kbit/s) 32000 (256 kbit/s) 64000 (512 kbit/s) 128000 (1024 kbit/s) 256000 (2048 kbit/s)
Mean throughput class Mean throughput refers to the number of bytes per hour at reference points R and Gi. The measurement period include the idle time when burst applications do not transmit data. Mean throughput defines the expected mean rate of the data transmitted through the GPRS network during the period of the PDP context activation. For convenience, even if the network can provide higher throughput, it limits the mean throughput of a subscriber to a certain class. The Best Effort class is negotiated according to the requirement of an MS and according to available radio resources. There are 19 mean throughput classes, as listed in Table 19-6. Table 19-6 Mean throughput classes Mean Throughput Class 1 2 3 4 5 6 7 8 9 10 11 12 13 14 Mean Throughput (Bytes/Hour) 100 (about 0.22 bit/s) 200 (about 0.44 bit/s) 500 (about 1.11 bit/s) 1000 (about 2.2 bit/s) 2000 (about 4.4 bit/s) 5000 (about 11.1 bit/s) 10000 (about 22 bit/s) 20000 (about 44 bit/s) 50000 (about 111 bit/s) 100000 (about 0.22 kbit/s) 200000 (about 0.44 kbit/s) 500000 (about 1.11 kbit/s) 1000000 (about 2.2 kbit/s) 2000000 (about 4.4 kbit/s)
Issue 02 (2008-06-30)
19 GPRS
Mean Throughput Class 15 16 17 18 31
Mean Throughput (Bytes/Hour) 5000000 (about 11.1 kbit/s) 10000000 (about 22 kbit/s) 20000000 (about 44 kbit/s) 50000000 (about 111 kbit/s) Best effort
NOTE
Portfolios of different values of the attributes form various QoS scripts. One GPRS network supports only a subset of the QoS portfolios.
19.4.6 TBF Assignment

This describes the assignment of temporary block flow (TBF). When the network or an MS requests the establishment of TBF to transmit data, the GPRS network assigns channel resources for data transmission or refuses the request based on the network resources status and the multislot capability of the MS.
l
The network performs TBF assignment on Common Control Channel (CCCH), Packet Associated Control Channel (PACCH), or Packet Common Control Channel (PCCCH). TBF assignment is classified into uplink TBF assignment and downlink TBF assignment.
When an MS requests TBF establishment for data transmission, the network sends an Immediate Assignment message over the CCCH or a Packet Uplink Assignment message over the PCCCH to assign radio resources to the MS. When the MS requests establishment of an uplink TBF during TBF data transmission over the downlink, the network assigns a packet uplink channel to the MS through the PACCH. The MS transmits data on the assigned channel. When the network needs to establish a TBF for downlink data transmission, the network sends an Immediate Assignment message over the CCCH or a Packet Uplink Assignment message over the PCCCH to assign radio resources to the MS. When the MS transmits uplink TBF data, the network can assign a packet downlink channel to the MS through the PACCH if the network requests establishment of a TBF for downlink data transmission. The MS transmits data on the assigned channel. When channel resources are insufficient or for other reasons, the network can reject a request for TBF establishment.
The network assigns resources on different channels based on the CCCH or PCCCH configuration. In addition, the network 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 Without TBF Establishment. The BSS supports the following assignment modes:

Packet uplink resource assignment over a PACCH Packet downlink resource assignment over a PACCH Uplink immediate assignment for TBF establishment over a CCCH Downlink immediate assignment for TBF establishment over a CCCH
The parameters and timers involved in TBF assignment are as follows:


l l l l l l l l l
19 GPRS
T3192 T3168 BS_CV_MAX Release Delay of Non-extended Uplink TBF(ms) Inactive Period of Extended Uplink TBF(ms) Release Delay of Downlink TBF(ms) N3101_MAX N3103_MAX N3105_MAX
19.4.7 GPRS/GSM Paging Function

This describes packet paging and paging co-ordination in the GPRS/GSM system.
Packet Paging
In the GPRS system, the packet paging procedure is as follows: 1. 2. When the network needs to transmit downlink data to an MS, the SGSN initiates packet paging to locate the MS. The SGSN sends a paging request message to the PCU through the Gb interface. The PCU converts the paging request message into a Packet Paging Request message and sends it over the Um interface.
l
If a PCCCH is configured in the BSS, the Packet Paging Request message is sent over the PPCH. If no PCCCH is configured in the BSS, the PCU forwards the Packet Paging Request message to the BSC. Then, the BSC sends the message over a PCH.
3.
After receiving the Packet Paging Request message, the MS initiates an uplink TBF establishment procedure. Then, the MS sends a paging response packet in data format to the PCU through the Um interface. The PCU forwards the paging response packet to the SGSN. After receiving the paging response packet, the SGSN processes it and starts to transmit downlink data.
4.
Paging Co-ordination
In the GSM network, when a circuit paging reaches the MSC where the MS is located, the MSC determines the registered location area of the MS. Then, the MSC sends the circuit paging message to all the BSCs within the location area.
l
If the Gs interface between the SGSN and the MSC is available and the GPRS/GSM system operates in network operation mode I, then the CS paging messages of GSM services can be transmitted over GPRS packet channels. If the MS is attached to the GPRS, the CS paging messages are transmitted through the MSC to the SGSN and then through the Gb interface to the PCU. The PCU determines the channel to send the paging message. The principle for determining the channel is as follows:
If the MS is assigned with a packet dedicated channel, paging messages are sent over a PACCH.
Issue 02 (2008-06-30)
19 GPRS
If the MS is not assigned with a packet dedicated channel but a PCCCH is configured, paging messages are sent over a 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 CS paging message over the PCH.
If the Gs interface between the SGSN and the MSC is unavailable, the GPRS/GSM system can operate only in network operation mode II or III. In this case, the system sends CS paging messages over the CCCH. After receiving the circuit paging message, the MS accesses the network through the RACH to establish a circuit connection. The MS initiates the GPRS Suspend process to suspend the ongoing GPRS service. When the circuit connection is released, the MS resumes the GPRS service.
Huawei BSS supports the two paging modes.
19.4.8 GPRS Timing Advance

This describes the timing advance (TA) procedure, which is used to extract the correct TA value so that the MS can transmit radio data blocks in the uplink. The TA of the GPRS system is classified into two types:
l l
Initial TA estimation Continuous TA update
Initial TA Estimation
An initial TA value is estimated on the basis of a single access burst requesting a packet channel. Then, the network sends the TA to the MS through a Packet Uplink Assignment or a Packet Downlink Assignment message. Before receiving a new TA value, the MS uses this initial TA value for uplink data transmission.
Continuous TA Update
An MS in packet transfer mode should update TA continuously. The TA is transmitted over the Packet Timing advanced Control Channel (PTCCH) that is assigned to the MS.
l
For uplink packet transmission, the network sends the MS a Packet Uplink Assignment message to assign the timing advance index (TAI) and PTCCH. For downlink packet transmission, the network sends the MS a Packet Downlink Assignment message to assign the TAI and PTCCH.
TAI specifies a subchannel of PTCCH for the MS. In the uplink, the MS sends access bursts on the PTCCH subchannel specified by the TAI. The network extracts the TA value from the received access bursts. The network analyzes the TA value and determines a new TA value for each MS that performs continuous TA update over the PDCH. The new TA value is sent to the MS through a downlink signaling message on the PTCCH/D. The network can also send the new TA value to the MS through a Packet Power Control/Timing Advance or a Packet Uplink ACK/NACK message over the PACCH.
19 GPRS
19.4.9 Flow Control

This describes GPRS flow control. The PCU provides data flow control over the downlink and periodically reports relevant parameters to the SGSN. Because the physical media and transmission protocols on the Gb interface are different from those on the Um interface, the two interfaces have different data rates. Data rates on the Gb interface are greater than those on the Um interface. In addition, downlink data rates on the Um interface are subject to various factors, such as the multi-slot capability of the MS, radio signal quality, and available radio channels in the cell. Therefore, data rates are unstable and downlink flow control is required. When a cell is operational, the PCU initiates the flow control procedure. Based on the conditions of the radio packet channels in the cell, the PCU periodically reports the Bucket size and Bucket rate of the cell to the SGSN. In addition, the PCU reports the Bucket size and Bucket rate of the MS based on the radio resource utilization of the MS. Based on the reported parameters, the SGSN adjusts the downlink data rates of the cell and of each MS to achieve flow control.
NOTE
Bucket rate refers to the data rate.

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.
The GPRS system supports the downlink flow control of BSSGP virtual connection (BVC) and MS.
19.4.10 Dynamic Conversion Between TCH and PDCH

This describes the dynamic conversion between Traffic Channel (TCH) and Packet Data Channel (PDCH). To reduce the impact of GPRS services on GSM voice services, Huawei GPRS BSS supports the dynamic conversion between TCH and PDCH. In the GPRS BSS, channels are classified into fixed packet channels, voice channels, and dynamic channels, as listed below:
l
Fixed packet channels Fixed packet channels consist of PBCCHs, PCCCHs, PDCCH, and PDTCH. They are dedicated for packet services.
Voice channels Voice channels consist of TCHs, BCCHs, and SDCCHs. They are dedicated for voice services.
Dynamic channels Dynamic channels are initialized as TCHs. TCHs and PDCHs can be converted into each other dynamically.
The maximum number of PDCHs in a cell can be set through the parameter Maximum Ratio Threshold of PDCHs in a Cell. The capability of a cell to process packet services can be set through the parameters PDCH Uplink Multiplex Threshold and PDCH Downlink Multiplex Threshold. 1. When the number of packet service users exceeds Uplink Multiplex Threshold of Dynamic Channel Conversion or Downlink Multiplex Threshold of Dynamic Channel
Issue 02 (2008-06-30)
19 GPRS
Conversion, the PCU requests the BSC to convert some TCHs to PDCHs if there are idle TCHs. 2. When the voice service is busy, the BSC can convert some PDCHs into TCHs. In this process, voice services take priority over packet services to guarantee the QoS of voice services. The capability of packet services to preempt PDCHs can be set through the parameters Level of Preempting Dynamic Channel and Reservation Threshold of Dynamic Channel Conversion.
NOTE
When built-in PCUs are used for networking and the parameter Channel Type is set to TCH Full Rate, the BSC supports overall dynamic PDCHs. In this case, PDTCHs may not be configured.
19.4.11 Packet Access

This describes the packet access technology. The RLC/MAC layer of an MS initiates a packet channel request when the MS needs to transmit data. The types of packet access are as follows:
l l l l
Short Access One Phase Access Two Phase Access Single Block Without TBF Establishment For Short Access and One Phase Access, radio resources (such as the TFI, USF, and radio block position list) are assigned to an MS at a time. For a Two Phase Access request, only a radio block is assigned to the MS in the first phase. Then, the MS sends a Packet Resource Request message through the radio block. In the second phase, radio resources (such as the TFI, USF, and radio block position list) are assigned to the MS. Then, the MS starts to send data through the assigned radio resources. If less than eight RLC blocks are transmitted, the MS should request Short Access. The number of blocks should be calculated based on CS-1. If more than eight RLC blocks are transmitted and the requested RLC mode is the acknowledged mode, the MS should request either One Phase Access or Two Phase Access. If the data to be sent is a measurement report, the MS should request Single Block Without TBF Establishment.
The differences between these access types are as follows:

l
For different types of packet services, different access modes are used, as described below:
l
In addition, if the purpose of a packet access procedure is to send a Page Response, Cell Update, or Mobility Management, the MS can request One Phase Access or Two Phase Access. The Packet Channel Request message is an 8- or 11-bit access burst, which carries little information. The number of access burst bits can be set through the parameter Access Burst Type. The recommended setting is 8bit, because some MSs do not support the 11-bit access burst. The Packet Resource Request message is an RLC/MAC signaling packet in CS-1 encoding mode. It can carry relatively more information, including the temporary logical link identity (TLLI), multi-slot capability of the MS, and radio priority. This helps to assign appropriate resources to the MS. The capacity of a cell to allow packet access can be set through the parameter Packet Access Priority.
19 GPRS
19.4.12 Packet System Information

Packet system information refers to the packet system information on the Broadcast Control Channel (BCCH), Packet Broadcast Control Channel (PBCCH), and Packet Associated Control Channel (PACCH).
l
The packet system information on the BCCH includes SI3, SI4, SI7, SI8, and SI13.

SI3, SI4, SI7, and SI8 broadcast GPRS-supportive indicators. SI13 broadcasts GPRS-related parameters.
The packet system information on the PBCCH includes PSI1, PSI2, PSI3, PSI3bis, PSI4, and PSI5. The packet system information on the PACCH includes PSI1 and PSI13.
When the PBCCH is configured in a cell, the cell provides a timely broadcast of PSI1 over the PACCH to the MS that is in the transmission status. When the PBCCH is not configured in a cell, the cell provides a timely broadcast of PSI13 over the PACCH to the MS that is in the transmission status.
19.4.13 Measurement Reports

This describes UL measurement reports supported by GPRS. The BTS calculates the level and quality of UL signals from MS to BTS, sends them to the PCU through the inband signaling in the Abis TRAU frame, and generates a measurement report. Through the UL measurement report, the network side obtains the transmission quality for further adjustment of MS UL coding mode, cell reselection, and handover between overlaid subcell and underlaid subcell.
19.4.14 Performance Management

Performance management refers to statistical measurement and analysis of network performance, through which network problems can be located and solved. Performance management ensures that the network is operating normally. Performance management is basically known as performance data measurement, including performance data analysis and performance data management. Performance data management consists of data collection, data record, and data access. Performance management has the following functions: Analyzes the collected data Verifies the status of equipment and network Evaluates network availability Supports network planning and optimization Enhances network performance Ensures normal operating of the network GPRS performance management is to collect data during network operation, maintenance, or optimization, and to verify the physical or logical configuration of the network. In addition, based on the performance counters about the PS domain of the existing network, for example, number of uplink TBF establishment attempts, number of uplink GPRS TBF successful establishments, and number of downlink GPRS TBF successful establishments, potential problems in the existing network can be located and handled.
19.4.15 Power Control

This describes open loop power control performed by the BSS on the GPRS packet service. Open loop power control is based on the assumption that the uplink and the downlink have the same path loss and that the MS adjusts the output power based on the RX level.
19 GPRS
The procedure of open loop power control is as follows: 1. The BSS receives measurement reports from the MS through the channel specified by the parameter Measured Receive Power Level Channel. The setting of Measured Receive Power Level Channel can be BCCH or PDCH. The BSS performs open loop power control according to the measurement reports and the parameters Alpha Parameter and Initial Power Level.
2.
19.4.16 Coding Schemes

The GPRS coding schemes consist of CS-1, CS-2, CS-3, and CS-4. GPRS uses the Guassian Minimum Shift Keying (GMSK) modulation mode. Table 19-7 describes the relationship between coding schemes and data rates. Table 19-7 GPRS coding schemes and data rates Coding Scheme CS-1 CS-2 CS-3 CS-4 Rate (kbit/s) 8.0 12.2 14.4 20.2
Initially, the GPRS coding schemes are set through the Uplink Default CS Type and Downlink Default CS Type parameters. In GPRS application, whether the uplink and the downlink should be dynamically adjusted according to the quality of signal transmission is determined by the Uplink Fixed CS Type and Downlink Fixed CS Type parameters. If the uplink and the downlink should be dynamically adjusted, the GPRS coding schemes make adjustment based on the retransmission rate of Temporary Block Flow (TBF).
l
For uplink GPRS, if the quality of signal transmission is better and the retransmission rate of TBF is lower than the predefined threshold, the GPRS coding schemes are adjusted to high-rate coding schemes, which involve the following parameters:

Up TBF threshold From CS1 to CS2 Up TBF threshold From CS2 to CS3 Up TBF threshold From CS3 to CS4
For uplink GPRS, if the quality of signal transmission is worse and the retransmission rate of TBF is higher than the predefined threshold, the GPRS coding schemes are adjusted to low-rate coding schemes, which involve the following parameters:

Up TBF threshold From CS2 to CS1 Up TBF threshold From CS3 to CS2 Up TBF threshold From CS4 to CS3
For downlink GPRS, if the quality of signal transmission is better and the retransmission rate of TBF is lower than the predefined threshold, the GPRS coding schemes are adjusted to high-rate coding schemes, which involve the following parameters:
19-20

l
19 GPRS
Down TBF threshold From CS1 to CS2 Down TBF threshold From CS2 to CS3 Down TBF threshold From CS3 to CS4
For downlink GPRS, if the quality of signal transmission is worse and the retransmission rate of TBF is higher than the predefined threshold, the GPRS coding schemes are adjusted to low-rate coding schemes, which involve the following parameters:

Down TBF threshold From CS2 to CS1 Down TBF threshold From CS3 to CS2 Down TBF threshold From CS4 to CS3
19.4.17 Gb Interface
The built-in PCU is a component of the BSC. The external interfaces of the BSC include the Gb interface but exclude the Pb interface. 19.4.17.1 Description of the Gb Interface The Gb interface is a protocol-defined standard interface for interconnecting the BSS and the SGSN. 19.4.17.2 Management of the Gb Interface The management of the Gb interface involves the BSSGP Virtual Connection (BVC), Network Service Entity (NSE), Network Service Virtual Connection (NSVC), Network Service Virtual Link (NSVL), Bearer Channel (BC), and Permanent Virtual Connection (PVC). 19.4.17.3 Networking of the Gb Interface The networking of the Gb interface supports two modes, namely, Gb over FR and Gb over IP.
Description of the Gb Interface

The Gb interface is a protocol-defined standard interface for interconnecting the BSS and the SGSN.
Functions of the Gb Interface

The Gb interface enables the communication between SGSN and BSS, and performs the functions such as packet data transmission, flow control, and mobility management. The Gb interface is mandatory for GPRS networking.
Protocol Stack of the Gb Interface

Figure 19-3 shows the protocol stack of the Gb interface.
Issue 02 (2008-06-30)
19-21
19 GPRS
Figure 19-3 Protocol stack of the Gb interface

SGSN GMM/SM BSC BSSGP NS FR/IP LLC BSSGP NS FR/IP
Gb interface NS: Network Service layer LLC: Logical Link Control BSSGP: Base Station Subsystem GPRS Protocol GMM/SM: GPRS Mobility Management and Session Management
The protocol stack of the Gb interface is described as follows:

l
The physical layer of the Gb interface can use the FR protocol or the IP protocol in pointto-point direct connection or in RF or IP network connection. The physical layer serves the communication of the NS layer. The NS layer configures and manages the NSVCs or NSVLs, implements the routing of 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 transmits the LLC signaling and data in the uplink and downlink, performs flow control on the downlink data, and blocks, unblocks, and resets the BVC. The BSSGP layer complies with the GSM 08.18 protocol.
Management of the Gb Interface

The management of the Gb interface involves the BSSGP Virtual Connection (BVC), Network Service Entity (NSE), Network Service Virtual Connection (NSVC), Network Service Virtual Link (NSVL), Bearer Channel (BC), and Permanent Virtual Connection (PVC). A BC is specific to the frame relay (FR). The BC belongs to the physical layer and corresponds to the timeslot group of E1/T1. In the BSC, the Frame Relay Protocol Type parameter is set to determine the FR protocol used by the BC, and the Occupied Timeslot parameter is set to determine the bandwidth of the BC. The PVC is a logical transmission path. In a BC, the PVC is distinguished by the code Data Link Connection Identifier (DLCI). The NSE is a network service (NS) entity meaning end to end. One NSE managing multiple NSVCs or NSVLs can block, unblock, and reset the NSVCs or NSVLs.
l
For the bottom-layer link in FR transport, the Subnetwork Protocol Type parameter is set to Gb over FR. The NS layer serves the BSSGP layer through the NSVC. The NS layer transmits the BSSGP data on a valid NSVC, and then the NSVC corresponds to the PVC in the BC through Data Link Connection Identifier.
19-22

l
19 GPRS
For the bottom-layer link in IP transport, the Subnetwork Protocol Type parameter is set to Gb over IP and the IP Subnet Configure Mode parameter is specified as Static Configuration or Dynamic Configuration. The NS layer serves the BSSGP layer through the NSVC. The NS layer transmits the BSSGP data on a valid NSVL, and then the NSVL negotiates with the peer end through Local NSVL Identifier and Remote NSVL Identifier.
NOTE
When the Subnetwork Protocol Type parameter is set to Static Configuration, the BSC obtains the IP path of the SGSN by checking the configuration list of the remote NSVL. When the IP Subnet Configure Mode parameter is set to Dynamic Configuration, the BSC accesses Server IP Address through the specified Server UDP Port No. to obtain the signaling address and port number on the SGSN, and then through them to obtain the IP path of the SGSN.
The BVC is the communication path between the BSSGP entities. The entities at the equivalent layer of the BSSGP are Point-to-Point BSSGP Virtual Connection (PTPBVC), Point-toMultipoint BSSGP Virtual Connection (PTMBVC), and Signaling Permanent Virtual Connection (SIGPVC). The PTPBVC and PTMBVC transmit user data, and the SIGBVC transmits signaling messages. Each NSE is assigned an SIGBVC, and the BVC is related to the NSE through NSE Identifier.
Networking of the Gb Interface

The networking of the Gb interface supports two modes, namely, Gb over FR and Gb over IP. The FR and IP networking modes are defined in different protocols regarding the physical layer of the Gb interface.
l
When the physical layer of the Gb interface complies with the frame relay (FR) protocol, the BSC is configured with the GEPUG board. When the physical layer of the Gb interface complies with the Internet Protocol (IP), the BSC is configured with the GFGUG board.
FR Networking
In FR networking, the BSC and the SGSN can point-to-point directly connect to each other or communicate with each other through the FR network.
l
The Gb over FR point-to-point direct connection means that the BSC and the SGSN are directly connected without any intermediate networks. Generally, the BSC and the SGSN are used as the Data Terminal Equipment (DTE) and the Data Circuit-terminating Equipment (DCE) respectively, as shown in Figure 19-4. Figure 19-4 Gb over FR point-to-point direct connection
G E P U G
BSC
E1/T1
SGSN
l
Figure 19-5 shows the connection between BSC and SGSN through the FR network.
Issue 02 (2008-06-30)
19 GPRS
Figure 19-5 Gb over FR network connection

G E P U G
BSC
E1/T1
Fram Relay netwrok
E1/T1
SGSN
IP Networking
In IP networking, the BSC and the SGSN can directly connect to each other or communicate with each other through the IP network.
l
The Gb over IP direct connection means that the BSC and the SGSN are directly connected without any other IP networks. In this connection, a switch can be used to provide layer 2 (L2) switching services for the BSC and SGSN equipment, as shown in Figure 19-6. Figure 19-6 Gb over IP direct connection
G F G U G
BSC
FE/GE
SGSN
l
Gb over IP network connection means that the BSC and the SGSN are connected through the IP network. In this connection, the routers can be used to provide layer 3 (L3) routing services for the BSC and SGSN equipment, as shown in Figure 19-7. Figure 19-7 Gb over IP network connection
G F G U G
BSC
FE/GE Router Router
FE/GE
SGSN
Compared with FR networking, IP networking greatly increases the bandwidth on the Gb interface and saves operators' investment in network, operation, and maintenance.
19.4.18 Pb Interface
This describes the Pb interface, which is a non-standard internal interface between the PCU and the BSC. The implementation of the Pb interface varies from manufacturer to manufacturer. 19.4.18.1 Description of the Pb Interface This describes the functions and protocol stack of the Pb interface. 19.4.18.2 Management of the Pb Interface
19 GPRS
This describes the Pb interface management, which consists of trunk circuit management, packet radio resource management, packet service access support, transmission management, and Pb interface signaling links (PbSL) management. 19.4.18.3 Features of the Pb Interface This describes the features of the Pb interface. The Pb interface supports dynamic channel conversion between packet services and voice services. It also enables the MS to request access channels over a CCCH.
Description of the Pb Interface

This describes the functions and protocol stack of the Pb interface.
Functions of the Pb Interface

Various shared resources such as cells, packet channels, E1 trunks, and system information are managed on the Pb interface. The Pb interface also supports dynamic channel conversion. In addition, it allows an MS to access 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.
Protocol Stack of the Pb Interface

Figure 19-8 shows the protocol stack of the Pb interface. Figure 19-8 Protocol stack of the Pb interface
BSC PCU
RR PbIP LAPD Layer1 APP LAPD Layer1
Pb
The functions of the layers of the Pb interface are described as follows:

l
Layer 1 is a physical layer, complying with the G.703 standard. It is implemented through E1 sub-timeslots. The bandwidth of an E1 is divided into 128 sub-timeslots of 16 kbit/s, of which four sub-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 transmission service from the physical layer and provides connection-oriented or connectionless services to layer 3. In short, the purpose of LAPD is to connect layer 3 to layer 1. LAPD uses the transmission function of layer 1 to provide reliable end-to-end transmission for layer 3 entities. Layer 3 is the key part of the Pb interface. It consists of a series of self-defined signaling messages. Layer 3 manages various GPRS resources between the PCU and the BSC and
Issue 02 (2008-06-30)
19 GPRS
supports dynamic channel conversion between voice services and packet services. In addition, layer 3 enables the MS to initiate access procedures and enables the network to send speech paging messages on CCCHs.
NOTE
The standard LAPD protocol is used at layer 2. Therefore, the Pb interface protocol often refers to the signaling flow at layer 3.
Management of the Pb Interface

This describes the Pb interface management, which consists of trunk circuit management, packet radio resource management, packet service access support, transmission management, and Pb interface signaling links (PbSL) management.
Trunk Circuit Management

The purpose of trunk circuit management is to ensure the consistency between the status of trunk circuits on the BSC side and that on the PCU side. Thus, when requesting a PDCH or dynamic channel conversion, the PCU can be assigned with an idle circuit to ensure data services. The procedures related to the circuit resource management on the Pb interface are as follows:
l l l l
Circuit Block procedure Circuit Unblock procedure Uninstall Circuit procedure Reset Circuit procedure
These procedures are triggered by device (over the Pb interface) status change or OMC maintenance. The following rules are used to manage trunk circuits over the Pb interface to simplify the design:
l l l
The BSC records only the maintenance status of the circuits. All circuit management messages are sent by the BSC. Circuits can be blocked, unblocked, and reset on the PCU side. The status of the circuits on the BSC side is not affected. If circuit maintenance is disabled on the PCU side, the BSC cannot unblock a circuit that is blocked on the PCU side.
NOTE
The procedures of Circuit Block/Unblock, Uninstall Circuit, and Reset Circuit are almost the same as those on the A interface. The only difference is that the MSC is changed to the PCU and the trunk circuit identity code (CIC) on the A interface is changed to the trunk packet circuit identity code (PCIC) on the Pb interface.
Radio Resource Management

Radio resource management on the Pb interface refers to the management of the radio resources related to only packet services.
l
All the information on radio resources is configured on the BSC6000 Local Maintenance Terminal. Radio resource information on the PCU is obtained from the BSC. The whole procedure consists of three parts:
The cells on the BSC side and those on the PCU side are reset.
19-26

l
19 GPRS
The packet radio configuration is sent by the BSC to the PCU. Packet system information is broadcast.
Circuit services and packet services share radio resources, which are allocated on demand. Circuit services take priority over packet services in the allocation. Allocation on demand enables the BSC to assign radio resources between circuit services and packet services in real time based on actual requirements. This means a dynamic conversion between TCHs and PDCHs. The channel conversion procedures on the Pb interface are classified into the following types:
If the packet channels are insufficient for packet services, the PCU requests the BSC to convert some TCHs into PDCHs. 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 BSC finds that TCHs are insufficient for circuit services, it requests the PCU to convert some PDCHs into TCHs. This requirement is mandatory to ensure the QoS of circuit services. When the PCU finds that too many PDCHs are idle, it automatically converts some PDCHs back to TCHs. This ensures the QoS of circuit services.
The BSC is responsible for assigning TCHs, and the PCU is responsible for assigning PDCHs. After a PDCH is assigned to the PCU, the allocation and release of the PDCH is determined by the PCU. The BSC is responsible for the allocation and release of TCHs.
The status of radio resources on the BSC side should be consistent with that on the PCU side. To ensure the consistency, the BSC needs to notify the PCU of the change of the BTS and the impact of OMC operation on radio resource status. For example, if a certain packet channel is blocked through the OMC, the BSC should notify the PCU to update the status of the channel.
Packet Service Access Support

System Information 13 should be broadcast on the BCCH to support GPRS. In addition, System Information 3 and 7 should be modified to contain relevant GPRS information such as GPRS Indicator. Based on various system information, an MS decides whether and how to access the serving cell to request packet services. If no PCCCH is configured in the serving cell, the MS requests packet services through a CCCH. The MS can request packet services through one or more of the following procedures:
l l l
MS originated packet access MS terminated packet access Packet service suspension and restoration of an MS in class-B mode
Transmission Management
When converting a TCH into a PDCH, the BSC connects the trunk circuits on the Abis interface with those on the Pb interface. During the transmission of packet data, the BSC transmits packets between the BTS and the PCU. When converting a PDCH into a TCH, the BSC needs to disconnect the trunk circuits. In general, each PDCH corresponds to a 16 kbit/s timeslot. During data transmission, if the PCU finds that the transmission quality is satisfied, it can use a more efficient coding mode, such as
19 GPRS
CS-3 or CS-4. Meanwhile, the BSC needs to dynamically assign another 16 kbit/s timeslot to the PDCH. Therefore, the PDCH corresponds to a 32 kbit/s timeslot.
PBSL Management
The PCU-BSC signaling links (PBSLs) are LAPD links. 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 the release of the resources of the cell on both sides of the Pb interface. Code errors may occur during transmission. Thus, the Pb interface has error handling function. Messages that have error codes are omitted and confusion messages are transmitted selectively.
Features of the Pb Interface

This describes the features of the Pb interface. The Pb interface supports dynamic channel conversion between packet services and voice services. It also enables the MS to request access channels over a CCCH. 1. Supporting dynamic channel conversion between packet services and voice services Huawei GPRS BSS classifies channel attributes into three types: fixed packet channels, voice channels, and dynamic channels.
l
Fixed packet channels Fixed packet channels include PBCCHs and PCCCHs. They are dedicated for packet services.
Voice channels Voice channels consist of TCHs, BCCHs, and SDCCHs. They are dedicated for voice services.
Dynamic channels Dynamic channels are initialized as TCHs. TCHs and PDCHs can be converted into each other dynamically.
When the packet traffic volume is high and the speech traffic volume is low, the PCU requests the BSC to convert some TCHs into PDCHs. When the speech traffic volume is high, the BSC requests the PCU to convert some PDCHs into TCHs. In this process, voice services take priority over packet services to ensure the QoS of voice services. 2. Supporting the MS to request access channels on a CCCH The BTS cannot identify an access request message sent by the MS on a CCCH. Therefore, the BSC needs to analyze the request message from the MS. 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 sending the message to the BTS. Therefore, the procedure for processing the access request of an MS over the CCCH is different from that over a PCCCH. The technique of an MS that supports the access on a CCCH is relatively simple. Thus, the cost of the MS is low. These MSs are commonly used during the initial deployment stage of GPRS services. The Pb interface enables the PCU to support two different MS access modes. Thus, the capability of the system to adapt to various MSs is greatly improved. 3. Maintaining the consistency of various resources and data between the BSC and the PCU Because the PCU and the BSC are located at two places, the data of various shared resources (such as cells, channels, PCIC trunks, and system information parameters) should be
19 GPRS
consistent. This is another major function of the Pb interface. The functions of the Pb interface involve the maintenance and management of some resources, such as the cell parameter configuration, cell restart, channel block/unblock, PCIC block/unblock, PCIC restart, packet system information parameter configuration, and regular check on all the resource data. 4. Sending speech paging messages When network operation mode I is used and no PCCCH is configured, the MSC sends a speech paging message through the Gs interface and Gb interface. After receiving the speech paging message, the PCU sends it to the BSC through the Pb interface. Then, the BSC sends the speech paging message on a CCCH. 5. Supporting GPRS suspension and recovery messages sent by Class-B MSs An MS in class-B mode cannot simultaneously perform voice services and packet services. Therefore, after conversion from a packet service to a voice service, the MS sends a GPRS suspension request to the BSC. Then, the BSC sends the request to the PCU through the Pb interface for processing. After the voice service is complete, the BSC sends a GPRS service recovery request to the PCU through the Pb interface. The process of messages of this kind improves the system capability to support Class-B MSs. 6. Supporting two transmission modes In addition to terrestrial transmission, the Pb interface supports satellite transmission. If either of the two modes, you can install the BSC and the PCU in different equipment rooms. This solves the problem of long distance transmission in which one PCU is connected to multiple BSCs.
19.5 Capabilities
This describes the capabilities of the GPRS network in the cases of built-in PCUs and external PCUs.
Capabilities (with Built-in PCUs)

The capabilities of the GPRS network with built-in PCUs are as follows:
l l l
The BSS in full configuration supports a maximum of 9 (= 8 + 1) GDPUPs. Each GDPUP supports a maximum of 1,024 cells. Each GDPUP supports a maximum of 1,024 activated PDCHs. All the channels can use the CS-4 encoding mode. The BSS supports a maximum of 15,360 PDCHs. The BSS supports a maximum of 8,192 activated PDCHs. All the channels can use the CS-4 encoding mode. The Gb interface provides a maximum of 512 Mbit/s throughput. A single MS can use a maximum of 4 uplink PDCHs. A single MS can use a maximum of 5 downlink PDCHs. The system supports a maximum of 8 GFGUGs/GEPUGs pairs.
l l
l l l l
Capabilities (with External PCUs)

The capabilities of the GPRS network with external PCUs are as follows:
19 GPRS
l l l l
Each BSC supports a maximum of 256 E1s on the Pb interface. Each GMPS/GEPS subrack supports a maximum of 64 E1s on the Pb interface. Each GEIUP supports 32 E1s on the Pb interface. Each GOIUP provides one STM-1 optical port and 63 E1s.
19.6 Implementation
The implementation of GPRS involves configuring and verifying GPRS in two scenarios, namely, GPRS with internal PCUs and GPRS with external PCUs. 19.6.1 Configuration Principles (with Built-in PCU) GPRS must adhere to the related configuration principles. 19.6.2 Configuring GPRS (with Built-in PCU) This describes how to configure GPRS on the BSC6000 Local Maintenance Terminal. 19.6.3 Verifying GPRS (with Built-in PCU) GPRS with built-in PCUs can be verified on the BSC6000 Local Maintenance Terminal. 19.6.4 Configuration Principles (with External PCU) GPRS must adhere to the related configuration principles. 19.6.5 Configuring GPRS (with External PCU) This describes how to configure GPRS on the BSC6000 Local Maintenance Terminal. 19.6.6 Verifying GPRS (with External PCU) GPRS with external PCUs can be verified on the BSC6000 Local Maintenance Terminal.
19.6.1 Configuration Principles (with Built-in PCU)

GPRS must adhere to the related configuration principles. When the built-in PCUs are configured, the Gb interface adheres to the following principles:
l l l
One BSC can be connected to multiple SGSNs. One BSC can be configured with multiple NSEs. One SGSN corresponds to multiple NSEs in the BSC, but all the NSVCs and PTPBVCs in one NSE can serve only one SGSN. In FR transport mode, the NSVC Identifier of the BSC is the same as that of the SGSN. One cell corresponds to one PTPBVC. One BSC can belong to the cells of different SGSNs. The cell in one routing area (RA) must belong to the same NSE, that is, the same BSC and SGSN. If the BSC and the SGSN are point-to-point directly connected, one BC can bind as many timeslots on the E1 link as possible. The number of NSVCs configured on one BC is not specified. It is recommended that on one BC the number of NSVCs serving the same NSE should not be larger than two. This ensures that one group of NSVCs can be evenly distributed within the system.
l l l
19-30
Issue 02 (2008-06-30)
19 GPRS
19.6.2 Configuring GPRS (with Built-in PCU)

This describes how to configure GPRS on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The GPRS-supportive boards configured in the BSC are as follows:
When the Gb over FR transport mode is used, the GDPUP and GEPUG boards are configured in the BSC. When the Gb over IP transport mode is used, the GDPUP and GFGUG boards are configured in the BSC. In the BSC6000V900R008 Exceptional Commercial License Application Template, fill in the following information.
The license is applied and activated. To apply for and activate the license, do as follows: 1.
Fill in the number of resource items to be purchased in the Number of resources column corresponding to the resource item in the Resource control items column.

Maximum Number of PDCH Groups Activated If the Gb Over FR transport mode is used, maximum number of 64 kbit/s Gb links supported by GB OVER FR is involved. If the Gb Over FR transport mode is used, maximum number of 64 kbit/s Gb links supported by GB OVER IP is involved.
If the GPRS CS3/CS4 coding scheme is used, fill in 1 in the Number of resources column corresponding to Whether to activate CS34 in the Function control items column. Value 1 indicates that this function should be enabled.
2.
Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
Procedure
Step 1 Set the PCU type to built-in PCU. 1. 2. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Configure BSC Attributes from the shortcut menu. In the displayed dialog box, select the Basic Data tab page, as shown in Figure 19-9.
Issue 02 (2008-06-30)
19-31
19 GPRS
Figure 19-9 Configure BSC Attributes dialog box
3. 4.
Scroll down to set PCU Type to Inner. Click Finish to end the configuration.
Step 2 Configure the Gb links and related parameters.

l
When the Gb over FR transport mode is used on the Gb interface, do as follows: 1. Configure the NSE. For details, refer to Configuring the NSE. In this step, set Subnetwork Protocol Type to Gb Over FR and set the related parameters such as NSE Identifier, NSE Capability and NSE Status. 2. Configure the BC on the GEPUG board. For details, refer to Configuring the BC. In this step, set Occupied Timeslot and the related parameters such as Bearer Channel ID and Frame Relay Protocol Type. 3. 4. Configure the SGSN clock on the GEPUG board. For details, refer to Configuring the SGSN Clock. Configure the NSVC on the GEPUG board. For details, refer to Configuring the NSVC. In this step, set the parameters such as NSVC Identifier, Data Link Connection Identifier, NSE Identifier, and Bearer Channel ID, and adhere to the following principles:

NSE Identifier should correspond to NSE Identifier set in step 2.1. Bearer Channel ID should correspond to Bearer Channel ID set in step 2.2.
5.
Configure the PTPBVC. For details, refer to Configuring the PTPBVC. In this step, set the parameters such as BVC Identifier, NSE Identifier and Cell Name, and adhere to the following principles:
NSE Identifier should correspond to NSE Identifier set in step 2.1.

19-32
19 GPRS
If the system is not configured with any cell and as a result no Cell Name can be selected, this step fails.
When the Gb over IP transport mode is used on the Gb interface, do as follows: 1. Configure the NSE. For details, refer to Configuring the NSE. In this step, set Subnetwork Protocol Type to Gb Over IP, set the related parameters NSE Identifier, NSE Capability, NSE Status, IP Subnet Configure Mode, Server IP Address, and Server UDP Port No., and adhere to the following principles:
When the IP Subnet Configure Mode parameter is set to Static Configuration, the Server IP Address and Server UDP Port No. parameters need not be set. When the IP Subnet Configure Mode parameter is set to Dynamic Configuration, the Server IP Address and Server UDP Port No. parameters must be set. These two parameters specify the signaling address and port number of the SGSN and then obtain the NSVL information from the SGSN.
2.
Configure the device IP on the GFGUG board. For details, refer to step 3 in Configuring the GFGUG (Gb over IP). In this step, the Logical IP Address and Subnet Mask parameters need be set. Configure the port IP address on the GFGUG board. For details, refer to step 4 in Configuring the GFGUG (Gb over IP). In this step, select a Port No., configure IP Address and Subnet Mask of the selected port, and adhere to the following principles:
3.
If you set Port Type to FE when adding a GFGUG board, eight ports can be configured. The IP addresses of the eight ports should stay in different network segments but cannot remain in the same network segment as the device IP address. If you set Port Type to GE when adding a GFGUG board, only ports 0 and 4 can be configured. The IP addresses of the two ports should stay in different network segments but cannot remain in the same network segment as the device IP address. If active and standby GFGUGs are configured, their port IP addresses must be configured on the same network segment.
4.
Add a BSC router to the GFGUG board. For details, refer to step 5 in Configuring the GFGUG (Gb over IP). In this step, set the parameters such as Destination IP Address, Gateway, Subnet Mask, and Route PRI, and adhere to the following principles:
Destination IP Address should be set as a destination network segment but not a single IP address. Gateway should stay in the same network segment as the IP address of the port on the device. In the case of active and standby boards, add the BSC router after their port IP addresses are configured.
5.
Configure the local NSVL on the GFGUG board. For details, refer to Configuring the Local NSVL. In this step, set the parameters such as Local NSVL Identifier, NSE Identifier, and IP Address, and adhere to the following principles:

NSE Identifier should correspond to NSE Identifier set in step 2.1. IP Address is the Logical IP Address set in step 2.2.
6.
Configure the remote NSVL. For details, refer to Configuring the Remote NSVL. In this step, set the parameters such as Remote NSVL Identifier, NSE Identifier, IP Address, and IP Port No., and adhere to the following principles:
Issue 02 (2008-06-30)
19-33
19 GPRS
If IP Subnet Configure Mode in step 2.1 is set to Dynamic Configuration, the remote NSVL need not be configured. If IP Subnet Configure Mode in step 2.1 is set to Static Configuration, the remote NSVL must be configured.
7.
Configure the PTPBVC. For details, refer to Configuring the PTPBVC. In this step, set the parameters such as NSE Identifier, BVC Identifier, and Cell Name, and adhere to the following principles:

NSE Identifier should correspond to NSE Identifier set in step 2.1. If the system is not configured with any cell and as a result no Cell Name can be selected, this step fails.
Step 3 Configure the SGSN. 1. 2. On the BSC6000 Local Maintenance Terminal, right-click BSC6000 and then choose Configure PCU Data Add SGSN from the shortcut menu. Click Add. A dialog box is displayed, as shown in Figure 19-10. Figure 19-10 Add SGSN window
3. 4.
Set the SGSN Name and IP Address parameters. Click OK to end the configuration.
Step 4 Configure a cell to support GPRS. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page, and then select Set Cell Attributes . In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the Cells to be set list box, select the target cell, and then click Set Cell Attributes. A dialog box is displayed, as shown in Figure 19-11.
19-34
19 GPRS
4. 5.
Select the Support GPRS check box. Click OK to end the configuration.
Step 5 Configure idle timeslots if GPRS CS-3 or CS-4 is supported. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target BTS, and then choose Configure Site Idle Timeslot from the shortcut menu. A dialog box is displayed, as shown in Figure 19-12.
Issue 02 (2008-06-30)
19-35
19 GPRS
Figure 19-12 Configure Site Idle Timeslot dialog box
2. 3.
In the Idle Timeslot area, click the box under the Idle Timeslots area, and then enter the number of idle timeslots to be configured. Click Finish to end the configuration.
NOTE
l l l
Idle Timeslots should be configured only when Trans Type of the BSC is set to TDM. When the Flex Abis feature is enabled on the BTS, the idle timeslots cannot be configured if CS traffic is low, and GPRS in CS-3 or CS-4 can still work properly. When the Flex Abis feature is enabled on the BTS, it is recommended that the idle timeslots be configured if CS traffic is high; otherwise, GPRS in CS-3 or CS-4 cannot work properly for a long time.
Step 6 Configure a full-rate PDTCH or TCH for the GPRS-supportive cell. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a TRX on the Management Tree tab page, and then select Configure TRX Attributes. Select a TRX from the TRX view area and then click Configure TRX Attributes. In the displayed dialog box, click the Channel Attributes tab page, as shown in Figure 19-13.
19-36
Issue 02 (2008-06-30)
19 GPRS
Figure 19-13 Configure TRX Attributes tab page
4.
Select Channel No. and then select Channel Type as PDTCH or TCH Full Rate from the drop-down list box.
NOTE
If the cell supports only GPRS instead of EDGE, GPRS Channel Priority Type need not be configured.
5.
Click OK to end the configuration.
----End
19.6.3 Verifying GPRS (with Built-in PCU)

GPRS with built-in PCUs can be verified on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 Verify the PCU type of the BSC. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Configure BSC Attributes on the shortcut menu. A dialog box is displayed. In the displayed dialog box, select the Basic Data tab page, as shown in Figure 19-14.
2.
Issue 02 (2008-06-30)
19-37
19 GPRS
3.
Scroll down to confirm that PCU Type is set to Inner. When Gb over FR is applied on the Gb interface, do as follows: 1. On the BSC6000 Local Maintenance Terminal, click the BSC Attributes tab. A tab page is displayed, as shown in Figure 19-15.
Step 2 Verify the configuration of Gb links and related parameters.

l
19-38
Issue 02 (2008-06-30)
19 GPRS
Figure 19-15 BSC Attributes tab page
2.
Click the PCU tab. An NSE tab page is displayed, as shown in Figure 19-16.
Issue 02 (2008-06-30)
19-39
19 GPRS
Figure 19-16 NSE tab page
3. 4.
Check whether the related parameters such as NSE Identifier and Subnetwork Protocol Type are correctly configured. Click the BC tab. A dialog box is displayed, as shown in Figure 19-17.
19-40
Issue 02 (2008-06-30)
19 GPRS
Figure 19-17 BC tab page
5. 6.
Check whether the related parameters such as Occupied Timeslot, Bearer Channel ID, and Frame Relay Protocol Type are correctly configured. Click the NSVC tab. A dialog box is displayed, as shown in Figure 19-18.
Issue 02 (2008-06-30)
19-41
19 GPRS
Figure 19-18 NSVC tab page
7. 8.
Check whether the related parameters such as NSVC Identifier, Data Link Connection Identifier , and NSE Identifier are correctly configured. Click the PTPBVC tab. A dialog box is displayed, as shown in Figure 19-19.
19-42
Issue 02 (2008-06-30)
19 GPRS
Figure 19-19 PTPBVC tab page
9.
Check whether the related parameters such as NSE Identifier, BVC Identifier, and Cell Name are correctly configured.
10. Click Quit to end the verification.

l
When Gb over IP is applied on the Gb interface, do as follows: 1. 2. 3. 4. On the BSC6000 Local Maintenance Terminal, click the BSC Attributes tab. A tab page is displayed, as shown in Figure 19-15. Click the PCU tab. An NSE tab page is displayed, as shown in Figure 19-16. Check whether the related parameters such as NSE Identifier and Subnetwork Protocol Type are correctly configured. Click the Local NSVL Identifier tab. A dialog box is displayed, as shown in Figure 19-20.
Issue 02 (2008-06-30)
19-43
19 GPRS
Figure 19-20 Local NSVL Identifier tab page
5. 6.
Check whether the related parameters such as Local NSVL Identifier, NSE Identifier, and IP Address are correctly configured. Click the Remote NSVL Identifier tab. A dialog box is displayed, as shown in Figure 19-21.
19-44
Issue 02 (2008-06-30)
19 GPRS
Figure 19-21 Remote NSVL Identifier tab page
7. 8. 9.
Check whether the related parameters such as Remote NSVL Identifier, NSE Identifier, IP Address, and IP Port No. are correctly configured. Click the PTPBVC tab. A dialog box is displayed, as shown in Figure 19-19. Check whether the related parameters such as NSE Identifier, BVC Identifier, and Cell Name are correctly configured.
10. Click Quit. 11. Right-click a GFGUG on the BSC Device Panel of the BSC6000 Local Maintenance Terminal and select Configure BSC Router on the shortcut menu. A dialog box is displayed, as shown in Figure 19-22.
Issue 02 (2008-06-30)
19-45
19 GPRS
Figure 19-22 Configure BSC Router dialog box
12. Check whether the route related to Destination IP Address exists. 13. Click Finish to end the verification. ----End
19.6.4 Configuration Principles (with External PCU)

GPRS must adhere to the related configuration principles. One BSC can be configured with up to 32 PCUs. If multiple external PCUs are configured, the BSC should adhere to the following principles:
l
The Packet Circuit Identity Codes (PCICs) between multiple external PCUs must follow a uniform coding scheme. The PCICs of the BSC must correspond to those of the PCUs on a one-to-one basis, and the PCICs must be uniformly coded in the BSC.
When configuring the parameters on the A interface, ensure that CS paging messages are not transmitted through the Gs interface. At present, flow control is not provided on the Pb interface. If the BSC is connected to multiple external PCUs and the CS paging messages on the A interface are transmitted through the Gb interface, then the same CS paging message is transmitted from the external PCUs to the BSC through the Pb interface. This increases the load of the BSC.
The physical connection between the PCUs and the BSC must be consistent with data configuration.
19.6.5 Configuring GPRS (with External PCU)

This describes how to configure GPRS on the BSC6000 Local Maintenance Terminal.
19 GPRS
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. In the BSC6000V900R008 Exceptional Commercial License Application Template, fill in the following information.
l
Fill in the number of PDCHs to be purchased in the Number of resources column corresponding to the Maximum Number of PDCH Groups Activated in the Resource control items column. If the GPRS CS3/CS4 coding scheme is used, fill in 1 in the Number of resources column corresponding to Whether to activate CS34 in the Function control items column. Value 1 indicates that this function should be enabled.
2.
Procedure
Step 1 Set the PCU type to external PCU. 1. 2. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Configure BSC Attributes from the shortcut menu. In the displayed dialog box, select the Basic Data tab page, as shown in Figure 19-23.
3. 4.
Scroll down to set PCU Type to Outer. Click Finish to end the configuration.
Step 2 Configure the PCU.
Issue 02 (2008-06-30)
19-47
19 GPRS
NOTE
l l
One BSC can be configured with up to 32 PCUs. Each PCU has a unique name and ID in one BSC.
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Add PCU from the shortcut menu. A dialog box is displayed. Click Add. A dialog box is displayed, as shown in Figure 19-23. Figure 19-24 Add PCU dialog box
2.
3. 4.
Set PCU No. and PCU Name as planned. Click OK to end the configuration.
Step 3 Configure a Pb interface board. 1. On the LMT, click the BSC Device Panel tab. Right-click a slot and then choose Add Board from the shortcut menu. A dialog box is displayed, as shown in Figure 19-25.
19-48
Issue 02 (2008-06-30)
19 GPRS
Figure 19-25 Add Board dialog box
2. 3.
Select a Pb interface board (GEIUP/GOIUP). Click Finish.
Step 4 Configure the Pb interface E1/T1. 1. 2. Right-click a GEIUP board in the GMPS subrack and then choose Configure Pb Interface E1/T1 from the shortcut menu. Click Add. A dialog box is displayed, as shown in Figure 19-26.
Issue 02 (2008-06-30)
19-49
19 GPRS
Figure 19-26 Add Pb Interface E1/T1 dialog box
3. 4.
Select the Pb Interface E1/T1 Attributes tab and then set the parameters Subrack No., Slot No., Port No., Transmission Mode, Start PCIC, PCU No., and PCU Name. Click OK to end the configuration.
Step 5 Configure a signaling link on the Pb interface. 1. 2. Right-click a GEIUP board in the GMPS subrack and then choose Add Pb Signaling Link from the shortcut menu. Click Add. A dialog box is displayed, as shown in Figure 19-27.
19-50
Issue 02 (2008-06-30)
19 GPRS
Figure 19-27 Add Pb Signaling Link dialog box
3. 4.
Set Subrack No., Slot No., Port No., Timeslot No., TEI, Transmission Mode, Congestion Start Threshold, and Congestion End Threshold. Click OK to end the configuration.
Step 6 Configure a cell to support GPRS. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page, and then choose Set Cell Attributes from the shortcut menu. In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the Cells to be set list box, select the target cell, and then click Set Cell Attributes. A dialog box is displayed, as shown in Figure 19-28.
Issue 02 (2008-06-30)
19-51
19 GPRS
4. 5.
Select the Support GPRS check box and then choose a PCU number from the PCU dropdown list box. Click OK to end the configuration.
Step 7 Configure idle timeslots if GPRS CS-3 or CS-4 is supported. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target BTS, and then choose Configure Site Idle Timeslot from the shortcut menu. A dialog box is displayed, as shown in Figure 19-29.
19-52
Issue 02 (2008-06-30)
19 GPRS
2. 3.
NOTE
l l l
Idle Timeslots should be configured only when Trans Type of the BSC is set to TDM. When the Flex Abis feature is enabled on the BTS, the idle timeslots cannot be configured if CS traffic is low, and GPRS in CS-3 or CS-4 can still work properly. When the Flex Abis feature is enabled on the BTS, it is recommended that the idle timeslots be configured if CS traffic is high; otherwise, GPRS in CS-3 or CS-4 cannot work properly for a long time.
Step 8 Configure a PDCH and a dynamic PDCH for the cell that supports GPRS. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a TRX on the Management Tree tab page, and then choose Configure TRX Attributes from the shortcut menu. In the displayed dialog box, select the target TRX in the TRX view list box, and then click Configure TRX Attributes. In the displayed dialog box, click the Channel Attributes tab page, as shown in Figure 19-30.
Issue 02 (2008-06-30)
19-53
19 GPRS
Figure 19-30 Configure TRX Attributes tab page
4.
Select Channel No. and then select Channel Type as PDTCH or Dynamic PDCH from the drop-down list box.
NOTE
If the cell supports only GPRS instead of EDGE, GPRS Channel Priority Type need not be configured.
5.
Click OK to end the configuration.
----End
19.6.6 Verifying GPRS (with External PCU)

GPRS with external PCUs can be verified on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 Verify the PCU type of the BSC. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Configure BSC Attributes on the shortcut menu. A dialog box is displayed. In the displayed dialog box, select the Basic Data tab page, as shown in Figure 19-31.
2.
19-54
Issue 02 (2008-06-30)
19 GPRS
3.
Scroll down to confirm that PCU Type is set to Outer.
Step 2 Verify the PCU configuration and Pb signaling link. 1. On the BSC6000 Local Maintenance Terminal, click the BSC Attributes tab. A tab page is displayed, as shown in Figure 19-32.
Issue 02 (2008-06-30)
19-55
19 GPRS
Figure 19-32 BSC Attributes tab page
2.
Click PCU. A dialog box is displayed, as shown in Figure 19-33.
19-56
Issue 02 (2008-06-30)
19 GPRS
Figure 19-33 View PCU dialog box
3. 4.
Check whether PCU No. and PCU Name are correct. Click Pb Signaling Link. A dialog box is displayed, as shown in Figure 19-34. Check whether the planned PBSLs are correctly configured.
Issue 02 (2008-06-30)
19-57
19 GPRS
Figure 19-34 View Pb Signaling Link dialog box
5.
Click Quit to return to the previous dialog box.
Step 3 Verify the E1/T1 on the Pb interface. 1. On the tab page shown in Figure 19-32, click Timeslot of E1 Interface. On the displayed dialog box, click the Pb Interface E1 tab. A tag page is displayed, as shown in Figure 19-35.
19-58
Issue 02 (2008-06-30)
19 GPRS
Figure 19-35 Pb Interface E1 tab page
2. 3.
Check whether the planned Pb interface E1 is correctly configured. Click Quit to end the verification.
----End

This describes the alarms and counters related to GPRS.
Alarms
The alarms related to GPRS include the alarms related to internal PCUs and external PCUs, as described in Table 19-8 and Table 19-9. Table 19-8 Alarms related to internal PCUs Alarm ID 291 293 294
Issue 02 (2008-06-30)
Alarm Name Cell Transmission Delay Abnormal GB BC Faulty TRX Config Error
19 GPRS
Alarm ID 331 332 333 340 341 342 343 344
Alarm Name NSVC Faulty NSVL Faulty NSE Faulty Cell PS Service Faulty DSP Resource Overload PTP BVC Faulty NSVL Dynamic Configuration Process Failure FAULTY DSP OVER LIMIT
Table 19-9 Alarms related to external PCUs Alarm ID 104 128 Alarm Name All PBSLs in the PCU Are Faulty No Circuit Configured in the PCU
Counters
The counters related to GPRS also include the counters related to internal PCUs and the counters related to external PCUs, as described in Table 19-10 and Table 19-11. Table 19-10 Counters related to internal PCUs Counter A9401 A9402 A9403 A9404 A9405 A9406 Description Number of 8-Bit Packet Channel Requests Received on CCCH Number of 8-Bit One Phase Access Requests Received on RACH Number of 8-Bit Single Block Channel Requests Received on RACH Number of 11-Bit Packet Channel Requests Received on CCCH Number of 11-Bit One Phase Access Requests Received on RACH Number of 11-Bit Single Block Channel Requests Received on RACH
19-60
Issue 02 (2008-06-30)
19 GPRS
Counter AA9407 A9408 AA9409 A9410 A9411 A9501 A9502 A9503 A9504 A9505 A9506 A9507 A9508 A9509 A9510 A9511 A9512 A9601 A9602 A9603 A9604 A9605
Description Average Interval of Packet Access Requests on CCCH (s) Number of Packet Channel Requests Received on PCCCH Average Interval of Packet Access Requests on PCCCH(s) Number of Resource Requests Received on Uplink PACCH Number of Resource Requests Received on Downlink PACCH Number of Uplink Assignments Number of Successful Uplink Assignments Number of Uplink PS Immediate Assignments Number of Successful Uplink PS Immediate Assignments Number of Uplink Assignments on PACCH Number of Successful Uplink Assignments on PACCH Number of Downlink Assignments Number of Successful Downlink Assignments Number of Downlink PS Immediate Assignments Number of Successful Downlink PS Immediate Assignments Number of Downlink Assignments on PACCH Number of Successful Downlink Assignments on PACCH Number of Packet Paging Requests Received from the Gb Interface Number of Circuit Paging Requests Received from the Gb Interface Number of Circuit Paging Requests Sent on PACCH Number of Packet Paging Requests Sent on PPCH Number of Circuit Paging Requests Sent on PPCH
Issue 02 (2008-06-30)
19-61
19 GPRS
Counter A9606 H9001 H9002 H9003 H9004 H9007 H9008 H9009 H9010 H9011 H9012 H9013 H9014 A9001 A9002 A9003 A9004 A9005 A9006
Description Number of Discarded Paging Messages on PPCH Number of Overlaid Subcell to Underlaid Subcell Handover Requests Number of Underlaid Subcell to Overlaid Subcell Handover Requests Number of Successful Handovers from Overlaid Subcell to Underlaid Subcell Number of Successful Handovers from Underlaid Subcell to Overlaid Subcell Number of Times a Cell Is Selected by MS Number of Cell Reselections by MS at Short Interval Number of Cell Ping-Pong Reselections by MS Number of Network Controlled Cell Reselection Attempts Number of Network Controlled Cell Reselection Attempts due to Downlink Quality Number of Network Controlled Cell Reselection Attempts due to Traffic Load Number of Network Controlled Cell Reselection Attempts for Better Cell Number of Failed Network Controlled Cell Reselections Number of Uplink GPRS TBF Establishment Attempts Number of Successful Uplink GPRS TBF Establishments Number of Failed Uplink GPRS TBF Establishments due to No Channel Number of Failed Uplink GPRS TBF Establishments due to MS No Response Number of Uplink GPRS TBF Normal Releases Number of Uplink GPRS TBF Abnormal Releases due to N3101 Overflow (MS No Response)
19-62
Issue 02 (2008-06-30)
19 GPRS
Counter A9007
Description Number of Uplink GPRS TBF Abnormal Releases due to N3103 Overflow (MS No Response) Number of Uplink GPRS TBF Abnormal Releases due to SUSPEND Number of Uplink GPRS TBF Abnormal Releases due to FLUSH Number of Uplink GPRS TBF Abnormal Releases due to No Channel Total Number of Sampled Concurrent Uplink GPRS TBFs Sampling Times of Concurrent Uplink GPRS TBFs Average Number of Concurrent Uplink GPRS TBFs Total Duration of Uplink GPRS TBF (ms) Average Duration of Uplink GPRS TBF (s) Number of Downlink GPRS TBF Establishment Attempts Number of Successful Downlink GPRS TBF Establishments Number of Failed Downlink GPRS TBF Establishments due to No Channel Number of Failed Downlink GPRS TBF Establishments due to MS No Response Number of Downlink GPRS TBF Normal Releases Number of Downlink GPRS TBF Abnormal Releases due to N3105 Overflow Number of Downlink GPRS TBF Abnormal Releases due to SUSPEND Number of Downlink GPRS TBF Abnormal Releases due to FLUSH Number of Downlink GPRS TBF Abnormal Releases due to No Channel Total Number of Sampled Concurrent Downlink GPRS TBFs
A9008 A9009 A9010 A9011 A9012 AA9013 A9014 AA9015 A9101 A9102 A9103 A9104 A9105 A9106 A9107 A9108 A9109 A9110
Issue 02 (2008-06-30)
19-63
19 GPRS
Counter A9111 AA9112 A9113 AA9114 L9001 L9002 L9003 L9004 L9005 L9006 L9007 L9008 L9009 RL9010 RL9011 RL9012 RL9013 TL9014 TL9015 L9016 L9017
19-64
Description Sampling Times of Concurrent Downlink GPRS TBFs Average Number of Concurrent Downlink GPRS TBFs Total Duration of Downlink GPRS TBF (ms) Average Duration of Downlink GPRS TBF (s) Total Number of Uplink GPRS RLC Data Blocks Total Number of Uplink RLC Data Blocks Using CS1 Total Number of Uplink RLC Data Blocks Using CS2 Total Number of Uplink RLC Data Blocks Using CS3 Total Number of Uplink RLC Data Blocks Using CS4 Number of Valid Uplink RLC Data Blocks Using CS1 Number of Valid Uplink RLC Data Blocks Using CS2 Number of Valid Uplink RLC Data Blocks Using CS3 Number of Valid Uplink RLC Data Blocks Using CS4 Retransmission Rate of RLC Uplink Data Blocks Using CS1 (%) Retransmission Rate of RLC Uplink Data Blocks Using CS2 (%) Retransmission Rate of RLC Uplink Data Blocks Using CS3 (%) Retransmission Rate of RLC Uplink Data Blocks Using CS4 (%) Average Throughput of Uplink GPRS RLC (kbit/s) Average Payload of Single Uplink GPRS TBF (KB) Number of CS Upgrades on Uplink GPRS TBF Number of CS Degrades on Uplink GPRS TBF
19 GPRS
Counter L9018 L9019 L9101 L9102 L9103 L9104 L9105 L9106 L9107 L9108 L9109 RL9110 RL9111 RL9112 RL9113 TL9114 TL9115 L9116 L9117 L9118
Description Number of Uplink GPRS RLC Control Blocks Total Number of Uplink GPRS TBFs Total Number of Downlink GPRS RLC Data Blocks Total Number of Downlink RLC Data Blocks Using CS1 Total Number of Downlink RLC Data Blocks Using CS2 Total Number of Downlink RLC Data Blocks Using CS3 Total Number of Downlink RLC Data Blocks Using CS4 Total Number of Valid RLC Downlink Data Blocks Using CS1 Total Number of Valid RLC Downlink Data Blocks Using CS2 Total Number of Valid RLC Downlink Data Blocks Using CS3 Total Number of Valid RLC Downlink Data Block Using CS4 Retransmission Rate of RLC Downlink Data Block Using CS1 (%) Retransmission Rate of RLC Downlink Data Block Using CS2 (%) Retransmission Rate of RLC Downlink Data Block Using CS3 (%) Retransmission Rate of RLC Downlink Data Block Using CS4 (%) Average Throughput of Downlink GPRS RLC (kbit/s) Average Payload of Single Downlink GPRS TBF (KB) Number of CS Upgrades on Downlink GPRS TBF Number of CS Degrades on Downlink GPRS TBF Number of Downlink GPRS RLC Control Blocks
Issue 02 (2008-06-30)
19-65
19 GPRS
Counter L9119 L9120 L9401 L9402 L9403 AL9404 AL9405 TL9406 L9407 L9408 L9409 L9501 L9502 L9503 AL9504 L9505 L9506 AL9507 L9508 L9509 TL9510 L9511 L9512 L9513 R9001
Description Number of Downlink GPRS RLC Dummy Blocks Total Number of Downlink GPRS TBFs Total Number of Uplink TBFs Number of Uplink LLC PDUs sent Total Bytes of Uplink LLC PDUs Sent Average Length of Uplink LLC PDU Average LLC PDU Bytes per Uplink TBF Uplink LLC Throughput Rate (kbit/s) Total Bytes of Uplink GPRS Background Service LLC PDUs Sent Total Bytes of Uplink GPRS Interactive Service LLC PDUs Sent Total Bytes of Uplink GPRS Streaming Service LLC PDUs Sent Total Number of Downlink TBFs Total Number of Downlink LLC PDUs Received Total Bytes of Downlink LLC PDUs Received Average Length of Downlink LLC PDUs Total Number of LLC PDUs Sent Total Bytes of LLC PDUs Sent Average LLC PDU Bytes per Downlink TBF Number of Downlink LLC PDUs Discarded due to Timeout Number of Downlink LLC PDUs Discarded due to FLUSH Downlink LLC Throughput Rate (kbit/s) Total Bytes of Downlink GPRS Background Service LLC PDUs Sent Total Bytes of Downlink GPRS Interactive Service LLC PDUs Sent Total Bytes of Downlink GPRS Streaming Service LLC PDUs Sent Number of Packet Cell Resets by BSC
19-66
Issue 02 (2008-06-30)
19 GPRS
Counter R9002 R9003 R9006 R9007 R9101 R9102 R9103 R9104 R9105 R9106 R9107 R9108 R9201 R9202 RR9203 R9204 R9205 R9206 R9207 RR9208 RR9209 R9210 R9211 AR9212
Description Number of Packet Cells Blocked by BSC Number of Packet Cells Unblocked by BSC Number of Packet Channels Blocked by BSC Number of Packet Channels Unblocked by BSC Number of Application Attempts of Abis Timeslot Number of Successful Application Attempts of Abis Timeslot Number of Release Requests of Abis Timeslot Number of Successful Releases of Abis Timeslot Number of Application Attempts of IP PATH or HDLC Bandwidth (16K) Number of Successful Application Attempts of IP PATH or HDLC Bandwidth (16K) Number of Release Requests of IP PATH or HDLC Bandwidth (16K) Number of Successful Releases of IP PATH or HDLC Bandwidth (16K) Number of RLC Data Blocks Used on PDCH Total Number of RLC Data Blocks on PDCH Average PDCH Utilization (%) Number of RLC Data Blocks Received on Uplink PDTCH/PACCH Number of RLC Data Blocks Sent on Downlink PDTCH/PACCH Total Number of Uplink PDTCH/PACCH Blocks Total Number of Downlink PDTCH/PACCH Blocks Uplink PDTCH/PACCH Utilization (%) Downlink PDTCH/PACCH Utilization (%) Sampling Times of PDCH Queue Length Total Sampled PPCH Queue Lengths Average PPCH Queue Length
Issue 02 (2008-06-30)
19-67
19 GPRS
Counter R9213 AR9214 R9215 AR9216 R9301 R9302 AR9303 R9304 R9305 R9308 AR9309 R9310 AR9311 R9312 AR9313 R9314 AR9315 R9316 R9317 R9318 AR9319 R9324 AR9325 R9326 AR9327
Description Total Sampled PAGCH Queue Lengths Average PAGCH Queue Length Total Sampled PDTCH Queue Lengths Average PDTCH Queue Length Sampling Times of PDCH Measurement Total Number of Sampled Available PDCHs Average Number of Available PDCHs Maximum Number of Available PDCHs Minimum Number of Available PDCHs Total Number of Sampled GPRS PDCHs Activated Average Number of GPRS PDCHs Activated Total Number of Sampled PDCHs Occupied Average Number of Occupied PDCHs Total Number of Sampled PDCHs Occupied by Uplink TBF Average Number of PDCHs Occupied by Uplink TBF Total Number of Sampled PDCHs Occupied by Downlink TBF Average Number of PDCHs Occupied by Downlink TBF Maximum Number of Occupied PDCHs Minimum Number of Occupied PDCHs Total Number of Occupied GPRS PDCHs Average Number of Occupied GPRS PDCHs Total Allocated Seizure Duration of All Available PDCHs (ms) Average Allocated Seizure Duration of All Available PDCHs (s) Total Number of Sampled PDCHs Occupied by TBF Average Number of PDCHs Occupied by TBF
19-68
Issue 02 (2008-06-30)
19 GPRS
Counter R9328 AR9329 R9334 AR9335 R9341 R9342 R9343 R9344 L9601 L9602 L9603 L9604 L9605 L9701 L9702 L9703 L9704 L9705 L9706 L9707 L9708
Description Total Number of Sampled GPRS PDCHs Occupied by GPRS TBF Average Number of GPRS PDCHs Occupied by GPRS TBF Number of Concurrent GPRS TBFs on GPRS PDCH Average Number of Concurrent GPRS TBFs on GPRS PDCH Number of TCH to PDTCH Conversion Attempts Number of Successful TCH to PDTCH Conversions Number of Reclaimed Dynamic PDCHs Number of Reclaimed Busy Dynamic PDCHs Number of Frames Sent on BC Number of Frames Received on BC Number of Frames Discarded on BC Peak Bytes of NS PDUs Sent on BC Peak Bytes of NS PDUs Received on BC Number of NS PDUs Sent by NS sublayer (NSVC) Number of NS PDUs Received by NS Sublayer (NSVC) Number of NS PDUs Discarded by NS Sublayer (NSVC) Total Bytes of NS PDUs Sent by NS Sublayer (NSVC) Total Bytes of NS PDUs Received by NS Sublayer (NSVC) Number of RESET Messages Sent by NS Sublayer to Peer End Number of RESET ACK Messages Received from Peer End Number of RESET Messages Received by NS Sublayer from Peer End
Issue 02 (2008-06-30)
19-69
19 GPRS
Counter L9709 L9710 L9711 L9712 L9713 L9714 L9715 L9716 L9717 L9801 L9802 L9803 L9804 L9805 L9901 L9902 L9903 L9904 L9A01
Description Number of RESET ACK Messages Sent by NS Sublayer to Peer End Number of BLOCK Messages Sent by NS Sublayer to Peer End Number of BLOCK ACK Messages Received from Peer End Number of BLOCK Messages Received from Peer End Number of BLOCK ACK Messages Sent by NS Sublayer to Peer End Number of UNBLOCK Messages Sent by NS Sublayer to Peer End Number of UNBLOCK ACK Messages Received from Peer End Number of UNBLOCK Messages Received from Peer End Number of UNBLOCK ACK Messages Sent by NS Sublayer to Peer End Number of NS PDUs Sent by NS Sublayer (NSVL) Number of NS PDUs Received by NS Sublayer (NSVL) Number of NS PDUs Discarded by NS Sublayer (NSVL) Total Bytes of NS PDUs Sent by NS Sublayer (NSVL) Total Bytes of NS PDUs Received by NS Sublayer (NSVL) Number of FLUSH LL PDUs Received by BSSGP Sublayer Number of SUSPEND PDUs Sent by BSSGP Sublayer Number of RESUME PDUs Sent by BSSGP Sublayer Number of RADIO STATUS PDUs Sent by BSSGP Sublayer Number of Normal Frames Received
19-70
Issue 02 (2008-06-30)
19 GPRS
Counter L9A02 L9A03 L9A04 L9A05 L9B01 L9B02 L9B03 L9B04 R9401 R9402 AR9403 R9404 R9501 R9502 R9503 R9504 AR9505 R9506 R9507 R9508 AR9509 S9201 S9202 S9203 AS9204 S9205 S9206
Description Number of Out-of-Synchronization Frames Received Number of Check Error Frames Received Number of Valid TRAU Frames Sent Number of Empty TRAU Frames Sent Number of PTRAU Packets Received Number of PTRAU Packets Sent Number of Uplink PTRAU Packets Discarded Number of Disordered PTRAU Packets Received Total Sampled DSP CPU Usage Sampling Times of DSP CPU Usage Average DSP CPU Usage (%) Peak DSP CPU Usage (%) Maximum Number of PDCHs Activated on DSP Minimum Number of PDCHs Activated on DSP Total Number of Sampled PDCHs Activated on DSP Sampling Times of PDCH Measurement on DSP Average Number of PDCHs Activated on DSP Maximum Number of PDCHs Occupied on DSP Minimum Number of PDCHs Occupied on DSP Total Number of Sampled PDCHs Occupied on DSP Average Number of PDCHs Occupied on DSP Maximum Number of PDCHs Assigned per BSC Total Number of Sampled PDCHs Assigned per BSC Sampling Times of PDCHs Assigned per BSC Average Number of PDCHs Assigned per BSC Maximum Speed of PS Traffic per BSC (kbit/s) Number of Failed PDCH Assignments due to Congestion
Issue 02 (2008-06-30)
19-71
19 GPRS
Counter S9001 S9002 S9003 S9004 S9005 S9006 S9007 S9008 S9009 S9010 S9011 S9012 S9013 S9014 S9015 S9016 S9017 S9018 S9019 S9020 S9021 S9022 S9023 S9024 S9025 S9026 S9027 S9028 S9029 S9030
Description Number of Times GMSK_MEAN_BEP=1 Number of Times GMSK_MEAN_BEP=2 Number of Times GMSK_MEAN_BEP=3 Number of Times GMSK_MEAN_BEP=4 Number of Times GMSK_MEAN_BEP=5 Number of Times GMSK_MEAN_BEP=6 Number of Times GMSK_MEAN_BEP=7 Number of Times GMSK_MEAN_BEP=8 Number of Times GMSK_MEAN_BEP=9 Number of Times GMSK_MEAN_BEP=10 Number of Times GMSK_MEAN_BEP=11 Number of Times GMSK_MEAN_BEP=12 Number of Times GMSK_MEAN_BEP=13 Number of Times GMSK_MEAN_BEP=14 Number of Times GMSK_MEAN_BEP=15 Number of Times GMSK_MEAN_BEP=16 Number of Times GMSK_MEAN_BEP=17 Number of Times GMSK_MEAN_BEP=18 Number of Times GMSK_MEAN_BEP=19 Number of Times GMSK_MEAN_BEP=20 Number of Times GMSK_MEAN_BEP=21 Number of Times GMSK_MEAN_BEP=22 Number of Times GMSK_MEAN_BEP=23 Number of Times GMSK_MEAN_BEP=24 Number of Times GMSK_MEAN_BEP=25 Number of Times GMSK_MEAN_BEP=26 Number of Times GMSK_MEAN_BEP=27 Number of Times GMSK_MEAN_BEP=28 Number of Times GMSK_MEAN_BEP=29 Number of Times GMSK_MEAN_BEP=30
19-72
Issue 02 (2008-06-30)
19 GPRS
Counter S9031 S9032
Description Number of Times GMSK_MEAN_BEP=31 Number of Times GMSK_MEAN_BEP=32
Table 19-11 Counters related to external PCUs Counter AL8351 AL8353 AL8354 AL8355 AL8352 L0387 L8387 R3140 R3141 AR3011A AR3011B CR3011 AR3021A AR3021B A031 R3001A Description Mean Number of Faulty Circuits on the Pb Interface Mean Number of Blocked Circuits on the Pb Interface Mean Number of Idle Circuits on the Pb Interface Mean Number of Busy Circuits on the Pb Interface Mean Number of Circuits in Maintenance State on the Pb Interface Total Number of Messages Received from PCU Messages Received from a PCU Requests for TCH from the PCU Successful Requests for TCH from the PCU Mean Number of Dynamically Configured Channels (PDCH) (900/850 Cell) Mean Number of Dynamically Configured Channels (PDCH) (1800/1900 Cell) Mean Number of Dynamically Configured Channels (PDCH) Mean Number of Available Channels (PDCH) (900/850 Cell) Mean Number of Available Channels (PDCH) (1800/1900 Cell) SGSN-Initiated Paging Requests for PS Service Number of Initially Configured Channels (Static PDCH) (900/850 Cell)
Issue 02 (2008-06-30)
19-73
19 GPRS
Counter R3001B R3002A R3002B CR3001 CR3002 ZTA331 ZTA301H ZTL3188D
Description Number of Initially Configured Channels (Static PDCH) (1800/1900 Cell) Number of Initially Configured Channels (Dynamic PDCH) (900/850 Cell) Number of Initially Configured Channels (Dynamic PDCH) (1800/1900 Cell) Number of Initially Configured Channels (Static PDCH) Number of Initially Configured Channels (Dynamic PDCH) Paging Requests on the Abis Interface per BSC (PS Service) Immediate Assignment Commands per BSC (PS Service) PCH Overloads due to PS Service Counted through the Indications from the Abis Interface per BSC Delivered Paging Messages for PS Service PACKET CCCH LOAD IND Messages Sent on Abis Interface
A331 L3188D
19.8 References
This describes the reference documents related to GPRS. The GPRS reference documents are as follows:
l
3GPP TS41.061,General Packet Radio Service (GPRS); GPRS ciphering algorithm requirements 3GPP TS43.064,General Packet Radio Service (GPRS); Overall description of the GPRS radio interface; Stage 2 3GPP TS44.060,General Packet Radio Service(GPRS); Mobile Station(MS)-Base Station System(BSS)interface;Radio Link Control/Medium Access Control(RLC/MAC) protocol 3GPP TS44.064,Mobile Station - Serving GPRS Support Node (MS-SGSN);Logical Link Control (LLC) Layer Specification 3GPP TS44.160,General Packet Radio Service(GPRS); Mobile Station (MS)-Base Station System(BSS)interface;Radio Link Control/Medium Access Control(RLC/MAC)protocol for Iu mode 3GPP TS 48.014,General Packet Radio Service(GPRS);Base Station System(BSS)Serving GPRS Support Node(SGSN) interface; Gb interface Layer 1
19-74

l
19 GPRS
3GPP TS 48.016,General Packet Radio Service(GPRS);Base Station System(BSS)Serving GPRS Support Node(SGSN) interface;Network service 3GPP TS 48.018,General Packet Radio Service(GPRS);Base Station System (BSS)Serving GPRS Support Node(SGSN);BSS GPRS protocol (BSSGP) 3GPP TS 49.995,General Packet Radio Service(GPRS); Interworking between modified Public Land Mobile Network (PLMN)supporting GPRS and legacy GPRS mobiles
Issue 02 (2008-06-30)
19-75
20 EGPRS
20
About This Chapter
EGPRS
20.1 Overview This describes the EGPRS. The Enhanced Data Rate for GSM Evolution (EDGE) can provide high-rate data services. 20.2 Availability This lists the NEs, software versions, licenses, and other conditions required for the implementation of EDGE. 20.3 Impact This describes the impact of EGPRS on system performance. 20.4 Technical Description This describes the technical aspects of EDGE. EDGE is an evolution stage of PS services. It can be called as 2.75 G mobile communication technology. If the equipment on the current network remains unchanged, EDGE can be implemented through the upgrade of relevant software. EDGE can enhance the transmission rate of PS data. 20.5 Capabilities This describes the EDGE capabilities of the built-in PCU and external PCU. 20.6 Implementation EDGE implementation consists of configuring EDGE with the built-in PCU and configuring EDGE with the external PCU. 20.7 Maintenance Information This lists the alarms and counters related to EDGE. 20.8 References The references indicate the documents about EDGE from the related standard organizations.
Issue 02 (2008-06-30)
20-1
20 EGPRS
20.1 Overview
This describes the EGPRS. The Enhanced Data Rate for GSM Evolution (EDGE) can provide high-rate data services.
Definition
EDGE consists of the Enhanced GPRS (EGPRS) and the Enhanced Circuit Switched Data (ECSD).
l
EGPRS is the enhanced GPRS. EGPRS uses the 8PSK modulation mode so that the rate of a single channel is improved. The maximum rate of a single channel is 59.2 kbit/s. ECSD is the enhanced High Speed Circuit Switched Data (HSCSD).
NOTE
The Huawei BSS supports only EGPRS. Unless otherwise specified, EDGE referred to in this document indicates EGPRS.
Purposes
Using the new modulation and coding schemes, EDGE greatly improves the data service rates. The data transmission rates on the Um interface in EDGE are almost three times those in GSM. This meets the requirements of high-rate data services.
Term
None.

Acronym and Abbreviation EDGE GPRS PCIC BER BVC BSSGP QoS TBF CCCH PCCCH PACCH
20-2
Full Spelling Enhanced Data Rate for GSM Evolution General Packet Radio Service Packet Circuit Identity Code Bit Error Rate BSSGP Virtual Connection Base Station System GPRS Protocol Quality of Service Temporary Block Flow Common Control Channel Packet Common Control Channel Packet Associated Control Channel
Issue 02 (2008-06-30)
20 EGPRS
Acronym and Abbreviation RLC
Full Spelling Radio Link Control
20.2 Availability
This lists the NEs, software versions, licenses, and other conditions required for the implementation of EDGE.
NEs Involved
Table 20-1 lists the network elements (NEs) involved in EDGE. Table 20-1 NEs Involved in EDGE MS
NOTE
BTS
BSC
PCU
SGSN
GGSN
MSC -
HLR
Software Versions
Table 20-2 lists the versions of GBSS products that support EDGE. Table 20-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3X BTS3012A BTS3001C BTS3002C BTS3002E BTS3006C BTS3012 DTRU QTRU Version V900R008C01 and later versions G3BTS32V302R002C05 and later versions All versions All versions All versions BTS3000V100R002C01 and later versions BTS3000V100R002C01 and later versions BTS3000V100R001C01 and later versions BTS3000V100R008C01 and later versions
Issue 02 (2008-06-30)
20-3
20 EGPRS
Product BTS3012 AE DTRU QTRU
Version BTS3000V100R001C04 and later versions BTS3000V100R008C01 and later versions BTS3000V100R008C02 and later versions BTS3000V100R008C02 and later versions BTS3000V100R008C01 and later versions
BTS3900 GSM BTS3900A GSM DBS3900 GSM
Miscellaneous
The EDGE Support can be configured only when the GPRS Support is configured.
20.3 Impact
This describes the impact of EGPRS on system performance.

l
When the EDGE function is enabled, the maximum number of TRXs supported by one E1 cable in different network topologies decreases. Thus, the number of TRXs that each GMPS or GEPS supports decreases.
NOTE
The number of idle timeslots and TRXs that each E1 cable can be configured with must meet the following requirement: The number of configured TRXs + the number of configured idle timeslots/ 8 the maximum number of configurable TRXs.
l
When the external PCU is used and the EDGE function is enabled, the capacity of each RPPU in the PCU decreases. The number of PDCHs that can be activated on each RPPU decreases from 120 to 100.

None.

This describes the technical aspects of EDGE. EDGE is an evolution stage of PS services. It can be called as 2.75 G mobile communication technology. If the equipment on the current network remains unchanged, EDGE can be implemented through the upgrade of relevant software. EDGE can enhance the transmission rate of PS data. 20.4.1 8PSK Modulation Mode This describes the 8PSK modulation mode. In 8PSK modulation mode, symbols represent the absolute phases of signals. There are eight possible symbols and each symbol represents three bits of information. 20.4.2 EGPRS Transmit Power
20 EGPRS
This describes the transmit power of a BTS that uses 8PSK modulation mode. 20.4.3 MCS-1 to MCS-9 Coding Schemes This describes MCS-1 to MCS-9 modulation and coding schemes used in EDGE. 20.4.4 Link Quality Control This describes the link quality control. The link quality control enables the system to adapt to the radio transmission environment dynamically by changing modulation and coding schemes during data transmission, thus improving the link quality. 20.4.5 Types of Preferred EGPRS Channels This describes the types of preferred channels in EGPRS. 20.4.6 CCCH 11Bit EGPRS Access EDGE supports 11Bit EGPRS access on the CCCH. EDGE reduces the access delay and improves the access performance of the MS. 20.4.7 Assignment of Idle Timeslots For packet data services, the Abis interface supports the mapping of several timeslots to one traffic channel. Then, the timeslots are divided and combined on the TX and RX ends.
20.4.1 8PSK Modulation Mode

This describes the 8PSK modulation mode. In 8PSK modulation mode, symbols represent the absolute phases of signals. There are eight possible symbols and each symbol represents three bits of information. The GSM system uses the Gaussian Minimum Shift Keying (GMSK) modulation mode. In GMSK modulation mode, bit 0 or 1 indicates the change in signal phases. Each phase change is represented by a symbol. In 8PSK modulation mode, symbols represent the absolute phases of signals. There are eight possible symbols and each symbol represents three bits of information. Therefore, the data rate on the Um interface in EDGE can theoretically be three times that in GSM. Figure 20-1 shows the I/Q relations for the modulation and demodulation in GSM and EDGE. Figure 20-1 I/Q relations for the modulation and demodulation in GSM and EDGE
GPRS: GMSK Modulation Q (0,1,0) 1 (0,0,0) (0,1,1) GPRS: 8PSK Modulation Q
(0,0,0) I I (1,1,1)
0 (1,0,1) (1,0,0) (1,1,0)
Issue 02 (2008-06-30)
20-5
20 EGPRS
NOTE
In terms of performance, the 8PSK modulation mode is better than the GMSK modulation mode. The demodulation threshold of the 8PSK mode, however, is higher than the demodulation threshold of the GMSK mode. The modulation mode is radio environment specific. The PCU automatically adjusts the modulation mode based on the BER report from an MS. Therefore, the modulation and demodulation mode that EDGE uses can be 8PSK or GMSK.
Table 20-3 lists the modulation bits and corresponding symbols shown in Figure 20-1. Table 20-3 Modulation bits and corresponding symbols Modulation Bit (1,1,1) (0,1,1) (0,1,0) (0,0,0) (0,0,1) (1,0,1) (1,0,0) (1,1,0) Symbol 0 1 2 3 4 5 6 7
NOTE
Table 20-3 lists all the modulation bits and corresponding symbols.
20.4.2 EGPRS Transmit Power

This describes the transmit power of a BTS that uses 8PSK modulation mode. From the perspective of network operation, the transceiver of the BTS in EDGE must have the same spectrum features as those of an ordinary transceiver. When sending the signals modulated in 8PSK modulation mode, the transceiver of the BTS in EDGE uses the transmit power that is 2 dB5 dB less than the average power in GMSK modulation mode. Thus, the requirements for spectrum can be met. In the system, the parameter 8PSK Power Level can be specified to meet the requirements. The default value of this parameter is 0. On the BCCH, the transmit power of the signals modulated in 8PSK modulation mode is at most 4 dB less than the average transmit power of the signals modulated in GMSK modulation mode. On the timeslot located before the timeslot of the BCCH/CCCH, the transmit power of the signals modulated in 8PSK mode is at most 2 dB less than that of the signals modulated in GMSK modulation mode.
20.4.3 MCS-1 to MCS-9 Coding Schemes

This describes MCS-1 to MCS-9 modulation and coding schemes used in EDGE. EDGE uses MCS-1 to MCS-9 modulation and coding schemes, as listed in Table 20-4.
20 EGPRS
Table 20-4 Modulation and coding schemes in EDGE Coding Scheme Modulation Mode Number of Bits in the Payload of Each Burst 2 x 592 2 x 544 2 x 448 592 544 + 48 MCS-5 MCS-4 MCS-3 GMSK 448 352 296 272 + 24 MCS-2 MCS-1 224 176 Rate (kbit/s)
MCS-9 MCS-8 MCS-7 MCS-6
8PSK
59.2 54.4 44.8 29.6 27.2 22.4 17.6 14.8 13.6 11.2 8.8
NOTE
For 544 + 48 and 272 + 24 in the previous table, 544 and 272 indicate the significant bits, and 48 and 24 indicate the padding bits.
The initial coding schemes used in EDGE can be specified through the parameters Uplink Default MCS Type and Downlink Default MCS Type. When the EDGE service is used, whether the uplink/downlink is adjusted based on the signal transmission quality depends on the setting of the parameters Uplink Fixed MCS Type and Downlink Fixed MCS Type. Figure 20-2 shows the rates of GPRS channels and those of EDGE channels. Figure 20-2 Rates of GPRS channels and those of EDGE channels
kbit/s
60.0 50.0 40.0 30.0 20.0 12.2 10.0 0.0
CS-1 CS-2 CS-3 CS-4 MCS-1 MCS-2 MCS-3 MCS-4 MCS-5 MCS-6 MCS-7 MCS-8 MCS-9
59.2 54.4
GPRS EDGE
29.6 20.2 14.4 8.8 14.8 11.2 22.4 17.6
44.8
8.0
GMSK modulation
8PSK modulation
Issue 02 (2008-06-30)
20-7
20 EGPRS
20.4.4 Link Quality Control

This describes the link quality control. The link quality control enables the system to adapt to the radio transmission environment dynamically by changing modulation and coding schemes during data transmission, thus improving the link quality. EDGE uses a set of high-efficient link quality control algorithm. EDGE has two link quality control modes: Link Adaptation (LA) and Incremental Redundancy (IR). The link quality control mode is set through 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.
Basic Principle of LA
During data transmission, the sender retransmits the original data block or segments the original data block into two data blocks and then transmits them. The receiver need not restore the previous erroneous data blocks.
Basic Principle of IR
During data transmission, the sender does not consider the radio transmission environment at first and uses a high data rate coding scheme for the data transmission. Although the data rate is high, the capability of data protection is weak. If the data is received incorrectly, the sender retransmits additional coding information. The receiver combines the new information with the previous information and then performs decoding. The previous process is repeated until the decoding succeeds.
l
During uplink data transmission, the system notifies an MS to use the IR mode by setting RESEGMENT in the uplink resource assignment message to 0 (segmentation forbidden). In IR mode, the receiver should have sufficient memory to save the history information. If the network memory is insufficient, the system can notify the MS of the memory insufficiency by setting RESEGMENT in the UPLINK ACK/NACK message to 1. During downlink data transmission, if the memory of an MS is insufficient, the MS can send MS OUT OF MEMORY to the network through a DOWNLINK ACK/NACK message. Then, the network cannot use the IR mode in downlink data transmission.
20.4.5 Types of Preferred EGPRS Channels

This describes the types of preferred channels in EGPRS. The preferred channel types are as follows:
l
EGPRS dedicated channel EGPRS dedicated channels can be used by only EGPRS MSs. EGPRS preferred channel EGPRS preferred channels are preferentially used by EGPRS MSs. The EGPRS preferred channels can be used by GPRS MSs when the channels are in the idle state. When an EGPRS MS requests an EGPRS preferred channel, the GPRS MS that occupies the EGPRS preferred channel should be transferred to other channels. The signals of an EGPRS MS and those of a GPRS MS cannot be multiplexed onto one EGPRS preferred channel.
Normal EGPRS channel Normal EGPRS channels can be used by GPRS MSs and EGPRS MSs. GPRS channel
20-8
20 EGPRS
GPRS channels are used by GPRS MSs. If a cell is not configured with EGPRS channels, EGPRS MSs in the cell preferentially use GPRS channels to process GPRS services.
l
Non-GPRS channel Non-GPRS channels are not used for packet services.
When configuring Channel Type on the TRX, you can select the channel type through GPRS Channel Priority Type. When the system allocates PDCHs, the preferred channel type varies according to packet data services.
l
For the GPRS service, the GPRS channels are preferentially assigned. Then the normal EGPRS channels are assigned and finally the EGPRS preferred channels are assigned. For the EGPRS service, the EGPRS dedicated channels are preferentially assigned. Then the EGPRS preferred channels are assigned and finally the normal EGPRS channels are assigned.
On the normal EGPRS channel, the GPRS MS may use the uplink channel, and the EGPRS MS may use the downlink channel. The parameter Allow E Down G Up Switch can be set to avoid channel multiplexing. If you want to eliminate the possibility of EDGE/GPRS co-timeslot, do not configure normal EGPRS channels.
NOTE
Channels should be selected according to the preferred channel type. For example, if the channels on the TRX that supports EGPRS are configured as GPRS channels, these channels can be used for only GPRS services. EGPRS dedicated channels can be configured only as static channels. Other three types of preferred channels can be configured as static or dynamic channels.
20.4.6 CCCH 11Bit EGPRS Access

EDGE supports 11Bit EGPRS access on the CCCH. EDGE reduces the access delay and improves the access performance of the MS. The access process of the 11Bit EGPRS on the CCCH is as follows: 1. 2. The MS sends the 11bit EGPRS PAKCET CHANNEL REQUEST message on the CCCH for one phase packet access. The network assigns the EDGE channel for the MS through the IMMEDIATE ASSIGNMENT message. Therefore, the EGPRS TBF is established.
Whether to enable CCCH 11Bit EGPRS access depends on the setting of the parameter Support 11BIT EGPRS Access.
20.4.7 Assignment of Idle Timeslots

For packet data services, the Abis interface supports the mapping of several timeslots to one traffic channel. Then, the timeslots are divided and combined on the TX and RX ends. The data rate of each timeslot on the Abis interface is 16 kbit/s. In EDGE, the data rate can be 59.2 kbit/s. In GPRS, the CS-3/CS-4 coding scheme needs to be added with a subtimeslot. In EDGE, each PDCH can be added with three subtimeslots. EDGE coding schemes are MCS1 to MCS9. The number of Abis links required for different coding schemes is different, as described in Table 20-5.
20 EGPRS
Table 20-5 Coding schemes and number of required Abis links Coding Scheme MCS-1MCS-2 MCS-3MCS-6 MCS-7 MCS-8MCS-9 Number of Required Abis Links 1 2 3 4
The number of idle timeslots on the Abis interface requested during EDGE coding scheme adjustment is related to the coding scheme. As described in Table 20-5, when EDGE uses coding schemes MCS-3-MCS-6, an idle timeslot on the Abis interface is required. The idle timeslots on the Abis interface in the same BTS can be allocated to any PDCH on any TRX in the same cabinet group. The idle timeslot on the Abis interface is set through the parameter Idle Timeslots.
NOTE
l l l
When the Abis interface uses IP or HDLC transmission, there is no idle timeslot configuration. When the Flex Abis feature of the BTS is enabled, if the CS traffic is light, idle timeslots may not be configured and the EDGE service can still run normally. When the Flex Abis feature of the BTS is enabled, if the CS traffic is heavy, idle timeslots should be configured. Otherwise, the EDGE service may fail for a long time.
20.5 Capabilities
This describes the EDGE capabilities of the built-in PCU and external PCU.
Built-in PCU
The EDGE capabilities of the built-in PCU are as follows:
l
The system uses the resource pool redundancy configuration mode. The maximum configuration that the system can support is 8 + 1 = 9 GDPUPs. The maximum number of cells supported by each GDPUP is 1,024. The maximum number of activated PDCHs supported by each GDPUP is 1,024. All the channels support the MCS9 coding scheme. The maximum number of configurable PDCHs is 15,360. The maximum number of activated PDCHs in full configuration is 8,192. All the channels support the MCS9 coding scheme. The maximum throughput on the Gb interface is 512 Mbit/s. The maximum number of uplink PDCHs that can be used by a single MS is 4. The maximum number of downlink PDCHs that can be used by a single MS is 5. The maximum number of pairs of configured GFGUGs/GEPUGs are 8.
l l
l l
l l l l
20-10
Issue 02 (2008-06-30)
20 EGPRS
External PCU
The EDGE capabilities of the external PCU are as follows:
l l l l
The BSC supports 256 E1 lines on the Pb interface. Each GMPS/GEPS subrack supports 64 E1 lines on the Pb interface. Each GEIUP/GOIUP supports 32 E1 lines on the Pb interface. The GOIUP provides one STM-1 port, which carries 63 E1 links.
20.6 Implementation
EDGE implementation consists of configuring EDGE with the built-in PCU and configuring EDGE with the external PCU. 20.6.1 Configuring EGPRS (with Built-in PCU) This describes how to configure EDGE on the BSC6000 Local Maintenance Terminal. 20.6.2 Configuring EGPRS (with External PCU) This describes how to configure EDGE on the BSC6000 Local Maintenance Terminal.
20.6.1 Configuring EGPRS (with Built-in PCU)

This describes how to configure EDGE on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The system is configured to support GPRS. For details about how to configure GPRS with the built-in PCU, see 19.6.5 Configuring GPRS (with External PCU). The subrack-OSP mapping is configured. For details, refer to Configuring the SubrackOSP Mapping. The license is applied and activated. To apply for and activate the license, do as follows: 1. In the BSC6000V900R008 Exceptional Commercial License Application Template, fill in the following information.
Fill in the number of PDCHs to be purchased in the Number of resources column corresponding to the Maximum Number of PDCH Groups Activated in the Resource control items column. Fill in the number of TRXs to be purchased in the Number of resources column corresponding to the Number of the TRX Supporting EDGE in the Resource control items column.
2.
Procedure
Step 1 Configure site idle timeslot. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target BTS, and then choose Configure Site Idle Timeslot from the shortcut menu. A dialog box is displayed, as shown in Figure 20-3.
Issue 02 (2008-06-30)
20 EGPRS
2. 3.
NOTE
l l l
Idle Timeslots should be configured only when Trans Type of the BSC is set to TDM. When the Flex Abis feature of the BTS is enabled, if the CS traffic is light, idle timeslots may not be configured and the EDGE service can still run normally. When the Flex Abis feature of the BTS is enabled, if the CS traffic is heavy, idle timeslots should be configured. Otherwise, the EDGE service may fail for a long time.
Step 2 Configure the cell to support EDGE. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page, and then choose Set Cell Attributes from the shortcut menu. In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the Cells to be set list box, select the target cell, and then click Set Cell Attributes. A dialog box is displayed, as shown in Figure 20-4.
20-12
Issue 02 (2008-06-30)
20 EGPRS
4. 5.
Select EDGE Support. Click OK to end the configuration.
Step 3 Configure the channel type. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a TRX on the Management Tree tab page, and then choose Configure TRX Attributes from the shortcut menu. In the displayed dialog box, select the target TRX in the TRX view list box, and then click Configure TRX Attributes. In the displayed dialog box, click the Channel Attributes tab, as shown in Figure 20-5.
Issue 02 (2008-06-30)
20-13
20 EGPRS
Figure 20-5 Channel Attributes tab page
4.
Select Channel Number, and then select the channel type that supports packet services such as PDTCH or TCH Full Rate in the Channel Type drop-down list box. Then, set GPRS Channel Priority Type. Click OK to end the configuration.
5.
----End
20.6.2 Configuring EGPRS (with External PCU)

This describes how to configure EDGE on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The system is configured to support GPRS. For details about how to configure GPRS with the external PCU, refer to 19.6.5 Configuring GPRS (with External PCU). The subrack-OSP mapping is configured. For details, refer to Configuring the SubrackOSP Mapping. The license is applied and activated. To apply for and activate the license, do as follows: 1. In the BSC6000V900R008 Exceptional Commercial License Application Template, fill in the following information.
Fill in the number of PDCHs to be purchased in the Number of resources column corresponding to the Maximum Number of PDCH Groups Activated in the Resource control items column. Fill in the number of TRXs to be purchased in the Number of resources column corresponding to the Number of the TRX Supporting EDGE in the Resource control items column.
20-14
20 EGPRS
2.
Procedure
Step 1 Configure Site Idle Timeslot dialog box 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target BTS, and then choose Configure Site Idle Timeslot from the shortcut menu. A dialog box is displayed, as shown in Figure 20-6.
2. 3.
NOTE
l l l
Idle Timeslots should be configured only when Trans Type of the BSC is set to TDM. When the Flex Abis feature of the BTS is enabled, idle timeslots may not be configured and the EDGE service can still run normally,if the CS traffic is light. When the Flex Abis feature of the BTS is enabled, idle timeslots should be configured. Otherwise, the EDGE service may fail for a long time,if the CS traffic is heavy.
Step 2 Configure the cell to support EDGE. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page, and then choose Configure Cell Attributes from the shortcut menu. In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the Cells to be set list box, select the target cell, and then click Set Cell Attributes. A dialog box is displayed, as shown in Figure 20-7.
Issue 02 (2008-06-30)
20 EGPRS
4. 5.
Select EDGE Support. Click OK to end the configuration.
Step 3 Configure the channel type. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a TRX on the Management Tree tab page, and then choose Configure TRX Attributes from the shortcut menu. In the displayed dialog box, select the target TRX in the TRX view list box, and then click Configure TRX Attributes. In the displayed dialog box, click the Channel Attributes tab, as shown in Figure 20-8.
20-16
Issue 02 (2008-06-30)
20 EGPRS
Figure 20-8 Channel Attributes tab page
4. 5.
Select Channel Number, and then select PDTCH or Dynamic PDCH in the Channel Type drop-down list box. Then, set GPRS Channel Priority Type. Click OK to end the configuration.
----End

This lists the alarms and counters related to EDGE.
Alarms
The alarms related to EDGE consist of alarms related to the built-in PCU and alarms related to the external PCU, as listed in Table 20-6 and Table 20-7. Table 20-6 Alarms related to the built-in PCU Alarm ID 291 293 294 331 Alarm Name Cell Transmission Delay Abnormal Gb BC Faulty TRX Config Error NSVC Faulty
Issue 02 (2008-06-30)
20-17
20 EGPRS
Alarm ID 332 333 340 341 342 343 344
Alarm Name NSVL Faulty NSE Faulty Cell PS Service Faulty DSP Resource Overload PTP BVC Faulty NSVL Dynamic Configuration Process Failure FAULTY DSP OVER LIMIT
Table 20-7 Alarms related to the external PCU Alarm ID 104 128 Alarm Name All PBSLs in the PCU Are Faulty No Circuit Configured in the PCU
Counters
The counters related to EDGE consist of counters related to the built-in PCU and counters related to the external PCU, as listed in Table 20-8 and Table 20-9. Table 20-8 Counters related to the built-in PCU Counter A331 ZTA308H A031 L3188D A9201 A9202 A9203 Description Delivered Paging Messages for PS Service Immediate Assignment Requests per BSC (PS Service) SGSN-Initiated Paging Requests for PS Service PACKET CCCH LOAD IND Messages Sent on Abis Interface Number of Uplink EGPRS TBF Establishment Attempts Number of Successful Uplink EGPRS TBF Establishments Number of Failed Uplink EGPRS TBF Establishments due to No Channel
20-18
Issue 02 (2008-06-30)
20 EGPRS
Counter A9204 A9205 A9206
Description Number of Failed Uplink EGPRS TBF Establishments due to MS No Response Number of Uplink EGPRS TBF Normal Releases Number of Uplink EGPRS TBF Abnormal Releases due to N3101 Overflow (MS No Response) Number of Uplink EGPRS TBF Abnormal Releases due to N3103 Overflow (MS No Response) Number of Uplink EGPRS TBF Abnormal Releases due to SUSPEND Number of Uplink EGPRS TBF Abnormal Releases due to FLUSH Number of Uplink EGPRS TBF Abnormal Releases due to No Channel Total Number of Sampled Concurrent Uplink EGPRS TBFs Sampling Times of Concurrent Uplink EGPRS TBFs Average Number of Concurrent Uplink EGPRS TBFs Total Duration of Uplink EGPRS TBF (ms) Average Duration of Uplink EGPRS TBF (s) Number of Downlink EGPRS TBF Establishment Attempts Number of Successful Downlink EGPRS TBF Establishments Number of Failed Downlink EGPRS TBF Establishments due to No Channel Number of Failed Downlink EGPRS TBF Establishments due to MS No Response Number of Downlink EGPRS TBF Normal Releases Number of Downlink EGPRS TBF Abnormal Releases due to N3105 Overflow
A9207
A9208 A9209 A9210 A9211 A9212 AA9213 A9214 AA9215 A9301 A9302 A9303 A9304 A9305 A9306
Issue 02 (2008-06-30)
20-19
20 EGPRS
Counter A9307 A9308 A9309 A9310 A9311 AA9312 A9313 AA9314 L9201 L9202 L9203 L9204 L9205 L9206 L9207 L9208 L9209 L9210 L9211
Description Number of Downlink EGPRS TBF Abnormal Releases due to SUSPEND Number of Downlink EGPRS TBF Abnormal Releases due to FLUSH Number of Downlink EGPRS TBF Abnormal Releases due to No Channel Total Number of Sampled Concurrent Downlink EGPRS TBFs Sampling Times of Concurrent Downlink EGPRS TBFs Average Number of Concurrent Downlink EGPRS TBFs Total Duration of Downlink EGPRS TBF (ms) Average Duration of Downlink EGPRS TBF (s) Total Number of Uplink EGPRS RLC Data Blocks Total Number of Uplink EGPRS MCS1 RLC Data Blocks Total Number of Uplink EGPRS MCS2 RLC Data Blocks Total Number of Uplink EGPRS MCS3 RLC Data Blocks Total Number of Uplink EGPRS MCS4 RLC Data Blocks Total Number of Uplink EGPRS MCS5 RLC Data Blocks Total Number of Uplink EGPRS MCS6 RLC Data Blocks Total Number of Uplink EGPRS MCS7 RLC Data Blocks Total Number of Uplink EGPRS MCS8 RLC Data Blocks Total Number of Uplink EGPRS MCS9 RLC Data Blocks Total Number of Valid Uplink EGPRS MCS1 RLC Data Blocks
20-20
Issue 02 (2008-06-30)
20 EGPRS
Counter L9212 L9213 L9214 L9215 L9216 L9217 L9218 L9219 RL9220 RL9221 RL9222 RL9223 RL9224 RL9225 RL9226 RL9227 RL9228 L9229 L9230
Description Total Number of Valid Uplink EGPRS MCS2 RLC Data Blocks Total Number of Valid Uplink EGPRS MCS3 RLC Data Blocks Total Number of Valid Uplink EGPRS MCS4 RLC Data Blocks Total Number of Valid Uplink EGPRS MCS5 RLC Data Blocks Total Number of Valid Uplink EGPRS MCS6 RLC Data Blocks Total Number of Valid Uplink EGPRS MCS7 RLC Data Blocks Total Number of Valid Uplink EGPRS MCS8 RLC Data Blocks Total Number of Valid Uplink EGPRS MCS9 RLC Data Blocks Retransmission Rate of Uplink EGPRS MCS1 RLC Data Block (%) Retransmission Rate of Uplink EGPRS MCS2 RLC Data Block (%) Retransmission Rate of Uplink EGPRS MCS3 RLC Data Block (%) Retransmission Rate of Uplink EGPRS MCS4 RLC Data Block (%) Retransmission Rate of Uplink EGPRS MCS5 RLC Data Block (%) Retransmission Rate of Uplink EGPRS MCS6 RLC Data Block (%) Retransmission Rate of Uplink EGPRS MCS7 RLC Data Block (%) Retransmission Rate of Uplink EGPRS MCS8 RLC Data Block (%) Retransmission Rate of Uplink EGPRS MCS9 RLC Data Block (%) Number of MCS Upgrades on Uplink EGPRS TBF Number of MCS Degrades on Uplink EGPRS TBF
Issue 02 (2008-06-30)
20-21
20 EGPRS
Counter L9231 TL9232 TL9233 L9234 L9301 L9302 L9303 L9304 L9305 L9306 L9307 L9308 L9309 L9310 L9311 L9312 L9313 L9314 L9315
Description Number of Uplink EGPRS RLC Control Blocks Average Throughput of Uplink EGPRS RLC (kbit/s) Average Payload of Single Uplink EGPRS TBF (KB) Total Number of Uplink EGPRS TBFs Total Number of Downlink EGPRS RLC Data Blocks Total Number of Downlink EGPRS MCS1 RLC Data Blocks Total Number of Downlink EGPRS MCS2 RLC Data Blocks Total Number of Downlink EGPRS MCS3 RLC Data Blocks Total Number of Downlink EGPRS MCS4 RLC Data Blocks Total Number of Downlink EGPRS MCS5 RLC Data Blocks Total Number of Downlink EGPRS MCS6 RLC data blocks Total Number of Downlink EGPRS MCS7 RLC Data Blocks Total Number of Downlink EGPRS MCS8 RLC Data Blocks Total Number of Downlink EGPRS MCS9 RLC Data Blocks Total Number of Valid Downlink EGPRS MCS1 RLC Data Blocks Total Number of Valid Downlink EGPRS MCS2 RLC Data Blocks Total Number of Valid Downlink EGPRS MCS3 RLC Data Blocks Total Number of Valid Downlink EGPRS MCS4 RLC Data Blocks Total Number of Valid Downlink EGPRS MCS5 RLC Data Blocks
20-22
Issue 02 (2008-06-30)
20 EGPRS
Counter L9316 L9317 L9318 L9319 RL9320 RL9321 RL9322 RL9323 RL9324 RL9325 RL9326 RL9327 RL9328 L9329 L9330 L9331 L9332 TL9333 TL9334
Description Total Number of Valid Downlink EGPRS MCS6 RLC Data Blocks Total Number of Valid Downlink EGPRS MCS7 RLC Data Blocks Total Number of Valid Downlink EGPRS MCS8 RLC Data Blocks Total Number of Valid Downlink EGPRS MCS9 RLC Data Blocks Retransmission Rate of Downlink EGPRS MCS1 RLC Data Blocks (%) Retransmission Rate of Downlink EGPRS MCS2 RLC Data Blocks (%) Retransmission Rate of Downlink EGPRS MCS3 RLC Data Blocks (%) Retransmission Rate of Downlink EGPRS MCS4 RLC Data Blocks (%) Retransmission Rate of Downlink EGPRS MCS5 RLC Data Blocks (%) Retransmission Rate of Downlink EGPRS MCS6 RLC Data Blocks (%) Retransmission Rate of Downlink EGPRS MCS7 RLC Data Blocks (%) Retransmission Rate of Downlink EGPRS MCS8 RLC Data Blocks (%) Retransmission Rate of Downlink EGPRS MCS9 RLC Data Blocks (%) Number of MCS Upgrades on Downlink EGPRS TBF Number of MCS Degrades on Downlink EGPRS TBF Number of Downlink EGPRS RLC Control Blocks Number of Downlink EGPRS RLC Dummy Blocks Average Throughput of Downlink EGPRS RLC (kbit/s) Average Payload of Single Downlink EGPRS TBF (KB)
Issue 02 (2008-06-30)
20-23
20 EGPRS
Counter L9335 S9101 S9102 S9103 S9104 S9105 S9106 S9107 S9108 S9109 S9110 S9111 S9112 S9113 S9114 S9115 S9116 S9117 S9118 S9119 S9120 S9121 S9122 S9123 S9124 S9125 S9126 S9127 S9128 S9129
Description Total Number of Downlink EGPRS TBFs Number of Times 8PSK_MEAN_BEP=1 Number of Times 8PSK_MEAN_BEP=2 Number of Times 8PSK_MEAN_BEP=3 Number of Times 8PSK_MEAN_BEP=4 Number of Times 8PSK_MEAN_BEP=5 Number of Times 8PSK_MEAN_BEP=6 Number of Times 8PSK_MEAN_BEP=7 Number of Times 8PSK_MEAN_BEP=8 Number of Times 8PSK_MEAN_BEP=9 Number of Times 8PSK_MEAN_BEP=10 Number of Times 8PSK_MEAN_BEP=11 Number of Times 8PSK_MEAN_BEP=12 Number of Times 8PSK_MEAN_BEP=13 Number of Times 8PSK_MEAN_BEP=14 Number of Times 8PSK_MEAN_BEP=15 Number of Times 8PSK_MEAN_BEP=16 Number of Times 8PSK_MEAN_BEP=17 Number of Times 8PSK_MEAN_BEP=18 Number of Times 8PSK_MEAN_BEP=19 Number of Times 8PSK_MEAN_BEP=20 Number of Times 8PSK_MEAN_BEP=21 Number of Times 8PSK_MEAN_BEP=22 Number of Times 8PSK_MEAN_BEP=23 Number of Times 8PSK_MEAN_BEP=24 Number of Times 8PSK_MEAN_BEP=25 Number of Times 8PSK_MEAN_BEP=26 Number of Times 8PSK_MEAN_BEP=27 Number of Times 8PSK_MEAN_BEP=28 Number of Times 8PSK_MEAN_BEP=29
20-24
Issue 02 (2008-06-30)
20 EGPRS
Counter S9130 S9131 S9132
Description Number of Times 8PSK_MEAN_BEP=30 Number of Times 8PSK_MEAN_BEP=31 Number of Times 8PSK_MEAN_BEP=32
Table 20-9 Counters related to the external PCU Counter AR3015A AR3015B CR3015 AR3025A AR3025B CR3025 R3005A R3005B R3006A R3006B CR3005 CR3006 AL8351 AL8353 AL8354 Description Mean Number of Dynamically Configured Channels (EDGE) (900/850 Cell) Mean Number of Dynamically Configured Channels (EDGE) (1800/1900 Cell) Mean Number of Dynamically Configured Channels (EDGE) Mean Number of Available Channels (EDGE) (900/850 Cell) Mean Number of Available Channels (EDGE) (1800/1900 Cell) Mean Number of Available Channels (EDGE) Number of Initially Configured Channels (Static EDGE) (900/850 Cell) Number of Initially Configured Channels (Static EDGE) (1800/1900 Cell) Number of Initially Configured Channels (Dynamic EDGE) (900/850 Cell) Number of Initially Configured Channels (Dynamic EDGE) (1800/1900 Cell) Number of Initially Configured Channels (Static EDGE) Number of Initially Configured Channels (Dynamic EDGE) Mean Number of Faulty Circuits on the Pb Interface Mean Number of Blocked Circuits on the Pb Interface Mean Number of Idle Circuits on the Pb Interface
Issue 02 (2008-06-30)
20 EGPRS
Counter AL8355 AL8352 L0387 L8387 R3140 R3141 AR3011A AR3011B CR3011 AR3021A AR3021B CR3021 R3001A R3001B R3002A R3002B CR3001 CR3002 ZTA331
Description Mean Number of Busy Circuits on the Pb Interface Mean Number of Circuits in Maintenance State on the Pb Interface Total Number of Messages Received from PCU Messages Received from a PCU Requests for TCH from the PCU Successful Requests for TCH from the PCU Mean Number of Dynamically Configured Channels (PDCH) (900/850 Cell) Mean Number of Dynamically Configured Channels (PDCH) (1800/1900 Cell) Mean Number of Dynamically Configured Channels (PDCH) Mean Number of Available Channels (PDCH) (900/850 Cell) Mean Number of Available Channels (PDCH) (1800/1900 Cell) Mean Number of Available Channels (PDCH) Number of Initially Configured Channels (Static PDCH) (900/850 Cell) Number of Initially Configured Channels (Static PDCH) (1800/1900 Cell) Number of Initially Configured Channels (Dynamic PDCH) (900/850 Cell) Number of Initially Configured Channels (Dynamic PDCH) (1800/1900 Cell) Number of Initially Configured Channels (Static PDCH) Number of Initially Configured Channels (Dynamic PDCH) Paging Requests on the Abis Interface per BSC (PS Service)
20-26
Issue 02 (2008-06-30)
20 EGPRS
Counter ZTA301H ZTL3188D
Description Immediate Assignment Commands per BSC (PS Service) PCH Overloads due to PS Service Counted through the Indications from the Abis Interface per BSC
20.8 References
The references indicate the documents about EDGE from the related standard organizations. The references are as follows: 3GPP TS 50.059 "Enhanced Data rates for GSM Evolution (EDGE); Project scheduling and open issues for EDGE"
Issue 02 (2008-06-30)
20-27
21 Co-BCCH Cell
21
About This Chapter
Co-BCCH Cell
21.1 Overview This describes the definition and purposes of the Co-BCCH cell. The Co-BCCH cell adopts the dual-band technique and features expanded cell capacity and minimized handover occurrences. 21.2 Availability This lists the NEs, software, and hardware configuration of the BTS required for the implementation of the Co-BCCH cell. 21.3 Impact This describes the impact of the Co-BCCH cell on system performance. 21.4 Technical Description This describes the implementation of channel assignment and handover. 21.5 Capabilities None 21.6 Implementation This describes the configuration principle, configuration preparation, scenario analysis, configuration procedure, and deactivation of the Co-BCCH cell. 21.7 Maintenance Information This lists the performance counters related to the Co-BCCH cell. 21.8 References
Issue 02 (2008-06-30)
21-1
21 Co-BCCH Cell
21.1 Overview
This describes the definition and purposes of the Co-BCCH cell. The Co-BCCH cell adopts the dual-band technique and features expanded cell capacity and minimized handover occurrences.
Definition
The Co-BCCH cell refers to a cell where the GSM900&DCS1800 TRXs coexist (or GSM850&DCS1800, GSM850&PCS1900). The TRXs on the two bands use one main BCCH. In a dual-band network, a dual-band MS can work on either of the bands. A single-band MS can also work normally on its band. The GSM900 band consists of the P-GSM, E-GSM, and R-GSM.
Purposes
The Co-BCCH cell improves the continuous coverage and sparse coverage in hot spots. With the rapid increase of mobile users, the dual-band network solution becomes a growing trend around the globe. The dual-band network has the following three networking modes:
l l l
Independent MSC Networking Co-MSC Independent BSC Networking Co-BSC Networking
The highlight of the dual-band network with the Co-BCCH cell is that the primary frequency band and the secondary frequency band are the same and they coexist in one cell. The secondary frequency band is the extension of the primary frequency band. This feature eliminates the technical bottleneck on cell reselection and handover in other networking modes. Specifically, the advantages of the dual-band network with the Co-BCCH cell are listed as follows:
l
The capacity of the cell is expanded and the occurrences of cell reselection for the MS are reduced. For example, a site is configured with a GSM900 cell and a DCS1800 cell. Each cell is configured with two TRXs. You can obtain the data as listed in Table 21-1 when querying the ERLANG B. Table 21-1 Data in ERLANG B Network ing Mode Common dual-band network Dual-band network with CoBCCH cell Quantity of BCCHs 2 Quantity of SDCCHs 2 Quantity of TCHs 28 Call Loss Rate 2% Traffic Volume
16.40 ERL
29
2%
21.04 ERL
21-2
Issue 02 (2008-06-30)
21 Co-BCCH Cell
The inter-cell handover occurrences are reduced. When an MS initiates a handover request, the MS is handed over to the channels on the other frequency band in the serving cell.
The number of the BCCH TRXs is reduced and the interference caused by the BCCH TRXs is reduced. Convenient maintenance The number of cells and neighboring cells of the Co-BCCH cell network is less than that of the common dual-band network. Thus, the maintenance workload is reduced.
The system assigns channels on different frequency bands to the MS based on the RX level, RX quality and TA value. The underlaid subcell is used for cell coverage and the overlaid subcell is used for traffic absorption. Thus, the cell coverage is maximized and the capacity balance between the overlaid subcell and the underlaid subcell is maintained.
Terms
Terms M criteria Definition Indicates a criteria that selects only the neighbor cells of which the RX level is higher than the lowest MS 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. 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. Indicates the frequency band containing the main BCCH frequency in a Co-BCCH cell. Indicates the frequency band that does not contain the main BCCH frequency in a Co-BCCH cell.
ERLANG B
Primary frequency band Secondary frequency band

Acronyms and Abbreviations BCCH SDCCH PBGT BQ MR TA Full Spelling Broadcast Control Channel Stand-alone Dedicated Control Channel Power Budget Bad Quality Measurement Report Timing Advance
Issue 02 (2008-06-30)
21-3
21 Co-BCCH Cell
21.2 Availability
This lists the NEs, software, and hardware configuration of the BTS required for the implementation of the Co-BCCH cell.
NEs Involved
Table 21-2 lists the network elements involved in the Co-BCCH cell. Table 21-2 NEs involved in Co-BCCH cell MS NOTE
BTS
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 21-3 lists the NEs and software versions that support Co-BCCH cell. Table 21-3 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012 DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM BTS2X BTS3001C BTS3002C
21-4
Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases All releases All releases All releases
Issue 02 (2008-06-30)
21 Co-BCCH Cell
Product BTS3X Double-transceiver BTSs
Version All releases All releases
Miscellaneous
The BTS must meet the following requirements if you configure Co-BCCH.
l
Number of TRXs The number of GSM900 TRXs or DCS1800 TRXs should be less than or equal to four in a Co-BCCH cell. If the number exceeds four, enough antenna output ports and antenna models are required. The coverage of the TRXs on the same frequency band should be the same in the case of antenna installation.
Antenna types and azimuth
If the GSM900 TRX and the DCS1800 TRX use the same antenna, the dual-band antenna is required. If the GSM900 TRX and the DCS1800 TRX use the antenna respectively, either the dual-band antenna or the single-band antenna is allowed. When the sing-band antenna is used, the azimuth of the antennas used for the GSM900 TRX and the DCS1800 TRX in the same cell must be the same.
Type of the combiner As a combiner cannot support the GSM900 and the DCS1800 at the same time, the GSM900 TRX and the DCS1800 TRX must use different combiners.
Combination mode The combination mode of the TRXs on the same frequency band in a cell must be the same. Otherwise, the TX power levels of the TRXs on the same frequency band in a cell are not consistent, and the coverage of these TRXs is not consistent. Thus, the Co-BCCH cell cannot be enabled because of a 3-layer or more-layer concentric cell.
21.3 Impact
This describes the impact of the Co-BCCH cell on system performance.

The impact of the Co-BCCH cell on system performance is as follows:
l
Co-BCCH cell can be applied to specific scenarios only. If Co-BCCH is applied to unqualified scenarios, the network KPI is deteriorated. For details of the application scenarios of the Co-BCCH, refer to 21.6.3 Risk Analysis of the Configuration Scenarios.
The neighboring cell of the Co-BCCH cell is limited. The neighboring cell of the Co-BCCH cell cannot be GSM900 cell or DCS1800 cell. Otherwise, the traffic volume is unbalanced.
Issue 02 (2008-06-30)
21-5
21 Co-BCCH Cell
NOTE
If the GSM900 cell and the DCS1800 cell are at the same layer, they can be neighboring cell of the Co-BCCH cell. For details of network layer and network hierarchy, refer to 7.3.2.10 Fast-Moving Micro Cell Handover.
l
The configuration of network optimization parameters of the Co-BCCH cell is more difficult than that of the common cell.

The Co-BCCH cell and the double-timeslot cell cannot coexist.

This describes the implementation of channel assignment and handover. 21.4.1 GSM900/DSC1800 Co-BCCH Cell Channel Assignment This describes the Co-BCCH cell channel assignment. Channel assignment strategy of the CoBCCH cell complies with the channel assignment algorithm of the concentric cell and is associated with the frequency band supported by the MS. 21.4.2 GSM900/DCS1800 Co-BCCH Cell Handover This describes the GSM900/DCS1800 Co-BCCH cell handover. The Co-BCCH cell handover is based on the handover algorithm of the concentric cell.
21.4.1 GSM900/DSC1800 Co-BCCH Cell Channel Assignment

This describes the Co-BCCH cell channel assignment. Channel assignment strategy of the CoBCCH cell complies with the channel assignment algorithm of the concentric cell and is associated with the frequency band supported by the MS. The GSM900&DCS1800 (or GSM850&DCS1800, GSM850&PCS1900) Co-BCCH cell is realized based on the principles of the concentric cell, which are described as follows:
l l
GSM900 (or GSM850) TRXs are configured in the underlaid subcell for network coverage. DCS1800 (or PCS1900) TRXs are configured in the overlaid subcell for traffic absorption.
Therefore, the channel assignment of the Co-BCCH cell should comply with the channel assignment strategy of the concentric cell. Before the channel assignment, however, the network needs to determine the frequency bands supported by the MS. If the MS supports the bands in the underlaid and overlaid subcell, the channel assignment strategy of the concentric cell is applied. Otherwise, the network assigns only the channels in the underlaid subcell to the MS.
Immediate Assignment
In the immediate assignment procedure, the BSC does not receive any information about the MS. If TA exists, the BSC assigns underlaid or overlaid channels to the MS based on TA. The BSC preferentially assigns the channels in the underlaid subcell to the MS to ensure that the conversation can be established.
Assignment
In the assignment procedure, the channel assignment is related to MS classmark 3.

l
21 Co-BCCH Cell
If the BSC does not obtain MS classmark 3, or if MS classmark 3 indicates that the MS supports only the underlaid frequency band, then the BSC assigns only the underlaid channels to the MS. If MS classmark 3 indicates that the MS supports the underlaid and overlaid frequency bands, the BSC assigns underlaid or overlaid channels to the MS based on Assign Optimum Layer and Assign-optimum-level Threshold.
Incoming Internal Inter-Cell Handover

In the incoming internal inter-cell handover procedure, the channel assignment is related to MS classmark 3.
l
If the BSC does not obtain MS classmark 3, or if MS classmark 3 indicates that the MS supports only the underlaid frequency band, then the BSC assigns only the underlaid channels to the MS. If MS classmark 3 indicates that the MS supports the underlaid and overlaid frequency bands, the BSC assigns underlaid or overlaid channels to the MS based on Pref. Subcell in HO of Intra-BSC.
Because the inter-cell handover is generally triggered on the cell edge, you are advised to set the Pref. Subcell in HO of Intra-BSC to Underlaid Subcell.
Incoming External Inter-Cell Handover

In the incoming external inter-cell handover procedure, the channel assignment is related to MS classmark 3.
l
If the BSC does not obtain MS classmark 3, or if MS classmark 3 indicates that the MS supports only the underlaid frequency band, then the BSC assigns only the underlaid channels to the MS. If MS classmark 3 indicates that the MS supports the underlaid and overlaid frequency bands, the BSC assigns underlaid or overlaid channels to the MS based on Incoming-toBSC HO Optimum Layer.
Because the inter-cell handover is generally triggered on the cell edge, you are advised to set the Incoming-to-BSC HO Optimum Layer to Underlaid Subcell.
21.4.2 GSM900/DCS1800 Co-BCCH Cell Handover

This describes the GSM900/DCS1800 Co-BCCH cell handover. The Co-BCCH cell handover is based on the handover algorithm of the concentric cell.
Neighbor Cell Selection

Based on the M criteria, the actual RX level of the serving cell is used for the handover decision and the RX level of the neighbor cells is used for neighbor cell queuing, no matter the MS is located in the overlaid subcell or the underlaid subcell. When the MS is in the overlaid subcell, the underlaid subcell is handled as a special neighbor cell.
Handover Within an Enhanced Concentric Cell

The underlaid subcell can provide better speech quality in a concentric cell. Therefore, the utilization ratio of the underlaid subcell is maximized.
21 Co-BCCH Cell
The underlaid-to-overlaid subcell handover occurs only when the traffic volume in the underlaid cell is high, the RX level of the MS is high, the RX quality of the MS is good, and the TA value is low. In other words, all the following conditions must be met:
l
DL RX Level UtoO HO Received Level Threshold This condition is controlled by RX_LEV for UO HO Allowed. DL RX Quality < RX_QUAL Threshold This condition is controlled by RX_QUAL for UO HO Allowed. TA < (TA Threshold TA Hysteresis) This condition is controlled by TA for UO HO Allowed. Traffic of the underlaid subcell > Traffic Thrsh. of Underlaid Subcell This condition is controlled by Underlaid Subcell HO Step Period (s) and Underlaid Subcell HO Step Level.
If the serving cell has the highest priority in the neighbor cell queue, the overlaid-to-underlaid subcell handover occurs when the RX level of the MS, the RX quality of the MS, or the TA deteriorates. In other words, one of the following conditions should be met:
l
DL RX Level < OtoU HO Received Level Threshold This condition is controlled by RX_LEV for UO HO Allowed. DL RX Quality RX_QUAL Threshold This condition is controlled by RX_QUAL for UO HO Allowed. TA (TA Threshold TA Hysteresis) This condition is controlled by TA for UO HO Allowed.
If the serving cell does not have the highest priority in the neighbor cell queue, the MS is handed over to another neighbor cell.
Inter-Subcell Handover
The actual RX level of the cell is used for all the handover decision algorithms except the PBGT handover decision algorithm. The PBGT algorithm calculates the path loss of the neighbor cell at the same layer and hierarchy by using the RX level of the underlaid cell for handover decision. Because of fast fading of the signal level transmitted by the DCS1800 TRXs in the overlaid subcell, the handover decision based on the actual RX level in the overlaid subcell is improper when compared with the RX level in a neighbor cell. To ensure the accuracy of the PBGT handover decision, the handover decision should be based on the RX level in the underlaid subcell. For the incoming inter-cell handover and the incoming-to-BSC handover in the Co-BCCH cell, to avoid a low handover success rate due to inaccurate signal level of the target cell, set Pref. Subcell in HO of Intra-BSC and Incoming-to-BSC HO Optimum Layer to Underlaid Subcell.
21.5 Capabilities
None
21-8
Issue 02 (2008-06-30)
21 Co-BCCH Cell
21.6 Implementation
This describes the configuration principle, configuration preparation, scenario analysis, configuration procedure, and deactivation of the Co-BCCH cell. 21.6.1 Configuration Principles This describes the configuration principles of the Co-BCCH cell. 21.6.2 Preparations for the Configuration This describes the preparations for configuring the Co-BCCH cell. You are required to be familiar with the related information based on which the parameter configuration is performed. 21.6.3 Risk Analysis of the Configuration Scenarios This describes the risk analysis of the configuration scenarios. The configuration scenarios consist of common and special scenarios. 21.6.4 Configuring the Co-BCCH Cell This describes how to configure the Co-BCCH cell on the BSC6000 Local Maintenance Terminal. 21.6.5 Deactivating the Co-BCCH Cell This describes how to deactivate the Co-BCCH cell on the BSC6000 Local Maintenance Terminal.
21.6.1 Configuration Principles

This describes the configuration principles of the Co-BCCH cell. A Co-BCCH cell consists of an overlaid subcell and an underlaid subcell. The specific band configuration is as follows:
l
If the overlaid subcell is configured with the DCS1800 TRX, the underlaid subcell is configured with the GSM900 or GSM850 TRX. If the overlaid subcell is configured with the PCS1900 TRX, the underlaid subcell is configured with the GSM850 TRX.
NOTE
The path loss of the DCS1800 TRX is fast. At the distance of 0.5 to 1 km, the signal power of the DCS1800 TRX is about 15 dB less than the signal power of the GSM900 TRX.
Configure the Co-BCCH cell based on the following principles:

l
Generally, do not assign the overlaid subcell channel to a call, do not assign the incoming inter-cell handover request directly to the overlaid subcell, and do not forcibly assign a call beyond coverage of the DCS1800 TRX to the overlaid subcell. Properly assign the traffic volume in the underlaid subcell and the overlaid subcell to maintain the traffic balance between the overlaid subcell and the underlaid subcell. Configure the BCCH in the GSM900 TRX. The priority of the TRX types from high to low is: P-GSM, E-GSM, and R-GSM. Configure the SDCCH, PDCH, and BCCH in the same TRX. The frequency hopping between the GSM900 frequencies and the DCS1800 frequencies is not allowed. The frequency hopping between frequencies within the same frequency band is allowed.
l l
Issue 02 (2008-06-30)
21 Co-BCCH Cell
l
Prevent a multi-layer concentric cell due to inconsistent combination mode of the TRXs on the same frequency band. A multi-layer concentric cell deteriorates the network KPI, such as handover success rate and assignment success rate.
21.6.2 Preparations for the Configuration

This describes the preparations for configuring the Co-BCCH cell. You are required to be familiar with the related information based on which the parameter configuration is performed. Get familiar with the state of the current cell, which includes the following items:
l l l l l
User distribution and traffic volume in the coverage area of the site Ratio of the coverage of the DCS1800/PCS1900 TRX to the coverage of the entire cell Ratio of the coverage of the GSM900/GSM850 TRX to the coverage of the entire cell Whether the GSM900/GSM850 TRXs can carry all the traffic in the cell. Number of the GSM900/GSM850 TRXs and the DCS1800/PCS1900 TRXs. Whether the frequency reuse on the GSM900/GSM850 band is tight and whether the interference exists.
Pay attention to the following restrictions on network planning:

l
Number of TRXs
If the traffic is distributed mainly in the overlaid subcell and if the congestion is unlikely to occur in the underlaid subcell, the number of TRXs configured in the underlaid subcell can be small. If the traffic volume in the underlaid subcell is high, the TRXs in the underlaid subcell should outnumber or be equal to the TRXs in the overlaid subcell to prevent the congestion in the underlaid subcell. If the TRXs in the underlaid subcell are not enough, the TRXs in a fully-loaded underlaid subcell are likely to be congested in high traffic hours. This deteriorates the network KPIs, such as TCH Seizure Success Rate and handover success ratio. This factor is neglectable if the Co-BCCH cell is not adjacent to two or more singleband cells at the same time. If the Co-BCCH cell is adjacent to two single-band cells using the two bands of the CoBCCH cell at the same time, you should consider the network hierarchy.

Neighbor cell
This factor is neglectable if the Co-BCCH cell has a low priority. If the Co-BCCH cell is adjacent to two single-band cells using the two bands of the Co-BCCH cell at the same time, you should consider the network hierarchy.
You should consider the traffic load of neighbor cells if the Co-BCCH cell has a high priority. If the traffic load of neighbor cells is high, the traffic distributed on edge of a common cell is absorbed by the Co-BCCH cell. Thus, the TRXs in the underlaid subcell are likely to be congested and the network KPIs, such as TCH Seizure Success Rate and handover success ratio are deteriorated. In this case, the Co-BCCH cell is not recommended. If the Co-BCCH cell has to be used, you should analyze the traffic distribution based on the congestion conditions in the underlaid subcell and then adjust the handover parameters of related cells. The purpose is to prevent the calls on edge of a common cell from being handed over to the Co-BCCH cell.
21-10
21 Co-BCCH Cell
21.6.3 Risk Analysis of the Configuration Scenarios

This describes the risk analysis of the configuration scenarios. The configuration scenarios consist of common and special scenarios. In the Co-BCCH cell, two types of TRXs with different coverage capabilities are configured. Therefore, the traffic volume of the overlaid and underlaid subcells should be properly assigned without deteriorating the network KPIs. The traffic assignment of the overlaid and underlaid subcells is influenced by two factors. One is the number of TRXs in the overlaid and underlaid subcells, and the other is the actual coverage of the overlaid and underlaid subcells (represented by the inter-site distance).
Risk Analysis in Common Scenarios

Table 21-4 lists the risk analysis in common scenarios. Table 21-4 Risk analysis in common scenarios N o. 1 Scenario Descriptio n The intersite distance is within 800 m. Scenario Analysis Risk Solution
The coverage capability of the DCS1800 TRXs is equivalent to that of the GSM900 TRXs. Therefore, the underlaidto-overlaid or overlaid-tounderlaid handover in the Co-BCCH cell is unlikely to fail.
There is no risk, and the CoBCCH cell can be enabled.
None
Issue 02 (2008-06-30)
21-11
21 Co-BCCH Cell
N o. 2
Scenario Descriptio n
l
Scenario Analysis
Risk
Solution
The intersite distance is from 800 m to 1,600 m. The number of TRXs in the underlaid subcell is equal to or more than the number of TRXs in the overlaid subcell.
The overlaid subcell only covers about half of the coverage area of a CoBCCH cell. The underlaid subcell configured with enough TRXs can cover the remaining area of a CoBCCH cell. Therefore, the risk is low.
The risk is small, and the Co-BCCH cell can be enabled.
Assigns enough traffic volume to the underlaid subcell with precondition that no congestion occurs in the underlaid subcell. Thus, the risk of underlaid-to-overlaid handover in high traffic hours is minimized. Adjust UtoO HO Received Level Threshold to arrange the traffic of the overlaid and underlaid subcells.
l
If the value of this parameter is reduced, the number of underlaid subcell to overlaid subcell handovers increases. If the value of this parameter is increased, the number of underlaid subcell to overlaid subcell handovers decreases.
21-12
Issue 02 (2008-06-30)
21 Co-BCCH Cell
N o. 3
l
Scenario Analysis
Risk
Solution
The intersite distance is from 800 m to 1,600 m. The number of TRXs in the underlaid subcell is less than the number of TRXs in the overlaid subcell.
The overlaid subcell only covers about half of the coverage area of a CoBCCH cell. The underlaid subcell with few TRXs may not (or just be able to) cover the remaining area of a Co-BCCH cell. Therefore, most of the traffic is handed over to the overlaid subcell in high traffic hours. Possible risks are as follows:
l
Certain calls beyond the coverage of the overlaid subcell are likely to be handed over to the overlaid subcell and the handover fails. With the increase of cell traffic, the underlaid subcell becomes badly congested while the overlaid subcell remains idle. In addition, the performance indicators, such as the underlaidto-overlaid handover success rate and the DCS1800 channel seizure success rate are deteriorated.
The risk is medium, and you are advised not to enable the Co-BCCH. If you enable the Co-BCCH, you are advised to enable halfrate channels in the underlaid subcell or to add underlaid TRXs.
Enable the half-rate services or increase the TRXs in the underlaid subcell.
Issue 02 (2008-06-30)
21-13
21 Co-BCCH Cell
N o. 4
l
Scenario Analysis
Risk
Solution
The intersite distance is more than 1,600 m. The number of TRXs in the underlaid subcell is equal to or more than the number of TRXs in the overlaid subcell.
The overlaid subcell covers less than half of the coverage area of a CoBCCH cell and the underlaid subcell is configured with enough TRXs. Based on the quantity and distribution of users, either of the following scenarios may occur:
l
The risk is medium.

l
None
For scenario 1, the CoBCCH can be enabled. For scenario 2, you are advised not to enable the Co-BCCH. If you enable the CoBCCH, you are advised to enable halfrate channels in the underlaid subcell or to add underlaid TRXs.
Scenario 1 Most users are in the overlaid subcell. The TRXs of the underlaid subcell can carry the traffic in coverage of the underlaid subcell. In this situation, the underlaid subcell should carry most of the traffic to reduce the risk cause by the underlaidto-overlaid handover in high traffic hours. Scenario 2 Users are distributed evenly and the underlaid subcell TRXs cannot (or just be able to) carry the traffic in the coverage area of the underlaid subcell. Thus, the underlaid subcell becomes badly congested and the overlaid subcell remains idle. In addition, the performance indicators, such as the underlaidto-overlaid handover success rate and the DCS1800 channel seizure success rate are deteriorated.
21-14
Issue 02 (2008-06-30)
21 Co-BCCH Cell
N o. 5
l
Scenario Analysis
Risk
Solution
The intersite distance is more than 1,600 m. The number of TRXs in the underlaid subcell is less than the number of TRXs in the overlaid subcell.
The overlaid subcell covers less than half of the coverage area of a CoBCCH cell. The underlaid subcell with few TRXs cannot (or just be able to) carry the traffic in the coverage of the underlaid subcell. Possible risks are as follows:
l
The risk is large, and the CoBCCH cannot be enabled.
Enable the half-rate services or increase the TRXs in the underlaid subcell.
The underlaid subcell is badly congested. The overlaid subcell remains idle. The underlaid-tooverlaid handover success rate and the DCS1800 channel seizure success rate are deteriorated.
The methods for determining the risks are as follows:

l
In a common dual-band network, if the congestion does not occur in the overlaid or underlaid subcell, the related performance indicators have no change after the Co-BCCH cell is enabled. In a common dual-band network, if the congestion in the GSM900 subcell occurs at an earlier time than in the DCS1800 subcell, a forcible traffic transfer from the GSM900 subcell to the DCS1800 subcell is likely to deteriorate the KPIs. In this case, related performance indicators are deteriorated if the Co-BCCH cell is enabled. For example, the underlaid-to-overlaid handover success rate and the DCS1800 channel seizure success rate are reduced.
Risk Analysis in Special Scenarios

Use the following methods to eliminate problems which may occur when the Co-BCCH cell is enabled in special scenarios:
l
The TRXs number in the overlaid and underlaid subcells is equivalent and most of the traffic should be assigned in the overlaid subcell. You can lower the value of UtoO HO Received Level Threshold to increase the traffic in the overlaid subcell. To avoid ping-pong handovers because of signal level fluctuation, the value of OtoU HO Received Level Threshold should be less than 25.
Severe interference exists in the GSM900 subcell.
Issue 02 (2008-06-30)
21-15
21 Co-BCCH Cell
You can suppress the interference to some extent by adjusting the parameters related to Concentric Data. When the inter-site distance is less than 1,000 m, add the traffic in the overlaid subcell.
NOTE
You can determine that the GSM900 channel is seriously interfered if the interference band is high, the RX quality is bad, and the call drop rate is 1.2 times or more than the call drop rate of the DSC1800 channel.
l
In a common dual-band network, only few cells are configured to be the Co-BCCH cells. The neighbor cells are single-band or dual-band cells. In a common dual-band network, the DCS1800 cell is at Level 2 and the GSM900 cell is at level 3. That is, the DCS1800 cell level is higher than the GSM900 cell level. In this situation, the following may occur when the Co-BCCH cell is enabled:
If the Co-BCCH cell is set to level 2, the traffic absorption capability of the GSM900 TRX becomes enhanced. The traffic of the neighbor cells is absorbed. Thus, the traffic volume of the cell increases sharply and related performance indicators are deteriorated. If the Co-BCCH cell is set to level 3, the traffic in the coverage of the DCS1800 TRX is absorbed by the neighbor cells. The cell traffic volume is decreased.
To avoid these risks, you must enable the Co-BCCH cell in the neighbor sites.
21.6.4 Configuring the Co-BCCH Cell

This describes how to configure the Co-BCCH cell on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 Add a Co-BCCH cell 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target BTS and then choose Add Cell on the shortcut menu. The Add Cell dialog box is displayed. Click Add Cell. A dialog box is displayed, as shown in Figure 21-1. Figure 21-1 Add New Cell dialog box
2.
21-16
Issue 02 (2008-06-30)

NOTE
21 Co-BCCH Cell
Figure 21-1 takes an example of external PCU. When the PCU is in built-in mode, there is no PCU Name in Figure 21-1.
3.
In Figure 21-1, set Frequency Band to GSM900&DCS1800 or GSM850&DCS1800, and then click OK. The Add Cell dialog box is returned.
NOTE
If you select GSM850&PCS1900, you must set High Frequency Band to PCS1900, as shown in Figure 50-1 of 50.4.1 Configuring Intelligent Power Consumption Decrease.
4. 5.
Click Next. The Set Site Attributes dialog box is displayed. Select a site from the Site List, and then click Set Site Device to set related parameters.
NOTE
You must set Add Chain and Manual Abis according to transmission path and customer requirements.
Step 2 Configure cell attributes 1. Click Next. The Set Cell Attributes dialog box is displayed. Select cells from the Cells to be set list box, and then click Set Cell Attributes. A dialog box is displayed, as shown in Figure 21-2.
Issue 02 (2008-06-30)
21-17
21 Co-BCCH Cell
2. 1.
Set BCCH IUO Attribute. In the dialog box shown in Figure 21-2, click Frequency Config. A dialog box is displayed, as shown in Figure 21-3.
Step 3 Assign TRXs for the add cell
21-18
Issue 02 (2008-06-30)
21 Co-BCCH Cell
Figure 21-3 Set Cell Frequency dialog box
2.
Select the GSM900 frequencies and DCS1800 frequencies, and then click OK to return to the dialog box shown in Figure 21-2. In the dialog box shown in Figure 21-2, click TRX Config. A dialog box is displayed, as shown in Figure 21-4. Figure 21-4 Configure TRX Attributes dialog box (1)
Step 4 Set the attributes of the newly assigned TRXs 1.
Issue 02 (2008-06-30)
21-19
21 Co-BCCH Cell
2. 3.
On the Frequency Attributes tab page, double-click a target frequency in Available Frequencies to add the frequency to Assigned Frequencies. On the Device Attributes tab page, check Value of the HW_Concentric Attribute parameter, as shown in Figure 21-5.
NOTE
The Value of the HW_Concentric Attribute cannot be set. Instead, it is determined by the value of the BCCH IUO Attribute in Figure 21-2.
Figure 21-5 Configure TRX Attributes dialog box (2)
Step 5 Set ECSC 1. In the dialog box shown in Figure 21-2, click Call Control. A dialog box is displayed, as shown in Figure 21-6.
21-20
Issue 02 (2008-06-30)
21 Co-BCCH Cell
2.
Specify ECSC based on the actual situations.

NOTE
If you set ECSC to No, the MS reports classmark 3 only when the MSC queries. Before the MSC queries MS classmark 3, the MS is preferentially assigned to the channels on the GSM900 TRXs. Thus, the traffic load in the underlaid subcell may be too high.
Step 6 Set the handover parameters 1. Click Handover Data in the dialog box shown in Figure 21-2. A dialog box is displayed, as shown in Figure 21-7.
Issue 02 (2008-06-30)
21-21
21 Co-BCCH Cell
Figure 21-7 Set Handover Parameter dialog box (1)
2. 3.
Select Enhanced Concentric Allowed. Click Advanced. A dialog box is displayed, as shown in Figure 21-8.
21-22
Issue 02 (2008-06-30)
21 Co-BCCH Cell
Figure 21-8 Set Handover Parameter dialog box (2)
4.
Set UtoO Traffic HO Allowed to Yes.

NOTE
UtoO Traffic HO Allowed is available only when Enhanced Concentric Allowed is set to Yes. When Enhanced Concentric Allowed is set to Yes, the serving cell automatically becomes a neighbor cell of itself and cannot be deleted. In the handover algorithm of the enhanced concentric cell, the signal strength of the BCCH TRX is measured in the same way as the signal strength of the neighbor cell. Therefore, the error caused by estimation of the signal strength of the BCCH TRX in the handover algorithm of the common concentric cell can be eliminated.
Step 7 Set other parameters 1. 2. 3. 4. In the dialog box shown in Figure 21-8, set Pref. Subcell in HO of Intra-BSC and Incoming-to-BSC HO Optimum Layer to Underlaid Subcell. Set Assign Optimum Layer, Assign-optimum-level Threshold, and TA Threshold of Assignment Pref.. Set Concentric Circles HO Allowed, UL to OL HO Allowed, and OL to UL HO Allowed. Set TA for UO HO Allowed, RX_LEV for UO HO Allowed, and RX_QUAL for UO HO Allowed.
----End
21.6.5 Deactivating the Co-BCCH Cell

This describes how to deactivate the Co-BCCH cell on the BSC6000 Local Maintenance Terminal.
Prerequisite
To deactivate a non Co-BCCH cell, you need to delete the cell and then add a cell according to the actual command.
Issue 02 (2008-06-30)
21-23
21 Co-BCCH Cell
Procedure
Step 1 Delete the existing cell. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target cell and then choose Delete Cell from the shortcut menu. The Delete Cell dialog box is displayed. In the Delete Cell dialog box, double-click the target cell in the Cell view area to add the cell to the Cells to be deleted area. Click Finish. The deletion is complete.
2. 3.
Step 2 Add a new cell and complete the cell configuration. ----End

This lists the performance counters related to the Co-BCCH cell.
Alarms
None
Counters
Table 21-5 lists the performance counters related to the Co-BCCH cell. Table 21-5 Counters related to the Co-BCCH cell Counter AS330A Description Mean Uplink Receive Level during Concentric Cell Handover Initiation (Overlay to Underlay) Mean Downlink Receive Level during Concentric Cell Handover Initiation (Overlay to Underlay) Mean Uplink Receive Level during Concentric Cell Handover Initiation (Underlay to Overlay) Mean Downlink Receive Level during Concentric Cell Handover Initiation (Underlay to Overlay) Mean Timing Advance during Concentric Cell Handover Initiation (Overlay to Underlay) Mean Timing Advance during Concentric Cell Handover Initiation (Underlay to Overlay)
AS332A
AS330B
AS332B
AS334A
AS334B
21-24
21 Co-BCCH Cell
Counter H3001 H3002 H3012 H3011 H3022A
Description Internal Intra-Cell Handover Requests (Overlay to Underlay) Internal Intra-Cell Handover Requests (Underlay to Overlay) Internal Intra-Cell Handover Commands (Underlay to Overlay) Internal Intra-Cell Handover Commands (Overlay to Underlay) Failed Internal Intra-Cell Handovers (Channel Unavailable) (Underlay to Overlay) Failed Internal Intra-Cell Handovers (Channel Unavailable) (Overlay to Underlay) Failed Internal Intra-Cell Handovers (Other Causes) (Underlay to Overlay) Failed Internal Intra-Cell Handovers (Other Causes) (Overlay to Underlay) Success Rate of Internal Intra-Cell Handover (Underlaid Subcell to Overlaid Subcell) Success Rate of Internal Intra-Cell Handover (Overlay to Underlay) MRs on Signaling Channels (Underlaid Subcell) MRs on Signaling Channels (Overlaid Subcell) MRs on TCHs (Underlaid Subcell) MRs on TCHs (Overlaid Subcell) Traffic Volume of TCHs (Underlaid Subcell) Traffic Volume of TCHs (Overlaid Subcell) Channel Assignment Requests (Underlaid Subcell Only) Channel Assignment Requests (Overlaid Subcell Only)
H3021A
H3022M H3021M TH3032
TH3031 S3012 S3011 S3002 S3001 CR3557 CR3558 R3200 R3201
Issue 02 (2008-06-30)
21-25
21 Co-BCCH Cell
Counter R3202 R3203 R3202B R3203B R3202D
Description Channel Assignment Requests (Underlaid Subcell Preferred) Channel Assignment Requests (Overlaid Subcell Preferred) TCH Assignment Requests (Underlaid Subcell Preferred) TCH Assignment Requests (Overlaid Subcell Preferred) Channel Assignment Requests in Incoming Internal Inter-Cell Handover Procedure (TCH)(Underlaid Subcell Preferred) Channel Assignment Requests in Incoming Internal Inter-Cell Handover Procedure (TCH) (Overlaid Subcell Preferred) Channel Assignment Requests in Incoming External Inter-Cell Handover Procedure (TCH) (Underlaid Subcell Preferred) Channel Assignment Requests in Incoming External Inter-Cell Handover Procedure (TCH) (Overlaid Subcell Preferred) Channel Assignment Overflows (TCH) (Underlaid Subcell Preferred) Channel Assignment Overflows (TCH) (Overlaid Subcell Preferred) Channel Assignment Overflows in Incoming Internal Inter-Cell Handover Procedure (TCH) (Underlaid Subcell Preferred) Channel Assignment Overflows in Incoming Internal Inter-Cell Handover Procedure (TCH) (Overlaid Subcell Preferred) Channel Assignment Overflows in Incoming External Inter-Cell Handover Procedure (TCH) (Underlaid Subcell Preferred)
R3203D
R3202E
R3203E
R3222B R3223B R3222D
R3223D
R3222E
21-26
Issue 02 (2008-06-30)
21 Co-BCCH Cell
Counter R3223E
Description Channel Assignment Overflows in Incoming External Inter-Cell Handover Procedure (TCH) (Overlaid Subcell Preferred) Channel Assignment Overflows in Underlaid Subcell (TCH) Channel Assignment Overflows in Overlaid Subcell (TCH) Channel Assignment Overflows in Underlaid Subcell (SDCCH) Channel Assignment Overflows in Overlaid Subcell (SDCCH) Channel Assignment Overflows in Underlaid Subcell (TCHF) Channel Assignment Overflows in Overlaid Subcell (TCHF) Channel Assignment Overflows in Underlaid Subcell (TCHH) Channel Assignment Overflows in Overlaid Subcell (TCHH) Failed Handovers from Underlaid Subcell to Overlaid Subcell due to Busy Channels in Overlaid Subcell Failed Handovers from Overlaid Subcell to Underlaid Subcell due to Busy Channels in Underlaid Subcell
R3225J R3224J R3225G R3224G R3225H R3224H R3225I R3224I R3224K
R3225K
21.8 References
l
GSM 08.08: "Mobile Switching Centre - Base Station system (MSC-BSS) Interface Layer 3 Specification"
GSM 04.08 "Mobile Radio Interface - Layer 3 Specification"
Issue 02 (2008-06-30)
21-27
22 Satellite Transmission
22
About This Chapter
Satellite Transmission
22.1 Overview This describes the application of satellite transmission, which is mainly adopted in remote mountainous areas or sparsely populated plains. 22.2 Availability This lists the NEs and software required for the implementation of satellite transmission. 22.3 Impact The describes the impact of satellite transmission on system performance and other features. 22.4 Technical Description This describes the network topologies of satellite transmission and the application of satellite transmission over the Abis interface. Huawei BSS supports the satellite transmission over the Ater, A, Abis, Pb interface, and Gb interfaces. 22.5 Implementation This describes how to configure satellite transmission on the Ater, A, Abis, and Pb interfaces. 22.6 Maintenance Information None. 22.7 References None.
Issue 02 (2008-06-30)
22-1
22.1 Overview
This describes the application of satellite transmission, which is mainly adopted in remote mountainous areas or sparsely populated plains.
Definition
Satellite transmission enables different entities to communicate with each other by using the satellites orbiting the earth. Compared with traditional terrestrial transmission, satellite transmission encounters the problems such as delay, jitter, and bit error. Huawei BSS eliminates the delay, jitter, and bit error problems over satellite transmission through the optimization of signaling procedures and the adjustment of relevant timers. Huawei BSS supports the satellite transmission over the A, Ater, Abis, Pb, and Gb interfaces.
Purposes
The satellite transmission features wide coverage, long transmission distance, and flexible link scheduling. This enables satellite transmission to be used beyond geographical difference and transmission distance. Satellite transmission is widely used in remote mountainous areas or sparsely populated plains.
Terms
None

Acronyms and Abbreviations BC DCE DTE VSAT Full Spelling Bear Channel Data Circuit-Terminating Equipment Data Terminal Equipment Very Satellite Communications Terminal
22.2 Availability
This lists the NEs and software required for the implementation of satellite transmission.
NEs Involved
Table 22-1 describes the NEs involved in satellite transmission.
Table 22-1 NEs involved in satellite transmission MS NOTE

BTS
BSC
MSC
MGW -
SGSN
GGSN -
HLR -
Software Releases
Table 22-2 describes the versions of GBSS products that support satellite transmission. Table 22-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012A E BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM BTS30 BTS312 BTS3012A BTS3001C BTS3002C DTRU QTRU Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases All releases All releases All releases All releases All releases
Miscellaneous
None
Issue 02 (2008-06-30)
22-3
22.3 Impact
The describes the impact of satellite transmission on system performance and other features.

The delay involved in satellite transmission may affect the counters such as call drop rate, handover success rate, and assignment success rate.

Call drops occur when the forward link and reverse link in the Huawei BTS ring topology are switched over.

This describes the network topologies of satellite transmission and the application of satellite transmission over the Abis interface. Huawei BSS supports the satellite transmission over the Ater, A, Abis, Pb interface, and Gb interfaces. 22.4.1 Network Topologies of Satellite Transmission This topic describes the networking of the satellite transmission over the Abis interface. 22.4.2 Satellite Transmission on the Abis Interface This describes the satellite transmission over the Abis interface. Satellite transmission has a higher transmission delay than the terrestrial transmission. Huawei BSS is developed with multiple optimization mechanisms to avoid abnormal procedures caused by prolonged delay. 22.4.3 Satellite Transmission on the Pb Interface The link layer on the Pb interface adopts LAPD link protocols. The processing on the LAPD link is the same as that on the Abis interface.
22.4.1 Network Topologies of Satellite Transmission

This topic describes the networking of the satellite transmission over the Abis interface. Star topology is generally adopted when the satellite transmission is implemented over the Abis interface. Figure 22-1 shows a typical networking of satellite transmission.
NOTE
The principle of satellite transmission over Abis, Ater, Pb, and Gb interfaces is the same as that over the Abis interface.
22-4
Issue 02 (2008-06-30)
Figure 22-1 Typical networking of satellite transmission
Satellite ground station MSC
E1 Ground receiving station
BTS
BSC
BTS
E1 Ground receiving station
BTS
SDH/PDH or microwave/ optical cables
BTS
The satellite communication is composed of the communication satellites and ground stations. The communications satellite is usually a geosynchronous satellite, which orbits the equator. The satellite orbits at a distance of 35786 km from the earth and has an angular orbital velocity equal to the earth orbital velocity. 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 is transferred to the Earth stations for communication, through the terrestrial network. Using the VSAT-based system to build up a private network causes lower cost, smaller aperture, and flexible deployment.
22.4.2 Satellite Transmission on the Abis Interface

This describes the satellite transmission over the Abis interface. Satellite transmission has a higher transmission delay than the terrestrial transmission. Huawei BSS is developed with multiple optimization mechanisms to avoid abnormal procedures caused by prolonged delay.
Immediate Assignment Opt.

The immediate assignment procedure involves the following steps: 1. 2. 3.
Issue 02 (2008-06-30)
The BSC sends a Channel Activation message to the BTS. The BTS responds with a Channel Activation Acknowledgement message. The BSC sends an Immediate Assignment Command message to the MS.
NOTE
In the terrestrial transmission, the interval between the Channel Activation message and the Channel Activation Acknowledgement is short. In the satellite transmission, however, the MS takes a longer time to receive the Immediate Assignment Command message from the BSS. The optimized immediate assignment procedure is adopted in the satellite transmission to avoid prolonged call proceeding and immediate assignment failure due to transmission delay.
After sending a Channel Activation message to the BTS, the BSC proceeds to send an Immediate Assignment Command message to the MS without waiting for the Channel Activation Acknowledgement message from the BTS.
Impact of System Information

To avoid the transmission delay and improve the access success rate of the MS in satellite transmission, performs the following settings:
l
Add the times for the MS to send the Channel Request message. The default value of MS MAX Retrans is 4, and you can set the value of it according to actual commands. Increase the interval between two transmissions by setting Tx-integer to 50.
Processing of LAPD Protocols

Prolong the length of timers and increase the value of the sliding window while processing LAPD protocols to overcome the impact of transmission delay.
Operating Mode of the BTS Clock

The BTS clock is subject to the BSC clock. If the satellite equipment fails to keep clock synchronization, you can select the internal clock as the clock reference. The internal clock extracted from the BSS also meets the requirements specified in GSM protocols.
Voice Quality
The voice quality is not affected when the bit error rate is less than 110-6. Generally, the bit error rate in satellite transmission is less than 110-8.
22.4.3 Satellite Transmission on the Pb Interface

The link layer on the Pb interface adopts LAPD link protocols. The processing on the LAPD link is the same as that on the Abis interface.
22.4.4 Satellite Transmission on the Gb Interface

This describes the satellite transmission on the Gb interface. Because E1 transmission on the Gb interface is unavailable in some countries and regions, the BSC supports satellite as a relay for transmission on the Gb interface. FR is used on the Gb interface as bearer protocol. The FR link on the Gb interface of the Huawei BSS can support 600 ms delay carried with satellite transmission. When you configure satellite transmission on the Gb interface, ensure that the following parameters involved in the FR link on the Gb interface meet the requirement of delay:
l
N391
22-6

l l l
N392 N393 T391
The value of T391 must be greater than three times of satellite transmission delay. The mode of Bear Channel (BC) is determined by networking:
l
If the PCU is directly connected to the SGSN, set the PCU to Data Terminal Equipment (DTE) and the SGSN to Data Circuit-Terminating Equipment (DCE). If the PCU is connected to the SGSN through an intermediate network, set the PCU to DTE, intermediate network to DCE, and SGSN to either DTE or DCE.
When IP transmission mode is used on the Gb interface, the default settings can support the 600 ms delay carried with satellite transmission.
NOTE
The timers are set to default values.
22.5 Implementation
This describes how to configure satellite transmission on the Ater, A, Abis, and Pb interfaces. 22.5.1 Configuring Satellite Transmission on the Ater Interface This describes how to configure satellite transmission on the Ater interface on the BSC6000 Local Maintenance Terminal. 22.5.2 Configuring Satellite Transmission on the A Interface This describes how to configure satellite transmission on the A interface on the BSC6000 Local Maintenance Terminal. 22.5.3 Configuring Satellite Transmission on the Abis Interface This describes how to configure satellite transmission on the Abis interface on the BSC6000 Local Maintenance Terminal. 22.5.4 Configuring Satellite Transmission on the Pb Interface This describes how to configure satellite transmission on the Pb interface on the BSC6000 Local Maintenance Terminal or PCU LocalWS.
22.5.1 Configuring Satellite Transmission on the Ater Interface

This describes how to configure satellite transmission on the Ater interface on the BSC6000 Local Maintenance Terminal.
Prerequisite
The Ater connection path is configured for the GEIUT/GOIUT in the GMPS.
Context
When the GTCS is remotely configured, the signaling transmission, service transmission, and GTCS OM are required. Therefore, you are advised not to configure satellite transmission on the Ater interface when the GTCS is remotely configured. To enable the normal processing of PS services in the satellite transmission mode, the PS cell GPRS parameters T3168 must be set to 2000ms, T3192 to 0ms, BS_CV_MAX to 15.
Procedure
Step 1 On the BSC Device Panel tab page of the BSC6000 Local Maintenance Terminal, right-click a GEIUT/GOIUT, and then choose Configure Ater Connection Path. A dialog box is displayed. Step 2 Click Add. A dialog box is displayed, as shown in Figure 22-2. Figure 22-2 Add Ater Connection Path dialog box
Step 3 Set the parameters related to the Ater connection path, and click OK. The addition of an Ater connection path is complete. Step 4 On the BSC Device Panel tab page of the BSC6000 Local Maintenance Terminal, right-click a GEIUT/GOIUT, and then choose Add Ater Signaling Link. A dialog box is displayed. Step 5 Click Add. A dialog box is displayed, as shown in Figure 22-3.
22-8
Issue 02 (2008-06-30)
Figure 22-3 Add Ater Signaling Link dialog box
Step 6 Set Transmission Mode to Satellite Transmission. Step 7 Set corresponding Timeslot No. as shown in Figure 22-4. Only one timeslot No. can be configured. Figure 22-4 Configuring timeslot
Issue 02 (2008-06-30)
22-9
Step 8 Click OK. The upper-level dialog box is displayed. Step 9 Click Finish to complete the configuration of satellite transmission on the Ater interface. ----End
22.5.2 Configuring Satellite Transmission on the A Interface

This describes how to configure satellite transmission on the A interface on the BSC6000 Local Maintenance Terminal.
Prerequisite
The E1 is configured for the GEIUA/GOIUA in the GTCS.
Context
To enable the normal processing of PS services in the satellite transmission mode, the PS cell GPRS parameters T3168 must be set to 2000ms, T3192 to 0ms, BS_CV_MAX to 15.
Procedure
Step 1 On the BSC Device Panel tab page of the BSC6000 Local Maintenance Terminal, right-click a GEIUA/GOIUA, and then choose Configure A Interface E1/T1. A dialog box is displayed. Step 2 Click Add. A dialog box is displayed, as shown in Figure 22-5. Figure 22-5 Adding A interface E1/T1
Step 3 Set relevant parameters on the A Interface E1/T1 Attributes tab page, and then click OK. The addition of an E1 to the A interface is complete.
Step 4 On the BSC Device Panel tab page of the BSC6000 Local Maintenance Terminal, right-click a GEIUA/GOIUA in the GTCS, and then choose Configure SS7 Signaling Link. A dialog box is displayed. Step 5 Click Add. A dialog box is displayed, as shown in Figure 22-6. Figure 22-6 Adding an SS7 signaling link
Step 6 Select the MTP2 tab, and then set parameters, as shown in Figure 22-7.
CAUTION
The signaling link with the Rate Type of 64 kbit/s can be configured with only one E1 timeslot.
Issue 02 (2008-06-30)
22-11
Figure 22-7 Configuring timeslot
Step 7 Select the MTP3 tab, set SLC, SLC Send, and Satellite Flag, as shown in Figure 22-8.
22-12
Issue 02 (2008-06-30)
Figure 22-8 Configuring MTP3 parameters
NOTE
l l
Meanings of the Satellite Flag values: Yes indicates that satellite transmission is supported, and No indicates that the terrestrial transmission is supported. The settings of SLC and SLC send must be the same between the BSC and the MSC.
Step 8 Click OK. The upper-level dialog box is displayed. Step 9 Click Finish to complete the configuration of satellite transmission on the A interface. ----End
22.5.3 Configuring Satellite Transmission on the Abis Interface

This describes how to configure satellite transmission on the Abis interface on the BSC6000 Local Maintenance Terminal.
Prerequisite
Apply for a license and activate the license. 1. To apply for the license for the satellite transmission on Abis interface, in the BSC6000V900R008 Exceptional Commercial License Application Template, you should fill in the number of the sites that support satellite transmission in the Number of sites supporting satellite transmission column in the License control items column.
Issue 02 (2008-06-30)
2.
Activate the license on the Local Maintenance Terminal. For details, see Activating the BSC License.
After the licenses are activated, the BSC can support satellite transmission over the Abis interface based on the number of applied licenses. By default, the satellite transmission over Abis interface is closed. You can perform certain data configuration on the BSC6000 Local Maintenance Terminal to open the satellite transmission on Abis interface.
NOTE
The license strategy applies only to the Abis interface. The other interfaces can support satellite transmission once they are correctly configured.
Context
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click a BTS that needs to be configured with satellite transmission data, and then choose Site Operation > Configure Site Attributes on the shortcut menu. Step 2 Click Set Site Attributes. A dialog box is displayed, as shown in Figure 22-9. Figure 22-9 Configuring site attributes (1)
22-14
Issue 02 (2008-06-30)
Step 3 Select the Basic Information tab, and then set Transmission Mode to Satellite Transmission and Clock Type to Internal Clock. Step 4 Click OK. The upper-level dialog box is displayed. Step 5 Click Finish to complete the basic configuration of satellite transmission on the Abis interface.
NOTE
The transmission modes on the Abis interface are as follows:

l l
In terrestrial transmission, the information transferred between the BTS and the BSC is carried by the land bearing network. In satellite transmission, the information transferred between the BTS and the BSC is carried by the satellite communications equipment.
Step 6 Improve cell performance 1. Set RSL Lapd Link Window Size a. On the BSC6000 Local Maintenance Terminal, right-click a BTS on the Management Tree tab page. Then, choose BTS Operation > Configure BTS Attributes from the shortcut menu. The Configure Site Attributes dialog box is displayed. In the displayed dialog box, select Configure Cell Attributes. A dialog box is displayed, as shown in Figure 22-10.
b.
Figure 22-10 Site Attributes
Issue 02 (2008-06-30)
22-15
c.
Select the OML Setting tab, and then set RSL Lapd Link Window Size to 48.
NOTE
This parameter is bound to the parameterTransmission Mode. That is, the value of this parameter automatically matches that of the transmission mode.
2.
Set SDCCH Dynamic Allocation Allowed a. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell, and then choose Configure Cell Attributes from the shortcut menu. A dialog box is displayed. Select cells, and then click Next. In the displayed dialog box, click Configure Cell Attributes. A dialog box is displayed, as shown in Figure 22-11.
b.
c. 3.
22-16
Select SDCCH Dynamic Allocation Allowed.
Set MS MAX Retrans.

a. 4.
The default value of the MS MAX Retrans is 4. You can change the value according to actual commands. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell, and then choose Configure Cell Attributes from the shortcut menu. A dialog box is displayed. Select cells, and then click Next. In the displayed dialog box, click Configure Cell Attributes. A dialog box is displayed, as shown in Figure 22-11. In the Advanced Attributes area, click Idle Mode. A dialog box is displayed, as shown in Figure 22-12.
Set Tx-integer(RACH Timeslot(equals to a TDMA frame,4.615ms)). a.
b. c.
Figure 22-12 Set Idle Parameter dialog box (1)
d. 5. a.
Set Tx-integer(RACH Timeslot(equals to a TDMA frame,4.615ms)) to 50. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell, and then choose Configure Cell Attributes from the shortcut menu. A dialog box is displayed. Select cells, and then click Next. In the displayed dialog box, click Configure Cell Attributes. A dialog box is displayed, as shown in Figure 22-11. In the Advanced Attributes area, select Call Control. Click Advanced. A dialog box is displayed, as shown in Figure 22-13.
Set the timer.
b. c. d.
Issue 02 (2008-06-30)
22-17
Figure 22-13 Configuring Call Control Parameters
e.
Set T200 SDCCH(5ms) to 200, T200 SACCH SDCCH(10ms) to 100, and T200 SDCCH SAPI3(5ms) to 200.
NOTE
Huawei recommends that the value of T200 SDCCH(5ms) is equal to or greater than 840 ms (168 ms expressed in 5 ms on the BSC6000 Local Maintenance Terminal) when satellite transmission is enabled. The satellite transmission delay is 270 ms on average with different intermediate transmission.
----End
22.5.4 Configuring Satellite Transmission on the Pb Interface

This describes how to configure satellite transmission on the Pb interface on the BSC6000 Local Maintenance Terminal or PCU LocalWS.
Context
Procedure
l Configure satellite transmission on the Pb interface on the BSC6000 Local Maintenance Terminal. 1. On the BSC Device Panel tab page of the BSC6000 Local Maintenance Terminal, right-click GEIUP/GOIUP in the GEPS, and then choose Configure Pb Interface E1/T1. A dialog box is displayed. Click Add. A dialog box is displayed, as shown in Figure 22-14.
2.
22-18
Issue 02 (2008-06-30)
Figure 22-14 Adding Pb interface E1/T1
3.
Select the Pb Interface E1/T1 Attributes tab, and then set the Transmission Mode to Satellite Transmission.
NOTE
The Start PCIC must be the multiple of 128. The configuration of the parameters on the CIC Attributes tab page is not necessary.
4. 5.
Click OK. The upper-level dialog box is displayed. Click Finish to complete the configuration of satellite transmission over the Pb interface.
NOTE
Pb signaling links can be carried by terrestrial transmission or satellite transmission scheme. The satellite transmission scheme can be adopted in deserts or lakes where the terrestrial transmission is unavailable. After the Pb E1 ports are configured with satellite transmission scheme, the Pb signaling links can automatically switch to satellite transmission mode based on the transmission mode adopted on the E1 ports.
Configure satellite transmission on the Pb interface on the PCU LocalWS. 1. 2. 3. Run the mt gcell deactive<LCNo> command to deactivate a cell. Run the pcu add sattrans<LCNo>yes command to configure satellite transmission for the cell. Run the mt gcell active <LCNo> command to activate the cell.
----End
22.5.5 Configuring Satellite Transmission on the Gb Interface

This describes how to configure satellite transmission on the Gb interface on the BSC6000 Local Maintenance Terminal.
Context
Parameter T391 is involved in satellite transmission on the Gb interface. The default value of the parameter is 10 S, which can support the delay caused by satellite transmission. N391, N392, and N393 are set to default values. To enable the normal processing of PS services in the satellite transmission mode, the PS cell GPRS parameters T3168 must be set to 2000ms, T3192 to 0ms, BS_CV_MAX to 15.
Procedure
Step 1 On the BSC Device Panel tab page of the BSC6000 Local Maintenance Terminal, right-click GFGUG/GFPUG, and then choose Configure BC. Step 2 Modify DTE parameters on the displayed dialog box. ----End

None.
Alarms
None.
Counter
None.
22.7 References
None.
22-20
Issue 02 (2008-06-30)
23 TRX Cooperation
23
About This Chapter
TRX Cooperation
23.1 Overview This describes the BCCH TRX cooperation. When a BCCH TRX of a cell is unavailable, the BSC specifies another available TRX in the cell to replace the original BCCH TRX. This describes the TRX cooperation. When faults occur on the TRXs in a cell, the TRX cooperation ensures that the cell is functional. 23.2 Availability This lists the NEs and software required for the implementation of TRX cooperation. 23.3 Impact This describes the impact of TRX cooperation on system performance and on other features. 23.4 Technical Description This describes the principles of the BCCH TRX cooperation, baseband FH TRX cooperation, and the TRX cooperation algorithm. 23.5 Implementation This describes how to configure the TRX cooperation. 23.6 Maintenance Information This lists the alarms and performance counters related to TRX cooperation. 23.7 References None.
Issue 02 (2008-06-30)
23-1
23 TRX Cooperation
23.1 Overview
This describes the BCCH TRX cooperation. When a BCCH TRX of a cell is unavailable, the BSC specifies another available TRX in the cell to replace the original BCCH TRX. This describes the TRX cooperation. When faults occur on the TRXs in a cell, the TRX cooperation ensures that the cell is functional.
Definition
When some TRXs in a cell fail, the cell may be not functional. When faults occur on the TRXs in a cell, the TRX cooperation ensures that the cell is functional. The TRX cooperation is categorized into the following modes:
l
BCCH TRX Cooperation When a BCCH TRX fails, the BSC selects a normal TRX as the new BCCH TRX according to the TRX cooperation algorithm to ensure that the cell is functional. When the fault of the original BCCH TRX is rectified, the BSC can switch the BCCH back to the original TRX.
Description of the Baseband FH TRX Cooperation When a TRX of the cell in Baseband FH mode is faulty, the BSC changes the mode to be None FH to avoid decrease in the voice quality.
Purposes
When a BCCH TRX of a cell fails, all the services in this cell are interrupted. To ensure the normal running of the cell services, the BSC initiates another TRX in the cell to replace the faulty TRX. When the TRX of a cell in baseband FH mode fails, some speech frames in the call using the FH channel are lost. Thus, the voice quality is decreased. To ensure the voice quality in the cell, the BSC enables the baseband FH TRX cooperation and changes the mode to none FH. Then, faults of few TRXs do not affect the voice quality in the entire cell. After the faults are rectified, the BSC can revert the FH mode of the cell to baseband FH.
NOTE
During the period in which the service is interrupted due to TRX failure and then the service is resumed after TRX cooperation, the system determines whether the TRX cooperation is required, performs cell service handover, and cell re-initialization. The TRX cooperation is not triggered within a certain period after the cell is initialized. The period is determined by the Aiding Delay Protect Time(min). By default, the value is 15 minutes.
Terms
Terms Original main BCCH TRX Definition Indicates the main BCCH TRX configured on the BSC6000 Local Maintenance Terminal by the user in the cell.
23-2
Issue 02 (2008-06-30)
23 TRX Cooperation
Terms Cooperated TRX
Definition In TRX cooperation, the cooperated TRX is an available TRX selected through the TRX cooperation algorithm to replace the original main BCCH TRX. The selected TRX is the new BCCH TRX of the cell. Indicates the working BCCH TRX after TRX cooperation. Indicates the task that is performed each second in the system.
Current main BCCH TRX Task per second
Acronym and Abbreviation

Acronym and Abbreviation BCCH TCH SDCCH PDCH CBCH Full Spelling Broadcast Control CHannel Traffic Channel Stand-alone Dedicated Control Channel Packet Data Channel Cell Broadcast CHannel
23.2 Availability
This lists the NEs and software required for the implementation of TRX cooperation.
NEs Involved
Table 23-1 lists the network elements involved in TRX cooperation. Table 23-1 NEs involved in TRX cooperation MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 23-2 describes the versions supported by the GBSS NEs involved in TRX cooperation.
23 TRX Cooperation
Table 23-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012A E BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM BTS30 BTS312 BTS3012A BTS3001C BTS3002C DTRU QTRU Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases All releases All releases All releases All releases All releases
23.3 Impact
This describes the impact of TRX cooperation on system performance and on other features.

The impacts of the BCCH TRX cooperation on system performance are as follows:
l
After the BCCH TRX cooperation, the BSC specifies a normal non-BCCH TRX as the BCCH TRX; therefore, the number of available TCHs decreases and the cell capacity is reduced. The greater the number of faulty TRXs , the lower the cell capacity. If a PDCH TRX is involved in the BCCH TRX cooperation, the PDCH is unavailable and the packet service capacity is deceased after the BCCH TRX cooperation; if a CBCH TRX is involved in the BCCH TRX cooperation, the CBCH is unavailable and the cell broadcast service is terminated after the BCCH TRX cooperation. If either of the original main BCCH TRX or the cooperated TRX does not support the EDGE, neither of them supports the EDGE after the BCCH TRX cooperation. If the cell is a concentric cell and the cooperated TRX is in an overlaid subcell, the coverage of the cell decreases after the TRX cooperation.
The impacts of the baseband FH TRX cooperation on system performance are as follows:

l
23 TRX Cooperation
In the baseband FH TRX cooperation, the BSC changes the FH mode from Baseband FH to None FH. The cell cannot implement the functions of interference diversity and antiattenuation. When the baseband FH mode of the cell is Baseband FH Joined By The TRX Carrying the Primary BCCH and when the BCCH TRX of the cell fails, both the BCCH TRX cooperation and the baseband FH TRX cooperation are performed. That is, the BSC changes the FH mode of the cell to None FH. After all faults on the original primary BCCH TRX and the TRX involved in the FH are rectified, the BSC reverts to FH mode to Baseband FH.

The impacts of the TRX cooperation on other features are as follows:
l
The TRX cooperation is not performed during the validity period of the configured and modified data, resource check, and BTS initialization. If the SDCCH dynamic adjustment, full-rate/half-rate dynamic adjustment, or PDCH dynamic adjustment occurs in the cell, the types of the dynamically adjusted channels carried by the TRXs involved in the TRX cooperation are reverted to be the initial types after the TRX cooperation or TRX cooperation switchback.

This describes the principles of the BCCH TRX cooperation, baseband FH TRX cooperation, and the TRX cooperation algorithm. 23.4.1 BCCH TRX Cooperation This describes the BCCH TRX cooperation. When a BCCH TRX of a cell is unavailable, the BSC specifies another available TRX in the cell to replace the original BCCH TRX, thus ensuring that the cell is functional. When the fault of the original BCCH TRX is rectified, the BSC can switch the BCCH back to the original TRX. 23.4.2 Description of the Baseband FH TRX Cooperation This describes the baseband FH TRX cooperation. In a cell with the FH mode as Baseband FH, when a TRX involved in the FH fails, the BSC initiates the baseband FH TRX cooperation and changes the FH mode of the cell to None FH. After the TRX faults are rectified, the BSC reverts the FH mode to Baseband FH. 23.4.3 TRX Cooperation Algorithm This describes the algorithm adopted by the BSC to select the cooperated TRX in the TRX cooperation.
23.4.1 BCCH TRX Cooperation

This describes the BCCH TRX cooperation. When a BCCH TRX of a cell is unavailable, the BSC specifies another available TRX in the cell to replace the original BCCH TRX, thus ensuring that the cell is functional. When the fault of the original BCCH TRX is rectified, the BSC can switch the BCCH back to the original TRX. The BCCH TRX cooperation involves the following:
l
BCCH TRX Cooperation

Issue 02 (2008-06-30)
23 TRX Cooperation
l
Recovery of the original BCCH TRX
BCCH TRX Cooperation

The BCCH TRX cooperation is triggered by the required status change message reported from the BTS. The requirements of the BCCH TRX cooperation are as follows:
l
The object in the message must be of the channel level and must be the main BCCH.
NOTE
If the BCCH TRX cooperation occurs, the object in the message must be the main BCCH after the TRX cooperation.
l l
The status of the main BCCH is DISABLED. The availability status of the main BCCH must be one of those listed in Table 23-3. Table 23-3 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 cell number in the BCCH TRX cooperation message is used to identify the cell where the BCCH TRX cooperation is performed. The BCCH TRX cooperation of different cells can be performed concurrently. The process of the BCCH TRX cooperation is as follows: 1. When a cell meets the requirements for the BCCH TRX cooperation, the BSC starts a protection timer with the duration as one minute.
NOTE
The protection timer with the duration of one minute can avoid the TRX cooperation caused by unstable TRX status.
2.
After the protection timer times out, the BSC checks whether the cell meets the requirements for the TRX cooperation again.
l
If the cell meets the requirements, the BSC sends requests to all the calls in the cell for force handover and starts a 10-second timer. If the cell does not meet the requirements, 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 times out, the BSC selects an available TRX in the cell to replace the original BCCH TRX. The BSC initializes the cell and delivers the configuration data to the BTS. In addition, the BSC delivers the configuration data of the original BCCH TRX to the cooperated TRX and
23-6
23 TRX Cooperation
delivers the configuration data of the cooperated TRX to the original BCCH TRX. The cooperated TRX thus can provide services of the original BCCH TRX.
Recovery of the Original BCCH TRX

After the BCCH TRX cooperation, if the fault on the original BCCH TRX in the cell is rectified, recovery of the original BCCH TRX is performed. The configuration data of the two TRXs involved in the TRX cooperation is adjusted, and the initial configuration data of the cell is restored. The process of the original BCCH TRX recovery is reverse to that of the BCCH TRX cooperation. The differences between them are the triggering conditions and processing. The time to perform the original BCCH TRX recovery is controlled by TRX Aiding Function Control, which can be set to TRX Aiding Not Allowed, Allowed & Recover Immediately, or Allowed Recover When Check Res. The recovery of the original BCCH TRX is triggered by the required status change message reported from the BTS. In addition, the status of the original BCCH is DISABLED. The cell number in the BCCH TRX recovery message is used to identify the cell where the recovery of the original BCCH TRX is performed. The recovery of the original BCCH TRX of different cells can be performed concurrently. When a cell meets the requirements for the original BCCH TRX recovery, the process of the original BCCH TRX recovery is similar to that of the BCCH TRX cooperation. Finally, you need to restore the initial configuration data before the TRX cooperation according to certain mapping rules.
23.4.2 Description of the Baseband FH TRX Cooperation

This describes the baseband FH TRX cooperation. In a cell with the FH mode as Baseband FH, when a TRX involved in the FH fails, the BSC initiates the baseband FH TRX cooperation and changes the FH mode of the cell to None FH. After the TRX faults are rectified, the BSC reverts the FH mode to Baseband FH. The baseband FH TRX cooperation involves the following:
l l
Description of the Baseband FH TRX Cooperation Recovery of the original baseband FH TRX
Description of the Baseband FH TRX Cooperation

The baseband FH TRX cooperation can be performed in only the baseband FH cell, and is triggered by the required status change message reported from the BTS. The requirements for the baseband FH TRX cooperation are as follows:
l
The object in the message must be of the BT level and must be the TRX involved in the baseband FH. The TRX is in DISABLED status. The availability status of the TRX must be one of those listed in Table 23-4.
l l
Issue 02 (2008-06-30)
23-7
23 TRX Cooperation
Table 23-4 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 cell number in the baseband FH TRX cooperation message is used to identify the cell where the baseband FH TRX cooperation is performed. The baseband FH TRX cooperation of different cells can be performed concurrently. The process of the baseband FH TRX cooperation is as follows: 1. When a cell meets the requirements for the baseband FH TRX cooperation, the BSC starts a protection timer with the duration as one minute.
NOTE
The protection timer with the duration of one minute can avoid the TRX cooperation caused by unstable TRX status.
2.
After the protection timer times out, the BSC checks whether the cell meets the requirements for the TRX cooperation again.
l
If the cell meets the requirements, the BSC sends requests to all the calls in the cell for force handover and starts a 10-second timer. If the cell does not meet the requirements, 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 times out, the BSC changes the FH mode of the cell from Baseband FH to None FH. The BSC initializes the cell, delivers new configuration data to the BTS, and changes the FH mode of the cell from Baseband FH to None FH.
Recovery of the Original Baseband FH TRX

When the faults of the baseband FH TRX in the cell are rectified, the BSC reverts the FH mode of the cell to Baseband FH. The time to perform the original BCCH TRX recovery is controlled by TRX Aiding Function Control, which can be set to TRX Aiding Not Allowed, Allowed & Recover Immediately, or Allowed Recover When Check Res. The process of the original baseband FH TRX is reverse to that of the baseband FH TRX cooperation. The differences between them are the triggering conditions and processing. The recovery of the original baseband FH TRX can be performed in only the baseband FH cell, and is triggered by the required status change message reported from the BTS. The object in the message must be of the BT level and must be the TRX involved in the baseband FH. The status of the original baseband FH TRX must be ENABLED. The cell number in the baseband FH TRX recovery message is used to identify the cell where the recovery of the original baseband FH TRX is performed. The recovery of the original baseband FH TRX can be performed concurrently in different cells.
23 TRX Cooperation
23.4.3 TRX Cooperation Algorithm

This describes the algorithm adopted by the BSC to select the cooperated TRX in the TRX cooperation. TRX cooperation is performed between the following three status:
l l l
Default status Preprocessing status Post-processing status
In the TRX cooperation, the BSC takes the following protection measures to ensure the communication quality of the radio network.
l
Preprocessing protection Avoids the frequent TRX cooperation caused by the TRX intermittence. Post-processing protection Provides sufficient time for the calls in the cell where the TRX cooperation is performed.
23.4.3.1 Checking the Availability Status of Cells This describes how to check the availability status of a cell to determine whether the cell meets the requirements for the TRX cooperation. 23.4.3.2 Checking the TRX Status This describes how to check the TRX status to specify the type of TRX cooperation in a cell. 23.4.3.3 Preprocessing the TRX Cooperation This describes the processing before the TRX cooperation. The processing before the TRX cooperation involves searching for the cooperated TRX and processing after the TRX cooperation.
Checking the Availability Status of Cells

This describes how to check the availability status of a cell to determine whether the cell meets the requirements for the TRX cooperation. The cell status check is triggered by the task per second. The 512 cells are checked cyclically. In the cell status check, the BSC ignores the cell in the abnormal state and finds the cell meeting the requirements for the TRX cooperation. The cells in the abnormal state are as follows:
l
The cell is not installed. AIDING_EXPT_CELL_NOT_INSTALL The cell is not in the working state. AIDING_EXPT_IN_INITIAL_PROCESS The OML of the cell is disconnected. AIDING_EXPT_OML_ABNORMAL The dynamic adjustment is not allowed. AIDING_EXPT_DATA_ADJUST_DISABLE The TRX cooperation is not in the default state. AIDING_EXPT_NOT_AIDING_BUTT
Issue 02 (2008-06-30)
23-9
23 TRX Cooperation
l
The cell is initialized for less than 15 minutes. AIDING_EXPT_INITIAL_PROTECT
After the BSC finds the normal cell, the TRX cooperation process is started.
Checking the TRX Status

This describes how to check the TRX status to specify the type of TRX cooperation in a cell.
Conditions of the BCCH TRX Cooperation and Recovery of the Original BCCH TRX
The BCCH TRX cooperation and the recovery of the original BCCH TRX can be performed only when certain conditions are satisfied. Table 23-5 shows the conditions of the BCCH TRX cooperation and recovery of the original BCCH TRX. Table 23-5 Conditions of the BCCH TRX cooperation and recovery of the original BCCH TRX Conditions of the BCCH TRX Cooperation The TRX Aiding Function Control Switch in the cell is enabled. The status of the current BCCH is DISABLED. The availability status of the BCCH can be POWER_OFF, FAILED, NOT_INSTALLED_REAL, or DEPENDENCY. Conditions of the Recovery of the Original BCCH TRX The TRX Aiding Function Control Switch in the cell is enabled. The current BCCH TRX is not the one in the initial configuration. The status of the BCCH in the initial configuration is ENABLED.
Conditions of the Baseband FH TRX Cooperation and Recovery of the Original Baseband FH TRX
The baseband FH TRX cooperation and the recovery of the original baseband FH TRX can be performed only when certain conditions are satisfied. Table 23-6 shows the conditions of the baseband FH TRX cooperation and recovery of the original baseband FH TRX. Table 23-6 Conditions of the baseband FH TRX cooperation and recovery of the original baseband FH TRX Conditions of the Baseband FH TRX Cooperation The TRX Aiding Function Control Switch in the cell is enabled. The FH mode of the cell is Baseband FH. Conditions of the Recovery of the Original Baseband FH TRX The TRX Aiding Function Control Switch in the cell is enabled. The BSC changes the FH mode of the cell from Baseband FH to None FH.
Issue 02 (2008-06-30)
23-10
23 TRX Cooperation
Conditions of the Baseband FH TRX Cooperation The baseband FH TRX cooperation is not performed in this cell. That is, all the TRXs involved in the baseband FH are normal. The availability status of at least one TRX involved in the baseband FH is POWER_OFF, FAILED, NOT_INSTALLED_REA, or DEPENDENCY.
Conditions of the Recovery of the Original Baseband FH TRX The status of the original BCCH is DISABLED. The status of all the TRXs involved in the baseband FH is ENABLED.
NOTE
When the BCCH TRX cooperation is performed in the cell where the baseband FH occurs, the BSC initiates the baseband FH TRX cooperation forcibly and changes the FH mode of the cell from Baseband FH to None FH.
After the TRX status check is complete:

l l
If the BSC detects that the TRX cooperation is not required, the TRX cooperation is quitted. If the BSC detects that the conditions of the TRX cooperation are satisfied, the BSC starts the preprocessing timer. The duration of the timer is one minute.
When the timer for the processing before the TRX cooperation expires, the BSC starts the processing before the TRX cooperation. The BSC then checks the TRX status again to avoid frequent TRX cooperation caused by TRX intermittence. If the BCCH TRX cooperation is required, the BSC starts to search for the cooperated TRX.
Preprocessing the TRX Cooperation

This describes the processing before the TRX cooperation. The processing before the TRX cooperation involves searching for the cooperated TRX and processing after the TRX cooperation.
Searching for the Cooperated TRX

Before starting the BCCH TRX cooperation, the BSC must select a normal TRX in the cell as the candidate cooperated TRX. In the selection, configuration of the TRX should be considered. The following TRXs cannot be selected as the candidate cooperated TRX:
l l
TRX where the current BCCH is located TRX that is in a different DTMU from the original BCCH TRX (The BCCH TRX cooperation cannot be performed across cabinet groups.) TRX in the DISABLED state TRX that cannot exchange frequencies with the original BCCH TRX (The TRX, the CDU and PBU to which the TRX belongs do not support the frequencies of the original BCCH.) TRX involved in the RF FH in the cavity combiner
l l
Issue 02 (2008-06-30)
23 TRX Cooperation
l
TRX that is in a different cavity combiner from that of the original BCCH TRX, and whose frequency spacing is less than 3 after the frequency exchange.
The BSC puts all the available TRXs in the cell into the candidate TRX queue, and then ranks them according to priorities. The TRX with the highest priority is selected as the candidate cooperated BCCH TRX. The principle for accessing the priorities is as follows: Each TRX is assigned with a byte. Initially, the byte is set to OxFF. Each bit represents whether the related function is supported. When the certain condition is satisfied, the bit is set to 0. After the assessment of the priorities, the smaller the value, the higher the priority. Figure 23-1 lists the principles for assessing the priority of the candidate TRX. Figure 23-1 Principles for assessing the priority of the candidate TRX
bit7 bit6 bit5 bit4 bit3 bit2 bit1 bit0
No PDCH No CBCH Consistent transmit and receive modes Consistent mode of supporting EDGE
Reserved
Underlaid subcell TRX
Table 23-7 lists the meanings of parameters in assessing the priority of the candidate TRX. Table 23-7 Parameters in assessing the priority of the candidate TRX Bit bit0 bit1 bit2 Meaning bit0=0: The candidate TRX is not configured with the PDCH. bit1=0: The candidate TRX is not configured with the CBCH. Bit2=0: The transmit and receive mode of the candidate TRX is the same as that of the original main BCCH TRX.
NOTE The transmit and receive mode is a concept in the BTS3012. The RF transmit modes supported by the DTRU of the BTS3012 include transmit independence, Power Boost Technology (PBT), wideband combination, and transmit diversity; the receive modes supported by the DTRU of the BTS3012 include independent receive, receive diversity, and four-way receive diversity. The transmit and receive mode of other types of BTSs is OxFF.
bit3
bit3=0: If the original main BCCH TRX supports the EDGE, the candidate TRX also supports the EDGE; if the original main BCCH TRX does not support the EDGE, the candidate TRX does not support the EDGE.
23-12
Issue 02 (2008-06-30)
23 TRX Cooperation
Bit bit4
Meaning bit4=0: The candidate TRX is in the underlaid subcell. If the cell is a concentric cell, the main BCCH TRX is generally in the underlaid subcell and has a wide coverage. If the main BCCH TRX fails, the coverage of the cell decreases.
bit5 bit6 bit7
Reserved.
In the TRX cooperation, the cell needs to be initialized. The calls in the current cell must be handed over to other cells in order not to affect the voice quality. After the processing before the TRX cooperation, the BSC starts a time for processing after the TRX cooperation with the duration of 10 seconds to ensure sufficient time for the handover of all calls in the cell.
Processing After the TRX Cooperation

When the timer for the processing after the TRX cooperation times out, the BSC starts the processing after the TRX cooperation. The processing after the TRX cooperation includes the following: 1. Modifying the dynamic variables The BSC records the numbers of the cooperated TRX, the original BCCH TRX, and the current BCCH TRX. The cooperated TRX is mapped to the original BCCH TRX, and the initial configuration of the current BCCH TRX is restored. When the cell is initialized, the BSC delivers configuration information to the each TRX according to the mapping rules. 2. Sending alarms The alarms include 401 BCCH Mutual Aid in a Cell, 402 Switchback after BCCH Mutual Aid in a Cell, 409 Cell BCCH Aiding to IUO_INN TRX, 403 Baseband FH Mutual Aid in a Cell, and 404 Switchback after Baseband FH Mutual Aid in a Cell. 3. Requesting the initialization of the cell The cell needs to be initialized in both the BCCH TRX cooperation and the baseband FH TRX cooperation. In the cell initialization of the BCCH TRX cooperation, the configuration of the original BCCH TRX and that of the cooperated TRX are exchanged except the attributes of whether the AMR is supported and the RF receive mode and not exchanged.
23.5 Implementation
This describes how to configure the TRX cooperation. 23.5.1 Configuring TRX Cooperation This topic describes how to configure TRXs on the BSC6000 Local Maintenance Terminal.
23.5.1 Configuring TRX Cooperation

This topic describes how to configure TRXs on the BSC6000 Local Maintenance Terminal.
23 TRX Cooperation
Context
The TRX cooperation switch is at the cell level. That is, each cell can independently choose to enable or disable the TRX cooperation.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the cell to be configured with the TRX cooperation and choose Configure Cell Attributes from the shortcut menu. Step 2 In the displayed dialog box, double-click the cell to be configured with the TRX cooperation in the Cell view list box to add the cell to the Selected cells list box. Then, click Next. Step 3 In the Cells to be set area, select the cell to be configured with the TRX cooperation, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 23-2. Figure 23-2 Set Cell Attributes dialog box
23-14
Issue 02 (2008-06-30)
23 TRX Cooperation
Step 4 In the Advanced Attributes area, click Call Control. Step 5 In the displayed dialog box, click Advanced. A dialog box is displayed, as shown in Figure 23-3. Figure 23-3 Setting advanced call control parameters
Step 6 In Figure 23-3, select the Call Control tab, and then set the TRX Aiding Function Control to TRX Aiding Not Allowed, Allowed & Recover Immediately, or Allowed Recover When Check Res.
NOTE
The default value of TRX Aiding Function Control is Allowed Recover When Check Res; therefore, by default, the TRX cooperation of each cell is enabled.
Step 7 Click OK to return to the dialog box shown in Figure 23-2. Step 8 Click OK to save the settings of the parameters. ----End

This lists the alarms and performance counters related to TRX cooperation.
Alarms
Table 23-8 lists the alarms related to TRX cooperation. Table 23-8 Alarms related to TRX cooperation Alarm ID 401
Issue 02 (2008-06-30)
Alarm Name BCCH Mutual Aid in a Cell

23 TRX Cooperation
Alarm ID 402 403 404 409
Alarm Name Switchback after BCCH Mutual Aid in a Cell Baseband FH Mutual Aid in a Cell Switchback after Baseband FH Mutual Aid in a Cell Cell BCCH Aiding to IUO_INN TRX
Counters
Table 23-9 lists the counters related to TRX cooperation. Table 23-9 Counters related to TRX cooperation Counter R3710 R3711 R3720 R3721 Description Cell BCCH Mutual Aids Recoveries after Cell BCCH Mutual Aids Cell Baseband Hopping Mutual Aids Recoveries after Cell Baseband Hopping Mutual Aids
23.7 References
None.
23-16
Issue 02 (2008-06-30)
24 Cell Frequency Scan
24
About This Chapter
Cell Frequency Scan
24.1 Overview This describes cell frequency scan. Cell frequency scan refers to the function where a specific frequency is scanned to obtain the signal levels on the frequency. The cell frequency scan function provides references for engineers to select proper operating frequencies. 24.2 Availability This lists the NEs, software, and license required for the implementation of cell frequency scan. 24.3 Impact This describes the impact of cell frequency scan on system performance and on other features. 24.4 Technical Description This describes the technical aspects of cell frequency scan. 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 UL receive levels of a specified frequency. The scan is performed on an idle frame of a TCH in the target cell. 24.5 Capabilities This describes the capabilities of cell frequency scan. 24.6 Implementation This describes how to configure cell frequency scan. 24.7 Maintenance Information None. 24.8 References None.
Issue 02 (2008-06-30)
24-1
24.1 Overview
This describes cell frequency scan. Cell frequency scan refers to the function where a specific frequency is scanned to obtain the signal levels on the frequency. The cell frequency scan function provides references for engineers to select proper operating frequencies.
Definition
The cell frequency scan is performed to detect the UL signal levels on a specific frequency by using the specified channel in a cell. The scan provides references for engineers to select proper operating frequencies.
Purposes
The interference conditions of each frequency are important references for network optimization. Although the performance statistics of a BSC provides information on UL interference and you can analyze the interference statistics of a cell, analyzing only the UL interference statistics has the following limitations:
l l
You can obtain the interference conditions of only the configured frequencies. You cannot determine the interference sources.
The cell frequency scan can be performed to scan all the frequencies on a frequency band. In addition, you can set the parameters of specified sites, cells, and frequencies to perform specific measurements.
Terms
None.

None.
24.2 Availability
This lists the NEs, software, and license required for the implementation of cell frequency scan.
NEs Involved
Table 24-1 lists the NEs involved in cell frequency scan. Table 24-1 NEs involved in cell frequency scan MS BTS BSC MSC MGW SGSN GGSN HLR -
24-2
Issue 02 (2008-06-30)
MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 24-2 lists the versions of GBSS products that support cell frequency scan. Table 24-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
None.
24.3 Impact
This describes the impact of cell frequency scan on system performance and on other features.

None.

The impact of cell frequency scan on other features is as follows:

l l l
Cell frequency scan requires an idle frame on a TCH. Cell frequency scan cannot be performed when an RF hopping loopback test is performed. Cell frequency scan cannot be performed when an empty frame test is performed.

This describes the technical aspects of cell frequency scan. 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 UL receive levels of a specified frequency. The scan is performed on an idle frame of a TCH in the target cell. UL frequency scan is performed on an idle frame of a TCH in the target cell to scan the UL receive levels of a specified frequency. Generally, when a BSC assigns TCHs, 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 UL frequency scan of each frequency contain multiple measurement values. The results of UL frequency scan contain the current, minimum, maximum, and mean values of the main receive levels and diversity receive levels. As the UL frequency scan is performed on the Idle frame, the UL receive levels of synchronous cells cannot be obtained in practice. For accurate measurement and analysis of the interference band, refer to the counters of BTSM Management(BTSM) and Channel Measurement (CHAN) in BSC Counter Reference.
24.5 Capabilities
This describes the capabilities of cell frequency scan. The capabilities of cell frequency scan are as follows:
l l l
The frequencies on all the frequency bands for GSM can be scanned. The objects of traffic measurements for frequency scan are cells. The cell frequency scan can be performed to measure the signal levels on main and diversity antennas simultaneously. A maximum of 124 UL frequencies in a cell can be scanned simultaneously. For each cell, the frequencies of only one frequency band can be scanned at a time.
NOTE
l l
The frequency bands are GSM900, DCS1800, PCS1900, E-GSM, and R-GSM.
24.6 Implementation
This describes how to configure cell frequency scan. 24.6.1 Configuring Cell Frequency Scan This describes how to configure cell frequency scan on the BSC6000 Local Maintenance Terminal.
24.6.1 Configuring Cell Frequency Scan

This describes how to configure cell frequency scan on the BSC6000 Local Maintenance Terminal.
Procedure
l Through GUI 1. On the BSC6000 Local Maintenance Terminal, choose BTS Maintenance > Maintain Cell > Configure Frequency Scan. A dialog box is displayed, as shown in Figure 24-1. Figure 24-1 Configure Frequency Scan dialog box
2. 3. l
Set the parameters in the Location, Option, and Frequency areas. Then, click Start to enable the frequency scan. On the BSC6000 Local Maintenance Terminal, choose BTS Maintenance > Maintain Cell > Query Frequency Scan to query the result of the frequency scan.
Through MML
NOTE
In the dialog box, the parameters highlighted in red must be set.
1. 2. 3. ----End
On the Local Maintenance Terminal, enter the SET CELLSOFT command. Set the Frequency Scan Result Type. Run the command and the operation is complete.

None.
Alarms
None.
Counters
None.
24.8 References
None.
24-6
Issue 02 (2008-06-30)
25 High-Speed Signaling
25
About This Chapter
High-Speed Signaling
25.1 Overview This describes the definition and purposes of applying No.7 signaling links. The No.7 signaling links with different data rates can be applied according to the signaling load. 25.2 Availability This lists the NEs and software required for the implementation of high-speed signaling links. 25.3 Impact This describes the impact of high-speed signaling links on system performance. 25.4 Technical Description The implementation of the 2 Mbit/s signaling link in the BSC is achieved by several boards. Also, the implementation of the 2 Mbit/s signal link and its functions differ with those of the 64 kbit/s signaling link. 25.5 Capabilities This describes the capabilities of the high-speed signaling links. 25.6 Implementation This describes how to configure, verify, and disable high-speed signaling links. 25.7 Maintenance Information This lists the alarms and counters related to high-speed signaling links. 25.8 References
Issue 02 (2008-06-30)
25-1
25.1 Overview
This describes the definition and purposes of applying No.7 signaling links. The No.7 signaling links with different data rates can be applied according to the signaling load.
Definition
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 link in the SS7 network with a data rate of N x 64 kbit/s (1 N < 32). 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
A high-speed signaling link occupies multiple 64 kbit/s timeslots with a data rate of N x 64 kbit/s (1 N < 32). The electrical features of the high-speed signaling link port comply with the ITU-T G.703 protocol and its frame structure complies with the ITU-T G.704 protocol.
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.
Purposes
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
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.
Terms
Terms Signaling link Definition No.7 signaling link, used to connect the signaling points in the SS7 network and to transmit signaling information High-speed signaling link with a data rate of N x 64 kbit/s (1 N < 32) Signaling link with a data rate of 64 kbit/s
2 Mbit/s signaling link 64 kbit/s signaling link
25-2
Issue 02 (2008-06-30)

Acronyms and Abbreviations BSN FSN LI SLC Full Spelling Backward Sequence Number Forward Sequence Number Length Indicator Signaling Link Code
25.2 Availability
This lists the NEs and software required for the implementation of high-speed signaling links.
NEs Involved
Table 25-1 lists the NEs involved in high-speed signaling links. Table 25-1 NEs involved in high-speed signaling links MS NOTE
BTS -
BSC
MSC
MGW
SGSN -
GGSN -
HLR -
Software Releases
Table 25-2 lists the versions of GBSS products that support high-speed signaling links. Table 25-2 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
None.
25.3 Impact
This describes the impact of high-speed signaling links on system performance.

Compared with the 64 kbit/s signaling link, the 2 Mbit/s signaling link is configured with more timeslots; thus, the signaling transmission capacity of the 2 Mbit/s signaling link is greatly enhanced.
NOTE
l l
Generally, high-speed signaling links are used for terrestrial transmission instead of for satellite transmission. Compatibility tests must be performed when the high-speed signaling equipment from different manufacturers are used in the same network.

None.

The implementation of the 2 Mbit/s signaling link in the BSC is achieved by several boards. Also, the implementation of the 2 Mbit/s signal link and its functions differ with those of the 64 kbit/s signaling link. 25.4.1 Implementation This describes the implementation of the 2 Mbit/s signaling links, which are achieved by the GXPUM, GSCU, and GEIUA. 25.4.2 Comparison Between 2 Mbit/s Signaling Link and 64 kbit/s Signaling Link This compares the 2 Mbit/s signaling link with the 64 kbit/s signaling link in terms of implementation and functions.
25.4.1 Implementation
This describes the implementation of the 2 Mbit/s signaling links, which are achieved by the GXPUM, GSCU, and GEIUA.
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 25-1 shows the processing of the No.7 signaling in BM/TC separated mode. Figure 25-2 shows the processing of the No.7 signaling in BM/TC combined mode.
Figure 25-1 Sigaling link on the A interface (BM/TC separated)

Ater G X P U M G S C U G E I U T G E I U T G T N U G E I U A A M S C
GMPS/GEPS BSC6000
GTCS
25-4
Issue 02 (2008-06-30)
1.
In the GMPS/GEPS, the GXPUM processes the signaling based on the MTP3, SCCP, and BSSAP protocols. Then, the GSCU transmits the processed signaling to the GEIUT/GOIUT in the same subrack. The GEIUT in the GMPS/GEPS processes the received signaling based on the MTP2 protocol, and then transmits the signaling to the GEIUT in the GTCS through the Ater interface. In the GTCS, the GTNU performs timeslot-based TDM switching of the signaling, and then transmits the signaling to the GEIUA/GOIUA. The signaling is transmitted to the MSC over the A interface.
2.
3. 4.
Figure 25-2 Signaling link on the A interface (BM/TC combined)

A G X P U M G S C U G E I U A M S C
GMPS/GEPS BSC6000
1.
In the GMPS/GEPS, the GXPUM/GXPUT processes the signaling based on the MTP3, SCCP, and BSSAP protocols. Then, the GSCU transmits the processed signaling to the GEIUT/GOIUA in the same subrack. The GEIUA/GOIUA processes the signaling based on the MTP2 protocol, and then transmits the signaling to the MSC.
2.
Configuration Principles
The configuration principles are as follows:
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. The high-speed signaling link and 64 kbit/s signaling link cannot be applied in one BSC. The bandwidth of each 2 Mbit/s signaling link might vary. However, you are advised to apply the same bandwidth for the 2 Mbit/s signaling links as they share the traffic load during the operation. Each high-speed signaling link can occupy the randomly combined timeslots except timeslot 0. 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. Determine the signaling mode used between the BSC and MSC before configuring the signaling links in the BSC.
l l
Issue 02 (2008-06-30)
l
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 BSC6000 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 circuits (CIC) between the BSC and the MSCs (MSC Servers or MGWs) to the total A interface circuits (CIC).
Configuration in BM/TC separated mode:

l l
Each 2 Mbit/s signaling link can be configured only in one E1 port of the GEIUT. Multiple 2 Mbit/s signaling links can be configured in one E1 port of the GEIUT and occupy different timeslots over the E1 port. If the 2 Mbit/s signaling links in the GEIUT are removed, you need to reset the GEIUT before configuring the 64 kbit/s signaling links. If the 64 kbit/s signaling links in the GEIUT are removed, you need to reset the GEIUT before configuring the 2 Mbit/s signaling links. A maximum of eight 2 Mbit/s signaling links can be configured in one GEIUT.
If the 2 Mbit/s signaling links is 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.
25.4.2 Comparison Between 2 Mbit/s Signaling Link and 64 kbit/s Signaling Link
This 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 BSN and 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 25-3 shows the formats of the signal units in the 2 Mbit/s signaling link. The 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.
25-6
Issue 02 (2008-06-30)
Figure 25-3 Formats of the signal units in the 2 Mbit/s signaling link
F 8 CK 16 SIF 8n, n 2 SIO 8 Spare 7 LI 9 F I Res B 1 3 FSN 12 B I B 1 Res 3 BSN 12 F 8 First bit transmitted
(a) Basic format of a Message Signal Unit (MSU) F I Res B 1 3 B I B 1
F 8
CK 16
SF 8 or 16
Spare 7
LI 9
FSN 12
Res 3
BSN 12
F 8 First bit transmitted
(b) Format of a Link Status Signal Unit (LSSU) F I Res B B I B
F 8
CK
Spare
LI
FSN
Res
BSN 12
F 8 First bit transmitted T1178370-96
1 3 12 1 16 7 9 3 (c) Format of a Fill-In Signal Unit (FISU)
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 time segments with flags. The 64 kbit/s signal links adopts the preventive cyclic retransmission method.
l l
The sequence-related messages such as COO and 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. 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 code can be used to delimit a signal unit. The bit pattern for the flag code is 01111110. The zero insertion method is applied to ensure that the pattern cannot be imitated elsewhere in the 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.
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.
Error detection The error detection function is performed by means of 16 check bits provided at the end of each signal unit.
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
Issue 02 (2008-06-30)
25-7
sequence. This mechanism enables that the transmitted but not yet positively acknowledged signal units remain available for retransmission before new signal units are transmitted.
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.
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 indication of the signaling link is sent to the transmitting end, informing the transmitting end to stop transmitting the signal units already acknowledged.
If the congestion is abated, 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.
25.5 Capabilities
This describes the capabilities of the high-speed signaling links. The capabilities of the high-speed signaling links are as follows:
l l l
One 2 Mbit/s signaling link can be configured with 1 to 31 timeslots. One BSC subrack can be configured with up to eight 2 Mbit/s signaling links. One BSC subrack must be configured with only one type of signaling links such as 2 Mbit/ s signaling link or 64 kbit/s signaling link.
25.6 Implementation
This describes how to configure, verify, and disable high-speed signaling links. 25.6.1 Configuring High-Speed Signaling Links This describes how to configure a 2 Mbit/s signaling link on the BSC6000 Local Maintenance Terminal. 25.6.2 Verifying High-Speed Signaling Links This describes how to verify high-speed signaling links on the BSC6000 Local Maintenance Terminal and Local Maintenance Terminal. 25.6.3 Disabling High-Speed Signaling links This describes how to remove the 2 Mbit/s signaling links on the BSC6000 Local Maintenance Terminal and Local Maintenance Terminal.
25.6.1 Configuring High-Speed Signaling Links

This describes how to configure a 2 Mbit/s signaling link on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 Right-click a GEIUA on the BSC Device Panel of the BSC6000 Local Maintenance Terminal and choose Configure SS7 Signaling Link from the shortcut menu. A dialog box is displayed, as shown in Figure 25-4. Figure 25-4 Configuring an SS7 signaling link
Step 2 Click Add. A dialog box is displayed, as shown in Figure 25-5. On the MTP2 tab page, set Rate Type to 2Mbit/s, and select the timeslots for A Timeslot Mask and Ater Timeslot Mask.
Issue 02 (2008-06-30)
25-9
Figure 25-5 Adding an SS7 signaling link (MTP2)
NOTE
In BM/TC separated mode when the GTCS is configured remotely, you are advised to configure the SS7 signaling link on the main GTCS. Also, TS1 should not be selected in Ater Timeslot Mask.
Step 3 On the MTP3 tab page as shown in Figure 25-6, set SLC and SLC Send.
25-10
Issue 02 (2008-06-30)
Figure 25-6 Adding an SS7 signaling link (MTP3)
Step 4 Click OK to return to the dialog box shown in Figure 25-4. Step 5 Click Finish to complete the configuration of the SS7 signaling link. ----End
25.6.2 Verifying High-Speed Signaling Links

This describes how to verify high-speed signaling links on the BSC6000 Local Maintenance Terminal and Local Maintenance Terminal.
Procedure
l Through GUI 1. 2. On the BSC6000 Local Maintenance Terminal, select the BSC Attributes tab page. In the Other Data area, click A Signaling Link. A dialog box is displayed, as shown in Figure 25-7. You can view and query the status of the high-speed signaling link on the Figure 25-7.
Issue 02 (2008-06-30)
25-11
Figure 25-7 Viewing SS7 signaling links
3.
On the menu of the BSC6000 Local Maintenance Terminal, choose BSC Maintenance > Maintain Transmission and Signaling > Maintain MTP3 Link. In the displayed dialog box, click Query to query the status of the No.7 signaling links. On the Local Maintenance Terminal, enter the command LST N7LNK.
NOTE
Through MML 1.
The parameters highlighted in red must be set.
2. 3. ----End
Set parameters. Run the command and the operation is complete.
25.6.3 Disabling High-Speed Signaling links

This describes how to remove the 2 Mbit/s signaling links on the BSC6000 Local Maintenance Terminal and Local Maintenance Terminal.
Procedure
l
25-12
Through GUI
1.
Right-click a GEIUA on the BSC Device Panel of the BSC6000 Local Maintenance Terminal and choose Configure SS7 Signaling Link from the shortcut menu. A dialog box is displayed, as shown in Figure 25-8.
Figure 25-8 Removing SS7 signaling links
2. 3. l 1.
Select the SS7 signaling link to be removed in Figure 25-8, and click Delete. Click Finish to complete the removing of the SS7 signaling link. On the Local Maintenance Terminal, enter the command RMV N7LNK.
NOTE
Through MML
2. 3. ----End
Set parameters. Run the command and the operation is complete.

This lists the alarms and counters related to high-speed signaling links.
Alarms
Table 25-3 lists the alarms related to high-speed signaling links.
Issue 02 (2008-06-30)
25-13
Table 25-3 Alarms related to high-speed signaling links Alarm ID 21503 21504 21512 21511 21514 Alarm Name MTP3 Link Unavailable MTP3 Layer 2 Congestion MTP3 Link Test Failure MTP3 Link Test Success MTP2 Link Service Disrupted
Counters
Table 25-4 lists the counters related to high-speed signaling links. Table 25-4 Counters related to high-speed signaling links Counter TL6001 L6002 L6003 L6004 L6005 L6006 L6007 L6008 L6009 L6010 L6011 L6012 L6013 L6014 L6015 L6016 L6017 L6018
25-14
Description In Service Duration of MTP3 Link Out-of-Service Duration of MTP3 Link Duration of MTP3 Link Fault Duration of MTP3 Link Local Inhibition Duration of MTP3 Link Remote Inhibition Duration of MTP3 Link Remote Processor Fault Duration of MTP3 Link Congestion MTP3 Link Failures for All Reasons MTP3 Link Local Inhibitions MTP3 Link Remote Inhibitions MTP3 Link Remote Processor Failures MTP3 Link Local Switchovers MSUs Sent on MTP3 Link MSUs Received on MTP3 Link MTP3 Link Congestions Discarded MSUs during Link Congestion Transfer Inhibition Messages Received on MTP3 Link Octets in SIFs or SIOs Sent on MTP3 Link
Counter L6019 L6020 RL6021 RL6022 L6023
Description Octets in SIFs and SIOs Received on MTP3 Link This counter measures the number of user unreachable messages received by the MTP3. Ratio of Transmit Bandwidth to Total Bandwidth Ratio of Receive Bandwidth to Total Bandwidth. Bytes of MTP2 Message Head in MSU Messages on MTP3 Link
25.8 References
ITU_T Q.703, "Specifications of Signalling System No. 7 Message transfer part signaling link"
Issue 02 (2008-06-30)
25-15
26 Local Multiple Signaling Point
26
About This Chapter
Local Multiple Signaling Point
26.1 Overview This describes the multiple signaling point feature, which enables one physical BSC to serve as multiple BSCs so that each logical BSC can exchange signaling with the MSC. 26.2 Availability This lists the NEs, software, and licenses required for the implementation of local multiple signaling point. 26.3 Impact This describes the impact of local multiple signaling point on system performance and on other features. 26.4 Technical Description This describes the functions and provides background information of local multiple signaling point. 26.5 Capabilities This describes the capabilities of local multiple signaling point. 26.6 Implementation This describes how to configure local multiple signaling point. 26.7 Maintenance Information This describes the alarms and counters related to local multiple signaling point. 26.8 References None.
Issue 02 (2008-06-30)
26-1
26.1 Overview
This describes the multiple signaling point feature, which enables one physical BSC to serve as multiple BSCs so that each logical BSC can exchange signaling with the MSC.
Introduction
The feature of local multiple signaling point enables one physical BSC to serve 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 the services.
Purposes
You can configure the location area of each logical BSC by implementing the local multiple signaling 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.
Terms
Terms Signaling point Definition 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. It can communicate with other NEs. Local multiple signaling points of the BSC Local signaling point One physical BSC serves as multiple logical BSCs. Each logical BSC has an SS7 signaling point code and can exchange signaling with the MSC. The local signaling point of the BSC is assigned to the BSC and is referred to as local originating signaling point.

Acronym and Abbreviation STP SPC Full Spelling Signaling Transfer Point Signaling Point Code
26-2
Issue 02 (2008-06-30)
26.2 Availability
This lists the NEs, software, and licenses required for the implementation of local multiple signaling point.
NEs Involved
Table 26-1 lists the NEs involved in local multiple signaling point. Table 26-1 NEs involved in local multiple signaling point MS NOTE
BTS -
BSC
MSC
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 26-2 lists the GBSS products and the software versions that support local multiple signaling point. Table 26-2 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Important Point
If IP transmission mode is adopted on the A interface, the local multiple signaling point is not supported.
26.3 Impact
This describes the impact of local multiple signaling point on system performance and on other features.

The impact of local multiple signaling point on system performance is as follows:

l
The original intra-BSC handover or intra-BSC directed retry may be converted into outgoing BSC handover or outgoing BSC directed retry. Thus, the signaling load on the A interface and the call establishment time are increased. The location areas should be configured properly to reduce the load impact on the system effectively. Improper configuration of local areas my have an adverse effect on the performance of the system.

To apply for the license for local multiple signaling point, in the BSC6000V900R008 Exceptional Commercial License Application Template, you should fill in the originating signaling point and destination signaling point of the GMPS subrack in ESN Information. For details on how to obtain ESN, refer to Querying BSC ESNs.

This describes the functions and provides background information of local multiple signaling point.
Background Information
According to GSM SS7 protocols, a maximum of 16 narrowband signaling links (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 (SLC). The SLC has four bits. This indicates that the number of signaling links between a pair of signaling points cannot exceed 16. Figure 26-1 Signaling links between the BSC and the MSC
link0 BSC link15 MSC SPC0
For a large capacity BSC, 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 26-2 shows the connections of local multiple signaling points. Figure 26-2 Connections of local multiple signaling points
link0 BSC SPC1
Logical BSC1 Logical BSC2
link15 link0
MSC SPC0
BSC SPC2 link15
26.5 Capabilities
This describes the capabilities of local multiple signaling point. The capabilities of local multiple signaling point are as follows:
l
The local signaling point is configured in the unit of BM subrack. That is, one local signaling point is assigned to at least one BM subrack, and each BM subrack must belong to one local signaling point. Thus, the BSC can be configured with up to four local signaling points. Each GTCS has only one local signaling point. A common signaling point is provided to the GTCS and BM subrack to which the GTCS is connected. Thus, when multiple BM
Issue 02 (2008-06-30)
subracks are connected to one GTCS, these BM subracks should be configured with the same local signaling point.
l
If a local signaling point is assigned to only one BM subrack, the BM subrack can be configured with up to sixteen 64 kbit/s signaling links or up to eight high-speed signaling links on the A interface. If a local signaling point is assigned to multiple BM subracks, these BM subracks can be configured with up to sixteen 64 kbit/s SS7 signaling links or up to sixteen high-speed signaling links on the A interface. In addition, Each BM subrack can be configured with not more than eight high-speed signaling links. For a physical BSC, the signaling links (on the Ater interface) of all the local signaling points must be of the same type. The signaling links (on the A interface) of all the local signaling points must be of the same type. So, all the signaling links must be configured as 64 kbit/s narrowband signaling links or high-speed (Nx64 kbit/s) signaling links. All the local signaling points of a physical BSC should have the same encoding scheme: 14-bit signaling point code or 24-bit signaling point code.
26.6 Implementation
This describes how to configure local multiple signaling point. 26.6.1 Configuring Local Multiple Signaling Point This describes how to configure local multiple signaling point on the BSC6000 Local Maintenance Terminal.
26.6.1 Configuring Local Multiple Signaling Point

This describes how to configure local multiple signaling point on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 Configure an SS7 signaling point. 1. On the Management Tree tab page of theBSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Configure SS7 Signaling Point from the shortcut menu. A dialog box is displayed, as shown in Figure 26-3.
26-6
Issue 02 (2008-06-30)
Figure 26-3 Configure SS7 Signaling Point dialog box
2.
Click the OSP tab. Then, click Add OSP. A dialog box is displayed, as shown in Figure 26-4. Figure 26-4 Add OSP dialog box
3.
Set relevant parameters and then click OK.

NOTE
A maximum of four OSPs can be configured. After the configuration, click OK to return to the dialog box shown in Figure 26-3.
Issue 02 (2008-06-30)
26-7
4.
In Figure 26-3, click the DSP tab. A dialog box is displayed, as shown in Figure 26-5.
Figure 26-5 Configure SS7 Signaling Point dialog box
5.
Click Add DSP. A dialog box is displayed, as shown in Figure 26-6. Figure 26-6 Add a DSP.
26-8
Issue 02 (2008-06-30)

NOTE
If there is no direct physical link between the OSP and the DSP, then you have to configure STPs. In the dialog box, as shown in Figure 26-6, set Using STP to Yes.
6.
Set the parameters of the DSP.
Step 2 Configure the mapping between subracks and signaling points. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and choose Configure Subrack-OSP Mapping from the shortcut menu. A dialog box is displayed, as shown in Figure 26-7.
Figure 26-7 Configure Subrack-OSP Mapping dialog box
2. 3.
Set OSP for the target subrack. Click Finish to complete the configuration.
NOTE
For each BM subrack, you should configure the mapping between the BM subrack and the local signaling point. For each signaling point, you should configure SS7 signaling links. The configuration procedure is similar to configuring general SS7 signaling links.
----End

This describes the alarms and counters related to local multiple signaling point.
Alarms
None.
Counters
None.
26.8 References
None.
26-10
Issue 02 (2008-06-30)
27 Semipermanent Link
27
About This Chapter
Semipermanent Link
27.1 Overview This describes semipermanent link, which helps to improve the usage of existing transmission resources and enables telecom operators to minimize the operation cost. 27.2 Availability This lists the NEs and software required for the implementation of semipermanent link. 27.3 Technical Description This describes the connections and implementation of the semipermanent link. 27.4 Capabilities None. 27.5 Implementation This describes how to configure a semipermanent link and a monitoring timeslot. 27.6 Maintenance Information This lists the alarms and counters related to semipermanent link. 27.7 References None.
Issue 02 (2008-06-30)
27-1
27.1 Overview
This describes semipermanent link, which helps to improve the usage of existing transmission resources and enables telecom operators to minimize the operation cost.
Definition
The semipermanent link feature enables some of the idle E1 timeslots in the current network to be used to provide transmission paths for subscribers. The paths are used to transmit such information as business hall information, alarm information on the BTS AC power supply, and other maintenance information.
Purposes
When the telecom operator needs to transmit some data from one terminal to another terminal and the data does not have a high requirement for the transmission bandwidth, the idle transmission resources in the GSM network can be specially used to transfer the data.
Terms
Terms OML RSL Ater connection path Definition Operation and maintenance link (OML) is used to operate and maintain a BTS. Radio signaling link (RSL) is a link between the BSC and a TRX. The RSL is used to transmit radio signaling. Ater connection path is the transmission path between the GMPS/GEPS and the GTCS. It is used to transmit traffic data and signaling.

Acronyms and Abbreviations CIC HW Full Spelling Circuit Identity Code High Way
27.2 Availability
This lists the NEs and software required for the implementation of semipermanent link.
NEs Involved
Table 27-1 lists the NEs involved in semipermanent link.
Table 27-1 NEs involved in semipermanent link MS NOTE

BTS
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 27-2 lists the versions of GBSS products that support semipermanent link. Table 27-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012A E BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM DTRU QTRU Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
Timeslot cross connection equipment is required at both ends of the semipermanent link. The equipment extracts the timeslots that are assigned to the semipermanent link to transmit signals.

This describes the connections and implementation of the semipermanent link. 27.3.1 Connections of Semipermanent Link This describes the connections of a semipermanent link. The boards related to a semipermanent link are the transparent transmission interface board, GTNU, GEIUB, GEHUB, and BTS interface board.
27.3.2 Implementation of Semipermanent Link This describes the implementation of semipermanent link in different physical entities.
27.3.1 Connections of Semipermanent Link

This describes the connections of a semipermanent link. The boards related to a semipermanent link are the transparent transmission interface board, GTNU, GEIUB, GEHUB, and BTS interface board. Generally, when an MS makes a call, the BSS connects the CIC link on the A interface and the link on the Abis interface through the GTNU, interface board, and GDPUC. When the call is disconnected, the connections are released. The previous procedure for establishing a link is not applicable to a semipermanent link. After the data related to a semipermanent link is configured, the BSS system automatically establishes the link. Except that the link is manually deleted, the link remains available. In the traditional TDM transport mode, to establish a semipermanent link from the BTS to the A interface, the BSS system must reserve a timeslot on the E1 link that connects to the transparent transmission board, GTNU, GEIUB, and BTS interface board. The timeslot is not used to transmit traffic signals or signaling. Then, the BSS system connects the reserved timeslots one by one to form a connection path.Figure 27-1 shows a semipermanent link in the BSS system in the TDM transport mode. Figure 27-1 Semipermanent link in the BSS system (in TDM transport mode)
G E I U B
Transparent transmission interface board
G T N U
B T S 1
B T S 2
In the Abis transport optimization mode, the physical links are established by connecting a timeslot on a port of the GEHUB to a timeslot on another port, and then by using cables to connect the ports of the GEHUB and the GEIUB. Other links are connected in the same way as the TDM transport mode. Figure 27-2 shows a semipermanent link in the BSS system in the Abis transport optimization mode. Figure 27-2 Semipermanent link in the BSS system (in Abis transport optimization mode)
G E I U B G E H U B
Transparent transmission interface board
G T N U
B T S 1
B T S 2
NOTE
The transparent transmission interface board is only responsible for transparent transmission of signals. It can be configured as an output-only board, an input-only board, or a board for both input and output.
In the BSS system, semipermanent links are of two types:


l
Semipermanent link The semipermanent connection refers to the connection on both sides of the GTNU. In this connection, the BSC interface boards are used for input and output, and the GTNU exchanges signals between the interface boards. The semipermanent connection can be configured on the BSC6000 Local Maintenance Terminal or Local Maintenance Terminal.
Monitoring timeslot The monitoring timeslot refers to the semipermanent link between the BTS and the transparent transmission interface board in the BSC. You can configure the monitoring timeslot on the BSC6000 Local Maintenance Terminal or Local Maintenance Terminal.
NOTE
Based on actual requirements, the input port and output port can be configured on the same interface board. On the BSC6000 Local Maintenance Terminal or Local Maintenance Terminal, the semipermanent connection is configured on the basis of the BSC, whereas the monitoring timeslot is configured on the basis of the BTS.
The main difference between the semipermanent connection and the monitoring timeslot is the start point and end point of the two connections. As the two ends of the monitoring timeslot are the BSC and the BTS, a semipermanent link is established when the monitoring timeslot is configured.
27.3.2 Implementation of Semipermanent Link

This describes the implementation of semipermanent link in different physical entities.
Implementation of a Semipermanent Link in the Interface Board

The connection between the E1 timeslot of the BSC interface board and the highway timeslot of the GTNU depends on the net table sent by the BSC. The BSC interface board supports semipermanent links of 8 kbit/s, 16 kbit/s, 32 kbit/s, and 64 kbit/s. The 64 kbit/s semipermanent link on the Ater interface can be multiplexed with the RSL. No semipermanent link can be configured between the BM subrack and the TC subrack.
Implementation of a Semipermanent Link in the BTS

The BTS interface board can transparently transmit the timeslot signals on one port to any other port. Thus, a semipermanent link (monitoring timeslot) of the BTS can be configured. The monitoring timeslot signals are transmitted from any other port. Alternatively, the monitoring timeslot signals are transparently transmitted to the incoming E1 timeslot of a lower-level BTS. Thus, the semipermanent link of cascaded BTSs is realized.
Implementation of a Semipermanent Link in the GTNU

A connection is established between the timeslot of the semipermanent link on the BSC interface board and the input port on the GTNU. In addition, a connection is established between the timeslot of the semipermanent link on the BSC interface board and the output port on the GTNU. The GTNU establishes a connection between these connections based on relevant timeslots. Thus, a semipermanent link is established between the transparent transmission interface board and another interface board or a BTS.
After the semipermanent link is configured, timeslot cross connection equipment should be installed at both ends of the physical link. The equipment extracts required timeslots to transmit information.
27.4 Capabilities
None.
27.5 Implementation
This describes how to configure a semipermanent link and a monitoring timeslot. 27.5.1 Configuring a Semipermanent Link This describes how to configure a semipermanent link on the BSC6000 Local Maintenance Terminal . 27.5.2 Configuring a Monitoring Timeslot This describes how to configure a monitoring timeslot on the BSC6000 Local Maintenance Terminal . 27.5.3 Verifying a Semipermanent Link This describes how to verify whether a semipermanent link is successfully established.
27.5.1 Configuring a Semipermanent Link

This describes how to configure a semipermanent link on the BSC6000 Local Maintenance Terminal .
Prerequisite
Before configuring a semipermanent link, you should install timeslot cross connection equipment at both ends of the semipermanent link. The equipment extracts the timeslots assigned to the semipermanent link to transmit information. The license of NC2 is applied and activated. To apply for and activate the license, do as follows: 1. Fill in the Resource Control Items column of Number of semipermanent connection under Function control items in BSC6000V900R008 Exceptional Commercial License Application Template. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click BSC6000, and then choose Configure Semipermanent Link on the shortcut menu. A dialog box is displayed. Step 2 Click Add. A dialog box is displayed, as shown in Figure 27-3.
27-6
Issue 02 (2008-06-30)
Figure 27-3 Configuring a semipermanent link (2)
Step 3 Set Semipermanent Link Rate, In-BSC Subrack No., In-BSC Slot No., In-BSC Port No., In-BSC Timeslot No., In-BSC Sub-Timeslot Start No., Out-BSC Subrack No., Out-BSC Slot No., Out-BSC Port No., Out-BSC Timeslot No., and Out-BSC Sub-Timeslot Start No.. Then click OK. A dialog box is displayed, as shown in Figure 27-4. Figure 27-4 Configuring a semipermanent link (3)
Step 4 Click Finish. A dialog box is displayed.

Step 5 Click Yes. The configuration is complete. ----End
27.5.2 Configuring a Monitoring Timeslot

This describes how to configure a monitoring timeslot on the BSC6000 Local Maintenance Terminal .
Prerequisite
Before configuring a monitoring timeslot, you should install timeslot cross connection equipment at both ends of the semipermanent link. The equipment extracts the timeslots assigned to the semipermanent link to transmit information.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target site, and then choose Configure Site Monitor Timeslot on the shortcut menu. Step 2 On the displayed dialog box, click Set Monitor Timeslot. Step 3 On the displayed dialog box, click Add Record. A dialog box is displayed, as shown in Figure 27-5. Figure 27-5 Configuring site monitor timeslot (3)
Step 4 Set Timeslot Rate, In-BSC Subrack No., In-BSC Slot No., In-BSC Port No., In-BSC Timeslot No., In-BSC Sub-Timeslot No., Site Port No., Site Timeslot No., and Site SubTimeslot No.. Then click OK. A dialog box is displayed, as shown in Figure 27-6.
27-8
Issue 02 (2008-06-30)
Figure 27-6 Configuring site monitor timeslot (4)
Step 5 Click OK. Step 6 Click Finish. Monitoring timeslots are configured for the BTS. ----End
27.5.3 Verifying a Semipermanent Link

This describes how to verify whether a semipermanent link is successfully established.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, click the BSC Attributes tab. Step 2 On the displayed dialog box, click Timeslot of E1/T1 Int. A dialog box is displayed, as shown in Figure 27-7.
Issue 02 (2008-06-30)
27-9
Figure 27-7 View E1/T1 dialog box
Step 3 Click the target interface E1 tab. Take Ater Interface E1/T1 for example. A dialog box is displayed, as shown in Figure 27-8.
27-10
Issue 02 (2008-06-30)
Figure 27-8 Ater Interface E1/T1
Step 4 Select Subrack No., Slot No., and Port No.. In the Timeslot list on the right, the Timeslot Type of the semipermanent link is SemiCon. ----End

This lists the alarms and counters related to semipermanent link.
Alarms
None.
Counters
None.
27.7 References
None.
Issue 02 (2008-06-30)
27-11
28 Discontinuous Transmission and Discontinuous Reception
28
Discontinuous Transmission and Discontinuous Reception
About This Chapter

28.1 Overview This describes the definitions of DTX and DRX and purposes of applying DTX and DRX. DTX and DRX mechanism reduces the interference level and improves the system efficiency. Through this mechanism, the wastage of system resources can be minimized and meanwhile an acceptable signal quality is maintained. 28.2 Availability This lists the NEs and software required for the implementation of DTX and DRX. 28.3 Technical Description This describes the technical aspects of DTX and DRX. The DTX and DRX improve the system efficiency by introducing the comfortable noises and enabling the MS to detect system information sent from paging groups. 28.4 Capabilities None. 28.5 Implementation This describes how to configure DTX and DRX. 28.6 Maintenance Information None. 28.7 References
Issue 02 (2008-06-30)
28-1
28.1 Overview
This describes the definitions of DTX and DRX and purposes of applying DTX and DRX. DTX and DRX mechanism reduces the interference level and improves the system efficiency. Through this mechanism, the wastage of system resources can be minimized and meanwhile an acceptable signal quality is maintained.
Definition
l
Discontinuous Transmission When the MS is engaged but no speech signals are transferred, the MS sends only comfortable noises to the peer end. These comfortable noises are added deliberately and periodically. The information contained in the comfortable noises is less than the information contained in the sampled data of normal speeches.
Discontinuous Reception The MS in idle mode detects only the paging channels within a specific paging group. When other paging groups send paging messages to the MS, the MS blocks the receive channel.
Purposes
l
DTX The 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, the 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.
DRX 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, the 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. This also save power.
Terms
None.

None.
28.2 Availability
This lists the NEs and software required for the implementation of DTX and DRX.
NEs Involved
Table 28-1 lists the NEs involved in DTX and DRX.
Table 28-1 NEs involved in DTX and DRX MS

NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 28-2 lists the versions of GBSS products that support DTX and DRX. Table 28-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
None.

This describes the technical aspects of DTX and DRX. The DTX and DRX improve the system efficiency by introducing the comfortable noises and enabling the MS to detect system information sent from paging groups. 28.3.1 DTX This describes DTX. Through this mechanism, the transmit power of an MS is reduced when the MS does not receive any speech signals. DTX is used to improve the speech services of the entire radio network.
28.3.2 DRX This describes DRX. In DRX mode, every MS (IMSI) 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.
28.3.1 DTX
This describes DTX. Through this mechanism, the transmit power of an MS is reduced when the MS does not receive any speech signals. DTX is used to improve the speech services of the entire radio network. DTX involves the following technical aspects:
l l l
Silence Descriptor (SID) frames Voice Activation Detection (VAD) technique 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 technique enables the MS to accurately detect speech signals. The principles of SID frames and the VAD technique are described as follows:
l
Silence Descriptor (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, which is 260 bits each in length, are constructed 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 identify 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 completes the interleaving process with the voice frame before it and the next SID. The DTX function is optional. UL DTX and DL DTX are independent from each other. The control unit of DTX is a cell. UL DTX and DL DTX are independent from each other, the two processes are respectively activated by related system parameters:
l l
The UL DTX is activated by the parameters DtxMeasUsed and UL DTX on the BSC side. The DL DTX is activated by the "DTX Flag" in the "Service/BSC Table on the MSC side and by the DtxMeasUsed and DL DTX on the BSC side.
DTX is used only in voice transmission mode and non-transparent data transmission mode. UL DTX depends on the input to the MS and DL DTX depends on the input to the MSC/TRAU.
l
VAD When DTX is enabled, the coder must decide whether the current signal is a speech signal or a noise signal. The VAD technique is designed to help the coder to make the decision. The VAD technique distinguishes the speech from the noise based on a principle that the energy of noises is always lower than that of speeches. VAD specifies a threshold for the power of the voice signal based on the power of the noise signal in actual environment. Only the signal with power value greater than the threshold is identified as voice. The VAD technique is closely associated with the speech coding algorithm. VAD compares the energy of filtered signals with the threshold defined by itself, and then decides whether
28-4
Issue 02 (2008-06-30)
every output frame contains the speech or the 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 of voice block for decision on whether the next 20 ms voice block is voice or noise. In case a strong background noise, the noise signal is identified as the voice by VAD and is sent after encoding. Two measurement methods are available in the GSM: global measurement and local measurement.
l
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: measures the receive level and receive quality in 12 timeslots and calculates the average value, including eight continuous TCH bursts and four SACCH bursts carrying measurement reports.
To ensure consistency, the BTS and the MS perform the global and local measurements regardless of the activated UL/DL DTX. Each SACCH measurement report of the BTS and the MS specifies whether the DTX function is applied, so the BSC can select the global measurement or local measurement for decision based on the measurement report.
NOTE
In downlink, the network set SRO to 1 when sending frame B
28.3.2 DRX
This describes DRX. In DRX mode, every MS (IMSI) 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 not enough. 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 the CCCH message blocks that a cell owns reflects the resources that can be used as the AGCH or the PCH in the cell. Table 28-3 lists the mapping relation between the CCCH Conf and the number of CCCH message blocks in the BCCH multi-frame structure. Table 28-3 Relation 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 Number of CCCH Message Blocks in BCCH Multi-Frame 9 3
Issue 02 (2008-06-30)
28-5
CCCH Configuration 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 18 27 36
BS_AG_BLKS_RES specifies the number of CCCH message blocks used as the AGCH in the BCCH multi-frame structure. BS-PA-MFRARMS 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 = (Number of CCCH Message Blocks in BCCH Multi-Frame BS_AG_BLKS_RES) x BS-PA-MFRARMS
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 BS-PAMFRARMS 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.
28.4 Capabilities
None.
28.5 Implementation
This describes how to configure DTX and DRX. 28.5.1 Configuring DTX This describes how to configure DTX on the BSC6000 Local Maintenance Terminal. 28.5.2 Configuring DRX This describes how to configure DRX on the BSC6000 Local Maintenance Terminal and Local Maintenance Terminal.
28.5.1 Configuring DTX

This describes how to configure DTX on the BSC6000 Local Maintenance Terminal.
28-6
Issue 02 (2008-06-30)
Prerequisite
NOTE
l l
The setting of uplink DTX is completed only on the BSC side. The setting of downlink DTX should be performed on both the BSC side and the MSC side; otherwise, the downlink DTX does not work. Data configuration on the MSC side: The setting of "DTX Flag" in the "Servie/BSC Table" determines whether downlink DTX is allowed on the MSC side.
l l
If Yes is selected, the downlink DTX is enabled. The MSC attaches the DTX flag in the assignment message, requesting the BSS to read the DTX flag. If No is selected, the downlink DTX is disabled. The MSC does not request the BSS to read the DTX flag.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell, and then choose Configure Cell Attributes from the shortcut menu. The Configuring Cell Attributes dialog box is displayed. Step 2 Double-click the target cell in the Cell view list box to add it to the Selected cells list box. Step 3 Click Next. The Configuring Cells Attributes dialog box is displayed. Step 4 Double-click the target cell in the Cell view list box to add it to the Selected cells list box. Step 5 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 28-1.
Issue 02 (2008-06-30)
28-7
Step 6 Click Handover Data. The Set Handover Parameter dialog box is displayed. Step 7 Click Advanced. The dialog box as shown in Figure 28-2 is displayed. Select the Filter/Penalty Data tab.
28-8
Issue 02 (2008-06-30)
Step 8 Set DtxMeasUsed to Open, and then click OK to return to Figure 28-1. Step 9 In Figure 28-1, set UL DTX to Shall use to configure uplink DTX. Step 10 In Figure 28-1, select DL DTX and click OK. The configuration of downlink DTX is complete. ----End
28.5.2 Configuring DRX

This describes how to configure DRX on the BSC6000 Local Maintenance Terminal and Local Maintenance Terminal.
Procedure
Issue 02 (2008-06-30)
28-9
Figure 28-3 Setting Cell Attributes dialog box
Step 5 Click Idle Mode. The Browse Idle Parameter dialog box is displayed. Step 6 Set BS_AG_BLKS_RES and BS-PA-MFRARMS. Click OK to complete the configuration. ----End

None.
Alarms
None.
Counters
None.
28.7 References
3GPP TS 05.02
Issue 02 (2008-06-30)
28-11
29 Location Service
29
About This Chapter
Location Service
29.1 Overview This describes location service. Although the precision of the GSM location service is not high, it can meet the current requirements of the customers in the mobile communications market. 29.2 Availability This lists the NEs, software, NSS, BSS, and license required for the implementation of location service. 29.3 Technical Description This describes the technical aspect of LCS. Location service is realized through the interaction between the software and hardware entity in an LCS server and that in an LCS client. 29.4 Capabilities This describes the positioning precision of location service. 29.5 Implementation This describes how to configure location service and simple location service. 29.6 Maintenance Information This describes the alarms and counters related to location service. 29.7 References
Issue 02 (2008-06-30)
29-1
29 Location Service
29.1 Overview
This describes location service. Although the precision of the GSM location service is not high, it can meet the current requirements of the customers in the mobile communications market.
Definition
An MS can be positioned according to the longitude and latitude of the GSM BTS and the timing advance (TA) value.
Purposes
The location service (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 conditions. For single-user message trace, the simple location service can locate the user based on the related information.
Terms
None.

Acronyms and Abbreviations PLMN LCS TA Full Spelling PLMN Public Land Mobile Network LoCation Service Timing Advance
29.2 Availability
This lists the NEs, software, NSS, BSS, and license required for the implementation of location service.
NEs Involved
Table 29-1 lists the NEs involved in location service. Table 29-1 NEs involved in location service MS
29-2
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Issue 02 (2008-06-30)
29 Location Service
MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 29-2 lists the NEs and software versions that support location service. Table 29-2 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
The location service is available only when both the NSS and BSS support it. Location service requires a license on the BSS side.

This describes the technical aspect of LCS. Location service is realized through the interaction between the software and hardware entity in an LCS server and that in an LCS client. 29.3.1 Concepts This describes the concepts related to location service: LCS server and LCS client. 29.3.2 Location Service Processing Procedure This describes the processing procedure of location service. 29.3.3 Location Estimate This describes Location Estimate, which indicates the location information on an MS. 29.3.4 Message Format This describes the IEs of two messages between the BSC and the MSC.
29.3.1 Concepts
This describes the concepts related to location service: LCS server and LCS client.
l
LCS server The LCS server is the software and hardware entity that provides location service. The LCS server receives service requests and responds to the requests. It consists of components that are distributed in one or more PLMNs.
LCS client
Issue 02 (2008-06-30)
29 Location Service
The LCS client is the software and hardware entity that obtains location information for one or more MSs. The LCS client interacts with the LCS server. To obtain location information, the LCS client subscribes to location service from the LCS server.

The LCS client may and may not interact with the MS. The LCS client formats data, displays data, and manages GUI. Each LCS client has a unique international identifier.
29.3.2 Location Service Processing Procedure

This describes the processing procedure of location service. The LCS server is located inside the BSC. Figure 29-1 shows the processing procedure of location service. Figure 29-1 Processing procedure of location service
BSC Perform Location Request Perform Location Response (Abort) MSC
1. 2.
l
On receiving a location request from an MS, the MSC sends a Perform Location Request message to the BSC. On receiving the Perform Location Request message, the BSC performs as follows: If the serving cell of the MS does not support location service, the BSC performs no processing and sends no response message to the MSC. If the serving cell of the MS supports location service but does not support the location algorithms required by the MSC, the BSC sends a Perform Location Response message to the BSC. The cause value of the message is Position Method Failure.
NOTE
As shown in Figure 29-1, Perform Location Response (Abort) indicates two conditions: 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.
l
If the serving cell of the MS supports the location service and required location algorithms, the BSC calculates the required information by referring to the data configuration and TA value. Then, the BSC sends a Perform Location Response message to the MSC.
29.3.3 Location Estimate

This describes Location Estimate, which indicates the location information on an MS. Location Estimate indicates the location information on an MS. Represented by a certain shape, Location Estimate indicates the possible area where an MS is located. According to related protocols, location information can be represented by seven shapes, including Ellipsoid Point, Ellipsoid point with uncertainty circle, Polygon, and Ellipsoid Arc.
29 Location Service
The Huawei BSC uses the CELL+TA positioning method. Location Estimate is represented by Ellipsoid Arc, as shown in Figure 29-2. Figure 29-2 Location information represented by Ellipsoid Arc
North
Point(o)
q b
r1
r2
: offset angle, that is, azimuth of the antenna r1: inner radius Point (o): indicates the coordinate of a location. Point (o) is identified by the longitude and latitude of the location.
: included angle r2: uncertainty radius
NOTE
If r1 = 0, the arc is a sector. In addition, if = 0 and = 360, the arc is a circle, which represents an omnidirectional cell.
Generated by the LCS server, the Location Estimate indicates the location area of the positioning target. Location Estimate is contained in the Perform Location Response message. Figure 29-3 shows the coding of the Location Estimate represented by Ellipsoid Arc.
Issue 02 (2008-06-30)
29-5
29 Location Service
Figure 29-3 Coding of the Location Estimate represented by Ellipsoid Arc

8 1 S Degrees of latitude 7 0 6 1 5 0 4 3 2 1 Octet 1 Octet 2 Octet 3 Octet 4 Octet 5 Degrees of longitude Octet 6 Octet 7 Inner radius Octet 8 Octet 9 0 Space Uncertainty radius Offset angle Included angle 0 Space Confidence Octet 10 Octet 11 Octet 12 Octet 13
Space
Table 29-3 Description of coding for the Location Estimate represented by Ellipsoid Arc Name S Meaning Bit value 0 = North Bit value 1 = South Degrees of latitude The latitude of Point (o), as shown in Figure 29-2. N = [X x 223/90], where [ ] is an integral function. The value of N ranges from 0 to 2231. Assume that N is the coding of the latitude, and X is the absolute value of the actual latitude. The value of X ranges from 0 to 90. N is coded in 24 bits: 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 2231.
29-6
Issue 02 (2008-06-30)
29 Location Service
Name Degrees of longitude
Meaning The longitude of Point (o), as shown in Figure 29-2. N = [X x 224/360], where [ ] is an integral function. The value of N ranges from 223 to 2231. Assume that N is the coding of the longitude, and X is the absolute value of the actual longitude. The value of X ranges from 180 to +180. N is coded in 24 bits (bit 0 to bit 23) and is represented by two's complement.
NOTE When X = 180, the value of N is 2231.
Inner radius
r1, as shown in Figure 29-2. N = [R/5], where [ ] is an integral function. Assume that N is the coding of inner radius, and X is the actual value of inner radius. N is coded in sixteen bits (bit 0 to bit 15).
Uncertainty radius
r2, as shown in Figure 29-2. r = C((1 + x)k 1), where C = 10 and x = 0.1. Assume that K is the coding of Uncertainty radius, and r is the actual value of Uncertainty radius. K is coded in seven bits (bit 0 to bit 6). The value of K ranges from 0 to 127.
Offset angle
, as shown in Figure 29-2. N = [a/2], where [ ] is an integral function. The value of N ranges from 0 to 180. Assume that N is the coding of the angle, and a is the actual value of the angle. N is coded in eight bits (bit 0 to bit 7).
Included angle
, as shown in Figure 29-2. N = [a/2], where [ ] is an integral function. The value of N ranges from 0 to 180. Assume that N is the coding of the angle, and a is the actual value of the angle. N is coded in eight bits (bit 0 to bit 7).
Confidence
Confidence indicates the possibility that an MS is located in the area represented by Ellipsoid Arc. K is the coding of confidence and is coded in seven bits (bit 0 to bit 6). The value of K ranges from 0 to 100.
NOTE
The value of r1+r2 is determined by the tilt and height of the antenna, and the value of r1 is determined by TA.
Issue 02 (2008-06-30)
29-7
29 Location Service
The Location Estimate can be configured on the BSC6000 Local Maintenance Terminal. For details, refer to Step 2 in 29.5.1 Configuring Location Service.
29.3.4 Message Format

This describes the IEs of two messages between the BSC and the MSC. Table 29-4 describes the Perform Location Request message from the MSC to the BSC. Where, n indicates n bytes. Table 29-4 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 the LCS client the channel that is assigned to the current service The priority of location service. Level 0 is the highest priority, and level 1 is the normal priority. Transmission Direction Both Both Length (Bytes) 1 3n
Cell Identifier Classmark Information Type 3 LCS Client Type Chosen Channel
Both Both Both Both
5-10 3-14 3n 2
LCS Priority
Both
3n
LCS QoS
QoS of location Both service. The parameters related to LCS QoS include horizontal precision and vertical precision. GPS assistance data Protocol data unit of the BSS LAPD layer MSCBSS Both
3n
GPS Assistance Data APDU
3n 3n
29-8
Issue 02 (2008-06-30)
29 Location Service
Table 29-5 describes the Perform Location Response message that the BSC sends to the MSC. Where, n indicates n bytes. Table 29-5 Perform Location Response message Information Element Message type Location Estimate Description Message type Location information on an MS Positioning data, including the resolution and positioning method deciphering keys, including encryption identifier, current deciphering key, and deciphering key of the next data frame Cause value of location service Transmission Direction Both Both Length (Bytes) 1 3-22
Positioning Data
Both
3n
Deciphering Keys
BSSMSC
3n
LCS Cause
Both
3n
29.4 Capabilities
This describes the positioning precision of location service. The positioning precision depends on the following factors:
l
Angle of antennas in a cell: Directional antennas have higher positioning precision than omnidirectional antennas. Movement speed of the LCS client: The faster the LCS client moves, the lower the positioning precision is. Precision of the location data configured in a cell.
NOTE
If all the following conditions are met, an MS can be positioned in a sector area that has a radius of 500 meters (the distance of one TA). The conditions are as follows: The location of the MS is unchanged. The transmission quality of radio signals is good. The data configuration of a cell is correct. The Cell+TA positioning method is used.
29.5 Implementation
This describes how to configure location service and simple location service. 29.5.1 Configuring Location Service
29 Location Service
This describes how to configure location service on the BSC6000 Local Maintenance Terminal. 29.5.2 Configuring Simple Location Service This describes how to configure simple location service on the BSC6000 Local Maintenance Terminal.
29.5.1 Configuring Location Service

This describes how to configure location service on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license of NC2 is applied and activated. To apply for and activate the license, do as follows: 1. When applying for the LCS license, ensure that the Number of resources column corresponding to Whether to activate the LCS(CELLID+TA) function or not under Function control items row in BSC6000V900R008 (None) Commercial License Application Template is set to 1. Value 1 indicates that this function should be enabled. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Procedure
Step 1 Configure the BSC to support location service. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Configure BSC Attributes on the shortcut menu. A dialog box is displayed. Click the Software Parameters tab. Set LCS Support Control to Yes, as shown in Figure 29-4.
2.
29-10
Issue 02 (2008-06-30)
29 Location Service
Figure 29-4 Configuring the LCS Support Control parameter
Step 2 Configure the LCS attributes of a cell. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page, and choose Configure Cell Attributes . In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 29-5.
Issue 02 (2008-06-30)
29-11
29 Location Service
4.
Click Other Attributes. A dialog box is displayed. Click Advanced. A dialog box is displayed, as shown in Figure 29-6.
29-12
Issue 02 (2008-06-30)
29 Location Service
5. 6.
Click the LCS Parameters tab, and then set the parameters as required. Click OK to return to the upper-level menu until configuring location service is complete.
----End
Postrequisite
In a location service enabled cell, use an MS to make a test call. On the BSC6000 Local Maintenance Terminal, enable the MS tracing function to trace the call signaling of the MS. When analyzing the signaling on the A interface, you can find the Perform Location Request and Perform Location Response messages. If the Perform Location Response message contains the Location Estimate IE, you can infer that location service is active. If you select Display Location Information, the location information is displayed.
29.5.2 Configuring Simple Location Service

This describes how to configure simple location service on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, click the Trace & Monitor tab. Then, doubleclick Trace User Message on the tab page. A dialog box is displayed, as shown in Figure 29-7.
Issue 02 (2008-06-30)
29-13
29 Location Service
Step 2 Select Display Location Information in the Set Display area to configure simple location service.
NOTE
For details on how to configure the parameters in the dialog box shown in Figure 29-7, refer to 9.6.1 Configuring Message Tracing.
Step 3 Click OK to complete the parameter settings for single-user message tracing and to save the trace message file. Step 4 On the BSC6000 Local Maintenance Terminal, click the Trace & Monitor tab. Then, doubleclick Review Tracing on the tab page. Select a trace message file and open it. A window is displayed, as shown in Figure 29-8. In the window shown in Figure 29-8, the Location Information column lists the location information about the user during the period of message trace.
29-14
Issue 02 (2008-06-30)
29 Location Service
Figure 29-8 Trace User Message window
----End

This describes the alarms and counters related to location service.
Alarms
None.
Counters
None.
29.7 References
3G TS 23.032 V3.1.0 (2000-03)
Issue 02 (2008-06-30)
29-15
30 TFO
30
About This Chapter
30.1 Overview This describes the application of the TFO in improving voice quality. 30.3 Impact This describes the impact of TFO on other system features.
TFO
30.2 Availability This lists the NEs, software, and voice coding schemes required for the implementation of TFO.
30.4 Technical Description This describes the application of the TFO. Once a call connection is established, the TRAU frame is used for channel activation so that the TFO message response mechanism is established. The rearranged speech frames form the TFO frames so that the codec process is reduced to such a level that the speech quality is significantly improved. 30.5 Capabilities This describes the TFO capabilities with different service types. 30.6 Implementation This describes how to configure and verify TFO. 30.7 Maintenance Information None. 30.8 References
Issue 02 (2008-06-30)
30-1
30 TFO
30.1 Overview
This describes the application of the TFO in improving voice quality.
Definition
There is a process called the Tandem Operation during a conversation in which the speech is transcoded two times. Speech signals are degraded due to Tandem Operation, as shown in Figure 30-1. Figure 30-1 Tandem operation
Speech frame BTS BSC (TC) PCM MSC PCM BSC (TC) BTS Speech frame
Encoding
Speech compression
Decoding
A-law/u-law PCM
Encoding
Speech compression
Decoding
Figure 30-2 shows the Tandem Free Operation in which the speech signals are transparently transferred between two MSs. Figure 30-2 TFO
Speech frame BTS BSC (TC) PCM MSC PCM BSC (TC) BTS Speech frame
Disable Tandem operation
TFO
Disable Disable Tandem Tandem operation operation
TFO
Disable Tandem operation
Endcoding
Speech compression
Decoding
Purposes
TFO eliminates one encoding/decoding process to improve the speech quality.
Terms
Terms TFO Definition Tandem Free Operation: It eliminates one encoding/decoding process during an MS-MS call.
30-2
Issue 02 (2008-06-30)
30 TFO
Terms IPE
Definition 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 on. The TFO MESSAGE is the in-band signaling used for TFO negotiation between TCs. As shown in Figure 30-2, TRAU frame is the speech data format used between the MS and the TC. TFO frame is the speech data format used between the TCs once the TFO is established.
TFO MESSAGE TFO FRAME

Acronyms and Abbreviations AEC ALC EFR FR HR IPE MOS TFO TRAU Full Spelling Acoustic Echo Cancellation Adaptive Level Control Enhance Full Rate speech codec Full Rate speech codec Half Rate speech codec In Path Equipment Mean Opinion Score Tandem Free Operation Transcoding and Rate Adaptation Unit
30.2 Availability
This lists the NEs, software, and voice coding schemes required for the implementation of TFO.
NEs Involved
Table 30-1 lists the NEs involved in TFO. Table 30-1 NEs involved in TFO MS BTS BSC MSC MGW SGSN GGSN HLR
Issue 02 (2008-06-30)
30-3
30 TFO
MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 30-2 lists the versions of GBSS products that support TFO. Table 30-2 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
The BSC supports the TFO in the FR, HR, EFR coding schemes. It dos not support the TFO in the AMR HR and AMR FR coding schemes. When BSC Subrack Combination Type is set to IP on A Interface, the BSC does not support TFO. When BSC Subrack Combination Type is set to BM/TC Together:
l l
If the TDM mode is applied on the Abis interface, the BSC supports TFO. If the HDLC/IP mode is applied on the Abis interface, the BSC does not support TFO.
30.3 Impact
This describes the impact of TFO on other system features.

None

Once TFO is enabled, the system disables the AEC/ALC/ANR associated with the FR/EFR/HR services.

This describes the application of the TFO. Once a call connection is established, the TRAU frame is used for channel activation so that the TFO message response mechanism is established. The rearranged speech frames form the TFO frames so that the codec process is reduced to such a level that the speech quality is significantly improved.
30 TFO
30.4.1 TFO Messages This describes the TFO message types, namely, TFO_REQ, TFO_ACK, and IS_IPE. 30.4.2 TFO Frame This describes the TFO frame, which is actually a bit conversion format of the TRAU (see GSM Rec.08.60). 30.4.3 TRAU Operating Process in TFO Mode This describes the TRAU operating process in ideal and abnormal cases. 30.4.4 Realization of TFO This describes how the TRAU activates a channel on the Abis interface, transfers TFO messages, and establishes acknowledgement mechanism.
30.4.1 TFO Messages

This describes the TFO message types, namely, TFO_REQ, TFO_ACK, and IS_IPE.
Transmission of TFO Messages

TFO messages are transmitted in bit spacing schemes. In other words, the least significant bit in the first sample of the 16 PCM samples is replaced. This minimizes the impact caused by bit replacement.
Classification of TFO Messages

l
TFO_REQ messages This command type requests to activate the TFO feature. TFO_ACK messages This command type responds to the TFO_REQ commands. IS_IPE messages The IS_IPE messages are classified into FO_TRANS messages and TFO_NORMAL messages.
The TFO_TRANS messages are used to activate and maintain the ability of the IPE equipment to support the TFO feature. The TFO_NORMAL messages are used to revert the IPEs to normal operation.
NOTE
The TFO_FILL does not belong to IS_IPE in terms of classification. Its enables the IPE to synchronize with the TFO message in short. The TFO_FILL is mainly used to re-synchronize the IPEs in abnormal cases.
l
Other commands
When the TFO_DUP command is used in intra-cell and inter-cell handovers, the TFO connection between the newly activated TRAU channels and the original TRAU channels can be established immediately. The TFO_SYL command reports that the synchronization information of the TFO frame is lost. It is mainly used for channel handover.
30.4.2 TFO Frame

This describes the TFO frame, which is actually a bit conversion format of the TRAU (see GSM Rec.08.60).
30 TFO
The TFO frame occupies the two least significant bits of the 8-bit PCM frame. The remaining six bits are still used for transmitting the decoded speech signals. In other words, when the TFO is activated, the decoder of the TRAU is still in work. On receiving the TRAU frame through the Abis interface, the decoder performs decoding and A-law conversion of the TRAU frame, and generates a new PCM frame by combining the six most significant bits of the TRAU frame with the TFO frame.
30.4.3 TRAU Operating Process in TFO Mode

This describes the TRAU operating process in ideal and abnormal cases.
TRAU Operating Process in Idea Case (Simple Mode)

1. 2. The TRAU is activated when it receives a speech frame. The encoder and decoder are activated at the same time. The TRAU activates the TFO protocol processor, sends the TFO_REQ message on the A interface, and monitors the TFO messages on the A interface (check whether there is TFO_REQ or TFO_ACK sent from the remote end). If the coding format of the TRAUs matches at two ends, the TRAU initiates the uplink TFO and begins to send TFO frames. The TRAU also embeds TFO_TRANS messages into the TFO frames to maintain the "direct pass-through" function of the IPE. On receiving the remote TFO frames through the A interface, the TRAU initiates the downlink TFO and deactivates the encoder. The TFO protocol processor is then responsible for the construction and transmission of downlink TRAU frames. If the synchronization with the BTS fails in 10 successive frames, the current channel is regarded being released. The TRAU deactivates the decoder and the TFO protocol processor.
3.
4.
5.
Handling in Abnormal Cases

l
After a channel is activated, the TRAU sends consecutive TFO_REQ commands. If no response is received when the number of TFO_REQ commands has exceeded the threshold, the TRAU stops sending TFO messages but keeps monitoring the TFO messages on the A interface until the channel is released. If the coding format of the TRAUs does not match at two ends, the TRAU aborts the establishment of TFO links and returns to normal operation. Bit errors occur during the transmission of TFO frames and TFO messages. Bit errors are detected through comparison between synchronization bits and Cyclic Redundancy Check (CRC). The TFO messages can do certain error correction of the bit errors. However, the bits to be corrected differ. For details, refer to the protocols listed in 30.8 References. If the TFO frames cannot be normally received due to bit errors, only synchronization bit errors are allowed based on the DTX status. If there are error parameters, the current frame should be discarded and replaced with the preceding good one.
Synchronization lost of the TFO frames In normal situations, the synchronization lost of the TFO frames are mainly caused by the instant channel handover. The TRAU has no knowledge of the channel handover information. Therefore, if there is synchronization lost of TFO frames, 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 responses with the TFO_DUP. If the
30-6
Issue 02 (2008-06-30)
30 TFO
connection is established within a predefined period, the current status of the call remains; if the connection is not established within the predefined period, the local TRAU quits the TFO status.
30.4.4 Realization of TFO

This describes how the TRAU activates a channel on the Abis interface, transfers TFO messages, and establishes acknowledgement mechanism. 1. 2.
l
During the call setup process, the TRAU searches for valid TRAU frames on the Abis interface to activate the current channel. When the channel is activated, the TRAU activates the encoder and decoder, and inserts TFO messages in the PCM samples on the A interface by using the bit stealing scheme. If the TFO message acknowledgment mechanism is not established within a predefined period, the TRAU performs the transcoding in a normal way. If the TFO message acknowledgment mechanism is established, the TRAU rearranges the speech frames received on the Abis interface, forms the TFO frames, and then transmits the TFO frames to the remote TRAU. On receiving the TFO frames, the remote TRAU processes the bits that constitute the TFO frames, forms the TRAU frames, and then transmits the TRAU frames over the Abis interface. As the speech signals are encoded and decoded only in the MS, this prevents repeated transcoding and can thus improve speech quality.
30.5 Capabilities
This describes the TFO capabilities with different service types. In the TFO, the Mean Opinion Score (MOS) of the HR services increases by 0.3-0.5, the FR services by 0.2-0.4, and the EFR services by 0.1-0.3.
30.6 Implementation
This describes how to configure and verify TFO. 30.6.1 Configuring TFO This describes how to configure TFO on the BSC6000 Local Maintenance Terminal. 30.6.2 Verifying TFO This describes how to verify TFO on the BSC6000 Local Maintenance Terminal.
30.6.1 Configuring TFO

This describes how to configure TFO on the BSC6000 Local Maintenance Terminal.
Context
Configure TFO according to the setting of BSC Subrack Combination Type:
l
In BM/TC separate mode, the TFO should be configured in the GDPUC/GDPUX of the GTCS. The TFO need not be configured in the GDPUX of the GMPS/GEPS.
Issue 02 (2008-06-30)
30 TFO
l
In BM/TC together mode and that the TDM mode is applied on the Abis interface, the TFO should be configured in the GDPUX of the GMPS/GEPS. In A over IP mode, the TFO is not supported.
Procedure
Step 1 Configure the attributes of different boards according to the BSC subrack combination modes.
l
BM/TC separate On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click the GDPUC/GDPUX of the GTCS and select Configure Board Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 30-3.
Figure 30-3 Configuring GDPUC/GDPUX attributes
BM/TC together On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click the GDPUX of the GMPS/GEPS and select Confiugre Board Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 30-4.
30-8
Issue 02 (2008-06-30)
30 TFO
Figure 30-4 Configuring GDPUC attributes
Step 2 Click Next. A dialog box is displayed, as shown in Figure 30-5. Figure 30-5 Configuring the TFO feature
Step 3 Select Configure All and set TFO Switch to Open. Step 4 Click Finish. The configuration is complete. ----End
Issue 02 (2008-06-30)
30-9
30 TFO
30.6.2 Verifying TFO

This describes how to verify TFO on the BSC6000 Local Maintenance Terminal.
Context
Verify TFO according to the setting of BSC Subrack Combination Type:
l l
In BM/TC separate mode, verify TFO of the GDPUC/GDPUX in the GTCS. In BM/TC together mode, verify TFO of the GDPUX in the GMPS/GEPS.
NOTE
This takes the example of verifying TFO of the GDPUC in the GTCS in the BM/TC separate mode.
Procedure
Step 1 On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click the GDPUC of the GTCS and selectQuery DSP Resources from the shortcut menu. A dialog box is displayed, as shown inFigure 30-6.
30-10
Issue 02 (2008-06-30)
30 TFO
Figure 30-6 Querying DSP resources
Step 2 Click the DSP Channel/Link State. A dialog box is displayed, as shown in Figure 30-7.
Issue 02 (2008-06-30)
30-11
30 TFO
Figure 30-7 Querying DSP channel/link state
Step 3 Select the corresponding Subrack No., Slot No., and DSP No., and then click Query. If there are TCHs whose TFO status is activated, you can infer that the TFO verification succeeds. ----End

None.
Alarms
None
Counters
None
30 TFO
30.8 References
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 08.62: "Inband Tandem Free Operation (TFO) of Speech Codecs; Service Description; Stage 3"
Issue 02 (2008-06-30)
30-13
31 PBT
31
About This Chapter
31.2 Availability This lists the NEs, software, and licenses required for the implementation of PBT. 31.3 Impact This describes the impact of PBT on system performance and on other features.
PBT
31.1 Overview This describes the power boost technology (PBT), which can be used to expand the radio coverage of BTSs.
31.4 Technical Description This describes the technical aspects of PBT. In PBT mode, one signal is divided into two signals. The two signals are amplified and then combined into one. Thus, the transmit power is almost doubled. 31.5 Capabilities This describes the combination power of PBT and the capabilities of dynamic PBT. 31.6 Implementation This describes how to configure PBT and configure dynamic PBT. 31.7 Maintenance Information This lists the alarms and counters related to PBT. 31.8 References None.
Issue 02 (2008-06-30)
31-1
31 PBT
31.1 Overview
This describes the power boost technology (PBT), which can be used to expand the radio coverage of BTSs.
Definition
The PBT is a power boost technology. In PBT mode, the double-transceiver unit serves as a single transceiver. One signal output through modulation and DA conversion is divided into two RF signals, which then enter the power amplifier for amplification. Then, the amplified signals are combined. 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 corresponding timeslots on the two TRXs of a double-transceiver unit are set to PBT, and other timeslots are set to non-PBT. After the timeslots in PBT mode are released, they can be set to non-PBT.
Purposes
PBT is used to expand the radio coverage of BTSs and is applicable to the areas with wide coverage. In PBT mode, the downlink signal strength is increased. At the same time, if the UL signals are optimized during network construction, the overall radio coverage is expanded. Dynamic PBT makes full use of idle timeslots and expands the coverage in the areas with weak signals, 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.
Terms
None.

Acronym and Abbreviation PBT DTRU Full Spelling Power Booster Technology Double TRansceivers Unit
31.2 Availability
This lists the NEs, software, and licenses required for the implementation of PBT.
NEs Involved
Table 31-1 describes the NEs involved in PBT.
31 PBT
Table 31-1 NEs involved in PBT MS NOTE

BTS
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 31-2 lists the versions of the GBSS products that support PBT. Table 31-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 BTS3012AE BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM DTRU DTRU Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R001C04 and later releases Not supported Not supported BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Table 31-3 lists the versions of the GBSS products that support dynamic PBT. Table 31-3 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 BTS3012AE DTRU DTRU Version V900R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases
31-3
Issue 02 (2008-06-30)
31 PBT
Product BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM
Version Not supported Not supported Not supported Not supported Not supported
Miscellaneous
PBT and dynamic PBT are controlled by the licenses.
31.3 Impact
This describes the impact of PBT on system performance and on other features.

In PBT mode, one double-transceiver unit in the BTS3012/BTS3012AE serves as one TRX. Thus, a fully configured cabinet provides only six TRXs. In dynamic PBT mode, the corresponding timeslots of the two TRXs in one double-transceiver unit form a channel group. After dynamic PBT is adopted, these channel groups are restored to independent channels. After channel groups are released, the overall capacity is the same as that in non-PBT mode.

None.

This describes the technical aspects of PBT. In PBT mode, one signal is divided into two signals. The two signals are amplified and then combined into one. Thus, the transmit power is almost doubled.
PBT
Physically, after multiple signals that have the same phase and frequency are superposed, signals can be strengthened. This principle is used in PBT. In PBT mode, one signal is divided into two signals, and then the two signals are amplified. After that, the two signals are superposed in the same phase and with the same frequency. The two signals are aligned in phase, so their combination is functionally equivalent to power amplification. Figure 31-1 shows the working principle of PBT in the DTRU.
31 PBT
Figure 31-1 Working principle of PBT in the DTRU

TX1 Control unit TX TRX0 Combiner
TCOM
TX2 TX TRX1
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 signals are transmitted through the TCOM port. When PBT is adopted, the uplink coverage may be insufficient if the UL signals are not amplified or the uplink receiver sensitivity is not improved. The UL coverage and the DL coverage may be imbalanced. Thus, measures should be taken to improve the receive quality of UL signals. You can use one of the following ways to improve the receive quality of UL signals:
l l
Configure 33 Four-Way Receive Diversity. Configure a tower mounted amplifier (TMA).
The TMA is a low noise amplifier module that is installed on a tower. After receiving UL 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. A triplex TMA is commonly used. A triplex TMA consists of the following parts:
l l l
Triplex filter Low noise amplifier Feeder
A triplex TMA processes signals as follows: 1. 2. 3. The triplex filter filters the signals from the antenna to remove the out-band interference. The low noise amplifier amplifies the weak signals. The feeder transmits the amplified signals to the indoor units.
As shown in Figure 31-2, the triplex TMA should be installed close to the antenna.
31 PBT
Figure 31-2 Installing the TMA

1 2
(1) Antenna (4) TMA
(2) Antenna support (5) Feeder
(3) Jumper (6) Cabinet
Dynamic PBT
Dynamic PBT is mainly applicable to concentric cells. If the downlink coverage in the overlaid subcell is restricted, continuous coverage is unavailable, and the capacity of the underlaid subcell is small. Thus, the underlaid subcell may be congested and the overlaid subcell may be idle. In PBT mode, only one TRX in a double-transceiver unit is used and the TRX utilization is low. Dynamic PBT supports timeslot-based PBT. In other words, two TRXs in a double-transceiver unit work independently except in some specific timeslots. Dynamic conversion is performed between channel groups and common channels. This keeps a balance among cost, capacity, and coverage. The resource utilization is increased and the coverage problem is solved to some extent.
NOTE
When the DTRU works in dynamic PBT mode, the channels with the same timeslot number on the two TRXs of the same DTRU 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 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 the same DTRU. The 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 and assigns them to the call. If the optimal channels can form a channel group but one of them is occupied by an MS, the BSC attempts to hand over the MS to another channel. After the channel is 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
31 PBT
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 the same DTRU is occupied by the call, the MS on the other channel should be handed over to other 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. In addition, 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 increased through the handover of edge calls 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 implemented through software. That is, the hardware connections of the BTS in dynamic PBT are the same as those in PBT, and only software upgrade is required.
31.5 Capabilities
This describes the combination power of PBT and the capabilities of dynamic PBT. Table 31-4 and Table 31-5 describe the output power in PBT mode. Table 31-4 Output power of the BTS3012/BTS3012AE in PBT mode Modulation Mode GMSK 8PSK Output Power of a Single TRX in DTRU Specification 1 40 W (46 dBm) 40 W (46 dBm) Specification 2 60 W (47.78 dBm) 40 W (46 dBm) Output Power in PBT Mode 100 W (49 dBm) 60 W (47.78 dBm)
Table 31-5 Output power of the DBS3900 GSM in PBT mode Output Power of a Single TRX in RRU (Non-Combination Mode) 900 M 30 W (44.77 dBm) 20 W (43 dBm) 1800 M 20 W (43 dBm) 15 W (41.76 dBm) Output Power in PBT Mode 900 M 40 W (46 dBm) 25 W (43.98 dBm) 1800 M 30 W (44.77 dBm) 20 W (43 dBm)
Modulati on Mode GMSK 8PSK
Capabilities of dynamic PBT: If a channel group works in the same manner as that in PBT mode, the output power is the same as the combination power in PBT mode. That is, the power is
31 PBT
amplified after signal combination. If a channel works in independent mode, the power is transmitted in wideband combination mode.
31.6 Implementation
This describes how to configure PBT and configure dynamic PBT. 31.6.1 Configuring PBT This describes the hardware configuration for PBT. It also describes how to configure PBT on the BSC6000 Local Maintenance Terminal. 31.6.2 Configuring Dynamic PBT This describes how to configure dynamic PBT on the BSC6000 Local Maintenance Terminal.
31.6.1 Configuring PBT

This describes the hardware configuration for PBT. It also describes how to configure PBT on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. In the Resource control items column of BSC6000V900R008 Exceptional Commercial License Application Template, locate the Number of multi-transceivers supporting PBT transmit row and specify a value in the cell corresponding to the Resource number column. The value indicates the number of DTRUs that support PBT. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Context
The DTRUs of the BTS3012 are classified into two types: DTRU (type A) and DTRU (type B). The two types of DTRUs have different panels. Therefore, the cable connections are also different. The TRX attributes and antenna feeder attributes for the DBS3900 GSM are set on the BSC side. The method of configuring PBT for the DBS3900 GSM is the same as that for the BTS3012/ BTS3012AE.
Procedure
l Configure the hardware for PBT. Figure 31-3 and Figure 31-4 show the connections between the DTRU and the DDPU in PBT mode.
31-8
Issue 02 (2008-06-30)
31 PBT
Figure 31-3 Connections between the DTRU (type A) and the DDPU in PBT mode
DDPU
RUN ALM VSWRA VSWRB
COM
POWER
RXA1
RXA2 TXA RXA3 RXA4 RXB1 RXB2 RXB3 TXB RXB4
DTRU
TX1 IN1 TCOM IN2 TX2
RUN ACT ALM RF_IND
RS T RXM1 RXD1 RXM2 RXD2
POWER
Issue 02 (2008-06-30)
31-9
31 PBT
Figure 31-4 Connections between the DTRU (type B) and the DDPU in PBT mode
DDPU
RUN ALM VSWRA VSWRB
COM
POWER
RXA1
DTRU
TX1
TCOM
TX2
RUN ACT ALM RF_IND
POWER
31-10
Issue 02 (2008-06-30)
31 PBT
For details on the descriptions of the ports on the DTRU (type A), DTRU (type B), and DDPU, refer to Table 2 and Table 3 in LEDs and Ports on the DTRU, and Table 2 in LEDs and Ports on the DDPU. l Configure the data. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target TRX and then choose Configure TRX Attributes from the shortcut menu. In the displayed dialog box, click Set TRX Attributes. In the displayed dialog box, click the Device Attributes tab. Set Send Mode to PBT, as shown in Figure 31-5. Figure 31-5 Configuring TRX attributes
2. 3.
----End
31.6.2 Configuring Dynamic PBT

This describes how to configure dynamic PBT on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. In the License control items of the BSC6000V900R008 Exceptional Commercial License Application Template, locate the Number of TRXs that support dynamic PBT row and specify a value in the cell corresponding to the Resource number column. The value indicates the number of DTRUs that support dynamic PBT.
Issue 02 (2008-06-30)
31 PBT
2.
Context
The hardware configuration for dynamic PBT is the same as that for PBT. For details, refer to 31.6.1 Configuring PBT.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell. Then, choose Configure Cell Attributes from the shortcut menu. Step 2 In the displayed dialog box, double-click the target cell. Then, click Next. Step 3 In the displayed dialog box, click Configure Cell Attributes. A dialog box is displayed, as shown in Figure 31-6.
31-12
Issue 02 (2008-06-30)
31 PBT
Step 4 In the dialog box shown in Figure 31-6, set Cell Type to Concentric cell. Then, click Channel Management. A dialog box is displayed, as shown in Figure 31-7.
Issue 02 (2008-06-30)
31-13
31 PBT
Step 5 Set Dynamic Transmission Diversity (PBT) Supported to DPBT. Then, click OK. The dialog box shown in Figure 31-6 is displayed. Step 6 Select the TRXs for the overlaid cell in the Assigned TRXs area. Then, click TRX Config. Step 7 In the displayed dialog box, click the Device Attributes tab. set Send Mode to DPBT, as shown in Figure 31-8.
31-14
Issue 02 (2008-06-30)
31 PBT
Step 8 Click OK until the configuration is complete. ----End

This lists the alarms and counters related to PBT.
Alarms
Table 31-6 lists the alarms related to the PBT. Table 31-6 Alarms Alarm ID 4110 4112 4140 4144 Alarm Name TRX Power Decrease Alarm Close HPA Alarm PAU Temperature Alarm TRX VSWR Alarm
Issue 02 (2008-06-30)
31-15
31 PBT
Counters
None.
31.8 References
None.
31-16
Issue 02 (2008-06-30)
32 Transmit Diversity
32
About This Chapter
Transmit Diversity
32.1 Overview This describes the definitions and purposes of transmit diversity and dynamic transmit diversity. Transmit diversity is a method to manually realize the multipath, thus improving downlink signal quality. 32.2 Availability This lists the NEs, software, and licenses required for the implementation of transmit diversity and dynamic transmit diversity. 32.3 Technical Description This describes the technical aspects of transmit diversity and dynamic transmit diversity. Multipath attenuation is one of the characteristics of radio channels. Through the transmit diversity and dynamic transmit diversity techniques, the signal attenuation can be minimized. 32.4 Implementation This describes how to configure transmit diversity and dynamic transmit diversity. 32.5 Maintenance Information This lists the alarms and counters related to transmit diversity. 32.6 References None.
Issue 02 (2008-06-30)
32-1
32.1 Overview
This describes the definitions and purposes of transmit diversity and dynamic transmit diversity. Transmit diversity is a method to manually realize the multipath, thus improving downlink signal quality.
Definition
In transmit diversity mode, the baseband signal of one MS is transmitted on two RF channels. As there is no correlation between two antennas, the problems of dramatic change of signal level and QoS decrease due to multipath propagation are solved, thus improving the downlink coverage performance. 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.
Purposes
The transmit diversity technique can improve the downlink signal quality, thus meeting the demanding requirements for radio communications in certain cases. Dynamic transmit diversity makes full use of idle timeslots and expands the coverage in the areas with weak signals, 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.
Terms
None.

None.
32.2 Availability
This lists the NEs, software, and licenses required for the implementation of transmit diversity and dynamic transmit diversity.
NEs Involved
Table 32-1 describes the NEs involved in transmit diversity and dynamic transmit diversity. Table 32-1 NEs involved in transmit diversity MS
32-2
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Issue 02 (2008-06-30)
MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 32-2 lists the software versions of the GBSS products that support transmit diversity. Table 32-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 BTS3012AE BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM DTRU DTRU Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Table 32-3 lists the software versions of the GBSS products that support dynamic transmit diversity. Table 32-3 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 BTS3012AE DTRU DTRU Version V900R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases
32-3
Issue 02 (2008-06-30)
Product BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM
Version BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases Not supported Not supported Not supported
Miscellaneous
The number of TRXs that support transmit diversity or dynamic transmit diversity is determined by the license.

This describes the technical aspects of transmit diversity and dynamic transmit diversity. Multipath attenuation is one of the characteristics of radio channels. Through the transmit diversity and dynamic transmit diversity techniques, the signal attenuation can be minimized.
Transmit Diversity
In the radio propagation environment, TX signals may be adversely affected by shadow attenuation, which is caused by buildings and other obstacles. TX signals arrive at the receive end in various ways, such as line-of-sight (LOS), reflections, and dispersions. As the MS moves around, Rayleigh attenuation occurs because the TX signals traveling through various paths are combined. Rayleigh attenuation causes a rapid fluctuation of the signal amplitude. Therefore, the signal quality is severely affected. Shadow attenuation and Rayleigh attenuation severely degrade the quality of RX signals. The two types of attenuation are major factors in the vulnerable radio link of the mobile communications. The transmit diversity technology uses the non-correlation feature between two routes of signals, that is, the two routes of signals have different deep fading points, to improve the quality of the received signals, thus conquering multipath fading. In transmit diversity mode, one baseband signal is transmitted through two RF channels. The signal combination in the multipath transmission is optimized. Thus, the impact of Rayleigh attenuation on the MS is reduced. The gain of transmit diversity is high in the scenarios with obvious multipath effects. In the static channel model (such as grassland and sea), transmit diversity cannot bring about obvious diversity gain, Figure 32-1 shows the transmit diversity of a double-transceiver unit. The signal from TRX0 is divided into two signals by a 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 over the antenna.
Figure 32-1 Transmit diversity
NOTE
In transmit diversity mode, one double-transceiver unit serves as only one TRX.
Dynamic Transmit Diversity

Dynamic transmit diversity is mainly applicable to concentric cells. If the downlink coverage in the overlaid subcell is restricted, continuous coverage is unavailable, and the capacity of the underlaid subcell is small. Thus, the underlaid subcell may be congested and the overlaid subcell may be idle. In transmit diversity mode, only one TRX in a double-transceiver unit is used and the TRX utilization is low. Dynamic transmit diversity supports timeslot-based transmit diversity. In other words, two TRXs in a double-transceiver unit work independently except in some specific timeslots. Dynamic conversion is performed between channel groups and common channels. This keeps a balance among 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 the 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 and assigns them to different calls. If the optimal channels can form a channel group but one of them is occupied by an MS, the BSC
attempts to hand over the MS to another channel. After the channel is 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 MS 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 used in the overlaid subcell, the coverage of the overlaid subcell is increased. That is, the edge calls can be handed over to the overlaid subcell. This keeps a traffic balance between the overlaid and underlaid subcell. Dynamic transmit diversity is implemented through software. That is, the hardware connections of the BTS in dynamic transmit diversity are the same as those in transmit diversity, and only software upgrade is required.
32.4 Implementation
This describes how to configure transmit diversity and dynamic transmit diversity. 32.4.1 Cable Connections (Transmit Diversity) This describes how to connect the cables in transmit diversity mode. 32.4.2 Configuring Transmit Diversity This describes how to configure transmit diversity on the BSC6000 Local Maintenance Terminal. 32.4.3 Configuring Dynamic Transmit Diversity This describes how to configure dynamic transmit diversity on the BSC6000 Local Maintenance Terminal.
32.4.1 Cable Connections (Transmit Diversity)

This describes how to connect the cables in transmit diversity mode.
Procedure
l The blue lines in Figure 32-2 show the cable connections between the DTRU and the DDPU in the BTS3012/BTS3012AE in transmit diversity mode.
32-6
Issue 02 (2008-06-30)
Figure 32-2 Cable connections between the DTRU and the DDPU in transmit diversity mode
DDPU
RUN ALM VSWRA VSWRB
COM
POWER
RXA1
DTRU
TX1
TCOM
TX2
RUN ACT ALM RF_IND
POWER
Issue 02 (2008-06-30)
32-7
For details on how to connect the RF cables in the BTS3012/BTS3012AE, refer to Installing the RF Signal Cables of the BTS3012/BTS3012AE. For details on the descriptions of the ports on the DTRU and DDPU, refer to LEDs and Ports on the DTRU and LEDs and Ports on the DDPU.
Figure 32-3 shows the cable connections between the DDPM and the DDRM in the BTS3006C in transmit diversity mode. Figure 32-3 cable connections between the DDPM and the DDRM in the BTS3006C in transmit diversity mode.
DDRM DSEM
TX1-
TX2-
DMCM DSEM DDPM
TXB TXA
RXB1
RUN ALM VSWR A
RUN/SLPACTALMRF_IND
RXA1
RXM1RXD1-
RXB2
VSWRB
RXA2
RXM2RXD2FAN-
RXB3
RXA3
ANTB ANTA
Figure 32-4 shows the cable connections between the DDPM and the DDRM in the BTS3002E in transmit diversity mode.
32-8
Issue 02 (2008-06-30)
Figure 32-4 cable connections between the DDPM and the DDRM in the BTS3002E in transmit diversity mode
DDPM DDRM DPSM
TX1TXB TXA
RXB1 RUN ALM VSWRB RXB2 RXA2 RXA1
TX2-
VSWR A
RXB3
RXA3
ANTB ANTA
DMCM DATM
FAN-
DOOR
For details on how to connect the RF cables in the BTS3006C/BTS3002E, refer to Installing the RF Signal Cables of the BTS3006C/BTS3002E. For details on the descriptions of the ports on the DDRM and DDPM, refer to LEDs and Ports on the DDRM and LEDs and Ports on the DDPM.
Figure 32-5 shows the cable connections in the DBS3900 GSM in transmit diversity mode.
Issue 02 (2008-06-30)
32-9
Figure 32-5 Cable connections in the DBS3900 GSM in transmit diversity mode
ANT Antenna
ANT_TX/RXA
ANT_TX/RXB
RX_IN/OUT
RRU0
CPRI_E
CPRI_W
CPRI0
CPRI5
BBU
For details on how to connect the RF cables in the DBS3900 GSM, refer to Installing the RF Cables of the RRU. For details on the descriptions of the ports on the RRU and BBU, refer to Ports of the RRU Module and Ports of the BBU.
----End
32.4.2 Configuring Transmit Diversity

This describes how to configure transmit diversity on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. In the Resource control items column of BSC6000V900R008 Exceptional Commercial License Application Template, locate the Number of multi-transceivers supporting diversity transmit row and specify a value in the cell corresponding to the Resource number column. The value indicates the number of double-transceiver units that support transmit diversity. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
32-10
Issue 02 (2008-06-30)
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target TRX and then select Configure TRX Attributes from the shortcut menu. Step 2 In the displayed dialog box, click Set TRX Attributes. A dialog box is displayed. Select the Device Attributes tab page, as shown in Figure 32-6. Figure 32-6 Setting DTRU transmit diversity mode
Step 3 Set Send Mode to Diversity Transmitter. Step 4 Click OK. The configuration is complete.
NOTE
In the case of transmit diversity, one double-transceiver unit serves as one TRX.
----End
32.4.3 Configuring Dynamic Transmit Diversity

This describes how to configure dynamic transmit diversity on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. In the License control items column of the BSC6000V900R008 Exceptional Commercial License Application Template, locate the Number of TRXs that support dynamic PBT
Issue 02 (2008-06-30)
row and specify a value in the cell corresponding to the Resource number column. The value indicates the number of TRXs that support dynamic PBT. 2. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell. Then, choose Configure Cell Attributes from the shortcut menu. Step 2 In the displayed dialog box, double-click the target cell. Then, click Next. Step 3 In the displayed dialog box, click Set Cell Properties. A dialog box is displayed, as shown in Figure 32-7. Figure 32-7 Set Cell Attributes dialog box
Step 4 In the dialog box shown in Figure 32-7, set Cell Type to Concentric cell. Then, click Channel Management. A dialog box is displayed, as shown in Figure 32-8.
Step 5 Set Dynamic Transmission Diversity (PBT) Supported to DDIVERSITY. Then, click OK. The dialog box shown in Figure 32-7 is displayed. Step 6 Select the target TRX of the concentric cell in the Assigned TRXs area. Then, click TRX Config. A dialog box is displayed. Click the Device Attributes tab, and set Send Mode to DDIVERSITY, as shown in Figure 32-9.
Issue 02 (2008-06-30)
32-13
Step 7 Click OK until the configuration is complete. ----End

This lists the alarms and counters related to transmit diversity.
Alarms
Table 32-4 lists the alarms related to transmit diversity. Table 32-4 Alarms related to transmit diversity Alarm ID 4112 4140 4144 4196 Alarm Name Close HPA Alarm PAU Temperature Alarm TRX VSWR Alarm SEND DIV Channel Alarm
32-14
Issue 02 (2008-06-30)
Counters
None.
32.6 References
None.
Issue 02 (2008-06-30)
32-15
33 Four-Way Receive Diversity
33
About This Chapter
Four-Way Receive Diversity
33.1 Overview This describes the definition and purposes of the four-way receive diversity. The four-way receive diversity combines the four-way RX signals to optimize the uplink signals. 33.2 Availability This lists the NEs, software, and license required for implementing the four-way receive diversity. 33.3 Technical Description This describes the technical aspects of the four-way receive diversity. The radio channel is a type of multipath fading channel. Through the four-way receive diversity technique, multipath attenuation can be suppressed and the power gain of the uplink signals on the radio channel and the receiver sensitivity can be improved. 33.4 Capabilities This describes the ICC gain. 33.5 Implementation This describes how to install the hardware equipment and configure the four-way receive diversity. 33.6 Maintenance Information This lists the alarms related to four-way receive diversity. 33.7 References None.
Issue 02 (2008-06-30)
33-1
33.1 Overview
This describes the definition and purposes of the four-way receive diversity. The four-way receive diversity combines the four-way RX signals to optimize the uplink signals.
Definition
The four-way RX signals are sent to one TRX simultaneously. Through the diversity combination technique, the uplink receiver sensitivity is improved.
Purposes
The four-way receive diversity technique optimizes uplink signals to meet the demanding requirements for radio communications in certain cases and to improve the uplink performance in wide coverage scenarios.
Terms
None.

Acronym and Abbreviation ICC MRC Full Spelling Interference Cancellation Combining Maximal Ratio Combining
33.2 Availability
This lists the NEs, software, and license required for implementing the four-way receive diversity.
NEs Involved
Table 33-1 lists the network elements involved in the four-way receive diversity. Table 33-1 Network elements involved in the four-way receive diversity MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
33-2
Issue 02 (2008-06-30)
Software Releases
Table 33-2 lists the NEs and software versions that support four-way receive diversity. Table 33-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 BTS3012AE BTS3006C BTS3002E BTS3900 GSM BTS3900A GSM DTRU DTRU Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
Four-way receive diversity is controlled by the license.

This describes the technical aspects of the four-way receive diversity. The radio channel is a type of multipath fading channel. Through the four-way receive diversity technique, multipath attenuation can be suppressed and the power gain of the uplink signals on the radio channel and the receiver sensitivity can be improved. 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 in various ways, such as line-of-sight (LOS), reflections, and dispersions. As the MS moves around, the Rayleigh fading is generated because the TX signals traveling through various paths are combined. In the Rayleigh fading, the signal amplitude changes very quickly. The four-way receive diversity technique can be used to suppress this type of fading. Four-way receive diversity means that four RX paths receives the same signal separately. The received signals are combined into one, and thus the uplink gain is enhanced. To ensure that the diversity antennas receives 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. Figure 33-1 shows the principles of four-way receive diversity of the DTRU. The four RX signals (RXM1, RXD1, RXM2, and RXD2) are sent to one TRX in the DTRU for combination.

NOTE
With four-way receive diversity, only one TRX in the DTRU can be used.
Figure 33-1 Working principles of the four-way receive diversity
TX1 IN1 TCOM IN2 TX2 Combiner TX TRX0
RXM1
Divider Divider
RXD1
TX RXM2 TRX1 RXD2
There are two types of four-way receive diversity techniques: Interference Cancellation Combining (ICC) and Maximal Ratio Combining (MRC). MRC is the best in the case that there is no interference and noise is restricted. MRC does not consider the correlation of interference on combining diversities. In the actual network, the interference on different diversity antennas comes from the interference signals of the same source. Therefore, the interference has a certain correlation. ICC uses this correlation to eliminate some interference. ICC is a technique developed based on MRC. When the DTRU adopts the four-way receive diversity technique, the TX signals arrive at the diversity antennas through different radio paths. This process generates combinative antenna thermal noise and co-channel interference, thus affecting the demodulation performance of the BTS. The noise of the diversity antennas has no correlation, but the co-channel interference has a certain correlation. The ICC technique takes into account the correlation between noises and between interference sources. Therefore, noise and co-channel interference are suppressed, and the demodulation performance of the BTS is enhanced. The ICC algorithm combines the diversity signals r1(k), r2(k), r3(k), and r4(k) to suppress noise and interference. Figure 33-2 shows the principles of the ICC algorithm.
Figure 33-2 ICC algorithm
RX channel 1
RX signal r1 (k )
Noise and W1 interference
S1 (k )
Noise and interference W2 RX channel 2 TX signal x(k) RX channel 3 RX signal r3 ( k ) RX signal r2 ( k )
S2 (k ) S3 (k ) S4 (k )
Noise and interference Noise and interference RX channel 4 RX signal r4 ( k )
W3
y(k)
W4
The ICC algorithm procedure shown in Figure 33-2 is described as follows: 1. The TX signal x(k) arrives at the diversity antennas through four receive paths. Then, the signals are 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, calculate the adaptive combining coefficients W1, W2, W3, and W4 and obtain the output signal value through the formula: y(k) = W1 x S1(k) + W2 x S2(k) + W3 x S3(k) + W4 x S4(k).
NOTE
2.
l l
When W1, W2, W3, and W4 are equal to 1, y(k) is the output signal value calculated through the MRC algorithm. The four receive paths shown in Figure 33-2 correspond to two pairs of main/diversity paths.
Huawei four-way receive diversity algorithm supports the MRC algorithm and the ICC algorithm with blind detection. The ICC algorithm with blind detection prevents negative gain relative to the MRC algorithm when the ICC algorithm is used in the scenario with no interference and restricted noise. The ICC algorithm with blind detection is scenario-adaptive and can determine the scenario of RX signals on each timeslot.
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 the high capability to resist multipath fading and co-channel interference, and the receiver sensitivity is improved.
33.4 Capabilities
This describes the ICC gain.
Assume that there are three interference sources in the actual network. The first interference source is 6 dB higher than the second one and 10 dB higher than the third one. In addition, the first interference source is 9 dB higher than the noise power . Table 33-3 lists the ICC gain. Table 33-3 ICC gain relative to the MRC gain Scenario Two-antenna ICC Four-antenna ICC Gain [1.5 dB, 2.0 dB] [2.5 dB, 3.5 dB]
33.5 Implementation
This describes how to install the hardware equipment and configure the four-way receive diversity. 33.5.1 Installing Hardware (Four-Way Receive Diversity) This describes how to install the hardware and connect the cables in four-way receive diversity mode. 33.5.2 Configuring Four-Way Receive Diversity This describes how to configure four-way receive diversity on the BSC6000 Local Maintenance Terminal or on the Local Maintenance Terminal.
33.5.1 Installing Hardware (Four-Way Receive Diversity)

This describes how to install the hardware and connect the cables in four-way receive diversity mode.
Procedure
Installing the RF Signal Cables of the BTS3012/BTS3012AE shows the procedure for hardware installation in four-way receive diversity mode. This takes the BTS3012/BTS3012AE as an example. The red lines in Figure 33-3 shows the connection between the DTRU and the DDPU in fourway receive diversity mode.
33-6
Issue 02 (2008-06-30)
Figure 33-3 Connection between the DTRU and the DDPU in four-way receive diversity mode
DDPU
RUN ALM VSWRA VSWRB
DDPU
RUN ALM VSWRA VSWRB
COM
COM
POWER
POWER
RXA1
RXA1
DTRU
TX1
DTRU
TX1
TCOM
TCOM
TX2
RUN ACT ALM RF_IND
TX2
RUN ACT ALM RF_IND
POWER
POWER
Table 33-4 Description of ports on the DTRU Port TX1 TCOM Type N female connector N female connector Description TX1 output Combines and exports signals from TX1 and TX2 or exports PBT combined signals.
33-7
Issue 02 (2008-06-30)
Port TX2 RXM1 RXD1 RXM2 RXD2 PWR
Type N female connector SMA female connector SMA female connector SMA female connector SMA female connector 3V3 power connector
Description TX2 output Main receive port of TRX 1 or diversity receive port 1 of TRX 1 Diversity receive port of TRX 1 or diversity receive port 2 of TRX 1 Main receive port of TRX 2 or diversity receive port 3 of TRX 1 Diversity receive port of TRX 2 or diversity receive port 4 of TRX 1 Power input
Table 33-5 Description of ports on the DDPU Port COM Type DB26 female connector Description
l
Receives control signal, communication signal, clock signal, and rack number signal from the DCTB of the BTS3012. Receives control signal, communication signal, and clock signal from the DSCB of the BTS3012AE.
POWER TXA TXB RXA1 RXA2 RXA3 RXA4 RXB1 RXB2 RXB3 RXB4 ANTA
3V3 power connector N female connector N female connector SMA female connector SMA female connector SMA female connector SMA female connector SMA female connector SMA female connector SMA female connector SMA female connector DIN female connector
Power input Combined TX input from the DTRU to the DCOM Combined TX input from the DTRU to the DCOM Main output port for route 1 Main output port for route 2 Main output port for route 3 Main output port for route 4 Diversity output port for route 1 Diversity output port for route 2 Diversity output port for route 3 Diversity output port for route 4
l
Connects to the BTS3012 indoor 1/2-inch jumper or the Bias-Tee. Connects to the BTS3012AE indoor 1/4-inch jumper or the Bias-Tee.
33-8
Issue 02 (2008-06-30)
Port ANTB
Type DIN female connector
Description
l
Connects to the BTS3012 indoor 1/2-inch jumper or the Bias-Tee. Connects to the BTS3012AE indoor 1/4-inch jumper or the Bias-Tee.
----End
33.5.2 Configuring Four-Way Receive Diversity

This describes how to configure four-way receive diversity on the BSC6000 Local Maintenance Terminal or on the Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. Apply for the license for four-way receive diversity. In the BSC6000V900R008 Exceptional Commercial License Application Template, specify a value of the Resource number corresponding to the Number of multi-transceiver unit which Receiver is Four Diversity Receiver row in the Resource control items column. The value indicates the number of multi-transceiver units that support four-way receive diversity. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target TRX and then select Configure TRX Attributes from the shortcut menu. Step 2 In the displayed dialog box, click Set TRX Attributes. A dialog box is displayed. Select the Device Attributes tab page, as shown in Figure 33-4. Set Receive Mode to Four Diversity Receiver.
Issue 02 (2008-06-30)
33-9
Figure 33-4 Setting DTRU four-way receive diversity mode
----End

This lists the alarms related to four-way receive diversity.
Alarms
Table 33-6 lists the alarms related to the four-way receive diversity. Table 33-6 Alarms related to four-way receive diversity Alarm ID 4118 Alarm Name 4-way Diversity receiving alarm
Counters
None.
33.7 References
None.
Issue 02 (2008-06-30)
33-11
34 SDCCH Dynamic Adjustment
34
About This Chapter
SDCCH Dynamic Adjustment
34.1 Overview This describes SDCCH dynamic adjustment. The SDCCH dynamic adjustment refers to the process through which the TCHF is converted to the SDCCH and the SDCCH is switched back to TCHF. The SDCCH dynamic adjustment can reduce the probability of SDCCH congestion and the impact of SDCCH initial configuration on the system performance. 34.2 Availability This lists the NEs and software required for the implementation of SDCCH dynamic adjustment. 34.3 Impact This describes the impact of SDCCH dynamic adjustment on system performance. 34.4 Technical Description This describes the technical aspects of SDCCH dynamic adjustment. SDCCH dynamic adjustment should be triggered depending on the cause of unsuccessful channel assignment, current traffic flow, and channel assignment procedure. If SDCCH dynamic adjustment is required, the BSC searches for an appropriate TCHF and triggers the SDCCH dynamic adjustment. If the adjustment is successful, the BSC uses the related algorithm to determine whether to switch back the SDCCH. If the requirements for switchback are met, the BSC switches back the SDCCH that is converted from the TCHF to the TCHF. 34.5 Implementation This describes how to configure SDCCH dynamic adjustment. 34.6 Maintenance Information This lists the counters related to SDCCH dynamic adjustment. 34.7 References None.
Issue 02 (2008-06-30)
34-1
34.1 Overview
This describes SDCCH dynamic adjustment. The SDCCH dynamic adjustment refers to the process through which the TCHF is converted to the SDCCH and the SDCCH is switched back to TCHF. The SDCCH dynamic adjustment can reduce the probability of SDCCH congestion and the impact of SDCCH initial configuration on the system performance.
Definition
When an MS fails to request an SDCCH or the SDCCH resources are insufficient, the SDCCH dynamic adjustment may be triggered. SDCCH dynamic adjustment is performed to convert the TCHF to the SDCCH. This can optimize the configuration of the SDCCH and TCHF. After the TCHF is converted to the SDCCH, the switchback of the SDCCH to the TCHF may also be triggered.
Purposes
SDCCH dynamic adjustment can optimize the utilization of traffic channels and signaling channels. It can also reduce the congestion rate of the SDCCH, the number of SDCCHs to be configured, the impact on the system performance, and the requirement for the accuracy of the required SDCCHs. For example, if the TCHs are idle but the SDCCHs are congested because the traffic volume of short messages increases or because the traffic peak hour bursts, the MSs may not be able to apply for SDCCHs and cannot access the network. After SDCCH dynamic adjustment is applied, the system capacity and call completion rate can be increased.
Terms
Terms SDCCH TCHF TCHH Definition Stand-alone Dedicated Control Channel Full-rate speech channel Half-rate speech channel

Acronyms and Abbreviations MS SDCCH Full Spelling Mobile Station Stand-alone Dedicated Control Channel
34.2 Availability
This lists the NEs and software required for the implementation of SDCCH dynamic adjustment.
NEs Involved
Table 34-1 lists the NEs involved in SDCCH dynamic adjustment. Table 34-1 NEs involved in SDCCH dynamic adjustment MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 34-2 lists the versions of GBSS products that support SDCCH dynamic adjustment. Table 34-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C04 and later releases BTS3000V100R008C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R002C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
None.
34.3 Impact
This describes the impact of SDCCH dynamic adjustment on system performance.
Issue 02 (2008-06-30)
34-3

The impact of SDCCH dynamic adjustment on system performance is as follows:
l
The bearer capacity of TCHs in a cell is reduced because the SDCCH dynamic adjustment uses the TCHFs. SDCCH dynamic adjustment requires the intra-cell handover because the seized TCH must be adjusted. This increases the traffic volume of intra-cell handovers.

None.

This describes the technical aspects of SDCCH dynamic adjustment. SDCCH dynamic adjustment should be triggered depending on the cause of unsuccessful channel assignment, current traffic flow, and channel assignment procedure. If SDCCH dynamic adjustment is required, the BSC searches for an appropriate TCHF and triggers the SDCCH dynamic adjustment. If the adjustment is successful, the BSC uses the related algorithm to determine whether to switch back the SDCCH. If the requirements for switchback are met, the BSC switches back the SDCCH that is converted from the TCHF to the TCHF. 34.4.1 SDCCH Dynamic Adjustment Procedure This describes the SDCCH dynamic adjustment procedure, which consists of the conversion of the TCHF to the SDCCH and the switchback of the SDCCH to the TCHF. 34.4.2 SDCCH Dynamic Adjustment Decision This describes the SDCCH dynamic adjustment decision. SDCCH dynamic adjustment decision is triggered after the SDCCH assignment procedure is complete. 34.4.3 SDCCH Dynamic Adjustment Algorithms This describes SDCCH dynamic adjustment algorithms. SDCCH dynamic adjustment algorithms are the TCHF selection and the conversion of the TCHF to the SDCCH. 34.4.4 SDCCH Switchback Decision This describes the SDCCH switchback decision. If the requirements for SDCCH switchback are met, the SDCCH is switched back to the original TCHF after the TCHF is converted to the SDCCH. 34.4.5 SDCCH Switchback Procedure This describes the SDCCH switchback procedure. If the requirements for SDCCH switchback are met, the BSC performs the SDCCH switchback procedure.
34.4.1 SDCCH Dynamic Adjustment Procedure

This describes the SDCCH dynamic adjustment procedure, which consists of the conversion of the TCHF to the SDCCH and the switchback of the SDCCH to the TCHF. Figure 34-1 shows the procedure for SDCCH dynamic adjustment.
34-4
Issue 02 (2008-06-30)
Figure 34-1 SDCCH dynamic adjustment procedure

Start
SDCCH dynamic adjustment decision
SDCCH dynamic adjustment implementation
SDCCH switchback decision
SDCCH switchback implementation
End
The SDCCH dynamic adjustment procedure is as follows: 1. 2. 3. 4. Determine whether to perform SDCCH dynamic adjustment. Perform SDCCH dynamic adjustment to convert idle TCHFs to SDCCHs. Determine whether to perform SDCCH switchback. Perform SDCCH switchback to convert SDCCHs to TCHFs.
34.4.2 SDCCH Dynamic Adjustment Decision

This describes the SDCCH dynamic adjustment decision. SDCCH dynamic adjustment decision is triggered after the SDCCH assignment procedure is complete. The SDCCH assignment procedure is triggered by procedures such as the immediate assignment procedure and the SDCCH incoming cell handover procedure. After an SDCCH assignment procedure is complete, the SDCCH dynamic adjustment decision is triggered if the SDCCH resources are insufficient or if the SDCCH assignment fails. When an SDCCH assignment fails, the SDCCH dynamic adjustment is triggered, but the adjusted SDCCH is used only for the next SDCCH request. Figure 34-2 shows the procedure for triggering the SDCCH dynamic adjustment decision.
Issue 02 (2008-06-30)
34-5
Figure 34-2 Procedure for triggering the SDCCH dynamic adjustment decision
Start
Is the SDCCH assignment successful? Yes
No
No
Is SDCCH dynamic adjustment required?
Is the SDCCH request triggered by channel adjustment? No
Yes
Yes Perform dynamic adjustment of the TCHF to the SDCCH
End
After the SDCCH dynamic adjustment decision is triggered, the BSC decides whether the adjustment is allowed. SDCCH dynamic adjustment is triggered only when all the conditions are met. The conditions for triggering SDCCH dynamic adjustment are as follows: 1. Whether the internal flow control level is greater than 0 If the internal flow control level is greater than 0, the SDCCH dynamic adjustment cannot be triggered. If the internal flow control level is not greater than 0, the SDCCH dynamic adjustment can be triggered. The internal flow control level can be determined by the current CPU usage. When the CPU usage is less than 65%, the internal flow control level is usually 0 if no emergency such as a burst of numerous maintenance operations occurs. Level 0 of flow control indicates that flow control is not triggered.
NOTE
For details about how to query the current CPU usage, refer to Querying the CPU/DSP Usage.
2.
Whether SDCCH Dynamic Allocation Allowed is selected If it is selected, the SDCCH dynamic adjustment can be triggered. If it is not selected, the SDCCH dynamic adjustment cannot be triggered.
3.
Whether there are an ongoing SDCCH dynamic adjustment procedure If there is an ongoing SDCCH dynamic adjustment procedure, a new DCCH dynamic adjustment cannot be triggered. If there is no ongoing SDCCH dynamic adjustment procedure, a new DCCH dynamic adjustment can be triggered.
NOTE
If an SDCCH dynamic adjustment procedure is not complete, a new SDCCH dynamic adjustment procedure is unavailable. The switchback procedure and the adjustment procedure can be performed simultaneously.
34-6
Issue 02 (2008-06-30)
4.
Whether the number of idle SDCCHs in the current cell is greater than Idle SDCCH Threshold N1 If the number of idle SDCCHs in the current cell is greater than the value of this parameter, the SDCCH dynamic adjustment cannot be triggered. If the number of idle SDCCHs in the current cell is not greater than the value of this parameter, the SDCCH dynamic adjustment can be triggered.
5.
If the SDCCH dynamic adjustment is successful, whether the number of SDCCHs in the current cell is greater than Cell SDCCH Channel Maximum after the adjustment If the number of SDCCHs in the current cell is greater than the value of this parameter after the adjustment, the SDCCH dynamic adjustment cannot be triggered. If the number of SDCCHs in the current cell is not greater than the value of this parameter after the adjustment, the SDCCH dynamic adjustment can be triggered.
NOTE
One TCHF can be converted to eight SDCCHs. Therefore, the criterion is whether the number of all the SDCCHs plus eight is greater than Cell SDCCH Channel Maximum.
6.
Whether each TRX in the cell is assigned sufficient idle TCHs. 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 twice the number of TCHFs plus the number of idle TCHHs is greater than eight. If the total number is greater than eight, the SDCCH dynamic adjustment can be triggered. If the total number is not greater than eight, the BSC proceeds with 6.3. (3) The BSC determines whether twice the number of TCHFs plus the number of idle TCHHs is greater than twice the number of TRXs in the cell. If the total number is greater than twice the number of TRXs in the cell, there are sufficient idle TCHs and the SDCCH dynamic adjustment can be triggered. If the total number is not greater than twice the number of TRXs in the cell, the SDCCH dynamic adjustment cannot be triggered.
NOTE
For details about how to determine the number of idle channels in a cell, refer to Monitoring Channel Status.
7.
Whether there are appropriate TCHFs for adjustment If there are no appropriate TCHFs for adjustment, the SDCCH dynamic adjustment cannot be triggered. If there are appropriate TCHFs for adjustment, the SDCCH dynamic adjustment can be triggered.
NOTE
For details on the TCHF selection , refer to 34.4.3 SDCCH Dynamic Adjustment Algorithms.
Figure 34-3 shows the procedure for the SDCCH dynamic adjustment decision.
Issue 02 (2008-06-30)
34-7
Figure 34-3 Procedure for the SDCCH dynamic adjustment decision

Start
Does the system performance support SDCCH dynamic adjustment? Yes Is the parameter SDCCH Dynamic Allocation Allowed selected in data configuration? Yes Yes Is SDCCH dynamic adjustment being performed in the current cell? No Measure the number of normal SDCCHs and the number of idle SDCCHs in the current cell
No
No
Is the number of idle SDCCHs not greater than Idle SDCCH Threshold N1? Yes If the conversion is performed, is the number of converted SDCCHs not greater than Cell SDCCH Channel Maximum? Yes Does each TRX in the cell have sufficient idle TCHs? Yes Is there any TCH that can be dynamically converted to the SDCCH? Yes Perform the dynamic adjustment
No
No
No
No
End
34-8
Issue 02 (2008-06-30)
34.4.3 SDCCH Dynamic Adjustment Algorithms

This describes SDCCH dynamic adjustment algorithms. SDCCH dynamic adjustment algorithms are the TCHF selection and the conversion of the TCHF to the SDCCH.
TCHF Selection
The TCHF used for SDCCH dynamic adjustment must meet the following requirements:
l l
The channel must be in the available state. The frequency band where the current BCCH is located and the frequency band supported by the TCHF must have a mapping listed in Table 34-3. The current type of the channel used for SDCCH dynamic adjustment must be TCHF, but the channel can be set to TCHF or TCHH during data configuration. The number of SDCCHs on the TRX where the TCHF is located cannot exceed eight. If the channel type of a timeslot is SDCCH/8, the timeslot contains eight SDCCHs. The current cell must have more than one TRX.
Table 34-3 Mapping between the frequency band where the BCCH is located and the frequency band supported by the TCHF Frequency Band Where the BCCH Is Located P-GSM900M E-GSM900M R-GSM900M DCS1800M PCS1900M GSM850M GSM480M GSM450M Frequency Band Supported by the TCHF P-GSM900M P-GSM900M or E-GSM900M P-GSM900M, E-GSM900M, or RGSM900M DCS1800M PCS1900M GSM850M GSM480M GSM450M
The following table describes the selection of TCHFs to be adjusted for different types of cells. If... The cell is a common cell, Then... Dynamic adjustment can be performed if the previous requirements are met. Figure 34-4 shows the selection procedure.
Issue 02 (2008-06-30)
34-9
If... The cell is not a concentric cell (GSM900/ DCS1800 Co-BCCH cell),
Then... The BSC preferentially selects the idle TCHFs that meet the above requirements in the underlaid subcell. If such idle TCHFs are not found, the BSC selects the seized TCHFs. If the TCHFs that meet the requirements are not found in the underlaid subcell, the BSC selects the idle TCHFs that meet the requirements in the overlaid subcell. If such idle TCHFs are not found, the BSC selects the seized TCHFs. Figure 34-4 shows the selection procedure. The BSC preferentially selects the idle TCHFs that meet the above requirements in the underlaid subcell. If such idle TCHFs are not found, the BSC selects the seized TCHFs. Figure 34-4 shows the selection procedure.
NOTE The TCHFs in the overlaid subcell cannot be used for SDCCH dynamic adjustment.
The cell is a concentric cell (GSM900/ DCS1800 Co-BCCH cell),
34-10
Issue 02 (2008-06-30)
Figure 34-4 Procedure for selecting a TCHF when the TRX is selected
Start
Yes
Is the SDCCH dynamic adjustment decision implemented for the TCHF that meets the above requirements? No Are the TRX number and the TCHF number marked? Yes Are the SDCCHs on the current TRX fewer than the SDCCHs on the temporarily marked TRX? Mark the current TRX and a TCHF as the selected TRX and TCHF No
Yes
No No Does the SDCCHs on the current TRX equal the SDCCHs on the temporarily marked TRX? Yes No Is the marked TCHF seized? Yes Is the TCHF idle? No End and return the marked TRX number and TCHF number Yes
Converting the TCHF to the SDCCH

After selecting a TCHF, the BSC performs the SDCCH dynamic adjustment procedure. A busy TCHF can also be used for the adjustment. Therefore, the SDCCH dynamic adjustment procedure is of two types based on the status of the selected TCHF.
l
The TCHF is idle. 1. 2. 3. The BSC adds the SDCCH/8, deletes the TCHF, and adjusts the channel attributes. The BSC issues a command of adjusting channel attributes to the BTS and measures the related performance counters. The BSC performs different operations based on the implementation of the previous processing.
If the previous processing is successful, the BSC sets the cell dynamic adjustment tag and triggers the Timer of SDCCH Back TCH Justify Timer (s) and the Timer of TCH or SDCCH Dynamic Adjust Check Timer (s). The BSC sets the Timer of
Issue 02 (2008-06-30)
SDCCH Back TCH Justify Timer (s) to TCH Minimum Recovery Time (S). The SDCCH dynamic adjustment is successful. The BSC prepares for the switchback procedure.
If the previous processing fails, the BSC clears the record of cell dynamic adjustment and stops the adjustment.
4. 5.
After receiving the command, the BTS starts converting channels. After 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 SDCCH/8 to idle and cancels the cell dynamic adjustment tag. The dynamic adjustment is complete. The TCHF used for adjustment is seized by a call. To avoid the disruption of the call, the BSC initiates a forced intra-cell handover and triggers the Timer of Waiting CRDLC HO Responses(s) to reserve sufficient time for the intra-cell handover. The BSC sets the cell dynamic adjustment tag and sets the channel status to "TCHF converted to SDCCH, waiting for forced handover response" to prevent the TCHF from being assigned before adjustment. The BSC also triggers the Timer of TCH or SDCCH Dynamic Adjust Check Timer (s) to prevent the possibility that the channel cannot be recovered because of a cell fault. Different operations are performed based on whether a forced handover response is received.
The TCHF is busy. 1.
2.
3.
If a forced handover response is received, the BSC stops the Timer of Waiting CRDLC HO Responses(s) and determines whether the forced handover is successful.
If the forced handover fails, the BSC does not release the TCHF, but stops the Timer of TCH or SDCCH Dynamic Adjust Check Timer(s), cancels the cell dynamic adjustment tag, and stops the adjustment. If the forced handover is successful, the BSC sets the channel status to "Waiting for channel release". When the channel status is idle, the BSC follows the adjustment procedure for the idle TCHF to adjust the channel.
If the BSC does not receive a forced handover response and the Timer of Waiting CRDLC HO Responses (s) expires, the BSC stops the Timer of TCH or SDCCH Dynamic Adjust Check Timer (s), cancels the cell dynamic adjustment tag, and stops the adjustment.
NOTE
Timer of SDCCH Back TCH Justify Timer (s), Timer of TCH or SDCCH Dynamic Adjust Check Timer (s), Timer of Waiting CRDLC HO Responses (s), and the related channel status are internal parameters. They cannot be set by external users.
34.4.4 SDCCH Switchback Decision

This describes the SDCCH switchback decision. If the requirements for SDCCH switchback are met, the SDCCH is switched back to the original TCHF after the TCHF is converted to the SDCCH. After the TCHF is converted to the SDCCH, the SDCCH switchback can be performed if the following requirements are met:
l
The SDCCH must be converted from a TCHF.

34-12

l l
The SDCCH must have some idle sub-channels. Different types of cells must meet the following requirements:
If the cell is not a concentric cell, the SDCCH switchback can be performed when the above requirements are met. If the cell is a concentric cell, the BSC preferentially selects an SDCCH that meets the above requirements on the TRX that is in the overlaid subcell. If there is no appropriate SDCCH in the overlaid subcell, the BSC selects an appropriate SDCCH in the underlaid subcell.
After an SDCCH dynamic adjustment procedure is complete, the BSC triggers the Timer of SDCCH Back TCH Justify Timer(s) and sets the length of the timer to TCH Minimum Recovery Time. The timer controls the implementation of switchback. Figure 34-5 shows the procedure for the switchback decision.
Issue 02 (2008-06-30)
34-13
Figure 34-5 Procedure for the SDCCH switchback decision

Start
Timer of SDCCH Back TCH Justify Timer(s) expires Set the value of the switchback timer to TCH Minimum Recovery Time(s) Measure the number of idle SDCCHs that are dynamically adjusted in the current cell
No
Is the number of idle SDCCHs greater than "Idle SDCCH Threshold N1 + 8"?
Yes
12 is added to the value of the switchback timer automatically
3 is subtracted from the value of the switchback timer automatically
No
Is the value of the switchback timer greater than 0?
Yes
Set the value of the switchback timer to TCH Minimum Recovery Time(s)
Is there any SDCCH not switched back? Yes Can the SDCCH be switched back? Yes Perform the switchback
No
Stop Timer of Waiting CRDLC Channel Release(s)
No
Start Timer of Waiting CRDLC Channel Release(s)
End
34.4.5 SDCCH Switchback Procedure

This describes the SDCCH switchback procedure. If the requirements for SDCCH switchback are met, the BSC performs the SDCCH switchback procedure. The SDCCH switchback procedure should not exceed three seconds. A busy SDCCH can also be used for the switchback. Therefore, the SDCCH switchback procedure is of two types based on the status of the selected SDCCH.
l
If all the sub-channels of the selected SDCCH are idle, the SDCCH switchback procedure is as follows:
34-14
1. 2. 3. 4.
The BSC adds the TCHF, deletes the SDCCH, and adjusts the channel attributes. The BSC issues a command of adjusting channel attributes to the BTS and measures the related performance counters. After receiving the command, the BTS starts converting channels. After 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 and cancels the cell dynamic adjustment tag. The switchback is complete.
If some sub-channels of the selected SDCCH are busy, the SDCCH switchback procedure is as follows: 1. 2. 3. To avoid the disruption of calls on the selected SDCCH, the BSC triggers the Timer of Waiting CRDLC Channel Release (s) to wait 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 switchback. When the Timer of Waiting CRDLC Channel Release (s) expires, the BSC determines whether the sub-channels are being used. If some sub-channels are used, the BSC releases them forcibly. When all the sub-channels of the SDCCH are idle, the BSC follows the related procedure to switch back the SDCCH.
NOTE
4.
Generally, the seizure duration of the SDCCH is short. All the services stop before the Timer of Waiting CRDLC Channel Release (s) expires.
34.5 Implementation
This describes how to configure SDCCH dynamic adjustment. 34.5.1 Configuring SDCCH Dynamic Adjustment This describes how to configure SDCCH dynamic adjustment on the BSC6000 Local Maintenance Terminal.
34.5.1 Configuring SDCCH Dynamic Adjustment

This describes how to configure SDCCH dynamic adjustment on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page. Then, choose Configure Cell Attributes. Step 2 In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. Step 3 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 34-6. Select SDCCH Dynamic Allocation Allowed.
Step 4 Click Channel Management. A dialog box is displayed, as shown in Figure 34-7. Set the parameters related to SDCCH dynamic adjustment. The parameters are as follows:
l l l
Idle SDCCH Threshold N1 Cell SDCCH Channel Maximum TCH Minimum Recovery Time
34-16
Issue 02 (2008-06-30)
----End

This lists the counters related to SDCCH dynamic adjustment.
Alarms
None.
Counters
Table 34-4 lists the performance counters related to SDCCH dynamic adjustment. Table 34-4 Counters related to SDCCH dynamic adjustment. Counte r R3516A
Issue 02 (2008-06-30)
Description Number of Channel Conversions (TCH-SDCCH)

Counte r R3516B H3024A H3024B H3004A H3004B H3014A H3014B TH3034 A TH3034 B CH3034 A CH3034 B
Description Number of Channel Conversions (SDCCH-TCH) Failed Internal Intra-Cell Handovers (Dynamic Conversion, TCH-SDCCH) Failed Internal Intra-Cell Handovers (Dynamic Conversion, SDCCH-TCH) Internal Intra-Cell Handover Requests (Dynamic Conversion, TCHSDCCH) Internal Intra-Cell Handover Requests (Dynamic Conversion, SDCCHTCH) Internal Intra-Cell Handover Commands (Dynamic Conversion, TCHSDCCH) Internal Intra-Cell Handover Commands (Dynamic Conversion, SDCCHTCH) Success Rate of Internal Intra-Cell Handover (Dynamic Conversion, TCHSDCCH) Success Rate of Internal Intra-Cell Handover (Dynamic Conversion, SDCCH-TCH) Successful Internal Intra-Cell Handovers (Dynamic Conversion, TCHSDCCH) Successful Internal Intra-Cell Handovers (Dynamic Conversion, SDCCHTCH)
34.7 References
None.
34-18
Issue 02 (2008-06-30)
35 NACC
35
About This Chapter
NACC
35.1 Overview Network Assisted Cell Change (NACC) accelerates MS cell reselection and shortens the service disruption time during cell reselection. 35.2 Availability This lists the NEs, software, and licenses required for the implementation of NACC. 35.3 Technical Description This describes the application scenarios and the procedure of NACC. 35.4 Implementation This describes how to configure NACC. 35.5 Maintenance Information None. 35.6 References
Issue 02 (2008-06-30)
35-1
35 NACC
35.1 Overview
Network Assisted Cell Change (NACC) accelerates MS cell reselection and shortens the service disruption time during cell reselection.
Definition
NACC is short for Network Assisted Cell Change. In the NC0 and NC1 network control modes and the packet transfer mode, the MS requests the system information of the reselected neighbor cell from the network side when performing cell reselection. The network side notifies the MS of the requested neighbor cell system information through the Cell Change Notification (CCN) procedure.
NOTE
The CCN procedure is the NACC procedure.
Purposes
The purpose of NACC is to accelerate the cell reselection of the MS.
Terms
None.

Acronym and Abbreviation NACC NC0 NC1 NC2 CCN Full Spelling Network Assisted Cell Change Network Control Mode 0 Network Control Mode 1 Network Control Mode 2 Cell Change Notification
35.2 Availability
This lists the NEs, software, and licenses required for the implementation of NACC.
NEs Involved
Table 35-1 lists the NEs involved in NACC in external PCU mode.
35-2
Issue 02 (2008-06-30)
35 NACC
Table 35-1 NEs involved in NACC MS

NOTE
BTS -
BSC
PCU
MSC -
MGW -
SGSN -
GGSN -
HLR -
Table 35-2 lists the NEs involved in NACC in built-in PCU mode. Table 35-2 NEs involved in NACC MS
NOTE
BTS -
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 35-3 lists the versions of GBSS products that support NACC in external PCU mode. Table 35-3 GBSS products and software versions Product BSC PCU BSC6000 PCU Version V900R008C01 and later releases G3PCUV300R005C05 and later releases
Table 35-4 lists the versions of the software that supports NACC in built-in PCU mode. Table 35-4 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
NACC is available only when a license is obtained. NACC requires the support of the MS.
35 NACC

This describes the application scenarios and the procedure of NACC.
Application Scenarios
NACC application scenarios are based on cell reselection initiated by the MS. NACC only accelerates cell reselection initiated by the MS. The MS and BSC performs NACC when the following conditions are met:
l l l l
The Network Control Mode parameter is set to nc0 or nc1. In the cell configuration of the BSC, the Support NACC parameter is set to YES. The MS operates in CCN mode. The MS detects that the signal strength in the serving cell is poor and finds the neighbor cell with good signal strength.
NACC Procedure
The NACC procedures consist of starting NACC only, starting NACC and SI Status, and starting NACC and NC2.
l
Starting NACC only In the cell configuration, the Support NACC parameter is set to YES. In such a case, only the NACC procedure is started, as shown in Figure 35-1. Figure 35-1 Starting NACC
MS PACKET CELL CHANGE NOTIFICATION PACKET NEIGHBOUR CELL DATA PACKET CELL CHANGE CONTINUE
BSC
1.
When the MS in CCN mode determines to perform cell reselection, it does not perform a handover but sends the PACKET CELL CHANGE NOTIFICATION message to the BSC to request the system information of the target cell to be reselected. Upon receipt of the PACKET CELL CHANGE NOTIFICATION message, the BSC sends the PACKET NEIGHBOUR CELL DATA message to the MS. This message can be sent in one or more cases. The PACKET NEIGHBOUR CELL DATA message carries the SI1, SI3, and SI13 system information of the target cell. Then, the BSC
2.
35-4
35 NACC
sends the PACKET CELL CHANGE CONTINUE message to the MS to inform the MS to continue with cell reselection. 3. After receiving the PACKET NEIGHBOUR CELL DATA message from the BSC, the MS saves the system information carried by this message. After receiving the PACKET CELL CHANGE CONTINUE message, the MS returns to NC0/NC1 mode from CCN mode and continues with cell reselection. Based on the system information of the target cell, the MS is handed over to the reselected target cell. The system information of the target cell can speed up the cell reselection.
4.
Starting NACC and SI Status The NACC procedure is performed to transfer the system information of the neighbor cell to the MS, and the SI Status procedure is performed to transfer the system information of the serving cell to the MS. The combination of the NACC procedure and the SI Status procedure can speed up the cell reselection. In the cell configuration, the Support NACC and PACKET SI STATUS parameters are set to YES. In such a case, the NACC procedure and the SI Status procedure are started, as shown in Figure 35-2. Figure 35-2 Starting NACC and SI Status
MS PACKET CELL CHANGE NOTIFICATION PACKET NEIGHBOUR CELL DATA PACKET CELL CHANGE CONTINUE PACKET SI STATUS PACKET SERVING CELL DATA
BSC
1.
After the MS is handed over to a new cell, if the MS does not receive the system information of this cell, it sends the PACKET SI STATUS message to the BSC to request the system information of the serving cell. Upon receipt of the PACKET SI STATUS message, the BSC sends the PACKET SERVING CELL DATA message to the MS. This message can be sent in one or more cases. It carries the system information of the serving cell. After receiving the PACKET SERVING CELL DATA message from the BSC, the MS saves the system information carried by the message. The MS can speed up the access to the serving cell according to the system information of the serving cell.
2.
3.
Issue 02 (2008-06-30)
35 NACC
l
Starting NACC and NC2 When the Support NACC parameter is set to YES and the Network Control Mode parameter is set to NC2, the procedure is actually the NC2 procedure. Before sending the PACKET CELL CHANGE ORDER message to the MS, the BSC must send the PACKET NEIGHBOUR CELL DATA message to MS. The PACKET NEIGHBOUR CELL DATA message carries the system information of the neighbor cell.
35.4 Implementation
This describes how to configure NACC. 35.4.1 Configuring NACC This describes how to configure NACC on the BSC6000 Local Maintenance Terminal.
35.4.1 Configuring NACC

This describes how to configure NACC on the BSC6000 Local Maintenance Terminal.
Prerequisite
l l
The cell supports the GPRS services. The license is applied and activated. To apply for and activate the license, do as follows: 1. Apply for the license for the NACC. In the BSC6000V900R008 Exceptional Commercial License Application Template, specify a value in the corresponding cell of the Number of Cell supporting NC2 row in the Resource control items column. The value indicates the number of cells that support the NACC. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Procedure
35-6
Issue 02 (2008-06-30)
35 NACC
Figure 35-3 Set Cell Attributes dialog box (NACC)
Step 5 Click GPRS Attributes. The Set PS Cell GPRS Parameter dialog box is displayed. Then, set Network Control Mode to nc0 or nc1. Step 6 Click OK to return to the dialog box shown in Figure 35-3. Step 7 Select Support NACC.
NOTE
To configure the SI STATUS, select Support PACKET SI STATUS.
Step 8 Click OK to return to the Set Cell Attributes dialog box. Step 9 Click Finish to complete the configuration of the cell attributes. ----End
Issue 02 (2008-06-30)
35-7
35 NACC

None.
Alarms
None.
Counters
None.
35.6 References
3GPP TS 44.060 V6.12.0
35-8
Issue 02 (2008-06-30)
36 NC2
36
About This Chapter
36.2 Availability This lists the NEs, software, and license required for the implementation of NC2.
NC2
36.1 Overview This describes network controlled cell reselection, which is also referred to as network control mode 2 (NC2). In NC2 mode, the network requests measurement reports from the MS and controls the cell reselection.
36.3 Technical Description This describes three types of cell reselection modes in NC2: critical cell reselection, cell load reselection, and general cell reselection. 36.4 Implementation This describes how to configure NC2 and the PCU. 36.5 Maintenance Information This lists the alarms and counters related to NC2. 36.6 References
Issue 02 (2008-06-30)
36-1
36 NC2
36.1 Overview
This describes network controlled cell reselection, which is also referred to as network control mode 2 (NC2). In NC2 mode, the network requests measurement reports from the MS and controls the cell reselection.
Definition
If an MS is in NC2 and packet transfer mode, the network can send a Packet Cell Change Order message to notify the MS to initiate a cell reselection.
Purposes
In NC2 mode, the network orders the MS to reselect a new cell that has better transmission quality. Compared with the autonomous cell reselection of the MS, the network controlled cell reselection comprehensively considers the load conditions of each cell and automatically adjusts the loads of the cells.
Terms
None.

Acronyms and Abbreviations NC2 Full Spelling Network Control Mode 2
36.2 Availability
This lists the NEs, software, and license required for the implementation of NC2.
NEs Involved
Table 36-1 lists the NEs involved in NC2 in external PCU mode. Table 36-1 NEs involved in NC2 MS
NOTE
BTS -
BSC
PCU
MSC -
MGW -
SGSN -
GGSN -
HLR -
36-2
Issue 02 (2008-06-30)
36 NC2
Table 36-2 lists the NEs involved in NC2 in built-in PCU mode. Table 36-2 NEs involved in NC2 MS
NOTE
BTS -
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 36-3 lists the versions of the software that supports NC2 in external PCU mode. Table 36-3 GBSS products and software versions Product BSC PCU BSC6000 PCU Version V900R008C01 and later releases G3PCUV300R005C05 and later releases
Table 36-4 lists the versions of the software that supports NC2 in built-in PCU mode. Table 36-4 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
NC2 is available only when a license is obtained. NC2 requires the support of an MS. If an MS supports the NC2 mode, the MS sends a Packet Measurement Report message to trigger an NC2 procedure.

This describes three types of cell reselection modes in NC2: critical cell reselection, cell load reselection, and general cell reselection.
36 NC2
Critical Cell Reselection

Critical cell reselection is based on the transmission quality of cells. Based on the UL and DL receive quality on the Um interface, the PCU determines whether a critical cell reselection should be performed. Through bit error rates (BERs), the PCU determines the variation in the transmission quality. The increase in BERs indicates that signal levels decrease or channel interference increases. Then, the PCU orders the MS to reselect a neighbor cell that has stronger signal strength.
Cell Load Reselection

In the network, the loads of some cells are heavy, whereas the loads of other cells are light. To balance the loads of these cells, cell load reselection is performed. In a cell load reselection procedure, some MSs in heavy-load cells are reselected to light-load cells. In addition, the MSs in neighbor cells should not be reselected to heavy-load cells. Figure 36-1 shows the cell load reselection mode. Figure 36-1 Cell load reselection mode (1)
A cell with a heavy load A cell with a light load A cell with a heavy load A cell with a light load A cell with a light load A cell with a heavy load A cell with a light load
To determine the traffic load of a cell, compare the channel multiplexing rate with the predefined threshold:
l
If the channel multiplexing rate of a cell is higher than the start threshold of load cell reselection, you can infer that the traffic load of the cell is heavy and load cell reselection algorithms should be performed. If the channel multiplexing rate of a cell is lower than the receiving threshold of cell load reselection, you can infer that the traffic load of the cell is light. Therefore, some of the loads of heavy-load cells can be reselected to the cell.
In cell load reselection mode, an MS with overhigh signal levels cannot be reselected to a neighbor cell. Through the setting of the level threshold of cell load reselection, an MS whose signal level is lower than the level threshold of cell load reselection can be reselected to a neighbor cell. Figure 36-2 shows the cell load reselection mode.
36-4
Issue 02 (2008-06-30)
36 NC2
Figure 36-2 Cell load reselection mode (2)

Load reselection area Normal reselection border
Cell A
Cell B
Load reselection threshold
General Cell Reselection

General cell reselection is based on signal levels. If the transmission quality and traffic load of the serving cell do not trigger cell reselection, the MS is reselected to a neighbor cell that has stronger signal strength through the general cell reselection procedure.
36.4 Implementation
This describes how to configure NC2 and the PCU. 36.4.1 Configuring NC2 This describes how to configure NC2 on the BSC6000 Local Maintenance Terminal. 36.4.2 Configuring the External PCU This describes how to configure NC2 on the PCU Maintenance Terminal.
36.4.1 Configuring NC2

This describes how to configure NC2 on the BSC6000 Local Maintenance Terminal.
Prerequisite
The cell supports the GPRS services. The license of NC2 is applied and activated. To apply for and activate the license, do as follows: 1. Apply for the license for the NC2. In the BSC6000V900R008 Exceptional Commercial License Application Template, specify a value in the corresponding cell of the Number of Cell supporting NC2 row in the Resource control items column. The value indicates the number of cells that support the NC2. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Context
The configuration schemes for NC2 are as follows:
l
Only NC2 needs to be configured in built-in PCU mode.

Issue 02 (2008-06-30)
36 NC2
l
NC2 and 36.4.2 Configuring the External PCU need to be configured in external PCU mode.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the target cell, and then choose Configure Cell Attributes on the shortcut menu. The Select Cell dialog box is displayed. Step 2 Double-click the target cell in the Cell view list box to add the cell to the Selected cells list box. Step 3 Click Next. The Configuring Cells Attributes dialog box is displayed. Step 4 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 36-3. Figure 36-3 Set Cell Attributes dialog box (NC2)
36-6
Issue 02 (2008-06-30)
36 NC2
Step 5 Click GPRS Attributes. The Set PS Cell GPRS Parameter dialog box is displayed. Then, set Network Control Mode to nc2. Step 6 Click OK to return to the dialog box shown in Figure 36-3. Step 7 Select Support NC2. Step 8 Click OK to return to the Set Cell Attributes dialog box. Step 9 Click Finish to complete the configuration of the cell attributes. ----End
36.4.2 Configuring the External PCU

This describes how to configure NC2 on the PCU Maintenance Terminal.
Procedure
l Configure NC2 on the PCU Maintenance Terminal in static data configuration mode. 1. 2. Log in to the PCU Maintenance Terminal through Telnet. On the PCU Maintenance Terminal, run the command pcu add relatedinfo LCNo NCO BSIC SpgcCCCHSup PriAccThr RAColor to add the parameters related to System Information of logical cells, as shown in Figure 36-4.
Figure 36-4 Parameters related to System Information of logical cells
Table 36-5 describes the parameters related to System Information of logical cells.
Issue 02 (2008-06-30)
36-7
36 NC2
Table 36-5 Description of the parameters related to System Information of logical cells Parameter LCNo NCO Description The number of a logical cell. Value range: 065534 Network control mode. Value range: NC0, NC1, and NC2
l l
NC0: An MS performs autonomous cell reselection. NC1: An MS sends measurement reports to the network and performs autonomous cell reselection. NC2: An MS sends measurement reports to the network and cannot perform autonomous cell reselection.
BSIC
Base station identity code. When configuring BSIC, you should refer to the configuration information of the BSIC on the BSC side. Value range: 063 Whether the SPLIT_PG_CYCLE parameter is transmitted on the CCCH of the cell. Value range: yes and no Packet access priority level. PriAccThr specifies the priority level of the MS to access the cell. Value range: 0, 36
l l l l l
SpgcCCCHSup PriAccThr
0: MSs are not allowed to perform packet services. 3: MSs with priority level 1 can perform packet services. 4: MSs with priority levels 12 can perform packet services. 5: MSs with priority levels 13 can perform packet services. 6: MSs with priority levels 14 can perform packet services.
RAColor
RAColor defines the routing area color code of a GPRS cell. Value range: 07
3.
Run the write command to save the setting. Then type Y to end the configuration, as shown in Figure 36-5.
36-8
Issue 02 (2008-06-30)
36 NC2
Figure 36-5 Configuration successful
Configure NC2 on the PCU Maintenance Terminal in dynamic data configuration mode. 1. 2. Log in to the PCU Maintenance Terminal through Telnet. On the PCU Maintenance Terminal, run the command pcu cell dynsetLCNo to enter the cell dynamic configuration window, as shown in Figure 36-6.
Figure 36-6 Cell dynamic configuration window
3.
Set NCO to NC2, as shown in Figure 36-7.
Issue 02 (2008-06-30)
36-9
36 NC2
Figure 36-7 Setting NC2 mode (2)
4.
Type e to activate the configuration. If you need to configure other attributes, type Y. If you do not need to configure other attributes, type N, as shown in Figure 36-8.
Figure 36-8 Setting NC2 mode (2)
5.
Run the write command to save the setting. Then type Y to end the configuration, as shown in Figure 36-9.
36-10
Issue 02 (2008-06-30)
36 NC2
Figure 36-9 Setting NC2 mode result window
----End

This lists the alarms and counters related to NC2.
Alarms
None.
Counters
Table 36-6 Counters related to NC2 Counter Number of Cell Reselections Controlled by the Network Number of Critical Cell Reselections Controlled by the Network Number of Cell Load Reselections Controlled by the Network Number of General Cell Reselections Controlled by the Network
Issue 02 (2008-06-30)
Description The counter Number of Cell Reselections Controlled by the Network is a cell-level performance counter. The counter Number of Critical Cell Reselections Controlled by the Network is a cell-level performance counter. The counter Number of Cell Load Reselections Controlled by the Network is a cell-level performance counter. The counter Number of General Cell Reselections Controlled by the Network is a cell-level performance counter.
36-11
36 NC2
Counter Number of Failed Cell Reselections Controlled by the Network
Description The counter Number of Failed Cell Reselections Controlled by the Network is a cell-level performance counter.
36.6 References
3GPP TS 44.060 V6.12.0
36-12
Issue 02 (2008-06-30)
37 Streaming QoS
37
About This Chapter
Streaming QoS
37.1 Overview This describes the transmission requirements for streaming services, such as the guaranteed bit rate, maximum bit rate, and transmission delay. 37.2 Availability This lists the NEs, software, and license required for the implementation of Streaming QoS. 37.3 Impact This describes the impact of streaming QoS on system performance. 37.4 Technical Description This describes the technical aspects of steaming QoS. The PCU acquires the GBR of an MS through the PFC procedure, and then calculates the data blocks transmitted on the Um interface in a unit time based on the active codec scheme. 37.5 Implementation This describes how to configure and verify Streaming QoS. 37.6 Maintenance Information None. 37.7 References
Issue 02 (2008-06-30)
37-1
37 Streaming QoS
37.1 Overview
This describes the transmission requirements for streaming services, such as the guaranteed bit rate, maximum bit rate, and transmission delay.
Definition
Streaming services comprise audio and video services. The streaming QoS defines the transmission requirements for streaming services.
Purposes
The guaranteed bit rate (GBR) specified in QoS is used to guarantee a sufficient and stable bandwidth for the streaming services in progress. An MS that supports GBR can preempt the bandwidth of another MS that does not support GBR. If both MSs support GBR, the Um resources that are insufficient are allocated to the MS that accesses the network earlier.
Terms
None.

Acronyms and Abbreviations QoS GBR PFC PSI SI PFI ABQP PFT BSS PFM SGSN PDP Full Spelling Quality of Service Guaranteed Bit Rate Packet Flow Context Packet System Information System Information Packet Flow Identifier Aggregate BSS QoS Profile Packet Packet Flow Timer Base Station Subsystem Packet Flow Management Service GPRS Support Node Packet Data Protocol
37-2
Issue 02 (2008-06-30)
37 Streaming QoS
37.2 Availability
This lists the NEs, software, and license required for the implementation of Streaming QoS.
NEs Involved
Table 37-1 lists the NEs involved in Streaming QoS in external PCU mode. Table 37-1 NEs involved in streaming QoS MS
NOTE
BTS -
BSC -
MSC -
PCU
MGW -
SGSN
GGSN -
HLR
Table 37-2 lists the NEs involved in Streaming QoS in built-in PCU mode. Table 37-2 NEs involved in streaming QoS MS
NOTE
BTS -
BSC
MSC -
MGW -
SGSN
GGSN -
HLR
Software Releases
Table 37-3 lists the versions of GBSS products that support Streaming QoS in external PCU mode. Table 37-3 GBSS products and software versions Product PCU PCU6000 Version All releases
Table 37-4 lists the versions of GBSS products that support Streaming QoS in built-in PCU mode.
37 Streaming QoS
Table 37-4 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
The Streaming QoS must be activated with a license. The availability of streaming QoS also requires the support of the MS and the subscription of the users. The PFC Feature Mode field in the GPRS Cell Options IE of system information PSI13/SI13 specifies whether the networks support the PFC. If the uplink data block sent on the Um interface by an MS contains the PFI that is greater than or equal to 8 bits, the MS supports steaming QoS.
37.3 Impact
This describes the impact of streaming QoS on system performance.

l
An MS that supports the streaming QoS feature has a higher priority over the MS that does not support the streaming QoS feature. Thus, the MS supports the streaming QoS feature may preempt a much wider bandwidth than the MS that does not support the streaming QoS feature. When the radio resources are insufficient, the MS that accesses the network earlier is allocated a wider bandwidth than the MS accessing the network later.

None.

This describes the technical aspects of steaming QoS. The PCU acquires the GBR of an MS through the PFC procedure, and then calculates the data blocks transmitted on the Um interface in a unit time based on the active codec scheme. 37.4.1 Establishment of PFC This describes the procedure for establishing the PFC. The establishment procedure specifies a PFC for an MS and provides the parameters required for the uplink and downlink data transmission. The PFC establishment can be initiated by the BSS or by the SGSN. 37.4.2 Modification of PFC This describes the procedure for modifying the PFC. This procedure, which can be initiated by the BSS or by the SGSN, modifies the PFC of an MS in the BSS. 37.4.3 Deletion of PFC
37 Streaming QoS
This describes the procedure for deleting the PFC. This procedure, which can be initiated by the BSS or by the SGSN, deletes the PFC of the MS in the BSS. 37.4.4 GBR-Supported Uplink TBF Establishment Procedure This describes the GBR-supported procedure for establishing the uplink TBF. 37.4.5 GBR-Supported Downlink TBF Establishment Procedure This describes the GBR-supported procedure for establishing the downlink TBF. 37.4.6 Resources Reallocation Due to Changes of Uplink and Downlink Codec Modes This describes the principles for reallocating the resources on the Um interface when there is change in the uplink and downlink codec modes. 37.4.7 Resources Reallocation Due to Changes of PFC The SGSN initiates a PFC modification procedure and modifies the Packet Flow Context (PFC) of the Temporary Block Flow (TBF) in use. After the modification procedure is complete, the BSS reallocates resources based on the new PFC and modifies the flow control of the MS.
37.4.1 Establishment of PFC

This describes the procedure for establishing the PFC. The establishment procedure specifies a PFC for an MS and provides the parameters required for the uplink and downlink data transmission. The PFC establishment can be initiated by the BSS or by the SGSN.
PFC Establishment Procedure Initiated by the BSS

1. On receiving the Downlink Unitdata message on the Gb interface and the Uplink RLC data block message, EGPRS Uplink RLC data block message, Packet Resource Request message, and Packet Downlink Ack/Nack message, which includes the information element Channel Request Description on the Um interface, the BSS checks whether the PFC that corresponds to the PFI field carried by the MS exists. If the PFC does not exist, the BSS sends a Download_BSS_PFC PDU message to the SGSN and starts timer T6 to trigger the retransmission mechanism. If the BSS fails to receive a Create_BSS_PFC PDU message after the retransmission mechanism terminates, the PFC establishment procedure is complete. On receiving the Download_BSS_PFC PDU message from the BSS, the SGSN responds with a Create_BSS_PFC PDU message. If the Download_BSS_PFC PDU message contains unknown PFI, the SGSN does not send the Create_BSS_PFC PDU message. The corresponding ABQP and PFT are provided. On receiving the Create_BSS_PFC PDU message, the BSS stops T6 and negotiates between the Packet Flow Management (PFM) and QoS about the ABQP. After the negotiation, the BSS establishes the PFC corresponding to the PFI. If the establishment succeeds, the BSS sends a Create_BSS_PFC_ACK message to the SGSN. If the establishment fails, the BSS sends a Create_BSS_PFC_Nack message to the SGSN.
2.
3.
Figure 37-1 shows the PFC establishment procedure initiated by the BSS.
Issue 02 (2008-06-30)
37-5
37 Streaming QoS
Figure 37-1 PFC establishment procedure initiated by the BSS

MS Downlink/Uplink Unitdata Download_BSS_PFC Create_BSS_PFC Create_BSS_PFC_Ack/Nack BSS SGSN
PFC Establishment Procedure Initiated by the SGSN

After the MS finishes the Packet Data Protocol (PDP) context activation, the SGSN sends a Create_BSS_PFC PDU message to the BSS. The following steps are the same as those listed in the PFC Establishment Procedure Initiated by the BSS. Figure 37-2 shows the PFC establishment procedure initiated by the SGSN. Figure 37-2 PFC establishment procedure initiated by the SGSN
MS Downlink/Uplink Unitdata Modify_BSS_PFC Modify_BSS_PFC_Ack BSS SGSN
37.4.2 Modification of PFC

This describes the procedure for modifying the PFC. This procedure, which can be initiated by the BSS or by the SGSN, modifies the PFC of an MS in the BSS.
PFC Modification Procedure Initiated by the BSS

1. Upon receipt of the PFC modification indication from the PCU, the BSS sends a Modify_BSS_PFC PDU message to the SGSN and starts timer T8 to trigger the retransmission mechanism. If the BSS fails to receive a Modify_BSS_PFC_Ack message after the retransmission mechanism is terminated, the PFC modification procedure is complete. When the SGSN receives the Modify_BSS_PFC PDU message:
l l
2.
If the new PFC is accepted, the SGSN responds with a Modify_BSS_PFC_Ack message, which contains the original ABQP. The modification of the PFC succeeds. If the new PFC is not accepted, the SGSN responds with a Modify_BSS_PFC_Ack message, which does not contain the original ABQP. The modification of the PFC fails.
3.
Upon receipt of the Modify_BSS_PFC_Ack message, the BSS stops timer T8 and compares the ABQP from the QoS with the ABQP from the SGSN.
37-6

l l
37 Streaming QoS
If the two ABQPs are the same, the current PFC is modified. If the two ABQPs are different, the modification of the PFC fails, and the original PFC is retained.
Figure 37-3 shows the PFC modification procedure initiated by the BSS. Figure 37-3 PFC modification procedure initiated by the BSS
MS BSS PDP Context Activation Create _BSS_PFC Create_BSS_PFC_Ack/Nack SGSN
PFC Modification Procedure Initiated by the SGSN

The SGSN sends the BSS a Create_BSS_PFC PDU message, in which the PFI corresponds to the PFC in the BSS. For the detailed procedure, refer to 37.4.1 Establishment of PFC.
37.4.3 Deletion of PFC

This describes the procedure for deleting the PFC. This procedure, which can be initiated by the BSS or by the SGSN, deletes the PFC of the MS in the BSS.
PFC Deletion Procedure Initiated by the BSS

The BSS deletes specified or all PFCs without notifying the SGSN.
PFC Deletion Procedure Initiated by the SGSN

Upon receipt of the Delete_BSS_PFC message, the BSS, based on the PFI present in the message, deletes the corresponding PFC saved in the BSS, and then sends a Delete_BSS_PFC_Ack message to the SGSN. Figure 37-4 shows the PFC deletion procedure initiated by the SGSN. Figure 37-4 PFC deletion procedure initiated by the SGSN
BSS Delete_BSS_PFC Delete_BSS_PFC_Ack SGSN
37.4.4 GBR-Supported Uplink TBF Establishment Procedure

This describes the GBR-supported procedure for establishing the uplink TBF. When establishing the uplink TBF:
37 Streaming QoS
l
If the uplink TBF establishment uses two phase access, the BSS searches for the PFC based on the PFI specified in the Packet Resource Request message.
If the PFC is not established, the BSS should negotiate with the SGSN to establish the PFC, and then allocate resources based on Best Effort. If the PFC is established, the BSS allocates resources based on the GBR specified in the PFC.
If the uplink TBF establishment uses one phase access, the BSS allocates resources based on Best Effort. After the PFC is established, BSS reallocates the resources.
NOTE
When the PFC establishment procedure between the PCU and SGSN is complete, the BSS reallocates resources based on the GBR specified in the PFC.
37.4.5 GBR-Supported Downlink TBF Establishment Procedure

This describes the GBR-supported procedure for establishing the downlink TBF. When establishing the downlink TBF, the BSS searches for the PFC in the PCU based on the PFI attached in the LLC PDU.
l
If the PFC is not established, the BSS should negotiate with the SGSN to establish the PFC, and then allocates resources based on Best Effort. If the PFC is established, the BSS allocates resources based on the GBR specified in the PFC.
NOTE
When the PFC establishment procedure between the PCU and SGSN is complete, the BSS reallocates resources based on the GBR specified in the PFC.
37.4.6 Resources Reallocation Due to Changes of Uplink and Downlink Codec Modes
This describes the principles for reallocating the resources on the Um interface when there is change in the uplink and downlink codec modes. The resources reallocation caused by changes of UL/DL codec modes does not change the allocated channel group. Instead, the block budgeting is performed only on the allocated channel group.
l l
The handling is complete if the remaining block budgeting matches the original GBR. If the remaining block budgeting does not match the original GBR, all the remaining resources are allocated to the MS, and the PFC modification procedure is initiated. The GBR is modified based on the allocated resources, and the SGSN is notified of the GBR modification.
37.4.7 Resources Reallocation Due to Changes of PFC

The SGSN initiates a PFC modification procedure and modifies the Packet Flow Context (PFC) of the Temporary Block Flow (TBF) in use. After the modification procedure is complete, the BSS reallocates resources based on the new PFC and modifies the flow control of the MS.
37-8
Issue 02 (2008-06-30)
37 Streaming QoS
37.5 Implementation
This describes how to configure and verify Streaming QoS. 37.5.1 Configuring Streaming QoS This describes how to configure streaming QoS. 37.5.2 Verifying Streaming QoS This describes how to verify streaming QoS.
37.5.1 Configuring Streaming QoS

This describes how to configure streaming QoS.
Prerequisite
In built-in PCU mode, activate the license through the Local Maintenance Terminal. For the detailed operations, refer to Activating the BSC License. In external PCU mode, the license should be written through the PCU maintenance console. 1. Write the license in a newly deployed and an expanded office.
l
To write a license in a newly deployed office, do as follows: (1) Enter the public key. For details, refer to the command pcu limit updatekey. (2) Enter the SSN. For details, refer to the command pcu limit putssn. (3) Switch the active and standby boards and repeat steps 1.1 and 1.2. (4) Reset the system.
To write a license in an expanded office, do as follows: (1) Back up the SSN by referring to the following instructions.
NOTE
Retrieve and save the original SSN for problem locating when the expansion procedure fails.
(2) Enter the SSN by referring to the command pcu limit putssn. (3) Reset the system. 2. Write the public key file.
NOTE
Command: pcu limit updatekey <HostIP>< FileName> In the command, <HostIP> is the IP address of the <TFTP Server>, which is reserved at present. You can update the public key only by uploading the public key file from the hard disk. By default, the <HostIP> is set to 0.0.0.0. <FileName is the path containing the file name. Enter /hda0/filename if you upload the public key from partition 0 of the hard disk.
Upload the public key file to the hard disk of the active POMU board. (1) Enter the command ftp enable. (2) Enter the command ftp adduser to add an FTP user. (3) Upload the public key file to the hard disk of the POMU board through the FTP utility.
37 Streaming QoS
(4) Enter the public key by running the command pcu limit updatekey 0.0.0.0 /hda0/ ssn/pcu.pk. Assume /hda0/ssn/pcu.pk is the path in which the public key file is saved. (5) Delete the public key file in the hard disk of the POMU board after the operation succeeds. 3. Write the SSN file.
NOTE
Command: pcu limit putssn <HostIP> <FileName> Where, <HostIP> is the IP address of the TFTP Server, which is reserved at present. You can update the public key only by uploading the public key file from the hard disk now. The <HostIP> is set to 0.0.0.0 by default.< FileName is the path containing the file name. Enter /hda0/filename if you upload the public key from partition 0 of the hard disk.
Enter SSN from the hard disk of the active POMU board. (1) Enter the command ftp enable. (2) Enter the command ftp adduser to add an FTP user. (3) Upload the SSN file to the hard disk of the POMU board through the FTP utility. (4) Enter SSN by running the command pcu limit putssn 0.0.0.0 /hda0/ssn/1.ssn. Assume /hda0/ssn/1.ssn is the path in which the SSN file is saved. (5) If the operation fails, locate the problem based on the returned message. If the Key Error message is displayed, enter the public key file by referring to preceding operations. (6) If the operation succeeds, reset the system for the changes to take effect. (7) Delete the SSN file from the hard disk of the POMU board after the operation is complete. 4. Obtain the SSN file:
NOTE
Command: pcu limit backupssn <HostIP> <FileName> Where, <HostIP> is the IP address of the TFTP Server, which is reserved at present. You can update the public key only by uploading the public key file from the hard disk now. The <HostIP> is set to 0.0.0.0 by default.< FileName is the path containing the file name. Enter /hda0/filename if you upload the public key from partition 0 of the hard disk.
Back up the SSN file in the hard disk of the active POMU board. (1) Enter the command ftp enable. (2) Enter the command ftp adduser to add an FTP user. (3) Back up the SSN by running the command pcu limit backupssn 0.0.0.0 /hda0/ssn/ filename.ssn. Assume /hda0/ssn/filename.ssn is the path in which the SSN file is stored. (4) Download the SSN file to the target computer through the FTP utility. (5) Delete the SSN file from the hard disk of the corresponding POMU board after the operation is complete.
37-10
Issue 02 (2008-06-30)
37 Streaming QoS
Context
CAUTION
l
Write the public key in both the active and the standby POMU boards. A license alarm is generated if the license is not written in the active and standby boards simultaneously. In addition, the services may not be restored after the boards are switched. The writing of the SSN in the standby POMU board is optional as the active POMU board automatically synchronizes the SSN in the standby POMU board. The prerequisite is that a public key is correctly written in the standby POMU board and the active POMU board. After the writing of public key is complete, delete the files uploaded to the hard disk of the POMU board. The prerequisite for entering the license commands is that the POMU board is started. Use the telnet to connect to the POMU board for operation and maintenance. Perform the preceding operations in Huawei Engineer mode to ensure information security. Enter the public key if the public key has not been written. To avoid data collision, use one terminal to perform license-related operations of a POMU board, such as the commands putssn, backupssn, and updatekey (the commands showesn and showssn are not affected). Delete the corresponding files from the hard disk of the POMU board after the operations are complete.
l l l
Procedure
Step 1 Enable the PFC function on the SGSN side. On the SGSN side, enter the command set softpara. Select BYTE as the parameter type, 13 as the parameter index, and 32 as the parameter value. Step 2 Register the MS with the HLR. Run the command mod GPRS to modify the following fields:
l l l
Set Traffic Class to Streaming. Set uplink GBR to Expected Value. Set downlink GBR to an Expected Value.
----End
37.5.2 Verifying Streaming QoS

This describes how to verify streaming QoS.
Procedure
Step 1 Test the streaming services of the MS that supports streaming QoS and check whether there is a PFC establishment procedure during the PDP activation process.
37 Streaming QoS
Step 2 Verify that the access requests of other MSs or the downlink services do not affect the streaming QoS. ----End

None.
Alarms
None.
Counters
None.
37.7 References
l
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 23.107: "Quality of Service (QoS) concept and architecture".
37-12
Issue 02 (2008-06-30)
38 Packet Performance Improvement
38
Packet Performance Improvement
About This Chapter

38.1 Overview This describes three sub-functions of the packet performance improvement, namely, extended uplink TBF, EGPRS access of 11-bit messages, and takeover of the packet immediate assignment by the BTS. 38.2 Availability This lists the NEs and software required for the implementation of the packet performance improvement, as well as the MS capabilities. 38.3 Technical Description This describes the sub-functions of the packet performance improvement, namely, extended uplink TBF, EGPRS access of 11-bit messages, and takeover of the packet immediate assignment by the BTS. 38.4 Capabilities This describes the influences of the three sub-functions of the packet performance improvement on the system performance. 38.5 Implementation This describes how to configure and verify packet performance improvement. 38.6 Maintenance Information This lists the counters related to packet performance improvement. 38.7 References
Issue 02 (2008-06-30)
38-1
38.1 Overview
This describes three sub-functions of the packet performance improvement, namely, extended uplink TBF, EGPRS access of 11-bit messages, and takeover of the packet immediate assignment by the BTS.
Definition
The definitions for the sub-functions of the packet performance improvement are as follows:
l
Extended Uplink TBF
Normal uplink TBF The MS determines the release of the TBF. The MS indicates the end of the TBF by sending the RLC/MAC data block with CV = 0. On receiving all the data blocks, the network sends the Packet Uplink Ack/Nack message with FAI = 1 to release the TBF.
NOTE
The CV field attached to the message from the MS specifies the remaining data blocks sent on the uplink TBF. For example, the CV of the second-to-last data block is 1 and the CV of the last data block is 0. When the network receives all the uplink data blocks, the FAI bit is set to 1. Otherwise, the FAI bit is 0.
Extended Uplink TBF On receiving all the uplink data blocks, the network sends a control block with FAI = 0, sets the uplink TBF to be in inactive period, and starts an inactive period timer. Before the inactive period timer expires, the network continues allocating uplink resources for the MS. The uplink resources allow the MS to transfer control blocks. The network sets the TBF to be in active period again upon the reception of uplink data blocks during the inactive period of the TBF. When the inactive period timer expires, the network sends the control block with FAI = 1 and releases the uplink TBF.
EGPRS Access of 11-Bit Messages on the CCCH The MS sends the 11-bit EGPRS Packet Channel Request message on the CCCH for one phase packet access. The network assigns the EDGE channel for the MS through the Immediate Assignment message. Therefore, the EGPRS TBF is established.
Takeover of the Packet Immediate Assignment by the BTS The packet immediate assignment is taken over from the PCU to the BTS. The BTS processes the packet channel request, performs the uplink immediate assignment, and therefore establishes the uplink TBF. The PCU allocates the uplink TBF resources in advance and sends an additional immediate assignment message to the BTS. When the MS initiates a packet channel request, the BTS assigns the pre-allocated resources to the MS and establishes the uplink TBF. The packet performance improvement enables the immediate assignment message to be sent at an earlier time. Thus, the MS can access the network at a faster speed.
Purposes
l
Extended Uplink TBF

38-2
The MS enters the inactive period when there is no data transmission and automatically switches to the active period upon any data transmission. The procedures for reapplication and resource assignment are not required and therefore the transmission delay is minimized.
l
EGPRS Access of 11-Bit Messages on the CCCH The EGPRS one phase access is enabled and the access delay is minimized. Thus, the EDGE MS access performance is improved.
Takeover of the Packet Immediate Assignment by the BTS The packet immediate assignment is taken over from the PCU to the BTS. Thus, the MS access performance is improved and the access delay is minimized.
Terms
None.

Acronyms and Abbreviations CV FAI TBF Full Spelling Countdown Value Final Acknowledge Indication Temporary Block Flow
38.2 Availability
This lists the NEs and software required for the implementation of the packet performance improvement, as well as the MS capabilities.
NEs Involved
Table 38-1 lists the NEs involved in the packet performance improvement. Table 38-1 NEs involved in the packet performance improvement MS
NOTE
BTS
BSC
PCU
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 38-2 lists the versions of GBSS products that support the extended uplink TBF.
Table 38-2 GBSS products and software versions Product PCU PCU Version V300R005C05 and later releases
Table 38-3 lists the versions of GBSS products that support the EGPRS access of 11-bit messages on the CCCH. Table 38-3 GBSS products and software versions Product PCU BTS PCU BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM Version V300R006C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Table 38-4 lists the versions of GBSS products that support the takeover of the packet immediate assignment by the BTS. Table 38-4 GBSS products and software versions Product BSC PCU BTS BSC6000 PCU BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C Version V900R008C01 and later releases V300R006C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases
38-4
Issue 02 (2008-06-30)
Product BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM
Version BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
l
Extended Uplink TBF The MS must support the GERAN Feature Package 1. EGPRS Access of 11-Bit Messages on the CCCH The MS must support the EGPRS.

This describes the sub-functions of the packet performance improvement, namely, extended uplink TBF, EGPRS access of 11-bit messages, and takeover of the packet immediate assignment by the BTS. 38.3.1 EGPRS Access of 11-Bit Messages on the CCCH This describes the procedure for the EGPRS access of 11-bit messages on the CCCH. 38.3.2 Extended Uplink TBF This describes the transmission procedure for the extended uplink TBF. 38.3.3 Takeover of the Packet Immediate Assignment by the BTS This describes the procedure for the takeover of the packet immediate assignment by the BTS.
38.3.1 EGPRS Access of 11-Bit Messages on the CCCH

This describes the procedure for the EGPRS access of 11-bit messages on the CCCH. Figure 38-1 shows the procedure for the EGPRS access of 11-bit messages on the CCCH. Figure 38-1 Procedure for EGPRS access of 11-bit messages on the CCCH
MS Channel Request Immediate Assignment PCU
The procedure for the EGPRS access of 11-bit messages on the CCCH is the same as that for the one-phase access of 8-bit messages on the CCCH. The access rate of the EGPRS access of 11-bit messages on the CCCH is equivalent to that of the one-phase access of 8-bit messages on
the CCCH. Compared with the EDGE two-phase access, the EGPRS access of 11-bit messages on the CCCH is faster by 300 ms.
38.3.2 Extended Uplink TBF

This describes the transmission procedure for the extended uplink TBF. The transmission procedure for the extended uplink TBF consists of two phases:
l l
Active period Inactive period

NOTE
Normal uplink TBF has only the active period.
When there is no data transmission on the MS (the data block with CV = 0 is sent), the extended uplink TBF does not stop immediately. The extended uplink TBF enters the inactive period when the network sends the Packet Uplink Ack/Nack message with FAI = 0. During the inactive period, the MS does not transfer any new data blocks. When the inactive period timer on the network side expires, the network initiates the release procedure. The duration of the inactive period timer can be regulated. Figure 38-2 shows the procedure for the extended uplink TBF.
38-6
Issue 02 (2008-06-30)
Figure 38-2 Procedure for the extended uplink TBF

MS Normal Uplink TBF Packet Uplink Data Block (CV=1) Packet Uplink Data Block (CV=0) Packet Uplink Ack/Nack (FAI=1) Packet Control Ack PCU
Extended Uplink TBF Packet Uplink Data Block (CV=1) Packet Uplink Data Block (CV=0) Packet Uplink Ack/Nack (FAI=0) Packet Uplink Dummy Block Packet Uplink Dummy Block Packet Uplink Data Block (CV=1) Packet Uplink Data Block (CV=0) Packet Uplink Ack/Nack (FAI=0) Packet Uplink Dummy Block Packet Uplink Dummy Block Packet Uplink Ack/Nack (FAI=1) Packet Control Ack Inactive period timer expire Start inactive period timer Stop inactive period timer Start inactive period timer
38.3.3 Takeover of the Packet Immediate Assignment by the BTS

This describes the procedure for the takeover of the packet immediate assignment by the BTS.
l
Pre-allocating resources The PCU allocates the uplink resources in advance, and sends an additional immediate assignment message to the BTS.
Processing channel request The MS sends the Channel Request message to the BTS. The BTS responds with the Immediate Assignment message and schedules the uplink data blocks through the preemption mechanism.
Issue 02 (2008-06-30)
38-7
Figure 38-3 Procedure for the takeover of the packet immediate assignment by the BTS
MS Channel Request Immediate Assignment BTS PCU Pre-allocate Uplink TBF Resource
Channel Request (additional) Immediate Assignment (additional)
Uplink Data Block Uplink Data Block
38.4 Capabilities
This describes the influences of the three sub-functions of the packet performance improvement on the system performance.
l
Extended Uplink TBF Run the Ping command on the server. The Ping delay is reduced by 300 ms. EGPRS Access of 11-Bit Messages on the CCCH The access delay for the EGPRS capable MS is reduced by 300 ms. Takeover of the Packet Immediate Assignment by the BTS The access delay for the MS is reduced by 100 ms.
38.5 Implementation
This describes how to configure and verify packet performance improvement. 38.5.1 Configuring Packet Performance Improvement This describes how to configure packet performance improvement through the maintenance terminal on the PCU side. 38.5.2 Verifying Packet Performance Improvement This describes how to test the service performance by using an MS, with the three sub-functions of packet performance improvement enabled and disabled.
38.5.1 Configuring Packet Performance Improvement

This describes how to configure packet performance improvement through the maintenance terminal on the PCU side.
Procedure
Step 1 Configuring the extended uplink TBF
l
In external PCU mode, run the command PCU add privateoptpara through the maintenance terminal on the PCU side to configure the duration of the inactive period timer.
To configure the duration of the inactive period timer to 2000 ms, run the following command:
38-8
pcu add privateoptpara<LCNo><PSPrecedence><UpTbfRelDelay>2000<DnTbfRelDelay>
To disable the extended uplink TBF when the UpExtTbfInActDelay parameter is set to 0, run the following command: pcu add privateoptpara<LCNo><PSPrecedence><UpTbfRelDelay>0<DnTbfRelDelay>
In built-in PCU mode, run the command SET PRIVATEOPTPARA on the Local Maintenance Terminal to configure the duration of the inactive period timer.
Step 2 Configuring the EGPRS access of 11-bit messages on the CCCH

l
In external PCU mode, run the command PCU set egprspara through the maintenance terminal on the PCU side to configure the EGPRS access of 11-bit messages on the CCCH for the cell.
To enable the EGPRS access of 11-bit messages on the CCCH for the cell, run the following command: pcu set egprspara <LCNo><LQCMode><BepPeriod>yes<UpFixMcs><UpDefaultMcs><DnFixMcs> <DnDefaultMcs>
To disable the EGPRS access of 11-bit messages on the CCCH for the cell, run the following command: pcu set egprspara <LCNo><LQCMode><BepPeriod>no<UpFixMcs><UpDefaultMcs><DnFixMcs> <DnDefaultMcs>
In built-in PCU mode, run the command SET PSBASE on the Local Maintenance Terminal to configure the duration of the inactive period timer.
----End
38.5.2 Verifying Packet Performance Improvement

This describes how to test the service performance by using an MS, with the three sub-functions of packet performance improvement enabled and disabled.
Procedure
Step 1 Extended Uplink TBF Use an MS supporting the GERAN Feature Package 1 to test the Ping service performance, with the extended uplink TBF enabled and disabled. Step 2 EGPRS Access of 11-Bit Messages on the CCCH Use an EGPRS capable MS to test the Ping service performance, with the EGPRS access of 11bit messages on the CCCH enabled and disabled. Step 3 Takeover of the Packet Immediate Assignment by the BTS Use an MS to test the Ping service performance, with the takeover of the packet immediate assignment by the BTS enabled and disabled. ----End

This lists the counters related to packet performance improvement.
Alarms
None.
Counters
Counter Number of EGPRS packet channel requests on the CCCH Number of EGPRS one phase access requests on the RACH Description This measurement provides the number of EGPRS packet channel requests received on the CCCH in a granularity period. This measurement provides the number of EGPRS one phase access requests received on the RACH in a granularity period. The counter indicates the service type of the MS in progress. This measurement provides the number of EGPRS two phase access requests received on the RACH in a granularity period. The counter indicates the service type of the MS in progress.
Number of EGPRS two phase access requests on the RACH
38.7 References
l l
The extended uplink TBF complies with 3GPP TS 44.060 (Release 4). The EGPRS access of 11-bit messages on the CCCH complies with 3GPP TS 44.018 (Release 4).
38-10
Issue 02 (2008-06-30)
39 Flex Abis
39
About This Chapter
Flex Abis
39.1 Overview Flex Abis is used for the dynamic allocation of the Abis interface transmission resources on the Um interface. This feature helps to fully use the transmission resources on the Abis interface. 39.2 Availability This lists the NEs, software, and license required for the implementation of Flex Abis. 39.3 Impact This describes the impact of Flex Abis on system performance and on other features. 39.4 Technical Description Flex Abis is used for the dynamic allocation of the Abis interface transmission resources and greatly improves the utilization of transmission resources on the Abis interface. 39.5 Implementation This describes how to configure Flex Abis. 39.6 Maintenance Information This lists the alarms and performance counters related to Flex Abis. 39.7 References None.
Issue 02 (2008-06-30)
39-1
39 Flex Abis
39.1 Overview
Flex Abis is used for the dynamic allocation of the Abis interface transmission resources on the Um interface. This feature helps to fully use the transmission resources on the Abis interface.
Definition
In the traditional BSC, the Abis interface transmission resources are allocated in fixed allocation mode. That is, the transmission resources on the Abis interface and the TCH resources on the Um interface are fixedly allocated according to the configuration in a one-to-one correspondence. They cannot be shared with each other. In practice, the PS services and CS services in different cells and different BTSs are not always busy.
l l
Generally, when the load of a BTS is heavy, the load of other BTSs is light. When the traffic volume of PS services is heavy, that of CS services is light.
In such a case, if the Abis interface transmission resources can be shared among different BTSs, cells, and services, the resource utilization can be greatly improved. Flex Abis is an allocation mode of the Abis interface transmission resources. That is, the Abis interface transmission resources form a resource pool to share resources among CS services and PS services (including idle timeslots) and also among different cells and BTSs.
Purposes
With the intense competition in the communication industry, telecom operators become more and more concerned about how to reduce operating expenditure and increase profitability. Transmission resources account for one fourth of the whole operating expenditure. Flex Abis enables the sharing of the Abis interface transmission resources among different BTSs, cells, and services and thus improves the resource utilization. Especially, the Abis interface transmission resources can be fully used when Flex Abis applies to the following cases:
l l l
Multi-cell large-capacity BTSs Cascaded BTSs Cells configured with the EGPRS function
Terms
Term ESL Definition The extend signaling link (ESL) transmits signaling between the BSC and the BTS. The ESL and the operation and maintenance link (OML) use the same 64 kbit/s timeslot. In 16 kbit/s multiplexing mode, the system does not allocate timeslots for the ESL. Therefore, the ESL shares the same timeslot with the OML. After Flex Abis is configured, one BTS can be configured with only one ESL.
39-2
Issue 02 (2008-06-30)
39 Flex Abis

Acronym and Abbreviation LMT ESL Flex Abis Full Spelling Local Maintenance Terminal Extend Signaling Link Flexible Abis
39.2 Availability
This lists the NEs, software, and license required for the implementation of Flex Abis.
NEs Involved
Table 39-1 lists the NEs involved in Flex Abis. Table 39-1 NEs involved in Flex Abis MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 39-2 lists the versions of GBSS products that support Flex Abis. Table 39-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E
Issue 02 (2008-06-30)
Version V900R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R001C07 and later releases
39-3
39 Flex Abis
Product DBS3900 GSM BTS3900 GSM BTS3900A GSM
Version Not supported Not supported Not supported
Miscellaneous
Flex Abis requires a proper license. The number of TRXs that support Flex Abis is defined by the license.
39.3 Impact
This describes the impact of Flex Abis on system performance and on other features.

The impact of Flex Abis on system performance is as follows:
l
Flex Abis uses dynamic allocation of Abis interface transmission resources. When the BSC allocates related resources, it notifies the BTS through signaling messages. Therefore, the signaling load on the Abis interface increases. The reliability of dynamic allocation is low relative to fixed allocation.

The impact of Flex Abis on other features is as follows:
l
Flex Abis serves as the basis of the BTS local switching feature. After the BTS local switching, the occupied Abis interface transmission resources are released. This can save the transmission resources on the Abis interface. The ring topology of BTS I with Flex Abis enabled has the following impact on other features:
Flex Abis must be enabled in all the BTSs, and only the forward and reverse single E1 link is supported. The Abis bypass function is not supported. The 16 kbit/s LAPD link is not supported.
The Flex Abis and Abis bypass functions can be enabled simultaneously.

Flex Abis is used for the dynamic allocation of the Abis interface transmission resources and greatly improves the utilization of transmission resources on the Abis interface.
39 Flex Abis
Flex Abis Timeslot Allocation

In traditional mode, there is a one-to-one correspondence between the Um interface resources and the Abis interface transmission resources. Even if the Um interface resources are idle, the fixed Abis interface transmission resources are also occupied. After Flex Abis is enabled in the BSC, the Abis interface transmission resources use the resource pool mode. The associated Abis interface transmission resources are allocated on demand only when the Um interface resources are occupied. This substitutes the traditional fixed resource allocation mode and improves the utilization of the Abis interface transmission resources. Except that the monitoring timeslot (TS0), RSL, and OML still use the fixed allocation mode of the Abis interface transmission resources, other Abis interface transmission resources fall into the resource pool, as shown in Figure 39-1. Figure 39-1 Principle of Flex Abis
0 clock
Fixed TRX1
0 1 2 3 4 5 6 7
Dynamic
0 clock
10
10
11 12 13 20 21 22 23 30 31 32 33 40 41 42 43 5 0
11 12 13 20 21 22 23 30 31 32 33 40 41 42 43 5 0
TRX2
0 1 2 3 4 5 6 7
Occupied
Idle
Flex Abis Networking

As shown in Figure 39-2, 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 physical transmission media can be one or more E1s/T1s or satellite transmission is used. The transmission resources on each Abis interface transmission link form a resource pool to share resources between CS services and PS services.
l
The transmission resources on Link1 form Pool0.

Issue 02 (2008-06-30)
39 Flex Abis
The resources in Pool0 can be shared by CS services and PS services on BTS0, BTS1, and BTS2.
l
The transmission resources on Link2 form Pool1. The resources in Pool1 can be shared by CS services and PS services on BTS1 and BTS2. The transmission resources on Link3 form Pool2. The resources in Pool2 can be shared by CS services and PS services on BTS2.
Figure 39-2 Flex Abis network topology

Link1 Link2 Link3
B S C Pool 0
PoolB 1 T S 0 Pool 1
B T S 1 Pool 2
B T S 2
If Flex Abis is enabled in the BSC, the BSC must allocate the Abis interface transmission resources and establishes the transmission link between the BSC and the BTS, as shown in Figure 39-2. When a channel on BTS2 is allocated, the BSC must dynamically allocate the Abis interface transmission resources on Link1, Link2, and Link3 for the channel and inform BTS0, BTS1, and BTS2 that the transmission links for the channel are established. To ensure the reliable transmission of connection messages between the BSC and the BTS, a new ESL is added for transmitting connection messages. In 64 kbit/s reuse mode, the ESL and OML must use the same 64 kbit/s timeslot on an E1. The maximum number of RSL links reused by the OML must be adjusted. A maximum of two RSL links can be reused. During the second dynamic timeslot allocation, if FlexAbis Bypast-connect Status is set to YES, the BSC uses the timeslot occupied last time and does not sends the same connection message to the BTS again.
Flex Abis PS Domain Function

After Flex Abis is enabled in the BSC, the PS domain transmission resources are allocated in the following ways to improve the utilization of transmission resources:
l
The BSC allocates a main timeslot based on the transmission resources of the 16 kbit/s subtimeslot. The BSC allocates additional timeslots dynamically in steps of 16 kbit/s based on the required coding rate on the Um interface.
NOTE
When Flex Abis and EGPRS are enabled simultaneously, if the traffic volume of CS services on the BTS is light, EGPRS can operate normally even if the Idle Timeslots parameter is not specified. If the traffic volume of CS services is heavy, the Idle Timeslots parameter should be specified. Otherwise, high-speed EGPRS may be disrupted for a long period of time.
39.4.1 Abis Resources Load-Triggered Half-Rate Assignment Algorithm

39 Flex Abis
This describes the Abis resources load-triggered half-rate assignment algorithm. This algorithm determines whether the full-rate/half-rate channel assignment should be adjusted on the basis of the Abis resource load. If this algorithm is used, the full-rate TCHs can be converted to the halfrate TCHs when the Abis resources are insufficient. 39.4.2 Abis Resources Preempted by the CS Services from the PS Services When all the Abis interface transmission resources are occupied, the new CS services can preempt the Abis interface transmission resources of the PS services.
39.4.1 Abis Resources Load-Triggered Half-Rate Assignment Algorithm

This describes the Abis resources load-triggered half-rate assignment algorithm. This algorithm determines whether the full-rate/half-rate channel assignment should be adjusted on the basis of the Abis resource load. If this algorithm is used, the full-rate TCHs can be converted to the halfrate TCHs when the Abis resources are insufficient. After Flex Abis is enabled in the BSC, the Abis interface transmission resources may be insufficient before the Um interface resources are used up. Therefore, triggering half-rate assignment through the Um interface resource load in the cell may affect the performance of the entire network. The Abis resources load-triggered half-rate assignment algorithm solves this problem. Figure 39-3 shows the Abis resources load-triggered half-rate assignment procedure. Figure 39-3 Abis resources load-triggered half-rate assignment procedure
Start Calculate the Abis resources load on the transmission link Make an Abis resource load decision on the transmission link.
Make a comprehensive decision
End
1. Calculate the Abis resource load on the transmission link. After Flex Abis is enabled, the Abis interface transmission resources on the entire link are shared among all the BTSs. Therefore, the Abis resource load depends on the load of all the Abis interface connection links on the entire link. 2. Make an Abis resource load decision on the transmission link. When the Abis Resource Adjustment TCHH Function Switch is set to Yes, the system allocates half-rate TCHs preferentially if the fixed Abis channel seizure ratio exceeds the
39 Flex Abis
Fix Abis Prior Choose Abis Load Thred(%) and the Flex Abis channel seizure ratio exceeds the Flex Abis Prior Choose Abis Load Thred(%). 3. Make a comprehensive decision. The system make a comprehensive decision based on the Um interface resource load decision result and the Abis resource load decision result.
l
Assignment adjustment must be started if either of the decision results is preferential assignment of half-rate TCHs. Assignment adjustment need not be started or loopback from half rate to full rate is triggered only when the two decision results are preferential assignment of full-rate TCHs.
NOTE
For details about the decision on preferential assignment of half-rate TCHs, see 12.4.1 Channel Rate Assignment Strategies.
39.4.2 Abis Resources Preempted by the CS Services from the PS Services

When all the Abis interface transmission resources are occupied, the new CS services can preempt the Abis interface transmission resources of the PS services. The CS services and PS services share the Abis interface transmission resources. The CS services can preempt the resources of PS services on the secondary link (or even the primary link if necessary) in the local and lower-level BTSs. Whether the CS services can preempt the resources of PS services on the secondary link in the local BTS and in the lower-level BTS are determined by the parameters Sublink resources preemption switch and Lower-level sublink resources preemption switch respectively. When the CS services preempt the Abis interface transmission resources of the PS services, if the PCU supports the preemption and the PCU Support PREEMPT_ABIS_LINK message is set to Open, the BSC sends this message to the PCU.
39.5 Implementation
This describes how to configure Flex Abis. 39.5.1 Configuration Suggestions This provides the suggestions for configuring Flex Abis, which can help improve the network performance. 39.5.2 Configuring Flex Abis This describes how to configure Flex Abis on the BSC6000 Local Maintenance Terminal. 39.5.3 Configuring an Exclusive Timeslot This describes how to configure an exclusive timeslot on the BSC6000 Local Maintenance Terminal.
39.5.1 Configuration Suggestions

This provides the suggestions for configuring Flex Abis, which can help improve the network performance.
39 Flex Abis
Scenarios
To improve the resource utilization, enable Flex Abis in the following scenarios:
l
Transmission resources are limited, and the rent is very high, for example, satellite transmission. The actual traffic volume is lighter than that in the Um interface resource plan. The cells that share Abis interface transmission resources have different peak hours. The proportion of PS service users in the cell is high. Generally, the PS service and CS service have different peak hours. The resource utilization can be improved if the PS service and CS service share Abis interface transmission resources.
l l l
Suggestions on Cascaded BTS Configuration

The suggestions on the configuration of cascaded BTSs with Flex Abis enabled are as follows:
l
If you need to configure a cascaded BTS on a link to support Flex Abis, the Flex Abis Mode parameter of the upper-level BTS must be set to Flex. If the Flex Abis Mode parameter of a BTS on the link is set to SemiSolid, the Flex Abis Mode parameter of all the lower-level BTSs must be set to SemiSolid. The main cabinet group of the level 1 BTS can be connected to the GEIUB only through the E1 port on the main cabinet group. The extension cabinet group of the level 1 BTS can be connected to the GEIUB through the internal connections of the main cabinet group or through the E1 port on the extension cabinet group. The BTSs can be cascaded only through the E1 ports on the main cabinet group. The extension cabinet group can be cascaded with the upper-level BTS only through the main cabinet group. The extension cabinet groups in the same BTS cannot be cascaded. Each BTS can be cascaded with only one upper-level BTS. One BTS cannot be connected to an upper-level BTS and a GEIUB at the same time.
Suggestions on PS Service Configuration

After Flex Abis is enabled in the BSC, if the actual traffic volume is lighter than the estimated value in network design, the Abis interface transmission resources can be dynamically allocated. The static PDTCH and Idle Timeslots are not configured. That is, the primary link and secondary link are dynamically allocated. When the CS services are busy, all Abis interface transmission resources may be occupied. In this case, no Abis resources can be allocated to the subsequent PS services. If the traffic volume of PS services is light, the static PDTCH or Idle Timeslots are not required. For BTSs with Flex Abis enabled, partial static PDTCH channels and idle timeslots must be reserved for fixed allocation so that the PS services or high-speed data services can operate normally when the traffic volume becomes heavy.
Suggestions on Configuration of BTS Combined Cabinets and Cabinet Groups

The suggestions on the configuration of cabinet combination or cabinet groups between the double-transceiver BTS and the BTS that does not support Flex Abis are as follows:
39 Flex Abis
l
The Flex Abis Mode parameter 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 is set to Fix. The Flex Abis Mode between the double-transceiver BTS and the BSC or between the double-transceiver BTSs is set to Flex or SemiSolid.
Figure 39-4 Configuration of BTS combined cabinets and cabinet groups

BSC BTS BTS
Dynamic allocation
Main cabinet group (double-transceiver BTS) Fixed allocation
Fixed allocation
BTS not supporting Flex Abis
Extension cabinet group (BTS not supporting Flex Abis)
Suggestions on Parameter Modification

Generally, the Multiplexing Mode of the BTS is set to 4:1. When Flex Abis is enabled, the Multiplexing Mode can be set to 5:1 or 6:1 to multiplex five RSL links or six RSL links to a 64 kbit/s timeslot and to prevent an additional 64 kbit/s timeslot from being occupied. During the initial configuration of a BTS, set FlexAbis Mode to Flex Abis or SemiSolid to enable Flex Abis. After the BTS is configured, if you need to enable Flex Abis, set Flex Abis Mode to Flex or SemiSolid.
Other Configuration Suggestions

For a BTS with Flex Abis enabled, certain timeslots except the permanently assigned timeslots (such as signaling timeslots and monitoring timeslots) on E1 links can be disabled. These unavailable timeslots can be used for special conditions (such as satellite transmission) or in the case that only some timeslots on an E1 are available. For details, see 39.5.3 Configuring an Exclusive Timeslot.
39.5.2 Configuring Flex Abis

This describes how to configure Flex Abis on the BSC6000 Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. Apply for the license of Flex Abis. In the BSC6000V900R008 Exceptional Commercial License Application Template, specify a value in the Number of TRX supporting Flex
39-10
39 Flex Abis
Abis row of the Resource control items column. The value indicates the number of TRXs that support Flex Abis. 2. Activate the license on the Local Maintenance Terminal. For details, see Activating the BSC License.
Context
NOTE
Before configuring Flex Abis, see 39.5.1 Configuration Suggestions.
Procedure
Step 1 Configure a Flex Abis BTS.
NOTE
This describes only the Flex Abis configuration during the BTS configuration. For details about the BTS configuration, see Adding a BTS (TDM Transmission Mode).
1. 2.
On the BSC6000 Local Maintenance Terminal, right-click the GEIUB, and then choose Add Site from the shortcut menu. A dialog box is displayed. Click Add Site. A dialog box is displayed, as shown in Figure 39-5. Set FlexAbis Mode to Flex Abis or SemiSolid and set Multiplexing Mode.
NOTE
l l l
When the transmission resources are limited, if Flex Abis is enabled, set Multiplexing Mode to 5:1 or 6:1. This may cause link congestion to a certain extent. If the OML and ESL are multiplexed to timeslot 31 on each E1 link, the Multiplexing Mode of the timeslot cannot be set to 5:1 or 6:1. If the Support Separate check box is selected, the BTS can be configured with the multitransceiver unit.
Issue 02 (2008-06-30)
39-11
39 Flex Abis
Figure 39-5 Add New Site dialog box
Step 2 Configure the cell attributes. 1. 2. 3. On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page. Then, select Configure Cell Attributes from the shortcut menu. In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Select cells list box. Then, click Next. In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 39-6.
39-12
Issue 02 (2008-06-30)
39 Flex Abis
4.
Click Other Attributes. A dialog box is displayed. Click Advanced. A dialog box is displayed, as shown in Figure 39-7. On the Cell Soft Parameters tab page, set Sublink resources preemption switch and Lower-level sublink resources preemption switch according to actual requirements.
Issue 02 (2008-06-30)
39-13
39 Flex Abis
Figure 39-7 Setting other parameters
5. 6.
Click OK to return to the dialog box shown in Figure 39-6. In the dialog box shown in Figure 39-6, click Call Control. A dialog box is displayed, as shown in Figure 39-8. Set Abis Resource Adjustment TCHH Function Switch.
39-14
Issue 02 (2008-06-30)
39 Flex Abis
7. 8.
Click OK to return to the dialog box shown in Figure 39-6. In the dialog box shown in Figure 39-6, click Channel Management. Then, click Advanced. A dialog box is displayed, as shown in Figure 39-9. On the HW II Channel Assignment and Radio Channel Control tab page, set Flex Abis Prior Choose Abis Load Thred(%) according to actual requirements.
Issue 02 (2008-06-30)
39-15
39 Flex Abis
Figure 39-9 Setting channel management parameters
Step 3 Configure BSC attributes. 1. 2. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and choose Configure BSC Attributes from the shortcut menu. On the Software Parameters tab page, set FlexAbis Bypast-connect Status. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the BTS that carries the call and select Site Operation > Modify Site Flex Abis Mode. A dialog box is displayed, as shown in Figure 39-10. Set Flex Abis Mode to Flex or SemiSolid.
Step 4 Modify the Flex Abis feature of the BTS.
39-16
Issue 02 (2008-06-30)
39 Flex Abis
Figure 39-10 Configuring the Flex Abis attribute of a BTS
2.
Click Finish. The Flex Abis configuration of the BTS is complete.
----End
39.5.3 Configuring an Exclusive Timeslot

This describes how to configure an exclusive timeslot on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click a BTS with Flex Abis enabled, and then choose Manually Assign Site Abis Timeslot from the shortcut menu. Step 2 Click Set Exclusive Timeslot. A dialog box is displayed, as shown in Figure 39-11.
Issue 02 (2008-06-30)
39-17
39 Flex Abis
Figure 39-11 Set Exclusive Timeslot dialog box
Step 3 Select a port on which the exclusive timeslot is located, and then click Set Port Exclusive Timeslot. A dialog box is displayed, as shown in Figure 39-12. Set Start Time Slot No, Start Sub-TS No, End Time Slot No, and End Sub-TS No according to the actual conditions.
39-18
Issue 02 (2008-06-30)
39 Flex Abis
Figure 39-12 Browse Timeslot on the ports on site dialog box
Step 4 Click Set to let the configuration take effect.

NOTE
If you want to reconfigure Flex Abis on the exclusive timeslot, click Restore.
Step 5 Click OK. The configuration is complete. ----End

This lists the alarms and performance counters related to Flex Abis.
Alarms
Table 39-3 lists the alarms related to Flex Abis. Table 39-3 Alarms related to Flex Abis Alarm ID 410 Alarm Name BTS's capability doesn't account with the config data
Issue 02 (2008-06-30)
39-19
39 Flex Abis
Counters
Table 39-4 lists the counters related to Flex Abis. Table 39-4 Counters related to Flex Abis Counter R2720 R2721 R2722 R2723 R2730 R2731 R2732 R2733 R2741 R2742 R2751 RR2752 R276 R3162b R3163b R3164b R3142 R3151c Description Dynamic Assign Abis Resource(8K_CS) Dynamic Assign Abis Resource(16K_CS) Dynamic Assign Abis Resource (PS_MainLink) Dynamic Assign Abis Resource(PS_SubLink) Failed Dynamic Assign Abis Resource (8K_CS) Failed Dynamic Assign Abis Resource (16K_CS) Failed Dynamic Assign Abis Resource (PS_MainLink) Failed Dynamic Assign Abis Resource (PS_SubLink) FlexAbis TSs Fault FlexAbis TSs Congestion Ratio of Dynamic Assign Abis Resource(8K) Congestion Ratio of Dynamic Assign Abis Resource(16K) CS Service Connection Failures Due to Abis Link Failure Number of Failures to Allocate Abis Resources (TCHF) Number of Failures to Allocate Abis Resources (TCHH) Number of Failures to Allocate Abis Resources (Dynamic PDCH) Number of Failures to Request Dynamic PDCH (No Abis Resources Available) Number of Successful Additions of SubTimeslot (through Dynamic Allocation of Idle Timeslots)
39-20
Issue 02 (2008-06-30)
39 Flex Abis
Counter R3152a R3153a R3153c R3154a R3181
Description Number of Failures to Add Sub-Timeslot (Abis Resource Request Failure) Number of Pre-emptions of the Dynamic Abis Sub-Timeslots of the Serving Site Number of Pre-emptions of the Dynamic Abis Sub-Timeslots of the Lower-Level Site Number of Pre-emptions of Dynamic Abis Sub-Timeslots Number of Times CS Services Pre-empt the Resources for PS Services
39.7 References
None.
Issue 02 (2008-06-30)
39-21
40 MSC Pool
40
About This Chapter
MSC Pool
40.1 Overview This introduces the MSC pool. The MSCs in the MSC pool implement load balancing and resource sharing for even distribution of traffic in the MSC pool, thus reducing inter-MSC handovers and realizing redundancy backup. 40.2 Availability This lists the NEs, software, and other conditions required for the implementation of the MSC pool. 40.3 Technical Description This describes the technical aspects of the MSC pool. Through the MSC pool, the NAS node can be selected according to the load balancing algorithm. For example, new MSs are assigned to different MSCs in the MSC pool according to this algorithm; thus implementing the load balancing between MSCs in the MSC pool. 40.4 Capabilities This describes the capabilities of the MSC pool. 40.5 Implementation This describes how to configure and verify the MSC pool. 40.6 Maintenance Information This lists the alarms related to the MSC pool. 40.7 References
Issue 02 (2008-06-30)
40-1
40 MSC Pool
40.1 Overview
This introduces the MSC pool. The MSCs in the MSC pool implement load balancing and resource sharing for even distribution of traffic in the MSC pool, thus reducing inter-MSC handovers and realizing redundancy backup.
Definition
Multiple MSCs constitute an MSC pool. The BSC connects to each MSC in the MSC pool.
Purposes
The MSC pool is based on the 3GPP TS 23.236-630 protocol and has the following features:
l
The MSCs in the MSC pool implements load balancing and resource sharing, thus improving the network capacity and reducing equipment investment. The resources between MSCs in the MSC pool are evenly distributed, thus realizing redundancy backup. If you add or delete an MSC, services are not affected. Therefore, network reliability is improved. The MSC pool is logically an MSC. Therefore, the handcover between MSCs is reduced and network performance is improved.
Terms
Terms Pooling area Definition A pooling area refers to the serving area of one or more RAN nodes. Within a pooling area, an MS can roam freely without the change of the serving node of the CN. A pooling area is served by one or more CNs. Multiple pooling areas can be overlapped. The node selection mechanism refers to a mechanism where a CN device is selected to serve MSs. An NRI is used to identify a CN device. A NULL_NRI is a special NRI. It is coded following the same priciples as common NRIs.
l
Node selection mechanism NRI NULL_NRI
For an MSC pool with a single operator, the NULL_NRI is unique. When the MOCN is supported, each operator has a unique NULL_NRI in the MSC pool.
Non-broadcast LAI
A Non-broadcast LAI is a special LAI. It is coded following the same principles as common LAIs. Each MSC in the MSC pool must be assigned a unique nonbroadcast LAI, which is used when the MSC is offloaded.
40-2
Issue 02 (2008-06-30)
40 MSC Pool
Terms MSC status
Definition The MSC can be in the administration state and the operation state.
l
Administration state In the administration state, the configuration data of the MSC and the private messages on the A interface can be modified. The administration state can be normal, offload, or inhibited.
Operation state The actual state of the CN can be available or unavailable. For example, when all the No. 7 signaling links are disconnected, the state of the MSC is unavailable. After the disconnected No. 7 signaling links are restored, the state of the MSC becomes available.

Acronyms and Abbreviations BSC CN DPC IMSI IMEI MGW MSC MOCN NAS NRI RAN TMSI Full Spelling Base Station Controller Core Network Destination (signaling) Point Code International Mobile Station Identity International Mobile Station Identity Media Gateway Mobile Switching Center Multi-Operator Core Network Non Access Stratum Network Resource Identifier Radio Access Network International Mobile Station Identity
40.2 Availability
This lists the NEs, software, and other conditions required for the implementation of the MSC pool.
Issue 02 (2008-06-30)
40-3
40 MSC Pool
NEs Involved
Table 40-1 lists the NEs involved in the MSC pool. Table 40-1 NEs involved in the MSC pool MS
NOTE
BTS -
BSC
MSC
MGW
SGSN -
GGSN -
HLR
Software Releases
Table 40-2 lists the versions of GBSS products related to the MSC pool. Table 40-2 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
The precautions for using the MSC pool are as follows:
l
To implement the MSC pool, licenses are required and MSC Pool Function Enabled must be configured on the BSC side. In actual networking, the interconnected MSCs must support the MSC pool. After the MSC pool is enabled on the BSC side, the TMSI re-allocation function must be enabled on the MSC side. If the BSC supports the MSC pool, the following data of the BSC must be the same as the data of the MSC and the MGW:

l l
NRI Length(Bit) and NRI and DPC Route NULL-NRI and NULL-NRI and DPC Route MSC Available Capacity, MNC, CN ID, and MSC Administration State
In the BSC6000V900R008C01, the MSC pool in the CS domain rather than the PS domain is implemented.

This describes the technical aspects of the MSC pool. Through the MSC pool, the NAS node can be selected according to the load balancing algorithm. For example, new MSs are assigned
40 MSC Pool
to different MSCs in the MSC pool according to this algorithm; thus implementing the load balancing between MSCs in the MSC pool. 40.3.1 Typical Topology This describes the typical topology of the MSC pool. 40.3.2 TMSI Carrying NRI This describes the TMSI carrying the NRI. After the MSC pool is enabled on the BSC side, the P-TMSI allocation function must be enabled on the MSC side and the NRI must be included in the TMSI that is allocated to the MS by the MSC. 40.3.3 Load Balancing Algorithm This describes the load balancing algorithm. The BSC implements load balancing between MSCs. The BSC selects an MSC according to the status and available capacity of the MSC so that load balancing between MSCs is ensured. 40.3.4 NAS Node Selection (TMSI) This describes NAS node selection. The BSC selects an MSC in the MSC pool by parsing the NRI value in the TMSI. 40.3.5 NAS Node Selection (IMSI/IMEI) This describes the NAS node selection. When the MS uses the IMSI/IMEI to access the network, the BSC assigns the MS to an MSC according to the load balancing algorithm. 40.3.6 IMSI Paging Processing This describes IMSI paging processing. When a paging message delivered by the network carries the IMSI, the paging response message of the MS also carries the IMSI. If the two IMSIs are consistent, the BSC sends the paging response message to the MSC that sends the paging. 40.3.7 Load Reassignment This describes load reassignment. The system can reassign MSs of an MSC to other MSCs in the MSC pool. 40.3.8 Message Processing on the A Interface This describes message processing on the A interface. After the MSC pool is enabled, private messages can also be processed on the A interface. There are some changes of the standard message processing on the A interface.
40.3.1 Typical Topology

This describes the typical topology of the MSC pool. Figure 40-1 shows the typical topology of the MSC pool.
Issue 02 (2008-06-30)
40-5
40 MSC Pool
Figure 40-1 Typical topology of the MSC pool

MSC3 MSC2 MSC1 MSC6 MSC5 MSC4 MSC7
CS pool-area 1
CS pool-area 2
RAN node
Area 1
RAN node
Area 2
RAN node
Area 3
RAN node
Area 4
RAN node
Area 5
RAN node
Area 6
RAN node
Area 7
RAN node
Area 8
PS pool-area 1
PS pool-area 2
SGSN1 SGSN2
SGSN3 SGSN4 SGSN5
SGSN6
As shown in Figure 40-1, MSC1, MSC2, and MSC3 constitute an MSC pool, and Area1, Area 2, Area 5, and Area 6 constitute a pool area. Through the MSC pool, one BSC can be connected to multiple MSCs at the same time. In addition, the services on the BSC are evenly distributed to the corresponding MSC for handling according to the NRI or load balancing principle. A pool area refers to the serving area of one or more RAN nodes. Within a pool area, an MS can roam freely without the change of the serving node of the CN. A pool area is served by one or more CNs. Multiple pool areas can have common parts.
40.3.2 TMSI Carrying NRI

This describes the TMSI carrying the NRI. After the MSC pool is enabled on the BSC side, the P-TMSI allocation function must be enabled on the MSC side and the NRI must be included in the TMSI that is allocated to the MS by the MSC. The NRI length ranges from 0 bits to 10 bits and is used to identify each MSC in the MSC pool. The NRI is positioned in a specified segment and starts from the 23rd bit, as shown in Figure 40-2.
40-6
Issue 02 (2008-06-30)
40 MSC Pool
Figure 40-2 Position of the NRI in the TMSI

31 30 29 28 27 26 25 24 23 22 21 20 19 18 1 0
CS/PS
VLR-restart
used NRI range
The NRIs in a pooling area must be equal in length. If two pooling areas overlap, the NRIs in the two areas must be equal in length.
40.3.3 Load Balancing Algorithm

This describes the load balancing algorithm. The BSC implements load balancing between MSCs. The BSC selects an MSC according to the status and available capacity of the MSC so that load balancing between MSCs is ensured. The load balancing algorithm consists of the algorithm defined by protocols and the random number algorithm.
l
Algorithm defined by the 3GPP 23.236-630 protocol When the NAS message of an MS includes the IMSI or IMEI, the BSC calculates the value of V based on the formula (IMSI10)mod 1000 or (IMEI10)mod 1000. Then, the BSC selects an MSC after querying the (V, MSC) relation table. The (V, MSC) relation table is generated by the BSC based on the status and available capacity of each MSC in the MSC pool. According to this algorithm, the traffic load of the MSC is related to the distribution of the IMSI, which cannot fully implement the load balancing function.
Random number algorithm When the NAS message of the MS includes IMSI/IMEI/NULL_NRI, the BSC chooses a random number from 0 to 999 as the value of V. Then, the BSC queries the (V, MSC) relation table to determine the MSC for the current service.
The two algorithms differ in the methods for calculating the value of V but the two algorithms have the same way of selecting an MSC based on the value of V.
CAUTION
If the random number algorithm is used, the TMSI allocation function must be enabled on the MSC. This is because the mapping relation between the IMSI and the MSC is uncertain.
l
If the TMSI allocation function is not enabled on the MSC, the MS carrying the IMSI initiates a call and the BSC routes the call to other MSCs at random. This call fails because because the data of the MS is not available in the VLR of another MSC. If the TMSI allocation function is enabled on the MSC, the MS can use the TMSI in preference to initiate a call. Therefore, the call is successful.
Issue 02 (2008-06-30)
40-7
40 MSC Pool
40.3.4 NAS Node Selection (TMSI)

This describes NAS node selection. The BSC selects an MSC in the MSC pool by parsing the NRI value in the TMSI. The mapping relation between the NRI and the MSC is defined in data configuration of the BSC. An NRI corresponds to only one MSC whereas an MSC can correspond to multiple NRIs. When an MS uses the TMSI to update the location or initiate a call, the BSC can determine the MSC by parsing the NRI value in the TMSI and querying the mapping relation between the NRI and the MSC.
l
If the value of the NRI is NULL-NRI, the BSC uses the random number algorithm to select an MSC from the MSCs whose states are normal and available. If the BSC cannot find the corresponding MSC, or the MSC is in the unavailable state, or the MSC Administration State is inhibited, the BSC uses the random number algorithm to select an MSC from the MSCs whose states are normal and available.
NOTE
If the MSC pool function is enabled on the BSC, the BSC selects most of MSCs by parsing the TMSI.
40.3.5 NAS Node Selection (IMSI/IMEI)

This describes the NAS node selection. When the MS uses the IMSI/IMEI to access the network, the BSC assigns the MS to an MSC according to the load balancing algorithm. If the message Complete Layer 3 Information reported by the MS carries the IMSI, the BSC assigns the services of the MS to an MSC according to the load balancing algorithm. The MS can request services such as call initiation, location update, paging response, service re-setup, RR Initialization Request, and IMSI Detach. If the message Complete Layer 3 Information reported by the MS carries the IMEI, the BSC assigns the services on the MS to an MSC according to the load balancing algorithm. The MS can request services such as the emergence call service.
40.3.6 IMSI Paging Processing

This describes IMSI paging processing. When a paging message delivered by the network carries the IMSI, the paging response message of the MS also carries the IMSI. If the two IMSIs are consistent, the BSC sends the paging response message to the MSC that sends the paging. To ensure the normal processing of a call, the BSC must send the paging response message to the MSC that issues the paging message.
l
When a paging message carries only the IMSI, the BSC buffers the mapping relation between the IMSI and the MSC signaling point. After receiving the paging response message, the BSC queries the mapping relation between the IMSI and the MSC to find the MSC signaling point. Then, the BSC sends the paging response message to the corresponding MSC. If the BSC does not receive the paging response message within a specified period (configurable), the BSC releases the mapping relation between the IMSI and the MSC signaling point. When a paging message carries the TMSI, the BSC need not buffer the mapping relation between the IMSI and the MSC signaling point. After receiving the paging response message, the BSC finds the MSC signaling point according to the NRI in the TMSI. Then, the BSC sends the paging response message to the corresponding MSC.
40-8
40 MSC Pool
The MSC sends the CS paging message to the SGSN through the Gs interface. The SGSN forwards the message to the BSC. Then, the MS reports the paging response message to the MSC through the A interface.
l
For the CS paing message that contains the IMSI, the BSC must record the information about the mapping relation between the paging message and the MSC that issues the paging message so that the BSC can send the paging response message to the MSC in future. For the CS-domain paging message that contains the TMSI, the BSC can find the corresponding MSC according to the NRI in the TMSI. For the PS paging message, the paging response of the MS is forwarded to the SGSN through the BSC.
40.3.7 Load Reassignment

This describes load reassignment. The system can reassign MSs of an MSC to other MSCs in the MSC pool. Assume that MS1 is originally attached to MSC1, and now MSC1 is in the offload state. The offload process of MS1 is as follows:
l
MS1 initiates a call. 1. 2. 3. Before the call is established, MSC1 reassigns a TMSI to MS1. The value of the NRI is NULL_NRI and the value of the LAI is Non-broadcast LAI/RAI. After the call is terminated, if MS1 finds that the LAI sent by MSC1 is different from the LAI of the current cell, MS1 immediately initiates the location update procedure. In the location update message Complete Layer 3 Information reported by MS1, the BSC obtains the NRI NULL_NRI by decoding the TMSI. The BSC then connects MS1 to another MSC according to the load balancing algorithm. The MSC assigns a new TMSI to MS1.
4.
l
If MS1 does not initiate a call for a long period, it is assigned to an MSC through through periodical location update procedures. 1. 2. 3. 4. In the location update procedure of MS1, MS1 reports the TMSI and the BSC assigns the TMSI to MSC1. MSC1 assigns the TMSI to MS1. The NRI value in the TMSI is NULL_NRI and the LAI value in the message is Non-broadcast LAI/RAI. If MS1 finds that the LAI in the message is different from the LAI of the current cell, MS1 initiates the location update procedure again. When MSC1 is in the offload state and the NRI value in the TMSI is NULL_NRI, the BSC assigns MS1 to another MSC. In this way, MS1 is reassigned.
If MS1 is powered off for a long period, it initiates a location update procedure immediately after it is powered on.
If MSC1 is still in the offload state, MS1 is reassigned in accordance with the preceding location update procedure. If MSC1 is restored to the normal state, MS1 continues being attached to MSC1 and is not reassigned.
After the offload is complete, you must set the administration state of MSC1 to normal. Otherwise, MSC1 cannot receive the information about newly registered MSs.
40 MSC Pool
40.3.8 Message Processing on the A Interface

This describes message processing on the A interface. After the MSC pool is enabled, private messages can also be processed on the A interface. There are some changes of the standard message processing on the A interface.
Private Message Processing

In the MSC pool networking, if the MSC and the BSC are Huawei devices, the MSC periodically broadcasts its capacity usage. The private message carries the information about the total capacity and available capacity of the MSC. After receiving the private message, the BSC updates the value of the MSC available capacity parameter, thus making the load balancing algorithm more effective. If the available capacity in the private message is directly used by the BSC as a load balancing parameter, MSC Available Capacity that is set on the BSC side is invalid and unavailable for future use. To solve the problem, the BSC uses the following formula: MSC available capacity = MSC Available Capacity configured by the BSC - (total MSC capacity in the private message - MSC available capacity in the private message) When MSC Available Capacity configured by the BSC is far less than the total MSC capacity in the private message, the calculated result may be equal to or smaller than 0. In this case, the MSC available capacity is regarded as 0. In addition, the MSC sends the configuration message to notify the BSC of the current MSC status. In this way, the MSC is offloaded. The MSC can query the current MSC status saved on the BSC. If the MSC considers that the query result is abnormal, it can send the configuration message to the BSC to reset the MSC status.
NOTE
By default, the period for broadcasting the private message is one hour. The period can be set on the NSS side.
Standard Message Processing

The changes of the standard message processing on the A interface are as follows:
l
Initiating the processing of the Overload message Originally, the BSC sends the Overload message to only one MSC. After the MSC pool is enabled, the BSC needs to send the Overload message to all MSCs in the MSC pool.
Processing the RESET message Before the MSC pool is enabled, the BSC releases all the calls after receiving the RESET message on the A interface. This is because all the calls are processed by one MSC. After connecting to multiple MSCs, the BSC responds to only the MSC that sends the RESET message. The responses of the BSC include restart-indication, call clearance, and circuit initialization.
Sending the RESET message If the BSC is reset after connecting to multiple MSCs, the BSC sends the RESET message to all the MSCs and sets the Receive MSC Config. Msg. Timer to wait for the responses from all the MSCs. If the BSC does not receive any RESET message response from the MSC, the BSC resends the RESET message to the MSC.
40-10
Issue 02 (2008-06-30)
40 MSC Pool
40.4 Capabilities
This describes the capabilities of the MSC pool. The common capabilities of the MSC pool are as follows:
l l l l l l l l
Each MSC pool can be configured with up to 32 MSCs. Each BSC can be connected to 32 MSCs. Each NMS can manage 128 BSCs at the same time. Each NMS can manage 32 MSC pools at the same time. Each MSC can belong to up to eight MSC pools at the the same time. Each MSC/VLR can be configured with up to eight NRIs at the same time. Each BSC can be configured with up to 1024 NRIs. Each BSC can be configured with up to 5 NULL-NRIs and each NULL-NRI can be configured with up to 32 MSCs.
40.5 Implementation
This describes how to configure and verify the MSC pool. 40.5.1 Configuring MSC Pool (in A Interface over TDM Mode) This describes how to configure the MSC pool on the BSC6000 Local Maintenance Terminal. 40.5.2 Configuring MSC Pool (in A Interface over IP Mode) This describes how to configure the MSC pool on the BSC6000 Local Maintenance Terminal. 40.5.3 Verifying MSC Pool This describes how to verify the MSC pool. On the BSC6000 Local Maintenance Terminal, you can view the distribution of an MS to the MSC through the messages traced on the A interface.
40.5.1 Configuring MSC Pool (in A Interface over TDM Mode)

This describes how to configure the MSC pool on the BSC6000 Local Maintenance Terminal.
Prerequisite
l l l
The BSC and MSC are Huawei devices. The MSC server interconnects to the MGW and the relevant data is configured correctly. The license is applied and activated. To apply for and activate the license, do as follows: 1. When applying for the MSC pool license, ensure that Support MSC POOL Function under Function control items in BSC6000V900R008 Exceptional Commercial License Application Template is set to 1.
Issue 02 (2008-06-30)
40 MSC Pool
2. 3.
Activate the license on the BSC6000 Local Maintenance Terminal. For details, refer to Activating the BSC License. The BSC supports the MSC pool after the license is activated. Set the attributes of related objects and parameters on the BSC6000 Local Maintenance Terminal.
Context
This describes the application of the MSC pool on the BSC.
Procedure
Step 1 Configure the data of the MSC server and the MGW. 1. 2. 3. For Huawei core network devices, enable the MSC pool on the MSC side. Set A-Flex to Yes on the MSC side. Configure the parameters related to the MSC pool, such as the NRI and NULL_NRI of each MSC, available capacity of the MSC, MNC, and CN ID. For details about setting parameters, refer to the user manuals related to the MSC products. Step 2 Add a DSP. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then select Configure SS7 Signaling Point from the shortcut menu. A dialog box is displayed, as shown in Figure 40-3. In Figure 40-3, click the DSP tab. Figure 40-3 Configuring an SS7 signaling point
2.
Click Add DSP. A dialog box is displayed, as shown in Figure 40-4. Configure DSP Group No., MSC Available Capacity, MNC, CN ID, MSC Administration State, and BSC Default DSP.
40-12
Issue 02 (2008-06-30)
40 MSC Pool
Figure 40-4 Adding the DSP
NOTE
If you plan to add multiple DSPs, you need to modify BSC Default DSP.
3. 1.
Click OK. The configuration is complete. Right-click a GEIUA on the BSC Device Panel of the BSC6000 Local Maintenance Terminal and select Configure A Interface E1/T1 from the shortcut menu. A dialog box is displayed, as shown in Figure 40-5.
Step 3 Configure the A interface E1/T1.
Issue 02 (2008-06-30)
40-13
40 MSC Pool
Figure 40-5 Configuring A interface E1/T1
2.
Click Add. A dialog box is displayed, as shown in Figure 40-6. Figure 40-6 Adding A interface E1/T1
40-14
Issue 02 (2008-06-30)
40 MSC Pool
CAUTION
The DSP Group No. maps the Port No.. Configure the Start CIC of this port. The start CICs of different ports within a DPC group cannot be duplicate. 3. 1. Click OK. The configuration is complete. On the BSC6000 Local Maintenance Terminal, right-click BSC6000 and then select Configure BSC Attributes from the shortcut menu. Click the MSC Pool Parameters tag on the displayed dialog box as shown in Figure 40-7.
Step 4 Configure MSC pool parameters.
Figure 40-7 Configuring MSC pool parameters
2.
Configure the parameters displayed in Figure 40-7 and then click Finish. The configuration of the MSC pool parameters is complete. Click the NRI and DPC Route tab in Figure 40-7. A tab page is displayed, as shown in Figure 40-8.
Step 5 Configure the NRI and DPC route. 1.
Issue 02 (2008-06-30)
40-15
40 MSC Pool
Figure 40-8 Configuring the NRI and DPC route
2.
Click Add. A dialog box is displayed, as shown in Figure 40-9. Configure NRI and DPC. Figure 40-9 Adding the NRI and DPC route
3.
Click OK. The configuration of the NRI and DPC route is complete.
Step 6 Configure the Null-NRI and DPC route. 1. Click the Null-NRI and DPC Route tab in Figure 40-7. A tab page is displayed, as shown in Figure 40-10.
40 MSC Pool
Figure 40-10 Configuring the Null-NRI and DPC route
2.
Click Add. A dialog box is displayed, as shown in Figure 40-11. Configure NULL-NRI and DPC. Figure 40-11 Adding the Null-NRI and DPC route
3.
Click OK. The configuration of the Null-NRI and DPC route is complete.
----End
40 MSC Pool
40.5.2 Configuring MSC Pool (in A Interface over IP Mode)

This describes how to configure the MSC pool on the BSC6000 Local Maintenance Terminal.
Prerequisite
l l l
The BSC and MSC are Huawei devices. The MSC server interconnects to the MGW and the relevant data is configured correctly. The license is applied and activated. To apply for and activate the license, do as follows: 1. When applying for the MSC pool license, ensure that Support MSC POOL Function under Function control items in BSC6000V900R008 Exceptional Commercial License Application Template is set to 1. Activate the license on the BSC6000 Local Maintenance Terminal. For details, refer to Activating the BSC License. The BSC supports the MSC pool after the license is activated. Set the attributes of related objects and parameters on the BSC6000 Local Maintenance Terminal.
2. 3.
Context
This describes the application of the MSC pool on the BSC.
Procedure
Step 1 Configure the data of the MSC server and the MGW. 1. 2. 3. For Huawei core network devices, enable the MSC pool on the MSC side. Set A-Flex to Yes on the MSC side. Configure the parameters related to the MSC pool, such as the NRI and NULL_NRI of each MSC, available capacity of the MSC, MNC, and CN ID. For details about setting parameters, refer to the user manuals related to the MSC products. Step 2 Configure the M3UA destination entity. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then select Configure M3UA Data > Configure M3UA Entity from the shortcut menu. A dialog box is displayed, as shown in Figure 40-12. In Figure 40-12, click the DSP tab.
40-18
Issue 02 (2008-06-30)
40 MSC Pool
Figure 40-12 Configuring the M3UA destination entity
2.
Click Add. A dialog box is displayed, as shown in Figure 40-13. Configure DSP Group No., MSC Available Capacity, MNC, CN ID, MSC Administration State, and BSC Default DSP. Figure 40-13 Adding the M3UA destination entity
3.
Click OK. The configuration is complete.
Step 3 Configure the M3UA link set.

40 MSC Pool
1.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then select Configure M3UA Data > Configure M3UA Linkset from the shortcut menu. A dialog box is displayed, as shown in Figure 40-14.
Figure 40-14 Configuring the M3UA link set
2.
Click Add. A dialog box is displayed, as shown in Figure 40-15. Figure 40-15 Adding the M3UA link set
3.
40-20
Set each parameter and click OK. The configuration of the M3UA link set is complete.
40 MSC Pool
Step 4 Configure the M3UA route. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then select Configure M3UA Data > Configure M3UA Route from the shortcut menu. A dialog box is displayed, as shown in Figure 40-16.
Figure 40-16 Configuring the M3UA route
2.
Click Add. A dialog box is displayed, as shown in Figure 40-17. Figure 40-17 Adding the M3UA route
Issue 02 (2008-06-30)
40-21
40 MSC Pool
3. 1.
Set each parameter and click OK. The configuration of the M3UA route is complete. On the BSC6000 Local Maintenance Terminal, right-click the GFGUA board of the GMPS subrack, and then select Configure M3UA Link from the shortcut menu. A dialog box is displayed, as shown in Figure 40-18.
Step 5 Configure the M3UA link.
Figure 40-18 Configuring the M3UA link
2.
Click Add. A dialog box is displayed, as shown in Figure 40-19.
40-22
Issue 02 (2008-06-30)
40 MSC Pool
Figure 40-19 Adding the M3UA link
3.
Set each parameter and click OK. The configuration of the M3UA route is complete.
Step 6 Configure MSC pool parameters. 1. On the BSC6000 Local Maintenance Terminal, right-click BSC6000 and then select Configure BSC Attributes from the shortcut menu. Click the MSC Pool Parameters tab in the displayed dialog box, as shown in Figure 40-20.
Figure 40-20 Configuring MSC pool parameters
Issue 02 (2008-06-30)
40-23
40 MSC Pool
2.
Set each parameter and click Finish. The configuration of the MSC pool parameters is complete. Click the NRI and DPC Route tab in Figure 40-20. A tab page is displayed, as shown in Figure 40-21.
Step 7 Configure the NRI and DPC route. 1.
Figure 40-21 Configuring the NRI and DPC route
2.
Click Add. A dialog box is displayed, as shown in Figure 40-22. Configure NRI and DPC.
40-24
Issue 02 (2008-06-30)
40 MSC Pool
Figure 40-22 Adding the NRI and DPC route
3.
Click OK. The configuration of the NRI and DPC route is complete.
Step 8 Configure the Null-NRI and DPC route. 1. Click the Null-NRI and DPC Route tab in Figure 40-20. A tab page is displayed, as shown in Figure 40-23. Figure 40-23 Configuring the Null-NRI and DPC route
2.
Click Add. A dialog box is displayed, as shown in Figure 40-24. Configure NULL-NRI and DPC.
Issue 02 (2008-06-30)
40-25
40 MSC Pool
Figure 40-24 Adding the Null-NRI and DPC route
3.
Click OK. The configuration of the Null-NRI and DPC route is complete.
----End
40.5.3 Verifying MSC Pool

This describes how to verify the MSC pool. On the BSC6000 Local Maintenance Terminal, you can view the distribution of an MS to the MSC through the messages traced on the A interface.
Prerequisite
l l
The BSC and MSC are Huawei devices. The MSC server interconnects to the MGW and the relevant data is configured correctly.
Context
The MSC pool is verified with the load balancing algorithm.
Procedure
l Select Random Algorithm in the MSC Pool Load Balancing Algorithm Selection table. 1. After the MS is powered on, its location is updated.
Use the IMSI for location update. The MS is assigned to a normal and available MSC in the MSC pool at random. The MSC with a higher available capacity is more probable to be chosen.
Use the TMSI for location update. The MS is assigned to the MSC that maps the NRI in the TMSI.
2.
After the location of the MS is updated, the MSC assigns the TMSI to the MS. This MSC provides later service for the MS.
40-26
40 MSC Pool
3. l
When the MS initiates a call or other services again, the MS is assigned to the MSC.
Select Based on MSC ID Algorithm in the MSC Pool Load Balancing Algorithm Selection table. Each time the location of the MS is updated through the IMSI or a call is initiated, the BSC assigns the MS to a specified MSC in the normal and available state.
----End

This lists the alarms related to the MSC pool.
Alarms
If multiple DSPs are supported, the DPC information is added to the alarms related to the MSC for distinguishing different MSCs. Table 40-3 lists the alarms related to the MSC pool. Table 40-3 Alarms related to the MSC pool Alarm ID 124 126 129 130 131 132 133 Alarm Name No A Interface Circuit Configured in the BSC No Circuit Configured in the MSC MSC Resetting BSC Resetting Failure BSC Unable to Reset a Circuit BSC Unable to Block a Circuit BSC Unable to Unblock a Circuit
Performances
None.
40.7 References
3GPP TS 23.236 V6.3.0
Issue 02 (2008-06-30)
40-27
41 BTS Ring Topology
41
About This Chapter
BTS Ring Topology
41.1 Overview This describes the definition and purpose of BTS ring topology. In addition to saving transmission resources, the BTS ring topology improves system reliability, protects operators' investment, and ensures normal services. 41.2 Availability This describes the availability of the BTS ring topology, which involves the network elements (NEs), software, and other conditions. 41.3 Impact This describes the impact of BTS ring topology on the system performance. 41.4 Technical Description This describes the technical aspects of BTS ring topology, including the automatic switchover and manual switchover during link disconnection, and the types of BTS ring topology. 41.5 Implementation This describes how to configure the BTS ring topology, change non-ring topology to ring topology, verify BTS ring topology, delete a BTS from the ring topology, and manually switch over the BTS ring topology. 41.6 Maintenance Information There is no maintenance information about the BTS ring topology. 41.7 References None.
Issue 02 (2008-06-30)
41-1
41.1 Overview
This describes the definition and purpose of BTS ring topology. In addition to saving transmission resources, the BTS ring topology improves system reliability, protects operators' investment, and ensures normal services.
Definition
The BTS ring topology is one of the topologies supported by the BTS. Other topologies include star, chain, and tree topologies. Figure 41-1 and Figure 41-2 show the BTS ring topologies. Figure 41-1 BTS ring topology (1)
A 0 G E I U B BTS0 1
B 0 BTS1 1
C 0 BTS2
D 1
E 1 BTS3 0
Figure 41-2 BTS ring topology (2)
A G E I U B 0 BTS0 1
B 0 BTS1 1
C 0 BTS2
D 1
G E I U B
E 1 BTS3 0
41-2
Issue 02 (2008-06-30)

NOTE
0 and 1 shown in Figure 41-1 refer to port 0 and port 1 of the BTS. In the BTS ring topology, the link set up at port 0 is a forward link and the link set up at port 1 is a reverse link. The BTS ring topology can be implemented between interface boards but not between subracks. In other words, the BTS ring topology must be implemented between the GEIUBs located in the same subrack, as shown in Figure 41-2.
Normally, the BTS ring topology is a chain of BTS0, BTS1, and BTS2 in sequence, known as a forward direction. In the forward direction as shown in Figure 41-1, BTS0 is the highest-level BTS, BTS1 is the second-level BTS, .and other BTSs are connected analogically. When the link A, B, C, or D is broken, the BTSs in front of the breakpoint remains in the same topology, and the BTSs behind the breakpoint form a chain in a reverse direction. The BTS ring topology is categorized into two types, namely, Huawei BTS ring topology and Huawei BTS ring topology . In BTS ring topology , the BTS with a reverse link will be initialized again after transmission disruption, and thus the services of the BTS are interrupted. In BTS ring topology , the services of the BTS with a reverse link are not interrupted after transmission disruption.
Purposes
The BTS ring topology saves transmission resources and improves network reliability.
Terms
None.

None.
41.2 Availability
This describes the availability of the BTS ring topology, which involves the network elements (NEs), software, and other conditions.
NEs Involved
Table 41-1 lists the NEs involved in the BTS ring topology. Table 41-1 NEs involved in BTS ring topology MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Issue 02 (2008-06-30)
41-3
Software Releases
Table 41-2 lists the versions of GBSS products that support BTS ring topology . Table 41-2 GBSS products and software versions supporting BTS ring topology Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM Version V900R008C01 and later releases BTS3000V100R001C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Table 41-3 lists the versions of GBSS products that support BTS ring topology . Table 41-3 GBSS products and software versions supporting BTS ring topology Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM Version V900R008C01 and later releases BTS3000V100R004C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
41-4
Issue 02 (2008-06-30)
Miscellaneous
l l
The BTS in the ring topology can be connected only with a single E1 link. The BTS in the same ring topology can be configured as only one type, that is, either BTS ring topology or BTS ring topology . Based on physical links, a maximum of five levels of cascaded BTSs can be set up in the ring topology. Call drops occur when the forward link and reverse link in BTS ring topology are switched over.
NOTE
The ring topology uses port 0 and port 1 of the BTS.
41.3 Impact
This describes the impact of BTS ring topology on the system performance.

BTS Ring Topology I
l
If you manually switch over the BTS ring topology, the BTS is reset and thus the services of the BTS are affected. After automatic disconnection, the BTS is initiated and thus the services of the BTS are affected. The BTS ring topology with 39 Flex Abis enabled does not preempt lower-level sublink resources.
BTS Ring Topology II

l
The switchover from forward link to reverse link of the BTS ring topology lasts no longer than eight seconds, which is also the time when a physical link is restored to an RSL link. The OML link is established eight seconds after the setup of the physical link.

BTS Ring Topology I
l l l
Other ports of the BTSs cannot be connected to the cascaded BTSs. 53.4.2 Abis over IP and Hub BTS are not supported. BTS ring topology I with 39 Flex Abis enabled has the following impacts on the other features:
39 Flex Abis must be enabled in all the BTSs and only the forward and reverse single E1 link is supported. The Abis bypass function is not supported. The 16 kbit/s LAPD link is not supported.
BTS Ring Topology II

l l
Other ports of the BTSs cannot be connected to the cascaded BTSs. 53.4.2 Abis over IP and Hub BTS are not supported.
Issue 02 (2008-06-30)

l
39 Flex Abis, 54 Abis Transmission Optimization, and Abis bypass are not supported.

This describes the technical aspects of BTS ring topology, including the automatic switchover and manual switchover during link disconnection, and the types of BTS ring topology. 41.4.1 Automatic Switchover During Link Disconnection This describes the automatic switchover performed during link disconnection. When a link of the BTS ring topology is broken, the BTSs behind the breakpoint automatically set up a link in the reverse direction. 41.4.2 Manual Switchover During Link Disconnection This describes the manual switchover during link disconnection. When a link is broken and the transmission is restored with the setup of a reverse link, the automatic switchover is disabled. 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. 41.4.3 Types of BTS Ring Topology The BTS ring topology is categorized into two types, namely, BTS ring topology and BTS ring topology . The difference between the two types is that after transmission disruption, BTS ring topology re-initializes the reverse-link BTS and thus interrupts the BTS services, whereas BTS ring topology does not interrupt the BTS services. 41.4.4 BTS HDLC Ring Topology The HDLC ring topology is composed of the BTSs that operate in Abis optimized transmission mode.
41.4.1 Automatic Switchover During Link Disconnection

This describes the automatic switchover performed during link disconnection. When a link of the BTS ring topology is broken, the BTSs behind the breakpoint automatically set up a link in the reverse direction. The automatic switchover is a basic function of the BTS ring topology. Normally, all the BTSs in the ring topology form a chain of forward links. If one of the links is broken, all the BTSs behind the breakpoint automatically set up a link in the reverse direction. When the reverse link is set up, the BTSs are initialized to form a new chain which can work normally. If the forward link is restored to a normal state but 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 (Ring I Waiting Time Before Rotate(s) or Ring Waiting Time Before Rotate(s) to prevent the switchover caused by OML intermittent.
41.4.2 Manual Switchover During Link Disconnection

This describes the manual switchover during link disconnection. When a link is broken and the transmission is restored with the setup of a reverse link, the automatic switchover is disabled. 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 must be first connected to the specified port. If the connection fails, the
BTS is connected to another port. The BTSs are connected separately to form a ring topology, and the OML of the lower-level BTSs can be set up only after the upper-level BTSs transparently transmit the timeslot exchange. 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 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. When you switch over the reverse link to the forward link, you must first switch over the highest-level BTS in the forward direction.
NOTE
During manual switchover, the corresponding BTS is reset and related alarms are reported. The port mentioned herein refers to the port on the GEIUB/GOIUB.
l
The parameters involved in the switchover of BTS ring topology are Ring I Waiting Time Before Rotate(s) and Ring I Try Rotating Duration Time(s). The parameters involved in the switchover of BTS ring topology are Ring Waiting Time Before Rotate(s) and Ring Try Rotating Duration Time(s).
41.4.3 Types of BTS Ring Topology

The BTS ring topology is categorized into two types, namely, BTS ring topology and BTS ring topology . The difference between the two types is that after transmission disruption, BTS ring topology re-initializes the reverse-link BTS and thus interrupts the BTS services, whereas BTS ring topology does not interrupt the BTS services.
BTS Ring Topology

In BTS ring topology , when the BTS is disconnected from the network, the BTS can be reconnected in the reverse direction through automatic switchover. Thus, the BTS can work normally. If the transmission is restored to the normal state after the BTS is reconnected in the reverse direction, the automatic switchover is disabled. You can enable the manual switchover function to connect the BTS in the forward direction. When BTS ring topology and Flex Abis are enabled at the same time, the dynamic assignment of timeslots for transmission can be performed in the forward and reverse directions if the communication in the two directions is normal, as shown in Figure 41-3. This function prevents transmission links from congestion and enhances network resource utilization. Figure 41-3 Transmission in the forward and reverse directions
A 0 G E I U B BTS0 1
B 0 BTS1
C 1 0 BTS2
D 1
Forward link
Reverse link
E 1 BTS3 0
Issue 02 (2008-06-30)
41-7
BTS Ring Topology

BTS ring topology is optimized on the basis of BTS ring topology . The difference between the two types is that after transmission disruption, BTS ring topology re-initializes the reverselink BTS and thus interrupts the BTS services, whereas BTS ring topology does not interrupt the BTS services. The parameters related to BTS ring topology are configured on the BSC6000 Local Maintenance Terminal. To enable BTS ring topology , set Configure Ring to Yes. Other parameters include Ring Waiting Time Before Rotate(s), Ring Try Rotating Duration Time(s), and Ring Rotating Penalty Time(s). In addition, set the parameters related to OML links. The system detects the OML link status according to the parameters T200 (10ms), T203 (s), and N200 (time)
NOTE
The parameters related to BTS ring topology can be queried.
41.4.4 BTS HDLC Ring Topology

The HDLC ring topology is composed of the BTSs that operate in Abis optimized transmission mode. The HDLC ring topology applies only to ring topology II. The HDLC ring topology supports the formation of the ring through ports 0 and 1 of each BTS. The forward ring and reverse ring can be connected over one interface board or over two interface boards. However, the two rings cannot be connected over different subracks. Compared with the TDM ring topology, the HDLC ring topology has the following restrictions:
l l l
The HDLC ring topology does not support the HDLC-TDM hybrid networking. The HDLC ring topology does not support the connection of a secondary link. In HDLC ring topology, the hybrid grouping with an old cabinet (BTS30 or BTS312) is not supported. The HDLC ring topology does not support the connection of a branch BTS. The HDLC ring topology does not the functions such as Flex Abis, Abis bypass, local switching, and 16 kbit/s LAPD signaling links. The HDLC ring topology supports the configuration of exclusive timeslots, but does not support the configuration of monitor timeslots. The timeslots associated with the HDLC ring topology do not support the manual allocation. The HDLC ring topology does not support the conversion of the bearing modes, that is, the conversion from the HDLC ring topology to the TDM ring topology.
NOTE
l l
l l
Based on physical links, a maximum of five levels of cascaded BTSs can be set up in the ring topology. In HDLC ring topology, ports 0 and 1 of the BTSs are used. The connection of ports 0 and 1 of the BTSs should cannot be modified.
41-8
Issue 02 (2008-06-30)
41.5 Implementation
This describes how to configure the BTS ring topology, change non-ring topology to ring topology, verify BTS ring topology, delete a BTS from the ring topology, and manually switch over the BTS ring topology. 41.5.1 Recommended Configuration of BTS Ring Topology This provides the recommended configuration of BTS ring topology to meet different network requirements. 41.5.2 Configuring BTS Ring Topology This describes how to configure the BTS ring topology on the BSC6000 Local Maintenance Terminal. 41.5.3 Changing Non-Ring Topology to Ring Topology This describes how to change non-ring topology to ring topology on the BSC6000 Local Maintenance Terminal. 41.5.4 Verifying BTS Ring Topology This describes how to verify the BTS ring topology on the BSC6000 Local Maintenance Terminal. 41.5.5 Deleting a BTS from Ring Topology This describes how to delete a BTS from the ring topology on the BSC6000 Local Maintenance Terminal. 41.5.6 Manually Switching over BTS Ring Topology This describes how to manually switch over the BTS ring topology on the BSC6000 Local Maintenance Terminal.
41.5.1 Recommended Configuration of BTS Ring Topology

This provides the recommended configuration of BTS ring topology to meet different network requirements.
Scenarios
Generally, BTS ring topology is implemented in the following scenarios:
l l
Communication quality is good and transmission is stable. Communication quality is poor and transmission is unstable.
Recommended Configurations
Table 41-4 describes the parameter configuration of BTS ring topology in good-quality transmission.
Issue 02 (2008-06-30)
41-9
Table 41-4 Parameter configuration of BTS ring topology in good-quality transmission Ring Waiting Time Before Rotate (s) 0 Ring Try Rotating Duration Time(s) 60 Ring II Rotating Penalty Time(s) 0 T200 (10ms) T203 (s) N200 (time)
12
Table 41-5 describes the parameter configuration of BTS ring topology in poor-quality transmission. Table 41-5 Parameter configuration of BTS ring topology in poor-quality transmission Ring Waiting Time Before Rotate (s) 30 Ring Try Rotating Duration Time(s) 60 Ring II Rotating Penalty Time(s) 0 T200 (10ms) T203 (s) N200 (time)
24
41.5.2 Configuring BTS Ring Topology

This describes how to configure the BTS ring topology on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The type of BTS ring topology is determined, that is, either BTS ring topology I or BTS ring topology II. The service bearing mode is determined, that is, either TDM mode or HDLC mode.
Context
NOTE
This takes adding TDM ring topology on the GEIUB as an example for configuring BTS ring topology I. This takes adding HDLC ring topology on the GEHUB as an example for configuring HDLC ring topology.
Procedure
l Configure BTS ring topology I. 1. 2. On the BSC6000 Local Maintenance Terminal, right-click the GEIUB, and then select Add Site from the shortcut menu. A dialog box is displayed. In the displayed dialog box, click Add Site. Then, in the displayed dialog box, set the parameters such as SiteType and Site Name, set Config Ring to Yes, and set Service Mode to TDM, as shown in Figure 41-4.
41-10
Issue 02 (2008-06-30)
Figure 41-4 Add New Site dialog box (TDM)
3.
Click OK and a dialog box is displayed. SpecifyRev Ring Slot No and Rev Ring Port No, as shown in Figure 41-5. Figure 41-5 Set Rev Info dialog box (1)
4.
Click OK. A dialog box is displayed, as shown in Figure 41-6.
Issue 02 (2008-06-30)
41-11
Figure 41-6 Add Site dialog box (1)
5.
Click Add Site, as shown in Figure 41-6. For details, refer to Adding a BTS (TDM Transmission Mode).
NOTE
If the BTS in the ring topology supports Flex Abis, you are required to configure Flex Abis. For details, refer to 39.5.2 Configuring Flex Abis.
Configure BTS ring topology . 1. On the BSC6000 Local Maintenance Terminal, right-click a BTS and select Site Operation > Configure Site Attributes from the shortcut menu.
NOTE
BTS ring topology II is configured on the basis of BTS ring topology I.
2.
In the displayed dialog box, click Set Site Attributes. A dialog box is displayed, as shown in Figure 41-7.
41-12
Issue 02 (2008-06-30)
Figure 41-7 Site Attributes dialog box
3.
Select the Ring Information tab page, set Configure Ring to Yes, and set other parameters, as shown inFigure 41-8.
Issue 02 (2008-06-30)
41-13
Figure 41-8 Configuring parameters related to BTS ring topology II
4. l 1. 2.
Click OK to return to the previous dialog box, and click Finish to end the task. On the BSC6000 Local Maintenance Terminal, right-click the GEHUB, and then select Add Site from the shortcut menu. In the displayed dialog box, click Add Site. Then, in the displayed dialog box, set the parameters such as SiteType and Site Name, set Config Ring to Yes, and set Service Mode to HDLC, as shown in Figure 41-9.
Configure HDLC ring topology.
41-14
Issue 02 (2008-06-30)
Figure 41-9 Add New Site dialog box (HDLC)
3.
Click OK and a dialog box is displayed. SpecifyRev Ring Slot No and Rev Ring Port No, as shown in Figure 41-10. Figure 41-10 Set Rev Info dialog box (2)
4.
Click OK. A dialog box is displayed, as shown in Figure 41-11.
Issue 02 (2008-06-30)
41-15
5. ----End
Click Add Site, as shown in Figure 41-11. For details, refer to Adding a BTS (HDLC/ HUB Transmission Mode).
41.5.3 Changing Non-Ring Topology to Ring Topology

This describes how to change non-ring topology to ring topology on the BSC6000 Local Maintenance Terminal.
Context
Before you change non-ring topology to ring topology, the following prerequisites must be met :
l
The BTSs must be in the chain topology, and port 1 of the upper-level BTS must be connected to port 0 of the lower-level BTS. Only the ring topology parameters of the lowest-level BTS can be modified. The cables between the lowest-level BTS and the BSC are connected.
l l
CAUTION
During the change from non-ring topology to ring topology, the corresponding BTS is reset and related alarms are reported.
41-16
Issue 02 (2008-06-30)
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a BTS whose ring topology is to be changed, and then choose Site Operation > Configure Site Attributes . A dialog box is displayed, as shown in Figure 41-12. Figure 41-12 Configure Site Attributes dialog box
Step 2 Select the lowest-level BTS in the ring topology, and then click Set Site Attributes. A dialog box is displayed. Step 3 Select the Ring Information tab page, and then set Configure Ring to Yes, as shown in Figure 41-13. Then, Click OK.
Issue 02 (2008-06-30)
41-17
Figure 41-13 Site Attributes dialog box
Step 4 Click OK to return to the upper-level menu. Step 5 Click Finish to end the task.
NOTE
To change the ring topology to BTS ring topology , refer to the related section in 41.5.2 Configuring BTS Ring Topology.
----End
41.5.4 Verifying BTS Ring Topology

This describes how to verify the BTS ring topology on the BSC6000 Local Maintenance Terminal.
Context
BTS ring topology verification happens in the network deployment acceptance phase and the troubleshooting phase.
CAUTION
During manual switchover, the corresponding BTS is reset and related alarms are reported.
41-18
Issue 02 (2008-06-30)
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BTS Maintenance > Maintain Site > Maintain Ring Network. A dialog box is displayed, as shown in Figure 41-14. Figure 41-14 Maintain Ring Network dialog box
Step 2 Select a BTS in the ring topology, and then click Query. The Working Port of the BTS is displayed. Step 3 Manually switch over the BTS. Select the BTSs that need to be switched over, and then click Switch. Step 4 Query the working port of the BTS. After the BTS is normally started, refer to Step 1 and Step 2 to query the Working Port of the BTS. If any of the following situations occurs, you can infer that the ring topology is set up successfully.
l l
The Working Port queried in Step 2 is 0, and the Working Port queried in this step is 1. The Working Port queried in Step 2 is 1, and the Working Port queried in this step is 0.
----End
Issue 02 (2008-06-30)
41-19
41.5.5 Deleting a BTS from Ring Topology

This describes how to delete a BTS from the ring topology on the BSC6000 Local Maintenance Terminal.
Prerequisite
CAUTION
Before deleting a BTS, ensure that the E1 cables connected to the target BTS are removed.
Context
If the deleted BTS has lower-level BTSs, the lower-level BTSs are also deleted.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a BTS in the ring topology, and then choose Site Operation > Delete Site. A dialog box is displayed, as shown in Figure 41-15. Figure 41-15 Delete Site dialog box
Step 2 Select the BTS that needs to be deleted, and then double-click it to add it into the Site List. Step 3 Click Finish to end the task. ----End
41.5.6 Manually Switching over BTS Ring Topology

This describes how to manually switch over the BTS ring topology on the BSC6000 Local Maintenance Terminal.
Prerequisite
The communication between the BSC and the BTS is normal.
Context
When you switch over the forward link to the reverse link, first switch over the highest-level BTS in the reverse direction and then the other BTSs in sequence. When you switch over the reverse link to the forward link, first switch over the highest-level BTS in the forward direction and then the other BTSs in sequence.
CAUTION
The manual switchover of BTS ring topology is critical to operation and maintenance. After switchover, the BTS cannot work for a period of time, which may affect services. Therefore, be cautious when performing this operation.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, choose BTS Maintenance > Maintain Site > Maintain Ring Network. A dialog box is displayed, as shown in Figure 41-16.
Issue 02 (2008-06-30)
41-21
Figure 41-16 Maintain Ring Network dialog box
Step 2 Select BTSs from the Candidate Sites, and click Query. The parameters Working Port, Auto Switch Enable, Waiting Time Before Switch(s), Try Switching Duration Time(s), RingNet , and Query Result of the selected BTSs are displayed.
NOTE
The settings of displayed parameters are determined by RingNet . If RingNet is set to No, the value of RingNet is displayed; if RingNet is set to Yes, the value of RingNet is displayed.
Step 3 Select the BTSs that need to be switched over, and then click Switch. The Maintain Ring Network dialog box is displayed, as shown in Figure 41-16. ----End

There is no maintenance information about the BTS ring topology.
Alarms
None.
Counters
None.
41.7 References
None.
Issue 02 (2008-06-30)
41-23
42 Remote Upgrade
42
About This Chapter
Remote Upgrade
42.1 Overview This describes the remote upgrade of the host software and OMU software of the BSC through the M2000 client. 42.2 Availability This lists the NEs, software, and other conditions required for the implementation of remote upgrade. 42.3 Technical Description This describes how to perform remote upgrade. The upgrade of the BSC network element is performed on three levels and in six modes. The upgrade process involves three phases, getting ready for the upgrade, executing the upgrade, and processing after the upgrade. 42.4 Implementation This describes how to get ready for the upgrade, create an NE object, upload software and data, and perform upgrade. 42.5 Maintenance Information None. 42.6 References None
Issue 02 (2008-06-30)
42-1
42 Remote Upgrade
42.1 Overview
This describes the remote upgrade of the host software and OMU software of the BSC through the M2000 client.
Definition
The BSC software involved in remote upgrade consists of the host software and the OMU software. The host software runs on various service boards. It consists of the operating system, middleware, and application software. The OMU software runs on the GBAM or on the GOMU to perform the operation and maintenance of the BSC. Remote upgrade involves the upgrade of the host software and OMU software.
Purposes
Remote upgrade has the following benefits over the local upgrade:
l l l
Remote upgrade saves time and efforts. Remote upgrade provides the simultaneous upgrade of multiple network elements. You do not need to be familiar with the Linux commands because the M2000 client provides a user-friendly and convenient interface for operation.
Terms
Term Cold patch Definition 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. A set of files 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 process running on the GBAM or the GOMU to implement remote upgrade of the BSC software.
Hot patch
Upgrading process

Acronyms and Abbreviations RUS OMU
42-2
Full Spelling Remote Upgrade Service Operation and Maintenance Unit
Issue 02 (2008-06-30)
42 Remote Upgrade
Acronyms and Abbreviations SMU MML SWM
Full Spelling Service Management Unit Man Machine Language SoftWare Management
42.2 Availability
This lists the NEs, software, and other conditions required for the implementation of remote upgrade.
NEs Involved
Table 42-1 lists the NEs involved in remote upgrade. Table 42-1 NEs involved in remote upgrade MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 42-2 lists the versions of GBSS products that support remote upgrade. Table 42-2 GBSS products and related versions Product BSC M2000 BSC6000 Version V900R008C01 and later releases V200R006
Miscellaneous
The remote upgrade is restricted by the following conditions:
l l
The remote upgrade can be implemented only through the matching version of the M2000. The adaptation layer of the M2000 must be installed for the upgrade version.
Issue 02 (2008-06-30)
42 Remote Upgrade
l
The messages between the new and old versions of the monitoring process on the BSC GBAM/GOMU must be compatible. The configuration data of the new BSC version cannot be modified before upgrade. The Level 2 BIOS of a new BSC version must be able to run the host software of an old version. The remote upgrade is not allowed when the BSC board fails. In remote upgrade, the BSC6000 V900R008C01 can be upgraded to later releases.
NOTE
l l
l l
For the matching of versions, refer to BSC6000 V900R008C01BXXX Release Notes.

This describes how to perform remote upgrade. The upgrade of the BSC network element is performed on three levels and in six modes. The upgrade process involves three phases, getting ready for the upgrade, executing the upgrade, and processing after the upgrade. Remote upgrade is divided into three levels: step, command, and sub-operation. An upgrade consists of multiple steps; each step consists of multiple MML commands; each MML command consists of one or more sub-operations. To shield the differences between network elements, the M2000 only needs to understand and the steps and commands and controls the BSC NEs. The upgrade process needs to understand and control the steps, commands, and sub-operations. The steps and commands in upgrade are defined in the customized .xml file of the upgrade process. Figure 42-1 shows the system architecture of remote upgrade.
42-4
Issue 02 (2008-06-30)
42 Remote Upgrade
Figure 42-1 Architecture of remote upgrade
Active OMU MML M2000 MML Upgrading process OMU LOCAL OMU CORE
SMU SMU SMU
MML MML
Standby OMU Upgrading process OMU LOCAL OMU CORE
In the architecture of remote upgrade, the relationship between the processes is as follows:
l l l
The M2000 and the OMUCore process use the MML interface. The M2000 and the upgrade process use the MML interface. To start and quit the OMUCore process and the OMULocal process, the MML interface between the upgrade process and the monitoring process is used. The MML interface between the upgrade process and the Linux operating system is used in backing up OMU files and installing the OMU. The upgrade processes on the active and standby OMUs use the internal message interface based on TCP.
MML MML
Monitoring process
LINUX operating system
Monitoring process
LINUX operating system
42.3.1 Remote Upgrade Modes

This describes the modes of remote upgrade. After the remote upgrade is started, the M2000 automatically judges the upgrade mode, that is, the upgrade process and whether to adopt the remote upgrade.
42 Remote Upgrade
The remote upgrade modes are as follows:

l
Upgrading the entire system with dual-OMU Both the OMU software and the host software need to be upgraded. The remote upgrade is adopted.
Upgrading only the OMU software with dual-OMU The OMU software is upgraded through cold patches. The remote upgrade is not adopted. Upgrading only the SMU software with dual-OMU The host software is upgraded through hot patches. The remote upgrade is not adopted. Upgrading the entire system with single-OMU Both the OMU software and the host software need to be upgraded. The remote upgrade is adopted.
Upgrading only the OMU software with single-OMU The OMU software is upgraded through cold patches. The remote upgrade is not adopted. Upgrading the SMU software with single-OMU The host software is upgraded through hot patches. The remote upgrade is not adopted.
NOTE
Dual-OMU indicates the active and standby GOMUs; single-OMU indicates the GOMU or the GBAM.
42.3.2 Remote Upgrade Procedures

This describes the remote upgrade procedures, which involve dual-OMU upgrade and singleOMU upgrade. Figure 42-2 shows the procedure for upgrading the entire system in dual-OMU mode.
42-6
Issue 02 (2008-06-30)
42 Remote Upgrade
Figure 42-2 Procedure for upgrading the entire system in dual-OMU mode
Start Select the upgrade version
Prepare the software required for the upgrade Back up the old configuration data file Generate the new configuration data file
Get ready for remote upgrade
Download the software
Download the data of the new version Create network element object Load the software and BIOS
Upload the software
Upload the software and data
Execute upgrade
Upload the data Perform remote upgrade
Load and activate license
Submit upgrade (rollback)
End
Complete the upgrade
The procedure for upgrading the entire system in dual-OMU mode involves the following phases: 1. Preparation This phase involves preparing the software required for the upgrade, backing up the old configuration data file, and generating the new configuration data file. 2. Execution This phase involves loading software and BIOS, executing upgrade, and loading and activating license among which executing upgrade is further divided into three operations by sequence, namely, preparing the configuration data, installing the OMU software, and activating the SMU software. 3. Postprocessing This phase involves either submitting upgrade or upgrade rollback according to the upgrade result.
l
Submitting upgrade This involves installing the OMU software (installing the standby OMU software) and enabling the backup and switchover.
Upgrade rollback
Issue 02 (2008-06-30)
42 Remote Upgrade
This involves rolling back the host software, rolling back the active OMU software, and activating the host software. The procedure for upgrading the entire system in single-OMU mode is the same as the procedure for upgrading the entire system in dual-OMU mode. In the procedure for upgrading the entire system in single-OMU mode, the standby OMU software is not upgraded.
42.4 Implementation
This describes how to get ready for the upgrade, create an NE object, upload software and data, and perform upgrade. 42.4.1 Precautions for Remote Upgrade This describes the precautions for remote upgrade. 42.4.2 Getting Ready for Remote Upgrade Before the remote upgrade, you need to prepare related software, back up the old data, generate the new configuration file, and install the mediation layer of the M2000 for the upgrade version. 42.4.3 Creating a Network Element Object This describes how to create a BSC network element object through the M2000 Client if no network element object is on the M2000 Client. 42.4.4 Uploading the Software and Data This describes how to upload the upgrade software and data file of the BSC from the M2000 Client to the M2000 server. 42.4.5 Performing Remote Upgrade This describes the operations involved in remote upgrade, including selecting the upgrade version, downloading software and data, loading software and BIOS, performing upgrade, upgrade submission, and upgrade rollback.
42.4.1 Precautions for Remote Upgrade

This describes the precautions for remote upgrade. The precautions for remote upgrade are as follows:
l
In a network with the bandwidth as 10 Mbit/s, the time taken to download the OMU upgrade software package cannot exceed 30 seconds. In upgrading the entire system in dual-OMU mode, the period of service interruption cannot exceed seven minutes. The time taken to upgrade the software on the active or standby OMU cannot exceed five minutes. If the upgrade of the OMU software fails, the rollback time cannot exceed five minutes. The time taken to upgrade the entire system with dual-OMU cannot exceed 30 minutes. If the upgrade of the entire system with dual-OMU fails, the rollback time cannot exceed 30 minutes.
l l l
42.4.2 Getting Ready for Remote Upgrade

Before the remote upgrade, you need to prepare related software, back up the old data, generate the new configuration file, and install the mediation layer of the M2000 for the upgrade version.
42 Remote Upgrade
Procedure
Step 1 Prepare the software required for the upgrade. 1. 2. Visit the website http://support.huawei.com. On the TECHNICAL SUPPORT page, search the software at Software > Version Software > Wireless Product Line > GSM-BSS > GSM-BSC6000 > HUAWEI BSC6000 > HUAWEI BSC6000 V900R008. On the right of the web page, click the NE version link in the Version Name or Version column. On the displayed web page, download the corresponding software version in the Software area. After downloading, open the compressed package to obtain the files needed in remote upgrade, as shown in Table 42-3. Table 42-3 List of downloaded files File Name boardfile.9.8.x.yy.zip omu-9.8.x-yy.i586.rpm verpkg.xml Function Compressed host software package, software used to upgrade the boards Installation package of the OMU software, software used to upgrade the OMU Version configuration information file of the upgrade package, used to verify the board software and OMU software during the upgrade Configuration file for remote upgrade Version configuration information of remote upgrade, used to verify the preceding four files when the upgrade package is uploaded to the M2000 server
3. 4. 5.
upgradecfg.xml vercfg.xml
6.
Download the corresponding release notes in the Document area.
Step 2 Back up the configuration data file running on the BSC before upgrade. Log in to the old version BSC6000 Local Maintenance Terminal. Choose Back Up Local Data from the Configuration menu and specify the name for the backup file in the displayed Save dialog box. Then, click Execute to start the backup. For the detailed operations, refer to Backing Up Sever Data. Step 3 Generate the configuration data file of the new version. 1. Log in to the new version BSC6000 Local Maintenance Terminal offline.
NOTE
Before logging in to the new version BSC6000 Local Maintenance Terminal offline, check whether the GBAM or GOMU mode is adopted after upgrade and select a correct login mode.
2.
Load the configuration data. In the displayed Open dialog box, select the old version configuration data file backed up in Step 2. At the prompt of The binfile's version(BSC6000DATAV900R008C01) is not
Issue 02 (2008-06-30)
42-9
42 Remote Upgrade
compatible with LMT, upgrade now? , click Yes to upgrade the data. After a period, the system prompts that the upgrade succeeds. Click OK to complete the upgrade of the configuration data file. For the detailed operations, refer to Loading Other Configuration Data. 3. Back up LMT local data. The BSC6000 Local Maintenance Terminal verifies the data globally. For the detailed operations, refer to Backing Up LMT Local Data.
l
If the verification fails, data cannot be backed up. The error information is displayed. You need to manually modify the data to meet the checking rules. If the verification succeeds, select the path for backing up the file and input the file name. By default, the file is saved to the directory HW LMT\BSC6000 \BSC6000V900R008C01\BackupCfgData.
CAUTION
l l
The data file of the new version must be saved as lmt.dat for use in future upgrade. If the default value of the parameter changes, manually modify the parameters as required.
Step 4 Install the mediation layer of the M2000 for the upgrade version. For detailed operations, refer to M2000 Commissioning Guide. ----End
42.4.3 Creating a Network Element Object

This describes how to create a BSC network element object through the M2000 Client if no network element object is on the M2000 Client.
Procedure
Step 1 Start the M2000 client and choose Topo > Main Topology on the menu. Then, right-click in the right pane on the Main Topology tab page and select New > Create Topo Object from the shortcut menu. Step 2 After Create Topo Object is selected, a dialog box is displayed, as shown in Figure 42-3. In the left Management Tree pane, select the BSC6000. Then, in the right pane, configure the relevant parameters such as the IP Address and Name.
42-10
Issue 02 (2008-06-30)
42 Remote Upgrade
Figure 42-3 Create Topo Object dialog box
----End
42.4.4 Uploading the Software and Data

This describes how to upload the upgrade software and data file of the BSC from the M2000 Client to the M2000 server.
Prerequisite
l
Copy the files listed in Table 42-3 to the PC installed with the M2000 Client, such as to the path E:\upgradepkg. Copy the new version configuration files with the extension .dat to the PC installed with the M2000 Client, such as to the path E:\data.
Procedure
Step 1 Upload the software. 1. On the M2000 Client menu, choose Software > File Transfer Wizard. A dialog box is displayed, as shown in Figure 42-4.
Issue 02 (2008-06-30)
42-11
42 Remote Upgrade
Figure 42-4 Selecting general parameters
2.
Select From GUI To Server from the Direction drop-down list and select BSC6000 > Software from the Server Path list box. Then, click Next. A dialog box is displayed, as shown in Figure 42-5.
Figure 42-5 Selecting the software
42-12
Issue 02 (2008-06-30)
42 Remote Upgrade
3.
Select the directory in which the file to be uploaded is saved. Then, click Finish to start software uploading. On the M2000 Client menu, choose Software > File Transfer Wizard. A dialog box is displayed, as shown in Figure 42-6.
Step 2 Upload the data. 1.
Figure 42-6 Selecting general parameters
2.
In the Direction drop-down list, select From GUI To Server. Then, in the Server Path list box, select BSC6000 > Data > NE name. Click Next. A dialog box is displayed, as shown in Figure 42-5. Select the directory in which the file to be uploaded is saved. Then, click Finish to start data uploading.
3.
----End
42.4.5 Performing Remote Upgrade

This describes the operations involved in remote upgrade, including selecting the upgrade version, downloading software and data, loading software and BIOS, performing upgrade, upgrade submission, and upgrade rollback.
Context
CAUTION
Do not modify the time of the GBAM/GOMU during the upgrade; otherwise, upgrade may fail due to timeout.
Issue 02 (2008-06-30)
42-13
42 Remote Upgrade
Procedure
Step 1 On the M2000 Client menu, choose Software > NE Upgrade Wizard > Upgrade BSC6000. In the displayed dialog box, select the related NE. Step 2 Click OK. A dialog box is displayed, as shown in Figure 42-7. Then, select the upgrade version. Figure 42-7 Selecting the upgrade version
Step 3 Click Next to start the upgrade, and observe the process and result of each step. Figure 42-8 shows the upgrade wizard.
42-14
Issue 02 (2008-06-30)
42 Remote Upgrade
Figure 42-8 Upgrade wizard
The upgrade wizard involves the following steps: 1. 2. Select the upgrade version. Select the correct upgrade version. Download software. When downloading the software, take the following into account:
l
If the software package of the upgrade version is already downloaded successfully, click Skip. If the previous upgrade process is not closed because the upgrade is not complete or an exception occurs to the upgrade, the software download may fail. In this case, manual interference is required.
3. 4.
Download the new version data. Skip this step if the new version data has been successfully downloaded. Load the software and BIOS. In the download process, the information such as the total number of modules, the number of successfully executed modules, and the number of running modules is displayed. If failure occurs to the boards after the download is complete, click Next to repeat the operation.
Issue 02 (2008-06-30)
42-15
42 Remote Upgrade
NOTE
The incremental loading feature is applied to the system; thus, the software and BIOS are re-loaded only to the boards whose loading fails. If the loading failure occurs to the board for several times, you need to determine the cause for the failure and take actions accordingly.
5.
Execute the upgrade. This step involves upgrading the OMU software and activating the SMU software. You can view the process and result of the upgrade on the upgrade wizard.
l
Upgrade the OMU software. The OMU software is upgraded automatically without user confirmation. The following may occur in the upgrade:
It takes some time for the M2000 to set up a connection to the new version NE; thus, a connection with NE failure prompt may occur in the upgrade process. This is normal. Wait for a moment, and then click Retry to complete the upgrade. If error occurs in the upgrade process, a start up omudaemon failed prompt may occur. The following options are available:
If you click Retry, the system executes the upgrade from the point where the error occurs. If you click Restart, the system executes the upgrade again from the beginning. If you click RollBack, the system rolls back to the version before the upgrade. If upgrade is needed after rollback, start the BSC6000 upgrade wizard again to execute the upgrade from Step 2.
NOTE
Huawei recommends that you determine the cause for the upgrade failure. After the fault is rectified, click Retry. If retry fails for several times, click RollBack to roll back the system to the previous version.
l
Activate the SMU software. Activating the SMU software interrupts the service. You need to click Continue for confirmation to execute the upgrade. The OMU software is upgraded to the new version; however, the SMU software of the original version is running on the board. To reduce the message interaction between the OMU software of the new version and the SMU software of the original version, click Continue as soon as possible to upgrade the SMU software. If the system is abnormal or the upgrade needs to be terminated, click RollBack to roll back the system to the original version. If upgrade is needed after rollback, start the BSC6000 upgrade wizard again to execute the upgrade from Step 2.
6.
Load and activate the license. a. b. Copy the license file to the PC installed with the M2000 Client, such as to the path E:\license. Upload the license file by referring to 42.4.4 Uploading the Software and Data. 1) 2) On the M2000 Client menu, choose Software > File Transfer Wizard. In the displayed dialog box, select From GUI to Server from the Direction dropdown list. In the Server Path list box, select BSC6000 > License > NE name and then click Next. Select the path to save the license, for example, E:\license. Then, click Finish to start uploading the license.
3)
42-16
42 Remote Upgrade
7.
Submit the upgrade. In this step, the active OMU software and SMU software are upgraded to the new version. If you do not need to perform any further operations on the M2000 Client, pause the upgrade at this step for the new version software to run for a certain period. When you ensure that the software of the new version is running normally, submit the upgrade.
l
Select Submit Upgrade Immediately and click Next to submit the upgrade. The entire upgrade progress is complete. If you select Submit Upgrade Lately, you need to click Finish to close the upgrade wizard. If you start the upgrade wizard again when the new version software has run for some time, the prompt "This NE has the upgrade process, the upgrade version is BSC6000V900R008C01. Please continue the old upgrade." is displayed. Click Continue to return to the start of this step.
If the new version software does not run normally, select RollBack. Click Next, the system is thus rolled back to the previous version.
CAUTION
In the dual-OMU entire system upgrade, select Upgrade Submission to complete the upgrade of the OMU software. If the standby GOMU is faulty, this step fails. In this case, you need to determine the cause for the failure, rectify the fault, and perform local upgrade accordingly. 8. Roll back the upgrade. The following may occur in the upgrade rollback:
l
It takes some time for the M2000 Client to set up a connection to the old version NE; thus, a connection with NE failure prompt may occur in the rollback process. This is normal. Wait for a moment, and then click Retry to complete the rollback. If the rollback fails, a dialog box is displayed for you to choose to Retry or Quit Upgrade.

If you click Retry, the upgrade rollback is executed again. If the upgrade rollback fails after retry for several times, click Quit Upgrade and perform manual intervention on the local end. Determine the cause of the failure and rectify the fault accordingly. Then, perform upgrade rollback according to the local upgrade rollback wizard.
9.
Complete the upgrade.
----End

None.
Alarms
None
42 Remote Upgrade
Counters
None
42.6 References
None
42-18
Issue 02 (2008-06-30)
43 APS
43
About This Chapter
APS
43.1 Overview This provides the definition and describes the purposes of Automatic Protection Switching (APS). When the BSC is connected to the optical transmission equipment and the working channel is faulty, the BSC negotiates with the optical transmission equipment on the protection channel through the APS to switch traffic signals onto the protection channel. 43.2 Availability This lists the NEs, software versions, and other support required for the implementation of APS. 43.3 Technical Description This describes the technical aspects of APS. The BSC implements the standard APS 1+1 protect mode on the optical port of the OIUa (providing the A/Ater/Abis/Pb interface). Therefore, the OIUa can be connected to the transmission equipment, network equipment, or BTS in compliance with the APS 1+1 protect mode to implement backup protection to optical transmission links. 43.4 Implementation This describes how to configure APS or APS (based on MML), verify APS, and deactivate APS. 43.5 Maintenance Information This lists the alarms and performance counters related to APS. 43.6 References
Issue 02 (2008-06-30)
43-1
43 APS
43.1 Overview
This provides the definition and describes the purposes of Automatic Protection Switching (APS). When the BSC is connected to the optical transmission equipment and the working channel is faulty, the BSC negotiates with the optical transmission equipment on the protection channel through the APS to switch traffic signals onto the protection channel.
Definition
APS is a type of SDH multiplex section protection switching protocol based on the G.841 standard of the ITU-T. APS applies to optical port backup. Because the optical ports of the BSC is bound up with the OIUa boards, you must switch over the OIUa boards before you switch over optical ports. Therefore, APS actually applies to board backup. The APS entities of the BSC are a pair of active and standby boards. The optical port corresponding to the small slot number is the working channel, and that corresponding to the large slot number is the protection channel. The working and protection channels are static, and thus they do not change according to the active/standby state of a board.
Purposes
APS improves the stability and maintainability of the entire system and enhances the reliability of BSC links. APS also ensures the real-time lossless protection switching of active and standby channels and reduces the risk of service interruption on links. APS applies to various interconnection scenarios. For example, the A interface is used to connect the NSS or equipment of other vendors, and the Abis interface is used to connect the optical transceiver or other equipment. This brings numerous benefits to network operators.
Terms
Terms Switch Bridge K byte Definition The action of selecting traffic from the protection channel not from the working channel. The action of transmitting identical traffic on the working and protection channels simultaneously. A general designation of K1 byte and K2 byte in the SDH. K1 byte and K2 byte are used to transmit APS signaling. In K1 byte, the first four bits indicate the switch request, and the second four bits indicate the request channel number. In K2 byte, bits 1 to 4 indicate the bridge channel number, bit 5 indicates the type code, and bits 6 to 8 indicate the status code. A switch event that is recorded in K byte format and to which the APS request is converted. The switch mode is classified into unidirectional mode and bidirectional mode.
K byte event Switch mode
43-2
43 APS
Terms recover mode Signal degrade Signal failure
Definition The recover mode is classified into revertive mode and non-revertive mode. The link has bit errors. The quality of signals is unstable. The signals on the RX end of the link are lost. The local communication is disrupted.

Acronyms and Abbreviations BSC APS MSP LOP FS MS EXERS SF SD WTR DNR NR RR GOIU SDH SONET CFG DEV HRD MS-AIS MS-RDI Full Spelling Base Station Controller Automatic Protection Switching Multiplex Section Protection Lockout of Protection Force Switch Manual Switch Exercise Switch Signal Fail Signal Degrade Wait To Restore Do not Revert No Request Reverse Request GSM Optical Interface Unit Synchronous Digital Hierarchy Synchronous Optical Network Configure Device Hardware Multiplex Section Alarm Indication signal Multiplex Section Remote Defect Indication
Issue 02 (2008-06-30)
43-3
43 APS
43.2 Availability
This lists the NEs, software versions, and other support required for the implementation of APS.
NEs Involved
Table 43-1 lists the NEs involved in APS in external PCU mode. Table 43-1 NEs involved in APS MS
NOTE
BTS
BS C
PCU
MSC
MGW
SGSN
GGSN
HLR
Table 43-2 lists the NEs involved in APS in built-in PCU mode. Table 43-2 NEs involved in APS MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 43-3 lists the versions of GBSS products that support APS in external PCU mode. Table 43-3 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Table 43-4 lists the versions of GBSS products that support APS in built-in PCU mode.
43-4
Issue 02 (2008-06-30)
43 APS
Table 43-4 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
APS must meet the following requirements:
l l
APS applies only to the optical port protection switching of the OIUa. The interconnected optical ports must be in the same mode. The optical port in SDH mode cannot interconnect that in SONET mode. The BSC supports only the APS 1+1 protect mode. The configuration of the parameters Protect mode, Switch mode and recover mode at both ends must be consistent. Otherwise, the protocol processing may be affected. The optical fibers at both ends must be connected properly. The protection channel at the local end must be connected to that at the peer end.
l l

This describes the technical aspects of APS. The BSC implements the standard APS 1+1 protect mode on the optical port of the OIUa (providing the A/Ater/Abis/Pb interface). Therefore, the OIUa can be connected to the transmission equipment, network equipment, or BTS in compliance with the APS 1+1 protect mode to implement backup protection to optical transmission links. Before APS is performed, the traffic data is transmitted and received on the working channel. If a fault occurs on the working channel (for example, an SF alarm is generated), the BSC negotiates with the transmission equipment on the protection channel through the APS to switch traffic data onto the protection channel. The protection switching for transmission links is complete, thus improving the reliability and stability of BSC transmission links and reducing the risk of communication service interruption. 43.3.1 APS Mode This describes the APS mode. The APS mode is classified into 1+1 protect mode and 1:N protect mode. 43.3.2 Prerequisites for APS This lists the three prerequisites for APS. 43.3.3 APS Policy This describes the priorities and states of APS. When the BSC detects SF and SD alarms, K byte reports, or external commands on working channel or protection channel, the BSC selects the highest priority input based on the current status of the local end and performs state transition and switching as required. 43.3.4 APS Categories This describes the APS policy. APS may be triggered by fault alarms, external commands, K byte requests, and APS processing equipment. 43.3.5 APS Process This describes the APS process in unidirectional switch mode and bidirectional switch mode.
43 APS
43.3.6 Other Features of APS This describes other features of APS.
43.3.1 APS Mode

This describes the APS mode. The APS mode is classified into 1+1 protect mode and 1:N protect mode. The APS mode is classified into the following two types:
l
1+1 protect mode. In 1+1 protect mode, two identical traffic signals are transmitted at one end, and one better traffic signal is received at the other end.
1:N protect mode. In 1:N protect mode, N working channels share the same protection channel. Each working channel can preempt the protection channel according to the APS.
According to the Switch mode and recover mode, the 1+1 protect mode can be classified into the following types:
l
Unidirectional mode. The local end performs switching based on the link quality without negotiating with the peer end.
Bidirectional mode. Before switchover is performed, the two ends negotiate. After the negotiation is successful, the two ends switch over at the same time.
Revertive mode. In revertive mode, traffic signals can be switched to the working channel when the working channel is recovered or the manual switch command is run.
Non-revertive mode. In non-revertive mode, though the working channel is recovered, traffic signals are still transmitted on the protection channel.
43.3.2 Prerequisites for APS

This lists the three prerequisites for APS. The prerequisites for APS are as follows:
l l l
SF and SD alarms of optical ports and board failures K byte event reported by the peer end External commands (The APS triggered by external commands consists of lockout of protection, force switch, and exercise switch.)
43.3.3 APS Policy

This describes the priorities and states of APS. When the BSC detects SF and SD alarms, K byte reports, or external commands on working channel or protection channel, the BSC selects the highest priority input based on the current status of the local end and performs state transition and switching as required. Figure 43-1 shows the APS priority in a descending order.
43 APS
Figure 43-1 APS priorities
Manual switch Wait-to restore Exercise Reverse request Do not revert No request
APS has the following states:

l
Idle state (IDLE STATE). APS is in the IDLE state when no bridge requests are generated or detected. Generally, the initial state of APS is IDLE.
Switching state (SWITCH STATE). When a bridge request is initiated or terminated at one end, the end is in the SWITCH state. Wait-to-restore state (WTR STATE). When one end is in the SWITCH state, if SF and SD clear alarms are detected, or there is no request in the K bytes transmitted by the peer end, or an externally initiated switch clearing command is received, the state is changed from SWITCH to WTR.
Figure 43-2 shows the process of APS state transition.
Issue 02 (2008-06-30)
43-7
43 APS
Figure 43-2 Process of APS state transition

Detect SF or SD signals Receive the K byte switch request Receive the external switch request
IDLE STATE SWITCH STATE
Receive the external switch clearing
Receive the no request codes from the peer end T2 timeout
Detect the SF or SD signal clearing Receive the K byte switch request Receive the external switch request Detect the SF or SD signal clearing Receive the K byte switch no request Receive the external switch clearing
WTR STATE
43.3.4 APS Categories

This describes the APS policy. APS may be triggered by fault alarms, external commands, K byte requests, and APS processing equipment.
APS Triggered by Fault Alarms

The BSC handles fault alarms according to the priorities: no alarm, SD alarm, SF alarm, and faulty in ascending order. The optical port with low alarm priority is the one for the working channel. When the alarm priority of the optical port for the working channel is higher than that of the optical port for the protection channel, APS is performed. For example, when the optical port for the working channel generates a critical alarm (SF alarm) and the alarm in the optical port for the protection channel is cleared, the optical ports for the working and protection channels perform APS and the OIUa with the optical port for the working channel is reset. In addition, when the optical port for the working channel and the optical port for the protection channel generate alarms of the same severity simultaneously and or the alarms on the optical port for the protection channel are cleared earlier, the optical port for the protection channel may perform APS.
APS Triggered by External Commands

When maintenance personnel issue external switch commands, APS is performed according to the command function defined in the protocol. The BSC supports the following external APS commands:
l l
Lockout of protection (LOP) Force switch (FS)

43-8

l l
43 APS
Exercise switch (EXERS) Switch clearing (CLEAR)
The BSC does not support saving external commands. That is, the BSC receives the K byte request or SF/SD request after external commands are issued. When the priority of the K byte request or SF/SD request is higher than that of external commands, the external commands are preempted by the K byte request or SF/SD request. After the K byte request or SF/SD request is cleared, the BSC does not continue to run the external commands.
APS Triggered by the K Byte Request

NOTE
APS triggered by the K byte request applies only to the bidirectional switch mode.
K1 and K2 bytes received on the protection channel from the peer equipment are resolved and processed in compliance with the protocol.
l
K1 byte. In K1 byte, the first four bits indicate the switch request, and the second four bits indicate the request channel number, as described in Table 43-5. Table 43-5 Composition of K1 byte bit1 bit2 bit3 bit4 bit5 bit6 bit7 bit8
Switch request
Request channel number
Table 43-6 describes the first four bits in K1 byte. Table 43-6 Description of the first four bits in K1 byte Bits 1111 1110 1101 1100 1011 1010 1000 0110 0100 0010 0001
Issue 02 (2008-06-30)
State or External Command Lockout of protection Force switch Signal fail high priority Signal fail low priority Signal degrade high priority Signal degrade low priority Manual switch Wait to restore Exercise switch Reverse request Do not revert
PRI 0000 indicates the lowest priority, and 1111 indicates the highest priority. The priorities ascend from 0000 to 1111.
43-9
43 APS
Bits 0000
State or External Command No request
PRI
Values of the second four bits in K1 byte: 0 indicates the protection channel number, 1 to 14 indicate the working channel number, and 15 indicates the additional transmission channel.
NOTE
Because APS fulfills only 1+1 backup in the BSC, the working channel number is 1 permanently.
l
K2 byte. In K2 byte, bits 1 to 4 indicate the bridge channel number, bit 5 indicates the type, and bits 6 to 8 indicate the status code, as described in Table 43-7. Table 43-7 Composition of K2 byte bit1 bit2 bit3 bit4 bit5 Status code bit6 bit7 bit8
Bridge channel number
Status code
Values of the first four bits in K2 byte: 0 indicates the protection channel number, 1 to 14 indicate the working channel number, and 15 indicates the additional transmission channel. Values of bit 5 in K2 byte: 0 indicates 1+1 protect mode, and 1 indicates 1:N protect mode. Values of the last three bits in K2 byte: The bidirectional switch mode and unidirectional switch mode are optional in the SDH mode, as described in Table 43-8. Table 43-8 K2 byte status code bit6-bit8 111 110 101 100 Miscellaneous Meaning AIS Alarm RDI alarm Bidirectional switch mode Unidirectional switch mode Reserved
APS Triggered by the APS Processing Equipment

If the OIUa in which the working channel resides is faulty and services are affected, the active/ standby switchover is required. APS is to perform the switching function of the equipment subsystem. The switching decision is completed by the BSC. When the equipment is faulty, the
43 APS
BSC performs switching decision. After the decision is complete, if the switching is required, the switching interface of the equipment is invoked to perform APS and the reset type is recorded. APS is triggered through the notification of the equipment or the regular health check. Except hardware failures and the existing board switchover function, the equipment subsystem can also trigger APS. After APS backup is added, the 5-minute switching protection restriction of the equipment is cancelled in APS.
43.3.5 APS Process

This describes the APS process in unidirectional switch mode and bidirectional switch mode.
Unidirectional Switch Mode

The process of the APS in 1+1 unidirectional mode is simple. The local end does not need to exchange K bytes with the peer end. Switching decision is made according to the conditions of only the local end.
Bidirectional Switch Mode

Figure 43-3 shows the process of APS in bidirectional switch mode. Figure 43-3 Bidirectional switch mode
B Working channel Protection channel
1. 2. 3. 4.
A transmits switch request K bytes on the original protection channel to B. The state of the A controller is switched to the switching state. Upon receipt of K bytes, B performs a bridge and transmits a reverse request to A. Upon receipt of reverse request K bytes from B, A transmits switching request K bytes to B and performs APS. Upon receipt switching request K bytes from A, B performs APS. APS in 1+1 bidirectional mode is complete.
NOTE
As shown in Figure 43-3, equipment A is connected to equipment B in 1+1 protect mode. The Switch mode is set to Bidirectional Switch, and the recover mode is set to Revertive. If the optical cable between equipment A and equipment B is faulty,bidirectional switch can be performed.
Issue 02 (2008-06-30)
43-11
43 APS
43.3.6 Other Features of APS

This describes other features of APS.
Non-Revertive Processing
Only APS triggered by SF or SD alarms can enter the DNR state. After the external command is cleared (the working channel is forcibly switched to the protection channel), APS enters the IDLE state.
WTR Time Setting

Generally, the WTR time, that is recover time(s) must be set to greater than 2 minutes. If the WTR time is too short, frequent switching may be caused when intermittent link failures occur.
NOTE
The WTR time of the BSC is from 30s to 60000s. The default WTR time is 600s.
l
Bidirectional revertive mode When SF or SD alarms are cleared, the end that detects SF or SD alarms starts the WTR timer and transmits WTR request K bytes to the peer end. At this moment, the peer end also enters the WTR state but does not start the WTR timer. When the WTR timer expires, both ends return to the IDLE state.
1+1 unidirectional revertive mode Only the end with SF or SD alarms cleared enters the WTR state. 1+1 non-revertive mode When SF or SD alarms are cleared, both ends enter the DNR state without the WTR process.
Manual Clearing of WTR

There is no command for clearing WTR. Therefore, only the high priority request can be used to preempt it.
Clearing of External Commands

The CLEAR command in the BSC can be used for clearing external commands.
NOTE
In all equipment, when a higher priority request preempts the external command request, the ongoing external command is cleared.
APS Alarm
When the highest priority switch request changes, the BSC clear the original alarm and reports a new alarm.
K1K2 Mismatch
In 1+1 two ends mode, when the received first four bites of K2 byte are inconsistent with the sent latter four bits of K1 byte, the timer for K1K2 mismatch is started. When the timer expires, the K1K2 mismatch alarm is generated. If the received first four bits of K2 byte are consistent
43 APS
with the sent latter four bits of K1 byte, the alarm is cleared. In 1+1 one end mode, there is no K1K2 mismatch.
K2 Mismatch
Whatever the APS configuration mode is, if the received fifth bit of K2 byte is inconsistent with the sent one, the K2 mismatch alarm is generated. If the received fifth bit of K2 byte is consistent with the sent one, the alarm is cleared.
NOTE
When a K2 mismatch occurs, the APS management module stops the processing task. When a K1K2 mismatch occurs, the APS management module continues with the processing task.
Bidirectional/Unidirectional Mismatch Alarm

The bidirectional/unidirectional switch modes at both ends of the APS protection section are inconsistent. One end is 1+1 unidirectional switch mode, and the other end is 1+1 bidirectional switch mode. If the bidirectional mode is configured at the local end and the unidirectional mode is configured at the peer end, the APS management module changes the switch mode at the local end to the unidirectional mode. If the switch mode at the peer end is changed to the bidirectional mode, the BSC changes the switch mode at the local end to the bidirectional mode.
Processing with 10s Delay of SD and SF Alarms

When the optical fiber is recovered or the laser is started, the optical port cannot enter the WTR or DNR state immediately because in the OIUa the SD and SF alarms are delayed for 10s. Ten seconds after the SD or SF alarm is cleared, the OIUa reports the SD or SF clear alarm.
43.4 Implementation
This describes how to configure APS or APS (based on MML), verify APS, and deactivate APS. 43.4.1 Typical Network Topologies over Optical Ports This describes the typical network topologies over optical ports. 43.4.2 Configuring APS This describes how to configure APS on the BSC6000 Local Maintenance Terminal. 43.4.3 Verifying APS This describes how to verify APS on the Local Maintenance Terminal. 43.4.4 Deactivating APS This describes how to deactivate APS on the BSC6000 Local Maintenance Terminal.
43.4.1 Typical Network Topologies over Optical Ports

This describes the typical network topologies over optical ports. The typical network topologies over optical ports are as follows:
l
Connecting to the peer end through an optical fiber, as shown in Figure 43-4
Issue 02 (2008-06-30)
43 APS
Figure 43-4 Network topology with the BSC directly connected to the MSC
BTS
or Optical cable
BSC6000
l
MSC
Connecting to the peer end through an optical transceiver, as shown in Figure 43-5 Figure 43-5 Network topology with the BSC connected to the MSC through an optical transceiver
Optical transceiver or Optical cable Optical cable
BTS
BSC6000
l
MSC
Connecting to an optical transceiver and then to the peer end through the converted electrical port, as shown in Figure 43-6 Figure 43-6 Network topology with the BSC connected to the MSC through the electrical port converted by an optical transceiver
Optical transceiver or Optical cable E1 coaxial cable
BTS
BSC6000
MSC
43.4.2 Configuring APS

This describes how to configure APS on the BSC6000 Local Maintenance Terminal.
43 APS
Prerequisite
The principles and requirements for configuring APS are as follows:
l
The APS attributes at the local and peer ends must be consistent. The default configuration is recommended for the BSC. If the configurations of APS attributes at both ends are inconsistent, you must make modification. The interconnected optical ports must be in the same mode. The optical port in SDH mode cannot interconnect that in SONET mode. APS must be enabled at both ends. Check whether the optical cable is connected properly. The protection channel at the local end must be properly connected to that at the peer end. Otherwise, protocol exchange cannot be performed. The protect modes at both ends must be consistent. The BSC supports only the 1+1 protect mode. The configuration parameters at both ends must be consistent. For example, the bidirectional mode and the revertive/non-revertive mode at both ends must be consistent. Otherwise, the protocol switching may be affected.
l l
Context
The interfaces that can be configured with APS are as follows:
l
In BM/TC separated (built-in PCU) mode, A (GOIUA), Abis (GOIUB), Ater (GOIUT), and Pb (GOIUP) interfaces can be configured. In BM/TC combined (external PCU) mode, A (GOIUA), Abis (GOIUB), and Pb (GOIUP) interfaces can be configured. In A over IP (external PCU) mode, Abis (GOIUB) and Pb (GOIUP) interfaces can be configured. In BM/TC separated (built-in PCU) mode, A (GOIUA), Abis (GOIUB), and Ater (GOIUT) interfaces can be configured. In BM/TC combined (built-in PCU) mode, A (GOIUA) and Abis (GOIUB) interfaces can be configured.
NOTE
This document takes the A interface (GOIUA) in BM/TC separated (external PCU) mode as an example to illustrate how to configure APS. When you add active/standby GOIUB, GOIUP, or GOIUT, the APS is automatically configured.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, click the BSC Device Panel tab, and then select the number of the cabinet where the GTCS is located from the Current Cabinet dropdown list. Step 2 Right-click empty slots 18 to 25 in the subrack, and then choose Add Board from the shortcut menu. The Add Board dialog box is displayed. Step 3 Set the FuncType to A interface board and Board Type to GOIUA, select Work Mode, and select Active/standby Mode and Support APS. Click Finish. The GOIUA is configured with APS.
43 APS
NOTE
If you do not select Support APS, the 1+1 backup mode of DEV is used by default.
Step 4 Right-click the GOIUA, and then choose Configure Board Attributes. The dialog box for configuring Board Attributes and CPU Attributes (Configure Board Attributes) is displayed. Step 5 Click Next. The Sub Board Attributes (Configure Board Attributes) dialog box is displayed. Select Support APS.
NOTE
If you do not select Support APS, the APS cannot be configured.
Step 6 Click Next. The Port Attributes (Configure Board Attributes) dialog box is displayed.
NOTE
l l l
The configuration of J0 and J1 related parameters must be consistent with the configuration on the NSS side. The attributes of the optical sub-board and optical port at the local end must be consistent with those at the peer end. To query the parameters of the optical sub-board and optical port, refer to Querying the Status of an Interface Board Port.
Step 7 Click Next. The Aps Attributes (Configure Board Attributes) dialog box is displayed, as shown in Figure 43-7. Figure 43-7 Configuring APS attributes
Step 8 In Figure 43-7, set the Protect mode, Switch mode, recover mode, recover time(s), SD Enable, K2 Mode, and SFSD Priority. Click Finish. Configuring APS is complete. ----End
43-16
Issue 02 (2008-06-30)
43 APS
43.4.3 Verifying APS

This describes how to verify APS on the Local Maintenance Terminal.
Procedure
Step 1 Ensure that the configuration parameters and interconnection modes at the local and peer ends are correct. Step 2 On the Local Maintenance Terminal, enter the SET APSCMD command. 1. 2. Set the Subrack No and Slot No of the GOIUA and set the APS Command to EXERS (Exercise switch). Run the command. The operation is complete.
Step 3 On the Local Maintenance Terminal, enter the DSP APS command. 1. 2. Set the Subrack No and Slot No of the GOIUA. Run the command. If the switchover request is forced switchover and protocol status is switchover status, you can infer that the switchover is successful. Verifying APS is complete.
----End
43.4.4 Deactivating APS

This describes how to deactivate APS on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC Device Panel tab page of the BSC6000 Local Maintenance Terminal, select the GEIUA of which the APS is to be deactivated. Right-click the GEIUA, and then select Configure Board Attributes. The dialog box for configuring Board Attributes and PCU Attributes (Configure Board Attributes) is displayed. Step 2 Click Next. The Sub Board Attributes (Configure Board Attributes) dialog box is displayed. Step 3 Click the Support APS list box to deselect it. Click Next. The Port Attributes (Configure Board Attributes) dialog box is displayed. Step 4 Click Finish. Deactivating APS is complete. ----End

This lists the alarms and performance counters related to APS.
Alarms
Table 43-9 lists the alarms related to APS.
43 APS
Table 43-9 Alarms related to APS Alarm ID 21581 21582 21583 21584 21585 21586 Alarm Name APS protocol start alarm APS protocol stop alarm APS protocol switch alarm APS protection section K1/K2 mismatch alarm APS protection section K2 mismatch alarm APS protection section bidirectional/unidirectional mismatch alarm
Counters
None
43.6 References
l
ITU-T Recommendation G.784 (1994), Synchronous Digital Hierarchy (SDH) management. ITU-T Recommendation G.803 (1997), Architectures of transport networks based on the Synchronous Digital Hierarchy (SDH). ITU-T Recommendation G.841 (1998), Types and characteristics of SDH network protection architectures.
43-18
Issue 02 (2008-06-30)
44 BSC Local Switching
44
About This Chapter
BSC Local Switching
44.1 Overview This provides the definition and describes the purposes of BSC local switching. 44.2 Availability This lists the NEs, software versions, and other support required for the implementation of BSC local switching. 44.3 Impact This describes the impact of BSC local switching on system performance and other features. 44.4 Technical Description This describes the technical aspects of BSC local switching, consisting of start, recovery, and handover of BSC local switching calls. 44.5 Implementation This describes how to configure and verify BSC local switching. 44.6 Maintenance Information This lists the alarms and performance counters related to BSC local switching. 44.7 References None.
Issue 02 (2008-06-30)
44-1
44.1 Overview
This provides the definition and describes the purposes of BSC local switching.
Definition
BSC local switching refers to a process in which speech signals on the Abis interface loop back to the MS without passing through the NSS when the calling party and called party are served by the same BSC, as shown in Figure 44-1. BSC local switching saves transmission resources of section C. Figure 44-1 BSC local switching diagram
A B C D E F
BTS MSC BTS MGW
BSC
TC
MGW
BTS
F Speech signal stream of the BSC local switching between BTSs controlled by a BSC Traffic link Signaling link
NOTE
BSC local switching is performed on the BSC side without involving the NSS. Speech signals do not pass through the MSC. The transmission resources of section D and section E on the MSC side, however, are not released.
Purposes
BSC local switching saves transmission resources of the Ater interface.
44-2
Issue 02 (2008-06-30)
Terms
Terms BTS local switching Definition 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. Calls in the local switching state are recovered to the ordinary conversation state. Interface between the GMPS/GEPS and the GTCS In the GSM communication system, the versions of the speech coding/decoding algorithm are categorized into full-rate speech versions 1, 2, and 3 and half-rate speech versions 1, 2, and 3. Indicates the additional services such as call waiting and call hold, which are provided for users to handle a successful call. Supports a simultaneous communication with more than one party. Supplementary services for multiparty communication are categorized into two types: multiparty service and conference call.
Loopback restoration Ater Speech Version
Supplementary services of a successful call Supplementary services of multiparty communication

Acronyms and Abbreviations ACS TFO AMR CIC GMPS GEPS GTCS Full Spelling Active Codec Set Tandem Free Operation Adaptive Multi Rate Circuit Identity Code GSM Main Processing Subrack GSM Extended Processing Subrack GSM TransCoder Subrack
44.2 Availability
This lists the NEs, software versions, and other support required for the implementation of BSC local switching.
NEs Involved
Table 44-1 lists the NEs involved in BSC local switching. Table 44-1 NEs involved in BSC local switching MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 44-2 lists the versions of GBSS products that support BSC local switching. Table 44-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012 AE BTS3006C BTS3002E BTS3900 GSM BTS3900A GSM DBS3900 GSM DTRU QTRU Version V900R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R001C07 and later releases Not supported currently Not supported currently Not supported currently
Miscellaneous
The other requirements for BSC local switching are as follows:
l l
A license is required for BSC local switching. If IP transmission mode is adopted on the A interface, the BSC local switching is not supported. If transmission optimization mode is adopted on the Abis interface, the BSC local switching is not supported.
44-4

l
If IP transmission mode is adopted on the Abis interface, the BSC local switching is not supported. The Hub BTS does not support BSC local switching. If the BSC Subrack Combination Type is set to BM/TC Together, the BSC local switching is not supported. The BSS can perform BSS local switching independently without the MSC cooperation. If the BSS Loop Switch MSC Cooperate Switch is set to Open, you can infer that the BSC local switching is controlled by the MSC. If the MSC does not allow BSC local switching, which is carried in the assignment request message, the BSC local switching is not supported. For a group of combined BTSs, if BTS versions support BSC local switching, but carrier versions of BTSs do not support this feature, BSC local switching cannot be enabled. The charging of local switching is determined by the NSS.
l l
44.3 Impact
This describes the impact of BSC local switching on system performance and other features.

The impact of BSC local switching on system performance is as follows:
l
After BSC local switching is enabled, the handover success rate may decrease, and the call drop rate may increase. For details about the causes, refer to 44.4.3 Handover of BSC Local Switching Call. When the GTCS is locally configured, BSC local switching should not be enabled because the transmission line of the Ater interface is relatively short. After BSC local switching is enabled, the announcement and lawful interception services of the MSC are not supported. If the MS in the call setup procedure requires to be monitored, the MSC asks the BSC not to initiate BSC local switching. If a forced handover is required upon the activation of BTS local switching, the BSC is unable to request the PCU to convert the PDCH back to TCH and to perform contention resolution in the channel request process. BSC local switching may fail to be enabled owing to the unavailability of radio resources. Enabling BSC local switching may cause discontinuous voice for a short time.

The impact of BSC local switching on other features is as follows:
l
After BSC local switching is enabled, call completion supplementary services and MPTY supplementary services are not supported.

This describes the technical aspects of BSC local switching, consisting of start, recovery, and handover of BSC local switching calls. 44.4.1 Initiation of BSC Local Switching Call
This describes the requirements for the start of BSC local switching call. To initiate a BSC local switching call, the call must meet the relevant conditions, pass the BSC local switch call check, comply with the relevant initiation policies, and select the correct speech version for the calling and called parties. 44.4.2 Recovery of BSC Local Switching Call This describes the recovery of BSC local switching call. When a handover occurs during a BSC local switching call, the target cell may not support local switching or the outgoing BSC handover fails. In this case, the BSC local switching call must be recovered to an ordinary call. 44.4.3 Handover of BSC Local Switching Call This describes the handover of BSC local switching call. The intra-BSC handover and outgoing BSC handover of the BSC local switching call are different from the common handover mechanism.
44.4.1 Initiation of BSC Local Switching Call

This describes the requirements for the start of BSC local switching call. To initiate a BSC local switching call, the call must meet the relevant conditions, pass the BSC local switch call check, comply with the relevant initiation policies, and select the correct speech version for the calling and called parties. The process for initiating a BSC local switching call is as follows: 1. After the called party answers or the incoming BSC handover of speech service is complete, the BSC checks the conditions for starting BSC local switching. The conditions for starting BSC local switching are as follows:
l l l
Whether the license supports BSC local switching. Whether BSS General Strategy supports BSC local switching. Whether the call meets the requirement for initiating the BSS General Strategy.
2. 3.
If these conditions are met, the BSC starts local switching call detection to detect whether the calling and called parties are served by the same BSC. If the caller and the called party are located under the same BSC, proceed with the following steps:
l
If Options for BSC Local Switch is set to Prefix Number, and one party meets the start conditions, BSC local switching is started. If Avoid Number for BSC is set, and one party meets the closing conditions, BSC local switching is not started.
When starting BSC local switching, ensure that the voice coding rates of the calling and called parties are the same. If different voice coding rates are used, the BSC adjusts the different rates to the same rate through a forcible handover. If the adjustment fails, the BSC local switching is not initiated. In AMR mode, the same voice coding rate must be used by the caller and the called party. In addition, the rate is fixed. When a BSC local switching call selects a speech version, the selected speech version must be supported by the caller and the called party.
l
If the speech versions supported by the caller and the called party intersect, and the speech versions used by the caller and the called party belong to the intersection, select a speech version according to the policies described in Table 44-3.
44-6
Issue 02 (2008-06-30)
Table 44-3 Policies for selecting a speech version for local switching AMR Whether the ACS Is Consistent and Uses the Same Rate Consistent Full- or HalfRate Channel Speech Version Adjustment Policy
Both the caller and the called party use AMR.
Not involved
Not involved
The conditions for local switching are met. There is no need for adjustment. Both the caller and the called party need to be adjusted. Change an MS using AMR to a non-AMR MS. Ensure that the specific rate and speech version of one party are consistent with those of the other party. Change a halfrate MS to a full-rate MS. Ensure that the specific rate and speech version of one party are consistent with those of the other party. The conditions for local switching are met. There is no need for adjustment.
Inconsistent
Not involved
Not involved
AMR is used by either the caller or the called party of a call.
Not involved
Not involved
Not involved
Neither the caller nor the called party uses AMR.
Not involved
Inconsistent
Not involved
Consistent
Same
Issue 02 (2008-06-30)
44-7
AMR
Whether the ACS Is Consistent and Uses the Same Rate
Full- or HalfRate Channel
Speech Version
Adjustment Policy
Different
Change the speech version of a high-rate MS to the speech version of a low-rate MS.
If only one speech version that is being used belongs to the intersection, select the speech version as the target speech version. If neither the speech version currently used by the caller nor the speech version currently used by the called party belongs to the intersection, select the speech version of the highest version from the intersection. Full rate is preferred when both full rate and half rate are supported.
NOTE
As the same rate set is used for a call when the call uses Adaptive MultiRate (AMR), AMR is not selected when neither the speech version used by the caller nor the speech version used by the called party belongs to the intersection.
When the speech versions used by both parties are consistent, the BSC sets up speech signal links, and both parties perform TDM switching in the BSC. After the TDM switching is successful, the call enters the BSC local switching state, and the redundant resources on the Ater interface are released.
NOTE
The MSC cannot obtain BSC local switching information because speech signals do not pass through the MSC. To ensure the consistency of circuit resources on the MSC and BSC sides, however, the BSC does not release the CIC circuit.
44.4.2 Recovery of BSC Local Switching Call

This describes the recovery of BSC local switching call. When a handover occurs during a BSC local switching call, the target cell may not support local switching or the outgoing BSC handover fails. In this case, the BSC local switching call must be recovered to an ordinary call. The BSC resets up the Ater interface transmission channel, and the speech signals are sent to the MSC through the BSC and then are switched to the MS. The recovery of the BSC local switching call is determined by the BSC without manual intervention and configuration parameters.
44.4.3 Handover of BSC Local Switching Call

This describes the handover of BSC local switching call. The intra-BSC handover and outgoing BSC handover of the BSC local switching call are different from the common handover mechanism.
Intra-BSC Handover
The difference between the intra-BSC handover of the BSC local switching call and the common handover is that the speech version cannot be changed during the handover of the BSC local switching call. That is, the speech version before the handover must be consistent with the speech version after the handover. The restriction on speech versions may result in the drop of handover success rate and the increase of call drop rate.
l
After the intra-BSC handover succeeds, the BSC local switching call may be maintained or switched to a BTS local switching call and then recovered to an ordinary call depending on the local switching support capability of the target channel. If the intra-BSC handover fails, the BSC local switching call is kept in the BSC local switching state.
Inter-BSC Handover
The process of the inter-BSC handover of a BSC local switching call is as follows: 1. 2. Based on the handover decision algorithm, the BSC determines to initiate a BSC handover by sending a handover request to the MSC. Upon receipt of the handover request, the MSC issues a handover command to the BSC.
l
Upon receipt of the handover command, the BSC informs the peer end of the local switching call that the call is restored to a common call. This ensures a normal speech after the inter-BSC handover succeeds. If the BSC does not receive the handover command, the BSC local switching call is maintained. If the BSC receives the handover failure message reported by an MS, the BSC informs the caller of the local switching call that the call is restored to a common call.
44.5 Implementation
This describes how to configure and verify BSC local switching. 44.5.1 Configuring BSC Local Switching This describes how to configure BSC local switching on the BSC6000 Local Maintenance Terminal. 44.5.2 Verifying BSC Local Switching This describes how to verify BSC local switching on the BSC6000 Local Maintenance Terminal.
44.5.1 Configuring BSC Local Switching

This describes how to configure BSC local switching on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The license is applied and activated. To apply for and activate the license, do as follows: 1. In the BSC6000V900R008 Exceptional Commercial License Application Template, fill in the actual number of TRXs that support BSC local switching in the Number of
Issue 02 (2008-06-30)
resources column corresponding to the Number of the TRX supporting BSC local switching in the Resource control items. 2.
l
Enable the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
The SS7 signaling points of the BSC are configured. For how to configure the SS7 signaling points, refer to Configuring the SS7 Signaling Points.
Procedure
Step 1 Configure BSS local switching (performed by the BSC independently or cooperating with the MSC) on the BSC. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and select Configure SS7 Signaling Point from the shortcut menu. A dialog box is displayed. Click the DSP tab, as shown in Figure 44-2.
2.
Figure 44-2 Configuring DSP
3.
Select a DSP, and the click Modify DSP. A dialog box is displayed, as shown in Figure 44-3.
44-10
Issue 02 (2008-06-30)
Figure 44-3 Modifying DSP
4.
Set the BSS Loop Switch MSC Cooperate Switch.

l
If the BSC performs BSS local switching independently, set the BSS Loop Switch MSC Cooperate Switch to Close. If the MSC cooperates with the BSC for the BSS local switching, set the BSS Loop Switch MSC Cooperate Switch to Open, and set parameters on the MSC side so that the BSS local switching is supported.
Step 2 Set parameters involved in BSC local switching on the BSC. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and select Configure BSS Local Switch from the shortcut menu. A dialog box is displayed, as shown in Figure 44-4.
Issue 02 (2008-06-30)
44-11
Figure 44-4 BSS General Strategy
2. 3.
Set BSS General Strategy to BSC Priority or BSC Local Switching. Set Options for BSC Local Switch.
l
If Options for BSC Local Switch is set to Start Ater for BSC, set Start Ater Threshold for BSC. Go to 2.4. If Options for BSC Local Switch is set to Prefix Number or Unconditional Start, go to 2.4. If Options for BSC Local Switch in Figure 44-4 is set to Prefix Number, set Prefix Number for BSC and Number in the BSC Local Switching Prefix Start tag page. Go to 2.5. If Options for BSC Local Switch in Figure 44-4 is set to Unconditional Start, go to 2.5.
4.
Click Next. A dialog box is displayed, as shown in Figure 44-5.

l
44-12
Issue 02 (2008-06-30)
Figure 44-5 BSC Local Switching Prefix Start
5.
Click the BSC Local Switching Prefix Close tab, as shown in Figure 44-6.
l
If BSC Close Based on Number in Figure 44-4 is set to Yes, set Avoid Number for BSC and Number. Go to 2.6. If BSC Close Based on Number in Figure 44-4 is set to No, go to 2.6.
Issue 02 (2008-06-30)
44-13
Figure 44-6 BSC Local Switching Prefix Close
6.
Click Finish to complete the configuration of BSC local switching.
----End
44.5.2 Verifying BSC Local Switching

This describes how to verify BSC local switching on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC6000 LMT window, choose BSC Maintenance > User Resource Maintenance > Query Call Resources. A dialog box is displayed, as shown in Figure 44-7.
44-14
Issue 02 (2008-06-30)
Figure 44-7 Query result
Step 2 Enter the relevant information in Calling ID. Then, click Query. The result is displayed, as shown in Figure 44-8. If BSC local switching is started successfully, the following output is displayed in the Query Result window:
l
The TC subrack information contains only A interface information instead of Ater interface information. The BM subrack information contains Abis interface information.
The activation of BSC local switching is successful.
Issue 02 (2008-06-30)
44-15
Figure 44-8 Query result
----End

This lists the alarms and performance counters related to BSC local switching.
Alarms
None.
Counters
Table 44-4 lists the counters related to BSC local switching. Table 44-4 Counters related to BSC local switching Counter R381 Description Number of Loopback Start Attempts
44-16
Issue 02 (2008-06-30)
Counter R3820 R3821 R3822 R3824 R3825 R3826 R3827 R382b R382c R382d R3830 R3830a
Description Number of Loopback Start Failures (No Loopback Policy Available) Number of Loopback Start Failures (Speech Version Adjustment Failure) Number of Loopback Start Failures (Invalid State) Number of Loopback Start Failure (Territorial Resource Request Failure) Number of Loopback Start Failure (Timer Expired) Number of Loopback Start Failures (Not Support by the BTS) Number of Loopback Start Failures (Other Causes) Number of BSC Loopback Failures after the Handover during the BTS Loopback Number of BTS Loopback Failures after the Handover during the BSC Loopback Number of BSC Loopback Failures after the Handover during the BSC Loopback Number of Successful BSC Loopback Attempts Number of Successful BSC Loopback Attempts after the Handover during the BTS Loopback Number of Successful BSC Loopback Attempts after the Handover during the BSC Loopback Number of Successful BTS Loopback Attempts after the Handover during the BSC Loopback Number of Loopback Start Failures Number of Attempts to Return to Normal Call from BSC Loopback Number of Failures to Return to Normal Call from BSC Loopback (Territorial Resource Request Failure) Number of Failures to Return to Normal Call from BSC Loopback (Others)
R3830b
R3831b
CR382 R3840 R3850a
R3850b
Issue 02 (2008-06-30)
Counter CR3850 R3860 TR3860 M3720
Description Number of Failures to Return to Normal Call from BSC Loopback Number of Successful Attempts to Return to Normal Call from BSC Loopback BSC Loopback to Normal Call Success Rate Call Drops due to BSC Loopback Start Failure (Terrestrial Resource Request Failure) Call Drops due to BSC Loopback Start Failure (Others) Call Drops due to Loopback Start Failure (Timer Expired) Call Drops due to Loopback Start Failure Call Drops due to Handover Failure During the Loopback Call Drops due to Connection Failures in Stable BSC Loopback State Call Drops due to Error Indications in Stable BSC Loopback State Call Drops due to Release Indications in Stable BSC Loopback State Call Drops due to No MRs from MS in Stable BSC Loopback State Call Drops due to Forced Handovers in Stable BSC Loopback State Call Drops due to Abis Terrestrial Link Failure in Stable BSC Loopback State Call Drops due to Equipment Failures in Stable BSC Loopback State Call Drops in Stable BSC Loopback State Call Drops due to Failures to Return to Normal Call from BSC Loopback (Terrestrial Resource Request Failure) Call Drops due to Failures to Return to Normal Call from BSC Loopback (Others) Call Drops due to Failures to Return to Normal Call from Loopback
M3721 M390 CM397 CM398 M3701 M3700 M3702 M372 M375 M373 M374 CM370 M3751
M3752 CM385
44-18
Issue 02 (2008-06-30)
Counter CM390 M3852 CM385 CM390
Description Call Drops During Loopback Call Drops due to Failures to Return to Normal Call from BTS Loopback (Others) Call Drops due to Failures to Return to Normal Call from Loopback Call Drops During Loopback
44.7 References
None.
Issue 02 (2008-06-30)
44-19
45 BTS Local Switching
45
About This Chapter
BTS Local Switching
45.1 Overview BTS local switching is a process in which speech signals are switched to the target MS of a call through the BTS. It helps save transmission resources. 45.2 Availability This lists the NEs, software, and other conditions required for the implementation of BTS local switching. 45.3 Impact This describes the impact of BTS local switching on system performance and on other features. 45.4 Technical Description This describes the initiation of BTS local switching call, recovery of BTS local switching call, and handover of BTS local switching call. 45.5 Implementation This describes how to configure and verify BTS local switching. 45.6 Maintenance Information The maintenance information about BTS local switch refers to performance counters. 45.7 References None.
Issue 02 (2008-06-30)
45-1
45.1 Overview
BTS local switching is a process in which speech signals are switched to the target MS of a call through the BTS. It helps save transmission resources.
Definition
In BTS local switching, the calling and called parties are served by the same BTS or by the same BTS group. The BTS or BTS group processes the Abis speech signals associated with the call and transmits the speech signals to the addressed party without routing the speech signals to the BSC and MSC, as shown in Figure 45-1. Figure 45-1 BTS local switching diagram
A (1) B C D E F
(2)
BTS BTS
MSC
MGW
BSC
TC
MGW
BTS
F Speech signal stream of the BTS local switching under the same BTS or same BTS group Traffic link Signaling link
NOTE
BTS local switching is performed on the BSS side, not involving on the NSS side. The speech signals are not routed to the MSC. The transmission resources on segments D and E on the MSC side, however, are not released.
Purposes
With BTS local switching, the transmission resources on the Abis and Ater interfaces are greatly saved. As shown in Figure 45-1, BTS local switching helps save the transmission resources on segments B and C or on segments A, B, and C.
Terms
Terms BSC Local Switching Definition In BSC local switching, the two MSs involved in a call are served by the same BSC. On the Abis interface, the BSC routes the speech signals to the addressed MS directly without routing the speech signals to NSS. The Ater transmission resources originally occupied by the call are released and saved accordingly. Indicates that a call in the local switching status is restored to a common call. Interface between the GMPS/GEPS and the GTCS There are different versions of speech codec algorithms available in the GSM. For example, the full-rate speech versions are numbered 1, 2, and 3, and the half-rate speech versions are also numbered 1, 2, and 3. This is a timeslot allocation scheme adopted on the Abis interface. In this scheme, the channels on the Um interface and the timeslots on the Abis interface are not long bundled together. Instead, the timeslots on the Abis interface are allocated dynamically for each call. Indicates the additional services such as call waiting and call hold, which are provided for users to handle a successful call. Supports a simultaneous communication with more than one party. Supplementary services for multiparty communication are categorized into two types: multiparty service and conference call. Connecting the BTS ring topology to the BSC helps improve the robustness and reliability of the network. For details about the BTS ring topology, refer to 41 BTS Ring Topology.
Loopback restoration Ater Speech Version
Flex Abis
Supplementary services of a successful call Supplementary services of multiparty communication BTS ring topology

Acronyms and Abbreviations ACS BSC MSC CN DPC NRI TMSI Full Spelling Active Codec Set Base Station Controller Mobile Switching Center Core Network Destination (signaling) Point Code Network Resource Identifier International Mobile Station Identity
Issue 02 (2008-06-30)
45-3
Acronyms and Abbreviations IMSI IMEI MGW NAS MOCN
Full Spelling International Mobile Station Identity International Mobile Station Identity Media Gateway Non Access Stratum Multi-Operator Core Network
45.2 Availability
This lists the NEs, software, and other conditions required for the implementation of BTS local switching.
NEs Involved
Table 45-1 lists the NEs involved in BTS local switching. Table 45-1 NEs involved in BTS local switching MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 45-2 lists the versions of GBSS products that support BTS local switching. Table 45-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012 AE BTS3006C
45-4
Version V900R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases
Issue 02 (2008-06-30)
DTRU QTRU
Product BTS3002E BTS3900 GSM BTS3900A GSM DBS3900 GSM
Version BTS3000V100R001C07 and later releases Not supported currently Not supported currently Not supported currently
Miscellaneous
BTS local switching has the following limits:
l l
A license is required for BTS local switching. If IP transmission mode is adopted on the A interface, the BTS local switching is not supported. If transmission optimization mode is adopted on the Abis interface, the BTS local switching is not supported. If IP transmission mode is adopted on the Abis interface, the BTS local switching is not supported. The Hub BTS does not support BTS local switching. BTS local switching is not restricted when BSC Subrack Combination Type is set to BM/ TC together. The BSS can perform BSS local switching independently without the MSC cooperation. If BSS Loop Switch MSC Cooperate Switch is set to Open, you can infer that the BSC local switching is controlled by the MSC. If the BSS local switching is not allowed on the MSC side, this information is carried in the assignment request message and thus the BTS local switching is not supported. BTS local switching and BTS ring topology cannot be enabled for a BTS at the same time. In the sites with hybrid BTS cabinet groups the BTS local switching cannot be implemented if the BTS software versions support BTS local switching while the TRX software versions do not support BTS local switching. The charging of local switching is controlled by the NSS.
l l
l l
45.3 Impact
This describes the impact of BTS local switching on system performance and on other features.

BTS local switching has the following impact on system performance:
l
After BTS local switching is enabled, the handover success rate may decrease, and the call drop rate may increase. For details about the causes, refer to 45.4.3 Handover of BTS Local Switching Call. During the process for enabling BTS local switching, temporary audio discontinuity may occur.
Issue 02 (2008-06-30)

l
After BTS local switching is enabled, the system does not support the MSC announcement and lawful interception services. If the MS in the call setup process requires to be supervised, the MSC instructs the BSC not to initiate BTS local switching. If a forced handover is required upon the activation of BTS local switching, the BSC is unable to request the PCU to convert the PDCH back to TCH and to perform contention resolution in the channel request process. The BTS local switching may fail if no radio resources are available. During the process for enabling BTS local switching, temporary audio discontinuity may occur.

BTS local switching has the following impact on other features:
l
After BTS local switching is enabled, the system does not support the supplementary services of a successful call or the supplementary services of multiparty communication. BTS local switching can be enabled only when BTSs support Flex Abis and the timeslot assignment mode is set to dynamic assignment. For details, refer to 39 Flex Abis.

This describes the initiation of BTS local switching call, recovery of BTS local switching call, and handover of BTS local switching call. 45.4.1 Initiation of BTS Local Switching Call This describes the initiation of a BTS local switching call. To initiate a BTS local switch call, the call must meet the relevant conditions, pass the BTS local switch call check, comply with the relevant initiation policies, and selects the correct speech version for the calling and called parties. 45.4.2 Recovery of BTS Local Switching Call When the handover of a BTS local switching call occurs, the TRX of the target channel may not support local switching or the handover of a particular type may fail. In such a case, a BTS local switching call must be restored to a common call. 45.4.3 Handover of BTS Local Switching Call The implementation of intra-BSC handover and inter-BSC handover of a BTS local switching call is different from that of a common handover.
45.4.1 Initiation of BTS Local Switching Call

This describes the initiation of a BTS local switching call. To initiate a BTS local switch call, the call must meet the relevant conditions, pass the BTS local switch call check, comply with the relevant initiation policies, and selects the correct speech version for the calling and called parties. The process for initiating the BTS local switching call is as follows: 1. After the called party picks up a phone or the speech service is switched to the BSC, the BSC determines whether the conditions for initiating BTS local switching are met. The conditions for initiating BTS local switching are as follows:
l
Whether the existing license supports BTS local switching

45-6

l l
Whether the BSS General Strategy supports BTS local switching Whether the call meets the Options for BTS Local Switch
2.
If the conditions for initiating BTS local switching are met, the BSC starts checking a local switching call. That is, through the GTCS, the BSC checks whether the calling and the called parties are served by the same BSC. If the calling and called parties are served by the same BSC, proceed with the following steps:
l
3.
When Options for BTS Local Switch is set to number prefix for initiation, initiate BTS local switching if either the calling party or the called party meets the initiation conditions. When Avoid Number for BTS is set, do not initiate local switching if either the caller or the called party meets the closing condition.
When the BTS local switching is started, the speech codec rates of the calling party and called party must be the same. If different speech codec rates are used, the BSC adjusts the different rates to the same rate through a forced handover. If the adjustment fails, the BSC local switching is not initiated. In AMR mode, the same speech codec rate must be used by the calling and called parties. In addition, the rate is fixed. When a BTS local switching call selects a speech version, the selected speech version must be supported by the caller and the called party.
l
If the speech versions supported by the caller and the called party intersect, and the speech versions used by the caller and the called party belong to the intersection, select a speech version according to the policies described in Table 45-3. Table 45-3 Policies for selecting a speech version for local switching AMR Whether the ACS Is Consistent and Uses the Same Rate Consistent Full- or HalfRate Channel Speech Version Adjustment Policy
Both the caller and the called party use AMR.
Not involved
Not involved
The conditions for local switching are met. There is no need for adjustment. Both the caller and the called party need to be adjusted.
Inconsistent
Not involved
Not involved
Issue 02 (2008-06-30)
45-7
AMR
Whether the ACS Is Consistent and Uses the Same Rate Not involved
Full- or HalfRate Channel
Speech Version
Adjustment Policy
AMR is used by either the caller or the called party of a call.
Not involved
Not involved
Change an MS using AMR to a non-AMR MS. Ensure that the specific rate and speech version of one party are consistent with those of the other party. Change a halfrate MS to a full-rate MS. Ensure that the specific rate and speech version of one party are consistent with those of the other party. The conditions for local switching are met. There is no need for adjustment. Change the speech version of a high-rate MS to the speech version of a low-rate MS.
Neither the caller nor the called party uses AMR.
Not involved
Inconsistent
Not involved
Consistent
Same
Different
If only one speech version that is being used belongs to the intersection, select the speech version as the target speech version. If neither the speech version currently used by the caller nor the speech version currently used by the called party belongs to the intersection, select the speech version of the highest version from the intersection. Full rate is preferred when both full rate and half rate are supported.
45-8
Issue 02 (2008-06-30)

NOTE
As the same rate set is used for a call when the call uses Adaptive MultiRate (AMR), AMR is not selected when neither the speech version used by the caller nor the speech version used by the called party belongs to the intersection.
When the speech version used by the calling and called parties is the same, the BSC issues a link setup command to the BTS. The call loops back on the Abis interface of the BTS or the BTS group. After the loopback is successful, the call is switched to the BTS local switching status. Then, the resources on the Abis and Ater interface are released.
45.4.2 Recovery of BTS Local Switching Call

When the handover of a BTS local switching call occurs, the TRX of the target channel may not support local switching or the handover of a particular type may fail. In such a case, a BTS local switching call must be restored to a common call. The BSC issues a link setup command to the BTS to re-establish the Abis terrestrial transmission resource associated with the channel on the Um interface. In the BSC, the transmission channel on the Ater interface is set up. Speech signals are sent from the BSC to the MSC, which routes the speech signals to the called party. The recovery of BTS local switching call is determined by the BSC without human intervention. There are no configuration parameters available.
45.4.3 Handover of BTS Local Switching Call

The implementation of intra-BSC handover and inter-BSC handover of a BTS local switching call is different from that of a common handover.
Intra-BSC Handover
The difference between the intra-BSC handover of the BTS local switching call and the common handover is that the speech version cannot be changed during the handover of the BTS local switching call. That is, the speech version before the handover must be consistent with that after the handover. The restriction on speech versions may result in the drop of handover success rate and the increase of call drop rate.
l
After the intra-BSC handover of a BTS local switching call succeeds, the BTS local switching call may be retained, be changed to a BSC local switching call, or be restored to a common call based on the local switching capability of the target channel. After the BSS receives a handover failure message reported by the MS, the BTS local switching call is restored to a common call if the BSC receives a handover detection message. If the BSC does not receive a handover detection message, the BTS local switching call remains unchanged.
Inter-BSC Handover
The process of the inter-BSC handover of a BSC local switching call is as follows: 1. 2. Based on the handover decision algorithm, the BSC determines to initiate an inter-BSC handover by sending a handover request to the MSC. On receiving the handover request message, the MSC sends a handover command message to the BSC.
Issue 02 (2008-06-30)

l
On receiving the handover command message, the BSC informs the peer end of the local switching call that the call is restored to a common call. This ensures a normal speech after the inter-BSC handover succeeds. If the BSC does not receive the handover command message, the BTS local switching call remains unchanged. If the BSC receives the handover failure message reported by an MS, the BSC informs the caller of the local switching call that the call is restored to a common call.
45.5 Implementation
This describes how to configure and verify BTS local switching. 45.5.1 Configuring BTS Local Switching This describes how to configure BTS local switching on the BSC6000 Local Maintenance Terminal. 45.5.2 Verifying BTS Local Switching This describes how to verify BTS local switching on the BSC6000 Local Maintenance Terminal.
45.5.1 Configuring BTS Local Switching

This describes how to configure BTS local switching on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The license is applied and activated. To apply for and activate the license, do as follows: 1. In the BSC6000V900R008 Exceptional Commercial License Application Template, fill in the actual number of TRXs that support BTS local switching in the Number of resources column corresponding to the Number of the TRX supporting BTS local switching in the Resource control items. Enable the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
l
The SS7 signaling points of the BSC are configured. For how to configure the SS7 signaling points, refer to Configuring the SS7 Signaling Points.
Procedure
Step 1 Configure BSS local switching (performed by the BSC independently or cooperating with the MSC) on the BSC. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and select Configure SS7 Signaling Point from the shortcut menu. A dialog box is displayed. Click the DSP tab, as shown in Figure 45-2.
2.
45-10
Issue 02 (2008-06-30)
Figure 45-2 Configuring DSP
3.
Select a DSP, and the click Modify DSP. A dialog box is displayed, as shown in Figure 45-3. Figure 45-3 Modifying DSP
4.
Set the BSS Loop Switch MSC Cooperate Switch.

l
If the BSC performs BSS local switching independently, set the BSS Loop Switch MSC Cooperate Switch to Close.
Issue 02 (2008-06-30)
45-11

l
If the MSC cooperates with the BSC for the BSS local switching, set the BSS Loop Switch MSC Cooperate Switch to Open, and set parameters on the MSC side so that the BSS local switching is supported.
Step 2 On the BSC, set parameters related to BTS local switching. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000 and select Configure BSS Local Switch from the shortcut menu. A dialog box is displayed, as shown in Figure 45-4.
Figure 45-4 General Strategy of the BSS Local Switching
2. 3.
Set BSS General Strategy to BTS Priority or BTS Local Switching. Configure Options for BTS Local Switch.
l
If Options for BTS Local Switch is set to Start Abis for BTS, set Start Abis Threshold for BSC. Go to 2.4. If Options for BTS Local Switch is set to Prefix Number or Unconditional Start, go to 2.4. If Options for BTS Local Switch in Figure 45-4 is set to Prefix Number, set Prefix Number for BTS and Number in the BTS Local Switching Prefix Start tag page. Go to 2.5. If Options for BTS Local Switch in Figure 45-4 is set to Unconditional Start, go to 2.5.
4.
Click Next. A dialog box is displayed, as shown in Figure 45-5.

l
45-12
Issue 02 (2008-06-30)
Figure 45-5 Prefix to start BTS local switch
5.
Click the Segment to Avoid BTS Local Switch tab shown in Figure 45-6.
l
If BTS Close Based on Number in Figure 45-4 is set to Yes, set Avoid Number for BTS and Number. Go to 2.6. If BTS Close Based on Number in Figure 45-4 is set to No, go to 2.6.
Issue 02 (2008-06-30)
45-13
Figure 45-6 Segment to avoid BTS local switch
6.
Click Finish to complete the configuration of the BSC.
Step 3 On the BTS, set parameters related to BTS local switching. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick a BTS and select Site Operation > Configure Site Attributes from the shortcut menu. Select a BTS in the Site View list box and click Set Site Attributes. A dialog box is displayed, as shown in Figure 45-7. Set Support BTS Local Switch to Yes.
2.
45-14
Issue 02 (2008-06-30)
Figure 45-7 Configuring site attributes (2)
3.
Click OK to complete the configuration.
Step 4 Configure the Flex Abis attribute of a BTS. 1. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the BTS that carries the call and select Site Operation > Modify Site Flex Abis Mode. A dialog box is displayed, as shown in Figure 45-8.
Issue 02 (2008-06-30)
45-15
Figure 45-8 Configuring the Flex Abis attribute of a BTS
2. 3.
Set Flex Abis Mode to Flex or SemiSolid. Click Finish to complete the configuration.
----End
45.5.2 Verifying BTS Local Switching

This describes how to verify BTS local switching on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal window, choose BSC Maintenance > Maintain User Resource > Query Single User Resources. A dialog box is displayed, as shown in Figure 45-9.
45-16
Issue 02 (2008-06-30)
Figure 45-9 Querying single user resources
Step 2 Enter the relevant information in the Calling ID area. Then, click Query. The result is displayed, as shown in Figure 45-10. If BSC local switching is started successfully, the following information is displayed in the Query Result pane:
l
TC Subrack Information contains only A Interface Information and does not contain the Ater interface information. BM Subrack Information is not available.
Issue 02 (2008-06-30)
45-17
Figure 45-10 Querying single user resources
----End

The maintenance information about BTS local switch refers to performance counters.
Alarms
None.
Counters
Table 45-4 lists the performance counters pertaining to BTS local switch. Table 45-4 Performance counters pertaining to BTS local switch Counter R380 R381
45-18
Description Local switching call check times Loopback start attempts

Counter R3820 R3821 R3822 R3823 R3824 R3825 R3826 R3827 R382b R382c R382a R3831 R3830a R3831a R3831b CR382 R3841 R3851a R3851b CR3851 R3861 TR3861
Description Loopback start failures (loopback policy unavailable) Loopback start failures (speech version adjustment failure) Loopback start failures (invalid state) Loopback start failures (BTS failure) Loopback start failures (ground resource application failure) Loopback start failures (timer timeout) Loopback start failures (not supported by the BTS) Loopback start failures (other reasons) BSC loopback failures after BTS loopback handover BTS loopback failures after BSC loopback handover BTS loopback failures after BTS loopback handover BTS loopback success times BSC loopback success times after BTS loopback handover BTS loopback success times after BTS loopback handover BTS loopback success times after BSC loopback handover Loopback start failures BTS loopback recovery attempts BTS loopback recovery failures (ground resource application failure) BTS loopback recovery failures (other reasons) BTS loopback recovery failures BTS loopback recovery success times BTS loopback recovery success ratio
Issue 02 (2008-06-30)
45-19
Counter M3820
Description Call drop times due to BTS loopback start failure (ground resource application failure) Call drop times due to BTS loopback start failure (BTS failure) Call drop times due to BTS loopback start failure (other reasons) Call drop times due to BTS loopback start failure (timer timeout) Call drop times due to loopback start failure Call drop times due to loopback handover failure Call drop times due to connection failure in the BTS loopback state Call drop times due to wrong indication in the BTS loopback state Call drop times due to release indication in the BTS loopback state Call drop times due to no MS report for long time in the BTS loopback state Call drop times due to forcible handover in the BTS loopback state Call drop times due to a ground link fault of the Abis interface in the BTS loopback state Call drop times due to equipment fault in the BTS loopback state Call drop times in the BTS loopback state Call drop times due to BTS loopback recovery failure (ground resource application failure) Call drop times due to BTS loopback recovery failures (other reasons) Call drop times due to loopback recovery failure Call drop times due to loopback
M3821 M3822 M390 CM397 CM398 M3801 M3800 M3802 M382 M385 M383
M384 CM380 M3851
M3852 CM385 CM390
45-20
Issue 02 (2008-06-30)
45.7 References
None.
Issue 02 (2008-06-30)
45-21
46 Dynamic MAIO
46
About This Chapter
Dynamic MAIO
46.1 Overview Dynamic MAIO is used to reduce the co-channel interference and adjacent-channel interference in the GSM system through the preferential selection of the channels with less interference during channel assignment. 46.2 Availability This lists the NEs, software versions, and other support required for the implementation of dynamic MAIO. 46.3 Technical Description This describes channel assignment, MAIO assignment, and HSN assignment related to dynamic MAIO. 46.4 Capabilities This describes the functions that dynamic MAIO supports and the limitations on dynamic MAIO. 46.5 Implementation This describes how to configure and verify dynamic MAIO. 46.6 Maintenance Information This lists the alarms and performance counters related to dynamic MAIO. 46.7 References The references indicate the documents about dynamic MAIO from the related standard organizations.
Issue 02 (2008-06-30)
46-1
46 Dynamic MAIO
46.1 Overview
Dynamic MAIO is used to reduce the co-channel interference and adjacent-channel interference in the GSM system through the preferential selection of the channels with less interference during channel assignment.
Definition
Dynamic MAIO means that channels with less interference are preferentially selected during channel assignment. If the finally selected channel incurs interference, the minimum MAIO or HSN is assigned to the channel.
Purposes
Because the frequency resources are limited, much co-channel interference and adjacent-channel interference occur in the GSM system in the case of aggressive frequency reuse. Dynamic MAIO can be used to minimize the co-channel interference and adjacent-channel interference for some channels when frequency hopping is enabled in a cell. HSN assignment principle: If other channels on the same timeslot with the finally selected channel in the cell are in the inactive state, and if there are occupied channels on the same timeslot in all neighbor cells in the BTS, change the HSN of the current channel and select an unused HSN to reduce the interference between active channels.
Terms
Terms Flex MAIO HSN MA MAIO Definition Dynamic MAIO Hopping sequence number Mobile allocation, that is, a frequency set of the cell frequency hopping group Mobile allocation index offset

Acronyms and Abbreviations HSN MA MAIO Full Spelling Hopping Sequence Number Mobile Allocation Mobile Allocation Index Offset
46-2
Issue 02 (2008-06-30)
46 Dynamic MAIO
46.2 Availability
This lists the NEs, software versions, and other support required for the implementation of dynamic MAIO.
NEs Involved
Table 46-1 describes the NEs involved in dynamic MAIO. Table 46-1 NEs involved in dynamic MAIO MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 46-2 lists the software versions of GBSS products that support dynamic MAIO. Table 46-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3X BTS3002E BTS3006C BTS3012 DTRU QTRU BTS3012A E BTS3036 BTS3036A DBS3036 DTRU QTRU Version V900R008C01 and later releases GBTS32R007C02 and later releases BTS3000V100R001C07 and later releases BTS3000V100R001C07 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C01 and later releases
Issue 02 (2008-06-30)
46-3
46 Dynamic MAIO
Miscellaneous
The other requirements for dynamic MAIO are as follows:
l
The BTS software must meet the version requirements. For details, refer to Table 46-2. If the BTS software does not meet the version requirements, call failures may occur. On the BSC6000 Local Maintenance Terminal, enable the FLEX MAIO SWITCH and perform channel frequency hopping.

This describes channel assignment, MAIO assignment, and HSN assignment related to dynamic MAIO. 46.3.1 Dynamic MAIO Channel Assignment This describes dynamic MAIO channel assignment based on the priority of timeslot interference. 46.3.2 Assignment Principle for Dynamic MAIO and HSN This describes the assignment principle for the dynamic MAIO and HSN.
46.3.1 Dynamic MAIO Channel Assignment

This describes dynamic MAIO channel assignment based on the priority of timeslot interference. In the case of the same priority, the channel with the least dynamic MAIO timeslot interference is preferentially selected. During channel frequency hopping, the frequency is related to the MA, frame number, HSN, and MAIO. According to the 45.002 protocol, the index of the frequency in the MA table can be calculated as follows: (S+MAIO)%N Where, S indicates the frequency index calculated on the basis of the frame number and HSN. N indicates the number of frequencies in the MA. According to the formula, when two channels on the same timeslot have the same HSN and MA and there are some adjacent frequencies in the MA, one of the following cases may occur:
l
The adjacent-channel interference occurs only when two channels on the same timeslot use the adjacent MAIO. The co-channel interference occurs only when two channels on the same timeslot use the same MAIO.
If two channels use different MAs, but the number of frequencies in the MAs and the HSN are the same, there are adjacent frequencies or the same frequencies between the MAs.
l
If two channels use adjacent frequencies, and the MAIO difference is the same as the spacing between the two adjacent frequencies in the MA table, the adjacent-channel interference occurs between the channels. For example, MA = (1, 2, 5, 7). If the MAIOs used by two channels on the same timeslot are 0 and 1 respectively, the MAIO difference is 1. If the spacing between adjacent frequencies 1 and 2 in the MA table is also 1, the adjacent-channel interference occurs between the two channels.
46-4
Issue 02 (2008-06-30)

l
46 Dynamic MAIO
If two channels use the same frequencies, and if the MAIO difference is the same as the spacing between the two frequencies in the MA table, the co-channel interference occurs between the channels.
The weight of co-channel interference in a cell or between cells is the highest. If an MAIO is assigned, channels on the same timeslot in the BTS cannot be assigned with the same MAIO, that is, co-channel interference is prohibited in the BTS. The TCHF channel interference is eight times the SDCCH/8 interference. The TCHH channel interference is four times the SDCCH/8 interference. The interference in cells is stronger than that between cells. The adjacent-channel interference in cells is stronger than the co-channel interference between cells. When a channel is occupied, it may produce co-channel or adjacentchannel interference to other channels on the same timeslot in the BTS. The timeslot interference record contains the total interference of all the active channels on the timeslot in the BTS to the channels in a timeslot in the cell. Based on the current timeslot interference record, channels with less interference can be selected during channel assignment. Active channels refer to not only occupied channels but also dynamic or static PDCHs. According to the characteristics of packet services, if there is a dynamic PDCH or a static PDCH on the timeslot, the configured HSN or MAIO must be used during the channel activation and assignment irrespective of circuit services or packet services. Dynamic assignment cannot be performed. If this channel is configured with an HSN or MAIO, the channel permanently uses it. The HSN or MAIO of this channel cannot be dynamically assigned to other channels. Dynamic MAIO does not apply to this channel. The timeslot interference priority is not the prerequisite for channel assignment. This priority is higher than the priority of history records, carriers, and interference but lower than the priority of the TCH rate type and Flex Abis. For details, refer to the description of Huawei II Channel Assignment Algorithm in 2.3.3 Channel Assignment Algorithms.
46.3.2 Assignment Principle for Dynamic MAIO and HSN

This describes the assignment principle for the dynamic MAIO and HSN. The assignment principle for the dynamic MAIO and HSN is as follows:
l
If a channel is not for RF frequency hopping, or the configuration type is dynamic PDCH or static PDCH, the MAIO is not updated. Use 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, use the HSN and MAIO of the occupied subchannel to activate the channel. If the active HSN on the timeslot is different from the configured HSN, use the active HSN and the configured MAIO to activate the channel. If there is no active channel on the same timeslot in the cell, but there are active channels on the same timeslot in all neighbor cells in the BTS and the HSN of active channels in neighbor cells is the configured HSN, an unused HSN is dynamically assigned. The HSN for activating the channel is a newly assigned HSN, and the MAIO for activating the channel is the configured MAIO. If the timeslot interference record is read based on the timeslot number of the channel, the configured HSN, and the MAIO of the timeslot and if the channel incurs interference, the MAIO with the least interference is dynamically assigned and this MAIO is the MAIO for activating the channel.
Issue 02 (2008-06-30)
46-5
46 Dynamic MAIO
46.4 Capabilities
This describes the functions that dynamic MAIO supports and the limitations on dynamic MAIO. Dynamic MAIO supports the following functions:
l l
Assigning the channel with the least interference or the MAIO and HSN to CS calls Supporting dynamic MAIO assignment in the BTS
The limitations on dynamic MAIO are as follows:

l
Only the function of selecting a channel with the least interference is supported. Dynamic MAIO assignment is not supported during baseband frequency hopping. Only circuit services support dynamic MAIO assignment. Packet services do not support dynamic MAIO assignment.
46.5 Implementation
This describes how to configure and verify dynamic MAIO. 46.5.1 Precautions for Configuring Dynamic MAIO This provides the precautions for configuring dynamic MAIO. 46.5.2 Configuring Dynamic MAIO This describes how to configure dynamic MAIO on the BSC6000 Local Maintenance Terminal. 46.5.3 Verifying Dynamic MAIO This describes how to verify dynamic MAIO on the BSC6000 Local Maintenance Terminal.
46.5.1 Precautions for Configuring Dynamic MAIO

This provides the precautions for configuring dynamic MAIO. The limitations for configuring dynamic MAIO are as follows:
l l
Each cell can be configured with a maximum of 2 different MAs. The MAs used by the same timeslot in the same BTS have the same length. The channels on the same timeslot in the same BTS use the same MA for frequency hopping. No cells in the BTS are configured with frame offset. The configuration of FLEX MAIO SWITCH of cells in the same BTS must be consistent. Because the double-slot extended cell features wide coverage and non-aggressive frequency reuse, dynamic MAIO does not need to be enabled.
l l l
For better performance of the dynamic MAIO algorithm, the frequency hopping data configuration of the BTS must meet the following requirements:
l
1x1 frequency reuse with BCCH frequencies not joining in frequency hopping All the frequency hopping channels in the BTS use the same MA and HSN. 1x1 frequency reuse with BCCH frequencies joining in frequency hopping
46-6
46 Dynamic MAIO
All the channels on timeslot 0 in the BTS use one set of frequency hopping data {MA0, HSN0}. All the other channels use another set of frequency hopping data {MA1, HSN1}.
l
1x3 frequency reuse with BCCH frequencies not joining in frequency hopping
The frequency hopping data used by the cells in the BTS is different, but the number of frequencies in all MAs and the HSN are the same. Adjacent frequencies exist not in MAs but between the MAs. The frequency hopping data used by all the FH channels in the cell is the same. The frequency hopping data used by the cells in the BTS is different, but the number of frequencies in all MAs on the same timeslot and the HSN are the same. Adjacent frequencies exist not in MAs but between the MAs. The MA used by timeslot 0 in the cell is different from the MA used by other timeslots. The frequency hopping data used by other timeslots is the same.
1x3 frequency reuse with BCCH frequencies joining in frequency hopping
46.5.2 Configuring Dynamic MAIO

This describes how to configure dynamic MAIO on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click a cell on the Management Tree tab page. Then, choose Configure Cell Attributes. Step 2 In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. Step 3 In the displayed dialog box, click Configure Cell Attributes. A dialog box is displayed, as shown in Figure 46-1.
Issue 02 (2008-06-30)
46-7
46 Dynamic MAIO
Step 4 As shown in Figure 46-1, click Channel Management. Click Advanced, as shown in Figure 46-2.
46-8
Issue 02 (2008-06-30)
46 Dynamic MAIO
Figure 46-2 Configuring Flex MAIO channel management parameters in a cell
Step 5 On the HWII Channel Assignment and Radio Channel Control tab page, as shown in Figure 46-2, set FLEX MAIO SWITCH and FLEX HSN SWITCH. Step 6 Configure the frequency hopping data of the cell to enable the cell to support dynamic MAIO. For details about the configuration of frequency hopping data, refer to 17 Frequency Hopping. ----End
46.5.3 Verifying Dynamic MAIO

This describes how to verify dynamic MAIO on the BSC6000 Local Maintenance Terminal.
Prerequisite
The prerequisites for verifying dynamic MAIO are as follows:
l l
The BSC6000 Local Maintenance Terminal is started normally. The communication between the BSC and the BTS is normal.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, click Trace&Monitor, and then choose Trace > Trace User Message. A dialog box is displayed, as shown in Figure 46-3.
Issue 02 (2008-06-30)
46-9
46 Dynamic MAIO
Figure 46-3 Tracing User Messages
Step 2 Set parameters in the Interface Type, Tracing Mode, and Color areas. Select and fill in the IMSI, TMSI, MSISDN, IMEI, or Channel of the user to be traced. Click OK to start tracing. The result is displayed, as shown in Figure 46-4. Figure 46-4 Result of tracing user messages
Step 3 Double-click the CHANNEL ACTIVATION area. A window is displayed, as shown in Figure 46-5.
46 Dynamic MAIO
Figure 46-5 Viewing Messages
If the messages shown in Figure 46-5 contain frequency hopping attributes, you can infer that dynamic MAIO is enabled. Otherwise, dynamic MAIO is not enabled. ----End

This lists the alarms and performance counters related to dynamic MAIO.
Alarms
None
Counters
None
46.7 References
The references indicate the documents about dynamic MAIO from the related standard organizations.
46 Dynamic MAIO
The references are as follows:

l
GSM 05.03 V7.3.1 "Digital cellular telecommunications system (Phase 2+); Channel coding" GSM 05.09 V7.7.1 "Digital cellular telecommunications system (Phase 2+); Link Adaptation" GSM 04.08 V7.21.0 "Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification"
GSM 06.90 V7.2.1 "Digital cellular telecommunications system (Phase 2+); Adaptive Multi-Rate (AMR) speech transcoding"
GSM 06.91 V7.1.1 "Digital cellular telecommunications system (Phase 2+); Substitution and muting of lost frames for Adaptive Multi Rate (AMR) speech traffic channels"
GSM 06.92 V7.1.1 "Digital cellular telecommunications system (Phase 2+); Comfort noise aspects for Adaptive Multi-Rate (AMR) speech traffic channels "
GSM 06.93 V7.5.0 "Digital cellular telecommunications system (Phase 2+); Discontinuous transmission (DTX) for Adaptive Multi Rate (AMR) speech traffic channels"
GSM 06.94 V7.1.1 "Digital cellular telecommunications system (Phase 2+); Voice Activity Detection (VAD) for Adaptive Multi-Rate speech traffic channels"
GSM 08.08 V7.7.0 "Digital cellular telecommunications system (Phase 2+); Mobile-services Switching Centre - Base Station System (MSC - BSS) interface; Layer 3 specification"
GSM 08.58 V7.4.1 "Digital cellular telecommunications system (Phase 2+); Base Station Controller - Base Transceiver Station (BSC - BTS) interface; Layer 3 specification"
GSM 08.60 V7.3.0 "Digital cellular telecommunications system (Phase 2+); In-band control of remote transcoders and rate adaptors for full rate traffic channels"
GSM 08.61 V7.3.0 "Digital cellular telecommunications system (Phase 2+); In band control of remote transcoders and rate adaptors for half rate traffic channels"
46-12
Issue 02 (2008-06-30)
47 Antenna Hopping
47
About This Chapter
Antenna Hopping
47.1 Overview This describes antenna hopping. Antenna hopping enables the random transmission of downlink data of each carrier on other carriers. This optimizes the data reception of the MS from the main BCCH carrier and the data transmission of the main BCCH carrier, thus improving the network performance. 47.2 Availability This lists the NEs and software required for the implementation of antenna hopping. 47.3 Technical Description This describes the technical aspects of antenna hopping. Through the hopping bus, the data of a carrier can be randomly transmitted on other carriers. Antenna hopping is implemented on the basis of the hopping bus and the antenna hopping algorithm. 47.4 Implementation This describes how to configure antenna hopping. 47.5 Maintenance Information This lists the alarms related to antenna hopping. 47.6 References
Issue 02 (2008-06-30)
47-1
47 Antenna Hopping
47.1 Overview
This describes antenna hopping. Antenna hopping enables the random transmission of downlink data of each carrier on other carriers. This optimizes the data reception of the MS from the main BCCH carrier and the data transmission of the main BCCH carrier, thus improving the network performance.
Definition
Antenna hopping enables the random transmission of downlink data of each carrier on other carriers. During antenna hopping, the data on the main BCCH carrier is randomly transmitted on other carriers, and the data on other carriers is also randomly transmitted on the main BCCH carrier.
Purposes
In a GSM cell, the frequency, frame number, system information, and paging group are transmitted on the BCCH of the main BCCH carrier. These broadcast messages are used by the MS in idle mode to search for a network and by the MS in dedicated mode to measure the neighbor cell. If the MS is located in a place where it is difficult to receive the messages from the main BCCH carrier or if the antenna for the main BCCH carrier is damaged, the MS cannot receive the broadcast control messages from the BCCH carrier properly. Similar to baseband frequency hopping, antenna hopping enables the data of all the timeslots on the main BCCH carrier to be transmitted on the antennas of all the carriers in the cell in sequence. This increases the space diversity of the main BCCH signals, and optimizes the data reception of the MS from the main BCCH carrier and the data transmission of the main BCCH carrier. Therefore, the network performance is improved.
Terms
Terms Hopping Bus Timeslot Interval Definition Data bus that receives the external carrier data in baseband frequency hopping or antenna hopping Hardware interruption every 577 s specified in GSM Rec. 05.02

Acronyms and Abbreviations CA FN
47-2
Full Spelling Cell Allocation Frame Number
Issue 02 (2008-06-30)
47 Antenna Hopping
Acronyms and Abbreviations MAIO HSN MA FH-BUS D-BUS RF TRX
Full Spelling Mobile Allocation Index Offset Hopping Sequence Number Mobile Allocation Frequency Hopping Bus DATA-BUS Radio Frequency Transceiver
47.2 Availability
This lists the NEs and software required for the implementation of antenna hopping.
NEs Involved
Table 47-1 lists the NEs involved in antenna hopping. Table 47-1 NEs involved in antenna hopping MS NOTE
BTS
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 47-2 lists the versions of GBSS products that support antenna hopping. Table 47-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE
Issue 02 (2008-06-30)
Version V900R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases
47-3
DTRU
47 Antenna Hopping
Product QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM
Version BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R001C07 and later releases Not supported currently Not supported currently Not supported currently
Miscellaneous
None.

This describes the technical aspects of antenna hopping. Through the hopping bus, the data of a carrier can be randomly transmitted on other carriers. Antenna hopping is implemented on the basis of the hopping bus and the antenna hopping algorithm. 47.3.1 Hopping Bus This describes the hopping bus. The hardware of antenna hopping is implemented based on the hardware of baseband frequency hopping. 47.3.2 Antenna Hopping Algorithm This describes antenna hopping algorithm. Through the antenna hopping frequency list and the ID algorithm, antenna hopping algorithm ensures that the frequency and data of each frame on the hopping bus is unique and has a one-to-one relation with the carrier number.
47.3.1 Hopping Bus

This describes the hopping bus. The hardware of antenna hopping is implemented based on the hardware of baseband frequency hopping. During baseband frequency hopping and antenna hopping, a large number of data exchanges are performed between different carriers in the same cabinet. The hopping bus is introduced to facilitate data exchanges. When antenna hopping is realized, each carrier sends the TX frequency, TX ID, and data of the current frame to the hopping bus during the timeslot interval. The carrier receives the corresponding frequency and data from the hopping bus and configures the RF based on the frequency. Then, the RF sends the data to the MS over the Um interface. Figure 47-1 shows the position of the hopping bus in the BTS.
47-4
Issue 02 (2008-06-30)
47 Antenna Hopping
Figure 47-1 Position of the hopping bus in the BTS
ANT
FH_BUS TRX1
DBUS
ANT
TRXn
DBUS
47.3.2 Antenna Hopping Algorithm

This describes antenna hopping algorithm. Through the antenna hopping frequency list and the ID algorithm, antenna hopping algorithm ensures that the frequency and data of each frame on the hopping bus is unique and has a one-to-one relation with the carrier number. Build the antenna hopping frequency list based on the frequency information configured on the BSC side. The BTS searches for the frequency from the antenna hopping frequency list when it needs to send the antenna hopping frequency. When calculating the antenna ID, enter the carrier number to calculate an offset based on the frame number and timeslot number of the carrier number, and then obtain an unique antenna hopping ID based on the offset. Figure 47-2 shows the procedure for transmitting the data in antenna hopping.
Issue 02 (2008-06-30)
47-5
47 Antenna Hopping
Figure 47-2 Procedure for transmitting the data in antenna hopping

Start Receives the data to be transmitted No
Antenna hopping or not? Yes Frequency hopping or not? Yes Update the antenna hopping frequency list with frequency hopping frequency list Search for the frequency from the antenna hopping frequency list Calculate the antenna hopping ID Send the data to the frequency hopping bus End
Transmit on the local TRX
No
Update the antenna hopping frequency list with non frequency hopping frequency list
Figure 47-3 shows the procedure for receiving the data in antenna hopping.
47-6
Issue 02 (2008-06-30)
47 Antenna Hopping
Figure 47-3 Procedure for receiving the data in antenna hopping

Start
Check for the data on frequency hopping bus
The data matches the ID of the TRX? Yes Receive the data
No
No handling
Send the data to the MS over the Um interface
End
47.4 Implementation
This describes how to configure antenna hopping. 47.4.1 Configuring Antenna Hopping This describes how to configure antenna hopping on the BSC6000 Local Maintenance Terminal. 47.4.2 Verifying Antenna Hopping This describes how to verify antenna hopping. Antenna hopping is invisible to the MS. To verify antenna hopping, you must use a spectrum analyzer to check whether there are continuous output signals on the main BCCH frequencies on the main BCCH carrier. If the signals are discontinuous, the antenna hopping is enabled.
47.4.1 Configuring Antenna Hopping

This describes how to configure antenna hopping on the BSC6000 Local Maintenance Terminal.
Prerequisite
Antenna hopping is mainly applied in the cells with poor radio propagation conditions and poor Um interface quality.
Context
When baseband frequency hopping and antenna hopping are applied at the same time, adhere to the following principles:
47 Antenna Hopping
l
The number of baseband frequency hopping groups must be the same as that of antenna hopping groups. One carrier number must belong to the baseband frequency hopping group and the antenna hopping group with the same group number.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click the cell where antenna hopping is to be modified, and then choose Configure Cell Attributes from the shortcut menu. Step 2 In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Step 3 Click Next. In the displayed dialog box, select the target cell from the Cells to be set list box, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 47-4. Figure 47-4 Set Cell Attributes dialog box
47-8
Issue 02 (2008-06-30)
47 Antenna Hopping
Step 4 Click Antenna Hopping. A dialog box is displayed. Set CELL Antenna Hopping to YES, and set Group Number, Current Group No., HSN, and corresponding TRXs, as shown in Figure 47-5.
NOTE
l l
Antenna hopping is configured in a cell. Each cell can be configured with more than one antenna hopping group. When a TRX in an antenna hopping group incurs a fault, the BSC requests that antenna hopping be disabled in this antenna hopping group. If the faulty TRX recovers, antenna hopping is enabled in the antenna hopping group.
Figure 47-5 Configure Cell Antenna Hopping dialog box
CAUTION
Do not set HSN to 0 (cyclic hopping), because this leads to low quality of interference source diversity. Step 5 Click OK until the configuration is complete. ----End
47.4.2 Verifying Antenna Hopping

This describes how to verify antenna hopping. Antenna hopping is invisible to the MS. To verify antenna hopping, you must use a spectrum analyzer to check whether there are continuous output signals on the main BCCH frequencies on the main BCCH carrier. If the signals are discontinuous, the antenna hopping is enabled.
47 Antenna Hopping

This lists the alarms related to antenna hopping.
Alarms
Table 47-3 lists the alarms related to antenna hopping. Table 47-3 Alarms related to antenna hopping. Alarm ID 4114 2126 3584 Alarm Name Interior I/O Alarm TRX Interior I/O Alarm DRU Interior I/O Alarm
Counters
None.
47.6 References
l
GSM 05.02 V7.0.0 (1999-03) Digital cellular telecommunications system (Phase 2+); Multiplexing and multiple access on the radio path
GSM 05.02 V7.0.0 (1999-03) Digital cellular telecommunications system (Phase 2+); Channel coding
47-10
Issue 02 (2008-06-30)
48 Voice Quality Index
48
About This Chapter
48.3 Technical Description This describes the technical aspects of VQI.
Voice Quality Index
48.1 Overview This describes the definition and purposes of applying VQI. 48.2 Availability This lists the NEs and software required for the implementation of VQI.
48.4 Implementation This describes how to configure and verify VQI. 48.5 Maintenance Information This lists the counters related to VQI. 48.6 References None.
Issue 02 (2008-06-30)
48-1
48.1 Overview
This describes the definition and purposes of applying VQI.
Definition
Voice Quality Index (VQI) defines the mapping between the radio transmission performance and the voice quality.
Purposes
Through the VQI, the influence of the radio transmission performance on the voice quality can be measured in a direct way.
Terms
Terms MOS analysis Definition A method for assessing the voice quality with 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 and Level 5 the best. CHR CHR is a system for quick fault location. It can record and store the faults during calls for each user on a CHR server. You can query the call history records of a specific user on a CHR client to quickly locate the faults if necessary.

Acronyms and Abbreviatio ns VQI BER FER LFE DTX MOS CHR
48-2
Full Spelling Voice Quality Index Bit Error Ratio Frame Error Rate Longest Consecutive Frame Error Discontinuous Transmission Mean Opinion Score Call History Record
48.2 Availability
This lists the NEs and software required for the implementation of VQI.
NEs Involved
Table 48-1 lists the NEs involved in VQI. Table 48-1 NEs involved in VQI MS BTS BSC MSC MGW SGSN GGSN HLR
NOTE -: not involved : involved
Software Releases
Table 48-2 lists the versions of GBSS products that support VQI. Table 48-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM Version V900R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R001C07 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
None.

This describes the technical aspects of VQI. 48.3.1 Principle of Voice Quality Index This describes the assessment of voice quality with the establishment of the mapping model between the radio transmission performance and the voice quality. 48.3.2 Measurement of Voice Quality 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.
48.3.1 Principle of Voice Quality Index

This describes the assessment of voice quality with the establishment of the mapping model between the radio transmission performance and the voice quality.
VQI model
Figure 48-1 shows the VQI model. Figure 48-1 VQI model
BTS BER FER HO DTX CODE Nonlinear calculation Short-time VQI Handover Nonlinear calculation BSC BSC(traffic statistics)
Long-time VQI
Calculate the average value
VQI
The VQI model involves the following operations: 1. 2. Collecting information about the radio transmission performance, including the BER, FER, and HO. Recording other information, including the DTX and the Codec modes. The DTX is used to filter the valid statistics of the FER/BER/HO; the Codec is used to filter the mapping between the radio transmission performance and the voice quality. Processing the parameters according to the preceding information. Performing nonlinear processing, such as normalizing the BER according to the Codec modes. Performing linear prediction to obtain an estimated VQI score.
3. 4. 5.
The preceding analysis shows that the voice quality is determined by the bit errors and frame errors (including packet loss) information; that is, VQI=F(BER,FER).

l
The principle of the coder determines that the voice quality depends on the erroneous frames and lost frames. The VQI score is related to the FER to the power of x; that is, VQI FERx. The voice quality is related not only to the measurement of FER but also to the distribution of the erroneous frames. Thus, the variable LFE is applied to represent their relation, that is, VQILFE. In the GSM TCH, the frames verified by the 3-bit CRC mechanism might contain residual erroneous codes. Thus, the formula VQIBER should be applied.
In conclusion, the formula for the relation between the VQI and the radio transmission performance is VQI = A BER + B FER + C LEF + Const.
NOTE
In the formula, A, B, and C are the model parameters, and Const is a constant.
Rectification of the VQI Model

To ensure higher credibility of the estimated VQI score, a large number of tests must be performed to yield the data for adjustment and rectification. Figure 48-2 shows the principle of rectifying the VQI model. Figure 48-2 Principle of rectifying the VQI model
RX end Channel decoding Source decoding Channel decoding Multiparameter modeling Channel decoding VQI model
Speech RX
The VQI model is rectified by comparing the radio performance parameters such as BER, FER, and LFE at the receiving end and comparing the voice quality of the received calls.
48.3.2 Measurement of Voice Quality

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.
Obtaining the VQI Information

In each call, when the parameter Voice quality report switch is enabled, the TRX receives the customized extended measurement reports from the BTS every five measurement periods (five measurement periods last 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- 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 for 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 48-3. Table 48-3 Voice quality levels Level Initial level Level 1 Level 2 Level 3 Level 4 Level 5 Level 6 Level 7 Level 8 Level 9 Level 10 Meaning 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 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.
48-6
Issue 02 (2008-06-30)
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
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. 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 deduced by analogy.
48.4 Implementation
This describes how to configure and verify VQI. 48.4.1 Configuring Voice Quality Index This describes how to configure VQI on the BSC6000 Local Maintenance Terminal. 48.4.2 Verifying Voice Quality Index This describes how to verify VQI on the BSC6000 Local Maintenance Terminal.
48.4.1 Configuring Voice Quality Index

This describes how to configure VQI on the BSC6000 Local Maintenance Terminal.
Procedure
Issue 02 (2008-06-30)
48-7
Step 4 Click Other Attributes. A dialog box is displayed, as shown in Figure 48-4. Set Voice quality report switch to report.
48-8
Issue 02 (2008-06-30)
----End
48.4.2 Verifying Voice Quality Index

This describes how to verify VQI on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the Management Tree panel of the BSC6000 Local Maintenance Terminal, select the Trace&Monitor tab. On the tab page, choose Trace > Trace User Message and double-click it. A dialog box is displayed, as shown in Figure 48-5.
Issue 02 (2008-06-30)
48-9
Step 2 Set the parameters Interface Type, Tracing Mode, and Color. Select and fill in the IMSI, TMSI, MSISDN, IMEI, or Channel of the user to be traced. Click OK to start tracing. The result is displayed, as shown in Figure 48-6. Figure 48-6 Result of tracing the user message
48-10
Issue 02 (2008-06-30)
Step 3 Select Preprocessed Measurement Result (If the preprocessed measurement result function is not enabled, select Measurement Result). Double-click it. A dialog box is displayed, as shown in Figure 48-7. Figure 48-7 Message explanation
In Figure 48-7,
l l
if the tlv-type-vqir field exists, it indicates that the BTS reports the VQI information. otherwise, the BTS does not report the VQI information.
----End

This lists the counters related to VQI.
Alarms
None.
Counters
Table 48-4 lists the counters related to VQI.
Table 48-4 Counters Counter S4504 S4505 S4506 S4507 S4513 S4514 S4515 S4516 S4517 S4518 S4519 S4520 S4521 S4522 S4523 Description Number of the Measurements of the FR VQI in the Customized MR Total Number of the Measurements of the FR VQI in the Customized MR Number of the Measurements of the HR VQI in the Customized MR Total Number of the Measurements of the HR VQI in the Customized MR Number of MRs with Speech Quality Smaller than 0.5 in the Customized MR Number of MRs with Speech Quality Between 0.5 and 1.0 in the Customized MR Number of MRs with Speech Quality Between 1.0 and 1.5 in the Customized MR Number of MRs with Speech Quality Between 1.5 and 2.0 in the Customized MR Number of MRs with Speech Quality Between 2.0 and 2.5 in the Customized MR Number of MRs with Speech Quality Between 2.5 and 3.0 in the Customized MR Number of MRs with Speech Quality Between 3.0 and 3.5 in the Customized MR Number of MRs with Speech Quality Between 3.5 and 4.0 in the Customized MR Number of MRs with Speech Quality Between 4.0 and 4.5 in the Customized MR Number of MRs with Speech Quality Between 4.5 and 5.0 in the Customized MR Number of MRs with Speech Quality Greater than 5.0 in the Customized MR
48.6 References
None.
48-12
Issue 02 (2008-06-30)
49 Automatic Noise Restraint
49
About This Chapter
Automatic Noise Restraint
49.1 Overview This describes the definition and purposes of applying the automatic noise restraint (ANR). ANR improves the speech quality in the case that the background noise exists. 49.2 Availability This lists the NEs and software required for the implementation of ANR. 49.3 Technical Description This describes the technical aspects of ANR. The ANR mechanism 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 the filtering based on decision updates to obtain the time speech signals after noise cancellation. 49.4 Implementation This describes how to configure ANR. 49.5 Maintenance Information None. 49.6 References None.
Issue 02 (2008-06-30)
49-1
49.1 Overview
This describes the definition and purposes of applying the automatic noise restraint (ANR). ANR improves the speech quality in the case that the background noise exists.
Definition
ANR processes the uplink speech signals after decoding and filters the background noise.
Purposes
ANR reduces the background noise in the uplink speech signals and improves the SNR and speech intelligibility. Thus, the speech signals are clear on the peer end.
Terms
Terms Speech intelligibility Window Definition Intelligibility of speech information. General method for speech preprocessing, like Haming window.

Acronyms and Abbreviations ANR SNR FFT IFFT TFO Full Spelling Automatic Noise Restraint Signal Noise Ratio Fast Fourier Transform Algorithm Inverse Fast Fourier Transform Algorithm Tandem Free Operation
49.2 Availability
This lists the NEs and software required for the implementation of ANR.
NEs Involved
Table 49-1 lists the NEs related to ANR.
49-2
Issue 02 (2008-06-30)
Table 49-1 NEs related to ANR MS NOTE

BTS -
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 49-2 lists the versions of GBSS products that support ANR. Table 49-2 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
None.

This describes the technical aspects of ANR. The ANR mechanism 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 the filtering based on decision updates to obtain the time speech signals after noise cancellation. The procedure for the ANR is as follows: 1. 2. 3. 4. 5. The system performs weighting and window processing on the speech signals. The system performs FFT to convert time-domain speech signals into frequency-domain speech signals. The system divides the generated frequency speech signals into 16 bands for energy estimation. The system performs the SNR estimation based on the noise energy of each band. After the SNR estimation, each SNR is associated with a sound measurement estimation value. The system accumulates the sound measurement estimation values of 16 bands to obtain the sum. The system performs the frequency offset estimation. (1) The transient energy of each band is expressed in unit dB. (2) The system compares the transient energy with the mean energy of each band.
6.
(3) The system obtains the frequency offset of each band. The accumulated frequency offset of all the bands is the overall frequency offset estimation.
NOTE
The mean energy of each band is calculated through the smooth method. The smooth coefficient is related to the total energy of current frames and must be calculated for each frame.
7. 8.
The signals with a lower sound measurement or lower 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 1.
9.
After the noise identification, the frequency speech signals of each band are weighted by its band gain to complete the frequency filtering.
10. The system restores the time-domain speech signals using the IFFT.
CAUTION
l l l
ANR takes effect in real time. If TFO is activated in a call, ANR automatically becomes unavailable in the call. When you use a speech quality test device (for example, DSLA), disable ANR to obtain the accurate test data.
49.4 Implementation
This describes how to configure ANR. 49.4.1 Configuring ANR This describes how to configure ANR on the BSC6000 Local Maintenance Terminal.
49.4.1 Configuring ANR

This describes how to configure ANR on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC Device Panel of the BSC6000 Local Maintenance Terminal, right-click a GDPUC or a GDPUX, and then select Configure Board Attributes from the shortcut menu. Step 2 In the displayed dialog box, set Load Key, and then click Next. Step 3 In the displayed dialog box, select Configure All and set ANR switch to Open, as shown in Figure 49-1.
49-4
Issue 02 (2008-06-30)
Figure 49-1 Configuring the ANR switch
Step 4 Click Finish. The configuration is complete. ----End
Postrequisite
Make a call from an MS to a fixed telephone. Determine whether the background noise received on the fixed telephone end is reduced and whether the speech quality is improved.

None.
Alarms
None.
Counters
None.
49.6 References
None.
Issue 02 (2008-06-30)
49-5
50 Intelligent Power Consumption Decrease
50
Intelligent Power Consumption Decrease
About This Chapter

50.1 Overview Intelligent power consumption decrease is to decrease the power consumption of the BTS in idle time periods. 50.2 Availability This lists the NEs and software required for the implementation of intelligent power consumption decrease. 50.3 Technical Description Intelligent power consumption decrease refers to a technique in which the system can decrease power consumption by adjusting the working voltage of the configured TRX module, shutting down the power amplifier configured with the TRX module when the TRX module is idle, or shutting down the power amplifier not configured with the TRX module. 50.4 Implementation This describes how to configure intelligent power consumption decrease on BSCs, cells, and TRX modules. 50.5 Maintenance Information The relevant maintenance information on intelligent power consumption decrease is not available. 50.6 References None.
Issue 02 (2008-06-30)
50-1
50.1 Overview
Intelligent power consumption decrease is to decrease the power consumption of the BTS in idle time periods.
Definition
Intelligent power consumption decrease applies to the following scenarios:
l
For the BTS main equipment that does not process services, the dormant mode is started to decrease the power consumption. When the BTS main equipment operates normally and processes services, intelligent power consumption decrease is performed to decrease the power consumption of the BTS in the same coverage.
Huawei BSS products implement intelligent power consumption decrease through the following methods:
l l l
Power-off of power amplifier on the timeslot level Intelligent voltage adjustment Preferential assignment of the BCCH For details about the preferential assignment of the BCCH, see 2 Channel Management. Power control For details about power control, see 6 Power Control. DTX For details about DTX, see 28 Discontinuous Transmission and Discontinuous Reception.
Use of industry-leading power amplifiers
Purposes
When the traffic is light, the power amplifiers of idle TRX modules are shut down to decrease the power consumption of the BTS. In the current network, many cells are in the idle state in most of time of a day. Thus, part of TRX modules are sufficient for carrying the existing traffic. In such a case, the power amplifiers of extra TRX modules can be shut down to save more power. As a result, the operator's operation expenditure is greatly reduced.
Terms
Term GMSK modulation mode XMU Definition Gaussion Minimum Shift Keying modulation mode General name for BTS3012 DTMU, BTS3012AE DTMU, BTS3006C DMCM, and BTS3002E DMCM
50-2
Term 8PSK modulation mode TCHF TCHH
Definition 8 Phase Shift Keying modulation mode Full-rate traffic channel Half-rate traffic channel

Acronym and Abbreviation DTX Full Spelling Discontinuous Transmission
50.2 Availability
This lists the NEs and software required for the implementation of intelligent power consumption decrease.
NEs Involved
Table 50-1 lists the NEs involved in intelligent power consumption decrease. Table 50-1 NEs involved in intelligent power consumption decrease MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 50-2 lists the versions of GBSS products that support intelligent power consumption decrease. Table 50-2 GBSS products and software versions Product BSC BTS
Issue 02 (2008-06-30)
Version BSC6000 BTS3012 DTRU V900R008C01 and later releases BTS3000V100R001C07 and later releases
50-3
Product QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E DBS3900 GSM BTS3900 GSM BTS3900A GSM
Version BTS3000V100R004C02 and later releases BTS3000V100R001C07 and later releases BTS3000V100R004C02 and later releases BTS3000V100R001C07 and later releases BTS3000V100R001C07 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C02 and later releases
Miscellaneous
None.

Intelligent power consumption decrease refers to a technique in which the system can decrease power consumption by adjusting the working voltage of the configured TRX module, shutting down the power amplifier configured with the TRX module when the TRX module is idle, or shutting down the power amplifier not configured with the TRX module.
Dynamic Voltage Adjustment

Dynamic voltage adjustment is a preferred option for the configured TRX module. The actual working voltage of the TRX module is adjusted according to the following configurations:
l
Site type Macro BTS or mini BTS Power types of the TRX module Modulation mode of the TRX module GMSK modulation mode or 8PSK modulation mode Frequency band types of the TRX module Static power class configured for the TRX module
l l
l l
Intelligent Shutdown of the Power Amplifier

Based on the traffic volume, the BSC determines whether to issue a command to switch off the power amplifier of the TRX module to decrease the power consumption of a BTS. 50.3.1 Intelligent Power Consumption Decrease Configured with the TRX Module
This describes the conditions and process of dynamic voltage adjustment, intelligent shutdown of the power amplifier, and power-on of the power amplifier in case one or two carriers are configured. 50.3.2 Intelligent Power Consumption Decrease Not Configured with the TRX Module Intelligent power consumption decrease not configured with the TRX module refers to intelligent shutdown of the power amplifier. 50.3.3 Intelligent Shutdown of the TRX Power Amplifier When selecting TRX modules to be shut down, you need to select the ones that have the longest operation interval and are beyond the power-on protection period to avoid frequent power-on or shutdown of the TRX power amplifier. 50.3.4 Intelligent Shutdown of the TRX Power Amplifier and Channel Assignment The BSC attempts to assign busy channels to a small number of TRX modules and assign calls to the TRX modules that cannot be dynamically shut down. Therefore, call drops and handover times decrease when TRX power amplifiers are shut down.
50.3.1 Intelligent Power Consumption Decrease Configured with the TRX Module
This describes the conditions and process of dynamic voltage adjustment, intelligent shutdown of the power amplifier, and power-on of the power amplifier in case one or two carriers are configured.
Dynamic Voltage Adjustment

Different from the BTS without the TRX module, the BTS with the TRX module needs voltage adjustment. The modulation modes used by the TRX module are categorized into the following types:
l
GMSK modulation mode In GMSK modulation mode, the decrease of working voltage in a permissible range does not affect the output power of the power amplifier. Adjusting the working voltage of the power amplifier can improve the efficiency of the power amplifier and decrease power consumption.
8PSK modulation mode You can determine that the TRX module operates in 8PSK modulation mode only when the following conditions are met:

The TRX supports the EDGE service. More than one PDCH channel is available.
Intelligent Shutdown of the Power Amplifier

After the service of intelligent power consumption decrease is enabled, the system checks the configuration of the TRX module configured with only one carrier within 10 minutes. In such a case, the TRX module can close an unconfigured carrier to save power. The system switches off the power amplifier of the configured TRX module in the following situations:
l
The XMU issues a command to shut down a power amplifier.

Issue 02 (2008-06-30)

l l
The TRX module is locked. A critical alarm is generated on the TRX module.
Once the system detects that a power amplifier is in the closed state for one minute, the system shuts down the power amplifier. This is the mode of delaying the shutdown of a power amplifier.
Power-on of the TRX Power Amplifier

The TRX module immediately switches on the power amplifier of a carrier only when the following conditions are met and the power amplifier is not switched on repeatedly within one minute:
l l
Critical alarms are not generated or are already cleared on the TRX module. The XMU does not issue a command to shut down a power amplifier or the XMU issues a command to switch on a power amplifier. The TRX module is not locked or the TRX is unlocked.
50.3.2 Intelligent Power Consumption Decrease Not Configured with the TRX Module
Intelligent power consumption decrease not configured with the TRX module refers to intelligent shutdown of the power amplifier. The shutdown of the power amplifier not configured with the TRX module is also called immediate shutdown.
NOTE
For details about how to switch on the power amplifier, see 50.3.1 Intelligent Power Consumption Decrease Configured with the TRX Module.
50.3.3 Intelligent Shutdown of the TRX Power Amplifier

When selecting TRX modules to be shut down, you need to select the ones that have the longest operation interval and are beyond the power-on protection period to avoid frequent power-on or shutdown of the TRX power amplifier. You need to record the time of each operation on a TRX module. The operation interval indicates the period between the last operation time and the current operation time. Periodically, the BSC checks whether a cell has sufficient idle channels. If sufficient idle channels are available for a TRX module in a period, select to shut down the power amplifier of the TRX module. The TRX module whose power amplifier should be shut down must meet the following conditions:
l l
The TRX module is in the Normal TRX state. The maximum operation interval of the TRX module is greater than TRX Power-on Protection Time (in Second). After the TRX module is shut down, an idle SDCCH is available for this cell. There is no packet traffic channel on the TRX module. The channel that is experiencing type change does not exist on the TRX module.
l l l
50-6
As the dynamic power-on of the TRX power amplifier performed on the BTS may be delayed, the periodic check for Number of Reserved Idle Channels is added. If the number of idle TCHs in a cell is smaller than Number of Reserved Idle Channels, the BTS switches on the power amplifier of a TRX module. The BTS can shut down the power amplifier of the TRX module only when the number of idle SDCCHs is greater than Idle SDCCH Threshold N1. A concentric cell may cause the forcible handover for intelligent shutdown of the TRX power amplifier or the ping-pong handover of a concentric circle. Therefore, the BSC can issue a command to the BTS to shut down the power amplifier of the TRX module in a concentric cell even though calls are available on the TRX module. When the BTS detects that calls are not available on the TRX module, the BTS shuts down the power amplifier of the TRX module.
50.3.4 Intelligent Shutdown of the TRX Power Amplifier and Channel Assignment
The BSC attempts to assign busy channels to a small number of TRX modules and assign calls to the TRX modules that cannot be dynamically shut down. Therefore, call drops and handover times decrease when TRX power amplifiers are shut down. To avoid the conflict between the channel type change and the shutdown of a power amplifier, prohibit the shutdown of the associated power amplifier during the channel type change. When some TRX modules are idle, the BSC shuts down the power amplifiers of these TRX modules. When the traffic is heavy, the BSC needs to switch on the power amplifiers of some TRX modules in an effort to avoid channel congestion. If the BSC detects that the power amplifier of a TRX module where the directly assigned channels or dynamically adjusted channels are located is shut down when the BSC assigns channels, the BSC issues a command to the BTS, requesting the power-on of the power amplifier.
NOTE
For details about the channel assignment algorithm, see 2 Channel Management.
50.4 Implementation
This describes how to configure intelligent power consumption decrease on BSCs, cells, and TRX modules. 50.4.1 Configuring Intelligent Power Consumption Decrease This describes how to configure intelligent power consumption decrease on the BSC6000 Local Maintenance Terminal.
50.4.1 Configuring Intelligent Power Consumption Decrease

This describes how to configure intelligent power consumption decrease on the BSC6000 Local Maintenance Terminal.
Prerequisite
When the BSC enables the intelligent shutdown of the power amplifier, the BTS checks only the circuit-based services.
Before configuring Allow the Shutdown of the TRX Power Amplifier on the TRX module, ensure that the TRX module meets the following conditions:
l l l
The non-primary BCCH is located on the TRX module. The dynamic or static PDCH does not exist. Antenna hopping or frequency hopping is not enabled.
NOTE
During a BTS deployment test, set Allow Dynamic Shutdown of TRX Power Amplifier to No on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC, configure the intelligent shutdown of the power amplifier.
NOTE
On some special days, such as holidays, do not shut down the power amplifiers of TRX modules. For the dates when the intelligent shutdown of power amplifiers is allowed, you need to set a time segment for each date. You can set 12 dates.
1. 2.
On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick BSC6000, and then choose Configure BSC Attributes from the shortcut menu. In the displayed dialog box, click the Triger Saving Power Function tab, as shown in Figure 50-1. Configure Allow Dynamic Shutdown of TRX Power Amplifier, Time When the Function Is Enabled (HH: MM), Time When the Function Is Disabled (HH: MM), Time for TRX Power-on Protection (in Second), and Number of Reserved Idle Channels.
NOTE
In the Prohibit Close TRX Power Amplifier pane shown in Figure 50-1, set the dates on which the TRX power amplifier cannot be closed.
50-8
Issue 02 (2008-06-30)
Figure 50-1 Triger Saving Power Function tab page
3. 4. 1. 2. 3.
Click Finish. A dialog box is displayed. Click Yes to complete the configuration. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick a cell, and then choose Configure Cell Attributes from the shortcut menu. In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 50-2. Select Allow Dynamic Voltage Adjustment and Allow Dynamic Shutdown of TRX Power Amplifier.
Step 2 Configure intelligent power consumption decrease for cells.
Issue 02 (2008-06-30)
50-9
Step 3 On the TRX module, configure the intelligent shutdown of the power amplifier. 1. 2. 3. On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, rightclick the target TRX, and then choose Configure TRX Attributes from the shortcut menu. In the displayed dialog box, select the target TRX, and then click Configure TRX Attributes. Click the Device Attributes tab and set Allow Shutdown of TRX Power Amplifier to Yes, as shown in Figure 50-3.
50-10
Issue 02 (2008-06-30)
4.
Click OK to complete the configuration.
----End

The relevant maintenance information on intelligent power consumption decrease is not available.
Alarms
None.
Counters
None.
50.6 References
None.
Issue 02 (2008-06-30)
50-11
51 BCCH Dense Frequency Multiplexing
51
BCCH Dense Frequency Multiplexing
About This Chapter

51.1 Overview BCCH dense frequency multiplexing (hereinafter called "Tight BCCH frequency reuse") enables the BCCHs to use fewer frequencies, thus increasing the number of frequencies at the FH layer and expanding the system capacity. 51.2 Availability This lists the NEs and software required for the implementation of tight BCCH frequency reuse. 51.3 Impact The describes the impact of tight BCCH frequency reuse on system performance and on other features. 51.4 Technical Description Tight BCCH frequency reuse involves the following functions: tight BCCH common channel assignment, tight BCCH handover algorithm, and channel assignment for tight BCCH handover. 51.5 Implementation This describes how to configure tight BCCH frequency reuse and disable tight BCCH frequency reuse. 51.6 Maintenance Information This describes the maintenance information related to tight BCCH frequency reuse. 51.7 References There is no reference information about tight BCCH frequency reuse.
Issue 02 (2008-06-30)
51-1
51.1 Overview
BCCH dense frequency multiplexing (hereinafter called "Tight BCCH frequency reuse") enables the BCCHs to use fewer frequencies, thus increasing the number of frequencies at the FH layer and expanding the system capacity.
Definition
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.
Purposes
The tight BCCH frequency reuse technology is applicable to the network with limited frequency resources. It helps to increase the reuse intensity of BCCH frequencies and reduce the number of frequencies used by the BCCHs. Therefore, more frequencies can be used at the FH layer. 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.
Terms
Term BCCH frequency Tight BCCH Definition Frequency where the BCCH is located BCCH Dense Frequency Multiplexing

Acronym and Abbreviation EFL BCCH TCH Full Spelling Effective Frequency Load BroadCast Channel Traffic Channel
51.2 Availability
This lists the NEs and software required for the implementation of tight BCCH frequency reuse.
NEs Involved
Table 51-1 lists the NEs involved in tight BCCH frequency reuse.
Table 51-1 NEs involved in tight BCCH frequency reuse MS

NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 51-2 lists the versions of the GBSS products that support tight BCCH frequency reuse. Table 51-2 GBSS products and software versions Product BSC BSC6000 Version V900R008C01 and later releases
Miscellaneous
None.
51.3 Impact
The describes the impact of tight BCCH frequency reuse on system performance and on other features.

If the load of a cell increases, an MS served by a channel on the non-BCCH frequency may be handed over to a channel on the BCCH frequency, thus increasing the number of handovers in the network.

The impact of this feature on other features is as follows:
l l
Concentric cells do not support tight BCCH frequency reuse. Multiband networks do not support tight BCCH frequency reuse.

Tight BCCH frequency reuse involves the following functions: tight BCCH common channel assignment, tight BCCH handover algorithm, and channel assignment for tight BCCH handover.
Technical Description
In general, the purpose of limiting the BCCH frequency reuse intensity is to ensure good performance of the TCHs on the BCCH frequency. When aggressive frequency reuse is adopted, the interference in the system is increased, thus greatly decreasing the performance of TCHs. This problem can be solved if tight BCCH frequency reuse is enabled. Tight BCCH frequency reuse has the following advantages:
l
Reducing the number of frequencies occupied by the BCCHs, and improving the spectrum utilization Increasing the number of frequencies available for TCHs and for FH, expanding the system capacity without adding new hardware, and saving the costs of adding sites and cells Assigning the TCHs on BCCH frequencies to only the MSs near the BTS, thus improving the voice quality because of less uplink interference Reducing random access failures, and improving the access performance
When tight BCCH frequency reuse is adopted, a cell is classified into different logical layers: TCH layer on the BCCH frequency and FH layer, as shown in Figure 51-1.
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 51-1 Logical layers of tight BCCH frequency reuse
BCCH Frequency coverage area Limit to move to hopping layer Limit to move to BCCH
Call moved to hopping layer if the quality degrades too much
Tight BCCH frequency reuse involves the following functions:

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
If a TCH on non-BCCH frequencies is available, the TCH is preferentially assigned to ensure access performance. If all the TCHs on non-BCCH frequencies are occupied, the TCH on the BCCH frequency is assigned.
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 of a non-BCCH frequency exceeds Load Threshold for TIGHT BCCH HO, the MS with good signal quality and far from the cell edge is handed over to the TCH on the BCCH frequency. Thus, the TCHs on non-BCCH frequencies are reserved for other calls. This ensures the call performance of other calls. The principle of tight BCCH handover algorithm is as follows: During the period specified by TIGHT BCCH HO Watch Time (s), if the period when tight BCCH handover conditions are met exceeds TIGHT BCCH HO Valid Time (s), 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 frequency. Therefore, if the cause of a handover is tight BCCH handover, a TCH on the BCCH frequency should be assigned.
51.5 Implementation
This describes how to configure tight BCCH frequency reuse and disable tight BCCH frequency reuse. 51.5.1 Recommended Configuration of Tight BCCH Frequency Reuse This describes the suggestions for configuring tight BCCH frequency reuse. 51.5.2 Configuring Tight BCCH Frequency Reuse This describes how to configure tight BCCH frequency reuse on the BSC6000 Local Maintenance Terminal. 51.5.3 Disabling Tight BCCH Frequency Reuse This describes how to disable tight BCCH frequency reuse on the BSC6000 Local Maintenance Terminal.
51.5.1 Recommended Configuration of Tight BCCH Frequency Reuse

This describes the suggestions for configuring tight BCCH frequency reuse. 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 reducing the number of frequencies involved in FH. In a network where the frequencies are highly reused and the frequency resources are limited, relatively few frequencies at the FH layer are a capacity bottleneck. No anti-interference technology such as FH is used on BCCH frequencies. If the 3x3 mode is used in BCCH frequency planning, the TCHs on BCCH frequencies have low anti-interference
capabilities, thus increasing the interference in the system. When aggressive frequency reuse is adopted, the performance of TCHs decreases greatly and is unacceptable. In this case, enabling tight BCCH frequency reuse on the BSC side can solve the problem.
51.5.2 Configuring Tight BCCH Frequency Reuse

This describes how to configure tight BCCH frequency reuse on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 Configure channel assignment algorithm parameters. 1. On the BSC6000 Local Maintenance Terminal, right-click the target cell on the Management Tree tab page, and then choose Configure Cell Attributes from the shortcut menu. In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 51-2.
2. 3.
51-6
Issue 02 (2008-06-30)
4.
Click Channel Management. A dialog box is displayed, as shown in Figure 51-3.
Issue 02 (2008-06-30)
51-7
5. 6.
Set TIGHT BCCH Switch to Yes. Click OK to end the configuration.
Step 2 Configure handover algorithm parameters. 1. In the dialog box shown in Figure 51-2, click Handover Data. A dialog box is displayed, as shown in Figure 51-4.
51-8
Issue 02 (2008-06-30)
2. 3.
Set TIGHT BCCH HO Watch Time (s) and TIGHT BCCH HO Valid Time (s). Click Advanced. A dialog box is displayed, as shown in Figure 51-5.
Issue 02 (2008-06-30)
51-9
Figure 51-5 Cell HO Data tab page
4.
Set RX_QUAL Threshold for TIGHT BCCH HO and Load Threshold for TIGHT BCCH HO.
----End
51.5.3 Disabling Tight BCCH Frequency Reuse

This describes how to disable tight BCCH frequency reuse on the BSC6000 Local Maintenance Terminal.
Procedure
Step 1 On the BSC6000 Local Maintenance Terminal, right-click the target cell on the Management Tree tab page, and then choose Configure Cell Attributes from the shortcut menu. Step 2 In the displayed dialog box, double-click the target cell in the Cell view list box to add it to the Selected cells list box. Then, click Next. Step 3 In the Cells to be set list box, select the target cell, and then click Set Cell Properties. A dialog box is displayed, as shown in Figure 51-6.
51-10
Issue 02 (2008-06-30)
Step 4 Click Channel Management. A dialog box is displayed, as shown in Figure 51-7.
Issue 02 (2008-06-30)
51-11
Step 5 Set TIGHT BCCH Switch to No. Step 6 Click OK to end the configuration. ----End

This describes the maintenance information related to tight BCCH frequency reuse.
Alarms
None.
Counters
None.
51.7 References
There is no reference information about tight BCCH frequency reuse.
Issue 02 (2008-06-30)
51-13
52 Intra BSC Soft-Synchronized Network
52
Intra BSC Soft-Synchronized Network
About This Chapter

52.1 Overview The technology of intra BSC soft-synchronized network (hereinafter called "Um interface software synchronization") can convert an asynchronous network into a synchronous network. In cooperation with other related technologies, this technology eliminates the random and unpredictable interference and thus enhances the system capacity. 52.2 Availability This lists the NEs, software, and license required for the implementation of Um interface software synchronization. 52.3 Impact This describes the impact of Um interface software synchronization on system performance and on other features. 52.4 Technical Description The Um interface software synchronization technology adjusts the frame numbers and bit offsets in the frames of the BTSs on the basis of reference BTSs, thus enabling all the BTSs to realize Um interface synchronization. 52.5 Capabilities This describes the capabilities of Um interface software synchronization. 52.6 Implementation This describes how to configure, verify, and disable Um interface software synchronization. 52.7 Maintenance Information None. 52.8 References None.
Issue 02 (2008-06-30)
52-1
52.1 Overview
The technology of intra BSC soft-synchronized network (hereinafter called "Um interface software synchronization") can convert an asynchronous network into a synchronous network. In cooperation with other related technologies, this technology eliminates the random and unpredictable interference and thus enhances the system capacity.
Definition
Um interface software synchronization requires the cooperation of MSs and the BSS to implement the synchronization on the Um interface. For the hardware synchronization, each BTS is equipped with a GPS and the entire network is synchronized through a satellite. In an asynchronous network, the BTSs use different frame numbers and different bit offsets in the frames. In a synchronous network, the BTSs use the same frame number and the same bit offset in the frame.
Purposes
In the existing GSM system, the BTSs are asynchronous with each other. In an asynchronous network, the co-channel interference and the adjacent-channel interference are uncontrollable and different timeslots are overlapped randomly. The timeslot overlap, however, may lead to unnecessary and unpredictable interference. The randomness and unpredictability disable the implementation of some technologies, such as IBCA. In addition, the performance of some technologies, such as ICC and SAIC, is greatly degraded. At present, the Um interface synchronization is realized through hardware synchronization, that is, each BTS is equipped with a GPS. The hardware synchronization, however, increases the cost. To reduce the cost, Huawei introduces the concept of software synchronization, which applies the MSs and the BSS in the network to realize the Um interface synchronization.
Terms
Terms IBCA Definition Interference based channel allocation. The C/I ratios of idle channels are estimated. Then, channels are assigned on the basis of the C/I ratio requirements of calls. At the same time, the newly assigned channels should not bring unacceptable interference to the established calls. The interference elements of the multiple signals received by multiple antennas are associated with co-channel interface (CCI) and inter-symbol interference (ISI). Considering the correlation of these two types of interference, the ICC constructs the two-dimensional combining coefficient matrix to combine the signals according to the maximum signal-to-noise ratio criterion.
ICC
52-2
Issue 02 (2008-06-30)
Terms SAIC
Definition SAIC is applicable to the MS with a single antenna. SAIC is used to reduce the impact of interference on the reception of downlink signals through a signal processing technology. For details of SAIC, refer to the 3GPP R6 protocol. The software synchronization status of the BTS is changed from synchronous with the network to asynchronous with the network. The BTS clock status is changed from locked to other states, such as Capture or Free-run.
BTS loss of synchronization Clock unlocked

Acronym and Abbreviation AB IBCA ICC SAIC Full Spelling Access Burst Interference Based Channel Allocation Interference Cancellation Combining Single Antana Interference Cancellation
52.2 Availability
This lists the NEs, software, and license required for the implementation of Um interface software synchronization.
NEs Involved
Table 52-1 lists the NEs involved in Um interface software synchronization. Table 52-1 NEs involved in Um interface software synchronization MS
NOTE
BTS
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Releases
Table 52-2 describes the versions of GBSS products that support Um interface software synchronization.
Table 52-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU BTS3006C BTS3002E Version V900R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases
Miscellaneous
Um interface software synchronization is available only when a license is obtained.
52.3 Impact
This describes the impact of Um interface software synchronization on system performance and on other features.

After the Um interface software synchronization is achieved, the IBCA function can be performed. This greatly improves the performance of the ICC and SAIC technologies and of the radio-related KPI counters, such as MOS, paging success rate, handover success rate, call drop rate, and traffic volume. The conversion from an asynchronous network to a synchronous network can effectively reduce the interference on the entire network and expand the network capacity.

None.

The Um interface software synchronization technology adjusts the frame numbers and bit offsets in the frames of the BTSs on the basis of reference BTSs, thus enabling all the BTSs to realize Um interface synchronization. 52.4.1 Collecting the Offset Information Between BTSs This describes how to collect the offset information between BTSs. 52.4.2 Synchronizing Two BTSs This describes how to synchronize two BTSs.
52.4.3 Synchronizing the Entire Network This describes how to synchronize the entire network. 52.4.4 Managing the Synchronization Status of BTSs This describes how to manage the synchronization status of the BTSs.
52.4.1 Collecting the Offset Information Between BTSs

This describes how to collect the offset information between BTSs. For the collection of the offset information between BTSs, the MS sends an AB to the BTSs. Then, the BSC obtains the information about the frame numbers, timeslot numbers, and bit offsets in timeslots. The time synchronization of the two BTSs is performed on the basis of the obtained information. See Figure 52-1. Figure 52-1 Collecting the offset information
BTS1 x MS 0 1 2 3 4 5 6 7 x+1
BTS2 0 y 1 2 3 4 5 6 7 y+1
As shown in Figure 52-1, x and y indicate the frame numbers. The procedure for collecting the offset information between BTSs is as follows:
l l l l
The BSC selects an MS within the overlapping area of BTS1 and BTS2. The MS sends an AB. BTS 1 and BTS 2 receive the AB. After receiving the AB, BTS1 and BTS2 report the time when the AB is received, and obtain the frame number, timeslot number, and bit offset in the timeslot. Based on the time information reported by BTS1 and BTS2, the BSC calculates the frame number offset and bit offset between the two BTSs.
NOTE
The MS in the overlapping area of BTS1 and BTS2 is required to collect the offset information. In addition, channels on the cells must be reserved for the synchronization measurement. It is recommended that the information for synchronization be collected when the traffic volume is small.
52.4.2 Synchronizing Two BTSs

This describes how to synchronize two BTSs. Take BTS1 as the reference BTS. Keep the frame number and the offset of BTS1 unchanged. Synchronize BTS2 with BTS1 by adjusting the frame number and the offset. See Figure 52-2.
Figure 52-2 Synchronization of BTSs
BTS1 x BTS2 y BTS2 x BTS2 0 0
1 2
7 x+1
1 2
7 y+1 7
1 2
1 2
7 x+1
As shown in Figure 52-2, x and y indicate the frame numbers. The synchronization procedure is as follows:
l
Frame number synchronization: adjust the frame number of BTS2 to the same value as that of BTS1. Offset synchronization: adjust the offset of BTS2 to the same value as that of BTS1.
NOTE
During the BTS synchronization, call drops may occur. Therefore, when configuring the synchronization tasks, ensure that the synchronization is performed during the hours with the smallest traffic volume.
52.4.3 Synchronizing the Entire Network

This describes how to synchronize the entire network. Synchronize each two BTSs under one BSC so that all the BTSs under the BSC are synchronized, as shown in Figure 52-3. Figure 52-3 Synchronizing the entire network
20 8 19 18 17 7 6 16 9 2 1 5 15 10 3 4 14 11 12 13
The procedure for synchronizing all the BTSs under one BSC is as follows:
1. 2.
Take BTS1 as a reference and synchronize the first circle of BTSs, for example, BTS2BTS7 shown in Figure 52-3, around BTS1. Take each BTS in the first circle as a reference and synchronize two neighbor BTSs in the second circle. If BTS2 is used as a reference, two neighbor BTSs of BTS2, for example, BTS8 and BTS9 shown in Figure 52-3, should be synchronized. Use the same way to synchronize all the BTSs under the BSC.
3.
52.4.4 Managing the Synchronization Status of BTSs

This describes how to manage the synchronization status of the BTSs. Figure 52-4 shows the synchronization procedure and the synchronization status monitoring. Figure 52-4 Synchronization task management
Information to be collected Trigger collection Collection in progress Collection completed BTS out of synchronization BTS reset Clock unlocked Information collected Trigger synchronization Synchronization completed
Before synchronization, all BTSs are in the Information to be collected state. The BSC initiates the measurement of the offsets between each two BTSs and the collection of synchronization information. After the synchronization information is collected, the BTS triggers the adjustment of frame number and offset. After the adjustment, the BTS is in the Synchronized state. If an event incurs loss of synchronization, for example, BTS reset, BTS clock unlocked, clock precision, or other reasons, the BTS state is changed to To Be Collected. In this case, a synchronization of the corresponding BTSs with the network is initiated again.
52.5 Capabilities
This describes the capabilities of Um interface software synchronization. The capabilities of Um interface software synchronization are as follows: For two neighbor BTSs to be synchronized, the offsets between the timeslots should be at most four bits.
52.6 Implementation
This describes how to configure, verify, and disable Um interface software synchronization. 52.6.1 Recommended Configuration of Um Interface Software Synchronization This provides suggestions for configuring Um interface software synchronization.
52.6.2 Configuring Um Interface Software Synchronization This describes how to configure the Um interface software synchronization function on the Local Maintenance Terminal. 52.6.3 Verifying Um interface Software Synchronization This describes how to verify the Um interface software synchronization function on the Local Maintenance Terminal. 52.6.4 Disabling Um Interface Software Synchronization This describes how to disable the Um interface software synchronization function on the Local Maintenance Terminal.
52.6.1 Recommended Configuration of Um Interface Software Synchronization

This provides suggestions for configuring Um interface software synchronization. The recommended configuration of Um interface software synchronization is as follows:
l
Um interface software synchronization 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 coverage should be continuous. Under one BSC, the continuous coverage area can be a set of synchronous BTSs. For an area that is continuously covered by the BTSs under multiple BSCs, Um interface software synchronization is not applicable. At present, the network under a single BSC can be synchronized, and the network under multiple BSCs cannot be synchronized. If Um interface software synchronization is not in cooperation with other algorithms, the interference on certain channels may change from random collision to persistent collision, which leads to the decrease in performance counters on these channels. Therefore, Um interface software synchronization must be used with other technologies, such as network planning or IBCA.
52.6.2 Configuring Um Interface Software Synchronization

This describes how to configure the Um interface software synchronization function on the Local Maintenance Terminal.
Prerequisite
The license is applied and activated. To apply for and activate the license, do as follows: 1. In BSC6000V900R008 Exceptional Commercial License Application Template, set Whether to activate the soft synchronization function or not under License control items to 1. The value 1 indicates that this function is enabled. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Procedure
Step 1 On the Local Maintenance Terminal, enter the command SET AISSCFG.

NOTE
Step 2 Set both Collect Offset Information and Offset Time Adjustment Switch to ON, and set other parameters. Step 3 Run the command. The operation is complete. ----End
52.6.3 Verifying Um interface Software Synchronization

This describes how to verify the Um interface software synchronization function on the Local Maintenance Terminal.
Procedure
Step 1 On the Local Maintenance Terminal, run the command LST AISSCFG. Check whether the related information in the returned messages is correct. Step 2 On the Local Maintenance Terminal, run the command DSP AISSRUNSTATE. Check whether synchronization tasks are performed properly. Step 3 On the Local Maintenance Terminal, run the command DSP BTSSYNCINFO. Check the synchronization status of the BTS. ----End
52.6.4 Disabling Um Interface Software Synchronization

This describes how to disable the Um interface software synchronization function on the Local Maintenance Terminal.
Procedure
Step 1 On the Local Maintenance Terminal, enter the command SET AISSCFG.
NOTE
Step 2 Set both Collect Offset Information and Offset Time Adjustment Switch to OFF. Step 3 Run the command. The operation is complete. ----End

None.
52.8 References
None.
52-10
Issue 02 (2008-06-30)
53 Interface over IP
53
About This Chapter
Interface over IP
53.1 Overview Interface over IP refers to that IP network is used to transmit signaling and speech signals on interfaces. 53.2 Availability This lists the NEs and software required for the implementation of interface over IP. 53.3 Impact This describes the impact of interface over IP on system performance and on other features. 53.4 Technical Description The interface over IP is classified into A over IP, Abis over IP, and Gb over IP. 53.5 Capabilities This describes the capabilities of interface over IP. 53.6 Implementation This describes how to configure A over IP, Abis over IP, and Gb over IP. 53.7 Maintenance Information This lists the alarms and counters related to interface over IP. 53.8 References
Issue 02 (2008-06-30)
53-1
53.1 Overview
Interface over IP refers to that IP network is used to transmit signaling and speech signals on interfaces.
Definition
The BSC supports the following types of interface over IP:
l
A over IP IP network is used to transmit signaling and speech signals on the A interface. The SIGTRAN (SCCP/M3UA/SCTP/IP) protocol stack is applied to the signaling plane, and the RTP/UDP/IP protocol stack is applied to the user plane. When A over IP is enabled, the transcoding from the TRAU of the GTCS to the PCM is performed by the MGW.
Abis over IP IP network is used to transmit signaling and speech signals on the Abis interface. The LAPD Over UPD/IP protocol stack is applied to the signaling plane, and the PTRAU Over UDP/ IP protocol stack is applied to the user plane.
Gb over IP IP network is used to transmit PS service signals on the Gb interface. The Gb over IP protocol stack is applied to the Gb interface.
Purposes
The purposes of interface over IP are as follows:
l
The interface over IP supports hybrid transmission modes and low-speed links. Thus, the topology and transmission mode of IP network are more flexible. Becasue service transmission network and OM network are based on IP network, the cost of operation and management can be reduced. Interface over IP uses the packet switching technique of the IP network. This enables efficient utilization of transmission resources and enables reduction of cost of transmission and devices. IP transmission meets the requirements for future evolution to 3G.
Terms
Terms Association Definition 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.
53-2
Issue 02 (2008-06-30)
Terms BFD
Definition BFD is a simple Hello protocol, similar to the adjacent detection in the route protocol. Two systems periodically sends BFD check messages on the channel between the two systems. If one system does not receive the check messages from the other system for a long time, you can infer that the channel is faulty. Under some circumstances, the TX and RX rates between the two systems need to be adjusted to reduce traffic load. The DiffServ defines the DS field in the ToS byte. The DiffServ also defines a set of packet transfer processing database. The mark of the DS field in a packet and the processing of the DS field generates different service levels. Therefore, DiffServ is actually a strategy of relative priority. 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. PPP, a protocol on the data link layer, provides point-to-point transmission and encapsulates data packets on the network layer. PPP, located in layer 2 of the IP protocol stack, supports point-to-point data transmission on full-duplex synchronous and asynchronous links. RTP, a protocol for end-to-end realtime transmission, provides the RX end with information such as packet serial number for recovering realtime data, and provides communications quality test. SCTP, an end-to-end, connection-oriented protocol that transports data in independent sequenced streams, provides a reliable transmission of user messages between equivalent SCTP users. 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. Stream refer to the directional logical path from one end to anther end in an SCTP link. UDP is a simple data-oriented end-to-end transmission protocol without reliability. The UDP sends the data from one end to another through the IP layer regardless of whether the data can arrive at destinations.
DiffServ
IP protocol
PPP
RTP
SCTP
SIGTRAN
Stream UDP
Issue 02 (2008-06-30)
53-3
Terms VC Trunk VRRP
Definition VC Trunk refers to the logical path formed by some cascaded VCs. VRRP, an Internet protocol, provides one or more than one backup route when static routing is used in local area network.

Acronyms and Abbreviations ASP BFD BMRC BTSCP BTSM BTSTRC CECHM CEGPRS CM CPOS CRDLC DBAPI DBMI DHCP DiffServ EML ESL IPSP M3UA MSIP MSTP OML PBIP Full Spelling Application Server Process Bidirectional Forwarding Detection BM Resource Control BTS Common Processing Base Transceiver Station Management BTS Transmisson Resource Control Cell Channel Management Cell GPRS Processing Configuration Management Channelize Packet Over SDH Call Radio Link Control DataBase API DataBase Management Interface Dynamic Host Configuration Protocol Differentiated Service Extend Operation Maintenance Link Extend Signalling Link IP Server Process MTP3 User Adaptation Layer MS Instance Processing Multiservice Transport Platform Operation Maintenance Link Pb Interface Processing
53-4
Issue 02 (2008-06-30)
Acronyms and Abbreviations PDCH POS RC RR RRM RSL SAPI SCTP SGP SIGTRAN TEI UMG VC Trunk VRRP
Full Spelling Packet Data Channel Packet Over SDH Resource Control Radio Resource Radio Resource Management Radio Signalling Link Service Access Point Identifier Stream Control Transmission Protocol Signalling Gateway Process Signalling Transport Terminal Endpoint Identifier Universal Media Gateway Virtual Container Trunk Virtual Router Redundancy Protocol
53.2 Availability
This lists the NEs and software required for the implementation of interface over IP.
NEs Involved
Table 53-1 lists the NEs involved in interface over IP. Table 53-1 NEs involved in interface over IP MS
NOTE
BTS
BSC
MSC
MGW
SGSN
GGSN
HLR
Software Releases
Table 53-2 lists the versions of GBSS products that support interface over IP.
Table 53-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012AE DTRU QTRU Version V900R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases
Miscellaneous
None
53.3 Impact
This describes the impact of interface over IP on system performance and on other features.

The impact of interface over IP on system performance is as follows:
l
The Abis over IP supports the star topology of built-in PCU and BTS, and does not support the BTS cascade, HubBTS, or TDM/hybrid IP transport. When A over IP is enabled, the functions of the GTCS are taken over by the MGW and the BSC is not configured with the GTCS. The Abis over IP and A over IP support only IPv4.

None

The interface over IP is classified into A over IP, Abis over IP, and Gb over IP. 53.4.1 A over IP The A over IP is a technique where the IP network is used to transmit signaling and speech signals on the A interface. 53.4.2 Abis over IP The Abis over IP is a technique where the IP network is used to transmit signaling and speech signals on the Abis interface.
53.4.3 Gb over IP Gb over IP refers to that when the built-in PCU is used, the PS service signals between the BSC and the SGSN are transmitted over IP network.
53.4.1 A over IP
The A over IP is a technique where the IP network is used to transmit signaling and speech signals on the A interface.
Network Topologies
The A over IP supports the following three network topologies:
l
Direct connection Figure 53-1 shows the network topology of direct connection. Figure 53-1 Network topology for A over IP (direct connection)
MSC server FE/GE transmission Signaling on A interface
BSC
MGW
The network topology of direct connection has the following features:

l
The reliability is high, the cost is low, and the maintenance is easy. A high QoS can be easily realized and the call access can be easily controlled.
Layer 2 network through switches Figure 53-2 shows the network topology of layer 2 network through switches.
Issue 02 (2008-06-30)
53-7
Figure 53-2 Network topology for A over IP (layer 2 network through switches)
MSC Server
Switch FE/GE BSC Switch
Layer2 Network
Switch
l
MGW
Layer 3 network through routers Figure 53-3 shows the network topology of layer 3 network through routers. Figure 53-3 Network topology for A over IP (layer 3 network through routers)
MSC Server
Router
FE/GE BSC Router
IP Network
Router
The previous two network topologies have the following features:
l l l l
MGW
Provides a large-capacity bandwidth and a reliable transmission bearer for the A interface Meets the requirement of GSM evolution for the transport bearer network Adapts to the impact of burst data on the network Satisfies the requirement of a large-scale network because of flexibility
Reliability of the Network Topologies

For the previous network topologies, the BSC provides high reliability for load sharing, involving both inter-board ports and intra-board ports. For the BSC, there are two routes to each
destination IP address at the peer end. If the active route is disrupted, the standby one is functional, as shown in Figure 53-4. Figure 53-4 Reliability of the network topologies for A over IP
BSC
A interface board (active)
Switch
Router
Router
MSC server
IP network
A interface board (standby)
Switch
Router
Router
MGW
Protocol Stack Scheme

When A over IP is enabled, the functions of the GTCS are taken over by the MGW and the BSC does not perform transcoding. The compressed speech coding mode is still used, and thus the transmission bandwidth is reduced on the A interface. When an MS calls another MS in the network, secondary speech coding/decoding can be avoided if the calling and called parties use the same speech coding scheme. Thus, the speech quality is enhanced and the resources are saved. On the A interface, both the signaling plane and the user plane support the IP transmission. The signaling plane uses the M3UA/SCTP/IP protocol stack and the user plane uses the RTP/UDP/ IP protocol stack to bear speech frames, as shown in Figure 53-5. Figure 53-5 Protocol stack scheme for A over IP
Protocol stack for signaling plane MSC server BSSMAP SCCP M3UA SCTP IP FE/GE BSC Voice RTP UDP IP FE/GE
BSC BSSMAP SCCP M3UA SCTP IP FE/GE
Protocol stack for user plane MGW Voice RTP UDP IP FE/GE
A interface
Issue 02 (2008-06-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
A interface
53-9
QoS
The GBSS adopts the following mechanisms to ensure high end-to-end QoS.
l
Physical bandwidth shaping Through the buffer and token bucket, the burst flow in the network is restricted. If the messages are transmitted at a too fast speed, they are buffered and then transmitted at a uniform speed under the control of the token bucket.
Priority mapping A definite rule is used to identify the messages for different services. Then, the messages are classified and prioritized, and they are associated with the corresponding flow control and resource assignment. Based on the load on the current network, a specific flow control action is taken.
Congestion management When the speed for the messages to access the network devices is beyond the transmission capability of the port, congestion occurs and a large amount of network resources are wasted. Improper resource assignment may lead to system deadlock or corruption. Increasing the network bandwidth is a direct method of alleviating resource insufficiency. In addition, congestion avoidance mechanisms are used to avoid congestion. Generally, the tail drop and WRED are used. When congestion occurs, the Priority Queue (PQ) or Weighted Round Robin (WRR) of queue scheduling is used to solve the congestion problem.
Different QoS mechanisms are used for different protocol layers, for example, resource reservation for the application layer, DiffServ for the IP layer, PQ for the data link layer, and LR for the physical layer, as listed in Table 53-3. Table 53-3 Mapping between protocol layer and QoS mechanism Protocol Layer Application layer IP layer Data link layer Physical layer QoS Mechanism Resource reservation DiffServ PQ LR
53.4.2 Abis over IP

The Abis over IP is a technique where the IP network is used to transmit signaling and speech signals on the Abis interface.
Network Topologies
The network topologies for Abis over IP support three transmission modes: MSTP, data network, and satellite link. In these transmission modes, an FE/GE port is provided for the BSC and an FE port for the BTS.
l
MSTP-based IP network topology

53-10
Figure 53-6 shows the MSTP-based IP network topology. Figure 53-6 MSTP-based IP network topology
FE/GE BSC Router
MSTP Router
FE
BTS
This network topology has the following features:

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 interface, thus facilitating BTS upgrade and capacity expansion and enabling the fast deployment for data services of the BTS. The VC trunk function provided by the MSTP network enables the establishment of two VC trunk links between the BTS and the BSC, transmitting real-time service data and non-real-time service data respectively.
Data network-based IP network topology Figure 53-7 shows the data network-based IP network topology.
Figure 53-7 Data network-based IP network topology
BSC FE/GE
Router IP/MPLS/VPN
Switch FE/GE
BSC
BTS
This network topology has the following features:
BTS
The data network can provide a large-capacity bandwidth and a reliable transmission for the Abis interface. The data network can fulfill the evolution from the GSM network to the IP network. The star network topology of satellite earth stations (station + substation) can be used. In this network topology, one station can be accessed by multiple BTSs, as shown in Figure 53-8.
Satellite link-based IP network topology, including the following two scenarios:
Issue 02 (2008-06-30)
53-11
Figure 53-8 Satellite link-based IP network topology (star network topology)
FE SDH/PDH or microwave transmission network BSC Satellite earth substation Satellite earth station Satellite earth substation
BTS
FE BTS
The mesh network topology of satellite earth stations can be used. This network topology is flexible and convenient, as shown in Figure 53-9. Figure 53-9 Satellite link-based IP network topology (mesh network topology)
FE FE/GE Satellite earth station Satellite earth station FE Satellite earth station BTS BTS
BSC

When Abis over IP is enabled, the LAPD Over UPD/IP protocol stack is applied to the signaling plane, and the PTRAU Over UDP/IP protocol stack is applied to the user plane, as shown in Figure 53-10.
53-12
Issue 02 (2008-06-30)
Figure 53-10 Protocol stack scheme for Abis over IP
BTS
Protocol stack for signaling plane
BSC BTS PTRU UDP IP MAC
Protocol stack for user plane BSC PTRU UDP IP MAC
OML/RSL/ ESL/EML LAPD UDP IP MAC
OML/RSL/ ESL/EML LAPD UDP IP MAC
Abis interface
Abis interface
QoS
Refer to QoS in 53.4.1 A over IP.
53.4.3 Gb over IP
Gb over IP refers to that when the built-in PCU is used, the PS service signals between the BSC and the SGSN are transmitted over IP network.
Network Topologies
Figure 53-11 shows the network topologies supported by Gb over IP. Figure 53-11 Network topology for Gb over IP
FE/GE BSC Router
IP Network Router
FE/GE
SGSN
When Gb over IP is enabled, the signals between the BSC and the SGSN are transmitted over IP network, and routers are used to provide layer 3 routing services for the BSC and the SGSN. The bandwidth on the Gb interface is added. Thus, the cost of operation and maintenance is reduced.

When Gb over IP is enabled, FE/GE transmission is applied to the physical layer, NS protocol to layer 2 (Sub NS complies with the IP protocol), and BSSGP to application layer, as shown in
Figure 53-12. For details of the protocol stack for Gb over IP, refer to 19.4.17.1 Description of the Gb Interface. Figure 53-12 Protocol stack scheme for Gb over IP
SGSN
BSC
LLC
BSSGP
BSSGP NS IP FE/GE
NS IP FE/GE
Gb interface
53.5 Capabilities
This describes the capabilities of interface over IP. The capabilities of the interface over IP feature are listed as follows:
l
A maximum of 20 pairs of GFGUA/GOGUA can be configured, with a maximum of 5 pairs in each subrack. They can be configured in only the rear subracks. A maximum of 6,144 speech channels can be provided by the GFGUA/GOGUA. A maximum of 20 pairs of GFGUB/GOGUB can be configured, with a maximum of 5 pairs in each subrack. They can be configured in only the rear subracks. The GTCS does not require the configuration of GFGUB/GOGUB. The number of pairs of GFGUB/GOGUB configured in the main subrack in the case of GOMU is two less than that in the case of GBAM. A maximum of 384 TRXs can be supported by the GFGUB/GOGUB. A maximum of 8 pairs of GFGUGs can be configured. For the capabilities of the Gb interface, refer to 19.5 Capabilities and 20.5 Capabilities.
53.6 Implementation
This describes how to configure A over IP, Abis over IP, and Gb over IP. 53.6.1 Configuring A over IP This describes how to configure A over IP on the BSC6000 Local Maintenance Terminal. 53.6.2 Configuring Abis over IP This describes how to configure Abis over IP on the BSC6000 Local Maintenance Terminal. 53.6.3 Configuring Gb over IP This describes how to configure Gb over IP on the BSC6000 Local Maintenance Terminal.
53.6.1 Configuring A over IP

This describes how to configure A over IP on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The BSC is configured with the GFGUA/GOGUA, which serves as the A over IP interface board. The license is applied and activated. To apply for and activate the license, do as follows: 1. When applying for the A over IP license, ensure that the Number of resources column corresponding to Whether to activate A over IP or not under Function control items row in BSC6000V900R008 (None) Commercial License Application Template is set to 1. Value 1 indicates that this function should be enabled. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Procedure
Step 1 On the Management Tree tab page of the BSC6000 Local Maintenance Terminal, right-click BSC6000 and then select Configure BSC Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 53-13. On the Basic Data tab page, set BSC Subrack Combination Type to IP on A Interface. Figure 53-13 Configure BSC Attributes dialog box
Step 2 Add a GFGUA/GOGUA and configure the related parameters. 1. Add a GFGUA/GOGUA. For details, refer to step 1 described in Configuring the GFGUA/GOGUA.
Issue 02 (2008-06-30)
2.
Configure the following parameters: Ethernet port attributes, QoS attributes, and physical link detect attributes. For details, refer to step 2 described in Configuring the GFGUA/ GOGUA. Configure the device IP address. For details, refer to step 3 described in Configuring the GFGUA/GOGUA. Set Subsystem No., IP Address, and Subnet Mask. Device IP is the logical IP address used for communication. The device IP address is valid for all the ports on the device. The active and standby interface boards must be configured with the same IP address.
3.
4.
Configure the port IP address. For details, refer to step 4 described in Configuring the GFGUA/GOGUA. Set Port No., IP Address, and Subnet Mask. The configuration principles are as follows:
l
The port IP address and the device IP address must be on different network segments.
If the FE transmission is used, one GFGUA can be configured with eight port IP addresses, and the addresses must distribute on different network segments. If the GE transmission is used, one GFGUA can be configured with two port IP addresses, and the addresses must distribute on different network segments.
If active and standby GFGUAs are configured, their port IP addresses should be different and should distribute on the same network segment.
5.
Configure the BSC router. For details, refer to step 5 described in Configuring the GFGUA/GOGUA. Set Destination IP Address, Route PRI, and Gateway IP Address. The configuration principles are as follows:
l
Destination IP Address should be set as the destination network segment but not a single IP address. Gateway should be on the same network segment as the port IP address of the GFGUA. In the case of active and standby boards, add a BSC router after their port IP addresses are configured.
l l
Step 3 Configure the M3UA entities. For details, refer to Configuring the M3UA Entities. 1. 2. Configure the local entity. Set Local Entity Name and OPC (Hex). Configure the destination entity. Set Destination Entity Name and DPC(Hex).
NOTE
If there is no direct physical link between the local entity and the destination entity, you need to configure the STP entity. In this situation, you need to set Using STP to Yes, and then perform the following operations.
3.
Configure the STP entity. Set STP Entity Name and STPC (Hex).
Step 4 Configure the subrack-OSP mapping. For details, refer to Configuring the Subrack-OSP Mapping. According to the OPC (Hex) set in Step 3, configure OSP.
Step 5 Configure the M3UA link set. For details, refer to Configuring the M3UA Link Set. Set Linkset Name and Adjacent DE Name. Step 6 Configure the M3UA route. For details, refer to Configuring the M3UA Route. According to the M3UA entity configured in Step 3 and the M3UA link set configured in Step 5, set Destination Entity Name and Linkset Name. Step 7 Configure the M3UA link. For details, refer to Configuring the M3UA Link. On the M3UA tab page, set Local Port No., Local Address 1, Local Address 2, Peer Address 1, Peer Address 2, Peer Port No., and Priority. Where, Local Address 1 is the device IP address configured in Step 2. In this situation, the configuration is not required. In addition, an M3UA link can be configured only when the device IP address is configured. ----End
53.6.2 Configuring Abis over IP

This describes how to configure Abis over IP on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
The BSC is configured with the GFGUB/GOGUB, which serves as the Abis over IP interface board. The license is applied and activated. To apply for and activate the license, do as follows: 1. In the License control items of the BSC6000V900R008 Exceptional Commercial License Application Template, locate the Number of TRX supporting Abis Over IP row and specify a value in the cell corresponding to the Resource number column. Activate the license on the Local Maintenance Terminal. For details, refer to Activating the BSC License.
2.
Procedure
Step 1 Add a GFGUB/GOGUB and configured the related parameters. 1. 2. Add a GFGUB/GOGUB. For details, refer to step 1 described in Configuring the GFGUB/ GOGUB. Configure the following parameters: Ethernet port attributes, QoS attributes, and physical link detect attributes. For details, refer to step 2 described in Configuring the GFGUB/ GOGUB. Configure the device IP address. For details, refer to step 3 described in Configuring the GFGUB/GOGUB. Set Subsystem No., IP Address, and Subnet Mask. Device IP is the logical IP address used for communication. The device IP address is valid for all the ports on the device. The active and standby interface boards must be configured with the same IP address. 4. Configure the port IP address. For details, refer to step 4 described in Configuring the GFGUB/GOGUB. Set Port No., IP Address, and Subnet Mask.
3.
The configuration principles are as follows:

l
The port IP address and the device IP address must be on different network segments.
If the FE transmission is used, one GFGUB can be configured with eight port IP addresses, and the addresses must distribute on different network segments. If the GE transmission is used, one GFGUB can be configured with two port IP addresses, and the addresses must distribute on different network segments.
If active and standby GFGUBs are configured, their port IP addresses should be different and should distribute on the same network segment.
5.
Configure the BSC router. For details, refer to step 5 described in Configuring the GFGUB/GOGUB. Set Destination IP Address, Route PRI, and Gateway IP Address. The configuration principles are as follows:
l l l
Destination IP Address should be set as the destination network segment but not a single IP address. Gateway IP Address should be on the same network segment as the port IP address of the GFGUB. In the case of active and standby boards, add a BSC router after their port IP addresses are configured.
Step 2 Add a BTS and configure the related parameters. 1. Add a BTS. For details, refer to steps 1 through 5 described in Adding a BTS (IP Transmission Mode). Specify Site Name and Site Type. Set Service Mode to IP. Then, set Logic IP. Adhere to the following principles when configuring the parameters:
l l
Only the BTS3012, BTS3012AE, and BTS3012_II support the IP transmission mode. Only the BTS3012, BTS3012AE, and BTS3012_II can be set to Support Separate. If the Support Separate check box is selected, the BTS3012, BTS3012AE, and BTS3012_ can be configured with the multi-transceiver unit.
2.
Add a cell. For details, refer to steps 6 through 9 described in Adding a BTS (IP Transmission Mode). Set Cell Name and Frequency Band.
NOTE
Ensure that the Frequency Band of the cell should be supported by the TRX board.
3.
Configure the antenna feeder attributes for the DDPU. For details, refer to steps 10 through 13 described in Adding a BTS (IP Transmission Mode). Set Tributary No and the parameters under TRX Transmit and Receive Relationship. The configuration principles are as follows:
l l
At least one TRX should be specified for the downlink tributary. For other tributaries, use the default values or modify them as required. The DDPU has two paths: A and B. The two paths are independent of each other. The data configurations of the DDPU must be consistent with the physical connections, and the frequency band of the TRX must be the same as the frequency band of the DDPU.
4. 5.
Configure the TRX. For details, refer to steps 14 through 18 described in Adding a BTS (IP Transmission Mode). Configure the DDPU attributes. For details, refer to steps 19 through 25 described in Adding a BTS (IP Transmission Mode).
53-18

l
On the PTU parameter of BTS tab page, set Main PTU Bar Code, Back PTU Bar Code, PTU Logical IP, and conPIU IP The configuration principles are as follows:
Back PTU Bar Code and Main PTU Bar Code must be different. They must be unique. If the standby board is not configured, Back PTU Bar Code must be set to a nonzero value. The zero value indicates that the parameter is null.
On the FE port parameter of BTS tab page, set Physical IP Address of Ethernet Port. The configuration principles are as follows:
If the layer 2 networking mode is used, the first physical IP address of the DPTU in the BTS and the physical IP address of the GFGUB in the BSC must be on the same network segment. If the layer 3 networking mode is used, the first physical IP address of the DPTU in the BTS and the port IP address of the router must be on the same network segment.
6.
Configure the cell attributes. For details, refer to steps 26 through 31 described in Adding a BTS (IP Transmission Mode). Set MCC, MNC, LAC, CI, BCC, NCC, Cell Extension Type, and Cell Type. Add a BTS route. For details, refer to the steps described in Adding a BTS (IP Transmission Mode). Set Destination IP Address and Gateway. Where, Destination IP Address is the logical IP address of the DPTU in the BTS; Gateway and the port IP address of the DPTU must be on the same network segment.
7.
----End
53.6.3 Configuring Gb over IP

This describes how to configure Gb over IP on the BSC6000 Local Maintenance Terminal.
Prerequisite
For details, refer to 19.6.2 Configuring GPRS (with Built-in PCU).
Procedure
Step 1 Configure the Gb interface and related parameters. For details, refer to Step 2 in 19.6.2 Configuring GPRS (with Built-in PCU). Step 2 Configure the SGSN. For details, refer to Step 3 in 19.6.2 Configuring GPRS (with Built-in PCU). ----End

This lists the alarms and counters related to interface over IP.
Alarms
Table 53-4 lists the alarms related to interface over IP. Table 53-4 Alarms related to interface over IP Alarm ID 701 702 703 704 705 21525 21526 Alarm Name M3UA Link Fault M3UA Link Congestion M3UA Route Unvailable M3UA Destination Entity Unvailably PIU Route Status Unavailable SCCP DSP Unreachable SCCP Subsystem Prohibited
Counters
Table 53-5 lists the counters related to interface over IP. Table 53-5 Counters related to interface over IP Counter L0031 L0032 L0033 L0034 L0035 L0036 L0021 L0022 L0023 L0011 L0012 L0024 L0025
53-20
Description Data Blocks Retransmitted over SCTP Link Error Packets Received over SCTP Link Data Blocks Sent over SCTP Link Data Blocks Received over SCTP Link Packets Sent over SCTP Link Packets Received over SCTP Link M3UA Link Failure Times M3UA Link Failure Duration M3UA Link Congestion Duration M3UA Destination Inaccessible Times M3UA Destination Inaccessible Duration M3UA Link Sent Packets M3UA Link Received Packets
Counter L01001 L01002 L01003 L01004 L01005 SC010A SC000A SC011A SC001A SC012A SC002A SC003A
Description Received Bytes Received Packets Sent Bytes Sent Packets Error Sent Packets CS Packets Sent over FE Port of the PTU CS Packets Received over FE Port of the PTU PS Packets Sent over FE Port of the PTU PS Packets Received over FE Port of the PTU Control-Plane Packets Sent over FE Port of the PTU Control-Plane Packets Received over FE Port of the PTU Error CRC Packets Received over FE Port of the PTU
53.8 References
.
l
3GPP TS 48.016 General Packet Radio Service (GPRS);Base Station System (BSS) Serving GPRS Support Node (SGSN) interface;Network Service 3GPP TS 23.236 Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes 3GPP TS 48.008 Mobile Switching Centre - Base Station system (MSC-BSS) interface; Layer 3 specification 3GPP TS 48.060 In-band control of remote transcoders and rate adaptors for full rate traffic channels 3GPP TS 48.061 In-band control of remote transcoders and rate adaptors for half rate traffic channels 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 TR 25.953 TrFO/TFO ETSI TS 101 318 Using GSM speech codecs within ITU-T Recommendation H.323
l l
Issue 02 (2008-06-30)
l
RFC 3267 Real-Time Transport Protocol (RTP) Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs RFC 3551 RTP Profile for Audio and Video Conferences with Minimal Control RFC 2198 RTP Payload for Redundant Audio Data RFC 2960 Stream Control Transmission Protocol
l l l
53-22
Issue 02 (2008-06-30)
54 Abis Transmission Optimization
54
Abis Transmission Optimization
About This Chapter

54.1 Overview Different from the traditional resource allocation, where a timeslot or sub-timeslot is allocated to a traffic channel, the Abis transmission optimization allows several links to be multiplexed on a channel composed of several timeslots. The Abis transmission optimization allows more efficient use of transmission resources. 54.2 Availability The Abis transmission optimization can be implemented only with the cooperation of related NEs, the support of certain software releases, and a license. 54.3 Impact This describes the impact of the Abis transmission optimization on the system performance and other features. 54.4 Technical Description This describes the HDLC over E1/T1, HubBTS, HDLC channel, service bearer on the BSC signaling plane and user plane, setup and configuration of the HDLC channel on the BTS maintenance plane and service plane, Abis data uplink technology, Abis data downlink technology, and Abis-interface resource allocation. 54.5 Implementation This describes the application of Abis transmission optimization engineering, including the configuration principles of the HDLC channel, configuration of Abis transmission optimization, and configuration of the HubBTS. 54.6 Maintenance Information The maintenance information for Abis transmission optimization includes the associated alarms and performance counters. 54.7 References None.
Issue 02 (2008-06-30)
54-1
54.1 Overview
Different from the traditional resource allocation, where a timeslot or sub-timeslot is allocated to a traffic channel, the Abis transmission optimization allows several links to be multiplexed on a channel composed of several timeslots. The Abis transmission optimization allows more efficient use of transmission resources.
Definition
The Abis transmission optimization employs the Voice Activity Detection (VAD) to detect and compress the silent voice frames, and uses the High level Data Link Control (HDLC) protocol to transmit data. It allows the CS and PS services of multiple TRXs and signaling messages to be transmitted through an HDLC channel. The HDLC channel is shared by multiple TRXs.
Purpose
According to the attributes of voice, the total bandwidth to be allocated on a shared channel is far less than the sum of the bandwidth required by TRXs in the same configuration. Therefore, the share of the HDLC channel enables more efficient use of resources, optimizing the transmission over the Abis interface.
Terms
Terms Interworking Definition A table that implements protocol termination and conversion through the transmission interface board. The Interworking tables consist of the uplink table and downlink table. Half static An original configuration is generated in data configuration. This configuration can be dynamically adjusted by the resource management module.

Acronyms and Abbreviations BTSM EML ESL HDLC HubBTS OML PTU
54-2
Full Spelling Base Transceiver Station Management Extend Maintenance Link Extend Signalling Link High level Data Link Control Hub Base Transceiver Station Operation Maintenance Link Packet Transfer Unit
Issue 02 (2008-06-30)
Acronyms and Abbreviations RSL SAPI TEI VAD
Full Spelling Radio Signalling Link Service Access Point Identifier Terminal Endpoint Identifier Voice Active Detection
54.2 Availability
The Abis transmission optimization can be implemented only with the cooperation of related NEs, the support of certain software releases, and a license.
NEs Involved
Table 54-1 lists the NEs required to implement the Abis transmission optimization. Table 54-1 NEs involved in the Abis transmission optimization MS NOTE
BTS
BSC
MSC -
MGW -
SGSN -
GGSN -
HLR -
Software Release
Table 54-2 lists the versions of the GBSS NEs involved in the Abis transmission optimization. Table 54-2 GBSS products and software versions Product BSC BTS BSC6000 BTS3012 DTRU QTRU BTS3012A E BTS3006C BTS3002E
Issue 02 (2008-06-30)
Version V900R008C01 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C02 and later releases BTS3000V100R008C01 and later releases BTS3000V100R008C01 and later releases
54-3
DTRU QTRU
Product DBS3900 GSM BTS3900 GSM BTS3900A GSM
Version Not supported Not supported Not supported
Miscellaneous
l
A license is required for implementing the Abis transmission optimization. The license defines the number of TRXs that supports the Abis transmission optimization. Only the BTS3012 and BTS3012AE support the HubBTS. To support the HubBTS, the BTS must be configured with a DPTU. In Abis transmission optimization mode, one E1 supports either 24 TCH/F carriers or 20 TCH/H carriers,one T1 supports either 18 TCH/F carriers or 16 TCH/H carriers.
l l l
54.3 Impact
This describes the impact of the Abis transmission optimization on the system performance and other features.

The Abis transmission optimization does not adversely affect the system performance.

l l
To implement the Abis transmission optimization, the BSC must adopt the built-in PCU. The Abis transmission optimization does not support intra-BSC local switching, intra-BTS local switching, or Flex Abis. The Abis transmission optimization supports BTS cascading.

This describes the HDLC over E1/T1, HubBTS, HDLC channel, service bearer on the BSC signaling plane and user plane, setup and configuration of the HDLC channel on the BTS maintenance plane and service plane, Abis data uplink technology, Abis data downlink technology, and Abis-interface resource allocation. 54.4.1 HDLC over E1/T1 The E1/T1 transmission on the Abis interface is implemented through 64 kbit/s sub-timeslots. The Abis transmission optimization allows one or more (consecutive or non-consecutive) E1/ T1 64 kbit/s sub-timeslots to form a transmission channel that is shared by traffic links. 54.4.2 HDLC Channel This section describes the classification and model of the HDLC channels. 54.4.3 HubBTS
In the sparsely-populated area, the HubBTS networking can save transmission resources. 54.4.4 Service Bearer on the BSC Signaling Plane and User Plane For BTSs that support Abis transmission optimization, the service bearer on the BSC signaling plane and user plane is bound to an HDLC channel in the unit of TRX. All signal streams are transmitted on an HDLC channel. 54.4.5 HDLC Setup on the BTS Maintenance Plane and Service Plane This describes the setup of the HDLC on the BTS maintenance plane and service plane in Abis transmission optimization and HubBTS modes. 54.4.6 Procedure for Transmitting the BTS Uplink Data This describes the procedure for transmitting the BTS uplink data. 54.4.7 Procedure for Transmitting the BTS Downlink Data This describes the procedure for transmitting the BTS downlink data. 54.4.8 Resource Allocation on the Abis Interface This describes the resource allocation on the Abis interface.
54.4.1 HDLC over E1/T1

The E1/T1 transmission on the Abis interface is implemented through 64 kbit/s sub-timeslots. The Abis transmission optimization allows one or more (consecutive or non-consecutive) E1/ T1 64 kbit/s sub-timeslots to form a transmission channel that is shared by traffic links. When TDM transmission is adopted on the Abis interface, each traffic channel, RSL, or OML occupies a 16 kbit/s or 64 kbit/s sub-timeslot. Even when a traffic channel is idle, the sub-timeslot is still occupied. The FlexAbis technology allows the transmission resources on the Abis interface to be allocated based on the demand of traffic channels. When a traffic channel is idle, the system does not allocate any timeslot for it. Thus, the transmission resources on the Abis interface can be reused based on time. Such kind of reuse is implemented through the idle traffic channels in different cells or sites. Generally, the voice activation factor in a conversation is about 0.5. A voice link may have a large number of silent frames and idle timeslots. The time-based FlexAbis technology, however, cannot make use of this voice attribute. The Abis transmission optimization uses HDLC to reuse the transmission resource on the Abis interface. The HDLC mechanism increases the number of TRXs supported by an E1. The reuse of resources is implemented through the large number of silent frames and idle timeslots on the traffic channel. The Abis transmission optimization allows one or more (consecutive or nonconsecutive) E1/T1 64 kbit/s sub-timeslots to form an HDLC channel. Figure 54-1 shows the networking of the system supporting the HDLC over E1/T1 function.
Issue 02 (2008-06-30)
54-5
Figure 54-1 System networking for HDLC over E1/T1

MSC BTS HubBTS BSC HDLC over E1/T1 TDM transmission BTS BTS BTS BTS SGSN FE/GE/FR transmission
54.4.2 HDLC Channel

This section describes the classification and model of the HDLC channels.
Classification
The HDLC channels can be classified into the following:
l
HDLC channels on the Abis interface

HDLC channel between the GEHUB of the BSC and the DPTU of the HubBTS HDLC channels between the GEHUB of the BSC and the DTMU of the BTSs that are directly connected to the BSC HDLC channels between the DPTU of the HubBTS and the DTMU of the lower-level BTSs HDLC channels between the DPTU of the HubBTS and other cabinets in the cabinet group HDLC channels between the main cabinet group and the extension cabinet groups of the BTSs (supporting the Abis transmission optimization) directly connected to the BSC or the lower-level BTSs of the HubBTS
NOTE
HDLC channels in the BTS
The main cabinet group implements transparent transmission of the data from the main cabinet group to the extension cabinet groups over the HDLC channel.
In the BTS cascading, the intermediate HubBTS/BTS implements transparent transmission of the data over the HDLC channel on the Abis interface.
HDLC Channel Model

Figure 54-2 shows the models of the HDLC channel.
54-6
Issue 02 (2008-06-30)
Figure 54-2 HDLC channel model

{TS3,TS4,TS5} E1(0) HDLC connection point HDLC connection point {TS3,TS4,TS5} Direct connection
{TS3,TS4,TS5}
{TS3,TS4,TS5} E1(1)
{TS7,TS8,TS9} E1(3)
{TS7,TS8,TS9} Indirect connection
HDLC connection point HDLC transfer point
HDLC
connection point
In the direct connection, the timeslots TS3, TS4, and TS5 of the two connection points of the HDLC channel exchange information directly. In the non-direct connection, TS3 of E1 (1) exchanges information with TS7 of E1 (3), TS4 of E1 (1) exchanges information with TS8 of E1 (3), and TS5 of E1 (1) exchanges information with TS9 of E1 (3).
54.4.3 HubBTS
In the sparsely-populated area, the HubBTS networking can save transmission resources. After the Abis transmission optimization is implemented, the BTS can be installed with a DPTU board to implement the HubBTS function. The DPTU board converges and transfers data. The HubBTS can converge the data from the BTSs of the same level and the lower-level BTSs. By utilizing the feature that the transmission convergence and resource reuse can bring more gain, the HubBTS enables the most effective use of the Abis transmission resources between the HubBTS and the BSC. The HubBTS also allows proper bandwidth configuration based on the traffic model. Each HubBTS can converge a maximum of 72 TRXs. Figure 54-3 shows the networking of the HubBTS. Figure 54-3 Networking of the HubBTS
MSC BTS HubBTS BSC HDLC over E1/T1 TDM transmission BTS BTS BTS BTS SGSN FE/GE/FR transmission
Issue 02 (2008-06-30)
54-7

NOTE
At present, only the HDLC HubBTS is supported.
54.4.4 Service Bearer on the BSC Signaling Plane and User Plane
For BTSs that support Abis transmission optimization, the service bearer on the BSC signaling plane and user plane is bound to an HDLC channel in the unit of TRX. All signal streams are transmitted on an HDLC channel. The HDLC channel on the Abis interface of the HubBTS is semi-static. When configuring the HDLC channel, first configure the HDLC channel mapping based on the bandwidth of the BTS and TRX. When services are in progress, the BSC resource management module dynamically adjusts the Abis resources to be allocated according to the bandwidth of the current channel. The BSC reads different types of data such as voice service and data facsimile service data in the CS domain and high-priority and low-priority service data in the PS domain according to the priority of subscribers and then sends the data to the BTS through cell attributes. The BTS dispatches and processes the associated types of frames according to the configured priority. The priority ranges from 0 to 7. 0 indicates the highest priority, and 7 indicates the lowest priority. You can configure the priority according to the actual requirements. The parameters are as follows:
l l l l
CS Voice ServicePRI CS Data ServicePRI PS HighPRI ServicePRI PS LowPri ServicePRI
ESL Link
The ESL ensures the reliable transmission of important signaling messages. The ESL link in Abis transmission optimization is only used to transmit the Packet Transfer Unit (PTU) configuration messages in the HubBTS. When the PTU is initiated, the ESL link is used for configuring PTU messages. When the PTU starts to work, the ESL is used to for adjusting the cross connection and transfer control table of the service plane dynamically. On the BSC6000 Local Maintenance Terminal, you can perform message tracing and performance measurement on the ESL link. For details, see Tracing ESL Messages on the Abis Interface.
54.4.5 HDLC Setup on the BTS Maintenance Plane and Service Plane
This describes the setup of the HDLC on the BTS maintenance plane and service plane in Abis transmission optimization and HubBTS modes. In Abis transmission optimization mode, the procedure for HDLC setup on the BTS maintenance plane and service plane is as follows: 1. 2. The BTS sets up the OML link with the BSC. The BTS receives the configuration message on the OML link from the BSC, including the HDLC configuration message and data exchange table. You can obtain the binding relationship between the E1/T1 timeslots on the Abis interface and the HDLC channel numbers and the bearer relationship between the BTS links and the
HDLC channels through the configuration message. Timeslot 31 is bound to a channel for carrying the OML link. 3. The BTS checks whether the configuration data from the BSC is complete and consistent. If the configuration data is consistent, the internal exchange table is generated based on the configuration data and takes effect. The BTS exchanges data according to the exchange table.
l
4.
On the downlink, the BTS receives the data from the Abis interface and searches the destination for exchange according to the address information in the datagram header and the exchange table. On the uplink, the BTS measures the amount of data to be transmitted on each TRX and controls the transmission of uplink data on each link according to the measurement results and the data transmission capability of the HDLC channel.
In Abis transmission optimization mode, the DPTU is added, the procedure for HDLC setup on the BTS maintenance plane and service plane is the same as that in Abis transmission optimization mode except that the initialization procedure for the DPTU is added. The initialization procedure for the DPTU is as follows: 1. 2. The PTU sets up the ESL link with the BSC. The BSC sends the DPTU configuration information, HDLC channel binding relationship, and data exchange table.
54.4.6 Procedure for Transmitting the BTS Uplink Data

This describes the procedure for transmitting the BTS uplink data. The uplink data transmission technology must enable the TRXs to use the resources on the same HDLC channel and ensure successful delivery of data to the HDLC channel. The data transmission procedure in the BTS is as follows: 1. 2. 3. The BTS stores the uplink data to the buffer. The BTS calculates the volume of the data to be sent. The control TRX of the BTS sends data to the Abis interface at the specified time.
Figure 54-4 shows the procedure for transmitting the BTS uplink data.
Issue 02 (2008-06-30)
54-9
Figure 54-4 Procedure for transmitting the BTS uplink data
Start
Set up the OML link with the BSC and receive the HDLC configuration message and data transfer relationship
Set up the HDLC channel on the Abis interface
Take statistics on the data to be transmitted on the HDLC channel
Calculate the amount of data to be transmitted and the time for transmitting data
Is the TRX time up?
No
Yes Transmit the data to the Abis interface
No
Is the transmission stop message received? Yes End
54-10
Issue 02 (2008-06-30)

NOTE
In HubBTS mode, the DPTU is added to converge the data. The procedure for transmitting the BTS uplink data is the same as that for Abis transmission optimization mode.
54.4.7 Procedure for Transmitting the BTS Downlink Data

This describes the procedure for transmitting the BTS downlink data. On the downlink, the BTS constructs the exchange table according to the data exchange relationship sent by the BSC. The BTS exchanges the data on the Abis interface to the specified timeslot according to the exchange table. Figure 54-5 shows the procedure for transmitting the BTS downlink data.
Issue 02 (2008-06-30)
54-11
Figure 54-5 Procedure for transmitting the BTS downlink data

Start
Set up the OML link with the BSC and receive the HDLC configuration message and data transfer relationship
Set up the HDLC channel on the Abis interface and build the downlink data transfer relationship
Generate the data exchange table based on the BSC configuration data
Receive the data from the HDLC channel
Is the destination HDLC searched? Yes Transmit the data to the destination link
No
Discard the data
No
Is the transmission stop message received? Yes End
54-12
Issue 02 (2008-06-30)

NOTE
In HubBTS mode, the DPTU is added to converge the data. The procedure for transmitting the BTS downlink data is the same as that for Abis transmission optimization mode.
54.4.8 Resource Allocation on the Abis Interface

This describes the resource allocation on the Abis interface. Figure 54-6 shows the principle of resource allocation on the Abis interface. The following describes the resource allocation on the Abis interface based on the two BTSs that are connected through an E1 cable. Figure 54-6 Resource allocation on the Abis interface
BSC Abis interface BTS1
HDLC1 TS1-TS10 timeslots HDLC2 TS11-TS29 timeslots BTS2 maintenance signaling is multiplexed on the HDLC BTS1 maintenance signaling is multiplexed on the HDLC OML/EML(ESL) OML/EML(ESL) BTS2
HDLC2
OML/EML(ESL)
The BSC is connected with BTS 1 through an E1 cable, and BTS 1 is cascaded with BTS 2. The data on the user plane and signaling plane of all the TRXs on BTS 1 is multiplexed on HDLC 1. The data on the user plane and signaling plane of all the TRXs on BTS 2 is multiplexed on HDLC 2.
The resource allocation on the Abis interface in Abis transmission optimization mode has the same characteristics as the resource allocation in TDM mode. That is, timeslot 0 is used for synchronization, and timeslot 31 is used for carrying the OML link between the BSC and BTS 1. The difference between the resource allocation on the Abis interface in Abis transmission optimization mode and the resource allocation in TDM mode is as follows: Timeslots 1-10 of BTS 1 are combined to form an HDLC channel. All the TRXs of BTS 1 share this HDLC channel. Not each TRX is allocated with a timeslot.
54.5 Implementation
This describes the application of Abis transmission optimization engineering, including the configuration principles of the HDLC channel, configuration of Abis transmission optimization, and configuration of the HubBTS. 54.5.1 Configuration Principles of the HDLC Channel
This describes the configuration principles of the HDLC channel. 54.5.2 Configuring Abis Transmission Optimization or HubBTS This describes how to configure Abis transmission optimization or HubBTS on the BSC6000 Local Maintenance Terminal.
54.5.1 Configuration Principles of the HDLC Channel

This describes the configuration principles of the HDLC channel. The configuration principles of the HDLC channel are as follows:
l
The HDLC channel can be bound with multiple 64 kbit/s timeslots. The 64 kbit/s timeslots can be discontinuous. The HDLC channel does not support the binding of sub-timeslots. An HDLC channel cannot be configured on two E1/T1 cables. That is, the HDLC channel cannot be configured cross the E1/T1 cables. In E1 mode, the HDLC channel supports the binding of a maximum of 31 timeslots. In T1 mode, the HDLC channel supports the binding of a maximum of 24 timeslots. When the HDLC channel is bound with multiple timeslots, it transmits and receives data according to the sequence of timeslots. Because the timeslots in the middle node use transparent transmission configuration, cross connection must be established according to the timeslot sequence. The HDLC channel must be configured according to the channel type and bandwidth. The continuous HDLC channel is recommended.
54.5.2 Configuring Abis Transmission Optimization or HubBTS

This describes how to configure Abis transmission optimization or HubBTS on the BSC6000 Local Maintenance Terminal.
Prerequisite
l
Apply for the license and activate it. 1. To apply for the license of Abis transmission optimization or HubBTS, enter the number of TRXs that need to support Abis transmission optimization or HubBTS in the specification range in Number of TRXs supporting Abis transmission optimization or Number of HubBTS TRXs supporting HDLC in the Resource control items column in the BSC6000V900R008 Exceptional Commercial License Application Template. Activate the license on the Local Maintenance Terminal. For details, see Activating the BSC License.
2.
l l l
The BTS has the DPTU board, and the BSC has the GEHUB board. There are idle ports on the GEHUB in the GMPS or GEPS. The GXPUM/GXPUT is configured for the GMPS or GEPS where the GEHUB is located.
NOTE
The difference between the HubBTS configuration and the Abis transmission optimization configuration lies in the transmission bearer mode. The transmission bearer mode of the HubBTS is HDLC HubBTS, and that of Abis transmission optimization is HDLC. This operation takes adding a HubBTS transmission mode on the GEHUB in the GEPS as an example.
54-14
Issue 02 (2008-06-30)
Table 54-3 Example of the data negotiated and planned for adding a BTS Parameter Site Attributes Site Name Site Type Upper-Level Port No. Multiplexing Mode FlexAbis Mode Service Mode In Port Config Ring Config AbisByPass Cell attributes Cell Name Frequency Band MCC MNC LAC CI BCC NCC Cell Extension Type Example BTS 1 BTS3012 0 GEHUB Port 4:1 Fix Abis HDLC HubBTS 0 No No Cell 1 GSM900 460 01 8240 1 1 1 Common Cell Source Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning
Issue 02 (2008-06-30)
54-15
Parameter Cell Type TRX Attributes Assigned Cell Freq Config TRX Config FH MODE Antenna feeder attributes Tributary No. Band Type TRX Transmit and Receive Relationship
Example Common Cell Cell 1 988 (main BCCH frequency), 994 TRX 0, TRX 1 None. Downlink Tributary PGSM900 TRX No.1: 0, A TRX No.2: 1, B
Source Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning Network Planning
Procedure
Step 1 Start the wizard for adding a BTS.
l
When adding a BTS for the first time, you can start the wizard for adding a BTS only on the GEHUB in the GMPS or GEPS. On the BSC6000 Local Maintenance Terminal, right-click a GEHUB in the GEPS. If a BTS already exists, you can add a cascaded BTS under this BTS. On the Management Tree tab page, right-click a BTS.
Step 2 Choose Add Site from the shortcut menu. A dialog box is displayed, as shown in Figure 54-7.
54-16
Issue 02 (2008-06-30)
Step 3 Click Add Site. A dialog box is displayed, as shown in Figure 54-8.
Issue 02 (2008-06-30)
54-17
Figure 54-8 Add New Site dialog box
Step 4 Set the parameters by referring to Table 54-3.

NOTE
The Support Separate option is available only for the BTS3012, BTS3012 II, and BTS3012AE. If Support Separate is selected, the BTS3012, BTS3012 II, and BTS3012AE can be configured with the multi-TRX boards.
54-18
Issue 02 (2008-06-30)
Step 6 Click Next. A dialog box is displayed, as shown in Figure 54-10. Figure 54-10 Add Site dialog box (3)
Step 7 Select a BTS, and then click Add Cell. A dialog box is displayed, as shown in Figure 54-11.
Issue 02 (2008-06-30)
54-19
Figure 54-11 Adding a cell
Step 8 Set the parameters by referring to Table 54-3.

NOTE
To add more cells at a time, set Number of Cells. The added cell is named in the form of current Cell Name + sequential number.
Step 9 Click OK. A dialog box is displayed, as shown in Figure 54-12. Figure 54-12 Add Site dialog box (4)
54-20
Issue 02 (2008-06-30)
Step 11 Click Site Attributes. A dialog box is displayed, as shown in Figure 54-14.
Issue 02 (2008-06-30)
54-21
Step 12 Double-click DDPU. A dialog box is displayed, as shown in Figure 54-15.
54-22
Issue 02 (2008-06-30)
Figure 54-15 Set antenna feeder property dialog box
NOTE
l l l
This takes the configuration of one antenna feeder port on the DDPU as an example. If the antenna feeder port is not required, you can delete the DDPU. You have to specify at least one TRX for the downlink tributary of the DDPU. For other tributaries, use the default settings. The DDPU has two paths: A and B. The two paths are independent of each other. The data configurations of the DDPU must be consistent with the physical connections, and the frequency band of the TRX must be the same as the frequency band of the DDPU.
Step 13 Set the parameters by referring to Table 54-3, as shown in Figure 54-16. Figure 54-16 Setting antenna feeder attributes
Issue 02 (2008-06-30)
54-23
Step 14 In the dialog box shown in Figure 54-14, right-click an empty slot in the DTRU and choose Add Board > TRU from the shortcut menu. A TRU is added. Step 15 Right-click the added TRU and choose Configure Board Attributes from the shortcut menu. A dialog box is displayed, as shown in Figure 54-17. Figure 54-17 Binding Logical TRX dialog box
Step 16 Set Assigned Cell by referring to Table 54-3. Step 17 Click OK to return to the dialog box shown in Figure 54-14. Step 18 Repeat Step 14 through Step 17 to configure more TRX boards. Step 19 Click OK to return to the dialog box shown in Figure 54-13. Step 20 Click Next. A dialog box is displayed, as shown in Figure 54-18.
54-24
Issue 02 (2008-06-30)
Step 21 Click Cell Attributes. A dialog box is displayed, as shown in Figure 54-19.
Issue 02 (2008-06-30)
54-25
Step 22 Set the basic attributes of the cell by referring to Table 54-3.
NOTE
l l
The CI of a cell must be unique. If you select GPRS Support, the BSC must be configured with the built-in PCU. If the BTS does not support the GPRS function or the GPRS services are unavailable in the cell, do not select GPRS Support.
Step 23 Click OK to return to the dialog box shown in Figure 54-18. Step 24 Click Finish. The BTS is configured. ----End
54-26
Issue 02 (2008-06-30)

The maintenance information for Abis transmission optimization includes the associated alarms and performance counters.
Alarms
Table 54-4 lists the alarms related to Abis transmission optimization. Table 54-4 Alarms related to Abis transmission optimization Alarm ID 422 423 Alarm Name BTS doesn't support abis optimize Extension Signaling Link Failure
Counters
Table 54-5 lists the performance counters related to Abis transmission optimization. Table 54-5 Performance counters related to Abis transmission optimization Counter S4010A S4010B S4013A S4000A S4000B S4003A S4011A S4011B S4014A S4001A S4001B S4004A S4012A S4012B S4015A
Issue 02 (2008-06-30)
Description Sent CS Packets Sent CS Bytes Sent but Lost CS Packets Received CS Packets Received CS Bytes Received but Lost CS Packets Sent PS Packets Sent PS Bytes Sent but Lost PS Packets Received PS Packets Received PS Bytes Received but Lost PS Packets Sent Signaling-Plane Packets Sent Signaling-Plane Bytes Sent but Lost Signaling-Plane Packets
Counter S4002A S4002B S4005A SD010A SD000A SD011 SD001 SD012 SD002 SD02 SD003
Description Received Signaling-Plane Packets Received Signaling-Plane Bytes Received but Lost Signaling-Plane Packets CS Packets Sent over HDLC Path CS Packets Received Over HDLC Path PS Packets Sent Over HDLC Path PS Packets Received Over HDLC Path Control-Plane Packets Sent over HDLC Path Control-Plane Packets Received over HDLC Path Packets Overflowed over HDLC Path Error CRC Packets Received over HDLC Path
54.7 References
None.
54-28
Issue 02 (2008-06-30)

BSS Feature Description (V900R008C01 - 02)

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BSS Feature Description (V900R008C01 - 02)

Uploaded by

Copyright:

Available Formats

HUAWEI BSC6000 Base Station Subsystem V900R008

BSS Feature Description

Issue Date INTERNAL

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Huawei Technologies Co., Ltd.

Trademarks and Permissions

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

3 Combined BTS Cabinets..........................................................................................................3-1

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

13 Automatic Level Control.......................................................................................................13-1

14 Acoustic Echo Cancellation..................................................................................................14-1

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

24 Cell Frequency Scan..............................................................................................................24-1

26 Local Multiple Signaling Point...........................................................................................26-1

28 Discontinuous Transmission and Discontinuous Reception........................................28-1

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

33 Four-Way Receive Diversity................................................................................................33-1

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

34 SDCCH Dynamic Adjustment............................................................................................ 34-1

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

38 Packet Performance Improvement......................................................................................38-1

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

41 BTS Ring Topology................................................................................................................41-1

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

44 BSC Local Switching.............................................................................................................44-1

45 BTS Local Switching..............................................................................................................45-1

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

48 Voice Quality Index...............................................................................................................48-1

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

49 Automatic Noise Restraint...................................................................................................49-1

50 Intelligent Power Consumption Decrease........................................................................50-1

51 BCCH Dense Frequency Multiplexing..............................................................................51-1

52 Intra BSC Soft-Synchronized Network.............................................................................52-1

53 Interface over IP......................................................................................................................53-1

54 Abis Transmission Optimization........................................................................................54-1

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

HUAWEI BSC6000 Base Station Subsystem BSS Feature Description