hspa layering for ues in common channels

7/26/2019 HSPA Layering for UEs in Common Channels

http://slidepdf.com/reader/full/hspa-layering-for-ues-in-common-channels 1/25

© 2007 Nokia DRAFT Issue 1-1 dn0666854

Nokia Proprietary and Confidential

Nokia WCDMA RAN System, Rel. RAS06, Pre-Release

Documentation

HSPA Layering for UEs in Common

Channels





Short feature description

• This feature transfers UEs to correct layer based on their HSDPA and HSUPA

capability.

• Non-HSDPA UEs are transferred to the non-HSDPA layer.

• HSDPA capable UEs are transferred to the layer that supports HSDPA.

• HSUPA capable UEs are transferred to layer that supports HSUPA.

• If there are several HSDPA, HSUPA or non-HSDPA layers, load balancing is utilized.

• The transfer occurs in

• RRC connection setup phase (Directed RRC connection setup for HSDPA layer)

• State transition from Cell_FACH to Cell_DCH.

• This feature also covers enhancements to the Directed RRC Connection Setup

for HSDPA Layer feature.





Operator benefits

• The feature greatly enhances two (or several) layer operation with HSDPA and

HSUPA. Choosing the correct layer for the UE on each transition to Cell_DCH

guarantees correct layer based on the UE capability on all practical mobility

scenarios.• When several layers support HSPA, the feature chooses the layer in an optimal

manner based on expected DL throughput on each HSPA layer.





Main functionality

Contents:

1. Introduction

2. Signalling

3. Decision making is based on

• UE capability in decision making

• The service which UE is going to use in decision making

4. Decision making in RRC connection setup phase

• Directed RRC connection setup in non-HSPA layer

• Directed RRC connection setup in HSDPA/HSPA layer

5. Decision making in state transition Cell_FACH -> Cell_DCH phase

• State transition Cell_FACH -> Cell_DCH in non-HSPA layer

• State transition Cell_FACH -> Cell_DCH in HSDPA/HSPA layer

6. HSDPA load balancing

7. Interworking with Directed RRC connection setup feature





Introduction

• Feature consist of

• Enhancement of Directed RRC connection setup for HSDPA layer

• The service indicated by UE in RRC connection request is taken into account

• More than 2 layers are supported

• 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 indecision making for Rel-6 and onwards UEs.

• Moving UE to correct layer in state transition Cell_FACH -> Cell_DCH phase

• Feature works inside BTS between cell which has same Sector ID. (Also

Transmission power of primary CPICH (PtxPrimaryCPICH) and Offset of the P-

CPICH, reference service powers (CPICHtoRefRABoffset) and PLMN code

(MCC + MNC) needs to be identical.)





Signalling

Directed RRC connection set up for HSDPA

layer (successful case signalling not

changed from RAN05)

HSPA layering for UEs in common channels

RNC

RLC parameters needto be changed

Frequency layer / cell selectionand capacity allocation

DL capacity need is detected by MAC orRAB Assignment Request from CS core

BTSUE

UE moves to CELL_DCH stateand to new frequency

RRC:Radio Bearer Reconfiguration (Frequency Info)

RRC: Radio Bearer Reconfiguration Complete

RRC:Measurement Report

(AND/OR)UL capacity need isdetected by MAC

UE is in CELL_DCH state

NBAP Radio Link Setup procedure

UE is in CELL_FACH or CELL_PCH state





Decision making is based on

• UE capability

• Cell capabilities (non-HSDPA, HSDPA or HSPA)

• The service which UE is going to use

• Load balancing is utilized.

Source and target cell load is taken into account

• Measured Non-HSPA load in a cell• Measured HSDPA load in a cell

• Number of HSDPA and HSUPA users in a cell

• CellWeightForHSDPALayering (operator parameter)





UE capability in decision making

Directed RRC connection set up for HSDPA

layer

• UE capability is interpret from the

information UE sends in RRC ConnectionRequest

• access stratum release indicator IE

(indicates the release that UE

supports) (Used already in RAS05)

• UE capability indication IE (indicates

the HSDPA and HSUPA capability of

Release 6 and onwards UEs)


• When UE is either in Cell_FACH or

Cell_PCH state RNC has alreadyinformation of UE HSDPA and HSUPA

capability.





The service which UE is going to use in decision

makingDirected RRC connection set up for HSDPA

layer

• Establishment cause IE in RRC

connection Request (indicates what kindof service UE is expected to be use).

• DRRCForHSDPALayerServices is

operator parameter. Operator can define

which services (indicated in Establishment

cause IE) it wants to direct to HSPA layer.


• If PS service is started DL/UL capacity

need is detected by MAC layer orMeasurement Report from UE is

received.

• If CS service is started RAB Assignment

Request is received from CS core.

• ServicesToHSDPALayer is operator

