HSDPA Partner Workshop v1

HSDPA Workshop
Nokia RNWP CHT Project 2006 Sept.
NOKIA
HSDPA General Workshop / MHL /2006 Sept
Company Confidential
HSDPA General principle

Channel quality information Error correction Ack/Nack L1 Feedback Data Shared DL data channel Fast link adaptation, scheduling and L-1 error correction done in BTS 1-5 codes in RAN05 (max.15 codes RAN06) Data QPSK or 16QAM modulation User may be time and/or code multiplexed.
Terminal 1 (UE)
L1 Feedback
Terminal 2
2 NOKIA HSDPA General Workshop / MHL /2006 Sept
Fast Link Adaptation in HSDPA

16 C/I received by UE 14 12 10 8 6 4 2 0 -2
0 20
Instantaneous EsNo [dB]
C/I varies with fading
40
16QAM3/4 16QAM2/4 QPSK3/4 QPSK2/4 QPSK1/4

3 NOKIA
Link adaptation mode
Time [number of TTIs]
60
80
100
120
140
160
BTS adjusts link adaptation mode with a few ms delay based on channel quality reports from the UE
Link adaptation: Modulation

Q 1011 10 00 1010 I 1110 11 01 1111 1101 0101 0111 1100 0100 0110 1000 0000 0010 I 1001 Q 0001 0011
QPSK 2 bits / symbol = 480 kbit/s/HS-PDSCH = max. 7.2 Mbit/s
16QAM 4 bits / symbol = 960 kbit/s/HS-PDSCH = max. 14.4 Mbit/s
NOKIA
HSDPA Peak Bit Rates

Coding Codingrate rate Coding Codingrate rate 1/4 1/4 QPSK QPSK 2/4 2/4 3/4 3/4 2/4 2/4 16QAM 16QAM 3/4 3/4 4/4 4/4 5 5codes codes 600 600kbps kbps 1.2 1.2Mbps Mbps 1.8 1.8Mbps Mbps 2.4 2.4Mbps Mbps 3.6 3.6Mbps Mbps 4.8 4.8Mbps Mbps 10 10codes codes 1.2 1.2Mbps Mbps 2.4 2.4Mbps Mbps 3.6 3.6Mbps Mbps 4.8 4.8Mbps Mbps 7.2 7.2Mbps Mbps 9.6 9.6Mbps Mbps 15 15codes codes 1.8 1.8Mbps Mbps 3.6 3.6Mbps Mbps 5.4 5.4Mbps Mbps 7.2 7.2Mbps Mbps 10.7 10.7Mbps Mbps 14.4 14.4Mbps Mbps
RAN05 RAN05 CD1

User throughput
HSDPA uses downlink shared channel. Downlink data is scheduled in 2 ms TTIs to users. User throughput depends upon the number of active HSDPA users in the cell/BTS.
Three HSDPA UEs receiving data

3rd TTI
2nd TTI 1st TTI
NOKIA
1-THROUGHPUT
1800000 1600000 1400000 1200000 Throughput 1000000 800000 600000 400000 200000 0 -3
Throughput vs. EcNo
Stationary Stationary user user Option Option datacard datacard with with Nemo Nemo RLC RLC throughput throughput Initial Initial EcNo EcNo on on the the x-axis x-axis
2W 4W 6W 8W 10 W
PtxMaxHSDPA
-6
-9 EcNo
-12
-15
Ec/Io: with and without HSDPA (R99 + R5 HSDPA)

Ec/Io vs Initial Ec/Io
-4.0 -5.0 -6.0 -7.0
Ec/Io (with HSDPA)
HSDPA_2W HSDPA_4W HSDPA_6W HSDPA_8W HSDPA_10W
-8.0 -9.0 -10.0 -11.0 -12.0 -13.0 -14.0 -15.0 -16.0 -3 -6 -9

Initial Ec/Io (w ithout HSDPA)
-12
-15
General General Obersvation: Obersvation: E.g. E.g. Initial Initial CPICH CPICH Ec/Io Ec/Io is is -3dB. -3dB. However, However, when HSDPA user is active, immediate when HSDPA user is active, immediate observation observation of of Ec/Io Ec/Io degradation. degradation. Amount of degradation Amount of degradation depends depends on on the the PtxMaxHSDPA parameter set. PtxMaxHSDPA parameter set. 8 NOKIA HSDPA General Workshop / MHL /2006 Sept
Mobile UE Under 1 Cell - Throughput

