hsdpa partner workshop v1

8/13/2019 HSDPA Partner Workshop v1

1/43


2/43

2 NOKIA HSDPA General Workshop / MHL /2006 Sept Company Confidential

HSDPA General principle

Terminal 1 (UE)

Terminal 2

L1 Feedback

L1 Feedback

Data

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)

QPSK or 16QAMmodulation

User may be time and/orcode multiplexed.

Channel qualityinformation

Error correctionAck/Nack


3/43


Fast Link Adaptation in HSDPA

0 20 40 60 80 100 120 140 160

-2

0

2

4

68

10

12

14

16

Time [number of TTIs]

QPSK1/4

QPSK2/4

QPSK3/4

16QAM2/4

16QAM3/4

In

stantaneous

EsNo

[dB] C/I received by

UE

Linkadaptation

mode

C/I varieswith fading

BTS adjusts link adaptationmode with a few ms delaybased on channel quality

reports from the UE


4/434 NOKIA HSDPA General Workshop / MHL /2006 Sept Company Confidential

Link adaptation: Modulation

QPSK2 bits / symbol =

480 kbit/s/HS-PDSCH =max. 7.2 Mbit/s

6QAM4 bits / symbol =

960 kbit/s/HS-PDSCH =max. 14.4 Mbit/s

1011 1001

10001010

0001 0011

00100000

0100 0110

01110101

1110 1100

11011111

Q

I

10 00

0111

Q

I



HSDPA Peak Bit Rates

Coding rateCoding rate

QPSKQPSK

Coding rateCoding rate

1/41/4

2/42/4

3/43/4

5 codes5 codes 10 codes10 codes 15 codes15 codes

600 kbps600 kbps 1.2 Mbps1.2 Mbps 1.8 Mbps1.8 Mbps

1.2 Mbps1.2 Mbps 2.4 Mbps2.4 Mbps 3.6 Mbps3.6 Mbps


16QAM16QAM

2/42/4

3/43/4

4/44/4




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 thecell/BTS.

1st TTI

2nd TTI

3rd TTI

Three HSDPA UEsreceiving data



1-THROUGHPUT

Throughput vs. EcNo

0

200000

400000

600000

800000

1000000

1200000

1400000

1600000

1800000

-3 -6 -9 -12 -15EcNo

Through

put

2 W

4 W

6 W

8 W

10 W

PtxMaxHSDPAPtxMaxHSDPA

Stationary user

Option datacard with Nemo

RLC throughput

Initial EcNo on the x-axis

Stationary user

Option datacard with Nemo

RLC throughput

Initial EcNo on the x-axis



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

Ec/Io vs Initial Ec/Io

-16.0

-15.0

-14.0

-13.0

-12.0

-11.0

-10.0

-9.0

-8.0-7.0

-6.0

-5.0

-4.0

-3 -6 -9 -12 -15

Initial Ec/Io (w ithout HSDPA)

E

c/Io(withHSDPA)

HSDPA_2W

HSDPA_4W

HSDPA_6W

HSDPA_8W

HSDPA_10W

General Obersvation:

E.g. Initial CPICH Ec/Io is -3dB. However,

when HSDPA user is active, immediateobservation of Ec/Io degradation.

Amount of degradation depends on the

PtxMaxHSDPA parameter set.

General Obersvation:

E.g. Initial CPICH Ec/Io is -3dB. However,

when HSDPA user is active, immediateobservation of Ec/Io degradation.

Amount of degradation depends on the

PtxMaxHSDPA parameter set.



Mobile UE Under 1 Cell - Throughput Novatel Data card

Thr oughtput vs RS P

0

200

400

600

800

1000

1200

1400

1600

1800

2000

-120-110-100-90-80-70-60-50-40

RSCP ( dBm)

Throughput

(kbps)

Q vs RS P

0

5

10

15

20

25

-120-110-100-90-80-70-60-50-40

RSCP (dBm)

CQI

EcNo vs RS P

-20

-15

-10

-5

0

-120-110-100-90-80-70-60-50-40

RSCP ( dBm)

Ec/No

A li ti th h t


10/43


Application throughput

