UMT SYS DD 0054 V11.06 UMTS Radio Mobility Approved Standard

UMTS Radio Mobility

Document number: UMT/SYS/DD/0054 Document issue: 11.06/EN Document status: Approved_Standard Date: 17/Sep/2010

External document

Copyright 2009 Alcatel-Lucent, All Rights Reserved

Printed in France

UNCONTROLLED COPY: The master of this document is stored on an electronic database and is “write protected”; it may be altered only by authorized persons. While copies may be printed, it is not recommended. Viewing of the master electronically ensures access to the current issue. Any hardcopies taken must be regarded as uncontrolled copies.

ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is the property of Alcatel-Lucent. Except as expressly authorized in writing by Alcatel-Lucent, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information from disclosure and dissemination to third parties. Except as expressly authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the information contained herein. If you have received this document in error, please notify the sender and destroy it immediately.

UMTS Radio Mobility

Passing on or copying of this document, use and communication of its contents not permitted without Alcatel·Lucent written authorization

UMT/SYS/DD/0054 11.06/EN Approved_Standard 17/Sep/2010 Page 2/244

PUBLICATION HISTORY

17/September/2010

Issue 11.06 / EN, Approved_Standard

• Standard edition, no remark received.

03/September/2010

Issue 11.05 / EN, Approved_Preliminary

• Correction on 81204 - Dual cell Hsdpa operation chapter

• Update after review.

04/May/2010

Issue 11.04 / EN, Draft

Minor correction on §1.2.

CR DCTPD00265749: describe restriction in case of Relocation UE Not Involved from UA7.1 to UA6.

07/April/2010


Introduction of the following feature:

• 81204 - Dual cell Hsdpa operation

23/March/2010


Introduction of the following feature:

• 81213 - Load balancing between HSPA carriers

28/January/2010


Introduction of the following features:

• 81436 - Mobility between UMTS and LTE - Cell reselection

• 104489 - LTE to UMTS HO

04/September/2009

Issue 10.02 / EN, Standard

Standard edition after review

UMTS Radio Mobility



03/July/2009

Issue 10.01 / EN, Preliminary

New version for UA07.1; Introduction of § previously in Traffic management FN; reorganization of redirection chapters

29/June/2009

Issue 09.05 / EN, Standard

Standard Edition

UMTS Radio Mobility



CONTENTS

CONTENTS..............................................................................................................................................4

1. INTRODUCTION...............................................................................................................................14

1.1. OBJECT ....................................................................................................................................14

1.2. SCOPE OF THIS DOCUMENT ........................................................................................................14

1.3. AUDIENCE FOR THIS DOCUMENT .................................................................................................15

1.4. DEFINITIONS AND SPECIFICATION PRINCIPLES.............................................................................15

2. RELATED DOCUMENTS .................................. ...............................................................................15

2.1. APPLICABLE DOCUMENTS...........................................................................................................15

2.2. REFERENCE DOCUMENTS...........................................................................................................16

3. DEFINITIONS & CONCEPTS...........................................................................................................17

3.1. NETWORK ARCHITECTURE..........................................................................................................17

3.2. 3GPP BASIC PROCEDURES..........................................................................................................18 3.2.1 Soft handover................................................................................................................18 3.2.2 Softer handover ............................................................................................................18 3.2.3 Hard handover ..............................................................................................................19 3.2.4 Cell reselection .............................................................................................................20 3.2.5 SRNS relocation ...........................................................................................................20 3.2.6 Radio Link Reconfiguration...........................................................................................21

4. MOBILITY CASES..................................... .......................................................................................22

4.1. SOFT HANDOVER INTRA RNC .............................................................................................24 4.1.1 Description ....................................................................................................................24 4.1.2 Applicability ...................................................................................................................25 4.1.3 Parameters ...................................................................................................................25 4.1.4 Access Network impacts...............................................................................................25 4.1.5 Core Network impacts ..................................................................................................25

4.2. SOFT HANDOVER INTER RNC .............................................................................................26 4.2.1 Description ....................................................................................................................26 4.2.2 Applicability ...................................................................................................................28 4.2.3 Parameters ...................................................................................................................28 4.2.4 Access Network impacts...............................................................................................28 4.2.5 Core Network impacts ..................................................................................................28

4.3. SOFTER HANDOVER ............................................................................................................29 4.3.1 Description ....................................................................................................................29 4.3.2 Applicability ...................................................................................................................29 4.3.3 Parameters ...................................................................................................................30 4.3.4 Access Network impacts...............................................................................................30 4.3.5 Core Network impacts ..................................................................................................30

4.4. CELL RESELECTION IN “IDLE MODE”..................................................................................30 4.4.1 Description ....................................................................................................................30 4.4.2 Applicability ...................................................................................................................30 4.4.3 Algorithm.......................................................................................................................30

UMTS Radio Mobility



4.4.3.1 Neighbouring cells measurement rules ...................................................................31 4.4.3.2 Neighbouring cells measurement rules when using absolute priority .....................31 4.4.3.3 Criteria S..................................................................................................................32 4.4.3.4 Cell ranking criteria ..................................................................................................33 4.4.3.5 Cell ranking criteria when using absolute priority ....................................................33 4.4.3.6 Overall cell reselection process...............................................................................33 4.4.3.7 Overall cell reselection process when using absolute priority .................................34

4.4.4 Parameters ...................................................................................................................35 4.4.4.1 At UTRAN/FDD cell level.........................................................................................35 4.4.4.2 At UTRAN/FDD neighbouring cell level...................................................................38 4.4.4.3 At GSM neighbouring cell level ...............................................................................39

4.4.5 Access Network impacts...............................................................................................39 4.4.6 Core Network impacts ..................................................................................................39

4.5. CELL RESELECTION IN “CELL FACH AND CELL/URA PCH MODE” ..................................39 4.5.1 Description ....................................................................................................................39

4.5.1.1 Intra-RNC case ........................................................................................................39 4.5.1.2 Inter-RNC case ........................................................................................................40 4.5.1.3 3G to 2G case..........................................................................................................43 4.5.1.4 2G to 3G case..........................................................................................................44 4.5.1.5 3G to E-UTRAN case ..............................................................................................44 4.5.1.6 Dual cell hsdpa case................................................................................................44

4.5.2 Applicability ...................................................................................................................44 4.5.3 Algorithm.......................................................................................................................44 4.5.4 Parameters ...................................................................................................................44

4.5.4.1 at UTRAN/FDD cell level .........................................................................................45 4.5.4.2 At UTRAN/FDD neighbouring cell level...................................................................47 4.5.4.3 At GSM neighbouring cell level ...............................................................................47

4.5.5 Access Network impacts...............................................................................................47 4.5.6 Core Network impacts ..................................................................................................47

4.6. 2G TO 3G HANDOVER FOR CS DOMAIN .............................................................................47 4.6.1 Description ....................................................................................................................47

4.6.1.1 Dataflow...................................................................................................................47 4.6.1.2 Target resource description.....................................................................................50

4.6.2 Applicability ...................................................................................................................50 4.6.3 Algorithm.......................................................................................................................51

4.6.3.1 Relocation Request Message structure...................................................................51 4.6.3.2 Relocation Request Rejection .................................................................................51 4.6.3.3 Target resource allocation in RNC ..........................................................................51 4.6.3.4 CipherinG.................................................................................................................52 4.6.3.5 Integrity ....................................................................................................................52 4.6.3.6 Dependencies with GSM .........................................................................................52 4.6.3.7 Use of Default Configuration ...................................................................................53

4.6.4 Failure cases.................................................................................................................53 4.6.4.1 Connection Release ................................................................................................53 4.6.4.2 return on old channel ...............................................................................................53 4.6.4.3 Relocation rejected by target RNC..........................................................................54

4.6.5 Parameters ...................................................................................................................55 4.6.6 Access Network impacts...............................................................................................55 4.6.7 Core Network impacts ..................................................................................................55

4.7. 2G TO 3G HANDOVER FOR PS DOMAIN .............................................................................55

4.8. 2G TO 3G HANDOVER FOR CS + PS DOMAINS ..................................................................56

4.9. 3G TO 2G HANDOVER FOR PS DOMAIN .............................................................................56 4.9.1 Description ....................................................................................................................56 4.9.2 Applicability ...................................................................................................................58 4.9.3 Algorithm.......................................................................................................................58

4.9.3.1 HO Decision Process...............................................................................................58 4.9.3.2 MeasurementS configuration...................................................................................58

UMTS Radio Mobility



4.9.3.3 Target cell choice.....................................................................................................58 4.9.4 Failure cases.................................................................................................................58

4.9.4.1 target cell synchronization failure ............................................................................58 4.9.5 Parameters ...................................................................................................................59 4.9.6 Access Network impacts...............................................................................................59 4.9.7 Core Network impacts ..................................................................................................59

4.10. 3G TO 2G HANDOVER FOR CS DOMAIN .............................................................................59 4.10.1 Description ....................................................................................................................59 4.10.2 Applicability ...................................................................................................................61 4.10.3 Algorithm.......................................................................................................................61

4.10.3.1 HO Decision Process...............................................................................................61 4.10.3.2 MeasurementS configuration...................................................................................61 4.10.3.3 Target Cell Choice ...................................................................................................61

4.10.4 Failure cases.................................................................................................................61 4.10.4.1 target cell synchronization failure ............................................................................61 4.10.4.2 Relocation Preparation Failure ................................................................................62

4.10.5 Parameters ...................................................................................................................62 4.10.6 Access Network impacts...............................................................................................63 4.10.7 Core Network impacts ..................................................................................................63 4.10.8 Performance Management ...........................................................................................63

4.11. 3G TO 2G HANDOVER FOR CS+PS DOMAINS....................................................................63 4.11.1 Description ....................................................................................................................63

4.11.1.1 General ....................................................................................................................63 4.11.1.2 Successful Class A/DTM case ................................................................................65 4.11.1.3 Successful Class B case .........................................................................................67 4.11.1.4 handling Unsuccessful cases ..................................................................................67


4.11.3.1 HO Decision Process...............................................................................................70 4.11.3.2 MeasurementS configuration...................................................................................70 4.11.3.3 Target Cell Choice ...................................................................................................70

4.11.4 Parameters ...................................................................................................................70 4.11.5 Access Network impacts...............................................................................................70 4.11.6 Core Network impacts ..................................................................................................70

4.12. 4G TO 3G RELOCATION FOR PS DOMAIN ..........................................................................70 4.12.1 Description ....................................................................................................................70

4.12.1.1 Dataflow...................................................................................................................70 4.12.2 Algorithm.......................................................................................................................73

4.12.2.1 Relocation Request Message structure...................................................................73 4.12.2.2 Relocation Request Rejection .................................................................................74 4.12.2.3 Target resource allocation in RNC ..........................................................................74 4.12.2.4 CipherinG.................................................................................................................75 4.12.2.5 Integrity ....................................................................................................................75 4.12.2.6 Dependencies with LTE...........................................................................................76

4.12.3 Failure cases.................................................................................................................76 4.12.3.1 Relocation rejected by target RNC..........................................................................76

4.12.4 Parameters ...................................................................................................................76 4.12.5 Access Network impacts...............................................................................................77 4.12.6 Core Network impacts ..................................................................................................77 4.12.7 CS FALLBACK..............................................................................................................77

4.13. INTER-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR...........................................78 4.13.1 Description ....................................................................................................................78

4.13.1.1 General ....................................................................................................................78 4.13.2 Applicability ...................................................................................................................81 4.13.3 Algorithm.......................................................................................................................81

4.13.3.1 HO Decision process...............................................................................................81 4.13.3.2 MeasurementS configuration...................................................................................81

UMTS Radio Mobility



4.13.3.3 Target Cell Choice ...................................................................................................81 4.13.4 Failure cases.................................................................................................................81 4.13.5 Parameters ...................................................................................................................81 4.13.6 Access Network impacts...............................................................................................82 4.13.7 Core Network impacts ..................................................................................................82

4.14. INTRA-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR...........................................82 4.14.1 Description ....................................................................................................................82 4.14.2 Applicability ...................................................................................................................82 4.14.3 Algorithm.......................................................................................................................82

4.14.3.1 Iur interface status ...................................................................................................82 4.14.3.2 Measurement configuration .....................................................................................83 4.14.3.3 HO decision .............................................................................................................83

4.14.3.3.1 reception of measurement report measId 1 .......................................................83 4.14.3.3.2 reception of measurement report measId 16 .....................................................83

4.14.4 Parameters ...................................................................................................................83 4.14.5 Access network impact .................................................................................................84 4.14.6 Core network impact.....................................................................................................84

4.15. INTER-FREQUENCY INTRA-RNC HANDOVER....................................................................84 4.15.1 Description ....................................................................................................................84

4.15.1.1 General ....................................................................................................................84 4.15.1.2 Over the Iur..............................................................................................................85


4.15.3.1 HO decision process................................................................................................87 4.15.3.2 Measurements configuration ...................................................................................87 4.15.3.3 choice of target cell..................................................................................................87

4.15.4 Failure cases.................................................................................................................87 4.15.5 Parameters ...................................................................................................................87 4.15.6 Access Network impacts...............................................................................................88 4.15.7 Core Network impacts ..................................................................................................88 4.15.8 Performance management ...........................................................................................88

4.16. INTER-FREQUENCY INTER-RNC HANDOVER WITH IUR AND MEASUREMENTS...........88 4.16.1 Description ....................................................................................................................89

4.16.1.1 General ....................................................................................................................89 4.16.1.2 From SRNC TO DRNC............................................................................................89 4.16.1.3 From DRNC TO DRNC............................................................................................90 4.16.1.4 From DRNC TO SRNC............................................................................................92


4.16.3.1 HO decision process................................................................................................93 4.16.3.2 Measurements configuration ...................................................................................93 4.16.3.3 choice of target cell..................................................................................................94

4.16.4 Failure cases.................................................................................................................94 4.16.5 Parameters ...................................................................................................................94 4.16.6 Access Network impacts...............................................................................................94 4.16.7 Core Network impacts ..................................................................................................94 4.16.8 Performance management ...........................................................................................94

4.17. SRNS RELOCATION – “UE NOT INVOLVED” .......................................................................94 4.17.1 Description ....................................................................................................................94 4.17.2 Applicability ...................................................................................................................95 4.17.3 Algorithm.......................................................................................................................95 4.17.4 Parameters ...................................................................................................................95 4.17.5 Access Network impacts...............................................................................................95 4.17.6 Core Network impacts ..................................................................................................95

4.18. REDIRECTION FEATURES FOR TRAFFIC SEGMENTATION.............................................95 4.18.1 REDIRECTION AT CONNECTION SETUP (iMCRA step 1) .......................................95

4.18.1.1 Description...............................................................................................................95

UMTS Radio Mobility



4.18.1.2 Applicability..............................................................................................................97 4.18.1.2.1 Interaction with Cell_FACH: ...............................................................................97 4.18.1.2.2 Interaction with follow-on / Subscribed Traffic Class:.........................................97 4.18.1.2.3 Emergency calls: ................................................................................................97 4.18.1.2.4 HSPA Load.........................................................................................................98 4.18.1.2.5 Initial Power on Redirection................................................................................99

4.18.1.3 Algorithm..................................................................................................................99 4.18.1.3.1 Redirection Type = UE capability only................................................................99 4.18.1.3.2 Redirection Type = UE capability and establishment cause ........................... 102 4.18.1.3.3 Redirection Type = Preferred FA..................................................................... 103 4.18.1.3.4 Redirection Type = CAC.................................................................................. 104 4.18.1.3.5 Redirection Type = None................................................................................. 104

4.18.1.4 failure cases:......................................................................................................... 104 4.18.1.5 Parameters ........................................................................................................... 104

4.18.2 3G2G REDIRECTION AT RRC ESTABLISHMENT FOR SPEECH CALLS............. 108 4.18.2.1 Description............................................................................................................ 108 4.18.2.2 Applicability........................................................................................................... 108 4.18.2.3 Algorithm............................................................................................................... 109 4.18.2.4 Parameters ........................................................................................................... 110

4.18.3 EMERGENCY AND PRIORITY CALLS..................................................................... 111 4.18.3.1 Description............................................................................................................ 111 4.18.3.2 Apllicability ............................................................................................................ 111 4.18.3.3 Algorithm............................................................................................................... 111 4.18.3.4 Parameters ........................................................................................................... 113 4.18.3.5 Performance management ................................................................................... 114

4.18.4 3G2G REDIRECTION BASED ON CELL LOAD....................................................... 115 4.18.4.1 Description............................................................................................................ 115 4.18.4.2 Applicability........................................................................................................... 115 4.18.4.3 Algorithm............................................................................................................... 116 4.18.4.4 Parameters ........................................................................................................... 118 4.18.4.5 Performance management ................................................................................... 119

4.18.5 PRIORITY BETWEEN RRC REDIRECTION FEATURES........................................ 119 4.18.5.1 Description............................................................................................................ 119 4.18.5.2 Algorithm............................................................................................................... 119

4.18.6 Access Network impacts............................................................................................ 120 4.18.7 Core Network impacts ............................................................................................... 120

4.19. DUAL CELL HSDPA OPERATION ................................................................................................. 121 4.19.1 description.................................................................................................................. 121 4.19.2 Aplicability .................................................................................................................. 121 4.19.3 Algorithm.................................................................................................................... 122

4.19.3.1 Soft Handover....................................................................................................... 122 4.19.3.1.1 Active Set Update............................................................................................ 122 4.19.3.1.2 Primary Link Change ....................................................................................... 122 4.19.3.1.3 Uplink Aspects................................................................................................. 125 4.19.3.1.4 SRB Aspects.................................................................................................... 125 4.19.3.1.5 IuR Aspects ..................................................................................................... 125 4.19.3.1.6 Messaging ....................................................................................................... 125

4.19.3.2 Hard Handover ..................................................................................................... 126 4.19.3.2.1 HHO from R99/SC/DC to DC .......................................................................... 126 4.19.3.2.2 HHO from DC to SC/R99................................................................................. 127

4.19.3.3 SRNS Relocation.................................................................................................. 127 4.19.3.3.1 UE Involved ..................................................................................................... 127 4.19.3.3.2 UE Not Involved............................................................................................... 128

4.19.3.4 Compressed Mode ............................................................................................... 128 4.19.4 Parameters ................................................................................................................ 128 4.19.5 Performance management ........................................................................................ 128

4.20. INTELLIGENT MULTI CARRIER TRAFFIC ALLOCATION (IMCTA) ................................... 128 4.20.1 Description ................................................................................................................. 129

UMTS Radio Mobility



4.20.1.1 iMCTA triggers...................................................................................................... 129 4.20.1.2 Crossover between iMCTA triggers or with others procedures............................ 131

4.20.2 Applicability ................................................................................................................ 131 4.20.2.1 Management in Cell HSxPA ................................................................................. 131 4.20.2.2 Iur management.................................................................................................... 131

4.20.2.2.1 iMCTA trigger = SERVICE .............................................................................. 132 4.20.2.2.2 iMCTA trigger = CAC FAILURE ...................................................................... 132 4.20.2.2.3 iMCTA trigger = ALARM.................................................................................. 132

4.20.2.3 2G Inter RAT management .................................................................................. 133 4.20.2.3.1 iMCTA trigger = SERVICE .............................................................................. 133 4.20.2.3.2 iMCTA trigger = CAC FAILURE ...................................................................... 133 4.20.2.3.3 iMCTA trigger = ALARM.................................................................................. 133

4.20.2.4 iMCTA load based HO developments [USA Market]............................................ 134 4.20.3 Algorithm.................................................................................................................... 134

4.20.3.1 Main functional steps ............................................................................................ 134 4.20.3.2 iMCTA Feature activation ..................................................................................... 134 4.20.3.3 Neighbour Carriers Selection ............................................................................... 134 4.20.3.4 Neighbour Cells Selection for Measurement Reporting ....................................... 135 4.20.3.5 Compressed mode and measurement configuration ........................................... 135 4.20.3.6 Target Cell Selection upon Measurement Report ................................................ 136

4.20.3.6.1 IMCTA trigger is Service.................................................................................. 136 4.20.3.6.2 IMCTA trigger is CAC FAilure.......................................................................... 137 4.20.3.6.3 IMCTA trigger is Alarm .................................................................................... 137

4.20.3.7 iMCTA Hard handover processing or iMCTA exit ................................................ 138 4.20.3.7.1 IMCTA HHO processing .................................................................................. 138 4.20.3.7.2 IMCTA Exit....................................................................................................... 139

4.20.3.8 iMCTA Cell load criteria ........................................................................................ 139 4.20.3.8.1 cell load indicators ........................................................................................... 139 4.20.3.8.2 Originating Fdd Cell eligibility .......................................................................... 139 4.20.3.8.3 [USA Market] target FDD cell Load iMCTA load based HO criteria (used for

CAC and Alarm): ............................................................................................. 140 4.20.3.8.4 Target Fdd Cell eligibility (used for Service).................................................... 140 4.20.3.8.5 Target 2G Cell eligibility................................................................................... 140 4.20.3.8.6 Target 2G Cell color definition......................................................................... 141

4.20.4 Parameters ................................................................................................................ 141 4.20.4.1 iMCTA Options ..................................................................................................... 141

4.20.4.1.1 Service Segmentation Option Definition.......................................................... 143 4.20.4.1.2 Service Handover Option Definition ................................................................ 144 4.20.4.1.3 HSDPA Traffic Segmentation option definition................................................ 144

4.20.4.2 iMCTA Priority Tables........................................................................................... 144 4.20.4.2.1 iMCTA Priority Table definition: General aspects............................................ 145 4.20.4.2.2 iMCTA Alarm and CAC Priority Tables definition ............................................ 146 4.20.4.2.3 iMCTA Service Priority Table definition........................................................... 146 4.20.4.2.4 iMCTA Service Type definition ........................................................................ 146 4.20.4.2.5 IMCTA Service Segmentation Priority Table definition ................................... 147 4.20.4.2.6 IMCTA Service for Traffic Segmentation Priority definition ............................. 147

4.20.5 Performance Management ........................................................................................ 147

4.21. HSDPA AND HSUPA MOBILITY ......................................................................................... 147 4.21.1 Description ................................................................................................................. 148

4.21.1.1 Deployment scenarios .......................................................................................... 148 4.21.1.1.1 HSPDA on dedicated layer.............................................................................. 148 4.21.1.1.2 HSDPA on existing layer ................................................................................. 148

4.21.1.2 Redirection at connection setup ........................................................................... 149 4.21.1.3 HSDPA and HSUPA call mobility procedures ...................................................... 149

4.21.1.3.1 Intra-frequency mobility ................................................................................... 149 4.21.1.3.2 compressed mode ........................................................................................... 150 4.21.1.3.3 Inter-frequency mobility ................................................................................... 150 4.21.1.3.4 Inter-system mobility........................................................................................ 152

4.21.2 Applicability ................................................................................................................ 152

UMTS Radio Mobility



4.21.3 Algorithm.................................................................................................................... 152 4.21.4 Parameters ................................................................................................................ 152 4.21.5 Access Network impacts............................................................................................ 152 4.21.6 Core Network impacts ............................................................................................... 152

4.22. MOBILITY IN CELL_PCH AND URA_PCH RRC STATES .................................................. 153 4.22.1 Description ................................................................................................................. 153 4.22.2 Applicability ................................................................................................................ 155 4.22.3 Algorithm.................................................................................................................... 155 4.22.4 Parameters ................................................................................................................ 155 4.22.5 Access Network impacts............................................................................................ 155 4.22.6 Core Network Impacts ............................................................................................... 156

4.23. HCS: CELL RESELECTION CONTROL IN A HIERARCHICAL CELL STRUCTURE [GLOBAL MARKET]................................................................................................................................ 156

4.23.1 Description ................................................................................................................. 156 4.23.2 Applicability ................................................................................................................ 157 4.23.3 Algorithm.................................................................................................................... 158

4.23.3.1 Cell Reselection Criteria when HCS is used ........................................................ 159 4.23.3.2 Inter RNC Case .................................................................................................... 161

4.23.4 Parameters ................................................................................................................ 161 4.23.4.1 At UTRAN/FDD cell level...................................................................................... 161 4.23.4.2 At UTRAN/FDD neighbouring cell level................................................................ 163 4.23.4.3 At GSM neighbouring cell level ............................................................................ 163

4.23.5 Access Network impacts............................................................................................ 163 4.23.6 Core Network impacts ............................................................................................... 163

5. COMMON PROCEDURES ............................................................................................................ 164

5.1. PERIODIC MEASUREMENT REPORTING MODE............................................................. 164

5.2. INTRA-FREQUENCY EVENT TRIGGERED MEASUREMENT REPORTING MODE ........ 164 5.2.1 Description ................................................................................................................. 164 5.2.2 configuration .............................................................................................................. 165

5.2.2.1 Common ID procedure handling........................................................................... 166 5.2.2.2 Measurement Control Failure ............................................................................... 166 5.2.2.3 Summary .............................................................................................................. 166

5.2.3 feature interworking ................................................................................................... 167 5.2.3.1 Radio Link color .................................................................................................... 167 5.2.3.2 SRLR blind window............................................................................................... 167

5.2.3.2.1 Event 1A, 1C, 1E, 1J ....................................................................................... 168 5.2.3.2.2 Event 1B, 1F.................................................................................................... 168 5.2.3.2.3 Event 1D.......................................................................................................... 168 5.2.3.2.4 Events 2D, 2F, 6A, 6B ..................................................................................... 168

5.2.4 Parameters ................................................................................................................ 168

5.3. ACTIVE SET MANAGEMENT.............................................................................................. 168 5.3.1 Algorithm for periodic reporting mode........................................................................ 168 5.3.2 Enhanced Algorithm for periodic reporting mode ...................................................... 169 5.3.3 Parameters for periodic reporting mode .................................................................... 170 5.3.4 Case of intra-frequency Event-Triggered Reporting mode........................................ 171

5.3.4.1 Description of event-triggered reporting measurements based on relative thresholds ............................................................................................................. 171

5.3.4.2 Description of event-triggered reporting measurements based on Absolute thresholds ............................................................................................................. 173

5.3.4.3 Algorithm............................................................................................................... 174 5.3.4.4 Configuration ........................................................................................................ 176

5.3.4.4.1 1A event configuration..................................................................................... 176 5.3.4.4.2 1B event configuration..................................................................................... 177 5.3.4.4.3 1C event configuration..................................................................................... 178 5.3.4.4.4 1E event configuration..................................................................................... 178

UMTS Radio Mobility



5.3.4.4.5 1F event configuration ..................................................................................... 179 5.3.5 Parameters for Event reporting mode........................................................................ 179 5.3.6 Performance management ........................................................................................ 181

5.3.6.1 Counters ............................................................................................................... 181 5.3.6.2 Traces................................................................................................................... 181

5.3.7 E-DCH active set management ................................................................................. 182

5.4. PRIMARY CELL DETERMINATION .................................................................................... 182 5.4.1 Description ................................................................................................................. 182 5.4.2 Case of intra-frequency Periodic Reporting mode..................................................... 182 5.4.3 Case of intra-frequency Event-Triggered Reporting mode........................................ 183

5.4.3.1 Description............................................................................................................ 183 5.4.3.2 Algorithm............................................................................................................... 184 5.4.3.3 Configuration ........................................................................................................ 184

5.4.3.3.1 1D event configuration..................................................................................... 184 5.4.4 Parameters ................................................................................................................ 185

5.5. LIST OF COMPOUNDING CELLS FOR THE MONITORED SET DEFINITION .................. 185 5.5.1 Description ................................................................................................................. 185 5.5.2 Applicability ................................................................................................................ 185 5.5.3 Algorithm.................................................................................................................... 186 5.5.4 Parameters ................................................................................................................ 187 5.5.5 Performance management ........................................................................................ 189

5.6. MANAGEMENT OF SYSTEM INFORMATION BLOCKS (SIB)........................................................... 189 5.6.1 SIB Update................................................................................................................. 189 5.6.2 SIB Repetition period................................................................................................. 190

5.7. INTRA-FREQ MEASUREMENTS CONFIGURATION VIA SIB11 ....................................... 191

5.8. DHO MANAGEMENT........................................................................................................... 191

5.9. ALARM HANDOVER AND ALARM MEASUREMENTS ...................................................... 192 5.9.1 Overview .................................................................................................................... 192 5.9.2 Alarm measurement activation with periodic Intra Frequency measurements.......... 193

6. ALARM MEASUREMENT ACTIVATION WITH EVENT BASED INTRA FREQUENCY MEASUREMENTS......................................................................................................................... 195

6.1.1.1 Description............................................................................................................ 195 6.1.1.2 Algorithm............................................................................................................... 196 6.1.1.3 Configuration ........................................................................................................ 200

6.1.1.3.1 2D event configuration..................................................................................... 201 6.1.1.3.2 2F event configuration ..................................................................................... 201 6.1.1.3.3 6A event configuration..................................................................................... 202 6.1.1.3.4 6B event configuration..................................................................................... 202

6.1.2 Parameters ................................................................................................................ 203

6.2. MEASUREMENTS CONFIGURATION FOR INTER-FREQ/2G INTER-RAT ...................... 204 6.2.1 Measurement reporting.............................................................................................. 204 6.2.2 Reported cells ............................................................................................................ 204 6.2.3 Configuration for inter-system measurements........................................................... 204 6.2.4 Configuration for inter-frequency measurements ...................................................... 205 6.2.5 Change of Measurement Type .................................................................................. 205 6.2.6 Parameters for Measurement .................................................................................... 206

6.2.6.1 Measurement activation parameters .................................................................... 206 6.2.6.2 Other Parameters ................................................................................................. 207

6.3. INTRA-FREQUENCY MEASUREMENTS ........................................................................... 207 6.3.1 Configuration.............................................................................................................. 207

6.3.1.1 Activation/Deactivation ......................................................................................... 207 6.3.1.2 Measurement reporting......................................................................................... 208 6.3.1.3 Reporting quantities.............................................................................................. 208 6.3.1.4 Reported cells....................................................................................................... 208

UMTS Radio Mobility



6.3.1.5 Filtering ................................................................................................................. 209 6.3.2 Missing Measurements.............................................................................................. 209

6.4. COMPRESSED MODE........................................................................................................ 210 6.4.1 Introduction ................................................................................................................ 210 6.4.2 UE capability .............................................................................................................. 210 6.4.3 Method ....................................................................................................................... 211 6.4.4 Measurement purpose............................................................................................... 212

6.4.4.1 GSM measurements............................................................................................. 212 6.4.4.2 FDD inter-frequency measurements .................................................................... 213

6.4.5 Pattern shape............................................................................................................. 213 6.4.5.1 GSM measurements............................................................................................. 213 6.4.5.2 FDD inter-frequency measurements .................................................................... 214

6.4.6 slot formats/ frame structure ...................................................................................... 214 6.4.7 Procedures & messages............................................................................................ 214

6.4.7.1 Data flow............................................................................................................... 214 6.4.7.2 RRC/RB Setup message...................................................................................... 215 6.4.7.3 RRC/RB Reconfiguration message ...................................................................... 216 6.4.7.4 RRC/Measurement Control message................................................................... 216 6.4.7.5 NBAP/Radio Link Reconfiguration Prepare message .......................................... 216 6.4.7.6 NBAP/Compressed Mode Command message ................................................... 217 6.4.7.7 NBAP/Radio link reconfiguration COMMIT message........................................... 217 6.4.7.8 RNSAP/Radio Link Setup/addition Request message ......................................... 217 6.4.7.9 RNSAP/Compressed Mode Command message ................................................ 218 6.4.7.10 RNSAP/Radio link reconfiguration COMMIT message ........................................ 218

6.4.8 Impacts on RRM Specific for SF/2 method ............................................................... 218 6.4.8.1 Code tree management........................................................................................ 218

6.4.9 HLS ............................................................................................................................ 219 6.4.9.1 HLS assumptionS ................................................................................................. 220 6.4.9.2 HLS GAP PATTERN configuration....................................................................... 220 6.4.9.3 Switching between Compressed Mode methods ................................................. 221 6.4.9.4 CM method selection rules: .................................................................................. 223

6.4.10 SRNS Relocation....................................................................................................... 224 6.4.11 RNS Inter-release Compatibility Use cases .............................................................. 226 6.4.12 DRNS scenarios ........................................................................................................ 228 6.4.13 Alpha CEM cards impact ........................................................................................... 229 6.4.14 UE impacts................................................................................................................. 230 6.4.15 Impact on other procedures....................................................................................... 230

6.4.15.1 intra-NodeB soft handover.................................................................................... 230 6.4.15.2 intra-RNC/inter-NodeB soft handover................................................................... 230 6.4.15.3 inter-RNC soft handover ....................................................................................... 231

6.4.16 Change of Alarm measurement type (Common HLS and SF/2) ............................... 232 6.4.17 Defence mechanism for UE not supporting CM with HSPA...................................... 233 6.4.18 Parameters ................................................................................................................ 234

6.4.18.1 Dynamic parameters............................................................................................. 234 6.4.18.2 O&M parameters .................................................................................................. 234

6.4.18.2.1 General parameters......................................................................................... 234 6.4.18.2.2 Pattern parameters.......................................................................................... 235 6.4.18.2.3 Power control parameters ............................................................................... 236 6.4.18.2.4 Static parameters ............................................................................................ 237 6.4.18.2.5 control performed by the ALCATEL-LUCENT RNC........................................ 238

6.5. 2G TARGET CELL CHOICE RADIO CRITERIA .................................................................. 238 6.5.1 Description ................................................................................................................. 238 6.5.2 Parameters ................................................................................................................ 239

6.6. FDD TARGET CELL CHOICE INTER FREQUENCY RADIO CRITERIA ............................ 239 6.6.1 Description ................................................................................................................. 239 6.6.2 Parameters ................................................................................................................ 240

6.7. NEIGHBOR CELLS FLEXIBLE MANAGEMENT ................................................................. 240

UMTS Radio Mobility



6.7.1 Description ................................................................................................................. 240 6.7.2 Algorithm.................................................................................................................... 240 6.7.3 Parameters ................................................................................................................ 241

7. ABBREVIATIONS AND DEFINITIONS...................... ................................................................... 242

7.1. ABBREVIATIONS ................................................................................................................ 242

7.2. DEFINITIONS ...................................................................................................................... 243

UMTS Radio Mobility



1. INTRODUCTION

1.1. OBJECT

This document specifies the UMTS mobility procedures for mobiles connected to the network. Intersystem mobility procedures (to and from GSM) are also described in this document.

Although this document is focused on UTRAN, it also addresses radio mobility procedure applicable to the Core Network.

How is the document structured?

Chapter3 presents definitions and concepts which will be used throughout the document.

Chapter4 contains the mobility cases supported in this version of the document

Chapter5 contains common procedures used in several mobility cases (such as measurement processing, compressed mode ...)

1.2. SCOPE OF THIS DOCUMENT

This document applies to UA07.2 of Alcatel-Lucent UTRAN.

The new UA07.1 features covered by this document are:

• 34437 iMCTA developments in UA07 (complete)

• 78333 Globalization of feature 34224 IF/IRAT measurement evolution

• 78327 Globalization of feature 34291 support of 64 UMTS neighbours (with limitation due to HCS)

• 33331 Alarm HHO based on UE Tx power

• 34476 SRNS HO (UE not involved) – support on oneBTS

• 34480 3G/2G RRC redirection based on cell load

The new UA07.2 features covered by this document are:

• 81436 Mobility between UMTS and LTE - Cell reselection

• 104489 LTE to UMTS HO

• 81213 - Load balancing between HSPA carriers

• 81204 Dual Cell HSDPA operation

UMTS Radio Mobility



1.3. AUDIENCE FOR THIS DOCUMENT

This is an external document.

1.4. DEFINITIONS AND SPECIFICATION PRINCIPLES

The present document addresses several markets with potentially different behaviours in those markets. The definition of “Global Market” and “USA Market” are:

Global Market: customers other than those part of the following market.

USA Market: customers with UTRAN where Alcatel-Lucent 939X Node B (former Lucent Flexent Node B) is deployed.

For the purpose of the present document, the following notations apply:

[Global Market] This tagging of a word indicates that the word preceding the tag "[Global Market]" applies only to the Global Market. This tagging of a heading indicates that the heading preceding the tag "[Global Market]" and the section following the heading applies only to the Global Market.

[USA Market] This tagging of a word indicates that the word preceding the tag "[USA Market]" applies only to the USA Market. This tagging of a heading indicates that the heading preceding the tag "[USA Market]" and the section following the heading applies only to the USA Market.

[Global Market - …] This tagging indicates that the enclosed text following the "[Global Market - " applies only to the Global Market. Multiple sequential paragraphs applying only to Global Market are enclosed separately to enable insertion of USA Market specific (or common) paragraphs between the Global Market specific paragraphs.

[USA Market - …] This tagging indicates that the enclosed text following the "[USA Market - " applies only to the USA Market. Multiple sequential paragraphs applying only to USA Market are enclosed separately to enable insertion of Global Market specific (or common) paragraphs between the USA Market specific paragraphs.

Text that is not identified via one of the hereabove tags is common to all markets.

Except when specified, all performance management information (counters) are described in [R14], [R15] and [R16] documents.

2. RELATED DOCUMENTS

2.1. APPLICABLE DOCUMENTS

[A1] 25.413 UTRAN Iu interface RANAP signalling

[A2] 25.423 UTRAN Iur interface RNSAP signalling

[A3] 25.433 UTRAN Iub interface NBAP signalling

UMTS Radio Mobility



[A4] 25.331 Radio Resource Control (RRC) Protocol Specification

[A5] 25.304 UE procedures in idle mode and procedures for cell reselection in connected mode

[A6] 44.018 Mobile radio interface layer 3 specification; Radio Resource Control (RRC) protocol

[A7] 25.133 Requirements for support of radio resource management (FDD)

[A8] 23.401 General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access

[A9] 23.272 Circuit Switched Fallback in Evolved Packet System

2.2. REFERENCE DOCUMENTS

[R1] UMT/SYS/DD/000031 Traffic Management

[R2] UMT/SYS/DD/000034 PS Call Management

[R3] UMT/SYS/DD/013000 Mobility Performance Improvements

[R4] UMT/SYS/DD/013319 HSDPA System Specification

[R5] UMT/SYS/DD/013008 Intra-frequency Event Triggered Measurement Reporting Functional Specification

[R6] UMT/SYS/DD/018827 E-DCH System Specification

[R7] UMT/SYS/DD/000128 IRM - Intelligent Rab mapping

[R8] UMT/SYS/DD/18470 SRNS Relocation – UE not involved

[R9] NN-20500-028 Alcatel-Lucent 9300 W-CDMA Product Family – Counter Reference Guide - RNC Counters

[R10] UMT/SYS/DD/000086 UTRAN Power Management

[R11] UMT/SYS/DD/023088 UE dedicated scenarios

[R12] UMT/SYS/DD/023091 Preemption

[R13] UMT/SYS/DD/010042 3G-2G Emergency redirection

[R14] 411-8111-822P1 Observation counters - Volume 1 (RNC Callp)

[R15] 411-8111-822P2 Observation counters - Volume 2 (BTS)

[R16] 411-8111-822P3 Observation counters - Volume 1 (RNC base)

UMTS Radio Mobility



3. DEFINITIONS & CONCEPTS

3.1. NETWORK ARCHITECTURE

The following figure briefly presents the UMTS network elements which are relevant to mobility features.

SGSN

RNC

MSC/VLR

IuCore Network

UTRANRNC

Node BNode BNode BNode BNode B

UE

cells

IurIub

Uu

MSC/VLRE

SGSN

GGSN

Gn

Gn

Gs

External Networks

Packet datanetwork PSTN

HLR

Figure 1: general architecture

The protocol stacks which are used in this document are the following: In UTRAN:

RANAP: specified in 25.413. RANAP is the Radio Access Network Application Part. This protocol specifies radio network layer signalling procedures between RNCs and CN on the Iu interface.

RNSAP: specified in 25.423. RNSAP is the Radio Network Subsystem Application Part. This protocol specifies radio network layer signalling procedures between RNCs in UTRAN on the Iur interface.

NBAP: specified in 25.433. NBAP is the NodeB Application Part. This protocol specifies radio network layer signalling procedures between RNC and Node B on the Iub interface.

RRC: specified in 25.331. RRC is the Radio Resource Control protocol for the UE-UTRAN radio interface. This protocol terminates in the UE and in the Serving RNC. RRC messages are sent over the Iub and Uu interfaces (and possibly the Iur interface)

ALCAP: ALCAP refers to AAL2 Signalling and is specified in ITU-T/Q2630.1. AAL2 is one of the transport layer used in UTRAN, and also between UTRAN and Core Network for CS applications.

In the Core Network:

MAP : specified in 29.002. MAP is the Mobile Application Part. This protocol specifies the signalling procedures between the CS Core Network nodes.

GTP: specified in 29.060. GTP is the GPRS Tunnelling Protocol. This protocol specifies the signalling procedures between the PS Core Network nodes.

UMTS Radio Mobility



3.2. 3GPP BASIC PROCEDURES

This chapter intends to clarify the basic mobility procedures which are applicable to UMTS UTRAN/FDD networks, irrespective of the version to which this document applies. The intention is also to set some vocabulary basis that will be used throughout the document. The mobility cases specified in the following sections are all using those basic procedures, i.e.: • soft handover • hard handover • cell reselection (UE controlled mobility) • SRNS relocation • radio link reconfiguration

3.2.1 SOFT HANDOVER

The soft handover is a procedure allowing the mobile to “do it before break it “ i.e. swapping from one cell to another one without call interruption by opposition to hard handover (i.e. some PDU may be lost). As a matter of fact, the mobile is connected to a set of cells known as the “active set” and takes benefit from macro-diversity. The figure below is an example of soft handover.

Cell 1

UE UE

Call establishment

Cell 2 Cell 1 Cell 2

UE

Cell 2 Cell 3

Intra RNC soft handover Inter RNC soft handover

SRNC SRNC DRNC

Figure 2: Soft handover examples

Regarding network architecture, the soft handover may be either: • intra-NodeB: the cells belong to the same NodeB (In case the NodeB performs recombination between radio

links, this case is called softer handover; refer to § 3.2.2) • inter-NodeB: the cells belong to different NodeB • intra-RNC: the NodeB involved in the active set are all controlled by the same RNC (the controlling RNC) • inter-RNC: the NodeB involved in the active set are controlled by different RNC (requires Iur) Soft handover only applies to dedicated physical channels and E-DCH. Soft handover cannot be applied to shared or common transport channels (e.g. DSCH, FACH...).

3.2.2 SOFTER HANDOVER

In the softer handover case, the macro-diversity radio links belong to the same NodeB.

UMTS Radio Mobility



NodeB

UE

Cell 1 Cell 2

Figure 3: softer handover example

Soft and softer handover may be combined (i.e. used at the same time for a given mobile)

3.2.3 HARD HANDOVER

Hard handover is a category of handover procedures where all the old radio links in the UE are abandoned before the new radio links are established (break it before make it). Hard handover may occur in UTRAN in the following cases: • when using shared channels (DSCH transport channel) or common channels (FACH transport channel) • when the Iur is not present and the UE is changing RNC (i.e. soft handover is not possible) • when the UE is handed over another UTRAN carrier • when the UE is handed over another mode (e.g. TDD) • when the UE is handed over another technology (e.g. GSM) • when soft handover is not permitted (due to O&M constraint) The figure below is an example of hard handover.

UE UE

Before After

Cell 1 Cell 2 Cell 1 Cell 2

Figure 4: hard handover example

Regarding network architecture, the hard handover may be either: • intra-NodeB: the cells belong to the same NodeB • inter-NodeB: the cells belong to different NodeB • intra-RNC: the NodeB involved are all controlled by the same RNC (the controlling RNC) • inter-RNC: the NodeB involved are controlled by different RNC • inter-system: between UTRAN and GSM • inter-PLMN: the NodeB involved are part of different PLMN Hard handover applies to the following RRC states: • CELL_DCH (the mobile is allocated either a dedicated channels (DCH transport channel) or a shared

channels (DSCH transport channel)) • CELL_FACH (the mobile is using common transport channels), as an option from the network

UMTS Radio Mobility



3.2.4 CELL RESELECTION

Cell reselection algorithms are applied by any mobiles in Idle mode (i.e. there is no RRC connection between the UE and the network). Besides, when the mobile is connected to the network (i.e. a RRC connection is present), there are some cases in which the UE mobility follows the rules of "cell reselection" which apply normally when the UE is in Idle mode. In particular, this is true in the following RRC states: • URA_PCH • CELL_PCH • CELL_FACH1 In the cell reselection process, and depending on the information broadcast by the network, the mobile may select a cell from • another frequency • another mode (e.g. TDD) • another system (e.g. GSM, LTE) Regarding network architecture, cell reselection may happen between cells: • from the same RNC or NodeB • from different RNC or NodeB • from different PLMN (in case the Core Network is implementing the "equivalent PLMN" feature).

3.2.5 SRNS RELOCATION

This procedure is used to move the UTRAN anchor point from the serving RNC to another RNC (the UTRAN anchor point is the node in which the mobile-network RRC connection and RLC/MAC radio protocols are terminating). Depending on the network topology, a SRNS relocation may be either intra or inter MSC or SGSN. The figure below is an example of SRNS relocation, from RNC1 to RNC2:

MSC SGSNSGSN MSC

RNC1 RNC2

HLR

MSC SGSNSGSN MSC

RNC1 RNC2

HLR

Before After

RRC

RLC

MAC

RRC

RLC

MAC

Figure 5: SRNS relocation example

SRNS relocation may be used in many cases: • incoming intersystem handover (in this case, the source RNC is actually a 2G-BSC) • outgoing intersystem handover (in this case, the target RNC is actually a 2G-BSC) • UTRAN radio mobility in case Iur is not present, or some Iur needed functions are not supported (this may

also happen in case of handover between 2 PLMN) • UTRAN radio mobility in case Iur is overloaded • SRNS relocation for optimisation of UTRAN Iur routing • SRNS relocation for optimisation of UTRAN parameters

1 Reselection from UTRA cell fach towards E-UTRA idle is not allowed

UMTS Radio Mobility



Depending on the case for which the relocation is used, there may or may not be a change of the physical channels being used for the communication. In any case, the SRNS relocation implies: • a u-RNTI (UTRAN Radio Network Temporary Identity) re-allocation • a reset of the radio protocol layers

3.2.6 RADIO LINK RECONFIGURATION

Refer to [R1] for details.

UMTS Radio Mobility



4. MOBILITY CASES

This chapter describes all the mobility cases applicable for the current version of the document. For all data flows in this chapter, Iub/Iur is on ATM so ALCAP is used to allocate Cid. If Iub/Iur is on IP there is no seperate ALCAP-like message to allocate/release IP transport resources (IP address and UDP ports). The complete list of cases is summarized in the table below:

Section Softer Handover 4.3 Soft Handover, intra-RNC 4.1 Soft Handover, inter-RNC 4.2 Inter-frequency Inter-RNC Handover without Iur (i.e. SRNS UE involved)

4.13

Intra-frequency Inter-RNC Handover without Iur (i.e. SRNS UE involved)

4.14

Hard handover inter-frequency, intra-RNC 4.15 Inter-Frequency Inter-RNC Handover with Iur and measurements 4.16 HSDPA and HSUPA mobility 4.21 SRNS Relocation (“Ue not involved”) 4.17 3G2G Redirection at RRC establishment for speech call 4.18 Emergency and Priority Calls 4.18.3 iMCTA 4.20 Mobility in Cell_PCH and URA_PCH states 4.21 HCS 4.23 3G to 2G handover for PS domain in blind mode 4.7 3G to 2G handover for PS domain with measurements 4.7 3G to 2G handover for CS domain in blind mode 4.10 3G to 2G handover for CS domain with measurements 4.10 2G to 3G handover for CS domain 4.6 2G to 3G handover for PS domain 4.7 2G to 3G handover for CS + PS domain 4.8 3G to 2G handover for both PS and CS domains 4.11 4G to 3G relocation 4.12 3G to 2G cell reselection in Idle mode 4.4 3G to E-UTRAN cell reselection in Idle mode 4.4 3G to 3G cell reselection inter-frequency in Idle mode 4.4 3G to 3G cell reselection intra-frequency in Idle mode 4.4 3G to 2G cell reselection in CELL_FACH mode 4.5 3G to 3G cell reselection inter-frequency in CELL_FACH mode 4.5 3G to 3G cell reselection intra-frequency in CELL_FACH mode 4.5

Table 1:list of mobility cases Since UA05.0, Inter Frequency Hard Handover or Inter System Hard Handover are triggered by the iMCTA function for Alarm, Service or CAC failure re ason (refer to 4.20 section). The following table lists the PMId of the mobility features with the release introduction.

Feature title PMId UTRAN release Section

AT&T Global

Market

2G to 3G for CS domain 13448 UA06.0 UA03.2 4.6 IMSI based HO 21091 UA06.0 UA03.2 5.2

UMTS Radio Mobility



Inter Frequency inter RNC without Iur 17569 UA06.0 UA03.2 4.14 3G to 2G HO for PS & CS simultaneously 21319 UA06.0 UA03.2 4.11 3G2G Redirection for emergency call 25145 UA06.0 UA03.2 4.18.3 Event-Triggered measurements 21135 UA06.0 UA04.0 5.3 Fast Alarm handover triggering 25757 UA06.0 UA04.1 5.9 Composite Neighbour List 21296 UA06.0 UA04.1 6.7 Inter frequency intra RNC handover based on CM 19794 UA06.0 UA04.2 6.4 3G/2G Redirection enhancement for 911 calls 32580 UA06.0 UA04.2 4.18.3 3G/2G Redirection for speech call 13451 UA06.0 UA04.2 4.18 HSDPA step 1 (see note 1) 27932 UA06.0 UA04.2 4.21 Intra-frequency Event-triggered Measurements 27219 UA06.0 UA04.2 5.3 Coexistence of Inter-frequency and 2G Inter-Rat measurements

27597 UA06.0 UA04.2 6.2

HSDPA Alarm mobility 27937 UA06.0 UA04.2 4.21 HSDPA Intra-frequency mobility 27936 UA06.0 UA04.2 4.21 Intra-frequency Hard Handover in case of no Iur 21302 UA06.0 UA04.2 4.14 Intelligent Multi Carrier Traffic Allocation 29415 UA06.0 UA05.0 4.20 HSDPA HO with measurements 29802 UA06.0 UA05.0 4.21 E-DCH step 1 23840 UA06.0 UA05.0 4.21 SRNS Relocation “UE not involved” 18880 (34476) UA07.1 UA05.0 4.17 Dynamic SIB scheduling 30675 UA06.0 UA05.0 5.6 HSDPA over Iur 29817 UA06.0 UA05.0 4.21 Hierarchical Cell Structure (HCS) 29816 NA UA05.0 4.23 URA_PCH 26673 UA06.0 UA05.0 4.21 CELL_PCH 26675 UA06.0 UA05.0 4.21 E-DCH macro diversity support 32076 UA06.0 UA06.0 4.21 Broadcast of SIB4 33819 UA06.0 UA06.0 5.6 Broadcast of SIB12 33820 UA06.0 UA06.0 5.6 Broadcast of SIB19 81436 UA07.1.2 UA07.1.2 5.6 HSUPA over Iur 30744 NA UA06.0 4.21 Intra frequency inter RNC without Iur 33814 NA UA06.0 4.14 Compressed Mode by Higher Layer Scheduling (HLS) 28035 UA06.0 UA06.0 6.4 Immediate handover for emergency call 34151 UA06.0 NA 4.18.3 Service Based Mobility parameters enhancement 33546 UA06.0 UA06.0 5.3 Multi layer developments 33665 NA UA06.0 4.18.3 iMCTA enhancements for WPS 32601 (78332) UA06.0 UA07.0 4.18.3 Support of 64 UMTS neighbours 34291 (78327) UA06.0 UA07.1 6.7 Soft Handover developments 34231 (78326) UA06.0 UA07.0 5.3 2G Inter-RAT handover developments 34230 (78331) UA06.0 UA07.0 4.10 Inter-Frequency Handover developments 34229 (78487) UA06.0 UA07.0 4.16 Inter-Frequency/2G Inter-RAT measurements evolution

34224 (78333) UA06.0 UA07.1 6.2

Defence mechanisms for UE not supporting CM with HSPA

34167 UA06.0 UA06.0 6.4

Compounding Neighbour Cell List developments intra-frequency

33693 UA06.0 UA06.0 6.7

Compounding Neighbour Cell List developments IFREQ/IRAT

34274 UA06.0 UA06.0 6.7

Unified RRM step 2 cell load information exchange between 2G and 3G

33326 NA UA06.0 4.20

Redirection during RRC connection setup 75069 UA07.0 UA07.0 4.18 iMCTA load based HO developments (R3, R4, R9, R11)

34437 UA07.0 UA07.0 4.20

iMCTA load based HO developments (R1, R2, R10) 34437.1 UA07.1 NA 4.20 iMCTA load based HO developments (R5) 34437.2 UA07.1 UA07.1 4.20 Alarm HHO based on UE Tx power 33331 UA07.1 UA07.1 5.9 3G/2G RRC redirection based on cell load 34480 UA07.1 UA07.1 4.18.4

UMTS Radio Mobility



3G to LTE cell reselection in Idle mode 81436 UA07.1.2 UA07.1.2 4.4 3G to LTE cell reselection in Cell/URA PCH mode 81436 UA07.1.2 UA07.1.2 4.5 4G to 3G relocation 104489 UA07.1.2 UA07.1.2 4.12 Load balancing between HSPA carriers 81213 UA07.1.2 UA07.1.2 4.18 Dual Cell HSDPA operation 81204 UA07.1.2 UA07.1.2 4.19

For features introduced in only one type of market in a release, the feature Id of the globalization/above parity feature is given into ( ). Note 1: HSDPA step 1 feature contains HSDPA SHO mobility and traffic segmentation functions.

4.1. SOFT HANDOVER INTRA RNC

4.1.1 DESCRIPTION

In this case, the links which are added/withdrawn from the active set are all managed by the SRNC (i.e. the RNC in charge of the RRC connection with the mobile). Radio link recombination is performed at the SRNC level. For further details on this process, please refer to the "DHO management" section in the Common procedures chapter.

SRNC

NodeB 1

UE

Iub

New radio linkto be added

NodeB 2

Iu

Figure 6: soft handover overview

In this case, there is already a macro-diversity link supported by the Serving RNC (NodeB1). A new link from NodeB2 is added:

UE NodeB 2 Serving RNC

RRC/ active set update

RRC/ active set update complete

NBAP/ Radio Link setup req

NBAP/ Radio Link setup resp

RRC/ Measurement Report

1

2

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)

Figure 7: Radio Link addition

(1) based on active set evaluation process result, a new branch is added using the NodeB 2. This implies a new

radio link to be setup with the NodeB 2, and the associated AAL2 Cid(s) to be allocated. The Node B shall only consider a transport bearer synchronised after it has received at least one DL DATA FRAME on this transport bearer before LTOA (Latest Time of Arrival).

(2) once new resources are created, the mobile active set is updated with the new radio link

UMTS Radio Mobility



The next dataflow is an example of radio link removal.

UE NodeB Serving RNC



NBAP/ Radio Link deletion req

NBAP/ Radio Link deletion resp 2

1

RRC/ Measurement Report (event 1B)

Figure 8: Radio Link deletion

(1) based on active set evaluation process result, the SRNC decides to remove a radio link from the active set.

The mobile active set is updated with the new configuration. (2) the link is deleted at the NodeB, and the AAL2 Cid(s) are released. For details on the active set evaluation process, please refer to the [Active Set Evaluation] section in the Common Procedures chapter

4.1.2 APPLICABILITY

The soft handover applies only on dedicated physical resources. In this version, the active set evaluation (i.e. Decision to add/drop links) is based on the same algorithm and parameters (with possibly different values) for PS and CS calls. Therefore, soft & softer handover is a network default behaviour which applies to all PS & CS calls whatever is the user data rate. Soft & softer handover do not apply to HS-DSCH calls. Besides, it is possible to limit the number of soft handover legs being used by setting the relevant parameter to the needed value. For more details, please refer to the [Active Set Evaluation] section in the Common Procedures chapter. If the Active Set Update procedure fails, the call is kept with the previous active set cells.

4.1.3 PARAMETERS

Refer to the [Active Set Evaluation] section in the [Common Procedures] chapter.

4.1.4 ACCESS NETWORK IMPACTS

• Measurement processing and decision algorithm for active set updating • Support of relevant procedures on the Iub interface and RRC protocol. • Support of User plane combining and splitting

4.1.5 CORE NETWORK IMPACTS

None. (CN is completely transparent to this procedure).

UMTS Radio Mobility



4.2. SOFT HANDOVER INTER RNC

4.2.1 DESCRIPTION

In this case, the links which are added/withdrawn from the active set are not all controlled by the SRNC. In such a case two RNC’s are involved with each a different role: • the SRNC (Serving RNC): which is the RNC in charge of the RRC connection with the mobile • the DRNC (Drift RNC): which is the RNC which controls the NodeB having a radio link in the active set.

This DRNC acts as a router from the RNC and the UTRAN transport point of view (e.g. in this version there are as many dedicated links on the Iur as radio links which are controlled by the DRNC).

The fact that there is a DRNC in the communication path rather than only one unique SRNC is completely hidden to the mobile and the Core Network. For further details on the Radio link recombination process, please refer to the "DHO management" section in the Common procedures chapter.

DRNC

Iur

SRNC

UE

Iub

New radio link to be added

NodeB 1 NodeB 2 NodeB 0

Iu

Figure 9: soft handover over Iur

In this case, there is already a macro-diversity link supported by the NodeB0 (controlled by the SRNC) and the NodeB1 (controlled by the Drift RNC). A new link from NodeB2 is added:

UMTS Radio Mobility



Serving RNCUE Drift NodeB2 Drift RNC



RNSAP/ Radio Link addition req

RNSAP/ Radio Link addition resp (Binding Id)




1

2

AAL2/ ERQ

AAL2/ ECF

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)

AAL2/ ERQ

AAL2/ ECF

New AAL2 connections are setup for boththe DCCH and the DTCH

Figure 10: Radio Link addition over Iur

(1) Based on active set evaluation result, a new branch is added using the NodeB2. A new radio link is setup with the NodeB 2, the associated AAL2 Cid(s) are allocated on the Iub and Iur. On the Iur, 2 separate Cid are used on the Iur for both DCCH and DTCH. Since there is already a macro-diversity link controlled by the DRNC for that communication, • there is no need to build a SCCP connection between the SRNC and the DRNC (this has already been done

when the Radio Link towards NodeB 1 has been setup) • the SRNC is using the "Radio Link Addition" rather than "Radio Link Setup" RNSAP procedure. In the RADIO LINK ADDITION RESPONSE message, the Drift RNC provides to the SRNC the list of neighbouring cells. This information is used by the SRNC to update the list of cells to be measured by the UE. (2) Once new resources are created, the mobile active set is updated with the new radio link The next dataflow is an example of radio link removal.

UMTS Radio Mobility



Serving RNC UE Drift NodeB Drift RNC



RNSAP/ Radio Link deletion req

RNSAP/ Radio Link deletion resp


NBAP/ Radio Link deletion resp

AAL2/ REL

AAL2/ RLC

2

1

SCCP/ Released

AAL2/ REL

AAL2/ RLC


SCCP/ Release Complete

Figure 11: Radio Link deletion over Iur

(1) based on active set evaluation result, the SRNC decides to remove a radio link from the active set. The

mobile active set is updated with the new configuration. (2) the link is deleted at the NodeB, the Iub AAL2 Cid the 2 Iur AAL2 Cid are released. The SCCP released

message is sent if the radio link which is removed is the last one supported by the DRNC for this mobile. For details on the active set evaluation process, please refer to the [Active Set Evaluation] section in the Common procedures chapter

4.2.2 APPLICABILITY

The soft handover inter-RNC requires the presence of an Iur between the involved RNCs. For other applicability considerations, please refer to [Soft Handover intra-RNC].

4.2.3 PARAMETERS



All impacts which come from the "soft handover intra RNC", plus: • support of dedicated channel on Iur and associated RNSAP procedures.



UMTS Radio Mobility



4.3. SOFTER HANDOVER

4.3.1 DESCRIPTION

In this case, the links which are added/withdrawn from the active set are all controlled by a NodeB already supporting a radio link towards the mobile, as in the following figure:

SRNC

NodeB

UE

Iub

New radio linkto be added

Iu

Figure 12: softer handover overview

The corresponding dataflow is as follows:




NBAP/ Radio Link Addition req

NBAP/ Radio Link Addition resp


1

2

Figure 13: Radio Link addition for softer handover

(1) based on active set evaluation result, a new branch is added using the NodeB. There is no new AAL2 Cid to be allocated since the recombination between the 2 radio links is performed at the NodeB. When the Radio Link Addition Response is sent, the NodeB start UL reception and DL transmission on the new radio link. (2) once new resources are created, the mobile active set is updated with the new radio link For further details on the active set evaluation process, please refer to [Active Set Evaluation] section in the Common procedures chapter For further details on the Radio link recombination process, please refer to the [DHO management] section in the Common procedures chapter. A new UA06.0 feature can be activated and enables Node B to support the softer handover with 3 sectors amongst any of the 6 sectors on the same frequency, i.e. without cluster limitation.

4.3.2 APPLICABILITY

Please refer to § 4.1

UMTS Radio Mobility



4.3.3 PARAMETERS


Name Object/Class Definition

is6SectorsNodeb RadioAccessService Class3

Flag for 6 sectors softer HO feature activation


• Support of relevant Iub procedures



4.4. CELL RESELECTION IN “IDLE MODE”

4.4.1 DESCRIPTION

This paragraph covers the following mobility cases: • "3G to 3G cell reselection intra-frequency in Idle mode" which allows a UMTS mobile camping on a 3G

cell to reselect a cell using the same technology and frequency • "3G to 3G cell reselection inter-frequency in Idle mode", i.e. with 3G cells using different frequencies • "3G to 2G cell reselection in Idle mode" which allows a "GSM capable" UMTS mobile to reselect a GSM

cell when being in idle mode in the UMTS coverage. • “3G to LTE cell reselection in Idle mode” which allows a “LTE capable” UMTS mobile to reselect a LTE

cell when being in idle mode in the UMTS coverage. • only UTRAN/FDD, LTE Radio Access Technologies and GSM Radio Access Technologies are known

and supported • HCS (Hierarchical Cell Structure) in Idle mode is supported (Please refer to section 4.23; present

chapter describes behaviour when HCS is not used) • High mobility detection is supported

4.4.2 APPLICABILITY

This feature is applicable to any multimode (for the intersystem reselection) mobile or UTRAN/FDD mobile (for the 3G only reselection) being Idle under UMTS coverage.

4.4.3 ALGORITHM

As specified in 25.304, there are 2 algorithms defined for cell reselection: algorithm when absolute priority is not used for cell reselection defines • a criteria for GSM or UTRAN/FDD neighbouring cells tracking and measurement • a criteria S to assess GSM and FDD cells eligibility • a criteria R for ranking of eligible cells -algorithm when absolute priority is used for cell reselection defines • a prioriy for UTRAN frequency and a priority for a E-UTRAN frequency

UMTS Radio Mobility



• a criteria S for E-UTRAN neighbouring cells eligibility • several criterion for ranking of eligible cells The UE will process the following cell reselection process:

• inter frequency cell reselection 2G inter rat cell reselection based on the legacy algorithm; • LTE inter rat cell reselection based on the new algorithm using absolute priorities

4.4.3.1 NEIGHBOURING CELLS MEASUREMENT RULES

In order to limit the time during which the mobile performs measurements on UTRAN/FDD neighbouring cells, 25.304 specifies the following algorithm for the mobile in Idle mode: • If Squal > Sintrasearch, UE need not perform intra-frequency measurements. • If Squal <= Sintrasearch, perform intra-frequency measurements. • If Sintrasearch, is not sent for serving cell, perform intra-frequency measurements The same algorithm has been defined in 25.304 for intersystem cell reselection: • If Squal > SsearchRAT m, and (Srxlev > SHCS,RATm if SHCS,RATm is signaled) UE need not perform

measurements on cells of RAT "m". • If Squal <= SsearchRAT m, or (Srxlev <= SHCS,RATm if SHCS,RATm is signaled) perform measurements on cells of

RAT "m". • If SsearchRAT m, is not sent for serving cell, perform measurements on cells of RAT "m" The same algorithm has been defined in 25.304 for inter-frequency cell reselection: • If Squal > Sintersearch, and MBMS PL has not been indicated, and (Srxlev > SsearchHCS if SsearchHCS is signaled)

UE need not perform inter-frequency measurements • If Squal > Sintersearch, or (Srxlev <= SsearchHCS if SsearchHCS is signaled) perform inter-frequency measurements • If Squal <= Sintersearch, perform inter-frequency measurements. • If Sintersearch, is not sent for serving cell, perform inter-frequency measurements. NOTE 1: If HCS is not used and if Slimit,SearchRATm is sent for serving cell, UE shall ignore it. NOTE 2: The presence of SsearchHCS and SHCS,RATm thresholds in system information are used to avoid introducing new parameters to system information and their presence does not imply that HCS is used. The change is that the RxLev (i.e. RSCP) of the serving cell below a RSCP based threshold may also trigger UE measurements (R5 mobiles) and on another frequency or another RAT.

4.4.3.2 NEIGHBOURING CELLS MEASUREMENT RULES WHEN U SING ABSOLUTE PRIORITY

As specified in 25.304, when the mobile has received absolute priority information for inter-RAT layers, The UE shall perform measurements of inter-RAT layers with a priority higher than the priority of the current serving cell.

For inter-RAT layers with a priority lower than the priority of the current serving cell:

UMTS Radio Mobility



If SrxlevServingCell > Sprioritysearch1 and SqualServingCell > Sprioritysearch2 the UE may choose not to perform measurements of inter-RAT layers of lower priority

If SrxlevServingCell <= Sprioritysearch1 or SqualServingCell <= Sprioritysearch2 the UE shall perform measurements of inter-RAT layers of lower priority

4.4.3.3 CRITERIA S

25.304 defines the FDD cell selection criteria S as being For FDD cells: Srxlev > 0 AND Squal > 0 For GSM cells: Srxlev > 0 For E-UTRAN cells: Srxlev > 0 Where: Squal = Qqualmeas – Qqualmin Srxlev = Qrxlevmeas - Qrxlevmin - Pcompensation with: Squal Cell Selection quality value (dB) Srxlev Cell Selection RX level value (dB) Qqualmeas Measured cell quality value. The quality of the received signal expressed in

CPICH Ec/N0 (dB) Qrxlevmeas Measured cell RX level value. This is received signal, CPICH RSCP for FDD

cells (dBm) Qqualmin Minimum required quality level in the cell (dB) Qrxlevmin Minimum required RX level in the cell (dBm) Pcompensation max(UE_TXPWR_MAX_RACH – P_MAX, 0) (dB) UE_TXPWR_MAX_RACH Maximum TX power level an UE may use when accessing the cell on RACH

(read in system information) (dBm) P_MAX Maximum RF output power of the UE (dBm) Any cell (serving and any GSM or UTRAN/FDD neighbouring cells) which fulfill these criteria will be part of the list for ranking.

UMTS Radio Mobility



4.4.3.4 CELL RANKING CRITERIA

The following cell re-selection criteria are used for intra-frequency cells, inter-frequency cells if no absolute priority information for any inter-frequency layer is available to the UE, and inter-RAT cells if no absolute priority information for any inter-RAT layer is available to the UE for that RAT. All the neighbouring cells being eligible (S criteria) are ranked accordingly to the R criteria, as defined below:

Rs = Qmeas,s + Qhysts ; for the serving cell Rn = Qmeas,n - Qoffsets,n ; for any GSM or UTRAN/FDD neighbouring cell

(There is no "Temporary Offset" in the above criteria when HCS is not used). with

Qmeas Quality value. The quality value of the received signal derived from the averaged CPICH Ec/No or CPICH RSCP for FDD cells and from the averaged received signal level for GSM cells. For FDD cells, the measurement that is used to derive the quality value is set by the Cell_selection_and_reselection_quality_measure information element.

Qoffset1 This specifies the offset between the two cells (Qoffset). It is used for GSM cells and for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH RSCP.

Qoffset2 This specifies the offset between the two cells (Qoffset). It is used for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH Ec/No.

Qhyst1 This specifies the hysteresis value (Qhyst). It is used for GSM cells and for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH RSCP.

Qhyst2 This specifies the hysteresis value (Qhyst). It is used for FDD cells if the quality measure for cell selection and re-selection is set to CPICH Ec/No.

4.4.3.5 CELL RANKING CRITERIA WHEN USING ABSOLUTE P RIORITY

All the neighbouring cells being eligible (S criteria) are ranked accordingly to the following criteria: Criterion 1: the SrxlevnonServingCell,x of a cell on an evaluated higher absolute priority layer is greater than Threshx,high during a time interval Treselection

Criterion 2: SrxlevServingCell < Threshserving,low or SqualServingCell < 0 and the SrxlevnonServingCell,x of a inter-frequency cell on an evaluated equal absolute priority layer is greater than Threshx,low during a time interval Treselection

Criterion 3: SrxlevServingCell < Threshserving,low or SqualServingCell < 0 and the SrxlevnonServingCell,x of a cell on an evaluated lower absolute priority layer is greater than Threshx,low during a time interval Treselection

4.4.3.6 OVERALL CELL RESELECTION PROCESS

Among the GSM and FDD cells which verifies the S criteria, the mobile shall perform ranking according to the R criteria specified above. In this first step, the offset Qoffset1s,n is used for Qoffsets,n to calculate Rn, the hysteresis Qhyst1s is used for Qhysts to calculate Rs. Then the following selection process applies: • If a GSM cell is ranked as the best cell, then the UE shall perform cell re-selection to that GSM cell. • If an FDD cell is ranked as the best cell and the quality measure for cell selection and re-selection is set to

CPICH RSCP, the UE shall perform cell re-selection to that FDD cell. • If an FDD cell is ranked as the best cell and the quality measure for cell selection and re-selection is set to

CPICH Ec/No, the UE shall perform a second ranking of the FDD cells according to the R criteria specified

UMTS Radio Mobility



above, but using the measurement quantity CPICH Ec/No for deriving the Qmeas,n and Qmeas,s and calculating the R values of the FDD cells. The offset Qoffset2s,n is used for Qoffsets,n to calculate Rn, the hysteresis Qhyst2s is used for Qhysts to calculate Rs. Following this second ranking, the UE shall perform cell re-selection to the best ranked FDD cell.

In all cases, the UE shall reselect the new cell, only if the cell reselection criteria are fulfilled during a time interval Treselection. Since R5 release (if the following scaling parameters are sent in SIB3), the UE shall apply the scaling rules:

� Intra frequency cells: If High mobility is detected, Treselection value is multiplied by the speed dependent scaling factor for Treselection value (=speedDependScalingFactorTReselection OAM parameter) which is lower than 1;

� Inter frequency cells: Treselection value is multiplied by the inter-frequencyScaling factor for treselection value (=interFreqScalingFactorTReselection OAM parameter) which is greater than 1. If the mobile is in High-mobility state it is also multiplied by the speed dependent scaling factor for Treselection value;

� Inter Rat cells: Treselection value is multiplied by the inter-rat scaling factor for treselection value (=interFreqScalingFactorTReselection OAM parameter) which is greater than 1. If the mobile is in High-mobility state it is also multiplied by the speed dependent scaling factor for Treselection value.

These parameters gives a mean to have shorter Treselection for fast moving UEs and also to have longer Treselection towards inter-frequency or inter-RAT neighbor cells (i.e. operator’s policy is to keep UE cell reselection in the current frequency). High mobility detection (if HCS not used) If the number of cell reselections during period non-TCRmax exceeds non-NCR, high-mobility has been detected. When the number of cell reselection during time period non-TCrmaxHyst no longer exceeds non-NCR, UE shall:

� Continue these measurement during non-TCrmaxHyst; � If the criteria for entering high mobility is not detected during time period non-TCrmaxHyst: Exit high-

mobility. The high mobility state doesn’t mean the mobile speed is high but the number of reselection is high.

4.4.3.7 OVERALL CELL RESELECTION PROCESS WHEN USING ABSOLUTE PRIORITY

Cell reselection to a cell on a higher absolute priority layer than the camped frequency shall be performed if criterion 1 is fulfilled. Cell reselection to an inter-frequency cell on an equal absolute priority layer to the camped frequency shall be performed if criterion 2 is fulfilled. Cell reselection to a cell on a lower absolute priority layer than the camped frequency shall be performed if criterion 3 is fulfilled. If more than one cell meets the above criteria, the UE shall reselect the cell with the highest SrxlevnonServingCell,x among the cells meeting the criteria on the highest absolute priority layer.

The UE shall not perform cell reselection until more than 1 second has elapsed since the UE camped on the current serving cell.

For UE in RRC connected mode states CELL_PCH or URA_PCH the interval Treselections,PCH applies, if provided in SIB4 , while for UE in RRC connected mode state CELL_FACH the interval Treselections,FACH applies, if provided in SIB4.

UMTS Radio Mobility



In all the above criteria the values of Treselections, Treselections,PCH or Treselections,FACH apply for Treselection and are scaled according to the UE mobility state and target RAT

4.4.4 PARAMETERS

This paragraph lists all the parameters needed when HCS is not used and displayed to the operator at the OMC-R. All those parameters are broadcast on the BCCH using either • SIB3 for cell reselection parameters related to the serving cell; • SIB11 for cell reselection parameters related to neighbouring cells; • SIB19 for LTE cell reselection.

4.4.4.1 AT UTRAN/FDD CELL LEVEL

Information Element SIB Object description/comment qualMeas 3&11 CellSelectionInfo Choice of measurement (CPICH Ec/No or CPICH

RSCP) to use as quality measure for Fdd cell.

sIntraSearch 3 CellSelectionInfo Integer (-32..20 by step of 2) In [dB]

sSearchRatGsm 3 CellSelectionInfo Integer (-32..20 by step of 2) In [dB]

sInterSearch 3 CellSelectionInfo Integer (-32..20 by step of 2) In [dB]

qQualMin 3 CellSelectionInfo Integer (-24..0) Ec/N0, In [dB]

qRxLevMin 3 CellSelectionInfo Integer (-115..-25 by step of 2) RSCP, In [dBm] As of UA04.2 Integer (-58..-13 by step of 2)

qHyst1 3 CellSelectionInfo Integer (0..40 by step of 2) In [dB]

qHyst2 3 CellSelectionInfo Integer (0..40 by step of 2) In [dB]

tReselection 3 CellSelectionInfo Integer (0..31) In [s]

sibMaxAllowedUlTxPowerOnRach

3 PowerConfClass From -50 to 33 In [dBm]

sSearchHcs 3 CellSelectionInfo Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the limit for Srxlev in the serving cell below which the UE shall initiate measurements of all neighbouring cells of the serving cell. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-frequency neighbouring cells of the serving cell.

sHcsRatGsm 3 CellSelectionInfo Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the RAT specific threshold in the serving cell used in the inter-RAT measurement rules. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-RAT neighbouring cells of the serving cell.

speedDependScalingFactorTReselection

3 CellSelectionInfo Real (0..1 by step of 0.1). This specifies the scaling (multiplication) factor to be used by the UE in idle mode or RRC connected mode states for the parameters Treselection

in case high-mobility state has been detected. interFreqScalingFactorTReselection

3 CellSelectionInfo Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-frequency case.

interRatScalingFactorTReselection

3 CellSelectionInfo Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the

UMTS Radio Mobility



parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-RAT case.

tCrMax 3 CellSelectionInfo Enumerated (not used, 30, 60, 120, 180, 240). This specifies the duration for evaluating allowed amount of cell reselection(s). This parameter is mapped to non-TCRmax or TCRmax IE for SIB3 filling depending of HCS use or not.

nCR 3 CellSelectionInfo Integer (1..16). This specifies the maximum number of cell reselections. This parameter is mapped to non-NCR or NCR IE for SIB3 filling depending of HCS use or not.

tCrMaxHyst 3 CellSelectionInfo Enumerated (not used, 10, 20, 30, 40, 50, 60, 70). This specifies the additional time period before the UE can exit high-mobility. This parameter is mapped to non-TCrmaxHyst

or TCrmaxHyst IE for SIB3 filling depending of HCS use or not.

UMTS Radio Mobility



utraServingCellPriority UA07.1.2: FddCell.reserved4(byte0) bit 0-2

19 FDDCell in UA7.1.2 CellSelectionInfoWithPriority in UA8

Integer (0..7). Absolute priority of the serving Fdd cell

utraSPrioritySearch1 UA07.1.2: FddCell.reserved4(byte1) bit 0-5


Integer (0..62) by step of 2. Srxlev of the UTRA cell used for neighboring measurement triggering

utraSPrioritySearch2 UA07.1.2: FddCell.reserved4(byte2) bit 0-5


Integer (0..7) by step of 1. Srxlev of the UTRA cell used for neighboring measurement triggering

utranThreshSLow UA07.1.2: FddCell.reserved4(byte3) bit 0-5


Integer (0..62) by step of 2. RSCP threshold Low of the UTRA cell used by the UE reselection process

eUtraTargetDlCarrierFrequencyArfcn UA07.1.2: First instance FddCell.reserved5 (byte0 and 1) Second instance FddCell.reserved6 (byte0 and 1)

19 FDDCell in UA7.1.2 EUtranFrequencyAndPriorityInfoList in UA8

Integer (0..65535). E-UTRA frequencies to be used in cell reselection procedure

measurementBandwidth UA07.1.2: First instance FddCell.reserved5 (byte2) bit 0-2 Second instance FddCell.reserved6 (byte2) bit 0-2


Enumerated (6,15,25,50,75,100). Measurement bandwidth information used by SIB19 and common for all neighbouring cells on the carrier frequency

eUtraTargetFrequencyPriority UA07.1.2: First instance FddCell.reserved5 (byte2) bit 3-5 Second instance FddCell.reserved6 (byte2) bit 3-5


Byte (0..7). Priority of a E-UTRA frequency

eUtraTargetFrequencyDetection UA07.1.2: First instance FddCell.reserved5 (byte2) bit 6 Second instance FddCell.reserved6 (byte2) bit 6


Boolean. ‘TRUE’ means that the UE may detect the presence of a E-UTRA cell and report to NAS

eUtraTargetFrequencyQrxLevMin UA07.1.2: First instance FddCell.reserved5 (byte3) bit 0-5


Integer (-140..-44) by step of 2; Qrxlevmin (RSRQ) of the E-UTRA cell used for S criteria of the reselection process.

UMTS Radio Mobility



Second instance FddCell.reserved6 (byte3) bit 0-5 eUtraTargetFrequencyThreshxLow UA07.1.2: First instance FddCell.reserved7 (byte0) bit 0-5 Second instance FddCell.reserved7 (byte2) bit 0-5


Integer (0..62) by step of 2; RxLev (RSRP) Threshold Low of the E-UTRA cell used by the UE reselection process

eUtraTargetFrequencyThreshxHigh UA07.1.2: First instance FddCell.reserved7 (byte1) bit 0-5 Second instance FddCell.reserved7 (byte3) bit 0-5


Integer (0..62) by step of 2; RxLev (RSRP) Threshold High of the E-UTRA cell used by the UE reselection process

4.4.4.2 AT UTRAN/FDD NEIGHBOURING CELL LEVEL

Information Element SIB Object description/comment

maxAllowedUlTxPower 11 UmtsNeighbouringRelation From -50 to 33 In [dBm]

primaryScramblingCode 11 FDDCell (neighbouring) Integer(0..511) ulFrequencyNumber 11 FDDCell (neighbouring) This parameters equals ( 5 * FreqDL MHz ) dlFrequencyNumber 11 FDDCell (neighbouring) This parameters equals ( 5 * FreqDL MHz ) neighbouringCellOffset 11 UmtsNeighbouringRelation Integer(-10..10)

In [dB] qOffset1sn 11 UmtsNeighbouringRelation Integer(-50..50)

In [dB] qOffset2sn 11 UmtsNeighbouringRelation Integer(-50..50)

In [dB] qQualMin 11 UmtsNeighbouringRelation Integer (-24..0)

Ec/N0, In [dB] qRxLevMin 11 UmtsNeighbouringRelation Integer (-115..-25 by step of 2)

RSCP, In [dBm]

UMTS Radio Mobility



4.4.4.3 AT GSM NEIGHBOURING CELL LEVEL

Information Element SIB Object description/comment maxAllowedUlTxPower 11 GSMCell From -50 to 33

In [dBm] Ncc 11 GSMCell bit string(3) Network Color Code. Part of the BSIC Bcc 11 GSMCell bit string(3) Base Station Color Code. Part of the BSIC GSMbandIndicator 11 GSMCell DCS 1800 band used,

PCS 1900 band used bcchFrequency 11 GSMCell Integer (0..1023) GSM ARFCN gsmCellIndivOffset 11 GSMCell Integer(-10..10)

In [dB] qOffset1sn 11 GsmNeighbouring

Cell Integer(-50..50) In [dB]

qRxLevMin 11 GsmNeighbouringCell

Integer (-115..-25 by step of 2) In [dBm]


• Ability to broadcast the necessary parameters on the radio interface BCCH.


• Support of location registration update from a 3G to a 2G cell, for a PS or CS attached mobile.

4.5. CELL RESELECTION IN “CELL FACH AND CELL/URA PC H MODE”

4.5.1 DESCRIPTION

When in CELL_FACH, CELL PCH or URA PCH mode, although the mobile is connected to the network (there exist a RRC connection) the UE mobility is controlled by "cell re-selection rules" as in Idle mode. This paragraph covers the following mobility cases: • "3G to 3G cell reselection intra-frequency in CELL_FACH or CELL/URA PCH mode" • "3G to 3G cell reselection inter-frequency in CELL_FACH or CELL/URA PCH mode" • "3G to 2G cell reselection in CELL_FACH or CELL/URA PCH mode" • “3G to E-UTRAN cell reselection in CELL/URA PCH mode” HCS (Hierarchical Cell Structure) in Fach mode is supported (Please refer to section 4.23; present chapter describes behaviour when HCS is not used)

4.5.1.1 INTRA-RNC CASE

In this case, the UE is reselecting a new cell being also controlled by the SRNC, as in the figure below (please note that the old and the new cells may also be controlled by the same NodeB).

UMTS Radio Mobility



SRNC

NodeB 1

UE

Iub

FACH 1

NodeB 2

Iu

FACH 2

Before After UE

Figure 14: Intra-RNC cell re-selection in CELL_FACH

The next dataflow is an example of intra-RNC cell re-selection in CELL_FACH.

Serving RNC SGSN NodeB 1, 2 UE

RRC/ RACH / Cell Update (cause "cell reselection")

RRC/ FACH / Cell Update Confirm (RRC state = CELL_FACH,CN Information (PLMN Id, LAI, RAI), c-RNTI)

If the mobile enters a new Location Area or Routing Area:

GMM/ RACH / Routing Area Update Request

GMM/ RACH / Routing Area Update Accept

RRC/ RACH / UTRAN Mobility Information Confirm

Figure 15: Intra-RNC cell re-selection in CELL_FACH dataflow

Having re-selected the new cell, the UE generates a CELL UPDATE to the SRNC, so that the SRNC keeps the current cell updated for paging. In case the CELL UPDATE CONFIRM message either includes "CN information elements" or "Ciphering mode info" or "Integrity protection mode info" or "New C-RNTI" or "New U-RNTI", a UTRAN MOBILITY INFORMATION CONFIRM message is then answered by the mobile. In Alcatel-Lucent implementation, the CELL UPDATE CONFIRM will always contain a new-CRNTI.

4.5.1.2 INTER-RNC CASE

In this case, the UE is reselecting a new cell being controlled by an RNC different from the SRNC. As in the figure below, this RNC may possibly depend from another SGSN.

UMTS Radio Mobility



RNC 2 RNC 1

UE

Iub

Before

SGSN 2 SGSN 1

GGSN

UE

After

Iub

FACH 1 FACH 2

Iur

NodeB 2 NodeB 1

Figure 16: Inter-RNC cell re-selection in CELL_FACH

The next dataflow is an example of inter-RNC cell re-selection in CELL_FACH. In this version, UTRAN does not support common channel over Iur. The complete service re-establishment is therefore divided into 3 parts:

• The initial RRC access • The RAU phase (if needed) • The service re-establishment phase

SGSN 1 SGSN 2 Alcatel-Lucent

Serving RNC1

Alcatel-Lucent Drift

RNC2 UE

RRC/ RACH / Cell Update (U-RNTI, cause “cell reselection”)

RRC/ FACH / RRC Connection Release (U-RNTI, cause “DSCR”)

Based on the u-RNTI analysis, the new RNC (RNC2) detects that the UE is actually connected to another SRNC. The RNC2 rejects the cell update using the RRC connection release procedure, forcing the mobile to Idle mode.

Figure 17: Initial RRC access, first steps when the Drift RNC2 is Alcatel-Lucent

UMTS Radio Mobility



SGSN 1 SGSN 2

Alcatel-Lucent Serving RNC1

NonAlcatel-Lucent Drift

RNC2 UE

RRC/ RACH / Cell Update (U-RNTI, cause “cell reselection”)

RRC/ FACH / RRC Connection Release (U-RNTI, cause “U-RNTI, cause “directed signaling connection re-establishment”)

RRC message received from UE containing U-RNTI ID as addressing information. The procedure is used by the drift RNC2 to forward to the Serving RNC1 the RRC Cell Update message received on the RACH.

RNSAP/ UPLINK SIGNALLING TRANSFER INDICATION / Cell Update is forwarded to the SRNC

RNSAP/ DOWNLINK SIGNALLING TRANSFER REQUEST / RRC Connection Release (U-RNTI, cause “directed signaling connection re-establishment”)

The SRNC received the cell update and starts an RRC connection release procedure, forcing the mobile to idle mode. The Serving RNC1 uses the Downlink Signalling Transfer procedure to request from the non Alcatel-Lucent Drift RNC2 the transfer of a RRC Connection Release message on the FACH. This procedure is in response to the received Uplink Signalling Transfer procedure.

Figure 18: Initial RRC access, first steps when the Drift RNC2 is not Alcatel-Lucent

SGSN 1 SGSN 2 RNC 1 RNC 2 UE

RRC/ RACH / RRC Connection Request (cause « re-establishment »)

When it enters Idle mode, the UE requests for a RAU, which will be followed by a "service request" (follow-on request pending) used for re-establishing UTRAN resources corresponding to the PS services which were supported by RNC 1.

RRC/ FACH / RRC Connection Setup (DCCH, U-RNTI, RRC state = CELL_FACH)

RRC/ RACH / RRC Connection Setup Complete

RRC/ RACH / Initial Direct Transfer (Routing Area Update Request, Follow-on request pending, PS domain)

SCCP/ Connection Request (Initial UE msg (Routing Area Update Request))

SCCP/ Connection Confirm

Figure 19: Initial RRC access

UMTS Radio Mobility



GTP/ SGSN ctx request


GTP/ SGSN ctx response

GTP/ SGSN ctx ack

RANAP/ SRNS ctx request

RANAP/ SRNS ctx response

RANAP/ Iu release command

RANAP/ Iu release complete

GMM/ Authentication and Ciphering Request

GMM/ Authentication and Ciphering Response

GMM / Routing Area Update Accept (P_TMSI)

GMM/ Routing Area Update Complete

RANAP/ Security Mode Command (UIAx, UEAy)

RANAP/ Security Mode Complete

RRC/ Security Mode Command

RRC/ Security Mode Complete

The active PDP context(s) are retrieved from the old to the new SGSN, and security procedures are activated by the new SGSN.

The connection with the old RNC is eventually released once the RAU procedure is completed in the new SGSN.

Once security is in place, the GGSN and the HLR are updated with the new UE status and location

Figure 20: The Routing Area Update phase


GMM/ Service Request (Data)

RANAP/ RAB Assignment Request

RANAP/ RAB Assignment Response

The SGSN requests the UTRAN for RAB allocation, corresponding to the active PDP context being re-activated by the UE. In this example, the new RAB is setup in CELL_FACH state.

RRC/ FACH / RB Setup (DTCH, RRC state)

RRC/ RACH / RB Setup Complete

GMM/ Service Accept

In the target RNC, the new RAB is setup in CELL_FACH state, as for a PS call establishment. Further on, based on Always-On algorithm and user traffic volume, the mobile is possibly moved to the CELL_FACH state.

Figure 21: The service re-establishment phase

4.5.1.3 3G TO 2G CASE

This mobility case is similar to the inter-RNC mobility case: • at some point, the mobile in PS active mode will reselect a GSM cell • the mobile will perform a RA update in its new GSM cell

UMTS Radio Mobility



• this will imply a SGSN context transfer between the old and new SGSN • at the end all user-related resources will be cleared in UTRAN through Iu Release Request from the old

SGSN

4.5.1.4 2G TO 3G CASE

From the UTRAN point of view, this case is equivalent to a “Routing Area Update” procedure followed by a PS call setup (possibly linked together using the “follow-on request” facility in the GMM RAU procedure).

4.5.1.5 3G TO E-UTRAN CASE

This mobility case is similar to the inter-RNC mobility case: • at some point, the mobile in PS active mode will reselect a E-UTRAN cell • the mobile will perform a Tracking Area Update in its new E-UTRAN cell • this will imply a SGSN context transfer between the old and new SGSN • at the end all user-related resources will be cleared in UTRAN through Iu Release Request from the old

SGSN

4.5.1.6 DUAL CELL HSDPA CASE

In multi-layer networks with some layers supporting DC transmission and others not, it would be preferable for DC capable UEs to camp on DC capable layers. Unfortunately, 3GPP has not defined any mechanisms to force cell reselection based on DC capability. Therefore, no specific cell reselection handling or specific SI broadcast is available for DC feature. If a DC UE attempts call establishment on a cell that is not DC capable, then Redirection onto another DC layer may be performed during RRC establishment or the call can get handed over to a DC layer after call establishment. In the current release neither iMCRA nor iMCTA ensure redirection or handover to a DC capable cell.

4.5.2 APPLICABILITY

This feature is applicable to any multimode (for the intersystem reselection) mobile or UTRAN/FDD mobile (for the 3G only reselection) being in CELL_FACH mode under UMTS coverage.

4.5.3 ALGORITHM

Please refer to [Cell Reselection In Idle Mode].

4.5.4 PARAMETERS

In connected mode (CELL-FACH, CELL-PCH and URA-PCH), specific reselection parameters when HCS is not used can be sent using: • SIB4 for cell reselection parameters related to the serving cell if feature “broadcast of SIB4” is enabled • SIB12 for cell reselection parameters related to the neighboring cells if feature “broadcast of SIB12” is

enabled • SIB19 for cell reselection parameters when absolute priority is used if feature “broadcast of SIB19” is

enabled Following activation parameters are used:

Name Object/Class Definition SIB4enable FDDCell

Class3 When set to TRUE, indicates that the SIB4 feature is activated. In this case,

UMTS Radio Mobility



the parameter isDynamicSibAlgoWithSbAllowed has to be set to true. YES: SIB4 is sent NO: SIB4 is not sent

SIB12enable FDDCell Class3

When set to TRUE, indicates that the SIB12 feature is activated. In this case, the parameter isDynamicSibAlgoWithSbAllowed has to be set to true. YES: SIB12 is sent NO: SIB12 is not sent

SIB19enable FDDCell Class3

When set to TRUE, indicates that the SIB19 feature is activated. In this case, the parameter isDynamicSibAlgoWithSbAllowed has to be set to true. YES: SIB19 is sent NO: SIB19 is not sent

isDynamicSibAlgoWithSBAllowed RadioAccessService Class3

This parameter activates/deactivates the use of SB block in the dynamic SIB scheduling algorithm used to broadcast SIB on the Air interface. It has to be set to true in order to broadcast SIB4, SIB12 and SIB19.

The list of parameters for SIB4/12 is the same as for SIB3/11 but they are described in dedicated objects. If SIB4/SIB12 are not broadcasted, parameters of SIB3/SIB11 are used instead. For qHyst1, qHyst2 and tReselection it is furthermore possible to configure them differently on FACH and PCH.


Information Element SIB Object description/comment qualMeas 4&12 CellSelectionInfoC

onnectedMode

Choice of measurement (CPICH Ec/No or CPICH RSCP) to use as quality measure for Fdd cell.

sIntraSearch 4 CellSelectionInfoConnectedMode

Integer (-32..20 by step of 2) In [dB]

sSearchRatGsm 4 CellSelectionInfoConnectedMode


sInterSearch 4 CellSelectionInfoConnectedMode


qQualMin 4 CellSelectionInfoConnectedMode

Integer (-24..0) Ec/N0, In [dB]

qRxLevMin 4 CellSelectionInfoConnectedMode

Integer (-115..-25 by step of 2) RSCP, In [dBm] As of UA04.2 Integer (-58..-13 by step of 2)

qHyst1 4 CellSelectionInfoConnectedMode

Integer (0..40 by step of 2) In [dB]

qHyst1Fach 4 CellSelectionInfoConnectedMode


qHyst1PCH 4 CellSelectionInfoConnectedMode


qHyst2 4 CellSelectionInfoConnectedMode


qHyst2Fach 4 CellSelectionInfoConnectedMode


qHyst2Pch 4 CellSelectionInfoC Integer (0..40 by step of 2)

UMTS Radio Mobility



onnectedMode In [dB] tReselection 4 CellSelectionInfoC

onnectedMode Integer (0..31) In [s]

tReselectionFach 4 CellSelectionInfoConnectedMode

Integer (0..31) In [s]

tReselectionPch 4 CellSelectionInfoConnectedMode

Integer (0..31) In [s]

sibMaxAllowedUlTxPowerOnRach

4 PowerConfClass From -50 to 33 In [dBm]

sSearchHcs 4 CellSelectionInfoConnectedMode

Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the limit for Srxlev in the serving cell below which the UE shall initiate measurements of all neighbouring cells of the serving cell. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-frequency neighbouring cells of the serving cell.

sHcsRatGsm 4 CellSelectionInfoConnectedMode

Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the RAT specific threshold in the serving cell used in the inter-RAT measurement rules. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-RAT neighbouring cells of the serving cell.

speedDependScalingFactorTReselection

4 CellSelectionInfoConnectedMode

Real (0..1 by step of 0.1). This specifies the scaling (multiplication) factor to be used by the UE in idle mode or RRC connected mode states for the parameters Treselection

in case high-mobility state has been detected.

interFreqScalingFactorTReselection


Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-frequency case.

interRatScalingFactorTReselection


Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-RAT case.

tCrMax 4 CellSelectionInfoConnectedMode

Enumerated (not used, 30, 60, 120, 180, 240). This specifies the duration for evaluating allowed amount of cell reselection(s). This parameter is mapped to non-TCRmax or TCRmax IE for SIB3 filling depending of HCS use or not.

nCR 4 CellSelectionInfoConnectedMode

Integer (1..16). This specifies the maximum number of cell reselections. This parameter is mapped to non-NCR or NCR IE for SIB3 filling depending of HCS use or not.

tCrMaxHyst 4 CellSelectionInfoConnectedMode

Enumerated (not used, 10, 20, 30, 40, 50, 60, 70). This specifies the additional time period before the UE can exit high-mobility. This parameter is mapped to non-TCrmaxHyst

or TCrmaxHyst IE for SIB3 filling depending of HCS use or not.

UMTS Radio Mobility




Information Element SIB Object description/comment maxAllowedUlTxPower 12 FddNeighCellSelectionInfoC

onnectedMode From -50 to 33 In [dBm]

primaryScramblingCode 12 FDDCell (neighbouring) Integer(0..511) ulFrequencyNumber 12 FDDCell (neighbouring) This parameters equals ( 5 * FreqDL MHz ) dlFrequencyNumber 12 FDDCell (neighbouring) This parameters equals ( 5 * FreqDL MHz ) qOffset1sn 12 FddNeighCellSelectionInfoC

onnectedMode Integer(-50..50) In [dB]

qOffset2sn 12 FddNeighCellSelectionInfoConnectedMode

Integer(-50..50) In [dB]

qQualMin 12 FddNeighCellSelectionInfoConnectedMode

Integer (-24..0) Ec/N0, In [dB]

qRxLevMin 12 FddNeighCellSelectionInfoConnectedMode

Integer (-115..-25 by step of 2) RSCP, In [dBm]

cellIndivOffset 12 FddNeighCellSelectionInfoConnectedMode

Integer [-20.0..20.0] step:0.5 In [dB]


Information Element SIB Object description/comment maxAllowedUlTxPower 12 GSMCell From -50 to 33

In [dBm] Ncc 12 GSMCell bit string(3) Network Color Code. Part of the BSIC Bcc 12 GSMCell bit string(3) Base Station Color Code. Part of the BSIC GSMbandIndicator 12 GSMCell DCS 1800 band used,

PCS 1900 band used bcchFrequency 12 GSMCell Integer (0..1023) GSM ARFCN gsmCellIndivOffset 12 GsmCellSelectionI

nfoConnMode Integer(-10..10) In [dB]

qOffset1sn 12 GsmCellSelectionInfoConnMode

Integer(-50..50) In [dB]

qRxLevMin 12 GsmCellSelectionInfoConnMode

Integer (-115..-25 by step of 2) In [dBm]


• Ability to broadcast the necessary parameters on the radio interface BCCH. • RRC connection reject in case of unknown u-RNTI


• Support of location registration update from a 3G to a 2G cell, for a PS or CS attached mobile.

4.6. 2G TO 3G HANDOVER FOR CS DOMAIN

4.6.1 DESCRIPTION

4.6.1.1 DATAFLOW

In this case the mobile connected to the CS domain is moved from a 2G cell to a 3G cell.

UMTS Radio Mobility



SRNCBSC

BTS NodeB

UE

Abis

Before

3G-MSC2G-MSC

UE

After

Iub

AnchorMSC

Figure 22: 2G to 3G handover for CS

The next dataflow is an example of inter-MSC 2G to 3G CS handover.

UMTS Radio Mobility



BSSMAP/ Handover command (Handover to UTRAN command)

BSSMAP/ Clear command

BSSMAP/ Handover Required (Source RNC to target RNC transparent information)

UE RNC 2G-MSC/VLR BSS

RANAP/ Relocation request Ack (Handover to UTRAN command)

RRC/ Handover to UTRAN complete

RR/ Intersystem to UTRAN Handover command (Handover to UTRAN command)

3G-MSC/VLR

RANAP/ Relocation request (Source RNC to target RNC transparent information)

NodeB

MAP/ Prepare Handover (Handover Request)

MAP/ Prepare Handover ack (Handover Request Ack)

RANAP/ Relocation Detect

MAP / Process Access Signalling (HO detect)

MAP / Send End Signal

1

2

3

AAL2/ ERQ

AAL2/ ECF

RANAP/ Relocation Complete

GSM resource release

BSSMAP/ Clear complete

NBAP/ Radio Link Setup Request

NBAP/ Radio Link Setup Response

SCCP/ Connection Request


RRC/ Security Mode Command (Integrity Protection)

RRC/ UTRAN Mobility Information (PS domain NAS Information (Routing Area Id))

RRC/ UTRAN Mobility Information Confirm

RRC/ Security Mode complete

Follow up procedures after successful handover from GSM to UMTS:

• Security Update • RRC measurement setup • UE capability enquiry • Mobility Update • In case of Default Configuration:

Radio Link- and Bearer Configuration to ALU standard

4

Figure 23: 2G to 3G handover for CS dataflow

(1) Handover preparation phase. When the handover decision is made, the serving BSC sends a handover

required towards the 2G-MSC and containing the target RNC ID (this IE allows the source MSC to route the message to the correct 3G-MSC/RNC). The request is forwarded to the target 3G RNC which allocates resources to support the call. The request sent from the source BSC identifies only one cell in one RNC. There is no list of possible target.

UMTS Radio Mobility



The "Source RNC to target RNC transparent container" information element which is transferred to the target RNC contains: • the UE capability • the pre-defined configuration status (i.e. which pre-defined configurations have been read by the UE –

if exists) (2) Handover execution phase. The HANDOVER TO UTRAN COMMAND RRC message is sent from the

target 3G to the UE via the MSC nodes and the serving BSC. The handover command message contains the target cell resource description. The handover is performed when the UE is successfully connected to the 3G system. The SECURITY MODE COMMAND procedure is used to trigger integrity protection in UMTS. The UTRAN MOBILITY INFORMATION procedure is used to provide the UE with PS domain Location Information, so that the mobile can initiate or resume PS activity.

(3) Old resource release phase. Old radio link(s) in GSM system are released. (4) Post Handover Procedures.


Radio Link- and Bearer Configuration to ALU standard (see below)

4.6.1.2 TARGET RESOURCE DESCRIPTION

The description of the resource in the target cell is provided by the target RNC to the mobile using the INTERSYSTEM TO UTRAN HANDOVER COMMAND message from the GSM RR layer. There exist 3 possibilities in the 3GPP specifications for describing the target cell resource: 1. The target resource is explicitly described in the "Intersystem to UTRAN Handover command" message. In

this case, the handover message will have a length estimated to 160 bytes, which will imply segmentation on the GSM RR interface (i.e. around 8 segments).

2. In order to reduce the size of the message, pre-defined configurations may be used. These configurations are broadcast on the UTRAN BCCH using SIB 16, and are possibly read by the UE when camping on GSM cell.

3. For the same reason, default configurations may also be used. These configurations are described in 25.331 RRC specifications, and shall be supported by mobiles. They all are derived from 34.108 UE conformance testing specification.

In this version of the document the Alcatel-Lucent RNS either builds the handover message containing: • The explicit target resource description.

The impact is RR message segmentation on the GSM side. The estimated size for a HANDOVER TO UTRAN RRC message is around 180 bytes in case of a (DCCH + speech 12.2) configuration.

• The default configuration 3 for CS Voice 12.2 With this the segmentation of the handover message at GSM RR can be avoided. However, the default configuration has lower performance than the normally used configuration and a reconfiguration after successful handover is required.

The behaviour is configurable by parameter isGsmIratHoDefaultConfigurationUsed.

4.6.2 APPLICABILITY

Depends on BSC algorithm.

UMTS Radio Mobility



4.6.3 ALGORITHM

4.6.3.1 RELOCATION REQUEST MESSAGE STRUCTURE

As the RELOCATION REQUEST message is specified in 2 different specifications (24.413 for the RANAP part, 25.331 for RRC specific IE), this paragraph presents a simplified view of the structure of the message: RELOCATION REQUEST (25.413 §9.1.10)

• source RNC to target RNC transparent container (25.413 §9.2.1.28) • RRC information to target RNC (25.331 §14.12.1)

• Handover to UTRAN Info (25.331 §14.12.4.1) • UE Radio Access capability (25.331 §10.3.3.42)

• Security capability (25.331 §10.3.3.37) • Ciphering algorithm capability • Integrity protection algorithm capability

• Pre-defined configuration status information (25.331 §10.3.4.5a) • UE security information (25.331 §14.13.2.2)

• START-CS • Inter-RAT UE radio access capability (25.331 §10.3.8.7)

• Mobile Station classmark 2 • Mobile Station classmark 3

• nb of Iu instances (=1) • Relocation type (= UE involved) • target cell Id • cell load information group (1)

• RAB to be setup List • Integrity protection information • Encryption information

Note (1): this element is optional and treated if feature uRRM step 2 is activated.

4.6.3.2 RELOCATION REQUEST REJECTION

In this version, a RELOCATION REQUEST rejection by the target RNC can happen in the following cases: There is no resource available in target RNS to support the incoming call Based on the “RAB to setup list” contained by the RELOCATION REQUEST message, the RNC tries to allocate a suitable resource based on CAC algorithm. In case of congestion, a resource may not be available. Resource shortage can also be caused by exhaustion of the reduced Uplink Scrambling Codes for 2G->3G handover with default configuration. The RELOCATION REQUEST has not been issued by a GSM BSS There is no explicit information element in the RELOCATION REQUEST message which indicates from which technology (i.e. GSM or UMTS) the message is issued. However, it is deduced by the target RNC by the content of the “RRC information to target RNC” IE, which is a mandatory part of the message. This IE may be of 2 types:

• In case of handover from another RAT, this IE contains a “Handover to UTRAN Info” container • In case of SRNC relocation, this IE contains a “SRNS Relocation Info” container

4.6.3.3 TARGET RESOURCE ALLOCATION IN RNC

The target resource allocation algorithm in target RNC for incoming calls from 2G takes into account the following limitations from the standard:

• Due to the RELOCATION REQUEST message structure, there is only one target cell to be considered by the target RNC

UMTS Radio Mobility



• Due to limitation of the GSM standard for circuit call, there will be only one RAB in the “RAB to be setup list” in the RELOCATION REQUEST message

Besides, in this version: The resource allocation for incoming relocation from 2G follows the same algorithm as for initial call setup resource allocation, i.e. there is no pool of reserved capacity for incoming relocation from 2G. Based on RAB parameters requested by the Core Network, the RNC will choose a Radio Bearer configuration among the ones which are supported in this version. In this case, the algorithm for RAB to RB mapping is the same as used for call initiation.

4.6.3.4 CIPHERING

The necessary information is passed from the source BSS to the target RNC using the HANDOVER REQUIRED / RELOCATION REQUEST messages so that there is no break in the ciphering:

• Mobile supported ciphering algorithm are provided to the mobile in the “RRC container” • START-CS (used to initialise the 20 MSBs of all hyper frame numbers: MAC-d HFN, RLC UM HFN,

RLC AM HFN, RRC HFN) is provided in the “RRC container” CK (UMTS ciphering Key) is provided by the 3G-MSC in the RELOCATION REQUEST (“Encryption information “ IE), resulting from the conversion of Kc (GSM ciphering key) by the 3G-MSC. Ciphering is started by the mobile immediately after receiving the HANDOVER TO UTRAN COMMAND message.

4.6.3.5 INTEGRITY

Integrity is started by the RNC immediately after receiving the HANDOVER TO UTRAN COMPLETE RRC message. The necessary information is passed from the source BSS to the target RNC using the HANDOVER REQUIRED / RELOCATION REQUEST messages so that there is no break in the ciphering:

• Mobile supported integrity algorithm are provided to the mobile in the “RRC container” • START-CS (used to initialise the 20 MSBs of all hyper frame numbers: MAC-d HFN, RLC UM HFN,

RLC AM HFN, RRC HFN) is provided in the “RRC container” IK (UMTS Integrity Key) is provided by the 3G-MSC in the Relocation Request (“Integrity protection information“ IE), resulting from the conversion of Kc (GSM ciphering key) by the 3G-MSC.

UE RNC


NodeB



4.6.3.6 DEPENDENCIES WITH GSM

For this procedure to be working correctly, it is mandatory the GSM BSS supports the “UTRAN classmark change” as specified in GSM TS 04.18 Release 99 (resp. 3GPP TS 44.018 Release 4 and beyond), as this message contains the following information:

• UE Radio Access capability ([A4] §10.3.3.42) • START-CS parameter (this parameter is actually stored on the mobile USIM)

UMTS Radio Mobility



4.6.3.7 USE OF DEFAULT CONFIGURATION

The IRAT HO message should be sent within one block in GSM to reduce handover delay and increase handover success rate.

The UMTS standard allows specifying individually the radio bearer and transporting channels via a large set of parameters. This results in large messages, which have to be transferred via the GSM air interface in order to inform the UE about the radio configuration for the UMTS network access. In case that segmentation is used, subsequent segments can only be transferred after acknowledgement of earlier transmitted segments. In case of handover however, the quality of the uplink may be quite poor resulting in a failure to transfer acknowledgements. This implies that it may be impossible to quickly transfer a segmented handover message. Segmentation over more than two GSM air interface blocks could have a significantly detrimental impact on handover performance.

The handover performance is improved when it is possible to transfer the handover to UTRAN command within a non-segmented GSM air interface message. The usage of the default reduces the size of the HANDOVER TO UTRAN COMMAND message and thus the GSM HANDOVER COMMAND message.

Default Configuration #3 (see [A4]) is supported for 12.2 kbps CS speech and transmitted in the handover command via core network and GERAN to the UE.

Whether the requested RAB can be served by default configuration #3 or not depends on the Iu UP version and the offered AMR codecs in the inter-RAT relocation request as per following table:

Iu UP version

Offered AMR codecs in 2G to 3G relocation

request

Selected configuration type for handover to UTRAN command

any mono rate 12.2 default config #3 any mono rate != 12.2 full config any multi rate without 12.2 full config Iu UP v1 multi rate with 12.2 default config #3 Iu UP v2 multi rate with 12.2 full config

After successful completion of the GSM to UMTS handover, indicated by receipt of the HANDOVER TO UTRAN COMPLETE message, the RNC reconfigures the radio bearer to the normal, optimized configuration.

Within this reconfiguration the RLC parameters should be reconfigured, too. If RLC reconfiguration is available, then it advisable to enable it (parameter isRlcAMReconfigurationAllowed and isUER99RlcAmReconfigurationAllowed). If it is not available, then either the use of default configurations should be disabled (parameter isGsmIratHoDefaultConfigurationUsed) or the call will have sub-optimal RLC parameter settings.

4.6.4 FAILURE CASES

4.6.4.1 CONNECTION RELEASE

On the network side, if timer T3121 elapses before either the HANDOVER TO UTRAN COMPLETE ([A4] and [A6]) RRC message is received on the UTRAN channel(s), or a HANDOVER FAILURE RRC message is received on the old channels, or the mobile station has re-established the call, the old channels are released if they were dedicated channels and all contexts related to the connections with that mobile station are cleared.

4.6.4.2 RETURN ON OLD CHANNEL

In case the mobile fails to synchronize or access on the new UTRAN channel, the mobile returns on the old channel it was using in the GSM source cell.

UMTS Radio Mobility



BSSMAP/ Handover command (Handover to UTRAN command)



RR/ Intersystem to UTRAN Handover command (Handover to UTRAN command)

3G-MSC/VLR NodeB

MAP / Prepare Handover ack (Handover Request Ack)

RANAP/ Iu Release Command

MAP / Abort

1

2

RANAP/ Iu Release Complete

The UE returns on the old channel

RR/ Handover Failure

BSSMAP/ Handover failure

Handover preparation phase (as in normal successful case)

AAL2/ REL

AAL2/ RLC

NBAP/ Radio Link Deletion Request

NBAP/ Radio Link Deletion Response

Cancellation of on-going HO procedure

Figure 24: 2G to 3G handover for CS – failure case (1) As the mobile returns to the old channel, a handover failure message is sent to the 2G_MSC, leading to a cancellation of the handover procedure on the MAP interface. (2) As a consequence, the target RNC receives an Iu release command message from its MSC, requesting all the resources which have been allocated during the handover preparation phase to be released.

4.6.4.3 RELOCATION REJECTED BY TARGET RNC

If the relocation preparation phase fails (see possible causes in the related chapter), a relocation failure is sent from RNC to the 3G-MSC.

BSSMAP/ Handover Required reject

BSSMAP/ Handover Required(Source RNC to target RNC transparent information)


RANAP/ Relocation failure (No resource available)

3G-MSC/VLR

RANAP/ Relocation request(Source RNC to target RNC transparent information)

NodeB

MAP / Prepare Handover (Handover Request)

MAP / Prepare Handover ack (failure)

No resource in RNS

UMTS Radio Mobility



Figure 25: 2G to 3G handover for CS – failure case

4.6.5 PARAMETERS

The parameters are:

Name Object/Class Definition is2GTo3GCSHandoverAllowedWithinRnc InterFreqMeasConf

Class3 This parameter indicates whether the 2G To 3G CS Handover is allowed within the RNC YES: incoming relocation request from 2G are processed NO: incoming relocation requests from 2G are rejected

isGsmIratHoDefaultConfigurationUsed

RadioAccessService Class3

This parameter enables/disables the use of default configurations for inter RAT handover from GSM to UMTS.


• support for incoming relocation procedures (involving SCCP connections initiated by the CN) • ability to format the HANDOVER TO UTRAN message (as defined in the RRC specification) • start of security procedure (ciphering & integrity) at the end of the handover execution at RRC level


• BSSMAP to RANAP message interworking at the 3G-MSC level. This implies not only message conversion, but also deriving RAB attributes from the current channel in use in GSM.

• Ciphering and integrity key conversion at the 3G-MSC

4.7. 2G TO 3G HANDOVER FOR PS DOMAIN

In this case the mobile connected to the network in GPRS mode is moved from a 2G cell to a 3G-PS cell.

RNC BSC

BTS 1 NodeB 2

UE

Iub

Before

3G-SGSN 2G-SGSN

GGSN

UE

After

Abis

Figure 26: 2G to 3G handover for PS

UMTS Radio Mobility



In GPRS, the mobility decision is taken by the UE. The GPRS mobility is done via a Routing Area Update procedure. Once PDP context transferred from old to new SGSN, the 3G SGSN requests for a RAB establishment as for a call establishment. The next dataflow is an example of inter-SGSN 2G to 3G handover.


3G-SGSN 2G-SGSN Serving BSC Target RNC UE

GMM/ RA update request


BTS

GMM / RA update accept

PDP context update with GGSN

RANAP/ RAB assignment request

Update GPRS location with HLR

GMM / RA update complete

RANAP/ RAB assignment response

GTP/ SGSN ctx ack


4.8. 2G TO 3G HANDOVER FOR CS + PS DOMAINS

In this case the mobile connected to both CS and PS domains, and is moved from a 3G cell to a 2G cell. CS and PS parts are managed independently. The CS part is managed as described in § 4.6 and the PS part as in § 4.7.

4.9. 3G TO 2G HANDOVER FOR PS DOMAIN

4.9.1 DESCRIPTION

In this case the mobile connected to the network in PS mode is moved from a 3G cell to a 2G-GPRS cell.

UMTS Radio Mobility



BSCSRNC

NodeB 1 BTS 2

UE

Iub

Before

2G-SGSN3G-SGSN

GGSN

UE

After

Abis


The next dataflow is an example of inter-SGSN 3G to 2G handover. In this version, the mobile is using dedicated resources for PS services in 3G network. Therefore, the handover decision is taken by the SRNC (as if it were a CS call). Meanwhile, as opposed to CS handover, the connection and resource allocation in the target system are performed on UE request.


2G-SGSN 3G-SGSNServing RNC Target BSCUE



GTP/ SGSN ctx ack



RANAP/ SRNS data forward command

TDATAfwd



GMM / RA update response

RRC/ Cell change order from UTRAN (BSIC, BCCH ARFCN)

2G access and GPRS resource allocation

Serving NodeB



1

2

3


Figure 29: 3G to 2G handover for PS dataflow

(1) Based on measurements, the serving RNC decides to hand the mobile over a 2G cell. Following the mobile

access on the 2G cells, resources are allocated in the target BSS. The cell change order message contains the

UMTS Radio Mobility



target cell BSIC and BCCH ARFCN which are used by the mobile to get the target synchronisation before accessing to the network.

(2) The mobile updates its location in the target 2G system using the "RA update" procedure. The PDP contexts which were active in 3G and the N-PDU and GTP-PDU counters are transferred in 2G using GTP and RANAP context transfer procedures. In this version, N-PDU and GTP-PDU will not be transferred by the RNC on the RANAP protocol.

(3) Although not supported by UTRAN in this version, data forwarding may be asked by the source SGSN. Even if no data is forwarded, the old SRNC shall not complete the resource release phase until TDATAfwd (data forwarding timer). In this version, TDATAfwd is equal to 0 sec.

4.9.2 APPLICABILITY

In this version, the mobile is using either dedicated or shared resources for PS services in 3G network. Since the quality of service offered to subscribers will be better in UMTS as compared to what GPRS can offer, the PS subscribers will be kept in 3G as much as possible, and will only be handed to 2G in case of UTRAN coverage holes, or when leaving a UTRAN coverage spot. The decision to launch this mobility procedure is taken by the iMCTA function (refer to section 4.19)

4.9.3 ALGORITHM

4.9.3.1 HO DECISION PROCESS

Please refer to section 4.20.

4.9.3.2 MEASUREMENTS CONFIGURATION


4.9.3.3 TARGET CELL CHOICE


4.9.4 FAILURE CASES

4.9.4.1 TARGET CELL SYNCHRONIZATION FAILURE

If the mobile fails to access and synchronize on the target GSM cell, Alcatel-Lucent UTRAN allows a possible return on the old channels. In such a case, the mobile sends a CELL CHANGE ORDER FROM UTRAN FAILURE message on the channel that was used in the serving UTRAN cell(s) and re-establish on the resource that were user in 3G.

2G-SGSN 3G-SGSNServing RNC Target BSCUE

RRC/ Cell change order from UTRAN (BSIC, BCCH ARFCN)

The HO fails on the target system

Serving NodeB

RRC/ Cell change order from UTRAN failure

Figure 30: 3G to 2G handover for PS - failure case

UMTS Radio Mobility



Another handover will be tried as in the normal process, i.e. possibly next time the handover criteria is evaluated and using "target cell choice" algorithm as specified. No handover will be tried towards the 2nd best cell.

4.9.5 PARAMETERS

The parameters are:

Name Object/Class Definition activationHoGsmPsAllowed RadioAccessService

Class3 This parameter indicates if the PS handover toward a GSM cell is allowed.

See also:

� Section 4.20; � Section 6.5.


On the UTRAN Access side: • UE UTRAN DL measurement activation • support of one GSM neighbouring cells information (including BSIC and ARFCN) • support of relevant Iu RANAP procedures On the GSM Access side: • None (in this case, the handover is seen from the BSS as a new GPRS call setup). Restrictions: • data packet forwarding is not supported by the source RNC. Therefore, some packets will be lost during the

handover. End-to-end reliability is supposed to be provided by transport layer (e.g. TCP). • the "SRNS context transfer" procedure is not supported by the source RNC (i.e. the messaging is supported

but the PDU counters are not transferred). As for "packet forwarding", the consequence is that some packets may be lost, since the target RNC doesn't know which GTP-PDU have actually been sent and acknowledged.


• support of relevant RANAP procedures • the 3G PDP QoS parameters need to be translated by the 3G-SGSN into 2G parameters • the ciphering key CK needs to be translated into 2G GPRS ciphering key

4.10. 3G TO 2G HANDOVER FOR CS DOMAIN

4.10.1 DESCRIPTION

In this case the mobile connected to the CS domain is moved from a 3G cell to a 2G cell.

UMTS Radio Mobility



BSCSRNC

NodeB BTS

UE

Iub

Before

2G-MSC3G-MSC

UE

After

Abis

AnchorMSC

RelayMSC

Figure 31: 3G to 2G handover for CS

The next dataflow is an example of inter-MSC 3G to 2G CS handover.

RANAP/ Relocation Command (handover command)


RANAP/ Relocation Required (CM2, CM3, old BSS to new BSS information)


BSSMAP/ Handover Request Ack (handover command)


RRC/ Handover from UTRAN Command (handover command (cell description))

BSSMAP/ Handover Complete

RR/ Handover Access

3G-MSC/VLR

BSSMAP/ Handover Request (CM2, CM3, old BSS to new BSS information)

NodeB


MAP / Prepare Handover Ack (Handover Request Ack)

BSS resource allocation



BSSMAP/ Handover Detect MAP / Process Access Signalling (HO detect)


1

2

3

AAL2 / REL

AAL2 / RLC


RR/ Physical Information (Timing Advance)

RR/ Handover Complete


(1) Handover preparation phase. When the handover decision is made, the serving RNC activates the relocation procedure towards the 3G-MSC. The request is forwarded to the target 2G BSS which allocates resources to support the call. The RELOCATION REQUIRED message contains the UE GSM capability (ClassMark 2 and 3).

UMTS Radio Mobility



The "old BSS to new BSS" information element contains the UE capability, which is transferred to the target BSS, in case the mobile is handed over 3G again. It also contains the cell load information group element if feature uRRM step 2 is activated. (2) Handover execution phase. The HANDOVER COMMAND message from the GSM RR layer is sent from the target 2G to the UE via the MSC nodes and the serving RNC. This message contains the target cell description (i.e. BSIC and BCCH ARFCN), which will allow the mobile to synchronize to the cell when the handover is made in blind mode. The handover is performed when the UE is successfully connected to the 2G system. (3) Old resource release phase. Old radio link(s) and associated AAL2 Cid(s) are released.

4.10.2 APPLICABILITY

In this version, 3G to 2G handover for CS calls which have reached the call established state is a rescue type of mobility, triggered on radio alarm criterion. CS subscribers may be handed to 2G in case of UTRAN coverage holes, or when leaving a UTRAN coverage spot.

In addition to providing this alarm-based 3G-2G handover for established calls, the 3G infrastructure may also move calls in the following use cases:

� iMCTA function decision (refer to section 4.194.20);

� RRC Speech Redirection: If a UE cannot successfully connect to the UTRAN (via RRC connection establishment) or in case of load or of emergency call, the RNC instructs the UE to perform inter-system cell reselection and re-originate the call on the 2G network (refer to 4.18.2 to 4.18.4 sections).

4.10.3 ALGORITHM







4.10.4 FAILURE CASES

4.10.4.1 TARGET CELL SYNCHRONIZATION FAILURE

If the mobile fails to access and synchronize on the target GSM cell, it has to send a HANDOVER FROM UTRAN FAILURE message on the channel that was used in the serving UTRAN cell(s).

UMTS Radio Mobility



2G-MSC 3G-MSCServing RNC Target BSCUE

RRC/ Handover from UTRAN command (BSIC, BCCH ARFCN)

The HO fails on the target system

Serving NodeB

RRC/ handover from UTRAN failure

Figure 33: 3G to 2G handover for CS - failure case

Another handover will be tried as in the normal process, i.e. possibly next time the handover criteria is evaluated and using "target cell choice" algorithm as specified. No handover will be tried towards the 2nd best cell.

4.10.4.2 RELOCATION PREPARATION FAILURE

It may happen the Relocation Preparation fails, e.g. because the target GSM BSS has no resource left. In this case, the relocation preparation procedure ends up as follows:

RANAP/ Relocation preparation failure (cause)

RANAP/ Relocation Required(CM2, CM3, old BSS to new BSS information)


BSSMAP/ Handover Failure (cause)

3G-MSC/VLR

BSSMAP/ Handover request(CM2, CM3, old BSS to new BSS information)

NodeB


MAP / Prepare Handover ack (Handover failure)


Figure 34: 3G to 2G handover for CS - failure case

If allowed by parameter isGsmIratHoToNextBestCellAllowed, if the UE had reported further eligible GSM target cells in a measurement report and if the criteria for handover are still fulfilled then the RNC retries relocation preparation for the next best GSM cell. The attempts are repeated until either • The relocation preparation has failed for the last eligible GSM cell • A follow-up measurement report contains both, eligible GSM and inter-frequency target cells. In this case

the RNC tries the handover to the strongest inter-frequency target. • The criteria for handover are no longer fulfilled, e.g. an event 2F indicates the end of the alarm condition. Another handover will be tried as in the normal process, i.e. possibly next time the handover criteria are evaluated and using "target cell choice" algorithm as specified.

4.10.5 PARAMETERS

The parameters are:

Name Object/Class Definition activationHoGsmCsAllowed RadioAccessService

Class3 This parameter indicates if the CS handover toward a GSM cell is allowed.

UMTS Radio Mobility



isCellLoadInformationSendingAllowed RadioAccessService Class3

This parameter controls sending of cell load information IE in handover messages to 2G

isGsmIratHoToNextBestCellAllowed


This parameter enables/disables the IRAT handover to the next best GSM cell if handover is not possible to the first cell, e.g. due to overload.

See also

� Section 4.19. � Section 6.5.


On the UTRAN Access side: • support of relevant Iu RANAP procedures • support of relevant RRC procedures On the GSM Access side: • Some impacts on the A interface (new UE Capability IE in the Handover Request) • Only impact is a new counter on 3G to 2G (based on the source cell " Cell identification discriminator"

contained by the Handover Request)


• BSSMAP to RANAP message interworking at the 3G-MSC level. This implies not only message conversion, but also deriving GSM channel type attributes from the RAB attributes.

4.10.8 PERFORMANCE MANAGEMENT

• IRATHO.AttRelocPrepOutCS.NextBestCell (-.NeighbRnc) Attempted relocation preparations for CS UMTS to GSM handover to the next best GSM cell. This counter is a complement to counter IRATHO_AttRelocPrepOutCS. IRATHO_AttRelocPrepOutCS is pegged on all attempted relocation preparations for CS UMTS to GSM handover. IRATHO.AttRelocPrepOutCS.NextBestCell is pegged only if the relocation preparation has failed for one target GSM cell and the RNC retries the handover for the next GSM target cell. The difference between IRATHO_AttRelocPrepOutCS and IRATHO.AttRelocPrepOutCS.NextBestCell represents the actual number of handover attempts without repeated relocation preparation procedures.

• IRATHO.SuccRelocPrepOutCS.NextBestCell (-.NeighbRnc) Successful relocation preparations for CS UMTS to GSM handover to the next best GSM cell (CS inter-RAT Handover Attempt) from network point of view.

4.11. 3G TO 2G HANDOVER FOR CS+PS DOMAINS

4.11.1 DESCRIPTION

4.11.1.1 GENERAL

In this case the mobile is connected to both CS and PS domains, and is moved from a 3G cell to a 2G cell.

UMTS Radio Mobility



BSCSRNC

NodeB BTS

UE

Iub

Before

2G-MSC3G-MSC

UE

After

Abis

AnchorMSC

2G-SGSN3G-SGSN

GGSN

Figure 35: 3G to 2G handover for CS+PS

Several classes of mobile have been defined in the GPRS specifications: • class C: the mobile is attached to either GPRS or GSM services. Alternate use only. This case is not further

considered in this document. • class B: the mobile is attached to both GPRS and GSM services, but the mobile can only operate one set of

services at a time • class A: the mobile is attached to both GPRS and GSM services, and can support simultaneous traffic • DTM (Dual Transfer Mode): DTM is a subset of class A mode of operation. In this mode, GSM CS and PS

resource allocation are coordinated in BSC/PCU in order to simplify mobile implementation. Class A or DTM The real successful case (i.e. PS and CS services are both active in the new cell) assumes that • the mobile is either GPRS Class A or DTM (Dual Transfer Mode or simple Class A) capable • the new cell can offer GPRS service Regarding the CS domain, the CS service is handed over the target GSM cell exactly as in the "3G to 2G handover for CS" case, i.e.: • a relocation is required by the serving RNC • new resources corresponding to the CS RAB are allocated in the target system • and the mobile is explicitly handed over the target resources (this is performed through the "Handover from

UTRAN" RRC procedure) Regarding the PS domain, the PS service is handed over the target GSM cell in the same way as the "3G to 2G handover for PS" case, i.e.: • the mobile is requested by the SRNC to change cell (this is done implicitly through the "Handover from

UTRAN" RRC procedure) • the mobile tries to re-establish the PS service in the target cell Class B In this case, the CS service is handed over to GSM and the PS service cannot be maintained. Since the mobile will not detach nor deactivate the PDP context which were active in the source 3G-SGSN, the PDP context will remain active in the 3G-SGSN. Remark: In this version, the source RNC will not take into account the mobile GPRS capability in the handover decision algorithm.

UMTS Radio Mobility



4.11.1.2 SUCCESSFUL CLASS A/DTM CASE

The next dataflow is an example of successful inter-MSC 3G to 2G CS+PS handover for a class A or DTM capable mobile.

RANAP/ Relocation command (handover command)




BSSMAP/ Handover request Ack (handover command)

Resources Release

RRC/ Handover from UTRAN command (handover command (cell description))

BSSMAP/ Handover Complete

RR/ Handover Access

3G-MSC/VLR

BSSMAP/ Handover request (CM2, CM3, old BSS to new BSS information)

NodeB


MAP / Prepare Handover ack (Handover Request)

BSS resource allocation



BSSMAP/ Handover Detect MAP / Process Access Signal (HO detect)


1

2

4+5 AAL2 / REL

AAL2 / RLC

3G-MSC/VLR



3G-SGSN

2G-SGSN 3G-SGSN




GTP/ SGSN ctx ack



GMM / RA update response

2G access and GPRS resource

allocation

3

RANAP/ Iu release request

TRelocResourceReleasePs3Gto2Gtimer (set to 20 sec)

Figure 36: 3G to 2G handover for CS+PS dataflow

UMTS Radio Mobility



(1) CS Handover preparation phase. When the handover decision is made, the serving RNC activates the relocation procedure towards the 3G-MSC. The request is forwarded to the target 2G BSS which allocates resources to support the call.

(2) CS Handover execution phase. The handover command is sent from the target 2G to the UE via the MSC nodes and the serving RNC. The handover command message contains the cell description (i.e. target cell BSIC and BCCH), which will be used by the mobile to synchronise on the target cell and decode the (P)BCCH for the PS service re-establishment. The handover is performed when the UE is successfully connected to the 2G system.

(3) PS service re-establishment: The UE performs a packet access in the 2G new cell. Eventually, the registration is accepted, and the PS data transfer is resumed.

(4) + (5) coordinated release of old CS + PS resources • Old radio links are released • Iu CS resource release. AAL2 Cid(s) associated to the CS domain are released. • Iu PS resource release. As for the "3G to 2G handover case", the source SGSN may request the source

RNC to forward the PS packets queued in the SRNC using the SRNS DATA FORWARD COMMAND message. In that case, the RNC behaviour is the same as for the "3G to 2G PS handover" case.

The data flow above is only provided as an example. The order of the different phase may be different as compared to a real case. For example, the Iu CS release (4) may be requested before the PS registration (3). In this release: upon receipt of message IU RELEASE COMMAND (CS), the RNC arms immediately a timer called RelocResourceReleasePs3Gto2Gtimer (optimized at 20 sec) and sends an IU RELEASE REQUEST (PS) message. Upon receipt of the IU RELEASE COMMAND (PS) or RelocResourceReleasePs3Gto2Gtimer expiration, the RNC coordinates release of old CS and PS resources.

Upon receipt of the IU RELEASE COMMAND (PS):

RNC 3G MSC/VLR 3G SGSN

UE 3G MSC/VLR 3G SGSN

RANAP / Iu Release Command

RANAP / Iu Release Request


RANAP / Iu Release Complete


Release of all CSand PS resources

TR

eloc

Res

ourc

eRel

ease

Ps

3Gto

2Gtim

er (

set t

o 20

sec

)

4+5

para

llel

Upon receipt TRelocResourceReleasePs3Gto2Gtimer expiration:

UMTS Radio Mobility



RNC 3G MSC/VLR 3G SGSN

UE 3G MSC/VLR 3G SGSN


RANAP / Iu Release Request


Release of all CSand PS resources

4+5

TR

eloc

Res

ourc

eRel

ease

Ps

3Gto

2Gtim

er (

set t

o 20

sec

)

4.11.1.3 SUCCESSFUL CLASS B CASE

In this case the PS service will not be handed over the 2G target cell. The phase (3) “PS service re-establishment” does not occur. As the RNC sends an IU RELEASE REQUEST to the 3G-SGSN, the RNC will receive an IU RELEASE COMMAND from the 3G-SGSN or will experience the timeout RelocResourceReleasePs3Gto2Gtimer (set to 20 sec). In any case the RNC releases the CS and PS resources: phase “(4)+ (5) coordinated release of old CS and PS resources”. This case is further described in the [unsuccessful case] section.

4.11.1.4 HANDLING UNSUCCESSFUL CASES

Iu connections timers In order to cover the following case: • the mobile is completely lost (i.e. the handover has failed and the mobile has not returned to the old channel) • the PS service is lost during HO (e.g. because of limited UE capability (class B or C), or because the target

cell cannot accept or support GPRS access) Two timers (one for the PS domain, one for the CS domain) are implemented in the RNC to request a release of UTRAN resources to the relevant CN domain. In the CS+PS case, only one timer is started, corresponding to the highest value. The following dataflow illustrate the 1st case: Phase 1 and 2 (handover preparation and execution) are performed as in the successful case. In phase 3 and 4, when the "Iu release" timer elapses, the source RNC requests for both CS and PS Iu release.

UMTS Radio Mobility






UE RNC



3G-MSC/VLR NodeB





1

2

3

AAL2 / REL

AAL2 / RLC


Iu release timer

3G-SGSN




Figure 37: 3G to 2G handover for CS+PS - failure case

The following dataflow illustrates the 2nd case: Phase 1 and 2 (handover preparation and execution) are performed as in the successful case. Following successful CS handover the Core Network commands a release of the Iu. This release is not processed until the "Iu release timer" elapses. In which case, both Iu-CS and PS connections (and associated UTRAN resources) are released.

UMTS Radio Mobility






UE RNC



3G-MSC/VLR NodeB





1

2

3

AAL2 / REL

AAL2 / RLC



3G-SGSN

Iu release timer


Figure 38: 3G to 2G handover for CS+PS - failure case

HO failure case The possible failure cases are the following: • The synchronisation on the new CS channel fails. In that case, the mobile returns on the old channel using

the Handover from UTRAN failure message and the relocation is cancelled by the source RNC, as in the CS only case.

• The handover for the CS service is successfully performed, but the PS registration fails (reject from the new SGSN, or because GPRS is not supported by target cell ...). In this case, nothing specific is done. The CS service goes on, whereas the PS service has failed. From a source UTRAN point of view, this case is identical to the Class B mobile handover case.

Due to the time needed to resynchronise the CS service, it is not expected the PS service can be resumed in the new cell before the CS service. Handover/call setup race condition If a 3G to 2G handover decision is made while a PS call is active and a CS call is being setup, nothing is done until the CS RAB is established. Once the CS RAB is setup, and if the handover conditions are still valid, a 3G to 2G PS+CS handover is tried. If a 3G to 2G handover decision is made while a CS call is active and a PS call is being setup, nothing is done until the PS RAB is established. Once the PS RAB is setup, and if the handover conditions are still valid, a 3G to 2G PS+CS handover is tried.


See 4.10.2 [3G To 2G Handover for CS Domain] section APPLICABILITY

UMTS Radio Mobility



4.11.3 ALGORITHM






Please refer to section 4.19. It has to be noted that the UE classmark (support of class A or DTM) or the target cell GPRS capability is not taken into account in the decision process.

4.11.4 PARAMETERS

Refer to: � Section 4.19. � Section 6.5.

Note: In the CS+PS case a handover to a 2G cell is only performed if both activationHoGsmCsAllowed and activationHoGsmPsAllowed parameters are set to "YES"


On the UTRAN Access side: • UE UTRAN DL measurement activation • support of GSM neighbouring cells information (including BSIC and ARFCN) • support of relevant Iu RANAP procedures • support of relevant RRC procedures On the GSM Access side: • No functional impact • Only impact is a new counter on 3G to 2G


No specific impact, as compared to the 3G to 2G PS or CS handover. Since the Gs interface is not supported, the 2 handover procedures are seen as independent.

4.12. 4G TO 3G RELOCATION FOR PS DOMAIN

4.12.1 DESCRIPTION

4.12.1.1 DATAFLOW

In this case the mobile connected to the network in PS mode is moved from a 4G eNodeB cell to a 3G cell.

UMTS Radio Mobility



GERAN

BTSBTSBTS

E-UTRAN

SGWSGWeNBeNB

MMEMME

PGW/GGSNPGW/GGSN

PCRFPCRF

S11

S1-U S5

Gx

SGi

HSS HSS

Rx

S1-MME

S6a

Data ServicesData Services(e.g., VPN, FTP)(e.g., VPN, FTP)

ApplicationApplicationFunctionFunction

UTRAN

NBNBNB RNCRNCRNC

SGSNPre-Rel 8

SGSNSGSNPrePre--RelRel 88

Gn (signaling)

Iu-ps

S10

Gn (user)

Pre-R8 Interfaces

BSCBSCBSCGbAbis

Iub

Gr

Anchor of the

IP session

• MME acts like a SGSN

• PGW acts like a GGSN

• MME & PGW have to support Gn

interface (GTPv1-c support)

Control planeUser plane

Figure 39: 4G to 3G handover (Interworking with pre-Rel. 8 legacy SGSN, Without direct tunnelling) The PDN GW provides the functions of a GGSN for the SGSN. Interworking is provided only with Gn and Gp interfaces but no S3, S4 or S5/S8 interfaces, i.e. these Gn/Gp SGSNs provide no functionality that is introduced specifically for the EPS or for interoperation with the E-UTRAN. The next dataflow is an example of 4G to 3G relocation request.

UMTS Radio Mobility



S1/ Handover command (Handover to UTRAN command)

S1/ UE context release complete

S1/ Handover Required (Source RNC to target RNC transparent information)

UE RNC MME eNB



RRC mobility from EUTRAN command (Handover to UTRAN command)

SGSN


NodeB

GTP/ Forward Relocation request (Handover Required)

GTP/ Forward Relocation response (Handover Request Ack)

RANAP/ Relocation Detect

GTP/ Forward Relocation Complete ()

1

2

3

AAL2/ ERQ

AAL2/ ECF

RANAP/ Relocation Complete


NBAP/ Radio Link Setup Response



RRC/ Security Mode Command (Integrity Protection)

RRC/ UTRAN Mobility Information (PS domain NAS Information (Routing Area Id))

RRC/ UTRAN Mobility Information Confirm

RRC/ Security Mode complete

Follow up procedures after successful handover from E-UTRAN to UMTS:


Radio Link- and Bearer Configuration to ALU standard

4

GTP/ Forward Relocation Complete Acknowledge ()

S1/ UE context release command


(1) Handover preparation phase. When the handover decision is made, the source eNodeB sends a handover

required towards the source MME to request the CN to establish resources in the target RNC, and the target SGSN. The MME sends a Forward Relocation Request message (IMSI, Tunnel Endpoint Identifier Signalling, MM Context, PDP Context, Target Identification, RAN Transparent Container, RANAP Cause, GCSI) to the new SGSN. PDP context contains GGSN Address for User Plane and

UMTS Radio Mobility



Uplink TEID for Data. The Source to Target Transparent Container received from eNodeB is indicated as RAN Transparent Container. SCCP connection is established between the SGSN and the RNC. The Ranap Relocation Request message contains the IE “source RNC to target RNC transparent container” including the RRC container IE “Inter rat handover Info with inter Rat UE capabilities” . This message must also contain the IEs “Integrity Protection Information”, and the IE “Encryption Information”, which represent the information used for the ciphering and integrity protection. The RNC checks and allocates the resources needed in order to become the SRNC (RRC context, RAB context). The successful allocation of resources is confirmed to the CN via the Ranap Relocation Request Acknowledge message. The RRC Handover Command message is included in the IE “target RNC to source RNC transparent container”. The timer Treloc complete is started. The S1 Handover Command message is sent to the source eNB including the RRC Handover to UTRAN message.

(2) Handover execution phase. The HANDOVER TO UTRAN COMMAND RRC message is sent from the target 4G to the UE. The handover command message contains the target cell resource description. The handover is performed when the UE is successfully connected to the 3G system. . The SECURITY MODE COMMAND procedure is used to trigger integrity protection in UMTS. The UTRAN MOBILITY INFORMATION procedure is used to provide the UE with PS domain Location Information, so that the mobile can initiate or resume PS activity. The target SRNC confirms to the CN that the SRNC relocation has been successful by sending the Ranap Relocation Complete message. The timer Treloc complete is stopped by the SGSN.

(3) Old resource release phase. Old radio link(s) in LTE system are released.

(4) Post Handover Procedures.

• Security Update • RRC measurement setup • UE capability enquiry • Mobility Update

4.12.2 ALGORITHM

4.12.2.1 RELOCATION REQUEST MESSAGE STRUCTURE

RELOCATION REQUEST (25.413 §9.1.10) • CN Domain Indicator (M): PS Domain; • source RNC to target RNC transparent container (25.413 §9.2.1.28)

• RRC information to target RNC (25.331 §14.12.1) • Handover to UTRAN Info (25.331 §14.12.4.1)

• UE Radio Access capability (25.331 §10.3.3.42) • Security capability (25.331 §10.3.3.37)

• Ciphering algorithm capability • Integrity protection algorithm capability

• Pre-defined configuration status information (not used) • UE security information (not used) • UE security information2 (25.331 §10.3.3.42c)

• START-PS • Inter-RAT UE radio access capability (25.331 §10.3.8.7)

• Mobile Station classmark 2 (not used) • Mobile Station classmark 3 (not used)

• nb of Iu instances (=1) • Relocation type (= UE involved) • target cell Id • cell load information group (not used)

• RAB to be setup List • Integrity protection information

UMTS Radio Mobility



• Encryption information The difference with the CS 2G 3G relocation (4.6.3.1) concerns the following IE: • CN Domain Indicator: PS Domain; • Source RNC To Target RNC Transparent Container;

• UE security information2 (START-PS values to be used) • UE radio access capability compressed (not used, see Note 1) • UE radio access capability comp2 (not used, see Note 1).

• RAB to be setup List • Synchronisation Indicator (Not used, only significant for speech) • Data Volume Reporting Indication (not used) • PDP type information (not used) • UP Mode Versions (to be used); • Iu Transport Association (GTP TEID: to be used) • Alternative RAB Parameter Values (not used) • GERAN BSC Container (not set: used only when coming from 2G) • E-UTRAN Service Handover (As UA07.1.2 uses the 3GPP Iu Rel 7, this IE will be not decoded by the

RNC if receivei) • Global CN-ID (only used when relocation comes from 2G)

Note 1: The two IE were created in Rel 5/6 to reduce the size of the information reported by the UE on the “GSM air”. We don’t guess it will be an issue in E-UTRA. So the proposal is to not use them in E-UTRA when asking the UE to report its UTRAN capabilities.

4.12.2.2 RELOCATION REQUEST REJECTION

In this version, a RELOCATION REQUEST rejection by the target RNC can happen in the following cases: The incoming relocation from E-UTRA is not allowed (isEutraToUtraHhoAllowed=FALSE). There is a ciphering mismatch with parameter FromEutraRelocationCiphering. There is no resource suitable or available in target RNS to support the incoming call • In case of a RAB or a Rab combination not supported by ALU RNC • Based on the “RAB to setup list” contained by the RELOCATION REQUEST message, the RNC tries to

allocate a suitable resource based on CAC algorithm. In case of congestion, a resource may not be available. • In case of failure of the NBAP Radio Link setup (reception of radio link setup failure or no answer) The RELOCATION REQUEST has not been issued by a E-UTRAN There is no explicit information element in the RELOCATION REQUEST message which indicates from which technology (i.e. GSM or E-UTRAN) the message is issued. However, it is deduced by the target RNC by checking the two following parameters:

• CN Domain indicator IE = PS • The presence of E-UTRA Capability in IE “Inter-RAT UE radio access capability” in “INTER RAT

HANDOVER INFO WITH INTER RAT CAPABILITIES” received in the Source RNC To Target RNC Transparent Container Ranap IE

4.12.2.3 TARGET RESOURCE ALLOCATION IN RNC

Unlike the 2G 3G relocation, several RAB can be received in the the “RAB to be setup list” in the RELOCATION REQUEST message.

UMTS Radio Mobility



The maximum of PS Rab supported simultaneously is 3 by taken into the following combinations. The Multi PS data Rb combination supported are:

• Downlink DCH (PS + PS) / Uplink DCH (PS + PS) • Downlink DCH (PS + PS + PS)/ Uplink DCH (PS + PS + PS) [USA Market] • HS-DSCH (PS + PS) + E-DCH (PS + PS) [Global Market + Korean Market] • HS-DSCH (PS + PS) + Uplink DCH (PS+PS) • HS-DSCH (PS + PS + PS) + Uplink DCH (PS+PS+PS) [USA Market]

The PS services type combination may be: • PS streaming + PS I/B signalling + PS I/B • PS I/B signalling + PS I/B • PS I/B + PS I/B • PS streaming + PS I/B • PS I/B + PS I/B + PS I/B

The target resource allocation algorithm in target RNC for incoming calls from 4G takes into account the following limitations:

• Due to the RELOCATION REQUEST message structure, there is only one target cell to be considered by the target RNC

Besides, in this version: The resource allocation for incoming relocation from 4G follows the same algorithm as for initial call setup resource allocation, i.e. there is no pool of reserved capacity for incoming relocation from 4G. Based on RAB parameters requested by the Core Network, the RNC will choose a Radio Bearer configuration among the ones which are supported in this version. In this case, the algorithm for RAB to RB mapping is the same as used for call initiation.

4.12.2.4 CIPHERING

The necessary information is passed from the source eNodeB to the target RNC using the HANDOVER REQUIRED / RELOCATION REQUEST messages so that there is no break in the ciphering:

• Mobile supported ciphering algorithm are provided to the mobile in the “RRC container” • START-PS (used to initialise the 20 MSBs of all hyper frame numbers: MAC-d HFN, RLC UM HFN,

RLC AM HFN, RRC HFN) is provided in the “RRC container” CK (UMTS ciphering Key) is provided by the MME in the RELOCATION REQUEST (“Encryption information “ IE), resulting from the conversion of KASME (LTE ciphering key) by the MME. Ciphering is started by the mobile immediately after receiving the HANDOVER TO UTRAN COMMAND message.

4.12.2.5 INTEGRITY

Integrity is started by the RNC immediately after receiving the HANDOVER TO UTRAN COMPLETE RRC message. The necessary information is passed from the source eNb to the target RNC using the HANDOVER REQUIRED / RELOCATION REQUEST messages so that there is no break in the ciphering:

• Mobile supported integrity algorithm are provided to the mobile in the “RRC container” • START-PS (used to initialise the 20 MSBs of all hyper frame numbers: MAC-d HFN, RLC UM HFN,

RLC AM HFN, RRC HFN) is provided in the “RRC container” IK (UMTS Integrity Key) is provided by the MME in the Relocation Request (“Integrity protection information“ IE), resulting from the conversion of Kc (LTE ciphering key) by the MME.

UMTS Radio Mobility



UE RNC


NodeB



4.12.2.6 DEPENDENCIES WITH LTE

For this procedure to be working correctly, it is mandatory the MME supports translation from EPS bearer to PDP contexts supported by SGSN and UTRAN.


4.12.3.1 RELOCATION REJECTED BY TARGET RNC

If the relocation preparation phase fails, a relocation failure is sent from RNC to the SGSN.

S1/ Handover preparation failure

S1/ Handover Required (Source RNC to target RNC transparent information)

UE RNC MME eNB

RANAP/ Relocation failure

SGSN


NodeB

GTP/ Forward Relocation request (Handover Required)

GTP/ Forward Relocation failure



Figure 41: 4G to 3G handover preparation failure case

4.12.4 PARAMETERS

The parameters are:

Name Object/Class Definition isEutraToUtraHhoAllowed RadioAccessService

Class3 This parameter indicates whether the 4G To 3G PS Handover is allowed within the RNC YES: incoming relocation request from 4G are processed

UMTS Radio Mobility



NO: incoming relocation requests from 4G are rejected

FromEutraRelocationCiphering RadioAccessService Class3

This parameter is used to indicate if ciphering is allowed during SRNS relocation from LTE within the RNC. If the value is cipheringDisabledRejected the ciphering is not allowed and the relocation procedure is rejected If the value is cipheringDisabledIgnore the ciphering is not allowed and the relocation procedure continue normally If the value is cipheringEnabled the ciphering is allowed and the relocation procedure continue normally. Enum( cipheringDisabledRejected, cipheringDisabledIgnore, cipheringEnabled)


• support for incoming relocation procedures (involving SCCP connections initiated by the CN) • ability to format the HANDOVER TO UTRAN message (as defined in the RRC specification) • start of security procedure (ciphering & integrity) at the end of the handover execution at RRC level


• Support of the Gn Interfaces: SGSN–MME and SGSN-P_GW.

4.12.7 CS FALLBACK

An UE camping on E-UTRA may be moved by the eNB by using the following procedures:

1. UE connection release by requesting the UE to select a UTRA network;

2. UE connection release by requesting the UE to access a given Fdd cell (selected in blind mode or with measurements);

3. SRNS relocation from E-UTRA to UTRA followed by a CS Rab Assignment.

These procedures have no impact on the UTRA. A specific Ranap cause is created in Ranap Rel8 “CS fallback triggered”. In UA07.1.2, as the Iu is based on Rel 7, this cause value should not be received. MME will map S1AP "CSFB Triggered" to the RANAP "Relocation Triggered. As the RNC does not know the relocation cause “CS fallback triggered’, it has no way to improve the CS establishment by postponing some procedures.

The CS fallback data flows are described in [A9].

UMTS Radio Mobility



4.13. INTER-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR

4.13.1 DESCRIPTION

4.13.1.1 GENERAL

The purpose of this mobility case is to allow user mobility between cells of different frequency, being controlled by different RNC not connected to an Iur. This may be used, e.g. in the 2 following cases:

• inter-PLMN mobility • intra-PLMN mobility between 2 frequency layers

In the example below, the mobile is using 2 radio links from NodeB0 and NodeB1, controlled by the SRNC. At some point, the SRNC decides to hand the UE over another cell controlled by another RNC and using another frequency (f2).

RNC

NodeB 0

UE

Iub

Target radio link

f2

SRNC

Iu

NodeB 1

f1

NodeB 2

MSC MSC

Figure 42: inter-frequency inter-RNC handover

As described in the following flow diagram, inter-frequency inter-RNC hard handover makes use of the Relocation procedure (UE involved), as the UTRAN RRC connection anchor point is moved from one RNC to another. The global process is divided into two phases:

• The relocation preparation in which all the needed resources are allocated in the target RNC and NodeB • The relocation execution in which the mobile is handed over the new resource

Relocation preparation

UMTS Radio Mobility



CS CN node Serving RNC Target RNC UE

RANAP/ Relocation required (RB parameters,Number of Iu instances)

RANAP/ Relocation request ack (Radio Bearer Reconfiguration)

Serving NodeB Target NodeB



RANAP/ Relocation request (RB parameters,Number of Iu instances,

RAB parameters)

Based on the inter-PLMN handover criteria, a request for relocation is issue by the serving RNC. When accepted, this request triggers resource allocation within the target RNC:

• A radio link is allocated in the target NodeB • An AAL2 circuits are allocated on Iub and Iu interfaces



AAL2/ ERQ

AAL2/ ECF

On reception of Relocation Request, the target RNC allocates UTRAN resources corresponding to the requested RABs

Figure 43: inter-frequency inter-RNC handover - relocation preparation

UMTS Radio Mobility



Relocation execution

CN node Serving RNC Target RNC UE



Serving NodeB Target NodeB

RANAP/ Relocation command (Radio Bearer Reconfiguration)

RANAP/ Relocation complete



RANAP/ Relocation detect

RRC/ Radio Bearer reconfiguration (RB to reconfigure,

Physical channel configuration)

RRC/ Radio Bearer reconfiguration complete

During the relocation execution phase, a new RNTI is allocated to the mobile, integrity (and possibly) ciphering are activated. This is all done through the Radio Bearer Reconfiguration RRC procedure.

RRC/ Measurement Control (id1, Release)

AAL2 / REL

AAL2 / RLC

Once the mobile is successfully established on the target resource, the anchor MSC triggers a release of all UTRAN resources used under the old serving RNC

SCCP/ Released

RRC/ Measurement Control (id2, Release)

…

RRC/ Measurement Control (id1, Setup)

RRC/ Measurement Control (id2, Setup)

…

Old measurement Ids are released, and new measurements are setup by the new SRNC.

SCCP/ Release Complete

Figure 44: inter-frequency inter-RNC handover - relocation execution Remarks:

• From the RELOCATION REQUEST messages received, the Alcatel-Lucent target RNC tries to identify the Radio Bearer configuration which is the closest to the requested configuration. In case there is no matching configuration (i.e. there is no configuration in the target RNC that matches the number and type of radio bearer in the existing configuration managed by the serving RNC) then the relocation is failed and a RELOCATION FAILURE is sent back to the Core Network.

• Regarding measurement configuration, the Alcatel-Lucent target RNC deletes every measurement configured previously in the source RNC once relocation is successfully performed. All the needed measurements are then setup.

UMTS Radio Mobility




In this version, outgoing inter-frequency handover inter-RNC is triggered upon iMCTA decision (refer to section 4.19). The feature is applicable for calls on DCH, HS-DSCH or E-DCH, with check of global activation parameters isHsdpaHHOwithMeasAllowed and isEdchHHOwithMeasAllowed. This algorithm is applicable to PS, CS and CS+PS connections.

4.13.3 ALGORITHM






In this version of the document, the target cell choice decision is based on inter-frequency measurements from the mobile, possibly using compressed mode. There is no support for blind handover, meaning that a target cell for inter-frequency handover as described in this section has to be a cell reported by the mobile, and this cell has to fulfill the process described in section 4.19.


In case the inter-frequency handover is not successful (e.g. the mobile fails to synchronise on the target cell) there is no second try or other try to a second best eligible cell. In case of CS+PS handover, if the handover fails for one of the domains, the handover is aborted.

4.13.5 PARAMETERS

Name Object/Class Definition is3Gto3GWithoutIurAllowedForPS RadioAccessService

Class3 YES: incoming or out-going inter-frequency alarm handover is allowed for PS domain RAB NO: incoming or out-going inter-frequency alarm handover is not allowed

is3Gto3GWithoutIurAllowedForCS RadioAccessService Class3

YES: incoming or out-going inter-frequency alarm handover is allowed for CS domain RAB NO: incoming or out-going inter-frequency alarm handover is not allowed

Refer also to

� Section 4.19.

UMTS Radio Mobility



� Section 6.6.


• Support for out-going/incoming relocation to/from 3G for PS, CS and CS+PS services • Support of inter-frequency compressed mode scheme • Support for inter-frequency measurements


• Support for the relocation procedure in PS and CS domain

4.14. INTRA-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR

4.14.1 DESCRIPTION

This feature introduces the capability to detect the need to hard handover a call from one cell to another cell of the same frequency, but controlled by a different RNC without Iur. When all the conditions are met, the existing outgoing and incoming relocation procedures (UE involved) are invoked to execute the HHO. It may be used e.g. in following situations:

• Two different operators (PLMN) are using the same frequency in the same geographical area, and they have set up national roaming agreements between them

• In a single PLMN, where it’s not possible to communicate via Iur between two RNCs controlling cells of the same frequency, e.g. for IOT reasons between two RNCs from different manufacturers.

• The Iur interface provisioned between 2 RNCs is not in an operational state. Once the intra-frequency inter-RNC HHO condition is met, the procedure is exactly the same as for an inter-freq inter-RNC HHO (refer to § 4.13.1 for detailed description).


The feature is applicable for calls on DCH, HS-DSCH or E-DCH, with check of global activation parameters isHsdpaHHOwithMeasAllowed and isEdchHHOwithMeasAllowed. It is applicable to all RABs combinations. It is applicable in full-event mode only. The application of this feature should be limited to the situations where there is no Iur between 2 RNCs and is not recommended as a general mobility mechanism.

4.14.3 ALGORITHM

4.14.3.1 IUR INTERFACE STATUS

The Iur interface can be unavailable for following reasons: • The interface is not provisioned at system start up • The Iur interface status is not operational as notified to the Fault manager and to the user applications.

This status is checked only when receiving measurement reports and its change does not affect measurement configuration.

UMTS Radio Mobility



4.14.3.2 MEASUREMENT CONFIGURATION

In order to separate SHO from HHO conditions, a new intra-frequency measurement is introduced. It configures event1A with measId = 16 and contains all isolated cells (cells in the monitored set that are controlled by another RNC and have no Iur interface provisioned with the serving RNC). It is configured with specific parameters (refer to § 4.14.4). CIO is used. If needed, it is configured at the same time as other events 1x with measId = 1.

4.14.3.3 HO DECISION

4.14.3.3.1 RECEPTION OF MEASUREMENT REPORT MEASID 1

On receipt of a measurement report with measId = 1 to add a cell from a neighbouring RNC in the monitored set, and if the Iur interface is disabled, a SHO cannot occur. In that case, if all activation parameters allow it, following check is done:

If the cell to add has a better Ec/N0 than other cells of the set and its Ec/N0 and RSCP are greater than a minimumCipchEcNoValueForHho and minimumCipchRscpValueForHho respectively, then a HHO with this target cell is decided. Otherwise, no handover (neither HHO or SHO) is attempted.

4.14.3.3.2 RECEPTION OF MEASUREMENT REPORT MEASID 16

On receipt of a measurement report with measId = 16 to add a cell from an isolated neighbouring RNC in the monitored set, a SHO cannot occur. In that case, if all activation parameters allow it, following check is done:

If the cell to add has a better Ec/N0 than other cells of the set and its Ec/N0 and RSCP are greater than a minimumCipchEcNoValueForHho and minimumCipchRscpValueForHho respectively, then a HHO with this target cell is decided. Otherwise, no handover (neither HHO or SHO) is attempted.

4.14.4 PARAMETERS

Name Object/Class Definition isIntraFreqInterRncHhoOnIurLinkDownAllowed


Indicates if the intra-frequency inter-RNC HHO is allowed if Iur Link is down

isIntraFreqInterRncHHOAllowed RadioAccessService Class3

indicates if the intra-frequency inter-RNC HHO feature is enabled or disabled

minimumCpichEcNoValueForHHO

IntraFreqTargetCellParams (DlUserService) Class 3

CPICH Ec/No threshold for intra-frequency cell eligibility in HHO case

minimumCpichRscpValueForHHO

IntraFreqTargetCellParams (DlUserService) Class 3

CPICH Rscp threshold for intra-frequency cell eligibility in HHO case

amountRep FullEventRepCritHhoMgtEvent1AWithoutIur (MeasurementConfCl

Amount of periodical reporting when triggered by intraFreq-interRnc Event in Full Event Mode

UMTS Radio Mobility



ass) Class 3

repInterval FullEventRepCritHhoMgtEvent1AWithoutIur (MeasurementConfClass) Class 3

Interval between 2 similar reports for amount reporting mgmt of intraFreq-interRnc Event in Full Event Mode

maxNbReportedCells FullEventRepCritHhoMgtEvent1AWithoutIur (MeasurementConfClass) Class 3

Maximum number of reported cells to configure in Reporting Cell Status for intraFreq-interRnc Event in Full Event Mode

timeToTrigger FullEventHoConfHhoMgtEvent1AWithoutIur (UsHoConf) Class 3

Period during which the condition of the intraFreq-interRnc Event must be satisfied before sending a measurement report in Full Event Mode

hysteresis FullEventHoConfHhoMgtEvent1AWithoutIur (UsHoConf) Class 3

Hysteresis to configure for the triggering condition of intraFreq-interRnc Event in Full Event Mode. It is related to the conditions for the change of Primary Radio Link

cpichEcNoReportingRange FullEventHoConfHhoMgtEvent1AWithoutIur (UsHoConf) Class 3

Reporting Range to configure for the triggering condition of the intraFreq-interRnc Event in Full Event Mode

4.14.5 ACCESS NETWORK IMPACT

Refer to § 4.13.6.

4.14.6 CORE NETWORK IMPACT

Refer to § 4.13.7.

4.15. INTER-FREQUENCY INTRA-RNC HANDOVER

4.15.1 DESCRIPTION

4.15.1.1 GENERAL

This mobility case applies to Multilayer deployment in a single operator.

f1

f2

RNC

UMTS Radio Mobility



Figure 45: Hard Handover inter-frequency intra-RNC

In this case, the RNC control cells from different frequencies (f1 and f2); f1 and f2 cells may be either 2 sectors of the same NodeB, or belong to different NodeB. The 2 frequency layers overlap and the subscribers may camp on either of the 2 layers depending on cell selection and re-selection rules and parameters. Once connected, the subscribers remain on same frequency. However, as UE are moving out of the smallest frequency spot (f1 as in the picture above), an alarm hard handover towards the other frequency is triggered by the SRNC. Similarly, an inter-frequency intra-RNC hard handover may also be performed from f2 to f1 in case of lack of f2 coverage, e.g. as in an “outdoor to indoor” mobility case.


RRC/ Radio Bearer Reconfiguration

RRC/ Radio Bearer Reconfiguration complete

NBAP/ Radio Link Setup req

NBAP/ Radio Link Setup resp


1

2

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)



NodeB 0

Figure 46: Hard Handover inter-frequency intra-RNC dataflow

In the first step, a new radio link is set up on the new target NodeB, using another frequency. In the second step, the Radio Bearer is re-configured and the old radio links (there may be more than one, depending on the current active set) are deleted. In the figure above, NodeB 0 and NodeB 1 may be the same network node.

4.15.1.2 OVER THE IUR

The source and/or target cell may be controlled by another RNC, as in the figure below.

f1

f2

SRNC DRNC

Figure 47: Hard Handover inter-frequency intra-RNC – over the Iur

In such a case, the Radio Link Addition, Setup or Deletion is performed over the Iur interface

UMTS Radio Mobility



Serving RNC UE Drift NodeB1 Drift RNC


RRC/ Radio Bearer Reconfiguration Complete

RNSAP/ Radio Link Addition req

RNSAP/ Radio Link Addition resp (Binding Id)




1

2

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)

AlCAP Iur Transport Bearer Setup

AlCAP Iub Transport Bearer Setup






AlCAP Iub Transport Bearer Release

AlCAP Iur Transport Bearer Release

3

Figure 48: Hard Handover inter-frequency intra-RNC dataflow – over the Iur

In step (1) a new radio link is set up over Iur on the new target Drift NodeB, using another frequency. In step (2) the Radio Bearer is reconfigured. In step (3) the old radio links (there may be more than one, depending on the current active set) are deleted. The radio link belonging to the previous primary cell is to be deleted over Iur as depicted in figure above. In the figure above, Drift NodeB 0 and Drift NodeB 1 may be the same network node.

UMTS Radio Mobility




In this version, inter-frequency hard handover intra-RNC is triggered upon iMCTA decision (refer to section 4.19). This algorithm is applicable to PS, CS and CS+PS connections. The RNSAP RL Addition procedure does not permit to reconfigure the DCH part of the call. This procedure is used in case we establish a radio link on a drift RNC (over Iur) while we have already one or more radio-links established on this D-RNC. The following restriction applies:

In case the target cell is located on a D-RNC, the mobility procedure depends on the parameter isInterFreqHandoverOverIurAllowed: If the parameter isInterFreqHandoverOverIurAllowed is false, the RNC will process a SRNS Relocation "UE involved". If the parameter isInterFreqHandoverOverIurAllowed is true, the RNC will process a HHO through Iur after processing a reconfiguration towards DCH in case the call was established in HSPA.

4.15.3 ALGORITHM





4.15.3.3 CHOICE OF TARGET CELL



In case the inter-frequency handover is not successful (e.g. the mobile fails to synchronise on the target cell) there is no second try or other try to a second best eligible cell. However for intra DRNC handover a relocation procedure (refer to section 4.13) will be initiated towards the same target cell if the relocation is enabled according to section 4.13.5 (is3Gto3GWithoutIurAllowedForPS and is3Gto3GWithoutIurAllowedForCS)..

4.15.5 PARAMETERS

Intra DRNC handover will be enabled/disabled by the parameter defined in section 4.16.5 (isInterFreqHandoverOverIurAllowed). There is no new parameter associated to the “intra-RNC case” exclusively. The Radio criteria algorithm for inter-frequency intra-RNC handover uses the same parameters with the same values as in the inter-RNC case.

UMTS Radio Mobility




• Support of inter-frequency compressed mode scheme • Support for inter-frequency measurements




The following counters are defined:

• HHO.AttOutInterFreq / HHO.AttOutInterFreq.NeighbRnc Total number of attempted outgoing inter-frequency hard handovers

• HHO.AttOutInterFreq.RSCP / HHO.AttOutInterFreq.RSCP .NeighbRnc Attempted outgoing inter-frequency hard handovers due to insufficient RSCP quality of the used frequency

• HHO.AttOutInterFreq.EcNo / HHO.AttOutInterFreq.EcNo .NeighbRnc Attempted outgoing inter-frequency hard handovers due to insufficient Ec/No quality of the used frequency

• HHO.SuccOutInterFreq / HHO.SuccOutInterFreq.NeighbRnc Total number of successful outgoing inter-frequency hard handovers

• HHO.SuccOutInterFreq.RSCP / HHO.SuccOutInterFreq.RSCP.NeighbRnc Successful outgoing inter-frequency hard handovers due to insufficient RSCP quality of the used frequency

• HHO.SuccOutInterFreq.EcNo / HHO.SuccOutInterFreq.EcNo.NeighbRnc Successful outgoing inter-frequency hard handovers due to insufficient Ec/No quality of the used frequency

The counters are of cumulative type. They are defined as two sets – one set on per FDDCell basis (the Primary RL of the UE is on this FDDCell) and one set on per neighboring RNC basis (the Primary RL of the UE is on this Neighboring RNC): In context of intra RNC handover

• the counters on per FDDCell basis will be pegged if the handover is performed within the SRNC • the counters on per neighboring RNC basis will be pegged if the handover is performed within a

neighboring RNC in DRNC role.

4.16. INTER-FREQUENCY INTER-RNC HANDOVER WITH IUR AND MEASUREMENTS

In release UA05, Iur is not used for that type of handover. We use SRNS Relocation “UE involved” instead (refer to § 4.13). – In UA07, Inter-frequency handover over Iur is reintroduced in order to avoid interoperability issues which may occur in case of SRNS Relocation with other vendor’s RNCs. SRNS Relocation “UE involved “ is still used if handover over Iur is disabled towards the target DRNC or as fallback option in case of the handover attempt over Iur having been unsuccessful.

UMTS Radio Mobility



4.16.1 DESCRIPTION

4.16.1.1 GENERAL

The purpose of this mobility case is to allow user mobility between cells of different frequencies (f1 and f2) being controlled by different RNCs connected to an Iur. Depending on the allocation of the source cell on f1 (primary cell of the current active set) and the target cell on f2 the inter-frequency inter RNC hard handover is to be performed

• from SRNC to DRNC • from DRNC to DRNC • from DRNC to SRNC

as detailed below.

4.16.1.2 FROM SRNC TO DRNC

This scenario is characterized by the primary cell on f1 being controlled by the SRNC and the target cell on f2 cell being controlled by a DRNC. If the call is HSxPA then it needs to be reconfigured to DCH before the handover because direct handover from HSxPA to HSxPA is not supported towards a DRNC.

f1

f2

SRNC DRNC

Figure 49: Hard Handover inter-frequency inter-RNC – from SRNC to DRNC

UMTS Radio Mobility






RNSAP/ Radio Link Setup req

RNSAP/ Radio Link Setup resp (Binding Id)




1

2

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)



UE NodeB0 Serving RNC




3

Figure 50: Hard Handover inter-frequency inter-RNC data flow – from SRNC to DRNC

In step (1) a new radio link is set up over Iur on the new target Drift NodeB, using another frequency. In step (2) the Radio Bearer is reconfigured. In step (3) the old radio links (there may be more than one, depending on the current active set) are deleted. The radio link belonging to the previous primary cell is to be deleted directly over Iub without Iur being involved as depicted in figure above.

4.16.1.3 FROM DRNC TO DRNC

This scenario is characterized by the primary cell on f1 being controlled by a DRNC and the target cell on f2 being controlled by another DRNC while the SRNC remains the same. If the call is HSxPA then it needs to be reconfigured to DCH before the handover because direct handover from HSxPA to HSxPA is not supported towards a DRNC.

UMTS Radio Mobility



f1

f2

SRNC DRNC 2

DRNC 1

Figure 51: Hard Handover inter-frequency inter-RNC – from DRNC to DRNC

Serving RNC UE Drift NodeB1 Drift RNC 2



RNSAP/ Radio Link Setup req

RNSAP/ Radio Link Setup resp (Binding Id)




1

2

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)



Serving RNC UE Drift NodeB0 Drift RNC 1







3

Figure 52: Hard Handover inter-frequency inter-RNC data flow – from DRNC to DRNC

In step (1) a new radio link is set up over Iur on the new target Drift NodeB, using another frequency.

UMTS Radio Mobility



In step (2) the Radio Bearer is reconfigured. In step (3) the old radio links (there may be more than one, depending on the current active set) are deleted. The radio link belonging to the previous primary cell is to be deleted over Iur as depicted in figure above.

4.16.1.4 FROM DRNC TO SRNC

This scenario is characterized by the primary cell on f1 being controlled by a DRNC and the target cell on f2 cell being controlled by the SRNC. If the call is HSxPA then it can be handed over directly with HSxPA being kept. There is no need for HSxPA to DCH reconfiguration.

f1

f2

SRNC DRNC

Figure 53: Hard Handover inter-frequency inter-RNC – from DRNC to SRNC



RRC/ Radio Bearer Reconfiguration complete

NBAP/ Radio Link Setup req

NBAP/ Radio Link Setup resp


1

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)


2

Drift RNC

UMTS Radio Mobility










3

Figure 54: Hard Handover inter-frequency inter-RNC data flow – from DRNC to SRNC

In step (1) a new radio link is set up on the new target NodeB, using another frequency. This radio link is to be setup directly over Iub without Iur being involved. In step (2) the Radio Bearer is reconfigured. In step (3) the old radio links (there may be more than one, depending on the current active set) are deleted. The radio link belonging to the previous primary cell is to be deleted over Iur as depicted in figure above.


In this version, inter-frequency hard handover inter-RNC is triggered upon iMCTA decision (refer to section 4.19). This algorithm is applicable to PS, CS and CS+PS connections. When the target cell is on D-RNC, whatever the location of the current active set, the mobility procedure depends of the isInterFreqHandoverOverIurAllowed parameter value: If the parameter isInterFreqHandoverOverIurAllowed is false, the RNC will process a SRNS Relocation "UE involved". If the parameter isInterFreqHandoverOverIurAllowed is true, the RNC will process a HHO through Iur after processing a reconfiguration towards DCH in case the call was established in HSPA (refer to section 4.15.2).

4.16.3 ALGORITHM





UMTS Radio Mobility



4.16.3.3 CHOICE OF TARGET CELL



In case the inter-frequency handover is not successful (e.g. the mobile fails to synchronise on the target cell) there is no second try or other try to a second best eligible cell. However if the target cell is on a DRNC (i.e. handover from SRNC to DRNC or handover from DRNC to DRNC) a relocation procedure (refer to section 4.13) will be initiated towards the same target cell if enabled according to section 4.13.5.

4.16.5 PARAMETERS

Name Object/Class Definition isInterFreqHandoverOverIurAllowed

Neighbouring RNC Indicates if inter-frequency HHO over Iur is allowed. Used for both intra and inter RNC HHO.


• Support of inter-frequency compressed mode scheme • Support for inter-frequency measurements




The counters listed in section 4.15.8 do apply for the inter RNC scenarios as well. In context of inter RNC handover

• the counters on per FDDCell basis will be pegged if the handover is performed from the SRNC to a DRNC

• the counters on per neighboring RNC basis will be pegged if the handover is performed from this neighboring RNC in DRNC role to another DRNC or to the SRNC

4.17. SRNS RELOCATION – “UE NOT INVOLVED”

Warning: SRNS Relocation “UE not involved” can be rejected when UA7.1 SRNC is sending r7 RRC extensions which are not handled by the UA6 TRNC. The relocation is rejected and the call stays up.

4.17.1 DESCRIPTION

See [R8].

UMTS Radio Mobility




See [R8].

4.17.3 ALGORITHM

See [R8].

4.17.4 PARAMETERS

See [R8].


See [R8].


See [R8].

4.18. REDIRECTION FEATURES FOR TRAFFIC SEGMENTATION

A redirection may be triggered upon a RRC Connection Request receipt without attempting to allocate resource on the current Fdd layer. Before calling redirection features the overload function is processed. If overload criterion is fulfilled (=rach is filtered before attempting CAC) no redirection applies. The following features may trigger a redirection:

• HSPA traffic segmentation (feature 27932) and its evolution redirection during RRC connection setup (75069/81213).

• 3G2G redirection for speech call (feature 13451) • 3G2G redirection for emergency call (feature 25145) • 3G2G redirection based on cell load (feature 34480) • Pre-emption process for DCH and HSDPA/HSUPA (feature 33322)

These features are described in following sections.

4.18.1 REDIRECTION AT CONNECTION SETUP (IMCRA STEP 1)

4.18.1.1 DESCRIPTION

Mobiles in idle mode will select a layer according to radio conditions. The cell selection/reselection algorithm is not governed by HSDPA availability so it is not possible to guarantee that an HSDPA mobile will select the HSDPA layer (and vice versa a non-HSDPA mobile will select the non-HSDPA layer).

UMTS Radio Mobility



Figure 55: Example of Redirection at RRC establishment

SGSN Node B – twin cell RNC UE

RRC/ RACH / RRC connection Request

(cause)

RRC/ FACH / RRC Connection Setup (DCCH, U-RNTI,

RRC state = CELL_DCH,

Primary CPICH info = f2 cell

Frequency info = twin cell frequency)


The RRC Connection Setup message contains the signalling bearers (DCCH) definition. The Primary CPICH info corresponds to the CPICH of the twin cell (frequency f2)

The RRC Connection Request message is received on cell A (frequency f1)

NBAP/ RL Setup Request)

NBAP / RL Setup Response

The radio-link is setup on the twin cell (f2) of cell A (f1) No resources are allocated on cell A

The response is received on the twin cell (f2)

Figure 56: redirection from f1 to f2 with establishment done in Cell_DCH

For establishment in Cell_FACH, the dataflow is the same as without redirection, except that resources are reserved in the twin-cell and that the mobile is redirected thanks to the frequency info IE.

SGSN Node B RNC UE


(cause)


RRC state = CELL_FACH, frequency info=freq f2)


The RRC Connection Request message initiated by the UE contains the establishment cause.


(cause) RRC/ FACH / RRC Connection Setup (DCCH, U-RNTI,

RRC state = CELL_FACH)

The UE is redirected to the other layer (f2).

The RRC connection request is sent again in the new cell, normally in the twin cell but not necessarily.

Figure 57: redirection with establishment done in Cell_FACH

The dataflow consists in making the mobile request again the RRC connection establishment in the frequency of the twin cell. On this second request, the call is established normally. Following description explains the RRC traffic segmentation/redirection during RRC connection setup feature.

f1 : non-HSDPA layer

f2 : HSDPA layer

2. RRC Cnx Setup

(redirection -> f2)

1. RRC Cnx Request

(AS Release Indicator

= R4 or absent)

2. RRC Cnx Setup

(redirection -> f1)

1. RRC Cnx Request (AS

Release Indicator = R5)

UMTS Radio Mobility



4.18.1.2 APPLICABILITY

Mobiles are redirected to the right layer at RRC connection establishment. For example mobiles that are eligible to HSxPA are directed towards the HSxPA layer and the other ones are directed towards the non-HSxPA layer. The RRC redirection procedure uses a list of candidate twin cells (if no twin cell is operational then redirection is not triggered). The RNC determines the HSPA cell capability as follows:

HSPA Cell Capability Cell Configuration

DCH hsdpaActivation = FALSE

HSDPA hsdpaActivation = TRUE

edchActivation = FALSE

HSUPA hsdpaActivation = TRUE

edchActivation = TRUE

Table 2: HSPA Cell Capability For specific network configurations it can be useful to allow several layers to carry HSPA traffic but still to prefer some of the HSPA capable layers for R99 traffic. Especially, this is useful if R99 carriers get unavailable e.g. due to automatic carrier switch-off. If isHspaCellLoadAllowedForImcra = FALSE and if the originating cell as well as all operational cells contained in the twinCellList are either HSDPA or HSUPA capable, i.e. no DCH cell, then the RNC evaluates the FDDCell parameter layerPreferredForR99 of the originating and all operational twin cells. For all cells with layerPreferredForR99 = TRUE the RNC assumes HSPA Cell Capability = DCH. If isHspaCellLoadAllowedForImcra = TRUE then the parameter layerPreferredForR99 has slightly different semantics:

• HSPA load balancing towards this layer is allowed when the all HSPA “pure” layers are loaded. • When the HSPA “R99 preferred” layers are loaded, the HSPA calls are assigned to HSPA “pure” layers

whatever their load. The segmentation is done by the RNC when a mobile tries to establish an RRC connection. The segmentation is done only at the RRC Connection establishment. During the call, redirection is performed by iMCTA.

4.18.1.2.1 INTERACTION WITH CELL_FACH:

If a UE in Always-On on Cell_FACH reselects another layer, it may be redirected to the right layer by iMCTA when traffic resumes.

4.18.1.2.2 INTERACTION WITH FOLLOW-ON / SUBSCRIBED TRAFFIC CLASS:

The mobile may establish a signalling connection to perform a Location Update prior to the establishment of the RAB, using “the follow-on” indicator at the end of the Location Update. In this case, the mobile uses the same RRC connection for the Location Update and the RAB establishment, using the cause ‘Registration’. The establishment cause ‘Registration’ will be set up in the originating cell. For ‘Originating High Priority Signalling’ cause, Although the UE may use it for PS I/B calls according to what has been provisioned by the operator (QoS in Traffic Class set to ‘Subscribed Traffic Class’), the call will also be set up in the originating cell. More information is provided in Annex L of 24.008.

4.18.1.2.3 EMERGENCY CALLS:

Emergency calls are usually not redirected and are served on the layer selected by the mobile to limit the probability of call setup failure. Only in case that the RRC establishment fails on the originating cell due to CAC

UMTS Radio Mobility



failure then the call is redirected to a twin cell if redirection is enabled (parameter rrcRedirectionType has a value unequal to "none" and twin cells are available).

4.18.1.2.4 HSPA LOAD

Since UA07.1.2 the HSDPA load is considered for HSPA I/B calls by iMCRA load based decisions if enabled via parameter isHspaCellLoadAllowedForImcra. HSUPA load is not evaluated in current release. The HSDPA load is calculated from DL power and DL code: Dl power load formula: HSPA_dl_power_load = 1 - HSPA_dl_power_share HSPA_dl_power_share = dl power resource share available for next HSPA without GBR service = dl_load_power_avail_HSPA_wo_GBR_MinBR[ratio] div (nb_current_HSDPA_I_B_services + 1) With:

• nb_current_HSDPA_I_B_services: Number of current HSDPA I/B services • Dl_load_power_avail_HSPA_wo_GBR_MinBR[ratio] =

(max_tx_power_cell – dl_power [R99 + HSDPA GBR]) div max_tx_power_cell • dl_power[R99+HSDPA GBR] = Total Transmitted Carrier Power of all codes not used for HSDPA and

E-DCH + HS-DSCH required power needed to ensure the GBR power. Dl code load formula: HSPA_dl_codes_load = 1 - HSPA_dl_codes_share HSPA_dl_codes_share = dl code resource share available for next HSPA without GBR service = dl_load_codes_avail_HSPA_wo_GBR_MinBR[ratio] div (nb_current_HSDPA_I_B_services + 1) With:

• Dl_load_codes_avail_HSPA_wo_GBR_MinBR[ratio] = (SizeBiggestSf16Pool - TotalHsdpaUsedSF16) / 16

• SizeBiggestSf16Pool: Variable introduced by UA06 feature 33694: The number of free codes in the largest SF16 code block. Note that a code block consists of a number of successive SF16 codes. This is an integer value.

• TotalHsdpaUsedSF16: The minimumnumber of SF16 codes that are allocated in use for HSDPA in one cell calculated based on HSDPA GBR, HSDPA MinBR and HSDPA I/B without MinBR (mib value).

For HSDPA load four load colors are supported: green, yellow, red, black The RNC determines the HSPA downlink load colors from

• HSPA DL Power Color: Calculated ‘HSPA dl power Load’ and the color transitions defined by parameters - green2YellowHSPAPwrDlLoadThreshold - yellow2GreenHSPAPwrDlLoadThreshold - yellow2RedHSPAPwrDlLoadThreshold - red2YellowHSPAPwrDlLoadThreshold - red2BlackHSPAPwrDlLoadThreshold - Black2RedHSPAPwrDlLoadThreshold

• HSPA DL Codes Color: Calculated ‘HSPA dl codes Load’ and the color transitions defined by parameters - green2YellowHSPACodesDlLoadThreshold - yellow2GreenHSPACodesDlLoadThreshold - yellow2RedHSPACodesDlLoadThreshold - red2YellowHSPACodesDlLoadThreshold - red2BlackHSPACodesDlLoadThreshold - Black2RedHSPACodesDlLoadThreshold

• DL HSPA load = max (HSPA DL Power Color, HSPA DL Codes Color)

UMTS Radio Mobility



4.18.1.2.5 INITIAL POWER ON REDIRECTION

Typcially, source and target cell for a redirection are co-located and about the same transmission power is needed in both cells for successful communication between NodeB and UE. If, however, the load in the target cell is higher then the usage of more power may be useful to ensure successful call establishment. Since UA07.1.2 the RNC can calculate the expected power needed in the target cell based on the comparision of source and target cell load if isPinitRrcRedirectionAllowed is set to TRUE. Note: Power is increased if the load in the target is higher than in the originating cell. Power is not reduced if the load in the target is lower than in the originating cell.

4.18.1.3 ALGORITHM

The operator has the choice between five algorithms for target carrier FA (= Frequency Allocation) selection, using parameter rrcRedirectionType:

• UE capability only • UE capability and establishment cause • Preferred FA • CAC • None

The selected FA information will be sent to UE through the RRC connection Setup message.

4.18.1.3.1 REDIRECTION TYPE = UE CAPABILITY ONLY

It is based on the Access Stratum Release Indicator IE present in RRC Connection Request, knowing that R99/R4 mobiles do not support HSDPA. If a R99/R4 mobile sends its connection request in the HSDPA layer, it is redirected to the non-HSPDA layer in the RRC Connection Setup message. If a R5 (or later release) mobile sends its connection request in the non-HSDPA layer, it is redirected to the HSDPA layer. For R5 mobiles the RRC Connection Request does not clearly identify if the mobile is HSDPA capable or not. The RNC assumes that all R5 mobiles are HSDPA capable – see table below.

UE Release

UE capability indication

HSPA UE capability (potential or

real)

Selected Target FA

R99/R4 n/a

>= R6 absent DCH Preferred target FA is DCH cell

R5 n/a

>= R6 HS-DSCH HSDPA Preferred target FA is HSDPA cell

>= R6 HS-DSCH + E-DCH HSUPA Preferred target FA is HSUPA cell

Table 3: UE Capabilities If no twin cell of the selected target FA is available the RNC selects another target FA as per the fallback mechanism defined in Table 4:

UMTS Radio Mobility



Selected Target FA

Fallback if selected target FA is not available

DCH If there is no DCH cell then continue with originating and all twin cells (which will select least loaded cell in 2nd and following steps below)

HSDPA If there is no HSDPA cell then select HSUPA cell. If there is neither HSDPA nor HSUPA cell then select DCH cell.

HSUPA If there is no HSUPA cell then select HSDPA cell. If there is neither HSUPA nor HSDPA cell then select DCH cell.

Table 4: Target FA Fallback

Different iMCRA behaviour applies dependent on whether HSPA load criterion is used or not. RNC selects the target Cell with following procedure if isHspaCellLoadAllowedForImcra = FALSE:

1. Search all cells in the twinCellList and originating cell. Select cells which have compatible cell capability with UE capability or the fallback cells if no compatible cell found.

2. If originating cell is included in the set of selected cells and the originating cell color is better than rrcRedirectOrigCellColourThreshold then the call is established in the originating cell. If the originating cell color is equal or worse then go to next step.

3. If more than one cell is selected then select the cells with lowest cell color (Green < Yellow < Red).

4. If more than one cell is selected: If the originating cell is one of the target cells then the UE should remain in originating cell. Else, from the remaining cells of the twinCellList the target cell is selected with round robin mechanism.

RNC selects the target Cell with following procedure if isHspaCellLoadAllowedForImcra = TRUE:

1. Select the applicable cells for redirection from the originating cell and its twin cells as per Table 5. The Call Capability is the same as the UE Capability for this option.

Call Capability # Cell Capability

DCH HSPA (HSDPA or HSUPA)

1 DCH Select 1 if neither 2, 3, 4 nor 5

available

2 Unloaded “R99 preferred”

Select 2 if 4 not available

3 Loaded “R99 preferred”

Select 1, 2 and 3

Select 3 if neither 2, 4 nor 5 available

4 Unloaded “pure” HSPA

Select 4

5 Loaded “pure” HSPA

Select 4 and 5 if neither 1, 2 nor 3

available Select 5 if neither 2 nor 4 available

Table 5: Applicable Cells With

• An “R99 preferred” cell is loaded if o DCH load > twinCellTargetCellColourThreshold, or o DL HSPA load > twinCellTargetHspaCellLoadThreshold

• A “pure” HSPA cell is loaded if o DL HSPA load > twinCellTargetHspaCellLoadThreshold

Note: The uplink load is ignored.

UMTS Radio Mobility



2. If for a HSPA call more than one cell with HSPA capability is selected then select the cells that fit best to the Call capability as per Table 6. The “R99 preferred” configuration is ignored because it was taken into account by step 1 already.

Call Capability

1st Choice 2nd Choice

HSDPA HSDPA HSUPA

HSUPA HSUPA HSDPA

Table 6: Best fit Capability Table 7 defines the target capability dependent on Call and cell capability:

Call Capability

Cell Capability

Target Capability

DCH <any>

<any> DCH DCH

HSDPA HSDPA

HSDPA HSUPA

HSUPA HSDPA

HSDPA

HSUPA HSUPA HSUPA

Table 7: Target Capability

3. If the originating cell is included in the set of selected cells and the originating cell color is better than the originating threshold then the call is established in the originating cell – see Table 8. If the originating cell color is equal or worse then go to next step. The originating threshold is dependent on the target capability (note: “R99 preferred” configuration is ignored here). For streaming calls (RRC establishment cause is ‘Originating Streaming Call’ or ‘Terminating Streaming Call’) the DCH load criterion is applied independent of Target Capability.

Target Capability

Load Criterion for Establishment on Originating Cell

DCH

or streaming call DCH load < rrcRedirectOrigCellColourThreshold

HSPDA

HSUPA

DL HSPA load < rrcRedirectOrigHspaCellLoadThreshold and

UL DCH load < rrcRedirectOrigCellColourThreshold Table 8: Load Criterion for Establishment on Originating Cell

4. If more than one cell is selected then select the cells with lowest cell color as per Table 9. For streaming calls the DCH load criterion and for other calls the load criterion as per Target Capability is applied.

Target Capability Load Comparison

DCH

or streaming call Select cells with lowest combined UL and DL DCH load

HSPDA

HSUPA

1st step: Select cells with lowest DL HSPA load

2nd step: Select cells with lowest UL DCH load Table 9: Load Comparison

UMTS Radio Mobility




4.18.1.3.2 REDIRECTION TYPE = UE CAPABILITY AND ESTABLISHMENT CAUSE

It is possible to use the traffic class –derived from the Establishment Cause IE- as a second criterion for filtering, knowing that only Interactive, Background and Streaming traffic classes are mapped on HSDPA, so Conversational traffic class is redirected to the non-HSDPA layer. This criterion is optional because this traffic class is not necessarily representative of the services that will be actually used during the life of the RRC connection (a user may start with a service and then establish other services).

Following table gives the call type according to the establishment cause:

Call Type RRC Establishment Cause

Conversational Originating Conversational Call Terminating Conversational Call

Data Originating Interactive Call Originating Background Call Originating Streaming Call Terminating Interactive Call Terminating Background Call Terminating Streaming Call Originating High Priority Signaling Registration Originating Subscribed Traffic Call

Other Other causes

Table 10: RRC Establishment Causes

Then, the preferred FA is chosen using both criteria:

HSPA UE capability (potential or

real)

Call Type by Establishment Cause

Call Capability

Conversational Data

DCH cell DCH

Other Originating cell

Conversational DCH cell

Data HSDPA cell HSDPA


Conversational DCH cell

Data HSUPA cell HSUPA


Table 11: UE Capabilities and Establishment Cause

If no twin cell of the selected target FA is available the RNC selects another target FA as per the fallback mechanism defined in Table 4. RNC selects the target Cell with following procedure:

1. If the Call Capability has been determined to “Originating Cell” as per Table 11 then the call is established on the originating cell.

UMTS Radio Mobility



Otherwise: If isHspaCellLoadAllowedForImcra = TRUE then the RNC follows the procedure for option “UE Capability Only“ where the Call Capability is determined from Table 11 instead of Table 3. Otherwise…

2. Search all cells in the twinCellList and originating cell. Select cells which have compatible cell capability with UE capability and RRC establishment cause or the fallback cells if no compatible cell found.

3. If originating cell is included in the set of selected cells and the originating cell color is better than rrcRedirectOrigCellColourThreshold then the call is established in the originating cell. If the originating cell color is equal or worse then go to next step.

4. If more than one cell is selected then select the cells with lowest cell color (Green < Yellow < Red).


4.18.1.3.3 REDIRECTION TYPE = PREFERRED FA

In case of option "Preferred FA" the RNC selects the target FA based on the Call Type determined from the RRC establishment cause as per Table 10. The UE capabilities are not taken into account. The RNC determines the preferred FAs from the assigned RrcRedirectionConfClass and its contained list of FrequencyAllocation's as per Table 12. Target FAs for that no cell is defined in the twinCellList are ignored.

Call Type Preferred FA

Conversational Select FAs with faType set to 'conversational'. If no 'conversational' FA is available then select FAs of type 'other'. If neither 'conversational' nor 'other' is available select 'data'

Data Select FAs with faType set to 'data'. If no 'data' FA is available then select FAs of type 'other'. If neither 'data' nor 'other' is available select 'conversational'

Other Select every FA given in the referenced RrcRedirectionConfClass

Table 12: Preferred FA If a single FA is selected then the RNC establishes the call in the twin cell of this FA. Otherwise … If isHspaCellLoadAllowedForImcra = TRUE then the RNC follows the procedure for option “UE Capability Only“ from step 3 onwards. Otherwise…

1. If the FA of the originating cell is included in the set of selected FAs and the originating cell color is better than rrcRedirectOrigCellColourThreshold then the call is established in the originating cell. If the originating cell color is equal or worse then go to next step.

2. If more than one FA is selected then select the FAs for which the related twin cell from the twinCellList or the originating cell have lowest cell color (Green < Yellow < Red).

UMTS Radio Mobility



3. If more than one cell/FA has lowest cell color: If the originating cell is one of the target cells then the UE should remain in originating cell. Else, from the remaining cells of the twinCellList the target cell is selected with round robin mechanism.

4.18.1.3.4 REDIRECTION TYPE = CAC

If CAC failure occurred during SRB establishment on the originating cell then the RNC considers redirection to another cell. The RNC selects the cells with lowest cell color from the twinCellList. If more than one cell has lowest cell color: The RNC selects from the remaining cells of the twinCellList the target cell with round robin mechanism. For the load comparision the RNC either uses the DCH load if isHspaCellLoadAllowedForImcra = FALSE or otherwise the load criterion as detailed in Table 9.

4.18.1.3.5 REDIRECTION TYPE = NONE

No traffic segmentation is performed. The call is established on the originating cell if possible.

4.18.1.4 FAILURE CASES:

It may happen that the UE can not synchronise on the new frequency, it will resend an RRC connection request in the same cell (except if it had to perform a cell reselection meanwhile). When receiving this second RRC connection request with the same cause within time T300*N300, then the RNC attempts call establishment in the originating cell. This use case is also applicable to mobiles that do not support RRC redirection.

SGSN Node B RNC UE


(cause)


..)




(cause) RRC/ FACH / RRC Connection Setup (DCCH, U-RNTI,

)

The UE is redirected to the other layer

The UE fails to synchronise on the target layer. The RRC connection request is sent again in the originating cell

The RNC does not try to redirect again and proceeds on this cell

Figure 58: redirection failure

4.18.1.5 PARAMETERS

Redirection during RRC connection setup parameters:

Name Object/Class Definition isRrcRedirectionInterFreq

RadioAccessService Feature activation flag for inter-frequency redirection on RRC connection setup.

rrcRedirectionType InterFreqHhoFddCell The redirection algorithm is configured on cell basis by parameter rrcRedirectionType

UMTS Radio Mobility



twinCellList InterFreqHhoFddCell List of up to 5 inter-frequency twin cells (co-located cells referenced by Cell Id) to which inter-frequency RRC redirection is considered.

rrcRedirectOrigCellColourThreshold InterFreqHhoFddCell If the originating cell and one or more twin cells belong to the FA type for RRC redirection as determined by parameter rrcRedirectionType then the call is kept on the originating cell if its cell colour is below the configured rrcRedirectOrigCellColourThreshold. If the cell color is equal to or above the threshold then RRC redirection to a twin cell is considered.

rrcRedirectOrigHspaCellLoadThreshold UA07.1.2: FDDCell.reserved0 (byte1) bit 2,3

InterFreqHhoFddCell This threshold applies to originating HSPA cell and used by iMCRA as a condition to trigger HSPA cell load balancing: The HSPA cell load has to be higher or equal than this threshold

dlFrequencyNumber FrequencyAllocation (in RrcRedirectionConfClass MO)

Downlink UARFCN

ulFrequencyNumber FrequencyAllocation (in RrcRedirectionConfClass MO)

Uplink UARFCN

faType FrequencyAllocation (in RrcRedirectionConfClass MO)

FA type (conversational, data, other)

layerPreferredForR99 FDDCell Traffic segmentation on RRC establishment can be used to separate R99 and HSPA traffic onto different layers (parameter rrcRedirectionType). For specific network configurations it can be useful to allow several layers to carry HSPA traffic but still to prefer some of the HSPA capable layers for R99 traffic. Especially, this is useful if R99 carriers get unavailable e.g. due to automatic carrier switch-off.

isHspaCellLoadAllowedForImcra UA07.1.2: RadioAccessService.reserved5 (byte0,byte1,byte2,byte3)

RadioAccessService HSPA cell load criteria allowed or not in iMCRA. When allowed there is a dependency with several sub functions activations: NBAP measurements configuration, HSPA services number calculation, HSPA cell load indicator calculation and broadcasting.

isPinitRrcRedirectionAllowed UA07.1.2: RadioAccessService.reserved1 (byte2) bit 0

RadioAccessService Activation/deactivation of the use of the Pinit based on the ratio between Total Transmitted power used on originating cell and target cells. It applies during RRC redirection procedure.

UMTS Radio Mobility



twinCellTargetHspaCellLoadthreshold UA07.1.2: FDDCell.reserved1 (byte1) bit 2,3

FDDCell iMCRA considers an HSPA cell as overloaded if the HSPA load is greater than this threshold. If all HSPA cells are overloaded then R99 preferred cells are considered for HSPA calls. See also parameter layerPreferredForR99.

twinCellTargetCellColourThreshold UA07.1.2: FDDCell.reserved1 (byte1) bit 4,5

FDDCell iMCRA considers an R99 preferred FDD twin cell as overloaded if the R99 load is greater than this threshold.

green2YellowHspaPwrDlLoadThreshold UA07.1.2: FDDCell.reserved1 (byte2) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink power cell load to transition from green to yellow. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

yellow2GreenHspaPwrDlLoadThreshold UA07.1.2: FDDCell.reserved1 (byte3) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink power cell load to transition from yellow to green. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

yellow2RedHspaPwrDlLoadThreshold UA07.1.2: FDDCell.reserved2 (byte0) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink power cell load to transition from yellow to red. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

red2YellowHspaPwrDlLoadThreshold UA07.1.2: FDDCell.reserved2 (byte1) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink power cell load to transition from red to yellow. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

red2BlackHspaPwrDlLoadThreshold UA07.1.2: FDDCell.reserved2 (byte2) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink power cell load to transition from red to black. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

UMTS Radio Mobility



black2RedHspaPwrDlLoadThreshold UA07.1.2: FDDCell.reserved2 (byte3) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink power cell load to transition from black to red. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

green2YellowHspaCodesDlLoadThresho ld UA07.1.2: FDDCell.reserved0 (byte2) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink codes cell load to transition from green to yellow. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

yellow2GreenHspaCodesDlLoadThreshold UA07.1.2: FDDCell.reserved0 (byte3) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink codes cell load to transition from yellow to green. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

yellow2RedHspaCodesDlLoadThreshold UA07.1.2: FDDCell.reserved3 (byte0) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink codes cell load to transition from yellow to red. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

red2YellowHspaCodesDlLoadThreshold UA07.1.2: FDDCell.reserved3 (byte1) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink codes cell load to transition from red to yellow. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

red2BlackHspaCodesDlLoadThreshold UA07.1.2: FDDCell.reserved3 (byte2) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink codes cell load to transition from red to black. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

black2RedHspaCodesDlLoadThreshold UA07.1.2: FDDCell.reserved3 (byte3) bit 0..6

HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink codes cell load to transition from black to red. The value indicates the percentage of the cell capacity being occupied, i.e. not available to a new user. The lower the value, the more capacity is available.

UMTS Radio Mobility



4.18.2 3G2G REDIRECTION AT RRC ESTABLISHMENT FOR SPEECH CALLS


The Redirection during the Rab Assignment processing is covered by the iMCTA function (refer also to § 4.19). There are 2 general points in the speech call setup request where the call could fail as a result of UTRAN related resource contention:

o RACH Access: The RACH channel has a fixed (shared) bandwidth, and contention will occur if the number of UEs attempting to access the 3G network exceeds a given threshold. Under extreme conditions the amount of UL interference generated by the UEs may significantly reduce the number of UEs which are able to access the UTRAN. Users may experience delays in accessing the network due to collisions on the RACH channel. The UE will re-attempt the call setup (multiple times with increasing power each time), but if the RACH access failure persists, the call will fail. Call failures associated with RACH access are outside of the scope of this feature capability.

o SRB Assignment: The SRB is established as a result of the first Access Stratum (AS) message being received by the RNC, and is used to allow the UE and CN to exchange subsequent Non Access Stratum (NAS) messages to allow the call to progress. RRC Redirection is triggered by failures at this point in the call progression.


o The redirection applies to calls with RRC Establishment cause equal to MO Conversational or Emergency. o The RNC is unaware of the UE capabilities at RRC Connection Request time. Therefore, the RNC will

attempt an RRC Redirection irrespective of whether the UE supports the Redirection IE in the RRC reject message, or whether the UE supports GSM. The resultant behaviour is not defined in the standards; however, the end result is that the ability to redirect the call to 2G may not function in these cases.

o RRC Redirection does not apply to any mobile terminated call scenario. This is due to the fact that the anchor 3G-MSC has already been established prior to the RRC Connection Request, and is not able to be modified. The call would fail at the CN if a RRC Redirection is attempted. Therefore, RRC Redirection is not triggered for this scenario.

o RRC Redirection will not be triggered by the RNC if the UE already has an established RRC connection. This could be the case in the following scenarios:

o A PS call is established prior to invocation of the speech call attempt, and is in either the active state or AO Step 1 state.

o The UE did not release the RRC connection after the initial Location Update. This could possibly be the case where the call is invoked very early after the UE is powered up. The UE may choose to set the “follow-on request” indicator during the Location Update Request, if it has a subsequent request pending. There may be other cases where the UE will request the network to keep the RRC Connection established.

o RRC will redirect all MO Conversational calls to 2G upon admission failure (irrespective of service type and domain). This includes:

o Non-speech calls such as Video telephony, which will arrive, and fail, on the 2G network. However, these calls have already failed to establish on the 3G network. GSM may either simply fail the call or attempt to redirect the Video telephony back to 3G.

o Conversational calls on the PS domain. This is not currently the case, but they may be present in the future.

This is merely a consequence of the fact that the RRC establishment cause is not able to uniquely identify a CS speech at this early stage of the call progression.

If the neighbouring 2G cells (measurement based or blind) are not provisioned at the OMC-R, RRC Redirection will not be triggered in the RNC, even if RRC Redirection is enabled for that cell. However, having RRC Redirection enabled for a cell which has no 2G neighbouring cells provisioned is considered a configuration error.

UMTS Radio Mobility



4.18.2.3 ALGORITHM

The flow for RRC Redirection is shown in Figure 59: RRC Speech Redirection.

Node B RNC UE

RRC/RACH (RRC connection Request (cause: MO Conv or Emergency))

RRC/ FACH (RRC Connection Reject (Wait Time, Redirection info: GSM))


If admission fails, and the UTRAN is enabled to redirect speech calls to 2G, a RRC Connection Reject is sent to the UE with redirection info included.

1 2

Figure 59: RRC Speech Redirection

The key steps are as follows: o Step 1: The UE requests the initial signalling as a normal conversational call setup request. While in this

example the setup relates to a speech call setup, the same RRC cause value would be used for a Video Telephony call setup request. There is also a separate cause value for an emergency call request, which could also trigger RRC Redirection. This step is preceded by the location registration (not shown here).

o Step 2: The RNC will execute normal (i.e. existing) RRC Connection Admission mechanism, which consist

of the following functions: � Cell CAC: The UL interference (conveyed in the RSSI) is checked to ensure it does not exceed a

provisioned UL interference level threshold; � RNC Overload: The RRC connection request may be denied based on the current RNC Overload level

CAC; � Maximum UE Contexts: The RNC checks that the maximum number of concurrent UE contexts will

not be exceeded. � SRB CAC: The RNC will check that the resources required to support the SRB are available. The

required resources are dependant on whether the setup is via Cell_FACH or Cell_DCH, and is as follows:

o Cell_DCH: � Radio Resources (OVSF codes, DL Power) � NodeB CEM � AAL2 CAC: In this case there are several existing possible exhaust scenarios, such as

Iub bandwidth exhaust (or Iur in the case of a DRNC scenario), CID exhaust, PID failure, and PathGroup failure. However, the most likely failure scenario is Iub bandwidth exhaust, due to the throughput constraint of this physical connection. This is a calculated capacity, based on the sum total of all RBs currently assigned to that resource (partitioned into DS and NDS traffic, as of UA04.1).

� Internal RNC U-Plane resources (e.g. PSFP) o Cell_FACH:

� Number of contexts on the FACH channel � Internal RNC U-Plane resources (e.g. PSFP)

If failure occurs on any one of the above RRC admission controls, the RNC will execute the RRC Redirection Enabling Criteria. The RRC Connection Reject message will contain the Redirection info IE with Inter-RAT info set to “GSM”. In order to improve the 3G-2G HHO duration, the IE “GSM target cell info list” may be set for Rel6 UE if allowed (OAM parameter isGsmTargetInfoListAllowed). The mobile station performs inter-system cell reselection and re-originates the speech call on the 2G network.

UMTS Radio Mobility



The UE cell selection is not a blind HO, since the UE performs target GSM cell selection.

In the case where the 2G cell selection fails, the UE will re-attempt a call in 3G, and this up to N300 times. However, the UE is required to wait (at least) a predetermined time before the subsequent attempt on the 3G network. This wait time is sent by the RNC to the UE in the Wait Time IE in the RRC Connection Reject message. The Wait Time parameter will be set to the value associated with one of the following parameters:

o timeReject. If the admission failure which causes the redirection is “RNC overload”; o a static RNC value if the admission failure which causes the redirection is not ” overload”; o waitTime3Gto2GRedirectFailure. In the case of a “3G-2G Emergency

When the re-attempt occurs in the same Fdd cell within a certain period of time (RrcCnxRepeatTime OAM parameter), the RNC doesn’t redirect the call to the 2g and attempts to establish the call on the FDD cell thanks to a mechanism at cell level which registers the UE identity before launching the 3G2G redirection. If the re-attempt occurs after the timer elapses or in a different Fdd cell, the Rach is managed as a first RRC establishment request.

4.18.2.4 PARAMETERS

Name Object/Class Definition is3Gto2gConversationalCallRedirectOnRrcEstabFailAllowed


This parameter enables the RRC Speech Redirection feature

blindHoGsmNeighbourTargetCgi

FDDCell Class3

link to a GSMCell instance

timeReject RadioAccessService Class3

Wait time used when the redirection is due to RNC overload

WaitTime3GTo2GRedirectFailure FDDCell Class 3

This parameter clarifies the wait Time to provide to the UE in case of failed redirection triggered by the features CS speech call redirection to 2G , 3G2G redirection for emergency call or 3G2G redirection based on cell load.

emergencyCallRepeatTime renamed rrcCnxRepeatTime

RNC RadioAccessService ServiceInit

Definition is updated: This is the maximum time between two Emergency call or CS speech call attempts from the same UE (where the first attempt was already rejected with 2G redirection information present) that can lead to a non redirection to the 2G network (even if the 3G to 2G redirection for emergency calls is allowed).

isGsmTargetInfoListIeAllowed RNC RadioAccessService ServiceInit

This parameter allows using the R6 IE GSM Target Info List in the RRC Connection Reject message. Two values: TRUE/FALSE TRUE: the IE may be used

UMTS Radio Mobility



when a redirection towards GSM has to be processed. FALSE: the IE shall not be used when a redirection towards GSM has to be processed.

4.18.3 EMERGENCY AND PRIORITY CALLS


For emergency calls in some countries it is required to determine the location of the UE at call establishment. Current UMTS networks and/or UEs may not allow for a determination of the UE location with sufficient accuracy. In order to take advantage of existing GSM location position solution that satisfies the FCC E911 Phase II requirements, emergency calls can be redirected on initial 3G call set-up [USA Market - or handed over after 3G call set-up] to the 2G GSM network.

4.18.3.2 APLLICABILITY

Emergency calls are always mobile originated speech calls. UTRAN is aware that the call initiated by the mobile is an emergency call from the RRC establishment cause set to "Emergency call", [USA Market - and from the RANAP RAB Assignment Request when the IE 'Priority Level' in 'RAB Parameters' – 'Allocation/Retention priority' has the value as configured by parameter RadioAccessService.emergencyCallPriorityLevel ]

4.18.3.3 ALGORITHM

• Normal Case Under Normal (i.e. non-overload) conditions and if no re-direction to GSM is required (see section "3G-2G Emergency Redirection" below), no specific treatment is applied by the RNC during call establishment. The call is handled as specified in the "MO call setup" section. When the RNC is in an overload condition, the percentage of emergency calls processed by the RNC may be reduced. The effect of overload on emergency calls is provided in [R1].

• 3G-2G Emergency Redirection For specific needs related to UE positioning, it may be required by the operator to re-direct the UE initiating an emergency call to the 2G network, in order to utilize a location solution deployed in the operator’s 2G network. The redirection is made upon reception of the RRC Connection Request message by the RNC (from the UE), if each of the following conditions is true: • RRC Establishment Cause is Emergency Call • The RRC Redirection feature is enabled on the RNC (on a per-cell basis) • If the mobile current cell has provisioned a 2G neighbouring cell. [USA Market - In case the UE has an on-going PS call at the time the emergency call is attempted, then the emergency call establishment is not initiated with RRC Connection Request. Therefore no RRC Redirection is possible. With "Immediate Handover of Emergency Calls" (see [R2] for details) this problem can be avoided by initiating handover to 2G after call establishment.] The flow for RRC Redirection is shown in following figure:

UMTS Radio Mobility



MSC-CS Node B RNC UE

RRC/ RACH (RRC connection Request (cause: Emergency Call))

RRC/ FACH (RRC Connection Reject (Wait Time,

Redirection info: GSM))


If the UTRAN is setup to re-direct emergency calls to 2G and if 2G neighbouring cells are available, a RRC Connection Reject is sent to the mobile, otherwise, the call is processed as in "MO Call Setup".

Figure 60: 3G-2G Emergency Redirection

The RRC Connection Reject message will contain the Redirection info IE with Inter-RAT info set to “GSM”. In order to improve the 3G-2G HHO duration, the IE “GSM target cell info list” may be set for Rel6 UE if allowed (OAM parameter isGsmTargetInfoListAllowed). On reception of the RRC Connection Reject message, and as specified in [A4] (RRC specification): If WaitTime equals 0, the mobile enters Idle Mode. The call setup is considered as unsuccessful and there is no further RRC connection attempts tried by the mobile for this call. Otherwise, if WaitTime is different from 0, the mobile shall:

Perform GSM cell selection immediately In case of GSM selection failure, the UE shall not re-select a UMTS cell until WaitTime has expired.

In case there is an on-going PS at the time the emergency call is attempted, there is no possibility to re-direct the call to GSM, as the RRC connection has already been established for the PS session. If the mobile fails the redirection and if the user re-attempts a new E911 call setup, the RNC will try to redirect again this call to the 2G network. Likely the redirection will fail again, and the mobile will again enter idle mode. To avoid endless loop preventing the E911 call to be setup, an enhancement allows the RNC to accept a repeated RRC Connection Setup for an Emergency call coming from the same mobile within a certain period of time (RrcCnxRepeatTime OAM parameter), even if Redirection to 2G is configured for E911 calls. A filtering mechanism is also implemented in the RNC to discard Rach repetition within a certain period of time (Static parameter: repeatFilteringTime).

Refer to § 4.18.2 for redirection procedure. Refer to [R13] for more details on specific emergency redirection.

• [USA Market - Immediate Inter-RAT Handover Radio access bearer resources are assigned in UMTS to allow for fast call establishment. Depending on parameter immediateHOofEmergencyCalls after successful call establishment the emergency call is handed over to GSM as soon as possible taking into account the cell configuration and UE capabilities. The UE performs GSM measurements and if a suitable GSM target cell is found within time interSystemHOe911Timer then the handover is initiated. Location reporting requests from the MSC are queued during this time and discarded in case of successful handover. The core network will then repeat the location reporting request to the GSM network. In case no suitable GSM target cell is found or in case of handover failure the emergency call is continued in UMTS and the location reporting request is processed.]

Special handling may apply also to priority calls. An example is the Wireless Priority Service (WPS) in the US, which defines redirection to the GSM system of WPS calls which originate from a UMTS subscriber, or NS/EP calls which terminate to a UMTS subscriber, if radio resource congestion occurs on the UTRAN. On RAB Assignment the MSC indicates that the call is a priority call. If UTRAN is congested, then the UTRAN initiates directed retry to GSM (see section 4.19 for a description of the CAC based handover algorithm). The directed retry for WPS calls can be enabled on RNC basis.

In case of inter-RAT handover attempts for emergency [USA Market] or priority calls the RNC does not retry handover to the next best cell in case of relocation preparation failure – see section 4.10.4.

UMTS Radio Mobility



4.18.3.4 PARAMETERS

Name Object/Class Definition is3Gto2GRedirectForEmergencyAllowed

FDDCell Activation flag to enable 3G to 2G redirection for emergency calls

WaitTime3Gto2GRedirectFailure

FDDCell Value for WaitTime IE sent to the mobile in case of re-direction to GSM. From 0 to 15 seconds. The default value is 1 second.

isGsmTargetInfoListIeAllowed


This parameter allows using the R6 IE GSM Target Info List in the RRC Connection Reject message. Two values: TRUE/FALSE TRUE: the IE may be used when a redirection towards GSM has to be processed. FALSE: the IE shall not be used when a redirection towards GSM has to be processed.



Definition is updated: This is the maximum time between two Emergency call or CS speech call attempts from the same UE (where the first attempt was already rejected with 2G redirection information present) that can lead to a non redirection to the 2G network (even if the 3G to 2G redirection for emergency calls is allowed).

immediateHOofEmergencyCalls [USA Market]

FDDCell / NeighbouringRNC Class 3

Indicates whether emergency calls should be handed over to GSM using immediate Inter-System Handover after RAB establishment or kept in UMTS. Following options are available: - disabled - inter system handover for all emergency calls - inter system handover for emergency calls of non-GPS UEs The RNC level parameter RadioAccessService::isImmediateHOofEmergencyCallsAllowed must be enabled for immediate inter-system handover of emergency calls.

emergencyCallPriorityLevel

RadioAccessService Class 3

The parameter identifies the 'Priority Level' of Emergency Call bearer and is used to recognise the Emergency Call on receiving RANAP Allocation/Retention Priority communicated by CN to RNC over Iu interface.

interSystemHOe911Timer [USA Market]


If a call is an emergency call and an immediate handover to GSM should be performed, then the RNC tries the handover for the time interSystemHOe911Time. On expiry of this timer the attempt to revert the emergency call to GSM is aborted. An ongoing handover attempt is not aborted. The call will be handled like a normal call, i.e. the call will be kept in UMTS but may be handed over to GSM at a later time e.g. due to coverage reasons.

isImmediateHOofEmergencyCallsAllowed [USA Market]


This parameter enables/disables the 'Immediate Handover of Emergency Calls to GSM' on a per RNC basis. On cell basis further configuration options are available.

isWpsDirectedRetryAllowed

Imcta Class 3

If enabled Wireless Priority Service (WPS) calls are directed to GSM if the UMTS cell is in congestion.

UMTS Radio Mobility



wpsTRelocPrep

Imcta Class 3

Length of time the source RNC will await a response from the CN after sending a RELOCATION REQUIRED message to the CN. If the timer expires the RNC will abort the Relocation Preparation procedure by initiating the Relocation Cancel procedure. This specific timer for US priority call service Wireless Priority Service (WPS) has higher values than normal to regard for queuing in the target GSM system of the WPS calls. When a directed retry handover of a WPS call is attempted, the call may queue for an idle trunk and/or a radio for up to 180 seconds.

4.18.3.5 PERFORMANCE MANAGEMENT

[USA Market -The following counters are available for "Immediate Handover of Emergency calls":

• RAB.AttEstabCSV.EC This PM counts the number of RAB Assignment Requests for Emergency Calls. This PM is only applicable for Emergency Calls.

• RAB.SuccEstabCSV.EC This PM counts the number of Successful RAB Establishments for Emergency Calls. This PM is only applicable for Emergency Calls.

• VS.IRATHO.ECIHO.AttHO This PM counts the number of Emergency calls for that an Immediate Inter-System Handover is attempted. Only applicable for the context of "Emergency Call Immediate Inter-System Handover".

• VS.IRATHO.ECIHO.AttRelocPrep The number of attempted relocation preparations for Emergency Call Immediate Inter-System Handover (ECIHO). Only applicable for the context of "Emergency Call Immediate Inter-System Handover".

• VS.IRATHO.ECIHO.AttRRCHO The number of attempted handovers for Emergency Call Immediate Inter-System Handover (ECIHO). Only applicable for the context of "Emergency Call Immediate Inter-System Handover".

• VS.IRATHO.ECIHO.SuccHO The number of successful Emergency Call Immediate Inter-System Handovers (ECIHO). Only applicable for the context of "Emergency Call Immediate Inter-System Handover".

• VS.IRATHO.ECIHO.CancelHO The number of Emergency calls for that an Immediate Inter-System Handover is cancelled by normal call release after the RAB has been successfully established and before the handover is initiated by a relocation preparation procedure. Only applicable for the context of "Emergency Call Immediate Inter-System Handover".

• VS.IRATHO.ECIHO.CancelRelocPrep The number of Emergency calls for that an Immediate Inter-System Handover is cancelled by normal call release after the RAB has been successfully established and before the handover is initiated by a relocation preparation procedure. Only applicable for the context of "Emergency Call Immediate Inter-System Handover".]

The following counters are available for "Wireless Priority Service":

• RAB.AttEstabCSV.WPS RAB Assignment Requests for Wireless Priority Service (WPS) calls. Number of RAB Assignment Requests for Wireless Priority Service (WPS) calls. This measurement is pegged only if WPS handling is enabled in the RNC. Applicable in the context of WPS calls, only.

• VS.3g2gOutHoFailure Number of failed outgoing CS IRAT Handovers from 3G to 2G

• VS.IRATHO.WPS.AttDirectedRetry Attempted CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls. Number of

UMTS Radio Mobility



attempted CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls. Applicable in the context of Directed Retry for WPS calls, only.

• VS.IRATHO.AttRelocPrepOutCS.WPS Attempted CS IRAT relocation preparations of CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls. Applicable in the context of Directed Retry for WPS calls, only.

• VS.IRATHO.WPS.AttHO Attempted CS IRAT handovers of CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls. Description: Applicable in the context of Directed Retry for WPS calls, only.

• VS.IRATHO.WPS.SuccDirectedRetry Successful CAC failure initiated CS IRAT Directed Retries of Wireless Priority Service (WPS) calls. Applicable in the context of Directed Retry for WPS calls, only.

• VS.IRATHO.WPS.CancelHO Cancelled WPS CS IRAT Directed Retry attempts. The number of WPS calls for that the Directed Retry is cancelled by normal call release after the RAB Assignment was received and before the Directed Retry is initiated by a relocation preparation procedure. Applicable for the context of WPS call Directed Retry, only.

• VS.IRATHO.WPS.CancelRelocPrep Cancelled WPS CS IRAT Directed Retry Relocation Preparations. The number of WPS calls for that the Directed Retry is cancelled by normal call release during ongoing relocation preparation procedure. Applicable for the context of WPS call Directed Retry, only.

The counters are of cumulative type. They are defined as two sets, one set on per FDDCell basis (the Primary RL of the UE is on this FDDCell) and one set on per neighboring RNC basis (the Primary RL of the UE is on this Neighboring RNC).

4.18.4 3G2G REDIRECTION BASED ON CELL LOAD


This feature enables 3G/2G RRC redirection of CS Speech calls when the cell load on the originating UMTS cell reaches a configurable threshold. The following elementary load indicators are read by the feature to take the decision to move call towards the 2G:

• CEM ul and CEM dl load; • Iub dl load: the max elementary Iub color among the load color conversational, streaming or I/B DCH

is taken into account; • Code load; • Downlink power load; • RTWP load of the ul DCH + non scheduled E-DCH.

Definitions of the load indicator are given in [R7]. The worst load color of the different indicators is taken into account and compared with a threshold (redirection3G2GOnCellLoadThreshold parameter) dedicated to this feature.


The service eligible to this feature is identified when the RNC receives a RRC establishment request by using the following RRC Information Element:

• RRC Establishment cause IE = “Originating Conversational Call” or ” Emergency call”; • Call type IE (Rel6)= “CS speech”;

UMTS Radio Mobility



The call type is a R6 IE. This IE is mandatory present if the IE "Domain indicator" has the value "CS domain" and the IE “Establishment cause” has the value “Originating Conversational Call” or “Emergency Call”. Otherwise it is not needed. It allows differentiating a speech call from a video telephony call. For UE with a release up to R5, call type IE is not present and a CS speech service or a CS video telephony cannot be differentiated. It may induce the redirection of a video telephony service. On RRC Connection Setup request message receipt the criterion to a redirect the call towards 2G is:

• The feature is activated on this FDD cell (is3G2GRedirectOnCellLoadAllowed OAM parameter) AND

• The Rach is not a repeated Rach AND

• The current FDD cell has neighboring GSM cells configured (see Note 1) AND

• The 3G2G redirection load color of the cell receiving the RACH or of the twin cell if traffic segmentation applies, is above or equal to the cell 3G2G redirection load threshold (redirection3G2GOnCellLoadThreshold OAM parameter)

AND • (

• The UE version is R6 or above and the Domain indicator = “CS domain” and the Call type IE = “CS speech” and the RRC Establishment cause IE = “Originating Conversational Call”;

OR • The UE version is R6 or above and the Domain indicator = “CS domain” and the Call

type IE = “CS speech” and the RRC Establishment cause IE = “emergency call” and the feature is configured to apply to emergency call (is3G2GRedirectOnCellLoadAllowedForEmergency OAM parameter);

OR • The UE version is up to R5 and the RRC Establishment cause IE = “Originating

Conversational Call” and the feature is configured to UE with a release up to R5 (is3G2GRedirectOnCellLoadAllowedForR99AndR5 OAM parameter);

OR • The UE version up to R5 and the RRC Establishment cause IE = “Emergency call” and

the feature is configured to apply to emergency call and the feature is configured to UE with a release up to R5.

• ) Note 1: The GSM frequency bands supported by the UE are unknown when processing the RRC Connection Request message (only given in the RRC Connection complete message): this capability cannot be checked by the RNC. Note 2: 2G load is not taken into account to take the decision to trigger the redirection. Note 3: A load threshold equal to “green” may be used to redirect all candidate RRC connection request towards the 2G. The interaction with other RRC redirection features is given in 4.18.5.

4.18.4.3 ALGORITHM

The flow for RRC Redirection is shown in Figure 61: RRC Redirection.

UMTS Radio Mobility



Node B RNC UE

RRC/RACH (RRC connection Request (cause: MO Conv or Emergency))

RRC/ FACH (RRC Connection Reject (Wait Time, Redirection info: GSM))


If the call is eligible to to the 3G2G redrection criterion a Rrc Connection Reject is sent to the UE with redirection info included which may include the GSM target cell info list IE

1 2

Figure 61: RRC Redirection

On receipt of the RRC connection request, after applying the priority between all RRC redirection features (see 4.18.5), the redirection criterion described in 4.18.4.2 is checked. If it is verified the call is redirected towards the 2G using a RRC Connection Reject message with the following setting:

• Initial UE identity (Mandatory IE)= <read from RRC connection request msg> • Rejection cause (Mandatory IE)= ‘congestion’ • Wait time (Mandatory IE)= waitTime3Gto2GRedirectFailure • Redirection to GSM information:

o CHOICE Redirection info () • Inter-RAT info

• Inter-RAT info = “GSM” • GSM target cell Info List (1 to maxGSMTargetCells=32) (IE

Rel 6) o BCCH ARFCN o Band Indicator o BSIC

Upon receiving this message, the UE will process GSM cell selection process using or not the GSM target cell info and will attempt a Rach on 2G if it finds an eligible GSM target cell. If no GSM cell fulfills the selection criteria, the UE will re-attempt a new RACH towards the UTRAN after the “wait time” timer (UE timer) has elapsed. The UE may camp on the same Fdd cell or another Fdd cell (the cell reselection process may change the Fdd cell . When the re-attempt occurs in the same Fdd cell within a certain period of time (RrcCnxRepeatTime OAM parameter), the RNC doesn’t redirect the call to the 2g and attempts to establish the call on the FDD cell thanks to a mechanism (already used for all features dealing with RRC Redirection) at cell level which registers the UE identity before launching the 3G2G redirection. If the re-attempt occurs after the timer elapses or in a different Fdd cell, the Rach is managed as a first RRC establishment request. [UA06-UA07 difference]:The feature reuses the EmergencyCallRepeatTime parameter created by the feature 3G/2G redirection enhancement for 911 calls and renames it: “RrcCnxRepeatTime”. The value setting has to take into account the worst scenario: The UE doesn’t find a suitable cell among the GSM cell list given by the RNC. The UE has to wait 10 sec (3GPP static value) before starting a new search among all GSM cells. A value around 30 sec is recommended. As for feature 3G/2G redirection enhancement for 911 calls, a filtering mechanism is implemented in the RNC to discard Rach repetition within a certain period of time (Static parameter: repeatFilteringTime).

UMTS Radio Mobility



4.18.4.4 PARAMETERS

New parameters:

Parameter MO Class Definition is3G2GRedirectOnCellLoadAllowed RNC NodeB

FDDCell 3-A2 Enables the feature when

the Rach concerns a normal or emergency CS speech call .

is3G2GRedirectOnCellLoadAllowedForEmergency RNC RadioAccessService

3-A2 Enables the feature when the Rach concerns an emergency CS speech call.

is3G2GRedirectOnCellLoadAllowedForR99AndR5 RNC NodeB FDDCell

3-A2 Enables the feature when the Rach conerns a UE with a release strictly below R6.

redirection3G2GOnCellLoadThreshold RNC NodeB FDDCell

3-A2 Enum (green, yellow, red) When the cell load color is higher or equal to this threshold, the 3G2G redirection feature may apply.

isGsmTargetInfoListIeAllowed RNC RadioAccessService ServiceInit

3-A2 This parameter allows using the R6 IE GSM Target Info List in the RRC Connection Reject message. Two values: TRUE/FALSE TRUE: the IE may be used when a redirection towards GSM has to be processed. FALSE: the IE shall not be used when a redirection towards GSM has to be processed.

[UA06-UA07 difference]:Parameters modified:

Parameter MO Class Definition waitTime3Gto2GRedirectFailure RNC NodeB FDDCell 3-A2 Already used by feature 3G/2G

redirection for emergency calls. The Definition is updated: see 4.18.2.4.



3-B Already used by feature 3G/2G redirection enhancement for 911 calls. Definition is updated: This is the maximum time between two Emergency call or CS speech call attempts from the same UE (where

UMTS Radio Mobility



the first attempt was already rejected with 2G redirection information present) that can lead to a non redirection to the 2G network (even if the 3G to 2G redirection for emergency calls is allowed).

4.18.4.5 PERFORMANCE MANAGEMENT

[UA06-UA07 difference]:Counters modified: RRC.FailConnEstab. Counter added: VS.RRC_ConnectionReAttempt. See [A14] for more details.

4.18.5 PRIORITY BETWEEN RRC REDIRECTION FEATURES


The interaction between the different redirection features are described in the following section

4.18.5.2 ALGORITHM

Following table gives the interworking between all the above features:

UMTS Radio Mobility



Call Type 1 # RRC

2

attempt 25145

3

(emergency) 13451 (CAC)

34480 (load)

75069 / 81213

Reference 4

Cell Cell Load of

reference cell Result

emergency first active <any> <any> <any> originating <any> Redirect to 2G triggered by 25145 <any> repeated <any> <any> <any> <any> originating below CAC RRC establishment in reference cell <any> repeated <any> <any> <any> <any> originating CAC failure Reject RRC establishment or

33322 to trigger pre-emption in reference cell non-CSV first <any> <any> <any> disabled originating below CAC RRC establishment in reference cell non-CSV first <any> <any> <any> enabled selected by

75069 below CAC RRC establishment in reference cell

non-CSV first <any> <any> <any> disabled originating CAC failure Reject RRC establishment or 33322 to trigger pre-emption in reference cell

non-CSV first <any> <any> <any> enabled selected by 75069

CAC failure Reject RRC establishment

CSV first inactive <any> <any> disabled originating below 34480 load CAC ok

RRC establishment in reference cell

CSV first inactive <any> <any> enabled selected by 75069

below 34480 load CAC ok


CSV first inactive <any> disabled disabled originating above 34480 load CAC ok


CSV first inactive <any> disabled enabled selected by 75069

above 34480 load CAC ok


CSV first inactive <any> enabled disabled originating above 34480 load Redirect to 2G triggered by 34480 CSV first inactive <any> enabled enabled selected by

75069 above 34480 load Redirect to 2G triggered by 34480

CSV first inactive enabled <any> disabled originating below 34480 load CAC failure

Redirect to 2G triggered by 13451

CSV first inactive enabled <any> enabled selected by 75069

below 34480 load CAC failure

Redirect to 2G triggered by 13451

CSV first inactive disabled disabled disabled originating CAC failure Reject RRC establishment or 33322 to trigger pre-emption in reference cell

CSV first inactive disabled disabled enabled selected by 75069

CAC failure Reject RRC establishment

Table 13: Feature Interactions Notes:

1. CSV is normal speech or emergency call 2. RRC attempt after callp filtering mechanism 3. Feature 25145 is active if

- 25145 is enabled in originating cell, and - the call attempt is for an emergency call, and - 2G neighbours configured

4. Reference cell for load check including related OA&M parameters and for call establishment 5. From release UA07.1.2 feature 75069 is enhanced by feature 81213.

Note: If the load of the selected twin cell is not available, a “red” default color is used for this cell in order to disfavor it: a 3G2G redirection will be launched. For consistency, the feature has to be activated in all Fdd cells of the RNC.


Support of admission control and RRC Redirection procedures.


None.

UMTS Radio Mobility



4.19. DUAL CELL HSDPA OPERATION

4.19.1 DESCRIPTION

From mobility perspective, the Dual cell Hsdpa operation has interacted with different procedures as described below:

• For Cell Selection procedure: no impact • For Redirection during RRC Establishment: Covered by UA08 feature 89857, no related functionality

available in UA7.1.2 (PLM decision) • For Soft Handover / Primary Link Change: please see section 4.19.3.1 • For Hard Handover: please see section 4.19.3.2 • SRNS Relocation: please refer to section 4.19.3.3

The interactions inducing some changes on the procedure described above are highlighted in the sub-section:

4.19.2 APLICABILITY

In the release UA07.1.2, the Dual cell Hsdpa operation shall satisfy the following requirement:

• DC HSDPA is applicable only to Cell DCH state, • DL/UL DCH signalling traffic will be transmitted via anchor carrier. • DC mobility is based on legacy mobility procedures based on the anchor carrier • Only PS I/B mapped on EDCH/HSDPA call can be setup on dual cell, the table below summarizes the

possible transitions that can be performed.

SRB

SRB + PS I/B

SRB + PS I/B+ PS I/B

+ PS I/B

- PS I/B

- PS I/B

+ 2 PS I/B

- 2 PS I/B

+ PS I/B

Call is On Single Carrier

Call is On Dual Carrier

SRB + PS I/B

SRB + PS I /B+ PS I/B

+ PS I/B

- PS I/B

- PS I/B

+ 2 PS I/B

- PS I/B

+ PS I/B

+ PS I/B

1

2

3

4

5

6

b

c

de

f

g

Dual Cell Conditions fulfilled Dual Cell Conditions not fulfilled

h

a

Only dotted arrows are applicable to Trial Scope

Example of transitions for Dual Cell Hsdpa Operation

UMTS Radio Mobility



4.19.3 ALGORITHM

4.19.3.1 SOFT HANDOVER

4.19.3.1.1 ACTIVE SET UPDATE

Active set updates are possible for the anchor carrier, only. RNC 9370 handles primary cell change and active set update as separate procedures. DC operation affects the primary cell, only. Therefore active set updates do not change the DC configuration.

• Links over IuR o No special handling is needed for DC operation on active set update over IuR. Normal HSPA

behaviour applies. • E-DCH Active Set

o No special handling is needed for DC operation in case of E-DCH active set change.

4.19.3.1.2 PRIMARY LINK CHANGE

DC operation has no influence on the decision to perform Primary Link Change (PLC). The existing criteria for primary link change, e.g. event 1d, are kept without modification. R99 to HSDPA DC case Successful Operation

If for a R99 call the primary link changes then a reconfiguration to HSPA may get triggered - this is existing functionality. As part of the reconfiguration to HSPA for DC capable UEs the RNC checks DC applicability of the new cell. If DC is applicable then the RNC enhances the reconfiguration to HSPA by inclusion of the secondary cell information.

The RNC includes one instance of the IE "Additional HS Cell Information RL Reconf Prep" in the NBAP message RADIO LINK RECONFIGURATION PREPARE to the new serving NodeB with following sub-IEs:

• HS-PDSCH RL ID • C-ID • HS-DSCH FDD Secondary Serving Information

The NodeB shall include the IE "Additional HS Cell Information Response" in the NBAP message RADIO LINK RECONFIGURATION READY. The RNC includes the IE "Downlink secondary cell info FDD" in the RRC message RADIO BEARER RECONFIGURATION. The RNC considers the reconfiguration to HSPA DC as successful on reception of RRC message RADIO BEARER RECONFIGURATION COMPLETE. Unsuccessful Operation

If due to any reason the new serving NodeB is not able to establish the secondary cell requested by the RNC in the RADIO LINK RECONFIGURATION PREPARE message then the NodeB shall completely fail the radio link reconfiguration. The NodeB shall reply with NBAP message RADIO LINK RECONFIGURATION FAILURE and include the cause value "Multi Cell operation not available".

On receipt of message RADIO LINK RECONFIGURATION FAILURE with cause value "Multi Cell operation not available" the RNC attempts to reconfigure the call to HSPA with SC operation. For this the RNC appliesthe existing R99 to HSPA reconfiguration procedure. Note: If non-serving NodeBs are part of the active set then these are already configured at this time.

UMTS Radio Mobility



Note: No special handling is needed for DC because the RADIO LINK RECONFIGURATION CANCEL message which is part of the existing failure handling will remove the DC configuration from the new serving NodeB if the preparation had failed for a non-serving NodeB. In case the RNC receives a Radio LINK Reconfiguration failure message the RNC applies the existing failure handling for R99 to HSPA configuration.

Note: The RNC does not know if the failure was caused by the DC configuration or any other reason. The existing failure handling is the reconfiguration to R99, this will remove the DC configuration in the NodeB.

HSDPA SC to DC case Successful Operation In case of PLC for a HSPA call the serving cell is changed from old to new serving cell - this is existing functionality. As part of the serving cell change for DC capable UEs the RNC checks DC applicability of the new cell. In case of PLC for a SC call and for the new cell DC is applicable then the RNC enhances the serving cell change procedure by inclusion of the secondary cell information: The RNC includes one instance of the IE "Additional HS Cell Information RL Reconf Prep" in the NBAP message RADIO LINK RECONFIGURATION PREPARE to the new serving NodeB with following sub-IEs:


The NodeB shall include the IE "Additional HS Cell Information Response" in the NBAP message RADIO LINK RECONFIGURATION READY. The RNC includes the IE "Downlink secondary cell info FDD" in the RRC message RADIO BEARER RECONFIGURATION. The RNC considers the serving cell change with DC target as successful on reception of RRC message RADIO BEARER RECONFIGURATION COMPLETE

Unsuccessful Operation If due to any reason the new serving NodeB is not able to establish the secondary cell requested by the RNC in the RADIO LINK RECONFIGURATION PREPARE message then the NodeB shall completely fail the radio link reconfiguration. The NodeB shall reply with NBAP message RADIO LINK RECONFIGURATION FAILURE and include the cause value "Multi Cell operation not available". On receipt of message RADIO LINK RECONFIGURATION FAILURE with cause value "Multi Cell operation not available" the RNC attempts to perform serving cell change with target SC operation. For this the RNC applies the existing serving cell change procedure.

Notes: In case of inter-NodeB serving cell change the old serving NodeB is already configured at this time. Thus, a new RADIO LINK RECONFIGURATION PREPARE with SC HSPA configuration must be sent to the new serving NodeB only. Same procedure applies for inter- and intra-NodeB serving cell change. In case of intra-NodeB serving cell change the new serving NodeB is also the old serving NodeB. Note: No special handling is needed for DC because the RADIO LINK RECONFIGURATION CANCEL message which is part of the existing failure handling will remove the DC configuration from the new serving NodeB if the preparation had failed for the old serving NodeB.

UMTS Radio Mobility



In case the RNC receives a RADIO BEARER RECONFIGURATION FAILURE message the RNC applies the existing failure handling for serving cell change. The RNC does not know if the failure was caused by the DC configuration or any other reason. The existing failure handling is the reconfiguration to R99, this will remove the DC configuration in the NodeB.

HSDPA DC to DC case Successful Operation In case of PLC for a HSPA call the serving cell is changed from old to new serving cell - this is existing functionality. As part of the serving cell change for DC capable UEs the RNC checks DC applicability of the new cell. In case of PLC for a DC call and for the new cell DC is also applicable then the RNC enhances the serving cell change procedure by inclusion of the secondary cell information: In case of intra-NodeB serving cell change the RNC includes one instance of the IE "Additional HS Cell Information RL Reconf Prep" in the NBAP message RADIO LINK RECONFIGURATION PREPARE to the serving NodeB with following sub-IE:


In case of inter-NodeB serving cell change the RNC includes one instance of the IE "Additional HS Cell Information RL Reconf Prep" in the NBAP message RADIO LINK RECONFIGURATION PREPARE to the new serving NodeB with following sub-IEs:


Note: In case of inter-NodeB serving cell change the secondary cell on the old serving NodeB is implicitly removed together with the anchor cell due to inclusion of IE "HS-DSCH MAC-d Flows To Delete"; no changes required for DC. The new serving NodeB shall include the IE "Additional HS Cell Information Response" in the NBAP message RADIO LINK RECONFIGURATION READY.

The RNC includes the IE "Downlink secondary cell info FDD" in the RRC message RADIO BEARER RECONFIGURATION. The RNC considers the serving cell change with DC target as successful on reception of RRC message RADIO BEARER RECONFIGURATION COMPLETE

Unsuccessful Operation The RNC handles unsuccessful PLC from DC to DC cell in the same way as for SC to DC.

HSDPA DC to SC case Successful Operation

In case of PLC for a HSPA call the serving cell is changed from old to new serving cell - this is existing functionality. As part of the serving cell change for DC capable UEs the RNC checks DC applicability of the new cell. In case of PLC for a DC call and for the new cell DC is not applicable then the RNC enhances the serving cell change procedure as follows:

UMTS Radio Mobility



In case of intra-NodeB serving cell change the RNC includes one instance of the IE "Additional HS Cell Information RL Reconf Prep" in the NBAP message RADIO LINK RECONFIGURATION PREPARE to the serving NodeB with following sub-IEs:

• HS-PDSCH RL ID • HS-DSCH Secondary Serving Remove

Note: No changes are required to existing procedure in case of inter-NodeB serving cell change: The secondary cell on the old serving NodeB is implicitly removed together with the anchor cell due toinclusion of IE "HS-DSCH MAC-d Flows To Delete". The new serving NodeB is configured as SC with the existing procedure. The RNC considers the serving cell change with SC target as successful on reception of RRC message RADIO BEARER RECONFIGURATION COMPLETE.

Unsuccessful Operation In case of failure, e.g. the RNC receives message RADIO LINK RECONFIGURATION FAILURE or RADIO BEARER RECONFIGURATION FAILURE, then the RNC applies the existing failure handling for serving cell change.

HSPDA DC to R99 case The RNC handles a PLC with reconfiguration from DC HSPA to R99 in the same way as for SC HSPA to R99, i.e. the existing functionality applies. Note: It is not required to include IE "HS-DSCH Secondary Serving Remove" in the NBAP message to the old serving NodeB.

4.19.3.1.3 UPLINK ASPECTS

In this release DC-HSDPA is supported with E-DCH in the uplink, only. The RNC verifies the E-DCH capability of the new primary link as one of the pre-conditions for DC-HSDPA operation.

4.19.3.1.4 SRB ASPECTS

In UA07.1.2 only SRB over DCH is supported. SRB over HSPA is planned for UA08 with feature 29810 "Fractional DPCH - SRB over HSPA". The RNC is able to handle DC mobility procedures with SRB over DCH.

4.19.3.1.5 IUR ASPECTS

DC operation over Iur is not supported in this release then, • PLC to DRNC implies reconfiguration to single cell. • PLC from DRNC to SRNC triggers reconfiguration to DC if applicable.

4.19.3.1.6 MESSAGING

NBAP The RNC uses NBAP message RADIO LINK RECONFIGURATION PREPARE for serving HS DSCH cell change. The RNC includes in this message the IE "Additional HS Cell Information RL Reconf Prep" dependent on the use case: Use cases:

a) PLC with reconfiguration from SC to DC (inter- or intra-NodeB) or R99 to DC NBAP message to the new serving NodeB: One instance of IE "Additional HS Cell Information RL Reconf Prep" with following sub-IEs:

UMTS Radio Mobility




b) PLC intra-NodeB with reconfiguration DC to SC NBAP message to the serving NodeB: One instance of IE "Additional HS Cell Information RL Reconf Prep" with following sub-IEs:

• HS-PDSCH RL ID • HS-DSCH Secondary Serving Remove

Note: In case of inter-NodeB the secondary cell on the old serving NodeB is implicitly removed together with the anchor cell due to inclusion of IE "HS-DSCH MAC-d Flows To Delete".

c) PLC intra-NodeB, call remains on DC NBAP message: One instance of IE "Additional HS Cell Information RL Reconf Prep" with following sub-IEs:


d) PLC inter-NodeB, call remains on DC Same as a) for new serving cell

Note: In case of inter-NodeB the secondary cell on the old serving NodeB is implicitly removed together with the anchor cell due to inclusion of IE "HS-DSCH MAC-d Flows To Delete".

e) PLC with reconfiguration from DC to R99: will behave as the existing reconfiguration messages without any specifics for DC.

RRC The RNC uses RRC message RADIO BEARER RECONFIGURATION for serving HS-DSCH cell change. In case of serving HS-DSCH cell change with DC disabled in target configuration, the RNC omits the IE "Downlink secondary cell info FDD" in the RRC message RADIO BEARER RECONFIGURATION. In case of serving HS-DSCH cell change with DC enabled in target configuration, the RNC includes the IE "Downlink secondary cell info FDD" in RRC message RADIO BEARER RECONFIGURATION.

4.19.3.2 HARD HANDOVER

4.19.3.2.1 HHO FROM R99/SC/DC TO DC

Successful Operation

In case of HHO for a DC capable UE the RNC checks DC applicability of the target cell as with respect of dual

cell admission control. If DC is applicable then the RNC applies DC configuration on the target cell. For this the target RNC shall enhance the existing HHO procedure: The RNC includes one instance of the IE "Additional HS Cell Information RL Setup" in the NBAP message RADIO LINK SETUP REQUEST to the target NodeB with following sub-IEs:


The NodeB shall include the IE "Additional HS Cell Information Response" in the NBAP message RADIO LINK SETUP RESPONSE.

UMTS Radio Mobility



The RNC includes the IE "Downlink secondary cell info FDD" in the RRC message RADIO BEARER RECONFIGURATION.

Unsuccessful Operation If in the target NodeB the anchor cell establishment would be successful but due to any reason establishment of the secondary cell requested by the RNC in the RADIO LINK SETUP REQUEST message is not possible then the NodeB shall:

• completely fail the radio link setup including anchor cell, and • reply on NBAP with message RADIO LINK SETUP FAILURE with failure cause "Multi

Cell operation not available".

On receipt of message RADIO LINK SETUP FAILURE with cause value "Multi Cell operation not available" the RNC retries the HHO with SC configuration on target cell. In case the RNC receives a RADIO LINK SETUP FAILURE with a failure cause value other than "Multi Cell operation not available" from the target NodeB then the RNC applies the existing failure handling for HHO.

In case the RNC receives a RADIO BEARER RECONFIGURATION FAILURE message the RNC applies the existing failure handling for HHO. Note: The RNC does not know if the failure was caused by the DC configuration or any other reason. The existing failure handling includes the deletion of the new radio links on NBAP, this will remove the DC configuration in the target NodeB.

4.19.3.2.2 HHO FROM DC TO SC/R99

The RNC and NodeB shall handle the HHO from DC to SC or DC to R99 in the same way as the existing HHO procedure from SC to SC or SC to R99. Note: In case of successful operation the source active set is deleted and it is not important if the configuration was SC or DC. In case of unsuccessful operation the call either has dropped or continues on the old (DC) configuration without any specific action.

4.19.3.3 SRNS RELOCATION

This feature does not introduce the R8 transparent container for SRNS Relocation. For SRNS Relocation of 3GPP R8 UEs the SRNC shall use the R7 transparent container. For this the SRNC shall:

• reconfigure DC calls to SC, i.e. to a R7 compliant configuration, • for UE capability information

o map R8 IEs to R7 IEs where possible o omit R8 specific IEs

As part of the existing post SRNS Relocation procedures for both, UE involved and UE not involved the target RNC requests the UE capabilities. When the UE capabilities are received and indicate DC capability then the target RNC shall consider a reconfiguration to DC operation on next mobility soft or hard handover as specified in previous section dedicated to the both procedures.

4.19.3.3.1 UE INVOLVED

If for a DC call SRNS Relocation UE involved is triggered then the RNC reconfigures the call to SC prior to the SRNS Relocation. Note: Reconfiguration to SC is required because R8 transparent container is not supported.

UMTS Radio Mobility



4.19.3.3.2 UE NOT INVOLVED

During SRNS Relocation "UE not involved” the call is on single cell because DC is not supported over IuR. Thus, the SRNS Relocation "UE not involved" is not directly affected by DC in this release. But there are some related aspects that need to be handled as detailed below.

• If DRNC receives RNSAP message RL Setup, Addition or Reconfiguration with HS-DSCH Secondary Serving Information IE, it shall reject this RL Setup with failure cause "Multi Cell operation not supported".

4.19.3.4 COMPRESSED MODE

As per 3GPP 25.331 section 8.4.1.3 some UEs might not require compressed mode for measurements on adjacent frequencies - see also 3GPP section 10.3.3.21 for the UE measurement capability information. When the NodeB for a UE with DC call applies compressed mode to the anchor carrier, then the NodeB has to apply the same compressed mode configuration with same timing on the supplementary carrier. The NodeB shall apply the same compressed mode algorithm to anchor and supplementary carrier.

Note: No separate NBAP compressed mode commands are required for the supplementary carrier.

4.19.4 PARAMETERS

No new parameters have been dedicated specially to the mobility aspects. But, the dual cell hsdpa operation feature needs to be activated, please refers to [R6] for this purpose.


The following counters have been added Name: VS.HsdpaMobilitySuccess Description: Number of successful HSDPA Dual Cell mobility described by the following screenings:

• 1) HSDPA Dual Cell to HSDPA Dual Cell, • 2) HSDPA Dual Cell to HSDPA Single Cell, • 3) HSDPA Single Cell to HSDPA Dual Cell, • 4) HSDPA Dual Cell to R99 Cell, • 5) R99 Cell to HSDPA Dual Cell, Reference Cell is new primary cell of call.

Name: VS.HsdpaMobilityUnsuccess Description: Number of unsuccessful HSDPA Dual Cell mobility described by the following screenings:

• 1) HSDPA Dual Cell to HSDPA Dual Cell, • 2) HSDPA Dual Cell to HSDPA Single Cell, • 3) HSDPA Single Cell to HSDPA Dual Cell, • 4) HSDPA Dual Cell to R99 Cell, • 5) R99 Cell to HSDPA Dual Cell, Reference Cell is new primary cell of call.

4.20. INTELLIGENT MULTI CARRIER TRAFFIC ALLOCATION (IMCTA)

To increase the network capacity, operators may deploy multi layer configurations with several layers structures: Multi layers with equal coverage, Hot spots, micro cells Hierarchical cells structure. There is a need to distribute the traffic between the different layers including 2G (GSM) layers. The traffic distribution strategy may be based on load balancing, Service partitioning, UE speed, Carrier redirection preferences and mobility triggers.

UMTS Radio Mobility



The introduction of HSDPA/HSUPA will be also progressive with hot spots and there is a need to redirect HSDPA/HSUPA capable mobile towards HSDPA/HSUPA cells. The iMCTA function covers this network evolution. It includes the Alarm Handover. The iMCTA function is managed by the RNC.

FDD1 non HSXPA

FDD2 HSDPA/HSUPA

2 G

R5

R99 R5

Figure 62: Service Redirection application

FDD2 HSDPA/HSUPA

R5

FDD1 HSDPA/HSUPA

R5 R5

R5

Figure 63: Load balancing application

4.20.1 DESCRIPTION

IMCTA function allocates traffic across available carriers. For a given call, the carrier is selected by the RNC according to the Operator strategy through iMCTA configuration parameters (including Priority tables) which allows to take into account the Handover reason, the service type, the mobile type (i.e. HSDPA, HSUPA capable or not), the redirection triggers and the cells load.

4.20.1.1 IMCTA TRIGGERS

The main reasons to invoke the iMCTA function are: � Alarm condition is hit; � A CAC reason: a CAC failure occurs during the processing of a Rab Assignment sent by the CN. A

fallback to another Carrier may be done;

UMTS Radio Mobility



� A user service reason: A successful Rab establishment/modification/release, a Always On upsize or an IU Release Command is done but the mobile may be moved to a better Carrier;

� A mobility service reason: A successful Intra Freq mobility is done but mobile may be moved to a better Carrier.

The User and mobility Service triggers don’t apply if the primary cell is managed through Iur.

The Alarm and CAC triggers apply even if the primary cell is managed through Iur.

iMCTA trigger: Alarm HO reason The Alarm criterion for Inter Frequency and the Inter Rat Handover is described in section 5.9. iMCTA trigger: User Service CAC reason A CAC failure triggers iMCTA function if the failure occurs during the processing of a Rab Assignment message coming from the CN. The purpose is to find another Carrier (which may have a different PLMN) on which a target cell is eligible to support the call (established in signalling or traffic). The list of CAC failure causes which may induce iMCTA triggering is:

� From Cell: no radio resource available � From NodeB: Radio Link Reconfiguration Failure � From IUB, IUR, IU: Transport Resource allocation failure � From RNC Uplane: Resource allocation failure � From C-RNC: User Plane Dedicated Bearer allocation failure.

When a CAC failure occurs during a Rab Assignment towards HSxPA, a HSxPA to DCH fallback may be attempted. If the fallback faces up a CAC failure or may not apply, iMCTA may be called. iMCTA doesn’t apply to IRM table reject cases. iMCTA trigger: User Service reason The triggers which invoke the iMCTA function are:

� Rab Assignment sent by the CN which induces the establishment of a Traffic Rab, a Rab release or a modification of the established Traffic type. The iMCTA is invoked if the final state of the call is: one or several Traffic Rab are established;

� Incoming Relocation with one or several Traffic Rab; � After a mobile performs a successful Always On upsize from Cell_FACH or URA/Cell_PCH to

Cell_DCH; � Iu Release Command due to a Core network or a RNC (after sending an IU Release Request) decision

when applying to a Multi Service call. The triggers are valid if the originating cell (i.e. primary cell) is eligible regarding its load. This trigger belongs to “Service” triggers. When the purpose of the iMCTA is to redirect the call according to the Service and mobiles capabilities the load condition of the originating cell, i.e. using origin cell load colour threshold different from green, has not to be used if we want no limitation of the redirection application. iMCTA applies in case of Rab Assignment procedure inducing a successful fallback on DCH when no HS-DSCH resource is available. iMCTA trigger: Mobility Service reason The triggers which invoke the iMCTA functions are:

� It concerns HSDPA or HSUPA capable mobiles traffic connected in DCH and/or HS-DSCH and/or E-DCH. The trigger is a primary link cell change with the new primary cell configured with mobilityServiceForHsxpaEnable O&M attribute set to True;

� It concerns HSDPA and HSUPA non capable mobiles traffic connected in DCH. The trigger is a primary link cell change with the new primary cell configured with mobilityServiceForNonHsxpaEnable O&M attribute set to True.

The triggers are valid if the originating cell (i.e. primary cell) is eligible regarding its load level.

UMTS Radio Mobility



If service segmentation is activated, when User service or Mobility service trigger is used, the load of the originating cell is not taken into account.

4.20.1.2 CROSSOVER BETWEEN IMCTA TRIGGERS OR WITH OTHERS PROCEDURES

When the RNC waits for iMCTA measurements for a given trigger, a second iMCTA trigger, a Primary link modification or a Service modification may occur. The following rules apply:

o Priority Rule between iMCTA triggers: Alarm > CAC > User Service > Mobility Service; o Priority Rule between iMCTA triggers and others procedures:

o Alarm/CAC triggers > Primary cell change or Service modification; o User or Mobility Service triggers = Primary cell change or Service modification.

The following actions occur:

o The last event (iMCTA trigger or Primary cell change or Service modification) may induce an update of the neighbour cells;

o When the second event has a higher or equal priority than the previous with no target access change, the Measurement period may be re-started after the expiration (i.e. no target cell identified) of the current period. If the target access changes, the measurement period is stopped and re-started with the new neighbouring.

In case of CAC failure, following procedures, if applicable, apply in decreasing priority order:

• Fallback to DCH • iMCTA • preemption (refer to [R12])


The iMCTA function only applies to calls in Cell DCH, E-DCH and HS-DSCH connected mode. Calls in Cell Fach (signaling or traffic), Cell PCH or URA PCH connected mode are not managed. iMCTA works with up to six UMTS carriers1, plus a 2G layer (whatever the frequencies). The function may be activated according to four modes:

� Alarm only: Alarm trigger applies � Alarm and CAC: Alarm and User CAC Service triggers apply � Alarm and Service: Alarm and Service triggers apply � All: All iMCTA triggers apply

4.20.2.1 MANAGEMENT IN CELL HSXPA

When a CAC failure occurs during a Rab Assignment towards HSxPA, a HSxPA to DCH fallback may be attempted. If the fallback faces up a CAC failure or may not apply, iMCTA may be called (see [R6]).

4.20.2.2 IUR MANAGEMENT

Following tables gives the type of procedure executed according to the type of source/target cell and iMCTA trigger.

1 As per 3GPP [A7] UEs are required to support the own carrier and two additional FDD carriers.

UMTS Radio Mobility



4.20.2.2.1 IMCTA TRIGGER = SERVICE

Target cell

S-RNC D-RNC

S-RNC Interfreq intraRNC HHO OK Interfreq InterRNC HHO ok if feature

activated (with fallback to DCH before for HSPA calls), 3G3G relocation otherwise Source

cell

D-RNC No HHO (no measurement

started) (1) No HHO (no measurement started ) (1)

(1) No service handover from D-RNC because load information not reliable

4.20.2.2.2 IMCTA TRIGGER = CAC FAILURE

(1) CAC failure and R5 mobiles:

During intra RNC inter frequency HHO, if changing the Transport channel from HSxPA to DCH or vice-versa is needed, modifying RLC information has to be processed. The Radio Bearer Release (and also Radio Bearer Setup) message provides this capability from Rel6. For a Rel5 UE, this shall be done separately with a Radio Bearer Reconfiguration: this R5 CAC failure use case is not supported by iMCTA in this version. (2) CAC failure and interfreq HHO:

Any time Rab Assignment request is processed for a CS Rab setup, when IMCTA CAC is hit and decision is made to launch an inter freq HHO, the procedure Radio Bearer Setup used to add the CS Rab on the new frequency is replaced by two consecutive RRC procedures:

• Inter Frequency Radio Bearer Reconf to perform first mobility on the new frequency. • Intra frequency Radio Bearer Setup to add the new CS Rab.

This is due to ciphering issue at UE side. (3) CAC failure and 3G3G Relocation

Upon CAC failure, the FDD target cell shall be managed by the S-RNC. A 3G3G relocation is not supported in that case. CAC failure and directed retry

The 3GPP allows Directed Retry via relocation for RAB CS establishment failure use case only towards 2G.

4.20.2.2.3 IMCTA TRIGGER = ALARM

Target cell S-RNC D-RNC

S-RNC Interfreq intraRNC

HHO ok (1)(2) No HHO (no measurement started)(3)

Source cell

D-RNC Interfreq interRNC

HHO ok (2) No HHO (no measurement started)(3)

UMTS Radio Mobility



4.20.2.3 2G INTER RAT MANAGEMENT

Following tables gives the type of procedure executed according to the type of RAB established/to establish and

the iMCTA trigger.

4.20.2.3.1 IMCTA TRIGGER = SERVICE

RAB established on source cell CS 2G interRAT HHO PS 2G interRAT HHO (cell change order) CS + PS 2G interRAT HHO (with/without PS

reestablishement according to UE class)

4.20.2.3.2 IMCTA TRIGGER = CAC FAILURE

RAB established on source cell

RAB to establish

Signalling CS RAB assignment failure (cause directed retry) + 2G interRAT HHO

Signalling PS RAB assignment failure (cause unspecified) + 2G interRAT HHO (Cell Change Order)(1)

Signalling + CS PS RAB assignment failure for PS (cause unspecified) + 2G interRAT HHO for CS (1)

Signalling + PS CS RAB assignment failure (cause directed retry) + 2G interRAT HHO if supported by UE (2)

(1) The 3GPP only allows Directed Retry for RAB CS establishment failure use case. (2) CAC failure and 3G2G Relocation:

When a CAC failure occurs during the CS Rab establishment: • When a PS call is already established, iMCTA triggers a Directed Retry towards the 2G. This use case

is supported in 3GPP Rel 6 (Sept). If the UE doesn’t supports this use case, the redirection failed and the mobile stays with the PS established. A 3GPP R2-062614 (release 6 Sept 2006) asks to support a HHO Inter Rat when a PS + CS signalling is established. So ALU does the best effort policy: HHO is attempted. If the mobile doesn’t support this state, the HHO ends by processing the failure case (call kept on the FDD access).

4.20.2.3.3 IMCTA TRIGGER = ALARM

Target cell S-RNC D-RNC

S-RNC Interfreq

intraRNC HHO ok

Interfreq InterRNC HHO ok if feature activated (with fallback to DCH before for HSPA calls),

3G3G relocation otherwise Source

cell

D-RNC Interfreq

interRNC HHO ok

Interfreq IntraD-RNC or InterD-RNC HHO ok if feature activated (with fallback to DCH before for HSPA calls), 3G3G relocation otherwise

UMTS Radio Mobility



RAB established on source cell CS 2G interRAT HHO PS 2G interRAT HHO (cell change order) CS + PS 2G interRAT HHO (with/without PS

reestablishement according to UE class)

4.20.2.4 IMCTA LOAD BASED HO DEVELOPMENTS [USA MARK ET]

This feature is introduced in UA07.1. It enhances the iMCTA triggering in order to avoid choosing an inter frequency HHO when a risk of HHO failure exists when the handover reason is alarm or CAC. The risk detection is based on the target FDD cell load estimation but also in case of HHO CAC failure reason on the cause of the CAC failure. This feature by choosing the most suitable access (GSM or FDD) will decrease the handover failure rate during Handover algorithm. It can be activated through parameter isImctaLoadBasedAllowed The feature iMCTA load based HO developments uses load indicators which are undefined when the originating cell or the target cell are located on a D-RNC. For this reason the criteria attached to the feature iMCTA load based HO developments don’t apply to a cell located on a D-RNC.

4.20.3 ALGORITHM

4.20.3.1 MAIN FUNCTIONAL STEPS

If one of the triggers is valid for the primary cell, the function may process the following functional steps to identify a target cell on another Carrier:

1. Checking of the iMCTA feature activation parameters ; 2. Identification of the Service Type and RAB to be set; 3. Selection of the iMCTA Carrier priority table; 4. Selection of the candidate Carriers; 5. Selection of the candidate Cells for UE measurements; 6. Configuration of the Compressed mode and of the UE measurements; 7. Cell selection upon Measurement Report; 8. iMCTA HHO processing or iMCTA exit .

If no target cell is found after iMCTA algorithm processing or no measurement received or the HHO failed, the RNC has to wait the next iMCTA trigger iteration for a new call redirection attempt. For an alarm HHO trigger, when no Inter Freq/Inter Rat measurement can be requested to the mobile (compressed mode not allowed for the Service), no eligible target cell is found in the reported measurements, a iMCTA blind HHO may be attempt to the 2G twin cell (if configured).

4.20.3.2 IMCTA FEATURE ACTIVATION

The iMCTA feature activation is based on: � mode O&M attribute value (see 4.20.4); � When the trigger is Service:

o Originating cell load eligibility (if service segmentation not activated); o mobilityServiceForHsxpaEnable and mobilityServiceForNonHsxpaEnable O&M attribute

value.

4.20.3.3 NEIGHBOUR CARRIERS SELECTION

iMCTA is triggered for Service reason

UMTS Radio Mobility



The Service priority table set by O&M (refer to 4.20.4) is read for the service type requested or in progress (i.e. mobility use case). The carriers with a priority higher or equal to the current one are candidate for iMCTA target cells selection. iMCTA is triggered for Alarm or CAC reason All carriers (2G or 3G) with a priority not equal to PNA are candidate for iMCTA target cells selection. If the carriers list is empty, the iMCTA function is cancelled (step 8 is processed).

4.20.3.4 NEIGHBOUR CELLS SELECTION FOR MEASUREMENT REPORTING

When the candidate carriers are identified, the selection of the neighbour cells (see section 5.5) is sent to the mobile for measurement. The O&M FDD neighbouring provisioning of a cell has to be limited to 2 carriers in order to fulfill the mobile measurements performance requirements defined in [A7] (the 3GPP doesn’t describe the UE behaviour in case of more than 2 neighbour carriers). All following actions occur whatever the iMCTA trigger:

� The neighbouring cells fulfilling the IMSI based HO condition and belonging to layers supported by the mobile (UE capabilities checked) are selected and ordered according to the Carriers priorities for the requested Service type (according to the service priority table);

� For each neighbour cells type (Inter Freq / Intra Freq / 2G), the measurement capability is checked (i.e. Compressed Mode applicability for the current service and UE capability). Cells which must not be measured are discarded from the neighbour cells list;

� If activated by parameter “isImctaFddLayerLoadPreCheckAllowed“ (and isImctaLoadBasedAlarmAllowed for alarm) and if the target cell load filtering criteria applies to Fdd cells (for service reason [USA Market - or for alarm or CAC when a load criteria is requested by the feature iMCTA load based HO developments]):

o If all Fdd cells of a given Fdd carrier don’t fulfill the target cell load criteria, the cells are filtered (the Fdd carrier will not be monitored) from the neighbor cell list;

o For CAC all DRNC cells are filtered if no SRNC cells are to be measured of that carrier.

If the iMCTA neighbouring cells list after applying the different filters contains Inter Freq Cells and 2G (GSM) cells:

• If GSM cells have strictly the highest priority, Fdd cells are removed; • If highest priority Fdd cells have a priority strictly higher than 2G cells, 2G cells are removed; • If GSM cells have the same priority as the Fdd cells with highest priority, all cells are kept.

If the target cells list is empty, the iMCTA function is cancelled (step 8 is processed) when the triggering is for CAC or Service reasons. In case of Alarm, an iMCTA blind HHO may occur.

4.20.3.5 COMPRESSED MODE AND MEASUREMENT CONFIGURAT ION

Inter Frequency and Inter RAT measurements are configured in periodic Mode. Whatever the iMCTA trigger (Alarm, CAC or Service) the compressed mode activation and the measurements activation procedures are the same. Refer to:

� Section 6.2; � Section 6.4;

UMTS Radio Mobility



4.20.3.6 TARGET CELL SELECTION UPON MEASUREMENT REP ORT

The RRC Measurement Report message due to iMCTA function invoke may be postponed (“blocking phase”) by the RNC and processed at the end of the current procedure when another procedure (SHO, Rab Assignment, Rate modification…) is in progress. An iMCTA criteria re-evaluation/evaluation is done (i.e. iMCTA neighbor cells list may be updated) before processing the RRC Measurement Report message: a measured cell is candidate to the iMCTA cell selection criteria if it belongs to the iMCTA neighbor cells list. If a target cell (FDD or 2G) exists after applying the different filtering steps the HHO is processed. Otherwise the RNC waits next measurement reports until the guard timer elapses. The Radio criteria for target cell selection are the same whatever the trigger (Alarm, CAC, Service). Refer to:

� Section 6.5; � Section 6.6.

Any Inter freq or Inter RAT measurement due to iMCTA function received after the guard timer elapses is discarded. The following paragraphs describe the target cell selection for each trigger type.

4.20.3.6.1 IMCTA TRIGGER IS SERVICE

The following steps are processed to select a cell among the measured FDD neighbour cells: 1. For each Carrier, the best measured cell which fulfills the Radio criteria is selected, i.e. it’s the cell with

the best Ec/No which verifies FDD HHO condition; 2. Then if HSDPA traffic segmentation option (see [Parameters] section) is set to true, according to the

mobile capabilities the non HSxPA cells for a HSxPA capable mobile and the HSxPA cells for a non HSxPA UE are removed;

3. Then the FDD cells are filtered according to the following rule: a. A cell belonging to a Carrier with a priority upper than the originating cell Carrier priority

shall have a cell load color fulfilling the target cell load color criteria (see [iMCTA cell load criteria] section);

b. A cell belonging to a Carrier with a priority equal to the originating cell carrier priority shall have a cell load color fulfilling the target cell load color criteria (see [iMCTA cell load criteria] paragraph) and lower than the originating cell (i.e. primary cell) load color (except if service segmentation has a higher priority);

4. Then if Service segmentation priority option (see [Parameters] section) is set to true, if the capability of the target cell with respect to HSxPA does not match partially or fully the capability of the UE (refer to § 4.20.4.1.1 for details), the cell is removed;

5. Then if several FDD cells are eligible, the following steps (with decreasing priority) are processed until retaining one cell:

a. Cell(s) belonging to the Carrier with the highest priority is kept; b. Preference is given to the less loaded cell; c. Preference is given to the cell with the best Radio level (Ec/No).

The following steps are processed to select a cell among the measured 2G neighbour cells: 1. The cells which fulfill the Radio criteria are selected, i.e. their Rxlev verify 2G HHO condition; 2. Then the neighbour cells not fulfilling the 2G cell color load criteria are filtered (see [iMCTA cell load

criteria] section); 3. Then if several 2G cells are eligible, the cell with the highest radio level is selected (Ec/No).

If FDD and 2G neighbour cells are eligible then the FDD target is selected if parameter is3GHandoverPreferred is set to TRUE or vice versa. If 2G is selected as target and the relocation preparation to the selected target cell fails, e.g. due to load conditions in the GSM cell, then the RNC may re-evaluate the measurement report for the next best 2G neighbour cell and - if found any - re-attempt handover to this 2G cell. This re-attempt can be controlled with parameter isGsmIratHoToNextBestCellAllowed.

UMTS Radio Mobility



4.20.3.6.2 IMCTA TRIGGER IS CAC FAILURE

The following steps are processed to select a cell among the measured FDD neighbour cells: 1. For each Carrier

- the best measured cell which fulfils the Radio criteria is selected, i.e. the cell with the best Ec/No which verifies FDD HHO condition;

- [USA Market - If iMCTA load based HO developments is activated • Its load satisfies the target cell Load iMCTA based HO load color criteria (described in section

4.20.3.8.3); AND

• If the CAC failure reason is due to: o A Iub CAC failure (bandwidth lack or CID lack):

� the Iub load color (see note 3) of the target cell has to be strictly better than the iub load color of the current active set;

o A NodeB CAC failure (on one or several cells of the active set): � If the CEM load is relevant for the current active set cell and for the target FDD

cell, the CEM load color of the target cell has to be strictly better than the CEM load color of the current active set.]

2. Then if several FDD cells are eligible, the following steps (with decreasing priority) are processed until

retaining one cell: a) If UE is HSUPA capable, preference is given to HSUPA cells then HSDPA cells else if UE is

HSDPA capable, preference is given to HSDPA cells; b) Preference is given to the less loaded cell;

c) Preference is given to cell(s) belonging to the carrier with the highest priority;

d) Preference is given to the cell with the best radio level (Ec/No). The following steps are processed to select a cell among the measured neighbour 2G cells:

1. The cells fulfilling the Radio criteria are selected, i.e. their Rxlev verify 2G HHO condition; 2. The less loaded cell is preferred; 3. Then if several 2G cells are eligible, the cell with the highest Radio level is selected.

[USA Market - If iMCTA load based HO developments is activated:

If no FDD cell is eligible, a GSM cell will be selected if a suitable GSM cell is reported by the UE (see previous paragraph and note 1)

] If FDD and 2G neighbour cells are eligible then the FDD target is selected if parameter is3GHandoverPreferred is set to TRUE or vice versa.

If 2G is selected as target and the relocation preparation to the selected target cell fails, e.g. due to load conditions in the GSM cell, then the RNC may re-evaluate the measurement report for the next best 2G neighbour cell and - if found any - re-attempt handover to this 2G cell. This re-attempt can be controlled with parameter isGsmIratHoToNextBestCellAllowed. Note 1: the blind GSM cell is not used by iMCTA when the HHO reason is a CAC failure. Note 2: A WPS call is not eligible to feature iMCTA load based HO developments. Note 3: The Iub load color is the load part attached to the QoS of the services to be established.

4.20.3.6.3 IMCTA TRIGGER IS ALARM

The following steps are processed to select a cell among the measured FDD neighbour cells: 1. For each Carrier

- the best measured cell which fulfils the Radio criteria is selected, i.e. the cell with the best Ec/No which verifies FDD HHO condition

- [USA Market - If iMCTA load based HO developments is activated

UMTS Radio Mobility



• Its load satisfies the target cell Load iMCTA based HO load color criteria (described in section 4.20.3.8.3);]

2. Then if several FDD cells are eligible, the following steps (with decreasing priority) are processed until

retaining one cell: a. If UE is HSUPA capable, preference is given to HSUPA cells then HSDPA cells else if UE is

HSDPA capable, preference is given to HSDPA cells; b. Preference is given to the less loaded cell;

c. Preference is given to cell(s) belonging to the carrier with the highest priority;

d. Preference is given to the cell with the best radio level (Ec/No). The following steps are processed to select a cell among the measured neighbour 2G cells:

1. The cells fulfilling the Radio criteria are selected, i.e. their Rxlev verify 2G HHO condition; 2. The less loaded cell is preferred; 3. Then if several 2G cells are eligible, the cell with the highest Radio level is selected.

[USA Market - If iMCTA load based HO developments is activated:

If no FDD cell is eligible a GSM cell will be selected if a suitable GSM cell is reported by the UE (see previous paragraph);

Else ] If FDD and 2G neighbour cells are eligible then the FDD target is selected if parameter is3GHandoverPreferred is set to TRUE or vice versa.

If no target cell is eligible, a blind GSM cell may be used if configured. If 2G is selected as target and the relocation preparation to the selected target cell fails, e.g. due to load conditions in the GSM cell, then the RNC may re-evaluate the measurement report for the next best 2G neighbour cell and - if found any - re-attempt handover to this 2G cell. This re-attempt can be controlled with parameter isGsmIratHoToNextBestCellAllowed.

4.20.3.7 IMCTA HARD HANDOVER PROCESSING OR IMCTA EX IT

4.20.3.7.1 IMCTA HHO PROCESSING

When iMCTA function gives a target neighbouring cell to process a Hard Handover (possibly in blind mode if a 2g blind cell is configured and the mobility to the 2G domain is allowed by the Alarm priority table and Service handover option), the transition to the HHO depends on the iMCTA trigger type:

� Service or Alarm triggers: the HHO mobility procedure occurs and then waiting procedures may be processed;

� CAC trigger: After a CAC failure during a Rab Assignment/Release/Modification, the following actions are processed:

o If resources were partially allocated for the requested Rab they are released; o If the Target cell is managed by the S-RNC (i.e. Inter Freq Intra RNC HHO):

� The Inter Freq Hard Handover procedure towards the target cell is processed; � A Rab Assignment Response message is returned by the S-RNC to the Core Network; � Then waiting procedures may be processed.

o If the Target cell is not managed by the S-RNC (i.e. Inter Rat): � A Rab Assignment failure is returned to the CN with the Rab failed and a “Directed

Retry” (CS CN) or “unspecified” (PS CN) cause ; � A 3G/2G.

o If the Target cell is not managed by the S-RNC (i.e. Inter Freq RNC HHO): � A Rab Assignment failure is returned to the CN with the Rab failed and a “no-

resource available” cause

UMTS Radio Mobility



For the Hard Handover execution see the section describing the Hard Handover type used. The resource type and the rate to be allocated on a target FDD cell depends on the RNC resource allocation policy (refer to section 4.18).

4.20.3.7.2 IMCTA EXIT

The exit may occur if: � No target neighbour cell was found before the guard timer elapses (in some use case the timer was re-

armed) and no blind HHO 3G/2G may be processed; � The mobile is no more in connected mode (cell DCH).

The transition depends on the iMCTA trigger type. If Inter Frequency/Inter Rat measurements were requested to the mobile, they are released. According to the trigger, the actions are:

� Service and Alarm trigger: the waiting procedures may be processed; � CAC trigger: After CAC failure during a Rab Assignment/ Release/ Modification, the following actions

are processed: � If resources were partially allocated for the requested Rab they are released; � A Rab Assignment Response Failure message is returned by the S-RNC to the CN

with the Rab failed; � The waiting procedures may be processed.

4.20.3.8 IMCTA CELL LOAD CRITERIA

The cell load information is needed by the iMCTA function to filter loaded cells or to give a preference to the less loaded cell. The cell load iMCTA color is built by using metrics linked to DCH and non-scheduled E-DCH resources (and HSDPA ones (power and OVSF codes) if fair sharing feature is activated) occupancy at Cell, CEM or Iub levels. Whatever the resource used by the call (DCH, HS-DSCH, E-DCH), the elementary load colors depend only on the RABs established or to establish (CAC failure case). Cell load for the originating cell is not taken into account in case of iMCTA triggered for service reasons when service segmentation has a higher priority than load balancing. [UA06-UA07 difference]: With the addition of the feature iMCTA load based HO developments, the originating cell color threshold is configurable per service.

4.20.3.8.1 CELL LOAD INDICATORS

The feature consults the following elementary load indicators: • CEM ul and dl loads; • Iub downlink load; • Downlink OVSF code load; • Downlink power load; • Uplink load (RTWP).

The definition of the load indicators are given in [R7]. The Iub downlink load consulted is the load part attached to the QoS of the services to be established. For cell eligibility, each relevant cell load indicator is checked.

4.20.3.8.2 ORIGINATING FDD CELL ELIGIBILITY

For each Rab established, a set of cell load elementary colors is read.

An originating FDD cell is eligible for iMCTA if one of each relevant cell load colors is higher or equal to the

iMCTA originating cell color triggering threshold (parameter originatingCellColourThresholdPerService):

UMTS Radio Mobility



� At least one DL color ≥ iMCTA originating cell color threshold

OR

� At least one UL color ≥ iMCTA originating cell color threshold.

4.20.3.8.3 [USA MARKET] TARGET FDD CELL LOAD IMCTA LOAD BASED HO CRITERIA (USED FOR CAC AND ALARM):

The load check can be enabled for iMCTA CAC with parameter isImctaLoadBasedAllowed and for iMCTA alarm with parameters isImctaLoadBasedAllowed and isImctaLoadBasedAlarmAllowed. If the load check is enabled a FDD cell is eligible by the feature iMCTA cell load based HO if the iMCTA based load HO color of the cell is below or equal to the iMCTA FDD target cell color dedicated to feature iMCTA load based HO developments (parameter imctaLoadBasedTargetCellColorThreshold). For example if the target cell load threshold is equal to “Yellow”, the target cell load has to be “Green” or “Yellow”.

4.20.3.8.4 TARGET FDD CELL ELIGIBILITY (USED FOR SERVICE)

For each Rab to establish, a set of cell load elementary colors is read.

A target FDD cell is eligible for iMCTA if each relevant cell load color is lower or equal to the iMCTA target

cell color triggering threshold (parameter targetCellColourThreshold):

� All Cell DL color ≤ iMCTA target cell color threshold

AND

� All Cell UL color ≤ iMCTA target cell color threshold

When a FDD cell belongs to a D-RNC but is not in the S-RNC neighbor cells provisioning, the iMCTA target Cell color threshold has a Red default color.

4.20.3.8.5 TARGET 2G CELL ELIGIBILITY

A 2G target cell is eligible if its color is lower or equal to the iMCTA target cell color triggering threshold

(parameter targetCellColourThreshold).

When a neighbour 2G cell is given by a D-RNC and cannot be found in the S-RNC provisioning, the iMCTA target Cell color threshold has a Red default color. Two colors are supported: green/red. At the cell configuration, the cell iMCTA color is green by default. For cells managed by a D-RNC, the cell iMCTA color is also green by default.

UMTS Radio Mobility



4.20.3.8.6 TARGET 2G CELL COLOR DEFINITION

The GSM target cell color can be determined two different ways:

uRRM step 1:

A GSM target cell has a red color if a handover towards this cell has been rejected for load reasons in the previous x (3g2GInhibTimer parameter value configurable). Otherwise the cell color is green. The 2G cell load detection is based on the receipt of the RANAP Relocation Preparation Failure message with a cause IE value equal to “Relocation failure in target CN/RNC or target system”. The cell color modification trigger occurrence for a GSM cell is linked to the number of HHO 3G2G attempt towards this cell. So the filtering mechanism efficiency may be lower when the trigger occurrence for a GSM cell is low.

uRRM step 2 [Global Market]:

If cell load information present in handover messages from GSM and if cell load management feature is activated, the GSM target cell color is calculated thanks to cell load information. When the 2G cell load information received from the BSC is above the configured congestion threshold, the 2G cell shall be put in Red color for a configurable time or until new cell load information for that cell is received below the congestion threshold (refer to [R7] for more details). Step 1 and step 2 information are exclusive. If cell load information element is present and feature activated, the handover reject cause will not be managed.

4.20.4 PARAMETERS

4.20.4.1 IMCTA OPTIONS

Name Object/Class Definition serviceHoRanapEnable RadioAccessService

Class 3 If set to True, the Service Handover IE (if present) will be taken into account by the RNC whatever the iMCTA triggers.

IsServiceSegmentationTopPriority

ServiceForTrafficSegmentationPriority Class3

If set to True, the service segmentation will have a higher priority than load balancing in iMCTA algorithm (option Service Segmentation activated

Is2GCellLoadInformationManagementAllowed [Global Market]


uRRM step 2 feature: if set to True, the cell load information IE (if present) will be taken into account by the RNC to set GSM cell color.

InhibitTimer3g2g RadioAccessService Class 3

If uRRM step 2 not activated: when a HO3G2G is rejected, this timer is armed for the requested target 2G cell. This cell will not be selected by the RNC until the timer elapses. If the timer has a 0 value, the timer is not armed and the cell is not filtered.

mode

FDDCell Class 3

Four modes allowed. If set to “AlarmOnly”, the feature only applies when the trigger is an Alarm HHO condition. If set to “AlarmAndCac” the feature applies for Alarm and CAC reasons. If set to “AlarmAndService” the feature applies for Alarm and Service reasons. If set to All, all iMCTA triggers apply.

hsxpaSegmentationEnable

FDDCell Class3

If set to True the iMCTA function shall not try to allocate non-HSxPA capable mobiles on a cell supporting HSxPA and HSxPA capable mobiles on a cell not supporting HSxPA. If set to false the segmentation doesn’t occurs. This option doesn’t apply in case of iMCTA

UMTS Radio Mobility



Alarm/CAC failure triggering. mobilityServiceForHsxpaEnable

FDDCell Class3

This parameter is read when a HSDPA/HSUPA capable mobile has moved through an Intra Freq Intra RNC SHO procedure. If set to False, iMCTA is not triggered after the SHO. If set to True, iMCTA function may apply.

mobilityServiceForNonHsxpaEnable

FDDCell Class3

This parameter is read when a non HSDPA/HSUPA capable mobile has moved through an Intra Freq Intra RNC SHO procedure. If set to False, iMCTA is not triggered after the SHO. If set to True, iMCTA function may apply.

originatingCellColourThresholdPerService

OriginatingCellColourThresholdConfClass Class 3

An iMCTA applies to the originating cell if its relevant cell colors are upper (worse) than this threshold. For example, if the threshold is yellow, the iMCTA applies if at least one relevant originating cell color is red. This color is taken into account when the iMCTA triggers are different from Alarm and CAC.

mode NeighbouringRNC Class 3

Two modes allowed. If set to “AlarmOnly” (default mode), the feature only applies when the trigger is an Alarm HHO condition. If set to “AlarmAndCac” the feature is activated for Alarm and CAC triggers.

targetCellColourThreshold

FDDCell Class 3

A neighboring cell is eligible as target for iMCTA if all relevant cell colors are lower (better) than this threshold. For example, if the threshold is yellow, all relevant target cell colors must be green or yellow. This color is taken into account if iMCTA triggers are different than Alarm or CAC.

userServiceSigToTrafficOnlyEnable

FddIntelligentMultiCarrierTrafficAllocation Class 3

This parameter may limit iMCTA triggering to the transition signaling to Traffic. If set to TRUE, addition of a new Traffic Rab to a current Traffic Rab, a current Traffic Rab removal, a current RAB modification or an Iu Release command will not trigger iMCTA.

is3GHandoverPreferred

FDDCell / NeighbouringRNC Class 3

Same priority can be configured for inter-frequency and 2G inter-RAT handover. Most UEs need compressed mode for the simultaneous activation of both inter-frequency and inter-RAT measurements. This simultaneous compressed mode may not be possible in certain situations, depending on RAB combination or NodeB capabilities. If simultaneous compressed mode is required but not possible then instead a single target system is measured, only. This parameter specifies whether to perform inter-frequency (3G) or inter-RAT (2G) measurements.

isGsmIratHoToNextBestCellAllowed


This parameter enables/disables the IRAT handover to the next best GSM cell if handover is not possible to the first cell due to overload.

isChangeGsmIratHoCriterionAllowed


This parameter enables/disables the change of the Service Handover criterion of CS voice calls for UMTS to GSM handover from 'should' to 'should not' if the UE is involved in an active PS call.

isImctaLoadBasedAllowed [USA Market]


Enables the target FDD cell load criteria when iMCTA reason is Alarm or CAC failure.

imctaLoadBasedTargetCellColorThreshold [USA Market]

UmtsNeighbouringRelation UmtsNeighbouringIntelligent-

A neighboring FDD cell is eligible as target for feature iMCTA load based HO developments if all relevant cell colors are lower (better) or equal than this threshold. For example, if the threshold is

UMTS Radio Mobility



MultiCarrierTrafficAllocation Class 3

yellow, all relevant target cell colors must be green or yellow.

isImctaFddLayerLoadPreCheckAllowed


Enables the target FDD carrier filtering based on cells load. A candidate target FDD layer shall be discarded and no measurements shall be activated by iMCTA if none of the candidate neighbour cells on that layer fulfil the cell load criteria. It applies when iMCTA reason is service, but may also apply to iMCTA CAC and Alarm when 34437 load criterion is used. TRUE: Enables the target FDD carrier filtering (this flag is used to control R5 of feature 34437) FALSE: Disables the target FDD carrier filtering

isImctaLoadBasedAlarmAllowed

FDDCell Class 3

Enables the cell load filtering criteria when iMCTA reason is Alarm. As a pre-condition parameter isImctaLoadBasedAllowed must be enabled. The value of parameter isImctaLoadBasedAlarmAllowed is derived from the primary cell if the primary cell is on SRNC. If the primary cell is on DRNC then the value FALSE is assumed.

4.20.4.1.1 SERVICE SEGMENTATION OPTION DEFINITION

This option applies only for iMCTA Services triggers (users and mobility). It is meant to allow the operator to define a preference between service segmentation and load balancing. For a given call, if the option is activated via the IsServiceSegmentationTopPriority flag, then the following modifications to the current iMCTA algorithm apply:

- The Load of the originating cell is not anymore taken into account to trigger the iMCTA algorithm in the case the UE capability and primary cell HSxPA capability do not match i.e.

o UE is “HSDPA capable” and Primary cell is “not HSDPA capable” o UE is “HSUPA capable” and Primary cell is “not HSUPA capable” o UE is “not HSDPA/HSUPA capable” and primary cell is “HSDPA capable” or “HSUPA

capable” - When processing the measurement reports in order to select a target cell:

o the load of the target cell is only checked with respect to the target cell colour threshold and not with respect to originating cell colour

o the target cell can only be selected if the UE/cell capability compatibility is partial or full. The definition of UE/cell capability compatibility is:

� partial= UE is HSUPA and cell is HSDPA only � full=(UE is R99 and cell is R99) OR (UE is HSDPA and cell is HSDPA or HSUPA)

OR (UE is HSUPA and cell is HSUPA) � false=(UE is R99 and cell is HSDPA or HSUPA) OR (UE is HSDPA or HSUPA and

cell is R99) cell HSDPA or HSUPA is based on O&M cell provisioing.

− On measurement report after removing target cells using the criteria above plus radio and HSxPA

criteria: o If originating and target cell have the same priority o If target cell load criteria is fulfilled o If target cell load is equal or lower than originating cell load o If UE and originating cell don't have full compatibility

the target cell is candidate. Otherwise it is discarded.

UMTS Radio Mobility



4.20.4.1.2 SERVICE HANDOVER OPTION DEFINITION

This option applies whatever the iMCTA trigger and is based on the Service Handover IE carried in the RANAP Rab Assignment and Relocation Request messages. [A1] gives the definition of this IE. This option applies to the GSM Carrier. Its priority coming from the iMCTA selected table may be updated according to the Service Handover IE value and the O&M Service Handover option value. If “ Service Handover” option is enabled, and this information element is received from the Core network in the RAB assignment request, the following rules shall apply:

� IF at least one Rab has a Service Handover IE indicates “Shall not”, the algorithm shall act as if the Priority was set to PNA (not applicable) regarding the GSM carrier for all priority tables.

� ELSE IF at least one Rab has a Service Handover IE which indicates “Should not”, the algorithm shall act as if the Priority was set to P8 (lowest) regarding the GSM carrier for the Service priority table;

� ELSE IF at least one Rab has a Service Handover IE which indicates “Should”, the algorithm shall act as if the Priority was set to P0 (highest) regarding the GSM carrier for all priority tables. However, the MSC, that sets the Service Handover IE, does not know if the UE has a simultaneous PS call. If the strategy is to keep simultaneous CS+PS calls in UMTS then the parameter isChangeGsmIratHoCriterionAllowed can be set to TRUE. In this case the RNC internally changes the received Service Handover IE from “Should” to “Should not” if the UE has a simultaneous active PS call.

The Service handover IE values depend on User subscription. P0 and P8 are RNC internal priority values which are not available at OMC-R level. It allows giving the highest /lowest priority for GSM carrier. The priority rule is the following: P0>P1>P2>P3>P4>P5>P6>P7>P8

4.20.4.1.3 HSDPA TRAFFIC SEGMENTATION OPTION DEFINITION

This option only applies for iMCTA Services triggers and doesn't apply in case of Alarm HHO and CAC failures triggers. The priority tables give a Traffic Allocation strategy at Carrier level. When the Carrier has cells with different capabilities, this option may limit the mobility towards a carrier if the eligible target cell has not the required capability. When this option is set and whatever the established traffic service the RNC has to apply the following requirements when it processes the target cell selection during iMCTA algorithm:

� shall not try to allocate non-HSDPA/HSUPA capable mobiles (R99) on a cell supporting HSDPA/HSUPA ;

� shall not try to allocate HSDPA/HSUPA capable mobiles on a cell not supporting HSDPA/HSUPA

4.20.4.2 IMCTA PRIORITY TABLES

Name Object/Class Definition AlarmPriorityTableConfClass RadioAccessService

Class3 This table gives for 2G access and 3G Fdd carrier a priority value per service type. This table is used when an iMCTA Alarm trigger is processed.

CacPriorityTableConfClass


This table gives for 2G access and 3G Fdd carries a priority value per service type. This table is used when an iMCTA CAC trigger is processed.

ServicePriorityGeneralTableConfClass RadioAccessService Class3

This table gives for each Fdd and 2G carriers a priority value per service type. This table is used when an iMCTA service trigger is processed and one of the following tables may not be used (i.e. the UE is not HSXPA or the tables are not present).

UMTS Radio Mobility



ServicePriorityTableForHsdpaConfClass RadioAccessService Class 3

This table gives for each Fdd and 2G carriers a priority value per service type. This table is used when an iMCTA service trigger is processed for a HSDPA capable mobile.

ServicePriorityTableForHsupaConfClass RadioAccessService Class 3

This table gives for each Fdd and 2G carriers a priority value per service type. This table is used when an iMCTA service trigger is processed for a HSUPA capable mobile.

ServiceSegmentationPriorityClass RadioAccessService Class3

This table gives for each Service if the Service Segmentation has a higher priority than load balancing

alarmPriorityTableConfClassId FDDCell Class 3

Pointer towards one instance of the AlarmPriorityTableConfClass tables.

cacPriorityTableConfClassId FDDCell Class 3

Pointer towards one instance of the CacPriorityTableConfClass tables.

servicePriorityGeneralTableConfClassId FDDCell Class 3

Pointer towards one instance of the ServicePriorityGeneralTableConfClass tables.

servicePriorityTableForHsdpaConfClassId FDDCell Class 3

Pointer towards one instance of the ServicePriorityTableForHsdpaConfClass tables.

servicePriorityTableForHsupaConfClassId FDDCell Class 3

Pointer towards one instance of the ServicePriorityTableForHsupaConfClass tables.

alarmPriorityTableConfClassId

NeighbouringRNC Class 3

Pointer towards one instance of the AlarmPriorityTableConfClass tables.

cacPriorityTableConfClassId NeighbouringRNC Class 3

Pointer towards one instance of the CacPriorityTableConfClass tables.

serviceSegmentationPriorityTableRef FDDCell (iMCTA) Class3

This parameter is a pointer to one of the five ServiceSegmentationPriorityClass instances

[UA06-UA07 difference]: With the feature iMCTA load based HO developments, the iMCTA Alarm and CAC priority tables have the same format as the iMCTA service priority table. It allows:

• A better control of the mobility; • limiting the number of Fdd Carriers to be measured by the UE: it reduces the UE measurements delay

and avoids asking measurements on more than 2 neighboring FDD carriers (3GPP doesn’t require a UE to measure more than to 2 neighboring FDD carriers).

iMCTA priority table

Service type 1 Service type 2 …… Service type n FDD1 Pi FDD2 Pj FDD3 Pk FDD4 Pl FDD5 Pm FDD6 Pn 2G Po OtherFDD Pp The list of services is given below in § 4.20.4.2.4 iMCTA Service Type Definition. The instance “OtherFDD” is used as default value. The RNC has to apply the following behavior when selecting candidate target layer(s) for HHO: when the frequency of a neighbour cell is not present in the Alarm or CAC tables, the priority of each service has to be read from the instance “OtherFDD” of the MO frequency. This instance was created for upgrade from UA06 to UA07 (for all iMCTA table types) with the introduction of the feature iMCTA Load Based HO developments.

4.20.4.2.1 IMCTA PRIORITY TABLE DEFINITION: GENERAL ASPECTS

When iMCTA is invoked by one of the triggers, the function has first to select the candidate target Carriers taken into account the UE capabilities and the priority of the different carriers for the request service type. The priorities per carrier and per service type are defined via O&M. The operator may give different Carrier priorities according to the iMCTA trigger (Alarm, CAC and Service).

UMTS Radio Mobility



4.20.4.2.2 IMCTA ALARM AND CAC PRIORITY TABLES DEFINITION

There is one table for Alarm and another one for CAC, they have the same format. The tables allow setting the target Radio Access technology preference between 3G and 2G when a HHO has to be processed for Alarm and CAC reasons. Since UA07.0, allows the priority setting of each FDD frequency (as for iMCTA service priority table). The different priority values are: PNA, P1…P8 with P1>P2>…>P8. If the priority is set to PNA (Priority Not Applicable), a Fdd frequency or a set of Fdd frequencies or the 2G Radio Access System shall not be considered for the request service type. For each Service type, it is possible to have the PNA value for all Access. If, after applying the different filtering, two Radio Access System are selected (Priority <>PNA), with same priority then the neighbours of both systems are measured and handover is executed to the cell reported first by the UE (typically 3G cells because the measurement is much faster than for 2G that requires BSIC verification) and eligible to iMCTA target cell criteria. FDD carriers priorities could be the same in order to allow load balancing between FDD layers. The table applies to all mobiles types (HSDPA/HSUPA capable or not) with a primary link located on the C-RNC or a D-RNC.

4.20.4.2.3 IMCTA SERVICE PRIORITY TABLE DEFINITION

The table allows setting the layer preferences between all 3G layers and the 2G layer when a HHO has to be processed for Service reason. For each service type the 2G carrier priority can be equal or different to the FDD carrier priorities. FDD carriers priorities could be the same in order to allow load balancing between FDD layers. For each Service type, it is possible to have the PNA value for all layers (FDD and 2G). The different priority values are: PNA, P1…P7 with P1>P2>….P7. If the priority is set to PNA, the carrier shall not be considered for the request service type. The table only applies to a call with a primary link located on the C-RNC. The operator can configure a specific Service table per UE type:

� iMCTA HSUPA table (optional table). If present, the table has to be used when the mobile release is HSUPA capable;

� iMCTA HSDPA table (optional table). If present, the table has to be used when the mobile is HSDPA capable. It also my used if the mobile release is HSUPA capable and the iMCTA HSUPA table is not present;

� iMCTA General table (mandatory table). The table has to be used for non HSDPA/HSUPA capable mobiles. It has also to be used in the following cases:

o When the mobile is HSDPA capable and the iMCTA HSDPA is not present; o When the mobile is HSUPA capable and the iMCTA HSDPA and HSUPA table are not

present. If the originating cell belongs to a Carrier described in the Service priority table with a priority value equal to PNA for the given service type and mobile type, the RNC has to replace the priority value with the lowest priority value (i.e. P8).

4.20.4.2.4 IMCTA SERVICE TYPE DEFINITION

The Service Type is an input to access information (i.e. priority value) in Priority tables. The goal is to establish all requested RAB on a better carrier. Whatever the result of the procedure which triggers the iMCTA, the service type is read by the RNC in its configuration parameters (DlUserService MO) based on the RABs requested by the CN which may be established or not. The list of Service types is:

UMTS Radio Mobility



� CS Speech � CS Conversational (64/64) � CS Streaming � PS Streaming � PS Interactive/Background � CS speech + other service (PS, or PS+PS...) � none

Multiple service Radio Bearers and Multiple PS Radio Bearers are mapped onto a Service Type according to the following static rule which gives the priority between RB. The “highest RB” will be the input to map the Service type. The rule is:

� conversational/speech > streaming > I/B Example: CS 64/64 + PS I/B shall be handled as CS 64/64 which is mapped onto CS conversational service. The “none” value is used to set some User Service (signaling…) ineligible to iMCTA.

Name Object/Class Definition serviceType DlUserService

Class 3 For each DlUserService Instance, a ImctaServiceTypeId is set which allows to access the iMCTA priority tables. The operator has not to modify the list without Alcatel-Lucent agreement.

4.20.4.2.5 IMCTA SERVICE SEGMENTATION PRIORITY TABLE DEFINITION

This table allows the operator to define per service if service segmentation has a higher priority than load balancing. The goal is to redirect the call on a cell with a better matching capability when the HSxPA capability of the originating cell and the UE capability do not match, independently of the load of the primary cell.

4.20.4.2.6 IMCTA SERVICE FOR TRAFFIC SEGMENTATION PRIORITY DEFINITION

This ServiceForTrafficSegmentationPriority is an input to access information (activation of service segmentation option per service) in Service Segmentation priority tables. The list of Services is the same as in Service type.


The document [R9] gives the description of the counters.

4.21. HSDPA AND HSUPA MOBILITY

This section provides a high level view of the interactions between HSDPA or HSUPA and mobility. Full details are available in § [R4] UMT/SYS/DD/013319 HSDPA System Specification and [R6] UMT/SYS/DD/018827 E-DCH System Specification. In the following sections, HSDPA call stand for a call where there is at least one traffic radio-bearer mapped on HS-DSCH in DL without traffic or signaling radio bearer on E-DCH in UL. HSUPA call stands for a call where there is at least one radio-bearer mapped on E-DCH in UL (so necessarily mapped on HS-DSCH in DL).

UMTS Radio Mobility



4.21.1 DESCRIPTION

4.21.1.1 DEPLOYMENT SCENARIOS

Different deployment scenarios are foreseen for the introduction of HSDPA/HSUPA on existing networks: HSPDA/HSUPA on a dedicated layer or on an existing layer. Note: to deploy HSUPA in a cell, it is necessary that HSDPA is also configured in this cell. This is because any radio-bearer mapped on E-DCH in uplink will necessary be mapped on HS-DSCH in downlink. However, HSDPA may be deployed in a cell without deploying HSUPA.

4.21.1.1.1 HSPDA ON DEDICATED LAYER

Different scenarios can be deployed for multi-layers networks: • HSDPA is not deployed everywhere (HSDPA can only be deployed on one frequency). This HSDPA

layer may be deployed either widely or restricted to some hot-spots and is able to manage both R99 and HSDPA/HSUPA UEs.

Layer with HSDPA configured

Layer without HSDPA

• a three-layer deployment scenario: o one reserved for R99 o one with HSDPA, used for HSDPA but with or without HSUPA o one with HSDPA and HSUPA and used for HSDPA+HUSPA

The advantage of this scenario is that there is no impact on the layer that has already been deployed.

4.21.1.1.2 HSDPA ON EXISTING LAYER

Even though deploying HSDPA and HSUPA on a separate layer is the preferred option, there is nothing that mandates to do so and HSDPA and HSUPA can be configured on any cell (knowing that HSUPA cannot be activated without HSDPA in the cell, see above). The drawback of this scenario is that HSUPA traffic may impact R99 Uplink traffic by generating interferences. When all layers support HSDPA and/or HSUPA, one of them may be tagged as “layerPreferredForR99” by configuration. If HSDPA (resp. HSUPA) is not deployed everywhere in the layer then an automatic channel type switching between DCH and HS-DSCH (resp. E-DCH) is performed when the UE enters in or leaves an HSDPA (resp. HSUPA) cell (more information are provided in paragraph 4.21.1.3). Full details are available in [R4] and [R6].

UMTS Radio Mobility



4.21.1.2 REDIRECTION AT CONNECTION SETUP

Traffic segmentation (HSDPA vs R99) can be ensured by different means, each one described in a specific section:

• either at RRC connection establishment (refer to § 4.18.1), • or at RAB assignment (iMCTA feature, § 4.19), based on the HSDPA/HSUPA capability of the mobile

and on traffic class of the RAB, • or on other iMCTA trigger (refer to § 4.19),

4.21.1.3 HSDPA AND HSUPA CALL MOBILITY PROCEDURES

This section is only applicable to HSDPA calls (mobile having at least one HS-DSCH radio-bearer, possibly in parallel with other DCH radio bearers) and HSUPA calls (at least on E-DCH radio-bearer). Mobility of R99 calls – even in an HSDPA or HSUPA cell – is handled as described in the other sections. Note: in following paragraphs, PS RABs means:

• PS I/B RABs (for HSxPA) • PS streaming RABs (for HSDPA only, if streaming on HSDPA feature activated) It does not include Conversational RABs.

4.21.1.3.1 INTRA-FREQUENCY MOBILITY

Mobility of associated DCH

Soft and softer handover are handled normally on the associated DCHs and the Active Set evaluation and primary cell selection are managed as described by sections 5.3 and 5.4.

Mobility of HS-DSCH

As specified by the 3GPP standards, HS-DSCH is established in only one cell so is never in soft handover. In Alcatel-Lucent implementation, HS-DSCH is established on the primary cell (good radio conditions and not changing too often). Each time the primary cell changes, the HS-DSCH RL is deleted on the former primary and re-established under the new primary, using a synchronized radio link reconfiguration. If the new primary cell does not support HSDPA then the RB is reconfigured to DCH. Moreover anytime an HSDPA-capable mobile (currently operating in DCH mode) enters an HSDPA primary cell it is reconfigured to HSDPA (for radio bearers that can be served on HSDPA).

Mobility of E-DCH

As specified by the 3GPP standards, there is only one serving E-DCH radio-link and it is established in the same cell that the HS-DSCH radio-link. The mobility of the E-DCH serving link is based on the same principals than the HS-DSCH one. In case of primary cell change, the E-DCH serving link and the HS-DSCH link are moved at the same time (one procedure). If the new primary cell does not support HSUPA then the RB is reconfigured to DCH in UL (it is maintained on HS-DSCH in DL if the cell supports HSDPA). On the opposite, it is reconfigured to E-DCH if the mobile comes back to HSUPA coverage. From UA06.0 release, macro-diversity of E-DCH (having non-serving E-DCH radio-links) is supported by Alcatel-Lucent (refer to § 5.3.7).

UMTS Radio Mobility



Mobility over Iur

HS-DSCH is managed over Iur. [Global Market: E-DCH is managed over Iur since UA06 (refer to [R6])]. If E-DCH support over Iur is disabled on SRNC: When the mobile moves so that the primary cell moves under the control of a drift RNC, the E-DCH radio-bearers is reconfigured to DCH in UL. When the mobile comes back under the serving RNC and the primary cell supports HSUPA, the radio bearer is reconfigured to E-DCH in UL otherwise it remains in DCH. [Global Market: If E-DCH support over Iur is enabled on SRNC then no restrictions apply to mobility over Iur.] If E-DCH support over Iur is disabled on DRNC: In case an Alcatel-Lucent RNC receives a RNSAP RL Setup or Addition or Reconfiguration with an E-DCH radio-bearer from the Iur then the procedure is refused. [Global Market: If E-DCH support over Iur is enabled on DRNC then no restrictions apply to the incoming E-DCH mobility.] [Global Market - A SRNS relocation (“UE not involved”) may be triggered for an HSxPA call on the Iur as for a R99 call.] When the Serving RNC triggers a relocation (“UE involved”), the RNC policy is the following:

• If the HSDPA capability of the UE is given in the RRC transparent container then the RNC will try to map directly PS RABs onto HS-DSCH. Otherwise a DCH resource is chosen. In case of HS-DSCH CAC failure, the RNC will perform a DCH fallback as for a RAB assignment (refer to [R4]). If the CAC also fails for the fallback, then the relocation is refused.

• If the E-DCH capability of the UE is given in the RRC transparent container then the RNC will try to map directly PS RABs onto E-DCH/HS-DSCH. In case of CAC failure on E-DCH or HS-DSCH, the RNC will perform a DCH fallback as for a RAB assignment (see [R6]). If the CAC also fails for the fallback, then the relocation is refused.

After SRNS relocation, and whatever the container content, the CRNC performs a UE capability enquiry procedure and may reconfigure the PS radio-bearers to HS-DSCH (resp. E-DCH) if not already done.

4.21.1.3.2 COMPRESSED MODE

Compressed Mode will be activated in Uplink and Downlink to perform inter-frequency and inter-RAT measurements if needed by the UE. For an HSDPA call, the Mac-hs scheduler will not schedule a UE if a gap falls into the timeslot because the UE would not be able to receive and decode the data. It will also not be scheduled if the answer (Ack/Nack) falls during a gap for the same reasons. For an HSUPA call, the Mac-e scheduler will also take into account compressed mode gaps.

4.21.1.3.3 INTER-FREQUENCY MOBILITY

Inter-frequency handover is supported for HSDPA calls and HSUPA calls as for any R99 call. And this may trigger either an intra-RNC handover (with or without Iur) or an inter-RNC handover (over Iur or with relocation procedure). The handover protocol to be performed and possible HSxPA to DCH and DCH to HSxPA reconfigurations depend on the allocation of the target cell. In case of the target cell being controlled by the SRNC, i.e.

• intra-RNC handover within the SRNC or • inter RNC handover towards the SRNC,

the PS RB will be kept (or established) on HS-DSCH (resp. E-DCH) if the target cell supports HSDPA (resp. E-DCH). If it is not the case, it is reconfigured (or kept) to DCH in downlink (resp. uplink) In case of the target cell being controlled by a DRNC, i.e.

UMTS Radio Mobility



• intra-RNC handover within a DRNC or • inter-RNC handover towards a DRNC

the inter-frequency handover may be performed over Iur or with relocation procedure depending on either or both features being enabled as depicted in figure below. Inter-frequency handover over Iur will be done with preference if enabled towards the DRNC to control the target cell (refer to §4.16 for Inter-frequency handover over Iur). If performed over Iur then only DCH to DCH handover is supported and HSxPA calls need to be reconfigured to DCH before the handover. Reconfiguration back to HSxPA will be done on the new frequency after successful handover or on the old frequency after unsuccessful handover as described for intra frequency mobility above.

IFHHO with SRNS Relocation (HSxPA or DCH)

IFHHO Procedure

(HSxPA or DCH)

HSxPA to DCH Reconfiguration

successful ?

successful ?

Target cell on DRNC and Reloc.enabled

?

Yes DCH

No HSxPA

No old freq.

Yes

No

Yes

Call on old frequency

No

IFHHO

Yes

Call on new frequency

Call on DCH ?

Yes DCH

No HSxPA

No (on DRNC or does not support HSxPA)

successful ?

Yes Enabled over Iur ?

No

HSxPA / DCH Handover

Target cell on SRNC and

HSxPA ?

Target cell on SRNC ?

Yes SRNC

No DRNC

Yes HSxPA

In case of inter frequency handover over Iur being disabled or being unsuccessful with return to old frequency, this triggers a relocation. If the target cell supports HSDPA (resp. HSUPA) and the source RNC has indicated that the UE supports HSDPA in the Rel’5 extensions (resp. HSUPA in Rel’6 extensions) of the UE capabilities put in the container then the PS I/B radio-bearers are mapped directly on HS-DSCH in downlink (resp. E-DCH in uplink). If no information about the HSDPA (resp. HSUPA) capabilities of the mobile has been provided by the source RNC then the PS radio-bearers are first mapped on DCH in downlink (resp. DCH in uplink). A UE capability enquiry is then triggered. If it happens that the UE is HSDPA (resp. HSUPA) capable then the PB radio-bearers are reconfigured to HS-DSCH in downlink if the primary cell is HSDPA (resp. E-DCH in uplink if the primary cell is HSUPA).

UMTS Radio Mobility



4.21.1.3.4 INTER-SYSTEM MOBILITY

3G to 2G handover

3G to 2G handover is supported for HSDPA/HSUPA calls. The handover is triggered on the same conditions as for non-HSDPA calls (see section 4.19).

2G to 3G handover

2G to 3G handover is supported. In case of a pure PS call, this is seen as a new Mobile Originated PS call from the target RNC (No incoming relocation as the mobile was in GSM/GPRS). The same rules as the initial admission apply, leading possibly to the allocation of HS-DSCH (resp. E-DCH) to the incoming UE.


See [R4]. See [R6].

4.21.3 ALGORITHM

See [R4]. See [R6].

4.21.4 PARAMETERS

See [R4]. See [R6]. Mobility parameters can be tuned by mobility service type.


See [R4]. See [R6].


See [R4]. See [R6].

UMTS Radio Mobility



4.22. MOBILITY IN CELL_PCH AND URA_PCH RRC STATES

4.22.1 DESCRIPTION

URA update

URA update URA update

Broadcast of URA identity

The management of the URA_PCH needs the SIB2 broadcasting. This SIB only contains: � the number of URA_identities (1..8); � the URA (UTRAN Registration Area) identity (ies) of the cell.

Note: if SIB2 is not broadcasted in a cell then a mobile in URA_PCH that has reselected this cell will perform a URA_UPDATE (change of URA), allowing the RNC to move the UE to Cell_PCH RRC state.

URA reselection process

The RNC has to assign one URA identity to the UE when it moves the mobile to URA_PCH. The RNC modifies this URA identity when an RRC Update occurs with the “change of URA” cause. When the UE reselects a cell that does not belong to this URA (ie: this URA identity is not present in SIB2), the UE performs a URA update procedure with URA update cause ‘change of URA’. On reception of the URA update for URA reselection reason, the RNC shall assigned (assuming it knows the UE) a new URA to this UE.

UE UTRAN

URA UPDATE (u-rnti)

URA UPDATE CONFIRM (u-rnti ; new URA identity)

Figure 64: Assigning a new URA

If multiple URAs are defined in the current cell, the RNC shall select the appropriate one: the one on top of the list.

UMTS Radio Mobility



IUR Management

ASSUMPTION: IT IS NOT ALLOWED TO SPREAD A URA OVER TWO RNS. The operator has to take care of it. The same management as for Cell Fach through Iur applies to CELL_PCH and URA_PCH (refer to section 4.5). Note that the release is applicable anytime the RNC receives a message from an unknown u-RNTI. Note: Alcatel-Lucent RNC will not support Paging Request over URA from the Iur and will ignore this message. Alcatel-Lucent RNC will not provide any information on URAs on the Iur (in RL Setup/Addition Response and in Uplink Signalling TransferIndication messages).

IOT Mobile restrictions

It is possible that some UEs do not support URA or CELL PCH. In case the UE does not support the RRC state, the RRC procedure used to reconfigure the UE to this state will fail (eg: The RNC will receive a Radio Bearer Reconfiguration Failure message from the mobile). If for any reason, the reconfiguration fails then the RNC shall release the RRC connection (moves UE to Idle). There is no functional consequence to this because the interest of these states vs idle is only a faster resume time.

Cell Update and URA update management

The update procedures use the following messages:

Cell reselection Used in CELL_FACH or CELL_PCH when the UE re-selects a new cell URA reselection Used in URA_PCH when the UE leaves the URA it was assigned to Periodic Cell update Used in CELL_FACH or CELL_PCH when T305 expires (periodic cell

update timer) Periodic URA update Used in URA_PCH when T305 expires (periodic URA update timer) Re-entered service area Used in CELL_FACH or CELL_PCH or URA_PCH when the UE re-

enters service area and timers T307 or T317 or T316 are running (this means that the mobile could not find any suitable cell for a certain period of time, short enough not to change to Idle mode)

The following specifies the Alcatel-Lucent UTRAN behaviour on reception of a cell update or URA update for a mobile in URA_PCH or Cell_PCH RRC state, based on the cause indicated by the UE in the message. Cell reselection On reception of the Cell update message from a mobile in Cell_PCH state, the RNC increments the counter of number of Cell reselections. If this counter reaches a configurable threshold, the RNC shall send the mobile to URA_PCH (if the operator has activated URA_PCH). Else, the RNC shall resend the mobile to Cell_PCH. In case the cell is part of new LA/RA, then a LA/RA update is performed on Cell_FACH. Periodic cell update On reception of the Cell Update message, the RNC updates the UE location and resends the mobile to Cell_PCH. It is used as supervision mechanism: the call is released in case of periodical update lack.. Re-entered service area On reception of the Cell Update message, the RNC updates the UE location and sends the mobile to URA_PCH or Cell_PCH according to what was the previous state of the mobile and has been configured by the operator for the cell. If the u-rnti is not known by the RNC (because the RNC tried to contact the UE without success so released the RRC connection), the RNC shall send an RRC Connection Release message to the UE.

UMTS Radio Mobility



URA reselection On reception of the URA update message, the RNC shall resend the mobile to URA_PCH with a new URA (the one at the head of the list defined for this cell). or If the current cell is not part of any URA, the RNC shall send the mobile to Cell_PCH (given it is allowed on the network) or Idle (if Cell_PCH is not allowed). The RNC doesn’t check if the cell is part of new LA/RA: no LA/RA update procedure is performed on Cell_FACH. Periodic URA update Nothing to do except resend the mobile to URA_PCH state keeping the same URA. It is used as supervision mechanism: the call is released in case of periodical update lack. “Unknown” u-RNTI In case the UE sends a Cell Update or URA update message with an unknown u-RNTI, the RNC shall:

� If the u-RNTI belongs to another RNS, it shall send an RRC Connection Release message (directed signalling connection re-establishment cause): see [Iur management] in a previous paragraph;

� If the u-RNTI belongs to this RNS, it shall send an RRC Connection Release to the UE. Multiple URA_update or Cell_Update The RNC may receive several URA_update or Cell_Update in case the UE did not receive the confirmation message from the RNC (eg: it has reselected another cell). In this case, the RNC shall act as for the first one received (but may assign a different URA if the cell reselected is different).


This feature is applicable when the call enters in Cell/URA PCH state.

4.22.3 ALGORITHM

The cell selection/re-selection evaluation process (see [A5]) in Cell_PCH or URA_PCH RRC state for Intra Freq, Inter Frequency or Inter rat mobility management is the same as for CELL-FACH RRC state. Please refer to section § 4.5.4.

4.22.4 PARAMETERS

The activation of using CELL/URA PCH RRC state is described in [R3]. The mobility configuration is made through the following parameter:

Name Object/Class Definition URA identity [1..8]: (0..65535)

FDDCell Class3

at least one identity is needed if URA_PCH is used (a UE moving to URA_PCH is assigned the first one in the list . If the list is not provided, the mobile shall be moved to Cell_PCH (if enabled) or idle (else).


� Ability to broadcast the configuration parameter on the radio interface. � Management of the Cell/URA update procedures.

UMTS Radio Mobility




No impact.

4.23. HCS: CELL RESELECTION CONTROL IN A HIERARCHIC AL CELL STRUCTURE [GLOBAL MARKET]

4.23.1 DESCRIPTION

The Hierarchical Cell Structure feature enables the cell reselection control procedure in a Multi Layer network. HCS algorithm is based on the classical principles of the re-selection algorithm of the UE in Idle/connected mode as defined in the sections 4.4 and 4.5 but with additional algorithms handled by the HCS and applicable to the new concept of the UE fast moving also called high mobility. This feature allows the operator to prioritize cell layers for mobiles in idle mode, Cell_Fach, and URA/Cell_PCH connected modes. The cell reselection algorithms could be also applicable to the UE speed so that fast moving UEs can be placed in large cells to avoid excessive cell reselections (i.e. macro cells/ mobility layer). In addition it allows a better radio plan management and handles the UTRAN resources with better efficiency improving the UTRAN capacity (i.e. micro cells/capacity layer), improving higher data rate services in small areas, handling others services as in private systems, and so decrease the total system cost. Also to be considered the Hierarchical Cell Structure provides the architecture of a multi-layered cellular network where subscribers are handed over from the macro to the micro or to the pico cell layer depending on the current network capacity and the needs of the subscriber. It means the cell plan has several levels.

For example fast moving terminals could be redirected to macro cell layer (i.e. mobility layer), rather low moving terminals to micro/pico cell layer (i.e. capacity layer). Note: HCS is not used by the UE for inter-RAT reselection if absolute priority based cell reselection is used for inter-RAT. (see [A5])

UMTS Radio Mobility



The 3GPP has introduced with the cell re-selection algorithm for Hierarchical Cell Structure the concept of the high mobility detection (UE fast moving) which may be used without HCS feature activation. As the traffic user demands on the network should vary in time and in space, local traffic peaks are likely to occur and so required micro cells are needed to complement the macro cells. Now with fast UE, large number of handoff between these cells may occur. Typically High mobility detection is useful in such cases, and shall avoid too much undesirable handoffs which can produce call drops. It shall also offer to reduce negative radio effect when one fast moving UE is connected to a distant macro cell, and enters a micro cell, then the unwanted radiation of the high power transmission UE may generate some interferences at the micro cell NodeB, which is tuned to lower transmission terminals. It may appear in particular radio conditions (UE at the edge of radio cells), to trigger the high mobility detection even if it’s not a real fast moving UE case.


The HCS applies to the following mobility cases: • "3G to 3G cell reselection intra-frequency in Idle/Fach mode" which allows a UMTS mobile camping on a

3G cell to reselect a cell using the same technology and frequency according to a priority level between the serving cell and its neighbouring

• "3G to 3G cell reselection inter-frequency in Idle/Fach mode", according to a priority level between the serving cell and its neighbouring

• "3G to 2G cell reselection in Idle/Fach mode" which allows a "GSM capable" UMTS mobile to reselect a GSM cell when being in idle mode in the UMTS coverage according to a priority level between the serving cell and its neighbouring, • only UTRAN/FDD and GSM Radio Access Technologies are known and supported

HCS priority level I

HCS STRUCTURE PLAN

Macro cell

Micro cells

Pico cells

HCS priority level J

HCS priority level K

FFFFm

FFFFk

FFFFn

UMTS Radio Mobility



The HCS algorithm is based on the classical principles of the re-selection algorithm of the UE in Idle/connected mode, but for R5 UE some new concepts are introduced based on the priority set to a cell for a given set of cell (Serving cell and neighbouring cells) and the high mobility detection. The new specific parameters for HCS cell re-selection procedure are controlled by the RNC. The broadcasting of these new parameters implies coding/scheduling modification for SIB3/SIB11 broadcasted on the BCCH channel in idle mode, and for SIB4/SIB12 in FACH or PCH mode if enabled.

4.23.3 ALGORITHM

As specified in [A5], the UE algorithm for cell reselection applied to HCS still defines � a criteria for UTRAN/FDD or GSM neighbouring cells tracking and measurement � a criteria S to assess FDD and GSM cells eligibility � a criteria H for HCS using a quality level threshold to prioritise cells for the ranking � a criteria R for ranking of eligible cells

The cell re-selection algorithm defined for HCS takes into account:

� Classical re-selection parameters: o Quality measured/value derived from the CPICH Ec/No or CPICH RSCP, o UE measurement for intra/inter frequency, o UE measurement for inter RAT, o Time reselection duration according to the corresponding UE state (URA/Cell PCH or Cell-

FACH), o 3GPP defined thresholds level (Qhyst1s , Qoffset1s,n,…), o Cell Ranking criteria R,

� New parameters/concepts for HCS re-selection:

o Priority levels for serving and neighbouring cells (0 to 7) as: o HCS_PRIOs: Defines the HCS priority level for serving cell, o HCS_PRIOn: Defines the HCS priority level for neighbouring cells, o HCS re-selection criterion and HCS thresholds as:

� Qhcs: Quality threshold level for applying hierarchical cell reselection, � Hs/ Hn: Quality threshold criterion for applying hierarchical cell reselection, � H criterion used for neighbour cells selection for the ranking � Additional HCS parameters (including temporary offset) for HCS criterion H and

cell-ranking criterion R,

o High mobility detection (UE fast Moving), o UE measurement for intra/inter frequency used for high mobility state detection, o UE measurement for inter RAT used for high mobility state detection,

From an algorithmic point of view the main differences with the classical reselection procedure are on the measurement rules and on the ranking algorithm.

o HCS cell-reselection procedure is based on UE measurements and the measurements rules, o The new concept of high mobility detection procedure could be applied to the HCS measurement rules

if configured, in order to detect a high mobility state. o When HCS is used SsearchHCS specifies the threshold for Srxlev below which Intra-frequency and inter-

frequency measurements of the neighbouring cell are performed.

Note: When HCS is not used the SsearchHCS applies also, in that case it specifies the threshold for Srxlev below which ranking for inter-frequency of the neighbouring cell of the serving cell is performed (see section 4.4 ).

UMTS Radio Mobility



4.23.3.1 CELL RESELECTION CRITERIA WHEN HCS IS USED

If HCS is used in the serving cell, Cell re-selection criteria apply for intra/inter frequency and inter RAT cells. Main steps Step 1: The UE measurement rules described in [A5] apply: the list of measured cells depends on HCS priority level and the UE high-mobility state. The list may be a sub-list of all provisioned neighbour cells sent in the SIB11message. Step 2: The S and H criterion apply on the measured cells to identify cells candidates for the neighbour cells ranking criterion R. The S criterion is described in the section 4.4. The quality threshold level criterion H for HCS, involving a prioritized ranking to the candidate cells, is defined as:

Hs = Qmeas,s - Qhcss Hn = Qmeas,n - Qhcsn – TOn * Ln

with:

Q meas,s , Q meas,n Measured cell quality value. The quality of the received signal expressed in CPICH Ec/N0 (dB)

QHCS s , QHCS n Quality threshold levels for applying HCS algorithmic. Ln Constant value TOn Time Offset

If at least one measured neighbor cell verifies H ≥ 0 the criterion S applies according to the high mobility state:

o If high mobility state is not active, the criterion S apply on measured cells with the highest HCS_PRIO with H ≥ 0 (use case: favour transition from mobility layer to capacity layer with the assumption of mapping mobility layer with one lowest priority );

o If high mobility state is active, the criterion S apply on measured cells with: o If (HCS_PRIOn < HCS_PRIOs), the highest HCS_PRIOn priority level which verify H ≥ 0: the

neighbor layers with the closest priority of the serving layer is selected (use case: UE leaves a serving layer coverage towards a layer with a lower and closest priority);

o If (HCS_PRIOn ≥ HCS_PRIOs), neighbour cells with the lowest HCS_PRIOn priority level which verify H ≥ 0: the neighbor layers with the closest or the same priority as the serving layer is selected (use case: UE sees new cell layers with an upper closest or equal priority);

If no cell verifies H ≥ 0 the criterion S and R are used as if HCS was not used (see S criterion of section 4.4). Step 3: The cell ranking with the cell ranking criterion R is applied by the following formula to the cells fulfilling the step 2 conditions:

Rs = Qmeas,s + Qhysts Rn = Qmeas,n - Qoffsets,n - TOn * (1 – Ln)

UMTS Radio Mobility



The best ranking cell is the cell with the highest R value. As explained in the section 4.4 the ranking is based on CPICH RSCP quality and a second ranking may occur when quality measurement is Ec/No. The selected cell has to fulfill the Access restriction rules see [A5]. TO n and Ln calculation Extract of [A5]. Time Offset (TO) applies in:

� Hn formula when Ln =1 (i.e. HCS_PRIOn <> HCS_PRIOs ) � Rn formula when Ln =0 (i.e. HCS_PRIOn = HCS_PRIOs)

Time Offset parameter applies a temporary offset value which is added to the offset Qoffsets,n in order to increase the offset and so temporary disadvantage a neighbour cell for the Hn and Rn criterion: it allows avoiding ping-pong effect.

Qmeas = quality value of the received signal HCS_PRIOs, HCS_PRIOn, = HCS priority level of the cell, TO n = TEMP_OFFSETn * W(PENALTY_TIMEn – Tn) Ln = 0 if HCS_PRIOn = HCS_PRIOs Ln = 1 if HCS_PRIOn <> HCS_PRIOs Tn = Timer - W(x) = 0 for x < 0 - W(x) = 1 for x >= 0

Hn formula: TO applies when the neighbour cell HCS priority is different from the serving cell HCS priority: the objective is to give a mean to disadvantage some neighbour cells before ranking when they belong to a layer with a priority different than the serving layer priority (use case: ping pong between cells of different priorities). Rn formula: TO applies when the neighbour cell HCS priority is equal to the serving cell HCS priority: the objective is to give a mean to disadvantage some neighbour cells ranking which belong to the same layer or to layers with equal priority: the ranking value will be decreased during TO. (use case: ping pong between cells of same priorities). TEMP_OFFSET n applies an offset to the R and H criteria for the duration of PENALTY_TIMEn after a timer Tn has started for that neighbouring cell.

T n timer definition Extract of [A5]. There is one Tn timer per neighbour measured cell. It bounds the temporary offset use. The condition for arming this timer depends on HCS_PRIOn and HCS_PRIOs parameter values:

� If (HCS_PRIOn <> HCS_PRIOs) the condition is based on the neighbour cell quality measurement without regarding the serving cell quality:

� If (HCS_PRIOn == HCS_PRIOs) the condition is based on the difference between quality measurements of the serving and the neighbour cell: the purpose is to keep the mobile on the actual layer except if the quality is “well better” on the neighbour layer.

The Tn timer is stopped when the condition is no longer fulfilled. The change of the serving cell doesn’t imply a timer stopping.

UMTS Radio Mobility



- If (HCS_PRIOn <> HCS_PRIOs) && ( Qmeas,n >= Qhcsn) Start Tn, - If (HCS_PRIOn == HCS_PRIOs) && ( Qmeas,n > Qmeas,s + Qoffsets,n) Start Tn,

Else Stop timer Tn,

Fdd Cell: If quality measurement used is CPICH Ec/No, Qoffsets,n = Qoffset2s,n . If quality measurement used is CPICH RSCP, Qoffsets,n = Qoffset1s,n. 2G Cell: Qoffsets,n = Qoffset1s,n. High mobility detection (if HCS is used) Extract of [A5]. If the number of cell reselections during period TCRmax exceeds NCR, high-mobility has been detected. When the number of cell reselection during time period TCrmaxHyst no longer exceeds NCR, UE shall:

� Continue these measurement during TCrmaxHyst; � If the criteria for entering high mobility is not detected during time period TCrmaxHyst: Exit high-mobility.

The high mobility state doesn’t mean the mobile speed is high but the number of reselection is high. The high mobility detection may be used if HCS is not used (see section 4.4)

4.23.3.2 INTER RNC CASE

In this version full HCS is applicable for intra RNC case only.

4.23.4 PARAMETERS


The “isHscUsed” parameter allows the activation/deactivation of the HCS procedure.

The “tCrMax” allows the activation/deactivation of the High mobility detection.

UMTS Radio Mobility



OAM parameter SIB Object description/comment isHcsUsed FDDCell This parameter indicates whether HCS is used in the Fdd cell

3 CellSelectionInfo sSearchRatGsm


Integer (-32..20 by step of 2) In [dB]. This specifies the 2G RAT specific threshold in the serving cell used in the inter-RAT measurement rules.

3 CellSelectionInfo sSearchHcs


Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the limit for Srxlev in the serving cell below which the UE shall initiate measurements of all neighbouring cells of the serving cell. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-frequency neighbouring cells of the serving cell.

3 CellSelectionInfo sHcsRatGsm 4 CellSelectionInfoCo

nnectedMode

Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the 2G RAT specific threshold in the serving cell used in the inter-RAT measurement rules. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-RAT neighbouring cells of the serving cell.

3 CellSelectionInfo speedDependScalingFactorTReselection


Real (0..1 by step of 0.1). This specifies the scaling (multiplication) factor to be used by the UE in idle mode or RRC connected mode states for the parameters Treselections or Treselections,PCH or Treselections,FACH in case high-mobility state has been detected.

3 CellSelectionInfo interFreqScalingFactorTReselection 4 CellSelectionInfoCo

nnectedMode

Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-frequency case.

3 CellSelectionInfo interRatScalingFactorTReselection


Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-RAT case.

3 CellSelectionInfo tCrMax


Enumerated (not used, 30, 60, 120, 180, 240). This specifies the duration for evaluating allowed amount of cell reselection(s). This parameter is mapped to non-TCRmax or TCRmax IE for SIB3/4 filling depending of HCS use or not.

3 CellSelectionInfo nCR 4 CellSelectionInfoCo

nnectedMode

Integer (1..16). This specifies the maximum number of cell reselections. This parameter is mapped to non-NCR or NCR IE for SIB3 filling depending of HCS use or not.

3 CellSelectionInfo tCrMaxHyst


Enumerated (not used, 10, 20, 30, 40, 50, 60, 70). This specifies the additional time period before the UE can exit high-mobility. This parameter is mapped to non-TCrmaxHyst or TCrmaxHyst IE for SIB3/4 filling depending of HCS use or not.

3 CellSelectionInfo hcsPrio


Integer (0..7). This specifies the HCS priority level (0-7) for serving cell . HCS priority level 0 means lowest priority and HCS priority level 7 means highest priority.

3 CellSelectionInfo qHcs 4 CellSelectionInfoCo

nnectedMode

Integer( 0..99). This specifies the quality threshold levels for applying prioritised hierarchical cell re-selection

3 CellSelectionInfo sLimitSearchRat


Integer (-32..20 by step of 2). This threshold is used in the measurement rules for cell re-selection when HCS is used. It specifies the RAT specific threshold (in dB) in the serving UTRA cell above which the UE may choose to not perform any inter-RAT measurements in RAT "m".

UMTS Radio Mobility




OAM parameter SIB Object description/comment 11 UmtsNeighbouringRelation hcsPrio

12 FddNeighCellSelectionInfoConnectedMode

Integer (0..7). ). This specifies the HCS priority level (0-7) for the neighbouring cells. HCS priority level 0 means lowest priority and HCS priority level 7 means highest priority.

11 UmtsNeighbouringRelation qHcs 12 FddNeighCellSelectionInfoCon

nectedMode

Integer( 0..99). This specifies the quality threshold levels for applying prioritised hierarchical cell re-selection.

11 UmtsNeighbouringRelation penaltyTime


Integer(0, 10, 20, 30, 40, 50, 60) in sec. This specifies the time duration for which the TEMPORARY_OFFSETn is applied for a neighbouring cell.

11 UmtsNeighbouringRelation temporaryOffset1


Integer(3, 6, 9, 12, 15, 18, 21, inf) in dB. This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY_TIMEn. It is used in case the quality measure for cell selection and re-selection is set to CPICH RSCP.

11 UmtsNeighbouringRelation temporaryOffset2


Integer(2, 3, 4, 6, 8, 10, 12, inf) in dB. This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY_TIMEn. It is used for FDD cells in case the quality measure for cell selection and re-selection is set to CPICH Ec/No.


OAM parameter SIB Object description/comment 11 GsmNeighbouringCell hcsPrio

12 GsmCellSelectionInfoConnMode

Integer (0..7). This specifies the HCS priority level (0-7) for the neighbouring cells. HCS priority level 0 means lowest priority and HCS priority level 7 means highest priority.

11 GsmNeighbouringCell qHcs 12 GsmCellSelectionInfoC

onnMode

Integer( 0..99). This specifies the quality threshold levels for applying prioritised hierarchical cell re-selection.

11 GsmNeighbouringCell penaltyTime 12 GsmCellSelectionInfoC

onnMode

Integer(0, 10, 20, 30, 40, 50, 60) in sec. This specifies the time duration for which the TEMPORARY_OFFSETn is applied for a neighbouring cell.

11 GsmNeighbouringCell temporaryOffset1

12 GsmCellSelectionInfoConnMode

Integer (3, 6, 9, 12, 15, 18, 21, inf)in dB. This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY_TIMEn. It is used for GSM cells in case the quality measure for cell selection and re-selection is set to CPICH RSCP.


• Support of the corresponding system information transmission, • Support of a hierarchical radio plan, • Support of radio parameters setting with high accuracy, • Support of mobility detection for better efficiency even if not mandatory for HCS processing,


No impact.

UMTS Radio Mobility



5. COMMON PROCEDURES

5.1. PERIODIC MEASUREMENT REPORTING MODE

One possible reporting mode is the periodic reporting mode. This section indicates in which order the various processes are performed in the RNC when receiving a periodic Measurement Report message from the mobile (e.g. each 500 msec). 1. alarm handover criteria evaluation (inter-system, intra-frequency inter-RNC or inter-frequency handover

criteria evaluation based on current primary cell) 2. active set evaluation process 3. primary cell determination process 4. measurement configuration update (either modification of intra-frequency monitored set, or inter-system

measurements…) This reporting mode for intra-frequency measurements is not recommended in this version (but is still available for trace purpose or state transitioning enhancement).

5.2. INTRA-FREQUENCY EVENT TRIGGERED MEASUREMENT REPORTING MODE

5.2.1 DESCRIPTION

Another reporting mode is the intra-frequency event triggered reporting mode. This is the ALU UTRAN nominal mode for all features except call trace function. The use of “event triggered” reporting has a direct impact on the following mechanisms:

• primary cell determination (refer to § 5.4) • active set management (refer to § 5.3) • alarm measurement criteria (refer to § 5.9) • inter-frequency blind handover (refer to § 5.2.3) • Radio Link colour determination (refer to § 5.2.3)

The target cell choice for alarm handover is not impacted by the event triggered reporting mode. The basic principle of event handling is that the event semantic is taken into account in the implementation, e.g. event 1A reception leads to radio link addition, while event 1B involves a RL deletion. If not specified otherwise, “Measured results” reported by the UE on other cells than the one having triggered the event are not used in mobility handling algorithms e.g. measured results reported in event 1A shall not lead to RL deletion in the current active set. The main reason for is about “Time To Trigger”. Making a decision at the RNC side until Time To Trigger has elapsed at the UE side may lead to unstable situations (ping-pong …). The main principle of intra-frequency event triggered is to

• Rely on intra frequency events for management of intra-frequency mobility: configuration of events (1A, 1B, 1C, 1D, 1E, 1F, 2D and 2F)

1A to add a cell in the active set (1) 1B to remove a cell in the active set (1) 1C to replace a cell in the active set (1) 1D to replace the primary cell in the active set (1) 2D to enter the alarm condition and possibly start inter-freq or inter-RAT measurements (2) 2F to leave the alarm condition and possibly stop inter-freq or inter-RAT measurements (2)

UMTS Radio Mobility



Note: Although being related to intra-frequency measurements, 2D and 2F are categorized in the ‘inter-frequency” event group, which helps to decrease the number of simultaneous intra-frequency events required.

• Also configure events (1E and 1F) if the feature SHO enhancement (release UA04.1) is enabled (on a per user service basis)

1E to add a radio link (1) 1F to remove a radio link (1)

Note: The release information above is added in order to distinguish between this feature (refer to [R5]) and the later SHO enhancements.

• Also configure, when the alarm condition is fulfilled, inter-frequency or inter-RAT measurements in periodic mode

• Also configure event (1J) used for E-DCH active set management if parameter isRrcEdchEvent1JAllowed is set to TRUE (refer to [R6] for details).

1J a radio link that is DCH active set but not in the E-DCH active set becomes stronger than one radio link that is in the E-DCH active set

• Also configure events (6A and 6B) if the feature “Alarm HHO based on UE Tx Power” is enabled and the call uses DCH transport for uplink

6A The UE Tx Power becomes larger than an absolute threshold 6B The UE Tx Power becomes less than an absolute threshold

(1) Measurement result is Ec/N0

(2) Measurement results are Ec/N0 and RSCP

5.2.2 CONFIGURATION

The event-triggered mode is chosen if this reporting mode is allowed in the FDD Primary Cell (O&M Fdd Cell parameter isEventTriggeredMeasAllowed) where the UE is established and if the preferred event-triggered mode is FULL-EVENT at the RNC level. During all the life of a call, this choice of the reporting mode is computed at each transition to CELL DCH (CELL_FACH or xxx_PCH or Idle to CELL_DCH whether the call is handled over DCH or HSDPA). And when the mode “Full-Event” is selected at the establishment in CELL_DCH, there is no mechanism to switch the mode during this phase of the call in CELL_DCH. If event-triggered is configured in the cell where the UE transits to CELL_DCH, the RNC chooses this measurement reporting mode after the transition to CELL_DCH. If the event-triggered reporting is configured, all SHO related events are configured, plus events required for Alarm Measurement criteria. If the call is setup on CELL_FACH or if an Always-On takes place, the events are configured once the RB is setup or reconfigured in CELL_DCH state. If the call is setup on CELL_DCH, the events are configured once the Signalling Radio Bearer is setup. According to [R3]

• Event 1A may be configured in SIB11

UMTS Radio Mobility



• A MEASUREMENT CONTROL will be sent after the transition to CELL_DCH to configure 1A (the 1A configured by SIB11 is overridden) to 1J events.

The intra-frequency cell list will be updated by the first MEASUREMENT CONTROL sent after the transition to CELL_DCH i.e. the entire cell list is sent to the UE (by removing all the cells and giving the new list) to ensure that the cell list in the UE and the RNC are exactly the same. As a principle, if all parameters related to a specific event are unchanged, the event is not configured again. On the other hand, if SHO and Alarm Measurement parameters are changing after a change of primary cell or a RB reconfiguration, all events need to be re-configured, as in call setup case.

5.2.2.1 COMMON ID PROCEDURE HANDLING

The Common ID procedure is used in the early phase of the connection setup by the Core Network to provide the RNC with the user IMSI identity. This identity is stored by the RNC in order to allow paging coordination, i.e. the possibility to make the relationship between an on-going connection and a paging received by another Core Network domain so that the Paging is sent as a type 2 on DCCH. In the “National Roaming” context, the user IMSI is also used to restrict the list of neighbouring cells, depending on the “IMSI-PLMN access right” table defined at the RNC level. From that perspective, it may happen that Measurement Control RRC messages are sent to the UE on reception of the Common ID message on the Iu. There is no impact on the measurement configuration. An update of the monitored set cells (intra-frequency and/or inter-frequency and/or inter-RAT) may be required.

5.2.2.2 MEASUREMENT CONTROL FAILURE

On reception of a MEASUREMENT CONTROL FAILURE from the UE, the RNC will: • if the UE is pre-release 5 (i.e. R99, R4) the message is ignored. This may lead to a drop call since

measurement reporting may be not configured properly and therefore mobility management may not be handled.

• If the UE is Release 5 o if the failure is due to a configuration of inter-frequency/inter-RAT alarm measurements then

the RNC takes no action. The timeout of the Blind HO timer is normally running and a Blind Handover procedure is triggered at its expiration.

o For 6A and 6B, the RNC has to memorize the non support of this measurement avoiding another sending of this configuration at next measurement update

• Deactivate the Compressed Mode in the NodeB in case of Measurement Control Failure due to CM activation for an HSxPA call.

5.2.2.3 SUMMARY

According to [A7], the UE shall be able to support in parallel per category up to Ecat reporting criteria as defined in following table:

UMTS Radio Mobility



25.133 Requirements for reporting criteria per meas urement category

Measurement category E cat Note Intra-frequency 8 Inter-frequency 6 Inter-frequency, virtual active set 4 Inter-RAT 4 Only applicable for UE with this

capability UE internal measurements 8 Traffic volume measurements 2 + (2 per Transport

Channel)

Quality measurements 2 per Transport Channel UP measurements 2 Only applicable for UE with this

capability. All the events needed in UA07.1 Alcatel-Lucent implementation are listed Appendix 1.

5.2.3 FEATURE INTERWORKING

5.2.3.1 RADIO LINK COLOR

Once that the event reporting mode is introduced, the radio link colour evaluation as currently implemented for periodical reporting (see [R7] for details) needs to be updated. If event reporting mode is configured, the radio link colour evaluation is based on the measurement results available in the event reporting and other RRC messages to refresh the RL colour. The major drawback of this solution is that in very low mobility scenarios (i.e. number of event reports is low) the RL colour may not reflect the current status of the RL

5.2.3.2 SRLR BLIND WINDOW

Synchronous Radio Link Reconfiguration (SRLR) may be performed at any time during connection lifetime (Always-On, incoming PS on a CS call, RB adaptation …). During SRLR processing time, the RNC is unable to maintain the active set. In periodic reporting mode, all measurement received during this phase are put aside, and the active set management process is resumed on the basis of measurements received once the SRLR is complete. In event reporting mode, the situation is different, as critical events may have been received during the SRLR phase. As from 25.331 RRC specifications, some events as 1A, 1B, 1C and 1J can be reported periodically, but others like 1D, 1E, 1B and 1F cannot. Based on the events received during the SRLR time window, the RNC applies a specific process described below. This process is also applicable to other RRC procedures such as “active set update”. Active Set processing during the blocking phase:

• Take into account all received event 1F (if one RL is remaining at least). • Take into account all received event 1B (if one RL is remaining at least) or the last one if

isOne1bStorageAllowed is set to TRUE. • Take into account the last received event 1A or 1C (if there is enough room in Active Set at least for

1A). • Take into account the last received event 1E (if there is enough room in Active Set at least). • Take into account the last received event 1J (if there is enough room in Active Set at least). • Take into account the last received event 1D. If the triggering cell is in the Monitored Set (possible for

UE not in R5), a RL Addition can be performed with this cell.

UMTS Radio Mobility



The actions of RL Addition/Deletion have to be decided to keep a not empty Active Set and to respect the Maximum number of RL in it.

5.2.3.2.1 EVENT 1A, 1C, 1E, 1J

The RNC processes the last 1A, 1C, 1E or 1J event received during the SRLR window, so that the corresponding Radio Link is added to the active set just after the completion of the SRLR. In case of the change of the DLAsConf, the received 1A, 1C, 1D, 1E, 1J events with the old configuration (previous DLAsConf) are available. Even if the new configuration is different, they are used to take a mobility decision at the end of a Blocking Phase. Event 1A and 1C will be processed before event 1B stored in parallel if this event 1B is from a UE later than R99 and the parameter isOne1bStorageAllowed is set to TRUE.

5.2.3.2.2 EVENT 1B, 1F

If the parameter isOne1bStorageAllowed is set to TRUE then only the last received event 1B will be stored for UEs later than R99 because those UEs are capable to repeat event 1B as well. If received during the SHO blocking window (i.e. during the NBAP procedure execution), 1B and 1F are treated by the RNC at the end of a Blocking Phase. Event 1B from a UE later than R99 will be processed after any event 1A or 1C stored in parallel if the parameter isOne1bStorageAllowed is set to TRUE.

5.2.3.2.3 EVENT 1D

The last 1D event received during the SRLR window, is treated by the RNC.

5.2.3.2.4 EVENTS 2D, 2F, 6A, 6B

These events are processed when received since they correspond to arm and stop timer. The Hard HO treatment has priority on Soft HO, which has priority on alarm measurements activation.

5.2.4 PARAMETERS

Name Object/Class Definition isEventTriggeredMeasAllowed FDDCell

Class3 Flag which enables the event reporting mode

isOne1bStorageAllowed RadioAccessService Class3

enables/disables the storage of only one event 1B on a per RNC basis

5.3. ACTIVE SET MANAGEMENT

The Active Set is managed differently according to the reporting mode (periodic or intra-frequency event triggered). The Active Set is supported over Iur. Note: RNC does not check cell barring information in active set management.

5.3.1 ALGORITHM FOR PERIODIC REPORTING MODE

The active set evaluation process is characterized by: - periodic evaluation: performed at each reception of periodic RRC MEASUREMENT REPORT - decision based on relative criterion: threshold applied on (max CPICH Ec/No – CPICH Ec/No(cell to be

evaluated))

UMTS Radio Mobility



- a hysteresis is applied for radio link removal which leads to two thresholds: ADD and DROP thresholds - continuity in active set is insured: at least the best cell of the current active set is maintained after new

active set evaluation even if it is outside window. The algorithm is the following: 1. Find the cell with the highest CPICH Ec/No. Let’s call it cell(0) with Ec/No(0) 2. Compare (Ec/No(0) – Ec/No(i)) to drop_threshold for cells in the current active set

- Keep as eligible in the active set those which Ec/No(0)-Ec/No(i) < drop_threshold - Cells to be dropped = the others - If all the cells of the current active set are non eligible, keep at least the best one

3. Compare (Ec/No(0) – Ec/No(i)) to add_threshold for cells not in the current active set - Put as eligible those which Ec/No(0)-Ec/No(i) < add_threshold

4. Rank all the eligible cells - Keep the max_legs first cells in the active set - but insuring that at least one cell from the current active set is in the list

All the parameters used in the algorithm above are attached to the current primary cell.

CPICH Ec/No

Max CPICH Ec/No add_thresholddrop_threshold

Cell in current active setCell not in current active set

Measurement periods

Figure 65: algorithm for active set management

5.3.2 ENHANCED ALGORITHM FOR PERIODIC REPORTING MODE

The algorithm specified in the section above is based on a relative threshold comparison. Based on the field observations and CDMA experience, the following points have been identified as important factors to better manage the mobility:

• Add a good link to the Active Set as quick as possible • Maintain the quality of the Active Set by preventing weak links to get into the Active Set and dropping

them from the Active Set as quick as possible As a consequence, an “enhanced SHO management algorithm” is available, working as follows:

• If a radio link from the active set satisfies either the relative drop_threshold comparison, or a comparison with an absolute threshold ShoLinkAdditionCpichEcNoThreshold, the radio link is removed from the active set.

• Similarly, if a radio link from the monitored set satisfies either the relative add_threshold comparison, or a comparison with an absolute threshold ShoLinkDeletionCpichEcNoThreshold, the radio link is added to the active set.

UMTS Radio Mobility



The first condition is illustrated by the following picture.

Radio Link to be deleted Cells 1 2 3 4 5 6 7

ShoLinkDeletionCpichEcNoThreshold

Links already in the Active Set

Measured Links Max CPICH Ec/No

Delta Drop Threshold

Links in the Active Set (final) Figure 66: SHO enhancement - link deletion

The second condition is illustrated by the following picture.

Link to be added to the Active Set

Cells 1 2 3 4 5 6 7

ShoLinkAdditionCpichEcNoThreshold

Links already in the Active Set

Measured Links Max CPICH Ec/No

Delta Add Threshold

Links in the Active Set (final) Figure 67: SHO enhancement - link addition

This algorithm can be completely or partially de-activated. Please check the [parameter] section for further details. Moreover this enhanced SHO management algorithm enables the use of CIO (cell individual offset) parameter in the evaluation of active set update and primary cell determination algorithm.

5.3.3 PARAMETERS FOR PERIODIC REPORTING MODE

The parameters are:

Name Object/Class Definition legDroppingDelta SoftHoConf

Class3 threshold to withdraw a cell from the active set, referred to as drop_threshold in the section above

legAdditionDelta SoftHoConf Class3

threshold to add a cell in the active set, referred to as add_threshold in the section above

UMTS Radio Mobility



maxActiveSetSize SoftHoConf Class3

maximum number of legs in macro-diversity (from 1 to 6), referred to as max_legs in the section above

ShoLinkDeletionCpichEcNoThreshold SoftHoConf Class3

Absolute threshold for radio link deletion

ShoLinkAdditionCpichEcNoThreshold SoftHoConf Class3

Absolute threshold for radio link addition

ShoLinkDeletionAbsoluteThresholdEnable SoftHoConf Class3

If enabled, the absolute threshold for radio link deletion is applied

ShoLinkAdditionAbsoluteThresholdEnable SoftHoConf Class3

If enabled, the absolute threshold for radio link addition is applied

When the current primary cell pertains to the DRNC and as far as neither the class of cell nor the cell parameters (which are proprietary) are not reported over the Iur, the set of parameters which will be used for the algorithm will be a default set defined per Neighbour RNC. Cell Individual Offset CIO will be used in the AS evaluation algorithm only when at least one of the ShoLinkXxxAbsoluteThresholdEnable flag is True.

5.3.4 CASE OF INTRA-FREQUENCY EVENT-TRIGGERED REPORTING MODE

5.3.4.1 DESCRIPTION OF EVENT-TRIGGERED REPORTING MEASUREMENTS BASED ON RELATIVE THRESHOLDS

In event triggered mode, events 1A and 1B are used, so that Radio Link Addition (resp. Radio Link Deletion) are actually triggered by the reception of event 1A (resp. 1B) from the mobile. As in [A4], the condition for event 1A reporting is as follows:

)2/(10)1(1010 111

aaBest

N

iiNewNew HRLogMWMLogWCIOLogM

A

−−⋅⋅−+

⋅⋅≥+⋅ ∑

=

If W is set to 0, event 1A allows the same behavior as with current algorithm. This works the same way for event 1B:

),2/(10)1(1010 111

bbBest

N

iiOldOld HRLogMWMLogWCIOLogM

A

+−⋅⋅−+

⋅⋅≤+⋅ ∑

=

In order to trigger a report, the triggering condition has to be valid for a period of time named “time to trigger”. This parameter is configurable for each event.

• CIONew and CIOOld refer to as Cell Individual Offset. • MBest and MOld refer to as CPICH Ec/No measurements made by the mobile. • H1a and H1b refer to as hysteresis parameters. They can be set to the value of hysteresis1A and

hysteresis1B. • R1a and R1b refer to as reporting range parameters. They are configured to the values of

cpichEcNoReportingRange1A and cpichEcNoReportingRange1B respectively.

In case of “SHO leg number” limitation or if the Active Set is full, it is critical to put the strongest cells in the active set (among the ones being reported by 1A). For that purpose, event 1C is (A non-active primary CPICH becomes better than an active primary CPICH) needed to ensure the RNC keeps the main radio links in the active set, as with the existing “periodic reporting” mechanism. The following picture illustrates a case where 1C event is needed, based on the following assumptions: The active set is limited to 2 links – for illustration purpose only

UMTS Radio Mobility



Events 1A and 1B are configures as above (CIO = 0, W = 0, H1A = H1B = 0

Reporting event 1A

Reporting event 1C

Measurement quantity

Time

P CPICH 1

P CPICH 2

P CPICH 3

R1A

R1B

Figure 68: event 1C use case

At the beginning, cell 1 and 2 are part of the active set, cell 1 being the strongest one. As Cell 3 crosses R1A, event 1A is reported. However, cell 3 is not added to the active set, as the active set size is limited to 2 radio links only. Further on, as 1C is reported, cell 3 is added and cell 2 is removed, so that the active set is based on the strongest cells from the monitored set. Unless 1C is available, this cannot be achieved, as in this case cell 2 remains above R1B. As in [A1], event 1C is triggered by the following condition:

2/1010 1cInASInASNewNew HCIOLogMCIOLogM ++⋅≥+⋅

• CIONew and CIOInAS refer to as Cell Individual Offset.

• MBest and MInAS refer to as CPICH Ec/No measurements made by the mobile.

• H1c refer to as hysteresis parameter. It can is set to the value of hysteresis1C.

In order to trigger a report, the triggering condition has to be valid for a period of time named “time to trigger”. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger1A, timeToTrigger1B, timeToTrigger1C). The recommended value for timeToTrigger1B will be greater than that for timeToTrigger1C. This may result in the scenario shown in figure below. Event 1C triggered by a non-active cell may be sent earlier than event 1B even if the trigger condition for event 1B started to apply before. However the non-active cell to appear as a candidate for replacement is too weak and should not be added to the active set.

UMTS Radio Mobility



Strongest active set cell

Reporting Range for e1a

Reporting Range for e1b

Time-to-Trigger e1b

Time-to-Trigger e1c

Non-active cell

2nd active set cell

Problem: e1c is sent earlier than e1b, but the non-active cell is too weak and should not be added to the active set. The 2nd active set cell should be just removed from the active set.

Pilo

t str

engt

h

Time

Figure 69: Enhanced event 1C handling

The algorithm was enhanced such that replacement of an active set cell by a non-active cell reported in Event 1C depends on a threshold thr_replace as defined in formula below:

• thr_replace = CPICH_Ec/N0 (strongest active set cell) - Reporting Range R1b A non-active cell will only be added if its reported CPICH_Ec/N0 plus the Cell Individual Offset is greater than thr_replace:

• Reported CPICH_Ec/N0 + CIO > thr_replace Otherwise the non-active cell will not be added and only the weak active set cell will be removed as if Event 1B would have been received. The RRC protocol allows configuring the event 1A trigger by either Monitored Set cells or Detected Set cells or both Monitored and Detected Set cells. The following events need to be configured:

Reporting quantity Event id Triggering condition CPICH Ec/No 1A Monitored set cells or

Monitored and Detected set cells

CPICH Ec/No 1B Active set cells CPICH Ec/No 1C Monitored set cells

The RRC protocol allows configuring periodic reporting of event 1A, 1C and 1B (only from Release 5) as long as the reporting criteria are still valid.

5.3.4.2 DESCRIPTION OF EVENT-TRIGGERED REPORTING MEASUREMENTS BASED ON ABSOLUTE THRESHOLDS

This will be achieved by using 2 events, namely 1E and 1F on CPICH Ec/No measurements. The following equations [A1] describe the “triggering condition” for 1E:

2/10 11 eeNewNew HTCIOLogM +≥+⋅

UMTS Radio Mobility



and 1F:

,2/10 11 ffOldOld HTCIOLogM −≤+⋅

• H1e and H1f refer to as hysteresis parameters. They can is set to the value of hysteresis1E and

hysteresis1F. • T1e and T1f refer to as absolute thresholds. • CIOOld and CIONew refer to as Cell Individual Offset. • MNew refers to as CPICH Ec/No or CPICH RSCP measurement made by the mobile.

The following picture illustrates event 1E and 1F reporting, in case CIO and H parameters are set to 0. In this figure, the P-CPICH 3 will trigger an event 1E and P-CPICH 1 will trigger an event 1F.

Absolute threshold of 1F event

Absolute threshold of 1E event

Reporting event 1E


Time

P CPICH 1

P CPICH 2

P CPICH 3

Reporting event 1F

Figure 70: Events 1E and 1F

In order to trigger a report, the triggering condition has to be valid for a period of time named “time to trigger”. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger1E, timeToTrigger1F). The RRC protocol allows configuring the event 1E trigger by either Monitored Set cells or Detected Set cells or both Monitored and Detected Set cells. The events used to support this feature would be as follows:

Reporting quantity Event id Triggering condition CPICH Ec/No 1E All Monitored set cells or

Monitored and Detected set cells

CPICH Ec/No 1F All active set cells Please note that CIO is a configurable parameter defined against the primary cell for each of its neighbour cell.

5.3.4.3 ALGORITHM

In case of intra-frequency Event-Triggered Reporting mode, the RNC behaviour is as follows:

• If either 1A or 1E (if configured) event is received for a cell of the monitored set, the corresponding radio link is (possibly) added to the active set. In case of several Monitored Set to Add, only the best ordered in the IE “Event Results” of the Measurement Report is added. The reception of an event 1A or 1E is received for a detected cell will generate a trace and the cell which trigs the event will not be

UMTS Radio Mobility



added in the active set unless special conditions for event 1A do apply. If the parameter isDetectedSetCellsAllowed is set to TRUE and the parameter detectedSetCellAddition is set to TRUE or AUTOMATIC then Detected Set cells reported in event 1A will be added to the active set in the following scenario: If the combined intra frequency Cell Info List exceeds its maximum size then cells with lower ranking priority need to be cut off from the list (refer to 5.5.3) which in consequence does no more represent the complete neighborhood of the active set. The cells having been cut off may reappear as Detected Set cells reported by the UE and will then no longer be ignored but be added to the active set.

• If either 1B or 1F (if configured) event is received for a cell of the active set, the corresponding radio link is removed from the active set

• If 1C event is received, the RNC will replace the cell in the Active Set indicated in the measurement report with the cell triggering this event. If several Active Set cells are included in the “Event Results” and are worse than the Monitored Set cell to add, the RNC deletes them: so the RNC can resize the Active Set. Detected Set cells will be added to the active set under the same conditions as described for event 1A above. However a non-active cell (i.e. Monitored Set cell or possibly Detected Set cell) will not be added to the active set if it is too weak as described for enhanced event 1C handling above. In this case event 1C will be acted upon as if event 1B would have been received i.e. only a radio link removal will result.

In this version, the RNC will not have a special handling to avoid a potential ping-pong generated by RNC actions (i.e. RL addition/deletion) triggered by

• The reception of one event based on absolute thresholds (1E/1F) followed by the reception of one event based on relative thresholds (1A/1B). Typical example of this scenario could be the addition of a new RL triggered by 1E followed immediately by the deletion of this RL triggered by 1B of the same cell.

Or • The reception of one event based on relative thresholds (1A/1B) followed by the reception of one event

based on absolute thresholds (1E/1F). Typical example could be the addition of a new RL due to 1A followed immediately by deletion of the same RL due to 1F reception.

If the Primary cell needs to be removed due to event 1B or 1C reception then the RNC will first determine the new Primary cell (the best cell of the remaining active set) and in case of a HSPA call perform the serving cell change before executing the active set update (see also section 5.4). Note: If event 1F identifies the Primary cell to be removed then the event is ignored. As in “SHO enhancement” specification for release UA04.1, the radio link addition/deletion absolute criteria makes use of CIO parameter defined in the RNC database (Cell Individual Offset). Therefore:

• If the “SHO enhancement” feature (release UA04.1) is active, the CIO will be sent to the UE through the Measurement Control message. In this case, CIO will be applied by the UE on events 1E and 1F, but also on events 1A, 1B, 1C and 1D (for R5 UEs if configured), as in the current “SHO enhancement” implementation

• If the “SHO enhancement” feature (release UA04.1) is not active, the CIO will not be sent to the UE and events 1E and 1F are not configured.

Note: The release information above is added in order to distinguish between this feature (refer to [R5])and the later SHO enhancements.

As specified in [R10], the initial power of the Radio Link to be added not only depends from CPICH Ec/No measurement of the new cell, but also on the measurements reported for the other cells in the active set. This is still the case when event-triggered measurement reports are used. The measured results included in the Measurement Report are configured to be reported on Active Set cells and Monitored Set cells and on Detected Set cells (if configured via the parameter isDetectedSetCellsAllowed). If Detected Set cells are reported the RNC will trace this as specified in § 5.3.6.

The reception of an event during a procedure in progress may induce the storage of the event in order to solve the issues: refer to § 5.2.3

UMTS Radio Mobility



5.3.4.4 CONFIGURATION

As only one intra-frequency measurement quantity is actually required (CPICH Ec/No), all intra-frequency events and measurements can be configured in a single message. As in [A4], some events reporting are not repeated. In order to limit the risk of loosing an event on the radio interface because of bad transmission conditions, all intra-frequency event reports are configured in RLC Acknowledged Mode. The overall structure of the intra-frequency MEASUREMENT CONTROL message is as follows. Up to 8 events can be configured in a single message.

§10.2.17 Meas. Control

Common part (reporting type…)

§10.3.7.36 Intra-freq measurements

Common part (meas quantities…)

Event 1A

Event 1B

…

§10.3.7.39 Intra-freq meas rep criteria

Figure 71: intra-frequency Measurement Control message structure

In the §10.2.17 common part: The IE Measurement reporting mode contains the specific information:

• Measurement Report Transfer Mode: Acknowledged mode RLC • Reporting Mode: Event trigger

In the §10.3.7.36 common part: • Intra-frequency measurement quantity: CPICH Ec/No • Intra-frequency reporting quantity:

o For active set cells: CPICH Ec/No and CPICH RSCP o For monitored set cells: CPICH Ec/No and CPICH RSCP o For detected set cells: CPICH Ec/No

In all the tables below: “not needed” means the IE is not part of the message, as it is not needed by 3GPP 25.331 specifications “not used” means the IE is optional and not used in this implementation.

5.3.4.4.1 1A EVENT CONFIGURATION

Information Element/Group name Need Parameter Value Parameters required for each event OP >Intra-frequency event identity MP “1a” >Triggering condition 1 CV–clause 0 Not needed >Triggering condition 2 CV–clause 6 “Monitored Set Cells” or “Monitored and

Detected Set cells” >Reporting Range Constant CV–clause 2 Use cpichEcNoReportingRange1A

parameter >Cells forbidden to affect Reporting range CV–clause 1 Not used

UMTS Radio Mobility



Information Element/Group name Need Parameter Value >W CV–clause 2 Use weight1A parameter >Hysteresis MP Use hysteresis1A parameter >Threshold used frequency CV-clause 3 Not needed >Reporting deactivation threshold CV–clause 4 Use value (maxActiveSetSize-1) >Replacement activation threshold CV-clause 5 Not needed >Time to trigger MP Use timeToTrigger1A parameter >Amount of reporting CV–clause 7 Use amountRep1A parameter >Reporting interval CV–clause 7 Use repInterval1A parameter >Reporting cell status OP Use maxNbReportedCells1A parameter

Remark: The “Reporting deactivation threshold” IE indicates the maximum number of cells allowed in the active set in order for event 1a to occur, so that if the active set is limited by the maxActiveSetSize parameter, the value of this IE shall be set to (maxActiveSetSize-1). The purpose of this IE is to avoid the UE to report event 1A if the active set size limit is reached.

5.3.4.4.2 1B EVENT CONFIGURATION

Information Element/Group name Need Parameter Value Parameters required for each event OP >Intra-frequency event identity MP “1b” >Triggering condition 1 CV–clause 0 “Active Set Cells” >Triggering condition 2 CV–clause 6 Not needed >Reporting Range Constant CV–clause 2 Use cpichEcNoReportingRange1B

parameter >Cells forbidden to affect Reporting range CV–clause 1 Not used >W CV–clause 2 Use weight1B parameter >Hysteresis MP Use hysteresis1B parameter >Threshold used frequency CV-clause 3 Not needed >Reporting deactivation threshold CV–clause 4 Not needed >Replacement activation threshold CV-clause 5 Not needed >Time to trigger MP Use timeToTrigger1B parameter >Amount of reporting CV–clause 7 Not needed >Reporting interval CV–clause 7 Not needed >Reporting cell status OP Use maxNbReportedCells1B parameter >Periodical reporting information-1b CV–clause 9 Use amountOfRep1B and repInterval1B

parameters

Remark: As a 3GPP R5 improvement, a periodical reporting IE has been added for event 1B. This change is made on a backward compatible way, meaning that this IE, when present, will be decoded by R5 and above UE, and ignored by R99 UEs. This IE is part of Alcatel-Lucent implementation and is sent each time event 1B is configured.

UMTS Radio Mobility



5.3.4.4.3 1C EVENT CONFIGURATION

Information Element/Group name Need Parameter Value Parameters required for each event OP >Intra-frequency event identity MP “1c” >Triggering condition 1 CV–clause 0 Not needed >Triggering condition 2 CV–clause 6 Not needed >Reporting Range Constant CV–clause 2 Not needed >Cells forbidden to affect Reporting range CV–clause 1 Not used >W CV–clause 2 Not needed >Hysteresis MP Use hysteresis1C parameter >Threshold used frequency CV-clause 3 Not needed >Reporting deactivation threshold CV–clause 4 Not needed >Replacement activation threshold CV-clause 5 Use maxActiveSetSize parameter >Time to trigger MP Use timeToTrigger1C parameter >Amount of reporting CV–clause 7 Use amountOfRep1C parameter >Reporting interval CV–clause 7 Use repInterval1C parameter >Reporting cell status OP Use maxNbReportedCells1C parameter

Remark: The “Replacement activation threshold” indicates the minimum number of cells allowed in the active set in order for event 1C to occur. The purpose of this IE is to avoid the UE to report event 1C if the active set size limit is not reached.

5.3.4.4.4 1E EVENT CONFIGURATION

Information Element/Group name Need Parameter Value Parameters required for each event OP >Intra-frequency event identity MP “1e” >Triggering condition 1 CV–clause 0 Not needed >Triggering condition 2 CV–clause 6 “Monitored Set Cells” or “Monitored and

Detected Set Cells” >Reporting Range Constant CV–clause 2 Not needed >Cells forbidden to affect Reporting range CV–clause 1 Not used >W CV–clause 2 Not needed >Hysteresis MP Use hysteresis1E parameter. >Threshold used frequency CV-clause 3 Use cpichEcNoThresholdUsedFreq1E >Reporting deactivation threshold CV–clause 4 Not needed >Replacement activation threshold CV-clause 5 Not needed >Time to trigger MP Use timeToTrigger1E parameter >Amount of reporting CV–clause 7 Not needed >Reporting interval CV–clause 7 Not needed >Reporting cell status OP Use maxNbReportedCells1E parameter

UMTS Radio Mobility



5.3.4.4.5 1F EVENT CONFIGURATION

Information Element/Group name Need Parameter Value Parameters required for each event OP >Intra-frequency event identity MP “1f” >Triggering condition 1 CV–clause 0 “Active Set Cells” >Triggering condition 2 CV–clause 6 Not needed >Reporting Range Constant CV–clause 2 Not needed >Cells forbidden to affect Reporting range CV–clause 1 Not used >W CV–clause 2 Not needed >Hysteresis MP Use hysteresis1F parameter. >Threshold used frequency CV-clause 3 Use cpichEcNoThresholdUsedFreq1F >Reporting deactivation threshold CV–clause 4 Not needed >Replacement activation threshold CV-clause 5 Not needed >Time to trigger MP Use timeToTrigger1F parameter >Amount of reporting CV–clause 7 Not needed >Reporting interval CV–clause 7 Not needed >Reporting cell status OP Use maxNbReportedCells1F parameter

5.3.5 PARAMETERS FOR EVENT REPORTING MODE

All event parameters may be provisioned at OAM level except the Reporting Deactivation Threshold which is equal to “ maxActiveSetSize (set by OAM)”.

Name Object/Class Definition isDetectedSetCellsAllowed RadioAccessService

Class3 Allows tracking of detected cells

detectedSetCellAddition

FDDCell Class3

Allows addition of detected set cells to the active set.

cpichEcNoReportingRange1A UsHoConf Class3

Relative CPICH Ec/No threshold for SHO Radio Link Addition.

hysteresis1A UsHoConf Class3

CPICH Ec/No hysteresis for link addition in Active Set

weight1A UsHoConf Class3

defines the weight to configure for the triggering of event 1A in Full Event mode

timeToTrigger1A UsHoConf Class3

Period of time during which the event condition has to be satisfied before sending event 1A

amountRep1A MeasurementConfClass Class3

Amount of periodical reporting for event 1A

repInterval1A MeasurementConfClass Class3

Interval of periodical reporting for event 1A

maxNbReportedCells1A MeasurementConfClass Class3

Maximum allowed number of cells to report with event 1A

cpichEcNoReportingRange1B UsHoConf Class3

Relative CPICH Ec/No threshold for SHO Radio Link Deletion.

hysteresis1B UsHoConf Class3

CPICH Ec/No hysteresis for link deletion in Active Set .

weight1B UsHoConf Class3

defines the weight to

UMTS Radio Mobility



configure for the triggering of event 1B in Full Event mode

timeToTrigger1B UsHoConf Class3

Period of time during which the event condition has to be satisfied before sending event 1B

isOne1bStorageAllowed

Radio Access Service Class 3

Allows storage of only the latest received event 1B while another procedure is in progress

amountRep1B MeasurementConfClass Class3

Amount of periodical reporting for event 1B

repInterval1B MeasurementConfClass Class3

Interval of periodical reporting for event 1B

maxNbReportedCells1B MeasurementConfClass Class3

Maximum allowed number of cells to report with event 1B

hysteresis1C UsHoConf Class3

CPICH Ec/No hysteresis for cell replacement in Active Set

timeToTrigger1C UsHoConf Class3

Period of time during which the event condition has to be satisfied before sending event 1C

amountRep1C MeasurementConfClass Class3

Amount of periodical reporting for event 1C

repInterval1C MeasurementConfClass Class3

Interval of periodical reporting for event 1C

maxNbReportedCells1C MeasurementConfClass Class3

Maximum allowed number of cells to report with event 1C

isEnhanced1cHandlingAllowed

Radio Access Service Class 3

Allows to prevent weak non-active radio links from being added to the active set

isEvent1EUsed UsHoConf Class3

If enabled, the absolute threshold for radio link addition is applied

hysteresis1E UsHoConf Class3

CPICH Ec/No hysteresis for absolute threshold link addition in Active Set

timeToTrigger1E UsHoConf Class3

Period of time during which the event condition has to be satisfied before sending event 1E

maxNbReportedCells1E MeasurementConfClass Class3

Maximum allowed number of cells to report with event 1E

cpichEcNoThresholdUsedFreq1E UsHoConf Class3

Absolute CPICH Ec/No threshold for SHO Radio Link Addition.

isEvent1FUsed UsHoConf Class3

If enabled, the absolute threshold for radio link deletion is applied

hysteresis1F UsHoConf Class3

CPICH Ec/No hysteresis for absolute threshold link deletion in Active Set

timeToTrigger1F UsHoConf Class3

Period of time during which the event condition has to be satisfied before sending event 1F

maxNbReportedCells1F MeasurementConfClass Class3

Maximum allowed number of cells to report with event 1F

UMTS Radio Mobility



cpichEcNoThresholdUsedFreq1F UsHoConf Class3

Absolute CPICH Ec/No threshold for SHO Radio Link Deletion.


5.3.6.1 COUNTERS

The following counters are defined: Per FDDCell (the Primary RL of the UE is on this FDDCell). All the following counters are of cumulative type:

• Number of Event 1A triggered by a Cell of the Monitored Set (triggered by event 1A reception). • Number of Event 1B (triggered by event 1B reception). • Number of Event 1C (triggered by event 1C reception). • Number of Event 1D (triggered by event 1D reception). • Number of Event 1E triggered by a Cell of the Monitored Set (triggered by event 1E reception). • Number of Event 1F (triggered by event 1F reception). • Number of Event 1J (triggered by event 1J reception). • Number of Event 2D (triggered by event 2D reception). • Number of Event 2F (triggered by event 2F reception). • Indication of at least one available Call Failure Trace due to a Detected Cell (triggered by reception of

event 1A or 1E triggered by a Detected Cell). • Number of Event 6A (triggered by event 6A reception). • Number of Event 6B (triggered by event 6B reception).

Per neighboring RNC (The Primary RL of the UE is on this Neighboring RNC). All the following counters are of cumulative type:

• Number of Event 1A triggered by a Cell of the Monitored Set (triggered by event 1A reception). • Number of Event 1B (triggered by event 1B reception). • Number of Event 1C (triggered by event 1C reception). • Number of Event 1D (triggered by event 1D reception). • Number of Event 1E triggered by a Cell of the Monitored Set (triggered by event 1E reception). • Number of Event 1F (triggered by event 1F reception). • Number of Event 2D (triggered by event 2D reception). • Number of Event 2F (triggered by event 2F reception). • Indication of at least one available Call Failure Trace due to a Detected Cell (triggered by reception of

event 1A or 1E triggered by a Detected Cell). • Number of Event 6A (triggered by event 6A reception). • Number of Event 6B (triggered by event 6B reception).

5.3.6.2 TRACES

If the MIB flag RadioAccessService.isDetectedSetCellsAllowed is TRUE, the RNC requests the UE: • to trigger the following events on Detected Cells also:

o event 1A, where triggering Cells are both Detected Set Cells and Monitored Set Cells, o event 1E, where triggering Cells are both Detected Set Cells and Monitored Set Cells,

• To report the measurement of the Detected Cells in the Measured Result part of these events.

If a Detected Cell is reported by the UE, the related counter will be incremented and a Call Failure Trace will be triggered based on a filtering mechanism to avoid overload in both RNC and OMC due to too many Call Failure Traces. This filtering mechanism allows to have at most one Call Failure Trace in a given period (e.g. 15 seconds – static value cpTimerFileringCallFailureTrace -), for a set of calls. For the Call Failure Trace, the intra-frequency part of the RRC Measurement Report message and the scrambling code of the Detected Cell are traced.

UMTS Radio Mobility



5.3.7 E-DCH ACTIVE SET MANAGEMENT

From UA06.0, the E-DCH active set can have up to 4 links that are a subset of DCH active set. The serving link is always the primary cell of the DCH active set. All links added to (resp. removed from) the DCH active set are also added, if compatible, to (resp. removed from) the E-DCH active set. If the E-DCH active set is full and a new primary cell is elected which is not in E-DCH active set, this cell is added to E-DCH active set (as serving) and the former primary is removed from E-DCH active set. A new event 1J can be managed: a radio link that is DCH active set but not in the E-DCH active set becomes stronger than one radio link that is in the E-DCH active set. On event 1J report, one link (given in the measurement report) is removed from the E-DCH active set (but kept in the DCH one) and is replaced as non-serving by a link of the DCH active set (also given the measurement report). For all details on this feature, refer to [R6] UMT/SYS/DD/018827 E-DCH System Specification.

5.4. PRIMARY CELL DETERMINATION

5.4.1 DESCRIPTION

The primary cell is a sort of reference cell for the UE. It is used for monitored cells set determination and also as a pointer to mobility parameters, i.e. parameters with a cell granularity which are to be used for a mobile are those corresponding to its primary cell. Note: RNC does not check cell barring information in primary cell determination.

5.4.2 CASE OF INTRA-FREQUENCY PERIODIC REPORTING MODE

The determination of a new primary cell is performed after each “active set evaluation” process.

The algorithm is the following: After the active set evaluation process, a candidate cell for new primary cell is selected according to the following condition: - the cell which was already in the active set (so that its neighbouring is already known even if this

cell is located on a DRNC) and which has the best CPICH Ec/No

Two cases must be considered: - either this candidate cell = current primary cell, in this case the new primary cell = current primary

cell - or this candidate cell is different from the current primary cell. In this case:

o if CPICH Ec/No(candidate cell) – CPICH Ec/No(current primary cell) > DropPriRL new primary cell = candidate primary cell

o else the new primary cell = current primary cell

UMTS Radio Mobility



5.4.3 CASE OF INTRA-FREQUENCY EVENT-TRIGGERED REPORTING MODE

5.4.3.1 DESCRIPTION

The primary cell determination will be usually based on event 1D reception. Note: In addition a primary cell selection can be triggered by event 1B or 1C if the event requests the deletion of the current primary cell (see also section 'Algorithm' in 5.3.4). In the following the normal case of event 1D is described but the same behaviour applies also in case of event 1B or 1C with primary cell removal. In [A4], event 1D is triggered on a condition relative to active set or monitored set measurements, as in the following formula (applicable to CPICH Ec/No measurements):

2/1010 1dBestNotBest HLogMLogM +⋅≥⋅

In 3GPP R5, the definition of event 1D has been changed to take into account CIO parameters. In this formula, CIO will only be applied by R5 UEs, and only if requested by a configuration flag present in event 1D configuration sent in Measurement Control message:

2/1010 1dBestBestNotBestNotBest HCIOLogMCIOLogM ++⋅≥+⋅

• H1d refers to as hysteresis parameter. This parameter will be set to the value of hysteresis1D parameter.

• CIONotBest and CIOBest refer to as Cell Individual Offset.

• MBest and MNotBest refer to as CPICH Ec/No measurements made by the mobile. The following picture illustrates event 1D reporting, in case CIO parameters are set to 0, cell (1) being the current primary. Event 1D is reported once cell (2) measurement quantity exceeds cell (1) by H1d/2.

Reporting event 1D


Time

P CPICH 1

P CPICH 2

P CPICH 3

H1d/2

Figure 72: event 1D

As in existing periodic measurement based algorithm, a hysteresis can be used, either cell dependent (through the Cell Individual Offset parameter) or absolute (through the H1D parameter).

UMTS Radio Mobility



5.4.3.2 ALGORITHM

The primary cell determination will be based on event 1D reception. Based on the reception of this event, the RNC stores the new primary, and applies the current process used in case of change of primary cell.

The 1D event can be triggered by a cell in the Active Set for R5/R6 UEs or in the Monitored Set for R99/R4 UEs.

Since the events 1A, 1C are also configured (see section 5.3) it is assumed that the new primary cell is already in the Active Set when an 1D event is triggered as explained in the following. This will be typically ensured if the time to trigger of 1D is greater or equal than the time to trigger of events 1A or 1C. It should be noted that a monitored set cell that needs to be included in the active set will trigger first an 1A event if its CPICH Ec/No is lower than the best cell in the Active set but entering in its reporting range or 1C event if the Active Set is full and this cell is better than the worse in the Active Set. An event 1D will typically be triggered by a cell better than the best in the active set. Therefore due to the triggering conditions definition of these events and if the time to trigger of 1D is greater or equal than 1A and 1C typically the 1D will be triggered by a cell in the active set. When CIO is used it may happen that 1A event is not triggered but 1D event is triggered.

If the event 1D is triggered by a monitored cell, the RL will be added in the Active Set if not full. If the Active Set is full, then the event1D will provide the replacement of the worse cell in the Active Set.

If “SHO enhancements” (release UA04.1) is enabled and the useCIOfor1D is set to TRUE then CIO values are configured in the UE if the UE is Release 5.

Note: The release information above is added in order to distinguish between this feature (refer to [R5]) and the later SHO enhancements.

A new primary cell will also be defined if the current primary cell will be removed due to reception of RL deletion events.


Refer to § 5.3.4 / configuration for common part of Measurement Control message.

5.4.3.3.1 1D EVENT CONFIGURATION

Information Element/Group name Need Parameter Value Parameters required for each event OP >Intra-frequency event identity MP “1d” >Triggering condition 1 CV–clause 0 Not needed >Triggering condition 2 CV–clause 6 Not needed >Reporting Range Constant CV–clause 2 Not needed >Cells forbidden to affect Reporting range CV–clause 1 Not used >W CV–clause 2 Not needed >Hysteresis MP Use hysteresis1D parameter. >Threshold used frequency CV-clause 3 Not needed >Reporting deactivation threshold CV–clause 4 Not needed >Replacement activation threshold CV-clause 5 Not needed >Time to trigger MP Use timeToTrigger1D parameter >Amount of reporting CV–clause 7 Not needed >Reporting interval CV–clause 7 Not needed >Reporting cell status OP Use maxNbReportedCells1D parameter >Use CIO CV–clause 10 Use useCIO1D parameter

UMTS Radio Mobility



5.4.4 PARAMETERS

The parameters are:

Name Object/Class Definition rrcIntraFreqMeasurementDropPrimaryRlDelta UsHoConf

Class3 hysteresis for primary cell modification, referred to as DropPriRL in the section above.

useCIOfor1D MeasurementConfClass Class3

This flag indicates if CIO parameter has to be taken into account in 1D triggering condition

hysteresis1D UsHoConf Class3

CPICH Ec/No hysteresis primary cell determination

timeToTrigger1D UsHoConf Class3

Period of time during which the event condition has to be satisfied before sending event 1D.

maxNbReportedCells1D MeasurementConfClass Class3

Maximum allowed number of cells to report with event 1D

When the current primary cell pertains to the DRNC and as far as neither the class of cell nor the cell parameters (which are proprietary) are not reported over the Iur, the set of parameters which will be used for the algorithm will be a default set defined per Neighbour RNC.

5.5. LIST OF COMPOUNDING CELLS FOR THE MONITORED SE T DEFINITION

5.5.1 DESCRIPTION

The object of the section is the introduction of dynamic compounding cell lists in connected mode. This section is based on the feature called UMTS composite neighbour list. Compounding list functionality is the capability for the RNC:

o To dynamically create the neighbour list a UE will monitor, when in dedicated mode, depending on the “radio” neighbourhood of this UE, this neighbourhood being either defined by the active set, or by measurements.

o To send, through RRC Measurement Control message, this compound list to UE A new algorithm (type 1) to compute the compound neighbour cell list has been introduced for intra-frequency, inter-frequency and 2G inter-RAT neighbour cells. In the latter cases only those cells which are supported by the UE according to its capabilities will be considered for addition to the compound neighbour list.

5.5.2 APPLICABILITY

The feature is efficient if the intra frequency -, inter frequency – or inter RAT neighbour of each Fdd cell is optimized. In this case there will be enough space in the Measurement Control message to add neighbour cells of active cells other than those of the primary cell. It applies for calls in cell-DCH state only.

UMTS Radio Mobility



5.5.3 ALGORITHM

The best cell is the cell with the best CPICH Ec/No. If feature compounding list is not activated:

• The monitored set is the neighbouring list of the primary cell. If feature compounding list is activated: � Three different algorithms (PRL, Type1 and Type2) are available for intra frequency neighbour cells and

two different algorithms (PRL and Type1) are available for inter frequency - or inter RAT neighbour cells. The algorithm will be selected according to the value of primary cell parameter • typeOfCompoundingNeighbourListIntraFreq • typeOfCompoundingNeighbourListInterFreq • typeOfCompoundingNeighbourListInterRAT respectively:

• Type PRL:

The monitored set is the neighbouring list of the primary cell. The behavior is the same as if feature compounding list is not activated.

• Type 1:

Compound neighbour list is build from all active set cells. The neighbors are selected into the compound list based on (given in order of significance) • The RNC selects the first N cells from the prioritized neighbour list of the primary cell (N stands

for parameter numOfPrimaryCellNeighbourIntraFreq, numOfPrimaryCellNeighbourInterFreq or numOfPrimaryCellNeighbourInterRAT respectively)

• It adds cells with the highest number of occurrences of the cell in the neighbor lists of the active set cells

• If some neighbour cells have the same occurrence, it selects the cell with the highest measured quality of the active set cell

• In case of same quality, it selects cells with higher priority of neighbour cell (parameter neighbourCellPrio or sorting order for DRNC)

• If the maximum number of allowed cells in the compound neighbor list (parameter maxCompoundingListSizeIntraFreq, maxCompoundingListSizeInterFreq or maxCompoundingListSizeInterRAT respectively) is exceeded then the lower priority cells are discarded.

• Type 2 (only applicable for intra frequency neighbour cells): The monitored set is built as the union of o The primary cell plus its static neighbour list for dedicated mode o Either the best cells of the active set and their static neighbour list for dedicated mode, when the

connection is engaged in soft or softer HO, until:

� the last leg and its static neighborhood list for dedicated mode has been added,

� or the list reaches maxSizeCompoundingList cells.

o Or the N first (bests) measured cells and their static neighbour list for dedicated mode, when the connection is not engaged in soft or softer HO. Until:

� the new monitored cell set goes up to maxNbOfMonitoredCellForNonShoCompoundList cells ,

� or the list reaches maxSizeCompoundingList cells;

UMTS Radio Mobility



� or until the last measured cell.

The compound intra frequency neighbour cell list shall be computed when

• state transition to Cell_DCH, • successful hard handover, • change of primary cell or • active set update

has occurred. The compound inter frequency neighbour cell list shall be computed when

• change of primary cell or • active set update

has occurred while inter frequency measurements are ongoing or when

• a new RRC Measurement Control message for inter-frequency measurements (measurement type 2)

has to be sent to UE. The compound inter RAT neighbour cell list shall be computed when

• a new RRC Measurement Control message for 2G inter-RAT measurements (measurement type 3)

has to be sent to UE.

Whatever the neighbor building list method, the neighbour list updates only include the cells to be removed and to be added (delta between the previous neighbourhood and the new neighbourhood). In case of intra frequency neighbour cells there is a special handling such that no update will be sent to UE if cells have been removed only but no cells have been added.

5.5.4 PARAMETERS

Name Object/Class Definition maxCompoundingListSizeIntraFreq RadioAccessService

Class3 Maximum number of cells in the intra-freq compounded list

maxCompoundingListSizeInterFreq RadioAccessService Class3

Maximum number of cells in the inter-freq compound list

maxCompoundingListSizeInterRAT RadioAccessService Class3

Maximum number of cells in the 2G inter-RAT compound list

isCompoundingCellListActivated


Used to activate or inhibit the compounded list feature

typeOfCompoundingNeighbourListIntraFreq FDDCell Class 3

Used to determine the algorithm for intra-frequency neighbor list creation for dedicated measurements. Possible values are PRL, Type1, Type2

typeOfCompoundingNeighbourListIntraFreq NeighbouringRNC Class 3

Used to determine the algorithm for intra-frequency neighbor list creation for dedicated measurements. Used when primary cell is on

UMTS Radio Mobility



DRNC. Possible values are PRL, Type1, Type2

typeOfCompoundingNeighbourListInterFreq FDDCell Class 3

Used to determine the algorithm for inter-frequency neighbor list creation for dedicated measurements. Possible values are PRL, Type1

typeOfCompoundingNeighbourListInterFreq NeighbouringRNC Class 3

Used to determine the algorithm for inter-frequency neighbor list creation for dedicated measurements. Used when primary cell is on DRNC. Possible values are PRL, Type1

typeOfCompoundingNeighbourListInterRAT FDDCell Class 3

Used to determine the algorithm for inter RAT neighbor list creation for dedicated measurements. Possible values are PRL, Type1

typeOfCompoundingNeighbourListInterRAT NeighbouringRNC Class 3

Used to determine the algorithm for 2G inter-RAT neighbor list creation for dedicated measurements. Used when primary cell is on DRNC. Possible values are PRL, Type1

numOfPrimaryCellNeighbourIntraFreq FDDCell Class 3

The minimal number of intra-frequency neighbor cells of the primary cell to be definitely included in the compound neighbor list.

numOfPrimaryCellNeighbourIntraFreq NeighbouringRNC Class 3

The minimal number of intra-frequency neighbor cells of the primary cell on DRNC to be definitely included in the compound neighbor list.

numOfPrimaryCellNeighbourInterFreq FDDCell Class 3

The minimal number of inter-frequency neighbor cells of the primary cell to be definitely included in the compound neighbor list.

numOfPrimaryCellNeighbourInterFreq NeighbouringRNC Class 3

The minimal number of inter-frequency neighbor cells of the primary cell on DRNC to be definitely included in the compound neighbor list.

numOfPrimaryCellNeighbourInterRAT FDDCell Class 3

The minimal number of 2G inter-RAT neighbor cells of the primary cell to be definitely included in the compound neighbor list.

numOfPrimaryCellNeighbourInterRAT NeighbouringRNC Class 3

The minimal number of 2G inter-RAT neighbor cells of

UMTS Radio Mobility



the primary cell on DRNC to be definitely included in the compound neighbor list.

umtsFddNeighbouringCell-List[].neighbourCellPrio

FDDCell Class 3

The priority of intra-frequency or inter-frequency neighbour cells

gsmNeighbouringCell-List[].neighbourCellPrio

FDDCell Class 3

The priority of 2G inter-RAT neighbour cells


The following counters are defined on FDDCell basis

• VS.MeasurementControlCellListSize Size of the compound intra frequency neighbor list

• VS.ExceededAggregateCellListSizeIntraFreq Amount by which the maximum intra-frequency neighbor list size is exceeded.

• VS.AggregateCellListAmbiguousCellIntraFreq The aggregate intra-frequency neighbor list contains an ambiguous cell.

• VS.MeasCtrlCellListSizeInterFreq Size of the compound inter-frequency neighbor list

• VS.ExcdAggrCellListSizeInterFreq Amount by which the maximum inter-frequency neighbor list size is exceeded

• VS.AggrCellListAmbigCellInterFreq The aggregate inter-frequency neighbor list contains an ambiguous cell.

• VS.MeasCtrlCellListSizeInterRAT Size of the compound 2G inter-RAT neighbor list

• VS.ExcdAggrCellListSizeInterRAT Amount by which the maximum 2G inter-RAT neighbor list size is exceeded

• VS.AggrCellListAmbigCellInterRAT The aggregate 2G inter-RAT neighbor list contains an ambiguous cell

5.6. MANAGEMENT OF SYSTEM INFORMATION BLOCKS (SIB)

5.6.1 SIB UPDATE

During procedures like cell search or cell (re)selection, the UE may read some system information (SIB) broadcasted on the FDD cell. If the operator modifies an FDD cell attribute, this updated attribute is broadcasted by a System Information Block (SIB1, SIB2, SIB3, SIB4, SIB5, SIB6, SIB11 or SIB12, SIB19) as follows: • The SRNC sends the content of all SIB to the NodeB (NBAP System Info Update procedure), which leads it

to update the broadcasted SIB content with an updated value tag • Then the UE’s in idle mode are notified by paging from RNC which forces them to re-acquire the new Sys.

Info. • For the UE in cell FACH state, they are notified by a SYSTEM INFORMATION CHANGE INDICATION

message. • For the UE in URA PCH or CELL PCH state, the behaviour is the same than in Idle date (type 1 paging) Note 1: The SIB7 filling is managed by the NodeB. Note 2: SIB4, SIB12 and SIB19 are sent only if parameters SIB4Enable, SIB12Enable, SIB19Enable and isDynamicSibAlgoWithSBAllowed are set to TRUE (refer to § 4.5.4).

UMTS Radio Mobility



5.6.2 SIB REPETITION PERIOD

In UA05.0, a dynamic SIB scheduling algorithm sets the repetition period (IB_SG_REP) and the position (IB_SG_POS) of each SIB according to the number of SIB segments needed [A3]. The algorithm uses the following constraints:

� MIB block has a repetition period set to 8 and a position set to 0 ;

� SIB1 and SIB7 blocks have the same repetition period set to 16 and a start position set to 2;

� SIB3 shall have a RP0 repetition period between 32 and 128;

� SIB2, SIB5, SIB6 and SIB11 shall have a RP1 repetition period between 32 and 256.

The setting of RP0 has a higher priority than RP1 i.e. the algorithm tries to find the lowest repetition period value for RP0 first then for RP1.

In UA06.0, with introduction of SIB4 and SIB12, the dynamic SIB scheduling algorithm is modified. This new algorithm is used if parameter isDynamicSibAlgoWithSBAllowed is set to TRUE. It uses the following constraints: • Limitation of the number of MIB segments. It shall not exceed one segment. Use of a SB1 block when all

scheduling information cannot be coded in one MIB segment: the SIB scheduling information (whatever the SIB) which cannot be encoded in MIB are encoding in SB1.

• MIB block has a repetition period set to 8 and a position set to 0 ;

• SIB1 and SIB7 blocks have the same repetition period set to 16 and a start position set to 2;

• SIB3 and SIB4 shall have the same RP0 repetition period between 32 and 128;

• SIB2, SIB5, SIB6, SIB11 and SIB12 shall have the same RP1 repetition period between 32 and 256.

• The SB1 repetition period is set to the lowest repetition period of SIB(s) (RP0 or RP1) which may be addressed by SB1.

In UA07.1.2, with introduction of SIB19, the dynamic SIB scheduling algorithm is modified. This new algorithm is used if parameter isDynamicSibAlgoWithSBAllowed is set to TRUE, parameters isSib19Allowed and sib19Enable are set to TRUE. It uses the following constraints: • Limitation of the number of MIB segments. It shall not exceed one segment. Use of a SB1 block when all

scheduling information cannot be coded in one MIB segment: the SIB scheduling information (whatever the SIB) which cannot be encoded in MIB are encoding in SB1.

• MIB block has a repetition period set to 8 and a position set to 0 ;

• SIB1 and SIB7 blocks have the same repetition period set to 16 and a start position set to 2;

• SIB3 and SIB4 shall have the same RP0 repetition period between 32 and 128;

• SIB2, SIB5, SIB6, SIB11, SIB12 and SIB19 shall have the same RP1 repetition period between 32 and 256.

• The SB1 repetition period is set to the lowest repetition period of SIB(s) (RP0 or RP1) which may be addressed by SB1.

UMTS Radio Mobility



5.7. INTRA-FREQ MEASUREMENTS CONFIGURATION VIA SIB1 1

The UTRAN provides UEs in other state than Cell-DCH with the configuration of intra-frequency measurements via the SIB11. This allows the activation of the intra-frequency measurement event 1A for each mobile entering in Cell-DCH state. These UEs acquire intra-frequency configuration contained in SIB11. They can start and report their intra-frequency measurements without waiting any RRC Measurement Control message. For event triggered reporting only event 1A is configured.

See reference document [R3] UMT/SYS/DD/013000 Mobility Performance Improvements.

5.8. DHO MANAGEMENT

This section provides an overview of the management of diversity handover (uplink) in Alcatel-Lucent UTRAN nodes.

SRNC

NodeB 2 NodeB 3

DRNC

UE

Iub

Iur

MSC/SGSN

Iu

NodeB 1

Figure 73: Macro-diversity in uplink

At the NodeB level: If several radio links are active for the same UE in a NodeB, the NodeB performs radio link recombination, so that there is only one transport connection (AAL2 CID for ATM, or UDP port for IP) for the same transport bearer (DCH, MAC-d flow for HS-DSCH or E-DCH) on the Iub for all combined radio links. This is what is done in NodeB 2 in the figure above. The MRC (Maximum Ratio Combining) algorithm implemented in the BTS makes use of conventional "Rake receiver" techniques, i.e. all the different paths (or at least the ones received with the highest energy) are recombined in the rake receiver before channel decoding. At the DRNC level: The Cid from the Iub interface are only switched to the Iur (in the figure above, the 2 data streams from NodeB 2 and NodeB 3 are switched to the Iur between the DRNC and the SRNC). In this version, Radio Link recombination is not supported at the DRNC. It means that, if a "Radio Link Addition" is received from the SRNC, requesting the DRNC to perform diversity recombination, the request will be rejected by the Alcatel-Lucent DRNC if two different Node Bs are involved under the drift (but accepted if only one Node B). At the SRNC level: All the Radio Links terminating at the SRNC level are recombined by the SRNC (i.e. the data streams from NodeB 1 and the 2 streams from the Iur in the figure above).

UMTS Radio Mobility



The recombination process performed by the SRNC is actually a frame selection process, based on the payload CRC, and TB CRCI (CRC Indicator) and QE (Quality Estimate) fields received from each data stream. This process works as follows: • the payload CRC of the UP frames (if included) is checked. Any frames with bad CRC is rejected • in each frame, only TB with a "correct" CRCi are kept. Others are rejected. • in case TB from different stream have a "correct" CRCi, the TB with the best QE if eventually selected • anyway, if the QE is not good enough, the CRCi will be considered as "not correct" regardless of the value

received from the NodeB

5.9. ALARM HANDOVER AND ALARM MEASUREMENTS

5.9.1 OVERVIEW

In this version of the document, alarm handover is a Hard Handover triggered by the iMCTA function when an Radio alarm condition is detected. The others reasons for processing a Hard Handover managed by the iMCTA function are: CAC failure and Service (see section 4.19). It may induce one of the following mobility cases:

• 3G to 2G handover for PS • 3G to 2G handover for CS • 3G to 2G handover for CS+PS • inter-frequency inter-RNC handover • inter-frequency intra-RNC • intra-frequency inter-RNC

“Alarm Measurements” refers to either “inter-frequency measurements” or “inter-system GSM measurements”. This section deals with Alarm radio condition. The Triggering of the Alarm measurement and the handover is based on the “Fast Alarm” algorithm. Fast Alarm algorithm description: As illustrated in the figure below, the Alarm measurements are activated once a criteria Cr is fulfilled, possibly following by Compressed Mode activation. As soon as the first valid measurement is received from the mobile, the Alarm handover is performed. This algorithm allows better reactivity from UTRAN, as only one radio criteria is used for both alarm measurement and handover triggering. It also has a positive impact on network capacity as it limits the time during which Compressed Mode is active.

Radio quality

Cr

time

Alarm Measurements trigger

1st valid measurement from UE Alarm Handover trigger

Alarm Measurements Reporting phase

Figure 74: the fast alarm algorithm

UMTS Radio Mobility



5.9.2 ALARM MEASUREMENT ACTIVATION WITH PERIODIC INTRA FREQUENCY MEASUREMENTS

Inter-system and inter-frequency measurements are requested under certain radio conditions. At each reception of RRC MEASUREMENT REPORT (which is periodic), and once the primary cell has been updated, the following criteria is evaluated:

AlarmMeas = (CPICH Ec/No < ThreshEcMeas) or (CPICH RSCP < ThreshRSCPMeas) for the Primary cell. Then, the following process is applied: If AlarmMeas is valid

Increment AlarmMeasCounter by UpStep Else Let AlarmMeasCounter = max (0, AlarmMeasCounter – DownStep) Endif If AlarmMeasCounter > AlarmMeasCounterThreshold then Alarm measurements are requested from the mobile The following figure illustrates this process:

Alarm Measurement criteria

time Measurement report occasions

AlarmMeasCounter

AlarmMeasCounterThreshold

Alarm Meas decision:

AlarmMeasCounter > AlarmMeasCounterThreshold

UpStep

DownStep

No

Yes

Figure 75: Alarm measurement decision process

In case the Alarm Measurement Criteria is valid, then the following is applied: 1. Inter-system or inter-frequency measurements are requested from the mobile using a Measurement Control

message (please refer to the section 6.2 for further details). 2. Compressed Mode is possibly activated using the Measurement Control message, based on mobile needs, as

indicated in the mobile "UE capabilities" Information Element". For further details on this procedure, please refer to the 6.4 chapter on Compressed Mode.

3. if compressed mode needs to be reactivated , a Compressed Mode Command message is sent to the UE

UMTS Radio Mobility



Full Periodic Mode

MR Counter meas hit

Wait for Inter Freq/Inter Rat meas

HHO processing

time

Target cell found

time

This is described in the following figure (the use case concerns Intra Frequency periodic measurements with Inter System additional measurements):

UE Serving RNC

RRC/ Measurement control (intrafrequency)

PS/CS call setup

Intrafrequency measurement configurationdone in the call setup phase

RRC/ Measurement report (intrafreq meas)

RRC/ Measurement control (intersystem,neigh GSM cells,

start CM)

...

Based on intrafrequency measuremenst anddepending on mobile capability, the SRNCdecides to request intersystem measurements.Compressed Mode is also possibly activated,depending on mobile needs

The UE is now able to report both intersystemand intrafrequency measurements. There is onesingle report for both reported quantities

RRC/ Measurement control (start CM)

RRC/ Measurement report (intrafreq meas,intersystem meas))

RRC/ Measurement report (intrafreq meas,intersystem meas))

...

Later on, the compressed mode activationcondition is still valid, and compressed mode isre-activated

Figure 76: measurement activation example (inter-system case)

As a MEASUREMENT REPORT is received with GSM (resp. inter-frequency) measurements, the Alarm Measurement criteria is checked again. If still valid, a hard handover is triggered towards the chosen target cell. If no neighbouring measurement may be requested to the UE but Inter Rat HHO is allowed (for example: CM not possible, neighbouring cells filtered after applying IMSI criteria…) or no suitable Alarm measurement is reported by the mobile within a guard timer period, a blind handover towards the blind GSM cell provisioned for the Primary cell may be performed by the RNC. Remark 1: The additional check on the Alarm Measurement criteria once a measurement is received is needed, as the radio conditions may change between the measurement activation and the reception of the first measurement report with GSM/inter-frequency measurements. As seen on live networks, the mean period of time between the sending of the MEASUREMENT CONTROL and the reception of the related MEASUREMENT REPORT is around 3s. This is explained by:

• The current value of Compressed Mode activation time (1,52 s), quite high but necessary to secure the correct reception of the MEASUREMENT REPORT message by the UE

• The fact that the mobiles need at least 1,5 s of Compressed Mode for measuring and decoding a first set of neighbouring GSM BSIC.

UMTS Radio Mobility



Remark 2: In case of handover failure, the HO decision counter (InterSystemDetectionCounter) need to be reset in order to avoid a second handover attempt to be made towards the same cell too shortly after the failure.

6. ALARM MEASUREMENT ACTIVATION WITH EVENT BASED INTRA FREQUENCY MEASUREMENTS

6.1.1.1 DESCRIPTION

A solution based on events 2D and 2F will be used. Although being related to intra-frequency measurements, 2D and 2F are categorized in the ‘inter-frequency” event group, which helps to decrease the number of simultaneous intra-frequency events required. Besides, the fact that 2D/2F are only triggered by the “Best” cell of the active set allows to save un-necessary measurement reports.

In [A4], events 2D and 2F are defined as follows:

2/22 ddUsedUsed HTQ −≤ And

2/22 ffUsedUsed HTQ +≥

• TUsed2d refers to an absolute threshold. For CPICH Ec/No based event this is set to the value of the parameter cpichEcNoThresholdUsedFreq2D. For CPICH RSCP based event this is set to the value of the parameter cpichRscpThresholdUsedFreq2D.

• TUsed2f refers to an absolute threshold. For CPICH Ec/No based event, the configuration of this parameter is set to the value of the parameter cpichEcNoThresholdUsedFreq2F which is a hysteresis to cpichEcNoThresholdUsedFreq2D. For CPICH RSCP based event, the configuration of this parameter is set to the value of the parameter cpichRscpThresholdUsedFreq2F which is a hysteresis to cpichRscpThresholdUsedFreq2D.

• H2d and H2f refer to as hysteresis parameters. They can be set to the value of hysteresis2D and

hysteresis2F.

• Qused refers to as the quality of the currently used frequency. This is defined by:

Best

N

iiUsed LogMWMLogWQ

A

⋅⋅−+

⋅⋅= ∑

=

10)1(101

• W is set to 0, so that QUsedn actually refers to as CPICH Ec/No or CPICH RSCP of the best cell in the active set, depending on 2D and 2F “measurement result” configuration.

In order to trigger a report, the triggering condition has to be valid for a period of time named “time to trigger”. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger2D, timeToTrigger2F). In UA07.1, a solution based on UeTxPower is also introduced. It is based on event 6A and 6B. In [A4], event 6A and 6B are defined as:

• For 6A: the UE Tx power is greater than the value in IE "UE Transmitted Power Tx power threshold" stored for this event (parameter UeTxPwrMaxThresholdOffset)

• For 6B: the UE Tx power is less than the value in IE "UE Transmitted Power Tx power threshold" stored for this event (parameter UeTxPwrMaxThresholdOffset)

UMTS Radio Mobility



In order to trigger a report, the triggering condition has to be valid for a period of time named “time to trigger”. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger6A, timeToTrigger6B).

NB: The measurements configuration (for 6A and 6B triggers) are defined per mobility service type. mobilityServiceType: this parameter defines the mobility service type that matches with each DlUserService. It is used as UsHoConf index id. (dlUserService ---> mobilityserviceType ---> usHoConf). => it’s the DL rab which is taken into account.

Figure 77: use of Event per Ul Service. Time To triggers values are not relevant in this figure

At the end, the list of configured events for alarm handover activation would be as follows (for 2D and 2F, there is no “triggering” condition. By default, any of the active set cells may trigger the event):

Reporting quantity Event id CPICH RSCP 2D CPICH RSCP 2F CPICH Ec/No 2D CPICH Ec/No 2F UeTxPwr 6A UeTxPwr 6B

6.1.1.2 ALGORITHM

The Alarm criteria may be set by: • Either event 6A and 6B; • Or Event 2D and 2F

Event 2D and 2F are managed the following way (events 6A and 6B are managed exactly the same way): The algorithm used to trigger alarm measurements will be based on the following principles:

UMTS Radio Mobility



• On reception of 2D event the RNC starts a timer. If the timer elapses until 2F is received, Alarm measurements are configured. If 2F is received while the timer is running, the timer is stopped.

• Use of event “time to trigger” parameter, so that the event is only reported once 2D or 2F is valid for a certain period of time.

CPICH Ec/No

2D

2D

Long « Time To Trigger »

Short « Time To Trigger »

2D sent

2F

2F

HO decision

Figure 78: influence of short & long time to trigger

The figure above illustrates a cell edge case where the measurement quantity fluctuates around 2D and 2F triggering thresholds, as observed from the field: In case of long “Time To Trigger”, event 2D may possibly not be reported, as the condition is evaluated over a long period of time Short “Time To trigger” (around 100 to 300ms) allows much faster detection. In order to avoid un-necessary activation, Alarm criteria is only considered valid once a certain period of time has elapsed without receiving 2F. Short “Time To Trigger” values are preferred to ensure better network reactivity under alarm conditions As a consequence, a time window solution needs to be implemented at the RNC side, for event confirmation.

The criteria conditions 2D/2F for both Ec/N0 and RSCP, and 6A/6B are managed simultaneously. The algorithm is the following:

• The timer timerAlarmHOEvent2D to confirm alarm handover criteria is started once a 2D event is received for any of the measurement quantity (RSCP or Ec/No).

• The timer timerAlarmHOEvent6A to confirm alarm handover criteria is started once a 6A event is received;

• If another subsequent 2D event with another measurement quantity is received, the timer timerAlarmHOEvent2D shall continue and the RNC stores that both quantities fulfils their triggering condition

• The timer timerAlarmHOEvent2D is stopped if a 2F event corresponding to the triggering 2D is received. In case both quantities (RSCP and Ec/N0) have fulfils their triggering condition, the timer is stopped if both 2F corresponding events are received (Ec/N0 and RSCP).

• The timer timerAlarmHOEvent6A is stopped if a 6B event corresponding to the triggering 6B is received;

• A change of primary (event 1D) or Service type received while the timers are running has no effect on the algorithm, except the case when the new primary has different thresholds than the previous primary cell in which case the 2C/2D/6A/6B events are modified with the new thresholds;

UMTS Radio Mobility



• Once the timer timerAlarmHOEvent2D or timerAlarmHOEvent6A elapses, the RNC activates inter Freq or Inter Rat periodical measurements depending on iMCTA provisioning;

• When inter Freq or Inter Rat periodical measurements are already activated for a given criteria or the other criteria is set, no new measurements are requested to the Ue;

• After inter Freq or Inter Rat measurements are setup due to one criteria (2D or 6A), if all alarm criteria previously set become invalid (i.e. reception of a 2F and/or 6B events) before the alarm measurement results are received, the alarm handover procedure is cancelled and the alarm measurement results will be ignored when received. If one alarm criteria (2D or 6A) are again met a new alarm measurement (inter Freq or Inter Rat based on periodical reporting) will be setup again.

As an example, the complete decision table for 2D CPICH Ec/No triggering event is described hereafter. “Alarm criteria” reflects the RNC decision once the timer has elapsed:

Triggering event Received while timer is running Timer stopped? 2D Ec/No - No 2D Ec/No 2F RSCP No 2D Ec/No 2F Ec/No Yes 2D Ec/No 2D RSCP No 2D Ec/No 2D RSCP ; 2F Ec/No No 2D Ec/No 2D RSCP ; 2F RSCP No 2D Ec/No 2D RSCP ; 2F Ec/No ; 2F RSCP Yes

Timer decision table

The alarm measurement activation is illustrated by the following picture:

Radio quality

Threshold.

time

Alarm criteria Confirmation timer

2D received

Inter-frequency or inter-RAT configured

Figure 79: Alarm Measurement activation overview

2D Timer elapses

2D

MR

Event Trigger Mode

2D Timer

time

HHO processing

Wait for Inter Freq/Inter Rat meas

UMTS Radio Mobility



Hard Handover Failure: If the mobile fails to synchronize to the target resource, a Hard Handover Failure message is sent to the SRNC, indicating the mobile has returned to the old channel. In such a case, in order to avoid too frequent handovers, the Alarm Criteria confirmation timer is started again.

Figure 80: Alarm Measurement 2D criteria hit then 6A

TT 6B

UE Pwr

time

6A Received 6A Alarm timer started

6B received 6A Alarm timer stopped

6A Thresh.

UE Tx Pwr

TT 6A

6B Thresh

Figure 81: Alarm Measurement 6A followed by 6B

UMTS Radio Mobility



If neighbouring measurement cannot be requested to the UE but Inter Rat HHO is allowed (for example: CM not possible with the current RAB, neighbouring cells filtered after applying IMSI criteria…) or no suitable Alarm measurement is reported by the mobile within a guard timer period, a blind handover towards the blind GSM cell provisioned for the Primary cell may be performed by the RNC.

When the Alarm HHO fails during preparation –( - for all possible targets – see section 4.10.4) or execution phase, the compressed mode pattern is deactivated and the Inter Rat or Inter freq measurements are removed and then:

• If the alarm criterion is still hit (no event 2F to cancel the event 2D during the HHO), in order to delay a new HHO attempt the Alarm confirmation timer is set with the value max (2D timer+TTT2D, 1800ms). At the timer expiration, measurements configuration and compressed mode activation are sent to the UE;

• If the alarm criterion is not hit anymore, the procedure ends. The behavior is the same for 6A/6B.


Regarding inter-frequency measurement, three different quantities are actually required: • CPICH Ec/No: reported in events 2D, 2F • CPICH RSCP: reported in events 2D, 2F • UeTxPower: for events 6A, 6B

So that three MEASUREMENT CONTROL messages are actually needed to configure inter-frequency events.

As in [A4] specification, inter-frequency events reporting are not repeated. In order to limit the risk of loosing an event on the radio interface because of bad transmission conditions, all intra-frequency event reports are configured in RLC Acknowledged Mode. The overall structure of the inter-frequency MEASUREMENT CONTROL message is as follows.



§10.3.7.16 Inter-freq measurements


Event 2D

Event 2F

…

§10.3.7.19 Inter-freq meas rep criteria

Figure 82: inter-frequency Measurement Control message structure

In the §10.2.17 common part: The IE Measurement reporting mode contains the specific information:

• Measurement Report Transfer Mode: Acknowledged mode RLC

UMTS Radio Mobility



• Reporting Mode: Event trigger In the §10.3.7.16 common part:

• Inter-frequency measurement quantity (§10.3.7.18) • Intra-frequency measurement quantity: “CPICH Ec/No” or “CPICH RSCP” • Measurement quantity for frequency quality estimate: “CPICH Ec/No” or “CPICH RSCP” • Inter-frequency reporting quantity (§10.3.7.21)

o For 2D/2F CPICH Ec/No (if measurement quantity is Ec/No) or CPICH RSCP (if the measurement quantity is RSCP)

6.1.1.3.1 2D EVENT CONFIGURATION

Information Element/Group name Need Parameter Value Parameters required for each event OP >Inter-frequency event identity MP “2d” >Threshold used frequency CV–clause 0 Use cpichEcNoThreshold2D or

cpichRscpThreshold2D parameter >W used frequency CV–clause 2 Use weight2D parameter >Hysteresis MP Use hysteresis2D parameter >Time to trigger MP Use timeToTrigger2D parameter >Reporting cell status OP Use maxNbReportedCells2D parameter >Parameters required for each non-used frequency

OP Not needed

>>Threshold non used frequency CV–clause 1 Not needed >>W non-used frequency CV–clause 1 Not needed

6.1.1.3.2 2F EVENT CONFIGURATION

Information Element/Group name Need Parameter Value Parameters required for each event OP >Inter-frequency event identity MP “2f” >Threshold used frequency CV–clause 0 Use cpichEcNoThreshold2F or

cpichRscpThreshold2F parameter >W used frequency CV–clause 2 Use weight2F parameter >Hysteresis MP Use hysteresis2F parameter >Time to trigger MP Use timeToTrigger2F parameter >Reporting cell status OP Use maxNbReportedCells2F parameter >Parameters required for each non-used frequency

OP Not needed

>>Threshold non used frequency CV–clause 1 Not needed >>W non-used frequency CV–clause 1 Not needed

Remark: In order to avoid event ping-pong effect, 2D and 2F need to be triggered by different conditions. This may be achieved through:

• Specific 2D and 2F thresholds (as in the tables above) • Same thresholds, using a hysteresis different than 0.

UE internal measurements event reports are configured in RLC Acknowledged Mode. The overall structure of the UE internal measurements MEASUREMENT CONTROL message is as follows.

UMTS Radio Mobility





§10.3.7.77 UE internal measurements


Event 6A

Event 6B

…

§10.3.7.80 UE internal meas rep criteria

Figure 83:UE internal Measurement Control message structure

6.1.1.3.3 6A EVENT CONFIGURATION

Information Element/Group name Need Parameter Value Measurement quantity

OP “UE Transmitted Power”

Filter coefficient OP 3(already defined for Ue Internal measurement in OAM)

UE Transmitted Power MP True UE Rx-Tx time difference MP False UE internal event identity MP “6A” Time to trigger MP Use new timeToTrigger6A parameter UE Transmitted Power Tx power threshold MP Use new UeTxPwrMaxThresholdOffset for

6A parameter

6.1.1.3.4 6B EVENT CONFIGURATION

Information Element/Group name Need Parameter Value Measurement quantity

OP “UE Transmitted Power”

Filter coefficient OP 3(already defined for Ue Internal measurement in OAM)

UE Transmitted Power MP True UE Rx-Tx time difference MP False UE internal event identity MP “6B” Time to trigger MP Use new timeToTrigger6B parameter UE Transmitted Power Tx power threshold MP Use new UeTxPwrMaxThresholdOffset for

6B parameter Remark: - In order to avoid event ping-pong effect, 6A and 6B need to be triggered by different conditions. This may be achieved through Specific 6A and 6B thresholds (as in the tables above) - For UE transmitted power reporting, the UE applies a L3 log filtering algorithm.

UMTS Radio Mobility



6.1.2 PARAMETERS

Name Object/Class Definition

IsAlarmHHOUeTxPwrAllowed RadioAccessService Class 3

This parameter controls the activation of the feature "Alarm HHO based on UE Tx Power". This feature doesn't apply to E-DCH calls.

timerAlarmHOEvent2D UsHoConf Class3

Used for Alarm handover criteria in event-reporting mode. This timer is started on reception of 2D event.

timerAlarmHOEvent6A UsHoConf Class3

Timer armed by the RNC Activation when it receives 6A Event. When the timer elapses before receiving an event 6B, the HHO criteria is hit.

hysteresis2D UsHoConf Class3

hysteresis for event 2D

Weight2D UsHoConf Class3

defines the weight to configure for the triggering of event 2D in Full Event mode

timeToTrigger2D UsHoConf Class3

Period of time during which the event condition has to be satisfied before sending event 2D

maxNbReportedCells2D MeasurementConfClass Class3

Maximum allowed number of cells to report with event 2D

cpichEcNoThresholdUsedFreq2D UsHoConf Class3

Specific CPICH Ec/No threshold specific to event

cpichRscpThresholdUsedFreq2D UsHoConf Class3

Specific CPICH RSCP threshold specific to event

hysteresis2F UsHoConf Class3

hysteresis for event 2F .

Weight2F UsHoConf Class3

defines the weight to configure for the triggering of event 2F in Full Event mode

timeToTrigger2F UsHoConf Class3

Period of time during which the event condition has to be satisfied before sending event 2F

maxNbReportedCells2F MeasurementConfClass Class3

Maximum allowed number of cells to report with event 2F

cpichEcNoThresholdUsedFreq2F UsHoConf Class3

Specific CPICH Ec/No threshold specific to event 2F (used as an hysteresis to the corresponding event 2D parameter)

cpichRscpThresholdUsedFreq2F UsHoConf Class3

Specific CPICH RSCP threshold specific to event 2F (used an hysteresis to the corresponding event 2D parameter)

UeTxPwrMaxThresholdOffset UsHoConf FullEventHOConfHhoMgtEvent6A Class3

Delta power to be minus to UlUsPowerConf MaxAllowedUlTxPower for event 6A

UeTxPwrMaxThresholdOffset UsHoConf FullEventHOConfHhoMgtEvent6B

Delta power to be minus to UlUsPowerConf MaxAllowedUlTxPower

UMTS Radio Mobility



Class3 for event 6B

timetoTrigger6A UsHoConf Class3

Time To trigger timer value attached to the event 6A

timetoTrigger6B UsHoConf Class3

Time To trigger timer value attached to the event 6B

6.2. MEASUREMENTS CONFIGURATION FOR INTER-FREQ/2G INTER-RAT

6.2.1 MEASUREMENT REPORTING

Periodic reporting is used in this version for Inter Frequency/GSM Inter-System measurements. The reporting period is 500 milliseconds. All the measured quantities will be reported by the mobile in the same measurement report message (Inter frequency/GSM Inter-System are additional measurements) when Intra Frequency measurements configuration is periodic. When Intra Frequency measurements configuration is event type and only one of both, Inter Frequency or GSM Inter-System measurements are used, then the measurement is configured as main measurement configuration in periodic mode. When Intra Frequency measurements configuration is event type and both, Inter Frequency and GSM Inter-System measurements are used, then the Inter Frequency measurement is configured as main measurement in periodic mode and the GSM measurement is configured as additional measurement of the Inter Frequency measurement. The list of neighbour cells to be monitored is given by the iMCTA function. The neighbor cells are selected among the neighboring cells of the primary cell and/or other active set cells (refer to § 5.5). When an update of the neighbour list has to be sent to the UE, it only includes the cells to be removed and to be added (delta between the previous neighbouring and the new neighbouring).

6.2.2 REPORTED CELLS

In this release, the UE is requested to report up to 6 neighbouring cells amongst the monitored set. The 6 cells may be either inter-frequency or GSM inter-system neighbouring cells. The monitored set is defined as the set of inter-frequency or GSM neighbours of the primary cell and is provided to the UE through a MEASUREMENT CONTROL message first time the measurement condition is fulfilled and on modification of monitored set. For more details on the primary cell determination, please refer to the section 5.4.

6.2.3 CONFIGURATION FOR INTER-SYSTEM MEASUREMENTS

The SRNC requests the following quantities to be reported by the mobiles: • GSM Carrier RSSI: Received Signal Strength Indicator on a GSM BCCH carrier • Observed time difference to GSM cell (for observation only) • Verified BSIC (this option is required to avoid the mobile reporting GSM measurement for which the BSIC

is not identified. Otherwise, depending on the GSM reuse pattern and the radio condition, this might increase the risk of handover failure)

L3 filtering is applied in the UE for each measurement, as specified in [A4], and as described in the section 6.3. For that purpose, a specific value of “filter coefficient” is provided for RSSI quantity, as a configuration parameter. No additional filtering is applied by the SRNC.

UMTS Radio Mobility



The inter-RAT cell info indication IE supported by R5 UE is managed by the S-RNC. When the inter-RAT cells list changes (e.g. due to a primary cell change or OAM modification), the SRNC increments the value of this IE present in the RRC Measurement Control message. When receiving inter rat measurements from the UE, the RNC uses the inter-RAT cell info indication IE present in the RRC Measurement Report by associating it with the correct configuration.

6.2.4 CONFIGURATION FOR INTER-FREQUENCY MEASUREMENTS

The SRNC requests the following quantities to be reported by the mobiles: • CPICH Ec/No • CPICH RSCP

L3 filtering is applied in the UE for each measurement, as specified in 25.331, and as described in section 6.3. For that purpose, a specific value of “filter coefficient” is provided for RSSI quantity, as a configuration parameter. No additional filtering is applied by the SRNC.

6.2.5 CHANGE OF MEASUREMENT TYPE

Following a change of primary link, it may happen that the measurement type changes, i.e. if 3G, 2G or simultaneous 3G and 2G measurements are requested. In this case the ongoing measurement is continued and if the UE reports a valid target cell, then the handover is executed. The new measurement type is taken into account for next iMCTA trigger evaluation.

UMTS Radio Mobility



6.2.6 PARAMETERS FOR MEASUREMENT

6.2.6.1 MEASUREMENT ACTIVATION PARAMETERS

The following parameters are used when the HHO reason is an alarm reason.

Name Object/Class Definition cpichEcNoThreshold FastAlarmHardHoConf

per UsHoConf Class 3

Threshold on CPICH Ec/N0 used in the decision process of inter system or inter-frequency measurement and hard handover

cpichRscpThreshold FastAlarmHardHoConf per UsHoConf Class 3

Threshold on CPICH RSCP used in the decision process of inter system or inter-frequency measurement and hard handover

counter FastAlarmHardHoConf per UsHoConf Class 3

The measurement and hard handover decision is taken when decision counter, based on CPICH RSCP or CPICH Ec/N0 criterion, is above this quantity.

StepDown fastAlarmHHOTimeFilter per UsHoConf Class 3

decision counter is decremented by stepdown when the downlink quality HHO criterion based on CpichRSCP or CpichEc/N0 is not hit

StepUp fastAlarmHHOTimeFilter per UsHoConf Class 3

decision counter is incremented by stepup when the downlink quality HHO criterion based on CpichRSCP or CpichEc/N0 is hit

UMTS Radio Mobility



6.2.6.2 OTHER PARAMETERS

The following parameters are used whatever the HHO reason.

Name Object/Class Definition interFreqFilterCoeff InterFreqMeasConf

Class3 Filter coefficient for inter-frequency Layer 3 filtering in the UE

rrcGsmMeasurementFilterCoefficient RRCMeasurement Class3

Filter coefficient for GSM RSSI Layer 3 filtering in the UE

rrcIntraFreqMeasurementFilterCoeff RRCMeasurement Class3

Filter coefficient for intra-frequency Layer 3 filtering in the UE

isBlindHoRescueAllowed RadioAccessService Class3

This parameter indicates whether the RNC is allowed to trigger a blind rescue handover towards a GSM cell.

measurementGuardTimer2g


When the RNC waits for UE measurements this timer is used as a guard timer (compressed mode may activated or not depending on UE capabilities). At the timer expiration a blind HHO towards a 2G cell may be processed. Its value is set to encompass the compressed mode duration: >=TCmodeStart + TCmodeDuration + 1000 ms.

measurementGuardTimerFdd


When the RNC waits for UE measurements this timer is used as a guard timer (compressed mode may activated or not depending on UE capabilities). At the timer expiration a blind HHO towards a 2G cell may be processed. Its value is set to encompass the compressed mode duration: >=TCmodeStart + TCmodeDuration + 1000 ms.

6.3. INTRA-FREQUENCY MEASUREMENTS

6.3.1 CONFIGURATION

6.3.1.1 ACTIVATION/DEACTIVATION

Intra-frequency measurements are activated for all mobiles at the transition to CELL_DCH RRC state (e.g. call establishment or CELL_FACH to CELL_DCH transition after always on upsize…), through the MEASUREMENT CONTROL message, or via SIB11/SIB12 configuration. Intra-frequency measurements are never deactivated, unless the mobile-network RRC connection is released (e.g. at the end of the call) The events (6A, 6B) are configured if the following conditions are fulfilled:

- the feature “HHO based on UE Tx power” is activate at OAM level (parameter isAlarmHhoUeTxPwrAllowed);

- the feature is allowed at OAM level for the Service in progress; - if the call only uses DCH transports for uplink.

The feature applies for Multi Rab call using DCH transport.

UMTS Radio Mobility



When the call leaves this transport type towards E-DCH transport, a SRLR is processed with an update of the measurements: the event 6A and 6B are de-configured. If the RNC receives during the transition an event 6A or 6B, they are discarded except if the HHO criterion was hit before the SRLR. When the call moves again towards DCH Ul transports, a SRLR is processed with an update of the measurements: 6A and 6B are configured if the condition given above allows it.

6.3.1.2 MEASUREMENT REPORTING

Periodic or Full Event reporting may be used in this version for the intra-frequency measurements. For periodic measurement the reporting period is 500milliseconds or more. As specified in [A4], different measurements quantities must use separate "measurement identities". Nevertheless, as the [A4] allows, they will be reported in the same Measurement Report message in order to keep the uplink signalling at the lowest level.

6.3.1.3 REPORTING QUANTITIES

The SRNC requests the following quantities to be reported by the mobiles: • “Cell Synchronization information” which provides the difference between SFN of the reported cell and

CFN as observed by the UE. This quantity is used by the SRNC in order to calculate “Frame Offset” and “Chip offset” Iub/Iur parameters which position transmission/reception time of the new cell to be added.

• CPICH Ec/No: the received energy per chip divided by the power density in the band. • CPICH RSCP: is the received power on one code measured on the Primary CPICH. • UE Transmitted Power: is the output measured power, averaged by the UE over one timeslot at level 1 Other reporting quantities are also supported by UTRAN and are also requested to the UE for tracing purposes: • SFN – SFN observed time difference "type 2": the relative timing difference between cell j and cell i

measured on the primary CPICH; • Quality measurements.

6.3.1.4 REPORTED CELLS

The 3GPP TS25.331 allows the UTRAN to configure the cells to be reported in the following way: • reporting of x best cells from the active set or all the active set • reporting of y best cells of the monitored set • reporting of z detected cells i.e. cells measured by the UE but neither in the active set, nor in the

monitored set. In this release, the UE is requested to report measurements on: • the whole active set cells • the 6 best monitored set cells • the 3 detected cells are reported (in Full Event mode only) The active set is known by the UE through the ACTIVE SET UPDATE message which requests the UE to update its active set. The monitored set is defined in section 6.7 and is provided to the UE through a MEASUREMENT CONTROL message when it changes. For more details on the primary cell determination, please refer to the active set determination algorithm (Section 5.3).

UMTS Radio Mobility



Note: If Detected Set cells are reported the RNC will trace this as specified in [R5]. When possible and activated, detected cells can be added to the active set (refer to § 5.3.4.3).Based on traces the neighbouring provisioning may be modified.

6.3.1.5 FILTERING

As specified in 25.331, L3 filtering is applied in the UE for the following measurements: • CPICH Ec/No • CPICH RSCP • UE transmitted power

The filtering algorithm is as follow:

nnn MaFaF ⋅+⋅−= −1)1(

with: • Fn is the updated filtered measurement result • Fn-1 is the old filtered measurement result. In order to initialise the averaging filter, F0 is set to M1 when the

first measurement result from the physical layer measurement is received • Mn is the latest received measurement result from physical layer measurements. • a = 1/2(k/2), where k is the parameter received in the IE "Filter coefficient" in the Measurement Control

message and in SIB11/SIB12 (if used). If k is set to 0 that will mean no layer 3 filtering. A specific value of k is provided for each of the measurement quantities, as an operator parameter. No additional filtering is applied by the SRNC.

6.3.2 MISSING MEASUREMENTS

When periodic measurements are reported, the RNC implement a specific process in order to cope with missing measurements for a given cell. The reason for this may be e.g. mobile limitation, or radio interface variation which may cause a cell not be reported for some period of time. This process only applies to intra-frequency measurements, for cells being part of the active set. The algorithm is as follows: Let’s call (cell,N) the missing measurement:

• the counter of consecutive missing measurements for this cell is incremented • if the counter value is above maxAllowedNumber, the measurement for this cell is replaced by a

minimal default value, used with a minimal coefficient in computations. This until the measurement is received again.

• else, the measurement is substituted by quantity (cell, N-1) – missedPenalty (there exists one penalty value for each CPICH RSCP and Ec/No reporting quantity)

Note: A similar algorithm is applied to inter-frequency and 2G inter-RAT measurements, too. The corresponding parameters are:

Name Object/Class Definition maxAllowedNumber MissingMeasurement

Class3 Maximum number of allowed missing measurements in the message RRC Measurement Report for a cell of the monitored set.

missedEcNoMeasurementPenalty MissingMeasurement Class3

Penalty coefficient which is subtracted to the last received CPICH Ec/N0

UMTS Radio Mobility



measurement to replace a missing one. missedRscpMeasurementPenalty MissingMeasurement

Class3 Penalty coefficient which is subtracted to the last received CPICH RSCP measurement to replace a missing one.

6.4. COMPRESSED MODE

6.4.1 INTRODUCTION

The compressed mode is used to allow a UE in FDD in dedicated mode to make measurements on a UTRA cell (either FDD or TDD) or on another Radio Access Technology (RAT), such as GSM, as part of the handover preparation. Measurement on a UTRA FDD cell is referred to as inter-frequency measurement and measurement on a UTRA TDD cell or a GSM cells is referred to as intersystem measurement. The compressed mode involves interrupting the transmission in the uplink or downlink, or possibly both at the same time, for short amounts of time (less than one 10 ms radio frame) in a regular manner to allow the mobile to perform the requested measurements. Any transmission interruption time, called a transmission gap, may be contained within one radio frame or span the boundary between two radio frames such that the transmission gap does not exceed half of the period of any one radio frame (10 ms). In this version of the document • compressed mode is either used when needed for GSM and/or FDD inter-frequency measurements • compressed mode is used for all kind of CS or PS services, without discrimination.

6.4.2 UE CAPABILITY

The real need for compressed mode is indicated by the mobile in the UE Radio Access Capability information element, provided in the RRC CONNECTION SETUP COMPLETE message. This information element is sent on network request ("GSM capability required" indication in the RRC Connection Setup message sent from the network).

Node B RNCUE

RRC/ RACH (RRC connection Request)


NBAP/ Radio Link Setup response

RRC/ FACH (RRC Connection Setup (GSM capability required))

RRC/ RRC Connection Setup Complete (UE Radio Access Capability)

...

The UE radio access capability is not reported bythe UE unless it is requested by the RNC.

Figure 84: Retrieving UE capability

In the UE Radio Access capability, the mobile indicates if compressed mode is needed in either UL or DL for the following modes: • FDD • GSM450 • GSM480 • GSM850 • GSM900P • GSM900E • GSM900R • GSM1800 • GSM1900

UMTS Radio Mobility



All FDD R7 frequency bands capabilities are used by the RNC. The UTRAN supports: • all FDD R7 frequency bands except the band IV; • the mobility between these bands except between band I and band II; • Inter Rat handover from/towards theses bands.

The UE Radio Access capability information is used by the network to configure and activate compressed mode in 3 possible ways: • for the uplink only • for the downlink only • for both In the paragraph on "procedures & messages", and as specified in 3GPP documents, it is explained that compressed mode configuration is done very early in the call process, and that compressed mode is only activated when needed. Regarding compressed mode for GSM, in order not to configure compressed mode in every case, a set of flags indicating the frequency band of the GSM neighbouring cells will be defined and used in the RNC to determine whether or not compressed mode is needed, and for which direction. The list of flags is the following: • GSM450present • GSM480present • GSM850present • GSM900Ppresent • GSM900Epresent • GSM900Rpresent • GSM1800present • GSM1900present Each flag indicates that there exists at least a GSM cell of the corresponding frequency band in the access network (i.e. not only being part of the GSM neighbouring lists seen by the RNC) to which handover from a 3G cell is supported by the network. Therefore, if compressed mode is needed by the mobile for that frequency band it will be configured accordingly and possibly activated by the network if the measurement request concerns at least a neighbour cell of that band.

6.4.3 METHOD

There exist 3 methods for compressed mode: • Puncturing: transmission gaps are created by performing additional puncturing or fewer repetitions in rate

matching compared to normal mode so that the bit rate resulting from the rate matching can be accommodated within the transmitted slots. This is a DL only method.

• Higher Layer Scheduling: transmission gaps are created by restricting the TFC in the TFCS. This implies that the transport channel can cope with some transmission delay. Therefore this method is not applicable to conversational services. This method is applicable to both UL and DL.

• SF reduction: the spreading factor of the compressed radio frames is divided by two, allowing the same number of bits to be sent in a smaller amount of time. This method is applicable to both UL and DL.

NOTE: puncturing method removed from 3GPP since R5, Compressed mode will be using the following method:

1) SF/2 reduction method 2) Higher Layer Scheduling (HLS) method

SF reduction and HLS methods can be configured in the UL or DL, or possibly both, for GSM or FDD inter-frequency measurements. The use of the SF/2 reduction method has an impact on the Scrambling and OVSF code used. This is further detailed in the chapter about "impacts on RRM" (see 6.4.8).

UMTS Radio Mobility



6.4.4 MEASUREMENT PURPOSE

Compressed mode makes use of pattern sequences, each of them being associated to a measurement purpose. The defined measurement purposes are applicable whatever the compressed mode method is (SF/2, HLS). The same CM pattern definition is used whatever the method is. In case of HSDPA or HSUPA calls, the compressed mode method only applies to the DCH part of the call. The pattern information are used to generate gaps in the HSDPA and HSUPA part of the call. A pattern sequence is composed of 2 pre-defined patterns (pattern 1 and pattern 2) being used alternatively, as in the figure below. A sequence may have a finite or infinite value depending on the TGPRC parameter. In principle, each pattern sequence is dedicated to a certain measurement quantity, so that, the network shall configure as many pattern sequences as measurement quantities to be reported by the mobile.

Transmission

Transmission gap 2

gap 2

TGSN TGSN

TGL2 TGL2

TG pattern 2

#TGPRC

gap 1

Transmission Transmission

gap 1

TGD TGD

TGPL1 TGPL2

TG pattern 1 TG pattern 2

TGL1 TGL1

#1 #2 #3 #4 #5

TG pattern 1TG pattern 1 TG pattern 2 TG pattern 1 TG pattern 2

Figure 85: Compressed Mode pattern sequence overview

6.4.4.1 GSM MEASUREMENTS

Regarding GSM measurements, there may be up to 3 pattern sequences needed, depending on the "measurement purpose": • RSSI measurements • Initial BSIC identification • BSIC re-confirmation In order to illustrate how the 3 measurements types are performed in the mobile, the following figure presents an overall view of compressed mode processes for GSM in the mobile, as specified in 25.133. • The mobile is provided with GSM neighbouring cell list, contained in the Measurement Control RRC

message. • The "RSSI measurement process" can be seen as a sort of endless loop, intending to identify the 8 strongest

cells. • The "Initial BSIC identification process" intends to identify the BSIC in the list. Once being successfully

identified, the BSIC is given to the re-confirmation process. • The "BSIC re-confirmation process" can be seen as a sort of endless loop, intending to re-confirm identified

BSIC, and maintain timing information with the identified cells.

UMTS Radio Mobility



RSSI measurementprocess

Initial BSIC IDprocess

BSIC re-confirmationprocess

8 strongest cells

up to 8 identified cells

identification failed

re-confirmation failed

Measurement Report

Measurement Control

(BSIC, BCCH ARFCN) GSM neigh.cells

Figure 86: UE process overview for GSM measurements

6.4.4.2 FDD INTER-FREQUENCY MEASUREMENTS

Regarding FDD inter-frequency measurements, only one pattern sequence is needed as there is only one "measurement purpose": • FDD measurement

6.4.5 PATTERN SHAPE

6.4.5.1 GSM MEASUREMENTS

In this version, for GSM measurements, Alcatel-Lucent UTRAN implements 2 finite length patterns: • one for GSM RSSI measurements • one for BSIC identification No pattern sequence for "BSIC reconfirmation" will be activated. The 2 patterns have finite duration (i.e.: TGPRC=1 to 511), and are not running in parallel (i.e. the pattern for BSIC identification is only started once the pattern for RSSI is over). An example for such a configuration is presented in the figure below:

CFN

CFN +x

RSSI

BSICIdentification

...

...

x frames y frames

UMTS Radio Mobility



Figure 87: Pattern sequences for GSM measurements Once RSSI measurements are performed, the mobile should normally attempt to identify the 8 strongest RSSI, using the relevant pattern sequence. Once BSIC have been identified and reported to the network, the network may possibly make a handover decision toward a GSM target. Please refer to the chapter on [parameters] for the pattern parameters supported in this version.

6.4.5.2 FDD INTER-FREQUENCY MEASUREMENTS

In this version, for FDD inter-frequency measurements, Alcatel-Lucent UTRAN implements a finite length pattern, as in the figure below.

CFN FDD measurement

...

x frames

Figure 88: Pattern sequence for FDD measurements

Please refer to the chapter on [parameters] for the pattern parameters supported in this version.

6.4.6 SLOT FORMATS/ FRAME STRUCTURE

According to 25.211 section 5.3.2 “Dedicated downlink physical channels”, in compressed frames, a different DPCH slot format is used compared to normal mode.

� There are two possible compressed slot formats (labeled A & B).

� The selection between them is dependent on the used method:

� DL Slot format B shall be used in frames compressed by SF reduction,

� DL Slot format A shall be used in frames compressed by HLS,

� Same Transmission gap position calculation used for SF/2 and for HLS compressed mode method.

� Frame structure type A and Type B shall be supported by the UTRAN.

6.4.7 PROCEDURES & MESSAGES

6.4.7.1 DATA FLOW

The principle is that compressed mode configuration and activation/de-activation are done in different phases: • configuration is performed at initial DTCH Radio Link setup/addition/reconfiguration (i.e. when the RAB

ASSIGNMENT REQUEST message is received from the Core Network). A reconfiguration of the compressed mode may occur when a CM method change is needed, e.g. due to additional RAB setup or RAB deletion.

• activation/deactivation is based on a separate criteria, i.e. when the iMCTA function needs measurement for HHO processing for Alarm, CAC or Service reason.

UMTS Radio Mobility



MSC-CS Node B RNC UE



RRC/ RB Setup (DTCH config, CM config for GSM, CM config for FDD)

RRC/ RB Setup Complete

NBAP/ Radio Link Reconfiguration Prepare (DTCH config, CM config for GSM, CM config for FDD)

NBAP/ Radio Link Reconfiguration Response

NBAP/ Radio Link Reconfiguration Commit (no pattern active)

Initial RRC connection DCCH establishment Initial UE DTAP message

Criteria is reached => CM activation

NBAP/ Compressed Mode Command (active pattern, starting CFN)

RRC/ Measurement Control (active pattern, starting CFN)

Criteria is reached => CM re-activation

NBAP/ Compressed Mode Command (active pattern, starting CFN)

RRC/ Measurement Control (active pattern, starting CFN)

Figure 89: Compressed Mode activation Note: "The 3GPP indicates the UE behaviour is unknown when the RNC asks to stop a compressed mode pattern when it is not yet started (CFN not passed). The RNC follows this rule."

6.4.7.2 RRC/RB SETUP MESSAGE

This message contains the CM configuration, which will be possibly be activated by the RNC when the criteria is reached. It contains the following information: • 10.2.33 RB Setup

• 10.3.6.24 Downlink information common for all radio links • 10.3.6.33 DPCH compressed mode info

TGPSI TGPS Status Flag TGCFN TGMP TGPRC TGSN

UMTS Radio Mobility



TGL1 TGL2 TGD TGPL1 TGPL2 RPP ITP UL/DL mode Downlink compressed mode method Uplink compressed mode method Downlink frame type DeltaSIR1 DeltaSIRafter1 DeltaSIR2 DeltaSIRafter2 N Identify abort T Reconfirm abort

• 10.3.6.27 Downlink information for each radio link

• 10.3.6.21 Downlink DPCH info for each RL Scrambling code change

6.4.7.3 RRC/RB RECONFIGURATION MESSAGE

This message is used to reconfigure the compressed mode (used to change the method). The same IEs are used as for initial CM configuration in RB Setup message – see above.

6.4.7.4 RRC/MEASUREMENT CONTROL MESSAGE

This message is used to trigger/stop compressed mode pattern sequences. • 10.2.17 Measurement Control

• 10.3.6.34 DPCH compressed mode status info TGPSI TGPS Status Flag TGCFN

6.4.7.5 NBAP/RADIO LINK RECONFIGURATION PREPARE MES SAGE

This message is used by the RNC to configure the compressed mode sequences to be used at the BTS. • 9.2.1.42 Radio Link Reconfiguration Prepare

• 9.2.2.14A DL code information • 9.2.2.53B Transmission Gap Pattern Sequence Code Information

Scrambling code change

• 9.2.2.57 UL DPCCH Slot Format • 9.2.2.10 DL DPCH Slot Format

• 9.2.2.53A Transmission Gap Pattern Sequence Information

TGPSI TGSN

UMTS Radio Mobility



TGL1 TGL2 TGD TGPL1 TGPL2 UL/DL mode Downlink compressed mode method Uplink compressed mode method Downlink frame type DeltaSIR1 DeltaSIRafter1 DeltaSIR2 DeltaSIRafter2

6.4.7.6 NBAP/COMPRESSED MODE COMMAND MESSAGE

This message is used to trigger/stop compressed mode pattern sequences. • 9.1.60 Compressed Mode Command

• 9.2.2.A Active Pattern Sequence Information

• CM activation

IE/Group Name Presence Range Type and reference CM Configuration Change CFN M CFN Transmission Gap Pattern Sequence Status

0.. <maxTGPS> group present (range > 0)

>TGPSI Identifier M >TGPRC M >TGCFN M CFN

• CM deactivation

IE/Group Name Presence Range Type and reference

CM Configuration Change CFN M CFN

6.4.7.7 NBAP/RADIO LINK RECONFIGURATION COMMIT MESS AGE

This message is used to trigger/stop compressed mode pattern sequences. • 9.1.60 Compressed Mode Command

• 9.2.2.A Active Pattern Sequence Information Same structure as § above.

6.4.7.8 RNSAP/RADIO LINK SETUP/ADDITION REQUEST MES SAGE

This message is used in case of inter-RNC soft handover. The main difference with equivalent message used on the Iub interface (NBAP Radio Link Reconfiguration Prepare message) is that the "code information" (i.e. whether or not the alternate scrambling is used) is not indicated in the RNSAP, so that the choice is left to the DRNC. Aside from this very specific point, the DRNC applies the same configuration as the SRNC in terms of pattern definition and Power control. • 9.1.3.1 Radio Link Setup Request or 9.1.6 Radio Link Addition Request

• 9.2.2.A Active Pattern Sequence Information

UMTS Radio Mobility



TGPSI TGCFN TGPRC

• 9.2.2.47A Transmission Gap Pattern Sequence Information

TGPSI TGSN TGL1 TGL2 TGD TGPL1 TGPL2 UL/DL mode Downlink compressed mode method Uplink compressed mode method Downlink frame type DeltaSIR1 DeltaSIRafter1 DeltaSIR2 DeltaSIRafter2

6.4.7.9 RNSAP/COMPRESSED MODE COMMAND MESSAGE

This message is used to trigger/stop compressed mode pattern sequences. Its format is equivalent to the message used on the Iub.

6.4.7.10 RNSAP/RADIO LINK RECONFIGURATION COMMIT ME SSAGE

This message is used to trigger/stop compressed mode pattern sequences. Its format is equivalent to the message used on the Iub.

6.4.8 IMPACTS ON RRM SPECIFIC FOR SF/2 METHOD

6.4.8.1 CODE TREE MANAGEMENT

The use of the SF reduction method has some impacts on the Scrambling and OVSF code used for the transmission. These impacts are described in what follows. For DL transmission in uncompressed frames, the network is using • scrambling code SC • OVSF code Cch,SF,n For DL transmission in compressed frames, Alcatel-Lucent UTRAN is using the alternate scrambling method, which makes use of 2 additional scrambling codes, as specified in 25.213, § 5.1.2 and 5.2.2: • SC+8192 • SC+16384 Depending on the position of the OVSF code Cch,SF,n in the code tree, either the 1st or the 2nd alternate is used: • if (n<SF/2), SC+8192 is used • if (n>=SF/2), SC+16384 is used In both cases, the OVSF code which is used for compressed frames is Cch,SF/2,n mod SF/2

UMTS Radio Mobility



0SF-1 SF/2 0SF-1 SF/2

RIGHT case

0SF-1 SF/2 0SF-1 SF/2

Scrambling code = SC +8192

Scrambling code = SC +16384

Scrambling code = SC

Scrambling code = SC

LEFT case

Figure 90: Alternate scrambling code usage

Due to the fact that alternate scrambling are used: • the code tree allocation algorithm which was defined in earlier product versions is kept unchanged • there is no OVSF code blocking issue due to the use of compressed mode in UTRAN

6.4.9 HLS

[USA Market: HLS method is supported in uplink, only. I.e. dependent on the uplink bearer combination SF/2 or HLS can be used. In downlink SF/2 method is available, only.]

This chapter describes the Compressed Mode by HLS over dedicated physical channel. The gain of the HLS CM method is � Does not require additional resources:

o No additional power is requested for transmission at same level of protection of the user bit o No additional OVSF resources

� allows removal of the interference impact created by the SF/2 and thus allows increase of the overall cell capacity

� allows the support of DCH RB with uplink SF=4 � obviously, avoids SF change and any new requirements for channelisation code usage � DL HLS is less stringent in CEM processing capacity requirement than SF/2

Such method can be configured as the following ones: � compressed mode is used when needed for GSM or FDD inter-frequency measurements � compressed mode by SF/2 reduction may be used for all kind of CS or PS services, � compressed mode by SF/2 reduction method is possible for both UL and DL whenever GSM or FDD inter-

frequency measurements is used, � compressed mode by HLS is used for UL/DL PS I/B mono/multi services over DCH, � compressed mode by HLS is used for UL/DL multiplexed PS I/B services over DCH, � compressed mode by HLS is also used for certain multiplexed PS I/B + CS services – see below. � compressed mode method by HLS or SF/2 can be used in mixed CM method UL/DL (ex. UL HLS and DL

SF/2) whatever the measurement purpose is.

UMTS Radio Mobility



6.4.9.1 HLS ASSUMPTIONS

� In most of the cases, only one method (either HLS or SF reduction) may be active at a time � For some specific configurations SF reduction may apply in DL whereas HLS applies in UL � Compressed mode (SF/2 or HLS) is active in Cell-DCH mode only, � Compressed mode (SF/2) is active with HSDPA, CMode method only applies to the DCH part of a call and

not to HS-DSCH, as a consequence the associated DCH (ie SRB only) uses SF/2 for any such configuration,

� Compressed mode (SF/2) is active with HSUPA CMode method only applies to the DCH part of a call and not to the E-DCH part,

� Standalone SRB configuration: o Design choice: HLS is not applied to “Standalone SRB” configurations in order to keep the SRB

capacity � Mono-service handling:

o HLS is not supported for any CS only call o HLS is not supported for PS Streaming only call o HLS is not supported for CSD64 only call o HLS is supported in both UL & DL for PS I/B x/y only call over DCH, with x/y > 8 kbps o If PS I/B only traffic is carried by DCH/HS-DSCH channel then only the SF/2 method is supported in

DL whereas the HLS method is supported in UL � Multi-service handling:

o HLS is supported in UL/DL for multi-service calls involving a CS call: SRB + CS Speech + PS I/B x/y over DCH with x/y > 8 Kbps, Only the PS I/B TF(s)/TFC(s) are restricted during transmission with gap,

o HLS is not supported for multi-service calls involving a PS Streaming session excepted if that RB combination gets a SF equal to 4 and the GBR is guaranteed,

o HLS is not supported in UL for multi-service calls involving a CSD call excepted if that RB combination gets a SF equal to 4,

o HLS is supported for multiplexed PS I/B x/y calls with x/y > 8 Kbps, o HLS can be applied to SRB + PS Streaming + PS I/B provided the streaming GBR while compressed

frames is guaranteed, � 3GPP baseline is R6 � UE capability

o Any UE is supposed to support HLS (3GPP mandatory feature for UE) o Some UEs do not require compressed mode to perform their inter-frequency or inter-RAT

measurements, while other require the compressed mode to be activated either in UL or DL only or in both UL and DL.

o UE capability analysis performed by the RNC is not impacted by the introduction of the HLS compressed mode, same UE capabilities filtering algorithm is applied,

6.4.9.2 HLS GAP PATTERN CONFIGURATION

� Compressed Mode configuration management: o The same CM patterns will be used for both HLS & SF/2 methods, refer to §6.4.5. o When compressed mode is activated, as per [25.211], slot format A applies to compressed mode by

HLS whereas slot format B applies to compressed mode by SF reduction

� Transmission over DL DCH shall be optimized while CM by HLS is active: o As per 3GPP spec, the max ratio of compressed frames is 2/3. With the current CM pattern, the ratio

is 1/3 in case of single 2G or 3G measurement and 2/3 in case of simultaneous 2G and 3G measurement.

o Some TF/s on PS RAB only are forbidden for TTIs where transmission with gap is performed o E.g. for a DL transmission with TTI = 10ms, assuming that the CM pattern configuration is as

described in section, 6.4.5. TFS reduction will only apply during 2 or 4 TTIs every 6 TTIs.

UMTS Radio Mobility



6.4.9.3 SWITCHING BETWEEN COMPRESSED MODE METHODS

The system shall be able to switch to the most appropriate method after a RAB combination modification, i.e. � Whenever a CM method change occurs in UL or DL or both the following applies:

o While SRLR the previous CM method is deactivated at CFN#1, o When SRLR ends the new CM method is configured and activated at the CFN#2 time,

=> For the specific case where the PS I/B would be supported by UL DCH / HS-DSCH transport channels, HLS would apply in the UL direction, while the SF/2 method would apply in the DL direction.

Hereafter the impacted RRC/NBAP/RNSAP messages used on the different transition use cases below: o NBAP/RNSAP RL SETUP Request (RBs + CM parameters) // CM configuration provisioning

// + start CM at TGCFN time

o NBAP/RNSAP RL RECONFIGURATION PREPARE (RBs + CM parameters) // CM configuration provisioning

o NBAP/RNSAP RL RECONFIGURATION COMMIT () // CM configuration provisioning // + start CM at TGCFN or CFN time

o NBAP/RNSAP COMPRESSED MODE COMMAND () // start CM at TGCFN or CFN time // stop CM configuration change // CFN time

o RRC RADIO BEARER SETUP (RBs + CM parameters) // configuration + Start/Stop CM // at TGCFN time for each // TGPSI

o RRC RADIO BEARER RECONFIGURATION (RBs + CM parameters) // configuration + Start/Stop CM // at TGCFN time for each TGPSI

o RRC MEASUREMENT CONTROL () // Start/Stop CM at TGCFN time // for each TGPSI

UMTS Radio Mobility



Switching between Compressed Mode methods use cases

� Compressed method switching while CM active: See call flow diagram below: MSC-CS Node B RNC UE

RRC/ RB Setup/Reconfiguration/Release (DTCH config, CM config for GSM, CM config for FDD)

RRC/ RB Setup/reconf/Release Complete



NBAP/ Radio Link Reconfiguration Prepare ((DTCH config, CM config for GSM, CM config for FDD)




NBAP/ Compressed Mode Command (active pattern, starting CFN: TGCFN time)

RRC/ Measurement Control (active pattern, starting CFN: TGCFN time) NodeB compares the CFN of DL FP DCH frames to TGCFN to trigger CM activation

RB configuration change => CM method switching: � RNC detects the CM method change

NBAP/ Radio Link Reconfiguration Prepare (DTCH config, New CM configuration/method)


NBAP/ Radio Link Reconfiguration commit (CM activation at new CFN: TGCFN time)

RRC/ RB Reconfiguration (DTCH config, for FDD, New CM configuration/method, CM activation at new CFN: TGCFN time )

RRC/ RB Reconfiguration complete (DTCH config, for FDD)


CM Method Switching: � Determination of the deactivation time (CFN) for old CM method, � CM deactivation command to RNC MAC-d � CM deactivation command to the NodeB /UE


New CM Method activation: � Determination of the activation time (new CFN) � CM activation command to RNC MAC-d � CM activation command to the Node B/UE

Criteria is reached => CM activation:

� Selection of the CM method � Determination of the activation time (CFN) � If HLS selected in DL

CM activation command to RNC MAC-d

NBAP/ Compressed Mode Command (Stop CM at CFN: CM configuration change CFN time)

RRC/ Measurement Control (Stop CM at CFN: CM configuration change CFN time )

UMTS Radio Mobility



Compressed method switching while CM not active: See call flow diagram below: MSC-CS Node B RNC UE

RRC/ RB Setup/Reconfiguration/Release (DTCH config, CM config for GSM, CM config for FDD)

RRC/ RB Setup/reconf/Release Complete







NBAP/ Compressed Mode Command (active pattern, starting CFN: TGCFN time)

RRC/ Measurement Control (active pattern, starting CFN: TGCFN time)

NodeB compares the CFN of DL FP DCH frames to TGCFN to trigger CM activation

RB configuration change => CM method switching: � RNC detects the CM method change � CM was not activated

NBAP/ Radio Link Reconfiguration Prepare (DTCH config, New CM configuration/method)


NBAP/ Radio Link Reconfiguration commit ( no Pattern active)

RRC/ RB Reconfiguration (DTCH config, for FDD, New CM configuration/method, no pattern active )

RRC/ RB Reconfiguration complete (DTCH config, for FDD)



New CM Method activation when HHO criteria will be reached:

� Determination of the activation time (new CFN) � CM activation command to RNC MAC-d � CM activation command to the Node B/UE




CM ends normally at a finite time,

6.4.9.4 CM METHOD SELECTION RULES:

• SF/2 selection method rules:

A - SF/2 is the default CM method applicable to all CS NB/WB/CSD mono RB on DCH

B - SF/2 is the default CM method applicable to all PS streaming mono RB on DCH excepted when SF equal 4

C - SF/2 is the default CM method applicable to all CS NB/WB + PS streaming RB(s) on DCH

UMTS Radio Mobility



D - SF/2 is the default CM method applicable to all CS NB/WB + PS streaming RB(s) + I/B on DCH

E - SF/2 is the default CM method applicable to all combinations including a RB over HSDPA/HSUPA

F - SF/2 is the default CM method applicable to multiple PS I/B x/y + PS Streaming u/p RB over DCH excepted for rates with x/y >= 64 and u/p >= 64 Kbps

G - SF/2 is the default CM method applicable to SRB Standalone combination

• HLS selection method rules:

A - HLS is the default CM method applicable to PS I/B x/y mono/multiplexed RB on DCH, excepted

for I/B 8 Kbps

B - HLS is the default CM method applicable to all CS NB/WB + PS I/B x/y combination on DCH, with x/2 & y/2 ≥ SRB max rate + AMR max rate (excepted for CS NB/WB + PS I/B 8/16 Kbps)

C - HLS is the default CM method applicable to all CSD 64 + PS I/B x/y mono/multiplexed RB over DCH, with x/2 & y/2 > 64 Kbps

D - HLS is the default CM method applicable to PS I/B x/y + PS Streaming u/p RB over DCH, with SF = 4, HLS is the default CM method applicable to multiple PS I/B x/y + PS Streaming u/p RB over DCH only for x/y >= 64 and (u/p > 64 and u/p <384Kbps), and x/y ≥ GBR

E - HLS is the default CM method applicable to CS NB/WB PS I/B x/y + PS Streaming u/p RB over DCH, with SF = 4, HLS is the default CM method applicable to multiple CS NB/WB PS I/B x/y + PS Streaming u/p RB over DCH only for x/y >= 64 and (u/p > 64 and u/p <384Kbps), and x/y ≥ GBR

F - SRB + CS Streaming u/v + PS I/B x/y

o for cases the allocated Ul/DlAsConf supports SRB max rate + u/v + x/y, with x/2 & y/2 ≥ SRB max rate + u/v kbps – and x/2 & y/2 ≥ GBR only the TFS for PS I/B are restricted during transmission with gap

G - RB combination SF 4 based: HLS is the default CM method applicable to any RB combination if defined with a SF equal to 4

Note: When a RB combination gets a SF=4 then RNC has the possibilities: o To apply the HLS method even through for PS streaming traffic, o To downgrade the granted rate of that RB combination with a greater SF

6.4.10 SRNS RELOCATION

� Interaction with SRNS relocation (UE not involved).

UMTS Radio Mobility



- Incoming SRNS relocation with HLS compressed mode activated from a non Alcatel-Lucent SRNC: For an incoming SRNS relocation the DRNC shall apply the following:

If the the CM configuration checking indicates different CM configurations (CM configuration of the relocation container not the same than the one on DRNC), then:

1. The Target RNC shall stop the current CM at the UE/NodeB side for any active TGPS at the CM

configuration CFN time, 2. The target RNC is configured with its MIB compressed mode configuration/CM prefered method,

There is no dynamical compressed mode configuration, since it may generate call drops, 3. The target DRNC shall start its CM at the new CFN time on the UE/NodeB side when the Alarm

HHO criteria is met

See hereafter the call flow for that use case.

Note: Sending the RRC measurement Ctrl to deactivate the initial compressed mode ensure a correct deactivation on UE side , in order to reduce some undecoded radio frame.

UMTS Radio Mobility



Target RNC CM deactivation: � Stop previous CM Methodif active for any active TGPS

SRNC relocation ends

SRNS reloc criteria reached � All radio links belong to the DRN � CM was activated before SRNS



RRC/ RB Reconfiguration Complete()

NodeB compares the new CFN of DL FP DCH frames to TGCFN to trigger CM activation

RANAP/ Relocation Request ACK

RRC/ RB Reconfiguration (DTCH config, CM config for GSM, CM config for FDD, no CM activation) )

RANAP/ Relocation Request

NBAP/ Radio Link Reconfiguration commit (no CM activation: no TGPS status)

RRC/ Measurement Control (Stop previous CM at CFN= CM Configuration change CFN)

NBAP/ Compressed Mode Command (Stop previous CM at CM Configuration change CFN)




NBAP/ Compressed Mode Command (active pattern, starting TGCFN)

RRC/ Measurement Control (active pattern, starting CFN= TGCFN)

Initial RRC connection DCCH establishment

Target SGSN

UE Node B Target RNC Source RNC

6.4.11 RNS INTER-RELEASE COMPATIBILITY USE CASES

The DRNC does not perform any check regarding CM activation and the CM Configuration/method since the DRNC does only relay the CM method/configuration to the NodeB(s), But the SRNC shall apply a filtering based on the IsHlsCmAllowedOnDRNC parameter value to match the supported CM method supported on the DRNC side (SF/2 or HLS). • UA06.0 SRNC facing an oldest DRNC version:

- New parameter required in the NeighbouringRNC MO: IsHlsCmAllowedOnDRNC to be set to false when a SRNC faces a DRNC not supporting the HLS methods otherwise it is set to “true”.

o While CM activation:

1) When SRNC facing an oldest DRNC version and if the CM method in use is SF/2:

- The SRNC does not need to apply any particular action on its Iur interface, follow on of the SF/2 CM method/configuration with the same TGPS to the DRNC

2) When SRNC facing an oldest DRNC version and if the CM method in use is HLS:

UMTS Radio Mobility



- If IsHlsCmAllowedOnDRNC is equal to “false” then

- For any RB combination to be supported on the SRNC/DRNC and the SF of the established combination is not equal to SF4:

- SRNC shall apply a CM method switching from the HLS method to the SF/2 method in UL and/or DL before to transmit any RNSAP RL Setup/reconfiguration message, refer to the CM method switching procedure described above.

- For any RB combination to be supported on the SRNC and DRNC and the SF of the current combination is equal to SF4:

- In spite of a SF/2 CM method cannot be applied to a RB with an SF4, SRNC shall apply a CM method switching from the HLS method to the SF/2 method in UL and/or DL before to transmit any RNSAP RL Setup/reconfiguration message, refer to the CM method switching procedure described above.

- CM activation is blocked while call has RB combination with SF=4. Inter-freq/inter-RAT HHO cannot be triggered as long as call has RB combination with SF=4. HHO is never processed whatever the reason of the handover. If HHO reason was alarm HHO 3G2G may be processed in blind mode (if allowed) at next Alarm condition.

o Without CM activation:

3) When SRNC facing an oldest DRNC version and if the CM method to be used is SF/2:

- No additional action, follow on of the CM method/configuration with the same TGPS, to the DRNC

4) When SRNC facing an oldest DRNC version and if the CM method in used is HLS:

- Same case as 2) but without CM deactivation,

See hereafter the call flow for that use case.

UMTS Radio Mobility



V6 Node B DRNC SRNC UE

� Radio links addition/reconf to the DRNS: � HLSCMAllowedOnDRNC = False � CM was activated before on SRNS

Initial RRC connection DCCH establishment

SRNS filtering on HLSCMAllowedOnDRNC: If HLS not supported on DRNS => CM method switching:

� RNC detects the CM method change � CM was activated � SF/2 method selected

NBAP/ Compressed Mode Command (Stop CM at CFN= CM configuration change CFN time)

RRC/ Measurement Control (Stop CM at CFN:= CM configuration change CFN time )

RNSAP/ Radio Link Setup Request (DTCH config, New CM config./method, TGCFN time )

RRC/ RB Reconfiguration (DTCH config, for FDD, New CM configuration/method, CM activation at new CFN= TGCFN time )

RRC/RB Reconfiguration complete (DTCH config, for FDD)

NBAP/ Radio Link Reconfiguration Prepare (DTCH config, New CM config./method,)

NBAP/ Radio Link Reconfiguration Ready ()

NBAP/ Radio Link Reconfiguration Commit (CM configuration activation at TGCFN time ())

� SF/2 method selected on V6 NodeB

� Determination of the activation time: New TGCFN

NBAP/ Radio Link Setup Request (DTCH config, New CM config./method, TGCFN time)

� SF/2 method selected on oldest NodeB version

� Transmission of the activation time: New TGCFN

� CM activation command to the Node B/UE

NBAP/ Radio Link Setup Response ()

RNSAP/ Radio Link Setup Response ()

Node B Non V6

• UA0x.x SRNC facing an UA06.0 DRNC version:

When facing an oldest version on its Iur interface the DRNC just relays the SF/2 CM method/configuration to the NodeB(s), nothing specific at this stage.

6.4.12 DRNS SCENARIOS

The DRNC does not perform any check regarding HLS activation and the AsConf. Similarly, the DRNC does not perform any check regarding the activation of different CM methods in UL & DL.

UMTS Radio Mobility



� ALU SRNC/ ALU DRNC: � not ALU SRNC/ ALU DRNC (IOT use case)

1. CM not activated in the SRNC,

No specific action required at the RNC/NodeB side. It corresponds to an existing use case, the SRNC configures the CM patterns as usual with the RRC measurement Ctrl message and with the NBAP/RNSAP RL Setup/reconfiguration messages and shall activate the CM when the RNC HHO alarm criteria are reached.

2. CM activated in the SRNC, No specific action at the RNC/NodeB side. It corresponds to an existing use case, the SRNC has configured the CM patterns as usual with the RRC measurement Ctrl message and with the NBAP/RNSAP RL Setup/reconfiguration messages and activated the CM when the RNC HHO alarm criteria are reached. When RL(s) is added on the DRNC, the DRNC relays the CM patterns to the dedicated NodeB. CM on DRNC side is activated at the correct TGCFN time. The TGCFN is the one calculated by the SRNC and shall ensure that the CM activation on DRNC is synchronised with the RL(s) established with the SRNC.

• For these use cases the DRNC does not need to check the CM method (for ALU SRNC/ ALU DRNC only).

• The DRNC and the Node B should accept any 3GPP compliant sequence or combination for compressed mode activation/deactivation for supported compressed mode methods.

� ALU SRNC/ not ALU DRNC

1. If the CM is active and CM method in used is SF/2:

The SRNC does not need to apply any particular action on its Iur interface, follow on of the SF/2 CM method with the same TGPS.

2. If the CM is active and CM method in used is HLS: - If IsHlsCmAllowedOnDRNC is equal to “false” then

Same action shall be performed as for the RNS inter release case see §6.4.11 (CM method switching).

� CM not supported on the DRNC side:

1. If the SRNC CM configuration is not supported by the DRNC, this last shall answer by a RNSAP RL Setup/Reconfiguation failure with the cause IE set to “CM not Supported”,

2. The SRNC shall not intend to activate any CM on that radio link anymore,

6.4.13 ALPHA CEM CARDS IMPACT

• HLS method is not supported on alpha CEM card,

• A NodeB with alpha CEM cards inside will generate a RL SETUP/RECONFIGURATION FAILURE at the compressed mode activation,

• A RL establishment on a NodeB with alpha CEM cards inside cannot be activated with a HLS CM method. If the HLS method is configured and activated on a node alpha card base, a NBAP/RNSAP RL SETUP/RECONFIGURATION FAILURE is transmit to the SRNC.

• On reception of the NBAP/RNSAP RL SETUP/RECONFIGURATION FAILURE message the SRNC shall stop the HLS procedure,

UMTS Radio Mobility



6.4.14 UE IMPACTS

Independently of the different characteristic to assign to the UE for a SF/2 or HLS compressed mode method use and according the cell profile to be measured by the UE the 3GPP rules shall be supported on the UE side (refer TS 25.133). If a R5/R6 UE is not capable to support CM activation while HSDPA/HSUPA a fallback to DCH is triggered (see [R4] and [R6]).

6.4.15 IMPACT ON OTHER PROCEDURES

This paragraph studies the impact of compressed mode on other procedures: • intra-NodeB soft handover • intra-RNC/inter-NodeB soft handover • inter-RNC soft handover

6.4.15.1 INTRA-NODEB SOFT HANDOVER

In this case, a new radio link is added to existing ones in the NodeB. In case Compressed Mode is already active for the existing UE Radio Links, the Radio Link Addition Request message sent to the NodeB contains the following information: • "De-activation Flag" IE set to "maintain active", since the compressed mode is kept active • "Scrambling Code Change" IE set to "code change", since the alternate scrambling method is used For the new radio link, The NodeB has to apply the same compressed mode and pattern parameters as for the other radio links already present in the NodeB for the given UE-network connection.




NBAP/ Radio Link Addition req (maintain active, code change)

NBAP/ Radio Link Addition resp


Figure 91: intra-NodeB soft handover during compressed mode

6.4.15.2 INTRA-RNC/INTER-NODEB SOFT HANDOVER

In this case, a new radio link is added belonging to a new BTS controlled by the Serving RNC. In case Compressed Mode is already active for the existing UE Radio Links, the Radio Link Setup Request Iub message sent to the NodeB contains the following information: • "Transmission Gap Pattern Sequence Information" IE, containing the pattern sequences information • "Active Pattern Sequence Information", containing the pattern sequence length, and the starting CFN

(TGCFN) • In case of SF/2: "Scrambling Code Change" IE set to "code change", since the alternate scrambling method

is used The new NodeB has to activate immediately the pattern sequence when receiving the RADIO LINK SETUP REQUEST message as specified in 25.433 §8.2.17.2. The RNC calculates the compressed mode parameters (e.g. TGCFN, TGPRC) such that the patterns are in sync with the other active set cells and UE.

UMTS Radio Mobility



In case of SF/2: It has to be noted that the 3GPP standard allows the 2 methods "scrambling code change" and "no scrambling code change" to be used simultaneously for radio links belonging to different NodeB. A fortiori, this is also valid for the inter-RNC soft handover case.





NBAP/ Radio Link setup req (code change, Pattern Sequence Info, TGCFN)


FP/ DL Sync (CFN)

FP/ UL Sync (ToA)

Figure 92: intra-RNC soft handover during compressed mode

6.4.15.3 INTER-RNC SOFT HANDOVER

In this case, a new radio link is added belonging to a new BTS controlled by a Drift RNC. In case Compressed Mode is already active for the existing UE Radio Links, the Radio Link Setup Request Iur message sent to the Drift RNC contains the following information: • "Transmission Gap Pattern Sequence Information" IE, as on Iub, containing the pattern sequences

information • "Active Pattern Sequence Information" IE, as on Iub, containing the pattern sequence length, and the

starting CFN (TGCFN) As in "intra-RNC/inter-NodeB soft handover" case, the RNC calculates the compressed mode parameters (e.g. TGCFN, TGPRC) for the cell on DRNC to be in sync with the ongoing CM pattern. In case Compressed Mode is not active, it can be activated later on in the call, using the COMPRESSED MODE COMMAND RNSAP message, in the same way as for the Iub interface. In case of SF/2: The "Scrambling code change" method is not specified on the Iur. The choice is left to the Drift RNC. In case of an Alcatel-Lucent Drift RNC, the "scrambling code change" is applied. In any case, the RADIO LINK ADDITION RESPONSE message indicates to the SRNC which method is used, so that the SRNC can inform the mobile on the scrambling code which is actually used on the new radio link.

UMTS Radio Mobility



Serving RNC UE Drift NodeB Drift RNC

RRC/ active set update (SF/2: code change)


RNSAP/ Radio Link setup req (Pattern Sequence Info, TGCFN)

RNSAP/ Radio Link Setup resp (SF/2: code change)

NBAP/ Radio Link setup req (Pattern Sequence Info, TGCFN, (SF/2: code change))



FP/ DL Sync (CFN)

FP/ UL Sync (ToA)

SCCP/ CR

SCCP/ CC

AAL2/ ERQ

AAL2/ ECF

FP/ DL Sync (CFN)

FP/ UL Sync (ToA)

AAL2/ ERQ

AAL2/ ECF

Figure 93: inter-RNC soft handover during compressed mode

When an Alcatel-Lucent Drift RNC is receiving a RNSAP RADIO LINK SETUP REQUEST message with compressed mode parameters, these parameters may not be consistent with the DRNC capability. This may happen in case the access network is composed of RNC from multiple manufacturers. In order to avoid compressed mode configuration which Alcatel-Lucent RNS is not able to support, The Alcatel-Lucent RNC implements a filtering function. Based on the output of this function, the RADIO LINK SETUP REQUEST or RADIO LINK ADDITION REQUEST received from the Iur is either accepted or rejected by the Alcatel-Lucent RNC. In this case, a rejection means that a RADIO LINK SETUP FAILURE or RADIO LINK ADDITION FAILURE is sent back to the SRNC. The filtering function is specified in the chapter on "Parameters".

6.4.16 CHANGE OF ALARM MEASUREMENT TYPE (COMMON HLS AND SF/2)

The Alarm Measurement Type, and associated compressed mode sequence depend on the Primary cell neighbouring list and priority setting, as explained in section 4.19 and 5.9. In case the primary cell is changed while compressed mode is running, the RNC keeps the ongoing measurement active independent of the configuration of the new Primary cell. This behaviour ensures that handover can be executed as fast as possible. The configuration of the new Primary cell is taken into account for the next measurement setup. In case of change of iMCTA trigger with crossover between inter-RAT and inter-frequency the ongoing measurement is aborted and the new measurement is started as detailed below. • The compressed mode is stopped when the CFN activation is passed. • The measurement criteria is evaluated • If the Alarm Measurement Criteria is still valid, measurements (either inter-freq or inter-system) are

activated, depending on the Alarm Measurement Type This is illustrated in the following figure:

UMTS Radio Mobility



Pattern sequence for inter-freq Inter-system CM

CMperiod

...

Trigger change. Detection of crossover from GSM to inter-frequency measurements Measurement Type is now set to "inter-freq" Current compressed mode pattern is stopped

A new CM scheme is started

Figure 94: change of CM scheme The following message flow illustrates what happens in case of change of CM scheme.

RRC/ Measurement Control (Release GSM measurement)

NBAP/ Compressed Mode Command (CM Configuration Change CFN, inter-frequency starting TGCFN)

RRC/ Measurement Control (setup inter-frequency measurement)

Inter-system CM is active. Change of trigger with crossover from GSM to inter-frequency target

RRC/ Measurement Control (2G pattern=inactive, TGPS reconf CFN, Fdd pattern=active, inter-frequency starting TGCFN)


Figure 95: Dataflow on change of CM scheme

The initial RRC MEASUREMENT CONTROL message instructs the mobile to stop the GSM measurement. The subsequent RRC MEASUREMENT CONTROL messages provide the mobile with

• a list of inter-frequency cells to be monitored • a TGPS reconfiguration CFN, at which all pattern sequences shall be de-activated. This IE has the same

value as the CM Configuration Change CFN of the NBAP message below. • a starting CFN for the inter-frequency pattern sequence

The NBAP COMPRESSED MODE COMMAND contains a CM Configuration Change CFN, indicating the CFN at which the NodeB shall de-activate all the on-going pattern sequences. This message also contains a starting CFN for the inter-frequency pattern sequence. The procedure is applicable independently of the CM method.

6.4.17 DEFENCE MECHANISM FOR UE NOT SUPPORTING CM WITH HSPA

Some non-standards conforming UEs do not support compressed mode in combination with HSDPA or HSUPA. If compressed mode activation for HSxPA fails or the UE indicates in its capability information that it does not compressed mode with HSUPA or for HSUPA calls if CM is disabled at OAM level then a reconfiguration to DCH is performed and compressed mode is activated with the DCH configuration. For details refer to [R4] (HSDPA) and [R6] (HSUPA).

UMTS Radio Mobility



6.4.18 PARAMETERS

This chapter lists all the configuration parameters for Compressed mode, most of them being part of 25.331

6.4.18.1 DYNAMIC PARAMETERS

These parameters are not accessed by the operator. The following set of parameter is present for each pattern, being active or not.

TGPS Status Flag active, inactive current status of the Transmission Gap Pattern Sequence

TGCFN Integer (0..255) Connection Frame Number of the first frame of the first pattern within the Transmission Gap Pattern Sequence.

UL/DL mode UL only, DL only, UL/DL Defines whether only DL, only UL, or combined UL/DL compressed mode is used. The value of this parameter depends on the UE classmark.

6.4.18.2 O&M PARAMETERS

This list contains the parameters which are used to configure the CM function. For the parameters displayed at the OMC-R level, it is always possible to change the value. If this should occur, there is no guarantee regarding Alcatel-Lucent UTRAN performances, or interoperability with mobiles. Parameters at the RNC level Most of the parameters listed below are defined at the RNC level.

6.4.18.2.1 GENERAL PARAMETERS

Name Definition Granularity gsm450Present YES: there exist GSM neighbouring cells of that frequency

band in the access network NO: otherwise


gsm480Present YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise


Gsm850Present YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise


Gsm900PPresent YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise


Gsm900EPresent YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise


Gsm900RPresent YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise


UMTS Radio Mobility







Name Object/Class Definition isGsmCModeActivationAllowed DlUserService

Managed Object. Class 3

Indicates if compressed mode for GSM is allowed for this DL UserService.

isInterFreqCModeActivationAllowed DlUserService Managed Object. Class 3

Indicates if the Compressed Mode for inter-frequency is allowed for this DL UserService.

isHlsCModeAllowed RadioAccessService Class 3

Indicates if compressed mode by HLS is allowed or not.

isHlsCmMethodPreferred UlUserService Managed Object. Class 3

Indicates if HLS is the preferred method of compression for generating uplink compressed mode gaps

isHlsCmMethodPreferred DlUserService Managed Object. Class 3

Indicates if HLS is the preferred method of compression for generating downlink compressed mode gaps

IsHlsCmAllowedOnDRNC NeighbouringRNC Managed Object. Class 3

Indicates if a ALU-DRNC is HLS method capable,

isSimCMAllowed[not supported in this version]

DlUserService and UlUserService Managed Object. Class 3

If this parameter is set to TRUE than the RNC is allowed to use simultaneous compressed mode for inter-frequency and 2G inter-RAT measurements for this service. Simultaneous inter-frequency and 2G inter-RAT measurements are not possible for certain RAB combinations due the enhanced compressed mode requirements. If simultaneous compressed mode is requested but not possible then the RNC uses single compressed mode as per parameter is3GHandoverPreferred. Engineering guideline: TRUE for all RAB combinations with - isHlsCmMethodPreferred=No, or - isHlsCmMethodPreferred=Yes if throughput reduction by simultaneous CM pattern is acceptable. Otherwise: FALSE

6.4.18.2.2 PATTERN PARAMETERS

A certain number of pattern sequences can be defined in Alcatel-Lucent UTRAN. For each of the pattern, the available parameters are described in the table below. Those parameters are defined at the cell level. ALU uses a double frame CM pattern.

Name Range Definition TGMP FDD measurement,

GSM RSSI measurement, GSM Initial BSIC identification, GSM BSIC re-confirmation

Transmission Gap pattern sequence Measurement Purpose.

TGPRC Integer (1..511, Infinity) The number of transmission gap patterns within the Transmission Gap Pattern Sequence.

UMTS Radio Mobility



TGSN Integer (0..14) Transmission Gap Starting Slot Number The slot number of the first transmission gap slot within the TGCFN.

TGL1 Integer(1..14) The length of the first Transmission Gap within the transmission gap pattern expressed in number of slots

TGL2 Integer (1..14) The length of the second Transmission Gap within the transmission gap pattern

TGD Integer(15..269, undefined) Transmission gap distance indicates the number of slots between starting slots of two consecutive transmission gaps within a transmission gap pattern

TGPL1 Integer (1..144) The duration of transmission gap pattern 1 expressed in number of frames

TGPL2 Integer (1..144) The duration of transmission gap pattern 2 expressed in number of frames

TGCFNoffset Integer(0..255) used as: TGCFN = (CFNx+TGCFN offset) mod 256 expressed in number of frames

N Identify abort Integer(1..128) Indicates the maximum number of repeats of patterns that the UE shall use to attempt to decode the unknown BSIC of the GSM cell in the initial BSIC identification procedure

T Reconfirm abort

Integer(1..20) Indicates the maximum time allowed for the re-confirmation of the BSIC of one GSM cell in the BSIC re-confirmation procedure. The time is given in steps of 0.5 seconds.

GSM and/or FDD inter-frequency measurements: The following table provides preferred sets of parameters which will be used in this version:

Pattern purpose GSM RSSI

Measurements GSM Initial BSIC

Identification FDD Measurements

TGPRC 8 3x26=78 50 TGSN 8 8 10 TGL1 14 14 10 TGL2 undefined undefined undefined TGD undefined undefined undefined TGPL1 6 6 6 TGPL2 undefined undefined undefined TGCFNoffset 0 8x6=48 3 N_IDENTIFY_ABORT not applicable 26 not applicable T_RECONFIRM_ABORT not applicable not applicable not applicable

Remarks on pattern parameters for simultaneous GSM and inter-frequency measurements: • In case of simultaneous measurements two CM gaps occur within each Transmission Gap Pattern (TGP), the

GSM RSSI or BSIC Identification gap and the FDD measurement gap. These two gaps are spread by applying the TGCFNoffset=3 for FDD measurements.

6.4.18.2.3 POWER CONTROL PARAMETERS

This set of parameters is linked to power control algorithms used by the BTS when compressed mode is active. Those parameters are defined at the cell level.

UMTS Radio Mobility



Name Range Definition RPP mode 0, mode 1 Recovery Period Power control mode

during the frame after the transmission gap within the compressed frame. Indicates whether normal or compressed Power Control mode is applied

ITP mode 0, mode 1 Initial Transmit Power is the uplink power control method to be used to compute the initial transmit power after the compressed mode gap.

DeltaSIR1 Real(0..3 by step of 0.1) Delta in DL SIR target value to be set in the UE during the frame containing the start of the first transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase)

DeltaSIRafter1 Real(0..3 by step of 0.1) Delta in DL SIR target value to be set in the UE one frame after the frame containing the start of the first transmission gap in the transmission gap pattern.

DeltaSIR2 Real(0..3 by step of 0.1) Delta in DL SIR target value to be set in the UE during the frame containing the start of the second transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase) When omitted, DeltaSIR2 = DeltaSIR1.

DeltaSIRafter2 Real(0..3 by step of 0.1) Delta in DL SIR target value to be set in the UE one frame after the frame containing the start of the second transmission gap in the transmission gap pattern. When omitted, DeltaSIRafter2 = DeltaSIRafter1.

The following table provides preferred sets of parameters which will be used in this version:

RPP mode 0 ITP mode 0 DeltaSIR1 Not needed DeltaSIRafter1 Not needed DeltaSIR2 Not needed DeltaSIRafter2 Not needed

6.4.18.2.4 STATIC PARAMETERS

This set of parameter is static, and not displayed at the OMC-R level. These parameters are defined at the RNC level.

Name Range Definition Downlink compressed mode method

puncturing, SF/2, higher layer scheduling

Method for generating downlink compressed mode gap

Uplink compressed mode method

SF/2, higher layer scheduling

Method for generating uplink compressed mode gap

Downlink frame type

A, B See 25.212, §4.4.2

Scrambling code change

code change, no code change Indicates whether the alternative scrambling code is used for compressed mode method 'SF/2'

UMTS Radio Mobility



In this version, these parameters will be using the following values: Static parameters per Ul/DlAsConf:

Downlink compressed mode method SF/2, HLS, SF/2&HLS Uplink compressed mode method SF/2, HLS, SF/2&HLS Downlink frame type B , A Scrambling code change code change, no code change

6.4.18.2.5 CONTROL PERFORMED BY THE ALCATEL-LUCENT RNC

The following table specifies the control which is performed by the Alcatel-Lucent RNC on the compressed mode parameters received in the RADIO LINK SETUP REQUEST or RADIO LINK ADDITION REQUEST Iur message.

Parameter received from Iur Alcatel-Lucent RNC control TGCFN No check TGSN No check TGL1 No check TGL2 No check TGD No check TGPRC No check TGPL1 No check TGPL2 No check Downlink compressed mode method SF/2, HLS Uplink compressed mode method SF/2, HLS Downlink frame type No check DeltaSIR1 No check DeltaSIRafter1 No check DeltaSIR2 No check DeltaSIRafter2 No check

6.5. 2G TARGET CELL CHOICE RADIO CRITERIA

6.5.1 DESCRIPTION

At each measurement period the mobile reports the measured cells even if all neighbour cells are not measured. By selecting the first cell reported by the mobile which fulfils the IMCTA criteria (the selected cell may not be the best cell on a given Carrier), the compressed mode duration is limited. On reception of inter-system measurement report, if a decision for handover is made, the RNC applies a 3-step process for the choice of the target cell:

• Measurement equalization • Measurement filtering • Target cell identification

Measurement equalization This process consists in adding an offset to the reported measurements, as in the following formula:

equalized measurement = reported measurement + Neighbouring Cell Offset The Neighbouring Cell Offset parameter is configured at the OMC-R for each GSM neighbouring cell. In the Iur case, this parameter is provided by the DRNC as the Radio Link is added. In case no valid value is provided by the DRNC, the Alcatel-Lucent SRNC uses 0 as a default value. Measurement filtering

UMTS Radio Mobility



Following the measurement equalization, the following condition is evaluated. When not fulfilled, the corresponding cell is considered as not eligible. The following criteria are evaluated on the measurements reported by the mobile (i.e. not equalized)

GSM Carrier RSSI > minimumGsmRssiValueForHHO Target cell identification The target is chosen by the iMCTA function based on different criteria (radio, load,. refer to § 4.19). if no measurement is valid or if there is no eligible cell in the list reported by the mobile • if a blind target has been defined for the Primary, then a handover is tried towards that cell • else no handover is tried For further details on measurements, please refer to the section 6.2. Note: In intra-freq periodic mode, if a cell was reported in a previous measurement report and is missing in the new report then the 'Missing Measurement' algorithm applies as specified in section 6.3.2.

6.5.2 PARAMETERS

Name Object/Class Definition minimumGsmRssiValueForHO RadioAccessService

Class3 Threshold on GSM carrier RSSI for inter-system target cell eligibility

gsmCellIndivOffset GsmNeighbouringCell Class3

Offset used for "target cell equalization"

6.6. FDD TARGET CELL CHOICE INTER FREQUENCY RADIO CRITERIA

6.6.1 DESCRIPTION

At each measurement period the mobile reports the measured cells even if all neighbor cells are not measured. By selecting the first cell reported by the mobile which fulfills the IMCTA criteria (the selected cell may not be the best cell on a given Carrier), the compressed mode duration is limited. On reception of inter-frequency measurement report, if a decision for handover is made, the RNC applies a 3-step process for the choice of the target cell:

• Measurement equalization • Measurement filtering • Target cell identification

Measurement equalization This process consists in adding an offset to the reported measurements, as in the following formula:

equalized measurement = reported measurement + Neighbouring Cell Offset The Neighbouring Cell Offset parameter is configured at the OMC-R for each FDD neighbouring cell. In the Iur case, this parameter is provided by the DRNC as the Radio Link is added. In case no valid value is provided by the DRNC, the Alcatel-Lucent SRNC uses 0 as a default value. Measurement filtering Following the measurement equalization, the following condition is evaluated. When not fulfilled, the corresponding cell is considered as not eligible.

UMTS Radio Mobility



The following criteria are evaluated on the measurements reported by the mobile (i.e. not equalized) CPICH Ec/No > minimumCpichEcNoValueForHHO and CPICH RSCP > minimumCpichRscpValueForHHO

Target cell identification The target cell is chosen by the iMCTA function based on different criteria (radio, load, FDD layer priority... refer to § 4.19).

6.6.2 PARAMETERS

Name Object/Class Definition neighbouringCellOffset UMTSFddNeighbouringCell

Class3 Offset used for "target cell equalization"

minimumCpichEcNoValueForHO DlUserService Class3

CPICH Ec/No threshold for inter-frequency cell eligibility

minimumCpichRscpValueForHO DlUserService Class3

CPICH RSCP threshold for inter-frequency cell eligibility

6.7. NEIGHBOR CELLS FLEXIBLE MANAGEMENT

6.7.1 DESCRIPTION

The Alcatel-Lucent UTRAN allow any combination of intra-freq, inter-freq and 2G inter-RAT neighbour cells in SIB11

• If feature “SIB11 enhancements” is activated (parameter isEnhancedSib11Allowed set to False): as long as the total number does not exceed 48 or 47 depending whether Measurement control is activated in SIB11).

• If feature “SIB11 enhancements” is not activated (parameter isEnhancedSib11Allowed set to True): up to the maximum of 96 (32 each).

. This will improve the call setup success rate and therefore it will increase the quality of the 3G network. At OAM level, for a given Fdd Cell, the operator can flag among all neighbour cells (Intra Frequency/ Inter Frequency/ Inter Rat) the neighbour cells to be put in SIB11 and in the RRC Measurement Control message.

6.7.2 ALGORITHM

If SIB11AndDCHNeighbouringFddCellAlgo parameter is set to classic, the Fdd neighbour selection is done by the RNC and the number max of UMTS Fdd neighbor cells to be put in SIB11 is limited to the first 16 Intra Freq and the first 15/16 inter Freq cells. For the Measurement Control message building, all Fdd neighbour cells (intra freq/inter freq) are put in the message. For inter Rat neighbor cells the selection depends on the sib11OrDchUsage parameter value. If SIB11AndDCHNeighbouringFddCellAlgo parameter is set to manual, the neighbor number flexibility (i.e. any combination of intra-freq, inter-freq and 2G inter-RAT neighbor cells allowed in SIB11 within a global limitation of 47/48 or 96 neighbor cells according to isEnhancedSib11Allowed value) applies (all neighbor cells may be selected by the operator). Each neighbor cell will be selected according to sib11OrDchUsage parameter value. The SIB11 neighboring filling based on flagged cells is processed in the following order: Intra Frequency cells, Inter frequency cells and Inter Rat cells. The selection ends when all requested cells are encoded or the encoding fails or the number max of neighbor cells is achieved.

UMTS Radio Mobility



Note: The System block information 11 is limited to 16 segments. The RRC description ([A4]) defined a message format which may exceed the 16 segments when too many IE are set. The Alcatel-Lucent RNC controls the size of the SIB11 message during the ASN1 encoding of the data provisioned at OAM level. An Alarm is sent by the RNC to the OMC-R. If SIB11 enhancement procedure is allowed and there is ASN-1 encoding errors, RNC shall not update SIB11 with a truncated list of neighbours as per current solution but let NodeB continue to broadcast current SIB11. [Global Market - This especially might be the case if feature HCS has been enabled simultaniously (refer to 4.23, FDDCell::isHcsUsed) which requires that HCS related Information Elements are to be added to SIB11. As this will lead to a shrinkage of the space available for neighbour data, it might not be possible to add data for all neighbours to SIB11.A tradeoff between number of neighbours to be supported for a cell, the number of parameters deviating from defaults and the usage of HCS in order to cope with SIB11limitations imposed by 3GPP shall be found.] Note: SIB12 follows same rules as SIB11 to select cells and set parameters in the message

6.7.3 PARAMETERS

Name Object/Class Definition Sib11OrDchUsage gsmNeighbouringCellList Enum

(sib11AndDch,sib11Usage,dchUsage) Indicates if the cell has to be put in SIB11 and/or the Measurement Control messages.

Sib11OrDchUsage UMTSFddNeighbouringCell Enum (sib11AndDch,sib11Usage,dchUsage) Indicates if the cell has to be put in SIB11 and/or the Measurement Control messages. This neighbour Fdd cell parameter is valid if SIB11NeighbouringFddCellAlgo parameter is equal to manual.

SIB11AndDCHNeighbouringFddCellAlgo FDDCell Class 3

Enum (classic, manual) classic: The first 16 UMTS Fdd neighbour cells in the Fdd neighbor list (Intra Freq or Inter Freq) are selected for SIB11 manual: The UMTS Fdd neighbour cells in the Fdd neighbor list (Intra Freq or Inter Freq) are selected for SIB11 and/or Measurement Control according to Sib11OrDchUsage value.

isEnhancedSib11Allowed FDDCell Class 3

This parameter is used to enable/disable feature "SIB11 enhancements" allowing to add more than 48 neighbour cells to System Information Block type 11

UMTS Radio Mobility



7. ABBREVIATIONS AND DEFINITIONS

7.1. ABBREVIATIONS

ALCAP AAL2 signalling AO Always On ARFCN Absolute Radio Frequency Channel Number ATM Asynchronous Transfer Mode BCCH Broadcast Control Channel BSIC Base transceiver Station Identity Code BTS Base Transceiver Station CAC Call Admission Control CAS Component Administration System CFN Connection Frame Number CIO Cell Individual Offset CM Compressed Mode CN Core Network CPICH Common Pilot Channel CRNC Controlling Radio Network Controller CS Circuit Switched CSD Circuit Switched Data DCCH Dedicated Common Channel DCH Dedicated Channel DRNC Drift RNC DHO Diversity Handover DSCH Downlink Shared Channel DTCH Dedicated Traffic Channel DTM Dual Transfer Mode E-DCH Enhanced DCH EPS Evolved Packet System FACH Fast Access Channel FDD Frequency Division Duplex GPRS General Packet Radio Service GTP GPRS Tunnelling Protocol HCS Hierarchical Cell Structure HHO Hard HandOver HLS Higher Layer Scheduling HSDPA High Speed Downlink Packet Access HS-DSCH High Speed Downlink Shared CHannel HSUPA High Speed Uplink Packet Access HSS Home Subsciber Server I/B Interactive/Background IF Inter Frequency iMCRA Intelligent Multi Carrier RRC Connection Allocation iMCTA Intelligent Multi Carrier Traffic Allocation IP Internet Protocol IRAT Inter RAT – usually GSM measurements or GSM handover LTOA Latest Time Of Arrival MAP Mobile Application Part MME Mobility Management Entity MSC Mobile Switching Centre NB Narrow Band NBAP Node B Application Part PCH Paging Channel PGW PDN Gateway PS Packet Switched RAB Radio Access Bearer

UMTS Radio Mobility



RACH Random Access Channel RAN Radio Access Network RAT Radio Access Technology RANAP Radio Access Network Application Part RB Radio Bearer RL Radio Link RNC Radio Network Controller RNS Radio network subsystem RNSAP Radio network subsystem Application part RRC Radio Resource Control RSCP Received Signal code Power SCCP Subsystem Connection Control Protocol SF Spreading Factor SGSN Serving GPRS Support Node SGW Signalling Gateway SHO Soft HandOver SIB System Information Block SRB Signalling Radio Bearer SRLR Synchronous Radio Link Reconfiguration SRNC Serving RNC SRNS Serving Radio network subsystem TDD Time Division Duplex TGCFN TGPS CFN TGPRC TGPS Repetition Count TGPS Transmission Gap Pattern Sequence TRB Traffic Radio Bearer UP User Plane URA UTRAN Registration Area UTRAN Universal Terrestrial Radio Access Network WB Wide Band

7.2. DEFINITIONS

Empty chapter.

APPENDIX 1: EVENTS CONFIGURATION

Feature ID

Feature Reporting quantity Group Nb Criteria

Category

17569 HHO 3G3G Periodic: Ec/No&RSCP Mobility 1 Inter Frequency 27219 Full Event trigger support Event 2D,2F Ec/No Mobility 2 Inter Frequency 27219 Full Event trigger support Event 2D,2F RSCP Mobility 2 Inter Frequency xxxxxx HHO 3G2G Periodic: GSM Carrier RSSI Mobility 1 Inter RAT 32525 UA06.0 Call trace

enhancement Periodic: CPICH Ec/No&CPICH RSCP

Call Trace 1 Intra Frequency

33692 Air Status Measurement Periodic: CPICH Ec/No&CPICH RSCP

Call Trace 1 Intra Frequency

xxxxxx, 27219

SHO, Full event support and HHO towards CDMA

SIB11 XOR (1A,1B,1C,1D,1E,1F,1J) XOR periodic intra freq Ec/No&RSCP

Mobility 7 Intra Frequency

34227 State transitioning enhancements

Periodic, once(meas ctrl or SIB11): Ec/No

Mobility 1 Intra Frequency

30443, Support of WCDMA to Event 1D, 1E, 1F, 2D, 3A or (1A Mobility 2 Intra Frequency

UMTS Radio Mobility



33853 CDMA handover and 1C) 21302 33814

HHO intra Freq inter RNC Event: 1A Mobility 1 Intra Frequency

34212 ATT Perf monitoring Periodic: CPICH Ec/No&CPICH RSCP

Monitoring 1 Intra Frequency

24089 CellId RTT positioning Periodic, once: Path Loss Positioning 1 Intra Frequency 77736 Non GPS LBS Periodic,once, successively:

CPICH Ec/No&CPICH RSCP&Pathloss

Positioning 1 Intra Frequency

30223 30250

UA05.0 call trace enhancements

Periodic: DL TrCH BLER Call Trace 1 Quality

33692 Air Status Measurement Periodic: DL TrCH BLER Call Trace 1 Quality 34212 ATT Perf monitoring Periodic: DL TrCH BLER Monitoring 1 Quality xxxxxx Always ON Event 4A

. RLC Buffer Payload

. Average of RLC Buffer Payload

. Variance of RLC Buffer Payload for RBs multiplexed onto the same Transport channel

RRM 1 Traffic Volume

33565 UA06 Always on devlopment

From 0/0 only (Event 4A): . RLC Buffer Payload . Average of RLC Buffer Payload . Variance of RLC Buffer Payload for RBs multiplexed onto the same Transport channel

RRM 1 Traffic Volume

34227 State transitioning enhancements

Event: 4A (1 per ul DCH) RRM 1 Traffic Volume

30223 30250

UA05.0 call trace enhancements

Periodic: UE transmitted power Call Trace 1 UE Internal

33692 Air Status Measurement Periodic: UE Tx Power&Rx-Tx Type 1

Call Trace 1 UE Internal

32525 UA06.0 Call trace enhancement

Periodic: UE Tx Power&UE Rx-Tx Time Difference

Call Trace 1 UE Internal

24089 CellId RTT positioning Periodic, once: Tx Type2 Positioning 1 UE Internal 34226 RAB modification Event 6A: UE transmitted power RRM 1 UE Internal 34227 State transitioning

enhancements UE TX power (additional meas of 4A)

RRM 1 UE Internal

33692 Air Status Measurement GPS timing of cell frame Call Trace 1 UE Positioning 27615 Assisted GPS

Enhancements (step 2) Periodic: GPS timing of cell frame

Positioning 1 UE Positioning

33331 Alarm HHO based on UL Tx power

Event 6A and 6B: Ue Transmitted power

Mobility 2 UE Internal

24089 CellId RTT positioning Periodic, once: Rx-Tx Type1 Positioning 1 UE Positioning

�� END OF DOCUMENT

Documents

UMT SYS DD 0054 V11.06 UMTS Radio Mobility Approved Standard