Novatel Data card
25
CQ I vs RSCP
20
Thr ought put vs RSCP
2000 1800 1600 1400 Thr oughput ( kbps) 1200 1000

CQ I
15
10
EcNo vs RSCP
800 600 400 200 0 -40
0 -40
0
-50
-60
-70
-80 RSCP ( dBm )
-90
-100
-110
-120
-5
-50
-60
-70
Ec/No
-80 RSCP ( dBm )
-90
-100
-110
-120
-10
-15
NOKIA
-40 -50 Company Confidential
-20
-60
-70
-80 RSCP ( dBm )
-90
-100
-110
-120
Application throughput 1800000 1600000 1400000 1200000 1000000 800000 600000 400000 200000 0 0 50 100 150 200 250 300 350 400 450 500140000 550
120000 100000 # messages
bps
CQI distribution
s CPICH Ec/No
0.0 -5.0 0 dB -10.0 -15.0 -20.0 -25.0 s

CQI 30.0 25.0 20.0 15.0 10.0 5.0 0.0 0 50 100 150 200 250 300 s
CPICH RSCP 0.0 -20.0 0 -40.0 dBm -60.0 -80.0 -100.0 -120.0 s 50 100 150 200 250 300 350 400 450 500
50
100
150
200
250
300
350
400
450
500
80000 60000 40000 20000 0
550
17
19
21
23
25
27
11
13
350
400
450
500
550
Avg. Throughput ~950kbps
550
10
NOKIA
15
CQI value
29
Effect of HSDPA Traffic on R'99 DCHs Ec/No Quality FTP download Example (good radio Conditions)
Pilot Ec/No
Without HSDPA User => Ec/No = 4dB With HSDPA User => Ec/No degraded = -8dB
HSDPA Throughput
11
NOKIA
Effect of HSDPA Traffic on R'99 DCHs Ec/No Quality FTP download Example (good radio Conditions)
Ec/Io decreases of 3 dB during the transfer. This difference is due to the PtxMaxHSDPA power which is allocated only when there is at least one HSDPA user
Test 2 run 2
1600000 1400000 1200000 -3 Application TP -4 -5 -6 -7 400000 -8 200000 0 0 20 40 60 80 100 -9 -10 120 0 -1 -2
800000 600000
Relative Time
Application Throughput
Ec/No
12
NOKIA
Ec/Io (dB)
1000000
Multiple Users Test: 3 Datacards in Static

Datacards: 2 Novatel and 1 Sierra Service: 3 FTP users
Impact of 3 Users on Throughput
1600000 A p p licatio n T h ro u g h p u t (b p s) 1400000 1200000 1000000 800000 600000 400000 200000 0 Time (s)
1 user
2 users
3 users
2 users
1 user
13
NOKIA
Release99 vs HSDPA Retransmissions

Rel99 DCH/DSCH Rel5 HS-DSCH RNC
Packet
Retransmission RLC ACK/NACK
RLC Retransmission
BTS
Packet RLC ACK/NACK L1 ACK/NACK
L1Retransmission
Terminal
14
NOKIA
New Node B functionality for HSDPA

RNC Node B Terminals
ARQ & Coding ACK/NACK & Feedback Decoding
Packets Flow Control
Scheduler & Buffer
New Node B functions: Scheduler: Terminal scheduling, Coding & Modulation selection (16QAM as new modulation) ARQ Retransmissions Handling Uplink Feedback Decoding Flow Control towards SRNC
New terminal functionality for HSDPA

RNC Node B Terminal
ARQ Decoding Soft Buffer & Combining ACK/NACK & Feedback Generation
Packets Flow Control
New terminal functions: 16 QAM demodulation ARQ Retransmissions Handling Soft buffer & combining Fast Uplink Feedback Generation & encoding First terminals are data cards without voice capability
HSDPA Protocol Architecture

