SJ-20120815154121-028-ZWF21-03-003 Inter-Frequency Hard Handover - 451987 PDF

Feature Deployment and Testing Guide
Inter-Frequency Hard Handover

Feature ID: ZWF21-03-003
Version: V4.11.20
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 2012-09-17 First edition
Serial Number: SJ-20120815154121-028
Publishing Date: 2012-09-17 (R1.0)
SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

Contents
Chapter 1 Functional Description ............................................................. 1-1
Chapter 2 Preparations .............................................................................. 2-1
Chapter 3 Data Configuration.................................................................... 3-1
Chapter 4 Testing ....................................................................................... 4-1
4.1 Test Purpose...................................................................................................... 4-1
4.2 Steps for Test..................................................................................................... 4-1
4.3 Expected Results ............................................................................................... 4-3
Chapter 5 Counter List............................................................................... 5-1

II

Chapter 1
Functional Description
Inter-frequency hard handover means a UE in connecting state hands over from a cell on
a frequency of UTRAN to another cell on another frequency.
The factors triggering inter-frequency hard handover include radio quality, load, and
moving speed of UE.
Inter-frequency hard handover triggered by radio quality: Initiate inter-frequency

measurement when the quality of frequency where UE is currently located worsens, and
handover UE to the frequency with better quality based on inter-frequency measurement
results. The quality of the carrier frequency where the UE is currently located is measured
through the following four standards (For details, see Inter-Frequency Handover
Strategy):
l PCPICH quality of cell in current serving carrier frequency
l Uplink Block Error Rate (BLER) of the Dedicated CHannel (DCH).
l Uplink transmit power of DCH
l Downlink transmit power of DCH
Inter-frequency hard handover triggered by cell load: When the load of cell on current
frequency is too heavy, the system switches partial services of this cell to an adjacent cell
on another frequency.
Inter-frequency hard handover triggered by moving speed of 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 so as to realize appropriate traffic distribution in cells, make
full use of system resources and enhance system performance.
For non-double-receiver terminals in WCDMA, the compressed mode must be initiated for
inter-frequency measurement. The initiation of compressed mode has some impact on
the performance of both system and UE .Therefore, compressed mode must be initiated
only when necessary (for example, when the quality of current serving carrier frequency
worsens).
The inter-frequency handover is a feature in which the UE hands over from one
frequency of UTRAN to another one. It can either be handover based on inter-frequency
measurement, or blind handover based on ShareCover(Overlap or Covers). The
measurement-based handover cannot trigger the 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 balance.
The prerequisite for measurement-based inter-frequency handover is that UE performs

quality measurement of non-used frequency. For inter-frequency measurement in
CELL_DCH state, UE needs to initiate compressed mode unless it has double-receiver.
1-1

