You are on page 1of 66

HSDPA Call

Setup

HSDPA Call Setup


Review of HSDPA

HSDPA Call Setup

Radio Resource Control Messages

Review of HSDPA

Physical Channels for One HSDPA UE


Associated DPCH, Dedicated Physical
Channel

BTS

DPCH needed for each HSDPA UE.


Signalling, uplink data.

HS-DPCCH

1-4 x HS-SCCH

Associated
DPCH
Associated
DPCH
1-15 x HSPDSCH

HS-PDSCH: High-Speed Physical Downlink


Shared Channel
Actual HSDPA data of HS-DSCH transport
channel.
1-15 code channels.
QPSK or 16QAM modulation.

HS-SCCH: High-Speed Shared Control


Channel
Informs UE how to receive HS-PDSCH in the
same TTI.

UE

HS-DPCCH: High-Speed Dedicated


Physical Control Channel
MAC-hs Ack/Nack information.
Channel Quality Information.

HSDPA Layer 1 channels

Uplink Physical Channel


Dedicated uplink physical channels
There are three types of uplink dedicated physical channels, the uplink Dedicated
Physical Data Channel (uplink DPDCH), the uplink Dedicated Physical Control Channel
(uplink DPCCH ), and the uplink Dedicated Control Channel associated with HS-DSCH
transmission (uplink HS-DPCCH ).
The DPDCH, the DPCCH and the HS-DPCCH are I/Q code multiplexed.
The uplink DPDCH is used to carry the DCH transport channel.
The uplink DPCCH is used to carry control information generated at Layer 1. The Layer 1
control information consists of known pilot bits, transmit power-control (TPC) commands,
feedback information (FBI), and transport-format combination indicator (TFCI).

Uplink Physical Layer


cd,1

Data
Ndata bits

DPDCH

DPDCH1

Tslot = 2560 chips, Ndata = 10*2k bits (k=0..6)


cd,3

DPDCH3
cd,5

Pilot
Npilot bits

DPCCH

FBI
NFBI bits

TFCI
NTFCI bits

TPC
NTPC bits

Tslot = 2560 chips, 10 bits

DPDCH5

Sdpch,n
chs

I+jQ

hs

HS-DPCCH

(If Nmax-dpdch mod 2 = 0)

cd,2

Slot #0

Slot #1

Slot #i

Slot #14

1 radio frame: T f = 10 ms

DPDCH2

Frame structure for uplink DPCCH


cd,4

DPDCH4
cd,6

cc

chs

hs

DPDCH6

Tslot = 2560 chips

2Tslot = 5120 chips

HARQ-ACK

CQI

One HS-DPCCH subframe (2 ms)

DPCCH

HS-DPCCH
(If Nmax-dpdch mod 2 = 1)

Spreading for uplink DPCCH, DPDCHs and HS-DPCCH

Subframe #0

Subframe #i
One radio frame Tf = 10 ms

Frame structure for uplink HS-DPCCH

Subframe #4

Transport /Physical Channels mapping (UL


example)
TrCH x

Ue Side

Transport Block

Higher Layers
UTRAN:MAC / FP

Transport Block

TFITransport Block TFITransport Block

TFCI

Physical Layer
BTS L1

Coding & Multiplexing

Physical Control
Channel
DPCCH

TFI

Physical Data
Channel
DPDCH

BS Side

TB & Error
Indication

TB & Error
Indication

TB & Error
Indication

TFCI
decoding

TFI

TB & Error
Indication

DeCoding & De-Multiplexing

Physical Control
Channel
DPCCH

TrCH y

Physical Data
Channel
DPDCH

Downlink Physical Channel

(1/2)

Dedicated downlink physical channels


There is only one type of downlink dedicated physical channel, the Downlink Dedicated
Physical Channel (downlink DPCH).
Within one downlink DPCH, dedicated data generated at Layer 2 and above, i.e. the
dedicated transport channel (DCH), is transmitted in time-multiplex with control
information generated at Layer 1 (known pilot bits, TPC commands, and an optional
TFCI). The downlink DPCH can thus be seen as a time multiplex of a downlink DPDCH and
a downlink DPCCH.

Downlink Physical Channel

(2/2)

Common downlink physical channels


The High Speed Physical Downlink Shared Channel (HS- PDSCH) is used to carry the High
Speed Downlink Shared Channel (HS-DSCH). A HS-PDSCH corresponds to one
channelization code of fixed spreading factor SF=16 from the set of channelization codes
reserved for HS-DSCH transmission. Multi-code transmission is allowed, which translates
to UE being assigned multiple channelisation codes in the same HS-PDSCH subframe,
depending on its UE capability.
The HS-SCCH is a fixed rate (60 kbps, SF=128) downlink physical channel used to carry
downlink signalling related to HS-DSCH transmission. Figure 26A illustrates the sub-frame
structure of the HS-SCCH.

Downlink Physical Channel


DPCCH

DPDCH
Different downlink
Physical channels
(point S in Figures 8)

Data1
Ndata1 bits

G1

TPC
NTPC bits

TFCI
NTFCI bits

DPDCH

DPCCH

Data2
Ndata2 bits

Pilot
Npilot bits

Tslot = 2560 chips, 10*2k bits (k=0..7)


G2

P-SCH
GP

(point T in
Figure 11)

Slot #0

Slot #1

Slot #i

Slot #14

One radio frame, Tf = 10 ms

S-SCH
GS

Combining of downlink physical channels

Frame structure for downlink DPCH


Data
Ndata 1 bits

Data
Ndata 1 bits
Tslot = 2560 chips, M*10*2 k bits (k=4)

Slot #0

Slot#1

T slot = 2560 chips, 40 bits

Slot #2

1 subframe: Tf = 2 ms

Subframe structure for the HS-PDSCH

Slot #0

Slot#1
1 subframe: Tf = 2 ms

Subframe structure for the HS-SCCH

Slot #2

HSDPA Protocol Architecture


New MAC entity, MAC-hs (high-speed) added to the Node B
Layers above, such as RLC, unchanged.

RLC

RLC

MAC-d

MAC-d

MAC-hs

HS-DSCH

MAC-hs

HS-DSCH FP

PHY

HS-PDSCH

PHY

TNL

UE

Uu

BTS

MAC-d flow

HS-DSCH FP
TNL

Iub

RNC

MAC Architecture
Handles
common
channels
MAC Control

Handles
high
speed
channels

