HSUPA RRM

NumberEDCHReservedSHOBranchAdditions Number of E-DCHs reserved for SHO branch additions WCEL; 0..5; 1; 2NSN: Enabling HSUPA only in combination with HSDPA by HSUPAEnabled & EDCHQOSClasses

HSUPAEnabled WCEL; 0 = disabled; 1 = enabledMaximum Number of Connections Maximum number of E-DCH allocations defined byMaxNumberEDCHCell for individual cellMaxNumberEDCHLCG for Local Cell Group (LCG) Number of E-DCH allocations reserved for SHO:NumberEDCHReservedSHOBranchAdditions both for individual cells & cell groups. Note: This parameter has no effect if HSPA128UsersPerCell=1MaxNumberEDCHCellmax. number of E-DCHs (serving+non-serving) in the cell WCEL; 1..72; 1; 20 (RU20)0, 1 1024; 1; 0 = not limited (RU30, RU40)EDCHQOSClasses enabling certain E-DCH QoS classes (RNC); 5 bit parameter:Bit 1 = Background BGBits 2/3/4 = Interactive with THP = 3/2/1Bit 5 = streaming31 = all traffic classes enabledMaxNumberEDCHLCG max. number of E-DCHs (serving+non-serving) in the LCG WBTS; 1..72; 1; 60 (RU20)0, 1 1024; 1; 0 = not limited (RU30, RU40)RU20: According default settings:20 - 2 = 18 new E-DCH allowed in individual cell60 - 2 = 58 new E-DCH allowed in cell group LCGLCG: Local Cell GroupHSPA72UsersPerCell (RU20, RU30)max. number of serving + non-serving E-DCHs per cell is 72 WCEL; 0 = not enabled; 1 = enabledNote: In RU340, HSUPA connections are only counted by the serving cell (prior to RU340 they are counted in both the serving and non-serving cells)HSPA128UsersPerCell (RU40)max. number of serving E-DCHs per cell is 128 WCEL; 0 = not enabled; 1 = enabledmodifiedAccording to default settings:RU30: 72 - 2 = 70 new E-DCH allowed in cellRU40: 128 = 128 new E-DCH allowed in cellIn RU30/40, max number of users (serving+non-serving) per LCG is limited by HSUPA scheduler capacity: up to 480 HSUPA (2x Flexi System Module) or 240 (1x Flexi System Module) users per LCG # Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#I suggest removing this text, becasue:- On the right hand side of the slide I added which parameter limits the serving connections, and which parameter limits the serving+non-serving connections. So this onformation is complete. HSUPA RRM & parameters:Module ObjectivesAt the end of the module you will be able to:

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

# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA RRM: ContentsHSUPA PrinciplesTTI: 2 ms / 10 msHSUPA Physical ChannelsE-TFC SelectionBTS SchedulingHSUPA Power ControlHSUPA Load ControlHSUPA MobilityHSUPA Channel Type Selection & SwitchingAppendix# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Comparing HSUPA & HSDPA (1/2)3GPP Rel. 6: TS 25.309 HSUPA technical requirements Node B controlled scheduling Hybrid ARQ Shorter TTI: 2 ms or 10 ms Downward compatibility to R99, R4 & R5 HSUPA requires HSDPA Minimise HSUPA (UE and UTRAN) complexity Full mobility support and urban, suburban & rural deploymentHSDPAUEsIubUuHSUPAsame as HSDPA

RNCNode B# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Comparing HSUPA & HSDPA (2/2)Why notadaptingHSDPA solutionsto UL?HSUPA problems / differences to HSDPA: Power Control PC: Fast Power Controlon DL centralized PCon UL individual PC pure time multiplexing difficult on UL fast PC still necessary (same as Rel. 99) (UL interference UL scrambling codes) Higher order modulation difficult for UE (Rel.7) Soft Handover required due to coverage reasons HSUPA (similar to HSDPA) is based on Fast H-ARQ terminated at Node B Fast UL Packet Scheduling controlled by Node B Fast Link Adaptation: - Adaptive coding (1/4 - 4/4 code rate) - Adaptive modulation (3GPP Rel. 7)

# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#E-DCH: Enhanced Dedicated Channel (TS 25.309)Dedicated channel DCHA channel dedicated to 1 UE used in UL or DL.UEIubUuEnhanced dedicated channel E-DCHE-DCH transport channel characteristics UL (only) transport channel Dedicated to 1 UE Subject to Node-B controlled scheduling & HARQ Supports 2 ms TTI and 10 ms TTI

RNCNode B# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#E-DPDCH & E-DPCCH

