UMTS Radio Mobility

Document number: Document issue: Document status: Date: UMT/SYS/DD/0054 11.06/EN Approved_Standard 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 AlcatelLucent. 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

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 Issue 11.03 / EN, Draft Introduction of the following feature: • 81204 - Dual cell Hsdpa operation

23/March/2010 Issue 11.02 / EN, Draft Introduction of the following feature: • 81213 - Load balancing between HSPA carriers

28/January/2010 Issue 11.01 / EN, Draft 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
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

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

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 3/244

UMTS Radio Mobility

CONTENTS
CONTENTS..............................................................................................................................................4 1. INTRODUCTION ...............................................................................................................................14 1.1. 1.2. 1.3. 1.4. OBJECT ....................................................................................................................................14 SCOPE OF THIS DOCUMENT ........................................................................................................14 AUDIENCE FOR THIS DOCUMENT .................................................................................................15 DEFINITIONS AND SPECIFICATION PRINCIPLES.............................................................................15

2. RELATED DOCUMENTS .................................................................................................................15 2.1. 2.2. APPLICABLE DOCUMENTS ...........................................................................................................15 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
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 4/244

....1 Connection Release ..............4............................................................5.................................47 4..........................32 4..............3...............................................47 4...9...............................................31 4....................4..6..56 4....5..6.....3 Criteria S.......3..................3.............1 Intra-RNC case ...................................................5......................5........................1...........4.2 At UTRAN/FDD neighbouring cell level.44 4................................2 MeasurementS configuration.....6 Dual cell hsdpa case...3...................................4........................................4 CipherinG......52 4.............7 Overall cell reselection process when using absolute priority ...............4............................6...............................5 Parameters ................ 2G TO 3G HANDOVER FOR CS DOMAIN .2 Target resource description ..............................................................3....................................6.........1.45 4....6 Core Network impacts ..................................55 2G TO 3G HANDOVER FOR CS + PS DOMAINS ....................................................................................33 4.......................................55 4.............51 4........5.......6............43 4..2 return on old channel ..............1 Description ...........4.................35 4..............4..............47 4........................................39 4..............................................................................................................................5........................3..............................................................55 4......55 4.....................5.................7 Use of Default Configuration ...............................................................56 4................................................53 4...........................................2 Inter-RNC case .............................56 4......................................................................5....1......4............................6...3..............................................3....53 4..............3.............33 4...4.4......................................................................................58 4....39 4....39 4..............2 At UTRAN/FDD neighbouring cell level................1 Description ...........................3 Algorithm..........3........3 Algorithm.............5....47 4..4.......35 4..........................................44 4.......1..........................1 Relocation Request Message structure..3 At GSM neighbouring cell level ................................4............................5 3G to E-UTRAN case ...........................................................5..4..........4.........................................3.....................2 Relocation Request Rejection ...............06/EN Approved_Standard 17/Sep/2010 Page 5/244 ..........................6.........................4 Parameters .........5......... CELL RESELECTION IN “CELL FACH AND CELL/URA PCH MODE” .2 Applicability ..................................40 4.........4 2G to 3G case.......................................52 4...........................................................................58 4..........................................................5..........6...58 4..........................................51 4....1..........................................................................................................................51 4..............4..............................33 4...........5................................4....1 At UTRAN/FDD cell level.....................................................................................5...........................................................................1 Description .........4......................7 Core Network impacts ...................................................................................................................................5........................................................51 4................1 HO Decision Process...................3.................................9....................................................................................................................................7..........................6.........................3.......................................2 Neighbouring cells measurement rules when using absolute priority ...............6...........6...............5.........................................................................39 4..................................................9... 4........................47 4...3 3G to 2G case......................4 Parameters .......................................................................6.6....3..............................................................6.....3 Target resource allocation in RNC ..............................1........................1 Dataflow .........4 Cell ranking criteria ..........................................53 4..............................3 At GSM neighbouring cell level ......................................4...............3 Relocation rejected by target RNC ..............6 Access Network impacts...........................................50 4....................9.................................................................................................39 4...................4........................44 4...........................................................................................................1............................................................6.......................................6....UMTS Radio Mobility 4.....................5 Access Network impacts................31 4................................50 4.....5 Cell ranking criteria when using absolute priority ....................................... use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11..........................................6 Dependencies with GSM ........52 4............6...............................................1.........................................................................2 Applicability ....................................................58 Passing on or copying of this document................................. 2G TO 3G HANDOVER FOR PS DOMAIN ..........................................................................54 4.....................9.................4.................... 3G TO 2G HANDOVER FOR PS DOMAIN ......................1 at UTRAN/FDD cell level .................................5 Access Network impacts............3..8....47 4..................................6.......34 4.39 4.......6 Overall cell reselection process....47 4................4 Failure cases.........4....................................................3.........................44 4...........9.......................................................................1 Neighbouring cells measurement rules ...................44 4............6...53 4.........................44 4..................2 Applicability .....6 Core Network impacts ................5 Integrity ..........4.3 Algorithm...............................................6..........38 4...

.............................................................2 MeasurementS configuration...........................10..............75 4......................................................................................2 Applicability ..............................67 4...........1................1 Description ....5 Integrity ............6 Dependencies with LTE.....77 4...............3.................................12.........................................3.........3................................................................................11...............2............67 4..................1 Dataflow ...........................................................81 4..............................59 4.......3 Failure cases.............................................. 3G TO 2G HANDOVER FOR CS+PS DOMAINS..........2 Successful Class A/DTM case .......................................74 4................12.............................................UMTS Radio Mobility 4.11............................................2 Relocation Request Rejection ........................................3 4..7 Target cell choice..13...................10......9.........63 4.63 4......................3.........................10...........10..........................................1 General .............1.....................................................................................5 Access Network impacts.........................................1..........................................................70 4..............................1 target cell synchronization failure ..12..............................................................................................3..............78 4............13...................................................................77 4.......2 MeasurementS configuration.............11...............2.................................1 Description .......................................4.................................3 Successful Class B case ................3............................................70 4..............58 Failure cases...............................10....................................................................9....6 Core Network impacts ................69 4.............11...............10.................70 4..............................................................................................9............................................................................................................73 4...............................59 4..............10..............2 MeasurementS configuration..06/EN Approved_Standard 17/Sep/2010 Page 6/244 ...................1................11................11.....73 4..............................75 4...........................70 4..........1 General ....................................12.....7 Core Network impacts ...............................4 4........61 4.................70 4.6 Access Network impacts.......11...............................................................................2..........................................................3 Algorithm............74 4..............................2...............3.....................................58 Parameters .............................................13.............8 Performance Management .........61 4........70 4........59 Core Network impacts .78 4....9............................................................... use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.......................................................12...........58 target cell synchronization failure .............................................12......................................10.................13......3.........1 HO Decision process ...................3 Algorithm...............................................................13............................................11...............................................................................4 Parameters .................................2 Algorithm...................1......13.....................................5 4.5 Parameters ...........................................10.......11...................................62 4.4.61 4...................................................................................................4 CipherinG...........................5 Access Network impacts.................................61 4............................61 4.............4 Failure cases................................3 Target resource allocation in RNC ....................2.12.11..................12..............................................................................................13...............6 4....................................................................................................................10..............................................................7 CS FALLBACK....12........81 4......1 Relocation rejected by target RNC .......................... INTER-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR.....................3 Target Cell Choice ...10..........................................................................9..........................................................................81 Passing on or copying of this document............................11.....4.......70 4.............................10..................................1 Relocation Request Message structure.......76 4........2 Applicability ........................................76 4.............61 4....65 4.................70 4...........................3 Target Cell Choice ............................3..76 4.12.................................................................1 HO Decision Process.................................................11..................................................6 Core Network impacts ...........................................................81 4............................................................12.........................................................70 4..78 4.............1 HO Decision Process....11................................................63 4..9...............................................3 Algorithm....................63 4.........10.........12................................................................ 4G TO 3G RELOCATION FOR PS DOMAIN ...............61 4...2 Applicability ...............................62 4.....................................70 4...........1......................63 4....................................59 Access Network impacts.................................................................... 3G TO 2G HANDOVER FOR CS DOMAIN .............................................77 4.........................................................................1 Description ....63 4..................................................10.............2...............59 4............................................................1 4...........................................................12..............................................4 handling Unsuccessful cases .12.......................................................12................................2 Relocation Preparation Failure .........................................................................................................................................................12......................................................3................11....4 Parameters ..........................76 4..........1 Description .................

...............................16............................................14.....................................15....1........................................................1 reception of measurement report measId 1 .....................................................................84 4...8 Performance management ...........................95 4..............................................93 4........................82 4...............................................14....... INTER-FREQUENCY INTER-RNC HANDOVER WITH IUR AND MEASUREMENTS......81 4..........................................93 4..1 Iur interface status .....................87 4........................88 4..................................................1....................3 Algorithm..............................................2 reception of measurement report measId 16 ...................3...............................................93 4....3................4 Failure cases.......................................15..............................14.....................................1........................95 4.2 Over the Iur.....16.....3 Algorithm........................7 Core Network impacts ...... use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.........1 Description.......................................15.3...........................15..........................................87 4..................................................3............13...15........5 Parameters .............3 HO decision ......82 4...........94 4..............3......................................4 Failure cases...................................8 Performance management ....................3...............1 Description .15......................................95 4..1 General ......................................................................................................................13.......................5 Parameters ..............................16.........94 4................1 General .........14.................................................89 4..................................................................................................16.......5 Access Network impacts............................................................16......16..........88 4..........................87 4..............................................................95 4................13.................18................15.......................18.........................................1 Description ..............................................................94 4...............................................................................................16..87 4....................95 4.........................82 4.....................1............................................................................................82 4........................................2 Measurement configuration ................2 Applicability ............................................83 4.......................................................................3 choice of target cell.............................................14........................95 Passing on or copying of this document........3....................83 4.............................................................................3 Target Cell Choice ........................83 4..........1 Description .....................................................82 4.......................................................84 4........................................................................17..15.............................94 4...........................................................................................................................13.....1 REDIRECTION AT CONNECTION SETUP (iMCRA step 1) ...................15.....17..........................................84 4......................................................3..14.........................................................................3....................90 4.84 4.........................................................3.......1 HO decision process............................2 Measurements configuration ............94 4...................................06/EN Approved_Standard 17/Sep/2010 Page 7/244 ..............5 Access network impact .........17.........81 4..7 Core Network impacts .......5 Parameters .6 Access Network impacts........................... INTER-FREQUENCY INTRA-RNC HANDOVER.............14........................................89 4.....................82 4...........................6 Access Network impacts....3 choice of target cell..........92 4...............................16..............17...........................1 Description ..................93 4......1..................................................................................14...................................4 From DRNC TO SRNC..................3 Algorithm....15..........................83 4......................................3...................................... INTRA-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR............................................................................................................13............14........................16..........................................17............................95 4..........................15...........87 4..................1.................................................................................................................1.. SRNS RELOCATION – “UE NOT INVOLVED” ...2 From SRNC TO DRNC............................................15......................................................94 4.4 Parameters .2 Applicability ..............................6 Core network impact.......................3............................................1 HO decision process.................14...........16............17.......................................95 4..................81 4.................................................................................................16...........................................................................................................................3 From DRNC TO DRNC.................................................................... REDIRECTION FEATURES FOR TRAFFIC SEGMENTATION ...........................89 4.....94 4..................4 Parameters ...88 4............................84 4.........3...............................................................87 4.......87 4......................85 4...2 Measurements configuration ...........2 Applicability ..............................4 Failure cases...18...............................14......14........................................6 Core Network impacts .......16...............................83 4...........................................................17...16............................82 4.....................................2 Applicability ......16......7 Core Network impacts .......6 Access Network impacts.....................................................94 4......UMTS Radio Mobility 4...................................................................................................................................................................3 Algorithm............................................16...................88 4...........3..............15.15...............................16.....................................................................

...............3 Algorithm......................2 Aplicability ............19................................................3.......1...............UMTS Radio Mobility 4....18................19......2 3G2G REDIRECTION AT RRC ESTABLISHMENT FOR SPEECH CALLS.............18............1...................97 4.18........................................................................ 120 4..................4........ 118 4..............3....19.....................................5 Performance management ............................06/EN Approved_Standard 17/Sep/2010 Page 8/244 ..............................................................18.......5 Performance management ..............................................................18.....................................................19...................18.........18.....................................3......19............ 111 4.....18.....................................................................................3.....3................................................. 111 4..18..............................3........................................................ 128 4..........1 Redirection Type = UE capability only............................ 120 4................18................19........................18...........2 Apllicability ..18... 111 4....4.......................... 122 4...... 122 4........................4 Parameters ................3.................. 125 4............................19. 115 4.........3.................................................... DUAL CELL HSDPA OPERATION .............................18...........................................4 Parameters ........4 Parameters ......4 Parameters .1...............19..........1 Description .......1...... 125 4................1 Interaction with Cell_FACH: ............................................................3 EMERGENCY AND PRIORITY CALLS.........2 Algorithm...........1 Description.............19........1 Active Set Update....................4................19.....5 IuR Aspects .............3.................................... INTELLIGENT MULTI CARRIER TRAFFIC ALLOCATION (IMCTA) ................................................1............................................3..................................................... 111 4........................6 Access Network impacts....................................18.....................................1 HHO from R99/SC/DC to DC .5 Parameters ...3........................................................19...............................7 Core Network impacts ..18.............................. 104 4...........97 4.............3....... 128 4...........2..18.........2 Redirection Type = UE capability and establishment cause . 104 4.....2.................3. 119 4.......................................2............................................................. 127 4................................... 119 4.......3......4 HSPA Load ..............................18..........3................................................99 4..............................2.....................................3 Emergency calls: .............5 Performance management .........5........................................................................................... 103 4................................................1...................... 115 4.........1 Soft Handover..........3 Redirection Type = Preferred FA..2 Primary Link Change ...... 128 4........................................... 126 4...............................................19.2.....................................1............................................................................18...........................................................................2 HHO from DC to SC/R99....2 Hard Handover .........................................................2.......................................... 114 4.... 104 4...............................................................4 Compressed Mode ..........................19...................... 121 4.............................18.................18........3 Uplink Aspects ................................1 Description........................................ 102 4..................................................................................................18................... 128 4.............................1............ 110 4.........................3...............................................................................99 4..........................18..................1...1 Description....................................................2........................2..... 108 4...5 PRIORITY BETWEEN RRC REDIRECTION FEATURES ..............................................1 description..........................................1...... 108 4.......18.......................... 109 4........... 116 4........................... 127 4......3.......1 UE Involved .....................1..........1........................3 Algorithm................3..............20......................................3. 122 4........ 125 4...........3 SRNS Relocation...........5 Redirection Type = None..4 failure cases:.....18......................... use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.....18............3..1.......................................................1....................19.................18. 121 4..................1 Description................................99 4.19...........................................18..........19..................18..........3 Algorithm...................................................3............ 126 4...........18..............................1............................................ 119 4...................................97 4..................................................................4 SRB Aspects....................................18................2 Applicability.............2 Applicability.............3....4............................................................19.......3..............5...................3 Algorithm......... 128 4..........................................................18...18.........18.......1........................3 Algorithm.............19........ 127 4...............................................98 4.................4 3G2G REDIRECTION BASED ON CELL LOAD..... 122 4................................................................................2................................. 129 Passing on or copying of this document...4... 108 4...................18...........................................................................2..............................2 Applicability....................................................3...........3........................................................97 4........1...2........................1.. 113 4...............................1................................ 121 4.....5 Initial Power on Redirection................................................................................... 104 4...........1............................3......... 119 4............20..............19..................................... 125 4.18............................... 115 4..............................................6 Messaging ............................4 Redirection Type = CAC..........19..2 UE Not Involved....18...................2 Interaction with follow-on / Subscribed Traffic Class:.

.................................. 149 4..................................1.......1..............................20.....3...............2 Iur management..................................................................................................2.........20.20.......20............20.............................. 149 4....2.......................................3.....1........................20.......................................20....21....3.2...............................1.............1.........................................2................................3.........8.2 iMCTA trigger = CAC FAILURE .. 147 4.......1 iMCTA Priority Table definition: General aspects............3................2...................... 133 4....... HSDPA AND HSUPA MOBILITY ..................................6 IMCTA Service for Traffic Segmentation Priority definition ............3 iMCTA Service Priority Table definition.............1 Management in Cell HSxPA ...6...............................................20.....................................................20.. 134 4..... 132 4.....................................................6...7.................20.....20.............................................. 147 4.............2...............2..........3..................................................................4.....2 IMCTA trigger is CAC FAilure..........21...............8...5 Performance Management ....2....3 Inter-frequency mobility .. 140 4................8..21......2.20..................... 146 4.........................................................................................20...........3.......20.. 135 4.........1...........2 Originating Fdd Cell eligibility .20..................1 Main functional steps ...............3............................................2 Redirection at connection setup ..... 146 4........ 140 4.... 131 4...................... 137 4......2 iMCTA trigger = CAC FAILURE .1....................... 145 4.........4..3 2G Inter RAT management ................................................................................... use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.................................................................. 129 4.....8....... 144 4....20..............................................................3 [USA Market] target FDD cell Load iMCTA load based HO criteria (used for CAC and Alarm): .......................1............................4.....21.................3 Neighbour Carriers Selection .................................................20............2.............. 149 4..20... 132 4............................21...............................3.....4......4 Target Fdd Cell eligibility (used for Service)..........1 IMCTA trigger is Service........................................21..........................2 iMCTA Feature activation ........20......20....2 HSDPA on existing layer ..5 Target 2G Cell eligibility.......20.................3......2 Crossover between iMCTA triggers or with others procedures...... 131 4...2 Applicability ......2 Applicability ....................... 148 4........................................20..........2....4 Neighbour Cells Selection for Measurement Reporting .....3............................20........... 141 4.................2.......4....................3 Algorithm......7 iMCTA Hard handover processing or iMCTA exit ........................................1.20......................................................................................20......... 131 4..........2.....................20............ 139 4.........4..20.20............. 140 4............1 iMCTA Options ............20....20.......................3....20...............3 IMCTA trigger is Alarm ..4 iMCTA Service Type definition ...... 147 4...........5 IMCTA Service Segmentation Priority Table definition .. 147 4..................... 139 4...1 cell load indicators .............. 133 4... 150 4......................1 Service Segmentation Option Definition..20.............................20.....3..1 iMCTA triggers.....................3 HSDPA Traffic Segmentation option definition...........3.........................3.1 Intra-frequency mobility ................................20..................1.................................1 HSPDA on dedicated layer..................20........ 135 4.................. 139 4.......2...20.3...........4.............. 141 4...1 Description ................................................................. 144 4...................4.......1 iMCTA trigger = SERVICE .................1 IMCTA HHO processing ....1..............4 iMCTA load based HO developments [USA Market]............................20.....................7... 148 4........3 iMCTA trigger = ALARM .............6 Target Cell Selection upon Measurement Report ................... 148 4................... 138 4...20............ 148 4............ 144 4..........................................................2 IMCTA Exit...........4.............................6 Target 2G Cell color definition ..... 134 4......................... 152 4........................................................4..........1....2 iMCTA Alarm and CAC Priority Tables definition ................2.............................2 Service Handover Option Definition .................8..... 138 4........................................... 139 4...........2 compressed mode ....................3........2..............................3....21..........1 Deployment scenarios ................................3 HSDPA and HSUPA call mobility procedures ............ 134 4................................20.....................................................06/EN Approved_Standard 17/Sep/2010 Page 9/244 .............21. 133 4.....................................................................3...........................................3.................1...............................................................4............21............3.. 133 4........................UMTS Radio Mobility 4......................................20....... 134 4..20..................20.................................................1.........3...................3 iMCTA trigger = ALARM .......... 152 Passing on or copying of this document........ 134 4.................20.......................................................... 146 4........ 132 4............ 141 4...............................................8 iMCTA Cell load criteria ...............3......................................20..........................3.............. 143 4.............. 131 4...21......................................2..........1................................4 Inter-system mobility........ 150 4.....................................20................. 137 4............20....... 136 4.................4 Parameters ..............................2.....21....1.21.1 iMCTA trigger = SERVICE ...3.... 136 4...............................3................................................................................2.......2 iMCTA Priority Tables........8..........................................................6.....5 Compressed mode and measurement configuration .....

.............4....4.........2 Applicability ................................................3......... 155 4.......................2.........4.............................................................................................................................4 Parameters ..............3 Summary .2............1 Description of event-triggered reporting measurements based on relative thresholds ..................3........... 152 Parameters ..... 168 5.............. COMMON PROCEDURES ..........................................4.....................................................2 SRLR blind window....................................................................2...... 163 4.................UMTS Radio Mobility 4...............................................................................22........3 Algorithm............................................ 152 Core Network impacts ................23...................................... 163 4......3 feature interworking ........................23.......... PERIODIC MEASUREMENT REPORTING MODE...2................................ 168 5................................. 168 5.....3......... ACTIVE SET MANAGEMENT.3..........3 1C event configuration................................... 168 5........ 2F........... 164 5...............................................................................21................................................................................................. 173 5.................................................................................3 4...4..............................................................................22......................................3.................................................... 156 4........................................ 166 5.....4 Parameters ......2........... 177 5....22......3 At GSM neighbouring cell level .......................4 Events 2D..06/EN Approved_Standard 17/Sep/2010 Page 10/244 ....................................................................... 158 4..23.......................4..........................................3...................................... 155 4.....................................................................5 4.......................................................... 152 4.................1 Description ........................................3 Event 1D .................6 Algorithm........ 156 4...............3....3. 161 4..............................................1 Cell Reselection Criteria when HCS is used .....................................2...5 Access Network impacts...........................................................23.................. 166 5...........................................3....5 Access Network impacts.................................................................................................2 Description of event-triggered reporting measurements based on Absolute thresholds ..........................................................2.............2...3.... 155 4................23........ 1J .................................2 Inter RNC Case ...............................................................23............................................................................................................................. 152 Access Network impacts............4 Parameters .......2 configuration ... 167 5........... 166 5...................................................................... 178 5................... 1E................................................. 168 5.....2....................................................................................... 168 5...........3 Algorithm........... 156 4.................... 176 5................................... 170 5........................................................................2 1B event configuration.2.....................................2.........3....................2..... 164 5.................................................2.3...........2............1................1 At UTRAN/FDD cell level...............2..........6 Core Network impacts ........ INTRA-FREQUENCY EVENT TRIGGERED MEASUREMENT REPORTING MODE ......................1 Event 1A. 6A........................21.........................1 1A event configuration.............................................................................4 Configuration .............4...... 167 5..3 Parameters for periodic reporting mode . 174 5...................... 1F ............1 Description .... 155 4..........6 Core Network Impacts ......21........... 153 4...........4 Case of intra-frequency Event-Triggered Reporting mode........ 163 5..............................................................................1 Description ......3.....3............. 161 4...........3.................................... 153 4................................ 171 5....................................2 Event 1B.................... 171 5......................................1 Common ID procedure handling.........................................1 Algorithm for periodic reporting mode...................4 4....3........23............................................................2..............3..................... use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11...................................................22...........21.................................23......................................2..... MOBILITY IN CELL_PCH AND URA_PCH RRC STATES ............ HCS: CELL RESELECTION CONTROL IN A HIERARCHICAL CELL STRUCTURE [GLOBAL MARKET].........2..............................3.............................2 Enhanced Algorithm for periodic reporting mode .2 Applicability ....................................................................... 169 5.............................................................3 Algorithm................................................2.................22...............2........................................................................................22..............3....2 Measurement Control Failure ...... 164 5.................................23........................4........... 168 5.................23............... 159 4................ 178 Passing on or copying of this document................................2 At UTRAN/FDD neighbouring cell level....... 164 5......4..... 165 5...................................................... 6B .....1 Radio Link color .....................4............................................4 1E event configuration......................................3............... 1C.. 157 4........................................................................4................................ 161 4.. 176 5...3......................... 167 5.4...........23.....................22...................................................4..4................................. 163 4.23...............4.2.....................................................

... 200 6............... 181 5.............................. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11........................ 185 5.......1....3 Configuration ................................................................. 205 6.......1.................... 181 5............................ 189 5..........2 Parameters . 190 5...................4....................................................................2...................................... 189 5.1............3..............................3.......................................................4. 189 5....1 Activation/Deactivation ...............9....................... 203 6..........3.................................................................. 183 5........5 Performance management ....1 Description.............................2..............................2 Reported cells ..06/EN Approved_Standard 17/Sep/2010 Page 11/244 ................1......................3...............................9....................................................................................................2 Algorithm..............2 Traces ........3...............................1 Description .................. INTRA-FREQ MEASUREMENTS CONFIGURATION VIA SIB11 .................7 E-DCH active set management .........................................................4.... 202 6.........................3 6A event configuration......................... 184 5.........1 Configuration...... ALARM HANDOVER AND ALARM MEASUREMENTS ...........1.............................................5 1F event configuration ........................................................................... 192 5. 185 5.........................4 6B event configuration.....4.................................................................................... 191 DHO MANAGEMENT............... 206 6.. 191 5...................................5....... 193 6............................................. 207 6................................................................................................7...........................3......................4 Parameters .........5 Change of Measurement Type ...5...................................................1............ 183 5....................... 184 5.....................................................................................3...............1...1 Description ...........1 2D event configuration................................ 195 6......................... 185 5........................................ 202 6.............................3........................ 185 5.......................................4.................................... 204 6......... 208 6....................3....................6 Parameters for Measurement .................3..1 1D event configuration............3........1 Counters .. 207 6.................... 182 5................2 Case of intra-frequency Periodic Reporting mode...................................................................................1 SIB Update.................................................6..... 182 5...........................5................................................3..........3..............4.................................... 205 6.................4.....................1 Measurement reporting................... 201 6...........................................3 Reporting quantities...........2.................3......... 201 6......................2 Alarm measurement activation with periodic Intra Frequency measurements.............2...........................3....................1.................................................................................2 2F event configuration ..........................5........... 207 6...............................................................................3................... LIST OF COMPOUNDING CELLS FOR THE MONITORED SET DEFINITION ...... 192 5.......................... 208 Passing on or copying of this document...........................................................................................................................................2 Applicability ........................................... 204 6.................................................................4 Configuration for inter-frequency measurements .......1............. 184 5............................................2 Other Parameters .......................................................................1...........6..............5..............4......2.........................................................3......... 206 6....................................................................................................................3........................2.......9...4 Parameters ............................1........................5 Parameters for Event reporting mode............................1............................UMTS Radio Mobility 5..................1 Measurement activation parameters ........................................ 181 5..................................... 196 6..... 195 6......................... 204 6.................................................................................................. 187 5........3 Case of intra-frequency Event-Triggered Reporting mode...........6...........3 Configuration ....................6...... 5....................8........ 186 5............. MEASUREMENTS CONFIGURATION FOR INTER-FREQ/2G INTER-RAT ..........................................2 Measurement reporting................ 179 5.................................................................. MANAGEMENT OF SYSTEM INFORMATION BLOCKS (SIB)......1.............5.............................6.........4...............1 Description......................... ALARM MEASUREMENT ACTIVATION WITH EVENT BASED INTRA FREQUENCY MEASUREMENTS..........6....... 182 5..............4.............................. 179 5........................................3 Algorithm..............1.........1...........................................................2..............................4 Reported cells.........................................................................1.1 Overview ............. 182 5...3 Configuration for inter-system measurements................................................ 207 6...................... PRIMARY CELL DETERMINATION .................1...2..2 Algorithm................................................................... 208 6........1................3............2.......3..................6...........1...........2 SIB Repetition period... 204 6.....3..... INTRA-FREQUENCY MEASUREMENTS ......6 Performance management ...............................................................4..............................................

.......4...........................18.................................................................7.................. 215 6.4......................................................... 230 6....... 213 6................................ 212 6...7.....18...................................... 228 6........................ 229 6...............................................4......3........ NEIGHBOR CELLS FLEXIBLE MANAGEMENT .. 234 6.......9.........7............................................................................3 inter-RNC soft handover ..2.............4... 210 6.................................................................17 Defence mechanism for UE not supporting CM with HSPA..........................1 Introduction ..........4... 239 6... 218 6...................6........ 217 6..................4..................4 Measurement purpose......4................................................... 240 6..... 214 6..........3...............7......... 210 6............................1 Description .............4.18...........................7...............6 slot formats/ frame structure ..............7 NBAP/Radio link reconfiguration COMMIT message.......................3 Switching between Compressed Mode methods ...............................7............. 219 6..................... 234 6.............................................................7......7...............4............................1 Data flow.....4...........18.............. 231 6.....................................................................4....6 NBAP/Compressed Mode Command message ........... 237 6..........15.......... 216 6...................................................1 GSM measurements.....................................2..........................................................................2 HLS GAP PATTERN configuration............7......4.....UMTS Radio Mobility 6................. 214 6........ FDD TARGET CELL CHOICE INTER FREQUENCY RADIO CRITERIA ....3 Method ................................................ 220 6........................................2 FDD inter-frequency measurements ......7.... 232 6..4 Static parameters .......................................8 Impacts on RRM Specific for SF/2 method ..............2...........................5 Pattern shape...........4................... 239 6............................ 239 6................................5...........2 Missing Measurements........................................................9............................................................................................4.4............................7 Procedures & messages................................9 RNSAP/Compressed Mode Command message .............. 240 Passing on or copying of this document........1 General parameters.........15........4........ 234 6............................4....................5...3 RRC/RB Reconfiguration message .........................1 Code tree management ........................................................................................4.....1 Dynamic parameters...... 236 6......2 FDD inter-frequency measurements ........................4.....4..............................4...4.................4................................................................10 RNSAP/Radio link reconfiguration COMMIT message ....................4.................7............................ 214 6...... 223 6...........4...........................................................15 Impact on other procedures...............................6..........................................15.......12 DRNS scenarios .........................................................................................1 Description ............................4................................................... 2G TARGET CELL CHOICE RADIO CRITERIA .......................................1........................ 216 6........4.............................. 230 6......4.9...4............................................... 234 6.......4................................. 217 6.....................................1 HLS assumptionS ......2 Parameters ......4................................ 224 6..............................................................10 SRNS Relocation ..................18................................ 238 6................... 216 6...................4.......................................................................................................................................4 CM method selection rules: .....2 RRC/RB Setup message ..............................2 Parameters ...............5.4..................... 238 6.......................................1 GSM measurements........................................................5 control performed by the ALCATEL-LUCENT RNC .......................................4...............................4.....................................16 Change of Alarm measurement type (Common HLS and SF/2) ...........................................18............... 226 6...................................................... 209 6......2 O&M parameters ...4..........8....................18.......................................... 218 6.....................................................2 UE capability ..................11 RNS Inter-release Compatibility Use cases ......4...... 238 6...5 Filtering . 213 6..........................2 Pattern parameters....................06/EN Approved_Standard 17/Sep/2010 Page 12/244 ... 218 6....................... 230 6.....5........................................5......................14 UE impacts.4....................... 214 6........................4........4 RRC/Measurement Control message.....4..........1 intra-NodeB soft handover..........................................................4........... 217 6......4.............................................5 NBAP/Radio Link Reconfiguration Prepare message ............... 220 6......................... 235 6..............4.4.............3 Power control parameters ..4.....................................4.. 211 6................. 233 6..6...4............................................13 Alpha CEM cards impact ...................18 Parameters ..........4................................9........................9 HLS ................................. COMPRESSED MODE ..............................................................................................................................................................................................2................. 212 6..........................................2................................ use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11...............8 RNSAP/Radio Link Setup/addition Request message .............. 230 6...... 210 6........................................................... 221 6..............2 intra-RNC/inter-NodeB soft handover.................... 209 6..............4................................4....... 218 6........... 213 6...................

.........1 6.............................2...........................................2 6........... 242 DEFINITIONS ............................. 240 Parameters ......................................................................................................................................................................................................... 7...........................................3 Description ..............1.............................................................. 242 7.....................7................. 243 Passing on or copying of this document...........7.......... ABBREVIATIONS .... ABBREVIATIONS AND DEFINITIONS...................7.......................................................... use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11...................................................UMTS Radio Mobility 6..............06/EN Approved_Standard 17/Sep/2010 Page 13/244 .............. 241 7..... 240 Algorithm.........

2 of Alcatel-Lucent UTRAN.UMTS Radio Mobility 1.. compressed mode .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..) 1. INTRODUCTION OBJECT This document specifies the UMTS mobility procedures for mobiles connected to the network. Although this document is focused on UTRAN.06/EN Approved_Standard 17/Sep/2010 Page 14/244 . 1. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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.1.Cell reselection 104489 LTE to UMTS HO 81213 . SCOPE OF THIS DOCUMENT This document applies to UA07.2 features covered by this document are: • • • • 81436 Mobility between UMTS and LTE .Load balancing between HSPA carriers 81204 Dual Cell HSDPA operation Passing on or copying of this document.2. Intersystem mobility procedures (to and from GSM) are also described in this document. The new UA07. How is the document structured? Chapter3 presents definitions and concepts which will be used throughout the document. it also addresses radio mobility procedure applicable to the Core Network.

[USA Market] [Global Market .06/EN Approved_Standard 17/Sep/2010 Page 15/244 . This tagging indicates that the enclosed text following the "[Global Market .4. 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 word indicates that the word preceding the tag "[USA Market]" applies only to the USA Market. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.3.…] Text that is not identified via one of the hereabove tags is common to all markets. 2. DEFINITIONS AND SPECIFICATION PRINCIPLES The present document addresses several markets with potentially different behaviours in those markets. 1. RELATED DOCUMENTS APPLICABLE DOCUMENTS [A1] [A2] [A3] 25. 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. Except when specified. AUDIENCE FOR THIS DOCUMENT This is an external document.1." applies only to the USA Market. all performance management information (counters) are described in [R14].433 UTRAN Iu interface RANAP signalling UTRAN Iur interface RNSAP signalling UTRAN Iub interface NBAP signalling Passing on or copying of this document. This tagging indicates that the enclosed text following the "[USA Market .UMTS Radio Mobility 1. 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. 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. 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. 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. 2.…] [USA Market .423 25. The definition of “Global Market” and “USA Market” are: Global Market: customers other than those part of the following market.413 25." applies only to the Global Market. [R15] and [R16] documents.

133 23.UMTS Radio Mobility [A4] [A5] [A6] [A7] [A8] [A9] 25.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] [R15] [R16] 411-8111-822P1 411-8111-822P2 411-8111-822P3 Observation counters .06/EN Approved_Standard 17/Sep/2010 Page 16/244 . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Radio Resource Control (RRC) protocol Requirements for support of radio resource management (FDD) General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access Circuit Switched Fallback in Evolved Packet System 2.2.272 Radio Resource Control (RRC) Protocol Specification UE procedures in idle mode and procedures for cell reselection in connected mode Mobile radio interface layer 3 specification.Volume 1 (RNC base) Passing on or copying of this document.018 25.Volume 1 (RNC Callp) Observation counters .Volume 2 (BTS) Observation counters .Intelligent Rab mapping [R8] UMT/SYS/DD/18470 [R9] NN-20500-028 SRNS Relocation – UE not involved Alcatel-Lucent 9300 W-CDMA Product Family – Counter Reference Guide .401 23.331 25.304 44. 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 .

1.331. This protocol specifies radio network layer signalling procedures between RNCs in UTRAN on the Iur interface. Passing on or copying of this document.1. This protocol specifies radio network layer signalling procedures between RNC and Node B on the Iub interface. RRC is the Radio Resource Control protocol for the UE-UTRAN radio interface.423. DEFINITIONS & CONCEPTS NETWORK ARCHITECTURE The following figure briefly presents the UMTS network elements which are relevant to mobility features. GTP is the GPRS Tunnelling Protocol. 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. NBAP: specified in 25. RANAP is the Radio Access Network Application Part.413.002.060. 3. RNSAP: specified in 25. This protocol terminates in the UE and in the Serving RNC.UMTS Radio Mobility 3. RNSAP is the Radio Network Subsystem Application Part. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. NBAP is the NodeB Application Part. This protocol specifies the signalling procedures between the PS Core Network nodes. AAL2 is one of the transport layer used in UTRAN. This protocol specifies radio network layer signalling procedures between RNCs and CN on the Iu interface. MAP is the Mobile Application Part. In the Core Network: MAP: specified in 29. This protocol specifies the signalling procedures between the CS Core Network nodes. RRC: specified in 25. Packet data network External Networks GGSN HLR Gn SGSN Gn SGSN Gs MSC/VLR E MSC/VLR PSTN Core Network UTRAN RNC Iur Iub RNC Iu Node B cells Node B Node B Node B Node B Uu UE Figure 1: general architecture The protocol stacks which are used in this document are the following: In UTRAN: RANAP: specified in 25. GTP: specified in 29. and also between UTRAN and Core Network for CS applications.433.06/EN Approved_Standard 17/Sep/2010 Page 17/244 .

2. The figure below is an example of soft handover.2. 3GPP BASIC PROCEDURES This chapter intends to clarify the basic mobility procedures which are applicable to UMTS UTRAN/FDD networks. FACH. some PDU may be lost).e. the soft handover may be either: • intra-NodeB: the cells belong to the same NodeB (In case the NodeB performs recombination between radio links. irrespective of the version to which this document applies. As a matter of fact.e. i.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 • hard handover • cell reselection (UE controlled mobility) • SRNS relocation • radio link reconfiguration 3. The mobility cases specified in the following sections are all using those basic procedures. The intention is also to set some vocabulary basis that will be used throughout the document. the macro-diversity radio links belong to the same NodeB. 3.06/EN Approved_Standard 17/Sep/2010 Page 18/244 . this case is called softer handover.e.2.2. the mobile is connected to a set of cells known as the “active set” and takes benefit from macro-diversity.2 SOFTER HANDOVER In the softer handover case.g.. refer to § 3.UMTS Radio Mobility 3.. swapping from one cell to another one without call interruption by opposition to hard handover (i. SRNC SRNC DRNC Cell 1 Cell 2 Cell 1 Cell 2 Cell 2 Cell 3 UE Call establishment UE Intra RNC soft handover UE Inter RNC soft handover Figure 2: Soft handover examples Regarding network architecture. DSCH. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1 SOFT HANDOVER The soft handover is a procedure allowing the mobile to “do it before break it “ i. Soft handover cannot be applied to shared or common transport channels (e.). Passing on or copying of this document.

used at the same time for a given mobile) 3.06/EN Approved_Standard 17/Sep/2010 Page 19/244 .e. GSM) • when soft handover is not permitted (due to O&M constraint) The figure below is an example of hard handover.2. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. as an option from the network Passing on or copying of this document. soft handover is not possible) • when the UE is handed over another UTRAN carrier • when the UE is handed over another mode (e.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).g. TDD) • when the UE is handed over another technology (e. 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). Cell 1 Cell 2 Cell 1 Cell 2 UE Before UE After Figure 4: hard handover example Regarding network architecture.g.UMTS Radio Mobility NodeB Cell 1 Cell 2 UE Figure 3: softer handover example Soft and softer handover may be combined (i. 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.

06/EN Approved_Standard 17/Sep/2010 Page 20/244 . a SRNS relocation may be either intra or inter MSC or SGSN.2. the target RNC is actually a 2G-BSC) • UTRAN radio mobility in case Iur is not present. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.e. In particular. TDD) • another system (e.2. there is no RRC connection between the UE and the network). the mobile may select a cell from • another frequency • another mode (e.g. 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 Passing on or copying of this document. 3.e. Besides. Depending on the network topology. when the mobile is connected to the network (i. 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). from RNC1 to RNC2: Before HLR SGSN After HLR SGSN SGSN MSC MSC SGSN MSC MSC RRC RLC MAC RRC RNC1 RNC2 RNC1 RNC2 RLC MAC Figure 5: SRNS relocation example SRNS relocation may be used in many cases: • incoming intersystem handover (in this case. 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. 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.UMTS Radio Mobility 3. a RRC connection is present). LTE) Regarding network architecture.g. The figure below is an example of SRNS relocation. GSM.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). the source RNC is actually a 2G-BSC) • outgoing intersystem handover (in this case.4 CELL RESELECTION Cell reselection algorithms are applied by any mobiles in Idle mode (i.

2. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. there may or may not be a change of the physical channels being used for the communication. In any case. Passing on or copying of this document.UMTS Radio Mobility Depending on the case for which the relocation is used.06/EN Approved_Standard 17/Sep/2010 Page 21/244 . the SRNS relocation implies: • a u-RNTI (UTRAN Radio Network Temporary Identity) re-allocation • a reset of the radio protocol layers 3.6 RADIO LINK RECONFIGURATION Refer to [R1] for details.

17 4.16 4. For all data flows in this chapter.UMTS Radio Mobility 4. SRNS UE involved) Intra-frequency Inter-RNC Handover without Iur (i.0.21 4. Iub/Iur is on ATM so ALCAP is used to allocate Cid.18.5 4.10 4. SRNS UE involved) Hard handover inter-frequency.3 4.12 4.0 UA03.0 UA03.3 4. MOBILITY CASES This chapter describes all the mobility cases applicable for the current version of the document.e.11 4. inter-RNC Inter-frequency Inter-RNC Handover without Iur (i.10 4.14 4.7 4.21 4.4 4.23 4.5 4.2 4. intra-RNC Soft Handover.1 4. Service or CAC failure reason (refer to 4.7 4. The complete list of cases is summarized in the table below: Section 4.4 4. Feature title PMId UTRAN release AT&T Global Market UA06.2 Section 2G to 3G for CS domain IMSI based HO 13448 21091 4.8 4. Inter Frequency Hard Handover or Inter System Hard Handover are triggered by the iMCTA function for Alarm.2 UA06.2 Passing on or copying of this document.15 4.5 Softer Handover Soft Handover. If Iub/Iur is on IP there is no seperate ALCAP-like message to allocate/release IP transport resources (IP address and UDP ports).4 4. intra-RNC Inter-Frequency Inter-RNC Handover with Iur and measurements HSDPA and HSUPA mobility SRNS Relocation (“Ue not involved”) 3G2G Redirection at RRC establishment for speech call Emergency and Priority Calls iMCTA Mobility in Cell_PCH and URA_PCH states HCS 3G to 2G handover for PS domain in blind mode 3G to 2G handover for PS domain with measurements 3G to 2G handover for CS domain in blind mode 3G to 2G handover for CS domain with measurements 2G to 3G handover for CS domain 2G to 3G handover for PS domain 2G to 3G handover for CS + PS domain 3G to 2G handover for both PS and CS domains 4G to 3G relocation 3G to 2G cell reselection in Idle mode 3G to E-UTRAN cell reselection in Idle mode 3G to 3G cell reselection inter-frequency in Idle mode 3G to 3G cell reselection intra-frequency in Idle mode 3G to 2G cell reselection in CELL_FACH mode 3G to 3G cell reselection inter-frequency in CELL_FACH mode 3G to 3G cell reselection intra-frequency in CELL_FACH mode Table 1:list of mobility cases Since UA05.20 4.06/EN Approved_Standard 17/Sep/2010 Page 22/244 . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.13 4.4 4.6 4.6 5.20 section).7 4.e.18 4. The following table lists the PMId of the mobility features with the release introduction.

0 UA05.1 UA07.2 UA04.3 4.0 UA06.0 UA05.10 4.0 UA07.18.0 UA06.4 4.2 UA04.21 4.0 NA UA07.18 4.0 UA05.0 NA UA06.7 6.2 UA04.0 UA06.0 UA06.6 5.23 4.21 4.7 4.0 NA UA06.20 4.0 UA06.0 UA06.4 Passing on or copying of this document.0 UA06.0 UA06.0 UA05.0 UA07.0 UA07.9 6.18.1 UA06.21 4.3 6.21 5. R4.16 6.1 UA07. R2.0 UA05.2 UA04.18.0 UA07.0 UA06.0 UA06.0 UA06.20 4.1.0 UA07.20 4.21 4.21 4.2 4.0 UA06.9 4.0 UA07.0 UA06.0 UA06.3 5.7 6.2 UA05.0 NA UA07.0 UA07.0 UA07.0 UA06.6 5.0 UA06.21 4.18.2 33331 34480 UA06.18 4.4 6.0 UA05.2 NA NA UA06.0 UA06.0 UA06. R10) iMCTA load based HO developments (R5) Alarm HHO based on UE Tx power 3G/2G RRC redirection based on cell load 17569 21319 25145 21135 25757 21296 19794 32580 13451 27932 27219 27597 27937 27936 21302 29415 29802 23840 18880 (34476) 30675 29817 29816 26673 26675 32076 33819 33820 81436 30744 33814 28035 34151 33546 33665 32601 (78332) 34291 (78327) 34231 (78326) 34230 (78331) 34229 (78487) 34224 (78333) 34167 33693 34274 33326 75069 34437 34437.21 4.1 UA06.18.0 UA07.0 UA06.0 UA06.14 4.1.0 UA06.2 UA03.0 UA06.0 UA05.1 UA04.0 UA06.11 4.0 UA05.20 5.20 4.0 UA06.0 UA06.7 5. R11) iMCTA load based HO developments (R1.6 4.UMTS Radio Mobility Inter Frequency inter RNC without Iur 3G to 2G HO for PS & CS simultaneously 3G2G Redirection for emergency call Event-Triggered measurements Fast Alarm handover triggering Composite Neighbour List Inter frequency intra RNC handover based on CM 3G/2G Redirection enhancement for 911 calls 3G/2G Redirection for speech call HSDPA step 1 (see note 1) Intra-frequency Event-triggered Measurements Coexistence of Inter-frequency and 2G Inter-Rat measurements HSDPA Alarm mobility HSDPA Intra-frequency mobility Intra-frequency Hard Handover in case of no Iur Intelligent Multi Carrier Traffic Allocation HSDPA HO with measurements E-DCH step 1 SRNS Relocation “UE not involved” Dynamic SIB scheduling HSDPA over Iur Hierarchical Cell Structure (HCS) URA_PCH CELL_PCH E-DCH macro diversity support Broadcast of SIB4 Broadcast of SIB12 Broadcast of SIB19 HSUPA over Iur Intra frequency inter RNC without Iur Compressed Mode by Higher Layer Scheduling (HLS) Immediate handover for emergency call Service Based Mobility parameters enhancement Multi layer developments iMCTA enhancements for WPS Support of 64 UMTS neighbours Soft Handover developments 2G Inter-RAT handover developments Inter-Frequency Handover developments Inter-Frequency/2G Inter-RAT measurements evolution Defence mechanisms for UE not supporting CM with HSPA Compounding Neighbour Cell List developments intra-frequency Compounding Neighbour Cell List developments IFREQ/IRAT Unified RRM step 2 cell load information exchange between 2G and 3G Redirection during RRC connection setup iMCTA load based HO developments (R3.2 UA04.1 34437.1 UA04.0 UA06.2 6.0 UA06.0 UA06.0 UA06.3 4.2 UA04.1 UA07.0 UA06.3 4.0 UA06.0 UA06.0 UA07.0 UA06.0 UA06.0 UA07.0 NA UA06.3 6.3 5.1 UA07.0 UA06.0 UA06.6 4.18.2 UA04.0 UA06.06/EN Approved_Standard 17/Sep/2010 Page 23/244 . R9.4 4.21 5.2 UA04.3 5.0 UA06.17 5.2 UA06.1 UA03.0 UA06.2 UA04.21 4.14 6.0 UA06.14 4.0 UA06.1 UA07.2 UA03.3 4.1 UA07.1 4.0 UA04. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.0 UA07.

Radio link recombination is performed at the SRNC level. the RNC in charge of the RRC connection with the mobile).1.1. there is already a macro-diversity link supported by the Serving RNC (NodeB1). Iu SRNC Iub NodeB 1 NodeB 2 New radio link to be added UE Figure 6: soft handover overview In this case. (2) once new resources are created.e. the links which are added/withdrawn from the active set are all managed by the SRNC (i.2 UA07.2 UA07. and the associated AAL2 Cid(s) to be allocated. For further details on this process. 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1.1.2 UA07.1. a new branch is added using the NodeB 2.1.1.19 For features introduced in only one type of market in a release.12 4.2 UA07. A new link from NodeB2 is added: UE NodeB 2 RRC/ Measurement Report NBAP/ Radio Link setup req NBAP/ Radio Link setup resp FP/ DL Sync (CFN) FP/ UL Sync (ToA) RRC/ active set update RRC/ active set update complete Serving RNC 1 2 Figure 7: Radio Link addition (1) based on active set evaluation process result.2 UA07.1.2 UA07.1.UMTS Radio Mobility 3G to LTE cell reselection in Idle mode 3G to LTE cell reselection in Cell/URA PCH mode 4G to 3G relocation Load balancing between HSPA carriers Dual Cell HSDPA operation 81436 81436 104489 81213 81204 UA07. 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). the mobile active set is updated with the new radio link Passing on or copying of this document.1 SOFT HANDOVER INTRA RNC DESCRIPTION In this case.06/EN Approved_Standard 17/Sep/2010 Page 24/244 .1.1. 4.2 UA07.2 UA07.5 4.1.18 4.2 UA07. Note 1: HSDPA step 1 feature contains HSDPA SHO mobility and traffic segmentation functions. This implies a new radio link to be setup with the NodeB 2. the feature Id of the globalization/above parity feature is given into ( ).4 4. please refer to the "DHO management" section in the Common procedures chapter.2 4.

and the AAL2 Cid(s) are released. The mobile active set is updated with the new configuration. In this version.3 PARAMETERS Refer to the [Active Set Evaluation] section in the [Common Procedures] chapter. For more details. Therefore. UE NodeB Serving RNC RRC/ Measurement Report (event 1B) RRC/ active set update RRC/ active set update complete 1 NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp 2 Figure 8: Radio Link deletion (1) based on active set evaluation process result. 4.e. the SRNC decides to remove a radio link from the active set.1.UMTS Radio Mobility The next dataflow is an example of radio link removal. Besides.2 APPLICABILITY The soft handover applies only on dedicated physical resources. If the Active Set Update procedure fails.5 CORE NETWORK IMPACTS None. please refer to the [Active Set Evaluation] section in the Common Procedures chapter. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Passing on or copying of this document. the active set evaluation (i. the call is kept with the previous active set cells.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. For details on the active set evaluation process. Decision to add/drop links) is based on the same algorithm and parameters (with possibly different values) for PS and CS calls.1.06/EN Approved_Standard 17/Sep/2010 Page 25/244 .1. please refer to the [Active Set Evaluation] section in the Common Procedures chapter 4. (2) the link is deleted at the NodeB. 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. it is possible to limit the number of soft handover legs being used by setting the relevant parameter to the needed value. (CN is completely transparent to this procedure). 4.

Iu SRNC Iur DRNC Iub NodeB 0 NodeB 1 NodeB 2 New radio link to be added UE Figure 9: soft handover over Iur In this case.06/EN Approved_Standard 17/Sep/2010 Page 26/244 .g. please refer to the "DHO management" section in the Common procedures chapter.UMTS Radio Mobility 4. A new link from NodeB2 is added: Passing on or copying of this document. For further details on the Radio link recombination process. there is already a macro-diversity link supported by the NodeB0 (controlled by the SRNC) and the NodeB1 (controlled by the Drift RNC). in this version there are as many dedicated links on the Iur as radio links which are controlled by the DRNC). the links which are added/withdrawn from the active set are not all controlled by the SRNC. 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.2. This DRNC acts as a router from the RNC and the UTRAN transport point of view (e.1 • • SOFT HANDOVER INTER RNC DESCRIPTION In this case.2. 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. 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.

the associated AAL2 Cid(s) are allocated on the Iub and Iur. a new branch is added using the NodeB2. 2 separate Cid are used on the Iur for both DCCH and DTCH. the mobile active set is updated with the new radio link The next dataflow is an example of radio link removal. A new radio link is setup with the NodeB 2. This information is used by the SRNC to update the list of cells to be measured by the UE. Passing on or copying of this document. Since there is already a macro-diversity link controlled by the DRNC for that communication. the Drift RNC provides to the SRNC the list of neighbouring cells.UMTS Radio Mobility UE Drift NodeB2 RRC/ Measurement Report Drift RNC Serving RNC RNSAP/ Radio Link addition req NBAP/ Radio Link setup req NBAP/ Radio Link setup resp RNSAP/ Radio Link addition resp (Binding Id) New AAL2 connections are setup for both the DCCH and the DTCH AAL2/ ERQ AAL2/ ECF AAL2/ ERQ AAL2/ ECF 1 FP/ DL Sync (CFN) FP/ DL Sync (CFN) FP/ UL Sync (ToA) FP/ UL Sync (ToA) RRC/ active set update RRC/ active set update complete 2 Figure 10: Radio Link addition over Iur (1) Based on active set evaluation result. In the RADIO LINK ADDITION RESPONSE message. 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 27/244 . • 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. (2) Once new resources are created. On the Iur.

The SCCP released message is sent if the radio link which is removed is the last one supported by the DRNC for this mobile. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.2. (CN is completely transparent to this procedure). Passing on or copying of this document.5 CORE NETWORK IMPACTS None.2. For other applicability considerations.06/EN Approved_Standard 17/Sep/2010 Page 28/244 .4 ACCESS NETWORK IMPACTS All impacts which come from the "soft handover intra RNC". For details on the active set evaluation process. (2) the link is deleted at the NodeB. plus: • support of dedicated channel on Iur and associated RNSAP procedures. 4.2.3 PARAMETERS Refer to the [Active Set Evaluation] section in the [Common Procedures] chapter. the SRNC decides to remove a radio link from the active set. 4. the Iub AAL2 Cid the 2 Iur AAL2 Cid are released. please refer to [Soft Handover intra-RNC].UMTS Radio Mobility UE Drift NodeB RRC/ Measurement Report RRC/ active set update RRC/ active set update complete 1 Drift RNC Serving RNC RNSAP/ Radio Link deletion req NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp RNSAP/ Radio Link deletion resp AAL2/ REL AAL2/ RLC AAL2/ REL AAL2/ RLC SCCP/ Released SCCP/ Release Complete 2 Figure 11: Radio Link deletion over Iur (1) based on active set evaluation result. 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. 4. The mobile active set is updated with the new configuration.

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. a new branch is added using the NodeB. without cluster limitation. please refer to the [DHO management] section in the Common procedures chapter.e. the links which are added/withdrawn from the active set are all controlled by a NodeB already supporting a radio link towards the mobile. There is no new AAL2 Cid to be allocated since the recombination between the 2 radio links is performed at the NodeB. A new UA06.UMTS Radio Mobility 4. (2) once new resources are created.3.3.2 APPLICABILITY Please refer to § 4.06/EN Approved_Standard 17/Sep/2010 Page 29/244 . 4.1 Passing on or copying of this document. When the Radio Link Addition Response is sent. as in the following figure: Iu SRNC Iub NodeB New radio link to be added UE Figure 12: softer handover overview The corresponding dataflow is as follows: UE NodeB RRC/ Measurement Report NBAP/ Radio Link Addition req NBAP/ Radio Link Addition resp 1 Serving RNC RRC/ active set update 2 RRC/ active set update complete Figure 13: Radio Link addition for softer handover (1) based on active set evaluation result. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. the NodeB start UL reception and DL transmission on the new radio link. please refer to [Active Set Evaluation] section in the Common procedures chapter For further details on the Radio link recombination process. 4.1 SOFTER HANDOVER DESCRIPTION In this case. the mobile active set is updated with the new radio link For further details on the active set evaluation process. i.3.

4.23. 4. present chapter describes behaviour when HCS is not used) • High mobility detection is supported 4.3 ALGORITHM As specified in 25. 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. 4.304. 4.5 CORE NETWORK IMPACTS None.1 CELL RESELECTION IN “IDLE MODE” 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". use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.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.3. Name is6SectorsNodeb Object/Class RadioAccessService Class3 Definition Flag for 6 sectors softer HO feature activation 4. 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 Passing on or copying of this document.4 • ACCESS NETWORK IMPACTS Support of relevant Iub procedures 4. (CN is completely transparent to this procedure).4. • “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.3.06/EN Approved_Standard 17/Sep/2010 Page 30/244 . 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.3. • only UTRAN/FDD.4. i.UMTS Radio Mobility 4.4.e.3 PARAMETERS Refer to the [Active Set Evaluation] section in the [Common Procedures] chapter.

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 USING 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:
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 31/244

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 interRAT 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 Srxlev Qqualmeas Qrxlevmeas Qqualmin Qrxlevmin Pcompensation UE_TXPWR_MAX_RACH P_MAX Cell Selection quality value (dB) Cell Selection RX level value (dB) Measured cell quality value. The quality of the received signal expressed in CPICH Ec/N0 (dB) Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells (dBm) Minimum required quality level in the cell (dB) Minimum required RX level in the cell (dBm) max(UE_TXPWR_MAX_RACH – P_MAX, 0) (dB) Maximum TX power level an UE may use when accessing the cell on RACH (read in system information) (dBm) 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.

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 32/244

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. 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. 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. 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. 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.

Qoffset1

Qoffset2 Qhyst1 Qhyst2

4.4.3.5

CELL RANKING CRITERIA WHEN USING ABSOLUTE PRIORITY

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
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 33/244

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 highmobility.

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.
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 34/244

4.1).. 4..1 AT UTRAN/FDD CELL LEVEL SIB 3&11 3 3 3 3 3 Object CellSelectionInfo CellSelectionInfo CellSelectionInfo CellSelectionInfo CellSelectionInfo CellSelectionInfo description/comment Choice of measurement (CPICH Ec/No or CPICH RSCP) to use as quality measure for Fdd cell.4..FACH apply for Treselection and are scaled according to the UE mobility state and target RAT 4.-13 by step of 2) Integer (0. Integer (-32. Real (0.4.. • SIB11 for cell reselection parameters related to neighbouring cells.PCH or Treselections. 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. Real (1.. All those parameters are broadcast on the BCCH using either • SIB3 for cell reselection parameters related to the serving cell.75 by step of 0. This threshold is used in the measurement rules for cell re-selection. This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections.31) In [s] From -50 to 33 In [dBm] Integer (-105. it specifies the RAT specific threshold in the serving cell used in the inter-RAT measurement rules. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.PCH or Treselections.75 by step of 0..UMTS Radio Mobility In all the above criteria the values of Treselections.4.2 Integer (-58.40 by step of 2) In [dB] Integer (0. Integer (-105. Treselections. When HCS is used. it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-frequency neighbouring cells of the serving cell. This threshold is used in the measurement rules for cell re-selection. Real (1......91 by step of 2). it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-RAT neighbouring cells of the serving cell. This specifies the scaling (multiplication) factor to be used by the UE for scaling the Information Element qualMeas sIntraSearch sSearchRatGsm sInterSearch qQualMin qRxLevMin qHyst1 qHyst2 tReselection sibMaxAllowedUlTxPower OnRach sSearchHcs 3 3 3 3 3 CellSelectionInfo CellSelectionInfo CellSelectionInfo PowerConfClass CellSelectionInfo sHcsRatGsm 3 CellSelectionInfo speedDependScalingFacto rTReselection 3 CellSelectionInfo interFreqScalingFactorTRe selection 3 CellSelectionInfo interRatScalingFactorTRes election 3 CellSelectionInfo Passing on or copying of this document.4 PARAMETERS This paragraph lists all the parameters needed when HCS is not used and displayed to the operator at the OMCR.40 by step of 2) In [dB] Integer (0. In [dB] Integer (-115.25).25).1 by step of 0.-25 by step of 2) RSCP..20 by step of 2) In [dB] Integer (-24.06/EN Approved_Standard 17/Sep/2010 Page 35/244 ..0) Ec/N0.20 by step of 2) In [dB] Integer (-32.4.FACH for the inter-frequency case. In [dBm] As of UA04. When HCS is not 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.. When HCS is used.20 by step of 2) In [dB] Integer (-32.91 by step of 2). • SIB19 for LTE cell reselection.

Integer (1. 30.. 40. 180. 240). 10. Enumerated (not used. This parameter is mapped to non-TCRmax or TCRmax IE for SIB3 filling depending of HCS use or not. 30. This parameter is mapped to non-TCrmaxHyst or TCrmaxHyst IE for SIB3 filling depending of HCS use or not.PCH or Treselections. 50. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 60. tCrMax 3 CellSelectionInfo nCR 3 CellSelectionInfo tCrMaxHyst 3 CellSelectionInfo Passing on or copying of this document. 20.06/EN Approved_Standard 17/Sep/2010 Page 36/244 . This specifies the additional time period before the UE can exit high-mobility.FACH for the inter-RAT case. This specifies the duration for evaluating allowed amount of cell reselection(s).UMTS Radio Mobility parameters Treselections or Treselections. 60. This parameter is mapped to non-NCR or NCR IE for SIB3 filling depending of HCS use or not. 120. Enumerated (not used. This specifies the maximum number of cell reselections. 70).16).

‘TRUE’ means that the UE may detect the presence of a E-UTRA cell and report to NAS 19 FDDCell in UA7.2: First instance FddCell.65535). Srxlev of the UTRA cell used for neighboring measurement triggering 19 FDDCell in UA7.reserved5 (byte3) bit 0-5 19 FDDCell in UA7.1.1.2: First instance FddCell.1.100).1. Srxlev of the UTRA cell used for neighboring measurement triggering 19 FDDCell in UA7. Priority of a E-UTRA frequency 19 FDDCell in UA7.15..2 CellSelectionInfoWit hPriority in UA8 Integer (0.1.2 EUtranFrequencyA ndPriorityInfoList in UA8 Integer (-140.reserved5 (byte0 and 1) Second instance FddCell.50.reserved4(byte2) bit 0-5 utranThreshSLow UA07.7) by step of 1.reserved6 (byte2) bit 0-2 eUtraTargetFrequencyPrior ity UA07.2: FddCell. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11..1.1.reserved5 (byte2) bit 6 Second instance FddCell.1.2: FddCell.2 EUtranFrequencyA ndPriorityInfoList in UA8 Enumerated (6.62) by step of 2.2 EUtranFrequencyA ndPriorityInfoList in UA8 Integer (0. Passing on or copying of this document.06/EN Approved_Standard 17/Sep/2010 Page 37/244 .7).reserved4(byte0) bit 0-2 utraSPrioritySearch1 UA07.2 CellSelectionInfoWit hPriority in UA8 Integer (0.1.25.-44) by step of 2.75. E-UTRA frequencies to be used in cell reselection procedure 19 FDDCell in UA7..1.62) by step of 2.2: First instance FddCell.reserved5 (byte2) bit 0-2 Second instance FddCell.2: First instance FddCell.2 CellSelectionInfoWit hPriority in UA8 Integer (0.1.1.2: FddCell.reserved5 (byte2) bit 3-5 Second instance FddCell.2 EUtranFrequencyA ndPriorityInfoList in UA8 Byte (0.2 CellSelectionInfoWit hPriority in UA8 Integer (0. Measurement bandwidth information used by SIB19 and common for all neighbouring cells on the carrier frequency 19 FDDCell in UA7.reserved6 (byte0 and 1) measurementBandwidth UA07.reserved4(byte3) bit 0-5 eUtraTargetDlCarrierFrequ encyArfcn UA07.2 EUtranFrequencyA ndPriorityInfoList in UA8 Boolean..UMTS Radio Mobility utraServingCellPriority UA07.1.1.7). Absolute priority of the serving Fdd cell 19 FDDCell in UA7.1.reserved6 (byte2) bit 6 eUtraTargetFrequencyQrx LevMin UA07... Qrxlevmin (RSRQ) of the E-UTRA cell used for S criteria of the reselection process.1..2: FddCell.1.1.reserved6 (byte2) bit 3-5 eUtraTargetFrequencyDete ction UA07.2: First instance FddCell.reserved4(byte1) bit 0-5 utraSPrioritySearch2 UA07. RSCP threshold Low of the UTRA cell used by the UE reselection process 19 FDDCell in UA7.

reserved7 (byte3) bit 0-5 19 19 FDDCell in UA7.reserved7 (byte1) bit 0-5 Second instance FddCell.reserved7 (byte0) bit 0-5 Second instance FddCell.reserved6 (byte3) bit 0-5 eUtraTargetFrequencyThre shxLow UA07.2 AT UTRAN/FDD NEIGHBOURING CELL LEVEL SIB 11 11 11 11 11 11 11 11 11 Object UmtsNeighbouringRelation FDDCell (neighbouring) FDDCell (neighbouring) FDDCell (neighbouring) UmtsNeighbouringRelation UmtsNeighbouringRelation UmtsNeighbouringRelation UmtsNeighbouringRelation UmtsNeighbouringRelation description/comment From -50 to 33 In [dBm] Integer(0.62) by step of 2.2 EUtranFrequencyA ndPriorityInfoList in UA8 Integer (0.1.10) In [dB] Integer(-50.511) This parameters equals ( 5 * FreqDL MHz ) This parameters equals ( 5 * FreqDL MHz ) Integer(-10...2: First instance FddCell.reserved7 (byte2) bit 0-5 eUtraTargetFrequencyThre shxHigh UA07....06/EN Approved_Standard 17/Sep/2010 Page 38/244 .50) In [dB] Integer(-50. In [dB] Integer (-115.0) Ec/N0.1..2: First instance FddCell.4.-25 by step of 2) RSCP..UMTS Radio Mobility Second instance FddCell.62) by step of 2. RxLev (RSRP) Threshold High of the E-UTRA cell used by the UE reselection process 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. In [dBm] Information Element maxAllowedUlTxPower primaryScramblingCode ulFrequencyNumber dlFrequencyNumber neighbouringCellOffset qOffset1sn qOffset2sn qQualMin qRxLevMin Passing on or copying of this document.4..2 EUtranFrequencyA ndPriorityInfoList in UA8 Integer (0. RxLev (RSRP) Threshold Low of the E-UTRA cell used by the UE reselection process FDDCell in UA7.50) In [dB] Integer (-24.1.1.

CELL RESELECTION IN “CELL FACH AND CELL/URA PCH MODE” DESCRIPTION 4.3 AT GSM NEIGHBOURING CELL LEVEL SIB 11 11 11 11 11 11 11 11 Object GSMCell GSMCell GSMCell GSMCell GSMCell GSMCell GsmNeighbouring Cell GsmNeighbouring Cell description/comment From -50 to 33 In [dBm] bit string(3) Network Color Code.1023) GSM ARFCN Integer(-10. 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.UMTS Radio Mobility 4. present chapter describes behaviour when HCS is not used) 4. CELL PCH or URA PCH mode.5.. Part of the BSIC bit string(3) Base Station Color Code. 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 39/244 ..23. 4.50) In [dB] Integer (-115. 4.6 • CORE NETWORK IMPACTS Support of location registration update from a 3G to a 2G cell. PCS 1900 band used Integer (0. Passing on or copying of this document.5 • ACCESS NETWORK IMPACTS Ability to broadcast the necessary parameters on the radio interface BCCH.4. the UE is reselecting a new cell being also controlled by the SRNC.4. 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.. as in the figure below (please note that the old and the new cells may also be controlled by the same NodeB).-25 by step of 2) In [dBm] Information Element maxAllowedUlTxPower Ncc Bcc GSMbandIndicator bcchFrequency gsmCellIndivOffset qOffset1sn qRxLevMin 4.10) In [dB] Integer(-50.5.5.4. Part of the BSIC DCS 1800 band used.1 When in CELL_FACH..1.4. for a PS or CS attached mobile.1 INTRA-RNC CASE In this case.

a UTRAN MOBILITY INFORMATION CONFIRM message is then answered by the mobile. CN Information (PLMN Id. UE NodeB 1.5. the CELL UPDATE CONFIRM will always contain a new-CRNTI. As in the figure below. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 4. LAI. In Alcatel-Lucent implementation.UMTS Radio Mobility Iu SRNC Iub NodeB 1 NodeB 2 FACH 1 FACH 2 UE Before UE After 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. c-RNTI) RRC/ RACH / UTRAN Mobility Information Confirm Serving RNC SGSN If the mobile enters a new Location Area or Routing Area: GMM/ RACH / Routing Area Update Request GMM/ RACH / Routing Area Update Accept Figure 15: Intra-RNC cell re-selection in CELL_FACH dataflow Having re-selected the new cell.06/EN Approved_Standard 17/Sep/2010 Page 40/244 . this RNC may possibly depend from another SGSN. the UE generates a CELL UPDATE to the SRNC.1. 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". RAI). so that the SRNC keeps the current cell updated for paging. 2 RRC/ RACH / Cell Update (cause "cell reselection") RRC/ FACH / Cell Update Confirm (RRC state = CELL_FACH. the UE is reselecting a new cell being controlled by an RNC different from the SRNC.2 INTER-RNC CASE In this case. Passing on or copying of this document.

RRC/ RACH / Cell Update (U-RNTI. 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 UE Alcatel-Lucent Serving RNC1 Alcatel-Lucent Drift RNC2 SGSN 1 SGSN 2 Based on the u-RNTI analysis.06/EN Approved_Standard 17/Sep/2010 Page 41/244 . first steps when the Drift RNC2 is Alcatel-Lucent Passing on or copying of this document. cause “cell reselection”) RRC/ FACH / RRC Connection Release (U-RNTI. cause “DSCR”) Figure 17: Initial RRC access. In this version. forcing the mobile to Idle mode. the new RNC (RNC2) detects that the UE is actually connected to another SRNC. UTRAN does not support common channel over Iur. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.UMTS Radio Mobility GGSN SGSN 1 Iur RNC 1 Iub NodeB 1 Iub SGSN 2 RNC 2 NodeB 2 FACH 1 FACH 2 UE Before After UE 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. The RNC2 rejects the cell update using the RRC connection release procedure.

first steps when the Drift RNC2 is not Alcatel-Lucent UE RNC 1 RNC 2 SGSN 1 SGSN 2 When it enters Idle mode. PS domain) SCCP/ Connection Request (Initial UE msg (Routing Area Update Request)) SCCP/ Connection Confirm Figure 19: Initial RRC access Passing on or copying of this document.06/EN Approved_Standard 17/Sep/2010 Page 42/244 . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Follow-on request pending. This procedure is in response to the received Uplink Signalling Transfer procedure. cause “directed signaling connection re-establishment”) RRC/ FACH / RRC Connection Release (U-RNTI. U-RNTI. the UE requests for a RAU. cause “U-RNTI. forcing the mobile to idle mode. RNSAP/ DOWNLINK SIGNALLING TRANSFER REQUEST / RRC Connection Release (U-RNTI. cause “cell reselection”) RRC message received from UE containing U-RNTI ID as addressing information.UMTS Radio Mobility Alcatel-Lucent Serving RNC1 NonAlcatel-Lucent Drift RNC2 UE SGSN 1 SGSN 2 RRC/ RACH / Cell Update (U-RNTI. cause “directed signaling connection re-establishment”) Figure 18: Initial RRC access. 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. 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. The procedure is used by the drift RNC2 to forward to the Serving RNC1 the RRC Cell Update message received on the RACH. RRC state = CELL_FACH) RRC/ RACH / RRC Connection Setup Complete RRC/ RACH / Initial Direct Transfer (Routing Area Update Request. RNSAP/ UPLINK SIGNALLING TRANSFER INDICATION / Cell Update is forwarded to the SRNC The SRNC received the cell update and starts an RRC connection release procedure. RRC/ RACH / RRC Connection Request (cause « re-establishment ») RRC/ FACH / RRC Connection Setup (DCCH.

the mobile is possibly moved to the CELL_FACH state.06/EN Approved_Standard 17/Sep/2010 Page 43/244 . based on Always-On algorithm and user traffic volume. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. the new RAB is setup in CELL_FACH state. the mobile in PS active mode will reselect a GSM cell • the mobile will perform a RA update in its new GSM cell Passing on or copying of this document. Further on. RANAP/ RAB Assignment Request In the target RNC. In this example. RANAP/ Iu release command RANAP/ Iu release complete GMM/ Routing Area Update Accept (P_TMSI) GMM/ Routing Area Update Complete Figure 20: The Routing Area Update phase UE RNC 1 RNC 2 SGSN 1 SGSN 2 GMM/ Service Request (Data) The SGSN requests the UTRAN for RAB allocation. and security procedures are activated by the new SGSN.UMTS Radio Mobility UE RNC 1 RNC 2 SGSN 1 SGSN 2 The active PDP context(s) are retrieved from the old to the new SGSN. the GGSN and the HLR are updated with the new UE status and location The connection with the old RNC is eventually released once the RAU procedure is completed in the new SGSN. as for a PS call establishment.1.5. UEAy) RRC/ Security Mode Command RRC/ Security Mode Complete RANAP/ Security Mode Complete Once security is in place. corresponding to the active PDP context being re-activated by the UE.3 3G TO 2G CASE This mobility case is similar to the inter-RNC mobility case: • at some point. the new RAB is setup in CELL_FACH state. RRC/ FACH / RB Setup (DTCH. GTP/ SGSN ctx request RANAP/ SRNS ctx request RANAP/ SRNS ctx response GTP/ SGSN ctx response GTP/ SGSN ctx ack GMM/ Authentication and Ciphering Request GMM/ Authentication and Ciphering Response RANAP/ Security Mode Command (UIAx. RRC state) RRC/ RACH / RB Setup Complete RANAP/ RAB Assignment Response GMM/ Service Accept Figure 21: The service re-establishment phase 4.

it would be preferable for DC capable UEs to camp on DC capable layers. indicates that the SIB4 feature is activated. If a DC UE attempts call establishment on a cell that is not DC capable.1. CELL-PCH and URA-PCH).06/EN Approved_Standard 17/Sep/2010 Page 44/244 .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. 4. In the current release neither iMCRA nor iMCTA ensure redirection or handover to a DC capable cell. 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 FDDCell Class3 SIB4enable Definition When set to TRUE.5. 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). 3GPP has not defined any mechanisms to force cell reselection based on DC capability.5.6 DUAL CELL HSDPA CASE In multi-layer networks with some layers supporting DC transmission and others not. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Unfortunately.5. 4. 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.4 2G TO 3G CASE From the UTRAN point of view.5 3G TO E-UTRAN CASE This mobility case is similar to the inter-RNC mobility case: • at some point.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.1.5. Therefore.3 ALGORITHM Please refer to [Cell Reselection In Idle Mode]. 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. no specific cell reselection handling or specific SI broadcast is available for DC feature.1.5. Passing on or copying of this document.5. 4. 4.4 PARAMETERS In connected mode (CELL-FACH. In this case.

In [dB] Integer (-115. For qHyst1.2 Integer (-58.40 by step of 2) Information Element qualMeas sIntraSearch 4 sSearchRatGsm sInterSearch qQualMin qRxLevMin 4 4 4 4 qHyst1 qHyst1Fach qHyst1PCH qHyst2 qHyst2Fach qHyst2Pch 4 4 4 4 4 4 Passing on or copying of this document.5.20 by step of 2) In [dB] Integer (-32. In this case.0) Ec/N0. qHyst2 and tReselection it is furthermore possible to configure them differently on FACH and PCH.40 by step of 2) In [dB] Integer (0. In [dBm] As of UA04. YES: SIB12 is sent NO: SIB12 is not sent When set to TRUE. SIB12 and SIB19.... Integer (-32. If SIB4/SIB12 are not broadcasted...40 by step of 2) In [dB] Integer (0. In this case. It has to be set to true in order to broadcast SIB4.20 by step of 2) In [dB] Integer (-32..20 by step of 2) In [dB] Integer (-24.1 AT UTRAN/FDD CELL LEVEL SIB 4&12 Object CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC description/comment Choice of measurement (CPICH Ec/No or CPICH RSCP) to use as quality measure for Fdd cell.. parameters of SIB3/SIB11 are used instead. indicates that the SIB19 feature is activated.40 by step of 2) In [dB] Integer (0. the parameter isDynamicSibAlgoWithSbAllowed has to be set to true. YES: SIB19 is sent NO: SIB19 is not sent This parameter activates/deactivates the use of SB block in the dynamic SIB scheduling algorithm used to broadcast SIB on the Air interface. SIB12enable FDDCell Class3 SIB19enable FDDCell Class3 isDynamicSibAlgoWithSBAllowed RadioAccessService Class3 The list of parameters for SIB4/12 is the same as for SIB3/11 but they are described in dedicated objects....-25 by step of 2) RSCP. the parameter isDynamicSibAlgoWithSbAllowed has to be set to true.40 by step of 2) In [dB] Integer (0..-13 by step of 2) Integer (0.4. indicates that the SIB12 feature is activated. YES: SIB4 is sent NO: SIB4 is not sent When set to TRUE. 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 45/244 . 4..UMTS Radio Mobility the parameter isDynamicSibAlgoWithSbAllowed has to be set to true.40 by step of 2) In [dB] Integer (0.

31) In [s] Integer (0.25). 60..4. 30. This threshold is used in the measurement rules for cell re-selection. 20. Real (1. Real (1.1). tReselection tReselectionFach tReselectionPch sibMaxAllowedUlTxPower OnRach sSearchHcs 4 4 4 4 4 sHcsRatGsm 4 CellSelectionInfoC onnectedMode speedDependScalingFacto rTReselection 4 CellSelectionInfoC onnectedMode interFreqScalingFactorT Reselection interRatScalingFactorTR eselection tCrMax 4 CellSelectionInfoC onnectedMode 4 CellSelectionInfoC onnectedMode 4 CellSelectionInfoC onnectedMode nCR tCrMaxHyst 4 CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode 4 Passing on or copying of this document. it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-frequency neighbouring cells of the serving cell. This specifies the duration for evaluating allowed amount of cell reselection(s).75 by step of 0. Enumerated (not used. Real (0.1 by step of 0. 30. This specifies the maximum number of cell reselections. Integer (-105.25). This parameter is mapped to non-TCRmax or TCRmax IE for SIB3 filling depending of HCS use or not. 10.16). This specifies the additional time period before the UE can exit high-mobility... 120. When HCS is not used.FACH for the inter-RAT case. 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.PCH or Treselections. When HCS is used.UMTS Radio Mobility onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode PowerConfClass CellSelectionInfoC onnectedMode In [dB] Integer (0. it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-RAT neighbouring cells of the serving cell. When HCS is used. Enumerated (not used. 240).. 180.75 by step of 0..FACH for the inter-frequency case.PCH or Treselections. This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections.31) In [s] From -50 to 33 In [dBm] Integer (-105.06/EN Approved_Standard 17/Sep/2010 Page 46/244 . 60. This threshold is used in the measurement rules for cell re-selection.31) In [s] Integer (0. it specifies the RAT specific threshold in the serving cell used in the inter-RAT measurement rules... 40.91 by step of 2). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections.4. When HCS is not used. 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. Integer (1. This parameter is mapped to non-NCR or NCR IE for SIB3 filling depending of HCS use or not..91 by step of 2). This parameter is mapped to non-TCrmaxHyst or TCrmaxHyst IE for SIB3 filling depending of HCS use or not.. 70). 50.

. In [dB] Integer (-115.6.-25 by step of 2) RSCP.. Part of the BSIC DCS 1800 band used.50) In [dB] Integer(-50..0] step:0.0) Ec/N0.20.6.50) In [dB] Integer (-24..1.5.6.UMTS Radio Mobility 4.2 AT UTRAN/FDD NEIGHBOURING CELL LEVEL SIB 12 12 12 12 12 12 12 12 12 Object FddNeighCellSelectionInfoC onnectedMode FDDCell (neighbouring) FDDCell (neighbouring) FDDCell (neighbouring) FddNeighCellSelectionInfoC onnectedMode FddNeighCellSelectionInfoC onnectedMode FddNeighCellSelectionInfoC onnectedMode FddNeighCellSelectionInfoC onnectedMode FddNeighCellSelectionInfoC onnectedMode description/comment From -50 to 33 In [dBm] Integer(0.-25 by step of 2) In [dBm] Information Element maxAllowedUlTxPower Ncc Bcc GSMbandIndicator bcchFrequency gsmCellIndivOffset qOffset1sn qRxLevMin 4.3 AT GSM NEIGHBOURING CELL LEVEL SIB 12 12 12 12 12 12 12 12 Object GSMCell GSMCell GSMCell GSMCell GSMCell GsmCellSelectionI nfoConnMode GsmCellSelectionI nfoConnMode GsmCellSelectionI nfoConnMode description/comment From -50 to 33 In [dBm] bit string(3) Network Color Code.1 2G TO 3G HANDOVER FOR CS DOMAIN DESCRIPTION DATAFLOW In this case the mobile connected to the CS domain is moved from a 2G cell to a 3G cell. Part of the BSIC bit string(3) Base Station Color Code.5 • • ACCESS NETWORK IMPACTS Ability to broadcast the necessary parameters on the radio interface BCCH.0.. for a PS or CS attached mobile. Passing on or copying of this document. PCS 1900 band used Integer (0. 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 47/244 .6 • CORE NETWORK IMPACTS Support of location registration update from a 3G to a 2G cell.. In [dBm] Integer [-20. 4..4. RRC connection reject in case of unknown u-RNTI 4.5 In [dB] Information Element maxAllowedUlTxPower primaryScramblingCode ulFrequencyNumber dlFrequencyNumber qOffset1sn qOffset2sn qQualMin qRxLevMin cellIndivOffset 4.5..10) In [dB] Integer(-50.1 4.5..4.1023) GSM ARFCN Integer(-10..511) This parameters equals ( 5 * FreqDL MHz ) This parameters equals ( 5 * FreqDL MHz ) Integer(-50.50) In [dB] Integer (-115. 4.5.

06/EN Approved_Standard 17/Sep/2010 Page 48/244 . Passing on or copying of this document.UMTS Radio Mobility Anchor MSC 2G-MSC 3G-MSC BSC Abis BTS Iub SRNC NodeB UE Before After UE Figure 22: 2G to 3G handover for CS The next dataflow is an example of inter-MSC 2G to 3G CS handover. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.

UMTS Radio Mobility UE NodeB RNC 3G-MSC/VLR 2G-MSC/VLR BSS BSSMAP/ Handover Required (Source RNC to target RNC transparent information) MAP/ Prepare Handover (Handover Request) SCCP/ Connection Request SCCP/ Connection Confirm RANAP/ Relocation request (Source RNC to target RNC transparent information) NBAP/ Radio Link Setup Request NBAP/ Radio Link Setup Response AAL2/ ERQ AAL2/ ECF RANAP/ Relocation request Ack (Handover to UTRAN command) MAP/ Prepare Handover ack (Handover Request Ack) BSSMAP/ Handover command (Handover to UTRAN command) RR/ Intersystem to UTRAN Handover command (Handover to UTRAN command) RRC/ Handover to UTRAN complete RRC/ Security Mode Command (Integrity Protection) RRC/ Security Mode complete RRC/ UTRAN Mobility Information (PS domain NAS Information (Routing Area Id)) RRC/ UTRAN Mobility Information Confirm RANAP/ Relocation Detect MAP/ Process Access Signalling (HO detect) RANAP/ Relocation Complete MAP/ Send End Signal BSSMAP/ Clear command GSM resource release BSSMAP/ Clear complete 3 2 1 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. When the handover decision is made.and Bearer Configuration to ALU standard 4 Figure 23: 2G to 3G handover for CS dataflow (1) Handover preparation phase. The request is forwarded to the target 3G RNC which allocates resources to support the call.06/EN Approved_Standard 17/Sep/2010 Page 49/244 . There is no list of possible target. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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). Passing on or copying of this document. The request sent from the source BSC identifies only one cell in one RNC.

which will imply segmentation on the GSM RR interface (i.and Bearer Configuration to ALU standard (see below) 4. In this case. The estimated size for a HANDOVER TO UTRAN RRC message is around 180 bytes in case of a (DCCH + speech 12. around 8 segments).e. The HANDOVER TO UTRAN COMMAND RRC message is sent from the target 3G to the UE via the MSC nodes and the serving BSC. They all are derived from 34. However. default configurations may also be used.6. For the same reason. The behaviour is configurable by parameter isGsmIratHoDefaultConfigurationUsed.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. 4.331 RRC specifications. The handover command message contains the target cell resource description. The handover is performed when the UE is successfully connected to the 3G system. (3) Old resource release phase. These configurations are broadcast on the UTRAN BCCH using SIB 16. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.e. In this version of the document the Alcatel-Lucent RNS either builds the handover message containing: • The explicit target resource description.1. In order to reduce the size of the message.2 With this the segmentation of the handover message at GSM RR can be avoided. These configurations are described in 25.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. (4) Post Handover Procedures. There exist 3 possibilities in the 3GPP specifications for describing the target cell resource: 1. and shall be supported by mobiles. the default configuration has lower performance than the normally used configuration and a reconfiguration after successful handover is required. which pre-defined configurations have been read by the UE – if exists) (2) Handover execution phase. 2. Old radio link(s) in GSM system are released. The UTRAN MOBILITY INFORMATION procedure is used to provide the UE with PS domain Location Information.6.2 APPLICABILITY Depends on BSC algorithm.2) configuration. the handover message will have a length estimated to 160 bytes. • Security Update • RRC measurement setup • UE capability enquiry • Mobility Update • In case of Default Configuration: Radio Link.108 UE conformance testing specification. Passing on or copying of this document. • The default configuration 3 for CS Voice 12. so that the mobile can initiate or resume PS activity. The impact is RR message segmentation on the GSM side. 3. The SECURITY MODE COMMAND procedure is used to trigger integrity protection in UMTS.06/EN Approved_Standard 17/Sep/2010 Page 50/244 . pre-defined configurations may be used. The target resource is explicitly described in the "Intersystem to UTRAN Handover command" message. and are possibly read by the UE when camping on GSM cell.

a resource may not be available.3.3. Resource shortage can also be caused by exhaustion of the reduced Uplink Scrambling Codes for 2G->3G handover with default configuration. this IE contains a “SRNS Relocation Info” container 4.e.5a) • UE security information (25.3.1) • UE Radio Access capability (25.12.3.2. this IE contains a “Handover to UTRAN Info” container • In case of SRNC relocation.6.413 §9.331 §10.4.13.6.413 §9.06/EN Approved_Standard 17/Sep/2010 Page 51/244 . it is deduced by the target RNC by the content of the “RRC information to target RNC” IE. 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.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. However.10) • source RNC to target RNC transparent container (25. there is only one target cell to be considered by the target RNC Passing on or copying of this document.6.UMTS Radio Mobility 4. This IE may be of 2 types: • In case of handover from another RAT.1) • Handover to UTRAN Info (25.4. the RNC tries to allocate a suitable resource based on CAC algorithm. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.331 §10.2.331 §14. which is a mandatory part of the message.3.42) • Security capability (25.331 §10. this paragraph presents a simplified view of the structure of the message: RELOCATION REQUEST (25. GSM or UMTS) the message is issued.1.28) • RRC information to target RNC (25.3.37) • Ciphering algorithm capability • Integrity protection algorithm capability • Pre-defined configuration status information (25.3.331 for RRC specific IE). 25.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.3 4.6.413 for the RANAP part.12.331 §14. In case of congestion.2) • START-CS • Inter-RAT UE radio access capability (25. 4.331 §14.1 ALGORITHM RELOCATION REQUEST MESSAGE STRUCTURE As the RELOCATION REQUEST message is specified in 2 different specifications (24.8.2 RELOCATION REQUEST REJECTION In this version.3.1. 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.331 §10.3.

6. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. as this message contains the following information: • UE Radio Access capability ([A4] §10.06/EN Approved_Standard 17/Sep/2010 Page 52/244 .6.18 Release 99 (resp. Ciphering is started by the mobile immediately after receiving the HANDOVER TO UTRAN COMMAND 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. 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).UMTS Radio Mobility • Due to limitation of the GSM standard for circuit call.3. 3GPP TS 44.e. RLC AM HFN. the RNC will choose a Radio Bearer configuration among the ones which are supported in this version. 4.3.6 DEPENDENCIES WITH GSM For this procedure to be working correctly. in this version: The resource allocation for incoming relocation from 2G follows the same algorithm as for initial call setup resource allocation.3. there is no pool of reserved capacity for incoming relocation from 2G. resulting from the conversion of Kc (GSM ciphering key) by the 3G-MSC.018 Release 4 and beyond). In this case. the algorithm for RAB to RB mapping is the same as used for call initiation.6. UE NodeB RNC RRC/ Handover to UTRAN complete RRC/ Security Mode Command RRC/ Security Mode Complete 4. RLC UM HFN. RLC UM HFN. it is mandatory the GSM BSS supports the “UTRAN classmark change” as specified in GSM TS 04.3. 4.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. Based on RAB parameters requested by the Core Network.3. there will be only one RAB in the “RAB to be setup list” in the RELOCATION REQUEST message Besides. 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).42) • START-CS parameter (this parameter is actually stored on the mobile USIM) Passing on or copying of this document. RLC AM HFN.5 INTEGRITY Integrity is started by the RNC immediately after receiving the HANDOVER TO UTRAN COMPLETE RRC message. resulting from the conversion of Kc (GSM ciphering key) by the 3G-MSC. i.

2 multi rate with 12. In case of handover however.4 4. Segmentation over more than two GSM air interface blocks could have a significantly detrimental impact on handover performance.4. Default Configuration #3 (see [A4]) is supported for 12.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.2 multi rate with 12.2 RETURN ON OLD CHANNEL In case the mobile fails to synchronize or access on the new UTRAN channel. Passing on or copying of this document. the old channels are released if they were dedicated channels and all contexts related to the connections with that mobile station are cleared.2 multi rate without 12. subsequent segments can only be transferred after acknowledgement of earlier transmitted segments.6.2 kbps CS speech and transmitted in the handover command via core network and GERAN to the UE. if timer T3121 elapses before either the HANDOVER TO UTRAN COMPLETE ([A4] and [A6]) RRC message is received on the UTRAN channel(s). In case that segmentation is used. 4.2 mono rate != 12. Within this reconfiguration the RLC parameters should be reconfigured.6.6.3. This implies that it may be impossible to quickly transfer a segmented handover message. optimized configuration.1 FAILURE CASES CONNECTION RELEASE On the network side. If RLC reconfiguration is available. or a HANDOVER FAILURE RRC message is received on the old channels. then it advisable to enable it (parameter isRlcAMReconfigurationAllowed and isUER99RlcAmReconfigurationAllowed).06/EN Approved_Standard 17/Sep/2010 Page 53/244 . indicated by receipt of the HANDOVER TO UTRAN COMPLETE message.UMTS Radio Mobility 4. 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 any any any Iu UP v1 Iu UP v2 Offered AMR codecs in 2G to 3G relocation request mono rate 12. 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. The usage of the default reduces the size of the HANDOVER TO UTRAN COMMAND message and thus the GSM HANDOVER COMMAND message.2 Selected configuration type for handover to UTRAN command default config #3 full config full config default config #3 full config After successful completion of the GSM to UMTS handover. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. The UMTS standard allows specifying individually the radio bearer and transporting channels via a large set of parameters. then either the use of default configurations should be disabled (parameter isGsmIratHoDefaultConfigurationUsed) or the call will have sub-optimal RLC parameter settings. or the mobile station has re-established the call.4. the quality of the uplink may be quite poor resulting in a failure to transfer acknowledgements.6. the mobile returns on the old channel it was using in the GSM source cell. If it is not available. too. This results in large messages. the RNC reconfigures the radio bearer to the normal. The handover performance is improved when it is possible to transfer the handover to UTRAN command within a non-segmented GSM air interface message. 4.

(2) As a consequence.06/EN Approved_Standard 17/Sep/2010 Page 54/244 . a relocation failure is sent from RNC to the 3G-MSC. a handover failure message is sent to the 2G_MSC. the target RNC receives an Iu release command message from its MSC.6. 4. leading to a cancellation of the handover procedure on the MAP interface.4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. UE NodeB RNC 3G-MSC/VLR 2G-MSC/VLR BSS BSSMAP/ Handover Required (Source RNC to target RNC transparent information) MAP/ Prepare Handover (Handover Request) RANAP/ Relocation request (Source RNC to target RNC transparent information) No resource in RNS RANAP/ Relocation failure (No resource available) MAP/ Prepare Handover ack (failure) BSSMAP/ Handover Required reject Passing on or copying of this document.3 RELOCATION REJECTED BY TARGET RNC If the relocation preparation phase fails (see possible causes in the related chapter).UMTS Radio Mobility UE NodeB RNC 3G-MSC/VLR 2G-MSC/VLR BSS Handover preparation phase (as in normal successful case) RANAP/ Relocation request Ack (Handover to UTRAN command) MAP/ Prepare Handover ack (Handover Request Ack) BSSMAP/ Handover command (Handover to UTRAN command) RR/ Intersystem to UTRAN Handover command (Handover to UTRAN command) The UE returns on the old channel RR/ Handover Failure BSSMAP/ Handover failure MAP/ Abort Cancellation of on-going HO procedure 1 RANAP/ Iu Release Command NBAP/ Radio Link Deletion Request NBAP/ Radio Link Deletion Response AAL2/ REL AAL2/ RLC RANAP/ Iu Release Complete 2 Figure 24: 2G to 3G handover for CS – failure case (1) As the mobile returns to the old channel. requesting all the resources which have been allocated during the handover preparation phase to be released.

7 • • CORE NETWORK IMPACTS BSSMAP to RANAP message interworking at the 3G-MSC level. Ciphering and integrity key conversion at the 3G-MSC 4. GGSN 2G-SGSN 3G-SGSN BSC Iub BTS 1 Abis RNC NodeB 2 UE Before After UE Figure 26: 2G to 3G handover for PS Passing on or copying of this document. 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.06/EN Approved_Standard 17/Sep/2010 Page 55/244 .UMTS Radio Mobility Figure 25: 2G to 3G handover for CS – failure case 4. This implies not only message conversion.7.6.6 • • • ACCESS NETWORK IMPACTS 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 4. 4. but also deriving RAB attributes from the current channel in use in GSM. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.6.5 PARAMETERS The parameters are: Name is2GTo3GCSHandoverAllowedWithinRnc Object/Class InterFreqMeasConf Class3 isGsmIratHoDefaultConfigurationUsed RadioAccessService Class3 Definition 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 This parameter enables/disables the use of default configurations for inter RAT handover from GSM to UMTS.6.

CS and PS parts are managed independently. and is moved from a 3G cell to a 2G cell. Passing on or copying of this document. 4. Once PDP context transferred from old to new SGSN.1 3G TO 2G HANDOVER FOR PS DOMAIN DESCRIPTION In this case the mobile connected to the network in PS mode is moved from a 3G cell to a 2G-GPRS cell.06/EN Approved_Standard 17/Sep/2010 Page 56/244 . The GPRS mobility is done via a Routing Area Update procedure.9. UE BTS Serving BSC GMM/ RA update request Target RNC 3G-SGSN 2G-SGSN GTP/ SGSN ctx request RANAP/ RAB assignment request RANAP/ RAB assignment response GTP/ SGSN ctx ack GTP/ SGSN ctx response PDP context update with GGSN Update GPRS location with HLR GMM/ RA update accept GMM/ RA update complete Figure 27: 2G to 3G handover for PS 4.UMTS Radio Mobility In GPRS. the mobility decision is taken by the UE. 4.9. the 3G SGSN requests for a RAB establishment as for a call establishment. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. The next dataflow is an example of inter-SGSN 2G to 3G handover.7.8. The CS part is managed as described in § 4. 2G TO 3G HANDOVER FOR CS + PS DOMAINS In this case the mobile connected to both CS and PS domains.6 and the PS part as in § 4.

the mobile is using dedicated resources for PS services in 3G network. In this version. The cell change order message contains the Passing on or copying of this document. resources are allocated in the target BSS.UMTS Radio Mobility GGSN 3G-SGSN 2G-SGSN SRNC Iub NodeB 1 Abis BSC BTS 2 UE Before After UE Figure 28: 3G to 2G handover for PS The next dataflow is an example of inter-SGSN 3G to 2G handover. the handover decision is taken by the SRNC (as if it were a CS call). Therefore. Following the mobile access on the 2G cells. BCCH ARFCN) 2G access and GPRS resource allocation GMM/ RA update request GTP/ SGSN ctx request RANAP/ SRNS ctx request RANAP/ SRNS ctx response 2 GTP/ SGSN ctx response GTP/ SGSN ctx ack GMM/ RA update response 1 RANAP/ SRNS data forward command RANAP/ Iu release command NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp 3 RANAP/ Iu release complete TDATAfwd Figure 29: 3G to 2G handover for PS dataflow (1) Based on measurements. Meanwhile. as opposed to CS handover.06/EN Approved_Standard 17/Sep/2010 Page 57/244 . the connection and resource allocation in the target system are performed on UE request. the serving RNC decides to hand the mobile over a 2G cell. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. UE Serving NodeB Serving RNC Target BSC 2G-SGSN 3G-SGSN RRC/ Measurement Report RRC/ Cell change order from UTRAN (BSIC.

1 FAILURE CASES TARGET CELL SYNCHRONIZATION FAILURE If the mobile fails to access and synchronize on the target GSM cell. the mobile is using either dedicated or shared resources for PS services in 3G network. BCCH ARFCN) The HO fails on the target system RRC/ Cell change order from UTRAN failure Figure 30: 3G to 2G handover for PS .3 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.4 4.3 TARGET CELL CHOICE Please refer to section 4. Alcatel-Lucent UTRAN allows a possible return on the old channels. The decision to launch this mobility procedure is taken by the iMCTA function (refer to section 4.9. 4.failure case Passing on or copying of this document. the PS subscribers will be kept in 3G as much as possible.06/EN Approved_Standard 17/Sep/2010 Page 58/244 .3. the old SRNC shall not complete the resource release phase until TDATAfwd (data forwarding timer). 4.2 MEASUREMENTS CONFIGURATION Please refer to section 4. In such a case. In this version. and will only be handed to 2G in case of UTRAN coverage holes. Since the quality of service offered to subscribers will be better in UMTS as compared to what GPRS can offer.2 APPLICABILITY In this version.3.19) 4. 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.20.4. (3) Although not supported by UTRAN in this version. 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.9.9. Even if no data is forwarded.20. TDATAfwd is equal to 0 sec. data forwarding may be asked by the source SGSN. 4. (2) The mobile updates its location in the target 2G system using the "RA update" procedure. In this version. 4. or when leaving a UTRAN coverage spot.9.9.1 ALGORITHM HO DECISION PROCESS Please refer to section 4. UE Serving NodeB Serving RNC Target BSC 2G-SGSN 3G-SGSN RRC/ Cell change order from UTRAN (BSIC.20.3.9.9. N-PDU and GTP-PDU will not be transferred by the RNC on the RANAP protocol.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.

use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. possibly next time the handover criteria is evaluated and using "target cell choice" algorithm as specified. As for "packet forwarding".9.5.6 ACCESS NETWORK IMPACTS 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. No handover will be tried towards the 2nd best cell.e. 4. Passing on or copying of this document. the handover is seen from the BSS as a new GPRS call setup). i.e. Restrictions: • data packet forwarding is not supported by the source RNC. Therefore. 4.7 • • • CORE NETWORK IMPACTS 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.06/EN Approved_Standard 17/Sep/2010 Page 59/244 . Definition This parameter indicates if the PS handover toward a GSM cell is allowed.g.9.UMTS Radio Mobility Another handover will be tried as in the normal process.1 DESCRIPTION In this case the mobile connected to the CS domain is moved from a 3G cell to a 2G cell.20. 3G TO 2G HANDOVER FOR CS DOMAIN 4.9. • the "SRNS context transfer" procedure is not supported by the source RNC (i. TCP).10. the messaging is supported but the PDU counters are not transferred). some packets will be lost during the handover. since the target RNC doesn't know which GTP-PDU have actually been sent and acknowledged. the consequence is that some packets may be lost. End-to-end reliability is supposed to be provided by transport layer (e. 4. Section 6.5 PARAMETERS The parameters are: Name Object/Class RadioAccessService Class3 activationHoGsmPsAllowed See also: Section 4.10.

When the handover decision is made. UE NodeB RNC 3G-MSC/VLR 2G-MSC/VLR BSS RRC/ Measurement Report RANAP/ Relocation Required (CM2. old BSS to new BSS information) BSS resource allocation BSSMAP/ Handover Request Ack (handover command) RANAP/ Relocation Command (handover command) MAP/ Prepare Handover Ack (Handover Request Ack) 1 RRC/ Handover from UTRAN Command (handover command (cell description)) RR/ Handover Access RR/ Physical Information (Timing Advance) RR/ Handover Complete 2 MAP/ Process Access Signalling (HO detect) BSSMAP/ Handover Detect BSSMAP/ Handover Complete MAP/ Send End Signal RANAP/ Iu release command NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp AAL2/ REL AAL2/ RLC RANAP/ Iu release complete 3 Figure 32: 3G to 2G handover for CS dataflow (1) Handover preparation phase. The RELOCATION REQUIRED message contains the UE GSM capability (ClassMark 2 and 3). CM3. old BSS to new BSS information) MAP/ Prepare Handover (Handover Request) BSSMAP/ Handover Request (CM2.06/EN Approved_Standard 17/Sep/2010 Page 60/244 . CM3. The request is forwarded to the target 2G BSS which allocates resources to support the call. 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.UMTS Radio Mobility Anchor MSC 3G-MSC 2G-MSC Relay MSC SRNC Iub NodeB Abis BSC BTS UE Before After UE Figure 31: 3G to 2G handover for CS The next dataflow is an example of inter-MSC 3G to 2G CS handover. the serving RNC activates the relocation procedure towards the 3G-MSC.

10.4 4. in case the mobile is handed over 3G again.3 4. The handover is performed when the UE is successfully connected to the 2G system. Old radio link(s) and associated AAL2 Cid(s) are released.10.10.10. Passing on or copying of this document.3. 4.1 FAILURE CASES TARGET CELL SYNCHRONIZATION FAILURE If the mobile fails to access and synchronize on the target GSM cell.4 sections). 4.1 ALGORITHM HO DECISION PROCESS Please refer to section 4.20. 4. 4.20).10. which is transferred to the target BSS.2 to 4.e. triggered on radio alarm criterion. 3G to 2G handover for CS calls which have reached the call established state is a rescue type of mobility. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.20.194.3. It also contains the cell load information group element if feature uRRM step 2 is activated. 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.10. the 3G infrastructure may also move calls in the following use cases: iMCTA function decision (refer to section 4.4. BSIC and BCCH ARFCN).2 APPLICABILITY In this version. which will allow the mobile to synchronize to the cell when the handover is made in blind mode. (3) Old resource release phase.20.18.3 TARGET CELL CHOICE Please refer to section 4. 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.2 MEASUREMENTS CONFIGURATION Please refer to section 4.10. it has to send a HANDOVER FROM UTRAN FAILURE message on the channel that was used in the serving UTRAN cell(s).18. In addition to providing this alarm-based 3G-2G handover for established calls.UMTS Radio Mobility The "old BSS to new BSS" information element contains the UE capability. the RNC instructs the UE to perform intersystem cell reselection and re-originate the call on the 2G network (refer to 4. This message contains the target cell description (i. 4. or when leaving a UTRAN coverage spot. CS subscribers may be handed to 2G in case of UTRAN coverage holes. (2) Handover execution phase.06/EN Approved_Standard 17/Sep/2010 Page 61/244 .3.

failure case If allowed by parameter isGsmIratHoToNextBestCellAllowed. an event 2F indicates the end of the alarm condition. Passing on or copying of this document. In this case. BCCH ARFCN) The HO fails on the target system 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.2 RELOCATION PREPARATION FAILURE It may happen the Relocation Preparation fails. No handover will be tried towards the 2nd best cell. 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.4. In this case the RNC tries the handover to the strongest inter-frequency target. old BSS to new BSS information) MAP/ Prepare Handover (Handover Request) BSSMAP/ Handover request (CM2. e. i.g. because the target GSM BSS has no resource left. possibly next time the handover criteria are evaluated and using "target cell choice" algorithm as specified. e.e. 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. the relocation preparation procedure ends up as follows: UE NodeB RNC 3G-MSC/VLR 2G-MSC/VLR BSS RRC/ Measurement Report RANAP/ Relocation Required (CM2.e.5 PARAMETERS The parameters are: Name Object/Class RadioAccessService Class3 activationHoGsmCsAllowed Definition This parameter indicates if the CS handover toward a GSM cell is allowed. The attempts are repeated until either • The relocation preparation has failed for the last eligible GSM cell • A follow-up measurement report contains both.10. 4. eligible GSM and inter-frequency target cells.06/EN Approved_Standard 17/Sep/2010 Page 62/244 .UMTS Radio Mobility UE Serving NodeB Serving RNC Target BSC 2G-MSC 3G-MSC RRC/ Handover from UTRAN command (BSIC. Another handover will be tried as in the normal process. possibly next time the handover criteria is evaluated and using "target cell choice" algorithm as specified. • The criteria for handover are no longer fulfilled. CM3. CM3. i. old BSS to new BSS information) BSSMAP/ Handover Failure (cause) MAP/ Prepare Handover ack (Handover failure) RANAP/ Relocation preparation failure (cause) Figure 34: 3G to 2G handover for CS .g.10.

1 DESCRIPTION GENERAL In this case the mobile is connected to both CS and PS domains. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.AttRelocPrepOutCS.1 4.19.11. due to overload. • 4.AttRelocPrepOutCS.7 • CORE NETWORK IMPACTS BSSMAP to RANAP message interworking at the 3G-MSC level.06/EN Approved_Standard 17/Sep/2010 Page 63/244 .6 ACCESS NETWORK IMPACTS 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) 4.10. but also deriving GSM channel type attributes from the RAB attributes.5. Passing on or copying of this document. IRATHO. 3G TO 2G HANDOVER FOR CS+PS DOMAINS 4. The difference between IRATHO_AttRelocPrepOutCS and IRATHO.NextBestCell represents the actual number of handover attempts without repeated relocation preparation procedures. This counter is a complement to counter IRATHO_AttRelocPrepOutCS. and is moved from a 3G cell to a 2G cell.8 • PERFORMANCE MANAGEMENT IRATHO.11. 4.AttRelocPrepOutCS. 4.SuccRelocPrepOutCS.g.10. IRATHO_AttRelocPrepOutCS is pegged on all attempted relocation preparations for CS UMTS to GSM handover.NeighbRnc) Attempted relocation preparations for CS UMTS to GSM handover to the next best GSM cell. This implies not only message conversion. See also Section 4.10. e.1.11. IRATHO.UMTS Radio Mobility isCellLoadInformationSendingAllowed isGsmIratHoToNextBestCellAllowed RadioAccessService Class3 RadioAccessService Class3 This parameter controls sending of cell load information IE in handover messages to 2G This parameter enables/disables the IRAT handover to the next best GSM cell if handover is not possible to the first cell.NextBestCell (-.NeighbRnc) Successful relocation preparations for CS UMTS to GSM handover to the next best GSM cell (CS interRAT Handover Attempt) from network point of view. Section 6.NextBestCell (-.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.

• class B: the mobile is attached to both GPRS and GSM services. the PDP context will remain active in the 3G-SGSN. i.e. the CS service is handed over the target GSM cell exactly as in the "3G to 2G handover for CS" case. the source RNC will not take into account the mobile GPRS capability in the handover decision algorithm. Alternate use only. i. GSM CS and PS resource allocation are coordinated in BSC/PCU in order to simplify mobile implementation. Since the mobile will not detach nor deactivate the PDP context which were active in the source 3G-SGSN. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Class A or DTM The real successful case (i. the CS service is handed over to GSM and the PS service cannot be maintained. Passing on or copying of this document. 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. Remark: In this version.06/EN Approved_Standard 17/Sep/2010 Page 64/244 .UMTS Radio Mobility GGSN Anchor MSC 3G-SGSN 3G-MSC 2G-MSC 2G-SGSN SRNC Iub NodeB Abis BSC BTS UE Before After UE 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.e. In this mode. This case is not further considered in this document. and can support simultaneous traffic • DTM (Dual Transfer Mode): DTM is a subset of class A mode of operation.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.: • 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. 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 PS service is handed over the target GSM cell in the same way as the "3G to 2G handover for PS" case.

CM3. old BSS to new BSS information) MAP/ Prepare Handover (Handover Request) BSSMAP/ Handover request (CM2. CM3. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.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.UMTS Radio Mobility 4.1. UE NodeB RNC 3G-MSC/VLR 2G-MSC/VLR BSS RANAP/ Relocation Required (CM2. old BSS to new BSS information) BSS resource allocation BSSMAP/ Handover request Ack (handover command) RANAP/ Relocation command (handover command) MAP/ Prepare Handover ack (Handover Request) 1 RRC/ Handover from UTRAN command (handover command (cell description)) 2 RR/ Handover Access MAP/ Process Access Signal (HO detect) MAP/ Send End Signal BSSMAP/ Handover Detect BSSMAP/ Handover Complete 2G access and GPRS resource allocation GMM/ RA update request 3G-SGSN 2G-SGSN GTP/ SGSN ctx request RANAP/ SRNS ctx request RANAP/ SRNS ctx response GTP/ SGSN ctx response GTP/ SGSN ctx ack GMM/ RA update response 3 3G-MSC/VLR RANAP/ Iu release command TRelocResourceRe leasePs3Gto2Gtim er (set to 20 sec) Resources Release NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp AAL2/ REL AAL2/ RLC 3G-SGSN RANAP/ Iu release request RANAP/ Iu release command 4+5 RANAP/ Iu release complete Figure 36: 3G to 2G handover for CS+PS dataflow Passing on or copying of this document.06/EN Approved_Standard 17/Sep/2010 Page 65/244 .11.

the serving RNC activates the relocation procedure towards the 3G-MSC. (2) CS Handover execution phase. Upon receipt of the IU RELEASE COMMAND (PS) or RelocResourceReleasePs3Gto2Gtimer expiration. In this release: upon receipt of message IU RELEASE COMMAND (CS).e. the RNC coordinates release of old CS and PS resources. In that case. The order of the different phase may be different as compared to a real case. target cell BSIC and BCCH). the RNC arms immediately a timer called RelocResourceReleasePs3Gto2Gtimer (optimized at 20 sec) and sends an IU RELEASE REQUEST (PS) message. • Iu PS resource release. the registration is accepted. For example. the source SGSN may request the source RNC to forward the PS packets queued in the SRNC using the SRNS DATA FORWARD COMMAND message. As for the "3G to 2G handover case". (3) PS service re-establishment: The UE performs a packet access in the 2G new cell. the RNC behaviour is the same as for the "3G to 2G PS handover" case. When the handover decision is made. The data flow above is only provided as an example. AAL2 Cid(s) associated to the CS domain are released. the Iu CS release (4) may be requested before the PS registration (3). and the PS data transfer is resumed. The handover command is sent from the target 2G to the UE via the MSC nodes and the serving RNC.UMTS Radio Mobility (1) CS Handover preparation phase. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. The request is forwarded to the target 2G BSS which allocates resources to support the call. Eventually. 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 command message contains the cell description (i. The handover is performed when the UE is successfully connected to the 2G system.06/EN Approved_Standard 17/Sep/2010 Page 66/244 . (4) + (5) coordinated release of old CS + PS resources • Old radio links are released • Iu CS resource release. Upon receipt of the IU RELEASE COMMAND (PS): RNC TRelocResourceReleasePs 3Gto2Gtimer (set to 20 sec) 3G MSC/VLR RANAP/ Iu Release Command RANAP/ Iu Release Request RANAP/ Iu Release Command 3G SGSN Release of all CS and PS resources RANAP/ Iu Release Complete parallel 4+5 RANAP/ Iu Release Complete UE 3G MSC/VLR 3G SGSN Upon receipt TRelocResourceReleasePs3Gto2Gtimer expiration: Passing on or copying of this document.

corresponding to the highest value. In phase 3 and 4. The following dataflow illustrate the 1st case: Phase 1 and 2 (handover preparation and execution) are performed as in the successful case. In any case the RNC releases the CS and PS resources: phase “(4)+ (5) coordinated release of old CS and PS resources”. the source RNC requests for both CS and PS Iu release. This case is further described in the [unsuccessful case] section.11.UMTS Radio Mobility RNC TRelocResourceReleasePs 3Gto2Gtimer (set to 20 sec) 3G MSC/VLR RANAP/ Iu Release Command RANAP/ Iu Release Request 3G SGSN 4+5 Release of all CS and PS resources RANAP/ Iu Release Complete UE 3G MSC/VLR 3G SGSN 4.e. one for the CS domain) are implemented in the RNC to request a release of UTRAN resources to the relevant CN domain.3 SUCCESSFUL CLASS B CASE In this case the PS service will not be handed over the 2G target cell. when the "Iu release" timer elapses. the handover has failed and the mobile has not returned to the old channel) • the PS service is lost during HO (e. In the CS+PS case. 4.11. The phase (3) “PS service reestablishment” does not occur.4 HANDLING UNSUCCESSFUL CASES Iu connections timers In order to cover the following case: • the mobile is completely lost (i. because of limited UE capability (class B or C). only one timer is started.06/EN Approved_Standard 17/Sep/2010 Page 67/244 .1.g. As the RNC sends an IU RELEASE REQUEST to the 3G-SGSN.1. the RNC will receive an IU RELEASE COMMAND from the 3G-SGSN or will experience the timeout RelocResourceReleasePs3Gto2Gtimer (set to 20 sec). use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. or because the target cell cannot accept or support GPRS access) Two timers (one for the PS domain. Passing on or copying of this document.

In which case.UMTS Radio Mobility UE NodeB RNC 3G-MSC/VLR RANAP/ Relocation Required (CM2.06/EN Approved_Standard 17/Sep/2010 Page 68/244 . old BSS to new BSS information) MAP/ Prepare Handover (Handover Request) 1 RANAP/ Relocation command (handover command) MAP/ Prepare Handover ack (Handover Request) 2 Iu release timer RRC/ Handover from UTRAN command (handover command (cell description)) 3G-SGSN RANAP/ Iu release request RANAP/ Iu release request RANAP/ Iu release command RANAP/ Iu release command NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp AAL2/ REL AAL2/ RLC RANAP/ Iu release complete RANAP/ Iu release complete 3 Figure 37: 3G to 2G handover for CS+PS . Following successful CS handover the Core Network commands a release of the Iu.failure case The following dataflow illustrates the 2nd case: Phase 1 and 2 (handover preparation and execution) are performed as in the successful case. CM3. This release is not processed until the "Iu release timer" elapses. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Passing on or copying of this document. both Iu-CS and PS connections (and associated UTRAN resources) are released.

From a source UTRAN point of view. a 3G to 2G PS+CS handover is tried. Due to the time needed to resynchronise the CS service.2 [3G To 2G Handover for CS Domain] section APPLICABILITY Passing on or copying of this document. a 3G to 2G PS+CS handover is tried.2 APPLICABILITY See 4.). 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. • The handover for the CS service is successfully performed.10. as in the CS only case. In that case. If a 3G to 2G handover decision is made while a CS call is active and a PS call is being setup. and if the handover conditions are still valid. the mobile returns on the old channel using the Handover from UTRAN failure message and the relocation is cancelled by the source RNC. Once the CS RAB is setup.failure case HO failure case The possible failure cases are the following: • The synchronisation on the new CS channel fails. and if the handover conditions are still valid. nothing is done until the CS RAB is established.11..UMTS Radio Mobility UE NodeB RNC 3G-MSC/VLR RANAP/ Relocation Required (CM2. In this case. CM3. but the PS registration fails (reject from the new SGSN. or because GPRS is not supported by target cell . nothing specific is done. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. old BSS to new BSS information) MAP/ Prepare Handover (Handover Request) 1 RANAP/ Relocation command (handover command) Iu release timer MAP/ Prepare Handover ack (Handover Request) 2 RRC/ Handover from UTRAN command (handover command (cell description)) RANAP/ Iu release command 3G-SGSN RANAP/ Iu release request RANAP/ Iu release command 3 NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp AAL2/ REL AAL2/ RLC RANAP/ Iu release complete RANAP/ Iu release complete Figure 38: 3G to 2G handover for CS+PS .06/EN Approved_Standard 17/Sep/2010 Page 69/244 . 4. it is not expected the PS service can be resumed in the new cell before the CS service. Once the PS RAB is setup. nothing is done until the PS RAB is established.. this case is identical to the Class B mobile handover case. whereas the PS service has failed. The CS service goes on.

4.11.9.12. 4. 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.3.UMTS Radio Mobility 4.3 4.11.11. Passing on or copying of this document.19. 4G TO 3G RELOCATION FOR PS DOMAIN 4.06/EN Approved_Standard 17/Sep/2010 Page 70/244 .19.20.3. as compared to the 3G to 2G PS or CS handover.5 ACCESS NETWORK IMPACTS 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 4.1. Section 6.11.1 4. 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" 4.1 ALGORITHM HO DECISION PROCESS Please refer to section 5.3.3 TARGET CELL CHOICE Please refer to section 4.12.11. the 2 handover procedures are seen as independent.11.1 DESCRIPTION DATAFLOW In this case the mobile connected to the network in PS mode is moved from a 4G eNodeB cell to a 3G cell.2 MEASUREMENTS CONFIGURATION Please refer to section 4.4 Refer to: PARAMETERS Section 4. 4.6 CORE NETWORK IMPACTS No specific impact. Since the Gs interface is not supported.12. 4.11.5.

Interworking is provided only with Gn and Gp interfaces but no S3. S4 or S5/S8 interfaces. VPN. Passing on or copying of this document.g. these Gn/Gp SGSNs provide no functionality that is introduced specifically for the EPS or for interoperation with the EUTRAN.e.06/EN Approved_Standard 17/Sep/2010 Page 71/244 . The next dataflow is an example of 4G to 3G relocation request. i. FTP) Anchor of the IP session Figure 39: 4G to 3G handover (Interworking with pre-Rel.. 8 legacy SGSN.UMTS Radio Mobility GERAN BTS BTS Abis BSC BSC Gb • MME acts like a SGSN • PGW acts like a GGSN • MME & PGW have to support Gn interface (GTPv1-c support) UTRAN SGSN SGSN RNC RNC Pre-Rel 8 PrePre-Rel 8 Iu-ps Gn (signaling) Gr NB NB Iub S6a HSS HSS Pre-R8 Interfaces Rx MME MME S1-MME S11 E-UTRAN S1-U S5 S10 Gn (user) PCRF PCRF Gx Application Function SGi eNB eNB Control plane User plane SGW SGW PGW/GGSN PGW/GGSN Data Services (e. Without direct tunnelling) The PDN GW provides the functions of a GGSN for the SGSN. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.

Target Identification.and Bearer Configuration to ALU standard 4 Figure 40: 4G to 3G handover for CS dataflow (1) Handover preparation phase. Tunnel Endpoint Identifier Signalling. RANAP Cause. the source eNodeB sends a handover required towards the source MME to request the CN to establish resources in the target RNC. MM Context. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. RAN Transparent Container.UMTS Radio Mobility UE NodeB RNC SGSN MM E eNB S1/ Handover Required (Source RNC to target RNC transparent information) GTP/ Forward Relocation request (Handover Required) SCCP/ Connection Request SCCP/ Connection Confirm RANAP/ Relocation request (Source RNC to target RNC transparent information) 1 NBAP/ Radio Link Setup Request NBAP/ Radio Link Setup Response AAL2/ ERQ AAL2/ ECF RANAP/ Relocation request Ack (Handover to UTRAN command) GTP/ Forward Relocation response (Handover Request Ack) S1/ Handover command (Handover to UTRAN command) RRC mobility from EUTRAN command (Handover to UTRAN command) RRC/ Handover to UTRAN complete RANAP/ Relocation Detect RRC/ Security Mode Command (Integrity Protection) RRC/ Security Mode complete RRC/ UTRAN Mobility Information (PS domain NAS Information (Routing Area Id)) RRC/ UTRAN Mobility Information Confirm RANAP/ Relocation Complete GTP/ Forward Relocation Complete () GTP/ Forward Relocation Complete Acknowledge () 2 S1/ UE context release command S1/ UE context release complete 3 Follow up procedures after successful handover from E-UTRAN to UMTS: • Security Update • RRC measurement setup • UE capability enquiry • Mobility Update • In case of Default Configuration: Radio Link. PDP context contains GGSN Address for User Plane and Passing on or copying of this document. and the target SGSN. GCSI) to the new SGSN.06/EN Approved_Standard 17/Sep/2010 Page 72/244 . PDP Context. When the handover decision is made. The MME sends a Forward Relocation Request message (IMSI.

12. and the IE “Encryption Information”. so that the mobile can initiate or resume PS activity. The UTRAN MOBILITY INFORMATION procedure is used to provide the UE with PS domain Location Information. The handover command message contains the target cell resource description.2.331 §10.UMTS Radio Mobility Uplink TEID for Data.42c) • START-PS • Inter-RAT UE radio access capability (25.28) • RRC information to target RNC (25. The timer Treloc complete is started. RAB context).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 Passing on or copying of this document.1) • Handover to UTRAN Info (25. The successful allocation of resources is confirmed to the CN via the Ranap Relocation Request Acknowledge message.1. The S1 Handover Command message is sent to the source eNB including the RRC Handover to UTRAN message.331 §14. • source RNC to target RNC transparent container (25.4. (3) Old resource release phase. (4) Post Handover Procedures. SCCP connection is established between the SGSN and the RNC.3.10) • CN Domain Indicator (M): PS Domain.42) • Security capability (25. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1) • UE Radio Access capability (25. The handover is performed when the UE is successfully connected to the 3G system. • • • • Security Update RRC measurement setup UE capability enquiry Mobility Update 4. . The target SRNC confirms to the CN that the SRNC relocation has been successful by sending the Ranap Relocation Complete message.3.3. The timer Treloc complete is stopped by the SGSN. The HANDOVER TO UTRAN COMMAND RRC message is sent from the target 4G to the UE.413 §9.331 §10. The RNC checks and allocates the resources needed in order to become the SRNC (RRC context. which represent the information used for the ciphering and integrity protection.12.331 §10.37) • Ciphering algorithm capability • Integrity protection algorithm capability • Pre-defined configuration status information (not used) • UE security information (not used) • UE security information2 (25.12.8. The RRC Handover Command message is included in the IE “target RNC to source RNC transparent container”. Old radio link(s) in LTE system are released.1. 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”.1 ALGORITHM RELOCATION REQUEST MESSAGE STRUCTURE RELOCATION REQUEST (25.12.331 §14. The SECURITY MODE COMMAND procedure is used to trigger integrity protection in UMTS.3. The Source to Target Transparent Container received from eNodeB is indicated as RAN Transparent Container.331 §10. This message must also contain the IEs “Integrity Protection Information”.3.2 4.413 §9.3.06/EN Approved_Standard 17/Sep/2010 Page 73/244 .3. (2) Handover execution phase.2.

2. see Note 1). Source RNC To Target RNC Transparent Container. So the proposal is to not use them in E-UTRA when asking the UE to report its UTRAN capabilities. GSM or E-UTRAN) the message is issued.12.1. In case of congestion. 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”.2 RELOCATION REQUEST REJECTION In this version. 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. a resource may not be available.e.UMTS Radio Mobility • Encryption information The difference with the CS 2G 3G relocation (4.06/EN Approved_Standard 17/Sep/2010 Page 74/244 . • 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. • 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. the RNC tries to allocate a suitable resource based on CAC algorithm. We don’t guess it will be an issue in E-UTRA.6. RAB to be setup List • Synchronisation Indicator (Not used. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Passing on or copying of this document.3. There is a ciphering mismatch with parameter FromEutraRelocationCiphering.1) concerns the following IE: • • CN Domain Indicator: PS Domain.3 TARGET RESOURCE ALLOCATION IN RNC Unlike the 2G 3G relocation. only significant for speech) • Data Volume Reporting Indication (not used) • PDP type information (not used) • UP Mode Versions (to be used). several RAB can be received in the the “RAB to be setup list” in the RELOCATION REQUEST message. 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).12.2 uses the 3GPP Iu Rel 7. see Note 1) • UE radio access capability comp2 (not used. 4.2. However. • UE security information2 (START-PS values to be used) • UE radio access capability compressed (not used. 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.

use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. in this version: The resource allocation for incoming relocation from 4G follows the same algorithm as for initial call setup resource allocation.2. RLC UM HFN. RLC AM HFN. 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. i. there is only one target cell to be considered by the target RNC Besides. In this case. 4. resulting from the conversion of KASME (LTE ciphering key) by the MME. 4. resulting from the conversion of Kc (LTE ciphering key) by the MME. 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). Based on RAB parameters requested by the Core Network. there is no pool of reserved capacity for incoming relocation from 4G.5 INTEGRITY Integrity is started by the RNC immediately after receiving the HANDOVER TO UTRAN COMPLETE RRC message.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.2. 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).e. Passing on or copying of this document. Ciphering is started by the mobile immediately after receiving the HANDOVER TO UTRAN COMMAND 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.UMTS Radio Mobility The maximum of PS Rab supported simultaneously is 3 by taken into the following combinations.12. the RNC will choose a Radio Bearer configuration among the ones which are supported in this version.06/EN Approved_Standard 17/Sep/2010 Page 75/244 . the algorithm for RAB to RB mapping is the same as used for call initiation.12.

6 DEPENDENCIES WITH LTE For this procedure to be working correctly.2.12.UMTS Radio Mobility UE NodeB RNC RRC/ Handover to UTRAN complete RRC/ Security Mode Command RRC/ Security Mode Complete 4.12.3. 4.06/EN Approved_Standard 17/Sep/2010 Page 76/244 . it is mandatory the MME supports translation from EPS bearer to PDP contexts supported by SGSN and UTRAN. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1 FAILURE CASES RELOCATION REJECTED BY TARGET RNC If the relocation preparation phase fails.4 PARAMETERS The parameters are: Name isEutraToUtraHhoAllowed Object/Class RadioAccessService Class3 Definition This parameter indicates whether the 4G To 3G PS Handover is allowed within the RNC YES: incoming relocation request from 4G are processed Passing on or copying of this document.12.12. a relocation failure is sent from RNC to the SGSN. UE NodeB RNC SGSN MM E eNB S1/ Handover Required (Source RNC to target RNC transparent information) GTP/ Forward Relocation request (Handover Required) SCCP/ Connection Request SCCP/ Connection Confirm RANAP/ Relocation request (Source RNC to target RNC transparent information) RANAP/ Relocation failure GTP/ Forward Relocation failure S1/ Handover preparation failure Figure 41: 4G to 3G handover preparation failure case 4.3 4.

UE connection release by requesting the UE to access a given Fdd cell (selected in blind mode or with measurements). As the RNC does not know the relocation cause “CS fallback triggered’.12. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.2.1. cipheringDisabledIgnore. this cause value should not be received. CS FALLBACK An UE camping on E-UTRA may be moved by the eNB by using the following procedures: UE connection release by requesting the UE to select a UTRA network.6 • CORE NETWORK IMPACTS Support of the Gn Interfaces: SGSN–MME and SGSN-P_GW. 2. The CS fallback data flows are described in [A9].12. SRNS relocation from E-UTRA to UTRA followed by a CS Rab Assignment.7 1.UMTS Radio Mobility NO: incoming relocation requests from 4G are rejected 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. cipheringEnabled) FromEutraRelocationCiphering RadioAccessService Class3 4. These procedures have no impact on the UTRA.06/EN Approved_Standard 17/Sep/2010 Page 77/244 .12. A specific Ranap cause is created in Ranap Rel8 “CS fallback triggered”. as the Iu is based on Rel 7. 3. MME will map S1AP "CSFB Triggered" to the RANAP "Relocation Triggered. Passing on or copying of this document.5 • • • ACCESS NETWORK IMPACTS 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 4. 4. Enum( cipheringDisabledRejected. In UA07. it has no way to improve the CS establishment by postponing some procedures.

the SRNC decides to hand the UE over another cell controlled by another RNC and using another frequency (f2). At some point. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1 DESCRIPTION GENERAL The purpose of this mobility case is to allow user mobility between cells of different frequency. 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 Passing on or copying of this document.13. as the UTRAN RRC connection anchor point is moved from one RNC to another. in the 2 following cases: • inter-PLMN mobility • intra-PLMN mobility between 2 frequency layers In the example below.1 4.13.UMTS Radio Mobility 4. being controlled by different RNC not connected to an Iur. inter-frequency inter-RNC hard handover makes use of the Relocation procedure (UE involved).13.1. e. the mobile is using 2 radio links from NodeB0 and NodeB1. controlled by the SRNC. MSC Iu SRNC MSC RNC Iub NodeB 0 NodeB 1 NodeB 2 f1 Target radio link f2 UE Figure 42: inter-frequency inter-RNC handover As described in the following flow diagram.g. This may be used.06/EN Approved_Standard 17/Sep/2010 Page 78/244 . INTER-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR 4.

Number of Iu instances. the target RNC allocates UTRAN resources corresponding to the requested RABs NBAP/ Radio Link setup req NBAP/ Radio Link setup resp AAL2/ ERQ AAL2/ ECF RANAP/ Relocation request ack ( Radio Bearer Reconfiguration) Figure 43: inter-frequency inter-RNC handover . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.relocation preparation Passing on or copying of this document.06/EN Approved_Standard 17/Sep/2010 Page 79/244 . a request for relocation is issue by the serving RNC. When accepted. RAB parameters) On reception of Relocation Request. 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 RANAP/ Relocation required (RB parameters. Number of Iu instances) SCCP/ Connection Request SCCP/ Connection Confirm RANAP/ Relocation request (RB parameters.UMTS Radio Mobility UE Serving NodeB Serving RNC Target NodeB Target RNC CS CN node Based on the inter-PLMN handover criteria.

a new RNTI is allocated to the mobile. RANAP/ Relocation command (Radio Bearer Reconfiguration) RRC/ Radio Bearer reconfiguration (RB to reconfigure. the Alcatel-Lucent target RNC tries to identify the Radio Bearer configuration which is the closest to the requested configuration. 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. Passing on or copying of this document. Release) RRC/ Measurement Control (id2. In case there is no matching configuration (i. Release) … RRC/ Measurement Control (id1.e.UMTS Radio Mobility Relocation execution UE Serving NodeB Serving RNC Target NodeB Target RNC CN node During the relocation execution phase.06/EN Approved_Standard 17/Sep/2010 Page 80/244 . the Alcatel-Lucent target RNC deletes every measurement configured previously in the source RNC once relocation is successfully performed. and new measurements are setup by the new SRNC. Setup) RRC/ Measurement Control (id2. • Regarding measurement configuration.relocation execution Remarks: • From the RELOCATION REQUEST messages received. RRC/ Measurement Control (id1. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. All the needed measurements are then setup. Physical channel configuration) RRC/ Radio Bearer reconfiguration complete RANAP/ Relocation detect RANAP/ Relocation complete Old measurement Ids are released. integrity (and possibly) ciphering are activated. Setup) … 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 RANAP/ Iu release command NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp AAL2/ REL AAL2/ RLC RANAP/ Iu release complete SCCP/ Released SCCP/ Release Complete Figure 44: inter-frequency inter-RNC handover . This is all done through the Radio Bearer Reconfiguration RRC procedure.

19.13.13.2 MEASUREMENTS CONFIGURATION Please refer to section 4.19.g. There is no support for blind handover.13. the handover is aborted.5 Name PARAMETERS Object/Class RadioAccessService Class3 is3Gto3GWithoutIurAllowedForPS is3Gto3GWithoutIurAllowedForCS RadioAccessService Class3 Definition YES: incoming or out-going interfrequency alarm handover is allowed for PS domain RAB NO: incoming or out-going interfrequency alarm handover is not allowed YES: incoming or out-going interfrequency alarm handover is allowed for CS domain RAB NO: incoming or out-going interfrequency alarm handover is not allowed Refer also to Section 4. HS-DSCH or E-DCH.3.3 TARGET CELL CHOICE In this version of the document.1 ALGORITHM HO DECISION PROCESS Please refer to section 4. 4. outgoing inter-frequency handover inter-RNC is triggered upon iMCTA decision (refer to section 4.13. 4.19. 4.19. meaning that a target cell for inter-frequency handover as described in this section has to be a cell reported by the mobile.13.UMTS Radio Mobility 4.13. 4. Passing on or copying of this document. The feature is applicable for calls on DCH.06/EN Approved_Standard 17/Sep/2010 Page 81/244 . In case of CS+PS handover.2 APPLICABILITY In this version.3.3. with check of global activation parameters isHsdpaHHOwithMeasAllowed and isEdchHHOwithMeasAllowed. the mobile fails to synchronise on the target cell) there is no second try or other try to a second best eligible cell. the target cell choice decision is based on inter-frequency measurements from the mobile.19). use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.3 4. 4.13. and this cell has to fulfill the process described in section 4. This algorithm is applicable to PS. possibly using compressed mode.4 FAILURE CASES In case the inter-frequency handover is not successful (e. CS and CS+PS connections. if the handover fails for one of the domains.

• The Iur interface provisioned between 2 RNCs is not in an operational state.2 APPLICABILITY The feature is applicable for calls on DCH. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1 ALGORITHM 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. It may be used e.6 • • • ACCESS NETWORK IMPACTS Support for out-going/incoming relocation to/from 3G for PS. the existing outgoing and incoming relocation procedures (UE involved) are invoked to execute the HHO.13. When all the conditions are met.1 for detailed description).14.06/EN Approved_Standard 17/Sep/2010 Page 82/244 .3. INTRA-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR 4. It is applicable to all RABs combinations.7 • CORE NETWORK IMPACTS Support for the relocation procedure in PS and CS domain 4. with check of global activation parameters isHsdpaHHOwithMeasAllowed and isEdchHHOwithMeasAllowed. It is applicable in full-event mode only.14. and they have set up national roaming agreements between them • In a single PLMN.g. where it’s not possible to communicate via Iur between two RNCs controlling cells of the same frequency. 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. 4. in following situations: • Two different operators (PLMN) are using the same frequency in the same geographical area. 4. This status is checked only when receiving measurement reports and its change does not affect measurement configuration. e. Passing on or copying of this document.g.UMTS Radio Mobility Section 6.3 4. HS-DSCH or E-DCH.14.13. CS and CS+PS services Support of inter-frequency compressed mode scheme Support for inter-frequency measurements 4.13. for IOT reasons between two RNCs from different manufacturers. but controlled by a different RNC without Iur. Once the intra-frequency inter-RNC HHO condition is met.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. the procedure is exactly the same as for an inter-freq inter-RNC HHO (refer to § 4.6.

and if the Iur interface is disabled. if all activation parameters allow it.14. 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).UMTS Radio Mobility 4. 4. if all activation parameters allow it. a SHO cannot occur. it is configured at the same time as other events 1x with measId = 1. a new intra-frequency measurement is introduced.1 HO DECISION 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.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. If needed. no handover (neither HHO or SHO) is attempted. 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.4). Otherwise. no handover (neither HHO or SHO) is attempted. then a HHO with this target cell is decided.3.4 PARAMETERS Object/Class RadioAccessService Class3 RadioAccessService Class3 IntraFreqTargetCellP arams (DlUserService) Class 3 IntraFreqTargetCellP arams (DlUserService) Class 3 FullEventRepCritHho MgtEvent1AWithoutI ur (MeasurementConfCl Definition Indicates if the intra-frequency inter-RNC HHO is allowed if Iur Link is down indicates if the intra-frequency inter-RNC HHO feature is enabled or disabled CPICH Ec/No threshold for intrafrequency cell eligibility in HHO case CPICH Rscp threshold for intrafrequency cell eligibility in HHO case Amount of periodical reporting when triggered by intraFreqinterRnc Event in Full Event Mode Name isIntraFreqInterRncHhoOnIurLinkDownAllo wed isIntraFreqInterRncHHOAllowed minimumCpichEcNoValueForHHO minimumCpichRscpValueForHHO amountRep Passing on or copying of this document. 4.06/EN Approved_Standard 17/Sep/2010 Page 83/244 . It is configured with specific parameters (refer to § 4.3. 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.3.14.3. then a HHO with this target cell is decided. a SHO cannot occur.3. CIO is used.14.14. Otherwise. 4.14.2 MEASUREMENT CONFIGURATION In order to separate SHO from HHO conditions.14.3. In that case. In that case.3 4.

06/EN Approved_Standard 17/Sep/2010 Page 84/244 . RNC f1 f2 Passing on or copying of this document. It is related to the conditions for the change of Primary Radio Link Reporting Range to configure for the triggering condition of the intraFreq-interRnc Event in Full Event Mode 4.7.15.14.15.13.1 DESCRIPTION GENERAL This mobility case applies to Multilayer deployment in a single operator.6.13.14.15.1.1 4. 4.5 ACCESS NETWORK IMPACT Refer to § 4.6 CORE NETWORK IMPACT Refer to § 4. 4. INTER-FREQUENCY INTRA-RNC HANDOVER 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.UMTS Radio Mobility ass) Class 3 FullEventRepCritHho MgtEvent1AWithoutI ur (MeasurementConfCl ass) Class 3 FullEventRepCritHho MgtEvent1AWithoutI ur (MeasurementConfCl ass) Class 3 FullEventHoConfHh oMgtEvent1AWithou tIur (UsHoConf) Class 3 FullEventHoConfHh oMgtEvent1AWithou tIur (UsHoConf) Class 3 repInterval Interval between 2 similar reports for amount reporting mgmt of intraFreq-interRnc Event in Full Event Mode maxNbReportedCells Maximum number of reported cells to configure in Reporting Cell Status for intraFreq-interRnc Event in Full Event Mode timeToTrigger hysteresis cpichEcNoReportingRange FullEventHoConfHh oMgtEvent1AWithou tIur (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 to configure for the triggering condition of intraFreqinterRnc Event in Full Event Mode.

the subscribers remain on same frequency. a new radio link is set up on the new target NodeB. the Radio Link Addition. 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. or belong to different NodeB. In the second step. Setup or Deletion is performed over the Iur interface Passing on or copying of this document.15. an alarm hard handover towards the other frequency is triggered by the SRNC. However. using another frequency. e.06/EN Approved_Standard 17/Sep/2010 Page 85/244 .UMTS Radio Mobility Figure 45: Hard Handover inter-frequency intra-RNC In this case. f1 and f2 cells may be either 2 sectors of the same NodeB. the RNC control cells from different frequencies (f1 and f2). the Radio Bearer is re-configured and the old radio links (there may be more than one. as in the figure below. 4. as UE are moving out of the smallest frequency spot (f1 as in the picture above). Similarly.2 OVER THE IUR The source and/or target cell may be controlled by another RNC.g. UE NodeB 1 RRC/ Measurement Report NBAP/ Radio Link Setup req NBAP/ Radio Link Setup resp Serving RNC 1 FP/ DL Sync (CFN) FP/ UL Sync (ToA) RRC/ Radio Bearer Reconfiguration RRC/ Radio Bearer Reconfiguration complete NodeB 0 NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp 2 Figure 46: Hard Handover inter-frequency intra-RNC dataflow In the first step.1. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. NodeB 0 and NodeB 1 may be the same network node. an inter-frequency intra-RNC hard handover may also be performed from f2 to f1 in case of lack of f2 coverage. as in an “outdoor to indoor” mobility case. SRNC DRNC f1 f2 Figure 47: Hard Handover inter-frequency intra-RNC – over the Iur In such a case. In the figure above. depending on the current active set) are deleted.

In step (3) the old radio links (there may be more than one. using another frequency. The radio link belonging to the previous primary cell is to be deleted over Iur as depicted in figure above.06/EN Approved_Standard 17/Sep/2010 Page 86/244 .UMTS Radio Mobility UE Drift NodeB1 RRC/ Measurement Report Drift RNC Serving RNC RNSAP/ Radio Link Addition req NBAP/ Radio Link setup req NBAP/ Radio Link setup resp RNSAP/ Radio Link Addition resp (Binding Id) AlCAP Iur Transport Bearer Setup 1 AlCAP Iub Transport Bearer Setup FP/ DL Sync (CFN) FP/ DL Sync (CFN) FP/ UL Sync (ToA) FP/ UL Sync (ToA) RRC/ Radio Bearer Reconfiguration RRC/ Radio Bearer Reconfiguration Complete 2 UE Drift NodeB0 Drift RNC Serving RNC RNSAP/ Radio Link deletion req NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp AlCAP Iub Transport Bearer Release 3 RNSAP/ Radio Link deletion resp AlCAP Iur Transport Bearer Release 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. In step (2) the Radio Bearer is reconfigured. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Drift NodeB 0 and Drift NodeB 1 may be the same network node. depending on the current active set) are deleted. In the figure above. Passing on or copying of this document.

inter-frequency hard handover intra-RNC is triggered upon iMCTA decision (refer to section 4. The following restriction applies: In case the target cell is located on a D-RNC. the RNC will process a HHO through Iur after processing a reconfiguration towards DCH in case the call was established in HSPA.5 (is3Gto3GWithoutIurAllowedForPS and is3Gto3GWithoutIurAllowedForCS).19.5 (isInterFreqHandoverOverIurAllowed).06/EN Approved_Standard 17/Sep/2010 Page 87/244 .15. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.15.13) will be initiated towards the same target cell if the relocation is enabled according to section 4.5 PARAMETERS Intra DRNC handover will be enabled/disabled by the parameter defined in section 4. the RNC will process a SRNS Relocation "UE involved".3. This algorithm is applicable to PS.19). The Radio criteria algorithm for inter-frequency intra-RNC handover uses the same parameters with the same values as in the inter-RNC case.3. Passing on or copying of this document. 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. If the parameter isInterFreqHandoverOverIurAllowed is true.16.4 FAILURE CASES In case the inter-frequency handover is not successful (e. There is no new parameter associated to the “intra-RNC case” exclusively. However for intra DRNC handover a relocation procedure (refer to section 4.2 APPLICABILITY In this version.15.15.15. 4.3 4.15..g. 4.1 ALGORITHM HO DECISION PROCESS Please refer to section 4.2 MEASUREMENTS CONFIGURATION Please refer to section 4. CS and CS+PS connections. 4.15.13.UMTS Radio Mobility 4. 4.19. The RNSAP RL Addition procedure does not permit to reconfigure the DCH part of the call. the mobility procedure depends on the parameter isInterFreqHandoverOverIurAllowed: If the parameter isInterFreqHandoverOverIurAllowed is false.3. the mobile fails to synchronise on the target cell) there is no second try or other try to a second best eligible cell.3 CHOICE OF TARGET CELL Please refer to section 4. 4.19.

NeighbRnc Attempted outgoing inter-frequency hard handovers due to insufficient RSCP quality of the used frequency HHO.AttOutInterFreq / HHO.RSCP / HHO. 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.15.SuccOutInterFreq.SuccOutInterFreq. 4. 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.AttOutInterFreq.SuccOutInterFreq. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.EcNo.AttOutInterFreq.SuccOutInterFreq. 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. (CN is completely transparent to this procedure).13).RSCP. 4.RSCP.EcNo.EcNo / HHO.NeighbRnc Attempted outgoing inter-frequency hard handovers due to insufficient Ec/No quality of the used frequency HHO.16.06/EN Approved_Standard 17/Sep/2010 Page 88/244 .AttOutInterFreq.EcNo / HHO. INTER-FREQUENCY INTER-RNC HANDOVER WITH IUR AND MEASUREMENTS In release UA05. Iur is not used for that type of handover.NeighbRnc Total number of successful outgoing inter-frequency hard handovers HHO.15.AttOutInterFreq.NeighbRnc Successful outgoing inter-frequency hard handovers due to insufficient Ec/No quality of the used frequency • • • • The counters are of cumulative type.15.6 • • ACCESS NETWORK IMPACTS Support of inter-frequency compressed mode scheme Support for inter-frequency measurements 4.NeighbRnc Successful outgoing inter-frequency hard handovers due to insufficient RSCP quality of the used frequency HHO. – In UA07. We use SRNS Relocation “UE involved” instead (refer to § 4.SuccOutInterFreq / HHO.RSCP / HHO. Passing on or copying of this document.SuccOutInterFreq.AttOutInterFreq.8 PERFORMANCE MANAGEMENT The following counters are defined: • • HHO.NeighbRnc Total number of attempted outgoing inter-frequency hard handovers HHO.7 CORE NETWORK IMPACTS None.UMTS Radio Mobility 4.

16.06/EN Approved_Standard 17/Sep/2010 Page 89/244 . 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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.16.1. 4. SRNC DRNC f1 f2 Figure 49: Hard Handover inter-frequency inter-RNC – from SRNC to DRNC Passing on or copying of this document.16.1.1 4.1 DESCRIPTION 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.UMTS Radio Mobility 4.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.

4.06/EN Approved_Standard 17/Sep/2010 Page 90/244 .16. Passing on or copying of this document.1. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. In step (2) the Radio Bearer is reconfigured. 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. 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. using another frequency.UMTS Radio Mobility UE Drift NodeB1 RRC/ Measurement Report Drift RNC Serving RNC RNSAP/ Radio Link Setup req NBAP/ Radio Link setup req NBAP/ Radio Link setup resp RNSAP/ Radio Link Setup resp (Binding Id) AlCAP Iur Transport Bearer Setup 1 AlCAP Iub Transport Bearer Setup FP/ DL Sync (CFN) FP/ DL Sync (CFN) FP/ UL Sync (ToA) FP/ UL Sync (ToA) RRC/ Radio Bearer Reconfiguration RRC/ Radio Bearer Reconfiguration Complete 2 UE NodeB0 Serving RNC NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp 3 AlCAP Iub Transport Bearer Release 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. In step (3) the old radio links (there may be more than one.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.

UMTS Radio Mobility SRNC DRNC 1 DRNC 2 f1 f2 Figure 51: Hard Handover inter-frequency inter-RNC – from DRNC to DRNC UE Serving RNC Drift NodeB1 RRC/ Measurement Report Drift RNC 2 RNSAP/ Radio Link Setup req NBAP/ Radio Link setup req NBAP/ Radio Link setup resp RNSAP/ Radio Link Setup resp (Binding Id) AlCAP Iur Transport Bearer Setup 1 AlCAP Iub Transport Bearer Setup FP/ DL Sync (CFN) FP/ DL Sync (CFN) FP/ UL Sync (ToA) FP/ UL Sync (ToA) RRC/ Radio Bearer Reconfiguration RRC/ Radio Bearer Reconfiguration Complete 2 UE Drift NodeB0 Drift RNC 1 Serving RNC RNSAP/ Radio Link deletion req NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp AlCAP Iub Transport Bearer Release 3 RNSAP/ Radio Link deletion resp AlCAP Iur Transport Bearer Release 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. Passing on or copying of this document.06/EN Approved_Standard 17/Sep/2010 Page 91/244 . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.

There is no need for HSxPA to DCH reconfiguration. In step (3) the old radio links (there may be more than one. depending on the current active set) are deleted.06/EN Approved_Standard 17/Sep/2010 Page 92/244 . The radio link belonging to the previous primary cell is to be deleted over Iur as depicted in figure above.UMTS Radio Mobility In step (2) the Radio Bearer is reconfigured. If the call is HSxPA then it can be handed over directly with HSxPA being kept. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. SRNC DRNC f1 f2 Figure 53: Hard Handover inter-frequency inter-RNC – from DRNC to SRNC UE NodeB 1 Drift RNC RRC/ Measurement Report NBAP/ Radio Link Setup req Serving RNC NBAP/ Radio Link Setup resp 1 AlCAP Iub Transport Bearer Setup FP/ DL Sync (CFN) FP/ UL Sync (ToA) RRC/ Radio Bearer Reconfiguration RRC/ Radio Bearer Reconfiguration complete 2 Passing on or copying of this document.1.16.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. 4.

4. This algorithm is applicable to PS. When the target cell is on D-RNC. 4.1 ALGORITHM HO DECISION PROCESS Please refer to section 4.16.16.UMTS Radio Mobility UE Drift NodeB0 Drift RNC Serving RNC RNSAP/ Radio Link deletion req NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp AlCAP Iub Transport Bearer Release 3 RNSAP/ Radio Link deletion resp AlCAP Iur Transport Bearer Release 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. The radio link belonging to the previous primary cell is to be deleted over Iur as depicted in figure above. inter-frequency hard handover inter-RNC is triggered upon iMCTA decision (refer to section 4.16.2 APPLICABILITY In this version.3.19. whatever the location of the current active set. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.16. In step (3) the old radio links (there may be more than one. In step (2) the Radio Bearer is reconfigured. the RNC will process a SRNS Relocation "UE involved".15.3 4. If the parameter isInterFreqHandoverOverIurAllowed is true.3. 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.19).19. using another frequency.2). CS and CS+PS connections. depending on the current active set) are deleted. Passing on or copying of this document. This radio link is to be setup directly over Iub without Iur being involved. 4. the mobility procedure depends of the isInterFreqHandoverOverIurAllowed parameter value: If the parameter isInterFreqHandoverOverIurAllowed is false.2 MEASUREMENTS CONFIGURATION Please refer to section 4.06/EN Approved_Standard 17/Sep/2010 Page 93/244 .

4.16. the mobile fails to synchronise on the target cell) there is no second try or other try to a second best eligible cell.06/EN Approved_Standard 17/Sep/2010 Page 94/244 .17.16. Used for both intra and inter RNC HHO.5 PARAMETERS Object/Class Neighbouring RNC Definition Indicates if inter-frequency HHO over Iur is allowed. handover from SRNC to DRNC or handover from DRNC to DRNC) a relocation procedure (refer to section 4.15.1 See [R8].16.UMTS Radio Mobility 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.5.19. Name isInterFreqHandoverOverIurAllowed 4.8 do apply for the inter RNC scenarios as well.8 PERFORMANCE MANAGEMENT The counters listed in section 4.4 FAILURE CASES In case the inter-frequency handover is not successful (e. DESCRIPTION Passing on or copying of this document.16. 4.3 CHOICE OF TARGET CELL Please refer to section 4. The relocation is rejected and the call stays up.16.7 CORE NETWORK IMPACTS None.16.3. SRNS RELOCATION – “UE NOT INVOLVED” Warning: SRNS Relocation “UE not involved” can be rejected when UA7. 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. 4.6 • • ACCESS NETWORK IMPACTS Support of inter-frequency compressed mode scheme Support for inter-frequency measurements 4. However if the target cell is on a DRNC (i.13) will be initiated towards the same target cell if enabled according to section 4.e. (CN is completely transparent to this procedure).1 SRNC is sending r7 RRC extensions which are not handled by the UA6 TRNC.g. 4.17.13.

18.6 See [R8]. 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.17.4 See [R8].5 See [R8]. Passing on or copying of this document.1 REDIRECTION AT CONNECTION SETUP (IMCRA STEP 1) DESCRIPTION Mobiles in idle mode will select a layer according to radio conditions.06/EN Approved_Standard 17/Sep/2010 Page 95/244 . PARAMETERS 4.18. 4. ACCESS NETWORK IMPACTS 4. APPLICABILITY 4. CORE NETWORK IMPACTS 4. ALGORITHM 4.UMTS Radio Mobility 4. If overload criterion is fulfilled (=rach is filtered before attempting CAC) no redirection applies. Before calling redirection features the overload function is processed. The following features may trigger a redirection: • HSPA traffic segmentation (feature 27932) and its evolution redirection during RRC connection setup (75069/81213). 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). • 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.17.1 4.17.17.1.3 See [R8].18.2 See [R8].17.

RRC Cnx Request (AS Release Indicator = R4 or absent) 2. Following description explains the RRC traffic segmentation/redirection during RRC connection setup feature. The UE is redirected to the other layer (f2). the call is established normally. frequency info=freq f2) RRC/ RACH / RRC connection Request (cause) RRC/ FACH / RRC Connection Setup (DCCH.06/EN Approved_Standard 17/Sep/2010 Page 96/244 . RRC/ RACH / RRC Connection Setup Complete 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. U-RNTI. RRC Cnx Setup (redirection -> f1) f2 : HSDPA layer f1 : non-HSDPA layer 1. normally in the twin cell but not necessarily. RRC state = CELL_FACH. the dataflow is the same as without redirection. RRC Cnx Request (AS Release Indicator = R5) Figure 55: Example of Redirection at RRC establishment UE Node B – twin cell RRC/ RACH / RRC connection Request (cause) RNC SGSN 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 RRC Connection Setup message contains the signalling bearers (DCCH) definition. RRC Cnx Setup (redirection -> f2) 2. UE Node B RRC/ RACH / RRC connection Request (cause) RRC/ FACH / RRC Connection Setup (DCCH. On this second request. except that resources are reserved in the twin-cell and that the mobile is redirected thanks to the frequency info IE. U-RNTI. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. RRC state = CELL_DCH. RRC state = CELL_FACH) RNC SGSN The RRC Connection Request message initiated by the UE contains the establishment cause. The RRC connection request is sent again in the new cell.UMTS Radio Mobility 1. Primary CPICH info = f2 cell Frequency info = twin cell frequency) RRC/ RACH / RRC Connection Setup Complete Figure 56: redirection from f1 to f2 with establishment done in Cell_DCH For establishment in Cell_FACH. The Primary CPICH info corresponds to the CPICH of the twin cell (frequency f2) The response is received on the twin cell (f2) RRC/ FACH / RRC Connection Setup (DCCH. U-RNTI. Passing on or copying of this document.

e. • When the HSPA “R99 preferred” layers are loaded.2 APPLICABILITY Mobiles are redirected to the right layer at RRC connection establishment. 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. 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’).18. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1. redirection is performed by iMCTA. The segmentation is done by the RNC when a mobile tries to establish an RRC connection.06/EN Approved_Standard 17/Sep/2010 Page 97/244 .1 INTERACTION WITH CELL_FACH: If a UE in Always-On on Cell_FACH reselects another layer. The segmentation is done only at the RRC Connection establishment. it may be redirected to the right layer by iMCTA when traffic resumes.g. due to automatic carrier switch-off.2. using “the follow-on” indicator at the end of the Location Update.2. For ‘Originating High Priority Signalling’ cause. In this case.18. Only in case that the RRC establishment fails on the originating cell due to CAC Passing on or copying of this document. 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.1.2. the HSPA calls are assigned to HSPA “pure” layers whatever their load. using the cause ‘Registration’.1. More information is provided in Annex L of 24.1. For all cells with layerPreferredForR99 = TRUE the RNC assumes HSPA Cell Capability = DCH. then the RNC evaluates the FDDCell parameter layerPreferredForR99 of the originating and all operational twin cells.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.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.UMTS Radio Mobility 4. The RRC redirection procedure uses a list of candidate twin cells (if no twin cell is operational then redirection is not triggered). no DCH cell. During the call. this is useful if R99 carriers get unavailable e.008. 4. the call will also be set up in the originating cell.18. If isHspaCellLoadAllowedForImcra = FALSE and if the originating cell as well as all operational cells contained in the twinCellList are either HSDPA or HSUPA capable. the mobile uses the same RRC connection for the Location Update and the RAB establishment. Especially. 4. 4. The RNC determines the HSPA cell capability as follows: HSPA Cell Capability DCH HSDPA Cell Configuration hsdpaActivation = FALSE 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. The establishment cause ‘Registration’ will be set up in the originating cell.18. i.

1.red2BlackHSPACodesDlLoadThreshold .yellow2RedHSPAPwrDlLoadThreshold . TotalHsdpaUsedSF16: The minimumnumber of SF16 codes that are allocated in use for HSDPA in one cell calculated based on HSDPA GBR. HSUPA load is not evaluated in current release.06/EN Approved_Standard 17/Sep/2010 Page 98/244 .red2YellowHSPAPwrDlLoadThreshold .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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. This is an integer value. The HSDPA load is calculated from DL power and DL code: Dl power load formula: HSPA_dl_power_load = 1 . yellow. For HSDPA load four load colors are supported: green.18.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).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 .Black2RedHSPAPwrDlLoadThreshold • HSPA DL Codes Color: Calculated ‘HSPA dl codes Load’ and the color transitions defined by parameters . Note that a code block consists of a number of successive SF16 codes.1.4 HSPA LOAD Since UA07.red2YellowHSPACodesDlLoadThreshold .green2YellowHSPAPwrDlLoadThreshold . 4.TotalHsdpaUsedSF16) / 16 SizeBiggestSf16Pool: Variable introduced by UA06 feature 33694: The number of free codes in the largest SF16 code block. Dl code load formula: HSPA_dl_codes_load = 1 .Black2RedHSPACodesDlLoadThreshold • DL HSPA load = max (HSPA DL Power Color.yellow2RedHSPACodesDlLoadThreshold .2 the HSDPA load is considered for HSPA I/B calls by iMCRA load based decisions if enabled via parameter isHspaCellLoadAllowedForImcra.red2BlackHSPAPwrDlLoadThreshold . red.yellow2GreenHSPACodesDlLoadThreshold . HSDPA MinBR and HSDPA I/B without MinBR (mib value).green2YellowHSPACodesDlLoadThreshold .yellow2GreenHSPAPwrDlLoadThreshold .2. HSPA DL Codes Color) Passing on or copying of this document. 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 .

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.5 INITIAL POWER ON REDIRECTION Typcially.3 ALGORITHM The operator has the choice between five algorithms for target carrier FA (= Frequency Allocation) selection. it is redirected to the HSDPA layer. UE Release UE capability indication HSPA UE capability (potential or real) Selected Target FA R99/R4 >= R6 R5 >= R6 >= R6 n/a absent n/a HS-DSCH HS-DSCH + E-DCH DCH Preferred target FA is DCH cell HSDPA Preferred target FA is HSDPA cell 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: Passing on or copying of this document. 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.UMTS Radio Mobility 4.2. knowing that R99/R4 mobiles do not support HSDPA. Power is not reduced if the load in the target is lower than in the originating cell. If a R5 (or later release) mobile sends its connection request in the non-HSDPA layer.1. it is redirected to the non-HSPDA layer in the RRC Connection Setup message.18. 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. 4. 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.1. If a R99/R4 mobile sends its connection request in the HSDPA layer.3.06/EN Approved_Standard 17/Sep/2010 Page 99/244 .1 REDIRECTION TYPE = UE CAPABILITY ONLY It is based on the Access Stratum Release Indicator IE present in RRC Connection Request.1.18.18. Since UA07. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. however. If.1. 4. the load in the target cell is higher then the usage of more power may be useful to ensure successful call establishment.

The Call Capability is the same as the UE Capability for this option. 2 nor 3 available Table 5: Applicable Cells Select 4 Select 5 if neither 2 nor 4 available Passing on or copying of this document. Search all cells in the twinCellList and originating cell. If there is no HSUPA cell then select HSDPA cell. Select cells which have compatible cell capability with UE capability or the fallback cells if no compatible cell found. 2 and 3 Select 4 and 5 if neither 1. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. RNC selects the target Cell with following procedure if isHspaCellLoadAllowedForImcra = TRUE: 1. If more than one cell is selected then select the cells with lowest cell color (Green < Yellow < Red). Else. 3. 3. If the originating cell color is equal or worse then go to next step. 2.06/EN Approved_Standard 17/Sep/2010 Page 100/244 .UMTS Radio Mobility Selected Target FA DCH HSDPA HSUPA Fallback if selected target FA is not available 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) If there is no HSDPA cell then select HSUPA cell. Cell Capability DCH Unloaded “R99 preferred” Loaded “R99 preferred” Unloaded “pure” HSPA Loaded “pure” HSPA DCH HSPA (HSDPA or HSUPA) Select 1 if neither 2. Call Capability # 1 2 3 4 5 With • An “R99 preferred” cell is loaded if o DCH load > twinCellTargetCellColourThreshold. 4. 4 nor 5 available Select 2 if 4 not available Select 3 if neither 2. If there is neither HSDPA nor HSUPA cell then select DCH cell. or o DL HSPA load > twinCellTargetHspaCellLoadThreshold • A “pure” HSPA cell is loaded if o DL HSPA load > twinCellTargetHspaCellLoadThreshold Note: The uplink load is ignored. from the remaining cells of the twinCellList the target cell is selected with round robin mechanism. Table 4: Target FA Fallback Different iMCRA behaviour applies dependent on whether HSPA load criterion is used or not. 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 more than one cell is selected: If the originating cell is one of the target cells then the UE should remain in originating cell. Select the applicable cells for redirection from the originating cell and its twin cells as per Table 5. 4 nor 5 available Select 1. If there is neither HSUPA nor HSDPA cell then select DCH cell. RNC selects the target Cell with following procedure if isHspaCellLoadAllowedForImcra = FALSE: 1.

The “R99 preferred” configuration is ignored because it was taken into account by step 1 already. 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. Call Capability HSDPA 1st Choice HSDPA 2nd Choice HSUPA HSUPA HSUPA HSDPA Table 6: Best fit Capability Table 7 defines the target capability dependent on Call and cell capability: Call Capability DCH <any> HSDPA HSDPA HSUPA HSUPA Cell Capability <any> DCH HSDPA HSUPA HSDPA HSUPA HSUPA Table 7: Target Capability HSDPA Target Capability DCH 3. For streaming calls the DCH load criterion and for other calls the load criterion as per Target Capability is applied. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. The originating threshold is dependent on the target capability (note: “R99 preferred” configuration is ignored here).UMTS Radio Mobility 2. Target Load Criterion for Establishment on Originating Cell Capability DCH DCH load < rrcRedirectOrigCellColourThreshold or streaming call HSPDA DL HSPA load < rrcRedirectOrigHspaCellLoadThreshold and UL DCH load < rrcRedirectOrigCellColourThreshold HSUPA Table 8: Load Criterion for Establishment on Originating Cell 4. 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 DCH or streaming call HSPDA HSUPA Load Comparison Select cells with lowest combined UL and DL DCH load 1st step: Select cells with lowest DL HSPA load 2nd step: Select cells with lowest UL DCH load Table 9: Load Comparison Passing on or copying of this document. 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 more than one cell is selected then select the cells with lowest cell color as per Table 9. If the originating cell color is equal or worse then go to next step.06/EN Approved_Standard 17/Sep/2010 Page 101/244 .

Passing on or copying of this document. Else.06/EN Approved_Standard 17/Sep/2010 Page 102/244 .as a second criterion for filtering. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.UMTS Radio Mobility 5. Following table gives the call type according to the establishment cause: Call Type Conversational Data RRC Establishment Cause Originating Conversational Call Terminating Conversational Call 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 causes Table 10: RRC Establishment Causes Other Then. 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. Background and Streaming traffic classes are mapped on HSDPA. knowing that only Interactive.3. so Conversational traffic class is redirected to the non-HSDPA layer. the preferred FA is chosen using both criteria: HSPA UE capability (potential or real) Call Type by Establishment Cause Call Capability DCH Conversational Data Other Conversational DCH cell Originating cell DCH cell HSDPA cell Originating cell DCH cell HSUPA cell Originating cell HSDPA Data Other Conversational HSUPA Data Other 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.18. from the remaining cells of the twinCellList the target cell is selected with round robin mechanism.1. REDIRECTION TYPE = UE CAPABILITY AND ESTABLISHMENT CAUSE 4. 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). 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.2 It is possible to use the traffic class –derived from the Establishment Cause IE.

The UE capabilities are not taken into account. Otherwise… 2. from the remaining cells of the twinCellList the target cell is selected with round robin mechanism.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.18.1. 5. 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 neither 'data' nor 'other' is available select 'conversational' Select every FA given in the referenced RrcRedirectionConfClass Table 12: Preferred FA Data Other If a single FA is selected then the RNC establishes the call in the twin cell of this FA. Otherwise… 1. If neither 'conversational' nor 'other' is available select 'data' Select FAs with faType set to 'data'. If more than one cell is selected then select the cells with lowest cell color (Green < Yellow < Red). 3. If no 'conversational' FA is available then select FAs of type 'other'. The RNC determines the preferred FAs from the assigned RrcRedirectionConfClass and its contained list of FrequencyAllocation's as per Table 12. If the originating cell color is equal or worse then go to next step.06/EN Approved_Standard 17/Sep/2010 Page 103/244 . Select cells which have compatible cell capability with UE capability and RRC establishment cause or the fallback cells if no compatible cell found. Search all cells in the twinCellList and originating cell.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.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. Otherwise … If isHspaCellLoadAllowedForImcra = TRUE then the RNC follows the procedure for option “UE Capability Only“ from step 3 onwards. 2. 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. If the originating cell color is equal or worse then go to next step. Call Type Conversational Preferred FA Select FAs with faType set to 'conversational'. 4. Else. Passing on or copying of this document. 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. If no 'data' FA is available then select FAs of type 'other'. 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). Target FAs for that no cell is defined in the twinCellList are ignored.

UMTS Radio Mobility 3.1. 4.18.4 REDIRECTION TYPE = CAC If CAC failure occurred during SRB establishment on the originating cell then the RNC considers redirection to another cell. from the remaining cells of the twinCellList the target cell is selected 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. UE Node B RRC/ RACH / RRC connection Request (cause) RRC/ FACH / RRC Connection Setup (DCCH.5 REDIRECTION TYPE = NONE No traffic segmentation is performed. 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. The RNC selects the cells with lowest cell color from the twinCellList. 4. U-RNTI.5 PARAMETERS Redirection during RRC connection setup parameters: Name isRrcRedirectionInterFreq Object/Class RadioAccessService Definition Feature activation flag for interfrequency redirection on RRC connection setup. When receiving this second RRC connection request with the same cause within time T300*N300.) RRC/ RACH / RRC connection Request (cause) RRC/ FACH / RRC Connection Setup (DCCH. The redirection algorithm is configured on cell basis by parameter rrcRedirectionType rrcRedirectionType InterFreqHhoFddCell Passing on or copying of this document. ) RNC SGSN The RRC Connection Request message initiated by the UE contains the establishment cause. The call is established on the originating cell if possible.4 FAILURE CASES: It may happen that the UE can not synchronise on the new frequency. The RRC connection request is sent again in the originating cell The RNC does not try to redirect again and proceeds on this cell RRC/ RACH / RRC Connection Setup Complete Figure 58: redirection failure 4.1.18.3. then the RNC attempts call establishment in the originating cell. The UE is redirected to the other layer The UE fails to synchronise on the target layer. it will resend an RRC connection request in the same cell (except if it had to perform a cell reselection meanwhile)..18. U-RNTI. . 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.06/EN Approved_Standard 17/Sep/2010 Page 104/244 . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.18. This use case is also applicable to mobiles that do not support RRC redirection. 4.1.3.1.

If the cell color is equal to or above the threshold then RRC redirection to a twin cell is considered. Activation/deactivation of the use of the Pinit based on the ratio between Total Transmitted power used on originating cell and target cells.1.3 InterFreqHhoFddCell dlFrequencyNumber ulFrequencyNumber faType layerPreferredForR99 FrequencyAllocation (in RrcRedirectionConfClass MO) FrequencyAllocation (in RrcRedirectionConfClass MO) FrequencyAllocation (in RrcRedirectionConfClass MO) FDDCell Uplink UARFCN FA type (conversational. isHspaCellLoadAllowedForImcra UA07.2: RadioAccessService.2: RadioAccessService. It applies during RRC redirection procedure.reserved5 (byte0. due to automatic carrier switch-off. Especially. HSPA cell load criteria allowed or not in iMCRA. this is useful if R99 carriers get unavailable e. data. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. HSPA cell load indicator calculation and broadcasting.2: FDDCell.byte1. 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 Downlink UARFCN rrcRedirectOrigCellColourThreshold InterFreqHhoFddCell rrcRedirectOrigHspaCellLoadThreshold UA07. 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.UMTS Radio Mobility twinCellList InterFreqHhoFddCell List of up to 5 inter-frequency twin cells (co-located cells referenced by Cell Id) to which interfrequency RRC redirection is considered.g.1. other) Traffic segmentation on RRC establishment can be used to separate R99 and HSPA traffic onto different layers (parameter rrcRedirectionType).byte3) RadioAccessService isPinitRrcRedirectionAllowed UA07.byte2.06/EN Approved_Standard 17/Sep/2010 Page 105/244 . 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 rrcRedirectOrigCellColourThreshol d.1.reserved1 (byte2) bit 0 RadioAccessService Passing on or copying of this document. When allowed there is a dependency with several sub functions activations: NBAP measurements configuration. HSPA services number calculation.reserved0 (byte1) bit 2.

the more capacity is available. twinCellTargetCellColourThreshold UA07. The lower the value. i.2: FDDCell.reserved2 (byte0) bit 0.1.2: FDDCell.1.1. This parameter defines the threshold on HSPA Downlink power cell load to transition from yellow to red.reserved1 (byte3) bit 0.reserved1 (byte1) bit 4.6 HspaCellLoadParameters red2YellowHspaPwrDlLoadThreshold UA07. The lower the value.2: FDDCell. The lower the value.reserved1 (byte2) bit 0.1. i. the more capacity is available.e...reserved2 (byte1) bit 0. not available to a new user.6 FDDCell HspaCellLoadParameters yellow2GreenHspaPwrDlLoadThreshold UA07. This parameter defines the threshold on HSPA Downlink power cell load to transition from green to yellow. The lower the value.e.2: FDDCell.6 HspaCellLoadParameters Passing on or copying of this document. See also parameter layerPreferredForR99.6 HspaCellLoadParameters yellow2RedHspaPwrDlLoadThreshold UA07.. the more capacity is available.e. not available to a new user.reserved1 (byte1) bit 2. This parameter defines the threshold on HSPA Downlink power cell load to transition from yellow to green. This parameter defines the threshold on HSPA Downlink power cell load to transition from red to yellow.06/EN Approved_Standard 17/Sep/2010 Page 106/244 .6 HspaCellLoadParameters red2BlackHspaPwrDlLoadThreshold UA07. i.. The value indicates the percentage of the cell capacity being occupied.e.1. The value indicates the percentage of the cell capacity being occupied.reserved2 (byte2) bit 0.5 green2YellowHspaPwrDlLoadThreshold UA07. This parameter defines the threshold on HSPA Downlink power cell load to transition from red to black.UMTS Radio Mobility twinCellTargetHspaCellLoadthreshold UA07.. If all HSPA cells are overloaded then R99 preferred cells are considered for HSPA calls. The lower the value. the more capacity is available.2: FDDCell. The value indicates the percentage of the cell capacity being occupied. i. not available to a new user.1.e. The value indicates the percentage of the cell capacity being occupied.2: FDDCell. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. not available to a new user.2: FDDCell. not available to a new user.1. The value indicates the percentage of the cell capacity being occupied. iMCRA considers an R99 preferred FDD twin cell as overloaded if the R99 load is greater than this threshold. the more capacity is available.3 FDDCell iMCRA considers an HSPA cell as overloaded if the HSPA load is greater than this threshold. i.

. the more capacity is available.2: FDDCell.1.reserved2 (byte3) bit 0.. The lower the value.e.6 HspaCellLoadParameters This parameter defines the threshold on HSPA Downlink power cell load to transition from black to red. i. i.1.e.1.UMTS Radio Mobility black2RedHspaPwrDlLoadThreshold UA07.. not available to a new user.2: FDDCell. the more capacity is available.reserved0 (byte2) bit 0..6 HspaCellLoadParameters red2BlackHspaCodesDlLoadThreshold UA07. The lower the value.6 HspaCellLoadParameters black2RedHspaCodesDlLoadThreshold UA07.2: FDDCell.1.6 HspaCellLoadParameters Passing on or copying of this document. the more capacity is available.2: FDDCell.reserved3 (byte0) bit 0. not available to a new user. The value indicates the percentage of the cell capacity being occupied.e. the more capacity is available.reserved3 (byte3) bit 0.06/EN Approved_Standard 17/Sep/2010 Page 107/244 .e. The value indicates the percentage of the cell capacity being occupied.e. The lower the value.e.6 HspaCellLoadParameters yellow2RedHspaCodesDlLoadThreshold UA07. i. i. The value indicates the percentage of the cell capacity being occupied. the more capacity is available. 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.e. The value indicates the percentage of the cell capacity being occupied. not available to a new user. green2YellowHspaCodesDlLoadThresho ld UA07. The lower the value. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.2: FDDCell.. The value indicates the percentage of the cell capacity being occupied. The lower the value. This parameter defines the threshold on HSPA Downlink codes cell load to transition from black to red. not available to a new user.1. not available to a new user. i.reserved3 (byte1) bit 0. This parameter defines the threshold on HSPA Downlink codes cell load to transition from yellow to red. i.. the more capacity is available. i. The lower the value. This parameter defines the threshold on HSPA Downlink codes cell load to transition from red to yellow. not available to a new user.1. The value indicates the percentage of the cell capacity being occupied. The lower the value.6 HspaCellLoadParameters red2YellowHspaCodesDlLoadThreshold UA07.reserved0 (byte3) bit 0. the more capacity is available.2: FDDCell. This parameter defines the threshold on HSPA Downlink codes cell load to transition from red to black.2: FDDCell. not available to a new user..reserved3 (byte2) bit 0.1. This parameter defines the threshold on HSPA Downlink codes cell load to transition from yellow to green.6 HspaCellLoadParameters yellow2GreenHspaCodesDlLoadThresho ld UA07.

Passing on or copying of this document. 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.19). and fail. 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. o The UE did not release the RRC connection after the initial Location Update.2. 4. but they may be present in the future. If the neighbouring 2G cells (measurement based or blind) are not provisioned at the OMC-R. The UE will re-attempt the call setup (multiple times with increasing power each time). on the 2G network.UMTS Radio Mobility 4. The UE may choose to set the “follow-on request” indicator during the Location Update Request. or whether the UE supports GSM. RRC Redirection is not triggered for this scenario. these calls have already failed to establish on the 3G network. This includes: o Non-speech calls such as Video telephony. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. However.2. and contention will occur if the number of UEs attempting to access the 3G network exceeds a given threshold. Therefore. GSM may either simply fail the call or attempt to redirect the Video telephony back to 3G. Users may experience delays in accessing the network due to collisions on the RACH channel.2 3G2G REDIRECTION AT RRC ESTABLISHMENT FOR SPEECH CALLS DESCRIPTION 4. the call will fail. This could possibly be the case where the call is invoked very early after the UE is powered up. The resultant behaviour is not defined in the standards. This could be the case in the following scenarios: o A PS call is established prior to invocation of the speech call attempt. the end result is that the ability to redirect the call to 2G may not function in these cases. o RRC Redirection will not be triggered by the RNC if the UE already has an established RRC connection. 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. o Conversational calls on the PS domain.18. Call failures associated with RACH access are outside of the scope of this feature capability. and is used to allow the UE and CN to exchange subsequent Non Access Stratum (NAS) messages to allow the call to progress. o RRC will redirect all MO Conversational calls to 2G upon admission failure (irrespective of service type and domain). The RNC is unaware of the UE capabilities at RRC Connection Request time.18. the RNC will attempt an RRC Redirection irrespective of whether the UE supports the Redirection IE in the RRC reject message. however.06/EN Approved_Standard 17/Sep/2010 Page 108/244 . However.2 o o APPLICABILITY The redirection applies to calls with RRC Establishment cause equal to MO Conversational or Emergency. RRC Redirection is triggered by failures at this point in the call progression. o SRB Assignment: The SRB is established as a result of the first Access Stratum (AS) message being received by the RNC. even if RRC Redirection is enabled for that cell.1 The Redirection during the Rab Assignment processing is covered by the iMCTA function (refer also to § 4. and is in either the active state or AO Step 1 state. which will arrive. RRC Redirection will not be triggered in the RNC. The call would fail at the CN if a RRC Redirection is attempted. 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. There may be other cases where the UE will request the network to keep the RRC Connection established. but if the RACH access failure persists. having RRC Redirection enabled for a cell which has no 2G neighbouring cells provisioned is considered a configuration error. if it has a subsequent request pending. This is not currently the case.18. Therefore. and is not able to be modified.

such as Iub bandwidth exhaust (or Iur in the case of a DRNC scenario).g. Maximum UE Contexts: The RNC checks that the maximum number of concurrent UE contexts will not be exceeded. existing) RRC Connection Admission mechanism. This step is preceded by the location registration (not shown here). PID failure. the IE “GSM target cell info list” may be set for Rel6 UE if allowed (OAM parameter isGsmTargetInfoListAllowed). the same RRC cause value would be used for a Video Telephony call setup request. which could also trigger RRC Redirection.2. Step 2: The RNC will execute normal (i. In order to improve the 3G-2G HHO duration. the RNC will execute the RRC Redirection Enabling Criteria. the most likely failure scenario is Iub bandwidth exhaust.UMTS Radio Mobility 4. The RRC Connection Reject message will contain the Redirection info IE with Inter-RAT info set to “GSM”. based on the sum total of all RBs currently assigned to that resource (partitioned into DS and NDS traffic. 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. and the UTRAN is enabled to redirect speech calls to 2G.3 ALGORITHM The flow for RRC Redirection is shown in Figure 59: RRC Speech Redirection. While in this example the setup relates to a speech call setup. RRC/ FACH (RRC Connection Reject (Wait Time. This is a calculated capacity. PSFP) If failure occurs on any one of the above RRC admission controls. However. There is also a separate cause value for an emergency call request. PSFP) o Cell_FACH: Number of contexts on the FACH channel Internal RNC U-Plane resources (e. 1 2 If admission fails. SRB CAC: The RNC will check that the resources required to support the SRB are available.e. a RRC Connection Reject is sent to the UE with redirection info included.1). CID exhaust. Redirection info: GSM)) 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. UE Node B RNC The RRC Connection Request message initiated by the UE RRC/RACH (RRC connection Request (cause: MO Conv or Emergency)) contains the establishment cause. as of UA04.06/EN Approved_Standard 17/Sep/2010 Page 109/244 . The required resources are dependant on whether the setup is via Cell_FACH or Cell_DCH. RNC Overload: The RRC connection request may be denied based on the current RNC Overload level CAC. o Passing on or copying of this document. due to the throughput constraint of this physical connection. and is as follows: o Cell_DCH: Radio Resources (OVSF codes. The mobile station performs inter-system cell reselection and re-originates the speech call on the 2G network.g. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Internal RNC U-Plane resources (e.18. and PathGroup failure. DL Power) NodeB CEM AAL2 CAC: In this case there are several existing possible exhaust scenarios.

The Wait Time parameter will be set to the value associated with one of the following parameters: o timeReject. 4. 3G2G redirection for emergency call or 3G2G redirection based on cell load. o a static RNC value if the admission failure which causes the redirection is not ” overload”.4 PARAMETERS Object/Class RadioAccessService Class3 FDDCell Class3 RadioAccessService Class3 FDDCell Class 3 Name is3Gto2gConversationalCallRedirectOnRrcEs tabFailAllowed blindHoGsmNeighbourTargetCgi timeReject Definition This parameter enables the RRC Speech Redirection feature link to a GSMCell instance Wait time used when the redirection is due to RNC overload 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 . the UE is required to wait (at least) a predetermined time before the subsequent attempt on the 3G network.06/EN Approved_Standard 17/Sep/2010 Page 110/244 . This parameter allows using the R6 IE GSM Target Info List in the RRC Connection Reject message. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.UMTS Radio Mobility The UE cell selection is not a blind HO. and this up to N300 times. However. since the UE performs target GSM cell selection. 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). Two values: TRUE/FALSE TRUE: the IE may be used WaitTime3GTo2GRedirectFailure emergencyCallRepeatTime renamed rrcCnxRepeatTime RNC RadioAccessService ServiceInit isGsmTargetInfoListIeAllowed RNC RadioAccessService ServiceInit Passing on or copying of this document. 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. the Rach is managed as a first RRC establishment request. o waitTime3Gto2GRedirectFailure. If the reattempt occurs after the timer elapses or in a different Fdd cell. This wait time is sent by the RNC to the UE in the Wait Time IE in the RRC Connection Reject message. In the case where the 2G cell selection fails.2. 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).18. If the admission failure which causes the redirection is “RNC overload”. the UE will re-attempt a call in 3G.

UMTS Radio Mobility when a redirection towards GSM has to be processed. [USA Market . no specific treatment is applied by the RNC during call establishment. Current UMTS networks and/or UEs may not allow for a determination of the UE location with sufficient accuracy. • 3G-2G Emergency Redirection For specific needs related to UE positioning.3.3 4.18. 4. With "Immediate Handover of Emergency Calls" (see [R2] for details) this problem can be avoided by initiating handover to 2G after call establishment. it may be required by the operator to re-direct the UE initiating an emergency call to the 2G network. FALSE: the IE shall not be used when a redirection towards GSM has to be processed. Therefore no RRC Redirection is possible.or handed over after 3G call set-up] to the 2G GSM network. in order to utilize a location solution deployed in the operator’s 2G network. In order to take advantage of existing GSM location position solution that satisfies the FCC E911 Phase II requirements.3. the percentage of emergency calls processed by the RNC may be reduced. When the RNC is in an overload condition.In case the UE has an on-going PS call at the time the emergency call is attempted. emergency calls can be redirected on initial 3G call set-up [USA Market .18. 4.18.e.3.] The flow for RRC Redirection is shown in following figure: Passing on or copying of this document. [USA Market .06/EN Approved_Standard 17/Sep/2010 Page 111/244 . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. non-overload) conditions and if no re-direction to GSM is required (see section "3G-2G Emergency Redirection" below).2 APLLICABILITY Emergency calls are always mobile originated speech calls. 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. The call is handled as specified in the "MO call setup" section. The redirection is made upon reception of the RRC Connection Request message by the RNC (from the UE).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.3 ALGORITHM • Normal Case Under Normal (i. The effect of overload on emergency calls is provided in [R1]. then the emergency call establishment is not initiated with RRC Connection Request.emergencyCallPriorityLevel ] 4. UTRAN is aware that the call initiated by the mobile is an emergency call from the RRC establishment cause set to "Emergency call".1 EMERGENCY AND PRIORITY CALLS DESCRIPTION For emergency calls in some countries it is required to determine the location of the UE at call establishment.18.

On reception of the RRC Connection Reject message. the RNC will try to redirect again this call to the 2G network. The core network will then repeat the location reporting request to the GSM network. The call setup is considered as unsuccessful and there is no further RRC connection attempts tried by the mobile for this call. The UE performs GSM measurements and if a suitable GSM target cell is found within time interSystemHOe911Timer then the handover is initiated. as the RRC connection has already been established for the PS session. The directed retry for WPS calls can be enabled on RNC basis. Likely the redirection will fail again.4. On RAB Assignment the MSC indicates that the call is a priority call. 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 IE “GSM target cell info list” may be set for Rel6 UE if allowed (OAM parameter isGsmTargetInfoListAllowed). Redirection info: GSM)) 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 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. even if Redirection to 2G is configured for E911 calls.UMTS Radio Mobility UE Node B RNC MSC-CS RRC/ RACH (RRC connection Request (cause: Emergency Call)) The RRC Connection Request message initiated by the UE contains the establishment cause. To avoid endless loop preventing the E911 call to be setup. If the mobile fails the redirection and if the user re-attempts a new E911 call setup.] Special handling may apply also to priority calls. there is no possibility to re-direct the call to GSM. and as specified in [A4] (RRC specification): If WaitTime equals 0. 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).18.Immediate Inter-RAT Handover Radio access bearer resources are assigned in UMTS to allow for fast call establishment. 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. the UE shall not re-select a UMTS cell until WaitTime has expired.10. If the UTRAN is setup to re-direct emergency calls to 2G and if 2G neighbouring cells are available. Location reporting requests from the MSC are queued during this time and discarded in case of successful handover. Refer to [R13] for more details on specific emergency redirection.19 for a description of the CAC based handover algorithm). the mobile enters Idle Mode. the mobile shall: Perform GSM cell selection immediately In case of GSM selection failure. Otherwise. the call is processed as in "MO Call Setup". A filtering mechanism is also implemented in the RNC to discard Rach repetition within a certain period of time (Static parameter: repeatFilteringTime). otherwise. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. if WaitTime is different from 0. and the mobile will again enter idle mode. or NS/EP calls which terminate to a UMTS subscriber. Refer to § 4. If UTRAN is congested. In order to improve the 3G-2G HHO duration. Passing on or copying of this document.2 for redirection procedure. then the UTRAN initiates directed retry to GSM (see section 4. In case there is an on-going PS at the time the emergency call is attempted. An example is the Wireless Priority Service (WPS) in the US. if radio resource congestion occurs on the UTRAN.06/EN Approved_Standard 17/Sep/2010 Page 112/244 . which defines redirection to the GSM system of WPS calls which originate from a UMTS subscriber. a RRC Connection Reject is sent to the mobile. RRC/ FACH (RRC Connection Reject ( Wait Time. • [USA Market .

emergencyCallPrio RadioAccess The parameter identifies the 'Priority Level' of Emergency Call rityLevel Service bearer and is used to recognise the Emergency Call on receiving Class 3 RANAP Allocation/Retention Priority communicated by CN to RNC over Iu interface.disabled .g. From 0 to 15 seconds. interSystemHOe911 RadioAccess If a call is an emergency call and an immediate handover to Timer Service GSM should be performed.UMTS Radio Mobility 4. due to coverage reasons. An ongoing handover attempt is not aborted.06/EN Approved_Standard 17/Sep/2010 Page 113/244 .4 PARAMETERS Object/Class FDDCell Definition Activation flag to enable 3G to 2G redirection for emergency calls Name is3Gto2GRedirectF orEmergencyAllow ed WaitTime3Gto2GR edirectFailure Value for WaitTime IE sent to the mobile in case of re-direction to GSM.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.3. [USA Market] isWpsDirectedRetry Imcta If enabled Wireless Priority Service (WPS) calls are directed to Allowed Class 3 GSM if the UMTS cell is in congestion. rvice ServiceInit Two values: TRUE/FALSE TRUE: the IE may be used when a redirection towards GSM has to be processed. On expiry of this timer the attempt to revert the emergency call to GSM is aborted.inter system handover for all emergency calls . FDDCell Passing on or copying of this document. Following options are available: Class 3 .e. immediateHOofEm FDDCell / Indicates whether emergency calls should be handed over to ergencyCalls Neighbouring GSM using immediate Inter-System Handover after RAB [USA Market] RNC establishment or kept in UMTS.18. the call will be kept in UMTS but may be handed over to GSM at a later time e. then the RNC tries the handover for [USA Market] Class 3 the time interSystemHOe911Time. emergencyCallRepeatTime RNC Definition is updated: renamed rrcCnxRepeatTime RadioAccessService This is the maximum time between two ServiceInit 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). use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. isImmediateHOofE RadioAccess This parameter enables/disables the 'Immediate Handover of mergencyCallsAllo Service Emergency Calls to GSM' on a per RNC basis. On cell basis wed Class 3 further configuration options are available. The call will be handled like a normal call. The default value is 1 second. FALSE: the IE shall not be used when a redirection towards GSM has to be processed. isGsmTargetInfoLis RNC This parameter allows using the R6 IE GSM Target Info List in RadioAccessSe tIeAllowed the RRC Connection Reject message. i.

] • • • • • • • The following counters are available for "Wireless Priority Service": • RAB.IRATHO.5 • PERFORMANCE MANAGEMENT [USA Market -The following counters are available for "Immediate Handover of Emergency calls": RAB.WPS RAB Assignment Requests for Wireless Priority Service (WPS) calls.3.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.IRATHO.AttDirectedRetry Attempted CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls. This PM is only applicable for Emergency Calls. the call may queue for an idle trunk and/or a radio for up to 180 seconds.AttRRCHO The number of attempted handovers for Emergency Call Immediate Inter-System Handover (ECIHO). Applicable in the context of WPS calls. Only applicable for the context of "Emergency Call Immediate Inter-System Handover".IRATHO.IRATHO. This PM is only applicable for Emergency Calls.AttRelocPrep The number of attempted relocation preparations for Emergency Call Immediate Inter-System Handover (ECIHO).ECIHO. only.18. VS.ECIHO.ECIHO. VS.IRATHO.06/EN Approved_Standard 17/Sep/2010 Page 114/244 .SuccHO The number of successful Emergency Call Immediate Inter-System Handovers (ECIHO). This measurement is pegged only if WPS handling is enabled in the RNC. 4.ECIHO.IRATHO. Number of RAB Assignment Requests for Wireless Priority Service (WPS) calls. VS. 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. Only applicable for the context of "Emergency Call Immediate InterSystem Handover".SuccEstabCSV.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.ECIHO. When a directed retry handover of a WPS call is attempted.AttHO This PM counts the number of Emergency calls for that an Immediate Inter-System Handover is attempted.3g2gOutHoFailure Number of failed outgoing CS IRAT Handovers from 3G to 2G VS. Only applicable for the context of "Emergency Call Immediate Inter-System Handover". VS.WPS. VS. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.EC This PM counts the number of RAB Assignment Requests for Emergency Calls. VS. VS.AttEstabCSV. Only applicable for the context of "Emergency Call Immediate InterSystem Handover". Only applicable for the context of "Emergency Call Immediate Inter-System Handover". Only applicable for the context of "Emergency Call Immediate Inter-System Handover".AttEstabCSV.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. Number of • • Passing on or copying of this document.IRATHO. If the timer expires the RNC will abort the Relocation Preparation procedure by initiating the Relocation Cancel procedure.ECIHO.EC This PM counts the number of Successful RAB Establishments for Emergency Calls. RAB.

only. only.4.CancelHO Cancelled WPS CS IRAT Directed Retry attempts.IRATHO.CancelRelocPrep Cancelled WPS CS IRAT Directed Retry Relocation Preparations. Applicable for the context of WPS call Directed Retry. They are defined as two sets. • Code load.18.18. Applicable for the context of WPS call Directed Retry. • RTWP load of the ul DCH + non scheduled E-DCH. 4.WPS.IRATHO.WPS Attempted CS IRAT relocation preparations of CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls.IRATHO. 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. Passing on or copying of this document. only. VS. 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.WPS.18.1 3G2G REDIRECTION BASED ON CELL LOAD DESCRIPTION This feature enables 3G/2G RRC redirection of CS Speech calls when the cell load on the originating UMTS cell reaches a configurable threshold. VS.IRATHO. Definitions of the load indicator are given in [R7]. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. VS.AttHO Attempted CS IRAT handovers of CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls. 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).IRATHO.4. • • • • The counters are of cumulative type. • VS. The number of WPS calls for that the Directed Retry is cancelled by normal call release during ongoing relocation preparation procedure. VS. Description: Applicable in the context of Directed Retry for WPS calls. only. Applicable in the context of Directed Retry for WPS calls. streaming or I/B DCH is taken into account.06/EN Approved_Standard 17/Sep/2010 Page 115/244 . Applicable in the context of Directed Retry for WPS calls. only. • Downlink power load.4 4. • Call type IE (Rel6)= “CS speech”.WPS.WPS. The worst load color of the different indicators is taken into account and compared with a threshold (redirection3G2GOnCellLoadThreshold parameter) dedicated to this feature.2 APPLICABILITY 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”. • Iub dl load: the max elementary Iub color among the load color conversational.UMTS Radio Mobility attempted CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls.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. 4.AttRelocPrepOutCS. only.

4. 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.UMTS Radio Mobility The call type is a R6 IE.3 ALGORITHM The flow for RRC Redirection is shown in Figure 61: RRC Redirection. 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).06/EN Approved_Standard 17/Sep/2010 Page 116/244 . It may induce the redirection of a video telephony service. Note 2: 2G load is not taken into account to take the decision to trigger the redirection. Passing on or copying of this document. The interaction with other RRC redirection features is given in 4. 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”.5. For UE with a release up to R5. is above or equal to the cell 3G2G redirection load threshold (redirection3G2GOnCellLoadThreshold OAM parameter) ( • 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 = “Originating Conversational Call”. It allows differentiating a speech call from a video telephony call.4.18. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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). call type IE is not present and a CS speech service or a CS video telephony cannot be differentiated. Otherwise it is not needed. Note 3: A load threshold equal to “green” may be used to redirect all candidate RRC connection request towards the 2G.18. • OR • OR • • ) 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. On RRC Connection Setup request message receipt the criterion to a redirect the call towards 2G is: • AND • AND • AND • AND • The feature is activated on this FDD cell (is3G2GRedirectOnCellLoadAllowed OAM parameter) The Rach is not a repeated Rach The current FDD cell has neighboring GSM cells configured (see Note 1) The 3G2G redirection load color of the cell receiving the RACH or of the twin cell if traffic segmentation applies.

A value around 30 sec is recommended. 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.18. 1 2 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 RRC/ FACH (RRC Connection Reject (Wait Time. a filtering mechanism is implemented in the RNC to discard Rach repetition within a certain period of time (Static parameter: repeatFilteringTime).06/EN Approved_Standard 17/Sep/2010 Page 117/244 . If no GSM cell fulfills the selection criteria. The UE may camp on the same Fdd cell or another Fdd cell (the cell reselection process may change the Fdd cell . Redirection info: GSM)) Figure 61: RRC Redirection On receipt of the RRC connection request. 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. the UE will re-attempt a new RACH towards the UTRAN after the “wait time” timer (UE timer) has elapsed.18. If the re-attempt occurs after the timer elapses or in a different Fdd cell. the redirection criterion described in 4. Passing on or copying of this document.UMTS Radio Mobility UE Node B RNC The RRC Connection Request message initiated by the UE RRC/RACH (RRC connection Request (cause: MO Conv or Emergency)) contains the establishment cause. When the re-attempt occurs in the same Fdd cell within a certain period of time (RrcCnxRepeatTime OAM parameter). after applying the priority between all RRC redirection features (see 4.2 is checked. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. As for feature 3G/2G redirection enhancement for 911 calls. The UE has to wait 10 sec (3GPP static value) before starting a new search among all GSM cells.5). 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.4. the Rach is managed as a first RRC establishment request. 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) Rel 6) o BCCH ARFCN o Band Indicator o BSIC (IE Upon receiving this message. [UA06-UA07 difference]:The feature reuses the EmergencyCallRepeatTime parameter created by the feature 3G/2G redirection enhancement for 911 calls and renames it: “RrcCnxRepeatTime”.

18.4 New parameters: PARAMETERS Parameter is3G2GRedirectOnCellLoadAllowed MO RNC NodeB FDDCell Class 3-A2 is3G2GRedirectOnCellLoadAllowedForEmergency RNC RadioAccessService 3-A2 is3G2GRedirectOnCellLoadAllowedForR99AndR5 RNC NodeB FDDCell 3-A2 Definition Enables the feature when the Rach concerns a normal or emergency CS speech call . 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. yellow.4. The Definition is updated: see 4.UMTS Radio Mobility 4. Already used by feature 3G/2G redirection enhancement for 911 calls.2. redirection3G2GOnCellLoadThreshold RNC NodeB FDDCell 3-A2 isGsmTargetInfoListIeAllowed RNC RadioAccessService ServiceInit 3-A2 [UA06-UA07 difference]:Parameters modified: Parameter waitTime3Gto2GRedirectFailure MO RNC NodeB FDDCell Class 3-A2 emergencyCallRepeatTime renamed rrcCnxRepeatTime RNC RadioAccessService ServiceInit 3-B Definition Already used by feature 3G/2G redirection for emergency calls. red) When the cell load color is higher or equal to this threshold. Definition is updated: This is the maximum time between two Emergency call or CS speech call attempts from the same UE (where Passing on or copying of this document. Enables the feature when the Rach concerns an emergency CS speech call. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. the 3G2G redirection feature may apply.06/EN Approved_Standard 17/Sep/2010 Page 118/244 . Enum (green.18. Enables the feature when the Rach conerns a UE with a release strictly below R6. This parameter allows using the R6 IE GSM Target Info List in the RRC Connection Reject message.4.

2 ALGORITHM Following table gives the interworking between all the above features: 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.5 PERFORMANCE MANAGEMENT [UA06-UA07 difference]:Counters modified: RRC.5.1 PRIORITY BETWEEN RRC REDIRECTION FEATURES DESCRIPTION The interaction between the different redirection features are described in the following section 4.4.18. Counter added: VS.RRC_ConnectionReAttempt. 4. 4.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).5. See [A14] for more details.06/EN Approved_Standard 17/Sep/2010 Page 119/244 .FailConnEstab.18.5 4.18.18.

Note: If the load of the selected twin cell is not available.06/EN Approved_Standard 17/Sep/2010 Page 120/244 . CORE NETWORK IMPACTS Passing on or copying of this document. CSV is normal speech or emergency call 2. and . From release UA07. a “red” default color is used for this cell in order to disfavor it: a 3G2G redirection will be launched. For consistency.the call attempt is for an emergency call.1.18. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 4.6 ACCESS NETWORK IMPACTS Support of admission control and RRC Redirection procedures. 4. RRC attempt after callp filtering mechanism 3. the feature has to be activated in all Fdd cells of the RNC. Reference cell for load check including related OA&M parameters and for call establishment 5.2G neighbours configured 4.2 feature 75069 is enhanced by feature 81213.18. and .7 None.UMTS Radio Mobility # RRC attempt emergency first <any> repeated <any> repeated Call Type 1 2 13451 25145 (emergency) (CAC) active <any> <any> <any> <any> <any> <any> <any> <any> <any> inactive inactive inactive inactive inactive inactive inactive inactive inactive inactive <any> <any> <any> <any> <any> <any> <any> <any> <any> <any> enabled enabled 3 34480 (load) <any> <any> <any> <any> <any> <any> <any> <any> <any> 75069 / Reference 81213 Cell <any> originating <any> originating <any> originating disabled originating enabled selected by 75069 disabled originating enabled selected by 75069 disabled originating enabled 4 Cell Load of reference cell <any> below CAC CAC failure below CAC below CAC CAC failure CAC failure below 34480 load CAC ok below 34480 load CAC ok above 34480 load CAC ok above 34480 load CAC ok above 34480 load above 34480 load below 34480 load CAC failure below 34480 load CAC failure CAC failure CAC failure Result Redirect to 2G triggered by 25145 RRC establishment in reference cell Reject RRC establishment or 33322 to trigger pre-emption in reference cell RRC establishment in reference cell RRC establishment in reference cell Reject RRC establishment or 33322 to trigger pre-emption in reference cell Reject RRC establishment RRC establishment in reference cell RRC establishment in reference cell RRC establishment in reference cell RRC establishment in reference cell Redirect to 2G triggered by 34480 Redirect to 2G triggered by 34480 Redirect to 2G triggered by 13451 Redirect to 2G triggered by 13451 Reject RRC establishment or 33322 to trigger pre-emption in reference cell Reject RRC establishment non-CSV non-CSV non-CSV non-CSV CSV CSV CSV CSV CSV CSV CSV CSV CSV CSV first first first first first first first first first first first first first first selected by 75069 disabled disabled originating disabled enabled enabled enabled <any> <any> selected by 75069 disabled originating enabled selected by 75069 disabled originating enabled selected by 75069 disabled disabled disabled originating disabled disabled enabled selected by 75069 Table 13: Feature Interactions Notes: 1. Feature 25145 is active if .25145 is enabled in originating cell.

06/EN Approved_Standard 17/Sep/2010 Page 121/244 . no related functionality available in UA7.1 For Hard Handover: please see section 4.2 • • • • APLICABILITY In the release UA07.19.PS I/B g .PS I/B + 2 PS I/B SRB + PS I/B b SRB + PS I/B + PS I/B + PS I/B d e h + PS I/B 4 2 .2 SRNS Relocation: please refer to section 4.PS I/B a 5 1 f + 2 PS I/B + PS I/B + PS I/B 3 .1.19. 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.PS I/B SRB + PS I/B + PS I/B .1 DESCRIPTION From mobility perspective.3 The interactions inducing some changes on the procedure described above are highlighted in the sub-section: 4. the table below summarizes the possible transitions that can be performed.19.2.2 (PLM decision) For Soft Handover / Primary Link Change: please see section 4.PS I/B SRB + PS I /B + PS I/B Dual Cell Conditions fulfilled Dual Cell Conditions not fulfilled Only dotted arrows are applicable to Trial Sc ope Call is On Single Carrier Call is On Dual Carrier Example of transitions for Dual Cell Hsdpa Operation Passing on or copying of this document. SRB .19. DUAL CELL HSDPA OPERATION 4.19.3.3. 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.UMTS Radio Mobility 4. 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.3.19.1.2 PS I/B 6 c .

1 ALGORITHM SOFT HANDOVER ACTIVE SET UPDATE Active set updates are possible for the anchor carrier.19. E-DCH Active Set o No special handling is needed for DC operation in case of E-DCH active set change. are kept without modification. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. event 1d. Normal HSPA behaviour applies. 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.3 4. R99 to HSDPA DC case Successful Operation If for a R99 call the primary link changes then a reconfiguration to HSPA may get triggered .3. Therefore active set updates do not change the DC configuration.2 DC operation has no influence on the decision to perform Primary Link Change (PLC).3. The RNC includes the IE "Downlink secondary cell info FDD" in the RRC message RADIO BEARER RECONFIGURATION.19.UMTS Radio Mobility 4. only. 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.this is existing functionality. The existing criteria for primary link change. The NodeB shall reply with NBAP message RADIO LINK RECONFIGURATION FAILURE and include the cause value "Multi Cell operation not available". The RNC considers the reconfiguration to HSPA DC as successful on reception of RRC message RADIO BEARER RECONFIGURATION COMPLETE. only. e. Note: If non-serving NodeBs are part of the active set then these are already configured at this time.1.1.3. • • Links over IuR o No special handling is needed for DC operation on active set update over IuR. Passing on or copying of this document. As part of the reconfiguration to HSPA for DC capable UEs the RNC checks DC applicability of the new cell. RNC 9370 handles primary cell change and active set update as separate procedures. PRIMARY LINK CHANGE 4.g. For this the RNC appliesthe existing R99 to HSPA reconfiguration procedure. 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. If DC is applicable then the RNC enhances the reconfiguration to HSPA by inclusion of the secondary cell information.06/EN Approved_Standard 17/Sep/2010 Page 122/244 .1 4.19.19. DC operation affects the primary cell.

For this the RNC applies the existing serving cell change procedure.06/EN Approved_Standard 17/Sep/2010 Page 123/244 . Passing on or copying of this document. Notes: In case of inter-NodeB serving cell change the old serving NodeB is already configured at this time.this is existing functionality.and intra-NodeB serving cell change. 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: • • • 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. 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. 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.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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. The RNC includes the IE "Downlink secondary cell info FDD" in the RRC message RADIO BEARER RECONFIGURATION. The NodeB shall reply with NBAP message RADIO LINK RECONFIGURATION FAILURE and include the cause value "Multi Cell operation not available". Same procedure applies for inter. In case of intra-NodeB serving cell change the new serving NodeB is also the old serving NodeB. The existing failure handling is the reconfiguration to R99. 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 . 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. Thus. As part of the serving cell change for DC capable UEs the RNC checks DC applicability of the new cell. this will remove the DC configuration in the NodeB. a new RADIO LINK RECONFIGURATION PREPARE with SC HSPA configuration must be sent to the new serving NodeB only.

The RNC does not know if the failure was caused by the DC configuration or any other reason. The new serving NodeB shall include the IE "Additional HS Cell Information Response" in the NBAP message RADIO LINK RECONFIGURATION READY. 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. The existing failure handling is the reconfiguration to R99. 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: • • • HS-PDSCH RL ID C-ID HS-DSCH FDD Secondary Serving Information 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: • • • HS-PDSCH RL ID C-ID HS-DSCH FDD Secondary Serving Information 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". As part of the serving cell change for DC capable UEs the RNC checks DC applicability of the new cell.this is existing functionality. 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. this will remove the DC configuration in the NodeB. 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: Passing on or copying of this document. no changes required for DC.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. 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 . As part of the serving cell change for DC capable UEs the RNC checks DC applicability of the new cell.06/EN Approved_Standard 17/Sep/2010 Page 124/244 . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. The RNC includes the IE "Downlink secondary cell info FDD" in the RRC message RADIO BEARER RECONFIGURATION.

i.1. then the RNC applies the existing failure handling for serving cell change. only. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Unsuccessful Operation In case of failure.19.3.1.3.2 only SRB over DCH is supported. the existing functionality applies. 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.3.SRB over HSPA". • PLC from DRNC to SRNC triggers reconfiguration to DC if applicable.e.06/EN Approved_Standard 17/Sep/2010 Page 125/244 . the RNC receives message RADIO LINK RECONFIGURATION FAILURE or RADIO BEARER RECONFIGURATION FAILURE. 4. • PLC to DRNC implies reconfiguration to single cell. SRB over HSPA is planned for UA08 with feature 29810 "Fractional DPCH .4 SRB ASPECTS In UA07.1. e.19. The RNC verifies the E-DCH capability of the new primary link as one of the pre-conditions for DC-HSDPA operation.19.5 IUR ASPECTS DC operation over Iur is not supported in this release then. 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. 4.6 MESSAGING NBAP The RNC uses NBAP message RADIO LINK RECONFIGURATION PREPARE for serving HS DSCH cell change. The RNC considers the serving cell change with SC target as successful on reception of RRC message RADIO BEARER RECONFIGURATION COMPLETE.1. Note: It is not required to include IE "HS-DSCH Secondary Serving Remove" in the NBAP message to the old serving NodeB. 4.19.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: Passing on or copying of this document. 4.3 UPLINK ASPECTS In this release DC-HSDPA is supported with E-DCH in the uplink. The new serving NodeB is configured as SC with the existing procedure.1.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 "HSDSCH MAC-d Flows To Delete".3.g. The RNC is able to handle DC mobility procedures with SRB over DCH.

In case of serving HS-DSCH cell change with DC enabled in target configuration. call remains on DC NBAP message: One instance of IE "Additional HS Cell Information RL Reconf Prep" with following sub-IEs: • HS-PDSCH RL ID • C-ID • HS-DSCH FDD Secondary Serving Information d) PLC inter-NodeB. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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". 4. the RNC includes the IE "Downlink secondary cell info FDD" in RRC message RADIO BEARER RECONFIGURATION. 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: • 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 SETUP RESPONSE. e) PLC with reconfiguration from DC to R99: will behave as the existing reconfiguration messages without any specifics for DC.1 HARD HANDOVER 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. RRC The RNC uses RRC message RADIO BEARER RECONFIGURATION for serving HS-DSCH cell change.06/EN Approved_Standard 17/Sep/2010 Page 126/244 . If DC is applicable then the RNC applies DC configuration on the target cell.2. In case of serving HS-DSCH cell change with DC disabled in target configuration.19.3. Passing on or copying of this document. c) PLC intra-NodeB.UMTS Radio Mobility • • • HS-PDSCH RL ID C-ID HS-DSCH FDD Secondary Serving Information 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".19.2 4. the RNC omits the IE "Downlink secondary cell info FDD" in the RRC message RADIO BEARER RECONFIGURATION.3.

In case the RNC receives a RADIO BEARER RECONFIGURATION FAILURE message the RNC applies the existing failure handling for HHO. 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.19. In case of unsuccessful operation the call either has dropped or continues on the old (DC) configuration without any specific action. Note: In case of successful operation the source active set is deleted and it is not important if the configuration was SC or DC.3. 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. 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. 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. to a R7 compliant configuration. For SRNS Relocation of 3GPP R8 UEs the SRNC shall use the R7 transparent container.3. Passing on or copying of this document. 4.3 SRNS RELOCATION This feature does not introduce the R8 transparent container for SRNS Relocation. UE involved and UE not involved the target RNC requests the UE capabilities.2.19. Note: The RNC does not know if the failure was caused by the DC configuration or any other reason. and • reply on NBAP with message RADIO LINK SETUP FAILURE with failure cause "Multi Cell operation not available".06/EN Approved_Standard 17/Sep/2010 Page 127/244 . 4. i.3. The existing failure handling includes the deletion of the new radio links on NBAP. Note: Reconfiguration to SC is required because R8 transparent container is not supported.UMTS Radio Mobility The RNC includes the IE "Downlink secondary cell info FDD" in the RRC message RADIO BEARER RECONFIGURATION. this will remove the DC configuration in the target NodeB. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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.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. 4. For this the SRNC shall: • • reconfigure DC calls to SC.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.3.19.e.

• 3) HSDPA Single Cell to HSDPA Dual Cell. The NodeB shall apply the same compressed mode algorithm to anchor and supplementary carrier. it shall reject this RL Setup with failure cause "Multi Cell operation not supported".20. Hot spots. • 4) HSDPA Dual Cell to R99 Cell. • 2) HSDPA Dual Cell to HSDPA Single Cell. Addition or Reconfiguration with HS-DSCH Secondary Serving Information IE. 4. • 3) HSDPA Single Cell to HSDPA Dual Cell. the SRNS Relocation "UE not involved" is not directly affected by DC in this release. • If DRNC receives RNSAP message RL Setup. Note: No separate NBAP compressed mode commands are required for the supplementary carrier.HsdpaMobilitySuccess Description: Number of successful HSDPA Dual Cell mobility described by the following screenings: • 1) HSDPA Dual Cell to HSDPA Dual Cell. Service partitioning. There is a need to distribute the traffic between the different layers including 2G (GSM) layers. 4.331 section 8.3.19.4. • 5) R99 Cell to HSDPA Dual Cell. Passing on or copying of this document. INTELLIGENT MULTI CARRIER TRAFFIC ALLOCATION (IMCTA) To increase the network capacity. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. then the NodeB has to apply the same compressed mode configuration with same timing on the supplementary carrier. operators may deploy multi layer configurations with several layers structures: Multi layers with equal coverage. UE speed.3.3.4 COMPRESSED MODE As per 3GPP 25.3 some UEs might not require compressed mode for measurements on adjacent frequencies . • 5) R99 Cell to HSDPA Dual Cell. 4. The traffic distribution strategy may be based on load balancing.4 PARAMETERS No new parameters have been dedicated specially to the mobility aspects. 4.21 for the UE measurement capability information. • 4) HSDPA Dual Cell to R99 Cell.HsdpaMobilityUnsuccess Description: Number of unsuccessful HSDPA Dual Cell mobility described by the following screenings: • 1) HSDPA Dual Cell to HSDPA Dual Cell.06/EN Approved_Standard 17/Sep/2010 Page 128/244 .see also 3GPP section 10.19.3.UMTS Radio Mobility 4.19. Name: VS. But there are some related aspects that need to be handled as detailed below. micro cells Hierarchical cells structure.5 PERFORMANCE MANAGEMENT The following counters have been added Name: VS.1. the dual cell hsdpa operation feature needs to be activated.2 UE NOT INVOLVED During SRNS Relocation "UE not involved” the call is on single cell because DC is not supported over IuR. • 2) HSDPA Dual Cell to HSDPA Single Cell. Carrier redirection preferences and mobility triggers. Reference Cell is new primary cell of call. please refers to [R6] for this purpose. When the NodeB for a UE with DC call applies compressed mode to the anchor carrier.19.3. But. Reference Cell is new primary cell of call. Thus.

the mobile type (i.20. It includes the Alarm Handover.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. HSDPA. HSUPA capable or not).e. For a given call. A fallback to another Carrier may be done. the service type.20. 4. A CAC reason: a CAC failure occurs during the processing of a Rab Assignment sent by the CN. the redirection triggers and the cells load. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1 IMCTA TRIGGERS The main reasons to invoke the iMCTA function are: Alarm condition is hit. Passing on or copying of this document.06/EN Approved_Standard 17/Sep/2010 Page 129/244 .1 DESCRIPTION IMCTA function allocates traffic across available carriers. 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. 2G R99 R5 FDD2 HSDPA/HSUPA R5 FDD1 non HSXPA Figure 62: Service Redirection application R5 FDD2 HSDPA/HSUPA R5 R5 R5 FDD1 HSDPA/HSUPA Figure 63: Load balancing application 4.1. The iMCTA function is managed by the RNC. The iMCTA function covers this network evolution.

06/EN Approved_Standard 17/Sep/2010 Page 130/244 . The triggers are valid if the originating cell (i. The iMCTA is invoked if the final state of the call is: one or several Traffic Rab are established. using origin cell load colour threshold different from green. iMCTA applies in case of Rab Assignment procedure inducing a successful fallback on DCH when no HSDSCH resource is available. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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. A mobility service reason: A successful Intra Freq mobility is done but mobile may be moved to a better Carrier. primary cell) is eligible regarding its load level. a HSxPA to DCH fallback may be attempted. 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 Alarm and CAC triggers apply even if the primary cell is managed through Iur.9. 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 mobilityServiceForHsxpaEnable O&M attribute set to True. iMCTA trigger: Alarm HO reason The Alarm criterion for Inter Frequency and the Inter Rat Handover is described in section 5.UMTS Radio Mobility A user service reason: A successful Rab establishment/modification/release. The trigger is a primary link cell change with the new primary cell configured with mobilityServiceForNonHsxpaEnable O&M attribute set to True. If the fallback faces up a CAC failure or may not apply. iMCTA may be called.e. 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. When a CAC failure occurs during a Rab Assignment towards HSxPA. The triggers are valid if the originating cell (i. IU: Transport Resource allocation failure From RNC Uplane: Resource allocation failure From C-RNC: User Plane Dedicated Bearer allocation failure. 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).e. iMCTA doesn’t apply to IRM table reject cases. 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. i.e. The User and mobility Service triggers don’t apply if the primary cell is managed through Iur. 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. This trigger belongs to “Service” triggers. 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 EDCH. After a mobile performs a successful Always On upsize from Cell_FACH or URA/Cell_PCH to Cell_DCH. a Always On upsize or an IU Release Command is done but the mobile may be moved to a better Carrier. has not to be used if we want no limitation of the redirection application. Passing on or copying of this document. Incoming Relocation with one or several Traffic Rab. primary cell) is eligible regarding its load. IUR. a Rab release or a modification of the established Traffic type.

Passing on or copying of this document.UMTS Radio Mobility If service segmentation is activated. iMCTA works with up to six UMTS carriers1.e. 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. a HSxPA to DCH fallback may be attempted. 4. plus a 2G layer (whatever the frequencies).1.06/EN Approved_Standard 17/Sep/2010 Page 131/244 .2. apply in decreasing priority order: • Fallback to DCH • iMCTA • preemption (refer to [R12]) 4.2 CROSSOVER BETWEEN IMCTA TRIGGERS OR WITH OTHERS PROCEDURES When the RNC waits for iMCTA measurements for a given trigger.20. 1 As per 3GPP [A7] UEs are required to support the own carrier and two additional FDD carriers. In case of CAC failure. the measurement period is stopped and re-started with the new neighbouring. o User or Mobility Service triggers = Primary cell change or Service modification. o Priority Rule between iMCTA triggers and others procedures: o Alarm/CAC triggers > Primary cell change or Service modification. when User service or Mobility service trigger is used. Calls in Cell Fach (signaling or traffic). the load of the originating cell is not taken into account. E-DCH and HS-DSCH connected mode. following procedures. 4. no target cell identified) of the current period.2 APPLICABILITY The iMCTA function only applies to calls in Cell DCH.2 IUR MANAGEMENT Following tables gives the type of procedure executed according to the type of source/target cell and iMCTA trigger.2. If the target access changes.1 MANAGEMENT IN CELL HSXPA When a CAC failure occurs during a Rab Assignment towards HSxPA. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. If the fallback faces up a CAC failure or may not apply.20. o When the second event has a higher or equal priority than the previous with no target access change. 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. The following rules apply: o Priority Rule between iMCTA triggers: Alarm > CAC > User Service > Mobility Service. a Primary link modification or a Service modification may occur. if applicable.20. the Measurement period may be re-started after the expiration (i. Cell PCH or URA PCH connected mode are not managed. iMCTA may be called (see [R6]). a second iMCTA trigger.20.

CAC failure and directed retry The 3GPP allows Directed Retry via relocation for RAB CS establishment failure use case only towards 2G.20. the FDD target cell shall be managed by the S-RNC. 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.20. A 3G3G relocation is not supported in that case. • Intra frequency Radio Bearer Setup to add the new CS Rab. 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.2.UMTS Radio Mobility 4.2. if changing the Transport channel from HSxPA to DCH or vice-versa is needed.2.3 IMCTA TRIGGER = ALARM Passing on or copying of this document.2.20. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.2 IMCTA TRIGGER = CAC FAILURE Target cell S-RNC S-RNC Interfreq intraRNC HHO ok (1)(2) Interfreq interRNC HHO ok (2) D-RNC No HHO (no measurement started)(3) Source cell D-RNC No HHO (no measurement started)(3) (1) CAC failure and R5 mobiles: During intra RNC inter frequency HHO.2. modifying RLC information has to be processed.06/EN Approved_Standard 17/Sep/2010 Page 132/244 . For a Rel5 UE. when IMCTA CAC is hit and decision is made to launch an inter freq HHO.1 IMCTA TRIGGER = SERVICE Target cell S-RNC S-RNC Source cell D-RNC No HHO (no measurement started) (1) Interfreq intraRNC HHO OK D-RNC Interfreq InterRNC HHO ok if feature activated (with fallback to DCH before for HSPA calls). The Radio Bearer Release (and also Radio Bearer Setup) message provides this capability from Rel6. This is due to ciphering issue at UE side. 4. 3G3G relocation otherwise No HHO (no measurement started ) (1) (1) No service handover from D-RNC because load information not reliable 4. (3) CAC failure and 3G3G Relocation Upon CAC failure.2.

use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.3. 3G3G relocation otherwise 4. the redirection failed and the mobile stays with the PS established.2. 4.UMTS Radio Mobility Target cell S-RNC S-RNC Source cell D-RNC Interfreq intraRNC HHO ok Interfreq interRNC HHO ok D-RNC Interfreq InterRNC HHO ok if feature activated (with fallback to DCH before for HSPA calls).20. A 3GPP R2-062614 (release 6 Sept 2006) asks to support a HHO Inter Rat when a PS + CS signalling is established.2 IMCTA TRIGGER = CAC FAILURE RAB established on source cell Signalling Signalling Signalling + CS Signalling + PS RAB to establish CS PS PS CS RAB assignment failure (cause directed retry) + 2G interRAT HHO RAB assignment failure (cause unspecified) + 2G interRAT HHO (Cell Change Order)(1) RAB assignment failure for PS (cause unspecified) + 2G interRAT HHO for CS (1) 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.3. 3G3G relocation otherwise Interfreq IntraD-RNC or InterD-RNC HHO ok if feature activated (with fallback to DCH before for HSPA calls). iMCTA triggers a Directed Retry towards the 2G.20.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. If the UE doesn’t supports this use case. If the mobile doesn’t support this state. So ALU does the best effort policy: HHO is attempted.2. This use case is supported in 3GPP Rel 6 (Sept).06/EN Approved_Standard 17/Sep/2010 Page 133/244 .3 IMCTA TRIGGER = ALARM Passing on or copying of this document.20.1 IMCTA TRIGGER = SERVICE RAB established on source cell CS PS CS + PS 2G interRAT HHO 2G interRAT HHO (cell change order) 2G interRAT HHO (with/without PS reestablishement according to UE class) 4.2.20. (2) CAC failure and 3G2G Relocation: When a CAC failure occurs during the CS Rab establishment: • When a PS call is already established.3. the HHO ends by processing the failure case (call kept on the FDD access).2. 4.

2.3 4. a iMCTA blind HHO may be attempt to the 2G twin cell (if configured). iMCTA HHO processing or iMCTA exit .3. the function may process the following functional steps to identify a target cell on another Carrier: 1. Selection of the iMCTA Carrier priority table. no eligible target cell is found in the reported measurements. 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. 4.1 ALGORITHM MAIN FUNCTIONAL STEPS If one of the triggers is valid for the primary cell. 3. Configuration of the Compressed mode and of the UE measurements. when no Inter Freq/Inter Rat measurement can be requested to the mobile (compressed mode not allowed for the Service). Identification of the Service Type and RAB to be set.20.20.3 NEIGHBOUR CARRIERS SELECTION iMCTA is triggered for Service reason Passing on or copying of this document. Selection of the candidate Carriers. When the trigger is Service: o Originating cell load eligibility (if service segmentation not activated). 4.06/EN Approved_Standard 17/Sep/2010 Page 134/244 . For an alarm HHO trigger. 6. 5. 8.4 IMCTA LOAD BASED HO DEVELOPMENTS [USA MARKET] This feature is introduced in UA07. Cell selection upon Measurement Report.2 IMCTA FEATURE ACTIVATION The iMCTA feature activation is based on: mode O&M attribute value (see 4. Checking of the iMCTA feature activation parameters . If no target cell is found after iMCTA algorithm processing or no measurement received or the HHO failed.3. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 2. 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. 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.UMTS Radio Mobility RAB established on source cell CS PS CS + PS 2G interRAT HHO 2G interRAT HHO (cell change order) 2G interRAT HHO (with/without PS reestablishement according to UE class) 4.20.3.20.20. the RNC has to wait the next iMCTA trigger iteration for a new call redirection attempt. 7. 4. o mobilityServiceForHsxpaEnable and mobilityServiceForNonHsxpaEnable O&M attribute value.4). 4.1. 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.20. This feature by choosing the most suitable access (GSM or FDD) will decrease the handover failure rate during Handover algorithm. Selection of the candidate Cells for UE measurements.

3. 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). For each neighbour cells type (Inter Freq / Intra Freq / 2G). Whatever the iMCTA trigger (Alarm.UMTS Radio Mobility The Service priority table set by O&M (refer to 4. the cells are filtered (the Fdd carrier will not be monitored) from the neighbor cell list. the measurement capability is checked (i. Section 6. the iMCTA function is cancelled (step 8 is processed) when the triggering is for CAC or Service reasons.20.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. CAC or Service) the compressed mode activation and the measurements activation procedures are the same. 4. The carriers with a priority higher or equal to the current one are candidate for iMCTA target cells selection. Refer to: Section 6. • If GSM cells have the same priority as the Fdd cells with highest priority. In case of Alarm. 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 highest priority Fdd cells have a priority strictly higher than 2G cells.5) is sent to the mobile for measurement. mobility use case).4 NEIGHBOUR CELLS SELECTION FOR MEASUREMENT REPORTING When the candidate carriers are identified. Cells which must not be measured are discarded from the neighbour cells list. If the target cells list is empty. an iMCTA blind HHO may occur.20. o For CAC all DRNC cells are filtered if no SRNC cells are to be measured of that carrier. the iMCTA function is cancelled (step 8 is processed). the selection of the neighbour cells (see section 5. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.5 COMPRESSED MODE AND MEASUREMENT CONFIGURATION Inter Frequency and Inter RAT measurements are configured in periodic Mode. 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. all cells are kept. If the carriers list is empty. 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 . Passing on or copying of this document.20.2.3.e. 4. 2G cells are removed.e.06/EN Approved_Standard 17/Sep/2010 Page 135/244 .4. Fdd cells are removed. Compressed Mode applicability for the current service and UE capability).4) is read for the service type requested or in progress (i. 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).

The Radio criteria for target cell selection are the same whatever the trigger (Alarm.3. Preference is given to the cell with the best Radio level (Ec/No). Section 6.6 TARGET CELL SELECTION UPON MEASUREMENT REPORT 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.6. i. the cell is removed. An iMCTA criteria re-evaluation/evaluation is done (i. Passing on or copying of this document. Then if several 2G cells are eligible. c. Rate modification…) is in progress. 3. 2.g.re-attempt handover to this 2G cell.e.if found any . If a target cell (FDD or 2G) exists after applying the different filtering steps the HHO is processed. This re-attempt can be controlled with parameter isGsmIratHoToNextBestCellAllowed. 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). Then the neighbour cells not fulfilling the 2G cell color load criteria are filtered (see [iMCTA cell load criteria] section). 2. If FDD and 2G neighbour cells are eligible then the FDD target is selected if parameter is3GHandoverPreferred is set to TRUE or vice versa.20. Then if HSDPA traffic segmentation option (see [Parameters] section) is set to true. 4. The following paragraphs describe the target cell selection for each trigger type.e. the best measured cell which fulfills the Radio criteria is selected. Then if Service segmentation priority option (see [Parameters] section) is set to true. it’s the cell with the best Ec/No which verifies FDD HHO condition.4. 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. due to load conditions in the GSM cell.6.e. the following steps (with decreasing priority) are processed until retaining one cell: a.1 IMCTA TRIGGER IS SERVICE The following steps are processed to select a cell among the measured FDD neighbour cells: 1. Rab Assignment. Cell(s) belonging to the Carrier with the highest priority is kept. 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. If 2G is selected as target and the relocation preparation to the selected target cell fails. The cells which fulfill the Radio criteria are selected. the cell with the highest radio level is selected (Ec/No). their Rxlev verify 2G HHO condition. primary cell) load color (except if service segmentation has a higher priority). b. Service). CAC.5. Refer to: Section 6. 3. 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. Otherwise the RNC waits next measurement reports until the guard timer elapses.UMTS Radio Mobility 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1. 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. 5.1 for details). b. Any Inter freq or Inter RAT measurement due to iMCTA function received after the guard timer elapses is discarded. Then if several FDD cells are eligible. i. e.e.06/EN Approved_Standard 17/Sep/2010 Page 136/244 . The following steps are processed to select a cell among the measured 2G neighbour cells: 1. For each Carrier.3. Preference is given to the less loaded cell. Then the FDD cells are filtered according to the following rule: a.20.20. 4. then the RNC may re-evaluate the measurement report for the next best 2G neighbour cell and .

e.[USA Market . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. The less loaded cell is preferred.re-attempt handover to this 2G cell. 4. 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. Then if several FDD cells are eligible. The following steps are processed to select a cell among the measured neighbour 2G cells: 1. 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.6. 2.e. b) Preference is given to the less loaded cell. Preference is given to the cell with the best radio level (Ec/No).e. Note 2: A WPS call is not eligible to feature iMCTA load based HO developments. preference is given to HSUPA cells then HSDPA cells else if UE is HSDPA capable. due to load conditions in the GSM cell.20.3. their Rxlev verify 2G HHO condition.the best measured cell which fulfils the Radio criteria is selected. Note 3: The Iub load color is the load part attached to the QoS of the services to be established. [USA Market .g.3.the best measured cell which fulfils the Radio criteria is selected. This re-attempt can be controlled with parameter isGsmIratHoToNextBestCellAllowed. The cells fulfilling the Radio criteria are selected. i. then the RNC may re-evaluate the measurement report for the next best 2G neighbour cell and . preference is given to HSDPA cells.if found any .If iMCTA load based HO developments is activated: If no FDD cell is eligible.3). Note 1: the blind GSM cell is not used by iMCTA when the HHO reason is a CAC failure. If 2G is selected as target and the relocation preparation to the selected target cell fails.[USA Market . c) d) Preference is given to cell(s) belonging to the carrier with the highest priority. e. i.20. For each Carrier .UMTS Radio Mobility 4.20.06/EN Approved_Standard 17/Sep/2010 Page 137/244 .6.2 IMCTA TRIGGER IS CAC FAILURE The following steps are processed to select a cell among the measured FDD neighbour cells: 1.3 IMCTA TRIGGER IS ALARM The following steps are processed to select a cell among the measured FDD neighbour cells: 1.8.] 2. 3. the cell with the best Ec/No which verifies FDD HHO condition. the cell with the highest Radio level is selected. Then if several 2G cells are 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 iMCTA load based HO developments is activated Passing on or copying of this document. the following steps (with decreasing priority) are processed until retaining one cell: a) If UE is HSUPA capable.3.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. For each Carrier . i. . the cell with the best Ec/No which verifies FDD HHO condition . the CEM load color of the target cell has to be strictly better than the CEM load color of the current active set.

A 3G/2G. If 2G is selected as target and the relocation preparation to the selected target cell fails. 2. c. e. preference is given to HSUPA cells then HSDPA cells else if UE is HSDPA capable. Its load satisfies the target cell Load iMCTA based HO load color criteria (described in section 4. due to load conditions in the GSM cell. The cells fulfilling the Radio criteria are selected.e. A Rab Assignment Response message is returned by the S-RNC to the Core Network.3. If no target cell is eligible. The less loaded cell is preferred.3). Inter Freq RNC HHO): A Rab Assignment failure is returned to the CN with the Rab failed and a “noresource available” cause Passing on or copying of this document. o If the Target cell is not managed by the S-RNC (i. o If the Target cell is managed by the S-RNC (i.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). Preference is given to the less loaded cell.20. This re-attempt can be controlled with parameter isGsmIratHoToNextBestCellAllowed. Preference is given to the cell with the best radio level (Ec/No).UMTS Radio Mobility • 2. If UE is HSUPA capable. Then if several 2G cells are eligible. 3. their Rxlev verify 2G HHO condition. Inter Freq Intra RNC HHO): The Inter Freq Hard Handover procedure towards the target cell is processed.1 IMCTA HARD HANDOVER PROCESSING OR IMCTA EXIT 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.] Then if several FDD cells are eligible. CAC trigger: After a CAC failure during a Rab Assignment/Release/Modification.if found any . [USA Market .20. b. Preference is given to cell(s) belonging to the carrier with the highest priority.06/EN Approved_Standard 17/Sep/2010 Page 138/244 .g. The following steps are processed to select a cell among the measured neighbour 2G cells: 1.e.3.20. the cell with the highest Radio level is selected.3.e. then the RNC may re-evaluate the measurement report for the next best 2G neighbour cell and .7. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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. the following actions are processed: o If resources were partially allocated for the requested Rab they are released.e.7 4.re-attempt handover to this 2G cell. Then waiting procedures may be processed. the following steps (with decreasing priority) are processed until retaining one cell: a. o If the Target cell is not managed by the S-RNC (i. a blind GSM cell may be used if configured. 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 . preference is given to HSDPA cells. d. i. 4.8.

20. The transition depends on the iMCTA trigger type. 4. the actions are: Service and Alarm trigger: the waiting procedures may be processed. The waiting procedures may be processed. • Iub downlink load. • Downlink OVSF code load. 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): Passing on or copying of this document. they are released. a set of cell load elementary colors is read. each relevant cell load indicator is checked. 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.1 CELL LOAD INDICATORS The feature consults the following elementary load indicators: • CEM ul and dl loads.3. The definition of the load indicators are given in [R7]. 4. the elementary load colors depend only on the RABs established or to establish (CAC failure case). • Downlink power load.20.7. 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. 4.06/EN Approved_Standard 17/Sep/2010 Page 139/244 .3. CEM or Iub levels.8. 4.3.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 rearmed) and no blind HHO 3G/2G may be processed. E-DCH).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.3. the originating cell color threshold is configurable per service.2 ORIGINATING FDD CELL ELIGIBILITY For each Rab established. Whatever the resource used by the call (DCH.UMTS Radio Mobility For the Hard Handover execution see the section describing the Hard Handover type used. 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. For cell eligibility.8. 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.20. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. • Uplink load (RTWP). If Inter Frequency/Inter Rat measurements were requested to the mobile. HS-DSCH. A Rab Assignment Response Failure message is returned by the S-RNC to the CN with the Rab failed. According to the trigger.20. [UA06-UA07 difference]: With the addition of the feature iMCTA load based HO developments. The mobile is no more in connected mode (cell DCH). The Iub downlink load consulted is the load part attached to the QoS of the services to be established.18).

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. For cells managed by a D-RNC.3.20.20. For example if the target cell load threshold is equal to “Yellow”.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. When a neighbour 2G cell is given by a D-RNC and cannot be found in the S-RNC provisioning.20. Passing on or copying of this document.UMTS Radio Mobility At least one DL color ≥ iMCTA originating cell color threshold OR At least one UL color ≥ iMCTA originating cell color threshold.8.3. 4. 4. 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).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).8.4 TARGET FDD CELL ELIGIBILITY (USED FOR SERVICE) For each Rab to establish. the target cell load has to be “Green” or “Yellow”. Two colors are supported: green/red. the iMCTA target Cell color threshold has a Red default color.06/EN Approved_Standard 17/Sep/2010 Page 140/244 . the cell iMCTA color is also green by default. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 4. the iMCTA target Cell color threshold has a Red default color. the cell iMCTA color is green by default. a set of cell load elementary colors is read.8. At the cell configuration.3.

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
4.20.4.1

PARAMETERS
IMCTA OPTIONS
Object/Class RadioAccessService Class 3 ServiceForTrafficSegm entationPriority Class3 RadioAccessService Class 3 RadioAccessService Class 3 Definition If set to True, the Service Handover IE (if present) will be taken into account by the RNC whatever the iMCTA triggers. If set to True, the service segmentation will have a higher priority than load balancing in iMCTA algorithm (option Service Segmentation activated 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. 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. 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. 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

Name serviceHoRanapEnable

IsServiceSegmentationTopPr iority Is2GCellLoadInformationM anagementAllowed [Global Market] InhibitTimer3g2g

mode

FDDCell Class 3

hsxpaSegmentationEnable

FDDCell Class3

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 141/244

UMTS Radio Mobility
Alarm/CAC failure triggering. 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. 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. 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. 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. 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. 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. 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 interfrequency (3G) or inter-RAT (2G) measurements. 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. 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. Enables the target FDD cell load criteria when iMCTA reason is Alarm or CAC failure. 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

mobilityServiceForHsxpaEn able

FDDCell Class3

mobilityServiceForNonHsxp aEnable

FDDCell Class3

originatingCellColourThres holdPerService

OriginatingCellColour ThresholdConfClass Class 3

mode

NeighbouringRNC Class 3

targetCellColourThreshold

FDDCell Class 3

userServiceSigToTrafficOnly Enable

FddIntelligentMultiCar rierTrafficAllocation Class 3

is3GHandoverPreferred

FDDCell / NeighbouringRNC Class 3

isGsmIratHoToNextBestCell Allowed isChangeGsmIratHoCriterio nAllowed

RadioAccessService Class 3 RadioAccessService Class 3

isImctaLoadBasedAllowed [USA Market] imctaLoadBasedTargetCell ColorThreshold [USA Market]

RadioAccessService Class 3 UmtsNeighbouringRel ation UmtsNeighbouringInte lligent-

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 142/244

UMTS Radio Mobility
MultiCarrierTrafficAll ocation Class 3 RadioAccessService Class 3 yellow, all relevant target cell colors must be green or yellow. 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 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.

isImctaFddLayerLoadPreCh eckAllowed

isImctaLoadBasedAlarmAllo wed

FDDCell Class 3

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.

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 143/244

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
Name

IMCTA PRIORITY TABLES
Object/Class
RadioAccessService Class3

Definition
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. 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. 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).

AlarmPriorityTableConfClass

CacPriorityTableConfClass

RadioAccessService Class3

ServicePriorityGeneralTableConfClass

RadioAccessService Class3

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 144/244

1 IMCTA PRIORITY TABLE DEFINITION: GENERAL ASPECTS When iMCTA is invoked by one of the triggers. the priority of each service has to be read from the instance “OtherFDD” of the MO frequency. This table is used when an iMCTA service trigger is processed for a HSUPA capable mobile. Pointer towards one instance of the ServicePriorityTableForHsupaConfClass tables.06/EN Approved_Standard 17/Sep/2010 Page 145/244 .UMTS Radio Mobility ServicePriorityTableForHsdpaConfClass RadioAccessService Class 3 This table gives for each Fdd and 2G carriers a priority value per service type. Pointer towards one instance of the CacPriorityTableConfClass tables.2. This table is used when an iMCTA service trigger is processed for a HSDPA capable mobile. Pointer towards one instance of the AlarmPriorityTableConfClass tables. This parameter is a pointer to one of the five ServiceSegmentationPriorityClass instances ServicePriorityTableForHsupaConfClass RadioAccessService Class 3 ServiceSegmentationPriorityClass alarmPriorityTableConfClassId cacPriorityTableConfClassId servicePriorityGeneralTableConfClassId servicePriorityTableForHsdpaConfClassId servicePriorityTableForHsupaConfClassId alarmPriorityTableConfClassId cacPriorityTableConfClassId serviceSegmentationPriorityTableRef RadioAccessService Class3 FDDCell Class 3 FDDCell Class 3 FDDCell Class 3 FDDCell Class 3 FDDCell Class 3 NeighbouringRNC Class 3 NeighbouringRNC Class 3 FDDCell (iMCTA) Class3 [UA06-UA07 difference]: With the feature iMCTA load based HO developments. CAC and Service).2. iMCTA priority table Service type 2 …… FDD1 FDD2 FDD3 FDD4 FDD5 FDD6 2G OtherFDD Service type 1 Pi Pj Pk Pl Pm Pn Po Pp Service type n The list of services is given below in § 4.20. Pointer towards one instance of the ServicePriorityGeneralTableConfClass tables. Pointer towards one instance of the ServicePriorityTableForHsdpaConfClass tables. The priorities per carrier and per service type are defined via O&M.4. 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.4 iMCTA Service Type Definition. • 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).20. 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. Passing on or copying of this document. This table gives for each Service if the Service Segmentation has a higher priority than load balancing Pointer towards one instance of the AlarmPriorityTableConfClass tables. The instance “OtherFDD” is used as default value. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. the iMCTA Alarm and CAC priority tables have the same format as the iMCTA service priority table. This table gives for each Fdd and 2G carriers a priority value per service type.4. It allows: • A better control of the mobility. 4. The operator may give different Carrier priorities according to the iMCTA trigger (Alarm. 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. Pointer towards one instance of the CacPriorityTableConfClass tables.

The goal is to establish all requested RAB on a better carrier.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. 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. 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. a Fdd frequency or a set of Fdd frequencies or the 2G Radio Access System shall not be considered for the request service type.20. If the priority is set to PNA (Priority Not Applicable). The operator can configure a specific Service table per UE type: iMCTA HSUPA table (optional table). it is possible to have the PNA value for all Access. priority value) in Priority tables.4. after applying the different filtering. the table has to be used when the mobile is HSDPA capable. Since UA07. 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. iMCTA General table (mandatory table).2. P8). 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 list of Service types is: Passing on or copying of this document. allows the priority setting of each FDD frequency (as for iMCTA service priority table).4 IMCTA SERVICE TYPE DEFINITION The Service Type is an input to access information (i. they have the same format. P1…P7 with P1>P2>…. 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. P1…P8 with P1>P2>…>P8. the carrier shall not be considered for the request service type.P7. the RNC has to replace the priority value with the lowest priority value (i.20.e. The table applies to all mobiles types (HSDPA/HSUPA capable or not) with a primary link located on the CRNC or a D-RNC. The table has to be used for non HSDPA/HSUPA capable mobiles.20.e. 4. Whatever the result of the procedure which triggers the iMCTA.4.0.2. The different priority values are: PNA.4. FDD carriers priorities could be the same in order to allow load balancing between FDD layers. For each Service type. The different priority values are: PNA. FDD carriers priorities could be the same in order to allow load balancing between FDD layers.06/EN Approved_Standard 17/Sep/2010 Page 146/244 . If. For each Service type. If present. For each service type the 2G carrier priority can be equal or different to the FDD carrier priorities. the table has to be used when the mobile release is HSUPA capable. If present. it is possible to have the PNA value for all layers (FDD and 2G). two Radio Access System are selected (Priority <>PNA). iMCTA HSDPA table (optional table).2. 4. If the priority is set to PNA.UMTS Radio Mobility 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.2 IMCTA ALARM AND CAC PRIORITY TABLES DEFINITION There is one table for Alarm and another one for CAC. The table only applies to a call with a primary link located on the C-RNC. It also my used if the mobile release is HSUPA capable and the iMCTA HSUPA table is not present.

) 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 list of Services is the same as in Service type. HSDPA AND HSUPA MOBILITY This section provides a high level view of the interactions between HSDPA or HSUPA and mobility. 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.20. Full details are available in § [R4] UMT/SYS/DD/013319 HSDPA System Specification and [R6] UMT/SYS/DD/018827 E-DCH System Specification.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. Name serviceType Object/Class DlUserService Class 3 Definition For each DlUserService Instance. a ImctaServiceTypeId is set which allows to access the iMCTA priority tables. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.UMTS Radio Mobility CS Speech CS Conversational (64/64) CS Streaming PS Streaming PS Interactive/Background CS speech + other service (PS. independently of the load of the primary cell. 4.20.20.5 PERFORMANCE MANAGEMENT The document [R9] gives the description of the counters.2.21. 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. 4.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.2. 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). The “highest RB” will be the input to map the Service type.06/EN Approved_Standard 17/Sep/2010 Page 147/244 .. The “none” value is used to set some User Service (signaling…) ineligible to iMCTA.4. Passing on or copying of this document. The operator has not to modify the list without Alcatel-Lucent agreement. or PS+PS. 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. 4. 4.4..

4.1. When all layers support HSDPA and/or HSUPA. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.21. one of them may be tagged as “layerPreferredForR99” by configuration. HSUPA) is not deployed everywhere in the layer then an automatic channel type switching between DCH and HS-DSCH (resp.2 Even though deploying HSDPA and HSUPA on a separate layer is the preferred option.21. If HSDPA (resp.21.1 4. it is necessary that HSDPA is also configured in this cell. E-DCH) is performed when the UE enters in or leaves an HSDPA (resp.21.1.21.1 DESCRIPTION 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. HSUPA) cell (more information are provided in paragraph 4. The drawback of this scenario is that HSUPA traffic may impact R99 Uplink traffic by generating interferences.1. Full details are available in [R4] and [R6]. 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.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).06/EN Approved_Standard 17/Sep/2010 Page 148/244 . 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. Passing on or copying of this document.UMTS Radio Mobility 4.1. However. Layer with HSDPA configured Layer without HSDPA • a three-layer deployment scenario: o one reserved for R99 o one with HSDPA. HSDPA ON EXISTING LAYER 4.3). This is because any radio-bearer mapped on E-DCH in uplink will necessary be mapped on HS-DSCH in downlink. Note: to deploy HSUPA in a cell. see above).1. 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. HSDPA may be deployed in a cell without deploying HSUPA.

PS RABs means: • PS I/B RABs (for HSxPA) • PS streaming RABs (for HSDPA only. Passing on or copying of this document.1.3.1. 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). possibly in parallel with other DCH radio bearers) and HSUPA calls (at least on E-DCH radio-bearer). use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.3 HSDPA AND HSUPA CALL MOBILITY PROCEDURES This section is only applicable to HSDPA calls (mobile having at least one HS-DSCH radio-bearer. Mobility of R99 calls – even in an HSDPA or HSUPA cell – is handled as described in the other sections. 4.3.21.1.2 REDIRECTION AT CONNECTION SETUP Traffic segmentation (HSDPA vs R99) can be ensured by different means.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. From UA06. If the new primary cell does not support HSDPA then the RB is reconfigured to DCH. In case of primary cell change. • or at RAB assignment (iMCTA feature. Note: in following paragraphs. based on the HSDPA/HSUPA capability of the mobile and on traffic class of the RAB. Mobility of E-DCH As specified by the 3GPP standards. each one described in a specific section: • either at RRC connection establishment (refer to § 4. § 4. HS-DSCH is established on the primary cell (good radio conditions and not changing too often). In Alcatel-Lucent implementation. On the opposite.21. using a synchronized radio link reconfiguration.19). • or on other iMCTA trigger (refer to § 4. 4.06/EN Approved_Standard 17/Sep/2010 Page 149/244 . Mobility of HS-DSCH As specified by the 3GPP standards.1). it is reconfigured to E-DCH if the mobile comes back to HSUPA coverage.3 and 5. if streaming on HSDPA feature activated) It does not include Conversational RABs.UMTS Radio Mobility 4.18.0 release. HS-DSCH is established in only one cell so is never in soft handover. the HS-DSCH RL is deleted on the former primary and re-established under the new primary.21. the E-DCH serving link and the HS-DSCH link are moved at the same time (one procedure). The mobility of the E-DCH serving link is based on the same principals than the HS-DSCH one. macro-diversity of E-DCH (having non-serving E-DCH radio-links) is supported by Alcatel-Lucent (refer to § 5.4. Each time the primary cell changes. 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). there is only one serving E-DCH radio-link and it is established in the same cell that the HS-DSCH radio-link.19).7).

When the mobile comes back under the serving RNC and the primary cell supports HSUPA.e.] 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.3. EDCH). 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. then the relocation is refused. In case of the target cell being controlled by the SRNC. E-DCH) if the target cell supports HSDPA (resp. And this may trigger either an intra-RNC handover (with or without Iur) or an inter-RNC handover (over Iur or with relocation procedure). Otherwise a DCH resource is chosen. 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. [Global Market: If E-DCH support over Iur is enabled on DRNC then no restrictions apply to the incoming EDCH mobility. the E-DCH radio-bearers is reconfigured to DCH in UL.3.06/EN Approved_Standard 17/Sep/2010 Page 150/244 . i. the Mac-e scheduler will also take into account compressed mode gaps. the radio bearer is reconfigured to E-DCH in UL otherwise it remains in DCH.3 INTER-FREQUENCY MOBILITY Inter-frequency handover is supported for HSDPA calls and HSUPA calls as for any R99 call. If it is not the case.e.21. [Global Market: If E-DCH support over Iur is enabled on SRNC then no restrictions apply to mobility over Iur.1.A SRNS relocation (“UE not involved”) may be triggered for an HSxPA call on the Iur as for a R99 call. For an HSDPA call. E-DCH) if not already done. the PS RB will be kept (or established) on HS-DSCH (resp.21. and whatever the container content. [Global Market: E-DCH is managed over Iur since UA06 (refer to [R6])]. 4. then the relocation is refused. 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. i.1. After SRNS relocation. Passing on or copying of this document. • intra-RNC handover within the SRNC or • inter RNC handover towards the SRNC. the RNC will perform a DCH fallback as for a RAB assignment (refer to [R4]). In case of HS-DSCH CAC failure. It will also not be scheduled if the answer (Ack/Nack) falls during a gap for the same reasons.UMTS Radio Mobility Mobility over Iur HS-DSCH is managed over Iur. the CRNC performs a UE capability enquiry procedure and may reconfigure the PS radio-bearers to HS-DSCH (resp.] When the Serving RNC triggers a relocation (“UE involved”). it is reconfigured (or kept) to DCH in downlink (resp. • 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. If the CAC also fails for the fallback.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. 4. If the CAC also fails for the fallback. the RNC will perform a DCH fallback as for a RAB assignment (see [R6]). use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. In case of CAC failure on E-DCH or HS-DSCH.] [Global Market . The handover protocol to be performed and possible HSxPA to DCH and DCH to HSxPA reconfigurations depend on the allocation of the target cell. For an HSUPA call. uplink) In case of the target cell being controlled by a DRNC.

16 for Inter-frequency handover over Iur). 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. HSUPA) and the source RNC has indicated that the UE supports HSDPA in the Rel’5 extensions (resp. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Passing on or copying of this document. If the target cell supports HSDPA (resp. If it happens that the UE is HSDPA (resp. IFHHO with SRNS Relocation (HSxPA or DCH) Yes Target cell on DRNC and Reloc. HSUPA) capable then the PB radio-bearers are reconfigured to HS-DSCH in downlink if the primary cell is HSDPA (resp. If performed over Iur then only DCH to DCH handover is supported and HSxPA calls need to be reconfigured to DCH before the handover. Inter-frequency handover over Iur will be done with preference if enabled towards the DRNC to control the target cell (refer to §4. IFHHO HSxPA / DCH Handover Yes SRNC Target cell on SRNC ? No DRNC Yes Call on DCH ? Yes DCH Yes HSxPA No HSxPA Target cell on SRNC and HSxPA ? No (on DRNC or does not support HSxPA) HSxPA to DCH Reconfiguration Enabled over Iur ? No IFHHO Procedure (HSxPA or DCH) Yes DCH successful ? No HSxPA successful ? Yes No old freq.enabled ? No Call on new frequency Yes successful ? No Call on old frequency In case of inter frequency handover over Iur being disabled or being unsuccessful with return to old frequency. E-DCH in uplink). If no information about the HSDPA (resp.06/EN Approved_Standard 17/Sep/2010 Page 151/244 . 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. this triggers a relocation. A UE capability enquiry is then triggered.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. 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). E-DCH in uplink if the primary cell is HSUPA).

E-DCH) to the incoming UE.4 PARAMETERS See [R4].21.21. 4. ACCESS NETWORK IMPACTS 4. this is seen as a new Mobile Originated PS call from the target RNC (No incoming relocation as the mobile was in GSM/GPRS).3 See [R4]. leading possibly to the allocation of HS-DSCH (resp. See [R6]. See [R6]. The handover is triggered on the same conditions as for non-HSDPA calls (see section 4. ALGORITHM 4.1.6 See [R4]. In case of a pure PS call.21.UMTS Radio Mobility 4.5 See [R4].2 See [R4]. CORE NETWORK IMPACTS Passing on or copying of this document. See [R6].21.06/EN Approved_Standard 17/Sep/2010 Page 152/244 .21. 2G to 3G handover 2G to 3G handover is supported. Mobility parameters can be tuned by mobility service type. The same rules as the initial admission apply. APPLICABILITY 4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.19). See [R6].3. See [R6].4 INTER-SYSTEM MOBILITY 3G to 2G handover 3G to 2G handover is supported for HSDPA/HSUPA calls. 4.21.

new URA identity) Figure 64: Assigning a new URA If multiple URAs are defined in the current cell. allowing the RNC to move the UE to Cell_PCH RRC state. the RNC shall select the appropriate one: the one on top of the list. 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). When the UE reselects a cell that does not belong to this URA (ie: this URA identity is not present in SIB2).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. the RNC shall assigned (assuming it knows the UE) a new URA to this UE. URA reselection process The RNC has to assign one URA identity to the UE when it moves the mobile to URA_PCH.06/EN Approved_Standard 17/Sep/2010 Page 153/244 . The RNC modifies this URA identity when an RRC Update occurs with the “change of URA” cause. On reception of the URA update for URA reselection reason.. the URA (UTRAN Registration Area) identity (ies) of the cell.22. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.UMTS Radio Mobility 4. the UE performs a URA update procedure with URA update cause ‘change of URA’.8). Passing on or copying of this document.22. MOBILITY IN CELL_PCH AND URA_PCH RRC STATES 4. UE URA UPDATE (u-rnti) UTRAN URA UPDATE CONFIRM (u-rnti .

Re-entered service area On reception of the Cell Update message. 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). IOT Mobile restrictions It is possible that some UEs do not support URA or CELL PCH. If this counter reaches a configurable threshold. In case the UE does not support the RRC state.UMTS Radio Mobility IUR Management ASSUMPTION: IT IS NOT ALLOWED TO SPREAD A URA OVER TWO RNS. 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.06/EN Approved_Standard 17/Sep/2010 Page 154/244 . It is used as supervision mechanism: the call is released in case of periodical update lack. Passing on or copying of this document. Alcatel-Lucent RNC will not provide any information on URAs on the Iur (in RL Setup/Addition Response and in Uplink Signalling TransferIndication messages). Cell reselection On reception of the Cell update message from a mobile in Cell_PCH state. There is no functional consequence to this because the interest of these states vs idle is only a faster resume 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. Periodic cell update On reception of the Cell Update message. Note that the release is applicable anytime the RNC receives a message from an unknown u-RNTI. the RNC shall send the mobile to URA_PCH (if the operator has activated URA_PCH). the reconfiguration fails then the RNC shall release the RRC connection (moves UE to Idle). the RNC shall send an RRC Connection Release message to the UE. based on the cause indicated by the UE in the message. the RNC shall resend the mobile to Cell_PCH. Cell Update and URA update management The update procedures use the following messages: Cell reselection URA reselection Periodic Cell update Periodic URA update Re-entered service area Used in CELL_FACH or CELL_PCH when the UE re-selects a new cell Used in URA_PCH when the UE leaves the URA it was assigned to Used in CELL_FACH or CELL_PCH when T305 expires (periodic cell update timer) Used in URA_PCH when T305 expires (periodic URA update timer) Used in CELL_FACH or CELL_PCH or URA_PCH when the UE reenters 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. the RNC increments the counter of number of Cell reselections. the RNC updates the UE location and resends the mobile to Cell_PCH. 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). 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.. In case the cell is part of new LA/RA.5). Else. If for any reason. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. then a LA/RA update is performed on Cell_FACH. Note: Alcatel-Lucent RNC will not support Paging Request over URA from the Iur and will ignore this message.

or If the current cell is not part of any URA. In this case. it shall send an RRC Connection Release to the UE.22. Inter Frequency or Inter rat mobility management is the same as for CELL-FACH RRC state. 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). Periodic URA update Nothing to do except resend the mobile to URA_PCH state keeping the same URA. 4..5 ACCESS NETWORK IMPACTS Ability to broadcast the configuration parameter on the radio interface. the RNC shall: If the u-RNTI belongs to another RNS.UMTS Radio Mobility URA reselection On reception of the URA update message.65535) Object/Class FDDCell Class3 Definition 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 . 4. The mobility configuration is made through the following parameter: Name URA identity [1.3 ALGORITHM The cell selection/re-selection evaluation process (see [A5]) in Cell_PCH or URA_PCH RRC state for Intra Freq. Passing on or copying of this document. If the u-RNTI belongs to this RNS. It is used as supervision mechanism: the call is released in case of periodical update lack. 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).4 PARAMETERS The activation of using CELL/URA PCH RRC state is described in [R3]. If the list is not provided.2 APPLICABILITY This feature is applicable when the call enters in Cell/URA PCH state. the RNC shall act as for the first one received (but may assign a different URA if the cell reselected is different).8]: (0.22.22. Please refer to section § 4.22. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 4. it shall send an RRC Connection Release message (directed signalling connection re-establishment cause): see [Iur management] in a previous paragraph. “Unknown” u-RNTI In case the UE sends a Cell Update or URA update message with an unknown u-RNTI. the mobile shall be moved to Cell_PCH (if enabled) or idle (else). 4.5. The RNC doesn’t check if the cell is part of new LA/RA: no LA/RA update procedure is performed on Cell_FACH. the RNC shall send the mobile to Cell_PCH (given it is allowed on the network) or Idle (if Cell_PCH is not allowed).06/EN Approved_Standard 17/Sep/2010 Page 155/244 .. Management of the Cell/URA update procedures.4.

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. In addition it allows a better radio plan management and handles the UTRAN resources with better efficiency improving the UTRAN capacity (i.23.6 No impact.e. handling others services as in private systems. macro cells/ mobility layer). capacity layer). and URA/Cell_PCH connected modes. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. rather low moving terminals to micro/pico cell layer (i. Note: HCS is not used by the UE for inter-RAT reselection if absolute priority based cell reselection is used for inter-RAT. mobility layer).5 but with additional algorithms handled by the HCS and applicable to the new concept of the UE fast moving also called high mobility. Cell_Fach. 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.e. For example fast moving terminals could be redirected to macro cell layer (i. improving higher data rate services in small areas.06/EN Approved_Standard 17/Sep/2010 Page 156/244 . (see [A5]) Passing on or copying of this document. 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. HCS: CELL RESELECTION CONTROL IN A HIERARCHICAL CELL STRUCTURE [GLOBAL MARKET] 4.4 and 4. micro cells/capacity layer).1 DESCRIPTION The Hierarchical Cell Structure feature enables the cell reselection control procedure in a Multi Layer network. and so decrease the total system cost. It means the cell plan has several levels. CORE NETWORK IMPACTS 4.23.e.e. This feature allows the operator to prioritize cell layers for mobiles in idle mode.UMTS Radio Mobility 4.22.

and enters a micro cell. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. which is tuned to lower transmission terminals. It may appear in particular radio conditions (UE at the edge of radio cells). large number of handoff between these cells may occur. Typically High mobility detection is useful in such cases. 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. It shall also offer to reduce negative radio effect when one fast moving UE is connected to a distant macro cell. to trigger the high mobility detection even if it’s not a real fast moving UE case.23.UMTS Radio Mobility Macro cell Fk HCS priority level I Micro cells Fm HCS priority level J Pico cells Fn HCS priority level K HCS STRUCTURE PLAN 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.06/EN Approved_Standard 17/Sep/2010 Page 157/244 . local traffic peaks are likely to occur and so required micro cells are needed to complement the macro cells. then the unwanted radiation of the high power transmission UE may generate some interferences at the micro cell NodeB. As the traffic user demands on the network should vary in time and in space. and shall avoid too much undesirable handoffs which can produce call drops. Now with fast UE. 4.2 APPLICABILITY 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". • only UTRAN/FDD and GSM Radio Access Technologies are known and supported Passing on or copying of this document.

Passing on or copying of this document. Qoffset1s. in order to detect a high mobility state. The new specific parameters for HCS cell re-selection procedure are controlled by the RNC. o o o HCS cell-reselection procedure is based on UE measurements and the measurements rules.3 ALGORITHM As specified in [A5]. o 3GPP defined thresholds level (Qhyst1s .UMTS Radio Mobility The HCS algorithm is based on the classical principles of the re-selection algorithm of the UE in Idle/connected mode. Note: When HCS is not used the SsearchHCS applies also.06/EN Approved_Standard 17/Sep/2010 Page 158/244 . and for SIB4/SIB12 in FACH or PCH mode if enabled. 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. o Cell Ranking criteria R. 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 o o High mobility detection (UE fast Moving). 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. o Time reselection duration according to the corresponding UE state (URA/Cell PCH or CellFACH). When HCS is used SsearchHCS specifies the threshold for Srxlev below which Intra-frequency and interfrequency measurements of the neighbouring cell are performed. The broadcasting of these new parameters implies coding/scheduling modification for SIB3/SIB11 broadcasted on the BCCH channel in idle mode. UE measurement for intra/inter frequency 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.23. o HCS re-selection criterion and HCS thresholds as: Qhcs: Quality threshold level for applying hierarchical cell reselection. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.…). 4.n. o UE measurement for intra/inter frequency. 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.4 ). o UE measurement for inter RAT. 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. Hs/ Hn: Quality threshold criterion for applying hierarchical cell reselection. UE measurement for inter RAT used for high mobility state detection. o HCS_PRIOn: Defines the HCS priority level for neighbouring cells. The new concept of high mobility detection procedure could be applied to the HCS measurement rules if configured.

s + Qhysts Rn = Qmeas. The list may be a sub-list of all provisioned neighbour cells sent in the SIB11message. 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 ). The quality of the received signal expressed in CPICH Ec/N0 (dB) Quality threshold levels for applying HCS algorithmic. Step 2: The S and H criterion apply on the measured cells to identify cells candidates for the neighbour cells ranking criterion R.s .n .06/EN Approved_Standard 17/Sep/2010 Page 159/244 .3. 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.4).TOn * (1 – Ln) Passing on or copying of this document. Constant value 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.Qhcsn – TOn * Ln with: Q meas. is defined as: Hs = Qmeas. the criterion S apply on measured cells with: o If (HCS_PRIOn < HCS_PRIOs).Qhcss Hn = Qmeas.n . 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). QHCS n Ln TOn Measured cell quality value. The quality threshold level criterion H for HCS. involving a prioritized ranking to the candidate cells. 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). 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.4. Q meas.n .23.s . o 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. Cell re-selection criteria apply for intra/inter frequency and inter RAT cells.UMTS Radio Mobility 4. The S criterion is described in the section 4.Qoffsets.n QHCS s . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. If high mobility state is active. o If (HCS_PRIOn ≥ HCS_PRIOs).1 CELL RESELECTION CRITERIA WHEN HCS IS USED If HCS is used in the serving cell.

There is one Tn timer per neighbour measured cell.e. Qmeas = quality value of the received signal HCS_PRIOs. TO n and Ln calculation Extract of [A5].e. HCS_PRIOn <> HCS_PRIOs ) Rn formula when Ln =0 (i. HCS_PRIOn. The selected cell has to fulfill the Access restriction rules see [A5].UMTS Radio Mobility The best ranking cell is the cell with the highest R value. As explained in the section 4. 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. 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.W(x) = 0 for x < 0 . (use case: ping pong between cells of same priorities). 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. = HCS priority level of the cell. Time Offset (TO) applies in: Hn formula when Ln =1 (i. The change of the serving cell doesn’t imply a timer stopping.n in order to increase the offset and so temporary disadvantage a neighbour cell for the Hn and Rn criterion: it allows avoiding pingpong effect.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). T n timer definition Extract of [A5].4 the ranking is based on CPICH RSCP quality and a second ranking may occur when quality measurement is Ec/No. 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. TO n = TEMP_OFFSETn * W(PENALTY_TIMEn – Tn) Ln = 0 Ln = 1 Tn = Timer if HCS_PRIOn = HCS_PRIOs if HCS_PRIOn <> HCS_PRIOs . It bounds the temporary offset use. HCS_PRIOn = HCS_PRIOs) Time Offset parameter applies a temporary offset value which is added to the offset Qoffsets. The Tn timer is stopped when the condition is no longer fulfilled.06/EN Approved_Standard 17/Sep/2010 Page 160/244 .

n.23.n) Start Tn.4 4.n = Qoffset1s. 2G Cell: Qoffsets.n = Qoffset1s. If the number of cell reselections during period TCRmax exceeds NCR.4. high-mobility has been detected. 4. . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Qoffsets. If quality measurement used is CPICH RSCP. Fdd Cell: If quality measurement used is CPICH Ec/No.UMTS Radio Mobility . Passing on or copying of this document.n . The high mobility state doesn’t mean the mobile speed is high but the number of reselection is high.4) 4. The “tCrMax” allows the activation/deactivation of the High mobility detection.n > Qmeas.23.If (HCS_PRIOn == HCS_PRIOs) && (Qmeas.23. Qoffsets.If (HCS_PRIOn <> HCS_PRIOs) && (Qmeas.1 PARAMETERS AT UTRAN/FDD CELL LEVEL The “isHscUsed” parameter allows the activation/deactivation of the HCS procedure.n >= Qhcsn) Start Tn. UE shall: Continue these measurement during TCrmaxHyst.n = Qoffset2s. High mobility detection (if HCS is used) Extract of [A5]. The high mobility detection may be used if HCS is not used (see section 4.3.n. If the criteria for entering high mobility is not detected during time period TCrmaxHyst: Exit high-mobility.2 INTER RNC CASE In this version full HCS is applicable for intra RNC case only.06/EN Approved_Standard 17/Sep/2010 Page 161/244 .s + Qoffsets. When the number of cell reselection during time period TCrmaxHyst no longer exceeds NCR. Else Stop timer Tn.

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". Enumerated (not used.. Real (0. This specifies the duration for evaluating allowed amount of cell reselection(s). 70). 60. 120.1 by step of 0.25). 40.7). This threshold is used in the measurement rules for cell re-selection.UMTS Radio Mobility OAM parameter isHcsUsed sSearchRatGsm SIB Object FDDCell CellSelectionInfo CellSelectionInfoCo nnectedMode CellSelectionInfo CellSelectionInfoCo nnectedMode description/comment This parameter indicates whether HCS is used in the Fdd cell Integer (-32. Integer (-105.99). When HCS is used.75 by step of 0. This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections.4. Integer (-105...06/EN Approved_Standard 17/Sep/2010 Page 162/244 .. This specifies the 2G RAT specific threshold in the serving cell used in the inter-RAT measurement rules. Real (1.91 by step of 2).. 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.75 by step of 0. 3 4 sSearchHcs 3 4 sHcsRatGsm 3 4 CellSelectionInfo CellSelectionInfoCo nnectedMode speedDependScalingFacto rTReselection 3 4 CellSelectionInfo CellSelectionInfoCo nnectedMode CellSelectionInfo CellSelectionInfoCo nnectedMode CellSelectionInfo CellSelectionInfoCo nnectedMode CellSelectionInfo CellSelectionInfoCo nnectedMode CellSelectionInfo CellSelectionInfoCo nnectedMode CellSelectionInfo CellSelectionInfoCo nnectedMode CellSelectionInfo CellSelectionInfoCo nnectedMode CellSelectionInfo CellSelectionInfoCo nnectedMode CellSelectionInfo CellSelectionInfoCo nnectedMode interFreqScalingFactorT Reselection interRatScalingFactorTR eselection tCrMax 3 4 3 4 3 4 nCR 3 4 tCrMaxHyst 3 4 hcsPrio 3 4 qHcs sLimitSearchRat 3 4 3 4 Passing on or copying of this document. When HCS is not used.91 by step of 2). This parameter is mapped to non-TCrmaxHyst or TCrmaxHyst IE for SIB3/4 filling depending of HCS use or not. When HCS is not used. 10.16). 20. 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. This parameter is mapped to non-NCR or NCR IE for SIB3 filling depending of HCS use or not. Enumerated (not used. Integer( 0. HCS priority level 0 means lowest priority and HCS priority level 7 means highest priority. it specifies the 2G RAT specific threshold in the serving cell used in the inter-RAT measurement rules. This specifies the quality threshold levels for applying prioritised hierarchical cell re-selection Integer (-32. This threshold is used in the measurement rules for cell re-selection when HCS is used. This threshold is used in the measurement rules for cell re-selection.FACH for the inter-RAT case.FACH for the inter-frequency case. This parameter is mapped to non-TCRmax or TCRmax IE for SIB3/4 filling depending of HCS use or not.. 30. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.PCH or Treselections. it specifies the limit for Srxlev in the serving cell below which the UE ranks interfrequency neighbouring cells of the serving cell. 240). Real (1.20 by step of 2) In [dB].PCH or Treselections. 60.20 by step of 2).PCH or Treselections.1). 180. Integer (0. Integer (1. This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections. 50.25). This specifies the maximum number of cell reselections.4. 30. it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-RAT neighbouring cells of the serving cell.. This specifies the additional time period before the UE can exit high-mobility.FACH in case high-mobility state has been detected.... This specifies the HCS priority level (0-7) for serving cell .

). 10. Support of a hierarchical radio plan. It is used for FDD cells in case the quality measure for cell selection and reselection is set to CPICH Ec/No. 12. It is used for GSM cells in case the quality measure for cell selection and re-selection is set to CPICH RSCP.. This specifies the HCS priority level (0-7) for the neighbouring cells. Integer(0. 3. It is used in case the quality measure for cell selection and re-selection is set to CPICH RSCP. 4. This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY_TIMEn. Integer( 0. 9. Support of mobility detection for better efficiency even if not mandatory for HCS processing. 10. 30.3 AT GSM NEIGHBOURING CELL LEVEL SIB 11 12 Object GsmNeighbouringCell GsmCellSelectionInfoC onnMode GsmNeighbouringCell GsmCellSelectionInfoC onnMode GsmNeighbouringCell GsmCellSelectionInfoC onnMode GsmNeighbouringCell GsmCellSelectionInfoC onnMode description/comment Integer (0. This specifies the time duration for which the TEMPORARY_OFFSETn is applied for a neighbouring cell. This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY_TIMEn. This specifies the quality threshold levels for applying prioritised hierarchical cell re-selection. 20. 21. 40. Integer (3.06/EN Approved_Standard 17/Sep/2010 Page 163/244 . 12. 50. 18. 40. CORE NETWORK IMPACTS Passing on or copying of this document.23. inf) in dB. 60) in sec.. 50. This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY_TIMEn. 60) in sec.2 AT UTRAN/FDD NEIGHBOURING CELL LEVEL SIB 11 12 Object UmtsNeighbouringRelation FddNeighCellSelectionInfoCon nectedMode UmtsNeighbouringRelation FddNeighCellSelectionInfoCon nectedMode UmtsNeighbouringRelation FddNeighCellSelectionInfoCon nectedMode UmtsNeighbouringRelation FddNeighCellSelectionInfoCon nectedMode description/comment Integer (0. 12. HCS priority level 0 means lowest priority and HCS priority level 7 means highest priority. HCS priority level 0 means lowest priority and HCS priority level 7 means highest priority.7). 20. 4.7).23. 21. Integer(2. 15. 18. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 6. 10. This specifies the HCS priority level (0-7) for the neighbouring cells. 6.99).23. This specifies the time duration for which the TEMPORARY_OFFSETn is applied for a neighbouring cell. Integer( 0.99). inf)in dB. 15. 6. OAM parameter hcsPrio qHcs 11 12 11 12 11 12 penaltyTime temporaryOffset1 4. Integer(3. inf) in dB.UMTS Radio Mobility 4. 30. OAM parameter hcsPrio qHcs 11 12 11 12 penaltyTime temporaryOffset1 11 12 temporaryOffset2 11 12 UmtsNeighbouringRelation FddNeighCellSelectionInfoCon nectedMode 4.. This specifies the quality threshold levels for applying prioritised hierarchical cell re-selection. Support of radio parameters setting with high accuracy.. 8. Integer(0.4.6 No impact.4. 9.5 • • • • ACCESS NETWORK IMPACTS Support of the corresponding system information transmission.23.

g. 1D. event 1A reception leads to radio link addition. This is the ALU UTRAN nominal mode for all features except call trace function. 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). INTRA-FREQUENCY EVENT TRIGGERED MEASUREMENT REPORTING MODE DESCRIPTION 5. 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. 4. measured results reported in event 1A shall not lead to RL deletion in the current active set. 1B. The use of “event triggered” reporting has a direct impact on the following mechanisms: • primary cell determination (refer to § 5. intra-frequency inter-RNC or inter-frequency handover criteria evaluation based on current primary cell) active set evaluation process primary cell determination process measurement configuration update (either modification of intra-frequency monitored set. 3.3) The target cell choice for alarm handover is not impacted by the event triggered reporting mode.UMTS Radio Mobility 5. COMMON PROCEDURES PERIODIC MEASUREMENT REPORTING MODE One possible reporting mode is the periodic reporting mode.2.2. 2. 1E. alarm handover criteria evaluation (inter-system. “Measured results” reported by the UE on other cells than the one having triggered the event are not used in mobility handling algorithms e. The main reason for is about “Time To Trigger”.1.2. while event 1B involves a RL deletion.1 Another reporting mode is the intra-frequency event triggered reporting mode. 5. 1C.4) • active set management (refer to § 5. 1. If not specified otherwise. 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.3) • Radio Link colour determination (refer to § 5. 1F.06/EN Approved_Standard 17/Sep/2010 Page 164/244 . 2D and 2F) 1A 1B 1C 1D 2D 2F to add a cell in the active set (1) to remove a cell in the active set (1) to replace a cell in the active set (1) to replace the primary cell in the active set (1) to enter the alarm condition and possibly start inter-freq or inter-RAT measurements (2) to leave the alarm condition and possibly stop inter-freq or inter-RAT measurements (2) 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.9) • inter-frequency blind handover (refer to § 5.g. The basic principle of event handling is that the event semantic is taken into account in the implementation.2. e.3) • alarm measurement criteria (refer to § 5. 5. Making a decision at the RNC side until Time To Trigger has elapsed at the UE side may lead to unstable situations (ping-pong …). each 500 msec).

If event-triggered is configured in the cell where the UE transits to CELL_DCH. • Also configure events (1E and 1F) if the feature SHO enhancement (release UA04. If the event-triggered reporting is configured. 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. all SHO related events are configured. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. the RNC chooses this measurement reporting mode after the transition to CELL_DCH. And when the mode “Full-Event” is selected at the establishment in CELL_DCH.1) is enabled (on a per user service basis) 1E 1F to add a radio link (1) 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. the events are configured once the Signalling Radio Bearer is setup. which helps to decrease the number of simultaneous intra-frequency events required. During all the life of a call. According to [R3] • Event 1A may be configured in SIB11 Passing on or copying of this document. 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 6B The UE Tx Power becomes larger than an absolute threshold 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. 2D and 2F are categorized in the ‘inter-frequency” event group. 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).UMTS Radio Mobility Note: Although being related to intra-frequency measurements.2. there is no mechanism to switch the mode during this phase of the call in CELL_DCH.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. • • Also configure. plus events required for Alarm Measurement criteria. when the alarm condition is fulfilled.06/EN Approved_Standard 17/Sep/2010 Page 165/244 . If the call is setup on CELL_DCH. 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).

• 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. R99.2.2 MEASUREMENT CONTROL FAILURE On reception of a MEASUREMENT CONTROL FAILURE from the UE.2. This may lead to a drop call since measurement reporting may be not configured properly and therefore mobility management may not be handled. if SHO and Alarm Measurement parameters are changing after a change of primary cell or a RB reconfiguration. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. all events need to be re-configured.06/EN Approved_Standard 17/Sep/2010 Page 166/244 . 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. This identity is stored by the RNC in order to allow paging coordination.3 SUMMARY According to [A7]. 5. the UE shall be able to support in parallel per category up to Ecat reporting criteria as defined in following table: Passing on or copying of this document. if all parameters related to a specific event are unchanged.2. An update of the monitored set cells (intra-frequency and/or inter-frequency and/or inter-RAT) may be required. From that perspective. as in call setup case. The timeout of the Blind HO timer is normally running and a Blind Handover procedure is triggered at its expiration. The intra-frequency cell list will be updated by the first MEASUREMENT CONTROL sent after the transition to CELL_DCH i. As a principle. 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.2. it may happen that Measurement Control RRC messages are sent to the UE on reception of the Common ID message on the Iu. In the “National Roaming” context. 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.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.e. i. R4) the message is ignored.e. • 5. There is no impact on the measurement configuration.2. On the other hand.2. o For 6A and 6B. the event is not configured again. depending on the “IMSI-PLMN access right” table defined at the RNC level. 5. the user IMSI is also used to restrict the list of neighbouring cells.e.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. the RNC will: • if the UE is pre-release 5 (i.

the radio link colour evaluation as currently implemented for periodical reporting (see [R7] for details) needs to be updated. Passing on or copying of this document. • Take into account the last received event 1D. a RL Addition can be performed with this cell.UMTS Radio Mobility 25. • Take into account the last received event 1A or 1C (if there is enough room in Active Set at least for 1A). 1B and 1F cannot. All the events needed in UA07. and the active set management process is resumed on the basis of measurements received once the SRLR is complete. number of event reports is low) the RL colour may not reflect the current status of the RL 5.2. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1 FEATURE INTERWORKING RADIO LINK COLOR Once that the event reporting mode is introduced.e. the situation is different.3 5. some events as 1A. As from 25.06/EN Approved_Standard 17/Sep/2010 Page 167/244 . virtual active set Inter-RAT UE internal measurements Traffic volume measurements Quality measurements UP measurements Ecat 8 6 4 4 8 2 + (2 per Transport Channel) 2 per Transport Channel 2 Note Only applicable for UE with this capability Only applicable for UE with this capability.331 RRC specifications.1 Alcatel-Lucent implementation are listed Appendix 1. The major drawback of this solution is that in very low mobility scenarios (i. 1B.3.133 Requirements for reporting criteria per measurement category Measurement category Intra-frequency Inter-frequency Inter-frequency. the RNC is unable to maintain the active set. Active Set processing during the blocking phase: • Take into account all received event 1F (if one RL is remaining at least). During SRLR processing time. If the triggering cell is in the Monitored Set (possible for UE not in R5). 5. but others like 1D. If event reporting mode is configured.3. 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. In periodic reporting mode. • Take into account all received event 1B (if one RL is remaining at least) or the last one if isOne1bStorageAllowed is set to TRUE. all measurement received during this phase are put aside. RB adaptation …). 1E. • Take into account the last received event 1J (if there is enough room in Active Set at least). Based on the events received during the SRLR time window. the RNC applies a specific process described below. incoming PS on a CS call.2. 1C and 1J can be reported periodically. as critical events may have been received during the SRLR phase.2 SRLR BLIND WINDOW Synchronous Radio Link Reconfiguration (SRLR) may be performed at any time during connection lifetime (Always-On.2. This process is also applicable to other RRC procedures such as “active set update”. In event reporting mode. • Take into account the last received event 1E (if there is enough room in Active Set at least).

5. they are used to take a mobility decision at the end of a Blocking Phase. 1J The RNC processes the last 1A. 6A. is treated by the RNC. 5. The Active Set is supported over Iur. 1C.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.1 ALGORITHM FOR PERIODIC REPORTING MODE The active set evaluation process is characterized by: . 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. 1E or 1J event received during the SRLR window. 1E.4 PARAMETERS Object/Class FDDCell Class3 RadioAccessService Class3 Definition Flag which enables the event reporting mode enables/disables the storage of only one event 1B on a per RNC basis Name isEventTriggeredMeasAllowed isOne1bStorageAllowed 5.2. If received during the SHO blocking window (i.2.3.2.3. 5. during the NBAP procedure execution).4 EVENTS 2D.2. The Hard HO treatment has priority on Soft HO. so that the corresponding Radio Link is added to the active set just after the completion of the SRLR.3.3 EVENT 1D The last 1D event received during the SRLR window. In case of the change of the DLAsConf.3. 5. 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. ACTIVE SET MANAGEMENT The Active Set is managed differently according to the reporting mode (periodic or intra-frequency event triggered).decision based on relative criterion: threshold applied on (max CPICH Ec/No – CPICH Ec/No(cell to be evaluated)) Passing on or copying of this document. 1J events with the old configuration (previous DLAsConf) are available. Note: RNC does not check cell barring information in active set management. 1B and 1F are treated by the RNC at the end of a Blocking Phase.2.2 EVENT 1B.1 EVENT 1A. 5. 1C. 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. 2F.e.periodic evaluation: performed at each reception of periodic RRC MEASUREMENT REPORT . the received 1A.3. 6B These events are processed when received since they correspond to arm and stop timer. Even if the new configuration is different.2.2. which has priority on alarm measurements activation.3. 1D.2.06/EN Approved_Standard 17/Sep/2010 Page 168/244 . 1E.2. 1C. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.

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 3. 4. the radio link is removed from the active set.06/EN Approved_Standard 17/Sep/2010 Page 169/244 . 2.If all the cells of the current active set are non eligible. Based on the field observations and CDMA experience.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.2 ENHANCED ALGORITHM FOR PERIODIC REPORTING MODE The algorithm specified in the section above is based on a relative threshold comparison. CPICH Ec/No Max CPICH Ec/No add_threshold drop_threshold Cell in current active set Cell not in current active set Measurement periods Figure 65: algorithm for active set management 5. keep at least the best one Compare (Ec/No(0) – Ec/No(i)) to add_threshold for cells not in the current active set . or a comparison with an absolute threshold ShoLinkAdditionCpichEcNoThreshold. Find the cell with the highest CPICH Ec/No. 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. Passing on or copying of this document.3. or a comparison with an absolute threshold ShoLinkDeletionCpichEcNoThreshold. The algorithm is the following: 1. an “enhanced SHO management algorithm” is available. the radio link is added to the active set. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.Keep as eligible in the active set those which Ec/No(0)-Ec/No(i) < drop_threshold .Put as eligible those which Ec/No(0)-Ec/No(i) < add_threshold Rank all the eligible cells . All the parameters used in the algorithm above are attached to the current primary cell. working as follows: • If a radio link from the active set satisfies either the relative drop_threshold comparison.Cells to be dropped = the others . if a radio link from the monitored set satisfies either the relative add_threshold comparison. Let’s call it cell(0) with Ec/No(0) Compare (Ec/No(0) – Ec/No(i)) to drop_threshold for cells in the current active set . • Similarly.

referred to as drop_threshold in the section above threshold to add a cell in the active set.06/EN Approved_Standard 17/Sep/2010 Page 170/244 .UMTS Radio Mobility The first condition is illustrated by the following picture. referred to as add_threshold in the section above legAdditionDelta Passing on or copying of this document.link addition This algorithm can be completely or partially de-activated. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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.3 PARAMETERS FOR PERIODIC REPORTING MODE The parameters are: Name legDroppingDelta Object/Class SoftHoConf Class3 SoftHoConf Class3 Definition threshold to withdraw a cell from the active set.link deletion The second condition is illustrated by the following picture.3. Links already in the Active Set Max CPICH Ec/No Measured Links Delta Add Threshold ShoLinkAdditionCpichEcNoThreshold Link to be added to the Active Set Cells 1 2 3 4 5 6 7 Links in the Active Set (final) Figure 67: SHO enhancement . 5. Links already in the Active Set Max CPICH Ec/No Measured Links ShoLinkDeletionCpichEcNoThreshold Delta Drop Threshold Radio Link to be deleted Cells 1 2 3 4 5 6 7 Links in the Active Set (final) Figure 66: SHO enhancement . Please check the [parameter] section for further details.

Cell Individual Offset CIO will be used in the AS evaluation algorithm only when at least one of the ShoLinkXxxAbsoluteThresholdEnable flag is True.4 CASE OF INTRA-FREQUENCY EVENT-TRIGGERED REPORTING MODE DESCRIPTION OF EVENT-TRIGGERED REPORTING MEASUREMENTS BASED ON RELATIVE THRESHOLDS 5. • H1a and H1b refer to as hysteresis parameters. 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. based on the following assumptions: The active set is limited to 2 links – for illustration purpose only Passing on or copying of this document. The following picture illustrates a case where 1C event is needed. events 1A and 1B are used. • MBest and MOld refer to as CPICH Ec/No measurements made by the mobile. as with the existing “periodic reporting” mechanism. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. the set of parameters which will be used for the algorithm will be a default set defined per Neighbour RNC. They can be set to the value of hysteresis1A and hysteresis1B. As in [A4].3. • CIONew and CIOOld refer to as Cell Individual Offset. Radio Link Deletion) are actually triggered by the reception of event 1A (resp. 1B) from the mobile.UMTS Radio Mobility maxActiveSetSize SoftHoConf Class3 SoftHoConf Class3 SoftHoConf Class3 SoftHoConf Class3 SoftHoConf Class3 ShoLinkDeletionCpichEcNoThreshold ShoLinkAdditionCpichEcNoThreshold ShoLinkDeletionAbsoluteThresholdEnable ShoLinkAdditionAbsoluteThresholdEnable maximum number of legs in macrodiversity (from 1 to 6). They are configured to the values of cpichEcNoReportingRange1A and cpichEcNoReportingRange1B respectively. the triggering condition has to be valid for a period of time named “time to trigger”. event 1A allows the same behavior as with current algorithm. it is critical to put the strongest cells in the active set (among the ones being reported by 1A).3. referred to as max_legs in the section above Absolute threshold for radio link deletion Absolute threshold for radio link addition If enabled. This parameter is configurable for each event. 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.    i =1  In order to trigger a report. 5. so that Radio Link Addition (resp.4. For that purpose.06/EN Approved_Standard 17/Sep/2010 Page 171/244 . the absolute threshold for radio link deletion is applied If enabled.1 In event triggered mode. In case of “SHO leg number” limitation or if the Active Set is full. • R1a and R1b refer to as reporting range parameters. This works the same way for event 1B:  NA  10 ⋅ LogM Old + CIOOld ≤ W ⋅ 10 ⋅ Log  ∑ M i  + (1 − W ) ⋅ 10 ⋅ LogM Best − ( R1b + H 1b / 2). the condition for event 1A reporting is as follows: 10 ⋅ LogM New + CIONew  NA  ≥ W ⋅10 ⋅ Log  ∑ M i  + (1 − W ) ⋅10 ⋅ LogM Best − ( R1a − H1a / 2)    i =1  If W is set to 0.

Unless 1C is available. It can is set to the value of hysteresis1C. timeToTrigger1B. MBest and MInAS refer to as CPICH Ec/No measurements made by the mobile. timeToTrigger1C). Passing on or copying of this document. the triggering condition has to be valid for a period of time named “time to trigger”. Further on. However. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger1A. so that the active set is based on the strongest cells from the monitored set. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. This may result in the scenario shown in figure below. H1c refer to as hysteresis parameter. event 1A is reported. The recommended value for timeToTrigger1B will be greater than that for timeToTrigger1C. As in [A1]. However the non-active cell to appear as a candidate for replacement is too weak and should not be added to the active set. W = 0. As Cell 3 crosses R1A.06/EN Approved_Standard 17/Sep/2010 Page 172/244 . as the active set size is limited to 2 radio links only. H1A = H1B = 0 Measurement quantity P CPICH 1 P CPICH 2 R1B R1A P CPICH 3 Reporting event 1A Reporting event 1C Time Figure 68: event 1C use case At the beginning. as in this case cell 2 remains above R1B. as 1C is reported. 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. this cannot be achieved. cell 1 and 2 are part of the active set. cell 1 being the strongest one.UMTS Radio Mobility Events 1A and 1B are configures as above (CIO = 0. cell 3 is not added to the active set. cell 3 is added and cell 2 is removed. In order to trigger a report. event 1C is triggered by the following condition: 10 ⋅ LogM New + CIONew ≥ 10 ⋅ LogM InAS + CIOInAS + H 1c / 2 • • • CIONew and CIOInAS refer to as Cell Individual Offset.

06/EN Approved_Standard 17/Sep/2010 Page 173/244 .4. namely 1E and 1F on CPICH Ec/No measurements.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. but the non-active cell is too weak and should not be added to the active set. 5. 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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) . 1C and 1B (only from Release 5) as long as the reporting criteria are still valid. The 2nd active set cell should be just removed from the active set. The following events need to be configured: Reporting quantity CPICH Ec/No Event id 1A Triggering condition Monitored set cells or Monitored and Detected set cells Active set cells Monitored set cells CPICH Ec/No CPICH Ec/No 1B 1C The RRC protocol allows configuring periodic reporting of event 1A.UMTS Radio Mobility Pilot strength Strongest active set cell Reporting Range for e1a 2 nd active set cell Reporting Range for e1b Time-to-Trigger e1b Non-active cell Time-to-Trigger e1c Problem: e1c is sent earlier than e1b. The following equations [A1] describe the “triggering condition” for 1E: 10 ⋅ LogM New + CIO New ≥ T1e + H 1e / 2 Passing on or copying of this document.3.2 DESCRIPTION OF EVENT-TRIGGERED REPORTING MEASUREMENTS BASED ON ABSOLUTE THRESHOLDS This will be achieved by using 2 events.

Measurement quantity P CPICH 1 P CPICH 2 Absolute threshold of 1E event Absolute threshold of 1F event P CPICH 3 Reporting event 1E Reporting event 1F Time Figure 70: Events 1E and 1F In order to trigger a report. MNew refers to as CPICH Ec/No or CPICH RSCP measurement made by the mobile. the RNC behaviour is as follows: If either 1A or 1E (if configured) event is received for a cell of the monitored set. The following picture illustrates event 1E and 1F reporting. 5. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.4. only the best ordered in the IE “Event Results” of the Measurement Report is added. 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. in case CIO and H parameters are set to 0. They can is set to the value of hysteresis1E and hysteresis1F. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger1E. timeToTrigger1F). T1e and T1f refer to as absolute thresholds. • • • • H1e and H1f refer to as hysteresis parameters. the triggering condition has to be valid for a period of time named “time to trigger”. CIOOld and CIONew refer to as Cell Individual Offset. the corresponding radio link is (possibly) added to the active set. 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 Passing on or copying of this document. In case of several Monitored Set to Add. In this figure.3 • ALGORITHM In case of intra-frequency Event-Triggered Reporting mode. the P-CPICH 3 will trigger an event 1E and P-CPICH 1 will trigger an event 1F.UMTS Radio Mobility and 1F: 10 ⋅ LogMOld + CIOOld ≤ T1 f − H1 f / 2.3.06/EN Approved_Standard 17/Sep/2010 Page 174/244 . The events used to support this feature would be as follows: Reporting quantity CPICH Ec/No Event id 1E Triggering condition All Monitored set cells or Monitored and Detected set cells All active set cells CPICH Ec/No 1F Please note that CIO is a configurable parameter defined against the primary cell for each of its neighbour cell.

the radio link addition/deletion absolute criteria makes use of CIO parameter defined in the RNC database (Cell Individual Offset). 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.4). Therefore: • If the “SHO enhancement” feature (release UA04. 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. In this case event 1C will be acted upon as if event 1B would have been received i. the initial power of the Radio Link to be added not only depends from CPICH Ec/No measurement of the new cell. only a radio link removal will result. If several Active Set cells are included in the “Event Results” and are worse than the Monitored Set cell to add. 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. the RNC will not have a special handling to avoid a potential ping-pong generated by RNC actions (i. 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.1) is active. As in “SHO enhancement” specification for release UA04.5. the CIO will not be sent to the UE and events 1E and 1F are not configured.3) which in consequence does no more represent the complete neighborhood of the active set. In this version. In this case. 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.2.6.3. If Detected Set cells are reported the RNC will trace this as specified in § 5. Note: If event 1F identifies the Primary cell to be removed then the event is ignored. 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). the CIO will be sent to the UE through the Measurement Control message.06/EN Approved_Standard 17/Sep/2010 Page 175/244 . but also on the measurements reported for the other cells in the active set. 1C and 1D (for R5 UEs if configured).UMTS Radio Mobility added in the active set unless special conditions for event 1A do apply. 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. Note: The release information above is added in order to distinguish between this feature (refer to [R5])and the later SHO enhancements.e. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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). as in the current “SHO enhancement” implementation • If the “SHO enhancement” feature (release UA04. As specified in [R10]. 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 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.e.3 Passing on or copying of this document. • • If either 1B or 1F (if configured) event is received for a cell of the active set. the RNC will replace the cell in the Active Set indicated in the measurement report with the cell triggering this event. However a non-active cell (i. Detected Set cells will be added to the active set under the same conditions as described for event 1A above.1) is not active. the corresponding radio link is removed from the active set If 1C event is received.e. CIO will be applied by the UE on events 1E and 1F. but also on events 1A. 1B. This is still the case when event-triggered measurement reports are used. the RNC deletes them: so the RNC can resize the Active Set.1.

39 Intra-freq meas rep criteria Event 1A Event 1B … Figure 71: intra-frequency Measurement Control message structure In the §10.06/EN Approved_Standard 17/Sep/2010 Page 176/244 .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. all intra-frequency event reports are configured in RLC Acknowledged Mode. §10.7. some events reporting are not repeated.36 Intra-freq measurements Common part (meas quantities…) §10. as it is not needed by 3GPP 25.3. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.3.2. Up to 8 events can be configured in a single message.7.4.4.3. 5.4 CONFIGURATION As only one intra-frequency measurement quantity is actually required (CPICH Ec/No). As in [A4].2.4.3. The overall structure of the intra-frequency MEASUREMENT CONTROL message is as follows. all intra-frequency events and measurements can be configured in a single message.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.17 Meas.UMTS Radio Mobility 5.331 specifications “not used” means the IE is optional and not used in this implementation.1 1A EVENT CONFIGURATION Need OP MP CV–clause 0 CV–clause 6 CV–clause 2 CV–clause 1 Parameter Value “1a” Not needed “Monitored Set Cells” or “Monitored and Detected Set cells” Use cpichEcNoReportingRange1A parameter Not used Information Element/Group name Parameters required for each event >Intra-frequency event identity >Triggering condition 1 >Triggering condition 2 >Reporting Range Constant >Cells forbidden to affect Reporting range Passing on or copying of this document. In order to limit the risk of loosing an event on the radio interface because of bad transmission conditions. Control Common part (reporting type…) §10.7.3.

when present. This IE is part of Alcatel-Lucent implementation and is sent each time event 1B is configured. and ignored by R99 UEs. meaning that this IE.4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. so that if the active set is limited by the maxActiveSetSize parameter. This change is made on a backward compatible way. Passing on or copying of this document. the value of this IE shall be set to (maxActiveSetSize-1). will be decoded by R5 and above UE. 5.UMTS Radio Mobility Information Element/Group name >W >Hysteresis >Threshold used frequency >Reporting deactivation threshold >Replacement activation threshold >Time to trigger >Amount of reporting >Reporting interval >Reporting cell status Need CV–clause 2 MP CV-clause 3 CV–clause 4 CV-clause 5 MP CV–clause 7 CV–clause 7 OP Parameter Value Use weight1A parameter Use hysteresis1A parameter Not needed Use value (maxActiveSetSize-1) Not needed Use timeToTrigger1A parameter Use amountRep1A parameter Use repInterval1A parameter 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. a periodical reporting IE has been added for event 1B.4.3.06/EN Approved_Standard 17/Sep/2010 Page 177/244 . The purpose of this IE is to avoid the UE to report event 1A if the active set size limit is reached.2 1B EVENT CONFIGURATION Need OP MP CV–clause 0 CV–clause 6 CV–clause 2 CV–clause 1 CV–clause 2 MP CV-clause 3 CV–clause 4 CV-clause 5 MP CV–clause 7 CV–clause 7 OP CV–clause 9 Parameter Value “1b” “Active Set Cells” Not needed Use cpichEcNoReportingRange1B parameter Not used Use weight1B parameter Use hysteresis1B parameter Not needed Not needed Not needed Use timeToTrigger1B parameter Not needed Not needed Use maxNbReportedCells1B parameter Use amountOfRep1B and repInterval1B parameters Information Element/Group name Parameters required for each event >Intra-frequency event identity >Triggering condition 1 >Triggering condition 2 >Reporting Range Constant >Cells forbidden to affect Reporting range >W >Hysteresis >Threshold used frequency >Reporting deactivation threshold >Replacement activation threshold >Time to trigger >Amount of reporting >Reporting interval >Reporting cell status >Periodical reporting information-1b Remark: As a 3GPP R5 improvement.

4.06/EN Approved_Standard 17/Sep/2010 Page 178/244 . 5. The purpose of this IE is to avoid the UE to report event 1C if the active set size limit is not reached.3.3.3 1C EVENT CONFIGURATION Need OP MP CV–clause 0 CV–clause 6 CV–clause 2 CV–clause 1 CV–clause 2 MP CV-clause 3 CV–clause 4 CV-clause 5 MP CV–clause 7 CV–clause 7 OP Parameter Value “1c” Not needed Not needed Not needed Not used Not needed Use hysteresis1C parameter Not needed Not needed Use maxActiveSetSize parameter Use timeToTrigger1C parameter Use amountOfRep1C parameter Use repInterval1C parameter Use maxNbReportedCells1C parameter Information Element/Group name Parameters required for each event >Intra-frequency event identity >Triggering condition 1 >Triggering condition 2 >Reporting Range Constant >Cells forbidden to affect Reporting range >W >Hysteresis >Threshold used frequency >Reporting deactivation threshold >Replacement activation threshold >Time to trigger >Amount of reporting >Reporting interval >Reporting cell status Remark: The “Replacement activation threshold” indicates the minimum number of cells allowed in the active set in order for event 1C to occur.4. Use cpichEcNoThresholdUsedFreq1E Not needed Not needed Use timeToTrigger1E parameter Not needed Not needed Use maxNbReportedCells1E parameter Information Element/Group name Parameters required for each event >Intra-frequency event identity >Triggering condition 1 >Triggering condition 2 >Reporting Range Constant >Cells forbidden to affect Reporting range >W >Hysteresis >Threshold used frequency >Reporting deactivation threshold >Replacement activation threshold >Time to trigger >Amount of reporting >Reporting interval >Reporting cell status Passing on or copying of this document.4 1E EVENT CONFIGURATION Need OP MP CV–clause 0 CV–clause 6 CV–clause 2 CV–clause 1 CV–clause 2 MP CV-clause 3 CV–clause 4 CV-clause 5 MP CV–clause 7 CV–clause 7 OP Parameter Value “1e” Not needed “Monitored Set Cells” or “Monitored and Detected Set Cells” Not needed Not used Not needed Use hysteresis1E parameter.4.4.UMTS Radio Mobility 5. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.

use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.3.UMTS Radio Mobility 5.4.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)”.5 1F EVENT CONFIGURATION Need OP MP CV–clause 0 CV–clause 6 CV–clause 2 CV–clause 1 CV–clause 2 MP CV-clause 3 CV–clause 4 CV-clause 5 MP CV–clause 7 CV–clause 7 OP Parameter Value “1f” “Active Set Cells” Not needed Not needed Not used Not needed Use hysteresis1F parameter. defines the weight to Passing on or copying of this document. Use cpichEcNoThresholdUsedFreq1F Not needed Not needed Use timeToTrigger1F parameter Not needed Not needed Use maxNbReportedCells1F parameter Information Element/Group name Parameters required for each event >Intra-frequency event identity >Triggering condition 1 >Triggering condition 2 >Reporting Range Constant >Cells forbidden to affect Reporting range >W >Hysteresis >Threshold used frequency >Reporting deactivation threshold >Replacement activation threshold >Time to trigger >Amount of reporting >Reporting interval >Reporting cell status 5. Name isDetectedSetCellsAllowed detectedSetCellAddition cpichEcNoReportingRange1A Object/Class RadioAccessService Class3 FDDCell Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 hysteresis1A Definition Allows tracking of detected cells Allows addition of detected set cells to the active set. CPICH Ec/No hysteresis for link addition in Active Set weight1A timeToTrigger1A amountRep1A repInterval1A maxNbReportedCells1A cpichEcNoReportingRange1B MeasurementConfClass Class3 MeasurementConfClass Class3 MeasurementConfClass Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 hysteresis1B weight1B defines the weight to configure for the triggering of event 1A in Full Event mode Period of time during which the event condition has to be satisfied before sending event 1A Amount of periodical reporting for event 1A Interval of periodical reporting for event 1A Maximum allowed number of cells to report with event 1A Relative CPICH Ec/No threshold for SHO Radio Link Deletion. Relative CPICH Ec/No threshold for SHO Radio Link Addition.3. CPICH Ec/No hysteresis for link deletion in Active Set .4.06/EN Approved_Standard 17/Sep/2010 Page 179/244 .

UMTS Radio Mobility configure for the triggering of event 1B in Full Event mode Period of time during which the event condition has to be satisfied before sending event 1B Allows storage of only the latest received event 1B while another procedure is in progress Amount of periodical reporting for event 1B Interval of periodical reporting for event 1B Maximum allowed number of cells to report with event 1B CPICH Ec/No hysteresis for cell replacement in Active Set Period of time during which the event condition has to be satisfied before sending event 1C Amount of periodical reporting for event 1C Interval of periodical reporting for event 1C Maximum allowed number of cells to report with event 1C Allows to prevent weak nonactive radio links from being added to the active set If enabled. the absolute threshold for radio link deletion is applied CPICH Ec/No hysteresis for absolute threshold link deletion in Active Set Period of time during which the event condition has to be satisfied before sending event 1F Maximum allowed number of cells to report with event 1F timeToTrigger1B UsHoConf Class3 isOne1bStorageAllowed Radio Access Service Class 3 amountRep1B repInterval1B maxNbReportedCells1B hysteresis1C timeToTrigger1C MeasurementConfClass Class3 MeasurementConfClass Class3 MeasurementConfClass Class3 UsHoConf Class3 UsHoConf Class3 amountRep1C repInterval1C maxNbReportedCells1C isEnhanced1cHandlingAllowed MeasurementConfClass Class3 MeasurementConfClass Class3 MeasurementConfClass Class3 Radio Access Service Class 3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 isEvent1EUsed hysteresis1E timeToTrigger1E maxNbReportedCells1E cpichEcNoThresholdUsedFreq1E MeasurementConfClass Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 isEvent1FUsed hysteresis1F timeToTrigger1F maxNbReportedCells1F MeasurementConfClass Class3 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. If enabled.06/EN Approved_Standard 17/Sep/2010 Page 180/244 . the absolute threshold for radio link addition is applied CPICH Ec/No hysteresis for absolute threshold link addition in Active Set Period of time during which the event condition has to be satisfied before sending event 1E Maximum allowed number of cells to report with event 1E Absolute CPICH Ec/No threshold for SHO Radio Link Addition.

• Number of Event 1E triggered by a Cell of the Monitored Set (triggered by event 1E reception). If a Detected Cell is reported by the UE. for a set of calls.6. • Number of Event 2D (triggered by event 2D reception). Per neighboring RNC (The Primary RL of the UE is on this Neighboring RNC).g. • Number of Event 2D (triggered by event 2D reception). • Number of Event 1F (triggered by event 1F reception). the intra-frequency part of the RRC Measurement Report message and the scrambling code of the Detected Cell are traced. o event 1E. 5. 15 seconds – static value cpTimerFileringCallFailureTrace -). • Number of Event 1E triggered by a Cell of the Monitored Set (triggered by event 1E reception).3. 5. • Number of Event 1C (triggered by event 1C reception). • Number of Event 6B (triggered by event 6B reception).6 5. • Number of Event 1B (triggered by event 1B 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 2F (triggered by event 2F reception). 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).06/EN Approved_Standard 17/Sep/2010 Page 181/244 . where triggering Cells are both Detected Set Cells and Monitored Set Cells. • Number of Event 1C (triggered by event 1C reception). • Number of Event 1J (triggered by event 1J reception). • To report the measurement of the Detected Cells in the Measured Result part of these events.isDetectedSetCellsAllowed is TRUE.1 PERFORMANCE MANAGEMENT COUNTERS The following counters are defined: Per FDDCell (the Primary RL of the UE is on this FDDCell).2 TRACES If the MIB flag RadioAccessService. 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 6B (triggered by event 6B reception).6.3. • Number of Event 1D (triggered by event 1D reception).3. where triggering Cells are both Detected Set Cells and Monitored Set Cells. For the Call Failure Trace. This filtering mechanism allows to have at most one Call Failure Trace in a given period (e. 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. • Number of Event 6A (triggered by event 6A reception). the RNC requests the UE: • to trigger the following events on Detected Cells also: o event 1A. • 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).UMTS Radio Mobility cpichEcNoThresholdUsedFreq1F UsHoConf Class3 Absolute CPICH Ec/No threshold for SHO Radio Link Deletion. • Number of Event 6A (triggered by event 6A reception). • Number of Event 1B (triggered by event 1B reception). • Number of Event 1F (triggered by event 1F reception). • Number of Event 2F (triggered by event 2F reception). Passing on or copying of this document. • Number of Event 1D (triggered by event 1D reception).

removed from) the E-DCH active set. 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 Passing on or copying of this document. All links added to (resp. removed from) the DCH active set are also added. in this case the new primary cell = current primary cell . 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. to (resp.1 PRIMARY CELL DETERMINATION DESCRIPTION The primary cell is a sort of reference cell for the UE. parameters with a cell granularity which are to be used for a mobile are those corresponding to its primary cell. if compatible. The serving link is always the primary cell of the DCH active set. the E-DCH active set can have up to 4 links that are a subset of DCH active set. 5. 5.4. 5.0. this cell is added to E-DCH active set (as serving) and the former primary is removed from EDCH active set.06/EN Approved_Standard 17/Sep/2010 Page 182/244 . refer to [R6] UMT/SYS/DD/018827 E-DCH System Specification.3. If the E-DCH active set is full and a new primary cell is elected which is not in EDCH active set.or this candidate cell is different from the current primary cell. On event 1J report.4.7 E-DCH ACTIVE SET MANAGEMENT From UA06.e.either this candidate cell = current primary cell. The algorithm is the following: After the active set evaluation process. 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). Note: RNC does not check cell barring information in primary cell determination. i.2 CASE OF INTRA-FREQUENCY PERIODIC REPORTING MODE The determination of a new primary cell is performed after each “active set evaluation” process. For all details on this feature. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.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: .4. It is used for monitored cells set determination and also as a pointer to mobility parameters.UMTS Radio Mobility 5. a candidate cell for new primary cell is selected according to the following condition: .

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. In this formula. and only if requested by a configuration flag present in event 1D configuration sent in Measurement Control message: 10 ⋅ LogM NotBest + CIO NotBest ≥ 10 ⋅ LogM Best + CIOBest + H 1d / 2 • H1d refers to as hysteresis parameter.4.3.06/EN Approved_Standard 17/Sep/2010 Page 183/244 . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Passing on or copying of this document. Event 1D is reported once cell (2) measurement quantity exceeds cell (1) by H1d/2. either cell dependent (through the Cell Individual Offset parameter) or absolute (through the H1D parameter). 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.1 The primary cell determination will be usually based on event 1D reception.UMTS Radio Mobility 5.3 CASE OF INTRA-FREQUENCY EVENT-TRIGGERED REPORTING MODE DESCRIPTION 5. in case CIO parameters are set to 0. CIO will only be applied by R5 UEs. cell (1) being the current primary.4.3. This parameter will be set to the value of hysteresis1D parameter.4). as in the following formula (applicable to CPICH Ec/No measurements): 10 ⋅ LogM NotBest ≥ 10 ⋅ LogM Best + H 1d / 2 In 3GPP R5. a hysteresis can be used. • • CIONotBest and CIOBest refer to as Cell Individual Offset. MBest and MNotBest refer to as CPICH Ec/No measurements made by the mobile. Measurement quantity H1d/2 P CPICH 1 P CPICH 2 P CPICH 3 Reporting event 1D Time Figure 72: event 1D As in existing periodic measurement based algorithm. The following picture illustrates event 1D reporting. the definition of event 1D has been changed to take into account CIO parameters.

If the event 1D is triggered by a monitored cell. 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. When CIO is used it may happen that 1A event is not triggered but 1D event is triggered.1 1D EVENT CONFIGURATION Information Element/Group name Parameters required for each event >Intra-frequency event identity >Triggering condition 1 >Triggering condition 2 >Reporting Range Constant >Cells forbidden to affect Reporting range >W >Hysteresis >Threshold used frequency >Reporting deactivation threshold >Replacement activation threshold >Time to trigger >Amount of reporting >Reporting interval >Reporting cell status >Use CIO Need OP MP CV–clause 0 CV–clause 6 CV–clause 2 CV–clause 1 CV–clause 2 MP CV-clause 3 CV–clause 4 CV-clause 5 MP CV–clause 7 CV–clause 7 OP CV–clause 10 Parameter Value “1d” Not needed Not needed Not needed Not used Not needed Use hysteresis1D parameter.1) is enabled and the useCIOfor1D is set to TRUE then CIO values are configured in the UE if the UE is Release 5.UMTS Radio Mobility 5.4 / configuration for common part of Measurement Control message. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. the RNC stores the new primary. then the event1D will provide the replacement of the worse cell in the Active Set. 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. 5. Note: The release information above is added in order to distinguish between this feature (refer to [R5]) and the later SHO enhancements. If “SHO enhancements” (release UA04.3 CONFIGURATION Refer to § 5. the RL will be added in the Active Set if not full.3.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. Not needed Not needed Not needed Use timeToTrigger1D parameter Not needed Not needed Use maxNbReportedCells1D parameter Use useCIO1D parameter Passing on or copying of this document.3. If the Active Set is full. 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.3. 5. 1C are also configured (see section 5.3.3.4. Since the events 1A. Based on the reception of this event. An event 1D will typically be triggered by a cell better than the best in the active set. A new primary cell will also be defined if the current primary cell will be removed due to reception of RL deletion events.4. and applies the current process used in case of change of primary cell.06/EN Approved_Standard 17/Sep/2010 Page 184/244 .2 ALGORITHM The primary cell determination will be based on event 1D reception.4. 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 in dedicated mode.5.4 PARAMETERS The parameters are: Name rrcIntraFreqMeasurementDropPrimaryRlDelta Object/Class UsHoConf Class3 Definition hysteresis for primary cell modification. LIST OF COMPOUNDING CELLS FOR THE MONITORED SET DEFINITION DESCRIPTION 5. depending on the “radio” neighbourhood of this UE. the set of parameters which will be used for the algorithm will be a default set defined per Neighbour RNC. inter frequency – or inter RAT neighbour of each Fdd cell is optimized. inter-frequency and 2G inter-RAT neighbour cells. this compound list to UE A new algorithm (type 1) to compute the compound neighbour cell list has been introduced for intra-frequency. this neighbourhood being either defined by the active set.5. or by measurements. Passing on or copying of this document.06/EN Approved_Standard 17/Sep/2010 Page 185/244 . This section is based on the feature called UMTS composite neighbour list. 5.1 The object of the section is the introduction of dynamic compounding cell lists in connected mode. referred to as DropPriRL in the section above. It applies for calls in cell-DCH state only. 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. 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. through RRC Measurement Control message.4.UMTS Radio Mobility 5. 5.2 APPLICABILITY The feature is efficient if the intra frequency -. Compounding list functionality is the capability for the RNC: o To dynamically create the neighbour list a UE will monitor. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. o To send. 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. This flag indicates if CIO parameter has to be taken into account in 1D triggering condition useCIOfor1D MeasurementConfClass Class3 hysteresis1D UsHoConf Class3 UsHoConf Class3 timeToTrigger1D maxNbReportedCells1D MeasurementConfClass Class3 CPICH Ec/No hysteresis primary cell determination Period of time during which the event condition has to be satisfied before sending event 1D.5.

or the list reaches maxSizeCompoundingList cells. Until: the new monitored cell set goes up to maxNbOfMonitoredCellForNonShoCompoundList cells .3 ALGORITHM The best cell is the cell with the best CPICH Ec/No. Passing on or copying of this document. maxCompoundingListSizeInterFreq or maxCompoundingListSizeInterRAT respectively) is exceeded then the lower priority cells are discarded. when the connection is not engaged in soft or softer HO. If feature compounding list is not activated: • The monitored set is the neighbouring list of the primary cell. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.5. o Or the N first (bests) measured cells and their static neighbour list for dedicated mode.06/EN Approved_Standard 17/Sep/2010 Page 186/244 . 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. Type1 and Type2) are available for intra frequency neighbour cells and two different algorithms (PRL and Type1) are available for inter frequency .UMTS Radio Mobility 5. If feature compounding list is activated: Three different algorithms (PRL. it selects the cell with the highest measured quality of the active set cell In case of same quality. The behavior is the same as if feature compounding list is not activated. when the connection is engaged in soft or softer HO. • Type 1: Compound neighbour list is build from all active set 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. • 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. 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. 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. until: the last leg and its static neighborhood list for dedicated mode has been added.or inter RAT neighbour cells. or the list reaches maxSizeCompoundingList cells.

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. Whatever the neighbor building list method. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. change of primary cell or active set update has occurred. The compound intra frequency neighbour cell list shall be computed when • • • • state transition to Cell_DCH.06/EN Approved_Standard 17/Sep/2010 Page 187/244 .4 PARAMETERS Object/Class RadioAccessService Class3 RadioAccessService Class3 RadioAccessService Class3 RadioAccessService Class3 FDDCell Class 3 Name maxCompoundingListSizeIntraFreq maxCompoundingListSizeInterFreq maxCompoundingListSizeInterRAT Definition Maximum number of cells in the intra-freq compounded list Maximum number of cells in the inter-freq compound list Maximum number of cells in the 2G inter-RAT compound list Used to activate or inhibit the compounded list feature isCompoundingCellListActivated typeOfCompoundingNeighbourListIntraFreq Used to determine the algorithm for intra-frequency neighbor list creation for dedicated measurements. Used when primary cell is on typeOfCompoundingNeighbourListIntraFreq NeighbouringRNC Class 3 Passing on or copying of this document. the neighbour list updates only include the cells to be removed and to be added (delta between the previous neighbourhood and the new neighbourhood).UMTS Radio Mobility or until the last measured cell. 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. successful hard handover. 5. 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. Type1. Possible values are PRL. Type2 Used to determine the algorithm for intra-frequency neighbor list creation for dedicated measurements.

Type2 Used to determine the algorithm for inter-frequency neighbor list creation for dedicated measurements. Type1. Type1 Used to determine the algorithm for inter RAT neighbor list creation for dedicated measurements. Used when primary cell is on DRNC. Used when primary cell is on DRNC. Possible values are PRL.06/EN Approved_Standard 17/Sep/2010 Page 188/244 . The minimal number of intrafrequency neighbor cells of the primary cell on DRNC to be definitely included in the compound neighbor list. Possible values are PRL. The minimal number of interfrequency neighbor cells of the primary cell to be definitely included in the compound neighbor list. The minimal number of 2G inter-RAT neighbor cells of the primary cell to be definitely included in the compound neighbor list. The minimal number of interfrequency neighbor cells of the primary cell on DRNC to be definitely included in the compound neighbor list. Possible values are PRL. Possible values are PRL. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Possible values are PRL. The minimal number of 2G inter-RAT neighbor cells of typeOfCompoundingNeighbourListInterFreq FDDCell Class 3 typeOfCompoundingNeighbourListInterFreq NeighbouringRNC Class 3 typeOfCompoundingNeighbourListInterRAT FDDCell Class 3 typeOfCompoundingNeighbourListInterRAT NeighbouringRNC Class 3 numOfPrimaryCellNeighbourIntraFreq FDDCell Class 3 numOfPrimaryCellNeighbourIntraFreq NeighbouringRNC Class 3 numOfPrimaryCellNeighbourInterFreq FDDCell Class 3 numOfPrimaryCellNeighbourInterFreq NeighbouringRNC Class 3 numOfPrimaryCellNeighbourInterRAT FDDCell Class 3 numOfPrimaryCellNeighbourInterRAT NeighbouringRNC Class 3 Passing on or copying of this document.UMTS Radio Mobility DRNC. Type1 Used to determine the algorithm for 2G inter-RAT neighbor list creation for dedicated measurements. Type1 The minimal number of intrafrequency neighbor cells of the primary cell to be definitely included in the compound neighbor list. Type1 Used to determine the algorithm for inter-frequency neighbor list creation for dedicated measurements.

6.06/EN Approved_Standard 17/Sep/2010 Page 189/244 . • For the UE in URA PCH or CELL PCH state. SIB3.MeasCtrlCellListSizeInterFreq Size of the compound inter-frequency neighbor list VS. SIB6. VS.neighbourCellPrio FDDCell Class 3 FDDCell Class 3 5. VS.6.AggregateCellListAmbiguousCellIntraFreq The aggregate intra-frequency neighbor list contains an ambiguous cell.neighbourCellPrio gsmNeighbouringCellList[].MeasCtrlCellListSizeInterRAT Size of the compound 2G inter-RAT neighbor list VS.4). Info. the behaviour is the same than in Idle date (type 1 paging) Note 1: The SIB7 filling is managed by the NodeB.MeasurementControlCellListSize Size of the compound intra frequency neighbor list VS. 5. they are notified by a SYSTEM INFORMATION CHANGE INDICATION message.ExceededAggregateCellListSizeIntraFreq Amount by which the maximum intra-frequency neighbor list size is exceeded.5. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.ExcdAggrCellListSizeInterFreq Amount by which the maximum inter-frequency neighbor list size is exceeded VS. 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. Note 2: SIB4.5 PERFORMANCE MANAGEMENT The following counters are defined on FDDCell basis • • • • • • • • • VS.ExcdAggrCellListSizeInterRAT Amount by which the maximum 2G inter-RAT neighbor list size is exceeded VS. SIB5.UMTS Radio Mobility the primary cell on DRNC to be definitely included in the compound neighbor list.AggrCellListAmbigCellInterRAT The aggregate 2G inter-RAT neighbor list contains an ambiguous cell 5. SIB11 or SIB12.AggrCellListAmbigCellInterFreq The aggregate inter-frequency neighbor list contains an ambiguous cell.1 MANAGEMENT OF SYSTEM INFORMATION BLOCKS (SIB) SIB UPDATE During procedures like cell search or cell (re)selection. this updated attribute is broadcasted by a System Information Block (SIB1. SIB19Enable and isDynamicSibAlgoWithSBAllowed are set to TRUE (refer to § 4. SIB2. VS. Passing on or copying of this document. SIB12Enable. If the operator modifies an FDD cell attribute. the UE may read some system information (SIB) broadcasted on the FDD cell. • For the UE in cell FACH state. SIB19) as follows: • The SRNC sends the content of all SIB to the NodeB (NBAP System Info Update procedure).5. The priority of intra-frequency or inter-frequency neighbour cells The priority of 2G inter-RAT neighbour cells umtsFddNeighbouringCellList[]. SIB4. SIB12 and SIB19 are sent only if parameters SIB4Enable.

This new algorithm is used if parameter isDynamicSibAlgoWithSBAllowed is set to TRUE. SIB3 and SIB4 shall have the same RP0 repetition period between 32 and 128. SIB1 and SIB7 blocks have the same repetition period set to 16 and a start position set to 2.2. 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.0.06/EN Approved_Standard 17/Sep/2010 Page 190/244 . It uses the following constraints: • Limitation of the number of MIB segments. parameters isSib19Allowed and sib19Enable are set to TRUE. SIB6. SIB12 and SIB19 shall have the same RP1 repetition period between 32 and 256. 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. It shall not exceed one segment.0. In UA06. with introduction of SIB4 and SIB12. The setting of RP0 has a higher priority than RP1 i. This new algorithm is used if parameter isDynamicSibAlgoWithSBAllowed is set to TRUE. SIB11. the dynamic SIB scheduling algorithm is modified.2 SIB REPETITION PERIOD In UA05. with introduction of SIB19. SIB6 and SIB11 shall have a RP1 repetition period between 32 and 256. SIB5. The SB1 repetition period is set to the lowest repetition period of SIB(s) (RP0 or RP1) which may be addressed by SB1. 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]. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.6. the dynamic SIB scheduling algorithm is modified. • • • • • In UA07. SIB1 and SIB7 blocks have the same repetition period set to 16 and a start position set to 2. • • • • • Passing on or copying of this document. SIB2. SIB2.1. SIB11 and SIB12 shall have the same RP1 repetition period between 32 and 256. MIB block has a repetition period set to 8 and a position set to 0 .e. SIB5. SIB2. MIB block has a repetition period set to 8 and a position set to 0 . The algorithm uses the following constraints: MIB block has a repetition period set to 8 and a position set to 0 . SIB3 and SIB4 shall have the same RP0 repetition period between 32 and 128. the algorithm tries to find the lowest repetition period value for RP0 first then for RP1. SIB6. SIB5. It uses the following constraints: • Limitation of the number of MIB segments.UMTS Radio Mobility 5. SIB3 shall have a RP0 repetition period between 32 and 128. It shall not exceed one segment. The SB1 repetition period is set to the lowest repetition period of SIB(s) (RP0 or RP1) which may be addressed by SB1. SIB1 and SIB7 blocks have the same repetition period set to 16 and a start position set to 2.

These UEs acquire intra-frequency configuration contained in SIB11. i. This is what is done in NodeB 2 in the figure above. They can start and report their intra-frequency measurements without waiting any RRC Measurement Control message. 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).e. The MRC (Maximum Ratio Combining) algorithm implemented in the BTS makes use of conventional "Rake receiver" techniques. See reference document [R3] UMT/SYS/DD/013000 Mobility Performance Improvements. This allows the activation of the intra-frequency measurement event 1A for each mobile entering in Cell-DCH state. or UDP port for IP) for the same transport bearer (DCH. For event triggered reporting only event 1A is configured. At the SRNC level: All the Radio Links terminating at the SRNC level are recombined by the SRNC (i. DHO MANAGEMENT This section provides an overview of the management of diversity handover (uplink) in Alcatel-Lucent UTRAN nodes. MSC/ SGSN Iu Iur SRNC DRNC Iub NodeB 1 NodeB 2 NodeB 3 UE Figure 73: Macro-diversity in uplink At the NodeB level: If several radio links are active for the same UE in a NodeB.8. Radio Link recombination is not supported at the DRNC. MAC-d flow for HS-DSCH or E-DCH) on the Iub for all combined radio links. the data streams from NodeB 1 and the 2 streams from the Iur in the figure above). so that there is only one transport connection (AAL2 CID for ATM. Passing on or copying of this document.e. the NodeB performs radio link 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). It means that. 5. all the different paths (or at least the ones received with the highest energy) are recombined in the rake receiver before channel decoding.UMTS Radio Mobility 5. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. if a "Radio Link Addition" is received from the SRNC. requesting the DRNC to perform diversity recombination. INTRA-FREQ MEASUREMENTS CONFIGURATION VIA SIB11 The UTRAN provides UEs in other state than Cell-DCH with the configuration of intra-frequency measurements via the SIB11.7.06/EN Approved_Standard 17/Sep/2010 Page 191/244 . In this version.

Any frames with bad CRC is rejected • in each frame. This process works as follows: • the payload CRC of the UP frames (if included) is checked. It also has a positive impact on network capacity as it limits the time during which Compressed Mode is active. The Triggering of the Alarm measurement and the handover is based on the “Fast Alarm” algorithm. Others are rejected. As soon as the first valid measurement is received from the mobile.1 ALARM HANDOVER AND ALARM MEASUREMENTS OVERVIEW In this version of the document. Radio quality Cr Alarm Measurements Reporting phase time Alarm Measurements trigger 1st valid measurement from UE Alarm Handover trigger Figure 74: the fast alarm algorithm Passing on or copying of this document. based on the payload CRC.9. Fast Alarm algorithm description: As illustrated in the figure below. • in case TB from different stream have a "correct" CRCi. the Alarm handover is performed. possibly following by Compressed Mode activation.UMTS Radio Mobility The recombination process performed by the SRNC is actually a frame selection process.19). use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.9. The others reasons for processing a Hard Handover managed by the iMCTA function are: CAC failure and Service (see section 4. the CRCi will be considered as "not correct" regardless of the value received from the NodeB 5. alarm handover is a Hard Handover triggered by the iMCTA function when an Radio alarm condition is detected. This section deals with Alarm radio condition.06/EN Approved_Standard 17/Sep/2010 Page 192/244 . 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”. only TB with a "correct" CRCi are kept. This algorithm allows better reactivity from UTRAN. and TB CRCI (CRC Indicator) and QE (Quality Estimate) fields received from each data stream. if the QE is not good enough. 5. the Alarm measurements are activated once a criteria Cr is fulfilled. the TB with the best QE if eventually selected • anyway. as only one radio criteria is used for both alarm measurement and handover triggering.

At each reception of RRC MEASUREMENT REPORT (which is periodic). AlarmMeasCounter – DownStep) Endif If AlarmMeasCounter > AlarmMeasCounterThreshold then Alarm measurements are requested from the mobile The following figure illustrates this process: Yes Alarm Measurement criteria No Measurement report occasions AlarmMeasCounter AlarmMeasCounterThreshold DownStep UpStep Alarm Meas decision: AlarmMeasCounter > AlarmMeasCounterThreshold time Figure 75: Alarm measurement decision process In case the Alarm Measurement Criteria is valid.2 for further details). Compressed Mode is possibly activated using the Measurement Control message.06/EN Approved_Standard 17/Sep/2010 Page 193/244 . based on mobile needs.4 chapter on Compressed Mode. the following process is applied: If AlarmMeas is valid Increment AlarmMeasCounter by UpStep Else Let AlarmMeasCounter = max (0. For further details on this procedure. the following criteria is evaluated: AlarmMeas = (CPICH Ec/No < ThreshEcMeas) or (CPICH RSCP < ThreshRSCPMeas) for the Primary cell. a Compressed Mode Command message is sent to the UE 3. then the following is applied: 1. as indicated in the mobile "UE capabilities" Information Element".2 ALARM MEASUREMENT ACTIVATION WITH PERIODIC INTRA FREQUENCY MEASUREMENTS Inter-system and inter-frequency measurements are requested under certain radio conditions. Then. please refer to the 6. if compressed mode needs to be reactivated . 2. and once the primary cell has been updated.9. Inter-system or inter-frequency measurements are requested from the mobile using a Measurement Control message (please refer to the section 6. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Passing on or copying of this document.UMTS Radio Mobility 5.

as the radio conditions may change between the measurement activation and the reception of the first measurement report with GSM/inter-frequency measurements.5 s of Compressed Mode for measuring and decoding a first set of neighbouring GSM BSIC. Compressed Mode is also possibly activated. neigh GSM cells. the compressed mode activation condition is still valid. the SRNC decides to request intersystem measurements.06/EN Approved_Standard 17/Sep/2010 Page 194/244 .52 s).. Passing on or copying of this document. neighbouring cells filtered after applying IMSI criteria…) or no suitable Alarm measurement is reported by the mobile within a guard timer period... the mean period of time between the sending of the MEASUREMENT CONTROL and the reception of the related MEASUREMENT REPORT is around 3s. a blind handover towards the blind GSM cell provisioned for the Primary cell may be performed by the RNC. Intrafrequency measurement configuration done in the call setup phase RRC/ Measurement report (intrafreq meas) RRC/ Measurement control (intersystem. inter-frequency) measurements.UMTS Radio Mobility Counter meas hit MR Target cell found Full Periodic Mode Wait for Inter Freq/Inter Rat meas HHO processing time time This is described in the following figure (the use case concerns Intra Frequency periodic measurements with Inter System additional measurements): UE PS/CS call setup Serving RNC RRC/ Measurement control (intrafrequency) . intersystem meas)) RRC/ Measurement control (start CM) Based on intrafrequency measuremenst and depending on mobile capability. RRC/ Measurement report (intrafreq meas. There is one single report for both reported quantities Later on. If still valid. This is explained by: • The current value of Compressed Mode activation time (1.. the Alarm Measurement criteria is checked again. depending on mobile needs The UE is now able to report both intersystem and intrafrequency measurements. and compressed mode is re-activated Figure 76: measurement activation example (inter-system case) As a MEASUREMENT REPORT is received with GSM (resp. 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. As seen on live networks. Remark 1: The additional check on the Alarm Measurement criteria once a measurement is received is needed. If no neighbouring measurement may be requested to the UE but Inter Rat HHO is allowed (for example: CM not possible. a hard handover is triggered towards the chosen target cell. start CM) RRC/ Measurement report (intrafreq meas. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. intersystem meas)) .

1. For CPICH Ec/No based event. Although being related to intra-frequency measurements. the fact that 2D/2F are only triggered by the “Best” cell of the active set allows to save un-necessary measurement reports. 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. timeToTrigger2F).1 A solution based on events 2D and 2F will be used. It is based on event 6A and 6B. In order to trigger a report. ALARM MEASUREMENT ACTIVATION WITH EVENT BASED INTRA FREQUENCY MEASUREMENTS DESCRIPTION 6. They can be set to the value of hysteresis2D and hysteresis2F. the configuration of this parameter is set to the value of the parameter cpichEcNoThresholdUsedFreq2F which is a hysteresis to cpichEcNoThresholdUsedFreq2D. a solution based on UeTxPower is also introduced. For CPICH RSCP based event.UMTS Radio Mobility Remark 2: In case of handover failure. 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) Passing on or copying of this document.1. depending on 2D and 2F “measurement result” configuration. TUsed2f refers to an absolute threshold. events 2D and 2F are defined as follows: QUsed ≤ TUsed 2 d − H 2 d / 2 And QUsed ≥ TUsed 2 f + H 2 f / 2 • • TUsed2d refers to an absolute threshold. For CPICH RSCP based event this is set to the value of the parameter cpichRscpThresholdUsedFreq2D.06/EN Approved_Standard 17/Sep/2010 Page 195/244 . the triggering condition has to be valid for a period of time named “time to trigger”. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. so that QUsedn actually refers to as CPICH Ec/No or CPICH RSCP of the best cell in the active set. 2D and 2F are categorized in the ‘inter-frequency” event group. H2d and H2f refer to as hysteresis parameters. Qused refers to as the quality of the currently used frequency. the configuration of this parameter is set to the value of the parameter cpichRscpThresholdUsedFreq2F which is a hysteresis to cpichRscpThresholdUsedFreq2D. In UA07. which helps to decrease the number of simultaneous intra-frequency events required. This is defined by: • •  NA  QUsed = W ⋅10 ⋅ Log  ∑ M i  + (1 − W ) ⋅10 ⋅ LogM Best    i =1  • W is set to 0. In [A4]. Besides.1. 6. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger2D. In [A4]. For CPICH Ec/No based event this is set to the value of the parameter cpichEcNoThresholdUsedFreq2D.

2 ALGORITHM The Alarm criteria may be set by: • Either event 6A and 6B.06/EN Approved_Standard 17/Sep/2010 Page 196/244 . the triggering condition has to be valid for a period of time named “time to trigger”.1. the list of configured events for alarm handover activation would be as follows (for 2D and 2F. • 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: Passing on or copying of this document.UMTS Radio Mobility In order to trigger a report.1. there is no “triggering” condition. Figure 77: use of Event per Ul Service. => it’s the DL rab which is taken into account. It is used as UsHoConf index id. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. NB: The measurements configuration (for 6A and 6B triggers) are defined per mobility service type. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger6A. any of the active set cells may trigger the event): Reporting quantity CPICH RSCP CPICH RSCP CPICH Ec/No CPICH Ec/No UeTxPwr UeTxPwr Event id 2D 2F 2D 2F 6A 6B 6. Time To triggers values are not relevant in this figure At the end. timeToTrigger6B). By default. (dlUserService ---> mobilityserviceType ---> usHoConf). mobilityServiceType: this parameter defines the mobility service type that matches with each DlUserService.

and 6A/6B are managed simultaneously. the timer is stopped if both 2F corresponding events are received (Ec/N0 and RSCP). Alarm criteria is only considered valid once a certain period of time has elapsed without receiving 2F. the timer is stopped. The criteria conditions 2D/2F for both Ec/N0 and RSCP. as the condition is evaluated over a long period of time Short “Time To trigger” (around 100 to 300ms) allows much faster detection. The timer timerAlarmHOEvent6A is stopped if a 6B event corresponding to the triggering 6B is received. event 2D may possibly not be reported. The timer timerAlarmHOEvent6A to confirm alarm handover criteria is started once a 6A event is received.06/EN Approved_Standard 17/Sep/2010 Page 197/244 . for event confirmation. 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. In case both quantities (RSCP and Ec/N0) have fulfils their triggering condition. so that the event is only reported once 2D or 2F is valid for a certain period of time. 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 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. 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. If 2F is received while the timer is running. Alarm measurements are configured. a time window solution needs to be implemented at the RNC side. A change of primary (event 1D) or Service type received while the timers are running has no effect on the algorithm. In order to avoid un-necessary activation.UMTS Radio Mobility • • On reception of 2D event the RNC starts a timer. If the timer elapses until 2F is received. Use of event “time to trigger” parameter. If another subsequent 2D event with another measurement quantity is received. CPICH Ec/No 2F 2D Long « Time To Trigger » 2D sent 2F 2D HO decision Short « Time To Trigger » 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”. Short “Time To Trigger” values are preferred to ensure better network reactivity under alarm conditions As a consequence.

2F RSCP Yes Timer decision table The alarm measurement activation is illustrated by the following picture: Radio quality Threshold . the complete decision table for 2D CPICH Ec/No triggering event is described hereafter.UMTS Radio Mobility • • • Once the timer timerAlarmHOEvent2D or timerAlarmHOEvent6A elapses. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. the RNC activates inter Freq or Inter Rat periodical measurements depending on iMCTA provisioning.06/EN Approved_Standard 17/Sep/2010 Page 198/244 . When inter Freq or Inter Rat periodical measurements are already activated for a given criteria or the other criteria is set. 2F Ec/No No 2D RSCP . the alarm handover procedure is cancelled and the alarm measurement results will be ignored when received. 2F RSCP No 2D RSCP . if all alarm criteria previously set become invalid (i. As an example. “Alarm criteria” reflects the RNC decision once the timer has elapsed: Triggering event 2D Ec/No 2D Ec/No 2D Ec/No 2D Ec/No 2D Ec/No 2D Ec/No 2D Ec/No Received while timer is running Timer stopped? No 2F RSCP No 2F Ec/No Yes 2D RSCP No 2D RSCP . no new measurements are requested to the Ue.e. 2F Ec/No . Alarm criteria Confirmation timer time 2D received Inter-frequency or inter-RAT configured Figure 79: Alarm Measurement activation overview MR 2D Timer elapses 2D Event Trigger Mode 2D Timer Wait for Inter Freq/Inter Rat meas time HHO processing Passing on or copying of this document. reception of a 2F and/or 6B events) before the alarm measurement results are 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. After inter Freq or Inter Rat measurements are setup due to one criteria (2D or 6A).

indicating the mobile has returned to the old channel.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. In such a case. 6B Thresh TT 6A TT 6B UE Tx Pwr time 6A Received 6A Alarm timer started 6B received 6A Alarm timer stopped Figure 81: Alarm Measurement 6A followed by 6B Passing on or copying of this document.06/EN Approved_Standard 17/Sep/2010 Page 199/244 . Figure 80: Alarm Measurement 2D criteria hit then 6A UE Pwr 6A Thresh. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. the Alarm Criteria confirmation timer is started again. in order to avoid too frequent handovers.

The behavior is the same for 6A/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. measurements configuration and compressed mode activation are sent to the UE. 2F • CPICH RSCP: reported in events 2D. neighbouring cells filtered after applying IMSI criteria…) or no suitable Alarm measurement is reported by the mobile within a guard timer period. Control Common part (reporting type…) §10.1. §10.10.for all possible targets – see section 4.7. The overall structure of the inter-frequency MEASUREMENT CONTROL message is as follows.4) or execution phase.2. 2F • UeTxPower: for events 6A. In order to limit the risk of loosing an event on the radio interface because of bad transmission conditions. 6.06/EN Approved_Standard 17/Sep/2010 Page 200/244 . three different quantities are actually required: • CPICH Ec/No: reported in events 2D.7. all intra-frequency event reports are configured in RLC Acknowledged Mode.2.19 Inter-freq meas rep criteria Event 2D Event 2F … Figure 82: inter-frequency Measurement Control message structure In the §10. • If the alarm criterion is not hit anymore.1. When the Alarm HHO fails during preparation –( .17 common part: The IE Measurement reporting mode contains the specific information: • Measurement Report Transfer Mode: Acknowledged mode RLC Passing on or copying of this document. At the timer expiration. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.17 Meas. inter-frequency events reporting are not repeated. in order to delay a new HHO attempt the Alarm confirmation timer is set with the value max (2D timer+TTT2D.3 CONFIGURATION Regarding inter-frequency measurement. a blind handover towards the blind GSM cell provisioned for the Primary cell may be performed by the RNC. 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).3.3. As in [A4] specification.16 Inter-freq measurements Common part (meas quantities…) §10. the procedure ends. 6B So that three MEASUREMENT CONTROL messages are actually needed to configure inter-frequency events. 1800ms).

1.1.3. This may be achieved through: • Specific 2D and 2F thresholds (as in the tables above) • Same thresholds.16 common part: • Inter-frequency measurement quantity (§10.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. 2D and 2F need to be triggered by different conditions.2 2F EVENT CONFIGURATION Need OP MP CV–clause 0 CV–clause 2 MP MP OP OP CV–clause 1 CV–clause 1 Parameter Value “2f” Use cpichEcNoThreshold2F or cpichRscpThreshold2F parameter Use weight2F parameter Use hysteresis2F parameter Use timeToTrigger2F parameter Use maxNbReportedCells2F parameter Not needed Not needed Not needed Information Element/Group name Parameters required for each event >Inter-frequency event identity >Threshold used frequency >W used frequency >Hysteresis >Time to trigger >Reporting cell status >Parameters required for each non-used frequency >>Threshold non used frequency >>W non-used frequency Remark: In order to avoid event ping-pong effect. The overall structure of the UE internal measurements MEASUREMENT CONTROL message is as follows.1 2D EVENT CONFIGURATION Need OP MP CV–clause 0 CV–clause 2 MP MP OP OP CV–clause 1 CV–clause 1 Parameter Value “2d” Use cpichEcNoThreshold2D or cpichRscpThreshold2D parameter Use weight2D parameter Use hysteresis2D parameter Use timeToTrigger2D parameter Use maxNbReportedCells2D parameter Not needed Not needed Not needed Information Element/Group name Parameters required for each event >Inter-frequency event identity >Threshold used frequency >W used frequency >Hysteresis >Time to trigger >Reporting cell status >Parameters required for each non-used frequency >>Threshold non used frequency >>W non-used frequency 6.3.06/EN Approved_Standard 17/Sep/2010 Page 201/244 .3.1.7. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.3. using a hysteresis different than 0.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.UMTS Radio Mobility • Reporting Mode: Event trigger In the §10.7.3. UE internal measurements event reports are configured in RLC Acknowledged Mode.7. Passing on or copying of this document.

77 UE internal measurements Common part (meas quantities…) §10. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.4 6B EVENT CONFIGURATION Need OP Parameter Value “UE Transmitted Power” Information Element/Group name Measurement quantity Filter coefficient OP MP MP MP MP MP UE Transmitted Power UE Rx-Tx time difference UE internal event identity Time to trigger UE Transmitted Power Tx power threshold 3(already defined for Ue Internal measurement in OAM) True False “6B” Use new timeToTrigger6B parameter Use new UeTxPwrMaxThresholdOffset for 6B parameter Remark: .1. This may be achieved through Specific 6A and 6B thresholds (as in the tables above) . 6A and 6B need to be triggered by different conditions.7. Passing on or copying of this document.3.For UE transmitted power reporting.7.80 UE internal meas rep criteria Event 6A Event 6B … Figure 83:UE internal Measurement Control message structure 6.3.3.1.17 Meas.1.1. Control Common part (reporting type…) §10. the UE applies a L3 log filtering algorithm.3.UMTS Radio Mobility §10.3 6A EVENT CONFIGURATION Need OP Parameter Value “UE Transmitted Power” Information Element/Group name Measurement quantity Filter coefficient OP MP MP MP MP MP UE Transmitted Power UE Rx-Tx time difference UE internal event identity Time to trigger UE Transmitted Power Tx power threshold 3(already defined for Ue Internal measurement in OAM) True False “6A” Use new timeToTrigger6A parameter Use new UeTxPwrMaxThresholdOffset for 6A parameter 6.In order to avoid event ping-pong effect.2.06/EN Approved_Standard 17/Sep/2010 Page 202/244 .

the HHO criteria is hit.1. When the timer elapses before receiving an event 6B. This feature doesn't apply to E-DCH calls.UMTS Radio Mobility 6. Used for Alarm handover criteria in event-reporting mode. hysteresis for event 2D defines the weight to configure for the triggering of event 2D in Full Event mode Period of time during which the event condition has to be satisfied before sending event 2D Maximum allowed number of cells to report with event 2D Specific CPICH Ec/No threshold specific to event Specific CPICH RSCP threshold specific to event hysteresis for event 2F . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.2 PARAMETERS Object/Class RadioAccessService Class 3 Definition This parameter controls the activation of the feature "Alarm HHO based on UE Tx Power".06/EN Approved_Standard 17/Sep/2010 Page 203/244 . defines the weight to configure for the triggering of event 2F in Full Event mode Period of time during which the event condition has to be satisfied before sending event 2F Maximum allowed number of cells to report with event 2F Specific CPICH Ec/No threshold specific to event 2F (used as an hysteresis to the corresponding event 2D parameter) Specific CPICH RSCP threshold specific to event 2F (used an hysteresis to the corresponding event 2D parameter) Delta power to be minus to UlUsPowerConf MaxAllowedUlTxPower for event 6A Delta power to be minus to UlUsPowerConf MaxAllowedUlTxPower Name IsAlarmHHOUeTxPwrAllowed timerAlarmHOEvent2D UsHoConf Class3 timerAlarmHOEvent6A UsHoConf Class3 hysteresis2D Weight2D UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 MeasurementConfClass Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 MeasurementConfClass Class3 UsHoConf Class3 timeToTrigger2D maxNbReportedCells2D cpichEcNoThresholdUsedFreq2D cpichRscpThresholdUsedFreq2D hysteresis2F Weight2F timeToTrigger2F maxNbReportedCells2F cpichEcNoThresholdUsedFreq2F cpichRscpThresholdUsedFreq2F UsHoConf Class3 UeTxPwrMaxThresholdOffset UeTxPwrMaxThresholdOffset UsHoConf FullEventHOConfHhoMgtEvent6A Class3 UsHoConf FullEventHOConfHhoMgtEvent6B Passing on or copying of this document. Timer armed by the RNC Activation when it receives 6A Event. This timer is started on reception of 2D event.

3. For more details on the primary cell determination.06/EN Approved_Standard 17/Sep/2010 Page 204/244 . Inter Frequency or GSM Inter-System measurements are used.1 Periodic reporting is used in this version for Inter Frequency/GSM Inter-System measurements. 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.2.5). please refer to the section 5.UMTS Radio Mobility Class3 UsHoConf Class3 UsHoConf Class3 for event 6B Time To trigger timer value attached to the event 6A Time To trigger timer value attached to the event 6B timetoTrigger6A timetoTrigger6B 6. 6. and as described in the section 6. 6.2. MEASUREMENTS CONFIGURATION FOR INTER-FREQ/2G INTER-RAT MEASUREMENT REPORTING 6. then the measurement is configured as main measurement configuration in periodic mode. Inter Frequency and GSM InterSystem measurements are used. Passing on or copying of this document. The list of neighbour cells to be monitored is given by the iMCTA function. this might increase the risk of handover failure) L3 filtering is applied in the UE for each measurement. as a configuration parameter. No additional filtering is applied by the SRNC. as specified in [A4].2. The reporting period is 500 milliseconds. When Intra Frequency measurements configuration is event type and only one of both.2. 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. it only includes the cells to be removed and to be added (delta between the previous neighbouring and the new neighbouring).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. 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. When an update of the neighbour list has to be sent to the UE. The neighbor cells are selected among the neighboring cells of the primary cell and/or other active set cells (refer to § 5.4. Otherwise. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. When Intra Frequency measurements configuration is event type and both.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. a specific value of “filter coefficient” is provided for RSSI quantity. depending on the GSM reuse pattern and the radio condition. For that purpose.

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.

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 205/244

UMTS Radio Mobility

6.2.6
6.2.6.1

PARAMETERS FOR MEASUREMENT
MEASUREMENT ACTIVATION PARAMETERS

The following parameters are used when the HHO reason is an alarm reason.
Name cpichEcNoThreshold Object/Class FastAlarmHardHoConf per UsHoConf Class 3 FastAlarmHardHoConf per UsHoConf Class 3 FastAlarmHardHoConf per UsHoConf Class 3 Definition Threshold on CPICH Ec/N0 used in the decision process of inter system or inter-frequency measurement and hard handover Threshold on CPICH RSCP used in the decision process of inter system or inter-frequency measurement and hard handover The measurement and hard handover decision is taken when decision counter, based on CPICH RSCP or CPICH Ec/N0 criterion, is above this quantity. decision counter is decremented by stepdown when the downlink quality HHO criterion based on CpichRSCP or CpichEc/N0 is not hit decision counter is incremented by stepup when the downlink quality HHO criterion based on CpichRSCP or CpichEc/N0 is hit

cpichRscpThreshold

counter

StepDown

fastAlarmHHOTimeFilter per UsHoConf Class 3

StepUp

fastAlarmHHOTimeFilter per UsHoConf Class 3

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 206/244

UMTS Radio Mobility

6.2.6.2

OTHER PARAMETERS

The following parameters are used whatever the HHO reason.
Name interFreqFilterCoeff rrcGsmMeasurementFilterCoefficient rrcIntraFreqMeasurementFilterCoeff isBlindHoRescueAllowed Object/Class InterFreqMeasConf Class3 RRCMeasurement Class3 RRCMeasurement Class3 RadioAccessService Class3 RadioAccessService Class 3 Definition Filter coefficient for inter-frequency Layer 3 filtering in the UE Filter coefficient for GSM RSSI Layer 3 filtering in the UE Filter coefficient for intra-frequency Layer 3 filtering in the UE This parameter indicates whether the RNC is allowed to trigger a blind rescue handover towards a GSM cell. 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. 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.

measurementGuardTimer2g

measurementGuardTimerFdd

RadioAccessService Class 3

6.3. 6.3.1
6.3.1.1

INTRA-FREQUENCY MEASUREMENTS CONFIGURATION
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.
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 207/244

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).

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 208/244

• else. 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. the measurement is substituted by quantity (cell. When possible and activated. A specific value of k is provided for each of the measurement quantities.Based on traces the neighbouring provisioning may be modified.331.3.3.5 FILTERING As specified in 25.3). The reason for this may be e. 6. as an operator parameter.g.UMTS Radio Mobility Note: If Detected Set cells are reported the RNC will trace this as specified in [R5]. where k is the parameter received in the IE "Filter coefficient" in the Measurement Control message and in SIB11/SIB12 (if used).2 MISSING MEASUREMENTS When periodic measurements are reported.N) the missing measurement: • the counter of consecutive missing measurements for this cell is incremented • if the counter value is above maxAllowedNumber.4. • a = 1/2(k/2).3. detected cells can be added to the active set (refer to § 5.1. the RNC implement a specific process in order to cope with missing measurements for a given cell. used with a minimal coefficient in computations. This process only applies to intra-frequency measurements. or radio interface variation which may cause a cell not be reported for some period of time. the measurement for this cell is replaced by a minimal default value. 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: Fn = (1 − a ) ⋅ Fn −1 + a ⋅ M n with: • Fn is the updated filtered measurement result • Fn-1 is the old filtered measurement result. Penalty coefficient which is subtracted to the last received CPICH Ec/N0 missedEcNoMeasurementPenalty MissingMeasurement Class3 Passing on or copying of this document. The corresponding parameters are: Name maxAllowedNumber Object/Class MissingMeasurement Class3 Definition Maximum number of allowed missing measurements in the message RRC Measurement Report for a cell of the monitored set. too. In order to initialise the averaging filter. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 6. No additional filtering is applied by the SRNC. The algorithm is as follows: Let’s call (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. If k is set to 0 that will mean no layer 3 filtering. for cells being part of the active set. mobile limitation.06/EN Approved_Standard 17/Sep/2010 Page 209/244 . This until the measurement is received again.

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 Passing on or copying of this document. 6. Penalty coefficient which is subtracted to the last received CPICH RSCP measurement to replace a missing one.UMTS Radio Mobility measurement to replace a missing one.. or possibly both at the same time. such as GSM.4.2 UE CAPABILITY The real need for compressed mode is indicated by the mobile in the UE Radio Access Capability information element. without discrimination. RNC . 6. as part of the handover preparation..4. 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).06/EN Approved_Standard 17/Sep/2010 Page 210/244 . 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.4. called a transmission gap. 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. Figure 84: Retrieving UE capability In the UE Radio Access capability. Any transmission interruption time. The compressed mode involves interrupting the transmission in the uplink or downlink. UE Node B RRC/ RACH (RRC connection Request) NBAP/ Radio Link Setup 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 by the UE unless it is requested by the RNC. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. missedRscpMeasurementPenalty MissingMeasurement Class3 6. 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. provided in the RRC CONNECTION SETUP COMPLETE message.1 COMPRESSED MODE 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). This information element is sent on network request ("GSM capability required" indication in the RRC Connection Setup message sent from the network).

NOTE: puncturing method removed from 3GPP since R5.4. This is further detailed in the chapter about "impacts on RRM" (see 6. it is explained that compressed mode configuration is done very early in the call process. 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. or possibly both. 6. for GSM or FDD inter-frequency measurements. 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. This method is applicable to both UL and DL. 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. This implies that the transport channel can cope with some transmission delay. 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.8). Regarding compressed mode for GSM. Therefore this method is not applicable to conversational services. Passing on or copying of this document.06/EN Approved_Standard 17/Sep/2010 Page 211/244 . and for which direction. This method is applicable to both UL and DL. Therefore. • Higher Layer Scheduling: transmission gaps are created by restricting the TFC in the TFCS.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. 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 that compressed mode is only activated when needed.4. This is a DL only method. The use of the SF/2 reduction method has an impact on the Scrambling and OVSF code used. • SF reduction: the spreading factor of the compressed radio frames is divided by two. The UTRAN supports: • all FDD R7 frequency bands except the band IV. • the mobility between these bands except between band I and band II. and as specified in 3GPP documents. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.UMTS Radio Mobility All FDD R7 frequency bands capabilities are used by the RNC. allowing the same number of bits to be sent in a smaller amount of time. • Inter Rat handover from/towards theses bands. 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.e. in order not to configure compressed mode in every case.

4. contained in the Measurement Control RRC message.1 GSM MEASUREMENTS Regarding GSM measurements. each of them being associated to a measurement purpose. the network shall configure as many pattern sequences as measurement quantities to be reported by the mobile. as in the figure below. the BSIC is given to the re-confirmation process. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. there may be up to 3 pattern sequences needed. The pattern information are used to generate gaps in the HSDPA and HSUPA part of the call. the following figure presents an overall view of compressed mode processes for GSM in the mobile. In case of HSDPA or HSUPA calls. #1 TG pattern 1 #2 TG pattern 2 #3 TG pattern 1 #4 TG pattern 2 #5 TG pattern 1 #TGPRC TG pattern 2 TG pattern 1 TG pattern 2 Transmission Transmission gap 1 Transmission gap 2 Transmission gap 1 gap 2 TGSN TGL1 TGD TGPL1 TGL2 TGSN TGL1 TGD TGPL2 TGL2 Figure 85: Compressed Mode pattern sequence overview 6. • The "Initial BSIC identification process" intends to identify the BSIC in the list.4. each pattern sequence is dedicated to a certain measurement quantity.UMTS Radio Mobility 6. Passing on or copying of this document.133. intending to re-confirm identified BSIC. intending to identify the 8 strongest cells. 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 mobile is provided with GSM neighbouring cell list. as specified in 25. A sequence may have a finite or infinite value depending on the TGPRC parameter. The defined measurement purposes are applicable whatever the compressed mode method is (SF/2. A pattern sequence is composed of 2 pre-defined patterns (pattern 1 and pattern 2) being used alternatively. • The "RSSI measurement process" can be seen as a sort of endless loop. the compressed mode method only applies to the DCH part of the call. Once being successfully identified.4 MEASUREMENT PURPOSE Compressed mode makes use of pattern sequences. and maintain timing information with the identified cells.06/EN Approved_Standard 17/Sep/2010 Page 212/244 .4. The same CM pattern definition is used whatever the method is. • The "BSIC re-confirmation process" can be seen as a sort of endless loop. so that. In principle. HLS).

and are not running in parallel (i.2 FDD INTER-FREQUENCY MEASUREMENTS Regarding FDD inter-frequency measurements..: TGPRC=1 to 511). the pattern for BSIC identification is only started once the pattern for RSSI is over). CFN RSSI .e.5 6.. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.4.06/EN Approved_Standard 17/Sep/2010 Page 213/244 .1 PATTERN SHAPE GSM MEASUREMENTS In this version. only one pattern sequence is needed as there is only one "measurement purpose": • FDD measurement 6.e. for GSM measurements.4. An example for such a configuration is presented in the figure below: x frames y frames .UMTS Radio Mobility Measurement Control (BSIC.4. BCCH ARFCN) GSM neigh...cells RSSI measurement process 8 strongest cells Initial BSIC ID process up to 8 identified cells BSIC re-confirmation process Measurement Report identification failed re-confirmation failed Figure 86: UE process overview for GSM measurements 6. 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. CFN +x BSIC Identification Passing on or copying of this document.4.5. The 2 patterns have finite duration (i.

UMTS Radio Mobility Figure 87: Pattern sequences for GSM measurements Once RSSI measurements are performed. 6. • activation/deactivation is based on a separate criteria.e. CFN FDD measurement Figure 88: Pattern sequence for FDD measurements Please refer to the chapter on [parameters] for the pattern parameters supported in this version. Please refer to the chapter on [parameters] for the pattern parameters supported in this version.. using the relevant pattern sequence.4. 6. when the iMCTA function needs measurement for HHO processing for Alarm.4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. The selection between them is dependent on the used method: DL Slot format B shall be used in frames compressed by SF reduction.2 FDD INTER-FREQUENCY MEASUREMENTS In this version. e. in compressed frames..7. Same Transmission gap position calculation used for SF/2 and for HLS compressed mode method.211 section 5.5. the network may possibly make a handover decision toward a GSM target. when the RAB ASSIGNMENT REQUEST message is received from the Core Network).4.06/EN Approved_Standard 17/Sep/2010 Page 214/244 .3.6 SLOT FORMATS/ FRAME STRUCTURE According to 25.e. CAC or Service reason. 6. There are two possible compressed slot formats (labeled A & B). x frames .1 PROCEDURES & MESSAGES 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.4. DL Slot format A shall be used in frames compressed by HLS.7 6. Frame structure type A and Type B shall be supported by the UTRAN. Passing on or copying of this document.2 “Dedicated downlink physical channels”. A reconfiguration of the compressed mode may occur when a CM method change is needed. the mobile should normally attempt to identify the 8 strongest RSSI. Alcatel-Lucent UTRAN implements a finite length pattern.g. as in the figure below. due to additional RAB setup or RAB deletion. i. a different DPCH slot format is used compared to normal mode. for FDD inter-frequency measurements. Once BSIC have been identified and reported to the network.

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).6.6.UMTS Radio Mobility UE Node B Initial RRC connection DCCH establishment Initial UE DTAP message RANAP/ RAB Assignment Request NBAP/ Radio Link Reconfiguration Prepare (DTCH config.7. starting CFN) Criteria is reached => CM re-activation NBAP/ Compressed Mode Command (active pattern. which will be possibly be activated by the RNC when the criteria is reached. CM config for FDD) NBAP/ Radio Link Reconfiguration Response NBAP/ Radio Link Reconfiguration Commit (no pattern active) RRC/ RB Setup (DTCH config.2.3. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. The RNC follows this rule.4. starting CFN) RRC/ Measurement Control (active pattern.33 DPCH compressed mode info TGPSI TGPS Status Flag TGCFN TGMP TGPRC TGSN Passing on or copying of this document. starting CFN) RRC/ Measurement Control (active pattern.33 RB Setup • 10.2 RRC/RB SETUP MESSAGE This message contains the CM configuration. It contains the following information: • 10.06/EN Approved_Standard 17/Sep/2010 Page 215/244 . CM config for FDD) RRC/ RB Setup Complete RANAP/ RAB Assignment Response Criteria is reached => CM activation RNC MSC-CS NBAP/ Compressed Mode Command (active pattern. CM config for GSM. CM config for GSM.3.24 Downlink information common for all radio links • 10." 6.

2.2.5 NBAP/RADIO LINK RECONFIGURATION PREPARE MESSAGE This message is used by the RNC to configure the compressed mode sequences to be used at the BTS.06/EN Approved_Standard 17/Sep/2010 Page 216/244 . 6.2.6. • 9.6.2.53B Transmission Gap Pattern Sequence Code Information Scrambling code change • • • 9.10 DL DPCH Slot Format 9.3.4.34 DPCH compressed mode status info TGPSI TGPS Status Flag TGCFN 6.3.2.4.2.2.3.7.2.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.7.21 Downlink DPCH info for each RL Scrambling code change 6.7.1.2. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.2.27 Downlink information for each radio link • 10.17 Measurement Control • 10.2.57 UL DPCCH Slot Format 9. The same IEs are used as for initial CM configuration in RB Setup message – see above.4.4 RRC/MEASUREMENT CONTROL MESSAGE This message is used to trigger/stop compressed mode pattern sequences.53A Transmission Gap Pattern Sequence Information TGPSI TGSN Passing on or copying of this document.42 Radio Link Reconfiguration Prepare • 9.14A DL code information • 9.2. • 10.6.3 RRC/RB RECONFIGURATION MESSAGE This message is used to reconfigure the compressed mode (used to change the method).

1.1. • 9.60 Compressed Mode Command • 9.8 RNSAP/RADIO LINK SETUP/ADDITION REQUEST MESSAGE This message is used in case of inter-RNC soft handover. so that the choice is left to the DRNC.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.7. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1. <maxTGPS> M M M Type and reference CFN group present (range > 0) IE/Group Name CM Configuration Change CFN Transmission Gap Pattern Sequence Status >TGPSI Identifier >TGPRC >TGCFN CFN • CM deactivation Presence M Range Type and reference CFN IE/Group Name CM Configuration Change CFN 6.e.2.2.2. • 9.2.06/EN Approved_Standard 17/Sep/2010 Page 217/244 .4. 6.2.3. • 9.60 Compressed Mode Command • 9.2. whether or not the alternate scrambling is used) is not indicated in the RNSAP. the DRNC applies the same configuration as the SRNC in terms of pattern definition and Power control.1 Radio Link Setup Request or 9.6 NBAP/COMPRESSED MODE COMMAND MESSAGE This message is used to trigger/stop compressed mode pattern sequences.6 Radio Link Addition Request • 9.1.4.. The main difference with equivalent message used on the Iub interface (NBAP Radio Link Reconfiguration Prepare message) is that the "code information" (i.7. Aside from this very specific point.A Active Pattern Sequence Information Same structure as § above.A Active Pattern Sequence Information • CM activation Presence M Range 0.7.A Active Pattern Sequence Information Passing on or copying of this document.7 NBAP/RADIO LINK RECONFIGURATION COMMIT MESSAGE This message is used to trigger/stop compressed mode pattern sequences.4.

8 6.2: • SC+8192 • SC+16384 Depending on the position of the OVSF code Cch.UMTS Radio Mobility TGPSI TGCFN TGPRC • 9.2.2. as specified in 25. the network is using • scrambling code SC • OVSF code Cch.SF/2.4. Alcatel-Lucent UTRAN is using the alternate scrambling method.n mod SF/2 Passing on or copying of this document. These impacts are described in what follows.7. Its format is equivalent to the message used on the Iub. § 5. For DL transmission in uncompressed frames.SF.10 RNSAP/RADIO LINK RECONFIGURATION COMMIT MESSAGE This message is used to trigger/stop compressed mode pattern sequences. Its format is equivalent to the message used on the Iub. SC+8192 is used • if (n>=SF/2).06/EN Approved_Standard 17/Sep/2010 Page 218/244 .SF.1 IMPACTS ON RRM SPECIFIC FOR SF/2 METHOD CODE TREE MANAGEMENT The use of the SF reduction method has some impacts on the Scrambling and OVSF code used for the transmission.4. either the 1st or the 2nd alternate is used: • if (n<SF/2). SC+16384 is used In both cases.2 and 5. which makes use of 2 additional scrambling codes. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.9 RNSAP/COMPRESSED MODE COMMAND MESSAGE This message is used to trigger/stop compressed mode pattern sequences.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. 6.4.4. 6. the OVSF code which is used for compressed frames is Cch.n For DL transmission in compressed frames.213.1.2.8.7.n in the code tree.

compressed mode by HLS is also used for certain multiplexed PS I/B + CS services – see below.06/EN Approved_Standard 17/Sep/2010 Page 219/244 . compressed mode by HLS is used for UL/DL multiplexed PS I/B services over DCH. I. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.] This chapter describes the Compressed Mode by HLS over dedicated physical channel. In downlink SF/2 method is available. only.9 HLS [USA Market: HLS method is supported in uplink. compressed mode by HLS is used for UL/DL PS I/B mono/multi services over DCH. 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. only. UL HLS and DL SF/2) whatever the measurement purpose is. Passing on or copying of this document. dependent on the uplink bearer combination SF/2 or HLS can be used.4.e. compressed mode method by HLS or SF/2 can be used in mixed CM method UL/DL (ex.UMTS Radio Mobility Scrambling code = SC LEFT case Scrambling code = SC +8192 SF-1 SF/2 0 SF-1 SF/2 0 Scrambling code = SC Scrambling code = SC +16384 RIGHT case SF-1 SF/2 0 SF-1 SF/2 0 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. 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. compressed mode by SF/2 reduction method is possible for both UL and DL whenever GSM or FDD interfrequency measurements is used.

o When compressed mode is activated. assuming that the CM pattern configuration is as described in section. 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. for a DL transmission with TTI = 10ms.4.211].4. while other require the compressed mode to be activated either in UL or DL only or in both UL and DL. 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.06/EN Approved_Standard 17/Sep/2010 Page 220/244 . o Some TF/s on PS RAB only are forbidden for TTIs where transmission with gap is performed o E. same UE capabilities filtering algorithm is applied. Only the PS I/B TF(s)/TFC(s) are restricted during transmission with gap. the max ratio of compressed frames is 2/3.9. TFS reduction will only apply during 2 or 4 TTIs every 6 TTIs. o HLS can be applied to SRB + PS Streaming + PS I/B provided the streaming GBR while compressed frames is guaranteed. 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.9. as a consequence the associated DCH (ie SRB only) uses SF/2 for any such configuration.2 HLS GAP PATTERN CONFIGURATION Compressed Mode configuration management: o The same CM patterns will be used for both HLS & SF/2 methods.UMTS Radio Mobility 6. 6. With the current CM pattern.g.5. 6. CMode method only applies to the DCH part of a call and not to HS-DSCH. Passing on or copying of this document. 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. 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. o HLS is supported for multiplexed PS I/B x/y calls with x/y > 8 Kbps. as per [25.4. refer to §6.1 HLS ASSUMPTIONS In most of the cases.5. 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. the ratio is 1/3 in case of single 2G or 3G measurement and 2/3 in case of simultaneous 2G and 3G measurement. 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. 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Compressed mode (SF/2) is active with HSDPA. o UE capability analysis performed by the RNC is not impacted by the introduction of the HLS compressed mode.4.

HLS would apply in the UL direction.4.06/EN Approved_Standard 17/Sep/2010 Page 221/244 . 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.9. 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 () // + start CM at TGCFN or CFN time o NBAP/RNSAP COMPRESSED MODE COMMAND () // stop CM configuration change // CFN time o RRC RADIO BEARER SETUP (RBs + CM parameters) // at TGCFN time for each // TGPSI // CM configuration provisioning // start CM at TGCFN or CFN time // configuration + Start/Stop CM o RRC RADIO BEARER RECONFIGURATION (RBs + CM parameters) // configuration + Start/Stop CM // at TGCFN time for each TGPSI o RRC MEASUREMENT CONTROL () // for each TGPSI // Start/Stop CM at TGCFN time Passing on or copying of this document. o When SRLR ends the new CM method is configured and activated at the CFN#2 time. i.UMTS Radio Mobility 6. => For the specific case where the PS I/B would be supported by UL DCH / HS-DSCH transport channels.3 SWITCHING BETWEEN COMPRESSED MODE METHODS The system shall be able to switch to the most appropriate method after a RAB combination modification. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. while the SF/2 method would apply in the DL direction.e.

UMTS Radio Mobility Switching between Compressed Mode methods use cases Compressed method switching while CM active: See call flow diagram below: UE Node B Initial RRC connection DCCH establishment Initial UE DTAP message RANAP/ RAB Assignment Request NBAP/ Radio Link Reconfiguration Prepare ((DTCH config. for FDD.06/EN Approved_Standard 17/Sep/2010 Page 222/244 . starting CFN: TGCFN time) NodeB compares the CFN of DL FP DCH frames to TGCFN to trigger CM activation RNC MSC-CS RANAP/ RAB Assignment Request RB configuration change => CM method switching: RNC detects the CM method change CM Method Switching: Determination of the deactivation time (CFN) for old CM method. New CM configuration/method) NBAP/ Radio Link Reconfiguration Response 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 NBAP/ Radio Link Reconfiguration commit (CM activation at new CFN: TGCFN time) RRC/ RB Reconfiguration (DTCH config. New CM configuration/method. CM config for FDD) RRC/ RB Setup/reconf/Release Complete RANAP/ RAB Assignment Response 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 (active pattern. CM config for GSM. CM deactivation command to RNC MAC-d CM deactivation command to the NodeB /UE 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 ) NBAP/ Radio Link Reconfiguration Prepare (DTCH config. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. CM activation at new CFN: TGCFN time ) RRC/ RB Reconfiguration complete (DTCH config. for FDD) RANAP/ RAB Assignment Response Passing on or copying of this document. starting CFN: TGCFN time) RRC/ Measurement Control (active pattern. CM config for FDD) NBAP/ Radio Link Reconfiguration Response NBAP/ Radio Link Reconfiguration Commit (no pattern active) RRC/ RB Setup/Reconfiguration/Release (DTCH config. CM config for GSM.

CM config for FDD) RRC/ RB Setup/reconf/Release Complete RANAP/ RAB Assignment Response 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 (active pattern. for FDD) RANAP/ RAB Assignment Response 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 6. no pattern active ) RRC/ RB Reconfiguration complete (DTCH config. starting CFN: TGCFN time) NodeB compares the CFN of DL FP DCH frames to TGCFN to trigger CM activation RRC/ Measurement Control (active pattern. CM config for GSM. CM config for GSM. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. starting CFN: TGCFN time) RNC MSC-CS CM ends normally at a finite time.SF/2 is the default CM method applicable to all PS streaming mono RB on DCH excepted when SF equal 4 C .UMTS Radio Mobility Compressed method switching while CM not active: See call flow diagram below: UE Node B Initial RRC connection DCCH establishment Initial UE DTAP message RANAP/ RAB Assignment Request NBAP/ Radio Link Reconfiguration Prepare ((DTCH config.4. New CM configuration/method) NBAP/ Radio Link Reconfiguration Response NBAP/ Radio Link Reconfiguration commit ( no Pattern active) RRC/ RB Reconfiguration (DTCH config.SF/2 is the default CM method applicable to all CS NB/WB/CSD mono RB on DCH B .06/EN Approved_Standard 17/Sep/2010 Page 223/244 .SF/2 is the default CM method applicable to all CS NB/WB + PS streaming RB(s) on DCH Passing on or copying of this document. RANAP/ RAB Assignment Request RB configuration change => CM method switching: RNC detects the CM method change CM was not activated NBAP/ Radio Link Reconfiguration Prepare (DTCH config. for FDD.9. CM config for FDD) NBAP/ Radio Link Reconfiguration Response NBAP/ Radio Link Reconfiguration Commit (no pattern active) RRC/ RB Setup/Reconfiguration/Release (DTCH config.4 • CM METHOD SELECTION RULES: SF/2 selection method rules: A . New CM configuration/method.

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.SF/2 is the default CM method applicable to all combinations including a RB over HSDPA/HSUPA F . Passing on or copying of this document.HLS is the default CM method applicable to all CSD 64 + PS I/B x/y mono/multiplexed RB over DCH.UMTS Radio Mobility D .HLS is the default CM method applicable to PS I/B x/y + PS Streaming u/p RB over DCH. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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 . and x/y ≥ GBR F .HLS is the default CM method applicable to all CS NB/WB + PS I/B x/y combination on DCH.HLS is the default CM method applicable to PS I/B x/y mono/multiplexed RB on DCH. 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 .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 . o To downgrade the granted rate of that RB combination with a greater SF 6. with x/2 & y/2 ≥ SRB max rate + AMR max rate (excepted for CS NB/WB + PS I/B 8/16 Kbps) C .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.4.06/EN Approved_Standard 17/Sep/2010 Page 224/244 . 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).10 SRNS RELOCATION Interaction with SRNS relocation (UE not involved). with SF = 4. with x/2 & y/2 > 64 Kbps D . excepted for I/B 8 Kbps B .SF/2 is the default CM method applicable to all CS NB/WB + PS streaming RB(s) + I/B on DCH E .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.

There is no dynamical compressed mode configuration. 3. Note: Sending the RRC measurement Ctrl to deactivate the initial compressed mode ensure a correct deactivation on UE side . since it may generate call drops. in order to reduce some undecoded radio frame.UMTS Radio Mobility . Passing on or copying of this document. The target RNC is configured with its MIB compressed mode configuration/CM prefered method. then: 1.06/EN Approved_Standard 17/Sep/2010 Page 225/244 .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). The Target RNC shall stop the current CM at the UE/NodeB side for any active TGPS at the CM configuration CFN time. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 2. 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.

CM config for GSM. CM config for GSM.The SRNC does not need to apply any particular action on its Iur interface.4. starting TGCFN) RRC/ Measurement Control (active pattern.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).0 SRNC facing an oldest DRNC version: . CM config for FDD) NBAP/ Radio Link Reconfiguration Response NBAP/ Radio Link Reconfiguration commit (no CM activation: no TGPS status) RRC/ RB Reconfiguration (DTCH config. 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). no CM activation) ) RRC/ RB Reconfiguration Complete() 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 NodeB compares the new CFN of DL FP DCH frames to TGCFN to trigger CM activation NBAP/ Compressed Mode Command (active pattern.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”. 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 226/244 . 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: Passing on or copying of this document.UMTS Radio Mobility UE Node B Target RNC Source RNC Target SGSN Initial RRC connection DCCH establishment SRNS reloc criteria reached All radio links belong to the DRN CM was activated before SRNS RANAP/ Relocation Request SRNC relocation ends RANAP/ Relocation Request ACK Target RNC CM deactivation: Stop previous CM Methodif active for any active TGPS NBAP/ Compressed Mode Command (Stop previous CM at CM Configuration change CFN) RRC/ Measurement Control (Stop previous CM at CFN= CM Configuration change CFN) NBAP/ Radio Link Reconfiguration Prepare ((DTCH config. starting CFN= TGCFN) 6. • UA06. CM config for FDD. o While CM activation: 1) When SRNC facing an oldest DRNC version and if the CM method in use is SF/2: .

No additional action. refer to the CM method switching procedure described above.CM activation is blocked while call has RB combination with SF=4.If IsHlsCmAllowedOnDRNC is equal to “false” then .Same case as 2) but without CM deactivation.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. o Without CM activation: 3) When SRNC facing an oldest DRNC version and if the CM method to be used is SF/2: .06/EN Approved_Standard 17/Sep/2010 Page 227/244 . .For any RB combination to be supported on the SRNC/DRNC and the SF of the established combination is not equal to SF4: . If HHO reason was alarm HHO 3G2G may be processed in blind mode (if allowed) at next Alarm condition. Inter-freq/inter-RAT HHO cannot be triggered as long as call has RB combination with SF=4. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. HHO is never processed whatever the reason of the handover. Passing on or copying of this document.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.For any RB combination to be supported on the SRNC and DRNC and the SF of the current combination is equal to SF4: .UMTS Radio Mobility . to the DRNC 4) When SRNC facing an oldest DRNC version and if the CM method in used is HLS: . See hereafter the call flow for that use case. refer to the CM method switching procedure described above. follow on of the CM method/configuration with the same TGPS.

for FDD) RNSAP/ Radio Link Setup Request (DTCH config. New CM config. 6. TGCFN time) NBAP/ Radio Link Setup Response () RNSAP/ Radio Link Setup Response () • UA0x. the DRNC does not perform any check regarding the activation of different CM methods in UL & DL./method./method. New CM config. 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 Request (DTCH config. nothing specific at this stage. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Similarly.06/EN Approved_Standard 17/Sep/2010 Page 228/244 . CM activation at new CFN= TGCFN time ) RRC/RB Reconfiguration complete (DTCH config./method. for FDD. New CM configuration/method.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).UMTS Radio Mobility UE Node B Non V6 V6 Node B DRNC SRNC Initial RRC connection DCCH establishment Radio links addition/reconf to the DRNS: HLSCMAllowedOnDRNC = False CM was activated before on SRNS 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 ) SF/2 method selected on V6 NodeB Determination of the activation time: New TGCFN NBAP/ Radio Link Reconfiguration Prepare (DTCH config.4.12 DRNS SCENARIOS The DRNC does not perform any check regarding HLS activation and the AsConf. New CM config.x SRNC facing an UA06. Passing on or copying of this document.) NBAP/ Radio Link Reconfiguration Ready () NBAP/ Radio Link Reconfiguration Commit (CM configuration activation at TGCFN time ()) RRC/ RB Reconfiguration (DTCH config.

CM not supported on the DRNC side: 1. If the HLS method is configured and activated on a node alpha card base. 2. follow on of the SF/2 CM method with the same TGPS. • A NodeB with alpha CEM cards inside will generate a RL SETUP/RECONFIGURATION FAILURE at the compressed mode activation. It corresponds to an existing use case. 2. CM not activated in the SRNC.13 ALPHA CEM CARDS IMPACT • HLS method is not supported on alpha CEM card. 2. For these use cases the DRNC does not need to check the CM method (for ALU SRNC/ ALU DRNC only). a NBAP/RNSAP RL SETUP/RECONFIGURATION FAILURE is transmit to the SRNC. 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. CM on DRNC side is activated at the correct TGCFN time.If IsHlsCmAllowedOnDRNC is equal to “false” then Same action shall be performed as for the RNS inter release case see §6. When RL(s) is added on the DRNC. No specific action at the RNC/NodeB side. • On reception of the NBAP/RNSAP RL SETUP/RECONFIGURATION FAILURE message the SRNC shall stop the HLS procedure. No specific action required at the RNC/NodeB side. It corresponds to an existing use case. CM activated in the SRNC. If the SRNC CM configuration is not supported by the DRNC. If the CM is active and CM method in used is HLS: . this last shall answer by a RNSAP RL Setup/Reconfiguation failure with the cause IE set to “CM not Supported”. The DRNC and the Node B should accept any 3GPP compliant sequence or combination for compressed mode activation/deactivation for supported compressed mode methods. 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.4. 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. The SRNC shall not intend to activate any CM on that radio link anymore.UMTS Radio Mobility ALU SRNC/ ALU DRNC: not ALU SRNC/ ALU DRNC (IOT use case) 1. 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.4. 6. • A RL establishment on a NodeB with alpha CEM cards inside cannot be activated with a HLS CM method. • • ALU SRNC/ not ALU DRNC 1. the DRNC relays the CM patterns to the dedicated NodeB.06/EN Approved_Standard 17/Sep/2010 Page 229/244 .11 (CM method switching). Passing on or copying of this document.

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]). since the alternate scrambling method is used For the new radio link. In case Compressed Mode is already active for the existing UE Radio Links. Passing on or copying of this document. In case Compressed Mode is already active for the existing UE Radio Links.2.4. the Radio Link Addition Request message sent to the NodeB contains the following information: • "De-activation Flag" IE set to "maintain active". 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". The RNC calculates the compressed mode parameters (e.g.2. containing the pattern sequence length. since the compressed mode is kept active • "Scrambling Code Change" IE set to "code change".4. and the starting CFN (TGCFN) • In case of SF/2: "Scrambling Code Change" IE set to "code change".15.433 §8. a new radio link is added to existing ones in the NodeB. a new radio link is added belonging to a new BTS controlled by the Serving RNC. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. 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. 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. code change) NBAP/ Radio Link Addition resp RRC/ active set update RRC/ active set update complete Serving RNC Figure 91: intra-NodeB soft handover during compressed mode 6.4.06/EN Approved_Standard 17/Sep/2010 Page 230/244 .2 INTRA-RNC/INTER-NODEB SOFT HANDOVER In this case.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. TGPRC) such that the patterns are in sync with the other active set cells and UE. UE NodeB RRC/ Measurement Report NBAP/ Radio Link Addition req (maintain active.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.UMTS Radio Mobility 6. 6. TGCFN.1 INTRA-NODEB SOFT HANDOVER In this case.17.15.

3 INTER-RNC SOFT HANDOVER In this case.g. containing the pattern sequences information • "Active Pattern Sequence Information" IE. it can be activated later on in the call. using the COMPRESSED MODE COMMAND RNSAP message. Passing on or copying of this document. In case of SF/2: The "Scrambling code change" method is not specified on the Iur. 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. containing the pattern sequence length. In case Compressed Mode is not active.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. the RNC calculates the compressed mode parameters (e. Pattern Sequence Info. TGCFN) NBAP/ Radio Link setup resp FP/ DL Sync (CFN) FP/ UL Sync (ToA) RRC/ active set update RRC/ active set update complete Serving RNC Figure 92: intra-RNC soft handover during compressed mode 6. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. A fortiori. UE NodeB RRC/ Measurement Report NBAP/ Radio Link setup req (code change.15. TGCFN. In case Compressed Mode is already active for the existing UE Radio Links.4. this is also valid for the inter-RNC soft handover case. the "scrambling code change" is applied.06/EN Approved_Standard 17/Sep/2010 Page 231/244 . as on Iub. as on Iub. TGPRC) for the cell on DRNC to be in sync with the ongoing CM pattern. The choice is left to the Drift RNC. In any case. in the same way as for the Iub interface. the Radio Link Setup Request Iur message sent to the Drift RNC contains the following information: • "Transmission Gap Pattern Sequence Information" IE. and the starting CFN (TGCFN) As in "intra-RNC/inter-NodeB soft handover" case. In case of an Alcatel-Lucent Drift RNC. a new radio link is added belonging to a new BTS controlled by a Drift RNC.

In case the primary cell is changed while compressed mode is running. The configuration of the new Primary cell is taken into account for the next measurement setup. depending on the Alarm Measurement Type This is illustrated in the following figure: Passing on or copying of this document. This may happen in case the access network is composed of RNC from multiple manufacturers. The filtering function is specified in the chapter on "Parameters". a rejection means that a RADIO LINK SETUP FAILURE or RADIO LINK ADDITION FAILURE is sent back to the SRNC. In order to avoid compressed mode configuration which Alcatel-Lucent RNS is not able to support. the RADIO LINK SETUP REQUEST or RADIO LINK ADDITION REQUEST received from the Iur is either accepted or rejected by the Alcatel-Lucent RNC. The AlcatelLucent RNC implements a filtering function.UMTS Radio Mobility UE Drift NodeB RRC/ Measurement Report SCCP/ CR SCCP/ CC RNSAP/ Radio Link setup req (Pattern Sequence Info. Based on the output of this function.9. 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. as explained in section 4.4. measurements (either inter-freq or inter-system) are activated. the RNC keeps the ongoing measurement active independent of the configuration of the new Primary cell. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. (SF/2: code change)) NBAP/ Radio Link setup resp RNSAP/ Radio Link Setup resp (SF/2: code change) AAL2/ ERQ AAL2/ ECF AAL2/ ERQ AAL2/ ECF FP/ DL Sync (CFN) FP/ DL Sync (CFN) FP/ UL Sync (ToA) FP/ UL Sync (ToA) RRC/ active set update (SF/2: code change) RRC/ active set update complete Drift RNC Serving RNC 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. TGCFN.06/EN Approved_Standard 17/Sep/2010 Page 232/244 . • • • The compressed mode is stopped when the CFN activation is passed. This behaviour ensures that handover can be executed as fast as possible. In this case. 6. these parameters may not be consistent with the DRNC capability. TGCFN) NBAP/ Radio Link setup req (Pattern Sequence Info. The measurement criteria is evaluated If the Alarm Measurement Criteria is still valid. and associated compressed mode sequence depend on the Primary cell neighbouring list and priority setting.19 and 5.16 CHANGE OF ALARM MEASUREMENT TYPE (COMMON HLS AND SF/2) The Alarm Measurement Type.

use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. Trigger change.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. This IE has the same value as the CM Configuration Change CFN of the NBAP message below.UMTS Radio Mobility CMperiod Inter-system CM Pattern sequence for inter-freq . Fdd pattern=active. indicating the CFN at which the NodeB shall de-activate all the on-going pattern sequences. UE NodeB Serving RNC Inter-system CM is active.. Change of trigger with crossover from GSM to inter-frequency target RRC/ Measurement Control (Release GSM measurement) RRC/ Measurement Control (setup inter-frequency measurement) RRC/ Measurement Control (2G pattern=inactive. at which all pattern sequences shall be de-activated. inter-frequency starting TGCFN) NBAP/ Compressed Mode Command (CM Configuration Change CFN. • a starting CFN for the inter-frequency pattern sequence The NBAP COMPRESSED MODE COMMAND contains a CM Configuration Change CFN. Passing on or copying of this document. This message also contains a starting CFN for the inter-frequency pattern sequence. The subsequent RRC MEASUREMENT CONTROL messages provide the mobile with • a list of inter-frequency cells to be monitored • a TGPS reconfiguration CFN. 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. 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. 6. TGPS reconf CFN.. The procedure is applicable independently of the CM method.4.06/EN Approved_Standard 17/Sep/2010 Page 233/244 . 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. For details refer to [R4] (HSDPA) and [R6] (HSUPA).

Defines whether only DL. The following set of parameter is present for each pattern. 6..4. 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 234/244 .18. only UL. there is no guarantee regarding Alcatel-Lucent UTRAN performances. or combined UL/DL compressed mode is used.18. UL/DL mode UL only. inactive Integer (0. Parameters at the RNC level Most of the parameters listed below are defined at the RNC level.18. being active or not.255) current status of the Transmission Gap Pattern Sequence Connection Frame Number of the first frame of the first pattern within the Transmission Gap Pattern Sequence. it is always possible to change the value.18 PARAMETERS This chapter lists all the configuration parameters for Compressed mode. or interoperability with mobiles. For the parameters displayed at the OMC-R level. most of them being part of 25.1 GENERAL PARAMETERS Definition YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise Granularity RadioAccessService Class 3 Name gsm450Present gsm480Present RadioAccessService Class 3 RadioAccessService Class 3 RadioAccessService Class 3 RadioAccessService Class 3 RadioAccessService Class 3 Gsm850Present Gsm900PPresent Gsm900EPresent Gsm900RPresent Passing on or copying of this document.4. DL only. TGPS Status Flag TGCFN active.4. The value of this parameter depends on the UE classmark. If this should occur.331 6.2.4.2 O&M PARAMETERS This list contains the parameters which are used to configure the CM function. UL/DL 6.1 DYNAMIC PARAMETERS These parameters are not accessed by the operator.UMTS Radio Mobility 6.

Name TGMP Range FDD measurement. Those parameters are defined at the cell level. GSM RSSI measurement. Indicates if the Compressed Mode for interfrequency is allowed for this DL UserService. 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. Class 3 NeighbouringRNC Managed Object.UMTS Radio Mobility Gsm1800Present Gsm1900Present YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise YES: there exist GSM neighbouring cells of that frequency band in the access network NO: otherwise RadioAccessService Class 3 RadioAccessService Class 3 Name isGsmCModeActivationAllowed isInterFreqCModeActivationAllowed isHlsCModeAllowed isHlsCmMethodPreferred isHlsCmMethodPreferred IsHlsCmAllowedOnDRNC isSimCMAllowed[not supported in this version] Object/Class DlUserService Managed Object. For each of the pattern. GSM BSIC re-confirmation Integer (1.2. If simultaneous compressed mode is requested but not possible then the RNC uses single compressed mode as per parameter is3GHandoverPreferred. Simultaneous inter-frequency and 2G inter-RAT measurements are not possible for certain RAB combinations due the enhanced compressed mode requirements. Indicates if compressed mode by HLS is allowed or not. Class 3 Definition Indicates if compressed mode for GSM is allowed for this DL UserService.isHlsCmMethodPreferred=No.511. Otherwise: FALSE 6. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.18.. Class 3 DlUserService Managed Object. GSM Initial BSIC identification. ALU uses a double frame CM pattern.isHlsCmMethodPreferred=Yes if throughput reduction by simultaneous CM pattern is acceptable. Engineering guideline: TRUE for all RAB combinations with . Class 3 RadioAccessService Class 3 UlUserService Managed Object.06/EN Approved_Standard 17/Sep/2010 Page 235/244 . Infinity) Definition Transmission Gap pattern sequence Measurement Purpose. the available parameters are described in the table below.2 PATTERN PARAMETERS A certain number of pattern sequences can be defined in Alcatel-Lucent UTRAN. Class 3 DlUserService and UlUserService Managed Object. Passing on or copying of this document.4. TGPRC The number of transmission gap patterns within the Transmission Gap Pattern Sequence. or . Indicates if HLS is the preferred method of compression for generating uplink compressed mode gaps Indicates if HLS is the preferred method of compression for generating downlink compressed mode gaps Indicates if a ALU-DRNC is HLS method capable. Class 3 DlUserService Managed Object.

The time is given in steps of 0..3 POWER CONTROL PARAMETERS This set of parameters is linked to power control algorithms used by the BTS when compressed mode is active. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.20) GSM and/or FDD inter-frequency measurements: The following table provides preferred sets of parameters which will be used in this version: Pattern purpose TGPRC TGSN TGL1 TGL2 TGD TGPL1 TGPL2 TGCFNoffset N_IDENTIFY_ABORT T_RECONFIRM_ABORT GSM RSSI Measurements 8 8 14 undefined undefined 6 undefined 0 not applicable not applicable GSM Initial BSIC Identification 3x26=78 8 14 undefined undefined 6 undefined 8x6=48 26 not applicable FDD Measurements 50 10 10 undefined undefined 6 undefined 3 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).4.06/EN Approved_Standard 17/Sep/2010 Page 236/244 .255) N Identify abort Integer(1. Passing on or copying of this document.14) TGL2 TGD Integer (1.. These two gaps are spread by applying the TGCFNoffset=3 for FDD measurements.... Those parameters are defined at the cell level.18.144) Integer (1.128) T Reconfirm abort Integer(1. the GSM RSSI or BSIC Identification gap and the FDD measurement gap.UMTS Radio Mobility TGSN Integer (0.2.14) Integer(15.144) Integer(0.. undefined) TGPL1 TGPL2 TGCFNoffset Integer (1. The length of the first Transmission Gap within the transmission gap pattern expressed in number of slots The length of the second Transmission Gap within the transmission gap pattern Transmission gap distance indicates the number of slots between starting slots of two consecutive transmission gaps within a transmission gap pattern The duration of transmission gap pattern 1 expressed in number of frames The duration of transmission gap pattern 2 expressed in number of frames used as: TGCFN = (CFNx+TGCFN offset) mod 256 expressed in number of frames 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 Indicates the maximum time allowed for the re-confirmation of the BSIC of one GSM cell in the BSIC re-confirmation procedure.14) Transmission Gap Starting Slot Number The slot number of the first transmission gap slot within the TGCFN.. TGL1 Integer(1..269. 6.5 seconds..

B code change. These parameters are defined at the RNC level.4.4.1) DeltaSIRafter2 Real(0.2 Indicates whether the alternative scrambling code is used for compressed mode method 'SF/2' Passing on or copying of this document. mode 1 Definition Recovery Period Power control mode during the frame after the transmission gap within the compressed frame.3 by step of 0. §4. higher layer scheduling SF/2. DeltaSIRafter2 = DeltaSIRafter1..1) DeltaSIRafter1 Real(0.. higher layer scheduling A.212.1) The following table provides preferred sets of parameters which will be used in this version: RPP ITP DeltaSIR1 DeltaSIRafter1 DeltaSIR2 DeltaSIRafter2 mode 0 mode 0 Not needed Not needed Not needed Not needed 6. and not displayed at the OMC-R level.18.2.. Name Downlink compressed mode method Uplink compressed mode method Downlink frame type Scrambling code change Range puncturing.3 by step of 0.UMTS Radio Mobility Name RPP Range mode 0.3 by step of 0. Indicates whether normal or compressed Power Control mode is applied Initial Transmit Power is the uplink power control method to be used to compute the initial transmit power after the compressed mode gap. 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.1) DeltaSIR2 Real(0. SF/2. 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. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11. When omitted. no code change Definition Method for generating downlink compressed mode gap Method for generating uplink compressed mode gap See 25.3 by step of 0.4 STATIC PARAMETERS This set of parameter is static. DeltaSIR2 = DeltaSIR1. 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) 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.06/EN Approved_Standard 17/Sep/2010 Page 237/244 . ITP mode 0.. mode 1 DeltaSIR1 Real(0.

6. HLS. In the Iur case. HLS No check No check No check No check No check 6. no code change 6. the compressed mode duration is limited.5.06/EN Approved_Standard 17/Sep/2010 Page 238/244 . SF/2&HLS B. SF/2&HLS SF/2. 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. Measurement filtering Passing on or copying of this document. if a decision for handover is made.2.4. On reception of inter-system measurement report.1 2G TARGET CELL CHOICE RADIO CRITERIA DESCRIPTION At each measurement period the mobile reports the measured cells even if all neighbour cells are not measured.UMTS Radio Mobility In this version. HLS.A code change. 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). this parameter is provided by the DRNC as the Radio Link is added. Parameter received from Iur TGCFN TGSN TGL1 TGL2 TGD TGPRC TGPL1 TGPL2 Downlink compressed mode method Uplink compressed mode method Downlink frame type DeltaSIR1 DeltaSIRafter1 DeltaSIR2 DeltaSIRafter2 Alcatel-Lucent RNC control No check No check No check No check No check No check No check No check SF/2. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.18. In case no valid value is provided by the DRNC. the Alcatel-Lucent SRNC uses 0 as a default value.5. HLS SF/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. 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. these parameters will be using the following values: Static parameters per Ul/DlAsConf: Downlink compressed mode method Uplink compressed mode method Downlink frame type Scrambling code change SF/2.

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
Object/Class RadioAccessService Class3 GsmNeighbouringCell Class3 Definition Threshold on GSM carrier RSSI for inter-system target cell eligibility Offset used for "target cell equalization"

Name minimumGsmRssiValueForHO gsmCellIndivOffset

6.6.

FDD TARGET CELL CHOICE INTER FREQUENCY RADIO CRITERIA DESCRIPTION

6.6.1

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 3step 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.
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 239/244

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
Object/Class UMTSFddNeighbouringCell Class3 DlUserService Class3 DlUserService Class3 Definition Offset used for "target cell equalization" CPICH Ec/No threshold for inter-frequency cell eligibility CPICH RSCP threshold for interfrequency cell eligibility

Name neighbouringCellOffset minimumCpichEcNoValueForHO minimumCpichRscpValueForHO

6.7. 6.7.1

NEIGHBOR CELLS FLEXIBLE MANAGEMENT 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.
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 240/244

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
Object/Class gsmNeighbouringCellList Definition Enum (sib11AndDch,sib11Usage,dchUsage) Indicates if the cell has to be put in SIB11 and/or the Measurement Control messages. 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. 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. This parameter is used to enable/disable feature "SIB11 enhancements" allowing to add more than 48 neighbour cells to System Information Block type 11

Name Sib11OrDchUsage

Sib11OrDchUsage

UMTSFddNeighbouringCell

SIB11AndDCHNeighbouringFddCellAlgo

FDDCell Class 3

isEnhancedSib11Allowed

FDDCell Class 3

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 241/244

UMTS Radio Mobility

7.
7.1.

ABBREVIATIONS AND DEFINITIONS
ABBREVIATIONS
AAL2 signalling Always On Absolute Radio Frequency Channel Number Asynchronous Transfer Mode Broadcast Control Channel Base transceiver Station Identity Code Base Transceiver Station Call Admission Control Component Administration System Connection Frame Number Cell Individual Offset Compressed Mode Core Network Common Pilot Channel Controlling Radio Network Controller Circuit Switched Circuit Switched Data Dedicated Common Channel Dedicated Channel Drift RNC Diversity Handover Downlink Shared Channel Dedicated Traffic Channel Dual Transfer Mode Enhanced DCH Evolved Packet System Fast Access Channel Frequency Division Duplex General Packet Radio Service GPRS Tunnelling Protocol Hierarchical Cell Structure Hard HandOver Higher Layer Scheduling High Speed Downlink Packet Access High Speed Downlink Shared CHannel High Speed Uplink Packet Access Home Subsciber Server Interactive/Background Inter Frequency Intelligent Multi Carrier RRC Connection Allocation Intelligent Multi Carrier Traffic Allocation Internet Protocol Inter RAT – usually GSM measurements or GSM handover Latest Time Of Arrival Mobile Application Part Mobility Management Entity Mobile Switching Centre Narrow Band Node B Application Part Paging Channel PDN Gateway Packet Switched Radio Access Bearer

ALCAP AO ARFCN ATM BCCH BSIC BTS CAC CAS CFN CIO CM CN CPICH CRNC CS CSD DCCH DCH DRNC DHO DSCH DTCH DTM E-DCH EPS FACH FDD GPRS GTP HCS HHO HLS HSDPA HS-DSCH HSUPA HSS I/B IF iMCRA iMCTA IP IRAT LTOA MAP MME MSC NB NBAP PCH PGW PS RAB

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 242/244

1F.0 Call trace enhancement Air Status Measurement SHO.1B.2. Full event support and HHO towards CDMA State transitioning enhancements Support of WCDMA to Reporting quantity Periodic: Ec/No&RSCP Event 2D.1E. 27219 34227 30443.UMTS Radio Mobility RACH RAN RAT RANAP RB RL RNC RNS RNSAP RRC RSCP SCCP SF SGSN SGW SHO SIB SRB SRLR SRNC SRNS TDD TGCFN TGPRC TGPS TRB UP URA UTRAN WB Random Access Channel Radio Access Network Radio Access Technology Radio Access Network Application Part Radio Bearer Radio Link Radio Network Controller Radio network subsystem Radio network subsystem Application part Radio Resource Control Received Signal code Power Subsystem Connection Control Protocol Spreading Factor Serving GPRS Support Node Signalling Gateway Soft HandOver System Information Block Signalling Radio Bearer Synchronous Radio Link Reconfiguration Serving RNC Serving Radio network subsystem Time Division Duplex TGPS CFN TGPS Repetition Count Transmission Gap Pattern Sequence Traffic Radio Bearer User Plane UTRAN Registration Area Universal Terrestrial Radio Access Network Wide Band 7. 2D.2F Ec/No Event 2D. Feature HHO 3G3G Full Event trigger support Full Event trigger support HHO 3G2G UA06.06/EN Approved_Standard 17/Sep/2010 Page 243/244 . once(meas ctrl or SIB11): Ec/No Event 1D.1D. use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.1J) XOR periodic intra freq Ec/No&RSCP Periodic.1C. APPENDIX 1: EVENTS CONFIGURATION Feature ID 17569 27219 27219 xxxxxx 32525 33692 xxxxxx. 3A or (1A Nb Criteria Mobility 1 Mobility 2 Mobility 2 Mobility 1 Call Trace 1 Call Trace Mobility 1 7 Group Category Inter Frequency Inter Frequency Inter Frequency Inter RAT Intra Frequency Intra Frequency Intra Frequency Mobility Mobility 1 2 Intra Frequency Intra Frequency Passing on or copying of this document.1F. 1E. DEFINITIONS Empty chapter.2F RSCP Periodic: GSM Carrier RSSI Periodic: CPICH Ec/No&CPICH RSCP Periodic: CPICH Ec/No&CPICH RSCP SIB11 XOR (1A.

06/EN Approved_Standard 17/Sep/2010 Page 244/244 . use and communication of its contents not permitted without Alcatel·Lucent written authorization UMT/SYS/DD/0054 11.once.0 call trace enhancements Air Status Measurement ATT Perf monitoring Always ON Call Trace Call Trace Monitoring RRM 1 1 1 1 Quality Quality Quality Traffic Volume 33565 UA06 Always on devlopment RRM 1 Traffic Volume 34227 30223 30250 33692 32525 24089 34226 34227 33692 27615 33331 24089 State transitioning enhancements UA05. Variance of RLC Buffer Payload for RBs multiplexed onto the same Transport channel From 0/0 only (Event 4A): .0 call trace enhancements Air Status Measurement UA06. RLC Buffer Payload . RLC Buffer Payload .0 Call trace enhancement CellId RTT positioning RAB modification State transitioning enhancements Air Status Measurement Assisted GPS Enhancements (step 2) Alarm HHO based on UL Tx power CellId RTT positioning RRM Call Trace 1 1 1 1 1 1 1 1 1 2 1 Traffic Volume UE Internal UE Internal UE Internal UE Internal UE Internal UE Internal UE Positioning UE Positioning UE Internal UE Positioning Periodic: UE Tx Power&Rx-Tx Call Trace Type 1 Periodic: UE Tx Power&UE RxCall Trace Tx Time Difference Periodic. successively: CPICH Ec/No&CPICH RSCP&Pathloss Periodic: DL TrCH BLER Periodic: DL TrCH BLER Periodic: DL TrCH BLER Event 4A . once: Rx-Tx Type1 Positioning END OF DOCUMENT  Passing on or copying of this document. once: Path Loss Periodic. Variance of RLC Buffer Payload for RBs multiplexed onto the same Transport channel Event: 4A (1 per ul DCH) Periodic: UE transmitted power Mobility Monitoring Positioning Positioning 1 1 1 1 Intra Frequency Intra Frequency Intra Frequency Intra Frequency 30223 30250 33692 34212 xxxxxx UA05. Average of RLC Buffer Payload .UMTS Radio Mobility 33853 21302 33814 34212 24089 77736 CDMA handover HHO intra Freq inter RNC ATT Perf monitoring CellId RTT positioning Non GPS LBS and 1C) Event: 1A Periodic: CPICH Ec/No&CPICH RSCP Periodic. once: Tx Type2 Positioning Event 6A: UE transmitted power RRM UE TX power (additional meas of RRM 4A) GPS timing of cell frame Call Trace Periodic: GPS timing of cell Positioning frame Event 6A and 6B: Ue Mobility Transmitted power Periodic. Average of RLC Buffer Payload .