HSDPA Channels and Features

HS-PDSCHHS-PDSCH: High-Speed Physical Downlink Shared ChannelTransfer of actual HSDPA data5 - 15 code channelsQPSK or 16QAM modulationDivided into 2 ms TTIsFixed SF16

up to 15 HS PDSCHsHSPDSCHCodeSet HS-PDSCH code set; WCEL; (-) (-) (5 codes)

Examples00000 00000 100000 = always 5 codes reserved (default)11010 10100 100000 = number of reserved codes adjustable (5, 8, 10, 12, 14 or 15 codes, recommended)0-4 codes always disabled11-15 codes6-10 codesHS-PDSCH code set parameterSpecifies whether number of codes channels reserved for HSDPA is fixed* or dynamically adjustableMinimum 5 code channels / Maximum 15 codes channelsPossible numbers of code channels enabled / disabled bit wise# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRM & parameters:Module ObjectivesAt the end of the module you will be able to:

Explain the physical layer basics of HSDPA technologyList the key changes brought by HSDPA and their impact on the network and on the protocol model Explain HSDPA RRM and the related parameters in detail, including packet scheduling, resource allocation, mobility and channel type selection

# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRM: ContentsHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU40 RU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection & SwitchingAssociated UL DCHAppendix# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA Principles

High Speed Downlink Packet Access (HSDPA) based on: Node B decisions Multi-code operation Fast Link Adaptation Adaptive Modulation & Coding AMC Fast Packet Scheduling Fast H-ARQ Fast 2 ms TTI* Downwards Compatibility with R99 (shared or dedicated carrier)* TTI = 1 Subframe = 3 Slots = 2 msH-ARQ: Hybrid Automatic Repeat Request

Motivation: enhanced spectrum efficiency higher peak rates >> 2 Mbps higher cell throughput reduced delay for ACK transmission3GPP Rel. 5; TS 25.308:HSDPA Overall Descriptionup to 15 HS PhysicalDL Shared ChannelsHSDPAenabledWCEL; 0 = disabled; 1 = enabled# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Adaptive Modulation & Coding (1/2)IQ000000100011000110001010101110011100111011111101010001100111010116QAM4-Bit KeyingQPSK2-Bit KeyingQI(1,1)(0,1)(1,0)(0,0)HSDPA uses QPSK 16QAM 64QAM*dynamically based on quality of the radio link* defined in 3GPP Rel. 7 / implemented with NSN RU20# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Adaptive Modulation & Coding (2/2)BitRateMatchingPuncturing /RepetitionTurbo Coding1/3BitBitBitBitBitBitBitBitBitEffectiveCode Rate:1/4 - 3/4 HSDPA Adaptive Coding based on the R99 1/3 Turbo Coding Rate Matching: Puncturing or Repetition code rate: 1/6 4/4 dynamically based on quality of the radio link# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#C1,0 = [1]C2,1 = [1-1]C2,0 = [11]C4,0 = [1111]C4,1 = [11-1-1]C4,2 = [1-11-1]C4,3 = [1-1-11]C8,0 = [11111111]C8,1 = [1111-1-1-1-1]C8,2 = [11-1-111-1-1]C8,3 = [11-1-1-1-111]C8,4 = [1-11-11-11-1]C8,5 = [1-11-1-11-11]C8,6 = [1-1-111-1-11]C8,7 = [1-1-11-111-1]C16,0 = [.........]C16,1 = [.........]C16,15 = [........]C16,14 = [........]C16,13 = [........]C16,12 = [........]C16,11 = [........]C16,10 = [........]C16,9 = [.........]C16,8 = [.........]C16,7= [.........]C16,6 = [.........]C16,5 = [.........]C16,4 = [.........]C16,3 = [.........]C16,2 = [.........]SF = 1248SF = 16256512...SF = 16 240 ksymb/sMulti-Code operation:1..15 codes 0.24 .. 3.6 Msymb/sMulti Code Operation (1/3)# Nokia Siemens Networks RN31679EN30GLA1

RN31679EN30GLA1HSDPA RRM & parameters#Link adaptation algorithmGeneration of CQImeasured :UE monitors EC/I0UE reads PHS-PDSCH SIG (L3/RRC signalling)UE reports CQImeasured every 4 ms (NSN solution)Increased CQI feedback cycle (for non CPC users) is enabled if MassEventHandler is enabled & number of serving HSDPA users in the cell MEHHSDPAUserNbrCQI & MEHCQIFeedbackCycle (CQI value ) > CQI feedback cycle value 4 ms3) CQI Correction in Node BNode B corrects reported CQImeasured to CQIcompensated based on:actual HS-PDSCH power PHS-PDSCH TRUENumber of ACK & NACK4) Link Adaptation decision: Node B decides about TB size for next sub-frame:ModulationCoding rateNumber of codesCQI Reporting & Link Adaptation

up to 15 HS PDSCHsP-CPICHHS DPCCH (ACK; CQI)HS SCCHCQI used for: Link Adaptation decision Packet Scheduling decisionACK/NACK used for: H-ARQ process Link Adaptation decision HS-SCCH power adaptationRemember:* UE internal (proprietary) processPHS-PDSCH: HS-PDSCH transmission powerTB: Transport BlockUE observesP-CPICH (Ec/Io) CQImeasured*CQImeasured*# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#CQI Compensation (1/3)CQImeasuredUE generates CQImeasured assuming Tx power PHS-PDSCH SIG = PCPICH + + calculated by RNC: = f x Min(PtxMaxHSDPA, PtxMax PtxNonHSDPA) PCPICH PHS-PDSCH SIG = (f x Min(PtxMaxHSDPA, Ptxmax PtxNonHSDPA)) [dBm] +

= Reference Power Adjustment (Power Offset) [dB] CQI tablesPtxMax = max. cell powerPtxNonHSDPA = total power allocated to R99 & DL control channels (latest report is taken)PtxMaxHSDPA = max. allowed HSDPA power signalled to UE in case of HS-DSCH setup Serving cell changef = 0.7 for static HS-PDSCH power allocationf = 0.5 for dynamic HS-PDSCH powerCQI Compensation in Node BNode B compensates CQI from differences between assumed HS-PDSCH Tx power & actual HS-PDSCH Tx power PHS-PDSCH TRUEPart of HSDPA power used for HS-SCCHHS-PDSCH power can vary because of dynamic power allocation

Offset X used to convert reported CQImeasured into compensated CQIcompensated

CQIcompensated = CQImeasured + X [dB]X = PHS-PDSCH TRUE (PCPICH + + ) A [dB]correction A estimated by outer loop link adaptation algorithm

# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#BTS may allocate all unused DL power up to maximum cell powerall power available after DCH traffic, HSUPA control & common channels can be used for HSDPAPtxNCPtxNRTPtxHSDPAPtxMax = min (PtxCellMax, MaxDLPowerCapability)PtxNonHSDPADynamic HS-PDSCH Power Allocation (1/7)PtxCellMaxCell maximum transmission power0..50 dBm; 0.1 dB; 43 dBmMaxDLPowerCapability: 0..50 dBm; 0.1 dB; -# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Static & Dynamic Allocation (3/3)128128128Available CCAllocated CCBlocked CCSF16SF3232SF64646464SF256256256256256256256256256256256256256256256256128128128128128128128SF128+14 x SF16HS-PDSCHCPICH AICHS-CCPCH1S-CCPCH2HS-SCCHHS-SCCHHS-SCCH326464256256256256256256256256128128128128SF16E-RGCHE-HICHE-AGCHMaximum of 14 HS-PDSCH codes possible with 3 HS-SCCH & HSUPAP-CCPCH PICH# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#TNLMAC-dDCHFPDCHFPMAC-dTNLNode BIubRNCRLCRLCPHYPHYTNLMAC-dMAC-hsMAC-ehsHS-DSCH FPMAC-dTNLUEUuNode BIubRNCRLCRLCMAC-d flowHS-DSCHPHYPHYUEUuDCHDPCHHS-PDSCHR99HSDPA(R5)(e)hs: (enhanced) high speedTNL : Transport Network LayerHSDPA Protocol ModelMAC-hsMAC-ehsHS-DSCH FPHSDPA(R7)# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#MAC: Medium Access Control MAC TS 25.321Mapping of logical channels onto transport channelsMultiplexing of multiple logical channels onto a single transport channel, e.g. of 4 signalling radio bearers (SRB) onto single DCHComplete MAC multiplexing for user plane data currently not supportedMultiplexing requires the addition of a MAC headerMAC entities on network side distributed between RNC and Node B

MAC-hssupports HSDPA with 3GPP Rel. 5 Tasks of MAC-hs within the Node BFlow control (see section packet scheduling)Packet scheduling (see section packet scheduling)H-ARQ (see section layer 1 re-transmission)Transport format selection (see section link adaptation)Tasks of MAC-hs within the UEHARQ (see section layer 1 re-transmission)Disassembly of transport blocksRe-orderingHeader & payload Payload: Concatenating of one or more MAC-d PDU into single MAC-hs PDUHeader: 21 bits assuming single MAC-d PDU size

MAC-ehssupports enhanced HS-DSCH functions of 3GPP Rel. 7 - 9must be configured to support features such as: 64QAM (RAN1643), MIMO (RAN 1642), flexible RLC (RAN1638), Dual-Cell HSDPA (RAN1906)Concepts of MAC Layer, MAC-hs & MAC-ehs# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Physical Channel OverviewHS-PDSCHHigh-Speed Physical DL Shared ChannelHS-SCCHHigh Speed Shared Control Channelassociated DCHDedicated Channel (Rel. 99)HS-DPCCHHigh Speed Dedicated Physical Control Channel

Node BMAC-hsF-DPCHFractional Dedicated Physical Channel (Rel. 6/7)# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HS-DPCCHUL HS-DPCCH: High-Speed Dedicated Physical Control ChannelMAC-hs Ack/Nack information (send when data received)Channel Quality Information (CQI reports send every 4ms, hardcoded period)Fixed SF 256HARQ-ACK(10 bit)1 Slot = 2560 chip2 Slots = 5120 chipSubframe # 0Subframe # iSubframe # N1 HS-DPCCH Subframe = 2ms CQI (20 bit)Channel Quality IndicationTS 25.2124: CQI values = 0 (N/A), 1 .. 30; steps: 1;1 indicating lowest, 30 highest air interface quality # Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU40 RU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection and SwitchingAssociated UL DCHAppendix

# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#SummaryCharacteristicRU10RU20RU30RU40HSDPA users per cell 64 72 (RAN1668) 72 128 (RAN2124)ModulationQPSK/16QAMQPSK/16QAM & 64QAM (RAN1643)QPSK/16QAM/64QAMQPSK/16QAM/64QAMMIMONoYes (2x2) (RAN1642)YesYesDual-Cell HSDPANoYes (RAN1906)DC-HSDPADC-HSDPADB DC HSDPA (RAN2179)Data rate per UEup to 14 Mbpsup to 42 Mbpsup to 42 Mbps 84 Mbps (RAN 1907)up to 84 Mbps (RAN1907)Traffic ClassesInteractive + Background + Streaming+ CS Voice over HSPA (RAN1689)all traffic classesall traffic classes