parameter. Operator can define if only PS

RABs or all RABs are directed to HSDPA

layer.





Decision making in RRC connection setup phase

• A cell which HSPA capability is identical with UE HSPA capability is selected ifpossible.

• R99 and Rel-4 UE -> non HSDPA cell

• Rel5 UE -> HSDPA cell• Rel-6 and newer non-HSDPA UE -> non HSDPA cell

• Rel-6 and newer HSDPA UE -> HSDPA cell

• Rel-6 and newer HSDPA&HSUPA UE -> HSDPA&HSUPA cell

• Establishment cause sent by UE needs to be activated inDRRCForHSDPALayerServices in the case the target cell supports HSDPA.

• Target cell load should not be too high

• HSDPA target cell – Maximum number of HSDPA users not reached.

• Non-HSDPA target cell – Directed RRC connection setup triggers not reached.• If several identical HSDPA candidate cells exist a cell with best available

HSDPA power per user is selected. (HSDPA load balancing)





Directed RRC connection setup in non-HSPA layer

Decision making

1. UE HSPA capability = cell HSPAcapability (f1)

A Yes -> current layer (f1)

B&C No -> f2 & f3

2. Establishment cause =DRRCForHSDPALayerServices

B&C No -> current layer (f1)

B&C Yes -> f2 & f33. UE HSPA capability = target cell

HSPA capability (f2 & f3)

B -> f2 & f3

C -> f3

4. Better available HSDPAthroughput

B -> f2 or f3

f1, Rf1, R´́9999

f2, HSDPAf2, HSDPA

f3, HSDPA&HSUPAf3, HSDPA&HSUPA

A

B

UE reporting Rel5 or

Rel-6 & HSDPA capability

Any other UE

UE reporting Rel-6

HSDPA & HSUPA capability

C





Directed RRC connection setup in HSDPA/HSPA layer

Decision making

1. UE HSDPA capability = cell HSDPA

capability (f2/f3)

A No -> f1

B&C No -> f2 & f3

2. Establishment cause =

DRRCForHSDPALayerServices

B&C No -> current layer (f2/f3)

B&C Yes -> f2 & f3

3. UE HSUPA capability = cell HSUPA

capability (f2 & f3)

B -> f2 & f3

C -> f3

4. Better available HSDPA throughput (forinteractive and background

Establishment cause)

B -> f2 or f3

f1, Rf1, R´́9999

f2, HSDPAf2, HSDPA


A

B



Any other UE

UE reporting Rel-6


C





Decision making in state transition Cell_FACH ->

Cell_DCH phase• A cell which HSPA capability is identical with UE HSPA capability is selected if

possible.

• non-HSDPA UE -> non HSDPA cell

• HSDPA UE -> HSDPA cell

• HSDPA&HSUPA UE -> HSDPA&HSUPA cell

• RAB type needs to be activated in ServicesToHSDPALayer (PS, any type of

service) in the case the target cell supports HSDPA.

• Target cell load should not be too high

• HSDPA target cell – Maximum number of HSDPA users not reached.

• Non-HSDPA target cell – Directed RRC connection setup triggers not reached.

• If several identical HSDPA candidate cells exist a cell with best availableHSDPA power per user is selected. (HSDPA load balancing)





State transit ion Cell_FACH -> Cell_DCH in non-HSPA

layer Decision making

1. UE HSPA capability = cell HSPA

capability (f1)

A Yes -> current layer (f1)B&C No -> f2 & f3

2. RAB type =

ServicesToHSDPALayer

B&C No -> current layer (f1)

B&C Yes -> f2 & f3

3. UE HSPA capability = target cell

HSPA capability (f2 & f3)

B -> f2 & f3

C -> f3

4. Better available HSDPA

throughput

B -> f2 or f3

f1, Rf1, R´́9999

f2, HSDPAf2, HSDPA


A

B



Any other UE

UE reporting Rel-6

HSDPA & HSUPA

capability

C





State transit ion Cell_FACH -> Cell_DCH in

HSDPA/HSPA layer Decision making

1. UE HSDPA capability = cellHSDPA capability (f2/f3)

A No -> f1

B&C No -> f2 & f3

2. RAB type = interactive orbackground

B&C No -> current layer (f2/f3)

B&C Yes -> f2 & f33. UE HSUPA capability = cell

HSUPA capability (f2 & f3)

B -> f2 & f3

C -> f3

4. Better available HSDPAthroughput

B -> f2 or f3

f1, Rf1, R´́9999

f2, HSDPAf2, HSDPA


A

B



Any other UE

UE reporting Rel-6


C





HSDPA load balancing (under threshold) 1/3

Cell which has1. highest cell weight

(CellWeightForHSDPALayering)

2. number of HS-DSCH

users is highest

shall be selected.

Cell

f1

