Feature Deployment and Testing Guide

E-DCH Intra-Frequency Hard Handover

Feature ID: ZWF25-03-003

Version: V3.11.10

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-6-18 First eition

Serial Number: SJ-20120802112720-215

Publishing Date: 2012-06-18 (R1.0)

SJ-20120802112720-215|2012-06-18 (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-4

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

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

 II

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

 Chapter 1
Functional Description
Hard handover is a typical handover mechanism in which a UE needs to disconnect the
link with the original cell before setting up a link (synchronization) with the new cell (that
is, new and original links do not co-exist in UE). The intra-frequency hard handover is only
adopted when soft/softer handover is unavailable.

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

intra-frequency hard handover. If target cell supports HSUPA, intra-frequency hard
handover will accompany with E-DCH serving cell change, otherwise E-DCH will fall back
to DCH.

Introduction to Intra-Frequency Measurement

Intra-frequency measurement means to perform measurement on intra-frequency cells.
Only event-based method of reporting measurement result is supported, and parameter
SofthoMthd is invalid. The event-based report method means the UE judges whether
intra-frequency events are met based on the quality measurement result of 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.
l Event 1A: A Primary CPICH enters the Reporting Range. It can be used for adding
cell to the active set.
l Event 1B: A Primary CPICH leaves the Reporting Range. It can be used for deleting
cell from the active set.
l 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.
l Event 1D: The best cell changes. It can be used for soft/softer handover,
intra-frequency hard handover and inter-frequency load balance.

Handling of Intra-Frequency Events

l Handling of Event 1A

Add links to the active set if the number of links in the DCH active set is less than
3. Do not handle Event 1A if the total number of links in the active set reaches
the maximum.

If a link to be added to the active set is rejected in Event 1A, the handover
punishment timer (5s) is initiated so that the Event 1A reported by this rejected
cell will not be handled until the timer times up.

1-1

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF25-03-003

If the cell reporting Event 1A is the target cell traced by the detected set, no link
will be added to the active set. For details, see Detected set Tracing.
If the measurement report contains several target cells, the cell with best quality
(Ec/N0) will be selected as the target cell to be added in the active set.
l Handling of Event 1B
Delete the link of related cell based on Event 1B reported by UE.
If the measurement report contains several target cells, the cell with worst quality
(Ec/N0) will be selected as the target cell to be deleted from the active set.
l Handling of Event 1C
Replace the cell if the radio links in active set are equal 3.
If a link to be added to the active set in Event 1C is admission control failure,
the handover punishment timer is initiated so that the Event 1C reported by this
admission control failure cell will not be handled until the timer times up.
l Handling of Event 1D
The cell triggering Event 1D is an intra-frequency adjacent cell outside the
active set. if the criterion mentioned in "1.3.3 Scenarios of Intra-Frequency hard
handover" is fulfilled, RNC will perform intra-frequency hard handover.
The cell triggering Event 1D is an intra-frequency adjacent cell outside the active
set. If the DCH active set is full, turn to Event 1C handling. If the DCH active
set is not full, turn to Event 1A handling. And if event 1A or 1C is failure due to
admission control failure, RNC will perform intra-frequency hard handover.
If the cell triggering Event 1D is within the active set, change the best cell in the
active set.
After Active Set Update is sent from RNC to UE, if Active Set Update Complete is not
received in a period of time (TWAITACTSETUPCMP), RNC will consider active set update
to fail.

Scenarios of Intra-Frequency hard handover

When soft handover cannot be realized in adjacent cells of intra-frequency for some
reasons, intra-frequency hard handover can guarantee the service continuity. The
scenarios where soft/softer handover is unavailable (intra-frequency hard handover must
be adopted) in the case of intra-frequency handover include:
l Adding new link fails in soft handover when 1A or 1C event is triggered.
l Intra-frequency measurement report excludes the OFF and TM of the target cell.
l lur interface between RNCs is unavailable in the case of intra-frequency handover.
l Types of target and source cells are different (define R99, R5+R99, R6+ R5+ R99
belong to the same cell type and R5, R6+ R5 belong to another cell type), for example,
the UE hands over from a DCH-capable cell to an HSPA-capable cell.
l The signal RB is carried on HS-DSCH in active cell, while F-DPCH is not supported
in soft add cell.

1-2

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

 Chapter 1 Functional Description

l The capability of target cell is not consistent with that of source cell. Such as UE
uses transmit diversity in active set cell, but the target cell does not support transmit
diversity; UE uses multi-user detection in the active set cell, but the target cell does not
support multi-user detection; UE uses DTX-DRX in the active set cell, but the target
cell does not support the capability; uplink 16QAM is configurated but the target cell
does not support; TTI 2ms service is setup in source cell but the target cell does not
support; the transmission delay TimeDelay reported during intra-frequency handover
for the NodeB 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 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.

Intra-RNC Hard handover

Figure 1-1 Intra-RNC hard handover procedure

1-3

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF25-03-003

Inter-RNC Hard Handover Through lur Interface

Figure 1-2 Inter-RNC hard handover through lur interface

If inter-frequency cells between RNCs are adjacent and Iur interface is unavailable, the
hard-handover-triggered SRNS relocation is performed. The procedure is as follows:
The SRNC setup radio link at DRNC through the lu interface relocation, and then
reconfigure UE to the cell of DRNC through relocation. Upon receiving the reconfiguration
response message from the UE, the DRNC informs the CN to complete relocation and
changes into SRNC. The CN then releases the resources of UE at the original SRNC
through Iu interface release command.

1-4

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

 Chapter 2
Preparations
License
N/A

Hardware Requirement
Hardware requirement is shown in Table 2-1.

Table 2-1 Hardware Requirement

NE Requirement

RNC None

NodeB None

Software Requirement
Software requirement is shown in Table 2-2.

Table 2-2 Software Requirement

NE Involved Version Requirement

UE YES UMTS FDD Number: 1

Release : R6

NodeB YES V4.11.10.14 ZTE equipment

RNC YES V3.11.10.11 ZTE equipment

MSCS YES None ZTE equipment

MGW YES None ZTE equipment

SGSN YES None ZTE equipment

GGSN NO None None

HLR NO None None

Topology
Topology is shown in Figure 2-1.

2-1

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF25-03-003

Figure 2-1 Topology

2-2

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

 Chapter 3
Data configuration
SGSN/GGSN - ZTE
N/A

MSC/MGW - ZTE
N/A

HLR ZTE
UE subscribe interactive MBR 2mbps/2mbps.
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.trafficClass = eRANAP_TrafficClass_interactiv
e

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.n = 1

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.rAB_Parameters.maxBitrate.elem[0] = 2048000

RNC
In this test, the two test cells are cell108 and cell112, they are intra-frequency cells belong
to different NodeB in the same RNC. To fulfill intra-frequency hard handover scenario, cell
108 is configured to support HSUPA, HSDPA and DCH, cell 112 is configured to support
HSUPA and HSDPA.
l Set cell 108 support HSUPA, HSDPA and DCH

HSPA Support Method: Support HSUPA, HSDPA and DCH

3-1

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF25-03-003

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Cell Ability and Cell
Reselection > HSPA Support Method
l Set cell 112 support HSUPA and HSDPA
HSPA Support Method: Support HSUPA, HSDPA and DCH

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Cell Ability and Cell
Reselection > HSPA Support Method
l Set cell 112 as cell 108's neighbour cell
Cell Identity: 108 / Neighbouring Physical Cell Identity: 112 / Does Neighbouring Cell
Belong to Self Physical RNC: True

3-2

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Data configuration

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > Neighbouring Cell > Create

NodeB
N/A

3-3

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF25-03-003

This page intentionally left blank.

3-4

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

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

4.1 Test Purpose

The purpose of this test case is to verify if the function of E-DCH Intra-Frequency Hard
Handover is working normal.

Related documents:

ZTE UMTS Handover Control Feature Guide.doc

4.2 Steps for Test

1. UE initiala PS service in cell 108 and start ftp uploading.
l From "rrcConnectionRequest" message, UE support release 6.

l From "RAB_AssignmentRequestMsg", UE traffic class is interactive, maxBitrate

is UL2mbps/DL2mbps.

4-1

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF25-03-003

l From "RadioLinkReconfigurationPrepareFDDMsg" message, UE service setup

on E-DCH.

2. UE movesfrom Cell108 to Cell112 to trigger event 1D. Then UE performs hard

handover to Cell112.
l From "measurementReport" message, UE reports event 1D. The primary
scrambling code 112 is cell 112's PSC.

4-2

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

 Chapter 4 Testing

l From the following "RadioLinkSetupRequestFDDMsg" message, UE service set

up on E-DCH in cell 112.

3. Deactivate UE's PS service.

4-3

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF25-03-003

4.3 Expected Results

In step2 of chapter 4.2 Steps for Test, UE performs the E-DCH intra-frequency hard
handover procedure successfully.

The uploading speed is stable before and after handover, there is little gap in handover.

4-4

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

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

C310332525 Number of outgoing inter-NodeB, intra-RNC intra frequency hard handover

attempt

C310332547 Number of outgoing inter-RNC intra frequency hard handover via Iur attempt

C310332575 Number of outgoing inter-RNC intra frequency hard handover via Iur attempt
for E-DCH

C310332589 Number of outgoing inter-RNC intra frequency hard handover via Iur failed for
E-DCH

C310332597 Number of outgoing intra frequency hard handover attempt, Radio quality
required

C310332598 Number of outgoing intra frequency hard handover attempt, Load control
required

C310332599 Number of outgoing intra frequency hard handover attempt, Load and ability
proportion required

C310332600 Number of outgoing intra frequency hard handover attempt, MBMS Modify
request required

C310332650 Number of outgoing intra frequency hard handover attempt, Streaming class

C310332651 Number of outgoing intra frequency hard handover attempt, Interactive class

C310332652 Number of outgoing intra frequency hard handover attempt, Background class

C310332666 Number of outgoing intra frequency hard handover attempt, PS domain

C310332679 Number of outgoing intra frequency hard handover attempt, E-DCH

C310332693 Number of outgoing intra frequency hard handover failed, E-DCH

C310335701 Number of outgoing intra frequency hard handover attempt, Admission failed

C310335702 Number of outgoing intra frequency hard handover attempt, No Report

Adjacency Cell Information

C310335703 Number of outgoing intra frequency hard handover attempt, No Iur

C310335704 Number of outgoing intra frequency hard handover attempt, Capability of

Adjacency Cell And Source Cell Unlikeness

C310336186 Number of outgoing PS intra frequency hard handover attempted using

physical channel reconfiguration

5-1

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF25-03-003

C310336208 Number of outgoing PS intra frequency hard handover attempted using Radio
bearer setup

C310336230 Number of outgoing PS intra frequency hard handover attempted using Radio
bearer reconfiguration

C310336252 Number of outgoing PS intra frequency hard handover attempted using Radio
bearer release

C310336274 Number of outgoing PS intra frequency hard handover attempted using

Transport Channel reconfiguration

C310336606 Number of attempted intra-RNC intra-frequency hard handover, PS domain

traffic

C310336608 Number of successful intra-RNC intra-frequency hard handover, PS domain

traffic

C310336614 Number of attempted inter-RNC intra-frequency hard handover, PS domain

traffic

C310336616 Number of successful inter-RNC intra-frequency hard handover, PS domain

traffic

C310336836 Number of outgoing intra-NodeB intra frequency hard handover preparation

attempt

C310336846 Number of outgoing inter-NodeB, intra-Rnc intra frequency hard handover

preparation attempt

C310336856 Number of outgoing inter-Rnc intra frequency hard handover preparation

attempt

5-2

SJ-20120802112720-215|2012-06-18 (R1.0) ZTE Proprietary and Confidential