HSDPA Parameters

Ver. 1

Nokia RNWP 2006 Sept

1

© NOKIA

HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL

Company Confidential

HSDPA Activation
• HSDPA is enabled with HSDPAenable parameter (Requires object locking) • MAC-hs entity is created. • HSDPAenabled
• •

Parameter enables / disables the use of HSDPA in the cell. When the value of the parameter is set to 1 (HSDPA functionality is enabled for the cell) the system checks that maximum amount of HSDPA capable BTSs and cells is not exceeded. If it is not possible to activate HSDPA for new BTS or cell then activation does not succeed and error is printed out.

• When HSDPA is enabled following BTS resources are allocated:
• • •

WSPC capacity for HSDPA 5 HS-PDSCH codes (SF16) 1 HS-SCCH code (SF128)

2

© NOKIA

HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL

Company Confidential

Directed RRC Connection Setup for HSDPA (1/2)
• DirectedRRCEnabled The parameter enables/disables the use of directed RRC connection setup or directed RRC connection setup for HSDPA layer in the cell.
0: Directed RRC connection setup is not enabled in the cell 1: Directed RRC connection setup is enabled in the cell 2: Directed RRC connection setup for HSDPA layer is enabled in the cell

3

© NOKIA

HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL

Company Confidential

Directed RRC Connection Setup for HSDPA (2/2)
• Directed RRC connection setup for HSDPA layer cannot be used simultaneously in the cell with Directed RRC connection setup feature (load based). • (Load based) Directed RRC connection setup would move also potential HSDPA users away from HSDPA supporting cell. • When Directed RRC connection setup for HSDPA layer is used, the maximum number of cells (layers) in one sector of the base station that can be configured is two. • If three-layer network is used one of the DCH layers (not supporting HSDPA) has to have different Sector Identifier in base station than in layers (DCH layer and HSDPA layer) where the Directed RRC connection setup for HSDPA layer is supported.

4

© NOKIA

HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL

Company Confidential

ppt / 2006 Sept / MHL Company Confidential .Planning parameters in RAN05 for Power allocation • HSDPA power is defined by the PtxMaxHSDPA parameter. Note that the HSDPA power can be used for Rel-99 channels when there are no MAC-d flows in the cell. Related Parameters PtxMaxHSDPA HSDPAPriority PtxTargetHSDPA PtxOffsetHSDPA WinLCHSDPA • • • • • • • • 5 © NOKIA HSDPA_Parameters_v1_cv. The signaling takes place in a physical shared channel reconfiguration procedure after cell setup in cells that support HSDPA and have HSDPA enabled (parameter HSDPAenabled). The value of the parameter is signaled to the BTS with codes.

ppt / 2006 Sept / MHL Company Confidential ..Power Allocation PtxMaxHSDPA The parameter defines the maximum allowed HSDPA transmission power.8 dBm (6W) Modification Requires object locking 6 © NOKIA HSDPA_Parameters_v1_cv.50 dBm.1 dBm Default value 37. step 0. Range and step 0..

either the total transmitted carrier power or the total non-controllable transmitted power has to be below or equal to PtxTargetHSDPA before the first MAC-d flow can be allocated in the cell. If the averaged PtxnonHSDPA exceeds or equals PtxTargetHSDPA+ PtxOffsetHSDPA. step 0.ppt / 2006 Sept / MHL Company Confidential .50 dBm..1 dB Default value 0.6 dB. step 0. Range and step -10.1 dBm Default value 38. If at least one MAC-d flow is allocated in the cell.5 dBm PtxOffsetHSDPA The target value of the transmitted non-HSDPA power (PtxTargetHSDPA) can be exceeded by the value of this parameter before the cell is considered to be overloaded in the downlink.... Range and step 0. overload control actions targeted either to MAC-d flows or NRT DCHs are started.8 dB 7 © NOKIA HSDPA_Parameters_v1_cv. depending on the setting of the parameter HSDPAPriority. PtxTargetHSDPA is used instead of PtxTarget as a target of PtxnonHSDPA in NRT DCH scheduling.Power Allocation PtxTargetHSDPA Depending on the setting of the parameter HSDPAPriority.