New MAC entity, MAC-hs added to the Node B Layers above, such as RLC, unchanged.
UE NAS RLC MAC-d MAC-hs WCDMA L1
Node B
SRNC RLC MAC-d FRAME PROTOCOL TRANSPORT
MAC-hs WCDMA L1
FRAME PROTOCOL TRANSPORT Iub/Iur
Iu
Uu
HSDPA user plane
17
NOKIA
PDUs of Different Protocol Layers

higher layer
higher layer data packet
RNC
RLC
header
part of RLC SDU
header
part of RLC SDU
MAC-d
header
RLC PDU (= MAC-d SDU)
header
RLC PDU (= MAC-d SDU)
Iub
Node-B
MAC-hs
header
MAC-d PDU (= MAC-hs SDU)
MAC-d PDU (= MAC-hs SDU)
pad
physical layer
MAC-hs PDU (= transport block = TB) HS-SCCH
18
NOKIA
MAC-d and MAC-hs

Mac-d remains in RNC in the same way as for Release 99 Mac-hs is located in the Node B to allow rapid re-transmission of NRT data Mac-d is responsible for:

mapping between logical channels and transport channels; selection of appropriate Transport Format priority handling identification of UEs on common transport channels multiplexing/demultiplexing of upper layer PDUs traffic volume measurement; transport Channel type switching; ciphering for transparent mode RLC Packet scheduling Link adaptation L1 error correction and retransmissions (H-ARQ) Flow control between RNC and BTS
RLC MAC-d
MAC-d flow
Mac-hs is responsible for:

RLC MAC-d HSDSCH FP TNL Iub RNC
MAC-hs HS-DSCH MAC-hs PHY UE

HS-PDSCH
HSDSCH FP TNL
PHY BTS
Uu
19
NOKIA
MAC-hs
MAC-hs functions in BTS Iub Flow Control Data Buffering Packet Scheduling Link Adaptation Hybrid ARQ MAC-hs Protocol Services Data transfer on HS-DSCH In-order delivery within priority queue For each subframe = 3 slots = 2 ms Interpret incoming Ack/Nack and CQI information. Perform Packet Scheduling, i.e. choose one priority queue for transmission. Determine if retransmission is needed. New transmission. Perform Link Adaptation. Build MAC-hs PDU. Retransmission No need for LA. Use same MAC-hs PDU. Perform Power Control for HS-SCCH.
20
NOKIA
HSDPA Protocol Model

MAC-d flow UE-specific 1:1 with FP entity 1:1 with AAL2 connection Up to 8 MAC-d flows per UE RAN05: 1 MAC-d flow per UE HS-DSCH Transport channel Shared by the UEs in the cell Controlled by MAC-hs Between BTS and UE(s) HS-PDSCH 0 to 15 per cell RAN05: max. 5 per HSDPA cell HS-SCCH, HS-DPCCH In the figure, the SRNC and DRNC are co-incident. This is always the case in RAN05 which has no Iur for HSDPA.
RLC MAC-d
DCH
RLC MAC-d DCH FP TNL DCH FP TNL Iub RNC
PHY
DPCH
PHY
UE
Uu
BTS
RLC MAC-d MAC-hs PHY UE

HS-DSCH MAC-d flow
RLC MAC-d HS-DSCH FP TNL Iub RNC
MAC-hs PHY
HS-DSCH FP TNL
HS-PDSCH
Uu
BTS
HSDPA Protocol Model

Up to 8 MAC-d flows can be mapped to one UE (3GPP) In RAN05 only one MAC-d flow per UE is possible
Physical chs
HS-PDSCH HS-SCCH HS-DPCCH
Transport chs
Logical chs
MAC-d flow #1 MAC-d flow #2
HSDPA
HS-DSCH
UE
MAC-d flow #8
DPDCH DPCCH
DCH
DTCH #1 DTCH #2
DCH
22
NOKIA
Physical Channels for One HSDPA UE

DL CHANNELS
BTS
Associated DPCH Associated DPCH 1-15 x HS-PDSCH
HS-PDSCH: High-Speed Physical Downlink Shared Channel HS-SCCH: High-Speed Shared Control Channel
1-4 x HS-SCCH
HS-DPCCH
Rel99 DCH
Associated DPCH, Dedicated Physical Channel. UL CHANNELS Associated DPCH, Dedicated Physical Channel HS-DPCCH: High-Speed Dedicated Physical Control Channel
UE
23
NOKIA
HSDPA DL physical channels

