Iur Strategy of Utran Network v1.2

Iur Strategy of Utran Network


ZTE Confidential Proprietary © 2011 ZTE Corporation. All rights reserved.


TABLE OF CONTENTS

Iur Strategy of Utran Network..................................................................................................1

1 Introduction........................................................................................................................ 3

1.1 Purpose.................................................................................................................. 3

1.2 Scope..................................................................................................................... 3

1.3 General Principle....................................................................................................3

1.4 Using IUR and No IUR strategy compare..............................................................4

1.5 Related Parameter.................................................................................................5

Related Parameters for ZTE-SRNC........................................................................................5

2 IUR Strategy Summary.....................................................................................................6

2.1 Strategy for Intra-frequency Scenario with Iur........................................................6

2.1.1 Between ZTE and Ericsson........................................................................6

Strategy for Intra-frequency Scenario between ZTE and Ericsson with Iur.............................6

2.1.2 Between ZTE and HW................................................................................7

Strategy for Intra-frequency Scenario between ZTE and HW with Iur.....................................7

2.1.3 Between ZTE and ZTE...............................................................................7

Strategy for Intra-frequency Scenario between ZTE and ZTE with Iur....................................7

2.2 Strategy for Inter-frequency Scenario with Iur........................................................8


Strategy for Inter-frequency Scenario between ZTE and Ericsson with Iur.............................8


Strategy for Inter-frequency Scenario between ZTE and HW with Iur.....................................8


Strategy for Inter-frequency Scenario between ZTE and ZTE with Iur....................................9

2.3 Strategy for Scenario without Iur............................................................................9






1 Introduction

1.1 PurposeThis document describes the Iur strategy for between ZTE-Ericsson and ZTE-HW RNC

inter-working issues.

1.2 ScopeThis document covers the different service handover and relocation related issues

between ZTE-Ericsson and ZTE-HW in UMTS system. The strategy will focus on both

intra-frequency and inter-frequency handover scenarios. Also there will be some words to

describe the strategy about without Iur connection.

1.3 General PrincipleThe strategies of inter-frequency scenario and without Iur connection scenario are

simpler than intra-frequency scenario. The general principle of intra-frequency Iur

strategy recommended by ZTE are list blow, all of these were got from global Inter-

Operability Test experience.

When ZTE RNC acts as DRNC, the Iur strategy is decided by for Ericsson and HW RNC

that acts as SRNC. No matter what strategy (Relocation/DSCR/Keep via Iur) is can be

support by ZTE-DRNC.

When ZTE RNC acts as SRNC, after the measurement report triggering handover to

Ericsson and HW RNC that acts as DRNC is received, fallback procedure will be

performed firstly if HSPA(HSDPA or HSUPA) service is involved.

We illustrate it in the following figure:



Figure 1 General Principle of Intra-frequency strategy

1.4 Using IUR and No IUR strategy compare

Item Using IUR No IUR

Handover Soft handover success rate is

more than 99%

Customers perceptions is good

Hard handover success rate is

nearly 70%

Customers perceptions is bed

Call Drop Less（SHO SR） More（HHO SR）Pilot pollution

on IUR board

No All over on IUR board

IURlink

load(Relocatio

n)

For continued call From SRNC

to DRNC,IUR Links is release

after relocation

No

IUR link

load(No

Relocation)

For continued call From SRNC

to DRNC,IUR Links is keeping

until that call is release.

No

NOTES: Relocation and no Relocation effect

1. IUR Relocation can save the IUR Link resource.

2. IUR Relocation can reduce the SRNC call drop rate.



3. IUR Relocation will due on DRNC response.IUR strategy between ZTE and ZTE

relocation was on.

1.5 Related ParameterThere are several parameters used to control the strategy when ZTE RNC acted as

SRNC. They can be configured separated to different Target RNC object and

summarized in the table below.

Related Parameters for ZTE-SRNC

Parameters Name Name on the

Interface

Explain

RncFeatSwitch0 Hard-handover With

Relocation

Whether relocation is involved in

hard handover. Value 1 means

hard handover without relocation

and 0 means hard handover with

relocation.

RncFeatSwitch1 Support HSDPA Iur

Interface Process

Whether HSDPA IUR procedure

will be supported. Value 1 means

support and 0 means not support.

RncFeatSwitch2 Support HSUPA Iur

Interface Process

Whether HSUPA IUR procedure

will be supported. Value 1 means

support and 0 means not support.

RncFeatSwitch4 Support Hard

Handover DSCR

Whether Hard Handover DSCR will

be support. Value 1 means support

and 0 means not support.

RncFeatSwitch7 Use DSCR for PS

service when UE all

RLs need moved to

DRNC

Whether PS service will DSCR in

DRNC. Value 1 means perform

DSCR and 0 means not perform.

RNCFeatSwitch10 Support UE not

Involved Relocation

for CS Service

Whether UE not involved relocation

procedure will be support for CS

Service. Value 1 means support


RNCFeatSwitch11 Support UE not

Involved Relocation

for PS Service

Whether UE not involved relocation

procedure will be support for PS

Service. Value 1 means support


bAal2Server Peer RNC is AAL2

Server

Whether DRNC is AAL2 server or

not. Value 1 means YES and 0

means NOT. Need set it to “YES”

because the ATM address in radio-



link-setup-response message is not

