Вы находитесь на странице: 1из 18

Feature Deployment and Testing Guide

SRNS Relocation
Feature ID: ZWF21-03-020

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-041

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

SJ-20120802112720-041|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-041|2012-08-09 (R1.0) ZTE Proprietary and Confidential


II

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


Chapter 1
Functional Description
SRNS relocation can be categorized into relocation UE not involved (soft handover
triggered) and relocation UE involved (hard handover triggered) according that whether
UE is involved.
Relocation UE not involved: It is soft handover relocation namely, and UE can use radio
resource in DRNC and connect with CN through SRNC. The trigger condition is:
There is an Iur interface between RNCs.
The switch of relocation UE not involved is open. It is differentiated by CS service and PS
service, RncFeatSwitch bit10 is for CS service and RncFeatSwitch bit11 for PS service.

When all radio links are handed over to DRNC, timer is activated (CsReDelayTimer and
PsReDelayTImer are configured according to CS service and PS service respectively, the
timer of CS service is considered for multi-RAB service) and relocation is performed when
the corresponding timer is overtime.
Relocation UE involved: Namely it is hard handover relocation. The trigger condition is:
The switch of relocation UE involved RncFeatSwitch bit0 is open

The special relocation handling of CS+PS service: If UE has CS and PS Service


simultaneously and DRNC of network vendor doesn't support PS relocation, the PS
service will be released before SRNC relocation with hard handover when the parameter
RncFeatSwitch bit4 is set to “1”, the CS service will begin relocation as soon as PS
is released. As a result, the CS call will be kept, and the PS will reestablished by UE
automatically.
Figure 1-1 and Figure 1-2 shows the Intra-RNC soft handover.

1-1

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


Feature Deployment and Testing Guide Feature ID: ZWF21-03-020

Figure 1-1 Intra-RNC soft handover (Add a radio link)

1-2

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


Chapter 1 Functional Description

Figure 1-2 Intra-RNC soft handover (Delete a radio link)

Figure 1-3 shows the procedure description.

Figure 1-3 Relocation triggered by soft handover

1-3

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


Feature Deployment and Testing Guide Feature ID: ZWF21-03-020

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 CS and PS domains. When SRNC sends the Relocation Required
message, it shall start the timer Trelocprep. Upon reception of the Relocation
Command message, SRNC shall stop the timer and terminate the Relocation
Preparation procedure. If there is no response from the CN to the Relocation Required
message before expiry of timer Trelocprep, SRNC shall cancel 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 “RAB SETUP”
message.
3. After the RAB of DRNC is established successfully, the DRNC sends “Relocation
Request Ack” message to the CN.
4. The CN sends “Relocation Command” message to the SRNC requiring the SRNC to
start relocation. Upon reception of the Relocation Command message, SRNC shall
stop the timer Trelocprep, start the timer Trelocoverall and terminate the Relocation
Preparation procedure. If the Iu Release procedure is not initiated towards SRNC
from CN before expirty of Trelocoverall, SRNC shall initiate the Iu Release Request
procedure towards CN with cause “Trelocoverall expiry”.
5. The SRNC sends “Relocation Commit” message to the DRNC through the lur interface.
6. The DRNC sends “Relocation Detect” message to the CN and is converted into a new
SRNC through role exchange.
7. The new SRNC sends “UTRAN Mobility Information” message to UE to relocate
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 “Relocation Complete” message to inform the CN of the
successful relocation.
10. Upon receiving the message from the new SRNC, CN sends “Iu Release Command”
message to the original SRNC to release all the resources in the original SRNC.
11. Upon releasing the lu resource, original SRNC sends “Iu Release Complete” message
to the CN.
12. There may be some exceptional procedures during relocation.

Relocation failure caused by “UTRAN Mobility Information” message transmission


failure.
The DRNC fails to initiate the “UTRAN Mobility Information Configuration” procedure due
to procedure timeout or the UE failure in returning UTRAN mobility message. In such a
case, the DRNC does not send a “Relocation Complete” message to the CN, and after
the CN relocation timer times out, the CN initiates a “Iu Release Command” message to
release the resources on the DRNC side.

1-4

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


Category: Any
Release : R99

NodeB YES V4.11.10.14

RNC YES V3.11.10.11

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-041|2012-08-09 (R1.0) ZTE Proprietary and Confidential


Feature Deployment and Testing Guide Feature ID: ZWF21-03-020

Figure 2-1 Topology

2-2

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


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