Packet SchedulerProportional Fair (PF)+ QoS Aware HSPA SchedulingPF + QoS aware schedulingPF + QoS awareschedulingPF + QoS awarescheduling

HSDPA Multi-RABmultiple RAB HSDPA + AMRmultiple RAB HSDPA + AMRmultiple RAB HSDPA + AMR, +CS64 Conv.multiple RAB HSDPA + AMR, +CS64 Conv.Code Multiplexing(Scheduled users per TTI)Yes (up to 3)Yes (up to 4)Yes (up to 4)Yes (up to 4)UL associated DCH16, 64, 128, 384 Kbps16, 64, 128, 384 Kbps16, 64, 128, 384 Kbps16, 64, 128, 384 KbpsDB: Dual Band# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Feature activationMost enhanced features must be licensed individually and are Must be activated by setting individual off / on parameterSome features can be activated on cell level, others on WBTS or even RNC level onlyFeature ActivationHSDPAenabledWCEL; 0 = disabled; 1 = enabledHSDPA48UsersEnabledWCELRNC (till RU20 On Top), RNFC (from RU30); 0 = disabled; 1 = enabledHSDPA64UsersEnabledWCEL; 0 = disabled; 1 = enabledHSDPA14MbpsPerUserWBTS; 0 = disabled; 1 = enabledHSDPAMobilityServing HS-DSCH cell change & SHO on/off switchRNC (till RU20 On Top), RNFC (from RU30); 0 = disabled; 1 = enabledHspaMultiNrtRabSupportHSPA multi RAB NRT supportWCEL; 0 = disabled; 1 = enabled HSDPADynamicResourceAllocationHSDPA Dynamic Resource AllocationRNC WCEL(till RU20 On Top), RNFC (from RU30); 0 = disabled; 1 = enabled HSDPA16KPBSReturnChannelHSDPA 16 Kbps UL DCH return channel on/offRNC (till RU20 On Top), RNFC (from RU30); 0 = disabled; 1 = enabled HSPA72UsersPerCellWCEL; 0 = disabled; 1 = enabledif enabled, max. 72 HSDPA/HSUPA users can be supported per cell.HSPA128UsersPerCellWCEL; 0 = disabled; 1 = enabledif enabled, max. 128 HSDPA/HSUPA users can be supported per cell.RU20/30HSDPA64QAMAllowed; MIMOEnabled; DCellHSDPAEnabled; MIMOWith64QAMUsageWCEL; 0 (Disabled), 1 (Enabled)DCellAndMIMOUsageWCEL; 0=DC-HSDPA and MIMO disabled; 1=DC-HSDPA and MIMO w/o 64QAM enabled; 2=DC-HSDPA and MIMO with 64QAM enabledFDPCHEnabled; CPCEnabledWCEL; 0 (Disabled), 1 (Enabled)HSPAQoSEnabledRNC WCEL; 0..4; 1; 0 = disabled0 = QoS prioritization is not in use for HS transport1 = QoS prioritization is used for HS NRT channels2 = HSPA streaming is in use3 = HSPA CS voice is in use4 = HSPA streaming & CS voice are in useRU40# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Cell Group DefinitionSCHs under the same Node B should not overlap with each otherdefine for each sector offset relative to BTS frame number with parameter TcellCells with offsets within certain range form one cell groupGroup 1 offset = 0-512 chipsGroup 2 offset = 768-1280 chipsGroup 3 offset = 1536-2048 chipsGroup 4 offset = 2304 chips

0 chips256 chips512 chipsBTS referenceSCHBTS referenceSCHBTS referenceSCHTcellFrame timing offset of a cellWCEL; 0..2304 chips; 256 chips; no default# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#

6 users4 users6 users6 users9 users1 usersMinimum Baseband / 16 users per cellShared Packet Scheduler for cell groupmax. 5 codes allocated (HS-PDSCHcodeset = 00000 00000 10000)max. 16 HSDPA users per cell group (HSDPA48/64usersEnabled & HSPA72usersPerCell = disabled)no code multiplexing: MaxNbrOfHSSCCHCodes = 1FSM: Flexi System Module

16 users16 users16 usersDedicated Packet Scheduler (for each cell)max. 5 codes allocated (HS-PDSCHcodeset = 00000 00000 10000)max. 16 HSDPA users per cell (HSDPA48/64usersEnabled & HSPA72usersPerCell = disabled)no code multiplexing: MaxNbrOfHSSCCHCodes = 1

FSP: FlexiSystem Processor# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#

36 users6 users6 users6 users20 users22 users48 or 64 users per cell group / per cellShared Packet Scheduler for cell groupmax. 15 codes allocated (HS-PDSCHcodeset = 11010 10100 100000)max. 48 / 64 HSDPA users per cell group (HSDPA48/64usersEnabled = enabled & HSPA72usersPerCell = not enabled)code multiplexing with max. 3 user/TTI: MaxNbrOfHSSCCHCodes = 3FSP: FlexiSystem Processor

48/64 users48/64 users48/64 usersDedicated Packet Schedulermax. 15 codes allocated (HS-PDSCHcodeset = 11010 10100 100000)max. 48 / 64 HSDPA users per cell (HSDPA48/64usersEnabled = enabled & HSPA72usersPerCell = not enabled)MaxNbrOfHSSCCHCodes = 3 HSDPA 16 Kbps UL DCH should be enabled to avoid UL overload

HSDPA48UsersEnabledHSDPA64UsersEnabled WCEL; 0 = disabled; 1 = enabled

FSM: Flexi System Module

# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSPA 72 / 128 Users per Cell (1/3)

72/128users72/128users72/128usersUTRAN Hardware requirements: Flexi Node B must have Rel2 or Rel3 system module UltraSite Node B must have EUBBHSPA72UsersPerCellWCEL; 0 = not enabled; 1 = enabledEUBB: Enhanced UltraSite Base BandHSPA 72 users/cell: RAN1686 (RU20); HSPA 128 users/cell: RAN2124 (RU40); optional Feature RNC License Key required (On-Off)increases the number of simultaneous HSPA users to 72 / 128 per cellboth with dedicated & shared schedulerHSDPA, HSUPA, Dynamic Resource Allocation must be enabled, Continuous Packet Connectivity & F-DPCH are recommended for both RAN1686 & RAN2124, HSUPA DL Physical Channel Power Control recommended for RAN2124max. 15 codes allocated (HS-PDSCH code set = 11010 10100 10000)Code multiplexing (max. no. of HS-SCCH codes MaxNbrOfHSSCCHCodes = 4)HSDPA 16 Kbps UL DCH should be enabled to avoid UL overloadOther parameters may restrict max. number of HSPA users, e.g.: WCEL: HSDPA64UsersEnabled WCEL: HSUPA64UsersEnabled WBTS: HSUPAXUsersEnabled WCEL: MaxNumberEDCHCell WBTS: MaxNumberEDCHLCG WCEL: MaxNumberHSDSCHMACdFlows WCEL: MaxNumberHSDPAUsers WCEL: MaxNumbHSDPAUsersS WCEL: MaxNumbHSDSCHMACdFS WCEL: MEHMaxHSDPAUsersHSPA128UsersPerCellWCEL; 0 = not enabled; 1 = enabled# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#DL Code allocation in a cell depends on activated features and traffic ongoingif HSPA 72 Users Per Cell or HSPA 128 Users Per Cell is enabled, RNC allocates DL codes according to Maximum number of scheduled HSDPA user per TTI (Code Multiplexing) or Temporary maximum number of HSDPA users if Mass Event Handler is enabled (MEHMaxHSDPAUsers; WCEL; 0..128; 1; 30)MaxNbrOfHSSCCHCodes; WCEL; 1..4; 1; 1 (4 is recommended in both cases)1 E-RGCH & E-HICH codes is reserved in cell setup; max number of E-RGCH/E-HICH codes is 4 or not limitedreserved number of E-RGCH/E-HICH codes depend on number of HSUPA users, TTI (2ms or 10ms), whether the cell is serving or non-serving E-DCH cell to the UE, and scheduled or non-scheduled transmition if Paging 24 kbps feature is enabled, more DL codes are needed to separate FACH and PCH trafficPCH24kbpsEnabled; WCEL; on/off & NbrOfSCCPCHs; WCEL; 1..3; 1; 1

P-CPICHP-CCPCHAICHPICHS-CCPCHdepending on FACH / PCHconfigurationHS-SCCHE-RGCHE-HICHE-AGCH 10msE-AGCH 2msS-CPICH MIMOF-DPCHHSPA 72 / 128 Users Per Cell (2/3)DL Code allocationSF 16,0SF 32SF 64SF 128SF 2560123456789101112131415# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters# No. of HS-SCCH channels increased to 4 to schedule & control increased number of HSPA users in a cell DL code space limited dynamic DL control channel allocation mechanism introduced to maximize available codes for HS-PDSCHs HSUPA RRM (E-RGCH & E-HICH management / dynamic code allocation) if code tree resources allocated like on previous slide, following traffic is supported:15 codes @ SF16 for HSDPAsingle user per 2 ms TTI (no code multiplexing)maximum 20 HSUPA user in the cellMIMO enabledF-DPCH enabled most likely RNC will allocate another SF16 branch to increase control channel traffic reducing HSDPA SF16 codes further Traffic analysisHSPA 72 / 128 Users Per Cell (3/3)MaxNbrOfHSSCCHCodesWCEL; RU10 & earlier: 1..3; 1; 1; RU20: 1..4

Code allocation incase of 4 HS-SCCH:# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU40 RU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection and SwitchingAssociated UL DCHAppendix

# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Outer loop link adaptation algorithm correction AIf ACK received for first transmission of a packetCorrection A decreased by 0.005 dBBut not below -4 dB (maximum CQI improvement towards higher TBS)If NACK received for first transmission of a packetCorrection A increased by 0.05 dBBut not above 4 dB (maximum CQI downgrade towards lower TBS)ACK for 1st transmissionNACK for 1st transmissiontimeP0CQI Compensation (2/3)increase CQIlower CQI# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#

CQIMEASURED = 3233 bits per TB (167 K)e.g. PHS-PDSCH SIG = 37 dBme.g. PHS-PDSCH TRUE = 40 dBmX = (40 37) dB = 3 dBCQICOMPENSATED = 3 + 3 = 6461 bits per TB (230 K)X = 3 dBCQI compensation makes it difficult to map reported CQI from UE log files into expected HSDPA transport block size TBSCQI Compensation (3/3)# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Spectral Efficient Link AdaptationGood radio conditions CQICOMPENSATED, but less data to be sentNode B determines CQINEEDED required for actual serviceNode B reduces HSDPA transmission power by CQICOMPENSATED - CQINEEDEDExample:CQICOMPENSATED = 10Actual service 384 KRequires 768 bits per TBCQINEEDED = 8Power reduction = (10 8) dB = 2 dBRAN1244: Spectral Efficient Link Adaptation# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#

