Multi Carrier StrategyV1.4

Multi-carrier Strategy
Version V0.1 V0.2 Date 27-04-2011 5-5-2011 Author Fulei Liu Fulei Liu Approved By Remarks Create Put IOT strategy between ZTE RNC and other vendors with Iur in section 5.2. Add the comparison of ZTE strategy in chapter 2 and current network strategy in chapter 3 to chapter 3.4. Update Cons of ZTE strategy in chapter 3.4.
V0.3
10-5-2011
Fulei Liu
V0.4
16-5-2011
Fulei Liu
2012 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.
ZTE Confidential Proprietary
2012 ZTE Corporation. All rights reserved.
TABLE OF CONTENTS
1 OVERVIEW........................................................................................5 2 ZTE MULTI-CARRIER OPERATION.........................................................6 2.1 Scenario........................................................................................................6 2.2 Strategy........................................................................................................6 2.3 Parameters....................................................................................................9 3 MULTI-CARRIER STRATEGY IN CURRENT NETWORK.............................14 3.1 Scenario......................................................................................................14 3.2 Strategy .....................................................................................................14 3.3 Parameters..................................................................................................15 3.4 Comparison ................................................................................................18 4 INTERWORKING WITH OTHER VENDORS............................................19 4.1 Scenario......................................................................................................19 4.2 Strategy......................................................................................................21 4.3 Parameters..................................................................................................23 5 APPENDIX.......................................................................................23 5.1 Multi-carrier strategy after swap..................................................................23
FIGURES
MULTI-CARRIER OPERATION OF THE ENTIRE NETWORK.............................6 MULTI-CARRIER OPERATION INTRA 3G ....................................................6 MULTI-CARRIER OPERATION BETWEEN 3G AND 2G ...................................8 MULTI-CARRIER OPERATION IN CURRENT NETWORK ..............................14 INTRA-FREQUENCY OPERATION WITH OTHER VENDORS..........................20 1ST INTER-FREQUENCY OPERATION WITH OTHER VENDORS....................20 2ND INTER-FREQUENCY OPERATION WITH OTHER VENDORS...................21 MULTI-CARRIER STRATEGY AFTER SWAP................................................23
TABLES
RELATED PARAMETER OF CELL CONFIGURATION......................................9 RELATED PARAMETER OF 3G CELL RESELECTION ...................................10 RELATED PARAMETER OF 2G CELL RESELECTION....................................11 RELATED PARAMETER OF LOAD AND SERVICE BALANCE..........................11 RELATED PARAMETER OF INTER-FREQUENCY AND INTER-RAT HANDOVER 11 PARAMETER SETTINGS FOR ZTE-SRNC TO ZTE-DRNC .............................13 RELATED PARAMETER OF CELL CONFIGURATION....................................16 RELATED PARAMETER OF LOAD AND SERVICE BALANCE..........................16 STRATEGY FOR INTRA-FREQUENCY BETWEEN ZTE AND ERICSSON/HW WITHOUT IUR.....................................................................................21 STRATEGY FOR INTER-FREQUENCY BETWEEN ZTE AND ERICSSON/HW WITHOUT IUR.....................................................................................22 RELATED PARAMETER OF CELL CONFIGURATION....................................24
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

