Académique Documents
Professionnel Documents
Culture Documents
2 / 262
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.1 EVOLIUM Radio Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.2 Extended GSM Band (E-GSM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.3 GSM 850 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.4 Frequency Band Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.1.5 GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2 BSS Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.1 Call Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.2 Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.3 Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.2.4 Operations & Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3 BSS Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.1 Base Station Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.2 Base Transceiver Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.3 Transcoder And Transmission Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.3.4 The Multi-BSS Fast Packet Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4 Extended GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1 E-GSM Mobile Station Recognition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.2 E-GSM Management After Initial Determination . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.3 E-GSM Determination at Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.4.4 TCH Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5 External Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5.1 Network Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5.2 Mobile Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.5.3 Phase 2 Mobile Support in a Phase 1 Infrastructure . . . . . . . . . . . . . . . . . . . . . . . 1.5.4 Operations and Maintenance Center-Radio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6 Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6.1 Telecommunications Management Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.6.2 Q3 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7 BSS Telecommunications Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.1 Call Management Sub-layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.2 Mobility Management Sub-layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.3 Radio Resource Management Sub-layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.4 The A Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.5 The Ater Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.6 The Abis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.7 Satellite Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.8 The Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.9 System Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.7.10 Dynamic SDCCH Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . GPRS in the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.1 Packet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.1.2 GPRS Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2 GPRS Channels and System Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.1 MPDCH Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.2 Master Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.3 Static Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.4 Multiple PCCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.5 Logical Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2.2.6 Virtual Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 16 16 17 17 17 17 18 18 19 19 19 20 20 21 24 25 27 27 28 28 28 29 30 31 35 35 36 36 37 37 38 38 38 39 40 40 41 42 45 48 49 50 50 51 54 54 54 54 56 57 57
3 / 262
Contents
2.3
2.2.7 System Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 GPRS Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 2.3.1 The Gb Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 2.3.2 The BSCGP Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 2.3.3 The GCH Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 2.3.4 Specific LCS Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 2.4 GPRS Network Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 2.4.1 MAC and RLC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 2.4.2 Temporary Block Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 2.4.3 Mobility Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 2.4.4 Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 2.4.5 Radio Power Control and Radio Link Measurement . . . . . . . . . . . . . . . . . . . . . . . . 67 2.5 Resource Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 2.5.1 Time Slot Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 2.5.2 Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 2.5.3 PCM Link Sharing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 2.5.4 TBF Resource Re-allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 2.6 Traffic Load Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 2.6.1 PDCH Allocation with "High Load Traffic" . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 2.6.2 Smooth PDCH Traffic Adaption to Cell Load Variation . . . . . . . . . . . . . . . . . . . . . . 72 2.6.3 Congestion Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 2.6.4 GPRS Overload Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 2.7 Data Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 2.7.1 GPRS Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 2.7.2 Packet Data Protocol Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 2.7.3 Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 2.7.4 Packet Data Protocol Context De-activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 2.7.5 GPRS Suspend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 2.7.6 GPRS Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 2.7.7 GPRS Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 2.8 Location Services (LCS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 2.8.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 2.8.2 Logical Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 2.8.3 LCS Positioning Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 2.8.4 LCS Scenario in Circuit-Switched Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 2.8.5 Physical Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 2.8.6 SMLC Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 2.8.7 BSS and Cell Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 2.8.8 LCS O&M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 2.9 High Speed Data Service (HSDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 2.9.1 HSDS Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 2.9.2 GPRS CS3/CS4 and EGPRS Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 2.9.3 Transmission Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 2.9.4 Cell/GPU Mapping Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 2.9.5 GCH Congestion Control Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 Call Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 3.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 3.1.1 Call Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 3.1.2 Call Set Up Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 3.2 Mobile-Originated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 3.2.1 Radio and Link Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 3.2.2 Authentication and Ciphering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108 3.2.3 Normal Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 3.3 Mobile-Terminated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 3.3.1 Radio and Link Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 3.3.2 Authentication and Ciphering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 3.3.3 Normal Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
4 / 262
Contents
3.3.4 Off Air Call Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3.5 IMSI Attach-Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.1 Paging Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4.2 Discontinuous Reception . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 Congestion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.1 Queueing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.2 In-queue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5.3 Pre-emption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6 Classmark Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.1 Classmark IE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.2 Classmark Updating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6.3 Location Updating with Classmark Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7 Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.1 IMSI/TMSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7.2 Authentication Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8 Ciphering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.1 Mobile Station Ciphering Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.2 BSS Ciphering Capability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.3 Ciphering Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.8.4 Ciphering Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9 Tandem Free Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9.1 TFO Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9.2 TFO Functional Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.9.3 TFO Optimization and Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Call Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2 In-Call Modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.1 In-Call Modification Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.2 Circuit-Switched Group 3 Fax Data Rate Change . . . . . . . . . . . . . . . . . . . . . . . . . 4.2.3 Error Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3 Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.1 Baseband Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.3.2 Synthesized Frequency Hopping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4 Speech Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.1 Continuous Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.2 Discontinuous Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.3 Voice Activity Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.4.4 BSS Discontinuous Transmission Towards Mobile Station . . . . . . . . . . . . . . . . . 4.4.5 Mobile Station Discontinuous Transmission Towards BSS . . . . . . . . . . . . . . . . . 4.5 Radio Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.1 BTS Radio Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.2 Mobile Station Radio Power Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.3 Radio Link Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.4 Power Control Decision and Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.5.5 Change Power Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6 Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.1 Principal Handover Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.2 Radio Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.3 Handover Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.4 Target Cell Evaluation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.5 Synchronous and Asynchronous Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.6.6 Circuit-Switched Telecom Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7 Overload Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.1 BTS Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.7.2 BSC Overload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.8 Call Re-establishment by the Mobile Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
118 118 119 121 123 124 124 125 127 128 129 131 132 133 133 134 134 135 135 136 136 138 139 140 141 143 144 144 145 146 146 147 148 149 150 150 150 151 151 152 154 154 154 155 156 157 159 160 161 162 169 171 174 176 176 177 179
5 / 262
Contents
Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 Call Release Procedures in Normal Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.1 Normal Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2.2 Calls Terminated Following a Channel Change . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 Call Release - Special Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.1 Call Release Following Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.2 BSC-Initiated Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.3 BSC-Initiated SCCP Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.4 BTS-Initiated Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.5 Mobile Station-Initiated Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.6 Remote Transcoder Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 Preserve Call Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Normal Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 Abnormal Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling User Traffic Across the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2 Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.1 Analog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.2 Interleaving and Forward Error Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.3 Speech Data Bursts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.4 Digital Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.5 Digital 64 kbit/s A-law Encoded Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.6 Enhanced Full-Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.7 Half-Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.8 Adaptive Multiple Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.2.9 Channel Mode Adaption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3 Circuit-Switched Data Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.1 Transparent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.3.2 Non-Transparent Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4 Short Message Service - Cell Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.1 SMS-CB Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.4.2 Phase 2+ Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5 Support of Localized Service Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.6 PLMN Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Cell Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.1 Rural and Coastal Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.2 Urban Coverage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 Concentric Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3 Sectored Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4 Extended Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.1 Standard Extended Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4.2 Enlarged Extended Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5 Umbrella Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.1 Mini Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.2 Microcell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5.3 Indoor Cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6 Cell Shared by Two BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Operations & Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.1 Subsystem O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.1.2 System O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2 O&M Control - Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.1 LMTs and the IMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
181 182 183 183 188 189 189 191 193 193 196 197 198 198 199 201 202 202 203 203 203 204 204 205 206 206 209 210 210 211 212 213 213 214 215 217 218 219 219 219 220 221 221 222 222 222 223 226 227 229 230 230 232 233 233
6 / 262
Contents
8.3
8.4
8.5
8.6
8.7
8.8
8.2.2 OML Auto-Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.3 Managed Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.2.4 Security Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . O&M Control - The OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.1 Multiple Human-Machine Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.2 ACO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.3 Secured X.25 Connection From BSC to OMC-R . . . . . . . . . . . . . . . . . . . . . . . . . . 8.3.4 Electronic Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configuration Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.1 Hardware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.2 Logical Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.3 Software Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.4 Auto-Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.5 OML Auto-Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.4.6 Network Element Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fault Management - Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.1 Alarm Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.2 Alarm Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.3 BSC Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.4 BTS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.5 Alarms Detected by the TSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.6 MFS Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.7 Recovery Example: Carrier Unit Failures with BCCH . . . . . . . . . . . . . . . . . . . . . . 8.5.8 Automatic Power-Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.5.9 BSC Alerter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Performance Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6.1 Traces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6.2 Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6.3 Radio Measurements Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.6.4 Results Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Audits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7.1 Audit Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8.7.2 Audit Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
233 234 234 234 235 236 236 238 238 239 240 240 240 242 243 244 245 246 247 250 252 252 253 255 255 256 256 257 257 258 259 259 260 261
7 / 262
Figures
Figures
Figure 1: BSS in the PLMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Figure 2: Antenna Diversity on G1 and G2 BTSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Figure 3: Antenna Diversity on the BTS A9100 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 Figure 4: Transmission Components in the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Figure 5: Cell Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Figure 6: Logical Position of External Components Associated with BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Figure 7: Location Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Figure 8: TMN System Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Figure 9: General Telecommunication Layers in GSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 Figure 10: BSS Application, Transmission Layers and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Figure 11: Time Slot 4 of a TDMA Frame Supporting Access Grant Channels . . . . . . . . . . . . . . . . . . . . . . . . . 43 Figure 12: Model LLC Packet Data Unit used in GPRS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Figure 13: The Alcatel GPRS Solution in the PLMN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Figure 14: GPRS Traffic Load Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 Figure 15: GPRS Attach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Figure 16: Mobile Station-Originating Packet Data Protocol Context Activation . . . . . . . . . . . . . . . . . . . . . . . . 75 Figure 17: GGSN-Originating Packet Data Protocol Context Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Figure 18: Mobile-Originated Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Figure 19: Mobile-Terminated Data Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Figure 20: Mobile-Originating Packet Data Protocol Context De-activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Figure 21: Network-Originating Packet Data Protocol Context De-activation Processes . . . . . . . . . . . . . . . . 83 Figure 22: GPRS Suspend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Figure 23: GPRS Resume . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 Figure 24: Mobile Station-Originating GPRS Detach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Figure 25: Network-Originating GPRS Detach Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Figure 26: Generic LCS Logical Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Figure 27: Radio and Link Establishment for Mobile-Originated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Figure 28: SDCCH Channel Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Figure 29: Immediate Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Figure 30: Connection for Mobile-Originated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Figure 31: Normal Assignment for Mobile-Originated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 Figure 32: Channel Activation Process for the Traffic Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112 Figure 33: Channel Assignment Process for the Traffic Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Figure 34: Call Connection for Mobile-Originated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114 Figure 35: Radio and Link Establishment for Mobile-Terminated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Figure 36: Normal Assignment for Mobile-Terminated Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Figure 37: CCCH with Three Blocks Reserved for AGCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Figure 38: Four TDMA Frame Cycles Providing 24 Paging Sub-channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Figure 39: Paging Message Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
8 / 262
Figures
Figure 40: Location Update with Classmark Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Figure 41: Location Update with Mobile Station Sending Location Area Identity of Previous VLR . . . . . . . 133 Figure 42: Ciphering Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Figure 43: Example of TFO Establishment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Figure 44: Frequency Hopping within an FHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Figure 45: Different Forms of Discontinuous Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Figure 46: Power Control Flow of Measurement and Decision Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156 Figure 47: Power Output Balancing Based on Received Quality and Signal Levels . . . . . . . . . . . . . . . . . . . . 157 Figure 48: Quality and Level Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 Figure 49: Better Zone Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Figure 50: Better Cell Handover (Power Budget) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Figure 51: Distance Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Figure 52: Umbrella Cell Load in Mobile Velocity Dependent Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168 Figure 53: Asynchronous External Handover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Figure 54: Mobile Station Disconnecting a Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Figure 55: Normal Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Figure 56: Initiation of Normal Release by MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Figure 57: BSC/BTS/Mobile Station Interactions in Normal Call Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Figure 58: Normal Release Final Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Figure 59: Call Release Following a Channel Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188 Figure 60: Call Release Following Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Figure 61: BSC-initiated Call Release toward the MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191 Figure 62: BTS-initiated Call Release following LAPD Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 Figure 63: Call Release due to Mobile Station-Initiated Radio Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 196 Figure 64: Call Release due to Communication Failure detected by Transcoder . . . . . . . . . . . . . . . . . . . . . . 197 Figure 65: Encoded Speech Transmission Across the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Figure 66: Multiplexed Ater Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Figure 67: Data Transmission Across the BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210 Figure 68: Short Message Service - Cell Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Figure 69: Example: Cell Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218 Figure 70: Sectored Site Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220 Figure 71: Example of Extended Cell Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221 Figure 72: Umbrella Cell with Mini Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223 Figure 73: Example: Handovers due to Threshold Triggering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225 Figure 74: Indoor Cell Example Network Hierarchy with Three Layers and Two Bands . . . . . . . . . . . . . . . . 226 Figure 75: Multiple HMI Access to OMC-Rs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235 Figure 76: ACO Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Figure 77: X.25 Without Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236 Figure 78: X.25 With Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Figure 79: RSL Correlation on the Abis Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
9 / 262
Figures
Figure 80: Example: Alarm Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249 Figure 81: Example: Loss of Carrier Unit Holding BCCH. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
10 / 262
Tables
Tables
Table 1: Types of Call Set Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Table 2: Network Subsystem Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Table 3: Traffic Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Table 4: Control Channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Table 5: System Information Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Table 6: GPRS System Information Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 Table 7: GPRS System Information Messages Used with MPDCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Table 8: Gb Interface Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Table 9: BSCGP Interface Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Table 10: GPRS Mobility Management States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Table 11: Cell Reselection Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Table 12: Network Operation Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Table 13: Time Slot Allocation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 Table 14: TBF Allocation Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Table 15: PDCH Traffic Load States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Table 16: HSDS Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Table 17: Types of Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Table 18: Call Set Up Phases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Table 19: Cell List Identifier and Paging Performed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Table 20: Paging Request Message and Mobile Station Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Table 21: Classmark Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Table 22: Classmark IE Field Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Table 23: Classmark Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Table 24: Mobile Station Ciphering Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Table 25: Downlink Discontinuous Transmission Status in Channel_activation . . . . . . . . . . . . . . . . . . . . . . . . 151 Table 26: Operator Discontinuous Transmission Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Table 27: Radio Link Measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155 Table 28: Mobile Station Maximum and Minimum Power Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Table 29: Target Cell Handover Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Table 30: Handovers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175 Table 31: AMR Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208 Table 32: Circuit-Switched Data Rate Conversions Across the Air Interface . . . . . . . . . . . . . . . . . . . . . . . . . . 211 Table 33: Subsystem O&M Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 Table 34: Configuration Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239 Table 35: Fault Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245 Table 36: BTS Alarm Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Table 37: BTS Alarms Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250 Table 38: Performance Management Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256 Table 39: Audit Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
11 / 262
Tables
12 / 262
Preface
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: Mobile Communications Support These areas describe how the BSS handles communications between a mobile station and the NSS. It follows a call through the Alcatel BSS, and describes how each element in the system functions individually and with other elements. This shows how the BSS and its units react as a system. Operations and Maintenance. These areas describe the O&M functions within the system. It describes both local and distributed O&M functions in a BSS.
Audience
This manual is for people requiring an in-depth understanding of the functions of the Alcatel BSS: Network decision makers who require an understanding of the underlying functions of the system, including: Network planners Technical design staff Trainers. 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.
13 / 262
Preface
Assumed Knowledge
The document assumes that the reader has an understanding of: GSM GPRS Mobile Telecommunications Network Management concepts and terminology.
14 / 262
1 Introduction
1 Introduction
This chapter gives a brief overview of the Alcatel BSS, its functions and features.
15 / 262
1 Introduction
1.1 Overview
The BSS provides radio coverage for GSM subscribers in a defined area. Its principal role is to provide and support signaling and traffic channels between 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 Mobile Stations Network Subsystem MSC TC BTS BSC MFS SGSN PSDN Fixed Network PSTN
Router
OMCR
AGPS server
NMC
: Multi-BSS Fast Packet Server : Network Management Center : Packet Switched Data Network : Public Switched Telephone Network : Serving GPRS Support Node
Note:
16 / 262
1 Introduction
1.1.5 GPRS
GPRS, the solution chosen by European Telecommunication Standards Institute to answer the demand for increased data transmission rates, is available in the Alcatel BSS. This means there are now two parallel systems in the PLMN: circuit-switched transmission for voice, and packet-switched transmission for data. For information on how GPRS functions in the BSS, see GPRS in the BSS (Section 2).
17 / 262
1 Introduction
Supplementary Supplementary service calls, such as SMS, allow the mobile Service station to send and receive messages to and from the BTS. These calls pass small amounts of information. Therefore, only a signaling channel is used. User Traffic User traffic calls, such as speech or data calls to a correspondent, can pass large amounts of information. Therefore, they require greater bandwidth than a signaling channel. These calls use traffic channels.
18 / 262
1 Introduction
19 / 262
1 Introduction
20 / 262
1 Introduction
21 / 262
1 Introduction
TX C O U P L I N G a a ab best of a&b b b a U N I T RX
B I E
FU
F H U
CU
RX (option)
: Base Station Interface Equipment : Carrier Unit : Frequency Hopping Unit : Frame Unit : Operations and Maintenance Unit : Receiver : Transmitter
22 / 262
1 Introduction
TRE 2 S U M
ab best of a&b
TRE 3
ab ab best of a&b b a
TRE 4
ab best of a&b b a
b a
b ANT b Tx / Rx
ANy
ANx
ANC
BASEBAND CONTROL BASEBAND RADIO COMBINING RADIO DUPLEXING
: Antenna : Antenna Network Type x : Antenna Network Type y : Station Unit Module : Transmitter/Receiver Equipment
Note:
The configuration shown above (1 Sector, 3X4 Transceivers) is one example only. Other combinations of Antennas and TREs are possible. There is no ANy in the BTS A9110, and ANy is not needed if the sector has two TREs.
23 / 262
1 Introduction
BTS
BIE
BIE
BSC
SM
SM
TC
MSC
BTS
BIE
BIE
BSC
TC
TSC BTS
BIE SM TSC TC
24 / 262
1 Introduction
25 / 262
1 Introduction
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 Radio link 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 Signaling management on the GSL Interface.
26 / 262
1 Introduction
GPU1
BSC
GPU2
GPU3
GPU4
GPU
27 / 262
1 Introduction
28 / 262
1 Introduction
SGSN
GGSN
PSDN
Router
OMCR HLR
AGPS server
NMC
: Gateway GPRS Support Node : Home Location Register : Multi-BSS Fast Packet Server : Network Management Center : Packet Switched Data Network : Public Switched Telephone Network : Serving GPRS Support Node
29 / 262
1 Introduction
30 / 262
1 Introduction
31 / 262
1 Introduction
32 / 262
1 Introduction
33 / 262
1 Introduction
The BSS adds the cell identity of the mobile stations 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 either in its HLR or its VLR. Following a location update procedure, the VLR can assign a new Temporary Mobile Subscriber Identity (TMSI) 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.
VLR
34 / 262
1 Introduction
35 / 262
1 Introduction
OMCR
Mediation Function
MFS
Network Element
BSC
BSS
BTS
BTS
: Operation Support System : Multi-BSS Fast Packet Server : Network Management Center
36 / 262
1 Introduction
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: Association connection and disconnection mechanisms Message format and structure Command types. For more information on Network Management and the Q3 Interface, see the Operations & Maintenance Principles.
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 RRM GSM Application Layers
TRANSMISSION
CM MM MS RRM
37 / 262
1 Introduction
LAPDm
LAPDm
LAPD
LAPD
SCCP SS7
SCCP SS7
Layer (2)
Layer (1)
Layer (1)
TC A Interface
Abis Interface
: BSS Application Part : Call Management : Link Access Protocol on the D Channel : Link Access Protocol on the Dm Channel : Physical Layer : Data Link Transfer Layer : Mobility Management : Radio Resource Management : Signal Connection Control Part : Signaling System No. 7 : Transcoder
38 / 262
1 Introduction
39 / 262
1 Introduction
40 / 262
1 Introduction
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.
41 / 262
1 Introduction
42 / 262
1 Introduction
The following figure shows time slot four of a TDMA frame supporting Access Grant Channels.
A G C H A G C H A G C H A G C H A G C H
Frame 1
Frame 2
Frame 3
Frame 4
Frame 5
AGCH
Figure 11: Time Slot 4 of a TDMA Frame Supporting Access Grant Channels
Channels can be divided into traffic channels and control channels.
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).
43 / 262
1 Introduction
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.
CCCH
The CCCH communicate with mobile stations in the cell before a dedicated signaling 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.
DCCH
The DCCH pass signaling information for a specific mobile station transaction. Two channels use the DCCH time slot: SDCCH: used for signaling and short message information CBCH: uses an SDCCH channel for Short Message Service - Cell Broadcasts.
ACCH
The ACCH pass signaling information for a specific mobile station transaction. An ACCH channel is always associated with a traffic channel. Two channels use the ACCH time slot: FACCH: associated with a traffic channel, and can steal slots out of 24 or 26 slots which are normally dedicated to the traffic channel for signaling purposes as well as the SACCH slot. SACCH: associated with a traffic channel, which uses one out of 26 slots for signaling purposes.
44 / 262
1 Introduction
45 / 262
1 Introduction
Message Sys_info 3
Channel BCCH
Information Cell Identity Location Area Identity Control channel description Cell options: Power central information Discontinuous Transmission (mechanism) information Radio link time out. Cell selection parameters: Cell reselect hysteresis for Location Area reselection Maximum transmit power allowed in cell Additional reselection parameter Allows/forbids new establishment causes (phase 2 mobile stations) Minimum receive level to access cell. RACH control information Spare bits setting flags and timers.
Sys_info 4
BCCH
Location Area Identity. Cell selection parameters: Cell reselect hysteresis for Location Area reselection Maximum transmit power allowed in cell Additional reselection parameter Allows/forbids new establishment causes (phase 2 mobile stations) Minimum receive level to access cell. RACH control information CBCH channel description CBCH Mobile Allocation Spare bits setting flags and timers.
SACCH SACCH
Neighbor cell BCCH frequency list. Extended Neighbor cell BCCH frequency list. This message is only sent if: The serving cell is a GSM 1800 cell and Sys_info 5 is not sufficient to encode all GSM 1800 neighbor frequencies The serving cell is a GSM 900 cell, and The mobile station is phase 2, and There are neighboring GSM 1800 cells, and Sys_info 5ter is not sufficient to encode all of the GSM 1800 cells.
46 / 262
1 Introduction
Message Sys_info 5ter (multiband systems and phase 2 mobile stations only) Sys_info 6
Channel SACCH
Information Extended Neighbor cell BCCH frequency list in different band as serving cell. The minimum number of cells, if available, to be reported in each supported band in measurement results.
SACCH
Cell Identity Location Area Identity Cell options: Power control information Discontinuous Transmission information Radio link time out Indication of which Network Color Code it is allowed to monitor.
Sys_info 7 and 8
BCCH
SI 7 Rest Octets SI 8 Rest Octets SI 4 Rest Octets_S LSA Parameters LSA ID information LSA identity
Sys_info 13
BCCH
SI 13 Rest Octets without PBCCH configured in the cell: SI 13 Rest Octets GPRS Mobile Allocation GPRS cell options GPRS Power Control parameters. SI 13 Rest Octets with PBCCH configured in the cell: SI 13 Rest Octets GPRS Mobile Allocation PBCCH description.
Sys_info 16 and 17
BCCH
SI 16 Rest Octets SI 17 Rest Octets LSA Parameters LSA ID information LSA identity
47 / 262
1 Introduction
48 / 262
49 / 262
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 graphic-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 the 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.
50 / 262
4. At the destination, another PAD reads the envelope information, strips it off, and reassembles the data in the proper order.
Header Address Control Field Field DATA
Information Field
Footer
FCS
ENVELOPE
Address Field Contains: Protocol discriminator Command/response SAPI (mobility management, QoS, SMS)
FCS SAPI : Frame Check Sequence
Control Field 4 possible types: Confirmed information transfer Supervisory functions Unconfirmed information transfer Control functions
MS
SGSN
GGSN
BSS
BTS GCH BTS Abis BSC GCH BSCGP Transcoder Ater MSC/ VLR Circuit Switched Traffic MFS
To PSTN
GCH
: BSC GPRS Protocol : Frame Relay Data Network : GPRS Channel : Gateway GPRS Support Node : Multi-BSS Fast Packet Server : Public Switched Telephone Network : Serving GPRS Support Node : Visitor Location Register
51 / 262
The following internal and external components are described in this chapter: GPRS mobiles The Serving GPRS Support Node The Gateway GPRS Support Node The Multi-BSS Fast packet Server.
52 / 262
53 / 262
54 / 262
55 / 262
BS_PAG_BLKS _RES
Number of blocks allocated to the PAGCH or PDTCH or PACCH per 52 multiframe. Number of static PRACH blocks. Number of dynamic PRACH blocks.
Number
None.
Number
BS_PRACH_BLKS <= BS_PRACH_BLKS_MAX BS_PRACH_BLKS_MAX >= BS_PRACH_BLKS S/(16 * BS_PRAC H_BLKS_ MAX) > round_trip_delay.
Number
56 / 262
57 / 262
58 / 262
Channel PBCCH
Information The PSI 3/3bis messages are sent on the PBCCH in several instances (up to 16) in order to give information on: BCCH allocation in the neighbor cells. The list of BCCH frequencies is then called the BA(GPRS) list. Cell selection parameters for the serving cell and the neighbor cells Localized Service Area (LSA) identification of the serving cell and of the neighbor cells for the SoLSA feature. Up to 32 neighbor cells can be defined by the PSI 3/3bis messages. In order to reduce the number of PSI 3/3bis instances, the coding of the PSI 3/3bis messages is optimized by compressing the redundant parameters. PSI 3quater is used to describe 3G cells for 2G to 3G cell reselection.
PSI 8
PBCCH
The PSI 8 message is optionally sent on the PBCCH to give information on the configuration of the cell broadcast channel (CBCH).
59 / 262
60 / 262
Note:
The common radio signaling functions of the BSCGP are handled on the GPRS Signaling Link, which is carried inside the Ater Interface.
61 / 262
62 / 262
63 / 262
GMM Ready
GMM Standby
NC1
NC2
64 / 262
65 / 262
2.4.4 Paging
Paging is the procedure by which the network contacts a mobile station. The network can co-ordinate 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 Network Operation Mode 1 Description Circuit-switched paging messages are sent via the SGSN and MFS. 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.
66 / 262
Description Circuit-switched paging messages are sent via the MSC and BSC, but not the MFS. 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. The MPDCH cannot be used.
Circuit-switched paging messages are sent via the MSC and BSC, but not the MFS. 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.
67 / 262
2.
The number of PDCHs is determined by the: Mobile station multislot class. This is not always known in the uplink case O&M parameter (MAX_PDCH_PER_TBF). This defines the maximum number of allocatable PDCHs per TBF.
3. If the requested number of PDCHs is not available, a request to establish a TBF is sent to the BSC. 4. PDCHs are allocated to the TBF.
68 / 262
69 / 262
The four types of TBF re-allocations are described in the table below: This type of re-allocation... T1 T2 Is used to...
Maintain a TBF alive despite a pre-emption. Re-allocate an on-going TBF when establishing a concurrent TBF when: A downlink TBF is established concurrent with an existing uplink TBF, which is allocated with the maximum number of time slots supported in the direction of the bias, re-allocation cannot be given to the mobile station An uplink TBF is established concurrent with a downlink TBF.
T3
Offer better throughput to on-going TBFs when: A TBF cannot be served with the maximum number of PDCHs it supports because: Of lack of resources at the time of the request The EGPRS class is used to establish a GPRS TBF, where the GPRS mobile station class allows a greater number of allocated PDCHs with better PDCH allocation available to serve the TBF. "Signaling traffic" becomes "data traffic" An EGPRS TBF is served on a TRX which offers a higher throughput (i.e., a better TRX class). In this case, "Signaling traffic" becomes "data traffic", and an EGPRS TBF is served on a TRX which offers a higher throughput (i.e., a better TRX class).
T4
Move an uplink GPRS TBF sharing one PDCH with a downlink EGPRS TBF onto PDCHs which do not support a downlink EGPRS TBF. When one PDCH is shared between an uplink GPRS TBF and a downlink EGPRS TBF, the downlink EGPRS TBF is limited to GMSK (i.e., MCS4). Consequently, after a T4 re-allocation the downlink EGPRS TBF is able to use 8-PSK (i.e., up to MCS9).
70 / 262
Busy
Full
71 / 262
This is the process that takes place during the phase marked "High BSC Load". The following figure shows a typical sequence illustrating the PDCH allocation procedure. Numbers in bold refer to the steps above.
allocated SPDCHs
(3)
Max_SPDCH_Dyn
(4) (5)
Max_SPDCH_Dyn
(2)
Max_PDCH Nb_TS_MPDCH
(1) time
PDCH
72 / 262
73 / 262
GPRS
Attach
Reque
st
Update
Locati
on
Authe
nticati
on
er scrib Sub ta Da
Loca
GPRS
Attach
Accep
: Home Location Register : Multi-BSS Fast Packet Server : Mobile Station : General Packet Radio Service : Serving GPRS Support Node
74 / 262
BSC
MFS
SGSN
GGSN
st
: Gateway GPRS Support Node : Multi-BSS Fast Packet Server : Mobile Station : Packet Data Protocol : Serving GPRS Support Node
75 / 262
Routin
g Info ACK
: Gateway GPRS Support Node : Home Location Register : Multi-BSS Fast Packet Server : Mobile Station : Packet Data Protocol : Protocol Data Unit : Serving GPRS Support Node
76 / 262
BSS
SGSN
2 3
RLC
PDU
5
PDU RLC ACK /N ACK
: Logical Link Control : Mobile Station : Protocol Data Unit : Radio Link Control : Serving GPRS Support Node : Temporary Block Flow : Uplink
77 / 262
STAND BY
Pag PCH H or PPC Pack et Ch Requ annel est F L TB et U t Pack ignmen Ass ing P S
2 3
READY
LLC PDU
DL
: Downlink : Mobile Station : Logical Link Control : Paging Channel : Protocol Data Unit : Packet Paging Channel : Packet Switched : Serving GPRS Support Node : Temporary Block Flow : Uplink
78 / 262
5. The SGSN sends the data LLC-PDUs to the BSS. 6. The BSS establishes a Downlink TBF on receipt of the first LLC-PDU, and releases after sending of the last LLC-PDU.
79 / 262
80 / 262
This PDCH cannot be pre-empted. It guarantees to the corresponding cell that a TBF may be established in any case. The location of this established PDCH can vary in time as is the case of pre-allocated MIN_PDCH PDCHs. A periodic background mechanism verifies every T_Initial_PDCH seconds that at least one Slave PDCH is established in the cell. When the T_PDCH_Inactivity(_Last) timer expires, the concerned PDCH established is re-evaluated. When a Master Channel is de-allocated or when EN_FAST_INITIAL_GPRS_ACCESS is changed from "enabled" to "disabled", no specific action is undertaken. If a PDCH establishment is not required, transmission resources are de-allocated after the T_PDCH_Inactivity(_Last) timer expires. The default value of the timer T_PDCH_Inactivity is reduced from 10s to 2s. Because of "Immediate uplink TBF Establishment", initial establishment of one PDCH is sufficient. With the exception of high congestion situations, as soon as there is GPRS traffic in the cell, there is always room for the establishment of an additional uplink TBF on already established PDCHs. Finally, the EN_FAST_INITIAL_GPRS_ACCESS parameter setting interacts with the MIN_PDCH parameter and the number of the Master Channels in the cell. It carries out the following rules:
MIN_PDCH - Nb_TS_MPDCH > 0 if EN_FAST_INITIAL_GPRS_ACCESS =
enabled If there is a Master Channel configured in the cell and EN_FAST_INITIAL_GPRS_ACCESS = enabled, then MIN_PDCH > 1 The EN_FAST_INITIAL_GPRS_ACCESS parameter is set according to overall system dimensioning. These initial resources are statically established and cannot be pre-empted. The cell/GPU mapping is modified in order to take this function into account.
81 / 262
BSC
ate PDP Context Request
MFS
SGSN
GGSN
1
DeActiv
4
Context ate PDP Accept
DeActiv
: Gateway GPRS Support Node : Multi-BSS Fast Packet Server : Mobile Station : Packet Data Protocol : Serving GPRS Support Node
82 / 262
BSC
MFS
SGSN
GGSN
Delete PDP Context Request
e PDP Delet ponse Res text Con
SGSNOriginating
3
Context ate PDP Request
DeActiv
4
DeActiv ate PDP Context Accept
GGSNOriginating
2
Context ate PDP Request
DeActiv
3
DeActiv ate PDP Context Accept
: Gateway GPRS Support Node : Multi-BSS Fast Packet Server : Mobile Station : Packet Data Protocol : Serving GPRS Support Node
83 / 262
MS
BTS
BSC
MFS
SGSN
1
RR Susp end
Suspen
3
T3
Suspen
Suspend
Ack
Suspend
Ack
MFS SGSN
84 / 262
MFS
SGSN
2
Resu me
T_GPRS_Resume
T4 3 4k c me A Resu
ck me A Resu
5
RR el Re Chann lease
6
Routing Area Up date Request
MFS MS RR SGSN
: Multi-BSS Fast Packet Server : Mobile Station : Radio Resource : Serving GPRS Support Node
85 / 262
6. The mobile station resumes GPRS services by sending a Routing Area Update Request message in the following cases: Reception of a Channel Release with GPRS Resumption = NOK Reception of a Channel Release without GPRS Resumption IE T3240 expiry.
BSC
MFS
SGSN
GGSN
1
Detach Request
4
tach GPRS De Accept
: Gateway GPRS Support Node : Multi-BSS Fast Packet Server : Mobile Station : Packet Data Protocol : Serving GPRS Support Node
86 / 262
BSC
MFS
SGSN
GGSN
HLR
1
ation l Loc Cance
1
quest tach Re GPRS De
2 3
Conte
4
Detach Accept
2
Cancel Location ACK
: Gateway GPRS Support Node : Home Location Register : Multi-BSS Fast Packet Server : Mobile Station : Packet Data Protocol : Serving GPRS Support Node
87 / 262
88 / 262
As depicted in the above figure: The GMLC is the first network element for external Location Application (LA) access in a GSM PLMN. The GMLC requests routing information from the HLR via the Lh Interface. After performing registration authorization, it sends positioning requests to the MSC or to the SGSN and receives final location estimates from the MSC or the SGSN via the Lg Interface The SMLC is the network element serving the mobile station. The SMLC manages the overall co-ordination and scheduling of resources required to perform positioning of a mobile station. It also calculates the final location estimate and accuracy. The SMLC controls to obtain radio Interface measurements enabling mobile station location in the service area. The SMLC is connected to the BSS (via the Lb Interface). It dialogs with other SMLCs (via the Lp Interface) to obtain measurements managed by another SMLC when the mobile station is at the border of the SMLC-covered area.
2.8.3.1 TA Positioning
TA Positioning delivers Cell ID, Timing Advance, and, optionally, Measurement Report information to the SMLC. TA Positioning regroups several distinct methods, depending on the availability and the relevance of the elementary information: The Time Advance (TA) Cell Id (CI), only in omnidirectional cells, the geographic co-ordinates of the BTS is returned instead of the real mobile station position. The TA value is used to determine the region as a circle or a ring Cell Id + Timing Advance (CI+TA). With the TA positioning method, no signaling exchange is required between the SMLC and the mobile station . The TA positioning applies to all mobile stations whether they support LCS or not.
89 / 262
4. When the mobile station is in dedicated mode (after a specific SDCCH establishment for location, or during an on-going call), the MSC sends the location request to the BSC in the existing SCCP connection for the current call, which forwards it to the SMLC. 5. The SMLC chooses a positioning method and triggers the appropriate procedure to locate the mobile station. Some message exchanges take place between the SMLC and the BSC.
6. The MSC then sends a response to the GMLC. The LCS-related messages exchanged between the BSC and the MFS are conveyed through current GSLs (same SAPI as for GPRS-related messages).
90 / 262
91 / 262
92 / 262
8-PSK-capable TRX
TRX type n
TRX class n
93 / 262
Explanation In the BSC, pool of 16k extra Abis nibbles allocated to a TRX HSDS where a pool type n contains (n-1) x 8 extra Abis nibbles. Possibility for the TRX to support EGPRS or not and if it is able to support EGPRS, its maximum MCS. The corresponding radio and transmission resources are allocated and the corresponding EGCH is activated. The corresponding radio resource has been allocated by the BSC, but no associated Ater resources are allocated.
Allocated PDCH
94 / 262
When a block is retransmitted with a given MCS, it can be retransmitted (if needed) via ARQ with a more robust MCS of the same family. Two selective ARQ mechanisms are used for the transfer of EGPRS RLC data blocks in the acknowledged RLC/MAC mode: Type I ARQ mechanism: with this mechanism, when a RLC data block is retransmitted, the same or another MCS from the same family is selected Type II ARQ mechanism (also called Incremental Redundancy (IR): in this case a second "puncturing scheme" is applied to the same MCS, if an error is detected. Four Coding Schemes are used for GPRS (CS1 to CS4). GPRS and EGPRS signaling always uses CS1. MCS1 to MCS4 are based on GMSK modulation, while MCS5 to MCS9 are based on 8-PSK modulation. The Alcatel BSS does not support MCS5-MCS9 in the uplink direction. Coding Scheme Modulation Maximum rate [kbps] per radio TS basis 59.2 54.4 44.8 29.6 22.4 17.6 14.8 11.2 8.8 21.4 15.6 13.4 9.05
MCS9 MCS8 MCS7 MCS6 MCS5 MCS4 MCS3 MCS2 MCS1 CS4 CS3 CS2 CS1
8-PSK 8-PSK 8-PSK 8-PSK 8-PSK GMSK GMSK GMSK GMSK GMSK GMSK GMSK GMSK
95 / 262
96 / 262
97 / 262
98 / 262
3 Call Set Up
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.
99 / 262
3 Call Set Up
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.
Service Calls
100 / 262
3 Call Set Up
101 / 262
3 Call Set Up
102 / 262
3 Call Set Up
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.
MS
Channel Request (RACH)
Channel Required REF+RFN+ TA
BTS
BSC
MSC
REF
SDCCH Allocation
: Description of the allocated SDCCH (Standalone Dedicated Control Channel) : Initial Layer 3 message : Timing advance : Unnumbered acknowledgment
103 / 262
3 Call Set Up
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.
Note:
Contention resolution prevents two mobile stations connecting to the same SDCCH. The following figure shows the Channel Activation procedure.
MS BTS BSC SDCCH Allocation
wer H+po DCC TA+S
Chann el Activ
MSC
Chann
el Acti
vation
ation A
ck
power SDCCH TA
: Mobile Station power or BTS power : Description of the allocated SDCCH (Standalone Dedicated Control Channel) : Timing advance
104 / 262
3 Call Set Up
dia Imme
Switch to SDCCH
te ass
ignme
nt (AG
CH)
and comm ssign diate a RFN Imme REF+ wer+ H+po DCC TA+S
: Random access information value : Reduced frame number : Description of the allocated SDCCH (Standalone Dedicated Control Channel) : Timing advance
105 / 262
3 Call Set Up
Therefore, the system implements a special immediate_assignment_reject message when the following conditions are met: 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 All SDCCHs in the cell are busy. 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. The immediate_assignment_reject message is contained in the information element of the immediate_assign_command message. This message starts a timer in the mobile station which causes it to wait in idle mode until the timer expires, before sending new channel_request messages. The length of the timer is dependent upon the establishment cause, and can be set by the user. If an immediate_assign_command message is received before expiration of the timer, it has priority and the mobile station will respond to it, thus connecting the call.
Note:
This message cannot be used when the mobile station is responding to paging, i.e., in the case of a mobile-terminated call.
106 / 262
3 Call Set Up
BTS
BSC
MSC
nnecti SCCP Co
irm on Conf
cm Service Request UA
: Classmark : Initial Layer 3 message including the mobile station identity and classmark : Unnumbered acknowledgment
107 / 262
3 Call Set Up
108 / 262
3 Call Set Up
109 / 262
3 Call Set Up
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.
MS
set up
BTS
(SDCCH) layer 3 CC
BSC
layer 3 CC
layer 3 CC
MSC
call proceeding
TCH allocation
request context physical
(SACCH
on activati channel pher i TA + c r TCH + + powe + DTX channel activati on acknow ledge d comman ment assign
assign
mman ment co
CH d (SDC
release SDCCH
Set transcoder
assignme
nt comp lete
layer 3 CC
layer 3 CC
layer 3 CC
layer 3 CC
connect acknowledgement
layer 3 CC
cipher cm DTX TA
: Encryption algorithm + ciphering key : Classmark : Discontinuous transmission flags : Timing advance
110 / 262
3 Call Set Up
111 / 262
3 Call Set Up
MS
BTS
BSC
TCH allocation
request context physical
MSC
channel
) (SACCH
activati
on
channel
activati
on acknow le
dge
assignme
: Encryption algorithm + ciphering key : Discontinuous transmission flags : Mobile Station : Timing advance : Traffic Channel
112 / 262
3 Call Set Up
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 with 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.
release SDCCH
SABM (F ACCH)
establis h indica ti
CCH) UA (FA
assignme nt comp lete (F ACCH)
Set transcoder
on
assignme
nt comp lete
FACCH MS SABM UA
: Fast Associated Control Channel : Mobile Station : Set Asynchronous Balanced Mode : Unnumbered Acknowledgment
113 / 262
3 Call Set Up
layer 3 CC
layer 3 CC
alerting
layer 3 CC
layer 3 CC
connect
connect acknowledgement
layer 3 CC
MS SDCCH
114 / 262
3 Call Set Up
BSC
paging
TMSI/IMS list I + cell
MSC
(PCH)
comman paging
channel request
(RACH)
channel
required
: International Mobile Subscriber Identity : Mobile Station : Paging Channel : Random Access Channel : Temporary Mobile Subscriber Identity
115 / 262
3 Call Set Up
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).
116 / 262
3 Call Set Up
MS SDCCH
117 / 262
3 Call Set Up
118 / 262
3 Call Set Up
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 assignment 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 for the PCH. The parameter to reserve these blocks is set to BS_AG_BLKS_RES = 3.
TDMA Frame Cycle
CCCH0
CCCH1
CCCH2
CCCH3
CCCH4
CCCH5
CCCH6
CCCH7
CCCH8
: Access Grant Channel : Common Control Channel : Paging Channel : Time Division Multiple Access
119 / 262
3 Call Set Up
In the example shown in the figure above, BS_AG_BLKS_RES is set to three. Every occurrence of the TDMA frame cycle carrying the CCCH has three AGCHs and six PCHs. However, more than six paging groups can be defined by assigning a different group of six PCHs to a number of TDMA multiframe cycles. This is specified using the parameter BS_PA_MFRMS, as shown in the following figure.
First TDMA Frame cycle
AGCH
AGCH
AGCH
PGR0
PGR1
PGR2
PGR3
PGR4
PGR5
AGCH
AGCH
AGCH
PGR6
PGR7
PGR8
PGR9
PGR10
PGR11
AGCH
AGCH
AGCH
PGR12
PGR13
PGR14
PGR15
PGR16
PGR17
AGCH
AGCH
AGCH
PGR18
PGR19
PGR20
PGR21
PGR22
PGR23
These four TDMA frames represent 24 PCHs. The parameter to reserve these is BS_PA_MFRMS =4
: Access Grant Channel : Paging Group : Paging Channel : Time Division Multiple Access
120 / 262
3 Call Set Up
Error in IE
Mobile Station Identification IMSI or TMSI (for one mobile station) IMSI, IMSI or TMSI, TMSI or IMSI, TMSI (for two mobile stations)
121 / 262
3 Call Set Up
Paging Request Message Type_2, identifying three mobile stations. Type_3, identifying four mobile stations.
Mobile Station Identification TMSI, TMSI, TMSI or TMSI, TMSI, IMSI TMSI, TMSI, TMSI, TMSI
paging
comm
and
st
chan
REF
SABM + serv ice req ue (pagin g resp st onse)
nel re
+ RF
quire
A
N+T
establi
sh indic
ation
: Common Control Channel : Information Element : International Mobile Subscriber Identity : Mobile Station : Random access information value : Reduced frame number : Set Asynchronous Balanced Mode : Timing advance : Temporary Mobile Subscriber Identity
122 / 262
3 Call Set Up
123 / 262
3 Call Set Up
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_Queue_Length parameter to 0 disables 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.
124 / 262
3 Call Set Up
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_Queue_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 or Forced Directed Retry.
125 / 262
3 Call Set Up
126 / 262
3 Call Set Up
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 signaling 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 and Phase 2 GSM, the signaling 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 pvi: The pre-emption vulnerability indication indicates if the transaction can be pre-empted prec: The pre-emption recommendation. This is needed in order to defer pre-emption until a suitable non-congested cell is found in the preferred cell list. The pre-emption recommendation is used when the old BSS recommends that another connection be pre-empted. Pre-emption is applied to the TCH only. The pre-emption feature is optional and controlled by the O&M parameter (EN_TCH_PREEMPT) on a per-BSC basis. The BSC provides pre-emption of TCH radio resources. This takes into account the priority of the call. The lowest lower priority call with the pvi bit set is pre-empted and thus released. Directed retry and/or forced handover in order to avoid pre-emption is not supported.
3.5.3.1 eMLPP
Enhanced Multi Level Priority and Pre-emption (eMLPP) is a supplementary service that allows a subscriber in the fixed or mobile network to initiate calls that have a priority and pre-emption attribute known to all the network elements. The eMLPP standardization provides the transportation of the subscription information for priority and pre-emption on MAP. This subscription information is stored in the HLR and the GCR and is transported to the VLR. This information is used for the following procedures: Paging TCH Assignment TCH Handover. Only TCH pre-emption is supported (i.e., only for circuit-switched services).
127 / 262
3 Call Set Up
MSC
Mobile station
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.
128 / 262
3 Call Set Up
3.6.1 Classmark IE
The Alcatel 900/1800 BSS supports classmark 1, classmark 2 and classmark 3 IEs. Classmark 1 IE is always sent to the BSS when the mobile station tries to establish communication. Classmark 1 The Classmark 1 IE contains: The revision Level The RF Power Level Support of A5/1 Encryption. Classmark 2 The Classmark 2 IE is defined in GSM to allow the coding of phase 2 capabilities such as the A5/2 ciphering algorithm. The classmark contains the same elements as Classmark 1 IE, plus support of A5/2 encryption. Classmark 3 The Classmark 3 IE is defined in GSM to allow multiband mobile stations to indicate their capabilities. The classmark specifies the supported bands and the respective power classes.
129 / 262
3 Call Set Up
Indicates... the mobile station power capability. For Alcatel 900: Class 1 = 20 W Class 2 = 8 W Class 3 = 5 W Class 4 = 2 W Class 5 = 0.8 W For Alcatel 1800: Class 1 = 1 W Class 2 = 0.25 W 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.
whether the mobile station supports the A5/1 encryption algorithm. If the A5/1 encryption algorithm is not supported, there is no indication of other algorithms being supported. whether the mobile station supports the A5/2 encryption algorithm. If the A5/2 encryption algorithm is not supported, there is no indication of other algorithms being supported.
130 / 262
3 Call Set Up
Action The classmark_enquiry message is never initiated by the BSC. The BSC always initiates a classmark update when it receives a location update request. The BSC only initiates a classmark update on reception of a location update request if A5/1 is not available. This is worked out from the classmark 1 IE.
131 / 262
3 Call Set Up
BTS
BSC
MSC
switch to SDCCH
SABM + rn + fn + cm
(FACCH/S
ACCH)
y k enquir classmar
nnecti SCCP co
on
confirm
classmark change
classmark 2IE
classmark update
classmark 2IE
location update
(SDCCH)
: Classmark : Fast Associated Control Channel : Information Element : Mobile Station : Random Access Channel : Set Asynchronous Balanced Mode : Slow Associated Control Channel : Signal Connection Control Part : Standalone Dedicated Control Channel : Timing advance
132 / 262
3 Call Set Up
6. The mobile station responds with a classmark_change message containing the classmark 2 IE. This information is passed to the MSC in a classmark_updating message. If the mobile station is a phase 1 mobile station, it responds with an RR_status message which is ignored by the BSS. In this case, the BSS sets ciphering with the information available from the classmark 1 IE. 7. The MSC initiates the authentication procedure and on receipt of the authentication response message, initiates the ciphering procedure. Refer to Ciphering (Section 3.8) for more information about ciphering. 8. When ciphering is set, the MSC can accept the location 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.
3.7.1 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.
BSC
MSC
VLR
info request
IMSI + Ki
service request + TMSI + old LAI new TMSI BTS Mobile Station BSC
MSC
VLR
: International Mobile Subscriber Identity : Individual Subscriber Authentication Key : Location Area Identity : Temporary Mobile Subscriber Identity : Visitor Location Register
Figure 41: Location Update with Mobile Station Sending Location Area Identity of Previous VLR
133 / 262
3 Call Set Up
3.8 Ciphering
Ciphering is supported in the Alcatel 900/1800 BSS to protect information transmitted on the Air Interface. This includes: Subscriber information such as the IMSI User data SMS and SS data Information such as called and calling party numbers.
134 / 262
3 Call Set Up
Ciphering protects the information by using encryption. There are three different ciphering modes, the use of which depends on the mobile station classmark and the capability of the BTS. These modes are: Encryption using algorithm A5/1 Encryption using algorithm A5/2 No encryption. The two encryption algorithms are defined in GSM. If either is to be used, both the mobile station and BTS must have the same encryption capability.
135 / 262
3 Call Set Up
136 / 262
3 Call Set Up
4. 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. 5. The mobile station either: Starts the encryption and sends an encrypted Layer 2 acknowledgment message to the BTS. This prompts the BTS to start encryption mode for frames sent to the mobile station Sends an unencrypted level 2 acknowledgment to the BTS. 6. The mobile station sends a ciphering_mode_complete message to the BTS which is passed transparently to the BSC. The BSC sends a cipher_mode_complete message to the MSC. This process is shown in the following figure.
MS BTS BSC
e com man d
MSC
ciphe
od ing m
ciphe
od ing m
e com
man
mand
perm
lgorit itted a
hms +
Kc
(SDCC
H)
algorithm or no encryption
cipher
mode
comple
te
MS SDCCH
137 / 262
3 Call Set Up
138 / 262
3 Call Set Up
BSC A
TC A PCM samples
TC B
BSC B
Channel activation TFO enabled TRAU frames CON_REQ DL_ACK
BTS B
1 2 3 4
TFO_ACK
TFO_ACK
Codecs match
TFO_ON
TFO frames
TFO_ON
5
TFO REPORT (TFO STATUS= ON) TFO REPORT (TFO STATUS= ON)
: Pulse Code Modulation : Transcoder : Tandem Free Operation : Transcoder Rate Adaptation Unit
139 / 262
3 Call Set Up
6. The BTS are made aware of the exchange of TFO frames by tfo_on. The BSC is informed via a tfo_report message on the Abis Interface. The Alcatel TFO implementation is fully compliant with the GSM standard and additionally provides: As an operator 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.
140 / 262
3 Call Set Up
141 / 262
3 Call Set Up
142 / 262
4 Call Handling
4 Call Handling
This chapter provides an overview of Call Handling and describes the supervision of a call in progress.
143 / 262
4 Call Handling
4.1 Overview
An obvious requirement for the effective management of calls in the BSS is to provide the following: Maximum perceived signal quality with minimum perceived interference Call continuity regardless of changes in propagation conditions or change of location of the mobile station. Given that spectrum is limited, this must be accomplished with maximum resource reuse. Another important factor for the customer (and the operator as well) is power efficiency to reduce overall power consumption and prolong the autonomy of the mobile station under battery operation. The supervision of calls in progress is provided by the Call Handling function. Call Handling, with associated features, implements needed changes in the required teleservice to maintain call quality and continuity. Call Handling functions and features include: In-Call Modification Frequency Hopping Discontinuous Transmission Radio Power Control Handover Overload Control Call re-establishment by the mobile station.
144 / 262
4 Call Handling
Calls requiring a change of service have to negotiate a dual-service before the normal assignment procedure. This is indicated in the set_up message, which is described in Call Set Up (Section 3).
Note:
Changing the data rate of a fax call is not a true in-call modification procedure, as the teleservice is not changed (no dual-service negotiation). The main difference between the in-call modification procedure and a change of data rate for fax are as follows: The in-call modification procedure is triggered by a message from the mobile station The data rate change for fax is triggered by in-band signaling from the fax machine to the MSC. Both procedures use existing resources, therefore no new resources need to be allocated. All full-rate traffic channels can be used for speech or data at any of the defined data rates. Both procedures use the mode modify procedure to change the transmission mode. This is basically a normal assignment procedure but instead of a new channel being assigned, a new mode is assigned.
145 / 262
4 Call Handling
4. 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.
146 / 262
4 Call Handling
147 / 262
4 Call Handling
f1
f2
f3
f1
f2
f3
f1
f2
f3
f1
f2
f3
: Frequency : Frequency Hopping System : Traffic Channel : Mobile Allocation Index Offset : Hopping Sequence Number : Time slot
148 / 262
4 Call Handling
Note:
Normally, in both Frequency Hopping schemes (Baseband and Synthesized), time slot 0 (TS0) is not available for Frequency Hopping. This is because it carries the BCCH, which must always be at maximum power and on a frequency known to mobile stations in Idle mode in the cell.
149 / 262
4 Call Handling
150 / 262
4 Call Handling
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: 0. This is the default value, and allows Discontinuous Transmission on the downlink for all calls that are established on the BCCH TRX 1. This bans Discontinuous Transmission on the downlink for all calls that are established on the BCCH TRX.
OMC-R Discontinuous Transmission_ DOWNLINK_ ENABLE (per BSC basis) True True
False False
OFF OFF
151 / 262
4 Call Handling
The BTS tells the Transcoder to perform Discontinuous Transmission by setting the Discontinuous Transmission bit in the speech frame. In the BSS, the Transcoder is responsible for Discontinuous Transmission operation. In the BTS, the information is processed in the FU in the following way: 1. When the Transcoder detects voice activity it informs the FU, using in-band signaling. The speech signaling flag is set in the speech frame. 2. Every 20 ms the FU receives either speech frames or SID frames containing background noise characteristics. 3. At the end of the speech period (four bursts of detected silence) the FU sends a SID frame over the Air Interface. 4. During speech inactivity, the last received SID frame is sent at regular 480 ms intervals rather than at 20 ms. Otherwise dummy bursts are sent. These dummy bursts are: Transmitted for traffic channels on the BCCH frequency, due to the need for constant transmission on the BCCH frequency Not transmitted for traffic channels on other frequencies.
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.
152 / 262
4 Call Handling
Description This allows the mobile station to choose either quality by not using uplink Discontinuous Transmission, or power-saving by using uplink Discontinuous Transmission. The OMC-R operator has decided, due to low interference, to have improved speech and 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. The following figure shows the different forms of transmission.
DTX
: Discontinuous Transmission
153 / 262
4 Call Handling
154 / 262
4 Call Handling
155 / 262
4 Call Handling
clear
a F ch
requ
est
clear
MIE in
MS TX
156 / 262
4 Call Handling
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
R X Q U A L
Signal level too high Quality bad Handover desired High Signal Level
RXLEV
RXQUAL RXLEV
Figure 47: Power Output Balancing Based on Received Quality and Signal Levels
30 dBm (1 W)
10 dBm
39 dBm (8 W) 39 dBm (8 W)
13 dBm 13 dBm
157 / 262
4 Call Handling
Mobile Station Phase GSM 850/900/1800/1900 Mobile station phase 2, GSM 1800 Mobile station GSM 1900
33 dBm (2 W)
0 dBm
158 / 262
4 Call Handling
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 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: A new channel is assigned, ready to support the call The mobile station moves over to the new channel On successful completion of the handover, the system clears the resources for the old channel.
159 / 262
4 Call Handling
160 / 262
4 Call Handling
161 / 262
4 Call Handling
162 / 262
4 Call Handling
123456 123456789 123456 123456789 123456 123456789 123456789 Level 123456Desired Power Power 123456789 Intercell 123456 Quality Increase Decrease to Handover to Conserve 123456and Level 123456789 Improve Balance Resources 123456(no action 123456789 Level and Minimize 123456needed) 123456789 Interference 123456 123456789 123456 123456789 123456 123456789 123456 12345678901234 123456789 123456 Power Increase to 12345678901234 123456 12345678901234 improve quality 123456 12345678901234 123456 12345678901234
Quality Intercell Handover Quality Intracell Handover High Level Low Level
Low Quality
163 / 262
4 Call Handling
164 / 262
4 Call Handling
165 / 262
4 Call Handling
This type of handover can be caused by the following events: Power budget is greater than handover margin threshold High signal level in neighbor microcell (macrocell to microcell handover).
BSS 1 = Best Cell BSS 2 = Best Cell
166 / 262
4 Call Handling
BSS 1
123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789 123456789
BSS 2
167 / 262
4 Call Handling
This is to avoid sending a call to the umbrella cell in the following cases: A call initiated at the limit of the lower layer cell A call transferred from the umbrella cell to the lower layer cell, just before reaching the limit of that cell After an external handover, when there is no information on the preceding cell and handover cause. Whatever the dwell time, any emergency handover sends the call to the umbrella cell, which acts as the rescue cell. The load on the umbrella cell is taken into consideration when determining the threshold at which handovers are performed. Saturation of the umbrella cell can cause the loss of calls, when a handover is required from another umbrella cell or a lower layer cell. As the load on the umbrella cell increases, the dwell time threshold is increased, keeping some 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 Macrocell saturated High load Traffic regulation Low load Max speed discrimination in force Low minimum dwell time Speed discrimination disabled
Macrocell with little traffic Minimum Dwell Time High minimum dwell time
168 / 262
4 Call Handling
169 / 262
4 Call Handling
Mobile station distance from target BTS Handover cause. The HO_MARGIN parameter is an O&M parameter set by the Network Operator. It is used to prevent a call being continually handed over between two cells. For example, following a power budget handover, the new cell immediately starts power budget calculations for its neighbor cells. It may find that the original cell is giving a better power budget reading and try to hand back immediately. This effect can be caused by slight climactic changes which affect the propagation of signals. It is known as the ping-pong effect. The HO_MARGIN parameter stops a call being handed back to a cell from which it has just been handed over. There is also an O&M parameter, W_PBGT_HO which can be set by the OMC-R operator, to add a weighting for the power budget parameters of cells controlled by another BSC. Refer to the A1353-RA Configuration Handbook for more information. The target cell chosen also depends on the mobile station classmark (see Classmark Handling (Section 3.6)) and its compatibility with the BTSs ciphering capabilities (see Ciphering (Section 3.8)). The procedures initiated to hand over a call depend on which cell has been chosen as the target cell.
170 / 262
4 Call Handling
If the target and serving cell are... not controlled by the same BSC, but the two BSC are controlled by the same MSC, this is called an interBSS intraMSC handover. This handover is controlled by the MSC. controlled by different BSCs and the two BSCs are controlled by different MSCs, this is called an interBSS interMSC handover. The control of this handover is shared between the MSCs. Handovers controlled by the BSC are called internal handovers. Handovers controlled by the MSC are called external handovers.
171 / 262
4 Call Handling
Target BTS
(SACCH)
Serving BTS
Target BSC
Serving BSC
MSC
1
measurement results
2 3
channel activation
SACCH/FACCH
required
l IDs+DTX+cause+c
+ handover command
d handover comman
handover command
handover command
ch+cell+HOref+cipher
handover detect
5
handover detect
HO ref + TA
handover detect
6
ack
establish indication
(FACCH)
handover complete
handover performed
clear command
: Discontinuous Transmission : Fast Associated Control Channel : Handover : Mobile Station : Set Asynchronous Balanced Mode : Slow Associated Control Channel : Timing advance
172 / 262
4 Call Handling
173 / 262
4 Call Handling
5. 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. 6. 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 stations 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.
A capture handover refers to a handover triggered only on the signal level received from the neighbor cell, independently of the signal received from the serving cell. A power budget handover refers to a handover triggered on a power budget criterion. The power budget is a measure of the difference between the signal level received from a neighbor cell and the signal level received from the serving cell. The higher is the power budget, the more likely a power budget handover is triggered.
Power Budget
Cause 14
Handover Cause 14 is used in hierarchical networks to unload the umbrella cells by directing slow mobile station towards a lower or indoor layer cell. Mobile station speed is estimated by measuring the residence time of the mobile station in the indoor and lower layer cells. If this residence time is below a certain threshold, the mobile station is deemed to move rapidly. If the residence time is above another threshold, the mobile station is deemed to move slowly.
174 / 262
4 Call Handling
Description
In multiband networks, the operator defines a preferred band where multiband mobile station are directed. Handover Cause 21 is triggered when a mobile station in the non-preferred band receives a good signal level from a neighbor cell where the traffic load is not high and which belongs to the preferred band. Handover Cause 23 reduces the serving cell size when it is high loaded relative to a low loaded neighbor cell. The traffic handover enables better distribution of traffic in the serving cell neighborhood. When the mobile station moves away from the BTS, as the path loss increases, the power budget increases and a traffic handover is triggered sooner. The power budget is used to evaluate the difference between the signal levels received from the neighbor cell and from the serving cell. In hierarchical networks where cells use different frequency bands, a general capture handover Cause 24 is required to manage, on a per cell adjacency basis, the ability of the mobile station to be captured by a neighbor cell. This allows capture from a macrocell to a microcell or from the same macrocell to another cell in the preferred band. This general capture handover takes into account the load in the serving cell and in the target cell.
Cause 23
Cause 24
175 / 262
4 Call Handling
Note:
The telecommunications processors of the MSC can also become overloaded. However, MSC overload control is not the domain of the BSS.
176 / 262
4 Call Handling
177 / 262
4 Call Handling
perform global action for BTS-to-BSC overload conditions. The number of access classes that can be barred and unbarred in one step can also be configured from the OMC-R.
178 / 262
4 Call Handling
179 / 262
4 Call Handling
180 / 262
5 Call Release
5 Call Release
This chapter provides an overview of Call Release and describes the procedures which ensure resource allocation to a call. 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.
181 / 262
5 Call Release
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 finished and either the called or calling party hang up A mobile station is turned off A call is handed over and the resources for the original call are released A call is modified and the resources for the original channel are released There is operator intervention, such as a channel being blocked There is a failure There is a radio link failure The system detects an LAPDm failure. If a call is terminated normally, the Call Release procedures are triggered automatically. If the call is terminated abnormally, the system has to detect that the resources are no longer required and release them. For a complete Call Release, the following resources must be released: A Interface resources Abis Interface resources Air Interface resources MSC resources: Layer 3 for the A Interface SS7 signaling 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.
182 / 262
5 Call Release
MS
disconne ct
BSS
(layer 3 CC)
MSC
request release
CC) (layer 3
release
complete
(layer 3 CC)
MS
: Mobile Station
183 / 262
5 Call Release
2. 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. 3. 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
clear c
MIE in
MSC
omma nd
lue use va
g ca cludin
chann
el rele
ase
tiva te S AC
CH
c dea
(to re
UA
relea
dicati
on
physic
al c
reque ontext
st
RF ch
annel
RF ch
annel
Timer
releas e ack
: Link Access Protocol on the Dm Channel : Mandatory Information Element : Mobile Station : Slow Associated Control Channel : Signal Connection Control Part : Transcoder : Unnumbered Acknowledgment
184 / 262
5 Call Release
BSC
MSC
1
clear
udin MIE incl
command
value g cause
release channel
clear co mplete
2 3
complete
: Mandatory Information Element : Mobile Station : Slow Associated Control Channel : Signal Connection Control Part
185 / 262
5 Call Release
BSC
clea and r comm
ding c ause v alue
MSC
clu MIE in
chann
el rele
ase
d tiv eac ate SAC
CH
2
(to re lease LAP Dm) UA
disc
plete
ed
releas
relea
se in
dicati
on
SCCP
release
comple
te
: Link Access Protocol on the Dm Channel : Mandatory Information Element : Mobile Station : Slow Associated Control Channel : Signal Connection Control Part : Transcoder : Unnumbered Acknowledgment
186 / 262
5 Call Release
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). 4. 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. 5. 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
3
UA
releas e indi cation
context
Timer
confirm
5
nel RF chan release
RF chan nel rele ase ack
Timer
MS UA
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 Call Set Up (Section 3) for more information).
187 / 262
5 Call Release
Target BTS
Serving BTS
e
Target BSC
Serving BSC
MSC
handover complet
handover perform
ed
chan
nel re
leas
deac
tivate
SAC
CH
: Fast Associated Control Channel : Mandatory Information Element : Mobile Station : Slow Associated Control Channel
188 / 262
5 Call Release
5.3.1.1 Reset
The MSC initiates Call Release when it has to release all calls associated with the BSS (Reset). The MSC sends a reset message containing a cause value to the BSC. The BSC then: Sends an alarm to the OMC-R Sends a block message to the MSC to block circuits Starts to clear all calls in the BSS. For each call, the procedure in Normal Release (Section 5.2.1) is repeated. For each SCCP connection on the A Interface, the BSC can send an SCCP_release message and release any A Interface resources associated with the SCCP. A timer allocates a certain amount of time for the calls to clear. When the timer expires, the BSC sends a reset_ack message to the MSC. Figure 60 shows the Call Release process after a reset is initiated.
189 / 262
5 Call Release
MSC
block
SCCP releas e
circuits blocked
disc
to releas e LAPD m
SCCP
releas
e com
plete
SCCP re
lease
indicatio
n
SCCP releas e com plete
disc
to rele ase L APD m
confirm
RF chan
ase
RF chan
nel releas
e ack
timer
reset a ck
LAPDm MS SCCP
: Link Access Protocol on the Dm Channel : Mobile Station : Signal Connection Control Part
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.
190 / 262
5 Call Release
MSC
MIE MS
191 / 262
5 Call Release
Note:
In this process, once the BSC considers the mobile station disconnected, it initiates release of the RF channel from the BTS. This can occur following: 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.
192 / 262
5 Call Release
193 / 262
5 Call Release
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.
194 / 262
5 Call Release
The BSC re-initializes 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.
MS
BTS
Detection of LAPD failure. BTS stops sending SACCH frames.
disc
BSC
MSC
timer
disc
timer
disc
timer
UA
UA
UA
mmand clear co
e use valu uding ca MIE incl clear comple te
: Frame Unit : Link Access Protocol on the D Channel : Mandatory Information Element : Mobile Station : Slow Associated Control Channel : Transmitter/Receiver Equipment : Unnumbered Acknowledgment
195 / 262
5 Call Release
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
Interruption of SACCH frames
BTS
BSC
MSC
start counter
connec tion fa ilur e indi ca tion
cause value
clear
reques
se elea el r hann RF c
clea
mm r co
and
MIE MS SACCH
Figure 63: Call Release due to Mobile Station-Initiated Radio Link Failure
196 / 262
5 Call Release
Alarm
clea
MIE inc
r co
mm
and
se v alue
g ludin
cau
MIE MS TC
197 / 262
5 Call Release
198 / 262
5 Call Release
199 / 262
5 Call Release
200 / 262
201 / 262
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. Transmission 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 A 13 kbit/s CIM 13 kbit/s 64 kbit/s A/D
BTS
BIE
BIE
BSC
SM
SM
TC
MSC
PSTN
Mobile Station A 6.5 kbit/s CIM 6.5 kbit/s 13 kbit/s 64 kbit/s A/D
: Analog : Analog/Digital : Base Station Interface Equipment : Channel Encoded, Interleaved, and Modulated : Public Switched Telephone Network : Submultiplexer : Transcoder : Traffic Channel
202 / 262
6.2.1 Analog
The microphone converts speech to an analog signal. The analog signal is encoded into a digital signal depending on the type of traffic channel used: 13 kbit/s for a full-rate traffic channel (or enhanced full-rate) 6.5 kbit/s for a half-rate traffic channel. It is then transmitted on a 16 kbit/s (8 kbit/s for half-rate) radio time slot. 3 kbit/s and 1.5 kbit/s are used for signaling on full-rate and half-rate channels respectively.
203 / 262
BSC
SM
SM
TC
MSC
SM TC
: Submultiplexer : Transcoder
204 / 262
205 / 262
6.2.7 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: BSC A9120 G2 Transcoder A9125 Transcoder One of the following BTSs: G1 BTS equipped with Dual Rate Frame Unit EVOLIUM BTS.
206 / 262
Alcatel offers two versions of AMR: 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 greatly, 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-R, 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.
207 / 262
AMR_SUBSET_HR
EN_AMR_CHANNEL_ADAPTATION
EN_AMR
OFFSET_CA_NORMAL
OFFSET_CA_HIGH
RXQUAL_CA_NORMAL
RXQUAL_CA_HIGH
208 / 262
209 / 262
BTS
BIE
BIE
BSC
SM
SM
TC
MSC
PSTN
Mobile Station V.110 data blocks A 13 kbit/s CIM 13 kbit/s 64 kbit/s ISDN /Analog A/D
: Analog : Analog/Digital : Base Station Interface Equipment : Channel Encoded, Interleaved, and Modulated : Public Switched Telephone Network : Submultiplexer : Transcoder
210 / 262
Table 32: Circuit-Switched Data Rate Conversions Across the Air Interface
211 / 262
Error handling and rate adaptation are handled as follows: Error Handling 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.
: Cell Broadcast Center : Human Machine Interface : Short Message Service - Cell Broadcast
212 / 262
213 / 262
214 / 262
215 / 262
216 / 262
7 Cell Environments
7 Cell Environments
This chapter describes the cell environments available in the Alcatel 900/1800 BSS.
217 / 262
7 Cell Environments
7.1 Overview
The Alcatel BSS provides coverage suited to the needs of urban, rural and coastal areas by offering a variety of possible cell environments. 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 GSM 1800 bands. The parameters to define cells are grouped into five types: Cell dimension. This consists of macro up to 35 Km (can be up to 70 km with extended cell), and micro up to 300 meters Cell Coverage. There are four types of coverage, single, lower, upper, and indoor Cell Partition. Two types of frequency partition exist, normal or concentric Cell Range. The cell range can be normal or extended Cell Band Type. A cell belongs to either the GSM 900 or GSM 1800 bands, or both in case of a multiband cell. The following figure 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.
Sectored Site Umbrella Cell Microcell Microcell Microcell Inner Cell Outer Limit Umbrella & Concentric Cell Microcell Microcell Microcell
Extended Cell
Overlap Zone
218 / 262
7 Cell Environments
219 / 262
7 Cell Environments
Cell 1
Cell 3
Sector 3
Antenna
220 / 262
7 Cell Environments
35 km max
221 / 262
7 Cell Environments
222 / 262
7 Cell Environments
The following figure shows the application of the two-layer hierarchical network, with macrocells for both layers, in a small town.
Umbrella Cell
Pedestrian area
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 microcells small radius is created by limiting the maximum power output strategically to cover a pre-defined microcell area. Handover occurs more frequently in a microcell environment due to the small radius sizes. Microcell handovers occur: To handle stationary mobile stations (especially mobile stations used indoors) When a mobile station moves in a street covered by microcells To avoid losing calls. Whenever there is a risk of losing a call, a handover is triggered to the umbrella cell. Fast moving mobiles are handled by the umbrella cell. A mobile handled by a microcell is sent to the umbrella cell if the delay between handovers becomes too small. Conversely a mobile is sent to a microcell if it receives a high level of signal for a sufficient time. Call quality/control is achieved by providing four thresholds for microcell handover and one handover threshold for macrocell handover.
223 / 262
7 Cell Environments
Rescue Handover
Note:
If the low threshold is not used, the M_to_m Threshold value must be above the high threshold value.
224 / 262
7 Cell Environments
d B m
A mobile station is moving along a street. As it moves along a street, the mobile station is handed over from microcell to microcell (1). A mobile station turns a corner then moves indoors. 1. Call starts at (2). The signal level is normal. 2. The mobile station signal level drops below the high threshold level (3), e.g., when turning a corner. To protect the call, it is handed over to the macrocell until a better microcell is found. The call remains with the macrocell until a strong signal from another microcell is received (normal case). 3. If a strong signal from a microcell cannot be found, a weaker signal from a microcell with enough strength to be above M_to_m threshold level, but that remains below the high threshold is found (4). In this case, as long as the signal strength remains above the low threshold and there is not a better microcell, the call remains with that microcell (e.g., the mobile station is indoors). 4. The signal level drops below the low threshold (5). The mobile station is again passed to the macrocell (e.g., the mobile station moves further inside a building). The macrocell is used to ensure call quality. 5. The mobile station moves into a position where the mobile station reports a microcell signal level above the M_to_m threshold (6). The call is handed over to that microcell, e.g., the mobile station is still indoors, but has a stronger signal from a microcell.
225 / 262
7 Cell Environments
Lower layer
Indoor layer
Figure 74: Indoor Cell Example Network Hierarchy with Three Layers and Two Bands
226 / 262
7 Cell Environments
The already deployed network hierarchy has to be adapted as follows: If there were already two layers, cells belonging to the upper layer will remain unchanged. Outdoor cells belonging to the lower layer will also remain in the lower layer. New cells introduced for the indoor layer will belong to the indoor layer 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.
Note:
This feature only applies to BTS A9100. Each set of TRX in a certain BTS must have its own coupling. It is possible to combine the coupling output towards the same antenna through an additional duplexer, although this is a special installation. The fact that part of the sector is in another BTS does not increase the number of necessary antennae. For BTS A9100, each BTS can have one slave, but each slave can in turn have another slave, up to a maximum of three linked slaves for one master BTS. If linked BTSs support part of the same cell, the linked BTSs must be clock synchronized with each other (master/slave). With this feature, the operator can associate two physical sectors from different BTSs into one shared sector. This shared sector can be mono or dual-band and it can support one cell as a normal sector. It takes the identity of one of the physical sectors, called the primary sector. The other physical sector is the secondary sector.
227 / 262
7 Cell Environments
228 / 262
229 / 262
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 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 Fault Management is used to supervise and to repair the network when anomalies occur. This is done through a sequence of steps from detection to report and recovery. These are carried out by all the BSS/MFS subsystems, and are reported to the operator at the OMC-R. Performance Management. Performance Management is used to monitor the efficiency of the system and the telecom services. It is controlled entirely from the OMC-R and provides measurements and statistics about various traffic events and resource use in the BSS.
230 / 262
Is used... By the BTS to monitor the condition of the hardware modules it manages, and report any change in status to the BSC. By the BSC to supervise its own hardware modules and report changes in status to the OMC-R. By the BSC and Transcoder together to provide a set of transmission O&M functions to ensure a high level of fault tolerance and reliability. The functions also provides efficient use of the terrestrial links between the equipment of the BSS. By the MFS to supervise its own hardware modules and report changes in status to the OMC-R. For more information, see Fault Management - Alarms (Section 8.5).
Performance Management
By the BSC and the MFS to: Collect raw measurement data from network elements Transfer the raw measurement data to the OMC-R, where the results are processed and displayed. For more information, see Performance Management (Section 8.6).
231 / 262
232 / 262
BSC Terminal User Guide Transmission Terminal User Guide BTS Terminal User Guide EVOLIUM A9125 Compact TC Terminal User Guide EVOLIUM A9135 MFS IMT User Guide
233 / 262
234 / 262
HMI Server
X.25 Network
OMCR Host n
HMI
235 / 262
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 OMC-Rs, 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 OMCR Workstation
OMCR 3
OMCR 1
Area 3
Area 1
OMCR 2
Area 2
ACO
OSI CPRA 2
: Common Management Information Service Element : Common Processor Type A : File Transfer Access and Management : High Speed Interface : Open System Interconnection
236 / 262
Definition of the primary and the secondary links based on their hardware configuration can achieve various types of redundancy, such as: OMC-R-side redundancy BSC-side redundancy Complete redundancy. The following figure illustrates these redundancy types.
OMCR X.25 Network HSI Board 0 1 2 3 3 1 2 OSI CPRA 2 Secondary Link BSC Primary Link OSI CPRA 1
Secondary Link Configurations 1. OMCR side redundancy 2. BSC side redundancy 3. Complete redundancy
237 / 262
238 / 262
Configuration Management Functions Communication through the LAPD link with the BSC Reading and modifying parameters Control station and GPU configuration Framer configuration for Gb Interface messages GPU switch configuration for circuit-switched connections.
239 / 262
8.4.4 Auto-Identification
Auto-Identification gives the BTS A9100 and the BTS A9110 the capacity to recognize their own hardware configuration, and to provide this information to the OMU and the BTS Terminal. The auto-identification procedure is triggered by the OMU in the following situations: BTS/SUM power up BTS reset OMU reset/auto reset Module initialization (on maintenance operator command, or during a Local Recovery Action or Hardware Extension, the auto identification takes place only for the module(s) concerned by the operation). The BTS A9100 and the BTS A9110 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.
240 / 262
EVOLIUM BTS A9100/A9110 Functional Description EVOLIUM BTS A9100 Hardware Description EVOLIUM BTS A9110 Hardware Description BTS Terminal User Guide.
241 / 262
242 / 262
243 / 262
244 / 262
Network Fault Management Functions Element BTS Testing the equipment. This includes collecting alarms and reporting to the BSC. Fault detection, fault correlation and fault localization for the BTS Management of equipment states. This includes triggering BTS channel configuration in case of a failure. Provides access for local diagnostics and configuration of the BTS BTS power supply control Event report management. See Alarm Generation (Section 8.5.1) for further information concerning events. MFS Collects all fault information for telecom and external alarms, the telecommunications hardware and the active server Records the fault information in a table Allows the IMT and the OMC-R access to the fault information Generates the ending alarm for pending alarms Manages the communications with the IMT.
245 / 262
Alarms can be generated as a result of previous alarms or events which influence other parts of the system. For example, when the Carrier Unit produces an alarm to signal an internal fault, the FU and the Radio Signaling Link produce alarms to signal that no information is being received from the Carrier Unit. Fault correlation and filtering actions are performed by the O&M modules in each unit, so that a single fault is sent as an alarm. In the case of the faulty Carrier Unit, an alarm is sent signaling a Carrier Unit fault. In this example, the loss of the RSL link is signalled from the BSC but is not correlated. Refer also to Alarm Handling in the Operations & Maintenance Principles document.
8.5.2.1 Correlation
Correlation refers to the collection and analysis of all available fault indications for a particular problem. Fault correlation is performed to define where and why the fault occurred. An example of correlation is described below: 1. When several boards in the BTS report clock problems, these reports are correlated by the OMU. 2. The clock generator is faulty alarm is sent to the OMC-R via the BSC.
8.5.2.2 Filtering
Alarms are filtered to minimize the number of fault alarms reported and displayed to the operator and are displayed in order of severity. Refer also to Alarm Handling in the Operations & Maintenance Principles document. To reduce the number of alarms in the OMC-R, short end alarms are filtered. For these alarms a BEGIN is raised soon after the previous END. These END /BEGINs are not considered significant and are filtered. The operator sees fewer alarms and is informed that alarms are filtered, because the number of filtered alarms, if any, is indicated in AS.
8.5.2.3 Persistency
A fault is signaled only if there is no recovery after the timer expires. For example, for a LAPD failure of an RSL link, an alarm is only sent if the LAPD link has not recovered before the persistency timer has expired.
246 / 262
247 / 262
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.
Fault Start RSL1 Persistency Correlation CPR Informed RSL State Change Alarm begin BTS_TEL ACTIVE INACTIVE Fault Start RSL2
CPR RSL
248 / 262
Note:
249 / 262
250 / 262
251 / 262
252 / 262
Note:
In the BTS A9100 or the BTS A9110, the SBLs FU and Carrier Unit have been merged into one indivisible SBL, called the TRE. At the BSC, however, all BTS A9100 and BTS A9110 TRE faults are mapped to the Carrier Unit to provide compatibility with G1 and G2 BTSs. Thus, at the BSC all such errors are displayed as Carrier Unit faults. That is how they are presented in this example. FU faults in G1 and G2 BTSs continue to be reported as such.
253 / 262
5. The BTS receives and acknowledges the recovery message. It then switches off the faulty Carrier Unit and switches on the second Carrier Unit. The second Carrier Unit adjusts its frequency to the BCCH frequency. 6. If the configuration was successful, the BTS sends a confirmation to the BSC. The BSC then sends the new sys_info (1-6). 7. The BCCH is now broadcasting on the same frequency as before, via the newly configured Carrier Unit. 8. The BSC sets the BTS_TEL SBL to FIT and informs the OMC-R by sending an end of alarm. The BTS_TEL remains FIT due to the loss of a channel. 9. If the new Carrier Unit was previously IT, its previously attached resources are lost. An alarm is sent to the OMC-R to update the information on lost channels. The following figure shows the redundancy process for a failed Carrier Unit with BCCH.
OMC BSC
BTS_TEL=IT
Resources blocked, BCCH reconfiguration possible
req ( Reco_ CU, F OS)
BTS
CU Fault
BTS_TEL=FIT
BTS_C
ONF_
DATA
BTS_TEL=FIT
(2)
6 8
of BC CH en d)
BTS_C
SYS_IN
FO (1..6
Alarm
ss (cell, lo
BTS_TEL=FIT
BCCH CU TCH
Note:
The 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.
254 / 262
EVOLIUM BTS A9100/A9110 Functional Description EVOLIUM BTS A9100 Hardware Description EVOLIUM BTS A9110 Hardware Description.
Note:
For performance reasons, each alerter type has a maximum limit of 16 alarms. For more information about BSC Alerters, refer to BSC Alerters in the Operations & Maintenance Principles document.
255 / 262
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. Call tracing follows a specified transaction (subscriber call, location update, short message, etc.) inside the BSC. When the specified transaction ends, or the transaction changes to another BSC, the trace activity ends. IMSI tracing is not restricted to speech. It includes information about the radio resources set up for the mobile. This includes, for example, location updating, supplementary services, short messages, etc. For more information on trace management, refer to Trace Management in the Operations & Maintenance Principles document.
256 / 262
257 / 262
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 of 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. Voice quality statistics. Nine counters and indicators provide an overview of the communications quality (TCH only) for each TRX. Radio Measurement Statistics is available on G1 BTS Mk2, G2 BTS equipped with DRFU and EVOLIUM BTS.
258 / 262
8.7 Audits
Audits can be automatic or initiated by an operator. They can be performed at several levels: From the OMC-R to the Transcoder, the BSC, or the MFS From the BSC to the BTS. More information on Audits can be found in the Operations & Maintenance Principles document. as follows: Configuration Management Audits in Configuration Management Audits/Resynchronization Fault Management Audits in Fault Management Audits. Using the IMT, it is possible to perform a radio re-initialization, or a radio resynchronization of the MFS.
Alarm Audit
State Audit
259 / 262
Two types of action are possible for the MFS: Re-initialize GPRS configuration Allows the OMC-R to force the logical configuration of the MFS, by deleting the current one, and then recreating one from scratch, using the current OMC-R configuration. This is roughly the equivalent of a Force configuration at the BSS side. However, it always induces some outages Resynchronize GPRS configuration. Allows the OMC-R to force the logical configuration of the MFS, by computing the differences with the current OMC-R configuration. It is the preferred synchronization action at the MFS side, as it minimizes the MFS outage. A suite of audits is automatically invoked by the OMC-R or the BSC to resynchronize the system. This is done: To perform a RESET/RESTART When there is a loss of links between subsystems. This ensures that the system databases are synchronized after autonomous operation while the link was down (i.e., the BTS_O&M was disabled). To make changes in the databases, without the possibility of aligning both subsystems To start a BSC Alarms-in-Force audit if the BSC alarm queue overflows To perform software database replacement. Audit information for the whole system is stored in the OMC-R.
260 / 262
261 / 262
262 / 262