2RF Sites Configuration Guidelines RAS06

2RF Sites Configuration Guidelines based on Nokia Flexi Technology

MS NPO WSE - ES

Página 1 de 20 3G RF EngineeringNOKIA SIEMENS NETWORKS

Revision History

Date Rev. Originator Summary of Change

15.3.2009 1.0 NSN NPO Spain First Version: RAS06

MS NPO WSE - ES


1 INTRODUCTION ............................................................................................................ 4

2 SECOND CARRIER DEPLOYMENT STRATEGY ..................................................... 4

2.1 TRAFFIC HANDLING.......................................................................................................42.1.1 DEDICATED HSDPA LAYER SOLUTION DESCRIPTION....................................................5

3 2RF CONFIGURATION RULES ................................................................................... 8

3.1 FLEXI BTS CONFIGURATION.........................................................................................83.2 HSDPA SCHEDULERS....................................................................................................9

4 2RF PARAMETERS ...................................................................................................... 10

4.1 CELL RESELECTION PARAMETERS..............................................................................104.2 IFHO AND DRRC PARAMETERS.................................................................................114.2.1 IFHO..........................................................................................................................114.2.2 DRRC........................................................................................................................134.3 List of parameters..........................................................................................................17

MS NPO WSE - ES


1 Introduction

The purpose of this document is to provide guidance for WCDMA layering & frequency planning and for the traffic handling between WCDMA layers.

2 Second Carrier deployment strategy

In networks with low or normal load, a single carrier/frequency is typically used. But times are changing and increased traffic in 3G networks together with new features (HSDPA & HSUPA) will start to require more capacity than can be offered by one layer. Operators must clearly define the strategy to follow when upgrading a site with a new frequency layer in order to maximize resources.

There are few possible scenarios to use two or more frequencies in a 3G network. The most common way is to deploy an additional carriers using same site/coverage area than existing one to provide extra capacity in the area.

a) Basic usage with two or more carriers

In case the chosen layering configuration is to add a carrier to an existing site, thus sharing same coverage area, a strategy for layering need to be defined. Depending on the traffic demands and HSPA throughput requirements, the additional layers can be deployed over the whole network /cluster level or only for the traffic hot spots or special events.

When defining layer strategy, one important issue is to clarify for which layer(s) HSPA is implemented. Carrier can be shared between HSPA and R99 traffic or there can be dedicated carrier for HSPA. Selected configuration depends highly on the operator demands and amount of HSPA traffic in the network.

2.1 Traffic handling

Targeted sites for RF carrier upgrade are typically having high density of all kind of traffic. Two different approaches can be used:

1. R99 and HSDPA shared in F1. The R99 DCH traffic could use most of the BTS power and leave little power for HSDPA use. This would have negative impact on HSDPA throughput.

MS NPO WSE - ES


f1

f2 f2

f1

2. Dedicating F2 carrier for HSDPA and F1 for R99. Provide more resources for HSDPA but disable HSDPA coverage and mobility in border areas. HSDPA Inter-frequency Handover (HSDPA IFHO) without channel type switching is supported from RU10 onwards, but in RAS06 only Serving Cell change between the same frequency carriers is supported.

Taking into account the Orange objectives, what NSN proposes is a solution following the second approach. Reasons:

It maximizes HSDPA throughput + capacity. HSDPA users in a mobility scenario are quite uncommon. HSDPA IFHO will be supported in RU10 and it could be considered as

a starting point for having the network ready for incoming releases. HSDPA -> DCH CTS due to IFHO without coming back to HSDPA layer

again could be minimized by introducing the feature HSPA Layering for UEs in Common Channels which enables also the transfer of UEs between layers in the transition from CELL_FACH to CELL_DCH.

Special parameterization in order to retain as much as possible HSDPA user in F2 could be implemented

2.1.1 Dedicated HSDPA layer solution description