HS-PDSCH: High-Speed Physical Downlink Shared Channel

Transfers actual HSDPA data of HS-DSCH transport channel. 1-15 code channels. QPSK or 16QAM modulation. Divided into 2ms TTIs Fixed SF16 Doesnt have power control
HS-SCCH: High-Speed Shared Control Channel Includes information to tell the UE how to decode the next HS-PDSCH frame Fixed SF128 Nokia implementation has power control Shares downlink power with the HSPDSCH More than one HS-SCCH required when code multiplexing is used
Field Channelisation code set information Modulation scheme information Transport block size information Hybrid ARQ process information Redundancy and constellation version New data indicator UE identity
Number of uncoded bits 7 bits 1 bit 6 bits 3 bits 3 bits 1 bit 16 bits
24
NOKIA
HSDPA DL physical channels

Associated DPCH, Dedicated Physical Channel Transfers signalling (Signalling Radio Bearer (SRB)) information e.g. RRC measurement control messages Power control commands for associated UL DCH DPCH needed for each HSDPA UE. No SHO support in RAN05 (coming in RAN05.1)
25
NOKIA
HSDPA UL physical channels

HS-DPCCH: High-Speed Dedicated Physical Control Channel MAC-hs Ack/Nack information (send when data received). Channel Quality Information, CQI reports (send in every 4ms) SF 256
Associated DPCH, Dedicated Physical Channel DPCH needed for each HSDPA UE. Transfers signalling Also transfers uplink data 64, 128, 384kbps, e.g. TCP acks No SHO support in RAN05 (coming in RAN05.1)
26
NOKIA
Physical channel structure

1 radio frame (15 slots, total 10 ms) 2 ms 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
enables time and code multiplexing. presents time multiplexing

User data on HS-DSCH
3GPP
Subframe #1
UE 1 UE 1 UE 1 UE 1 UE 1 UE 1 UE 1 UE 1
Subframe #2
UE 2 UE 2 UE 2 UE 2 UE 2 UE 2
Subframe #3
UE 3 UE 3 UE 3
Subframe #4
UE 1 UE 1 UE 1
Subframe #5
HS-PDSCH #1 HS-PDSCH #2
Picture
2 slots
UE 1
HS-PDSCH #3
UE 1
UE 1
UE 1
UE 2
UE 2
UE 2
UE 3
UE 3
UE 3
UE 1
HS-SCCH
3 slots UE #3 L1 feedback HS-DPCCH
UE #2 UE #1
L1 feedback
HS-DPCCH
L1 feedback
HS-DPCCH
Code Multiplexing (not in RAN05/5.1)

With Code Multiplexing, multiple UEs can be scheduled during one TTI. Multiple HS-SCCH channels One for each simultaneously receiving UE. HS-SCCH power overhead. HS-PDSCH codes divided for different transport blocks. Multiple simultaneous transport blocks to one UE not possible. Important when cell supports more codes than UEs do. For example 10 codes per cell, UE category 6. How to divide HS-PDSCH power between simultaneous UEs? Packet Scheduling algorithm?
HS-SCCH HS-SCCH HS-PDSCH HS-PDSCH HS-PDSCH HS-PDSCH HS-PDSCH HS-PDSCH HS-PDSCH HS-PDSCH HS-PDSCH HS-PDSCH
cat 8
cat 6
cat 6
cat 6
cat 6
28
NOKIA
Downlink Code Allocation

HSDPA with 5 codes allocated at cell MAC-hs start-up when HSDPA is enabled Code allocation is dynamic in future releases when more than 5 codes are allocated
SF = 1 SF = 2 SF = 4 SF = 8 SF = 16 SF = 32 SF = 64 SF = 128 SF = 256
Codes for 5 HS-PDSCH's Code for one HS-SCCH Codes for the cell common channels
166 codes @ SF=256 available for the associated DCHs and non-HSDPA uses
29
NOKIA
DL DCH Spreading Factor (Nemo)
DCH 384kbps DCH 128kbps DCH 64kbps SRB 13.6kbps (During Call Setup) Associated DL DPCH (for SRB, 3.4bkps)
30
NOKIA
Channel Allocation in WSPC

