06 - HSDPA Call Setup - v2

HSDPA Call Setup
2006 Nokia
HSDPA Call Setup / Kittipong Thamapa
HSDPA Call Setup

Review of HSDPA
HSDPA Call Setup
Radio Resource Control Messages
2006 Nokia
Review of HSDPA
2006 Nokia
Physical Channels for One HSDPA UE

Associated DPCH, Dedicated Physical Channel
DPCH needed for each HSDPA UE. Signalling, uplink data.
BTS
HS-PDSCH: High-Speed Physical Downlink Shared Channel Associated DPCH Associated DPCH 1-15 x HS-PDSCH 1-4 x HS-SCCH HS-DPCCH
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.
2006 Nokia
In the slide are shown new Physical channel introduced with the HSDPA: Associated DPCH is a combination of DCCH & DTCH logical channels. Actually the information carried over DPCH are RRC messages UL & DL and RLC + TCP Ack UL toward respectively the RNC and HTTP server. HS-PDSCH is the high speed channel in DL carrying TCP-IP traffic to the UE. This channel is shared among all the users located in the same cell that need to have HSDPA traffic. HS-SCCH contains information necessary to decode , from the UE point of view, the contents of the HS-PDSCH channel. As this information are generated in the BS by MAChs,it is not mapped in the transport channel. HS-DPCCH contains information like Ack/Nack generated by the UE in order to manage retransmission between Node B and UE.CQI information are necessary to manage the speed of the connection in the air interface i.e. number of code per UE, type of modulation QPSK or QAM and TBS ( transport block size ).
HSDPA Layer 1 channels
2006 Nokia
High speed downlink shared channel (HS-DSCH) carries the user data in the downlink direction, with the peak rate reaching up to 10 Mbps. High speed shared control channel (HS-SCCH) carries the necessary physical layer control information to enable decoding of the data on HS-DSCH Only one HS-SCCH needed if only time multiplexing is used. Time multiplexing means that 1 time slot of HS-PDSCH can be used by only one user per time. DCH always running in parallel. That channel is necessary to carry UL & DL RRC messages and UL RLC & TCP ack.
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 transportformat combination indicator (TFCI).
2006 Nokia
The UL DPCCH and UL HS-DPCCH channel carry information generated at L1.Note that these are DEDICATED physical channel. Only the UL DPDCH carry information generated at L2 or above.
Ref spec. ( 25211.580 )
Uplink Physical Layer

c d ,1 DPDCH1 c d ,3 DPDCH3 c d ,5 DPDCH5 I+ jQ S d d d
DPDCH
Data Ndata bits Tslot = 2560 chips, Ndata = 10*2k bits (k=0..6)
DPCCH
Pilot Npilot bits
TFCI NTFCI bits Tslot = 2560 chips, 10 bits
FBI NFBI bits
TPC NTPC bits
S dp ch,n c hs hs
H S -D P C C H
(If N m ax-dpdc h m od 2 = 0 )
Slot #0
Slot #1
Slot #i 1 radio frame: Tf = 10 ms
Slot #14
c d ,2 DPDCH2 c d ,4 DPDCH4 c d ,6 DPDCH6 cc DPCCH c hs H S -D P C C H

(If N m ax-dpdc h m o d 2 = 1 )
Frame structure for uplink DPCCH

d
Tslot = 2560 chips

d
2Tslot = 5120 chips CQI
HARQ-ACK
j
One HS-DPCCH subframe (2 ms)
hs
Subframe #0
Subframe #i One radio frame Tf = 10 ms
Subframe #4
Spreading for uplink DPCCH, DPDCHs and HS-DPCCH
Frame structure for uplink HS-DPCCH
2006 Nokia
Ref spec 25213.560 Uplink physical channel mapping.( UE side ) Ref spec 25211.580 DPCCH and HS-DPCCH physical channel contain only L1 information. Only DPDCHs channel contain information generated at L2 or above. That information are organised in Transport Blocks that can have different size.
Transport /Physical Channels mapping (UL example)

Ue Side
TrCH x
Transport Block
Higher Layers UTRAN:MAC / FP TB & Error Indication TB & Error Indication
BS Side
TrCH y
TB & Error Indication
Transport Block TFI Transport Block TFI
Transport Block
TFI
TFI
TB & Error Indication
TFCI
Coding & Multiplexing
Physical Layer BTS L1
TFCI decoding
DeCoding & De-Multiplexing
Physical Control Channel

DPCCH
Physical Data Channel

DPDCH
Physical Control Channel

DPCCH
Physical Data Channel

DPDCH
2006 Nokia
Each Transport Channel in Iub is carried using the Frame Protocol. TFI means Transport Format Indicator, in fact to have different Transport Format means that is possible to vary the Transport Block size and TTI ( Time Interval between two Transport Blocks ). It is very important to notice that TFCI information in the slide together with TPC , Pilots Bits... are generated and terminated at Layer 1, so no transport channel in Iub are dedicated to DPCCH channels.
Downlink Physical Channel

Dedicated downlink physical channels
(1/2)
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.
2006 Nokia
Ref spec 25211.580 Downlink physical channels are HS-DSCH, HS-SCCH ( shared among all the users ) and DPCH ( dedicated to only one user ). DPCH channel in downlink is used to carry RRC messages, control information for power control and TFCI to decode the data part. Data part includes DCCH logical channel for RRC messages, DTCH logical channel for RLC and TCP-IP ack and eventually speech connection to associate with HSDPA download

