UMTS Radio Mobility

UMTS Radio Mobility
Document number: Document issue: Document status: Date: UMT/SYS/DD/0054 08.08/EN Standard 09/Oct/2008 External document
Copyright 2007 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
29/AUG/2007
Issue 07.01 / EN, Preliminary New version for UA06.0 Integration of Intra-frequency event triggered measurement reporting FN in mobility FN.
17/SEP/2007
Issue 07.02 / EN, Preliminary Update after review
21/SEP/2007
Issue 07.03 / EN, Standard Standard edition
22/NOV/2007
Issue 07.04 / EN, Standard Update for compliance with UA06 POR
14/Feb/2008
Issue 08.01 / EN, Preliminary New version for additional UA06.0 features: 32601 34151 34224 34167 34229 34230 34231 34274 IMCTA Enhancements for WPS [USA Market] Immediate HO of Emergency Calls [USA Market] IF/IRAT Measurements Evolution [USA Market] Defense Mechanism for UE not Supporting CM with HSPA Mobility - Inter-freq HO Enhancements [USA Market] Mobility - IRAT Enhancements [USA Market] Mobility - SHO Enhancements [USA Market] Compound neighbour list developments (IFREQ/IRAT)
06/Mar/2008
Issue 08.02 / EN, Preliminary Update after review
Passing on or copying of this document, use and communication of its contents not permitted without AlcatelLucent written authorization
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 2/213
UMTS Radio Mobility 12/Mar/2008

31/Mar/2008
Issue 08.04 / EN, Standard Correction of release naming to UA06.0
18/Jul/2008
Issue 08.05 / EN, Draft Addition of Service Type PS Conversational Correction of functionality for features 34151 and 34224 UA06 special handling of 1a, 1b, 2d, 2f hysteresis
01/Aug/2008
01/Oct/2008
Issue 08.07 / EN, Draft Additions for UA06 feature 30744 HSUPA Over Iur [Global Market]
09/Oct/2008
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 3/213
UMTS Radio Mobility
CONTENTS
CONTENTS ............................................................................................................................................. 4 1. INTRODUCTION ........................................................................................................................... 9 1.1. 1.2. 1.3. 1.4. 2. OBJECT ................................................................................................................................... 9 SCOPE OF THIS DOCUMENT....................................................................................................... 9 AUDIENCE FOR THIS DOCUMENT ................................................................................................ 9 DEFINITIONS AND SPECIFICATION PRINCIPLES ........................................................................... 9
RELATED DOCUMENTS ........................................................................................................... 10 2.1. 2.2. APPLICABLE DOCUMENTS ....................................................................................................... 10 REFERENCE DOCUMENTS ....................................................................................................... 11
3.
DEFINITIONS & CONCEPTS ..................................................................................................... 12 3.1. NETWORK ARCHITECTURE ...................................................................................................... 12
3.2. 3GPP BASIC PROCEDURES ...................................................................................................... 13 3.2.1 Soft Handover............................................................................................................... 13 3.2.2 Softer handover ............................................................................................................ 13 3.2.3 Hard handover.............................................................................................................. 14 3.2.4 Cell reselection ............................................................................................................. 15 3.2.5 SRNS relocation ........................................................................................................... 15 3.2.6 Radio Link Reconfiguration .......................................................................................... 16 4. MOBILITY CASES ...................................................................................................................... 17 4.1. SOFT HANDOVER INTRA RNC.......................................................................................... 18 4.1.1 Description.................................................................................................................... 18 4.1.2 Applicability................................................................................................................... 19 4.1.3 Parameters ................................................................................................................... 19 4.1.4 Access Network impacts .............................................................................................. 19 4.1.5 Core Network impacts .................................................................................................. 19 4.2. SOFT HANDOVER INTER RNC.......................................................................................... 20 4.2.1 Description.................................................................................................................... 20 4.2.2 Applicability................................................................................................................... 22 4.2.3 Parameters ................................................................................................................... 22 4.2.4 Access Network impacts .............................................................................................. 22 4.2.5 Core Network impacts .................................................................................................. 22 4.3. SOFTER HANDOVER ......................................................................................................... 23 4.3.1 Description.................................................................................................................... 23 4.3.2 Applicability................................................................................................................... 23 4.3.3 Parameters ................................................................................................................... 24 4.3.4 Access Network impacts .............................................................................................. 24 4.3.5 Core Network impacts .................................................................................................. 24 4.4. CELL RESELECTION IN IDLE MODE .............................................................................. 25 4.4.1 Description.................................................................................................................... 25 4.4.2 Applicability................................................................................................................... 25 4.4.3 Algorithm ...................................................................................................................... 25
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 4/213
UMTS Radio Mobility

4.4.4 4.4.5 4.4.6 Parameters ................................................................................................................... 28 Access Network impacts .............................................................................................. 30 Core Network impacts .................................................................................................. 30
4.5. CELL RESELECTION IN CELL FACH AND CELL/URA PCH MODE ............................... 31 4.5.1 Description.................................................................................................................... 31 4.5.2 Applicability................................................................................................................... 35 4.5.3 Algorithm ...................................................................................................................... 35 4.5.4 Parameters ................................................................................................................... 35 4.5.5 Access Network impacts .............................................................................................. 37 4.5.6 Core Network impacts .................................................................................................. 38 4.6. 2G TO 3G HANDOVER FOR CS DOMAIN.......................................................................... 39 4.6.1 Description.................................................................................................................... 39 4.6.2 Applicability................................................................................................................... 41 4.6.3 Algorithm ...................................................................................................................... 42 4.6.4 Failure cases ................................................................................................................ 45 4.6.5 Parameters ................................................................................................................... 46 4.6.6 Access Network impacts .............................................................................................. 46 4.6.7 Core Network impacts .................................................................................................. 46 4.7. 4.8. 2G TO 3G HANDOVER FOR PS DOMAIN .......................................................................... 47 2G TO 3G HANDOVER FOR CS + PS DOMAINS............................................................... 48
4.9. 3G TO 2G HANDOVER FOR PS DOMAIN .......................................................................... 48 4.9.1 Description.................................................................................................................... 48 4.9.2 Applicability................................................................................................................... 49 4.9.3 Algorithm ...................................................................................................................... 50 4.9.4 Failure cases ................................................................................................................ 50 4.9.5 Parameters ................................................................................................................... 50 4.9.6 Access Network impacts .............................................................................................. 51 4.9.7 Core Network impacts .................................................................................................. 51 4.10. 3G TO 2G HANDOVER FOR CS DOMAIN.......................................................................... 52 4.10.1 Description.................................................................................................................... 52 4.10.2 Applicability................................................................................................................... 53 4.10.3 Algorithm ...................................................................................................................... 54 4.10.4 Failure cases ................................................................................................................ 54 4.10.5 Parameters ................................................................................................................... 55 4.10.6 Access Network impacts .............................................................................................. 55 4.10.7 Core Network impacts .................................................................................................. 56 4.10.8 Performance Management [USA Market] .................................................................... 56 4.11. 3G TO 2G HANDOVER FOR CS+PS DOMAINS ................................................................ 57 4.11.1 Description.................................................................................................................... 57 4.11.2 Applicability................................................................................................................... 63 4.11.3 Algorithm ...................................................................................................................... 64 4.11.4 Parameters ................................................................................................................... 64 4.11.5 Access Network impacts .............................................................................................. 64 4.11.6 Core Network impacts .................................................................................................. 64 4.12. INTER-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR ....................................... 65 4.12.1 Description.................................................................................................................... 65 4.12.2 Applicability................................................................................................................... 68 4.12.3 Algorithm ...................................................................................................................... 68 4.12.4 Failure cases ................................................................................................................ 68 4.12.5 Parameters ................................................................................................................... 68 4.12.6 Access Network impacts .............................................................................................. 69 4.12.7 Core Network impacts .................................................................................................. 69 4.13. INTRA-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR ....................................... 70 4.13.1 Description.................................................................................................................... 70 4.13.2 Applicability................................................................................................................... 70
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 5/213
UMTS Radio Mobility

4.13.3 4.13.4 4.13.5 4.13.6 Algorithm ...................................................................................................................... 70 Parameters ................................................................................................................... 71 Access network impact................................................................................................. 72 Core network impact..................................................................................................... 72
4.14. INTER-FREQUENCY INTRA-RNC HANDOVER ................................................................ 73 4.14.1 Description.................................................................................................................... 73 4.14.2 Applicability................................................................................................................... 75 4.14.3 Algorithm ...................................................................................................................... 75 4.14.4 Failure cases ................................................................................................................ 76 4.14.5 Parameters ................................................................................................................... 76 4.14.6 Access Network impacts .............................................................................................. 76 4.14.7 Core Network impacts .................................................................................................. 76 4.14.8 Performance management [USA Market] .................................................................... 76 4.15. INTER-FREQUENCY INTER-RNC HANDOVER W ITH IUR AND MEASUREMENTS............................. 78 4.15.1 Description.................................................................................................................... 78 4.15.2 Applicability................................................................................................................... 82 4.15.3 Algorithm ...................................................................................................................... 82 4.15.4 Failure cases ................................................................................................................ 83 4.15.5 Parameters [USA Market]............................................................................................. 83 4.15.6 Access Network impacts .............................................................................................. 83 4.15.7 Core Network impacts .................................................................................................. 83 4.15.8 Performance management [USA Market] .................................................................... 83 4.16. HSDPA AND HSUPA MOBILITY ......................................................................................... 84 4.16.1 Description.................................................................................................................... 84 4.16.2 Applicability................................................................................................................... 89 4.16.3 Algorithm ...................................................................................................................... 89 4.16.4 Parameters ................................................................................................................... 89 4.16.5 Access Network impacts .............................................................................................. 89 4.16.6 Core Network impacts .................................................................................................. 89 4.17. SRNS RELOCATION UE NOT INVOLVED [GLOBAL MARKET] ....................................... 90 4.17.1 Description.................................................................................................................... 90 4.17.2 Applicability................................................................................................................... 90 4.17.3 Algorithm ...................................................................................................................... 90 4.17.4 Parameters ................................................................................................................... 90 4.17.5 Access Network impacts .............................................................................................. 90 4.17.6 Core Network impacts .................................................................................................. 90 4.18. 3G2G REDIRECTION AT RRC ESTABLISHMENT FOR SPEECH CALLS ........................ 91 4.18.1 Description.................................................................................................................... 91 4.18.2 Applicability................................................................................................................... 91 4.18.3 Algorithm ...................................................................................................................... 92 4.18.4 Parameters ................................................................................................................... 93 4.18.5 Access Network impacts .............................................................................................. 93 4.18.6 Core Network impacts .................................................................................................. 93 4.19. EMERGENCY AND PRIORITY CALLS ............................................................................... 94 4.19.1 Parameters ................................................................................................................... 94 4.19.2 PERFORMANCE MANAGEMENT [USA Market] ........................................................ 95 4.20. INTELLIGENT MULTI CARRIER TRAFFIC ALLOCATION (IMCTA)................................... 97 4.20.1 Description.................................................................................................................... 97 4.20.2 Applicability................................................................................................................. 100 4.20.3 Algorithm .................................................................................................................... 101 4.20.4 Parameters ................................................................................................................. 107 4.20.5 Performance Management ......................................................................................... 112 4.21. MOBILITY IN CELL_PCH AND URA_PCH RRC STATES ................................................ 113 4.21.1 Description.................................................................................................................. 113 4.21.2 Applicability................................................................................................................. 115
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 6/213
UMTS Radio Mobility

4.21.3 4.21.4 4.21.5 4.21.6 Algorithm .................................................................................................................... 115 Parameters ................................................................................................................. 115 Access Network impacts ............................................................................................ 116 Core Network Impacts ................................................................................................ 116
4.22. HCS: CELL RESELECTION CONTROL IN A HIERARCHICAL CELL STRUCTURE [GLOBAL MARKET] ............................................................................................................................ 117 4.22.1 Description.................................................................................................................. 117 4.22.2 Applicability................................................................................................................. 118 4.22.3 Algorithm .................................................................................................................... 119 4.22.4 parameters ................................................................................................................. 122 4.22.5 Access Network impacts ............................................................................................ 124 4.22.6 Core Network impacts ................................................................................................ 124 5. COMMON PROCEDURES ....................................................................................................... 125 5.1. PERIODIC MEASUREMENT REPORTING MODE .......................................................... 125
5.2. INTRA-FREQUENCY EVENT TRIGGERED MEASUREMENT REPORTING MODE ...... 125 5.2.1 Description.................................................................................................................. 125 5.2.2 configuration ............................................................................................................... 126 5.2.3 feature interworking .................................................................................................... 128 5.2.4 parameters ................................................................................................................. 129 5.3. ACTIVE SET MANAGEMENT ........................................................................................... 130 5.3.1 Algorithm for periodic reporting mode ........................................................................ 130 5.3.2 Enhanced Algorithm for periodic reporting mode....................................................... 131 5.3.3 Parameters for periodic reporting mode..................................................................... 132 5.3.4 Case of intra-frequency Event-Triggered Reporting mode ........................................ 132 5.3.5 Parameters for Event reporting mode ........................................................................ 141 5.3.6 Performance management......................................................................................... 143 5.3.7 E-DCH active set management.................................................................................. 143 5.4. PRIMARY CELL DETERMINATION.................................................................................. 145 5.4.1 Description.................................................................................................................. 145 5.4.2 Case of intra-frequency Periodic Reporting mode ..................................................... 145 5.4.3 Case of intra-frequency Event-Triggered Reporting mode ........................................ 145 5.4.4 Parameters ................................................................................................................. 147 5.5. LIST OF COMPOUNDING CELLS FOR THE MONITORED SET DEFINITION................................... 149 5.5.1 Description.................................................................................................................. 149 5.5.2 Applicability................................................................................................................. 149 5.5.3 Algorithm .................................................................................................................... 149 5.5.4 Parameters ................................................................................................................. 151 5.5.5 Performance management......................................................................................... 153 5.6. MANAGEMENT OF SYSTEM INFORMATION BLOCKS (SIB) ........................................................ 154 5.6.1 SIB Update ................................................................................................................. 154 5.6.2 SIB Repetition period.................................................................................................. 154 5.7. 5.8. INTRA-FREQ MEASUREMENTS CONFIGURATION VIA SIB11 ..................................... 155 DHO MANAGEMENT ........................................................................................................ 155
5.9. ALARM HANDOVER AND ALARM MEASUREMENTS .................................................... 157 5.9.1 Overview..................................................................................................................... 157 5.9.2 Alarm measurements activation when Intra Frequency measurements are periodic based ........................................................................................................................... 157 5.9.3 Alarm measurements activation when Intra Frequency measurements are event based 160 5.9.4 Parameters ................................................................................................................. 166 5.10. MEASUREMENTS CONFIGURATION FOR INTER-FREQ/INTER-RAT ......................... 168 5.10.1 Measurement reporting .............................................................................................. 168
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 7/213
UMTS Radio Mobility

5.10.2 5.10.3 5.10.4 5.10.5 5.10.6 Reported cells............................................................................................................. 168 Configuration for inter-system measurements ........................................................... 168 Configuration for inter-frequency measurements....................................................... 169 Change of Measurement Type ................................................................................... 169 Parameters for Measurement..................................................................................... 170
5.11. INTRA-FREQUENCY MEASUREMENTS......................................................................... 172 5.11.1 Configuration .............................................................................................................. 172 5.11.2 Missing Measurements............................................................................................... 173 5.12. COMPRESSED MODE...................................................................................................... 175 5.12.1 Introduction ................................................................................................................. 175 5.12.2 UE capability............................................................................................................... 175 5.12.3 Method........................................................................................................................ 176 5.12.4 Measurement purpose................................................................................................ 177 5.12.5 Pattern shape ............................................................................................................. 178 5.12.6 slot formats/ frame structure....................................................................................... 179 5.12.7 Procedures & messages ............................................................................................ 179 5.12.8 Impacts on RRM Specific for SF/2 method ................................................................ 183 5.12.9 HLS............................................................................................................................. 185 5.12.10 SRNS Relocation [Global Market] .......................................................................... 192 5.12.11 RNS Inter-release Compatibility Use cases ........................................................... 193 5.12.12 DRNS scenarios ..................................................................................................... 195 5.12.13 Alpha CEM cards impact ........................................................................................ 196 5.12.14 UE impacts.............................................................................................................. 197 5.12.15 Impact on other procedures .................................................................................... 197 5.12.16 Change of Alarm measurement type (Common HLS and SF/2) ............................ 200 5.12.17 Defence mechanism for UE not supporting CM with HSPA ................................... 201 5.12.18 Parameters ............................................................................................................. 202 5.13. 2G TARGET CELL CHOICE RADIO CRITERIA ................................................................ 208 5.13.1 Description.................................................................................................................. 208 5.13.2 Parameters ................................................................................................................. 208 5.14. FDD TARGET CELL CHOICE INTER FREQUENCY RADIO CRITERIA .......................... 209 5.14.1 Description.................................................................................................................. 209 5.14.2 Parameters ................................................................................................................. 209 5.15. NEIGHBOR CELLS FLEXIBLE MANAGEMENT ............................................................... 210 5.15.1 Description.................................................................................................................. 210 5.15.2 Algorithm .................................................................................................................... 210 5.15.3 Parameters ................................................................................................................. 211 6. ABBREVIATIONS AND DEFINITIONS .................................................................................... 211 6.1. 6.2. 6.3. ABBREVIATIONS.............................................................................................................. 211 DEFINITIONS .................................................................................................................... 213 UA06 VALUE MAPPING FOR HYSTERESIS AND W EIGHT USA MARKET ................................. 213
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 8/213
UMTS Radio Mobility
1.
1.1.
INTRODUCTION
OBJECT
This document specifies the UMTS mobility procedures for mobiles connected to the network. Intersystem mobility procedures (to and from GSM) are also described in this document. Although this document is focused on UTRAN, it also addresses radio mobility procedure applicable to the Core Network.
How is the document structured? Chapter3 presents definitions and concepts which will be used throughout the document. Chapter4 contains the mobility cases supported in this version of the document Chapter5 contains common procedures used in several mobility cases (such as measurement processing, compressed mode ...)
1.2.
SCOPE OF THIS DOCUMENT

This document applies to UA06.0 of Alcatel-Lucent UTRAN.
1.3.
AUDIENCE FOR THIS DOCUMENT

This is an external document.
1.4.
DEFINITIONS AND SPECIFICATION PRINCIPLES

The present document addresses several markets with potentially different behaviours in those markets. The definition of Global Market and USA Market are: Global Market: customers other than those part of the following market. USA Market: customers with UTRAN where Alcatel-Lucent 939X Node B (former Lucent Flexent Node B) is deployed.
For the purpose of the present document, the following notations apply: [Global Market] This tagging of a word indicates that the word preceding the tag "[Global Market]" applies only to the Global Market. This tagging of a heading indicates that the heading preceding the tag "[Global Market]" and the section following the heading applies only to the Global Market.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 9/213
UMTS Radio Mobility

[USA Market] This tagging of a word indicates that the word preceding the tag "[USA Market]" applies only to the USA Market. This tagging of a heading indicates that the heading preceding the tag "[USA Market]" and the section following the heading applies only to the USA Market. This tagging indicates that the enclosed text following the "[Global Market - " applies only to the Global Market. Multiple sequential paragraphs applying only to Global Market are enclosed separately to enable insertion of USA Market specific (or common) paragraphs between the Global Market specific paragraphs. This tagging indicates that the enclosed text following the "[USA Market - " applies only to the USA Market. Multiple sequential paragraphs applying only to USA Market are enclosed separately to enable insertion of Global Market specific (or common) paragraphs between the USA Market specific paragraphs.
[Global Market - ]
[USA Market - ]
Text that is not identified via one of the hereabove tags is common to all markets.
2.
2.1.
RELATED DOCUMENTS
APPLICABLE DOCUMENTS
[A1] [A2] [A3] [A4] [A5] [A6] [A7] 25.413 25.423 25.433 25.331 25.304 44.018 25.133 UTRAN Iu interface RANAP signalling UTRAN Iur interface RNSAP signalling UTRAN Iub interface NBAP signalling 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; Radio Resource Control (RRC) protocol Requirements for support of radio resource management (FDD)
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 10/213
UMTS Radio Mobility
2.2.
REFERENCE DOCUMENTS
[R1] [R2] [R3] [R4] [R5] [R6] [R7] [R8] [R9] UMT/SYS/DD/000031 Traffic Management UMT/SYS/DD/000034 PS Call Management UMT/SYS/DD/013000 Mobility Performance Improvements UMT/SYS/DD/013319 HSDPA System Specification UMT/SYS/DD/013008 Intra-frequency Event Triggered Measurement Reporting Functional Specification UMT/SYS/DD/018827 E-DCH System Specification UMT/SYS/DD/000128 IRM - Intelligent Rab mapping UMT/SYS/DD/18470 NN-20500-028 SRNS Relocation UE not involved Alcatel-Lucent 9300 W-CDMA Product Family Counter Reference Guide - RNC Counters
[R10] UMT/SYS/DD/000086 UTRAN Power Management [R11] UMT/SYS/DD/023088 UE dedicated scenarios [R12] UMT/SYS/DD/023091 Preemption [R13] UMT/SYS/DD/010042 3G-2G Emergency redirection
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 11/213
UMTS Radio Mobility
3.
3.1.
DEFINITIONS & CONCEPTS

NETWORK ARCHITECTURE
The following figure briefly presents the UMTS network elements which are relevant to mobility features.
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.413. RANAP is the Radio Access Network Application Part. This protocol specifies radio network layer signalling procedures between RNCs and CN on the Iu interface. RNSAP: specified in 25.423. RNSAP is the Radio Network Subsystem Application Part. This protocol specifies radio network layer signalling procedures between RNCs in UTRAN on the Iur interface. NBAP: specified in 25.433. NBAP is the NodeB Application Part. This protocol specifies radio network layer signalling procedures between RNC and Node B on the Iub interface. RRC: specified in 25.331. RRC is the Radio Resource Control protocol for the UE-UTRAN radio interface. This protocol terminates in the UE and in the Serving RNC. RRC messages are sent over the Iub and Uu interfaces (and possibly the Iur interface) ALCAP: ALCAP refers to AAL2 Signalling and is specified in ITU-T/Q2630.1. AAL2 is one of the transport layer used in UTRAN, and also between UTRAN and Core Network for CS applications.
In the Core Network: MAP: specified in 29.002. MAP is the Mobile Application Part. This protocol specifies the signalling procedures between the CS Core Network nodes. GTP: specified in 29.060. GTP is the GPRS Tunnelling Protocol. This protocol specifies the signalling procedures between the PS Core Network nodes.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 12/213
UMTS Radio Mobility
3.2.
3GPP BASIC PROCEDURES
This chapter intends to clarify the basic mobility procedures which are applicable to UMTS UTRAN/FDD networks, irrespective of the version to which this document applies. The intention is also to set some vocabulary basis that will be used throughout the document. The mobility cases specified in the following sections are all using those basic procedures, i.e.: soft handover hard handover cell reselection (UE controlled mobility) SRNS relocation radio link reconfiguration
3.2.1 SOFT HANDOVER

The soft handover is a procedure allowing the mobile to do it before break it i.e. swapping from one cell to another one without call interruption by opposition to hard handover (i.e. some PDU may be lost). As a matter of fact, the mobile is connected to a set of cells known as the active set and takes benefit from macro-diversity. The figure below is an example of soft handover.
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, the soft handover may be either: intra-NodeB: the cells belong to the same NodeB (In case the NodeB performs recombination between radio links, this case is called softer handover; refer to 3.2.2) inter-NodeB: the cells belong to different NodeB intra-RNC: the NodeB involved in the active set are all controlled by the same RNC (the controlling RNC) inter-RNC: the NodeB involved in the active set are controlled by different RNC (requires Iur) Soft handover only applies to dedicated physical channels and E-DCH. Soft handover cannot be applied to shared or common transport channels (e.g. DSCH, FACH...).
3.2.2 SOFTER HANDOVER

In the softer handover case, the macro-diversity radio links belong to the same NodeB.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 13/213
UMTS Radio Mobility

NodeB Cell 1 Cell 2
UE
Figure 3: softer handover example Soft and softer handover may be combined (i.e. used at the same time for a given mobile)
3.2.3 HARD HANDOVER

Hard handover is a category of handover procedures where all the old radio links in the UE are abandoned before the new radio links are established (break it before make it). Hard handover may occur in UTRAN in the following cases: when using shared channels (DSCH transport channel) or common channels (FACH transport channel) when the Iur is not present and the UE is changing RNC (i.e. soft handover is not possible) when the UE is handed over another UTRAN carrier when the UE is handed over another mode (e.g. TDD) when the UE is handed over another technology (e.g. GSM) when soft handover is not permitted (due to O&M constraint) The figure below is an example of hard handover.
Cell 1 Cell 2 Cell 1 Cell 2
UE Before
UE After
Figure 4: hard handover example Regarding network architecture, the hard handover may be either: intra-NodeB: the cells belong to the same NodeB inter-NodeB: the cells belong to different NodeB intra-RNC: the NodeB involved are all controlled by the same RNC (the controlling RNC) inter-RNC: the NodeB involved are controlled by different RNC inter-system: between UTRAN and GSM inter-PLMN: the NodeB involved are part of different PLMN Hard handover applies to the following RRC states: CELL_DCH (the mobile is allocated either a dedicated channels (DCH transport channel) or a shared channels (DSCH transport channel)) CELL_FACH (the mobile is using common transport channels), as an option from the network
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 14/213
UMTS Radio Mobility
3.2.4 CELL RESELECTION

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

This procedure is used to move the UTRAN anchor point from the serving RNC to another RNC (the UTRAN anchor point is the node in which the mobile-network RRC connection and RLC/MAC radio protocols are terminating). Depending on the network topology, a SRNS relocation may be either intra or inter MSC or SGSN. The figure below is an example of SRNS relocation, from RNC1 to RNC2:
Before HLR SGSN After HLR SGSN
SGSN
MSC
MSC
SGSN
MSC
MSC
RRC RLC MAC
RNC1
RNC2
RNC1
RNC2
RRC RLC MAC
Figure 5: SRNS relocation example
SRNS relocation may be used in many cases: incoming intersystem handover (in this case, the source RNC is actually a 2G-BSC) outgoing intersystem handover (in this case, the target RNC is actually a 2G-BSC) UTRAN radio mobility in case Iur is not present, or some Iur needed functions are not supported (this may also happen in case of handover between 2 PLMN) UTRAN radio mobility in case Iur is overloaded SRNS relocation for optimisation of UTRAN Iur routing SRNS relocation for optimisation of UTRAN parameters
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 15/213
UMTS Radio Mobility

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

Refer to [R1] for details.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 16/213
UMTS Radio Mobility
4.
MOBILITY CASES
This chapter describes all the mobility cases applicable for the current version of the document. The complete list of cases is summarized in the table below: Section 4.3 4.1 4.2 4.12 4.13 4.14 4.15 4.16 4.17 4.18 4.19 4.20 4.21 4.22 4.7 4.7 4.10 4.10 4.6 4.7 4.8 4.10.8 4.4 4.4 4.4 4.5 4.5 4.5
Softer Handover Soft Handover, intra-RNC Soft Handover, inter-RNC Inter-frequency Inter-RNC Handover without Iur (i.e. SRNS UE involved) Intra-frequency Inter-RNC Handover without Iur (i.e. SRNS UE involved) Hard handover inter-frequency, 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 3G to 2G 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.0, Inter Frequency Hard Handover or Inter System Hard Handover are triggered by the iMCTA function for Alarm, Service or CAC failure reason (refer to 4.20 section). .
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 17/213
UMTS Radio Mobility
4.1.
SOFT HANDOVER INTRA RNC
4.1.1 DESCRIPTION
In this case, the links which are added/withdrawn from the active set are all managed by the SRNC (i.e. the RNC in charge of the RRC connection with the mobile). Radio link recombination is performed at the SRNC level. For further details on this process, please refer to the "DHO management" section in the Common procedures chapter.
Iu SRNC Iub
NodeB 1
NodeB 2
New radio link to be added
UE
Figure 6: soft handover overview
In this case, there is already a macro-diversity link supported by the Serving RNC (NodeB1). A new link from NodeB2 is added:
UE
NodeB 2 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
Figure 7: Radio Link addition (1) based on active set evaluation process result, a new branch is added using the NodeB 2. This implies a new radio link to be setup with the NodeB 2, and the associated AAL2 Cid(s) to be allocated. The Node B shall only consider a transport bearer synchronised after it has received at least one DL DATA FRAME on this transport bearer before LTOA (Latest Time of Arrival). (2) once new resources are created, the mobile active set is updated with the new radio link The next dataflow is an example of radio link removal.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 18/213
UMTS Radio Mobility

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, the SRNC decides to remove a radio link from the active set. The mobile active set is updated with the new configuration. (2) the link is deleted at the NodeB, and the AAL2 Cid(s) are released. For details on the active set evaluation process, please refer to the [Active Set Evaluation] section in the Common Procedures chapter
4.1.2 APPLICABILITY
The soft handover applies only on dedicated physical resources. In this version, the active set evaluation (i.e. Decision to add/drop links) is based on the same algorithm and parameters (with possibly different values) for PS and CS calls. Therefore, soft & softer handover is a network default behaviour which applies to all PS & CS calls whatever is the user data rate. Soft & softer handover do not apply to HS-DSCH calls. Besides, it is possible to limit the number of soft handover legs being used by setting the relevant parameter to the needed value. For more details, please refer to the [Active Set Evaluation] section in the Common Procedures chapter. If the Active Set Update procedure fails, the call is kept with the previous active set cells.
4.1.3 PARAMETERS
Refer to the [Active Set Evaluation] section in the [Common Procedures] chapter.
4.1.4 ACCESS NETWORK IMPACTS

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

None. (CN is completely transparent to this procedure).
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 19/213
UMTS Radio Mobility
4.2.
SOFT HANDOVER INTER RNC
4.2.1 DESCRIPTION
In this case, the links which are added/withdrawn from the active set are not all controlled by the SRNC. In
such a case two RNCs are involved with each a different role:
the SRNC (Serving RNC): which is the RNC in charge of the RRC connection with the mobile the DRNC (Drift RNC): which is the RNC which controls the NodeB having a radio link in the active set. This DRNC acts as a router from the RNC and the UTRAN transport point of view (e.g. in this version there are as many dedicated links on the Iur as radio links which are controlled by the DRNC).
The fact that there is a DRNC in the communication path rather than only one unique SRNC is completely hidden to the mobile and the Core Network. For further details on the Radio link recombination process, please refer to the "DHO management" section in the Common procedures chapter.
Iu
SRNC Iur
DRNC Iub
NodeB 0
NodeB 1
NodeB 2
UE
Figure 9: soft handover over Iur In this case, there is already a macro-diversity link supported by the NodeB0 (controlled by the SRNC) and the NodeB1 (controlled by the Drift RNC). A new link from NodeB2 is added:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 20/213
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, a new branch is added using the NodeB2. A new radio link is setup with the NodeB 2, the associated AAL2 Cid(s) are allocated on the Iub and Iur. On the Iur, 2 separate Cid are used on the Iur for both DCCH and DTCH. Since there is already a macro-diversity link controlled by the DRNC for that communication, there is no need to build a SCCP connection between the SRNC and the DRNC (this has already been done when the Radio Link towards NodeB 1 has been setup) the SRNC is using the "Radio Link Addition" rather than "Radio Link Setup" RNSAP procedure. In the RADIO LINK ADDITION RESPONSE message, the Drift RNC provides to the SRNC the list of neighbouring cells. This information is used by the SRNC to update the list of cells to be measured by the UE. (2) Once new resources are created, the mobile active set is updated with the new radio link
The next dataflow is an example of radio link removal.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 21/213
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, the SRNC decides to remove a radio link from the active set. The mobile active set is updated with the new configuration. (2) the link is deleted at the NodeB, the Iub AAL2 Cid the 2 Iur AAL2 Cid are released. The SCCP released message is sent if the radio link which is removed is the last one supported by the DRNC for this mobile. For details on the active set evaluation process, please refer to the [Active Set Evaluation] section in the Common procedures chapter
4.2.2 APPLICABILITY
The soft handover inter-RNC requires the presence of an Iur between the involved RNCs. For other applicability considerations, please refer to [Soft Handover intra-RNC].
4.2.3 PARAMETERS
Refer to the [Active Set Evaluation] section in the [Common Procedures] chapter.

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

UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 22/213
UMTS Radio Mobility
4.3.
SOFTER HANDOVER
4.3.1 DESCRIPTION
In this case, the links which are added/withdrawn from the active set are all controlled by a NodeB already supporting a radio link towards the mobile, as in the following figure:
Iu
SRNC Iub NodeB
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, a new branch is added using the NodeB. There is no new AAL2 Cid to be allocated since the recombination between the 2 radio links is performed at the NodeB. When the Radio Link Addition Response is sent, the NodeB start UL reception and DL transmission on the new radio link. (2) once new resources are created, the mobile active set is updated with the new radio link For further details on the active set evaluation process, please refer to [Active Set Evaluation] section in the Common procedures chapter For further details on the Radio link recombination process, please refer to the [DHO management] section in the Common procedures chapter. A new UA06.0 feature can be activated and enables Node B to support the softer handover with 3 sectors amongst any of the 6 sectors on the same frequency, i.e. without cluster limitation.
4.3.2 APPLICABILITY
Please refer to 4.1
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 23/213
UMTS Radio Mobility
4.3.3 PARAMETERS
Refer to the [Active Set Evaluation] section in the [Common Procedures] chapter. Name is6SectorsNodeb Object/Class RadioAccessService Class3
Definition Flag for 6 sectors softer HO feature activation

Support of relevant Iub procedures

UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 24/213
UMTS Radio Mobility
4.4.
CELL RESELECTION IN IDLE MODE
4.4.1 DESCRIPTION
This paragraph covers the following mobility cases: "3G to 3G cell reselection intra-frequency in Idle mode" which allows a UMTS mobile camping on a 3G cell to reselect a cell using the same technology and frequency "3G to 3G cell reselection inter-frequency in Idle mode", i.e. with 3G cells using different frequencies "3G to 2G cell reselection in Idle mode" which allows a "GSM capable" UMTS mobile to reselect a GSM cell when being in idle mode in the UMTS coverage. only UTRAN/FDD and GSM Radio Access Technologies are known and supported HCS (Hierarchical Cell Structure) in Idle mode is supported (Please refer to section 4.22; present chapter describes behaviour when HCS is not used) High mobility detection is supported
4.4.2 APPLICABILITY
This feature is applicable to any multimode (for the intersystem reselection) mobile or UTRAN/FDD mobile (for the 3G only reselection) being Idle under UMTS coverage.
4.4.3 ALGORITHM
As specified in 25.304, the algorithm 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
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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 25/213
UMTS Radio Mobility

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.
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 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.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 26/213
UMTS Radio Mobility
CELL RANKING CRITERIA

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
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 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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 27/213
UMTS Radio Mobility

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. operators policy is to keep UE cell reselection in the current frequency).
High mobility detection (if HCS not used)

If the number of cell reselections during period non-TCRmax exceeds non-NCR, high-mobility has been detected. When the number of cell reselection during time period non-TCrmaxHyst no longer exceeds non-NCR, UE shall: Continue these measurement during non-TCrmaxHyst; If the criteria for entering high mobility is not detected during time period non-TCrmaxHyst: Exit high-mobility.
The high mobility state doesnt mean the mobile speed is high but the number of reselection is high.
4.4.4 PARAMETERS
This paragraph lists all the parameters needed when HCS is not used and displayed to the operator at the OMC-R. All those parameters are broadcast on the BCCH using either SIB3 for cell reselection parameters related to the serving cell; SIB11 for cell reselection parameters related to neighbouring cells.
AT UTRAN/FDD CELL LEVEL

Information Element qualMeas sIntraSearch sSearchRatGsm sInterSearch qQualMin qRxLevMin 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. Integer (-32..20 by step of 2) In [dB] Integer (-32..20 by step of 2) In [dB] Integer (-32..20 by step of 2) In [dB] Integer (-24..0) Ec/N0, In [dB] Integer (-115..-25 by step of 2) RSCP, In [dBm] As of UA04.2 Integer (-58..-13 by step of 2) Integer (0..40 by step of 2) In [dB] Integer (0..40 by step of 2) In [dB] Integer (0..31) In [s] From -50 to 33 In [dBm] Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the limit for Srxlev in the serving cell below which the UE shall initiate measurements of all neighbouring cells of the serving cell. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-frequency neighbouring cells of the serving cell.
qHyst1 qHyst2 tReselection sibMaxAllowedUlTxPower OnRach sSearchHcs
3 3 3 3 3
CellSelectionInfo CellSelectionInfo CellSelectionInfo PowerConfClass CellSelectionInfo
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 28/213
UMTS Radio Mobility

sHcsRatGsm 3 CellSelectionInfo Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the RAT specific threshold in the serving cell used in the inter-RAT measurement rules. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-RAT neighbouring cells of the serving cell. Real (0..1 by step of 0.1). This specifies the scaling (multiplication) factor to be used by the UE in idle mode or RRC connected mode states for the parameters Treselection in case high-mobility state has been detected. Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-frequency case. Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-RAT case. Enumerated (not used, 30, 60, 120, 180, 240). This specifies the duration for evaluating allowed amount of cell reselection(s). This parameter is mapped to non-TCRmax or TCRmax IE for SIB3 filling depending of HCS use or not. Integer (1..16). This specifies the maximum number of cell reselections. This parameter is mapped to non-NCR or NCR IE for SIB3 filling depending of HCS use or not. Enumerated (not used, 10, 20, 30, 40, 50, 60, 70). This specifies the additional time period before the UE can exit high-mobility. This parameter is mapped to non-TCrmaxHyst or TCrmaxHyst IE for SIB3 filling depending of HCS use or not.
speedDependScalingFacto rTReselection
CellSelectionInfo
interFreqScalingFactorTRe selection
CellSelectionInfo
interRatScalingFactorTRes election
CellSelectionInfo
tCrMax
CellSelectionInfo
nCR
CellSelectionInfo
tCrMaxHyst
CellSelectionInfo
AT UTRAN/FDD NEIGHBOURING CELL LEVEL

Information Element maxAllowedUlTxPower primaryScramblingCode ulFrequencyNumber dlFrequencyNumber neighbouringCellOffset qOffset1sn qOffset2sn qQualMin qRxLevMin 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..511) This parameters equals ( 5 * FreqDL MHz ) This parameters equals ( 5 * FreqDL MHz ) Integer(-10..10) In [dB] Integer(-50..50) In [dB] Integer(-50..50) In [dB] Integer (-24..0) Ec/N0, In [dB] Integer (-115..-25 by step of 2) RSCP, In [dBm]
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 29/213
UMTS Radio Mobility
AT GSM NEIGHBOURING CELL LEVEL

