multi carrier strategyv1.4

Multi-carrier Strategy



Version Date Author Approved By Remarks

V0.1 27-04-2011 Fulei Liu Create

V0.2 5-5-2011 Fulei Liu

Put IOT strategy between

ZTE RNC and other

vendors with Iur in section

5.2.

V0.3 10-5-2011 Fulei Liu

Add the comparison of ZTE

strategy in chapter 2 and

current network strategy in

chapter 3 to chapter 3.4.

V0.4 16-5-2011 Fulei LiuUpdate Cons of ZTE

strategy in chapter 3.4.

ZTE Confidential Proprietary © 2023 ZTE Corporation. All rights reserved. 2

© 2023 ZTE Corporation. All rights reserved.ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used without the prior written permission of ZTE.Due to update and improvement of ZTE products and technologies, information in this document is subjected to change without notice.


TABLE OF CONTENTS

1 OVERVIEW............................................................................................................................... 5

2 ZTE MULTI-CARRIER OPERATION..............................................................................................6

2.1 Scenario..................................................................................................................................6

2.2 Strategy...................................................................................................................................6

2.2.1 Operation Intra 3G..............................................................................................................6

2.2.2 Operation between 3G and GSM........................................................................................8

2.3 Parameters..............................................................................................................................9

3 MULTI-CARRIER STRATEGY IN CURRENT NETWORK.................................................................15

3.1 Scenario................................................................................................................................15

3.2 Strategy.................................................................................................................................15

3.2.1 Operation Intra 3G............................................................................................................15

3.2.2 Operation between 3G and GSM......................................................................................16

3.3 Parameters............................................................................................................................16

3.4 Comparison...........................................................................................................................18

4 INTERWORKING WITH OTHER VENDORS................................................................................20

4.1 Scenario................................................................................................................................20

4.1.1 Intra-frequency Scenario...................................................................................................20

4.1.2 Inter-frequency Scenario...................................................................................................21

4.2 Strategy.................................................................................................................................22

4.3 Parameters............................................................................................................................24

5 APPENDIX.............................................................................................................................. 24

5.1 Multi-carrier strategy after swap..........................................................................................25

5.1.1 Scenario............................................................................................................................25

5.1.2 Strategy............................................................................................................................25

5.1.3 Parameter.........................................................................................................................26

5.2 Interworking with other vendors with Iur.............................................................................27



FIGURES

Figure 1 Multi-carrier operation of the entire network.................................................6

Figure 2 Multi-carrier operation intra 3G....................................................................6

Figure 3 Multi-carrier operation between 3G and 2G.................................................8

Figure 4 Multi-carrier operation in current network...................................................15

Figure 5 Intra-frequency operation with other vendors.............................................21

Figure 6 1st Inter-frequency operation with other vendors.......................................21

Figure 7 2nd Inter-frequency operation with other vendors......................................22

Figure 8 Multi-carrier strategy after swap.................................................................25

TABLES

Table 1 Related parameter of cell configuration.......................................................9

Table 2 Related parameter of 3G cell reselection...................................................10

Table 3 Related parameter of 2G cell reselection...................................................11

Table 4 Related parameter of load and service balance.........................................12

Table 5 Related parameter of inter-frequency and inter-RAT handover.................12

Table 6 Parameter Settings for ZTE-SRNC to ZTE-DRNC.....................................14

Table 7 Related parameter of cell configuration.....................................................16

Table 8 Related parameter of load and service balance.........................................17

Table 9 Strategy for Intra-frequency between ZTE and Ericsson/HW without Iur...22

Table 10 Strategy for Inter-frequency between ZTE and Ericsson/HW without Iur...23

Table 11 Related parameter of cell configuration.....................................................26

Table 12 Strategy for Intra-frequency between ZTE and Ericsson/HW with Iur........27

Table 13 Strategy for Inter-frequency between ZTE and Ericsson/HW with Iur........28

Table 14 Parameter Settings for ZTE-SRNC to Ericsson/HW-DRNC.......................29



1 Overview

Chapter 2 provides ZTE multi-carrier strategy, which is used during swap.

Chapter 3 provides multi-carrier strategy of current network, which is implemented by

ZTE configuration.

Chapter 4 presents the IOT strategy between ZTE RNC and other vendors without

Iur.

In the appendix, the multi-carrier strategy after swap is proposed in section 5.1. The

