Вы находитесь на странице: 1из 13

Direct Resurce Allocation for HSPA

RAN 1762

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

Direct Resource Allocation for HSPA

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

Direct Resource Allocation for HSPA


Introduction
Concept
Enabling the feature
Signalling
Other

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

Direct Resource Allocation for HSPA


Introduction

RAN 1762
Basic Software Feature (BSW)

Prior to RU20 for a NRT service a 0/0 DCH was allocated to a user :
If a Capacity Request (CR) was received, RNC made channel type selection
DCH intial bitrate (UL/DL) was allocated if resource available (e.g. 64k / 64k)
HSDPA and A-DCH or E-DCH was allocated depending on configuration
If no Capacity Request received by RNC, UE was moved to Cell_FACH
(after RNC: DLcapacityReqWait default 5 sec)

UE must support HSDPA and HSUPA transport channels


HSDPA and HSUPA must be enabled in the cell
4

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

Direct Resource Allocation for HSPA


Introduction

In RU20 HSPA transport channels can be allocated directly in Cell_DCH or


Cell_FACH (Common Channel Setup), without waiting for capacity request.

Operator can manage the feature to allocate HSPA directly


never (DCH 0/0 is used) or
when UE is in Cell_DCH and/or
when UE is in Cell-FACH

DRA is always used when UE has F-DPCH allocated


(even DRA shall not e used in a cell)

It is used for Background and Interactive traffic classes


DCH in downlink / DCH in uplink still used 0/0 kbps DCH allocation
DCH /DCH or
HSDPA / DCH
Direct Resource Allocation for HSPA reduces the HSPA cal setup delay
5

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

Enabling Direct Resource Allocation for HSPA

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

Direct Resource Allocation


Enabling the feature

RNC: RABDRAEnabled
The parameter enables/disables the use of the direct resource allocation for HSPA. It
also defines whether the direct resource allocation for HSPA is applied in Cell_FACH
state, Cell_DCH state or both. If the feature is enabled, HS-DSCH and E-DCH allocation
is tried for PS data of interactive and background traffic classes during the NRT RAB
setup.
Range and Step: 0 (Disabled), 1 (Enabled in Cell_FACH), 2 (Enabled in Cell_DCH), 3 (Enabled in
Cell_FACH and Cell_DCH)

Default: 0
Options:
0 (Disabled): Direct resource allocation for HSPA is not applied but DCH 0/0 kbps is allocated and traffic volume measurements
started in connection with PS NRT RAB setup
1 (Enabled in Cell_FACH): Direct resource allocation for HSPA is applied in Cell_FACH state but not in Cell_DCH state.
2 (Enabled in Cell_DCH): Direct resource allocation for HSPA is applied in Cell_DCH state but not in Cell_FACH state.
3 (Enabled in Cell_FACH and Cell_DCH): Direct resource allocation for HSPA is applied in Cell_FACH state and in Cell_DCH state.

Direct resource allocation is applied in the case of full HSPA (HS-DSCH/E-DCH and F-DPCH allocated)
irrespective of the value of this parameter.
7

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

Signaling

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

Signalling in CELL_DCH
UE

Node-B

RNC

CN

Signalling link established and UE in Cell_DCH state

HSPA is allocated during

RANAP:RAB ASSIGNMENT REQUEST [for PS HSPA NRT]


HSPA capacity request
for direct resource
allocation

RAB establishment

Replaces the allocation


of a 0/0 kbps DCH

NPAB: RADIO LINK RECONFIGURATION PREPARE


NPAB: RADIO LINK RECONFIGURATION READY
L2 resource allocation and Iub transmission setup

GTP tunnel creation


NPAB: RADIO LINK RECONFIGURATION COMMIT

RRC: RADIO BEARER SETUP [HS-DSCH + E-DCH]

RRC: RADIO BEARER SETUP COMPLETE

RANAP: RAB ASSIGNMENT RESPONSE

In case of successful DRA, HSPA connection is established for the user plane

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

Signalling in CELL_FACH
UE

Node-B

RNC

CN

HSPA is allocated during


RAB establishment

Signalling link established and UE in Cell_FACH state after Common Channel setup (RAN1797)

Moves the UE into

RANAP:RAB ASSIGNMENT REQUEST [for PS HSPA NRT]

CELL_DCH during RAB


establishment

HSPA capacity request for


direct resource allocation
NPAB: RADIO LINK SETUP REQUEST

Previously, the UE would

NPAB: RADIO LINK SETUP RESPONSE

be left in CELL_FACH until


after a subsequent
capacity request

L2 resource allocation and Iub transmission setup

GTP tunnel creation


RRC: RADIO BEARER SETUP [HS-DSCH + E-DCH]
RRC: RADIO BEARER SETUP COMPLETE
RANAP: RAB ASSIGNMENT RESPONSE

In case of successful DRA, HSPA connection is established for the user plane

10

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

NRT over NRT

11

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

NRT over NRT


Enhanced Priority based Scheduling (ePBS) represents NRT-over-NRT functionality
Serving RNC

direct resource allocation does not trigger NRT-over-NRT actions


Drift RNC

can not differentiate between capacity requests for direct resource


allocation and other capacity requests
direct resource allocation can trigger NRT-over-NRT actions

If direct resource allocation fails as a result of congestion then connection establishment

proceeds as in RU10, i.e. 0/0 kbps DCH is allocated for connection establishment in
CELL_DCH, and traffic volume measurements are configured to trigger capacity requests

12

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa

Thank You !

13

Nokia Siemens Networks

RU 20 SD RRM and PM / 13.07.2009 / THa