Information Element maxAllowedUlTxPower Ncc Bcc GSMbandIndicator bcchFrequency gsmCellIndivOffset qOffset1sn qRxLevMin 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. Part of the BSIC bit string(3) Base Station Color Code. Part of the BSIC DCS 1800 band used, PCS 1900 band used Integer (0..1023) GSM ARFCN Integer(-10..10) In [dB] Integer(-50..50) In [dB] Integer (-115..-25 by step of 2) In [dBm]

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

Support of location registration update from a 3G to a 2G cell, for a PS or CS attached mobile.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 30/213
UMTS Radio Mobility
4.5.
CELL RESELECTION IN CELL FACH AND CELL/URA PCH MODE
4.5.1 DESCRIPTION
When in CELL_FACH, CELL PCH or URA PCH mode, although the mobile is connected to the network (there exist a RRC connection) the UE mobility is controlled by "cell re-selection rules" as in Idle mode. This paragraph covers the following mobility cases: "3G to 3G cell reselection intra-frequency in CELL_FACH or CELL/URA PCH mode" "3G to 3G cell reselection inter-frequency in CELL_FACH or CELL/URA PCH mode" "3G to 2G cell reselection in CELL_FACH or CELL/URA PCH mode" HCS (Hierarchical Cell Structure) in Fach mode is supported (Please refer to section 4.22; present chapter describes behaviour when HCS is not used)
INTRA-RNC CASE
In this case, the UE is reselecting a new cell being also controlled by the SRNC, as in the figure below (please note that the old and the new cells may also be controlled by the same NodeB).
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.
UE NodeB 1, 2 RRC/ RACH / Cell Update (cause "cell reselection") RRC/ FACH / Cell Update Confirm (RRC state = CELL_FACH, CN Information (PLMN Id, LAI, RAI), c-RNTI) 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

UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 31/213
UMTS Radio Mobility
Having re-selected the new cell, the UE generates a CELL UPDATE to the SRNC, so that the SRNC keeps the current cell updated for paging. In case the CELL UPDATE CONFIRM message either includes "CN information elements" or "Ciphering mode info" or "Integrity protection mode info" or "New C-RNTI" or "New U-RNTI", a UTRAN MOBILITY INFORMATION CONFIRM message is then answered by the mobile. In Alcatel-Lucent implementation, the CELL UPDATE CONFIRM will always contain a new-CRNTI.
INTER-RNC CASE
In this case, the UE is reselecting a new cell being controlled by an RNC different from the SRNC. As in the figure below, this RNC may possibly depend from another SGSN.
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. In this version, UTRAN does not support common channel over Iur, nor 3G to 3G SRNS Relocation. 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, the new RNC (RNC2) detects that the UE is actually connected to another SRNC. The RNC2 rejects the cell update using the RRC connection release procedure, forcing the mobile to Idle mode. RRC/ RACH / Cell Update (U-RNTI, cause cell reselection) RRC/ FACH / RRC Connection Release (U-RNTI, cause DSCR)
Figure 17: Initial RRC access, first steps when the Drift RNC2 is Alcatel-Lucent
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 32/213
UMTS Radio Mobility

Alcatel-Lucent Serving RNC1 NonAlcatel-Lucent Drift RNC2
UE
SGSN 1
SGSN 2
RRC/ RACH / Cell Update (U-RNTI, cause cell reselection) RRC message received from UE containing U-RNTI ID as addressing information. The procedure is used by the drift RNC2 to forward to the Serving RNC1 the RRC Cell Update message received on the RACH. RNSAP/ UPLINK SIGNALLING TRANSFER INDICATION / Cell Update is forwarded to the SRNC The SRNC received the cell update and starts an RRC connection release procedure, forcing the mobile to idle mode. The Serving RNC1 uses the Downlink Signalling Transfer procedure to request from the non Alcatel-Lucent Drift RNC2 the transfer of a RRC Connection Release message on the FACH. This procedure is in response to the received Uplink Signalling Transfer procedure. RNSAP/ DOWNLINK SIGNALLING TRANSFER REQUEST / RRC Connection Release (U-RNTI, cause directed signaling connection re-establishment) RRC/ FACH / RRC Connection Release (U-RNTI, cause U-RNTI, cause directed signaling connection re-establishment)
Figure 18: Initial RRC access, first steps when the Drift RNC2 is not Alcatel-Lucent
UE RNC 1 RNC 2 SGSN 1 SGSN 2
When it enters Idle mode, the UE requests for a RAU, which will be followed by a "service request" (follow-on request pending) used for re-establishing UTRAN resources corresponding to the PS services which were supported by RNC 1. RRC/ RACH / RRC Connection Request (cause re-establishment ) RRC/ FACH / RRC Connection Setup (DCCH, U-RNTI, RRC state = CELL_FACH) RRC/ RACH / RRC Connection Setup Complete RRC/ RACH / Initial Direct Transfer (Routing Area Update Request, Follow-on request pending, PS domain) SCCP/ Connection Request (Initial UE msg (Routing Area Update Request)) SCCP/ Connection Confirm
Figure 19: Initial RRC access
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 33/213
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, and security procedures are activated by the new SGSN. 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, UEAy) RRC/ Security Mode Command RRC/ Security Mode Complete RANAP/ Security Mode Complete Once security is in place, 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. 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, corresponding to the active PDP context being re-activated by the UE. In this example, the new RAB is setup in CELL_FACH state. RANAP/ RAB Assignment Request In the target RNC, the new RAB is setup in CELL_FACH state, as for a PS call establishment. Further on, based on Always-On algorithm and user traffic volume, the mobile is possibly moved to the CELL_FACH state. RRC/ FACH / RB Setup (DTCH, RRC state) RRC/ RACH / RB Setup Complete RANAP/ RAB Assignment Response GMM/ Service Accept
Figure 21: The service re-establishment phase
3G TO 2G CASE
This mobility case is similar to the inter-RNC mobility case: at some point, the mobile in PS active mode will reselect a GSM cell the mobile will perform a RA update in its new GSM cell
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 34/213
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
2G TO 3G CASE
From the UTRAN point of view, this case is equivalent to a Routing Area Update procedure followed by a PS call setup (possibly linked together using the follow-on request facility in the GMM RAU procedure).
4.5.2 APPLICABILITY
This feature is applicable to any multimode (for the intersystem reselection) mobile or UTRAN/FDD mobile (for the 3G only reselection) being in CELL_FACH mode under UMTS coverage.
4.5.3 ALGORITHM
Please refer to [Cell Reselection In Idle Mode].
4.5.4 PARAMETERS
In connected mode (CELL-FACH, CELL-PCH and URA-PCH), specific reselection parameters when HCS is not used can be sent using: SIB4 for cell reselection parameters related to the serving cell if feature broadcast of SIB4 is enabled SIB12 for cell reselection parameters related to the neighboring cells if feature broadcast of SIB12 is enabled Following activation parameters are used: Name Object/Class
FDDCell Class3
SIB4enable
SIB12enable
FDDCell Class3
isDynamicSibAlgoWithSBAllowed
RadioAccessService Class3
Definition When set to TRUE, indicates that the SIB4 feature is activated. In this case, the parameter isDynamicSibAlgoWithSbAllowed has to be set to true. YES: SIB4 is sent NO: SIB4 is not sent When set to TRUE, indicates that the SIB12 feature is activated. In this case, the parameter isDynamicSibAlgoWithSbAllowed has to be set to true. YES: SIB12 is sent NO: SIB12 is not sent This parameter activates/deactivates the use of SB block in the dynamic SIB scheduling algorithm used to broadcast SIB on the Air interface. It has to be set to true in order to broadcast SIB4 and SIB12.
The list of parameters for SIB4/12 is the same as for SIB3/11 but they are described in dedicated objects. If SIB4/SIB12 are not broadcasted, parameters of SIB3/SIB11 are used instead.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 35/213
UMTS Radio Mobility

For qHyst1, qHyst2 and tReselection it is furthermore possible to configure them differently on FACH and PCH.

Information Element qualMeas 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 onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode PowerConfClass CellSelectionInfoC onnectedMode description/comment Choice of measurement (CPICH Ec/No or CPICH RSCP) to use as quality measure for Fdd cell. Integer (-32..20 by step of 2) In [dB] Integer (-32..20 by step of 2) In [dB] Integer (-32..20 by step of 2) In [dB] Integer (-24..0) Ec/N0, In [dB] Integer (-115..-25 by step of 2) RSCP, In [dBm] As of UA04.2 Integer (-58..-13 by step of 2) Integer (0..40 by step of 2) In [dB] Integer (0..40 by step of 2) In [dB] Integer (0..40 by step of 2) In [dB] Integer (0..40 by step of 2) In [dB] Integer (0..40 by step of 2) In [dB] Integer (0..40 by step of 2) In [dB] Integer (0..31) In [s] Integer (0..31) In [s] Integer (0..31) In [s] From -50 to 33 In [dBm] Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the limit for Srxlev in the serving cell below which the UE shall initiate measurements of all neighbouring cells of the serving cell. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-frequency neighbouring cells of the serving cell. Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the RAT specific threshold in the serving cell used in the inter-RAT measurement rules. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-RAT neighbouring cells of the serving cell. Real (0..1 by step of 0.1). This specifies the scaling (multiplication) factor to be used by the UE in idle mode or RRC connected mode states for the parameters Treselection in case high-mobility state has been detected. Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or
sIntraSearch
sSearchRatGsm sInterSearch qQualMin qRxLevMin
4 4 4 4
qHyst1 qHyst1Fach qHyst1PCH qHyst2 qHyst2Fach qHyst2Pch tReselection tReselectionFach tReselectionPch sibMaxAllowedUlTxPower OnRach sSearchHcs
4 4 4 4 4 4 4 4 4 4 4
sHcsRatGsm
CellSelectionInfoC onnectedMode
interFreqScalingFactorT
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 36/213
UMTS Radio Mobility

Reselection interRatScalingFactorTR eselection tCrMax
4 CellSelectionInfoC onnectedMode Treselections,FACH for the inter-frequency case. Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-RAT case. Enumerated (not used, 30, 60, 120, 180, 240). This specifies the duration for evaluating allowed amount of cell reselection(s). This parameter is mapped to non-TCRmax or TCRmax IE for SIB3 filling depending of HCS use or not. Integer (1..16). This specifies the maximum number of cell reselections. This parameter is mapped to non-NCR or NCR IE for SIB3 filling depending of HCS use or not. Enumerated (not used, 10, 20, 30, 40, 50, 60, 70). This specifies the additional time period before the UE can exit high-mobility. This parameter is mapped to non-TCrmaxHyst or TCrmaxHyst IE for SIB3 filling depending of HCS use or not.
nCR tCrMaxHyst
CellSelectionInfoC onnectedMode CellSelectionInfoC onnectedMode

Information Element maxAllowedUlTxPower primaryScramblingCode ulFrequencyNumber dlFrequencyNumber qOffset1sn qOffset2sn qQualMin qRxLevMin cellIndivOffset 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..511) This parameters equals ( 5 * FreqDL MHz ) This parameters equals ( 5 * FreqDL MHz ) Integer(-50..50) In [dB] Integer(-50..50) In [dB] Integer (-24..0) Ec/N0, In [dB] Integer (-115..-25 by step of 2) RSCP, In [dBm] Integer [-20.0..20.0] step:0.5 In [dB]

Information Element maxAllowedUlTxPower Ncc Bcc GSMbandIndicator bcchFrequency gsmCellIndivOffset qOffset1sn qRxLevMin 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. Part of the BSIC bit string(3) Base Station Color Code. Part of the BSIC DCS 1800 band used, PCS 1900 band used Integer (0..1023) GSM ARFCN Integer(-10..10) In [dB] Integer(-50..50) In [dB] Integer (-115..-25 by step of 2) In [dBm]

Ability to broadcast the necessary parameters on the radio interface BCCH. RRC connection reject in case of unknown u-RNTI
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 37/213
UMTS Radio Mobility

Support of location registration update from a 3G to a 2G cell, for a PS or CS attached mobile.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 38/213
UMTS Radio Mobility
4.6.
2G TO 3G HANDOVER FOR CS DOMAIN
4.6.1 DESCRIPTION
DATAFLOW
In this case the mobile connected to the CS domain is moved from a 2G cell to a 3G cell.
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.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 39/213
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
Follow up procedures after successful handover from GSM to UMTS: Security Update RRC measurement setup UE capability enquiry Mobility Update [USA Market - In case of Default Configuration: Radio Link- and Bearer Configuration to ALU standard]
Figure 23: 2G to 3G handover for CS dataflow (1) Handover preparation phase. When the handover decision is made, the serving BSC sends a handover required towards the 2G-MSC and containing the target RNC ID (this IE allows the source MSC to route the message to the correct 3G-MSC/RNC). The request is forwarded to the target 3G RNC which allocates resources to support the call. The request sent from the source BSC identifies only one cell in one RNC. There is no list of possible target.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 40/213
UMTS Radio Mobility

The "Source RNC to target RNC transparent container" information element which is transferred to the target RNC contains: the UE capability the pre-defined configuration status (i.e. which pre-defined configurations have been read by the UE if exists) (2) Handover execution phase. The HANDOVER TO UTRAN COMMAND RRC message is sent from the target 3G to the UE via the MSC nodes and the serving BSC. The handover command message contains the target cell resource description. The handover is performed when the UE is successfully connected to the 3G system. The SECURITY MODE COMMAND procedure is used to trigger integrity protection in UMTS. The UTRAN MOBILITY INFORMATION procedure is used to provide the UE with PS domain Location Information, so that the mobile can initiate or resume PS activity. (3) Old resource release phase. Old radio link(s) in GSM system are released. (4) Post Handover Procedures. Security Update RRC measurement setup UE capability enquiry Mobility Update [USA Market - In case of Default Configuration: Radio Link- and Bearer Configuration to ALU standard]
TARGET RESOURCE DESCRIPTION

The description of the resource in the target cell is provided by the target RNC to the mobile using the INTERSYSTEM TO UTRAN HANDOVER COMMAND message from the GSM RR layer. There exist 3 possibilities in the 3GPP specifications for describing the target cell resource: 1. The target resource is explicitly described in the "Intersystem to UTRAN Handover command" message. In this case, the handover message will have a length estimated to 160 bytes, which will imply segmentation on the GSM RR interface (i.e. around 8 segments). 2. In order to reduce the size of the message, pre-defined configurations may be used. These configurations are broadcast on the UTRAN BCCH using SIB 16, and are possibly read by the UE when camping on GSM cell. 3. For the same reason, default configurations may also be used. These configurations are described in 25.331 RRC specifications, and shall be supported by mobiles. They all are derived from 34.108 UE conformance testing specification. In this version of the document the Alcatel-Lucent RNS either builds the handover message containing: The explicit target resource description. The impact is RR message segmentation on the GSM side. The estimated size for a HANDOVER TO UTRAN RRC message is around 180 bytes in case of a (DCCH + speech 12.2) configuration. [USA Market - The default configuration 3 for CS Voice 12.2 With this the segmentation of the handover message at GSM RR can be avoided. However, the default configuration has lower performance than the normally used configuration and a reconfiguration after successful handover is required.] [USA Market - The behaviour is configurable by parameter isGsmIratHoDefaultConfigurationUsed.]
4.6.2 APPLICABILITY
Depends on BSC algorithm.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 41/213
UMTS Radio Mobility
4.6.3 ALGORITHM
RELOCATION REQUEST MESSAGE STRUCTURE
As the RELOCATION REQUEST message is specified in 2 different specifications (24.413 for the RANAP part, 25.331 for RRC specific IE), this paragraph presents a simplified view of the structure of the message: RELOCATION REQUEST (25.413 9.1.10) source RNC to target RNC transparent container (25.413 9.2.1.28) RRC information to target RNC (25.331 14.12.1) Handover to UTRAN Info (25.331 14.12.4.1) UE Radio Access capability (25.331 10.3.3.42) Security capability (25.331 10.3.3.37) Ciphering algorithm capability Integrity protection algorithm capability Pre-defined configuration status information (25.331 14.13.2.3) UE security information (25.331 14.13.2.2) START-CS Inter-RAT UE radio access capability (25.331 10.3.8.7) Mobile Station classmark 2 Mobile Station classmark 3 nb of Iu instances (=1) Relocation type (= UE involved) target cell Id cell load information group (1) RAB to be setup List Integrity protection information Encryption information Note (1): this element is optional and treated if feature uRRM step 2 is activated.
RELOCATION REQUEST REJECTION

In this version, a RELOCATION REQUEST rejection by the target RNC can happen in the following cases: There is no resource available in target RNS to support the incoming call Based on the RAB to setup list contained by the RELOCATION REQUEST message, the RNC tries to allocate a suitable resource based on CAC algorithm. In case of congestion, a resource may not be available. [USA Market - Resource shortage can also be caused by exhaustion of the reduced Uplink Scrambling Codes for 2G->3G handover with default configuration.] The RELOCATION REQUEST has not been issued by a GSM BSS There is no explicit information element in the RELOCATION REQUEST message which indicates from which technology (i.e. GSM or UMTS) the message is issued. However, it is deduced by the target RNC by the content of the RRC information to target RNC IE, which is a mandatory part of the message. This IE may be of 2 types: In case of handover from another RAT, this IE contains a Handover to UTRAN Info container In case of SRNC relocation, this IE contains a SRNS Relocation Info container In any case, if the RNC receives the relocation request from the PS Core Network domain, it will also be rejected.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 42/213
UMTS Radio Mobility
TARGET RESOURCE ALLOCATION IN RNC

The target resource allocation algorithm in target RNC for incoming calls from 2G takes into account the following limitations from the standard: Due to the RELOCATION REQUEST message structure, there is only one target cell to be considered by the target RNC Due to limitation of the GSM standard for circuit call, there will be only one RAB in the RAB to be setup list in the RELOCATION REQUEST message Besides, in this version: The resource allocation for incoming relocation from 2G follows the same algorithm as for initial call setup resource allocation, i.e. there is no pool of reserved capacity for incoming relocation from 2G. Based on RAB parameters requested by the Core Network, the RNC will choose a Radio Bearer configuration among the ones which are supported in this version. In this case, the algorithm for RAB to RB mapping is the same as used for call initiation.
CIPHERING
The necessary information is passed from the source BSS to the target RNC using the HANDOVER REQUIRED / RELOCATION REQUEST messages so that there is no break in the ciphering: Mobile supported ciphering algorithm are provided to the mobile in the RRC container START-CS (used to initialise the 20 MSBs of all hyper frame numbers: MAC-d HFN, RLC UM HFN, RLC AM HFN, RRC HFN) is provided in the RRC container CK (UMTS ciphering Key) is provided by the 3G-MSC in the RELOCATION REQUEST (Encryption information IE), resulting from the conversion of Kc (GSM ciphering key) by the 3G-MSC. Ciphering is started by the mobile immediately after receiving the HANDOVER TO UTRAN COMMAND message.
INTEGRITY
Integrity is started by the RNC immediately after receiving the HANDOVER TO UTRAN COMPLETE RRC message. The necessary information is passed from the source BSS to the target RNC using the HANDOVER REQUIRED / RELOCATION REQUEST messages so that there is no break in the ciphering: Mobile supported integrity algorithm are provided to the mobile in the RRC container START-CS (used to initialise the 20 MSBs of all hyper frame numbers: MAC-d HFN, RLC UM HFN, RLC AM HFN, RRC HFN) is provided in the RRC container IK (UMTS Integrity Key) is provided by the 3G-MSC in the Relocation Request (Integrity protection information IE), resulting from the conversion of Kc (GSM ciphering key) by the 3G-MSC.
UE
NodeB
RNC
RRC/ Handover to UTRAN complete
RRC/ Security Mode Command RRC/ Security Mode Complete
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 43/213
UMTS Radio Mobility
DEPENDENCIES WITH GSM

For this procedure to be working correctly, it is mandatory the GSM BSS supports the UTRAN classmark change as specified in GSM TS 04.18 Release 99 (resp. 3GPP TS 44.018 Release 4 and beyond), as this message contains the following information: UE Radio Access capability ([A4] 10.3.3.42) START-CS parameter (this parameter is actually stored on the mobile USIM)
USE OF DEFAULT CONFIGURATION [USA MARKET]

The IRAT HO message should be sent within one block in GSM to reduce handover delay and increase handover success rate. The UMTS standard allows to specify individually the radio bearer and transporting channels via a large set of parameters. This results in large messages, which have to be transferred via the GSM air interface in order to inform the UE about the radio configuration for the UMTS network access. In case that segmentation is used, subsequent segments can only be transferred after acknowledgement of earlier transmitted segments. In case of handover however, the quality of the uplink may be quite poor resulting in a failure to transfer acknowledgements. This implies that it may be impossible to quickly transfer a segmented handover message. Segmentation over more than two GSM air interface blocks could have a significantly detrimental impact on handover performance. The handover performance is improved when it is possible to transfer the handover to UTRAN command within a non-segmented GSM air interface message. The usage of the default reduces the size of the HANDOVER TO UTRAN COMMAND message and thus the GSM HANDOVER COMMAND message. Default Configuration #3 (see [A4]) is supported for 12.2 kbps CS speech and transmitted in the handover command via core network and GERAN to the UE. Whether the requested RAB can be served by default configuration #3 or not depends on the Iu UP version and the offered AMR codecs in the inter-RAT relocation request as per following table: Iu UP version any any any Iu UP v1 Iu UP v2 Offered AMR codecs in 2G to 3G relocation request mono rate 12.2 mono rate != 12.2 multi rate without 12.2 multi rate with 12.2 multi rate with 12.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, indicated by receipt of the HANDOVER TO UTRAN COMPLETE message, the RNC reconfigures the radio bearer to the normal, optimized configuration. Within this reconfiguration the RLC parameters should be reconfigured, too. The RLC reconfiguration is part of feature 33598. As of the time of writing of this document it is not yet decided if the RLC reconfiguration will be available. If it is available then it advisable to enable it (parameter isRlcAMReconfigurationAllowed and isUER99RlcAmReconfigurationAllowed). If it is not available then either the use of default configurations should be disabled (parameter isGsmIratHoDefaultConfigurationUsed) or the call will have sub-optimal RLC parameter settings.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 44/213
UMTS Radio Mobility
4.6.4 FAILURE CASES

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

In case the mobile fails to synchronize or access on the new UTRAN channel, the mobile returns on the old channel it was using in the GSM source cell.
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, a handover failure message is sent to the 2G_MSC, leading to a cancellation of the handover procedure on the MAP interface. (2) As a consequence, the target RNC receives an Iu release command message from its MSC, requesting all the resources which have been allocated during the handover preparation phase to be released.
RELOCATION REJECTED BY TARGET RNC

If the relocation preparation phase fails (see possible causes in the related chapter) a relocation failure is sent from RNC to the 3G-MSC.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 45/213
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) 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
Figure 25: 2G to 3G handover for CS failure case
4.6.5 PARAMETERS
The parameters are: Name is2GTo3GCSHandoverAllowedWithinRnc Object/Class
InterFreqMeasConf Class3
isGsmIratHoDefaultConfigurationUsed [USA Market]
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 request from 2G are rejected This parameter enables/disables the use of default configurations for inter RAT handover from GSM to UMTS.

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

BSSMAP to RANAP message interworking at the 3G-MSC level. This implies not only message conversion, but also deriving RAB attributes from the current channel in use in GSM. Ciphering and integrity key conversion at the 3G-MSC
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 46/213
UMTS Radio Mobility
4.7.
2G TO 3G HANDOVER FOR PS DOMAIN
In this case the mobile connected to the network in GPRS mode is moved from a 2G cell to a 3G-PS cell.
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 In GPRS, the mobility decision is taken by the UE. The GPRS mobility is done via a Routing Area Update procedure. Once PDP context transferred from old to new SGSN, the 3G SGSN requests for a RAB establishment as for a call establishment. The next dataflow is an example of inter-SGSN 2G to 3G handover.
UE
BTS
Serving BSC
Target RNC
3G-SGSN
2G-SGSN
GMM/ RA update request 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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 47/213
UMTS Radio Mobility
4.8.
2G TO 3G HANDOVER FOR CS + PS DOMAINS
In this case the mobile connected to both CS and PS domains, and is moved from a 3G cell to a 2G cell. CS and PS parts are managed independently. The CS part is managed as described in 4.6 and the PS part as in 4.7.
4.9.
3G TO 2G HANDOVER FOR PS DOMAIN
4.9.1 DESCRIPTION
In this case the mobile connected to the network in PS mode is moved from a 3G cell to a 2G-GPRS cell.
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. In this version, the mobile is using dedicated resources for PS services in 3G network. Therefore, the handover decision is taken by the SRNC (as if it were a CS call). Meanwhile, as opposed to CS handover, the connection and resource allocation in the target system are performed on UE request.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 48/213
UMTS Radio Mobility