Common downlink physical channels
(2/2)
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.
10
2006 Nokia

DPDCH
Different downlink Physical channels (point S in Figures 8) G1
DPCCH TPC NTPC bits TFCI NTFCI bits
DPDCH Data2 Ndata2 bits
DPCCH Pilot Npilot bits
Data1 Ndata1 bits
Tslot = 2560 chips, 10*2k bits (k=0..7)

G2
P-SCH GP S-SCH GS
(point T in Figure 11)
Slot #0
Slot #1
Slot #i One radio frame, Tf = 10 ms
Slot #14
Combining of downlink physical channels

Data Ndata 1 bits Tslot = 2560 chips, M*10*2 bits (k=4)
k
Frame structure for downlink DPCH

Data Ndata1 bits Tslot = 2560 chips, 40 bits
Slot #0
Slot#1 1 subframe: Tf = 2 ms
Slot #2
Slot #0
Slot#1 1 subframe: Tf = 2 ms
Slot #2
Subframe structure for the HS-PDSCH
Subframe structure for the HS-SCCH
11
2006 Nokia
Ref spec 25213.560 DPCCH part of the DPCH channel is generated at Layer 1 and DPCH part is generated at Layer 2 or above.Olso in this case information inside DPDCH channel are organised ion Transport Blocks associated with TFI.
HSDPA Protocol Architecture

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

HS-DSCH
RLC MAC-d MAC-hs PHY BTS HS-DSCH FP TNL Iub

MAC-d flow
HS-DSCH FP TNL RNC
HS-PDSCH
Uu
12
2006 Nokia
MAC Architecture
Handles common channels Handles high speed channels
MAC Control PCCH BCCH CCCH CTCH SHCCH
TDD only
MAC Control
DCCH DTCH MAC Control
DTCH
Handles dedicated channels
Configuration without MAC-c/sh Configuration with MAC-c/sh
MAC-d
MAC-hs
BS
Configuration with MAC-c/sh
MAC-c/sh
RNC
RNC
HS-DSCH HS-DSCH Associated Downlink Signalling
Iub
PCH FACH FACH
RACH
USCH
TDD only
USCH
TDD only
DSCH DSCH
TDD only TDD only
Associated Uplink Signalling
Iur or local
DCH
DCH
HS-PDSCH HS-SCCH HS-SCCH DL SF 128 HS-PDSCH DL n codes x SF 16 HS-DPCCH HS-DPCCH UL SF 256
Physical Layer
DPCH ( UL+DL rrc messages (DCCH) ) DPCH DL SF 256
DPCH ( UL RLC+TCPIP ack (DTCH) ) DPCH UL SF 16
13
2006 Nokia
Ref spec 25321 With the introduction of HSDPA , new MAC hs protocol has been included in the BS. It manages HS-SCCH, HS-PDSCH and HS-DPCCH channels, moreover flow control information, HS-PDSCH channelisation code, HS-PDSCH modulation type and retransmission in the Uu interface. Because of that MAC hs includes new packet scheduler and HARQ protocol. MAC c is the same protocol used in release 99 , necessary to manage Common Channel like PCH, FACH, RACH etc. MAC sh is not implemented because DSCH channel is not supported in current release. This channel allow the user to obtain 2 Mb/s of throughput. MAC d is used to manage DCH channel for RT connection for signalling connection, speech etc. An additional DCH transport channel carried over DPCH is necessary in case voice connection is opened in parallel with HSDPA traffic. Note that in this case the SF of the DPCH will change.
Node B enhancements for HSDPA

RNC Node B Terminals
HARQ & Coding ACK/NACK & Feedback Decoding R99 responsibilities:
Physical layer operations No dymanic decision making
Packets Flow Control
Scheduler & Buffer
New Node B functions for HSDPA:

Sophisticated Scheduler: 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
14
2006 Nokia
Node B enhancements New Sw and HW required to support higher data rates, new channel elements to handle HSDPA channels, increased memory requirements and buffer management. RRM (radio resource management) in HSDPa is dynamic in nature. It involves power management between existing UMTS R99 channels and the new HSDPA channels. SF (spreading factor) space management between UTMS R99 and HSDPA channels.
HS-DSCH code management

PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST [FDD] NBAP-PDU - messageDiscriminator: common PhysicalSharedChannelReconfigurationRequestFDD C-ID: 3 MaximumTransmissionPower: 378 HS-PDSCH-FDD-Code-Information - extension flag: 0 - preamble: 10 - number-of-HS-PDSCH-codes: 5 - hS-PDSCH-Start-code-number: 11 at restart phase RNC BS
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.
15
2006 Nokia
That message is sent during the restart of the BS. This message defines the limits in terms power and codes for the HS-PDSCH, that in this is 5 codes x SF 16.In current release in fact the DL throughput is limited to MAX 1.6 Mb/s per Ue. Note that 5 codes are time/codes multiplexing shared among all the Ue that belong in the same cell and need to get the PS data through the HS-PDSCH. Codes SF 16 number 1-10 are dedicated for different channels.
Retransmissions in HSDPA
Server RNC Node-B
MAC-hs retransmissions
TCP retransmissions RLC retransmissions
UE
16
2006 Nokia
It is important to notice that for HSDPA traffic exist 3 type of retransmission : MAC retransmission is managed by the Node B and Ue. Very fast but limited to Layer 1 RLC retransmission managed by RNC and UE. RLC PDU if not acknowledged by the Ue are retransmitted by the RNC. It work at Layer 2. TCP retransmission is managed by the HTTP server and the Ue. TCP/IP packages are retransmitted in case not acknowledgement is received by the HTTP server form the Ue.
Iub Flow Control messages