IOT strategy between ZTE RNC and other vendors with Iur is put in section 5.2.

During swap, two multi-carrier strategies are provided in chapter 2 and chapter 3,

ZTE proposes to use ZTE strategy in chapter 2. Which strategy, in chapter 4 or in

chapter 5.2, will be chosen is depended on the test result.



2 ZTE Multi-carrier operation

2.1 Scenario

Figure 1 Multi-carrier operation of the entire network

2.2 Strategy

2.2.1 Operation Intra 3G

Figure 2 Multi-carrier operation intra 3G

1) Camping and cell reselection



F1, F2 and F3 are all access layer. UE can camp on any of them according to cell’s

signal quality.

2) Load sharing and traffic distribution

Since three carriers can support R99+HSPA, the load balance is implemented by

inter-frequency cell reselection in idle mode, and there is no service balance.

3) Handover

(a) UE can play intra-frequency handover on each layer F1/F2/F3.

(b) At the boundary of F2/F3, UE hands over to F1.

4) Iur strategy between ZTE SRNC and ZTE DRNC

The intra-frequency and inter-frequency handover strategies via Iur for all kinds of

services are shown below.

Strategy for Intra-frequency between ZTE and ZTE with Iur

Services ZTE <=> ZTE

CS (AMR

12.2kbps)

SHO, relocation

R99 PS SHO, relocation

HSPA SHO, relocation

Voice+R99 SHO, relocation

Voice+HSPA SHO, relocation

Video SHO, relocation

Strategy for Inter-frequency between ZTE and ZTE with Iur


CS (AMR

12.2kbps)

HHO, Ue involved relocation

R99 PS HHO, Ue involved relocation




HSPA HHO, Ue involved relocation

Voice+R99 HHO, Ue involved relocation

Voice+HSPA HHO, Ue involved relocation

Video HHO, Ue involved relocation

2.2.2 Operation between 3G and GSM

Figure 3 Multi-carrier operation between 3G and 2G

1) Operation between ZTE F1 and GSM

(a) In IDLE mode, when F1 coverage is bad, UE reselects to GSM. When F1

coverage becomes good, UE reselects back to F1.

(b) For voice call, when F1 coverage is bad, UE can handover to GSM. When UE

finishes its voice call in GSM, it reselects back to ZTE F1

(c) For video call, if both RNC and CN allow video call fallback to CS 12.2k, and UE

has this function too, video call can fall back to CS and then hand over to GSM.



Otherwise, video call will drop and cannot hand over to GSM. By default, ZTE RNC

allow video call fall back to CS.

(d) For R99 PS, UE can handover to GSM. R99 PS services can reselect back to F1

when the coverage of F1 is good

(e) For HSPA, by ZTE default, HSDPA compressed mode is activated and can go to

GSM directly; While HSUPA falls back to DCH, and compressed mode is activated

and then goes to GSM. There are two parameters to control that.

The neighboring relations between F1 and GSM,

Both GSM900 and GSM1800 exist, F1 configures GSM900 and GSM1800.

GSM900 only exist, F1 configures GSM900.

GSM1800 only exist, F1 configures GSM1800

2) Operation from ZTE F2/F3 to GSM

In some cases, F1 does not have good coverage, so UE need reselect or hand over

to GSM.

2.3 ParametersNotes: (1) The value not presented in tables below uses ZTE default value.

Table 1 Related parameter of cell configuration

ZTE parameter

nameRange ZTE F1 ZTE F2 ZTE F3

HspaSptMeth 0: Not Support

HSUPA and

HSDPA;

1: Support HSDPA

and DCH;

2: Support HSDPA

only;

3: Support

HSUPA , HSDPA

3: Support

HSUPA ,

HSDPA and

DCH;

3: Support

HSUPA , HSDPA

and DCH;

3: Support

HSUPA , HSDPA

and DCH;



and DCH;

4: Support HSUPA

and HSDPA

ShareCover

0: Neighbor

1: Overlap

2: Covers

3: Contained in

F1-> co-

sector

F2/F3:

1: Overlap

F2-> co-sector

F1/F3:

1: Overlap

(At the boundary)

F2->not-co-

sector F1: 0:

Neighbor

F3-> co-sector

F1/F2:

1: Overlap;

(At the boundary)

F3->not-co-sector

F1: 0: Neighbor

Statemode 0: Idle State Only