CTCH

SHCCH

MAC Control

DCCH DTCH
MAC Control

TDD only

DTCH

MAC-d

Configuration
without MAC-c/sh
Configuration
with MAC-c/sh

MAC-hs

BS

HS-DSCH HS-DSCH
Associated Downlink
Signalling

HSSCCH

PCCH BCCH CCCH

Handles
dedicated
channels

HSPDSCH
HS-PDSCH DL

MAC-c/sh

Configuration
with MAC-c/sh

Iub

PCH FACH FACH

Associated Uplink
Signalling

HSDPCCH

HS-SCCH DL SF 128 n codes x SF 16HS-DPCCH UL SF 256

RACH

RNC

RNC

USCH

USCH

DSCH DSCH

TDD only

TDD only

TDD only

Physical Layer

TDD only

Iur or local

DCH

DPCH ( UL+DL
rrc messages
DPCH
(DCCH)
) DL SF
256

DCH

DPCH ( UL
RLC+TCP-IP ack
(DTCH)
DPCH)UL SF 16

Node B enhancements for HSDPA


Node B

RNC

Packets
Flow Control

Terminals

Scheduler

HARQ &

& Buffer

Coding
ACK/NACK &
Feedback
Decoding

R99 responsibilities:

New Node B functions for HSDPA:

Physical layer operations

Sophisticated Scheduler:

No dymanic decision making

In order Delivery within priority queue


Data Buffer management
OVSF (orthogonal Variable Spread. Fact.) code management
Packet scheduling
Data Transfer on HS-DSCH
Physical layer operations
HARQ Retransmissions Handling
Modulation selection
Link adaptation
Flow Control towards SRNC

HS-DSCH code management


PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST [FDD]
NBAP-PDU
- messageDiscriminator: common
PhysicalSharedChannelReconfigurationRequestFDD
C-ID: 3

RNC

BS

MaximumTransmissionPower: 378
HS-PDSCH-FDD-Code-Information
- extension flag: 0

at restart
phase

- preamble: 10
- number-of-HS-PDSCH-codes: 5
- hS-PDSCH-Start-code-number: 11

PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST is sent by the RNC during the restart
of the BS. It defines the Max power and Max number of codes SF 16 available for the HS-DSCH
channel.
MAC hs is responsible for HS-PDSCH management. Codes selection is a dynamic procedure based
on Ue BS link quality.

Retransmissions in HSDPA
Server

RNC

Node-B

MAC-hs retransmissions

TCP retransmissions
RLC retransmissions

UE

Iub Flow Control messages


(1/2)
HS-DSCH Capacity
Request

CRNC

Node B

CAPACITY REQUEST

HS-DSCH Capacity Request procedure

The HS-DSCH Capacity Request procedure provides means for the RNC to request
HS-DSCH capacity to the BS , by indicating the user buffer size in the RNC for a
given priority level (CmCH-PI).
The RNC is allowed to reissue the HS-DSCH Capacity Request if from the BS no
CAPACITY ALLOCATION has been received within an appropriate time threshold.

Iub Flow Control messages


(2/2)
HS-DSCH Capacity
Allocation

CRNC

Node B

CAPACITY ALLOCATION

HS-DSCH Capacity Allocation is generated either in response to a HS-DSCH


Capacity Request or at any other time.
The flow control is mainly controlled by the Node-B sending capacity allocation
messages. The Node-B does know the status of the buffers in the RNC by the
capacity request and by every further data frame . So the Node B may use this
message to modify the traffic flow at any time by indicating its capacity to deliver
PDU.

These are the possible status for a UE in a UMTS


network

UE RRC status

IDLE MODE: Stand by mode. The UE is able to


listen to BCH channel through the PCCPCH in
order to receive the System Information. No RRC
is available for the UE.

Connected Mode
Idle

mode

Cell DCH

Cell PCH

Cell FACH
URA PCH

CELL DCH: one of the Connected Mode. The UE


is able to send and receive RRC messages
DPDCH.
From Cell DCH for inactivity timer the UE can
move to Cell FACH . Here it is able to use the
DCCH and DTCH through the SCCPCH. This
status allow the UE to save battery and
resources. The UE can maintain low bit rate
connection with the HTTP server.
From Cell FACH for inactivity timer the UE can
move to Cell PCH. This status allow the UE to
save battery. In fact here the UE listen to the
PCH only.
URA PCH status is optional. It can be adopted in
case is necessary to decrease the number of cell
update performed by the UE when it move from
one to another cell.

RAS05 Mobility with DCH switching


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
in
HSDPA

Switch
to
DCH
0/0

HS-DSCH coverage
Throughput
HSDPA

DCH

128kbps or 384kbps according to settings


64kbps

Upgrad
e to e.g.
64 kbps

HSDPA resumption timer


switches the user from DCH to
HS-DSCH, when UE exits SHO
area

Upgrad
e to 128
/ 384
kbps

Cell B
Switch
to HSDSCH

HS-DSCH coverage
UE on
HSDSCH
Once the session is in DCH, it
remains there until the buffers are
empty.
After that, HSDPA can be selected

HSDPA Mobility Handling with DCH


Switching
Separate parameters sets for HSDPA UE is implemented by
including a HSDPA specific identifier in the WCEL parameters
The following object classes can be defined for each cell
Intra Frequency Measurement Control FMCS
Inter Frequency Measurement Control FMCI
Inter System Measurement Control FMCG
Intra Frequency Handover Path HOPS
Fallbacks from the HS-DSCH to the DCH can be followed up through
counters
CR727 when implemented will allow DCH to HSDPA switching
without having to go to Cell_FACH state first.

Serving Cell Change via cell_FACH


HSDPA Serving Cell Change via Cell-FACH
feature is used only in intra frequency
handover cases
In case of IFHO or ISHO the original DCH
switching procedures are used

Cell A
Service
in
HSDPA
HS-DSCH coverage
Throughput
HSDPA

DCH

128kbps or 384kbps according to parameter settings


64kbps

Switching to
Cell_FACH
within the
SHO area

Serving Cell Change switches


the user from HS-DSCH to
Cell_FACH then back to HSDSCH

Cell B
UE on HSDSCH

HS-DSCH coverage

HSDPA Resumption Timer


HSDPA resumption timer
Waiting time before a DCH to HS-DSCH
switch is attempted.

Cell A
Service
NRT DCH

R99 coverage
Throughput
HSDPA