CQI as a function of CPICH Ec/IoMeasurement Examples (1/2)CQI improves both with increasing:EC/I0HSDPA power# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#CQI estimation differs from one type of UE to the next one Prediction of different values in spite of identical channel conditionsCQI compensation capable to remove most of these differences Almost same service experienced in spite of proprietary CQI estimation

Prior to compensationAfter compensationMeasurement Examples (2/2)# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU40 RU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection and SwitchingAssociated UL DCHAppendix

# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#

R99 & HSDPA Retransmission

TerminalBTSR99 DCHR5 HS-DSCHPacketRe-transmissionRLC ACK/NACK

Re-transmissionL1 ACK/NACKPacket

TerminalBTSRNCRNCDataflowDL control moved to BTSH-ARQ: Hybrid Automatic Repeat reQuest# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#

Hybrid Automatic Repeat Request H-ARQH-ARQ Objective:ensures reliable data transfer between UE and Node Bshort Round Trip Time between UE and networkHSDPA connection re-transmission can originate from:MAC-hs layer between UE and Node B (HARQ)RLC layer between UE and RNCTCP layer between UE and application serverRe-transmission time outafter 3rd L1 re-transmission HSDPA packet discarded (hardcoded threshold)HARQ algorithms:Chase combining CCIncremental Redundancy IRAlgorithm selected by operator on BTS levelHARQRVConfigurationWBTS; 0 = Chase Combining, 1 = Incremental Redundancy# Nokia Siemens Networks RN31679EN30GLA1ARQ: Receiver sends ACK/NACK to transmitter which re-transmits if NACK is received, receiver discards corrupted packetsH-ARQ: Like ARQ, but receiver buffers corrupted packets so they can be combined with re-transmitted onesChase Combining CCIncremental Redundancy IRHSDPA H-ARQ uses up to 8 parallel stop-and-wait SAW processes6 processes required to ensure continuous transmission with 1 HSDPA connection (1st re-transmission after 18 slots = 6 sub-frames)Multiple processes required to account for delay in receiving ACK/NACKHARQ algorithmsChase combining CCIdentical retransmissionExactly same bits transmitted during each re-transmission for the packetIncremental Redundancy IRNon-identical retransmission1st transmission has systematic bits and less or no parity bitsRe-transmission has parity bits (or more of them)Algorithm can be selected by operator on BTS level

RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU40 RU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingScheduling Types: Round Robin & Proportional FairScheduling & Code MultiplexingBasics of QoS Aware Scheduling and Application Aware RANBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection and SwitchingAssociated UL DCHAppendixHow to incorporate App Aware RAN# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Scheduler TypesSupports packet schedulersRound Robin RRProportional Fair PF (requires individual license)Type of scheduler set by HSDPA.BB.Resource.Allocation commissioning parameter

Round Robin Scheduler assigns sub-frames in rotationUser at cell edge served as frequently as user at cell centre does not account for channel conditions experienced by UELow total throughput in cell if no data have to be transferred from Node B to certain UE then the sub-frame is assigned to the next one

# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Proportional Fair PF Scheduler (1/2)TTI 1TTI 2TTI 3TTI 4USER 1 Es/N0USER 2 Es/N0Scheduled userTakes into account multipath fading conditions experienced by UEImproved total throughput in cell in comparison to round robinSub-frames assigned according scheduling metricRatio instantaneous data rate / average data rate experienced in the pastUser at cell edge served less frequently as user at cell centreEstimate of instantaneously supported user throughputBased on compensated CQICalculated average user throughput in the pastThroughput measured every 10 ms with 100 ms sliding window

# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#

Round Robin RR schedulingMax. total throughput 1100 KbpsProportional Fair PF schedulingMax. total throughput 1300 KbpsExample:Macro cell 5 codes for HSDPACarrier shared with R99Maximum total transmission power 20 WStatic HS-PDSCH + HS-SCCH powerProportional Fair PF Scheduler (2/2)# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Scheduling / HSDPA Code MultiplexingUE1UE2UE3Amount ofdata in bufferUE1UE2UE3Full bufferDifferent data amounts7878RU10 & later15 codes21058310Codes & power are divided optimally between users depending on data amount.MaxNbrOfHSSCCHCodesMax. number of HS-SCCH codesWCEL; 1..4*; 1; 1 (no Code Multiplexing)HSDPA Code Multiplexing: enables simultaneous transmission of up to 4* HSDPA UEs during 1 TTIeach simultan. served HSDPA UEs must have separate HS-SCCH 5 codes must be allocated to HS-PDSCHMAC-hs entity selects (3) best users (based on PF or QoS aware metric) for transmission in the next TTIHS-PDSCH codes & power resources shared, taking into account:how much data user has in its bufferChannel conditions of user* 3 before RU20# Nokia Siemens Networks RN31679EN30GLA1HSDPA Code Multiplexing (RAN 853; RAS06): enables simultaneous transmission of up to 3 HSDPA UEs within a single cell during 1 TTIeach of the simultaneously served HSDPA UEs must have separate HS-SCCHtotally more than 5 codes must be allocated to HS-PDSCHMAC-hs entity selects (3) best users (based on PF or QoS aware metric) for transmission in the next TTIRetransmissions (if any) are scheduled firstif best UE (PF) using less codes than cell hast available 2nd UEif the 2 scheduled UE using less codes than cell has available can 3rd UEscheduled Retransmissions are given same amount of codes & HSDPA power as in original transmissionAvailable power & codes divided evenly between selected UEs in a TTISpectral Efficient Link Adaptation (RAN 1244; RU10 & later): HS-PDSCH codes & power resources shared more efficiently, taking into account:how much data user has in its bufferChannel conditions of user

HSPA 72 users per cell (RAN1686; RU20 & later): increases max. amount of HS-SCCH codes per cell to 4; allowing multiplexing of 4 users per cell when needed.

RN31679EN30GLA1HSDPA RRM & parameters#Basics of QoS Aware Scheduling (1/4)Shortcomings of standard PFPF metric does not distinguish between traffic classesNo bit rate guarantee, i.e. no streaming services supportedInteractive service not prioritised against background one

Idea of QoS aware HSPA scheduling (RAN1262)QoS aware HSPA scheduling enabled with parameter HSPAQoSEnabledHSDPA dynamic resource allocation must be enabledStreaming servicesGuaranteed bit rate set by RNCInteractive IA & Background BG servicesOperator can set nominal bit rate (target minimum bit rate)If not defined, service treated as best effort oneOperator can set service priorities, so that IA services are scheduled more often than BG onesServices belonging to same traffic class againscheduled according PFHSPAQoSEnabledRNC WCEL; 0..2; RU20: 0..4;1; 0 = disabled0 = QoS prioritization is not in use for HS transport1 = QoS prioritization is used for HS NRT channels2 = HSPA streaming is in use (RAN1004)3 = HSPA CS voice is in use (RAN1689)4 = HSPA streaming and CS voice are in use # Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Application aware RANNew slideIPIP/UDPGTP-UInspection and inner IP packet MarkingIPDPIDPI marks inner IP packet DSCP value based on operator policiesFPMACRLCPDCPGTPUHSPDAschedulerFPSPIweightMAC-dflowsTraffic type and/or activity triggers change of initial SPI (based on DPI marking) NodeBRNC078Same BearerSame BearerSPI-mod in FPChange scheduling weight associated with the MAC-d flow

Application Aware RAN Equips operators with QoS tools for typical terminals carrying multiple applications within one bearer with HSDPA allocatedEnables prioritization of the latency sensitive data by increasing the scheduling priority at the air interface and/or demotion of non-priority P2P traffic (priority drop = P2P traffic share down), and introduces dynamic demotion of UL bulk traffic by the BTS in a single RAB caseApplications requiring the same treatment at RAN are grouped by the operator into Application Groups (up to 6) characterized with AARConfigTable (consisted of AppGrpId, DSCPCode1..5 (up to 5 applications per group), Precedence, TargetSPIforSPI0..11) Precedence value determines what SPI should be chosen when packets belonging to multiple application groups are detected by the RNC (promote/demote/do nothing)

Shortcomings of available 3GPP QoS model:not possible to differentiate QoE to UE using multiple applications within a NRT RAB i.e. to have micro-QoS within a fat pipeAppAwareRANEnabledWCEL; Disabled (0), Enabled (1); 0 Precedence RNHSPA; 1..6; 1; 255 = not defined AppGrpId RNHSPA; 1..6; 1; 255 = not defined DSCPCode1..5 RNHSPA; 0..62; 1; 255 = not defined TargetSPIforSPI0..11 RNHSPA; 0..11; 1; 255 = not defined # Nokia Siemens Networks RN31679EN30GLA1QoS Aware Scheduling and Application Aware RAN (2/4) (1/2)Scheduling weightsFor each combination of RAB QoS parameters operator can define service priorityTraffic classTraffic handling priority THPAllocation & retention priority ARPService priorities & Scheduling Priority Indicators SPIDefined by multiple parameter QoSPriorityMappingFor services on DCH service priorities just define values entering queuing and priority based scheduling (see R99 PS)For services on HS-DSCH/E-DCH or HS-DSCH/DCH services priorities define directly SPIIt is initial SPI value if AppAwareRANEnabled = 1 (dynamic SPI based on the application type and initial SPI value is set and communicated to BTS using CmCH-PI field in Frame Protocol)If HSPAQoSEnabled is disabled but AppAwareRANEnabled = 1 then initial SPI for services with HSDPA can be configured by the operator with is defined by InitialSPINRT; RNHSPA; SPI 5 (5), SPI 6 (6); SPI 5 (5)SPI mapped onto scheduling weights:define how often service of certain QoS parameter set scheduled in comparison to another one with another QoS parameter setPF scheduling extended by required activity detection RAD with delay sensitivity DS

Priority for Streaming traffic class with ARP1/2/3:PriForStreamARP1/2/3 (RNC) (0..15) ( = 1) (13/13/13)Priority for Interactive TC with THP 1 & ARP 1/2/3:PriForIntTHP1ARP1/2/3 (RNC) (0..11) ( = 1) (11/11/11)Priority for Interactive TC with THP 2 & ARP 1/2/3:PriForIntTHP2ARP1/2/3 (RNC) (0..11) ( = 1) (8/8/8)Priority for Interactive TC with THP 3 & ARP 1/2/3:PriForIntTHP3ARP1/2/3 (RNC) (0..11) ( = 1) (5/5/5)Priority for Background TC with ARP 1/2/3:PriForBackARP1/2/3 (RNC) (0..11) ( = 1) (0/0/0)ARP: Allocation & retention prioritySPI: Scheduling priority indicatorsTHP: Traffic handling priority# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#QoS Aware Scheduling and Application Aware RAN (3/4) (1/2)Mapping QoS parameter for DCHQoS parameterRAB profileServicepriorityMapping definedby QoSPriorityMappingRNC PSQueuingPriority Based SchedulingMapping QoS parameter to scheduling weights for HS-DSCH/E-DCH or HS-DSCH/DCH QoS parameterRAB profileService priorityMapping definedby QoSPriorityMappingNode B PS:Scheduling weightmodifying PFSPI: Scheduling Priority IndicatorsMapping defined bySchedulingWeightListSchedulingWeightList is BTS commissioning parameter defining Mapping QoSPriorityMapping to SchedulingWeightIf AppAwareRANEnabled = 1 then dynamic SPI setting based on the application type and initial SPI# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#QoS Aware Scheduling (4/4)Guaranteed Bit Rate GBRSet by RNC for streaming services on basis of the RAB profile