HS-DSCH Capacity Request
Node B CRNC
(1/2)
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.
17
2006 Nokia
Trigger: No capacity available for the data waiting in RLC buffers. Parameters: User Buffer Size: Indicates the users' buffer size (i.e. the amount of data in the buffer in the SRNC) in octets for a given Common Transport Channel Priority Indicator level CmCH-PI: The Common Transport Channel Priority Indicator IE indicates the priority of the data frame and the SDUs included which are waiting in the SRNC's Tx buffer for transmission via the HS-DSCH.
Iub Flow Control messages

HS-DSCH Capacity Allocation
Node B CAPACITY ALLOCATION CRNC
(2/2)
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.
18
2006 Nokia
The HS-DSCH CAPACITY ALLOCATION message includes a number of parameters: It indicates the number of MAC-d PDUs that the RNC is allowed to transmit for the MAC-d flow, indicated by the HS-DSCH Credits. The associated priority level indicated by the CmCH-PI. The Maximum MAC-d PDU length, HS-DSCH Credits, indicating the number of MAC-d PDUs that RNC may transmit. HS-DSCH Interval, indicating a time interval during which the HS-DSCH Credits granted may be transmitted. HS-DSCH Repetition Period, indicating the number of subsequent intervals that the HS-DSCH Credits granted may be transmitted. Any capacity previously granted is replaced. If HS-DSCH Credits = 0, the RNC shall immediately stop transmission of MAC-d PDUs. If HS-DSCH Credits = 2047, the RNC can transmit MAC-d PDUs with unlimited capacity. If the HS-DSCH Repetition Period = "unlimited repetition period" it indicates that the RNC may transmit the specified number of MAC-d PDUs for an unlimited period according to the bounds of Maximum MAC-d PDU Length, HS-DSCH Credits and HS-DSCH Interval .
UE RRC status
These are the possible status for a UE in a UMTS network 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. CELL DCH: one of the Connected Mode. The UE is able to send and receive RRC messages DPDCH.
Connected Mode mode

Idle Cell DCH Cell FACH URA PCH Cell PCH
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.
19
2006 Nokia
In IDLE mode the is requested to create a RRC connection before any possible action requested by the RNC or by its self. UE is in Cell DCH every time it needs to perform location update, or answer a paging or in general have a RT connection through the Uu interface. In this status the RNC allocates a DPDCH channel only for that user and the same channel can be used either for only RRC messages or for speech as well. In case of PS connection the RNC activates the inactivity timer parameter. It means that if after a certain time the connection is not utilised the DPDCH channel for that user is released in order to save resources, so the Ue is forced to move the connection over the SCCPCH with the FACH inside. That channel allow the Ue to maintain the RRC connection open and transfer small traffic packages. Note that the SCCPH is a Common channel available for all the Ue located in the same cell. A second inactivity timer is activated by the RNC in case no traffic is sent over the FACH, so in this case the Ue is forced by the RNC to move the RRC connection over the PCH. Actually in this status the user and the RNC can exchange only few messages in order to inform one to each other about the necessity to re-establish strong connection with a different channel.
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
HSDPA resumption timer switches the user from DCH to HS-DSCH, when UE exits SHO area
Cell A Service in HSDPA HS-DSCH coverage

Throughput
HSDPA
Switch to DCH 0/0
Upgrade to e.g. 64 kbps
Upgrade to 128 / 384 kbps
Cell B Switch to HSDSCH
HS-DSCH coverage UE on HS-DSCH

Once the session is in DCH, it remains there until the buffers are empty. After that, HSDPA can be selected
DCH
128kbps or 384kbps according to settings 64kbps
0
20 2006 Nokia HSDPA Call Setup / Kittipong Thamapa
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.
21
2006 Nokia
In order to limits the number of active set in the Ue and in order to manage differently the Hand Over for HSDPA handover, additional groups of parameters are configured.
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
Serving Cell Change switches the user from HS-DSCH to Cell_FACH then back to HS-DSCH
Cell A Service in HSDPA HS-DSCH coverage

Throughput
HSDPA
128kbps or 384kbps according to parameter settings 64kbps
Switching to Cell_FACH within the SHO area
Cell B UE on HS-DSCH
HS-DSCH coverage
DCH
0
The same parameter settings apply for this feature as for the DCH switching no need for re-planning 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 If the user was moved to Cell-FACH because of intra frequency handover no HSDPA user penalty timers are used on Cell-FACH, the user will be immediately switched to a new HSDPA connection when there is a data volume request either from the UE or RNC If the user was moved to Cell-FACH because of low utilization or low throughput then the HSDPA user penalty timers are used on Cell-FACH If the HSDPA user moves to non-HSDPA cell, the user in HO area will be moved to CellFACH. The user will be immediately switched to the DCH of the requested bit rate when there is a data volume request either from the UE or RNC (no need for first DCH 0x0 DCH Initial bit rate DCH Final bit rate)
HSDPA Resumption Timer

HSDPA resumption timer
Waiting time before a DCH to HS-DSCH switch is attempted.
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 is tried after the resumption timer expires (if the Active set size is still 1)
Cell B
HS-DSCH coverage Download complete
DCH
0
This parameter defines the waiting time before a DCH to HS-DSCH switch is attempted. If this timer expires while the conditions for the use of HS-DSCH are still fulfilled, a DCH to HS-DSCH switch is attempted. The value 0 means that a DCH to HS-DSCH switch is attempted immediately (without any delay). The value 255 means that this functionality is not in use.
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 HS-DPCCH DPCH