Wideband Signal Processing unit (WSPC) is a flexible software based card handling both uplink and downlink channels WSPC can handle common channels for 3 carriers and user data according to base band processing capacity tables HSDPA block is able to handle up to 3 cells (time multiplexed) and is allocated to one WSPC card
1. WSPC 2. WSPC
HSDPA BLOCK (5codes) Reserved by RRM = 32CE
Nth WSPC
Carrier Carrier1 1 Carrier Carrier1 1 Carrier Carrier1 1
Common channels
Common chs remaining capacity 48 CE
remaining capacity 32 CE
capacity 64 CE
Traffic channels
Same type WSPC handles common and HSDPA channels

Customer Company Confidential
= R5 HSDPA = R99 DCH
31
NOKIA
PtxtargetHSDPA AND PtxoffsetHSDPA
STRATEGY: 1) The ratio between PC headroom and Variable Power shall remain the same after the introduction of HSDPA because HSDPA does not require any power control headroom 2) When HSDPA power is allocated DCH Power increases to to keep BLER targets, so in order to avoid HSDPA power to be allocated and soon released DCH power increase << PtxoffsetHSDPA
Power Allocation (CHT)

20W 15.8W Ptxoffset PtxTarget 43 dBm 42 dBm 8W 20W 43dBm
PtxmaxHSDPA
PtxoffsetHSDPA PtxTargetHSDPA 40.8dBm 39.8dBm
12W
DCH + Variable part of CCHs
9.5W
DCH + Variable part of CCHs

2W
CPICH
33 dBm
2W
CPICH
33dBm
HSDPAPriority =1
33
NOKIA
HW Requirements (CHT)
Requirement Carrier Node B HSDPA Code allocation Min Required CE Min Required WPA Min Required E1 2 Carrier (10762, 10787) Supreme/Optima/Metro50 5 128 40W/Sec 2E1 RNC Step5: 4 Initial DMCU Allocation RNC Step4: 3 RNC Step3: 2 Pwr allocation for HSDPA 8W 2 WSPC => 2E1 3 WSPC => 3E1
1 DMCU=4 DMPG=4*6 HSDPA sites=4*16 HSDPA users
Remark 10762: DCH 10787: HSDPA+DCH(Rel5UE) Max HSDPA allocation: 3 Cell/site

Sf16(11-15) 32CEs reserved for CCH 32CEs reserved for HSDPA
34
NOKIA
Deployment Strategy
-Co-existence of R'99 and R5 HSDPA = R5 HSDPA + R5 DCH = R'99 DCH
F1 F1(R99+R5) (R99+R5) Case 1: Carrier shared between R5 HSDPA and R'99 Operator definable resource sharing between R5 HSDPA and R'99. Most likely initial network setup:

cost efficiency Simple parameter planning (traffic handling) Capacity (additional load from HSDPA) Impact existing R'99 performance (Ec/No quality degradation)
35
NOKIA
Deployment Strategy
- Dedicated Carrier for HSDPA = R5 HSDPA + R5 DCH = R'99 DCH
Case2: Dedicated R5 (HSDPA+DCH) carrier R5 UE (HSDPA + DCH) directed to R5 HSDPA carrier Recommended for hotspot, indoor, major corporate customer office etc.
F2 F2R5 R5 F1 F1R99 R99
Minimum Impact to existing system (capacity and performance) than case 1. Guarantee certain level of HSDPA performance More complex parameter planning (DRRC, UE capability, IFHO) Control to have only R5 (HSDPA + DCH) on f2 (trigger point for inter-Frequency HO for realtime etc.)
Used in CHT Project
36
NOKIA
Directed RRC Connection Setup for HSDPA

DirectedRRCEnabled The parameter enables/disables the use of directed RRC connection setup or directed RRC connection setup for HSDPA layer in the cell.
0: Directed RRC connection setup is not enabled in the cell 1: Directed RRC connection setup is enabled in the cell 2: Directed RRC connection setup for HSDPA layer is enabled in the cell
37
NOKIA
ADJI (f2 -> f1) Planning - Include own sites f1 cells. - Plan up to 2~3 tier sites depending on f2s propagation.
Mobility Handling Scheme