UEs are forced to camp on layer 1 in idle mode, which is for R99 traffic only. With DRRC setup for HSDPA layering, all HSDPA capable UEs are moved to layer 2. HSDPA Serving Cell Change (SCC) is enabled in layer 2 providing full mobility for HSDPA users while F2 is present. Idle mode UEs will return back to layer 1.

In RAS51, the DRRC for HSDPA layering feature moved all HSDPA capable UEs to the HSDPA layer and R99 UE’s to the R99 layer, this move was based on UE HSPA capability only and does not check the establishment cause. With this implementation it was then also possible to move R5 UEs to F2 even if no PS service was being used. By activating RAS06 enhancements for Directed RRC connection setup for HSDPA layer, it is possible to move only those HSDPA capable UEs making PS call. (Only UEs which Establishment cause is listed with parameter DRRCforHSDPALayerService are transferred between the layers).

MS NPO WSE - ES


F2 – HSDPA (+R99)

F1 - R99 Only

DRRC

As stated, DRRC functionality is a basic player in 2RF sites configuration in order to achieve the expected system behaviour.

Directed RRC Connection Setup (DRRC setup) is a general feature in the RAN. DRRC Setup can be used to balance load between the carriers within same BTS, and by transferring UEs the correct layer based on service and UE capability. DRRC Connection setup works only between cells belonging to the same sector if they are configured with equal values for the following parameters. Parameters differs between RAS06 and earlier releases as can be seen from table below

RAS51 and earlier RAS06SectorID SectorIDPtxPrimaryCPICH PtxPrimaryCPICHPtxTarget & PtxOffset CPICHtoRefRABOffsetPrxTarget & PrxOffset PLMN identity (MCC, MNC) PLMN identity (MCC, MNC)

Mobile Country Code - MCC Mobile Country Code - MCC

Mobile Network Code -MNC Mobile Network Code -MNC

The RAS06 optional feature HSPA Layering for UEs in Common Channels provide multiple enhancements, one which is enhanced functionality for the Directed RRC Connection Setup for HSDPA feature. This feature enables also the transfer of UEs between layers in the transition from CELL_FACH to CELL_DCH, which will make the layering applicable also to connected mode UEs coming to cell in CELL_FACH or CELL_PCH with cell re-selection to the cell.

Basic functionality (DRRC setup and DRRC setup for HSDPA layer) Directed RRC connection setup provides load balancing between layers for

R99 traffic, and it is enabled with the parameter DirectedRRCEnabled. Directed RRC connection setup for HSDPA layer, which is enabled with the

parameter DirectedRRCForHSDPAEnabled can be used to direct HSDPA capable UE to the HSDPA layer and non-HSDPA capable UEs to the R99 layer. Basic functionality does not provide HSDPA load balancing, UEs are directed to correct layer based on UE category. The UEs are categorised to Release 5 and later UEs and R99/R4 UEs. With DRRC setup, support multiple carriers already in RAS51 onwards. With DRRC Setup for HSDPA layer the maximum number of carriers is 2.

RAS06 Enhanced functionality (optional) is activated with the parameter DirectedRRCForHSDPALayerEnhanc, which defines if improvements done with HSPA layering for UEs in common channels feature are activated or not.

More than 2 layers are supported (DRRC for HSDPA Layering) The service indicated by UE in RRC connection request is taken into account

MS NPO WSE - ES


Target cell load checking and HSDPA load balancing Simultaneous use of Directed RRC Connection Setup and Directed RRC

Connection Setup for HSDPA layer is supported UE capability indication IE (coming in RRC Connection Request message) is

used in decision making for Rel-6 and onwards UEs.

The DirectedRRCEnabled and DirectedRRCForHSDPAEnabled parameters can only be enabled together if DirectedRRCForHSDPALayerEnhanc is also enabled.

There are five possible combinations to configure these parameters as presented in the table below:

Config 1 Config 2 Config 3 Config 4 Config 5