DCH

128kbps or 384kbps according to parameter settings


64kbps (initial bitrate)

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

Switching to HS-DSCH is tried


after the resumption timer
expires
(if the Active set size is still 1)

Cell B

HS-DSCH coverage
Download
complete

Serving HS-DSCH Cell Change

Transmission of the HS-SCCH and the HS-PDSCH to one UE belongs to


only one of the radio links assigned to the UE, i.e. no soft/softer
handover support as for Rel99 dedicated channels.
Synchronized change of the serving HS-DSCH cell is supported in
RAS05.1
This allows implementation of HSDPA with full mobility and coverage,
including HSDPA coverage for UEs with an active set size larger than
one for its dedicated channels.
Soft/softer handover is not supported
for HS-SCCH/HS-PDSCH.

Serving
HS-DSCH cell

HS-SCCH
HS-PDSCH

DPCH

HS-DPCCH
DPCH
TS
25.308:

The mobility procedures are affected by the fact


that the HS-PDSCH allocation for a given UE
belongs to only one of the radio links assigned to
the UE, the serving HS-DSCH radio link. The cell
associated with the serving HS-DSCH radio link is
defined as the serving HS-DSCH cell. A serving
HS-DSCH cell change facilitates the transfer of the
role of serving HS-DSCH radio link from one radio
link belonging to the source HS-DSCH cell to a
radio link belonging to the target HS-DSCH cell.

RAS05.1

HSDPA Call set up

IDLE Mode Cell DCH transaction


UE

Node-B

RNC
IDLE MODE

RRC

RRC
RRC

RRC Connection Request ( RACH )


RRC

NBAP

Radio Link Setup Request


(C-NBAP )

NBAP

NBAP

Radio Link Setup Response


(C-NBAP )

NBAP

ALCAP

Establish Request
(ALCAP)

ALCAP

ALCAP

Establish Confirm
(ALCAP)

ALCAP

RRC Connection Set Up ( FACH )

RRC

RRC Connection Set Up Complete ( DCH )


RRC

Cell DCH status

SGSN

Cell DCH HS-DSCH transaction


UE (1/2)Node-B
RNC
RRC
RRC
RRC

RRC Direct Transfer: Attach request

RRC

SGSN
Attach request

RANAP

RANAP

Attach accept

RRC Direct Transfer: Attach accept

RRC

RANAP

RANAP

Authentic. &
Ciphering

PDP context request


RRC Direct Transfer: PDP context request
RRC

RANAP

RANAP

RAB assign. request


RANAP
RRC
RRC

Radio Bearer Set Up


Radio Bearer Set Up Complete

RRC
RRC

RAB assign. response

RANAP
RRC
RRC
RRC

RRC Direct Transfer: PDP context accept


RRC

Measurement Control
Measurement Report

RANAP

PDP context accept

RANAP

RRC
RRC

RANAP
RANAP

Cell DCH HS-DSCH transaction


UE (2/2)Node-B
RNC
NBAP
NBAP
ALCAP
ALCAP
ALCAP
ALCAP

Radio Link Reconfiguration


Prepare
Radio Link Reconfiguration
Ready
Establish Request
Establish Confirm
Establish Request
Establish Confirm

Radio Reconfiguration
Commit
Radio Bearer Reconfiguration
NBAP

RRC
RRC

NBAP
NBAP
ALCAP
ALCAP
ALCAP
ALCAP
NBAP
RRC

Radio Bearer Reconfiguration Complete


RRC

HSDPA Traffic

SGSN

HS-DSCH Cell PCH transaction


UE (1/2)Node-B
RNC
Status change for inactivity timer
RRC
RRC

Radio Bearer Reconfiguration

RRC

Radio Bearer Reconfiguration Complete


RRC

Cell FACH status


NBAP
NBAP
ALCAP
ALCAP

Radio Link Deletion Request


Radio Link Deletion
Response
Release Request
Release Confirm

NBAP
NBAP
ALCAP
ALCAP

SGSN

HS-DSCH Cell PCH transaction


UE (2/2)Node-B
RNC
ALCAP
ALCAP

ALCAP
ALCAP

RRC
RRC

Release Request
Release Confirm
Release Request
Release Confirm

ALCAP
ALCAP

ALCAP
ALCAP

Physical Channel Reconfiguration ( FACH )


RRC

Physical Channel Reconfiguration Complete ( RACH )


RRC

Cell PCH status

SGSN

Cell PCH HS-DSCH transaction


UE (1/3)Node-B
RNC
Cell PCH status
RRC

RRC

Cell Update
Cell Update confirm

RRC

RRC

Cell FACH status


RRC

RRC

UTRAN mobility information confirm


Measurement Report

NBAP

NBAP

Radio Link Setup Request

Radio Link Setup


Response

RRC

RRC

NBAP

NBAP

SGSN

Cell PCH HS-DSCH transaction


UE (2/3)Node-B
RNC
ALCAP

ALCAP

ALCAP

ALCAP

ALCAP

ALCAP

Establish Request
Establish Confirm

Establish Request

Establish Confirm
Establish Request
Establish Confirm

SGSN

ALCAP

RRC
Transport
Channel

ALCAP

establishme
nt

ALCAP

DPCH
Transport
Channel

ALCAP

ALCAP

ALCAP

establishme
nt
HS-DSCH
Transport
Channel
establishme
nt

Cell PCH HS-DSCH transaction


UE (3/3)Node-B
RNC
RRC

RRC

Radio Bearer Reconfiguration

RRC

Radio Bearer Reconfiguration complete


RRC

Cell DCH status

RRC

Measurement Control

HS-DSCH

Capacity Request

Capacity Allocation
HS-DSCH

RRC

HS-DSCH

HS-DSCH

SGSN

Radio Resource Control Messages

CELL Update
Node-B

UE

RNC

Cell Update (RACH)

RRC

RNTI

RNTI

Measurement IEs

Cell Update cause

RRC

SRNC
Admission Control

Select Transport Chan

Measurement Quantity
causes options:
cell reselection,
periodical cell update,
uplink data
transmission,
paging response,
re-entered service area,
radio link failure,
RLC unrecoverable
error)

RRC

UE
RLC buffer
Checking

CN

In dB CPICH_Ec/No

RRC state indicator


RLC re-establish indicator

RLC re-establish indicator

Cell Update confirm (FACH)

RRC