ZTE Confidential Proprietary 2012 ZTE Corporation. All rights reserved. 6
F1, F2 and F3 are all access layer. UE can camp on any of them according to cells 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 CS 12.2kbps) R99 PS HSPA Voice+R99 Voice+HSPA Video ZTE <=> ZTE (AMR SHO, relocation SHO, relocation SHO, relocation SHO, relocation SHO, relocation SHO, relocation
Strategy for Inter-frequency between ZTE and ZTE with Iur Services CS 12.2kbps) R99 PS HSPA Voice+R99 Voice+HSPA Video ZTE <=> ZTE (AMR HHO, Ue involved relocation
HHO, Ue involved relocation HHO, Ue involved relocation HHO, Ue involved relocation HHO, Ue involved relocation 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 Parameters
Notes: (1) The value not presented in tables below uses ZTE default value.
Table 1
Related parameter of cell configuration Range 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 0: Neighbor 1: Overlap 2: Covers 3: Contained in (At the boundary) F2->not-co-sector F1: 0: Neighbor (At the boundary) F3->not-co-sector F1: 0: Neighbor F3-> co-sector F1/F2: 0 (At the boundary) 9 ZTE F1 3: Support HSUPA , HSDPA and DCH; ZTE F2 3: Support HSUPA , HSDPA and DCH; ZTE F3 3: Support HSUPA , HSDPA and DCH;
ZTE parameter name HspaSptMeth
ShareCover
F1-> cosector F2/F3: 1: Overlap
F2-> co-sector F1/F3: 1: Overlap
F3-> co-sector F1/F2: 1: Overlap;
Statemode
0: Idle State Only 1: Cell_DCH State Only
F1-> cosector F2/F3: 0
F2-> co-sector F1/F3: 0 (At the boundary)
2: Connected State, NonCell_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
F2->not-co-sector F1: 6
F3->not-co-sector F1: 6
Table 2
Related parameter of 3G cell reselection ZTE parameter name QualMeas SInterSearchPre Sintersearch OtherRATInfoPre SSearchRat Qqualmin Range 1: CPICH Ec/No 2: CPICH RSCP 0: False 1: True (0..20 )dB Step 2dB 0: False 1: True (0..20 )dB Step 2dB (-24..0)dB step 1dB ZTE F1 1: CPICH Ec/No 0: False 10dB 1: True ZTE F2 1: CPICH Ec/No 0: False 10dB 1: True ZTE F3 1: Ec/No 0: False 10dB 1: True CPICH
0dB
18dB(current network -17dB) -115dBm 10dB(current network 4dB) 2dB 0dB (F1>F2/F3) 0dB (HW:0dB) (E: 7dB) (F1->GSM)
0dB
18dB(current network -17dB) -115dBm 10dB (current network 4dB) 2dB 0dB (F2>F1/F3) 0dB (HW:0dB) (E: 7dB) (F2->GSM) 0dB (F2>F1/F3)
0dB
-18dB(current network -17dB) -115dBm 10dB(current network 4dB) 2dB 0dB (F3>F1/F2) 0dB (HW:0dB) (E: 7dB) (F3->GSM) 0dB (F3>F1/F2) 10
QRxLevMin Qhyst1s
(-115..-25)dBm Step2dBm (0..40)dB step2 dB (0..40)dB step2 dB (-50..50)dB
Qhyst2s Qoffset1SNSib11
Qoffset2SNSib11
(-50..50)dB
0dB (F1->F2/F3)
Table 3
Related parameter of 2G cell reselection Parameter name Qsearch_I Range [0..15] 0 = - 98 dBm, 1 = - 94 dBm, , 6 = - 74 dBm, 7 = always 8 = - 78 dBm, 9 = - 74 dBm, , 14 = - 54 dBm, 15 = never [0..15] 0 = always 1 = -28 dB, 2 = -24 dB, , 15 = 28 dB [0..7] 0= -20dB, 1= -6dB, 2= -18dB, 3= -8dB, 4= -16dB, 5= -10dB, 6= -14dB, 7= -12dB GSM->3G 7(has 3G neighbor); 15(do not have neighbor) 0 3G
FDD_Qoffset
FDD_Qmin
7= -12dB
Table 4 ZTE parameter name InitRrcLBSw RabAssLBSw
Related parameter of load and service balance Range ZTE F1 0 0 ZTE F2 0 0 0 0 ZTE F3
0:Off 1: Inter-frequency Switch On 0: Off 1: Inter- frequency Switch On 2: Inter-system Switch On 3:Inter-frequency and Intersystem Switch On 0: Off 1: Inter-frequency Switch On 2: Inter-system Switch On 3: Inter-frequency and Intersystem Switch On 0: Off 1: On 0:Off 1: On 0:Off 1: On
CallHoldLBSw
InitRrcSBSw RabAssSBSw CallHoldSBSw
0 0 0
0 0 0
0 0 0
Table 5
Related parameter of inter-frequency and inter-RAT handover Range 0 Ec/No 1 RSCP 2: Ec/No and RSCP 0: Turn off Inter-frequency and Inter-RAT Handover 1: Only Inter Frequency F1 2: Ec/No and RSCP F2/F3 2: Ec/No and RSCP
ZTE parameter name NonIntraM easQuan IfOrRatHo Swch
2: Only Inter RAT
3: Inter Frequency Is Prior to Inter RAT 11
ZTE parameter name
Range
F1
F2/F3
2: Only Inter RAT 3: Inter Frequency Is Prior to Inter InterHoTac tic RAT 0: Algorithm Deciding 1: 2A Event Trigger 2: 2B Event Trigger InterMeas CfgNote 3: 2C Event Trigger 0: UE Period Report Parameters for CPICH Ec/No 3: UE Inter-frequency Event Report Parameters for CPICH Ec/No 4: UE Period Report Parameters for CPICH RSCP 7: UE Inter-frequency Event Report Parameters for CPICH RSCP 8: UE Inter-frequency Event Report Parameters for CPICH Ec/No(GSM) 9: UE Inter-frequency Event Report Parameters for CPICH ThreshUse dFreq RSCP(GSM) CPICH RSCP: (-115..-25 )dBm step 1dBm CPICH Ec/No: (-24..0) dB step 1dB 9 7
1: 2A Event Trigger
2D/2F: Voice: 2D: -100dBm/14dB 2F: -97dBm/11dB PS: 2D: -110dBm/15dB 2F: -107dBm/12dB
/
2D/2F: Voice: 2D: 14dB 2F: 11dB PS: 2D: 14dB 2F: 11dB
2E
-95dBm/-92dBm/-
-95dBm/-92dBm/-
ThreshNo UsedFreq
CPICH RSCP: (-115..-25 )dBm step 1dBm CPICH Ec/No: (-24..0) dB step 1dB
Voice/PS: 2E: -97 dBm/14dB

2D/2F: 2A/2D/2F/2E:
Hysteresis
(0, 0.5..14.5)dB step 0.5dB
2D: 2dB
2A: 4dB
12
ZTE parameter name
Range
F1
F2/F3
2F: 2dB
2D: 2dB 2E: 4dB 2F: 2dB

2A/2D/2F/2E: 2A: 100ms 2E: 100ms 2D/2F: 640 ms 0: Neighbor (not-cosite) 1: Overlap(co-site)
TrigTime
(0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000)ms
2D/2F: 2D/2F: 640 ms
GsmShare Cover
0: Neighbor; 1: Overlap; 2: Covers; 3: Contained in 0: Algorithm Deciding 1: 3A Event Trigger 2: 3C Event Trigger CPICH RSCP: (-115..-25 )dBm step 1dBm
0: Neighbor (not-cosite) 1: Overlap(co-site)
RatHoTacti c Thresh
1: 3A Event Trigger
1: 3A Event Trigger
3A:
3A:
Voice/PS 3A: -95 dBm/14dB

3A:
Voice/PS 3A: -95 dBm/14dB

3A:
ThreshSys
CPICH RSCP: (-115..-25 )dBm step 1dBm
Voice/PS 3A: -102 dBm

1: Parallel 0: Serial 1: Support SCUDIF, CS64 Service Established by a RB
Voice/PS 3A: -102 dBm

1: Parallel 0: Serial 1: Support SCUDIF, CS64 Service Established by a RB
HsdpaCm AssoMode HsupaCm AssoMode Cs64RbM odeSwch
0: Serial 1: Parallel 0: Serial 1: Parallel 0: Not Support SCUDIF 1: Support SCUDIF, CS64 Service Established by a RB
Table 6
Parameter Settings for ZTE-SRNC to ZTE-DRNC Name on the Interface Hard-handover With Relocation Support HSDPA Iur Interface Process Support HSUPA Iur Interface Process Support Hard Handover DSCR Use DSCR for PS service when UE all RLs need moved to DRNC Support UE not Involved Relocation for CS Service Support UE not Involved Relocation for PS Service
ZTE parameter name RncFeatSwitch0 RncFeatSwitch1 RncFeatSwitch2 RncFeatSwitch4 RncFeatSwitch7 RNCFeatSwitch10 RNCFeatSwitch11
ZTE<=> ZTE
0 1 1 0 0 1 1
Default Value 0 1 1 0 0 1 1 13
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.
2) Load sharing and traffic distribution

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 Refer to section 2.2.1.
3.2.2 Operation between 3G and GSM