Number of carriers Single Multiple Max 2 Multiple MultipleHSDPA enabled NO NO YES YES YESLoad Balancing for R99 traffic NO YES NO NO YESLoad Balancing for HSDPA traffic NO NO NO YES** YES**RAS06

DirectedRRCEnabled DisabledEnabled Disabled Disable Enabled

DirectedRRCForHSDPAEnabled Disabled DisabledEnabled

Enabled Enabled

DirectedRRCForHSDPALayerEnhanc* Disabled Disabled DisabledEnabled Enabled

* Parameter DirectedRRCForHSDPALayerEnhanc can be activated only if RAS06 optional feature HSPA Layering for UEs in Common Channels is activated. Configurations 4 and 5 are possible only if RAS06 optional feature HSPA Layering for UEs in Common Channels is activated.

** HSDPA Load Balancing applies only in those cases where HSDPA is configured in more than one frequency layer which is not the case of Orange network. DirectedRRCForHSDPALayerEnhanc functionality is used in order to make possible the movement of those R5/R6 users who are really using a PS service.

Two configurations among all the presented in the previous table are the ones NSN recommends for the 2RF sites depending on the following criterion:

Conventional 2RF sites with normal traffic figures and where Orange wants to maximize HSDPA throughput -> Configuration 4. F1 is reserved for R99 traffic and F2 for HSDPA one. No traffic balancing between F1 and F2 is applied as it is intended that F1 assumes all the R99 RT and NRT traffic. Only R5&R6 users making use of PS services will be moved to F2. In addition, in order to maximize even more

MS NPO WSE - ES


HSDPA throughput 10 codes activation over F2 cells is highly recommended.

Special 2RF sites where high load of RT traffic is expected (Special Events sites) -> Configuration 5. Even if the intention is to firstly handle RT users in RF1, heavy load conditions could make this layer goes in congestion. To avoid it and to make possible RT users moving to F2 once the UL interference or DL power in F1 becomes higher than a certain threshold, Directed RRC is enabled.

MS NPO WSE - ES


3 2RF Configuration Rules

3.1 Flexi BTS configuration

All BTS cabinets (at the exception of Femto BTS) are able to support multiple RF carriers. Configuring multiple RF carriers can have an impact upon the maximum power which is available per cell. Adding carriers might require to install a new Flexi RF module or splitting an existing one between two layers. Actually, most common solution for Flexi configuration used by OSP requires only Flexi remote re-commissioning with 40Watts + Multicarrier License in order to move from 1+1+1 (20 Watts per cell) configuration to 2+2+2 one (20 Watts per cell).

The support for multiple RF carriers is summarised in the Table1 below.

Node B Cabinet RNC SW/BTS SW RF Carriers Maximum Power per RF Carrier MetroSite 1 8 W

2 4 WMetroSite 50 1 37.5 W

2 15.5 WUltraSite All 1+1+1+1+1+1 20 W or 40W

All 2+2+2+2+2+2 20 W or 40WAll 3+3+3 20 W

RU10 / WBTS5.0 4+4+4 20 WFlexi All 1+1+1 20 W or 40W

RU10/ WBTS 5.0 1+1+1+1+1+1 20W, 30W or 40/60 WRAS06/WBTS4.0 2+2+2 20 W or 40WRU10/ WBTS 5.0 2+2+2 20W, 30W or 40/60 WRU10/ WBTS 5.0 2+2+2+2+2+2 20 W or 30 WRU10/ WBTS 5.0 3+3+3 20 W or 30 WRU10/ WBTS 5.0 4+4+4 20 W or 30 W

MS NPO WSE - ES


Note that with RAS06 maximum 2+2+2 configuration is supported. 3+3+3 will be introduced with RU10 and also 4+4+4 which could be an interesting solution for OSP for those sites in RAN-Sharing with Vodafone.

3.2 HSDPA Schedulers