Number of HS-DSCH users in the cell in the decision making moment

Max

0

HSDPALayerLoadShareThreshold

Cell

f2

Cell

f3





HSDPA load balancing (over threshold) 2/3

Cell which has

1. highest cell weight

(CellWeightForHSDPALayering)

2. number of HS-DSCH

users is highestshall be selected.

Cell

f1

Number of HS-DSCH users in the cell in the decision making moment

Max

0

HSDPALayerLoadShareThreshold

Cell

f2

Cell

f3

Cell which has highest

HSDPA power per

user available shall beselected





HSDPA load balancing (HSDPA power per user) 3/3

( )1

*

+

−=

DPAusers NumberOfHS

yeringForHSDPALaCellWeight PtxNonHSPAPPerUser HSDPApower Max

Operator parameter

(Range 0.01 … 1)

Number of HSDPA users

active in the cell

A cell with highest available HSDPA power per user shall be selected.

HSPA

power

Non

HSPA

power

Cell

PtxNonHSPA

Pmax

0



© 2007 Nokia DRAFT Issue 1-1 dn0666854Nokia Proprietary and Confidential

Interworking with Directed RRC connection setup

feature(Both parameters DirectedRRCEnabled and DirectedRRCForHSDPAEnabled are enabled.)

• The decision of directed RRC connection setup for HSDPA layer is done.

Decision = Change layer: Directed RRC connection setup for HSDPA layer is done.

Decision = Do not change layer: The decision of directed RRC connection setup is done.

• If several candidates exist (more than 2 layers) for Directed RRC connection setup UE is

tried to keep in most suitable layer from capability point of view.

• Non-HSDPA capable UE -> non-HSDPA capable cell

• HSDPA capable UE -> HSDPA or HSDPA&HSUPA capable cell

• HSDPA&HSUPA capable UE -> HSDPA&HSUPA capable cell is preferred and HSDPA

capable is next preferred.

• HSDPA/HSPA capable UEs in Directed RRC connection setup

• are not transferred away from HSDPA/HSPA layer if they are requesting interactive or

background service.• can be transferred away from HSDPA/HSPA layer if they are requesting other than interactive

or background service.




How feature will be implemented to RAN

• The affected NEs are RNC and NetAct.




Interaction with other features

• Directed RRC connection setup (explained in couple of slides before)

• Service and load based handover:

• Service and load based handovers are not done to HSDPA capable UEs in HSDPA

capable cell.

• Service and load based handover can transfer non HSDPA capable UE or HSDPA

capable UE which is in non-HSDPA capable cell to different layer than this feature or

directed RRC connection setup have directed the UE.




Feature specific parameters 1/3

Enables / disables the use of Directed

RRC connection setup for HSDPA

layer in the cell. (Old RAN05 feature)

00 Disabled1 EnabledOnlineDirectedRRCForHSDPALayerEnabledWCEL

Enables / disables the improvements

for RAN05 feature Directed RRC

connection setup for HSDPA layer .

00 Disabled

1 Enabled

OnlineDirectedRRCForHSDPALayerEnhancRNC

Enables / disables the use of HSDPA

layering for UEs in common channelsfeatures in the cell.

00 Disabled

1 Enabled

OnlineHSDPALayeringCommonChEnabledWCEL

Enables / disables the use of Directed

RRC connection setup in the cell. (Old

RAN04 feature)

10 Disabled

1 Enabled

OnlineDirectedRRCEnabledWCEL

DescriptionDefault

Value

RangeModificationNameObject





Directed RRC connection

setup for HSDPA layer (from

non-HSDPA layer to HSDPA

layer) in the cell is done ifthe UE indicates the service

in RRC Connection Request

(Establishment cause) which

is activated by this

parameter.

interactive

and

background

calls, Inter-RAT cell re-

selections

and Inter-

RAT cell

change order

Bitmask (16

bits)

OnlineDRRCForHSDPALayerServicesRNC

In state transition fromCell_FACH to Cell_DCH the

UE is transferred to HSDPA

layer if it has requested the

service defined with this

parameter.

00: Any typeof service is

requested

1: NRT PS

RAB is

requested

OnlineServicesToHSDPALayer RNC

DescriptionDefault

Value







This parameter is used to give

weight for the cell in HSDPA

layering decision making.

10.01 – 1,

step 0.01

OnlineCellWeightForHSDPALayeringWCEL

This parameter is used to

define if available HSDPApower is taken into account in

decision making for HSDPA

layering.

00 NO

1 YES

OnlineDisablePowerInHSDPALayeringDecisionRNC

This parameter is used todefine the threshold (number

of HSDPA users) for load

sharing between HSDPA

layers.

10Disabled

1 Enabled

OnlineHSDPALayerLoadShareThresholdRNC

DescriptionDefault

Value


hspa layering for ues in common channels

Documents