Nominal bit rate NBR = target minimum bit rateThe nominal bit rate NBR is set as the target minimum bit rate in the RNC for NRT HS-DSCHs. Can be specified by operator for NRT servicesIndividually for each SPI service priority 0..12 and Individually for UL and DLIf Application Aware RAN is enabled SPI is dynamically modified by the RNC PDCP layer but the new NBR value corresponding to the new SPI is not communicated to the BTS and BTS continues using the old NBR value. RNC ensures that the SPI promotion/demotion for NBR users is performed within the SPI range defined for NBR users

NBR: Nominal Bit RateNBRForPri0..12ULUL NBR for Priority value 0..12 (structured parameter)RNC; RU30: RNHSPA; 0..2000 K; 8 K; 0 K for all priority valuesNBRForPri0..12DLDL NBR for Priority value 0..12RNC; RU30: RNHSPA; 0..2000 K; 8 K; 0 K for all priority values# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU40 RU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationHS-SCCH & HS-DPCCH Power ControlStatic & Dynamic HS-PDSCH Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection and SwitchingAssociated UL DCHAppendix# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#

OverviewHS-PDSCHHigh-Speed Physical DL Shared ChannelHS-SCCHShared Control Channel for HS-DSCHassociated DCH*Dedicated ChannelHS-DPCCHDedicated Physical Control Channel (UL) for HS-DSCHStatic power allocationTx power fixedSlowly adjusted in dependence on HS-SCCH Tx powerDynamic power allocationAll power not needed for R99 services available for HSDPASlowly adjusted in dependence on R99 & HSDPA trafficFast power control in dependence on:- CQI- Feedback of UEFast power control parallel to DPCCH with offset for CQIACK/NACKInner loop PC basing DL TPC and CQI

WBTSUEF-DPCH*Fractional Dedicated Physical Channel* F-DPCH can be allocated in DL only if SRB can be mapped to HSPA channels# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Example:PCPICH + = 6 W (37.8 dBm)P0 = 0

CQITBSThroughputCQIPHS-SCCH4317159 K-7.7 dB(37.8 - 7.7) dBm = 30.1 dBm (1.0 W)1322791140 K-16.6 dB(37.8 - 16.6) dBm = 21.2 dBm (0.13 W)HS-SCCH inner loop power control algorithmNode B estimates HS-SCCH Tx power according to: PHS-SCCH = PCPICH + + CQI + P0

HS-SCCH Power Control (1/3)

PCPICH: CPICH power measurement power offset (see section link adaptation)CQI: power offset taken from CQICOMPENSATED by look up table (next slide)P0: correction estimated by HS-SCCH outer loop power control algorithmHS-SCCH Tx powerEstimated for each HSDPA connection individuallyUpdated with each CQI report# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HS-SCCH Power Control (2/3)HS-SCCH outer loop power control algorithmWith each feedback (ACK or NACK) from UECorrection P0 decreased by 0.005 dBBut not below -2 dB (maximum power decrease by factor 1.6)If there is no feedback from UECorrection P0 increased by 0.5 dBBut not above 4 dB (maximum power increase by factor 2.5)ACK or NACKNo feedbacktimeP00.005 dB0.5 dB# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HS-SCCH Power Control (3/3)

Variance of HS-SCCH Tx power in relatively poor channel conditions Variance of HS-SCCH Tx power in relatively good channel conditionsHS-SCCH Tx power increasesin poor channel conditionswith higher HS-PDSCH Tx powerLink budgets typically assume 0.5 W HS-SCCH Tx power at cell edgeStatic Power Allocation# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Power offsetsHS-DPCCH Tx power goes parallel to that of DPCCHfor ACK / NACK & CQI fields hardcoded power offsets in dependence on DPDCH data rate (16 / 64 / 128 / 384 K)for UL link budgets ACK / NACK offset more important than CQI oneHS-DPCCH Power ControlDPCCHDPDCH Factor2.7 dB for 16 K DPDCH9.5 dB for 384 K DPDCHCQIACK/NACKHS-DPCCH# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HS-PDSCH Power AllocationStatic Power AllocationDynamic Power AllocationPHSDPA PtxMaxHSDPAPHSDPA min(PtxMaxHSDPA, PtxCellMax)- power allocated to R99 DCH & DL control channelsFixed load target PtxTargetHSDPADynamically adjusted load target PtxTargetPSFixed overload threshold for R99Overload threshold for R99 goes parallel to load target:PtxTargetHSDPA + PtxOffsetHSDPAPtxTargetPS + PtxOffsetIn case of overload HSDPA might beIn case of overload HSDPA power might be reduced,released immediatelybut usually service not released immediatelyPriorities distinguish between R99 &Priorities distinguish between interactive & backgroundHSDPA users onlyusers as well

PtxMaxHSDPAMaximum allowed HSDPA powerWCEL; 0..50 dBm; 0.1 dB; 43 dBmPtxTargetHSDPA Target for transmitted non-HSDPA powerWCEL; -10..50 dBm; 0.1 dB; 38.5 dBmPtxOffsetHSDPAOffset for transmitted non-HSDPA powerWCEL; 0..6 dB; = 0.1 dB; 0.8 dBHSDPADynamicResourceAllocationHSDPA Dynamic Resource Allocation RNC; RU30: RNFC; 0 = disabled; 1 = enabledPtxCellMaxCell maximum transmission powerWCEL; 0 .. 50 dBm; 0.1 dB; 43 dBmPtxOffsetOffset for transmitted powerWCEL; 0 .. 6 dB; 0.1 dB; 1 dB# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Dynamic HS-PDSCH Power Allocation (2/7)No active HSDPA usersNRT DCH scheduling to PtxTarget + PtxOffset if HS-RACH isnt set up in the cellPtxTargetPS if HS-RACH is set up in the cellRT DCH admission to PtxTargetActive HSDPA usersNRT DCH scheduling to PtxTargetPS RT DCH admission to PtxTarget no RT HS-SDCHPtxTargetTot at least 1 RT HS-DSCHHSDPA activeNo HSDPA usersNo HSDPA usersPtxTarget + PtxOffsetPtxMaxPtxTargetPS PtxNCPtxNRTPtxHSDPA123PtxNonHSDPAPtxTotal# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Dynamic HS-PDSCH Power Allocation (3/7) Adjustable load target PtxTargetPSPtxTargetPSMin (minimum value)PtxTargetPSMax (maximum value, also initial value, HS-RACH is set up in the cell)PtxTargetPSMaxHSRACH (maximum value used if HS-RACH is set up in the cell)

PtxTargetPSMinMin DCH PS target for dynamic HSDPA pwr allocationWCEL; -10..50 dBm; 0.1 dB; 36 dBmPtxTargetPSMaxMax DCH PS target for dynamic HSDPA pwr allocationWCEL; -10..50 dBm; 0.1 dB; 40 dBmPtxTargetPSMaxHSRACHMax DCH target power level with HS-RACH for dynamic HSDPA pwr allocationWCEL; 0..40 dBm; 0.1 dB; 32767 dBm (Value set by the PtxTargetPSMax parameter used when the HS-RACH has been setup in the cell)PtxNCPtxNRTPtxHSDPAPtxMax PtxNonHSDPAPtxTargetPSMin (36 dBm)PtxTargetPSMax (40 dBm)PtxTargetPSPtxTargetPSMin-10..50 dBm; 0.1 dB; 36 dBmPtxTargetPSMax-10..50 dBm; 0.1 dB; 40 dBm# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters# Dynamic Load Target (4/7)Ideal load target: Ideal_PtxTargetPS Dynamic load target adjusted ifHigh DCH load or total load ANDCurrent load target deviates from ideal load target Ideal load target estimated by RNC in dependence onNon controllable traffic PtxNC = total non-controllable transmitted DCH power - power used by all HSDPA streaming users of the cell - non-controllable HSDPA powerNRT DCH traffic (sum over all weights of R99 services WeightDL_DCH)NRT HS-DSCH traffic (sum over all weights of HSDPA services WeightHS-DSCH)

PtxTargetPSMaxHSRACH if HS-RACH is set up in the cell# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Dynamic Load Target (5/7)Weights of individual services Can be set individually for each releaseR99 (structured parameter WeightDCH)HSPA (structured parameter WeightHSPA) Can be set individually for each traffic classInteractive THP1, THP2, THP3Background In case of multi-RAB the average weight of the individual RABs is taken for that userStructured parameter WeightDCHWeight of NRT DCH UE BG RABWeightDCHBG (RNC; RU30: RNHSPA) (0..100) ( = 1) (15)Weight of NRT DCH UE THP1/2/3 RABWeightDCHTHP1/2/3 (RNC; RU30: RNHSPA) (0..100) ( = 1) (90/65/40)Structured parameter WeightHSPAWeight of HSPA UE BG RABWeightHSPABG (RNC; RU30: RNHSPA) (1..100) ( = 1) (25)Weight of HSPA UE THP1/2/3 RABWeightHSPATHP1/2/3 (RNC; RU30: RNHSPA) (0.100) ( = 1) (100/75/50)1525Background4050Interactive THP36575Interactive THP290100Interactive THP1DCH weight value 0100HSDPA weight value 0100Traffic ClassIdeal Load Target - Example 2 HS-DSCH users interactive THP1 + background WeightHS-DSCH = 100 + 25 = 125 3 DCH users background WeightDL_DCH = 3 * 15 = 45 PtxMax = 43 dBm PrxNC = 37 dBm Ideal_PrxTargetPS = 37 dBm + (45 / (125 + 45)) * (43 dBm - 37 dBm) = 38.6 dBm# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Load Target Adjustment (6/7) Required informationTotal power PtxTotal measured by Node BNon HSDPA power PtxNonHSDPA measured by Node BBoth averaged according PSAveragingWindowSize (same parameter as for R99) Need for adjustment checked periodically according PtxTargetPSAdjustPeriod If adjustment neededIncrease by PtxTargetPSStepUp in case of DCH congestionDecrease by PtxTargetPSStepDown in case of HSDPA congestionPSAveragingWindowSize Load measurement averaging window size for PS WBTS; 1..20; 1; 4 scheduling periodsPtxTargetPSAdjustPeriodDCH PS target adjust period for dyn HSDPA power alloc; WBTS; 1..255; 1; 5 RRI periodsPtxTargetPSStepUpDCH PS target step up for dynamic HSDPA pwr alloc.WCEL; 0..5; 0.1; 1 dBPtxTargetPSStepDownDCH PS target step down for dynamic HSDPA pwr alloc.WCEL (0..5 dB) ( = 0.1 dB) (1 dB)# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Actions in Case of Congestion (7/7)DCH congestion only Increase PtxTargetPS by PtxTargetPSStepUp, if currently below ideal load target (but not above PtxTargetPSMax)