0

200000400000

600000

800000

1000000

1200000

1400000

1600000

1800000

0 50 100 150 200 250 300 350 400 450 500 550

s

bps

CPICH Ec/No

-25.0

-20.0

-15.0

-10.0

-5.0

0.0

0 50 100 150 200 250 300 350 400 450 500 550

s

dB

CQI

0.0

5.0

10.0

15.0

20.0

25.030.0

0 50 100 150 200 250 300 350 400 450 500 550

s

CPICH RSCP

-120.0

-100.0

-80.0

-60.0

-40.0

-20.0

0.0

0 50 100 150 200 250 300 350 400 450 500 550

s

dBm

CQI distribution

0

20000

40000

60000

80000

100000

120000

140000

1 3 5 7 9 11 13 15 17 19 21 23 25 27 29

CQI value

#messag

es

Avg. Throughput~950kbps

ff f ffi i


11/43


Effect of HSDPA Traffic on R'99 DCHs Ec/No QualityFTP download Example (good radio Conditions)

HSDPA Throughput

Pilot Ec/No

Without

HSDPA User

=> Ec/No = -

4dB

With HSDPA

User

=> Ec/No

degraded = -8dB

ff f ffi ' / li


12/43


Effect of HSDPA Traffic on R'99 DCHs Ec/No QualityFTP download Example (good radio Conditions)

Test 2 run 2

0

200000

400000

600000

800000

1000000

1200000

1400000

1600000

0 20 40 60 80 100 120

Relative Time

ApplicationTP

-10

-9

-8

-7

-6

-5

-4

-3

-2

-1

0

Ec/Io(dB)

Application Throughput Ec/No

Ec/Io decreases

of 3 dB during

the transfer. Thisdifference is due

to the

PtxMaxHSDPA

power which isallocated only

when there is at

least one HSDPA

user


13/43


Multiple Users Test: 3 Datacards in Static

Datacards: 2 Novatel and 1 Sierra

Service: 3 FTP users

Impact of 3 Users on Throughput

0

200000

400000

600000

800000

1000000

1200000

1400000

1600000

Time (s)

ApplicationT

hroughput

(bps)

1 user 1 user2 users 2 users3 users


14/43


Release99 vs HSDPA Retransmissions

Terminal

BTS

RNC

Rel99 DCH/DSCH Rel5 HS-DSCH

Packet Retransmission

RLC ACK/NACK

L1Retransmission

L1 ACK/NACK

Packet

RLC Retransmission

RLC ACK/NACK


15/43


New Node B functionality for HSDPA

TerminalsNode BRNC

PacketsScheduler

& Buffer

ARQ &

Coding

ACK/NACK &Feedback Decoding

Flow Control

New Node B functions:

Scheduler: Terminal scheduling, Coding & Modulation selection (16QAMas new modulation)

ARQ Retransmissions Handling

Uplink Feedback Decoding

Flow Control towards SRNC


16/43


New terminal functionality for HSDPA

TerminalNode BRNC

PacketsARQ

Decoding

Soft Buffer

& Combining

ACK/NACK &Feedback

Generation

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


17/43


HSDPA Protocol Architecture

New MAC entity, MAC-hs added to the Node B

Layers above, such as RLC, unchanged.

WCDMA L1

UE

Iub/Iur

SRNCNode B

Uu

MAC-hs

RLC

NAS

HSDPA user plane

WCDMA L1

MAC-hs

TRANSPORT

FRAMEPROTOCOL

TRANSPORT

FRAMEPROTOCOL

MAC-dRLC IuMAC-d


18/43


PDUs of Different Protocol Layers

RLC

higher layer

MAC-d

MAC-hs PDU (= transport block = TB)physical

layer

padMAC-hs

RN

C

No

de

-B

Iub

header MAC-d PDU (= MAC-hs SDU)

header RLC PDU (= MAC-d SDU) header RLC PDU (= MAC-d SDU)

header part of RLC SDU header part of RLC SDU

higher layer data packet

HS-SCCH

MAC-d PDU (= MAC-hs SDU)


19/43


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