Refer to section 2.2.2.
3.3 Parameters
Notes: Other parameters refer to section 2.3.
15
Table 7
Related parameter of cell configuration Range 1: Barred 2: Not Barred (10,20,40,80,160,320,640,1280)s 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 0: Neighbor 1: Overlap 2: Covers 3: Contained in ZTE F1 2 10s 3: Support HSUPA , HSDPA and DCH; ZTE F2 1 10s 3: Support HSUPA , HSDPA and DCH; ZTE F3 1 10s 3: Support HSUPA , HSDPA and DCH;
ZTE parameter name CellBarredIn d TBarred HspaSptMeth
ShareCover
F1-> cosector 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
Statemode
0: Idle State Only 1: Cell_DCH State Only 2: Connected State, NonCell_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
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 Range ZTE F1 0 ZTE F2 0 0 ZTE F3
ZTE parameter name
InitRrcLBSw
RabAssLBS w
0:Off 1: Inter-frequency Switch On 0: Off 1: Interfrequency Switch On 2: Inter-system Switch On
16
ZTE parameter name
Range
ZTE F1
ZTE F2
ZTE F3
CallHoldLBS w
3:Inter-frequency and Inter-system Switch On 0: Off 1: Inter-frequency Switch On 2: Inter-system Switch On 3: Inter-frequency and Inter-system Switch On
0: Off 1: On 0: Off 1: On 0: Off 1: On 0: Off 1: On (0..100%) step 1% (0..100%) (0..100%)
DlLdBalPwrSw ch LdBalCdSwch UlLdBalPwrSw ch LdBalHsSwch DlLdBalHsWei ght DlLdHsThdHs d ExtraCDeltaH sTrd
0 0 0 1 100% 80% 5%
0 0 0 0
0% 80% 0%
0 0 0 0
0% 80% 0%
InitRrcSBSw RabAssSBS w CallHoldSBS w PrefTrafType
CsHo4MulRab Swch
0: Off 1: On 0:Off 1: On 0:Off 1: On Bit0=0/1: Preferred / Bit1=0/1: Preferred Preferred Bit2=0/1: Preferred Preferred Bit3~Bit7: fixed to 0 0:Off 1: On
0 1 0 CS No CS Preferred R99 PS No / R99 PS HS PS / HS No PS Bit0=1 Bit1=1 Bit2=0 Bit3~B it7=0
0 0 0 Bit0=0 Bit1=0 Bit2=1 Bit3~B it7=0
0 0 0 Bit0=0 Bit1=0 Bit2=1 Bit3~Bit 7=0
Reversed,
0
17
3.4 Comparison
This chapter presents the pros and cons of ZTE strategy in chapter 2 and current network strategy in chapter 3.
ZTE
Pros Cons 1. Idle mode: three carriers can absorb Compared with Current network strategy, harbor, operators has more chance to neighboring relations with each other in attract users. 2. CELL_DCH: No RRC or RAB this strategy.
strategy users, especially, at the airport or co sector F2 and F3 are required to have
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 Current network Europe and HK. Load can be balanced from F1 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
strategy Service can be redirected to F2 and F3.
system
information,
18
and
later
reselect to F1, which is controlled by a timer (Tbarred). powers In to this case, UE
consumes
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 Scenario
Since 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.
UMTS 2100 F3 R99+HSPA UMTS 2100 F2 R99+HSPA UMTS 2100 F1 R99+HSPA
E/H RNC
ZTE RNC
Intra-frequency handover with other vendor