HSDPA congestion only Decrease PtxTargetPS by PtxTargetPSStepDown, if currently above ideal load target (but not below PtxTargetPSMin)

Both DCH & HSDPA congestion Increase PtxTargetPS, if currently below ideal load target Decrease PtxTargetPS, if currently above ideal load target# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#PtxMax 43 dBmPtxTargetPS PtxNCPtxNRTPtxHSDPA12PtxNonHSDPAPtxTotalPtxTargetPS_idealExample: HSDPA congestion1) HSDPA power congestion, if Ptxtotal PtxHighHSDPAPwrHigh threshold of PtxTotal for dynamic HSDPA pwr alloc:PtxHighHSDPAPwr (WCEL) (-10..50 dBm) ( = 0.1 dB) (41 dBm)PtxTargetPSMin-10..50; 0.1; 36 dBmPtxTargetPSMax-10..50; 0.1; 40 dBmPtxHighHSDPAPwr-10..50; 0.1; 41 dBmDecrease by PtxTargetPSStepDownin case of HSDPA congestionPtxTargetPSStepDown0..5; 0.1; 1 dB# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#2) NRT DCH power congestion, if PtxNonHSDPA PtxTargetPS - 1dB (hardcoded margin) PtxMax 43 dBmPtxTargetPS PtxNCPtxNRTPtxHSDPA12PtxNonHSDPAPtxTotalPtxTargetPS_idealExample: DCH CongestionPtxTargetPSMin-10..50; 0.1; 36 dBmPtxTargetPSMax-10..50; 0.1; 40 dBmPtxTargetPSStepUp0..5; 0.1; 1 dBIncrease by PtxTargetPSStepUpin case of DCH congestionPtxHighHSDPAPwr-10..50; 0.1; 41 dBm# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU40 RU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection and SwitchingAssociated UL DCHAppendix# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Static & Dynamic Allocation (1/3)HSPDSCHCodeSet11010 10100 100000HSPDSCHCodeSet00000 10100 100000HSPDSCHCodeSet00000 00000 100000Additionally required HSDPADynamicResourceAllocation = enabledNumber of HS-PDSCH codes (full set) HSDPA 15 Codes HSDPA 10 Codes Static code allocation 5 X X X 6 - - - 7 - - - 8 X X - 9 - - - 10 X X - 11 - - - 12 X - - 13 - - - 14 X - - 15 X - - # Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Static & Dynamic Allocation (2/3)Dynamic code allocation applied if:HSDPA dynamic resource allocation enabled (HSDPADynamicResourceAllocation)Maximum number of codes > minimum number (HSPDSCHCodeSet)BTS capable of 10/15 codesHSDPA service starts with minimum number of codes defined by HSPDSCHCodeSetCell-specific scheduler reserves HS-SCCH codes from the spreading code tree according to MaxNbrOfHSSCCHCodes

If HSDPA dynamic resource allocation disabled, 5 codes are available onlySF=8SF=4SF=2SF=1SF=161514131211109876543210HS-PDSCH..SF=8SF=4SF=2SF=1SF=161514131211109876543210HS-PDSCHRel-99 channels(& HS-SCCH)Rel-99 code area (& HS-SCCH)Shared code areaDedicated HS-PDSCH SF=8SF=4SF=2SF=1SF=161514131211109876543210HS-PDSCH..SF=8SF=4SF=2SF=1SF=161514131211109876543210HS-PDSCHRel-99 channels(& HS-SCCH)Rel-99 code area (& HS-SCCH)Shared code areaDedicated HS-PDSCH code area# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Dynamic Allocation Procedure (1/2)Periodic upgrade HSDPA service starts with minimum number of codes RNC attempts periodic upgrade according the timer HSPDSCHAdjustPeriod ifNumber of currently allocated HS-PDSCH codes < maximum allowed number supported by BTS capabilityFree SF 16 codes adjacent to currently allocated ones availableAfter upgrade enough SF 128 codes available according HSPDSCHMarginSF128 If all conditions are fulfilled, the next greater value from HS-PDSCH code set is taken

Periodic downgrade RNC attempts periodic downgrade according the timer HSPDSCHAdjustPeriod ifNumber of currently allocated HS-PDSCH codes > minimum allowed numberNot enough SF 128 codes available according HSPDSCHMarginSF128 If all condition fulfilled, the next lower value from HS-PDSCH code set is taken

HSPDSCHMarginSF128WCEL; 0..128; 1; 8# SF128 codes to be available after Code upgradeHSPDSCHAdjustPeriodRNC RU30: RNHSPA; 1..60; 1; 10s# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Dynamic Allocation Procedure (2/2)Number of allocated SF16 codesDPCHOverHSPDSCHThresholdset relative to max. number of codes6789101112131415Maximum code set5Code congestion eventsRT request congested due to lack of code HS-PDSCH downgrade in any caseNRT request congested due to lack of code HS-PDSCH downgrade only, if actually for HSDPA too much SF 16 codes in use according DPCHOverHSPDSCHThreshold

Limitations of congestion triggered downgradeNot below minimum allowed number of HS-PDSCH codesHighest still possible number of codes according HSPDSCHCodeSet is takenMinimum code setHSPDSCHCodeSetWCEL; 5..15; 1; 5DPCHOverHSPDSCHThresholdWCEL; 0..10; 1; 5Code tree optimizationCode tree optimization procedure tries to re-arrange DPCH codes to make room for HS-PDSCH code upgradeDPCHs having SRB DCH only are not allowed to be re-arrangedCodeTreeOptimisationWCEL; 0 = disabled; 1 = enabled# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingHSDPA Power AllocationHSDPA Code Allocation (Basics)HSDPA MobilityServing Cell ChangeInter-RNC MobilityCell Re-selectionInter-frequency MobilityDirected RRC Connection SetupHSDPA Channel Type Selection & SwitchingAssociated UL DCHAppendix# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Parameter TemplatesFMCS/I/GId identifies parameter set for intra-, inter-frequency & inter-system measurementsFMCS/G/I; 1..100; 1; no defaultHSDPAFMCS/I/GIdentifier Identifies FMCS/I/G parameter set to be applied for a HSDPA service within a certain serving cellWCEL; 1..100; 1; no defaultRTwithHSDPAFMCS/I/GIdentifierHSDPA FMCS/I/G identifier for AMR multi-serviceWCEL; 1..100; 1; no defaultIdentifies FMCS/I/G parameter set to be applied for a HSDPA + AMR multi-RAB service within a certain serving cellS:Intra-FrequencyI:Inter-FrequencyG:Inter-System WCELL ADJG / L ADJI ADJS WBTS RNC FMCS FMCI FMCG 100 100 100 HOPS 100 HOPI 100 HOPG 100 32 48 32 ADJD HOPS 100 32 HOPSIdHOPS identifier: identifies parameter set for intra-frequency mobilityHOPS; 1..100; 1; no defaultHSDPAHOPSIdentifierADJS; 1..100; 1; no defaultidentifies parameter set to be applied for a HSDPA service to move to a certain adjacent cellRTwithHSDPAHOPSIdentifierHSDPA HOPS identifier for AMR multi-serviceADJS; 1..100; 1; no defaultRNFCRNMOBI# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA MobilityServing Cell Change SCC (1/5): CandidateInitial cell selection1 cell active only: just attempt to establish serviceMore than 1 cell activeInitial selection of Serving Cell based on latest reported Ec/I0To be candidate, HSDPA capable cell must fulfil following condition:

Serving cell is chosen in order of EC/I0If allocation of HS-DSCH fails due to any reason, next best candidate cell is attemptedEC/I0 (active cell*) EC/I0 (best cell) HSDPAServCellWindowHSDPAServCellWindowCPICH Ec/Io window for serving HS-DSCH cell selectionRNC, RU30:RNMOBI; 0..6; 0.5; 2 dB* Serving CellMax. allowed difference between the best cell in the Active Set & the Serving HSDSCH cell. If Serving HS-DSCH cell out of this window Serving HS-DSCH cell change procedure initiated.Methods to handle HSDPA mobilityServing HS-DSCH cell changeCell reselection with HS-DSCH - FACH channel type switching ( Appendix)HSDPAMobilityServing HS-DSCH cell change & SHO on/off switchRNC, RU30:RNFC; 0 = HSDPA cell reselection 1 = Serving HS-DSCH cell change# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Serving Cell Change (2/5): Ec/Io basedPeriodical Intra-frequency EC/I0 measurements started when:HS-DSCH MAC-d flow active AND Active set size > 1 (event 1a)Measurements stopped if either of the above criteria not trueCPICH EC/I0 measurement reporting by UE:Higher layer filtering for measurement results before reporting by EcNoFilterCoefficientPeriodical reporting with reporting interval defined by HSDPACPICHReportPeriodRNC averages reports over HSDPACPICHAveWindowEC/I0 based Serving Cell change triggered if:Ec/I0 (server) < EC/I0 (best cell) HSDPAServCellWindow ANDEC/I0 (server) < HSDPACPICHEcNoThresholdEcNoFilterCoefficientFMCS; k = 0..6; 1; k = 3HSDPACPICHReportPeriodRNC, RU30:RNMOBI; 0.25, 0.5, 1, 2, 3, 4, 6, 8, 12; 0.5 sHSDPACPICHAveWindowRNC, RU30:RNMOBI; 1..10; 1; 3Addition windowCPICH 1CPICH 2EC/I0timeNew cell detectedPeriodic reportsServing cell change EC/I0 thresholdServing cell change triggeredperiodic reports as long process is runningHSDPAServCellWindowServing Cell change windowRNC, RU30:RNMOBI; 0..6; 0.5; 2 dBHSDPACPICHEcNoThresholdRNC, RU30: RNHSPA; -20..0; 0.5;-5 dB# Nokia Siemens Networks RN31679EN30GLA1HSDPACPICHEcNoThreshold: determines the absolute CPICH Ec/No threshold for the serving HS-DSCH cell change procedure. If the value of the CPICH Ec/No measurement in the serving HS-DSCH cell is above the threshold, serving HS-DSCH cell change is not initiated due to CPICH Ec/No reason.RN31679EN30GLA1HSDPA RRM & parameters#Serving cell change triggeredServing Cell Change (3/5): SIR error basedSIR error based Serving Cell change triggered if:SIRerror (Server) < HSDPASIRErrorServCellSIRerrortimePeriodic reports as long HSDPA service runningServing cell change SIRerror thresholdHSDPA service establishedHSDPASIRErrorServCellRNC, RU30: RNMOBI; -10..0; 0.5; -3 dBfor Inter Node B & intra Node B inter-LCG cell change only (not applicable for intra Node B inter-LCG )Periodical SIR error measurements started whenHS-DSCH MAC-d flow activedifference between actual SIR & SIRtarget: SIRerror = SIR SIRtargetMeasurement reporting by Node BHigher layer filtering for measurement results before reporting byHSDPASIRErrorFilterCoefficientPeriodical reporting with reporting interval defined byHSDPASIRErrorReportPeriod (if set to 0 SIR measurement is not used as criteria for SCC)RNC averages reports over HSDPASIRErrorAveWindowHSDPASIRErrorFilterCoefficientRNC, RU30: RNMOBI; k = 0..10; 1; 5HSDPASIRErrorReportPeriodRNC, RU30: RNMOBI; 0..10; 0.5; 0.5 sHSDPASIRErrorAveWindowRNC, RU30: RNMOBI; 1..10; 1; 3# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Serving Cell Change (4/5): other triggerMethodTriggerAS updateEvent 1BEvent 1CEvent 6F/6GHO to D-RNCAS update for Serving Cell to D-RNCon Serving Cell# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Serving Cell Change (5/5)Target cell selection criteriaDynamic Resource Allocation disabledCell having HSDPA power allocated already chosen as serving cellOtherwise serving cell chosen in order of EC/I0Dynamic Resource Allocation enabledServing Cell is chosen in order of EC/I0If serving cell change triggered by Ec/I0 or SIRerrorneed SIRerror (target) HSDPASIRErrorTargetCellIf triggered by other event:need SIRerror (target) HSDPASIRErrorServCell HSDPASIRErrorTargetCellRNC, RU30: RNMOBI; -10..0; 0.5; -2 dBTiming Constraintsmin. time interval between consecutive Serving HS-DSCH Cell changes based on Ec/I0: HSDPACellChangeMinIntervalmax. number of repetitive Serving HS-DSCH Cell changes HSDPAMaxCellChangeRepetition during predefined time period HSDPACellChangeRepetitionTimeif exceeded, HS-DSCH released & switched to DCH0/0 or DCH with initial bit rateHSDPACellChangeMinIntervalRNC , RU30: RNMOBI; k = 0..10; 1; 3 sHSDPACellChangeRepetitionTimeRNC, RU30: RNHSPA; 0..60; 1; 10 sHSDPAMaxCellChangeRepetitionRNC, RU30 RNHSPA; 1..16; 1; 4HSDPASIRErrorServCellRNC, RU30: RNMOBI; -10..0; 0.5; -3 dB# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Inter-RNC MobilityWith RAS 06Inter-RNC HS-DSCH serving cell change & relocation at the same timeNo flow of user data over IurSwitch back to DCH not required, but nevertheless interruption of HSDPA service by the mobility proceduresWith RU20First inter-RNC serving cell change, then relocationFlow of user data over Iur, when inter-RNC neighbour becomes new serving cellHSDPA service not interrupted by the mobility procedures

RNC

RNC

ABCAS={A,B,C}Normal SHO for A-DCHAS={A,B,C}C= best cell, HS-DSCH data over IurAS={C}Trigger relocation# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Inter-frequency Mobility (Optional feature)Trigger for IFHO / ISHO process in case of active HSDPA serviceEvent 1F (too low Ec/I0 or RSCP for all active cells)Event 6A (too high UE Tx power)Too high DL RL powerUL quality deteriorationIMSI based HOCapability based HO

General rule for HHO processChannel type switch HS-DSCH to DCH for ISHONo channel type switch for IFHO

Allowed transitions for IFHO processDCH/DCH toDCH/HSDPAHSUPA/HSDPADCH/HSDPA toDCH/DCHDCH/HSDPAHSUPA/HSDPA# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Directed RRC Connection Setup (1/8)Enhanced functionalityMore than 2 layers supportedCan be restricted to certain types ofservicesLoad balancing appliedR99 directed RRC connection setupsimultaneously supportedLayering in Cell_FACH supported(same rules as for RRC con. setup)

HSDPALayeringCommonChEnabled HSDPA layering for UEs in common channels enabledWCEL; 0 = disabled; 1 = enabledBasic functionalityOnly for 2 layersService (cause for RRC connectionsetup) not consideredLoad of target layer not consideredCannot be used simultaneously withR99 directed RRC connection setupLayering in Cell_FACH supported(same rules as for RRC con. setup)Basic featureTargetR5 or newer UEs directed from non-HSDPA supporting carrier to HSDPA supporting oneR99 or R4 UEs directed from HSDPA supporting carrier to non-HSDPA supporting oneFeature works within same sector defined by SectorIDRequired parameter settingsDirectedRRCForHSDPALayerEnabled = enabledDirectedRRCForHSDPALayerEnhanc = disabledDirectedRRCForHSDPALayerEnabledWCEL; 0 = disabled; 1 = enabledDirectedRRCForHSDPALayerEnhancRNC, RU30: RNMOBI; 0 = disabled; 1 = enabledSectorIDWCEL; 0..12; 1; 0 = cell not belonging to any sector# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Enhanced featureNon-HSDPA UEsDirected away from HSDPA capable cell ifLoad of the target cell not too big (i.e. R99 load balancing back to source cell not triggered)HSDPA UEsDirected away from non-HSDPA capable cell ifEstablishment cause indicated by UE allowed in HSDPA layerNot too much HS-DSCH users in target cellDirected to other HSDPA capable cell ifLoad balancing requiredEstablishment cause indicated by UE allowed in HSDPA layerHSUPA UEsSame rules as for HSDPA UEs, but additionallyDirected to HSUPA capable cell if possibleNot directed away from HSUPA capable cell

Directed RRC Connection Setup (2/8)# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#

Directed RRC Connection Setup (3/8): ExampleDecision algorithm for UEs camping on non HSDPA layer

UE HSPA capability = cell HSPA capabilityAYes current layer (f1)B & C No f2 & f3

Establishment cause allowed in HSDPA target layerB & C No current layer (f1)B & C Yes f2 & f3

UE HSPA capability = target cell HSPA capabilityB f2 or f3 (where more HSDPA throughput)C f3

f1, R99f2, HSDPAf3, HSDPA&HSUPAAB

UE reporting Rel5 or Rel-6, HSDPA capabilityAny other UE

UE reporting Rel-6HSDPA & HSUPA capabilityC

# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Decision algorithm for UEs camping on HSDPA layer

UE HSPA capability = cell HSPA capabilityANo f1B & CYes f2 & f3

Establishment cause allowed in HSDPA target layerB & CNo current layer (f2)B & C Yes f2 & f3

UE HSPA capability = target cell HSPA capabilityB f2 or f3 (where more HSDPA throughput)C f3

f1, R99f2, HSDPAf3, HSDPA&HSUPAAB

C

Directed RRC Connection Setup (4/8): Example

UE reporting Rel5 or Rel-6, HSDPA capabilityAny other UE

UE reporting Rel-6HSDPA & HSUPA capability

# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Load BalancingLoad of serving and target cell (both in same sector) is checked only if DirectedRRCForHSDPALayerEnhanc parameter is ONApplied if there are 2 or more layers supporting HSDPATarget layer selection depends on number of active HSDPA UEs, which is checked against HSDPALayerLoadShareThresholdif number of UEs > HSDPALayerLoadShareThreshold in one cell of sector HSDPA UEs directed to HSDPA layer offering highest HSDPA power per userOtherwise HSDPA UEs directed to HSDPA layer with highest value of CellWeightForHSDPALayering Directed RRC Connection Setup (5/8): Load BalancingHSDPALayerLoadShareThresholdHSDPA layers load sharing thresholdRNC, RU30: RNMOBI; 0..48; 1; 3CellWeightForHSDPALayeringCell weight for HSDPA layeringWCEL; 0.01..1; 0.01; 1# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Select cell which has Highest cell weight (CellWeightForHSDPALayering) Highest number of HS-DSCH users Cellf1Number of HS-DSCH users < HSDPALayerLoadShareThreshold for all layersMax0Cellf2Cellf3Directed RRC Connection Setup (6/8): Load BalancingHSDPALayerLoadShareThresholdRNC, RU30: RNMOBI; 0..48; 1; 3Number of HS-DSCH users > HSDPALayerLoadShareThreshold for one layerMax0Cellf1Cellf2Cellf3Select cell which offers highest HSDPA power per userCellWeightForHSDPALayeringWCEL; 0.01..1; 0.01; 1# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Directed RRC Connection Setup (7/8): Load BalancingHSDPA power per userIf not disabled with DisablePowerInHSDPALayeringDecision, select cell with highest HSDPA Power per user:

Otherwise select cell with highest HSDPA Cell Weight of:

HSPA powerNon HSPA powerPtxNonHSPAPtxMax0Number of HS-DSCH users > HSDPALayerLoadShareThreshold for one layer

DisablePowerInHSDPALayeringDecisionDisable power in decision making for HSDPA layeringRNC, RU30: RNMOBI; 0..1; 0 = not disabled# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Interworking with R99 directed RRC connection setup

Both parameters DirectedRRCEnabled and DirectedRRCForHSDPAEnabled enabled and DirectedRRCForHSDPALayerEnhanc enabled

Decision of directed RRC connection setup for HSDPA layer done firstDecision = change layer directed RRC connection setup for HSDPA layer is doneDecision = do not change layer decision of directed RRC connection setup is done

If several target candidates exist for R99 directed RRC connection setupUE kept in most suitable layer from capability point of view, if possibleNon HSDPA capable UE non-HSDPA capable cellHSDPA capable UE HSDPA or HSDPA and HSUPA capable cellHSDPA and HSUPA capable UE HSDPA & HSUPA capable cell preferred, then HSDPA capable cellF-DPCH capable UE F-DPCH capable cell preferred otherwise HSDPA&HSUPA capable and HSDPA capable cellsDC HSDPA capable UE HSPA/DC HSDPA capable cell preferred otherwise HSDPA&HSUPA capable and HSDPA capable cells