UE Serving NodeB Serving RNC Target BSC 2G-SGSN 3G-SGSN
RRC/ Measurement Report RRC/ Cell change order from UTRAN (BSIC, 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, the serving RNC decides to hand the mobile over a 2G cell. Following the mobile access on the 2G cells, resources are allocated in the target BSS. The cell change order message contains the target cell BSIC and BCCH ARFCN which are used by the mobile to get the target synchronisation before accessing to the network. (2) The mobile updates its location in the target 2G system using the "RA update" procedure. The PDP contexts which were active in 3G and the N-PDU and GTP-PDU counters are transferred in 2G using GTP and RANAP context transfer procedures. In this version, N-PDU and GTP-PDU will not be transferred by the RNC on the RANAP protocol. (3) Although not supported by UTRAN in this version, data forwarding may be asked by the source SGSN. Even if no data is forwarded, the old SRNC shall not complete the resource release phase until TDATAfwd (data forwarding timer). In this version, TDATAfwd is equal to 0 sec.
4.9.2 APPLICABILITY
In this version, the mobile is using either dedicated or shared resources for PS services in 3G network. Since the quality of service offered to subscribers will be better in UMTS as compared to what GPRS can offer, the PS subscribers will be kept in 3G as much as possible, and will only be handed to 2G in case of UTRAN coverage holes, or when leaving a UTRAN coverage spot. The decision to launch this mobility procedure is taken by the iMCTA function (refer to section 4.20)
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 49/213
UMTS Radio Mobility
4.9.3 ALGORITHM
HO DECISION PROCESS
Please refer to section 4.20.
MEASUREMENTS CONFIGURATION
TARGET CELL CHOICE

4.9.4 FAILURE CASES

TARGET CELL SYNCHRONIZATION FAILURE
If the mobile fails to access and synchronize on the target GSM cell, Alcatel-Lucent UTRAN allows a possible return on the old channels. In such a case, the mobile sends a CELL CHANGE ORDER FROM UTRAN FAILURE message on the channel that was used in the serving UTRAN cell(s) and re-establish on the resource that were user in 3G.
UE
Serving NodeB
Serving RNC
Target BSC
2G-SGSN
3G-SGSN
RRC/ Cell change order from UTRAN (BSIC, BCCH ARFCN) The HO fails on the target system RRC/ Cell change order from UTRAN failure
Figure 30: 3G to 2G handover for PS - failure case
Another handover will be tried as in the normal process, i.e. possibly next time the handover criteria is evaluated and using "target cell choice" algorithm as specified. No handover will be tried towards the 2nd best cell.
4.9.5 PARAMETERS
The parameters are: Name Object/Class
activationHoGsmPsAllowed
Definition This parameter indicates if the PS handover toward a GSM cell is allowed.
See also: Section 4.20; Section 5.13.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 50/213
UMTS Radio Mobility

On the UTRAN Access side: UE UTRAN DL measurement activation support of one GSM neighbouring cells information (including BSIC and ARFCN) support of relevant Iu RANAP procedures On the GSM Access side: None (in this case, the handover is seen from the BSS as a new GPRS call setup). Restrictions: data packet forwarding is not supported by the source RNC. Therefore, some packets will be lost during the handover. End-to-end reliability is supposed to be provided by transport layer (e.g. TCP). the "SRNS context transfer" procedure is not supported by the source RNC (i.e. the messaging is supported but the PDU counters are not transferred). As for "packet forwarding", the consequence is that some packets may be lost, since the target RNC doesn't know which GTP-PDU have actually been sent and acknowledged.

support of relevant RANAP procedures the 3G PDP QoS parameters need to be translated by the 3G-SGSN into 2G parameters the ciphering key CK needs to be translated into 2G GPRS ciphering key
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 51/213
UMTS Radio Mobility
4.10. 3G TO 2G HANDOVER FOR CS DOMAIN 4.10.1 DESCRIPTION

In this case the mobile connected to the CS domain is moved from a 3G cell to a 2G cell.
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.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 52/213
UMTS Radio Mobility

RRC/ Measurement Report RANAP/ Relocation Required (CM2, CM3, old BSS to new BSS information) MAP/ Prepare Handover (Handover Request) BSSMAP/ Handover Request (CM2, CM3, 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. When the handover decision is made, the serving RNC activates the relocation procedure towards the 3G-MSC. The request is forwarded to the target 2G BSS which allocates resources to support the call. The RELOCATION REQUIRED message contains the UE GSM capability (ClassMark 2 and 3). The "old BSS to new BSS" information element contains the UE capability, which is transferred to the target BSS, in case the mobile is handed over 3G again. It also contains the cell load information group element if feature uRRM step 2 is activated. (2) Handover execution phase. The HANDOVER COMMAND message from the GSM RR layer is sent from the target 2G to the UE via the MSC nodes and the serving RNC. This message contains the target cell description (i.e. BSIC and BCCH ARFCN), which will allow the mobile to synchronize to the cell when the handover is made in blind mode. The handover is performed when the UE is successfully connected to the 2G system. (3) Old resource release phase. Old radio link(s) and associated AAL2 Cid(s) are released.
4.10.2 APPLICABILITY
In this version, 3G to 2G handover for CS calls which have reached the call established state is a rescue type of mobility, triggered on radio alarm criterion. CS subscribers may be handed to 2G in case of UTRAN coverage holes, or when leaving a UTRAN coverage spot. In addition to providing this alarm-based 3G-2G handover for established calls, the 3G infrastructure may also redirect calls in the following use cases:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 53/213
UMTS Radio Mobility

iMCTA function decision (refer to section 4.20); RRC Speech Redirection: If a UE cannot successfully connect to the UTRAN (via RRC connection establishment) the RNC instructs the UE to perform inter-system cell reselection and re-originate the call on the 2G network (refer to 4.18 section).
4.10.3 ALGORITHM
HO DECISION PROCESS
TARGET CELL CHOICE

4.10.4 FAILURE CASES

TARGET CELL SYNCHRONIZATION FAILURE
If the mobile fails to access and synchronize on the target GSM cell, it has to send a HANDOVER FROM UTRAN FAILURE message on the channel that was used in the serving UTRAN cell(s).
UE
Serving NodeB
Serving RNC
Target BSC
2G-MSC
3G-MSC
RRC/ Handover from UTRAN command (BSIC, 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, i.e. possibly next time the handover criteria is evaluated and using "target cell choice" algorithm as specified. No handover will be tried towards the 2nd best cell.
RELOCATION PREPARATION FAILURE

It may happen the Relocation Preparation fails, e.g. because the target GSM BSS has no resource left. In this case, the relocation preparation procedure ends up as follows:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 54/213
UMTS Radio Mobility

RRC/ Measurement Report RANAP/ Relocation Required (CM2, CM3, old BSS to new BSS information) MAP/ Prepare Handover (Handover Request) BSSMAP/ Handover request (CM2, CM3, 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 - failure case [USA Market - If allowed by parameter isGsmIratHoToNextBestCellAllowed, if the UE had reported further eligible GSM target cells in a measurement report and if the criteria for handover are still fulfilled then the RNC retries relocation preparation for the next best GSM cell. The attempts are repeated until either The relocation preparation has failed for the last eligible GSM cell A follow-up measurement report contains both, eligible GSM and inter-frequency target cells. In this case the RNC tries the handover to the strongest inter-frequency target. The criteria for handover are no longer fulfilled, e.g. an event 2F indicates the end of the alarm condition.] Another handover will be tried as in the normal process, i.e. possibly next time the handover criteria are evaluated and using "target cell choice" algorithm as specified.
4.10.5 PARAMETERS
The parameters are: Name Object/Class
RadioAccessService Class3 RadioAccessService Class3 RadioAccessService Class3
activationHoGsmCsAllowed isCellLoadInformationSendingAllowed isGsmIratHoToNextBestCellAllowed [USA Market]
Definition This parameter indicates if the CS handover toward a GSM cell is allowed. 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, e.g. due to overload.
See also Section 4.20. Section 5.13.

On the UTRAN Access side: support of relevant Iu RANAP procedures support of relevant RRC procedures
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 55/213
UMTS Radio Mobility
On the GSM Access side: Some impacts on the A interface (new UE Capability IE in the Handover Request) Only impact is a new counter on 3G to 2G (based on the source cell " Cell identification discriminator" contained by the Handover Request)

BSSMAP to RANAP message interworking at the 3G-MSC level. This implies not only message conversion, but also deriving GSM channel type attributes from the RAB attributes.
4.10.8 PERFORMANCE MANAGEMENT [USA MARKET]

The following counters have been added in UA06.0 for USA Market: IRATHO.AttRelocPrepOutCS.NextBestCell (-.NeighbRnc) Attempted relocation preparations for CS UMTS to GSM handover to the next best GSM cell. This counter is a complement to counter IRATHO_AttRelocPrepOutCS. IRATHO_AttRelocPrepOutCS is pegged on all attempted relocation preparations for CS UMTS to GSM handover. IRATHO.AttRelocPrepOutCS.NextBestCell is pegged only if the relocation preparation has failed for one target GSM cell and the RNC retries the handover for the next GSM target cell. The difference between IRATHO_AttRelocPrepOutCS and IRATHO.AttRelocPrepOutCS.NextBestCell represents the actual number of handover attempts without repeated relocation preparation procedures. IRATHO.SuccRelocPrepOutCS.NextBestCell (-.NeighbRnc) Successful relocation preparations for CS UMTS to GSM handover to the next best GSM cell (CS inter-RAT Handover Attempt) from network point of view.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 56/213
UMTS Radio Mobility
4.11. 3G TO 2G HANDOVER FOR CS+PS DOMAINS 4.11.1 DESCRIPTION

GENERAL
In this case the mobile is connected to both CS and PS domains, and is moved from a 3G cell to a 2G cell.
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. Alternate use only. This case is not further considered in this document. class B: the mobile is attached to both GPRS and GSM services, but the mobile can only operate one set of services at a time class A: the mobile is attached to both GPRS and GSM services, and can support simultaneous traffic DTM (Dual Transfer Mode): DTM is a subset of class A mode of operation. In this mode, GSM CS and PS resource allocation are coordinated in BSC/PCU in order to simplify mobile implementation. Class A or DTM The real successful case (i.e. PS and CS services are both active in the new cell) assumes that the mobile is either GPRS Class A or DTM (Dual Transfer Mode or simple Class A) capable the new cell can offer GPRS service Regarding the CS domain, the CS service is handed over the target GSM cell exactly as in the "3G to 2G handover for CS" case, i.e.: a relocation is required by the serving RNC new resources corresponding to the CS RAB are allocated in the target system and the mobile is explicitly handed over the target resources (this is performed through the "Handover from UTRAN" RRC procedure) Regarding the PS domain, the PS service is handed over the target GSM cell in the same way as the "3G to 2G handover for PS" case, i.e.: the mobile is requested by the SRNC to change cell (this is done implicitly through the "Handover from UTRAN" RRC procedure)
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 57/213
UMTS Radio Mobility

the mobile tries to re-establish the PS service in the target cell
Class B In this case, the CS service is handed over to GSM and the PS service cannot be maintained. Since the mobile will not detach nor deactivate the PDP context which were active in the source 3G-SGSN, the PDP context will remain active in the 3G-SGSN. Remark: In this version, the source RNC will not take into account the mobile GPRS capability in the handover decision algorithm.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 58/213
UMTS Radio Mobility
SUCCESSFUL CLASS A/DTM CASE

The next dataflow is an example of successful inter-MSC 3G to 2G CS+PS handover for a class A or DTM capable mobile.
RANAP/ Relocation Required (CM2, CM3, old BSS to new BSS information) MAP/ Prepare Handover (Handover Request) BSSMAP/ Handover request (CM2, CM3, 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 3 GTP/ SGSN ctx response GTP/ SGSN ctx ack GMM/ RA update response
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

UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 59/213
UMTS Radio Mobility

(1) CS Handover preparation phase. When the handover decision is made, the serving RNC activates the relocation procedure towards the 3G-MSC. The request is forwarded to the target 2G BSS which allocates resources to support the call. (2) CS Handover execution phase. The handover command is sent from the target 2G to the UE via the MSC nodes and the serving RNC. The handover command message contains the cell description (i.e. target cell BSIC and BCCH), which will be used by the mobile to synchronise on the target cell and decode the (P)BCCH for the PS service re-establishment. The handover is performed when the UE is successfully connected to the 2G system. (3) PS service re-establishment: The UE performs a packet access in the 2G new cell. Eventually, the registration is accepted, and the PS data transfer is resumed. (4) + (5) coordinated release of old CS + PS resources Old radio links are released Iu CS resource release. AAL2 Cid(s) associated to the CS domain are released. Iu PS resource release. As for the "3G to 2G handover case", the source SGSN may request the source RNC to forward the PS packets queued in the SRNC using the SRNS DATA FORWARD COMMAND message. In that case, the RNC behaviour is the same as for the "3G to 2G PS handover" case. The data flow above is only provided as an example. The order of the different phase may be different as compared to a real case. For example, the Iu CS release (4) may be requested before the PS registration (3). In this release: upon receipt of message IU RELEASE COMMAND (CS), the RNC arms immediately a timer called RelocResourceReleasePs3Gto2Gtimer (optimized at 20 sec) and sends an IU RELEASE REQUEST (PS) message. Upon receipt of the IU RELEASE COMMAND (PS) or RelocResourceReleasePs3Gto2Gtimer expiration, the RNC coordinates release of old CS and PS resources. Upon receipt of the IU RELEASE COMMAND (PS):
RNC 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:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 60/213
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
SUCCESSFUL CLASS B CASE

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

Iu connections timers In order to cover the following case: the mobile is completely lost (i.e. the handover has failed and the mobile has not returned to the old channel) the PS service is lost during HO (e.g. because of limited UE capability (class B or C), or because the target cell cannot accept or support GPRS access) Two timers (one for the PS domain, one for the CS domain) are implemented in the RNC to request a release of UTRAN resources to the relevant CN domain. In the CS+PS case, only one timer is started, corresponding to the highest value. The following dataflow illustrate the 1st case: Phase 1 and 2 (handover preparation and execution) are performed as in the successful case. In phase 3 and 4, when the "Iu release" timer elapses, the source RNC requests for both CS and PS Iu release.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 61/213
UMTS Radio Mobility

UE NodeB RNC 3G-MSC/VLR
RANAP/ Relocation Required (CM2, CM3, old BSS to new BSS information) MAP/ Prepare Handover (Handover Request)
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 - failure case The following dataflow illustrates the 2nd case: Phase 1 and 2 (handover preparation and execution) are performed as in the successful case. Following successful CS handover the Core Network commands a release of the Iu. This release is not processed until the "Iu release timer" elapses. In which case, both Iu-CS and PS connections (and associated UTRAN resources) are released.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 62/213
UMTS Radio Mobility

UE NodeB RNC 3G-MSC/VLR
RANAP/ Relocation Required (CM2, CM3, old BSS to new BSS information) MAP/ Prepare Handover (Handover Request)
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 - failure case HO failure case The possible failure cases are the following: The synchronisation on the new CS channel fails. In that case, the mobile returns on the old channel using the Handover from UTRAN failure message and the relocation is cancelled by the source RNC, as in the CS only case. The handover for the CS service is successfully performed, but the PS registration fails (reject from the new SGSN, or because GPRS is not supported by target cell ...). In this case, nothing specific is done. The CS service goes on, whereas the PS service has failed. From a source UTRAN point of view, this case is identical to the Class B mobile handover case. Due to the time needed to resynchronise the CS service, it is not expected the PS service can be resumed in the new cell before the CS service.
Handover/call setup race condition If a 3G to 2G handover decision is made while a PS call is active and a CS call is being setup, nothing is done until the CS RAB is established. Once the CS RAB is setup, and if the handover conditions are still valid, a 3G to 2G PS+CS handover is tried. If a 3G to 2G handover decision is made while a CS call is active and a PS call is being setup, nothing is done until the PS RAB is established. Once the PS RAB is setup, and if the handover conditions are still valid, a 3G to 2G PS+CS handover is tried.
See 4.10.2 [3G To 2G Handover for CS Domain] section APPLICABILITY
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 63/213
UMTS Radio Mobility
4.11.3 ALGORITHM
HO DECISION PROCESS
TARGET CELL CHOICE

Please refer to section 4.20. It has to be noted that the UE classmark (support of class A or DTM) or the target cell GPRS capability is not taken into account in the decision process.
4.11.4 PARAMETERS
Refer to: Section 4.20. Section 5.13. Note: In the CS+PS case a handover to a 2G cell is only performed if both activationHoGsmCsAllowed and activationHoGsmPsAllowed parameters are set to "YES"

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

No specific impact, as compared to the 3G to 2G PS or CS handover. Since the Gs interface is not supported, the 2 handover procedures are seen as independent.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 64/213
UMTS Radio Mobility
4.12. INTER-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR 4.12.1 DESCRIPTION

GENERAL
The purpose of this mobility case is to allow user mobility between cells of different frequency, being controlled by different RNC not connected to an Iur. This may be used, e.g. in the 2 following cases: inter-PLMN mobility intra-PLMN mobility between 2 frequency layers In the example below, the mobile is using 2 radio links from NodeB0 and NodeB1, controlled by the SRNC. At some point, the SRNC decides to hand the UE over another cell controlled by another RNC and using another frequency (f2).
MSC Iu SRNC
MSC
RNC Iub
NodeB 0
NodeB 1
NodeB 2
f1
Target radio link f2
UE
Figure 39: inter-frequency inter-RNC handover As described in the following flow diagram, inter-frequency inter-RNC hard handover makes use of the Relocation procedure (UE involved), as the UTRAN RRC connection anchor point is moved from one RNC to another. The global process is divided into two phases: The relocation preparation in which all the needed resources are allocated in the target RNC and NodeB The relocation execution in which the mobile is handed over the new resource Relocation preparation
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 65/213
UMTS Radio Mobility

UE Serving NodeB Serving RNC Target NodeB Target RNC CN node
Based on the inter-PLMN handover criteria, a request for relocation is issue by the serving RNC. When accepted, this request triggers resource allocation within the target RNC: A radio link is allocated in the target NodeB An AAL2 circuits are allocated on Iub and Iu interfaces
RANAP/ Relocation required (RB parameters, Number of Iu instances) SCCP/ Connection Request SCCP/ Connection Confirm RANAP/ Relocation request (RB parameters, Number of Iu instances, RAB parameters) On reception of Relocation Request, 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 40: inter-frequency inter-RNC handover - relocation preparation
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 66/213
UMTS Radio Mobility

Relocation execution
UE Serving NodeB Serving RNC Target NodeB Target RNC CN node
During the relocation execution phase, a new RNTI is allocated to the mobile, integrity (and possibly) ciphering are activated. This is all done through the Radio Bearer Reconfiguration RRC procedure. RANAP/ Relocation command (Radio Bearer Reconfiguration) RRC/ Radio Bearer reconfiguration (RB to reconfigure, Physical channel configuration)
RRC/ Radio Bearer reconfiguration complete RANAP/ Relocation detect RANAP/ Relocation complete Old measurement Ids are released, and new measurements are setup by the new SRNC. RRC/ Measurement Control (id1, Release) RRC/ Measurement Control (id2, Release) RRC/ Measurement Control (id1, Setup) RRC/ Measurement Control (id2, 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 41: inter-frequency inter-RNC handover - relocation execution Remarks: From the RELOCATION REQUEST messages received, the Alcatel-Lucent target RNC tries to identify the Radio Bearer configuration which is the closest to the requested configuration. In case there is no matching configuration (i.e. there is no configuration in the target RNC that matches the number and type of radio bearer in the existing configuration managed by the serving RNC) then the relocation is failed and a RELOCATION FAILURE is sent back to the Core Network. Regarding measurement configuration, the Alcatel-Lucent target RNC deletes every measurement configured previously in the source RNC once relocation is successfully performed. All the needed measurements are then setup.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 67/213
UMTS Radio Mobility
In this version, outgoing inter-frequency handover inter-RNC is triggered upon iMCTA decision (refer to section 4.20). The feature is applicable for calls on DCH, HS-DSCH or E-DCH, with check of global activation parameters isHsdpaHHOwithMeasAllowed and isEdchHHOwithMeasAllowed. This algorithm is applicable to PS, CS and CS+PS connections.
4.12.3 ALGORITHM
HO DECISION PROCESS
TARGET CELL CHOICE

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

In case the inter-frequency handover is not successful (e.g. the mobile fails to synchronise on the target cell) there is no second try or other try to a second best eligible cell. In case of CS+PS handover, if the handover fails for one of the domains, the handover is aborted.
4.12.5 PARAMETERS
Name Object/Class
is3Gto3GWithoutIurAllowedForPS
is3Gto3GWithoutIurAllowedForCS
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.20.

UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 68/213
UMTS Radio Mobility

Section 5.14.

Support for out-going/incoming relocation to/from 3G for PS, CS and CS+PS services Support of inter-frequency compressed mode scheme Support for inter-frequency measurements
Support for the relocation procedure in PS and CS domain
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 69/213
UMTS Radio Mobility
4.13. INTRA-FREQUENCY INTER-RNC HANDOVER WITHOUT IUR 4.13.1 DESCRIPTION

This feature introduces the capability to detect the need to hard handover a call from one cell to another cell of the same frequency, but controlled by a different RNC without Iur. When all the conditions are met, the existing outgoing and incoming relocation procedures (UE involved) are invoked to execute the HHO. It may be used e.g. in following situations: Two different operators (PLMN) are using the same frequency in the same geographical area, and they have set up national roaming agreements between them In a single PLMN, where its not possible to communicate via Iur between two RNCs controlling cells of the same frequency, e.g. for IOT reasons between two RNCs from different manufacturers. The Iur interface provisioned between 2 RNCs is not in an operational state. Once the intra-frequency intra-RNC HHO condition is met, the procedure is exactly the same as for an inter-freq inter-RNC HHO (refer to 4.12.1 for detailed description).
The feature is applicable for calls on DCH, HS-DSCH or E-DCH, with check of global activation parameters isHsdpaHHOwithMeasAllowed and isEdchHHOwithMeasAllowed. It is applicable to all RABs combinations. It is applicable in full-event mode only. The application of this feature should be limited to the situations where there is no Iur between 2 RNCs and is not recommended as a general mobility mechanism.
4.13.3 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. This status is checked only when receiving measurement reports and its change does not affect measurement configuration.
MEASUREMENT CONFIGURATION
In order to separate SHO from HHO conditions, a new intra-frequency measurement is introduced. It configures event1A with measId = 14 and contains all isolated cells (cells in the monitored set that are controlled by another RNC and have no Iur interface provisioned with the serving RNC). It is configured with specific parameters (refer to 4.13.4). CIO is used. If needed, it is configured at the same time as other events 1x with measId = 1.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 70/213
UMTS Radio Mobility
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, and if the Iur interface is disabled, a SHO cannot occur. In that case, if all activation parameters allow it, following check is done: If the cell to add has a better Ec/N0 than other cells of the set and its Ec/N0 and RSCP are greater than a minimumCipchEcNoValueForHho and minimumCipchRscpValueForHho respectively, then a HHO with this target cell is decided. Otherwise, no handover (neither HHO or SHO) is attempted.
RECEPTION OF MEASUREMENT REPORT MEASID 14

On receipt of a measurement report with measId = 14 to add a cell from an isolated neighbouring RNC in the monitored set, a SHO cannot occur. In that case, if all activation parameters allow it, following check is done: If the cell to add has a better Ec/N0 than other cells of the set and its Ec/N0 and RSCP are greater than a minimumCipchEcNoValueForHho and minimumCipchRscpValueForHho respectively, then a HHO with this target cell is decided. Otherwise, no handover (neither HHO or SHO) is attempted.
4.13.4 PARAMETERS
Name isIntraFreqInterRncHhoOnIurLinkDownAllo wed
isIntraFreqInterRncHHOAllowed
Object/Class RadioAccessService Class3

RadioAccessService Class3 IntraFreqTargetCellP arams (DlUserService) Class 3 IntraFreqTargetCellP arams (DlUserService) Class 3 FullEventRepCritHho MgtEvent1AWithoutI ur (MeasurementConfCl ass) Class 3 FullEventRepCritHho MgtEvent1AWithoutI ur (MeasurementConfCl ass) Class 3 FullEventRepCritHho MgtEvent1AWithoutI
minimumCpichEcNoValueForHHO
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
minimumCpichRscpValueForHHO
amountRep
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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 71/213
UMTS Radio Mobility

ur (MeasurementConfCl ass) Class 3 FullEventHoConfHh oMgtEvent1AWithou tIur (UsHoConf) Class 3 FullEventHoConfHh oMgtEvent1AWithou tIur (UsHoConf) Class 3 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. It is related to the conditions for the change of Primary Radio Link For UA06 refer to section 6.3. Reporting Range to configure for the triggering condition of the intraFreq-interRnc Event in Full Event Mode
4.13.5 ACCESS NETWORK IMPACT

Refer to 4.12.6.
4.13.6 CORE NETWORK IMPACT

Refer to 4.12.7.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 72/213
UMTS Radio Mobility
4.14. INTER-FREQUENCY INTRA-RNC HANDOVER 4.14.1 DESCRIPTION

GENERAL
This mobility case applies to Multilayer deployment in a single operator.
RNC
f1 f2
Figure 42: Hard Handover inter-frequency intra-RNC
In this case, the RNC control cells from different frequencies (f1 and f2); f1 and f2 cells may be either 2 sectors of the same NodeB, or belong to different NodeB. The 2 frequency layers overlap and the subscribers may camp on either of the 2 layers depending on cell selection and re-selection rules and parameters. Once connected, the subscribers remain on same frequency. However, as UE are moving out of the smallest frequency spot (f1 as in the picture above), an alarm hard handover towards the other frequency is triggered by the SRNC. Similarly, an inter-frequency intra-RNC hard handover may also be performed from f2 to f1 in case of lack of f2 coverage, e.g. as in an outdoor to indoor mobility case.
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 NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp 2 NodeB 0 NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp
Figure 43: Hard Handover inter-frequency intra-RNC dataflow

In the first step, a new radio link is set up on the new target NodeB, using another frequency. In the second step, the Radio Bearer is re-configured and the old radio links (there may be more than one, depending on the current active set) are deleted. In the figure above, NodeB 0 and NodeB 1 may be the same network node.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 73/213
UMTS Radio Mobility
OVER THE IUR

The source and/or target cell may be controlled by another RNC, as in the figure below.
SRNC
DRNC
f1 f2
Figure 44: Hard Handover inter-frequency intra-RNC over the Iur

In such a case, the Radio Link Addition, Setup or Deletion is performed over the Iur interface
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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 74/213
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
RNSAP/ Radio Link deletion resp
AlCAP Iur Transport Bearer Release
Figure 45: Hard Handover inter-frequency intra-RNC dataflow over the Iur
In step (1) a new radio link is set up over Iur on the new target Drift NodeB, using another frequency. In step (2) the Radio Bearer is reconfigured. In step (3) the old radio links (there may be more than one, depending on the current active set) are deleted. The radio link belonging to the previous primary cell is to be deleted over Iur as depicted in figure above. In the figure above, Drift NodeB 0 and Drift NodeB 1 may be the same network node.
In this version, inter-frequency hard handover intra-RNC is triggered upon iMCTA decision (refer to section 4.20).
This algorithm is applicable to PS, CS and CS+PS connections. The RNSAP RL Addition procedure does not permit to reconfigure the DCH part of the call. This procedure is used in case we establish a radio link on a drift RNC (over Iur) while we have already one or more radio-links established on this D-RNC. The following restriction applies: If the handover implies the transition HSxPA->DCH for layer capabilities or target resource shortage reasons, the handover is not processed by the S-RNC. [USA Market - Intra DRNC handover is performed from DCH to DCH. HSxPA calls need to be reconfigured to DCH before the handover.]
4.14.3 ALGORITHM
HO DECISION PROCESS
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 75/213
UMTS Radio Mobility
CHOICE OF TARGET CELL


In case the inter-frequency handover is not successful (e.g. the mobile fails to synchronise on the target cell) here is no second try or other try to a second best eligible cell. [USA Market - However for intra DRNC handover a relocation procedure (refer to section 4.12) will be initiated towards the same target cell if the relocation is enabled according to section 4.12.5.]
4.14.5 PARAMETERS
[USA Market - Intra DRNC handover will be enabled/disabled by the parameter defined in section 4.15.5.] There is no new parameter associated to the intra-RNC case exclusively. The Radio criteria algorithm for inter-frequency intra-RNC handover uses the same parameters with the same values as in the inter-RNC case.

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


The following counters are defined :
HHO.AttOutInterFreq / HHO.AttOutInterFreq.NeighbRnc Total number of attempted outgoing inter-frequency hard handovers HHO.AttOutInterFreq.RSCP / HHO.AttOutInterFreq.RSCP.NeighbRnc Attempted outgoing inter-frequency hard handovers due to insufficient RSCP quality of the used frequency HHO.AttOutInterFreq.EcNo / HHO.AttOutInterFreq.EcNo.NeighbRnc Attempted outgoing inter-frequency hard handovers due to insufficient Ec/No quality of the used frequency HHO.SuccOutInterFreq / HHO.SuccOutInterFreq.NeighbRnc Total number of successful outgoing inter-frequency hard handovers HHO.SuccOutInterFreq.RSCP / HHO.SuccOutInterFreq.RSCP.NeighbRnc Successful outgoing inter-frequency hard handovers due to insufficient RSCP quality of the used frequency
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 76/213
UMTS Radio Mobility

HHO.SuccOutInterFreq.EcNo / HHO.SuccOutInterFreq.EcNo.NeighbRnc Successful outgoing inter-frequency hard handovers due to insufficient Ec/No quality of the used frequency
The counters are of cumulative type. They are defined as two sets one set on per FDDCell basis (the Primary RL of the UE is on this FDDCell) and one set on per neighboring RNC basis (the Primary RL of the UE is on this Neighboring RNC): In context of intra RNC handover the counters on per FDDCell basis will be pegged if the handover is performed within the SRNC the counters on per neighboring RNC basis will be pegged if the handover is performed within a neighboring RNC in DRNC role.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 77/213
UMTS Radio Mobility
4.15. Inter-Frequency Inter-Rnc Handover With Iur And Measurements

In release UA05, Iur is not used for that type of handover. We use SRNS Relocation UE involved instead (refer to 4.12). [USA Market - Inter-frequency handover over Iur is reintroduced in order to avoid interoperability issues which may occur in case of SRNS Relocation with other vendors RNCs. SRNS Relocation UE involved is still used if handover over Iur is disabled towards the target DRNC or as fallback option in case of the handover attempt over Iur having been unsuccessful.]
4.15.1 DESCRIPTION
GENERAL
The purpose of this mobility case is to allow user mobility between cells of different frequencies (f1and f2) being controlled by different RNCs connected to an Iur. Depending on the allocation of the source cell on f1 (primary cell of the current active set) and the target cell on f2 the inter-frequency inter RNC hard handover is to be performed
from SRNC to DRNC [USA Market] from DRNC to DRNC [USA Market] from DRNC to SRNC
as detailed below.
FROM SRNC TO DRNC [USA MARKET]

This scenario is characterized by the primary cell on f1 being controlled by the SRNC and the target cell on f2 cell being controlled by a DRNC. If the call is HSxPA then it needs to be reconfigured to DCH before the handover because direct handover from HSxPA to HSxPA is not supported towards a DRNC.
SRNC
DRNC f1 f2
Figure 46: Hard Handover inter-frequency inter-RNC from SRNC to DRNC
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 78/213
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)
UE
NodeB0
Serving RNC
NBAP/ Radio Link deletion req NBAP/ Radio Link deletion resp 3 AlCAP Iub Transport Bearer Release
Figure 47: Hard Handover inter-frequency inter-RNC data flow from SRNC to DRNC
In step (1) a new radio link is set up over Iur on the new target Drift NodeB, using another frequency. In step (2) the Radio Bearer is reconfigured. In step (3) the old radio links (there may be more than one, depending on the current active set) are deleted. The radio link belonging to the previous primary cell is to be deleted directly over Iub without Iur being involved as depicted in figure above.
FROM DRNC TO DRNC [USA MARKET]

This scenario is characterized by the primary cell on f1 being controlled by a DRNC and the target cell on f2 being controlled by another DRNC while the SRNC remains the same. If the call is HSxPA then it needs to be reconfigured to DCH before the handover because direct handover from HSxPA to HSxPA is not supported towards a DRNC.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 79/213
UMTS Radio Mobility
SRNC DRNC
DRNC f1 f2
Figure 48: Hard Handover inter-frequency inter-RNC from DRNC to DRNC
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)
UE
Drift NodeB0
Drift RNC
Serving RNC
Figure 49: 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.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 80/213
UMTS Radio Mobility

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

This scenario is characterized by the primary cell on f1 being controlled by a DRNC and the target cell on f2 cell being controlled by the SRNC. If the call is HSxPA then it can be handed over directly with HSxPA being kept. There is no need for HSxPA to DCH reconfiguration.
SRNC
DRNC f1 f2
Figure 50: Hard Handover inter-frequency inter-RNC from DRNC to SRNC
UE
NodeB 1 RRC/ Measurement Report NBAP/ Radio Link Setup req NBAP/ Radio Link Setup resp
Serving RNC
AlCAP Iub Transport Bearer Setup
FP/ DL Sync (CFN) FP/ UL Sync (ToA) RRC/ Radio Bearer Reconfiguration RRC/ Radio Bearer Reconfiguration complete 2
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 81/213
UMTS Radio Mobility

UE Drift NodeB0 Drift RNC Serving RNC
Figure 51: Hard Handover inter-frequency inter-RNC data flow from DRNC to SRNC
In step (1) a new radio link is set up on the new target NodeB, using another frequency. This radio link is to be setup directly over Iub without Iur being involved. In step (2) the Radio Bearer is reconfigured. In step (3) the old radio links (there may be more than one, depending on the current active set) are deleted. The radio link belonging to the previous primary cell is to be deleted over Iur as depicted in figure above.
In this version, inter-frequency hard handover inter-RNC is triggered upon iMCTA decision (refer to section 4.20). This algorithm is applicable to PS, CS and CS+PS connections. [USA Market - The RNSAP RL Setup procedure is used in case a radio link is established on a DRNC (over Iur) while there is no other radio link established yet on this DRNC for this context (in contrast to intra DRNC handover where RNSAP RL Addition is used, see section 4.14.2). The handover over Iur is only done for DCH. If the call is HSxPA then it will be reconfigured to DCH /DCH before the handover.]
4.15.3 ALGORITHM
HO DECISION PROCESS
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 82/213
UMTS Radio Mobility
CHOICE OF TARGET CELL


In case the inter-frequency handover is not successful (e.g. the mobile fails to synchronise on the target cell) here is no second try or other try to a second best eligible cell. [USA Market - However if the target cell is on a DRNC (i.e. handover from SRNC to DRNC or handover from DRNC to DRNC) a relocation procedure (refer to section 4.12) will be initiated towards the same target cell if enabled according to section 4.12.5.]
4.15.5 PARAMETERS [USA MARKET]

Name isInterFreqHandoverOverIurAllowed [USA Market] Object/Class Neighbouring RNC Definition Indicates if inter-frequency HHO over Iur is allowed

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


The counters listed in section 4.14.8 do apply for the inter RNC scenarios as well. In context of inter RNC handover the counters on per FDDCell basis will be pegged if the handover is performed from the SRNC to a DRNC the counters on per neighboring RNC basis will be pegged if the handover is performed from this neighboring RNC in DRNC role to another DRNC or to the SRNC
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 83/213
UMTS Radio Mobility
4.16. HSDPA AND HSUPA MOBILITY

This section provides a high level view of the interactions between HSDPA or HSUPA and mobility. Full details are available in [R4] UMT/SYS/DD/013319 HSDPA System Specification and [R6] UMT/SYS/DD/018827 E-DCH System Specification. In the following sections, HSDPA call stand for a call where there is at least one radio-bearer mapped on HS-DSCH in DL but no E-DCH in UL. HSUPA call stands for a call where there is at least one radiobearer mapped on E-DCH in UL (so necessarily mapped on HS-DSCH in DL).
4.16.1 DESCRIPTION
DEPLOYMENT SCENARIOS
Two deployment scenarios are foreseen for the introduction of HSDPA/HSUPA on existing networks: HSPDA/HSUPA on a dedicated layer or on an existing layer. Note: to deploy HSUPA in a cell, it is necessary that HSDPA is also configured in this cell. This is because any radio-bearer mapped on E-DCH in uplink will necessary be mapped on HS-DSCH in downlink. However, HSDPA may be deployed in a cell without deploying HSUPA.
HSPDA ON DEDICATED LAYER

The preferred scenario is to deploy a new layer dedicated to HSDPA and/or HSUPA on a new frequency. This layer may be deployed either widely or restricted to some hot-spots and is able to manage both R99 and HSDPA/HSUPA UEs.
Layer with HSDPA configured
Layer without HSDPA
It is even possible to have a three-layer deployment scenario: o one reserved for R99 o one with HSDPA, used for HSDPA but with or without HSUPA o one with HSDPA and HSUPA and used for HSDPA+HUSPA The advantage of this scenario is that there is no impact on the layer that is already deployed. Traffic segmentation can be ensured by two means: o either at RAB assignment (iMCTA feature), based on the HSDPA/HSUPA capability of the mobile and on traffic class of the RAB, or on other iMCTA trigger o or at RRC connection establishment (Traffic Segmentation feature: see [R4]), based on the release of the mobile (<R5 or >=R5) and possibly on the traffic class indicated in the establishment cause.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 84/213
UMTS Radio Mobility
Mobility between the two layers when the mobile is in an HSDPA and/or HSUPA call is handled as any other R99 call (see [Inter-frequency mobility] paragraph in this section).
HSDPA ON EXISTING LAYER

Even though deploying HSDPA and HSUPA on a separate layer is the preferred option, there is nothing that mandates to do so and HSDPA and HSUPA can be configured on any cell (knowing that HSUPA cannot be activated without HSDPA in the cell, see above). The drawback of this scenario is that HSUPA traffic may impact R99 Uplink traffic by generating high interferences.
If HSDPA (resp. HSUPA) is not deployed everywhere in the layer then an automatic channel type switching between DCH and HS-DSCH (resp. E-DCH) is performed when the UE enters in or leaves an HSDPA (resp. HSUPA) cell (more information are provided in [MOBILITY OF HS-DSCH] paragraph in this section). Full details are available in [R4] and [R6]. .
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 85/213
UMTS Radio Mobility
HSDPA AND HSUPA CALL MOBILITY PROCEDURES

This section is only applicable to HSDPA calls (mobile having at least one HS-DSCH radio-bearer, possibly in parallel with other DCH radio bearers) and HSUPA calls (at least on E-DCH radio-bearer). Mobility of R99 calls even in an HSDPA or HSUPA cell is handled as described in the other sections. Note: in following paragraphs, PS RABs means: PS I/B RABs (for HSxPA) PS streaming RABs (for HSDPA only, if streaming on HSDPA feature activated) It does not include Conversational RABs.
INTRA-FREQUENCY MOBILITY
Mobility of associated DCH
Soft and softer handover are handled normally on the associated DCHs and the Active Set evaluation and primary cell selection are managed as described by sections 5.3 and 5.4.
Mobility of HS-DSCH
As specified by the 3GPP standards, HS-DSCH(s) is (are) established in only one cell so is never in soft handover. In Alcatel-Lucent implementation, HS-DSCH(s) is (are) established on the primary cell (good radio conditions and not changing too often). Each time the primary cell changes, the HS-DSCH RL is deleted on the former primary and re-established under the new primary, using a synchronous reconfiguration. If the new primary cell does not support HSDPA then the RB is reconfigured to DCH. Moreover anytime an HSDPA-capable mobile (currently operating in DCH mode) enters an HSDPA primary cell it is reconfigured to HSDPA (for radio bearers that can be served on HSDPA).
Mobility of E-DCH
As specified by the 3GPP standards, there is only one serving E-DCH radio-link and it is established in the same cell that the HS-DSCH radio-link. The mobility of the E-DCH serving link is based on the same principals than the HS-DSCH one. In case of primary cell change, the E-DCH serving link and the HS-DSCH link are moved at the same time (one procedure). If the new primary cell does not support HSUPA then the RB is reconfigured to DCH in UL (it is maintained on HS-DSCH in DL if the cell supports HSDPA). On the opposite, it is reconfigured to E-DCH if the mobile comes back to HSUPA coverage. From UA06.0 release, macro-diversity of E-DCH (having non-serving E-DCH radio-links) is supported by Alcatel-Lucent (refer to 5.3.7).
Mobility over Iur

HS-DSCH is managed over Iur. [Global Market: E-DCH is managed over Iur since UA06 (refer to [R6])]. If E-DCH support over Iur is disabled on SRNC: When the mobile moves so that the primary cell moves under the control of a drift RNC, the E-DCH radio-bearers is reconfigured to DCH in UL. When the mobile comes back under the serving RNC and the primary cell supports HSUPA, the radio bearer is reconfigured to E-DCH in UL otherwise it remains in DCH. [Global Market: If E-DCH support over Iur is enabled on SRNC then no restrictions apply to mobility over Iur.]
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 86/213
UMTS Radio Mobility

If E-DCH support over Iur is disabled on DRNC: In case an Alcatel-Lucent RNC receives a RNSAP RL Setup or Addition or Reconfiguration with an E-DCH radio-bearer from the Iur then the procedure is refused. [Global Market: If E-DCH support over Iur is enabled on DRNC then no restrictions apply to the incoming E-DCH mobility.] [Global Market - A SRNS relocation (UE not involved) may be triggered for an HSxPA call on the Iur as for a R99 call.] When the Serving RNC triggers a relocation (UE involved), the RNC policy is the following: If the HSDPA capability of the UE is given in the RRC transparent container then the RNC will try to map directly PS RABs onto HS-DSCH. Otherwise a DCH resource is chosen. In case of HSDSCH CAC failure, the RNC will perform a DCH fallback as for a RAB assignment (refer to [R4]). If the CAC also fails for the fallback, then the relocation is refused. If the E-DCH capability of the UE is given in the RRC transparent container then the RNC will try to map directly PS RABs onto E-DCH/HS-DSCH. In case of CAC failure on E-DCH or HSDSCH, the RNC will perform a DCH fallback as for a RAB assignment (see [R6]). If the CAC also fails for the fallback, then the relocation is refused. Whatever the container content, the CRNC performs a UE capability enquiry procedure and may reconfigure the PS radio-bearers to HS-DSCH (resp. E-DCH) if not already done.
COMPRESSED MODE
Compressed Mode will be activated in Uplink and Downlink to perform inter-frequency and inter-RAT measurements if needed by the UE. For an HSDPA call, the Mac-hs scheduler will not schedule a UE if a gap falls into the timeslot because the UE would not be able to receive and decode the data. It will also not be scheduled if the answer (Ack/Nack) falls during a gap for the same reasons. For an HSUPA call, the Mac-e scheduler will also take into account compressed mode gaps.
INTER-FREQUENCY MOBILITY
Inter-frequency handover is supported for HSDPA calls and HSUPA calls as for any R99 call. And this may trigger either an intra-RNC handover (with or without Iur) or an inter-RNC handover (over Iur [USA Market] or with relocation procedure). The handover protocol to be performed and possible HSxPA to DCH and DCH to HSxPA reconfigurations depend on the allocation of the target cell. In case of the target cell being controlled by the SRNC, i.e. intra-RNC handover within the SRNC or inter RNC handover towards the SRNC, the PS RB will be kept (or established) on HS-DSCH (resp. E-DCH) if the target cell supports HSDPA (resp. E-DCH). If it is not the case, there are reconfigured (or kept) to DCH in downlink (resp. uplink) In case of the target cell being controlled by a DRNC, i.e. intra-RNC handover within a DRNC or inter-RNC handover towards a DRNC the inter-frequency handover may be performed over Iur [USA Market] or with relocation procedure depending on either or both features being enabled as depicted in figure below. [USA Market - Inter-frequency handover over Iur will be done with preference if enabled towards the DRNC to control the target cell. If performed over Iur then only DCH to DCH handover is supported and HSxPA calls need to be reconfigured to DCH before the handover. Reconfiguration back to HSxPA will be done on the new frequency after successful handover or on the old frequency after unsuccessful handover as described for intra frequency mobility above.]
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 87/213
UMTS Radio Mobility
IFHHO
HSxPA / DCH Handover
Yes SRNC
Target cell on SRNC ?
No DRNC Yes Enabled over Iur ? No
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
IFHHO Procedure (HSxPA or DCH)
Yes DCH
successful ?
No HSxPA
successful ? Yes
No old freq. IFHHO with SRNS Relocation (HSxPA or DCH) Yes Target cell on DRNC and Reloc.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 [USA Market], this triggers a relocation. If the target cell supports HSDPA (resp. HSUPA) and the source RNC has indicated that the UE supports HSDPA in the Rel5 extensions (resp. HSUPA in Rel6 extensions) of the UE capabilities put in the container then the PS I/B radio-bearers are mapped directly on HS-DSCH in downlink (resp. E-DCH in uplink). If no information about the HSDPA (resp. HSUPA) capabilities of the mobile has been provided by the source RNC then the PS radio-bearers are first mapped on DCH in downlink (resp. DCH in uplink). If the HSDPA or HSUPA capability is lacking then a UE capability enquiry is triggered. If it happens that the UE is HSDPA (resp. HSUPA) capable then the PB radio-bearers are reconfigured to HS-DSCH in downlink if the primary cell is HSDPA (resp. E-DCH in uplink if the primary cell is HSUPA).
INTER-SYSTEM MOBILITY
3G to 2G handover
3G to 2G handover is supported for HSDPA/HSUPA calls. The handover is triggered on the same conditions as for non-HSDPA calls (see section 4.20).
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 88/213
UMTS Radio Mobility 2G to 3G handover

2G to 3G handover is supported. In case of a pure PS call, this is seen as a new Mobile Originated PS call from the target RNC (No incoming relocation as the mobile was in GSM/GPRS). The same rules as the initial admission apply, leading possibly to the allocation of HS-DSCH (resp. E-DCH) to the incoming UE.
See [R4]. See [R6].
4.16.3 ALGORITHM
See [R4]. See [R6].
4.16.4 PARAMETERS
See [R4]. See [R6]. Mobility parameters can be tuned by mobility service type.

See [R4]. See [R6].

See [R4]. See [R6].
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 89/213
UMTS Radio Mobility
4.17. SRNS RELOCATION UE NOT INVOLVED [Global Market] 4.17.1 DESCRIPTION

See [R8].
See [R8].
4.17.3 ALGORITHM
See [R8].
4.17.4 PARAMETERS
See [R8].

See [R8].

See [R8].
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 90/213
UMTS Radio Mobility
4.18. 3G2G REDIRECTION AT RRC ESTABLISHMENT FOR SPEECH CALLS 4.18.1 DESCRIPTION
The Redirection during the Rab Assignment processing is covered by the iMCTA function (refer also to 4.20). There are 2 general points in the speech call setup request where the call could fail as a result of UTRAN related resource contention: o RACH Access: The RACH channel has a fixed (shared) bandwidth, and contention will occur if the number of UEs attempting to access the 3G network exceeds a given threshold. Under extreme conditions the amount of UL interference generated by the UEs may significantly reduce the number of UEs which are able to access the UTRAN. Users may experience delays in accessing the network due to collisions on the RACH channel. The UE will re-attempt the call setup (multiple times with increasing power each time), but if the RACH access failure persists, the call will fail. Call failures associated with RACH access are outside of the scope of this feature capability. o SRB Assignment: The SRB is established as a result of the first Access Stratum (AS) message being received by the RNC, and is used to allow the UE and CN to exchange subsequent Non Access Stratum (NAS) messages to allow the call to progress. RRC Redirection is triggered by failures at this point in the call progression.
The redirection applies to calls with RRC Establishment cause equal to MO Conversational or Emergency. o The RNC is unaware of the UE capabilities at RRC Connection Request time. Therefore, the RNC will attempt an RRC Redirection irrespective of whether the UE supports the Redirection IE in the RRC reject message, or whether the UE supports GSM. The resultant behaviour is not defined in the standards; however, the end result is that the ability to redirect the call to 2G may not function in these cases. o RRC Redirection does not apply to any mobile terminated call scenario. This is due to the fact that the anchor 3G-MSC has already been established prior to the RRC Connection Request, and is not able to be modified. The call would fail at the CN if a RRC Redirection is attempted. Therefore, RRC Redirection is not triggered for this scenario. o RRC Redirection will not be triggered by the RNC if the UE already has an established RRC connection. This could be the case in the following scenarios: o A PS call is established prior to invocation of the speech call attempt, and is in either the active state or AO Step 1 state. o The UE did not release the RRC connection after the initial Location Update. This could possibly be the case where the call is invoked very early after the UE is powered up. The UE may choose to set the follow-on request indicator during the Location Update Request, if it has a subsequent request pending. There may be other cases where the UE will request the network to keep the RRC Connection established. o RRC will redirect all MO Conversational calls to 2G upon admission failure (irrespective of service type and domain). This includes: o Non-speech calls such as Video telephony, which will arrive, and fail, on the 2G network. However, these calls have already failed to establish on the 3G network. GSM may either simply fail the call or attempt to redirect the Video telephony back to 3G. o Conversational calls on the PS domain. This is not currently the case, but they may be present in the future. This is merely a consequence of the fact that the RRC establishment cause is not able to uniquely identify a CS speech at this early stage of the call progression. If the neighbouring 2G cells (measurement based or blind) are not provisioned at the OMC-R, RRC Redirection will not be triggered in the RNC, even if RRC Redirection is enabled for that cell. However,
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 91/213
UMTS Radio Mobility

having RRC Redirection enabled for a cell which has no 2G neighbouring cells provisioned is considered a configuration error.
4.18.3 ALGORITHM
The flow for RRC Redirection is shown in Figure 52.
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.
2
If admission fails, and the UTRAN is enabled to redirect speech calls to 2G, a RRC Connection Reject is sent to the UE with redirection info included. RRC/ FACH (RRC Connection Reject (Wait Time, Redirection info: GSM))
Figure 52: RRC Speech Redirection

The key steps are as follows:
Step 1: The UE requests the initial signalling as a normal conversational call setup request. While in this example the setup relates to a speech call setup, the same RRC cause value would be used for a Video Telephony call setup request. There is also a separate cause value for an emergency call request, which could also trigger RRC Redirection. This step is preceded by the location registration (not shown here). Step 2: The RNC will execute normal (i.e. existing) RRC Connection Admission mechanism, which consist of the following functions: Cell CAC: The UL interference (conveyed in the RSSI) is checked to ensure it does not exceed a provisioned UL interference level threshold; RNC Overload: The RRC connection request may be denied based on the current RNC Overload level CAC; Maximum UE Contexts: The RNC checks that the maximum number of concurrent UE contexts will not be exceeded. SRB CAC: The RNC will check that the resources required to support the SRB are available. The required resources are dependant on whether the setup is via Cell_FACH or Cell_DCH, and is as follows: o Cell_DCH: Radio Resources (OVSF codes, DL Power) NodeB CEM AAL2 CAC: In this case there are several existing possible exhaust scenarios, such as Iub bandwidth exhaust (or Iur in the case of a DRNC scenario), CID exhaust, PID failure, and PathGroup failure. However, the most likely failure scenario is Iub bandwidth exhaust, due to the throughput constraint of this physical connection. This is a calculated capacity, based on the sum total of all RBs currently assigned to that resource (partitioned into DS and NDS traffic, as of UA04.1). Internal RNC U-Plane resources (e.g. PSFP) o Cell_FACH: Number of contexts on the FACH channel Internal RNC U-Plane resources (e.g. PSFP)
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 92/213
UMTS Radio Mobility

If failure occurs on any one of the above RRC admission controls, the RNC will execute the RRC Redirection Enabling Criteria. The RRC Connection Reject message will contain the Redirection info IE with Inter-RAT info set to GSM. The mobile station performs inter-system cell reselection and re-originates the speech call on the 2G network. The UE cell selection is not a blind HO, since the UE performs target GSM cell selection. In the case where the 2G cell selection fails, the UE will re-attempt a call in 3G, and this up to N300 times. However, the UE is required to wait (at least) a predetermined time before the subsequent attempt on the 3G network. This wait time is sent by the RNC to the UE in the Wait Time IE in the RRC Connection Reject message. The Wait Time parameter will be set to the value associated with one of the following parameters: o timeReject. If the admission failure which causes the redirection is RNC overload; o a static RNC value if the admission failure which causes the redirection is not overload; o waitTime3Gto2GRedirectFailure. In the case of a 3G-2G Emergency
4.18.4 PARAMETERS
Name is3Gto2gConversationalCallRedirectOnRrcEstabFailAllowed Object/Class
blindHoGsmNeighbourTargetCgi timeReject
FDDCell Class3 RadioAccessService Class3
WaitTime3GTo2GRedirectFailure
FDDCell Class 3
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 Wait time used when the redirection concerns an emergency call

Support of admission control and RRC Redirection procedures.

None.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 93/213
UMTS Radio Mobility
4.19. EMERGENCY AND PRIORITY CALLS

For emergency calls in some countries it is required to determine the location of the UE at call establishment. Current UMTS networks and/or UEs may not allow for a determination of the UE location with sufficient accuracy. In order to take advantage of existing GSM location position solution that satisfies the FCC E911 Phase II requirements, emergency calls can be redirected on initial 3G call set-up [USA Market - or handed over after 3G call set-up] to the 2G GSM network.
RRC Redirection On receipt of RRC Connection Request message from the mobile station with cause emergency, if the feature is activated and a 2G neighbouring cell is provisioned on the current cell, then the UTRAN responds with an RRC Connection Reject message containing the Redirection info IE with Inter RAT info set to GSM.
The mobile station performs inter-system cell reselection and re-originates the emergency call on the 2G network. Existing GSM emergency call procedures and positioning technology are then used to provide location information. Activation of emergency call redirect is configurable on a per cell/sector basis. Refer to 4.18 for redirection procedure. Refer to [R1] and [R13] for more details on specific emergency redirection.
[USA Market - Immediate Inter-RAT Handover Radio access bearer resources are assigned in UMTS to allow for fast call establishment. Depending on parameter immediateHOofEmergencyCalls after successful call establishment the emergency call is handed over to GSM as soon as possible taking into account the cell configuration and UE capabilities. The UE performs GSM measurements and if a suitable GSM target cell is found within time interSystemHOe911Timer then the handover is initiated. Location reporting requests from the MSC are queued during this time and discarded in case of successful handover. The core network will then repeat the location reporting request to the GSM network. In case no suitable GSM target cell is found or in case of handover failure the emergency call is continued in UMTS and the location reporting request is processed.]
[USA Market - Special handling may apply also to priority calls. An example is the Wireless Priority Service (WPS) in the US, which defines redirection to the GSM system of WPS calls which originate from a UMTS subscriber, or NS/EP calls which terminate to a UMTS subscriber, if radio resource congestion occurs on the UTRAN. On RAB Assignment the MSC indicates that the call is a priority call. If UTRAN is congested, then the UTRAN initiates directed retry to GSM (see section 4.20 for a description of the CAC based handover algorithm). The directed retry for WPS calls can be enabled on RNC basis.] [USA Market - In case of inter-RAT handover attempts for emergency or priority calls the RNC does not retry handover to the next best cell in case of relocation preparation failure see section 4.10.4.]
4.19.1 PARAMETERS
Name immediateHOofEmergencyC alls [USA Market] Object/Class FDDCell / NeighbouringRNC Class 3 Definition Indicates whether emergency calls should be handed over to GSM using immediate InterSystem Handover after RAB establishment or kept in UMTS. Following options are available: - disabled - inter system handover for all emergency calls - inter system handover for emergency calls of non-GPS UEs The RNC level parameter RadioAccessService::isImmediateHOofEmerge ncyCallsAllowed must be enabled for
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 94/213
UMTS Radio Mobility

immediate inter-system handover of emergency calls. The parameter identifies the 'Priority Level' of Emergency Call bearer and is used to recognise the Emergency Call on receiving RANAP Allocation/Retention Priority communicated by CN to RNC over Iu interface. If a call is an emergency call and an immediate handover to GSM should be performed, then the RNC tries the handover for the time interSystemHOe911Time. On expiry of this timer the attempt to revert the emergency call to GSM is aborted. An ongoing handover attempt is not aborted. The call will be handled like a normal call, i.e. the call will be kept in UMTS but may be handed over to GSM at a later time e.g. due to coverage reasons. This parameter enables/disables the 'Immediate Handover of Emergency Calls to GSM' on a per RNC basis. On cell basis further configuration options are available. If enabled Wireless Priority Service (WPS) calls are directed to GSM if the UMTS cell is in congestion. Length of time the source RNC will await a response from the CN after sending a RELOCATION REQUIRED message to the CN. If the timer expires the RNC will abort the Relocation Preparation procedure by initiating the Relocation Cancel procedure. This specific timer for US priority call service Wireless Priority Service (WPS) has higher values than normal to regard for queuing in the target GSM system of the WPS calls. When a directed retry handover of a WPS call is attempted, the call may queue for an idle trunk and/or a radio for up to 180 seconds.
emergencyCallPriorityLevel [USA Market]
RadioAccessService Class 3
interSystemHOe911Timer [USA Market]
isImmediateHOofEmergency CallsAllowed [USA Market] isWpsDirectedRetryAllowed [USA Market] wpsTRelocPrep [USA Market]
Imcta Class 3 Imcta Class 3

The following counters are available for "Immediate Handover of Emergency calls":
RAB.AttEstabCSV.EC This PM counts the number of RAB Assignment Requests for Emergency Calls. This PM is only applicable for Emergency Calls. RAB.SuccEstabCSV.EC This PM counts the number of Successful RAB Establishments for Emergency Calls. This PM is only applicable for Emergency Calls. VS.IRATHO.ECIHO.AttHO This PM counts the number of Emergency calls for that an Immediate Inter-System Handover is attempted. Only applicable for the context of "Emergency Call Immediate Inter-System Handover". VS.IRATHO.ECIHO.AttRelocPrep The number of attempted relocation preparations for Emergency Call Immediate Inter-System Handover (ECIHO). Only applicable for the context of "Emergency Call Immediate Inter-System Handover".
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 95/213
UMTS Radio Mobility

VS.IRATHO.ECIHO.AttRRCHO The number of attempted handovers for Emergency Call Immediate Inter-System Handover (ECIHO). Only applicable for the context of "Emergency Call Immediate Inter-System Handover". VS.IRATHO.ECIHO.SuccHO The number of successful Emergency Call Immediate Inter-System Handovers (ECIHO). Only applicable for the context of "Emergency Call Immediate Inter-System Handover". VS.IRATHO.ECIHO.CancelHO The number of Emergency calls for that an Immediate Inter-System Handover is cancelled by normal call release after the RAB has been successfully established and before the handover is initiated by a relocation preparation procedure. Only applicable for the context of "Emergency Call Immediate Inter-System Handover". VS.IRATHO.ECIHO.CancelRelocPrep The number of Emergency calls for that an Immediate Inter-System Handover is cancelled by normal call release after the RAB has been successfully established and before the handover is initiated by a relocation preparation procedure. Only applicable for the context of "Emergency Call Immediate Inter-System Handover".
The following counters are available for "Wireless Priority Service":
RAB.AttEstabCSV.WPS RAB Assignment Requests for Wireless Priority Service (WPS) calls. Number of RAB Assignment Requests for Wireless Priority Service (WPS) calls. This measurement is pegged only if WPS handling is enabled in the RNC. Applicable in the context of WPS calls, only. VS.3g2gOutHoFailure Number of failed outgoing CS IRAT Handovers from 3G to 2G VS.IRATHO.WPS.AttDirectedRetry Attempted CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls. Number of attempted CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls. Applicable in the context of Directed Retry for WPS calls, only. VS.IRATHO.AttRelocPrepOutCS.WPS Attempted CS IRAT relocation preparations of CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls. Applicable in the context of Directed Retry for WPS calls, only. VS.IRATHO.WPS.AttHO Attempted CS IRAT handovers of CAC failure initiated Directed Retries of Wireless Priority Service (WPS) calls. Description: Applicable in the context of Directed Retry for WPS calls, only. VS.IRATHO.WPS.SuccDirectedRetry Successful CAC failure initiated CS IRAT Directed Retries of Wireless Priority Service (WPS) calls. Applicable in the context of Directed Retry for WPS calls, only. VS.IRATHO.WPS.CancelHO Cancelled WPS CS IRAT Directed Retry attempts. The number of WPS calls for that the Directed Retry is cancelled by normal call release after the RAB Assignment was received and before the Directed Retry is initiated by a relocation preparation procedure. Applicable for the context of WPS call Directed Retry, only. VS.IRATHO.WPS.CancelRelocPrep Cancelled WPS CS IRAT Directed Retry Relocation Preparations. The number of WPS calls for that the Directed Retry is cancelled by normal call release during ongoing relocation preparation procedure. Applicable for the context of WPS call Directed Retry, only.
The counters are of cumulative type. They are defined as two sets, one set on per FDDCell basis (the Primary RL of the UE is on this FDDCell) and one set on per neighboring RNC basis (the Primary RL of the UE is on this Neighboring RNC).
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 96/213
UMTS Radio Mobility
4.20. INTELLIGENT MULTI CARRIER TRAFFIC ALLOCATION (IMCTA)

To increase the network capacity, operators may deploy multi layer configurations with several layers structures: Multi layers with equal coverage, Hot spots, micro cells Hierarchical cells structure. There is a need to distribute the traffic between the different layers including 2G (GSM) layers. The traffic distribution strategy may be based on load balancing, Service partitioning, UE speed, Carrier redirection preferences and mobility triggers. The introduction of HSDPA/HSUPA will be also progressive with hot spots and there is a need to redirect HSDPA/HSUPA capable mobile (R5, R6) towards HSDPA/HSUPA cells. The iMCTA function covers this networks evolution. It includes the Alarm Handover. The iMCTA function is managed by the RNC.
2G
R99
R5
FDD2 HSDPA/HSUPA
R5
FDD1 non HSXPA
Figure 53: Service Redirection application

R5 FDD2 HSDPA/HSUPA
R5
R5
R5 FDD1 HSDPA/HSUPA
Figure 54: Load balancing application
4.20.1 DESCRIPTION
IMCTA function allocates traffic across available carriers. For a given call, the carrier is selected by the RNC according to the Operator strategy through iMCTA configuration parameters (including Priority
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 97/213
UMTS Radio Mobility

tables) which allows to take into account the Handover reason, the service type, the mobile type (i.e. HSDPA, HSUPA capable or not), the redirection triggers and the cells load.
iMCTA triggers
The main reasons to invoke the iMCTA function are: Alarm condition is hit; A CAC reason: a CAC failure occurs during the processing of a Rab Assignment sent by the CN. A fallback to another Carrier may be done; A user service reason: A successful Rab establishment/modification/release, a Always On upsize or an IU Release Command is done but the mobile may be moved to a better Carrier; A mobility service reason: A successful Intra Freq mobility is done but mobile may be moved to a better Carrier. The User and mobility Service triggers dont apply if the primary cell is managed through Iur. The Alarm and CAC triggers apply even if the primary cell is managed through Iur.
iMCTA trigger : Alarm HO reason The Alarm criterion for Inter Frequency and the Inter Rat Handover is described in section 5.9.
iMCTA trigger : User Service CAC reason A CAC failure triggers iMCTA function if the failure occurs during the processing of a Rab Assignment message coming from the CN. The purpose is to find another Carrier (which may have a different PLMN) on which a target cell is eligible to support the call (established in signalling or traffic). The list of CAC failure causes which may induce iMCTA triggering is: From Cell: no radio resource available From NodeB: Radio Link Reconfiguration Failure From IUB, IUR, IU: Transport Resource allocation failure From RNC Uplane : Resource allocation failure From C-RNC: User Plane Dedicated Bearer allocation failure.
When a CAC failure occurs during a Rab Assignment towards HSxPA, a HSxPA to DCH fallback may be attempted. If the fallback faces up a CAC failure or may not apply, iMCTA may be called. iMCTA doesnt apply to IRM table reject cases.
iMCTA trigger : User Service reason The triggers which invoke the iMCTA function are: Rab Assignment sent by the CN which induces the establishment of a Traffic Rab, a Rab release or a modification of the established Traffic type. The iMCTA is invoked if the final state of the call is: one or several Traffic Rab are established; Incoming Relocation with one or several Traffic Rab; After a mobile performs a successful Always On upsize from Cell_FACH or URA/Cell_PCH to Cell_DCH; Iu Release Command due to a Core network or a RNC (after sending an IU Release Request) decision when applying to a Multi Service call.
The triggers are valid if the originating cell is eligible regarding its load. This trigger belongs to Service triggers. When the purpose of the iMCTA is to redirect the call according to the Service and mobiles capabilities the load condition of the originating cell, i.e. using origin cell load colour threshold different from green, has not to be used if we want no limitation of the redirection application. iMCTA applies in case of Rab Assignment procedure inducing a successful fallback on DCH when no HSDSCH resource is available.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 98/213
UMTS Radio Mobility

iMCTA trigger : Mobility Service reason The triggers which invoke the iMCTA functions are: It concerns HSDPA or HSUPA capable mobiles traffic connected in DCH and/or HS-DSCH and/or E-DCH. The trigger is a primary link cell change with the new primary cell configured with mobilityServiceForHsxpaEnable O&M attribute set to True; It concerns HSDPA and HSUPA non capable mobiles traffic connected in DCH. The trigger is a primary link cell change with the new primary cell configured with mobilityServiceForNonHsxpaEnable O&M attribute set to True.
The triggers are valid if the originating cell is eligible regarding its load level. If service segmentation is activated, when User service or Mobility service trigger is used, the load of the originating cell is not taken into account.
Crossover between iMCTA triggers or with others procedures

When the RNC waits for iMCTA measurements for a given trigger, a second iMCTA trigger, a Primary link modification or a Service modification may occur. The following rules apply: o Priority Rule between iMCTA triggers: Alarm > CAC > User Service > Mobility Service; o Priority Rule between iMCTA triggers and others procedures: o Alarm/CAC triggers > Primary cell change or Service modification; o User or Mobility Service triggers = Primary cell change or Service modification. The following actions occur: o The last event (iMCTA trigger or Primary cell change or Service modification) may induce an update of the neighbour cells; o When the second event has a higher or equal priority than the previous with no target access change, the Measurement period may be re-started after the expiration (i.e. no target cell identified) of the current period. If the target access changes, the measurement period is stopped and re-started with the new neighbouring. In case of CAC failure, following procedures, if applicable, apply in decreasing priority order : Fallback to DCH iMCTA preemption (refer to [R12])
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 99/213
UMTS Radio Mobility
The iMCTA function only applies to calls in Cell DCH, E-DCH and HS-DSCH connected mode. Calls in Cell Fach (signaling or traffic), Cell PCH or URA PCH connected mode are not managed. iMCTA works with up to six UMTS carriers1, plus a 2G layer (whatever the frequencies). The function may be activated according to four modes: Alarm only: Alarm trigger applies Alarm and CAC: Alarm and User CAC Service triggers apply Alarm and Service: Alarm and Service triggers apply All: All iMCTA triggers apply
Management in Cell E-DCH (design implementation)

When a CAC failure occurs during a Rab Assignment towards HSxPA, a HSxPA to DCH fallback may be attempted. If the fallback faces up a CAC failure or may not apply, iMCTA may be called. (see [R6]).
CAC failure and 3G3G Relocation

The 3GPP only allows Directed Retry for RAB CS establishment failure use case towards 2G. Upon CAC failure, the FDD target cell shall be managed by the S-RNC or by the D-RNC through Iur: a 3G3G relocation is not supported.
CAC failure and 3G2G Relocation

The 3GPP only allows Directed Retry for RAB CS establishment failure use case. When a CAC failure occurs during the PS Rab establishment: When no CS call is already established iMCTA is not triggered; When a CS call is already established and a RANAP Rab Assignment failure is returned to the PS Domain iMCTA triggers a 3G2G HHO towards the 2G CS. When a CAC failure occurs during the CS Rab establishment: When a PS call is already established, iMCTA triggers a Directed Retry towards the 2G. This use case is supported in 3GPP Rel 6 (Sept). If the UE doesnt supports this use case, the redirection failed and the mobile stays with the PS established. A 3GPP R2-062614 (release 6 Sept 2006) asks to support a HHO Inter Rat when a PS + CS signalling is established. So we do the best effort policy: HHO is attempted. If the mobile doesnt support this state, the HHO ends by processing the failure case (call kept on the FDD access).
CAC failure and R5 mobiles

During intra RNC inter frequency HHO, if changing the Transport channel from HSxPA to DCH or viceversa is needed, modifying RLC information has to be processed. The Radio Bearer Release (and also Radio Bearer Setup) message provides this capability from Rel6. For a Rel5 UE, this shall be done separately with a Radio Bearer Reconfiguration: this R5 CAC failure use case is not supported by iMCTA in this version.
Iur management
The Service trigger doesnt apply if the primary cell is managed through Iur. The Alarm and CAC triggers apply even if the primary cell is managed through Iur. As per 3GPP [A7] UEs are required to support the own carrier and two additional FDD carriers. Thus, within a region no more than 3 UMTS carriers should be used.
1
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 100/213
UMTS Radio Mobility

There is no Iur inter RNS version impact.
4.20.3 ALGORITHM
MAIN FUNCTIONAL STEPS
If one of the triggers is valid for the primary cell, the function may process the following functional steps to identify a target cell on another Carrier: 1. Checking of the iMCTA feature activation parameters ; 2. Identification of the Service Type and RAB to be set; 3. Selection of the iMCTA Carrier priority table; 4. Selection of the candidate Carriers; 5. Selection of the candidate Cells for UE measurements; 6. Configuration of the Compressed mode and of the UE measurements; 7. Cell selection upon Measurement Report; 8. iMCTA HHO processing or iMCTA exit . If no target cell is found after iMCTA algorithm processing or no measurement received or the HHO failed, the RNC has to wait the next iMCTA trigger iteration for a new call redirection attempt. For an alarm HHO trigger, when no Inter Freq/Inter Rat measurement can be requested to the mobile (compressed mode not allowed for the Service), no eligible target cell is found in the reported measurements, a iMCTA blind HHO may be attempt to the 2G twin cell (if configured).
IMCTA FEATURE ACTIVATION

The iMCTA feature activation is based on: mode O&M attribute value (see 4.20.4); When the trigger is Service: o Originating cell load eligibility (if service segmentation not activated); o mobilityServiceForHsxpaEnable and mobilityServiceForNonHsxpaEnable O&M attribute value.
NEIGHBOUR CARRIERS SELECTION

iMCTA is triggered for Service reason The Service priority table set by O&M (refer to 4.20.4) is read for the service type requested or in progress (i.e. mobility use case). The carriers with a priority higher or equal to the current one are candidate for iMCTA target cells selection. iMCTA is triggered for Alarm or CAC reason All carriers (2G or 3G) with a priority not equal to PNA are candidate for iMCTA target cells selection. If the carriers list is empty, the iMCTA function is cancelled (step 8 is processed).
NEIGHBOUR CELLS SELECTION FOR MEASUREMENT REPORTING

When the candidate carriers are identified, the selection of the neighbour cells (see section 5.5) is sent to the mobile for measurement. The O&M FDD neighbouring provisioning of a cell has to be limited to 2 carriers in order to fulfill the mobile measurements performance requirements defined in [A7] (the 3GPP doesnt describe the UE behaviour in case of more than 2 neighbour carriers). All following actions occur whatever the iMCTA trigger:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 101/213
UMTS Radio Mobility

The neighbouring cells fulfilling the IMSI based HO condition and belonging to layers supported by the mobile (UE capabilities checked) are selected and ordered according to the Carriers priorities for the requested Service type (according to the service priority table); For each neighbour cells type (Inter Freq / Intra Freq / 2G), the measurement capability is checked (i.e. Compressed Mode applicability for the current service and UE capability). Cells which must not be measured are discarded from the neighbour cells list; [Global Market - If the iMCTA neighbouring cells list contains Inter Freq Cells and 2G (GSM) cells, the cells with highest carrier priorities belonging to the same RAT will be kept. For example: list (cell 1 fdd1, cell 2 fdd2, cell 3 GSM, cell 4 fdd3), cell 3 is removed.] If the target cells list is empty, the iMCTA function is cancelled (step 8 is processed) when the triggering is for CAC or Service reasons. In case of Alarm, a iMCTA blind HHO may occur.
COMPRESSED MODE AND MEASUREMENT CONFIGURATION

Inter Frequency and Inter RAT measurements are configured in periodic Mode. Whatever the iMCTA trigger (Alarm, CAC or Service) the compressed mode activation and the measurements activation procedures are the same. Refer to: Section 5.10; Section 5.12;
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, Rab Assignment, Rate modification) is in progress. An iMCTA criteria re-evaluation/evaluation is done (i.e. iMCTA neighbor cells list may be updated) before processing the RRC Measurement Report message: a measured cell is candidate to the iMCTA cell selection criteria if it belongs to the iMCTA neighbor cells list. If a target cell (FDD or 2G) exists after applying the different filtering steps the HHO is processed. Otherwise the RNC waits next measurement reports until the guard timer elapses. The Radio criteria for target cell selection are the same whatever the trigger (Alarm, CAC, Service). Refer to: Section 5.13; Section 5.14. Any Inter freq or Inter RAT measurement due to iMCTA function received after the guard timer elapses is discarded. The following paragraphs describe the target cell selection for each trigger type.
IMCTA TRIGGER IS SERVICE

The following steps are processed to select a cell among the measured FDD neighbour cells: 1. For each Carrier, the best measured cell which fulfills the Radio criteria is selected, i.e. its the cell with the best Ec/No which verifies FDD HHO condition; 2. Then if HSDPA traffic segmentation option (see [Parameters] section) is set to true, according to the mobile capabilities the non HSxPA cells for a HSxPA capable mobile and the HSxPA cells for a non HSxPA UE are removed; 3. Then the FDD cells are filtered according to the following rule : a. A cell belonging to a Carrier with a priority upper than the originating cell Carrier priority shall have a cell load color fulfilling the target cell load color criteria (see [iMCTA cell load criteria] section);
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 102/213
UMTS Radio Mobility

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 load color (except if service segmentation has a higher priority); Then if Service segmentation priority option (see [Parameters] section) is set to true, if the capability of the target cell with respect to HSxPA does not match exactly the capability of the UE, the cell is removed; Then if several FDD cells are eligible, the following steps (with decreasing priority) are processed until retaining one cell: a. Cell(s) belonging to the Carrier with the highest priority is kept; b. Preference is given to the less loaded cell; c. Preference is given to the cell with the best Radio level (Ec/No). b.
4.
5.
The following steps are processed to select a cell among the measured 2G neighbour cells: 1. The cells which fulfill the Radio criteria are selected, i.e. their Rxlev verify 2G HHO condition; 2. Then the neighbour cells not fulfilling the 2G cell color load criteria are filtered (see [iMCTA cell load criteria] section); 3. Then if several 2G cells are eligible, the cell with the highest radio level is selected (Ec/No). [USA Market - If FDD and 2G neighbour cells are eligible then the FDD target is selected.] [USA Market - If 2G is selected as target and the relocation preparation to the selected target cell fails, e.g. due to load conditions in the GSM cell, then the RNC may re-evaluate the measurement report for the next best 2G neighbour cell and - if found any - re-attempt handover to this 2G cell. This re-attempt can be controlled with parameter isGsmIratHoToNextBestCellAllowed.]
IMCTA TRIGGER IS ALARM OR CAC

The following steps are processed to select a cell among the measured FDD neighbour cells: 1. For each Carrier, the best measured cell which fulfils the Radio criteria is selected, i.e. the cell with the best Ec/No which verifies FDD HHO condition; 2. Then if several FDD cells are eligible, the following steps (with decreasing priority) are processed until retaining one cell: a) If UE is HSUPA capable, preference is given to HSUPA cells then HSDPA cells else if UE is HSDPA capable, preference is given to HSDPA cells; b) Preference is given to the less loaded cell; c) Preference is given to the cell with the best radio level (Ec/No). The following steps are processed to select a cell among the measured neighbour 2G cells: 1. The cells fulfilling the Radio criteria are selected, i.e. their Rxlev verify 2G HHO condition; 2. The less loaded cell is preferred; 3. Then if several 2G cells are eligible, the cell with the highest Radio level is selected. [USA Market - If FDD and 2G neighbour cells are eligible then the FDD target is selected.] [USA Market - If 2G is selected as target and the relocation preparation to the selected target cell fails, e.g. due to load conditions in the GSM cell, then the RNC may re-evaluate the measurement report for the next best 2G neighbour cell and - if found any - re-attempt handover to this 2G cell. This re-attempt can be controlled with parameter isGsmIratHoToNextBestCellAllowed.]
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 103/213
UMTS Radio Mobility
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; CAC trigger : After a CAC failure during a Rab Assignment/Release/Modification, the following actions are processed: o If resources were partially allocated for the requested Rab they are released; o If the Target cell is managed by the S-RNC (i.e. Inter Freq Intra RNC HHO): The Inter Freq Hard Handover procedure towards the target cell is processed; A Rab Assignment Response message is returned by the S-RNC to the Core Network; Then waiting procedures may be processed. o If the Target cell is not managed by the S-RNC (i.e. Inter Rat or Inter Freq Inter RNC HHO): A Rab Assignment failure is returned to the CN with the Rab failed and a Directed Retry cause ; A 3G/2G or 3G/3G Hard Handover is processed. For the Hard Handover execution see the section describing the Hard Handover type used. The resource type and the rate to be allocated on a target FDD cell depends on the RNC resource allocation policy (refer to section 4.16).
IMCTA EXIT
The exit may occur if: No target neighbour cell was found before the guard timer elapses (in some use case the timer was re-armed) and no blind HHO 3G/2G may be processed; The mobile is no more in connected mode (cell DCH, E-DCH and HS-DSCH). The transition depends on the iMCTA trigger type. If Inter Frequency/Inter Rat measurements were requested to the mobile, they are released. According to the trigger, the actions are: Service and Alarm trigger: the waiting procedures may be processed; CAC trigger : After CAC failure during a Rab Assignment/ Release/ Modification, the following actions are processed: If resources were partially allocated for the requested Rab they are released; A Rab Assignment Response Failure message is returned by the S-RNC to the CN with the Rab failed; The waiting procedures may be processed.
IMCTA CELL LOAD CRITERIA

