Evolution Of HSPA

Evolution of HSPA
- a tutorial to Rel-7 HSPA+

sppe12083@gmail.com
RAN System Engineer

Contents
HSPA review
- What we have now
HSPA+ features:
- MIMO: 2x2 DTxAA
- High-Order-Modulation(HOM): 64QAM DL&16QAM UL
- CPC: HS-SCCH Less Operation, DTX/DRX
- Layer2 enhancement: Flexible PDU size
- Enhanced CELL_FACH: HS-DSCH reception in CELL_FACH
- F-DPCH enhancement
Special features on HSPA:
- VoIP over HSPA
- CS voice over HSPA
Advanced Receivers
- Type 1: receive diversity mode
- Type 2: LMMSE (Linear Minimum Mean Square Error) chip level Equalizer
- Type 3: LMMSE + receive diversity

3GPP TR 25.999(v710) “HSPA evolution”
3GPP TS 25.101 “ UE radio transmission and reception”
All rights reserved @ 2008

HSPA review: is it adequate as “packetized” radio interface?

HSDPA
RNC

Downlink max 14.4Mpbs
Associated DCH:
MAC-hs: - F-DPCH in DL
- Scheduling - DPCH in UL
- HARQ Tx
- Link
adaptation HS
HS -DSCH
HS -SC
-DP CH NodeB
NodeB CC
H
Non-serving cell
Serving cell UE in SHO
(for associated DCH)

