Escolar Documentos
Profissional Documentos
Cultura Documentos
Descriptive Documentation
BSS Concepts
Status RELEASED
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2 BSS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2.1 Call Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
1.2.2 Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.3 Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.2.4 Operations & Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3 BSS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3.1 Base Station Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
1.3.2 Base Transceiver Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.3 Transcoder And Transmission Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
1.3.4 The Multi-BSS Fast Packet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
1.3.5 Multi-GPU per BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.4 Extended GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.5 External Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
1.5.1 Network Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
1.5.2 Mobile Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
1.5.3 Phase 2 Mobile Support in a Phase 1 Infrastructure . . . . . . . . . . . . . . . . . . . . . . . 33
1.5.4 Operations and Maintenance Center-Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.6 Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.6.1 Telecommunications Management Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.6.2 Q3 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
1.7 BSS Telecommunications Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.7.1 Call Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.7.2 Mobility Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.7.3 Radio Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1.7.4 The A Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1.7.5 The Abis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.7.6 Satellite Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.7.7 The Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
2 GPRS in the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.1.1 Packet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
2.1.2 GPRS Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.2 GPRS Channels and System Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.2.1 Master Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.2.2 Static Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
2.2.3 Dynamic Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.2.4 Multiple PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
2.2.5 Logical Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.2.6 Virtual Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
2.2.7 System Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.3 GPRS Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.3.1 The Gb Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
2.3.2 The BSCGP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.3.3 The GCH Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
2.4 GPRS Network Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.4.1 Mobility Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
2.4.2 Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.4.3 Radio Power Control and Radio Link Measurement . . . . . . . . . . . . . . . . . . . . . . . . 64
2.5 Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
2.5.1 Time Slot Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figures
Figure 1: BSS in the PLMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Figure 2: Antenna Diversity on G1 and G2 BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Figure 3: Antenna Diversity on the BTS A9100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Figure 4: Transmission Components in the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Figure 5: Cell Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 6: Logical Position of External Components Associated with BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Figure 7: Location Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 8: TMN System Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 9: General Telecommunication Layers within GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 10: BSS Application, Transmission Layers and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Figure 11: Time Slot 4 of a Time Division Multiple Access Frame Supporting Access Grant Channels . . . 41
Figure 12: Model LLC Packet Data Unit used in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 13: The Alcatel GPRS solution in the PLMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Figure 14: GPRS Traffic Load Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 15: GPRS Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 16: Mobile Station-Originating Packet Data Protocol Context Activation . . . . . . . . . . . . . . . . . . . . . . . . 74
Figure 17: GGSN-Originating Packet Data Protocol Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Figure 18: Mobile-Originated Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 19: Mobile-Terminated Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 20: Mobile Station Originating Packet Data Protocol Context De-activation . . . . . . . . . . . . . . . . . . . . . 78
Figure 21: Network-Originating Packet Data Protocol Context De-activation Processes . . . . . . . . . . . . . . . . 79
Figure 22: GPRS Suspend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Figure 23: GPRS Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 24: Mobile Station-Originating GPRS Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 25: Network-Originating GPRS Detach Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 26: Radio and Link Establishment for Mobile Originated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 27: SDCCH Channel Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 28: Immediate Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 29: Connection for Mobile Originated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 30: Normal Assignment for Mobile Originated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Figure 31: Channel Activation Process for the Traffic Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 32: Channel Assignment Process for the Traffic Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 33: Call Connection for Mobile Originated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 34: Radio and Link Establishment for Mobile Terminated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 35: Normal Assignment for Mobile Terminated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 36: CCCH with Three Blocks Reserved for AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 37: Four TDMA Frame Cycles Providing 24 Paging Sub-channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 38: Paging Message Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Figure 39: Location Update with Classmark Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Figure 40: Location Update with Mobile Station Sending Location Area Identity of Previous VLR . . . . . . . 123
Figure 41: Ciphering Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Figure 42: Example of TFO Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Figure 43: Frequency Hopping within an FHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Figure 44: Different Forms of Discontinuous Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Figure 45: Power Control Flow of Measurement and Decision Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Figure 46: Power Output Balancing Based on Received Quality and Signal Levels . . . . . . . . . . . . . . . . . . . . 147
Figure 47: Quality and Level Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Figure 48: Better Zone Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Figure 49: Better Cell Handover (Power Budget) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Figure 50: Distance Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Figure 51: Umbrella Cell Load in Mobile Velocity Dependent Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Figure 52: Synchronous Internal Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Figure 53: Asynchronous External Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Figure 54: Mobile Station Disconnecting a Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Figure 55: Normal Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Figure 56: Initiation of Normal Release by MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Figure 57: BSC/BTS/Mobile Station interactions in Normal Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Figure 58: Normal Release Final Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Figure 59: Call Release Following a Channel Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Figure 60: Call Release Following Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Figure 61: BSC-initiated Call Release toward the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Figure 62: BTS-initiated Call Release following LAPD failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Figure 63: Call Release due to Mobile Station initiated Radio Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Figure 64: Call Release due to Communication Failure detected by Transcoder . . . . . . . . . . . . . . . . . . . . . . 190
Figure 65: Encoded Speech Transmission Across the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Figure 66: Multiplexed Ater Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Figure 67: Data Transmission Across the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Figure 68: Short Message Service - Cell Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Figure 69: Example: Cell Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Figure 70: Sectored site configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Figure 71: Example of Extended Cell Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Figure 72: Umbrella Cell with Mini Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Figure 73: Example: Handovers due to Threshold Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Figure 74: Indoor cell example network hierarchy with three layers and two bands . . . . . . . . . . . . . . . . . . . . 215
Figure 75: Multiple HMI Access to OMC-Rs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 76: ACO Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Figure 77: X.25 Without Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Figure 78: X.25 With Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 79: RSL Correlation on the Abis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Tables
Table 1: System Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Table 2: GPRS System Information Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Table 3: GPRS System Information Messages Used with MPDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Table 4: Gb Interface Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Table 5: BSCGP Interface Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Table 6: Network Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Table 7: Time Slot Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Table 8: PDCH Traffic Load States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Table 9: Types of Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Table 10: Call Set Up Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Table 11: Cell List Identifier and Paging Performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Table 12: Paging Request Message and Mobile Station Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Table 13: Classmark Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Table 14: Classmark Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 15: Mobile Station Ciphering Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Table 16: Downlink Discontinuous Transmission Status in Channel_activation . . . . . . . . . . . . . . . . . . . . . . . . 141
Table 17: Operator Discontinuous Transmission Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
Table 18: Radio Link Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Table 19: Mobile Station Maximum and Minimum Power Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Table 20: Circuit-Switched Data Rate Conversions Across the Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Table 21: Configuration Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Table 22: Fault Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Table 23: BTS Alarm Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Table 24: BTS Alarms Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Table 25: Performance Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Table 26: Audit Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Preface
Purpose This document provides detailed descriptions of the functions and features
of the Alcatel BSS. Some functions and features may not be available on
the system installed at your location.
The technical information in this document covers:
Audience This manual is for people requiring an in-depth understanding of the functions
of the Alcatel BSS:
Operations and support staff who need to know how the system operates in
normal conditions, including:
Operators
Support engineers
Maintenance staff
Client Help Desk personnel.
Assumed Knowledge The document assumes that the reader has an understanding of:
GSM
GPRS
Mobile Telecommunications
1 Introduction
This chapter gives a brief overview of the Alcatel BSS, its functions and
features. It describes:
Overview
BSS functions
1.1 Overview
The BSS provides radio coverage for GSM subscribers in a defined area. Its
principal role is to provide and support signalling and traffic channels between
mobile stations and the NSS.
The following figure shows the BSS within the PLMN, and its links to the PSTN
and the PSDN in a fixed network.
PLMN
MSC PSTN
TC
BTS BSC
MFS
SGSN PSDN
OMC−R
NMC
G2 BSC
G2 Transcoder
G2.5 Transcoder
BTS A9100
BTS A910
A935 MFS.
Extended GSM Band The Alcatel BSS supports the E-GSM band. E-GSM consists of:
(E-GSM) The 900 MHz primary band, called the P-GSM band. This uses 890-915
MHz for uplink, and 935-960 MHz for downlink.
The 900 MHz extended band, called the G1 band. This uses 880-890 MHz
for uplink, and 925-935 MHz for downlink.
GSM 850 The GSM 850 MHz band has been introduced in the Release 1999 of the 3GPP
Standard in 1999 to allow operators to replace progressively the D-AMPS and
CDMA technologies that were using these frequencies. Besides certain Asian
countries, the GSM 850 MHz band concerns in particular the Latin American
countries where many operators already use in their network the GSM system
with the GSM 1900 MHz to extend or replace their D-AMPS existing network.
The term GSM 850 is used for any GSM system which operates in 824 MHz to
849 MHz band for the uplink direction and in the 869 MHz to 894 MHz band for
the downlink direction. The GSM 850 band is defined by 124 absolute radio
frequency channel numbers (ARFCN) among the 1024 ARFCNs available in
the GSM standard.
Frequency Band The Alcatel BSS supports the following multiband network configurations:
Configurations BSS with a mix of GSM 850 and GSM 1900 cells
Call Set Up
Call Handling
Call Release
Mobility Management
Supplementary service
User traffic.
Mobility Management Mobility Management calls, such as location update, are used by the system
Calls to gather mobile station information. The exchanges are protocol messages
only. Therefore, only a signalling channel is used.
Supplementary Service Supplementary service calls, such as SMS, allows the mobile station to send
Calls and receive messages to and from the BTS. These calls pass small amounts of
information. Therefore, only a signalling channel is used.
User Traffic Calls 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
signalling channel. These calls use traffic channels.
Call set up processes include:
Handover when the quality of the current channel drops below an acceptable
level.
Ciphering to ensure data security on the Air Interface.
Special Cases:
Call release following a reset
BSC-initiated release
BTS-initiated release
Mobile station-initiated release.
Fault Management
Performance Management.
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.
Database management
Channel management
Operations and maintenance functions within the BSS
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 The A Interface (Section 1.7.4), The Abis
Interface (Section 1.7.5) and The Air Interface (Section 1.7.7).
For a more detailed description of the BSC, refer to the EVOLIUM BSC/TC
Overall Description document.
These families of BTS have different architectures, and are not functionally
identical, (e.g. only the BTS A9100 or BTS A910 can support GPRS).
The BTS performs the following functions under the control of the BSC:
Transmit and receive functions
Antenna diversity
Frequency hopping
The BTS also includes BIEs which enable it to communicate with the BSC over
the Abis interface. In the BTS A9100 and BTS A910, the BIE is integrated
into the SUM.
For a more detailed description of the BTS, refer to the BTS Functional
Description or the EVOLIUM BTS A9100/A910 Functional Description
documents.
TX
C
O
U
P
L
I
B F N
I FU H CU G
E U a
U RX
a N
a a I
T
ab
best of a&b
b b RX
b
b
(option)
OMU
TRE 1
best of a a
ab a&b
b ANT a
Tx / Rx
TRE 2
a
best of a
ab a&b
S b
U b
M
TRE 3
best of
ab ab b
a&b
a
TRE 4 b b
best of b ANT b
ab a&b a Tx / Rx
a
ANy ANx
ANC
BASEBAND BASEBAND RADIO RADIO
CONTROL COMBINING DUPLEXING
ANT : Antenna
ANx : Antenna Network Type x
ANy : Antenna Network Type y
SUM : Station Unit Module
TRE : Transmitter/Receiver Equipment
Figure 3: Antenna Diversity on the BTS A9100
Note: The configuration shown above (1 Sector, 3X4 Transceivers) is one example
only. Other combinations of Antennas and TREs are possible. There is no
antenna network y in the BTS A910, and the antenna network y is not needed if
the sector has two TREs.
TSC
OMC−R
MSC
TSC
BTS
PCU functions:
PAD function
Scheduling of packet data channels
Automatic Retransmission Request functions
Channel access control functions
Radio channel management functions.
The MFS converts GPRS frames, carried on multiple 16 kb/s links from multiple
BTSs, to one or more frame relay channels connected to the SGSN on the Gb
interface. See The Gb Interface (Section 2.3.1) for details of the Gb interface.
The set-up of Packet Data Channels is controlled by the MFS. It also negotiates
resources with the BSC and routes GPRS packets. When an additional channel
is required on a BTS, the MFS asks the BSC to allocate a channel and to
connect it to an Ater channel which the MFS controls.
The Alcatel solution also supplies two dedicated GPRS interfaces between the
MFS and the BSS:
Hardware and software management of the MFS is provided using the IMT.
The MFS is divided in GPRS processing units (GPU) which are inter-connected
via an Ethernet bus and controlled a control station. The GPU handles the
O&M and telecom functions of several cells, but a cell cannot be shared
between several GPUs.
A GPU cannot be connected to more than one BSC, which means that each
GPU cannot manage simultaneously several BSSs. However, the use of several
GPUs per BSS is required for traffic capacity reasons. The MFS is in charge of
associating each cell to a GPU. This later operation is called GPU cell mapping.
The GPU is in charge of:
O&M functions:
Initialization of the MFS
Software download
Software configuration
Performance monitoring.
Telecom functions:
Radio and transmission resources control
Radiolink control of packet connections
Common control channels management
MS radio resource control
Logical Link Control (LLC)
Protocol Data Unit (PDU) transfer
Multiframe management
Congestion control
Gb interface management
Signalling management on the GSL interface.
The GPU is split into two sub-units, the Packet Management Unit (PMU)
and the Packet Traffic Unit (PTU).
The protocols handled by a GPU are split in the following manner:
Protocols handled by the PTU:
Radio interface protocols (RLC and MAC)
GCH interface protocols (L2-GCH and L1-GCH).
The PTU manages the corresponding GCH interface (see The GCH
Interface (Section 2.3.3) for more information).
Protocols handled by the PMU:
Gb interface protocols (BSSGP, Network Service, and FR)
BSC interface protocols (BSCGP, L2-GSL, and L1-GSL)
RRM protocol.
The PMU manages the corresponding Gb and GSL interfaces.
Cell Mapping Mapping a cell means that a cell is associated to a GPU. Remapping a cell
means that a cell, already linked to a GPU, is moved to another GPU. The
mapping of cells onto GPUs is performed by the MFS, which actually defines
the mapping of cells onto LXPUs (logical GPU). An LXPU is either the primary
GPU, or the spare GPU in the case of switch-over. All the GPRS traffic of one
cell is handled by only one GPU. The following figure shows an example of
cell mapping.
MFS
Cell 1
Cell 4 Cell 2 GPU1
Cell 3
Cell 5
Cell 6 GPU2
Cell 7
BSC
Cell 8
Cell 12 Cell 9 GPU3
Cell 11
Cell 10
Cell 14
Cell 13
GPU4
E-GSM Mobile Station From messages sent by the mobile station, the BSS determines if a mobile
Recognition supports the E-GSM band.
The mobile station is determined to be E-GSM if:
The FC bit of the Classmark 2 is set to 1 (regardless of the value of the
Band 2 bit of the Classmark 3) or
The FC bit of the Classmark 2 is set to 0, and the Band 2 bit of the
Classmark 3 is set to 1.
E-GSM Management Once the E-GSM ability has been initially determined as described above, it
After Initial may happen that the mobile station radio characteristics change during a
Determination transaction. If the BSC receives a classmark change message, it takes this
into account and updates the E-GSM ability according to the content of the
received message.
E-GSM Determination In the case of internal handover, the E-GSM ability of a mobile station is
at Handover stored in the BSC memory. In the case of external incoming Handover, the
handover request message includes either Classmark 1 or Classmark 2 IE,
and optionally Classmark 3 IE. If Classmark 1 is present and Classmark 3 is
not present or Classmark 3 is present but does not contain the Band 2 bit,
the mobile station is not considered as E-GSM. If both Classmark 1 and
Classmark 3 are present, and Classmark 3 contains the Band 2 bit, the BSC
gets the E-GSM ability of the mobile station from the Classmark 3. If Classmark
2 is present and Classmark 3 is not present, or Classmark 3 is present but
does not contain the Band 2 bit, the BSC gets the E-GSM ability of the mobile
station from the Classmark 2 ("FC" bit). If both Classmark 2 and Classmark 3
are present, the mobile station is seen as E-GSM:
If the FC bit of the Classmark 2 is set to 1 (whatever the value of the band
2 bit of the Classmark 3)
If the FC bit of the Classmark 2 is set to 0 and the band 2 bit of the
Classmark 3 is set to 1.
TCH Allocation The allocation of G1 band channels can be done for Normal Assignment
(NASS), Internal Channel Change (ICC), or External Channel Change (ECC).
Each TRE has the capability to support the P-GSM or the E-GSM band. Each
TRX is configured as a P-GSM TRX or a G1 TRX. When a TCH is needed, if it
is for an E-GSM mobile station then a TCH belonging to the G1 TRX subset
is preferably chosen. If no resource is available in the G1 TRX subset, the
mobile station is allocated to the P-GSM TRX subset.
The following figure shows the logical position of the External Components.
PLMN
BTS BSC
MFS
BTS Gb Interface
SGSN GGSN PSDN
Abis
Interface
OMC−R HLR
NMC
MSC
Authentication Center
Equipment Identity Register
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.
Home Location Register 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 mobile station is located.
Visitor Location Register The VLR temporarily stores information about mobile stations entering its
coverage area. Linked to one or more MSCs, the VLR transmits data to a new
VLR when a mobile station changes areas.
Authentication Center The AuC manages the security data used for subscriber authentication.
Equipment Identity The EIR contains the lists of mobile station equipment identities.
Register
Phase 1
Phase 1 extended
Phase 2.
Mobile Station Idle Mode A mobile station is in idle mode when it is switched on, but not communicating
with the network on an SDCCH or a traffic channel. The BSS supports three
idle mode functions:
Overload control.
Mobile Station A mobile station monitors the broadcast messages from the BTS. This includes
Cell Selection and monitoring the FCCH and SCH.
Reselection The mobile station chooses the best cell on which to camp. If this cell is in a
location area other than that stored in the mobile station memory, then the
mobile station initiates a location update procedure. For a mobile station to
camp on a cell, it has to synchronize with the cell.
The BTS broadcasts an FCCH and an SCH at a defined time in the BCCH
cycle. These channels are used as reference points for the mobile station to
synchronize with the BCCH. Once synchronized, the mobile station continues
to monitor these channels to stay synchronized.
GSM/GPRS to UMTS The reselection of a UTRAN cell is triggered by a multi-RAT mobile station
Cell Reselection in circuit-switched idle mode, packet-switched idle mode, or packet-switched
transfer mode. In NC0 mode, a multi-RAT mobile station can reselect a
UTRAN cell in any GMM state. In dedicated mode, the multi-RAT mobile
station follows the GSM handover procedures. The BSS then broadcasts the
set of UTRAN cell parameters which allows the multi-RAT mobile station to
reselect a UTRAN cell on its own.
Location Updating The location update procedure is always initiated by the mobile station.
Location update is performed after the call has finished (cell reselection).
Reasons for location updates include:
A periodic update
Periodic location update is performed by the mobile station after a lack of
signalling activity for a specific time. If the timer expires, the mobile station
initiates a location update, even if it has not changed Location Area. The
duration of the mobile station timer is defined by the network and sent to the
mobile station as system information messages on the BCCH. The time can
be between six minutes and 25 hours.
The mobile station camps on a cell with a different location area code to the one
in the mobile station memory. The mobile station 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 signalling channel and
establishes a signalling path between the mobile station and MSC. See Mobile
Originated Call (Section 3.2) for more information.
When a signalling path is established, the mobile station sends the Location
Area Identity 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 Location Updating with Classmark Procedure (Section
3.6.3) and Authentication (Section 3.7).
The Location Area Identity is made up of:
Mobile Country Code
The BSS adds the cell identity of the mobile station current location to the
message sent to the MSC. This information is sent in a Mobility Management
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 to the mobile
station. See Authentication (Section 3.7) for more information about the TMSI.
The following figure shows a mobile station as it moves to a new location area.
Protocol Messages
Mobile MSC VLR
Station
BTS BSC
BSC
Phase 2 mobile stations send some phase 2 messages even though they
are in a phase 1 environment.
For example, phase 2 mobile stations send either new messages or new
elements in messages, which the phase 1 infrastructure could reject. This
blacklists the mobile station 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 messages/elements. The messages
can be either ignored or only partly treated. This is based on information
contained within the messages or elements.
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.
Network Element
MFS
BTS
BTS
BTS
1.6.2 Q3 Interface
Communication between the NMC and the OMC-R takes place across the Q3
Interface (see Figure 8). The Q3 protocols can be divided into the following
main areas:
Command types.
For further information on Network Management and the Q3 Interface see the
Operations & Maintenance Principles document.
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.
The following figure shows the general distribution of the telecommunication
functions within a GSM network.
MS BTS BSC NSS
CM
MM GSM
Application
Layers
RRM
TRANSMISSION
CM : Call Management
MM : Mobility Management
MS : Mobile Station
RRM : Radio Resource Management
Figure 9: General Telecommunication Layers within GSM
CM
GSM
MM Application
Layers
RRM
SCCP SCCP
LAPDm LAPDm LAPD LAPD Layer 2
SS7 SS7
08.60 TC
Air Interface Abis Interface A Interface
BSSAP : BSS Application Part
CM : Call Management
LAPD : Link Access Protocol on the D Channel
LAPDm : Link Access Protocol on the Dm Channel
MM : Mobility Management
RRM : Radio Resource Management
SCCP : Signal Connection Control Part
SS7 : Signaling System No. 7
TC : Transcoder
Figure 10: BSS Application, Transmission Layers and Interfaces
Terrestrial lines
Satellite link.
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. The actual physical link used depends on Network Operator
implementation.
Data Link Layer 2 Layer 2 provides the frame handling functions for the interface. It is also used to
pass signalling messages using the International Telecommunications Union
signalling System No. 7 protocol. This comprises:
Message Transfer Part, which provides the mechanism for reliable transfer
of the signalling messages
Application Sub-layer To transfer layer 3 messages relating to a transaction, the SCCP uses the BSS
RRM Application Part. This is divided into two parts:
Ater Interface The part of the A Interface between the Transcoder and BSC is known as the
Ater Mux Interface. The Ater Mux Interface is the result of multiplexing four Ater
Interfaces. Transcoding is a layer 1 process, therefore the difference between
the two interfaces is at the physical level.
Optimized Ater Interface This feature improves efficiency on the Ater Mux PCM connection between
Mapping the G2 BSC and the G2 Transcoder.
Four Ater Interfaces are submultiplexed onto the Ater Mux connection. This
interconnects four Digital Trunk Controllers and four Transcoder Rate Adaption
Units, achieving a 4:1 mapping.
The 4:1 mapping of the G2 BSC and G2 Transcoder allows up to 116 traffic
channels.
Physical layer 1
Data Link Layer 2 The data link layer provides frame handling and signalling functions using
the LAPD.
This layer supports three types of signalling links:
The Radio Signalling Link for signalling to the mobile station (including SMS)
Application Sub-layer The BTS management layer is used for layer 3 messages between the BSC
BTS and the BTS. Some of these messages are transparent to the BTS. These are
passed directly to the mobile station 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.
Modification of parameters is done from the OMC and propagated to the BSC
and the concerned BTSs. A new connection type parameter is associated to
each Abis link. The operator can set the parameter at Abis creation time. If
the satellite link is to be made using the Ater interface, the new connection
type parameter associated to Ater as a whole is used. Both Abis and Ater
connection types can be either terrestrial, or via satellite. The default value for
each is terrestrial.
Note: This is not a standard GSM feature and Alcatel cannot guarantee the
performance because there are so many unknown factors, such as error rate
and mobile population variations, which have significant effects because of
the delay.
Closed multidrop
PCM synchronization (the BTS must be configured as free running).
Physical layer 1
Data Link Layer 2 The data link layer provides frame handling and signalling functions, using
a modified version of the LAPDm.
Application Sub-Layer On the Air Interface, most of the layer 3 messages are transparent to the BTS.
Radio Resources The BTS uses layer 3 to extract certain information from some messages
Management 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 Ciphering (Section 3.8).
Air Interface Channels The Air Interface is divided by frequency and time, using Frequency-Division
Multiplex Access and Time Division Multiple Access. 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 Time Division Multiple
Access frames.
GPRS traffic uses the same radio resources as circuit-switched traffic, and
is carried on the same type of physical channel. Refer to GPRS in the BSS
(Chapter 2) for information on GPRS channels.
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.
The following figure shows time slot four of a TDMA frame supporting Access
Grant Channels.
A A A A A
G G G G G
C C C C C
H H H H H
Traffic Channels A traffic channel can be used for speech or data. The Alcatel BSS supports the
following types of traffic channels:
Speech:
Full-rate speech traffic channel
Enhanced full-rate speech traffic channel
Half-rate speech traffic channel.
Data:
Full-rate data traffic channel (9.6 Kbit/s)
Full-rate data traffic channel (4.8 Kbit/s)
Half-rate data traffic channel (4.8 Kbit/s)
Full-rate data traffic channel (<2.4 Kbit/s)
Half-rate data traffic channel (<2.4 Kbit/s).
Control Channels CCHs control communications between the BSS and the mobile stations.
There are three types of CCH:
The BCCH broadcast cell information to any mobile station in range. Three
channels use the BCCH time slot:
FCCH: used on the downlink for frequency correction of the mobile
station with the BTS
SCH: used on the downlink for frame synchronization of the mobile
station with the BTS
BCCH: used to broadcast system information to the mobile stations on
the downlink, to give the cell configuration, and how to access the cell.
The CCCH communicate with mobile stations in the cell before a dedicated
signalling channel is established. Three channels use the CCCH time slot:
RACH: used on the uplink by the mobile station for initial access to
the network
PCH: used on the downlink for paging messages to the mobile station
AGCH: used on the downlink to give the mobile station access
information before a dedicated channel is assigned.
The DCCH and ACCH pass signalling information for a specific mobile
station transaction. Two channels use the DCCH time slot:
SDCCH: used for signalling and short message information
CBCH: uses an SDCCH channel for Short Message Service — Cell
Broadcasts.
Overview
Packet Switching
GPRS Elements
GPRS Channels and Interfaces
2.1 Overview
The success of GSM has taken place in parallel with the explosion of interest in
the Internet and related data services. Presently, data transmission over the air
interface is limited to 9.6 kb/s, too slow for use of graphics-intensive services
such as the World Wide Web and personal video conferencing. In addition,
the circuit-switched method used for data transmission makes inefficient use
of radio resources, which are under increasing pressure from the growth in
GSM subscribers and use.
The solution chosen by European Telecommunication Standards Institute for
the double challenge of increased demand for data service and pressure
on radio resources is called General Packet Radio Service. The European
Telecommunication Standards Institute recommendations establish a standard
for inserting an alternative transmission method for data in the PLMN: packet
switching instead of circuit switching.
The Alcatel GPRS solution follows the ETSI GSM phase 2+ recommendations
closely.
4. At the destination, another PAD reads the envelope information, strips it off,
and reassembles the data in the proper order.
Header DATA Footer
Address Control
Field Field Information Field FCS
ENVELOPE
To Public Data
Networks
OMC−R
MS
Gb Gb
FRDN
Packet
SGSN Switched GGSN
Traffic
BSS
BTS MFS
GCH BSCGP
Abis
Transcoder Circuit
BTS Ater
BSC Switched
Traffic To PSTN
MSC/
GCH GCH VLR
In the Alcatel solution, the Multi-BSS Fast packet Server with its associated
interfaces is the BSS element. All other components are external to the BSS.
The following internal and external components are described in this chapter:
GPRS mobiles
The Serving GPRS Support Node
Class A
Class B
Class C.
Class A Class A mobile stations can handle circuit-switched voice and GPRS traffic
simultaneously.
Class B Class B mobile stations can be IMSI attached and GPRS attached at the same
time, but use only one service (circuit-switched or GPRS) at a time. A GPRS
attached class B mobile station can initiate an IMSI connection and suspend its
GPRS service in the following cases:
When the user is not engaged in any GPRS data transfer, and either:
A mobile station originated call is initiated
The mobile station receives a mobile termination call.
Class C Class C mobile stations an be either IMSI attached or GPRS but not both, and
can use circuit-switched or GPRS services alternately.
The Serving GPRS The SGSN is a GPRS network entity at the same hierarchical level as the
Support Node MSC. It is external to the BSS and communicates with it via Frame Relay
over the Gb interface. The SGSN is involved in requesting specific network
resources for GPRS traffic. It performs GPRS paging, authentication, and
cipher setting procedures based on the same algorithms, keys and criteria
as in circuit-switched GSM traffic.
When a mobile station wants to access GPRS services, it makes its presence
known to the network by performing a GPRS Attach procedure. This
establishes a logical link between the mobile station and the SGSN. The mobile
station is then available for SMS over GPRS, paging from the SGSN, and
notification of incoming GPRS data.
The SGSN also participates with other network elements in the routing and
relaying of packets from one node to another.
One SGSN can be connected to many MSCs and many MFSs.
The Gateway GPRS The GGSN is connected with SGSNs via an IP-based backbone. It provides
Support Node interworking between the GPRS network and external packet switched
networks. It is external to the BSS.
When the mobile station sends or receives GPRS data, it activates the Packet
Data Protocol address that it wants to use. This has the effect of making the
mobile station known to the GGSN. User data is transferred transparently from
the mobile station and external data systems by the GGSN using encapsulation
and tunnelling. This allows data packets equipped with GPRS-specific protocol
information to be transferred between the mobile station and GGSN. This
reduces the requirement for the GPRS system to interpret external data
protocols.
The GGSN also works with other network elements in the routing and relaying
of packets from one node to another.
The Multi-BSS Fast See The Multi-BSS Fast Packet Server (Section 1.3.4) for details of the MFS
Packet Server
GPRS Primary
GPRS Secondary
GPRS Primary Master A primary Master Channel can be dynamically allocated as soon as there is
Channel GPRS traffic in a cell. This feature can be enabled on a per cell basis. If there
is no GPRS traffic, the primary Master Channel is released in this cell.
The GPRS Primary Master Channel is a Packet Data Channel (PDCH) carrying
the Packet Broadcast Control Channel (PBCCH) to broadcast GPRS system
information in the cell and the Packet Common Control Channel (PCCCH)
providing GPRS specific control channels.
The Primary MPDCH is dynamically allocated by the BSS upon occurrence
of any GPRS traffic in the cell (receipt of either a downlink LLC PDU, or a
channel request from a mobile station with any establishment cause). The
primary MPDCH is dynamically de-allocated when no GPRS traffic is detected
during a given period (typically a few minutes). This minimizes the TCU load
(and also the CCCH load).
When there is a GPRS Primary Master Channel in a cell, the Alcatel BSS
broadcasts its channel description on the BCCH. Mobile stations can monitor
the broadcast and thus receive all GPRS specific system information pertaining
to the cell. The Primary Master Channel is mandatory when the Optimized
access on CCCH feature is not used. There may be at most one Primary
Master Channel in a cell.
The Primary Master Channel feature allows the operator to set a primary Master
Channel and to benefit from the following advantages, on a per cell basis:
GPRS Secondary Master The GPRS Secondary Master Channel is a Packet Data Channel (PDCH)
Channel carrying the Packet Common Control Channel (PCCCH) providing GPRS
specific control channels. In addition to the Primary Master Channel, one
or several Secondary Master Channels can be allocated in the cell. This
feature enables automatic dynamic allocation and release of secondary Master
Channels based on common signalling traffic load estimates. This dynamically
adapts the GPRS signalling capacity of the cell to the traffic demand. The
secondary master PDCH are always dynamically established or released in
the cell, regardless of whether the Primary Master Channel is statically or
dynamically allocated. The feature provides the operator with the following
improvements:
Avoids the need to reserve static radio resources to match the maximum
traffic demand.
Configuration of the allocation and de-allocation algorithm thresholds is
performed automatically by the BSS.
PBCCH
PCCCH
PDTCH
PACCH.
The MPDCH carrying the PBCCH is called the primary Master PDCH. The
PBCCH carrier is indicated on the BCCH (in the SI13 message). Up to
16 MPDCH can be allocated in a cell (one primary MPCCH, 15 secondary
MPDCH). The additional MPDCH are called secondary Master PDCH.
When the primary MPDCH is activated, the BSC broadcasts the SI 13 message
with the radio configuration of the PBCCH. When the primary MPDCH is
deactivated (always decided by the MFS even following a fault, e.g. TRX
recovery impacting the MPDCH), the SI 13 message no longer contains a
PBCCH description. Paging and assignment messages are routed either on
CCCH or PCCCH according to the presence or not of the MPDCH.
To summarize, if the primary MPDCH is on slots 0 to 3, the secondary MPDCH
can be located at any slot position. If primary MPDCH is on slot k (k = 4 to 7),
secondary MPDCH shall be on slot n with n > k – 4; in such case, the lower k is,
the highest flexibility is to allocate a secondary MPDCH.
The following table describes the parameters that can be defined by the
operator.
11=Block B0,
B6, B3, and
B9 used for
PBCCH
Packet Traffic Channel This channel is analogous to a circuit-switched traffic channel, and is used for
user data transmission and its associated signaling. It has two sub-channels:
Packet Data Traffic Channel which contains the user data traffic
If multiple PDTCHs are assigned to one mobile station, the PACCH is always
allocated on one of the PDCHs on which PDTCHs are allocated.
The function of these sub channels is analogous to their circuit-switched
counterparts.
Packet Timing Advance This bi-directional channel is used for maintaining a continuous timing advance
Control Channel update mechanism.
Also, when an MPDCH exists, the messages shown in the following table
are used.
Cell allocation
GPRS mobile allocations
Via the Ater Mux interface through the Transcoder to the MSC. In this case
it carries a combination of packet-switched and circuit-switched traffic
and signalling.
Combinations of these methods are also possible. See Figure 13 for the
position of the Gb interface in the system.
The Gb interface provides end-to-end signaling between the MFS and the
SGSN, and serves as the BSS-GPRS backbone. Its principal functions are
shown in the following table.
Function Description
Network services Transfer of BSSGP-PDUs between BSS and
SGSN
Allocation and load sharing of PDUs among
Virtual Channels
Access to intermediate Frame Relay Data Network
BSS-GPRS Protocol Radio resource information
services
Quality of Service Information
Routing information
Transfer of LLC-PDUs between the BSS and the
SGSN
Suspend and Resume procedures for class B
mobile stations
Function Description
Common radio signaling Circuit-switched and packet-switched paging
(MFS to BSC)
Channel Requests from BSC to MFS
Uplink and downlink channel assignment (MFS
to BSC)
GPRS radio resource Allocation/de-allocation of resources (MFS to
management BSC)
Release indication (BSC to MFS)
Load indication: this limits the allocation for GPRS
traffic (BSC to MFS)
Note: The common radio signaling functions of the BSCGP are handled on the GPRS
Signaling Link, which is carried inside the Ater interface.
Transfer of PDUs between MFS and BTS (thus packet data is not directly
handled by the BSC but passes transparently through it on the GCH
interface)
L1-GCH layer
L1-GCH is the physical layer based on ITU-T recommendations G.703.
The L1-GCH layer utilizes digital transmission at a rate of 2048 kbit/s with a
frame of 32 x 64 kbit/s time slots. An L1-GCH channel has a transmission
rate of 16 kbit/s.
L2-GCH layer
L2-GCH is the data link layer which is an Alcatel proprietary protocol. This
layer is in charge of the data transfer of the GCH frames between the
MFS and the BTS.
The L2-GCH layer offers a service of data transport for the RLC/MAC layers
located in the MFS. Its main functions are:
GCH link establishment and release
Synchronization with the radio interface
RLC/MAC PDUs transfer.
For more information on GSM transmission, refer to Call Set Up (Chapter 3).
MAC and RLC Functions Since multiple mobile stations can be competing for the same physical
resource(s), an arbitration procedure is necessary. This is provided by the
Medium Access Control function.
The MAC function operates between the MFS and the mobile station, and
works in conjunction with the Radio Link Control function. Radio Link Control
defines the procedures for retransmission of unsuccessfully delivered data
blocks (error correction) and for the disassembly and reassembly of PDUs.
Temporary Block Flow When PDUs need to be transferred between the MFS and the mobile station,
a temporary point-to-point physical connection is set up to support the
unidirectional transfer of PDUs on one or more PDCHs. This connection
is called a Temporary Block Flow.
A Temporary Block Flow is maintained only for the duration of the data transfer.
The Temporary Block Flow is allocated radio resources on one or more PDCHs
and comprises a number of RLC/MAC blocks carrying one or more PDUs.
A typical user session in which data is exchanged bi-directionally requires the
establishment of one Temporary Block Flow in each direction, and the path
of each Temporary Block Flow can be different.
Re-establishment If the mobile station detects a radio link failure, it will re-establish the link with
the SGSN. The BSS transmits the reselection configuration parameters to be
used by the mobile station. Mobile controlled re-selection is equivalent to
circuit-switched call re-establishment. Refer to Call Re-establishment by the
Mobile Station (Section 4.8) for more information.
2.4.2 Paging
Paging is the procedure by which the network contacts a mobile station.
The network can coordinate circuit-switched and packet-switched paging, if
there is a Gs interface between the MSC and the SGSN. This means that
circuit-switched paging messages can be sent on the channels used for
packet-switched paging messages, and vice-versa. Three modes are defined.
Mode Description
Network Circuit-switched paging messages are sent via the SGSN
Operation Mode and MFS
1 The circuit-switched paging message for the
GPRS-attached mobile station is sent on the PPCH or
CCCH paging channel, or on the PACCH. This means
that the mobile station only needs to monitor one paging
channel. It receives circuit-switched paging messages on
the PACCH when the mobile station is in packet transfer
mode.
Network Circuit-switched paging messages are sent via the MSC
Operation Mode and BSC, but not the MFS.
2 The circuit-switched paging message for the
GPRS-attached mobile station is sent on the CCCH
paging channel. The channel is also used for
packet-switched paging messages. This means that
the mobile station only needs to monitor the PCH.
Circuit-switched paging continues on the PCH even if the
mobile station is assigned a PDCH.
Network Circuit-switched paging messages are sent via the MSC
Operation Mode and BSC, but not the MFS.
3 The circuit-switched paging message for the
GPRS-attached mobile station is sent on the CCCH
paging channel. The packet-switched paging message is
sent on either the PPCH (if allocated) or on the CCCH
paging channel
Packet-switched paging does not use the Local Area for paging, but a GPRS
Routing Area . The RA is smaller, thus fewer cells are involved.
Mobile station multislot class. This is not always known in the uplink case.
Time Slot Allocation If MAX_UL_TBF_SPDCH is set to five, the minimum raw bit rate per user will be
Scenario increased from 1.9 kbit/s to 2.68 kbit/s (13.4/5). When the PDCH reaches five,
it is declared full and will not accept a sixth shared user.
However, setting the N_TBF_PER_PDCH parameter will affect a compromise
between resource efficiency and quality of service For example, if
N_TBF_PER_PDCH= 2 and coding scheme 2 is used, the preferred raw bit rate
per user will be 6.7 kbits/s (13.4/2). When the number of users on the PDCH
reaches the N_TBF_PER_PDCH value (2), the PDCH is declared “busy” and will
preferably not accept a third user. But if the GPRS load is such that all PDCHs
are busy, the BSS will override the number of users set in N_TBF_PER_PDCH
and increase the number of shared resources to the maximum, using the
MAL_XL_TBF_SPDCH value.
State Explanation
Empty No established TBFs.
Active At least one established TBF and the total number of
established TBFs is smaller than a defined threshold
(O&M Parameter N_TBF_PER_PDCH).
Busy The number of established TBFs is greater than
or equal to O&M Parameter N_TBF_PER_PDCH but
smaller than the maximum allowed (O&M Parameter
MAX_UL/DL_TBF_PDCH).
Full The number of established TBFs is equal
to the maximum set by O&M Parameter
MAX_UL/DL_TBF_PDCH.
2. The MFS de-allocates PDCHs as soon as they become empty until the
new, lower threshold is reached.
3. When normal load conditions resume, the MFS can then reallocate
additional resources up to the limit defined for its PDCH group. This is set by
the parameter MAX_PDCH_GROUP.
This is the process that takes place during the phase marked “High BSC Load”,
shown in the figure below. The figure shows a typical sequence illustrating the
PDCH allocation procedure. Numbers in bold refer to the steps above.
MAX_PDCH_GROUP
MAX_PDCH_HIGH_LOAD
1
MIN_PDCH_GROUP
Acknowledged mode
Unacknowledged mode.
Acknowledged Mode When the network wishes to delay the release of the TBF, it sends the last
RLC data block but does not set the Final Block Indicator (FBI) bit. The
network only sets the FBI bit when it wishes to permanently end the TBF.
Once the network has sent the RLC data block containing the last octets of
the most recent LLC frame to the MS, the network maintains the downlink
TBF by occasionally sending dummy downlink RLC data blocks to the MS,
incrementing the BSN with each dummy data block sent. When the network
receives a new LLC frame, it begins to transmit new RLC data blocks to the MS,
beginning with the next available BSN.
When the network wishes to poll the MS for a Packet Downlink Ack/Nack when it
has no LLC data to send, the network sends a dummy downlink RLC data block.
The dummy downlink RLC data block is formed by inserting an LLC Dummy
UI Command into a CS-1 downlink RLC data block. The LLC Dummy UI
Command is an invalid LLC PDU and is discarded by the LLC entity in the MS.
Unacknowledged Mode In RLC unacknowledged mode the MS detects the end of the TBF by detecting
the Final Block Indicator (FBI) bit set to 1. The MS then transmits a Packet
Control Acknowledgement, acknowledging the end of the TBF. The procedure
for delayed release of downlink TBF in RLC acknowledged mode applies
except that no retransmission of data blocks is done.
GPRS
Attach
Reque
st
Update
Locati
on
er
nticati
on scrib
Authe Sub ta
Da
Subs
c
Data riber
ACK
ate
Upd ACK
a t i o n
Loc
t
Accep
Attach
GPRS
GPRS
Attach
Comp
lete
1. The mobile station sends a GPRS Attach Request to the SGSN. This
request contains:
2. The SGSN verifies the mobile station identity, sends a location update to
the HLR, (if the attach requested is a combined GPRS/IMSI Attach, the
MSC/VLR is also updated), and requests a subscriber data profile.
3. The HLR sends a location acknowledgment back to the SGSN with the
subscriber data inserted.
4. The SGSN then assigns a P_TMSI to the mobile station.
5. The mobile station acknowledges the P_TMSI, and the Attach procedure
is complete.
Once the GPRS Attach procedure is performed, the mobile station is in Standby
and can activate Packet Data Protocol contexts.
Activat
e PDP
Context
Reque
st
Create
PDP
Context
Reque
st
DP
te P
Crea sponse
t Re
tex
Con
ept
xt Acc
Conte
te PDP
Activa
2. The SGSN verifies the mobile station subscriber data, creates a Tunnel
Identifier (TID — a logical bidirectional tunnel between the mobile station
and the GGSN), and sends the new Packet Data Protocol type and address
to the GGSN.
3. The GGSN creates a context, sends an acknowledgment to the SGSN,
which sends an acknowledgment to the mobile station.
4. The GGSN can now send data through the SGSN, and billing can begin.
GGSN-Originating The GGSN Packet Data Protocol context activation process is illustrated in
Activation the following figure.
MS BTS BSC MFS SGSN HLR GGSN
PDU
PDP
Info
ting
Rou
uest
Req
Routin
g Info
ACK
t
eques
tion R
otifica
PDU N
PDU N
otificatio
n Resp
onse
n
itvatio
text Ac
st PDP Con
Reque
PDP C
ontext
Activatio
n
1. When the GGSN receives data, it sends a message to the HLR requesting
the mobile station location.
2. The HLR sends the GGSN location information and the current SGSN IP
address.
3. The GGSN sends a PDU Notification Request to the SGSN, which indicates
a Packet Data Protocol context needs to be created.
4. The SGSN returns a PDU Notification Response to the GGSN, and sends a
Request Packet Data Protocol Context Activation message to the mobile
station. This message contains the Packet Data Protocol type and address
5. The mobile station then begins a Packet Data Protocol context activation
procedure as described above
Pack
1 et Ch
Requ annel
est
F
L TB
et U t
Pack ignmen
2 Ass
RLC
3 PDU
PDU
RLC ACK
4 K / N
AC
UL L
LC P
DU
5
PDU
RLC ACK
/ N
ACK
6
STAND BY
g PS 1
in
Pag
PCH
H or
PPC
2
Pack
et Ch
Requ annel
3 est
F
L TB
a c k et U ent
P gnm
Assi
4 LLC
PDU
UL −
LLC
PDU
READY
PDU 5
LLC
DL −
F
L TB
a c k et D ent
P gnm
6 Assi
DL : Downlink
MS : Mobile station
LLC : Logical Link Control
PCH : Paging Channel
PDU : Protocol Data Unit
PPCH : Packet Paging Channel
PS : Packet Switched
SGSN : Serving GRPS Support Node
TBF : Temporary Block Flow
UL : Uplink
Figure 19: Mobile-Terminated Data Transfer
De−Ac
tivate
PDP C
ontext
Reque
st
Delete
Conte PDP
xt Req
uest
P
te PD
Dele esponse
t R
tex
Con
ept
xt Acc
PDP Conte
De−Activate
DP
te P
Dele sponse
e
xt R
C onte
st
Reque
ontext
vate PDP C
ti
De−Ac
De−Ac
tivate
PDP C
ontext
Accep
t
GGSN−Originating te P
DP
Dele equest
R
text
Con
uest
xt Req
PDP Conte
tivate
De−Ac
De−Ac
tivate
PDP C
ontext
Accep
t
Delete
Conte PDP
xt Res
ponse
1. The SGSN sends a Delete Packet Data Protocol Context Request to the
GGSN, which contains the TID.
2. The GGSN de-activates the Packet Data Protocol context and sends a
Delete Packet Data Protocol Context Response to the SGSN.
3. The SGSN sends a De-activate Packet Data Protocol Context Request to
the mobile station.
4. The mobile station de-activates the context, and returns a De-activate
Packet Data Protocol Context Accept.
GGSN-Originating 1. The GGSN sends a Delete Packet Data Protocol Context request to the
De-activation SGSN, which contains the TID.
2. The SGSN sends a De-activate Packet Data Protocol Context Request to
the mobile station.
3. The mobile station de-activates the context and returns a De-activate
Packet Data Protocol Context Accept.
4. The SGSN sends a Delete Packet Data Protocol Context Response to the
GGSN, which deletes the context.
RR Su
spend
Susp
end
Susp
end
T3
nd Ack
Suspe
nd Ack
Suspe
Resu
me
Resu
me
T_GPRS_Resume T4
ck
me A
Resu
ck
me A
Resu
se
Relea
annel
RR Ch
Routing Area
Update Reque
st
4. On receipt of the Resume Ack from the SGSN, the MFS stops the guard
timer (T4) and sends a Resume Ack message to the BSC. If no Resume Ack
is received from the SGSN before expiry of the guard timer (T4), the MFS
sends a Resume Nack to the BSC. On receipt of the Resume Ack or Nack
message from the MFS, the BSC stops the guard timer (T_GPRS_Resume).
5. The BSC sends an RR Channel Release (GPRS Resumption) message
to the mobile station and deletes its suspend/resume context. GPRS
Resumption indicates whether the BSS has successfully requested the
SGSN to resume GPRS services for the mobile station, (i.e., whether
Resume Ack was received in the BSS before the RR Channel Release
message was transmitted). The mobile station then exits dedicated mode. If
the guard timer expired, or if a Resume Nack message was received by
the BSC, the Channel Release message includes the GPRS Resumption
indication equal to NOK.
6. The mobile station resumes GPRS services by sending a Routing Area
Update Request message in the following cases:
T3240 expiry.
The mobile station leaves the Ready mode and enters the Idle mode
Detac
h Req
uest
Delete
Conte PDP
xt Req
uest
P
te PD
Dele esponse
R
text
Con
pt
h Acce
Detac
GPRS
1. The mobile station sends a GPRS Detach Request to the SGSN. This
message contains:
2. The SGSN tells the GGSN to de-activate the Packet Data Protocol context,
and sends a Detach Accept message to the mobile station.
Network-Originating Network-originating GPRS Detach procedures are shown in the following figure.
Detach
MS BTS BSC MFS SGSN GGSN HLR
ion
ocat
cel L
Can
Delete
PDP
Conte
xt Req
uest
uest
h Req
Detac
GPRS
DP
te P
Dele sponse
t R e
Contex
Detac
h Acce
pt
Cance
l Loca
tion AC
K
A GPRS Detach can be initiated by both the SGSN and the HLR.
An SGSN Detach is the most common network Detach. In this procedure:
1. The SGSN sends a Detach Request to the mobile station, which contains
the Detach type. The Detach type tells the mobile station if it needs to
re-attach and re-activate the Packet Data Protocol context previously used.
2. The SGSN tells the GGSN to de-activate the Packet Data Protocol contexts,
and the mobile station sends the Detach Accept message to the SGSN.
If the Detach is requested by the HLR:
1. The HLR sends a Cancel Location message to the SGSN, which initiates
the above process.
2. The SGSN confirms the Packet Data Protocol context deletion by sending a
Cancel Location Acknowledgment to the HLR.
3 Call Set Up
This chapter provides an overview of how a call is set up between the NSS and
the mobile station. 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:
Overview
Congestion
Classmark Handing
Authentication
Ciphering.
3.1 Overview
Call set up is required to establish communication between a mobile station
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 Normal Assignment (Section 3.2.3) for more information.
Call Types The following table shows the three basic types of call:
The channels used for calls are the SDCCH for signalling and the traffic channel
for user traffic (see The Air Interface (Section 1.7.7) for more information).
These channels are associated with FACCH/SACCH. An SDCCH is always
assigned for call set up, even if a traffic channel 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 mobile
station and the MSC.
Call Set Up Phases The following table shows the phases involved in call set up:
Phase Composition
Radio and Link Paging (for mobile terminated calls only) informs
Establishment the mobile station that it is being called.
If attach_detach_allowed is activated, the
mobile station IMSI_detach message can
eliminate the need for paging. See IMSI
Attach-Detach (Section 3.3.4).
Immediate assignment procedure allocates a
resource to the mobile station and establishes a
Radio signalling Linkbetween the BSS and the
mobile station.
A interface connection, to assign an SCCP
signalling channel between the BSC and MSC
Assignment of a switching path through the BSC.
Authentication and Classmark handling
Ciphering Authentication
Ciphering.
Normal assignment Teleservice/bearer service negotiation
Channel allocation
Physical context procedure
Assigning a traffic channel, if required
Connecting the call.
The phases are described in Mobile Originated Call (Section 3.2) and Mobile
Terminated Call (Section 3.3).
The procedure of obtaining these initial connections is called radio and link
establishment. The radio and link establishment procedure establishes
signalling links between:
The BSS and the mobile station via the SDCCH channel
These links pass the information for call negotiation, and set up a traffic
channel, if required.
The figure below shows radio and link establishment for a mobile originated call.
Channel Request The mobile station initiates a call by sending a channel_request message,
with an REF. The REF includes an establishment cause and a RAND (used for
authentication). It is transmitted on the RACH channel. The RACH channel is
associated with the CCCH channel which the mobile station is monitoring while
in idle mode. The establishment cause field of the REF specifies:
An emergency call
Call re-establishment
Response to paging
Location update
The mobile station notes the random number and frame number associated
with each channel_request message. These are used by the mobile station to
recognize the response sent from the BSS. This response is sent on the AGCH,
which can be monitored by many mobile stations. The mobile station 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.
Chann
el Activ
ation A
ck
d
mman
ign co
ed iate ass
Imm REF
RFN+
wer+
GCH) C C H+po
ment (A TA+SD
iate assign
MS compares Immed
message with +SD CCH
RF N+TA
REF in memory REF+
Switch to SABM
SDCCH + cm +
Service
Request Establis
h Indic
ation
UA cm + Se SCCP
rvice Re Conne
quest ction R
equest
uest cm + Se
e Req rvice Re
Servic quest
cm : Classmark
ID : Mobile station identity
power : Mobile station power or BTS power
REF : Random access information value
RFN : Reduced frame number
SDCCH : Description of the allocated SDCCH (Stand-alone Dedicated Control Channel)
Service : Initial layer 3 message
Request
TA : Timing advance
UA : Un-numbered acknowledgment
Figure 26: Radio and Link Establishment for Mobile Originated Call
Displays a network error message for all calls except location updates
Performs automatic reselection for location update calls. This means that
the mobile station attempts random access on a different cell.
On receipt of the channel_request message from the mobile station, the BTS
sends a channel_required message to the BSC. This message contains the
random number sent by the mobile station, and the timing advance measured
by the BTS.
Note: Under peak load conditions, resources may be over allocated due to this
process. See below for details on how the Immediate Assignment Extended
feature works to alleviate this problem.
SDCCH Channel The BSC checks the channel_required message to ensure it can accept the
Activation 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
traffic channel has the most available SDCCHs. This ensures the load is
spread between the traffic channels.
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
Mobile station and BTS power commands. The mobile station 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 mobile station message on the
SDCCH. It then sends a channel_activation_acknowledgment message to
the BSC. The BSC stops its guard timer.
Note: Contention resolution prevents two mobile stations connecting to the same
SDCCH.
The following figure shows the Channel Activation procedure.
MS BTS BSC MSC
SDCCH
Allocation
vation
el Acti
Chann
er
+pow
DCCH
TA+S
Chann
el Activ
ation A
ck
nd
omma
sign c
m ediate as FN
Im EF+R
er+R
+pow
GCH) DC C H
ent (A TA+S
te as signm
Im media DCCH
TA+S
F+RFN+
Switch to RE
SDCCH
Immediate Assignment When there is congestion on the SDCCH, the mobile station could retry
Reject repeatedly without success to access a channel. This produces the following
undesired effects:
Undesirable messages on the mobile station screen
Repeated futile attempts to connect overload the RACH and Abis interface
The BSC flag EN_IM_ASS_REJ is set to true. This flag is set on a BSC
basis, and can be viewed but not modified from the OMC-R.
The BSC receives a channel_required message from the BTS with one of
the following establishment causes:
Emergency call
Call re-establishment
Mobile station originating call
Location update
Service Calls.
Note: This message can not be used when the mobile station is responding to
paging, i.e. in the case of a Mobile-terminated call.
Immediate Assignment Under peak load conditions, it is likely that the mobile station will send several
Extended channel_request messages before receiving an immediate_assignment
message indicating that a channel has been allocated to it. At this stage,
the BSC is unable to identify the mobile station which sent a given
channel_request and so it will grant several SDCCHs to the same mobile
station, thus wasting resources and reducing throughput on the AGCH.
If several immediate_assignment messages are queued on the AGCH,
the BTS will try to build an immediate_assignment_extended message,
passed to the mobile station on the air interface, constructed from pieces of
two immediate_assignment messages as follows:
Set Asynchronous The first layer 2 frame sent on the SDCCH is a standard LAPDm type frame,
Balanced Mode known as the Set Asynchronous Balanced Mode. This is equivalent to the
Set Asynchronous Balanced Mode Extended frame in the LAPD. On the Air
interface, it establishes the LAPDm connection with the BTS. This frame
can also contain layer 3 messages.
Contention Resolution The mobile station 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 acknowledgment to the mobile station containing the same layer
3 message. Therefore, only the mobile station that sent the message can
accept the acknowledgment from the BTS and consider itself connected.
The following figure shows the establishment of the connection for a mobile
originated call.
MS BTS BSC MSC
SABM
+ cm +
Service
Reques Establi
t sh Indic
ation
cm + Se
UA rvice Re SCCP
quest Conne
ction R
equest
quest cm + Se
Serv ice Re rvice Re
quest
nfirm
on Co
Co nnecti
SCCP
cm : Classmark
Service : Initial layer 3 message including the mobile station identity and classmark
Request
UA : Un-numbered acknowledgment
Figure 29: Connection for Mobile Originated Call
For a mobile station originated call, the layer 3 message from the mobile
station contains:
An Information Element indicating:
CM service request (speech/data, SMS, emergency call)
Location updating request (location updating procedure)
CM re-establishment request (after a failure)
IMSI detach indication (mobile station power off - see IMSI Attach-Detach
(Section 3.3.4) for more information).
The mobile station identity (see Authentication (Section 3.7) for more
information)
The mobile station classmark (see Classmark Handling (Section 3.6) for
more information).
The network uses this message to decide which call negotiation procedures are
required and whether to assign a traffic channel.
Establish Indication The BTS sends an establish_indication message to the BSC to indicate that
the mobile station has connected. The BSC stops the guard timer, extracts the
classmark information, and initiates an SCCP connection with the MSC.
SCCP Connection 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 mobile station and the MSC.
Sends the Random Number for the ciphering and authentication procedures.
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 Ciphering (Section 3.8).
Channel Request The MSC initiates the assignment of the traffic channel 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 traffic
channel this is speech or data plus data rate). This message also contains
the mobile station classmark which the BSC uses if it has not received the
classmark from the mobile station.
The assignment_request message may contain a codec list, giving, in order of
preferences, the type of codec it prefers to use (for example, one that supports
enhanced full-rate speech). In this case, the BSC checks the list against those
supported by the cell, and chooses the preferred codec type that can be used
by both the BTS and by the mobile station.
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 mobile station.
quest
ment re
assign
m
pe+c
nel ty
chan
TCH
allocation
quest
text re
al con
physic
physica
l conte
xt confi
rm
power +
TA
vation
el acti
chann
her
+ cip
+ TA er
(SACC
H) TCH p o w
X+
+ DT
ates
r upd channe
powe l activa
TA + in fo 5 e6 tion ac
knowle
+ sys dge
and
comm
ment
assign
H)
(SDCC
mand
nment com
assig
release
SDCCH SABM
(FACC
H)
estab
lish in
dicatio
Set n
H) transcoder
UA (FACC
assign
ment c
o mplete
initiate SDCCH
release alerting
layer 3 CC
layer 3 CC
layer 3 CC connect
layer 3 CC
connect acknowledgement
layer 3 CC
Traffic Channel The BSC ensures that it is not running any other procedures for the mobile
Allocation station and then allocates resources for the traffic channel. 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 traffic
channel resource allocation algorithms for:
Normal assignment
In-call modification
Intercell handover
Intracell handover
Directed retry
Concentric cells
Microcells.
Traffic Channel The BSC sends a physical_context_request message to the BTS, to find out
Activation the current power and timing advance being used by the mobile station on
the SDCCH. The BTS responds with a physical_context_confirm message,
containing the relevant information. If no channel is available, and queuing
is enabled, the call is placed in the queue. Refer to Congestion (Section
3.5) for more about queuing.
The following figure shows the channel activation process for the traffic channel.
MS BTS BSC MSC
TCH
allocation
quest
text re
al con
physic
physical
context
confirm
power +
TA
ation
el activ
chann
er
+ ciph
+ TA
H) TCH ower
(SACC X + p
+ DT
ates
r upd
powe channe
TA + 5&6 l activa
in fo tion ack
+ sys nowled
ge
com mand
assignment
CH)
d (SDC
omman
ment c
assign
The BSC starts a timer, and waits for the BTS to acknowledge that it has
activated the channel.
The BTS initializes its resources for the traffic channel, sets the ciphering
mode, sends timing advance and power information to the mobile station
on the SACCH associated to the traffic channel, which is constantly
monitored by the mobile station. At the same time, the BTS sends a
channel_activation_acknowledgment message to the BSC. The BSC stops
its timer and sends an assignment_command message on the SDCCH to the
mobile station. This instructs the mobile station to change to the traffic channel.
When the mobile station receives the assignment_command message, it
disconnects the physical layer, and performs a local release to free the LAPDm
connection of the SDCCH.
The following figure shows the channel assignment process for the traffic
channel.
MS BTS BSC MSC
release
SDCCH SABM
(FACC
H)
establi
sh ind
ication
Set
CCH) transcoder
UA (FA
assign
ment c
omple
te
The mobile station then establishes the LAPDm connection (via the SABM on
the FACCH) for the traffic channel. 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 acknowledgment to the mobile
station. The mobile station 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).
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 mobile station. The
mobile station generates a ring tone.
When the called party answers, the MSC sends a connect message to the
mobile station. The mobile station responds with a connect_acknowledgment
message. The call is established.
The following figure shows the call connection process for a mobile originated
call.
MS BTS BSC MSC
initiate SDCCH
release alerting
layer 3 CC layer 3 CC
layer 3 CC connect
layer 3 CC
connect acknowledgement
layer 3 CC
MS : Mobile station
SDCCH : Stand-alone Dedicated Control Channel
Figure 33: Call Connection for Mobile Originated Call
Off Air Call Set-Up OACSU is a method available in the BSS where the network assigns a traffic
channel only when the called party has answered the call. This improves the
efficiency of traffic channel allocation as unsuccessful calls will not take up any
traffic channel resources. This feature is controlled by the MSC.
Practically speaking, the way this happens is the Layer 3 alerting message
is sent by the MSC just after the call_proceeding message. The mobile
station then enters the ringing phase. The assignment_request message is
not sent by the MSC until the called party answers. The rest of the Layer 3
exchanges between MSC and BSC take place after the mobile station sends
the assignment_complete message to the MSC.
When OACSU is in use the mobile station may provide internally generated
tones to the user (in a Mobile Originated call) during the ringing phase, as the
traffic channel is not yet available for tones or in-band announcements to be
sent.
This feature has the effect on the system of increasing the probability of an
internal (SDCCH to SDCCH) handover being initiated by the BSS while the
Normal Assignment procedure is being initiated by the MSC.
paging
t
cell lis
IMSI +
TMSI/
com mand
paging
up +
ing gro
SI pag
(PCH) TMSI/IM
el num
b e r
reques
t chann
paging
SI
TMSI/IM
chann
el requ
est
(RACH
)
chann
el requ
ired
The mobile station identity (TMSI or IMSI of the mobile station 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
mobile station.
The BSC checks the paging message and, if valid, calculates the mobile
station paging group and the CCCH time slot 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.
The mobile station listens to messages sent to its paging group. When
it receives a paging message with its mobile station 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 Mobile Originated Call (Section 3.2).
Note: When the mobile station sends the SABM, it indicates that the connection is
in response to a paging request. For more information about paging, see
Paging (Section 3.4).
layer 3 CC r service
tele/beare
layer 3 CC
call confirmed
(SDCCH)
bearer service layer 3 CC
layer 3 CC
ring
tone alerting
layer 3 CC
layer 3 CC
user
answer connect
layer 3 CC
layer 3 CC
e
knowledg
connect ac
layer 3 CC
layer 3 CC
MS : Mobile station
SDCCH : Stand-alone Dedicated Control Channel
Figure 35: Normal Assignment for Mobile Terminated Call
Off Air Call Set-Up If OACSU is in use, it is possible that at one moment the called party may have
answered the call, but the traffic channel is still not assigned by the network (for
example, the call is queued). In this case the mobile station may supply tones
to the answering user, so that the user does not hang up before the Normal
Assignment procedure completes.
3.4 Paging
Paging is the procedure by which the network contacts a mobile station. For
example, if the network needs to inform the mobile station of an incoming call, it
pages the mobile station to prompt it to request a channel. After the immediate
assign procedure, the service_request message from the mobile station
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 mobile station from monitoring every occurrence of the PCH,
each mobile station is assigned a paging group calculated from the IMSI.
Each mobile station calculates its paging group and monitors only that PCH
sub-channel. This saves mobile station battery power.
The number of paging groups and the CCCH organization varies for each
configuration. The mobile station knows the CCCH organization from the
information passed on the BCCH (sys_info 3).
The AGCH sends the immediate_assignment message to the mobile station.
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. The following figure 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
The BSC calculates the paging group of the mobile station for each cell and the
CCCH time slot. It then sends a paging_command message to each BTS,
indicating the CCCH time slot number, mobile station paging group and the
mobile station identity (IMSI/TMSI).
The BTS builds a paging_request_type_x message to send to the mobile
station. There are three types of paging request messages, as the BTS can
page more than one mobile station at a time. The following table shows the
relationship between the paging message type, the number of mobile stations
to be paged and the mobile station ID used.
Paging Request
Message Mobile Station Identification
Type_1, identifying up to IMSI or TMSI (for 1 mobile station)
two mobile stations IMSI, IMSI or TMSI, TMSI or IMSI, TMSI (for two
mobile stations)
Paging Request
Message Mobile Station Identification
Type_2, identifying three TMSI, TMSI, TMSI or
mobile stations TMSI, TMSI, IMSI
Type_3, identifying four TMSI, TMSI, TMSI, TMSI
mobile stations
paging
list IE
+ cell
nd
comma
paging
up
ing gro
t + pag
CH timeslo
reques
t + CC
paging
S I
TMSI/IM
channe
l reque
st
channe
l requir
ed
REF +
RFN +
TA
SABM
+ serv
ice req
uest (p
aging
respon establis
se) h indic
ation
3.5 Congestion
To prevent an assignment_request or an external handover_request
message being rejected, the BSS allows queueing of traffic channel requests.
Congestion occurs when all traffic channels 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.
3.5.1 Queueing
Queueing is used to achieve a higher rate of successful call set up and external
handover completion in cases of traffic channel congestion. This is achieved by
queueing the request for a defined period of time. During this time a traffic
channel can become available and the traffic channel assignment can then
be completed.
When all traffic channels of a cell are busy, assignment and external handover
requests for traffic channel 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.
3.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.
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 incoming
request is higher than the lowest in the queue, the incoming 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 preempted 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:
Traffic channel availability
Traffic Channel If another traffic channel disconnects within the cell, the request at the top of
Availability the queue is assigned to the newly available traffic channel. The request is
removed from the queue. An assignment_complete message is sent to the
MSC notifying it of the successful assignment of a traffic channel.
Forced Directed Retry The BSC detects that the call can be supported on another cell, and
implements Forced Directed Retry.
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 traffic
channel in a target cell is known as directed retry.
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 traffic channel is chosen and a handover is attempted (SDCCH to
traffic channel). 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.
Queue Preemption If a higher priority request arrives in the queue, Queue Preemption is
implemented.
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.
Reshuffling Half-Rate Half-rate calls use only a half time slot. If two half-rate calls are alone on
Calls separate time slots they are gathered on to a single time slot. This frees a
whole time slot to serve a queued full-rate request. Reshuffling half-rate calls
is enabled on a per cell basis, by setting the EN_HR_RESHUFFLING parameter
to TRUE. Setting the EN_HR_RESHUFFLING parameter to FALSE disables
reshuffling half-rate calls for that cell.
Fast traffic handover is enabled when all of the following conditions are met:
If the request is a half-rate request, it is not queued but served, because at least
two half-rate resources in the half-rate pool are required to trigger the algorithm.
If there is only one resource in the half-rate pool, it means there is an odd
number of half-rate calls in the cell, so it is not possible to pair the last one. The
queued request may be an assignment, or an incoming external emergency
handover. If the algorithm has been triggered once and the queued request
served (or rejected by expiry of the timer), if at least another request still
remains in the queue, and if the trigger condition is still fulfilled for the top
queued request (assignment or external emergency handover), then the
algorithm is triggered again. If a half-rate request is queued behind a full-rate
request, the half-rate request is served on a remaining half-rate resource of the
half-rate pool (if any) without triggering the algorithm again.
Half-rate calls are paired using an intracell handover. In the case of concentric
cells, mobile stations are queued in the outer zone only. The check for two
free half-rate resources applies to the outer zone only (to free a resource in
the outer zone). The mobile station selected will make its handover into the
outer zone (i.e. this handover does not allow handover from the outer zone
to the inner zone).
Fast Traffic Handover Another possibility to save resources in case of traffic peaks is to force
handovers toward neighbor cells which have less traffic. The fast traffic
handover searches in the whole cell for a mobile which can perform a handover
to a neighbor cell with less traffic if the received signal level of the BCCH is
good enough. It is much more efficient than the forced directed retry when the
overlap of adjacent cells is reduced, e.g., in the case of single layer networks,
or for deep indoor coverage (if the umbrella cell does not overlap totally the
microcells). Fast traffic handover is enabled on a per cell basis, by setting the
EN_FAST_TRAFFIC_HO parameter to TRUE. Setting the EN_FAST_TRAFFIC_HO
parameter to FALSE disables fast traffic handover for that cell.
Fast traffic handover is enabled when all of the following conditions are met:
3.5.3 Pre-emption
Pre-emption is an optional feature and is initiated during congestion periods.
The feature allows radio resources in a cell to be allocated to those calls which
are deemed to be the most important. The importance of the connection
is given by the MSC to the BSC via signalling on the A interface. During
congestion periods, the BSC ensures that high priority transactions obtain the
resources they require. The BSC performs a release of radio resources in order
to obtain the radio resource for the higher priority call.
For Phase 1 & Phase 2 GSM the signalling for priority and pre-emption exists
on the A interface. The setting of this data on the A interface is controlled by
the MSC. The conditions under which the information is set is up to operator
choices. For Phase 2+ GSM the priority and pre-emption information is based
on subscription data which is stored in the HLR and downloaded to the VLR via
MAP protocols. This information can also be used by the MSC when setting the
priority level and pre-emption attributes for the call.
The pre-emption attributes of a call are defined by three bits:
pci. The pre-emption capability indication indicates if the transaction can
pre-empt another transaction
Paging
TCH Assignment
TCH Handover.
Pre-emption Rules An Assignment Request message with pci=1 and priority level=p1 will
pre-empt an on-going call with pvi=1 and priority level=p2 (p2 is lower than p1).
A Handover Request message with pci=1 and priority level=p1 will pre-empt
an on-going call with pvi=1 and priority level=p2, except if the prec bit is present
and set to 0 (i.e. the old BSS does not recommend the pre-emption of an
on-going call to be performed by the target BSS).
In both cases, the call with the lowest priority level=p2 value is selected first,
and if several calls have the same lowest priority level=p2 value, one of them
with the pci bit set to 0 is preferred.
Handover
Power Control
Ciphering
Overload Control
Location Updating.
Mobile stations of different types have different capabilities within the network.
It is essential that the network recognizes the mobile station classmark when
initiating procedures for a specific mobile station.
There are three entities that provide classmark handling as shown in the
following table.
Note: The BSS can receive mobile station classmark information from both the MSC
and the mobile station. The information from the mobile station overrides
information from the MSC.
3.6.1 Classmark IE
The Alcatel 900/1800 BSS supports classmark 1, classmark 2 and classmark 3
IEs. The classmark 1 IE is always sent to the BSS when the mobile station
tries to establish communication.
Revision Level The revision level indicates either a phase 1 or phase 2 mobile station. It does
not distinguish between phase 1 and phase 1 extended mobile stations. If there
is an error in this field, then a default phase 1 is assumed.
RF Power Level The RF Power Level indicates the mobile station power capability.
For Alcatel 900:
Class 1 = 20W
Class 2 = 8W
Class 3 = 5W
Class 4 = 2W
Class 5 = 0.8W.
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 mobile station power capability is assumed to be the same as the
maximum transmit power allowed in the cell.
Support of A5/1 This field indicates whether the mobile station supports the A5/1 encryption
Encryption algorithm. If the A5/1 encryption algorithm is not supported, there is no
indication of other algorithms being supported.
Support of A5/2 This field indicates whether the mobile station supports the A5/2 encryption
Encryption algorithm. If the A5/2 encryption algorithm is not supported, there is no
indication of other algorithms being supported.
Impact on BSS and MSC The main difference between classmarks 1 and 2 for the BSS or MSC is the
support of the encryption algorithm. For procedures that require ciphering,
the BSS and MSC cannot recognize the mobile station ciphering capability if
only the classmark 1 Information Element was received. Therefore, there is
a classmark updating procedure.
Similarly, for classmark 3, the BSS and MSC do not recognize the mobile
stations multiband capabilities if only classmark 1 Information Element was
received. Therefore, a classmark updating procedure is required.
channel
required
switch to
SDCCH SABM +
rn + fn + cm
establish
indication
SCCP co
nnection
ion
connect
SCCP
H/SA CCH)
(FACC
confirm
5&6
+s ys info ark enauiry
pow er + TA classm
classmark change
classmark 2IE
classmark update
classmark 2IE
location update
(SDCCH)
cm : Classmark
FACCH : Fast Associated Control Channel
IE : Information Element
MS : Mobile station
RACH : Random Access Channel
SABM : Set Asynchronous Balanced Mode
SACCH : Slow Associated Control Channel
SCCP : Signal Connection Control Part
SDCCH : Stand-alone Dedicated Control Channel
TA : Timing advance
Figure 39: Location Update with Classmark Update
3.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 mobile station, 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 mobile station has changed location area, it includes the
old Location Area Identity. 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 the figure below.
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.
info IMSI +
Mobile Station moving and connecting request
in a new location area Ki
BTS BSC
Mobile
Station
The ciphering key is calculated from the authentication Key value assigned to
the IMSI or TMSI and the value RAND.
The mobile station responds using the RAND and the value authentication
Key assigned to its TMSI or IMSI.
For mobile station originated calls, the mobile station uses:
For mobile station terminated calls, the mobile station uses the TMSI or IMSI as
requested in the paging message from the network.
For emergency calls, the mobile station uses:
The TMSI, if available
The IMEI, if there is no TMSI or IMSI. This can happen when there is no
SIM in the mobile station.
If the TMSI was used, the network can request that the mobile station
sends its IMSI.
If this is a valid IMSI, but is different from the IMSI that the network
associated with the TMSI, the authentication procedure is restarted with
the correct parameters.
3.8 Ciphering
Ciphering is supported in the Alcatel 900/1800 BSS to protect information
transmitted on the Air interface. This includes:
User data
No encryption.
The two encryption algorithms are defined in GSM. If either is to be used, both
the mobile station and BTS must have the same encryption capability.
Mobile Station Capability The mobile station ciphering capability depends on whether it is a phase 1
mobile station, a phase 1 extended mobile station, or a phase 2 mobile station.
The following table shows the different mobile station ciphering capabilities.
Only phase 2 mobile stations can turn off ciphering or change the ciphering
mode during a channel change procedure such as a handover.
The ciphering capability of a mobile station is signalled to the BSS in the
mobile station classmark.
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
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.
The resulting value Kc is used to decipher the encrypted bit stream on the
downlink, by the mobile station, and on the uplink, by the BTS.
The ciphering capability of the BTS being used to set up the call.
If the mobile station 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 Ciphering is initiated by the MSC by sending a cipher_mode command to the
Mode BSC. This command contains the permitted_algorithms message.
The BSC compares the permitted algorithms with the mobile station
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 mobile station 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 mobile
station 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 mobile station.
The mobile station either:
mand
e com
ng mod
cipheri
s + Kc
orithm
ted alg
comm
and permit
tion
encryp
c or
m+K
and algorith tion
mm ry p
ng mode co no e n c
cipheri
H)
(SDCC
algorithm or
no encryption
cipheri
ng mo
de com
plete
cipher
mode
comple
te
MS : Mobile station
SDCCH : Stand-alone Dedicated Control Channel
Figure 41: Ciphering Procedure
Ciphering During Only phase 2 mobile stations can change ciphering mode during a handover.
Handover If a phase 2 mobile station 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 mobile station using the A5/1 algorithm needs to be handed over,
the target cell must support A5/1, as the phase 1 mobile station 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 mobile station to
use the ’no encryption’ option, as this is supported by all cells.
Without TFO
One GSM coding and decoding scheme (codec), is used between mobile
station 1 and Transcoder 1, then A/µ law coding is used (at 64 kbit/s)
between the two Transcoders and finally one GSM codec is used between
Transcoder 2 and mobile station 2. This means a loss of quality for the
speech call.
With TFO
The intermediate transcoding realized by the two involved Transcoders is
avoided. The same codec is used on both BSS. This improves the speech
quality of mobile-to-mobile calls, particularly when using the half-rate codec.
This allows the wide use of the half-rate codec, with a good level of speech
quality, in order to save resources in BSS.
The TFO procedure can be applied whenever the two mobile stations use the
same codec. To satisfy this condition, after TCH allocation, the two BSS
negotiate at each side a common codec (full-rate, half-rate or enhanced
full-rate), by using an in-band protocol in the speech frame. The following figure
shows an example of TFO call establishment.
BTS A BSC A TC A TC B BSC B BTS B
Channel activation Channel activation
TFO enabled PCM samples TFO enabled 1
TRAU frames TRAU frames
CON_REQ CON_REQ
DL_ACK
DL_ACK
TFO_REQ
2
TFO_REQ TRAU frames
TRAU frames 3
TFO_ACK
TFO_ACK
Codecs match
4
TFO_ON TFO frames TFO_ON
5
TFO REPORT (TFO STATUS= ON) TFO REPORT (TFO STATUS= ON)
The Alcatel TFO implementation is fully compliant with the GSM standard
and additionally provides:
As an operator s choice, the Alcatel BSS is able to force the distant BSS
(Alcatel or not) to overcome ETSI codec choice rules, in order to optimize
voice quality and load management. This mechanism is patented by Alcatel.
Codec optimization, to take into account that the two mobile stations may
use the same codec, but a better codec is available on both parts.
Same Codec Used on As the same codec is used on both sides, there is no TFO negotiation needed
Each Side between the TRAU.
Codec Mismatch, In this case, TFO communication is possible between the two BSS, but the
Negotiation Needed TRAUs do not use the same speech codec. TFO negotiation and resolution by
the BSS are needed. When detecting the mismatch, each TRAU sends to the
other (using TFO messages) the codec locally used, and the list of possible
codecs. At each side, the BSS determines the matching codec. On each BSS,
the same algorithm is implemented, this algorithm attempts to find a matching
codec using the information given by the TRAU. If a common codec can be
found, an internal intra-cell handover is performed to change the speech codec
locally used, and TFO exchange of speech stream begins. A logical parameter,
configurable at OMC-R level, allows the BSC to ignore the load in the cell
and to force the handover in order to solve codec mismatch situations. If no
common codec can be found, or internal intra-cell handover is not possible,
TFO mode is given up, and the system reverts to normal mode.
TFO Optimization For a better speech quality, TFO Optimization allows a new TFO negotiation
on an on-going TFO mobile-to-mobile call, to find a better common codec, in
terms of speech quality. Therefore, enhanced full-rate coding is considered to
be better than full-rate coding which is considered to be better than half-rate
coding. The Enable TFO Optimization feature can be enabled or disabled, per
cell, at the OMC-R.
In some cases, both parts may use the same codec, but a better codec is
available at each side and may be used (e.g., half-rate is used at both sides,
but full-rate is possible). The procedure is then the same as the modification of
speech codec in mismatch status, except that it takes place only when TFO
frames are already exchanged. The TFO messages exchanged between both
TRAUs are then embedded in TFO frames.
TFO Negotiation Control For a better traffic load regulation Alcatel has defined the function "Force
TFO half-rate when loaded" to give control to the operator of load regulation
precedence over TFO. This function can be enabled or disabled, per cell, at
the OMC-R, and allows the BSC to take into account the load in the cell while
building the list of supported codec types. If the cell is loaded, only half-rate (if
possible) will be included in the list. If the distant BSS supports TFO but not
half-rate, the function "Force TFO half-rate when loaded" allows the BSC in
this case to recompute the list of supported codec types by inserting full-rate
and enhanced full-rate in the list. Therefore, the function Force TFO half-rate
when loaded leads to three different behaviors, depending on three possible
values of corresponding flag:
TFO half-rate not forced. No filtering on the load is done. The load is not
tested and all the codec types supported by the call and by the cell are listed
in the supported codec type list
TFO half-rate only. Filtering is done on the load, half-rate is forced if the cell
is loaded and the mobile station supports half-rate, and if this codec type
is authorized in the cell. The list of supported codec types is restricted to
the half-rate codec type. As a consequence, if the distant part supports
half-rate, then the distant part will do an intra-cell handover to use half-rate,
and TFO will go on with half-rate. If the distant part does not support
half-rate, TFO will not be possible.
TFO half-rate preferred. Filtering is done on the load, but TFO is preferred
to half-rate. In the case of a load situation, only half-rate is sent in the list of
preferred codecs. But if the distant BSS does not support half-rate, a new
list is computed, without taking into account the load in the cell.
4 Call Handling
Overview
In-call modification
Frequency hopping
Discontinuous Transmission
Handover procedures
Overload conditions
4.1 Overview
An obvious requirement for the effective management of calls in the BSS
is to provide the following:
In-Call Modification
Frequency Hopping
Discontinuous Transmission
Handover
Overload Control
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 data rate change for fax is triggered by in-band signalling from the
fax machine to the MSC.
Mobile Station to Mobile For a mobile station to mobile station call, both mobile stations must negotiate a
Station Call dual service during call establishment.
The mobile station initiates the procedure by sending a layer 3 Call Control
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 mobile station 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 traffic
channel during call set up (described in Call Set Up (Chapter 3)), with the
following exceptions:
When the MSC receives the assignment_complete message from the BSC, it
sends a layer 3 CC modify_complete message to the mobile station. This
informs the mobile station that the procedure is successfully completed, and
the mobile station can start transmitting in the new mode.
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:
Non-Transparent Group For non-transparent fax transmission, the data rate change is handled within
3 Fax 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 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 Group 3 Fax 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 mobile station. When the
MSC receives the assignment_complete message from the BSC, it sets the
new data rate to the correspondent.
In-Call Modification For example, if the mobile station does not reply to the channel_mode_modify
Example 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.
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
Frequency Hopping, 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 Frequency Hopping improves transmission performance.
Interference Diversity Interference Diversity spreads the co-channel interference between several
mobile stations. 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
mobile station will experience the effects of such interference.
A MAIO. The MAIO indicates the initial hopping frequency of the traffic
channel within the FHS. Use of the MAIO ensures that each traffic channel
is assigned a different frequency during hopping.
TCH2 on TS2
f2 f3 f1 f2
MAIO=1
TCH3 on TS3
f3 f1 f2 f3
MAIO=2
f : Frequency
FHS : Frequency Hopping System
TCH : Traffic Channel
MAIO : Mobile Allocation Index Offset
HSN : Hopping Sequence Number
TS : Time slot
Figure 43: Frequency Hopping within an FHS
Continuous transmission
Discontinuous transmission.
Continuous Sound is continuously encoded into digital information even when no one
Transmission 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 Only actual speech is digitally encoded and transmitted. During the non-speech
Transmission 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:
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.
To eliminate the noise side effects generally known as banjo noise, the operator
can ban Discontinuous Transmission on the downlink for all calls that are
established on the BCCH TRX, without hopping, for all types of BTS. This is
achieved using the FORBID_DTXD_NH_BCCH parameter. The parameter can
be set to one of two values:
1. This bans Discontinuous Transmission on the downlink for all calls that
are established on the BCCH TRX.
Voice Activity Detection VAD is used to detect when there is speech, silence or just background noise.
The VAD device is located in the Transcoder. 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).
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:
Transmitted for traffic channels on the BCCH frequency, due to the need
for constant transmission on the BCCH frequency
Note: The BTS uses the measurement_result message to inform the BSC
that Discontinuous Transmission is operating. The BSC compensates for
Discontinuous Transmission when calculating power control and handover.
Option Description
Will perform This forces the mobile station to use Discontinuous
Discontinuous Transmission. It reduces the call quality but also
Transmission reduces interference in the cell and saves mobile
station battery power. During silent phases only
1 in 24 bursts are sent, which greatly reduces
interference.
Can perform This allows the mobile station to choose either quality
Discontinuous by not using uplink Discontinuous Transmission,
Transmission or power-saving by using uplink Discontinuous
Transmission.
Cannot perform The OMC-R operator has decided, due to low
Discontinuous interference, to have improved speech and
Transmission measurement control on the uplink side.
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.
Continuous Transmission
Discontinuous Transmission
DTX : Discontinuous Transmission
Figure 44: Different Forms of Discontinuous Transmission
Uplink link quality too low, or using power resources beyond quality
requirements of the call.
Similarly, the reasons for changing the BTS power control are:
Downlink link quality too low, or using power resources beyond quality
requirements of the call.
Measurement Description
Signal strength 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 on a particular channel.
BER is a standard quality calculation in radio
transmission.
Absolute mobile This is estimated by measuring the Time Of Arrival of
station-BS distance the received burst at the BTS for each allocated time
slot. The TOA is based on transmission distance
and not the actual ground distance travelled. The
calculation of one bit period (3.69 µs) 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 traffic channel is 104 TDMA frames (480 ms). The information is
transmitted in the SACCH frames.
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
start counter
conn
ectio
n fail
ure in
dicati
on
caus
e va
lue
clear
requ
est
e
leas
n el re
chan
RF
and
mm
r co
clea alue
se v
g cau
in
clud
MIE in
MS : Mobile station
TX : Transmitter
Figure 45: Power Control Flow of Measurement and Decision Action
Note: The signal and quality levels are converted into the ranges Received Signal
Level and Received Signal Quality respectively. Each range is classed from
0-63 (Received Signal Level where 63 is high) and 7 -0 (Received Signal
Quality where 7 is poor).
High Quality
The maximum power setting of a mobile station is based on two factors: its
classmark (its physical maximum power rating), and the maximum mobile
station power setting for the cell.
Each cell can limit the maximum power level for all mobile stations in the cell.
For example, a 20 W mobile station can be limited to 5 W maximum power if
that is the maximum mobile station power level allowed in the cell. However, a 1
W mobile station can never exceed 1 W, 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 mobile station
over the SACCH.
Changing power from one power level to another happens gradually. The power
level changes by 2 dB every 60 milliseconds, until the desired level is reached.
4.6 Handover
A handover changes an active call from one channel to another channel. The
new channel can be in the same cell or another cell. The types of handover are:
Internal
External
Directed retry
Internal
External.
Incoming emergency
Fast traffic
UMTS to GSM
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
mobile station 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, mobile station 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:
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 Target Cell Evaluation (Section 4.6.3).
External 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 Target
Cell Evaluation (Section 4.6.3) for more details about these handover cases.
Directed Retry Handovers can also be performed when there is congestion in a cell. If
congestion exists, the traffic channel assignment can be queued. For more
information about congestion management, refer to Congestion (Section 3.5).
If there is no available traffic channel for the normal assignment procedure, a
Directed Retry can be performed. A Directed Retry is an attempt to assign a
mobile station to a traffic channel in a cell other than the serving cell.
There are two types of Directed Retry:
Secured Incoming The ability to keep free resources in a cell for incoming emergency and power
budget handovers is provided on a cell basis. When the resource threshold is
reached, assignments and other handover types are handled as if the cell was
completely congested. Once such a request is queued, a directed retry can be
performed as usual. The free resources can also be accessed in the case of a
full-rate to half-rate handover in the case of AMR calls, because it allows half a
resource (full-rate to half-rate) to be freed from the cell point of view. The feature
improves the quality of service, as it helps to limit the number of lost calls.
Fast Traffic The fast traffic handover searches in the whole cell for a mobile which can
perform a handover to a not loaded neighbor cell if the received signal level of
the BCCH is good enough. It is much more efficient than the forced directed
retry when the overlap of adjacent cells is reduced, e.g., in the case of single
layer networks, or for deep indoor coverage (if the umbrella cell does not
overlap totally the microcells).
UMTS to GSM For circuit-switched services, the BSS supports handover from UMTS to GSM.
The handover from GSM to UMTS is not supported in this release of the BSS.
A hard handover is performed from the UTRAN to the GSM BSS between a
UMTS core network and a 2G MSC. This handover is regarded by the BSS as
a GSM inter-BSS hand over. The signalling procedures, from the BSS point of
view, rely almost on the normal GSM procedures.
For packet-switched services, the current 3GPP standard does not allow
handover with channel preparation. Therefore, the UMTS mobile station
receives the 2G radio resource cell change order Information Element from the
UTRAN in the Inter System handover message. The UMTS mobile station then
performs an access request in the GPRS cell. Therefore, from a BSS point
of view, the UMTS mobile station is regarded as a 2G mobile station when it
indicates that it has selected a GSM cell.
Measuring the received signal quality for active and inactive channels
The mobile station sends its measurements to the BTS in a layer 3Radio
Resource measurement_report message on the SACCH. The mobile
station 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 mobile station
Need for Handover The BSC calculates the need for a handover using an algorithm, the use of
which is described in Handover Detection (Section 4.6.2).
Traffic Channel Quality The BSC uses the uplink idle channel measurements made by the BTS to
Tables make a table of traffic channel channels, classified by interference levels. This
table is used to select a channel for assignment.
Target Cell List A target cell list can be made by the BSC using the neighbor cell BCCH
measurements sent by the mobile station. This is used to evaluate whether a
neighbor cell can provide a better channel than the existing one.
Handover Decision 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.
Better zone
Distance
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)
Signal level too low on the uplink or downlink inner cell (concentric cells
only).
High Quality
123456 123456789
123456
123456 123456789
123456789
Level 123456 123456789
Intercell 123456 123456789
Power Desired Power
123456
Improve 123456789
Conserve
123456 123456789
123456
12345612345678901234
123456789
12345678901234
12345612345678901234Power Increase to
123456
123456 12345678901234
improve quality
12345678901234
Quality Intercell Quality Intracell
Handover Handover
Low Quality High
Level
Low Level
Received Signal Level
Figure 47: 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.
Quality Intercell The Quality Intercell Handover area represents the range of measurements
Handover 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 The Quality Intracell Handover area represents the range of measurements
Handover 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.
High Power
Outer Zone
Low Power
Inner Zone
MS Handed
Over to
Low Power
Zone
MS : Mobile station
Figure 48: Better Zone Handover
1234567890
1234567890
1234567890
1234567890
1234567890
1234567890
1234567890
1234567890
1234567890
BSS 1 BSS 2
1234567890
1234567890
1234567890
1234567890
1234567890
1234567890
A call transferred from the umbrella cell to the lower layer cell, just before
reaching the limit of that cell
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 mobile stations 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. The following figure shows a
graph of umbrella cell load and minimum dwell time.
Load in Umbrella Cell
Speed
Macrocell discrimination
saturated disabled
High load
Traffic
regulation
Low load
Max speed Macrocell with
discrimination little traffic
in force
Preferred-band handover
This parameter must be defined for each cell where multiband power budget
handovers are required.
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:
Power budget
HO_MARGIN parameter
Handover cause.
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.
Internal (IntraBSS): If the target cell is not the same as the serving cell but is controlled by the same
Intercell 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.
External (InterBSS): If the target cell and the serving cell are not controlled by the same BSC, but the
IntraMSC two BSC are controlled by the same MSC, this is called an interBSS intraMSC
handover. This handover is controlled by the MSC.
External (InterBSS): If the target cell and the serving cell are controlled by different BSCs and the
InterMSC 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.
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 mobile station 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 mobile station
accesses the target cell.
For an asynchronous handover, the mobile station has to synchronize with
the target cell before transmitting any user traffic.
4.6.4.1 Synchronous Internal Handover
This section describes the message flow for a synchronous internal handover.
The example in the figure below is for a handover of a traffic channel between
two separate cells controlled by two BTSs in a collocated configuration.
Target Serving
MS BTS BTS BSC MSC
measu
remen
t report
s (S
ACC H)
measu
re ment re
s ults
HO detect
HO alarm
cell evaluation
quest
text re
al con
physic
physic
al con
text
confirm
TA + p
ower
vation chann
el
el acti
chann + power +
DTX
ipher +
TA + c
chann
el acti
vation
ack
d
mman nel
ver co + chan
hando cipher
TA +
ell desc +
er + c
f + pow
HO re
release with
serving BTS
acces
s burs
t (SAC
CH)
hando
ver de
tection
SABM
establi
sh ind
ication
hando
ver co
mplete
hando
ver pe
rforme
d
Measurement Reporting The mobile station and BTS take measurements on the Air interface as
described above. The mobile station sends measurement information to the
BTS in a measurement_report message. The BTS sends mobile station and
BTS measurements to the BSC in a measurement_results message.
Handover Detection 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.
Channel Activation When the BSC receives the physical context information, it sends a
channel_activation message to the target BTS, indicating:
The target BTS sets its resources to support the channel. It then uses a
channel_activation_acknowledgment 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/FACCH frames so that when the mobile station
accesses this BTS, it receives sys_info 5 and sys_info 6 messages. The
mobile station also receives the timing advance and power control updates.
Handover Command The BSC sends the handover_command message transparently through the
BTS to the mobile station. This message contains:
The new channel and its associated control channel
A power level indication for the mobile station initial access to the target cell
A handover reference
The Handover The mobile station 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 mobile
station timing advance needs to be updated, the BSC sends this information in
the physical_information message on the FACCH channel associated with
the traffic channel.
The mobile station 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 mobile station, it sends an
acknowledgment frame to the mobile station and an establish_indication
message to the BSC. This informs the BSC that the radio link has been
established. The BSC starts BTS and mobile station power control.
On receipt of the acknowledgment frame, the mobile station sends a
handover_complete message to the BSC. The mobile station 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.
measurement repo
rts
(SACCH)
measurement resu
lts
HO detect
HO alarm
handover required
est
handover requ
on
channel activati X+cause+cm
her+cell IDs+DT
channel type+cip
SACCH/FACCH
+ handover com
mand
handover command
mand
handover com
d ch+cell+HOref+cipher
handover comman
release with
serving BTS
Synchronization handover detect
(FCCH + SCH)
set up switching
path between Abis
& A interfaces
physical info
(FACCH)
physical info
establish indication
ack
(FACCH)
handover complete
handover performed
d
clear comman
Measurement Reporting The mobile station and BTS take measurements on the Air interface as
described above. The mobile station sends measurement information to the
BTS in a measurement_report message. The BTS sends mobile station and
BTS measurements to the BSC in a measurement_results message.
Handover Detection 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 a mobile station is going to be handed
over. This message contains:
Channel type required
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_acknowledgment
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_acknowledgment message. The handover
command contains:
A handover reference
Any cipher mode information (phase 2 mobile stations can change cipher
mode during a handover procedure).
The Handover The mobile station releases its connection to the serving BTS. It synchronizes
with the target BTS using the FCCH and SCH information. Once synchronized,
the mobile station 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 mobile station 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 mobile station’s first frame and sends an
establish_indication message to the target BSC, and an acknowledgment to
the mobile station. On receipt of the acknowledgment, the mobile station 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.
Note: The telecommunications processors of the MSC can also become overloaded.
However, MSC overload control is not the domain of the BSS.
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 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.
BTS Overload Action 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.
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.
BSC Local Overload Local action in the BSC is taken by the local overload controller on each
Action processor. Local actions reduce the load on an individual board. The local
actions are:
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.
Mobile Station Access When the BSC receives a request for global overload action from a BTS, from
Class Barring 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
mobile station 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 mobile station 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:
The number of access classes that can be barred and unbarred in one step can
also be configured from the OMC-R.
Mobile Station Access When an overload message is received from the BTS or when an overload is
Class Unbarring 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.
5 Call Release
Overview
Following Reset
BSC initiated
BTS initiated
Mobile station initiated
This chapter also describes Remote Transcoder Alarms, and the processes
used to break a connection and disconnect the resources, depending on the
nature of radio transmission.
5.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 modified and the resources for the original channel are released
There is a failure
MSC resources:
Layer 3 for the A interface
SS7 signalling for the A interface
Layer 1 physical resources for the A interface.
BSC:
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.
BTS:
Layer 3 for the A, Abis and Air interface
Layer 2 LAPD for the Abis interface and LAPDm for the Air interface
Layer 1 physical resources for the Abis and Air interface.
Mobile station:
Layer 3 for the Air interface
Layer 2 LAPDm for the Air interface
Layer 1 for the Air interface.
Special cases, including detailed behavior of the MSC, BSC, BTS and mobile
station are described later in this chapter.
discon
nect (la
yer 3 CC)
3 CC)
(layer
uest
release req
release
comple
te (layer 3
CC)
MS : Mobile station
Figure 54: Mobile Station Disconnecting a Call
Once the MSC has confirmation that the mobile station wants to disconnect and
no longer requires the connection, it initiates the release procedure towards
the BSC. This procedure:
The BSC responds to the MSC to clear the connection on the A interface, and
initiates the Call Release procedure toward the BTS and mobile station. This
procedure releases the radio resources.
This action triggers the mobile station to release the LAPDm connection (disc
message) and the BSC to release physical resources allocated to the call.
This is shown in the following figure.
MS BTS BSC MSC
nd
omma
clear c
alue
ause v
cluding c
MIE in
ase
el rele
chann release of A
CH
AC interface resources
vat eS
deacti Timer start (SCCP release)
clear c
omplete
disc
disable remote Timer start (release indication)
(to re TC alarm detect
lease
LAPD
m) ed
relea releas
se in SCCP
UA dicati
on
SCCP
release
comple
te
t
reques
c ontext
physical
physic
al con Timer
text co
nfirm
lease
nnel re
RF cha
RF ch
annel
Timer
releas
e ack
MSC actions The MSC initiates Call Release at the end of the mobile station transaction.
The MSC can be informed of the end of the mobile station transaction:
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.
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.
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 the following figure.
MS BTS BSC MSC
nd
omma
clear c
e
e valu
g caus
cludin
MIE in
ase
el rele
chann release of A
C CH interface resources
SA
ate Timer start (SCCP release)
ctiv
dea clear c
omplete
SCCP
release
comple
te
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/Mobile Station The normal Call Release procedure towards the mobile station/BTS releases:
Interactions The radio resources associated with the call
The BSC receives the release_indication message and stops the timer.
nd
omma
clear c
alue
ause v
cluding c
MIE in
ase
el rele
chann CH release of A
te SAC interface resources
c tiva
dea Timer start (SCCP release)
clear c
omplete
disable remote
disc TC alarm detect Timer start (release indication)
(to re
lease
LAPD ed
m) releas
SCCP
relea
se in
UA dicati
on
SCCP
release
comple
te
Once the BSC considers the mobile station disconnected, it initiates release
of the RF channel from the BTS. In a normal call release procedure, this
occurs following the release of the mobile station from the Air interface (as
described earlier in this section).
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 acknowledgment, the BSC releases all resources for the RF
channel. This is shown in the following figure.
MS BTS BSC MSC
relea
UA se in
dicati
on
quest
text re
al con
physic
physic
al con
Timer
text co
nfirm
e
releas
annel
RF ch
RF ch
annel
Timer
releas
e ack
MS : Mobile station
UA : Unnumbered Acknowledgment
Figure 58: 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).
handover perform
ed
and
comm
clear lue
se va cau
ding
inclu
MIE
ase
el rele
chann
CH
AC
te S
ct iva
dea
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:
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. The figure below
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.
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
reset
SCCP
e releas
l releas e
channe circuits blocked
te
comple
release
disc SCCP
e SCCP re
to relea l releas lease
se LAP
Dm channe
release
indicatio
n
lete
omp
t request rele ase c
ntex CCP
physical co S
disc
to re physic
leas al con
e LA text co
PDm nfirm
rele
indic ase
atio nnel
n RF cha
release
RF channe
l release
ack
l
physica request
context
physical
context
confirm
lease
nnel re
RF cha
RF chan
nel relea
se ack
timer
reset a
ck
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 BSC-Initiated Release (Section
5.3.2) for more details.
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 Normal Release (Section 5.2.1)). The procedure starts
with the BSC releasing A channel resources. It initiates the release procedure
towards the mobile station (if still attached), and returns a clear_complete
message to the MSC. This sequence is shown in the following figure.
MS BTS BSC MSC
clear
requ
est
and
mm
r co
clea alue
se v
cau
ing
includ
MIE
Towards the Mobile The Call Release procedure towards the mobile station/BTS releases:
Station/BTS The radio resources associated with the call
The RF channel.
The release of the mobile station from the Air interface (as in the Normal
Release procedure)
A handover, when the BSC is sure that the mobile station has successfully
changed to the new channel. Refer to Calls Terminated Following a Channel
Change (Section 5.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 traffic
channel is available for reuse as quickly as possible.
Failed Release If there are no resources allocated to a call and the normal release of the SCCP
Procedure connection has failed, the BSC forces the release of the SCCP connection:
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.
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:
LAPD Failure When the BTS detects an LAPD failure on a link between one of its frame units
and the BSC, it forces the release of all mobile stations on active channels
associated with that Frame Unit (TRE for a BTS A9100 or BTS A910).
The BTS stops SACCH frames and sends a layer 2 disconnect message to
each affected mobile station. It also starts a timer to supervise each LAPDm
disconnection. The LAPD connection cannot be re-established until the BTS
receives an acknowledgment, or the timer expires for each LAPDm connection.
If a mobile station sends an acknowledgment, the BTS releases the RF
resources.
If a mobile station 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 mobile stations 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 the following figure.
Detection of LAPD
failure. BTS stops
sending SACCH frames.
disc
timer
disc
timer
disc
timer
UA
UA
release RF resources
UA
release RF resources
release RF resources
Re−establish LAPD connection
error
repo
rt
caus
e valu
e
d
mman
clear co
se va lue
cluding cau
MIE in cl
ear compl
ete
FU : Frame Unit
LAPD : Link Access Protocol on the D Channel
MIE : Mandatory Information Element
MS : Mobile station
SACCH : Slow Associated Control Channel
TRE : Transmitter/Receiver Equipment
UA : Unnumbered Acknowledgment
Figure 62: BTS-initiated Call Release following LAPD failure
O&M Intervention The BTS initiates a Call Release if its O&M entity requests a restart of an
Frame Unit (TRE for a BTS A9100 or BTS A910).
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 mobile stations. The timer allows enough time for the mobile stations
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.
Mobile Station-Initiated If SACCH frames are no longer received from the mobile station, the BTS starts
Radio Link Failure 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 mobile station ’disappears’ from the Air interface
(caused by adverse radio conditions, the mobile station is switched off, fatal
error, etc.).
Note: There is an optional feature where, after a number of missing SACCH frames,
the BSC sets both mobile station 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 below.
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 the following figure.
MS BTS BSC MSC
start counter
conn
ectio
n fail
ure in
dicati
on
caus
e va
lue
clear
requ
est
as e
e l rele
ch ann
RF
and
mm
r co
clea alue
se v
cau
lu d ing
inc
MIE
TC detects a communication
break and times out
Alarm
conn
ectio
n fail
ure in
dicati
on
caus
e valu
e
clear
requ
est
e
leas
el re
chann
RF
and
mm
r co
clea alue
se v
g cau
inc ludin
MIE
This chapter describes the flow of speech and data traffic across the BSS. It
describes:
Overview
How speech is encoded and rate adapted throughout 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.
6.2 Speech
Speech is passed from the mobile station to the PSTN and from the PSTN to
the mobile station. This section describes how speech is encoded from the
mobile station to the PSTN, as shown in the following figure. Speech in the
opposite direction follows the reverse process and so is not described.
Full Rate Speech TCH
Mobile
Station
Interleaving and Forward To pass speech over the Air interface, error checking and redundancy are
Error Correction 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).
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.
Digital Speech Speech bursts are returned to digital speech blocks in the BTS. They are sent
to the Transcoder 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 the figure below.
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 submultiplexing
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.
Ater Interface Ater−mux Interface Ater Interface A Interface
BSC SM SM TC MSC
Enhanced Full-Rate Enhanced full-rate is enabled in the BSC, on a cell-by-cell basis, by the O&M
Process parameter EFR_ENABLED. When an enhanced full-rate call is set up, the
following processes occur:
The mobile station 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
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 mobile station which
codec it should use when accessing the new channel.
Once the mobile station 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.
6.2.2 Half-Rate
Half-rate speech channels allow the operator to save time slots on the air
interface when the number of available frequencies is very limited. Half-rate
uses a different encoding algorithm than full-rate, in order to minimize any
perceived loss of comfort by the subscriber. Use of the half-rate feature does
create extra overhead on the A interface.
Half-rate is activated on a per-cell basis. In effect, the cell is capable of
operating in Dual Rate\mode, permitting either half-rate or full-rate traffic
channels to be allocated.
Half-rate can be applied to BSSs with the following equipment:
G2 BSC
G2 Transcoder
Enhanced full-rate brings a higher speech quality than full-rate but with
no noticeable impact on capacity.
AMR is a new technology defined by ETSI which relies on two extensive sets of
codec modes. One has been defined for full-rate and one for half-rate. When
used in combined full-rate and half-rate mode, AMR brings new answers to the
trade-off between capacity and quality:
Full-rate mode only, for operators who do not face capacity issues and want
to benefit from the optimized quality of speech.
Combined full-rate/half-rate mode, for operators who want to benefit from
the above defined trade-off between quality of speech and capacity.
Through these codec mode adaptations, AMR is able to adapt the sharing of
speech information and speech protection to current radio conditions, which
can vary in a large scale, depending on location, speed, and interference.
Therefore, for any radio conditions, the Alcatel BSS is able to offer the best
existing codec, thus the best existing voice quality.
AMR functionality can be activated by configuration of the cells and the BTS
radio resources in all the network elements (OMC, BSC, BTS). The relevant
algorithms are activated on a call by call basis. On the radio interface, the AMR
can only be used with AMR mobiles. On the A interface , the AMR can only
be used if the NSS implements it.
The AMR capability is available on a cell by cell basis.
Normal Assignment AMR is controlled on a per call basis by the MSC. In the assignment request
message, the MSC gives the Channel type IE, which indicates the following:
The BSC activates the channel in the BTS by sending a channel activation
message, containing the IE Multirate configuration. It indicates the subset
of codecs used for full-rate (or half-rate, respectively) link adaptation, the
threshold and hysteresis sent to the mobile station for full-rate (or half-rate,
respectively) link adaptation and, optionally, the start mode (i.e. the initial codec
mode). If the initial codec mode is not given, the BTS chooses the default start
mode depending on the number of codec modes contained in the subset. Once
the channel is activated within the BTS, the BSC sends all AMR relevant
parameters to the mobile station in the assignment command message.
When the speech path is established and synchronization is performed between
the Transcoder and the BTS, the BTS checks if the Request or Indication
Flag (RIF) given in the TRAU frame is coherent with the type of Codec
Mode (Indication or Command) that should be sent on the radio interface. If
necessary, a CMI_CMR alignment command is sent to the Transcoder. Once
the BTS detects that downlink CMI/CMR is synchronized between the TRAU
frames and the radio interface, it starts codec mode adaptation.
O&M Management This section summarizes the main O&M configuration parameters that can be
changed by the operator from the OMC-R:
AMR_SUBSET_FR Bitmap of 8 bits defining the codec subset for AMR full-rate
(1 to 4 codecs out of 8), on a per BSS basis.
AMR_SUBSET_HR Bitmap of 6 bits defining the codec subset for AMR half-rate
(1 to 4 codecs out of 6), on a per BSS basis.
EN_AMR Flag on a per cell basis to enable or disable AMR. This single flag is
used for AMR full-rate and AMR half-rate.
Full-Rate Channel This channel adaptation involves ongoing AMR full-rate communications within
Adaptation Due to High cells where half-rate is enabled. During any AMR call, the downlink radio quality
Radio Quality is reported by the mobile station through the RX_QUAL. In the same time, the
uplink radio quality is evaluated by the BTS through the RX_QUAL, and both
are compared to a load dependent threshold. Indeed, in a cell heavily loaded,
a half-rate channel will be preferred even with a bad quality. Whenever both
uplink and downlink radio quality are higher than this threshold, then an intracell
handover takes place from full-rate to half-rate channel. To take into account
the load, two different threshold values are used. The change will also only be
performed if the current channel type is dual rate and it authorizes changes.
Half-Rate Channel This channel adaptation involves ongoing AMR half-rate communications,
Adaptation Due to Low using a dual-rate channel type authorizing changes. During any such AMR
Radio Quality call, the downlink and uplink radio quality are evaluated with the same
metrics as stated for the full-rate channel adaption, and the same threshold
comparison is performed. If either uplink or downlink radio quality are lower
than this threshold, then an intracell handover takes place from half-rate to
full-rate channel. To take into account the load, two different thresholds are
also used but they differ from the ones used in full-rate adaptation by an offset
value which is also cell load dependent. This offset allows a hysteresis to be
introduced between full-rate and half-rate channels.
Non-transparent.
Mobile
Station
V.110 data blocks ISDN
/Analog
A 13 kbit/s CIM 13 kbit/s 64 kbit/s A/D
A : Analog
A/D : Analog/Digital
BIE : Base Station Interface Equipment
CIM : Channel Encoded, Interleaved, and Modulated
PSTN : Public Switched Telephone Network
SM : Submultiplexer
TC : Transcoder
Figure 67: Data Transmission Across the BSS
Rate adaptation.
Interleaving and Channel Interleaving for data is more complicated than for speech. The data block is split
Coding 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.
The table below 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 the table below for the rate
conversions. The Transcoder 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 byte. PCM transmission is at 8 000
bytes (64 kbit/s). The 8 kbit/s and 16 kbit/s intermediate rates (before the
Transcoder) are transposed as 1 or 2 bits per byte respectively.
Table 20: Circuit-Switched Data Rate Conversions Across the Air Interface
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 (LAPD).
Rate Adaptation 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 Transcoder, but not to the BTS. The Transcoder,
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.
OMC−R HMI
Broadcast
Message to
Selected SMS−CB
Cell(s) commands
and signaling
BTS BSC
Message
broadcast to all SMS−CB
Transmission commands
Mobile Stations Request and signaling
CBC
The SMS-CB is managed and operated from a separate CBC. The CBC is
connected to the BSC and the data needed to connect the BSC to the CBC is
sent from the OMC-R.
The operator at the CBC inputs the cell broadcast message 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 CBC to the BSCs handling the selected cells. The
BSCs then send 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 mobile stations in the cell over the Cell
Broadcast Channel of the Air Interface.
For SMS-CB, the BSC supports only the connection to an external CBC
platform. The SMS-CB implements all of the improvements of the phase 2+
recommendations.
Phase 2+ Enhancements An external CBC can be connected directly to the BSC. This allows the BSC to
send information to the CBC, e.g., billing information. Two types of connection
can be used to connect the CBC to the BSC:
Better service availability through the restart with recovery indication feature.
The feature brings also better convenience with the support of multipage
messages.
The localized service area concept gives the operator the basis to offer
subscribers or groups of subscribers different service features, different tariffs
and different access rights depending on the location of the subscriber.
It is up to the operator to decide which services features are required for
a specific service.
The LSA (Localized Service Area) can be considered as a logical subnetwork
of the operator‘s PLMN. This subnetwork can be configured by the operator.
A subscriber can have LSA‘s at several PLMN‘s. The following list shows
examples of different types of localized service area:
Office indoors. The office cells are those that are provided by indoor base
stations.
Home or office and its neighborhood. The localized service area can be
broadened outdoors. The neighborhood cells outdoors can be included
into the local service area.
Industry area. A company having several office buildings may want to have a
localized service area that covers all its buildings and outdoor environments.
7 Cell Environments
This chapter describes the cell environments available in the Alcatel 900/1800
BSS. The following cell environments are described:
Overview
Single Cell
Concentric Cell
Sectored Site
Extended Cell
Umbrella Cell
Mini Cell
Microcell.
Indoor cell
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. The BSS
supports a set of cell configurations to optimize the reuse of frequencies. The
operator may choose to deploy a network using both GSM 900 and DCS 1800
bands. The parameters to define cells are grouped into five types:
Cell Coverage. There are four types of coverage, single, lower, upper,
and indoor.
Cell Band Type. A cell belongs to either the GSM 900 or DCS 1800 bands,
or both in case of a multi-band cell.
Rural and Coastal In the rural and coastal environment coverage is principally a function of cell
Coverage planning. Standard cell layouts provide coverage of up to 35 km. 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.
Indoor cells.
These three 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 and indoor
cells. See Umbrella Cell (Section 7.5) for more information.
The figure below 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.
Inner Zone
Outer Zone
Single Cell Concentric
Cell
Sectored Site
Umbrella Cell
Microcell
Microcell
Umbrella &
Microcell Concentric
Cell
Microcell
Extended Cell
Inner Cell
Outer Cell
Sector
1
Cell 1
BTS
Cell 2 Sector
2
Cell 3
Sector
3 Antenna
Inner Cell
Highway
Urban Area
70 km
max
Outer Cell
35 km
max
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:
Carrier Unit 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 a mobile station 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 mobile stations
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 mobile
station, that it is actually in the inner cell, and assigns the mobile station
to an inner cell SDCCH frequency.
The outer cell uses one Carrier Unit with reception delayed by 60 bits. This
effectively shifts the logical position of a mobile station 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.
Different types of coverage are possible depending on the type of antenna
used for the inner and outer cells. The example in the figure above shows an
extended cell with an omnidirectional inner cell and directional outer cell.
Enlarged Extended Cell The enlarged extended cell is an extended cell designed to provide enlarged
capacity for areas where sustained traffic is high. It is especially well-suited for
rural areas and dense highways where more than one TRX is necessary to
handle traffic.
The enlarged extended cell relies on the general principles of the extended
cell: it is made up of two sub-cells to handle calls up to a distance of 70 km.
However, with enlarged extended cell the two sub-cells are covered by one
BTS, assuring a higher synchronization rate.
The following telecom features are supported:
The TDMA frame time slots can be used independently, providing any
TRX with full capacity
Inner cell mobile station access requests use the outer cell BCCH frequency
Pedestrian area
Mini Cells
Urban area
Figure 72: Umbrella Cell with Mini Cells
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:
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.
Low Threshold This type of handover occurs when the mobile station level is under the high
Handover threshold and the signal level has dropped below the low threshold. The
handover is to the umbrella/macrocell, which supports the call until the mobile
station moves into another cell. When the macro to micro threshold is exceeded
in the umbrella/macrocell, the mobile station is passed to a new microcell.
Rescue Handover The mobile station is forced to handover to the umbrella cell when no
measurement reports are transmitted. This occurs after a number of
consecutive SACCH reporting periods.
Note: If the low threshold is not used, the M_to_m Threshold value must be above the
high threshold value.
1
Micro−Micro
Handover
2
High Threshold
d 3 4 6
B M_to_m Threshold
m
Low Threshold
5
Secondly, to unloaded the cells provided for outdoor coverage but which are
accessible from these buildings.
Indoor cells can be deployed in all types of network, even in already very dense
networks which already have two layers (upper and lower). The feature eases
the optimization of multilayer networks which include cells dedicated to indoor
coverage. Indoor coverage is performed mostly from outdoor BTS. Although
already satisfactory in many cases, the indoor quality of service can be
improved by using dedicated in-building equipment. Together with this improved
quality, an increase in the indoor capacity can be achieved, particularly in high
density public areas such as airports, train stations, shopping malls, business
parks, etc. A three layer per band management is introduced and a new type
of cell is defined (the indoor cell) that maximizes traffic in these indoor cells
while preserving quality. In idle mode, classical criteria (C2) allows mobiles to
be forced to camp on indoor cells.
For example, when entering a building covered by an indoor cell, calls are
automatically transferred from outdoor cells, whatever their type. When moving
inside the building, calls are transferred from one indoor cell to another one,
even if the received power from outdoor cells is higher. It is only when the
mobile leaves the indoor coverage that it is transferred to an outdoor cell.
It is important for the Operator to minimize interference from indoor to
outdoor. Therefore, indoor cells will often be used with very low radiated
power (picocells). In this context, the feature provides also enhanced Power
Control algorithms.
The cells added to the network for indoor coverage are referred as indoor cells
and form a new layer referred as the indoor layer. The following figure gives an
example of network structure with three layers and two bands.
Figure 74: Indoor cell example network hierarchy with three layers and two bands
If there was only one layer, cells having the cell_layer_type single will
become upper. New cells introduced for the indoor layer will belong to the
indoor layer. There is no lower layer.
This chapter provides an overview and describes O&M functions in the context
of an operational network. It describes:
Overview
Configuration Management
Audits
Remote nventory.
This chapter does not describe the principles of O&M. For more information
about O&M, refer to the Operations & Maintenance Principles document.
8.1 Overview
To ensure that the BSS operates correctly, O&M actions are implemented at
all levels within the BSS. The O&M functions in the BSS are grouped into
three categories:
Configuration Management
Fault Management
Performance Management.
Configuration Management
The main benefit of configuration management is the reduced time needed
to perform operations and reduce telecom outages. This is achieved by
having fewer operator commands and providing smooth migration and
equipment configuration. The main functions of configuration management
include radio configuration management and equipment management.
Fault Management
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 BSC and Transcoder provide together a set of transmission O&M
functions to ensure a high level of fault tolerance and reliability. The
function also provides efficient use of the terrestrial links between the
equipment of the BSS.
The MFS, like the BSC, supervises its own hardware modules and
reports changes in status to the OMC-R.
Hardware and software management of the MFS is provided using
the IMT.
The OMC-R is the primary control station for the BSS/MFS and is
the heart of the O&M function.
Performance Management
Performance Management consists of three main system activities:
The collection of raw measurement data from network elements by
the BSC and the MFS
The transfer of the raw measurements to the OMC-R
The processing of the raw measurements and presentation of the
results on the OMC-R.
Managed Objects Managed Objects are used to represent elements of the Telecommunication
TMN environment on the Q3 interface in terms of system resources. This
concept is also used to represent the activities of management function blocks
performed on these resources.
In Alcatel’s network management model, Managed Objects can be physical
entities, such as a BSS, BTS, BSC, or a hardware module within one of these
entities. They can also be a logical entity, such as programs or program
routines which implement communication protocols.
Security Blocks Alcatel has an internal object model structure, based on objects called
Security Blocks. Security Blocks are only used for the BSC, the BTS, and
the Transcoder. Security Blocks are only visible to an operator performing
local maintenance using certain LMTs, i.e. BSC terminal, BTS terminal, or
transmission terminal. The SBL model is not used by the OMC-R or the IMT.
The OMC-R can display SBLs in certain circumstances, e.g. in BSSUSM.
Fault Management Fault Management allows the operator to supervise and to repair the network
when anomalies occur. It does this through a sequence of steps from
detection to reporting and recovery. These are carried out by all the BSS/MFS
subsystems, and are reported to the operator at the OMC-R.
Performance Performance Management allows the operator to monitor the efficiency of the
Management system and the telecom services. It is controlled entirely from the OMC-R
and provides measurements and statistics about various traffic events and
resource usage in the BSS.
Providing mediation between the Alcatel BSS and one or more NMCs.
This uses the Q3 interface.
Central Site
Additional
Printer
Workstation
X.25 Network
OMC−R OMC−R
Host 1 Host n
OMC−R
Host 2
Central Site The site used for multiple access contains the following:
Configuration Printing facilities
8.3.2 ACO
Alarm Call Out (ACO) is a process within the HMI server to perform alarm
management tasks for a complete network. Alarms from the BSSs controlled
by other OMC-Rs are directed to one OMC-R. These links are used to transfer
alarm notifications from the controlled OMC-Rs to the ACO OMC-R as shown in
the figure below. The ACO OMC-R collects alarms from these OMCs, applies
filters defined by the on duty operator, sends the filtered results to a dedicated
printer and sends e-mail to support technicians.
ACO can be started and stopped from any OMC-R.
ACO OMC−R
Workstation
OMC−R 3
OMC−R 1 Area 3
Area 1
OMC−R 2
Area 2
OMC−R
X.25 Network
BSC A
CMISE BSC A CMISE
HSI 0 OSI CPRA 1
BOARD
1
2 FTAM BSC A FTAM
3 OSI CPRA 2
Definition of the primary and the secondary links based on their hardware
configuration can achieve various types of redundancy, such as:
Complete redundancy.
OMC−R
X.25 BSC
Network Primary Link
HSI 0 OSI CPRA 1
Board
1 1
2 2
OSI CPRA 2
3 3 Secondary
Link
If the secondary link is in traffic, it becomes the active link and the
association is tried on this link.
Standard, Large, and The license for the documentation collection and Verity search engine is
XLarge Configurations installed on one OMC-R. All other OMC-R on the same site are connected
to this OMC-R. The maximum number of users that can be managed for
each search engine license is 75. This corresponds to a site with five Large
configuration OMC-R.
Refer to A1353-RA Capacity per BSS Category for more information on the
various OMC-R configurations.
MFS
Reading and modifying parameters
BTS/SUM power up
BTS reset
OMU reset/auto reset
The BTS A9100 and the BTS A910 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.
For more information, refer to the BTS Functional Description and the BTS
Terminal User Guide.
Consistency Checks When a new Configuration Data Message is received from the BSC, the BTS
A9100 and the BTS A910 performs a consistency check of its capabilities
against the Configuration Data Message. It also does this at module
initialization due to maintenance operator command or to a Hardware Extension
operation. The BTS A9100 and the BTS A910 also checks that the received
OMU Configuration Parameter Data File is valid for this generation of BTS.
Consistency checks are also performed by G1 and G2 BTS.
For more information, refer to the following:
The feature allows one extra time slot to be used for signalling (if no G1/G2
BTS are present on the Abis interface). This provides an increase of telecom
traffic on one Abis (because there are no time slots dedicated to the Qmux).
The OMC-R operator no longer needs to know on which time slot is the
OML, and no longer needs to configure it manually.
8.4.6 NE Provisioning
Network element provisioning allows equipment that is not yet in commercial
use to be distinguished from equipment that is under maintenance. This is mot
important for network monitoring. The feature introduces the status "commercial
use" that can be associated to the BTS. This status is changeable online from
the OMC-R. It is also available at the radio configuration export/import interface
of the OMC-R for coordination with the operators‘ information systems. For the
BTS marked as "not in commercial use", potential alarms are raised with only a
"warning" severity and the performance measurement results are not taken
into account. The BTS marked as "not in commercial use" are not reported
in the topology files sent to the A985-NPA and A956-RNO. They can be also
filtered from the supervision view.
Previously, as soon as a BTS was declared, it was supervised, but this raised
permanent alarms when the BTS was not physically connected. If cells were
created on this BTS, PM cell measurements were running on the BTS, and this
lead to very poor PM results as the BTS was not in commercial service.
An attribute (commercialUse = On or Off) is associated to each BTS. The
attribute can be changed from both the SC and the PRC radio network level
to mark the BTS as out of commercial use, or in commercial use. When this
attribute is set (i.e. the BTS is out of commercial use), all alarms related to the
BTS have a severity maximum equal to a warning (except for the alarms from
the MFS). At the OMC-R, the operator still sees all of the alarms and alarm
states, and is able to trigger all O&M commands, as usual. This allows the
operator to be aware of the fault situation of the BTS, but does not give a false
status of the network. There is no PM handling and storage for the BTS that are
marked out of commercial use (except for the PM counters that are relative to
RSL/OML traffic which are not filtered).
BTS
Testing of the equipment. This includes collecting
alarms and reporting to the BSC.
Event
An Event occurs when an unexpected situation arises during system
operation.
Filtering Alarms are filtered to minimize the number of fault alarms reported and
displayed to the operator. Alarms are displayed in order of severity.
Refer also to the Alarm Handling section of the Operations & Maintenance
Principles document.
Persistency A fault is signalled only if there is no recovery after the timer expiration. For
example, in the case of an LAPD failure of an RSL link, an alarm is sent only if
the LAPD link has not recovered before the persistency timer has expired.
Alarms-in-Force List Each BSS component keeps an Alarms-in-Force List, 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 Alarms-in-Force Lists
for each BSS component.
Processor Failure The active S-CPRA creates a daisy-chain map of all the processors in the
BSC. Every ten seconds, 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 FLT state.
The S-CPRA signals the processor failure to the OMC-R as follows:
If the processor failure is in the TCU, recovery only takes place to ensure
BCCH functionality.
If a DTC processor fails, the BSC tries to inform the MSC, so that the MSC
is aware the SS7 link is out of service. This implies:
The loss and, if possible, the change-over of the SS7
The blocking of circuits.
Telecom Link or Trunk The TSC supervises its trunks between the Transcoder, BTS, and MSC.
Failure 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 Transcoder and the MSC. However
they are also monitored by the BSC, in order to define the status of each
"end-to-end" A-trunk. The following figure 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 Carrier Units.
ACTIVE
Persistency Correlation
INACTIVE
Fault Start
RSL−2
Fault Start
RSL−N (last RSL)
The RITs are now in the SOS state. This is because the RTS belonging
to the RSL still functions, but cannot communicate with the BSC.
The RSL SBL is put into the FLT state, reflecting the loss of the RSL.
2. The persistency timer expires and the 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 sends a state-change-report
message to the OMC-R. The message contains a list of all RSL that are in
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 SBL is put in to the FLT state, it is
shown in the Alarms-In-Force List.
A Interface Fault When the BSC detects a DTC failure, the BSC puts the DTC SBL in the
Monitoring MSD-Auto state, then into the FLT state. Through the TS0 signalling, the MSC
is informed that the trunk is no longer operational and prevents all transactions
requiring the A channel (includes new mobile station-originated calls) from
using the failed link of the DTC. The failure is also 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.
Failures Detected by Software throughout the BSC detects error and alarm conditions. It reports
Software 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).
The figure below shows an example alarm report.
If one or more RSL links remain for the failed BTS, an event change is sent. The
BTS_TEL is put in a FIT state, as some channels for that cell are in operation.
The AIFL shows the new alarm. The BSC marks the cell as degraded in
service and reconfigures the BTS.
Alarm Collection 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):
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.
3. The alarm messages containing the alarm information are transmitted to the
BSC. The alarm messsages are described in the BTS Alarm Dictionary
and the BSC/TC Alarm Dictionary.
4. The message is sent to the CPR-A, where it is date and time stamped.
5. The BSC performs one of two activities:
6. The message is put in the alarm queue for BTS alarms. If the queue
overflows, the BSC performs an Alarms-in-Force audit on all the modules
in the BTS. 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. The alarm is put into
the AS component where it is logged.
The second poll occurs only if the state has changed, in order to obtain
more information about the changes.
The Transcoder supervises PCM links. The loss of a link between the BSC and
Transcoder is reported by the Transcoder to the TSC.
Collecting all fault information relating to GPUs, the active server, and
telecom and external alarms
Fault Recovery The recovery mechanism in the BSS allows a failed unit to switch to a
Mechanism replacement unit, such as:
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 Carrier
Unit/FU pair (TRE for a BTS A9100 or a BTS A910) is expendable to
replace the failed Carrier Unit).
The recovery mechanism of the BSS recognizes that the Carrier Unit can
change to its twin Carrier Unit.
Below is a step-by-step scenario of Carrier Unit recovery.
Carrier Unit Recovery 1. The Carrier Unit holding the BCCH fails.
Scenario 2. The BTS sends the BSC a recovery request, reporting that the Carrier Unit
is faulty and is out of service, and that a recovery is required. The BTS also
suggests a new Carrier Unit 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 Carrier Unit
are immediately released. The RSL is blocked. All calls on the Carrier Unit
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).
in)
H beg 4
ss of BCC
(cell, lo
Alarm BTS_CO
NF_DAT
A (2)
5
BTS_TEL=FIT BTS performs the reconfiguration
L
COMP
ONF_
BTS_C
6
SYS_INF
8 O (1..6)
nd)
CCH e
ell, lo ss of B
Alarm (c 9
begin)
of TCH
(ce ll, loss BTS_TEL=FIT
Alarm
Note: 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 Carrier Units.
Power-Down Alarm Once a power-supply failure alarm arrives, the OMU starts a timer. If, once the
Processing 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
traffic channel, 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 following:
Note: For performance reasons, each alerter type has a maximum limit of 16 alarms.
For further information concerning BSC Alerters, refer to the BSC Alerters
section of the Operations & Maintenance Principles document.
8.6.1 Traces
Trace management coordinates and triggers trace activities within the BSS.
Tracing is originated from the MSC. There are two types of tracing:
Call tracing
IMSI tracing.
Cumulative counters
RMS counters
For the MFS, the counters are all standard counters. These counters are
divided into two groups
Assess the traffic distribution in the cell from statistics on reported neighbor
cells
During the observation period, the BTS/FU keeps track of all the RMS
statistics derived from the measurements reported by the mobile stations
or measured by the BTS/FU itself on the TCH (SDCCH are not used with
RMS). At the end of the observation period when the RMS data has been
collected from the concerned BTS/FUs, the BSC builds a report (called the
RMS result file). The transfer towards the OMC-R occurs via FTAM. In
addition, it is possible during the observation period to apply MAFA (also called
Extended Measurement Reporting). This procedure consists in sending an
Extended Measurement Order (EMO) to the mobile stations. On receipt of
the command, the mobile stations take one SACCH multiframe to perform
measurements on specific frequencies. The measurements are reported via
the EXTENDED_MEASUREMENT_REPORT message. The EMO is sent only
once per call. The statistics related to MAFA are collected in the BTS and
integrated in the RMS results. The statistics are based on the measurements
performed at the BTS and the mobile station, on the TCH only.
The statistics can be classified as follows:
Radio related statistics. These can be classified as follows:
Statistics related to the whole serving cell
Statistics related to the TRXs
For more information on results analysis and the tools available to process
counter and indicators information, refer to the Results Analysis section of the
Operations & Maintenance Principles document.
8.7 Audits
Audits can be automatic or initiated by an operator. They can be performed at
several levels:
Audit Types There are several types of audits, as described in the following table.
Type Description
Logical Audit 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. No logical audit is provided for the MFS side.
Software Version The software version audit controls the versions of
Audit software that exist on the subsystem.
Hardware Audit 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.
Alarm Audit 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 differences.
State Audit 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.
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
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 Carrier
Unit and its pair FU do not match, the BSC disables the FU/Carrier Unit 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.