1: Cell_DCH State

Only

2: Connected

State, Non-

Cell_DCH

3: Idle State +

Cell_DCH State

4: Idle State +

Connected State,

Non-Cell_DCH

5: Cell_DCH State

+ Connected State,

Non-Cell_DCH

6: Idle State +

Cell_DCH State+

Connected State,

Non-Cell_DCH

F1-> co-

sector

F2/F3: 0

F2-> co-sector

F1/F3: 0

(At the boundary)

F2->not-co-

sector F1: 6

F3-> co-sector

F1/F2: 0

(At the boundary)

F3->not-co-sector

F1: 6

Table 2 Related parameter of 3G cell reselection

ZTE parameter


QualMeas1: CPICH Ec/No

2: CPICH RSCP

1: CPICH

Ec/No

1: CPICH

Ec/No

1: CPICH

Ec/No

SInterSearchPre0: False

1: True0: False 0: False 0: False

Sintersearch(0..20 )dB Step

2dB10dB 10dB 10dB

OtherRATInfoPre 0: False 1: True 1: True 1: True



ZTE parameter


1: True

SSearchRat(0..20 )dB Step

2dB0dB 0dB 0dB

Qqualmin(-24..0)dB step

1dB

-

18dB(current

network -

17dB)

-

18dB(current

network -

17dB)

-18dB(current

network -17dB)

QRxLevMin(-115..-25)dBm

Step2dBm-115dBm -115dBm -115dBm

Qhyst1s(0..40)dB step2

dB

10dB(current

network 4dB)

10dB (current

network 4dB)

10dB(current

network 4dB)

Qhyst2s(0..40)dB step2

dB2dB 2dB 2dB

Qoffset1SNSib11 (-50..50)dB

0dB (F1-

>F2/F3)

0dB

(F2>F1/F3)

0dB

(F3>F1/F2)

0dB

(HW:0dB)

(E: 7dB)

(F1->GSM)

0dB

(HW:0dB)

(E: 7dB)

(F2->GSM)

0dB

(HW:0dB)

(E: 7dB)

(F3->GSM)

Qoffset2SNSib11 (-50..50)dB0dB

(F1->F2/F3)

0dB

(F2>F1/F3)

0dB

(F3>F1/F2)

Table 3 Related parameter of 2G cell reselection

Parameter name Range GSM->3G

Qsearch_I

[0..15]

0 = - 98 dBm, 1 = - 94 dBm, …

,

6 = - 74 dBm, 7 = always

8 = - 78 dBm, 9 = - 74 dBm, …

,

14 = - 54 dBm, 15 = never

7(has 3G

neighbor);

15(do not

have 3G

neighbor)

FDD_Qoffset

[0..15]

0 = always

1 = -28 dB, 2 = -24 dB, … , 15

= 28 dB

0

FDD_Qmin

[0..7]

0= -20dB, 1= -6dB, 2= -18dB,

3= -8dB, 4= -16dB, 5= -10dB,

6= -14dB, 7= -12dB

7= -12dB



Table 4 Related parameter of load and service balance

ZTE parameter

name

Range ZTE F1 ZTE F2 ZTE F3

InitRrcLBSw 0:Off

1: Inter-frequency Switch On

0 0 0

RabAssLBSw 0: Off

1: Inter- frequency Switch On

2: Inter-system Switch On

3:Inter-frequency and Inter-

system Switch On

0 0 0

CallHoldLBSw 0: Off


2: Inter-system Switch On

3: Inter-frequency and Inter-

system Switch On

0 0 0

InitRrcSBSw 0: Off

1: On

0 0 0

RabAssSBSw 0:Off

1: On

0 0 0

CallHoldSBSw 0:Off

1: On

0 0 0

Table 5 Related parameter of inter-frequency and inter-RAT handover

ZTE

parameter

name

Range F1 F2/F3

NonIntraM

easQuan

0： Ec/No

1： RSCP

2: Ec/No and RSCP

2: Ec/No and RSCP 2: Ec/No and RSCP

IfOrRatHo

Swch

0: Turn off Inter-frequency and

Inter-RAT Handover

1: Only Inter Frequency

2: Only Inter RAT

3: Inter Frequency Is Prior to Inter

RAT

2: Only Inter RAT 3: Inter Frequency Is

Prior to Inter RAT

InterHoTa

ctic