In RAS06, the number of HSDPA enabled cells is not limited, but the number of schedulers is limited to 4 per BTS, which limits the number of HSDPA enabled cells to 12. HSDPA scheduler can be shared or dedicated, but BTS can handle only one type of scheduler at a time. There are four different types of HSDPA schedulers with different type of capacities. Scheduler capability depends also on RAN release

Minimum Baseband Allocation for 1 – 3 HSDPA cells

Maximum 16 HSDPA users per Flexi sub module – 32 CE reserved Up to 3.6 Mbps / 5 code per scheduler

HSDPA 16 Users per cell

Maximum of 16 HSDPA users per cell can be supported – 32 CE for each scheduler

Up to 3.6 Mbps / 5 code per scheduler

Shared HSDPA Scheduler for Baseband Efficiency for 1 – 3 HSDPA cells

Maximum of 48 users are supported Up to 10.8 Mbps with 16 QAM is supported per Flexi sub module 80 CEs for each scheduler

HSDPA 48 48 HSDPA users per cell Up to 14.4 Mbps with 16 QAM is supported per cell 80 CEs for each scheduler

Note that correct configuration of HSDPA feature and scheduler is critical in terms of CEs consumption. For actual 2RF configuration in Orange network only 3 HSDPA cells must be created with Shared HSDPA Scheduler for Baseband Efficiency in order to ensure 80 CEs consumption (Tcell parameters must be set accordingly).

MS NPO WSE - ES


4 2RF Parameters

4.1 Cell reselection parameters

When UE is in the idle mode it is responsible of the evaluation of the quality of the serving cell and the neighbour cells and for performing a cell re-selection procedure if needed. As described in section 2.1.1 the idea is to force the UEs to camp on F1 in idle mode. For that purpose following parameters must be tuned:

MS NPO WSE - ES


4.2 IFHO and DRRC Parameters

Different methods are available for transferring UE between carriers, based on decision by UE type, services and cell load together with signal level and quality which is used in cell re-selection procedure. Directed RRC Connection Setup works only during call setup phase, while different types of IFHO configurations can handle the mobility traffic also. Inter-Frequency HO can be made for the second layer based on quality, signal level, service or load (last two triggers require that RAS51 & RAS06 optional feature Load and Service based handover – LSHO is activated in the network).

IFHO always require that inter frequency adjacency definitions are done, but Directed RRC Connection Setup works between layers within same BTS and under common Sector id, so adjacency definition is not required. However, cell-reselection requires that adjacency definition is done. The available method depends on the current UE state.

UE state Layering method RAN release Layering criteria

Idle Adjacency definition, re-selection parameters

All Signal level and quality (load)

Idle Connected Directed RRC connection setup for HSDPA layer

All UE release (< RAS05, ≥ RAS05)

Directed RRC connection setup All All, cell load

Enhanced Layering RAS06, optional

Service, UE release, HSDPA/HSUPA support, cell load

Connected (CELL_PCH, CELL_FACH)

Adjacency definition, re-selection parameters

All Signal level and quality (load)

Connected (CELL_DCH) Load and Service based HO

HSPA Capability Based HO (RU10)

RAS05.1, RAS06, RU10 optional

Service and Load

HSPA capability

Connected (CELL_FACH CELL_DCH)

Enhanced Layering RAS06, optional

Service, UE release, HSDPA/HSUPA support, service class, cell load

4.2.1 IFHO

MS NPO WSE - ES


IF neighbour configuration is needed for cell reselection and IFHO purposes, so ADJI definition will be created from F2 to F1 only. Moreover, FMCXs and HOPX templates should be defined according to the following figures:

MS NPO WSE - ES


RF 2

RF 1

HOPS-1HOPS-1

HOPI-2HOPI-1

HOPS-1HOPS-1

RF 2

RF 1

FMCS1 for RT & NRT

FMCS2 for HSDPAFMCI 1

FMCS 2FMCS 3

FMCS 2FMCS 3

FMCS 1FMCS 2 FMCS 1FMCS 2