E/H UMTS 2100 F3 E/H UMTS 2100 F2 E/H UMTS 2100 F1 ZTE UMTS 2100 F3 ZTE UMTS 2100 F2 ZTE UMTS 2100 F1
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 F3 R99+HSPA UMTS 2100 F2 R99+HSPA UMTS 2100 F1 R99+HSPA E/H RNC ZTE RNC
Intra-frequency handover with other vendor Inter-frequency handover with other vendor
Figure 6
1st Inter-frequency operation with other vendors
20
UMTS 2100 F3 R99+HSPA UMTS 2100 F2 R99+HSPA UMTS 2100 F1 R99+HSPA
E/H RNC ZTE RNC
Intra-frequency handover with other vendor Inter-frequency handover with other vendor
Figure 7
2nd Inter-frequency operation with other vendors
4.2 Strategy
The 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 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 Voice 12.2kbps) R99 PS
ZTE Ericsson (AMRHHO, Ue involved relocation DSCR
=>ZTE<= Ericsson HHO, Ue involved relocation DSCR
ZTE=> HW HHO, Ue involved relocation HHO, Ue involved
ZTE<=HW HHO, Ue involved relocation HHO, Ue involved
HSPA
DSCR
DSCR
relocation relocation Fall back to DCHFall back to DCH & & relocation relocation
21
Voice+R99
Cs release, PsCs release, PsUe DSCR DSCR relocation Ps release, CsPs release, Cs
involvedUe relocation
involved
Voice+HSPA
relocation relocation Cs release, PsCs release, PsFall back to DCH Fall back to DCH & DSCR DSCR & Ue involved Ue involved relocation Ps release, CsPs release, Csrelocation
Video
relocation HHO, involved relocation
relocation UeHHO, involved relocation
UeHHO, Ue involvedHHO, Ue involved relocation relocation
Table 10 Strategy for Inter-frequency between ZTE and Ericsson/HW without Iur
Services Voice 12.2kbps)