0: Algorithm Deciding

1: 2A Event Trigger

2: 2B Event Trigger

3: 2C Event Trigger

/ 1: 2A Event Trigger

InterMeas 0: UE Period Report Parameters 9 7



ZTE

parameter

name

Range F1 F2/F3

CfgNote

for CPICH Ec/No

3: UE Inter-frequency Event

Report Parameters for CPICH

Ec/No

4: UE Period Report Parameters

for CPICH RSCP



RSCP



Ec/No(GSM)



RSCP(GSM)

ThreshUse

dFreq

CPICH RSCP: (-115..-25 )dBm

step 1dBm

CPICH Ec/No: (-24..0) dB step

1dB

2D/2F:

Voice:2D: -100dBm/-14dB2F: -97dBm/-11dBPS:2D: -110dBm/-15dB2F: -107dBm/-12dB

2D/2F:

Voice:2D: -95dBm/-14dB2F: -92dBm/-11dBPS:2D: -95dBm/-14dB2F: -92dBm/-11dB

ThreshNo

UsedFreq

CPICH RSCP: (-115..-25 )dBm

step 1dBm

CPICH Ec/No: (-24..0) dB step

1dB

/

2E： Voice/PS:2E: -97 dBm/-14dB

Hysteresis (0, 0.5..14.5)dB step 0.5dB 2D/2F:

2D: 2dB2F: 2dB

2A/2D/2F/2E:

2A: 4dB2D: 2dB2E: 4dB2F: 2dB

TrigTime (0, 10, 20, 40, 60, 80, 100, 120,

160, 200, 240, 320, 640, 1280,

2560, 5000)ms

2D/2F:

2D/2F: 640 ms

2A/2D/2F/2E:

2A: 100ms

2E: 100ms

2D/2F: 640 ms

GsmShare

Cover

0: Neighbor;

1: Overlap;

2: Covers;

0: Neighbor (not-co-

site)

1: Overlap(co-site)

0: Neighbor (not-co-

site)

1: Overlap(co-site)



ZTE

parameter

name

Range F1 F2/F3

3: Contained in

RatHoTact

ic

0: Algorithm Deciding

1: 3A Event Trigger

2: 3C Event Trigger

1: 3A Event Trigger

1: 3A Event Trigger

ThreshCPICH RSCP: (-115..-25 )dBm

step 1dBm

3A:

Voice/PS3A: -95 dBm/-14dB

3A:

Voice/PS3A: -95 dBm/-14dB

ThreshSysCPICH RSCP: (-115..-25 )dBm

step 1dBm

3A:

Voice/PS3A: -102 dBm

3A:

Voice/PS3A: -102 dBm

HsdpaCm

AssoMode

0: Serial

1: Parallel1: Parallel 1: Parallel

HsupaCm

AssoMode

0: Serial

1: Parallel0: Serial 0: Serial

Cs64RbM

odeSwch

0: Not Support SCUDIF

1: Support SCUDIF, CS64

Service Established by a RB

1: Support SCUDIF,

CS64 Service

Established by a RB

1: Support SCUDIF,

CS64 Service

Established by a RB

Table 6 Parameter Settings for ZTE-SRNC to ZTE-DRNC

ZTE parameter name Name on the Interface ZTE<=> ZTE Default

Value

RncFeatSwitch0 Hard-handover With Relocation 0 0

RncFeatSwitch1 Support HSDPA Iur Interface Process 1 1

RncFeatSwitch2 Support HSUPA Iur Interface Process 1 1

RncFeatSwitch4 Support Hard Handover DSCR 0 0

RncFeatSwitch7 Use DSCR for PS service when UE all RLs

need moved to DRNC

0 0

RNCFeatSwitch10 Support UE not Involved Relocation for

CS Service

1 1

RNCFeatSwitch11 Support UE not Involved Relocation for

PS Service

1 1

Notes: Parameters in table 6 can be used for intra- and inter-frequency with Iur scenarios.



3 Multi-carrier strategy in current network

3.1 Scenario

Figure 4 Multi-carrier operation in current network

3.2 Strategy

3.2.1 Operation Intra 3G

1) Camping in idle mode

F1 is the access layer. UE can camp on F1 only.

F2 and F3 are barred. No UE can access to them.

In this case, only F1 works in idle mode.


F1 supports R99+HSPA and it is set as R99 preferred.