UMTS F2 (HSDPA Enabled)
IFCR (f2->f1) -Oneway adji (same as IFHO)
HSDPA DRRC
IFHO (f2->f1) R99UE IFHO (f1->f2) RT/NRT: disabled
No IFCR (f1 -> f2) - No adji (f1->f2)
R5UE
-RT: RSCP (-95dBm) & Ec/No (-12dB) -NRT: RSCP (-95dBm) -Oneway adji
UMTS F1 (DCH)
No ISCR No ADJG (f2->2G) ISCR F1 -> 2G 2G -> 3G ISHO (RT) F1 -> 2G : Ec/No, RSCP Ec/No: -12 dB RSCP: -105 dBm CCO (NRT) F1 -> 2G : RSCP RSCP: -115 ISHO (f2->2G) -RT/NRT: Disabled
2G
Concern: If a HSDPA UE performs IFHO from f2 to f1, the UE cannot get HSDPA allocation again in f1 during the call. It has to disconnect and re-establish the RRC setup for PS call (using HSDPA DRRC) in order to get HSDPA allocation again. This is due to current HSDPA resumption timer works only within the same layer with HSDPA enabled cells.
Mobility Handling Scheme

Assumption F1 (HSDPA disabled), F2( HSDPA enabled) HSDPA DRRC This brings Rel5 UE to F2, and Rel99 UE to F1 during RRC Con Setup. ISHO / ISCR ISHO is only allowed from F1 to 2G. RT: RSCP (-105dBm) & Ec/No (-12dB) NRT: RSCP (-115dBm) ISHO from F2 not allowed. It will first move down to F1, since F1 has continuous coverage. ISCR is also allowed from F1 to 2G, since F2 does not have ADJG to 2G. IFHO / IFCR IFHO is only allowed from F2 to F1 RT: RSCP (-95dBm) & Ec/No (-12dB) NRT: RSCP (-95dBm) IFCR is also allowed from F2 to F1 only, since no ADJI from F1 to F2 defined. Neighbor Planning ADJS: F1~F1, F2~F2 ADJI: F2F1 ADJG: F1 2G
39
NOKIA
HSDPA mobility in RAS05 CD1 (1)

- HSDPA Serving Cell Change
HSDPA Serving Cell Change

HSDPA (serving cell) -> MR(e1a, serving cell) -> Cell_FACH (Target Cell) -> HSDPA (Target Cell)
Cell A Service in HSDPA

(Serving Cell)
Switching to Cell_FACH (Target Cell) within the SHO area
UE on HS-DSCH
(Target Cell)
Cell B
HS-DSCH coverage
Throughput
HSDPA
128kbps or 384kbps according to parameter settings 64kbps
HS-DSCH coverage
DCH
40
NOKIA
HSDPA mobility in RAS05 CD1 (1)

- HSDPA Resumption Timer
HSDPA resumption timer switches the user from DCH to HS-DSCH, when UE enters HSDPA area
The conditions preventing HSDPA allocation in HSPDA coverage area to HSDPA capable UE are: More than one serving cell (Soft Handover) Multi-RAB combination (not supported) Lack of HSDPA capacity in the cell
Cell A Service NRT DCH R99 coverage

Throughput
HSDPA
128kbps or 384kbps according to parameter settings 64kbps (initial bitrate)
Switching to HS-DSCH when not in SHO area
Cell B
HS-DSCH coverage Download complete
DCH
41
NOKIA
Resumption timer
RNP parameter in RNC. Timer started when HSDPA capable UE having DCH NRT enters into HSDPA capable cell and Active set size=1. Switching to HS-DSCH is tried after the timer expires, if the Active set size is still 1. Switching happens via DCH0/0. Normal HSDPA selection procedure is applied after a capacity request, when DCH0/0 is allocated.
42
NOKIA
Resumption timer
- DCH to HS-DSCH switch
1500000 1000000 bps 500000 0 0 10 20 s 30 40 50
Resumption timer started when Active set size =1. Resumption timer value in this case 4s. Switching to HS-DSCH tried after the timer expires.
Active set size=1 after this Active Set Update (no SHO anymore). Resumption timer started. RB reconfiguration to DCH0/0. 4s resumption timer applied before. ~2.5 seconds gap according signaling. The data gap is about 6s when measured with Ethereal. RB reconfiguration to HS-DSCH
Application throughput
DCH NRT
HS-DSCH
EventId RRCD RRCU RRCD RRCD RRCU RRCD RRCU RRCD RRCU RRCU RRCD
Time 08:24.8 08:24.8 08:25.1 08:29.3 08:30.5 08:30.7 08:30.7 08:31.7 08:32.8 08:32.8 08:33.1
Subchannel DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH DCCH
Message "ACTIVE_SET_UPDATE" "ACTIVE_SET_UPDATE_COMPLETE" "MEASUREMENT_CONTROL" "RADIO_BEARER_RECONFIGURATION" "RADIO_BEARER_RECONFIGURATION_COMPLETE" "MEASUREMENT_CONTROL" "MEASUREMENT_REPORT" "RADIO_BEARER_RECONFIGURATION" "MEASUREMENT_REPORT" "RADIO_BEARER_RECONFIGURATION_COMPLETE" "MEASUREMENT_CONTROL"
43
NOKIA

