Random camping strategy and impact v1.0

Random Camping Strategy and Impact in Project X

Issue 01Date 2013-02-18

HUAWEI TECHNOLOGIES CO., LTD.

Random Camping Strategy and Impact V1.0 INTERNAL

About This DocumentOverview

This document describes what are the concept, strategy and impact of the Random Camping feature in UMTS network. But why we are need like such features, herein below some reasons:

1- Enhance spectrum resource utilization; the loading of each carrier is almost balanced.

2- Decrease service access delay, improve the user experience.

So as we will see later, this feature have good impact on the UMTS network performance but taking into consideration to deploy this feature on a dense F1 and F2 co-coverage area to allow you to see the impact.

Document ReviewPrepared by Medhat Adel kamel Date 2013-02-18

Reviewed by Date

Change History

Date Version Description Author

2013-02-18 V1.0 Completed Medhat Adel kamel

Product Version

Product Version

BSC6900 V900R013

BTS3900 V200R013

Intended Audience This document is intended for:

Network design engineers Network monitoring engineers

Huawei Confidential of 12


Contents

1 Random Camping Strategy ………………………………………………………………………………………………………………………………………….4

2 Random Deployment Strategy …………………………………………………………………………………………………………………………………….4

2.1 Load Balancing between 2 Carriers …………………………………………………………………………………………….…………….…..4

2.2 Mobility Strategy between 2 Carriers ………………………………………………………………………………………….…….…………..5

3 Random Camping Script ………………………………….…………………………………………………………………….…………………………….……….5

4 Random Camping Performance Counters ……….…………………………………………………………………….………………………….………….7

5 Random Camping Impact ……………………………………………………………………………………………………………………………………………..7

6 Random Camping Advantages and Drawbacks ……………………………………………………………………………………………….…………12



1 Random Camping Strategy

In UMTS networks, most of the customers prefer to dedicate one or more frequency for data services, mainly HSDPA and this called dedicated carriers strategy, where:

F1: Priority to carry R99. F2: Priority to carry HSPA. All UEs are forced to camp on F1 (F2 is barred, or configure cell

reselection parameters to make F1 as the first priority to camp on). All services are assessed from F1. If a HSPA service is initiated, the call will be redirected from F1 to F2. UE will fall back to F1 after having finished the service on F2.

But the random Camping strategy is different, where:

Same service priority for both carriers. UE camps on either F1 or F2 randomly. UE performs cell selection/ reselection between F1 & F2. UEs access the service on its currently camped carrier (F1 or F2).

2 Random Deployment Strategy

2.1 Load Balancing between 2 Carriers

Strategy 1: Dedicated Carriers

For R99 Services: Access Mode: Service is initiated on F1. Attempt F2 only if F1 is overloaded. Connected Mode: If F1 is overloaded, the existing services will be re-redirected to F2.

For HSPA Services: Access Mode: Service is always re-directed to F2.

Strategy 2: Random Camping

For R99 Services: Access Mode: Service is initiated on the currently camped carrier (F1 or F2). Connected Mode: If F1 is overloaded, the existing services will be re-redirected to F2 and vice-versa.

For HSPA Services: Access Mode: Service is initiated on the currently camped carrier except if the number of HSPA users on the current carrier is higher than that of the other carrier plus a pre-defined offset, the in-coming HSPA service will be re-directed to the other carrier.


R99 + H

R99 + H R99 + H

R99 + H

F1

F2


2.2 Mobility Strategy between 2 Carriers

Inter-Frequency Blind Handover Blind handover neighbor relations (for service re-

direction/ load balancing) are configured between F1 and F2 cells in the same coverage area.

Bi-directional blind handover is allowed.

Intra-Frequency Soft Handover Intra-frequency handover based on coverage for both F1 and F2, respectively, is allowed.

Inter-Frequency Handover Unidirectional inter-frequency handover based

3 Random Camping Script

// F1 cells: 32011, 32012, 32013 and 32014// F2 cells: 38585, 38586, 38587 and 41813