before the HS-DSCH can be selected. before the HSDSCH can be selected. the overload control actions are targeted primarily to NRT DCH(s). all MAC-d flows in the cell are released. the total transmitted carrier power has to be below or equal to PtxTargetHSDPA. HSDPAPriority=2 When the first MAC-d flow in the cell is allocated. HSDPAPriority=1 When the first MAC-d flow in the cell is allocated. Only if there are no more NRT DCH(s) in the cell.HSDPA Priority The parameter defines the relative priority between NRT DCHs and MAC-d flows. If the averaged PtxnonHSDPA exceeds or equals PtxTargetHSDPA+ PtxOffsetHSDPA. the overload control actions are targeted to MAC-d flows and all MAC-d flows in the cell are released. If the averaged PtxnonHSDPA exceeds or equalsPtxTargetHSDPA+ PtxOffsetHSDPA. the total non-controllable transmitted power has to be below or equal to PtxTargetHSDPA. 8 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential .

ppt / 2006 Sept / MHL Company Confidential B C .Overload control actions for NRT DCH(s) started • Event C: PtxnonHSDPA>=PtxtargetHSDPA +PtxoffsetHSDPA . • When HSDPA power is in use: PtxNC target is Ptxtarget. otherwise DCH scheduling. • Event B: PtxnonHSDPA>=PtxtargetHSDPA +PtxoffsetHSDPA .No more NRT DCHs. all MAC-d flows in the cell are released Node-B Tx power Max power Ptxtotal PtxMaxHSDPA Ptx_target PtxnonHSDPA PtxNC Ptx_offset_HSDPA Ptx_target_HSDPA A 9 © NOKIA HSDPA_Parameters_v1_cv.Power allocation HSDPAPriority =1 • Event A: First MAC-d flow entering the cell PtxNC<=PtxtargetHSDPA -> HS-DSCH is selected. NRT DCH scheduling upto PtxtargetHSDPA.

All MAC-d flows in the cell released • Event C: (normal NRT DCH overload control) Ptxtotal>=Ptxtarget+Ptxoffset .ppt / 2006 Sept / MHL Company Confidential B C . otherwise DCH scheduling. NRT DCH scheduling upto PtxtargetHSDPA.Power allocation HSDPAPriority =2 • Event A: First MAC-d flow entering the cell Ptxtotal<=PtxtargetHSDPA -> HS-DSCH is selected. • Event B: PtxnonHSDPA>=PtxtargetHSDPA +PtxoffsetHSDPA . • When HSDPA power is in use: PtxNC target is Ptxtarget.Overload control actions for NRT DCH(s) started Node-B Tx power Max power Ptxtotal Ptx_offset Ptx_target PtxMaxHSDPA Ptx_offset_HSDPA Ptx_target_HSDPA PtxnonHSDPA PtxNC A 10 © NOKIA HSDPA_Parameters_v1_cv.

ppt / 2006 Sept / MHL Company Confidential . so in order to avoid HSDPA power to be allocated and soon released DCH power increase << PtxoffsetHSDPA 11 © NOKIA HSDPA_Parameters_v1_cv.PtxtargetHSDPA AND PtxoffsetHSDPA STRATEGY: 1) The ratio between PC headroom and Variable Power shall remain the same after the introduction of HSDPA because HSDPA does not require any power control headroom 2) When HSDPA power is allocated DCH Power increases to to keep BLER targets.

8W Ptxoffset PtxTarget 43 dBm 42 dBm 8W 20W 43dBm PtxmaxHSDPA PtxoffsetHSDPA PtxTargetHSDPA 40.5W DCH + Variable part of CCHs 2W CPICH 33 dBm 2W CPICH 33dBm HSDPAPriority =1 Company Confidential 12 © NOKIA HSDPA_Parameters_v1_cv.8dBm 39.8dBm 12W DCH + Variable part of CCHs 9.Power Allocation (CHT) 20W 15.ppt / 2006 Sept / MHL .