F2 and F3 support R99+HSPA and they are set as HS preferred.



Since all three carriers support R99+HSPA and F1 is access layer, load balance

feature needs to be activated. Due to traffic of R99 and HS are distributed to different

carriers, service balance also needs to be used.

In current network, HS redirection happens during RAB assignment. Therefore,

during 1st RAB assignment, the behavior of each category of UE on F1 are listed

below,

When R99 UE initiates voice call or R99 PS, it stays on F1.

When R5/R6+ UE initiate CS only, it will be kept on F1. When R5/R6+ UE initiate

HS only, it might be moved from F1 to F2/F3 depending on the load of F1/F2/F3.

If R5/R6+ UE with HS on F2/F3 initials another CS RAB, the UE with multi-RAB

will be kept on F2/F3 and does not handover to F1. If UE releases HS first, then

UE with CS only will not be moved to F1 by ZTE default.

3) Handover

Refer to section 2.2.1.

4) Iur strategy between ZTE SRNC and ZTE DRNC


3.2.2 Operation between 3G and GSM


3.3 Parameters

Notes: Other parameters refer to section 2.3.




ZTE

parameter

name


CellBarredIn

d

1: Barred

2: Not Barred2 1 1

TBarred(10,20,40,80,160,320,640,1280)

s10s 10s 10s

HspaSptMeth

0: Not Support HSUPA and

HSDPA;

1: Support HSDPA and DCH;

2: Support HSDPA only;

3: Support HSUPA , HSDPA and

DCH;

4: Support HSUPA and HSDPA

3:

Support

HSUPA ,

HSDPA

and

DCH;

3: Support

HSUPA , HSDPA

and DCH;

3: Support

HSUPA , HSDPA

and DCH;

ShareCover

0: Neighbor

1: Overlap

2: Covers

3: Contained in

F1-> co-

sector

F2/F3:

1:

Overlap

F2-> co-sector

F1:

1: Overlap

(At the boundary)

F2->not-co-

sector F1: 0:

Neighbor

F3-> co-sector F1

1: Overlap;

(At the boundary)

F3->not-co-

sector F1: 0:

Neighbor


1: Cell_DCH State Only

2: Connected State, Non-

Cell_DCH

3: Idle State + Cell_DCH State

4: Idle State + Connected State,

Non-Cell_DCH

5: Cell_DCH State + Connected

State, Non-Cell_DCH

6: Idle State + Cell_DCH State+

Connected State, Non-Cell_DCH

F1-> co-

sector

F2/F3: 1

F2-> co-sector

F1: 0

(At the boundary)

F2->not-co-

sector F1: 6

F3-> co-sector

F1: 0

(At the boundary)

F3->not-co-

sector F1: 6

Table 8 Related parameter of load and service balance

ZTE parameter

name


InitRrcLBSw 0:Off 0 0 0



ZTE parameter

name



RabAssLBSw 0: Off1: Inter- frequency Switch On2: Inter-system Switch On 3:Inter-frequency and Inter-system Switch On

1 0 0

CallHoldLBSw 0: Off1: Inter-frequency Switch On2: Inter-system Switch On3: Inter-frequency and Inter-system Switch On

0 0 0

DlLdBalPwrSwch 0: Off

1: On

0 0 0

LdBalCdSwch 0: Off

1: On

0 0 0

UlLdBalPwrSwch 0: Off

1: On

0 0 0

LdBalHsSwch 0: Off

1: On

1 0 0

DlLdBalHsWeight (0..100%) step 1% 100% 0% 0%

DlLdHsThdHsd (0..100%) 80% 80% 80%

ExtraCDeltaHsTrd (0..100%) 5% 0% 0%

InitRrcSBSw 0: Off 1: On

0 0 0

RabAssSBSw 0:Off1: On

1 0 0

CallHoldSBSw 0:Off1: On

0 0 0

PrefTrafType

Bit0=0/1: CS No Preferred / CS PreferredBit1=0/1: R99 PS No Preferred / R99 PS PreferredBit2=0/1: HS PS No Preferred / HS PS PreferredBit3~Bit7: Reversed, fixed to 0

Bit0=1Bit1=1Bit2=0Bit3~Bit7=0



CsHo4MulRab 0:Off 0 0 0



ZTE parameter

name


Swch 1: On

3.4 Comparison This chapter presents the pros and cons of ZTE strategy in chapter 2 and current