HSDPA Partner Workshop v1

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

HSDPA Partner Workshop v1

Enviado por

Direitos autorais:

Formatos disponíveis

HSDPA Workshop

Nokia RNWP CHT Project 2006 Sept.

HSDPA General Workshop / MHL /2006 Sept

HSDPA General principle

Fast Link Adaptation in HSDPA

Instantaneous EsNo [dB]

C/I varies with fading

16QAM3/4 16QAM2/4 QPSK3/4 QPSK2/4 QPSK1/4

Link adaptation mode

Time [number of TTIs]

HSDPA General Workshop / MHL /2006 Sept

Link adaptation: Modulation

QPSK 2 bits / symbol = 480 kbit/s/HS-PDSCH = max. 7.2 Mbit/s

16QAM 4 bits / symbol = 960 kbit/s/HS-PDSCH = max. 14.4 Mbit/s

HSDPA General Workshop / MHL /2006 Sept

HSDPA Peak Bit Rates

RAN05 RAN05 CD1

Three HSDPA UEs receiving data

2nd TTI 1st TTI

HSDPA General Workshop / MHL /2006 Sept

Throughput vs. EcNo

Ec/Io: with and without HSDPA (R99 + R5 HSDPA)

HSDPA_2W HSDPA_4W HSDPA_6W HSDPA_8W HSDPA_10W

-8.0 -9.0 -10.0 -11.0 -12.0 -13.0 -14.0 -15.0 -16.0 -3 -6 -9

Mobile UE Under 1 Cell - Throughput

Thr ought put vs RSCP

2000 1800 1600 1400 Thr oughput ( kbps) 1200 1000

-80 RSCP ( dBm )

-80 RSCP ( dBm )

HSDPA General Workshop / MHL /2006 Sept

-40 -50 Company Confidential

-80 RSCP ( dBm )

0.0 -5.0 0 dB -10.0 -15.0 -20.0 -25.0 s

Avg. Throughput ~950kbps

HSDPA General Workshop / MHL /2006 Sept

HSDPA General Workshop / MHL /2006 Sept

HSDPA General Workshop / MHL /2006 Sept

Multiple Users Test: 3 Datacards in Static

HSDPA General Workshop / MHL /2006 Sept

Release99 vs HSDPA Retransmissions

Retransmission RLC ACK/NACK

Packet RLC ACK/NACK L1 ACK/NACK

HSDPA General Workshop / MHL /2006 Sept

New Node B functionality for HSDPA

Packets Flow Control

Scheduler & Buffer

New terminal functionality for HSDPA

Packets Flow Control

HSDPA Protocol Architecture

UE NAS RLC MAC-d MAC-hs WCDMA L1

SRNC RLC MAC-d FRAME PROTOCOL TRANSPORT

FRAME PROTOCOL TRANSPORT Iub/Iur

HSDPA user plane

HSDPA General Workshop / MHL /2006 Sept

PDUs of Different Protocol Layers

part of RLC SDU

part of RLC SDU

RLC PDU (= MAC-d SDU)

RLC PDU (= MAC-d SDU)

MAC-d PDU (= MAC-hs SDU)

MAC-d PDU (= MAC-hs SDU)

MAC-hs PDU (= transport block = TB) HS-SCCH

HSDPA General Workshop / MHL /2006 Sept

MAC-d and MAC-hs