13 6255 NAK HSUPA Protocol Features

Contents
UMTS/HSPA Radio Resource Management & Parameter

 Introduction to Radio Resource Management
 Power Control
 Load Control
 Admission Control
 Packet Scheduling
 Code Tree Management
 PLMN and Cell Selection
 Handover Procedures
 HSDPA Protocol Features
 HSDPA Power Management
 HSDPA Code Resource Management
 HSDPA Mobility
 HSUPA Protocol Features
 HSUPA Power Management
 HSUPA Mobility
 HSPA+
00-1 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Content
HSUPA Protocol Features
 Introduction
 Radio Channel Configuration
 Fast Packet Scheduling & Link Adaptation
 10 and 2 ms TTI
 H-ARQ: Hybrid Automatic Repeat Request

HSUPA Objectives and Standardization
TS 25.309:
FDD Enhanced UL Standardisation
Overall
Description
closed:
R6 (06/2005)
TS 25.309 FDD Enhanced UL:

„The technical objective
of the FDD Enhanced UL work item
is to improve the performance of UL DCH,
i.e. to increase capacity & throughput • improves UL resource
and reduce delay. “ efficiency and throughput
• higher peak rates
• increasing coverage for
higher data rates
• reduced delays

HSUPA and HSDPA Differences and Similarities
Problems/Differences
Why not
adapting Power Control
DL centralized PC,
HSDPA solutions UL individual PC !
to UL?  pure time multiplexing difficult !
UL fast PC still necessary
(UL interference  UL scrambling codes)
UL no channelization code limitation

 more codes available  high order
modulation not so important
higher order modulation difficult for UE
SHO requested (full mobility and coverage)
HSUPA (similar to HSDPA) based on

Fast H-ARQ terminating at Node B
Fast Node B controlled UL scheduling
Fast link adaptation
but: no enhanced/adaptive modulation

HSUPA Network Modifications
HSUPA: functionalities shifted
TS 25.309: from RNC to Node B:
FDD Enhanced UL
Overall UTRAN and UE: Acknowledged transmission (H-ARQ)
Description modified PHY Layer  faster retransmission / reduced delays !
modified MAC  less Iub traffic !
UL Packet Scheduling*
 fast UL resource allocation !
Uu
Node
RNC B modified transport
Iub and physical channels
modified coding
UE
retransmission
Reduced
new functions more