options:
CELL_DCH,
CELL_FACH,
CELL_PCH,
URA_PCH)

Cell Update Message


CELL UPDATE
UL-CCCH-Message
integrityCheckInfo
messageAuthenticationCode: '01011101001110001111100011101001'B
rrc-MessageSequenceNumber: 2
message
cellUpdate
u-RNTI
srnc-Identity: '000100110010'B
s-RNTI: '00000000010011010100'B
startList
STARTSingle
cn-DomainIdentity: cs-domain
start-Value: '00000000000000000010'B
STARTSingle
cn-DomainIdentity: ps-domain
start-Value: '00000000000000001000'B

am-RLC-ErrorIndicationRb2-3or4: FALSE
am-RLC-ErrorIndicationRb5orAbove: FALSE
cellUpdateCause: uplinkDataTransmission
rb-timer-indicator
t314-expired: TRUE
t315-expired: FALSE
measuredResultsOnRACH
currentCell
modeSpecificInfo
fdd
measurementQuantity
cpich-Ec-N0: 45

Cell Update Confirm Message


CELL UPDATE CONFIRM [DCCH]
DL-DCCH-Message
integrityCheckInfo
messageAuthenticationCode: '11110111010101011110100011101101'B
rrc-MessageSequenceNumber: 2
message
cellUpdateConfirm
later-than-r3
rrc-TransactionIdentifier: 2
criticalExtensions
criticalExtensions
r5
cellUpdateConfirm-r5
new-C-RNTI: '0000000000000001'B
rrc-StateIndicator: cell-FACH
rlc-Re-establishIndicatorRb2-3or4: FALSE
rlc-Re-establishIndicatorRb5orAbove: FALSE
modeSpecificTransChInfo
fdd
modeSpecificPhysChInfo
fdd

DCH Allocation
Node-B

UE

RNC

Measurement Report (RACH)

RRC
Measured Result

Traffic Volume
Measured Result List

event: e4a

Traffic Volume
Event Identity

DPCH UL Scram. & Chan. code


Transport Ch DCH IDs

C-NBAP

RRC

Radio Bearer Identity num.


RLC Buffer Payload

SRNC

easured Result on RACHMeasurement Quantity


Event Result

CN

Admission Control
In dB CPICH_Ec/No

Radio Link Set up


Request

Collects Radio Ch
Parameters
Select Transport Ch IDs
C-NBAP

Radio link ID & Cell ID


Transport Ch DCH IDs

DPCH Power ctrl info

Binding ID

HS-DSCH MAC flow ctrl info

Transport Layer Address

Node-B

Dig Analysis Route find


ATM CAC

Path id & CID selection

Radio Ch set up
AAL2 TP Selection

SRNC

C-NBAP

Radio Link Set up


Response

C-NBAP

Measurement Report Message


MEASUREMENT REPORT

TrafficVolumeMeasuredResults

UL-DCCH-Message

rb-Identity: 3

integrityCheckInfo

rlc-BuffersPayload: pl0

messageAuthenticationCode: '11001011100111101...
rrc-MessageSequenceNumber: 6
message
measurementReport

TrafficVolumeMeasuredResults
rb-Identity: 4
rlc-BuffersPayload: pl0
TrafficVolumeMeasuredResults

measurementIdentity: 4

rb-Identity: 5

measuredResults

rlc-BuffersPayload: pl512

trafficVolumeMeasuredResultsList
TrafficVolumeMeasuredResults
rb-Identity: 1
rlc-BuffersPayload: pl0
TrafficVolumeMeasuredResults
rb-Identity: 2
rlc-BuffersPayload: pl0

measuredResultsOnRACH
currentCell
modeSpecificInfo
fdd
measurementQuantity
cpich-Ec-N0: 44
eventResults
trafficVolumeEventResults
ul-transportChannelCausingEvent
rachorcpch: NULL
trafficVolumeEventIdentity: e4a

- nrOfTransportBlocks: 3

- transportBlockSize: 336
Radio Link Set up Request Message
-----RADIO LINK SETUP REQUEST [FDD] - nrOfTransportBlocks: 1
NBAP-PDU
- transportBlockSize: 148
----------------

RadioLinkSetupRequestFDD
------

- transportBlockSize: 336

------ transmissionTimeInterval: msec-40

-messageDiscriminator: common
------

- nrOfTransportBlocks: 4

dl-TransportFormatSet

-----dl-TransportFormatSet

------

CRNC-CommunicationContextID: 1236

- nrOfTransportBlocks: 1

------

- transportBlockSize: 148

UL-DPCH-Information-RL-SetupRqstFDD

mode

- transmissionTimeInterval: msec-20

dynamicParts
- nrOfTransportBlocks: 0
------

- transmissionTimeInterval: msec-10
----------- uL-ScramblingCodeNumber: 1000212
- transmissionTimeInterval: msec-40 RL-InformationList-RL-SetupRqstFDD
---------------- minUL-ChannelisationCodeLength: v16
DCH-FDD-InformationItem
- rL-ID: 1
----------- c-ID: 3
DL-DPCH-Information-RL-SetupRqstFDD
- dCH-ID: 1
-----DCH-FDD-Information
ul-TransportFormatSet
- dl-ScramblingCode: 0
DCH-FDD-InformationItem
------ fdd-DL-ChannelisationCodeNumber:
- dCH-ID: 24
- nrOfTransportBlocks: 1
- initialDL-transmissionPower: -180
ul-TransportFormatSet
- transportBlockSize: 336
- maximumDL-power: -71
- nrOfTransportBlocks: 0
------ minimumDL-power: -180
------ nrOfTransportBlocks: 2
------ transportBlockSize: 336
hSDSCH-MACdFlows-Information
ul-ScramblingCode

------

------

dCH-InformationResponse
------

Radio Link Set up Response- dCH-ID: 24


------ bindingID: '00000009'H
RADIO LINK SETUP RESPONSE [FDD]
NBAP-PDU

-----49 00 00 10 20 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
------

------

- dCH-ID: 1

- messageDiscriminator: common
------

- bindingID: '00000004'H

RadioLinkSetupResponseFDD
------

-----CRNC-CommunicationContextID: 1236

49 00 00 10 20 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
------

-----NodeB-CommunicationContextID: 160001

hsDSCH-MACdFlow-Specific-InformationResp
------

------

- hsDSCHMacdFlow-Id: 0

RL-InformationResponseItem-RL-SetupRspFDD
-------