The cell load information is needed by the iMCTA function to filter loaded cells or to give a preference to the less loaded cell. The cell load iMCTA color is built by using metrics linked to DCH resources (and HSDPA ones (power and OVSF codes) if fair sharing feature is activated) occupancy at Cell, CEM or Iub levels. Whatever the resource used by the call (DCH, HS-DSCH, E-DCH), the elementary load colors depend only on the RABs established or to establish (CAC failure case). Cell load for the originating cell is not taken into account in case of iMCTA triggered for service reasons when service segmentation has a higher priority than load balancing. The cell load metrics are described in [R7].
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 104/213
UMTS Radio Mobility
ORIGINATING FDD CELL ELIGIBILITY

For each Rab established, a set of cell load elementary colors is read. An originating FDD cell is eligible for iMCTA if one of each relevant cell load colors is higher or equal to the iMCTA originating cell color triggering threshold: At least one DL color iMCTA originating cell color threshold OR At least one UL color iMCTA originating cell color threshold.
TARGET FDD CELL ELIGIBILITY

For each Rab to establish, a set of cell load elementary colors is read. A target FDD cell is eligible for iMCTA if each relevant cell load color is lower or equal to the iMCTA target cell color triggering threshold: All Cell DL color iMCTA target cell color threshold AND All Cell UL color iMCTA target cell color threshold
When a FDD cell belongs to a D-RNC but is not in the S-RNC neighbor cells provisioning, the iMCTA target Cell color threshold has a Red default color.
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.
When a neighbour 2G cell is given by a D-RNC and cannot be found in the S-RNC provisioning, the iMCTA target Cell color threshold has a Red default color. Two colors are supported: green/red. At the cell configuration, the cell iMCTA color is green by default. For cells managed by a D-RNC, the cell iMCTA color is also green by default.
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.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 105/213
UMTS Radio Mobility

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.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 106/213
UMTS Radio Mobility
4.20.4 PARAMETERS
IMCTA OPTIONS
Name serviceHoRanapEnable Object/Class RadioAccessService Class 3
ServiceForTrafficSegm entationPriority Class3 RadioAccessService Class 3 RadioAccessService Class 3
IsServiceSegmentationTopPr iority Is2GCellLoadInformationM anagementAllowed [Global Market] InhibitTimer3g2g
mode
FDDCell Class 3
hsxpaSegmentationEnable
FDDCell Class3
mobilityServiceForHsxpaEn able
FDDCell Class3
mobilityServiceForNonHsxp aEnable
FDDCell Class3
originatingCellColourThres hold
FDDCell Class 3
mode
NeighbouringRNC Class 3
targetCellColourThreshold
FDDCell 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 doesnt occurs. This option doesnt apply in case of iMCTA 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,
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 107/213
UMTS Radio Mobility

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 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.
userServiceSigToTrafficOnly Enable
FddIntelligentMultiCar rierTrafficAllocation Class 3
is3GHandoverPreferred [not supported in UA06]
FDDCell / NeighbouringRNC Class 3
isGsmIratHoToNextBestCell Allowed [USA Market] isChangeGsmIratHoCriterio nAllowed [USA Market]
RadioAccessService Class 3 RadioAccessService Class 3
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 its HSxPA capability and UE capability match (see above).
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:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 108/213
UMTS Radio Mobility

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 P6 (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. [USA Market - 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 P6 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
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 (R5, R6) on a cell not supporting HSDPA/HSUPA
IMCTA PRIORITY TABLES

Name AlarmPriorityTableConfClass Object/Class
CacPriorityTableConfClass
ServicePriorityGeneralTableConfClass
ServicePriorityTableForHsdpaConfClass
ServicePriorityTableForHsupaConfClass
Definition This table gives for 2G and 3G access a priority value per service type. This table is used when an iMCTA Alarm trigger is processed. This table gives for 2G and 3G access 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). This table gives for each Fdd and 2G carriers a priority value per service type. This table is used when an iMCTA service trigger is processed for a HSDPA capable mobile. This table gives for each Fdd and 2G
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 109/213
UMTS Radio Mobility

carriers a priority value per service type. This table is used when an iMCTA service trigger is processed for a HSUPA capable mobile. 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. Pointer towards one instance of the CacPriorityTableConfClass tables. Pointer towards one instance of the ServicePriorityGeneralTableConfClass tables. Pointer towards one instance of the ServicePriorityTableForHsdpaConfClass tables. Pointer towards one instance of the ServicePriorityTableForHsupaConfClass tables. Pointer towards one instance of the AlarmPriorityTableConfClass tables. Pointer towards one instance of the CacPriorityTableConfClass tables. This parameter is a pointer to one of the five ServiceSegmentationPriorityClass instances
ServiceSegmentationPriorityClass
RadioAccessServi ce Class3
FDDCell Class 3 FDDCell Class 3 FDDCell Class 3 FDDCell Class 3 FDDCell Class 3 NeighbouringRNC Class 3 NeighbouringRNC Class 3
alarmPriorityTableConfClassId cacPriorityTableConfClassId servicePriorityGeneralTableConfClassId
servicePriorityTableForHsdpaConfClassI d servicePriorityTableForHsupaConfClassI d alarmPriorityTableConfClassId cacPriorityTableConfClassId serviceSegmentationPriorityTableRef
FDDCell (iMCTA) Class3
iMCTA Priority Table definition : General aspects

When iMCTA is invoked by one of the triggers, the function has first to select the candidate target Carriers taken into account the UE capabilities and the priority of the different carriers for the request service type. The priorities per carrier and per service type are defined via O&M. The operator may give different Carrier priorities according to the iMCTA trigger (Alarm, CAC and Service).
iMCTA Alarm and CAC and Priority Tables definition

There is one table for Alarm and another one for CAC, they have the same format. The tables allow setting the target Radio Access technology preference between 3G and 2G when a HHO has to be processed for Alarm and CAC reasons. The different priority values are: PNA, P1 and P2 with P1>P2. If the priority is set to PNA (Priority Not Applicable), the Radio Access System (3G or 2G) shall not be considered for the request service type. For each Service type, it is possible to have the PNA value for all Access. If two Radio Access System are selected (Priority <>PNA), [Global Market - they must have a different priority. The two conditions contribute to give a preference.] [USA Market - 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)] The table applies to all mobiles types (HSDPA/HSUPA capable or not) with a primary link located on the C-RNC or a D-RNC.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 110/213
UMTS Radio Mobility

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. [Global Market - For each service type the 2G carrier priority (except for PNA value) shall not be equal to one of the FDD carrier priorities. FDD carriers priorities could be the same in order to allow load balancing between FDD layers.] [USA Market - For each service type the 2G carrier priority can be equal or different to the FDD carrier priorities.] For each Service type, it is possible to have the PNA value for all layers (FDD and 2G). The different priority values are: PNA, P1P5 with P1>P2>.P5. If the priority is set to PNA, the carrier shall not be considered for the request service type. The table only applies to a call with a primary link located on the C-RNC. The operator can configure a specific Service table per UE type: iMCTA HSUPA table (optional table). If present, the table has to be used when the mobile release is HSUPA capable; iMCTA HSDPA table (optional table). If present, the table has to be used when the mobile is HSDPA capable. It also my used if the mobile release is HSUPA capable and the iMCTA HSUPA table is not present; iMCTA General table (mandatory table). The table has to be used for non HSDPA/HSUPA capable mobiles. It has also to be used in the following cases : o when the mobile is HSDPA capable and the iMCTA HSDPA is not present; o When the mobile is HSUPA capable and the iMCTA HSDPA and HSUPA table are not present. If the originating cell belongs to a Carrier described in the Service priority table with a priority value equal to PNA for the given service type and mobile type, the RNC has to replace the priority value with the lowest priority value (i.e. P6);
iMCTA Service Type definition

The Service Type is an input to access information (i.e. priority value) in Priority tables. The goal is to establish all requested RAB on a better carrier. Whatever the result of the procedure which triggers the iMCTA, the service type is read by the RNC in its configuration parameters (DlUserService MO) based on the RABs requested by the CN which may be established or not. The list of Service types is: CS Speech CS Conversational (64/64) CS Streaming PS Streaming PS Interactive/Background CS speech + other service (PS, or PS+PS...) PS Conversational none Multiple service Radio Bearers and Multiple PS Radio Bearers are mapped onto a Service Type according to the following static rule which gives the priority between RB. The highest RB will be the input to map the Service type. The rule is: conversational/speech > streaming > I/B Example: CS 64/64 + PS I/B shall be handled as CS 64/64 which is mapped onto CS conversational service. The none value is used to set some User Service (signaling) ineligible to iMCTA.
Name
Object/Class
Definition
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 111/213
UMTS Radio Mobility

serviceType DlUserService Class 3
For each DlUserService Instance, a ImctaServiceTypeId is set which allows to access the iMCTA priority tables. The operator has not to modify the list without Alcatel-Lucent agreement.
IMCTA Service Segmentation Priority Table definition

This table allows the operator to define per service if service segmentation has a higher priority than load balancing. The goal is to redirect the call on a cell with a better matching capability when the HSxPA capability of the originating cell and the UE capability do not match, independently of the load of the primary cell.
IMCTA Service for Traffic Segmentation Priority definition

This ServiceForTrafficSegmentationPriority is an input to access information (activation of service segmentation option per service) in Service Segmentation priority tables. The list of Services is the same as in Service type.
4.20.5 PERFORMANCE MANAGEMENT

Existing mobility counters are modified and new counters are created. The document [R9] gives the description of the counters.
[USA Market - The following counters have been modified or added in UA06.0:
VS.CmActivationSuccess Number of successful Compressed Mode activations Screenings: - GSM - InterFrequency - GSMAndInterFrequency VS.CmActivationFailure Number of failed Compressed Mode activations Screenings: - GSM - InterFrequency - GSMAndInterFrequency
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 112/213
UMTS Radio Mobility
4.21. MOBILITY IN CELL_PCH AND URA_PCH RRC STATES 4.21.1 DESCRIPTION

URA update URA update
URA update
Broadcast of URA identity

The management of the URA_PCH needs the SIB2 broadcasting. This SIB only contains: the number of URA_identities (1..8); the URA (UTRAN Registration Area) identity (ies) of the cell.
Note: if SIB2 is not broadcasted in a cell then a mobile in URA_PCH that has reselected this cell will perform a URA_UPDATE (change of URA), allowing the RNC to move the UE to Cell_PCH RRC state.
URA reselection process

The RNC has to assign one URA identity to the UE when it moves the mobile to URA_PCH. The RNC modifies this URA identity when an RRC Update occurs with the change of URA cause. When the UE reselects a cell that does not belong to this URA (ie: this URA identity is not present in SIB2), the UE performs a URA update procedure with URA update cause change of URA. On reception of the URA update for URA reselection reason, the RNC shall assigned (assuming it knows the UE) a new URA to this UE.
UE
URA UPDATE (u-rnti)
UTRAN
URA UPDATE CONFIRM (u-rnti ; new URA identity)
Figure 55: Assigning a new URA

If multiple URAs are defined in the current cell, the RNC shall select the appropriate one: the one on top of the list.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 113/213
UMTS Radio Mobility

IUR Management
ASSUMPTION: IT IS NOT ALLOWED TO SPREAD A URA OVER TWO RNS. The operator has to take care of it. The same management as for Cell Fach through Iur applies to CELL_PCH and URA_PCH (refer to section 4.5). Note that the release is applicable anytime the RNC receives a message from an unknown u-RNTI. Note: Alcatel-Lucent RNC will not support Paging Request over URA from the Iur and will ignore this message. Alcatel-Lucent RNC will not provide any information on URAs on the Iur (in RL Setup/Addition Response and in Uplink Signalling TransferIndication messages).
IOT Mobile restrictions

It is possible that some UEs do not support URA or CELL PCH. In case the UE does not support the RRC state, the RRC procedure used to reconfigure the UE to this state will fail (eg: The RNC will receive a Radio Bearer Reconfiguration Failure message from the mobile). If for any reason, the reconfiguration fails then the RNC shall release the RRC connection (moves UE to Idle). There is no functional consequence to this because the interest of these states vs idle is only a faster resume time.
Cell Update and URA update management

The update procedures use the following messages: Cell reselection 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, short enough not to change to Idle mode)
The following specifies the Alcatel-Lucent UTRAN behaviour on reception of a cell update or URA update for a mobile in URA_PCH or Cell_PCH RRC state, based on the cause indicated by the UE in the message.
Cell reselection On reception of the Cell update message from a mobile in Cell_PCH state, the RNC increments the counter of number of Cell reselections. If this counter reaches a configurable threshold, the RNC shall send the mobile to URA_PCH (if the operator has activated URA_PCH). Else, the RNC shall resend the mobile to Cell_PCH.
In case the cell is part of new LA/RA, then a LA/RA update is performed on Cell_FACH.
Periodic cell update On reception of the Cell Update message, the RNC updates the UE location and resends the mobile to Cell_PCH. It is used as supervision mechanism: the call is released in case of periodical update lack..
Re-entered service area On reception of the Cell Update message, the RNC updates the UE location and sends the mobile to URA_PCH or Cell_PCH according to what was the previous state of the mobile and has been configured by the operator for the cell.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 114/213
UMTS Radio Mobility

