Feature Deployment and Testing Guide

Radio Connection Re-establishment

Feature ID: ZWF21-01-008

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-08-09 First edition

Serial Number: SJ-20120802112720-009

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

SJ-20120802112720-009|2012-08-09 (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-2

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

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 II

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 1
Functional Description
A UE in the DCH state may suffer from temporary radio connection interruption and
cannot continue the services due to burst interference or abrupt changes to the radio
environment. Before the UTRAN detects the radio connection interruption, the UE
recovers the services. At the moment, the UE sends the cell update message with the
cause as Radio link failure or RLC unrecoverable error (for the service RB) and attempts
to establish network connections.
In this scenario, the ZTE RAN supports re-establishing radio connection between the
UE and the UTRAN and recovers the communication without releasing the original RRC
connection and Iu connection. The user can feel the transient service interruption brought
about by the radio connection re-establishment but this does not cause call drop.
Call Re-establishment:
Call re-establishment is a procedure of re-establishing the radio link of a UE. When a link is
interrupted due to poor radio quality, if the UE in DCH state detects an RlC Unrecoverable
Error or RL FAILURE and the durations of all service re-establishment timers (T314 and
T315) are neither 0 nor in timeout state, the UE will switch to FACH state and reports the
Cell Update to UTRAN through a CCCH, expecting the UTRAN to re-establish this link and
reduce the call drop rate.
When detecting an out-of-sync condition on radio uplink or an RLC Unrecoverable Error,
the UTRAN can deactivate all the radio links of UE, thus driving the UE to trigger call
re-establishment to reduce the call drop rate.
Call re-establishment is a hard handoff, and its channel and cell selection principle is
similar to that of hard handoff. Call re-establishment may select the cell that reports
CELL UPDATE or other cells for the sake of load balance. The channel type adopted for
re-establishment may vary with cell type.

Call Re-establishment process can be described as follows:

1. Processing of Call Re-establishment

When the radio link is interrupted due to poor link quality, the UE in the DCH state
sends a “Cell Update” message with a cause value to the RNC. The RNC then sets
up a radio connection to the UE. See the following figure.

1-1

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-008

As shown in the above figure, the UE in the DCH state sends the CELL UPDATE
message to the RNC. If the cause value is Radio link failure (for example, T313 timer
expires) or RLC unrecoverable error (for example, the uplink RB in the RLC layer is
reset due to repeated data retransmission) and the value of the parameter AM_RLC
error indication (RB2, RB3 or RB4) is FALSE, the RNC initiates the setup of a radio
connection to the UE.
Delete the RL connection of the UE: If the RL connection belongs to the local RNC,
delete the Iub Interface Radio Link. If the RL belongs to another RNC, it notifies the
DRNC to delete the radio link.(for more details, refer to the section “Releasing the Iub
Interface Radio Link” and the section “Releasing the Iur Interface Radio Link”.)
The RNC reconfigures the RB, configures the SRB in the FACH channel, and keeps
the service RB unchanged. (Refer to the section “RB reconfiguration”).
The RNC reconfigures the RB for the UE, reselects the channel, and re-configures the
parameters of the signaling and services according to the selected channel. The RNC
sets up the RL in Node B.
The RNC sends the CELL UPDATE CONFIRM message to the UE, providing
information on the physical channel and RB reconfiguration. To ensure that the UE
correctly receives the message, the RNC sends the message for three consecutive
times, the RRC SN in the three messages remains unchanged.

1-2

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 1 Functional Description

According to the information on the physical channel and RB parameters carried in

the CELL UPDATE CONFIRM message sent by the RNC, the UE reconfigures the
physical channel or RB parameters, and returns a message indicating the completion
of physical channel reconfiguration or RB reconfiguration.
2. Call Re-establishment Triggered By Network
If the global switch of call re-establishment is enabled, RNC will initiates the cell update
call re-establishment procedure to improve the call completion rate and reduce the call
drop rate, when RNC detected the Uu response timeout..or RL fail or RLC unrecover

RNC will start call re-establishment according to different case:

a. In the rb setup procedure, RNC sends a “Radio Bearer Setup” message to UE

and starts Timer1 to wait for response from UE, Timer1 is set to 5 seconds. Upon
receiving the “Response” message from UE, RNC will stop Timer1. If Timer1
expires, the call re-establishment is triggered.

b. In handover procedure, RNC send a “Active Set Update” or “Radio Bear

Reconfiguration” or “transport channel Reconfiguration” or “physical channel
Reconfiguration” message to UE and starts Timer1 to wait for response from Uu,
Timer1 is set to 10 seconds. Upon receiving the “Response” message from UE,
RNC will stop Timer1. If Timer1 expires, the call re-establishment is triggered.

c. When RNC receive “Radio Link Failure Indication” message of all Radio Links
belong to a UE from NodeB, starts Timer1 to wait for Radio link Restore from
NodeB, Timer1 is set to 3 seconds. Upon receiving the “Restore” message from

1-3

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-008

NodeB, RNC will stop Timer1. If Timer1 expires, the call re-establishment is
triggered.
d. When “DL RLC unrecover error ” is detected by RNC, the call re-establishment is
triggered immediately.
If the call re-establishment is triggered:
a. If UE has CS service and T314 is set 0, or UE has PS service and T315 is set
0, RNC will directly release UE instead of call re-establishment. Otherwise, the
following procedure is ongoing.
b. RNC will send a “RADIO LINK ACTIVATION COMMAND” message to the Node
B, to which all radio links of the UE active set belong. Here “CHOICE Delayed
Activation Update” of the cell related to every radio link is set to “Deactivate” in
order to deactivate the radio link.
c. Upon receiving the “RADIO LINK ACTIVATION COMMAND” message, Node B
closes the downlink transmission on related link to drive UE to initiate the Cell
Update procedure as soon as possible.
d. After deactivating the radio links of UE, RNC sets Timer2 to wait for Cell Update.
Timer2 is set to 8 seconds for RB Setup/Reconfiguration/Release Response Timer
Expiration, and set to 10 seconds for others.
After receiving the “CELL UPDATE” message from UE, RNC will stop Timer2 and
initiate the call re-establishment procedure. (For details, see Call Re-Establishment
Procedure.)
If Timer2 expires, ,RNC perform exception handling according to the triggered
cause(eg, RNC perform handover fail process or release call or rb setup fail process).

1-4

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 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: 2

Category: Any
Release: Any

Node B YES V4.11.10.14 None

RNC YES V3.11.10.11 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

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-008

Figure 2-1 Topology

2-2

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

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

MSC/MGW - ZTE
N/A

HLR - ZTE
UE1 subscribes conversational 12.2Kbps voice call.
RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItem
First.rAB_Parameters.trafficClass = eRANAP_TrafficClass_conversational
RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItem
First.rAB_Parameters.maxBitrate.elem[0] = 12200
UE2 subscribes conversational 12.2Kbps voice call.
RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItem
First.rAB_Parameters.trafficClass = eRANAP_TrafficClass_conversational
RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItem
First.rAB_Parameters.maxBitrate.elem[0] = 12200

RNC
Parameters setting in the RNC
—- T313:1
Default value=3
Configuration during the test=1
—- N313

Default value=50
Configuration during the test=1

—- T315

Default value=30
Configuration during the test=50

3-1

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-008

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > Advanced Parameter Manager > UE Timers and Constants
Information > Waiting Time After DPCCH Established in CELL_DCH State Losing
Sychronization(T313)(s)
Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > Advanced Parameter Manager > UE Timers and Constants
Information > Maximum Number of Successive "Out of Sync“ Received form L1
(N313)

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > Advanced Parameter Manager > UE Timers and Constants
Information > Waiting Time for Completion of Cell Update When Radio Link Fails
and Radio Bearer(s) Associated with Exist (T315)(s)
—- N_OUTSYNC_IND
Default value=70
Configuration during the test=255
—- T_RLFAILURE
Default value=4.0
Configuration during the test=25

—- N_INSYNC_IND

Default value=4
Configuration during the test=1

3-2

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 3 Data Configuration

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Advanced Parameter
Manager > Utran Cell > The Number of Consecutive In-Sync Indications NodeB
Received After which RL Restore Procedure Shall be Triggered(N_OUTSYNC_IND)
Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Advanced Parameter
Manager > Utran Cell > The Number of Consecutive Out-of-Sync Indications NodeB
Received After which the Timer T_RLFAILURE Shall be started(N_OUTSYNC_IND)
Path: View > Configuration Management > RNC Managed Element > RNC
Radio Resource Management > UTRAN Cell > UTRAN Cell xxx > Advanced
Parameter Manager > Utran Cell > Timer Length for Trigger Radio Link Failure
Procedure After NodeB Receive N_OUTSYNC_INO Consecutive Out-of Sync
Indication(N_OUTSYNC_IND)(s)

Node B
N/A

3-3

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-008

This page intentionally left blank.

3-4

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

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

4.1 Test Purpose

The purpose of this test case is to verify if the function of Radio Connection
Re-establishment is working normally.
Related document:
ZTE UMTS Connection Management Feature Guide.doc

4.2 Steps for Test

1. UE1 and UE2 camp in Cell1, UE1 activates a voice call to UE2.

2. Take UE1 away from Cell1. Attenuate Cell1’s signal strength until UE1 reports “Cell
Update” with the cause “ radio link failure”.

4-1

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-008

3. Recover Cell1’s signal strength and take UE1 back to Cell1. We can see that the radio
link is deleted and re-established in Cell1. Then RNC return UE “ Cell Update Confirm
“ message.

4.3 Expected Results

Radio link is deleted and reset up in Cell 1 and all the time the call procedure isn’t
interrupted.

4-2

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 5
Counter List
Counter No. Description

C310080001 Number of attempted RRC connection

establishment,Originating Conversational Call

C310080008 Number of attempted RRC connection

establishment,Terminating Conversational Call

C310080170 Number of successful RRC connection

access,MO Conversational Call

C310080177 Number of successful RRC connection

access,MT Conversational Call

C310090254 Number of attempted RAB assignment setup in

cell for CS domain, AMR 12.2K

C311816403 Number of successful call reestablish by network

detect radio link failed

C311815749 Number of received cell update after Inactive

Radio link by network detect radio link failed

C310090252 Number of attempted RAB assignment setup in

cell for CS domain, Conversational

C310090254 Number of attempted RAB assignment setup in

cell for CS domain, AMR 12.2K

C310200711 Number of successful RAB assignment setup in

cell for CS domain, Conversational

C310231208 Number of RNC initiate release by Rab Release

Request for CS domain,AMR 12.2

C310231231 Number of RNC initiate RAB release by Iu release

request for CS domain,AMR 12.2

5-1

SJ-20120802112720-009|2012-08-09 (R1.0) ZTE Proprietary and Confidential