Feature Deployment and Testing Guide Feature ID: ZWF21-03-003
The compressed mode has a great impact on both the resource utilization (for example,
downlink power and uplink interference) and UE (for example, the transmit power
and battery consumption), so inter-frequency measurement is only initiated when the
radio quality of 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 UE for
PCPICH). Upon receiving the inter-frequency measurement results from UE, the RNC
makes a decision about inter-frequency handover, and hands over 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) in the adjacent cell configuration relation. If the radio
quality of a cell is good, then that of another cell with ShareCover(Overlap or Covers)
relation with this cell must also be good, that is, to forecast the radio quality of another cell
with ShareCover(Overlap or Covers) relation with a cell based on the radio quality of this
cell. Whether ShareCover(Overlap or Covers) relation exists among cells is determined by
the network planner based on cell coverage (Only 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.
l In the load balancing mechanism, if the load of the target cell for access or handover
is too heavy, you can access or handover the service into another less loaded cell that
has ShareCover(Overlap or Covers) relation with the target cell.
l In the load control mechanism, if the load of current cell is too heavy, you can forcedly
handover partial services into another less loaded cell that has ShareCover(Overlap
or Covers) relation with the target cell.
l In the handover based on moving speed, when the UE changes from low to high
moving speed, you can directly handover the UE from micro cell into a macro cell that
contains this micro cell.
When conducting inter-frequency measurement, the UE needs to implement layer 3 filter
for the measurement results to avoid measurement fluctuation and then make event
decision and report by using filtered values. The layer 3 filter factor is FilterCoeff (Inter).
For inter-frequency measurement formula, see Intra-frequency Measurement.
Carrier evaluation standards for inter-frequency measurement:
Where,
Qfrequency j: Refers to (Virtual) active set quality of carrier j, that is, the measurement result
of carrier j (dB for Ec/No; dBm for RSCP).
1-2

Chapter 1 Functional Description
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 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[MAX_INTER_MEAS_EVENT] or
Wused[MAX_INTER_MEAS_EVENT]) of the best cell in the (Virtual) active set of carrier j
during carrier measurement.
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 Ec/N0 or RSCP or both of them measurement quantity, which is based on the
parameter NonIntraMeasQuan. Only event-based method of reporting measurement
result is supported, and parameter InterHoMth is invalid.The event-based report means
the UE judges whether inter-frequency events are met based on the quality measurement
result of non-working carrier frequency PCPICH. If so, it reports inter-frequency events
(including such information as event ID, and 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 handover.
The inter-frequency handover events are described as follows:
Event 2A: The best carrier frequency changes.
Where,
QNotBest: Refers to the measurement result of current non-best carrier frequency.
QBest : Refers to the measurement result of current best carrier frequency.
H2a: Refers to handover decision hysteresis parameter
(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) 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.
Where,
QNon used: Refers to the measurement result of current non-working carrier frequency.
1-3

TNon used 2b: Refers to the absolute threshold

(ThreshNoUsedFreq[MAX_INTER_MEAS_EVENT]) of good quality of non-working
carrier frequency in Event 2B decision.
H2b: Refers to handover decision hysteresis parameter
(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2B.
QUsed: Refers to the measurement result of current working carrier frequency.
TUsed 2b: Refers to the absolute threshold
(ThreshUsedFreq[MAX_INTER_MEAS_EVENT]) of poor quality of working carrier
frequency in Event 2B decision.
Event 2C: The quality of non-working carrier frequency is higher than a threshold.
Where,
TNon used 2c: Refers to the absolute threshold
carrier frequency in Event 2C decision.
H2c: Refers to handover decision hysteresis parameter
(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2C.
Event 2D: The quality of working carrier frequency is lower than a threshold.
Where,
TUsed 2d: Refers to the absolute threshold
frequency in Event 2D decision.
H2d: Refers to handover decision hysteresis parameter
(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2D.
Event 2E: The quality of non-working carrier frequency is lower than a threshold.
Where,
TNon used 2e: Refers to the absolute threshold
carrier frequency in Event 2E decision.
1-4

Chapter 1 Functional Description
H2e: Refers to handover decision hysteresis parameter

(Hysteresis[MAX_INTER_MEAS_EVENT] ) of Event 2E.
Event 2F: The quality of working carrier frequency is higher than a threshold.
Where,
TUsed 2f: Refers to the absolute threshold

frequency in Event 2F decision.
H2f: Refers to handover decision hysteresis parameter

(Hysteresis[MAX_INTER_MEAS_EVENT] (Inter)) of Event 2F.
If a carrier frequency meets the reporting range or threshold of certain event, the condition
must be met within a period of time (TrigTime(Iner)) before the reporting of this event to
avoid inter-frequency event misreport due to the fluctuation of radio quality.
1-5

This page intentionally left blank.
1-6

Chapter 2
Preparations
License
N/A
Hardware Requirement
NE Requirement
RNC None
NodeB None
Software Requirement
NE Involved Version Requirement
UE YES UMTS FDD Number: 1

Category: Any
Release: Any
Node B YES V4.11.10.14 ZTE equipment
RNC YES V4.11.20.06 ZTE equipment
MSCS YES ZTE equipment
MGW YES ZTE equipment
SGSN YES ZTE equipment
GGSN NO
HLR NO
Topology
Topology is shown in Figure 2-1.
2-1

Figure 2-1 Topology
2-2

Chapter 3
Data Configuration
SGSN/GGSN - ZTE
Usually, the default configuration supports PS call. In the RAB_AssignmentRequestMsg
message, SGSN indicates the traffic class and the MBR:
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass_backgro
und
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[0] = 2048000
MSC/MGW - ZTE
N/A
HLR - ZTE
N/A
RNC
Parameters setting in the RNC
Cell78 and Cell77 have the different frequency
-DUARFCN: xxx (Refer to your parameter table)
3-1

Path: View > Configuration Management > Managed Element > UMTS Logical
Function Configuration > UTRAN Cell
Cell78 and Cell77 HSPA Support Method parameter settingSupport HSUPA, HSDPA and
DCH, Inter-frequency measurement Report Profile setting: UInterMeasProfile=0
Path: View->Configuration Management->Management Element->UMTS Logical

Function Configuration->UTRAN Cell
Inter-frequency measurement Profile setting follows this principle:
Firstly, choose the category number according to service and bearer type. There are 8
kinds of service category.
3-2

Chapter 3 Data Configuration
Please remember the srvCategory according to service and bearer type in test case
specification. For example, in this test case srvCategory=3, service and bearer type is
single NRT RAB on DL HS-DSCH/UL DCH[3].
3-3

Function Configuration > Service Configuration > Measurement Configuration > UE
Inter-frequency Measurement Profile > Inter-frequency Measurement Configuration
Related To Traffic Category
Secondly, choose the category number according to the measurement quantity, test
service and bearer type. For example, we choose the item that UInterMeasSrvSpec=3,
UInterMeasProfile=0, because UE has PS call in DL HS-PDSCH/ UL DCH, and
Inter-frequency measurement Report Profile setting: UInterMeasProfile=0 in Cells
parameter. You can modify Event parameters to trigger inter-frequency handover happen
easy.
3-4

Function Configuration > Service Configuration > Measurement Configuration > UE
Inter-frequency Measurement Profile > Inter-frequency Measurement Configuration
Related To Traffic Category > UE Inter-frequency Event Measurement Configuration
for CPICH RSCP(UTRAN)
Cell78 and Cell77 are configured as adjacent cells with different coverage.
3-5

3-6

Function Configuration > UTRAN Cell > Adjacent Relation Configuration >
Neighbouring Cell
Parent DN: CellXXX(Refer to your parameter table)
Neighbouring Cell Object ID: X (Refer to your parameter table)

Used UUtranCellFDD: CellXXX (Refer to your parameter table)
Share Cover Indication: Neighbor
Node B
N/A
3-7

3-8

Chapter 4
Testing
Table of Contents
Test Purpose ..............................................................................................................4-1
Steps for Test .............................................................................................................4-1
Expected Results .......................................................................................................4-3
4.1 Test Purpose

The purpose of this test case is to verify if the function of Inter-Frequency Hard Handover
is working normal.
Related document:
ZTE UMTS Handover Control Feature Guide.doc
4.2 Steps for Test

1. UE1 activates a PS service in Cell1 and starts FTP downloading, MBR= UL2Mbps/
DL2Mbps.
2. From the measurement Control message, we can find the 2D and 2F Event
parameters.
4-1

3. UE1 moves from Cell78 to Cell77 to trigger Event 2D and activate the compressed
mode.
After Event 2D, RNC sends measurementControl to UE including Event 2A, 2D,
2E, 2F which is set as our expectation to notice UE active Compress Mode(Path:
View->Configuration Management->Management Element->UMTS Logical
Function Configuration->Service Configuration->Measurement Configuration->UE
Inter-frequency Measurement Profile->Inter-frequency Measurement Configuration
Related To Traffic Category->UE Inter-frequency Event Measurement Configuration
for CPICH RSCP(UTRAN)).
4-2

Chapter 4 Testing
RNC sends CompressModeCommandMsg to Nodeb, we can see the TGPS=1.
4. UE1 moves further to Cell77 to trigger event 2A. UE1 performs the hard handover to
Cell77.
4.3 Expected Results

UE1 performs the hard handover successfully.
4-3

4-4

Chapter 5
Counter List
C310332514 Number of outgoing intra-NodeB inter frequency
hard handover attempt

hard handover failed,configuration unsupported

hard handover failed,Physical Channel failed

hard handover failed,Incompatible Simultaneous
Reconfiguration

hard handover failed,Compress Mode Error

hard handover failed,Protocol Error

hard handover failed,Cell Update Occurred

hard handover failed,invalid configuration

hard handover failed,configuration incomplete

hard handover failed,No Reply

hard handover failed,Other Causes
C310332536 Number of outgoing inter-NodeB,intra-RNC inter

frequency hard handover attempt

frequency hard handover failed,configuration
unsupported

frequency hard handover failed,Physical Channel
failed
5-1


frequency hard handover failed,Incompatible
Simultaneous Reconfiguration

frequency hard handover failed,Compress Mode
Error

frequency hard handover failed,Protocol Error

frequency hard handover failed,Cell Update
Occurred
C310332543 Number of outgoing inter-NodeB,intra-RNC

inter frequency hard handover failed,invalid
configuration

frequency hard handover failed,configuration
incomplete

frequency hard handover failed,No Reply

frequency hard handover failed,Other Causes
C310332558 Number of outgoing inter-RNC inter frequency

hard handover via Iur attempt

hard handover via Iur failed,configuration
unsupported

hard handover via Iur failed,Physical Channel
failed

hard handover via Iur failed,Incompatible
Simultaneous Reconfiguration

hard handover via Iur failed,Compress Mode
Error

hard handover via Iur failed,Protocol Error

hard handover via Iur failed,Cell Update Occurred
5-2

Chapter 5 Counter List

hard handover via Iur failed,invalid configuration

hard handover via Iur failed,configuration
incomplete

hard handover via Iur failed,No Reply

hard handover via Iur failed,Other Causes
5-3

SJ-20120815154121-028-ZWF21-03-003 Inter-Frequency Hard Handover - 451987 PDF

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

SJ-20120815154121-028-ZWF21-03-003 Inter-Frequency Hard Handover - 451987 PDF

Transféré par

Droits d'auteur :

Formats disponibles

Feature Deployment and Testing Guide

Inter-Frequency Hard Handover

Revision No. Revision Date Revision Reason

R1.0 2012-09-17 First edition

Serial Number: SJ-20120815154121-028

Publishing Date: 2012-09-17 (R1.0)

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

Chapter 5 Counter List............................................................................... 5-1

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

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

The prerequisite for measurement-based inter-frequency handover is that UE performs

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

Carrier evaluation standards for inter-frequency measurement:

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

Introduction to Inter-Frequency Measurement

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

TNon used 2b: Refers to the absolute threshold

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

H2e: Refers to handover decision hysteresis parameter

TUsed 2f: Refers to the absolute threshold

H2f: Refers to handover decision hysteresis parameter

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

UE YES UMTS FDD Number: 1

Node B YES V4.11.10.14 ZTE equipment

RNC YES V4.11.20.06 ZTE equipment

MSCS YES ZTE equipment

MGW YES ZTE equipment

SGSN YES ZTE equipment

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

Figure 2-1 Topology

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

Path: View->Configuration Management->Management Element->UMTS Logical

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

Neighbouring Cell Object ID: X (Refer to your parameter table)

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

4.1 Test Purpose

4.2 Steps for Test

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

RNC sends CompressModeCommandMsg to Nodeb, we can see the TGPS=1.

4.3 Expected Results

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20120815154121-028|2012-09-17 (R1.0) ZTE Proprietary and Confidential

C310332515 Number of outgoing intra-NodeB inter frequency

C310332516 Number of outgoing intra-NodeB inter frequency

C310332517 Number of outgoing intra-NodeB inter frequency

C310332518 Number of outgoing intra-NodeB inter frequency

C310332519 Number of outgoing intra-NodeB inter frequency

C310332520 Number of outgoing intra-NodeB inter frequency

C310332521 Number of outgoing intra-NodeB inter frequency

C310332522 Number of outgoing intra-NodeB inter frequency

C310332523 Number of outgoing intra-NodeB inter frequency