If the u-rnti is not known by the RNC (because the RNC tried to contact the UE without success so released the RRC connection), the RNC shall send an RRC Connection Release message to the UE.
URA reselection On reception of the URA update message, the RNC shall resend the mobile to URA_PCH with a new URA (the one at the head of the list defined for this cell). or If the current cell is not part of any URA, the RNC shall send the mobile to Cell_PCH (given it is allowed on the network) or Idle (if Cell_PCH is not allowed).
The RNC doesnt check if the cell is part of new LA/RA: no LA/RA update procedure is performed on Cell_FACH.
Periodic URA update Nothing to do except resend the mobile to URA_PCH state keeping the same URA. It is used as supervision mechanism: the call is released in case of periodical update lack.
Unknown u-RNTI In case the UE sends a Cell Update or URA update message with an unknown u-RNTI, the RNC shall: If the u-RNTI belongs to another RNS, it shall send an RRC Connection Release message (directed signalling connection re-establishment cause): see [Iur management] in a previous paragraph; If the u-RNTI belongs to this RNS, it shall send an RRC Connection Release to the UE. Multiple URA_update or Cell_Update The RNC may receive several URA_update or Cell_Update in case the UE did not receive the confirmation message from the RNC (eg: it has reselected another cell). In this case, the RNC shall act as for the first one received (but may assign a different URA if the cell reselected is different).
This feature is applicable when the call enters in Cell/URA PCH state.
4.21.3 ALGORITHM
The cell selection/re-selection evaluation process (see [A5]) in Cell_PCH or URA_PCH RRC state for Intra Freq, Inter Frequency or Inter rat mobility management is the same as for CELL-FACH RRC state. Please refer to section 4.5.4.
4.21.4 PARAMETERS
The activation of using CELL/URA PCH RRC state is described in [R3]. The mobility configuration is made through the following parameter:
Name URA identity [1..8] : (0..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 . If the list is not provided, the mobile shall be moved to Cell_PCH (if enabled) or idle (else).
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 115/213
UMTS Radio Mobility

Ability to broadcast the configuration parameter on the radio interface. Management of the Cell/URA update procedures.

No impact.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 116/213
UMTS Radio Mobility
4.22. HCS: CELL RESELECTION CONTROL IN A HIERARCHICAL CELL STRUCTURE [Global Market] 4.22.1 DESCRIPTION
The Hierarchical Cell Structure feature enables the cell reselection control procedure in a Multi Layer network. HCS algorithm is based on the classical principles of the re-selection algorithm of the UE in Idle/connected mode as defined in the sections 4.4 and 4.5 but with additional algorithms handled by the HCS and applicable to the new concept of the UE fast moving also called high mobility. This feature allows the operator to prioritize cell layers for mobiles in idle mode, Cell_Fach, and URA/Cell_PCH connected modes. The cell reselection algorithms could be also applicable to the UE speed so that fast moving UEs can be placed in large cells to avoid excessive cell reselections (i.e. macro cells/ mobility layer). In addition it allows a better radio plan management and handles the UTRAN resources with better efficiency improving the UTRAN capacity (i.e. micro cells/capacity layer), improving higher data rate services in small areas, handling others services as in private systems, and so decrease the total system cost. Also to be considered the Hierarchical Cell Structure provides the architecture of a multi-layered cellular network where subscribers are handed over from the macro to the micro or to the pico cell layer depending on the current network capacity and the needs of the subscriber. It means the cell plan has several levels. For example fast moving terminals could be redirected to macro cell layer (i.e. mobility layer), rather low moving terminals to micro/pico cell layer (i.e. capacity layer).
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 117/213
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. As the traffic user demands on the network should vary in time and in space, local traffic peaks are likely to occur and so required micro cells are needed to complement the macro cells. Now with fast UE, large number of handoff between these cells may occur. Typically High mobility detection is useful in such cases, and shall avoid too much undesirable handoffs which can produce call drops. It shall also offer to reduce negative radio effect when one fast moving UE is connected to a distant macro cell, and enters a micro cell, then the unwanted radiation of the high power transmission UE may generate some interferences at the micro cell NodeB, which is tuned to lower transmission terminals. It may appear in particular radio conditions (UE at the edge of radio cells), to trigger the high mobility detection even if its not a real fast moving UE case.
The HCS applies to the following mobility cases: "3G to 3G cell reselection intra-frequency in Idle/Fach mode" which allows a UMTS mobile camping on a 3G cell to reselect a cell using the same technology and frequency according to a priority level between the serving cell and its neighbouring "3G to 3G cell reselection inter-frequency in Idle/Fach mode", according to a priority level between the serving cell and its neighbouring "3G to 2G cell reselection in Idle/Fach mode" which allows a "GSM capable" UMTS mobile to reselect a GSM cell when being in idle mode in the UMTS coverage according to a priority level between the serving cell and its neighbouring, only UTRAN/FDD and GSM Radio Access Technologies are known and supported
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 118/213
UMTS Radio Mobility
The HCS algorithm is based on the classical principles of the re-selection algorithm of the UE in Idle/connected mode, but for R5 UE some new concepts are introduced based on the priority set to a cell for a given set of cell (Serving cell and neighbouring cells) and the high mobility detection. The new specific parameters for HCS cell re-selection procedure are controlled by the RNC. The broadcasting of these new parameters implies coding/scheduling modification for SIB3/SIB11 broadcasted on the BCCH channel in idle mode, and for SIB4/SIB12 in FACH or PCH mode if enabled.
4.22.3 ALGORITHM
As specified in [A5], the UE algorithm for cell reselection applied to HCS still defines a criteria for UTRAN/FDD or GSM neighbouring cells tracking and measurement a criteria S to assess FDD and GSM cells eligibility a criteria H for HCS using a quality level threshold to prioritise cells for the ranking a criteria R for ranking of eligible cells The cell re-selection algorithm defined for HCS takes into account: Classical re-selection parameters: o Quality measured/value derived from the CPICH Ec/No or CPICH RSCP, o UE measurement for intra/inter frequency, o UE measurement for inter RAT, o Time reselection duration according to the corresponding UE state (URA/Cell PCH or Cell-FACH), o 3GPP defined thresholds level (Qhyst1s , Qoffset1s,n,), o Cell Ranking criteria R, New parameters/concepts for HCS re-selection: o Priority levels for serving and neighbouring cells (0 to 7) as : o HCS_PRIOs : Defines the HCS priority level for serving cell, o HCS_PRIOn : Defines the HCS priority level for neighbouring cells, o HCS re-selection criterion and HCS thresholds as : Qhcs : Quality threshold level for applying hierarchical cell reselection, Hs/ Hn: Quality threshold criterion for applying hierarchical cell reselection, H criterion used for neighbour cells selection for the ranking Additional HCS parameters (including temporary offset) for HCS criterion H and cell-ranking criterion R,
o o o
High mobility detection (UE fast Moving), UE measurement for intra/inter frequency used for high mobility state detection, UE measurement for inter RAT used for high mobility state detection,
From an algorithmic point of view the main differences with the classical reselection procedure are on the measurement rules and on the ranking algorithm.
o o o
HCS cell-reselection procedure is based on UE measurements and the measurements rules, The new concept of high mobility detection procedure could be applied to the HCS measurement rules if configured, in order to detect a high mobility state. When HCS is used SsearchHCS specifies the threshold for Srxlev below which Intra-frequency and inter-frequency measurements of the neighbouring cell are performed.
Note: When HCS is not used the SsearchHCS applies also, in that case it specifies the threshold for Srxlev below which ranking for inter-frequency of the neighbouring cell of the serving cell is performed (see section 4.4 ).
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 119/213
UMTS Radio Mobility
CELL RESELECTION CRITERIA WHEN HCS IS USED

If HCS is used in the serving cell, Cell re-selection criteria apply for intra/inter frequency and inter RAT cells.
Main steps
Step 1: The UE measurement rules described in [A5] apply: the list of measured cells depends on HCS priority level and the UE high-mobility state. The list may be a sub-list of all provisioned neighbour cells sent in the SIB11message. Step 2: The S and H criterion apply on the measured cells to identify cells candidates for the neighbour cells ranking criterion R. The S criterion is described in the section 4.4. The quality threshold level criterion H for HCS, involving a prioritized ranking to the candidate cells, is defined as:
Hs = Qmeas,s - Qhcss Hn = Qmeas,n - Qhcsn TOn * Ln

with:
Q meas,s , Q meas,n QHCS s , QHCS n Ln TOn
Measured cell quality value. The quality of the received signal expressed in CPICH Ec/N0 (dB) Quality threshold levels for applying HCS algorithmic. Constant value Time Offset
If at least one measured neighbor cell verifies H 0 the criterion S applies according to the high mobility state:
If high mobility state is not active, the criterion S apply on measured cells with the highest HCS_PRIO with H 0 (use case: favour transition from mobility layer to capacity layer with the assumption of mapping mobility layer with one lowest priority ); If high mobility state is active, the criterion S apply on measured cells with : o If (HCS_PRIOn < HCS_PRIOs), the highest HCS_PRIOn priority level which verify H 0: the neighbor layers with the closest priority of the serving layer is selected (use case: UE leaves a serving layer coverage towards a layer with a lower and closest priority); o If (HCS_PRIOn HCS_PRIOs), neighbour cells with the lowest HCS_PRIOn priority level which verify H 0: the neighbor layers with the closest or the same priority as the serving layer is selected (use case: UE sees new cell layers with an upper closest or equal priority);
If no cell verifies H 0 the criterion S and R are used as if HCS was not used (see S criterion of section 4.4).
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 120/213
UMTS Radio Mobility

Step 3: The cell ranking with the cell ranking criterion R is applied by the following formula to the cells fulfilling the step 2 conditions:
Rs = Qmeas,s + Qhysts Rn = Qmeas,n - Qoffsets,n - TOn * (1 Ln)
The best ranking cell is the cell with the highest R value. As explained in the section 4.4 the ranking is based on CPICH RSCP quality and a second ranking may occur when quality measurement is Ec/No. The selected cell has to fulfill the Access restriction rules see [A5].
TO n and Ln calculation Extract of [A5].

Time Offset (TO) applies in: Hn formula when Ln =1 (i.e. HCS_PRIOn <> HCS_PRIOs ) Rn formula when Ln =0 (i.e. HCS_PRIOn = HCS_PRIOs) Time Offset parameter applies a temporary offset value which is added to the offset Qoffsets,n in order to increase the offset and so temporary disadvantage a neighbour cell for the Hn and Rn criterion: it allows avoiding ping-pong effect.
Qmeas = quality value of the received signal HCS_PRIOs, HCS_PRIOn, = HCS priority level of the cell, TO n = TEMP_OFFSETn * W(PENALTY_TIMEn Tn) Ln = 0 Ln = 1 Tn = Timer if HCS_PRIOn = HCS_PRIOs if HCS_PRIOn <> HCS_PRIOs
- W(x) = 0 for x < 0 - W(x) = 1 for x >= 0
Hn formula: TO applies when the neighbour cell HCS priority is different from the serving cell HCS priority : the objective is to give a mean to disadvantage some neighbour cells before ranking when they belong to a layer with a priority different than the serving layer priority (use case: ping pong between cells of different priorities). Rn formula: TO applies when the neighbour cell HCS priority is equal to the serving cell HCS priority: the objective is to give a mean to disadvantage some neighbour cells ranking which belong to the same layer or to layers with equal priority: the ranking value will be decreased during TO. (use case: ping pong between cells of same priorities). TEMP_OFFSET n applies an offset to the R and H criteria for the duration of PENALTY_TIMEn after a timer Tn has started for that neighbouring cell.
T n timer definition Extract of [A5].

There is one Tn timer per neighbour measured cell. It bounds the temporary offset use. The condition for arming this timer depends on HCS_PRIOn and HCS_PRIOs parameter values:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 121/213
UMTS Radio Mobility

If (HCS_PRIOn <> HCS_PRIOs) the condition is based on the neighbour cell quality measurement without regarding the serving cell quality : If (HCS_PRIOn == HCS_PRIOs) the condition is based on the difference between quality measurements of the serving and the neighbour cell: the purpose is to keep the mobile on the actual layer except if the quality is well better on the neighbour layer. The Tn timer is stopped when the condition is the condition is no longer fulfilled. The change of the serving cell doesnt imply a timer stopping. - If (HCS_PRIOn <> HCS_PRIOs) && (Qmeas,n >= Qhcsn) Start Tn, - If (HCS_PRIOn == HCS_PRIOs) && (Qmeas,n > Qmeas,s + Qoffsets,n) Start Tn, Else Stop timer Tn,
Fdd Cell: If quality measurement used is CPICH Ec/No, Qoffsets,n = Qoffset2s,n . If quality measurement used is CPICH RSCP, Qoffsets,n = Qoffset1s,n. 2G Cell: Qoffsets,n = Qoffset1s,n.
High mobility detection (if HCS is used)

Extract of [A5].
If the number of cell reselections during period TCRmax exceeds NCR, high-mobility has been detected. When the number of cell reselection during time period TCrmaxHyst no longer exceeds NCR, UE shall: Continue these measurement during TCrmaxHyst; If the criteria for entering high mobility is not detected during time period TCrmaxHyst: Exit highmobility. The high mobility state doesnt mean the mobile speed is high but the number of reselection is high. The high mobility detection may be used if HCS is not used (see section 4.4)
INTER RNC CASE

In this version full HCS is applicable for intra RNC case only.
4.22.4 PARAMETERS
The isHscUsed parameter allows the activation/deactivation of the HCS procedure. The tCrMax allows the activation/deactivation of the High mobility detection.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 122/213
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..20 by step of 2) In [dB]. This specifies the RAT specific threshold in the serving cell used in the inter-RAT measurement rules. Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the limit for Srxlev in the serving cell below which the UE shall initiate measurements of all neighbouring cells of the serving cell. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks interfrequency neighbouring cells of the serving cell. Integer (-105..91 by step of 2). This threshold is used in the measurement rules for cell re-selection. When HCS is used, it specifies the RAT specific threshold in the serving cell used in the inter-RAT measurement rules. When HCS is not used, it specifies the limit for Srxlev in the serving cell below which the UE ranks inter-RAT neighbouring cells of the serving cell. Real (0..1 by step of 0.1). This specifies the scaling (multiplication) factor to be used by the UE in idle mode or RRC connected mode states for the parameters Treselections or Treselections,PCH or Treselections,FACH in case high-mobility state has been detected. Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-frequency case. Real (1..4.75 by step of 0.25). This specifies the scaling (multiplication) factor to be used by the UE for scaling the parameters Treselections or Treselections,PCH or Treselections,FACH for the inter-RAT case. Enumerated (not used, 30, 60, 120, 180, 240). This specifies the duration for evaluating allowed amount of cell reselection(s). This parameter is mapped to non-TCRmax or TCRmax IE for SIB3/4 filling depending of HCS use or not. Integer (1..16). This specifies the maximum number of cell reselections. This parameter is mapped to non-NCR or NCR IE for SIB3 filling depending of HCS use or not. Enumerated (not used, 10, 20, 30, 40, 50, 60, 70). This specifies the additional time period before the UE can exit high-mobility. This parameter is mapped to non-TCrmaxHyst or TCrmaxHyst IE for SIB3/4 filling depending of HCS use or not. Integer (0..7). This specifies the HCS priority level (0-7) for serving cell . HCS priority level 0 means lowest priority and HCS priority level 7 means highest priority. Integer( 0..99). This specifies the quality threshold levels for applying prioritised hierarchical cell re-selection Integer (-32..20 by step of 2). This threshold is used in the measurement rules for cell re-selection when HCS is used. It specifies the RAT specific threshold (in dB) in the serving UTRA cell above which the UE may choose to not perform any inter-RAT measurements in RAT "m".
3 4
sSearchHcs
3 4
sHcsRatGsm
3 4
CellSelectionInfo CellSelectionInfoCo nnectedMode
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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 123/213
UMTS Radio Mobility

OAM parameter hcsPrio SIB 11 12 qHcs 11 12 11 12 temporaryOffset1 11 12 Object UmtsNeighbouringRelation FddNeighCellSelectionInfoCon nectedMode UmtsNeighbouringRelation FddNeighCellSelectionInfoCon nectedMode UmtsNeighbouringRelation FddNeighCellSelectionInfoCon nectedMode UmtsNeighbouringRelation FddNeighCellSelectionInfoCon nectedMode description/comment Integer (0..7). ). This specifies the HCS priority level (0-7) for the neighbouring cells. HCS priority level 0 means lowest priority and HCS priority level 7 means highest priority. Integer( 0..99). This specifies the quality threshold levels for applying prioritised hierarchical cell re-selection. Integer(0, 10, 20, 30, 40, 50, 60) in sec. This specifies the time duration for which the TEMPORARY_OFFSETn is applied for a neighbouring cell. Integer(3, 6, 9, 12, 15, 18, 21, inf) in dB. This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY_TIMEn. It is used in case the quality measure for cell selection and re-selection is set to CPICH RSCP. Integer(2, 3, 4, 6, 8, 10, 12, inf) in dB. This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY_TIMEn. It is used for FDD cells in case the quality measure for cell selection and reselection is set to CPICH Ec/No.
penaltyTime
temporaryOffset2
11 12
UmtsNeighbouringRelation FddNeighCellSelectionInfoCon nectedMode

OAM parameter hcsPrio SIB 11 12 qHcs 11 12 11 12 11 12 Object GsmNeighbouringCell GsmCellSelectionInfoC onnMode GsmNeighbouringCell GsmCellSelectionInfoC onnMode GsmNeighbouringCell GsmCellSelectionInfoC onnMode GsmNeighbouringCell GsmCellSelectionInfoC onnMode description/comment Integer (0..7). This specifies the HCS priority level (0-7) for the neighbouring cells. HCS priority level 0 means lowest priority and HCS priority level 7 means highest priority. Integer( 0..99). This specifies the quality threshold levels for applying prioritised hierarchical cell re-selection. Integer(0, 10, 20, 30, 40, 50, 60) in sec. This specifies the time duration for which the TEMPORARY_OFFSETn is applied for a neighbouring cell. Integer (3, 6, 9, 12, 15, 18, 21, inf)in dB. This specifies the offset applied to the H and R criteria for a neighbouring cell for the duration of PENALTY_TIMEn. It is used for GSM cells in case the quality measure for cell selection and re-selection is set to CPICH RSCP.
penaltyTime
temporaryOffset1

Support of the corresponding system information transmission, Support of a hierarchical radio plan, Support of radio parameters setting with high accuracy, Support of mobility detection for better efficiency even if not mandatory for HCS processing,

No impact.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 124/213
UMTS Radio Mobility
5.
5.1.
COMMON PROCEDURES
PERIODIC MEASUREMENT REPORTING MODE
One possible reporting mode is the periodic reporting mode. This section indicates in which order the various processes are performed in the RNC when receiving a periodic Measurement Report message from the mobile (e.g. each 500 msec). 1. 2. 3. 4. alarm handover criteria evaluation (inter-system, 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, or intersystem measurements)
This reporting mode is not recommended in this version (but is still available for trace purpose).
5.2.
INTRA-FREQUENCY EVENT TRIGGERED MEASUREMENT REPORTING MODE
5.2.1 DESCRIPTION
Another reporting mode is the intra-frequency event triggered reporting mode. This mode is strongly recommended. The use of event triggered reporting has a direct impact on the following mechanisms: primary cell determination (refer to 5.4) active set management (refer to 5.3) alarm measurement criteria (refer to 5.9) inter-frequency blind handover (refer to 5.2.3) Radio Link colour determination (refer to 5.2.3) The target cell choice for alarm handover is not impacted by the event triggered reporting mode. The basic principle of event handling is that the event semantic is taken into account in the implementation, e.g. event 1A reception leads to radio link addition, while event 1B involves a RL deletion. If not specified otherwise, Measured results reported by the UE on other cells than the one having triggered the event are not used in mobility handling algorithms e.g. measured results reported in event 1A shall not lead to RL deletion in the current active set. The main reason for is about Time To Trigger. Making a decision at the RNC side until Time To Trigger has elapsed at the UE side may lead to unstable situations (ping-pong ). The main principle of intra-frequency event triggered is to
Rely on intra frequency events for management of intra-frequency mobility: configuration of events (1A, 1B, 1C, 1D, 1E, 1F, 2D and 2F) 1A 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)
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 125/213
UMTS Radio Mobility

Note: Although being related to intra-frequency measurements, 2D and 2F are categorized in the inter-frequency event group, which helps to decrease the number of simultaneous intrafrequency events required.
Also configure events (1E and 1F) if the feature SHO enhancement (release UA04.1) is enabled (on a per user service basis) 1E 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 [USA Market].
Also configure, when the alarm condition is fulfilled, inter-frequency or inter-RAT measurements in periodic mode Also configure event (1J) used for E-DCH active set management if parameter isRrcEdchEvent1JAllowed is set to TRUE (refer to [R6] for details). 1J a radio link that is DCH active set but not in the E-DCH active set becomes stronger than one radio link that is in the E-DCH active set
(1) Measurement result is Ec/N0 (2) Measurement results are Ec/N0 and RSCP
5.2.2 CONFIGURATION
The event-triggered mode is chosen if this reporting mode is allowed in the FDD Primary Cell (O&M Fdd Cell parameter isEventTriggeredMeasAllowed) where the UE is established and if the preferred eventtriggered mode is FULL-EVENT at the RNC level. During all the life of a call, this choice of the reporting mode is computed at each transition to CELL DCH (CELL_FACH or xxx_PCH or Idle to CELL_DCH whether the call is handled over DCH or HSDPA). And when the mode Full-Event is selected at the establishment in CELL_DCH, there is no mechanism to switch the mode during this phase of the call in CELL_DCH. If event-triggered is configured in the cell where the UE transits to CELL_DCH, the RNC chooses this measurement reporting mode after the transition to CELL_DCH. If the event-triggered reporting is configured, all SHO related events are configured, plus events required for Alarm Measurement criteria. If the call is setup on CELL_FACH or if an Always-On takes place, the events are configured once the RB is setup or reconfigured in CELL_DCH state. If the call is setup on CELL_DCH, the events are configured once the Signalling Radio Bearer is setup. According to [R3] Event 1A may be configured in SIB11 A MEASUREMENT CONTROL will be sent after the transition to CELL_DCH to configure 1A (the 1A configured by SIB11 is overridden) to 1J events. The intra-frequency cell list will be updated by the first MEASUREMENT CONTROL sent after the transition to CELL_DCH i.e. the entire cell list is sent to the UE (by removing all the cells and giving the new list) to ensure that the cell list in the UE and the RNC are exactly the same.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 126/213
UMTS Radio Mobility

As a principle, if all parameters related to a specific event are unchanged, the event is not configured again. On the other hand, if SHO and Alarm Measurement parameters are changing after a change of primary cell or a RB reconfiguration, all events need to be re-configured, as in call setup case.
COMMON ID PROCEDURE HANDLING

The Common ID procedure is used in the early phase of the connection setup by the Core Network to provide the RNC with the user IMSI identity. This identity is stored by the RNC in order to allow paging coordination, i.e. the possibility to make the relationship between an on-going connection and a paging received by another Core Network domain so that the Paging is sent as a type 2 on DCCH. In the National Roaming context, the user IMSI is also used to restrict the list of neighbouring cells, depending on the IMSI-PLMN access right table defined at the RNC level. From that perspective, it may happen that Measurement Control RRC messages are sent to the UE on reception of the Common ID message on the Iu. There is no impact on the measurement configuration. An update of the monitored set cells (intra-frequency and/or inter-frequency and/or inter-RAT) may be required.
MEASUREMENT CONTROL FAILURE

On reception of a MEASUREMENT CONTROL FAILURE from the UE, the RNC will: if the UE is pre-release 5 (i.e. R99, R4) the message is ignored. This may lead to a drop call since measurement reporting may be not configured properly and therefore mobility management may not be handled. If the UE is Release 5 o if the failure is due to a configuration of intra-frequency measurement or inter-frequency measurement events 2D/2F the call will be released and the call will be traced o if the failure is due to a configuration of inter-frequency/inter-RAT alarm measurements then the RNC takes no action. The timeout of the Blind HO timer is normally running and a Blind Handover procedure is triggered at its expiration. Deactivate the Compressed Mode in the NodeB in case of Measurement Control Failure due to CM activation for an HSxPA call.
SUMMARY
According to [A7], the UE shall be able to support in parallel per category up to Ecat reporting criteria as defined in following table:
25.133 Requirements for reporting criteria per measurement category

Measurement category Intra-frequency Inter-frequency Inter-frequency, 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.
All the events needed in UA06.0 Alcatel-Lucent implementation are listed in the table below.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 127/213
UMTS Radio Mobility
Algorithm
Primary Cell Active Set Mgt Absolute Thresholds Alarm Meas. Criteria
Intrafrequency CPICH RSCP 0 0

0 0
Intrafrequency CPICH Ec/No 1 (1D) 4 (1A, 1B, 1C, 1J) 2 (1E, 1F)
0
Interfrequency2
InterRAT
Traffic volume measurements
0 0 0 4 (2D Ec/No, 2D RSCP, 2F Ec/No, 2F RSCP)
0 0 0 0
Always-On Intra-freq Inter-RNC HO without Iur Total:
1 (4A) 1 (1A)
Current solution requires fewer events than the 3GPP limit.
5.2.3 FEATURE INTERWORKING

RADIO LINK COLOR
Once that the event reporting mode is introduced, the radio link colour evaluation as currently implemented for periodical reporting (see [R7] for details) needs to be updated. If event reporting mode is configured, the radio link colour evaluation is based on (the measurement results available in the event reporting to refresh the RL colour. The major drawback of this solution is that in very low mobility scenarios (i.e. number of event reports is low) the RL colour may not reflect the current status of the RL
SRLR BLIND WINDOW

Synchronous Radio Link Reconfiguration (SRLR) may be performed at any time during connection lifetime (Always-On, incoming PS on a CS call, RB adaptation ). During SRLR processing time, the RNC is unable to maintain the active set. In periodic reporting mode, all measurement received during this phase are put aside, and the active set management process is resumed on the basis of measurements received once the SRLR is complete. In event reporting mode, the situation is different, as critical events may have been received during the SRLR phase. As from 25.331 RRC specifications, some events as 1A, 1C and 1J can be reported periodically, but others like 1D, 1E, 1B and 1F cannot. Based on the events received during the SRLR time window, the RNC applies a specific process described below. This process is also applicable to other RRC procedures such as active set update.
The inter-frequency events are used for inter-frequency handover as well as for inter-RAT handover
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 128/213
UMTS Radio Mobility
EVENT 1A, 1C, 1E, 1J

The RNC processes the last 1A, 1C, 1E or 1J event received during the SRLR window, so that the corresponding Radio Link is added to the active set just after the completion of the SRLR. In case of the change of the DLAsConf, the received 1A, 1C, 1D, 1E, 1J events with the old configuration (previous DLAsConf) are available. Even if the new configuration is different, they are used to take a mobility decision at the end of a Blocking Phase. [USA Market - 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]
EVENT 1B, 1F
If received during the SRLR window, all 1B and 1F are processed in UA05. [USA Market If the parameter isOne1bStorageAllowed is set to TRUE then only the last received event 1B will be stored for UEs later than R99 because those UEs are capable to repeat event 1B as well.] If received during the SHO blocking window (i.e. during the NBAP procedure execution), 1B and 1F are treated by the RNC at the end of a Blocking Phase. [USA Market 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.]
EVENT 1D
The last 1D event received during the SRLR window, is treated by the RNC. Active Set processing during the blocking phase: Take into account all received event 1F (if one RL is remaining at least). Take into account all received event 1B (if one RL is remaining at least). Take into account the last received event 1A or 1C (if there is enough room in Active Set at least for 1A). Take into account the last received event 1E (if there is enough room in Active Set at least). Take into account the last received event 1J (if there is enough room in Active Set at least). Take into account the last received event 1D. If the triggering cell is in the Monitored Set (possible for UE not in R5), a RL Addition can be performed with this cell. 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.
EVENTS 2D, 2F
These events are processed when received since they correspond to arm and stop timer. The Hard HO treatment has priority on Soft HO, which has priority on alarm measurements activation.
5.2.4 PARAMETERS
Name Object/Class
FDDCell Class3
isEventTriggeredMeasAllowed
Definition Flag which enables the event reporting mode
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 129/213
UMTS Radio Mobility
5.3.
ACTIVE SET MANAGEMENT
The Active Set is managed differently according to the reporting mode (periodic or intra-frequency event triggered). The Active Set is supported over Iur.
5.3.1 ALGORITHM FOR PERIODIC REPORTING MODE

The active set evaluation process is characterized by: - periodic evaluation: performed at each reception of periodic RRC MEASUREMENT REPORT - decision based on relative criterion : threshold applied on (max CPICH Ec/No CPICH Ec/No(cell to be evaluated)) - a hysteresis is applied for radio link removal which leads to two thresholds : ADD and DROP thresholds - continuity in active set is insured : at least the best cell of the current active set is maintained after new active set evaluation even if it is outside window.
The algorithm is the following : 1. 2. Find the cell with the highest CPICH Ec/No. Lets 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 - Keep as eligible in the active set those which Ec/No(0)-Ec/No(i) < drop_threshold - Cells to be dropped = the others - If all the cells of the current active set are non eligible, keep at least the best one Compare (Ec/No(0) Ec/No(i)) to add_threshold for cells not in the current active set - Put as eligible those which Ec/No(0)-Ec/No(i) < add_threshold Rank all the eligible cells - Keep the max_legs first cells in the active set - but insuring that at least one cell from the current active set is in the list
3. 4.
All the parameters used in the algorithm above are attached to the current primary cell.
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 56: algorithm for active set management
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 130/213
UMTS Radio Mobility
5.3.2 ENHANCED ALGORITHM FOR PERIODIC REPORTING MODE

The algorithm specified in the section above is based on a relative threshold comparison. Based on the field observations and CDMA experience, the following points have been identified as important factors to better manage the mobility: Add a good link to the Active Set as quick as possible Maintain the quality of the Active Set by preventing weak links to get into the Active Set and dropping them from the Active Set as quick as possible As a consequence, an enhanced SHO management algorithm is available, working as follows: If a radio link from the active set satisfies either the relative drop_threshold comparison, or a comparison with an absolute threshold ShoLinkAdditionCpichEcNoThreshold, the radio link is removed from the active set. Similarly, if a radio link from the monitored set satisfies either the relative add_threshold comparison, or a comparison with an absolute threshold ShoLinkDeletionCpichEcNoThreshold, the radio link is added to the active set. The first condition is illustrated by the following picture.
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 57: SHO enhancement - link deletion

The second condition is illustrated by the following picture.
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 58: SHO enhancement - link addition

UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 131/213
UMTS Radio Mobility
This algorithm can be completely or partially de-activated. Please check the [parameter] section for further details. Moreover this enhanced SHO management algorithm enables the use of CIO (cell individual offset) parameter in the evaluation of active set update and primary cell determination algorithm.
5.3.3 PARAMETERS FOR PERIODIC REPORTING MODE

The parameters are:
Name
Object/Class
SoftHoConf Class3 SoftHoConf Class3 SoftHoConf Class3 SoftHoConf Class3 SoftHoConf Class3 SoftHoConf Class3 SoftHoConf Class3
legDroppingDelta legAdditionDelta maxActiveSetSize ShoLinkDeletionCpichEcNoThreshold ShoLinkAdditionCpichEcNoThreshold ShoLinkDeletionAbsoluteThresholdEnable ShoLinkAdditionAbsoluteThresholdEnable
Definition threshold to withdraw a cell from the active set, referred to as drop_threshold in the section above threshold to add a cell in the active set, referred to as add_threshold in the section above maximum number of legs in macrodiversity (from 1 to 6), referred to as max_legs in the section above Absolute threshold for radio link deletion Absolute threshold for radio link addition If enabled, the absolute threshold for radio link deletion is applied If enabled, the absolute threshold for radio link addition is applied
When the current primary cell pertains to the DRNC and as far as neither the class of cell nor the cell parameters (which are proprietary) are not reported over the Iur, the set of parameters which will be used for the algorithm will be a default set defined per Neighbour RNC. Cell Individual Offset CIO will be used in the AS evaluation algorithm only when at least one of the ShoLinkXxxAbsoluteThresholdEnable flag is True.
5.3.4 CASE OF INTRA-FREQUENCY EVENT-TRIGGERED REPORTING MODE

DESCRIPTION OF EVENT-TRIGGERED REPORTING MEASUREMENTS BASED ON RELATIVE THRESHOLDS
In event triggered mode, events 1A and 1B are used, so that Radio Link Addition (resp. Radio Link Deletion) are actually triggered by the reception of event 1A (resp. 1B) from the mobile. As in [A4], the condition for event 1A reporting is as follows:
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, event 1A allows the same behavior as with current algorithm. This works the same way for event 1B:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 132/213
UMTS Radio Mobility
NA 10 LogM Old + CIOOld W 10 Log M i + (1 W ) 10 LogM Best ( R1b + H 1b / 2), i =1

In order to trigger a report, the triggering condition has to be valid for a period of time named time to trigger. This parameter is configurable for each event. CIONew and CIOOld refer to as Cell Individual Offset. MBest and MOld refer to as CPICH Ec/No measurements made by the mobile. H1a and H1b refer to as hysteresis parameters. They can is set to the value of hysteresis1A and hysteresis1B [USA Market refer to section 6.3]. R1a and R1b refer to as reporting range parameters. They are configured to the values of cpichEcNoReportingRange1A and cpichEcNoReportingRange1B respectively. In case of SHO leg number limitation or if the Active Set is full, it is critical to put the strongest cells in the active set (among the ones being reported by 1A). For that purpose, event 1C is (A non-active primary CPICH becomes better than an active primary CPICH) needed to ensure the RNC keeps the main radio links in the active set, as with the existing periodic reporting mechanism. The following picture illustrates a case where 1C event is needed, based on the following assumptions: The active set is limited to 2 links for illustration purpose only Events 1A and 1B are configures as above (CIO = 0, W = 0, H1A = H1B = 0
Measurement quantity P CPICH 1 P CPICH 2 R1B R1A P CPICH 3
Reporting event 1A
Reporting event 1C
Time
Figure 59: event 1C use case

At the beginning, cell 1 and 2 are part of the active set, cell 1 being the strongest one. As Cell 3 crosses R1A, event 1A is reported. However, cell 3 is not added to the active set, as the active set size is limited to 2 radio links only. Further on, as 1C is reported, cell 3 is added and cell 2 is removed, so that the active set is based on the strongest cells from the monitored set. Unless 1C is available, this cannot be achieved, as in this case cell 2 remains above R1B. As in [A1], event 1C is triggered by the following condition:
10 LogM New + CIONew 10 LogM InAS + CIOInAS + H 1c / 2

CIONew and CIOInAS refer to as Cell Individual Offset.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 133/213
UMTS Radio Mobility

MBest and MInAS refer to as CPICH Ec/No measurements made by the mobile. H1c refer to as hysteresis parameter. It can is set to the value of hysteresis1C.
In order to trigger a report, the triggering condition has to be valid for a period of time named time to trigger. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger1A, timeToTrigger1B, timeToTrigger1C). The recommended value for timeToTrigger1B will be greater than that for timeToTrigger1C. This may result in the scenario shown in figure below. Event 1C triggered by a non-active cell may be sent earlier than event 1B even if the trigger condition for event 1B started to apply before. However the non-active cell to appear as a candidate for replacement is too weak and should not be added to the active set.
Pilot strength
Strongest active set cell Reporting Range for e1a 2nd 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, but the non-active cell is too weak and should not be added to the active set. The 2nd active set cell should be just removed from the active set.
Time
Figure 60: Enhanced event 1C handling
[USA Market - the algorithm was enhanced such that replacement of an active set cell by a non-active cell reported in Event 1C depends on a threshold thr_replace as defined in formula below:
thr_replace = CPICH_Ec/N0 (strongest active set cell) - Reporting Range R1b
A non-active cell will only be added if its reported CPICH_Ec/N0 plus the Cell Individual Offset is greater than thr_replace:
Reported CPICH_Ec/N0 + CIO > thr_replace
Otherwise the non-active cell will not be added and only the weak active set cell will be removed as if Event 1B would have been received.] The RRC protocol allows configuring the event 1A trigger by either Monitored Set cells or Detected Set cells or both Monitored and Detected Set cells. The following events need to be configured:
Reporting quantity CPICH Ec/No
Event id 1A
Triggering condition Monitored set cells or Monitored and Detected set cells
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 134/213
UMTS Radio Mobility

CPICH Ec/No CPICH Ec/No 1B 1C Active set cells Monitored set cells
The RRC protocol allows configuring periodic reporting of event 1A, 1C and 1B (only from Release 5) as long as the reporting criteria are still valid.
DESCRIPTION OF EVENT-TRIGGERED REPORTING MEASUREMENTS BASED ON ABSOLUTE THRESHOLDS

This will be achieved by using 2 events, namely 1E and 1F on CPICH Ec/No measurements. The following equations [A1] describe the triggering condition for 1E:
10 LogM New + CIONew T1e + H 1e / 2

and 1F:
10 LogMOld + CIOOld T1 f H1 f / 2,
H1e and H1f refer to as hysteresis parameters. They can is set to the value of hysteresis1E and hysteresis1F. T1e and T1f refer to as absolute thresholds. CIOOld and CIONew refer to as Cell Individual Offset. MNew refers to as CPICH Ec/No or CPICH RSCP measurement made by the mobile.
The following picture illustrates event 1E and 1F reporting, in case CIO and H parameters are set to 0. In this figure, the P-CPICH 3 will trigger an event 1E and P-CPICH 1 will trigger an event 1F.
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 61: Events 1E and 1F

In order to trigger a report, the triggering condition has to be valid for a period of time named time to trigger. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger1E, timeToTrigger1F). The RRC protocol allows configuring the event 1E trigger by either Monitored Set cells or Detected Set cells or both Monitored and Detected Set cells. The events used to support this feature would be as follows:
Reporting quantity
Event id
Triggering condition
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 135/213
UMTS Radio Mobility