TS 25.308:
DPCH
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
24
2006 Nokia
HSDPA Call set up
25
2006 Nokia
IDLE Mode Cell DCH transaction

UE Node-B
IDLE MODE
RRC
RNC
SGSN
RRC Connection Request ( RACH )

NBAP NBAP ALCAP
RRC NBAP NBAP ALCAP ALCAP RRC RRC
Radio Link Setup Request (C-NBAP ) Radio Link Setup Response (C-NBAP ) Establish Request (ALCAP) Establish Confirm (ALCAP)
ALCAP RRC RRC
RRC Connection Set Up ( FACH ) RRC Connection Set Up Complete ( DCH ) Cell DCH status
26
2006 Nokia
Ue requests to open an RRC with the RNC. The cause of the request in this case is REGISTRATION. Through the NBAP RADIO LINK SET UP message in the BS is open the DCH that will be necessary to carry RRC messages Establish Request Message books the CID in the BS. RRC Connection Set Up message configures the first 4 Radio Bearer in the Ue in order to be able to send and receive RRC messages. RRC Connection Set Up complete is the first message sent over the DPDCH channel.
Cell DCH HS-DSCH transaction

UE
RRC RRC RRC
(1/2)
RNC
RRC RRC RRC
Node-B
RRC Direct Transfer: Attach request RRC Direct Transfer: Attach accept RRC Direct Transfer: PDP context request
SGSN
Attach request
RANAP RANAP
Authentic. &
Attach accept
RANAP RANAP RANAP RANAP RANAP RANAP
Ciphering
PDP context request RAB assign. request
RRC RRC
Radio Bearer Set Up Radio Bearer Set Up Complete
RRC RRC
RAB assign. response

RANAP RANAP RANAP
RRC RRC RRC

27 2006 Nokia
RRC Direct Transfer: PDP context accept Measurement Control Measurement Report
PDP context accept

RRC RRC RRC RANAP
Ue requests the GPRS attach with the CN. This is a NAS message carried over first RRC and then RANAP Just received the Attach accept message, Ue sends the PDP context request and the CN generates the RAB ASSIGNEMENT REQUEST for the RNC. Inside is included the traffic class allocated by the CN for that user. BACKGROUND and INTERACTIVE trigger the HSDPA. Radio Bearer Set Up open the Radio Bearer number 5 to use for traffic. That Radio Bearer will use the same DPDCH used previously by the Ue to perform GPRS attach, thats why inside this message are not reported parameters like Spreading factor or Scrambling code. RNC, configured the RAB confirms to the CN with RAB ASSIGNEMENT RESPONSE and the CN confirms to the Ue the activation of the PDP context. Measurement Control is a message necessary to set a threshold in the RLC buffer of the Ue. In other word the Ue will report a measurement every time this threshold is exceeded.
Cell DCH HS-DSCH transaction

UE Node-B
NBAP NBAP ALCAP ALCAP ALCAP ALCAP NBAP RRC RRC
(2/2)
RNC SGSN
NBAP NBAP ALCAP ALCAP ALCAP ALCAP NBAP RRC RRC
Radio Link Reconfiguration Prepare Radio Link Reconfiguration Ready Establish Request Establish Confirm Establish Request Establish Confirm Radio Reconfiguration Commit
Radio Bearer Reconfiguration Radio Bearer Reconfiguration Complete HSDPA Traffic
28
2006 Nokia
The RNC just received a measurement report that includes a buffer value that exceeds the threshold, require the BS to change the configuration of the radio channel that the Ue used to request the GPRS attach. The reconfiguration of the radio channel means to open the HS-PDSCH. In this message is not included any information about allocated channelisation code for HSDPA traffic , because the codes for that connection are managed in the BS by MAC-hs protocol. In Iub a transport channel was previously opened and used to carry RRC messages, but two additional CID are necessary to manage the HS-DSCH and associated DCH channel. Radio Link reconfiguration Commit message change definitely the configuration of the physical channel in the BS in HS-PDSCH. In the UE side in necessary now to change the configuration of the Radio Bearer ( usually the number 5 ) in order to support HSDPA traffic and just the UE confirms the reconfiguration, traffic can starts.
HS-DSCH Cell PCH transaction

UE Node-B RNC
Status change for inactivity timer
RRC RRC
(1/2)
SGSN
Radio Bearer Reconfiguration Radio Bearer Reconfiguration Complete Cell FACH status
NBAP NBAP ALCAP ALCAP
RRC RRC
Radio Link Deletion Request Radio Link Deletion Response Release Request Release Confirm
NBAP NBAP ALCAP ALCAP
29
2006 Nokia
the Ue stops downloading traffic , so the RNC after a certain inactivity timer move the Ue to Cell FACH status through the message Radio Bearer Reconfiguration. HS-PDSCH channel now is not anymore necessary so it is released with the message RADIO LINK DELETION REQUEST. Also the associated transport channel in the Iub are released with the message RELEASE REQUEST ( 3 times )
HS-DSCH Cell PCH transaction

