You are on page 1of 242

Alcatel 900/1800 BSS

System Description
Descriptive Document System Guide

3BK 02974 AAAA TQZZA Ed. 07

Status Change Note

Released

Short Title System Description All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization from Alcatel.

2 / 240

3BK 02974 AAAA TQZZA Ed. 07

Contents

Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 1.2 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Call Set Up . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.2 Call Handling . . . . . . . . . . . . . . . . . . . . . . . 1.2.3 Call Release . . . . . . . . . . . . . . . . . . . . . . . . 1.2.4 Operations & Maintenance . . . . . . . . . . . BSS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.1 Features Defined in the GSM Recommendations . . . . . . . . . . . . . . . . . . . 1.3.2 Alcatel BSS Features . . . . . . . . . . . . . . . . . . 1.3.3 New Service Improvement Features . . . . BSS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1 Base Station Controller . . . . . . . . . . . . . . . 1.4.2 Base Transceiver Station . . . . . . . . . . . . . . 1.4.3 Transmission Subsystem . . . . . . . . . . . . . . External Components . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5.1 Network Subsystem . . . . . . . . . . . . . . . . . . 1.5.2 Mobile Stations . . . . . . . . . . . . . . . . . . . . . . 1.5.3 Operations and Maintenance Center Radio . . . . . . . . . . . . . . . . . . . . . . . . Network Management . . . . . . . . . . . . . . . . . . . . . . . . . 1.6.1 Telecommunications Management Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6.2 Q3 Interface . . . . . . . . . . . . . . . . . . . . . . . . BSS Telecommunications Layers . . . . . . . . . . . . . . . . . 1.7.1 Call Management . . . . . . . . . . . . . . . . . . . 1.7.2 Mobility Management . . . . . . . . . . . . . . . . 1.7.3 Radio Resource Management . . . . . . . . . 1.7.4 The A Interface . . . . . . . . . . . . . . . . . . . . . . 1.7.5 The Abis Interface . . . . . . . . . . . . . . . . . . . 1.7.6 The Air Interface . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobile Originated Call . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 Radio and Link Establishment . . . . . . . . . 2.2.2 Authentication and Ciphering . . . . . . . . . 2.2.3 Normal Assignment . . . . . . . . . . . . . . . . . . 11 17 18 19 19 20 20 21 21 21 23 25 27 28 28 29 31 31 32 36 37 37 38 39 39 40 40 41 42 43 47 48 50 50 55 55

1.3

1.4

1.5

1.6

1.7

Call Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 2.2

3BK 02974 AAAA TQZZA Ed. 07

3 / 240

Contents

2.3

2.4 2.5 2.6

2.7 2.8

Mobile Terminated Call . . . . . . . . . . . . . . . . . . . . . . . . 2.3.1 Radio and Link Establishment . . . . . . . . . 2.3.2 Authentication and Ciphering . . . . . . . . . 2.3.3 Normal Assignment . . . . . . . . . . . . . . . . . . 2.3.4 IMSI Attach-Detach . . . . . . . . . . . . . . . . . Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.1 Queueing . . . . . . . . . . . . . . . . . . . . . . . . . . 2.5.2 In queue . . . . . . . . . . . . . . . . . . . . . . . . . . . Classmark Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.6.1 Classmark IE . . . . . . . . . . . . . . . . . . . . . . . . 2.6.2 Classmark Updating . . . . . . . . . . . . . . . . . 2.6.3 Location Updating with Classmark Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ciphering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.8.1 Ciphering Keys . . . . . . . . . . . . . . . . . . . . . . 2.8.2 Ciphering Procedure . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . In Call Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2.1 In Call Modification Procedure . . . . . . . . 3.2.2 Group 3 Fax Data Rate Change . . . . . . . 3.2.3 Error Handling . . . . . . . . . . . . . . . . . . . . . . Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.1 Radio Measurements . . . . . . . . . . . . . . . . . 3.3.2 Handover Detection . . . . . . . . . . . . . . . . . . 3.3.3 Target Cell Evaluation . . . . . . . . . . . . . . . . 3.3.4 Synchronous and Asynchronous Handover Overload Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1 BTS Overload . . . . . . . . . . . . . . . . . . . . . . . 3.4.2 BSC Overload . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Release Procedures in Normal Service . . . . . . . 4.2.1 Normal Release . . . . . . . . . . . . . . . . . . . . . 4.2.2 Calls Terminated Following a Channel Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Release - Special Cases . . . . . . . . . . . . . . . . . . . 4.3.1 Call Release Following Reset . . . . . . . . . . 4.3.2 BSC Initiated Release . . . . . . . . . . . . . . . . 4.3.3 BTS Initiated Call Release . . . . . . . . . . . . .

61 61 62 62 64 65 69 69 69 72 72 74 75 77 79 80 81 83 84 85 86 87 88 89 90 91 99 100 107 107 108 111 112 114 114 119 120 120 122 124

Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 3.2

3.3

3.4

Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 4.2

4.3

4 / 240

3BK 02974 AAAA TQZZA Ed. 07

Contents

4.3.4 4.3.5 5 5.1 5.2

MS Initiated Call Release . . . . . . . . . . . . . Remote TC Alarms . . . . . . . . . . . . . . . . . . .

126 127 129

Service Improvement Features . . . . . . . . . . . . . . . . . . . . . . .

5.3

5.4

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Features Defined in the GSM Recommendations . . . 131 5.2.1 Cellular Environment . . . . . . . . . . . . . . . . . 131 5.2.2 RPC Uplink and Downlink . . . . . . . . . . . . 131 5.2.3 Frequency Hopping . . . . . . . . . . . . . . . . . . 135 5.2.4 Discontinuous Transmission . . . . . . . . . . . 138 5.2.5 Discontinuous Reception . . . . . . . . . . . . . . 142 5.2.6 Phase 2 Mobile Support in a Phase 1 Infrastruc ture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 5.2.7 Call Re establishment by the MS . . . . . . . 143 5.2.8 Short Message Service Cell Broadcast . 144 5.2.9 Enhanced Full Rate . . . . . . . . . . . . . . . . . . 144 Alcatel BSS Features . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 5.3.1 Types of Cell Environments . . . . . . . . . . . . 146 5.3.2 Antenna Diversity . . . . . . . . . . . . . . . . . . . . 147 5.3.3 Multiple Human Machine Interface . . . . . 149 5.3.4 Night Time Concentration . . . . . . . . . . . . 151 5.3.5 Secured X.25 Connection From BSC to OMC R . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 5.3.6 Usage State on Demand . . . . . . . . . . . . . . 155 5.3.7 BSC Alerter . . . . . . . . . . . . . . . . . . . . . . . . . 156 New Service Improvement Features . . . . . . . . . . . . . . 158 5.4.1 Power Control due to Radio Link Failure 158 5.4.2 Q3 Multimanager . . . . . . . . . . . . . . . . . . . 158 5.4.3 OMC R Connection to TSC through BSC 158 5.4.4 Abis Signaling Links Static Multiplexing . 159 5.4.5 Transcoder Pools . . . . . . . . . . . . . . . . . . . . 159 5.4.6 Automatic Power Down . . . . . . . . . . . . . . . 160 5.4.7 Auto Identification . . . . . . . . . . . . . . . . . . . 160 5.4.8 Automatic Paging Repetition . . . . . . . . . . . 161 5.4.9 Access to PM Raw Counters via Binary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162 163 164 165 168 169 170 171 172 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.1 Transparent Mode . . . . . . . . . . . . . . . . . . . 6.3.2 Non Transparent Mode . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Handling User Traffic Across the BSS . . . . . . . . . . . . . . . . . 6.1 6.2 6.3

Cell Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1

3BK 02974 AAAA TQZZA Ed. 07

5 / 240

Contents

7.2 7.3 7.4 7.5

Concentric Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sectored Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Extended Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Umbrella Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.1 Mini Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.2 Microcell . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1 BSC O&M Functions . . . . . . . . . . . . . . . . . 8.1.2 BTS O&M (G1 and G2 BTSs) . . . . . . . . . . 8.1.3 BTS A9100 O&M . . . . . . . . . . . . . . . . . . . . 8.1.4 BTS O&M Functions (All Generations) . . 8.1.5 TSC O&M Functions . . . . . . . . . . . . . . . . . 8.1.6 OMC R in O&M Functions . . . . . . . . . . . . O&M Communication Mechanism . . . . . . . . . . . . . . . 8.2.1 O&M Command Flows . . . . . . . . . . . . . . . 8.2.2 Spontaneous Messages . . . . . . . . . . . . . . . Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.1 Alarm Generation . . . . . . . . . . . . . . . . . . . 8.3.2 BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.3 BTS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.4 TSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . Status Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.1 Phases of Board Operations . . . . . . . . . . . 8.4.2 State Change Operations . . . . . . . . . . . . . 8.4.3 States In Traffic . . . . . . . . . . . . . . . . . . . . . . 8.4.4 States Not In Traffic . . . . . . . . . . . . . . . . . . 8.4.5 BSS SBL Operator Commands . . . . . . . . . 8.4.6 Recovery Example: CU Failures with BCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.7 Reset Example: TSC RESET . . . . . . . . . . . . Tracing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.1 Call Tracing . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.2 IMSI Tracing . . . . . . . . . . . . . . . . . . . . . . . . Measurement Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6.1 OMC R Measurement Job Classes . . . . . 8.6.2 Measurement Results . . . . . . . . . . . . . . . . . 8.6.3 Counters . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6.4 Data Collection on the BSC . . . . . . . . . . . 8.6.5 Counter Examples . . . . . . . . . . . . . . . . . . . Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Telecom Parameters . . . . . . . . . . . . . . . . . .

174 175 176 178 178 179 183 184 184 186 187 188 188 190 191 191 193 194 194 195 199 200 201 201 202 203 204 205 207 209 211 211 212 213 213 214 214 216 218 220 222 223

Operations & Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1

8.2 8.3

8.4

8.5 8.6

8.7 8.8

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6 / 240

3BK 02974 AAAA TQZZA Ed. 07

Contents

Appendix A Index

Air Interface Channels . . . . . . . . . . . . . .

229 231

..........................................

3BK 02974 AAAA TQZZA Ed. 07

7 / 240

Contents

Figures
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Figure 24 Figure 25 Figure 26 Figure 27 Figure 28 Figure 29 Figure 30 Figure 31 Figure 32 Figure 33 Figure 34 Figure 35 Figure 36 Figure 37 Figure 38 Figure 39 Figure 40 Figure 41 Figure 42 Figure 43 Figure 44 BSS in the PLMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Base Station Subsystem Components . . . . . . . . . . . . . . . . . . . Transmission Subsystem Components . . . . . . . . . . . . . . . . . . . Logical Position of External Components Associated with BSS Location Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TMN System Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Telecommunication Layers within GSM . . . . . . . . . . BSS Application, Transmission Layers and Interfaces . . . . . . Time Slot 4 of a TDMA Frame Supporting AGCHs . . . . . . . . Radio and Link Establishment for Mobile Originated Call . . SDCCH Channel Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . Immediate Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Connection for Mobile Originated Call . . . . . . . . . . . . . . . . . Normal Assignment for Mobile Originated Call . . . . . . . . . . TCH Channel Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TCH Channel Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Connection for Mobile Originated Call . . . . . . . . . . . . . Radio and Link Establishment for Mobile Terminated Call . . Normal Assignment for Mobile Terminated Call . . . . . . . . . . CCCH with Three Blocks Reserved for AGCH . . . . . . . . . . . . Four TDMA Frame Cycles Providing 24 Paging Sub channels Paging Message Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . Location Update with Classmark Update . . . . . . . . . . . . . . . . Location Update with MS Sending LAI of Previous VLR . . . . . Ciphering Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Quality and Level Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . Better Zone Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Better Cell Handover (Power Budget) . . . . . . . . . . . . . . . . . . . . Distance Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Umbrella Cell Load in Mobile Velocity Dependent Handover Synchronous Internal Handover . . . . . . . . . . . . . . . . . . . . . . . . Asynchronous External Handover . . . . . . . . . . . . . . . . . . . . . . . MS Disconnecting a Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Normal Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Initiation of Normal Release by MSC . . . . . . . . . . . . . . . . . . . . BSC/BTS/MS interactions in Normal Call Release . . . . . . . . . Normal Release Final Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Release Following a Channel Change . . . . . . . . . . . . . . Call Release Following Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC initiated Call Release toward the MSC . . . . . . . . . . . . . . BTS initiated Call Release following LAPD failure . . . . . . . . . Call Release due to MS initiated Radio Link Failure . . . . . . . Call Release due to Communication Failure detected by TC Power Control Flow of Measurement and Decision Action . . 18 27 30 31 35 37 39 40 44 51 52 53 54 56 58 59 60 62 63 65 66 68 75 77 82 93 95 96 97 98 103 106 114 115 116 117 118 119 121 122 125 126 127 134

8 / 240

3BK 02974 AAAA TQZZA Ed. 07

Contents

Figure 45 Figure 46 Figure 47 Figure 48 Figure 49 Figure 50 Figure 51 Figure 52 Figure 53 Figure 54 Figure 55 Figure 56 Figure 57 Figure 58 Figure 59 Figure 60 Figure 61 Figure 62 Figure 63 Figure 64 Figure 65 Figure 66 Figure 67 Figure 68 Figure 69 Figure 70 Figure 71 Figure 72 Figure 73 Figure 74 Figure 75 Figure 76 Figure 77 Figure 78