Mac-hs is responsible for: Packet scheduling Link adaptation L1 error correction and retransmissions (H-ARQ) Flow control between RNC and BTS

MAC-hs

PHY PHY TNL

MAC-d

MAC-hs

HS-

DSCH FP

HS-

DSCH FP

MAC-d

TNL

UE Uu BTS Iub RNC

RLC RLCMAC-d flow

HS-DSCH

HS-PDSCH


20/43


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 CQIinformation.

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.


21/43


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 areco-incident. This is always the case in

RAN05 which has no Iur for HSDPA.

TNL

MAC-d

DCHFP

DCHFP

MAC-d

TNL

BTS Iub RNC

RLC RLC

PHY PHY

UE Uu

DCH

DPCH

MAC-hs

PHY PHY TNL

MAC-d

MAC-hsHS-DSCH

FP

HS-DSCH

FP

MAC-d

TNL

UE Uu BTS Iub RNC

RLC RLC

MAC-d flow

HS-DSCH

HS-PDSCH


22/43


UE

HSDPA Protocol Model

Transport chsPhysical chs

HS-DSCH

HS-PDSCH

HS-SCCH

HS-DPCCH

DPDCH

DPCCH

DTCH #1

DTCH #2

MAC-d flow #1

MAC-d flow #2

MAC-d flow #8

DCH

Up to 8 MAC-d flows can be mapped to one UE (3GPP)

In RAN05 only one MAC-d flow per UE is possible

Logical chs

HSDPA

DCH


23/43


Physical Channels for One HSDPA UE

UE

BTS

Associat

ed

DPCH

Associat

ed

DPCH

1-

15

xH

S-

PDSCH

1-

4

xH

S-

SCCH

HS-D

PCCH

DL CHANNELS HS-PDSCH: High-Speed Physical

Downlink Shared Channel

HS-SCCH: High-Speed Shared Control

Channel Associated DPCH, Dedicated Physical

Channel.

UL CHANNELS

Associated DPCH, Dedicated PhysicalChannel

HS-DPCCH: High-Speed DedicatedPhysical Control Channel

Rel99DCH


24/43


HSDPA DL physical channels

HS-SCCH: High-Speed Shared ControlChannel

Includes information to tell the UE howto decode the next HS-PDSCH frame

Fixed SF128 Nokia implementation has power

control Shares downlink power with the HS-

PDSCH More than one HS-SCCH required when

code multiplexing is used

Field Number ofuncoded bits

Channelisation code set information 7 bits

Modulation scheme information 1 bit

Transport block size information 6 bits

Hybrid ARQ process information 3 bits

Redundancy and constellation version 3 bits

New data indicator 1 bit

UE identity 16 bits

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

h i l h l


25/43


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)

HSDPA UL h i l h l


26/43


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)

HSDPA UL physical channels

Ph i l h l t t


27/43


Physical channel structure

HS-PDSCH #2UE1

UE2

UE2

UE2

UE1

UE1

UE1

HS-PDSCH #1UE1

UE2

UE2

UE2

UE1

UE3

UE3

UE3

UE1

UE1

HS-PDSCH #3UE1

UE1

UE1

UE1

UE #1

UE #2

UE #3

2 ms

1 radio frame (15 slots, total 10 ms)

151413121110987654321

Subframe #5Subframe #4Subframe #3Subframe #2Subframe #1

HS-SCCHUE1

UE2

UE2

UE2

UE1

UE3

UE3

UE3

UE1

UE1

User data onHS-DSCH

HS-DPCCHL1 feedback

3 slots

2 slots

HS-DPCCHL1 feedback

HS-DPCCHL1 feedback

3GPP enablestime and codemultiplexing.

Picture presentstime multiplexing

C d M lti l i ( t i RAN05/5 1)


28/43


HS-PDSCH

HS-PDSCH

HS-PDSCHHS-PDSCH

Code Multiplexing (not in RAN05/5.1)

With Code Multiplexing, multiple UEscan be scheduled during one TTI.

Multiple HS-SCCH channels One for each simultaneously

receiving UE. HS-SCCH power overhead.

HS-PDSCH codes divided for differenttransport blocks.