CPICH Ec/No 1E 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.
ALGORITHM
In case of intra-frequency Event-Triggered Reporting mode, the RNC behaviour is as follows:
If either 1A or 1E (if configured) event is received for a cell of the monitored set, the corresponding radio link is (possibly) added to the active set. In case of several Monitored Set to Add, only the best ordered in the IE Event Results of the Measurement Report is added. The reception of an event 1A or 1E is received for a detected cell will generate a trace and the cell which trigs the event will not be added in the active set unless special conditions for event 1A [USA Market] do apply. [USA Market - If the parameter isDetectedSetCellsAllowed is set to TRUE and the parameter detectedSetCellAddition is set to TRUE or AUTOMATIC then Detected Set cells reported in event 1A will be added to the active set in the following scenario: If the combined intra frequency Cell Info List exceeds its maximum size then cells with lower ranking priority need to be cut off from the list (refer to 5.5.3) which in consequence does no more represent the complete neighborhood of the active set. The cells having been cut off may reappear as Detected Set cells reported by the UE and will then no longer be ignored but be added to the active set.] If either 1B or 1F (if configured) event is received for a cell of the active set, the corresponding radio link is removed from the active set If 1C event is received, the RNC will replace the cell in the Active Set indicated in the measurement report with the cell triggering this event. If several Active Set cells are included in the Event Results and are worse than the Monitored Set cell to add, the RNC deletes them: so the RNC can resize the Active Set [USA Market - Detected Set cells will be added to the active set under the same conditions as described for event 1A above. However a non-active cell (i.e. Monitored Set cell or possibly Detected Set cell) will not be added to the active set if it is too weak as described for enhanced event 1C handling above. In this case event 1C will be acted upon as if event 1B would have been received i.e. only a radio link removal will result.]
In this version, the RNC will not have a special handling to avoid a potential ping-pong generated by RNC actions (i.e. RL addition/deletion) triggered by The reception of one event based on absolute thresholds (1E/1F) followed by the reception of one event based on relative thresholds (1A/1B). Typical example of this scenario could be the addition of a new RL triggered by 1E followed immediately by the deletion of this RL triggered by 1B of the same cell. Or The reception of one event based on relative thresholds (1A/1B) followed by the reception of one event based on absolute thresholds (1E/1F). Typical example could be the addition of a new RL due to 1A followed immediately by deletion of the same RL due to 1F reception. If the Primary cell needs to be removed due to event 1B or 1C reception then the RNC will first determine the new Primary cell (the best cell of the remaining active set) and in case of a HSPA call perform the serving cell change before executing the active set update (see also section 5.4). Note: If event 1F identifies the Primary cell to be removed then the event is ignored. As in SHO enhancement specification for release UA04.1, the radio link addition/deletion absolute criteria makes use of CIO parameter defined in the RNC database (Cell Individual Offset). Therefore: If the SHO enhancement feature (release UA04.1) is active, the CIO will be sent to the UE through the Measurement Control message. In this case, CIO will be applied by the UE on events
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 136/213
UMTS Radio Mobility

1E and 1F, but also on events 1A, 1B, 1C and 1D (for R5 UEs if configured), as in the current SHO enhancement implementation If the SHO enhancement feature (release UA04.1) is not active, the CIO will not be sent to the UE and events 1E and 1F are not configured.
Note: The release information above is added in order to distinguish between this feature (refer to [R5])and the later SHO enhancements [USA Market]. As specified in [R10], the initial power of the Radio Link to be added not only depends from CPICH Ec/No measurement of the new cell, but also on the measurements reported for the other cells in the active set. This is still the case when event-triggered measurement reports are used. The measured results included in the Measurement Report are configured to be reported on Active Set cells and Monitored Set cells and on Detected Set cells (if configured via the parameter isDetectedSetCellsAllowed). If Detected Set cells are reported the RNC will trace this as specified in 5.3.6. The reception of an event during a procedure in progress may induce the storage of the event in order to solve the issues: refer to 5.2.3
CONFIGURATION
As only one intra-frequency measurement quantity is actually required (CPICH Ec/No), all intra-frequency events and measurements can be configured in a single message. As in [A4], some events reporting are not repeated. In order to limit the risk of loosing an event on the radio interface because of bad transmission conditions, all intra-frequency event reports are configured in RLC Acknowledged Mode. The overall structure of the intra-frequency MEASUREMENT CONTROL message is as follows. Up to 8 events can be configured in a single message.
10.2.17 Meas. Control Common part (reporting type) 10.3.7.36 Intra-freq measurements Common part (meas quantities) 10.3.7.39 Intra-freq meas rep criteria Event 1A Event 1B
Figure 62: intra-frequency Measurement Control message structure

In the 10.2.17 common part: The IE Measurement reporting mode contains the specific information: Measurement Report Transfer Mode: Acknowledged mode RLC Reporting Mode: Event trigger In the 10.3.7.36 common part: Intra-frequency measurement quantity: CPICH Ec/No Intra-frequency reporting quantity:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 137/213
UMTS Radio Mobility

o o o
For active set cells: CPICH Ec/No and CPICH RSCP For monitored set cells: CPICH Ec/No and CPICH RSCP For detected set cells: CPICH Ec/No
In all the tables below: not needed means the IE is not part of the message, as it is not needed by 3GPP 25.331 specifications not used means the IE is optional and not used in this implementation.
1A 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 Need OP MP CVclause 0 CVclause 6 CVclause 2 CVclause 1 CVclause 2 Parameter Value 1a Not needed Monitored Set Cells or Monitored and Detected Set cells Use cpichEcNoReportingRange1A parameter Not used If isExtendedSrbDcch3dot4k = False: 0 If isExtendedSrbDcch3dot4k = True: Upper two Bits of hysteresis1A parameter with following mapping: 00 = 0.0 01 = 0.3 10 = 0.6 11 = 1.0 If isExtendedSrbDcch3dot4k = False: Use hysteresis1A parameter If isExtendedSrbDcch3dot4k = True: Lower two Bits of hysteresis1A parameter with following mapping: 00 = 0dB 01 = 1dB 10 = 2dB 11 = 3dB Not needed Use value (maxActiveSetSize-1) Not needed Use timeToTrigger1A parameter Use amountRep1A parameter Use repInterval1A parameter Use maxNbReportedCells1A parameter
>Hysteresis
MP
>Threshold used frequency >Reporting deactivation threshold >Replacement activation threshold >Time to trigger >Amount of reporting >Reporting interval >Reporting cell status
CV-clause 3 CVclause 4 CV-clause 5 MP CVclause 7 CVclause 7 OP
Remark: The Reporting deactivation threshold IE indicates the maximum number of cells allowed in the active set in order for event 1a to occur, so that if the active set is limited by the maxActiveSetSize parameter, the value of this IE shall be set to (maxActiveSetSize-1). The purpose of this IE is to avoid the UE to report event 1A if the active set size limit is reached. [Global Market: Parameter isExtendedSrbDcch3dot4k should be set to False] [USA Market: If parameter isExtendedSrbDcch3dot4k is set to True the WNMS parameter hysteresis1A has different semantics on the user interface (range 0dB to 7.5dB) and within the RNC. The RNC interprets two Bits of the value as hysteresis and the other two Bits as weight. For the parameter mapping refer to section 6.3. Note that the parameter isExtendedSrbDcch3dot4k was spare in UA06 and reused for this purpose; the parameter name does not reflect the actual semantics.]
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 138/213
UMTS Radio Mobility
1B 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 Need OP MP CVclause 0 CVclause 6 CVclause 2 CVclause 1 CVclause 2 Parameter Value 1b Active Set Cells Not needed Use cpichEcNoReportingRange1B parameter Not used If isExtendedSrbDcch3dot4k = False: 0 If isExtendedSrbDcch3dot4k = True: Upper two Bits of hysteresis1B parameter with following mapping: 00 = 0.0 01 = 0.3 10 = 0.6 11 = 1.0 If isExtendedSrbDcch3dot4k = False: Use hysteresis1B parameter If isExtendedSrbDcch3dot4k = True: Lower two Bits of hysteresis1B parameter with following mapping: 00 = 0dB 01 = 1dB 10 = 2dB 11 = 3dB Not needed Not needed Not needed Use timeToTrigger1B parameter Not needed Not needed Use maxNbReportedCells1B parameter Use amountOfRep1B and repInterval1B parameters
>Hysteresis
MP
>Threshold used frequency >Reporting deactivation threshold >Replacement activation threshold >Time to trigger >Amount of reporting >Reporting interval >Reporting cell status >Periodical reporting information-1b
CV-clause 3 CVclause 4 CV-clause 5 MP CVclause 7 CVclause 7 OP CVclause 9
Remark: As a 3GPP R5 improvement, a periodical reporting IE has been added for event 1B. This change is made on a backward compatible way, meaning that this IE, when present, will be decoded by R5 and above UE, and ignored by R99 UEs. This IE is part of Alcatel-Lucent implementation and is sent each time event 1B is configured. [Global Market: Parameter isExtendedSrbDcch3dot4k should be set to False] [USA Market: If parameter isExtendedSrbDcch3dot4k is set to True the WNMS parameter hysteresis1B has different semantics on the user interface (range 0dB to 7.5dB) and within the RNC. The RNC interprets two Bits of the value as hysteresis and the other two Bits as weight. For the parameter mapping refer to section 6.3. Note that the parameter isExtendedSrbDcch3dot4k was spare in UA06 and reused for this purpose; the parameter name does not reflect the actual semantics.]
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 139/213
UMTS Radio Mobility
1C 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 Need OP MP CVclause 0 CVclause 6 CVclause 2 CVclause 1 CVclause 2 MP CV-clause 3 CVclause 4 CV-clause 5 MP CVclause 7 CVclause 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
Remark: The Replacement activation threshold indicates the minimum number of cells allowed in the active set in order for event 1C to occur. The purpose of this IE is to avoid the UE to report event 1C if the active set size limit is not reached.
1E 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 Need OP MP CVclause 0 CVclause 6 CVclause 2 CVclause 1 CVclause 2 MP CV-clause 3 CVclause 4 CV-clause 5 MP CVclause 7 CVclause 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. Use cpichEcNoThresholdUsedFreq1E Not needed Not needed Use timeToTrigger1E parameter Not needed Not needed Use maxNbReportedCells1E parameter
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 140/213
UMTS Radio Mobility
1F 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 Need OP MP CVclause 0 CVclause 6 CVclause 2 CVclause 1 CVclause 2 MP CV-clause 3 CVclause 4 CV-clause 5 MP CVclause 7 CVclause 7 OP Parameter Value 1f Active Set Cells Not needed Not needed Not used Not needed Use hysteresis1F parameter. Use cpichEcNoThresholdUsedFreq1F Not needed Not needed Use timeToTrigger1F parameter Not needed Not needed Use maxNbReportedCells1F parameter
5.3.5 PARAMETERS FOR EVENT REPORTING MODE

All event parameters may be provisioned at OAM level except the Reporting Deactivation Threshold which is equal to maxActiveSetSize (set by OAM).
Name isDetectedSetCellsAllowed detectedSetCellAddition [USA Market] cpichEcNoReportingRange1A
Object/Class
RadioAccessService Class3 FDDCell Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3
hysteresis1A
timeToTrigger1A
amountRep1A repInterval1A maxNbReportedCells1A cpichEcNoReportingRange1B
MeasurementConfClass Class3 MeasurementConfClass Class3 MeasurementConfClass Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3
hysteresis1B
timeToTrigger1B
Definition Allows tracking of detected cells Allows addition of detected set cells to the active set. Relative CPICH Ec/No threshold for SHO Radio Link Addition. CPICH Ec/No hysteresis for link addition in Active Set For UA06 refer to section 6.3. 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. CPICH Ec/No hysteresis for link deletion in Active Set For UA06 refer to section 6.3. Period of time during which the event condition has to be satisfied before sending event 1B
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 141/213
UMTS Radio Mobility

isOne1bStorageAllowed [USA Market]
Radio Access Service Class 3
amountRep1B repInterval1B maxNbReportedCells1B hysteresis1C timeToTrigger1C
MeasurementConfClass Class3 MeasurementConfClass Class3 MeasurementConfClass Class3 UsHoConf Class3 UsHoConf Class3
amountRep1C repInterval1C maxNbReportedCells1C isEnhanced1cHandlingAllowed [USA Market] isEvent1EUsed
MeasurementConfClass Class3 MeasurementConfClass Class3 MeasurementConfClass Class3 Radio Access Service Class 3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3
hysteresis1E
timeToTrigger1E
maxNbReportedCells1E cpichEcNoThresholdUsedFreq1E
MeasurementConfClass Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3
isEvent1FUsed
hysteresis1F
timeToTrigger1F
maxNbReportedCells1F cpichEcNoThresholdUsedFreq1F
MeasurementConfClass Class3 UsHoConf Class3
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 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. 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 Absolute CPICH Ec/No threshold for SHO Radio Link Deletion.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 142/213
UMTS Radio Mobility

COUNTERS
The following counters are defined: Per FDDCell (the Primary RL of the UE is on this FDDCell). All the following counters are of cumulative type: Number of Event 1A triggered by a Cell of the Monitored Set (triggered by event 1A reception). Number of Event 1B (triggered by event 1B reception). Number of Event 1C (triggered by event 1C reception). Number of Event 1D (triggered by event 1D reception). Number of Event 1E triggered by a Cell of the Monitored Set (triggered by event 1E reception). Number of Event 1F (triggered by event 1F reception). Number of Event 1J (triggered by event 1J reception). Number of Event 2D (triggered by event 2D reception). Number of Event 2F (triggered by event 2F reception). Indication of at least one available Call Failure Trace due to a Detected Cell (triggered by reception of event 1A or 1E triggered by a Detected Cell). Per neighboring RNC (The Primary RL of the UE is on this Neighboring RNC). All the following counters are of cumulative type: Number of Event 1A triggered by a Cell of the Monitored Set (triggered by event 1A reception). Number of Event 1B (triggered by event 1B reception). Number of Event 1C (triggered by event 1C reception). Number of Event 1D (triggered by event 1D reception). Number of Event 1E triggered by a Cell of the Monitored Set (triggered by event 1E reception). Number of Event 1F (triggered by event 1F reception). Number of Event 2D (triggered by event 2D reception). Number of Event 2F (triggered by event 2F reception). Indication of at least one available Call Failure Trace due to a Detected Cell (triggered by reception of event 1A or 1E triggered by a Detected Cell).
TRACES
If the MIB flag RadioAccessService.isDetectedSetCellsAllowed is TRUE, the RNC requests the UE: to trigger the following events on Detected Cells also : o event 1A, where triggering Cells are both Detected Set Cells and Monitored Set Cells, o event 1E, where triggering Cells are both Detected Set Cells and Monitored Set Cells, To report the measurement of the Detected Cells in the Measured Result part of these events. If a Detected Cell is reported by the UE, the related counter will be incremented and a Call Failure Trace will be triggered based on a filtering mechanism to avoid overload in both RNC and OMC due to too many Call Failure Traces. This filtering mechanism allows to have at most one Call Failure Trace in a given period (e.g. 15 seconds static value cpTimerFileringCallFailureTrace -), for a set of calls. For the Call Failure Trace, the intra-frequency part of the RRC Measurement Report message and the scrambling code of the Detected Cell are traced.
5.3.7 E-DCH ACTIVE SET MANAGEMENT

From UA06.0, the E-DCH active set can have up to 4 links that are a subset of DCH active set. The serving link is always the primary cell of the DCH active set.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 143/213
UMTS Radio Mobility

All links added to (resp. removed from) the DCH active set are also added, if compatible, to (resp. removed from) the E-DCH active set. If the E-DCH active set is full and a new primary cell is elected which is not in E-DCH active set, this cell is added to E-DCH active set (as serving) and the former primary is removed from E-DCH active set. A new event 1J can be managed: a radio link that is DCH active set but not in the E-DCH active set becomes stronger than one radio link that is in the E-DCH active set. On event 1J report, one link (given in the measurement report) is removed from the E-DCH active set (but kept in the DCH one) and is replaced as non-serving by a link of the DCH active set (also given the measurement report). For all details on this feature, refer to [R6] UMT/SYS/DD/018827 E-DCH System Specification.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 144/213
UMTS Radio Mobility
5.4.
PRIMARY CELL DETERMINATION
5.4.1 DESCRIPTION
The primary cell is a sort of reference cell for the UE. It is used for monitored cells set determination and also as a pointer to mobility parameters, i.e. parameters with a cell granularity which are to be used for a mobile are those corresponding to its primary cell.
5.4.2 CASE OF INTRA-FREQUENCY PERIODIC REPORTING MODE

The determination of a new primary cell is performed after each active set evaluation process. The algorithm is the following : After the active set evaluation process, a candidate cell for new primary cell is selected according to the following condition : - the cell which was already in the active set (so that its neighbouring is already known even if this cell is located on a DRNC) and which has the best CPICH Ec/No Two cases must be considered : - either this candidate cell = current primary cell, in this case the new primary cell = current primary cell - or this candidate cell is different from the current primary cell. In this case : o if CPICH Ec/No(candidate cell) CPICH Ec/No(current primary cell) > DropPriRL new primary cell = candidate primary cell o else the new primary cell = current primary cell
5.4.3 CASE OF INTRA-FREQUENCY EVENT-TRIGGERED REPORTING MODE

DESCRIPTION
The primary cell determination will be usually based on event 1D reception. Note: In addition a primary cell selection can be triggered by event 1B or 1C if the event requests the deletion of the current primary cell (see also section 'Algorithm' in 5.3.4). In the following the normal case of event 1D is described but the same behaviour applies also in case of event 1B or 1C with primary cell removal. In [A4], event 1D is triggered on a condition relative to active set or monitored set measurements, as in the following formula (applicable to CPICH Ec/No measurements):
10 LogM NotBest 10 LogM Best + H 1d / 2

In 3GPP R5, the definition of event 1D has been changed to take into account CIO parameters. In this formula, CIO will only be applied by R5 UEs, and only if requested by a configuration flag present in event 1D configuration sent in Measurement Control message:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 145/213
UMTS Radio Mobility
10 LogM NotBest + CIONotBest 10 LogM Best + CIOBest + H 1d / 2

H1d refers to as hysteresis parameter. This parameter will be set to the value of hysteresis1D parameter. CIONotBest and CIOBest refer to as Cell Individual Offset. MBest and MNotBest refer to as CPICH Ec/No measurements made by the mobile.
The following picture illustrates event 1D reporting, in case CIO parameters are set to 0, cell (1) being the current primary. Event 1D is reported once cell (2) measurement quantity exceeds cell (1) by H1d/2.
Measurement quantity H1d/2
P CPICH 1 P CPICH 2 P CPICH 3
Reporting event 1D
Time
Figure 63: event 1D

As in existing periodic measurement based algorithm, a hysteresis can be used, either cell dependent (through the Cell Individual Offset parameter) or absolute (through the H1D parameter).
ALGORITHM
The primary cell determination will be based on event 1D reception. Based on the reception of this event, the RNC stores the new primary, and applies the current process used in case of change of primary cell. The 1D event can be triggered by a cell in the Active Set for R5/R6 UEs or in the Monitored Set for R99/R4 UEs. Since the events 1A, 1C are also configured (see section 5.3) it is assumed that the new primary cell is already in the Active Set when an 1D event is triggered as explained in the following. This will be typically ensured if the time to trigger of 1D is greater or equal than the time to trigger of events 1A or 1C. It should be noted that a monitored set cell that needs to be included in the active set will trigger first an 1A event if its CPICH Ec/No is lower than the best cell in the Active set but entering in its reporting range or 1C event if the Active Set is full and this cell is better than the worse in the Active Set. An event 1D will typically be triggered by a cell better than the best in the active set. Therefore due to the triggering conditions definition of these events and if the time to trigger of 1D is greater or equal than 1A and 1C typically the 1D will be triggered by a cell in the active set. When CIO is used it may happen that 1A event is not triggered but 1D event is triggered. If the event 1D is triggered by a monitored cell, the RL will be added in the Active Set if not full. If the Active Set is full, then the event1D will provide the replacement of the worse cell in the Active Set.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 146/213
UMTS Radio Mobility

If SHO enhancements (release UA04.1) is enabled and the useCIOfor1D is set to TRUE then CIO values are configured in the UE if the UE is Release 5. Note: The release information above is added in order to distinguish between this feature (refer to [R5]) and the later SHO enhancements [USA Market]. A new primary cell will also be defined if the current primary cell will be removed due to reception of RL deletion events.
CONFIGURATION
Refer to 5.3.4 / configuration for common part of Measurement Control message. 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 CVclause 0 CVclause 6 CVclause 2 CVclause 1 CVclause 2 MP CV-clause 3 CVclause 4 CV-clause 5 MP CVclause 7 CVclause 7 OP CVclause 10
Parameter Value 1d Not needed Not needed Not needed Not used Not needed Use hysteresis1D parameter. Not needed Not needed Not needed Use timeToTrigger1D parameter Not needed Not needed Use maxNbReportedCells1D parameter Use useCIO1D parameter
5.4.4 PARAMETERS
The parameters are:
Name
Object/Class
UsHoConf Class3
rrcIntraFreqMeasurementDropPrimaryRlDelta
useCIOfor1D
MeasurementConfClass Class3
Definition hysteresis for primary cell modification, referred to as DropPriRL in the section above. This flag indicates if CIO parameter has to be taken into account in 1D triggering condition
CPICH Ec/No hysteresis primary cell determination Period of time during which the event condition has to be satisfied before sending event 1D. Maximum allowed number of cells to report with event 1D
hysteresis1D
UsHoConf Class3 UsHoConf Class3
timeToTrigger1D
maxNbReportedCells1D
MeasurementConfClass Class3
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 147/213
UMTS Radio Mobility
When the current primary cell pertains to the DRNC and as far as neither the class of cell nor the cell parameters (which are proprietary) are not reported over the Iur, the set of parameters which will be used for the algorithm will be a default set defined per Neighbour RNC.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 148/213
UMTS Radio Mobility
5.5.
List Of Compounding Cells For The Monitored Set Definition
5.5.1 DESCRIPTION
The object of the section is the introduction of dynamic compounding cell lists in connected mode. This section is based on the feature called UMTS composite neighbour list. Compounding list functionality is the capability for the RNC: o To dynamically create the neighbour list a UE will monitor, when in dedicated mode, depending on the radio neighbourhood of this UE, this neighbourhood being either defined by the active set, or by measurements. o To send, through RRC Measurement Control message, this compound list to UE A new algorithm (type 1) to compute the compound neighbour cell list has been introduced for intrafrequency, inter-frequency and inter-RAT neighbour cells. In the latter cases only those cells which are supported by the UE according to its capabilities will be considered for addition to the compound neighbour list.
5.5.2 APPLICABILITY
The feature is efficient if the intra frequency -, inter frequency or inter RAT neighbour of each Fdd cell is optimized. In this case there will be enough space in the Measurement Control message to add neighbour cells of active cells other than those of the primary cell. It applies for calls in cell-DCH state only.
5.5.3 ALGORITHM
The best cell is the cell with the best CPICH Ec/No. If feature compounding list is not activated: The monitored set is the neighbouring list of the primary cell. If feature compounding list is activated: Three different algorithms (PRL, Type1 and Type2) are available for intra frequency neighbour cells and two different algorithms (PRL and Type1) are available for inter frequency - or inter RAT neighbour cells. The algorithm will be selected according to the value of primary cell parameter typeOfCompoundingNeighbourListIntraFreq typeOfCompoundingNeighbourListInterFreq typeOfCompoundingNeighbourListInterRAT respectively:
Type PRL: The monitored set is the neighbouring list of the primary cell. The behavior is the same as if feature compounding list is not activated.
Type 1: Compound neighbour list is build from all active set cells. The neighbors are selected into the compound list based on (given in order of significance)
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 149/213
UMTS Radio Mobility
The RNC selects the first N cells from the prioritized neighbour list of the primary cell (N stands for parameter numOfPrimaryCellNeighbourIntraFreq, numOfPrimaryCellNeighbourInterFreq or numOfPrimaryCellNeighbourInterRAT respectively) It adds cells with the highest number of occurrences of the cell in the neighbor lists of the active set cells If some neighbour cells have the same occurrence, it selects the cell with the highest measured quality of the active set cell In case of same quality, it selects cells with higher priority of neighbour cell (parameter neighbourCellPrio or sorting order for DRNC) If the maximum number of allowed cells in the compound neighbor list (parameter maxCompoundingListSizeIntraFreq, maxCompoundingListSizeInterFreq or maxCompoundingListSizeInterRAT respectively) is exceeded then the lower priority cells are discarded.
Type 2 (only applicable for intra frequency neighbour cells): The monitored set is built as the union of o The primary cell plus its static neighbour list for dedicated mode o Either the best cells of the active set and their static neighbour list for dedicated mode, when the connection is engaged in soft or softer HO, until: the last leg and its static neighborhood list for dedicated mode has been added, or the list reaches maxSizeCompoundingList cells.
Or the N first (bests) measured cells and their static neighbour list for dedicated mode, when the connection is not engaged in soft or softer HO. Until: the new monitored cell set goes up to maxNbOfMonitoredCellForNonShoCompoundList cells , or the list reaches maxSizeCompoundingList cells; or until the last measured cell.
The compound intra frequency neighbour cell list shall be computed when
state transition to Cell_DCH, successful hard handover, change of primary cell or active set update
has occurred. The compound inter frequency neighbour cell list shall be computed when
change of primary cell or active set update
has occurred while inter frequency measurements are ongoing or when
a new RRC Measurement Control message for inter-frequency measurements (measurement type 2)
has to be sent to UE. The compound inter RAT neighbour cell list shall be computed when
a new RRC Measurement Control message for inter-RAT measurements (measurement type 3)
has to be sent to UE.

UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 150/213
UMTS Radio Mobility

Whatever the neighbor building list method, the neighbour list updates only include the cells to be removed and to be added (delta between the previous neighbourhood and the new neighbourhood). In case of intra frequency neighbour cells there is a special handling such that no update will be sent to UE if cells have been removed only but no cells have been added.
5.5.4 PARAMETERS
Name maxCompoundingListSizeIntraFreq maxCompoundingListSizeInterFreq maxCompoundingListSizeInterRAT isCompoundingCellListActivated typeOfCompoundingNeighbourListIntraFreq Object/Class
RadioAccessService Class3 RadioAccessService Class3 RadioAccessService Class3 RadioAccessService Class3 FDDCell Class 3
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 inter-RAT compound list
Used to activate or inhibit the compounded list feature
Used to determine the algorithm for intra-frequency neighbor list creation for dedicated measurements. Possible values are PRL, Type1, Type2 Used to determine the algorithm for intra-frequency neighbor list creation for dedicated measurements. Used when primary cell is on DRNC. Possible values are PRL, Type1, Type2 Used to determine the algorithm for inter-frequency neighbor list creation for dedicated measurements. Possible values are PRL, Type1 Used to determine the algorithm for inter-frequency neighbor list creation for dedicated measurements. Used when primary cell is on DRNC. Possible values are PRL, Type1 Used to determine the algorithm for inter RAT neighbor list creation for dedicated measurements. Possible values are PRL, Type1 Used to determine the algorithm for inter-RAT neighbor list creation for dedicated measurements. Used when primary cell is on
typeOfCompoundingNeighbourListIntraFreq
typeOfCompoundingNeighbourListInterFreq
FDDCell Class 3
typeOfCompoundingNeighbourListInterFreq
typeOfCompoundingNeighbourListInterRAT
FDDCell Class 3
typeOfCompoundingNeighbourListInterRAT
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 151/213
UMTS Radio Mobility

DRNC. Possible values are PRL, Type1 The minimal number of intrafrequency neighbor cells of the primary cell to be definitely included in the compound neighbor list. The minimal number of intrafrequency neighbor cells of the primary cell on DRNC to be definitely included in the compound neighbor list. The minimal number of interfrequency 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. The minimal number of interRAT neighbor cells of the primary cell to be definitely included in the compound neighbor list. The minimal number of interRAT neighbor cells of the primary cell on DRNC to be definitely included in the compound neighbor list. The priority of intra-frequency or inter-frequency neighbour cells The priority of inter-RAT neighbour cells
numOfPrimaryCellNeighbourIntraFreq
FDDCell Class 3
numOfPrimaryCellNeighbourIntraFreq
numOfPrimaryCellNeighbourInterFreq
FDDCell Class 3
numOfPrimaryCellNeighbourInterFreq
numOfPrimaryCellNeighbourInterRAT
FDDCell Class 3
numOfPrimaryCellNeighbourInterRAT
umtsFddNeighbouringCellList[].neighbourCellPrio gsmNeighbouringCellList[].neighbourCellPrio
FDDCell
Class 3
FDDCell Class 3
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 152/213
UMTS Radio Mobility

The following counters are defined on FDDCell basis
VS.MeasurementControlCellListSize Size of the compound intra frequency neighbor list VS.ExceededAggregateCellListSizeIntraFreq Amount by which the maximum intra-frequency neighbor list size is exceeded. VS.AggregateCellListAmbiguousCellIntraFreq The aggregate intra-frequency neighbor list contains an ambiguous cell. VS.MeasCtrlCellListSizeInterFreq Size of the compound inter-frequency neighbor list VS.ExcdAggrCellListSizeInterFreq Amount by which the maximum inter-frequency neighbor list size is exceeded VS.AggrCellListAmbigCellInterFreq The aggregate inter-frequency neighbor list contains an ambiguous cell. VS.MeasCtrlCellListSizeInterRAT Size of the compound inter-RAT neighbor list VS.ExcdAggrCellListSizeInterRAT Amount by which the maximum inter-RAT neighbor list size is exceeded VS.AggrCellListAmbigCellInterRAT The aggregate inter-RAT neighbor list contains an ambiguous cell
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 153/213
UMTS Radio Mobility
5.6.
Management Of System Information Blocks (Sib)
5.6.1 SIB UPDATE

During procedures like cell search or cell (re)selection, the UE may read some system information (SIB) broadcasted on the FDD cell. If the operator modifies an FDD cell attribute, this updated attribute is broadcasted by a System Information Block (SIB1, SIB2, SIB3, SIB4, SIB5, SIB6, SIB11 or SIB12) as follows: The SRNC sends the content of all SIB to the NodeB (NBAP System Info Update procedure), which leads it to update the broadcasted SIB content with an updated value tag Then the UEs in idle mode are notified by paging from RNC which forces them to re-acquire the new Sys. Info. For the UE in cell FACH state, they are notified by a SYSTEM INFORMATION CHANGE INDICATION message. For the UE in URA PCH or CELL PCH state, the behaviour is the same than in Idle date (type 1 paging) Note 1: The SIB7 filling is managed by the NodeB. Note 2: SIB4 and SIB12 are sent only if parameters isDynamicSibAlgoWithSBAllowed are set to TRUE (refer to 4.5.4).
SIB4Enable,
SIB12Enable
and
5.6.2 SIB REPETITION PERIOD

In UA05.0, a dynamic SIB scheduling algorithm sets the repetition period (IB_SG_REP) and the position (IB_SG_POS) of each SIB according to the number of SIB segments needed [A3]. The algorithm uses the following constraints: MIB block has a repetition period set to 8 and a position set to 0 ; SIB1 and SIB7 blocks have the same repetition period set to 16 and a start position set to 2; SIB3 shall have a RP0 repetition period between 32 and 128; SIB2, SIB5, SIB6 and SIB11 shall have a RP1 repetition period between 32 and 256. The setting of RP0 has a higher priority than RP1 i.e. the algorithm tries to find the lowest repetition period value for RP0 first then for RP1. In UA06.0, with introduction of SIB4 and SIB12, the dynamic SIB scheduling algorithm is modified. This new algorithm is used if parameter isDynamicSibAlgoWithSBAllowed is set to TRUE. It uses the following constraints:
Limitation of the number of MIB segments. It shall not exceed one segment. Use of a SB1 block when all scheduling information cannot be coded in one MIB segment: the SIB scheduling information (whatever the SIB) which cannot be encoded in MIB are encoding in SB1. MIB block has a repetition period set to 8 and a position set to 0 ; SIB1 and SIB7 blocks have the same repetition period set to 16 and a start position set to 2; SIB3 and SIB4 shall have the same RP0 repetition period between 32 and 128; SIB2, SIB5, SIB6, SIB11 and SIB12 shall have the same RP1 repetition period between 32 and 256. The SB1 repetition period is set to the lowest repetition period of SIB(s) (RP0 or RP1) which may be addressed by SB1.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 154/213
UMTS Radio Mobility
5.7.
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. This allows the activation of the intra-frequency measurement event 1A for each mobile entering in Cell-DCH state. These UEs acquire intra-frequency configuration contained in SIB11. They can start and report their intra-frequency measurements without waiting any RRC Measurement Control message. For event triggered reporting only event 1A is configured. See reference document [R3] UMT/SYS/DD/013000 Mobility Performance Improvements.
5.8.
DHO MANAGEMENT
This section provides an overview of the management of diversity handover (uplink) in Alcatel-Lucent UTRAN nodes.
MSC/ SGSN Iu Iur SRNC DRNC
Iub NodeB 1 NodeB 2 NodeB 3
UE
Figure 64: Macro-diversity in uplink

At the NodeB level: If several radio links are active for the same UE in a NodeB, the NodeB performs radio link recombination, so that there is only one AAL2 Cid on the Iub for all combined radio links. This is what is done in NodeB 2 in the figure above. The MRC (Maximum Ratio Combining) algorithm implemented in the BTS makes use of conventional "Rake receiver" techniques, i.e. all the different paths (or at least the ones received with the highest energy) are recombined in the rake receiver before channel decoding. At the DRNC level: The Cid from the Iub interface are only switched to the Iur (in the figure above, the 2 data streams from NodeB 2 and NodeB 3 are switched to the Iur between the DRNC and the SRNC). In this version, Radio Link recombination is not supported at the DRNC. It means that, if a "Radio Link Addition" is received from the SRNC, requesting the DRNC to perform diversity recombination, the request will be rejected by the Alcatel-Lucent DRNC if two different Node Bs are involved under the drift (but accepted if only one Node B). At the SRNC level: All the Radio Links terminating at the SRNC level are recombined by the SRNC (i.e. the data streams from NodeB 1 and the 2 streams from the Iur in the figure above).
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 155/213
UMTS Radio Mobility

The recombination process performed by the SRNC is actually a frame selection process, based on the payload CRC, and TB CRCI (CRC Indicator) and QE (Quality Estimate) fields received from each data stream. This process works as follows: the payload CRC of the UP frames (if included) is checked. Any frames with bad CRC is rejected in each frame, only TB with a "correct" CRCi are kept. Others are rejected. in case TB from different stream have a "correct" CRCi, the TB with the best QE if eventually selected anyway, if the QE is not good enough, the CRCi will be considered as "not correct" regardless of the value received from the NodeB
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 156/213
UMTS Radio Mobility
5.9.
ALARM HANDOVER AND ALARM MEASUREMENTS
5.9.1 OVERVIEW
In this version of the document, alarm handover is a Hard Handover triggered by the iMCTA function when an Radio alarm condition is detected. The others reasons for processing a Hard Handover managed by the iMCTA function are: CAC failure and Service (see section 4.20). It may induce one of the following mobility cases: 3G to 2G handover for PS 3G to 2G handover for CS 3G to 2G handover for CS+PS inter-frequency inter-RNC handover inter-frequency intra-RNC intra-frequency inter-RNC Alarm Measurements refers to either inter-frequency measurements or inter-system GSM measurements. This section deals with Alarm radio condition. The Triggering of the Alarm measurement and the handover is based on the Fast Alarm algorithm.
Fast Alarm algorithm description:

As illustrated in the figure below, the Alarm measurements are activated once a criteria Cr is fulfilled, possibly following by Compressed Mode activation. As soon as the first valid measurement is received from the mobile, the Alarm handover is performed. This algorithm allows better reactivity from UTRAN, as only one radio criteria is used for both alarm measurement and handover triggering. It also has a positive impact on network capacity as it limits the time during which Compressed Mode is active.
Radio quality Cr
Alarm Measurements Reporting phase
time
Alarm Measurements trigger
1st valid measurement from UE Alarm Handover trigger
Figure 65: the fast alarm algorithm
5.9.2 ALARM MEASUREMENTS ACTIVATION WHEN INTRA FREQUENCY MEASUREMENTS ARE PERIODIC BASED
Inter-system and inter-frequency measurements are requested under certain radio conditions.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 157/213
UMTS Radio Mobility

At each reception of RRC MEASUREMENT REPORT (which is periodic), and once the primary cell has been updated, the following criteria is evaluated:
AlarmMeas = (CPICH Ec/No < ThreshEcMeas) or (CPICH RSCP < ThreshRSCPMeas) for the Primary cell.
Then, the following process is applied: If AlarmMeas is valid Increment AlarmMeasCounter by UpStep Else Let AlarmMeasCounter = max (0, AlarmMeasCounter DownStep) Endif If AlarmMeasCounter > AlarmMeasCounterThreshold then Alarm measurements are requested from the mobile The following figure illustrates this process:
Yes Alarm Measurement criteria No
Measurement report occasions AlarmMeasCounter AlarmMeasCounterThreshold DownStep UpStep Alarm Meas decision: AlarmMeasCounter > AlarmMeasCounterThreshold
time
Figure 66: Alarm measurement decision process