network strategy in chapter 3.

Pros Cons

ZTE

strategy

1. Idle mode: three carriers can absorb

users, especially, at the airport or

harbor, operators has more chance to

attract users.

2. CELL_DCH: No RRC or RAB

redirection (Load/service balance), no

impact on user successful access rate

and no blind handover call drop

3. Result: number of users on each

carrier is almost same. The load is

almost balanced on each carrier.

4. This network structure is not

influenced by traffic and UE type

changes and can be used in many

different situations. For example,

currently, voice is more and PS is less;

but in future, voice decreases and PS

increases.

5. Use case: several commercial

networks choose it, for example, in

Compared with “Current network

strategy”, co –sector F2 and F3 are

required to have neighboring relations

with each other in this strategy.



Europe and HK.

Current

network

strategy

Load can be balanced from F1 to F2

and F3.

Service can be redirected to F2 and F3.

1. Idle mode: Since F2 and F3 are barred,

only F1 can be used to absorb users.

2. Since F2 and F3 are barred, UE will

periodically try to camp on F2/F3 and read

F2/F3 system information, and later

reselect to F1, which is controlled by a

timer (Tbarred). In this case, UE

consumes powers to make useless

behavior. Moreover, it is need to test and

check whether all categories of UE can

make correct behavior after reading

“Barred”.

3. CELL_DCH: During RAB assignment,

there is service redirection which is blind

handover and will impact inter-frequency

call drop rate.

4. If voice is more than PS in current

network, F1 might be easy to be

congested and more voice need to be

redirected to F2/F3 which increase call

drop rate. Moreover, when Voice

redirection occurs and if UEA1 encryption

is enabled, water sound occurs.



4 Interworking with other vendors

4.1 ScenarioSince the whole network is swapped cluster by cluster, the scenarios that intra- or

inter- frequency operations may exist between ZTE and Ericsson/HW.

4.1.1 Intra-frequency Scenario One typical scenario of intra-frequency operations is shown below.

Figure 5 Intra-frequency operation with other vendors

4.1.2 Inter-frequency Scenario Two typical scenarios of inter-frequency operations are shown below.


UMTS 2100 F1

Intra-frequency handover with other vendor

ZTE UMTS 2100 F2

ZTE UMTS 2100 F1

UMTS 2100 F2

ZTE UMTS 2100 F3

R99+HSPA

R99+HSPA

UMTS 2100 F3R99+HSPA

E/H UMTS 2100 F2

E/H UMTS 2100 F1

E/H UMTS 2100 F3

ZTE RNCE/H RNC


Figure 6 1st Inter-frequency operation with other vendors

Figure 7 2nd Inter-frequency operation with other vendors

4.2 StrategyThe strategy between ZTE and Ericsson/HW will use operation without Iur, that is to

say, Iur interface is deactivated between ZTE RNC and Ericsson/HW RNC. It should

be pointed that strategies below depend on test results. Some in tables might be


UMTS 2100 F1


ZTE UMTS 2100 F2

ZTE UMTS 2100 F1

UMTS 2100 F2

ZTE UMTS 2100 F3

R99+HSPA

R99+HSPA


E/H UMTS 2100 F2

E/H UMTS 2100 F1

E/H UMTS 2100 F3

ZTE RNCE/H RNC

Inter-frequency handover with other vendor

UMTS 2100 F1


ZTE UMTS 2100 F2

ZTE UMTS 2100 F1

UMTS 2100 F2

ZTE UMTS 2100 F3

R99+HSPA

R99+HSPA


E/H UMTS 2100 F2

E/H UMTS 2100 F1

E/H UMTS 2100 F3

ZTE RNCE/H RNC

Inter-frequency handover with other vendor


modified according to test results because it also depends on the software version of

other vendors.

Table 9 Strategy for Intra-frequency between ZTE and Ericsson/HW without Iur

Services ZTE =>

Ericsson

ZTE<=

Ericsson

ZTE=> HW ZTE<=HW

Voice (AMR

12.2kbps)

HHO,

Ue involved

relocation

HHO,

Ue involved

relocation

HHO,

Ue involved

relocation

HHO,

Ue involved

relocation

R99 PS DSCR DSCR HHO,

Ue involved

relocation

HHO,

Ue involved

relocation

HSPA DSCR DSCR Fall back to DCH

& relocation