UE Node-B
ALCAP ALCAP
(2/2)
RNC SGSN
Release Request Release Confirm Release Request Release Confirm
ALCAP ALCAP
ALCAP ALCAP
ALCAP ALCAP
RRC RRC
Physical Channel Reconfiguration ( FACH ) Physical Channel Reconfiguration Complete ( RACH )
RRC RRC
Cell PCH status
30
2006 Nokia
The Ue now is in Cell FACH status. it is allowed to download small packages, but if no traffic is exchanged with the CN after a certain inactivity timer ,the RNC moves the Ue in Cell PCH through the messages PHYSICAL CHANNL RECONFIGURATION.
Cell PCH HS-DSCH transaction

UE Node-B
Cell PCH status
RRC
(1/3)
RNC SGSN
Cell Update Cell Update confirm Cell FACH status
RRC
RRC
RRC
RRC
UTRAN mobility information confirm Measurement Report
RRC
RRC
RRC
NBAP
Radio Link Setup Request
NBAP
NBAP
Radio Link Setup Response
NBAP
The Ue was in Cell PCH status because of inactivity timer. All the transport resources in Iub have been released, but PDP context still open even if the UE does perform traffic. An HTTP request is done by the UE toward the server through the RACH channel. The message sent by the UE is called cell update but it contains a request of uplink traffic. RNC with the message CELL UPDATE CONIRM force the UE to CELL FACH status. Also the UE is requested to RE-ESTABLISH the Radio Bearer 2,3,4 and 5 previously utilised. In case will be the RNC to request traffic , the message will be . PAGING ( DL ) & PAGING RESPONSE ( UL ).

UE Node-B RNC
(2/3)
SGSN
ALCAP
Establish Request
ALCAP
RRC Transport Channel establishment
ALCAP
Establish Confirm
ALCAP
ALCAP
Establish Confirm
ALCAP
DPCH Transport Channel establishment
ALCAP
Establish Confirm Establish Confirm
ALCAP
ALCAP
ALCAP
ALCAP
Establish Confirm
ALCAP
HS-DSCH Transport Channel establishment
32
2006 Nokia

UE
RRC
(3/3)
RNC
RRC
Node-B
Radio Bearer Reconfiguration
SGSN
RRC
Radio Bearer Reconfiguration complete Cell DCH status Measurement Control
RRC
RRC
RRC
HS-DSCH
Capacity Request
HS-DSCH
HS-DSCH
Capacity Allocation
HS-DSCH
33
2006 Nokia
Radio Resource Control Messages
34
2006 Nokia
CELL Update
UE
RRC
Node-B
Cell Update (RACH)
RNC
RRC
CN
RNTI Measurement IEs
RNTI Cell Update cause Measurement Quantity

causes options: cell reselection, periodical cell update, uplink data transmission, paging response, re-entered service area, radio link failure, RLC unrecoverable error) RLC re-establish indicator In dB CPICH_Ec/No
SRNC Admission Control Select Transport Channel
RRC state indicator RLC re-establish indicator

options: CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH)
RRC
UE RLC buffer Checking
Cell Update confirm (FACH)
RRC
35
2006 Nokia
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
36
2006 Nokia
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
UE
RRC Measured Result Measured Result on RACH Event Result
event: e4a
Node-B
Measurement Report (RACH)
Traffic Volume Measured Result List Measurement Quantity Traffic Volume Event Identity
Radio Bearer Identity num. RLC Buffer Payload
RNC
RRC
CN
SRNC Admission Control Collects Radio Ch Parameters

In dB CPICH_Ec/No
Select Transport Ch IDs

C-NBAP
DPCH UL Scram. & Chan. code Transport Ch DCH IDs Radio link ID & Cell ID DPCH Power ctrl info HS-DSCH MAC flow ctrl info
C-NBAP
Radio Link Set up Request
Transport Ch DCH IDs Binding ID Transport Layer Address
SRNC Dig Analysis Route finding ATM CAC Path id & CID selection
Node-B Radio Ch set up AAL2 TP Selection

C-NBAP
Radio Link Set up Response
C-NBAP
Measurement Report Message

MEASUREMENT REPORT UL-DCCH-Message integrityCheckInfo messageAuthenticationCode: '11001011100111101... rrc-MessageSequenceNumber: 6 message measurementReport measurementIdentity: 4 measuredResults trafficVolumeMeasuredResultsList TrafficVolumeMeasuredResults rb-Identity: 1 rlc-BuffersPayload: pl0 TrafficVolumeMeasuredResults rb-Identity: 2 rlc-BuffersPayload: pl0 TrafficVolumeMeasuredResults rb-Identity: 3 rlc-BuffersPayload: pl0 TrafficVolumeMeasuredResults rb-Identity: 4 rlc-BuffersPayload: pl0 TrafficVolumeMeasuredResults rb-Identity: 5 rlc-BuffersPayload: pl512 measuredResultsOnRACH currentCell modeSpecificInfo fdd measurementQuantity cpich-Ec-N0: 44 eventResults trafficVolumeEventResults ul-transportChannelCausingEvent rachorcpch: NULL
trafficVolumeEventIdentity: e4a
UE sends the measurement report in order to inform the RNC about the RLC usage ( payload ) for each different Radio Bearer. Event 4a is used to request an upgrade of the Radio channel used for PS connection, because the UE requested to do HTTP browsing.
Radio Link Set up Request Message