------ rL-ID: 1

- bindingID: '00000006'H

- contents (in bits): 00001


- rL-Set-ID: 1
- contents (in bits): 00001
- received-total-wide-band-power: 69
------

-----49 00 00 10 20 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
-----hsSCCH-Specific-Information-ResponseFDD
-----HSSCCH-Codes
------ codeNumber: 4

Establish Request Message


ERQ - ESTABLISH REQUEST

- Discard parameter
OSAID-Orig. sign. assoc. ident.
DAID-Dest. sign. assoc. ident.: 00000000
General action:
- Parameter's Compatibility: 00h
- Message's Compatibility: 00h
- Do not send notification
Pass-on not possible:
Pass-on not possible:
- Pass on message or parameter
- Do not send notification
- Do not send notification
Parameter length: 20 (14h)
- Pass on message or parameter
- Pass on message or parameter
- Address: 4900001020....FFF
General action:
General action:
LC-Link Charactreristics
- Do not send notification
- Do not send notification
- Parameter's Compatibility: 00h
- Pass on message or parameter
- Pass on message or parameter
Pass-on not possible:
Parameter length: 4 (04h)
CEID-Connection element ident.
- Do not send notification
- Signalling association identifier: 44F2900
- Parameter's Compatibility: 00h
- Pass on message or parameter
SUGR-Served user gen. reference
Pass-on not possible:
General action:
- Parameter's Compatibility: 00h
- Do not send notification
- Do not send notification
Pass-on not possible:
- Pass on message or parameter
- Pass on message or parameter
- Do not send notification
General action:
Parameter length: 12 (0Ch)
- Pass on message or parameter
- Do not send notification
- Maximum forward CPS-SDU bit rate: 82 (52h) General action:
- Pass on message or parameter
- Maximum backwards CPS-SDU bit rate: 84 (54h)
- Do not send notification
Parameter length: 5 (05h)
- Average forward CPS-SDU bit rate: 23 (17h) - Pass on message or parameter
- Path identifier: 1021 (3FDh)
- Average backwards CPS-SDU bit rate: 25 (19h)Parameter length: 4 (04h)
- Channel identifier: 20 (14h)
- Maximum forward CPS-SDU size: 24 (18h)
- Field: 00000009
NSEA-Dest. NSAP serv. endpoint addr.
- Maximum backwards CPS-SDU size: 26 (1Ah)
-Parameter's Compatibility: 10h
- Average forward CPS-SDU size: 24 (18h)
Pass-on not possible:
- Average backwards CPS-SDU size: 26 (1Ah)
- Do not send notification

Establish Confirm Message


ECF - ESTABLISH CONFIRM
DAID-Dest. sign. assoc. ident.: 44F29000
- Message's Compatibility: 00h
Pass-on not possible:
- Do not send notification
- Pass on message or parameter
General action:
- Do not send notification
- Pass on message or parameter
OSAID-Orig. sign. assoc. ident.
- Parameter's Compatibility: 00h
Pass-on not possible:
- Do not send notification
- Pass on message or parameter
General action:
- Do not send notification
- Pass on message or parameter
Parameter length: 4 (04h)
- Signalling association identifier: 0000000E

Establish Request Message


ERQ - ESTABLISH REQUEST
DAID-Dest. sign. assoc. ident.:
00000000
- Message's Compatibility: 00h
Pass-on not possible:
- Do not send notification
- Pass on message or parameter
General action:
- Do not send notification
- Pass on message or parameter
CEID-Connection element ident.
- Parameter's Compatibility: 00h
Pass-on not possible:
- Do not send notification
- Pass on message or parameter
General action:
- Do not send notification
- Pass on message or parameter
Parameter length: 5 (05h)
- Path identifier: 1021 (3FDh)

General action:

- Do not send notification


- Pass on message or parameter

-----Parameter length: 4 (04h)


- Signalling association identifier:
44F29100
SUGR-Served user gen. reference

Parameter length: 20 (14h)

- Parameter's Compatibility: 00h

- Parameter's Compatibility: 00h

General action:

Pass-on not possible:

- Do not send notification

- Do not send notification

- Pass on message or parameter

- Pass on message or parameter

Parameter length: 4 (04h)

General action:

- Field: 00000004

- Do not send notification

SSISU-Ser. spec. info (SAR-unassured)

- Pass on message or parameter

- Parameter's Compatibility: 00h

Parameter length: 12 (0Ch)

Pass-on not possible:

- Maximum forward CPS-SDU bit rate: 10 (Ah)

- Do not send notification

Pass-on not possible:


- Address:
4900001020FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF - Do not send notification
- Pass on message or parameter
LC-Link Charactreristics

- Maximum backwards CPS-SDU bit rate: 1102 - Pass on message or parameter


(44Eh)
General action:
- Average forward CPS-SDU bit rate: 2 (2h)
- Do not send notification
- Average backwards CPS-SDU bit rate: 1094
(446h)

- Pass on message or parameter

Parameter length: 7 (07h)


- Maximum forward CPS-SDU size: 3 (3h)
- Max length of SSAR-SDU forwards: 0
NSEA-Dest. NSAP serv. endpoint addr.- Maximum backwards CPS-SDU size: 45 (2Dh)
(0h)
-Parameter's Compatibility: 10h
- Average forward CPS-SDU size: 1 (1h)
- Max length of SSAR-SDU backwards:
Pass-on not possible:
175 (AFh)
-Average backwards CPS-SDU size: 43 (2Bh)
- Do not send notification
- Transmission error detection disabled
OSAID-Orig. sign. assoc. ident.
- Channel identifier: 21 (15h)

Establish Confirm
ECF - ESTABLISH CONFIRM
DAID-Dest. sign. assoc. ident.: 44F29100
- Message's Compatibility: 00h
Pass-on not possible:
- Do not send notification
- Pass on message or parameter
General action:
- Do not send notification
- Pass on message or parameter
OSAID-Orig. sign. assoc. ident.
- Parameter's Compatibility: 00h
Pass-on not possible:
- Do not send notification
- Pass on message or parameter
General action:
- Do not send notification
- Pass on message or parameter
Parameter length: 4 (04h)
- Signalling association identifier: 00000011

Establish Request Message


ERQ - ESTABLISH REQUEST

- Discard parameter

OSAID-Orig. sign. assoc. ident.

DAID-Dest. sign. assoc. ident.:


00000000

General action:

- Parameter's Compatibility: 00h

- Do not send notification

Pass-on not possible:

- Message's Compatibility: 00h

- Pass on message or parameter

- Do not send notification

Pass-on not possible:

Parameter length: 20 (14h)

- Pass on message or parameter

- Do not send notification

- Address: 4900001020....FFFFFFFF

General action:

- Pass on message or parameter

LC-Link Charactreristics

- Do not send notification

General action:

- Parameter's Compatibility: 00h

- Pass on message or parameter

- Do not send notification

Pass-on not possible:

Parameter length: 4 (04h)

- Pass on message or parameter

- Do not send notification

CEID-Connection element ident.

- Pass on message or parameter

- Signalling association identifier:


44F29200

- Parameter's Compatibility: 00h

General action:

SUGR-Served user gen. reference

Pass-on not possible:

- Do not send notification

- Parameter's Compatibility: 00h

- Do not send notification

- Pass on message or parameter

Pass-on not possible:

- Pass on message or parameter

Parameter length: 12 (0Ch)

- Do not send notification

General action:

- Maximum forward CPS-SDU bit rate: 0 (0h)

- Pass on message or parameter

- Do not send notification

General action:

- Pass on message or parameter

- Maximum backwards CPS-SDU bit rate: 24


(18h)

Parameter length: 5 (05h)

- Average forward CPS-SDU bit rate: 0 (0h)

- Pass on message or parameter

- Path identifier: 1021 (3FDh)

- Average backwards CPS-SDU bit rate: 2 (2h)

Parameter length: 4 (04h)

- Channel identifier: 22 (16h)

- Maximum forward CPS-SDU size: 1 (1h)

- Field: 00000006

NSEA-Dest. NSAP serv. endpoint addr. - Maximum backwards CPS-SDU size: 6 (6h)
- Average forward CPS-SDU size: 1 (1h)
-Parameter's Compatibility: 10h
Pass-on not possible:
- Do not send notification

- Average backwards CPS-SDU size: 6 (6h)

- Do not send notification

Establish Confirm
ECF - ESTABLISH CONFIRM
DAID-Dest. sign. assoc. ident.: 44F29200
- Message's Compatibility: 00h
Pass-on not possible:
- Do not send notification
- Pass on message or parameter
General action:
- Do not send notification
- Pass on message or parameter
OSAID-Orig. sign. assoc. ident.
- Parameter's Compatibility: 00h
Pass-on not possible:
- Do not send notification
- Pass on message or parameter
General action:
- Do not send notification
- Pass on message or parameter
Parameter length: 4 (04h)
- Signalling association identifier: 0000000D

Node-B

UE

RNC

Measurement Control (DPCH)

RRC
It defines the target DCH where
to measure the traffic volume

RRC

Traffic Vol. Meas. Object List


Traffic Volume Report Quantity

It defines the type of quantity. In


that case RLC buffer.

UE state
e.g.

UE state: Cell DCH, Cell FACH....

Event ID & Reporting threshold

Event type: e4a, e4b....&


threshold for the RLC buffer in
KB/s

CN

HS-DSCH

Capacity Allocation

HS-DSCH

CmCH-PI
The Common
Transport Channel
Priority Indicator IE
indicates the priority
of the data frame
Indicates the users buffer
size (i.e. the amount of data
in the buffer in the SRNC)

Maximum MAC PDU Length


HS-DSCH credits
e.g.
CmCH-PI
User Buffer Size
HS-DSCH

Capacity Request

Maximum MAC-d PDU


length
It indicates the
number of MAC-d
PDUs that the RNC is
allowed to transmit for
the MAC-d flow
HS-DSCH

Measurement Control

trafficVolumeMeasQuantity
rlc-BufferPayload: NULL

MEASUREMENT CONTROL

trafficVolumeReportingQuantity

DL-DCCH-Message

rlc-RB-BufferPayload: TRUE

integrityCheckInfo

rlc-RB-BufferPayloadAverage: FALSE

messageAuthenticationCode:
'01000100110001010011011101101100'B
rrc-MessageSequenceNumber: 9
message
measurementControl
later-than-r3
rrc-TransactionIdentifier: 0
criticalExtensions
r4
measurementControl-r4
measurementIdentity: 2
measurementCommand
setup
trafficVolumeMeasurement
trafficVolumeMeasurementObjectList
UL-TrCH-Identity
dch: 1

rlc-RB-BufferPayloadVariance: FALSE
measurementValidity
ue-State: cell-DCH
reportCriteria
trafficVolumeReportingCriteria
transChCriteriaList
TransChCriteria
ul-transportChannelID
dch: 1
eventSpecificParameters
TrafficVolumeEventParam
eventID: e4a
reportingThreshold: th1024
timeToTrigger: ttt0
pendingTimeAfterTrigger: ptat2
measurementReportingMode
measurementReportTransferMode:
acknowledgedModeRLC
periodicalOrEventTrigger: eventTrigger

Capacity Allocation / Request


e.g. credits =12
HS-DSCH CAPACITY ALLOCATION

HS-DSCH CAPACITY REQUEST

Control Frame CRC : 75 (4Bh)

Control Frame CRC : 50 (32h)

Control Frame Type : 11 (0Bh)

Control Frame Type : 10 (0Ah)

CmCH-PI : 15 (Fh)

CmCH-PI : 15 (Fh)

Maximum MAC-d PDU Length : 336 bit(s)

User Buffer Size : 3108 (0C24h) octets

HS-DSCH Credits : 12 (00Ch)


HS-DSCH Interval : 10 ms
HS-DSCH Repetition Period : 0 (00h) (unlimited repetition
period)
e.g. credits =0
HS-DSCH CAPACITY ALLOCATION
Control Frame CRC : 45 (2Dh)
Control Frame Type : 11 (0Bh)
CmCH-PI : 15 (Fh)
Maximum MAC-d PDU Length : 336 bit(s)
HS-DSCH Credits : 0 (000h) (stop transmission)
HS-DSCH Interval : 10 ms
HS-DSCH Repetition Period : 0 (00h) (unlimited repetition
period)

Node-B

UE

RNC

Radio Bearer Reconfiguration (FACH)

RRC

Status for the UE. Options:


Cell DCH, Cell FACH, Cell PCH,
URA PCH
Radio Bearer to configure, with
the relative transport & logical
Channel
DPCH UL & DL spreading factor,
scramb. code & power
information
Primary CPICH scramb. code info