Fall back to DCH &

relocation

Voice+R99 Cs release, Ps

DSCR

Ps release, Cs

relocation

Cs release, Ps

DSCR

Ps release, Cs

relocation

Ue involved

relocation

Ue involved

relocation

Voice+HSPA Cs release, Ps

DSCR

Ps release, Cs

relocation

Cs release, Ps

DSCR

Ps release, Cs

relocation

Fall back to DCH

& Ue involved

relocation

Fall back to DCH &

Ue involved

relocation

Video HHO, Ue

involved

relocation

HHO, Ue

involved

relocation

HHO, Ue involved

relocation

HHO, Ue involved

relocation

Table 10 Strategy for Inter-frequency between ZTE and Ericsson/HW without Iur

Services ZTE => EricssonZTE<= Ericsson ZTE=> HW ZTE<=HW

Voice (AMR HHO, Ue HHO, Ue HHO, Ue HHO, Ue



12.2kbps) involved

relocation

involved

relocation

involved

relocation

involved

relocation

R99 PS DSCR DSCR HHO, Ue

involved

relocation

HHO, Ue

involved

relocation

HSPA DSCR DSCR Fall back to

DCH & Ue

involved

relocation

Fall back to

DCH & Ue

involved

relocation

Voice+R99 HHO

Cs release, Ps

DSCR

Ps release, Cs

relocation

HHO

Ps DSCR

Cs relocation

Ue involved

relocation

Ue involved

relocation

Voice+HSPA HHO

Cs release, Ps

DSCR

Ps release, Cs

relocation

HHO

Ps DSCR

Cs relocation

Fall back to

DCH & Ue

involved

relocation

Fall back to

DCH & Ue

involved

relocation

Video Ue involved

relocation

Ue involved

relocation

Ue involved

relocation

Ue involved

relocation

4.3 ParametersIntra-frequency handover parameters refer to current network.

Inter-frequency handover parameters refer to table 5.

5 APPENDIX



5.1 Multi-carrier strategy after swap

5.1.1 Scenario

Figure 8 Multi-carrier strategy after swap

5.1.2 Strategy

A. Intra 3G

1) Camping and cell reselection

F1, F2 and F3 are all access layer. UE can camp on any of them according to cell’s

signal quality.


Since three carriers can support R99+HSPA, the load balance is implemented by

inter-frequency cell reselection in idle mode, and there is no service balance.

3) Handover

(a) UE can play intra-frequency handover on each layer F1/F2/F3.



(b) At the boundary of F3, UE hands over to F1, which is as same as that during

swap in section 2.2.1.In this way, there is no need to modify inter-frequency

neighboring relations.

B. Between 3G and 2G


5.1.3 Parameter


ZTE parameter


HspaSptMeth

0: Not Support

HSUPA and

HSDPA;

1: Support HSDPA

and DCH;

2: Support HSDPA

only;

3: Support

HSUPA , HSDPA

and DCH;

4: Support HSUPA

and HSDPA

3: Support

HSUPA ,

HSDPA and

DCH;

3: Support

HSUPA , HSDPA

and DCH;

3: Support

HSUPA , HSDPA

and DCH;

ShareCover

0: Neighbor

1: Overlap

2: Covers

3: Contained in

F1-> co-

sector

F2/F3:

1: Overlap

F2-> co-sector

F1/F3:

1: Overlap

F3-> co-sector

F1/F2:

1: Overlap;

(At the boundary)

F3->not-co-sector

F1: 0: Neighbor



ZTE parameter



1: Cell_DCH State

Only

2: Connected

State, Non-

Cell_DCH

3: Idle State +

Cell_DCH State

4: Idle State +

Connected State,

Non-Cell_DCH

5: Cell_DCH State

+ Connected State,

Non-Cell_DCH

6: Idle State +

Cell_DCH State+

Connected State,

Non-Cell_DCH

F1-> co-

sector

F2/F3: 0

F2-> co-sector

F1/F3: 0

F3-> co-sector

F1/F2: 0

(At the boundary)

F3->not-co-sector

F1: 6

Notes: (1) Other parameters refer to section 2.3. (2) In table 5, the inter-RAT

handover parameters of F2 refer to that of F1.


multi carrier strategyv1.4

Documents

3a event trigger

cs64 service

zte confidential

db step2 db

current network

f1 configures

dbm step 1dbm

current network