HSUPA
MAC-e: RTWP budget
Scheduling
MAC-e: HARQ Rx
RNC
HARQ Rx
MAC-es: re-ordering nt Unused
E-R Gra
G ve
CH lati NAK t
:
Ov Re K/ n E-DCH users
er lo C H: A C G ra it ]
E-H ad RG ICH: olute ppyB
ICH ind E- Inter-cell interference
Uplink max 5.76Mpbs DP :A ic a E-H : Abs Ha
CC CK tor CH RI,
H: /NA G E- TF Intra-cell DCH users
pilo
E-D t K E-A RSN,
NodeB C H bit s CH
:[ bit s Thermal Noise
PC CH lot NodeB
: pi
UE in SHO E-D DPD CCH
E- DP

MAC-e multiplex
Update Serving Grant
E-TFC selection;
All rights reserved @ 2008 HARQ Tx

Effective high data rates beyond HSPA:
theoretical hints

requires better signal strength
rather than wider bandwidth!

⎛ S⎞
C = W log 2 ⎜1 + ⎟
⎝ N⎠

Bandwidth expansion more
beneficial than Eb/No rise!

To get effective high data rate in WCDMA systems, we may want:

Reasonable bandwidth Spatial multiplexing

Reduced cell size High-order modulation

Tx/Rx diversity Interference suppression


The super highway leading forward - MIMO
MIMO (Spatial multiplexing)
- Each antenna used for transmitting a different stream. No antenna diversity in that case per stream

MIMO in practice: spatial multiplexing + diversity
- cross path between antennas exists and Diversity still needed for reliable transmittion
- MIMO used both for spatial multiplexing (rate improvement) and diversity (SNR improvement)


MIMO - capacity in Rayleigh propagation
Transformation of MIMO channel into n SISO channels:

MIMO capacity: ⎡ ρ ⎤
C = log 2 ⎢det( I + ⋅ H ⋅ H H )⎥
- channel known to Rx, unknown to Tx:
⎣ nt ⎦
- Maximized when Tx number = Rx number via orthogonal channels :
⎡ ρ ⎤
C = log 2 ⎢det( I + ⋅ n ⋅ I n )⎥ ⇒ C = n ⋅ log 2 (1 + ρ )
⎣ n ⎦
Hints:
• Capacity does not depend on the nature of the channel matrix as it increases linearly with n for a fixed SNR.
• Every 3dB increase of SNR corresponds to an n bits/s/Hz increase in capacity


MIMO in Practice –2x2 manner

Ideally, we want:

In practice, we use SVD decomposition to ease “H inversion”.
H=U⋅D⋅VH Where U , V is unitaries of dimension nr × nr and nt × nt ; D is a non-negative diagonal matrix of nr × nt
r r r
Applying V at Tx side and U H at Rx side, we get U H ⋅ r = L = D ⋅ s + n ′
r
r
S γ
Pre-coding:
S1 r1
- to “orthogonalize” the
H Signal
parallel transmitted signals V UH processing
S2 r2


MIMO in UTRAN – DTxAA
• DTxAA – Double Transmission Antenna Array, 2x2 MIMO
– Possible independent coding/modulation for each data stream
– Successive interference cancellation at receiver
– Peak rate at 28.8Mbps

• Backward-compatible:
– Pilot design: one CPICH using different pilot pattern as in Tx diversity per
cell.
– Control channels: based on HS-SCCH / HS-DPCCH.
– Pre-coding based spatial multiplex:
• weight factors complying to the R99 Tx diversity alphabet.

• Deployment preference:
– micro- or indoor- cells where NLOS(non light-of-sight) rays or wonderful multi-
path exists


MIMO in UTRAN – leveraging existing HSDPA
channels - Two independent data streams (i,e.
two TBs within one TTI);

MAC-hs:
- Scheduling
- HARQ Tx
- Rate adaptation HS
-DS
CH
HS
-SC
HS CH
-D P
NodeB CC
H
Associated DCH:
- F-DPCH in DL
- DPCH in UL
UE

3GPP TS 25.999(v100)


DTxAA - Dual stream processing in baseband
baseband
processing

Interleaving modulation

HARQ rate
matching channelization codes
spreading SF=16
stream1 stream2
CRC attach.
Turbo coding χ1 χ2
TrBlk1 TrBlk2
scrambing
Pre-coding
MAC-hs ⎛ y1 ⎞ ⎛ ω1 ω3 ⎞ ⎛ x1 ⎞
HARQ entity ω2 ⎜ ⎟=⎜
⎜ y2 ⎟ ⎜ω ω ⎟ ∗ ⎜ x ⎟
⎟ ⎜ ⎟
ω1 ω4 ⎝ ⎠ ⎝ 2 4⎠ ⎝ 2⎠
ω3
MAC-d flows
through Iub
Priority handling Scheduling
y1 y2
to antenna 1 to antenna 2


MIMO in UTRAN – leveraging existing HSDPA
channels - Two independent data streams (i,e.
two TBs within one TTI);

MAC-hs:
Part 1 Part 2
- Scheduling
- HARQ Tx
- Link adaptation HS -Channelization codes - UE ID
-DS
CH - Modulation schemes - Transport block size
HS
-SC - Number of streams - Hybrid ARQ information
HS CH - Precoding matrix - Transport block size, stream 2
-D P
NodeB CC - Hybrid ARQ information, stream 2
H
Jointly encoded HARQ-
ACKs for dual-stream Associated DCH:
(Hamming distance = 6) - F-DPCH in DL
- DPCH in UL Tpyp A: contains CQIs for dual stream,
UE 8 bits(0 ~ 255).
Type B: in case of single stream,
5 bits(0 ~ 30)
2 ms Subframe
Tslot = 2560 chips 2xTslot = 5120 chips

HARQ-ACK CQI PCI A A A B A A A B …… A A B

One HS-DPCCH subframe (2 ms)
w3 = w1 = 1 / 2 w4 = − w2
Subframe #0 Subframe #i Subframe #4

One radio frame T = 10 ms

3GPP TS 25.999(v100)
3GPP TS 25.214 section 6A.2


MIMO in UTRAN --- Procedures
•UE identifies multiple transmitting
antennas according to different modulation
patterns of P-CPICH Part 1 Part 2

•UE reports composite CQI and PCI (Pre- •Channelization codes •UE ID
coding Control Indication) to NodeB •Modulation schemes •Transport block size
•Number of streams •HARQ information
•Pre-coding matrix •Transport block size, stream 2
•NodeB scheduler decides to transmit one
HS-SCCH •HARQ information, stream 2
or two transport blocks in one TTI.
HS-DS
C H stre
am2
•In case of two streams in transmission, HS-DS
CH stream
1
NodeB explicitly notify UE about the MIMO
Parameters (e.g number of streams, pre-
coding matrix, transport block size and
HS-DPCCH
HARQ information)
ACK/NACK Composite CQI/PCI

3GPP TS 25.214 Annex A
3GPP TS 25.214 section 9


MIMO in UTRAN - Performance
• Assuming 80% cell power to
HS channels, 20% to CCHs,
UEs with Rx diversity

• Ior/Ioc = 10dB: a break point
for higher throughput for
64QAM and dual-stream MIMO

• Single stream mode of MIMO
provides at least 20% gain
across whole cell!
Cell sustained throughput

MIMO
64QAM
Rel-6
50%
20%
10.8 Mbps 20%
6 Mbps
20%

Source: “3G HSDPA evolution: MIMO and 64QAM Performance in Macro Cellular Deployments”, Wireless Conference, 2008. EW 2008. 14th European
“High Speed Packet Access Evolution – Concept and Technologies”, J.Peisa,S, et.al, IEEE 2007.

Higher Order Modulation – 64QAM(Downlink)
• In case of good channel condition but propagation channels
between antennas are high correlative, e.g LOS path exists

• new HS-DSCH slot format introduced

• Peak data rate(64QAM) = 15 codes * 2880 bits/2ms = 21.6Mbps
• New UE category needed

3GPP TS 25.213(v740) Table 3c


64QAM – UE dependencies

3GPP TS 25.306 Table5.1a

Higher Order Modulation – 16QAM(uplink)
• On E-DCH with peak rate at 11.5Mbps
• More power efficient for rates higher than 4Mbps
• Mandatory for rates higher than 5.7Mbps
• Will demand Interference Cancellation(IC) receiver at NodeB
• Will demand uplink PDU size modification, e.g. 336 bits -> 656
bits
• New UE Catogory 7 needed

11.5Mbps


The protocol basis for high data rates
- Layer 2 Enhancements
RLC sliding window
• Motivation: 0 n UTRAN Mobile
– Rel-7 physical layer provides peak rate up to
28.8Mbps in DL (with MIMO) and 11.5Mbps in
UL( with 16QAM). SN=0,
P=0
– However, Rel-6 has semi-static RLC PDU size:
SN=1,
• with RLC window size 2048, RLC PDU size=40 bytes and P=0
RTT=100ms, the max data rate achievable is about
Round Trip Time
2048*40*8/0.1=6.5Mbps(13.1Mbps for an 80 byte PDU)
SN=n,
• Goal: P=1

– is to prevent RLC PDU format from being the SN= n
STATUS,
bottleneck of high data rate transmission.
• Flexible RLC PDU size:
– Packet-Centric RLC Concept as LTE RLC D/C Sequence Number Oct1
– Being able to map packets one-to-one to RLC Sequence Number P HE Oct2
PDUs Length Indicator E Oct3 (Optional) (1)

– Use Header Extension(HE) to indicate that last .
.
byte of SDU is the last byte of the PDU .

Length Indicator E
RLC SDU 1 RLC SDU 1 RLC SDU 2
Data

RLC hdr payload RLC hdr payload
Header Extention in use Length Indicator in use PAD or a piggybacked STATUS PDU
OctN

3GPP TS 25.322(v750) section 9.2.1.4

Layer 2 Enhancements – MAC
• MAC-ehs:
– MAC will segment RLC PDUs to adapt to momentary raido channels
• Segmentation indicator introduced in header
– Allow multiplex of data from multiple priority queues within one TTI
• Header supports indication of multiple logical channel identities
• C/T header is removed
– MAC-hs header is Octet-aligned
– New MAC-hs PDU format introduced:
LCH id 1 L1 TSN 1 SI 1 F1 LCH id k Lk TSN k SI k Fk
LCH Id – 4 bits: logical channel id
L – 11 bits: length indicator
TSN – 6 bits: One TSN per reordering queue
SI – 2bits: segmentation indicator
F – 1 bit: flag indication
MAC-ehs Header Reordering PDU Reordering PDU Padding

• MAC-ehs or MAC-hs is subject to configuration by network

3GPP TS 25.321 section 4.2.4.6

Enhanced L2– example of MAC data multiplexing
Logical Channel 1 Logical Channel 2 Logical Channel 3 Logical Channel 4

MAC-d Flow 1 MAC-d Flow 2 MAC-d Flow 3 MAC-d Flow 4

Queue 1 Queue 2

LCH Id1 L1 TSN SI F LCH Id1 L2 F LCH Id2 L3 F LCH Id4 L4 TSN SI F


Enhanced Layer 2 – a case of IP packet
Assuming an IP packet at size of 1500 bytes

Rel-5: with fixed RLC PDU size at 40 bytes Rel-7: flexible RLC PDU size
IP packet (1500 bytes) IP packet (1500 bytes)
2 bytes 2 bytes

L2 PDCP : PDCP hdr IP packet (1500 bytes) PDCP hdr IP packet (1500 bytes)

40 bytes 22 bytes

RLC Segmentation: #1 #2 #37 #38
padding

L2 RLC: RLC hdr RLC hdr RLC hdr L RLC hdr Payload (1502 bytes)

42 bytes 42 bytes 42 bytes 1504 bytes

L2 MAC-d: MAC-d PDU(1504 bytes)

42 bytes 42 bytes
21 bits 24 bits

MAC-ehs hdr Payload(1504 bytes)
L2 MAC-hs : MAC-hs hdr Payload(42*38=1596 bytes)

Appropriate TrBlk 12810 bits 12056 bits
for HS-DSCH:
12943 bits 12056 bits

In total 7% L2 overhead (922 bits) for In total 0.3% L2 overhead (56 bits) for
IP packet transmission! IP packet transmission!


Is it efficient on the highway for small cargos?

?

• Continuous Packet Connectivity (CPC)
– to keep UEs in CELL_DCH for a longer time & avoid frequent state transition
• Scope:
1. DTX: to reduce UL intra-cell interference and save UE battery life
2. DRX: battery savings by discontinuous reception of HS-SCCH and E-
AGCH/E-RGCH. Note: F-DPCH will be in use and SRB is over HSPA.
3. HS-SCCH less operation: optimized design for small packets or low bit
rates (especially for VoIP or streaming) with bounded over-the-air latency
– HS-SCCH signaling overhead is not insignificant comparing to VoIP packets on
HS-DSCH
– Principle is to permit HS-DSCH transmissions without any companying HS-SCCH,
i,e. using a set of pre-defined formats (on HS-DSCH) aided by UE blind decoding

3GPP TR 25.903 “Continuous connectivity for packet data users(Rel-7) “


CPC: HS-SCCH less operation
Initial transmission:
No HS-SCCHs!
•No HS-SCCHs
HS -D
SCH •QPSK and Xrv=0
•Pre-defined transport format and channelization
codes
ACK
•UE_ID indicated by CRC bits on HS-DSCH

HS-SCC
H type 2 2nd transmission:
HS -D
SCH
•HS-SCCH type 2 defined in this case
•QPSK and Xrv=3
ACK
/NAC
K

HS-SC 3rd transmission:
CH t y
pe 2 •HS-SCCH type 2 in use
HS -D
ACK
/NAC
K

3GPP TS 25.212(v770) section 4.6A


CPC: HS-SCCH less operation
HS-SCCH type 2 Initial transmission:
No HS-SCCHs!
•Channelization code set information (7 bits) •No HS-SCCHs
•Modulation scheme informationH 1 bit)
HS -D
SC ( •QPSK and Xrv=0 information (2 bits);
• Transport-block size
•Special information type( 6 bits = “ 111110”) • Pointer to the previous transmission (3 bits);
•Pre-defined transport format and channelization
• Second or third transmission (1 bit);
•Special information (7 bits) codes
• Reserved (1 bit);
•UE ID (16 bits) ACK
•UE_ID indicated by CRC bits on HS-DSCH

HS-SCC
H type 2 2nd transmission:
HS -D
SCH
•HS-SCCH type 2 defined in this case
•QPSK and Xrv=3
ACK
/NAC
K

HS-SC 3rd transmission:
CH t y
pe 2 •HS-SCCH type 2 in use
HS -D
ACK
/NAC
K

3GPP TS 25.212(v770) section 4.6A


CPC - DTX
• Goal:
– to reduce the uplink control channel overhead for DPCCH.
• Principle:
– use occasional slots of DPCCH activity (i,e. uplink DPCCH gating) to
maintain uplink synchronization and reasonable power control, in case of no
data transmission.
– Controlled by either RRC signaling or physical layer L1 command
– No impact on ACK/NACK transmission on HS-DPCCH; CQI report follows
DTX pattern unless recent HS-DSCH reception occurred.

depends on E- applied when no
DCH inactivity uplink data
transmission

3GPP TS 25.214(v770) section 6C

CPC - DRX
• Goal:
– to reduce UE battery power consumption in active state
• Principle:
– Following certain period of HS-DSCH inactivity, UE is restricted to
monitor HS-SCCH,E-AGCH and E-RGCH in specified subframes.
– Always used together with DTX
– Reception of E-HICH and F-DPCH is not affected by DRX operation.
– Controlled by either RRC signaling or physical layer L1 command.

DTX_cycle and DRX_cycle
should match each other!


CPC: DTX/DRX activation
• Enabling delay:
– a configurable time to allow synchronization and power control loops to
stabilize when to activate DTX/DRX by RRC signalings
• HS-SCCH Order (L1 command):
– Reserved HS-SCCH bit patterns to switch on-off DTX/DRX by NodeB

• New DPCCH slot format:
– Contains only Pilot bits and TPC bits, for reduction of UL DPCCH Tx power.

3GPP TS 25.212(v770) section 6C.4


CPC: Performance
PB3 VoIP CAPACITY

0.30

Original HS-SCCH-less: 2 TB sizes

0.25 Original HS-SCCH-less: 4 TB sizes
HS-SCCH Less operation
Reduced complexity HS-SCCH-less: 4 TB sizes
provides near 17% VoIP capacity
Rel 5 HSDPA: Legacy
gain at 5% system outage rate
OUTAGE PROBABILITY

0.20

0.15

0.10

0.05 DTX contributes to
VoIP capacity gain
0.00
40 50 60 70 80 90 100
significantly!
VoIP USERS

Source: 3GPP TR 25.903 “Continuous connectivity for packet data users(Rel-7) “


What is use of a highway if it takes too long
to reach it?
• Enhanced CELL_FACH operation:
– Reduce state transition latency from Non CELL_DCH states to
CELL_DCH states
– Faster data transmission for bursty, small packet applications, e.g
Presense
– Lower UE power consumption in CELL_FACH state by
discontinuous reception
• HS-DSCH reception in CELL_FACH
– Not intended to keep an active UE in CELL_FACH for a long time,
but to prepare for quick moving to CELL_DCH while minimizing the
interruption for data transmission during state transitions.
• HS-DSCH reception in CELL_PCH/URA_PCH
– No plan to support this!

3GPP TS 25.308(v790) section 14


Enhanced CELL_FACH Operation
• HS-DSCH reception in CELL_FACH
– Enabled by including “HS-DSCH common
system information “ in system information MAC-ehs and
broadcast SIB 5/5 bis flexible PDU
size in use!
– Overwhelms S-CCPCH reception, CCH power Common No DCHs for
saved for HSPA channels H-RNTI receiving data!
t
cas
– UE, w.r.t Common H-RNTI, monitors HS-SCCH r oad
nb
for HS-DSCH reception atio PCH
rm C
– BCCH mapped to HS-DSCH: “System info S-C CC
H
st em S-S
Information Change” message can now be Sy H H
SC
conveyed in HS-DSCH for specific H-RNTIs. H S-D NodeB
– UE category 1~4 and 11 do not support this CH
RA
• Interacting with existing HSDPA Rel-7 UE
rules:
– No dedicated uplink channel, e.g HS-DPCCH
– HARQ replaced by quick blind repetition on MAC With MAC-ehs in use, received data
PDUs format in CELL_FACH will
– Link adaptation based on measurement reports be same as that of CELL_DCH,
via RACH to RNC which forwards it to NodeB to thereby no interruptions between
determine MCS and transmit power state transitions.


HSPA+: typical use in a web-browsing applications

High throughput in Very quick

Current Drain
DNLK direction transition to
transmit again
100-150ms (*) 10-15s (*)
CELL_DCH CELL_FACH CELL_PCH CELL_DCH

VoIP over HSPA
• What :
- VoIP application in IMS domain, already standardized in 3GPP R5.
• How :
- Rel-5 standard provides “PS conversational RAB at 42.8kbps” without head compression
- With RoHC(headers compressed to 7 bytes), PS conversational RAB at 15.6 kbps can
convey VoIP packets reliably.
- SRB over HSPA needed, thus F-DPCH required
- enhanced NodeB scheduler for VoIP service
- HS-SCCH less operation is preferred
• Benefit :
- reduced cost-per-bit
- with CPC, RAN can support
doubled user capacity per cell
against R99 voice users.
DCH DCH DCH HS-DSCH


VoIP over HSPA
• What :
- VoIP application in IMS domain, already standardized in 3GPP R5.
• How :
- Rel-5 standard provides “PS conversational RAB at 42.8kbps” without head compression
- With RoHC(headers compressed to 7 bytes), PS conversational RAB at 15.6 kbps can
convey VoIP packets reliably.
- SRB over HSPA needed, thus F-DPCH required
- enhanced NodeB scheduler for VoIP service
- HS-SCCH less operation is preferred
• Benefit :
- reduced cost-per-bit
- with CPC, RAN can support
doubled user capacity per cell
against R99 voice users

Radio Bearer
established on
HS-DSCH/E-
DCH


CS voice over HSPA
Motivation:
- an early implementation of R8 feature in R7
- can avoid surplus SRNS relocation signaling in collapsed
UTRAN architecture
Benefit:
- no needs of IMS core network for voice packet over HSPA
- Capacity gain:
• 23% capacity gain( with 2ms HSUPA TTI) over R99
voice user numbers per cell;
• with CPC, will have 48% capacity gains over R99.
- better talk time with CPC
Dependency:
- Demand Rel-7 UE with enabled “UE radio capability
parameters”

WCDMA L1 MAC-d RLC IuUP CS Telephony
DCH Iub FP
Processing TM Proc. IuCS Core Network

MAC-e MAC-es
E-DCH
scheduler Iub FP
HSPA L1 MAC-d RLC PDCP
UE Processing UM (cs
HS-DSCH MAC-hs (TN)
(HARQ proc)
scheduler (SN) counter)

NodeB RNC


HSPA evolution: benefits

Doubled Data Capacity over HSPA
2X higher peak rates

Up to 3X Voice Capacity over R99
H Voice over HSPA leverages HSPA features
S
Similar Performance as LTE
P With same Antenna numbers and bandwidth
A
Improved User Experience
+ Better always-on experience, lower latency, faster call setup

Backward Compatible and Natural Evolution
Incremental and cost-effective upgrade

3GPP TS 25.913(v800) “Requirements for Evolved UTRA (E-UTRA) and Evolved UTRAN (E-UTRAN)”


Q&A


Backup: conventional HSDPA Layer 1
processing
Scheduling
Priority Handling (per cell)

HARQ entity
(per user) MAC-hs
Virtual IR Second RM stage
buffer
CRC attachment First RM stage Nt,sys
Systematic Nsys RM_S
bits
bit scrambling
Rate Nt,p1
Parity 1
Np1
1/3 RM_P1_1 RM_P1_2
Turbo coding Turbo
coding Parity 2 Np2 Nt,p2
RM_P2_1 RM_P2_2

HARQ rate matching

r s
Physical channel
segmentation

Interleaving

Constellation
rearrangement


Backup: pre- and postamble detection

ACK: 1111111111
NACK: 0000000000
PREAMBLE (”PRE”): 0010010010
POSTAMBLE (”POST”): 0100100100


Backup: F-DPCH channel format
Any CPICH

10 ms 10 ms
P-CCPCH Radio framewith (SFN modulo 2) = 0 Radio framewith (SFN modulo 2) = 1

UE 1 DPCH τ
DPCH1

UE 2 DPCH τ
DPCH2 TPC bits for 1 slot

τ
DPCH3
UE 3 DPCH

Shared PC
channel

HS-PDSCH Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe
Subframes #0 #1 #2 #3 #4 #5 #6 #7
Ttx_diff 0 2 6 9

512 chips

TPC
(Tx OFF) (Tx OFF)
NTPC bits

Tslot = 2560 chips

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

1 radio frame: Tf = 10 ms


Review of Tx diversity: Alamouti code
• Assume channel constant across two symbols


Backup: coding for HS-DPCCH: CQI/PCI
• Composite PCI and CQI: concatenated and coded into
20 bits using a block code.
• PCI(2 bits): indicates the pre-coding matrices for the
UE.
• CQI
– Type A(8 bits): recommend number of streams and CQIs
Type A Type B
– Type B(5 bits): for single data stream transmission CQI
PCI OR CQI

Binary mapping Binary mapping

pci 0,pci 1 cqi 0,cqi 1, …cqi 7 cqi 0,cqi 1, …cqi4

concatenation

3GPP TS 25.214 section 6A.2 a0,a1...a9 OR a0,a1...a6


Backup: coding for HS-DPCCH: HARQ-ACK

Rel - 7

Rel - 5

3GPP TS 25.212 section 4.7.3


Backup: HS-SCCH Control information
Part 1
Part 2

3GPP TS 25.212(v770) section 4.6

Backup: parameters on DTX/DRX


Backup: MAC-ehs segmentation
Queue 1 Queue 2

RLC PDU1 LCH 0
RLC PDU 2
RLC PDU3

RLC PDU1 LCH 1
RLC PDU2

RLC PDU1 LCH 2

N SI
TS
LCH Id0 L1 0 00 0 LCH Id0 L1 0 LCH Id0 L2 1

N SI
TS
LCH Id1 L1 1 10 0 LCH Id1 L2 1

N SI N SI
TS TS
LCH Id1 L1 2 01 0 LCH Id2 L2 0 LCH Id4 L1 0 10 0 LCH Id4 L1 0 LCH Id4 L2 1

Complete PDU
Segmented PDU


Backup: HSPA+ usage in VoIP session

Constant end- Network
Current Drain Handover
to-end delay capacity
P P 160ms
P P P P P P P P

Evolution Of HSPA

Recommended

Recommended

More Related Content

What's hot

What's hot (17)

Viewers also liked

Viewers also liked (20)

Recently uploaded

Recently uploaded (20)

Evolution Of HSPA