30s) • Associated UL DCH needs to released also (InactivityTimer). • Low Utilisation indication is send when • MAC-d flow throughput is below MACdflowutilRelThr • And there is no more data in the BTS buffer (normal release).HS-DSCH & MAC-d release • HS-DSCH (HSDPA Transport Channel) is released when either UTILIZATION or THROUGHPUT indicates inefficient use of resources. • If the release of the MAC-d flow is caused by low throughput. • Low Throughput indication is send when • MAC-d flow throughput is below MACdflowthroughputRelThr • Even when there is still data in the BTS RLC buffer but it cannot be sent (abnormal release). def. when HS-DSCH is released 13 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential . the UE is not allowed to use HS-DSCH until the HS-DSCH guard timer has expired due to low throughput (RNP parameter HsdschGuardTimerLowThroughput.

ppt / 2006 Sept / MHL Company Confidential .HS-DSCH & MAC-d release: low utilisation PDUs in buffer Throughput Low utilization indication MACdflowUtilRelThr (Def: 256bps) MACdflowthrougputRelThr (Def: 0bps) MACdflowUtilTimetoTrigger (Def: 0s) 14 © NOKIA HSDPA_Parameters_v1_cv.

ppt / 2006 Sept / MHL Company Confidential .HS-DSCH & MAC-d release : low throughput PDUs in buffer Throughput Low throughput indication MACdflowUtilRelThr (Def: 256bps) MACdflowthrougputRelThr (Def: 0bps) HsdschGuardTimerLowThroughput. CHT: 5s) MACdflowUtilTimetoTrigger (Def: 0s) MACdflowThroughputTimetoTrigger (Def: 0s) 15 © NOKIA HSDPA_Parameters_v1_cv. (Def: 30s.

ppt / 2006 Sept / MHL Company Confidential . In this case UE specific timer HsdschGuardTimerLowThroughput is started.HS-DSCH & MAC-d release L3 starts procedure to release UL NRT DCH and MAC-d flow if: • MAC-d flow has low utilization and UL NRT DCH can be released (InactivityTimer). Or • MAC-d flow has low throughput and UL NRT DCH can be released (InactivityTimer). the functionality described in case of low utilization is followed HS-DSCH & associated DCHs released UE moved to Cell FACH 16 © NOKIA HSDPA_Parameters_v1_cv. If MAC-d flow has both low utilization and low throughput conditions valid at the same time.

• Range and step 0.. step 256 bps • Default value 256 bps 17 © NOKIA HSDPA_Parameters_v1_cv. • The throughput measurement measures the number of bits transmitted by MAC-d during the sliding measurement window. the MACdflowutilTimetoTrigger timer is started.64000 bps. The sliding measurement window is defined with the parameter MACdflowthroughputAveWin. • The threshold is defined as a number of bits per second.ppt / 2006 Sept / MHL Company Confidential . • If the result of the throughput measurement is lower than or equal to the threshold.MACdflowutilRelThr (Low utilization threshold of the MAC-d flow) • This parameter defines the low utilization threshold of the throughput measurement of the MAC-d flow..

the MACdflowutilTimetoTrigger is started.300 s. L2 sends a low utilisation indication to L3 and resets the MACdflowutilTimetoTrigger.ppt / 2006 Sept / MHL Company Confidential ..2 s • Default value 0 s 18 © NOKIA HSDPA_Parameters_v1_cv. the MACdflowutilTimetoTrigger is stopped and reset. the number of RLC PDUs in the transmission windows is checked: • If the sum of the RLC PDUs in the transmission windows of the NRT RBs mapped to the MAC-d flow equals zero. step 0. L2 keeps checking the transmission windows until they are empty or the downlink throughput goes above MACdflowutilRelThr. • If the result of the throughput measurement is lower than or equal to the MACdflowutilRelThr. • If the result of the throughput measurement is higher than the MACdflowutilRelThr. • If there are any RLC PDUs in the transmission windows.. • Range and step 0.MACdflowutilTimetoTrigger (Low utilization time to trigger of the MAC-d flow ) • This parameter defines the low utilization time to trigger timer of the throughput measurement of the MAC-d flow. • If the MACdflowutitTimetoTrigger expires.

• If the result of the throughput measurement is less than or equal to the threshold. • Range and step 0. • The threshold is defined as a number of bits per second. • The sliding measurement window is defined with the parameter MACdflowthroughputAveWin. the MACdflowthroughputTimetoTrigger timer is started. • The throughput measurement measures the number of bits transmitted by MAC-d during the sliding measurement window..ppt / 2006 Sept / MHL Company Confidential . step 256 bps • Default value 0 bps 19 © NOKIA HSDPA_Parameters_v1_cv.64000 bps..MACdflowthroughputRelThr (Low throughput threshold of the MAC-d flow) • This parameter defines the low throughput threshold of the throughput measurement of the MAC-d flow.

the MACdflowthroughputTimetoTrigger is started.ppt / 2006 Sept / MHL Company Confidential . the MACdflowthroughputTimetoTrigger is stopped and reset. L2 sends the low throughput indication to L3 and resets the MACdflowthroughputTimetoTrigger. • Range and step 0..2 s • Default value 5 s 20 © NOKIA HSDPA_Parameters_v1_cv. • If the result of the throughput measurement is lower than or equal to the MACdflowthroughputRelThr.MACdflowthroughputTimetoTrigger (Low throughput time to trigger of the MAC-d flow) • This parameter defines the low throughput time to trigger timer of the throughput measurement of the MAC-d flow..300 s. step 0. • If the MACdflowthroughputTimetoTrigger expires. • If the result of the throughput measurement is higher than the MACdflowthoughputRelThr.

step 0..5 s • Default value 3 s MACdflowthroughputAveWin 21 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential . • The throughput measurement measures the number of bits transmitted by MAC-d during the sliding measurement window.10 s. • Value 0 means that the MAC-d flow throughput measurement is not activated. • The sliding measurement window is defined with the parameter MACdflowthroughputAveWin. • Range and step 0..(Window size of the MAC-d flow throughput measurement) • This parameter defines the averaging window size for the throughput measurement of the MAC-d flow.

. • When the timer is running HS-DSCH allocation is not allowed to the UE.HSDSCHGuardTimerLowThroughput (HS-DSCHguard timer due to low throughput) • HSDSCHGuardTimerLowThroughput is a UE-specific timer.ppt / 2006 Sept / MHL Company Confidential .. • It is started after a release of the MAC-d flow. • Range and step 0. step 1 s • Default value 30 s • Proposed Value: 5s 22 © NOKIA HSDPA_Parameters_v1_cv.240 s. which was triggered by low throughput.

• General • Power Allocation • MAC-d flow utilization & throughput measurement • Associated UL Channel Bit Rate • Mobility 23 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential .

g.sent in every 4ms • SF 256 UE Associated DPCH. . • Fixed SF128 • Associated DPCH. UL CHANNELS • Associated DPCH. 128. Dedicated Physical Channel. • Channel Quality Information (CQI reports) . Dedicated Physical Channel .DPCH needed for each HSDPA UE.Power control commands for associated UL DCH -Transfer signalling (SRB) messages -Uplink data 64.ppt / 2006 Sept / MHL Company Confidential . • 1-15 code channels (QPSK or 16QAM modulation) • Divided into 2ms TTIs • Fixed SF16 • Doesn’t have power control BTS Associated DPCH Associated DPCH 1-15 x HS-PDSCH 1-4 x HS-SCCH HS-DPCCH Rel99 DCH • HS-SCCH: High-Speed Shared Control Channel • Informs UE how to receive HS-PDSCH in the next HSDPSCH frame. 384kbps. e. Dedicated Physical Channel • HS-DPCCH: High-Speed Dedicated Physical Control Channel • MAC-hs Ack/Nack information. TCP acks 24 © NOKIA HSDPA_Parameters_v1_cv.Physical Channels for One HSDPA UE DL CHANNELS • HS-PDSCH: High-Speed Physical Downlink Shared Channel • Actual HSDPA data of HS-DSCH transport channel.

Associated UL Channel Bit Rate . • If the HS-DSCH allocation is triggered by downlink.General • In order to use HS-DSCH as a downlink transport channel. • If the channel allocation fails due to congestion. • The RNC determines the initial bit rate to be used in the uplink return channel from the measured traffic volume and the configured initial bit rate. an HSDP Aassociated uplink DCH return channel is needed. • Supported data rates for a return channel are 64. • If the traffic volume measurement indicates Low traffic volume(TrafVolThresholdULLow). the HS-DSCH allocation is not possible and the RNC schedules a DCH to the UE. the RNC attempts to allocate the uplink with HSDPAinitialBitrateUL. 128 and 384 kbit/s. 25 © NOKIA HSDPA_Parameters_v1_cv. the RNC attempts to allocate a return channel with configured initial bit rate(HSDPAinitialBitrateUL). the RNC attempts to allocate a return channel with the highest possible bit rate.ppt / 2006 Sept / MHL Company Confidential . • If the traffic volume measurement indicates High traffic volume(TrafVolThresholdULHigh).

• Default. 64 kbps HSDPAminAllowedBitrateUL • Defines the minimum allowed bit rate in UL that can be allocated by the PS to the HSDPA associated UL DCH when downgrading bit rate. • Default.Planning parameters in RAN05 UL return channel • HSDPAinitialBitrateUL • Defines the initial bit rate for scheduling of the HSDPA associated UL DCH.ppt / 2006 Sept / MHL Company Confidential . 64 kbps • 26 © NOKIA HSDPA_Parameters_v1_cv.

ppt / 2006 Sept / MHL Company Confidential .Associated UL DPCH bitrate – use case 1/3 27 © NOKIA HSDPA_Parameters_v1_cv.

ppt / 2006 Sept / MHL Company Confidential .Associated UL DPCH bitrate – use case 2/3 28 © NOKIA HSDPA_Parameters_v1_cv.

Associated UL DPCH bitrate – use case 3/3 29 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential .

ppt / 2006 Sept / MHL Company Confidential .HSDPA Serving Cell Change • HSDPA Serving Cell Change •HSDPA (serving cell) -> MR(e1a. serving cell) -> Cell_FACH (Target Cell) -> HSDPA (Target Cell) Cell A Service in HSDPA (Serving Cell) Switching to Cell_FACH (Target Cell) within the SHO area UE on HS-DSCH (Target Cell) Cell B HS-DSCH coverage Throughput HSDPA 128kbps or 384kbps according to parameter settings 64kbps HS-DSCH coverage DCH 0 30 © NOKIA HSDPA_Parameters_v1_cv.HSDPA mobility in RAS05 CD1 (1) .

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 DCH0/0 DCH Initial bit rate DCH Final bit rate) 31 © NOKIA HSDPA_Parameters_v1_cv.Details on Cell Change via cell-FACH • HSDPA Serving Cell Change via Cell-FACH feature is used only in intra frequency handover cases. the user in HO area will be moved to Cell-FACH. 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.ppt / 2006 Sept / MHL Company Confidential . 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 throughput then the HSDPA user penalty timers are used on Cell-FACH • If the HSDPA user moves to non-HSDPA cell.