Multiple simultaneous transport blocksto one UE not possible.

Important when cell supports morecodes than UEs do. For example 10codes per cell, UE category 6.

How to divide HS-PDSCH powerbetween simultaneous UEs?

Packet Scheduling algorithm?

HS-PDSCH

cat 6

HS-PDSCH

HS-PDSCH

HS-PDSCHHS-PDSCH

HS-PDSCH

HS-SCCHHS-SCCH

cat 6 cat 6 cat 6cat 8


29/43


SF = 128

SF = 256

SF = 64

SF = 32

SF = 8

SF = 16

SF = 4

SF = 2

SF = 1

Codes for the cell common channels

Code for one

HS-SCCH

Codes for 5

HS-PDSCH's

Downlink Code Allocation

166 codes @ SF=256 available for the associated DCHs and non-HSDPA uses

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

DL DCH Spreading Factor (Nemo)


30/43


DL DCH Spreading Factor (Nemo)

DCH 384kbps

DCH 128kbps

DCH 64kbps

SRB 13.6kbps (During Call Setup)

Associated DL DPCH (for SRB, 3.4bkps)

Channel Allocation in WSPC


31/43


Channel Allocation in WSPC

Wideband Signal Processing unit (WSPC) is a flexible software based cardhandling both uplink and downlink channels

WSPC can handle common channels for 3 carriers and user data accordingto base band processing capacity tables

HSDPA block is able to handle up to 3 cells (time multiplexed) and isallocated to one WSPC card

Common chs

remainingcapacity

48 CE

Carrier 1Carrier 1Common channels

Carrier 1Carrier 1

Carrier 1Carrier 1

.

Traffic channels

1. WSPC 2. WSPC Nth WSPC

remainingcapacity

32 CE

capacity64 CE

HSDPA BLOCK(5codes)Reserved

by RRM = 32CE

Same type WSPC

handles common andHSDPA channels

= R5 HSDPA

= R99 DCH

Customer Confidential


32/43


PtxtargetHSDPA AND PtxoffsetHSDPA

STRATEGY:1) The ratio between PC headroom and Variable Power shall remain the same after the introduction of HSDPA becauseHSDPA 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 beallocated and soon released DCH power increase


33/43


Power Allocation (CHT)

PtxmaxHSDPA

CPICHCPICH

20W

12W

43dBm

40.8dBm

39.8dBm

33dBm2W

9.5W

8W

PtxoffsetHSDPA

2W 33 dBm

15.8W

20W

42 dBm

43 dBm

DCH + Variablepart of CCHs

PtxTargetHSDPADCH + Variablepart of CCHs

Ptxoffset

PtxTarget

HSDPAPriority =1

HW Requirements (CHT)


34/43


HW Requirements (CHT)

Sf16(11-15)5HSDPA Code allocation

1 DMCU=4 DMPG=4*6 HSDPA sites=4*16HSDPA users

RNC Step5: 4RNC Step4: 3

RNC Step3: 2

Initial DMCU Allocation

2 WSPC => 2E1

3 WSPC => 3E12E1Min Required E1

32CEs reserved for CCH

32CEs reserved for HSDPA128Min Required CE

Max HSDPA allocation: 3 Cell/siteSupreme/Optima/Metro50Node B

8WPwr allocation for HSDPA

40W/SecMin Required WPA

10762: DCH

10787: HSDPA+DCH(Rel5UE)

2 Carrier

(10762, 10787)Carrier

RemarkRequirement

Deployment Strategy


35/43


Deployment Strategy-Co-existence of R'99 and R5 HSDPA

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)

F1 (R99+R5)F1 (R99+R5)

= R5 HSDPA + R5 DCH= R'99 DCH

Deployment Strategy


36/43


Deployment Strategy- Dedicated Carrier for HSDPA

F1 R99F1 R99

F2 R5F2 R5

Case2: Dedicated R5 (HSDPA+DCH) carrier

R5 UE (HSDPA + DCH) directed to R5 HSDPA

carrier Recommended for hotspot, indoor, majorcorporate customer office etc.

Minimum Impact to existing system (capacity andperformance) 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.)