MSC/MGW - ZTE
Usually, the default configuration supports 12.2k AMR speech. In the
“RAB_AssignmentRequestMsg” message, MSC indicates the traffic class and the
MBR/GBR:
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
RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_SetupOrModifyItem
First.rAB_Parameters.guaranteedBitRate.elem[0] = 12200

HLR – ZTE
N/A

RNC
l DUARFCN: 10637 (Cell1 and Cell2 have the same frequency. Cell1 belongs to
RNC1/NodeB1. Cell2 belongs to RNC2/NodeB2)

3-1

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


Feature Deployment and Testing Guide Feature ID: ZWF21-03-020

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xxx > Cell Setup Parameters
> DUARFCN
l RNC Identity: 11 (RNC Identity of RNC2)
l Cell Identity: 301 (Cell Identity of Cell2)
l Location Area Code: 15 (Location Area Code of Cell2)
l Mobile Country Code: 460 (Mobile Country Code of Cell2)
l MNC BCD Code Length: 2 (MNC BCD Code Length of Cell2)
l Mobile Network Code: 15 (Mobile Network Code of Cell2)

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > External UTRAN Cell > Global Information > RNC
Identity
l DUARFCN: 10637 (downlink frequency of Cell2)
l Cell Primary Scrambling Code: 301 (Cell Primary Scrambling Code of Cell2)
l HSPA Support Method: HSUPA, HSDPA, and DCH (Cell2 Support HSUPA, HSDPA,
and DCH)

3-2

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


Chapter 3 Data configuration

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > External UTRAN Cell > Global Else > DUARFCN
l Cell Identity: 1611 (Cell Identity of Cell1)
l Neighbouring Physical Cell Identity: 721197 (Physical Cell Identity of Cell2)
l Dose Neighbouring Cell Belong to Self Physical RNC: False (Cell1 belongs to
RNC1/NodeB1. Cell2 belongs to RNC2/NodeB2)
l Share Cover Indication: Neighbor (Cell1 and Cell2 adjacent cells with different
coverage)

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > Neighbouring Cell > Neighbouring Cell
xxx > Share Cover Indication

l HSPA Support Method: HSUPA, HSDPA, and DCH (Cell1 and Cell2 Support HSUPA,
HSDPA, and DCH)

3-3

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


Feature Deployment and Testing Guide Feature ID: ZWF21-03-020

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell > UTRAN Cell xxx > Cell
Ability and Cell Reselection > HSPA Support Method

NodeB
N/A

3-4

SJ-20120802112720-041|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 the SRNC relocation procedure is normal.
Related documents:

l ZTE UMTS Handover Control Feature Guide.doc

4.2 Steps for Test


1. UE1 camps on Cell1 in Idle mode.
2. UE1 makes an AMR 12.2Kbps voice call to UE2. Hold the call.
From “RAB_AssignmentRequestMsg” message, the traffic class is conversationl, the
max bit rate and guaranteed bit rate is 12.2Kbps.

3. UE1 moves from Cell1 to Cell2 to trigger event 1A and 1B (For details, see
ZWF21-03-006 Inter-RNC Handover with Iur Support.docx).
4. Relocation is performed after event 1B. From “RelodationRequireMsg” message, the
source RNC ID is 12, the target RNC ID is 11.

4-1

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


Feature Deployment and Testing Guide Feature ID: ZWF21-03-020

From “RelodationRequestMsg” message of DRNC, the traffic class is conversationl,


the max bit rate and guaranteed bit rate is 12.2Kbps.

From “IU_ReleaseCommandMsg” message of SRNC, the cause of IuRelease is


relocation.

5. Release the AMR voice call.

4.3 Expected Results


The voice call is established successfully. UE1 performs the relocation procedure
successfully.

4-2

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


Chapter 5
Counter List
C310342745

C310342746

C310342747

C310342748

C310342749

C310342750
Number of attempted relocation preparation with UE not involved for CS domain,
C310342751 by cause

C310342752

C310342753

C310342754

C310342755

C310342756

C310342757

C310342758

C310342759

C310342760 Number of failed relocation preparation with UE not involved for CS domain, by cause

C310342761 Number of attempted outgoing relocation with UE not involved for CS domain

C310342762

C310342763 Number of failed outgoing relocation with UE not involved for CS domain, by cause

C310342837

C310342838

C310342839

C310342840

C310342841

C310342842
Number of attempted incoming relocation with UE not involved for CS domain, by
C310342843 cause

5-1

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


Feature Deployment and Testing Guide Feature ID: ZWF21-03-020

C310342844

C310342845

C310342846

C310342847

C310342848 Number of failed incoming relocation with UE not involved for CS domain, by cause

5-2

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