RRC

RRC state indicator


RBs and associated Log.& Trans. Ch ID
UL & DL DPCH scramb.
e.g. codes & SF
CPICH scramb. code info

UE
Open Radio CH
Configure RBs &
Log. CH
RRC

Cell DCH status

Radio Bearer Reconfiguration Complete (DPCH)


RNC
RNC starts traffic
conn.

RRC

CN

Radio Bearer Reconfiguration


RADIO
BEARER RECONFIGURATION [DCCH]rb-Identity: 2
(1/2)
DL-DCCH-Message

dch: 24
-----ul-TransportChannelType

------

------

rach: NULL

ul-AM-RLC-Mode
rrc-StateIndicator: cell-DCH

------

------

------

dl-TransportChannelType

dl-AM-RLC-Mode-r5
rrc-TransactionIdentifier: 3

fach: NULL

-----ul-TransportChannelType

rb-Identity: 1
------

dch: 24

dl-AM-RLC-Mode-r5
ul-TransportChannelType

ul-TransportChannelType

dl-TransportChannelType

dch: 24
-----dl-TransportChannelType

fach: NULL

dch: 24

------

------

rb-Identity: 3

-----ul-TransportChannelType

------

rach: NULL

rach: NULL

ul-AM-RLC-Mode
------

-----dl-TransportChannelType
fach: NULL

ul-TransportChannelType

-----dl-TransportChannelType

------

------

rach: NULL

------

ul-TransportChannelType

------

------

------

dch: 24

ul-AM-RLC-Mode

dl-TransportChannelType

------

dch: 24

rb-Identity: 4
------

------

dl-UM-RLC-Mode-r5

------

dch: 24

ul-UM-RLC-Mode

-------

dl-TransportChannelType

dl-TransportChannelType

dl-AM-RLC-Mode-r5

fach: NULL

-----ul-TransportChannelType
dch: 24

------

Radio Bearer Reconfiguration


(2/2)
rb-Identity: 5
------

dl-AddReconfTransChInfoList
ul-AM-RLC-Mode

------

DLAddReconfTransChInformation-r5
dl-TransportChannelType

dl-AM-RLC-Mode-r5

dch: 24

-----ul-TransportChannelType

-----dch-QualityTarget

dch: 1

bler-QualityValue: -20

-----dl-TransportChannelType
hsdsch: 0

DLAddReconfTransChInformation-r5
dl-TransportChannelType

ul-CommonTransChInfo
-----ul-AddReconfTransChInfoList

-----dch-QualityTarget
bler-QualityValue: -20
ul-ChannelRequirement

ul-TransportChannelType: dch

ul-DPCH-Info

transportChannelIdentity: 24
------

scramblingCode: 1000212

ULAddReconfTransChInformation

spreadingFactor: sf16

ul-TransportChannelType: dch -----transportChannelIdentity: 1


dl-HSPDSCH-Information
------

------dl-CommonTransChInfo

dl-DPCH-InfoCommon
-----sfd256: pb4
-----primaryCPICH-Info
primaryScramblingCode: 54
-----dl-DPCH-InfoPerRL

hsdsch: NULL

ULAddReconfTransChInformation

------

dl-CommonInformation

HS-SCCH-Codes: 4

fdd
pCPICH-UsageForChannelEst:
mayBeUsed
-----sf-AndCodeNumber
sf256: 10
------

Radio Bearer Reconfiguration Complete

RADIO BEARER RECONFIGURATION COMPLETE


UL-DCCH-Message
integrityCheckInfo
messageAuthenticationCode:
'10111011101100101110110100001011'B
rrc-MessageSequenceNumber: 7
message
radioBearerReconfigurationComplete
rrc-TransactionIdentifier: 3

Physical Shared Channel Reconfiguration


(1/3)

Physical Shared Channel Reconfiguration


(2/3)
PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST [FDD]
NBAP-PDU

PhysicalSharedChannelReconfigurationRequestFDD
- extension flag: 0
- preamble: 0
protocolIEs
- padding: 000000
- length: 00 05
- id: 25
- contents: 00 19
- criticality: reject
- contents (in bits): 00
- padding: 000000
- opentype length: 02
C-ID: 1
- contents: 00 01
- id: 43
- contents: 00 2B
- criticality: reject
- contents (in bits): 00
- padding: 000000
- opentype length: 01
ConfigurationGenerationID: 2
- contents: 02
- id: 522
- contents: 02 0A
- criticality: reject
- contents (in bits): 00
- padding: 000000
- opentype length: 02

...

Physical Shared Channel Reconfiguration


Messages (3/3)
MaximumTransmissionPower: 378
- contents: 01 7A
- id: 524
- contents: 02 0C
- criticality: reject
- contents (in bits): 00
- padding: 000000
- opentype length: 02
HS-PDSCH-FDD-Code-Information
- extension flag: 0
- preamble: 10
- number-of-HS-PDSCH-codes: 5
- contents (in bits): 0101
- hS-PDSCH-Start-code-number: 11
- contents (in bits): 1010
- trailing bits: 00000
- id: 525
- contents: 02 0D
- criticality: reject
- contents (in bits): 00
- padding: 000000
- opentype length: 02
HS-SCCH-FDD-Code-Information
- extension flag: 0
- choice index: 0
replace
- length (in bits): 00000
- HS-SCCH-FDD-Code-Information-Item: 4
- contents (in bits): 0000100
- trailing bits: 00

PS Call Setup

RRC Connection Setup Complete Message


RRC CONNECTION SETUP COMPLETE
UL-DCCH-Message
message
rrcConnectionSetupComplete
...
physicalChannelCapability
...
ue-RadioAccessCapability-v590ext
dl-CapabilityWithSimultaneousHS-DSCHConfig: kbps64
pdcp-Capability-r5-ext
supportForRfc3095ContextRelocation: FALSE
rlc-Capability-r5-ext
physicalChannelCapability
fdd-hspdsch
supported
hsdsch-physical-layer-category: 12
supportOfDedicatedPilotsForChannelEstimationOfHSDSCH: FALSE
simultaneousSCCPCH-DPCH-HSDSCH-Reception: FALSE
tdd384-hspdsch
unsupported: NULL
tdd128-hspdsch
unsupported: NULL
multiModeRAT-Capability-v590ext
supportOfUTRAN-ToGERAN-NACC: FALSE

Radio Bearer Setup