RADIO LINK SETUP REQUEST [FDD] NBAP-PDU ------messageDiscriminator: common -----RadioLinkSetupRequestFDD -----CRNC-CommunicationContextID: 1236 -----UL-DPCH-Information-RL-SetupRqstFDD ul-ScramblingCode - uL-ScramblingCodeNumber: 1000212 ------ minUL-ChannelisationCodeLength: v16 -----DL-DPCH-Information-RL-SetupRqstFDD DCH-FDD-Information DCH-FDD-InformationItem - dCH-ID: 24 ul-TransportFormatSet - nrOfTransportBlocks: 0 ----------40 2006 Nokia HSDPA Call Setup / Kittipong Thamapa
- nrOfTransportBlocks: 3 - transportBlockSize: 336 ------ nrOfTransportBlocks: 4 - transportBlockSize: 336 ------ transmissionTimeInterval: msec-20 -----dl-TransportFormatSet dynamicParts - nrOfTransportBlocks: 0 ------ transmissionTimeInterval: msec-10 -----RL-InformationList-RL-SetupRqstFDD ------ rL-ID: 1 - c-ID: 3 ------ dl-ScramblingCode: 0 - fdd-DL-ChannelisationCodeNumber: 10 - initialDL-transmissionPower: -180 - maximumDL-power: -71 - minimumDL-power: -180 -----hSDSCH-MACdFlows-Information ------
- nrOfTransportBlocks: 1 - transportBlockSize: 148 ------ transmissionTimeInterval: msec-40 -----dl-TransportFormatSet ------ nrOfTransportBlocks: 1 - transportBlockSize: 148 mode ------ transmissionTimeInterval: msec-40 -----DCH-FDD-InformationItem ------ dCH-ID: 1 ul-TransportFormatSet ------ nrOfTransportBlocks: 1 - transportBlockSize: 336 ------ nrOfTransportBlocks: 2 - transportBlockSize: 336
dCH-InformationResponse
Radio Link Set up Response

RADIO LINK SETUP RESPONSE [FDD] NBAP-PDU ------ messageDiscriminator: common -----RadioLinkSetupResponseFDD -----CRNC-CommunicationContextID: 1236 -----NodeB-CommunicationContextID: 160001 -----RL-InformationResponseItem-RL-SetupRspFDD ------ rL-ID: 1 - contents (in bits): 00001 - rL-Set-ID: 1 - contents (in bits): 00001 - received-total-wide-band-power: 69 ------
------ dCH-ID: 24 ------ bindingID: '00000009'H -----49 00 00 10 20 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ------ dCH-ID: 1 - bindingID: '00000004'H -----49 00 00 10 20 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF -----hsDSCH-MACdFlow-Specific-InformationResp ------ hsDSCHMacdFlow-Id: 0 ------- bindingID: '00000006'H -----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 ------
41
2006 Nokia
- codeNumber: 4 ------
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) - Channel identifier: 20 (14h) NSEA-Dest. NSAP serv. endpoint addr. -Parameter's Compatibility: 10h Pass-on not possible: - Do not send notification
42 2006 Nokia
- Discard parameter General action: - Do not send notification - Pass on message or parameter Parameter length: 20 (14h) - Address: 4900001020....FFF LC-Link Charactreristics - 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: 12 (0Ch) - Maximum forward CPS-SDU bit rate: 82 (52h) - Maximum backwards CPS-SDU bit rate: 84 (54h) - Average forward CPS-SDU bit rate: 23 (17h) - Average backwards CPS-SDU bit rate: 25 (19h) - Maximum forward CPS-SDU size: 24 (18h) - Maximum backwards CPS-SDU size: 26 (1Ah) - Average forward CPS-SDU size: 24 (18h) - Average backwards CPS-SDU size: 26 (1Ah)
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: 44F29000 SUGR-Served user gen. reference - 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) - Field: 00000009
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
43
2006 Nokia

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) - Channel identifier: 21 (15h) NSEA-Dest. NSAP serv. endpoint addr. -Parameter's Compatibility: 10h Pass-on not possible: - Do not send notification - Discard parameter 44 2006 Nokia General action: - Do not send notification - Pass on message or parameter Parameter length: 20 (14h) - Address: 4900001020FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF LC-Link Charactreristics - 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: 12 (0Ch) - Maximum forward CPS-SDU bit rate: 10 (Ah) - Average forward CPS-SDU bit rate: 2 (2h)
-----Parameter length: 4 (04h) - Signalling association identifier: 44F29100 SUGR-Served user gen. reference - 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) - Field: 00000004 SSISU-Ser. spec. info (SAR-unassured) - Parameter's Compatibility: 00h Pass-on not possible: - Do not send notification
- Pass on message or parameter - Maximum backwards CPS-SDU bit rate: 1102 (44Eh) General action: - Do not send notification - Average backwards CPS-SDU bit rate: 1094 (446h) - Pass on message or parameter - Maximum forward CPS-SDU size: 3 (3h) Parameter length: 7 (07h) - Maximum backwards CPS-SDU size: 45 (2Dh) - Average forward CPS-SDU size: 1 (1h) -Average backwards CPS-SDU size: 43 (2Bh) OSAID-Orig. sign. assoc. ident. --------- Max length of SSAR-SDU forwards: 0 (0h) - Max length of SSAR-SDU backwards: 175 (AFh) - Transmission error detection disabled
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
45
2006 Nokia

