3g Handover Detailed Document

Handover Control Feature

Guide

WCDMA RAN

Handover Control Feature Guide

ZTE Confidential Proprietary 1


Version Date Author Reviewer Revision History

V7.0 2012-3-30 Feng

Hong

Zhao

Dapeng

1. Added Section 2.1.24 “ZWF21-03-050

Handover Optimization in Weak-Coverage” and

Section 8.4 “Fast Return to EUTRAN”.

2. Added Section 6.4.1 “Special Events

Processing via IUR for PS0/0”.

3. Modified the switch of function enabled in

Section 5.8.

4. Modified the strategy of coupling between

DSCR and soft-handover relocation in Section

6.3.

5. Modified the remark for measurement quality in

Sections 5.1.2.7 and 7.1.2.5.

6. Added Section 4.3.7 “Criterion of Being in the

Same Active Set Based on Cell Type”.

7. Modified Chapter 9, and added the authorized

judgment strategy when SNAC list of PLMN

carried in CommonID is empty.

8. Modified Section 4.3.8, and added the parallel

processing strategy of Iub and Uu interfaces

when adding a radio link in a softer handover.

9. Modified the description of parameters‟

StateMode and GsmStateMode.

10. Added the following new parameters:

CelReturnLteSwch, fastRetEUtranSwch,

RncFeatSwitchBit18, RncFeatSwitchBit9,





RncFeatSwitchBit2, HcsSupportInd, and

ParallelSoftHO.

11. Deleted the following parameters:

RncFeatSwitch, UseofHcs(UtranCell),

UseofHcs(UtranRelation), and

UseofHcs(gsmRelation).



12. Added the special strategy to deal with the

situation that DRNC does not support the

strategy of compress mode command activates

compress mode in Section 3.3 “Compressed

Mode Configuration Strategy via RNC”.

13. Added Section 4.3.8.3 “Strategy for Soft

Handover OD Switch Configuration in the

Signaling Stage”.

14. Added Section 4.3.8.4 “Special Events Handling

via IUR for CS”.

15. Modified handover parameter index quotations

in Sections 4.1.2.4, 4.3.10, 5.1.2.7, 7.1.2.5.

16. Modified parameter-related MOs.

17. Modified parameter names from “table field

name” to “logical name”.

18. Added the following parameters:

RncFeatSwitchBit16, RncFeatSwitchBit17,,

CsIntraEvtSwch, srvHoIndAmr, srvHoIndCs64,

srvHoIndPsNRT, srvHoIndPsRT,

BSCPSFeatSwitch, BSCDTMFeatSwitch,

UIntraMeasProfile, UIntraMeasSrvSpec,

UIntraMeasNoSrvSpec, UInterMeasProfile,

UInterMeaSrvSpec, UInterMeasNoSrvSpec,

URatMeasProfile, URatMeasSrvSpec,

URatMeasNoSrvSpec, IurgFeatSwitch,

imsiMatchedDgtNum, imsiMatchedDigit,

BoardPwrOffHoTmr, UtraSISwitch,

intialHoCelSelScene, UUeIntMeasProfile,

refUUeIntMeasProfile, and evtAbTcpThrd.


MeasQuantity(Intra), MeasQuantity(Inter),

OwnMeasQuantity, RptCrt(Intra), RptCrt(Inter),

RptCrt(Rat), IntRatHoMth, InterHoMth,

SoftHoMth, servHoInd, BscFeatSwitch, ExtInfo,

ExtInfoDgtNum, MeasQuantity(UeInt),

RptCrt(UeInt), RptTxPwrInd, EvtMeasRTT2,

UeIntMCfgNote, and HoEvtMeasTP.

20. Added “Strategy of coupling between intelligent

carrier power off/on and inter-frequency

handover” in Section 5.1.2.7.

21. Added Section 7.7 “UMTS->GSM Handover



Based on Board Power Off”.

22. Added Section 8.8.1 “UTRA SI”.

V8.0 2012-11-2 Feng

Hong

Zhao

Dapeng

1. Added Section 8.5 “EUTRAN Blacklist

Management”.

2. Added Section 8.6 “Inter-RAT Handover based

on EUTRAN Load”, and modified Section 2.1.18

and added the condition of acquiring EUTRAN

load.

3. Added Section 8.7 “EUTRAN Detection

Supported”

4. Added Section 7.9 “Special UMTS->GSM

Handover Strategy based on the Indoor

Neighboring Cell”.

5. Modified Sections 5.4, 5.5, 5.6, 7.3, 7.4, 7.5,

and added the RNC level switch to control.

6. Modified Section 4.3.8.1 to “Intra-frequency

Handover Optimization in Weak Coverage”, and

added the quality judgement strategy for event

1D.

7. Added Section 2.1.24 “ZWF21-03-050

Handover Optimization in Weak-Coverage”.

8. Modified Section 7.1.2.4 “Processing of

Inter-RAT Events”, and changed the inter-RAT

handover failure penalty from direct at cell to

direct at UE;

9. Modified Section 5.1.2.7 “Parameter

Configuration Strategies”, and separated

“Inter-frequency and Inter-RAT Measurement

Choice” and described it in Section 5.10.

10. Added Section 5.11 “Inter-frequency and

Inter-RAT Period Measurement Algorithm”.

11. Added Section 6.2.3 “Common Status DSCR”.

12. Added Section 8.8 “RIM” and Section 8.8.2

“SON Transfer”.

13. Added Section 6.4.2 “Special Inter-frequency

Handover Strategy via IUR for HSPA”.

14. Added the following parameters:

EutranNCblstSwch, StateMode(UENbrBlkList),

LdBsdEutranHOInd, EutranUlLdThrd,

EutranDlLdThrd, EutraDetectionInd,

IndoorCellInd, RncTxPwrHoSwch,



RncUlBlerHoSwch, RatCelInfoSwch,

IntraHoEcNoThrd, IntraHoRscpThrd,

EnhanceHoSwch, HoToEutraPenTimer,

InterHoMth, IntRatHoMth, PeriodTriggerTime,

dscrInCmnToDedSwch, sonTransReqPeriod,

sonTransReqNumThrd, sonTransRespSwitch,

rxlevNecellInd, sonTransRespNumThrd,

CResPara5, RNCFEATSWITCHBit24,

LteCellIdenFlag, and RncFeatSwitchBit25.


EcNoThrAddNRLSHO and

RSCPThrAddNRLSHO.

V8.5 2013-7-4

Huang

Meiqing

Feng

Hong

Zhao

Dapeng

1. Modified Section 4.3.14 “Scenarios of

Intra-Frequency Hard Handover”: added the

synchronization mode.

2. Modified Section 8.4 “Fast Return to EUTRAN”.

3. Added the following parameters: GResPara47,

MulSrvRePsHoLteSw, EutranPsHoMode,

PsHoLteMeasTimer, and SimCompUserNum.

4. Modified Section 5.1.2.4 “Processing of

Inter-Frequency Events”: added the penalty

timer for inter-frequency handover failure.

5. Added Section 5.1.2.5 “Minimum Quality

Judgement Strategy in Inter-frequency

Handover”.


CResPara6, GResPara2, and GResPara5.

7. Modified Section 8.1 “UTRAN<->LTE PS

Handover Strategy”, and added strategy of

checking UE E-UTRA Capability before

initiating the PS handover procedure from

Utran to EUTRAN.

8. Modified Section 8.4 “Fast Return to EUTRAN”,

separated the control switch of fast return for

CSFB and SRVCC, added a timer for

identifying CSFB, and added strategy of

carrying CSFB information via Iur interface.


CResPara7, GResPara7, and PsSigForImsInd.

10. Added feature IDs, supplemented some

parameters, glossaries, and counters. Modified



some descriptions of the text. Deleted the

profile IDs.

© 2014 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used

without the prior written permission of ZTE.

Due to update and improvement of ZTE products and technologies, information in this document is subjected to

change without notice.



TABLE OF CONTENTS

1 Feature Attributes ............................................................................................ 14

2 Overview .......................................................................................................... 14

2.1 ZWF21-03-001 Soft/Softer Handover ................................................................. 16

2.2 ZWF21-03-002 Intra-Frequency Hard Handover ................................................ 16

2.3 ZWF21-03-003 Inter-Frequency Hard Handover ................................................ 16

2.4 ZWF21-03-004 Inter-RAT Mobility (GSM) .......................................................... 17

2.5 ZWF21-03-006 Inter-RNC Handover with Iur Support ........................................ 19

2.6 ZWF21-03-008 Directed Signalling Connection Re-establishment ..................... 20

2.7 ZWF21-03-009 Coverage Based Handover ....................................................... 20

2.8 ZWF21-03-010 Compressed Mode .................................................................... 20

2.9 ZWF21-03-011 Neighboring Cells Priorities ....................................................... 20

2.10 ZWF21-03-012 Handover Based on Dedicated Downlink Transmit Power ......... 21

2.11 ZWF21-03-012 Handover Based on Dedicated Uplink Transmit Power (UE) ..... 21

2.12 ZWF21-03-013 Quality-Based Handover ........................................................... 21

2.13 ZWF21-03-020 SRNS Relocation ...................................................................... 21

2.14 ZWF21-03-022 IMSI-based Handover ............................................................... 22

2.15 ZWF21-03-023 Inter-RAT PS Handover (GSM) ................................................. 22

2.16 ZWF21-03-024 DTM Handover .......................................................................... 22

2.17 ZWF21-03-025 NACC ........................................................................................ 22

2.18 ZWF21-03-026 Target Cell Load Based Inter-RAT Handover ............................ 23

2.19 ZWF21-05-022 Handover Strategy Based on Service Type ............................... 23

2.20 ZWF21-03-014 Enhanced Iur-g .......................................................................... 23

2.21 ZWF21-03-110 UTRAN<->LTE PS Handover Strategy ...................................... 23

2.22 ZWF21-03-120 Single Radio Voice Call Continuity (SRVCC)............................. 24

2.23 ZWF21-03-101 CS Fallback (CSFB) .................................................................. 24

2.24 ZWF21-03-050 Handover Optimization in Weak-Coverage ................................ 24

2.25 ZWF23-03-001 HS-DSCH Serving Cell Change ................................................ 24

2.26 ZWF23-03-002 HS-DSCH handover to/from DCH ............................................. 25

2.27 ZWF23-03-003 HS-DSCH Inter-RAT Reselection .............................................. 25

2.28 ZWF23-03-004 HSDPA Soft/Softer Handover of A-DPCH ................................. 25

2.29 ZWF23-03-005 HSDPA over Iur ......................................................................... 25

2.30 ZWF25-03-001 HSUPA Soft/Softer Handover .................................................... 25

2.31 ZWF25-03-002 E-DCH Serving Cell Change Inside Active Set .......................... 26

2.32 ZWF25-03-003 E-DCH Intra-frequency Hard Handover ..................................... 26

2.33 ZWF25-03-004 E-DCH Inter-frequency Hard Handover ..................................... 26

2.34 ZWF25-03-005 HSUPA over Iur ......................................................................... 26

2.35 ZWF25-03-012 HSUPA Inter-RAT Reselection .................................................. 27



3 Compressed Mode Strategy ........................................................................... 27

3.1 Introduction to Compressed Mode ..................................................................... 27

3.2 Compressed Mode Strategy .............................................................................. 29

3.3 Compressed Mode Configuration Strategy via RNC .......................................... 33

4 Intra-Frequency Handover Strategy ............................................................... 34

4.1 Intra-Frequency Measurement ........................................................................... 35

4.1.1 Introduction to Intra-Frequency Measurement .................................................... 36

4.1.2 Measurement Control Method Related to Active Set and Monitored set ............. 36

4.1.3 Neighboring Cells Configuration ......................................................................... 42

4.2 Handling Mechanism for Periodical Reporting of Intra-Frequency Handover

Measurement ..................................................................................................... 44

4.3 Intra-Frequency Handover Decision ................................................................... 45

4.3.1 Event 1A-Triggered Handover............................................................................ 45

4.3.2 Event 1B-Triggered Handover............................................................................ 47

4.3.3 Event 1C-Triggered Handover ........................................................................... 48

4.3.4 Event 1D-Triggered Handover ........................................................................... 50

4.3.5 CIO Configuration Strategy ................................................................................ 51

4.3.6 Time-To-Trigger Mechanism Used to Control Event Report ............................... 52

4.3.7 Criterion of Being in the Same Active Set Based on Cell Type ........................... 52

4.3.8 Processing of Intra-Frequency Events ............................................................... 53

4.3.9 Detected set Handover ...................................................................................... 57

4.3.10 Detected Set Tracing ......................................................................................... 58

4.3.11 Processing of the Rx-Tx Time Difference of a UE in Macro Diversity ................. 58

4.3.12 IUB Transmission Bandwidth Limitation Strategy ............................................... 60

4.3.13 Decision on Support-CS64k Traffic of Target Cell .............................................. 61

4.3.14 Scenarios of Intra-Frequency Hard Handover .................................................... 62

4.3.15 Disposal Strategy of Intra-Frequency Events in Buffer ....................................... 63

4.4 Intra-Frequency Handover Procedure ................................................................ 65

4.4.1 Inter-RNC Soft Handover (Adding a Radio Link) ................................................ 65

4.4.2 Inter-RNC Soft Handover (Deleting a Radio Link) .............................................. 66

4.4.3 Inter-RNC Soft Handover (Swapping a Radio Link) ............................................ 67

4.4.4 Intra-RNC Hard handover .................................................................................. 68

4.4.5 Inter-RNC Hard Handover Through lur Interface ................................................ 69

4.4.6 Inter-RNC Hard Handover Without lur Interface ................................................. 70

5 Inter-Frequency Handover Strategy ............................................................... 71

5.1 Inter-Frequency Measurement ........................................................................... 72

5.1.1 Introduction to Inter-Frequency Measurement .................................................... 74

5.1.2 Inter-Frequency Measurement Control Method .................................................. 78

5.1.3 Neighboring Cells Configuration ......................................................................... 90



5.2 Handling Mechanism for Periodical Report of Inter-Frequency and Inter-RAT

Handover Measurement ..................................................................................... 92

5.3 Downlink Coverage Based Inter-Frequency Handover ....................................... 93

5.4 Uplink BLER Based Inter-Frequency Handover ................................................. 93

5.5 Uplink Transmit Power Based Inter-Frequency Handover .................................. 94

5.6 Downlink Transmit Power Based Inter-Frequency Handover ............................. 95

5.7 Load Control Based Handover ........................................................................... 96

5.8 Moving Speed Based Handover ......................................................................... 96

5.9 Coupling Processing of Different Handovers ...................................................... 97

5.10 Inter-frequency and Inter-RAT Measurement Choice ......................................... 98

5.11 Inter-frequency and Inter-RAT Period Measurement Algorithm ........................ 100

5.11.1 Period Measurement Configuration .................................................................. 100

5.11.2 Processing of Period Measurement Report ...................................................... 102

5.12 Inter-Frequency Handover Procedure .............................................................. 103

6 Inter-RNC Mobility ......................................................................................... 104

6.1 SRNS Relocation ............................................................................................. 104

6.1.1 Relocation Triggered by Soft Handover ........................................................... 105

6.1.2 Relocation Triggered by Hard Handover .......................................................... 108

6.2 DSCR .............................................................................................................. 110

6.2.1 R99 DSCR ....................................................................................................... 110

6.2.2 HSPA DSCR .................................................................................................... 110

6.2.3 Common Status DSCR .................................................................................... 111

6.3 Coupling between relocation and DSCR .......................................................... 111

6.4 Special Handling Strategy of IUR ..................................................................... 111

6.4.1 Special Events Processing via IUR for PS0/0 .................................................. 111

6.4.2 Special inter-frequency handover strategy via IUR for HSPA ........................... 112

7 GSM Inter-RAT Handover Policy .................................................................. 112

7.1 Inter-RAT Measurement ................................................................................... 113

7.1.1 Overview of Inter-RAT Measurement ............................................................... 114

7.1.2 Control Methods for Inter-RAT Measurement ................................................... 116

7.1.3 Neighboring Cells Configuration ....................................................................... 125

7.2 Inter-RAT Handover Based on Downlink Coverage ......................................... 127

7.3 Inter-RAT Handover Based on Uplink BLER .................................................... 127

7.4 Inter-RAT Handover Based on Uplink Transmit Power .................................... 128

7.5 Inter-RAT Handover Based on Downlink Transmit Power ................................ 129

7.6 Handover Based on Load Control .................................................................... 130

7.7 UMTS->GSM Handover Based on Board Power Off ........................................ 130

7.8 Inter-RAT Handover based on GSM Load ....................................................... 131

7.8.1 Acquirement and Update of GSM Load Condition ............................................ 131

7.8.2 Inter-RAT Handover based on GSM Load Process .......................................... 132



7.9 Special UMTS->GSM Handover Strategy based on the Indoor Neighboring Cell133

7.10 Coupling for Different Handover Causes .......................................................... 133

7.11 Inter-RAT Handover Process ........................................................................... 134

7.11.1 CS Service Handover from 3G System to 2G System ...................................... 134

7.11.2 PS Service Reselection in 3G to 2G Handover ................................................ 137

8 UTRAN<->LTE Handover Strategy ............................................................... 141

8.1 UTRAN<->LTE PS Handover Strategy ............................................................ 141

8.1.1 EUTRAN Inter-RAT Measurement ................................................................... 142

8.1.2 EUTRAN Inter-RAT Handover Based on Downlink Coverage .......................... 145

8.1.3 EUTRAN Inter-RAT Handover Based on BLER and Transmit Power ............... 146

8.1.4 Coupling for Different Handover Causes .......................................................... 146

8.1.5 EUTRAN Inter-RAT Handover Process ............................................................ 147

8.2 SRVCC ............................................................................................................ 147

8.3 CSFB ............................................................................................................... 149

8.4 Fast Return to EUTRAN ................................................................................... 150

8.4.1 Fast Return in PS Handover Way .................................................................... 150

8.4.2 Fast Return in Redirection Way based on Measurement ................................. 152

8.4.3 Fast Return in Redirection Way without Measurement ..................................... 154

8.4.4 Fast Return Strategy of IUR ............................................................................. 156

8.5 EUTRAN Blacklist Management ...................................................................... 156

8.6 Inter-RAT Handover based on EUTRAN Load ................................................. 157

8.7 EUTRAN Detection Supported ......................................................................... 157

8.8 RIM .................................................................................................................. 157

8.8.1 UTRA SI .......................................................................................................... 159

8.8.2 SON Transfer ................................................................................................... 160

9 IMSI-based handover .................................................................................... 160

9.1 Querying Whether the SRNC Cell Is Authorized According to IMSI.................. 162

9.2 Querying Whether the DRNC Cell Is Authorized According to IMSI ................. 164

10 HSDPA-related special strategy ................................................................... 165

10.1 Overview .......................................................................................................... 166

10.2 Intra-frequency Handover ................................................................................ 166

10.3 Inter-frequency Handover ................................................................................ 168

10.4 Inter-RAT Handover ......................................................................................... 169

11 HSUPA-related special strategy ................................................................... 169

11.1 Overview .......................................................................................................... 170



11.4 Inter-RAT Handover ......................................................................................... 175



12 MBMS-related special strategy ..................................................................... 175



13 Parameters and Configurations ................................................................... 177

13.1 Intra-Frequency Handover Parameters ............................................................ 177

13.1.1 Parameter List ................................................................................................. 177

13.1.2 Parameter Configurations ................................................................................ 183

13.2 Inter-Frequency Handover Parameters ............................................................ 227

13.2.1 Parameter List ................................................................................................. 227


13.3 SRNC Relocation Parameters.......................................................................... 286

13.3.1 Parameter List ................................................................................................. 286


13.4 GSM Inter-RAT Handover Parameters ............................................................. 291

13.4.1 Parameter List ................................................................................................. 291


13.5 EUTARN Inter-RAT Handover Parameters ...................................................... 333

13.5.1 Parameter List ................................................................................................. 333


13.6 IMSI-based Handover Parameters ................................................................... 358

13.6.1 Parameter List ................................................................................................. 358


13.7 HSDPA Handover Parameters ......................................................................... 367

13.7.1 Parameter List ................................................................................................. 367


13.8 HSUPA Handover Parameters ......................................................................... 369

13.8.1 Parameter List ................................................................................................. 369


13.9 MBMS Handover Parameters .......................................................................... 371

13.9.1 Parameter List ................................................................................................. 371


14 Counter and Alarm ........................................................................................ 372

14.1 Counter List ..................................................................................................... 372

14.1.1 RNC Soft Handover Statistics .......................................................................... 372

14.1.2 RNC Hard Handover Statistics ......................................................................... 379

14.1.3 Cell Relocation Statistics .................................................................................. 394

14.1.4 Inter-RAT Cell Handover Statistics ................................................................... 400

14.1.5 HSPA Serving Cell Change Statistics .............................................................. 411

14.1.6 Inter-cell Hard Handover Statistics ................................................................... 415

14.1.7 Inter-cell Soft Handover Statistics .................................................................... 419



14.1.8 Inter-cell Detected Set Statistics ...................................................................... 421

14.1.9 Inter-RAT Inter-cell Handover Statistics ........................................................... 421

14.1.10 Soft Handover via Iur Statistics ........................................................................ 424

14.1.11 Eutran Inter-RAT Handover Statistics .............................................................. 425

14.1.12 Compressed Mode Statistics............................................................................ 426

14.2 Alarm List ......................................................................................................... 428

15 Glossary ......................................................................................................... 428



FIGURES

Figure 3-1 Transmission Gap (TG) Position .......................................................................28

Figure 3-2 Parameters of Compressed Mode ....................................................................29

Figure 3-3 Procedure for E-DCH Fallback to DCH Prior to Initiation of Compressed Mode 31

Figure 3-4 Procedure for Configuring Accompanying Compressed Mode ..........................32

Figure 3-5 Procedure for Configuring Dedicated Compressed Mode .................................33

Figure 4-1 Intra-frequency Handover Index Quotations ......................................................40

Figure 4-2 Cell Priority Configuration .................................................................................43

Figure 4-3 Time-To-Trigger mechanism .............................................................................52

Figure 4-4 Intra-RNC Soft Handover (Adding a Radio Link) ...............................................65

Figure 4-5 Intra-RNC Soft Handover (Deleting a Radio Link) .............................................66

Figure 4-6 Intra-RNC Soft Handover (Swapping a Radio Link) ..........................................67

Figure 4-7 Intra-RNC Hard Handover ................................................................................68

Figure 4-8 Inter-RNC Hard Handover Through lur Interface ...............................................69

Figure 4-9 Inter-RNC Hard Handover Without lur Interface ................................................70

Figure 5-1 Inter-Frequency Handover Index Quotations ....................................................87

Figure 5-2 Cell Priority Configuration .................................................................................91

Figure 6-1 Relocation Triggered by Soft Handover .......................................................... 105

Figure 6-2 Relocation Triggered by Hard Handover ......................................................... 108

Figure 7-1 Indexing relations for inter-RAT handover ....................................................... 123

Figure 7-2 Priority Settings of Cells .................................................................................. 126

Figure 7-3 3G to 2G CS Service Handover ...................................................................... 134

Figure 7-4 3G to 2G CS Service Handover Procedure via IUR-G .................................... 135

Figure 7-5 PS service reselection initiated by an UE in the case of 3G to 2G handover ... 138

Figure 7-6 PS service reselection initiated by the RNC in the case of 3G to 2G handover

........................................................................................................................................... 139

Figure 8-1 Indexing relation for inter-RAT handover ......................................................... 143

Figure 8-2 UTRAN->EUTRAN PS Handover Process ...................................................... 147

Figure 8-3 SRVCC from E-UTRAN to UTRAN ................................................................. 148



Figure 8-4 EUTRAN->UTRAN Handover for CSFB .......................................................... 149

Figure 9-1 Schematic Diagram of Querying Whether a the SRNC Cell Is Authorized

According to IMSI ............................................................................................................... 164

Figure 9-2 Schematic Diagram of Querying Whether a the DRNC Cell Is Authorized

According to IMSI ............................................................................................................... 165

TABLES

Table 2-1 Correspondence between Handover and Compressed Mode ............................15

Table 3-1 Parameters of Compressed Mode......................................................................30

Table 12-1 Table of Principle ........................................................................................... 176

Table 13-1 Service Type Related UE Inter-frequency Measurement Parameter

Configuration Default Value ................................................................................................ 267

Table 13-2 Service Type Related UE Inter-RAT Measurement Parameter Configuration

Default Value ...................................................................................................................... 304



1 Feature Attributes

System version: [RNCV3.12.10/RNCV4.12.10, Node B V4.12.10, OMMR V12.12.41,

OMMB V12.12.40]

Attribute: [Mandatory + Optional]

Involved NEs:

UE Node B RNC MSC MGW SGSN GGSN HLR

√ √ √ - - - - -

Note:

*-: Not involved.

*√: Involved.

Dependency: [None]

Mutual exclusion: [None]

Note: [None]

2 Overview

The cell handover strategy is required in WCDMA to implement mobility management of

RRC connections due to UE mobility. It is also required to balance traffic among cells to

lower traffic in heavily-loaded cells. Service connections must not be interrupted and

QoS must be guaranteed during handover.

In the process of a handover:

If a UE retains the radio connection with the current cell while establishing a radio

connection in a new cell, the handover is called soft handover.

If the new and current cells belong to the same Node B during a soft handover, the

handover is called softer handover.



If a UE needs to disconnect with the current cell before setting up a link

(synchronization) with a new cell (that is, the new and current links do not co-exist),

the handover is called hard handover.

A transient interruption will occur to UE transmission and reception duringa hard

handover. Therefore, the hard handover may affect the QoS.

Handovers may also be classified into intra-frequency handover, inter-frequency

handover and inter-RAT handover by different cell frequency features or access

technologies before and after a handover. A UE in connection can only receive

single-frequency service data, but soft/softer handover requires a UE to retain a radio link

with several cells concurrently, so the soft/ softer handover must be an intra-frequency

handover. However, a handover between the cells of the same frequency may not be a

soft/softer handover. It may be a hard handover. The inter-frequency/inter-RAT handover

is surely a hard handover because of different carrier frequencies/frequency bands.

Normally, a UE has only one set of receiver and transmitter, so activating compressed

mode is necessary for inter-frequency and inter-RAT measurement. The following table

lists the correspondence between handover and compressed mode.

Table 2-1 Correspondence between Handover and Compressed Mode

Softer

Handover Soft

Handover

Hard

Handover

Require Compressed

Mode to Activate or

Not

Intra-frequency Y Y Y N

Inter-frequency N N Y Y

Inter-RAT N N Y Y

A handover generally involves three steps: measurement, handover decision and

handover implementation. Measurement is the prerequisite for a handover, handover

decision is the core of a handover and handover implementation is the process of

implementing a handover decision. This document describes these three steps to

illustrate the relevant algorithms, and contains the following contents:



2.1 ZWF21-03-001 Soft/Softer Handover

In soft handover, a UE maintains several radio links with different Node Bs, while in softer

handover, a UE concurrently maintains radio links with several cells in a Node B, and

these cells are also known as macro diversity.

Soft/softer handover only occurs in intra-frequency cells. Compared with the hard

handover, the soft/softer handover has the following features:

Soft and softer handovers are seamless handovers and no service will be

interrupted during handover.

Macro diversity gain: When a UE maintains radio links with several cells, the

receiver may enhance the accuracy of data reception and link receiving quality and

lower the transmit power of all links by combining the signal receiving results of

several links.

The best cell where a UE registers may establish a radio connection with the UE in

time to lower the transmit power of the UE.

In view of these features, for intra-frequency handover, soft and softer handovers are

conducted whenever possible, a hard handover is only conducted when the soft/softer

handover is unavailable.

2.2 ZWF21-03-002 Intra-Frequency Hard Handover

Hard handover is a typical handover mechanism in which a UE needs to disconnect with

the current cell before setting up a link (synchronization) with a new cell (that is, the new

and current links do not co-exist). The intra-frequency hard handover is only conducted

when the soft/softer handover is unavailable.

2.3 ZWF21-03-003 Inter-Frequency Hard Handover

Inter-frequency hard handover means a UE in connection state hands over from one cell

on one frequency of UTRAN to another cell on another frequency.



The factors triggering an inter-frequency hard handover include radio quality, cell load,

and moving speed of the UE.

Inter-frequency hard handover triggered by radio quality: An inter-frequency

measurement is initiated when the quality of the frequency where the UE is currently

located worsens, and then the UE is handed over to the frequency with better quality

based on the inter-frequency measurement result. The quality of the carrier frequency

where the UE is currently located is measured according to the following four standards

(For details, see Chapter 5 “Inter-Frequency Handover Strategy”):

PCPICH quality of the cell in the current serving carrier frequency.

Uplink Block Error Rate (BLER) of the Dedicated Channel (DCH).

Uplink transmit power of DCH.

Downlink transmit power of DCH.

Inter-frequency hard handover triggered by cell load: When the load of a cell on the

current frequency is too heavy, the system switches partial services of the cell to an

adjacent cell on another frequency.

Inter-frequency hard handover triggered by moving speed of the UE: It is mainly used on

the HCS network. UEs with quick moving speed are carried in macro cells and those with

slow moving speed in micro cells for appropriate traffic distribution in cells, making full

use of system resources and enhancing system performance.

For non-double-receiver terminals in WCDMA, compressed mode must be initiated for

inter-frequency measurement. However, initiation of compressed mode has impact on

the performance of both the system and the UE. Therefore, compressed mode must not

be initiated unless absolutely necessary (for example, when the quality of the current

serving carrier frequency worsens).

2.4 ZWF21-03-004 Inter-RAT Mobility (GSM)

Inter-RAT mobility refers to the mobility management conducted when a UE switches

from one UMTS to another one. It only applies to the mobility management for UEs that



switch from UTRAN to RATx (the mobility management from RATx to UTRAN belongs to

the strategy of RATx).

This feature requires the UE to support both WCDMA and RATx. Moreover, the RATx

also needs to offer related features to support inter-RAT handover. The features required

by WCDMA are described below.

WCDMA-to-GSM handover supports the following services:

Conversational services

Videophone service fallback to ordinary voice service. (3GPP R6)

PS transferred to GPRS/GERAN

For a WCDMA-to-GSM handover combining CS and PS RAB, the system first switches

CS services to GERAN first, and then the RNC releases the PS on lu interface upon

receiving the context request message from the CN. The UE activates the PS service on

GERAN upon the release of CS services.

In WCDMA:

UTRAN-to-GERAN mobility of CS services in connected mode is implemented

through a CS service handover procedure.

UTRAN-to-GERAN mobility of PS services in CELL_DCH state is implemented

through a cell reselection procedure (PS service handover) triggered on the network

side.

UTRAN-to-GERAN mobility of PS services in CELL_FACH /URA_PCH state is

implemented through a cell reselection procedure triggered by UE.

Load-based UTRAN-to-GERAN handover of PS services in CELL_FACH state is

implemented through a cell reselection procedure triggered on the network side.

Inter-system mobility in connected mode must be accompanied by an inter-system

relocation.

The factors triggering a WCDMA-to-GSM handover include radio quality and cell load.



Inter-RAT handover triggered by radio quality: An inter-RAT measurement is initiated

when the quality of the frequency where the UE is currently located worsens and

inter-frequency measurement initiation conditions cannot be met or the quality of other

frequencies is also poor, and then the UE is handed over to the cell of RATx based on

the inter-RAT measurement result. The quality of the frequency where the UE is currently

located is measured according to the following four standards (For details, see “7 GSM

Inter-RAT Handover Policy”):

PCPICH quality of the cell in the current serving carrier frequency.

Uplink Block Error Rate (BLER) of the Dedicated Channel (DCH).

Uplink transmit power of DCH.

Downlink transmit power of DCH.

Inter-RAT handover triggered by cell load: When the load of a cell in the current UTRAN

system is too heavy, the system switches partial services of the cell to an adjacent cell in

GERAN.


inter-RAT measurement. However, initiation of compressed mode has impact on the

performance of both the system and the UE. Therefore, compressed mode must not be

initiated unless absolutely necessary (for example, when the quality of the current

serving carrier frequency worsens).

2.5 ZWF21-03-006 Inter-RNC Handover with Iur Support

This feature supports maintaining communication continuity in the case of a UE in

CELL_DCH state moving among inter-RNC cells. The Iur interface is configured between

different RNCs to ensure that a UE maintains the current connection with the CN when

being handed over in the coverage areas of different RNCs. There is no need to trigger

an SRNS relocation, so that the effect of SRNS relocation on service quality is reduced.



2.6 ZWF21-03-008 Directed Signalling Connection

Re-establishment

This feature enables the RNC to allow the UE with ongoing PS services to trigger a

DSCR procedure to interoperate with the RNC that cannot support the SRNS relocation

procedure.

2.7 ZWF21-03-009 Coverage Based Handover

This feature allows the system to utilize the measurement report to judge the quality of

radio links and thus to perform handovers to guarantee the service quality for users in the

case of changing network coverage conditions.

The RNC can control the UE to perform the intra-frequency, inter-frequency and

inter-RAT measurement and judge the radio link quality according to the measurement

result of event-triggered reports to trigger various handovers: soft/softer handover,

intra-frequency hard handover, inter-frequency hard handover and inter-RAT handover.

The RNC can also be configured with different handover parameters for different

services.

2.8 ZWF21-03-010 Compressed Mode


inter-RAT/inter-frequency measurement. When compressed mode is used, some

timeslots are specially used for inter-frequency/inter-RAT measurement instead of data

transmission during transmission and reception.

2.9 ZWF21-03-011 Neighboring Cells Priorities

This feature can be used to configure different priorities for different cells in the adjacent

cell list. It allows a UE to hand over to an adjacent cell of high priority with a higher

success rate to improve the handover performance of the system.



2.10 ZWF21-03-012 Handover Based on Dedicated

Downlink Transmit Power

This feature enables handovers based on the dedicated downlink transmit power, and

applies to the following scenario: The signal of pilot frequency is acceptable, but the

dedicated downlink transmit power has become very high, requiring the UE to hand over

to an inter-frequency or inter-RAT adjacent cell.

2.11 ZWF21-03-012 Handover Based on Dedicated

Uplink Transmit Power (UE)

This feature enables handovers based on the dedicated uplink transmit power, and

applies to the following scenario: The signal of pilot frequency is acceptable, but the

dedicated uplink transmit power has become very high, requiring the UE to hand over to

an inter-frequency or inter-RAT adjacent cell to avoid large interference on other users.

2.12 ZWF21-03-013 Quality-Based Handover

This feature enables handovers based on the uplink BLER and applies to the following

scenario: The signal of pilot frequency is acceptable, but the uplink of the UE is very poor

due to uplink interference or other reasons. In the event of the outer loop power control

failure, the UE needs to be handed off to an inter-frequency or inter-RAT adjacent cell as

quick as possible to avoid call drops.

2.13 ZWF21-03-020 SRNS Relocation

This feature supports that a UE in CELL_DCH state transfers services to a new RNC

when moving among adjacent RNC cells. When there is no Iur interface between RNCs,

SRNS relocation can maintain service continuity. When there is an Iur interface between

RNCs, SRNS relocation triggered timely after a handover via Iur is completed can reduce

the transmission resource consumption at the Iur interface.



2.14 ZWF21-03-022 IMSI-based Handover

The scope of authorized cells is configured based on the IMSI information on the network

side. The IMSI information is resolved through the CommonID on lu interface during a

service setup or handover, and the UE is not allowed to access or to be handed over to

unauthorized cells.

2.15 ZWF21-03-023 Inter-RAT PS Handover (GSM)

This feature shortens PS service interruption when there is a handover between

inter-RAT adjacent cells. With this feature, PS service continuity is enhanced, especially

for the real-time packet service with higher QoS requirements, and therefore user

experience is improved.

2.16 ZWF21-03-024 DTM Handover

This feature guarantees service continuity for UEs that have CS and PS combined

services during inter-RAT movement. It improves user experience.

When a UE with CS and PS services simultaneously moves between inter-RAT adjacent

cells, these CS and PS services are handed over to an inter-RAT cell in parallel via DTM

mechanism.

2.17 ZWF21-03-025 NACC

The PS service will be interrupted when it is handed over to GERAN via cell reselection

procedure, which leads to bad user experience. Network Assisted Cell Change (NACC)

reduces the duration of UE inter-RAT cell reselection procedure by sending system

information to the RNC in advance.



2.18 ZWF21-03-026 Target Cell Load Based Inter-RAT

Handover

This feature enables the RNC to get load information of 2G or EUTRAN adjacent cells.

The RNC selects an adjacent cell with a lower load as target cell when the UE is handed

over to GSM or EUTRAN from UMTS.

2.19 ZWF21-05-022 Handover Strategy Based on Service

Type

This feature determines whether and when services can be handed over to GSM based

on the service handover attribute in the RAB assignment request message.

This feature determines whether services can be handed over to EUTRAN based on the

EUTRAN service handover attribute in the RAB assignment request message.

2.20 ZWF21-03-014 Enhanced Iur-g

The feature supports the enhanced Iur-g interface between GERAN BSC and 3G RNC. It

enables the RNC to get capability and load information of 2G cells. By employing the

interface, inter-RAT load balance can be achieved, inter-RAT handover success ratio is

improved and handover delay is decreased.

2.21 ZWF21-03-110 UTRAN<->LTE PS Handover

Strategy

The feature supports UTRAN<->LTE PS Handover when the signal quality is poor, so

that the continuity of PS services between UTRAN and LTE is ensured.



2.22 ZWF21-03-120 Single Radio Voice Call Continuity

(SRVCC)

This feature ensures the continuity of voice services between UTRAN and LTE during

inter-RAT handovers. The RNC can transform the voice call from the VoIP/IMS packet

domain to the legacy circuit domain.

2.23 ZWF21-03-101 CS Fallback (CSFB)

This feature ensures the continuity of voice services between UTRAN and EUTRAN.

When CSFB traffic initializes a PS handover from EUTRAN to UTRAN, the

corresponding CS traffic can be set up in UTRAN later.

2.24 ZWF21-03-050 Handover Optimization in

Weak-Coverage

This feature supports enhancing handover performance. In the weak-coverage area, the

system decides the link quality of the target cell that is suitable for adding a new link into

macro diversity or serving cell change, and only when the quality is above the threshold,

the corresponding soft handover procedure or serving cell change procedure can be

initiated. This can increase the handover success rate, decrease call drop rate, and

improve RAN network performance and service experience.

2.25 ZWF23-03-001 HS-DSCH Serving Cell Change

The HS-PDSCH has only one serving cell. During an intra-system soft handover, if an

HS-PDSCH exists before and after the handover when the best cell changes (triggered

by 1D event), an HS-PDSCH serving cell change is triggered. If there is an HS-PDSCH

before and after a hard handover, the HS-PDSCH serving cell must change.



2.26 ZWF23-03-002 HS-DSCH handover to/from DCH

When a UE roams between HSDPA cell and R99 cell, a migration between the

HS-DSCH and DCH occurs to maintain service continuity.

This feature can be used for intra-RNC handover or inter-RNC handover.

2.27 ZWF23-03-003 HS-DSCH Inter-RAT Reselection

This feature ensures service continuity when HSDPA users moving from a UMTS cell to

a GSM cell. When an HSDPA user with services carried on HS-DSCH channel need be

handed over from a UTMS cell to a GSM cell, the RNC can hand over the UE to connect

the GSM cell directly without falling HS-DSCH back to DCH before the inter-RAT

handover.

2.28 ZWF23-03-004 HSDPA Soft/Softer Handover of

A-DPCH

The HSDPA service supports soft/softer handovers of associated DPDCH/DPCCH,

where the policy is identical with that of a common soft/softer handover.

2.29 ZWF23-03-005 HSDPA over Iur

This feature enables data transmission on HS-DSCH to be retained without falling

HS-DSCH back to DCH when an HSDPA subscriber is handed over between different

RNCs over Iur.

2.30 ZWF25-03-001 HSUPA Soft/Softer Handover

The HSUPA service supports soft/softer handovers of associated DPDCH/DPCCH,

where the policy is identical with that of a common soft/softer handover.



2.31 ZWF25-03-002 E-DCH Serving Cell Change Inside

Active Set

The E-DCH has only one serving cell, so if an E-DCH exists before and after an

intra-system soft handover when the best cell changes (triggered by 1D event), a change

of the E-DCH serving cell is triggered. If there is an E-DCH before and after a hard

handover, the E-DCH serving cell must change.

2.32 ZWF25-03-003 E-DCH Intra-frequency Hard

Handover

The procedure of an E-DCH intra-frequency hard handover is similar with a DCH

intra-frequency hard handover. If the target cell supports HSUPA, an intra-frequency

hard handover is conducted with an E-DCH serving cell change, otherwise, E-DCH will

fall back to DCH.

2.33 ZWF25-03-004 E-DCH Inter-frequency Hard

Handover

The procedure of an E-DCH inter-frequency hard handover is similar with a DCH

inter-frequency hard handover. If the target cell supports HSUPA, an inter-frequency

hard handover is conducted with an E-DCH serving cell change, otherwise, E-DCH will

fall back to DCH.

2.34 ZWF25-03-005 HSUPA over Iur

This feature enables data transmission on E-DCH to be retained without falling E-DCH

back to DCH when an HSUPA subscriber is handed over between different RNCs over

Iur.



2.35 ZWF25-03-012 HSUPA Inter-RAT Reselection

This feature ensures service continuity when HSUPA users moving from a UMTS cell to

a GSM cell. When an HSUPA user with services carried on E-DCH channel need be

handed over from a UTMS cell to a GSM cell, the RNC can hand over the UE to connect

the GSM cell directly without falling E-DCH back to DCH before the inter-RAT handover.

3 Compressed Mode Strategy

3.1 Introduction to Compressed Mode


inter-RAT/inter-frequency measurement. When compressed mode is used, some

timeslots are specially used for inter-frequency/inter-RAT measurement instead of data

transmission during transmission and reception.. The following two ways can generate

compressed mode frames:

1 Halving of Spreading Factor (SF)

By halving the SF, the bandwidth can be increased so that some timeslots in one

radio frame can be specially assigned for inter-frequency/inter-RAT measurement

and some can be specially assigned for data transmission. This transmission

strategy is generally used in services that have high requirements for delay and

minimum data rate, for example, CS- and S-type PS data services.

2 Higher Layer Scheduling

The higher layer scheduling is in nature a strategy in which the higher layer adjusts

and controls the data transmission rate. Some timeslots in a radio frame can be

specially assigned for inter-frequency/inter-RAT measurement and some can be

specially assigned for data transmission while the bandwidth remains unchanged.

This strategy is generally used for non-real-time services that have low

requirements for delay, for example, I/B-type PS data services.



After compressed mode is initiated, the GAP used for transmission/reception

(measurement) can be placed either within one radio frame or between two radio frames,

see Figure 3-1.

Figure 3-1 Transmission Gap (TG) Position

In the protocol TS 25.212, the Transmission Gap Length (TGL) can be set to 3, 4, 5, 7,

10 and 14 timeslots. The TG may start from any timeslot in a frame. When the TG spans

two consecutive frames, each frame at least has 8 non-compressed timeslots.

Figure 3-2 shows the parameters involved in compressed mode. The Transmission Gap

Pattern Sequence (TGPS) consists of consecutive TG patterns (TG pattern 1). One or

two TGs are defined in a TG pattern. The starting timeslot No. of the first TG is

determined by the parameter TGSN. The number of timeslots between starting timeslots

of two TGs in the TG pattern is determined by the parameter TGD. The first TGL is

determined by the parameter TGL1, and the second by the parameter TGL2. If the

parameter TGD is not defined, it means that there is only one TG in the TG pattern. The

length of a TG pattern is determined by the parameter TGPL1. The number of repeats of

a TG pattern is determined by the parameter TGPRC.

#14#Nfirst-1

(1) Single-frame method

(2) Double-frame method

First radio frame Second radio frame

Radio frameTransmission gap

Transmission gap

#0

#14

#Nlast+1

#Nfirst-1 #Nlast+1#0



Figure 3-2 Parameters of Compressed Mode

Transmission

gap 2

TGSN

TGL2

TG pattern 1

#TGPRC

gap 1

Transmission

TGD

TGPL1

TG pattern 1

TGL1

#1 #2 #3 #4 #5

TG pattern 1 TG pattern 1 TG pattern 1 TG pattern 1 TG pattern 1

3.2 Compressed Mode Strategy

If the UE capability message indicates that compressed mode is required during an FDD

inter-frequency or inter-RAT measurement procedure, compressed mode is initiated

upon the initiation of an inter-frequency or inter-RAT measurement. Compressed mode

must be disabled in either of the following scenarios: 1) Deleting the inter-frequency

measurement while keeping the inter-RAT measurement disabled. 2) Deleting the

inter-RAT measurement while keeping the inter-frequency measurement disabled.

As described in the previous section, the strategy of halving of SF does not affect the

real-time rate of services, while that of higher layer scheduling reduces the real-time rate

of services. For RT services, only the first strategy can be used to ensure delay and

transmission rate. For NRT services, both the first and second strategies can be used

because of their low requirements for delay and rate.

The above rules only apply to DCH/DCH. For HS-DSCH or E-DCH, only higher layer

scheduling is supported. An exception is that if SF/2 method is configured but has not

been activated, and currently the services are using UL SF4 and compressed mode

need to be activated, the RNC can modify it to higher layer scheduling method.



Compressed mode of all services on ZTE networks use identical parameters as listed

below:

Table 3-1 Parameters of Compressed Mode

GSM Adjacent Cell

Measurement

FDD Adjacent Cell Measurement

TGSN 4 (Slots) 3 (Slots)

TGL1 7 (Slots) 7 (Slots)

TGD Not configured Not configured

TGPL1 8 (Frames) 8 (Frames)

As shown in the table, when the TGSN is 4 (GSM) or 3 (FDD), TGL1=7, all GAPs of

compressed mode on ZTE networks in the same radio frame (one radio frame in FDD

has 15 slots), that is, single frame mode is uniformly used.

For all commercial terminals in the current market, compressed mode can be initiated

directly when services are carried on HS-DSCH. Whether HS-DSCH falls back to DCH

before the initiation of compressed mode is controlled through the parameter

HsdpaCmAssoMode. If the parameter value is “Serial”, HS-DSCH needs to fall back to

DCH before the initiation of compressed mode. If the parameter value is “Parallel”,

compressed mode is initiated directly.

Moreover, whether E-DCH falls back to DCH before the initiation of compressed mode is

controlled through the parameter HsupaCmAssoMode (UHspa). If the parameter value is

“Serial”, E-DCH needs to fall back to DCH (the reconfigured target rate is min (max

(DRBC lowest of rate grades, GBR), MaxBR), for DRBC rate grades, see ZTE UMTS

DRBC Algorithm Feature Guide) before the initiation of compressed mode. If the

parameter value is “Parallel”, compressed mode is initiated directly. Figure 3-3 shows

the procedure in which E-DCH falls back to DCH before the initiation of compressed

mode.



Figure 3-3 Procedure for E-DCH Fallback to DCH Prior to Initiation of Compressed

Mode

NodeBRNC

Radio Link Reconfiguration Prepare

UE

Measurement Report (Event 2d)

Radio Link Reconfiguration Commit

Radio Bearer Reconfiguration Complete

Radio Bearer Reconfiguration

(E-DCH to DCH, DPCH compressed mode info)

Radio Link Reconfiguration Ready

HS-DSCH/E-DCH

Compressed Mode Command

Measurement Control

E-DCH Downgrade to

DCH, configure

compressed mode

Active compressed mode

For a part of commercial terminals in the current market, compressed mode cannot be

initiated when services are carried on E-DCH. Whether a UE supports “Initiate

compressed mode for services carried on E-DCH” is not specified in 3GPP. Therefore,

when services are carried on E-DCH, the RNC does not know whether a UE can “Initiate

compressed mode for services carried on E-DCH”. To deal with these UEs, when

HsupaCmAssoMode is set to “Parallel” and the current services involve HSUPA services,

the RNC executes “„the safeguarded strategy after the initiation of HSUPA parallel

compressed mode fails” as follows:

When the RNC forwards the Measurement Control message to a UE for initiating

compressed mode and the UE returns the Measurement Control Failure message, the

RNC will reconfigure E-DCH to DCH before initiating compressed mode. Afterwards, if

the UE need switch from DL HS-DSCH/UL DCH to DL HS-DSCH/UL E-DCH based on

traffic volume measurement reports during a call process, the RNC will not allow it if the

UE is in compressed mode.

In the procedure of a service setup, state transition, call re-establishment and relocation

from other RNCs to the local RNC, the RNC will configure accompanying compressed



mode by default through RADIO BEARER SETUP/RADIO BEARER

RECONFIGURATION/PHYSICAL CHANNEL RECONFIGURATION to UE and RADIO

LINK SETUP REQUEST/RADIO LINK RECONFIGURATION to Node B. Figure 3-4

shows the procedure of configuring accompanying compressed mode. For state

transitions from CELL_PCH or CELL_FACH to CELL_DCH, GResPara14 is introduced

to control whether the RNC will configure accompanying compressed mode. If

GResPara14 is set to “1”, accompanying compressed mode will be configured, otherwise

the RNC will not configure accompanying compressed mode, so that the signaling

message length of the radio interface can be decreased, and dedicated compressed

mode will be configured when compressed mode needs to be activated.

In the event that compressed mode needs to be initialized (for example, event 2D is

reported), the neighboring cell relation changes or the best cell changes (for example,

the best cell changes from a cell that does not support inter-frequency or inter-RAT

handover to a cell that only supports inter-frequency handover), if compressed mode has

not been configured, the RNC will configure dedicated compressed mode through

PHYSICAL CHANNEL RECONFIGURATION/RADIO BEARER RECONFIGURATION to

the UE and RADIO LINK RECONFIGURATION to the Node B. Figure 3-5 shows the

procedure of configuring dedicated compressed mode.

Figure 3-4 Procedure for Configuring Accompanying Compressed Mode

UE NodeB RNC CN

RAB Assignment Request



Radio Bearer Setup

(DPCH compressed mode info-> TGPRC,TGSN,TGL1…)

Radio Bearer Setup Complete

RAB Assignment Response

Service setup,

configure

accompanying

compressed mode

……

Compressed Mode Command(Active Pattern Sequence Information

->TGCFN)

Measurement Control(DPCH compressed mode status info->TGCFN)

Active

compressed mode

Radio Link Reconfiguration Prepare(Transmission Gap Pattern Sequence Information

->TGSN, TGL1, TGPL1…)



Figure 3-5 Procedure for Configuring Dedicated Compressed Mode

UE NodeB RNC CN

RAB Assignment Request

Radio Link Reconfiguration Prepare



Radio Bearer Setup

Radio Bearer Setup CompleteRAB Assignment Response

Physical Channel Reconfiguration(DPCH compressed mode info-> TGPRC,TGSN,TGL1…)

Physical Channel Reconfiguration Complete

Service setup

Configure Dedicated

compressed mode

Radio Link Reconfiguration Prepare(Transmission Gap Pattern Sequence Information

->TGSN, TGL1, TGPL1…)



……

Compressed Mode Command(Active Pattern Sequence Information

->TGCFN)

Measurement Control(DPCH compressed mode status info->TGCFN)Active compressed

mode

……Need to initialize the

compressed mode(such as event 2D is reported)

Note: TGCFN is the connection frame number of the first frame of the first pattern within

the Transmission Gap Pattern Sequence (TGPS).

3.3 Compressed Mode Configuration Strategy via RNC

For inter-RNC handovers, some vendors do not support accompanying compressed

mode. To guarantee the normal procedure via IUR, ZTE performs the following two

special strategies:

The DRNC does not support accompanying compressed mode

RncFeatSwitchBit9 indicates whether the neighboring RNC supports accompanying

compressed mode. If compressed mode has not been activated on the SRNC side, the

method of configuring compressed mode is decided by RncFeatSwitch Bit9. If

compressed mode has been activated already, RncFeatSwitch Bit9 is invalid, and the

SRNC must configure accompanying compressed mode and activate it for the DRNC.



DRNC conditionally supports accompanying compressed mode

Some vendors do not support inter-frequency and inter-RAT accompanying compressed

mode simultaneously. CompMdCfgStra (ULogicalRnc) indicates the strategy of

accompanying compressed mode configuration. When inter-frequency and inter-RAT

neighboring cells exist, if the value of CompMdCfgStra (ULogicalRnc) is “0”, the RNC

configures two types of accompanying compressed mode (inter-frequency and inter-RAT). If

the value of CompMdCfgStra(ULogicalRnc) is “1”, the RNC configures only one type of

accompanying compressed mode (inter-frequency or inter-RAT) based on the specific

value of IfOrRatHoSwch(UCelInfoFDD) (For the details of IfOrRatHoSwch, see 5.10

Inter-Frequency and Inter-RAT Measurement Choice).

For inter-RNC handovers, some vendors have compatibility problems of compressed

mode.

To guarantee the normal procedure via IUR, ZTE performs the following special strategy:

The DRNC does not allow the compressed mode command via Iur to activate

compressed mode

Some vendors do not allow the compressed mode command via Iur to activate

compressed mode, RncFeatSwitchBit17 indicates the strategy for this situation. When

CS traffic and Iur link exist, if RncFeatSwitchBit17 is “0”, the DRNC does not activate

compressed mode even when needed (if compressed mode is already activated, the

DRNC does not take account of RncFeatSwitchBit17). When CS traffic and Iur link exist,

if RncFeatSwitchBit17 is “1”, the DRNC activates compressed mode when needed.

4 Intra-Frequency Handover Strategy

Intra-frequency handover refers to a handover performed between cells of the same

frequency in UTRAN. An intra-frequency handover can be triggered based on EcNo or

RSCP measurement through the parameter IntraMeasQuan (UUtranCellFDD).

Intra-frequency handover is the measurement-based handover. Intra-frequency

measurement contains active set measurement, monitored set measurement and

detected set measurement.



The active set refers to a set of cells retaining a radio connection with the UE.

The monitored set refers to a set of cells retaining no radio connection with the UE but

requesting a measurement by sending an intra-frequency measurement control message

to the UE.

The detected set refers to a set of intra-frequency cells other than those in the active set

and monitored set.

4.1 Intra-Frequency Measurement

When conducting an intra-frequency measurement, the UE needs to implement layer 3

filtering for the measurement results to avoid measurement fluctuations, and then make

event decisions and report by using filtered values. The layer 3 filter formula is as follows:

nnn MaFaF 1)1(

Where,

Fn-1 refers to the result of the last filter.

Fn refers to the result of the current measurement filter.

Mn refers to the current measurement result.

a = 1/2(k/2)

refers to the filter coefficient calculated based on the filter factor K (FilterCoeff

(For event-triggered measurements, if the measurement quantity is EcNo, this parameter

is obtained from UIntraEcNoEvMeas; if the measurement quantity is RSCP, this

parameter is obtained from UIntraRscpEvMeas. For detected set measurements, if the

measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeasForD;

if the measurement quantity is RSCP, this parameter is obtained from

UIntraRscpEvMeasForD. For periodical measurements, if the measurement quantity is

EcNo, this parameter is obtained from UIntraEcNoPrdMeas; if the measurement quantity

is RSCP, this parameter is obtained from UIntraRscpPrdMeas)).



4.1.1 Introduction to Intra-Frequency Measurement

Intra-frequency measurement refers to a measurement performed on intra-frequency

cells. It only supports event-triggered reporting. The event-triggered reporting method

means the UE judges whether intra-frequency events are met based on the quality

measurement result of the cell PCPICH. If so, it reports intra-frequency events (including

such information as event ID and target cell) to the RNC.

A series of intra-frequency measurement events are defined in 3GPP as the judgment

and trigger criteria for intra-frequency handover.

Event 1A: A Primary CPICH enters the Reporting Range. It can be used for adding cells

to the active set.

Event 1B: A Primary CPICH leaves the Reporting Range. It can be used for deleting cells

from the active set.

Event 1C: A Non-active Primary CPICH becomes better than an active Primary CPICH. It

can be used for replacing the cell with bad quality in the active set.

Event 1D: The best cell changes. It can be used for soft/softer handover, intra-frequency

hard handover and inter-frequency load balance.

4.1.2 Measurement Control Method Related to Active Set and Monitored

set

4.1.2.1 Measurement Setup

Intra-frequency measurement parameters are configured for the UE and intra-frequency

measurements are initiated through the measurement control setup message in the

following cases:

An RRC connection is set up and enters CELL_DCH state.

CELL_FACH -> CELL_DCH.

Relocation to the current RNC from other systems or RNCs.



An intra-frequency measurement is set up again after an intra-system hard handover

(including intra- or inter-frequency hard handover).

4.1.2.2 Measurement Modification

If an intra-frequency measurement is enabled, an intra-frequency measurement

modification is triggered in the following cases:

A change of the adjacent cell list may trigger a modification of intra-frequency

measurement to modify adjacent cell parameters after a soft handover.

After the best cell changes (Event 1D), a change of intra-frequency measurement

parameters will trigger a modification of intra-frequency measurement to update

handover parameters.

If a service is added or deleted, a change of intra-frequency measurement

parameters will trigger a modification of intra-frequency measurement to update

handover parameters.

4.1.2.3 Measurement Deletion

Upon receiving an exceptional intra-frequency measurement report (for example, the

measurement report belongs to a non-existent measurement task), or before making a

decision about the relocation triggered by a soft handover, the RNC will voluntarily

release the corresponding intra-frequency measurement. When the RNC sends a

MEASUREMENT CONGROL RELEASE message for a measurement ID, the time stamp

will be recorded. If the RNC receives a measurement report for the ID, the report will be

compared between the current time and recorded time. If the difference between the

current time and recorded time exceed the threshold TResndMeaCtrlRel (URncFunction)

configured, the MEASUREMENT CONTROL RELEASE message will be resent.

Otherwise, this measurement report is ignored.

4.1.2.4 Parameter Configuration Strategies

Intra-frequency event parameter configuration:



There are seven intra-frequency measurement events (1A, 1B, 1C, 1D, 1E, 1F and

1J) in total. The number of events configured depends on the parameter

MeasEvtNum (If the measurement quantity is EcNo, this parameter is obtained from

UIntraEcNoEvMeas. If the measurement quantity is RSCP, this parameter is

obtained from UIntraRscpEvMeas), and the intra-frequency events configured

depends on the parameter MeaEvtId (If the measurement quantity is EcNo, this

parameter is obtained from UIntraEcNoEvMeas. If the measurement quantity is

RSCP, this parameter is obtained from UIntraRscpEvMeas). MeaEvtId is defined

through array, and the dimension of array is equal to MeasEvtNum, which is seven

at most.

Handover parameter configuration strategy in macro diversity:

All measurement parameters are cell-based. In macro diversity, the measurement

parameters configured in the best cell will be used as handover parameters. If the

best cell changes, the measurement parameters need to be updated at the same

time.

For inter-RNC handovers, if there is an SRNC cell in the active set, the

measurement parameters of the best cell in the SRNC will be used as handover

parameters, and if there is no SRNC cell in the active set, the measurement

parameters of the last SRNC cell in the active set will be used as handover

parameters.

Configuration of several sets of handover parameters:

The intra-frequency handover parameters can be separately configured based on

the measurement quantity, measurement report mode and service bearer type. In

this way, several sets of measurement parameters are necessitated for different

purposes. The categories are as follows:

Measurement quantity

IntraMeasQuan(UUtranCellFDD) (CPICH EcNo or RSCP)

Measurement reporting mode



Periodical or event-triggered reporting. Only event-triggered reporting is

supported, and the following parameters related to periodical reporting are

invalid: UIntraEcNoPrdMeas (UIntraEcNoPrdMeas), UIntraRscpPrdMeas

(UIntraRscpPrdMeas), PrdRptAmount (If the measurement quantity is EcNo,

this parameter is obtained from UIntraEcNoPrdMeas. If the measurement

quantity is RSCP, this parameter is obtained from UIntraRscpPrdMeas) and

PrdRptInterval (If the measurement quantity is EcNo, this parameter is

obtained from UIntraEcNoPrdMeas. If the measurement quantity is RSCP, this

parameter is obtained from UIntraRscpPrdMeas).

Service bearer type (srvCategory (UIntraMeasSrvSpec))

RT RAB Including Voice

RT RAB Excluding Voice

Single NRT on DL DCH/UL DCH

Single NRT RAB on DL HS-DSCH/UL DCH

Single NRT RAB on DL HS-DSCH/UL E-DCH

All Multi-NRT RAB on DL DCH/UL DCH

Multi-NRT RAB, HSPA is Involved and only DCHs are Used in UL

Multi-NRT RAB, HSPA is Involved and E-DCH is Used in UL

Multi RAB Including CS and PS

Not Related to Service Type (Used for detected set measurement)

Notes:

(1). When concurrent services exist and include CS+PS services, the Multi RAB

Including CS and PS configuration is indexed.

(2). When concurrent services exist and include non-CS services, the RT RAB

Excluding Voice configuration is indexed.



(3). When the above principles are met simultaneously, the first one prevails.

To facilitate parameter modification and optimization, the intra-frequency parameters are

index-organized. The index quotations are listed as follows:

Figure 4-1 Intra-frequency Handover Index Quotations

UUtranCellFDD(UUtran

CellFDD)

UIntraMeasProfile(UIntraMeasProfile)

UIntraMeasSrvSpec(UIntraMeasSrvS

pec)

UIntraMeasNoSrvSpec(UIntraMeasNo

SrvSpec)

ref1UIntraMeasProfile

UIntraEcNoPrd

Meas(UIntraEc

NoPrdMeas)

UIntraRscpPrd

Meas(UIntraRsc

pPrdMeas)

UIntraEcNoEvM

easForD(UIntra

EcNoEvMeasFo

rD)

UIntraRscpEvM

easForD(UIntra

RscpEvMeasFo

rD)

UIntraEcNoEvM

eas(UIntraEcNo

EvMeas)

UIntraRscpEvM

eas(UIntraRscp

EvMeas)

srvCategory

intraMeasQuanintraMeasQuan

intraMeasCfgNo

(UIntraEcNoEv

Meas)

intraMeasCfgNo

(UIntraRscpEvM

eas)

intraMeasCfgNo

(UIntraEcNoPrd

Meas)

intraMeasCfgNo

(UIntraRscpPrd

Meas)

intraMeasCfgNo

(UIntraEcNoEv

MeasForD)

intraMeasCfgNo

(UIntraEcNoEv

MeasForD)

Note: When a new cell is set up, the value of intialHoCelSelScene (UIntraMeasProfile)

(0:Outdoor Scene, 1:High-Mobility Outdoor Scene, 2:Indoor Scene, 3:Subway/tunnel

Scene) is determined according to the actual cell scene (indicated by

HoCelSelScene(UUtranCellFDD)), and the available intra-frequency measurement

profile corresponding to intialHoCelSelScene is configured for the cell.

Before intra-frequency handover parameters are obtained,

profileId(UIntraMeasProfile) of the cell is found based on



ref1UintraMeasProfile(UUtranCellFDD), and then, in UintraMeasProfile

configuration items, the next level managed object is obtained according to the

current measurement application type: For event-triggered measurements,

“Intra-frequency Measurement Configuration Related to Traffic Category Object

ID(UIntraMeasSrvSpec)” is selected. For periodical measurements or detected set

tracing applications, “Intra-frequency Measurement Configuration Unrelated to

Traffic Category Object ID (UIntraMeasNoSrvSpec)” is selected.

In the managed object decided above, “Intra-Frequency Measurement

Configuration No. (IntraMeasCfgNo)” is found based on “Traffic Category

(srvCategory(UIntraMeasSrvSpec))” and “Measurement Quantity((intraMeasQuan)”.

Finally, the corresponding intra-frequency handover measurement parameters are

found. The details are as follows:

(1). For event-triggered measurements:

If the measurement quantity is EcNo, the measurement parameters are obtained

from the managed object UIntraEcNoEvMeas.

If the measurement quantity is RSCP, the measurement parameters are obtained

from the managed object UIntraRscpEvMeas.

(2). For periodical measurements:


from the managed object UIntraEcNoPrdMeas.


from the managed object UIntraRscpPrdMeas.

Note: Periodical reporting is not supported currently, so the measurement

parameters related to the managed object UIntraEcNoPrdMeas or

UIntraRscpPrdMeas are invalid.

(3). For detected set measurements:


from the managed object UIntraEcNoEvMeasForD.




from the managed object UIntraRscpEvMeasForD.

Correspondence between other parameters that need to be filled into the

intra-frequency measurement control message

Measurement Quantity and Measurement Report Criteria are automatically filled by the

system based on IntraMeasCfgNote.

For the cells of the neighbor RNC, if the value of Primary CPICH Power Configuration

Tag (PcpichPwrPre(UExternalUtranCellFDD)) is TURE, the cell information of the

intra-freq measurement should include the Primary CPICH Power for this cell. Otherwise

the cell information of the intra-freq measurement should not include the Primary CPICH

Power for this cell.

4.1.3 Neighboring Cells Configuration

During the neighboring cells configuration, the adjacent cell list used for reselection in

non-CELL_DCH state and for handovers in CELL_DCH state can be configured

separately. During handovers, target cells are selected by neighboring cells configuration

state (StateMode (UUtranRelation)). When the UE is in macro diversity state, the

neighboring cell list is a combination of neighboring cell lists of each cell in the active set,

so the number of intra-frequency neighboring cells may exceed 32, which is the

maximum number specified by the protocol. If the number of intra-frequency neighboring

cells exceeds 32, some cells must be deleted to ensure that there are only 32

intra-frequency neighboring cells. With minimal impact on the UEs in the active set, these

dropped cells are those with poorer signal quality or remoter geographical location.

Therefore, each intra-frequency neighboring cell is configured with a priority.

4.1.3.1 Cell Priority Configuration

The OMCR configuration parameter MeasPrio (UUtranRelation) defines the priority of

adjacent cells with three values (0: High priority; 1: Medium priority; 2: Low priority). The

value of MeasPrio (UUtranRelation) must be set by the network planning engineer based

on the existing network conditions (for example, adjacent cell quality and geographical

location of adjacent cell). Figure 4-2 shows the cell priority configuration based on the



geographical location of adjacent cells. For example, for the configuration of cells

adjacent to the innermost gray cell, there are three layers of adjacent cells surrounding

the gray cell, and they are differentiated from one another with yellow (0: Top priority),

blue (1: Medium priority) and red (2: Low priority).

Figure 4-2 Cell Priority Configuration

Source Cell

Priority 0

Priority 1

Priority 2

4.1.3.2 Strategy for Adjacent Cells Exceeding 32

As specified in the protocol, the maximum number of adjacent cells is 32 (including the

source cell). When the UE is in macro diversity state, the total number of intra-frequency

adjacent cells in the macro diversity may exceed 32, so some strategies are required to

control the number within 32, including:

Priority combination strategy

If a cell is adjacent to several cells in the active set, that is, the priority levels configured

for this cell may vary, the priority levels of this cell are combined and the highest priority

is taken as the priority of the cell.

Sorting strategy

If the total number of adjacent cells in the active set is 32, the system prioritizes them in

descending order and places the cells in excess of 32 into the adjacent cell reserve list,



which can buffer at most 64 truncated intra-frequency cells.

The priority levels of adjacent cells in the intra-frequency adjacent cell list will be updated

whenever Event 1A/1B/1C/1D is triggered. If Event 1B is triggered and the number of

adjacent cells is less than 32, the system selects cells from the reserve list in descending

order of priority and places them into the intra-frequency adjacent cell list. The number of

cells that can be selected: min (32 – Number of existing cells in the intra-frequency

adjacent cell list, Number of cells in the reserve list).

4.2 Handling Mechanism for Periodical Reporting of

Intra-Frequency Handover Measurement

The periodical reporting is that a report of intra-frequency measurement result is sent by

the UE periodically based on the periodical report interval (PrdRptInterval (If the

measurement quantity is EcNo, this parameter is obtained from UIntraEcNoPrdMeas. If

the measurement quantity is RSCP, this parameter is obtained from UIntraRscpPrdMeas)

and the amount of periodical reports (PrdRptAmount (If the measurement quantity is EcNo,

this parameter is obtained from UIntraEcNoPrdMeas. If the measurement quantity is

RSCP, this parameter is obtained from UIntraRscpPrdMeas)) configured by RNC. The

RNC judges intra-frequency handover events in accordance with the intra-frequency

event rule defined in the protocol by referring to the cell quality periodically reported by

the UE. If several decision conditions are concurrently met, the RNC will process events

in the sequence of 1D, 1A, 1C and 1B. Currently, periodical reporting mode is not

supported.

A long interval set in periodical reporting mode may result in call drop due to handover

delay. Therefore, it is recommended to set the interval to a low value. However, setting a

short interval will increase the signaling load of radio interface and easily lead to

signaling congestion, so event-triggered reporting mode is generally preferred.



4.3 Intra-Frequency Handover Decision

4.3.1 Event 1A-Triggered Handover

Event 1A means the quality of a certain cell outside the active set ameliorates. Upon

receiving Event 1A, the RNC adds the corresponding target cell into the active set to

enhance the gain of macro diversity. When the cell meets the conditions in the following

formula, the UE reports Event 1A to the RNC:

/2)H(RLogM10W)(1MLog10WCIOLogM10 1a1aBest

N

1i

iNewNew

A

The meanings of all parameters are described as follows:

R1a: Refers to the reporting range of Event 1A. It is used to control the extent of difficulty

in adding a cell into the active set (RptRange [MAX_INTRA_MEAS_EVENT] (For

event-triggered measurements, if the measurement quantity is EcNo, this parameter is

obtained from UIntraEcNoEvMeas, if the measurement quantity is RSCP, this parameter

is obtained from UIntraRscpEvMeas. For detected set measurements, if the

measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeasForD,


UIntraRscpEvMeasForD)).

H1a: Refers to the reporting hysteresis of Event 1A. It is used to control the extent of

difficulty in adding a cell into the active set (Hysteresis[MAX_INTRA_MEAS_EVENT]

(For event-triggered measurements, the measurement quantity is EcNo, this parameter

is obtained from UIntraEcNoEvMeas, if the measurement quantity is RSCP, this





MNew: Refers to the measurement of the to-be-evaluated cell outside the active set.

CIONew: Refers to the offset of the cell outside the active set in relation to other cells

(CellIndivOffset (UUtranRelation)).



Mi: Refers to the mean measurement value of the cells other than the best cell in the

active set.

NA: Refers to the number of cells other than the best cell in the active set.

MBest: Refers to the measurement of the best cell in the active set.

W: Refers to the weight (W[MAX_INTRA_MEAS_EVENT] (For event-triggered

measurements, if the measurement quantity is EcNo, this parameter is obtained from

UIntraEcNoEvMeas., if the measurement quantity is RSCP, this parameter is obtained

from UIntraRscpEvMeas. For detected set measurements, if the measurement quantity

is EcNo, this parameter is obtained from UIntraEcNoEvMeasForD, if the measurement

quantity is RSCP, this parameter is obtained from UIntraRscpEvMeasForD)) of the best

cell to the rest cells in the active set in evaluation standards.

From the formula, it can be concluded that the probability of triggering Event 1A can be

increased by either increasing R1a (Event 1A meets the reporting range conditions) or

decreasing H1a (Decision hysteresis range. Otherwise, probability of triggering Event 1A

can be reduced.

Event 1A supports event-triggered periodical reporting, that is, once Event 1A meets the

reporting range of quality standards, the UE reports Event 1A periodically

(EvtRptInterval[MAX_INTRA_MEAS_EVENT] (For event-triggered measurements, if the

measurement quantity is EcNo, this parameter is obtained from UIntraEcNoEvMeas, if

the measurement quantity is RSCP, this parameter is obtained from UIntraRscpEvMeas.

For detected set measurements, if the measurement quantity is EcNo, this parameter is

obtained from UIntraEcNoEvMeasForD, if the measurement quantity is RSCP, this

parameter is obtained from UIntraRscpEvMeasForD)) until this event does not meet

reporting conditions or the reporting times reach the maximum allowed times

(EvtRptAmount[MAX_INTRA_MEAS_EVENT] (For event-triggered measurements, if the





parameter is obtained from UIntraRscpEvMeasForD)).



There is a restriction on the number of radio links in active set, so Event 1A will not be

reported once the number of cells in the active set reaches the threshold

(RptDeactThr[MAX_INTRA_MEAS_EVENT](For event-triggered measurements,, if the






4.3.2 Event 1B-Triggered Handover

Event 1B indicates the quality deterioration of a certain cell in the active set. Upon

receiving Event 1B, the RNC may delete the cell from the active set. When the cell meets

the conditions in the following formula, the UE reports Event 1B to the RNC:

/2)H(RLogM10W)(1MLog10WCIOLogM10 1b1bBest

N

1i

iOldOld

A

R1b: Refers to the reporting range of Event 1B. It is used to control the extent of difficulty

in dropping a cell from the active set (RptRange [MAX_INTRA_MEAS_EVENT] (For

event-triggered measurements, if the measurement quantity is EcNo, this parameter is

obtained from UIntraEcNoEvMeas, if the measurement quantity is RSCP, this parameter

is obtained from UIntraRscpEvMeas. For detected set measurements, if the




H1b Refers to the reporting hysteresis of Event 1B. It is used to control the extent of

difficulty in dropping a cell from the active set (Hysteresis[MAX_INTRA_MEAS_EVENT]









MOld: Refers to the measurement of the to-be-evaluated cell in the active set.

CIOOld: Refers to the offset of the cell in active set in relation to other cells

(CellIndividualOffset (UUtranCellFDD)).

Mi: Refers to the mean measurement value of the cells other than the best cell in the

active set.

NA: Refers to the number of cells other than the best cell in the active set.

MBest: Refers to the measurement of the best cell in the active set.

W: Refers to the weight (W[MAX_INTRA_MEAS_EVENT] (For event-triggered

measurements, if the measurement quantity is EcNo, this parameter is obtained from

UIntraEcNoEvMeas, if the measurement quantity is RSCP, this parameter is obtained

from UIntraRscpEvMeas. For detected set measurements, if the measurement quantity

is EcNo, this parameter is obtained from UIntraEcNoEvMeasForD, if the measurement

quantity is RSCP, this parameter is obtained from UIntraRscpEvMeasForD)) of the best

cell to the rest cells in the active set in evaluation standards.

From the above formula, it can be concluded that the probability of triggering Event 1B

can be decreased by either increasing R1b (Event 1B meets the reporting range

conditions) or decreasing H1b (Decision hysteresis range). Otherwise, the probability of

triggering Event 1B can be increased.

4.3.3 Event 1C-Triggered Handover

Event 1C indicates that the quality of a cell in the non-active set is better than that of a

cell in the active set. Upon receiving Event 1C, the RNC may replace the cell in the active

set with a cell in the non-active set to obtain better gain of macro diversity. When the cell

meets the conditions in the following formula, the UE reports Event 1C to the RNC:

/2HCIOLogM10CIOLogM10 1cInASInASNewNew

H1c Refers to the reporting hysteresis of Event 1C. It is used to control the extent of

difficulty in replacing a cell in the active set (Hysteresis[MAX_INTRA_MEAS_EVENT]









MNew: Refers to the measurement of the to-be-evaluated cell outside the active set.

MInAS: Refers to the cell with poorest quality in the active set.

CIONew: Refers to the offset of the to-be-evaluated cell outside the active set in relation to

other cells (CellIndivOffset (UUtranRelation)).

CIOInAS: Refers to the offset of cell with poorest quality in the active set in relation to other

cells (CellIndividualOffset (UUtranCellFDD)).

From the above formula, it can be concluded that the probability of triggering Event 1C

can be decreased by increasing H1c (decision hysteresis range). Otherwise, the

probability of triggering Event 1C can be increased.

Event 1C supports event-triggered periodical reporting, that is, once Event 1C meets the

reporting range of quality standards, the UE will report Event 1C periodically

(EvtRptInterval[MAX_INTRA_MEAS_EVENT](For event-triggered measurements,, if the





parameter is obtained from UIntraRscpEvMeasForD)) until this event does not meet

reporting conditions or the reporting times reach the maximum allowed times

(EvtRptAmount[MAX_INTRA_MEAS_EVENT] (For event-triggered measurements, if the








To ensure the gain of macro diversity, the reporting of Event 1C is only allowed when the

number of cells in the active set reaches a certain threshold (RplcActThr

[MAX_INTRA_MEAS_EVENT] (If the measurement quantity is EcNo, this parameter is

obtained from UIntraEcNoEvMeas. If the measurement quantity is RSCP, this parameter

is obtained from UIntraRscpEvMeas)).

4.3.4 Event 1D-Triggered Handover

Event 1D indicates that the quality of a cell inside or outside the current active set is

better than the best cell in the current active set, that is, the best cell changes in the

active set. The following operations can be triggered upon the reception of Event 1D:

A cell is added into the active set (The cell outside the active set reports Event 1D

and the number of links in the active set does not reach the maximum limit).

The cell with poor quality in the active set is replaced (The cell outside the active set

reports Event 1D but the number of links in the active set reaches the maximum

limit).

The serving cell changes (for HS-DSCH/E-DCH).

When the cell meets the conditions in the following formula, the UE reports Event 1D to

the RNC:

/2HCIOLogM10CIOLogM10 1dBestBestNotBestNotBest

MNotBest: Refers to the measurement of the to-be-evaluated cell inside or outside the

active set.

CIONotBest: Refers to the offset of the to-be-evaluated cell inside the active set

(CellIndividualOffset (UUtranCellFDD)) or outside the active set (CellIndivOffset

(UUtranRelation)) in relation to other cells.

CIOBest: Refers to the offset of the to-be-evaluated cell in the active set in relation to other

cells (CellIndividualOffset (UUtranCellFDD)).

MBest: Refers to the measurement of the to-be-evaluated cell in the active set.



H1d: Refers to Event 1D reporting hysteresis (Hysteresis [MAX_INTRA_MEAS_EVENT]







From the above formula, it can be concluded that the probability of triggering Event 1D

can be decreased by increasing H1d (decision hysteresis range). Otherwise, the

probability of triggering Event 1D can be increased.

4.3.5 CIO Configuration Strategy

The Cell Individual Offset (CIO) defined by 3GPP is used to control the difficulty of event

triggering. The tendency of handover can be also controlled by the CIO in actual

scenarios.

The CIO principles of the target cell are described as follows.

If there is a neighboring relationship between the target cell and the best cell, the

CIO is CellIndivOffset (For a UTRAN cell, this parameter is obtained from

UUtranRelation. For a GSM cell, this parameter is obtained from UExternalGsmCell)

selected from the best cell. If there is not any neighboring relationship between the

target cell and the best cell, the CIO is the minimum absolute value of

CellIndivOffset selected from the cells in the active set. If there is not any

neighboring relationship between the target cell and the cells in the active set, the

CIO is set to zero.

If the target cell is the best cell, the CIO is CellIndividualOffset (UUtranCellFDD)

selected from the serving cell.

If the best cell changes, the RNC will inform UEs to update the CIO.



4.3.6 Time-To-Trigger Mechanism Used to Control Event Report

If a to-be-evaluated cell meets the reporting range or threshold of a certain event, the

condition must be met within a period of time (TrigTime[MAX_INTRA_MEAS_EVENT]




measurement quantity is EcNo, this parameter is obtained from

UIntraEcNoEvMeasForD., if the measurement quantity is RSCP, this parameter is

obtained from UIntraRscpEvMeasForD)) before the reporting of this event to avoid the

intra-frequency event misreport due to the fluctuation of radio quality. For example, if a

cell meets the reporting range of Event 1A, the UE only reports Event 1A only if the cell

quality meets this reporting range condition within

TrigTime[MAX_INTRA_MEAS_EVENT], see Figure 4-3.

Figure 4-3 Time-To-Trigger mechanism

Reporting event 1A


Time

TrigTime[MAX_INTRA_MEAS_EVENT]

P CPICH 1 RptRange

[MAX_INTRA_MEAS_EVENT]

P CPICH 2

P CPICH 3

4.3.7 Criterion of Being in the Same Active Set Based on Cell Type

Before adding a cell into the active set, the current service and the ability of the target cell

should be judged. If the target cell supports the current service or channel (For R99 cells,

supporting the channel associated with HSDPA services also counts.), the cell is allowed

to join the active set.



1. If the current service is a DCH service, R99, R5+R99, and R6+R5+R99 cells can be

in the same active set.

2. If the current service is an HS/D service, R99, R5, R6+R5, R5+R99, and

R6+R5+R99 cells can be in the same active set.

3. If the current service is an HS/E service, R6+R5 and R6+R5+R99 cells can be in the

same active set.

4. If HS and DCH services both exist, the criterion is as that of HS services.

4.3.8 Processing of Intra-Frequency Events

Processing of Event 1A

Links are added into the active set if the number of links in the DCH active set is

less than 3. Event 1A will not be processed if the total number of links in the active

set reaches the maximum limit.

If a link to be added into the active set is rejected in Event 1A, the handover

punishment timer (5s) is initiated, so that Event 1A reported by this rejected cell will

not be processed until the timer expires.

If the cell reporting Event 1A is the target cell traced by the detected set, no link will

be added into the active set. For details, see Detected set Tracing.

If the measurement report contains several target cells, the cell with best quality

(EcNo) will be selected as the target cell to be added in the active set.

If the cell reporting Event 1A is the cell of the SRNC side, and the parallel softer

handover switch of Iub and Uu ParallelSoftHO is “open”, the RL ADD procedure of

the Iub interface and the ACTIVE SET UPDATA procedure of the Uu interface will

be processed in parallel.

Processing of Event 1B

The link of the related cell is deleted based on Event 1B reported by the UE.



If the measurement report contains several target cells, the cell with worst quality

(EcNo) will be selected as the target cell to be deleted from the active set.

Processing of Event 1C

The cell is replaced if the radio links in the active set are equal to 3.

If a link to be added into the active set is rejected in Event 1C, the handover

punishment timer is initiated, so that Event 1C reported by this rejected cell will not

be processed until the timer expires.

The parallel processing of the Iub and Uu interfaces when adding a radio link in

softer handover is the same as that of Event 1A.

Processing of Event 1D

If the cell triggering Event 1D is an intra-frequency adjacent cell outside the active

set, and if the criterion described in “4.3.14 Scenarios of Intra-Frequency Hard

Handover” is fulfilled, the RNC will perform an intra-frequency hard handover.

If the cell triggering Event 1D is an intra-frequency adjacent cell outside the active

set, and if the DCH active set is full, Event 1D will be processed as Event 1C. If the

DCH active set is not full, Event 1D will be processed as Event 1A. If event 1A or 1C

fails due to admission control failure, the RNC will perform an intra-frequency hard

handover.

If the cell triggering Event 1D is inside the active set, the best cell in the active set

changes.

4.3.8.1 Intra-frequency Handover Optimization in Weak Coverage

When the UE adds a new link into macro diversity or the serving cell changes, if the link

quality is not good enough, the UE is easy to drop because of processing the reported

intra-frequency events. In response, the RNC executes “Quality Judgement Strategy of

Target Cell”, as described below.

For 1A, 1C events:



(1). EnhanceHoSwch (URncFunction) is set to “1: On”.

(2). AddNRLSHOSwch (UCelInfoFDD) is set to” 1: on”.

(3). The UE reports Event 1A or Event 1C.

(4). The quality of the target cell: CPICH EcNo< IntraHoEcNoThrd (URncFunction) or

CPICH RSCP< IntraHoRscpThrd (URncFunction).

If these conditions are met, the RNC will not process Event 1A and Event 1C reported by

the UE.

For 1D event:


(2). CResPara5 (UCelInfoFDD) is set to” 1: on”.

(3). The UE reports Event 1D.

(4). The quality of the target cell: CPICH EcNo< IntraHoEcNoThrd (URncFunction) or

CPICH RSCP< IntraHoRscpThrd (URncFunction).

If these conditions are met, the RNC will not process Event 1D reported by the UE.

Moreover, during an intra-frequency handover, the timer TWAITACTSETUPCMP

(URncFunction) for waiting for the Active Set Update Complete message is initiated after

the Active Set Update message is sent from RNC to the UE. When the timer expires and

the Active Set Update Complete message is not received, if the conditions described

below are met, the RNC will still decide the active set update succeed. Otherwise, the

RNC will decide the update fails.


(2). The user plane confirms that the UE has received the Active Set Update message.

4.3.8.2 Special Events Handling via IUR for CS+PS

For CS+PS services via IUR, call drops may occur due to incompatibility of different



vendors‟ equipment. In response, the SRNC executes “Special Events Handling via IUR

for CS+PS” if the following conditions are met:

(1). RncFeatSwitchBit15 is set to “0”.

(2). Concurrent services exist and include CS+PS services, being indexed to the

configuration of Multi RAB Including CS and PS.

If these conditions are met, the SRNC will not process Event 1A/1C/1D of the DRNC's

cells.

4.3.8.3 Strategy for Soft Handover OD Switch Configuration in the Signaling Stage

In response to the incompatibility that may occur when equipment from different vendors

is interconnected via IUR, the RNC adds the following special strategy in the signaling

stage:

If the SRNC receives 1A/1B/1C/1D events from the DRNC‟s cells in the signaling stage,

the SRNC will not process these events when RncFeatSwitchBit16 is “0”, and the SRNC

will process these events when RncFeatSwitchBit16 is “1”.

4.3.8.4 Special Events Handling via IUR for CS


is interconnected via IUR, for CS services, the SRNC executes “Special Events Handling

via IUR for CS” if the following conditions are met:


(2). CsIntraEvtSwch (UCelInfoFDD) is set to “1”.

(3). Only CS services, being indexed to the configuration of RT RAB Including Voice.

If these conditions are met, the SRNC will not process Event 1A/1C/1D of the DRNC's

cells.



4.3.9 Detected set Handover

The detected set handover is controlled through the parameter DetSetHoSwch

(UUtranCellFDD). If the detected set handover is enabled, and the number of adjacent

cells exceeds 32, the RNC needs to instruct the UE to submit the measurement report of

the detected set in the measurement control. If the target cell in the detected set event

reported by the UE is a cell in the adjacent cell reserve list described in 4.1.3.2 Cell

Dropping Strategy for Over 32 Adjacent Cells, the RNC processes the cell in the

detected set in the same way as it does in the monitored set, that is, making a handover

decision.

4.3.9.1 Related Measurement Procedure of Detected set Handover

(1). If the detected set handover (DetSetHoSwch (UUtranCellFDD)) of the best cell is

enabled and there are over 32 adjacent cells, a detected set measurement will be

initiated. The initiation strategy is changing “1A Triggering condition 2” into

“Detected set cells and monitored set cells”, and “Reporting cell status” into “Report

all active set cells + cells within monitored set and/or detected set on used

frequency”, that is, performing measurement reporting of active set, monitored set

and detected set concurrently by sharing the same set of handover measurement

parameters.

(2). If the detected set handover (DetSetHoSwch (UUtranCellFDD)) of the best cell is

disabled or there are less than 32 adjacent cells, the initiation strategy is changing

“1A Triggering condition” into “Monitored set cells” and “Reporting cell status” into

“Report cells within active set and/or monitored set cells on used frequency”, That is,

only reporting the monitored set instead of the detected set.

4.3.9.2 Related Parameter Configurations

The RNC only performs handovers for the detected set measurement reported by the

adjacent cells exceeding 32. The processing of the measurement report triggered by

these cells is actually consistent with that triggered by the monitored set. Therefore, the

detected set and monitored set share the same set of measurement configurations.



4.3.10 Detected Set Tracing

The detected set tracing is used in network planning and optimization to judge whether

there is any adjacent cell that is not configured based on the statistical report. The

purpose of detected set tracing measurement differs from that of handover measurement,

so the measurement parameters used for detected set tracing are separately configured

in the OMCR (The parameters of detected set tracing is irrelevant to service type, which

means all sorts of services will be indexed by “Not Related to Service Type “in service

type (srvCategory (UIntraMeasSrvSpec)), see 4.1.2.4 Parameter Configuration

Strategies.).

4.3.10.1 Measurement Procedure of Detected Set Tracing

1. The measurement of detected set tracing is controlled through the detected set

tracing task in the performance measurement of the OMCR. A detected set

measurement is started after a detected set tracing task is created and initiated if

the parameter NbrCellMonSupInd (ULogicalRnc) is 1. During the configuration of

the measurement control, “Triggering condition 2” is set to “Detected set cells”, and

“Reporting cell status” is set to “Report cells within detected set on used frequency”.

2. The measurement parameters of the detected set are indexed to the cell, and the

parameters of the best cell will be selected in macro diversity state. If the

parameters of the best cell are different from those used by the UE, the

measurement information needs to be modified through the measurement control

message.

3. After the detected set tracing task stops, the detected set tracing is disabled and the

related measurement task is released.

4.3.11 Processing of the Rx-Tx Time Difference of a UE in Macro Diversity

When a UE is in macro diversity, the uplink transmitting time of the UE is not adjusted.

The initial downlink channels can be correctly demodulated, but the downlink receiving

time changes along with the movement of the UE or with the drifting of the clock between

Node Bs. Therefore, the downlink receiving time may fall out of the time window of the

UE transmitting time T0 ± 148 chips, and consequently the UE cannot correctly



demodulate one or multiple downlink channels, causing the degradation of UE downlink

quality or even call drop. For this reason, the 3GPP protocols have defined the UE

internal measurement events 6F and 6G for UE Rx-Tx time difference measurement:

6F event: The UE Rx-Tx time difference for a link in the active set is greater than an

absolute threshold.

6G event: The UE Rx-Tx time difference for a link in the active set is less than an

absolute threshold.

The rlRefTimeAjtSw (ULogicalRnc) parameter controls the policy of the UE Rx-Tx

time difference in macro diversity. If the switch is on, the RNC removes the

corresponding link from macro diversity when the UE reports a 6F or 6G event

(indicating that the downlink receiving time falls out of the UE transmitting time

window). If the switch is off, the function is disabled.

4.3.11.1 Related Measurement Procedure

1. When the radio link reference time adjustment switch of the best cell

(rlRefTimeAjtSw (ULogicalRnc)) is on and the number of links in macro diversity

changes from one to multiple, the 6F/6G measurement parameters will be issued to

the UE. Furthermore, the parameter TxRxTDThres

[MAX_UE_INTER_MEAS_EVENT](URlEvtRttUeInt) indicates the UE Rx-Tx time

difference reporting threshold in chips in event 6F/6G.

MAX_UE_INTER_MEAS_EVENT is configured by MeasEvtNum (URlEvtRttUeInt).

The parameter TrigTime [MAX_UE_INTER_MEAS_EVENT] (URlEvtRttUeInt)

indicates the period of time during which the event conditions have to be satisfied

before a measurement report is sent.

2. The internal measurement parameters (6F/6G) of the UE are configured per cell

according to the index, and are subject to the parameters of the best cell. When the

UE internal measurement parameters are obtained, profileId (UUeIntMeasProfile) of

the cell is found based on refUUeIntMeasProfile (UUtranCellFDD), and then

according to the current measurement purpose “UE Rx-Tx Time Difference Event

Measurement for RL Timing Adjustment”, the managed object URlEvtRttUeInt is

obtained from UUeIntMeasProfile configuration items. Finally, the internal



measurement parameters are obtained from URlEvtRttUeInt. For a UE on which the

internal measurement (6F/6F) function is enabled in macro diversity, if the 6F/6G

event parameters of the best cell are different from the parameters issued to the UE,

the parameter configuration of the UE will be modified through measurement

control.

The correspondence between other parameters that need to be filled in the UE internal

measurement control message and OMCR configuration is described as follows:

UE internal measurement configuration index ueIntMCfgNo(URlEvtRttUeInt)

Measurement report transmission mode MeasRptTrMod(URlEvtRttUeInt)

Filter coefficient FilterCoeff(URlEvtRttUeInt)

UE internal event identity MeaEvtId(URlEvtRttUeInt)

3. When the number of links in macro diversity changes from multiple to one and the

internal measurement function (6F/6G) is enabled on the UE, a release of internal

measurement will be triggered on the UE.

4.3.12 IUB Transmission Bandwidth Limitation Strategy

When a network is constructed, there may be a shortage of Iub transmission resources.

An access of a high-rate UE may lead to inaccessibility of numbers of other users to the

network. To prevent some individual high-rate UEs from affecting the communication

quality in large scale, it is necessary to limit the maximum rate of these UEs in the cell.

For intra-RNC DCH users, the parameters RtMaxUlRateDch / RtMaxDlRateDch (for RT

services) and NrtMaxUlRateDch / NrtMaxDlRateDch (for NRT services) are used to limit

the maximum rates of uplink and downlink DCHs respectively. For intra-RNC E-DCH

users, the maximum rates are limited by the parameters RtMaxrateEdch (for RT services)

and NrtMaxRateEdch (for NRT services).

For inter-RNC DCH users, the parameters RtMaxUlRateDchD / RtMaxDlRateDchD (for

RT services) and NrtMaxUlRateDchD / NrtMaxDlRateDchD (for NRT services) are used

to limit the maximum rates of uplink and downlink DCHs respectively. For E-DCH users,

the maximum rates are limited by parameters RtMaxRateEdchD (for RT services) and

NrtMaxRateEdchD (for NRT services). If the related parameters are not configured in the

neighboring cells, the restriction decision does not take effect.



Processing of adding a radio link in active set

For DCH users, if the GBR of DCH users is higher than the rate limitation

RtMaxUlRateDch / RtMaxDlRateDch of the new neighboring cell, it does not add a radio

link. Otherwise, it adds a radio link.

For EDCH users, if the rate of E-DCH users is higher than the E-DCH rate limitation

RtMaxRateEdch / NrtMaxRateEdch of the new neighboring cell, it reduces E-DCH

Maximum Bitrate by radio link reconfiguration, and then adds the corresponding

neighboring cell into macro diversity.

Processing of deleting a radio link in active set

For DCH users, a radio link is deleted from macro diversity. If the UE rate is less than the

DCH rate limitation of the cells in macro diversity, the RNC will perform RB

reconfiguration.

For E-DCH users, a radio link is deleted from macro diversity. If the UE rate is less than

E-DCH rate limitation of the cells in macro diversity, the RNC will perform RL

reconfiguration to enhance E-DCH Maximum Bitrate.

4.3.13 Decision on Support-CS64k Traffic of Target Cell

For some special scenarios where accessing or handing over CS64K traffic is not

expected in a cell, the parameters Cs64kSwitch and AdjCs64Switch are used to control

whether a cell supports CS64k traffic in the SRNC and DRNC respectively. When CS64k

traffic is restricted in a cell, ingoing, outgoing and handover of CS64k traffic are

forbidden.

When a handover happens in intra-RNC cells and CS64k traffic is covered, if

Cs64kSwitch in the target cell is closed and the UE allows CS64k to fall back to

AMR12.2k, then CS64k falls back to AMR12.2k and the UE performs the related

handover. Otherwise, the UE does not perform any handover.

When a handover happens in inter-RNC cells and CS64k traffic is covered, if

AdjCs64kSwitch in the target cell is closed and the UE allows CS64k to fall back to

AMR12.2k, then CS64k falls back to AMR12.2k and the UE performs the related



handover. Otherwise, the UE does not perform any handover. If a DRNC cell

reported has no configuration relationship with SRNC cells, the cell supports CS64k

by default.

4.3.14 Scenarios of Intra-Frequency Hard Handover

When soft handover cannot be performed in intra-frequency adjacent cells for some

reasons, intra-frequency hard handover can guarantee service continuity. The scenarios

where a soft/softer handover is unavailable (An intra-frequency hard handover must be

used) include:

Adding a new link fails in a soft handover when a 1A or 1C event is triggered.

The intra-frequency measurement report excludes the OFF and TM of the target

cell.

The lur interface between RNCs is unavailable in the case of intra-frequency

handover.

The types of the target and source cells are different, for example, the UE is handed

over from a DCH-capable cell to an HSPA-capable cell.

The signal RB is carried on HS-DSCH in the active cell, while F-DPCH is not

supported in the adding target cell

The capability of the target cell is not consistent with that of the source cell,

including:

The UE uses transmit diversity in an active set cell, but the target cell does not

support transmit diversity.

The UE uses multi-user detection in an active set cell, but the target cell does not

support multi-user detection

The UE uses DTX-DRX in an active set cell, but the target cell does not support the

capability

Uplink 16QAM is configured but the target cell does not support it

A TTI 2ms service is set up in the source cell, but the target cell does not support

The transmission delay TimeDelay(UIubLink) reported during an intra-frequency

handover for the Node B where the neighboring cell of the current RNC resides is



inconsistent with the transmission delay of the cells in the current active set, or the

transmission delay ATimeDelay(UExternalUtranCellFDD) reported during

intra-frequency handover for the neighboring cell that is a DRNC cell is inconsistent

with the transmission delay of the cells in the current active set.

There are two synchronization modes for intra-frequency hard handover: Timing

re-initialised and Timing-maintained, which are controlled by the parameter

gRESPARA47.bit14 (URncFunction).

4.3.15 Disposal Strategy of Intra-Frequency Events in Buffer

If the RNC receives measurement events and discards them in unsteady state, it may

miss handover opportunities, and radio links with good signal quality may be not added

into the active set while radio links with poor signal quality may be still in the active set.

So it needs to cache measurement reports in buffer in unsteady state and then dispose

of such measurement reports while the RNC enters steady state. In unsteady state, the

RNC needs to combine the received measurement reports. The strategy is described as

follows:

Events Existing in Buffer

1A 1B 1C 1D

New

measurement

report

1A

If the

scrambling

code in the

new 1A event

is identical

with that in

the old 1A

event, then

the old 1A

event is

replaced by

the new one.

Otherwise,

the new 1A

event is

cached.

The 1A event

is cached. ×

The 1A event

is cached.

1B The 1B event The old 1B

event is 1B event is

If the

scrambling




1A 1B 1C 1D

is cached. replaced by

the new one.

cached code in the

1B event is

identical with

the existing

one, then the

1D event is

replaced by

the 1B event.

Otherwise,

the 1B event

is cached.

1C × The 1C event

is cached.

The old 1C

event is

replaced by

the new one.

If the

replaced

scrambling

code in the

1C event is

identical with

the existing

one in the 1D

event, then

the 1D event

is replaced

by the 1C

event.

Otherwise,

the 1C event

is cached.

1D The 1D event

is cached.

If scrambling

code in the

1D event is

identical with

the one in

the 1B event,

then the 1B

event is

replaced by

the 1D event.

Otherwise,

If the

scrambling

code in the

1D event is

identical with

the replaced

scrambling

code in the

1C event,

then the 1C

event is

The old 1D

event is

replaced by

the new one.




1A 1B 1C 1D

the 1D event

is cached.

replaced by

the 1D event.

Otherwise,

the 1D event

is cached.

4.4 Intra-Frequency Handover Procedure

4.4.1 Inter-RNC Soft Handover (Adding a Radio Link)

Figure 4-4 Intra-RNC Soft Handover (Adding a Radio Link)

UE Node B

Drift RNS

Drift

RNC

Serving

RNC

DCH - FP DCH - FP

8. Downlink Synchronisation

RNSAP RNSAP

1. Radio Li nk Setup

Request

Start TX description

NBAP NBAP

2. Radio Link Setup

Request

RNSAP RN SAP

4. Radio Link Setup

Response

NBAP NBAP

3. Radio Link Setup Response

Start RX description

Decision to setup new RL

RRC RRC

11. DCCH : Active Set Update Complete

RRC RRC

10. DCCH : Active Set Update

[Radio Link Addition]

ALCAP Iur Bearer Setup 5. ALCAP Iub Bearer Setup

DCH - FP DCH - FP

9. Uplink Synchronisation

RNSAP RNSAP

7. Radio Link Restore Indication

NBAP NBAP




4.4.2 Inter-RNC Soft Handover (Deleting a Radio Link)

Figure 4-5 Intra-RNC Soft Handover (Deleting a Radio Link)

UE Node B

Drift RNS

Drift

RNC

Serving

RNC

RRCRRC2. DCCH : Active Set Update Complete

Decision to delete

old RL

RNSAP RNSAP

3. Radio Link Deletion

Request

NBAP NBAP


Request

RNSAP RNSAP


Response

NBAP NBAP


Response

Stop RX and TX

RRCRRC

1. DCCH : Active Set Update

[Radio Link Deletion]

ALCAP Iur Bearer Release7. ALCAP Iub Bearer Release



4.4.3 Inter-RNC Soft Handover (Swapping a Radio Link)

Figure 4-6 Intra-RNC Soft Handover (Swapping a Radio Link)

9 . U plink Synchronisation

R N SA P R N SA P

1 . R adio L ink Setup

R equest

S tart T X

descrip tion

R N SA P R N SA P

4 . R adio L ink Setup

R esponse

N B A P N B A P

2 . R adio L ink Setup R equest

N B A P N B A P 3 . R adio L ink Setup R esponse

S tart R X

descrip tion

D ecision to setup

new R L and

release o ld R L

N B A P

12 . R adio L ink D eletion R equest

N B A P N B A P 13 . R adio L ink R elease R esponse

S top R X and T X

14 . A LC A P Iub D ata T ransport B earer R elease

R R C R R C

11 . D C C H : A ctive Set U pdate C om plete

R R C R R C

10 . D C C H : A ctive Set U pdate C om m and

[R adio L ink A ddition & D eletion]

N B A P

U E N ode B

D rift R N S

N ode B

Serving R N S

D rift

R N C

Serving

R N C

A LC A P Iur B earer Setup 5 . A LC A P Iub D ata T ransport B earer Setup

D C H -FP D C H -FP

D C H -FP D C H -FP

8 . D ownlink Synchronisation

R N SA P R N SA P

7 . R adio L ink R estore

Ind ication

N B A P N B A P 6 . R adio L ink R estore Ind ication



4.4.4 Intra-RNC Hard handover

Figure 4-7 Intra-RNC Hard Handover

RADIO LINK SETUP REQUEST

RADIO LINK SETUP RESPONSE

PHYSICAL CHANNEL RECONFIGURATION

PHYSICAL CHANNEL RECONFIGURATION COMPLETE

RADIO LINK DELETION REQUEST

RADIO LINK DELETION RESPONSE

UE NODEB2 NODEB1 RNC



4.4.5 Inter-RNC Hard Handover Through lur Interface

Figure 4-8 Inter-RNC Hard Handover Through lur Interface

RNSAP RNSAP

1. Radio Link Setup Request

UE Node B

Source

Node B Target

RNC Source

RNC target

SRNC

RRC

RRC

12. DCCH : Physical Channel Reconfiguration Complete

RRC

7. DCCH : Physical Channel Reconfiguration

RRC

6. ALCAP Iur Data Transport Bearer Setup

NBAP NBAP

2. Radio Link Setup Request

NBAP NBAP

3. Radio Link Setup Response

NBAP

NBAP

14. Radio Link Deletion Request

NBAP

NBAP

15. Radio Link Deletion Response

4. ALCAP Iub Data Transport Bearer Setup

16. ALCAP Iub Data Transport Bearer Release

RNSAP

RNSAP

17. Radio Link Deletion Response

18. ALCAP Iur Data Transport Bearer Release

RNSAP

5. RL Setup Response

RNSAP

RNSAP 13. Radio Link Deletion Request

RNS AP

NBAP

NBAP

8. Radio Link Failure Indication

RNSAP RNSAP

9. Radio Link Failure Indication

NBAP

NBAP


RNSAP

11. RL Restore Indication

RNSAP

If the cells belonging to different RNCs are adjacent and the lur interface is available, the

SRNC performs an inter-RNC hard handover. An SRNC relocation is triggered after the

hard handover.



4.4.6 Inter-RNC Hard Handover Without lur Interface

Figure 4-9 Inter-RNC Hard Handover Without lur Interface

2 . R elocation R equired R A N A P R A N A P

R A N A P R A N A P

3 . R elocation R equest

R A N A P R A N A P


A cknow ledge

R A N A P R A N A P 1 . R elocation R equired

U E R N C

Source

R N C

Target

M SC /SG SN

R A N A P R A N A P


R A N A P R A N A P


A cknow ledge

R A N A P R A N A P 11 . R elocation C om m and

R A N A P 12 . R elocation C om m and

R A N A P

R A N A P R A N A P

15 . R elocation

D etect

R R C 13 . D C C H : P hysical C hannel R econfiguration N ote 1

R R C

5 . A LC A P Iu D ata

T ransport B earer Setup

N ode B

Source

N ode B

Target

N B A P N B A P 6 . R adio L ink Setup R equest

N B A P N B A P 7 . R adio L ink Setup R esponse

8 . A LC A P Iub D ata T ransport B earer Setup

R A N A P R A N A P

19 . R elocation

C om plete

R R C R R C 18 . D C C H : P hysical C hannel R econfiguration C om plete N ote 1

R A N A P R A N A P 16 . R elocation D etect

R A N A P R A N A P 20 . R elocation C om plete

R A N A P 21 . Iu R elease C om m and

R A N A P

N B A P N B A P 17 . R adio L ink Failure Ind ication

R A N A P 22 . Iu R elease C om m and

R A N A P

23 . A LC A P Iu D ata T ransport B earer

R elease

R A N A P 24 . Iu R elease C om plete

R A N A P

R A N A P 25 . Iu R elease C om plete

R A N A P

SG SN /M SC

N B A P N B A P 14 . R adio L ink R estore Ind ication

If inter-frequency cells between RNCs are adjacent and the lur interface is unavailable,

the hard-handover-triggered SRNS relocation is performed. The procedure is described

as follows:

The SRNC sets up a radio link at the DRNC through an lu interface relocation, and then

reconfigure the UE to a cell of the DRNC through a relocation. Upon receiving the

reconfiguration response message from the UE, the DRNC informs the CN to complete



the relocation and changes into SRNC. The CN then releases the resources of the UE at

the original SRNC through the lu interface release command.

5 Inter-Frequency Handover Strategy

The inter-frequency handover is a feature in which the UE is handed over from one

frequency of UTRAN to another one. It can either be a handover based on the

inter-frequency measurement, or a blind handover based on ShareCover (Overlap or

Covers). The measurement-based handover cannot trigger a blind handover based on

shared coverage. The blind handover between cells with shared coverage can only be

triggered by such functions as load control and load balancing.

The prerequisite for measurement-based inter-frequency handovers is that the UE

performs a quality measurement of non-working frequencies. For an inter-frequency

measurement in CELL_DCH state, the UE needs to initiate compressed mode unless it

has double-receiver. Compressed mode has a great impact on both the resource

utilization (for example, downlink power and uplink interference) and UE (for example,

transmit power and battery consumption), so an inter-frequency measurement is only

initiated when the radio quality of the current serving carrier is poor, which can be

evaluated through four measurement quantities: Uplink BLER, UE uplink transmit power,

transmit power of downlink and inter-frequency measurement (quality measurement

performed by the UE for PCPICH). Upon receiving the inter-frequency measurement

results from the UE, the RNC makes a decision about inter-frequency handover, and

hands over the UE to the target frequency and cell carried in the measurement results.

The blind handover based on ShareCover (Overlap or Covers) is controlled through the

coverage indication (ShareCover UUtranRelation)) in the adjacent cell configuration

relation. If the radio quality of a cell is good, then that of another cell that has

ShareCover(Overlap or Covers) relation with it must also be good, which means

forecasting the radio quality of another cell that has ShareCover (Overlap or Covers)

relation with a cell based on the radio quality of this cell. Whether the ShareCover

(Overlap or Covers) relation exists among cells is determined by the network planner

based on cell coverage (Only those cells with completely the same coverage can be

called cells with shared coverage, and inter-frequency cells with shared coverage

generally share a site and antenna feeder. If a cell completely contains the coverage of



another cell, the relation between them is called ‟Covers‟). The blind handover based on

ShareCover (Overlap or Covers) is primarily used in load control, load balancing and

handover based on moving speed.

In the load balancing mechanism, if the load of the target cell for access or

handover is too heavy, you can access or hand over the service into another less

loaded cell that has ShareCover (Overlap or Covers) relation with the target cell.

In the load control mechanism, if the load of the current cell is too heavy, you can

forcedly hand over partial services into another less loaded cell that has

ShareCover (Overlap or Covers) relation with the target cell.

In a handover based on the moving speed, when the UE changes from a low to a

high moving speed, the UE can be directly handed over from a micro cell into a

macro cell that contains this micro cell.

5.1 Inter-Frequency Measurement

When conducting an inter-frequency measurement, the UE needs to implement layer 3

filter for the measurement results to avoid measurement fluctuations, and then make

event decisions and reports by using filtered values. The layer 3 filter factor is FilterCoeff

(If the measurement is an event-triggered measurement and the measurement quantity

is EcNo, for Event 2D/2F used for the EUTRAN system, this parameter is obtained from

UInterEcNoEvMeasforE. For Event 2D/2F used for the GSM system, this parameter is

obtained from UInterEcNoEvMeasforG. For inter-frequency measurement events used

for the UTRAN system, this parameter is obtained from UInterEcNoEvMeasforU. If the

measurement is an event-triggered measurement and the measurement quantity is

RSCP, for Event 2D/2F used for the EUTRAN system, this parameter is obtained from

UInterRscpEvMeasforE. For Event 2D/2F used for the GSM system, this parameter is

obtained from UInterRscpEvMeasforG. For inter-frequency measurement events used

for the UTRAN system, this parameter is obtained from UInterRscpEvMeasforU. If the

measurement is a periodical measurement and the measurement quantity is EcNo, this

parameter is obtained from UInterEcNoPrdMeas. If the measurement quantity is RSCP,

this parameter is obtained from UInterRscpPrdMeas). For the inter-frequency

measurement formula, see “Intra-frequency Measurement”.



Carrier evaluation standards for inter-frequency measurements:

jBestj

N

1i

jijjfrequencyfrequencyj LogM10)W(1MLog10WLogM10QjA

Where,

Qfrequency j: Refers to the (virtual) active set quality of carrier j, that is, the measurement

result of carrier j (dB for Ec/No; dBm for RSCP).

Mfrequency j: Refers to the physical measurement value (ratio for Ec/No; mW for RSCP) of

the (virtual) active set of carrier j.

Mi j: Refers to the physical measurement value of cell i of carrier j.

NA j: Refers to the number of cells (excluding the best cell) in the (virtual) active set of

carrier j.

MBest j: Refers to the measurement result of the best cell in the (virtual) active set of

carrier j.

Wj: Refers to the weight (WNoUsed (If the measurement quantity is EcNo, this parameter

is obtained from UInterEcNoEvMeasforU. If the measurement quantity is RSCP, this

parameter is obtained from UInterRscpEvMeasforU) or Wused (If the measurement

quantity is EcNo, for Event 2D/2F used for the EUTRAN system, this parameter is

obtained from UInterEcNoEvMeasforE. For event 2D/2F used for the GSM system, this

parameter is obtained from UInterEcNoEvMeasforG. For inter-frequency measurement

events used for the UTRAN system, this parameter is obtained from

UInterEcNoEvMeasforU. If the measurement quantity is RSCP, for Event 2D/2F used for

the EUTRAN system, this parameter is obtained from UInterRscpEvMeasforE. For event

2D/2F used for the GSM system, this parameter is obtained from

UInterRscpEvMeasforG. For inter-frequency measurement events used for the UTRAN

system, this parameter is obtained from UInterRscpEvMeasforU))of the best cell in the

(virtual) active set of carrier j during a carrier measurement.



5.1.1 Introduction to Inter-Frequency Measurement

The inter-frequency measurement contains radio quality measurement of both working

carrier frequency and non-working carrier frequency. It can be performed based on either

EcNo or RSCP or both measurement quantities, depending on the parameter

NonIntraMeasQuan (UUtranCellFDD). Only event-triggered reporting is supported. The

event-triggered reporting means the UE judges whether inter-frequency events are met

based on the quality measurement result of the non-working carrier frequency PCPICH.

If so, it reports inter-frequency events (including such information as event ID and the

target cell) to the RNC.

A series of inter-frequency measurement events are defined in 3GPP as the judgment

and trigger criteria for inter-frequency handovers.

The inter-frequency handover events are described as follows:

Event 2A: The best carrier frequency changes.

/2HQQ 2aBestNotBest

Where,

QNotBest: Refers to the measurement result of the current non-best carrier frequency.

QBest: Refers to the measurement result of the current best carrier frequency.

H2a: Refers to the handover decision hysteresis parameter (Hysteresis (If the

measurement quantity is EcNo, this parameter is obtained from UInterEcNoEvMeasforU.

If the measurement quantity is RSCP, this parameter is obtained from

UInterRscpEvMeasforU)) of Event 2A.

Event 2B: The quality of working carrier frequency is lower than a threshold and that of

non-working carrier frequency is higher than a threshold.

/2HTQ 2b2busedNonusedNon

/2HTQ 2b2bUsedUsed

Where,



QNon used: Refers to the measurement result of the current non-working carrier frequency.

TNon used 2b: Refers to the absolute threshold (ThreshNoUsedFreq (If the measurement

quantity is EcNo, this parameter is obtained from UInterEcNoEvMeasforU. If the

measurement quantity is RSCP, this parameter is obtained from

UInterRscpEvMeasforU)) of good-quality non-working carrier frequency in an Event 2B

decision.

H2b: Refers to the handover decision hysteresis parameter (Hysteresis (If the



UInterRscpEvMeasforU)) of Event 2B.

QUsed: Refers to the measurement result of the current working carrier frequency.

TUsed 2b: Refers to the absolute threshold (ThreshUsedFreq (If the measurement quantity

is EcNo, this parameter is obtained from UInterEcNoEvMeasforU. If the measurement

quantity is RSCP, this parameter is obtained from UInterRscpEvMeasforU)) of

poor-quality working carrier frequency in an Event 2B decision.

Event 2C: The quality of non-working carrier frequency is higher than a threshold.

/2HTQ 2c2cusedNonusedNon

Where,


TNon used 2c: Refers to the absolute threshold (ThreshNoUsedFreq (If the measurement



UInterRscpEvMeasforU)) of good-quality non-working carrier frequency in an Event 2C

decision.

H2c: Refers to the handover decision hysteresis parameter (Hysteresis (If the



UInterRscpEvMeasforU)) of Event 2C.



Event 2D: The quality of the working carrier frequency is lower than a threshold.

/2HTQ 2d2dUsedUsed

Where,


TUsed 2d: Refers to the absolute threshold (ThreshUsedFreq (If the measurement quantity

is EcNo, for Event 2D used for the EUTRAN system, this parameter is obtained from

UInterEcNoEvMeasforE. For Event 2D used for the GSM system, this parameter is

obtained from UInterEcNoEvMeasforG. For Event 2D used for the UTRAN system, this

parameter is obtained from UInterEcNoEvMeasforU. If the measurement quantity is

RSCP, for Event 2D used for the EUTRAN system, this parameter is obtained from

UInterRscpEvMeasforE. For Event 2D used for the GSM system, this parameter is

obtained from UInterRscpEvMeasforG. For Event 2D used for the UTRAN system, this

parameter is obtained from UInterRscpEvMeasforU)) of poor-quality working carrier

frequency in an Event 2D decision.

H2d: Refers to the handover decision hysteresis parameter (Hysteresis (If the

measurement quantity is EcNo, for Event 2D used for the EUTRAN system, this

parameter is obtained from UInterEcNoEvMeasforE. For Event 2D used for the GSM

system, this parameter is obtained from UInterEcNoEvMeasforG. For Event 2D used for

the UTRAN system, this parameter is obtained from UInterEcNoEvMeasforU. If the

measurement quantity is RSCP, for Event 2D used for the EUTRAN system, this

parameter is obtained from UInterRscpEvMeasforE. For Event 2D used for the GSM

system, this parameter is obtained from UInterRscpEvMeasforG. For Event 2D used for

the UTRAN system, this parameter is obtained from UInterRscpEvMeasforU)) of Event

2D.

Event 2E: The quality of non-working carrier frequency is lower than a threshold.

/2HTQ 2e2eusedNonusedNon

Where,




TNon used 2e: Refers to the absolute threshold (ThreshNoUsedFreq (If the measurement



UInterRscpEvMeasforU)) of good-quality non-working carrier frequency in an Event 2E

decision.

H2e: Refers to the handover decision hysteresis parameter (Hysteresis (If the



UInterRscpEvMeasforU)) of Event 2E.

Event 2F: The quality of working carrier frequency is higher than a threshold.

/2HTQ 2f2fUsedUsed

Where,


TUsed 2f: Refers to the absolute threshold (ThreshUsedFreq (If the measurement quantity

is EcNo, for Event 2F used for the EUTRAN system, this parameter is obtained from

UInterEcNoEvMeasforE. For Event 2F used for the GSM system, this parameter is

obtained from UInterEcNoEvMeasforG. For Event 2F used for the UTRAN system, this

parameter is obtained from UInterEcNoEvMeasforU. If the measurement quantity is

RSCP, for Event 2F used for the EUTRAN system, this parameter is obtained from

UInterRscpEvMeasforE. For Event 2F used for the GSM system, this parameter is

obtained from UInterRscpEvMeasforG. For Event 2F used for the UTRAN system, this

parameter is obtained from UInterRscpEvMeasforU)) of poor-quality working carrier

frequency in an Event 2F decision.

H2f: Refers to the handover decision hysteresis parameter (Hysteresis (If the

measurement quantity is EcNo, for Event 2F used for the EUTRAN system, this

parameter is obtained from UInterEcNoEvMeasforE. For Event 2F used for the GSM

system, this parameter is obtained from UInterEcNoEvMeasforG. For Event 2F used for

the UTRAN system, this parameter is obtained from UInterEcNoEvMeasforU. If the

measurement quantity is RSCP, for Event 2F used for the EUTRAN system, this

parameter is obtained from UInterRscpEvMeasforE. For Event 2F used for the GSM



system, this parameter is obtained from UInterRscpEvMeasforG. For Event 2F used for

the UTRAN system, this parameter is obtained from UInterRscpEvMeasforU)) of Event

2F.

If a carrier frequency meets the reporting range or threshold of a certain event, the

condition must be met within a period of time (TrigTime (If the measurement quantity is

EcNo, for Event 2D/2F used for the EUTRAN system, this parameter is obtained from

UInterEcNoEvMeasforE. For Event 2D/2F used for the GSM system, this parameter is

obtained from UInterEcNoEvMeasforG. For inter-frequency measurement events used

for the UTRAN system, this parameter is obtained from UInterEcNoEvMeasforU. If the

measurement quantity is RSCP, for Event 2D/2F used for the EUTRAN system, this

parameter is obtained from UInterRscpEvMeasforE. For Event 2D/2F used for the GSM

system, this parameter is obtained from UInterRscpEvMeasforG. For inter-frequency

measurement events used for the UTRAN system, this parameter is obtained from

UInterRscpEvMeasforU)) before the reporting of this event to avoid an inter-frequency

event misreport due to the fluctuation of radio quality.

5.1.2 Inter-Frequency Measurement Control Method

Among all inter-frequency measurement events, Event 2D and Event 2F only involve

measurements of working carrier frequencies, so compressed mode is not required

during a measurement and an extra overhead will not be brought to both the UE and the

RNC. Compressed mode can be enabled and disabled based on the definition of 2D/2F.

If there is any inter-frequency/Inter-RAT adjacent cell during a service setup, the RNC

will configure Event 2D, Event 2F and intra-frequency events to the UE. The following

measurement setup, modification and deletion apply to inter-frequency measurement

events other than Event 2D and Event 2F.


An inter-frequency measurement is only set up only when the inter-RAT measurement is

not initiated, and it can be triggered in either of the following scenarios:

1. The radio quality of the current serving carrier frequency deteriorates and there are

inter-frequency adjacent cells that have no ShareCover (Covers) relation (judged



through ShareCover(UUtranRelation)) with the current serving cell and the UE

supports the radio frequency band of these neighboring cells.

2. The UE meets the slow moving conditions and there is a micro cell with higher HCS

level in the coverage of the current cell (based on moving speed).

The “Radio Quality Deterioration of Current Serving Carrier Frequency” can be judged

through any of the following four indexes:

Uplink BLER: The uplink BLER value exceeds a certain threshold (1.25%) and the

Sirtarget value (real-time measurement result) reaches the maximum value of SIR

(ULMaxSIR) configured in the OMCR. The BLER is measured and judged by the

RNC.

Uplink transmit power of UE: The transmit power of the UE exceeds a certain

threshold (100%, in relation to the maximum transmit power of the UE). The uplink

transmit power is measured by the UE and reported to the RNC through the internal

measurement report 6A/6B. The threshold parameter of Event 6A and Event 6B

(txPowerThres(UHoEvtTPUeInt)) is a delta value relative to min(UE maximum

transmitted power, uplink DPCH maximum transmission power).

Downlink transmit power: The downlink transmit power exceeds a certain threshold

(90%, in relation to MaxDlDpchPwr of services). The downlink transmit power is

measured by the Node B and reported to the RNC through the dedicated Node B

measurement report.

The UE reports Event 2D.


If the inter-frequency measurement is enabled, an inter-frequency measurement

modification is triggered in the following cases:

If the inter-frequency measurement parameters and adjacent cells change after a

soft handover, the changed parameters and adjacent cells must be updated through

a measurement modification.



If the handover parameters change when a service is added or deleted, the

changed parameters must be updated through a measurement modification.


When the following inter-frequency measurement setup conditions are no longer met, the

corresponding inter-frequency measurement will be deleted (released).

There is no inter-frequency adjacent cell in the active set after a handover and

inter-frequency measurement is initiated.

There is an inter-frequency adjacent cell but it has ShareCover (Covers) relation

with a cell or an intra-frequency adjacent cell in the current active set, and an

inter-frequency measurement is initiated.

An inter-frequency measurement is initiated but the radio quality of working carrier

frequency becomes better. The standards for judging “The Radio Quality of Working

Carrier Frequency Changes Better” are described as follows:

The UE does not report Event 2D or reports Event 2F.

The uplink BLER does not exceed the poor quality threshold (1.25%) or the BLER

recovers below the normal quality threshold (CS64K: 0.1%; other services: 1%).

The UE‟s transmit power does not exceed inter-frequency measurement initiation

threshold (100%) or recovers below normal value (90%).

The downlink transmit power does not exceed inter-frequency measurement

initiation threshold (90%) or recovers below the normal value (80%).

An inter-frequency handover is completed.

An exception occurs, for example, receiving an exceptional inter-frequency

measurement report (for example, the measurement report belongs to a

non-existent measurement task on the network side).

When the RNC sends a MEASUREMENT CONGROL RELEASE message for a

measurement ID, the time stamp is recorded. If the RNC receives the measurement



report for the ID, it compares the current time and the recorded time. If the difference

between the current time and the recorded time exceed the threshold TResndMeaCtrlRel

(URncFunction) configured, the MEASUREMENT CONTROL RELEASE will be resent.

Otherwise, this measurement report will be ignored.

5.1.2.4 Processing of Inter-Frequency Events

1. Processing of Event 2A/2B/2C

If a measurement report contains several target cells, those with good quality

(RSCP) are preferentially selected as target cells. If there is any inter-frequency

adjacent cell that has ShareCover (Overlap or Covers) relation with the target cell,

inter-frequency load balancing is performed based on the cell‟s load. (For details,

see ZTE UMTS Load Balance Feature Guide).

For CS users, an inter-frequency hard handover is performed.

For PS users, a hard handover tends to fail due to admission failure in the event of

heavy cell load because a majority of resources are occupied by PS services. The

following strategies are required:

If the current channel type is DCH and the channel assigned for the target cell

is also DCH after a handover, a handover attempt is made first according to

the current rate. If the handover fails, another handover attempt is made

according to the GBR of the current services or the minimum rate grade of

DRBC (for details, see ZTE UMTS DRBC Algorithm Feature Guide), to

improve the handover success rate.

If the current channel type is HS-DSCH/E-DCH or HS-DSCH/DCH, and DCH

after a handover, the handover is performed directly according to the GBR of

the current services or the minimum rate grade of DRBC (for details, see ZTE

UMTS DRBC Algorithm Feature Description).

If the channel type is DCH before a handover and HS-DSCH/E-DCH or

HS-DSCH/DCH after it, the handover is admitted by the HS-DSCH/E-DCH or

HS-DSCH/DCH (for details, see ZTE UMTS DRBC Algorithm Feature Guide).

If the HS-DSCH/E-DCH or HS-DSCH/DCH admission fails, the handover can



also be implemented according to the minimum rate (GBR of services or

minimum rate grade of DRBC) of DCH.

In a cell, only one of Event 2A, Event 2B and Event 2C can be used to trigger an

inter-frequency handover. Which event is used depends on the inter-frequency

handover recommendation strategy parameter InterHoTactic (UUtranCellFDD).

If an inter-frequency handover fails, the penalty timer GresPara6, which is specific

to the UE, is started. The RNC will not process the reported inter-frequency

measurement reports before the timer expires, and will issue a new inter-frequency

measurement control message after the timer expires.

2. Processing of Event 2D

A blind handover attempt is made if there is a ShareCover (UUtranRelation) (2:

Covers) relationship in the inter-frequency adjacent cells.

Compressed mode is initiated and an inter-frequency measurement 2A/2B/2C/2E is

issued if there is no ShareCover (UUtranRelation) (Covers) relation in

inter-frequency adjacent cells or a blind handover fails. For the initiation decision of

compressed mode, see “Compressed Mode Enabling/Disabling”.

3. Processing of Event 2E

All non-working carrier frequencies report Event 2E, indicating that the radio quality

of all inter-frequency adjacent cells is poor and the 3G system quality deteriorates. If

there is any Inter-RAT adjacent cell that has cover relation (GsmShareCover

(UGsmRelation) value is “2 GSM neighboring cell covers the serving cell”) with the

current serving cell, an inter-RAT blind handover is implemented.

All non-working carrier frequencies report Event 2E, indicating that the radio quality

of all inter-frequency adjacent cells is poor and the 3G system quality deteriorates. If

the serving cell does not have any inter-RAT neighboring cell with cover relation

(GsmShareCover (UGsmRelation) value is not “2 GSM neighboring cell covers the

serving cell”), an inter-RAT measurement Event 3A/3C is issued.

4. Processing of Event 2F



Compressed mode and inter-frequency measurement disabling can be triggered.

For details, see Compressed Mode Enabling/Disabling and “Inter-Frequency

Measurement Control Method Measurement Deletion”.

5.1.2.5 Minimum Quality Judgement Strategy in Inter-frequency Handover

For 2A, 2B, 2C events:

1. CresPara6 (UCelInfoFDD) is set to “1: On”.

2. The UE reports Event 2A/2B/2C.

3. The quality of the target cell: CPICH EcNo<=GresPara2 (URncFunction) or CPICH

RSCP<=GresPara5 (URncFunction).

If these conditions are met, the RNC will not process Event 2A/2B/2C reported by the

UE.

5.1.2.6 Processing of Inter-Frequency and Inter-RAT Events in Buffer

If the RNC receives a measurement report and does not process it, the RNC may miss

handover opportunities and even drop the call when the RNC processing other events

such as the radio bearer reconfiguration procedure. So, the RNC needs to buffer these

events and does not process them until the current event has been processed.

There are six inter-frequency measurement events and six inter-RAT measurement

events in the buffer at most.

For event 2D/2F, if the measurement quantity (NonIntraMeasQuan

(UUtranCellFDD)) is “CPICH EcNo” or “CPICH RSCP”, the RNC will only buffer the

measurement events with the same measurement quality defined by

NonIntraMeasQuan (UUtranCellFDD). If the measurement quantity

(NonIntraMeasQuan (UUtranCellFDD)) is “CPICH EcNo and CPICH RSCP”, the

RNC will buffer the latest events with CPICH EcNo and CPICH RSCP measurement

quantity individually.



If Event 2A/2B/2C/2E or 3A/3C measurement event exists in the buffer and the

newly reported Event 2F has the same measurement quantity as

NonIntraMeasQuan (UUtranCellFDD), the RNC will delete the 2A/2B/2C/2E or

3A/3C and buffer Event 2F. Otherwise, the RNC will not process Event 2F.

If Event 2F with the same measurement quantity defined by NonIntraMeasQuan

(UUtranCellFDD) exists in the buffer, when Event 2A/2B/2C/2E or 3A/3C is reported,

the RNC will not process Event 2A/2B/2C/2E or 3A/3C. Otherwise, the RNC will

buffer these events.

After an intra-frequency and Intra-frequency hard handover, the RNC needs to

discard all measurement events in the buffer.

5.1.2.7 Parameter Configuration Strategies

Inter-frequency event parameter configuration

There are six inter-frequency measurement events (2a, 2B, 2C, 2D, 2E, and 2F) in

total. The number of events configured depends on the parameter MeasEvtNum (If

the measurement is an event-triggered measurement and the measurement

quantity is EcNo, for Event 2D/2F used for the EUTRAN system, this parameter is

obtained from UInterEcNoEvMeasforE. For Event 2D/2F used for the GSM system,

this parameter is obtained from UInterEcNoEvMeasforG. For inter-frequency

measurement events used for the UTRAN system, this parameter is obtained from

UInterEcNoEvMeasforU. If the measurement is an event-triggered measurement

and the measurement quantity is RSCP, for Event 2D/2F used for the EUTRAN

system, this parameter is obtained from UInterRscpEvMeasforE. For Event 2D/2F

used for the GSM system, this parameter is obtained from UInterRscpEvMeasforG.

For inter-frequency measurement events used for the UTRAN system, this

parameter is obtained from UInterRscpEvMeasforU), and the inter-frequency

events configured depends on the parameter meaEvtId (If the measurement is an

event-triggered measurement and the measurement quantity is EcNo, for Event

2D/2F used for the EUTRAN system, this parameter is obtained from

UInterEcNoEvMeasforE. For Event 2D/2F used for the GSM system, this parameter

is obtained from UInterEcNoEvMeasforG. For inter-frequency measurement events

used for the UTRAN system, this parameter is obtained from



UInterEcNoEvMeasforU. If the measurement is an event-triggered measurement

and the measurement quantity is RSCP, for Event 2D/2F used for the EUTRAN

system, this parameter is obtained from UInterRscpEvMeasforE. For Event 2D/2F

used for the GSM system, this parameter is obtained from UInterRscpEvMeasforG.

For inter-frequency measurement events used for the UTRAN system, this

parameter is obtained from UInterRscpEvMeasforU). meaEvtId is defined through

array, and the dimension of array is equal to MeasEvtNum, which is six at most.

Handover parameter configuration strategy in macro diversity

All measurement parameters are cell-based. In macro diversity, the measurement

parameters configured in the best cell will be used as handover parameters. If the

best cell changes, the measurement parameters need to be updated at the same

time.

For inter-RNC handover, if there is an SRNC cell in the active set, the measurement

parameters of the best cell in the SRNC will be used as handover parameters, and if

there is no SRNC cell in the active set, the measurement parameters of the last

SRNC cell in the active set will be used as handover parameters.

Configuration of several sets of handover parameters

The inter-frequency handover parameters can be separately configured based on

measurement quantity, measurement reporting mode and service bearer type. In

this way, several sets of measurement parameters are necessary for different

purposes. The specific categories are described as follows:


NonIntraMeasQuan (UUtranCellFDD) (CPICH RSCP or EcNo or both)

Note:

When NonIntraMeasQuan (UUtranCellFDD) is configured to “EcNo” or “RSCP”,

only the 2D/2F events corresponding measurement quality are issued.

When NonIntraMeasQuan (UUtranCellFDD) is configured to “EcNo and RSCP”,

two categories of 2D/2F measurement events about CPICH EcNo and CPICH



RSCP are configured and one of 2D measurement events can trigger compressed

mode. After compressed mode is triggered, the inter-frequency event of the

corresponding measurement quantity will be issued according to that of 2D event.

For example, if the measurement quantity of triggering 2D event is CPICH EcNo,

only an inter-frequency event of CPICH EcNo will be issued.


Event-triggered reporting or periodical reporting

Service bearer type (srvCategory (UInterMeaSrvSpec))










Not Related to Service Type (Used for detected set measurement)

Note:

(1) When concurrent services exist and include CS+PS services, the Multi RAB


(2) When concurrent services exist and include non-CS services, the RT RAB


(3) When the above principles are met simultaneously, the first one prevails.



To facilitate parameter modification and optimization, the inter-frequency

parameters are index-organized. The index quotations are listed as follows:

Figure 5-1 Inter-Frequency Handover Index Quotations


CellFDD)

UInterMeasProfile(UInterMeasProfile)

UInterMeaSrvSpec(UInterMeaSrvSpe

c)

UInterMeasNoSrvSpec(UInterMeasNo

SrvSpec)

refUInterMeasProfile

UInterRscpEvM

easforG(UInterR

scpEvMeasforG

)

UInterEcNoPrd

Meas(UInterEc

NoPrdMeas)

UInterRscpEvM

easforU(UInterR

scpEvMeasforU

)

UInterEcNoEvM

easforG(UInterE

cNoEvMeasforG

)

srvCategory

NonIntraMeasQuan NonIntraMeasQuan

InterMeasCfgNo

(UInteRscpEvM

easforU)

InterMeasCfgNo

(UInterEcNoEv

MeasforG)

InterMeasCfgNo

(UInteRscpEvM

easforG)

interMeasCfgNo

(UInterEcNoPrd

Meas)

UInterEcNoEvM

easforU(UInterE

cNoEvMeasforU

)

InterMeasCfgNo

(UInterEcNoEv

MeasforU)

UInterEcNoEvM

easforG(UInterE

cNoEvMeasforE

)

InterMeasCfgNo

(UInterEcNoEv

MeasforE)

UInterRscpEvM

easforG(UInterR

scpEvMeasforE)

InterMeasCfgNo

(UInteRscpEvM

easforE)

UInterEcNoPrd

Meas(UInterEc

NoPrdMeas)

interMeasCfgNo

(UInterRscpPrd

Meas)

Note: When a new cell is set up, the value of intialHoCelSelScene (UInterMeasProfile)


Scene) is determined according to the actual cell scene (indicated by HoCelSelScene

(UUtranCellFDD)), and the available inter-frequency measurement profile corresponding

to intialHoCelSelScene is configured for the cell.

Before inter-frequency handover parameters are obtained, profileId

(UInterMeasProfile) of the cell is found based on refUinterMeasProfile

(UUtranCellFDD), and then, in UinterMeasProfile configuration items, the next level

managed object is obtained according to the current measurement application type:

For event-triggered measurements, “Inter-frequency Measurement Configuration

Related to Traffic Category Object ID(UInterMeaSrvSpec)” is selected. For

periodical measurements, “Inter-frequency Measurement Configuration Unrelated to

Traffic Category Object ID (UInterMeasNoSrvSpec)” is selected.



In the managed object decided above, “Inter-Frequency Measurement

Configuration No. (InterMeasCfgNo)” is found based on “Traffic

Category(srvCategory(UInterMeaSrvSpec))” and “Measurement

Quantity(NonintraMeasQuan)”. Finally, the corresponding inter-frequency handover

measurement parameters are found. The details are as follows:

(1). Event-triggered measurement

i. Inter-frequency measurement events used for the UTRAN system


from the managed object UInterEcNoEvMeasforU.


from the managed object UInterRscpEvMeasforU.

ii. Event 2D/2F used for the GSM system


from the managed object UInterEcNoEvMeasforG.


from the managed object UInterRscpEvMeasforG.

iii. Event 2D/2F used for the EUTRAN system


from the managed object UInterEcNoEvMeasforE.


from the managed object UInterRscpEvMeasforE.

(2). Periodical measurement


from the managed object UInterEcNoPrdMeas.


from the managed object UInterRscpPrdMeas.



Correspondence between other parameters that need to be filled into the

inter-frequency measurement control message

Inter-Frequency measurement quantity and Inter-frequency measurement report

criteria are automatically filled by the system based on InterMeasCfgNote.

For the cells of the neighbor RNC, if the value of Primary CPICH Power

Configuration Tag (PcpichPwrPre (UExternalUtranCellFDD)) is TURE, the cell

information of the inter-freq measurement should include the Primary CPICH Power

for this cell. Otherwise the cell information of the inter-freq measurement should not

include the Primary CPICH Power for this cell.

Switch of inter-frequency handover based on measurement for different services

There are several switches for different services to control whether

measurement-based inter-frequency handovers can be performed. When such a

switch is open, it is allowed to perform inter-frequency handovers for the

corresponding service. Otherwise, the RNC forbids inter-frequency handovers for

the service by not activating the inter-frequency measurement. The switches for

different services are described as followed:

Service Switch

AMR amrIfHoSw (ULogicalRnc)

R99 RT r99RtIfHoSw (ULogicalRnc)

R99 NRT r99NrtIfHoSw (ULogicalRnc)

HSDPA hsdpaIfHoSw (ULogicalRnc)

HSUPA hsupaIfHoSw (ULogicalRnc)

Strategy of coupling between intelligent carrier power off/on and inter-frequency

handover

When the intelligent carrier power control is enabled, and the cell meets the

conditions of carrier power off, compressed mode must be initiated for

inter-frequency/inter-RAT measurements, no matter what IfOrRatHoSwch

(UCelInfoFDD) or

amrIfHoSw/r99RtIfHoSw/r99NrtIfHoSw/hsdpaIfHoSw/hsupaIfHoSw (ULogicalRnc)

is.




During the neighboring cells configuration, the adjacent cell list used for reselection in

non-CELL_DCH state and that used for handovers in CELL_DCH state can be

configured separately. During handovers, target cells are selected by neighboring cells

configuration state (StateMode (UUtranRelation)). When the UE is in macro diversity

state, the neighboring cell list is a combination of neighboring cell lists of each cell in the

active set, so the number of inter-frequency neighboring cells may exceed 32, which is

the maximum number specified by the protocol. If the number of inter-frequency

neighboring cells exceeds 32, some cells must be deleted to ensure that there are only

32 inter-frequency neighboring cells. With minimal impact on the UEs in the active set,

these dropped cells are those with poorer signal quality or remoter geographical location.

Therefore, each inter-frequency neighboring cell is configured with a priority.

5.1.3.1 Cell priority configuration

The OMCR configuration parameter MeasPrio (UUtranRelation) defines the priority of

adjacent cells with three values (0: High priority; 1: Medium priority; 2: Low priority). The

value of MeasPrio (UUtranRelation) must be set by the network planning engineer based

on the existing network conditions (for example, adjacent cell quality and geographical

location of adjacent cell). 0 shows the cell priority configuration based on the

geographical location of adjacent cells. For example, for the configuration of cells

adjacent to the innermost gray cell, there are three layers of adjacent cells surrounding

the gray cell, and they are differentiated from one another with yellow (0: Top priority),

blue (1: Medium priority) and red (2: Low priority).



Figure 5-2 Cell Priority Configuration

Source Cell

Priority 0

Priority 1

Priority 2


As specified in the protocol, the maximum number of inter-frequency adjacent cells is 32.

When the UE is in macro diversity state, the total number of inter-frequency adjacent

cells in the macro diversity may exceed 32, so some strategies are required to control the

number within 32, including:

Priority combination strategy

If a cell is adjacent to several inter-frequency cells in the active set, that is, the priority

levels configured for this cell may vary, the priority levels of this cell are combined and

the highest priority level prevails.

Sorting strategy

If the total number of inter-frequency adjacent cells in the active set is 32, the system

prioritizes them in descending order and places the cells in excess of 32 into the

inter-frequency adjacent cell reserve list, which can buffer at most 8 truncated

inter-frequency cells.

The priority levels of adjacent cells in the inter-frequency adjacent cell list will be updated

whenever Event 1A/1B/1C/1D is triggered. If Event 1B is triggered and the number of



inter-frequency adjacent cells is less than 32, the system selects cells from the reserve

list in descending order of priority and places them into the inter-frequency adjacent cell

list. The number of cells that can be selected: min (32 – Number of existing cells in the

inter-frequency adjacent cell list, Number of cells in the reserve list).

5.2 Handling Mechanism for Periodical Report of

Inter-Frequency and Inter-RAT Handover

Measurement

The periodical reporting is that a report of inter-frequency/inter-RAT measurement result

is sent by the UE periodically based on the periodical report interval (PrdRptInterval (For

an inter-frequency measurement, if the measurement quantity is EcNo, this parameter is

obtained from UInterEcNoPrdMeas. If the measurement quantity is RSCP, this

parameter is obtained from UinterRscpPrdMeas. For an inter-RAT measurement, if the

measurement quantity is EcNo, this parameter is obtained from URatEcNoPrdMeas. If

the measurement quantity is RSCP, this parameter is obtained from URatRscpPrdMeas))

and the amount of periodical reports (PrdRptAmount (For an inter-frequency measurement,

if the measurement quantity is EcNo, this parameter is obtained from

UInterEcNoPrdMeas. If the measurement quantity is RSCP, this parameter is obtained

from UInterRscpPrdMeas. For an inter-RAT measurement, if the measurement quantity

is EcNo, this parameter is obtained from URatEcNoPrdMeas. If the measurement

quantity is RSCP, this parameter is obtained from URatRscpPrdMeas)) configured by

RNC. The RNC judges inter-frequency/inter-RAT handover events in accordance with

the inter-frequency/inter-RAT event rule defined in the protocol by referring to the

inter-frequency/inter-RAT cell quality periodically reported by the UE. (For details on the

period algorithm, see “5.11 Inter-frequency and Inter-RAT Period Measurement

Algorithm”)

A long interval set in periodical reporting mode may result in call drop due to handover

delay. Therefore, it is recommended to set the interval to a low value. However, setting a

short interval will increase the signaling load of radio interface and easily lead to

signaling congestion, so event-triggered reporting is generally preferred.



5.3 Downlink Coverage Based Inter-Frequency

Handover

Downlink coverage uses Events 2D and 2F as a criterion to evaluate the quality of

current working carrier frequency signals. For details on processing strategies of Events

2D and 2F, see “Processing of Inter-Frequency Events”.

A coupling relationship exists among the coverage-based handover, uplink BLER-based

handover, uplink transmit power-based handover, downlink transmit power-based

handover, and moving speed-based handover. For details on enabling/disabling of

compressed mode and inter-frequency measurement setup/release, see

“Inter-Frequency Handover Strategy--> Coupling Processing of Different Handovers”.

5.4 Uplink BLER Based Inter-Frequency Handover

The activation of uplink BLER-based inter-frequency handovers is controlled through the

parameters RncUlBlerHoSwch and UlBlerHoSwch (UUtranCellFDD).

This strategy only applies to the DCH.

When the values of RncUlBlerHoSwch and UlBlerHoSwch (UUtranCellFDD) are both

“ON”, the RNC periodically collects the statistics of uplink BLER. If the uplink BLER value

exceeds a certain threshold (1.25%) and the Sirtarget value (real-time measurement

result) reaches the maximum value of SIR (ULMaxSIR) configured in the OMCR, then

the outer loop power control is already invalid and the uplink quality worsens. In such a

case, the UE is handed over into its inter-frequency adjacent cell that has ShareCover

(Covers) relation with the current cell, or an inter-frequency measurement is initiated.

The processing strategy is the same as that of Event 2D. For details, see Event 2D

processing in “Processing of Inter-Frequency Events”.



5.5 Uplink Transmit Power Based Inter-Frequency

Handover

The activation of uplink transmit power-based inter-frequency handovers is controlled

through the parameters RncTxPwrHoSwch and UlPwrHoSwch (UUtranCellFDD).


When the values of RncTxPwrHoSwch and UlPwrHoSwch(UUtranCellFDD) are both

“ON”, the RNC sets up the internal measurement of UEs when a service is initially

established. The UE internal measurement mainly measures the UE transmission power

(TxP) by event report.

Before obtaining the UE‟s internal measurement parameters, the profileId

(UUeIntMeasProfile) of the cell is found based on refUUeIntMeasProfile(UUtranCellFDD).

Then, according to the current measurement purpose “UE Transmitted Power Event

Measurement for Handover”, the managed object UHoEvtTPUeInt is obtained from

UUeIntMeasProfile configuration items. Finally, “UE Internal Measurement Configuration

Index (UeIntMCfgNo (UHoEvtTPUeInt))” and the following corresponding internal

measurement parameters are obtained from UHoEvtTPUeInt.

Measurement Report Transfer Mode measRptTrMod(UHoEvtTPUeInt)

Filter Coefficient filterCoeff(UHoEvtTPUeInt)

Maximum Event Number of UE Internal Measurement measEvtNum(UHoEvtTPUeInt)

UE Internal Measurement Event Identity meaEvtId(UHoEvtTPUeInt)

Time to Trigger(ms) trigTime(UHoEvtTPUeInt)

When the transmit power of the UE meets these threshold requirements, the UE will

report the corresponding events. After receiving an Event 6A report (The uplink power of

the UE exceeds txPowerThres(UHoEvtTPUeInt)) or an Event 6B report (The uplink

power of the UE is less than txPowerThres(UHoEvtTPUeInt)), the RNC uses the same

processing strategy as that of 2D or 2F, respectively. For details, see the Events 2D and

2F processing strategies in “Processing of Inter-Frequency Events”.



5.6 Downlink Transmit Power Based Inter-Frequency

Handover

The activation of downlink transmit power-based inter-frequency handovers is controlled

through the parameters RncTxPwrHoSwch and DlPwrHoSwch (UUtranCellFDD).


The Node B periodically sends the dedicated measurement report of downlink transmit

power to the RNC.

When the values of RncTxPwrHoSwch and DlPwrHoSwch (UUtranCellFDD) are both

“On”, the RNC will judge the downlink code power (DTCP) mentioned in the dedicated

measurement report sent by the Node B.

Obtaining of the Node B dedicated measurement parameters: According to the current

measurement purpose “Event A Report Parameters for TCP in Handover Control”/”

Event B Report Parameters for TCP in Handover Control”, the following parameters used

for handover control are obtained from the sub-object UNbDedMeas of the object

UNbDedMeasProfile:

Dedicated Measurement Type DedMeasType (UNbDedMeas)

Measurement Change Time /Measurement Hysteresis

Time EvtAbcdefTime (UNbDedMeas)

Measurement Filter Coefficient MeasFilterCoeff (UNbDedMeas)

Report Period RptPrd(UNbDedMeas)

Choice Report Periodicity Scale RptPrdUnit (UNbDedMeas)

Report Characteristics RptType(UNbDedMeas)

Measurement Threshold of Event A/B for Transmitted

Code Power EvtAbTcpThrd(UNbDedMeas)

NbDed Measure Configuration No NbDMCfgNo(UNbDedMeas)

When the DTCP value reaches the threshold of Event A, it indicates that the downlink

power is very high. In such a case, the UE is handed over to its inter-frequency adjacent



cell that has ShareCover (Covers) relation with the current cell, or an inter-frequency

measurement is initiated. The processing strategy is the same as that of Event 2D. When

the DTCP value reaches the threshold of Event B, the processing strategy is the same as

that of Event 2F. For details, see Event 2D/2F processing in “Processing of

Inter-Frequency Events”

5.7 Load Control Based Handover

When the load (downlink carrier power (TCP) or total uplink receive wideband power

(RTWP)) of a cell reaches a high level, if the cell has some less-loaded inter-frequency

adjacent cells that have ShareCover (Overlap or Covers) relation with this cell (judged

through ShareCover(UUtranRelation)), the RNC will hand over some UEs with low

priority from this cell into its adjacent cells to reduce this cell‟s load and ensure system

stability.

For details on load handover, see ZTE UMTS Overload Control Feature Guide.

5.8 Moving Speed Based Handover

In the Hierarchical Cell Structure (HCS), Macro cells are used to carry the fast-moving

UEs and they have low HCS priority (HcsPrio (for the current cell, this parameter is

obtained from UUtranCellFDD. For neighboring UTRAN cells, this parameter is obtained

from UExternalUtranCellFDD. For neighboring GSM cells, this parameter is obtained

from UExternalGsmCell)). Micro cells are used to carry the slow-moving UEs and they

have high HCS priority (HcsPrio).

The purpose of moving speed-based handovers is to hand over the fast-moving and

slow-moving UEs into Macro and Micro cells, respectively. The handover between Macro

and Micro cells requires an algorithm for judging the moving speeds of UEs. Whether to

process the handover judgement based on moving speed depends on the parameter

HcsSupportInd(URncFunction).

The number of best cell changes per unit time is taken as a criterion for judging the

moving speed of UEs. The more times the best cell changes per unit time, the faster the

moving speed. The number of best cell changes is based on the number of Event 1D



reports.

5.9 Coupling Processing of Different Handovers

Inter-frequency handover can be triggered by the following:

Load control

Downlink coverage events

Uplink transmit power

Uplink BLER

Downlink transmit power

Moving speed of UE

The load control-based handover aims to quickly reduce system loads and ensure

system stability, and it has the top priority. The handovers based on downlink coverage

events, uplink transmit power, uplink BLER or downlink transmit power aim to guarantee

the call QoS and user experience, and they have lower priority. The moving speed-based

handover in the HSC is used to appropriately allocate traffic for different cells, make full

use of system resources and enhance system performance. The moving speed-based

handover is a system optimization function and has the lowest priority.

The handover with top priority will shield the handovers with comparatively lower priority.

For example, if a load control-based handover occurs in a cell, the RNC can no longer

hand over or access new services into the cell. In the case of a poor carrier quality, the

RNC needs to hand over the UE into the cell with good quality through radio quality

measurement, without taking account of the moving speed of UE.



5.10 Inter-frequency and Inter-RAT Measurement Choice

When a cell has both neighboring inter-frequency and neighboring inter-RAT cells,

IfOrRatHoSwch (UCelInfoFDD) is used to indicate the priority of inter-frequency and

inter-RAT handovers.

IfOrRatHoSwch indicates “Turn off Inter-frequency and Inter-RAT Handover”.

Neither inter-frequency measurement nor inter-RAT measurement will be issued by

the RNC.

IfOrRatHoSwch indicates “Only Inter Frequency”.

If inter-frequency neighboring cells exist, the parameters of

inter-frequency 2D/2F event are initially issued (If the measurement

quantity is EcNo, the parameters are obtained from

UInterEcNoEvMeasforU. If the measurement quantity is RSCP, the

parameters are obtained from UInterRscpEvMeasforU). When

compressed mode is activated, only inter-frequency measurements are

issued by the RNC.

If no inter-frequency neighboring cell exists, no inter-frequency

measurement is issued by the RNC.

IfOrRatHoSwch indicates “Only Inter RAT”.

If both GSM and EUTRAN neighboring cells exist, according to

ChoStraMulRatHo(UCelInfoFDD), the parameters of inter-RAT 2D/2F

events are initially issued (If the measurement quantity is EcNo, the

parameters of EUTRAN inter-RAT 2D/2F events are obtained from

UInterEcNoEvMeasforE, and the parameters of GSM inter-RAT 2D/2F

events are obtained from UInterEcNoEvMeasforG. If the measurement

quantity is RSCP, the parameters of EUTRAN inter-RAT 2D/2F events

are obtained from UInterRscpEvMeasforE, and the parameters of GSM

inter-RAT 2D/2F events are obtained from UInterRscpEvMeasforG).

When compressed mode is activated, only RATx measurements

according to ChoStraMulRatHo are issued by the RNC.



If only GSM or EUTRAN neighboring cells exist, the parameters of GSM

inter-RAT 2D/2F events or EUTRAN inter-RAT 2D/2F events are initially

issued. When compressed mode is activated, only GSM or EUTRAN

measurements are issued by RNC.

If no inter-RAT neighboring cell exists, no inter-RAT measurement will be

issued by the RNC.

IfOrRatHoSwch indicates “Inter Frequency Is Prior to Inter RAT”.

If Only inter-frequency neighboring cells exist, the parameters of

inter-frequency 2D/2F events are initially issued. When compressed

mode is activated, inter-frequency measurements are issued by the RNC.

If only both GSM and EUTRAN neighboring cells exist, the parameters of

inter-RAT 2D/2F events are initially issued. When compressed mode is

activated, only RATx measurements according to ChoStraMulRatHo

(UCelInfoFDD) are issued by the RNC.

If only GSM or EUTRAN neighboring cells exist, the parameters of GSM

inter-RAT 2D/2F events or EUTRAN inter-RAT 2D/2F events are initially

issued. When compressed mode is activated, GSM or EUTRAN

measurements are issued by the RNC.

If both inter-frequency and inter-RAT neighboring cells exist, the RNC will

initially issue the parameters of inter-frequency 2D/2F events, and then

configure the inter-frequency measurement first when compressed mode

is activated and start the timer T4StpIfMeaActRat (URncFunction), when

a 2E event is reported or T4StpIfMeaActRat (URncFunction) expires, the

RNC will reconfigure the inter-frequency measurement to inter-RAT

measurement.



5.11 Inter-frequency and Inter-RAT Period Measurement

Algorithm

Inter-frequency and inter-RAT measurement can use event-triggered reporting method

or periodical reporting method, which is controlled by the RNC level parameters

InterHoMth and IntRatHoMth. When InterHoMth and IntRatHoMth are both “1: Event

Method”, the handover strategy corresponding to the event-triggered measurement is

used (For details, see “5.1.2.4 Processing of Inter-Frequency Events” and “5.10

Inter-frequency and Inter-RAT Measurement Choice”). Otherwise, the inter-frequency

and inter-RAT period measurement algorithm described below is used.

5.11.1 Period Measurement Configuration

InterHoMth is “0: Periodical Method”, IntRatHoMth is “1: Event Method”

The RNC issues period measurement configuration for inter-frequency measurement,

and event measurement configuration for inter-RAT measurement. Inter-frequency and

inter-RAT compressed modes are still activated separately. (For details about issuing

inter-frequency measurements or inter-RAT measurements, see “5.10 Inter-frequency

and Inter-RAT Measurement Choice”)

InterHoMth is “1: Event Method”, IntRatHoMth is “0: Periodical Method”

The RNC issues event measurement configuration for inter-frequency measurement,

and period measurement configuration for inter-RAT measurement. Inter-frequency and

inter-RAT compressed modes are still activated separately. (For details about issuing

inter-frequency measurements or inter-RAT measurements, see “5.10 Inter-frequency

and Inter-RAT Measurement Choice”)

InterHoMth is “0: Periodical Method”, IntRatHoMth is “0: Periodical Method”

IfOrRatHoSwch is “Only Inter Frequency” or “Only Inter RAT”

The RNC issues period measurement configuration for both inter-frequency and

inter-RAT measurements. (For details about issuing inter-frequency measurements or



inter-RAT measurements, see “5.10 Inter-frequency and Inter-RAT Measurement

Choice”)

IfOrRatHoSwch is “Inter Frequency Is Prior to Inter RAT”

Inter-frequency handover and inter-RAT handover are allowed.

a) When compressed mode is initiated by Event 2D, BLER or uplink/downlink transmit

power, the RNC issues inter-frequency and inter-RAT period measurement

configurations and activates the corresponding compressed modes simultaneously.

b) When compressed mode is initiated by measurement-based balancing or moving

speed-based inter-frequency handover, if the current frequency quality is good, only

inter-frequency period measurement configuration is issued and the corresponding

compressed mode is activated. Otherwise, the same strategy described in a) is

performed.

c) When compressed mode is initiated by the value of service handover IE, if the

current frequency quality is good, only inter-RAT period measurement configuration

is issued and the corresponding compressed mode is activated. Otherwise, the

same strategy described in a) is performed.

Note:

1) When the period measurement algorithm is used, Event 2D/2F is still reported by

using the event-triggered method.

2) When the measurement quantity is CPICH EcNo+RSCP, the period measurement

configuration corresponding to CPICH RSCP is selected.

3) When IntRatHoMth is “0: Periodical Method”, only two sets of compressed modes

(GSM carrier RSSI Measurement, GSM Initial BSIC Identification) are configured for

GSM; and inter-frequency and inter-RAT compressed modes are configured

simultaneously regardless of CompMdCfgStra.



5.11.2 Processing of Period Measurement Report

For one neighbor cell‟s period measurement report reported by the UE, the RNC will

judge it in accordance with the inter-frequency/inter-RAT event rule. If an event (M) is

met, the cell-specific timer PeriodTriggerTime (UCelInfoFDD) is initiated and Event M is

recorded. Event M will be exported as the final event, if the neighboring cell‟s periodical

measurement reports keep meeting Event M until the timer expires. Follow-up handovers

are still processed based on the existing handover strategy for event-triggered reporting.

Judgment criterion of periodical measurement report

(1). For inter-frequency measurements, the target cell is judged according to the Event

2C triggering rule.

QTarget_Freq_Cell+ CIOTarget_Freq_Cell>= TTarget_Freq_Cell+H/2

Where:

QTarget_Freq_Cell: Refers to the quality of the target carrier frequency.

CIOTarget_Freq_Cell: Refers to the cell individual offset of the target carrier frequency

especially defined for periodical measurement, whose value isCellIndivOffset

(UUtranRelation).

TTarget_Freq_Cell: Refers to the absolute threshold (ThreshNoUsedFreq (If the measurement



UInterRscpEvMeasforU)) of good quality non-working carrier frequency in an Event 2C

decision.

H: Refers to the handover decision hysteresis parameter (Hysteresis (If the



UInterRscpEvMeasforU)) of Event 2C.

(2). For inter-RAT measurements, the target cell is judged according to the Event 3C

triggering rule.

QTarget_Rat_Cell+ CIOTarget_Rat_Cell>= TTarget_Rat_Cell+H/2



Where:

QTarget_Rat_Cell: Refers to the quality of the target system cell.

CIOTarget_Rat_Cell: Refers to the cell individual offset of the target system cell

(CellIndivOffset (UExternalGsmCell)).

TTarget_Rat_Cell: Refers to the absolute threshold of other systems (ThreshSys (for

E-UTRAN cell, if the measurement quantity is EcNo, this parameter is obtained from

URatEcNoEvMeasforE. If the measurement quantity is RSCP, this parameter is obtained

from URatRscpEvMeasforE; for GSM cell, if the measurement quantity is EcNo, this

parameter is obtained from URatEcNoEvMeasforG. If the measurement quantity is

RSCP, this parameter is obtained from URatRscpEvMeasforG));

H: Refers to the hysteresis parameter (Hysteresis (For E-UTRAN cells, if the

measurement quantity is EcNo, this parameter is obtained from URatEcNoEvMeasforE.


URatRscpEvMeasforE. For GSM cells, if the measurement quantity is EcNo, this


RSCP, this parameter is obtained from URatRscpEvMeasforG)) for a 3C event decision.

Note:

1) When NonIntraMeasQuan is CPICH EcNo+ CPICH RSCP, period measurement

results corresponding to CPICH EcNo and CPICH RSCP must meet Event 2C or

3C.

5.12 Inter-Frequency Handover Procedure

Inter-frequency handovers are all hard handovers, and their procedures are identical with

intra-frequency hard handovers.



6 Inter-RNC Mobility

6.1 SRNS Relocation

SRNS relocation can be categorized into relocation of UE not involved (soft

handover-triggering) and relocation of UE involved (hard handover-triggering),

depending on UE relevance.

Relocation of UE not involved

It belongs to the soft handover relocation, and the UE can use radio resources in the

DRNC and connect with the CN through the SRNC. The triggering conditions are

described as follows:

There is an Iur interface between RNCs.

The switch of relocation of UE not involved is open. It is differentiated by CS

service and PS service, RncFeatSwitchBit10 is for CS service and

RncFeatSwitchBit11 for PS service.

When all radio links are handed over to the DRNC, the timer

(CsReDelayTimer(UIurLink) is activated and PsReDelayTImer(UIurLink) are

configured according to CS service and PS service respectively, the timer of

CS service is considered for the multi-RAB service) and a relocation is

performed when the corresponding timer expires.

Relocation of UE involved

It belongs to the hard handover relocation. The triggering conditions are described as

follows:

For CS services, the switch of relocation RncFeatSwitchBit0 is open.

For PS services, the switch of relocation RncFeatSwitchBit19 is open.

For CS and PS combined services, the switch of relocation RncFeatSwitchBit0

is open.



Special relocation processing of CS+PS services

If the UE has CS and PS services simultaneously and the DRNC of network vendor does

not support PS relocation, the PS services will be released before an SRNC relocation

with hard handover is performed when the parameter RncFeatSwitchBit4 is set to “1”.

The CS service will begin relocation as soon as the PS service is released. As a result,

the CS service will be kept, but the PS service will be reestablished by the UE

automatically.

6.1.1 Relocation Triggered by Soft Handover

Figure 6-1 Relocation Triggered by Soft Handover

UE

Target

RNCSGSN

Source

RNC

1.Relocation Required

2.Relocation Request

3.Relocation Request Ack

4.Relocation Command

5.Relocation Commit

6.Relocation Detect

7.UTRAN Mobility

Information

8.UTRAN Mobility

Information Confirm

9.Relocation Complete

10.Iu Release Command

11.Iu Release Complete

Procedure description:

1. Upon detecting that all links already exist in a DRNC, the SRNC initiates the

relocation procedure and sends a “Relocation Required” message to the CN. If the

SRNC connects with CS and PS domains, it needs to send the “Relocation

Required” message to the CS and PS domains. When the SRNC sends the

Relocation Required message, it starts the timer Trelocprep(UIuCnst). Upon

receiving the Relocation Command message, the SRNC stops the timer and

terminates the Relocation Preparation procedure. If there is no response from the



CN to the Relocation Required message before the timer Trelocprep(UIuCnst)

expires, the SRNC cancels the Relocation Preparation procedure by initiating the

Relocation Cancel procedure with the cause “Trelocprep expiry”.

2. The CN sends a “Relocation Request” message to the DRNC, carrying the “RAB

SETUP” IE.

3. After the RAB of DRNC is established successfully, the DRNC sends a “Relocation

Request Ack” message to the CN.

4. The CN sends a “Relocation Command” message to the SRNC, requiring the

SRNC to start a relocation. Upon receiving the Relocation Command message, the

SRNC stops the timer Trelocprep(UIuCnst), starts the timer Trelocoverall(UIuCnst)

and terminates the Relocation Preparation procedure. If the Iu Release procedure is

not initiated towards the SRNC from the CN before the expiry of

Trelocoverall(UIuCnst), the SRNC initiates the Iu Release Request procedure

towards the CN with cause “Trelocoverall expiry”.

5. The SRNC sends a “Relocation Commit” message to the DRNC through the lur

interface.

6. The DRNC sends a “Relocation Detect” message to the CN and is converted into a

new SRNC through role exchange.

7. The new SRNC sends a “UTRAN Mobility Information” message to the UE to

reallocate U-RNTI.

8. Upon relocating U-RNTI, the UE sends a “UTRAN Mobility Information Confirm”

message to the new SRNC.

9. The new SRNC sends a “Relocation Complete” message to inform the CN of the

successful relocation.

10. Upon receiving the message from the new SRNC, the CN sends an “Iu Release

Command” message to the original SRNC to release all the resources in the original

SRNC.



11. Upon releasing the lu resource, the original SRNC sends an “Iu Release Complete”

message to the CN.

There may be some exceptional procedures during a relocation.

Relocation failure caused by “UTRAN Mobility Information” message transmission

failure

The DRNC fails to initiate the “UTRAN Mobility Information Configuration” procedure

because the procedure times out or the UE fails to return a UTRAN mobility

message. In such a case, the DRNC does not send a “Relocation Complete”

message to the CN, but sends an “Iu Release Request” message to the CN to

release the resources on the DRNC side.

Where “procedure timeout” means: DRNC initiates the timer (400ms) after sending

“UTRAN Mobility Information” (UMI) message to UE, but cannot receive the UMI

confirm message from UE until the timer expires, then DRNC will resend the UMI

message, repeat the process. When the DRNC sends the UMI message for the

fourth time, and the UMI confirm message is not received when the timer expires,

this case is regarded as “procedure timeout”.

Note:

The sent timing of Relocation Detect can be controlled by the parameter

GResPara48(bit11). When GResPara48(bit11) is set to 0, the DRNC will send

Relocation Detect until UTRAN Mobility Information Confirm is received from the UE.

This is different from the above procedures.

Whether to initialize the RNC data forwarding function during a relocation can be

controlled by the parameter RncFeatSwitchBit25 (UIurLink). When

RncFeatSwitchBit25 (UIurLink) is “On”, the RNC will enable this function to

decrease or avoid the data loss in the process of sending UMI.



6.1.2 Relocation Triggered by Hard Handover

Figure 6-2 Relocation Triggered by Hard Handover

UE

Target

RNCSGSN

Source

RNC

1.Relocation Required

2.Relocation Request

3.Relocation Request Ack

4.Relocation Command

7.Relocation Detect

8.Physical Channel

Reconfiguration Complete

9.Relocation Complete

10.Iu Release Command

11.Iu Release Complete

5.Physical Channel

ReconfigurationUE

6.UE detected by target RNC


1 The SRNC initiates a “Relocation Required” message to the CN.

2 Upon receiving the message, the CN sends a “Relocation Request” message to the

DRNC. When the SRNC sends the Relocation Required message, it starts the timer

Trelocprep(UIuCnst). Upon receiving the Relocation Command message, the

SRNC stops the timer and terminates the Relocation Preparation procedure. If there

is no response from the CN to the Relocation Required message before the timer

Trelocprep(UIuCnst) expires, the SRNC cancels the Relocation Preparation

procedure by initiating the Relocation Cancel procedure with the Cause “Trelocprep

expiry”.

3 After the bearer on the lu interface and the radio link are established, the DRNC

returns a “Relocation Request Ack” message to inform the CN that the DRNC is

ready.

4 The CN sends a “Relocation Command” message to the SRNC, requiring the SRNC

to start a relocation.



5 The SRNC sends a “Physical Channel Reconfiguration” message to the UE,

requiring the UE to perform a hard handover. Upon receiving the Relocation

Command message, the SRNC stops the timer Trelocprep(UIuCnst), starts the

timer Trelocoverall(UIuCnst) and terminates the Relocation Preparation procedure.

If the Iu Release procedure is not initiated towards the SRNC from the CN before

the expiry of Trelocoverall(UIuCnst), the SRNC initiates the Iu Release Request

procedure towards the CN with cause “Trelocoverall expiry”.

6 The DRNC initiates a “UE Detect” message to imply that the DRNC already detects

the UE.

7 Upon detecting the UE, the DRNC sends a “Relocation Detect” message to the CN,

and then the DRNC is converted into a new SRNC through role exchange.

8 The UE returns a “Physical Channel Reconfiguration Complete” message to inform

the new SRNC of successful hard handover.

9 Upon receiving the message, the new SRNC sends a “Relocation Complete”

message to the CN.

10 Upon receiving the message from the new SRNC, the CN sends a “Iu Release

Command” message to the original SRNC to release all the resources in the original

SRNC.

11 Upon releasing the lu resource, the original SRNC sends a “Iu Release Complete”

message to the CN.

There may be some exceptional procedures during a relocation.

Relocation failure caused by radio bearer (RB) reconfiguration failure

Upon receiving the RB reconfiguration failure message, the SRNC will send a

relocation cancellation message to the CN and the CN releases the resources on

the DRNC side through the lu release procedure.



6.2 DSCR

6.2.1 R99 DSCR

Like relocation, R99 DSCR is categorized into hard handover DSCR and soft handover

DSCR. The triggering conditions of R99 DSCR are described as follows.

Soft handover DSCR

It means that all radio links are handed over to the DRNC and the relocation is not

performed. The DSCR will be triggered when all the following conditions are met:

The switch of soft handover DSCR RncFeatSwitchBit7 is open.

All radio links are on the DRNC side.

No CS service is included.

Hard handover DSCR

The DSCR will be triggered if all the following conditions are met when the

relocation is output in a hard handover.

The switch of hard handover DSCR RncFeatSwitchBit4 is open.

The hard handover is needed according to the decision.

No CS service is included.

6.2.2 HSPA DSCR


is interconnected via IUR, the RNC introduces HSPA DSCR for HSPA S/I/B services. If

the switch RncFeatSwitchBit15 is 0, the RNC will not process 1A/1C events of the

DRNC's cells. When Event 1D of the DRNC's cells is reported, the RNC will perform a

hard handover DSCR. Otherwise, HSPA DSCR is the same as R99 DSCR.



6.2.3 Common Status DSCR

To avoid the UE staying in common status continuously without any chance for

transferring large amount of data, the following strategy is introduced:

When the UE fails to transfer from common status to Cell_DCH status with the cause of

invalid configuration, if dscrInCmnToDedSwch is “1: On”, the RNC executes the DSCR

procedure, making the UE enter IDLE status and reestablish an RRC connection.

6.3 Coupling between relocation and DSCR

The DSCR is performed first when the conditions of relocation and DSCR are met

simultaneously.

DSCR and hard handover relocation

If there are only PS services, a DSCR is performed when the conditions of

relocation and DSCR are met simultaneously.

If there exists CS services, a relocation is performed.

DSCR and soft handover relocation

If there are only PS services, when the conditions of DSCR are met, a DSCR

is performed.

If there is only CS service, a relocation is performed.

For multi-RAB services, if DSCR conditions of PS service are met, then a

DSCR is performed after CS service is released.

6.4 Special Handling Strategy of IUR

6.4.1 Special Events Processing via IUR for PS0/0

In response to the incompatibility that may occur when IUR exists between different

vendors, for PS0/0 service, the SRNC executes “Special Events Handling via IUR for



PS0/0” if the following conditions are met:


(2). PS0/0 service exists currently.

If these conditions are met, the SRNC will not process Event 1A/1C/1D or 2A/2B/2C of

the DRNC's cells, and releases PS0/0 service and deals with the follow-up reported

events.

6.4.2 Special inter-frequency handover strategy via IUR for HSPA

When the current services of the UE include HSPA services, but the configuration of Iur

does not support the HSPA process, an inter-frequency handover via IUR needs to be

performed (not support “Relocation UE involved” or “Hard handover DSCR”):

If RNCFEATSWITCHBit24 (UIurLink) is set to “0: Not support HSPA fallback procedure

for inter-frequency handover via IUR”, an inter-frequency handover is performed together

with an HSPA transfer to DCH.

If RNCFEATSWITCHBit24 (UIurLink) is set to “1: Support HSPA fallback procedure for

inter-frequency handover via IUR”, an inter-frequency handover is performed after HSPA

is fallen back to DCH.

7 GSM Inter-RAT Handover Policy

Inter-RAT handover is the procedure which an UE handovers from one radio access

system to another, and specifically, from a UTRAN access system to an RATx system.

Inter-RAT handover can be a measurement-based handover between systems or a blind

handover based on GsmShareCover(Overlap or Covers).

The prerequisite of measured-based inter-RAT handover is that the UE measures the

quality of the Inter-RAT neighboring cells. In WCDMA system, for Inter-RAT

measurements in CELL_DCH state, the UE must enable compressed mode for

Inter-RAT measurements unless it has dual receivers. In addition, regarding the

influence of compressed mode on the system and UE, an inter-RAT measurement is



enabled only when the current UTRAN system has poor radio quality. The radio quality of

the current UTRAN system can be measured by four indicators, namely, uplink BLER,

uplink transmit power of the UE, downlink transmit power, and inter-frequency

measurement (quality measurement on the PCPICH by the UE). When receiving the

inter-RAT measurement result reported by the UE, the RNC makes an inter-RAT

handover decision and handovers the UE to the target cell specified in the measurement

result.

7.1 Inter-RAT Measurement

To avoid measurement fluctuations, the UE must perform layer 3 filtering on the

measurement result, and then use the filtered value for event decision and reporting. The

FilterCoeff (If the measurement is an event-triggered measurement and the

measurement quantity is EcNo, this parameter is obtained from URatEcNoEvMeasforG.

If the measurement is an event-triggered measurement and the measurement quantity is

RSCP, this parameter is obtained from URatRscpEvMeasforG. For a periodical

measurement, if the measurement quantity is EcNo, this parameter is obtained from

URatEcNoPrdMeas. If the measurement quantity is RSCP, this parameter is obtained

from URatRscpPrdMeas) is used as the layer 3 filtering factor for intra-system

measurements, and the GsmFilterCoeff(For an event-triggered measurement, if the

measurement quantity is EcNo, this parameter is obtained from URatEcNoEvMeasforG.


URatRscpEvMeasforG. For a periodical measurement, if the measurement quantity is

EcNo, this parameter is obtained from URatEcNoPrdMeas. If the measurement quantity

is RSCP, this parameter is obtained from URatRscpPrdMeas) is used for GSM system

measurements. The principles are the same as the formula for co-frequency

measurement.

Best

N

1i

iUTRANUTRAN LogM10W)(1MLog10WLogM10QA

Where:

QUTRAN indicates the measurement result of the currently used UTRAN frequency (dB for

Ec/No; dBm for RSCP).



MUTRAN indicates the measured physical value of the currently used UTRAN frequency

(ratio for Ec/No; mV for RSCP).

Mi indicates the measured physical value of cell I in the current active set.

NA indicates the number of the cells (excluding best cells) in the active set.

MBest indicates the measurement result of the best cells in the active set.

W (If the measurement quantity is EcNo, this parameter is obtained from

URatEcNoEvMeasforG. If the measurement quantity is RSCP, this parameter is obtained

from URatRscpEvMeasforG) indicates the weight of the best cells in the active set in the

frequency quality evaluation of the currently used UTRAN.

7.1.1 Overview of Inter-RAT Measurement

Inter-RAT measurement is intended to measure inter-RAT cells. In an Inter-RAT

measurement, the measurement quantity of the UTRAN network can be triggered by the

measurement quantity of EcNo or RSCP, or both. Which parameter is used is controlled

by the NonIntraMeasQuan(UUtranCellFDD) parameter. The measurement quantity of

Inter-RAT measurement depends on the systems to be measured. For the GERAN, the

measurement quantity is RSSI.

3GPP defies a series of Inter-RAT measurement events. An UE reports the

corresponding events when the defined conditions are met.

3A: The currently used UTRAN carrier quality is lower than a threshold, and the quality of

other radio systems is higher than a threshold. It is used for decision of Inter-RAT

handover.

/2HTQ 3aUsedUsed and

/2HTCIOM 3aRATOtherRATOtherRATOther

Where:

QUsed indicates the estimated quality of the used frequency of the UTRAN.

TUsed indicates the absolute threshold (Thresh (If the measurement quantity is EcNo, this




RSCP, this parameter is obtained from URatRscpEvMeasforG)) of the currently used

frequency difference.

H3a is the hysteresis parameter (Hysteresis (If the measurement quantity is EcNo, this


RSCP, this parameter is obtained from URatRscpEvMeasforG)) for a 3A event decision.

MOther RAT is the quality measurement result of other systems.

CIOOther RAT is the quality offset of other system cells (CellIndivOffset(UExternalGsmCell).

TOther RAT is the absolute threshold of other systems (ThreshSys (If the measurement

quantity is EcNo, this parameter is obtained from URatEcNoEvMeasforG. If the


URatRscpEvMeasforG)).l

3C: The quality of other radio systems is higher than a threshold. It can be used for a

inter-RAT handover decision.

/2HTCIOM 3cRATOtherRATOtherRATOther

Where:

MOther RAT is the quality measurement result of other systems.

CIOOther RAT is the quality offset of other system cells (CellIndivOffset(UExternalGsmCell).

TOther RAT is the absolute threshold of other systems (ThreshSys (If the measurement

quantity is EcNo, this parameter is obtained from URatEcNoEvMeasforG. If the


URatRscpEvMeasforG)).

H3c is the hysteresis parameter (Hysteresis (If the measurement quantity is EcNo, this


RSCP, this parameter is obtained from URatRscpEvMeasforG)) for a 3C event decision.

During an inter-RAT event decision, the carrier must keep meeting the reporting scope or

threshold of an event for a certain period of time (TrigTime (If the measurement quantity



is EcNo, this parameter is obtained from URatEcNoEvMeasforG. If the measurement

quantity is RSCP, this parameter is obtained from URatRscpEvMeasforG)) before it can

be reported as this event. In this way, improper reporting of Inter-RAT events resulting

from carrier quality fluctuation can be avoided.

7.1.2 Control Methods for Inter-RAT Measurement


The principles for setting up an inter-RAT measurement (service-based Inter-RAT

handover) depend on the value of the service handover IE in the RAB assignment

request message.

When the value of the service handover IE is “Handover to GSM should be

performed”, it indicates that the RAB should switch to the GSM system as soon as

possible. During the service setup or intra-system handover of such a service, if the

serving cell has a GSM neighboring cell and the inter-frequency measurement is not

enabled after the service setup or handover is successful, the RNC enables the

inter-RAT measurement immediately. (Note: The startup policy of service-based

inter-RAT measurements is not checked in the following scenarios:

i. A soft handover succeeds.

ii. Incoming compressed mode relocation of soft handovers is enabled.

When the value of the service handover IE is “Handover to GSM should not be

performed”, it indicates that the RAB can switch to the GSM only when it exceeds

the bearing capability of the UMTS. For such a service, the RNC enables the

inter-RAT measurement only when the quality of the UMTS system is poor. The

specific scenarios are described as follows:

The current working carrier is in poor quality (the measurement method is

described in “5.3 Downlink Coverage Based Inter-Frequency Handover”), but

the conditions for enabling inter-frequency measurements (that is, the

inter-frequency neighboring cell is not configured) or for inter-frequency blind

handover are not met. In this case, if the inter-RAT measurement is not



enabled or the conditions for inter-RAT blind handover are met but the blind

handover fails, an inter-RAT measurement is set up.

The inter-frequency measurement is enabled, and all non-working carriers

trigger 2E events. In this case, if the conditions for inter-RAT blind handovers

are not met and inter-RAT neighboring cells exist, or the conditions for

inter-RAT blind handovers are met, but the blind handover fails, the

inter-frequency measurement is disabled, and an inter-RAT measurement is

set up.

When the value of the service handover IE is “Handover to GSM shall not be

performed”, it indicates that the service cannot be switched to the GSM. For such a

service, the RNC does not enable the inter-RAT measurement or trigger a handover

to GSM.

The parameter srvBasedHoInd(ULogicalRnc) indicates whether the RNC supports

handovers based on service and ServHoSwch(UCelInfoFDD) is used to control

whether a cell open the function. For UEs in macro diversity state,

ServHoSwch(UCelInfoFDD) in the best cell is taken. If the best cell changes,

parameter configuration must be updated.

Service handover strategy controlled by RNC

When IE “service handover” is not included in RAB Assignment Request, the RNC

can perform the service handover strategy by using the parameter

srvHoIndAmr/srvHoIndCs64/srvHoIndPsNRT/srvHoIndPsRT(USrvBasedHo):

If the parameter is set to “Ignore service handover IE”, the RNC will ignore

“service handover” IE in requested RAB, and perform the strategy according to

the value of amrSrvHoStra/cs64SrvHoStra/psRtSrvHoStra/psNrtSrvHoStra

(USrvBasedHo). If the parameter is set to “Apply service handover IE” and

“service handover” is not included in the requested RAB, the RNC will also

perform the corresponding service handover strategy according to the value of

amrSrvHoStra/cs64SrvHoStra/psRtSrvHoStra/psNrtSrvHoStra

(USrvBasedHo). Otherwise, the RNC will perform the strategy based on the

value of “service handover” IE in the requested RAB.



Four service types (AMR/CS64/PS RT/PS NRT) are classified in this strategy

and the RNC performs service handovers according to the parameter

amrSrvHoStra/cs64SrvHoStra/psRtSrvHoStra/psNrtSrvHoStra(USrvBasedHo.

For multi-RAB services, srvHoComStra(USrvBasedHo) is used to control the

combination of service handover values. For example, if the service handover value

of AMR is “Handover to GSM should be performed”, and the value of PS RT service

is “Handover to GSM should not be performed”, the priority of “Handover to GSM

should not be performed” can be set to at a higher level than “Handover to GSM

should be perform”. When AMR and PS RT services are set up simultaneously, the

WCDMA carries the services. Only after the PS RT service is released, the CS

voice service can be handed over to the GSM based on the service handover value.


After the inter-RAT measurement is enabled, the measurement is changed in the

following cases:

After a soft handover, if the inter-RAT measurement parameters and inter-RAT

neighboring cells are changed, the inter-RAT measurement parameters and

inter-RAT neighboring cell list are updated by means of measurement modification.

When a service is added or deleted, if the handover parameters for a single service

or concurrent services are different, the inter-RAT measurement parameters must

be updated by means of measurement modification.


Before the hard handover, inter-RAT measurement is enabled. Terminate the

inter-RAT measurement.

After soft handover, inter-RAT measurement is terminated in any of the following

cases:

The cell in the active set does not have inter-RAT neighboring cells.



The inter-RAT neighboring cells and the cells in the current active set are

neighboring cells with GsmShareCover(Covers).

The inter-RAT neighboring cells and the intra-frequency neighboring cells of

the cells in the current active set are neighboring cells with

GsmShareCover(Covers).

When the service handover value of the service is “Handover to GSM should not be

performed” and the quality of the working carries becomes better (the measurement

method is the same as that described in “5.1.2.3 Measurement Deletion”),

compressed mode is closed, and the GSM measurement is terminated.

In the case of exceptions, for example, an exceptional report of the inter-RAT

measurement task (for example, an unavailable measurement task is received from

the network side), the corresponding inter-RAT measurement is released.

When the RNC sends a MEASUREMENT CONGROL RELEASE message for a

measurement ID, the time stamp is recorded. If the RNC receives the measurement

report for the ID, it compares the current time and the recorded time. If the difference

between the current time and the recorded time exceed the threshold

TResndMeaCtrlRel(URncFunction) configured, the MEASUREMENT CONTROL

RELEASE will be resent. Otherwise, this measurement report will be ignored.

7.1.2.4 Processing of Inter-RAT Events

Processing of 3A/3C events

1) In a cell, inter-RAT handovers can only be triggered by 3A or 3C events, which is

controlled by the inter-RAT handover tactic RatHoTactic(UUtranCellFDD).

2) For GSM handover, when the inter-RAT handover fails, the penalty timer

HoToGsmPenTimer, which is specific to the UE, is started. The RNC will not

process the reported inter-RAT measurement reports before the timer expires, and

will issue new inter-RAT measurement control messages after the timer expires.

When PS service exists, if the UE supports inter-RAT PS service handover and the

parameters psInterSysHoSuppInd(ULogicalRnc) and BSCPSFeatSwitch(UIurgLink)

in the OMCR indicates that the RNC and adjacent BSCs support PS service



handover respectively, the HANDOVER FROM COMMAND process is used (See

“CS Service Handover from 3G System to 2G System” process). Otherwise, the cell

reselection process of PS service handover is used (See “PS Service Reselection in

3G to 2G Handover” process). In the cell reselection of PS service handover

process, the inter-RAT cell reselection time can be decreased by the NACC, which

means that system information of the target GERAN cell is carried in the CELL

CHANGE ORDER FROM UTRAN message sent from the RNC to the UE, assisting

the UE in the inter-RAT cell reselection process. The NaccSuppInd(ULogicalRnc)

parameter indicates that whether the RNC supports the NACC function.

GeranCellInd(UExternalGsmCell) indicates whether a GSM cell is a GERAN cell.

When CS service and PS service exist simultaneity, if the UE supports inter-RAT

DTM handover and the parameters DtmSuppInd(ULogicalRnc) and

BSCDTMFeatSwitch(UIurgLink) in the OMCR indicates that the RNC and adjacent

BSCs support DTM handover, the HANDOVER FROM COMMAND process is used

to hand over concurrent services to the 2G system. Otherwise, PS services are

suspended firstly, and then CS service is handed over to the 2G system and PS

services are handed over to the 2G system in sequence.

Note: When the IE “inter-rat cell info indication” is filled into the measurement control

message, if the value of IE “inter-rat cell info indication” in the inter-RAT measurement

report reported by the UE is different from that filled in the measurement control message,

this measurement report will not be processed when RatCelInfoSwch is “0”, but be

processed when RatCelInfoSwch is “1”.

7.1.2.5 Policy for Setting Inter-RAT Measurement Parameters

Policy for setting Inter-RAT event parameters

There are four inter-RAT measurement events (3A, 3B, 3C, 3D). The EventNum (If

the measurement quantity is EcNo, this parameter is obtained from

URatEcNoEvMeasforG. If the measurement quantity is RSCP, this parameter is

obtained from URatRscpEvMeasforG) parameter controls the number of the events

to be configured. The EventId (If the measurement quantity is EcNo, this parameter

is obtained from URatEcNoEvMeasforG. If the measurement quantity is RSCP, this

parameter is obtained from URatRscpEvMeasforG) parameter controls the specific



events to be configured. The EventId parameter is defined through array, and the

dimensions of array are equal to EventNum, which is 4 at most.

Handover parameter configuration strategy in macro diversity:

Measurement parameters are based on cells. Therefore, in the case of macro

diversity, the measurement parameters configured for the best cell are used as

handover parameters. If the best cell changes, the measurement parameters must

be updated.

For inter-RNC handover, if an SRNC cell exists in the active set, the measurement

parameters of the best cell in the SRNC will be used as handover parameters. If

there is no SRNC cell in the active set, the measurement parameters of the last

SRNC cell in the active set will be used as handover parameters.

Setting of multiple sets of handover parameters

inter-RAT handover parameters can be configured separately according to the

measurement quantity, measurement reporting mode, and service bearer type. In

this way, multiple sets of measurement parameters are required for different

purposes. The classification is as follows:

Measurement quantity of the UTRAN

NonIntraMeasQuan(UUtranCellFDD) (CPICH RSCP or EcNo or both

of them)

Note:

When NonIntraMeasQuan is configured as “EcNo” or “RSCP”, only the 2D/2F

events corresponding to the measurement quality are issued.

When NonIntraMeasQuan is configured to “EcNo and RSCP”, two categories of

2D/2F measurement events about CPICH EcNo and CPICH RSCP are configured

and one of 2D measurement events can trigger compressed mode. After

compressed mode is triggered, inter-RAT events of corresponding measurement

quantity will be issued according to that of 2D event. For example, if the

measurement quantity of triggering 2D event is CPICH Ec/No, only inter-RAT events



of CPICH EcNo will be issued.


Event report or periodically report

Service bearer type (srvCategory (URatMeasSrvSpec))










Not Related to Service Type (used for detect set measurement)

Note:

(1). When concurrent services exist and include CS+PS services, the Multi RAB


(2). When concurrent services exist and include non-CS services, the RT RAB


(3). When the above principles are met simultaneously, the first one prevails.

For ease of parameter modification and optimization, inter-RAT handover parameters

are arranged by indexes. The indexing relations are shown in the figure below.



Figure 7-1 Indexing relations for inter-RAT handover


CellFDD)

URatMeasProfile(URatMeasProfile)

URatMeasSrvSpec(URatMeaSrvSpec)URatMeasNoSrvSpec(URatMeasNoS

rvSpec)

refURatMeasProfile

URatEcNoPrdM

eas(URatEcNoP

rdMeas)

URatRscpEvMe

asforG(URatRsc

pEvMeasforG)

srvCategory

NonIntraMeasQuanNonIntraMeasQuan

InterRatCfgNo(

URatRscpEvMe

asforG)

InterRatCfgNo(

URatEcNoPrdM

eas)

URatEcNoEvMe

asforG(URatEc

NoEvMeasforG)

InterRatCfgNo(

URatEcNoEvMe

asforG)

URatEcNoPrdM

eas(URatRscpP

rdMeas)

InterRatCfgNo(

URatRscpPrdM

eas)

Note: When a new cell is set up, the value of intialHoCelSelScene(URatMeasProfile)


Scene) is determined according to the actual cell scene (indicated by

HoCelSelScene(UUtranCellFDD)), and the available inter-RAT measurement profile

corresponding to intialHoCelSelScene is configured for the cell.

Before inter-RAT handover parameters are obtained, profileId(URatMeasProfile) of

the cell is found based on refURatMeasProfile(UUtranCellFDD), and then, in

URatMeasProfile configuration items, the next level managed object is obtained

according to the current measurement application type: For event-triggered

measurements, “Inter-RAT Measurement Configuration Related to Traffic Category

Object ID (URatMeasSrvSpec)” is selected. For periodical measurement, “Inter-RAT

Measurement Configuration Unrelated to Traffic Category Object ID

(URatMeasNoSrvSpec)” is selected.



In the managed object decided above, “Inter-RAT Measurement Configuration No.

(InterRatCfgNo)” is found based on “Traffic

Category(srvCategory(URatMeasSrvSpec))” and “Measurement

Quantity(NonintraMeasQuan)”. Finally, the corresponding inter-RAT handover

measurement parameters are found. The details are as follows:

(1). For event-triggered measurements:


from the managed object URatEcNoEvMeasforG.


from the managed object URatRscpEvMeasforG.

(2). For periodical measurements:


from the managed object URatEcNoPrdMeas.


from the managed object URatRscpPrdMeas.

The relations between the other parameters to be entered in the inter-RAT

measurement control message and the OMCR parameters are as follows:

Measurement report transmission mode MeasRptTrMod

GSM BSIC acknowledgement indication for

inter-RAT measurement BSICVeriReq

UTRAN quality estimation reporting

indication UtranEstQual

GSM cell RSSI reporting indication GsmCarrRSSIInd

Note: The Measured Quantity for UTRAN quality estimation in Inter-RAT

measurement and Measurement Report Criteria are automatically entered based

on InterRatCfgNote. The values of these parameters are for maintenance

personnel‟s reference.

Switch of inter-RAT handover based on measurement for different services



There are several switches for different services to control whether different

measurement-based RATx handovers can be performed. When such a switch is

open, it is allowed to perform RATx handovers for the corresponding service.

Otherwise, the RNC forbids inter-RAT handovers for the service by not activating

the inter-RAT measurement. The switches for different services are described as

followed:

Service Switch

AMR amrRatHoSw(ULogicalRnc)

R99 RT r99RtRatHoSw(ULogicalRnc)

R99 NRT r99NrtRatHoSw(ULogicalRnc)

HSDPA hsdpaRatHoSw(ULogicalRnc)

HSUPA hsupaRatHoSw(ULogicalRnc)


During the 2G neighboring cells configuration, the neighboring cell list used for

reselection in non-CELL_DCH state and for handover in CELL_DCH state can be

configured separately. During handovers, target cells are selected by neighboring cells

configuration state (GsmStateMode(UGsmRelation)). When the UE is in macro diversity

state, the neighboring cell list is a combination of neighboring cell lists of each cell‟s

active set, so the number of inter-RAT neighboring cells may exceed 32, which is the

maximum number specified by the protocol. If the number of inter-RAT neighboring cells

exceeds 32, some cells must be deleted to ensure that there are only 32 inter-RAT

neighboring cells. With minimal impact on the UEs in the active set, these dropped cells

are those with poorer signal quality or remoter geographical location. Therefore, each

inter-RAT neighboring cell is configured with a priority.

7.1.3.1 Cell Priority Configuration

The MeasPrio(UGsmRelation) parameter defines the priority of an 2G neighboring cell

with three values: 0 (high), 1 (medium), or 2 (low). The value can be determined by

network planning engineers according to the existing network conditions, for example,

the quality and geographic location of the inter-RAT neighboring cell. The value 0 shows

the priority settings of inter-RAT neighboring cells based on geographic locations. The

gray cell in the center of the following figure is the source cell. It has three layers of



inter-RAT neighboring cells, marked respectively in yellow, blue, and red. The inter-RAT

neighboring cells in yellow have the highest priority level, namely, 0. Those in blue have

the secondary highest priority level, namely, 1. Those in red have the lowest priority level,

namely, 2.

Figure 7-2 Priority Settings of Cells

Source Cell

Priority 0

Priority 1

Priority 2


The related standards stipulate that the maximum number of 2G neighboring cells is 32.

When an UE is in macro diversity state, the number of inter-RAT neighboring cells of

multiple cells in the macro diversity may exceed this limit. Therefore, a specific policy is

needed to delete neighboring cells. The policy involves combination, selection, and

deletion of the neighboring cells with the same priority.

Priority combination

If a cell is a common neighboring cell of multiple cells in the active set, it may be

configured with different priority levels in different cells. In this case, the multiple priority

levels of this cell must be combined, using the highest priority level as the priority of this

cell.

Neighboring cell list update and deletion in the case of more than 32 neighboring

cells



If the inter-RAT neighboring cell list of an active list contains more than 32 cells, the cells

are sorted in descending order based on priority. The first 32 cells remain unchanged,

and all other cells are put into the reserved inter-RAT neighboring cell list, which can

buffer at most 8 truncated inter-RAT cells.

Each time when the 1A, 1B, 1C, or 1D event is triggered, the priority levels of the

neighboring cells in the inter-RAT neighboring cell list are updated. If there are less than

32 cells in the inter-RAT neighboring cell list after the 1B event is triggered, the cells with

the highest priority in the reserved inter-RAT neighboring cell list are put into the

inter-RAT neighboring cell list. The number of the cells from the reserved inter-RAT

neighboring cell list equals: min(32 – number of existing cells in the inter-RAT

neighboring cell list).

7.2 Inter-RAT Handover Based on Downlink Coverage

Downlink coverage uses 2D and 2F events as the criterions for evaluating the signal

quality of the current frequency.

For GSM handovers, the RNC transmits the 2D ad 2F event configuration to the UE

when the service is set up. If the UE reports a 2D event, that is, the current carrier is in

poor signal quality, and no inter-frequency neighboring cells exist, or the UE reports a 2E

event after inter-frequency measurement is started (that is, the signal quality of the

measured inter-frequency neighboring cell is also poor), the RNC tries to initiate an

inter-RAT blind handover first if inter-RAT neighboring cells with

GsmShareCover(UGsmRelation)( Covers) exist. If inter-RAT neighboring cells exist but

have no GsmShareCover(Covers) relation, or the blind handover fails, the RNC needs to

configure and start an inter-RAT measurement 3A or 3C event to the UE, and then

performs the corresponding decision process for inter-RAT handover according to the 3A,

or 3C event subsequently reported by the UE.

7.3 Inter-RAT Handover Based on Uplink BLER

The RncUlBlerHoSwch and UlBlerHoSwch(UUtranCellFDD) parameters control the

enabling of uplink BLER based handovers.



This policy is specific to DCHs.

When the values of RncUlBlerHoSwch and UlBlerHoSwch(UUtranCellFDD) are both

“ON”, the RNC periodically measures the uplink BLER. If the measured uplink BLER is

higher than a certain threshold (1.25%), and the real-time measured value (Sirtarget)

reaches the maximum value of the BAM (ULMaxSIR), the RNC triggers the inter-RAT

measurement or handover policy. The process is the same as that for inter-RAT

handover based on downlink coverage.

7.4 Inter-RAT Handover Based on Uplink Transmit

Power

The RncTxPwrHoSwch and UlPwrHoSwch(UUtranCellFDD) parameters control the

enabling of inter-frequency handovers based on uplink transmit power.

Handover Based on Uplink Transmit Power is used only for traffic carried on DCHs.

When the values of RncTxPwrHoSwch and UlPwrHoSwch(UUtranCellFDD) are both

“ON”, the RNC sets up a UE internal measurement while services are initially established.

The UE internal measurement mainly measures the UE transmission power (TxP) by

event report.

Before UE internal measurement parameters are obtained, profileId(UUeIntMeasProfile)

of the cell is found based on refUUeIntMeasProfile(UUtranCellFDD). Then, according to

the current measurement purpose “UE Transmitted Power Event Measurement for

Handover”, the managed object UHoEvtTPUeInt is obtained from UUeIntMeasProfile

configuration items. Finally, “UE Internal Measurement Configuration

Index(UeIntMCfgNo(UHoEvtTPUeInt))” and the following corresponding internal

measurement parameters are obtained from UHoEvtTPUeInt.

Measurement Report Transfer Mode measRptTrMod(UHoEvtTPUeInt)

Filter Coefficient filterCoeff(UHoEvtTPUeInt)

Maximum Event Number of UE Internal Measurement measEvtNum(UHoEvtTPUeInt)

UE Internal Measurement Event Identity meaEvtId(UHoEvtTPUeInt)



Time to Trigger(ms) trigTime(UHoEvtTPUeInt)

When the transmit power of the UE meets the above threshold requirements, the UE

reports the corresponding events. After receiving an Event 6A report (Uplink power of UE

exceeds txPowerThres(UHoEvtTPUeInt)) or an Event 6B report (Uplink power of UE is

less than txPowerThres(UHoEvtTPUeInt)), the RNC uses the same processing strategy

as that of 2D or 2F, respectively. For details, see the Events 2D and 2F processing

strategies in “Inter-RAT Handover Based on Downlink Coverage”.

7.5 Inter-RAT Handover Based on Downlink Transmit

Power

The RncTxPwrHoSwch and DlPwrHoSwch(UUtranCellFDD) parameters control the

enabling of inter-frequency handovers based on downlink transmit power.

This policy is specific to DCHs.

When the values of RncTxPwrHoSwch and DlPwrHoSwch(UUtranCellFDD) are both

“On”, the RNC will check the DTCP in the Node B dedicated measurement report.

Obtaining of the Node B dedicated measurement parameters: According to the current

measurement purpose “Event A Report Parameters for TCP in Handover Control”/”

Event B Report Parameters for TCP in Handover Control”, the following parameters used

for handover control are obtained from the sub-object UNbDedMeas of the object

UNbDedMeasProfile:

Dedicated Measurement Type DedMeasType (UNbDedMeas)

Measurement Change Time /Measurement

Hysteresis Time EvtAbcdefTime (UNbDedMeas)

Measurement Filter Coefficient MeasFilterCoeff (UNbDedMeas)

Report Period RptPrd(UNbDedMeas)

Choice Report Periodicity Scale RptPrdUnit (UNbDedMeas)

Report Characteristics RptType(UNbDedMeas)



Measurement Threshold of Event A/B for Transmitted

Code Power EvtAbTcpThrd(UNbDedMeas)

NbDed Measure Configuration No NbDMCfgNo(UNbDedMeas)

If the DTCP reaches the threshold of Event A, it indicates the downlink power is very high,

the processing strategy is the same as that of Event 2D. If the DTCP reaches the

threshold of Event B, the processing strategy is the same as that of Event 2F. For details,

see “inter-RAT handover based on downlink coverage”.

7.6 Handover Based on Load Control

The RNC selects some users with lower priority levels in the cell and switches them to

the neighboring cells with GsmShareCover (Overlap or Covers) blindly in case of the

following conditions:

When the load (transmitted carrier power (TCP) or received total wideband power

(RTWP)) of a cell is rather high.

If the current neighboring cell does not have any inter-frequency neighboring cell

with ShareCover (Overlap or Covers), but has inter-RAT neighboring cells with

GsmShareCover (Overlap or Covers), the RNC selects some users with lower

priority levels in the cell and switches them to the neighboring cells with

GsmShareCover (Overlap or Covers) blindly.

In this way, the system load can be reduced quickly and the system reliability can be

guaranteed. For details about the inter-system handover based on load, refer to the ZTE

UMTS Load Balance Feature Guide.

7.7 UMTS->GSM Handover Based on Board Power Off

No matter whether the board power is off or board property is changed, services and

users in the corresponding board will be all dropped off, which will influence user

experience. Therefore, the waiting timer is set to control the time of turning off power

when the board power is off.



Whether a board is powered off is indicated by a notification flag (the flag for UE based

on saving energy or property changed, for details see “ZTE UMTS Intelligent Carrier

Power Control Feature Guide”).

When the notification flag is “True”, the timer BoardPwrOffHoTmr(URncFunction) is

started. For CS services, if there are 2G neighboring cells and all the relative inter-RAT

switches are open, Event 3C will be used in inter-RAT measurements to make the

service handovers to 2G network as soon as possible. For the other CS services that do

not meet the conditions of inter-RAT handovers, are released immediately. For PS

services, a DSCR is directly performed. After the timer expires, all the services in the

system will be released.

7.8 Inter-RAT Handover based on GSM Load

After IUR-G is introduced, the UMTS can acquire the load conditions in the GSM when

IurgFeatSwitch(UIurgLink) indicates that adjacent BSCs support the Iur-g signaling

procedure, so inter-RAT handover based on GSM load is taken into consideration to

avoid admission failure in the GSM because of overload in the GSM system. This

function is controlled by the parameter LdBsIntSysHOInd(ULogicalRnc).

7.8.1 Acquirement and Update of GSM Load Condition

3GPP defines three categories of GSM load in IUR-G: Load Value, RT Load, and NRT

Load. Load Value is about total load condition in cell, while RT Load for RT service load

and NRT Load for NRT service load.

GSM overload cell saving and update strategy

Defining the RT overload cell list and GSM overload cell list, the RNC saves and updates

the two lists in time, and sets up the overload valid timer CellLdInfoVldTim

(URncFunction). When the duration of a cell‟s overload information before an update

exceeds CellLdInfoVldTim(URncFunction), the cell will be deleted from the

corresponding overload cell list.

When the reported downlink RT Load in a GSM cell is not less than GsmDlRTLdThrd

(UExternalGsmCell) or the reported uplink RT Load in a GSM cell is not less than



GsmUlRtLdThrd (UExternalGsmCell), it means that the load in the GSM cell is heavy and

RT services cannot be accessed. The cell will be kept in the RT overload cell list. If the

reported uplink/downlink RT Load is smaller than the corresponding threshold in a cell

and the cell exists in the RT overload cell list, the cell will be deleted from the RT

overload cell list.

When the reported downlink load in a GSM cell is not less than GsmDlLdThrd

(UExternalGsmCell) or the reported uplink load in a GSM cell is not less than

GsmUlLdThrd (UExternalGsmCell), it means that any service cannot be accessed, and

the cell will be kept in the GSM overload cell list. If the reported uplink/downlink load is

smaller than the corresponding threshold in a cell and the cell exists in the GSM overload

cell list, the cell will be deleted from the GSM overload cell list.

For RT services, if the RT Load is reported, it is used to decide the load conditions of the

GSM cell. Otherwise, the Load Value is used to decide the conditions. For NRT services,

the Load Value is used to decide the load conditions of the GSM cell.

7.8.2 Inter-RAT Handover based on GSM Load Process

Under the following scenarios, the target cell list for handovers is selected. If a target cell

is included in the overload cell list, it is considered that the GSM cell is overloaded and

the handover to the cell is not triggered. Another cell in the candidate cells list will be

selected instead. If all cells in the candidate cells list do not satisfy the handover

conditions, the corresponding handover is not performed.

Inter-RAT handover based on quality of downlink coverage, uplink BLER, and

uplink/downlink transmit power.

Inter-RAT handover based on load control.

Inter-RAT handover based on load balance.

Note: For RT services, if the GSM reports RT information, the overload-cell list stands for

the RT overload-cell list. Otherwise, if the GSM does not report RT information, the

overload cell list stands for the GSM overload-cell list. For NRT services, the

overload-cell list means the GSM overload-cell list.



7.9 Special UMTS->GSM Handover Strategy based on

the Indoor Neighboring Cell

For a 3G cell within the present network, when the indoor neighboring cells exist, if the

processing strategy for ordinary 2G neighboring cells is still used, call drops may occur

before a handover can be performed. Therefore, for different 2G neighboring cells of the

one 3G cell, different 2D triggering thresholds are configured and different inter-RAT

measurement events are issued. In this way, timely handovers can be performed

immediately in response to the signal changes of indoor cells whenever an indoor cell

that meets the conditions exists.

If the following conditions are met, the special UMTS->GSM handover strategy should be

performed, which means issuing two sets of 3A/3C events simultaneously. Only 3A event

is processed by ordinary 2G neighboring cells, and 3C/3A events are both processed by

indoor 2G neighboring cells.

(1) RatHoTactic is “0: determined by algorithm”.

(2) There is at least one GSM neighboring cell whose IndoorCellInd is “1: indoor

cell”.

(3) The value of “service handover” is not “handover to GSM should be performed”.

7.10 Coupling for Different Handover Causes

As described above, the causes of 2G handovers include the following:

Handover based on load control

Handover based on downlink coverage/quality event

Handover based on uplink transmit power

Handover based on uplink BLER

Handover based on downlink transmit power



Handovers based on load control aim to reduce the system load quickly to ensure

system stability. Therefore, handovers based on load control has the highest priority. The

handover triggered by radio quality causes such as downlink coverage event, uplink

transmit power, uplink BLER, and downlink transmit power aim to ensure the QoS and

user experience. Handovers of this kind have the second highest priority.

The handover of higher priority shields the handover of lower priority, for example, a cell

handed over based on load control cannot admit new services.

7.11 Inter-RAT Handover Process

7.11.1 CS Service Handover from 3G System to 2G System

Figure 7-3 3G to 2G CS Service Handover

RNCNODE BUE

HANDOVER FROM UTRAN COMMAND

HANDOVER COMPLETE

CN

RELOCATION REQUIRED

RELOCATION COMMAND

BSC

HANDOVER REQUEST

HANDOVER DETECT

HANDOVER COMPLETE

IU RELEASE COMMAND

IU RELEASE COMPLETE

HANDOVER REQUEST ACK





Figure 7-4 3G to 2G CS Service Handover Procedure via IUR-G

RNCNODE BUE

5 HANDOVER FROM UTRAN COMMAND

12HANDOVER COMPLETE

CN

2 ENHANCED RELOCATION RESOURCE REQUEST

8 RELOCATION COMMAND

BSC

6 HANDOVER REQUEST

11 HANDOVER DETECT

13 HANDOVER COMPLETE

14 IU RELEASE COMMAND

15 IU RELEASE COMPLETE

7 HANDOVER REQUEST ACK

3 ENHANCED RELOCATION RESOURCE RESPONSE

4 RELOCATION REQUIRED

9 RELOCATION COMMIT

10 HANDOVER ACCESS

1 MEASUREMENT REPORT

When the UTRAN and GSM equipment is provided by ZTE, 3G to 2G CS service

handovers can be processed via IUR-G, which is added with this procedure. The



procedure is the part of the previous CN procedure between the RNC and the BSC to

reserve resources in advance. The procedure is described as follows:

1 Upon receiving the measurement report of the UE, the RNC decides to handover

the UE to a GSM cell.

2 The RNC sends an ENHANCED RELOCATION RESOURCE REQUEST message

to the BSC, requiring resources for the UE.

3 Upon receiving the message, the BSC reserves resources in advance for the UE

and sends an ENHANCED RELOCATION RESOURCE RESPONSE message to

the RNC.

4 Upon receiving the message, the RNC sends a RELOCATION REQUIRED

message to the CN and sends HANDOVER FROM UTRAN COMMAND to the UE,

requiring the UE to perform a hard handover.

5 Described in step 4.

6 Upon receiving the message RELOCATION REQUIRED, the CN sends a

HANDOVER REQUEST message to BSC.

7 After the resources are established, the BSC sends a HANDOVER REQUEST ACK

message to CN.

8 Upon receiving the message HANDOVER REQUEST ACK, the CN sends a

RELOCATION COMMAND message to the RNC.

9 Upon receiving the message RELOCATION COMMAND, the RNC sends a

RELOCATION COMMIT message to the BSC.

10 Upon receiving the message HANDOVER ACCESS from the UE, if the BSC has

already received the message RELOCATION COMMIT from the CN, the BSC will

send a HANDOVER DETECT to the CN. Otherwise, the BSC will not send

HANDOVER DETECT to the CN until receiving the message RELOCATION

COMMIT from the CN.

11 Described in step 4.



12 The UE returns “HANDOVER COMPLETE” to the BSC to inform the BSC that the

handover is finished.

13 After receiving HANDOVER COMPLETE from the UE, the BSC sends a

HANDOVER COMPLETE message to the CN.

14 Upon receiving the message HANDOVER COMPLETE, the CN sends an “IU

RELEASE COMMAND message to the RNC to release all the Iu resources.

15 Upon releasing the lu resources, the RNC returns IU RELEASE COMPLETE to the

CN.

Note: In the process of a 3G->2G CS service handover, the parameter rxlevNecellInd

(URncInfo) is used to control whether to fill the IE “RXLEV-NECELL” in

oldBSS_ToNewBSS of the RELOCATION REQUIRED message. When rxlevNecellInd

(URncInfo) is “1:On”, the IE is filled to allow the GSM to select suitable frequency.

7.11.2 PS Service Reselection in 3G to 2G Handover

If UE doesn‟t support inter-RAT PS service handover or adjacent BSC doesn‟t support

PS service handover, handover of PS domain from the UTRAN to the GSM can be

classified into the following cases:

The UE actively initiates the PS service reselection.

The UE selects a GPRS cell to dwell through the cell reselection process, sets up a

connection with the target cell, and then initiates route area update. This case applies to

an UE in CELL_FACH or URA_PCH state.



Figure 7-5 PS service reselection initiated by an UE in the case of 3G to 2G handover

U E C N

1. C ell R eselectio n

triggered

Serving

R N C

R AN AP R AN AP2. Iu R elease C o mmand

R AN AP R AN AP2. Iu R elease C o mplete

The RNC actively initiates PS service reselection.

The RNC decides to switch the UE to another RAT cell according to handover decision

results. This case applies to an UE in CELL_DCH state. The RNC sends a handover

command CELL CHANGE ORDER FROM UTRAN to the UE. After receiving the

command, the UE sets up a connection with the target cell, and then initiates route area

update.



Figure 7-6 PS service reselection initiated by the RNC in the case of 3G to 2G

handover

1. Cell Change Order from UTRAN

UE

RRC RRC

2. Reselection to the target GPRS cell; radio link establishment in GSM/BSS

GMM GMM 3. Routing Area Update Request

4. SRNS Context

Request RANAP RANAP

RANAP 5. SRNS Context

Response RANAP

6. SRNS Data Forward

Command RANAP RANAP

7. Forwarding of PDUs

RANAP RANAP 8. Iu Release Command

10. Routing Area Update Accept

Node B BTS

BSC CN

(SGSN)

RNC

Serving

GMM

GMM GMM

GMM 11. Routing Area Update Complete

RANAP 9. Iu Release Complete

RANAP


1. Upon detection of a trigger, SRNC initiates the handover to GSM/BSS by sending

the RRC message Cell Change Order from UTRAN to the UE, and starts the timer

TWaitContextReq(URncFunction). Upon reception of the SRNS Context Request

message, SRNC shall stop the timer. If TWaitContextReq expires, SRNC starts the

timer TWaitDataFwd(URncFunction).

2. The UE reselects to the target GPRS cell and establishes the radio connection to

the GSM/BSS.



3. The UE initiates the GPRS Routing Area Update procedure by sending the GMM

message Routing Area Update Request to the SGSN.

4. The SGSN sends the RANAP message SRNS Context Request to the SRNC listing

the PS RABs for which context transfer shall be performed.

5. SRNC responds to the SGNS with the RANAP message SRNS Context Response

containing the context information of all referenced PS RABs whose transfer is

successful and starts the timer TWaitDataFwd(URncFunction). Upon reception of

the SRNS Data Forward Command message, SRNC shall stop the timer. If

TWaitDataFwd expires, SRNC starts the timer TWaitRelCmd(URncFunction).

6. The SGSN asks the SRNC to forward its buffered data back to the SGSN by

sending the RANAP message SRNS Data Forward Command, and starts the timer

Tdatafwd(UiuCnst) and TWaitRelCmd(URncFunction). If Tdatafwd expires, the

SRNC releases the resource used to forward buffered data. Upon reception of the

IU RELEASE COMMAND message, the SRNC shall stop the timer TWaitRelCmd. If

TWaitRelCmd expires, the SRNC releases IU connection. For each PS RAB

indicated by the SRNS Data Forward Command, the SRNC starts duplicating and

tunneling the buffered data back to the SGSN.

7. The SGSN sends the RANAP message Iu Release Command to initiate the release

of the Iu connection with UTRAN.

8. At the expiration of the RNC data forwarding timer (i.e. TDATAfwd), the SRNC

sends the RANP message Iu Release Complete message to the SGSN.

9. The SGSN validates the UE‟s presence in the new RA by sending the GMM

message Routing Area Update Accept to the UE. The message may contain a new

P-TMSI that the network assigns to the UE.

10. The UE acknowledges the assignment of a new P-TMSI by sending the GMM

message Routing Area Update Complete to the UE.



8 UTRAN<->LTE Handover Strategy

8.1 UTRAN<->LTE PS Handover Strategy

RNC adds the “UTRAN<->LTE PS Handover Strategy” to ensure the continuity of PS

service between UTRAN and LTE. If an UE switches from a RATx system to a UTRAN

system, the RATx system policy is used. So, there is only UTRAN->LTE PS handover

strategy described. For now, only support radio quality based inter-RAT (UTRAN->LTE)

handover.

The conditions as follow need to be fulfilled firstly if RNC wants to execute UTRAN->LTE

PS handover strategy:

1. Parameter RncPsHoLteSw (ULogicalRnc) is set to “1: open”.

2. Support of Inter-RAT PS Handover to E-UTRA FDD IE of UE capability indicates

that RNC supports PS service handover from UTARN to LTE.

3. The switch for current service to control whether LTE based on measurement could

be performed is open.

Service Switch

R99 RT r99RtEutraHoSw (ULogicalRnc)

R99 NRT r99NrtEtraHoSw (ULogicalRnc)

HSDPA hsdpaEutraHoSw (ULogicalRnc)

HSUPA hsupaEutraHoSw (ULogicalRnc)

4. The system which RNC allows UE to hand over to is “EUTRAN”, that is judged by

cell level switch IfOrRatHoSwch, ChoStraMulRatHo and the conditions of neighbor

cell exiting (See “5.10 Inter-frequency and Inter-RAT Measurement Choice”).

5. The switch of whether to check the UE E-UTRA Capability before initiating the PS

handover procedure from UMTS to LTE, GresPara52 (bit11) is “Off” or GresPara52

(bit11) is “On” with UE E-UTRA Capability IE acquired.

Note: In the process of UTRAN->LTE handover, EUTRAN cell is identified by eNode

BID or RNCID that is indicated by parameter LteCellIdenFlag (UIupsLink). When SGSN



cannot recognize eNode BID of EUTRAN Cell, set LteCellIdenFlag (UIupsLink) to “1”

using RNCID for EUTRAN cell.

8.1.1 EUTRAN Inter-RAT Measurement

UE must perform layer 3 filter on the measurement result, and then use the filtered value

for event decision and reporting. The principles are the same as description in “7.1

Inter-RAT Measurement”, the difference is introducing the eUtranFilterCoeff for LTE

system measurement.

8.1.1.1 Measurement Event and Parameter Configuration

After supporting UMTS->EUTRAN inter-RAT handover, introduce the specific manage

objects: UInterEcNoEvMeasforE, UInterRscpEvMeasforE, URatEcNoEvMeasforE, and

URatRscpEvMeasforE.

1 UInterEcNoEvMeasforE and UInterRscpEvMeasforE correspond to event 2D/2F for

EUTRAN, See “5.1.1 Introduction to Inter-Frequency Measurement” and “5.1.2.6

Parameter Configuration Strategies” for details of the definition of the events and

policy for parameter configuration.

2 URatEcNoEvMeasforE and URatRscpEvMeasforE correspond to the inter-RAT

measurement events 3A, 3C. See “7.1.1 Overview of Inter-RAT Measurement” and

“7.1.2.5 Policy for Setting Inter-RAT Measurement Parameters” for details of the

definition of the events and policy for parameter configuration. The differences are as

follow:

(1) For the ETRAN, the measurement quantity is RSRP.

(2) The measurement parameters are gained from the manage objects defied for

EUTRAN.



Figure 8-1 Indexing relation for inter-RAT handover


CellFDD)

URatMeasProfile(URatMeasProfile)

URatMeasSrvSpec(URatMeaSrvSpec)URatMeasNoSrvSpec(URatMeasNoS

rvSpec)

refURatMeasProfile

URatEcNoPrdM

eas(URatEcNoP

rdMeas)

URatRscpEvMe

asforE(URatRsc

pEvMeasforE)

srvCategory

NonIntraMeasQuanNonIntraMeasQuan

InterRatCfgNo(

URatRscpEvMe

asforE)

InterRatCfgNo(

URatEcNoPrdM

eas)

URatEcNoEvMe

asforE(URatEc

NoEvMeasforE)

InterRatCfgNo(

URatEcNoEvMe

asforE)

URatEcNoPrdM

eas(URatRscpP

rdMeas)

InterRatCfgNo(

URatRscpPrdM

eas)

The parameters in below table, for event measurement and measurement quantity is

EcNo, gained from the object URatEcNoEvMeasforE, for event measurement and

measurement quantity is RSCP, gained from the object URatRscpEvMeasforE.

Absolute Threshold of the Quality of UTRAN Cell for 3A Thresh

Hysteresis(dB) hysteresis

Absolute Threshold of the Quality of Other RAT for

3A/3B/3C

ThreshSys

Time To Trigger TrigTime

Inter-RAT Measurement Event Number EventNum

Inter-RAT Event Identity EventId

UTRAN Filter Coefficient FilterCoeff



EUTRAN Filter Coefficient eUtranFilterCoeff

Weight of the UTRAN System for 3A W

Inter-RAT Measurement Configuration Index InterRatCfgNo

Note: Inter-RAT period measurement does not discriminate between EUTRAN and GSM.

The other parameter to be entered in the inter-RAT measurement control message:

Maximum bandwidth allowed to measure on the single frequency of EUTRAN-

EutranNMeasBand (for FDD cell, this parameter is obtained from MO

UExternalEUtranCellFDD; for TDD cell, this parameter is obtained from MO

UExternalEUtranCellTDD).

8.1.1.2 Setting up a measurement

The principles for setting up an inter-RAT measurement depend on the value of the

E-UTRAN service handover IE in the RAB assignment request message.

1. When the value of the E-UTRAN service handover IE is “Handover to E-UTRAN

shall not be performed”, it indicates that the service cannot be switched to the

E-UTRAN. For such these services, the RNC does not enable inter-RAT

measurement or trigger the handover to LTE.

2. When the value of the E-UTRAN service handover IE is not “Handover to E-UTRAN

shall not be performed”, it indicates that the service can be switched to the E-UTRAN.

RNC enables inter-RAT measurement in the following scenarios:

a) Inter-frequency measurement is enabled, all non-working carriers trigger

2E events, and EUTRAN neighboring cells exist.

b) The event 2D for EUTRAN is reported.

8.1.1.3 Modifying a measurement

Same as “7.1.2.2 Modifying a measurement”.



8.1.1.4 Deleting a measurement

1. When the E-UTRAN service handover value of the service is “Handover to E-UTRAN

shall not be performed” and the quality of the working carries becomes better, the

compressed mode is closed, and E-UTRAN measurement is terminated.

2. Other deleting scenarios seen in “7.1.2.3 Deleting a measurement”.

8.1.1.5 Processing of Inter-RAT Events

1. See “7.1.2.4 Processing of Inter-RAT Events“ for the policy of “the choice of

inter-RAT measurement event” and “judge the IE inter-rat cell info indication”.

2. Use HANDOVER FROM UTRAN COMMAND process for UTRAN->EUTRAN PS

handover (See “8.1.5 UTRAN->EUTRAN inter-RAT handover process”). When

concurrent services exist, if any one of these services doesn‟t support inter-RAT PS

service handover, RNC will not handover to LTE.

3. When EUTRAN inter-RAT handover fails, the penalty timer HoToEutraPenTimer,

which is specific to UE, is started, RNC will not handle the reported inter-RAT

measurement reports before the timer expires, and issue new inter-RAT

measurement control message after the timer expires.

8.1.1.6 Neighbor Cells Screened

When Measurement Control message for EUTRAN measurement needs to be issued,

RNC will select the suit cells according to the capacity of UE.

8.1.2 EUTRAN Inter-RAT Handover Based on Downlink Coverage

Downlink coverage uses 2D and 2F events as the criterions for evaluating the signal

quality of the current frequency.

For EUTRAN handover, RNC transmits the 2D ad 2F event configuration for EUTRAN to

the UE when the service is set up. If the UE reports a 2D event, that is, the current carrier

is in poor signal quality, and no inter-frequency neighboring cells exist, or the UE reports

a 2E event after inter-frequency measurement is started (that is, the signal quality of the



measured inter-frequency neighboring cell is also poor), the RNC needs to configure and

start inter-RAT measurement 3A or 3C event to the UE if inter-RAT neighboring cells

exist, and then performs the corresponding decision process for inter-RAT handover

according to the 3A, or 3C event subsequently reported by the UE. The choice strategy

of events 3A, 3C is the same as the related policy of GSM inter-RAT handover, controlled

by inter-RAT handover tactic RatHoTactic (UUtranCellFDD).

8.1.3 EUTRAN Inter-RAT Handover Based on BLER and Transmit Power

See “7.3 Inter-RAT Handover Based on Uplink BLER”, “7.4 Inter-RAT Handover Based

on Uplink Transmit Power” and “7.5 Inter-RAT Handover Based on Downlink Transmit

Power”.

8.1.4 Coupling for Different Handover Causes

The causes of LTE handover include the following:

Handover based on downlink coverage/quality event

Handover based on uplink transmit power

Handover based on uplink BLER

Handover based on downlink transmit power

The handovers triggered by radio quality causes such as downlink coverage event,

uplink transmit power, uplink BLER, and downlink transmit power aim to ensure the QoS

and user experience. The handovers of these kinds has the same priority.



8.1.5 EUTRAN Inter-RAT Handover Process

Figure 8-2 UTRAN->EUTRAN PS Handover Process

RNCNODE BUE

HANDOVER FROM UTRAN COMMAND

HANDOVER COMPLETE

CN

RELOCATION REQUIRED

RELOCATION COMMAND

eNB

HANDOVER REQUEST

HANDOVER DETECT

HANDOVER COMPLETE

IU RELEASE COMMAND

IU RELEASE COMPLETE

HANDOVER REQUEST ACK



8.2 SRVCC

Due to the continuity of voice service between the UTRAN and the LTE, the RNC is

needed to transition a voice call from the VoIP/IMS packet domain to the legacy circuit

domain during an inter-RAT handover. This mechanism is named SRVCC (Single Radio

Voice Call Continuity).

ZTE supports SRVCC, which is controlled by RncSrvccSw(ULogicalRnc), from LTE to

UTRAN.

ZTE supports IMS voice and IMS Voice+Data SRVCC. The procedure is described as

follows:



1. RncSrvccSw(ULogicalRnc) is “On”.

2. The UE connects with the EUTRAN and sets up IMS voice traffic.

3. The UE reports a measurement report.

4. The EUTRAN decides an SRVCC handover to the UTRAN due to measurement

reports.

5. The EUTRAN sends a message for the PS-CS handover procedure to the CN.

6. The CN initiates the PS-CS handover to the UTRAN procedure.

1) For IMS Voice+Data combined services with inter-RAT PS handovers,

RncPsHoLteSw (ULogicalRnc) must be “On”. If SIP is required to be handed

over to the RNC according to Relocation Request message, PsSigForImsInd

(ULogicalRnc) must be “Supported”.

7. The CN informs the EUTRAN of the handover result (maybe including the result of

inter-RAT PS handovers).

8. The EURAN sends a Handover from E-UTRAN Command message to the UE after

receiving the handover result.

Figure 8-3 SRVCC from E-UTRAN to UTRAN

UE E-UTRAN MME MSC Server Target UTRAN IMS

UE initiates IMS voice service

Measurement Reports

Handover RequiredPS to CS Req

CS Handover Preparation

IMS Service Continuity Procedure

PS to CS RespHandover Command

Handover From EUTRAN Command

Handover execution

Handle PS to PS HO for non-voice if needed



8.3 CSFB

Due to the continuity of voice service between UTRAN and EUTRAN, the CSFB service

can initial the PS handover from EUTRAN to UTRAN, and the corresponding CS service

can be set up in the UTRAN later.

ZTE supports CSFB, which is controlled by PSL2USWCHBYCS (ULogicalRnc), from

EUTRAN to UTRAN right now.

EUTRAN->UTRAN handover for CSFB

Procedure description: (1)The UE triggers voice traffic for originating call or terminated

call after setting up PS traffic in the EUTRAN. (2) If CS Fallback Indicator is received, PS

handover is supported and the EUTRAN will trigger a PS handover to the UTRAN. (3)

The UTRAN sets up traffic for originating call and terminated call.

Figure 8-4 EUTRAN->UTRAN Handover for CSFB

UE

HANDOVER FROM EUTRAN COMMAND

CN

RELOCATION REQUEST

(CSFB information)

eNB RNC

HANDOVER REQUIRED

RELOCATION REQUEST ACK

HANDOVER COMMAND

Handover execution

UE sets up CS service in UTRAN

UE triggers CS after setup PS(with CS fallback indicator)

… …

EUTRAN->UTRAN redirection for CSFB



Procedure description: (1) The UE triggers voice traffic for originating call or terminated

call in idle mode or after setting up PS traffic (PS handover is not supported) in the

EUTRAN. (2) If CS Fallback Indicator is received, the EUTRAN will trigger a redirection

to the UTRAN. (3) The UTRAN sets up traffics.

8.4 Fast Return to EUTRAN

When the UMTS and EUTRAN are jointly deployed, the UE in the EUTRAN is handed

over to the UTRAN due to CSFB, SRVCC or other reasons. To make these UEs get

better service experience, the UTRAN side will return them to the EUTRAN by way of PS

HO or Redirection after the CS service is released.

The conditions of identifying CSFB UE are described as follows:

1) “CSFB Indication” is carried in the RRC Connection Request message, or

2) Neither “CSFB Indication” nor “Pre-redirection info” is carried in the RRC

Connection Request message, the time difference between RRC Connection

Request message and first RAB Assignment Request message for CS services is

not greater than GresPara7, or

3) “CSFB Information” is carried in “Source RNC to Target RNC Transparent Container”

of the Relocation Request message.

The conditions of identifying SRVCC UE are described as follows:

The UE relocated from the EUTRANincludes CS service, and RncSrvccSw is “On”.

8.4.1 Fast Return in PS Handover Way

CSFB

1. PS Service when CS is released for Multi-RAB Service

After the UE is handed over from EUTRAN to UTRAN due to CSFB, when the CS

service is released for Multi-RAB, if the following conditions are met, EUTRAN‟s

compressed mode is activated, and the inter-RAT measurement is configured. After the

measurement reports are received, the PS handover procedure is performed and the UE



is handed over to EUTRAN.

1) EUTRAN neighboring cells exist.

2) The UE supports PS handover to the EUTRAN.

3) GresPara52 (bit11) is “Off”, or GresPara52 (bit11) is “On” with the UE E-UTRA

Capability IE acquired.

4) fastRetEUtranSwch (URncFunction) is “On”.

5) MulSrvRePsHoLteSw is “Handover judgment Based on Measurement”.

6) EutranPsHoMode is “PS handover”.

SRVCC


After the UE is from EUTRAN to UTRAN due to SRVCC, when the CS service is

released for Multi-RAB, if the following conditions are met, EUTRAN‟s compressed mode

is activated, and the inter-RAT measurement is configured. After measurement reports

are received, the PS handover procedure is performed and the UE is handed over to the

EUTRAN.


2) The UE supports PS handover to EUTRAN.

3) GresPara52 (bit11) is “Off”, or GresPara52 (bit11) is “On” with the UE E-UTRA

Capability IE acquired.


5) CresPara7:bit0~bit1 is “Handover judgment Based on Measurement”.

6) GresPara52:bit10 is “PS handover”.



Note:

1. SimCompUserNum is used to control the number of users with compressed mode

activation for fast return to EUTRAN based on measurement to avoid affecting

system performance. If the current number in compressed mode is not less than

SimCompUserNum, compressed mode will not be activated. Otherwise,

compressed mode will be activated.

2. If compressed mode is activated due to fast return to EUTRAN, the timer

PsHoLteMeasTimer is initialized. When the timer expires, if Event (3C) is not

reported, the RNC will judge whether compressed mode is deactivated or not based

on the current signal quality. (Where the current signal quality includes quality of

working frequency, uplink/downlink transmit power, and uplink BLER. For details,

see “8.1.2 EUTRAN Inter-RAT Handover Based on Downlink Coverage”, “8.1.3

EUTRAN Inter-RAT Handover Based on BLER and Transmit Power”.)

8.4.2 Fast Return in Redirection Way based on Measurement

CSFB


After the UE is from EUTRAN to UTRAN due to CSFB, when CS service is released for

Multi-RAB, if the following conditions are met, EUTRAN‟s compressed mode is activated,

and the inter-RAT measurement is configured. After the measurement reports are

received, the Redirection procedure is performed and downlink central frequency

information of the EUTRAN cell whose quality meets inter-RAT measurement event is

filled in Redirection info of RRC Connection Release, the UE is redirected to EUTRAN.



3) MulSrvRePsHoLteSw is “Handover judgment Based on Measurement”.

4) EutranPsHoMode is “Redirection”, the UE supports the EUTRAN measurement; or

EutranPsHoMode is “PS handover”, the UE does not support PS handovers to

EUTRAN but supports the EUTRAN measurement.



SRVCC


After the UE is from EUTRAN to UTRAN due to SRVCC, when CS service is released for

Multi-RAB, if the following conditions are met, then activate EUTRAN compressed mode,

configure inter-RAT measurement, and after measurement reports are received, perform

the Redirection procedure, fill downlink central frequency information of the EUTRAN cell

whose quality meets inter-RAT measurement event in Redirection info of RRC

Connection Release, the UE is redirected to EUTRAN.

1) EUTRAN neighboring cells exist;

2) fastRetEUtranSwch (URncFunction) is “On”;

3) CresPara7:bit0~bit1 is “Handover judgment Based on Measurement”;

4) GresPara52:bit10 is “Redirection”, the UE supports the EUTRAN measurement; or

GresPara52:bit10 is “PS handover”, the UE does not support PS handover to

EUTRAN but the EUTRAN measurement.

Note:

1. SimCompUserNum is used to control the number of users with compressed mode

activation for fast return to EUTRAN based on measurement to avoid affecting

system performance. If the current number in compressed mode is not less than

SimCompUserNum, compressed mode will not be activated. Otherwise,

compressed mode will be activated.

2. If compressed mode is activated due to fast return to EUTRAN, the timer

PsHoLteMeasTimer is initialized. When the timer expires, if Event (3C) is not

reported, the RNC will judge whether compressed mode is deactivated or not based

on the current signal quality. (Where the current signal quality includes quality of

working frequency, uplink/downlink transmit power, and uplink BLER. For details,



see “8.1.2 EUTRAN Inter-RAT Handover Based on Downlink Coverage”, “8.1.3

EUTRAN Inter-RAT Handover Based on BLER and Transmit Power”.)

8.4.3 Fast Return in Redirection Way without Measurement

CSFB


After the UE is handed over from EUTRAN to UTRAN due to CSFB, when the CS

service is released for Multi-RAB, if the following conditions are met, theEUTRAN cell‟s

downlink central frequency information is filled in Redirection info of RRC Connection

Release, the UE is redirected to EUTRAN.

1) EUTRAN neighboring cells exist;

2) fastRetEUtranSwch (URncFunction) is “On”;

3) MulSrvRePsHoLteSw is “Handover judgment Based on Measurement”, the UE

neither supports PS handovers to EUTRAN nor the EUTRAN measurement. It only

supports EUTRAN (Support of E-UTRA FDD/TDD). If MulSrvRePsHoLteSw is

“Redirection without Measurement”, the UE supports EUTRAN (Support of E-UTRA

FDD/TDD).

2. Only CS Service

After the UE is from EUTRAN to UTRAN due to CSFB, when the CS service is released

for Single-RAB, if the following conditions are met, the EUTRAN cell‟s downlink central

frequency information is filled in Redirection info of RRC Connection Release, the UE is

redirected to EUTRAN.

1) An EUTRAN neighboring cell exists.

2) The UE supports the EUTRAN (Support of E-UTRA FDD/TDD).


4) CelReturnLteSwch is “On”.



SRVCC


After the UE is handed over from EUTRAN to UTRAN due to SRVCC, when the CS

service is released for Multi-RAB, if the following conditions are met, the EUTRAN cell‟s





3) CresPara7:bit0~bit1 is “Handover judgment Based on Measurement”, the UE

neither supports PS handovers to EUTRAN nor the EUTRAN measurement. It only

supports EUTRAN (Support of E-UTRA FDD/TDD). If CresPara7:bit0~bit1 is

“Redirection without Measurement”, the UE supports EUTRAN (Support of E-UTRA

FDD/TDD).

2. Only CS Service

After the UE is handed over from EUTRAN to UTRAN due to SRVCC, when the CS

service is released for Single-RAB, if the following conditions are met, the EUTRAN cell‟s




2) The UE supports EUTRAN (Support of E-UTRA FDD/TDD).


4) CresPara7:bit2 is “On”.

Note:

1. Eight downlink central frequencies can be filled at most, four frequencies for FDD

and four frequencies for TDD.



8.4.4 Fast Return Strategy of IUR

Support Fast Return in Redirection Way via Iur

When the SRNC has no radio links and EUTRAN neighbor cells exist, the SRNC will

save the frequency information of EUTRAN neighbor cells returned by the DRNC, and

the union of the saved and the frequency information of EUTRAN neighbor cells

configured for the SRNC is filled in Redirection info if the redirection conditions are met.

Currently, only the Redirection way without measurement is supported.

Support CSFB Indicator via Iur

When the SRNC sends Relocation Request to the DRNC, if the UE is identified as a

CSFB user, the SRNC needs to fill CSFB in CSFB Information of Source To Target

Transparent Container to enable the target SRNC to identify the CSFB user and apply

the function of Fast Return to EUTRAN after the relocation procedure finished.

8.5 EUTRAN Blacklist Management

In the process of an inter-RAT handover or reselection from UTRAN to EUTRAN, some

EUTRAN cells are not appropriate for the UE to camp on. Those cells, forbidden to be

reselected or measured, are informed to the UE through the way of EUTRAN blacklist, to

avoid handover or reselection failure.

Principle description: when reselection or handover is performing, if EutranNCblstSwch,

the switch of the EUTRAN neighboring blacklist management, is “1: open”, the cells in

the EUTRAN neighboring blacklist management object (UENbrBlkList:

EutranFreqBandInd/ earfcnDl/ NEutranNum/ NeutranCId/StateMode), whose StateMode

is “0” are issued to the UE through SIB19 (for non-dedicated state), whose StateMode is

“1” are issued to the UE through measurement control information (for dedicated state),

and are forbidden to be searched by UE.

The condition that IUR carries the blacklist is not considered.



8.6 Inter-RAT Handover based on EUTRAN Load

As UTRAN can acquire the load conditions in EUTRAN through the Iu interface or RIM

process, an inter-RAT handover based on EUTRAN load is taken into consideration in

order to avoid admission failure in EUTRAN because of overload in the EUTRAN system.

This function is controlled by the parameter LdBsdEutranHOInd.

Currently, the load information of Composite Available Capacity Group through RIM

process is only acquired (See “8.8 RIM” for details of RIM procedure and the load

information acquired).

Principle description: When a quality-based inter-RAT handover is triggered, if

LdBsdEutranHOInd is “support inter-RAT handover based on EUTRAN load”, the

reported EUTRAN cell‟s load information should be judged. Those EUTRAN cells, whose

downlink load (1-Composite Available Capacity Group) is equal to or greater than

EutranDlLdThrd, or uplink load (1-Composite Available Capacity Group) is equal to

or greater than EutranUlLdThrd, will be eliminated from the target cell list. After that,

if the target cell list is not empty, the first cell of that list will be selected as the target

cell in handovers.

8.7 EUTRAN Detection Supported

If the following conditions are met, the UE will detect the EUTRAN cells whose priority is

lower than the current cell, and report the results to NAS to display the coverage

conditions of EUTRAN on the terminal interface.

(1) EutraDetectionInd is “True”.

(2) The UE is in CELL_PCH/URA_PCH/IDLE state.

8.8 RIM

The function of RIM is intended to exchanging information via CN between BSS, RNC,

and eNodeB. RIM information is transferred on Iu interface through Direct Information

Transfer message.



Procedure description: The controlling BSC sends a request to the Serving BSC, asking

for some concerned information and demanding the Serving BSC to respond in the form

of report (where Controlling BSC and Serving BSC can be BSC, RNC or ENodeB). The

report form can be single report or multiple reports.

The signalling flow charts corresponding to the two kinds of report form are described as

follows:

Single Report

Controlling BSC Serving BSC

RAN-INFORMATION-REQUEST/Single Report

RAN-INFORMATION/Single Report

Multiple Report


RAN-INFORMATION-REQUEST/Multiple Report

RAN-INFORMATION/Multiple Report-Initial

Different from the simple procedure in single report form, which only has one time

information exchange between the Controlling BSC and Serving BSC, in multiple report

form, when the information that the Controlling BSC concerns does change or the

Serving BSC cannot provide information any more, the Serving BSC needs to inform the

Controlling BSC through the update process shown below:




RAN-INFORMATION/Multiple Report or /End

RAN-INFORMATION-ACK

Moreover, in multiple report form, if the Controlling BSC does not need the Serving BSC

to provide information any more, it should inform the Serving BSC through the

termination process shown below:


RAN-INFORMATION-REQUEST/Stop

RAN-INFORMATION/Stop

8.8.1 UTRA SI

UTRA SI is one application of RIM, mainly used for ENB gaining the UTRAN cell system

information from the UTRAN network. Then ENB will transfer these SIs to the UE

accompanying the existing message between ENB and the UE to make the UE be

reselected from LTE to UTRAN faster.

Procedure description: UtraSISwitch(URncFunction) indicates that the RNC

supports the UTRA SI function of RIM. If the ENB sends a request message

(RAN-INFORMATION-REQUEST/Multiple Report or

RAN-INFORMATION-REQUEST/Single Report) for cell UTRA SI to the RNC, the

RNC will return the SI message of its cell to EUTRAN in the response message

(RAN INFORMATION/Multiple Report Initial or RAN INFORMATION/Single Report).



8.8.2 SON Transfer

The function of SON Transfer is to exchange load information of the cell among UTRAN,

ENB, and GERAN. The target system will respond the load information of cell to source

system after receiving the RIM request message of SON Transfer Function. Currently,

only the form of single report and single cell in SON Transfer are supported.

The function is currently mainly used in obtaining the load information between UTRAN

and EUTRAN. The process is bidirectional, both of the UTRAN and EUTRAN can trigger

the process, which is explained in detail as below.

RNC acquires load information of EUTRAN cell initiatively

When the timer sonTransReqPeriod (URncFunction) expires, if LdBsdEutranHOInd is

“support inter-RAT handover based on EUTRAN load”, the RNC will send

RAN-INFORMATION-REQUEST/Single Report to the CN through the Direct Information

Transfer message to trigger the SON Transfer process. The maximum number of the

request messages sent by the RNC is sonTransReqNumThrd (URncFunction) in one

second. The load information in the response message will be saved.

ENB initializes the SON Transfer process

When the RAN-INFORMATION-REQUEST/Single Report message sent by the ENB is

analyzed from Direct Information Transfer message received from the CN, if

sonTransRespSwitch (URncFunction) is “On”, the RNC will query load information in

accordance with the requested cell ID, and then structure the

“RAN-INFORMATION/Single Report” message and feed back the message to the CN

through the Direct Information Transfer message. The maximum number of messages

accepted for requiring load information of the RNC cell is sonTransRespNumThrd

(URncFunction) in one second.

9 IMSI-based handover

The parameter BasedImsiHoInd (ULogicalRnc) indicates whether the RNC supports

IMSI-based handover.



The IMSI-based handover can limit the range of cells for allowed for handover according

to IMSI of the UE with the following principle:

While a measurement control message is not delivered before the CommonID message

is received in the signaling stage, the RNC does not know the cells authorized to the user.

Therefore, the RNC delivers a measurement control message regardless of the

authorization status of the cells.

While delivering a measurement control message after receiving the CommonID

message, the RNC queries whether the cells are authorized according to the IMSI

information carried in the CommonID message of the lu interface and also the

authorization information configured on the network side. If the SNAC list of the PLMN

carried in CommonID is empty, all the cells of that PLMN will be considered as

authorized ones. Only the authorized neighbor cells will be included in the neighbor cell

list of the measurement control message.

In the process of RAB assignment of service, a decision of whether the current service

cell is authorized is made according to the IMSI information carried in the CommonID

message and the authorization information configured in the network side.

If none of the cells in the active set is authorized

If the best cells in the active set are like the coverage neighbor cells

(ShareCover (UUtranRelation)) and are also authorized cells,

then the inter-frequency handover is performed along with service

establishment

Otherwise,

If the best cells in the active set are like the coverage GSM neighbor

cells (GsmShareCover (UGsmRelation)) and are authorized cells,

and also the current service is AMR,

then Inter-RAT directional retry is performed

Otherwise,

The RAB assignment failure procedure is performed.



Otherwise,

The service is established normally. If some of the cells in the active set are

unauthorizedcells, delete the unauthorized cells from the active set through the

active set update flow.

9.1 Querying Whether the SRNC Cell Is Authorized

According to IMSI

Figure 9-1 shows the process of querying whether a neighbor cell belonging to the SRNC

is authorized according to the IMSI information carried in the CommonID message of the

lu interface and also the authorization information configured on the network side. The

steps of the query are described as follows:

1. The MCC, MNC and other number information (10 digits at most, in the name of

ExtendInformation below) are resolved according to the IMSI carried in the

CommonID message of the lu interface. The number of digits depends on

imsiMatchedDgtNum(UImsiSnacFilter).

2. The information (MCC, MNC and ExtendInformation) resolved and also the

authorized network information imsiMatchedDgtNum(UImsiSnacFilter) configured in

the network side are used to query whether the IMSI of the UE is authorized or not.

If MCC, MNC and Extend Information of the UE does not have a configuration item

in UImsiSnacFilter, “no neighbor cell authorized” is returned. Otherwise, the MCC

(SMCC), MNC (SMNC) and SNAC that are authorized are obtained.

3. According to the relationships between MCC (SMCC), MNC (SMNC), SNAC and

LAC (USnac) and also the cell information including MCC (UUtranCellFDD), MNC

(UUtranCellFDD), LAC (UUtranCellFDD), whether the cell belongs to the MCC

(USnac), MNC (USnac, and LAC (USnac) that are already authorized is queried. If

there is much authorization information, the cell which has configuration item will be

authorized.



Note: The UImsiSnacFilter parameter can have 1000 configuration items at most and

different configuration items can have the same MNC+MNC.

Example:

1. Configuration of UImsiSnacFilter

MCC 460 460 460

MNC 99 99 99

imsiMatchedDgtNum 5 6 7

ExtendInformation [0] [1] [2]

SMCC 460 460 460

SMNC 99 99 100

SNAC 60 61 62

The IMSI of UE1 is 460991234567890, and the authorized PLMN+SNAC for UE1 are

46099+60, 46099+61, and 460100+62.

The IMSI of UE2 is 460990987654321, and the authorized PLMN+SNAC for UE1 are

460+99+60.

2. Configuration of USnac

MCC 460 460 460 460

MNC 99 99 99 100

SNAC 60 60 61 62

LAC 01 02 02 03

3. If there are three cells: the PLMN+LAC configuration of Cell1 is 46099+01, the

PLMN+LAC configuration of Cell2 is 46099+02, and the PLMN+LAC configuration

of Cell3 is 46099+03. As shown in the above table, the authorized IMSI of

CELL1/CELL2 is from 460990000000000 to 46099999999999, and the authorized

IMSI of Cell3 is from 460991200000000 to 46099129999999.So UE1 can be

authorized by CELL1/CELL2/CELL3, and UE2 can be authorized by CELL1/CELL2.



Figure 9-1 Schematic Diagram of Querying Whether the SRNC Cell Is Authorized

According to IMSI

CommonID:MCC

MNC

ExtendInformation

UImsiSnacFilter:MCC

MNC

ExtendInformation

SNAC

Authorized:MCC

MNC

SNAC

USnac：MCC

MNC

SNAC

LAC

Authorized：MCC

MNC

LAC

UUtranCellFDD：MCC

MNC

LAC

Whether the

neighbor

cell is

authorized

9.2 Querying Whether the DRNC Cell Is Authorized

According to IMSI

Figure 9-2 shows the process of querying whether a neighbor cell belonging the DRNC is

authorized according to the IMSI information carried in the CommonID message of lu

interface and also the authorization information configured in the network side. The steps

of the query are:

1. The MCC, MNC and other number information (10 digits at most, in the name of

ExtendInformation below) are resolved according to the IMSI carried in the

CommonID message of the lu interface. The number of digits depends on

imsiMatchedDgtNum(UImsiSnacFilter).

2. The information (MCC, MNC and ExtendInformation) resolved and also the

authorized network information imsiMatchedDigit(UImsiSnacFilter) configured in the

network side are used to query whether the IMSI of the UE is authorized or not. If

MCC, MNC and Extend Information of the UE does not have a configuration item in

UImsiSnacFilter, “no neighbor cell authorized” is returned. Otherwise, the MCC

(SMCC), MNC (SMNC) and SNAC that are authorized are obtained.



3. According to the granted MCC(SMCC), MNC(SMNC), SNAC and the DRNC

neighbor cell information including: MCC(For GSM cells, this parameter is obtained

from UExternalGsmCell. For UTRAN cells, this parameter is obtained from

UExternalUtranCellFDD), MNC (For GSM cells, this parameter is obtained from

UExternalGsmCell. For UTRAN cells, this parameter is obtained from

UExternalUtranCellFDD), SNAC (For GSM cells, this parameter is obtained from


UExternalUtranCellFDD), whether the DRNC neighbor cell belongs to the

MCC(SMCC), MNC(SMNC)and SNAC that are already authorized is queried. If

there is much authorization information, the cell that has configuration item will be

authorized.

Note: In step 3, how many SNACs are configured for the DRNC neighboring cells are

controlled by SNACNum (For GSM cells, this parameter is obtained from


UExternalUtranCellFDD).

Figure 9-2 Schematic Diagram of Querying Whether the DRNC Cell Is Authorized

According to IMSI

CommonID:MCC

MNC

ExtendInformation

UImsiSnacFilter:MCC

MNC

ExtendInformation

SNAC

Authorized:MCC

MNC

SNAC

UExternalUtranCellFDD、

UExternalGsmCell：MCC

MNC

SNAC

Whether the

neighbor

cell is

authorized

10 HSDPA-related special strategy

For channel changes from non-DCH to DCH in the HSDPA handover process, the target

data rate of DCH is the guaranteed bit rate of GBR traffic or the minimum rate of DRBC

for no GBR traffic(refer to ZTE UMTS DRBC Algorithm Feature Guide for details).



10.1 Overview

The cells are classified in three types according to the support capability of HSDPA

(HspaSptMeth(For serving cells, this parameter is obtained from UUtranCellFDD. For

neighboring cells, this parameter is obtained from UExternalUtranCellFDD)) after

HSDPA is introduced: (1) support HSDPA and DCH; (2) do not support HSUPA or

HSDPA; (3) support HSDPA only. The services are classified in two types: HSDPA

service and NHSDPA service. The HSDPA handover is similar to R99 handover in terms

of measurement and handover decision, except that the decisions of cell capacity during

a handover and the service type are added. For the HSDPA service, the handover is

accepted through HS-DSCH to the cells that support HSDPA and DCH and cells that

support HSDPA only as much as possible. If the HS-DSCH fails, the handover to the

cells that support HSDPA and DCH and cells that do not support HSUPA or HSDPA

through DCH is accepted. For the NHSDPA service, the handover can only be accepted

through DCH to the cells that support HSDPA and DCH and cells that do not support

HSUPA or HSDPA.

After HSDPA is introduced, the inter-RNC handover also depends on the capability of

office direction RNC to support HSDPA (RncFeatSwitchBit1) because neighbor cells

feature varying support capabilities (HspaSptMeth(UExternalUtranCellFDD)). That is,

only if both the target cell and target RNC (office direction RNC) support HSDPA, the

HS- -

handover flow cannot be originated until HS-DSCH falls back to DCH. The channel

transfer is performed along with a handover. Different channel transfer situations are

described in the following based on different handover types.

10.2 Intra-frequency Handover

The intra-frequency handover of HDSPA includes soft add/soft drop/soft replacement of

HS-DSCH associated channel, HS-DSCH service cell change, channel type change due

to different capabilities between source cell and target cell during the handover process.

The strategy of soft add/soft drop/soft replacement of HS-DSCH associated channel is

described in “strategy of intra-frequency handover”. The HS-DSCH service cell change



and channel type change are special handover strategies that make HSDPA different

from the R99 (DCH) handover. The specific principles are:

1 HS-DSCH->DCH

If the HS-DSCH is used before the handover and the link to be deleted for 1B event

triggering/radio link failure happens to be the service cell of HS-DSCH, and also the

cells in the active set do not support acceptance through HS-DSCH, a decision of

soft handover together with HS-DSCH transferring to DCH is made.

If the HS-DSCH is used before the handover and the 1C event is triggered, the cell

to be replaced is the HS-DSCH service cell and also the cells in the new active set

do not support acceptance through HS-DSCH, a decision of soft handover together

with HS-DSCH transferring to DCH is made.

If the HS-DSCH is used before the handover and the 1D event triggers

intra-frequency hard handover and the target cell does not support acceptance

through HS-DSCH, a decision of intra-frequency hard handover together with

HS-DSCH transferring to DCH is made.

2 DCH->HS-DSCH

The current service of the UE includes HSDPA and also the DCH is used before the

handover. If the 1D event triggers intra-frequency hard handover and the target cell

supports acceptance through HS-DSCH, a decision of intra-frequency hard

handover together with DCH transferring to HS-DSCH is made.

The current service of the UE includes HSDPA, the DCH is used before the

handover and also the best cell in the active set supports HSDPA. If the downlink

traffic increases to trigger the 4A event (refer to ZTE UMTS DRBC Algorithm

Feature Guide for details), a decision of handover from DCH to HS-DSCH is made.

3 HS->DSCH->HS-DSCH

If the HS-DSCH is used before the handover and the 1D event triggers

intra-frequency hard handover and the target cell supports acceptance through

HS-DSCH, a decision of intra-frequency hard handover together with HS-DSCH

service cell change is made.



If the HS-DSCH is used before the handover and the link to be deleted for 1B event

triggering/radio link failure happens to be the service cell of HS-DSCH, and also

there are cells in the active set that support acceptance through HS-DSCH, a

decision of soft handover together with HS-DSCH change is made. If the 1C/1D

event triggers a soft handover, the cell to be replaced is the HS-DSCH service cell

and also the cells in the new active set support acceptance through HS-DSCH, a

decision of soft handover together with HS-DSCH change is made.

In the above described processes, the 1D event may trigger a ping-pong handover that

leads to frequent change of service cell. To avoid this, a time threshold (T1d(UHspa)) is

configured and changes of service cell should occur at an interval longer than this

threshold.

10.3 Inter-frequency Handover

The conditions for triggering the inter-frequency handover of HDSPA are described in

“inter-frequency handover strategy”. The HS-DSCH service cell change or channel type

change always happens in the handover process. The principles are as follow:

1 HS-DSCH->DCH

The current service of the UE includes HSDPA and also the HS-DSCH is used

before the handover. If the original decision is to trigger an inter-frequency handover

(measurement-based or blind handover) and also the target cell does not support

acceptance through HS-DSCH, a decision of inter-frequency hard handover

together with HS-DSCH transferring to DCH is made.

2 DCH->HS-DSCH

The current service of the UE includes HSDPA and also the DCH is used before the

handover. If the original decision is to trigger an inter-frequency handover

(measurement-based or blind handover) and also the target cell supports


together with DCH transferring to HS-DSCH is made.

3 HS-DSCH->HS-DSCH



The current service of the UE includes HSDPA and also the HS-DSCH is used




together with HS-DSCH service cell change is made.

4 Handover of HS-DSCH between Iur interfaces

For the hard handover of HS-DSCH between Iur interfaces, the handover strategy is

the same as the handover inside the RNC if the target cell supports HS-DSCH. But if

the target cell does not support HS-DSCH, the HS-DSCH/DCH should fall back to

DCH/DCH first, and then the hard handover between lur interfaces and redirection

flow can be performed.

10.4 Inter-RAT Handover

Two strategies are available for handovers between HSDPA systems:

UTRAN->GSM/GERAN strategy and GSM/GERAN -> UTRAN strategy.

1 UTRAN->GSM/GERAN/LTE

The HSDPA service is included and then the same handover flow as that for

between R99 systems is performed.

2 GSM/GERAN/LTE -> UTRAN

The strategy is similar to that when a service accesses the system for the first time.

If both service and target cell support HS-DSCH/DCH, the service is established

directly on HS-DSCH/DCH, otherwise try DCH/DCH.

11 HSUPA-related special strategy

If in the handover process, the channel type changes from non-DCH to DCH, the

handover is accepted according to the target rate of DCH, that is, the guaranteed bit rate

of the current service while the handover occurs or the minimum rate of DRBC (refer to

ZTE UMTS DRBC Algorithm Feature Guide for details).



11.1 Overview

HSUPA is developed on the basis of HSDPA. An HSUPA network element (UE, RNC or

Node B) that supports HSUPA will also supports HSDPA. That is, if the E-DCH is used in

uplink, HS-DSCH is used in downlink without doubt. Therefore, HSUPA supports five

types of cells (HspaSptMeth (For serving cells, this parameter is obtained from

UUtranCellFDD. For neighboring cells, this parameter is obtained from

UExternalUtranCellFDD)): (1) cells that support HSUPA and HSDPA; (2) cells that

support HSUPA, HSDPA and DCH; (3) cells that support HSDPA and DCH; (4) cells that

support HSDPA only; (5) cells that do not support HSUPA or HSDPA. For the cells that

support HSUPA and HSDPA, the E-DCH is used in uplink and the HS-DSCH is used in

downlink. The DPCH is used as associated channel. For the cells that support HSUPA,

HSDPA and DCH, the E-DCH or DCH is used in uplink and the HS-DSCH or DCH is

used in downlink. The DPCH is used as associated channel or allocated to users who do

not use HSUPA or HSDPA.

The service types supported by HSUPA are HSPA services if they can be carried by

HSUPA or HSDPA (HSUPA and HSDPA are equivalent as far as the services are

concerned). Otherwise, they are NHSPA services. The HSPA services should be

accepted first through E-DCH and HS-DSCH in cells that support HSUPA and HSDPA,

cells that support HSDPA only, cells that support HSUPA, HSDPA and DCH and cells

that support HSDPA and DCH (HspaSptMeth (For serving cells, this parameter is

obtained from UUtranCellFDD. For neighboring cells, this parameter is obtained from

UExternalUtranCellFDD)). If E-DCH and HS-DSCH fail to accept the services, the HSPA

services should be accepted through DCH in cells that support HSUPA, HSDPA and

DCH, cells that support HSDPA and DCH or cells that do not support HSUPA or HSDPA.

The NHSPA services can only be accepted through DCH in cells that support HSUPA,

HSDPA and DCH, cells that support HSDPA and DCH or cells that do not support

HSUPA or HSDPA.

The maximum number of cells allowed in the E-DCH active set in the process of HSUPA

soft handover is 3.

After HSUPA is introduced, the inter-RNC handover also depends on the capability of

office direction RNC to support HSUPA (RncFeatSwitchBit2) because neighbor cells



feature varying support capabilities (HspaSptMeth(UExternalUtranCellFDD)). That is,

only if both the target cell and target RNC (office direction RNC) support HSUPA, the

E-DCH<->E-DCH handover can be performed. Otherwise, the DCH<->DCH handover

flow cannot be originated until the E-DCH falls back to the DCH. The channel transfer is

performed along with a handover. Different channel transfer situations are described as

follows based on different handover types.


The intra-frequency handover of HSUPA includes soft add/soft drop/soft replacement of

E-DCH associated channel, E-DCH service cell change, channel type change due to

different capabilities between source cell and target cell during the handover process.

The strategy of soft add/soft drop/soft replacement of E-DCH associated channel is

described in “strategy of intra-frequency handover”. The E-DCH service cell change and

channel type change are special handover strategies that make HSUPA different from

the R99 (DCH) handover. The specific principles are:

1 HS-DSCH/E-DCH->DCH/DCH

The current service of the UE includes HSPA and also the HS-DSCH/E-DCH is

used before the handover. If the 1A event is triggered and the target cell supports

DCH/DCH instead of HS-DSCH/E-DCH, HS-DSCH/E-DCH is transferred to

DCH/DCH firstly, and then a soft handover is performed.

If the 1C event is triggered, the cell to be replaced is the HS-DSCH/E-DCH service

cell and also the target cell supports DCH/DCH instead of HS-DSCH/E-DCH,

HS-DSCH/E-DCH is transferred to DCH/DCH firstly, and then a soft handover is

performed.

If the 1D event is triggered, the best cell changes from HS-DSCH/E-DCH service

cell to a cell that does not support HS-DSCH/E-DCH, a decision of intra-frequency

hard handover with HS-DSCH/E-DCH transferring to DCH/DCH is made.

2 DCH/DCH->HS-DSCH/E-DCH



The current service of the UE includes HSPA and also the DCH/DCH is used before

the handover. If the 1D event triggers intra-frequency hard handover and the target

cell supports acceptance through HS-DSCH/E-DCH, a decision of intra-frequency

hard handover with DCH/DCH transferring to HS-DSCH/E-DCH is made.

The current service of the UE includes HSPA, the current channel type is DCH/DCH,

and also the best cell in the active set supports HSDPA. If the downlink or uplink

traffic increases to trigger the 4A event (refer to ZTE UMTS DRBC Algorithm

Feature Guide for details), a decision of handover from DCH/DCH to

HS-DSCH/E-DCH is made.

3 HS-DSCH/E-DCH->HS-DSCH/E-DCH

If the 1D event triggers intra-frequency hard handover and the target cell supports

acceptance through HS-DSCH/E-DCH, a decision of intra-frequency hard handover

together with HS-DSCH/E-DCH service cell change is made. Refer to 2.1.2

Intra-frequency Hard Handover for the scenario where the intra-frequency hard

handover is triggered.

If the link to be deleted for 1B event triggering/radio link failure happens to be the

service cell of HS-DSCH/E-DCH, and also there are cells in the active set that

support acceptance through HS-DSCH/E-DCH, a decision of soft handover

together with HS-DSCH/E-DCH service cell change is made. If the 1C/1D event

triggers soft handover, the cell to be replaced is the HS-DSCH/E-DCH service cell

and also the cells in the new active set support acceptance through

HS-DSCH/E-DCH, a decision of soft handover together with HS-DSCH/E-DCH

change is made.

4 HS-DSCH/E-DCH->HS-DSCH/DCH

The current service of the UE includes HSPA and also the HS-DSCH/E-DCH is

used before the handover. If the 1A event is triggered, and the target cell supports

HS-DSCH/DCH instead of HS-DSCH/E-DCH, HS-DSCH/E-DCH is transferred to

HS-DSCH/DCH firstly, and then a soft handover is performed.

If the 1C event is triggered, the cell to be replaced is the HS-DSCH/E-DCH service

cell and also the target cell supports HS-DSCH/DCH instead of HS-DSCH/E-DCH,



HS-DSCH/E-DCH is transferred to HS-DSCH/DCH firstly, and then a soft handover

is performed.

If the 1D event is triggered, the best cell changes from HS-DSCH/E-DCH service

cell to a cell that supports HS-DSCH/DCH instead of HS-DSCH/E-DCH, a decision

of intra-frequency hard handover with HS-DSCH/E-DCH transferring to

HS-DSCH/DCH is made.

5 HS-DSCH/DCH->HS-DSCH/E-DCH

The current service of the UE includes HSPA service and also the HS-DSCH/DCH

is used before the handover. If the 1D event is triggered, the best cell changes from

HS-DSCH/DCH service cell to a cell that supports HS-DSCH/E-DCH, a decision of

intra-frequency hard handover with HS-DSCH/DCH transferring to

HS-DSCH/E-DCH is made.


The conditions for triggering the inter-frequency handover of HSPA are described in

“inter-frequency handover strategy”. The HS-DSCH service cell change or channel type

change always happens in the handover process. The principles are as follow:

1 HS-DSCH/E-DCH->DCH/DCH

The current service of the UE includes HSPA and also the HS-DSCH/E-DCH is used


(measurement-based or blind handover) and also the target cell does not support

acceptance through HS-DSCH/E-DCH or HS-DSCH/DCH, a decision of

inter-frequency hard handover with HS-DSCH/E-DCH transferring to DCH/DCH is

made.

2 DCH/DCH->HS-DSCH/E-DCH

The current service of the UE includes HSPA and also the DCH/DCH is used before

the handover. If the original decision is to trigger an inter-frequency handover


acceptance through HS-DSCH/E-DCH, a decision of inter-frequency hard handover



with DCH/DCH transferring to HS-DSCH/E-DCH is made.

3 HS-DSCH/E-DCH->HS-DSCH/E-DCH





with HS-DSCH/E-DCH service cell change is made.

4 HS-DSCH/E-DCH->HS-DSCH/DCH




acceptance through HS-DSCH/DCH instead of HS-DSCH/E-DCH, a decision of

inter-frequency hard handover with HS-DSCH/E-DCH transferring to

HS-DSCH/DCH is made.

5 HS-DSCH/DCH->HS-DSCH/E-DCH

The current service of the UE includes HSPA and also the HS-DSCH/DCH is used




with HS-DSCH/DCH transferring to HS-DSCH/E-DCH is made.

6 Handover of HS-DSCH between Iur interfaces

For the hard handover of E-DCH between Iur interfaces, the handover strategy is

the same as the handover inside the RNC if the target cell supports E-DCH. But if

the target cell does not support E-DCH, the E-DCH should fall back to DCH first, and

then the hard handover between lur interfaces and redirection flow can be

performed.



11.4 Inter-RAT Handover

1 UTRAN->GSM/GERAN/LTE

The HSPA service is included, and then the same handover flow as that for between

R99 systems is performed.

2 GSM/GERAN/LTE-> UTRAN

Similar to the handover between R99 systems, if the target cell support

HS-DSCH/E-DCH, the service is established directly on HS-DSCH/E-DCH.

12 MBMS-related special strategy

After the MBMS is introduced, the cell type (MbmsSuptInd(UUtranCellFDD)) can be

defined as follows:

Cells that do not support MBMS (Not Support).

Cells that support both MBMS and non-MBMS (Support MBMS and not MBMS).

Cells that support MBMS only (Only Support MBMS).


1 The soft add strategy does not consider whether the soft add cell belongs to the

service area or whether it supports the MBMS in the case of 1A/1C soft add. That is,

the strategy is similar to that for the non-MBMS case.

2 1B/1C or the link is deleted due to radio link failure:

For the MBMS service that has set up p-t-p bearer but the link is deleted, if the best

cell does not belong to MBMS service area, the best cell does not support the

MBMS service, the best cell has set up the p-t-m bearer, or the best cell is not the

convergence carrier of the service, then p-t-p RB is released.



For the MBMS service that has not set up p-t-p bearer but the MBMS service

connection already exists, the best cell belongs to MBMS service area, the best cell

supports the MBMS service, the bearer type strategy needs to set up the p-t-m

bearer and the carrier can set up the bearer of the service, then p-t-p RB is set up.

3 The principle of the type change in the bearer of the MBMS service in the active set

under the macro diversity.

Table 12-1 Table of Principle

Bearer Change Type Cell Type Principles of Change

p-t-p->p-t-m Best cell Delete the p-t-p

Non best cell No change

p-t-m ->p-t-p Best cell

Set up p-t-p: If the channel of the service is DCH,

then set up p-t-p for all cells in the active set. If the

channel of the service is HS-DSCH, then set up

p-t-p in the best cell.

Non best cell No change

To avoid ping-pong switch between p-t-p and p-t-m, a time threshold (T1d(UHspa)) is

configured and any switchover should occur at an interval longer than this threshold.


When the UE reports MBMS MODIFIED REQUEST and the information of MBMS

preferred frequency request is carried,

1 If the target carrier comes with a cell with the same coverage (included: the

expected frequency layer cell includes the current working frequency cell) and the

cell belongs to the service area and supports the MBMS, and also the target cell is

able to allocate the resource of currently established dedicated bearer, then the cell

with the same coverage at the frequency layer can be taken as the target cell to

perform the hard handover.

2 If the target carrier does not come with a cell with the same coverage (included), the

neighbor cell of the current cell in the UE‟s active set includes the neighbor cell



(neighboring or being included) that is at the MBMS preferred frequency layer

corresponding to the MBMS service expected to be received and the neighbor cell

belongs to the service area and supports MBMS, then inter-frequency measurement

2A/2B/2C is started for UE. When the 2A/2B/2C event reported by the UE is

received, the cells that do not support MBMS are screened out and a proper cell is

taken for the hard handover.

No treatment is performed if the UE does not carry the information of MBMS preferred

frequency request in the MBMS MODIFIED REQUEST.

13 Parameters and Configurations

13.1 Intra-Frequency Handover Parameters

13.1.1 Parameter List

No. Field Name Name on the Interface

1. MeasPrio Measurement Priority of Neighboring Cell

2. DetSetHoSwch Detected Set Handover Switch

3. RptRange

[MAX_INTRA_MEAS_EVE

NT] (UIntraEcNoEvMeas)

Reporting Range Constant for Event 1A/1B

4. RptRange

[MAX_INTRA_MEAS_EVE

NT]

(UIntraEcNoEvMeasForD)


5. RptRange

[MAX_INTRA_MEAS_EVE

NT] (UIntraRscpEvMeas)


6. RptRange

[MAX_INTRA_MEAS_EVE

NT]

(UIntraRscpEvMeasForD)


7. W[MAX_INTRA_MEAS_EV

ENT] (UIntraEcNoEvMeas) Weight for Event 1A/1B




ENT]


Weight for Event 1A/1B


ENT] (UIntraRscpEvMeas) Weight for Event 1A/1B


ENT]


Weight for Event 1A/1B

11. Hysteresis[MAX_INTRA_M

EAS_EVENT]

(UIntraEcNoEvMeas)

Hysteresis


EAS_EVENT]


Hysteresis


EAS_EVENT]

(UIntraRscpEvMeas)

Hysteresis


EAS_EVENT]


Hysteresis

15. FilterCoeff(UIntraEcNoEvM

eas) Filter Coefficient

16. FilterCoeff(UIntraEcNoEvM

easForD) Filter Coefficient

17. FilterCoeff(UIntraEcNoPrd

Meas) Filter Coefficient

18. FilterCoeff(UIntraRscpEvM


19. FilterCoeff(UIntraRscpEvM

easForD) Filter Coefficient

20. FilterCoeff(UIntraRscpPrdM


21. TrigTime[MAX_INTRA_ME

AS_EVENT]

(UIntraEcNoEvMeas)

Time to Trigger




AS_EVENT]


Time to Trigger


AS_EVENT]

(UIntraRscpEvMeas)

Time to Trigger


AS_EVENT]


Time to Trigger

25. PrdRptAmount(UIntraEcNo

PrdMeas) Amount of reporting in Period Report Criteria

26. PrdRptAmount(UIntraRscp

PrdMeas) Amount of reporting in Period Report Criteria

27. PrdRptInterval(UIntraEcNo

PrdMeas) Reporting Interval in Period Report Criteria

28. PrdRptInterval(UIntraRscp


29. CellIndividualOffset(UUtran

CellFDD) Cell individual offset

30. CellIndivOffset(UUtranRelat

ion) Cell individual offset

31. RptDeactThr(UIntraEcNoEv

Meas)

Reporting Deactivation Threshold for Event

1A

32. RptDeactThr(UIntraEcNoEv

MeasForD)


1A

33. RptDeactThr(UIntraRscpEv

Meas)


1A

34. RptDeactThr(UIntraRscpEv

MeasForD)


1A

35. RplcActThr

(UIntraEcNoEvMeas)

Replacement Activation Threshold for Event

1C and 1J

36. RplcActThr

(UIntraRscpEvMeas)

Replacement Activation Threshold for Event

1C and 1J

37. profileId(UIntraMeasProfile) Profile Id

38. profileId(UUeIntMeasProfile

) Profile Id



39. ref1UIntraMeasProfile Used Intra-frequency Measurement Profile

40. refUUeIntMeasProfile Used UE Internal Measurement Profile

41. IntraMeasCfgNo(UIntraEcN

oEvMeas)

Intra-frequency Measurement Configuration

Index


oEvMeasForD)


Index


oPrdMeas)


Index

44. IntraMeasCfgNo(UIntraRsc

pEvMeas)


Index


pEvMeasForD)


Index


pPrdMeas)


Index

47. MeaEvtId[MAX_INTRA_ME

AS_EVENT]

(UIntraEcNoEvMeas)

Intra-frequency Event Identity

48. MeaEvtId[MAX_INTRA_ME

AS_EVENT]

(UIntraRscpEvMeas)

Intra-frequency Event Identity

49. srvCategory

Service and Bearer Type Used for

Differentiating Handover Configuration

50. IntraMeasCfgNote Function of Configuration Parameters

51. MeasEvtNum

(UIntraEcNoEvMeas)

Event Number of Intra-frequency

Measurement

52. MeasEvtNum

(UIntraRscpEvMeas)

Event Number of Intra-frequency

Measurement

53. ThreshUsedFreq[MAX_INT

RA_MEAS_EVENT]

(UIntraEcNoEvMeas)

Threshold of the Quality of the Used

Frequency for Event 1E/1F

54. ThreshUsedFreq[MAX_INT

RA_MEAS_EVENT]

(UIntraRscpEvMeas)

Threshold of the Quality of the Used

Frequency for Event 1E/1F

55. StateMode(UUtranRelation)

UE State Indicator Used for UTRAN

Neighboring Cell Configuration



56. IntraMeasQuan

UTRAN Measurement Quantity for

Intra-frequency Measurements

57. EvtRptInterval(UIntraEcNo

EvMeas) Reporting Interval for Event 1A/1B/1C/1J

58. EvtRptInterval(UIntraEcNo

EvMeasForD) Reporting Interval for Event 1A/1B/1C/1J

59. EvtRptInterval(UIntraRscpE

vMeas) Reporting Interval for Event 1A/1B/1C/1J

60. EvtRptInterval(UIntraRscpE

vMeasForD) Reporting Interval for Event 1A/1B/1C/1J

61. EvtRptAmount(UIntraEcNo

EvMeas) Amount of Reporting for Event 1A/1B/1C/1J

62. EvtRptAmount(UIntraEcNo

EvMeasForD) Amount of Reporting for Event 1A/1B/1C/1J

63. EvtRptAmount(UIntraRscp

EvMeas) Amount of Reporting for Event 1A/1B/1C/1J

64. EvtRptAmount(UIntraRscp

EvMeasForD) Amount of Reporting for Event 1A/1B/1C/1J

65. PcpichPwrPre Primary CPICH Power Configuration Tag

66. primaryCpichPower Primary CPICH Power

67. rlRefTimeAjtSw

Switch for RL Reference Time Adjust During

Diversity Mode

68. TimeDelay Transport Time Delay(NodeB)

69. ATimeDelay(UExternalUtra

nCellFDD) Transport Time Delay

70. RncFeatSwitchBit4 NotSupport/Support Hard Handover DSCR

71. NrtMaxUlRateDch

Maximum Bit Rate on UL DCH for NRT PS

RAB in Serving Cell

72. NrtMaxDlRateDch

Maximum Bit Rate on DL DCH for NRT PS

RAB in Serving Cell

73. RtMaxUlRateDch

Maximum Bit Rate on UL DCH for RT PS

RAB in Serving Cell

74. RtMaxDlRateDch

Maximum Bit Rate on DL DCH for RT PS

RAB in Serving Cell

75. RtMaxRateEdch

Maximum Bit Rate on E-DCH for RT PS RAB

in Serving Cell



76. NrtMaxRateEdch

Maximum Bit Rate on E-DCH for NRT PS

RAB in Serving Cell

77. NrtMaxUlRateDchD

Maximum Bit Rate on UL DCH for NRT PS

RAB in External UTRAN Cell

78. NrtMaxDlRateDchD

Maximum Bit Rate on DL DCH for NRT PS


79. RtMaxUlRateDchD

Maximum Bit Rate on UL DCH for RT PS


80. RtMaxDlRateDchD

Maximum Bit Rate on DL DCH for RT PS


81. NrtMaxRateEdchD

Maximum Bit Rate on E-DCH for NRT PS


82. RtMaxRateEdchD

Maximum Bit Rate on E-DCH for RT PS RAB

in External UTRAN Cell

83. Cs64Switch Switch of CS 64kbps Establishment

84. AdjCs64Switch

Switch of CS 64kbps Establishment for

External UTRAN Cell

85. NbrCellMonSupInd

Neighbouring Cell Monitoring Support

Indicator

86. UeIntMCfgNo(URlEvtRttUeI

nt)

UE Internal Measurement Configuration

Index

87.

TResndMeaCtrlRel

The Time Threshold that the RNC May

Resend the MEASUREMENT CONTROL

RELEASE

88. TxRxTDThres[MAX_UE_IN

TER_MEAS_EVENT]

(URlEvtRttUeInt)

UE Rx-Tx Time Difference Threshold

89. AddNRLSHOSwch Adding New Radio Link Judgement Switch

90. IntraHoEcNoThrd

Cpich Ec/No Minimum Threshold for

Intra-Frequency Handover

91. IntraHoRscpThrd

Cpich Rscp Minimum Threshold for

Intra-Frequency Handover

92. HOCELSELSCENE Mobility Configuration Scene

93. TWAITACTSETUPCMP

Waiting time length for ACTIVE SET

UPDATE COMPLETE(100ms)



94. MeasRptTrMod(URlEvtRttU

eInt)

Measurement Report Transfer Mode

95. FilterCoeff(URlEvtRttUeInt) Filter coefficient

96. MeaEvtId(URlEvtRttUeInt) UE Internal Measurement Event Identity

97. TrigTime[MAX_UE_INTER

_MEAS_EVENT]

(URlEvtRttUeInt)

Time to Trigger

98. MeasEvtNum(URlEvtRttUeI

nt)

Maximum Event Number of UE Internal

Measurement

99. RncFeatSwitchBit18 NotSupport/Support PS(0 Kbps /0 Kbps)

100. RncFeatSwitchBit15

NotProcess/Process 1A/1C/1D Event of

DRNC's Cell


NotUse/Use DSCR for PS Service When UE

all RLs Have Moved to DRNC

102.

ParallelSoftHO

Switch of RNC Send RL SETUP and ACTIVE

SET UPDATE parallel when Soft Add

Handover

103. CsIntraEvtSwch

Event 1A/1C/1D of DRNC‟s Cells for CS

Service Strategy Switch


NotProcess/Process Intra-Frequency Events

of DRNC's Cell in RRC Procedure

105. intialHoCelSelScene(UIntra

MeasProfile)

Mobility Configuration Scene

106. EnhanceHoSwch Enhanced Handover Switch

107. CResPara5 Cell Reserved Parameter 5

108. gRESPARA47 Global Reserved Parameter 47

13.1.2 Parameter Configurations

13.1.2.1 Measurement Priority of Neighboring Cell

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN

Cell->Adjacent Relation Configuration->Neighbouring Cell



Parameter configuration

This parameter indicates the measurement priority of the neighbouring cell. The priority

of the neighbouring cell can be set to 0, 1, or 2, of which, 0 represents the highest priority

and 2 represents the lowest priority. The priority of the neighbouring is set by the

configuration personnel according to the signal strength and distance of the neighboring

cell.

The neighbouring cells with the priority ranked the 33rd

or after are placed in the

neighboring cell reservation list. When the number of cells in the neighbouring cell list is

less than 32, the cell(s) with higher priority in the neighbouring cell reservation list are

placed to the neighbouring cell list.

13.1.2.2 Detected Set Handover Switch

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN Cell


The measurement control message that contains the detected set information is sent

only when the DetSetHO switch of the best cell in the current active set is set to 1 and the

current number of intra-frequency neighbouring cells is less than 32.

13.1.2.3 Reporting Range Constant for Event 1A/1B(UIntraEcNoEvMeas)

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Service

Configuration->Measurement Configuration->Intra-frequency Measurement

Profile->Intra-frequency Measurement Configuration Related to Traffic

Category->UEIntra-frequency Event Measurement Configuration for CPICH Ec/No


Event 1A is easier to be triggered when the reporting range constant for event 1A is set to

a larger value; and vice verse.



Event 1B is easier to be triggered when the reporting range constant for event 1B is set

to a smaller value; and vice verse.

13.1.2.4 Reporting Range Constant for Event 1A/1B(UIntraEcNoEvMeasForD)

OMC path



Profile->Intra-frequency Measurement Configuration Unrelated to Traffic

Category->Detected Set Measurement Configuration for CPICH Ec/No






13.1.2.5 Reporting Range Constant for Event 1A/1B(UIntraRscpEvMeas)

OMC path




Category->UEIntra-frequency Event Measurement Configuration for CPICH RSCP








13.1.2.6 Reporting Range Constant for Event 1A/1B(UIntraRscpEvMeasForD)

OMC path




Category->Detected Set Measurement Configuration for CPICH RSCP






13.1.2.7 Weight for Event 1A/1B(UIntraEcNoEvMeas)

OMC path






This parameter is used for the quality judgment of event 1A and 1B. This parameter

indicates the weight of the best cell in the quality judgment and is related to the

measurement quantity and the event type.

See the description of the formula for triggering event 1A/1B in section 4.3 for the effects

of this parameter on the quality judgment.

13.1.2.8 Weight for Event 1A/1B(UIntraEcNoEvMeasForD)

OMC path













13.1.2.9 Weight for Event 1A/1B(UIntraRscpEvMeas)

OMC path











13.1.2.10 Weight for Event 1A/1B(UIntraRscpEvMeasForD)

OMC path













13.1.2.11 Hysteresis(UIntraEcNoEvMeas)

OMC path






This parameter indicates the hysteresis when judging whether to trigger the event. This

parameter avoids the change of the trigger status due to very small change. This

parameter is related to the measurement quantity and the event type.

If a small hysteresis is configured, the corresponding event will be reported in a higher

probability; and vice versa.

13.1.2.12 Hysteresis(UIntraEcNoEvMeasForD)

OMC path













13.1.2.13 Hysteresis(UIntraRscpEvMeas)

OMC path











13.1.2.14 Hysteresis(UIntraRscpEvMeasForD)

OMC path













13.1.2.15 Filter Coefficient(UIntraEcNoEvMeas)

OMC path






This parameter indicates the filtering factor that the UE performs the L3 filtering on the

measurement results of the intra-frequency measurement. The smaller the value of the

filtering factor is, the larger effect the current measurement result will have on the

measurement result reported to RNC (periodical report) or the judgment (event report).

13.1.2.16 Filter Coefficient(UIntraEcNoEvMeasForD)

OMC path












13.1.2.17 Filter Coefficient(UIntraEcNoPrdMeas)

OMC path




Category->UEIntra-frequency Period Measurement Configuration for CPICH Ec/No






13.1.2.18 Filter Coefficient(UIntraRscpEvMeas)

OMC path










13.1.2.19 Filter Coefficient(UIntraRscpEvMeasForD)

OMC path












13.1.2.20 Filter Coefficient(UIntraRscpPrdMeas)

OMC path




Category->UEIntra-frequency Period Measurement Configuration for CPICH RSCP






13.1.2.21 Time to Trigger(UIntraEcNoEvMeas)

OMC path








This parameter indicates the time difference between the time that the event generation

is detected and the time that the event is reported. The event is triggered and the

measurement report is reported only when the event generation is detected and still

meets the requirements of event triggering after Time to trigger.

The larger the value is, the stricter the judgment is for the event to be triggered. The

parameter should be configured according to the actual requirements.

13.1.2.22 Time to Trigger(UIntraEcNoEvMeasForD)

OMC path












13.1.2.23 Time to Trigger(UIntraRscpEvMeas)

OMC path














13.1.2.24 Time to Trigger(UIntraRscpEvMeasForD)

OMC path












13.1.2.25 Amount of Reporting in Period Report Criteria(UIntraEcNoEvMeas)

OMC path








This parameter indicates the times of the periodical reports to be reported. In the case of

the UE side, the value is used for the determination of whether to report the

measurement report in reporting the periodical report. If the UE detects that the times of

event reporting exceeds the value of Amount of reporting, the UE stops reporting the

measurement results.

13.1.2.26 Amount of Reporting in Period Report Criteria(UIntraRscpEvMeas)

OMC path











13.1.2.27 Reporting Interval in Period Report Criteria(UIntraEcNoEvMeas)

OMC path






This parameter indicates the interval of periodical reporting specified in the periodical



reporting criteria. In the case of the periodical reporting, the UE reports the measurement

reports in the period indicated by the parameter.

13.1.2.28 Reporting Interval in Period Report Criteria(UIntraRscpEvMeas)

OMC path







reporting criteria. In the case of the periodical reporting, the UE reports the measurement

reports in the period indicated by the parameter.

13.1.2.29 Cell individual offset(UUtranCellFDD)

OMC path



This parameter defines the individual offset of cells in the active set relative to other cells.

When the value is positive, a positive value is added to the measurement result. If the

value is negative, a negative value is added to the measurement result. Refer to the

description of the formula for triggering event 1B/1C/1d in section 4.3 for the effect of this

parameter on the measurement report.

Through the configuration of the individual offset of a single cell, the trigger difficulty of

the cell can be adjusted to meet the practical requirements of network planning without

the need to modify the global handover parameters.



13.1.2.30 Cell individual offset(UUtranRelation)

OMC path




This parameter defines the individual offset of cells outside the active set relative to other

cells. When the value is positive, a positive value is added to the measurement result. If

the value is negative, a negative value is added to the measurement result. Refer to the

description of the formula for triggering event 1A/1C/1d in section 4.3 for the effect of this

parameter on the measurement report.


the cell can be adjusted to meet the practical requirements of network planning without

the need to modify the global handover parameters.

13.1.2.31 Reporting Deactivation Threshold for Event 1A(UIntraEcNoEvMeas)

OMC path






This parameter indicates the maximum number of the cells allowed in the active set.

When the UE detects that one cell in the monitoring set satisfies the trigger threshold of

event 1A, it determines whether the number of the cells in the current active set greater

than the value indicated by this parameter at first. If yes, the event 1A is not triggered.

13.1.2.32 Reporting Deactivation Threshold for Event 1A(UIntraEcNoEvMeasForD)

OMC path












13.1.2.33 Reporting Deactivation Threshold for Event 1A(UIntraRscpEvMeas)

OMC path










13.1.2.34 Reporting Deactivation Threshold for Event 1A(UIntraRscpEvMeasForD)

OMC path












13.1.2.35 Replacement Activation Threshold for Event 1C and

1J(UIntraEcNoEvMeas)

OMC path






This parameter indicates the minimum number of the cell allowed in the DCH active set

when triggering event 1C or in the E-DCH active set when triggering event 1j. When the

UE detects that the measurement result of a cell satisfies the trigger threshold of event

1c/1j, it first judges whether the number of cells in the current active set is smaller than

the value indicated by this parameter. If yes, event 1C/1j is not triggered.

13.1.2.36 Replacement Activation Threshold for Event 1C and

1J(UIntraRscpEvMeas)

OMC path








This parameter indicates the minimum number of the cell allowed in the DCH active set

when triggering event 1C or in the E-DCH active set when triggering event 1j. When the

UE detects that the measurement result of a cell satisfies the trigger threshold of event

1c/1j, it first judges whether the number of cells in the current active set is smaller than

the value indicated by this parameter. If yes, event 1C/1j is not triggered.

13.1.2.37 Profile Id(UIntraMeasProfile)

OMC path


Configuration->Measurement Configuration->Intra-frequency Measurement Profile


This parameter indicates the intra-frequency measurement profile identity.

13.1.2.38 Profile Id(UUeIntMeasProfile)

OMC path


Configuration->Measurement Configuration-> UE Internal Measurement Profile


This parameter indicates the UE internal measurement profile identity.

13.1.2.39 Used Intra-frequency Measurement Profile

OMC path



This parameter indicates the used intra-frequency measurement profile.



13.1.2.40 Used UE Internal Measurement Profile

OMC path



This parameter indicates the used UE internal measurement profile.

13.1.2.41 Intra-frequency Measurement Configuration Index(UIntraEcNoEvMeas)

OMC path






Each intra-frequency measurement configuration with different measurement purpose

and measurement quantity is assigned with a unique intra-frequency measurement

configuration index. This parameter indicates the index of the intra-frequency

measurement configuration. This configuration index is cited in the table Intra-frequency

measurement configuration relationship of the service type-related UE.

That is, the parameter Intra-frequency Measurement Profile Identity(namely

profileId(UIntraMeasProfile)) is cited in the advanced parameter of the serving cell and

different Intra-frequency Measurement Configuration Indexes (namely IntraMeasCfgNo)

can be selected aiming at the specific service type, measurement purpose, and

measurement quantity. Hence, this parameter can be used to meet the various

requirements of network planning.

13.1.2.42 Intra-frequency Measurement Configuration

Index(UIntraEcNoEvMeasForD)

OMC path



















13.1.2.43 Intra-frequency Measurement Configuration Index(UIntraEcNoPrdMeas)

OMC path



















13.1.2.44 Intra-frequency Measurement Configuration Index(UIntraRscpEvMeas)

OMC path

















13.1.2.45 Intra-frequency Measurement Configuration

Index(UIntraRscpEvMeasForD)

OMC path



















13.1.2.46 Intra-frequency Measurement Configuration Index(UIntraRscpPrdMeas)

OMC path



















13.1.2.47 Intra-frequency Event Identity(UIntraEcNoEvMeas)

OMC path






This parameter indicates the identity of the event triggered by the intra-frequency

measurement (1A~1D).

13.1.2.48 Intra-frequency Event Identity(UIntraRscpEvMeas)

OMC path






This parameter indicates the identity of the event triggered by the intra-frequency

measurement (1A~1D).



13.1.2.49 Service and Bearer Type Used for Differentiating Handover Configuration

OMC path



Profile->Intra-frequency Measurement Configuration Related to Traffic Category


All the services are classified into eight categories according to the real-time attribute of

services, channel type, and service quantity. This parameter indicates the service and

bearer type. The handover parameters can be configured flexibly for different scenarios

and the parameters may have different handover triggering thresholds and hysteresis.

The value 0xff (Not Related to Service Type) is exclusive used in the measurement of

the detected set.

13.1.2.50 Function of Configuration Parameters

OMC path




This parameter indicates the purpose and functions of the set of intra-frequency

measurement configuration parameters.

13.1.2.51 Event Number of Intra-frequency Measurement(UIntraEcNoEvMeas)

OMC path








This parameter indicates the number of events that should be configured for the set of

the intra-frequency measurement parameters for a certain purpose. The value is related

to the purpose of the measurement and the judgment method and the algorithm of the

soft handover.

13.1.2.52 Event Number of Intra-frequency Measurement(UIntraRscpEvMeas)

OMC path






This parameter indicates the number of events that should be configured for the set of

the intra-frequency measurement parameters for a certain purpose. The value is related

to the purpose of the measurement and the judgment method and the algorithm of the

soft handover.

13.1.2.53 Threshold of the Quality of the Used Frequency for Event

1E/1F(UIntraEcNoEvMeas)

OMC path






This parameter indicates the absolute threshold used for judging event 1e/1f by using

carrier frequency.



13.1.2.54 Threshold of the Quality of the Used Frequency for Event

1E/1F(UIntraRscpEvMeas)

OMC path






This parameter indicates the absolute threshold used for judging event 1e/1f by using

carrier frequency.

13.1.2.55 UE State Indicator Used for UTRAN Neighboring Cell Configuration

OMC path




This parameter indicates the UE status used for the neighboring cell. When the

neighbouring cell is configured by the status, the neighbouring cell list used for

reselection in non-dedicated mode and the neighbouring cell list used for handover in

dedicated mode are differentiated as follows:

When SIB11/SIB12/SIB11bis is to be sent, the UE selects the cell whose state is “only

cell selection/reselection” or “cell selection/reselection and handover” from the

neighboring cells list and fills in SIB11/SIB12/SIB11bis;

When the measurement control message is to be sent, the UE selects the cell whose

state is “only cell handover” from the neighboring cells list.



13.1.2.56 UTRAN Measurement Quantity for Intra-frequency Measurements

OMC path



This parameter indicates the measurement quantity (Ec/No or RSCP) for the

intra-frequency measurement of the cell. The measurement quantity Ec/No is

recommended.

13.1.2.57 Reporting Interval for Event 1A/1B/1C/1J(UIntraEcNoEvMeas)

OMC path






This parameter indicates the reporting interval for event 1A/1B/1C/1J. Once Event 1A/1C

meets the reporting range of quality standards, the UE will report Event 1A/1C

periodically (EvtRptInterval) until this event does not meet reporting conditions or the

reporting times reach the maximum allowed times (EvtRptAmount).

13.1.2.58 Reporting Interval for Event 1A/1B/1C/1J(UIntraEcNoEvMeasForD)

OMC path












13.1.2.59 Reporting Interval for Event 1A/1B/1C/1J(UIntraRscpEvMeas)

OMC path










13.1.2.60 Reporting Interval for Event 1A/1B/1C/1J(UIntraRscpEvMeasForD)

OMC path












13.1.2.61 Amount of Reporting for Event 1A/1B/1C/1J(UIntraEcNoEvMeas)

OMC path






This parameter indicates the reporting amount for event 1A/1B/1C/1J. Once Event 1A/1C




13.1.2.62 Amount of Reporting for Event 1A/1B/1C/1J(UIntraEcNoEvMeasForD)

OMC path










13.1.2.63 Amount of Reporting for Event 1A/1B/1C/1J(UIntraRscpEvMeas)

OMC path












13.1.2.64 Amount of Reporting for Event 1A/1B/1C/1J(UIntraRscpEvMeasForD)

OMC path










13.1.2.65 Primary CPICH Power Configuration Tag

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->External Resource

Configuration->External RNC Function->External UTRAN Cell


This parameter indicates whether PCPICH transmission power is configured.

PCPICH transmission power is valid when this parameter is set “True”. Otherwise,



PCPICH transmission power is invalid.

13.1.2.66 Primary CPICH Power

OMCR Interface




This parameter indicates cell‟s PCPICH transmission power, is an absolute value.

13.1.2.67 Switch for RL Reference Time Adjust During Diversity Mode

OMCR Interface

GUI: Managed Element ->UMTS Logical Function Configuration->PLMN Relating

Configuration->Logic RNC Configuration


When the switch is closed, RNC will not send measurement control of 6F/6G to UE;

when it is open, RNC may send measurement control of 6F/6G.

13.1.2.68 Transport Time Delay(NodeB)

OMCR Interface

GUI: Managed Element->UMTS Logical Function Configuration->Link Configuration->Iub

Link


This parameter indicates the Iub transport time delay, it could be 20ms/100ms/250ms.



13.1.2.69 Transport Time Delay(UExternalUtranCellFDD)

OMCR Interface




This parameter indicates the Iub transport time delay of external UTRAN cell. It could be

20ms/100ms/250ms.

13.1.2.70 NotSupport/Support Hard Handover DSCR

OMCR Interface

GUI: Managed Element->UMTS Logical Function Configuration->Link Configuration->Iur

Link


This parameter indicates whether to use DSCR in inter-RNC handover of HSPA service.

RncFeatSwitchBit4=0: not use; RncFeatSwitchBit4=1: use.

13.1.2.71 Maximum Bit Rate on UL DCH for NRT PS RAB in Serving Cell

OMCR Interface



This parameter indicates the maximum bit rate on UL DCH allowed in serving cell for an

NRT PS domain RAB.

13.1.2.72 Maximum Bit Rate on DL DCH for NRT PS RAB in Serving Cell

OMCR Interface





This parameter indicates the maximum bit rate on DL DCH allowed in serving cell for an

NRT PS domain RAB.

13.1.2.73 Maximum Bit Rate on UL DCH for RT PS RAB in Serving Cell

OMCR Interface


Cell->Extended Info of UTRAN Cell


This parameter indicates the maximum bit rate on UL DCH allowed in serving cell for an

RT PS domain RAB.

13.1.2.74 Maximum Bit Rate on DL DCH for RT PS RAB in Serving Cell

OMCR Interface




This parameter indicates the maximum bit rate on DL DCH allowed in serving cell for an

RT PS domain RAB.

13.1.2.75 Maximum Bit Rate on E-DCH for RT PS RAB in Serving Cell

OMCR Interface






This parameter indicates the maximum bit rate on E-DCH allowed in serving cell for an

RT PS domain RAB.

13.1.2.76 Maximum Bit Rate on E-DCH for NRT PS RAB in Serving Cell

OMCR Interface




This parameter indicates the maximum bit rate on E-DCH allowed in serving cell for an

RT PS domain RAB.

13.1.2.77 Maximum Bit Rate on UL DCH for NRT PS RAB in External UTRAN Cell

OMCR Interface




This parameter indicates the maximum bit rate on UL DCH allowed in the DRNC cell for

an NRT PS domain RAB.

13.1.2.78 Maximum Bit Rate on DL DCH for NRT PS RAB in External UTRAN Cell

OMCR Interface






This parameter indicates the maximum bit rate on DL DCH allowed in the DRNC cell for

an NRT PS domain RAB.

13.1.2.79 Maximum Bit Rate on UL DCH for RT PS RAB in External UTRAN Cell

OMCR Interface




This parameter indicates the maximum bit rate on UL DCH allowed in the DRNC cell for

an RT PS domain RAB.

13.1.2.80 Maximum Bit Rate on DL DCH for RT PS RAB in External UTRAN Cell

OMCR Interface




This parameter indicates the maximum bit rate on DL DCH allowed in the DRNC cell for

an RT PS domain RAB.

13.1.2.81 Maximum Bit Rate on E-DCH for NRT PS RAB in External UTRAN Cell

OMCR Interface




This parameter indicates the maximum bit rate on UL E-DCH allowed in the DRNC cell

for an NRT PS domain RAB.



13.1.2.82 Maximum Bit Rate on E-DCH for RT PS RAB in External UTRAN Cell

OMCR Interface




This parameter indicates the maximum bit rate on UL E-DCH allowed in the DRNC cell

for an RT PS domain RAB.

13.1.2.83 Switch of CS 64kbps Establishment

OMCR Interface



This parameter indicates whether establishing traffic CS 64kbps in serving cell is allowed

or not.

13.1.2.84 Switch of CS 64kbps Establishment for External UTRAN Cell

OMCR Interface




This parameter indicates whether establishing traffic CS 64kbps in external UTRAN cell

is allowed or not.

13.1.2.85 Neighbouring Cell Monitoring Support Indicator

OMC path






This parameter indicates whether RNC supports neighbouring cell monitoring.

0 means not supported, 1 means supported,

13.1.2.86 UE Internal Measurement Configuration Index(URlEvtRttUeInt)

OMC path


Configuration->Measurement Configuration->UE Internal Measurement Profile->UE

Rx-Tx Time Difference Event Measurement Configuration for RL Timing Adjustment->

UE Internal Measurement Configuration Index


This parameter indicates the UE internal measurement configuration index, which is

used to index different parameter configuration sets for the UE internal measurement,

because there are several different sets of measurement values for the same set of

parameters according to specific measurement purpose, measurement quantity, etc.

13.1.2.87 The Time Threshold that the RNC May Resend the MEASUREMENT

CONTROL RELEASE

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration


This parameter indicates the time threshold that the RNC may resend the

MEASUREMENT CONTROL RELEASE.

When RNC send MEASUREMENT CONGROL RELEASE message for a measurement

ID, the time stamp will be recorded. If RNC receive the measurement report for the ID, it

will be compared between current time and recorded time. If difference between current



time and recorded time exceed the threshold configured, the MEASUREMENT

CONTROL RELEASE will be resent, otherwise ignore this measurement report.

13.1.2.88 UE Rx-Tx Time Difference Threshold(URlEvtRttUeInt)

OMC path




the UE Rx-Tx Time Difference Threshold


This parameter indicates the UE Rx-Tx time difference reporting threshold in chips in

event 6f/6g.

13.1.2.89 Adding New Radio Link Judgement Switch

OMC path




This parameter indicates whether RNC handle the adding new radio link in soft handover,

when the signal quality of new radio link is lower than IntraHoEcNoThrd or

IntraHoRscpThrd.

13.1.2.90 Cpich Ec/No Minimum Threshold for Intra-Frequency Handover

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Cpich Ec/No Minimum

Threshold for Intra-Frequency Handover




The parameter indicates the Cpich EcNo minimum threshold for intra frequency

handover. If reported Cpich EcNo is less than this threshold, intra frequency handover

will not be triggered.

13.1.2.91 Cpich Rscp Minimum Threshold for Intra-Frequency Handover

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Cpich Rscp Minimum

Threshold for Intra-Frequency Handover


The parameter indicates the Cpich RSCP minimum threshold for intra frequency

handover. If reported Cpich RSCP is less than this threshold, intra frequency handover

will not be triggered.

13.1.2.92 Mobility Configuration Scene

OMC path



The parameter indicates handover and cell reselection scenarios.

13.1.2.93 Waiting time length for ACTIVE SET UPDATE COMPLETE

OMC path



The parameter indicates time of Waiting for CELL UPDATE After RB

Setup/Reconfiguration(not for hard-handover)/Release Response Timer Expiration Start:

When the RNC sends RL RADIO LINK ACTIVATION COMMAND to the Node B or

DRNC.



Stop: When the RNC receives the CELL UDPATE from UE. At expiry: The RNC releases

all RRC connection of UE.

13.1.2.94 Measurement Report Transfer Mode(URlEvtRttUeInt)

OMC path




Measurement Report Transfer Mode


This parameter indicates the RLC mode of the UE internal measurement report.

13.1.2.95 Filter coefficient(URlEvtRttUeInt)

OMC path




Filter coefficient



measurement results of the internal measurement.

13.1.2.96 UE Internal Measurement Event Identity(URlEvtRttUeInt)

OMC path




UE Internal Measurement Event Identity




This parameter indicates the UE internal measurement event identity

13.1.2.97 Time to Trigger(URlEvtRttUeInt)

OMC path




Time to Trigger


This parameter indicates the period of time during which the event condition has to be

satisfied before sending a measurement report.

13.1.2.98 Maximum Event Number of UE Internal Measurement(URlEvtRttUeInt)

OMC path




Maximum Event Number of UE Internal Measurement


This parameter indicates the maximum event number of UE internal measurements.

13.1.2.99 NotSupport/Support PS(0 Kbps /0 Kbps)

OMC path


Link




This parameter indicates whether adjacent RNC supports PS0/0 service or not.

RncFeatSwitchBit18=0: not support; RncFeatSwitchBit18=1: support.

13.1.2.100 NotProcess/Process 1A/1C/1D Event of DRNC's Cell

OMC path


Link


This parameter indicates whether to process 1A/1C/1D event of DRNC‟s cell or not when

CS and PS are concurrent via IUR.

RncFeatSwitchBit15=0: not process; RncFeatSwitchBit15=1: process.

13.1.2.101 NotUse/Use DSCR for PS Service When UE all RLs Have Moved to DRNC

OMC path


Link


This parameter indicates whether to use DSCR for PS service or not when all RLs have

moved to DRNC.

13.1.2.102 Switch of RNC Send RL SETUP and ACTIVE SET UPDATE parallel when

Soft Add Handover

OMC path





This parameter indicates whether to process the procedures of RL ADD in Iub interface

and ACTIVE SET UPDATA in Uu interface parallelly when adding radio link in softer

handover.

13.1.2.103 Event 1A/1C/1D of DRNC’s Cells for CS Service Strategy Switch

OMC path




This parameter indicates whether event 1A/1C/1D of DRNC‟s cells is processed for CS

or not.

13.1.2.104 NotProcess/Process Intra-Frequency Events of DRNC's Cell in RRC

Procedure

OMC path


Link


This parameter indicates whether to process intra-frequency events of DRNC‟s cells in

RRC procedure or not.

13.1.2.105 Mobility Configuration Scene(UIntraMeasProfile)

OMC path






The parameter indicates handover and cell reselection scenarios. For each scenario, the

corresponding parameters can be set as different values.

13.1.2.106 Enhanced Handover Switch

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Enhanced Handover

Switch


The parameter indicates license which to control several enhanced handover features as

follows:

1 When RNC is waiting reconfiguration complete message from UE, if RNC receives the

ACK of AM RLC, then RNC consider the UU procedure completed.

2 When the signal quality of current used frequency is bad, whether intra-frequency

handover will be performed.

3 When the signal quality of current used frequency is bad, whether HSPA serving cell

change will be performed.

13.1.2.107 Cell Reserved Parameter 5

OMC path




The parameter is the switch of indicating whether to judge the signal quality of target cell

when 1D event is reported.0: Off, 1: On.



13.1.2.108 Global Reserved Parameter 47

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Global Reserved

Parameter 47


The bit14 of this parameter indicates the synchronous mode in intra-frequency hard

handover.

bit14=0, Timing re-initialised; bit14=1, Timing-maintained.

13.2 Inter-Frequency Handover Parameters



1. MeasPrio Measurement Priority of Neighboring Cell

2. ULMaxSIR Maximum Uplink SIR Target

3. UlBlerHoSwch UL BLER Switch for handover

4. UlPwrHoSwch UE Tx Power Switch for handover

5. DlPwrHoSwch DL Tx Power Switch for handover

6. HcsPrio(UUtranCellFDD) HCS_PRIO

7. HcsPrio(UExternalUtranC

ellFDD) HCS_PRIO

8. InterHoTactic Inter- frequency Handover Tactic

9. FilterCoeff(UInterEcNoEv

MeasforE) Filter Coefficient


MeasforG) Filter Coefficient


MeasforU) Filter Coefficient

12. FilterCoeff(UInterEcNoPrd




13. FilterCoeff(UInterRscpEv

MeasforE) Filter Coefficient


MeasforG) Filter Coefficient


MeasforU) Filter Coefficient

16. FilterCoeff(UInterRscpPrd


17. ThreshUsedFreq(UInterE

cNoEvMeasforE)

Absolute Threshold of the Quality of the

Currently Used Frequency for 2B/2D/2F


cNoEvMeasforG)




cNoEvMeasforU)



20. ThreshUsedFreq(UInterR

scpEvMeasforE)




scpEvMeasforG)




scpEvMeasforU)



23. Wused(UInterEcNoEvMe

asforE)

Weight of the Currently Used Frequency for

2A/2B/2D/2F


asforG)


2A/2B/2D/2F


asforU)


2A/2B/2D/2F

26. Wused(UInterRscpEvMea

sforE)


2A/2B/2D/2F


sforG)


2A/2B/2D/2F


sforU)


2A/2B/2D/2F

29. hysteresis(UInterEcNoEv

MeasforE) Hysteresis


MeasforG) Hysteresis




MeasforU) Hysteresis

32. hysteresis(UInterRscpEv

MeasforE) Hysteresis


MeasforG) Hysteresis


MeasforU) Hysteresis

35. TrigTime(UInterEcNoEvM

easforE) Time to Trigger


easforG) Time to Trigger


easforU) Time to Trigger

38. TrigTime(UInterRscpEvM

easforE) Time to Trigger


easforG) Time to Trigger


easforU) Time to Trigger

41. ThreshNoUsedFreq(UInte

rEcNoEvMeasforU)


Non-used Frequency for 2B/2C/2E

42. ThreshNoUsedFreq(UInte

rRscpEvMeasforU)


Non-used Frequency for 2B/2C/2E

43. WNoUsed(UInterEcNoEvM

easforU)

Weight of the Non-used Frequency for

2A/2B/2C/2E

44. WNoUsed(UInterRscpEvMe

asforU)

Weight of the Non-used Frequency for

2A/2B/2C/2E

45. PrdRptAmount(UInterEcN

oPrdMeas) Amount of Reporting in Period Report Criteria

46. PrdRptAmount(UInterRsc

pPrdMeas) Amount of Reporting in Period Report Criteria

47. PrdRptInterval(UInterEcN

oPrdMeas) Reporting Interval in Period Report Criteria

48. PrdRptInterval(UInterRsc

pPrdMeas) Reporting Interval in Period Report Criteria



49. PrdRptAmount(URatEcNo

PrdMeas) Amount of Reporting in Period Report Criteria

50. PrdRptAmount(URatRscp

PrdMeas) Amount of Reporting in Period Report Criteria

51. PrdRptInterval(URatEcNo


52. PrdRptInterval(URatRscp


53. ShareCover Share Cover Indication

54. MaxDlDpchPwr DPCH Maximum DL Power

55. profileId(UInterMeasProfil

e) Profile Id

56. profileId(UUeIntMeasProfi

le) Profile Id

57. refUInterMeasProfile Used Inter-frequency Measurement Profile


59. InterMeasCfgNo(UInterEc

NoEvMeasforE)

Inter-frequency Measurement Configuration

Index


NoEvMeasforG)


Index


NoEvMeasforU)


Index


NoPrdMeas)


Index

63. InterMeasCfgNo(UInterRs

cpEvMeasforE)


Index


cpEvMeasforG)


Index


cpEvMeasforU)


Index


cpPrdMeas)


Index

67. meaEvtId

(UInterEcNoEvMeasforE) Inter-frequency Event Identity

68. meaEvtId

(UInterEcNoEvMeasforG) Inter-frequency Event Identity



69. meaEvtId

(UInterEcNoEvMeasforU) Inter-frequency Event Identity

70. meaEvtId

(UInterRscpEvMeasforE) Inter-frequency Event Identity

71. meaEvtId

(UInterRscpEvMeasforG) Inter-frequency Event Identity

72. meaEvtId

(UInterRscpEvMeasforU) Inter-frequency Event Identity

73. srvCategory

Service and Bearer Type Used for

Differentiating Handover Configuration

74. InterMeasCfgNote Function of Configuration Parameters

75. MeasEvtNum

(UInterEcNoEvMeasforE)

Event Number of Inter-frequency

Measurement

76. MeasEvtNum

(UInterEcNoEvMeasforG)


Measurement

77. MeasEvtNum

(UInterEcNoEvMeasforU)


Measurement

78. MeasEvtNum

(UInterRscpEvMeasforE)


Measurement

79. MeasEvtNum

(UInterRscpEvMeasforG)


Measurement

80. MeasEvtNum

(UInterRscpEvMeasforU)


Measurement

81. StateMode(UUtranRelatio

n)

UE State Indicator Used for UTRAN

Neighboring Cell Configuration

82. NonIntraMeasQuan

UTRAN Measurement Quantity for

Inter-frequency and Inter-RAT measurements

83. PcpichPwrPre Primary CPICH Power Configuration Tag

84. primaryCpichPower Primary CPICH Power

85. amrIfHoSw AMR Inter Frequency Handover Switch

86. r99RtIfHoSw R99 RT Inter Frequency Handover Switch

87. r99NrtIfHoSw R99 NRT Inter Frequency Handover Switch

88. hsdpaIfHoSw HSDPA Inter Frequency Handover Switch

89. hsupaIfHoSw HSUPA Inter Frequency Handover Switch

90. CompMdCfgStra Compressed Mode Configuration Strategy



91. IfOrRatHoSwch

Inter Frequency or Inter RAT Handover

Switch

92. UeIntMCfgNo(UHoEvtTP

UeInt)

UE Internal Measurement Configuration

Index

93.

TResndMeaCtrlRel

The Time Threshold that the RNC May

Resend the MEASUREMENT CONTROL

RELEASE


95. txPowerThres(UHoEvtTP

UeInt)

UE Transmitted Power Threshold

96.

RncFeatSwitchBit9

Accompanying Compressed

Mode/Accompanying Dedicated Compressed

Mode

97. HcsSupportInd HCS Support Indicator

98.

RncFeatSwitchBit17

NotActivate/Activate

Compressed Mode for CS

Service When Radio Link

via IUR Exists

99. intialHoCelSelScene(UInt

erMeasProfile)


100. RncUlBlerHoSwch

RNC Switch for Handover Based on UL

BLER

101. RncTxPwrHoSwch

RNC Switch for Handover Based on UE Tx

Power

102. InterHoMth Inter-frequency Handover Method

103. IntRatHoMth Inter-RAT Handover Method

104. PeriodTriggerTime

Time To Trigger for Inter-frequency and

Inter-Rat Period Measurement

105. measRptTrMod(UHoEvtTPU

eInt)

Measurement Report Transfer

Mode(UHoEvtTPUeInt)

106. filterCoeff(UHoEvtTPUeInt) Filter Coefficient(UHoEvtTPUeInt)

107. measEvtNum(UHoEvtTPUeI

nt)


Measurement(UHoEvtTPUeInt)

108. meaEvtId(UHoEvtTPUeInt)

UE Internal Measurement Event

Identity(UHoEvtTPUeInt)



109. trigTime(UHoEvtTPUeInt) Time to Trigger(ms) (UHoEvtTPUeInt)

110. GResPara14 Global Reserved Parameter 14


112. CResPara6 Cell Reserved Parameter 6



115. DedMeasType

(UNbDedMeas) Dedicated Measurement Type

116. EvtAbcdefTime

(UNbDedMeas)


Hysteresis Time

117. MeasFilterCoeff

(UNbDedMeas) Measurement Filter Coefficient

118. RptPrd(UNbDedMeas) Report Period

119. RptPrdUnit

(UNbDedMeas) Choice Report Periodicity Scale

120. RptType(UNbDedMeas) Report Characteristics

121. EvtAbTcpThrd(UNbDedM

eas)

Measurement Threshold of Event A/B for

Transmitted Code Power

122. NbDMCfgNo(UNbDedMe

as) NbDed Measure Configuration No


13.2.2.1 Measurement Priority of Neighboring Cell

OMC path




The priority of a neighbouring cell can be set to 0, 1, and 2, of which, 0 represents the

highest priority and 2 represents the lowest priority. The priority of the neighbouring is set

by the configuration personnel according to the signal strength and the distance of the

neighboring cell.



13.2.2.2 Maximum Uplink SIR Target

OMC path


Configuration->Service Function->Power Control Profile Related to Service->Power

Control Related to Service->Power Control Related to Service and Diversity Mode


This parameter indicates the maximum target signal-to-interference ratio (SIR) of the

uplink.

When the uplink SIR is already in the maximum threshold, if certain error packets are still

detected, the power control will become invalid because the SIR cannot be further

adjusted upwards. If the UL BLER switch for handover has been opened, the RNC will

initiate the compressed mode and the inter-frequency measurement.

13.2.2.3 UL BLER Switch for Handover

OMC path



This parameter indicates the handover switch based on uplink block error rate (BLER).

When the switch is on, if the uplink BLER arrives at the threshold, RNC will initiate

compressed mode and the inter-frequency measurement.

13.2.2.4 UE Tx Power Switch for Handover

OMC path





This parameter indicates the handover switch based on uplink transmit power. When the

switch is on, if the uplink transmit power arrives at the threshold, RNC will initiate the

compressed mode and the inter-frequency measurement.

13.2.2.5 DL Tx Power Switch for Handover

OMC path



This parameter indicates the handover switch based on downlink transmit power. When

the switch is on, if the downlink transmit power arrives at the threshold, RNC will initiate

the compressed mode and the inter-frequency measurement.

13.2.2.6 HCS_PRIO(UUtranCellFDD)

OMC path



This parameter indicates the HCS priority level of the UTRAN cell. 7 represents the

highest priority and 0 represents the lowest priority. A cell with a higher priority often

provides a smaller coverage and a cell with a lower priority offers a larger coverage.

13.2.2.7 HCS_PRIO(UExternalUtranCellFDD)

OMC path






This parameter indicates the HCS priority level of the neighbouring cell. 7 represents the

highest priority and 0 represents the lowest priority. A cell with a higher priority often

provides a smaller coverage and a cell with a lower priority often offers a larger coverage.

13.2.2.8 Inter- frequency Handover Tactic

OMC path



This parameter indicates the event that is used to trigger the inter-frequency handover.

The default value of the parameter is 2A, that is, the handover can be triggered when the

conditions for best carrier frequency change are satisfied.

13.2.2.9 Filter Coefficient (UInterEcNoEvMeasforE)

OMC path


Configuration->Measurement Configuration->UE Inter-frequency Measurement

Profile->Inter-frequency Measurement Configuration Related to Traffic Category->UE

Inter-frequency Event Measurement Configuration for CPICH Ec/No(EUTRAN)



measurement results of the inter-frequency measurement. The smaller the value of the



13.2.2.10 Filter Coefficient(UInterEcNoEvMeasforG)

OMC path






Inter-frequency Event Measurement Configuration for CPICH Ec/No(GSM)






13.2.2.11 Filter Coefficient(UInterEcNoEvMeasforU)

OMC path




Inter-frequency Event Measurement Configuration for CPICH Ec/No(UTRAN)






13.2.2.12 Filter Coefficient(UInterEcNoPrdMeas)

OMC path



Profile->Inter-frequency Measurement Configuration Unrelated to Traffic Category->UE

Inter-frequency Period Measurement Configuration for CPICH Ec/No








13.2.2.13 Filter Coefficient(UInterRscpEvMeasforE)

OMC path




Inter-frequency Event Measurement Configuration for CPICH RSCP(EUTRAN)






13.2.2.14 Filter Coefficient(UInterRscpEvMeasforG)

OMC path




Inter-frequency Event Measurement Configuration for CPICH RSCP(GSM)








13.2.2.15 Filter Coefficient(UInterRscpEvMeasforU)

OMC path




Inter-frequency Event Measurement Configuration for CPICH RSCP(UTRAN)






13.2.2.16 Filter Coefficient(UInterRscpPrdMeas)

OMC path




Inter-frequency Period Measurement Configuration for CPICH RSCP








13.2.2.17 Absolute Threshold of the Quality of the Currently Used Frequency for

2B/2D/2F(UInterEcNoEvMeasforE)

OMC path






This parameter indicates the absolute threshold that should be configured for event

2b/2d/2f (used when judging the quality of the currently used carrier frequency).

In the case of event 2B, the less the threshold configured, the more difficult the event 2B

been triggered.

In the case of event 2D, the less the threshold configured, the more difficult the event 2D

been triggered.

In the case of event 2F, the less the threshold configured, the easier the event 2B is

triggered.


2B/2D/2F(UInterEcNoEvMeasforG)

OMC path











been triggered.


been triggered.


triggered.


2B/2D/2F(UInterEcNoEvMeasforU)

OMC path









been triggered.


been triggered.


triggered.


2B/2D/2F(UInterRscpEvMeasforE)

OMC path











been triggered.


been triggered.


triggered.


2B/2D/2F(UInterRscpEvMeasforG)

OMC path









been triggered.




been triggered.


triggered.


2B/2D/2F(UInterRscpEvMeasforU)

OMC path









been triggered.


been triggered.


triggered.

13.2.2.23 Weight of the Currently Used Frequency for

2A/2B/2D/2F(UInterEcNoEvMeasforE)

OMC path








This parameter is used for quality judgment of the currently used carrier frequency. It

indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2d/2f)

and is related to the measurement quantity and the event type.


2A/2B/2D/2F(UInterEcNoEvMeasforG)

OMC path










2A/2B/2D/2F(UInterEcNoEvMeasforU)

OMC path












2A/2B/2D/2F(UInterRscpEvMeasforE)

OMC path










2A/2B/2D/2F(UInterRscpEvMeasforG)

OMC path












2A/2B/2D/2F(UInterRscpEvMeasforU)

OMC path









13.2.2.29 Hysteresis (UInterEcNoEvMeasforE)

OMC path






This parameter indicates the hysteresis used when judging whether to trigger the event.

This parameter avoids the trigger status change due to very small change. Different

events are configured separately and the events can be configured with different values.



13.2.2.30 Hysteresis(UInterEcNoEvMeasforG)

OMC path













13.2.2.31 Hysteresis(UInterEcNoEvMeasforU)

OMC path











13.2.2.32 Hysteresis(UInterRscpEvMeasforE)

OMC path













13.2.2.33 Hysteresis(UInterRscpEvMeasforG)

OMC path











13.2.2.34 Hysteresis(UInterRscpEvMeasforU)

OMC path













13.2.2.35 Time to Trigger (UInterEcNoEvMeasforE)

OMC path











parameter should be set according to the actual requirements.

13.2.2.36 Time to Trigger(UInterEcNoEvMeasforG)

OMC path














13.2.2.37 Time to Trigger(UInterEcNoEvMeasforU)

OMC path












13.2.2.38 Time to Trigger(UInterRscpEvMeasforE)

OMC path














13.2.2.39 Time to Trigger(UInterRscpEvMeasforG)

OMC path












13.2.2.40 Time to Trigger(UInterRscpEvMeasforU)

OMC path














13.2.2.41 Absolute Threshold of the Quality of the Non-used Frequency for

2B/2C/2E(UInterEcNoEvMeasforU)

OMC path







2b/2c/2e (used when judging the quality of the non-used frequency).

In the case of event 2b, the less the threshold configured, the more difficult the event 2B

been triggered.

In the case of event 2c, the larger the threshold configured, the more difficult the event 2c

been triggered.

In the case of event 2E, the larger the threshold configured, the easier the event 2E been

triggered.

13.2.2.42 Absolute Threshold of the Quality of the Non-used Frequency for

2B/2C/2E(UInterRscpEvMeasforU)

OMC path









2b/2c/2e (used when judging the quality of the non-used frequency).

In the case of event 2b, the less the threshold configured, the more difficult the event 2B

been triggered.

In the case of event 2c, the larger the threshold configured, the more difficult the event 2c

been triggered.

In the case of event 2E, the larger the threshold configured, the easier the event 2E been

triggered.

13.2.2.43 Weight of the Non-used Frequency for

2A/2B/2C/2E(UInterEcNoEvMeasforU)

OMC path






This parameter is used for quality judgment of the currently non-used frequency. It

indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2c/2e)




13.2.2.44 Weight of the Non-used Frequency for

2A/2B/2C/2E(UInterRscpEvMeasforU)

OMC path






This parameter is used for quality judgment of the currently non-used frequency. It

indicates the weight of the best RNC in the quality judgment (only for event 2a/2b/2c/2e)


13.2.2.45 Amount of Reporting in Period Report Criteria (UInterEcNoPrdMeas)

OMC path











13.2.2.46 Amount of Reporting in Period Report Criteria (UInterRscpPrdMeas)

OMC path













13.2.2.47 Reporting Interval in Period Report Criteria (UInterEcNoPrdMeas)

OMC path







reporting criteria. In the case of the periodical report, the UE reports the inter-frequency

measurement results in the period indicated by the parameter.

13.2.2.48 Reporting Interval in Period Report Criteria (UInterRscpPrdMeas)

OMC path









reporting criteria. In the case of the periodical report, the UE reports the inter-frequency

measurement results in the period indicated by the parameter.

13.2.2.49 Amount of Reporting in Period Report Criteria (URatEcNoPrdMeas)

OMC path


Configuration->Measurement Configuration->Inter-RAT Measurement

Profile->Inter-RAT Measurement Configuration Unrelated to Traffic Category->UE

Inter-RAT Period Measurement Configuration for CPICH Ec/No


This parameter indicates the times of the periodical reports to be reported.

13.2.2.50 Amount of Reporting in Period Report Criteria (URatRscpPrdMeas)

OMC path




Inter-RAT Period Measurement Configuration for CPICH RSCP


This parameter indicates the times of the periodical reports to be reported.

13.2.2.51 Reporting Interval in Period Report Criteria (URatEcNoPrdMeas)

OMC path









reporting criteria.

13.2.2.52 Reporting Interval in Period Report Criteria (URatRscpPrdMeas)

OMC path







reporting criteria.

13.2.2.53 Share Cover Indication

OMC path




This parameter describes the neighboring relationship of the current cell and the

neighboring cell. The relationship between the neighbouring cell and the current cell may

be Neighbor, Overlap, Covers, or Contained in.

13.2.2.54 DPCH Maximum DL Power

OMC path




Configuration->Service Function->Power Control Profile Related to Service->Power

Control Related to Service->Power Control Related to Service and Diversity Mode


This parameter indicates the maximum downlink transmit power of DPCH.

When the downlink inner loop power control is performed, the new transmit power must

be smaller than or equal to the configured DPCH Maximum DL Power.

If the DL Tx Power Switch for Handover (DlPwrHoSwch) is open, the RNC judges the

downlink code power (DTCP) in the dedicated measurement report of the Node B. That

is, when the DTCP arrives at a certain threshold, the inter-frequency handover is

triggered.

13.2.2.55 Profile Id(UInterMeasProfile)

OMC path


Configuration->Measurement Configuration->UE Inter-frequency Measurement Profile


This parameter indicates the inter-frequency measurement profile identity.


OMC path







13.2.2.57 Used Inter-frequency Measurement Profile

OMC path



This parameter indicates the used inter-frequency measurement profile.


OMC path




13.2.2.59 Inter-frequency Measurement Configuration Index(UInterEcNoEvMeasforE)

OMC path






Each inter-frequency measurement configuration with different measurement purpose

and measurement quantity is assigned with a unique inter-frequency measurement

configuration index. This parameter indicates the index of the inter-frequency

measurement configuration. This configuration index is cited in the table Inter-frequency


That is, the parameter Inter-frequency Measurement Profile Identity (namely

profileId(UInterMeasProfile)) is cited in the advanced parameters of the serving cell and



different Inter-frequency Measurement Configuration Indexes (namely IntraMeasCfgNo)

can be selected aiming at the specific service type, measurement objective, and

measurement quantity. This parameter can be used to meet various requirements of

network planning.

13.2.2.60 Inter-frequency Measurement Configuration

Index(UInterEcNoEvMeasforG)

OMC path
















network planning.

13.2.2.61 Inter-frequency Measurement Configuration Index(UInterEcNoEvMeasforU)

OMC path


















network planning.

13.2.2.62 Inter-frequency Measurement Configuration Index(UInterEcNoPrdMeas)

OMC path


















network planning.

13.2.2.63 Inter-frequency Measurement Configuration Index(UInterRscpEvMeasforE)

OMC path
















network planning.

13.2.2.64 Inter-frequency Measurement Configuration Index(UInterRscpEvMeasforG)

OMC path


















network planning.

13.2.2.65 Inter-frequency Measurement Configuration Index(UInterRscpEvMeasforU)

OMC path


















network planning.

13.2.2.66 Inter-frequency Measurement Configuration Index(UInterRscpPrdMeas)

OMC path
















network planning.

13.2.2.67 Inter-frequency Event Identity(UInterEcNoEvMeasforE)

OMC path








This parameter indicates the identity of the event triggered by the inter-frequency

measurement (2a~2f).

13.2.2.68 Inter-frequency Event Identity(UInterEcNoEvMeasforG)

OMC path








13.2.2.69 Inter-frequency Event Identity(UInterEcNoEvMeasforU)

OMC path








13.2.2.70 Inter-frequency Event Identity(UInterRscpEvMeasforE)

OMC path










13.2.2.71 Inter-frequency Event Identity(UInterRscpEvMeasforG)

OMC path








13.2.2.72 Inter-frequency Event Identity(UInterRscpEvMeasforU)

OMC path











OMC path



Profile->Inter-frequency Measurement Configuration Related to Traffic Category



services, channel type, and service quantity. This parameter indicates the service and

bearer type. The handover parameters can be configured flexibly for different scenarios

and the parameters may have different handover triggering thresholds and hysteresis.

The value 0xff (Not Related to Service Type) is exclusively used in the measurement of

the detected set.

Table 13-1 Service Type Related UE Inter-frequency Measurement Parameter

Configuration Default Value

Field Name Defa

ult

Valu

e 1

Defa

ult

Valu

e 2

Defa

ult

Valu

e 3

Defa

ult

Valu

e 4

Defa

ult

Valu

e 5

Defa

ult

Valu

e 6

Defa

ult

Valu

e 7

Defa

ult

Valu

e 8

Def

ault

Val

ue 9

profileId(UInte

rMeasProfile)

1 1 1 1 1 1 1 1 1

srvCategory 0 1 2 3 4 5 6 7 0xff

UInterEcNoPr

dMeas

0 0 0 0 0 0 0 0 0

UInterEcNoEv

MeasforU

3 3 3 3 3 3 3 3 3

UInterRscpPrd

Meas

4 4 4 4 4 4 4 4 4

UInterRscpEv

MeasforU

7 7 7 7 7 7 7 7 7




OMC path




This parameter indicates the purpose and functions of the set of inter-frequency

measurement configuration parameters.

13.2.2.75 Event Number of Inter-frequency Measurement(UInterEcNoEvMeasforE)

OMC path






This parameter indicates the number of events that should be configured for the index of

the inter-frequency measurement configuration for a certain purpose.

13.2.2.76 Event Number of Inter-frequency Measurement(UInterEcNoEvMeasforG)

OMC path










13.2.2.77 Event Number of Inter-frequency Measurement(UInterEcNoEvMeasforU)

OMC path








13.2.2.78 Event Number of Inter-frequency Measurement(UInterRscpEvMeasforE)

OMC path








13.2.2.79 Event Number of Inter-frequency Measurement(UInterRscpEvMeasforG)

OMC path










13.2.2.80 Event Number of Inter-frequency Measurement(UInterRscpEvMeasforU)

OMC path








13.2.2.81 UE State Indicator Used for UTRAN Neighboring Cell Configuration

OMC path




This parameter indicates the UE status applied to the neighboring cell. When the

neighbouring cell is configured by status, the neighbouring cells list used for reselection

in non-dedicated mode and the neighbouring cells list for handover in dedicated mode

are differentiated as follows:








13.2.2.82 UTRAN Measurement Quantity for Inter-frequency and Inter-RAT

Measurements

OMC path



This parameter indicates the UTRAN measurement quantity (Ec/No or RSCP) for the

inter-frequency and inter-RAT measurements. The measurement quantity RSCP is

recommended.

13.2.2.83 Primary CPICH Power Configuration Tag

OMC path




This parameter indicates whether PCPICH transmission power is configured.

PCPICH transmission power is valid when this parameter is set “True”. Otherwise,

PCPICH transmission power is invalid.

13.2.2.84 Primary CPICH Power

OMC path






This parameter indicates the value of PCPICH transmission power.

13.2.2.85 AMR Inter Frequency Handover Switch

OMC path




This parameter indicates whether AMR inter-frequency handover allowed or not.

13.2.2.86 R99 RT Inter Frequency Handover Switch

OMC path




This parameter indicates whether R99 RT inter-frequency handover allowed or not.

13.2.2.87 R99 NRT Inter Frequency Handover Switch

OMC path




This parameter indicates whether R99 NRT inter-frequency handover allowed or not.



13.2.2.88 HSDPA Inter Frequency Handover Switch

OMC path




This parameter indicates whether HSDPA inter-frequency handover allowed or not.

13.2.2.89 HSUPA Inter Frequency Handover Switch

OMC path




This parameter indicates whether HSUPA inter-frequency handover allowed or not.

13.2.2.90 Compressed Mode Configuration Strategy

OMCR Interface




This parameter indicates whether inter-frequency and inter-rat compressed mode will be

configured to the UE simultaneously or not, when inter-frequency cells and inter-rat

neighboring cells exist.

0: Configure Inter-Frequency and Inter-Rat Compressed Mode Simultaneously

1: Configure Inter-Frequency and Inter-Rat Compressed Mode Individually



13.2.2.91 Inter Frequency or Inter RAT Handover Switch

OMCR Interface




This parameter indicates how to perform neighbor measurement if a cell has both

inter-frequency and inter-RAT cells as its neighbors.

0: Turn off Inter-frequency and Inter-RAT Handover

1: Only Inter Frequency

2: Only Inter Rat

3: Inter Frequency is Prior to Inter Rat

13.2.2.92 UE Internal Measurement Configuration Index(UHoEvtTPUeInt)

OMC path



Transmitted Power Event Measurement Configuration for Handover-> UE Internal

Measurement Configuration Index


This parameter indicates the UE internal measurement configuration index


CONTROL RELEASE

OMC path













OMC path



The parameter indicates handover and cell reselection scenario.

13.2.2.95 UE Transmitted Power Threshold(UHoEvtTPUeInt)

OMC path



Transmitted Power Event Measurement Configuration for Handover


This parameter indicates the UE transmitted power threshold in event 6a/6b.

13.2.2.96 Accompanying Compressed Mode/Accompanying Dedicated Compressed

Mode

OMC path


Link




This parameter indicates whether adjacent RNC supports accompanying compressed

mode or not.

RncFeatSwitchBit9=0: not support, use dedicated compressed mode;

RncFeatSwitchBit9=1: support.

13.2.2.97 HCS Support Indicator

OMC path



This parameter indicates whether to process the handover judgement based on moving

speed or not.

HcsSupportInd=2/3: support HCS in handover; HcsSupportInd=0/1: not support HCS in

handover.

13.2.2.98 NotActivate/Activate Compressed Mode for CS Service When Radio Link

via IUR Exists

OMC path


Link


This parameter indicates whether to activate compressed mode for CS service when

radio link via IUR exists.

13.2.2.99 Mobility Configuration Scene(UInterMeasProfile)

OMC path








13.2.2.100 RNC Switch for Handover Based on UL BLER

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->RNC Switch for

Handover Based on UL BLER


The parameter indicates the RNC switch for handover based on uplink BLER. When the

switch is "Off", the function is turned off; when the switch is "On", judge the cell switch

UlBlerHoSwch to decide whether the function is turned on.

13.2.2.101 RNC Switch for Handover Based on UE Tx Power

OMC path


Handover Based on UE Tx Power


The parameter indicates the RNC switch for handover based on transmit power. When

the switch is "Off", the function is turned off; when the switch is "On", judge the cell switch

UlPwrHoSwch/DlPwrHoSwch to decide whether the function is turned on.

13.2.2.102 Inter-frequency Handover Method

OMC path



GUI: Managed Element ->UMTS Logical Function Configuration->Inter-frequency

Handover Method


The parameter indicates the inter-frequency handover method is periodical method or

event method.

13.2.2.103 Inter-RAT Handover Method

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Inter-RAT Handover

Method


The parameter indicates the inter-RAT handover method is periodical method or event

method.

13.2.2.104 Time To Trigger for Inter-frequency and Inter-Rat Period Measurement

OMC path


Cell->Extended Info of UTRAN Cell->Time To Trigger for Inter-frequency and Inter-Rat

Period Measurement


The parameter indicates interval between reception of periodical reports and triggering of

the inter-frequency or inter-rat handover. Only the neighboring cell in which the signal

quality is above a certain threshold in all periodic reports during a time equal to this

parameter can be selected as the target cell for the inter-frequency or inter-rat handover.

If this parameter is set to a greater value, the probability of incorrect decision becomes

low; however, the handover algorithm becomes slow in responding to signal change.



13.2.2.105 Measurement Report Transfer Mode (UHoEvtTPUeInt)

OMC path





The parameter indicates the RLC mode of the UE internal measurement report.

13.2.2.106 Filter Coefficient (UHoEvtTPUeInt)

OMC path





The parameter indicates the filtering factor that the UE performs the L3 filtering on the


13.2.2.107 Maximum Event Number of UE Internal Measurement (UHoEvtTPUeInt)

OMC path





The parameter indicates the maximum event number of UE internal measurement.



13.2.2.108 UE Internal Measurement Event Identity (UHoEvtTPUeInt)

OMC path





The parameter indicates the UE internal measurement event identity.

13.2.2.109 Time to Trigger (ms) (UHoEvtTPUeInt)

OMC path





The parameter indicates the period of time during which the event condition has to be



OMC path


Parameter 14


The parameter is the switch of associated compressed mode when the UE leaves

common state. 0: closed, do not configure accompanying compressed mode; 1: open,

configure accompanying compressed mode.




OMC path


Parameter 6


The parameter is the penlty timer. When inter frequency handover is failed, the timer is

initialization, and RNC will not handle inter-frequency measurement report until the timer

expires.


OMC path


Cell->Extended Info of UTRAN Cell-> Cell Reserved Parameter 6


This parameter indicates whether RNC judge the minimu quality threshold of target cells

in inter-frequency handover. If the switch is On, when the signal quality of target cells'

quality is lower than GresPara2 or GresPara5, RNC will not perform the inter frequency

handover.


OMC path


Parameter 2




This parameter indicates the CPICH EcNo minimum threshold for inter frequency

handover. If reported CPICH EcNo is less than GresPara2 or CPICH RSCP is less than

GresPara5, inter frequency handover will not be triggered.


OMC path


Parameter 5


This parameter indicates the CPICH RSCP minimum threshold for inter frequency

handover. If reported CPICH EcNo is less than GresPara2 or CPICH RSCP is less than

GresPara5, inter frequency handover will not be triggered.

13.2.2.115 Dedicated Measurement Type

OMC path


Configuration->Measurement Configuration->NodeB Dedicated Measurement Profile ->

NodeB Dedicated Measurement Configuration


This parameter indicates the type of dedicated measurement to be executed by Node B.

Configuration Rule: Dedicated measurement type should be chose according to the

usage of the dedicated measurement.

13.2.2.116 Measurement Change Time /Measurement Hysteresis Time

OMC path







For event A/B, this parameter is measurement hysteresis time and the measurement

hysteresis time provides the duration during which a reporting criterion has to be fulfilled

for the Measurement Reporting procedure to be triggered.

Configuration Rule: according to the measurement type and event of the dedicated

measurement.

The larger this parameter is, the more difficult to trigger the measurement event.

13.2.2.117 Measurement Filter Coefficient

OMC path





This parameter indicates the L3 filter coefficient.

The involved factor for setting this parameter: the smoothness and real-time of

measurement report value.

Influence of this parameter: the less of the value, the less fluctuate of the measurement

report value; the larger of the value, the more real-time of the measurement report value.

Suggestion for setting this parameter: not suggested to adjust.

13.2.2.118 Report Period

OMC path







This parameter indicates the frequency of measurement report transmitted by Node B.

Configuration Rule: According to the contribution to the system load and the timeliness of

the measurement report.

The larger the value, the more contribution to the system load but the less timely of the

measurement report; the smaller the value, the less contribution to the system load but

the timelier of the measurement report.

13.2.2.119 Choice Report Periodicity Scale

OMC path


Configuration->Measurement Configuration->Node B Dedicated Measurement Profile ->

Node B Dedicated Measurement Configuration


This parameter indicates the time unit of measurement report transmitted by Node B.

Configuration Rule: According to the measurement period which is determined according

to the contribution to the system load and the timeliness of the measurement report.

13.2.2.120 Report Characteristics

OMC path







This parameter indicates the report characteristics of measurement results, which can be

on demand, periodic or by triggering all kinds of events.


measurement.

13.2.2.121 Measurement Threshold of Event A/B for Transmitted Code Power

OMC path





The parameter indicates the power offset of the DPCH maximum DL power, which

defines which threshold that shall trigger event A, B for transmitted carrier power

measurement.

This parameter is a ternary array, which is fixed to the first element evtAbTcpThrd[0] for

handover control.

13.2.2.122 NbDed Measure Configuration No

OMC path





This parameter indicates the NbDed Measure Configuration Number.



13.3 SRNC Relocation Parameters


No. Parameter Field Name Name on the Interface

1. Trelocprep

SRNC Wait Time for Relocation Preparation

(100ms)

2. Trelocoverall

SRNC Overall Protective Time for Relocation

(100ms)

3. CsReDelayTimer Timer of Relocation Delay for CS Service

4. PsReDelayTimer Timer of Relocation Delay for PS Service


Not Support/Support UE not Involved

Relocation for CS Service


Not Support/Support UE not Involved

Relocation for PS Service


Hard-handover Without/With Relocation for CS

Service


PS Service hard-switch not together/together

with relocation

9. GresPara48 Global Reserved Parameter 48

10.

dscrInCmnToDedSwch

Switch of DSCR in Transferring

Unsuccessfully from Common Status to

CELL_DCH status

11. RNCFEATSWITCHBit24

Support HSPA fallback procedure for

inter-frequency handover via IUR


NotSupport/Support that the RNC forwarding

date when Relocation


13.3.2.1 SRNC Wait Time for Relocation Preparation

OMC path


Configuration->Iu Interface Timers and Constants Information




This parameter specifies the maximum time for Relocation Preparation procedure in the

source RNC after the SRNC successfully sends the RELOCATION REQUIRED

message to the CN. If the SRNC fails to receive the RELOCATION COMMAND message

within the time specified by the parameter, the timer is judged as expiry and the

relocation is canceled.

13.3.2.2 SRNC Overall Protective Time for Relocation

OMC path




This parameter specifies the maximum time for the initiation of the Iu release by the CN

after the SRNC receives the RELOCATION COMMAND message. If the CN fails to

initiate the Iu release within the time specified by the parameter, the timer is judged as

expiry and the SRNC initiates the Iu release instead.

13.3.2.3 Timer of Relocation Delay for CS Service

OMC path


Link


This parameter is applicable to CS services. It indicates the delay of initiating the

relocation procedure after the link at the S side is deleted.

13.3.2.4 Timer of Relocation Delay for PS Service

OMC path




Link


This parameter is applicable to PS services. It indicates the delay of initiating the

relocation procedure after the link at the S side is deleted.

13.3.2.5 Not Support/Support UE not Involved Relocation for CS Service

OMC path


Link


This parameter indicates whether to support the relocation which the UE is not involved

for CS service or not.

13.3.2.6 Not Support/Support UE not Involved Relocation for PS Service

OMC path


Link


This parameter indicates whether to support the relocation which UE is not involved for

PS service or not.

13.3.2.7 Hard-handover Without/With Relocation for CS Service

OMC path


Link




This parameter indicates whether hard handover can accompany with the relocation for

CS service or not.

13.3.2.8 PS Service hard-switch not together/together with relocation

OMC path


Link


This parameter indicates whether hard handover can accompany with the relocation for

PS service or not.


OMC path


Parameter 48


This parameter bit11 indicates what moment should send Relocation Detect

message to CN in soft handover relocation procedure.

Bit11=0: when the DRNC receives a UTRAN Mobility Information Confirm message

from UE, then send Relocation Detect message to CN;

Bit11=1: When the DRNC receives a Relocation Commit message from SRNC, then

send Relocation Detect message to CN.



13.3.2.10 Switch of DSCR in Transferring Unsuccessfully from Common Status to

CELL_DCH status

OMC path



This parameter indicates whether RNC should execute DSCR procedure when

transferring unsuccessfully from common connected RRC status to dedicated connected

RRC status with the UE returning configuration related failure cause.

13.3.2.11 Support HSPA fallback procedure for inter-frequency handover via IUR

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Iur Link Configuration


This parameter indicates whether RNC supports HSPA fallback procedure for

inter-frequency handover via IUR. If compatibility problem between vendors exists, this

parameter should be set "1".

13.3.2.12 NotSupport/Support that the RNC forwarding date when Relocation

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Iur Link Configuration


This parameter indicates whether the RNC forwarding date when Relocation.



13.4 GSM Inter-RAT Handover Parameters



1. MeasPrio Measurement Priority of Neighboring GSM Cell

2. RatHoTactic Inter-Rat Handover Tactic

3. UlBlerHoSwch UL BLER Switch for handover

4. DlPwrHoSwch DL Tx Power Switch for handover

5. UlPwrHoSwch UE Tx Power Switch for handover

6. Thresh(URatEcNoEvMea

sforG)

Absolute Threshold of the Quality of UTRAN Cell for

3A

7. Thresh(URatRscpEvMeas

forG)

Absolute Threshold of the Quality of UTRAN Cell for

3A

8. W(URatEcNoEvMeasforG

) Weight of the UTRAN System for 3A

9. W(URatRscpEvMeasforG

) Weight of the UTRAN System for 3A

10. ThreshSys(URatEcNoEv

MeasforG)


3A/3B/3C

11. ThreshSys(URatRscpEvM

easforG)


3A/3B/3C

12. hysteresis(URatEcNoEvM

easforG) Hysteresis

13. hysteresis(URatRscpEvM

easforG) Hysteresis

14. TrigTime(URatEcNoEvMe

asforG) Time to Trigger

15. TrigTime(URatRscpEvMe

asforG) Time to Trigger

16. profileId(URatMeasProfile

) Profile Id

17. profileId(UUeIntMeasProfi

le) Profile Id

18. refURatMeasProfile Used Inter-RAT Measurement Profile




20. srvCategory

Service and Bearer Type Used for Differentiating

Handover Configuration

21. InterRatCfgNo(URatEcNo

EvMeasforG) Inter-RAT Measurement Configuration Index

22. InterRatCfgNo(URatEcNo

PrdMeas) Inter-RAT Measurement Configuration Index

23. InterRatCfgNo(URatRscp

EvMeasforG) Inter-RAT Measurement Configuration Index

24. InterRatCfgNo(URatRscp

PrdMeas) Inter-RAT Measurement Configuration Index

25. InterRatCfgNote Function of Configuration Parameters

26. FilterCoeff(URatEcNoEvM

easforG) UTRAN Filter Coefficient

27. FilterCoeff(URatEcNoPrd

Meas) UTRAN Filter Coefficient

28. FilterCoeff(URatRscpEvM

easforG) UTRAN Filter Coefficient

29. FilterCoeff(URatRscpPrd

Meas) UTRAN Filter Coefficient

30. GsmFilterCoeff(URatEcN

oEvMeasforG) GSM Filter Coefficient

31. GsmFilterCoeff(URatEcN

oPrdMeas) GSM Filter Coefficient

32. GsmFilterCoeff(URatRscp

EvMeasforG) GSM Filter Coefficient

33. GsmFilterCoeff(URatRscp

PrdMeas) GSM Filter Coefficient

34. GeranCellInd GERAN Cell Indicator

35. EventNum(URatEcNoEv

MeasforG) Inter-RAT Measurement Event Number

36. EventNum(URatRscpEvM

easforG) Inter-RAT Measurement Event Number



37. EventId

[MAX_RAT_MEAS_EVEN

T]

(URatEcNoEvMeasforG)

Inter-RAT Event Identity

38. EventId

[MAX_RAT_MEAS_EVEN

T]

(URatRscpEvMeasforG)


39. CellIndivOffset

(UExternalGsmCell) Cell individual offset

40. GsmStateMode

UE State Indicator Used for GSM Neighboring Cell

Configuration

41. GsmShareCover Share Cover Indication

42. NonIntraMeasQuan

UTRAN Measurement Quantity for Inter-frequency

and Inter-RAT Measurements

43. HcsPrio

(UExternalGsmCell) HCS_PRIO

44. psInterSysHoSuppInd PS Inter-System Handover Indicator

45. DtmSuppInd Inter-System DTM Support Indicator

46. BSCPSFeatSwitch

Neighboring BSC whether or not Supports PS

Handover

47. BSCDTMFeatSwitch

Neighboring BSC whether or not Supports DTM

Handover

48. LdBsdIntSysHOInd Loading based InterSys HO Support Indicator

49. CellLdInfoVldTim Duration of Valid Cell Load Info

50. GsmUlRtLdThrd GSM Uplink RT Load Threshold

51. GsmDlRtLdThrd GSM Downlink RT Load Threshold

52. GsmUlLdThrd GSM Uplink Load Threshold

53. GsmDlLdThrd GSM Downlink Load Threshold

54. NaccSuppInd Nacc Support Indicator

55. HoToGsmPenTimer Handover to GSM Penalty Timer

56. srvBasedHoInd Service-Based Handover Support Indicator

57. ServHoSwch Service Handover Switch

58. srvHoComStra Service Handover Combination Strategy

59. amrRatHoSw AMR Inter Rat Handover Switch



60. r99RtRatHoSw R99 RT Inter Rat Handover Switch

61. r99NrtRatHoSw R99 NRT Inter Rat Handover Switch

62. hsdpaRatHoSw HSDPA Inter Rat Handover Switch

63. hsupaRatHoSw HSUPA Inter Rat Handover Switch

64. T4StpIfMeaActRat

Timer for Stopping Inter-frequency Measurement

and Activating Inter-RAT Measurement

65. srvHoIndAmr Service Handover Strategy Indicator

66. srvHoIndCs64 Service Handover Strategy Indicator

67. srvHoIndPsNRT Service Handover Strategy Indicator

68. srvHoIndPsRT Service Handover Strategy Indicator

69. amrSrvHoStra Service Handover Strategy of RNC for AMR

70. cs64SrvHoStra Service Handover Strategy of RNC for CS64

71. psRtSrvHoStra

Service Handover Strategy of RNC for PS RT

service

72. psNrtSrvHoStra

Service Handover Strategy of RNC for PS NRT

service

73. Tdatafwd

Maximum Time for Forwarding GTP-PDU Data in

SRNC

74. TWaitContextReq Waiting Timer for SRNS Context Request

75. TWaitDataFwd

Waiting Timer for SRNS DATA FORWARD

COMMAND

76. TWaitRelCmd Waiting Timer for IU RELEASE COMMAND

77. UeIntMCfgNo(UHoEvtTP

UeInt) UE Internal Measurement Configuration Index

78. TResndMeaCtrlRel

The Time Threshold that the RNC May Resend the

MEASUREMENT CONTROL RELEASE


80. IurgFeatSwitch Whether Support Iur-g Signaling Procedure

81. BoardPwrOffHoTmr

The Waiting Timer for UE Handover When Board's

Power is Off

82. intialHoCelSelScene(URa

tMeasProfile)


83. txPowerThres(UHoEvtTP

UeInt)

UE Transmitted Power Threshold



84. RncUlBlerHoSwch RNC Switch for Handover Based on UL BLER

85. RncTxPwrHoSwch RNC Switch for Handover Based on UE Tx Power

86. measRptTrMod(UHoEvtTPU

eInt)

Measurement Report Transfer

Mode(UHoEvtTPUeInt)

87. filterCoeff(UHoEvtTPUeInt) Filter Coefficient(UHoEvtTPUeInt)

88. measEvtNum(UHoEvtTPUeI

nt)


Measurement(UHoEvtTPUeInt)

89. meaEvtId(UHoEvtTPUeInt)

UE Internal Measurement Event

Identity(UHoEvtTPUeInt)

90. trigTime(UHoEvtTPUeInt) Time to Trigger(ms) (UHoEvtTPUeInt)

91. RatCelInfoSwch Inter-rat Cell Information indication Strategy

92. rxlevNecellInd

Switch of RXLEV-NECELL indication in

oldBSS_ToNewBSS

93. DedMeasType

(UNbDedMeas) Dedicated Measurement Type

94. EvtAbcdefTime

(UNbDedMeas)


Hysteresis Time

95. MeasFilterCoeff

(UNbDedMeas) Measurement Filter Coefficient

96. RptPrd(UNbDedMeas) Report Period

97. RptPrdUnit

(UNbDedMeas) Choice Report Periodicity Scale

98. RptType(UNbDedMeas) Report Characteristics

99. EvtAbTcpThrd(UNbDedM

eas)

Measurement Threshold of Event A/B for

Transmitted Code Power

100. NbDMCfgNo(UNbDedMe

as) NbDed Measure Configuration No


13.4.2.1 Measurement Priority of Neighboring GSM Cell

OMC path




Cell->Adjacent Relation Configuration->GSM Neighbouring Cell


This parameter indicates the measurement priority of the neighboring cell. 0 presents the

highest priority and 2 presents the lowest priority. This parameter should be configured

by the network planning engineer according to the actual conditions of the current

network, including the quality and geographic position of the inter-RAT neighbouring cell.

13.4.2.2 Inter-Rat Handover Tactic

OMC path



This parameter indicates the measurement event type (3A or 3C) that is used to trigger

the inter-RAT handover.

Event 3C can be triggered when the quality of the inter-RAT carrier frequency signal is

higher than a certain value. In contrast, the trigger of event 3A requires an additional

condition, that is, the quality of the carrier frequency signal of the current RAT must be

less than a certain value. Hence, the inter-RAT handover can be triggered more easily

when the parameter is set to 3C Event Trigger.

13.4.2.3 UL BLER Switch for Handover

OMC path



This parameter indicates the handover switch based on uplink BLER. When the switch is

on, the RNC will initiate compressed mode and inter-RAT measurement if the uplink

BLER quality arrives at the threshold.



13.4.2.4 DL Tx Power Switch for handover

OMC path



This parameter indicates the handover switch based on downlink transmit power. When

the switch is on, the RNC will initiate compressed mode and inter-RAT measurement if

the downlink transmit power arrives at the threshold.

13.4.2.5 UE Tx Power Switch for handover

OMC path



This parameter indicates the handover switch based on uplink transmit power. When the

switch is on, the RNC will initiate compressed mode and inter-RAT measurement if the

uplink transmit power arrives at the threshold.

13.4.2.6 Absolute Threshold of the Quality of UTRAN Cell for

3A(URatEcNoEvMeasforG)

OMC path



Profile->Inter-RAT Measurement Configuration Related to Traffic Category->UE

Inter-RAT Event Measurement Configuration for CPICH Ec/No(GSM)




This parameter indicates the absolute threshold of the UTRAN cell quality that is used by

the UE to judge event 3a. The range and unit of the parameter are related to the

measurement quantity of the cells of the UTRAN system.

The smaller the value configured, the more difficult the event 3a been reported.


3A(URatRscpEvMeasforG)

OMC path




Inter-RAT Event Measurement Configuration for CPICH RSCP(GSM)






13.4.2.8 Weight of the UTRAN System for 3A(URatEcNoEvMeasforG)

OMC path






This parameter indicates the weight of the best cell in the quality judgment of event 3a. It

is used in judging the quality of the UTRAN system in inter-RAT measurement.



See the description of the formula in Section 7.1 for the effect of this parameter on the


13.4.2.9 Weight of the UTRAN System for 3A(URatRscpEvMeasforG)

OMC path










13.4.2.10 Absolute Threshold of the Quality of Other RAT for

3A/3B/3C(URatEcNoEvMeasforG)

OMC path






This parameter indicates the absolute threshold used when judging the quality of other

RAT configured for event 3a/3b/3c. The value range and unit of this parameter are

related to the measurement quantity of the cells of other systems. At present, the

measurement quantity can only be GSM Carrier RSSI of the GSM system, which



corresponds to the CPICH RSCP of the UMTS system. Hence, the value range and unit

of this parameter correspond to CPICH RSCP.

The larger the value is configured, the more difficult it is to report event 3a/3b/3c.


3A/3B/3C(URatRscpEvMeasforG)

OMC path












The larger the value is configured, the more difficult it is to report event 3a/3b/3c.

13.4.2.12 Hysteresis(URatEcNoEvMeasforG)

OMC path








This parameter indicates the hysteresis used when judging whether the event meets the

conditions of been triggered.

This parameter is related to the measurement quantity and the event type. If a small

hysteresis is configured, the corresponding event will be reported in a high probability;

and vice versa.

13.4.2.13 Hysteresis(URatRscpEvMeasforG)

OMC path










and vice versa.

13.4.2.14 Time to Trigger(URatEcNoEvMeasforG)

OMC path







is detected and the time that the event is reported. The event can be triggered and



reported only when the event is detected and still meets all requirements of event

triggering after Time to trigger.



13.4.2.15 Time to Trigger(URatRscpEvMeasforG)

OMC path












13.4.2.16 Profile Id(URatMeasProfile)

OMC path


Configuration->Measurement Configuration->Inter-RAT Measurement Profile


This parameter indicates inter-RAT measurement profile identity.




OMC path





13.4.2.18 Used Inter-RAT Measurement Profile

OMC path



This parameter indicates the used inter-RAT measurement profile.


OMC path





OMC path



Profile->Inter-RAT Measurement Configuration Related to Traffic Category





the services, channel type, and service quantity. This parameter indicates the service

and bearer type. The handover parameters can be configured flexibly for different

scenarios and the parameters may have different handover triggering thresholds and

hysteresis.

The value 0xff (Not Related to Service Type) is exclusively used in the measurement of

the detected set.

Table 13-2 Service Type Related UE Inter-RAT Measurement Parameter Configuration

Default Value

Field Name Defa

ult

Valu

e 1

Defa

ult

Valu

e 2

Defa

ult

Valu

e 3

Defa

ult

Valu

e 4

Defa

ult

Valu

e 5

Defa

ult

Valu

e 6

Defa

ult

Valu

e 7

Defa

ult

Valu

e 8

Def

ault

Valu

e 9

profileId(URat

MeasProfile)

1 1 1 1 1 1 1 1 1

srvCategory 0 1 2 3 4 5 6 7 0xff

URatEcNoPrd

Meas

0 0 0 0 0 0 0 0 0

URatEcNoEv

MeasforG

2 2 2 2 2 2 2 2 2

URatRscpPrd

Meas

3 3 3 3 3 3 3 3 3

URatRscpEv

MeasforG

5 5 5 5 5 5 5 5 5

13.4.2.21 Inter-RAT Measurement Configuration Index(URatEcNoEvMeasforG)

OMC path








Each inter-RAT measurement configuration with different measurement purpose and

measurement quantity is assigned with a unique inter-RAT measurement configuration.

This parameter indicates the index of the inter-RAT measurement configuration. This

configuration index is cited in the table “Inter-RAT measurement configuration

relationship of the service type-related UE”.

That is, the parameter Inter-RAT Measurement Profile Identity (namely

profileId(URatMeasProfile)) is cited in the advanced parameter of the serving cell and

different Inter-RAT Measurement Configuration Index (namely InterMeasCfgNo) can

be selected aiming at the specific service type, measurement purpose, and


network planning.

13.4.2.22 Inter-RAT Measurement Configuration Index(URatEcNoPrdMeas)

OMC path


















network planning.

13.4.2.23 Inter-RAT Measurement Configuration Index(URatRscpEvMeasforG)

OMC path
















network planning.

13.4.2.24 Inter-RAT Measurement Configuration Index(URatRscpPrdMeas)

OMC path


















network planning.


OMC path




This parameter indicates the purpose and functions of the set of inter-RAT measurement

configuration parameters.

13.4.2.26 UTRAN Filter Coefficient(URatEcNoEvMeasforG)

OMC path









UTRAN measurement results of the inter-RAT measurement. The smaller the filtering

factor, the larger the effect of the measurement on the final result.

13.4.2.27 UTRAN Filter Coefficient(URatEcNoPrdMeas)

OMC path









13.4.2.28 UTRAN Filter Coefficient(URatRscpEvMeasforG)

OMC path









13.4.2.29 UTRAN Filter Coefficient(URatRscpPrdMeas)

OMC path











13.4.2.30 GSM Filter Coefficient (URatEcNoEvMeasforG)

OMC path







GSM measurement results of the inter-RAT measurement. The smaller the filtering factor,

the larger the effect of the measurement on the final result.

13.4.2.31 GSM Filter Coefficient(URatEcNoPrdMeas)

OMC path











13.4.2.32 GSM Filter Coefficient(URatRscpEvMeasforG)

OMC path









13.4.2.33 GSM Filter Coefficient(URatRscpPrdMeas)

OMC path









13.4.2.34 GERAN Cell Indicator

OMC path




Configuration->External GSM Cell


This parameter indicates whether the cell is a GERAN cell.

13.4.2.35 Inter-RAT Measurement Event Number(URatEcNoEvMeasforG)

OMC path






This parameter indicates the number of events that should be configured for the

inter-RAT measurement configuration index for a certain purpose.

13.4.2.36 Inter-RAT Measurement Event Number(URatRscpEvMeasforG)

OMC path








13.4.2.37 Inter-RAT Event Identity(URatEcNoEvMeasforG)

OMC path








This parameter indicates the identity of the event triggered by the inter-RAT

measurement (3a~3d).

13.4.2.38 Inter-RAT Event Identity(URatRscpEvMeasforG)

OMC path








13.4.2.39 Cell individual offset(UExternalGsmCell)

OMC path




This parameter indicates the individual offset of GSM cells. When the value is positive, a

positive value is added to the measurement result to be judged. If the value is negative, a

negative value is added to the measurement result to be judged. See the introduction to

inter-RAT measurement in section 7.1.1 for the effect of this parameter on the

measurement report.




the cell can be adjusted to meet the actual requirements of network planning, thus

avoiding the need to modify the global handover parameters.

13.4.2.40 UE State Indicator Used for GSM Neighboring Cell Configuration

OMC path




This parameter indicates the UE status applied to the GSM neighboring cell. When the

neighbouring cell is configured by status, the neighbouring cells list used for reselection

in non-dedicated mode and the neighbouring cells list used for handover in dedicated

mode are differentiated as follows:






13.4.2.41 Share Cover Indication

OMC path




This parameter indicates the neighboring relationship of the current cell and GSM

neighboring cell, including Neighbor, Overlap, Covers, and Contained in.



13.4.2.42 UTRAN Measurement Quantity for Inter-frequency and Inter-RAT

Measurements

OMC path



This parameter indicates the UTRAN measurement quantity (Ec/No or RSCP) for

inter-frequency and inter-RAT measurements. The measurement quantity RSCP is

recommended.

13.4.2.43 HCS_PRIO (UExternalGsmCell)

OMC path




This parameter indicates the HCS priority level of the GSM cell. 7 represents the highest

priority and 0 represents the lowest priority. A cell with a higher priority often provides a

smaller coverage and a cell with a lower priority often offers a larger coverage

IMSI-Based Handover Parameters

13.4.2.44 PS Inter-System Handover Indicator

OMC path




This parameter indicates whether RNC supports PS inter-RAT handover. 0 indicates not

support, 1 indicates support.



13.4.2.45 Inter-System DTM Support Indicator

OMC path




This parameter indicates whether the RNC supports DTM mode, that is, whether

supports inter-RAT handover both for CS domain services and PS domain services at the

same time. 0 indicates not support, 1 indicates support.

13.4.2.46 Neighboring BSC whether or not Supports PS Handover

OMC path

GUI: Managed Element->UMTS Logical Function Configuration->Link

Configuration->Iurg Link


This parameter indicates whether neighboring BSC supports PS service handover.

13.4.2.47 Neighboring BSC whether or not Supports DTM Handover

OMC path




This parameter indicates whether neighboring BSC supports DTM handover.

13.4.2.48 Loading Based InterSys HO Support Indicator

OMC path






This parameter indicates whether the target cell load information is taken into

consideration during the inter system handover procedure.

13.4.2.49 Duration of Valid Cell Load Info

OMC path



This parameter indicates the duration of inter-sys cell‟s load information which is valid to

use before updating.

13.4.2.50 GSM Uplink RT Load Threshold

OMC path




This parameter indicates the uplink overload threshold for RT service in GSM system.

13.4.2.51 GSM Downlink RT Load Threshold

OMC path






This parameter indicates the downlink overload threshold for RT service in GSM system.

13.4.2.52 GSM Uplink Load Threshold

OMC path




This parameter indicates the uplink overload threshold in GSM system.

13.4.2.53 GSM Downlink Load Threshold

OMC path




This parameter indicates the downlink overload threshold in GSM system.

13.4.2.54 Nacc Support Indicator

OMC path




This parameter indicates whether RNC supports NACC function or not.

13.4.2.55 Handover to GSM Penalty Timer

OMC path






When handover from UMTS to GSM is failed, the timer initiates, and RNC will not handle

inter-RAT measurement report until the timer expires.

13.4.2.56 Service-Based Handover Support Indicator

OMC path




This parameter indicates whether RNC supports handover based on service.

13.4.2.57 Service Handover Switch

OMC path




This parameter indicates whether service handover is allowed or not. When the “Service

Handover” IE is included in RAB assignment request, if the switch is open, RNC will

perform related process according to the value of “Service Handover” IE, otherwise RNC

will ignore the “Service Handover” IE.

13.4.2.58 Service Handover Combination Strategy

OMC path


Configuration->Handover Configuration Based on Service




This parameter indicates the service handover combination strategy in multi-RAB, and

RNC will perform related process according to the highest priority value of IE “service

handover”.

13.4.2.59 AMR Inter Rat Handover Switch

OMC path




This parameter indicates whether AMR inter-Rat handover is allowed or not.

13.4.2.60 R99 RT Inter Rat Handover Switch

OMC path




This parameter indicates whether R99 RT inter-Rat handover is allowed or not.

13.4.2.61 R99 NRT Inter Rat Handover Switch

OMC path




This parameter indicates whether R99 NRT inter-Rat handover is allowed or not.

13.4.2.62 HSDPA Inter Rat Handover Switch

OMC path






This parameter indicates whether HSDPA inter-Rat handover is allowed or not.

13.4.2.63 HSUPA Inter Rat Handover Switch

OMC path




This parameter indicates whether HSUPA inter-Rat handover is allowed or not.

13.4.2.64 Timer for Stopping Inter-frequency Measurement and Activating Inter-RAT

Measurement

OMCR Interface



This parameter indicates the time interval of issuing inter-frequency measurement and

inter-RAT measurement. When RNC issues inter-frequency measurement, the timer is

start. If the quality of non-used frequency is bad during the time length indicated by this

parameter, RNC will issue inter-RAT measurement if there is an inter-RAT neighboring

cell.

The larger the value is, the slower the inter-RAT measurement is initialized, and vice

versa.

13.4.2.65 Service Handover Strategy Indicator

OMCR Interface






This parameter indicates the service handover strategy controlled by RNC.

Bit=0/1: Ignore Service Handover IE for AMR Service/Apply Service handover IE for

AMR Service


OMCR Interface





Bit=0/1: Ignore Service handover IE for CS64 service/Apply Service Handover IE for

CS64 Service


OMCR Interface





Bit=0/1: Ignore Service Handover IE for PS RT Service/Apply Service Handover IE for

PS RT Service


OMCR Interface







Bit=0/1: Ignore Service Handover IE for PS NRT Service/Apply Service Handover for PS

NRT Service

13.4.2.69 Service Handover Strategy of RNC for AMR

OMCR Interface




This parameter indicates the service handover strategy for AMR.

0:should be performed(should be performed)

1:should not be performed(should not be performed)

2: shall not be performed(shall not be performed)

13.4.2.70 Service Handover Strategy of RNC for CS64

OMCR Interface




This parameter indicates the service handover strategy for CS64.






13.4.2.71 Service Handover Strategy of RNC for PS RT service

OMCR Interface




This parameter indicates the service handover strategy for PS RT service.




13.4.2.72 Service Handover Strategy of RNC for PS NRT service

OMCR Interface




This parameter indicates the service handover strategy for PS NRT service.




13.4.2.73 Maximum Time for Forwarding GTP-PDU Data in SRNC

OMC path






This parameter specifies the maximum time for GTP-PDU forwarding at the source RNC

during relocation of SRNS.

13.4.2.74 Waiting Timer for SRNS Context Request

OMCR Interface



This parameter indicates timer length waiting for SRNS CONTEXT REQUEST.

13.4.2.75 Waiting Timer for SRNS DATA FORWARD COMMAND

OMCR Interface



This parameter indicates timer length waiting for SRNS DATA FORWARD COMMAND.

13.4.2.76 Waiting Timer for IU RELEASE COMMAND

OMCR Interface



This parameter indicates timer length that waiting for IU RELEASE COMMAND.

13.4.2.77 UE Internal Measurement Configuration Index(UHoEvtTPUeInt)

OMC path



Transmitted Power Event Measurement Configuration for Handover-> the UE Internal

Measurement Configuration Index




This parameter indicates the UE internal measurement configuration index.


CONTROL RELEASE

OMC path











OMC path



The parameter indicates handover and cell reselection scenarios.

13.4.2.80 Whether Support Iur-g Signaling Procedure

OMC path






This parameter indicates whether adjacent BSC supports Iur-g signaling procedure.

13.4.2.81 The Waiting Timer for UE Handover When Board's Power is Off

OMC path



This parameter indicates timer length that waiting for UE handover when board‟s power

is off.

The value of this parameter is smaller, the time of turn off the power is shorter, and the

user experience is worse; the value of this parameter is larger, the time of turn off the

power is longer, and the user experience is better.

13.4.2.82 Mobility Configuration Scene(URatMeasProfile)

OMC path






13.4.2.83 UE Transmitted Power Threshold(UHoEvtTPUeInt)

OMC path







This parameter indicates the UE transmitted power threshold in event 6a/6b.

13.4.2.84 RNC Switch for Handover Based on UL BLER

OMC path


Handover Based on UL BLER


The parameter indicates the RNC switch for handover based on uplink BLER. When the

switch is "Off", the function is turned off; when the switch is "On", judge the cell switch

UlBlerHoSwch to decide whether the function is turned on.

13.4.2.85 RNC Switch for Handover Based on Tx Power

OMC path


Handover Based on Tx Power


The parameter indicates the RNC switch for handover based on transmit power. When

the switch is "Off", the function is turned off; when the switch is "On", judge the cell switch

UlPwrHoSwch/DlPwrHoSwch to decide whether the function is turned on.

13.4.2.86 Measurement Report Transfer Mode (UHoEvtTPUeInt)

OMC path







The parameter indicates the RLC mode of the UE internal measurement report.

13.4.2.87 Filter Coefficient (UHoEvtTPUeInt)

OMC path





The parameter indicates the filtering factor that the UE performs the L3 filtering on the


13.4.2.88 Maximum Event Number of UE Internal Measurement (UHoEvtTPUeInt)

OMC path





The parameter indicates the maximum event number of UE internal measurements.

13.4.2.89 UE Internal Measurement Event Identity (UHoEvtTPUeInt)

OMC path





The parameter indicates the UE internal measurement event identity.



13.4.2.90 Time to Trigger (ms) (UHoEvtTPUeInt)

OMC path





The parameter indicates the period of time during which the event condition has to be


13.4.2.91 Inter-rat Cell Inforamtion indication Strategy

OMC path



The parameter indicates whether to deal with the inter-RAT measurement report when

the value of “inter-rat cell info indication“ in inter-RAT measurement report reported by

the UE is different from that filled in measurement control message. The value is “1”, deal

with the report, the value is “0”, do not deal with the report.

13.4.2.92 Switch of RXLEV-NECELL indication in oldBSS_ToNewBSS

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Extended Info of RNC


The parameter is the switch of RXLEV-NECELL indication in oldBSS_ToNewBSS when

inter-system handover to GSM. When the switch is “On”, GSM can find the suitable

frequency according the RXLEV-NECELL information.



13.4.2.93 Dedicated Measurement Type

OMC path





This parameter indicates the type of dedicated measurement to be executed by Node B.

Configuration Rule: Dedicated measurement type should be chose according to the

usage of the dedicated measurement.

13.4.2.94 Measurement Change Time /Measurement Hysteresis Time

OMC path





For event A/B, this parameter is measurement hysteresis time and the measurement

hysteresis time provides the duration during which a reporting criterion has to be fulfilled

for the Measurement Reporting procedure to be triggered.


measurement.

The larger this parameter is, the more difficult to trigger the measurement event.

13.4.2.95 Measurement Filter Coefficient

OMC path







This parameter indicates the L3 filter coefficient.

The involved factor for setting this parameter: the smoothness and real-time of

measurement report value.

Influence of this parameter: the less of the value, the less fluctuate of the measurement

report value; the larger of the value, the more real-time of the measurement report value.

Suggestion for setting this parameter: not suggested to adjust.

13.4.2.96 Report Period

OMC path





This parameter indicates the frequency of measurement report transmitted by Node B.

Configuration Rule: According to the contribution to the system load and the timeliness of

the measurement report.

The larger the value, the more contribution to the system load but the less timely of the

measurement report; the smaller the value, the less contribution to the system load but

the timelier of the measurement report.

13.4.2.97 Choice Report Periodicity Scale

OMC path







This parameter indicates the time unit of measurement report transmitted by Node B.

Configuration Rule: According to the measurement period which is determined according

to the contribution to the system load and the timeliness of the measurement report.

13.4.2.98 Report Characteristics

OMC path





This parameter indicates the report characteristics of measurement results, which can be

on demand, periodic or by triggering all kinds of events.


measurement.

13.4.2.99 Measurement Threshold of Event A/B for Transmitted Code Power

OMC path







The parameter indicates the power offset of the DPCH maximum DL power, which

defines which threshold that shall trigger event A, B for transmitted carrier power

measurement.

This parameter is a ternary array, which is fixed to the first element evtAbTcpThrd[0] for

handover control.

13.4.2.100 NbDed Measure Configuration No

OMC path





This parameter indicates the NbDed Measure Configuration Number.

13.5 EUTARN Inter-RAT Handover Parameters



1. Thresh(URatEcNoEvMeasfor

E)

Absolute Threshold of the Quality of UTRAN

Cell for 3A

2. Thresh(\URatRscpEvMeasfor

E)

Absolute Threshold of the Quality of UTRAN

Cell for 3A

3. W(URatEcNoEvMeasforE) Weight of the UTRAN System for 3A

4. W(\URatRscpEvMeasforE) Weight of the UTRAN System for 3A

5. ThreshSys(URatEcNoEvMea

sforE)

Absolute Threshold of the Quality of Other

RAT for 3A/3B/3C

6. ThreshSys(\URatRscpEvMea

sforE)

Absolute Threshold of the Quality of Other

RAT for 3A/3B/3C



7. hysteresis(URatEcNoEvMea

sforE) Hysteresis

8. hysteresis(\URatRscpEvMea

sforE) Hysteresis

9. TrigTime(URatEcNoEvMeasf

orE) Time to Trigger

10. TrigTime(\URatRscpEvMeasf

orE) Time to Trigger

11. InterRatCfgNo(URatEcNoEv

MeasforE) Inter-RAT Measurement Configuration Index

12. InterRatCfgNo(URatRscpEv

MeasforE) Inter-RAT Measurement Configuration Index

13. FilterCoeff(URatEcNoEvMea

sforE UTRAN Filter Coefficient

14. FilterCoeff(URatRscpEvMea

sforE) UTRAN Filter Coefficient

15. EventNum(URatEcNoEvMea

sforE) Inter-RAT Measurement Event Number

16. EventNum(\URatRscpEvMea

sforE) Inter-RAT Measurement Event Number

17. EventId

[MAX_RAT_MEAS_EVENT]

(URatEcNoEvMeasforE)


18. EventId

[MAX_RAT_MEAS_EVENT]

(\URatRscpEvMeasforE)


19. ChoStraMulRatHo Choice Strategy in Multi-RAT Handover

20. RncPsHoLteSw RNC Switch for PS Handover with LTE

21. r99RtEutraHoSw

R99 RT Inter Rat(EUTRAN) Handover

Switch

22. r99NrtEtraHoSw

R99 NRT Inter Rat(EUTRAN) Handover

Switch

23. hsdpaEutraHoSw

HSDPA Inter Rat(EUTRAN) Handover

Switch

24. hsupaEutraHoSw

HSUPA Inter Rat(EUTRAN) Handover

Switch



25. RncSrvccSw RNC SRVCC Switch

26. eUtranFilterCoeff(URatEcNo

EvMeasforE)

EUTRAN Filter Coefficient

27. eUtranFilterCoeff(URatEcNo

PrdMeas)


28. eUtranFilterCoeff(URatRscp

EvMeasforE)


29. eUtranFilterCoeff(URatRscp

PrdMeas)


30. PSL2USWCHBYCS

Switch of Permit PS Handover from LTE to

UTRAN Because of CSFB

31. EutranNMeasBand(UExterna

lEUtranCellFDD)

EUTRAN Measurement Bandwidth

32. EutranNMeasBand(UExterna

lEUtranCellTDD)

EUTRAN Measurement Bandwidth

33. CelReturnLteSwch Cell Switch of Fast Return to EUTRAN

34. fastRetEUtranSwch RNC Switch of Fast Return to E-UTRAN

35. UtraSISwitch UTRA SI Switch

36. EutranNCblstSwch Switch of support the EUTRAN nbr blacklist

37. StateMode(UENbrBlkList)

UE State Indicator Used for Blacklist Cell

Configuration

38. LdBsdEutranHOInd

Loading based InterSys HO Support

Indicator

39. EutranDlLdThrd EUTRAN Downlink Load Threshold

40. EutranUlLdThrd EUTRAN Uplink Load Threshold

41. EutraDetectionInd E-UTRA Detection Indicator

42. IndoorCellInd Indoor Cell Indicator

43. HoToEutraPenTimer Handover to E-UTRAN Penalty Timer

44. sonTransReqPeriod The period of RNC starting the SON Transfer

45. sonTransReqNumThrd

Son Transfer Request Number Threshold in

one second

46. sonTransRespSwitch Son Transfer Response Switch

47. sonTransRespNumThrd

Response the Son Transfer message

Number Threshold in one second

48. LteCellIdenFlag Method of Identify EUTRAN cell



49.

MulSrvRePsHoLteSw

Switch of PS Service Fast Return to

EUTRAN when CS is released for Multi-RAB

Service

50. EutranPsHoMode PS Handover to EUTRAN Mode

51. PsHoLteMeasTimer

Timer of Deactivate Compressed Mode for

Fast Return to EUTRAN

52.

SimCompUserNum

User Number with Compressed Mode

Activation for Balance Strategy Based On

Measurement


54. CresPara7 Cell Reserved Parameter 7


56. PsSigForImsInd PS Signalling RAB for IMS Support Indicator

57. EutranFreqBandInd EUTRAN Frequency Band Indicator

58.

earfcnDl

Downlink EUTRAN Absolute Radio

Frequency Channel Number

59.

NEutranNum

EUTRAN blacklist Neighboring Cell Number

in specific Frequency

60. NeutranCId Physical EUTRAN Cell Identity



3A(URatEcNoEvMeasforE)

OMC path




Inter-RAT Event Measurement Configuration for CPICH Ec/No(EUTRAN)









3A(URatRscpEvMeasforE)

OMC path




Inter-RAT Event Measurement Configuration for CPICH RSCP(EUTRAN)






13.5.2.3 Weight of the UTRAN System for 3A(URatEcNoEvMeasforE)

OMC path












13.5.2.4 Weight of the UTRAN System for 3A(URatRscpEvMeasforE)

OMC path











3A/3B/3C(URatEcNoEvMeasforE)

OMC path














The larger the value configured, the more difficult event 3a/3b/3c be reported.


3A/3B/3C(URatRscpEvMeasforE)

OMC path












The larger the value configured, the more difficult event 3a/3b/3c be reported.

13.5.2.7 Hysteresis (URatEcNoEvMeasforE)

OMC path












and vice versa.

13.5.2.8 Hysteresis(URatRscpEvMeasforE)

OMC path










and vice versa.

13.5.2.9 Time to Trigger (URatEcNoEvMeasforE)

OMC path














13.5.2.10 Time to Trigger(URatRscpEvMeasforE)

OMC path












13.5.2.11 Inter-RAT Measurement Configuration Index(URatEcNoEvMeasforE)

OMC path


















network planning.

13.5.2.12 Inter-RAT Measurement Configuration Index(URatRscpEvMeasforE)

OMC path
















network planning.



13.5.2.13 UTRAN Filter Coefficient (URatEcNoEvMeasforE)

OMC path









13.5.2.14 UTRAN Filter Coefficient(URatRscpEvMeasforE)

OMC path









13.5.2.15 Inter-RAT Measurement Event Number(URatEcNoEvMeasforE)

OMC path










13.5.2.16 Inter-RAT Measurement Event Number(URatRscpEvMeasforE)

OMC path








13.5.2.17 Inter-RAT Event Identity(URatEcNoEvMeasforE)

OMC path








13.5.2.18 Inter-RAT Event Identity(URatRscpEvMeasforE)

OMC path










13.5.2.19 Choice Strategy in Multi-RAT Handover

OMC path




This parameter indicates which inter-RAT will be selected in priority for handover in

multi-RAT scenario.

13.5.2.20 RNC Switch for PS Handover with LTE

OMC path




The parameter indicates whether RNC support PS handover with LTE.

13.5.2.21 R99 RT Inter Rat(EUTRAN) Handover Switch

OMC path






This parameter indicates whether R99 RT inter-Rat handover to EUTRAN allowed or not.

13.5.2.22 R99 NRT Inter Rat(EUTRAN) Handover Switch

OMC path




This parameter indicates whether R99 NRT inter-Rat handover to EUTRAN allowed or

not.

13.5.2.23 HSDPA Inter Rat(EUTRAN) Handover Switch

OMC path




This parameter indicates whether HSDPA inter-Rat handover to EUTRAN allowed or not.

13.5.2.24 HSUPA Inter Rat(EUTRAN) Handover Switch

OMC path




This parameter indicates whether HSUPA inter-Rat handover to EUTRAN allowed or not.

13.5.2.25 RNC SRVCC Switch

OMC path






The parameter indicates whether RNC support SRVCC.

13.5.2.26 EUTRAN Filter Coefficient(URatEcNoEvMeasforE)

OMC path






This parameter indicates the value of the filtering factor is when the UE executes an LTE

measurement.

13.5.2.27 EUTRAN Filter Coefficient(URatEcNoPrdMeas)

OMC path







measurement.

13.5.2.28 EUTRAN Filter Coefficient(URatRscpEvMeasforE)

OMC path









measurement.

13.5.2.29 EUTRAN Filter Coefficient(URatRscpPrdMeas)

OMC path







measurement.

13.5.2.30 PSL2USWCHBYCS

OMC path




This parameter indicates is the switch of permit PS handover from LTE to UTRAN

because of CSFB.

13.5.2.31 EUTRAN Measurement Bandwidth(UExternalEUtranCellFDD)

OMC path




Configuration->External ENodeB Function->External EUTRAN Cell FDD


This parameter indicates is the maximum bandwidth allowed to measure on the single

frequency of EUTRAN in inter-RAT measurement.

13.5.2.32 EUTRAN Measurement Bandwidth(UExternalEUtranCellFDD)

OMC path


Configuration->External ENodeB Function->External EUTRAN Cell TDD


This parameter indicates is the maximum bandwidth allowed to measure on the single

frequency of EUTRAN in inter-RAT measurement.

13.5.2.33 Cell Switch of Fast Return to EUTRAN

OMC path



This parameter indicates cell switch of fast return to EUTRAN for CS service based on

the EUTRAN CSFB.

13.5.2.34 RNC Switch of Fast Return to E-UTRAN

OMC path





This parameter is a RNC switch, which indicates whether to enable the function of fast

return to EUTRAN or not.

13.5.2.35 UTRA SI Switch

OMC path



This parameter indicates whether RNC supports the UTRA SI function of RIM.

13.5.2.36 Switch of support the EUTRAN nbr blacklist

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN Cell->Switch

of support the EUTRAN Neighbouring cell blacklist


The parameter indicates cell switch of support the EUTRAN nbr blacklist.

13.5.2.37 UE State Indicator Used for Blacklist Cell Configuration

OMC path


Cell->Adjacent Relation Configuration->EUTRAN Neighbouring Cell Black List->UE

State Indicator Used for Blacklist Cell Configuration


The parameter indicates UE state which RNC can configure the EUTRAN nbr blacklist in

accordance with.

There are two kinds of UE state: 0, Cell Selection/Reselection; 1, Handover.



13.5.2.38 Loading based InterSys HO Support Indicator

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Loading based

InterSys HO Support Indicator


The parameter indicates if consider the target cell load Information during the inter

system handover procedure.

13.5.2.39 EUTRAN Downlink Load Threshold

OMC path


Configuration->External ENodeB Function->External EUTRAN Cell FDD->EUTRAN

Downlink Load Threshold


The parameter indicates the downlink overload threshold in the EUTRAN system.

13.5.2.40 EUTRAN Uplink Load Threshold

OMC path


Configuration->External ENodeB Function->External EUTRAN Cell FDD->EUTRAN

Uplink Load Threshold


The parameter indicates the uplink overload threshold in the EUTRAN system.



13.5.2.41 E-UTRA Detection Indicator

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->UTRAN Cell->Cell

Reselection Frequency and Priority Information->E-UTRA Detection Indicator


The parameter is the E-UTRA detection indicator. If this indicator exists and is set to

TRUE, and the UE is in CELL_PCH, URA_PCH state or idle mode, the UE may detect

the presence of an E-UTRA cell on a frequency with a priority lower than the current

UTRA cell and report the information to the NAS.

13.5.2.42 Indoor Cell Indicator

OMC path


Configuration->External GSM Cell->Indoor Cell Indicator


The parameter indicates whether the cell is indoor cell or not.

13.5.2.43 Handover to E-UTRAN Penalty Timer

OMC path


Configuration->Logic RNC Configuration->Handover to E-UTRAN Penalty Timer


When handover from UMTS to LTE is failed, the timer initiates, and RNC will not handle

inter-RAT measurement report until the timer expires.



The parameter is larger, next handover interval is longer, which may increase call-drop

possibility due to worsening quality. The parameter is smaller, next handover interval is

shorter and handover attempt is more frequent, which will occupy more system resource.

13.5.2.44 The period of RNC starting the SON Transfer

OMC path



The parameter indicates the period of RNC starting the SON Transfer.

13.5.2.45 Son Transfer Request Number Threshold in one second

OMC path



The parameter indicates Son Transfer Request Number Threshold in one second, is

used for controlling volume of messages.

13.5.2.46 Son Transfer Response Switch

OMC path



The parameter is the switch of response the LTE Son Transfer request.

13.5.2.47 Response the Son Transfer message Number Threshold in one second

OMC path





The parameter indicates Response the Son Transfer message Number Threshold in one

second, is used for controlling volume of messages.

13.5.2.48 Method of Identify EUTRAN cell

OMC path


Configuration->Iups Link


The parameter indicates the Method of Identify EUTRAN cell. If SGSN do not recognize

eNodeBID of EUTRAN CELL, RNCID/LAC/RAC should be used for EUTRAN CELL, and

this parameter should be set as 1, otherwise 0.

13.5.2.49 Switch of PS Service Fast Return to EUTRAN when CS is released for

Multi-RAB Service

OMC path

GUI: View-> UMTS Logical Function Configuration->UTRAN Cell->Extended Info of

UTRAN Cell


The parameter indicates whether EUTRAN compressed mode and measurement are

initialized for PS service to provide service fast return to EUTRAN as soon as possible or

redirection to EUTRAN without measurement when CS service is released for Multi-RAB

with CSFB from EUTRAN.

13.5.2.50 PS Handover to EUTRAN Mode

OMC path





This parameter indicates PS Handover Mode when CS is released for EUTRAN CSFB

Multi-RAB Service. PS handover or redirection can be used based on the UE capability.

13.5.2.51 Timer of Deactivate Compressed Mode for Fast Return to EUTRAN

OMC path



The parameter indicates timer of deactivate compressed mode for Fast Return to

EUTRAN. If compressed mode is initialized due to fast return to EUTRAN, the timer

activates. When the timer expires, if event(3C) doesn‟t report, RNC will judge whether

compressed mode is deactivate or not based on current signal quality.

13.5.2.52 User Number with Compressed Mode Activation for Balance Strategy

Based On Measurement

OMC path

GUI: View-> UMTS Logical Function Configuration->UTRAN Cell->Extended Info of

UTRAN Cell


This parameter will be used for deciding how many users are allowed to activate the

compressed mode for Balance Strategy Based on Measurement simultaneously.


OMC path




Parameter 52


Bit10: This parameter indicates PS Handover Mode when CS is released for EUTRAN

SRVCC Multi-RAB Service. PS handover or redirection can be used based on UE

capability.

Bit11: This parameter is the switch of checking the UE E-UTRA Capability before

initiating the PS handover procedure from UMTS to LTE.


OMC path


Cell->Extended Info of UTRAN Cell-> Cell Reserved Parameter 7


Bit0~Bit1: When CS service is released for Multi-RAB with SRVCC from EUTRAN, the

parameter indicates whether EUTRAN compressed mode and measurement are

initialized for PS service to provide service fast return to EUTRAN as soon as possible or

redirection to EUTRAN without measurement.

Bit2: This parameter indicates cell switch of fast return to EUTRAN for CS service based

on the EUTRAN SRVCC.


OMC path


Parameter 7




When pre-redirection information is not indicated in RRC Connection Request, if the time

between RRC Connection Request and CS RAB establish is not greater than this

parameter, the service is indicated CSFB.

13.5.2.56 PS Signalling RAB for IMS Support Indicator

OMC path


Configuration->Logic RNC Configuration->PS Signalling RAB for IMS Support Indicator


This parameter indicates if RNC supports PS Signalling RAB for IMS.

13.5.2.57 EUTRAN Frequency Band Indicator

OMC path


Cell->Adjacent Relation Configuration->EUTRAN Neighbouring Cell Black

List->EUTRAN Frequency Band Indicator


This parameter indicates the frequency band of the EUTRAN.

13.5.2.58 Downlink EUTRAN Absolute Radio Frequency Channel Number

OMC path



List->Downlink EUTRAN Absolute Radio Frequency Channel Number


The parameter indicates the downlink E-UTRAN Absolute Radio Frequency Channel

Number (EARFCN).



13.5.2.59 EUTRAN blacklist Neighboring Cell Number in specific Frequency

OMC path



List->EUTRAN blacklist Neighboring Cell Number in specific Frequency


Number of EUTRAN Neighboring blacklist per frequency.

13.5.2.60 Physical EUTRAN Cell Identity

OMC path


Cell->Adjacent Relation Configuration->EUTRAN Neighbouring Cell Black List->Physical

EUTRAN Cell Identity


The parameter is used to identify an EUTRAN physical cell. There are 504 unique physical-layer

cell identities. The physical-layer cell identities are grouped into 168 unique physical-layer

cell-identity groups, each group containing three unique identities.

13.6 IMSI-based Handover Parameters



1. BasedImsiHoInd Handover Based on IMSI Support

2. MCC(UImsiSnacFilter) MCC

3. MNC(UImsiSnacFilter) MNC

4. imsiMatchedDgtNum The Imsi Matched Digits Num

5. imsiMatchedDigit The Imsi Matched Digit

6. SMCC MCC of Shared Network

7. SMNC MNC of Shared Network



8. SNAC Shared Network Area Code

9. MCC(USnac) MCC

10. MNC(USnac) MNC

11. LAC(USnac) Location Area Code

12. SNAC(USnac) Shared Network Area Code

13. MCC(UUtranCellFDD) Mobile Country Code

14. MCC(UExternalUtranCellF

DD) Mobile Country Code

15. MCC(UExternalGsmCell)

Mobile Country Code of Neighbouring

GSM Cell

16. MNC(UUtranCellFDD) Mobile Network Code

17. MNC(UExternalUtranCellF

DD) Mobile Network Code

18. MNC(UExternalGsmCell)

Mobile Network Code of Neighbouring

GSM Cell

19. LAC(UUtranCellFDD) Location Area Code

20. LAC(UExternalUtranCellF

DD) Location Area Code

21. SNAC[MAX_NUM_SNAC_

PER_UTRANCEL]( UExter

nalUtranCellFDD)

Shared Network Area Code

22. SNACNum(UExternalUtra

nCellFDD) Shared Network Area Code Number

23. SNAC[MAX_NUM_SNAC_

PER_GSMCEL]( UExternal

GsmCell)

Shared Network Area Code

24. SNACNum(UExternalGsm

Cell) Shared Network Area Code Number


13.6.2.1 Handover Based on IMSI Support

OMC path






This parameter indicates whether RNC supports handover based IMSI or not.

13.6.2.2 MCC(UImsiSnacFilter)

OMC path

GUI: Managed Element ->UMTS Logical Function Configuration->Global Information

Configuration->User Authorized PLMN+SNAC Information


This parameter indicates the mobile country code (MCC) of the IMSI card. See 0 in the

text for the use case.

13.6.2.3 MNC(UImsiSnacFilter)

OMC path




This parameter indicates the mobile network code (MNC) of the IMSI card. See 0 in the


13.6.2.4 The Imsi Matched Digits Num

OMC path






The parameter indicates the number of IMSI digit, the maximum value of which is 15.

13.6.2.5 The Imsi Matched Digit

OMC path




The parameter indicates the digit of IMSI, including MCC, MNC and extend information.

13.6.2.6 MCC of Shared Network

OMC path




The parameter indicates the MCC of the shared network, namely the MCC of the target

location area code (LAC) that the handover is allowed in.

13.6.2.7 MNC of Shared Network

OMC path




The parameter indicates the MNC of the shared network, namely the MNC of the target

LAC that the handover is allowed in.



13.6.2.8 Shared Network Area Code

OMC path




This parameter indicates the shared network area code (SNAC). It is defined by the

customer.

13.6.2.9 MCC(USnac)

OMC path


Configuration->LAC and SNAC Information


This parameter in combination with parameters MNC(USnac), LAC(USnac), and

SNAC(USnac) specifies a target area code that the handover is allowed in. See 0 in the


13.6.2.10 MNC(USnac)

OMC path




This parameter in combination with parameters MCC(USnac), LAC(USnac), and





13.6.2.11 Location Area Code(USnac)

OMC path




This parameter in combination with parameters MCC(USnac), MNC(USnac), and



13.6.2.12 Shared Network Area Code(USnac)

OMC path




This parameter in combination with parameters MCC(USnac), MNC(USnac), and

LAC(USnac) specifies a target area code that the handover is allowed in. See 0 in the


13.6.2.13 Mobile Country Code(UUtranCellFDD)

OMC path


Configuration->Logic Cell Configuration


This parameter indicates the MCC of the cells in the RNC.



13.6.2.14 Mobile Country Code(UExternalUtranCellFDD)

OMC path




This parameter indicates the MCC of UTRAN cells that do not belong to the RNC.

13.6.2.15 Mobile Country Code(UExternalGsmCell)

OMC path




This parameter indicates in the MCC of the GSM cells.

13.6.2.16 Mobile Network Code(UUtranCellFDD)

OMC path


Configuration->Logic Cell Configuration


This parameter indicates the MNC of the cells in the RNC.

13.6.2.17 Mobile Network Code(UExternalUtranCellFDD)

OMC path






This parameter indicates the MNC of the cells that do not belong to the RNC.

13.6.2.18 Mobile Network Code(UExternalGsmCell)

OMC path




This parameter indicates in the MNC of the GSM cells.

13.6.2.19 Location Area Code(UUtranCellFDD)

OMC path



This parameter indicates the LAC of the cells in the RNC.

13.6.2.20 Location Area Code(UExternalUtranCellFDD)

OMCR Interface




This parameter indicates the LAC of UTRAN cells that do not belong to the RNC.

13.6.2.21 Shared Network Area Code(UExternalUtranCellFDD)

OMC path






This parameter indicates the shared network area code that the neighboring cell belongs

to. One cell can belong to at most four SNACs (shared network area code).

13.6.2.22 Shared Network Area Code Number(UExternalUtranCellFDD)

OMC path




This parameter indicates the number of shared network area code that the neighboring

cell belongs to.

13.6.2.23 Shared Network Area Code(UExternalGsmCell)

OMC path




This parameter indicates the shared network area code that the neighboring cell belongs

to. One cell can belong to at most four SNACs (shared network area code).

13.6.2.24 Shared Network Area Code Number(UExternalGsmCell)

OMC path






This parameter indicates the number of shared network area code that the neighboring

cell belongs to.

13.7 HSDPA Handover Parameters



1. HspaSptMeth(UUtranCellFD

D) HSPA Support Method

2. T1d Timer for Event 1D in HSPA or MBMS


NotSupport/Support HSDPA Iur Interface

Process

4. HsdpaCmAssoMode HSDPA Associate CM Method

5. HspaSptMeth(UExternalUtra

nCellFDD) HSPA Support Method


13.7.2.1 HSPA Support Method(UUtranCellFDD)

OMC path



This parameter indicates the support for various types of cells.

13.7.2.2 Timer for Event 1D in HSPA or MBMS

OMC path




Configuration->Hspa Configuration


For HSPA, this parameter indicates the minimum interval required for the change of the

HSPA serving cell or the transition between the HS and DCH channels. A large value of

this parameter helps to avoid too frequent HSPA serving cell change and channel

transition.

13.7.2.3 NotSupport/Support HSDPA Iur Interface Process

OMC path


Link


This parameter indicates whether the IUR interface supports the HSDPA feature.

13.7.2.4 HSDPA Associate CM Method

OMCR Interface




This parameter indicates the association between HSDPA and CM method.

The value “Serial” means HSDPA service will be reconfigured to DCH cannel before the

compress mode is activated.;

The default value is parallel.



13.7.2.5 HSPA Support Method(UExternalUtranCellFDD)

OMC path





13.8 HSUPA Handover Parameters



1. HspaSptMeth(UUtranCellFDD) HSPA Support Method


NotSupport/Support HSUPA Iur

Interface Process

3. HsupaCmAssoMode HSUPA Associate CM Method

4. HspaSptMeth(UExternalUtran

CellFDD) HSPA Support Method


13.8.2.1 HSPA Support Method(UUtranCellFDD)

OMC path






13.8.2.2 NotSupport/Support HSUPA Iur Interface Process

OMC path


Link


This parameter indicates whether the IUR interface supports the HSUPA feature.

13.8.2.3 HSUPA Associate CM Method

OMCR Interface




This parameter indicates the association between HSUPA and CM method.

The value “Serial” means HSUPA service will be reconfigured to DCH cannel before the

compress mode is activated.;

The default value is serial.

13.8.2.4 HSPA Support Method(UExternalUtranCellFDD)

OMC path







13.9 MBMS Handover Parameters



1. MbmsSuptInd MBMS Support Indicator

2. T1d Timer for Event 1D in HSPA or MBMS


13.9.2.1 MBMS Support Indicator

OMC path



This parameter indicates whether to support the MBMS. When the parameter is set to 0

(Not Support), the cell does not support the MBMS service.

When the parameter is set to 1 (Support MBMS and not MBMS), the cell supports both

the MBMS service and the mixed R99, R5, and R6 service. In this case, the cell can

either use a separate carrier frequency for establishing the co-coverage relationship or

HSC structure with other cells, or use the same carrier frequency as the neighboring cell.

When the parameter is set to 2 (Only Support MBMS), the cell supports only the MBMS

service. In this case, non-S-CCPCHs can neither be allocated separately for users nor

exist as the DCH channel of the concurrent service. The purpose of such a cell is to

share the load of the MBMS service.

13.9.2.2 Timer for Event 1D in HSPA or MBMS

OMC path






For HSPA, this parameter indicates the minimum interval required for the change of the

HSPA serving cell or the transition between the HS and DCH channels. A large value of

this parameter helps to avoid too frequent HSPA serving cell change and channel

transition.

For MBMS, this parameter indicates the minimum interval required for changing the best

cell of the MBMS service for two times caused by event 1d. This parameter helps to

avoid too frequent change between the PTP and PTM bearer types.

14 Counter and Alarm

14.1 Counter List

14.1.1 RNC Soft Handover Statistics

Counter No. Description

C310322211

Statistics of soft handover prepare

C310322212

C310322213

C310322214

C310322215

C310322216

Number of active set update attempted to add cell, by procedure C310322217

C310322218

C310322219

Number of active set update failed to add cell, by procedure C310322220

C310322221

C310322222

Number of active set update failed to add cell, by cause C310322223

C310322224

C310322225



C310322226

C310322227

C310322228

C310322229

C310322230

C310322231

C310322232

Number of active set update attempted to delete cell, by procedure C310322233

C310322234

C310326690

Number of active set update failed to delete cell ,by procedure C310326691

C310326692

C310322235

Number of active set update failed to delete cell, by cause

C310322236

C310322237

C310322238

C310322239

C310322240

C310322241

C310322242

C310322243

C310322244

C310322245

Number of active set update attempted to add cell, by traffic class C310322246

C310322247

C310322248

C310322249

Number of active set update failed to add cell, by traffic class C310322250

C310322251

C310322252

C310322253 Number of active set update attempted to delete cell, by traffic class

C310322254



C310322255

C310322256

C310322257

Number of active set update failed to delete cell, by traffic class C310322258

C310322259

C310322260

C310322261

Number of active set update attempted to add cell, by traffic class in

DCH

C310322262

C310322263

C310322264

C310322265

C310322266

C310322267

C310322268

C310322269

Number of active set update failed to add cell, by traffic class in DCH

C310322270

C310322271

C310322272

C310322273

C310322274

C310322275

C310322276

C310322277

Number of active set update attempted to delete cell, by traffic class in

DCH

C310322278

C310322279

C310322280

C310322281

C310322282

C310322283

C310322284

C310322285 Number of active set update failed to delete cell, by traffic class in

DCH C310322286



C310322287

C310322288

C310322289

C310322290

C310322291

C310322292

C310322293

Statistics of active set update for HS-DSCH C310322294

C310322295

C310322296

C310322297

Number of active set update attempted to add cell for E-DCH, by

procedure C310322298

C310322299

C310322300

Number of active set update failed to add cell for E-DCH, by


C310322302

C310322303

Number of active set update failed to add cell for E-DCH, by cause

C310322304

C310322305

C310322306

C310322307

C310322308

C310322309

C310322310

C310322311

C310322312

C310322313

Number of active set update attempted to delete cell for E-DCH, by


C310322315

C310322316

Number of active set update failed to delete cell for E-DCH, by cause

C310322317

C310322318



C310322319

C310322320

C310322321

C310322322

C310322323

C310322324

C310322325

C310322326

Number of active set update attempted to add cell for E-DCH, by

traffic class

C310322327

C310322328

C310322329

C310322330

Number of active set update failed to delete cell for E-DCH, by traffic

class

C310322331

C310322332

C310322333

C310322334

Number of active set update attempted to delete cell for E-DCH, by

traffic class

C310322335

C310322336

C310322337

C310322338

Number of active set update failed to delete cell for E-DCH, by traffic

class

C310322339

C310322340

C310322341

C310322342

Number of active set update for attempted add cell with multi-traffic C310322343

C310322344

C310322345

Number of active set update for failed add cell with multi-traffic C310322346

C310322347

C310322348 Soft handover ratio

C310322349

C310322350



C310322351

C310322352

C310322353

C310322354

C310322355

C310322356

C310322357

C310322358

C310322359

C310322360

C310322361

Soft handover rate of E-DCH user C310322362

C310322363

C310322364

C310322379

Number of UE having DCH active set cell in cell

Number of UE having DCH active set cell in cell

C310322380

C310322381

C310322382

C310322383

C310322384

C310322385

C310322386

C310322387

C310322388

C310322389

C310322390

C310322391

C310322392

C310322393

C310322394

C310322395

C310322396



C310322397

C310322398

C310322399

C310322400

C310322401

C310322402

C310322403

C310322404

C310322405

C310322406

C310322407

C310322408

C310322409

C310322410

C310322475

Number of UE having E-DCH active set cell in cell

C310322476

C310322477

C310322478

C310322479

C310322480

C310322481

C310322482

C310322483

C310322484

C310322485

C310322486

C310322487

Statistics of active set update, by traffic

C310322488

C310322489

C310322490

C310322491

C310322492



C310322493

C310322494

C310322495

Statistics of active set update, by domain

C310322496

C310322497

C310322498

C310322499

C310322500

C310322501

C310322502

14.1.2 RNC Hard Handover Statistics


C310336836

Number of hard handover preparation statistics

C310336837

C310336838

C310336839

C310336840

C310336841

C310336842

C310336843

C310336844

C310336845

C310336846

C310336847

C310336848

C310336849

C310336850

C310336851

C310336852

C310336853

C310336854



C310336855

C310336856

C310336857

C310336858

C310336859

C310336860

C310336861

C310336862

C310336863

C310336864

C310336865

C310332503

Number of intra-Node B hard handover statistics

C310332504

C310332505

C310332506

C310332507

C310332508

C310332509

C310332510

C310332511

C310332512

C310332513

C310332514

C310332515

C310332516

C310332517

C310332518

C310332519

C310332520

C310332521

C310332522

C310332523



C310332524

C310332525

Number of inter-Node B hard handover statistics

C310332526

C310332527

C310332528

C310332529

C310332530

C310332531

C310332532

C310332533

C310332534

C310332535

C310332536

C310332537

C310332538

C310332539

C310332540

C310332541

C310332542

C310332543

C310332544

C310332545

C310332546

C310332547

Number of SRNC Iur hard handover statistics

C310332548

C310332549

C310332550

C310332551

C310332552

C310332553

C310332554

C310332555



C310332556

C310332557

C310332558

C310332559

C310332560

C310332561

C310332562

C310332563

C310332564

C310332565

C310332566

C310332567

C310332568

C310332569

Number of SRNC Iur hard handover statistics, by channel type

C310332570

C310332571

C310332572

C310332573

C310332574

C310332575

C310332576

C310332577

C310332578

C310332579

C310332580

C310332581

C310332582

C310332583

C310332584

C310332585

C310332586

C310332587



C310332588

C310332589

C310332590

C310332591

C310332592

C310332593

C310332594

C310332595

C310332596

C310332597

Number of hard handover statistics, by source cause

C310332598

C310332599

C310332600

C310332601

C310332602

C310332603

C310332604

C310335701

Number of hard handover statistics,by inner source cause

C310335702

C310335703

C310335704

C310335705

C310335706

C310335707

C310335708

C310335738

C310332605

Number of CS hard handover statistics, by measurement quality

C310332606

C310332607

C310332608

C310332609

C310332610



C310332611

C310332612

C310332613

C310332614

C310332615

C310332616

C310332617

C310332618

C310332619

C310332620

C310332621

C310332622

C310332623

C310332624

C310332625

C310332626

C310332627

Number of PS hard handover statistics, by measurement quality

C310332628

C310332629

C310332630

C310332631

C310332632

C310332633

C310332634

C310332635

C310332636

C310332637

C310332638

C310332639

C310332640

C310332641

C310332642



C310332643

C310332644

C310332645

C310332646

C310332647

C310332648

C310332649

Number of hard handover statistics, by traffic class

C310332650

C310332651

C310332652

C310332653

C310332654

C310332655

C310332656

C310332657

C310332658

C310332659

C310332660

C310332661

C310332662

C310332663

C310332664

C310332665

Number of hard handover statistics, by domain

C310332666

C310332667

C310332668

C310332669

C310332670

C310332671

C310332672

C310336605

C310336606



C310336607

C310336608

C310336609

C310336610

C310336611

C310336612

C310336613

C310336614

C310336615

C310336616

C310336617

C310336618

C310336619

C310336620

C310332673

Number of intra-RNC hard handover statistics, by channel type

C310332674

C310332675

C310332676

C310332677

C310332678

C310332679

C310332680

C310332681

C310332682

C310332683

C310332684

C310332685

C310332686

C310332687

C310332688

C310332689

C310332690



C310332691

C310332692

C310332693

C310332694

C310332695

C310332696

C310332697

C310332698

C310332699

C310332700

C310336076

Statistics of hard handover outgoing by siganlling

C310336077

C310336078

C310336079

C310336080

C310336081

C310336082

C310336083

C310336084

C310336085

C310336086

C310336087


C310336088

C310336089

C310336090

C310336091

C310336092

C310336093

C310336094

C310336095

C310336096

C310336097



C310336098


C310336099

C310336100

C310336101

C310336102

C310336103

C310336104

C310336105

C310336106

C310336107

C310336108

C310336109


C310336110

C310336111

C310336112

C310336113

C310336114

C310336115

C310336116

C310336117

C310336118

C310336119

C310336120


C310336121

C310336122

C310336123

C310336124

C310336125

C310336126

C310336127

C310336128

C310336129



C310336130

C310336131


C310336132

C310336133

C310336134

C310336135

C310336136

C310336137

C310336138

C310336139

C310336140

C310336141

C310336142


C310336143

C310336144

C310336145

C310336146

C310336147

C310336148

C310336149

C310336150

C310336151

C310336152

C310336153


C310336154

C310336155

C310336156

C310336157

C310336158

C310336159

C310336160

C310336161



C310336162

C310336163

C310336164


C310336165

C310336166

C310336167

C310336168

C310336169

C310336170

C310336171

C310336172

C310336173

C310336174

C310336175


C310336176

C310336177

C310336178

C310336179

C310336180

C310336181

C310336182

C310336183

C310336184

C310336185

C310336186


C310336187

C310336188

C310336189

C310336190

C310336191

C310336192

C310336193



C310336194

C310336195

C310336196

C310336197


C310336198

C310336199

C310336200

C310336201

C310336202

C310336203

C310336204

C310336205

C310336206

C310336207

C310336208


C310336209

C310336210

C310336211

C310336212

C310336213

C310336214

C310336215

C310336216

C310336217

C310336218

C310336219


C310336220

C310336221

C310336222

C310336223

C310336224

C310336225



C310336226

C310336227

C310336228

C310336229

C310336230


C310336231

C310336232

C310336233

C310336234

C310336235

C310336236

C310336237

C310336238

C310336239

C310336240

C310336241


C310336242

C310336243

C310336244

C310336245

C310336246

C310336247

C310336248

C310336249

C310336250

C310336251

C310336252


C310336253

C310336254

C310336255

C310336256

C310336257



C310336258

C310336259

C310336260

C310336261

C310336262

C310336263


C310336264

C310336265

C310336266

C310336267

C310336268

C310336269

C310336270

C310336271

C310336272

C310336273

C310336274


C310336275

C310336276

C310336277

C310336278

C310336279

C310336280

C310336281

C310336282

C310336283

C310336284

C310336285


C310336286

C310336287

C310336288

C310336289



C310336290

C310336291

C310336292

C310336293

C310336294

C310336295

14.1.3 Cell Relocation Statistics


C310342701

Statistics of attempted relocation preparation, by channel type

C310342702

C310342703

C310342704

C310342705

C310342706

C310342707

C310342708

C310342709

C310342710

C310342711

C310342712

C310342713

C310342714

C310342715

Statistics of attempted outgoing relocation, by channel type

C310342716

C310342717

C310342718

C310342719

C310342720

C310342721

C310342722

C310342723



C310342724

C310342725

C310342726

C310342727

C310342728

C310342729

Number of attempted relocation preparation, by traffic class

C310342730

C310342731

C310342732

C310342733

C310342734

C310342735

C310342736

C310342737

Number of attempted outgoing relocation, by traffic class

C310342738

C310342739

C310342740

C310342741

C310342742

C310342743

C310342744

C310342745

Number of attempted relocation preparation with UE not involved for

CS domain, by cause

C310342746

C310342747

C310342748

C310342749

C310342750

C310342751

C310342752

Number of failed relocation preparation with UE not involved for CS

domain, by cause

C310342753

C310342754

C310342755



C310342756

C310342757

C310342758

C310342759

C310342760

C310342761 Number of attempted outgoing relocation with UE not involved for CS

domain

C310342762 Number of failed outgoing relocation with UE not involved for CS

domain, by cause C310342763

C310342764

Number of attempted relocation preparation with UE involved for CS

domain, by cause

C310342765

C310342766

C310342767

C310342768

C310342769

C310342770

C310342771

Number of failed relocation preparation with UE involved for CS

domain, by cause

C310342772

C310342773

C310342774

C310342775

C310342776

C310342777

C310342778

C310342779

C310342780 Number of attempted outgoing relocation with UE involved for CS

domain

C310342781

Number of failed outgoing relocation with UE involved for CS domain,

by cause

C310342782

C310342783

C310342784

C310342785

C310342786



C310342787

C310342788

C310342789

C310342790

C310342791

Number of attempted relocation preparation with UE not involved for

PS domain, by cause

C310342792

C310342793

C310342794

C310342795

C310342796

C310342797

C310342798

Number of failed relocation preparation with UE not involved for PS

domain, by cause

C310342799

C310342800

C310342801

C310342802

C310342803

C310342804

C310342805

C310342806

C310342807 Number of attempted outgoin relocation with UE not involved for PS

domain

C310342808 Number of failed outgoing relocation with UE not involved for PS


C310342810

Number of attempted relocation preparation with UE involved for PS

domain, by cause

C310342811

C310342812

C310342813

C310342814

C310342815

C310342816

C310342817 Number of failed relocation preparation with UE involved for PS



C310342818 domain, by cause

C310342819

C310342820

C310342821

C310342822

C310342823

C310342824

C310342825

C310342826 Number of attempted outgoing relocation with UE involved for PS

domain

C310342827

Number of failed outgoing relocation with UE involved for PS domain,

by cause

C310342828

C310342829

C310342830

C310342831

C310342832

C310342833

C310342834

C310342835

C310342836

C310342837

Number of attempted incoming relocation with UE not involved for CS

domain, by cause

C310342838

C310342839

C310342840

C310342841

C310342842

C310342843

C310342844

Number of failed incoming relocation with UE not involved for CS

domain, by cause

C310342845

C310342846

C310342847

C310342848



C310342849 Number of attempted incoming relocation with UE involved for CS


C310342851

Number of attempted incoming relocation with UE involved for CS

domain, by cause

C310342852

C310342853

C310342854

C310342855

C310342856

Number of failed incoming relocation with UE involved for CS domain,

by cause

C310342857

C310342858

C310342859

C310342860

C310342861

Number of attempted incoming relocation with UE not involved for PS

domain, by cause

C310342862

C310342863

C310342864

C310342865

C310342866

C310342867

C310342868

Number of failed incoming relocation with UE not involved for PS

domain, by cause

C310342869

C310342870

C310342871

C310342872

C310342873

Number of attempted incoming relocation with UE involved for PS

domain, by cause

C310342874

C310342875

C310342876

C310342877

C310342878

C310342879

C310342880 Number of failed incoming relocation with UE involved for PS domain,



C310342881 by cause

C310342882

C310342883

C310342884

C313780279

Statistics of outgoing relocation preparation for Adjacent RNC C313780280

C313780281

C313780282

C313780283

Statistics of outgoing relocation for Adjacent RNC

C313780284

C313780285

C313780286

C313780287

C313780288

C313780289

C313780290

14.1.4 Inter-RAT Cell Handover Statistics


C310352885

Number of attempted incoming inter-RAT handover for CS domain

C310352886

C310352887

C310352888

C310352889

C310352890

C310352891

C310352892

Number of failed incoming inter-RAT handover for CS domain

C310352893

C310352894

C310352895

C310352896

C310352897 Number of attempted incoming inter-RAT handover for PS domain



C310352898

C310352899

C310352900

C310352901

C310352902

C310352903

C310352904

Number of failed incoming inter-RAT handover for PS domain

C310352905

C310352906

C310352907

C310352908

C310352909 Number of attempted incoming inter-RAT handover for PS

domain(Cell Re-selection)

C310352910 Number of successful incoming inter-RAT handover for PS

domain(Cell Re-selection)

C310352911

Number of attempted relocation preparation for outgoing CS inter-RAT

handovers

C310352912

C310352913

C310352914

C310352915

C310352916

C310352917

C310352918

Number of failed relocation preparation for outgoing CS inter-RAT

handovers

C310352919

C310352920

C310352921

C310352922

C310352923

C310352924

C310352925

C310352926

C310352927 Number of attempted relocation preparation for outgoing PS inter-RAT

handovers C310352928



C310352929

C310352930

C310352931

C310352932

C310352933

C310352934

Number of failed relocation preparation for outgoing PS inter-RAT

handovers

C310352935

C310352936

C310352937

C310352938

C310352939

C310352940

C310352941

C310352942

C310352943 Statistics of outgoing CS and PS inter-RAT handovers(DTM)

C310352944

C310352945 Number of attempted outgoing CS inter-RAT handovers

C310352946

Number of failed outgoing CS inter-RAT handovers

C310352947

C310352948

C310352949

C310352950

C310352951

C310356583 Number of successful outgoing CS inter-RAT handovers

C310352952 Number of attempted outgoing PS inter-RAT handovers

C310352953

Number of failed outgoing PS inter-RAT handovers

C310352954

C310352955

C310352956

C310352957

C310352958

C310352959 Number of attempted outgoing PS inter-RAT handovers(Cell Change



Order)

C310352960

Number of failed outgoing PS inter-RAT handovers(Cell Change

Order)

C310352961

C310352962

C310352963

C310352964

C310352965

Statistics of relocation preparation for outgoing inter-RAT handovers,

by channel type

C310352966

C310352967

C310352968

C310352969

C310352970

C310352971

C310352972

C310352973

C310352974

C310352975


by channel type

C310352976

C310352977

C310352978

C310352979

C310352980

C310352981

C310352982

C310352983

C310352984

C310352985 Number of attempted outgoing inter-RAT handoverrs, by channel type

C310352986


by channel type

C310352987

C310352988

C310352989

C310352990



C310352991

C310352992

C310352993

C310352994

C310352995 Number of attempted outgoing inter-RAT handovers, by channel type

C310352996


by channel type

C310352997

C310352998

C310352999

C310353000

C310353001

C310353002

C310353003

C310353004


C310353006


by channel type

C310353007

C310353008

C310353009

C310353010

C310353011

C310353012

C310353013

C310353014


C310353016


by channel type

C310353017

C310353018

C310353019

C310353020

C310353021

C310353022



C310353023

C310353024


C310353026


by channel type

C310353027

C310353028

C310353029

C310353030

C310353031

C310353032

C310353033

C310353034


C310353036


by channel type

C310353037

C310353038

C310353039

C310353040

C310353041

C310353042

C310353043

C310353044


C310353046


by channel type

C310353047

C310353048

C310353049

C310353050

C310353051

C310353052

C310353053

C310353054



C310353055

Statistics of outgoing inter-RAT handovers, by channel type

C310353056

C310353057

C310353058

C310353059

C310353060

C310353061

C310353062


C310353063

C310353064

C310353065

C310353066

C310353067

C310353068

C310353069


C310353070

C310353071

C310353072

C310353073

C310353074

C310353075

C310353076


C310353077

C310353078

C310353079

C310353080

C310353081

C310353082

C310353083


C310353084

C310353085

C310353086



C310353087

C310353088

C310353089

C310353090


C310353091

C310353092

C310353093

C310353094

C310353095

C310353096

C310353097


C310353098

C310353099

C310353100

C310353101

C310353102

C310353103

C310353104


C310353105

C310353106

C310353107

C310353108

C310353109

C310353110

C310353111


C310353112

C310353113

C310353114

C310353115

C310353116

C310353117

C310353118 Number of speech outgoing inter-RAT handovers, by measurement



C310353119 quality

C310353120

C310353121

C310353122

C310353123

C310353124

C310353125

C310353126

C310353127

C310353128

C310353129

C310353130

C310353131

C310353132

C310353133

C310353134

Statistics of outgoing R99 data inter-RAT handovers(CCO), by

measurement quality

C310353135

C310353136

C310353137

C310353138

C310353139

C310353140

C310353141

C310353142

Number of DCH NRT outgoing inter-RAT handovers, by measurement

quality

C310353143

C310353144

C310353145

C310353146

C310353147

C310353148

C310353149

C310353150 Number of DCH video outgoing inter-RAT handover,by measurement



C310353151 Quality

C310353152

C310353153

C310353154

C310353155

C310353156

C310353157

C310353158

Number of DCH other RT outgoing inter-RAT handover,by

measurement Quality

C310353159

C310353160

C310353161

C310353162

C310353163

C310353164

C310353165

C310353166

Number of HS-DSCH outgoing inter-RAT handover,by measurement

Quality

C310353167

C310353168

C310353169

C310353170

C310353171

C310353172

C310353173

C310353174

Number of E-DCH outgoing inter-RAT handover,by measurement

Quality

C310353175

C310353176

C310353177

C310353178

C310353179

C310353180

C310353181

C310353182 Number of VoIP outgoing inter-RAT handover,by measurement



C310353183 Quality

C310353184

C310353185

C310353186

C310353187

C310353188

C310353189

C310353190

C310353191

C310353192

C310353193

C310353194

C310353195

C310353196

C310353197

C310353198

Statistics of outgoing inter-RAT handover,by start cause

C310353199

C310353200

C310353201

C310353202

C310353203

C310353204

C310353205

C310353206

C310353207

C310353208

C310353209

C310353210

C310353211

C310353212

C310353213

C310353214



C310353215

C310353216

C310353217

C310353218

C310353219

C310353220

C310353221

C310353222

C310353223

C310353224

C310353225

C310353226

C310353227

C310353228

C310353229

14.1.5 HSPA Serving Cell Change Statistics


C310363230

Statistics of HS-DSCH serving cell change

C310363231

C310363232

C310363233

C310363234

C310363235

C310363236

C310363237

C310363238

C310363239

C310363240

C310363241

C310363242

C310363243



C310363244

C310363245

C310363246

C310363247

C310363248

C310363249

C310363250

C310363251

C310363252

C310363253

C310363254

C310363255

C310363256

C310363257

C310363258

C310363259

C310363260

C310363261

C310363262

C310366700

Statistics of HS-DSCH serving cell change in Iur

C310366701

C310366702

C310366703

C310366704

C310366705

C310366706

C310366707

C310366708

C310366709

C310366710

C310366711

C310366712



C310366713

C310366714

C310366715

C310366716

C310366717

C310366718

C310366719

C310366720

C310366721

C310363263

Statistics of E-DCH serving cell change

C310363264

C310363265

C310363266

C310363267

C310363268

C310363269

C310363270

C310363271

C310363272

C310363273

C310363274

C310363275

C310363276

C310363277

C310363278

C310363279

C310363280

C310363281

C310363282

C310363283

C310363284

C310363285



C310363286

C310363287

C310363288

C310363289

C310363290

C310363291

C310363292

C310363293

C310363294

C310363295

C310366722

Statistics of E-DCH serving cell change in Iur

C310366723

C310366724

C310366725

C310366726

C310366727

C310366728

C310366729

C310366730

C310366731

C310366732

C310366733

C310366734

C310366735

C310366736

C310366737

C310366738

C310366739

C310366740

C310366741

C310366742

C310366743



14.1.6 Inter-cell Hard Handover Statistics


C310890001

Statistics of outgoing intra-NodeB hard handover

C310890002

C310890003

C310890004

C310890005

C310890006

C310890007

C310890008

C310890009

C310890010

C310890011

C310890012

C310890013

C310890014

C310890015

C310890016

C310890017

C310890018

C310890019

Stattistics of outgoing inter-NodeB,intra-RNC hard handover

C310890020

C310890021

C310890022

C310890023

C310890024

C310890025

C310890026

C310890027

C310890028

C310890029

C310890030



C310890031

C310890032

C310890033

C310890034

C310890035

C310890036

C310890037

Stattistics of outgoing inter-RNC hard handover via Iur

C310890038

C310890039

C310890040

C310890041

C310890042

C310890043

C310890044

C310890045

C310890046

C310890047

C310890048

C310890049

C310890050

C310890051

C310890052

C310890053

C310890054

C310890055

Stattistics of outgoing inter-RNC hard handover switching in the CN

C310890056

C310890057

C310890058

C310890059

C310890060

C310890061

C310890062



C310890063

C310890064

C310890065

C310890066

C310890067

C310890068

C310890069

C310890070

C310890071

C310890072

C310890073

Stattistics of outgoing hard handover,by channel and traffic

C310890074

C310890075

C310890076

C310890077

C310890078

C310890079

C310890080

C310890081

C310890082

C310890083

C310890084

C310890085

C310890086

C310890087

C310890088

C310890089

Statistics of outgoing hard handover,by domain

C310890090

C310890091

C310890092

C310890093

C310890094



C310890095

C310890096

C310890097

C310890098

C310890099

C310890100

C310890101


C310890102

C310890103

C310890104

C310890105

C310890106

C310890107

C310890108

C310890109

C310890110

C310890111

C310890112

C310890113


C310890114

C310890115

C310890116

C310890117

C310890118

C310890119

C310890120

C310890121

C310890122

C310890123

C310890124

C310890125 Statistics of outgoing hard handover,by domain

C310890126



C310890127

C310890128

C310890129

C310890130

C310890131

C310890132

C310890133

C310890134

C310890135

C310890136

14.1.7 Inter-cell Soft Handover Statistics


C310880137 Stattistics of radio link addition for soft handover between cells

C310880138

C310880139

Number of failed radio link addition for soft handover between cells,by

cause

C310880140

C310880141

C310880142

C310880143

C310880144

C310880145

C310880146

C310880147 Stattistics of radio link deletion for soft handover between cells

C310880148

C310880149

Number of failed radio link deletion for soft handover between cells,by

cause

C310880150

C310880151

C310880152

C310880153

C310880154

C310880155



C310880156

C310880157 Stattistics of soft handover between cells

C310880158

C310880159

Number of failed soft handover between cells,by cause

C310880160

C310880161

C310880162

C310880163

C310880164

C310880165

C310880166

C310880167 Statistics of soft handover between cells for monitor set

C310880168

Statistics of soft handover,add Radio link,by channel and traffic

C310880169

C310880170

C310880171

C310880172

C310880173

C310880174

C310880175

C310880176

C310880177

C310880178

C310880179

C310880180

C310880181

C310880182

C310880183

C310880184

Statistics of soft handover,delete Radio link,by channel and traffic C310880185

C310880186

C310880187



C310880188

C310880189

C310880190

C310880191

C310880192

C310880193

C310880194

C310880195

C310880196

C310880197

C310880198

C310880199

14.1.8 Inter-cell Detected Set Statistics


C310910200 Statistics of detected set

14.1.9 Inter-RAT Inter-cell Handover Statistics


C310900001

Stattistics of attempted relocation preparation for outgoing CS

inter-RAT handovers

C310900002

C310900003

C310900004

C310900005

C310900006

C310900007

C310900008

Stattistics of failed relocation preparation for outgoing CS

inter-RAT handovers

C310900009

C310900010

C310900011

C310900012

C310900013



C310900014

C310900015

C310900016

C310900017 Stattistics of attempted outgoing CS inter-RAT handovers

C310900018

Stattistics of failed outgoing CS inter-RAT handovers

C310900019

C310900020

C310900021

C310900022

C310900023

C310900024

Stattistics of attempted relocation preparation for outgoing PS

inter-RAT handovers(Handover from UTRAN)

C310900025

C310900026

C310900027

C310900028

C310900029

C310900030

C310900031

Stattistics of failed relocation preparation for outgoing PS

inter-RAT handovers(Handover From UTRAN)

C310900032

C310900033

C310900034

C310900035

C310900036

C310900037

C310900038

C310900039

C310900040 Stattistics of attempted outgoing PS inter-RAT

handovers(Handover From UTRAN)

C310900041

Stattistics of failed outgoing PS inter-RAT handovers(Handover

From UTRAN)

C310900042

C310900043

C310900044



C310900045

C310900046

C310900047 Stattistics of attempted outgoing PS inter-RAT handovers

C310900048

Stattistics of failed outgoing PS inter-RAT handovers

C310900049

C310900050

C310900051

C310900052

C310900053

Stattistics of outgoing inter-RAT handovers,by Channel and

traffic

C310900054

C310900055

C310900056

C310900057

C310900058

C310900059

C310900060

C310900061

C310900062

C310900063

C310900064

C310900065

C310900066

C310900067

C310900068

C310900069

Stattistics of incoming inter-RAT handovers

C310900070

C310900071

C310900072

C310900073

C310900074

C310900075

C310900076



C310900077

C310900078

C310900079

C310900080

C310900081

C310900082

14.1.10 Soft Handover via Iur Statistics


C312190211

Statistics of active set update ,Iur

C312190212

C312190213

C312190214

C312190215

C312190216

C312190217

C312190218

C312190219

C312190220

C312190221

C312190222

C312190223

C312190224

C312190225

C312190226

C312190227

C312190228

C312190229

C312190230

C312190231

C312190232

C312190233 Statistics of active set update for E-DCH,Iur



C312190234

C312190235

C312190236

C312190237

C312190238

C312190239

C312190240

C312190241

C312190242

C312190243

C312190244

C312190245

C312190246

C312190247

C312190248

C312190249

C312190250

C312190251

C312190252

C312190253

C312190254

14.1.11 Eutran Inter-RAT Handover Statistics


C312106764 Number of attempted incoming inter-RAT handover for SRVCC

C312106765

Number of failed incoming inter-RAT handover for SRVCC,by

cause

C312106766

C312106767

C312106768

C312106769

C312106770 Number of attempted incoming inter-RAT handover for PS

domain(Eutran to Utran)



C312106771

Number of failed incoming inter-RAT handover for PS

domain(Eutran to Utran)

C312106772

C312106773

C312106774

C312106775

C312106776 Number of attempted relocation preparation for outgoing PS

inter-RAT handovers(Utran to Eutran)

C312106777

Number of failed relocation preparation for outgoing PS

inter-RAT handovers(Utran to Eutran)

C312106778

C312106779

C312106780

C312106781

C312106782

C312106783

C312106784

C312106785

C312106786 Number of attempted outgoing PS inter-RAT handovers(Utran to

Eutran)

C312106787

Number of failed outgoing PS inter-RAT handovers(Utran to

Eutran)

C312106788

C312106789

C312106790

C312106791

C312106792

C312103530

Number of PS incoming inter-RAT handover for CSFB(EUTRAN

to UTRAN)

C312103531

C312103532

C312103533

C312103534

C312103535

14.1.12 Compressed Mode Statistics




C310605484 Total number of Compressed Mode Command in Cell

C310760044 Total number of Compressed Mode message send over Iur

C310615519 Total Number of Compress Mode Command over Iur(DRNC)

C310585292 Total Number of Measurement Control Send

C310585293 Number of Measurement Control to Activate Compressed Mode

for Interfrequency Measurement


for InterRAT Measurement


for CS Service


for PS Service


for CS+PS Service


for Ec/No Measurement


for RSCP Measurement

C310585300 Total Number of Measurement Control Failure Received

C310585301 Number of Measurement Control Failure due to Compressed

Mode Runtime Error

C310585302 Number of Measurement Control Failure due to Protocol Error

C310585303 Number of Measurement Control Failure due to Cell Update

Occurred

C310585304 Number of Measurement Control Failure due to Invalid

Configuration

C310585305 Number of Measurement Control Failure due to Configuration

Incomplete

C310585306 Number of Measurement Control Failure due to Unsupported

Measurement

C310585307 Number of Measurement Control Failure due to other

C310585308 Number of Measurement Control Failure to Activate Compressed

Mode for Interfrequency Measurement


Mode for InterRAT Measurement




Mode for CS Service


Mode for PS Service


Mode for CS+PS Service


Mode for Ec/No Measurement


Mode for RSCP Measurement

14.2 Alarm List

This feature has no related alarm.

15 Glossary

B

BLER Block error ratio

BSC Base Station Controller

C

CIO Cell individual offset

CN Core Network

CPICH Common Pilot Channel

CS Circuit switched

CSFB CS Fallback

CTCP Common transmitted carrier power

D



DCH Dedicated Channel

DL Downlink (Forward Link)

DPCCH Dedicated Physical Control Channel

DPDCH Dedicated Physical Data Channel

DRBC Dynamic Radio Bearer Control

DRNC Drift Radio Network Controller

DSCR Directed Signaling Connection Re-establishment

DTCP Dedicated transmitted code power

DTM Dual Transfer Mode

E

Ec/No Received energy per chip divided by the power density in the band

E-DCH Enhanced Dedicated Channel

E-UTRA Evolved Universal Terrestrial Radio Access

E-UTRAN Evolved Universal Terrestrial Radio Access Network

F

FDD Frequency Division Duplex

G

GBR Guaranteed Bit Rate

GGSN Gateway GPRS Support Node

GPRS General Packet Radio Service

GSM Global system for mobile communications



GERAN GSM/EDGE Radio Access Network

H

HCS Hierarchical Cell Structure

HLR Home Location Register

HSDPA High speed downlink packet access

HS-DSCH High Speed Downlink Shared Channel

HSPA High Speed Packet Access

HS-PDSCH High Speed Physical Downlink Shared Channel

HSUPA High speed uplink packet access

I

IMS IP Multimedia Sub-system

IMSI International Mobile Subscriber Identity

L

LTE Long Term Evolution

M

MBMS Multimedia Broadcast Multicast Service

MGW Media GateWay

MSC Mobile Switching Centre

N

NACC Network Assisted Cell Change

NRT Non-Real Time



O

OLPC Outer loop power control

P

P-CPICH Primary Common Pilot Channel

PS Packet switched

Q

Qos Quality of Service

R

RAB Radio access bearer

RIM RAN Information Management

RL Radio Link

RNC Radio network controller

RNS Radio Network Subsystem

RRC Radio resource control

RSCP Received Signal Code Power

RSRP Reference Signal Received Power

RSSI Received Signal Strength Indicator

RT Real Time

RTWP Received Total Wideband Power

S

SF Spreading Factor



SGSN Serving GPRS Support Node

SI System Information

SIR Signal to interference ratio

SON Self Organizing Networks

SRNC Serving Radio Network Controller

SRNS Serving RNS

SRVCC Single Radio Voice Call Continuity

T

TCP Transmitted Code Power

TDD Time Division Duplex(ing)

TFCS Transport format combination set

TG Transmission Gap

TGD Transmission Gap start Distance

TGL Transmission Gap Length

TGSN Transmission Gap Starting Slot Number

TGPL Transmission Gap Pattern Length

TTI Transmission time interval

U

UE User equipment

UL Uplink

UMTS Universal Mobile Telecommunications System



UTRA UMTS Terrestrial Radio Access

UTRAN UMTS Terrestrial radio access network

W

WCDMA Wideband CDMA, Code division multiple access

3g Handover Detailed Document

Documents

Transcript of 3g Handover Detailed Document