In case the Alarm Measurement Criteria is valid, then the following is applied: 1. 2. Inter-system or inter-frequency measurements are requested from the mobile using a Measurement Control message (please refer to the section 5.10 for further details). Compressed Mode is possibly activated using the Measurement Control message, based on mobile needs, as indicated in the mobile "UE capabilities" Information Element". For further details on this procedure, please refer to the 5.12 chapter on Compressed Mode. if compressed mode needs to be reactivated , a Compressed Mode Command message is sent to the UE
3.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 158/213
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) ...
Intrafrequency measurement configuration done in the call setup phase
RRC/ Measurement report (intrafreq meas) RRC/ Measurement control (intersystem, neigh GSM cells, start CM) RRC/ Measurement report (intrafreq meas, intersystem meas)) ... RRC/ Measurement report (intrafreq meas, intersystem meas)) RRC/ Measurement control (start CM)
Based on intrafrequency measuremenst and depending on mobile capability, the SRNC decides to request intersystem measurements. Compressed Mode is also possibly activated, depending on mobile needs The UE is now able to report both intersystem and intrafrequency measurements. There is one single report for both reported quantities
Later on, the compressed mode activation condition is still valid, and compressed mode is re-activated
Figure 67: measurement activation example (inter-system case)
As a MEASUREMENT REPORT is received with GSM (resp. inter-frequency) measurements, the Alarm Measurement criteria is checked again. If still valid, a hard handover is triggered towards the chosen target cell. If no neighbouring measurement may be requested to the UE but Inter Rat HHO is allowed (for example: CM not possible, neighbouring cells filtered after applying IMSI criteria) or no suitable Alarm measurement is reported by the mobile within a guard timer period, a blind handover towards the blind GSM cell provisioned for the Primary cell may be performed by the RNC.
Remark 1: The additional check on the Alarm Measurement criteria once a measurement is received is needed, as the radio conditions may change between the measurement activation and the reception of the first measurement report with GSM/inter-frequency measurements. As seen on live networks, the mean period of time between the sending of the MEASUREMENT CONTROL and the reception of the related MEASUREMENT REPORT is around 3s. This is explained by: The current value of Compressed Mode activation time (1,52 s), quite high but necessary to secure the correct reception of the MEASUREMENT REPORT message by the UE
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 159/213
UMTS Radio Mobility
The fact that the mobiles need at least 1,5 s of Compressed Mode for measuring and decoding a first set of neighbouring GSM BSIC.
Remark 2: In case of handover failure, the HO decision counter (InterSystemDetectionCounter) need to be reset in order to avoid a second handover attempt to be made towards the same cell too shortly after the failure.
5.9.3 ALARM MEASUREMENTS ACTIVATION WHEN INTRA FREQUENCY MEASUREMENTS ARE EVENT BASED
DESCRIPTION
A solution based on events 2D and 2F will be used. Although being related to intra-frequency measurements, 2D and 2F are categorized in the inter-frequency event group, which helps to decrease the number of simultaneous intra-frequency events required. Besides, the fact that 2D/2F are only triggered by the Best cell of the active set allows to save unnecessary measurement reports. In [A4], 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 Ec/No based event this is set to the value of the parameter cpichEcNoThresholdUsedFreq2D. For CPICH RSCP based event this is set to the value of the parameter cpichRscpThresholdUsedFreq2D. TUsed2f refers to an absolute threshold. For CPICH Ec/No based event, the configuration of this parameter is set to the value of the parameter cpichEcNoThresholdUsedFreq2F which is a hysteresis to cpichEcNoThresholdUsedFreq2D. For CPICH RSCP based event, the configuration of this parameter is set to the value of the parameter cpichRscpThresholdUsedFreq2F which is a hysteresis to cpichRscpThresholdUsedFreq2D. H2d and H2f refer to as hysteresis parameters. They can be set to the value of hysteresis2D and hysteresis2F. (Note: For UA06 refer to section 6.3) Qused refers to as the quality of the currently used frequency. This is defined by:
NA QUsed = W 10 Log M i + (1 W ) 10 LogM Best i =1

W is set to 0, so that QUsedn actually refers to as CPICH Ec/No or CPICH RSCP of the best cell in the active set, depending on 2D and 2F measurement result configuration.
In order to trigger a report, the triggering condition has to be valid for a period of time named time to trigger. This parameter is configurable for each event (the values sent to the UE are defined by the parameters timeToTrigger2D, timeToTrigger2F).
At the end, the list of configured events for alarm handover activation would be as follows (for 2D and 2F, there is no triggering condition. By default, any of the active set cells may trigger the event):
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 160/213
UMTS Radio Mobility

Reporting quantity CPICH RSCP CPICH RSCP CPICH Ec/No CPICH Ec/No Event id 2D 2F 2D 2F
ALGORITHM
The Alarm criteria may be set by: Event 2D and 2F
Event 2D and 2F are managed the following way: The algorithm used to trigger alarm measurements will be based on the following principles: On reception of 2D event the RNC starts a timer. If the timer elapses until 2F is received, Alarm measurements are configured. If 2F is received while the timer is running, the timer is stopped. Use of event time to trigger parameter, so that the event is only reported once 2D or 2F is valid for a certain period of time.
CPICH Ec/No 2F 2D Long Time To Trigger
2D sent 2F 2D
HO decision
Short Time To Trigger

Figure 68: influence of short & long time to trigger
The figure above illustrates a cell edge case where the measurement quantity fluctuates around 2D and 2F triggering thresholds, as observed from the field: In case of long Time To Trigger, event 2D may possibly not be reported, as the condition is evaluated over a long period of time Short Time To trigger (around 100 to 300ms) allows much faster detection. In order to avoid unnecessary activation, Alarm criteria is only considered valid once a certain period of time has elapsed without receiving 2F. Short Time To Trigger values are preferred to ensure better network reactivity under alarm conditions As a consequence, a time window solution needs to be implemented at the RNC side, for event confirmation.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 161/213
UMTS Radio Mobility
The following algorithm will be used: 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). If another subsequent 2D event with another measurement quantity is received, the timer shall continue and the RNC stores that both quantities fulfils their triggering condition The timer timerAlarmHOEvent2D is stopped if a 2F event corresponding to the triggering 2D is received. In case both quantities (RSCP and Ec/N0) have fulfils their triggering condition, the timer is stopped if both 2F corresponding events are received (Ec/N0 and RSCP). A change of primary (event 1D) received while the timer is running has no effect on the algorithm, except the case when the new primary has different thresholds than the previous primary cell in which case the 2D/2F events are modified with the new thresholds Once the timer timerAlarmHOEvent2D elapses, the RNC activates Alarm measurement based on periodical reporting, depending on neighbouring cell configuration. After the timer expiration and alarm measurement is setup, if the alarm criteria becomes invalid (i.e. reception of one 2F event) before the alarm measurement results are received, the alarm handover procedure is cancelled and the alarm measurement results will be ignored when received. If the alarm criteria are again met a new alarm measurement (i.e. based on periodical reporting) will be setup again. The complete decision table for 2D CPICH Ec/No triggering event is described hereafter. Alarm criteria reflects the RNC decision once the timer has elapsed:
Triggering event 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 2F RSCP 2F Ec/No 2D RSCP 2D RSCP ; 2F Ec/No 2D RSCP ; 2F RSCP 2D RSCP ; 2F Ec/No ; 2F RSCP Timer decision table
Timer stopped? No No Yes No No No Yes
The alarm measurement activation is illustrated by the following picture:
Radio quality Threshold .

Alarm criteria Confirmation timer
time
2D received
Inter-frequency or inter-RAT configured
Figure 69: Alarm Measurement activation overview
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 162/213
UMTS Radio Mobility

MR 2D Timer elapses
2D
Event Trigger Mode
2D Timer
Wait for Inter Freq/Inter Rat meas
time HHO processing
Hard Handover Failure: If the mobile fails to synchronize to the target resource, a Hard Handover Failure message is sent to the SRNC, indicating the mobile has returned to the old channel. In such a case, in order to avoid too frequent handovers, the Alarm Criteria confirmation timer is started again.
If neighbouring measurement cannot be requested to the UE but Inter Rat HHO is allowed (for example: CM not possible with the current RAB, neighbouring cells filtered after applying IMSI criteria) or no suitable Alarm measurement is reported by the mobile within a guard timer period, a blind handover towards the blind GSM cell provisioned for the Primary cell may be performed by the RNC. When the Alarm HHO fails during preparation [USA Market - for all possible targets see section 4.10.4] or execution phase, the compressed mode pattern is deactivated and the Inter Rat or Inter freq measurements are removed and then: If the alarm criterion is still hit (no event 2F to cancel the event 2D during the HHO), in order to delay a new HHO attempt the Alarm confirmation timer is set with the value max (2D timer+TTT2D, 1800ms). At the timer expiration, measurements configuration and compressed mode activation are sent to the UE; If the alarm criterion is not hit anymore, the procedure ends.
CONFIGURATION
Regarding inter-frequency measurement, three different quantities are actually required: CPICH Ec/No: reported in events 2D, 2F CPICH RSCP: reported in events 2D, 2F So that two MEASUREMENT CONTROL messages are actually needed to configure inter-frequency events. As in [A4] specification, inter-frequency events reporting are not repeated. In order to limit the risk of loosing an event on the radio interface because of bad transmission conditions, all intra-frequency event reports are configured in RLC Acknowledged Mode. The overall structure of the inter-frequency MEASUREMENT CONTROL message is as follows.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 163/213
UMTS Radio Mobility
10.2.17 Meas. Control Common part (reporting type) 10.3.7.16 Inter-freq measurements Common part (meas quantities) 10.3.7.19 Inter-freq meas rep criteria Event 2D Event 2F
Figure 70: inter-frequency Measurement Control message structure

In the 10.2.17 common part: The IE Measurement reporting mode contains the specific information: Measurement Report Transfer Mode: Acknowledged mode RLC Reporting Mode: Event trigger In the 10.3.7.16 common part: Inter-frequency measurement quantity (10.3.7.18) Intra-frequency measurement quantity: CPICH Ec/No or CPICH RSCP Measurement quantity for frequency quality estimate: CPICH Ec/No or CPICH RSCP Inter-frequency reporting quantity (10.3.7.21) o For 2D/2F CPICH Ec/No (if measurement quantity is Ec/No) or CPICH RSCP (if the measurement quantity is RSCP)
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 164/213
UMTS Radio Mobility
2D EVENT CONFIGURATION
Information Element/Group name Parameters required for each event >Inter-frequency event identity >Threshold used frequency >W used frequency Need OP MP CVclause 0 CVclause 2 Parameter Value 2d Use cpichEcNoThreshold2D or cpichRscpThreshold2D parameter If isExtendedSrbDcch3dot4k = False: 0 If isExtendedSrbDcch3dot4k = True: Upper two Bits of hysteresis2D parameter with following mapping: 00 = 0.0 01 = 0.3 10 = 0.6 11 = 1.0 If isExtendedSrbDcch3dot4k = False: Use hysteresis2D parameter If isExtendedSrbDcch3dot4k = True: Lower two Bits of hysteresis2D parameter with following mapping: 00 = 0dB 01 = 1dB 10 = 2dB 11 = 3dB Use timeToTrigger2D parameter Use maxNbReportedCells2D parameter Not needed Not needed Not needed
>Hysteresis
MP
>Time to trigger >Reporting cell status >Parameters required for each non-used frequency >>Threshold non used frequency >>W non-used frequency
MP OP OP CVclause 1 CVclause 1
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 165/213
UMTS Radio Mobility
2F EVENT CONFIGURATION
Information Element/Group name Parameters required for each event >Inter-frequency event identity >Threshold used frequency >W used frequency Need OP MP CVclause 0 CVclause 2 Parameter Value 2f Use cpichEcNoThreshold2F or cpichRscpThreshold2F parameter If isExtendedSrbDcch3dot4k = False: 0 If isExtendedSrbDcch3dot4k = True: Upper two Bits of hysteresis2F parameter with following mapping: 00 = 0.0 01 = 0.3 10 = 0.6 11 = 1.0 If isExtendedSrbDcch3dot4k = False: Use hysteresis2F parameter If isExtendedSrbDcch3dot4k = True: Lower two Bits of hysteresis2F parameter with following mapping: 00 = 0dB 01 = 1dB 10 = 2dB 11 = 3dB Use timeToTrigger2F parameter Use maxNbReportedCells2F parameter Not needed Not needed Not needed
>Hysteresis
MP
>Time to trigger >Reporting cell status >Parameters required for each non-used frequency >>Threshold non used frequency >>W non-used frequency
MP OP OP CVclause 1 CVclause 1
Remark: In order to avoid event ping-pong effect, 2D and 2F need to be triggered by different conditions. This may be achieved through: Specific 2D and 2F thresholds (as in the tables above) Same thresholds, using a hysteresis different than 0. [Global Market: Parameter isExtendedSrbDcch3dot4k should be set to False] [USA Market: If parameter isExtendedSrbDcch3dot4k is set to True the WNMS parameters hysteresis2D and hysteresis2F have different semantics on the user interface (range 0dB to 7.5dB) and within the RNC. The RNC interprets two Bits of the value as hysteresis and the other two Bits as weight. For the parameter mapping refer to section 6.3. Note that the parameter isExtendedSrbDcch3dot4k was spare in UA06 and reused for this purpose; the parameter name does not reflect the actual semantics.]
5.9.4 PARAMETERS
Name timerAlarmHOEvent2D Object/Class UsHoConf Class3
UsHoConf Class3 UsHoConf Class3 MeasurementConfClass Class3
Definition Used for Alarm handover criteria in event-reporting mode. This timer is started on reception of 2D event. hysteresis for event 2D For UA06 refer to section 6.3. 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
hysteresis2D timeToTrigger2D
maxNbReportedCells2D
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 166/213
UMTS Radio Mobility

cpichEcNoThresholdUsedFreq2D cpichRscpThresholdUsedFreq2D hysteresis2F timeToTrigger2F
UsHoConf Class3 UsHoConf Class3 UsHoConf Class3 UsHoConf Class3
Specific CPICH Ec/No threshold specific to event Specific CPICH RSCP threshold specific to event hysteresis for event 2F For UA06 refer to section 6.3. 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)
maxNbReportedCells2F cpichEcNoThresholdUsedFreq2F
MeasurementConfClass Class3 UsHoConf Class3
cpichRscpThresholdUsedFreq2F
UsHoConf Class3
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 167/213
UMTS Radio Mobility
5.10. MEASUREMENTS CONFIGURATION FOR INTERFREQ/INTER-RAT 5.10.1 MEASUREMENT REPORTING

Periodic reporting is used in this version for Inter Frequency/GSM Inter-System measurements. The reporting period is 500 milliseconds. All the measured quantities will be reported by the mobile in the same measurement report message (Inter frequency/GSM Inter-System are additional measurements) when Intra Frequency measurements configuration is periodic. [Global Market - When Intra Frequency measurements configuration is event type, Inter Frequency/GSM Inter-System measurements are reported in periodic mode as main measurement configuration.] [USA Market - When Intra Frequency measurements configuration is event type and only one of both, Inter Frequency or GSM Inter-System measurements are used, then the measurement is configured as main measurement configuration in periodic mode.] [USA Market - When Intra Frequency measurements configuration is event type and both, Inter Frequency and GSM Inter-System measurements are used, then the Inter Frequency measurement is configured as main measurement in periodic mode and the GSM measurement is configured as additional measurement of the Inter Frequency measurement.] The list of neighbour cells to be monitored is given by the iMCTA function. The neighbor cells are selected among the neighboring cells of the primary cell. When an update of the neighbour list has to be sent to the UE, it only includes the cells to be removed and to be added (delta between the previous neighbouring and the new neighbouring).
5.10.2 REPORTED CELLS

In this release, the UE is requested to report up to 6 neighbouring cells amongst the monitored set. The 6 cells may be either inter-frequency or GSM inter-system neighbouring cells. The monitored set is defined as the set of inter-frequency or GSM neighbours of the primary cell and is provided to the UE through a MEASUREMENT CONTROL message first time the measurement condition is fulfilled and on modification of monitored set. For more details on the primary cell determination, please refer to the section 5.4.
5.10.3 CONFIGURATION FOR INTER-SYSTEM MEASUREMENTS

The SRNC requests the following quantities to be reported by the mobiles: GSM Carrier RSSI: Received Signal Strength Indicator on a GSM BCCH carrier Observed time difference to GSM cell (for observation only) Verified BSIC (this option is required to avoid the mobile reporting GSM measurement for which the BSIC is not identified. Otherwise, depending on the GSM reuse pattern and the radio condition, this might increase the risk of handover failure) L3 filtering is applied in the UE for each measurement, as specified in [A4], and as described in the section 5.11. 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. 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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 168/213
UMTS Radio Mobility

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.
5.10.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 5.11. 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.
5.10.5 CHANGE OF MEASUREMENT TYPE

[GLOBAL MARKET]
Following a change of primary, it may happen e.g. that inter-frequency measurements are requested whereas inter-system GSM measurements were reported by the UE, as a result of the following sequence: The Measurement Criteria is verified, and the mobile is reporting GSM measurements, as the primary neighbouring list contains 2G cells The primary cell changes, and the new neighbouring list does not contain 2G cells anymore. However, 3G cells from another frequency are now in the neighbouring list The Measurement Criteria is still valid, but Measurement Type has changed. The mobile is now requested to report inter-frequency measurements instead of inter-system GSM measurement The next figure illustrates the change of Measurement Type in the "measurement validity" process: M1 and M2 measurements are considered as valid until the change of Measurement Type, due to a change of the primary cell Until M3 is received, no measurement shall be regarded as valid
a CM active period CM activation CM re-activation CM stopped
...
Measurement report received M2 Measurement validity: M1

Change of Alarm Measurement Type
M3
M4
Figure 71: change of measurement type
[USA MARKET]
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.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 169/213
UMTS Radio Mobility

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.
5.10.6 PARAMETERS FOR MEASUREMENT

MEASUREMENT ACTIVATION PARAMETERS
The following parameters are used when the HHO reason is an alarm reason.
Name
Object/Class
FastAlarmHardHoConf per UsHoConf Class 3
cpichEcNoThreshold
cpichRscpThreshold
counter
StepDown
fastAlarmHHOTimeFilter per UsHoConf Class 3
StepUp
fastAlarmHHOTimeFilter 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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 170/213
UMTS Radio Mobility
OTHER PARAMETERS
The following parameters are used whatever the HHO reason.
Name
Object/Class
InterFreqMeasConf Class3 RRCMeasurement Class3 RRCMeasurement Class3 RadioAccessService Class3 RadioAccessService Class 3
interFreqFilterCoeff rrcGsmMeasurementFilterCoefficient rrcIntraFreqMeasurementFilterCoeff isBlindHoRescueAllowed measurementGuardTimer2g
measurementGuardTimerFdd
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.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 171/213
UMTS Radio Mobility
5.11. INTRA-FREQUENCY MEASUREMENTS 5.11.1 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)
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.
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.
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)
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 172/213
UMTS Radio Mobility
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 5.15 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). Note: If Detected Set cells are reported the RNC will trace this as specified in [R5]. Based on traces the neighbouring provisioning may be modified.
FILTERING
As specified in 25.331, L3 filtering is applied in the UE for the following measurements: CPICH Ec/No CPICH RSCP UE transmitted power The filtering algorithm is as follow:
Fn = (1 a ) Fn1 + a M n
with: Fn is the updated filtered measurement result Fn-1 is the old filtered measurement result. In order to initialise the averaging filter, F0 is set to M1 when the first measurement result from the physical layer measurement is received Mn is the latest received measurement result from physical layer measurements. a = 1/2(k/2), where k is the parameter received in the IE "Filter coefficient" in the Measurement Control message and in SIB11/SIB12 (if used). If k is set to 0 that will mean no layer 3 filtering. A specific value of k is provided for each of the measurement quantities, as an operator parameter. No additional filtering is applied by the SRNC.
5.11.2 MISSING MEASUREMENTS

When periodic measurements are reported, the RNC implement a specific process in order to cope with missing measurements for a given cell. The reason for this may be e.g. mobile limitation, or radio interface variation which may cause a cell not be reported for some period of time. This process only applies to intra-frequency measurements, for cells being part of the active set. The algorithm is as follows: Lets call (cell,N) the missing measurement : the counter of consecutive missing measurements for this cell is incremented if the counter value is above maxAllowedNumber, the measurement for this cell is replaced by a minimal default value, used with a minimal coefficient in computations. This until the measurement is received again. else, the measurement is substituted by quantity (cell, N-1) missedPenalty (there exists one penalty value for each CPICH RSCP and Ec/No reporting quantity) Note: A similar algorithm is applied to inter-frequency and inter-RAT measurements, too.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 173/213
UMTS Radio Mobility

The corresponding parameters are:
Name
Object/Class
MissingMeasurement Class3
maxAllowedNumber
missedEcNoMeasurementPenalty missedRscpMeasurementPenalty
MissingMeasurement Class3 MissingMeasurement Class3
Definition Maximum number of allowed missing measurements in the message RRC Measurement Report for a cell of the monitored set. Penalty coefficient which is subtracted to the last received CPICH Ec/N0 measurement to replace a missing one. Penalty coefficient which is subtracted to the last received CPICH RSCP measurement to replace a missing one.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 174/213
UMTS Radio Mobility
5.12. COMPRESSED MODE 5.12.1 INTRODUCTION

The compressed mode is used to allow a UE in FDD in dedicated mode to make measurements on a UTRA cell (either FDD or TDD) or on another Radio Access Technology (RAT), such as GSM, as part of the handover preparation. Measurement on a UTRA FDD cell is referred to as inter-frequency measurement and measurement on a UTRA TDD cell or a GSM cells is referred to as intersystem measurement. The compressed mode involves interrupting the transmission in the uplink or downlink, or possibly both at the same time, for short amounts of time (less than one 10 ms radio frame) in a regular manner to allow the mobile to perform the requested measurements. Any transmission interruption time, called a transmission gap, may be contained within one radio frame or span the boundary between two radio frames such that the transmission gap does not exceed half of the period of any one radio frame (10 ms). In this version of the document compressed mode is either used when needed for GSM or FDD inter-frequency measurements] [Global Market - compressed mode cannot be used for GSM and FDD measurements simultaneously] compressed mode is used for all kind of CS or PS services, without discrimination.
5.12.2 UE CAPABILITY
The real need for compressed mode is indicated by the mobile in the UE Radio Access Capability information element, provided in the RRC CONNECTION SETUP COMPLETE message. This information element is sent on network request ("GSM capability required" indication in the RRC Connection Setup message sent from the network).
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. RNC
...
Figure 72: Retrieving UE capability

In the UE Radio Access capability, the mobile indicates if compressed mode is needed in either UL or DL for the following modes: FDD GSM450 GSM480 GSM850 GSM900P GSM900E GSM900R GSM1800 GSM1900 All FDD R7 frequency bands capabilities are used by the RNC. The UTRAN supports: all FDD R7 frequency bands except the band IV; the mobility between these bands except between band I and band II;
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 175/213
UMTS Radio Mobility
Inter Rat handover from/towards theses bands.
The UE Radio Access capability information is used by the network to configure and activate compressed mode in 3 possible ways: for the uplink only for the downlink only for both In the paragraph on "procedures & messages", and as specified in 3GPP documents, it is explained that compressed mode configuration is done very early in the call process, and that compressed mode is only activated when needed.
Regarding compressed mode for GSM, in order not to configure compressed mode in every case, a set of flags indicating the frequency band of the GSM neighbouring cells will be defined and used in the RNC to determine whether or not compressed mode is needed, and for which direction. The list of flags is the following: GSM450present GSM480present GSM850present GSM900Ppresent GSM900Epresent GSM900Rpresent GSM1800present GSM1900present
Each flag indicates that there exists at least a GSM cell of the corresponding frequency band in the access network (i.e. not only being part of the GSM neighbouring lists seen by the RNC) to which handover from a 3G cell is supported by the network. Therefore, if compressed mode is needed by the mobile for that frequency band it will be configured accordingly and possibly activated by the network if the measurement request concerns at least a neighbour cell of that band.
5.12.3 METHOD
There exist 3 methods for compressed mode: Puncturing: transmission gaps are created by performing additional puncturing or fewer repetitions in rate matching compared to normal mode so that the bit rate resulting from the rate matching can be accommodated within the transmitted slots. This is a DL only method. Higher Layer Scheduling: transmission gaps are created by restricting the TFC in the TFCS. This implies that the transport channel can cope with some transmission delay. Therefore this method is not applicable to conversational services. This method is applicable to both UL and DL. SF reduction: the spreading factor of the compressed radio frames is divided by two, allowing the same number of bits to be sent in a smaller amount of time. This method is applicable to both UL and DL. NOTE: puncturing method removed from 3GPP since R5, Compressed mode will be using the following method: 1) SF/2 reduction method 2) Higher Layer Scheduling (HLS) method SF reduction and HLS methods can be configured in the UL or DL, or possibly both, for GSM or FDD inter-frequency measurements. The use of the SF/2 reduction method has an impact on the Scrambling and OVSF code used. This is further detailed in the chapter about "impacts on RRM" (see 5.12.8).
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 176/213
UMTS Radio Mobility
5.12.4 MEASUREMENT PURPOSE

Compressed mode makes use of pattern sequences, each of them being associated to a measurement purpose. The defined measurement purposes are applicable whatever the compressed mode method is (SF/2, HLS). The same CM pattern definition is used whatever the method is. A pattern sequence is composed of 2 pre-defined patterns (pattern 1 and pattern 2) being used alternatively, as in the figure below. A sequence may have a finite or infinite value depending on the TGPRC parameter. In principle, each pattern sequence is dedicated to a certain measurement quantity, so that, the network shall configure as many pattern sequences as measurement quantities to be reported by the mobile.
#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 73: Compressed Mode pattern sequence overview
GSM MEASUREMENTS
Regarding GSM measurements, there may be up to 3 pattern sequences needed, depending on the "measurement purpose": RSSI measurements Initial BSIC identification BSIC re-confirmation In order to illustrate how the 3 measurements types are performed in the mobile, the following figure presents an overall view of compressed mode processes for GSM in the mobile, as specified in 25.133. The mobile is provided with GSM neighbouring cell list, contained in the Measurement Control RRC message. The "RSSI measurement process" can be seen as a sort of endless loop, intending to identify the 8 strongest cells. The "Initial BSIC identification process" intends to identify the BSIC in the list. Once being successfully identified, the BSIC is given to the re-confirmation process. The "BSIC re-confirmation process" can be seen as a sort of endless loop, intending to re-confirm identified BSIC, and maintain timing information with the identified cells.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 177/213
UMTS Radio Mobility
Measurement Control
(BSIC, 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 74: UE process overview for GSM measurements
FDD INTER-FREQUENCY MEASUREMENTS

Regarding FDD inter-frequency measurements, only one pattern sequence is needed as there is only one "measurement purpose": FDD measurement
5.12.5 PATTERN SHAPE

GSM MEASUREMENTS
In this version, for GSM measurements, Alcatel-Lucent UTRAN implements 2 finite length patterns: one for GSM RSSI measurements one for BSIC identification No pattern sequence for "BSIC reconfirmation" will be activated. The 2 patterns have finite duration (i.e.: TGPRC=1 to 511), and are not running in parallel (i.e. the pattern for BSIC identification is only started once the pattern for RSSI is over). An example for such a configuration is presented in the figure below:
x frames
y frames
... CFN RSSI ... CFN +x BSIC Identification
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 178/213
UMTS Radio Mobility

Figure 75: Pattern sequences for GSM measurements
Once RSSI measurements are performed, the mobile should normally attempt to identified the 8 strongest RSSI, using the relevant pattern sequence. Once BSIC have been identified and reported to the network, the network may possibly make a handover decision toward a GSM target. Please refer to the chapter on [parameters] for the pattern parameters supported in this version.
FDD INTER-FREQUENCY MEASUREMENTS

In this version, for FDD inter-frequency measurements, Alcatel-Lucent UTRAN implements a finite length pattern, as in the figure below.
x frames
... CFN FDD measurement
Figure 76: Pattern sequence for FDD measurements

Please refer to the chapter on [parameters] for the pattern parameters supported in this version.
5.12.6 SLOT FORMATS/ FRAME STRUCTURE

According to 25.211 section 5.3.2 Dedicated downlink physical channels, in compressed frames, a different DPCH slot format is used compared to normal mode. There are two possible compressed slot formats (labeled A & B). The selection between them is dependent on the used method: DL Slot format B shall be used in frames compressed by SF reduction, DL Slot format A shall be used in frames compressed by HLS, Same Transmission gap position calculation used for SF/2 and for HLS compressed mode method. Frame structure type A and Type B shall be supported by the UTRAN.
5.12.7 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.e. when the RAB ASSIGNMENT REQUEST message is received from the Core Network). A reconfiguration of the compressed mode may occur when a CM method change is needed, e.g. due to additional RAB setup or RAB deletion. activation/deactivation is based on a separate criteria, i.e. when the iMCTA function needs measurement for HHO processing for Alarm, CAC or Service reason.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 179/213
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, CM config for GSM, CM config for FDD) NBAP/ Radio Link Reconfiguration Response NBAP/ Radio Link Reconfiguration Commit (no pattern active) RRC/ RB Setup (DTCH config, CM config for GSM, 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, starting CFN) RRC/ Measurement Control (active pattern, starting CFN)
Criteria is reached => CM re-activation
NBAP/ Compressed Mode Command (active pattern, starting CFN) RRC/ Measurement Control (active pattern, starting CFN)
Figure 77: Compressed Mode activation
RRC/RB SETUP MESSAGE

This message contains the CM configuration, which will be possibly be activated by the RNC when the criteria is reached. It contains the following information:
10.2.33 RB Setup 10.3.6.24 Downlink information common for all radio links 10.3.6.33 DPCH compressed mode info
TGPSI TGPS Status Flag TGCFN TGMP TGPRC TGSN
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 180/213
UMTS Radio Mobility

TGL1 TGL2 TGD TGPL1 TGPL2 RPP ITP UL/DL mode Downlink compressed mode method Uplink compressed mode method Downlink frame type DeltaSIR1 DeltaSIRafter1 DeltaSIR2 DeltaSIRafter2 N Identify abort T Reconfirm abort
10.3.6.27 Downlink information for each radio link 10.3.6.21 Downlink DPCH info for each RL
Scrambling code change
RRC/RB RECONFIGURATION MESSAGE

This message is used to reconfigure the compressed mode (used to change the method). The same IEs are used as for initial CM configuration in RB Setup message see above.
RRC/MEASUREMENT CONTROL MESSAGE

This message is used to trigger/stop compressed mode pattern sequences.
10.2.17 Measurement Control 10.3.6.34 DPCH compressed mode status info

TGPSI TGPS Status Flag TGCFN
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.
9.2.1.42 Radio Link Reconfiguration Prepare 9.2.2.14A DL code information 9.2.2.53B Transmission Gap Pattern Sequence Code Information
Scrambling code change
9.2.2.57 UL DPCCH Slot Format 9.2.2.10 DL DPCH Slot Format 9.2.2.53A Transmission Gap Pattern Sequence Information
TGPSI TGSN
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 181/213
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
NBAP/COMPRESSED MODE COMMAND MESSAGE

9.1.60 Compressed Mode Command 9.2.2.A Active Pattern Sequence Information
CM activation
Presence M Range
0.. <maxTGPS>
IE/Group Name CM Configuration Change CFN Transmission Gap Pattern Sequence Status >TGPSI Identifier >TGPRC >TGCFN
Type and reference CFN group present (range > 0)
M M M
CFN
CM deactivation
Presence M Range Type and reference CFN
IE/Group Name CM Configuration Change CFN
[Global Market - The measurements are not activated in parallel. Each GAP sequence is activated sequentially at a specified TGCFN time per measurement purpose. It means the 3 GAP pattern are not running at the same duration period.]
NBAP/RADIO LINK RECONFIGURATION COMMIT MESSAGE

9.1.60 Compressed Mode Command 9.2.2.A Active Pattern Sequence Information Same structure as above.
RNSAP/RADIO LINK SETUP/ADDITION REQUEST MESSAGE

This message is used in case of inter-RNC soft handover. The main difference with equivalent message used on the Iub interface (NBAP Radio Link Reconfiguration Prepare message) is that the "code information" (i.e. whether or not the alternate scrambling is used) is not indicated in the RNSAP, so that the choice is left to the DRNC. Aside from this very specific point, the DRNC applies the same configuration as the SRNC in terms of pattern definition and Power control.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 182/213
UMTS Radio Mobility
9.1.3.1 Radio Link Setup Request or 9.1.6 Radio Link Addition Request 9.2.2.A Active Pattern Sequence Information
TGPSI TGCFN TGPRC
9.2.2.47A Transmission Gap Pattern Sequence Information

TGPSI TGSN TGL1 TGL2 TGD TGPL1 TGPL2 UL/DL mode Downlink compressed mode method Uplink compressed mode method Downlink frame type DeltaSIR1 DeltaSIRafter1 DeltaSIR2 DeltaSIRafter2
RNSAP/COMPRESSED MODE COMMAND MESSAGE

This message is used to trigger/stop compressed mode pattern sequences. Its format is equivalent to the message used on the Iub.
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.
5.12.8 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. These impacts are described in what follows. For DL transmission in uncompressed frames, the network is using scrambling code SC OVSF code Cch,SF,n For DL transmission in compressed frames, Alcatel-Lucent UTRAN is using the alternate scrambling method, which makes use of 2 additional scrambling codes, as specified in 25.213, 5.1.2 and 5.2.2: SC+8192 SC+16384 Depending on the position of the OVSF code Cch,SF,n in the code tree, either the 1st or the 2nd alternate is used: if (n<SF/2), SC+8192 is used if (n>=SF/2), SC+16384 is used In both cases, the OVSF code which is used for compressed frames is Cch,SF/2,n mod SF/2
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 183/213
UMTS Radio Mobility
Scrambling code = SC
LEFT case
Scrambling code = SC +8192
SF-1
SF/2
SF-1
SF/2
Scrambling code = SC
Scrambling code = SC +16384
RIGHT case
SF-1
SF/2
SF-1
SF/2
Figure 78: 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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 184/213
UMTS Radio Mobility
5.12.9 HLS
[USA Market: HLS method is supported in uplink, only. I.e. dependent on the uplink bearer combination SF/2 or HLS can be used. In downlink SF/2 method is available, only.]
This chapter describes the Compressed Mode by HLS over dedicated physical channel. The gain of the HLS CM method is Does not require additional resources: o No additional power is requested for transmission at same level of protection of the user bit o No additional OVSF resources allows removal of the interference impact created by the SF/2 and thus allows increase of the overall cell capacity allows the support of RB with SF=4 obviously, avoids SF change and any new requirements for channelisation code usage DL HLS is less stringent in CEM processing capacity requirement than SF/2 Such method can be configured as the following ones: compressed mode is used when needed for GSM or FDD inter-frequency measurements [Global Market - compressed mode cannot be used for GSM and FDD measurements simultaneously] compressed mode by SF/2 reduction may be used for all kind of CS or PS services, compressed mode by SF/2 reduction method is possible for both UL and DL whenever GSM or FDD inter-frequency measurements is used, compressed mode by HLS is used for UL/DL PS I/B mono/multi services over DCH, compressed mode by HLS is used for UL/DL multiplexed PS I/B services over DCH, compressed mode by HLS is also used for certain multiplexed PS I/B + CS services see below. compressed mode method by HLS or SF/2 can be used in mixed CM method UL/DL (ex. UL HLS and DL SF/2) whatever the measurement purpose is.
HLS ASSUMPTIONS
In most of the cases, only one method (either HLS or SF reduction) may be active at a time For some specific configurations SF reduction may apply in DL whereas HLS applies in UL Compressed mode (SF/2 or HLS) is active in Cell-DCH mode only, Compressed mode (SF/2) is active with HSDPA, CMode method only applies to the DCH part of a call and not to HS-DSCH, as a consequence the associated DCH (ie SRB only) uses SF/2 for any such configuration, Compressed mode (SF/2) is active with HSUPA CMode method only applies to the DCH part of a call and not to the E-DCH part, Standalone SRB configuration: o Design choice: HLS is not applied to Standalone SRB configurations in order to keep the SRB capacity Mono-service handling: o HLS is not supported for any CS only call o HLS is not supported for PS Streaming only call o HLS is not supported for CSD64 only call o HLS is supported in both UL & DL for PS I/B x/y only call over DCH, with x/y > 8 kbps o If PS I/B only traffic is carried by DCH/HS-DSCH channel then only the SF/2 method is supported in DL whereas the HLS method is supported in UL Multi-service handling: o HLS is supported in UL/DL for multi-service calls involving a CS call: SRB + CS Speech + PS I/B x/y over DCH with x/y > 8 Kbps, Only the PS I/B TF(s)/TFC(s) are restricted during transmission with gap, o HLS is not supported for multi-service calls involving a PS Streaming session excepted if that RB combination gets a SF equal to 4 and the GBR is guaranteed, o HLS is not supported in UL for multi-service calls involving a CSD call excepted if that RB combination gets a SF equal to 4, o HLS is supported for multiplexed PS I/B x/y calls with x/y > 8 Kbps,
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 185/213
UMTS Radio Mobility

o HLS can be applied to SRB + PS Streaming + PS I/B provided the streaming GBR while compressed frames is guaranteed, 3GPP baseline is R6 UE capability o Any UE is supposed to support HLS (3GPP mandatory feature for UE) o Some UEs do not require compressed mode to perform their inter-frequency or inter-RAT measurements, while other require the compressed mode to be activated either in UL or DL only or in both UL and DL. o UE capability analysis performed by the RNC is not impacted by the introduction of the HLS compressed mode, same UE capabilities filtering algorithm is applied,
HLS GAP PATTERN CONFIGURATION

Compressed Mode configuration management: o The same CM patterns will be used for both HLS & SF/2 methods, refer to 5.12.5. o When compressed mode is activated, as per [25.211], slot format A applies to compressed mode by HLS whereas slot format B applies to compressed mode by SF reduction Transmission over DL DCH shall be optimized while CM by HLS is active: o As per 3GPP spec, the max ratio of compressed frames is 2/3. With the current CM pattern, the ratio is 1/3 [USA Market - in case of single 2G or 3G measurement and 2/3 in case of simultaneous 2G and 3G measurement.] o Some TF/s on PS RAB only are forbidden for TTIs where transmission with gap is performed o E.g. for a DL transmission with TTI = 10ms, assuming that the CM pattern configuration is as described in section, 5.12.5. TFS reduction will only apply during 2 or 4 TTIs every 6 TTIs.
SWITCHING BETWEEN COMPRESSED MODE METHODS