CHANNEL TYPE SELECTION HS-DSCH is selected if all of the following conditions are met: 1. 9. HsdschGuardTimerHO and HsdschGuardTimerLowThroughput guard timers are not runnig • Both guard timers are operator-configurable parameters UE is not performing inter-frequency or inter-system measurements Active set size = 1 (RAN05) UE does not have DCHs scheduled with bit rates higher than 0kbps. condition (A or B. 6.1) • No multiRAB in RAN05 • AMR + HSDPA possible in RAN05. 10. 5. HS-DSCH physical layer category is supported 11. 3. A) PtxNC<=PtxtargetHSDPA B) Ptxtotal<=PtxtargetHSDPA 32 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential . depending on the HSDPApriority parameter) has to be valid. 2.1 The number of simultaneous HS-DSCH allocations in the BTS/cell is below the maximum number. If there is no existing MAC-d flow in the cell. 8. 7. 4. • RAN05 only interactive and background traffic classes are supported UE capability supports HS-DSCH The cell supports HSDPA and HS-DSCH is enabled in the cell No multi-RAB (RAN05) or supported multi-RAB combination (RAN05. Traffic class and traffic handling priority are allowed on HS-DSCH • The operator can configure which traffic classes and handling priority are allowed to be used with HSDPA with HSDSCHQoSclasses parameter.

HSDPA Addition Window HSDPA Addition Time Identifies parameter set for intra-frequency HOs of a user having HS-DSCH transport channel allocated through RRC: Measurement Control message . HSDPA Enable RRC Release HSDPA Release Margin Average EcNo HSDPA Release Margin Peak EcNo Defines time when HS-DSCH allocation is not allowed for a UE. Enables/disables diversity HO of the stand-alone signalling link after successful RRC connection setup for the HSDPA capable UE.ppt / 2006 Sept / MHL 33 © NOKIA . Default. 5s. Company Confidential • • • HSDPAHOPSidentifier • • • • • HsdschGuardTimerHO • • • HSDPARRCdiversity (SHO of HSDPA capable UE) • HSDPA_Parameters_v1_cv.Planning parameters in RAS05 for Mobility control • HSDPAFMCS/I/Gidentifier • Identifies parameter set for inter-/intra-frequency and inter-system measurements of a user having HS-DSCH transport channel allocated through RRC: Measurement Control message. after successful channel type switching to DCH due to any HO reasons.

Mobility Parameters relevant to HSDPA FMCS Addition Window (1A) Addition Time (1A) Addition Reporting Interval (1A) CPICH Ec/No Filter Coefficient CPICH Ec/NO HHO Threshold (1F) CPICH Ec/NO HHO Time Hysteresis (1F) CPICH RSCP HHO Filter Coefficient CPICH RSCP HHO Threshold (1F) CPICH RSCP HHO Time Hysteresis (1F) HOPS HHO Margin for Average Ec/No HHO Margin for Peak Ec/No Release Margin for Average Ec/No Release Margin for Peak Ec/No CPICH Ec/No Averaging Window Enable RRC Connection Release FMCI IFHO caused by CPICH Ec/No IFHO caused by CPICH RSCP IFHO caused by UE TX Power UE TX Power Filter Coefficient UE TX Power Threshold for NRT PS FMCG GSM HO caused by CPICH Ec/No GSM HO caused by CPICH RSCP GSM HO caused by UE TX Power UE TX Power Filter Coefficient UE TX Power Threshold for NRT PS 34 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential .

Measurement Events for HSDPA Mobility • Triggering Events for Channel Type Switching Event 1A 1F 6A Description A primary CPICH enters the reporting range -channel switching to Cell_FACH A primary CPICH goes below the absolute threshold -channel switching to DCH 0/0 kbps UE Tx power exceeds the absolute threshold -channel switching to DCH 0/0 kbps • A UE with a HS-DSCH transport channel allocated can have only one cell in the active set at a time.ppt / 2006 Sept / MHL Company Confidential . but utilizes the event 1A as a trigger for a HS-DSCH MAC-d flow release and transition to the Cell_FACH state. the size of active set limited to one. that is. • Because of this. the RNC does not ad cells to the active set based on reporting event1A when a HS-DSCH transport channel is allocated to the UE. 35 © NOKIA HSDPA_Parameters_v1_cv.

•Restriction is effective after RRC-connection establishment when SRB only or SRB and DCH 0/0 is/are allocated.. allocation of a HS-DSCH transport channel to the UE is prohibited.ppt / 2006 Sept / MHL Company Confidential . •The value of the parameter HSDPARRCdiversity shall be checked immediately after a successful RRC connection setup procedure. •The operator can disable diversity handover of the RRC connection (stand-alone signalling link) of a HSDPA-capable UE with the HSDPARRCdiversity parameter to maximise the use of the HS-DSCH. HSDPARRCdiversity (1/4) 36 © NOKIA HSDPA_Parameters_v1_cv.Diversity handover of stand-alone signalling link •If the active set size is greater than one. the active set size is limited to one for the RRC connection. •If SHO of the RRC connection (stand-alone signalling link) of the HSDPA-capable UE is not allowed.

the UE reverts to periodical reporting and continues reporting after the initial report by switching to the periodical measurement reporting mode. In this case.Exception • The RNC ignores the parameter value (and allows diversity handover of standalone signalling link) if measurement event 1A is received and the reported CPICH Ec/No of the entering cell meets the following conditions (that is. HSDPA_Parameters_v1_cv. and RNC has not added the cell into the active set. ReleaseMarginAverageEcNo(n) determines the maximum allowed difference between the averaged CPICH Ec/No of the entering cell(n) and the averaged CPICH Ec/No of the serving cell correspondingly. the threshold to perform HS-DSCH to Cell_FACH transition is exceeded): EcNoDownlink + ReleaseMarginPeakEcNo(n) < EcNoNcell(n) AveEcNoDownlink + ReleaseMarginAverageEcNo(n) < AveEcNoNcell(n) (1) (2) EcNoDownlink :CPICH Ec/No of the serving cell EcNoNcell(n) : CPICH Ec/No of the entering cell AveEcNoDownlink : averaged CPICH Ec/No of the serving cell AveEcNoNcell(n) : averaged CPICH Ec/No of the entering cell • • • • • 37 © NOKIA The comparison is applied when a cell has entered the reporting range.ppt / 2006 Sept / MHL Company Confidential . The HSDPA-specific HOPS parameters are used in the equation.Diversity handover of stand-alone signalling link . ReleaseMarginPeakEcNo(n) determines the maximum allowed difference between the CPICH Ec/No of the entering cell (n) and the CPICH Ec/No of the serving cell so that active set update is not executed. and triggered event 1A.HSDPARRCdiversity (2/4) .

5 dB EcNo Averaging Window (HSDPA HOPS) = 8 38 © NOKIA HSDPA_Parameters_v1_cv.HSDPARRCdiversity (3/4) .ppt / 2006 Sept / MHL HSDPA Allocation 2 Active Set Company Confidential Stand-alone Signalling Link .Diversity handover of stand-alone signaling link Ec/No DCH AdditionWindow DCH DeletionWindow ReleaseMarginAverageEcNo ReleaseMarginPeakEcNo P CPICH 2 P CPICH 1 DCH Addition Time DCH Deletion Time Call Start Periodic MR (e1A) ASU MR (e1B) ASU HSDPARRCDiversity: Not Allowed Addition Window (HSDPA FMCS) = 0dB Addition Time (HSDPA FMCS) = 1280ms EcNo Filter coefficient (HSDPA FMCS) = 800ms SHO of the HSDPA Capable UE (RNC) = disabled Enable RRC release (HSDPA HOPS) = enabled Release Margin Average EcNo (HSDPA HOPS) = 2dB Release Margin Peak EcNo (HSDPA HOPS) = 3.

ppt / 2006 Sept / MHL Company Confidential HSDPA Resumption Timer .HSDPARRCdiversity (4/4) .Diversity handover of stand-alone signaling link Ec/No DCH AdditionWindow ReleaseMarginAverageEcNo ReleaseMarginPeakEcNo P CPICH 2 indow DCH DeletionW P CPICH 1 DCH Addition Time DCH Deletion Time Call Start Periodic MR (e1A) ASU MR (e1B) ASU HSDPA Allocation HSDPARRCDiversity: Not Allowed * HSDPA enabled for both Serving & Target Cells 39 © NOKIA Stand-alone Signalling Link DCH Allocation HSDPA_Parameters_v1_cv.

40 © NOKIA HSDPA_Parameters_v1_cv.EnableRRCrelease (1/4) .disabled Measurement event 1A triggered HS-DSCH MAC-d flow release and parameter EnableRRCrelease is disabled: UE is transferred to the CELL_FACH state and the radio bearer is mapped to the FACH with the RRC: Radio bearer reconfiguration procedure.ppt / 2006 Sept / MHL Company Confidential .

disabled Ec/No HSDPA AdditionWindow P CPICH 1 HSDPA AdditionTime time Addition Window (HSDPA FMCS) = 0dB Addition Time (HSDPA FMCS) = 1280ms EcNo Filter coefficient (HSDPA FMCS) = 800ms SHO of the HSDPA Capable UE (RNC) = disabled Enable RRC release (HSDPA HOPS) = disabled Release Margin Average EcNo (HSDPA HOPS) = 2dB Release Margin Peak EcNo (HSDPA HOPS) = 3.5 dB EcNo Averaging Window (HSDPA HOPS) = 8 41 © NOKIA HSDPA allocation MR(e1A) FACH cell update RB_Reconfiguration (FACH) HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential .EnableRRCrelease (2/4) .

ppt / 2006 Sept / MHL Company Confidential . the UE reverts to periodical reporting. If the RNC receives measurement event 1A and the EnableRRCRelease parameter is enabled.EnableRRCrelease (3/4) . Based on the periodic measurement reporting mode and the control parameters. This means that the UE continues reporting after the initial report by switching to periodical measurement reporting mode. EnableRRCRelease indicates whether the RRC connection release (excluding emergency calls) is allowed due to non-optimum fast closed loop power control. HS-DSCH MAC-d flow release is not allowed to be triggered directly. For users with a HS-DSCH. CPICH Ec/No of the neighbouring cell (EcNoNcell) and the ReleaseMarginAverageEcNo and ReleaseMarginPeakEcNo control parameters. the RNC’s decision on HSDSCH MAC-d flow release is based on CPICH Ec/No of the serving cell (EcNoDownlink). When a cell has entered the reporting range and triggered event 1A and the RNC has not added the cell into the active set. As the EnableRRCRelease parameter is enabled. the UE is transferred to the CELL_FACH state and the radio bearer is mapped to the FACH with the RRC: Radio bearer reconfiguration procedure if the following conditions are effective: (1) EcNoDownlink + ReleaseMarginPeakEcNo(n) < EcNoNcell(n) (2) AveEcNoDownlink + ReleaseMarginAverageEcNo(n) < AveEcNoNcell(n) 42 © NOKIA HSDPA_Parameters_v1_cv.enabled Measurement event 1A triggered HS-DSCH MAC-d flow release and parameter EnableRRCrelease is enabled: For users other than HS-DSCH allocated.

EnableRRCrelease (4/4) .enabled Ec/No HSDPA AdditionWindow ReleaseMarginAverageEcNo ReleaseMarginPeakEcNo P CPICH 1 HSDPA AdditionTime time Addition Window (HSDPA FMCS) = 0dB Addition Time (HSDPA FMCS) = 1280ms EcNo Filter coefficient (HSDPA FMCS) = 800ms SHO of the HSDPA Capable UE (RNC) = disabled Enable RRC release (HSDPA HOPS) = enabled Release Margin Average EcNo (HSDPA HOPS) = 2dB Release Margin Peak EcNo (HSDPA HOPS) = 3.5 dB EcNo Averaging Window (HSDPA HOPS) = 8 HSDPA allocation FACH cell update RB_Reconfiguration (FACH) Periodic MR(e1A) 43 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential .

Range and step 0. step 1 s Default value 5 s 44 © NOKIA HSDPA_Parameters_v1_cv... Timer is not applied if UE is transferred directly to the CELL_FACH state due to reporting event 1A.HsdschGuardTimerHO HS-DSCH guard time after switching to DCH due to HO The parameter determines a period of time during which the HS-DSCH allocation is denied after successful channel type switching from HS-DSCH to DCH 0/0 kbps due to handover reasons(e1F. e6A).ppt / 2006 Sept / MHL Company Confidential .30 s.

Mobility in RAS05+CD1 • Mobility in RAS05 • Serving cell change via FACH • HSDPA selection in call setup • Mobility in RAS05+CD1 • Resumption timer • Improvement in HS-DSCH to FACH transition (target cell information) 45 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential .

ppt / 2006 Sept / MHL Company Confidential .Resumption timer (RAS05+CD1) • HSDPA resumption timer switches the user from DCH to HS-DSCH. when UE enters HSDPA area The conditions preventing HSDPA allocation in HSPDA coverage area to HSDPA capable UE are: • More than one serving cell (Soft Handover) • Multi-RAB combination (not supported) • Lack of HSDPA capacity in the cell Cell A Service NRT DCH R99 coverage Throughput HSDPA 128kbps or 384kbps according to parameter settings 64kbps (initial bitrate) Switching to HS-DSCH when not in SHO area Cell B HS-DSCH coverage Download complete DCH 0 46 © NOKIA HSDPA_Parameters_v1_cv.

if the Active set size is still 1. • Switching to HS-DSCH is tried after the timer expires. 47 © NOKIA HSDPA_Parameters_v1_cv.ppt / 2006 Sept / MHL Company Confidential . when DCH0/0 is allocated. • Normal HSDPA selection procedure is applied after a capacity request. • Switching happens via DCH0/0. • Timer started when HSDPA capable UE having DCH NRT enters into HSDPA capable cell and Active set size=1.Resumption timer • RNP parameter in RNC.

Active set size=1 after this Active Set Update (no SHO anymore). 4s resumption timer applied before.DCH to HS-DSCH switch (test case in NTN) • Resumption timer started when Active set size =1.ppt / 2006 Sept / MHL Company Confidential .7 08:31.3 08:30. • Switching to HS-DSCH tried after the timer expires. RB reconfiguration to HS-DSCH EventId RRCD RRCU RRCD RRCD RRCU RRCD RRCU RRCD RRCU RRCU RRCD Application throughput 1500000 1000000 bps 500000 0 0 10 20 s 30 40 50 DCH NRT HS-DSCH Time 08:24.8 08:33.5 08:30. The data gap is about 6s when measured with Ethereal. • Resumption timer value in this case 4s.7 08:30.8 08:32.1 08:29.8 08:25.8 08:24.7 08:32. Resumption timer started. RB reconfiguration to DCH0/0.5 seconds gap according signaling.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" 48 © NOKIA HSDPA_Parameters_v1_cv. ~2.

49 © NOKIA HSDPA_Parameters_v1_cv.Improved HS-DSCH to cell_FACH switching (RAS05+CD1) • Target cell (cell with best CPICH Ec/No in the measurement set) informed in the RB reconfiguration message. as the UE goes directly to strongest cell in cell_FACH.ppt / 2006 Sept / MHL Company Confidential . Scrambling code of the strongest cell in the measured set informed to UE. when UE is commanded to cell_FACH • There is no need for cell reselection in cell_FACH.