RNC’s but NodeB’s when Ericsson

RNC acting as DRNC and transport

network is ATM. Other situation

need set to “NO”.

IMPORTANT NOTE:

1. Some of these parameters are imported in version RNCV3.07.310p and RNCV3.09.30

and can not apply to any previous versions.

2. For some historical reason, to enable DSCR feature, we must set both RNCFeatSwitch11

and RNCFeatSwitch7 to one. Maybe we will get rid of this confusing limit in the future

version.

2 IUR Strategy Summary

2.1 Strategy for Intra-frequency Scenario with Iur

2.1.1 Between ZTE and Ericsson

Strategy for Intra-frequency Scenario between ZTE and Ericsson with Iur

Services ZTE -> Ericsson Ericsson ->ZTE

Voice (AMR 12.2kbps) SHO, without relocatoin SHO, without relocatoin

PS Release 99 DSCR DSCR

HSPA Fall back to DCH & DSCR Fall back to DCH & DSCR

Voice+R99 Multi-Rab SHO

If Cs release, Ps DSCR

If Ps release, Cs SHO

Multi-Rab SHO



Voice+HSPA Fall back to DCH,

Multi-Rab SHO



Fall back to DCH,

Multi-Rab SHO



Video SHO, without relocatoin SHO, without relocatoin



NOTES: According to the test result from TRT of KPN for intra-frequency scenario,

Ericsson RNC does not support:

1. UE not involved relocation of CS service.

2. Relocation procedure for all kind of PS services.

2.1.2 Between ZTE and HW

Strategy for Intra-frequency Scenario between ZTE and HW with Iur

Services ZTE -> HW HW ->ZTE

Voice (AMR 12.2kbps) SHO, without relocatoin SHO, without relocatoin

PS Release 99 SHO, relocation SHO, relocation

HSPA Fall back to DCH &

relocation

Fall back to DCH &

relocation

Voice+R99 Multi-Rab SHO

If Cs release, Ps relocation

If Ps release, Cs hold on

Multi-Rab SHO



Voice+HSPA Fall back to DCH,

Multi-Rab SHO



Fall back to DCH,

Multi-Rab SHO



Video SHO, without relocatoin SHO, without relocatoin

NOTES: According to the test result from lab of China UniCom for intra-frequency

scenario, HW RNC does not support UE not involved relocation of CS service. And there

are some unclear issues when HSPA service over Iur interface.

2.1.3 Between ZTE and ZTE

Strategy for Intra-frequency Scenario between ZTE and ZTE with Iur

Services ZTE<->ZTE

Voice (AMR 12.2kbps) SHO, relocation

PS Release 99 SHO, relocation

HSPA SHO, relocation



Voice+R99 SHO, relocation

Voice+HSPA SHO, relocation

Video SHO, relocation

2.2 Strategy for Inter-frequency Scenario with Iur


Strategy for Inter-frequency Scenario between ZTE and Ericsson with Iur

Services ZTE -> Ericsson Ericsson ->ZTE

Voice (AMR 12,2kbps) Ue involved relocation Ue involved relocation

PS Release 99 DSCR DSCR

HSDPA DSCR DSCR

Voice+R99 Multi-Rab hold


If Ps release, Cs relocation

Ps DSCR

Cs involved relocation

Voice+HSDPA Multi-Rab hold


If Ps release, Cs relocation

Ps DSCR

Cs involved relocation

Video Ue involved relocation Ue involved relocation

NOTES: According to the test result from TRT of KPN for inter-frequency scenario,

Ericsson RNC does not support relocation procedure for all kind of PS services. And

there are some unclear issues when HSPA service over Iur interface. And UE will

negative respond when hard handover from ZTE RNC to Ericsson RNC.


Strategy for Inter-frequency Scenario between ZTE and HW with Iur

Services ZTE -> HW HW ->ZTE

Voice (AMR 12,2kbps) Ue involved relocation Ue involved relocation



PS Release 99 Ue involved relocation Ue involved relocation

HSDPA Fall back to DCH & Ue

involved relocation

Fall back to DCH & Ue

involved relocation

Voice+R99 Ue involved relocation Ue involved relocation

Voice+HSDPA Fall back to DCH & Ue

involved relocation

Fall back to DCH & Ue

involved relocation

Video Ue involved relocation Ue involved relocation

NOTES: Because we had not tested inter-frequency scenario with HW RNC before, we

don’t know is there any issue about HW RNC.


Strategy for Inter-frequency Scenario between ZTE and ZTE with Iur

Services ZTE<->ZTE

Voice (AMR 12.2kbps) Ue involved relocation

PS Release 99 Ue involved relocation

HSPA Ue involved relocation

Voice+R99 Ue involved relocation

Voice+HSPA Ue involved relocation

Video Ue involved relocation

2.3 Strategy for Scenario without Iur


If there is no Iur connection between ZTE and Ericsson RNC, the strategy is same as

Inter-frequency scenario. Please refer to section 2.2.1.




If there is no Iur connection between ZTE and HW RNC, the strategy is same as Inter-

frequency scenario. Please refer to section 2.2.12.


If there is no Iur connection between ZTE and ZTE RNC, the strategy is same as Inter-

frequency scenario. Please refer to section Error: Reference source not found3.


Documents

Iur Strategy of Utran Network v1.2