= R5 HSDPA + R5 DCH= R'99 DCH

Used in CHT Project

Directed RRC Connection Setup for HSDPA


37/43


Directed RRC Connection Setup for HSDPA

DirectedRRCEnabled

The parameter enables/disables the use of directed RRC connection setup ordirected 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

Mobility Handling Scheme

ADJI (f2 -> f1) Planning- Include own sites f1 cells


38/43



2G

HSDPA DRRCIFHO (f2->f1)

-RT: RSCP (-95dBm) &Ec/No (-12dB)

-NRT: RSCP (-95dBm)

-Oneway adji

IFHO (f1->f2)

RT/NRT: disabledxNo IFCR (f1 -> f2)

- No adji (f1->f2)

XNo 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

UMTS F2 (HSDPA Enabled)

UMTS F1 (DCH)

ISHO (f2->2G)

-RT/NRT: Disabled

IFCR (f2->f1)

-Oneway adji

(same as IFHO)

R99UER5UE

Include own site s f1 cells.- Plan up to 2~3 tier sitesdepending on f2spropagation.

X

X

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.



39/43



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 continuouscoverage.

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: F12G

HSDPA mobility in RAS05 CD1 (1)


40/43


- HSDPA Serving Cell Change

HSDPA Serving Cell Change

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

HS-DSCH coverage HS-DSCH coverage

Service in

HSDPA(Serving Cell)

Switching to

Cell_FACH (Target

Cell) within the

SHO area

UE on HS-DSCH(Target Cell)

Cell A Cell B

HSDPA

DCH

0

Throughput

64kbps

128kbps or 384kbps according to parameter settings

HSDPA mobility in RAS05 CD1 (1)


41/43


- HSDPA Resumption Timer

HSDPA resumption timer switchesthe user from DCH to HS-DSCH,

when UE enters HSDPA area

The conditions preventing HSDPA allocation in HSPDAcoverage 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

R99 coverage HS-DSCH coverage

Service

NRT DCH

Switching to

HS-DSCH when

not in SHO area

Cell A Cell B

HSDPA

DCH

0

Throughput

64kbps (initial bitrate)

128kbps or 384kbps according to parameter settings

Download

complete

Resumption timer


42/43


Resumption timer

RNP parameter in RNC. Timer started when HSDPA

capable UE having DCH NRTenters into HSDPA capable cell

and Active set size=1.

Switching to HS-DSCH is triedafter the timer expires, if theActive set size is still 1.

Switching happens viaDCH0/0.

Normal HSDPA selection

procedure is applied after acapacity request, whenDCH0/0 is allocated.

Resumption timerDCH t HS DSCH it h


43/43


- DCH to HS-DSCH switch

Resumption timer startedwhen Active set size =1.

Resumption timer value inthis case 4s.

Switching to HS-DSCH triedafter the timer expires.

Application throughput

0

500000

1000000

1500000

0 10 20 30 40 50s

bps

"MEASUREMENT_CONTROL"DCCH08:33.1RRCD

"RADIO_BEARER_RECONFIGURATION_COMPLETE"DCCH08:32.8RRCU

"MEASUREMENT_REPORT"DCCH08:32.8RRCU

"RADIO_BEARER_RECONFIGURATION"DCCH08:31.7RRCD

"MEASUREMENT_REPORT"DCCH08:30.7RRCU


"RADIO_BEARER_RECONFIGURATION_COMPLETE"DCCH08:30.5RRCU

"RADIO_BEARER_RECONFIGURATION"DCCH08:29.3RRCD


"ACTIVE_SET_UPDATE_COMPLETE"DCCH08:24.8RRCU

"ACTIVE_SET_UPDATE"DCCH08:24.8RRCD

MessageSubchannelTimeEventIdActive set size=1 after this Active Set

Update (no SHO anymore).

Resumption timer started.

RB reconfiguration to DCH0/0.

4s resumption timer applied before.

RB reconfiguration to HS-DSCH

~2.5 seconds gap accordingsignaling. The data gap is about 6s

when measured with Ethereal.

DCH NRT HS-DSCH

hsdpa partner workshop v1

Documents