FMCSs are the same in terms of INTRAfreq parameters.FMCS1 & FMCS2 differents in IFHO criterion <-> FMCI 1.

MS NPO WSE - ES


When UE moves out of the coverage area of 2nd carrier, IFHO is used to move the connection onto the 1st carrier. Only DRRC is used to force UE from F1 to F2 and then IFHO to bring them back to the F1 when moving outside of 2nd carrier coverage areas.

Parameter Object Default F1 F2

IFHOcauseCPICHEcNo FMCIDisabled (0)

0 0

IFHOcauseCPICHrscp FMCIDisabled (0)

0 1

IFHOcauseTxPwrDL FMCIDisabled (0)

0 0

IFHOcauseTxPwrUL FMCIDisabled (0)

0 0

IFHOcauseUplinkQuality FMCIDisabled (0)

0 0

Basic IFHO parameter can be used between F2 -> F1. However cell-specific settings are used to facilitate RSCP based IFHO to target cell. AdjiPlossMargin uses different setting to make easier RSCP based IFHO to target cell. In addition different RSCP thresholds are defined for RT/NRT and HSPA users in order to prioritize F2 for HSPA usage. Recommended values are presented in the following file:

4.2.2 DRRC

As already mentioned, the basic functionality of Directed RRC connection setup is similar in RAS06 and earlier releases. The difference is in parameter setup: while earlier there was a unique parameter to define if either DRRC Setup or DRRC Setup for HSDPA layer is activated, in RAS06 there are dedicated parameters for both (DirectedRRCEnabled and DirectedRRCForHSDPAEnabled parameters). However, these parameters can be activated simultaneously only if parameter DirectedRRCForHSDPALayerEnhanc is enabled. Enabling DirectedRRCForHSDPALayerEnhanc require that RAS06 optional feature HSPA Layering for UEs in Common Channel is activated.

MS NPO WSE - ES


Parameter for enabling basic DRRC features like DRRC connection setup and DRRC connection setup for HSDPA layer can be found in the table below.

MS NPO WSE - ES


Parameter Object RangeParameter Description

DirectedRRCEnabled WCEL

0 (Disabled),1 (Enabled)

Enables/disables the use of the directed RRC connection setup in the cell.

DirectedRRCForHSDPALayerEnabled WCEL0 (Disabled), 1 (Enabled)

Enables / disables the use of the Directed RRC connection setup for the HSDPA layer in the cell.