R99 PS
ZTE => Ericsson ZTE<= Ericsson ZTE=> HW (AMRHHO, involved relocation DSCR UeHHO, involved relocation DSCR UeHHO, involved relocation HHO, involved relocation Fall back DCH involved &
ZTE<=HW UeHHO, involved relocation UeHHO, Ue involved relocation toFall back UeDCH & involved to Ue Ue
HSPA
DSCR
DSCR
Voice+R99
HHO
HHO
relocation relocation Ue involvedUe involved relocation relocation
Cs release, PsPs DSCR DSCR Cs relocation
Ps release, Cs Voice+HSPA relocation HHO HHO Fall DCH involved relocation back & toFall UeDCH back & to Ue
Cs release, PsPs DSCR DSCR Cs relocation
involved relocation
Ps release, Cs relocation
22
Video
Ue
involvedUe
involvedUe
involvedUe
involved
relocation
relocation
relocation
relocation
4.3 Parameters
Intra-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 cells 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 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 Refer to section 2.2.2.
5.1.3 Parameter
Table 11 Related parameter of cell configuration ZTE parameter name HspaSptMeth Range 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 ZTE F1 3: Support HSUPA , HSDPA and DCH; ZTE F2 3: Support HSUPA , HSDPA and DCH; ZTE F3 3: Support HSUPA , HSDPA and DCH;
24
ZTE parameter name ShareCover
Range 0: Neighbor 1: Overlap 2: Covers 3: Contained in
ZTE F1 F1-> cosector F2/F3: 1: Overlap
ZTE F2 F2-> co-sector F1/F3: 1: Overlap
ZTE F3 F3-> co-sector F1/F2: 1: Overlap; (At the boundary) F3->not-co-sector F1: 0: Neighbor F3-> co-sector F1/F2: 0 (At the boundary) F3->not-co-sector F1: 6
Statemode
0: Idle State Only 1: Cell_DCH State Only 2: Connected State, NonCell_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
F2-> co-sector F1/F3: 0
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.
25

Multi Carrier StrategyV1.4

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Multi Carrier StrategyV1.4

Hochgeladen von

Copyright:

Verfügbare Formate

Multi-carrier Strategy

ZTE Confidential Proprietary

2012 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

2012 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

2012 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

2012 ZTE Corporation. All rights reserved.

2 ZTE Multi-carrier operation

Multi-carrier operation of the entire network

Multi-carrier operation intra 3G

1) Camping and cell reselection

2.2.2 Operation between 3G and GSM

Multi-carrier operation between 3G and 2G

ZTE Confidential Proprietary

2012 ZTE Corporation. All rights reserved.

ZTE parameter name HspaSptMeth

F1-> cosector F2/F3: 1: Overlap

F2-> co-sector F1/F3: 1: Overlap

F3-> co-sector F1/F2: 1: Overlap;

0: Idle State Only 1: Cell_DCH State Only

F1-> cosector F2/F3: 0

F2-> co-sector F1/F3: 0 (At the boundary)

ZTE Confidential Proprietary

2012 ZTE Corporation. All rights reserved.

(-115..-25)dBm Step2dBm (0..40)dB step2 dB (0..40)dB step2 dB (-50..50)dB

ZTE Confidential Proprietary

2012 ZTE Corporation. All rights reserved.

Table 4 ZTE parameter name InitRrcLBSw RabAssLBSw

InitRrcSBSw RabAssSBSw CallHoldSBSw

ZTE parameter name NonIntraM easQuan IfOrRatHo Swch

2: Only Inter RAT

3: Inter Frequency Is Prior to Inter RAT 11

ZTE Confidential Proprietary

2012 ZTE Corporation. All rights reserved.

ZTE parameter name

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

(0, 0.5..14.5)dB step 0.5dB

2012 ZTE Corporation. All rights reserved.

ZTE parameter name

2D: 2dB 2E: 4dB 2F: 2dB

2D/2F: 2D/2F: 640 ms

0: Neighbor (not-cosite) 1: Overlap(co-site)

Voice/PS 3A: -95 dBm/14dB

Voice/PS 3A: -95 dBm/14dB

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

Voice/PS 3A: -102 dBm

Voice/PS 3A: -102 dBm

HsdpaCm AssoMode HsupaCm AssoMode Cs64RbM odeSwch

ZTE Confidential Proprietary

2012 ZTE Corporation. All rights reserved.

3 Multi-carrier strategy in current network

Multi-carrier operation in current network

2) Load sharing and traffic distribution

3) Handover Refer to section 2.2.1.

3.2.2 Operation between 3G and GSM

ZTE Confidential Proprietary

2012 ZTE Corporation. All rights reserved.

ZTE parameter name CellBarredIn d TBarred HspaSptMeth

F1-> cosector F2/F3: 1: Overlap

F3-> co-sector F1 1: Overlap; (At the boundary) F3->not-co-sector F1: 0: Neighbor

F1-> cosector F2/F3: 1