ERQ - ESTABLISH REQUEST - Discard 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: 44F29200 SUGR-Served user gen. reference - 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) - Field: 00000006 DAID-Dest. sign. assoc. ident.: 00000000 General action: - Do not send notification - 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) - Channel identifier: 22 (16h) NSEA-Dest. NSAP serv. endpoint addr. -Parameter's Compatibility: 10h Pass-on not possible: - Do not send notification
46 2006 Nokia
- Pass on message or parameter Parameter length: 20 (14h) - Address: 4900001020....FFFFFFFF LC-Link Charactreristics - 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: 12 (0Ch) - Maximum forward CPS-SDU bit rate: 0 (0h) - Maximum backwards CPS-SDU bit rate: 24 (18h) - Average forward CPS-SDU bit rate: 0 (0h) - Average backwards CPS-SDU bit rate: 2 (2h) - Maximum forward CPS-SDU size: 1 (1h) - Maximum backwards CPS-SDU size: 6 (6h) - Average forward CPS-SDU size: 1 (1h) - Average backwards CPS-SDU size: 6 (6h)
HSDPA traffic (MAC-d flows) and normal DCH connections are sharing the same VCCs. AAL2 connections for MAC-d flows are running in a best effort manner, meaning they are using the remaining VCC capacity, which is not utilized by other AAL2 connections like e.g. for RT and NRT DCHs. This is done by giving them a lower priority compared to RT or NRT connection, when multiplexed into a VCC. AAL2 connections with Background traffic are set up with a default size, which basically ensures some minimum capacity for HSDPA traffic. with Streaming traffic are set up with a required capacity according to the guaranteed bit rate (GBR). Thus there should always be enough transport capacity available to transport those MAC-d flows to the BTS (not part of RAN06)
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
47
2006 Nokia
UE
RRC
It defines the target DCH where to measure the traffic volume It defines the type of quantity. In that case RLC buffer. UE state: Cell DCH, Cell FACH.... Event type: e4a, e4b....& threshold for the RLC buffer in KB/s
Node-B
Measurement Control (DPCH)
Traffic Vol. Meas. Object List Traffic Volume Report Quantity UE state e.g. Event ID & Reporting threshold
RNC
RRC
CN
HS-DSCH
Capacity Allocation
CmCH-PI
HS-DSCH
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 e.g. CmCH-PI User Buffer Size

HS-DSCH
HS-DSCH credits
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
48
2006 Nokia
Measurement Control
MEASUREMENT CONTROL DL-DCCH-Message integrityCheckInfo 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
trafficVolumeMeasQuantity rlc-BufferPayload: NULL trafficVolumeReportingQuantity rlc-RB-BufferPayload: TRUE rlc-RB-BufferPayloadAverage: FALSE 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
49
2006 Nokia
Capacity Allocation / Request

e.g. credits =12 HS-DSCH CAPACITY ALLOCATION Control Frame CRC : 75 (4Bh) Control Frame Type : 11 (0Bh) CmCH-PI : 15 (Fh) Maximum MAC-d PDU Length : 336 bit(s) 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) HS-DSCH CAPACITY REQUEST Control Frame CRC : 50 (32h) Control Frame Type : 10 (0Ah) CmCH-PI : 15 (Fh) User Buffer Size : 3108 (0C24h) octets
50
2006 Nokia
UE
RRC
Node-B
Radio Bearer Reconfiguration (FACH)
RRC state indicator RBs and associated Log.& Trans. Ch ID UL & DL DPCH scramb. e.g. codes & SF CPICH scramb. code info
RNC
RRC
CN
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
UE Open Radio CH Configure RBs & Log. CH Cell DCH status

RRC
Radio Bearer Reconfiguration Complete (DPCH) RNC RNC starts traffic conn.
RRC
51
2006 Nokia
RADIO BEARER RECONFIGURATION [DCCH] DL-DCCH-Message -----rrc-StateIndicator: cell-DCH -----rrc-TransactionIdentifier: 3 rb-Identity: 1 -----ul-UM-RLC-Mode -----dl-UM-RLC-Mode-r5 -----ul-TransportChannelType dch: 24 -----dl-TransportChannelType dch: 24 -----ul-TransportChannelType rach: NULL -----dl-TransportChannelType fach: NULL ------52 2006 Nokia

rb-Identity: 2 -----ul-AM-RLC-Mode -----dl-AM-RLC-Mode-r5 -----ul-TransportChannelType dch: 24 -----dl-TransportChannelType dch: 24 -----ul-TransportChannelType rach: NULL -----dl-TransportChannelType fach: NULL -----rb-Identity: 3 -----ul-AM-RLC-Mode -----dl-AM-RLC-Mode-r5 -----HSDPA Call Setup / Kittipong Thamapa
dl-TransportChannelType dch: 24 -----ul-TransportChannelType rach: NULL -----dl-TransportChannelType fach: NULL -----rb-Identity: 4 -----ul-AM-RLC-Mode -----dl-AM-RLC-Mode-r5 -----ul-TransportChannelType dch: 24 -----dl-TransportChannelType dch: 24 -----ul-TransportChannelType rach: NULL -----dl-TransportChannelType fach: NULL ------
(1/2)
ul-TransportChannelType dch: 24