Directed RRC Connection Setup is intended to balance the DPCH load between RF carriers (Enabled with parameter DirectedRRCEnabled. The table below presents parameters for DRRC connection setup DPCH load balancing

ParameterObject

Range Parameter Description

DRRCPrxOffset WCEL-10..0 dB, step 0.1 dB

Threshold level which the UL load of the source cell must exceed before the Admission control of the RNC may direct the RRC connection setup to another cell within the sector.

DRRCptxOffset WCEL-30..0 dB, step 0.1 dB

Threshold level which the DL load of the source cell must exceed before the Admission control of the RNC may direct the RRC connection setup to another cell within the sector.

DRRCprxMargin

WCEL-30..30 dB, step 0.1 dB

Threshold level which the uplink load of the cell may not exceed in order for the Directed RRC Connection Setup to be possible from another cell (source cell) of the same sector.

DRRCptxMargin WCEL-30..30 dB, step 0.1 dB

Threshold level which the downlink load of the cell may not exceed in order for the Directed RRC Connection Setup to be possible from another cell (source cell) of the same sector.

Parameters related RAS06 optional feature HSPA Layering for UEs in Common Channels can be found in the following table. If DirectedRRCForHSDPALayerEnhanc is OFF, these parameters are not used and feature is not enabled. (RAS06 optional feature)

MS NPO WSE - ES


Parameter Object Range Parameter Description

DirectedRRCForHSDPALayerEnhanc

RNC0 (Disabled), 1 (Enabled)

Enabled/disabled enhancements for DRRC connection setup for the HSDPA layer feature

DRRCForHSDPALayerServices

RNC

204 (11001100), I & B calls, Inter-RAT cell re-selections and Inter-RAT cell change order

Only UEs which establishment cause is listed with this parameter can be transferred between HSDPA layers and from non-HSDPA layer to HSDPA layer.

HSDPALayerLoadShareThreshold

RNC0..48, step 1, (default 3)

Define threshold (number of HSDPA users) for load sharing between HSDPA layers. When the threshold is reached in any of the cells in the same sector, the HSDPA load sharing between layers is done. The load sharing decision making is based on the available HSDPA power per user and cell weight.

DisablePowerInHSDPALayeringDecision

RNC 0 (No), 1 (Yes)

Define if available HSDPA power is taken into account in the decision making for HSDPA layering. If HSDPA power is not used in the decision making, then only the number of HSDPA users in the cell and cell weight will be taken into account.

CellWeightForHSDPALayering

WCEL 0.01..1, step 0.01Used to give weight for the cell in making the HSDPA layering decision.

When parameter DirectedRRCForHSDPALayerEnhanc is enabled together with parameter DirectedRRCForHSDPALayerEnabled – following enhancements are in use:

1. The RNC accounts for the service requested in the RRC connection request when making the decision of Directed RRC connection setup to HSDPA layer. The services are defined with the DRRCForHSDPALayerServices parameter. And only UEs which establishment cause is listed with parameter are transferred between HSDPA layers and from non-HSDPA layer to HSDPA layer.

2. The RNC supports more than 2 layers.

3. The RNC supports HSDPA load sharing between layers.

4. The RNC supports simultaneous use of Directed RRC Connection Setup and Directed RRC Connection Setup for HSDPA layer features (the DirectedRRCEnabled and DirectedRRCForHSDPALayerEnabled parameters are enabled).

Re-direction from CELL_FACH is based upon the optional feature, RAN1011, HSPA Layering for UE in Common Channels. Re-direction is applicable during the state transition to CELL_DCH. Main objective is to separate HSDPA traffic from non-HSDPA traffic. Feature is enabled using parameter below.

MS NPO WSE - ES


Parameter Object Range Parameter Description

HSDPALayeringCommonChEnabled WCEL0 (Disabled), 1 (Enabled)

Enables / disables the use of HSDPA layering for UEs in common channel features in the cell.

ServicesToHSDPALayer RNC

0 (Any type of service is requested), 1 (NRT PS RAB is requested)

In state transition from Cell_FACH to Cell_DCH, the UE is transferred to the HSDPA layer if it has requested the service to be defined with this parameter.

In case Configuration 4 is applied:

Directed RRC connection setup for HSDPA layer used to direct HSDPA capable UEs to the HSDPA layer and non-HSDPA capable UEs to the R99 layer. Directed RRC connection setup for HSDPA layer is used in order to redirect non-HSDPA capable UEs from frequency F2 to frequency F1. This option does not provide load balancing for R99 traffic or for HSDPA traffic. UEs are redirected based on they HSDPA capability only.

ParameterObject Default

F1 F2

DirectedRRCEnabled WCEL 1 (Enabled) 0 0DirectedRRCForHSDPALayerEnabled

WCEL 0 (Disabled) 1 1

In case configuration 5 is applied:

ParameterObject Default F1 F2

DirectedRRCEnabled WCEL 1 (Enabled) 1 1DirectedRRCForHSDPALayerEnabled WCEL 0 (Disabled) 1 1DRRCPrxOffset WCEL -10 -10 -10DRRCptxOffset WCEL -30 -30 -30DRRCprxMargin WCEL 0 0 0DRRCptxMargin WCEL -5 -5 -5

MS NPO WSE - ES


4.3 List of parameters

MS NPO WSE - ES


Date post:	07-Nov-2014
Category:	Documents
Upload:	serverca
View:	84 times
Download:	4 times

2RF Sites Configuration Guidelines RAS06

Documents