HSDPA/HSUPA capable UE in R99 directed RRC connection setupnot transferred away from HSDPA/HSUPA layer if requesting interactive or background servicecan be transferred away from HSDPA/HSUPA layer if requesting other kind of serviceDirected RRC Connection Setup (8/8)# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection & Switching CTSChannel Type SelectionSwitching from DCH to HS-DSCHSwitching from HS-DSCH to DCHSwitching from HS-DSCH to FACHAssociated UL DCHAppendix# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HS-DSCH selected in case of Capacity Request if all of the following conditions are met:Traffic class & THP allowed on HS-DSCH: configurable with HSDSCHQoSClassesUE supports HS-DSCHCell supports HSDPA & HS-DSCH is enabledMulti-RAB combination of UE supported with HS-DSCHHSDPA + AMR to be enabled with AMRWithHSDSCH HSDPA + R99 NRT + AMR / R99 streaming enabled with HspaMultiNrtRabSupportNo. of simultaneous HS-DSCH allocations in BTS/cell below max. no. supported by base band configurationHsdschGuardTimerHO & HsdschGuardTimerLowThroughput guard timers not running for UEUE not performing inter-frequency or inter-system measurementsActive set size = 1 if HSDPAMobility = disabled If HSDPA dynamic resource allocation disabled and no existing MAC-d flow in the cellPtxNC PtxtargetHSDPA for HSDPAPriority = 1PtxnonHSDPA PtxtargetHSDPA for HSDPA Priority = 2UE does not have DCHs scheduled with bit rates higher than zeroHS-DSCH physical layer category is supportedHS-DSCH can be admitted if PS streaming and CS voice RB resource are utilizedHSDPA prevention function of the RAN2879: Mass Event Handler feature does not prevent from HS-DSCH allocationHSDPA prevention is started if RNC starts using the prioritized DL power AC for AMR CS DCH speech call

Channel Type Selection CTS (1/2)HSDSCHQoSClassesHS-DSCH QoS classesRNC, RU30: RNHSPA; 11111 = background / interactive with THP 1/2/3 / streaming allowedAMRWithHSDSCHUsage of AMR service with HS-DSCHRNC, RU30: RNFC; 0 = disabled; 1 = enabledHspaMultiNrtRabSupportHSPA multi RAB NRT supportWCEL; 0 = disabled; 1 = enabledTHP: Traffic Handling PriorityHsdschGuardTimerHOHS-DSCH guard time after switching to DCH due to HORNC, RU30: RNHSPA; 0..30 s; 1 s; 5 sHSDSCHGuardTimerLowThroughputHS-DSCH guard timer due to low throughputRNC, RU30: RNHSPA; 0..240 s; 1 s; 30 s# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#CTS: DCH to HS-DSCH (1/3)Trigger1)First HSDPA capable cell added to the Active Set (UE enters HSDPA coverage)Example: SHO of HSDPA capable UE2)RAB combination of UE is changed so that it supports HS-DSCHExample: Release of video call (multi RAB NRT support disabled)3)Initial HS-DSCH reservation not successful for temporary reason (DCH allocated although HS-DSCH supported)Example: No dynamic power allocation, initially too high non controllable load4)HS-DSCH to DCH switch done for IFHO/ISHO measurement, but IFHO/ISHO not performed due to unsatisfied measurement resultsExample: No suitable adjacent IF/IS cell foundHSDPAnon-HSDPASWITCHf1f2CTS: Channel Type Switching# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#CTS: DCH to HS-DSCH (2/3)General Conditions1)UE has RAB combination supporting HSDPANot more than three NRT RABs (if multi RAB NRT support enabled)No R99 streaming or NRT RAB (if multi RAB NRT support disabled)2)UE and at least 1 active cell HSDPA capableIf HSDPAMobility = disabled, active set size must be 13)No inactivity or low utilization detected on DCH (DL/UL)4)No guard timers running to prevent HS-DSCH selectionHsdschGuardTimerHOHSDSCHGuardTimerLowThroughputHSDSCHCTSwitchGuardTimer5)RAB attribute Maximum bit rate does not prevent use of HSDPAHSDSCHCTSwitchGuardTimer HS-DSCH channel type switch guard timerRNC, RU30: RNHSPA; 0..30 s; 1 s; 5 s# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Ec/Io condition for HS-DSCH candidate:

Periodic Ec/Io measurementsFiltering based on EcNoFilterCoefficient as for any mobility functionalityReporting period defined by specific parameter HSDPACPICHCTSRepPer RNC averaging over HSDPACPICHAveWindow reports*RNC needs as least 1 report to initiated channel type switchCTS: DCH to HS-DSCH (3/3)Addition windowCPICH 1 R99CPICH 2 HSDPAEC/I0timeHSDPA cell detectedPeriodic reportsChannel type switchAdditionTimeEc/Io (candidate) >Ec/Io (best cell) HSDPAChaTypeSwitchWindowHSDPAChaTypeSwitchWindowRNC, RU30: RNHSPA; 0..4; 0.5; 0 dBHSDPACPICHCTSRepPer RNC, , RU30: RNHSPA; 0.5; 1; 2; 3; 4; 6 s; 2 sHSDPACPICHAveWindow RNC, RU30: RNMOBI; 1 .. 10; 1; 3* as for any HSDPA mobility functionality# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#CTS: HS-DSCH to DCHTrigger Last HSDPA capable cell droppedEvent 1F (too low Ec/I0 or RSCP for all active cells)Event 6A (too high UE Tx power)Too high DL RL powerUL quality deteriorationDCH allocationattempted in next scheduling period with initial bit rates defined by InitialBitRateUL & InitialBitRateDLIf initial bit rates can not be allocated, DCH 0/0 is offered onlyOnly if ISHO process triggeredIn case of IFHO process switch not required# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#CTS: HS-DSCH to FACH (1/3)HS-DSCH released & channel type switching to Cell_FACH in following cases:Low utilizationLow throughputIn case of Multi-RAB with AMR no channel type switching to Cell_FACH, but to Cell_DCH with AMR + NRT DCH 0/0

Throughput calculated by counting all transmitted bits during configurable sliding measurement window MACdflowthroughputAveWinParameter = 0 throughput measurements switched offOtherwise throughput measurements averaged over sliding windowSliding measurement window moved every HS-DSCH MAC-d scheduling intervalMACdflowThroughputAveWinRNC, RU30: RNHSPA, RU40: WAC; 0..10 s; 0.5 s; 3 s# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Low Utilisation indicated whenMAC-d flow throughput below MACdflowutilRelThrAND RLC does not have any data to send AND there are no more data in the BTS buffer (normal release)TimeMACdflowutilRelThrTimer startedTimer startedThroughputMAC-d PDU in bufferTimer resetSwitching from HS-DSCH to FACH (2/3): Low UtilisationMACdflowutilRelThrLow utilisation threshold of the MAC-d flowRNC, RU30: RNHSPA, RU40: WAC; 0..64000 bps; 256 bps; 256 bpsMACdflowutilTimetoTrigger Low utilization time to trigger of the MAC-d flowRNC, RU30: RNHSPA, RU40: WAC; 0..300 s; 0.2 s; 0 sHS-DSCH released & CTS to Cell_FACH in following cases:Low utilizationLow throughputIn case of Multi-RAB with AMR no CTS to Cell_FACH, but to Cell_DCH with AMR + NRT DCH 0/0MACdflowThroughputAveWinRNC, RU30: RNHSPA, RU40: WAC; 0..10 s; 0.5 s; 3 s# Nokia Siemens Networks RN31679EN30GLA1Throughput calculated by counting all transmitted bits during configurable sliding measurement window MACdflowthroughputAveWinParameter = 0 throughput measurements switched offOtherwise throughput measurements averaged over sliding windowSliding measurement window moved every HS-DSCH MAC-d scheduling interval

RN31679EN30GLA1HSDPA RRM & parameters#TimeMACdflowutilRelThrMACdflowthroughputRelThrHsdschGuardTimerLowThroughputTimer startedTimer startedThroughputMAC-d PDU in bufferTimer startedTimer resetTimer startedLow Throughput indicated whenMAC-d flow throughput below MACdflowthroughputRelThrAND there is still data in the BTS buffer (abnormal release)After MAC-d flow release HS-DSCH not allowed until guard timer HsdschGuardTimerLowThroughput expiresMACdflowthroughputRelThrLow throughput threshold of the MAC-d flow RNC, RU30: RNHSPA; RU40: WAC ; 0..64000 bps; 256 bps; 0 bpsMACdflowthroughputTimetoTriggerLow throughput time to trigger of the MAC-d flowRNC, RU30: RNHSPA, RU40: WAC ; 0..300 s; 0.2 s; 5 sHsdschGuardTimerLowThroughputRNC, RU30: RNHSPA; ; 0..240 s; 1 s; 30 sSwitching from HS-DSCH to FACH (3/3): Low Throughput# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection & SwitchingAssociated UL DCHBit RatesPacket SchedulingAppendix# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#UL Return channel - Bit RatesRB mapped onto HS-DSCH in DL DCH (or E-DCH) allocated as UL return channeldata rates for UL DCH return channel:16, 64, 128 &384 kbit/s independent on R99 settings16, 64, 128 kbit/s if PS streaming is mapped on HS-DSCH16 kbps UL DCH return channel*: HSDPA16KBPSReturnChannelHSDPAminAllowedBitrateUL: min. allowed bit rate -> this parameter is also used to limit UL DCH date rate if RAN2879 Mass Event Handler is used

HSDPA16KBPSReturnChannelRNC, RU30: RNFC; 0 = disabled; 1 = enabled* optional featureRB: Radio BearerHSDPAminAllowedBitrateULMin. bit rate for HSDPA a-DCHRNC , RU30: RNHSDPA, RU40:WAC; 16 K, 64 K, 128 K, 384 K# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Packet Scheduling: HSDPA with UL associated DCHHS-DSCH allocation triggered by UL:high traffic volume indicated RNC tries to allocate return channel with highest possible bit ratelow traffic volume indicated RNC tries to allocate return channel with initial bit rateHS-DSCH allocation DL triggered: RNC tries to allocate HSDPAinitialBitrateULDirect DCH to HS-DSCH switch UL a-DCH bit rate can be same as existing DCH UL bit rateinitial bit rate cannot allocated HS-DSCH not possible UL/DL DCHHSDPAinitialBitrateULInitial bit rate for HSDPA a-DCH RNC, RU30: RNHSPA, RU40: WAC; 16 K, 64 K, 128 K, 384 KCapacity Request(TVMHigh)64kbps384128t0Capacity Request(TVM Low)Initial bitrate64 kbpsDecrease of the retried NRT DCH bitratePBSRT-over-NRTt1t2t3t516t4ExampleInitial bit rate = 64 KMinimum bit rate = 16 KCapacity Request(TVMHigh)Min. bitrate16 kbpsUL a-DCH functionalities:PBS & overload controlDecrease of retried NRT DCH bit rateRT over NRTThroughput based optimisationUpgrade of NRT DCH data rate (normal or flexible)DynUsageHSDPAReturnChannelDynamic usage of UL NRT a-DCH HSDPA return channelRNC, RU30: RNFC, ; 0 or 1; 0 = disabledenabled byTVM: Traffic Volume Measurement# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection & SwitchingAssociated UL DCHAppendix:Static HS-PDSCH Power Allocation Cell Reselection Iub Flow Congestion Control# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Static HS-PDSCH Power Allocation (1/2)Required parameter settingsDynamic HS-PDSCH power allocation disabledFixed HS-PDSCH power defined with PtxMaxHSDPARules for HSDPAPriority = 1 (higher priority for HSDPA)A: 1st HSDPA users enters cellNon-controllable traffic PtxNC PtxTargetHSDPA HSDPA allowedOtherwise R99 onlyHSDPA already activeR99 scheduled up to PtxTargetHSDPAB: Overload for total R99 traffic PtxnonHSDPA > modified overload thresholdStandard R99 overload actionsC: Overload for PtxNC > modified overload thresholdHSDPA releasedMax powerNode B Tx powerAPtxOffsetHSDPAPtxnonHSDPAPtxNCPtxTargetHSDPABPtxtotalPtxTargetCHSDPAPriority 1,2; 1 = HSDPA priority