// BlindHoFlag=TRUE for co-coverage cells (F1 & F2), F1<to>F2 or F2<to>F1// IdleQoffset1sn=0 And IdleQoffset2sn=0 to randomly camping on F1 or F2// Note: Blind HO should be "ON" to allow Inter-Freq HO if LDR is trigged.MOD UINTERFREQNCELL: RNCId=101, CellId=32011, NCellRncId=101, NCellId=38585, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, BlindHOQualityCondition=-95, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=32012, NCellRncId=101, NCellId=38586, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, BlindHOQualityCondition=-95, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=32013, NCellRncId=101, NCellId=38587, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, BlindHOQualityCondition=-95, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=32014, NCellRncId=101, NCellId=41813, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, BlindHOQualityCondition=-95, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;

MOD UINTERFREQNCELL: RNCId=101, CellId=38585, NCellRncId=101, NCellId=32011, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, BlindHOQualityCondition=-95, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;



MOD UINTERFREQNCELL: RNCId=101, CellId=38586, NCellRncId=101, NCellId=32012, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, BlindHOQualityCondition=-95, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=38587, NCellRncId=101, NCellId=32013, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, BlindHOQualityCondition=-95, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=41813, NCellRncId=101, NCellId=32014, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, BlindHOQualityCondition=-95, NPrioFlag=FALSE, InterNCellQualReqFlag=FALSE;

// BlindHoFlag=FALSE for non co-coverage cells (F1 & F2), if there are inter-freq relations between them:MOD UINTERFREQNCELL: RNCId=101, CellId=41813, NCellRncId=101, NCellId=32011, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=41813, NCellRncId=101, NCellId=32012, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=41813, NCellRncId=101, NCellId=32013, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;

MOD UINTERFREQNCELL: RNCId=101, CellId=38587, NCellRncId=101, NCellId=32012, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=38587, NCellRncId=101, NCellId=32011, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;

MOD UINTERFREQNCELL: RNCId=101, CellId=38586, NCellRncId=101, NCellId=32011, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=38586, NCellRncId=101, NCellId=32013, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=38586, NCellRncId=101, NCellId=32014, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;

MOD UINTERFREQNCELL: RNCId=101, CellId=38585, NCellRncId=101, NCellId=32014, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=38585, NCellRncId=101, NCellId=32013, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;MOD UINTERFREQNCELL: RNCId=101, CellId=38585, NCellRncId=101, NCellId=32012, SIB11Ind=TRUE, IdleQoffset1sn=0, IdleQoffset2sn=0, BlindHoFlag=FALSE;

// Switch off DRD on all F1 cells, optional:MOD UCELLDRD: CellId=32011, ServiceDiffDrdSwitch=OFF;MOD UCELLDRD: CellId=32012, ServiceDiffDrdSwitch=OFF;



MOD UCELLDRD: CellId=32013, ServiceDiffDrdSwitch=OFF;MOD UCELLDRD: CellId=32014, ServiceDiffDrdSwitch=OFF;

4 Random Camping Performance Counters

RRC Attempts numbers of F1 and F2 should be the same: VS.RRC.AttConnEstab.Cell HSDPA subscribers numbers of the two carriers should be balanced : VS.HSDPA.UE.Mean.Cell DRD.RBSetup.SuccOut num should very little or null: VS.DRD.RBSetup.SuccOut/VS.DRD.RBSetup.AttOut×100% Inter-frequency HHO success ratio.LB: VS.HHO.AttInterCell.LB/VS.HHO.SuccInterCell.LB*100% Inter-frequency HHO success ratio: VS.HHO.SuccInterFreqOut/ VS.HHO.AttInterFreqOut)*100%

5 Random Camping Impact



6 Random Camping Advantages and Drawbacks

Strategy 1: Dedicated Carriers

Advantages HSPA has the least impact on the existing R99 services. Better voice quality.

Drawbacks Spectrum resource is not fully utilized. Many service re-directed from F1 to F2. As the re-direction of HSPA services from F1 to F2 is always needed, it increases the service setup time. If F1 is fully of R99 users, all new in-coming R99 services will be directed from F1 to F2.



Strategy 2: Random Camping

Advantages Spectrum resource is fully utilized. The loading of each carrier is almost balanced. Smaller service access delay. Easy to be implemented.

Drawbacks Voice quality is not as good as Strategy 1, due to the impact of HSPA on the same carrier. Frequent R99 inter-frequency handovers may occur if 1-carrier and 2-carrier site locations are interleaved (i.e.

R99 inter-frequency handover from F2 to F1 when moving from 2-carrier site to 1-carrier site).


Random camping strategy and impact v1.0

Engineering

Transcript of Random camping strategy and impact v1.0