Rel. `99E-DPDCH: carries E-DCH transport channel user data only (+ 24 CRC bits/TTI) SF = 256 2 ! Multi-Code Operation: there may be 0, 1, 2 or 4 E-DPDCH on each radio link up to 2x SF2 + 2x SF4 up to 11.52 Mbps with 16QAME-DPCCH: transmits HSUPA L1 control information associated with the E-DCH SF = 256 fixed content: E-TFCI, RSN & Happy BitConfigura-tion #DPDCHDPCCHHS-DPCCHE-DPDCHE- DPCCH 1611--2111213-1141Rel. 6 UL: DCH & E-DCH ConfigurationsE-TFCI: Enhanced Transport Format Combination IndicationRSN: Retransmission Sequence Numbermodified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#according to 3gpp 25.213:"The possible combinations of the maximum number of respective dedicated physical channels which may be configured simultaneously for a UE in addition to the DPCCH are specified in table 0"

Thus I added the DPCCH colmn to table 0HSUPA 5.8MbpsTo support an UL peak rate of 5.8 Mbps* the UE needs to send on 4 E-DCH channels in parallel (2xSF2 + 2xSF4)UE category 6 + 7, 8 enable transmission of 4 codes in parallel & support 5.76 Mbps at maximum with QPSK modulationIn case of 4 code E-DCH transmission 3GPP defines that no DPDCH may be allocated simultaneouslyThe SRB needs to be mapped on E-DCH in this case. This requires RU20 RAN 1470 HSUPA 2ms TTI, which introduces the mapping of UL SRBs on E-DCHSF2SF4SF8Cch,2,0Cch,2,1Cch,4,0Cch,4,1Cch,4,2Cch,4,3E-DPDCH(on I- and Q-branches 2SF2 + 2SF4 max)RU20:5.8 Mbps &2 ms TTI* 5.76 MbpsMaxTotalUplinkSymbolRateWCEL; 0 (960 kbps, SF4), 1 (1.92 Mbps; 2xSF4),2 (3.84 Mbps; 2xSF2), 3 (5.76 Mbps; 2xSF2 + 2xSF4);HSUPA 5.8 Mbps active parameter value 3 allowed; else max. 2 RAN 981: HSUPA 5.8 Mbps peak rate Optional Feature (ASW) RNC License Key required (ON OFF)modified# Nokia Siemens Networks RN3167AEN30GLA1Feature ID: RAN981The peak bit rate on E-DCH for single user is increased up to 5.8 Mbps. Benefits for the operator:This feature enables operator to offer higher HSUPA bit rates to premium data subscribers and increase data service revenue.

Functional description:HSUPA UE categories 4, 6 and 7 support higher peak bit rate than 2 Mbps. With this feature category 4, 6 and 7 UEs may transmit data with their maximum bit rate, which is achieved with an E-DCH configuration of 2ms transmission time interval (TTI). Four parallel codes are required for category 6 and 7. When four codes are transmitted in parallel, two codes are transmitted with spreading factor two (2xSF2) and two with spreading factor four (2xSF4). Also intermediate bit rates are supported with 2 ms TTI.

The maximum theoretical throughput of category 6 and 7 terminal is 5.76 Mbps. Practical throughput achievable with this feature is limited by radio reception and allowed noise rise: Maximum theoretical throughput would require the use of coding rate close to 1. Coding rate 1 requires effectively error free reception without error correction coding. Targeting to error free reception reduces the system efficiency and capacity. In all practical conditions the throughput will be degraded if using coding rates close to 1. Quality of radio reception depends on aspects such as received signal strength, radio channel and interference, transmitter and receiver imperfections.

RN3167AEN30GLA1HSUPA RRM & parameters#Inner Loop Power Control for E-DPDCH & E-DPCCH (2/3)I- or Q- branchGain Factor Spreading withchannelisation codeS I+jQ ced,1 bed,1 E-DPDCH1 iqed,1 ced,k bed,k E-DPDCHk iqed,k ced,K bed,K E-DPDCHK iqed,K cec bec E-DPCCH iqec . . . . . . . . UE determinesgain factor ed,kbased on maximum Aed given by service grant and selected E-TFCE-DPDCHked = c * Aed

IndexAed = ed / c

modified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Inner Loop Power Control for E-DPDCH & E-DPCCH (3/3)Signalled values for D E-DPDCHQuantized amplitude ratios Aed = bed/bc31377/1530336/1529299/1528267/1527237/1526212/1525189/1524168/1523150/1522134/1521119/1520106/151995/151884/151775/151667/151560/151453/151347/151242/151138/151034/15930/15827/15724/15621/15519/15417/15315/15213/15111/1508/15IndexAed = ed / cnewPE-DPDCH (E-TFC2)PDPCCH DPCCHE-DPCCHE-DPDCHDPCCHE-DPCCHE-DPDCHPE-DPDCH (E-TFC2)PE-DPCCHPDPCCH DPCCHE-DPDCHDPCCHE-DPCCHE-DPDCHPE-DPDCH (E-TFC1)E-DPCCHNon boosted mode (non-16QAM)PE-DPCCH/PDPCCH/ = constLow E-TFCIHigh E-TFCILow E-TFCIHigh E-TFCIPE-DPDCH (E-TFC1)PE-DPCCHPDPCCH PE-DPCCHPower boosted mode (applicable to HSUPA 16 QAM)PE-DPCCH/PE-E-DPDCH/ = constPE-DPDCH depended on E-DPDCH instead of DPCCHAed in case of 16 QAME-DPCCH more robust to own signal interferences from high E-DPDH powerHigh own signal interference from E-DPDCH cause received E-DPCCH too poor# Nokia Siemens Networks RN3167AEN30GLA13GPP 25.213 Table 1B.2ARN3167AEN30GLA1HSUPA RRM & parameters#Soft & Softer HO (1/2)Types of mobility Intra-frequency mobility allowsIntra-BTS intra-RNC Softer handover (between cells belonging to the same LCG)Intra-BTS intra-RNC Soft handover (intra-frequency HO between cells belonging to different LCGs )Inter-BTS Intra-RNC Soft handoverInter-RNC Soft handover (If HSPA over Iur feature is enabled)

SHO Trigger Same events (1a, 1b, 1c) as for DCHBut specific FMCS parameter set available forUser both with HSDPA + HSUPAUser both with HSDPA + HSUPA and AMRFMCS is used for intra-frequency measurement control HSDPA serving cell change not affected by HSUPA SHOHSPAFmcsIdentifier HSPA FMCS identifier for Single or Multi PS RABWCEL; 1..100; 1; -RTWithHSPAFmcsIdentifierHSPA FMCS identifier for AMR multi-serviceWCEL; 1..100; 1; -modified# Nokia Siemens Networks RN3167AEN30GLA1HSUPA RRM 1.2.2 Hsupa handoversRN3167AEN30GLA1HSUPA RRM & parameters#Soft & Softer HO (2/2)E-DCH & DCH Active Set (AS) E-DCH AS: subset of DCH AS E-DCH active set is built when the E-DCH channel type is selected. All cells in the DCH active set are added to the E-DCH active set if possible Cells can be left out from E-DCH AS but included within DCH AS due toHSUPA not enabled for DCH active cellA cell is under DRNC and HSPA over Iur is disabledMax. number of E-DCH users reached for that cell or cell group to which it belongsNo free E-DCH resources within cell group to which it belongsSome other reasons (for example, signaling problems) Softer HO E-DCH & DCH AS have to be identical Soft HO E-DCH & DCH AS can be different Cell shall be added to E-DCH AS later if possible (by using internal retry timer) HSDPA cell is also HSUPA serving cell

E-DCHE-DCHDCHIf SHO failure for E-DCH Channel type switch to DCH, if non active cell becomes too strong in comparison to best active cellIn case of Softer HO for DCH no AS update either (RRC connection release due to DCH SHO failure possible as usual)modified# Nokia Siemens Networks RN3167AEN30GLA1WCDMA RAM RRM p. 172RN3167AEN30GLA1HSUPA RRM & parameters#Inter-Frequency & Inter-System HHOInter-Frequency HHO not yet supported for HSUPA same FMCI parameter set used as for HSDPA same HOPI parameter set used as for R99

Inter-System HHO not yet supported by HSUPAsame FMCG parameter set used as for HSDPA same HOPG parameter set used as for R99modified# Nokia Siemens Networks RN3167AEN30GLA1WCDMA RAN RRM HSUPA 14.4 Hard handovers p. 185

Inter-Frequency HHO not supported for HSUPA until RU30 CTS E-DCH DCH required same FMCI parameter set used as for HSDPA same HOPI parameter set used as for R99

RN3167AEN30GLA1HSUPA RRM & parameters#CELL_DCH CELL_FACH CELL_PCH URA_PCH RRC Connected Mode Camping on a UMTS cellIdle Mode CELL_DCH CELL_FACH CELL_PCH URA_PCH RRC Connected Mode Camping on a UMTS cellIdle Mode DCH LayerHSPA LayerHSPA Layering in Common ChannelsDirected RRC Connection EstablishmentHSUPA Layering (1/3)HSUPA layering features Directed RRC Connection Establishment: Re-direction from RRC Idle mode HSPA Layering in Common Channels: Layering from CELL_FACH # Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA Layering (2/3): HSUPA directed RRC connection setupParameter dependencies: same as discussed under HSDPAFeature details: same as discussed under HSDPADirectedRRCEnabledDirected RRC connection setup enabledWCEL; 0 or 1; 0 = disabled; 1 = enabledDirectedRRCForHSDPALayerEnabledDirected RRC connection setup for HSDPA layerWCEL; 0 or 1; 0 = disabled; 1 = enabledDirectedRRCForHSDPALayerEnhancDRRC connection setup for HSDPA layer enhancementsRNC; 0 or 1; 0 = disabled; 1 = enabledDRRCForHSDPALayerServicesServices for DRRC connection setup for HSDPA layer*RNC; 0..32767; 1; 204Further Requirements: HSUPA capability of UE taken into account only, if enhanced layering enabled with DirectedRRCForHSDPALayerEnhanc To be redirected to HSUPA layer, UE must indicate with RRC connection request: - R6 or newer & HSDPA + HSUPA capable at least 1 cell must be available fulfilling:Number of HS-DSCH allocations has not reached max. allowed valueHSUPA is enabled only single HSUPA capable cell available selected without checking max. allowed number of HSUPA users several HSUPA capable cells available Cells having not reached max. allowed number of HSUPA users are prioritisedFollowing parameters must be enabled:# Nokia Siemens Networks RN3167AEN30GLA1* 16 bit parameter to enable / disable enhanced layering for each traffic class & different types of signalling procedures individually; by default enabled for interactive / background service & inter-RAT cell re-selection / cell change order

RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA Layering (3/3): HSPA Layering in Common ChannelsFrom Cell_FACH Must be enabled with HSDPALayeringCommonChEnabled Redirection Cell_FACH to Cell_DCH to HSPA layer triggered ifUE is HSPA capableHSDPA not enabled for current cellHSDPA enabled for at least one cell in same sectorUE is requesting service for which state transition is enabled with ServicesToHSDPALayer HSUPA capability is taken into account if UE is HSUPA capable HSUPA enabled target cell available Layering from Cell_FACH not affected by settings for layering from RRC_idleHSDPALayeringCommonChEnabledHSDPA layering for UEs in common channels enabledWCEL; 0 or 1; 0 = disabled; 1 = enabledServicesToHSDPALayerServices to HSDPA layer in state transitionRNC; any service, NRT RAB# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#UERNCSGSNNode BRRC EstablishmentGPRS AttachRNC completes channel type selection procedurePDP Context ActivationMeasurement Report 4a0/0 kbps DCH allocatedUplink capacity requestE-DCH Establishment (1/3)Signalling (establishment from RRC_Idle) Same high level procedures as for NRT DCH After PDP context activation RNC starts by allocating DCH 0/0 kbps connection Selection between DCH and E-DCH completed when RNC receives UL capacity request HSUPA can be allocated from CELL_FACH or CELL_PCH as well

modified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#E-DCH Establishment (/)Direct Resource Allocation (DRA) for HSPA HSDPA or HSPA transport channels are directly allocated in the RAB setup phase from Cell_DCH or from Cell_FACH state DRA for the new entering PS RABs of interactive and background traffic classes Possible to define whether the DRA is to be used in CELL_DCH or CEL_FACH or both

newRABDRAEnabledUsage of the direct resource allocation for PS NRT HSPA RNFC; Disabled (0), Enabled in Cell_FACH (1), Enabled in Cell_DCH (2), Enabled in Cell_FACH and Cell_DCH (3)Further Requirements:In case of DRA to HSPA channels (HS-DSCH & E-DCH), F-DPCH need to be allocatedUERNCSGSNNode BRRC EstablishmentGPRS AttachPDP Context ActivationRadio Bearer setup to HSPA (direct)Uplink capacity request if neededUser Plane established on HSPAMeasurement Control# Nokia Siemens Networks RN3167AEN30GLA1Basic call FD 2.3.12.3RN3167AEN30GLA1HSUPA RRM & parameters#Final E-DCH active set is acceptableUplink NRT RB mapped to DCH > 0 kbpsUE capability supports E-DCHRAB combination allows use of E-DCHTraffic class and THP allowed on E-DCHHSDPA mobility enabled and HS-DSCH availableand no IFHO/ISHO measurementsHS-DSCH possible to select in the downlinkPreliminary E-DCH active set is acceptableHS-DSCH possible to select in the downlinkNumber of E-DCH allocations is below the maximumYesNoNoNoNoNoNoNoNoNoUE specific PSHCCell specific PS (can be more than 1)UE specific PSChannel type selection startedDCH selectedDCH selectedE-DCH selectedNoYesYesYesYesYesYesYesYesYesHSPA serving cell selected + Preliminary E-DCH active set selectedMinimum E-DCH active set selectedE-DCH Establishment (2/3)11) Channel type switching running2) RAB combinations allowed for HSUPA up to 3 NRT RAB (any combination E-DCH RABs / DCH RABs) with or without AMR3) Preliminary active set = all active cells with HSUPA enabled4) Minimum AS = all HSUPA enabled active cells with sufficient quality234IFHO/ISHO measurementsprevent HSUPADirect Resource Allocation (DRA) for HSPA not usedmodified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Minimum E-DCH Active Set: Exclude all active cells for which HSUPA is disabled Exclude all active cells which satisfy following equation EC/I0 of E-DCH cell < EC/I0 of serving E-DCH cell + EDCHAddEcNoOffsetE-DCH Establishment (3/3)

DCH active set step 1HSUPA enabledHSUPA disabledHSUPA enabled

Preliminary E-DCH active set step 2HSUPA enabledHSUPA enabled

Minimum E-DCH active set step 3CPICH Ec/Io = -5 dBCPICH Ec/Io = -7 dBEDCHAddEcNoOffsetallow E-DCH usage EcNo offsetFMCS; -10 .. 6; 0.5; 0 dBHspaMultiNrtRabSupportHSPA multi NRT RAB Support; up to 3 NRT RABWCEL; 0 or 1; 0 = disabled; 1 = enabled AMRwithEDCHUsage of AMR + E-DCH*WCEL; 0 or 1; 0 = disabled; 1 = enabled * AMR codec selection not affected by HSUPAMulti-RAB# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Channel Type Switching CTS (1/4)Overview: Trigger causing Channel Type Switching DCH E-DCH or E-DCH DCH HS-DSCH related trigger:1) DCH HS-DSCH channel type switching2)HS-DSCH serving cell change Quality related trigger:3)EC/I0 of serving HSDPA cell becomes acceptable for E-DCH4)EC/I0 of serving HSDPA cell becomes unacceptable for E-DCHEC/I0 is reported periodically like for HSDPA serving cell change Other5)Guard timer started after transition E-DCH DCH expires6)Re-try timer expires; started after unsuccessful attempts to get E-DCH (due to too high number of E-DCH users)Node B initiated transition E-DCH DCHPS streaming establishmentE-DCH active set updateCS voice RAB establishment (determines whether it is possible to switch to the full HSPA configuration)DCHE-DCHmodified# Nokia Siemens Networks RN3167AEN30GLA1WCDMA RAN HSUPA 1.4.3.2 p. 176RN3167AEN30GLA1HSUPA RRM & parameters#Channel Type Switching CTS (2/4)1) Trigger DCH HS-DSCH switch Attempt for DCH HS-DSCHIf succeeds then E-DCH may also be allocated (DCH/DCH -> E-DCH/HS-DSCH)If fails then E-DCH cannot be allocated (DCH/DCH -> DCH/DCH) HS-DSCH DCHE-DCH->DCH switch also triggered (E-DCH/HS-DSCH -> DCH/DCH)2) Trigger HS-DSCH Serving Cell change DCH allocated in the UL RNC checks if E-DCH can be selected E-DCH allocated in the UL RNC checks if E-DCH can be maintained For both casesServing cell must support E-DCHNon-serving active cells which cannot be added to E-DCH AS must not have too high CPICH Ec/Io (see minimum AS & quality related trigger)E-DCH areaNon-E-DCH areaNon-E-DCH areamodified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Channel Type Switching CTS (3/4)3) Trigger EC/I0 of Serving HSDPA cell becomes acceptable for E-DCH Triggers DCH E-DCH switch Serving cell changes to acceptable if AS cell which cannot be added to E-DCH AS becomes weak or is removedWeak: defined relative to Serving HS-DSCH cellThreshold defined by EDCHAddEcNoOffsetno time to triggerCPICH Ec/IoNon E-DCH capable cellServing HS-DSCH cellE-DCH capable cellTimeDCH to E-DCH switchEDCHAddEcNoOffsetFMCS; -10..6; 0.5; 0 dB4) Trigger EC/I0 of Serving HSDPA cell becomes un-acceptable for E-DCH Triggers E-DCH DCH switch Serving cell changes to unacceptable if AS cell which is not E-DCH active becomes strongdefined relative to Serving HS-DSCH cellThreshold defined by EDCHRemEcNoOffsetno time to triggerCPICH Ec/IoNon E-DCH capable cellServing HS-DSCH cellE-DCH capable cellTimeE-DCH to DCH switchEDCHRemEcNoOffsetFMCS; -10 .. 6; 0.5 dB; 2 dB# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Channel Type Switching CTS (4/4)5) Trigger CTS guard timer expires after CTS E-DCH DCH guard timer EDCHCTSwitchGuardTimer is started after expiration of the timer switch back to E-DCH allowedEDCHCTSwitchGuardTimerE-DCH CTS guard timerRNC; 0..20 s; 0.5 s; 2 s6) Trigger CTS re-try timer expires If E-DCH cannot be allocated, because max. # of HSUPA users users is reached, retry timer is started Timer can be applied for initial channel type selection or CTS after timer expiration next Capacity Request for E-DCH allowed Re-try Timer = min (10 s, number of failures * 2 s)EDCHCTSwitchGuardTimerTimeE-DCH DCH switch (guard timer started)Attempt for DCH E-DCH switch allowedRe-try TimerTimeDCH E-DCH switch failed (re-try timer started)Consecutive DCH E-DCH switch re-attempts7) Trigger Node B initiated switch E-DCH DCH Node B may need to release E-DCH resources to allocate HW resources more effectively Node B sends RL failure message with cause UL radio resources not available to RNC RNC shall change channel type from E-DCH to DCH CTS retry timer applied to allow connection to return to E-DCH# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Channel Type Switching CTS (/)8) PS streaming RB establishment Upon the establishment of the PS streaming RB, the channel type is selected if HSPA streaming is not activated, or the use of HSUPA is not allowed, the NRT RB channel type is switched from E-DCH to DCH if there are no resources available, the channel type of the NRT RB is not switched to DCH, but E-DCH usage is continued. The RT-over-NRT procedure is attempted for the streaming real-time bearer, and afterwards a DCH with 0/0 kbps is allocated and a new capacity request is awaited. 9) E-DCH active set updateWhen DCH is allocated for streaming and NRT services and a soft handover branch is deleted from the active set, the RNC checks whether all cells support E-DCH. The RNC triggers channel type switching from DCH to E-DCH if all of the following conditions are true: All cells support E-DCH. The HSPAQoSEnabled parameter is set to ON for the serving HS-DSCH cell.HSPAQoSEnabled HSPA QoS enabledWCEL; QoS prioritization is not in use for HS transport (0), QoS prioritization is used for HS NRT channels (1), HSPA streaming is in use (2), HSPA CS voice is in use (3), HSPA streaming and CS voice are in use (4), QoS prioritization is used for HS NRT channels (1), HSPA streaming is in use (2), HSPA CS voice is in use (3), HSPA streaming and CS voice are in use (4)new# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Channel Type Switching CTS (/)new10) HSPA to DCH switch triggered in case of CS voice RABIf the UE has full HSPA configuration, a switch to another configuration is triggered in the following cases: CS voice RAB establishment full HSPA (including CS voice over HSPA) configuration cannot be kept anymore, for example, due to the following reasons: not successful HSUPA TTI switch from 2 ms to 10 ms quality reasons start of compressed mode a cell that does not support CS voice on HSPA is added to the active set a cell that is under the DRNC is added to the active set RAB combination not supported with full HSPA configuration (but supported with DCH)

# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#E-DCH ReleaseThroughput measurement taken every TTI individual samples averaged over sliding window of size EDCHMACdFlowThroughputAveWin first average available when sliding window full sliding window moved every TTIRelease Trigger: low throughput indication After E-DCH allocation no MAC-d flow detected for EDCHMACdFlowThroughputAveWin + 2 s Low throughput EDCHMACdFlowThroughputRelThr during EDCHMACdFlowThroughputTimetoTrigger (or EDCHMACdFlowTputStrTtT for streaming E-DCH) if low throughput indication has been sent & throughput returns above threshold then normal throughput indication is triggered immediately HS-DSCH released E-DCH release independent on actual throughputEDCHMACdFlowThroughputAveWinwindow size of E-DCH MAC-d flow throughput measurementRNC; 0.5..10; 0.5; 3 sTTIEDCHMACdFlowThroughputAveWin Throughput Result EDCHMACdFlowThroughputTimetoTrigger Low throughput indication sent to layer 3 Normal throughput indication sent to layer 3 EDCHMACdFlowThroughputRelThrEDCHMACdFlowThroughputTimetoTriggerlow throughput time to trigger of the E-DCH MAC-d flowRNC; 0..300; 0.2 s; 5 sEDCHMACdFlowThroughputRelThrlow throughput threshold of the E-DCH MAC-d flowRNC; 0..64000; 256; 256 bpsEDCHMACdFlowTputStrTtT low throughput time to trigger for streaming E-DCH MAC-d flow RNHSPA; 0..300; 0.2 s; 5 smodified If low throughput in the UL is indicated for one RAB of a Multi PS RAB because no data is to be transferred, the radio bearer of the inactive RAB is released.# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#E-DCH Release for identified SmartphoneThe E-DCH inactivity control for the identified Smartphone follows the principlesdescribed in the MAC layer throughput measurements of the E-DCH NRT and streamingMAC-d, except the following new parameters:

SmartHSPATputAveWin (used instead of EDCHMACdFlowThroughputAveWin) SmartHSPATimeToTrigger (used instead of EDCHMACdFlowThroughputTimetoTrigger)SmartHSPATputAveWin Window size for Smartphone throughput measurement RNHSPA; 0.5..10; 0.5; 1 sSpecial value (0) Smartphone measurement not active (non_Smartphone measurement active for Smartphones)TTISmartHSPATputAveWinThroughput Result SmartHSPATimeToTriggerLow throughput indication sent to layer 3 Normal throughput indication sent to layer 3 EDCHMACdFlowThroughputRelThrSmartHSPATimeToTrigger Time-to-trigger for Smartphone throughput measurement RNC; 0.2..20; 0.2; 0.2 snew# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCUE sends HSUPA data carrying one transport block (MAC-e PDU)HSUPA Congestion Control: PrinciplesMAC-es PDUNDDIMAC-e PDUSIPaddingRNC responsible to detect congestion on Iub & to inform Node BNode B HSUPA scheduler takes actions on the air-interface to relieve congestion on Iub to avoidRLC re-transmissions resulting from Iub congestionGeneration of air-interface load for data which cannot be transferred to RNCData Flow from UE to RNC (1/5)# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

Node B Decodes E-DPDCH Forwards MAC-e PDU with connection frame number CFNMAC-e entity Extracts MAC-es PDUData Flow from UE to RNC (2/5)E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCMAC-es PDUMAC-es PDUNDDISIPaddingCNFCNFMAC-e PDU before extractionMAC-e PDU after extraction# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Non-serving RLS cells (under different Node B) transmit relative grants on E-RGCH Allowed HOLD, DOWN DOWN = overload indication HOLD = dont careServing / Non-Serving Radio Link Set RLS cellsIubIubIu..E-DCHServing E-DCH cell defined by Serving HSDPA cell transmits Absolute Grant on E-AGCHServing E-DCH RLS cells (under same Node B) Transmit same Relative Grant on E-RGCH Allowed UP, HOLD, DOWN

RNC

# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#max. # E-RGCH/E-HICH codes: using HSPA72UsersPerCell (RU30) (HSPA128UsersPerCell disabled) max. 4using HSPA128UsersPerCell (RU40) max. 32elsewise: 1Dynamic E-RGCH/E-HICH code allocation max. 40 signatures available with 1 SF128 code 1 signature for coding of E-RGCH & E-HICH each max. 20 UEs/codeRU30, RU40:RNC checks requirement for a new E-RGCH/E-HICH code every time an HSUPA connection is allocated

for furthersignatures upgradeRsrvdSignaturesOffsetdynamically allocate40 more signatures (1 code)for signaturesupgradesAllocation of additional code: # of free signatures - A RsrvdSignaturesOffsetRelease of existing code (from RN6.0 onwards): # of free signatures - A > 39 + MIN(RsrvdSignaturesOffset + 11; 2x RsrvdSignaturesOffset )40 signatures39 signaturesTraffic increaseTraffic decreasedynamically release40 signatures (1 code)RsrvdSignaturesOffsetWCEL; 5..1118; 1; 10modifiedMy source for this modification is HSUPA RRM in RNC Functional Description, chapter De-allocation of E-RGCH/E-HICH channel(s) (NumHSUsers, HS128U)# Nokia Siemens Networks RN3167AEN30GLA1RRM HSUPA p. 42RRM HSUPA p. 43

RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA RRM: ContentsHSUPA PrinciplesTTI: 2 ms / 10 msHSUPA Physical ChannelsE-TFC SelectionBTS SchedulingHSUPA Power ControlHSUPA Load ControlHSUPA MobilityHSUPA Channel Type Selection & SwitchingAppendix# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Idea: UE selects appropriate Transport Block Size depending on:UE CapabilityTransmission powerService grant TB size derived from TB index with help of TBS size table1 TBS size table for each TTI (2 ms & 10 ms)Supported Tables with 10ms TTITable 0 and Table 1Supported Tables with 2ms TTITable 0 and Table 1TBS size tables optimised for MAC-d PDU sizes of 336 and 656 bits

E-TFC Selection (1/4)TS 25.321 MACAnnex Bmodified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

Excluded: not supported by UE Category 3Excluded: UE without sufficient transmit power (blocked state)0 2 Excluded: Transport Block size too small for 336 bit MAC-d PDUE-TFC Selection (2/4)Step 1: Exclude E-TFCbased upon UE categoryIn blocked stateEDCHMinimumSetETFCIminimum E-TFCI setWCEL; 0..120; 1; 4 = 372 bit minimum E-TFCI set maximum E-TFC which cannot be blocked due to lack of UE power Can be used ifabsolute service grant givenno DCH transmission present0 3 Excluded: minimum E-TFCI Set parameter# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

Max. available E-TFC(UE has to send a lot of data)Excluded E-TFC: based upon Serving GrantUE can select e.g. this E-TFC because if it has less data to sendE-TFC Selection (3/4)Step 2 Identify E-TFC allowed by serving grant (maximum E-DPDCH / DPCCH power ratio) Select E-TFC based upon quantity of data to be send# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#E-TFC Selection (4/4)Puncturing limit UE selects appropriate SF & number of E-DPDCH once it knows E-TFC Maximum amount of puncturing1 - PLnon_max if number of code channels < maximum1 - PLmax if number of code channels = maximum

SF & E-DPDCH selection Step 1 can transport block be accommodated using single E-DPDCH without puncturing?Yes => select highest SF which avoids puncturingNo => go to step 2

Step 2 can transport block be accommodated using single E-DPDCH with PLnon_max ?Yes => select lowest SF (minimise puncturing)No => go to step 3

Step 3 last resortselect one or more E-DPDCH which offer highest number of bits without exceeding PLmaxExample:TTI = 10 ms, TBS = 10 kbit 1 MbpsUser Data Rate = L1 Rate (SF) / ( Puncturing limit x 3 )Turbo Coding 1/3Step 1) L1 Rate (SF) = User Data Rate x 3 = 3 Mbps go to step 2 Step 2) L1 Rate (SF) = User Data Rate x 3 x PLnon_max = 2.04 Mbps go to step 3Step 3) L1 Rate (SF) = User Data Rate x 3 x PLmax = 1.32 Mbps 2 x SF4 required

Puncturing LimitPLnon_max = 0.68 when 10ms TTI (also for HS-RACH)PLnon_max = 0.6 when 2ms TTI (hard coded by NSN)PLmax = 0.44 when not using 2SF2 + 2SF4 (3GPP)PLmax = 0.33 when using 2SF2 + 2SF4 (3GPP)modified# Nokia Siemens Networks RN3167AEN30GLA1WCDMA RAN RRM HSUPA p.92RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA RRM: ContentsHSUPA PrinciplesTTI: 2 ms / 10 msHSUPA Physical ChannelsE-TFC SelectionBTS SchedulingThroughput & Load Based SchedulingAbsolute & Relative Service GrantScheduling ProcessLoad Increase & DecreaseHSUPA Power ControlHSUPA Load ControlHSUPA MobilityHSUPA Channel Type Selection & SwitchingAppendix# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Throughput & Load Based Scheduling (1/4)Throughput & load based scheduling HSUPA scheduler combines throughput & load based algorithms Throughput based scheduling applied for lower load Power based scheduling applied for higher load

PrxMaxTargetBTSrelative to PrxNoise;should be > PrxTarget + PrxOffsetLmin_cellMaximum cell load for HSUPA schedulingThroughput basedLoad derived from throughputPower basedLoad derived from RTWPPrxLoadMarginEDCHrelative to PrxNoisePrxNoiseWCEL: -130..-50; 0.1; -105 dBmmodifiedPrxMaxOrigTargetBTSrelative to PrxNoise;should be > PrxMaxTargetBTS# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Throughput & Load Based Scheduling (2/4)Throughput based scheduling Node B calculates own cell load If own cell load < Lmin_cell then throughput based scheduling can be applied to increase own cell load up to Lmin_cell

PrxMaxTargetBTSLmin_cellMax. cell load for HSUPA schedulingActual own cell loadSchedulable resourcePrxLoadMarginEDCHWCEL; 0..30; 0.1; 2 dB 1.585 LminCell 37%PrxNoiseWCEL: -130..-50; 0.1; -105 dBmPrxLoadMarginEDCHInterference margin for minimum E-DCH load; WCEL; 0..30; 0.1; 2 dB 1.585Corresponding load factor LminCell = 1 - 1/100.2 = 0.37 (37 %)Load factor < margin throughput based load estimationOtherwise RTWP based load estimationPrxMaxOrigTargetBTSmodified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Throughput & Load Based Scheduling (3/4)Load based scheduling if calculated own cell load > Lmincell power based scheduling is applied to increase total cell load up to maximum cell load Node B measures actual RTWP & calculates actual total load

Lmin_cellMax. cell load for HSUPA schedulingSchedulable resourceActual total cell load =own cell load + inter cell interferenceActual own cell loadPrxMaxTargetBTSWCEL; 0..30; 0.1; 6 dB = 2.0 LmaxCell = 75%PrxLoadMarginEDCHWCEL; 0..30; 0.1; 2 dB 1.585 LminCell 37%PrxNoiseWCEL: -130..-50; 0.1; -105 dBmPrxMaxTargetBTSMax. target Rx wide band power for BTSWCEL; 0..30; 0.1; 6 dB = 2.0 Corresponding load factor LmaxCell = 1 - 1 / 100.6 = 0.75 (75 %)RTWP < maximum target more HSUPA service can be offeredOtherwise more HSUPA service can not be offered any more; HSUPA service has to be down-graded if too much RWP from non served UEs in comparison to E-DCH RWPPrxMaxOrigTargetBTSmodified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Throughput & Load Based Scheduling (4/4)Load based scheduling (Interference Cancellation feature (RAN1308) is applied) if calculated own cell load > Lmincell power based scheduling is applied to increase total cell load up to maximum cell load Node B measures actual RTWP & calculates actual total load

Lmin_cellMax. cell load for HSUPA schedulingSchedulable resourceActual total cell load =own cell load + inter cell interferenceActual own cell loadPrxMaxTargetBTSWCEL; 0..30; 0.1; 6 dB = 2.0LmaxCell = 75%Defines the maximum target level for residual received total wideband power in E-DCH scheduling.The residual received total wideband power is the received interference power after interference cancellation has been performed.PrxMaxOrigTargetBTSMax target received wide band original power for BTS. Parameter used when Interference Cancellation (RAN1308) is applied. WCEL; 0..30; 0.1; 8 dBCorresponding load factor LmaxCell = 1 - 1 / 100.8 = 0.85 (85 %)RTWP < maximum target more HSUPA service can be offeredOtherwise more HSUPA service can not be offered any more; PrxMaxOrigTargetBTSWCEL; 0..30; 0.1; 8 dB PrxMaxOrigTargetBTS= 85%new# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

Serving grant valuesPower ratioE-DPDCH / DPCCHAbsolute & Relative Service Grant (1/2)Absolute grant BTS signals maximum allowed power ratio E-DPDCH / DPCCH by service grant value Mapping between service grant values & power ratios hardcoded Mapping between power ratios & E-TFCs hardcoded Initial power ratio = (21/15)2 independent on service profile and UL load (corresponds to 32 kbps)TB-Index(= E-TFC)Amplitude Ratio321/15727/151134/151947/153960/156760/158575/1510384/15E-TFCTB Index 103 TB size = 15492 bit/10ms 1549.2 kbps# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Absolute & Relative Service Grant (2/2)Relative grant BTS signals to increase / reduce maximum allowed E-DPDCH / DPCCH power ratio When UE receives relative grant UP command, service grant value increases by 1 When UE receives relative grant DOWN command, service grant value decreases by 1

UP e.g. from 23 to 24DOWN e.g. from 19 to 18# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#RTWP Measured > PrxMaxTargetBTS ANDNon-serving E-DCH to total E-DCH power ratio > TargetNSEDCHToTotalEDCHPRHandling non-serving cell overloadScheduling Process (1/4)Handling Non-Serving Cell overload Scheduling procedure is completed every 10 ms Scheduler shall transmit DOWN grant to UE whose serving E-DCH RL is not provided by that BTS if the following criteria are trueTargetNSEDCHToTotalEDCHPRTarget non-serving E-DCH to total E-DCH power ratioWCEL; 0..100 %; = 1 %; 30 %PrxMaxTargetBTSWCEL; 0..30; 0.1; 6 dB = 2.0 LmaxCell = 75%Example BTS measures RTWP = -98 dBm Noise rise = -98 dBm - (-105 dBm) = 7 dB > PrxMaxTargetBTSTotal UL load from RTWP = 1 1 / 100.7 = 0.80 (80 %) Target non-serving E-DCH to total E-DCH power ratio e.g.: = 20% / 40% = 0.5 (50 %) > TargetNSEDCHToTotalEDCHPR both conditions fulfilled DOWN command allowedFirst bit rate ramp up E-AGCH can rapidly increase bit rate allocated to an UE Applicable if there is a single modifiable unhappy UE UE bit rate is not allowed to increase while PS Upgrade Timer Tup is running Value of Tup = 50 ms hardcoded BTS attempts to assign the available resources to that UE using the E-AGCH

E-AGCHAbsolute Grantif only 1unhappy UE# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#BCDECongestion indication received from the RNCRG DownResource reserved &not allocated to other UEDOWN grants generated periodically until No Congestion indication is received from the RNCNo Congestion indication receivedScheduling Process (2/4): Handling congestion indicatorsHandling non-serving cell overloadHandling congestion indicatorsDowngrading phase (B C): Iub congestion detected and reported on per UE basis (Frame Protocol from RNC) Downgrading phase: PS gives relative grant DOWN in pre-defined time interval based upon received congestion indicator Congestion cause can be either Delay Build-up or Frame Loss Frame Loss cause results in more rapid decrease of allocated grant (shorter time between down commands)Remaining phase (C D): No Congestion indication received Timer T2 started Packet scheduler does nothingignores happy bit & low utilization ratioholds current allocated E-TFCI & reserves released power for UE Timer T2 stopped if further congestion indicators receivedT2 expiresT3 startsResource reserved & not allocated to other UE while T3 is runningRecovering phase (D E): Packet scheduler gives relative grant command based upon Happy Bit & other available scheduling information Rest of reserved power shall be kept for this UE while T3 is running# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Low utilisation threshold (0.8, hardcoded)Low utilisation time to trigger (30 ms, hardcoded)Low utilisation flag setLow utilisation flag clearedScheduling Process (3/4)Handling non-serving cell overloadHandling congestion indicatorsHandling low utilizationHandling low utilization Node B monitors utilization of each HSUPA connection Utilization measured by comparing the E-DPDCH / DPCCH power ratios used by UE with those allocated by Node B Measurements filtered prior to evaluation, memory factor used for filteringHandling low utilization (downgrade queue) UE considered for downgrade once every scheduling period Scheduler checks for low utilisation UE within the downgrade queue Relative grant channel (E-RGCH) used to instruct downgradeDowngrade queue: highest allocated E-TFCI = highest priority; lowest allocated E-TFCI = lowest prioritytimeUtilization# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Lrx_EDCH_Allowed = Max(Lrx_EDCH_Power, Lrx_EDCH_Throughput)Lrx_EDCH_Allowed > 0Load increase estimationAllocate GrantLoad decrease estimationAllocate GrantYesNoScheduling Process (4/4)Handling non-serving cell overloadHandling congestion indicatorsHandling low utilizationHandling load increase / decrease Calculate maximum of the load increases allowed by throughput & power based thresholds If either is positive then E-DCH load can be increased Otherwise E-DCH load is decreasedPrxLoadMarginEDCH0..30; 0.1; 2 dB 1.585 LminCell 37%PrxMaxTargetBTS:0..30; 0.1; 6 dB = 2.0 LmaxCell = 75%# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Single Modifiable unhappy UE?fast Ramp-Up ProcedureIncrease the bit rate of the modifiable unhappy UEs using the E-RGCHLoad increase estimationYesModifiable unhappy UEs exists?Sufficient margin to allow an increaseHardware resources available?YesNoYesYesNoExitNoNoLoad Increase & Decrease (1/2)Handling load increaseHandling load increase (upgrade queue) Node B maintains upgrade queue for each HSUPA UE whose serving RL belongs to that Node B Node B sorts UEs according to their current max. allocated E-TFCI UE with lowest allocated E-TFCI is allocated highest priority If 2 UE have same allocated E-TFCI UE with highest utilisation is assigned the highest priority UEs with low utilisation shall not be considered when allocating upgrades

# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Load > PrxMaxTargetBTS ?Decrease the UEs bit rate using the E-RGCHActive E-DCH Exists?YesYesNoExitLoad decrease estimationNoExitLoad Increase & Decrease (2/2)Handling load decreasePrxMaxTargetBTS:0..30; 0.1; 6 dB = 2.0 LmaxCell = 75%# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA RRM: ContentsHSUPA PrinciplesTTI: 2 ms / 10 msHSUPA Physical ChannelsE-TFC SelectionBTS SchedulingHSUPA Power ControlPower Control for HSUPA DL ChannelsPower Control (Inner & Outer Loop) for HSUPA UL ChannelsHSUPA Load ControlHSUPA MobilityHSUPA Channel Type Selection & SwitchingAppendix# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Outer Loop Power Control OLPC for E-DPDCH & E-DPCCH (1/6)R99 1 OLPC entity for each transport channel 1 OLPC controller for all entities belonging to same RRC connection BLER target for RAB fixed

OLPC controller selects entity which indicates largest increase of SIR target Change of SIR target calculated according difference current BLER fixed BLER target HSUPA 1 OLPC entity for DCH + 1 OLPC entity for E-DCH One OLPC entity per each RAB 1 OLPC controller for all entities belonging to same RRC connection Up to four OLPC entities per E-DCH connection BLER target for RAB no longer fixedAdjusted by OLPC controller both for DCH and E-DCH on basis of current performanceCurrent BLER of DCH affects BLER target for E-DCH and vice versaAC provides ideal and maximum BLER target both for DCH and E-DCH OLPC controller selects entity which indicates largest difference current BLER ideal BLER target Change of SIR target calculated according difference current BLER current BLER targetRAN2302 Dynamic HSUPA BLER: Non Real Time (NRT) HSUPA BLER target is dynamically adapted based on HSUPA user transmission constraints:Continuous data stream; Bursty traffic; close to Peak data rates; E-DCH TTI: 2ms TTI, 10 ms TTI;Number of Retransmissions (ReTx);1%BLER on 1st ReTx*10ms TTI:20%BLER on 1st ReTx*10%BLER on 1st ReTx*HSUPA Non-Real Time traffic *Example values. 2msTTI: 10%BLER on 2nd ReTx*modified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#OLPC for E-DPDCH & E-DPCCH (2/6)Maximum & ideal BLER target Provided by AC both for DCH and E-DCH Values hardcoded, not configurable by operator BLER values given on logarithmic scaleMaxBLERTargetDCHMax. BLER target on DCHRNC; -4..-0.3; 0.1; -2 1%BLERTargetDCHIdeal BLER target on DCHRNC; -4..-0.3; 0.1; -2 1%Current BLER target on DCH Combination ofIdeal BLER target on DCHDeviation of current BLER from ideal BLER target on E-DCHDCHSlopeOfTheCurveDCH slope of the curveRNC; 0.1..0.5; 0.1; 0.2BLER_Target_DCH = BLERTargetDCH +DCHSlopeOfTheCurve x (L1BLERTargetEDCH BLER_EDCH)MaxL1BLERTargetEDCHMax. layer 1 BLER target on E-DCHRNC; -4..-0.3; 0.1; -0.8 16%L1BLERTargetEDCHIdeal layer 1 BLER target on E-DCHRNC; -4..-0.3;0.1; -1 10%Current BLER target on E-DCH Combination of Ideal BLER target on E-DCH Deviation of current BLER from ideal BLER target on DCHEDCHSlopeOfTheCurveEDCH slope of the curveRNC; 1..5; 0.5; 2BLER_Target_E-DCH = L1BLERTargetEDCH + EDCHSlopeOfTheCurve x (BLERTargetDCH BLER_DCH)# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#OLPC for E-DPDCH & E-DPCCH (3/6)Example Ideal BLER target on DCH = 1 % Ideal BLER target on E-DCH = 10 % DCHSlopeOfTheCurve = 1..3Increasing BLER on DCH Lower BLER target on E-DCH Stronger trend to increase SIR target (even if DCH is not worst channel)

Decreasing BLER on DCH Higher BLER target on E-DCH Stronger trend to decrease SIR target (even if DCH is not best channel)

# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#OLPC for E-DPDCH & E-DPCCH (4/6)

BLER target set by OLPC after number of ReTransmissions (ReTx)Values configurable by operatorDynHSUPABLERMaxRateThrBPeak rate threshold for Bursty data rates RNC; 10..100; 1; 75 75% Switch to Peak Rate BLER target when data rate is higher than 75% of Max Data RateDynHSUPABLERMaxRateThrC10Peak rate threshold for Continuous 10ms TTI transmission RNC; 10..100; 1; 65 65% Switch to Peak Rate BLER target when TTI=10ms and data rate is higher than 75% of Max Data RateDynHSUPABLERMaxRateThrC2Peak rate threshold for Continuous 2ms TTI transmission RNC; 10..100; 1; 60 60%Switch to Peak Rate BLER target when TTI=2 ms and data rate is higher than 75% of Max Data RateDynHSUPABLERPeakRateRxL1 HARQ retransmissions threshold to use Peak Rate BLER target in OLPC RNC; 1..3; 1; 1 DynHSUPABLERContDataRx2L1 HARQ retransmissions threshold to use Continuous Data Rate BLER target in OLPC when TTI=2ms RNC; 1..3; 1; 2 DynHSUPABLERContDataRx10L1 HARQ retransmissions threshold to use Continuous Data Rate BLER target in OLPC when TTI=10ms RNC; 1..3; 1; 1 BER target is adjusted by OLPC depending on the data rateValues configurable by operatorBLER Target value for EDCH NRT OLPC is set with parameterValues configurable by operatorL1ContBLERTrgtEDCH10 L1 BLER target for the Continuos E-DCH data stream when TTI = 10 ms. RNC; -2..0; 0.1; -0.7 20% L1ContBLERTrgtEDCH2L1 BLER target for the Continuos E-DCH data stream when TTI = 2 ms. RNC; -2..0; 0.1; -1 10% L1BurstDataBLERTrgtEDCHL1 BLER target for the Bursty E-DCH data stream. RNC; -2..0; 0.1; -1 10% L1PeakRateBLERTrgtEDCHL1 BLER target for the Peak E-DCH data rate. RNC; -2..0; 0.1; -2 1% newRAN2302 Dynamic HSUPA BLER requiredNote: parameter defaults are due to change at the time of creation of this document# Nokia Siemens Networks RN3167AEN30GLA1OLPC for E-DPDCH & E-DPCCH (5/6)Initial, minimum & maximum SIR target R99 RAB: Configurable by operator HSUPA RAB Provided by AC Values hardcoded, not configurable by operatorSIRDPCCHInitialEDCHInitial SIR Target for E-DCHRNC; -8.2..-17.3 dB; 0.1 dB;Default values are:...........................1Rx ant...2 Rx ant..4 Rx ant SF256.....................6 dB......3 dB......2 dBSF128.....................6 dB......3 dB......2 dBSF64.......................6 dB......3 dB......2 dBSF32.......................6 dB......3 dB......2 dBSF16.......................6 dB......3 dB......2 dBSF8.........................6 dB......3 dB......2 dBSF4.........................6 dB......3 dB......2 dB2xSF4.....................7 dB......4 dB......3 dB2xSF2.....................9 dB......6 dB......5 dB2xSF2+2xSF4........9 dB.......6 dB......5 dBCurrent SIR target Change of SIR target based on difference current BLER current BLER targetCurrent BLER > current BLER target SIR target increase

Otherwise SIR target decrease

StepSizeForDCHBLERStep Size for DCH BLER calculation RNC; 0.1..1 dB; 0.1 dB; 0.3 dBStepSizeForEDCHBLER Step Size for E-DCH BLER calculationRNC, 0.01..0.1 dB, 0.01 dB; 0.03 dBExample current BLER target = 10 % (0.1) measured BLER = 20 % On DCH SIR target increase = (1- 0.1) * 0.3 dB = 0.27 dB On E-DCH SIR target increase = (1 - 0.1) * 0.03 dB = 0.027 dB measured BLER = 5 % (0.05) On DCH SIR target decrease = 0.1 * 0.3 dB = 0.03 dB On E-DCH SIR target decrease = 0.1 * 0.03 dB = 0.003 dBSIRDPCCHMinimumEDCHMinimum SIR Target for E-DCHRNC; -8.2..-17.3 dB; 0.1 dB; -SIRDPCCHMaximumEDCHMaximum SIR Target for E-DCHRNC; -8.2..-17.3 dB; 0.1 dB; -modified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#OLPC for E-DPDCH & E-DPCCH (/)

From RU40, OLPC DTX is configurable by operator. The value for DTX period is no longer hardcoded to 200ms, but by default is equal to 0msSIR target change requests to be commanded directly after data is available to be send on E-DCH bearerULFastOLPCDTXthld DTX Threshold for uplink faster outer loop.Parameter determines the maximum length of the DTX period. During the DTX period the in-active UL OLPC entity is not allowed to transmit the SIR target modification commands. In case, the controlled bearer has been in DTX for more than DTX period value and being activated (data available on the Transport Channel), the UL outer loop PC Entity is allowed to send SIR Target up modification command to the UL outer loop PC controller. RNFC-FasterOLPCEnabled parameter need to be set to Enabled.

RNC;0 (200ms),1(0ms); 1(0ms)DTX measurement reportOLPC Entity activeOLPC Entity semi-activeOLPC Entity inactiveDTX periodOLPC Entity selected as activeOLPC Entity:- active: can send SIR change UP/DOWN requests- semi-active: can send SIR change UP requests- inactive: cannot send SIR change requestsnew# Nokia Siemens Networks RN3167AEN30GLA1OLPC for E-DPDCH & E-DPCCH (/)

Minimum step size for SIR target modificationMinimum step for SIR target modification that PC Entity can request for UL NRT return channelMinimum step size = 0.1 ... 0.3 dB (PRFILE or PDDB modifiable value)minimal step is smaller thus SIR target modification is more precise

Initial SIR targetSmaller step posssiblet [ms]SIR target [dB]FOLPCStepSizSIRTgt Faster OLPC step size of SIR target changes.Parameter defines the minimum step size of the SIR target modification a PC Entity of UL NRT return channel can request. The value of this parameter is used, if RNFC-FasterOLPCEnabled parameter is set to Enabled. Otherwise, RNC internal constant value 0.3 dB is used. If the minimum value of parameter is used, OLPC adjust SIR target more frequently in smaller steps than if the maximum value is used.

RNC; 0.1..0.3 dB, step 0.1 dB 0.1dBnew# Nokia Siemens Networks RN3167AEN30GLA1OLPC for E-DPDCH & E-DPCCH (/)

Minimum step size for SIR target modificationMinimum step for SIR target modification that PC Entity can request for UL NRT return channelMinimum step size = 0.1 ... 0.3 dB (PRFILE or PDDB modifiable value)minimal step is smaller thus SIR target modification is more preciseIf the minimum value of parameter is used, OLPC entity sends SIR modification command more frequently than if the maximum value is used.

Initial SIR targetSIR target modification intervalt [ms]SIR target [dB]FOLPCSIRTgtModInt Faster OLPC SIR target modification interval.This parameter defines the minimum interval between two SIR target modification commands sent by OLPC entity of UL NRT return channel over the DMPG-DMPG interface. RNFC-FasterOLPCEnabled parameter need to be set to Enabled. Otherwise, RNC internal constant value 500 ms is used.RNC; 100..700 ms, step 100 ms 200 msnew# Nokia Siemens Networks RN3167AEN30GLA1Activity reports and BLER measurements arriveInactivity on both DCH and E-DCHIf BLER failsSIRtarget = SIRtarget + stepupDCHElseSIRtarget = SIRtarget stepdownDCHYesNoNo update for SIR TargetInactivity only on DCHInactivity only on E-DCHYesOnly upgrades AllowedYesOnly Upgrades AllowedNoNoMeasured BLER EDCH IdealBLER Target EDCH>Measured BLER DCH IdealBLER Target DCHIf BLER failsSIRtarget = SIRtarget + stepupEDCHElseSIRtarget = SIRtarget stepdownEDCHNoYesE-DCH OLPC EntityOLPC ControllerDCH OLPC EntityDCH inactiveConsider E-DCH BLER onlyE-DCH inactiveConsider DCH BLER onlyBoth activeOLPC for channel suffering from worst difference measured BLER ideal BLER targetBLER failure:measured BLER > current BLER targetOLPC for E-DPDCH & E-DPCCH (6/6)# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA RRM: ContentsHSUPA PrinciplesTTI: 2 ms / 10 msHSUPA Physical ChannelsE-TFC SelectionBTS SchedulingHSUPA Power ControlHSUPA Load ControlDynamic Load TargetActions in Case of CongestionDCH & E-DCH CongestionHSUPA MobilityHSUPA Channel Type Selection & SwitchingAppendix # Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA Load Control (1/7): Dynamic Load TargetStatic & dynamic load target R99 static load targetFor cells without active HSUPA serviceFixed load target PrxTarget (relative to PrxNoise)Fixed overload threshold PrxOffset (relative to PrxTarget) HSUPA dynamic load targetfor cells with active HSUPA service similar concept as for HSDPA dynamic power allocationfor non-controllable traffic and semi-controllable same fixed load target PrxTarget as in static casefor NRT traffic adjustable load target PrxTargetPSPrxTargetPSMin (minimum value)PrxTargetPSMax (maximum value, also initial value)same PrxOffset value used as in static case to decide about overload actions, but now relative to PrxTargetPSmodified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#PrxTargetPSMinMinimum PS target in HSPA-DCH interference sharingWCEL; 0.1..30; 0.1; 4 dBPrxTargetPSMaxMaximum PS target in HSPA-DCH interference sharing WCEL; 0.1..30; 0.1; 4 dBHSUPA activeNo HSUPA usersNo HSUPA usersPrxTargetPSMin (e.g. 2 dB)PrxTarget (4 dB)PrxTargetPSMax (e.g. 3 dB)PrxTargetPSHSUPA Load Control (2/7): Dynamic Load Targeti.e. fixedPrxMaxTargetBTS0..30; 0.1; 6 dB = 2.0 LmaxCell = 75%PrxNC+PrxSCPrxNRTPrxEDCH*PrxMaxOrigTargetBTSWCEL; 0..30; 0.1; 8 dB PrxMaxOrigTargetBTS= 85%modified*RAN1308 Interference Cancellation feature required**RAN1913 HS Cell_FACH feature requiredPrxTargetPSMaxHSRACH0..30; 0.1; 32767 = special value PrxTargetPSMaxHSRACH= PrxTargetPSMaxPrxTargetPSMaxHSRACH - parameter defines the the maximum allowed target level for the UL PS NRT DCH packet scheduling when the HS-RACH** has been set up in the cellNC-Non Controllable trafficSC Semi Controllable traffic (Streaming)# Nokia Siemens Networks RN3167AEN30GLA1Non-controllable loadBearer bit rates cannot be changed with the link adaptationSemi-controllable loadIn the normal load conditions the bit rate is guaranteed In the overloaded conditions the resources could even be releasedRN3167AEN30GLA1HSUPA RRM & parameters#HSUPA Load Control (/): Dynamic Load Target

When the HS-RACH has been set up in the cell, the Prx_target_PS is possible to adjust between the values of the PrxTargetPSMin and PrxTargetPSMaxHSRACH management parametersWhen the HS-RACH has been set up in the cell, the initial value of the Prx_target_PS is equal to the value of the PrxTargetPSMaxHSRACH parameter. The following scenarios are considered:Initial value is taken into use when the HS-RACH has been set up in the cell.Initial value is taken into use also when the last NRT UL DCH is released in the cell.If PrxTargetPSMaxHSRACH and PrxTargetPSMin parameters are set to an equal value, the RNC does not adjust the Prx_target_PS, but it is used as the target value in the UL NRT DCH resource allocation.Prx_Target_PS is used always when the HS-RACH has been set up in the cell (although there is no E-DCH user on CELL_FACH (HS-RACH user) or CELL_DCH (HSUPA user) states)When the HS-RACH has been set up in the cell, the Prx_target_PS needs to be equal or lower than the value set by the PrxTargetPSMaxHSRACH parameter or than Prx_Target_PS_Target.

PrxTargetPSMin (e.g. 2 dB)PrxTarget (4 dB)PrxTargetPSMax replaced with PrxTargetPSMaxHSRACHPrxTargetPSPrxNC + PrxSCPrxNRTPrxEDCHPrxMaxTargetBTSPrxMaxOrigTargetBTSnew# Nokia Siemens Networks RN3167AEN30GLA1HSUPA Load Control (3/7): Dynamic Load TargetIdeal load target Dynamic load target adjusted ifHigh DCH load or total load ANDCurrent load target deviates from ideal load target Ideal load target PrxTargetIdeal estimated by RNC in dependence onNon controllable traffic PrxNCSemi controllable traffic PrxSC (streaming services)NRT DCH traffic (sum over all weights of R99 services WeightUL_DCH)NRT E-DCH traffic (sum over all weights of HSUPA services WeightEDCH)

Service weights can be set individually for each releaseR99HSPA 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 user

WeightDCHBG Weight of NRT DCH UE BG RABRNC; 0 .. 100; 1; 15WeightDCHTHP1/2/3 Weight of NRT DCH UE THP1/2/3 RABRNC; 0 .. 100; 1; 90/65/40WeightHSPABG Weight of HSPA UE BG RABRNC; 1 .. 100; 1; 25WeightHSPATHP1/2/3 Weight of HSPA UE THP1/2/3 RABRNC; 0 .. 100; 1; 100/75/50modified

# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA Load Control (4/7): Load Target Adjustment Required informationTotal load PrxTotal measured by Node BNon E-DCH load PrxNonEDCH calculated by RNCBoth averaged according PSAveragingWindowSize (same parameter as for R99) Need for adjustment checked periodically according PrxTargetPSAdjustPeriod If adjustment neededIncrease by PrxTargetPSStepUp dB in case of DCH congestionDecrease by PrxTargetPSStepDown dB in case of E-DCH congestionPSAveragingWindowSizeLoad measurement averaging window size for packet schedulingWBTS; 1..20; 1; 4 scheduling periodsPrxTargetPSAdjustPeriodPS target tune period in HSPA-DCH interference sharingWBTS; 1 .. 255; 1; 5 RRI periodsPrxTargetPSStepUpPS target step up in HSPA-DCH interference sharingWCEL; 0.1 .. 1 dB; 0.1 dB; 0.5 dBPrxTargetPSStepDownPS target setup down in HSPA-DCH interference sharingWCEL; 0.1 .. 1 dB; 0.1 dB; 0.5 dB# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA Load Control (5/7): Actions in Case of CongestionDCH congestion only Increase PrxTargetPS by PrxTargetPSStepUp, if currently < ideal load target (but not above PrxTargetPSMax or PrxTargetIdeal)

E-DCH congestion only Decrease PrxTargetPS by PrxTargetPSStepDown, if currently > ideal load target (but not below PrxTargetPSMin or PrxTargetIdeal)

Both DCH & E-DCH congestion Increase PrxTargetPS, if currently < ideal load target Decrease PrxTargetPS, if currently > ideal load targetmodified# Nokia Siemens Networks RN3167AEN30GLA1HSUPa RRM p. 160RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA Load Control (6/7): DCH Congestion Requirements to indicate DCH congestion

PrxNonEDCHPrxTotalPrxTargetPS (e.g. 2.5 dB)

Calculated by RNCCalculated by RNCLoad factor corresponding to current load targetLoad factor corresponding to PrxLoadMarginEDCHPrxMaxTargetBTS0..30; 0.1; 6 dBPrxLoadMarginEDCH0..30; 0.1; 2 dB 1.585 LminCell 37%PrxTargetPSStepUpWCEL; 0.1 .. 1; 0.1; 0.5 dBPrxTargetPSStepDownWCEL; 0.1 .. 1; 0.1; 0.5 dBPSAveragingWindowSizeLoad measurement averaging window size for PSWBTS; 1..20; 1; 4 scheduling periodsPrxTargetPSAdjustPeriodPS target tune period in HSPA-DCH interference sharingWBTS; 1 .. 255; 1; 5 RRI periods# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#E HSUPA Load Control (7/7): E-DCH CongestionPrxTotalPrxTargetPS (e.g. 2.5 dB) Requirements to indicate E-DCH congestion

Reported by Node BCalculated by RNCReported by Node BLoad factor corresponding to PrxLoadMarginEDCHMax (PrxTargetPSStepUp, PrxTargetPSStepDown)PrxMaxTargetBTS0..30; 0.1; 6 dBPrxLoadMarginEDCH0..30; 0.1; 2 dB 1.585 LminCell 37%PrxTargetPSStepUpWCEL; 0.1 .. 1; 0.1; 0.5 dBPrxTargetPSStepDownWCEL; 0.1 .. 1; 0.1; 0.5 dBPrxMaxOrigTargetBTS0..30; 0.1; 8 dBmodified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA RRM: ContentsHSUPA PrinciplesTTI: 2 ms / 10 msHSUPA Physical ChannelsE-TFC SelectionBTS SchedulingHSUPA Power ControlHSUPA Load ControlHSUPA MobilitySoft/Softer HOInter-Frequency & Inter-System HHOHSUPA LayeringHSUPA Channel Type Selection & SwitchingAppendix # Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA RRM: ContentsHSUPA PrinciplesTTI: 2 ms / 10 msHSUPA Physical ChannelsE-TFC SelectionBTS SchedulingHSUPA Power ControlHSUPA Load ControlHSUPA MobilityHSUPA Channel Type Selection & SwitchingE-DCH EstablishmentChannel Type SwitchingE-DCH ReleaseAppendix# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#HSUPA RRM: ContentsHSUPA PrinciplesTTI: 2 ms / 10 msHSUPA Physical ChannelsE-TFC SelectionBTS SchedulingHSUPA Power ControlHSUPA Load ControlHSUPA MobilityHSUPA Channel Type Selection & SwitchingAppendix: Basics of HSUPA Congestion ControlData Flow from UE to RNCCongestion DetectionActions in Case of Congestion

# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#E-DCH FP entity Constructs E-DCH FP frame from MAC- es PDUs and CFN Attaches frame sequence number FSN

E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCData Flow from UE to RNC (3/5)MAC-es PDUCNFMAC-es PDUMAC-es PDUFSNUL FP frame# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

E-DPCHE-DCH_FP_UP (data)Node B sends E-DCH UL FP frame (FSN, CFN and MAC-es PDUs) to RNCData Flow from UE to RNC (4/5)BTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCMAC-es PDUCNFMAC-es PDUMAC-es PDUFSN# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

Node B buffers user plane data at ATM layerBuffering causes variable delay to E-DCH FP transmissionIntermediate ATM nodes across transport network generate further delay variance.Data Flow from UE to RNC (5/5)E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCTNLE-DCH_FP_UP (data)# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCTNLCongestion Detection (1/4)RNC Congestion Detection entity detects possible TNL congestion based upon Delay build-up Lost framesE-DCH_FP_UP (data)# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

Congestion Detection (2/4)E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCTNLFrame loss detected from FSN ifFSN(n) != (FSN(n-1) +1) mod 16Delay calculated from CFN and time of receiving the E-DCH FP frame.

E-DCH_FP_UP (data)# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCTNLDelayFrame lossCongestion detection entity informs congestion indication entity about delay & frame lossCongestion indication entity compares delay with thresholds analogue to those used for HSDPACongestion Detection (3/4)E-DCH_FP_UP (data)# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Congestion Detection (4/4)Delay t1100 msProbability for congestion indication P(t)Pmax70 ms50 msCong. ind. in any caseCong. ind. with rapidlyincreasing P(t)Cong. ind. with slowlyincreasing P(t)DelayThresholdMinMinimum Threshold value for HSUPA congestion delayRNC; 0..320; 0.01; 50 msDelayThresholdMidMiddle Threshold value for HSUPA congestion delay RNC; 0.01..320; 0.01; 70 msDelayThresholdMaxMaximum Threshold for HSUPA congestion handling delayRNC; 0.01..320; 0.01; 100 ms

DelayThresholdMax2msTTIMaximum Threshold for HSUPA congestion handling delay 2ms TTIRNC; 0.01..320; 0.01; 100 ms

For HSUPA configurablemodified# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

Actions in Case of Congestion (1/5)E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCTNLE-DCH_FP_UP (data)E-DCH_FP_CTRL(delay OR Frame loss)In case of too high delay or frame loss congestion indication entity sends E-DCH FP control frame to Node BE-DCH FP control frame type is TNL congestion indication with value TNL congestion detected by delay build-up or TNL congestion detected by frame lossDelayFrame loss# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

Actions in Case of Congestion (2/5)E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCTNLE-DCH_FP_UP (data)Congestion indication(delay OR frame loss)E-DCH FP entity in BTS receives congestion indication & forwards it to E-DCH packet schedulerDelayFrame lossE-DCH_FP_CTRL(delay OR Frame loss)# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCTNLE-DCH_FP_UP (data)Relative Grant[DOWN]DelayFrame lossE-DCH_FP_CTRL(delay OR Frame loss)Congestion indication(delay OR frame loss)Actions in Case of Congestion (3/5)Packet Scheduler decreases UE bit rate by sending relative grant DOWN commandE-DCH Packet Scheduler decreases UE bit rate more aggressively in case of frame loss, compared to delay build-up

# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

E-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCTNLE-DCH_FP_UP (data)Relative Grant[DOWN]DelayFrame lossE-DCH_FP_CTRL(delay OR Frame loss)Congestion indication(delay OR frame loss)Transmission power taken away from UE due to congestion is kept reserved & cannot be given to other UEs in a cellActions in Case of Congestion (4/5)# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#

once congestion is over congestion indication entity send E-DCH FP control frame to Node B Frame type is TNL congestion indication with value no TNL congestion receiving no TNL congestion indication E-DCH packet scheduler stops sending DOWN commands to UE recovers gradually back to normal operationE-DPCHBTSE-DCH FPDownlinkE-DCH FPUplinkE-DCHPacketSchedulerCongestionIndicationCongestionDetectionE-DCH FPRNCTNLE-DCH_FP_UP (data)Relative Grant[UP]Small delayNo frame lossE-DCH_FP_CTRL(no TNL congestion)Congestion indication(no TNL congestion)Actions in Case of Congestion (5/5)# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#Version controlVersionDateStatusOwnerRU10_v1.014.08.2009RU10 level, RANPAR Combined version (A. Annen)Benedikt AschermannRU20_v1.031.12.2009RU20 level RANPAR Combined (Andreas Annen)Benedikt AschermannRU30_v1.108.04.2011RU30 level RANPAR Combined (Andreas Annen)Benedikt Aschermann# Nokia Siemens Networks RN3167AEN30GLA1RN3167AEN30GLA1HSUPA RRM & parameters#