Radio Bearer Setup/Reconfiguration


RADIO BEARER RECONFIGURATION [DCCH]

rb-MappingInfo

DL-DCCH-Message
...
radioBearerReconfiguration-r5
new-H-RNTI: '10011011 11001111'B
rrc-StateIndicator: cell-DCH
...

rt120

RB-MappingOption-r5
ul-LogicalChannelMappings
oneLogicalChannel
ul-TransportChannelType
dch: 1
rlc-SizeList
configured: NULL
mac-LogicalChannelPriority:
dl-LogicalChannelMappingList
DL-LogicalChannelMapping-r5
dl-TransportChannelType
hsdsch: 0
DL-AddReconfTransChInformation-r5
dl-TransportChannelType
hsdsch: NULL
tfs-SignallingMode
hsdsch
harqInfo
numberOfProcesses: 6
memoryPartitioning
implicit: NULL

addOrReconfMAC-dFlow

mac-hsQueueId: 0

(1/2)

mac-hs-AddReconfQueue-List
MAC-hs-AddReconfQueue
mac-dFlowId: 0

reorderingReleaseTimer:
mac-hsWindowSize: mws16
mac-d-PDU-SizeInfo-List
MAC-d-PDUsizeInfo

mac-d-PDU-Size: 336

mac-d-PDU-Index: 0
...
dl-HSPDSCH-Information
hs-scch-Info
modeSpecificInfo
fdd
hS-SCCHChannelisationCodeInfo
HS-SCCH-Codes: 4
measurement-feedback-Info
modeSpecificInfo
fdd
measurementPowerOffset: 9
feedback-cycle: fc4
cqi-RepetitionFactor: 1
deltaCQI: 4
modeSpecificInfo
fdd: NULL

Radio Bearer Setup/Reconfiguration


dl-InformationPerRL-List
DL-InformationPerRL-r5
modeSpecificInfo
fdd
primaryCPICH-Info
primaryScramblingCode: 30
servingHSDSCH-RL-indicator: TRUE
dl-DPCH-InfoPerRL
fdd
pCPICH-UsageForChannelEst: mayBeUsed
dpch-FrameOffset: 80
dl-ChannelisationCodeList
DL-ChannelisationCode
sf-AndCodeNumber
sf256: 10
tpc-CombinationIndex: 0

(2/2)

Capacity Allocation

HS-DSCH Capacity Request


HS-DSCH CAPACITY REQUEST
Control Frame CRC : 63 (3Fh)
Control Frame Type : 10 (0Ah)
CmCH-PI : 15 (Fh)
User Buffer Size : 42 (002Ah) octets

The HS-DSCH Capacity Request procedure provides means for the CRNC to request HSDSCH capacity by indicating the user buffer size in the CRNC for a given priority level.
The CRNC is allowed to reissue the HS-DSCH Capacity Request if no CAPACITY
ALLOCATION has been received within an appropriate time threshold.
HS-DSCH Capacity Request is sent for each priority group to indicate the user buffer size.
The control frame is sent by the HS-DSCH CAPACITY REQUEST is sent for each priority
group to indicate the user buffer size.

HS-DSCH Capacity Allocation & HS-DSCH Data


Frame
HS-DSCH CAPACITY ALLOCATION
Control Frame CRC : 76 (4Ch)
Control Frame Type : 11 (0Bh)
CmCH-PI : 15 (Fh)
Maximum MAC-d PDU Length : 336 bit(s)
HS-DSCH Credits : 4 (004h)
HS-DSCH Interval : 10 ms
HS-DSCH Repetition Period : 0 (00h) (unlimited repetition period)

HS-DSCH DATA FRAME


Header CRC : 15 (0Fh)
CmCH-PI : 15 (Fh)
MAC-d PDU Length : 336 bit(s)
NumOfPDU : 3 (03h)
User Buffer Size : 36920 (9038h) octets
MAC-d PDU
1. MAC-d PDU
80 90 16 2E 27 1F 00 C8 E0 48 14 2D E0 A9 11 0F 61 49 F8 42 7B 1E 38 80
DF 4C 80 70 09 87 10 8A 4A B0 48 8C 05 81 29 04 ED 11
2. MAC-d PDU
80 98 26 C0 1C D8 30 13 E8 4A 7C 03 22 C1 23 02 13 26 C6 29 C3 01 1E 05
81 89 D9 18 19 08 44 3E 40 06 34 EB 12 84 44 E9 1B 8C
3. MAC-d PDU
80 A0 21 E0 05 F0 F4 4E 02 00 28 00 44 2A 98 70 38 84 85 52 44 BC 52 51
7C FC 14 95 F4 41 55 48 0A A1 58 F1 22 0B 7F 0B 38 25
Spare Extension
Payload CRC : 32680 (7FA8h)

DCH to HS-DSCH switch

Active set size=1 after this


Active Set Update (no SHO
anymore). Resumption timer
started.

Application throughput
1500000
1000000
bps

Resumption timer started


when Active set size =1.
Resumption timer value in
this case 4s.
Switching to HS-DSCH tried
after the timer expires.

HS-DSCH

DCH NRT

500000
0
0

EventId

Time

10

20

Subchannel

Message

30

40

50

RRCD

08:24.8

DCCH

"ACTIVE_SET_UPDATE"

RRCU

08:24.8

DCCH

"ACTIVE_SET_UPDATE_COMPLETE"

RB reconfiguration to DCH0/0.

RRCD

08:25.1

DCCH

"MEASUREMENT_CONTROL"

4s resumption timer applied


before.
~2.5 seconds gap according
signaling. The data gap is
about 6s when measured with
Ethereal.

RRCD

08:29.3

DCCH

"RADIO_BEARER_RECONFIGURATION"

RRCU

08:30.5

DCCH

"RADIO_BEARER_RECONFIGURATION_COMPLETE"

RRCD

08:30.7

DCCH

"MEASUREMENT_CONTROL"

RRCU

08:30.7

DCCH

"MEASUREMENT_REPORT"

RRCD

08:31.7

DCCH

"RADIO_BEARER_RECONFIGURATION"

RRCU

08:32.8

DCCH

"MEASUREMENT_REPORT"

RRCU

08:32.8

DCCH

"RADIO_BEARER_RECONFIGURATION_COMPLETE"

RRCD

08:33.1

DCCH

"MEASUREMENT_CONTROL"

RB reconfiguration to HS-DSCH

You might also like