06 - hsdpa call setup_v2

Upload: kwangrok-chang

Post on 30-Oct-2015

82 views

Category:

Documents


4 download

TRANSCRIPT

  • 1 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HSDPA Call SetupHSDPA Call Setup

  • 2 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HSDPA Call Setup Review of HSDPA

    HSDPA Call Setup

    Radio Resource Control Messages

  • 3 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Review of HSDPA

  • 4 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Physical Channels for One HSDPA UE

    Associated DPCH, Dedicated Physical Channel DPCH needed for each HSDPA UE.

    Signalling, uplink data.

    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.

    HS-DPCCH: High-Speed Dedicated Physical Control Channel

    MAC-hs Ack/Nack information.

    Channel Quality Information.

    UE

    BTSAs

    soci

    ated

    DPC

    HAs

    soci

    ated

    DPC

    H1-

    15 x

    HS-

    PDSC

    H

    1-4

    x HS

    -SCC

    H

    HS-D

    PCCH

    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 MAC-hs,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 ).

  • 5 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HSDPA Layer 1 channels

    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.

  • 6 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

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

    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 )

  • 7 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Uplink Physical Layer

    I

    j

    cd,1 d

    Sdpch,n

    I+ jQ

    DPDCH 1

    Q

    cd,3 d DPDCH 3

    cd,5 d DPDCH 5

    cd,2 d DPDCH 2

    cd,4 d

    cc c DPCCH

    S

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

    DPDCH 4

    chs HS-DPCCH (If Nmax-dpdch mod 2 = 0)

    hs

    hs

    cd,6 d DPDCH 6

    Spreading for uplink DPCCH, DPDCHs and HS-DPCCH

    Pilot Npilot bits

    TPC NTPC bits

    DataNdata bits

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

    Tslot = 2560 chips, 10 bits

    1 radio frame: Tf = 10 ms

    DPDCH

    DPCCHFBI

    NFBI bitsTFCI

    NTFCI bits

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

    Frame structure for uplink DPCCH

    Subframe #0 Subframe #i Subframe #4

    HARQ-ACK CQI

    One radio frame Tf = 10 ms

    One HS-DPCCH subframe (2 ms)

    2 Tslot = 5120 chips Tslot = 2560 chips

    Frame structure for uplink HS-DPCCH

    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.

  • 8 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Transport /Physical Channels mapping (UL example)

    Transport Block

    Transport Block

    TFI

    TrCH x

    Transport Block

    Transport Block

    TFI

    TrCH y

    TFCI Coding & Multiplexing

    Physical Data Channel

    Physical ControlChannel

    TB & ErrorIndication

    TB & ErrorIndication

    TFI TB & ErrorIndication

    TB & ErrorIndication

    TFI

    TFCIdecoding DeCoding & De-Multiplexing

    Physical Data Channel

    Physical ControlChannel

    Higher Layers UTRAN:MAC / FP

    Physical Layer BTS L1

    DPCCH DPDCH DPCCH DPDCH

    Ue Side BS Side

    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.

  • 9 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    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.

    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

  • 10 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    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.

  • 11 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Downlink Physical Channel Different downlink Physical channels (point S in Figures 8)

    G1

    G2

    GP

    GS

    S-SCH

    P-SCH

    (point T in Figure 11)

    Combining of downlink physical channels

    One radio frame, Tf = 10 ms

    TPC NTPC bits

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

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

    Data2Ndata2 bits

    DPDCHTFCI

    NTFCI bitsPilot

    Npilot bitsData1

    Ndata1 bits

    DPDCH DPCCH DPCCH

    Frame structure for downlink DPCH

    Slot #0 Slot#1 Slot #2

    T slot = 2560 chips, M*10*2 k bits (k=4)

    Data N data 1 bits

    1 subframe: T f = 2 ms

    Subframe structure for the HS-PDSCH

    Slot #0 Slot#1 Slot #2

    Tslot = 2560 chips, 40 bits

    DataNdata1 bits

    1 subframe: T f = 2 ms

    Subframe structure for the HS-SCCH

    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.

  • 12 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HSDPA Protocol Architecture

    New MAC entity, MAC-hs (high-speed) added to the Node B

    Layers above, such as RLC, unchanged.

    PHY PHY TNL

    MAC-d

    HS-DSCH FP HS-DSCH FP

    MAC-d

    TNL

    UE Uu BTS Iub RNC

    RLC RLC

    MAC-d flow

    HS-PDSCH

    MAC-hs MAC-hsHS-DSCH

  • 13 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HS-SCCH

    MAC Architecture

    Handles high speed channels

    Handles dedicated channels

    HS-DSCH HS-DSCH

    Associated Uplink Signalling

    Associated Downlink Signalling

    FACH RACH

    DCCH DTCH DTCH

    DSCH TDD only

    MAC Control

    Iur or local

    MAC Control

    DCH DCH

    MAC-d

    USCH TDD only

    MAC-c/sh

    CCCH CTCH BCCH SHCCH TDD only

    PCCH

    FACH PCH USCH TDD only

    DSCH TDD only

    Iub

    MAC Control

    MAC-hs

    Configuration without MAC-c/sh

    Configuration with MAC-c/sh

    Configuration with MAC-c/sh

    Handles common channels

    HS-DPCCHDPCH ( UL+DL rrc messages (DCCH) )

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

    DPCH UL SF 16DPCH DL SF 256

    Physical Layer

    HS-DPCCH UL SF 256HS-SCCH DL SF 128

    BS RNC RNC

    HS-PDSCH

    HS-PDSCH DL n codes x SF 16

    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.

  • 14 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Node B enhancements for HSDPATerminalsNode BRNC

    PacketsScheduler

    & Buffer

    HARQ &

    Coding

    ACK/NACK & Feedback Decoding

    Flow Control

    R99 responsibilities:

    Physical layer operations

    No dymanic decision making

    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

    Node B enhancementsNew 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.

  • 15 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HS-DSCH code management

    PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST [FDD]NBAP-PDU

    - messageDiscriminator: commonPhysicalSharedChannelReconfigurationRequestFDD

    C-ID: 3MaximumTransmissionPower: 378HS-PDSCH-FDD-Code-Information

    - extension flag: 0 - 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.

    RNC BS

    at restart phase

    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.

  • 16 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Retransmissions in HSDPA

    Server RNC Node-B

    UE

    RLC retransmissions

    TCP retransmissions

    MAC-hs retransmissions

    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.

  • 17 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Iub Flow Control messages (1/2)

    HS-DSCH Capacity Request

    Node B CRNC

    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.

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

  • 18 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Iub Flow Control messages (2/2)

    HS-DSCH Capacity Allocation

    Node B CRNC

    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.

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

  • 19 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    UE RRC status

    Idlemode

    Connected ModeCell DCH

    URA PCH

    Cell PCH

    Cell FACH

    These are the possible status for a UE in a UMTS networkIDLE 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.

    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.

    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.

  • 20 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    RAS05 Mobility with DCH switching HSDPA resumption timer switches

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

    The conditions preventing HSDPA allocation in HSPDA coverage area to HSDPA capable UE are:

    More than one serving cell (Soft Handover) Multi-RAB combination (not supported)

    Lack of HSDPA capacity in the cell

    HS-DSCH coverage HS-DSCH coverage

    Service in HSDPA

    Switch to DCH

    0/0

    Cell A Cell B

    HSDPA

    DCH

    0

    Throughput

    64kbps128kbps or 384kbps according to settings

    Upgrade to e.g.

    64 kbps

    Upgrade to 128 /

    384 kbps Switch to HS-DSCH

    UE on HS-DSCH

    Once the session is in DCH, it remains there until the buffers are empty. After that, HSDPA can be selected

  • 21 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.

    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.

  • 22 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Serving Cell Change via cell_FACH Serving Cell Change switches the

    user from HS-DSCH to Cell_FACHthen back to HS-DSCH

    HS-DSCH coverage HS-DSCH coverage

    Service in HSDPA

    Switching to Cell_FACH

    within the SHO area

    UE on HS-DSCH

    Cell A Cell B

    HSDPA

    DCH

    0

    Throughput

    64kbps

    128kbps or 384kbps according to parameter settings

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

    The same parameter settings apply for this feature as for the DCH switching no need for re-planningHSDPA Serving Cell Change via Cell-FACH feature is used only in intra frequency handover casesIn case of IFHO or ISHO the original DCH switching procedures are usedIf 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 RNCIf the user was moved to Cell-FACH because of low utilization or low throughput then the HSDPA user penalty timers are used on Cell-FACHIf the HSDPA user moves to non-HSDPA cell, the user in HO area will be moved to Cell-FACH. 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)

  • 23 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    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

    R99 coverage HS-DSCH coverage

    Service NRT DCH

    Switching to HS-DSCH is tried after the resumption timer expires(if the Active set size is still 1)

    Cell A Cell B

    HSDPA

    DCH

    0

    Throughput

    64kbps (initial bitrate)

    128kbps or 384kbps according to parameter settings

    Download complete

    This parameter defines the waiting time before a DCH toHS-DSCH switch is attempted. If this timer expires whilethe conditions for the use of HS-DSCH are still fulfilled, aDCH to HS-DSCH switch is attempted.The value 0 means that a DCH to HS-DSCH switch isattempted immediately (without any delay).The value 255 means that this functionality is not in use.

  • 24 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    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.

    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.

    TS 25.308:

    HS-SCCHHS-PDSCH

    DPCH

    DPCHServing HS-DSCH cell

    Soft/softer handover is not supportedfor HS-SCCH/HS-PDSCH.

    HS-DPCCH

    RAS05.1

  • 25 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HSDPA Call set up

  • 26 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    IDLE Mode Cell DCH transactionUE RNC

    IDLE MODE

    SGSN Node-B

    RRC Connection Request ( RACH )RRC RRC

    RRC Connection Set Up ( FACH )RRC RRC

    RRC Connection Set Up Complete ( DCH )RRC RRC

    Radio Link Setup Response (C-NBAP )NBAPNBAP

    Radio Link Setup Request (C-NBAP )NBAPNBAP

    Establish Request (ALCAP)ALCAPALCAP

    Establish Confirm (ALCAP)ALCAPALCAP

    Cell DCH status

    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.

  • 27 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Cell DCH HS-DSCH transaction (1/2)UE RNC SGSN Node-B

    RRC Direct Transfer: PDP context requestRRC RRC

    Radio Bearer Set UpRRC RRC

    Radio Bearer Set Up CompleteRRC RRC

    RANAP RANAP

    PDP context request

    RANAP RANAP

    PDP context acceptRRC Direct Transfer: PDP context acceptRRC RRC

    RRC RRCMeasurement Control

    RRC RRCMeasurement Report

    RRC Direct Transfer: Attach requestRRC RRC RANAP RANAPAttach request

    RANAP RANAP

    Attach acceptRRC Direct Transfer: Attach acceptRRC RRC

    Authentic. &Ciphering

    RANAP RANAP

    RAB assign. request

    RANAP RANAP

    RAB assign. response

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

  • 28 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Cell DCH HS-DSCH transaction (2/2)UE RNC SGSN Node-B

    Radio Link Reconfiguration ReadyNBAPNBAP

    Radio Link Reconfiguration PrepareNBAPNBAP

    Establish RequestALCAPALCAP

    Establish ConfirmALCAPALCAP

    Radio Bearer Reconfiguration RRC RRC

    RRC RRCRadio Bearer Reconfiguration Complete

    Establish RequestALCAPALCAP

    Establish ConfirmALCAPALCAP

    NBAPNBAP Radio Reconfiguration Commit

    HSDPA Traffic

    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.

  • 29 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HS-DSCH Cell PCH transaction (1/2)UE RNC SGSN Node-B

    Release RequestALCAPALCAP

    Release ConfirmALCAPALCAP

    Radio Bearer Reconfiguration RRC RRC

    RRC RRCRadio Bearer Reconfiguration Complete

    Status change for inactivity timer

    Cell FACH status

    Radio Link Deletion ResponseNBAPNBAP

    Radio Link Deletion RequestNBAPNBAP

    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 )

  • 30 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HS-DSCH Cell PCH transaction (2/2)UE RNC SGSN Node-B

    Release RequestALCAPALCAP

    Release ConfirmALCAPALCAP

    Release RequestALCAPALCAP

    Release ConfirmALCAPALCAP

    Physical Channel Reconfiguration ( FACH )RRC RRC

    RRC RRCPhysical Channel Reconfiguration Complete ( RACH )

    Cell PCH status

    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.

  • 31 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Cell PCH HS-DSCH transaction (1/3)UE RNC

    Cell PCH status

    Cell Update confirmRRC RRC

    SGSN Node-B

    Cell UpdateRRC RRC

    UTRAN mobility information confirmRRC RRC

    Measurement ReportRRC RRC

    Radio Link Setup RequestNBAPNBAP

    Radio Link Setup ResponseNBAPNBAP

    Cell FACH status

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

  • 32 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Cell PCH HS-DSCH transaction (2/3)UE RNC SGSN Node-B

    Establish ConfirmALCAPALCAP

    Establish ConfirmALCAPALCAP

    Establish ConfirmALCAPALCAP

    Establish ConfirmALCAPALCAP

    Establish RequestALCAPALCAP

    Establish ConfirmALCAPALCAP

    RRC Transport Channel

    establishment

    DPCH Transport Channel

    establishment

    HS-DSCH Transport Channel

    establishment

  • 33 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Cell PCH HS-DSCH transaction (3/3)UE RNC

    RRC RRC

    SGSN Node-B

    Radio Bearer ReconfigurationRRC RRC

    Measurement ControlRRC RRC

    Capacity Allocation

    HS-DSCHHS-DSCH

    Radio Bearer Reconfiguration complete

    HS-DSCHHS-DSCH

    Capacity Request

    Cell DCH status

  • 34 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Radio Resource Control Messages

  • 35 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    CELL Update UE Node-B RNC CN

    Cell Update (RACH)RRC RRC

    SRNC

    Admission Control

    Select Transport Channel

    RNTI

    Measurement IEs

    RNTI

    Cell Update cause

    Measurement Quantity

    In dB CPICH_Ec/No

    causes options:cell reselection,

    periodical cell update,uplink data transmission,

    paging response,re-entered service area,

    radio link failure,RLC unrecoverable error)

    Cell Update confirm (FACH)RRC RRC

    RRC state indicator

    RLC re-establish indicatorRLC re-establish indicator

    options:CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH)

    UE

    RLC buffer Checking

  • 36 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Cell Update MessageCELL UPDATEUL-CCCH-MessageintegrityCheckInfomessageAuthenticationCode: '01011101001110001111100011101001'Brrc-MessageSequenceNumber: 2

    messagecellUpdateu-RNTIsrnc-Identity: '000100110010'Bs-RNTI: '00000000010011010100'B

    startListSTARTSinglecn-DomainIdentity: cs-domainstart-Value: '00000000000000000010'BSTARTSinglecn-DomainIdentity: ps-domainstart-Value: '00000000000000001000'B

    am-RLC-ErrorIndicationRb2-3or4: FALSEam-RLC-ErrorIndicationRb5orAbove: FALSEcellUpdateCause: uplinkDataTransmissionrb-timer-indicatort314-expired: TRUEt315-expired: FALSE

    measuredResultsOnRACHcurrentCellmodeSpecificInfofddmeasurementQuantitycpich-Ec-N0: 45

  • 37 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Cell Update Confirm MessageCELL UPDATE CONFIRM [DCCH]DL-DCCH-MessageintegrityCheckInfomessageAuthenticationCode: '11110111010101011110100011101101'Brrc-MessageSequenceNumber: 2

    messagecellUpdateConfirmlater-than-r3rrc-TransactionIdentifier: 2criticalExtensionscriticalExtensionsr5cellUpdateConfirm-r5new-C-RNTI: '0000000000000001'Brrc-StateIndicator: cell-FACHrlc-Re-establishIndicatorRb2-3or4: FALSErlc-Re-establishIndicatorRb5orAbove: FALSEmodeSpecificTransChInfofdd

    modeSpecificPhysChInfofdd

  • 38 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    DCH Allocation UE Node-B RNC CN

    Measurement Report (RACH)RRC RRC

    SRNC

    Admission Control

    Collects Radio Ch Parameters

    Select Transport Ch IDsIn dB CPICH_Ec/Noevent: e4a

    DPCH UL Scram. & Chan. code

    Transport Ch DCH IDs

    Measured Result

    Measured Result on RACH

    Traffic VolumeMeasured Result List

    Event ResultMeasurement Quantity

    Radio Bearer Identity num.RLC Buffer Payload

    Traffic VolumeEvent Identity

    C-NBAPC-NBAPRadio Link Set up Request

    Radio link ID & Cell ID

    DPCH Power ctrl info

    HS-DSCH MAC flow ctrl info

    C-NBAPC-NBAPRadio Link Set up Response

    Transport Layer Address

    Binding ID

    Transport Ch DCH IDs

    Node-B

    Radio Ch set up

    AAL2 TP Selection

    SRNC

    Dig Analysis Route finding

    ATM CAC

    Path id & CID selection

  • 39 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Measurement Report Message

    MEASUREMENT REPORTUL-DCCH-MessageintegrityCheckInfomessageAuthenticationCode: '11001011100111101...rrc-MessageSequenceNumber: 6

    messagemeasurementReportmeasurementIdentity: 4measuredResultstrafficVolumeMeasuredResultsListTrafficVolumeMeasuredResultsrb-Identity: 1rlc-BuffersPayload: pl0TrafficVolumeMeasuredResultsrb-Identity: 2rlc-BuffersPayload: pl0

    TrafficVolumeMeasuredResultsrb-Identity: 3rlc-BuffersPayload: pl0TrafficVolumeMeasuredResultsrb-Identity: 4rlc-BuffersPayload: pl0TrafficVolumeMeasuredResultsrb-Identity: 5rlc-BuffersPayload: pl512

    measuredResultsOnRACHcurrentCellmodeSpecificInfofddmeasurementQuantitycpich-Ec-N0: 44

    eventResultstrafficVolumeEventResultsul-transportChannelCausingEventrachorcpch: NULLtrafficVolumeEventIdentity: 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.

  • 40 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Radio Link Set up Request MessageRADIO 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-SetupRqstFDDDCH-FDD-Information

    DCH-FDD-InformationItem- dCH-ID: 24

    ul-TransportFormatSet- nrOfTransportBlocks: 0

    ------

    - nrOfTransportBlocks: 1- transportBlockSize: 148

    ------- transmissionTimeInterval: msec-40

    ------dl-TransportFormatSet

    ------- nrOfTransportBlocks: 1- transportBlockSize: 148

    mode------

    - transmissionTimeInterval: msec-40------

    DCH-FDD-InformationItem------

    - dCH-ID: 1ul-TransportFormatSet

    ------- nrOfTransportBlocks: 1- transportBlockSize: 336

    ------- nrOfTransportBlocks: 2- transportBlockSize: 336

    ------

    - nrOfTransportBlocks: 3- transportBlockSize: 336

    ------- nrOfTransportBlocks: 4- transportBlockSize: 336

    ------- transmissionTimeInterval: msec-20

    ------dl-TransportFormatSetdynamicParts

    - 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

    ------

  • 41 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    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-InformationResponse------

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

    - codeNumber: 4------

  • 42 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Establish Request MessageERQ - ESTABLISH REQUESTDAID-Dest. sign. assoc. ident.: 00000000- Message's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterCEID-Connection element ident.- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 5 (05h)- Path identifier: 1021 (3FDh)- Channel identifier: 20 (14h)NSEA-Dest. NSAP serv. endpoint addr.-Parameter's Compatibility: 10hPass-on not possible:- Do not send notification

    - Discard parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 20 (14h)- Address: 4900001020....FFFLC-Link Charactreristics- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter 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: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Signalling association identifier: 44F29000SUGR-Served user gen. reference- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Field: 00000009

  • 43 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Establish Confirm Message

    ECF - ESTABLISH CONFIRMDAID-Dest. sign. assoc. ident.: 44F29000- Message's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterOSAID-Orig. sign. assoc. ident.- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Signalling association identifier: 0000000E

  • 44 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Establish Request MessageERQ - ESTABLISH REQUESTDAID-Dest. sign. assoc. ident.: 00000000- Message's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterCEID-Connection element ident.- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 5 (05h)- Path identifier: 1021 (3FDh)- Channel identifier: 21 (15h)NSEA-Dest. NSAP serv. endpoint addr.-Parameter's Compatibility: 10hPass-on not possible:- Do not send notification- Discard parameter

    General action:- Do not send notification- Pass on message or parameterParameter length: 20 (14h)- Address: 4900001020FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFLC-Link Charactreristics- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 12 (0Ch)- Maximum forward CPS-SDU bit rate: 10 (Ah)- Maximum backwards CPS-SDU bit rate: 1102 (44Eh)- Average forward CPS-SDU bit rate: 2 (2h)- Average backwards CPS-SDU bit rate: 1094 (446h)- Maximum forward CPS-SDU size: 3 (3h)- 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.---------

    ------Parameter length: 4 (04h)- Signalling association identifier: 44F29100SUGR-Served user gen. reference- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Field: 00000004SSISU-Ser. spec. info (SAR-unassured)- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 7 (07h)- Max length of SSAR-SDU forwards: 0 (0h)- Max length of SSAR-SDU backwards: 175 (AFh)- Transmission error detection disabled

  • 45 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Establish Confirm

    ECF - ESTABLISH CONFIRMDAID-Dest. sign. assoc. ident.: 44F29100- Message's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterOSAID-Orig. sign. assoc. ident.- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Signalling association identifier: 00000011

  • 46 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Establish Request MessageERQ - ESTABLISH REQUESTDAID-Dest. sign. assoc. ident.: 00000000- Message's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterCEID-Connection element ident.- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 5 (05h)- Path identifier: 1021 (3FDh)- Channel identifier: 22 (16h)NSEA-Dest. NSAP serv. endpoint addr.-Parameter's Compatibility: 10hPass-on not possible:- Do not send notification

    - Discard parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 20 (14h)- Address: 4900001020....FFFFFFFFLC-Link Charactreristics- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter 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)

    OSAID-Orig. sign. assoc. ident.- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Signalling association identifier: 44F29200SUGR-Served user gen. reference- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Field: 00000006

    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)

  • 47 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Establish Confirm

    ECF - ESTABLISH CONFIRMDAID-Dest. sign. assoc. ident.: 44F29200- Message's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterOSAID-Orig. sign. assoc. ident.- Parameter's Compatibility: 00hPass-on not possible:- Do not send notification- Pass on message or parameterGeneral action:- Do not send notification- Pass on message or parameterParameter length: 4 (04h)- Signalling association identifier: 0000000D

  • 48 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    UE Node-B RNC CN

    e.g.

    Traffic Vol. Meas. Object List

    Traffic Volume Report Quantity

    UE state

    Event ID & Reporting threshold

    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

    Measurement Control (DPCH)RRC RRC

    Capacity AllocationHS-DSCHHS-DSCH

    HS-DSCHHS-DSCHCapacity Request

    e.g.

    CmCH-PI

    Maximum MAC PDU Length

    HS-DSCH credits

    CmCH-PI

    User Buffer Size Indicates the users buffer size (i.e. the amount of data in the buffer in the SRNC)

    The Common Transport Channel Priority Indicator IE indicates the priority of the data frame

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

    Maximum MAC-d PDU length

  • 49 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Measurement Control

    MEASUREMENT CONTROLDL-DCCH-MessageintegrityCheckInfomessageAuthenticationCode:

    '01000100110001010011011101101100'Brrc-MessageSequenceNumber: 9

    messagemeasurementControllater-than-r3rrc-TransactionIdentifier: 0criticalExtensionsr4measurementControl-r4measurementIdentity: 2measurementCommandsetuptrafficVolumeMeasurementtrafficVolumeMeasurementObjectListUL-TrCH-Identitydch: 1

    trafficVolumeMeasQuantityrlc-BufferPayload: NULL

    trafficVolumeReportingQuantityrlc-RB-BufferPayload: TRUErlc-RB-BufferPayloadAverage: FALSErlc-RB-BufferPayloadVariance: FALSE

    measurementValidityue-State: cell-DCH

    reportCriteriatrafficVolumeReportingCriteriatransChCriteriaListTransChCriteriaul-transportChannelIDdch: 1

    eventSpecificParametersTrafficVolumeEventParameventID: e4areportingThreshold: th1024timeToTrigger: ttt0pendingTimeAfterTrigger: ptat2

    measurementReportingModemeasurementReportTransferMode: acknowledgedModeRLCperiodicalOrEventTrigger: eventTrigger

  • 50 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Capacity Allocation / Request

    HS-DSCH CAPACITY ALLOCATIONControl 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 msHS-DSCH Repetition Period : 0 (00h) (unlimited repetition period)

    e.g. credits =12

    HS-DSCH CAPACITY ALLOCATIONControl 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 msHS-DSCH Repetition Period : 0 (00h) (unlimited repetition period)

    e.g. credits =0

    HS-DSCH CAPACITY REQUESTControl Frame CRC : 50 (32h)Control Frame Type : 10 (0Ah)CmCH-PI : 15 (Fh)User Buffer Size : 3108 (0C24h) octets

  • 51 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    UE Node-B RNC CN

    Radio Bearer Reconfiguration (FACH)RRC RRC

    UE

    Open Radio CH

    Configure RBs & Log. CH

    Radio Bearer Reconfiguration Complete (DPCH)RRC RRC

    e.g.

    RRC state indicator

    RBs and associated Log.& Trans. Ch ID

    UL & DL DPCH scramb. codes & SF

    CPICH scramb. code info

    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

    Cell DCH status

    RNC

    RNC starts traffic conn.

  • 52 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Radio Bearer Reconfiguration (1/2)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-TransportChannelTypedch: 24

    ------dl-TransportChannelTypedch: 24

    ------ul-TransportChannelTyperach: NULL

    ------dl-TransportChannelTypefach: NULL

    -------

    rb-Identity: 2------

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

    dl-AM-RLC-Mode-r5------

    ul-TransportChannelTypedch: 24

    ------dl-TransportChannelTypedch: 24

    ------ul-TransportChannelTyperach: NULL

    ------dl-TransportChannelTypefach: NULL

    ------rb-Identity: 3

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

    ------dl-AM-RLC-Mode-r5

    ------ul-TransportChannelType

    dch: 24

    dl-TransportChannelTypedch: 24

    ------ul-TransportChannelTyperach: NULL

    ------dl-TransportChannelTypefach: NULL

    ------rb-Identity: 4

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

    ------dl-AM-RLC-Mode-r5

    ------ul-TransportChannelTypedch: 24

    ------dl-TransportChannelTypedch: 24

    ------ul-TransportChannelTyperach: NULL

    ------dl-TransportChannelTypefach: NULL

    ------

  • 53 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Radio Bearer Reconfiguration (2/2)rb-Identity: 5------

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

    dl-AM-RLC-Mode-r5------

    ul-TransportChannelTypedch: 1

    ------dl-TransportChannelTypehsdsch: 0

    ul-CommonTransChInfo ------

    ul-AddReconfTransChInfoListUL-AddReconfTransChInformationul-TransportChannelType: dchtransportChannelIdentity: 24

    ------UL-AddReconfTransChInformationul-TransportChannelType: dchtransportChannelIdentity: 1

    ------dl-CommonTransChInfo

    ------

    dl-AddReconfTransChInfoListDL-AddReconfTransChInformation-r5dl-TransportChannelTypedch: 24

    ------dch-QualityTargetbler-QualityValue: -20

    DL-AddReconfTransChInformation-r5dl-TransportChannelTypehsdsch: NULL

    ------dch-QualityTargetbler-QualityValue: -20

    ul-ChannelRequirementul-DPCH-Info

    ------scramblingCode: 1000212spreadingFactor: sf16

    ------dl-HSPDSCH-Information

    -------HS-SCCH-Codes: 4

    ------

    dl-CommonInformationdl-DPCH-InfoCommon

    ------sfd256: pb4

    ------primaryCPICH-InfoprimaryScramblingCode: 54

    ------dl-DPCH-InfoPerRLfddpCPICH-UsageForChannelEst: mayBeUsed

    ------sf-AndCodeNumbersf256: 10

    ------

  • 54 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Radio Bearer Reconfiguration Complete

    RADIO BEARER RECONFIGURATION COMPLETEUL-DCCH-MessageintegrityCheckInfomessageAuthenticationCode:

    '10111011101100101110110100001011'Brrc-MessageSequenceNumber: 7

    messageradioBearerReconfigurationCompleterrc-TransactionIdentifier: 3

  • 55 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Physical Shared Channel Reconfiguration(1/3)

  • 56 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    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

  • 57 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    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

  • 58 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    PS Call Setup

  • 59 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    RRC Connection Setup Complete Message

    RRC CONNECTION SETUP COMPLETEUL-DCCH-MessagemessagerrcConnectionSetupComplete...physicalChannelCapability

    ...ue-RadioAccessCapability-v590extdl-CapabilityWithSimultaneousHS-DSCHConfig: kbps64pdcp-Capability-r5-extsupportForRfc3095ContextRelocation: FALSE

    rlc-Capability-r5-extphysicalChannelCapabilityfdd-hspdschsupportedhsdsch-physical-layer-category: 12supportOfDedicatedPilotsForChannelEstimationOfHSDSCH: FALSEsimultaneousSCCPCH-DPCH-HSDSCH-Reception: FALSE

    tdd384-hspdschunsupported: NULLtdd128-hspdschunsupported: NULL

    multiModeRAT-Capability-v590extsupportOfUTRAN-ToGERAN-NACC: FALSE

  • 60 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Radio Bearer Setup

  • 61 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Radio Bearer Setup/Reconfiguration (1/2)

    RADIO BEARER RECONFIGURATION [DCCH]DL-DCCH-Message...

    radioBearerReconfiguration-r5new-H-RNTI: '10011011 11001111'Brrc-StateIndicator: cell-DCH...

    rb-MappingInfoRB-MappingOption-r5ul-LogicalChannelMappingsoneLogicalChannelul-TransportChannelTypedch: 1

    rlc-SizeListconfigured: NULL

    mac-LogicalChannelPriority: 8dl-LogicalChannelMappingListDL-LogicalChannelMapping-r5dl-TransportChannelTypehsdsch: 0

    DL-AddReconfTransChInformation-r5dl-TransportChannelTypehsdsch: NULLtfs-SignallingModehsdschharqInfonumberOfProcesses: 6

    memoryPartitioningimplicit: NULL

    addOrReconfMAC-dFlow

    mac-hs-AddReconfQueue-List

    MAC-hs-AddReconfQueuemac-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-Informationhs-scch-InfomodeSpecificInfofddhS-SCCHChannelisationCodeInfoHS-SCCH-Codes: 4

    measurement-feedback-InfomodeSpecificInfofddmeasurementPowerOffset: 9feedback-cycle: fc4

    cqi-RepetitionFactor: 1deltaCQI: 4

    modeSpecificInfofdd: NULL

  • 62 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Radio Bearer Setup/Reconfiguration (2/2)

    dl-InformationPerRL-ListDL-InformationPerRL-r5modeSpecificInfofddprimaryCPICH-InfoprimaryScramblingCode: 30

    servingHSDSCH-RL-indicator: TRUEdl-DPCH-InfoPerRLfddpCPICH-UsageForChannelEst: mayBeUseddpch-FrameOffset: 80dl-ChannelisationCodeListDL-ChannelisationCodesf-AndCodeNumbersf256: 10

    tpc-CombinationIndex: 0

  • 63 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    Capacity Allocation

  • 64 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HS-DSCH Capacity Request

    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.

    HS-DSCH CAPACITY REQUEST

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

  • 65 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    HS-DSCH Capacity Allocation & HS-DSCH Data Frame

    HS-DSCH CAPACITY ALLOCATIONControl 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 msHS-DSCH Repetition Period : 0 (00h) (unlimited repetition period)

    HS-DSCH DATA FRAMEHeader CRC : 15 (0Fh)CmCH-PI : 15 (Fh)MAC-d PDU Length : 336 bit(s)NumOfPDU : 3 (03h)User Buffer Size : 36920 (9038h) octetsMAC-d PDU1. 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 ExtensionPayload CRC : 32680 (7FA8h)

  • 66 2006 Nokia HSDPA Call Setup / Kittipong Thamapa

    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.

    Application throughput

    0

    500000

    1000000

    1500000

    0 10 20 30 40 50s

    bps

    "MEASUREMENT_CONTROL"DCCH08:33.1RRCD

    "RADIO_BEARER_RECONFIGURATION_COMPLETE"DCCH08:32.8RRCU

    "MEASUREMENT_REPORT"DCCH08:32.8RRCU

    "RADIO_BEARER_RECONFIGURATION"DCCH08:31.7RRCD

    "MEASUREMENT_REPORT"DCCH08:30.7RRCU

    "MEASUREMENT_CONTROL"DCCH08:30.7RRCD

    "RADIO_BEARER_RECONFIGURATION_COMPLETE"DCCH08:30.5RRCU

    "RADIO_BEARER_RECONFIGURATION"DCCH08:29.3RRCD

    "MEASUREMENT_CONTROL"DCCH08:25.1RRCD

    "ACTIVE_SET_UPDATE_COMPLETE"DCCH08:24.8RRCU

    "ACTIVE_SET_UPDATE"DCCH08:24.8RRCD

    MessageSubchannelTimeEventIdActive set size=1 after this Active Set Update (no SHO anymore). Resumption timer started.

    RB reconfiguration to DCH0/0. 4s resumption timer applied before.

    RB reconfiguration to HS-DSCH

    ~2.5 seconds gap according signaling. The data gap is about 6s

    when measured with Ethereal.

    DCH NRT HS-DSCH