The system shall be able to switch to the most appropriate method after a RAB combination modification, i.e. Whenever a CM method change occurs in UL or DL or both the following applies: o While SRLR the previous CM method is deactivated at CFN#1, o When SRLR ends the new CM method is configured and activated at the CFN#2 time, => For the specific case where the PS I/B would be supported by UL DCH / HS-DSCH transport channels, HLS would apply in the UL direction, while the SF/2 method would apply in the DL direction. Hereafter the impacted RRC/NBAP/RNSAP messages used on the different transition use cases below:
NBAP/RNSAP RL SETUP Request (RBs + CM parameters) // CM configuration provisioning // + start CM at TGCFN time NBAP/RNSAP RL RECONFIGURATION PREPARE (RBs + CM parameters) // CM configuration provisioning NBAP/RNSAP RL RECONFIGURATION COMMIT () NBAP/RNSAP COMPRESSED MODE COMMAND ()
// CM configuration provisioning // + start CM at TGCFN or CFN time // start CM at TGCFN or CFN time // stop CM configuration change // CFN time // configuration + Start/Stop CM // at TGCFN time for each // TGPSI
RRC RADIO BEARER SETUP (RBs + CM parameters)
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 186/213
UMTS Radio Mobility

RRC RADIO BEARER RECONFIGURATION (RBs + CM parameters) // configuration + Start/Stop CM // at TGCFN time for each TGPSI RRC MEASUREMENT CONTROL ()
// Start/Stop CM at TGCFN time // for each TGPSI
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, CM config for GSM, 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, starting CFN: TGCFN time) RRC/ Measurement Control (active pattern, starting CFN: TGCFN time) NodeB compares the CFN of DL FP DCH frames to TGCFN to trigger CM activation 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, 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, 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, for FDD, New CM configuration/method, CM activation at new CFN: TGCFN time ) RRC/ RB Reconfiguration complete (DTCH config, for FDD) RANAP/ RAB Assignment Response
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 187/213
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, CM config for GSM, 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, starting CFN: TGCFN time) NodeB compares the CFN of DL FP DCH frames to TGCFN to trigger CM activation RRC/ Measurement Control (active pattern, starting CFN: TGCFN time) RNC MSC-CS
CM ends normally at a finite time,
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, New CM configuration/method) NBAP/ Radio Link Reconfiguration Response NBAP/ Radio Link Reconfiguration commit ( no Pattern active) RRC/ RB Reconfiguration (DTCH config, for FDD, New CM configuration/method, no pattern active ) RRC/ RB Reconfiguration complete (DTCH config, for FDD) 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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 188/213
UMTS Radio Mobility
CM METHOD SELECTION RULES:

1. SF/2 selection method rules:
A - SF/2 is the default CM method applicable to all CS NB/WB/CSD mono RB on DCH B - SF/2 is the default CM method applicable to all PS streaming mono RB on DCH excepted when SF equal 4 C - SF/2 is the default CM method applicable to all CS NB/WB + PS streaming RB(s) on DCH D - SF/2 is the default CM method applicable to all CS NB/WB + PS streaming RB(s) + I/B on DCH E - SF/2 is the default CM method applicable to all RB combination over HSDPA/HSUPA F - SF/2 is the default CM method applicable to multiple PS I/B x/y + PS Streaming u/p RB over DCH excepted for rates with x/y >= 64 and u/p >= 64 Kbps G - SF/2 is the default CM method applicable to SRB Standalone combination
2.
HLS selection method rules:

A - HLS is the default CM method applicable to PS I/B x/y mono/multiplexed RB on DCH, excepted for I/B 8 Kbps B - HLS is the default CM method applicable to all CS NB/WB + PS I/B x/y combination on DCH, with x/2 & y/2 SRB max rate + AMR max rate (excepted for CS NB/WB + PS I/B 8/16 Kbps) C - HLS is the default CM method applicable to all CSD 64 + PS I/B x/y mono/multiplexed RB over DCH, with x/2 & y/2 > 64 Kbps D - HLS is the default CM method applicable to PS I/B x/y + PS Streaming u/p RB over DCH, with SF = 4, HLS is the default CM method applicable to multiple PS I/B x/y + PS Streaming u/p RB over DCH only for x/y >= 64 and (u/p > 64 and u/p <384Kbps), and x/y GBR E - HLS is the default CM method applicable to CS NB/WB PS I/B x/y + PS Streaming u/p RB over DCH, with SF = 4, HLS is the default CM method applicable to multiple CS NB/WB PS I/B x/y + PS Streaming u/p RB over DCH only for x/y >= 64 and (u/p > 64 and u/p <384Kbps), and x/y GBR F - SRB + CS Streaming u/v + PS I/B x/y for cases the allocated Ul/DlAsConf supports SRB max rate + u/v + x/y, with x/2 & y/2 SRB max rate + u/v kbps and x/2 & y/2 GBR only the TFS for PS I/B are restricted during transmission with gap G - RB combination SF 4 based: HLS is the default CM method applicable to any RB combination if defined with a SF equal to 4
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 189/213
UMTS Radio Mobility

COMPRESSED MODE METHOD PER RADIO BEARER COMBINATION: CM method rules For the UL: Following table gives the Ul AsConfs for which the default value of class 3
isHlsCmMethodPreferred parameter in MIB is YES
(*) Ul AsConfs Default value of isHlsCmMethodPreferred MIB value = YES Id

0 3 8 10 20 21 22 26 27 28 29 30 42 43 30 58 60 61 62 63 64 80 85 90 91 94 95 96 101 105 106 148 149 152 157 158 160 161 164 165 166 167
SRB
SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB SRB
Traffic1
PS I/B 64 PS I/B 32 CS NB AMR PS I/B 128 PS I/B 64 Mux CS NB AMR PS I/B 384 PS I/B 128 Mux CS NB AMR CS NB AMR CS NB AMR CS NB AMR CSD 64 CSD 64 CSD 64 CS WB AMR CS WB AMR CS WB AMR CS WB AMR CS WB AMR CS WB AMR PS STR 16 PS STR 32 PS STR 64 PS STR 64 PS STR 128 PS STR 128 PS STR 128 CS NB 12.2 CS NB 12.2 CS NB 12.2 CSD 64 with 3 subflows CSD 64 with 3 subflows CSD 64 with 3 subflows PS 2 I/B 32 Mux PS 2 I/B 384 Mux CS NB AMR CS NB AMR PS 3 I/B 32 Mux PS 3 I/B 64 Mux PS 3 I/B 128 Mux PS 3 I/B 384 Mux
Traffic2
Traffic3
isHlsCmMethod Preferred
Yes Yes
PS I/B 64
Yes Yes Yes
PS I/B 64 Mux
Yes Yes (SF4*) Yes
PS I/B 128 Mux PS I/B 32 PS I/B 128 PS I/B 384 PS I/B 128 PS I/B 384 PS I/B 128 mux I/B 64 I/B 32 I/B 128 I/B 384 I/B 64 MUX I/B 128 MUX I/B 384 I/B 384 I/B 128 I/B 384 I/B 64 I/B 128 I/B 384 PS STR 16 PS STR 32 PS STR 32 PS I/B 128 PS I/B 384 PS I/B 128 Mux PS I/B 384 PS I/B 128 PS I/B 384
Yes Yes Yes Yes (SF4*) Yes Yes Yes (SF4*) Yes Yes Yes Yes Yes Yes Yes (SF4*) Yes (SF4*) Yes (SF4*) Yes (SF4*) Yes (SF4*) Yes (SF 4) Yes (SF4*) Yes (SF4*) Yes (SF4*) Yes (SF4*) Yes (SF4*) Yes (SF4*) Yes (SF4*) Yes Yes (SF4*)
PS 2 I/B 32 Mux PS 2 I/B 384 Mux
Yes Yes (SF4*) Yes Yes Yes (SF4*) Yes (SF4*)
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 190/213
UMTS Radio Mobility

170 171 172 173 184 187 SRB SRB SRB SRB SRB SRB CS NB AMR CS NB AMR CS NB AMR CS NB AMR PS STR 128 CS NB AMR PS 3 I/B 32 Mux PS 3 I/B 64 Mux PS 3 I/B 128 Mux PS 3 I/B 384 Mux PS 2 I/B 64 Mux PS STR 128 PS 2 I/B 64 Mux Yes Yes Yes (SF4*) Yes (SF4*) Yes (SF4*) Yes (SF4*)
For the DL: Following table gives the Dl AsConfs for which the default value of class 3
isHlsCmMethodPreferred parameter in MIB is YES
(**) Dl AsConfs Default value of isHlsCmMethodPreferred MIB value = YES Id

2 6 7 10 61 11 12 18 22 25 26 32 33 34 35 48 50 67 69 70 71 72 73 74 74 119 125 126 129 130 131
SRB
SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB 3.4 SRB SRB 3.4 SRB 3.4 SRB SRB SRB
Traffic1
PS I/B 64 PS I/B 128 PS I/B 384 CS NB AMR PS I/B 16 PS I/B 32 PS I/B 256 CS NB AMR CS NB AMR PS I/B 64 Mux CS NB AMR PS I/B 128 Mux PS I/B 384 Mux CS NB AMR CS NB AMR CS NB AMR CSD 64 CS WB AMR CS WB AMR CS WB AMR CS WB AMR CS WB AMR CS WB AMR CS WB AMR CS WB AMR CSD 64 with 3 subflows CSD 64 CSD 64 with 3 subflows PS 3 I/B 64 Mux PS 3 I/B 128 Mux CS NB AMR
Traffic2
Traffic3
isHlsCmMethod Preferred
Yes Yes Yes
PS I/B 64
Yes Yes Yes Yes
PS I/B 128 PS I/B 384 PS I/B 64 Mux
Yes Yes Yes Yes Yes Yes
PS I/B 128 Mux PS I/B 384 Mux PS I/B 32 PS I/B 128 PS I/B 64 PS I/B 128 PS I/B 32 PS I/B 384 PS I/B 64Mux PS I/B 128 Mux PS I/B 384 Mux PS I/B 384 Mux PS I/B 128 PS I/B 128 Mux PS I/B 128 Mux
Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes (SF4*)
PS 3 I/B 64 Mux
Yes
(SF4*): When a RB combination gets a SF=4 then RNC has the possibilities: o To apply the HLS method even through for PS streaming traffic, o To downgrade the granted rate of that RB combination with a greater SF
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 191/213
UMTS Radio Mobility
5.12.10
SRNS RELOCATION [GLOBAL MARKET]

Interaction with SRNS relocation (UE not involved).
- Incoming SRNS relocation with HLS compressed mode activated from a non Alcatel-Lucent SRNC: For an incoming SRNS relocation the DRNC shall apply the following:
If the the CM configuration checking indicates different CM configurations (CM configuration of the relocation container not the same than the one on DRNC), then: 1. The Target RNC shall stop the current CM at the UE/NodeB side for any active TGPS at the CM configuartion CFN time, 2. The target RNC is configured with its MIB compressed mode configuration/CM prefered method, There is no dynamical compressed mode configuration, since it may generate call drops, 3. The target DRNC shall start its CM at the new CFN time on the UE/NodeB side when the Alarm HHO criteria is met
See hereafter the call flow for that use case. Note: Sending the RRC measurement Ctrl to deactivate the initial compressed mode ensure a correct deactivation on UE side , in order to reduce some undecoded radio frame.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 192/213
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, CM config for GSM, 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, CM config for GSM, CM config for FDD, 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, starting TGCFN) RRC/ Measurement Control (active pattern, starting CFN= TGCFN)
5.12.11
RNS INTER-RELEASE COMPATIBILITY USE CASES
The DRNC does not perform any check regarding CM activation and the CM Configuration/method since the DRNC does only relay the CM method/configuration to the NodeB(s), But the SRNC shall apply a filtering based on the IsHlsCmAllowedOnDRNC parameter value to match the supported CM method supported on the DRNC side (SF/2 or HLS).
UA06.0 SRNC facing an oldest DRNC version:

- New parameter required in the NeighbouringRNC MO: IsHlsCmAllowedOnDRNC to be set to false when a SRNC faces a DRNC not supporting the HLS methods otherwise it is set to true. While CM activation:
1) When SRNC facing an oldest DRNC version and if the CM method in use is SF/2:
- The SRNC does not need to apply any particular action on its Iur interface, follow on of the SF/2 CM method/configuration with the same TGPS to the DRNC
2) When SRNC facing an oldest DRNC version and if the CM method in use is HLS:
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 193/213
UMTS Radio Mobility

- If IsHlsCmAllowedOnDRNC is equal to false then - For any RB combination to be supported on the SRNC/DRNC and the SF of the established combination is not equal to SF4: - SRNC shall apply a CM method switching from the HLS method to the SF/2 method in UL and/or DL before to transmit any RNSAP RL Setup/reconfiguration message, refer to the CM method switching procedure described above. - For any RB combination to be supported on the SRNC and DRNC and the SF of the current combination is equal to SF4: - No CM method change since a SF/2 CM method cannot be applied to a RB with an SF4. - In that case the SRNC shall still transmit RNSAP RL Setup/Reconfiguration to its DRNC. - As the NodeB is 3GPP compliant (SF/2 CM method not applicable to bearer with a SF = 4), the NodeB shall reject the incoming NBAP RL Setup/reconfiguration, - The NodeB answers by a NBAP RL Setup/reconfiguration failure message with the error cause set to CM not supported, - The DRNC relays the RL Setup/reconfiguration failure message through the Iur interface to its SRNC, - Upon reception of the RNSAP RL Setup/reconfiguration failure message:
o o
At this stage the SRNC shall distinguish for the RL failure case the cause error. The RNC shall interpret for such reported Iur RL failure cause CM not supported as an indication that any CM method can be supported for the current RB combination on that DRNC,
- Receiving the RNSAP RL failure the SRNC shall not attempt to retry a RNSAP RL Setup/reconfiguration.
Without CM activation: 3) When SRNC facing an oldest DRNC version and if the CM method to be used is SF/2: - No additional action, follow on of the CM method/configuration with the same TGPS, to the DRNC 4) When SRNC facing an oldest DRNC version and if the CM method in used is HLS: - Same case as 2) but without CM deactivation, See hereafter the call flow for that use case.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 194/213
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, New CM config./method,) NBAP/ Radio Link Reconfiguration Ready () NBAP/ Radio Link Reconfiguration Commit (CM configuration activation at TGCFN time ())
RRC/ RB Reconfiguration (DTCH config, for FDD, New CM configuration/method, CM activation at new CFN= TGCFN time ) RRC/RB Reconfiguration complete (DTCH config, for FDD) RNSAP/ Radio Link Setup Request (DTCH config, New CM config./method, TGCFN time )
SF/2 method selected on oldest NodeB version Transmission of the activation time: New TGCFN CM activation command to the Node B/UE
NBAP/ Radio Link Setup Request (DTCH config, New CM config./method, TGCFN time) NBAP/ Radio Link Setup Response () RNSAP/ Radio Link Setup Response ()
UA0x.x SRNC facing an UA06.0 DRNC version:

When facing an oldest version on its Iur interface the DRNC just relays the SF/2 CM method/configuration to the NodeB(s), nothing specific at this stage.
5.12.12
DRNS SCENARIOS
The DRNC does not perform any check regarding HLS activation and the AsConf. Similarly, the DRNC does not perform any check regarding the activation of different CM methods in UL & DL.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 195/213
UMTS Radio Mobility

ALU SRNC/ ALU DRNC: not ALU SRNC/ ALU DRNC (IOT use case)
1. CM not activated in the SRNC, No specific action required at the RNC/NodeB side. It corresponds to an existing use case, the SRNC configures the CM patterns as usual with the RRC measurement Ctrl message and with the NBAP/RNSAP RL Setup/reconfiguration messages and shall activate the CM when the RNC HHO alarm criteria are reached. 2. CM activated in the SRNC, No specific action at the RNC/NodeB side. It corresponds to an existing use case, the SRNC has configured the CM patterns as usual with the RRC measurement Ctrl message and with the NBAP/RNSAP RL Setup/reconfiguration messages and activated the CM when the RNC HHO alarm criteria are reached. When RL(s) is added on the DRNC, the DRNC relays the CM patterns to the dedicated NodeB. CM on DRNC side is activated at the correct TGCFN time. The TGCFN is the one calculated by the SRNC and shall ensure that the CM activation on DRNC is synchronised with the RL(s) established with the SRNC. For these use cases the DRNC does not need to check the CM method (for ALU SRNC/ ALU DRNC only). The DRNC and the Node B should accept any 3GPP compliant sequence or combination for compressed mode activation/deactivation for supported compressed mode methods.
ALU SRNC/ not ALU DRNC

1. If the CM is active and CM method in used is SF/2: The SRNC does not need to apply any particular action on its Iur interface, follow on of the SF/2 CM method with the same TGPS. 2. If the CM is active and CM method in used is HLS: - If IsHlsCmAllowedOnDRNC is equal to false then Same action shall be performed as for the RNS inter release case see 5.12.11 (CM method switching).
CM not supported on the DRNC side:

1. If the SRNC CM configuration is not supported by the DRNC, this last shall answer by a RNSAP RL Setup/Reconfiguation failure with the cause IE set to CM not Supported, The SRNC shall not intend to activate any CM on that radio link anymore,
2.
5.12.13
-
ALPHA CEM CARDS IMPACT

HLS method is not supported on alpha CEM card, A NodeB with alpha CEM cards inside will generate a RL SETUP/RECONFIGURATION FAILURE at the compressed mode activation, A RL establishment on a NodeB with alpha CEM cards inside cannot be activated with a HLS CM method. If the HLS method is configured and activated on a node alpha card base, a NBAP/RNSAP RL SETUP/RECONFIGURATION FAILURE is transmit to the SRNC. On reception of the NBAP/RNSAP RL SETUP/RECONFIGURATION FAILURE message the SRNC shall stop the HLS procedure,
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 196/213
UMTS Radio Mobility
5.12.14
UE IMPACTS
Independently of the different characteristic to assign to the UE for a SF/2 or HLS compressed mode method use and according the cell profile to be measured by the UE the 3GPP rules shall be supported on the UE side (refer TS 25.133). If a R5/R6 UE is not capable to support CM activation while HSDPA/HSUPA a fallback to DCH is triggered (see [R4] and [R6]).
5.12.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
INTRA-NODEB SOFT HANDOVER

In this case, a new radio link is added to existing ones in the NodeB. In case Compressed Mode is already active for the existing UE Radio Links, the Radio Link Addition Request message sent to the NodeB contains the following information: "De-activation Flag" IE set to "maintain active", since the compressed mode is kept active "Scrambling Code Change" IE set to "code change", since the alternate scrambling method is used For the new radio link, The NodeB has to apply the same compressed mode and pattern parameters as for the other radio links already present in the NodeB for the given UE-network connection.
UE NodeB RRC/ Measurement Report NBAP/ Radio Link Addition req (maintain active, code change) NBAP/ Radio Link Addition resp RRC/ active set update RRC/ active set update complete Serving RNC
Figure 79: intra-NodeB soft handover during compressed mode
INTRA-RNC/INTER-NODEB SOFT HANDOVER

In this case, a new radio link is added belonging to a new BTS controlled by the Serving RNC. In case Compressed Mode is already active for the existing UE Radio Links, the Radio Link Setup Request Iub message sent to the NodeB contains the following information: "Transmission Gap Pattern Sequence Information" IE, containing the pattern sequences information "Active Pattern Sequence Information", containing the pattern sequence length, and the starting CFN (TGCFN) In case of SF/2: "Scrambling Code Change" IE set to "code change", since the alternate scrambling method is used The new NodeB has to activate immediately the pattern sequence when receiving the RADIO LINK SETUP REQUEST message as specified in 25.433 8.2.17.2. The RNC calculates the compressed mode parameters (e.g. TGCFN, TGPRC) such that the patterns are in sync with the other active set cells and UE.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 197/213
UMTS Radio Mobility

In case of SF/2: It has to be noted that the 3GPP standard allows the 2 methods "scrambling code change" and "no scrambling code change" to be used simultaneously for radio links belonging to different NodeB. A fortiori, this is also valid for the inter-RNC soft handover case.
UE NodeB RRC/ Measurement Report NBAP/ Radio Link setup req (code change, 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 80: intra-RNC soft handover during compressed mode
INTER-RNC SOFT HANDOVER

In this case, a new radio link is added belonging to a new BTS controlled by a Drift RNC. In case Compressed Mode is already active for the existing UE Radio Links, the Radio Link Setup Request Iur message sent to the Drift RNC contains the following information: "Transmission Gap Pattern Sequence Information" IE, as on Iub, containing the pattern sequences information "Active Pattern Sequence Information" IE, as on Iub, containing the pattern sequence length, and the starting CFN (TGCFN) As in "intra-RNC/inter-NodeB soft handover" case, the RNC calculates the compressed mode parameters (e.g. TGCFN, TGPRC) for the cell on DRNC to be in sync with the ongoing CM pattern. In case Compressed Mode is not active, it can be activated later on in the call, using the COMPRESSED MODE COMMAND RNSAP message, in the same way as for the Iub interface. In case of SF/2: The "Scrambling code change" method is not specified on the Iur. The choice is left to the Drift RNC. In case of an Alcatel-Lucent Drift RNC, the "scrambling code change" is applied. In any case, the RADIO LINK ADDITION RESPONSE message indicates to the SRNC which method is used, so that the SRNC can inform the mobile on the scrambling code which is actually used on the new radio link.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 198/213
UMTS Radio Mobility

UE Drift NodeB RRC/ Measurement Report SCCP/ CR SCCP/ CC RNSAP/ Radio Link setup req (Pattern Sequence Info, TGCFN) NBAP/ Radio Link setup req (Pattern Sequence Info, TGCFN, (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 81: inter-RNC soft handover during compressed mode

When an Alcatel-Lucent Drift RNC is receiving a RNSAP RADIO LINK SETUP REQUEST message with compressed mode parameters, these parameters may not be consistent with the DRNC capability. This may happen in case the access network is composed of RNC from multiple manufacturers. In order to avoid compressed mode configuration which Alcatel-Lucent RNS is not able to support, The Alcatel-Lucent RNC implements a filtering function. Based on the output of this function, the RADIO LINK SETUP REQUEST or RADIO LINK ADDITION REQUEST received from the Iur is either accepted or rejected by the Alcatel-Lucent RNC. In this case, a rejection means that a RADIO LINK SETUP FAILURE or RADIO LINK ADDITION FAILURE is sent back to the SRNC. The filtering function is specified in the chapter on "Parameters".
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 199/213
UMTS Radio Mobility
5.12.16 CHANGE OF ALARM MEASUREMENT TYPE (COMMON HLS AND SF/2)

The Alarm Measurement Type, and associated compressed mode sequence depend on the Primary cell neighbouring list and priority setting, as explained in section 4.20 and 5.9. In case the primary cell is changed while compressed mode is running, the RNC keeps the ongoing measurement active independent of the configuration of the new Primary cell. This behaviour ensures that handover can be executed as fast as possible. The configuration of the new Primary cell is taken into account for the next measurement setup. In case of change of iMCTA trigger with crossover between inter-RAT and inter-frequency the ongoing measurement is aborted and the new measurement is started as detailed below.
The compressed mode is stopped immediately The measurement criteria is evaluated If the Alarm Measurement Criteria is still valid, measurements (either inter-freq or inter-system) are activated, depending on the Alarm Measurement Type
This is illustrated in the following figure:

CMperiod
Inter-system CM
Pattern sequence for inter-freq
...
Trigger change. Detection of crossover from GSM to inter-frequency measurements Measurement Type is now set to "inter-freq" Current compressed mode pattern is stopped A new CM scheme is started
Figure 82: change of CM scheme

The following message flow illustrates what happens in case of change of CM scheme.
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, TGPS reconf CFN, Fdd pattern=active, inter-frequency starting TGCFN)
NBAP/ Compressed Mode Command (CM Configuration Change CFN, inter-frequency starting TGCFN)
Figure 83: Dataflow on change of CM scheme

The initial RRC MEASUREMENT CONTROL message instructs the mobile to stop the GSM measurement.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 200/213
UMTS Radio Mobility
The subsequent RRC MEASUREMENT CONTROL messages provide the mobile with a list of inter-frequency cells to be monitored a TGPS reconfiguration CFN, at which all pattern sequences shall be de-activated. This IE has the same value as the CM Configuration Change CFN of the NBAP message below. a starting CFN for the inter-frequency pattern sequence The NBAP COMPRESSED MODE COMMAND contains a CM Configuration Change CFN, indicating the CFN at which the NodeB shall de-activate all the on-going pattern sequences. This message also contains a starting CFN for the inter-frequency pattern sequence. The procedure is applicable independently of the CM method.
5.12.17 DEFENCE MECHANISM FOR UE NOT SUPPORTING CM WITH HSPA

Some non-standards conforming UEs do not support compressed mode in combination with HSDPA or HSUPA. If compressed mode activation for HSxPA fails or the UE indicates in its capability information that it does not compressed mode with HSUPA then a reconfiguration to DCH is performed and compressed mode is activated with the DCH configuration. For details refer to [R4] (HSDPA) and [R6] (HSUPA).
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 201/213
UMTS Radio Mobility
5.12.18 PARAMETERS
This chapter lists all the configuration parameters for Compressed mode, most of them being part of 25.331
DYNAMIC PARAMETERS
These parameters are not accessed by the operator. The following set of parameter is present for each pattern, being active or not.
TGPS Status Flag TGCFN active, inactive Integer (0..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. Defines whether only DL, only UL, or combined UL/DL compressed mode is used. The value of this parameter depends on the UE classmark.
UL/DL mode
UL only, DL only, UL/DL
O&M PARAMETERS
This list contains the parameters which are used to configure the CM function. For the parameters displayed at the OMC-R level, it is always possible to change the value. If this should occur, there is no guarantee regarding Alcatel-Lucent UTRAN performances, or interoperability with mobiles. Parameters at the RNC level Most of the parameters listed below are defined at the RNC level.
GENERAL PARAMETERS
Name 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 RadioAccessService Class 3 RadioAccessService Class 3 RadioAccessService Class 3 RadioAccessService Class 3 RadioAccessService Class 3
gsm450Present gsm480Present Gsm850Present Gsm900PPresent Gsm900EPresent Gsm900RPresent
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 202/213
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
Object/Class
DlUserService Managed Object. Class 3 DlUserService Managed Object. Class 3
isGsmCModeActivationAllowed isInterFreqCModeActivationAllowed isHlsCModeAllowed isHlsCmMethodPreferred isHlsCmMethodPreferred IsHlsCmAllowedOnDRNC isSimCMAllowed

[not supported in UA06]
UlUserService Managed Object. Class 3 DlUserService Managed Object. Class 3
NeighbouringRNC
Managed Object. Class 3 DlUserService and UlUserService Managed Object. Class 3
Definition Indicates if compressed mode for GSM is allowed for this DL UserService. Indicates if the Compressed Mode for inter-frequency is allowed for this DL UserService. Indicates if compressed mode by HLS is allowed or not. 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,
If this parameter is set to TRUE than the RNC is allowed to use simultaneous compressed mode for inter-frequency and inter-RAT measurements for this service. Simultaneous inter-frequency and inter-RAT measurements are not possible for certain RAB combinations due the enhanced compressed mode requirements. If simultaneous compressed mode is requested but not possible then the RNC uses single compressed mode as per parameter is3GHandoverPreferred. Engineering guideline: TRUE for all RAB combinations with - isHlsCmMethodPreferred=No, or - isHlsCmMethodPreferred=Yes if throughput reduction by simultaneous CM pattern is acceptable. Otherwise: FALSE
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 203/213
UMTS Radio Mobility
PATTERN PARAMETERS
A certain number of pattern sequences can be defined in Alcatel-Lucent UTRAN. For each of the pattern, the available parameters are described in the table below. Those parameters are defined at the cell level.
Name TGMP Range FDD measurement, GSM RSSI measurement, GSM Initial BSIC identification, GSM BSIC re-confirmation Integer (1..511, Infinity) Definition Transmission Gap pattern sequence Measurement Purpose.
TGPRC
TGSN
Integer (0..14)
TGL1
Integer(1..14)
TGL2 TGD
Integer (1..14) Integer(15..269, undefined)
TGPL1 TGPL2 TGCFNoffset
Integer (1..144) Integer (1..144) Integer(0..255)
N Identify abort
Integer(1..128)
T Reconfirm abort
Integer(1..20)
The number of transmission gap patterns within the Transmission Gap Pattern Sequence. Transmission Gap Starting Slot Number The slot number of the first transmission gap slot within the TGCFN. 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. The time is given in steps of 0.5 seconds.
GSM measurement specific configuration [Global Market]: 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
GSM BSIC Re-confirmation -
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 204/213
UMTS Radio Mobility

Remarks on pattern parameters for GSM: the pattern allows at least a compressed mode-free 40ms window for intra-frequency neighbouring cell SFN decoding (the BCH has a TTI of 20ms). Therefore, the impact of compressed mode on intrafrequency measurements is very limited a transmission gap of 14 has been chosen in order to allow good performance on BSIC identification 8 patterns of 6x10ms have been allocated to RSSI measurements since the measurement period for the GSM carrier RSSI measurement is 480 ms in the CELL_DCH state (as stated in 25.133) 3x26 patterns have been allocated to initial BSIC identification in order to allow a minimum of 3 cells to be reported in the worst case (e.g. it takes up to N_IDENTIFY_ABORT to identify each cell)
FDD inter-frequency measurement specific configuration [Global Market]: 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
FDD Measurements 50 10 10 undefined undefined 6 undefined 0
Remarks on pattern parameters for inter-frequency: the pattern allows at least a compressed mode-free 40ms window for intra-frequency neighbouring cell SFN decoding (the BCH has a TTI of 20ms). Therefore, the impact of compressed mode on intrafrequency measurements is very limited
Simultaneous GSM and FDD inter-frequency measurements [USA Market]: 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), the GSM RSSI or BSIC Identification gap and the FDD measurement gap. These two gaps are spread by applying the TGCFNoffset=3 for FDD measurements.
POWER CONTROL PARAMETERS

This set of parameters is linked to power control algorithms used by the BTS when compressed mode is active. Those parameters are defined at the cell level.
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 205/213
UMTS Radio Mobility

Name RPP Range mode 0, mode 1 Definition Recovery Period Power control mode during the frame after the transmission gap within the compressed frame. Indicates whether normal or compressed Power Control mode is applied 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 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. Delta in DL SIR target value to be set in the UE during the frame containing the start of the second transmission gap in the transmission gap pattern (without including the effect of the bit-rate increase) When omitted, DeltaSIR2 = DeltaSIR1. Delta in DL SIR target value to be set in the UE one frame after the frame containing the start of the second transmission gap in the transmission gap pattern. When omitted, DeltaSIRafter2 = DeltaSIRafter1.
ITP
mode 0, mode 1
DeltaSIR1
Real(0..3 by step of 0.1)
DeltaSIRafter1
DeltaSIR2
DeltaSIRafter2
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
STATIC PARAMETERS
This set of parameter is static, and not displayed at the OMC-R level. These parameters are defined at the RNC level.
Name Downlink compressed mode method Uplink compressed mode method Downlink frame type Scrambling code change Range puncturing, SF/2, higher layer scheduling SF/2, higher layer scheduling A, B code change, no code change Definition Method for generating downlink compressed mode gap Method for generating uplink compressed mode gap See 25.212, 4.4.2 Indicates whether the alternative scrambling code is used for compressed mode method 'SF/2'
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 206/213
UMTS Radio Mobility

In this version, 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, HLS, SF/2&HLS SF/2, HLS, SF/2&HLS B,A code change, no code change
CONTROL PERFORMED BY THE ALCATEL-LUCENT RNC

The following table specifies the control which is performed by the Alcatel-Lucent RNC on the compressed mode parameters received in the RADIO LINK SETUP REQUEST or RADIO LINK ADDITION REQUEST Iur message.
Parameter received from Iur 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, HLS SF/2, HLS No check No check No check No check No check
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 207/213
UMTS Radio Mobility
5.13. 2G TARGET CELL CHOICE RADIO CRITERIA 5.13.1 DESCRIPTION

At each measurement period the mobile reports the measured cells even if all neighbour cells are not measured. By selecting the first cell reported by the mobile which fulfils the IMCTA criteria (the selected cell may not be the best cell on a given Carrier), the compressed mode duration is limited. On reception of inter-system measurement report, if a decision for handover is made, the RNC applies a 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 GSM neighbouring cell. In the Iur case, this parameter is provided by the DRNC as the Radio Link is added. In case no valid value is provided by the DRNC, the Alcatel-Lucent SRNC uses 0 as a default value.
Measurement filtering
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 among the eligible cells as the cell having the highest measured GSM Carrier RSSI after equalization. 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 5.10. Note: 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 5.11.2.
5.13.2 PARAMETERS
Name Object/Class
RadioAccessService Class3 GsmNeighbouringCell Class3
minimumGsmRssiValueForHO gsmCellIndivOffset
Definition Threshold on GSM carrier RSSI for inter-system target cell eligibility Offset used for "target cell equalization"
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 208/213
UMTS Radio Mobility
5.14. FDD TARGET CELL CHOICE INTER FREQUENCY RADIO CRITERIA 5.14.1 DESCRIPTION
At each measurement period the mobile reports the measured cells even if all neighbor cells are not measured. By selecting the first cell reported by the mobile which fulfills the IMCTA criteria (the selected cell may not be the best cell on a given Carrier), the compressed mode duration is limited. On reception of inter-frequency measurement report, if a decision for handover is made, the RNC applies a 3-step process for the choice of the target cell: Measurement equalization Measurement filtering Target cell identification
Measurement equalization
This process consists in adding an offset to the reported measurements, as in the following formula: equalized measurement = reported measurement + Neighbouring Cell Offset The Neighbouring Cell Offset parameter is configured at the OMC-R for each FDD neighbouring cell. In the Iur case, this parameter is provided by the DRNC as the Radio Link is added. In case no valid value is provided by the DRNC, the Alcatel-Lucent SRNC uses 0 as a default value.
Measurement filtering
Following the measurement equalization, the following condition is evaluated. When not fulfilled, the corresponding cell is considered as not eligible. 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 among the eligible cells as the cell having the highest CPICH Ec/No after equalization.
5.14.2 PARAMETERS
Name Object/Class
UMTSFddNeighbouringCell Class3 DlUserService Class3 DlUserService Class3
neighbouringCellOffset minimumCpichEcNoValueForHO minimumCpichRscpValueForHO
Definition Offset used for "target cell equalization" CPICH Ec/No threshold for interfrequency cell eligibility CPICH RSCP threshold for interfrequency cell eligibility
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 209/213
UMTS Radio Mobility
5.15. NEIGHBOR CELLS FLEXIBLE MANAGEMENT 5.15.1 DESCRIPTION

The Alcatel-Lucent UTRAN allow any combination of intra-freq, inter-freq and inter-RAT neighbour cells in SIB11 [Global Market - as long as the total number does not exceed the current allowed value (48 or 47 depending whether Measurement control is activated in SIB11).] [USA Market - 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.
5.15.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 inter-RAT neighbor cells allowed in SIB11 within a global limitation of 47/48 [Global Market] or 96 [USA Market] neighbor cells) 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.
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. Note: SIB12 follows same rules as SIB11 to select cells and set parameters in the message
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 210/213
UMTS Radio Mobility
5.15.3 PARAMETERS
Name Sib11OrDchUsage 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.
Sib11OrDchUsage
UMTSFddNeighbouringCell
SIB11AndDCHNeighbouringFddCellAlgo
FDDCell Class 3
6.
6.1.
ALCAP AO ARFCN ATM BCCH BSIC BTS CAC CAS CFN CIO CM CN CPICH CRNC CS CSD DCCH DCH DRNC DHO
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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 211/213
UMTS Radio Mobility

DSCH DTCH DTM E-DCH FACH FDD GPRS GTP HCS HHO HLS HSDPA HS-DSCH HSUPA I/B IF iMCTA IP IRAT LTOA MAP MSC NB NBAP PCH PS RAB RACH RAN RAT RANAP RB RL RNC RNS RNSAP RRC RSCP SCCP SF SGSN SHO SIB SRB SRLR SRNC SRNS TDD TGCFN TGPRC TGPS TRB UP URA UTRAN WB Downlink Shared Channel Dedicated Traffic Channel Dual Transfer Mode Enhanced DCH 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 Interactive/Background Inter Frequency Intelligent Multi Carrier Traffic Allocation Internet Protocol Inter RAT usually GSM measurements or GSM handover Latest Time Of Arrival Mobile Application Part Mobile Switching Centre Narrow Band Node B Application Part Paging Channel Packet Switched Radio Access Bearer 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 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
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 212/213
UMTS Radio Mobility
6.2.
DEFINITIONS
Empty chapter.
6.3.
UA06 Value Mapping for Hysteresis and Weight USA Market

If isExtendedSrbDcch3dot4k is set to True the WNMS parameters hysteresis, hysteresis1A, hysteresis1B, hysteresis2D and hysteresis2F have different semantics on the user interface (range 0dB to 7.5dB) and within the RNC. The RNC interprets two Bits of the value as hysteresis and the other two Bits as weight as per following table:
Hysteresis (1a, 1b, 2d, 2f) WNMS value: 0dB ASN.1 value: 0 ASN.1 value (bitmap): 0000 UA06 meaning RRC value - Hyst RRC value - W
0,5dB 1 0001
1dB 2 0010
1,5dB 3 0011
2dB 4 0100
2,5dB 5 0101
3dB 6 0110
3,5dB 7 0111
4dB 8 1000
4,5dB 9 1001
5dB 10 1010
5,5dB 11 1011
6dB 12 1100
6,5dB 13 1101
7dB 14 1110
7,5dB 15 1111
WNMS Hysteresis parameter is shared between Hysteresis (lower 2 Bits) and W (upper 2 Bits) 0dB 1dB 2dB 3dB 0dB 1dB 2dB 3dB 0dB 1dB 2dB 0,0 0,0 0,0 0,0 0,3 0,3 0,3 0,3 0,6 0,6 0,6
3dB 0,6
0dB 1,0
1dB 1,0
2dB 1,0
3dB 1,0
Notes: The value mapping was introduced when late during UA06 development it was detected that the weight parameter is not available as operator modifiable parameter and it was no longer possible to add it as separate parameter. As activation flag for the hysteresis/weight split the spare parameter isExtendedSrbDcch3dot4k is used. The parameter name does not reflect the actual semantics It is assumed that the restricted value ranges for hysteresis and weight are acceptable. In a later release the hysteresis parameter will again have full value range and a separate weight parameter will be introduced. Name Object/Class
isExtendedSrbDcch3dot4k
Definition Enable/Disable this feature globally
END OF DOCUMENT
UMT/SYS/DD/0054
08.08/EN
Standard
09/Oct/2008
Page 213/213

UMTS Radio Mobility

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UMTS Radio Mobility

Uploaded by

Copyright:

Available Formats

UMTS Radio Mobility

Copyright 2007 Alcatel-Lucent, All Rights Reserved Printed in France