Power Output Balancing Based on Received Quality and Signal Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Frequency Hopping within an FHS . . . . . . . . . . . . . . . . . . . . . . 137 Different Forms of Discontinuous Transmission . . . . . . . . . . . 141 Short Message Service Cell Broadcast . . . . . . . . . . . . . . . . . 144 Antenna Diversity on G1 and G2 BTSs . . . . . . . . . . . . . . . . . . 147 Antenna Diversity on the BTS A9100 (1 Sector, 3X4 Transceiver Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Multiple HMI Access to OMC Rs . . . . . . . . . . . . . . . . . . . . . . . 149 Night Time Concentration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 X.25 Without Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 X.25 With Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 Encoded Speech Transmission Across the BSS . . . . . . . . . . . . 165 Multiplexed Ater Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Data Transmission Across the BSS . . . . . . . . . . . . . . . . . . . . . . 168 Example: Cell Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Sectored site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Example of Extended Cell Topology . . . . . . . . . . . . . . . . . . . . . 177 Umbrella Cell with Mini Cells . . . . . . . . . . . . . . . . . . . . . . . . . . 178 Example: Handovers due to Threshold Triggering . . . . . . . . . 180 BSC O&M Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 O&M Components and Data Flow in the G1 and G2 BTS . 186 O&M Components and Data Flow in the BTS A9100 . . . . . . 187 Transmission System O&M Components . . . . . . . . . . . . . . . . . 189 Example: Message Flow Using CMISE . . . . . . . . . . . . . . . . . . 191 Example: BSC Command Flow . . . . . . . . . . . . . . . . . . . . . . . . 192 RSL Correlation on the Abis Interface . . . . . . . . . . . . . . . . . . . 196 Example: Alarm Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198 States and Phases of Board Operation . . . . . . . . . . . . . . . . . . 202 Relationship Between SBL States . . . . . . . . . . . . . . . . . . . . . . . . 204 Example: Loss of CU Holding BCCH. . . . . . . . . . . . . . . . . . . . 209 TSC Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Counter Object Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Data Collectors within the BSC . . . . . . . . . . . . . . . . . . . . . . . . . 217 Example: Counter Object Tree . . . . . . . . . . . . . . . . . . . . . . . . . 219 Channels and Their Direction of Flow . . . . . . . . . . . . . . . . . . . 230

3BK 02974 AAAA TQZZA Ed. 07

9 / 240

Contents

Tables
Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 System Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . Types of Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Set Up Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell List Identifier and Paging Performed . . . . . . . . . . . . . . . . Paging Request Message and MS Identification . . . . . . . . . . . Classmark Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Classmark Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS Ciphering Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . Radio Link Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MS Maximum and Minimum Power Ranges . . . . . . . . . . . . . . Downlink DTX Status in Channel_activation . . . . . . . . . . . . . . Operator DTX Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BSC Alerter Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Rate Conversions Across the Air Interface . . . . . . . . . . . O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Functional Unit States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SBL O&M Operator Commands . . . . . . . . . . . . . . . . . . . . . . . Measurement Job Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audit Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 48 49 67 67 72 74 79 133 135 139 140 157 169 185 201 206 213 220

10 / 240

3BK 02974 AAAA TQZZA Ed. 07

Preface

Preface
Purpose
This document provides detailed descriptions of the functions and features of the Alcatel 900/1800 Base Station Subsystem (BSS). Some functions and features may not be available on the system installed at your location. The technical information in this document covers:
"

Mobile Communications Support These areas describe how the BSS handles communications between a Mobile Station (MS) and the Network Subsystem (NSS). It follows a call through the Alcatel BSS, and describes how each element in the system functions individually and with other elements. This shows how the BSS and its units react as a system.

"

Operations and Maintenance These areas describe the Operations and Maintenance (O&M) functions within the system. It describes both local and distributed O&M functions in a BSS.

Audience

This manual is for people requiring an in depth understanding of the functions of the Alcatel BSS:
"

Network decision makers who require an understanding of the underlying functions of the system, including:
D D D

Network planners Technical design staff Trainers.

3BK 02974 AAAA TQZZA Ed. 07

11 / 240

Preface

"

Operations and support staff who need to know how the system operates in normal conditions, including:
D D D D

Operators Support engineers Maintenance staff Client Help Desk personnel.

Assumed Knowledge

The document assumes that the reader has an understanding of:


" " "

Global System for Mobile Communications (GSM) Mobile Telecommunications Network Management concepts and terminology.

Related Documents

Refer to the following O&M and descriptive documentation for more information about the Alcatel 900/1800 BSS/Operations and Maintenance Center Radio (OMC R) and the BSS units:
" " " " " " " " " " " " " " " " " "

Operations & Maintenance Principles Operations & Maintenance Reference Guide Operator Handbook BSC Terminal User Guide BTS A9100 Terminal User Guide BSS Alarm Dictionary NMC and OMC R Interworking OMC R Configuration Management Services OMC R Fault Management Services OMC R Performance Management Services BTS Functional Description BTS Software Description BTS A9100 Functional Description BTS A9100 Software Description G1 BSC Functional Description G2 BSC Functional Description G2 Transcoder Functional Description BSC Software Description.

12 / 240

3BK 02974 AAAA TQZZA Ed. 07

Preface

Conventions

This section describes the type fonts and character styles used in the document to indicate different types of messages. Convention Type message_types PARAMETER_TYPES Meaning Messages are shown in lower case bold italic type. Parameters which are part of a message or protocol are shown in upper case italic characters. Commands are shown in upper case characters. These brackets indicate a message pair consisting of a message followed by an acknowledgement for that message.

COMMANDS {}

Chapter Description

This section provides a brief description of the contents of each chapter. Chapter 1 Introduction, provides a brief overview of the Alcatel BSS, its functions and features. It describes: G G G Chapter 2 The internal and external components and interfaces An MS and its interaction, in idle mode, with the BSS The distribution of telecommunications software in the BSS.

Call Set Up, provides an overview of how a call is set up between the NSS and the MS. It details the various kinds of calls that can be set up. The type of teleservice and bearer service required are also explained. The chapter further describes the following parts of the call procedure: G G G G G G G Mobile Originated Call Mobile Terminated Call Paging Congestion Classmark Handling Authentication Ciphering.

3BK 02974 AAAA TQZZA Ed. 07

13 / 240

Preface

Chapter 3

Call Handling, provides an overview of Call Handling and explains the supervision of a call in progress. It describes: G In call modification, i.e. the process of changing from and to data and speech, and the implications for the system. Handover procedures, the underlying reasons for handover, and the measurements used to detect the need for handover. Overload conditions.

G Chapter 4

Call Release, provides an overview of Call Release and describes the procedures which ensure resource allocation to a call. It specifically describes Call Release procedures in normal service plus the following special cases: G G G G Following Reset BSC initiated BTS initiated MS initiated.

This chapter also describes Remote TC Alarms, and the processes used to break a connection and disconnect the resources, depending on the nature of radio transmission. Chapter 5 Service Improvement Features, provides an overview of the BSS Service Improvement Features. It describes how these features improve the quality of service between the MS and BSS, maximize the BSS and MS resources or increases operator efficiency. The service improvement features in the Alcatel BSS are classed as follows: G G Features defined in the GSM recommenda tions Alcatel BSS Features.

In addition, service improvement features which are new with the current BSS are described in a separate section.

14 / 240

3BK 02974 AAAA TQZZA Ed. 07

Preface

Chapter 6

Handling User Traffic Across the BSS, describes the flow of speech and data traffic across the BSS. It describes: G G G G How speech is encoded and rate adapted throughout the BSS What types of data can be transferred across the BSS Where data error correction is performed How the data rate is adapted.

Chapter 7

Cell Environments, describes the cell environments available in the Alcatel 900/1800 BSS. The following cell environments are described: G G G G G G G Single Cell Concentric Cell Sectored Site Extended Cell Umbrella Cell Mini Cell Microcell.

Chapter 8

Operations and Maintenance, provides an overview and explains O&M functions in the context of an operational network. It describes: G G G G G G G O&M Communication Mechanism Alarms Status Changes Call and International Mobile Subscriber Identity (IMSI) Tracing Measurement Jobs Audits Modifying Telecom Parameters.

Abbreviations Abbreviations are defined at their first use, and listed after the last chapter.

3BK 02974 AAAA TQZZA Ed. 07

15 / 240

Preface

Appendix A

Air Interface Channels, provides an overview of the different channels used in the Air Interface: G G G G G Traffic channels Broadcast channels Common Control channels Dedicated channels Associated channels.

Index

An Index is included at the end of the document.

16 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1 Introduction
This chapter gives a brief overview of the Alcatel BSS, its functions and features. It describes: G G G The internal and external components and interfaces An MS and its interaction, in idle mode, with the BSS The distribution of telecommunications software in the BSS.

3BK 02974 AAAA TQZZA Ed. 07

17 / 240

1 Introduction

1.1

Overview
The BSS provides radio coverage for GSM subscribers in a defined area. Its principal role is to provide and support signaling and traffic channels between MSs and the NSS. Figure 1 shows the BSS within the Public Land Mobile Network (PLMN).
PLMN

Mobile Stations

Base Station Subsystem

Network Subsystem

Fixed Network

BTS

TSS

BSC

TSS

MSC

PSTN

OMC R PSTN = Public Switched Telephone Network OMC R = Operations & Maintenance Center Radio NMC = Network Management Center TSS = Transmission Subsystem

NMC

Figure 1

BSS in the PLMN To respond to the swiftly evolving needs in BSSs, Alcatel offers the EVOLIUM Radio Solutions. The Alcatel EVOLIUM Radio Solutions includes the following BSS equipment described in this document:
" " " "

EVOLIUM Radio Solutions

G2 Base Station Controller (BSC) G2 Transcoder (TC) BTS A9100 Base Transceiver Station Micro Base Transceiver Station (Micro BTS) M1M and M2M.

18 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1.2

BSS Functions
Functions are defined by the International Telecommunications Union (ITU) and European Telecommunication Standards Institute (ETSI) recommendations. This section describes the BSS functions with a system wide view; that is, how the BSS functions work together within the system. The functional units are indicated where applicable, but are not described. For more information, refer to the specific unit description manuals, such as the BTS Functional Description. The BSS provides signaling and traffic channels between the MS and the NSS. To ensure a high level of service to the subscribers, the BSS offers the following functions:
" " " "

Call Set Up Call Handling Call Release Operations & Maintenance.

1.2.1

Call Set Up
The Call Setup function is used for speech and data calls. The three basic types of call are:
" " "

Mobility Management Supplementary service User traffic.

Mobility Management Calls Supplementary Service Calls User Traffic Calls

Mobility Management calls, such as location update, are used by the system to gather Mobile Station information. The exchanges are protocol messages only. Therefore, only a signaling channel is used. Supplementary service calls, such as Short Message Service (SMS) allows the Mobile Station to send and receive messages to and from the BTS. These calls pass small amounts of information. Therefore, only a signaling channel is used. User traffic calls, such as speech or data calls to a correspondent, can pass large amounts of information. Therefore, they require greater bandwidth than a signaling channel. These calls use traffic channels.

3BK 02974 AAAA TQZZA Ed. 07

19 / 240

1 Introduction

Call set up processes include:


"

Radio and Link Establishment to assign a signaling channel between the MS and the NSS Classmark handling to manage different MS power and ciphering capabilities Ciphering to ensure data security on the Air Interface The normal assignment process to assign a traffic channel between the MS and the NSS.

"

" "

Refer to Chapter 2 for more information on call set up.

1.2.2

Call Handling
The call handling function is used when a call moves to another cell, or moves to and from data and speech. Call handling involves:
" "

In call channel modification during a call Handover to change channels when an MS moves from one cell to another Handover when the quality of the current channel drops below an acceptable level Ciphering to ensure data security on the Air Interface Overload control to manage the call load on the system.

"

" "

Refer to Chapter 3 for more information on call handling.

1.2.3

Call Release
The call release function ensures that resources allocated to a call are free for reuse when they are no longer required by the current call. Specifically the Call Release function includes:
"

Call Release in normal service: D Calls terminated by call management D Calls terminated following a channel change. Special Cases: D Call release following a reset D BSC initiated release D BTS initiated release D MS initiated release.

"

Refer to Chapter 4 for more information on call release.

20 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1.2.4

Operations & Maintenance


O&M provides the operator interface for the management and control of the BSS, and its interconnection to the NSS. O&M is divided into three principal areas:
" " "

Configuration Management Fault Management Performance Management.

Refer to Chapter 8 for more information concerning O&M.

1.3

BSS Features
There are two categories of Features in the Alcatel BSS:
" "

Features defined in the ITU and ETSI GSM recommendations Alcatel BSS Service Features.

Note

Some of these features may not be available on your system.

1.3.1

Features Defined in the GSM Recommendations


The Alcatel BSS supports the following features, defined in the ITU and ETSI GSM recommendations:
" " " " " " " "

Cellular environment Radio Power Control (RPC) uplink and downlink Frequency Hopping (FH) Discontinuous Transmission/Voice Activity Detection (DTX/VAD) Discontinuous Reception (mechanism) (DRX) Call re establishment by the MS Short Message Service Cell Broadcast (SMS CB) Enhanced Full Rate (EFR).

Cellular Environment

The standard developed by the Groupe Speciale Mobile specifies a digital cellular network, as described in the System Introduction document. For details on cell environments offered in the Alcatel BSS, refer to Chapter 7.

3BK 02974 AAAA TQZZA Ed. 07

21 / 240

1 Introduction

RPC Uplink and Downlink

This feature ensures the dynamic balance between the quality of the radio link in the uplink and downlink directions. It protects against interference with other cells and contributes to power conservation. The balance is maintained by controlling the power output level to balance the reception power level and reception quality. FH is implemented within the system to reduce the limiting factor that frequency reuse can introduce. This feature improves the capability of coping with adjacent channel interference and improves security. FH provides Frequency Diversity and Interface Diversity. Two types of Frequency Hopping are available:
" "

Frequency Hopping

Baseband Frequency Hopping Synthesized Frequency Hopping

Discontinuous Transmission/Voice Activity Detection Discontinuous Reception

DTX/VAD is used to decrease the average interference level generated by the network in both the uplink and downlink directions. This feature, in association with frequency hopping, significantly improves spectrum efficiency without jeopardizing the quality of the telephony service. DRX is used to conserve battery power. It allows the MS to switch off its receiver and data processing while in the idle mode. The receiver and data processing of the MS is only switched on for a short time when the MS expects a message from the BTS. Instead of the MS listening continually on the Paging Channel (PCH) sub channel Common Control Channel (CCCH) for a paging message, it only listens to that part of the PCH which corresponds to its paging group. Power conservation is achieved by implementing an off/on ratio of 98 to 2. Call Re establishment by the MS allows an MS to resume a connection in progress after a radio link failure. This is possible only if there remains at least one active call control connection between the MS and MSC.
" " "

Call Re establishment by MS

Complete redundancy OMC R side redundancy BSC side redundancy.

Short Message Service Cell Broadcast

SMS CB allows messages to be broadcast to the MSs. This service can be used for a number of reasons, e.g. to transmit taxation information, road traffic information, etc. An SMS CB message can be transmitted to all the cells connected to the BSC, or to selected cells only, as required.

22 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

Enhanced Full Rate

EFR allows the use of codecs with an improved speech encoding algorithm, which provides enhanced speech quality on full rate channels.

1.3.2

Alcatel BSS Features


This section provides an outline of features provided in the Alcatel BSS. These features are designed to:
" " "

Improve the quality of service between the MS and BSS Maximize resources Increase operator efficiency. Types of cell environments Antenna diversity Antenna pre amplifier Improved Multipath Delay Equalization Minimum Frequency spacing Multiple Human Machine Interface (HMI) access to OMC Rs Night Time Concentration (NTC) Secured X.25 connection from BSC to OMC R Usage state on demand BSC alerter.

Features supported include:


" " " " " " " " " "

Types of Cell Environments

Several types of cell environments are available in the Alcatel BSS. This availability means that cells can be configured to meet the requirements of geography and the strategies of the Network Operator. Refer to Chapter 7 for more information concerning Cell Environments.

Antenna Diversity

Antenna Diversity is used to improve the performance of the radio path in the uplink direction in large cell configurations. Protection against multipath fading is achieved by duplicating the receive antenna and receive path up to the Frame Unit (FU) of the BTS (or the Transceiver Equipment (TRE) for a BTS A9100). The FU (or TRE) uses the data burst which has the fewest errors. This increases the low power MS range, therefore allowing larger cells. Antenna pre amplifier equipment is used to improve the sensitivity of the BTS, which results in better coverage. The use of this equipment allows the adaptive power control to reduce the output power of the MSs. This results in a reduced overall interference level in the network.

Antenna Pre Amplifier Equipment

3BK 02974 AAAA TQZZA Ed. 07

23 / 240

1 Introduction

Improved Multipath Delay Equalization Minimum Frequency Spacing Multiple Human Machine Interface

This feature is used to capture more signal content in the signal received by the BTS. This improves the system sensitivity of the BTS. This feature prevents the limitation of frequency assignment by keeping the frequency spacing between two carriers as small as possible. With a multiple HMI workstation, one operator performs network management actions usually done from several OMC Rs. This feature is mainly intended to provide off duty hours access to the network. The connection between the multiple HMI workstation and the other OMC R hosts is made via an X.25 network. The NTC feature is a process within the HMI server. The feature allows an operator to perform alarm management operations for a complete network, where the network consists of more than one OMC R. Link failures can occur on either the OMC R or BSC side. The Secured X.25 Connection feature provides redundant links in the event of a link failure. When a link failure occurs the initiator system involved must process the change over. The OMC R operator can display information on the current resource usage at the BSC. A request for overall information gives the availability and ratio of busy/available resources for each cell and Digital Trunk Controller (DTC) of the BSS. This display is refreshed periodically. A request for detailed information gives the ratio of busy/available resources for a restricted number of cells and DTCs. This information is presented as a single snapshot of resource usage. The BSC Alerter is a supervision function generating an alarm event when the system suspects abnormal behavior of a resource. An Alerter, activated in a BSC, functions by monitoring and computing the levels of specific Performance Management counters. If a count exceeds predefined parameters, the Alerter generates a single alarm, which is sent to the operator.

Night Time Concentration Secured X.25 Connection from BSC to OMC R Usage State on Demand

BSC Alerter

24 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1.3.3

New Service Improvement Features


Alcatel has introduced the following new service improvement features with the current BSS:
" " " " " " " " " "

Power control due to radio link failure Q3 Multimanager OMC NSS Session from OMC R Terminal OMC R connection to TSC through BSC Abis signaling links static multiplexing Transcoder pools Automatic power down Auto Identification Automatic paging repetition. Access to PM raw counters via binary files.

Power Control due to Radio Link Failure Q3 Multimanager

This feature provides an automatic attempt to recover the Air Interface after an interruption of the SACCH. For more information, see Section 4.3.4. The Q3 Multimanager feature permits the OMC R to communicate over the Q3 Interface with multiple Network Management Centers (NMCs). Refer to Section 1.6.2 for more information. In this feature, a remote terminal interface allows access to OMC NSS functions from the OMC R terminal. This means that from the same terminal, an operator can open two simultaneous windows, one connected to the OMC R and the other to the OMC NSS. Each window provides commands and messages specific to the OMC R with which it is associated. This feature allows the OMC R operator to remotely configure certain TSC supervision devices using the existing OMC R - BSC X.25 link. This permits a new transmission scheme corresponding to a new Abis configuration to be set up before on site modifications are made, with corresponding time gain. Testing can be carried out immediately after the on site operation. This feature increases the maximum number of TRXs connected to the same link from 9 to 12. This feature is used with the G2 BTS and Evolium BSSs.

OMC NSS Session from OMC R Terminal

OMC R Connection to TSC through BSC

Abis Signaling Links Static Multiplexing

3BK 02974 AAAA TQZZA Ed. 07

25 / 240

1 Introduction

Transcoder Pools

The demands of GSM subscribers for new services is constantly evolving. At the same time, GSM operators need to protect their investment in capital equipment. The Transcoder Pools feature serves both needs. It permits the grouping of Transcoders having the same capacities into pools on the A Interface, as defined in the GSM phase 2 recommendations. This permits efficient use of existing infrastructure, without having to replace or redeploy older TCs when a new feature is added. This feature is for battery equipped, BTS A9100s, most usually installed outdoors. It allows the BTS A9100 to continue operating in degraded mode in the event of a main power supply failure, and effects an orderly shutdown of TRE units, keeping the cell alive for up to one hour. Auto Identification gives the BTS A9100 the capacity to recognize its own hardware configuration, and to provide this information to the BTS Terminal. If an idle MS performs a cell re selection at the same time that it is paged, or if a paging message is lost on the Air Interface, the MS may not receive a paging message. Automatic Paging Repetition ensures that paging messages are not lost by automatically repeating an unanswered page on the PCH. For more information about paging, refer to Chapter 2. This feature provides a facility to export Performance Management (PM) raw counters to an external PM processing system.

Automatic Power Down

Auto Identification Automatic Paging Repetition

Access to PM Raw Counters via Binary Files

26 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1.4

BSS Components
There are three main units in the BSS:
"

The BTS, which provides the radio transmission and reception functions for a cell. The BSC, which acts as the controller of the BSS. The BSC provides control of the BTSs and their resources, and performs switching functions within the BSS. The Transmission Subsystem (TSS), which links the BTS and the BSC. The TSS also provides the physical layer, and support of the data link layer, for the internal interfaces.

"

"

The BSS shown in Figure 2 is supervised by the OMC R. In a large network, one or more high level supervisors, a Network Management Center, can exist to centralize network management activities. The NMC has the authority to send directives to the OMC R. For more information about the NMC, refer to NMC and OMC R Interworking, and to documentation supplied with the NMC.
Mobile Stations Base Station Subsystem Network Subsystem

BTS

TSS

BSC

TSS

MSC

To/from PSTN

OMC R

NMC

Figure 2

Base Station Subsystem Components

3BK 02974 AAAA TQZZA Ed. 07

27 / 240

1 Introduction

1.4.1

Base Station Controller


The BSC provides control of the BTSs and manages radio resources and radio parameters. From a transmission point of view, the BSC also performs a concentration function if more radio Traffic Channel (TCH) than terrestrial channels are connected to the MSC. A single BSC can control a large number of BTSs. The exact number is a function of the BSC equipment and the configurations used. The BSC provides:
" " " " " " "

Resource management Database management Radio measurement processing Channel management Operations and maintenance functions within the BSS Communication with the OMC R Switching between the Air Interface channels (and their associated Abis channels), and the A Interface channels. Further information concerning these interfaces can be found in Sections 1.7.4, 1.7.5 and 1.7.6.

For a more detailed description of the BSC, refer to the G1 BSC Functional Description and G2 BSC Functional Description documents.

1.4.2

Base Transceiver Station


The BTS provides radio transmission, control and baseband functions for a cell. The BTS also supports the Air Interface with the MSs. The BTS performs the following functions under the control of the BSC:
" " " " "

Transmit and receive functions Antenna diversity Frequency hopping Radio channel measurements Radio frequency testing.

For a more detailed description of the BTS, refer to the BTS Functional Description or BTS A9100 Functional Description documents.

28 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1.4.3

Transmission Subsystem
The main function of the TSS is to provide efficient use of the terrestrial links between the equipment of the BSS. The components of the TSS are shown in Figure 3. Each TSS component provides a specific set of functions:
"

The Base Station Interface Equipment (BIE) performs signaling and submultiplexing on the Abis Interface The Submultiplexer (SM) performs submultiplexing on the Ater Interface The Transcoder (TC) provides O&M control of the Transmission System. It also provides:
D

"

"

Conversion between A law and Radio Test Equipment Long Term Prediction (RTE LTP) encoded traffic (speech) Conversion between A law and Algebraic Code Excited Linear Prediction (ACELP) encoded traffic (speech) Rate adaptation (data).

D D

The TC is normally located next to the MSC. If submultiplexing is required on the MSC to BSC link, an SM is located at each end of the link.
"

The Transcoder Submultiplexer Controller (TSC) collects and processes transmission data. It also provides an operator interface to control the equipment of the TSS.

3BK 02974 AAAA TQZZA Ed. 07

29 / 240

1 Introduction

TSC
OMC R

BTS

BIE

BIE

BSC

SM

SM

TC MSC

BTS

BIE

BIE

BSC

TC

BTS

TSC

BIE = Base Station Interface Equipment SM = Submultiplexer

TSC = Transcoder Submultiplexer Controller TC = Transcoder

Figure 3

Transmission Subsystem Components

30 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1.5

External Components
The BSS communicates with three external components, they are:
" " "

The NSS on the A Interface The MS on the Air Interface The OMC R on the BSS/OMC R Interface.

Figure 4 shows the logical position of the the External Components.


PLMN Mobile Stations Base Station Subsystem Network Subsystem Fixed Network

BTS

TSS

BSC

TSS

MSC HLR VLR AuC EIR

PSTN

OMC R

HLR = Home Location Register VLR = Visitor Location Register

AuC = Authentication Center EIR = Equipment Identity Register

Figure 4

Logical Position of External Components Associated with BSS

1.5.1

Network Subsystem
Managing communication within the PLMN and external networks is the primary role of the NSS. The NSS manages the subscriber administration databases, it contains the following components:
" " " " "

MSC Home Location Register (HLR) Visitor Location Register (VLR) Authentication Center (AuC) Equipment Identity Register (EIR).

3BK 02974 AAAA TQZZA Ed. 07

31 / 240

1 Introduction

MSC

Performs and coordinates the outgoing and incoming Call Set Up function. The MSC is a large capacity switch used for passing mobile traffic to mobile subscribers, or to subscribers of external networks. This part of the NSS Interfaces with the BSS. The HLR is the central database within a given network for mobile subscriber specific data. It contains static data such as access authorization, information about subscribers and supplementary services. It also controls the dynamic data about the cell in which the MS is located. The VLR temporarily stores information about MSs entering its coverage area. Linked to one or more MSCs, the VLR transmits data to a new VLR when an MS changes areas. The AuC manages the security data used for subscriber authentication. The EIR contains the lists of mobile station equipment identities.

Home Location Register

Visitor Location Register Authentication Center Equipment Identity Register

1.5.2

Mobile Stations
MSs provide radio and processing functions which allow subscribers to access the mobile network via the Air Interface. Subscriber related information is stored on a specific device called a Subscriber Identity Module (SIM). The SIM is a removable smart card that conforms to internationally recognized standards specified by the International Standards Organization (ISO). It contains the International Mobile Subscriber Identity (IMSI). This is used by the Network Operator to identify the subscriber in the network and to provide security and protection against misuse. Each MS has its own International Mobile Station Equipment Identity (IMEI). The IMEI is used by the Network Operator to prevent stolen, or non type approved MSs from accessing the network. There are three types of MS in GSM:
" " "

Phase 1 Phase 1 extended Phase 2.

MSs have different capabilities according to the the class of MS and the purpose for which the MS was designed. These differences include power output and ciphering.

32 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

Only phase 2 MSs can turn off ciphering, or change the ciphering mode, during a channel change procedure such as a handover. The ciphering capability of an MS is signalled to the BSS in the MS Classmark. Ciphering is used to protect information transmitted on the Air Interface. This is performed between the BTS and the MS (i.e. Air Interface). Transmission ciphering does not depend on the type of data to be transmitted (i.e. speech, user data, signaling), but to normal transmission bursts. See Section 2.8 for further information concerning MS ciphering capabilities.

MS Idle Mode

An MS is in idle mode when it is switched on, but not communicating with the network on a Stand alone Dedicated Control Channel (SDCCH) or a TCH. The BSS supports three idle mode functions:
" " "

Cell selection and cell reselection Location updating Overload control.

MS Cell Selection and Reselection

An MS monitors the broadcast messages from the BTS. This includes monitoring the Frequency Correction Channel (FCCH) and Synchronization Channel (SCH). The MS chooses the best cell on which to camp. If this cell is in a location area other than that stored in the MS memory, then the MS initiates a location update procedure. For an MS to camp on a cell, it has to synchronize with the cell. The BTS broadcasts an FCCH and a SCH at a defined time in the Broadcast Control Channel (BCCH) cycle. These channels are used as reference points for the MS to synchronize with the BCCH. Once synchronized, the MS continues to monitor these channels to stay synchronized. This type of synchronization, along with cell configuration and channel frequency information, enables the MS to calculate where channels occur in the multiframe sequences. Timing advance information is sent to the MS when an SDCCH is assigned. The MS uses the channel configuration information to calculate which part of the CCCH contains its paging message, and therefore which Time Slot to monitor for paging messages. When the MS is camped on a cell, it continues to monitor the BCCH transmissions from neighboring cells. The BCCH frequencies of the neighboring cells are transmitted on the BCCH of the home cell (sys_info 2). It can decide to camp on a new cell if it receives a better signal from an adjacent cell.

3BK 02974 AAAA TQZZA Ed. 07

33 / 240

1 Introduction

Reasons for moving to a new cell include:


" "

A problem in the existing cell The MS moving. If the MS moves to a new cell which is in the same location area as the one currently in its memory, it does not initiate a location update. It recalculates its paging group and monitors the new paging channel. Paging messages are broadcast from all cells in a particular location area.

Location Updating

The location update procedure is always initiated by the MS. Location update is performed after the call has finished (cell reselection). Reasons for location updates include:
" "

A periodic update A handover to a cell in a new location area.

The MS camps on a cell with a different location area code to the one in the MS memory. Periodic location update is performed by the MS after a lack of signaling activity for a specific time. If the timer expires, the MS initiates a location update, even if it has not changed Location Area (LA). The duration of the MS timer is defined by the network and sent to the MS as system information messages on the BCCH. The time can be between six minutes and 25 hours. When an MS is handed over to a cell in a new location area, there is no automatic location update in the network. A new Location Area Identity (LAI) in the BCCH (sys_info 3 and sys_info 4) is detected by the MS when the current call has finished, and initiates the location update procedure. This saves the system performing several location updates if the MS is handed over several times during a call. The MS initiates the location update procedure by sending a channel_request message indicating that the call is for a location update. The BSS assigns a dedicated signaling channel and establishes a signaling path between the MS and MSC. See Section 2.2 for more information. When a signaling path is established, the MS sends the LAI of the old cell on which it was camped to the MSC. The new VLR interrogates the old VLR for authentication and subscriber information. For further information see Sections 2.6.3 and 2.7. The LAI is made up of:
" " "

Mobile Country Code (MCC) Mobile Network Code (MNC) Location Area Code (LAC).

34 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

The BSS adds the cell identity of the MS current location to the message sent to the MSC. This information is sent in an Mobility Management (MM) sub layer message and is transparent to the BSS. The NSS stores this information in either its HLR or its VLR. Following a location update procedure, the VLR can assign a new Temporary Mobile Subscriber Identity (TMSI) to the MS. See Section 2.7 for more information about the TMSI. Figure 5 shows an MS as it moves to a new location area.

BTS

BSC

MSC

VLR

MS

MS moving and connecting in a new location area

Protocol Messages
BTS BSC

MSC

VLR

MS

Figure 5

Location Update To protect the system against overload, the system can bar access to MSs, by changing the Random Access Channel (RACH) control information in the system information messages described in Table 1. For further information, see Section 3.4.

Overload Control

3BK 02974 AAAA TQZZA Ed. 07

35 / 240

1 Introduction

1.5.3

Operations and Maintenance Center Radio


The OMC R supervises one or more BSSs. It performs the following functions:
" " " "

Manages the BSS software versions Acts as the central repository for configurations Manages fault and performance measurement reports Handles supervision of alarms and events.

The reported data is available to the operator from the OMC R's central database. The OMC R only performs O&M activities. It does not perform user traffic processing or call establishment and control activities. Refer to the Operations & Maintenance Principles for more information. Operator actions via the terminal interface trigger commands throughout the BSS. The OMC R provides object oriented management information, and supports a Manager/Agent scheme to perform and control management activities. The terminal interface supports different user profiles with different access rights. For further information about Manager/Agent communications, see the NMC and OMC R Interworking document.

36 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1.6

Network Management
Normally the OMC R provides all the network management and control functions required by the BSS. However, the management and control functions are proprietary to the system supplier. In keeping with ITU and ETSI recommendations, the Network Management function is supported. Network Management is compatible with all equipment, even that of different manufacturers. Network Management is controlled from one or several NMCs.

1.6.1

Telecommunications Management Network


The ability to transfer management information across the Telecommunications Management Network (TMN) environment is defined by a protocol suite, the Q Interfaces. Figure 6 shows the hierarchical structure of the TMN. It graphically defines the respective management responsibilities in the three main levels of the Management Information Tree (MIT).

NMC Operator (Resource Management)

NMC Q3

OSS

Network Management & Network Element Management

OMC R Operator (Resource and Equipment Management)

OMC R

Mediation Function

Security Block (SBL) Management


BTS

BSC

BSS

Network Element

BTS

BTS

OSS = Operation Support System

Figure 6

TMN System Hierarchy

3BK 02974 AAAA TQZZA Ed. 07

37 / 240

1 Introduction

1.6.2

Q3 Interface
Communication between the NMC and the OMC R takes place across the Q3 Interface (see Figure 6). The Q3 protocols can be divided into the following main areas:
" " "

Association connection and disconnection mechanisms Message format and structure Command types.

Q3 Multimanager

The Q3 Multimanager feature allows the OMC R to communicate over the Q3 Interface with multiple NMCs, permitting the network operator to concentrate specific functions on each of several NMCs. For example, in a large network, one NMC might be dedicated exclusively to Performance Management, and another to Fault Management, etc. For further information on Network Management and the Q3 Interface see the NMC and OMC R Interworking document.

38 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1.7

BSS Telecommunications Layers


The telecommunications functions of a GSM network are split into layers. These layers are split into two basic categories:
"

The Application layer is split into sub layers, to control:


D D D

Call Management (CM) Mobility Management (MM) Radio Resource Management (RRM).

"

The transmission layers which provide transmission between the various components.

Note

These transmission layers relate to the OSI layers, that is, the Physical Layer (i.e. Layer 1) and the Data Layer (i.e. Layer 2). The protocols used for these layers are standard. Figure 7 shows the general distribution of the telecommunication functions within a GSM network.
MS BTS BSC NSS CM MM RRM GSM Application Layers

TRANSMISSION

Figure 7

General Telecommunication Layers within GSM

1.7.1

Call Management
The Call Management sub layer performs Call Control (CACO) to establish, maintain and release calls. SMS within Call Management allows the MS to send and receive messages of up to 160 characters. The Supplementary Service (SS) functions are also provided to the MSs as part of Call Management.

3BK 02974 AAAA TQZZA Ed. 07

39 / 240

1 Introduction

1.7.2

Mobility Management
The MM sub layer is used by the NSS to manage the subscriber database, including information on subscriber location and authentication. It is also used by the MSs to send location updates when they move to new location areas.

1.7.3

Radio Resource Management


The RRM sub layer establishes, maintains and releases stable connections between the MS and MSC for the duration of a call. This includes functions such as managing the limited radio resources, to ensure high service availability. It also performs handovers when an MS moves during a call, or the channel quality falls below an acceptable level. RRM functions occur mainly between the MS and the BSC. Figure 8 shows the application layers, transmission layers and Interfaces of the BSS.

MS

BTS

BSC

MSC CM MM RRM GSM Application Layers

BSSAP

BSSAP

BSSAP

LAPDM

LAPDM

LAPD

LAPD

SCCP SS7

SCCP SS7

Layer 2

Layer 1

L1

L1

L1

L1 TC A Interface

Layer 1

08.60

Air Interface

Abis Interface

BSSAP = BSS Application Part LAPD = Link Access Procedure on the D Channel LAPDM = Link Access Protocol on the D Mobile Channel SCCP = signaling Connection Control Part SS7 = ITU signaling System No. 7

Figure 8

BSS Application, Transmission Layers and Interfaces

40 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1.7.4

The A Interface
The A Interface is used for communication between the BSC and the MSC. The connection between the BSC and MSC can be via one of the following:
" "

Terrestrial lines Satellite link. Physical layer 1 Data Link layer 2 RRM sub layer 3 of the application layer

The A Interface comprises the:


" " "

Physical Layer 1

The physical layer provides a physical connection to transport the signals. It supports a 2 Mbit/s link divided into 32 x 64 kbit/s channels by Time Division Multiplex (TDM). The actual physical link used depends on Network Operator implementation. Layer 2 provides the frame handling functions for the interface. It is also used to pass signaling messages using the ITU signaling System No. 7 (SS7) protocol. This comprises:
"

Data Link Layer 2

Message Transfer Part (MTP), which provides the mechanism for reliable transfer of the signaling messages. signaling Connection Control Part (SCCP), which provides the mechanism to identify transactions relating to a specific communication.

"

Application Sub layer RRM

To transfer layer 3 messages relating to a transaction, the SCCP uses the BSS Application Part (BSSAP). This is divided into two parts:
"

Direct Transfer Application Part (DTAP), which transfers messages directly between the MSC and the MS. These messages are not interpreted by the BSS. The BSS must read and recognize the initial message as a DTAP message. BSS Management Application Part (BSSMAP) to support procedures between the MSC and the BSC, such as resource management and handover control. On the A Interface, the process is terminated at the BSC. Messages for the BSS, passed by the BSSMAP are interpreted , by the BSC layer 3.

"

3BK 02974 AAAA TQZZA Ed. 07

41 / 240

1 Introduction

Ater Interface

The part of the A Interface between the TC and BSC is known as the Ater Interface. If SMs are placed between the TC and BSC there is also an Ater mux Interface. The Ater mux Interface is the result of multiplexing three Ater Interfaces. Transcoding is a layer 1 process, therefore the difference between the two interfaces is at the physical level.

1.7.5

The Abis Interface


The Abis Interface is used for communication between the BSC and the BTS. The Abis Interface comprises:
" " "

Physical layer 1 Data Link layer 2 BTS management sub layer 3 of the application layer

Physical Layer 1

The physical layer provides a physical connection to transport the signals. It supports a 2 Mbit/s link divided into 32 x 64 kbit/s channels by TDM. The physical link used depends on the Network Operator implementing the interface.

Data Link Layer 2

The data link layer provides frame handling and signaling functions using the Link Access Procedure on the D Channel (LAPD). This layer supports three types of signaling links:
"

The Radio signaling Link (RSL) for signaling to the MS (including SMS) The Operations and Maintenance Link (OML) for O&M information The Layer 2 Management Link (L2ML) for the layer 2 management functions such as frame checking and error correction.

"

"

Application Sub layer BTS

The BTS management layer is used for layer 3 messages between the BSC and the BTS. Some of these messages are transparent to the BTS. These are passed directly to the MS using the BTS RR management sub layer 3 on the Air Interface. Non transparent messages include messages for radio link layer control and channel management.

42 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

1.7.6

The Air Interface


The Air Interface is the radio interface between the BTS and the MS. The Air Interface comprises:
" " "

Physical layer 1 Data Link layer 2 RRM sub layer 3 of the application layer

'

Physical Layer 1 Data Link Layer 2 Application Sub layer RRM

The physical layer is a radio link where channels are divided by time and frequency. The data link layer provides frame handling and signaling functions, using a modified version of the Link Access Protocol on the Dm Channel (LAPDm). On the Air Interface, most of the layer 3 messages are transparent to the BTS. The BTS uses layer 3 to extract certain information from some messages before passing on the equivalent message. For example, when the BTS receives an encryption_command message from the BSC, it reads the Ki value and the algorithm to be used, before passing on the cipher_mode_command message. This procedure is explained in detail in Section 2.8.

Air Interface Channels

The Air Interface is divided by frequency and time, using Frequency Division Multiplex Access (FDMA) and Time Division Multiple Access (TDMA). This provides frames of eight Time Slots for each frequency supported by the cell. The channels of the cell are then assigned to specific Time Slots within the TDMA frames. However, not all channels require the full capacity of a Time Slot at each occurrence of a frame. Channels are configured to share Time Slots by only using certain occurrences of the frame. The cycle of frame occurrences is known as a multiframe. A multiframe can be 26 or 51 occurrences of a frame, depending on the channels configured within it. Within a multiframe, the same physical channel can support more than one logical channel.

3BK 02974 AAAA TQZZA Ed. 07

43 / 240

1 Introduction

Figure 9 shows Time Slot four of a TDMA frame supporting Access Grant Channels (AGCHs).
A G C H A G C H A G C H A G C H A G C H

Frame 1

Frame 2

Frame 3

Frame 4

Frame 5

Figure 9

Time Slot 4 of a TDMA Frame Supporting AGCHs Channels can be divided into traffic channels and control channels.

Traffic Channels

A TCH can be used for speech or data. The Alcatel BSS supports the following types of traffic channels:
"

Speech:
D D D

A Full Rate Speech TCH (TCH/FS) An Enhanced Full Rate Speech TCH A Half Rate Speech TCH (TCH/HS). A Full Rate Data TCH (9.6 Kbit/s) (TCH/F9.6) A Full Rate Data TCH (4.8 Kbit/s) (TCH/F4.8) A Half Rate Data TCH (4.8 Kbit/s) (TCH/H4.8) A Full Rate Data TCH (<2.4 Kbit/s) (TCH/F2.4) A Half Rate Data TCH (<2.4 Kbit/s) (TCH/H2.4).

"

Data:
D D D D D

Control Channels

Control Channels (CCHs) control communications between the BSS and the MSs. There are three types of CCH:
"

The BCCH broadcasts cell information to any MS in range. Three channels use the BCCH Time Slot:
D D D

FCCH SCH BCCH.

"

The CCCH communicates with MSs in the cell before a dedicated signaling channel is established. Three channels use the CCCH Time Slot:
D D D

RACH PCH AGCH.

44 / 240

3BK 02974 AAAA TQZZA Ed. 07

1 Introduction

"

The Dedicated Control Channel (DCCH) and Associated Control Channel (ACCH) pass signaling information for a specific MS transaction. Two channels use the DCCH Time Slot:
D D

SDCCH Cell Broadcast Channel (CBCH). Fast Associated Control Channel (FACCH) which can also steal TCH Time Slots Slow Associated Control Channel (SACCH).

Two channels use the ACCH Time Slot:


D D

An ACCH channel is always associated with a TCH. For a complete description of the Air Interface channels, see Appendix A.

3BK 02974 AAAA TQZZA Ed. 07

45 / 240

1 Introduction

System Information Messages

System information messages transmit information about the cell to the MS. There are six system information messages. Four are sent on the BCCH as a general broadcast to any MSs in the cells, and two sent on the SACCH to MSs in communication with the BSS. Table 1 shows the system information messages, the channel on which they are transmitted and the type of information in each.

Table 1

System Information Messages


Message Sys_info 1 Sys_info 2 Sys_info 3 Channel BCCH BCCH BCCH Information Cell channel description RACH control information. Neighbor cell BCCH frequency list RACH control information. Cell Identity (CI) Location Area Identity Control channel description Cell options:

G G G G G
Sys_info 4 BCCH LAI

Power central information Discontinuous Transmission (mechanism) (DTX) information Radio link timeout. Max transmit power allowed in cell Min receive level to access cell.

Cell selection parameters:

RACH control information. Cell selection parameters:

G G

Maximum transmit power allowed in cell Minimum receive level to access cell.

RACH control information CBCH channel description. Sys_info 5 Sys_info 6 SACCH SACCH Neighbor cell BCCH frequency list. LAI Cell options:

G G G

Power control information DTX information Radio link timeout.

46 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

2 Call Set Up
This chapter provides an overview of how a call is set up between the NSS and the MS. It describes the various kinds of calls that can be set up. The type of teleservice and bearer service required are also described. This chapter also describes the following parts of the Call Set Up procedure: G G G G G G G Mobile Originated Call Mobile Terminated Call Paging Congestion Classmark Handing Authentication Ciphering.

3BK 02974 AAAA TQZZA Ed. 07

47 / 240

2 Call Set Up

2.1

Overview
Call set up is required to establish communication between an MS and the NSS. The NSS is responsible for establishing the connection with the correspondent. Different types of calls require different teleservices. These teleservices are defined in the GSM specifications. The type of teleservice and bearer service to be used is negotiated before the normal assignment procedure; see Section 2.2.3 for more information.

Call Types
Table 2
Type of Call Mobility Management Calls

Table 2 shows the three basic types of call:

Types of Calls
Description These calls, e.g. location update, are used by the system to gather MS information. The exchanges are protocol messages only; there fore, only a signalling channel is used. Figure 5 illustrates the loca tion update procedure. These calls, e.g. SMS and SS calls, pass small amounts of informa tion. Therefore, only a signalling channel is used. These calls, e.g. speech or data calls to a correspondent, can pass large amounts of information. Therefore they require greater band width than a signalling channel. These calls use traffic channels.

Service Calls User Traffic Calls

The channels used for calls are the SDCCH for signalling and the TCH for user traffic (see Section 1.7.6 for more information). These channels are associated with FACCH/SACCH. An SDCCH is always assigned for call set up, even if a TCH is later required for the call. The role of the BSS in call set up is to assign the correct channel for the call, and to provide and manage a communications path between the MS and the MSC.

48 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

Call Set Up Phases

Table 4 shows the phases involved in call set up: Table 3


Phase Radio and Link Establishment

Call Set Up Phases


Composition Paging (for mobile terminated calls only) If ATTACH_DETACH_ALLOWED is activated, the MS IMSI_detach message can eliminate the need for paging. See Section 2.3.4. Immediate assignment procedure to assign an SDCCH A interface connection, to assign a SCCP signalling channel between the BSC and MSC Assignment of a switching path through the BSC.

Authentication and Ciphering

Classmark handling Authentication Ciphering. Teleservice/bearer service negotiation Channel allocation Physical context procedure Assigning a TCH, if required Connecting the call.

Normal assignment

The phases are described in Sections 2.2 and 2.3.

3BK 02974 AAAA TQZZA Ed. 07

49 / 240

2 Call Set Up

2.2

Mobile Originated Call


A call initiated by an MS can either be a subscriber call, where speech and/or data is passed across the network, or a location update call from an MS in idle mode. Location update information is passed on the signalling connection. Therefore, the initial call set up procedure is similar to a subscriber call. The location update does not require allocation of a TCH.

2.2.1

Radio and Link Establishment


The radio and link establishment procedure establishes signalling links between:
" "

The BSS and the MS via the SDCCH channel The BSS and the MSC via the SCCP link.

These links pass the information for call negotiation, and set up a TCH, if required. Figure 10 shows radio and link establishment for a mobile originated call.

Channel Request

The MS initiates a call by sending a channel_request message, with a Random Access Information Value (REF). The REF includes an establishment cause and a Random Number (used for authentication) (RAND). It is transmitted on the RACH channel. The RACH channel is associated with the CCCH channel which the MS is monitoring while in idle mode. The establishment cause field of the REF specifies:
" " " " " " "

An emergency call Call re establishment Response to paging MS originating speech call MS originating data call Location update Service call (SMS etc.).

The MS notes the random number and frame number associated with each channel_request message. These are used by the MS to recognize the response sent from the BSS. This response is sent on the AGCH, which can be monitored by many MSs. The MS decodes all messages sent on this AGCH, and only accepts a message with a random number and frame number matching one of the last three requests sent.

50 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

MS

BTS

BSC

MSC

REF stored in MS memory

SDCCH Allocation

MS compares message with REF in memory Switch to SDCCH

Service Request must match original sent by MS in the SABM

REF RFN TA cm ID power SDCCH Service Request UA

= = = = = = = = =

Random access information value Reduced frame number Timing Advance Classmark Mobile Identity MS power, BTS power Description of the allocated SDCCH channel Initial layer 3 message including the MS identity and classmark Un numbered Acknowledgement

Figure 10

Radio and Link Establishment for Mobile Originated Call The MS continues to transmit channel_request messages until it receives a response. If no response is received before the MS has transmitted a predefined number of retries, the MS:
"

Displays a network error message for all calls except location updates Performs automatic reselection for location update calls. This means that the MS attempts random access on a different cell.

"

3BK 02974 AAAA TQZZA Ed. 07

51 / 240

2 Call Set Up

On receipt of the channel_request message from the MS, the BTS sends a channel_required message to the BSC. This message contains the random number sent by the MS, and the timing advance measured by the BTS.

SDCCH Channel Activation

The BSC checks the channel_required message to ensure it can accept the request. It allocates an SDCCH channel if one is available. The resource management software of the BSC allocates the SDCCH on the basis of which TCH has the most available SDCCHs. This ensures the load is spread between the TCHs. The BSC then sends a channel_activation message to the BTS. It also sets a timer to wait for an acknowledgment from the BTS, indicating that it is ready to activate the channel. The channel_activation message contains:
" " "

A description of the SDCCH to be used The timing advance MS and BTS power commands. The MS and BTS power are set to the maximum allowed in the cell.

The BTS initiates the physical layer resources for the channel and sets the LAPDm contention resolution ready for the first MS message on the SDCCH. It then sends a channel_activation_acknowledgement message to the BSC. The BSC stops its guard timer. Note Contention resolution prevents two MSs connecting to the same SDCCH. Figure 11 shows the Channel Activation procedure.
MS BTS BSC SDCCH Allocation MSC

TA power SDCCH

= = =

Timing Advance MS power, BTS power Description of the allocated SDCCH channel

Figure 11

SDCCH Channel Activation

52 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

Immediate Assignment

The BSC builds and sends an immediate_assign_command message reiterating the information given in the channel_activation message. This message also includes the random number and frame number of the original MS request to which the BSC is replying. It also instructs the BTS to inform the MS of the SDCCH channel assignment. The BSC starts a guard timer for the MS to respond. Figure 12 shows the Immediate Assignment procedure.

MS

BTS

BSC

MSC

Switch to SDCCH REF RFN TA SDCCH = = = = Random access information value Reduced frame number Timing Advance Description of the allocated SDCCH channel

Figure 12

Immediate Assignment The BTS sends the immediate_assignment message to the MS on the AGCH. The MS checks the random number and frame number in the immediate_assignment message. If it matches those from one of its last three channel_request messages, the MS switches to the indicated SDCCH and sets its timing advance to the value indicated in the immediate_assignment message.

Set Asynchronous Balanced Mode

The first layer 2 frame sent on the SDCCH is a standard LAPDm type frame, known as the Set Asynchronous Balanced Mode (SABM). This is equivalent to the Set Asynchronous Balanced Mode Extended (SABME) frame in the Link Access Procedure on the D Channel (LAPD). On the Air interface, it establishes the LAPDm connection with the BTS. This frame can also contain layer 3 messages. The MS starts its LAPDm connection and sends a layer 3 message in its first frame. The BTS uses this message for contention resolution. The BTS sends an acknowledgement to the MS containing the same layer 3 message. Therefore, only the MS that sent the message can accept the acknowledgement from the BTS and consider itself connected.

Contention Resolution

3BK 02974 AAAA TQZZA Ed. 07

53 / 240

2 Call Set Up

Figure 13 shows the establishment of the connection for a mobile originated call.
MS BTS BSC MSC

cm Service Request UA

= = =

Classmark Initial layer 3 message including the MS identify and classmark Un numbered Acknowledgement

Figure 13

Connection for Mobile Originated Call For an MS originated call, the layer 3 message from the MS contains:
"

An Information Element (IE) indicating:


D D D D

CM service request (speech/data, SMS, emergency call) Location updating request (location updating procedure) CM re establishment request ( after a failure) IMSI detach indication (MS power off - see section 2.3.4 for more information).

" "

The MS identity (see Section 2.7 for more information) The MS classmark (see Section 2.6 for more information).

The network uses this message to decide which call negotiation procedures are required and whether to assign a TCH.

Establish Indication

The BTS sends an establish_indication message to the BSC to indicate that the MS has connected. The BSC stops the guard timer, extracts the classmark information and initiates an SCCP connection with the MSC. The BSC sends an SCCP_connection_request message to the MSC. The MSC replies with an SCCP_connection_confirm message. This message can contain a classmark request or a cipher mode command. The signalling link is established between the MS and the MSC.

SCCP Connection

54 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

2.2.2

Authentication and Ciphering


The content of the classmark IE sent during radio and link establishment depends on the type of MS. The classmark information is used for MS power control and to set ciphering. The MSC can request a classmark update to ensure that it has the correct information. Classmark procedures are described in Section 2.6. The authentication procedure:
" "

Classmark Procedure

Authentication

Authenticates the MS identity Checks the MS has the correct Individual Subscriber Authentication Key (Ki) value on the SIM for the ciphering procedure Sends the Random Number for the ciphering and authentication procedures.

"

This procedure is described in Section 2.7.

Ciphering

Information passed on the Air interface must be protected. The MSC can request that the BSS set the ciphering mode before information is passed on the SDCCH. Ciphering is described in Section 2.8.

2.2.3

Normal Assignment
If the call requires a TCH to communicate with a called party, the MS sends a setup message. This indicates the teleservice and bearer service required, and the called party number. The information is sent transparently through the BSS. This message can contain more than one bearer service element, and a parameter indicating that the subscriber may request a change of service (In Call Modification) during the call. See Section 3.2 for information concerning In Call Modification. The MSC sends a call_proceeding message to the MS. This indicates that the call parameters have been received, and that attempts to establish communication with the called party are under way. Figure 14 shows the normal assignment process for a mobile originated call.

3BK 02974 AAAA TQZZA Ed. 07

55 / 240

2 Call Set Up

MS

BTS

BSC

MSC

TCH allocation

release SDCCH

Set transcoder Set switching path

initiate SDCCH release

cm = TA = cipher = DTX =

Classmark Timing Advance Encryption algorithm + ciphering key Discontinuous transmission flags

Figure 14

Normal Assignment for Mobile Originated Call

56 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

Channel Request

The MSC initiates the assignment of the TCH by sending the assignment_request message and sets a timer to supervise the response from the BSC. The BSC checks the message which must contain a channel type (for TCH this is speech or data plus data rate). This message also contains the MS classmark which the BSC uses if it has not received the classmark from the MS. If the BSC finds an error in the assignment_request message, it sends an assignment_failure message. If no error is detected, it starts the normal assignment procedure towards the MS.

Traffic Channel Allocation

The BSC ensures that it is not running any other procedures for the MS and then allocates resources for the TCH. The resources allocated are calculated using an algorithm in the BSC. The BSC can receive an assignment_request message in various situations. Therefore, it has TCH resource allocation algorithms for:
" " " " " " "

Normal assignment In call modification Intercell handover Intracell handover Directed retry Concentric cells Microcells.

In normal conditions (MS originated call, normal assignment), the normal assignment algorithm is used. The BSC keeps a table of idle channels in which the channels are classified by their interference level (1 = low, 5 = high). The interference level of all free channels is monitored by the BTS. This information is periodically sent to the BSC in the RF_resource_indication message. The BSC does not automatically allocate a channel from the lowest interference level, as a number of channels can be reserved for handover. After all reserved channels are accounted for, the channel allocated is from the lowest interference level. If the number of reserved channels exceeds the number of free channels, then the BSC allocates a channel from the highest interference level. If no channels are available, the BSC sends an assignment_failure message to the MSC indicating the cause of the failure.

3BK 02974 AAAA TQZZA Ed. 07

57 / 240

2 Call Set Up

TCH Channel Activation

The BSC sends a physical_context_request message to the BTS, to find out the current power and timing advance being used by the MS on the SDCCH. The BTS responds with a physical_context_confirm message, containing the relevant information. Figure 15 shows the TCH channel activation process.

MS

BTS

BSC
TCH allocation

MSC

TA cipher DTX

= Timing Advance = Encryption algorithm + ciphering key = Discontinuous transmission

Figure 15

TCH Channel Activation The BSC sends a channel_activation message to the BTS. This contains:
" " "

A description of the TCH to be used The MS timing advance to be applied The encryption algorithm and ciphering key (same as for SDCCH assignment) A Discontinuous Transmission (DTX) indicator for uplink (not used) and downlink (see Section 5.2.4 for more information) The MS power to be used (see Section 5.2.2 for more information) The BTS power to be used.

"

"

"

The BSC starts a timer, and waits for the BTS to acknowledge that it has activated the channel.

58 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

The BTS initializes its resources for the TCH, sets the ciphering mode, sends timing advance and power information to the MS on the SACCH associated to the TCH, which is constantly monitored by the MS. At the same time, the BTS sends a channel_activation_acknowledgement message to the BSC. The BSC stops its timer and sends an assignment_command message on the SDCCH to the MS. This instructs the MS to change to the TCH. When the MS receives the assignment_command message, it disconnects the physical layer, and performs a local release to free the LAPDm connection of the SDCCH. Figure 16 shows the TCH channel assignment process.
MS
release SDCCH

BTS

BSC

MSC

Set transcoder Set switching path

Figure 16

TCH Channel Assignment The MS then establishes the LAPDm connection (via the SABM on the FACCH) for the TCH. The BTS sends an establish_indication message to the BSC. It also sets the transcoder and its radio link failure detection algorithm. The BTS sends a layer 2 acknowledgement to the MS. The MS sends an assignment_complete message to the BSC. When the BSC receives the establish_indication message, it establishes a switching path between the allocated Abis and A interface resources. When it receives the assignment_complete message, it sends an assignment_complete message to the MSC and initiates release of the SDCCH (see Chapter 4 for more information).

3BK 02974 AAAA TQZZA Ed. 07

59 / 240

2 Call Set Up

Connecting the Call

Once communication with the called party is established (but before the call is answered), the MSC sends an alerting message to the MS. The MS generates a ring tone. When the called party answers, the MSC sends a connect message to the MS. The MS responds with a connect_acknowledgement message. The call is established. Figure 17 shows the call connection process for a mobile originated call.

MS

BTS

BSC
initiate SDCCH release

MSC

Figure 17

Call Connection for Mobile Originated Call

60 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

2.3

Mobile Terminated Call


A call from the NSS to an MS can be either a call routed through the NSS from a calling party, or it can be initiated by the NSS for mobility management. A mobile terminated call set up follows the same basic procedures as a mobile originated call. This section describes only those procedures which are different. Figure 18 shows radio and link establishment for a mobile terminated call.

2.3.1

Radio and Link Establishment


Paging
Before the BSS sets up a signalling link, the MS has to be paged. This procedure is initiated by the MSC. It sends a paging message to the BSC controlling the location area from which the MS last performed a location update. This message is sent in connectionless mode and contains:
" "

The MS identity (TMSI or IMSI of the MS to be paged). A cell identifier list which identifies the cells where the paging request is to be sent. This could be all cells or a group of cells.

The MSC sets a timer to wait for a paging_response message from the MS. The BSC checks the paging message and, if valid, calculates the MS paging group and the CCCH timeslot for the paging group. The BSC sends a paging_command message to each BTS, indicating the TMSI or IMSI, the paging group and the channel number. Each BTS formats the information and broadcasts a paging_request message on the Paging Channel (PCH). The MS listens to messages sent to its paging group. When it receives a paging message with its MS identity, it sends a channel_request message on the RACH to the BTS, indicating that the request is in response to a paging_request message. The BSS then performs the radio and link establishment procedure described in Section 2.2. Note When the MS sends the SABM, it indicates that the connection is in response to a paging request. For more information about paging, see Section 2.4.

3BK 02974 AAAA TQZZA Ed. 07

61 / 240

2 Call Set Up

MS

BTS

BSC

MSC

RADIO AND LINK ESTABLISHMENT PROCEDURE Refer to Figure 10

Figure 18

Radio and Link Establishment for Mobile Terminated Call

2.3.2

Authentication and Ciphering


The system handles authentication and ciphering for a mobile terminated call in the same manner as a mobile originated call, see Section 2.2.2. Refer to Section 2.6 for more information about the classmark, Section 2.7 for more information about authentication, and Section 2.8 for more information about ciphering procedures.

2.3.3

Normal Assignment
The normal assignment procedure for an MS terminated call is initiated by the MSC. This is shown in Figure 19. The MSC sends a layer 3 Call Control (CC) set_up message to the MS, indicating the bearer service and teleservice to be used for the call. The MSC can indicate more than one bearer service. The MS checks this message. If it can accept the call, it sends a call_confirmation message which can contain a bearer capability parameter indicating which bearer service is preferred.

62 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

The BSS performs the physical context and channel assignment. This is described in Section 2.2.3. Once the TCH is assigned, the MS alerts the user and sends an alerting message to the MSC. When the MS user answers, the MS sends a connection message to the MSC. The MSC sends a connection_acknowledgement message to the MS and connects the call. All these messages are layer 3 CC messages, and are transparent to the BSS.
MS BTS BSC MSC

NORMAL ASSIGNMENT PROCEDURE FOR TCH Refer to Figure 14


ring tone

user answer

Figure 19

Normal Assignment for Mobile Terminated Call

3BK 02974 AAAA TQZZA Ed. 07

63 / 240

2 Call Set Up

2.3.4

IMSI Attach-Detach
IMSI Attach Detach is a mobility feature which primarily concerns the MSC and the MS. Used together with the periodic location update procedure, IMSI Attach Detach allows the network to provide more efficient control and use of resources. For example, if a mobile terminated call arrives for an MS which is detached," the MSC knows that the MS is not active and does not need to start a paging request. For the BSS, this can reduce load on the PCH. Initiation of the IMSI Attach Detach procedure is controlled by a parameter in the BSS, ATTACH_DETACH_ALLOWED. When this parameter is set, the BSS broadcasts system information on all cells indicating that the network supports IMSI Attach Detach. MSs which have successfully connected and logged themselves onto the network are then obliged to perform IMSI Attach Detach procedures. Refer to documentation supplied with MSs which support this function For more information about the ATTACH_DETACH_ALLOWED parameter, see OMC R Configuration Management Services. IMSI Attach Detach is also used for other functions at the MSC. Refer to documentation for your network's MSC equipment.

64 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

2.4

Paging
Paging is the procedure by which the network contacts an MS. For example, if the network needs to inform the MS of an incoming call, it pages the MS to prompt it to request a channel. After the immediate assign procedure, the service_request message from the MS indicates that the connection is in response to a paging message. Paging messages are sent on the CCCH. The downlink CCCH carries the AGCH and the PCH. The PCH is divided into sub channels, each corresponding to a paging group. To save the MS from monitoring every occurrence of the PCH, each MS is assigned a paging group calculated from the IMSI. Each MS calculates its paging group and monitors only that PCH sub channel. This saves MS battery power. The number of paging groups and the CCCH organization varies for each configuration. The MS knows the CCCH organization from the information passed on the BCCH (sys_info 3). The AGCH sends the immediate_assignment message to the MS. A number of blocks can be reserved for the AGCH using the BS_AG_BLKS_RES parameter. If this parameter is set to 0, then the immediate_assignment message is sent on the PCH. Figure 20 shows a TDMA frame with nine CCCH blocks, three of which are reserved for the AGCH and the rest are for the PCH. The parameter to reserve these blocks is set to BS_AG_BLKS_RES = 3. TDMA Frame Cycle

CCCH0 CCCH1 CCCH2 CCCH3 CCCH4 CCCH5 CCCH6 CCCH7 CCCH8 Reserved for AGCH Figure 20 Available for PCH channels CCCH with Three Blocks Reserved for AGCH In the example in Figure 20, BS_AG_BLKS_RES is set to three. Every occurrence of the TDMA frame cycle carrying the CCCH has three AGCHs and six PCHs. However, more than six paging groups can be defined by assigning a different group of six PCHs to a number of TDMA multiframe cycles. This is specified using the parameter BS_PA_MFRMS, as shown in Figure 21.

3BK 02974 AAAA TQZZA Ed. 07

65 / 240

2 Call Set Up

First TDMA Frame cycle AGCH AGCH AGCH PGR0 PGR1 PGR2 PGR3 PGR4 PGR5

Second TDMA Frame cycle AGCH AGCH AGCH PGR6 PGR7 PGR8 PGR9 PGR10 PGR11

Third TDMA Frame cycle AGCH AGCH AGCH PGR12 PGR13 PGR14 PGR15 PGR16 PGR17

Fourth/1 TDMA Frame cycle AGCH AGCH AGCH PGR18 PGR19 PGR20 PGR21 PGR22 PGR23

These four TDMA frames represent 24 PCHs. The parameter to reserve these is BS_PA_MFRMS = 4

Figure 21

Four TDMA Frame Cycles Providing 24 Paging Sub channels The MSC has to initiate the paging procedure, as it holds the information on the last MS location update. The MSC sends the paging message to the BSC(s) and sets a timer for the paging_response from the MS, which is sent as part of the service_request message after the immediate assign procedure. The paging message from the MSC contains a cell list identifier IE, identifying the cells in which the paging message is to be transmitted. The BSC checks the cell identifier list and builds a paging_command message for the relevant BTSs. Table 4 shows the different cell identification lists and the paging performed by the BSC.

Paging Control

66 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

Table 4
No IE present

Cell List Identifier and Paging Performed


Paging Performance Paging performed in all cells con trolled by BSC Paging performed in all cells con trolled by BSC Paging performed in all cells con trolled by BSC Paging performed in only those cells specified Paging performed in all cells of each location area specified

Cell List Identifier

IE indicates all cells Error in IE IE indicated specific cell(s) IE indicates specific location area(s)

The BSC calculates the paging group of the MS for each cell and the CCCH timeslot. It then sends a paging_command message to each BTS, indicating the CCCH timeslot number, MS paging group and the MS identity (IMSI/TMSI). The BTS builds a paging_request_type_x message to send to the MS. There are three types of paging request messages, as the BTS can page more than one MS at a time. Table 5 shows the relationship between the paging message type, the number of MSs to be paged and the MS Identification (ID) used. Table 5 Paging Request Message and MS Identification
MS Identification IMSI or TMSI (for 1 MS) IMSI, IMSI or TMSI, TMSI or IMSI, TMSI (for two MSs) TMSI, TMSI, TMSI or TMSI, TMSI, IMSI TMSI, TMSI, TMSI, TMSI

Paging Request Message Type_1, identifying up to two MSs Type_2, identifying three MSs Type_3, identifying four MSs

By using a combination of paging message types, several MSs can be simultaneously paged. This is done even if some MSs are paged using the IMSI and others are paged using the TMSI. The paging_request messages are stored in a buffer, while waiting to be sent on the relevant PCH subchannel. If this buffer becomes full, the next paging_command message is discarded.

3BK 02974 AAAA TQZZA Ed. 07

67 / 240

2 Call Set Up

When the MS receives the paging_request message, it sends a channel_request message to initiate the immediate assign procedure. The service request message following the immediate assign procedure indicated that the channel_request is in response to a paging request message. This is shown in Figure 22.
MS BTS BSC MSC

IMMEDIATE ASSIGNMENT PROCEDURE Refer to Figure 14

REF RFN TA

= = =

Random access information value Reduced frame number Timing Advance

Figure 22

Paging Message Sequence

68 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

2.5

Congestion
To prevent an assignment_request or an external handover_request message being rejected, the BSS allows queueing of TCH requests. Congestion occurs when all TCHs are busy for a particular cell and the message arrives at the BSC. Queueing is allowed if indicated by the MSC in the request message.

2.5.1

Queueing
Queueing is used to achieve a higher rate of successful call set up and external handover completion in cases of TCH congestion. This is achieved by queueing the request for a defined period of time. During this time a TCH can become available and the TCH assignment can then be completed. When all TCHs of a cell are busy, assignment and external handover requests for TCH allocation can be queued, if:
"

Requested by the MSC If the MSC allows queueing, this information and the priority of the request for queueing are sent in the Priority Information Element of the request.

"

Configured in the BSC The BTS can perform queueing if specified in the BSC configuration. BTS queueing can be enabled/disabled by an operator command through the OMC R. Setting the BTS_Q_LENGTH parameter to 0 disables the queueing.

If either the MSC or BSC does not allow the request to be queued, the request is immediately rejected and an assignment_failure message is sent to the MSC.

2.5.2

In queue
If queueing is allowed, the request cannot be queued if one of the two queue limits is exceeded. These limits are:
"

The maximum number of requests that can be queued per BTS if defined by the O&M parameter BTS_Q_LENGTH. The range is from 1 to 64. This can be individually set for each BTS. The global limit of 64 queued requests in the BSS. The sum of all BTS queue lengths cannot exceed 64.

"

3BK 02974 AAAA TQZZA Ed. 07

69 / 240

2 Call Set Up

When one of the queue limits is exceeded, the request may still be queued if there is a lower priority request in the queue. If the priority of the in coming request is higher than the lowest in the queue, the in coming request is queued and the oldest lowest priority request is then rejected. Once a request is queued, the BSC informs the MSC by sending a queueing_indication message. A timer is activated when the request is queued. If the timer expires or the request is pre empted by a higher priority request, the request is rejected. Once in the queue, the request waits to be either accepted or rejected due to one of the following events:
" "

TCH availability Forced Directed Retry.

TCH Availability

If another TCH disconnects within the cell, the request at the top of the queue is assigned to the newly available TCH. The request is removed from the queue. An assignment_complete message is sent to the MSC notifying it of the successful assignment of a TCH. Forced Directed Retry; the BSC detects that the call can be supported on another cell. If the BSC detects the possibility of a handover for the queued request, it generates an internal or external handover alarm and initiates the appropriate handover procedure. A handover from an SDCCH in the serving cell to a TCH in a target cell is known as directed retry. This is described in Section 3.3. On detection of the handover alarm, the BSC cancels the queued request, stops the timer and selects a neighbor cell in the target cell list. The target cell must be able to support the ciphering requirements of the call. Once a cell is selected, a TCH is chosen and a handover is attempted (SDCCH->TCH). If the handover fails, another cell is chosen from the target cell list. This procedure continues until a successful handover or the handover limit (number of handover attempts allowed) is exceeded. The MSC is notified of a successful handover by an assignment_complete message. The direct retry finishes if the number of handover attempts is exceeded, or there are no more cells left in the target cell list. Finally an assignment_failure message is sent to the MSC indicating that there are no radio resources available.

Forced Directed Retry

70 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

Queue Pre emption

A higher priority request arrives in the queue If one of the queue limits is exceeded and the request is the oldest of the lowest priority requests in the queue, the request is rejected. An assignment_reject message is sent to the MSC indicating that there are no radio resources available.

Timer Expires

If the timer expires, the request is de queued and rejected. An assignment_reject message is sent to the MSC indicating that there are no radio resources available.

3BK 02974 AAAA TQZZA Ed. 07

71 / 240

2 Call Set Up

2.6

Classmark Handling
The MS classmark contains information about the MS type and capabilities. This information is used by the BSS when implementing procedures which affect an MS, such as:
" " " " "

Handover Power Control Ciphering Overload Control Location Updating.

MSs of different types have different capabilities within the network. It is essential that the network knows the MS classmark when initiating procedures for a specific MS. There are three entities which provide classmark handling as shown in Table 6. Table 6
Entity BSS

Classmark Handling
Classmark handling Performed by the BSC which is responsible for collecting the classmark data needed to perform procedures on the MS. Indicates the MS classmark data to the BSC for MSC initiated procedures. The BSS is informed of any classmark changes and information is sent on request from the BSS.

MSC MS

Note

The BSS can receive MS classmark information from both the MSC and the MS. The information from the MS overrides information from the MSC.

2.6.1

Classmark IE
The Alcatel 900/1800 BSS supports classmark 1 and classmark 2 IEs. The classmark 1 IE is always sent to the BSS when the MS tries to establish communication.

Classmark 1

The classmark 1 IE contains:


" " "

The revision Level The RF Power Level Support of A5/1 Encryption.

72 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

Classmark 2

The classmark 2 IE is defined in GSM to allow the coding of phase 2 capabilities such as the A5/2 ciphering algorithm. The classmark contains the same elements as the classmark 1 IE, plus support of A5/2 encryption. The revision level indicates either a phase 1 or phase 2 MS. It does not distinguish between phase 1 and phase 1 extended MSs. If there is an error in this field, then a default phase 1 is assumed. The RF Power Level indicates the MS power capability. For Alcatel 900:
" " " " "

Revision Level RF Power Level

Class Class Class Class Class

1 2 3 4 5

= 20W = 8W = 5W = 2W = 0.8W.

For Alcatel 1800:


" "

Class 1 = 1W Class 2 = 0.25W.

The value is not permitted if there is an error in this field. The result of this is that the MS power capability is assumed to be the same as the maximum transmit power allowed in the cell.

Support of A5/1 Encryption Support of A5/2 Encryption Impact on BSS and MSC

This field indicates whether or not the MS supports the A5/1 encryption algorithm. If the A5/1 encryption algorithm is not supported, there is no indication of other algorithms being supported. This field indicates whether or not the MS supports the A5/2 encryption algorithm. If the A5/2 encryption algorithm is not supported, there is no indication of other algorithms being supported. The main difference between classmarks for the BSS or MSC is the support of the encryption algorithms. For procedures that require ciphering, the BSS and MSC can not know the MS ciphering capability if only the classmark 1 IE has been received. Therefore, there is a classmark updating procedure.

3BK 02974 AAAA TQZZA Ed. 07

73 / 240

2 Call Set Up

2.6.2

Classmark Updating
Further classmark information may be required by the BSS or MSC when initiating a procedure which needs to encrypt information. The MS can also send updated information if, for example, its power capability changes. This means that the updating of classmark information can be initiated from the:
"

MS by sending a classmark_change message to the BSC which sends a classmark_update message to the MSC. BSC by sending a classmark_enquiry message through the BTS to the MS. The MS responds with a classmark_change message. MSC by sending a classmark_request message to the BSC. This prompts the BSC to send a classmark_enquiry message to the MS which responds with a classmark_change message.

"

"

The classmark_change message from the MS is passed through the BTS to the BSC. The BSC stores the information for its own use and forwards the information to the MSC. Depending on the network type and configuration, the classmark update is not always required. Therefore, the Alcatel 900/1800 BSS has a parameter in the BSC (Parameter: BSS_SEND_CM_ENQUIRY) which can be configured. Table 7 shows the possible configurations. Table 7
0 1 2

Classmark Configuration
Action The classmark_enquiry message is never initiated by the BSC. The BSC always initiates a classmark update when it receives a location update request. The BSC only initiates a classmark update on recep tion of a location update request if A5/1 is not avail able. This is worked out from the classmark 1 IE.

Parameter Value

If the system requests a classmark update to a phase 1 MS, the MS is not able to respond. It considers the message an error and sends an RR_status message. This message is ignored by the BSS and is not passed to the MSC.

74 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

2.6.3

Location Updating with Classmark Procedure


If the MS is a phase 1 extended or phase 2 MS, it can send classmark update information on request from the BSS or MSC. Because the BSS does not know the MS ciphering capability from the classmark 1 IE, updating is required. This is received when the MS establishes the LAPDm connection, as shown in Figure 23.

MS

BTS

BSC

MSC

IMMEDIATE ASSIGN PROCEDURE Refer to Figure 12


switch to SDCCH

AUTHENTICATION AND CIPHERING PROCEDURES Refer to Sections 2.7 and 2.8

cm

Classmark

Figure 23

Location Update with Classmark Update

3BK 02974 AAAA TQZZA Ed. 07

75 / 240

2 Call Set Up

The MS initiates a location update procedure by sending a channel_request message on the RACH. The BSS performs the immediate assign procedure, as described in Section 2.2. The MS establishes the LAPDm link and sends the location update request and classmark 1 IE. The BTS sends an establish_indication message to the BSC, containing the location update request and classmark 1 IE. The BSC uses the classmark to send MS power control information to the BTS to start power control. It stores the classmark information and requests an SCCP connection with the MSC. When the BSC receives an SCCP_connection_confirm message, it sends a classmark_enquiry message to the MS. The MS responds with a classmark_change message containing the classmark 2 IE. This information is passed to the MSC in a classmark_updating message. If the MS is a phase 1 MS, it responds with an RR_status message which is ignored by the BSS. In this case, the BSS sets ciphering with the information available from the classmark 1 IE. The MSC initiates the authentication procedure and on receipt of the authentication response message, initiates the ciphering procedure. Refer to Section 2.8 for more information about ciphering. When ciphering is set, the MSC can accept the location update.

76 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

2.7

Authentication
The authentication procedure ensures that the subscriber identification (IMSI, TMSI) and the IMEI are valid. The system behavior for non valid identifications is at the discretion of the Network Operator. The procedure also validates the Ki value in the MS, and sends the RAND which is used to calculate the ciphering key.

IMSI/TMSI

When the subscriber accesses the network for the first time, the subscription is identified by the IMSI sent in the location_updating_request message. When the NSS has performed authentication and set the ciphering mode, the VLR assigns a TMSI, in an encrypted format over the Air interface. The next time the subscriber connects to the system, it uses the TMSI as its identification. If the MS has changed location area, it includes the old LAI. The new VLR interrogates the old VLR for the authentication information (IMSI and Ki value). The new VLR then assigns a new TMSI. This is shown in Figure 24. New TMSIs can be assigned by the serving VLR at any time. The subscriber identity is secure because the TMSI is always ciphered and changed regularly.

BTS

BSC

MSC

VLR

MS

MS moving and connecting in a new location area

info request

IMSI + KG

service request + TMSI + old LAI new TMSI


BTS MS BSC

MSC

VLR

Figure 24

Location Update with MS Sending LAI of Previous VLR

3BK 02974 AAAA TQZZA Ed. 07

77 / 240

2 Call Set Up

Authentication Procedure

The authentication procedure is initiated by the NSS. It sends an authentication_request message to the MS and sets a guard timer. This message contains:
" "

Parameters for the MS to calculate the response A ciphering key sequence number.

The ciphering key is calculated from the Ki value assigned to the IMSI or TMSI and the value RAND. The MS responds using the RAND and the value Ki assigned to its TMSI or IMSI. For MS originated calls, the MS uses:
" "

The TMSI, if available The IMSI, if no TMSI is assigned.

For MS terminated calls, the MS uses the TMSI or IMSI as requested in the paging message from the network. For emergency calls, the MS uses:
" " "

The TMSI, if available The IMSI, if no TMSI is assigned The IMEI, if there is no TMSI or IMSI. This can happen when there is no SIM in the MS.

When the MS sends the authentication_response message, the NSS stops its guard timer and validates the response. If the MS response is not valid, the network response depends on whether the TMSI or IMSI was used:
"

If the TMSI was used, the network can request that the MS sends its IMSI. If this is a valid IMSI, but is different from the the IMSI that the network associated with the TMSI, the authentication procedure is restarted with the correct parameters. If the IMSI is invalid, the network sends an authentication_reject message to the MS.

"

"

78 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

2.8

Ciphering
Ciphering is supported in the Alcatel 900/1800 BSS to protect information transmitted on the Air interface. This includes:
" " " "

Subscriber information such as the IMSI User data SMS and SS data Information such as called and calling party numbers.

Ciphering protects the information by using encryption. There are three different ciphering modes, the use of which depends on the MS classmark and the capability of the BTS. These modes are:
" " "

Encryption using algorithm A5/1 Encryption using algorithm A5/2 No encryption.

The two encryption algorithms are defined in GSM. If either is to be used, both the MS and BTS must have the same encryption capability.

MS Capability

The MS ciphering capability depends on whether it is a phase 1 MS, a phase 1 extended MS, or a phase 2 MS. Table 8 shows the different MS ciphering capabilities. Table 8
MS Type Phase 1 Phase 1 Extended Phase 2

MS Ciphering Capabilities
Capability No encryption and A5/1 No encryption and A5/1 and A5/2 No encryption No encryption and A5/1 No encryption and A5/2 No encryption and A5/1 and A5/2

Only phase 2 MSs can turn off ciphering or change the ciphering mode during a channel change procedure such as a handover. The ciphering capability of an MS is signalled to the BSS in the MS Classmark.

3BK 02974 AAAA TQZZA Ed. 07

79 / 240

2 Call Set Up

BSS Capability

The Alcatel 900/1800 BSS supports both uniform ciphering network configurations and mixed ciphering network configurations. A cell can be configured to support one of the following:
" " "

No encryption No encryption and the A5/1 algorithm No encryption and the A5/2 algorithm.

A uniform ciphering network configuration is where all cells have the same ciphering capability. A mixed ciphering network configuration is where the cells have different ciphering capabilities.

2.8.1

Ciphering Keys
The encryption used on the Air interface is provided by the physical layer hardware. This means that it does not distinguish between signalling and user traffic; therefore, the entire bit stream is encrypted. The encryption pattern added to the bit stream is calculated by the algorithm A5/1 or A5/2, using a ciphering key. For maximum security, the value of the Ciphering Key (Kc) is not a fixed value. It is calculated separately by the Home Location Register, BSC and the MS for each call. This means that the value Kc is never transmitted on the Air interface. The value Kc must be the same in the HLR, BSC and the MS. It is calculated using:
"

A value Ki, which is assigned to the IMSI when the user subscribed to the service A RAND, sent from the MSC during the authentication procedure.

"

The resulting value Kc is used to decipher the encrypted bit stream on the downlink, by the MS, and on the uplink, by the BTS.

80 / 240

3BK 02974 AAAA TQZZA Ed. 07

2 Call Set Up

2.8.2

Ciphering Procedure
The ciphering chosen by the BSC for a call depends on:
"

Choosing the Ciphering Mode

The algorithms that the Network Operator allows in the network. This information is sent in the permitted_algorithm message from the MSC during ciphering or external handover procedures. The ciphering capability of the MS. This information is sent to the BSC in the MS classmark. The ciphering capability of the BTS being used to set up the call.

"

"

If the MS capability is not compatible with that of the BTS or is not allowed by the Network Operator, then the BSC sets ciphering with no encryption.

Setting the Ciphering Mode

Ciphering is initiated by the MSC by sending a cipher_mode command to the BSC. This command contains the permitted_algorithms message. The BSC compares the permitted algorithms with the MS classmark and the BTS capability. If they match, the BSC sends an encryption_command message to the BTS containing the value Kc and the algorithm to be used. If there is no match and 'no encryption' is permitted, the BSC sends the encryption_command to the BTS indicating 'no encryption'. If the BTS and MS capabilities are not compatible and the MSC does not allow the 'no encryption' option, then the BSC sends a cipher_mode_reject message to the MSC. The BTS sends the ciphering_mode command on the SDCCH to the MS indicating the algorithm or 'no encryption'. If encryption is to be used the BTS sets its decryption mode ready to receive encrypted frames from the MS. The MS either:
"

Starts the encryption and sends an encrypted layer 2 acknowledgement message to the BTS. This prompts the BTS to start encryption mode for frames sent to the MS. Sends an unencrypted level 2 acknowledgement to the BTS.

"

The MS sends a ciphering_mode_complete message to the BTS which is passed transparently to the BSC. The BSC sends a cipher_mode_complete message to the MSC.

3BK 02974 AAAA TQZZA Ed. 07

81 / 240

2 Call Set Up

This process is shown in Figure 25.


MS BTS BSC MSC

algorithm or no encryption

Figure 25

Ciphering Procedure Only phase 2 MSs can change ciphering mode during a handover. If a phase 2 MS using the A5/1 algorithm is handed over to a cell which supports A5/2 and 'no encryption', the BSC instructs the target BTS to set the new ciphering algorithm and sends the value Kc. If a phase 1 MS using the A5/1 algorithm needs to be handed over, the target cell must support A5/1, as the phase 1 MS cannot change ciphering mode. For mixed ciphering networks, it is normal that the initial cipher_mode command from the MSC only allows a phase 1 MS to use the 'no encryption' option, as this is supported by all cells.

Ciphering During Handover

82 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

3 Call Handling
This chapter provides an overview of Call Handling and describes the supervision of a call in progress. The following specific areas are described: G In call modification The process of changing from and to data and speech, and the implications for the system. G Handover procedures Handover procedures, the underlying reasons for handover, and the measurements used to detect the need for handover. G Overload conditions.

3BK 02974 AAAA TQZZA Ed. 07

83 / 240

3 Call Handling

3.1

Overview
The Call Handling function is used for the supervision of calls in progress. Call Handling uses the In Call Modification, Handover and Overload Control processes to implement (in call modification) possible changes in the required teleservice. It also performs changes from one channel to another for active calls as the MS moves from cell to cell. Another area of supervision is the monitoring of the BTS and BSC for signalling saturation (Overload Control).

84 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

3.2

In Call Modification
In call modification allows the teleservice to be changed during a call. This means that a call does not have to be cleared, and a new call established, if more than one teleservice is to be used. The different types of in call modification are:
" " " " " " " "

Alternate between speech and a transparent data service Alternate between speech and a non transparent data service Change from speech to a transparent data service Change from speech to a non transparent data service Alternate between speech and transparent fax group 3 Alternate between speech and non transparent fax group 3 Data rate change for transparent fax group 3 Data rate change for non transparent fax group 3.

Calls requiring a change of service have to negotiate a 'dual service' before the normal assignment procedure. This is indicated in the set_up message, which is described in Chapter 2. Note Changing the data rate of a fax call is not a true in call modification procedure, as the teleservice is not changed (no dual service negotiation). The main difference between the in call modification procedure and a change of data rate for fax are as follows:
"

The in call modification procedure is triggered by a message from the MS The data rate change for fax is triggered by in band signalling from the fax machine to the MSC.

"

Both procedures use existing resources, therefore no new resources need to be allocated. All full rate traffic channels can be used for speech or data at any of the defined data rates. Both procedures use the mode 'modify procedure' to change the transmission mode. This is basically a normal assignment procedure but instead of a new channel being assigned, a new mode is assigned.

3BK 02974 AAAA TQZZA Ed. 07

85 / 240

3 Call Handling

3.2.1

In Call Modification Procedure


In call modification is initiated from an MS. This can occur during a call to a correspondent on the public telephone network or to an MS.

MS to MS Call

For an MS to MS call, both MSs must negotiate a dual service during call establishment. The MS initiates the procedure by sending a layer 3 CC modify message to the MSC, indicating the new mode. If the data call direction is different to the original call set up, then this message contains an indicator to reverse the call direction. The MS starts a guard timer for the procedure. The MSC checks the modify message. If it can accept the mode change, it starts the normal assignment procedure by sending an assignment_request message and starting a guard timer. This message contains a channel type (speech or data plus data rate). The BSS handles the normal assignment procedure as if assigning a TCH during call set up (described in Chapter 2), with the following exceptions:
"

When the BSC has checked and accepted the assignment_request message, it does not assign a new TCH. This is because it already has a TCH assigned for the transaction. The transaction is identified by the SCCP connection on which the assignment_request message was received. The channel_activation and channel_activation_acknowledge messages are replaced by the mode_modify and mode_modify acknowledge messages.

"

When the MSC receives the assignment_complete message from the BSC, it sends a layer 3 CC modify_complete message to the MS. This informs the MS that the procedure is successfully completed, and the MS can start transmitting in the new mode.

86 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

3.2.2

Group 3 Fax Data Rate Change


Group 3 facsimile equipment can change the data transmission speed to reduce the error rate. Fax data rates can be:
" " " "

9600 bit/s 4800 bit/s 2400 bit/s 1200 bit/s.

The Alcatel 900/1800 BSS supports both transparent and non transparent fax transmission. The BSS supports the Group 3 fax data rate change by:
" "

In band signalling for non transparent fax The mode modify procedure for transparent fax.

Non Transparent Group 3 Fax

For non transparent fax transmission, the data rate change is handled within the BSS, using in band signalling. This means that the frame size is signalled in the frame by a "frame delimiter" field. The Radio Link Protocol (RLP) in the BTS uses this information to control the data flow on the Air interface. The BSS does not need to change the channel mode. Transparent fax frames are passed transparently through the BSS. Therefore, in band signalling cannot be used within the BSS. The Group 3 fax equipment informs the MSC of a data rate change using in band signalling. The MSC then initiates a mode modify procedure using the assignment_request message. This procedure is the same as the mode modify procedure for in call modification, except that the MSC does not send a layer 3 Call Control mode_modify_complete message. This is because the procedure was not triggered by a layer 3 CC modify message from the MS. When the MSC receives the assignment_complete message from the BSC, it sets the new data rate to the correspondent.

Transparent Group 3 Fax

3BK 02974 AAAA TQZZA Ed. 07

87 / 240

3 Call Handling

3.2.3

Error Handling
The Alcatel 900/1800 BSS tries to provide the highest level of service at all times. In general, if errors occur during an in call modification, the BSS tries to revert to the old mode to keep the call active.

In Call Modification Example

For example, if the MS does not reply to the channel_mode_modify message from the BSC, it is assumed that it is still active but in the old mode. The BTS, however, has set the new mode. The BSC sends a mode_modify message to the BTS indicating the old mode. If the BTS acknowledges that it has reverted to the old mode, the call is kept active.

88 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

3.3

Handover
A handover changes an active call from one channel to another. The new channel can be in the same cell or in a neighbor cell. The types of handover are:
" " "

Internal External Directed retry D Internal D External.

Handovers ensure a high level of call quality. They are performed when the BSS detects that the call quality has dropped below a defined level, and the call can be better supported by a different channel. The call quality can drop due to problems in the cell, such as an interface or an equipment problem. Call quality can also be affected simply because the MS has moved to an area where the radio coverage from another cell is better. The BSS detects the need for a handover by:
"

Measuring the Air interface channel quality, MS and BTS power outputs and the timing advance Using an algorithm to see if the received information conforms to the criteria for handover Selecting a more suitable channel from a list of target cells and their available channels.

"

"

If the BSS decides that a handover is required, the exact sequence of events depends on the type of handover to be performed. In all cases:
" " "

A new channel is assigned, ready to support the call The MS moves over to the new channel On successful completion of the handover, the system clears the resources for the old channel.

Internal

Internal handovers take place between cells controlled by the same BSC. This can include channel changes within the same cell. More details about these handover cases is given in Section 3.3.3. External Handovers take place between cells controlled by different BSC's. These can be under control of the same MSC or of different MSCs. See Section 3.3.3 for more details about these handover cases.

External

3BK 02974 AAAA TQZZA Ed. 07

89 / 240

3 Call Handling

Directed Retry

Handovers can also be performed when there is congestion in a cell. If congestion exists, the TCH assignment can be queued. For more information about congestion management, refer to Section 2.5. If there is no available TCH for the normal assignment procedure, a Directed Retry can be performed. A Directed Retry is an attempt to assign an MS to a TCH in a cell other than the serving cell. There are two types of Directed Retry:
"

An Internal Directed Retry without queueing attempts to handover the call to a TCH of a neighbor cell controlled by the same BSC. An External Directed Retry attempts to handover the queued call to a TCH of a neighbor cell which is controlled by a different BSC.

"

For more information on Directed Retry, refer to the BSC Software Description document.

3.3.1

Radio Measurements
The BTS constantly monitors the radio link by:
" "

Measuring the received signal strength for active channels Measuring the received signal quality for active and inactive channels Measuring the received signal timing for active channels Collecting signal strength and quality measurements from the MS for the active channel Collecting adjacent cell BCCH signal strength measurements from the MS (adjacent cell BCCH frequencies are sent to the MS in the sys_info 5 message on the SACCH).

" "

"

The MS sends its measurements to the BTS in a layer 3 Radio Resource (RR) measurement_report message on the SACCH. The MS and BTS measurements are passed to the BSC in a layer 3 RR measurement_result message. These messages are sent once per multiframe and are processed by the BSC. The BSC uses this information to:
" " " " "

Perform power control for the BTS and MS Calculate whether a handover is needed Make TCH quality tables Make the target cell list Make a handover decision.

90 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

Power Control Need for Handover TCH Quality Tables Target Cell List

BTS and MS power control is described in Section 5.2.2. From a handover point of view, no handover decision is taken because of signal quality until the power levels have been set to maximum. The BSC calculates the need for a handover using an algorithm, the use of which is described in Section 3.3.2. The BSC uses the uplink idle channel measurements made by the BTS to make a table of TCH channels, classified by interference levels. This table is used to select a channel for assignment. A target cell list can be made by the BSC using the neighbor cell BCCH measurements sent by the MS. This is used to evaluate whether a neighbor cell can provide a better channel than the existing one. Handover decision is based on averaged measurements and the results are averaged over a period of time. For example, the BSC detects the need for a handover, based on one measurement that may have been caused by freak conditions changing the signal propagation for a short period. This measurement is averaged with other measurements and a handover decision may or may not result, depending on the other measurements.

Handover Decision

3.3.2

Handover Detection
Each time the BSC processes a set of Air interface measurements, it checks whether a handover is needed. If the need for a handover is detected, it triggers the target cell evaluation process, see Section 3.3.3. If the handover algorithm in the BSC detects the need for a handover, it produces a handover alarm. As the target cell evaluation is handled by the BSC, this alarm is also handled internally by the BSC. The alarm includes a cause value used by the BSC to evaluate which type of handover is required. There are five basic categories of handover:
" " " " "

Quality and Level Handover Better Zone Handover Better Cell Handover (Power Budget) Distance Handover Mobile Velocity Dependent Handover.

3BK 02974 AAAA TQZZA Ed. 07

91 / 240

3 Call Handling

Quality and Level Handover


These handovers are used to keep an active call connected when the signal quality falls below a defined threshold. If a handover is not performed, a radio link failure may be detected and the call cleared. This type of handover can be caused by the following events:
" " " "

Quality level too low on the uplink or downlink Signal level too low on the uplink or downlink Interference level too high on the uplink or downlink Signal level too low on the uplink or downlink compared to low threshold (microcells only) Signal level too low on the uplink or downlink compared to high threshold (microcells only) Several consecutive bad SACCH frames received (microcells only) Signal level too low on the uplink or downlink inner cell (concentric cells only).

"

"

"

Microcell handovers are described in detail in Section 7.5.2. Refer to Section 7.2 for more information on concentric cells. If the received signal level or the received signal quality is too low, the BSC performs BTS and MS power control to try and achieve the optimum level/quality ratio. This is described in Section 5.2.2.

92 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

Figure 26 shows a graph of received signal level and received signal quality. The hatched areas show where power control is successful. The solid gray shaded areas show where power control fails to achieve the desired level/quality ratio. These areas are where the BSC detects the need for a handover.
High Quality

Received Signal Quality

Level Desired Power Intercell Increase Quality Handover and Level to Improve Balance (no action Level needed)

Quality Intercell Handover Low Quality Low Level

Figure 26

Quality and Level Handover

Level Intercell Handover

The Level Intercell Handover area represents the range of measurements where the received signal quality is acceptable, but the received signal level is too low. If the power output levels are already set to the maximum allowed in the cell, the BSC generates a handover alarm with a cause value indicating the reason for handover. Although the quality of the signal is acceptable (and may be very good), the call is in danger of being lost if the signal level drops rapidly, causing a radio link failure. The handover is an intercell handover, as the serving cell cannot support the call at the required power level. The call is handed over to a channel in a cell which can support the call at the required level and quality.

3BK 02974 AAAA TQZZA Ed. 07


Power Decrease to Conserve Resources and Minimize Interference Power Increase to improve quality Quality Intracell Handover High Level Received Signal Level

93 / 240

3 Call Handling

Quality Intercell Handover

The Quality Intercell Handover area represents the range of measurements where both the receive signal quality and the received signal level are too low. If the power output levels are already set to the maximum allowed in the cell, the BSC generates a handover alarm with a cause value indicating the reason for the handover. The handover is an intercell handover, as the serving cell cannot support the call at the required quality and power level. The call is handed over to a channel in a cell which can support the call at the required quality and level.

Quality Intracell Handover

The Quality Intracell Handover area represents the range of measurements where the received signal quality is too low, but the received signal level is acceptable. This situation is caused by interference on the channel, so the call is handed over to another channel in the same cell.

Better Zone Handover


This is used in concentric cell configurations when the MS moves into the inner zone. If the inner zone has a free channel, an interzone handover is triggered. This enables the MS to be supported on a channel requiring a lower power level, therefore creating less interference in the cell. The detection of this type of handover is performed on signal level measurements only (SACCH of serving cell, BCCH of adjacent cells). This is shown in Figure 27. This type of handover can be caused by the signal level being too high on the uplink and downlink outer zone (concentric cells only).

94 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

High Power Outer Zone

Low Power Inner Zone MS Handed Over to Low Power Zone

Figure 27

Better Zone Handover

Better Cell Handover


This is used to handover the MS to a cell which can support the call using lower BTS and MS power levels. The algorithm in the BSC calculates the power levels for the current cell, and the power levels required by adjacent cells from the adjacent cell information sent by the MS. This is shown in Figure 28. This type of handover is often referred to as a power budget handover, as it uses the Power Budget (PBGT) parameter to detect whether an adjacent cell can be used. If the PBGT for an adjacent cell gives a 'better' reading for a certain amount of time (a defined number of SACCH frames), then a handover alarm is produced. This type of handover can be caused by the following events:
" "

Power budget is greater than handover margin threshold High signal level in neighbor microcell (macrocell to microcell handover).

3BK 02974 AAAA TQZZA Ed. 07

95 / 240

3 Call Handling

BSS 1 = Best Cell

BSS 2 = Best Cell

Serving Cell BSS 1

Target Cell BSS 2

Zone for Power Budget Handover from BSS 1 to BSS 2

Figure 28

Better Cell Handover (Power Budget)

Distance Handover
This handover occurs when the propagation delay between the BTS and the MS is considered excessive. The MS is considered to be too far from the BTS and needs to be served by a closer BTS. This is shown in Figure 29. Under normal circumstances, as the MS moves away from a BTS, a Quality and Level or Better Cell handover takes place. However, under certain conditions which change the propagation qualities of a signal, a cell can provide a very high quality signal outside of the normal operating range of the serving cell. These propagation qualities are often due to climactic conditions which can change suddenly. If the high quality signal 'disappears' due to a change in the weather, the call would be lost. The distance handover ensures that this does not happen by handing the MS over to a 'closer' cell once a distance limit is exceeded. This type of handover is caused by too great a distance between the MS and the Base Station (BS).

96 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

BSS 1

Area of Normal Cell Boundaries

Figure 29

Distance Handover

Mobile Velocity Dependent Handover


In a hierarchical cell structure, where mini or microcells are overlaid by an umbrella cell (macrocell), fast moving MSs are handled by the upper layer cell. Discrimination of the speed of an MS is based on the dwell time of that MS in a lower layer cell. Depending on the time elapsed in the serving cell, the call is transferred to the lower layer cell or the umbrella cell. If the dwell time in the serving cell is above the threshold, the MS is considered slow moving and is sent to the lower layer cell that triggered the handover. If the dwell time is below the threshold, the MS is considered fast moving. To prevent a high number of handovers between the smaller lower layer cells, the call is sent to the umbrella cell. Dwell time is only calculated if there has been a power budget handover from another lower layer cell. This is to avoid sending a call to the umbrella cell in the following cases:
"

A call initiated at the limit of the lower layer cell

3BK 02974 AAAA TQZZA Ed. 07

BSS 2

Distance Handover Area from BSS1 to BSS2

97 / 240

3 Call Handling

"

A call transferred from the umbrella cell to the lower layer cell, just before reaching the limit of that cell After an external handover, when there is no information on the preceding cell and handover cause.

"

Whatever the dwell time, any emergency handover sends the call to the umbrella cell, which acts as the rescue cell. The load on the umbrella cell is taken into consideration when determining the threshold at which handovers are performed. Saturation of the umbrella cell can cause the loss of calls, when a handover is required from another umbrella cell or a lower layer cell. As the load on the umbrella cell increases, the dwell time threshold is increased, keeping some MSs in the lower layer cells. When the load on the umbrella cell is very high, speed discrimination is disabled, and priority is given to the load in the umbrella cell. Figure 30 shows a graph of umbrella cell load and minimum dwell time.
Load in Umbrella Cell Macrocell saturated High load Traffic regulation Speed discrimination disabled

Low load

Max speed discrimination in force

Macrocell with little traffic

Low minimum dwell time

High minimum dwell time

Minimum Dwell Time

Figure 30

Umbrella Cell Load in Mobile Velocity Dependent Handover

98 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

3.3.3

Target Cell Evaluation


Cell evaluation is performed by the BSC. Once a handover alarm is detected within the BSC, it evaluates the neighbor cells and compiles a list of possible target cells. The serving cell can be on the target cell list. The cells are evaluated and ranked by preference, calculated by one of the two algorithms, ORDER or GRADE. The Network Operator chooses which algorithm is to be used on a cell by cell basis. The BSC tries to handover to the most suitable cell. If this cell is controlled by the BSC, the BSC handles the handover procedure. If the target cell is controlled by another BSC, the serving BSC sends a handover_request message to the MSC.

Target Cell

The exact calculation performed to choose the target cell depends on the algorithm used and the cause of the handover alarm. The target cell is chosen taking into account the following criteria:
" " " " " " " "

Received signal level Power budget Number of free channels Relative load on the traffic channel of the cell Maximum power allowed in cell HO_MARGIN parameter MS distance from target BTS Handover cause.

The HO_MARGIN parameter is an O&M parameter set by the Network Operator. It is used to prevent a call being continually handed over between two cells. For example, following a power budget handover, the new cell immediately starts power budget calculations for its neighbor cells. It may find that the original cell is giving a better power budget reading and try to hand back immediately. This effect can be caused by slight climactic changes which affect the propagation of signals. It is known as the 'ping pong' effect. The HO_MARGIN parameter stops a call being handed back to a cell from which it has just been handed over. There is also an O&M parameter, W_PBGT_HO which can be set by the OMC R operator, to add a weighting for the power budget parameters of cells controlled by another BSC. Refer to OMC R Configuration Management Services for more information. The target cell chosen also depends on the MS classmark (see Section 2.6) and its compatibility with the BTS's ciphering capabilities (see Section 2.8).

3BK 02974 AAAA TQZZA Ed. 07

99 / 240

3 Call Handling

The procedures initiated to handover a call depend on which cell has been chosen as the target cell.

Internal: Intracell

If the target cell and the serving cell are the same, the call is handed over to a channel in the same cell. This is an intracell handover. This type of handover is most commonly due to interference in the cell. It is controlled by the BSC. If the target cell is not the same as the serving cell but is controlled by the same BSC, this is called an intercell intraBSS handover. This handover is normally controlled by the BSC. However, the Network Operator can specify that this type of handover is controlled by the MSC. If the target cell and the serving cell are not controlled by the same BSC, but the two BSC are controlled by the same MSC, this is called an interBSS intraMSC handover. This handover is controlled by the MSC. If the target cell and the serving cell are controlled by different BSCs and the two BSCs are controlled by different MSCs, this is called an interBSS interMSC handover. The control of this handover is shared between the MSCs. Handovers controlled by the BSC are called internal handovers. Handovers controlled by the MSC are called external handovers.

Internal (IntraBSS): Intercell

External (InterBSS): IntraMSC External (InterBSS): InterMSC

3.3.4

Synchronous and Asynchronous Handover


The handover to the target cell can be synchronous or asynchronous. A synchronous handover can be performed if the master clocks of the serving cell and the target cell are synchronized. This is the case when:
" "

The serving cell and the target cell are the same cell The BTSs of the serving cell and the target cell are in a collocated configuration.

BTSs in a collocated configuration take the clock pulse from one BTS in the configuration. For a synchronous handover, the MS does not have to resynchronize with the target BTS. Therefore, the physical context procedure for power levels and timing advance does not have to be performed after the MS accesses the target cell. For an asynchronous handover, the MS has to synchronize with the target cell before transmitting any user traffic.

100 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

Synchronous Internal Handover


This Section describes the message flow for a synchronous internal handover. The example in Figure 31 is for a handover of a TCH between two separate cells controlled by two BTSs in a collocated configuration.

Measurement Reporting

The MS and BTS take measurements on the Air interface as described above. The MS sends measurement information to the BTS in a measurement_report message. The BTS sends MS and BTS measurements to the BSC in a measurement_results message. The BSC detects the need for a handover and creates a handover alarm indicating the reason for the handover. The BSC evaluates possible target cells and creates a cell list. For this example, the first cell on the list (target cell) is a cell controlled by this BSC and the BTSs of both serving and target cell are collocated. Once this cell is chosen, the BSC initiates the synchronous internal handover procedure. The BSC sends a physical_context_request message to the serving BTS, requesting current timing advance and power level information. This information is passed to the target BTS. The serving BTS responds with a physical_context_confirm message.

Handover Detection

Channel Activation

When the BSC receives the physical context information, it sends a channel_activation message to the target BTS, indicating:
" " " "

The channel to be used The MS timing advance to be applied The encryption algorithm and ciphering key A Discontinuous Transmission (DTX) indicator for uplink (not used) and downlink (see Section 5.2.4) The MS power to be used The BTS power to be used.

" "

The target BTS sets its resources to support the channel. It then uses a channel_activation_acknowledgement message to reply to the BSC. This lets the BSC know that the target BTS is ready. The target BTS also starts transmission of SACCH/Fast Associated Control Channel (FACCH) frames so that when the MS accesses this BTS, it receives sys_info 5 and sys_info 6 messages. The MS also receives the timing advance and power control updates.

3BK 02974 AAAA TQZZA Ed. 07

101 / 240

3 Call Handling

Handover Command

The BSC sends the handover_command message transparently through the BTS to the MS. This message contains:
" " "

The new channel and its associated control channel The target cell description A power level indication for the MS initial access to the target cell A handover reference The timing advance to be used in the target cell Any cipher mode information (phase 2 MSs can change cipher mode during a handover procedure).

" " "

The Handover

The MS releases its connection with the serving BTS and sends four consecutive access bursts to the target BTS on the uplink SACCH. These bursts include the handover reference and use a timing advance of 0. The BTS calculates the timing advance (it may have changed since the physical context procedure). It sends a handover_detection message to the BSC indicating the timing advance measured for the access burst. If the MS timing advance needs to be updated, the BSC sends this information in the physical_information message on the FACCH channel associated with the TCH. The MS then sets ciphering (as required). It sends its first frame, SABM, using the timing advance information either as sent in the handover_command message, or as updated in the FACCH frames. When the BTS receives the frame from the MS, it sends an acknowledgement frame to the MS and an establish_indication message to the BSC. This informs the BSC that the radio link has been established. The BSC starts BTS and MS power control. On receipt of the acknowledgement frame, the MS sends a handover_complete message to the BSC. The MS can now start transmitting on the new channel. The BSC informs the MSC of the handover in a handover_performed message and initiates the release of the old channel.

102 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

MS

Target BTS

Serving BTS

BSC

MSC

HO detect HO alarm cell evaluation

release with serving BTS

Figure 31

Synchronous Internal Handover

3BK 02974 AAAA TQZZA Ed. 07

103 / 240

3 Call Handling

Asynchronous External Handover


This section describes the message flow for an asynchronous external handover. The example in Figure 32 is for a handover of a TCH between two separate cells controlled by two different BSCs.

Measurement Reporting

The MS and BTS take measurements on the Air interface as described above. The MS sends measurement information to the BTS in a measurement_report message. The BTS sends MS and BTS measurements to the BSC in a measurement_results message. The BSC detects the need for a handover and creates a handover alarm indicating the reason for the handover. The BSC evaluates possible target cells and creates a candidate cell list. To initiate the external handover procedure, the BSC sends a handover_required message to the MSC including the candidate cell list. It also starts a timer to prevent it sending the same cell list. It can only re send the cell list when the timer times out, or if it receives a handover_request_reject message from the MSC. The MSC chooses the target cell from the cell list. It sends a handover_request to the target BSC to inform it that an MS is going to be handed over. This message contains:
" " " " " " "

Handover Detection

Channel type required Cipher mode information MS classmark information Serving cell identification Target cell identification Downlink DTX flag Handover cause.

Channel Activation

The target BSC initiates the channel activation for the new channel with the channel_activation message. The target BTS sets its resources to support the new channel, starts sending the SACCH/FACCH and sends a channel_activation_acknowledgement message to the target BSC.

Handover Command

The target BSC builds a handover command. This command is sent to the MSC in the handover_request_acknowledgement message. The handover command contains:
" "

The new channel and its associated control channel The target cell description

104 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

" "

A handover reference Any cipher mode information (phase 2 MSs can change cipher mode during a handover procedure).

The MSC forwards the handover_command message to the serving BSC. The serving BSC sends the handover command message to the MS.

The Handover

The MS releases its connection to the serving BTS. It synchronizes with the target BTS using the FCCH and Synchronization Channel (SCH) information. Once synchronized, the MS continually sends access burst on the uplink SACCH until it receives the physical_information message on the FACCH from the target BSC. When the target BTS receives an access burst, it checks the handover reference and calculates the timing advance. This is sent to the target BSC in the handover_detect message. The target BSC informs the MSC of the handover detection and establishes a switching path between the allocated Abis and A interface resources. When the MS receives the physical_information message, it sends its first frame on the new channel using the timing advance sent in the physical_information message. The target BTS acknowledges the MS's first frame and sends an establish_indication message to the target BSC, and an acknowledgement to the MS. On receipt of the acknowledgement, the MS sends a handover_complete message on the uplink FACCH to the target BSC. The target BSC informs the MSC that the handover has been performed. The MSC initiates the call clearing procedure towards the serving BSC.

3BK 02974 AAAA TQZZA Ed. 07

105 / 240

3 Call Handling

MS

Target BTS

Serving BTS

Target BSC

Serving BSC

MSC

HO detect HO alarm

release with serving BTS handover detect

set up switching path between Abis & A interfaces

CALL CLEARING PROCEDURE ( old connection ) Refer to Chapter 4

Figure 32

Asynchronous External Handover

106 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

3.4

Overload Control
A lot of telecommunications signalling is required for the BSS to support communication between MSs in the cells under its control and the MSC. Telecommunication processors in the BTS or BSC can become overloaded. To avoid a sudden loss of communication when a processor becomes saturated, the BSS controls the load on these processors in the following steps: 1. Taking local action to reduce the load. 2. Taking global BSS action to further reduce the load. Note The telecommunications processors of the MSC can also become overloaded. However, MSC overload control is not the domain of the BSS.

3.4.1

BTS Overload
The BTS Frame Unit (or TRE for a BTS A9100) handles all the telecommunications signalling on the Air interface. If the FU or TRE becomes saturated, this can result in the loss of calls. Therefore, the BTS monitors the load and takes action where appropriate. On initial detection of the overload condition, the BTS takes local action to reduce the load. If the BTS local action does not reduce the load, the BTS sends overload messages to the BSC, which can decide to take global action. The different stages of BTS overload, from detection to resolution, are described below.

BTS Overload Detection

The BTS monitors the load on the FU or TRE by measuring the free time on the FU or TRE's Signalling Control Processor (SCP) and the free message space on the associated buffers. If either of these passes a set threshold, a counter is incremented. If a threshold is not passed again within a given time, the counter is decremented. The counter has two thresholds. If the first of these is passed, the BTS takes local overload action. If the second of these is passed the BTS sends overload messages to the BSC. When local action is triggered in the BTS, it discards low priority messages such as the establish_indication message to reduce the load on the SCP .

BTS Overload Action

3BK 02974 AAAA TQZZA Ed. 07

107 / 240

3 Call Handling

3.4.2

BSC Overload
The BSC has two entities handling telecommunications signalling:
"

The TCU handles telecommunications signalling for the Abis interface The DTC handles telecommunications signalling for the A interface.

"

The different stages of BSC overload, from detection to resolution, are described below.

BSC Overload Detection

For the BTS, overload is calculated on the processor free time and the free message space of the associated buffers. As the BSC handles more signalling traffic than the BTS, the detection of an overload, and whether to trigger local or global defense actions, is more complicated. The BSC uses an algorithm that takes into account which processors are affected, the level of overload, and which buffers are affected. Each processor has a local overload controller. The BSC's centralized overload controller is responsible for global overload defence actions. Local action in the BSC is taken by the local overload controller on each processor. Local actions reduce the load on an individual board. The local actions are:
"

BSC Local Overload Action

TCU Action The TCU discards a percentage of the measurement_result messages received from the BTS. The percentage of discarded messages is increased and decreased in steps, under the control of the local overload control. This only affects the handover and power control algorithms which still function but with less information.

"

DTC Action When the DTC detects an overload, its state is set to congested on the BSC database. This means that it cannot be selected by the resource management software to provide a new SCCP connection. Also, the DTC cannot send connectionless messages to the MSC.

"

BSC Global Overload Action The BSC controls global actions for the whole BSS. Global action reduces the amount of telecommunications signalling traffic in the BSS by inhibiting new calls. The BSC bars MS access classes either in one cell if the global action is requested by a BTS or TCU, or in several cells if a DTC or MSC are overloaded.

108 / 240

3BK 02974 AAAA TQZZA Ed. 07

3 Call Handling

MS Access Class Barring

When the BSC receives a request for global overload action from a BTS, from the MSC, or from one of its local overload control processors, it checks the message for errors. If it can accept the request, it builds new system information messages (1 to 4). These messages are sent on the BCCH. They bar certain MS classes from sending channel_request messages on the RACH. If the overload condition persists, the BSC can change the system information messages to bar more MS access classes from using the RACH. When the BTS is barring access classes, its behavior can be modified from the OMC R by modifying the following parameters:
"

AUT_BAR enables/disables the automatic banning of cells after all access classes have been barred. This forces the MS to camp on another cell. EC_BAR enables/disables the automatic barring of emergency calls. EN_BSS_OVRL_CLASS_BARR enables/disables the ability of the BSC to perform global action for BTS to BSC overload conditions.

"

"

The number of access classes that can be barred and unbarred in one step can also be configured from the OMC R.

MS Access Class Unbarring

When an overload message is received from the BTS or when an overload is detected in the BSC, a timer is set. If no overload message is received from the BTS, or no overload detected in the BSC during the period of the timer, the timer expires. When the timer expires, the BSC unbars some access classes according to a defined algorithm.

3BK 02974 AAAA TQZZA Ed. 07

109 / 240

3 Call Handling

110 / 240

3BK 02974 AAAA TQZZA Ed. 07

4 Call Release

4 Call Release
This chapter provides an overview of Call Release and describes the procedures which ensure resource allocation to a call. It specifically describes Call Release procedures in normal service plus the following special cases: G G G G Following Reset BSC initiated BTS initiated MS initiated

This chapter also describes Remote TC Alarms, and the processes used to break a connection and disconnect the resources, depending on the nature of radio transmission.

3BK 02974 AAAA TQZZA Ed. 07

111 / 240

4 Call Release

4.1

Overview
The Call Release procedures ensure that resources allocated to a call are free for reuse when they are no longer required by the current call. Call Release procedures are required when:
" " "

A call is finished and either the called or calling party hang up An MS is turned off A call is handed over and the resources for the original call are released A call is modified and the resources for the original channel are released There is operator intervention, such as a channel being blocked There is a failure There is a radio link failure The system detects a LAPDm failure.

"

"

" " "

If a call is terminated normally, the Call Release procedures are triggered automatically. If the call is terminated abnormally, the system has to detect that the resources are no longer required and release them. For a complete Call Release, the following resources must be released:
" " " "

A interface resources Abis interface resources Air interface resources MSC resources:
D D D

Layer 3 for the A interface SS7 signalling for the A interface Layer 1 physical resources for the A interface. Layer 3 for the A, Abis and Air interface Layer 2 SS7 for the A interface and LAPD for the Abis interface Layer 1 physical resource for the A and Abis interface.

"

BSC:
D D D

112 / 240

3BK 02974 AAAA TQZZA Ed. 07

4 Call Release

"

BTS:
D D D

Layer 3 for the A, Abis and Air interface Layer 2 LAPD for the Abis interface and LAPDm for the Air interface Layer1 physical resources for the Abis and Air interface Layer 3 for the Air interface Layer 2 LAPDm for the Air interface Layer 1 for the Air interface.

"

MS:
D D D

3BK 02974 AAAA TQZZA Ed. 07

113 / 240

4 Call Release

4.2

Call Release Procedures in Normal Service


The Call Release procedures, and the order in which they are triggered, depend on the reason for the release. This section describes the following Call Release scenarios, which occur during normal service:
" "

Normal Release (Calls terminated by Call Management) Calls terminated following a channel change.

Special cases, including detailed behavior of the MSC, BSC, BTS and MS are described later in this chapter.

4.2.1

Normal Release
Call termination initiated by Call Management is considered to be a normal reason for Call Release. In this type of Call Release, the MSC initiates the release. Before this can happen, the MS must inform the MSC that it has disconnected the call. This is done with layer 3 messages passed transparently through the BSS between the MS and MSC, as shown in Figure 33.
MS BSS MSC

Figure 33

MS Disconnecting a Call

Once the MSC has confirmation that the MS wants to disconnect and no longer requires the connection, it initiates the release procedure towards the BSC. This procedure:
" "

Releases the circuit (if applicable) Releases the SCCP connection.

The BSC responds to the MSC to clear the connection on the A interface, and initiates the Call Release procedure toward the BTS and MS. This procedure releases the radio resources.

114 / 240

3BK 02974 AAAA TQZZA Ed. 07

4 Call Release

This action triggers the MS to release the LAPDm connection (disc message) and the BSC to release physical resources allocated to the call. This is shown in Figure 34.
MS BTS BSC MSC

release of A interface resources Timer start (SCCP release) disable remote TC alarm detect Timer start (release indication)

Timer

Timer

Figure 34

Normal Call Release

MSC actions

The MSC initiates Call Release at the end of the MS transaction. The MSC can be informed of the end of the MS transaction:
" "

By a level 3 disconnection message from the MS (Figure 33) By a disconnection message from the Network Operator if the correspondent terminates the call At the end of a service call (i.e., SMS or location updating).

"

The normal release procedure of the MSC releases both the A interface resources used for the call, if any, and the SCCP connection used for the signalling which controls the connection.

3BK 02974 AAAA TQZZA Ed. 07

115 / 240

4 Call Release

The MSC initiates the release procedure by sending a clear_command message to the BSC. This command can include a cause value in the Mandatory Information Element (MIE). The BSC accepts the command even if no cause value is included. It immediately releases the A interface resources for the call and replies to the MSC with a clear_complete message. This is shown in Figure 35.
MS BTS BSC MSC

release of A interface resources Timer start (SCCP release) Timer start (release indication)

Figure 35

Initiation of Normal Release by MSC The BSC initiates the release of the Abis and Air interface resources. It also sets a timer to ensure that the MSC releases the SCCP signalling resources. On receipt of the clear_complete message from the BSC, the MSC releases the resources associated with the A interface and initiates the release of the SCCP signalling resources by sending the SCCP_released message to the BSC. The BSC stops its timer and sends the SCCP_release_complete message. The SCCP resources are now released and can be used for another call. If the BSC timer expires before the SCCP_released message is received, then the BSC force releases the SCCP connection.

BSC/BTS/MS Interactions

The normal Call Release procedure towards the MS/BTS releases:


" "

The radio resources associated with the call The Radio Frequency (RF) channel. A channel_release message to the MS via the BTS A deactivate_SACCH message to the BTS.

The BSC initiates the release of the radio resource by sending:


" "

116 / 240

3BK 02974 AAAA TQZZA Ed. 07

4 Call Release

The channel_release message prompts the MS to send a disc message to the BTS to release the LAPDm resource. When this is received, the BTS acknowledges this with a ua message to the MS and sends a release_indication message to the BSC. This procedure is supervised by a timer in the BSC. The BSC considers the MS disconnected and starts the RF channel release when:
" "

The timer expires The BSC receives the release_indication message and stops the timer.

When the BTS receives the deactivate_SACCH message, it stops sending SACCH information and disables the remote transcoder alarm detection. This stops the sending of Transcoder (TC) alarms to the BSC when the TC detects inactivity on the channel. This is shown in Figure 36. If the MS does not receive the channel_release message, it considers the stopping of SACCH information as a radio link failure and performs a local release.
MS BTS BSC MSC

release of A interface resources Timer start (SCCP release) disable remote TC alarm detect Timer start (release indication)

Figure 36

BSC/BTS/MS interactions in Normal Call Release Once the BSC considers the MS disconnected, it initiates release of the RF channel from the BTS. In a normal call release procedure, this occurs following the release of the MS from the Air interface (as described earlier in this section).

3BK 02974 AAAA TQZZA Ed. 07

117 / 240

4 Call Release

Before releasing the RF channel, the BSC sends a physical_context message to the BTS and starts a timer to supervise the response. The response from the BTS is a physical_context_confirm message which contains the last LAPDm performance measurements for the RF channel. On receipt of the physical_context_confirm message, or after the timer has timed out, the BSC sends an RF_channel_release message to the BTS and starts a timer to supervise the release. The BTS releases the level 1 and 2 resources for the channel and replies with an RF_channel_release_ack message. On receipt of the acknowledgement, the BSC releases all resources for the RF channel. This is shown in Figure 37.
MS BTS BSC MSC

Timer

Timer

Figure 37

Normal Release Final Steps If the timer supervising the release times out, the BSC sends the RF_channel_release message again and restarts the timer. If the timer times out again, the BSC releases all resources locally. It also sends an O&M error report to the OMC R with a cause value indicating that the RF channel release procedure has failed. Note The RF channel can be released locally by the BTS and still be active. If the RF channel is still active, it is released when the BSC attempts to assign it to another call with a channel_activation message. The BTS replies with a channel_activation_nack and the BSC releases the channel (refer to Chapter 3 for more information).

118 / 240

3BK 02974 AAAA TQZZA Ed. 07

4 Call Release

4.2.2

Calls Terminated Following a Channel Change


This section describes the Call Release procedure following a successful channel change procedure. The case presented is an external intercell handover. For an internal channel change, the serving and target BSCs are the same, and in some cases, the serving and target BTSs are the same. The target BSC receives confirmation of the successful handover from the MS when the MS sends the handover_complete message. This message is passed transparently through the target BTS. Refer to Section 3.3 for more information about handovers. The target BSC informs the MSC of the handover and initiates the Call Release procedure towards the serving BSC, by issuing a clear_command message. The serving BSC issues a channel_release message to the MS and a deactivate_SACCH message to the serving BTS. The normal Call Release procedure described in Section 4.2.1 continues between the serving BSC, the serving BTS, the MSC and the MS. This is shown in Figure 38.
MS Target BTS Serving BTS Target BSC Serving BSC MSC

NORMAL CALL RELEASE PROCEDURE continues on the old connection - refer to Figure 34

Figure 38

Call Release Following a Channel Change

3BK 02974 AAAA TQZZA Ed. 07

119 / 240

4 Call Release

4.3

Call Release - Special Cases


Call Release can occur for reasons outside normal service. This section treats the following special cases in which Call Release happens:
" " " " "

Call Release following Reset BSC initiated Call Release BTS initiated Call Release MS initiated Call Release Remote TC Alarms.

4.3.1

Call Release Following Reset


Resets are used in software/hardware failure situations, or when the database is corrupted and recovery procedures have failed. The MSC can reset all calls within a BSC or an individual circuit. For example, if the MSC loses dynamic information regarding calls (i.e. preventing it from providing such services as accounting), it can send a reset or reset_circuit message to the BSC.

Reset

The MSC initiates Call Release when it has to release all calls associated with the BSS (Reset). The MSC sends a reset message containing a cause value to the BSC. The BSC then:
" " "

Sends an alarm to the OMC R Sends a block message to the MSC to block circuits Starts to clear all calls in the BSS. For each call, the procedure in Section 4.2.1 is repeated.

For each SCCP connection on the A interface, the BSC can send an SCCP_release message and release any A interface resources associated with the SCCP . A timer allocates a certain amount of time for the calls to clear. When the timer expires, the BSC sends a reset_ack message to the MSC. Figure 39 shows the Call Release process after a reset is initiated.

Reset Circuit

The reset circuit procedure is initiated from the MSC. The procedure informs the BSC that an individual circuit is no longer active in the MSC. This triggers the call clearing procedure if the circuit has an active SCCP connection.

120 / 240

3BK 02974 AAAA TQZZA Ed. 07

4 Call Release

The MSC sends a reset_circuit message to the BSC for each circuit to be reset. Depending on the resources allocated, this can trigger the BSC to:
" " "

Release the A interface resources Initiate the release of the SCCP Initiate Call Release towards the BTS and MS.
BTS BSC MSC

MS

send alarm to OMC R circuits blocked

timer

Figure 39

Call Release Following Reset Note If this procedure is invoked due to SCCP problems, then messages on the A interface may not be passed. The MSC and BSC locally release resources for the A interface connections. Refer to Section 4.3.2 for more details.

3BK 02974 AAAA TQZZA Ed. 07

121 / 240

4 Call Release

4.3.2

BSC Initiated Release


The BSC is involved in Call Release for both the A interface and Abis/Air interfaces. The BSC initiates Call Release on the A interface when events internal to the BSS terminate communication with the MS. The Call Release towards the MS may already be in progress or have finished when the BSC initiates a release on the A interface. If the MS is still connected when the BSC initiates a release on the A interface, the release towards the MSC is triggered by the clear message from the MSC to the BSC.

Towards the MSC

The BSC initiates the release towards the MSC by sending a clear_request message. It also starts a timer to supervise the procedure. The MSC releases resources for the A channel and sends the clear_command message to the BSC. This command contains a cause value indicating that the BSC initiated the release. From this point, the Call Release follows the procedure described for normal Call Release (refer to Section 4.2.1). The procedure starts with the BSC releasing A channel resources. It initiates the release procedure towards the MS (if still attached), and returns a clear_complete message to the MSC. This sequence is shown in Figure 40.

MS

BTS

BSC

MSC

NORMAL CALL RELEASE PROCEDURE continues refer to Figure 34

Figure 40

BSC initiated Call Release toward the MSC

122 / 240

3BK 02974 AAAA TQZZA Ed. 07

4 Call Release

Towards the MS/BTS

The Call Release procedure towards the MS/BTS releases:


" "

The radio resources associated with the call The RF channel. A channel_release message to the MS via the BTS A deactivate_SACCH message to the BTS.

The BSC initiates the release of the radio resource by sending:


" "

This is the Normal Release procedure described in Section 4.2.1. Note In this process, once the BSC considers the MS disconnected, it initiates release of the RF channel from the BTS. This can occur following: G G G G The release of the MS from the Air interface (as in the Normal Release procedure) A handover, when the BSC is sure that the MS has successfully changed to the new channel. Refer to Section 4.2.2. An immediate assign procedure failure. This ensures that the SDCCH is available for reuse as quickly as possible. A normal assignment failure or handover failure. This ensures that the TCH is available for reuse as quickly as possible.

BSC Initiated SCCP Release


The BSC initiates an SCCP release when:
" "

A release procedure has failed Inactivity is detected in the BSC SCCP entity.

Failed Release Procedure

If there are no resources allocated to a call and the normal release of the SCCP connection has failed, the BSC forces the release of the SCCP connection:
" "

Internally by sending a level 3 command to its SCCP entity Externally by sending an SCCP_released message to the MSC.

The BSC does not wait for a reply from the MSC before releasing the SCCP connection. If the original failure is due to a problem on the SCCP connection or in the BSC SCCP entity, the SCCP_released message may not be sent. If the message is sent, the MSC replies with an SCCP_release_complete message and releases any allocated resources.

3BK 02974 AAAA TQZZA Ed. 07

123 / 240

4 Call Release

Inactivity Procedure

The BSC performs an inactivity procedure for each SCCP connection. If the BSC detects inactivity, it assumes that the associated transaction is no longer active and therefore:
" " "

Performs Call Release on the Air and Abis interfaces Initiates a reset circuit procedure if an A channel is active Initiates the release of the SCCP connection.

4.3.3

BTS Initiated Call Release


The BTS initiates a Call Release only if it detects a LAPD failure or when O&M requests a restart of the BTS. Otherwise the role of the BTS in Call Release is to:
" " "

Relay channel release messages to the MS Deactivate the SACCH under control of the BSC Send a release_indication message to the BSC when the MS releases the LAPDm connection.

LAPD Failure

When the BTS detects a LAPD failure on a link between one of its frame units and the BSC, it forces the release of all MSs on active channels associated with that FU (or TRE for a BTS A9100). The BTS stops SACCH frames and sends a layer 2 disconnect message to each affected MS. It also starts a timer to supervise each LAPDm disconnection. The LAPD connection cannot be re established until the BTS receives an acknowledgement, or the timer expires for each LAPDm connection. If an MS sends an acknowledgement, the BTS releases the RF resources. If an MS does not respond, the BTS continues to send layer 2 disconnect messages up to a predefined number. It then waits for the timer to expire and the BTS releases the RF resources.

Note

If the maximum number of disconnect retries is reached, the BTS LAPDm entity sends an error report to the BSC. This does not stop the timer supervising the disconnection. When all MSs are disconnected, the BTS attempts to re establish the LAPD connection. The BTS then sends an error report to the BSC with a cause value indicating O&M intervention. This cause value indicates that the FU or TRE has cleared all calls. The BSC reinitializes the link with the frame unit and starts Call Release for the affected calls with the MSC. This sequence is shown in Figure 41.

124 / 240

3BK 02974 AAAA TQZZA Ed. 07

4 Call Release

MS

BTS
Detection of LAPD failure. BTS stops sending SACCH frames. timer timer timer

BSC

MSC

release RF resources release RF resources release RF resources Re establish LAPD connection

Re initialize FU or TRE link

NORMAL CALL RELEASE PROCEDURE continues refer to Figure 34

Figure 41

BTS initiated Call Release following LAPD failure The BTS initiates a Call Release if its O&M entity requests a restart of an FU (or TRE for a BTS A9100). The FU or TRE's response to a restart request is to stop sending frames on the Air interface. The BTS starts a timer to supervise the disconnection of the MSs. The timer allows enough time for the MSs to detect a radio link failure due to the lack of SACCH frames. The BTS RF performs a local release. The BTS resets the FU or TRE and waits for the timer to expire. When the timer expires, the FU or TRE attempts to reestablish the LAPD link with the BSC. The BTS sends an error report to the BSC with a cause value indicating O&M intervention. The BSC releases the RF resources and initiates a Call Release with the MSC.

O&M Intervention

3BK 02974 AAAA TQZZA Ed. 07

125 / 240

4 Call Release

4.3.4

MS Initiated Call Release


The MS can initiate a Call Release by:
" "

Initiating a radio link failure Disconnecting the LAPDm connection.

MS Initiated Radio Link Failure

If SACCH frames are no longer received from the MS, the BTS starts to count the number of missing frames. When the BTS has counted a certain number of missing SACCH frames, it considers that the radio link has failed. This happens when the MS 'disappears' from the Air interface (adverse radio conditions, MS switched off, fatal error, etc.).

Note

There is an optional feature where, after a number of missing SACCH frames, the BSC sets both MS and BTS power to maximum in an attempt to regain the Air Interface. If the BTS continues to register missing frames, the radio link fails as described herein. The BTS sends a connection_failure_indication message to the BSC with a cause value indicating that the radio link has failed. The BSC initiates Normal Call Release procedures to the BTS by sending an RF_channel_release message to the BTS and a clear_request message to the MSC. This is shown in Figure 42.

MS
Interruption of SACCH frames

BTS

BSC

MSC

start counter

NORMAL CALL RELEASE PROCEDURE continues refer to Figure 34

Figure 42

Call Release due to MS initiated Radio Link Failure

126 / 240

3BK 02974 AAAA TQZZA Ed. 07

4 Call Release

MS Initiated LAPDm Disconnection

If the MS has an error which unexpectedly terminates the call, it sends a disconnect message to the BTS. The system reaction to the disconnect message in this instance is the same as when the disconnect message from the MS is prompted by a channel_release message from the BSC (as explained in Section 4.3.2).

4.3.5

Remote TC Alarms
If the TC detects a break in communication with the BTS, it sets a timer. This timer is defined by GSM standards. On expiry of this timer, the TC sends an alarm to the BTS. If the BTS remote TC alarm detection is active, a connection_failure_indication message is sent to the BSC with a cause value indicating a remote TC alarm. If the BTS detects a break in communication with the TC, it sends a connection_failure_indication message to the BSC with a cause value indicating a remote TC alarm. See Figure 43. During an internal handover, this can cause remote TC alarms to arrive at the BSC, as the connection is still active but the call has been handed over. The BSC ignores these alarms for a guard period on new and old channels during handover.
MS BTS BSC MSC
TC detects a communication break and times out

NORMAL CALL RELEASE PROCEDURE continues refer to Figure 34

Figure 43

Call Release due to Communication Failure detected by TC

3BK 02974 AAAA TQZZA Ed. 07

127 / 240

4 Call Release

128 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

5 Service Improvement Features


This chapter provides an overview of the BSS Service Improvement Features. It describes how these features improve the quality of service between the MS and BSS, maximizes the BSS and MS resources, or increases operator efficiency. The service improvement features in the Alcatel BSS are classed as follows: G G Features defined in the GSM recommendations Alcatel BSS Features.

In addition, service improvement features which are new with the current BSS are described in a separate section.

3BK 02974 AAAA TQZZA Ed. 07

129 / 240

5 Service Improvement Features

5.1

Overview
The following environmental factors affect the quality of service between the MS and the BSS:
"

MS Power Drain Because the MS is in constant contact with several cells, even while in idle mode, power drain can occur. This happens when the MS moves or changes its condition. This continual contact between an MS and the BTS limits the autonomy of the MS. Power saving extends the limited life span of MS batteries.

"

Interference Interference occurs in a mobile cell configuration where other cells located nearby use the same frequency. Interference can also occur as a result of meteorological and atmospheric conditions.

Alcatel provides a variety of features to improve quality of service, to increase MS autonomy and to contribute to operator efficiency. These are described in the following pages There are two categories of Features in the Alcatel BSS:
" "

Features defined in the ITU and ETSI GSM recommendations Alcatel BSS Service Features.

Note

Some of these features may not be available on your system.

130 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

5.2

Features Defined in the GSM Recommendations


The following features, defined in the GSM recommendations, are supported in the current Alcatel BSS:
" " " " " " " " "

Cellular environment RPC uplink and downlink Frequency hopping Discontinuous transmission Discontinuous reception Phase 2 mobile support in a Phase 1 infrastructure Call re establishment by the MS Short Message Service Cell Broadcast Enhanced Full Rate.

5.2.1

Cellular Environment
The standard developed by the Groupe Speciale Mobile specifies a digital cellular network, as described in the System Introduction document. This includes the capacity to define different types of cell configurations to meet the requirements of geography and the strategies of the Network Operator. For details on cell environments offered in the Alcatel BSS, refer to Chapter 7.

5.2.2

RPC Uplink and Downlink


Radio Power Control ensures the dynamic balance between the quality of the link against interference with other cells. It contributes to power conservation. The balance is maintained by controlling the power output level to balance the reception power level and reception quality. Both directions of the radio link between the MS and the BTS are subject to continuous power adjustments. The power adjustment of the BTS and the MS are under the control of the BSC, see Subsection 3.3.1. RPC improves spectrum efficiency by limiting intra system interference. It also increases the autonomy of the MS by saving battery power. The reasons for changing the MS power level are:
" "

Uplink power level too high or too low Uplink link quality too low, or using power resources beyond quality requirements of the call.

3BK 02974 AAAA TQZZA Ed. 07

131 / 240

5 Service Improvement Features

Similarly, the reasons for changing the BTS power control are:
" "

Downlink power level too high or too low Downlink link quality too low, or using power resources beyond quality requirements of the call.

BTS Radio Power Control


The MS performs power measurements of radio signals being transmitted by the BTS. The MS, via the SACCH, regularly sends a measurement_report message to the BTS indicating the quality and strength of the downlink plus measurements of neighboring cells. This information is combined with uplink measurements taken by the BTS and sent to the BSC in the measurement_result message. The BSC then alters the BTS power, based on the measurement information it receives from the MS. The maximum power level is limited by the maximum power of the BTS, and also by the maximum power allowed in the cell.

MS Radio Power Control


The BTS measures the signal power transmitted by the MS. The resulting measurements are combined with the measurement_report message from the MS and are sent to the BSC in the measurement_result message. The BSC sends commands to change the power level of the MS as needed. The maximum power level is limited by the maximum power of the MS, and also by the maximum power allowed in the cell. Power control can be applied to TCHs and Stand Alone Dedicated Control Channels.

Radio Link Measurements


Due to interference and signal quality problems on the Air Interface, the uplink and the downlink transmissions are constantly measured to maintain maximum efficiency of the air waves. A balance is maintained between the transmission power, which can interfere with other cells using the same frequency, and the quality of the actual link.

132 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

Table 9 shows the measurements used to achieve this balance. Table 9


Measurement Signal strength

Radio Link Measurements


Description Signal strength is calculated on both active and inactive channels. On active channels, this measurement is used to provide the actual strength of the signal received from the transmitter. Inactive channel strength provides measurement of interference levels.

Signal quality

The signal quality of a channel is calculated on the average Bit Error Rate (BER) on a particular chan nel. BER is a standard quality calculation in radio transmission.

Absolute MS BS distance This is estimated by measuring the Time Of Arrival (TOA) of the received burst at the BTS for each allocated timeslot. The TOA is based on transmission distance and not the actual ground distance travelled. The calculation of one bit period (3.69s) corresponds to 550m.

Reporting Period

The statistical parameters of signal level and quality are obtained over a measurement period. This period is called the 'Reporting Period'. The reporting period for a TCH is 104 TDMA frames (480ms). The information is transmitted in the SACCH frames.

Power Control Decision and Handover


At every measurement interval, the BSC receives:
"

Pre processed power measurement information (uplink and downlink) Timing advance (distance information) Power level information about neighboring cells (only the best six are transmitted). Lowering the power level in the uplink or downlink, as this has little effect on the quality of the link Increasing the power on the uplink or downlink if the link quality/level is low Producing a handover alarm (refer to Section 3.3.2 for more information) Taking no action, if the quality/level balance is acceptable.

" "

The BSC uses this information to perform power control by:


"

"

"

"

3BK 02974 AAAA TQZZA Ed. 07

133 / 240

5 Service Improvement Features

Figure 44 illustrates the measurements described previously, as well as power control flow. Figure 45 shows how power control tries and maintains optimum quality and power levels.
MS BTS BSC

Measurement of downlink, BTS power and neighbor cells (by MS) measurement_report message

Measurement of uplink, MS BTS distance and MS power (by BTS) Collated and pre processed mea surement_result message Power Control Decision Handover Decision Change MS TX power MS BTS Change BTS TX power BSC

Figure 44

Power Control Flow of Measurement and Decision Action Note The signal and quality levels are converted into the ranges Received Signal Level (RXLEV) and Received Signal Quality (RXQUAL) respectively. Each range is classed from 0 63 (RXLEV where 63 is high) and 7 0 (RXQUAL where 7 is poor).

High Quality Signal level low Increase power output

R X Q U A L

Desired balance no change

Signal level too high Decrease power output

Quality bad Increase power output RXLEV

Signal level too high Quality bad Handover desired High Signal Level

Low Quality Low Signal Level

Figure 45

Power Output Balancing Based on Received Quality and Signal Levels

134 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

Change Power Levels


The BSC controls the power levels of the BTS and the MS. The BTS power level can be altered down from its maximum power. This is done in 2 dBm steps to a minimum of 30 dBm from the maximum level. The BSC informs the BTS of the new power level via a BS_power_control message. The MS power level can be altered in steps of 2 dBm. Table 10 shows the maximum and minimum power ranges of MSs. Table 10 MS Maximum and Minimum Power Ranges
Max Power 43 dBm (20W) 30 dBm (1W) 39 dBm (8W) 30 dBm (1W) Min Power 13 dBm 10 dBm 13 dBm 4 dBm

MS Phase GSM 900/1800 MS Phase1, GSM 900 MS Phase1, GSM 1800 MS Phase2, GSM 900 MS Phase2, GSM 1800

The maximum power setting of an MS is based on two factors, its classmark (its physical maximum power rating), and the maximum MS power setting for the cell. Each cell can limit the maximum power level for all MSs in the cell. For example, a 20 W MS can be limited to 5 W maximum power if that is the maximum MS power level allowed in the cell. However, a 1 W MS can never exceed 1W, and can therefore never reach the 5 W maximum allowed in the cell. The BSC informs the BTS of the new power levels via the BS_power_control message. The BTS in turn transmits a power_command to the MS over the SACCH. Changing power from one power level to another happens gradually. The power level changes by 2 dB every 60 milliseconds (ms), until the desired level is reached.

5.2.3

Frequency Hopping
FH changes the frequency of a TCH time slot from one TDMA frame to another. The change occurs across a group of frequencies known as the Frequency Hopping System (FHS). Each data burst is transmitted on a different frequency within the FHS, controlled by a hopping algorithm. The FH algorithm can be either random or cyclic. Associated (i.e. paired) uplink and downlink frequencies are always 45 MHz.

3BK 02974 AAAA TQZZA Ed. 07

135 / 240

5 Service Improvement Features

Frequency Hopping improves BSS MS performance by providing two types of diversity:


" "

Frequency diversity Interference diversity.

Frequency Diversity

Frequency Diversity averages the effects of signal fading by using several frequencies to improve transmission performance. Obstacles such as buildings produce fading by reflecting the signal out of phase with the main signal. Each frequency is affected differently by fading. After error correction information is added to the data, it is encoded so that the data is split into packets and the information is repeated. This creates redundant information which is transmitted in bursts on the Air Interface. With FH, each redundant information burst is transmitted on a different frequency. This enables the original data to be reconstructed from the received flow, even if errors occur due to fading. In this way FH improves transmission performance.

Interference Diversity

Interference Diversity spreads the co channel interference between several MSs. In high traffic areas, the capacity of a cellular system is limited by its own interference; that is, the interference caused by frequency re use. Interference Diversity minimizes the time during which a given user on a given MS will experience the effects of such interference.

Types of Frequency Hopping


There are two major types of frequency hopping:
" "

Baseband Frequency Hopping Synthesized Frequency Hopping.

Baseband Frequency Hopping

A Mobile Allocation (MA) is a set of all the frequencies available for frequency hopping. When the FH procedure is implemented a group of MSs is assigned to an MA. When a TCH is set up in a cell where FH is active, the TCH is assigned:
" "

A particular time slot An FHS. An FHS is defined as the subset of frequencies within the MA to be used by a given cell for FH. A Mobile Allocation Index Offset (MAIO). The MAIO indicates the initial hopping frequency of the TCH within the FHS. Use of the MAIO ensures that each TCH is assigned a different frequency during hopping.

"

136 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

"

A Hopping Sequence Number (HSN). The HSN supplies the identifying number of an algorithm which is used to calculate the next frequency in the FHS on which the TCH transmits. There can up to 63 different HSN algorithms, all of which are pseudo random. Within a given FHS, only one algorithm is used to avoid collisions. An HSN of zero means a cyclic use of the frequencies.

An example of FH is shown in Figure 46. Because the HSN = 0, hopping occurs in a sequential manner. With a non zero HSN, each of the 3 TCHs would hop in a random fashion determined by the algorithm corresponding to the HSN.
Within this FHS the HSN=0 Assignment for TCH 1: TS=1 TCH1 on TS1 MAIO=0 MAIO=0 HSN=0 TCH2 on TS2 MAIO=1

Frame n 1

Frame n+1 2

Frame n+2 3

Frame n+3 1

TCH3 on TS3 MAIO=2

= Frequency

Figure 46

Frequency Hopping within an FHS

Synthesized Frequency Hopping

Synthesized FH functions in a similar fashion to Baseband FH, but is performed at a different location. Instead of switching each time slot between TCHs, the channel assigned to a time slot is assigned to a fixed CU (or TRE). The CU/TRE changes frequency with each TDMA frame in accordance with the HSN algorithm selected, in the same manner as above. Thus, instead of the channel hopping from one fixed transceiver to another, the transceiver itself hops from one frequency to another, in both cases, according to the algorithm and parameters selected. Synthesized FH has the advantage of allowing an FHS to contain one more frequency than the number of CUs/TREs in the system.

3BK 02974 AAAA TQZZA Ed. 07

137 / 240

5 Service Improvement Features

This is particularly useful in some microcellular applications where only one transceiver is available for FH. Note Normally, in both FH schemes (Baseband and Synthesized), Time Slot 0 (TS0) is not available for FH. This is because it carries the BCCH, which must always be at maximum power and on a frequency known to MSs in Idle mode in the cell.

5.2.4

Discontinuous Transmission
Speech is transmitted over the air in the following ways:
" "

Continuous transmission of speech Discontinuous Transmission

Continuous Transmission

Sound is continuously encoded into digital information even when no one is talking. In normal conversation, only one participant at a time talks. This is used by the system to its advantage, by transmitting only when someone is speaking.

Discontinuous Transmission

Only actual speech is digitally encoded and transmitted. During the non speech phase (silent periods), noise/comfort mode information is sent once every 480 ms instead of once every 20 ms for speech. In this way the system:
" "

Improves spectral interference Increases power savings By transmitting at a reduced rate of 1 in 24 during the silent phases, the power autonomy of the MS improves.

DTX does not occur during half rate speech or data modes. DTX can be activated for either the uplink or the downlink or both. The receivers of DTX information can automatically detect that the transmitter is in DTX mode by the reception of Silence Indication (SID) messages. During quiet periods SID messages are sent instead of speech bursts. SIDs carry noise information about background noise. This information is used to:
" "

Let the receiver know that the link is still open. Provide comfort noise. Users of telephones prefer to hear background noise rather than silence; complete silence disturbs the listener.

138 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

"

Provide measurements of the link quality and timing advance. If there are no bursts of data over the Air Interface for a particular channel, no power level control and quality can be performed.

Voice Activity Detection


Voice Activity Detection (VAD) is used to detect when there is speech, silence or just background noise. The VAD device is located in the TC. Once the VAD detects speech, it starts transmitting speech bursts. After four bursts of detected silence, the VAD goes back into silent mode, and SID information frames are transmitted (i.e. the comfort noise generation is activated).

BSS DTX Towards MS


Downlink DTX is activated on a per call basis by combining information from the MSC and the OMC R. The MSC informs the BSC about its downlink DTX preference. It does this via the Downlink DTX flag in the assignment_request or handover_request messages on a per call basis. The OMC R can enable or disable the possibility of downlink DTX per cell via the DTX_DOWNLINK_ENABLE parameter. This is a static parameter which can be set via the Common Management Information Service Element (CMISE) command M_LOGICAL_PARAM_MODIFY. The overall system reaction is shown in Table 11. Table 11 Downlink DTX Status in Channel_activation
MSC Downlink_DTX flag (per call basis) Allowed Unavailable/not allowed Allowed Unavailable/not allowed Result DTX flag ON OFF OFF OFF

OMC R DTX_DOWNLINK_ENABLE (per cell basis) True True False False

The MSC requests no downlink DTX during MS to MS calls, where double clipping can occur if both ends perform DTX. This can have a staccato like effect on speech. The BTS tells the TC to perform DTX by setting the DTX bit in the speech frame.

3BK 02974 AAAA TQZZA Ed. 07

139 / 240

5 Service Improvement Features

In the BSS, the TC is responsible for DTX operation. In the BTS, the information is processed in the FU in the following way: 1. When the TC detects voice activity it informs the FU, using inband signaling. The speech signaling flag is set in the speech frame. 2. Every 20 ms the FU receives either speech frames or SID frames containing background noise characteristics. 3. At the end of the speech period (four bursts of detected silence) the FU sends a SID frame over the Air Interface. 4. During speech inactivity, the last received SID frame is sent at regular 480 ms intervals rather than at 20 ms. Otherwise dummy bursts are sent. These dummy bursts are:
D

Transmitted for TCHs on the Broadcast Control Channel (BCCH) frequency, due to the need for constant transmission on the BCCH frequency Not transmitted for TCHs on other frequencies.

Note

The BTS uses the measurement_result message to inform the BSC that DTX is operating. The BSC compensates for DTX when calculating power control and handover.

MS DTX Towards BSS


The OMC R operator controls whether an MS can perform DTX towards the BSS per cell. This information is sent in cell_options information (sys_info 3, and sys_info 6 on the Air Interface). Table 12 shows the available operator options. Table 12
Option Will perform DTX

Operator DTX Options


Description This forces the MS to use DTX. It reduces the call quality but also reduces interference in the cell and saves MS battery power. During silent phases only 1 in 24 bursts are sent, which greatly reduces inter ference. This allows the MS to choose either quality by not using uplink DTX, or power saving by using uplink DTX. The OMC R operator has decided, due to low interference, to have improved speech and mea surement control on the uplink side.

Can perform DTX

Cannot perform DTX

140 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

The TC detects that the MS is in DTX mode by the reception of SIDs. Note There is a small quality reduction due to the fact that VAD only starts sending speech when a user starts to talk. This can cut the start of each speech activity. Power control and handover are also affected, as the BTS has fewer incoming messages with which to calculate power and interference. Figure 47 shows the different forms of transmission.

Sound continuously encoded

DTX during 'Silence' in uplink

DTX during 'Silence' in downlink Key

DTX during 'Silence' in up and downlink

Continuous Transmission Discontinuous Transmission

Figure 47

Different Forms of Discontinuous Transmission

3BK 02974 AAAA TQZZA Ed. 07

141 / 240

5 Service Improvement Features

5.2.5

Discontinuous Reception
Discontinuous Reception provides power savings when the MS is in idle mode. Instead of the MS listening continually on the PCH sub channel CCCH for a paging message, it only listens to that part of the PCH which corresponds to its paging group. The PCH is split into a number of paging sub channels, each of which serves the MSs of a particular paging group. The MS calculates its paging group and the part of the PCH it has to monitor. It gets the information from its IMSI, and from the Control Channel description sent on the BCCH (sys_info 3). The paging information is transmitted at predefined regular intervals. The MS only turns on its receiver to listen to its paging group and then turns itself off again. This occurs cyclically, between 0.95 seconds and 4.25 seconds, depending on the configuration of the cell. Apart from listening to the PCH, the MS monitors the home cell's BCCH up to once every 30 seconds, and the top six neighbor cells up to once every five minutes. For more information about Paging, refer to Section 2.4.

5.2.6

Phase 2 Mobile Support in a Phase 1 Infrastructure


The Alcatel 900/1800 BSS supports the use of Phase 2 MSs in a phase 1 infrastructure network. It conforms to the updated Phase 1 infrastructure as defined in the GSM recommendations. The BSS functions as Phase 2 on the Air Interface and has the capability of functioning as Phase 1 or Phase 2, depending on the MSC capabilities. The infrastructure (BSS and MSC) remains Phase 1. The problems of using Phase 2 MSs on a Phase 1 network are:
"

The implementation rules for Phase 1 are not strictly defined. Therefore some implementations cannot function with Phase 2 mobiles. For example, some of the spare bits in Phase 1 are now used by the Phase 2 protocol. However, some Phase 1 infrastructures reject the message as spare bits are used.

"

Some protocol changes in Phase 2 changed/replaced a Phase 1 protocol. For example, power and quality measurements sent by Phase 2 MSs have a finer range of power control, which Phase 1 infrastructure must process.

142 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

"

Phase 2 MSs send some Phase 2 messages even though they are in a Phase 1 environment. For example, Phase 2 MSs send either new messages or new elements in messages, which the Phase 1 infrastructure could reject. This blacklists the MS due to an invalid protocol message for Phase 1. Depending on what these messages are, the updates to the Phase 1 infrastructure would accept these message/elements. The messages can be either ignored or only partly treated. This is based on information contained within the messages or elements.

5.2.7

Call Re establishment by the MS


The Call Re establishment procedure allows an MS to resume a connection in progress after a lower layer failure, possibly in a new cell. The MS initiates the procedure when there is already a speech or data call in a stable state (TCH path connected) and the MS detects a radio link failure. The MS waits a predetermined time for a response from the network. If there is no response the MS performs a cell reselection procedure. If the new cell allows the re establishment procedure to be performed, the MS initiates the channel request procedure (RACH) and awaits the immediate_assignment message. The MS then performs the contention resolution procedure using the cm re establishment request message. The radio and link establishment procedure continues as described in Section 2.2. The network may not allow the MS to perform the channel request procedure, due to inhibition of the MS access class broadcast in the sys_info 1 to 4 messages. If this is the case the MS radio resource entity reports the failure of the radio and link establishment procedure to the higher layer entities in the MS. When the MSC receives the cm re establishment request message it initiates the procedures necessary to establish a new radio resource connection and continue the call management connection.

3BK 02974 AAAA TQZZA Ed. 07

143 / 240

5 Service Improvement Features

5.2.8

Short Message Service

Cell Broadcast

There are two types of SMS. The point to point SMS allows a short message to be sent to, or received from, an MS. The SMS CB allows messages to be broadcast to the MSs. This service can be used for a number of reasons, e.g. to transmit taxation information, road traffic information, etc. An SMS CB message can be transmitted to all the cells connected to the BSC, or to selected cells only, as required.
HMI Broadcast Message to Selected Cell(s) Broadcast Message set up by Operator SMS CB commands and signaling

MS Message broadcast to all MSs MS BTS

BSC

OMC R

Transmission Request

Figure 48

Short Message Service Cell Broadcast The operator inputs the cell broadcast message at the OMC R via the HMI identifying the broadcast text and the selected cell identities. Only one broadcast message per cell or cells is allowed. Any subsequent message simply replaces the message being broadcast. The message is sent from the OMC R to the BSCs handling the selected cells. The BSC then sends the message to the individual BTSs of the selected cells. On receipt of the transmission request message from the BSC the BTS broadcasts the message to the MSs in the cell over the Cell Broadcast Channel of the Air Interface.

5.2.9

Enhanced Full Rate


The EFR feature provides advanced encoding of speech on a Full Rate TCH, for improved voice quality and user comfort. EFR uses a codec with ACELP coding.

144 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

EFR Process

EFR is enabled in the BSC, on a cell by cell basis, by the O&M parameter EFR_ENABLED. When an EFR call is set up, the following processes occur:
"

The MS makes a call requiring speech, in which it announces its codec preferences to the MSC in the setup message. The MSC passes appropriate assignment_request and handover_request messages to the BSC. The BSC uses the codec list supplied by the MSC to choose the correct codec, based on the support for the codec in the BTS and A Interface Transcoder Rate Adapter (TRAU) equipment. The BSC activates the selected channel in the BTS, giving the indication of codec type. The BTS configures itself to handle the correct channel coding, and starts sending TRAU frames to the TRAU, in order to configure the TRAU. The BSC builds either an assignment_command message or a handover_command message, indicating to the MS which codec it should use when accessing the new channel. Once the MS is attached, the BSC reports the selected codec type to the MSC. In the case of subsequent handover if the BSC has had to change the codec the BSC informs the MSC of the change.

"

"

"

"

"

"

"

For further information concerning Enhanced Full Rate, refer to G2 Transcoder Functional Description and OMC R Configuration Management Services.

3BK 02974 AAAA TQZZA Ed. 07

145 / 240

5 Service Improvement Features

5.3

Alcatel BSS Features


This section provides an outline of features provided in the Alcatel BSS. These features are designed to:
" " "

Improve the quality of service between the MS and BSS Maximize resources Increase operator efficiency. Types of cell environments Antenna diversity Multiple HMI access to OMC Rs Night time concentration Secured X.25 connection from BSC to OMC R Usage state on demand BSC alerter.

Alcatel BSS Features include:


" " " " " " "

5.3.1

Types of Cell Environments


Several types of cell environments are available in the Alcatel BSS. This availability means that cells can be configured to meet the requirements of geography and the strategies of the Network Operator. A specific application of cell environments is the Extended Cell feature. It uses two synchronized, co located G2 BTSs to create a cell environment for rural areas covering up to 70 km. Refer to Chapter 7 for more information concerning Extended Cell and other Cell Environments.

146 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

5.3.2

Antenna Diversity
Antenna diversity provides protection against multipath fading. It is used to improve the performance of the radio path on the uplink in large cell configurations.

G1 and G2 BTSs

Antenna diversity on G1 and G2 BTSs duplicates the receive antenna and receive path up to the FU. The FU uses the data burst which has the fewest errors. This increases low power MS range, thus allowing larger cells and lowering infrastructure investment. Figure 49 shows the antenna diversity path through the G1 and G2 BTS.

TRANSMISSION OTHER ANTENNAS

B I E

FU

F H U a a

CU a

C O U P L I N G U N I T

Tx

RX

ab

best of a&b b b

RX (option)

OMU CONTROL BASEBAND CONTROL BASEBAND RADIO COUPLING

Figure 49

Antenna Diversity on G1 and G2 BTSs

3BK 02974 AAAA TQZZA Ed. 07

147 / 240

5 Service Improvement Features

BTS A9100

Antenna diversity on the BTS A9100 follows the same principle as in the G1 and G2 BTSs. The antennas are used for both transmit and receive, and the receive path is duplicated up to the TRE, providing the same gain in efficiency and low power MS range. Figure 50 shows the antenna diversity path through the BTS A9100.

TRANSMISSION

TRE 1
ab best of a&b a b a ANT a Tx / Rx a b

TRE 2
B I E S U M ab best of a&b a b

ab ab

ab

best of a&b

TRE 3
b a

TRE 4
ab best of a&b b a ANy RADIO COMBINING

b a ANx RADIO

b ANT b Tx / Rx

CONTROL

BASEBAND CONTROL

BASEBAND

DUPLEXING

Figure 50

Antenna Diversity on the BTS A9100 (1 Sector, 3X4 Transceiver Configuration) Note The configuration shown above is one example only. Other combinations of Antennas and TREs are possible. The ANy is not needed if the sector has two TREs.

148 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

5.3.3

Multiple Human Machine Interface


The HMI feature allows an operator located centrally, who is using a multiple access workstation, to perform network management actions. These actions are usually performed by different OMC Rs. The feature is mainly intended to provide off duty hours access to the network. The connection between the multiple access workstation and the other OMC R hosts is made via an X.25 network. Figure 51 illustrates the principle of operation.

Central Site Additional Workstation HMI Server Printer

Multiple Access Workstation

X.25 Network

OMC R Host 1 OMC R Host 2

OMC R Host n

Figure 51

Multiple HMI Access to OMC Rs

The implementation of this feature takes advantage of the distributed configuration of the OMC R which usually consists of a host machine and distinct local or remote HMI servers.

3BK 02974 AAAA TQZZA Ed. 07

149 / 240

5 Service Improvement Features

Central Site Configuration

The site used for multiple access contains the following:


" "

Printing facilities Additional workstations which connect to the multiple access workstation, but only connect to the same OMC R Configuration of each OMC R is specific to the multiple access workstation and its peripherals.

"

Switching Operation

The switching operation corresponds to the restart of the workstation inside a different OMC R environment. Beginning at the UNIX level the operator activates a script which performs the following:
"

Selection of an OMC R host from a configuration file describing the accessible OMC Rs and their addresses Restart of communication software Network information service and network file system re initialization HMI server application startup, which includes the data distribution for access control, help and Graphical Network Display.

" "

"

150 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

5.3.4

Night Time Concentration


The NTC feature appears as a process within the HMI server. The feature allows an operator to perform alarm management operations for a complete network, where the network consists of more than one OMC R. The primary use of the NTC feature is during off duty hours, when the supervision of a large network must be performed from a single location. The feature can be started and stopped from any OMC R or any operator having access to the feature. To retrieve alarms from the complete network, the OMC R from where the NTC feature was activated must be connected to all the other OMC Rs in the network. These links are used to transfer alarm notifications from the controlled OMC Rs to the NTC OMC R. Figure 52 illustrates the NTC feature.
NTC OMC R Workstation

OMC R 3

OMC R 1

Area 3

Area 1

OMC R 2

Area 2

Figure 52

Night Time Concentration

3BK 02974 AAAA TQZZA Ed. 07

151 / 240

5 Service Improvement Features

The functions provided by this feature are:


"

Configuring the NTC feature Provides a name and address list of the OMC Rs being supervised from a central location.

"

Starting the NTC feature Operators having authorized access to the NTC feature can perform this function. Upon start up, an alarm window is displayed. It shows the list of alarm notifications, including alarms originated in the local OMC R and all the controlled OMC Rs.

"

Displaying the OMC R Status During an NTC session the operator can open a window showing the access status of the OMC R, which is part of the NTC configuration.

"

Printing Alarm Reports The operator can print a report containing all incoming alarms from the selected OMC R, or print an alarm and all the preceding alarms immediately. In each case the number of alarms collected for printing is displayed.

"

Stopping the NTC feature This function allows the operator to stop the NTC. It stops the sending of notifications.

152 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

5.3.5

Secured X.25 Connection From BSC to OMC R


The configuration for the X.25 links consisted of two physical links, one for Common Management Information Service Elements (CMISE), and one for File Transfer Access and Management (FTAM). Figure 53 illustrates the configuration without redundancy.

OMC R CMISE BSC A

X.25 Network
HSI 0 BOARD 1 2 3 CMISE

BSC A OSI CPRA 1

FTAM BSC A

FTAM

OSI CPRA 2

HSI = High Speed Interface CPRA = Central Processor Type A

Figure 53

X.25 Without Redundancy Link failures can occur on either the OMC R or BSC side. The Secured X.25 Connection feature provides redundant links in the event of a link failure. When a link failure occurs, the initiator system involved must process the change over. Definition of the primary and the secondary links based on their hardware configuration can achieve various types of redundancy, such as:
" " "

OMC R side redundancy BSC side redundancy Complete redundancy.

3BK 02974 AAAA TQZZA Ed. 07

153 / 240

5 Service Improvement Features

Figure 54 illustrates these redundancy types.


OMC R HSI 0 Board 1 2 3 3 X.25 Network

Primary Link 1 2

BSC OSI CPRA 1

OSI CPRA 2 Secondary Link

Secondary Link Configurations 1. OMC R side redundancy 2. BSC side redundancy 3. Complete redundancy

Figure 54

X.25 With Redundancy When the OMC R or the BSC sets up a CMISE or FTAM association, the subsystem chooses the active link. The active link is the primary link if it is in traffic, otherwise it is the secondary link. The following events occur:
"

X.25 Link Transfer Scenario

The transfer is performed on the primary link if the association is successful. The association is attempted three times. The primary link is set out of service if the association is unsuccessful after the third try. If the secondary link is in traffic, it becomes the active link and the association is tried on this link.

"

"

If the secondary link is out of service, the application is impossible. Links are periodically tested for availability. When the primary link is recovered it becomes active and in traffic. Loss of one link (i.e. primary or secondary) triggers an alarm and the recovery triggers the end of alarm.

154 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

5.3.6

Usage State on Demand


The Usage State on Demand feature allows an OMC R operator to have a snapshot of the current resource usage at a BSC. This is displayed on the OMC R terminal. Two levels of information are available:
" "

Overall BSS information Specific cell or DTC information.

Overall Request

An overall request allows the operator to monitor the total resource usage of a BSC. The information displayed, which is refreshed every 1 to 3 minutes, is:
" " " " " " "

Identification of each cell and DTC State of each cell and DTC Ratio of busy/available TCH Ratio of busy/available SDCCH Number of SCCP connections Number of available SCCP connections Ratio of busy/available A channels.

Cell or DTC Request

A cell or DTC request displays a snapshot of resource usage for up to five cells or DTCs. The operator selects the required cells or DTCs from a list of those available. The information collected for each of the selected cells is:
" " " " " " " " " " " " "

Cell state Barred status and access classes Number of TRXs defined Number of TRXs available Terminal Endpoint Identifier (TEI) Number of Carrier Units (CUs) configured Number of CUs available Number of SDCCHs available Number of SDCCHs busy Number of TCHs available Number of TCHs busy Number of free TCHs/interference board TRX time slot state (8 x 8)

3BK 02974 AAAA TQZZA Ed. 07

155 / 240

5 Service Improvement Features

The information collected for each of the selected DTCs is:


" " " " " " " " " " "

DTC identification A trunk Security Block (SBL) state Number of Circuit Identification Codes (CICs) available Number of CICs busy No. 7 signaling Link SBL number No. 7 signaling Link SBL state Number of busy SCCP connections over No. 7 signaling Link BSSAP handled Number of SCCP connections available Number of SCCP connections busy State of A Interface pulse code modulation time slots (0 31)

5.3.7

BSC Alerter
The BSC Alerter is a telecom supervision function which generates an alarm event when the system suspects abnormal behavior of a resource. This is system defined and not dependent on site configuration or traffic conditions in a particular cell. Alerters are a background function in the BSC, passively collecting data, and do not interfere with any Telecom activity. An Alerter, activated in a BSC, functions by monitoring and computing the levels of specific Performance Management counters. If, during the Alerter observation period, the count exceeds the operator defined parameters, the Alerter generates an alarm for the BSC resource. This alarm is sent to the OMC R operator. There is a one to one relationship between an Alerter and the alarm generated by it, and only a single alarm is generated when the conditions have been triggered. Alerter counters are maintained regardless of whether an Alerter is activated or not. It is only when an Alerter is activated, that its counters are used to determine whether an alarm should be generated. The OMC R operator has control of the Alerters, being able to not only activate or deactivate them on a BSC basis, but also set the parameter levels which determine when the Alerter generates an alarm. Other parameters (such as re arming delay, and observation period) may be modified for each Alerter. A single formula is used for a specific Alerter type wherever it is activated. The formulae are system defined and are not operator modifiable. Depending on its type, an Alerter may be activated with different parameters on a per cell or BSS basis, giving flexibility of control to the operator. The four types of Alerter are shown in Table 13.

156 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

Table 13
Alerter Type Alerter 1 Alerter 2 Alerter 3 Alerter 4

BSC Alerter Types


Description Abnormally low traffic on SDCCH compared to other BSS cells Inconsistency in terrestrial channel states (A Interface) TCH Average occupancy time too long TCH Average occupancy time too short

Note

For performance reasons, each alerter type has a maximum limit of 16 alarms. For further information concerning BSC Alerters, refer to OMC R Performance Management Services and the Operator Handbook.

3BK 02974 AAAA TQZZA Ed. 07

157 / 240

5 Service Improvement Features

5.4

New Service Improvement Features


Alcatel has introduced the following new service improvement features with the current BSS:
" " " " " " " " "

Power control due to radio link failure Q3 Multimanager OMC R connection to TSC through BSC Abis signaling links static multiplexing Transcoder pools Automatic power down Auto Identification Automatic paging repetition Access to PM raw counters via binary files.

5.4.1

Power Control due to Radio Link Failure


This feature provides an automatic attempt to recover the Air Interface after an interruption of the SACCH. For more information, see Section 4.3.4.

5.4.2

Q3 Multimanager
The Q3 Multimanager feature permits the OMC R to communicate over the Q3 Interface with multiple NMCs. Refer to Section 1.6.2 for more information.

5.4.3

OMC R Connection to TSC through BSC


When re configuring a system, PLMN operators naturally want to minimize on site intervention time and costs. This feature saves time when reconfiguring the Abis Interface. The OMC R can configure certain TSC supervision devices directly, using the existing OMC R - BSC X.25 link. Communication is passed transparently through the BSC to the TSC, regardless of where in the system the TSC is physically positioned. This permits a new Abis transmission scheme to be set up before on site modifications are made, with corresponding time gain. Testing can be carried out immediately after the on site operation.

158 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

5.4.4

Abis Signaling Links Static Multiplexing


This feature is available on the G2 BTS and with Evolium BSSs. It permits a maximum of 12 TRXs connected to the same link, increased from 9. The RSL of a TRX supports two signaling rates:
" "

64 kbit/s 16 kbit/s.

With this feature, a TRX operating in Full Rate mode can multiplex up to four RSL channels belonging to TRXs of the same BTS onto one 64 kbit/s time slot. This has the advantage of reducing the number of time slots used by a single BTS on the Abis Interface. This feature is required for certain configurations on the BTS A9100. See your Alcatel representative for more information.

5.4.5

Transcoder Pools
This feature permits the grouping of Transcoders having the same capacities, into pools on the A Interface. This permits efficient use of existing infrastructure, without having to replace or redeploy older TCs when a new feature (such as Enhanced Full Rate) is added. Combined with the Abis Signaling Links Static Multiplexing feature, TRAUs can be grouped according to their data rate and encoding algorithm capacities. Two types of Transcoder pooling are available in the Alcatel BSS:
"

Fixed Transcoder pools follow phase 2 GSM recommendations. This involves TRAUs which have fixed submultiplexing schemes on the Ater Interface. There are four Transcoder types supported in this scheme. Complex Transcoder pools are an Alcatel enhancement. They allow an Alcatel MSC to have detailed knowledge of the Ater transmission schemes used by an Alcatel BSC. This permits the MSC to map the circuits for an A Interface trunk dynamically, according to traffic demand.

"

Transcoder pooling is enabled by a BSC parameter, EN_TC_POOL. Fixed or Complex pooling is set by the O&M flag, EN_COMPLEX_TRAU.

3BK 02974 AAAA TQZZA Ed. 07

159 / 240

5 Service Improvement Features

5.4.6

Automatic Power Down


This feature is available only on the BTS A9100. It is used typically in an outdoor installation where the BTS has a back up battery power supply. In case of main power supply failure, the BTS A9100 is automatically switched to battery power (until the main power is restored or the battery is drained, whichever happens first). To extend the time during which the BTS A9100 can function under battery power, the BTS is reduced to a minimum configuration to reduce power consumption.

Power Down Alarm Processing

Once a power supply failure alarm arrives, the OMU starts a timer. If, once the timer expires, the alarm is still active, the OMU switches off all TREs except the BCCH TRE (one per sector for a sectored site), by placing the TREs to be powered down in FOS state. If, in a given sector of a sectored site, the BCCH TRE is configured without a TCH, another TRE (which carries the SDCCH) is kept powered on, so that calls are still possible in this sector, though limited to one TRE. When the power supply failure alarm disappears, the OMU starts a timer. If the alarm re occurs before the timer expires, the OMU takes no further action. This is to guard against a possible unstable restoration of power. If the BTS power supply remains stable until the timer expires, the OMU performs an autonomous auto reset with BTS activation. This re initializes all available TREs. For more information on this feature, refer to the BTS A9100 Functional Description and the BTS A9100 Hardware Description documents.

5.4.7

Auto Identification
Auto Identification gives the BTS A9100 the capacity to recognize its own hardware configuration, and to provide this information to the OMU and the BTS Terminal. The auto identification procedure is triggered by the OMU in the following situations:
" " "

BTS/Station Unit Module (SUM) power up BTS reset OMU reset/auto reset

160 / 240

3BK 02974 AAAA TQZZA Ed. 07

5 Service Improvement Features

"

Module initialization (on maintenance operator command, or during a Local Recovery Action or Hardware Extension, the auto identification takes place only for the module(s) concerned by the operation).

The BTS A9100 capabilities received by the OMU at auto identification are stored and can be used internally by the OMU software or sent to the BSC at Hardware audit. Auto identification has two components:
" "

Remote Inventory RF Cable Identification. RIT type of each managed module Hardware capabilities of each RIT. Location of each RIT (subrack and slot) Sector to Antenna Network (AN)x mapping TRE to ANx mapping.

Remote Inventory

Remote inventory identifies the following:


" "

RF Cable Identification

RF Cable Identification provides the following information:


" " "

For more information, refer to the BTS A9100 Terminal User Guide document

Consistency Checks

When a new Configuration Data Message (CDM) is received from the BSC, the BTS A9100 performs a consistency check of its capabilities against the CDM. It also does this at module initialization due to maintenance operator command or to a Hardware Extension operation. The BTS A9100 also checks that the received OMU Configuration Parameter Data File (CPF) is valid for this generation of BTS. For more information, refer to BTS A9100 Functional Description, BTS A9100 Hardware Description, and BTS A9100 Terminal User Guide.

5.4.8

Automatic Paging Repetition


If an idle MS performs a cell re selection at the same time that it is paged, or if a paging message is lost on the Air Interface, the MS may not receive a paging message. Automatic Paging Repetition ensures that paging messages are not lost by automatically repeating an unanswered page on the PCH. For more information about paging, refer to Chapter 2.

3BK 02974 AAAA TQZZA Ed. 07

161 / 240

5 Service Improvement Features

5.4.9

Access to PM Raw Counters via Binary Files


This feature provides an export facility for PM raw counters. Two files stored in the OMC R are exported using FTP or RPC protocols to an external PM processing system. The external system can then read them directly, and process their data. The two files are:
"

A configuration file from which the topology of the BSS can be read A binary format file to retrieve the PM raw counters.

"

162 / 240

3BK 02974 AAAA TQZZA Ed. 07

6 Handling User Traffic Across the BSS

6 Handling User Traffic Across the BSS


This chapter describes the flow of speech and data traffic across the BSS. It describes: G G G G How speech is encoded and rate adapted throughout the BSS What types of data can be transferred across the BSS Where data error correction is performed How the data rate is adapted.

3BK 02974 AAAA TQZZA Ed. 07

163 / 240

6 Handling User Traffic Across the BSS

6.1

Overview
The BSS performs traffic handling in the uplink and downlink directions for speech and data. The BSS uses the BSC and BTS to perform the required radio transmission, control and baseband functions of a cell and to control the BTSs in its domain. The TSS provides the efficient use of the terrestrial links between the BSS components. Together these components perform the required encoding and rate adaptation procedures.

164 / 240

3BK 02974 AAAA TQZZA Ed. 07

6 Handling User Traffic Across the BSS

6.2

Speech
Speech is passed from the MS to the Public Switched Telephone Network (PSTN) and from the PSTN to the MS. This section describes how speech is encoded from the MS to the PSTN. Speech in the opposite direction follows the reverse process and so is not described.
Full Rate Speech TCH

A 13 kbit/s

CIM

13 kbit/s

64 kbit/s

A/D

BTS

BIE

BIE

BSC

SM

SM

TC

MSC

PSTN

MS A 6.5 kbit/s CIM 6.5 kbit/s 13 kbit/s 64 kbit/s A/D

Half Rate Speech TCH A Analog CIM Channel Encoded, Interleaved, and Modulated A/D Analog/Digital

Figure 55

Encoded Speech Transmission Across the BSS

Analog

The microphone converts speech to an analog signal. The analog signal is encoded into a 13 kbit/s (6.5 kbit/s for Half Rate) digital signal, then transmitted on a 16 kbit/s (8 kbit/s) radio timeslot. 3 kbit/s (1.5 kbit/s) are used for signalling. To pass speech over the Air interface, error checking and redundancy are included to make sure speech information is correctly transmitted. This ensures that valid continuous speech is passed through the BSS. Error correction is based on high redundancy with complicated parity and cyclic redundancy methods. This is done to ensure that many types of parasitic and sporadic errors are detected and to some degree, corrected. In the case of speech, there is cyclic coding, convolutional and parity error encoding of the data. The speech data starts as 260 bits (112 bits) and, after forward error checking, is encoded as a 456 bit block (228 bit block).

Interleaving and Forward Error Correction

3BK 02974 AAAA TQZZA Ed. 07

165 / 240

6 Handling User Traffic Across the BSS

These blocks are then split into eight (four for Half Rate), and interleaved with adjacent blocks into TDMA frames to be transmitted as radio wave bursts. This means that if some of the blocks are lost during transmission, there is a high chance that the other blocks hold enough redundancy to still have a valid speech block.

Speech Data Bursts

The interleaved blocks are transmitted over the Air interface and are then reassembled in the BTS. As described above, when the interleaved blocks are reassembled and checked for parity errors, there is a high chance that the data can be recovered. In speech data the most significant bits are heavily protected and are always transmitted at the start of a TDMA frame. This ensures that even if the speech block cannot be reassembled, at least the most significant speech data can be used to provide a close approximation. Speech bursts are returned to digital speech blocks in the BTS. They are sent to the TC as 13 kbit/s digital speech, plus 3 kbit/s for in band signalling if they are full rate speech. The channels on the Abis and Ater interfaces are 64 kbit/s. The speech blocks to be multiplexed on to these links. This is shown in Figure 56. Half rate speech is sent to the BSC on the Abis interface as 6.5 kbit/s, plus 1.5 kbit/s signalling. Two half rate 8 kbit/s channels are associated together into a 16 kbit/s channel. On the Ater interface a 16 kbit/s submultplexing scheme is used for all types of traffic. The two mated 8 kbit/s Abis channels are independently switched by the BSC onto two 16 kbit/s Ater channels.

Digital Speech

Ater Interface

Ater mux Interface

Ater Interface

A Interface

BSC

SM

SM

TC

MSC

30 x 16 kbit/s user traffic channels per link

90 x 16 kbit/s user traffic channels per link

30 x 16 kbit/s user traffic channels per link

30 x 64 kbit/s user traffic channels per link

Figure 56

Multiplexed Ater Interface

166 / 240

3BK 02974 AAAA TQZZA Ed. 07

6 Handling User Traffic Across the BSS

Digital 64 kbit/s A law Encoded Speech

The TC converts the 13 kbit/s digital speech to the 64 kbit/s A law encoding. This is a standard digital speech interface for Integrated Services Digital Network (ISDN) and PSTN exchanges. The information passes through the MSC and is sent to the PSTN. The TC performs rate adaptation in both directions.

3BK 02974 AAAA TQZZA Ed. 07

167 / 240

6 Handling User Traffic Across the BSS

6.3

Data
There are two types of data modes:
" "

Transparent Non Transparent.

Transparent

The transparent data mode is based on the V.110 protocol. V.110 is an ITU recommendation. It specifies how ISDN supports Data Terminal Equipment (DTE). It also specifies the transport of synchronous/asynchronous data over a synchronous link. Data is packaged and sent to the TC in the same way as speech. It is converted to the 64 kbit/s ISDN format for data transmission. Error handling is dealt with by the Air interface.

Non Transparent

The non transparent data mode is similar, although data is transmitted as packets from the modem on the MS to the modem in PSTN. Error handling is handled end to end. Refer to Subsection 6.3.1 for more information about the transparent mode and to Subsection 6.3.2 for more information about the non transparent mode. Figure 57 illustrates data transmission across the BSS.

BTS MS

BIE

BIE

BSC

SM

SM

TC

MSC

PSTN

V.110 data blocks A 13 kbit/s CIM 13 kbit/s 64 kbit/s

ISDN /Analog A/D

A Analog CIM Channel Encoded, Interleaved, and Modulated A/D Analog/Digital

Figure 57

Data Transmission Across the BSS

168 / 240

3BK 02974 AAAA TQZZA Ed. 07

6 Handling User Traffic Across the BSS

6.3.1

Transparent Mode
Transparent mode implies that the following functions are performed by the BSS:
" "

Interleaving and Channel Coding Rate adaptation.

Interleaving and Channel Coding

Interleaving for data is more complicated than for speech. The data block is split into 22 parts for interleaving 9.6 kbit/s and 4.8 kbit/s data rates. For 2.4 kbit/s, the interleaving is the same as speech. The lower the data rate, the more space can be used for redundancy and error detection. This lowers the error rate. The Air interface performs the error handling. The V.110 data packets are grouped together and transmitted across the Air interface exactly like speech. Table 14 shows the data rate and error rate. A low data rate provides more space for a better forward error correction scheme, in turn reducing the number of errors.

Rate adaptation

Data is packaged differently in V.110 for different data rates. The bandwidth is reduced and therefore the rate is lower. See Table 14 for the rate conversions. The TC plays the final role in the rate adaptation when the data stream is adapted to 64 kbit/s packets. There is a difference between data and speech rate adaptation. Speech is encoded to A law, while data is transposed to the first bit, and if required the second bit of a Pulse Code Modulation (PCM) byte. PCM transmission is at 8 000 bytes (64 kbit/s). The 8 kbit/s and 16 kbit/s intermediate rates (before the TC) are transposed as 1 or 2 bits per byte respectively. Table 14
User Rate 9600 4800 <=2400

Data Rate Conversions Across the Air Interface


Intermediate Rate 16 kbit/s 8 kbit/s 8 kbit/s Radio Interface 12 kbit/s 6 kbit/s 3.6 kbit/s Error Rate (at Full Rate) 0.3% 0.01% 0.001%

3BK 02974 AAAA TQZZA Ed. 07

169 / 240

6 Handling User Traffic Across the BSS

6.3.2

Non Transparent Mode


The Non Transparent data mode is a data transmission protocol. It is based on sending RLP packets as four V.110 frames. This is the same process used in transparent mode. Interleaving and channel coding are still used, as they are in the Transparent mode. The RLP adds extra protection and also allows the re transmission. Packing RLPs in four V.110 frames ensures transparency over the network. RLP packet size is the same as a radio block size, so it is transmitted as one radio block. The Non Transparent data mode uses a 12 kbit/s radio interface rate. Interleaving and channel coding are at 9.6 kbit/s (same as in the Transparent mode). The only difference between Transparent and Non Transparent modes for the BSS is the processing of the four V.110 frames of an RLP packet.

Error Handling

The Non Transparent data mode has a better error rate as there is no forward error checking or interleaving. Therefore, the size of packets remains small and less prone to errors. There are however, some cyclic redundancy bytes and the protocol is very similar in principle to Link Access Procedure on the D Channel (LAPD). There is no rate adaptation in Non Transparent mode. The rate can only be adapted by physically transmitting less than the full bandwidth available. The data rate is also limited by the number of errors, as packets have to be retransmitted. The difference between Transparent and Non Transparent mode data links is transparent to the TC, but not to the BTS. The TC, as described in Transparent mode, puts the data in the first bits of a PCM byte. The BTS must ensure that an RLP packet maps into four V.110 frames numbered 0, 1, 2, 3. These must be sent in one block on the Air interface.

Rate Adaptation

170 / 240

3BK 02974 AAAA TQZZA Ed. 07

7 Cell Environments

7 Cell Environments
This chapter describes the cell environments available in the Alcatel 900/1800 BSS. The following cell environments are described: G G G G G G G Single Cell Concentric Cell Sectored Site Extended Cell Umbrella Cell Mini Cell Microcell.

3BK 02974 AAAA TQZZA Ed. 07

171 / 240

7 Cell Environments

7.1

Overview
The Alcatel BSS provides coverage suited to the needs of urban, rural and coastal areas by offering a variety of possible cell environments.

Rural and Coastal Coverage

In the rural and coastal environment coverage is principally a function of cell planning. Standard cell layouts, providing coverage of up to 35 km, include:
" "

Single cells Concentric cells.

Extended cells, which have two co located antennae, provide options covering traffic density and ranges up to 70 km.

Urban Coverage

In the urban environment the coverage is determined by the location of the BTS antennae. Two types of cells are normally used:
"

Macrocells where the antenna is located above the roof tops and propagation occurs in all directions. These cells can be sectored by using specific antenna patterns. Microcells where the antenna is located below roof top level, on building facades or street lights. Propagation occurs mainly as line of sight along the street, with strong attenuation at street corners.

"

These two cell types can be used in a hierarchical cell environment where continuous coverage is provided by the macrocell (umbrella cell) and locations of increased traffic density are covered by dedicated microcells. Figure 58 shows various configurations of the normal GSM 900 or GSM 1800 cell type. Each of the following sections explain the functional differences between the cell described and the single cell configuration.

172 / 240

3BK 02974 AAAA TQZZA Ed. 07

7 Cell Environments

Inner Zone Outer Zone Single Cell Concentric Cell

Sectored Site Umbrella Cell Microcell Microcell Microcell Inner Cell Outer Limit Microcell Microcell Umbrella & Concentric Cell

Microcell

Extended Cell

Inner Cell Outer Cell

Overlap Zone

Outer Cell Inner Limit

Figure 58

Example: Cell Configurations

3BK 02974 AAAA TQZZA Ed. 07

173 / 240

7 Cell Environments

7.2

Concentric Cell
The goal of concentric cells is to increase the frequency economy of the network. This is done by reducing the interference levels of some BTS carriers. These carrier frequencies can be re used for smaller distances. The inner zone serves a high concentration of MS calls in a small area, with a reduced maximum power output limit. The outer zone performs call handling for a greater radius with a normal maximum power output limit. A non concentric cell has all the frequencies serving all of the 35km radius area. This causes interference problems due to the large number of frequencies being used. The BCCH, CCCH and SDCCH in concentric cells are put on the outer zone frequencies. TCH assignment during call connection can be allocated to either the outer or inner zones. It depends on the location of the MS at that time. The inner and outer zones are part of the same cell, and a frequency carrier is assigned either to the inner or outer zone. This is signalled by the ZONE_TYPE flag of 1 or 0, (1=inner, 0=outer). The outer zone maximum power limit is the same as normal zones. The inner zone is controlled by two maximum power limit values. One maximum power limit value for the MS and one maximum power limit value for the BTS.

174 / 240

3BK 02974 AAAA TQZZA Ed. 07

7 Cell Environments

7.3

Sectored Site
A sectored BTS site uses a single physical BTS equipped with up to three antennae illuminating three sectors, each covering a separate single macrocell as shown in Figure 59. The BTS in a sectored site contains up to three transceivers which are each allocated to different given sectors. Each sector and its associated cell are managed independently and are seen functionally, by the OMC and BSC, as separate BTSs connected in chain mode. Within the physical BTS site, there is a master BTS and up to two slave BTSs. Each BTS generates its own clock locally, but the slave BTSs are synchronised to the master BTS.

Sector 1

Cell 1

BTS Cell 2 Sector 2

Cell 3

Sector 3

Antenna

Figure 59

Sectored site configuration

3BK 02974 AAAA TQZZA Ed. 07

175 / 240

7 Cell Environments

7.4

Extended Cell
An extended cell is made up of two cells, an inner and an outer, see Figure 58. The inner cell handles calls up to a distance of 35 km (the same as a normal cell), while the outer cell handles traffic from 33 km up to a maximum range of 70 km. The inner and outer cells are covered by two synchronized, co located G2 BTSs. The reception (uplink) of the outer cell is delayed to correspond to a 33 km shift in range. Radio continuity between the two cells is ensured by the overlap zone. The inner cell uses two carrier units:
" "

CU BCCH Inner: at the inner cell BCCH frequency CU RACH Catcher: at the outer cell BCCH frequency, but with transmission switched off.

Because the outer cell can have areas of strong signal within the inner cell's coverage area, it is necessary to prevent an MS in such a region from camping on the outer cell frequency. This could lead to sudden signal degradation as conditions change, and eventual loss of the call. The RACH Catcher receives channel_request messages from MSs which are synchronized on the outer cell BCCH frequency, but are within 33 km of the BTS. The BTS knows, from the timing advance sent by the MS, that it is actually in the inner cell, and assigns the MS to an inner cell SDCCH frequency. The outer cell uses one CU with reception delayed by 60 bits. This effectively shifts the logical position" of an MS 33 km nearer than its actual position and allows it to be handled in the standard GSM 0 63 bit timing advance range. The handover procedure is controlled normally, with the settings ensuring that the necessary distance has been reached before handing a call over to the outer or inner cell.

176 / 240

3BK 02974 AAAA TQZZA Ed. 07

7 Cell Environments

Different types of coverage are possible depending on the type of antenna used for the inner and outer cells. The example in Figure 60 shows an extended cell with an omnidirectional inner cell and directional outer cell.

Inner Cell Highway Urban Area Outer Cell 70 km max

35 km max

Figure 60

Example of Extended Cell Topology

3BK 02974 AAAA TQZZA Ed. 07

177 / 240

7 Cell Environments

7.5

Umbrella Cell
In much denser traffic areas, depending on the required traffic capacity, a hierarchical network is used, where continuous coverage is provided by an umbrella cell (macrocell), and traffic hot spots are covered with dedicated lower layer cells of limited range. Fast moving mobiles are kept in the upper layer cell to avoid a high rate of handovers. For medium density areas small macrocells (called mini cells) are overlaid with one umbrella macrocell, see Section 7.5.1. For higher traffic densities microcells are installed in all the streets where very dense traffic occurs. Umbrella macrocells provide continuous coverage for level and quality handovers, and saturated overlaid cells. Refer to Section 7.5.2 for more information about the relationship between umbrella cells and microcells.

7.5.1

Mini Cell
Mini cells are used for dense urban areas where traffic hot spots are covered by very small macrocells (500 m to 1 km radius) and continuous coverage is provided by an overlaid macrocell (5 to 10 km radius). The lower layer mini cells handle pedestrian traffic while the umbrella cell handles the faster moving mobiles. As only macrocells are used there is no street corner effect. Figure 61 shows the application of the two layer hierarchical network, with macrocells for both layers, in a small town.
Umbrella Cell

Pedestrian area

Mini Cells Urban area

Figure 61

Umbrella Cell with Mini Cells

178 / 240

3BK 02974 AAAA TQZZA Ed. 07

7 Cell Environments

7.5.2

Microcell
Microcells have a small coverage area (less than 300 m radius). These cells are usually situated indoors or along streets in built up areas. Microcells have an umbrella cell (1 to 2 km radius) to minimize the risk of losing calls by providing maximum coverage. The microcell's small radius is created by limiting the maximum power output strategically to cover a pre defined microcell area. Handover occurs more frequently in a microcell environment due to the small radius sizes. Microcell handovers occur:
" " "

To handle stationary MSs (especially MSs used indoors). When an MS moves in a street covered by microcells. To avoid losing calls. Whenever there is a risk of losing a call, a handover is triggered to the umbrella cell.

Fast moving mobiles are handled by the umbrella cell. A mobile handled by a microcell is sent to the umbrella cell if the delay between handovers becomes too small. Conversely a mobile is sent to a microcell if it receives a high level of signal for a sufficient time. Call quality/control is achieved by providing four thresholds for microcell handover and one handover threshold for macrocell handover.

Micro to Micro Handover


Microcell to microcell handover occurs due to the proximity of the two cells. When the power budget is better in another cell, the MS is handed over to the cell which will serve the call more efficiently. This normally occurs in microcells serving in the same street.

Micro to Macro Handover High Threshold Handover Low Threshold Handover


This type of handover occurs when the signal strength has dropped below the theoretical signal level at the radius of the cell. This would normally mean that the MS has turned a street corner. This type of handover occurs when the MS level is under the high threshold and the signal level has dropped below the low threshold. The handover is to the umbrella/macrocell, which supports the call until the MS moves into another cell. When the macro to micro threshold is exceeded in the umbrella/macrocell, the MS is passed to a new microcell.

3BK 02974 AAAA TQZZA Ed. 07

179 / 240

7 Cell Environments

Rescue Handover

The MS is forced to handover to the umbrella cell when no measurement reports are transmitted. This occurs after a number of consecutive SACCH reporting periods.

Macro to Micro Handover M_to_m Threshold Handover


This occurs when the MS signal level in a microcell is above the M_to_m threshold for a certain period. This threshold value must always be higher than the low threshold value of the cell. Otherwise, a handover ping pong effect can occur between the umbrella and the microcell. If the low threshold is not used, the M_to_m Threshold value must be above the high threshold value.

Note

Threshold Handover Example


The example in Figure 62 shows two typical cases of handover in microcells:
" "

Micro micro handover along a street (Case 1 in Figure 62) Signal levels rising and dropping, causing macro/micro handover (Case 2 6 in Figure 62). This example shows the use of the two levels of Macro micro handover (strong to weak signal, and weak to weaker signal). This is represented by the high and low threshold handovers. This example also shows the macrocell handing back to a microcell once a stronger signal level is received.

High Signal Level 1 2 d B m 3 Micro Micro Handover 6 High Threshold M_to_m Threshold Low Threshold 5 Low Signal Level

Figure 62

Example: Handovers due to Threshold Triggering

180 / 240

3BK 02974 AAAA TQZZA Ed. 07

7 Cell Environments

Case 1

An MS is moving along a street. As it moves along a street, the MS is handed over from microcell to microcell (1).

Case 2 6

An MS turns a corner then moves indoors. 1. Call starts at (2). The signal level is normal. 2. The MS signal level drops below the high threshold level (3), e.g. when turning a corner. To protect the call, it is handed over to the macrocell until a better microcell is found. The call remains with the macrocell until a strong signal from another microcell is received (normal case). 3. If a strong signal from a microcell cannot be found, a weaker signal from a microcell with enough strength to be above M_to_m threshold level, but remain below the high threshold is found (4). In this case, as long as the signal strength remains above the low threshold and there is not a better microcell, the call remains with that microcell (e.g. the MS is indoors). 4. The signal level drops below the low threshold (5). The MS is again passed to the macrocell (e.g. the MS moves further inside a building). The macrocell is used to ensure call quality. 5. The MS moves into a position whereby the MS reports a microcell signal level above M_to_m threshold (6). The call is handed over to that microcell, e.g. the MS is still indoors, but has a stronger signal from a microcell.

3BK 02974 AAAA TQZZA Ed. 07

181 / 240

7 Cell Environments

182 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

8 Operations & Maintenance


This chapter provides an overview and describes O&M functions in the context of an operational network. It describes: G G G G G G G O&M Communication Mechanism Alarms Status Changes Call and IMSI Tracing Measurement Jobs Audits Modifying Telecom Parameters.

This chapter does not describe the principles of O&M. For more information about O&M, refer to the Operations & Maintenance Principles document.

3BK 02974 AAAA TQZZA Ed. 07

183 / 240

8 Operations & Maintenance

8.1

Overview
To ensure that the BSS functions correctly, O&M actions are implemented at all levels within the BSS. All of the BSS components perform O&M functions, as follows:
"

The BTS monitors the condition of the hardware modules it manages, and reports any change in status to the BSC. The BSC supervises its own hardware modules and reports changes in status to the OMC R. The TSS provides a set of O&M functions to ensure a high level of fault tolerance and reliability. It provides efficient use of the terrestrial links between the equipment of the BSS.

"

"

Note

The OMC R is an external component of the PLMN. Although, it is technically not a BSS component, it functions directly with the BSC for O&M purposes. The OMC R O&M functions of the BSS mainly involve operation and control actions. The BSC O&M functions mainly involve the routing, control and filtering of O&M messages. The hardware and software within the BSS are grouped into functional blocks. Each block, SBL, performs a set of associated functions. Functional redundancy based on autonomous recovery is provided in the SBL hierarchy to maintain an operational level within the system when faults occur.

8.1.1

BSC O&M Functions


The System Common Processor Type A (S CPRA) module of the BSC controls the O&M functions shown in Table 15. A BSC terminal allows an operator to perform Configuration and Fault Management functions on the BSC components.

184 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

Table 15

O&M Functions Function


G G G G G G Configuring local date and time Software and database replacement Reading and modifying logical parameters. Fault detection, fault correlation and fault localization on all devices controlled by the processor BSC reconfiguration in case of loss of the BCCH, Terminal Con trol Unit (TCU)/FU or a CU (G1 or G2 BTS). BSC reconfiguration in case of loss of the BCCH, TCU/TRE (BTS A9100). Result collection and collation X.25 related counters Traffic measurements on radio channels Performance Measurement result reporting Trace invocation result reporting.

Management Area
Configuration Management

Fault Management

Performance Management

G G G G G

Figure 63 shows a simplified block diagram of the BSC O&M components.

TCU

DTC To the MSC

TCU To Remote BTS TCU Digital Switching Network

DTC

S CPR

To the BSC Terminal To the OMC R

TCU

OSI CPR

BSC

Figure 63

BSC O&M Components

3BK 02974 AAAA TQZZA Ed. 07

185 / 240

8 Operations & Maintenance

8.1.2

BTS O&M (G1 and G2 BTSs)


The BTS is designed to ensure redundancy of the central and most important components in the BTS. This ensures that system integrity and availability are maintained at all times. Figure 64 illustrates the central BTS O&M components and data flow.
Air Interface

BSI

F H FU S W I T C H

CU COMBINER

FHI FU CU

RTE

Diagnostic and Control Link 1 (Token bus)


OMU

Diagnostic and Control Link 2 (Q1 bus)


EXTERNAL ALARMS & CONTROL

Legend Operations and Maintenance data BTS Terminal FHI = Frequency Hopping Interface Signal flow BSI = Base Station Interface

Figure 64

O&M Components and Data Flow in the G1 and G2 BTS The Operations and Maintenance Unit (OMU) controls and monitors all equipment connected to the BTS internal diagnostics and control links. This includes the Diagnostic and Control Link 1 Token Bus and the Diagnostic and Control Link 2 Q1 Bus. A BTS terminal allows an operator to perform Configuration and Fault Management functions on the BTS components.

186 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

8.1.3

BTS A9100 O&M


The design of the Alcatel BTS A9100 provides enhanced reliability by reducing the number of Functional Units. These are each subdivided into Functional Entities. There are three primary Functional Units in the BTS A9100:
" " "

TRE AN SUM

Figure 65 illustrates the O&M components and data flow in the BTS A9100.
Air Interface

BSII

BTS Terminal

BSII

Figure 65

3BK 02974 AAAA TQZZA Ed. 07


SUM
Abis interface to BSC TRANS & CLOCK BSII Switch and Timing

BSII

AN

ANX

ANY

RI

BCB

OMU

MMI

BCB

TRED

TREA

TRE

TREA = TRE - Analog part TRED = TRE - Digital part RI = Remote Inventory

Legend

O&M Data on the BSSI (Base Station Internal Interface) O&M Data on the BCB (Base station Control Bus) Signal flow

NOTE:

This diagram does not show all elements nor all interfaces. Refer to BTS A9100 Functional Description for details of functional entities.

O&M Components and Data Flow in the BTS A9100

187 / 240

8 Operations & Maintenance

The OMU is a Functional Entity in the SUM. It controls and monitors all equipment connected to the BTS internal diagnostics and control links. This includes the Base Station Internal Interface (BSII) and the Base Station Control Bus (BCB). A BTS terminal allows an operator to perform Configuration and Fault Management functions on the BTS components. For specific information about the architecture and interfaces of the BTS A9100, refer to BTS A9100 Functional Description. For specific information about the configuration of the BTS A9100, refer to BTS A9100 Software Description.

8.1.4

BTS O&M Functions (All Generations)


The BTS O&M functions are:
"

Supervision of the BTS equipment. This includes initializing and configuring of the BTS. Testing of the equipment. This includes collecting alarms and reporting to the BSC. Diagnosis and fault reporting for the system. Access provision for the local diagnostics and configuration of the BTS. Transfer of software and data files to the FUs (G1/G2) or TREs (BTS A9100). Management of equipment states. This includes triggering BTS channel configuration in case of a failure. Control of the Auto Identification feature (BTS A9100 only). Application of the logical configuration of the BTS. Event report management. See Section 8.3.1 for further information concerning events.

"

" "

"

"

" " "

8.1.5

TSC O&M Functions


The O&M functions of the BIE, SM and TC are monitored by a dedicated TSC. A TSC terminal allows an operator to perform Configuration and Fault Management functions on the TSS components. Alarm situations are monitored at the OMC R, and fault localization is based on information received by the OMC R.

188 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

The primary O&M functions of the TSC are:


"

Communication through the Q1 interface with the TC, SM and BIE modules Communication through the LAPD link with the BSC Status monitoring of the TC, SM and BIE modules Permission for configuration and re configuration of the TC, SM and BIE modules Access provision to the fault localizing features of the TSC Local access provision to configuration of the TC, SM and BIE modules.

" " "

" "

Figure 66 shows transmission modules that perform O&M functions.


X.25 Link to OMC R

BIE

BIE

LAPD Link to BSC Q1 Bus Q1 Bus

TSC Terminal

Figure 66

Transmission System O&M Components

3BK 02974 AAAA TQZZA Ed. 07


BSC
TSC

SM2M

SM2M

TRCU

A Interface to the MSC

189 / 240

8 Operations & Maintenance

8.1.6

OMC R in O&M Functions


The O&M functions of the OMC R are:
"

Providing the operator with an interface to the system to:


D

Configure the network


h h

Perform software configuration management (files, version downloading) Provide configuration functions for logical parameters. Display alarm status and history Display equipment and resource states Perform Performance Management jobs (scheduling, raw counter management, virtual counter definition) Snapshot management Definition and supervision of counter thresholds (Quality of Service alarms). Access to equipment management functions (test) Access to resource equipment state management.

Supervise the network


h h h h h

Maintain the network:


h h

"

Keeping track of hardware and software configurations in the system and managing software versions Providing mediation between the Alcatel BSS and one or more NMCs. This uses the Q3 interface.

"

190 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

8.2

O&M Communication Mechanism


This section explains how:
" "

O&M functions communicate within the BSS Messages are passed amongst the OMC R, BSC, BTS and the TSC.

The communication mechanism transports alarm, event, audit and operator command messages throughout the BSS.

8.2.1

O&M Command Flows


OMC R/BSC
OMC R information is passed between the OMC R and the BSC, using the CMISE protocol. The CMISE protocol is the OSI network management protocol over X.25. The majority of OMC R related commands are based on the four message scenarios:
" " " "

M_ACTION M_ACTIONcnf M_EVENT_REPORT M_EVENT_REPORTrsp.

These message scenarios are shown in Figure 67. The OMC R requests an action from the BSS via the CMISE command M_ACTION. Specific commands are used for each action. For example, to demand an alarm list, the OMC R issues the command: M_ALARM_LIST The word ACTION in the table above and in the illustrations which follow is replaced by the real command, in this case ALARM_LIST.
OMC R BSC

ACTION

Figure 67

Example: Message Flow Using CMISE

3BK 02974 AAAA TQZZA Ed. 07

191 / 240

8 Operations & Maintenance

BSC/BTS/TSC

The O&M protocol between the BSC, the BTS and the TSC uses the GSM standard 08.59 (O&M signalling transport layer) header. This header handles the sequencing and encapsulation of data. The O&M command/message is stored with its channel identity, reference and parameters. For more information about the alarm and measurement observation parameters, refer to the BSS Alarm Dictionary and the Operations & Maintenance Reference Guide. The command sequence between the BSC and its corresponding BTSs and TSCs uses a similar command flow to the CMISE. This is shown in Figure 68.
OMC BSC BTS

ACTION

Figure 68 Note

Example: BSC Command Flow

There are also other, less common message exchanges. They are based either on one pair of the four message sequence, or several replies to the original M_ACTION pair, i.e. M_ACTION and M_ACTIONcnf.

192 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

8.2.2

Spontaneous Messages
Messages such as alarms and event changes are spontaneous. Alarms are generated due to changes in the operation of the system. They are not in response to an action invoked by the OMC R. This means that there is no M_ACTION pair. There are two message scenarios for spontaneous messages:
"

M_EVENT_REPORT which is an event_report (i.e. from the BSC to the OMC R) M_EVENT_REPORTrsp which is a response to the event_report (i.e. from the OMC R to the BSC).

"

Alarms Event Changes

Alarm start and alarm end commands use two messages. The alarm arrives at the OMC R as an alarm report. The OMC R sends an acknowledgement. Event messages are spontaneous. They inform the OMC R of changes to the SBL state. See Section 8.3.1 for further information concerning events.

3BK 02974 AAAA TQZZA Ed. 07

193 / 240

8 Operations & Maintenance

8.3

Alarms
The BSS generates alarms to signal a change in the behavior of a particular function within the system, such as a potential problem or a confirmed failure in the system. This section describes the alarm generation process. It describes the alarms and their effects on the system.

8.3.1

Alarm Generation
When an Alarm is generated, it is indicated as either:
"

Fault (begin or end) If a fault arises, the related alarm is stored in an Alarms In Force List (AIFL) in the relevant BSS unit, and also in the OMC R. The alarm begin message signals that a particular system activity has stopped due to an error. When the error is corrected, an alarm end message is sent to indicate that the condition no longer exists, and the alarm is taken out of the AIFL.

"

Event An Event occurs when an unexpected situation arises during system operation.

Alarms can be generated as a result of previous alarms or events which influence other parts of the system. For example, when the CU produces an alarm to signal an internal fault, the FU and the Radio Signalling Link produce alarms to signal that no information is being received from the CU. Fault correlation and filtering actions are performed by the O&M modules in each unit, so that a single fault is sent as an alarm. In the case of the faulty CU, an alarm is sent signalling a CU fault. In this example, the loss of the RSL link is signalled from the BSC but is not correlated.

Correlation

Correlation refers to the collection and analysis of all available fault indications for a particular problem. Fault correlation is performed to define where and why the fault occurred. An example of correlation is as follows: 1. When several boards in the BTS report clock problems, these reports are correlated by the OMU. 2. The 'clock generator is faulty' alarm is sent to the OMC R.

194 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

Filtering Persistency

Alarms are filtered to minimize the number of fault alarms reported and displayed to the operator. Alarms are displayed in order of severity. A fault is signalled only if there is no recovery after the timer expiration. For example, in the case of a LAPD failure of an RSL link, an alarm is sent only if the LAPD link has not recovered before the persistency timer has expired. Each BSS component keeps an AIFL, so that the system knows that an alarm has begun. This list ensures synchronization of alarms throughout the BSS components. This makes the alarm situation visible at all times. The OMC R also keeps track of all the AIFLs for each BSS component.

Alarms in Force

8.3.2

BSC Alarms
BSC detects alarms on the Abis and A trunk via the TCU and the DTC. It also detects alarms from each functional unit of the BSC.

Heartbeat

The active S CPRA creates a daisy chain map of all the processors in the BSC. Every ten minutes, the S CPRA sends the map to the next processor. This processor sends the information to the next processor in line, until the S CPRA receives the daisy chain map. The daisy chain map can be modified by an intermediary processor when that processor cannot send the map to the next processor in line. In this case, the intermediary processor skips the processor and removes that processor from the daisy chain map. When the S CPRA receives the map with the same processor missing twice in a row, it tries to recover the processor. If the processor cannot be recovered, the S CPRA places the processor in the Faulty (FLT) state. The S CPRA signals the event change and alarm to the OMC R as follows:
"

If a TCU fails, recovery only takes place to ensure BCCH functionality. If a DTC fails, the BSC tries to inform the MSC, so that MSC is aware that the SS7 link is now out of service. This implies:
D D

"

The loss and, if possible, the change over of the SS7 The blocking of circuits.

3BK 02974 AAAA TQZZA Ed. 07

195 / 240

8 Operations & Maintenance

Telecom Link or Trunk Failure

The TSC supervises its trunks and their links between the TSC, BTS, and MSC. Failure of the Abis interface is signalled to the BSC by all of the RSLs of the associated BTS. A single RSL failure reflects the status of the corresponding LAPD and FU. All A interface faults are controlled by the TSC and the MSC. However they are also monitored by the BSC, in order to define the status of each "end to end" A trunk. Figure 69 shows RSL fault correlation on the Abis interface.

Note

The BTS_TEL SBL describes the status of the GSM defined BTS telecom functions. Its state is defined by operator commands, and correlation of the LAPD RSL states or of the different CUs.

Fault Start RSL-1

CPR Informed

RSL State Change Alarm begin BTS_TEL

Persistency Fault Start RSL-2

Correlation

ACTIVE INACTIVE

Fault Start RSL-N (last RSL)

Figure 69

RSL Correlation on the Abis Interface

196 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

The BSC monitors the A interface faults as follows: 1. The BSC detects the first LAPD RSL link failure of the BTS. The BSC starts a persistency timer. It puts the SBL of the RSL into a Maintenance Seized (MSD) Auto state while the following actions occur:
D

The Replaceable Items (RITs) are now in the Software Out of Service (SOS) state. This is because the Radio Time Slot (RTS) belonging to the RSL still functions, but cannot communicate with the BSC. Telecoms resources are blocked to prevent new activity at the BSC end of this link. The RSL SBL is put into the FLT state, reflecting the loss of the RSL.

D D

2. The persistency timer expires and the Common Processor (CPR) is informed of the fault. If the link recovers during the persistency period, nothing is reported. Otherwise a correlation timer starts and waits for further RSL link failures belonging to the same BTS. 3. Once the correlation timer expires the BSC informs the OMC R of each RSL failure by changing its state to the FLT state. 4. The OMC R is then informed about the state of the BTS_TEL. If all the RSLs belonging to the BTS have failed, then an alarm is sent to the OMC R signalling the loss of the cell. When an AIFL begins it puts the BTS_TEL in an FLT state. 5. When the BSC detects a DTC failure, the BSC puts the DTC SBL in the MSD Auto state. This prevents new MS originated calls from using the failed link of the DTC. It then changes the DTC SBL to the FLT state. This is then signalled to the OMC R. The TSC also detects a failure of the Ater link and signals the failure to the OMC R. Note The A channel is allocated only by the MSC. Software throughout the BSC detects error and alarm conditions. It reports these conditions to the alarm handling software. The alarm handling software performs persistency, filtering and correlation actions on the received alarm indicators, and determines the required action (e.g. to isolate a faulty SBL). Figure 70 shows an example alarm report.

Software Failure

3BK 02974 AAAA TQZZA Ed. 07

197 / 240

8 Operations & Maintenance

If one or more RSL links remain for the failed BTS, an event change is sent. An AIFL begins putting the BTS_TEL in a Faulty In Traffic (FIT) state, as some channels for that cell are in operation. The BSC marks the cell as degraded in service and reconfigures the BTS.
Alarm Class, Number and Name
==Alcatel 900 Event-time Event-type Object-class Object-instance

Alarm Type, Number and Name

BSS REPORT==============================125=== : 1995:11:15 10:43:42:09 Job-id : 44 : UNSOLICITED ALARM REPORT : SBL : unit-type : BTS nbr : 1 : SBL-type : FU nbr : 2

Alarm-info : alarm-class alarm-type alarm-nbr alarm-cat alarm-cond Prev-state Curr-state Rit-list unit-type BTS BTS BTS BTS BTS BTS BTS BTS Defence-action Suspected-rit unit-type BTS Addition-data

: : : : : : :

07 FRAME UNIT 006 BOTH-BSI-LINKS 1 PMA BEGIN IT FOS

nbr 1 1 1 1 1 1 1 1 :

rack 2 2 2 2 2 2 2 2

shelf 3 3 3 3 3 3 3 3

slot 5 21 33 15 17 19 25 27

rit-type FUPS FUCO FUIF CECC CDCC CDCC DMDT DMDT

NO ACTION

Addition-data

Addition-data

nbr 1 223 2 61 48 0 0 0 0 1 0 0 255 BTS 1

rack 2 53 0 42 1 255 1 0 0 0 8 0 255

shelf 3 6 48 0 51 255 0 0 0 1 0 8 255

slot 33 35 0 2 130 0 1 0 0 0 0 0 255

rit-type FUIF 8 223 0 0 0 0 0 0 8 0 255 255

Flt-loc-unit-type Flt-loc-unit-nbr

: :

Timestamp : 1995:11:15 10:43:42:09 ===========================================================================

Suspect RIT

Additional information

List of RITs belonging to SBL

Figure 70

Example: Alarm Report

198 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

8.3.3

BTS Alarms
Alarms in the BTS are tracked by the OMU. In G1 and G2 BTSs, the OMU has a Q1 interface to the CUs, Master Clock Unit (MCLU), External Alarm Collection Board (EACB), and Frequency Hopping Unit (FHU) modules in the system and a Token Bus interface with all of the FU modules. In the BTS A9100, the BSII provides the OMU with an interface to the TRE functional unit, and to the ANx and TRANS & CLOCK functional entities, which have their own on board controllers. The BCB provides an interface to all the functional entities in the BTS. On the Q1 interface, a system of double polling takes place. The OMU polls each subsystem individually to find out if there is an error. If there is an error, the OMU demands an error report from that board. Normally, the information from the error report is used as an alarm or an event notification. On the Token Bus interface, the OMU is informed by the FU about the type of error that has occurred. The OMU sends the alarm information to the BSC. On the Base Station Internal Interface, each module spontaneously reports errors to the OMU, which processes the report as an alarm or an event notification. The Base station Control Bus operates in a master/slave configuration where the SUM functions as Pilot (master) and the functional entities function as Terminals (slaves) in normal conditions. The OMU collects alarm information on the BCB and sends it to the BSC. The mechanism for BTS alarm collection on all buses is as follows: 1. The alarm is added to the AIFL. 2. The OMU enters alarm information in a queued buffer. In this way, alarms are queued even if the link between the BTS and the BSC is temporarily unusable. If the buffer becomes full (over 100 messages):
D D

G1/G2 Alarm Buses

BTS A9100 Alarm Buses

Q1 Interface (G1/G2 BTS)

Token Bus Interface (G1/G2 BTS) BSSI (BTS A9100) BCB (BTS A9100)

Alarm Collection

All fault/state change messages are deleted No more messages are sent until a state and alarm audit takes place to synchronize the BSC and the OMC R. An audit BTS request is transmitted on a regular basis until an audit occurs.

3BK 02974 AAAA TQZZA Ed. 07

199 / 240

8 Operations & Maintenance

3. The alarm messages are transmitted at level 3, over the Abis link to the BSC. The message format uses the GSM standard 08.59, which contains the alarm information. This is described in the BSS Alarm Dictionary and the Operations & Maintenance Reference Guide. 4. The message is sent to the System Common Processor Type A (CPRA), where it is date and time stamped. 5. The BSC performs one of two activities:
D

If possible, it processes the alarm, performs an action and sends a different alarm/event to the OMC R, via the alarm queue Otherwise, it re transmits the message to the OMC R, via the alarm queue.

6. The message is put in the alarm queue. If the queue overflows, the BSC performs an Alarms in Force audit on all the modules in the BSC. This signals that information was received and lost when the queue overflowed, and that resynchronization is required. 7. The OMC R receives the alarm over the CMISE link. It logs the alarm in the AIFL and on the console.

8.3.4

TSC Alarms
TSC O&M activities are similar to those performed by the BTS. The TSC has a Q1 interface to the transmission equipment. A system of double polling occurs on the Q1 interface:
" "

The first poll checks if there was a change in states The second poll occurs only if the state has changed, in order to obtain more information about the changes.

The loss of the link between the BSC and TSC is the only indication the TSC receives that a failure has occurred.

200 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

8.4

Status Changes
Status changes show the interaction between:
" " "

SBL states Operator commands The status of functional units.

This section describes possible changes in SBL status, and the effect such changes have on the rest of the system. It lists the operator commands that can be used in each SBL state. The impact of operator commands on the operation of the unit and on its SBL state are also described.

8.4.1

Phases of Board Operations


A functional unit (i.e. 1 SBL = n RITs = n boards) such as a TC passes through several states before becoming operational: Table 16
State Bootstrap

Functional Unit States


Action Bootstrap enables the functional unit to be initialized, and to perform functions including self tests and downloads. Extensive self tests take place to ensure that the functional unit is physically functional. Software download of programs occur if the SBL is able to load software. Software starts and is in operation. Non destructive self tests (memory checksum, program id verification, compatibility, etc.) are initiated to ensure that the hardware and software can function as a complete unit. This function ensures the download of configuration data. It also ensures synchronization. The board is now functional. The board is functioning, but could be in a state of degraded service. Degraded service can be due to hardware/software problems. The board can still operate, but at less than maximum service or reliability.

Self tests Software Download Software Start Tests

Download Configuration Start In Operation

3BK 02974 AAAA TQZZA Ed. 07

201 / 240

8 Operations & Maintenance

8.4.2

State Change Operations


Maintenance commands ensure the control of system entities and functions, either by returning them to a known active mode, or by deactivating them. Figure 71 shows the tasks performed for each maintenance command. The tasks are shown as they occur in the system boards during initialization phases.

COMMANDS DISABLE RESET (loadable units only) INIT

Tasks performed by SBL as a result of each command WAIT Bootstrap Self Tests

STATES OPR,FOS,FLT

SW Download MSD, MSD auto RESTART (loadable units only) SW Start Tests Download Config Function Start Operational IT, FIT, WTC

Figure 71

States and Phases of Board Operation The operational states show how the RESET, INIT, DISABLE and RESTART commands affect functional units and its SBL state. Note The status of a board (active, inactive or faulty) has a direct relation with the state of the SBL.

202 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

8.4.3

States In Traffic
The following states are all active SBL states: IT An SBL in the In Traffic (IT) state performs all its functions. It is set into traffic by the operator and no problems are detectable. An SBL in the FIT state performs its functions in a degraded mode. A RESET or RESTART can be performed as a recovery measure. The disabled SBL states FLT and Operator Out of Service (OPR) can exist only when a board is:
D D

FIT

Not operational and is waiting for a bootstrap start Already in self test mode.

WTC

An SBL in the Wait Traffic Clear (WTC) state waits for the traffic to clear (i.e. a transitional state). When there is no traffic, the SBL state changes to OPR. This SBL state signals that no new traffic will be accepted by this SBL/equipment. The WTC state is used in two ways:
D D

As a time out action in cases where existing traffic can be active until the timer expires To wait until all traffic disappears before changing the state.

EF

An SBL in the External Fault (EF) state cannot perform its function because another co operating item is not operational.

Figure 72 illustrates the relationships between SBL states.

3BK 02974 AAAA TQZZA Ed. 07

203 / 240

8 Operations & Maintenance

WTC

OPR

FIT

SOS

EF

MSD

IT

FU Only UT NEQ

FOS

FLT

Figure 72

Relationship Between SBL States

8.4.4

States Not In Traffic


The following states are all disabled states except for MSD and Under Test (UT) which are transitory states due to some automatic function: OPR An SBL in the OPR state has been disabled by the operator. The SBL cannot perform its functions until the operator takes action. A fatal error has been detected. The FLT state means the service is unavailable but the SBL has the capability to recover autonomously without operator intervention. A fatal error has been detected. The Faulty Out of Service (FOS) state means the service is unavailable and the SBL does not have the capability to recover autonomously. Maintenance action is required. The operator must use the INIT command to recover the SBL. An SBL in the Not Equipped (NEQ) state is not handled by the system because it has not been configured.

FLT

FOS

NEQ

204 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

MSD

MSD is a transitional state which takes effect while a board is going through the software and configuration load process. For example, when a fault is detected while the SBL is in the IT state, the SBL state changes to MSD. It remains in the MSD state while the system determines the effect of the fault and chooses one of the following final states:
D D D D

FLT FIT FOS EF .

UT

The SBL is being tested using automatic procedures. The service is temporarily unavailable. It is possible that due to the test actions, the previous level of service may change. This state is only valid for the Frame Unit Time Slot (FU_TS) SBL when the RTE Loop test is running (G1/G2 BTS only). An SBL in the SOS state cannot perform its function because a parent SBL is not operational.

SOS

The transitions from one state to another are controlled. The board state of the SBL changes from an active state to another state.

8.4.5

BSS SBL Operator Commands


The O&M operator commands, described in Table 17, which affect the state of the SBLs are as follows:
" " " "

DISABLE INIT RESET RESTART.

3BK 02974 AAAA TQZZA Ed. 07

205 / 240

8 Operations & Maintenance

Table 17
DISABLE

SBL O&M Operator Commands


Previous State The board can be in any known or unknown state. DISABLE puts the board out of active service for maintenance purposes. The board was previously in a wait state, or performing bootstrap or self tests. Action Taken The board is deactivated. New State The OMC R is informed over the CMISE link. The SBL is set to the OPR state. The unit is isolated from the rest of the system The unit is in an active state (In Traffic (IT)) and all previous active faults related to this SBL are removed from the AIFL. The OMC R is informed over the CMISE link. The logical flow described above is initiated. The unit is in an active state (IT) and all previous active faults related to this SBL are removed from the AIFL.

Command and Description Places an active SBL into a disabled state.

INIT Reactivates a component which had been previously disabled. Once initialised, the component is operational and active.

The board passes through all phases: G G G G G G Self tests SW download SW start Tests Configuration Operation.

RESET Acts as a combination of the DISABLE and INIT com mands. It allows the SBL to recover from a situation where the behavior is suspi cious. It initiates self tests and returns the SBL to a known state. This command applies to loadable components (i.e. processor SBLs), or to the BSC, the BTS, the TSC, and the BSS. RESTART

The board was operational, but usually with a malfunction.

The board passes through all phases: G G G G G G Self tests SW download SW start Tests Configuration Operation.

The board was previously operational Allows the software to restart (under normal without a download (unlike conditions), in either the RESET), and without losing the FIT or the IT SBL state. context (in most cases). This helps keep downtime to a minimum for active systems. This command applies to processor SBLs, BSC, BTS, TSC, and the BSS.

The board passes through these phases: G G G G SW start Tests Configuration Operation.

The logical flow described above is initiated. The unit is in an active state (IT) and all previous active faults related to this SBL are removed from the active AIFL. The OMC R is informed over the CMISE link.

206 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

8.4.6

Recovery Example: CU Failures with BCCH


As an example, this section describes the system's reactions when a CU (or TRE for the BTS A9100) which has the BCCH channel fails. Note In the BTS A9100, the SBLs FU and CU have been merged into one indivisible SBL, called the TRE. At the BSC, however, all BTS A9100 TRE faults are mapped to the CU to provide compatibility with G1 and G2 BTSs. Thus, at the BSC all such errors are displayed as CU faults. That is how they are presented in this example. FU faults in G1 and G2 BTSs continue to be reported as such. The recovery mechanism in the BSS allows a failed unit to switch to a replacement unit, such as:
" "

Fault Recovery Mechanism

Redundant hardware A similar unit which had lower priority active use than the failed unit. (For example, the BCCH has to exist for the cell to function, so another CU/FU pair (TRE in the BTS A9100) is expendable to replace the failed CU).

The recovery mechanism of the BSS recognizes that the CU can change to its twin CU. Note One CU is used for BCCH channel handling, another is used for normal traffic. If the CU holding the BCCH fails, it is switched out and the second CU takes the place of the first. Below is a step by step scenario of CU recovery. 1. The CU holding the BCCH fails. 2. The BTS sends the BSC a recovery request, reporting that the CU is faulty and is out of service, and that a recovery is required. The BTS also suggests a new CU to the BSC, to be used to carry the BCCH. When the recovery request is received, the BSC temporarily blocks the resources while it checks if reconfiguration is available. If reconfiguration is available, the BTS_TEL SBL becomes FIT and all calls on the CU are immediately released. The RSL is blocked and their SBLs are changed to RTS=EF. All calls on the CU are immediately released. 3. The BSC sends an alarm to the OMC R, signalling the loss of BCCH. 4. The BSC attempts a recovery. The recovery command is BTS CONF DATA(2).

Scenario

3BK 02974 AAAA TQZZA Ed. 07

207 / 240

8 Operations & Maintenance

5. The BTS receives and acknowledges the recovery message. It then switches off the faulty CU and switches on the second CU. The second CU adjusts its frequency to the BCCH frequency. 6. If the configuration was successful, the BTS sends a confirmation to the BSC. The BSC then sends the new SYS_INFO (1 6). 7. The BCCH is now broadcasting on the same frequency as before, via the newly configured CU. 8. The BTS sets its BTS_TEL SBL to FIT and informs the OMC R by sending an end of alarm. The BTS_TEL remains FIT due to the loss of a channel. 9. If the new CU was previously IT, then all resources are lost. An alarm start is sent towards the OMC R for each channel lost. Figure 73 shows the redundancy process for a failed CU with BCCH.

208 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

OMC

BSC
BTS_TEL=IT Resources blocked, BCCH reconfiguration possible 3 4

BTS
CU Fault

BTS_TEL=FIT

BTS_TEL=FIT

5 BTS performs the reconfiguration

6 8

9 BTS_TEL=FIT

Figure 73 Note

Example: Loss of CU Holding BCCH.

BTS_TEL SBL describes the status of the GSM defined BTS telecom functions. Its state is driven by operator commands, or by correlation of the LAPD RSL states or of the different CUs.

8.4.7

Reset Example: TSC RESET


As an example, this section describes the system's reactions when the TSC is reset by the operator:

Example TSC Reset

1. The operator invokes the RESET command. The OMC R accepts the command and places the TSC in the MSD state. The TSC remains in the MSD state while transmitting the reset to the BSC. 2. The BSC passes the RESET command to the TSC. It receives the ACK acknowledgement message from the TSC, disables the TSC LAPD Signalling Link (TSL) to the BSC, and starts the persistency timer. 3. The TSC accepts the command and places itself in the MSD state. The TSC disables the TSL from its end, and performs a self test. After ten seconds the TSL becomes active again. 4. The persistency timer starts the BSC, and sends a state change message to the OMC R.

3BK 02974 AAAA TQZZA Ed. 07

209 / 240

8 Operations & Maintenance

5. The TSL is re established and the TSC resets and reconstructs its alarm list. Once this is done the TSC sets its status to IT and sends the BSC a reset report. 6. The reset report is acknowledged. It is converted to a CMISE message which is sent to the OMC R. The OMC R resets its view of the TSC to the IT state, and clears alarm lists for all SBLs for that TSC. 7. The TSC then sends a fault indication message to the BSC. The BSC acknowledges the message. The BSC packages the information as a alarm report in CMISE and sends the information to the OMC R. 8. The OMC R requests a state audit and an Alarms In Force audit. These are performed at the same time so the OMC R and TSC are synchronized. 9. The TSC is now in operation and therefore in the ACTIVE state. Figure 74 shows the TSC Reset process.
OMC
1

BSC
TR_O&M=IT

TSC
TSC=IT

TSC=MSD

2 TSL DOWN SELF TEST TSL UP reconstructs BSC detects TSL alarm list TR_O&M=IT 3 TSC=MSD

TSC=IT

audit

TSC=IT 7

Figure 74

TSC Reset

210 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

8.5

Tracing
Within the BSC there are two types of tracing:
"

Call tracing which can be initiated from a GSM phase 1 MSC, the OMC R or the BSC Terminal. IMSI traces (based on mobile identity) which can be initiated from a GSM phase 2 MSC.

"

The trace data collected in the BSC is formatted into files and transferred, using FTAM, to the OMC R or to the BSC Terminal (if the trace was initiated there). The file formats, and contents, for call and IMSI traces are different. The BSC performs error checking on the message initiating the trace procedure and verifies that trace data can be collected and stored in the BSC. Separate trace record structures are created in the BSC to differentiate between call and IMSI trace records.

8.5.1

Call Tracing
Call tracing allows the operator to trace call events on a particular channel and timeslot on a BTS. These trace jobs are initiated from the OMC R. The NMC initiates call tracing jobs on specified transactions (subscriber call, location update, short message, etc). In this way, an operator can trace and analyze call anomalies in a particular cell when:
" " "

Intermittent fault alarms appear There is low frequency of successful handovers Customers complain about a particular cell.

The current implementation of call tracing provides mainly performance measurement and handover event information. The following menus are available to the operator:
" " "

Performance Management BSC Call Management Trace Job Management.

When a trace exceeds 20K bytes, a new trace file is created and the previous file is subsequently transferred to the OMC R (using FTAM). The trace is a continuous process and many 20k files are transferred to the OMC R. The BSC is limited to 99 concatenation files. These files are shared between trace jobs and measurement jobs, so care must be taken not to exceed this limit. This can be achieved by limiting the traces and measurements jobs running on the same BSC.

3BK 02974 AAAA TQZZA Ed. 07

211 / 240

8 Operations & Maintenance

On completion of the file transfer, the OMC R informs the BSC that the file has been read. The operator can then archive and analyze the trace file off line. (If more than one trace is produced for a job, the files are concatenated in the archived file). Trace jobs can also be created from the local BSC Terminal. The trace files that result from these jobs are not transferred to the OMC R. When the trace data is ready for collection, the BSC notifies the local terminal. The trace data is then retrieved from the BSC, by the operator, using a copy file command. For further information refer to the BSC Terminal User Guide document.

8.5.2

IMSI Tracing
IMSI tracing allows the operator to obtain call path information on a specific MS's connection, based on the mobile identity. This information is gathered from different network elements, together with traffic data and other events related to the call, independent of performance measurement functions. The mobile identity used may be the IMSI, IMEI or neither, depending on the trace invocation received from the MSC. The MSC controls the trace activation towards the BSC by using the MSC_INVOKE_TRACE message. The trace is not restricted to speech but includes any information which requires the setup of a connection to the MS. This information can include location updating, short messages and supplementary service operations. Trace record information can be used in the analysis of:
" " " "

Cell footprinting Network integrity Network Quality Of Service Equipment used for mobile originated or terminated call connections Destination, forwarded to, and translated numbers used on call connections.

"

IMSI trace files include additional data supplied in the message from the MSC. This information is transparent to the BSC and is used by network management personnel to correlate trace data from different BSCs and MSCs. IMSI trace files are always collected by the OMC R and then passed to the MSC that initiated the trace.

212 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

8.6

Measurement Jobs
OMC R measurement jobs are defined by the operator to acquire raw or formulated counter/measurement information. The information received is then used to analyze the state of the system in operation. There are several types of performance management types or jobs. They are all based on counter collection and analysis (warning, snapshots and measurements). The only real differences are:
" "

The treatment and analysis of the collected information Whether collection is one shot, timed periods, or permanent. The reformatting and analysis of all performance information in the OMC R The data collection process in the BSC and the OMC R.

This section describes:


"

"

8.6.1

OMC R Measurement Job Classes


There are four main Measurement Job class groups described in Table 18.

Table 18
Class Group

Measurement Job Classes


Description This class provides permanent or scheduled jobs based on one raw measure ment type. This class provides permanent or scheduled jobs based on Mediated counters. This class provides alarms when a Mediated counter, or a group of Mediated counters, pass a threshold (or thresholds) defined when the task was invoked. Typical use is to provide a traffic overload warning as an avoidance measure. This class provides a graphical result of a counter of a particular BSS. For example, the total erlangs per channel can be displayed. (Erlangs is a statisti cal value to show the theoretical number of users the channel can provide).

Raw Measurements Mediated Measurements Mediated Warnings

Snapshot Jobs

3BK 02974 AAAA TQZZA Ed. 07

213 / 240

8 Operations & Maintenance

8.6.2

Measurement Results
Measurement results can consist of the following:
"

Raw measurements Raw measurement information is collected on every functional unit of the BSC.

"

Mediated Device Counters Mediated Device Counters are derived from raw measurements. They supply the operator with more precise information. For example, to obtain the percentage of handover failures, the number of raw measurements (the number of different failures and the number of total attempts) is collected. The information is collated and a failure rate is calculated as a percentage.

8.6.3

Counters
The relationship between counter objects is shown in Figure 75. The types of object that make up the hierarchical counter tree are as follows:
" " " " " "

Mediated Device Objects Mediated Device Counters Virtual Raw Measurements Raw Measurement OMC R (job) Raw Measurement BSC (job) Measurement Administrator

Mediated Device Objects Mediated Device Counters

When an operator performs a measurement request, all the details of the request are stored in the Mediated Device Object. The request requires one or more counters. Mediated Device Counters are created per Mediated counter in the definition of the Mediated Device Objects. Mediated Device Counters handle the calculation of a counter value which is based on a series of raw measurements counters. The Mediated Device Counter requires results from several raw measurements to perform its calculations. That is, to obtain the percentage of handovers requires the number of successful handovers, divided by the number of handover attempts. This information is provided by the Virtual Raw Measurements, one per raw_counter type.

214 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

Virtual Raw Measurements

The Virtual Raw Measurements collect and process data from raw counters and manage the reporting interval. The Virtual Raw Measurement is a virtual image of the raw measurement. The information however, is dedicated for use by its Mediated counter (i.e. report intervals). The raw measurement handler is the part of the OMC R which is in contact with the BSC. It receives counter information. It is also responsible for asking the BSC to start raw measurement jobs on its behalf. The raw measurements are invoked on the BSC at a rate of one per measurement type. These tasks obtain the data, which is available on the Central Data Collector. The data is passed on to the OMC R, via CMISE/FTAM, every five minutes. The Measurement Administrator interrogates the Central Data Collector on behalf of the active raw measurement jobs. It passes the information on to the OMC R.

Raw Measurement OMC R Raw Measurement BSC

Measurement Administrator

3BK 02974 AAAA TQZZA Ed. 07

215 / 240

8 Operations & Maintenance

mediated device object mediated device counter virtual raw measurement

raw measure

mediated measure

mediated warning

snapshot

mdc(j)

mdc(k)

mdc(l)

mdc(m)

T1i

T1j

T2j

T1k

T3k

T6l

T6m

T1m

raw measurement handler OMC R BSC

Rm (T1)

Rm (T2)

Rm (T3)

Rm (T6)

Rm (T1)

Rm (T2)

Rm (T3)

Rm (T6)

Measurement Administrator

Central Data Collector

Figure 75

Counter Object Tree

8.6.4

Data Collection on the BSC


Measurement information is collected from parts of the BSC. Each module has a Local Data Collector, which collects the data for its particular module. For example, in the TCU the Local Data Collector collects data for the Abis link and for the corresponding BTS. This information is passed on towards the Central Data Collector, where the information is collected for later or immediate use. There are three types of information passed to the Central Data Collector from the Local Data Collectors:
"

Cumulated Counters The Central Data Collector polls the Local Data Collectors once every five minutes to collect the data. The counter types range from 1, 3 to 9 and 26 to 28. Counter types are defined in the Operations & Maintenance Reference Guide.

216 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

"

Observation Measurements Observation measurements are immediately sent from the Local Data Collector to the Measurement Administrator, by passing the Central Data Collector. The counter types range from 10 to 15.

"

Status Inspection Status inspection is provided on demand from the Central Data Collector, on the number of open radio channels. The Central Data Collector polls the Local Data Collectors every 20 seconds. The counter type is 2.

If a particular control board becomes inoperable, the Local Data Collector running within this control board is unavailable. This occurs when the subsystem remains inoperable. The Measurement Administrator is responsible for scheduling jobs, and for providing results to the OMC R. The Measurement Administrator treats the demands of active raw measurement jobs by accessing the Central Data Collector for the information, and then passing the information on to the OMC R. This check is done every five minutes. Figure 76 shows the data collectors in the BSC.
BTS BSC TSS

TCU FU

SYS CPRA

DTC TC

Local Data Collector

Local Data Collector

Local Data Collector

OSI CPRA TCU FU

Central Data Collector Measurement Local Data Administrator Collector

Local Data Collector

Figure 76

Data Collectors within the BSC

3BK 02974 AAAA TQZZA Ed. 07

217 / 240

8 Operations & Maintenance

8.6.5

Counter Examples
The following examples show how the mediated device counters are mapped down to basic raw measurements types. Two measurement operations are performed for requested type 1 and type 5 raw measurements. Figure 77 shows an example of the counter object tree required for each job.

Job1

Job1 requests the average TCH hold time per BTS (PR27), and the number of successful seizures (PR18) results from two Mediated Device Counters. Counter PR27 = C38/(C17+C18). Counter PR18 = C1+C2+C10.

Job2

Job2 requests a Mediated Warning of the number of SDCCH radio losses (RD28). Counter RD28 = C6+C7. All the above counters are type 1 counters, except C38 which belongs to type 5.

Note

Refer to the Operation & Maintenance Reference Guide for more information about counter types and definitions.

218 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

mediated device object

mediated meas

JOB1

mediated JOB2 warning

mediated device counter

PR27

PR18

RD28

virtual raw measurement

T1

T5

T1

T1

raw measurement handler

Rm (T1)

Rm (T5)

OMC R BSC Rm (T1) Rm (T5)

Figure 77

Example: Counter Object Tree

3BK 02974 AAAA TQZZA Ed. 07

219 / 240

8 Operations & Maintenance

8.7

Audits
Audits can be automatic or invoked by an operator. They can be performed at several levels:
" "

From the OMC R to the TSC or the BSC From the BSC to the BTS.

Audit Types
Table 19
Type Clock Audit Logical Audit

There are several types of audits, as described in Table 19.

Audit Types
Description Clock audits synchronize the clocks to the master date and time. A logical audit is performed on logical parameters. The logical parameters include dynamic cell information, its power ratings, information on adjacent cells, the radio configuration of the cell, and hopping and paging groups. The software version audit controls the versions of software that exist on the subsystem. Hardware audits control the hardware on the subsystem. This audit provides a physical list of all components in the subsystem, their SBLs, and their associated RITs. The OMC R updates the database with this information. The OMC R requests the AIFL from a unit of the BSS. The OMC R then compares this with its own list and updates its database if there are any differ ences. A state audit checks the state of SBLs on a particular subsystem, to ensure that SBL databases are synchronized. All the SBLs and their states are compared with the data in the OMC R. If the SBL does not exist in the database, it is created and its state is registered.

Software Version Audit Hardware Audit

Alarm Audit

State Audit

A suite of audits is automatically invoked by the OMC R or the BSC, to resynchronize the system. This is done:
" "

To perform a RESET/RESTART. When there is a loss of links between subsystems. This ensures that the system databases are synchronized after autonomous operation while the link was down (i.e. the BTS_O&M was disabled). To make changes in the databases, without the possibility of aligning both subsystems. To start a BSC Alarms in Force audit if the BSC alarm queue overflows. To perform software database replacement.

"

"

"

Audit information for the whole system is stored in the OMC R and is stored in the Management Information Base (MIB).

220 / 240

3BK 02974 AAAA TQZZA Ed. 07

8 Operations & Maintenance

Audit Flow

Audit flow is based on an action request from the OMC R, or on an automatic request. The subsystem receiving the audit request performs an audit of its functional units. The reply can have one or several report messages to pass the information back to the request originator. The request originator can generate more actions based on the information received. For example, when the state of the CU and its pair FU do not match, the BSC or OMC R disables the FU/CU pairs. The OMC R, on reception of the audit report, updates its database. During download the results of the software audit are used to provide the list of modules the OMC R needs to update the BSS subsystem. This is done by comparing the OMC R lists of modules to transfer, and their version numbers, to see if they already exist in the subsystem. Only the newer versions are transferred to the subsystem.

3BK 02974 AAAA TQZZA Ed. 07

221 / 240

8 Operations & Maintenance

8.8

Modifying Telecom Parameters


Modification of telecom parameters occurs:
"

On the BSC The BSC database is updated with the modifications. On the BTS The BSC informs all of the BTSs affected by the changes, using the following commands to change the telecom parameters:
D D

"

BCCH_INFO(SYS_INFO 1 4) to BCCH FU SCCH_FILL(SYS_INFO 5,6) to all FUs.

222 / 240

3BK 02974 AAAA TQZZA Ed. 07

Abbreviations

Abbreviations
ACCH ACELP AGCH AIFL AN AuC BCB BCCH BER BIE BS BSII BSS BSSAP BSSMAP CACO CBCH CCCH CCH CDM CI CIC CM CMISE CPF CPR CPRA CU DCCH DRX DTAP Associated Control Channel Algebraic Code Excited Linear Prediction Access Grant Channel Alarms In Force List Antenna Network Authentication Center Base Station Control Bus Broadcast Control Channel Bit Error Rate Base Station Interface Equipment Base Station Base Station Internal Interface Base Station Subsystem BSS Application Part BSS Management Application Part Call Control Cell Broadcast Channel Common Control Channel Control Channel Configuration Data Message Cell Identity Circuit Identification Code Call Management Common Management Information Service Element Configuration Parameter Data File Common Processor Common Processor Type A Carrier Unit Dedicated Control Channel Discontinuous Reception (mechanism) Direct Transfer Application Part

3BK 02974 AAAA TQZZA Ed. 07

223 / 240

Abbreviations

DTC DTE DTX DTX/VAD EACB EF EFR EIR ETSI FACCH FCCH FDMA FH FHS FHU FIT FLT FOS FTAM FU FU_TS GSM HLR HMI HSN ID IE IMEI IMSI ISDN ISO IT ITU

Digital Trunk Controller Data Terminal Equipment Discontinuous Transmission (mechanism) Discontinuous Transmission/Voice Activity Detection External Alarm Collection Board External Fault Enhanced Full Rate Equipment Identity Register European Telecommunication Standards Institute Fast Associated Control Channel Frequency Correction Channel Frequency Division Multiplex Access Frequency Hopping Frequency Hopping System Frequency Hopping Unit Faulty In Traffic Faulty Faulty Out of Service File Transfer Access and Management Frame Unit Frame Unit Time Slot Global System for Mobile Communications Home Location Register Human Machine Interface Hopping Sequence Number Identification Information Element International Mobile Station Equipment Identity International Mobile Subscriber Identity Integrated Services Digital Network International Standards Organization In Traffic International Telecommunications Union

224 / 240

3BK 02974 AAAA TQZZA Ed. 07

Abbreviations

Kc Ki L2ML LA LAC LAI LAPD LAPDm MA MAIO MCC MCLU MIB MIE MIT MM MNC MS ms MSD MTP NEQ NMC NSS NTC O&M OMC R OML OMU OPR PBGT PCH PCM

Ciphering Key Individual Subscriber Authentication Key Layer 2 Management Link Location Area Location Area Code Location Area Identity Link Access Procedure on the D Channel Link Access Protocol on the Dm Channel Mobile Allocation Mobile Allocation Index Offset Mobile Country Code Master Clock Unit Management Information Base Mandatory Information Element Management Information Tree Mobility Management Mobile Network Code Mobile Station milliseconds Maintenance Seized (due to an operator action) Message Transfer Part Not Equipped Network Management Center Network Subsystem Night Time Concentration Operations and Maintenance Operations and Maintenance Center Radio Operations and Maintenance Link Operations and Maintenance Unit Operator Out of Service Power Budget Paging Channel Pulse Code Modulation

3BK 02974 AAAA TQZZA Ed. 07

225 / 240

Abbreviations

PLMN PM PSTN RACH RAND REF RF RIT RLP RPC RR RRM RSL RTE LTP RTS RXLEV RXQUAL SABM SABME SACCH SBL SCCP SCH SCP SDCCH SID SIM SM SMS SMS CB SOS SS SS7

Public Land Mobile Network Performance Management Public Switched Telephone Network Random Access Channel Random Number (used for authentication) Random Access Information Value Radio Frequency Replaceable Item Radio Link Protocol Radio Power Control Radio Resource Radio Resource Management Radio signaling Link Radio Test Equipment Long Term Prediction Radio Time Slot Received Signal Level Received Signal Quality Set Asynchronous Balanced Mode Set Asynchronous Balanced Mode Extended Slow Associated Control Channel Security Block signaling Connection Control Part Synchronization Channel Signalling Control Processor Stand alone Dedicated Control Channel Silence Indication Subscriber Identity Module Submultiplexer Short Message Service Short Message Service Cell Broadcast Software Out of Service Supplementary Service signaling System No. 7

226 / 240

3BK 02974 AAAA TQZZA Ed. 07

Abbreviations

SUM S CPRA TC TCH TCH/F2.4 TCH/F4.8 TCH/F9.6 TCH/FS TCH/H2.4 TCH/H4.8 TCH/HS TCU TDM TDMA TEI TMN TMSI TOA TRAU TRE TS0 TSC TSL TSS UT VAD VLR WTC

Station Unit Module System Common Processor Type A Transcoder Traffic Channel A Full Rate Data TCH (<2.4 Kbit/s) Full Rate Data Traffic Channel (4.8 Kbit/s) Full Rate Data Traffic Channel (9.6 Kbit/s) A Full Rate Speech TCH A Half Rate Data TCH (<2.4 Kbit/s) A Half Rate Data TCH (4.8 Kbit/s) A Half Rate Speech TCH Terminal Control Unit Time Division Multiplex Time Division Multiple Access Terminal Endpoint Identifier Telecommunications Management Network Temporary Mobile Subscriber Identity Time Of Arrival Transcoder Rate Adapter Transceiver Equipment Time Slot 0 Transcoder Submultiplexer Controller TSC LAPD Signalling Link to the BSC Transmission Subsystem Under Test Voice Activity Detection Visitor Location Register Wait Traffic Clear

3BK 02974 AAAA TQZZA Ed. 07

227 / 240

Abbreviations

228 / 240

3BK 02974 AAAA TQZZA Ed. 07

Appendix A Air Interface Channels

Appendix A
A.1 TCH A.2

Air Interface Channels


Traffic Channel Full Rate: used on the uplink and downlink to transmit user traffic. The TCH uses 24 out of 26 sequential slots on its channel to transmit speech or data.

Traffic Channels

Broadcast Channels FCCH SCH BCCH


Frequency Correction Channel: used on the downlink (on the BCCH timeslot) for frequency correction of the MS with the BTS. Synchronization Channel: used on the downlink (on the BCCH timeslot) for frame synchronisation of the MS with the BTS. Broadcast Control Channel: used to broadcast system information to the MSs on the downlink, to give the cell configuration and how to access the cell.
" " " " " " " "

Number of CCCHs Whether CCCHs are combined with SDCCHs ACGH allocation Paging Organization CGI, LAI Cell Allocation BCCH frequencies of neighbor cells Maximum transmit power, which is allowed in the cell.

A.3

Common Control Channels CCCH RACH AGCH PCH


Common Control Channel: for control information before a dedicated channel is assigned. It comprises the RACH, AGCH and PCH. Random Access Channel: used on the uplink (on the CCCH timeslot) by the MS for initial access to the network. Access Grant Channel: used on the downlink (on the CCCH timeslot) gives to the MS access information before a dedicated channel is assigned. Paging Channel: used on the downlink (on the CCCH timeslot) for paging messages to the MS.

3BK 02974 AAAA TQZZA Ed. 07

229 / 240

Appendix A Air Interface Channels

A.4

Dedicated Channels SDCCH CBCH


Signalling Dedicated Channel: used for signalling and short message information. Cell Broadcast Channel: uses an SDCCH channel but all MSs will then know it is for Short Message Service Cell Broadcasts.

A.5

Associated Channels SACCH FACCH


Slow Associated Control Channel: associated with a TCH, which uses 1 out of 26 slots for signalling purposes. Fast Access Control Channel: associated with a TCH, and can steal slots out of 24 of 26 slots which are normally dedicated to the TCH for signalling purposes as well as the SACCH slot.

Traffic =

TCH

SACCH

FACCH

Broadcast =

FCCH

SCH

BCCH

Common =

RACH

AGCH

PCH

Dedicated =

SDCCH

KEY

Uplink Downlink

Figure 78

Channels and Their Direction of Flow

230 / 240

3BK 02974 AAAA TQZZA Ed. 07

Index

Index A
A interface, 41 A law, speech encoding, 167 Abis interface, 42 Abis Signalling Links Static Multiplexing, 25, 159 Access to PM Raw Counters via Binary Files, 26, 162 Air interface, 43 Alarms, 194 audit, 220 BSC, 195 BTS, 199 filtering, 195 generation, 194 in force, 195 mediated warning, 213 queue BTS, 200 status, 190 TSC, 200 Alcatel, EVOLIUM Radio Solutions, 18 Alcatel BSS Features, 23, 146 Alerter, BSC, 24, 156 Algorithms encryption, 72 handover, 99 hopping, 137 Antenna diversity, 23, 147 pre amplifier, 23 Asynchronous, handover, 100 Ater interface, 42 Audits, 220 Authentication, 77 centre, 32 identities, 77 Ki value, 77 procedure, 78 random number, 77 Auto Identification, BTS, 26, 160 Automatic Paging Repetition, 26, 161 Automatic Power Down, BTS, 26, 160

B
Base Station Control Bus, 188, 199 Base Station Controller. See BSC Base Station Interface Equipment, 29 Base Station Internal Interface, 188, 199 Base Station Subsystem. See BSS Base Tranceiver Station. See BTS Board, operation, 201 Boot strap, 201 BSB, 188, 199 BSC alarms, 195 alerter, 24, 156 call release, 122 data collection, 216 description, 28 O&M role, 184 OMC R/BSC command flows, 191 overload detection, 108 BSII, 188, 199 BSS description, 27 features, description, 129 features, overview, 21, 130 functions, 19 O&M functions, 184 SBL Operator Commands, 205, 206 BTS alarm queue, 200 alarms, 199 auto identification, 26, 160 automatic power down, 26, 160 call release, 124 description, 28 O&M role, 186 188 overload detection, 107 power control, 132 power level, 135 queue, 69 sectored site, 175 TC alarms, 127 BTS A9100, TRE SBL, 207

3BK 02974 AAAA TQZZA Ed. 07

231 / 240

Index

BTS_TEL, 196, 207, 208

C
Call See also call handling, release, set up connecting, 60 control, 39 mobile originated, 50 mobile terminated, 61 mobility management, 48 quality, 89 re establishment by MS, 22, 143 release, 111 service, 48 setup, 19 tracing, 211 types, 48 user traffic, 48 Call handling, 20 error handling, 88 Call release, 20, 111 128 channel change, 119 procedures in normal service, 114 resources, 112 SCCP 115 , special cases, 120 BSC initiated, 122 BSC initiated SCCP release, 123 BTS initiated, 124 BTS initiated LAPD failure, 124 MS initiated, 126 MS initiated radio link failure, 126 reset, 120 reset circuit, 120 Call set up, 19 authentication, 49, 55 channel activation, 52 ciphering, 49, 55 immediate assignment, 53 normal assignment, 49 phases, 49 radio and link establishment, 49 Calls mobility management, 19 supplementary service, 19 user traffic, 19

Cell concentric, 174 environments, 23, 146, 171 extended, 176 hierarchical network, 178 list identifier, 66 list information element, 66 macrocell, 178, 179 microcell, 179 mini cell, 178 sectored site, 175 target evaluation, 99 target list, 91 type, 172 types, 23, 146 umbrella, 178 Cellular Environment, 21, 131 Channels activation, 52, 58 allocation, traffic, 57 control, 44 interference levels, 91 traffic, 44 Ciphering, 79 BSS capability, 80 encryption algorithms, 79 handover, 82 keys, 80 Mobile Station capability, 79 mode, 81 procedure, 81 Classmark handling, 72 information element, 72 procedure, 55 updating, 74 Clipping, 139 Clock audit, 220 Communication, mechanism, 191 Concentric cell, 174 zones, 174 Configuration download, 201 SW management, 190 Congestion, 69 Contention resolution, 53 Control channel, 44

232 / 240

3BK 02974 AAAA TQZZA Ed. 07

Index

Correlation, 194 Counters, 213, 214 cummulative, 216 mediated device, 214

DTX, discontinuous transmission, 22, 138

E
EFR. See Enhanced Full-Rate Encryption A5/1, 72 74 A5/2, 73 algorithm, 72 74 Enhanced Full Rate, 23, 44, 144 Equipment Identity Register, 32 Erlangs, 213 Error, persistancy, 195 Event, changes, 193 EVOLIUM Radio Solutions, 18 Extended cell, 176 overlap zone, 176 External components, 31 handover, 89, 100 handover procedure, 104

D
Daisy chain, map, 195 Data central collector, 216 collection, BSC, 216 handling, 168 interleaving, 169 non transparent, 170 rate adaptation, 169 transparent, 169 V.110 protocol, 168 Data link layer A interface, 41 Abis interface, 42 Air interface, 43 Device counters, mediated, 214 Directed retry, 70 handover, 90 Disable, 202 Discontinuous reception, 142 Discontinuous transmission, 138 downlink, 139 flag, 139 uplink, 140 Distance, handover, 96 Download configuration, 201 software, 201 DRX, discontinuous reception, 22, 142 DTC, 197 failure, 195 overload action, 108

F
Fading, 136, 147 Failure DTC, 195 link, 196 software, 197 TCU, 195 Fault begin / end, 194 correlation, 194 Fax data rate change, 87 non transparent, 87 transparent, 87

3BK 02974 AAAA TQZZA Ed. 07

233 / 240

Index

Features Abis signalling links static multiplexing, 25, 159 access to PM raw counters via binary files, 26, 162 antenna diversity, 23 antenna pre amplifier equipment, 23 auto identification, 26 automatic paging repetition, 26, 161 automatic power down, 26 BSC Alerter, 24 BSS, 21, 129, 130 call re establishment by the MS, 22 cellular environment, 21, 131 discontinuous reception, 22 discontinuous transmission/voice activity detection, 22 enhanced full rate, 23 frequency hopping, 22 improved multipath delay equalization, 24 minimum frequency spacing, 24 multiple human machine interface, 24 night time concentration, 24 OMC NSS session from OMC R terminal, 25 OMC R connection to TSC trough BSC, 25, 158 power control due to radio link failure, 25, 158 Q3 multimanager, 25, 158 rpc uplink and downlink, 22 short message service - cell broadcast, 22 transcoder pools, 26, 159 types of cell environments, 23, 146 usage state on demand, 24 X.25 redundancy, 24 Features Defined in the GSM Recommendations, 21, 131 Features, Service Improvement in Alcatel BSS, 23, 146 new, 25, 158 Filtering, alarms, 195 Flag, DTX, 139 Frequency carrier spacing, 24 diversity, 136 hopping, 22, 135 MAIO, 136

Functions BSC O&M, 184 BSS, 19 BSS O&M, 184 BTS O&M, 186 188 call setup, 19 operations & maintenance, 21 telecommunications, 39 TSC O&M, 188

G
GSM features defined in, 21, 131 system functions, 19

H
Handover, 89 alarm, 91 algorithm, 99 asynchronous, 100 better cell, 95 better zone, 94 ciphering, 82 directed retry, 70, 90 external, 90 internal, 90 distance, 96 external, 89, 100 interBSS, 100 intercell, 100 internal, 89, 100 intracell, 100 level intercell, 93 margin, 99 micro to macrocell, 179 microcell, 92, 179 mobile velocity dependent, 97 power budget, 95 preparation, 91 quality and level, 92 quality intercell, 94 quality intracell, 94 queueing, 69 synchronous, 100 Hardware audit, 220 Hierarchical network, cells, 178 Home Location Register, 32

234 / 240

3BK 02974 AAAA TQZZA Ed. 07

Index

Hopping frequency, 135 sequence number, 136 Human Machine Interface, 24, 149 site configuration, 150

L
LAPD, failure, 124 LAPDm, disconnect, 127 Layers Call Management, 39 data link A, 41 data link Abis, 42 data link Air, 43 Mobility Management, 40 physical A, 41 physical Abis, 42 physical Air, 43 Radio Resource Management, 40 Level intercell, handover, 93 Location Area Identity, 34 Location updating, 34 Logical audit, 220

I
Immediate assignment, 53 SCCP connection, 54 IMSI Attach Detach, 49, 64 IMSI tracing, 212 In call modification, 85 procedure, 86 types, 85 Information element, mandatory, 116 Init, 202 InterBSS, handover, 100 Intercell, handover, 100 Interface A, 41 Abis, 42 Air, 43 Ater, 42 Q3, 38 Multimanager, 25, 38, 158 Interference, 130 Internal handover, 89, 100 handover procedure, 101 Intracell, handover, 100

M
Macrocell, 178, 179 Management, network, 37 Margin, handover, 99 Measurements administrator, 214 BSC, 214 BTS power, 132 counters, 214 job classes, 213 mediated, 213 OMC R, 214 radio, 90 radio link, 132 raw, 213 results, 214 virtual raw, 214 Mediated Device Counters, 214

J
Jobs, snapshot, 213

3BK 02974 AAAA TQZZA Ed. 07

235 / 240

Index

Mediated Device Objects, 214 Mediation, 214 Messages alerting, 60, 63 assign failure, 57 assignment command, 59 assignment complete, 59 assignment failure, 57, 69 assignment request, 57 authentication reject, 78 authentication response, 78 block, 120 BTS power control, 135 call confirmation, 62 call proceeding, 55 channel activation, 52, 58 channel release, 117 channel request, 50 channel required, 52 cipher mode, 81 cipher mode complete, 81 cipher mode reject, 81 classmark change, 74 classmark enquiry, 74 classmark request, 74 classmark update, 74 clear command, 116 clear complete, 116 connect, 60 connection, 63 deactivate SACCH, 117 disconnection, 115 encryption command, 81 establish indication, 54, 59 handover command, 102 handover complete, 102 handover detect, 105 handover detection, 102 handover performed, 102 immediate assign, 53 IMSI attach detach, 49 measurement report, 90, 132 measurement result, 90, 132 mode modify, 86 modify, 86 paging, 61, 66 paging command, 61, 66 paging request, 61 paging request type x, 67 paging response, 61, 66 permitted algorithm, 81

physical context confirm, 58 physical context request, 58 power command, 135 queueing indication, 70 release indication, 117 reset, 120 reset circuit, 120 RF channel release, 118 RF resource indication, 57 SCCP connection confirm, 54 SCCP connection request, 54 SCCP release complete, 116 SCCP released, 116 service request, 54 set up, 62 setup, 55 system information, 46 Microcell, 179 handover, 179 thresholds, 179 Mini cell, 178 Mobile, velocity dependent handover, 97 Mobile allocation, 136 Mobile Allocation Index Offset, 136 Mobile originated call, 50 Mobile services Switching Center. See MSC Mobile Station. See MS Mobile terminated call, 61 Mobility Management, 40 Mobility management calls, 19 MS allocation, 136 call re establishment, 22, 143 call release, 126 cell selection, 33 ciphering capability, 73 class barring, 109 classmark, 72 description, 32 idle mode, 33 location updating, 34 phase 2 support, 142 power control, 132 power drain, 130 revision level, 73 RF power level, 73

236 / 240

3BK 02974 AAAA TQZZA Ed. 07

Index

MS BS, absolute distance, 133 MSC, description, 32 Multiframe, 43 Multipath Delay Equalization, 24

OMC R Connection to TSC Through BSC, 25, 158 Operations & Maintenance, 21 Operations and maintenance, 183 Operations and Maintenance Center Radio. See OMC R Overload BSC detection, 108 BTS detection, 107 control, 107 DTC action, 108 MS class barring, 109 TCU action, 108

N
Network, management, 37 Network Management Center. See NMC Network Subsystem, 31 New Service Improvement Features, 25, 158 Night Time Concentration, 24, 151 NMC, 27, 37 Non transparent data, 170 Fax Group 3, 87 Normal assignment mobile originated call, 55 mobile terminated call, 62

P
Paging, 65 cell list identifier, 66 messages, 61 procedure, 61 request types, 67 Parameters, modification, 222 PBGT, handover, 95 Persistancy, 195 Phase 2, MS support, 142 Physical layer A interface, 41 Abis interface, 42 Air interface, 43 Power budget, handover, 95 Power control BTS, 132 decision, 133 handover, 133 MS, 132 radio, 131 reasons, 131 RXLEV, 134 RXQUAL, 134 Power Control due to Radio Link Failure, 25, 158 Power level, BTS, 135

O
O&M BSC role, 184 BTS role A9100, 187 G1 & G2, 186 command flow, 191 communication mechanism, 191 counters, 213 data collection, 216 observation measurements, 216 OMC R role, 190 TSC role, 188 OMC R description, 36 HMI access, 149 measurement job classes, 213 O&M role, 190 OMC NSS Session from OMC R Terminal, 25

3BK 02974 AAAA TQZZA Ed. 07

237 / 240

Index

Procedure, classmark, 55 Procedures authentication, 78 call release, 111 channel activation, 52 ciphering, 81 classmark, 75 external handover, 104 frequency hopping, 136 immediate assignment, 53 in call modification, 86 internal handover, 101 normal assignment, 55, 62 paging, 61 physical context, 58

Reporting, periods, 133 Reset, 202 call release, 120 circuit, 120 Resource usage, on demand, 24, 155 Restart, 202 RSL, 197 RXLEV, power control, 134 RXQUAL, power control, 134

S
SBL, 184, 205, 210 BTS_TEL, 196, 207, 208 DTC, 197 RSL, 197 states, 201 205 TRE in BTS A9100, 207 SCCP release, 115, 123 , Sectored site BTS, 175 cells, 175 Self test, 201 Service Improvement Features, 23, 146 new, 25, 158 Short Message Service, cell broadcast, 22, 144 Signal quality, 133 strength, 133 Silence Indication, discontinuous transmission, 138 Snapshot, jobs, 213 Software download, 201 failure, 197 start, 201 Software version audit, 220 Speech A law encoding, 167 digital encoding, 165 error correction, 165 handling, 165 interleaving, 165 multiplexing, 166 Spontaneous messages, 193

Q
Q1 Interface, 199 Q3 Interface, 38 Multimanager, 25, 38, 158 Quality, handover, 92 Quality intercell, handover, 94 Quality intracell, handover, 94 Queueing, 69 in queue, 69 priority, 70

R
Radio link failure, 126 link measurements, 132 measurements, 90 power control, 22, 131 resource release, 116 Radio and link establishment, 50, 61 Radio Resource Management, 40 Rate adaptation, 169 Raw, counters, 213 Reception, discontinuous, 142 Release See also Call release MSC normal, 115 radio resource, 116

238 / 240

3BK 02974 AAAA TQZZA Ed. 07

Index

State audit, 220 States In Traffic, 203 not In Traffic, 204 Status changes, 201 inspection, 216 Submultiplexer, 29 Subscriber identity module, 32 Supplementary services, calls, 19 Synchronous, handover, 100 System information messages, 46

Transcoder Submultiplexer Controller. See TSC Transmission discontinuous, 138 subsystem, 29 Transparent data, 169 Fax Group 3, 87 TSC, 29 alarms, 200 O&M role, 188 TSS, Transmission Subsystem, 29 Types of Cell Environments, 23, 146

T
Target cell evaluation, 99 list, 91 TC, 29 alarms, 127 TCU failure, 195 overload action, 108 Telecom, parameter modification, 222 Telecommunication layers Application, 39 Transmission, 39 Telecommunications Management Network. See TMN Temporary Mobile Subscriber Identity, 35 Terminal Control Unit. See TCU Thresholds, microcell, 179 Timing advance, 133 TMN, 37 Token bus, 199 Tracing call, 211 IMSI, 212 Traffic channel, 44 Transcoder. See TC Transcoder Pools, 26, 159

U
Umbrella, cell, 178 Usage state, on demand, 24, 155 User traffic, handling, 163 User traffic calls, 19

V
V.110 protocol, 168 Virtual Raw Measurements, 214 Visitor Location Register, 32 Voice Activity Detection, discontinuous transmission, 22, 139

W
Warning, mediated, 213

X
X.25 redundancy, 24, 153 link transfer, 154

Z
Zones concentric cell, 174 overlap, extended cell, 176

3BK 02974 AAAA TQZZA Ed. 07

239 / 240

Index

240 / 240

3BK 02974 AAAA TQZZA Ed. 07

C o v e r
Status Class_1 Class_2 Short Title Released Alcatel 900/1800 BSS Descriptive Document System Description

S h e e t
Class_3 Class_4 Doc ID System Guide

Main_Title Sub_Title DOCC MMCC

System Description

CRN No

History
Edition Date Change Note Operator: Comp. Dept. Name Originator: Comp. Dept. Name Appraisor: Comp. Dept. Name CITVY GCD D. L CITVY GCD D. L CITVY GCD D. L CITVY GCD-C M.Ridealgh CITVY GCD R.Gallon CITVY GCD R. Gallon CITVY GCD-C M. Ridealgh CITVY GCD R. Gallon CITVY GCD R.Gallon 01 950401 06 980130 07 980519

External History of Last Edition

Internal History of Last Edition


New Edition for release 4.2. Added features, reorga nized chapters 1 and 5.

3BK 02974 AAAA TQZZA Ed. 07

1 / 240

C o v e r
Distribution List
Internal Code company code Site 1 External Code department

S h e e t
chars name full name 5/12/15

Abstract

Review

3BK 02974 AAAA TQZZA Ed. 07

You might also like