(SW- intelligency new UE`s
modifications) (SW-modifications)

HSUPA Protocol Architecture
RNC MAC-es UE MAC-es and MAC-e

• in-sequence delivery (reordering) • H-ARQ retransmission
• SHO data combining • Scheduling and MAC-e multiplexing
• E-DCH TFC selection
UE
Node
S-RNC Iub
B
• Node B MAC-e •
• • H-ARQ retransmission •
• •
• Scheduling and MAC-e multiplexing
RLC RLC
MAC-d MAC-d
MAC-es
MAC-es / MAC-e
E-DCH FP Iub E-DCH FP MAC-e Uu
PHY PHY PHY PHY

Content
 Introduction
 10 and 2 ms TTI
 Hybrid Automatic Repeat Request

E-DCH Transport Channel
E-DCH characteristics
• Transport channel dedicated to 1 UE
• UL only
• 1 Transport Block / TTI
• Subject to Node B controlled scheduling and HARQ
• Supports 2 ms and 10 ms TTI
Enhanced Dedicated Channel E-DCH
Dedicated Channel DCH

A channel dedicated to 1 UE
used in UL or DL.
S-
RNC Node
B UE
Iub Uu

HSUPA Physical Channels
TS 25.211:
Transport and
Physical channels
(FDD)
E-AGCH
E-DCH Absolute Grant Channel
E-RGCH
E-DCH Relative Grant Channel
E-HICH
E-DCH Hybrid ARQ Indicator Channel UE
E-DPDCH
Enhanced Dedicated Physical Data Channel
Node
E-DPCCH
B Enhanced Dedicated Physical Control Channel
associated DCH

HSDPA and HSUPA Channel Mapping
Logical
DL BCCH PCCH CTCH CCCH DCCH DTCH Rel. 5: Channels
HSDPA
BCH PCH FACH DCH HS-DSCH Transport

Channels
P-CCPCH S-CCPCH DPDCH DPCCH HS-PDSCH Physical

Channels
CCCH DCCH DTCH Logical

UL Channels
RACH DCH E-DCH Transport

Channels
R6:
HSUPA Physical
PRACH DPDCH DPCCH HS-DPCCH E-DPDCH E-DPCCH Channels

E-DPDCH and E-DPCCH (1/3)
E-DPDCH
SF = 256 – 2, R = 15 – 1920 kbps
1 Slot = 2560 chip = 2/3 ms
Slot #0 Slot #1 Slot #2 Slot #i Slot #14
1 frame for 2 ms TTI
1 frame for 10 ms TTI
Bit / 10
E-DPDCH Channel bit Bit / 2 ms
SF rate [kbps]
ms
frame
Bit / slot
carries UL packet data (E-DCH) frame
up to 4 E-DPDCH for 1 radio link
64 60 600 120 40
SF = 256 – 2 (BPSK)
32 120 1200 240 80
pure user data and 24 bit CRC (1 CRC/TTI)
TTI = 2 / 10 ms 16 240 2400 480 160
Managed by MAC-e/-es 8 480 4800 960 320
Error protection by turbo coding 1/3 4 960 9600 1920 640
SHO support
2 1920 19200 3840 1280

E-DPCCH
SF = 256, 10 bit
1 Slot = 2560 chip = 2/3 ms
Slot #0 Slot #1 Slot #2 Slot #i Slot #14
1 frame for E-DPCCH
E-DPCCH
E-TFCI information (7 bit)
indicates E-DCH transport block size
i.e. coding at given TTI (TS 25.321 Annex B)
Retransmission sequence number (2 bit)
Value = 0 / 1 / 2 / 3 for:
Initial transmission, 1st / 2nd / further retransmission
„Happy" bit (1 bit)
Indicating if UE could use more resources or not
Happy 1
Not happy 0

Maximum number DPCCH TS 25.213

of simultaneous DPDCHs Sdpch
UL DCHs Spreading
Sdpch,n

HS-DPCCH Shs-dpcch I+jQ
Spreading
S
E-DPDCHs
E-DPCCH Se-dpch
Spreading
Configuration #i DPDCH HS-DPCCH E-DPDCH E-DPCCH

1 6 1 - -
2 1 1 2 1
3 - 1 4 1

12
E-AGCH and E-RGCH
E-AGCH
Carries DL absolute grants for UL E-DCH
Contains UE-Identity (E-RNTI) and
absolute UE power ratio E-DPDCH / DPCCH
Transmitted every 2 ms
SF = 256 (30 kbps, 20 bit/Slot)
Node
B
UE
E-RGCH
Carries DL relative grants for UL E-DCH E-DCH transmission
Contains UE identity and request to change After E-AGCH
After E-RGCH
UE power ratio („UP“, „HOLD“, „DOWN“)
Non-scheduled transmission

E-HICH
Node
B
UE
E-HICH
Carries H-ARQ acknowledgement indicator for UL E-DCH
Contains ACK/NACK (+1, -1) and UE-Identity

DL Channel Code Resource Management (1/3)
SF16
SF32 32
SF64 64 64 64
FACH / PCH
SF128 128 128 128 128 128 128 128
HS-SCCH E-RGCH/E-HICH
SF256 256 256 256 256 256 256 256 256 256 256 256 256 256 256 256
CPICH, BCH, AICH, PICH E-AGCH 2/10 ms
128 128
Allocated CC Blocked CC E-RGCH and E-HICH

• Share the same code with SF 128
E-AGCH • Distinguished by two different signatures per user
• Occupies 2 codes with SF 256 • Total capacity of 1 code = 40 signatures
• One channel needed for 10 ms TTI • Up to 20 users supported by 1 code
and one for 2 ms TTI

- Upgrade of E-RGCH / E-HICH resources by 1 code

if occupation of 1 code exceeds certain threshold
- Downgrade of E-RGCH / E-HICH resources by 1 code
if occupation falls below this threshold again
Too much users Offer one code more
Threshold e.g.15 users
Maximum 20 users
Few users again Remove additional code again
Nokia Ericsson Huawei

Maximum occupation of
E-RGCH/E-HICH code RsrvdSignaturesOffset eulNoERgchGroups Hard coded
5..11; 10 1..16; 4
All settings per cell

- If two codes for E-RGCH / E-HICH strongly occupied

upgrade to third code and so on
- Maximum number of codes has to be specified
Too much users Too much users Offer further code
Threshold Threshold
Nokia Ericsson Huawei
Maximum number of Hard coded numEhichErgchCodes Hard coded

E-RGCH/E-HICH codes 4 1..4; 2 8
Settings per cell

Content
 Introduction
 10 ms & 2 ms TTI

Fast Packet Scheduling
HSUPA packet scheduling performed by Node B

Checks every TTI, whether there is a scheduling request by an unhappy UE
Offers resources in dependence on actual UL noise rise
UE is allowed to transmit with certain power ratio E-DPDCH / DPCCH
Benefits
Fast up to date decision
Higher overload threshold possible
Scheduling request
Buffer status
Happy bit
S-RNC Iub
Scheduling grant
Power ratio E-DPDCH / DPCCH
E-AGCH
E-RGCH
E-DCH data

Fast Link Adaptation / Coding
After allocation of power ratio E-DPDCH / Under very good radio conditions multi-code
DPCCH UE checks further on operation is possible
Capability
The following options exist:
Power status
2 x SF4 (1.92 Mbit/s)
Buffer status
2 x SF2 (3.84 Mbit/s)
2 x SF4 + 2 x SF2 (5.76 Mbit/s) (for 2ms TTI only)
UE decides about
SF (256-2) The feature usually has to be activated by
Coding rate (1/4-1) specifying a maximum HSUPA data rate
Number of codes (1-4)
Maximum HSUPA data rate
Settings per RNC only

Maximum HSUPA data rate – Huawei
EdchRateAdjustSet
Settings per RNC
Each of the following levels can be
enabled/disabled individually (Bit
Field Type)
8,16,32,64,128,144,256,384,
608,1450,2048,2890,5760, 11480
kbit/s
EdchRateAdjustSet
• MO = UEDCHRATEADJUSTSET
• Description: (HSUPA DCCC Bit Field Type) Data rate set for adjusting the EDCH's data rate. The DCCC
function can allocate any data rate in such a data rate set to an EDCH. If there are a small number of data
rates in such a data rate set, the number of RB reconfigurations decreases and the data rate of an EDCH can
be quickly increased from the GBR to MBR. However, resource utilization is low. If there are a large amount of
data rates in such a data rate set, bandwidth resources can be appropriately allocated and resource utilization
is high. However, the number of RB reconfigurations increases and the increase from the GBR to MBR takes
a long period of time.

Maximum HSUPA data rate – Ericsson
eulMaxAllowedSchRate
0..6016, 5120 kbit/s Settings per BTS
eulMaxAllowedSchRate
• MO: NodeBFunction
• Description: The maximum allowed scheduled data rate per user.

Maximum HSUPA data rate – Nokia
MaxTotalUplinkSymbolRate Settings per cell
960/1920/3840/5760, 960 kbit/s = 1 x SF4
MaxTotalUplinkSymbolRate
• MO: WCEL
• Category: Basic parameters
• Description: This parameter determines the planned maximum total uplink symbol rate of the E-DPDCH(s) of the
UE in the cell. The lowest parameter value among the parameter values of the cells that belong to the E-DCH
active set is used when the E-DCH is allocated. The signaled value is updated when a soft handover branch
addition or deletion occurs and the lowest value changes. The final maximum total uplink symbol rate is the
minimum of the following limitations: UE capability, BTS capability, cell-based limitation, the possible limitation
which is set based on the maximum uplink user bit rate of the RAB, and the actual available capacity in the
RNC. In case the "HSUPA 2 Mbps" feature is active (state "On" and exist) but the "HSUPA 5.8 Mbps" feature is
not active, the maximum value of this parameter is "2". In this case the system also checks that the maximum
number of BTSs capacity value of "HSUPA 2 Mbps" feature is not exceeded, if the respective parameter value is
set to "2". If it is exceeded, this is informed by the appropriate configuration error and the parameter value
change to "2" is not allowed. In case "HSUPA 5.8 Mbps" feature is active (state "On" and exist), the maximum
value of this parameter is "3" and also the value "2" is allowed although the "HSUPA 2 Mbps" feature is not
active. If not active, the parameter value change to "3" is not allowed.

Scheduling Information SI
SI will be sent as part of the MAC-e header and will be used to provide the serving Node B with a better view of the
amount of system resources needed by the UE and the amount of resources it can actually make use of.
Scheduling Information SI is periodically included in MAC-e PDU tail and contains:
UE power headroom (UPH)
 Ratio maximum UE Tx power / current DPCCH Tx power
Total E-DCH buffer status (TEBS)
 Total amount of data available across all logical channels for which reporting has been requested by RRC
Highest priority logical channel buffer status (HLBS)
 Amount of data available from the logical channel identified by HLID,
 Relative to highest value of buffer size range reported by TEBS when reported TEBS index is not 31
 Relative to 50000 bits when reported TEBS index is 31
Highest priority logical channel identity (HLID)
 Highest priority logical channel with available data
 If multiple logical channels exist with same highest priority, that one corresponding to highest buffer
occupancy will be reported
MAC-e PDU
Service Data (MAC-es PDUs) SI Optional padding
Periodicity for SI Power Offset for SI

Scheduling Information SI – Huawei
Hsupa10msSchPrdForGrant/NonGrant Hsupa2msSchPrdForGrant/NonGrant
HSUPA TTI 10ms schedule period with HSUPA TTI 10ms schedule period with
grant/without grant grant/without grant
10, 20, 50, 100, 200, 500, 1000 ms, 100/ 50ms 10, 20, 50, 100, 200, 500, 1000 ms, 100/ 50ms
Hsupa10/2msSchPrdForGrant/NonGrant
• MO = UFRC
• Description: Time interval of sending HSUPA scheduling information for TTI 10ms/2ms when the user has
Schedule Grant/Non Grant: The larger the value of this parameter, the longer the SI reporting period. As a
result, the network side cannot obtain the SI in time, affecting the scheduling accuracy. The smaller the value
of this parameter, the shorter the SI reporting period. As a result, the network side can promptly obtain the SI,
which makes scheduling more accurate but wastes network resources.

Scheduling Information SI – Ericsson
Not given

Scheduling Information SI – Nokia
PeriodicityForSI PowerOffsetForSI
4..1000 ms; 200 ms 0..6; 1; 3 dB
PeriodicityForSI
• MO: RNHSPA
• Category: Basic parameters
• Description: This parameter defines periodicity for Scheduling Info (SI) in case that the BTS type is WBTS. In
case that the BTS type is NBxxx, periodicity for Scheduling Info (SI) is hard coded as 50 ms. The values define
periodicity in both cases, that is, when no grant is given and when grant is given to the UE.
PowerOffsetForSI
• MO: RNHSPA
• Category: Advanced parameters
• Description: This parameter defines the power offset for Scheduling Info (SI).

Content
 Introduction
 10 ms & 2 ms TTI

Principles
- HSUPA supports both 10 ms & 2 ms TTI

- Benefits of 2 ms TTI
• Reduced re-transmission delay
• Higher peak data rate
• Pre-requisite for 5.76 Mbit/s
- Disadvantages of 2 ms TTI
• Lower coverage
Node
B
UE
2 ms TTI UE
10 ms TTI

10 ms & 2 ms TTI
Transition from 2 ms to 10 ms TTI is triggered:
• A cell supporting 10 ms TTI only becomes active
• Coverage falls below a vendor specific threshold
As coverage criteria are applied
 RSCP of serving cell
 EC/I0 of serving cell
 UE power
Transition from 10 ms to 2 ms TTI is allowed:
• All active cells support 2 ms TTI
• Coverage is better than vendor specific threshold
UE UE
2 ms TTI 10 ms TTI

Selection of 2 ms TTI – Nokia (1/2)
• 2 ms TTI: SRB are mapped onto HSPA (Nokia specific)

• 10 ms TTI: SRB are mapped onto DPDCH (Nokia specific)
• SRB mapping onto HSUPA is mandatory for the 2×SF2 + 2×SF4 configuration because the DPDCH code is
blocked by E-DPDCH codes (3GPP specification)
The TTI selection procedure is triggered during:

• UL channel type selection (DCH or E-DCH)
• an ongoing existing HSUPA connection (TTI switching)
• RAB establishment or release (TTI switching)
The 2 ms HSUPA TTI is selected if:
• HSUPA 2 ms TTI is enabled
• UE supports 2 ms TTI
• RAB combination supports SRB on HSUPA
RNC reconfigures E-DCH 2ms TTI  E-DCH 10ms TTI if 2ms TTI Coverage criteria not fulfilled

Selection of 2 ms TTI – Nokia (2/2)
• Selection starts from CELL_DCH  CPICH RSCP (HSPA serving cell) measured by UE must satisfy the condition:
PtxPrimaryCPICH – CableLoss – Measured CPICH RSCP < CPICHRSCPThreEDCH2MS + MAX(0, UETxPowerMaxRef – P_MAX)
UETxPowerMaxRef CPICHRSCPThreEDCH2MS
-50..33 dBm; 1; 24 dBm 50..160 dB; 1 dB; 136 dB
• Selection in the state transition from CELL_FACH, CELL_PCH, and CELL_URA to CELL_DCH state. CPICH Ec/Io of current cell
measured by UE must satisfy the condition: Measured CPICH Ec/Io > CPICHECNOThreEDCH2MS
CPICHECNOThreEDCH2MS
-24..0 dB; 1 dB; -6 dB
• Selection starts from Inter-RAT Handover to UTRAN or from LTE (Ec/Io of the target cell not known)  Calculated CPICH
Ec/Io of current cell (calculated as the ratio of the Primary CPICH code power and transmitted carrier powermust) must be
higher then LoadBasedCPICHEcNoThreEDCH2MS
LoadBasedCPICHEcNoThreEDCH2MS • This is used also during the state transition from CELL_FACH,
-25..0 dB; 1 dB; 0 dB (means by default CELL_PCH and CELL_URA to the CELL_DCH state if the Ec/Io of
only 10ms TTI allowed) the target cell not known

Content
 Introduction
 10 ms & 2 ms TTI

Layer 1 Re-transmission
- Like HSDPA HSUPA supports layer 1 re-transmission between UE and Node B

- First re-transmission after 40/16 ms for 10/2 ms TTI
- Settable limit of re-transmissions
- Up to 4/8 pending transmission processes possible for 10/2 ms TTI
- Same algorithms (chase combining or incremental redundancy) as for HSDPA
E-DCH
S-RNC Correctly received

packets
ACK / NACK on HICH
E-DCH re-transmission

Layer 1 Re-transmission – Huawei
HARQ algorithm EdchHarqInfo (per RNC only)

Chase combining, incremental redundancy
Setting independent from HSDPA
Maximum number of 2-4 re-transmissions hardcoded

in dependence on scheduling priority indicator

Layer 1 Re-transmission – Ericsson
HARQ algorithm eulHarqRv (per RNC only)

chase combining, incremental redundancy
Setting independent from HSDPA
harqTransmUlMax (per RNC only)

1..8, 4 / 8 retransmissions for 10 / 2 ms TTI

Layer 1 Re-transmission – Nokia
HARQRVConfiguration (per Node B)

HARQ algorithm
chase Combining, incremental Redundancy
Same parameter as for HSDPA
EDCHMaxNumberOfHARQReTx (per RNC only)

0..3, 3 retransmissions

H-ARQ and SHO
- UE combines individual ACK/NACK received from all active E-DCH cells

Re-transmission only, if all active Node B send back NACK
- In softer HO Node B performs maximum ratio combining of the individual E-DCH links
Just the same ACK/NACK value for both
Correctly received packets again delivered to RNC
- RNC performs soft HO frame selection and re-ordering
E-DCH
Node B
ACK .
E-DCH E-DCH
NACK
Node B
Iub R
N
C Iub

13 6255 NAK HSUPA Protocol Features

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

13 6255 NAK HSUPA Protocol Features

Transféré par

Droits d'auteur :

Formats disponibles

Contents

UMTS/HSPA Radio Resource Management & Parameter

00-1 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-3 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

TS 25.309 FDD Enhanced UL:

00-4 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

UL no channelization code limitation

HSUPA (similar to HSDPA) based on

00-6 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

new functions more

00-8 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

RNC MAC-es UE MAC-es and MAC-e

00-10 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-13 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Enhanced Dedicated Channel E-DCH

Dedicated Channel DCH

00-14 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-16 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

BCH PCH FACH DCH HS-DSCH Transport

P-CCPCH S-CCPCH DPDCH DPCCH HS-PDSCH Physical

CCCH DCCH DTCH Logical

RACH DCH E-DCH Transport

00-18 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Slot #0 Slot #1 Slot #2 Slot #i Slot #14

1 frame for 2 ms TTI

1 frame for 10 ms TTI

00-20 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

1 Slot = 2560 chip = 2/3 ms

Slot #0 Slot #1 Slot #2 Slot #i Slot #14

1 frame for E-DPCCH

00-22 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Maximum number DPCCH TS 25.213

Configuration #i DPDCH HS-DPCCH E-DPDCH E-DPCCH

00-24 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-26 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-28 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

SF128 128 128 128 128 128 128 128

Allocated CC Blocked CC E-RGCH and E-HICH

00-30 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

- Upgrade of E-RGCH / E-HICH resources by 1 code

Too much users Offer one code more

Threshold e.g.15 users

Few users again Remove additional code again

Nokia Ericsson Huawei

All settings per cell

- If two codes for E-RGCH / E-HICH strongly occupied

Too much users Too much users Offer further code

Nokia Ericsson Huawei

Maximum number of Hard coded numEhichErgchCodes Hard coded

Settings per cell

00-34 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-37 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

HSUPA packet scheduling performed by Node B

00-38 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Maximum HSUPA data rate

Settings per RNC only

00-40 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-41 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-42 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-43 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

Service Data (MAC-es PDUs) SI Optional padding

Periodicity for SI Power Offset for SI

00-45 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved

00-46 TA-TC 6255 NAK www.techcom.de Copyright © All rights reserved