rb-Identity: 5 -----ul-AM-RLC-Mode -----dl-AM-RLC-Mode-r5 -----ul-TransportChannelType dch: 1 -----dl-TransportChannelType hsdsch: 0 ul-CommonTransChInfo -----ul-AddReconfTransChInfoList UL-AddReconfTransChInformation ul-TransportChannelType: dch transportChannelIdentity: 24 -----UL-AddReconfTransChInformation ul-TransportChannelType: dch transportChannelIdentity: 1 -----dl-CommonTransChInfo -----53 2006 Nokia HSDPA Call Setup / Kittipong Thamapa
(2/2)
dl-AddReconfTransChInfoList DL-AddReconfTransChInformation-r5 dl-TransportChannelType dch: 24 -----dch-QualityTarget bler-QualityValue: -20 DL-AddReconfTransChInformation-r5 dl-TransportChannelType hsdsch: NULL -----dch-QualityTarget bler-QualityValue: -20 ul-ChannelRequirement ul-DPCH-Info -----scramblingCode: 1000212 spreadingFactor: sf16 -----dl-HSPDSCH-Information ------HS-SCCH-Codes: 4 ----------sf-AndCodeNumber sf256: 10 ----------dl-DPCH-InfoPerRL fdd pCPICH-UsageForChannelEst: mayBeUsed -----primaryCPICH-Info primaryScramblingCode: 54 -----sfd256: pb4 dl-CommonInformation dl-DPCH-InfoCommon
Radio Bearer Reconfiguration Complete
RADIO BEARER RECONFIGURATION COMPLETE UL-DCCH-Message integrityCheckInfo messageAuthenticationCode: '10111011101100101110110100001011'B rrc-MessageSequenceNumber: 7 message radioBearerReconfigurationComplete rrc-TransactionIdentifier: 3
54
2006 Nokia
Physical Shared Channel Reconfiguration (1/3)
55
2006 Nokia
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 ...
56
2006 Nokia
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
57
2006 Nokia
PS Call Setup
58
2006 Nokia
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
59
2006 Nokia
Radio Bearer Setup
60
2006 Nokia
Radio Bearer Setup/Reconfiguration

RADIO BEARER RECONFIGURATION [DCCH]
DL-DCCH-Message ... radioBearerReconfiguration-r5 new-H-RNTI: '10011011 11001111'B rrc-StateIndicator: cell-DCH ... rb-MappingInfo RB-MappingOption-r5 ul-LogicalChannelMappings oneLogicalChannel ul-TransportChannelType dch: 1 rlc-SizeList configured: NULL mac-LogicalChannelPriority: 8 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
(1/2)
addOrReconfMAC-dFlow mac-hs-AddReconfQueue-List MAC-hs-AddReconfQueue mac-hsQueueId: 0 mac-dFlowId: 0 reorderingReleaseTimer: rt120 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
61
2006 Nokia
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)
62
2006 Nokia
Capacity Allocation
63
2006 Nokia
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 HS-DSCH 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.
64
2006 Nokia
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)
65
2006 Nokia
DCH to HS-DSCH switch

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 1500000 1000000 bps 500000 0 0 10 20 s 30 40 50
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"
66
2006 Nokia

06 - HSDPA Call Setup - v2

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

06 - HSDPA Call Setup - v2

Uploaded by

Copyright:

Available Formats

HSDPA Call Setup

HSDPA Call Setup / Kittipong Thamapa

HSDPA Call Setup

HSDPA Call Setup

Radio Resource Control Messages

HSDPA Call Setup / Kittipong Thamapa

HSDPA Call Setup / Kittipong Thamapa

Physical Channels for One HSDPA UE

HS-SCCH: High-Speed Shared Control Channel

HS-DPCCH: High-Speed Dedicated Physical Control Channel

HSDPA Call Setup / Kittipong Thamapa

HSDPA Layer 1 channels

HSDPA Call Setup / Kittipong Thamapa

Uplink Physical Channel

HSDPA Call Setup / Kittipong Thamapa

Ref spec. ( 25211.580 )

Uplink Physical Layer

Pilot Npilot bits

TFCI NTFCI bits Tslot = 2560 chips, 10 bits

FBI NFBI bits

TPC NTPC bits

Slot #i 1 radio frame: Tf = 10 ms

c d ,2 DPDCH2 c d ,4 DPDCH4 c d ,6 DPDCH6 cc DPCCH c hs H S -D P C C H

Frame structure for uplink DPCCH

Tslot = 2560 chips

2Tslot = 5120 chips CQI

One HS-DPCCH subframe (2 ms)

Subframe #i One radio frame Tf = 10 ms

Spreading for uplink DPCCH, DPDCHs and HS-DPCCH

Frame structure for uplink HS-DPCCH

HSDPA Call Setup / Kittipong Thamapa

Transport /Physical Channels mapping (UL example)

Transport Block TFI Transport Block TFI

TB & Error Indication

Coding & Multiplexing

Physical Layer BTS L1

DeCoding & De-Multiplexing

Physical Control Channel

Physical Data Channel

Physical Control Channel

Physical Data Channel

HSDPA Call Setup / Kittipong Thamapa

Downlink Physical Channel

HSDPA Call Setup / Kittipong Thamapa

Downlink Physical Channel

HSDPA Call Setup / Kittipong Thamapa

Downlink Physical Channel

DPCCH TPC NTPC bits TFCI NTFCI bits

DPDCH Data2 Ndata2 bits

DPCCH Pilot Npilot bits

Data1 Ndata1 bits

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

(point T in Figure 11)

Slot #i One radio frame, Tf = 10 ms

Combining of downlink physical channels

Frame structure for downlink DPCH

Subframe structure for the HS-PDSCH

Subframe structure for the HS-SCCH

HSDPA Call Setup / Kittipong Thamapa

HSDPA Protocol Architecture

RLC MAC-d MAC-hs PHY UE

RLC MAC-d MAC-hs PHY BTS HS-DSCH FP TNL Iub