PtxTargetHSDPATarget for transmitted non-HSDPA power -10..50 dBm; 0.1 dB; 38.5 dBmPtxOffsetHSDPAOffset for transmitted non-HSDPA power 0..6 dB; 0.1 dB; 0.8 dBPtxMaxHSDPAMaximum allowed HSDPA powerWCEL; 0..50 dBm; 0.1 dB; 43 dBm# Nokia Siemens Networks RN31679EN30GLA1Required parameter settingsDynamic HS-PDSCH power allocation disabledFixed HS-PDSCH power defined with PtxMaxHSDPASlow adjustment of HS-PDSCH power PHS-PDSCH due to HS-SCCH power consumptionTotal HSDPA power PHS-PDSCH + PHS-SCCH checked against PtxMaxHSDPAIf threshold exceeded, PHS-PDSCH reduced by hardcoded stepIf total HSDPA power below PtxMaxHSDPA - 2 dB, PHS-PDSCH increased by hardcoded stepRecommendations:if 20 W carrier shared by R99 & HSDPA users no higher total throughput for PtxMaxHSDPA > 6Wif carrier dedicated to HSDPA users only, PtxMaxHSDPA can be set to max. cell powerRequired parameter settingsHSDPAPriority (settable on RNC level only) priority for HSDPA vs. R99 NRT users in case of high loadmodified R99 Load Target with PtxTargetHSDPA [dBm]PtxMaxHSDPA & PtxTargetHSDPA should be selected thatmaximum cell power - PtxTargetHSDPA > PtxMaxHSDPAotherwise the former limits the HSDPA powermodified R99 Overload Threshold for R99 with PtxOffsetHSDPA (set relative to PtxTargetHSDPA in dB)all these parameters are ignored using dynamic HS-PDSCH power allocation

RN31679EN30GLA1HSDPA RRM & parameters#Static HS-PDSCH Power Allocation (2/2)Rules for HSDPAPriority = 2 (higher priority for R99)A: 1st HSDPA users enters cellTotal R99 traffic PtxnonHSDPA PtxTargetHSDPA Can have HSDPAOtherwise can have R99 onlyHSDPA already activeR99 scheduled up to PtxTargetHSDPAB: Overload for total R99 traffic PtxnonHSDPA > modified overload thresholdHSDPA releasedC: Standard overload for total R99 traffic PtxnonHSDPA > standard overload thresholdStandard R99 overload actionsMax powerNode-B Tx powerPtxOffsetHSDPAPtxnonHSDPAPtxNCPtxTargetHSDPAPtxtotalPtxTargetPtxOffsetABCHSDPAPriority 1,2; 1 = HSDPA priority

PtxTargetHSDPATarget for transmitted non-HSDPA power -10..50 dBm; 0.1 dB; 38.5 dBmPtxOffsetHSDPAOffset for transmitted non-HSDPA power 0..6 dB; 0.1 dB; 0.8 dB# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU10 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection & SwitchingAssociated UL DCHAppendix:Static HS-PDSCH Power Allocation Cell ReselectionIub Flow Congestion Control# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Cell Re-selection (1/3)HSDPAMobility set to disabled IF- mobility handled by HSDPA Cell Reselection, not by serving cell change IF- / IS- mobility handled by same events as for serving cell changeHSDPA cell reselection Transition to CELL_FACH based on event 1a Handling depends on setting of EnableRRCRelease if disabled 1a triggers transition to Cell_FACH immediately if enabled 1a triggers IF- measurements only; transition to cell_FACH triggered by release marginsEnableRRCReleaseEnable RRC connection releaseHOPS; 0 = disabled; 1 = enabledHSDPARRCdiversitySHO of the HSDPA capable UERNC, RU30: RNHSPA; 0 = disabled; 1 = enabledHSDPARRCdiversity can disable SHO for stand alone SRB of HSDPA capable UE (e.g. according addition window) reduces capacity consumption due to stand alone RRC connections (more capacity available for HSDPA) if conditions for HSDPA mobility fulfilled, SHO for stand alone SRB is allowed in any case (e.g. triggered by release margins)HSDPAMobilityServing HS-DSCH cell change & SHO on/off switchRNC, RU30: RNFC; 0 = HSDPA cell reselection; 1 = Serving HS-DSCH cell changeIF: InterfrequencyIS: Intersystem# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#timeEc/IoCPICH 2AdditionTimeMeasurementReportsAdditionWindowCPICH 1HSDPACELL_FACHHSDPAEnableRRCRelease = disabledRisk of ping-pongBut UE connected mostly to optimum cellAdditionWindowFMCS; 0..14.5 dB; 0.5 dB; 4 dBRecommended 0 dBCell Re-selection (2/3)# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#timeEc/IoCPICH 2MeasurementReportsCPICH 1HSDPACELL_FACHReleaseMarginAverageEcNoReleaseMarginPeakEcNoOne margin need to be exceeded onlyHSDPACell Re-selection (3/3)EnableRRCRelease = enabledNo ping-pongBut UE often connected to non optimum cellAdditionTimeAdditionWindowReleaseMarginAverageEcNoRelease margin for average Ec/IoHOPS; -6..6; 0.1; 2.5 dBReleaseMarginPeakEcNoRelease margin for peak Ec/IoHOPS; -6..6; 0.5 dB; 3.5 dB# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection & SwitchingAssociated UL DCHAppendix:Static HS-PDSCH Power Allocation Cell ReselectionIub Flow Congestion Control# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Iub Flow Control (1/4)ObjectiveNode B has to offer sufficient data for HSDPAto avoid overflow of its bufferto be performed per HSDPA connection on IubNode B informs RNC aboutMax. number of MAC-d PDUs (credits) allowed to be sent per time interval by RNC for unlimited 10ms periods. That means that the RNC can send data according to latest capacity allocation as long as new capacity allocation is receivedNumber of time intervalsDuration of 1 time intervalNumber of assigned credits are recalculated by BTS each 10ms and signaled to the RNC (if differs enough from the previously signaled). Calculated capacity allocation depends onAir interface Tthroughput estimation (the higher, the more credits)Buffer occupancy (the higher, the less credits)BTS prevents packet loss due to buffer overflow by reducing the capacity allocation in case of air interface congestion and ensures that the HSDPA capacity can be reached by having enough data to fill the reserved power allocation# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Iub Flow Control (2/4)Node BRNCCAPACITY REQUEST (CR)CAPACITY ALLOCATION (CA)DATAExample:

Intervals: 1 3 one CA sent with 3 creditsIntervals: 4 one CA sent with 6 creditsIntervals: 5 6 one CA sent with 1 creditsinterval = 10 msInterval number 1 2 3 4 56 Credits 3 3 3 6 1 1calculatedCA= 3 creditsCA= 6 creditsCA= 1 creditsSlide to be replaced with the next slide# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Iub Flow Control (2/4)Node BRNCCAPACITY REQUESTPriorityUser buffer size in RNCCAPACITY ALLOCATIONPriorityUser buffer size in Node BCredits (number of MAC-d PDUs)Repetition period (number of time intervals)Credit validity interval (duration of time interval)DATAPriorityUser buffer size in RNCLength of MAC-d PDUMAC-d PDUsExample:Credits = 4Repetition period = 3Credit validity interval = 10 msSlide replacing the previous one # Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Iub Flow Control (3/4)Number of credits allocated per user decreases and the HSDPA connection throughput decreases as the number of HSDPA connections increases and the connection throughput decreasesNumber of PDU transferred drops frequently when 1 HSDPA connection is active only

Raw dataAveraged data# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Iub Flow Control (4/4)

Raw dataAveraged dataNode B buffer occupancy can be evaluated from difference as follows number of acknowledged MAC-d PDU - number of MAC-d PDU transferred from the RNCComparison with previous slide shows, that number of credits decreases also because of high buffer occupancy# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#HSDPA RRMHSDPA PrinciplesHSDPA Protocols & Physical ChannelsRU30 Capabilities & Baseband ConfigurationHSDPA Link AdaptationHSDPA H-ARQHSDPA Packet SchedulingBasics of HSDPA Power AllocationBasics of HSDPA Code AllocationBasics of HSDPA MobilityHSDPA Channel Type Selection & SwitchingAssociated UL DCHAppendix:Static HS-PDSCH Power Allocation Cell ReselectionIub Flow Congestion Control# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Iub Congestion Control CC (1/2)Objective:RNC can not see Iub congestion towards Node B after hub nodeIub congestion must be detected by Node BRNC informs Node B by DL Frame Protocol about:Build up delaySequence numberNode B thus can detect:Too strong delay of framesLoss of framesDelay thresholds:3 thresholds (BTS commissioning parameter)Minimum threshold Thmin: 0..5000 ms; 50 msIntermediate threshold Thmid: 0..5000 ms; 250 150 msMaximum threshold Thmax: 0..5000 ms; 1000 250 msActions:Delay < Thmin 50 ms no actionThmin 50 ms delay Thmid 250 ms Node B reduces credits for RNC with low probability (depending linearly on delay with low slope)Thmid 250 ms delay Thmax 1000 ms Node B reduces credits for RNC with high probability (depending linearly on delay with high slope)Delay > Thmax 1000 ms or frame loss Node B reduces credits for RNC in any caseIf QoS aware scheduling applied:for high priority service Node B reduces credits for RNC with lower probability than for low priority serviceHSDPACCEnabled WBTS; 0 (disabled); 1 (enabled)# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Iub Congestion Control (2/2)Delay t11000 msProbability for less credits P(t)Pmax250 ms50 msLess credits in any caseLess credits with rapidlyincreasing P(t)Less credits with slowlyincreasing P(t)Slide to be replaced with the next slide# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Iub Congestion Control (2/2)Delay [ms]1ThmaxProbability for less credits P(delay)PmaxThmidThminLess credits in any caseLess credits with rapidlyincreasing P(t)Less credits with slowlyincreasing P(t)Slide to replace the previous slide# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#Version controlVersionDateStatusOwnerRU10_v1.014.08.2009RU10 level, RANPAR Combined version (A. Annen)Benedikt AschermannRU20_v1.231.12.2009RU20 level, RANPAR Combined (Andreas Annen)Benedikt AschermannRU30_v1.208.04.2011RU30 level, RANPAR Combined (Andreas Annen9Benedikt AschermannRU40_v1.014.02.13RU40 level update (Ewa Chmielewska, Michal Nowicki)Benedikt Aschermann# Nokia Siemens Networks RN31679EN30GLA1RN31679EN30GLA1HSDPA RRM & parameters#