Huawei RAN Feature & Parameter_0428

Apr. 2006 Node B Products of Huawei Huawei RANFeatures & ParametersHUAWEI TECHNOLOGIES CO., LTD.www.huawei.com

HUAWEI TECHNOLOGIES Co., Ltd.HUAWEI Confidential

Page *

Packet Scheduling Power Control Load Control Mobility HSDPA


Page *

Overview of Packet SchedulingPurpose:Scheduling the limited resources between NRT usersOptimize the utilization of system resourcesImprove the throughput of the systemMethods:RAB to RB mappingBit rate switching (DCCC, DCH only)TVM (Traffic Volume Measurement) based bit rate switchingCoverage based bit rate switchingLoad based bit rate reductionRRC state switchingPacket scheduling of HSDPA


Page *

RAB-to-RB MappingTVM based Bit Rate SwitchingCoverage based Bit Rate SwitchingRRC State Switching


Page *

Objective of RAB-to-RB MappingObjective:RB parameters configuration according to QoS of the requested RAB


Page *

RB Mapping Criteria and Contents Criteria:UE capabilities compliedEfficiently make use of the limited radio resourcesGuarantee QoS requirement

Contents:Channel type selectionRB parameter configuration


Page *

Channel Type MappingMain parameters:Mapping principle:

DomainTraffic ClassTransport ChannelSignalingDCH or CCHCSConversationalDCHStreamingPSConversationalDCHStreamingDCH or HS-DSCH InteractiveDCH or CCH or HS-DSCHBackground

MML commandParameter nameParameter IDDefault valueSET UFRCCHLTYPEPARADL BE traffic DCH decision thresholdUL BE traffic DCH decision thresholdDlBeTraffDecThsUlBeTraffDecThs8 kbpsSET UFRCCHLTYPEPARADL BE traffic threshold on HSDPADlBeTraffThsOnHsdpa64kbpsSET UFRCCHLTYPEPARADL streaming threshold on HSDPADlStrThsonHsdpa 64kbps


Page *

RAB-to-RB mappingTVM based Bit Rate SwitchingCoverage based Bit Rate SwitchingRRC State Switching


Page *

Traffic Volume Measurement (TVM) Taffic Volume < ThTaffic Volume > ThADD TYPRABDCCCMCTraffic Volume: RLC Buffer Occupancy: the amount of data in number of bytes that is available for transmission and retransmissionAlgorithm parameters:

TRAFFIC MEASUREMENT EVENT THRESHOLDIndicates the threshold to trigger Event 4A/4B.Default value: 1024/64 byte (4A/4B)Timer to Trigger: Indicates the period of time during which the event condition has to be satisfied, before sending a Measurement ReportDefault value: 240/5000 ms (4A/4B)Pending time after trigger: Indicates the period of time during which it is forbidden to send any new measurement reportsDefault value: 4000/4000 ms (4A/4B)


Page *

Bit Rate Switching based on TVM Report (Uplink)Uplink SET DCCC

Uplink Bit rate threshold for DCCC Range: 8 ~ 384kbpsDefault value: 64 kbpsUplink Rate adjust levelRange: 2 or 3Default value: 2


Page *

Bit Rate Switching based on TVM Report (Downlink)DownlinkSET DCCC

Downlink Bit rate threshold for DCCC Range: 8 ~ 384kbpsDefault value: 64 kbpsDownlink Rate adjust levelRange: 2 or 3Default value: 2


Page *

Summary: TVM based Bit Rate SwitchingImprove the utilization of:Base station transmission PowerChannelization codesIub transmission resources


Page *



Page *

Coverage based Bit Rate SwitchingObject:Avoid call drop due to power limitationGuarantee QoS perceived by userIndicator of Coverage:Downlink Transmitted Code PowerRLC data retransmission


Page *

Transmitted Code Power MeasurementSET UDCCCNote: Absolute threshold of Event E= maximum DL Power - comparative threshold + PO3

Measurement:Event Triggered (Ea/Eb/Fa/Fb)Periodic reported after Ea is triggered Algorithm parameters:

Event Ea relative thresholdEvent E reporting periodEvent Eb relative thresholdEVENT E HYSTERESIS TIMEEvent F reporting power marginEVENT F HYSTERESIS TIMEEvent F reporting period


Page *

RLC Retransmission MonitorADD TYPRABRLCMeasurement:RLC PDU retransmission rate is calculated through ACK and NACK feedback Event A triggered when the retransmission number > thresholdReported from Layer 2 to Layer 3 within RNCSET CORRMALGOSWITCH Algorithm parameters:

Event A thresholdRE-TX monitor periodRE-TX MEASURE FILTER COEFEVENT A TIME TO TRIGGEREVENT A PENDING TIME AFTER TRIGGER

RLC_RETRANS_MEASURE_SWITCH


Page *

Bit Rate Switching based on CoverageIf RLC retransmission measurement is switched on:Rate down switching is performed only when both Event Ea AND Event A are fulfilled


Page *



Page *

DCCC - Channel TransitionChannel TransitionTraffic Volume Report from UE, Event 4a and Event 4b- Event 4a: Traffic volume is above a threshold -> High active- Event 4b: Traffic volumes is below a threshold during a configurable time -> Low activeCell re-selection: - If number of cell reselections exceeds pre-define counters within the cell reselection timer, the UE is considered to be in the state of frequent cell reselectionPaging/Data: - There is data to be transferredUE activitySET UESTATETRANS

BE DCH to FACH to PCH 4B thdBE DCH to FACH 4B time to triggerBE DCH to FACH 4B Pending TimeDCH to FACH transition timerBE FACH TO DCH 4A threshold

FACH to PCH 4B time to triggerFACH to PCH 4B Pending TimeFACH to PCH transition timer

CELL RESELECTION TIMERCELL RESELECTION COUNTER


Page *

Summary - Packet SchedulingChannel TransitionCELL-DCH to/from CELL-FACHCELL-FACH to/from CELL-PCHCELL-PCH to/from URA-PCHRate SwitchingDownlink rate up-switchDownlink rate down-switchUplink rate up-switchUplink rate down-switchUE downlink activity (TVM)Downlink QualityUE uplink activity (TVM)UE activity (TVM)TriggerActionOptimize available resources for Best Effort ServiceAllocation resources dynamically to increase resource utilisationPrevent from call drop for users with high data rate service on the cell boarder UE activity (Cell Reselection)


Page *

Packet Scheduling - Parameters Structure


Page *



Page *

Power Control OverviewOpen-loop Power ControlUL Open-loop Power ControlDL Open-loop Power ControlUL Inner-loop Power ControlDL Inner-loop Power ControlActionInner-loop Power ControlOuter-loop Power ControlDownlink Power BalanceMake a rough estimation of path loss by means of a downlink signal, and then to provide a coarse initial power settingFast closed-loop power control to control the transmit power according to the RX SIR of the peer end, to compensate the fading of radio links UL Outer-loop Power ControlDL Outer-loop Power ControlMaintain the communication quality at the level required by the service bearer through adjustment of the SIR targetReduce the power drift between links during the soft handoverPurpose


Page *

Open Loop Power ControlInner Loop Power ControlOuter Loop Power ControlDownlink Power Balancing


Page *

Open Loop Power ControlObjectiveFor each UE, before accessing the network, and for each base station when RL is set up, estimate the initial UL / DL transmit power based on the downlink path loss calculation

ContentUplink Open Loop Power Control for PARCHUplink Open Loop Power Control for UL DPCCHDownlink Open Loop Power Control for DL DPCCH

Node BUEPRACHBCH: CPICH channel power UL interference levelDCHDCHCPICH Ec/IoRACH measurement reportNode BUE


Page *

Uplink Open-loop Power Control on PRACH


Page *

Uplink Open-loop Power Control on DPCCHDPDCHNo data on DPDCHPC PreambleSRB DelayDPCCH_Initial_Power = DPCCH_Power_Offset - CPICH_RSCP

Various power differences between DPDCH and DPCCH are defined through gain factors, called c for DPCCH and d for DPDCH DPCCH_Power_Offset = PCPICH TRANSMIT POWER + UL interference + CONSTANT VALUE CONFIGURED BY DEFAULT


Page *



Page *

Uplink Inner-loop Power ControlUL Inner-loop Power ControlPower control algorithm selectionUL closed loop power control step sizeFRC.ClassPCA1: UE adjusts uplink transmit power for each slot; the step of PCA1 should be 1dB or 2dB by UL CLOSED LOOP POWER CONTROL STEP SIZE parameter.PCA2: The UE adjusts the uplink transmit power for each 5-slot cycle and the step is 1dB fixedly.

Power control algorithm selection-- ALGORITHM1, ALGORITHM2UL closed loop power control step size -- 1 or 2 dB


Page *

Downlink Inner-loop Power ControlDL Inner-loop Power ControlDL power control modeFRC.ClassFDD DL power control step sizeDPC_MODE = 0The UE sends a unique TPC command in each slot and the TPC command generated is transmitted in the first available TPC field in the uplink DPCCH.DPC_MODE = 1The UE repeats the same TPC command over 3 slots and the new TPC command is transmitted such that there is a new command at the beginning of the frame .


Page *



Page *

Outer-loop Power ControlObjective:Keep the quality of communication at the required level by setting the SIR target for the fast power control


Page *

Mechanism of OLPCN: TTI number of SIR adjustment period N1TTI number of non DTX periodN2TTI number of DTX periodNN1N2 Mechanism:- Single RAB> OLPC based on BLER> OLPC based on DPCCH BER (N1=0, N20)- Multiple RABs> SIR target decrease only when all TrCHs request to decrease its SIRtar If any one of the services requires to increase the SIR target, the maximum value is used for the adjustment. If all the services require to reduce the SIR target, the minimum value is used for the adjustment.> Signaling DCH is involved in OLPC> Guarantee QoS of all TrCHs


Page *



Page *

Downlink Power BalanceSRNCNode BUEPref = (RATIO FOR MAX POWER) / 100 * (Pmax-Pcpich) + (1- RATIO FOR MAX POWER / 100) * (Pmin - Pcpich) After starting power balancing, the RNC calculates the UE DL reference power Pref and sends the Pref to the NodeB by the DOWNLINK POWER CONTROL REQUEST message Objective:To reduce the power drift between links of different NodeB.


Page *



Page *

Overview Intelligent Admission Control Intelligent Congestion Control


Page *

Load Control exists in all phasesLoad Control is used to keep system stable, maximize system capacity while ensuring the coverage and QoS.

Different load control algorithms according to different phases provided:- Before UE access: Potential User Control (PUC)- During UE access: Call Admission Check (CAC) and Intelligent Access Control (IAC)- After UE access: Load Reshuffling (LDR), and Overload Control (OLC)PUC: Potential User Control CAC: Call Admission ControlIAC: Intelligent Admission Control LDR: Load ReshufflingOLC: Overload Control


Page *

Load Control for different load level


Page *

Priority Definition in Huawei ImplementationPriority Consideration Conversational -> Streaming -> Interactive -> BackgroundTraffic ClassARPARP1 -> ARP2 -> ARP3 -> ARP14THPTHP1 -> THP2 -> THP3 -> THP14RAB Integrate Priority Strategy: TC top-priority or ARP top-priorityFor the same TC and ARPFor Interactive with the same ARP, priority is determined by THP. Indicator of Carrier Type Priority to control the priority between R99 and HSDPA. Bear TypeHS-DSCH or DCHTHP is provided in RAN6.0.


Page *

Priority Definition - ExampleServices with different ARP/TC/THP/BearARP is the top-priority, and HSDPA over DCHTC is the top-priority, and HSDPA over DCH

RAB IDARPTraffic ClassTHPBear TypeA1Interactive3DCHB1Interactive3HSDPAC2ConversationalDCHD2BackgroundDCHE2BackgroundHSDPAF2StreamingDCH

RANKARPTraffic ClassTHPBear TypeB1Interactive3HSDPAA1Interactive3DCHC2ConversationalDCHF2StreamingDCHE2BackgroundHSDPAD2BackgroundDCH

RANKTraffic ClassARPTHPBear TypeCConversational2DCHFStreaming2DCHBInteractive13HSDPAAInteractive13DCHEBackground2HSDPADBackground2DCH


Page *

Priority Definition in Huawei ImplementationUser PriorityUser Integrate Priority: - For multiple-RAB users, determined by the service with the highest RAB Integrate Priority.User Priority: Gold (1) Silver (2) Bronze (3)Typical Mapping of ARP and User Priority

ARP01234567891011121314User PriorityERROR11111222223333


Page *

GBR Configuration in Huawei ImplementationFor R99 I/B servicesUplink BE Guarantee Bitrate and Downlink BE Guarantee Bitrate are configurable respectively per cell. Uplink BE Guarantee Bitrate is used in BE downsizing due to uplink cell basic congestion.Downlink BE Guarantee Bitrate is used in BE downsizing due to downlink coverage and downlink cell basic congestion.

For R99 and HSDPA RT servicesGBR is in accordance with the requested guaranteed bit rate in RAB parameters.

For HSDPA I/B servicesDifferent GBRs are configured for Gold/Silver/Copper user.

GoldSilverCopperUplink64kbps64kbps64kbpsDownlink64kbps64kbps64kbps


Page *

Scheduling Priority used in HSDPA

Traffic classARPTHPSPIStreaming114213312Interactive111012913~15821722623~15531432333~152Background182532


Page *



Page *

Overview Resource Admission Check Rate Negotiation Pre-emption / Queuing Direct Retry / Re-direction


Page *

Intelligent Admission Control Overview


Page *

Resource Admission Check Overview

Affected usersUsers in connected modeProcedureMake decision whether to admit new users or service upgrade according to the available system resources.Resources to check1. DL Channelization Code2. Radio Resource: Power / Interference3. Credit: Resource4. Iub transmission bandwidthFor HSDPA/HSUPAMaximum user number per Cell / NodeB


Page *

Overview Resource Admission CheckRadio ResourceCode ResourceIub BandwidthNodeB CE Rate Negotiation Pre-emption / Queuing Direct Retry / Re-direction


Page *

Admission Check of Radio Resource UL and DL independently

On the basis of TCP / RTWP

On the basis of equivalent user number


Page *

Admission Algorithm SelectionAlgorithm 1: based on TCP/RTWP measurement and load increment estimationDownlink:Load level definition: TCP (Transmitted Carrier Power) Uplink: Load level definition: load factorLoad increment of the new request is taken into consideration.

Algorithm 2: based on static Equivalent Number of Users calculationStandard user: 12.2kbps AMR with active factor 100%.

Algorithm 3: based on current TCP/RTWP measurementBased on TCP/RTWP measurement;Load increment of the new request is not taken into consideration


Page *

Uplink Admission Algorithm 1 & 3! Increment is always equal to ZERO when algorithm 3 is applied


Page *

Downlink Admission Algorithm 1&3! Increment is always equal to ZERO when algorithm 3 is applied


Page *

UL & DL Admission Algorithm 2 Based on ENU (Equivalent Number of User s calculation) Standard user: 12.2kbps AMR with activity factor 100%EUN for standard user: 1 ENU for non standard user:Uplink

Downlink


Page *

Priority Handling of Admission Check Threshold for uplink radio resource admission checkThreshold for downlink radio resource admission check

ParametersDefault valueUL Handover access threshold 80UL threshold of Conv AMR service 75UL threshold of Conv non_AMR service 75UL threshold of other services 60

ParametersDefault valueDL Handover access threshold 85DL threshold of Conv AMR service 80DL threshold of Conv non_AMR service 80DL threshold of other services 75


Page *



Page *

Code Management Code management is used to manage the code resource between all the physical channels, including common channel (CCH) e.g. PCPICH and PCCPCH, dedicated channel (DPCH), and shared channel (HSDPA).Code for DPCH:Dynamically allocated Code for common channel:ReservedCode for HSDPA:Shared with R99 (Refer to HSDPA part)


Page *

Code Allocation Mechanism Reserve the codes with smallest SF to improve utilization rate of whole code tree. On the basis of maximum free sub-treeLess code fragments are left


Page *



Page *

Admission Check of Iub BandwidthDPCH ServiceBandwidth consumption: MBR * Active factor

HSDPA ServiceBandwidth consumption: GBR * Active factorConfigurable per service type

Traffic ClassActive FactorScopeCommon Channels0.7NodeBSRB0.5Telephony (AMR&VOIP)0.7R99 Conversational (VP)1R99 Streaming1R99 Interactive0.5R99 Background0.5HSDPA Streaming1HSDPA Interactive1HSDPA Background1


Page *



Page *

Admission Check of NodeB CreditAdmission Check:Credits of local cellCredits of local cell groupCredits of NodeB Credit Consumption Law:Reported from NodeBIn terms of SFHSDPA is not involved

Traffic ClassDirectionSFNumber of CEs ConsumedCorresponding Credits Consumed3.4 kbps SRBDL25611UL2561213.6 kbps SRBDL12811UL641212.2 kbps AMRDL12811UL641264 kbps VPDL3222UL163632 kbps PSDL6411UL321.5364 kbps PSDL3222UL1636128 kbps PSDL1644UL8510384 kbps PSDL888UL41020


Page *



Page *

Rate Negotiation in IACUE capabilitiesPhysical layer capabilityTransport channel capabilityRLC capabilityMaximum allowed bit rateSystem loadChannelization codes Iub transmission resourcesRadio resourcesInitial data rate / Target data rateScenarios: RAB setupRAB modify, reconfiguration


Page *



Page *

Pre-emption and QueuingQueuingWeight based queuingPeriodically retryPre-emptionLow PriorityHigh PriorityIntegrate Priority considered:- Traffic Class- Allocation/Retention Priority- Bear Type (R99/HSDPA)- THP (Traffic Handling Priority)Pqueue = Tmax Telapsed- Telapsed: the time which the service request has queued.- Tmax: the maximum time which the service request can be in the queue.


Page *



Page *

RRC Direct Retry & Re-direction1 RRC CONNECTION REQUEST2 RRC CONNECTION SETUP3 RRC CONNETION SETUP COMPLETEInitially camping on cell 1Freq2Freq1Cell2Resource apply12RRC Direct Retry successfully on cell231 RRC CONNECTION REQUEST2 RRC CONNECTION REJECT(Redirection info )3 Cell reselection: Inter-freq accessOr 3 Cell reselection: Inter-RAT accessInitially camping on cell 1Freq2Freq1Cell2Resource apply12RRC Re-Direct to Inter-Freq or inter-RAT cell3Cell2Inter-RAT Cell1Inter-Freq Cell1

RRC Connection Direct RetryRRC DRD is used when UE initiates RRC CONNECTION REQUEST procedure but is refused by the original cell. RRC Connection Re-directionRRC Redirection is used to indicate UE to reselect an inter-frequency or GSM cell if RRC DRD failed.


Page *

RAB Direct Retry1 RAB Assignment (from CN)2 SRNS relocation (to CN)3 Handover from UTRAN 4 Handover CompleteFreq2Freq1Cell213RNCCN24Cell212RNC31 RAB Assignment (from CN)2 RB SETUP (Freq1) 3 RB SETUP COMPLETE 4 RAB Assignment Resp4

RAB Direct RetryRAB DRD is used when UE initiates RAB ASSIGNMENT procedure but is refused by the original cell and may retry to other cells.


Page *

Parameters: Intelligent Admission Control DRD SwitchMax Queuing Time Length

Rate Negotiation1.PS maximum rate negotiation2.PS & CS initial rate negotiation3.PS target rate negotiation

Pre-emption1.User priority based pre-emption for R992.RAB priority based pre-emption for HSDPA

Queue1.RAB priority based queuing.

DRD1.RRC connection direct retry2.RRC connection redirection3.RAB direct retry


Page *



Page *

OverviewLoad ReshufflingOverload Control


Page *

State of Cell Load (Radio Resource)Load%THOLC100%ABCNormalTimeTHCACTHLDR


Page *

Intelligent Congestion ControlPower ResourcesIub Transmission ResourcesService Quality UnchangedService Quality DowngradedLoad Reshuffling (LDR)DownsizingBE rate reductionAMRCOverload Control (OLC)! Integrate priority is used in LDR and OLC.! Load reshuffling for HSDPA is not available in RAN 5.1.


Page *

OverviewLoad ReshufflingOverload Control


Page *

Triggers of LDRPower Resource:Load level > LDR trigger threshold

Iub Bandwidth:Available Iub bandwidth < predefined threshold

MML commandParameter nameParameter IDDefault valueADD/MOD UCELLLDMUL/DL LDR trigger thresholdULLDRTRIGTHDDLLDRTRIGTHD55%70%ADD/MOD TRMLOADTHForward congestion remain bandwidthBackward congestion remain bandwidthFWDCONGBWBWDCONGBW5%5%


Page *

Inter-Frequency Handover in LDRCandidate target cell:LDR trigger threshold in target cell current load level in target cell > Predefined threshold in target cellCandidate users:Users with the lowest Integrated PriorityBit rate smaller than the predefined maximum bandwidthAction:Blind handoverCell 1Cell 2Load: highLoad: low

MML commandParameter nameParameter IDDefault valueADD/LST/MOD UCELLLDR UL/DL Inter-freq cell load handover load space threshold ULINTERFREQHOCELLLOADSPACETHDDLINTERFREQHOCELLLOADSPACETHD 20 (%)UL/DL Inter-freq cell load handover maximum bandwidth ULINTERFREQHOBWTHD/DLINTERFREQHOBWTHD 200 (kbps)


Page *

BE Rate Reduction in LDRCandidate Users:Users with the lowest integrated priorityOnly BE services are involved.Action:Reconfiguration

HighestHighLowestBit rateGBRPriority384kbps128kbps

MML commandParameter nameParameter IDDefault valueADD/LST/MOD CELLLDR UL/DL LDR-BE rate reduction RAB numberULLDRBERATEREDUCTIONRABNUMDLLDRBERATEREDUCTIONRABNUM1


Page *

AMR Rate Reduction in LDRCandidate service:AMR service with the lowest integrated priorityAction:Downlink: Rate control over Iu interfaceUplink: TFC control over Uu interface.

MML commandParameter nameParameter IDDefault valueADD/LST/MOD CELLLDR UL/DL LDR-AMR rate reduction RAB numberULLDRAMRRATEREDUCTIONRABNUMDLLDRAMRRATEREDUCTIONRABNUM3


Page *

RT Service QoS Renegotiation in LDRCandidate service:PS streamingAction: QoS renegotiation over Iu1) RNC: RAB modification request (Iu)2) CN: RAB assignment (Iu)3) RNC: reconfiguration (Iub/Uu)

MML commandParameter nameParameter IDDefault valueADD/LST/MOD CELLLDR UL/DL LDR un-ctrl RT Qos re-nego RAB numULLDRPSRTQOSRENEGRABNUMDLLDRPSRTQOSRENEGRABNUM1


Page *

Inter-RAT Handover of LDRCandidate target cell:2G cells with same/bigger coverage as serving 3G cell Candidate users:User with lowest Integrated PriorityActions:PS service inter-RAT handoverCS service inter-RAT handover

WCDMAGSM CELLLoad: high

MML commandParameter nameParameter IDDefault valueADD/LST/MOD CELLLDR UL/DL LDR PS inter-rat ho user numberULLDRPSINTERRATHOUSERNUMDLLDRPSINTERRATHOUSERNUM1UL/DL LDR CS inter-rat ho user numberULLDRCSINTERRATHOUSERNUMDLLDRCSINTERRATHOUSERNUM 3


Page *

Summary: Load Reshuffling1st-6th LDR action sequenceUL/DL BE guarantee bit rate

Affected usersUsers in Connected modeProcedureUp to 6 service oriented strategies to use when cell enters basic congestion state.Related ParametersActionsInter-frequency load handoverUsers in CELL_DCHBE service rate reductionUsers with BE serviceAMR reductionUsers with AMR speechInter-RAT load handover in CS domainUsers with CS serviceInter-RAT load handover in PS domainUsers with PS serviceIu Qos renegotiationUsers with Streaming service


Page *

Overview Load Reshuffling Overload Control


Page *

Overload Control (OLC)Actions supported:TFC Control of R99 BE service Drop of low priority UEsSequence of OLC actions:Fast TFC control -> Call drop of UEs


Page *

Fast TFC Control in OLC Downlink TFC ControlPerformed within MAC-d/RNC Uplink TFC ControlRNC -> UE: TFC control


Page *

Parameters of Overload Control

MML commandParameter nameParameter IDDefault valueADD/LST/MOD CELLLDMUL/DL OLC trigger thresholdULOLCTRIGTHDDLOLCTRIGTHD95%UL/DL OLC Release thresholdULOLCRELTHD DLOLCRELTHD90%ADD/LST/MOD CELLOLCUL/DL OLC fast TF restrict RAB numberULOLCFTFRSTRCTRABNUMDLOLCFTFRSTRCTRABNUM3Data rate restrict coefficientRATERSTRCTCOEF68%DL OLC fast TF restrict data rate restrict timer lengthRATERSTRCTTIMERLEN3SDL OLC fast TF restrict data rate recover timer lengthRATERECOVERTIMERLEN5SUL/DL OLC traff release RAB numberULOLCTRAFFRELRABNUM DLOLCTRAFFRELRABNUM0


Page *

Summary: Load Control Parameter Classification


Page *

Call Admission Check Intelligent Access Control Load Reshuffling Service Differentiation EnhancementLoad Control Enhancement


Page *

Power Resource Admission CheckSupport downgrading power for admission

TypeAlgorithmRemarkRAN6.0DCHUL/DL algorithm1Based on power or interference (prediction)UL/DL algorithm2Based on the equivalent number of users UL/DL algorithm3Based on power or interference (without prediction)HSDPABEUser number checkControl the user number mapped on HS-DSCHPBR admission checkCheck the aggregated BE traffic provided bit ratePower usage checkCheck the power usage for HSDPA BEStreamingUser number checkControl the user number mapped on HS-DSCHPBR admission checkCheck the aggregated Streaming traffic provided bit ratePower usage checkCheck the power usage for HSDPA StreamingHSUPAUser number checkControl the user number mapped on E-DCHUL algorithm2Based on the equivalent number of usersMBMSDL algorithm1Based on power (prediction)


Page *

HSUPA Admission Check ProcedureMaximum HSUPA user number UL threshold of Conv AMR serviceUL threshold of Conv non_AMR serviceUL threshold of other servicesUL Handover access threshold Dl HSUPA reserved factorADD CELLCAC E-DPCCH Ec/No and E-DPDCH Ec/No are calculated based on DPCCH Ec/NoUser number admission checkENU admission checkIub transmission resource admission checkNodeB credit resource admission check

NodeB Max Hsupa User Number ADD NODEBALGOPARA


Page *

MBMS Admission Check ProcedureMBMS descend power RAB priority threshold ADD CELLLDR Power resource admission checkCode resource admission checkIub transmission resource admission checkNodeB credit resource admission check

Mechanism of downgrading power for MBMS admission: For a high priority MBMS service, the needed power is the maximum transmit power of FACH. DL threshold of other services is used for comparison. For a low priority MBMS service, the needed power is the maximum transmit power of FACH. LDR threshold is used for comparison. If the admission check fails, the needed power is reduced to the minimum power of FACH.


Page *

Intelligent Access ControlTriggered by admission check failure due to the limitation of EUN, user number and Iub transmissionTriggered by admission check failure due to the limitation of power, code and credit resource

Iu QoS NegotiationRAB DownsizingPreemptionQueuingDRDDCH serviceYYYYYHSDPA serviceYYYYHSUPA serviceYYYYMBMS serviceY


Page *

Load ReshufflingPower ResourcesIub TransmissionResourcesNodeB CreditResourcesHandoverDownsizingRAN-CNRenegotiationIRATHOIFHODCCCAMRCForPS StreamingService Quality UnchangeService Quality DowngradeCSPSLoad Reshuffling (LDR)Monitoring load, trigger the actions corresponding to basic congestionCode ResourcesEUNCode ReshufflingMBMS Power Downgrading! Code reshuffling only due to code limitation is supported in RAN6.0.! MBMS power downgrading only due to power limitation is supported in RAN6.0.


Page *

Available Reshuffling Actions And Objects

ResourceUL/DLLDR ActionsInter-Freq HOBE Rate ReductionInter-RAT CS HOInter-RAT PS HOAMR ReductionIu QoS RenegotiationCode ReshufflingMBMS Power DowngradingPower ResourceULXN.A.DLXCode ResourceULN.A.N.A.N.A.N.A.N.A.N.A.N.A.N.A.DLXXXXXXNodeB CreditULXXX XXDLXXXXXIub Transport ResourceULXXXDLXXXENUULXXN.A.DLXXX

ObjectLDR ActionsInter-Freq HOBE Rate ReductionInter-RAT CS HOInter-RAT PS HOAMR ReductionIu QoS RenegotiationCode ReshufflingMBMS Power DowngradingDCHN.A.HSDPAXXXXXN.A.HSUPAXXXXXN.A.MBMSXXXXXXX


Page *

Load Reshuffling Due To Power LimitationUplinkDownlinkReserved power for HSUPA related DL channels (The power of downlink control channels (E-AGCH/E-RGCH/E-HICH) )Dl HSUPA reserved factor ADD CELLCAC RTWP based UL LDR Power based DL LDR


Page *

Load Reshuffling Due To Code LimitationTrigger conditionCell SF reserve threshold Max user number of code adjust ADD CELLLDRActionsMinimum available SF > reserved SF_Thd Code reshuffling BE rate reduction


Page *

Load Reshuffling Due To NodeB Credit LimitationTrigger conditionActions UL/DL separate Inter-RAT PS/CS HO BE rate reduction


Page *

Load Reshuffling Due To ENU LimitationUplinkDownlink For R99 cell For HSDPA cellIf ENU based DL LDR is enabled, HSDPA users shall not be selected to perform load reshuffling actions. ENU based UL LDR


Page *

Service Differentiation EnhancementThe values of RAB Integrate Priority are set according to the Integrate Priority Configured Reference parameter as follows: If the value of the parameter is set to Traffic Class, the integrate priority abides by the following rules: - Classes of services: conversational -> streaming -> interactive -> background- Services of the same class: priority based on Allocation/Retention Priority (ARP) values- Only for the interactive service of the same ARP value: priority based on THP- Services of the same class and priority: HSDPA or DCH service preferred on the basis of the value of the Indicator of Carrier Type Priority parameter If the value of the parameter is set to ARP, the integrate priority abides by the following rules:- ARP1 -> ARP2 -> ARP3 -> ARP14- Same ARP value: conversational -> streaming -> interactive -> background- Only for the interactive service of the same ARP: priority based on THP- Services of the same ARP, class and THP (only for interactive service ): HSDPA or DCH service preferred on the basis of the value of the Indicator of Carrier Type Priority parameter THP consideration For interactive services, differentiate the priority through THP in the case of same ARP. Applied to determine the integrate priority


Page *



Page *

Mobility Management OverviewProvide the subscribers the continuous communication servicesLoad balancing and resources sharingImprove the utilization of system resources

ClassificationFunctionalityIntra-frequency Soft / Softer / Hard HandoverInter-frequency HandoverInter-RAT HandoverMotiveCoverage Based HandoverLoad Based HandoverUE Speed Based Handover (HCS)Service Based Handover


Page *

Handover ScenariosIntra-frequency HandoverSoft / Softer HandoverHard handover Based on CoverageBased onCoverage

Based onLoad/UE Speed

Inter-RAT HandoverBased onLoad/Service

Inter-frequencyHandoverBased onCoverage

GSM/GPRS/EDGEWCDMA Freq. 1WCDMA Freq. 2


Page *

Intra-Frequency HandoverUE Performs IF Measurement

MEASUREMENT CONTROL message> Measurement Quantity> Event Parameters> Neighbor cell list, etc.

If criteria is matched, UE sends measurement report.

RNC Performs Handover

> Apply for Resource (Admission)> Signaling Procedure Execution> Update Parameters to UEMeasurementPhaseDecisionPhaseExecutionHandoverRNC Makes Decision

> 1A Add Cell to AS> 1B Remove Cell in AS> 1C Replace a Cell in AS> 1D Indicate Best cell- Add 1D cell to AS or do replacement- May do Hard HO

Do Hard HO if conditions are met.


Page *

Intra-Frequency Handover Key ParametersEvent ParametersEvent 1A> CS/PS service 1A event relative threshold> 1A hysteresis > 1A event trigger delay time Event 1B> CS/PS service 1B event relative threshold > 1B hysteresis> 1B event trigger delay time Event 1C> 1C hysteresis> 1C event trigger delay timeEvent 1D> 1D hysteresis> 1D event trigger delay timeMeasurementPhase> Intra-freq Measure Quantity > Cell offset > Max number of cell in active set

DecisionPhase


Page *

Inter-Frequency HandoverHO Triggers1. Based on Coverage> UE Event 2D/2F Report

2. Based on Load > LDR Module Report

3. Based on UE Speed> HCS UE Speed EstimationMeasurement1. CM measurement needed> Periodical Meas. > Event Reporting2D start CM 2F stop CM2B coverage based handover2C load based handover2. No Meas. needed> Blind HO3. Use blind HO or 2C Event Reporting

RNC Perform Handover1. Apply for Resource Admission

2. Signaling Procedure Execution

3. Update Parameters to UEIF HO will be triggered1. Coverage basedPeriodically Reporting:> Signal Quality of target cell meet requirement > Keep Time to TriggerEvent Reporting:> Received 2B Event

2. LDR choose UE and target cell to Blind HO

3. Blind HO or 2C Event Report


Page *

Inter-Frequency Handover Key ParametersMeasurementPhaseHandoverTriggerEvent 2B> Inter-freq CS/PS Target/Used frequency trigger Ec/No THD *Thresholds also for RSCP

Event 2C> Inter-freq measure target frequency trigger Ec/No THD> 2B/2C hysteresis > 2B/2C event trigger delay timeDecisionPhaseEvent 2D> Inter-freq CS/PS measure start Ec/No THD

Event 2F> Inter-freq CS/PS measure stop Ec/No THD * Thresholds also for RSCP> 2D/2F hysteresis > 2D/2F event trigger delay time > Inter-frequency measure report modeInter-frequency measure quantity> Inter-frequency measure periodical rpt period (for periodical reporting mode)For Periodical reporting mode> Inter-freq CS/PS target frequency trigger Ec/No THD (thresholds also for RSCP)> Inter-freq handover min access Ec/No RSCP THD > HHO hysteresis


Page *

Inter-RAT HandoverHandoverTriggerMeasurementPhaseDecisionPhaseExecutionHandoverHO Triggers1. Based on Coverage> UE Event 2D/2F Report

2. Based on Load > LDR Module Report

3. Based on Service> When a service is established> Service HO propertiesMeasurement1. CM measurement needed > Event Reporting2D start CM 2F stop CM3A based on > Periodical Meas. Reporting

2/3. Use 3C Event Reporting.

The RNC initiates a handover procedure. Inter-RAT HO triggered1. Coverage based3A Event Reporting:> Received 3A EventPeriodically Reporting:> Signal quality of target cell meet requirement > Keep Time to Trigger

2/3. HO to cells in 3C Event Report By UE


Page *

Inter-RAT Handover Key ParametersMeasurementPhaseHandoverTriggerEvent 3A> Inter-RAT CS/PS Used frequency trigger Ec/No THD (or RSCP)> Inter-RAT CS/PS handover decision THD

Event 3C> Inter-RAT CS/PS handover decision THD > 3A/3C hysteresis > 3A/3C event trigger delay timeDecisionPhaseEvent 2D> Inter-RAT CS/PS measure start Ec/No THD

Event 2F> Inter-RAT CS/PS measure stop Ec/No THD * Thresholds also for RSCP> 2D/2F hysteresis > 2D/2F event trigger delay time > Inter-RAT report mode > 3A Measure Quantity> Inter-RAT period report interval > BSIC verify switchFor Periodical reporting mode> Time to trigger for verified GSM cell> Time to trigger for non-verified GSM cell> Inter-RAT CS/PS handover decision THD> Inter-RAT hysteresis


Page *



Page *

Overview Channel Type Mapping and SwitchingPower and Code ManagementAdmission ControlSchedulingFlow ControlMobility Management


Page *

HSDPA Key Techniques - OverviewAMCFast SchedulingHARQHybrid ARQ16QAMSF16, 2ms and CDM/TDM3 New Physical Channels


Page *



Page *

Interactive, Background and Streaming service could be mapped onto HS-DSCH.

The bit rate thresholds are used. RABs with maximum bit rate higher than or equal to the threshold will be mapped onto HS-DSCH.The bit rate thresholds (DL streaming threshold on HSDPA , DL BE traffic threshold on HSDPA) are OM configurable.

One switch (PS_STREAMING_ON_HSDPA_SWITCH) is available for operator to disable the mapping of streaming service onto HS-DSCH. HSDPA Channel Mapping


Page *

Channel type switching and state transitionCELL_DCH (with HS-DSCH) CELL_FACH based on user activityCELL_DCH (with HS-DSCH) CELL_DCH (without HS-DSCH)

HSDPA Channel SwitchingBased on user activity (TVM)Trigged by mobilityTriggered by TVMTriggered by timerSET UESTATETRANS SET COIFTIMER

BE HS-DSCH to FACH 4B threshold BE HS-DSCH to FACH 4B time to triggerBE HS-DSCH to FACH 4B Pending TimeBE HS-DSCH to FACH transition timer-- This parameter is used to detect the stability of a UE in low activity state in CELL_DCH (with HS-DSCH) state.

H Retry TimerLength -- Length of retry timer for periodical attempts to map the service onto the HS-DSCH.


Page *



Page *

HSDPA Power AllocationDynamic power allocationDPCHs have the preferential right to occupy the powerNode B can use all the remaining power for HSDPAThe minimum available part for HSDPA can be guaranteedA configurable margin is used to keep the system in stable status


Page *

HSDPA Channel Power Control HS-DPCCHSet power offsets between HS-DPCCH and associated DPCCH for ACK, NACK and CQIDifferent PO values are set according to minimum inter-TTI intervalDifferent PO values are used for soft handoverACKPO1, ACKPO2, ACKPO3NACKPO1, NACKPO2, NACKPO3CQIPOACKPO1FORSHO, ACKPO2FORSHO, ACKPO3FORSHONACKPO1FORSHO, NACKPO2FORSHO, NACKPO3FORSHOCQIPOFORSHOADD CELLHSDPCCH


Page *

HSDPA Channel Power Control HS-SCCH/HS-PDSCHHS-SCCH Power Control MethodHS-SCCH PowerHS-SCCH FERInitial HS-SCCH Transmission PowerMaximum/Minimum HS-SCCH Transmission Power HS-SCCH Power Control Adjustment PeriodStep of Power AdjustmentADD MACHSPARAHS-SCCH Power ControlFixed power controlBased on CQI CQI reported by UE DTX detected by Node B Target FER of HS-SCCHHS-PDSCH Power ControlAllocated by schedulerHSDPA power limitation per userMax Power per H user ADD MACHSPARA


Page *

Static Code AllocationSimple but robustThe code allocation for HS-SCCHs and HS-PDSCHs is static. It is configurableLow code utilization efficiencyHSDPA Code Allocation (1)ADD CELLHSDPA

HS-PDSCH Code Num--- This parameter sets the number of HS-PDSCH codes available in a cell.


Page *

HSDPA Code Allocation (2)RNC will continuously monitor the usage of OVSF codes for DPCH channelsVia RNC reconfiguration procedure Better code utilization efficiencyRNC-Controlled Dynamic AllocationADD CELLHSDPA

Maximum Number of HS-PDSCH Codes-- The maximum number of HS-PDSCH codes available in a cell Minimum Number of HS-PDSCH Codes-- The minimum number of HS-PDSCH codes available in a cell


Page *

HSDPA Code Allocation (3)NodeB-controlled Dynamic Code AllocationThe minimum number of codes for HSDPA is configurableReconfiguration procedure is not neededMaking full use of the whole code treeCodes for CCH and HS-SCCH7891011121314654315210Available codes for DPCHReserved codes for HSDPASF=16Node B enlarges the allocated codes for HSDPA temporally due to HSDPA data transmission if the adjacent code is freeNode B will release the code temporally occupied by HSDPA when it is allocated to DPCH by RNCSF=16SF=16.Code Number for HS-PDSCH ADD CELLHSDPA


Page *



Page *

Intelligent Access Control ProcedureTriggered by admission check failure due to the limitation of user number, power and Iub transmission

Iu QoS NegotiationRAB DownsizingPreemptionQueuingDRDDCH serviceYYYYYHSDPA serviceYYYY


Page *

Downlink Power Admission Control of HSDPA cellNew Measurements for HSDPA cell- Transmitted Carrier Power of all codes not used for HS-DSCH transmission: Pnon-hspa - HS-DSCH GBR required Power: GBP

Load estimation of new HSDPA service- Predicted HS-DSCH required power increase for Steaming service: Ppre-strm - Predicted HS-DSCH required power increase for BE service: Ppre-BE

Power resource admission check of HSDPA service in HSDPA cell

Power resource admission check of R99 service in HSDPA cell


Page *

Dynamic Power Management - OverviewP MaxP non-hspdaGBPRelative ParametersAdmission threshold for R99 power (Thrnon-hspa-cac)Admission threshold for cell total load(Thrtotal-cac)Admission threshold for HSDPA maximum power (Pmax-hspa)


Page *

GBR Consideration in Power Admission Check - DCHP MaxP non-hspdaGBP DCH service access:ABP(A and B) or (A and C) is true, then CAC is OK. C


Page *

Example DCH Access - Accept Suppose that: Pmax=Pmax-hspa; Thrtotal-cac=90%; Thrnon-hspa-cac= 80%Ptotal=90%, low HSDPA load (GBP=30%), low R99 load (30%)P MaxR99(Currently consumed power =30%)HSDPA (Currently consumed power =60%, GBP=30%)P (10%)A30%10%80%B30%60%90%10%TRUE !TRUE !C30%30%10%90%False !


Page *

Example DCH Access - Reject A30%10%80%B30%60%90%Suppose that: Pmax=Pmax-hspa; Thrtotal-cac=90%; Thrnon-hspa-cac=80%Low R99 load (30%), high H GBR load (55%), new R99 call accessesP MaxR99(Currently consumed power = 30%)HSDPA(Currently consumed power =60%, GBP=55%)

P (10%)TRUE !10%C30%55%10%90% False !False !


Page *

Example DCH Access Accept or Reject ?Suppose that: Pmax=Pmax-hspa; Thrtotal-cac=90%; Thrnon-hspa-cac=80%High R99 load (75% or 60%), low H GBR load (15%), new R99 call accessesP MaxR99HSDPA GBP = 15%P (10%)


Page *

GBR Consideration in Power Admission Check - HSDPAP MaxP non-hspdaGBPPABC HSDPA service access:(A and B) or (A and C) is true, then CAC is OK. ** B is not applied to BE service in RAN 5.1.


Page *

Example HSDPA Access AcceptSuppose that: Pmax=Pmax-hspa; Thrtotal-cac=90%; Thrnon-hspa-cac=80%Low H load (30%), low R99 load (30%), new H call accessesP MaxR99Currently consumed power = 30%HSDPACurrently consumed power = 30%, GBP=20%P (15%)(A and B) or (A and C) is trueABC30%20%15%90%15%30%30%20%15%90%100%TRUE !TRUE !TRUE !


Page *

Example HSDPA Access Reject (1)ABC30%55%15%90%15%60%30%55%15%90%Suppose that: Pmax=Pmax-hspa; Thrtotal-cac=90%; Thrnon-hspa-cac=80%Low R99 load (30%), high H GBR load (55%), new H call accessesP MaxP (15%)A is true, but B or C is false100%HSDPACurrently consumed power = 60%, GBP=55%R99Currently consumed power = 30%TRUE !False !False !


Page *

Example HSDPA Access Reject (2)ABC70%15%15%90%15%15%70%15%15%90%100%Suppose that: Pmax=Pmax-hspa; Thrtotal-cac=90%; Thrnon-hspa-cac=80%High R99 load (70%), low H GBR load (15%), new H call accessesP MaxR99H GBRP (15%)A is true, but B or C is falseTRUE !False !False !


Page *

Conclusions Downlink Power Admission for HSDPA CellGBR is introduced to HSDPA I/B services. ARP is considered when setting GBR. Power is shared between HSDPA and R99.Maximum power limitation is available for R99 and HSPDA respectively.HSDPA power is guaranteed for the pre-defined GBR.HSDPA is not best effort !


Page *



Page *

HSDPA EPF Scheduling Algorithmtime500msFor GBR service: GBR+PFFor GBR service: GBR+SPIFor all service: PF + SPITo guarantee the GBR For the users whose GBR is not satisfied in X phaseFor all the users considering fairnessSegmented into three parts

GBR service scheduled with PFX%GBR service forcibly scheduled (Y%)All service scheduled with PF(Z%)

scheduling algorithm periodscheduling algorithm periodscheduling algorithm period


Page *

Fast Scheduling Procedure500msuserAlluserGBRuserScheduling the users with GBRScheduling the users whose GBR is not satisfied in X phaseScheduling all the users

GBR service scheduled with PFX%GBR service forcibly GBR scheduled (Y%)All service scheduled with PF(Z%)


Page *

X, Y, and Z Time Segments in Scheduling Algorithm PeriodX time segment: GBR service: (traditional PF algorithm)Y time segment: GBR services not meeting the GBR requirements Larger SPI indicates higher priority.GBR services with the same SPI can use the RR, MAXC/I, or PF algorithm. Z time segment: all services including GBR ones that meet GBR requirements (PF*algorithm) Note*: priority proportion coefficient that corresponds to SPI value In X time segment, cell throughput is enhanced, which requires a larger segment size. When some GBR services cannot meet the GBR requirements, you must reduce the size of X time segment to enlarge Y segment, thus ensuring GBR services. 2. The sizes of the X, Y, and Z time segments can be dynamically changed to increase cell throughput with guaranteed GBR.


Page *

Power Resource Limiting Ratio in SchedulingPurposeTo settle the issue: The throughput of non GBR services is quite low due to power resources over-occupied by GBR services when the channel conditions are bad, and the power resource efficiency becomes lower.

Example 1. There are three users accessing the HSDPA BE service and two users accessing the HSDPA streaming service at 90 kbps. The CQIs of the five users are 18, 15, 6, 12, and 10. 2. During congestion, each HSDPA user uses 12% power at most. In this situation, the data rate of the third user can be increased from 20 kbps to (40 to 50) kbps at most. Otherwise, the impact on the cell throughput and the experience of the other users in the cell will be large.


Page *

CQI CorrectionInitial BLER-- [1,50]percent SET MACHSPARAImprovement of throughput and downlink loadFactors affecting accuracy of CQI:Channel environmentMeasurement accuracy of UE

CQI correction Node B corrects the CQI according to the target initial BLER and actual data transmission

Chart1

4.6380.575

4.640.3

MAC throughput(Mbps)

Downlink Load

Mac throughput(Mbps)

Downlink Load

Sheet1

Number of HS-PDSCH Code AllocatedIndoor coverageOutdoor macro coverage

51.61.3

154.52.4

MAC throughput(Mbps)Downlink Load

CQAC Closed4.63857.50%

CQAC Open4.6430%

Sheet1

Indoor coverage

Outdoor macro coverage

Num of Codes allocated

Cell throughput(Mbps)

Sheet2

&A

Page &P

MAC throughput(Mbps)

Downlink Load

Mac throughput(Mbps)

Downlink Load

Sheet3


Page *

OverviewChannel Type Mapping and SwitchingPower and Code ManagementAdmission ControlSchedulingFlow ControlMobility Management


Page *

HSDPA Flow Control OverviewNode BUuRNCIubCNWhy ?Balance the data flow between Iub and UuAchieve high bandwidth utilization efficiency, maximize the cell throughput Decrease data transmission delay, avoid data discard and retransmission due to congestionFunctionsResponse to a HS-DSCH Capacity Request, to indicate the number of MAC-d PDUs that the RNC is allowed to transmit for each CmCH-PI of each UE in the specified interval.Modify the capacity and control the user data flow according to the MAC-hs queue buffer size.


Page *

HSDPA Flow Control Procedure over IubQueue based flow control Avoid overflow in queue bufferQuick data transmission over IubIub utilization based flow control Allocate capacity considering available Iub bandwidthAvoid data loss over Iub


Page *

In RAN5.1, available Iub bandwidth for HSDPA is calculated in NodeB : BW_H =Min { (BW_Total - BW R99), BW_H_AAL2Path }BWR99 is the R99 Radio Bearer admitted transmission bandwidth CAC Iub bandwidth.MAC_hs Flow Control Step1: Available Iub Bandwidth for HSDPABWR99BWHSDPATotal AAL2 BW TtimeBWScenario 1 (larger R99 AF): Waste Iub bandwidthScenario 2 (Samll R99 AF): Overbook bandwidth, Iub will be congest Scenario 1: R99 service throughput < R99 CAC admitted BWScenario 2: R99 service throughput > R99 CAC admitted BWRL SET/RL RECONFIG


Page *

MAC_hs Flow Control Step 2 Allocate the H Iub bandwidth among HSDPA users1. HSDPA scheduler calculates each users air throughput and air capacity* 2. Based on each users air throughput, MAC_hs buffer occupation, RLC buffer occupation, MAC_hs calculates each users requirement for Iub bandwidth 3. Allocate the Iub bandwidth to each HSDPA userIf Iub is limited, bandwidth for each user will scale down with same ratio after each users GBR is guaranteed.


Page *

Available Iub bandwidth for HSDPA at Iub interface level:Available Iub Bandwidth for HSDPABWR99i is the R99 Radio Bearer admitted transmission bandwidth. BWR99BWHSDPATotal AAL2 BW TtimeBWScenario 1: Waste Iub bandwidth.Scenario 2: Overbook bandwidth. To avoid Iub congestion, HSDPA flow maps to lower priority PATH, and overbook function be enabled to avoid congestion.Scenario 1: R99 throughput < CAC admitted BWScenario 2: R99 throughput > CAC admitted BW


Page *

Adaptive Adjustment of Available Iub bandwidth for HSDPADetect Iub congestion state based on packet transmission delay (FrameDiscardRateThreshold ) and packet loss (DlTrDelayJitterThldBase). None congestion: Increase HSDPA available BW. Congestion: Decrease HSDPA available BW.


Page *



Page *

HSDPA Mobility Management (1)Handover between HSDPA and R99 cellsSoft handoverThe 1b (remove) is triggered by HSDPA cell Inter-frequency handover2B is triggered by R99 cell Soft handoverHSDPA cell is added into active setThe 1d event is triggered by HSDPA cellInter-frequency handoverThe 2B event is triggered by HSDPA cell


Page *

HSDPA Mobility Management (2)Handover between HSDPA cell and HSDPA cellSET HOCOMM The 1d event is triggered by cell 2Inter-frequency handover2B is triggered by HSDPA cell (cell2)HSDPA serving cell is deleted and the remaining cell supports HSDPA

HSDPA hysteresis timer length -- After event 1D triggers HSDPA handover, this timer is started. Then, event 1D will not trigger HSDPA handover any more before expiry of this timer.


Page *

HSDPA Mobility Management (3)Handover between HSDPA cell and GSM/GPRS cellCoverage basedService basedDirect RetryHSDPS request is initiated in the R99 cell Traffic volume increasesTimerAccess to the original HSDPA cell is rejected

*****The time-to-trigger is used to get time domain hysteresis, i.e. the condition must be fulfilled during the time-to-trigger time before a report is sent. Pending time after trigger is used to limit consecutive reports when one traffic volume measurement report already has been sent and enables periodic reporting while the traffic volume remains above(4a) or below(4b) the threshold.

The pending time after trigger for 4a is the timer started after the event measurement report is triggered. It has two functions: The first is that within the pending time, no more measurement report will be sent for the same measurement ID even the condition that triggers measurement report is met; the second is that when the pending timer times out, it judges whether the traffic is above the upper threshold or under the lower threshold. If yes it restarts the Time to Trigger for 4a timer and wont report any more 4a event unless the timer times out. The bigger the parameter value, the harder to trigger 4a event again. Large value prevents frequent adjustment of the BE service rate. But too large value can make the system respond very slowly. The smaller the parameter value, the easier to trigger event again. But too small value may result in frequent trigger under small fluctuation of the traffic.

The pending time after trigger for 4b is the timer started after the event measurement report is triggered. It has two functions: The first is that within the pending time, no more measurement report will be sent for the same measurement ID even the condition that triggers measurement report is met; the second is that when the pending timer times out, it judges whether the traffic is above the upper threshold or under the lower threshold. If yes it restarts the Time to Trigger for 4b timer and wont report any more 4b event unless the timer times out. The bigger the parameter value, the harder to trigger 4b event again. Large value prevents frequent adjustment of the BE service rate. But too large value can make the system respond very slowly. The smaller the parameter value, the easier to trigger event again. But too small value may result in frequent trigger under small fluctuation of the traffic. *The principle of RATE_UP_ONLY strategy is that:Downsizing is prohibited. If the UE is in low activity, the state of UE will be directly switched to CELL_FACH. Upsizing is performed if RNC receives uplink traffic volume event report 4a.The highest rate which can be upsized to is MIN {the request maximum bit rate assigned by CN, the maximum rate supported by UE capabilities}. ***Event E has two measurement thresholds 1 and 2. Event Ea means that the transmit power rises high above measurement threshold 1, Event Eb means that the transmit power falls below measurement threshold 2.

Event F has two measurement thresholds 1 and 2. Event Fa means the transmit power falls below measurement threshold 1, Event Fb means the transmit power rises above measurement threshold 2.

For different current rate and the upsizing target rate which is triggered by event 4a report, the measurement threshold is different. For the sake of the simplicity, measurement threshold 1 equals the measurement threshold 2 in program and the threshold is calculated by the following formula: Absolute threshold of Event F= maximum DL Power of target ratedifference Power between current rate and target rate Event F reporting power marginEVENT EA RELATIVE THRESHOLD + PO3

When the transmit power of the pilot fields of the DPCCH stays below the measurement threshold 1 for a period longer than T1 (EVENT F HYSTERESIS TIME) , the event Fa is triggered. Then the NodeB periodically report (Reporting period unit for event F and Event F reporting period[ms]) the measurement results of the transmit power to the RNC. When the transmit power of the pilot fields of the DPCCH stays above the measurement threshold 2 for a period longer than T1 (EVENT F HYSTERESIS TIME), the event Fb is triggered. Then the NodeB stop reporting the measurement results of the transmit power. *First, set up a statistic window according to MONITERPR, by which RLC retransmission is calculated, then filter the retransmission value by RE-TX MEASURE FILTER COEF, which is the filter coefficient like the DL code TX power meas filter coef, and judge whether the RLC retransmission value is above the EVENTATHRED, if it is above the threshold for a period of time (MONITERPR EVENT A TIME TO TRIGGER), RLC retransmission event A (This report is defined by ourselves, not standard event defined by 3GPP) is triggered and the RLC retransmission value is reported. *DOWNLINK MID BITRATE THRESHOLD is the middle bit rate threshold for adjustment of traffic volume in downlink. If the level of the traffic volume adjustment algorithm is 2, its value is equal to the RB rate closest to the highest rate divided by two. The bit rate is calculated in the RNC.

The RLC PDU retransmission rate aspect is optional controlled by the RLC_RETRANS_MEASURE_SWITCH parameter. **** ****ADD PRACHBASIC PCPICH transmit power ADD PCPICH/PCPICH transmit power SIB5UL interference SIB7 Increase step 2 maximum preamble retransmission 20. Constant value -20. *An uplink DPCCH Power Control Preamble (PC Preamble) is a period of uplink DPCCH transmission prior to the start of the uplink DPDCH transmission in order to ensure that the inner loop power control has converged when the transmission of the data bits begins. It consists of a given number of DPCCH slots transmitted prior to the data transmission on DPDCH. The RNC transmits the PC Preamble parameter (number of DPCCH preamble slots) in the Uplink DPCH power control info IE using the RRC signaling.

In addition to the PC Preamble delay, the mobile will not send any data on signaling radio bearers during the number of frames indicated in the SRB delay IE, sent through RRC signaling in the Uplink DPCH power control info IE. *****SIR init target valueThis parameter defines the initial SIR target value of Outer Loop Power Control algorithm. Value 0 corresponds to -8.2 dB, value 10 to -7.2 dB, and value 255 to 17.3 dB. OLPC adjustment periodOuter Loop Power Control varies with radio environment. A fast changing radio environment leads to a shorter Outer Loop Power Control adjustment period, while a slower changing one makes the period longer **1 According to measurement control (the measurement parameters includes DPB MEASUREMENT REPORT PERIOD, DPB MEASUREMENT FILTER COEFFICIENT parameters) from the RNC, the NodeB periodically reports the TCP (transmit code power) of RL in soft/softer handover. The RNC determines the power difference of RL for UE in soft/softer status, if the power difference is larger than DPB TRIGGERING THRESHOLD, and then starts the power balance, if less than DPB STOP THRESHOLD, then stops the power balancing.

********RAN6.0*********Pcomm=Pmax * *************Pqueue is the weight for the queuing service request. The service with the smallest values of Pqueue is performed with admission attempt.Telapsed is the time that the service request has queued. The unit is ms. The value of Telapsed can be obtained by the current time stamp minus the recorded queuing time stamp of the service request.Tmax is the maximum time that the service request can be in the queue. The value of Pqueue is approximate to the minimum value 0 when the value of Telapsed is getting close to that of Tmax. **IMA Inverse Multiplexing over ATM*IMA Inverse Multiplexing over ATM****RAN6.0*************For HSUPA services, the RNC should ensure that uplink ENU load which is the sum of the EUN load of users existing (include DCH ,HSUPA)and the EUN load for the new RAB in the cell does not exceed the configurable OM thresholds.

**Downlink Power Resource Decision for MBMSDifferent from the power resource admission of the DCH service, the RNC can decrease the power of low priority MBMS services for admission according to the current load.According to different priorities of new MBMS services, the required power is as follows:1) For a high priority MBMS service, the high power maximum transmit power of FACH is always used for admission.2) For a low priority MBMS service, if the current load is low, the high power maximum transmit power of FACH is used for admission. If the current load is high, the low power is used for admission.

The admission decision is performed in the following procedure:For a high priority MBMS service, the needed power is the maximum transmit power of FACH and the admission decision is made through DL threshold of other services.For a low priority MBMS service, the needed power is the maximum transmit power of FACH and the admission decision is made through DL LDR Trigger threshold. If the admission decision fails to be made, the needed power is reduced to the minimum power of FACH to make the admission decision again.

MBMSMBMSMMLMax FACH Transmit PowerMBMSFACHLeast Coverage Rate of MTCH For RAB Priority 0RABMTCHLeast Coverage Rate of MTCH For RAB Priority 15RABMTCHMin FACH Transmit PowerMBMSFACH

Max FACH Transmit Power - MBMS Descending Power RAB Priority ThresholdMax FACH Transmit Power - Min FACH Transmit Power

MBMSARPMBMS Pnon-hspa+Pmbms,max < Thdother *Pmax

MBMSARPMBMS Pnon-hspa+Pmbms,max < Thdldr *PmaxPnon-hspa+ Pmbms,min < Thdldr *Pmax

*MBMS MBMSMBMSMBMSMBMSRNC10s

**MBMSV18 RABMBMSMBMSMBMSMTCHFACH MBMSRAB0LDRMBMSRABRNCMBMSMTCHFACH IubCOMMON TRANSPORT CHANNEL RECONFIGURATION REQUESTLDRMBMS

R99V18 R99/HS-SCCH/E-AGCH/MBMSSCCPCH/MICH DPCHHSDPADPCHDPCHDPCH N_max

Credit CreditBECreditCreditcreditCreditHSDPACreditHSDPACreditHSUPAE-DCH

V18NodeBCreditV18NodeBNodeBCreditNodeBCredit

** AMRBE V18NSFThdSF_ThdLDR /BE

*CreditDCHHSUPADCHMBMSDCH

******Intra-frequency hard handover is used in either of the following scenarios: No Iur interface between RNCsIn this case soft handover between RNCs is unavailable.Iur interface congestionIn this case soft handover between RNCs is also unavailable.High-speed BE serviceFor the high-speed BE service, intra-frequency hard handover could be used to save downlink capacity, compared with soft handover.Failure in intra-frequency soft handover while intra-frequency hard handover allowed*Intra-frequency hard handover is used in either of the following scenarios: No Iur interface between RNCsIn this case soft handover between RNCs is unavailable.Iur interface congestionIn this case soft handover between RNCs is also unavailable.High-speed BE serviceFor the high-speed BE service, intra-frequency hard handover could be used to save downlink capacity, compared with soft handover.Failure in intra-frequency soft handover while intra-frequency hard handover allowed*LDR: Load ReshufflingCM: compressed mode*LDR: Load ReshufflingCM: compressed mode*LDR: Load ReshufflingCM: compressed mode*LDR: Load ReshufflingCM: compressed mode***Hybrid ARQReceived Transmitted blocks are decodedChecked for CRC errors on decoded blocksIf errors Store the erroneous block without discardingRequest the trasmitter for retransmissionCombine the received re-trasmission with previously received trasnmisison

AMC (Adaptive Modulation & Coding) based on Channel Quality Feedback: Adjust data rate to compensate channel conditions Good channel condition -- Higher rate Bad channel condition Lower rateAdjust the modulation scheme to compensate channel conditions Good channel condition 16QAM Bad channel condition QPSK

AMC may improve air interface bandwidth, and fit for high speed radio transmission.

**********NodeB-controlled dynamic allocation allows the NodeB to use the HS-PDSCH codes that are statically allocated by the RNC. Besides, the NodeB can dynamically allocate the idle codes of the current cell to the HS-PDSCH channel.The NodeB periodically detects the SF16 codes apart from the RNC-allocated HS-PDSCH codes every 2 ms. If the codes or subcodes are allocated by the RNC to the DCH or common channels, they are identified as occupied. Otherwise, they are identified as unoccupied. Therefore, the HS-PDSCH codes available for the HS-PDSCH channel include the codes allocated by the RNC and those consecutive and unoccupied SF16 codes.For example, if the RNC allocates 5 codes to the NodeB, that is, No.11 to 15 SF16 codes are allocated to the HS-PDSCH. Suppose in a 2 ms TTI, No. 0 to 4 SF16 codes are allocated to the DCH or common channels. No. 0 to 4 SF16 codes are occupied. Therefore, in the current TTI, the HS-PDSCH can use No. 5 to 15 SF16 codes.If the DCH codes allocated by the RNC are temporarily occupied by the HS-PDSCH during the setup of radio links, the message returned to the RNC indicates that the radio link is set up successfully. From the next 2 ms TTI, the HS-PDSCH no longer uses these codes until they are released by the DCH. *****Ptotal+Delta, GBR, GBR.

*H, R99, R99R99ABHR99PtotalPHH GBRHH GBRHH GBRH GBRHCH GBRHGBR*H GBR , R99, R99HGBRR99AH GBRBCR99R99HSDPA GBR*H GBR , R99, R99

R99HSPAA75%+10%>80%R99

A(R9960%)H GBRR99BCR99**H, R99, H,HGBPAHR99BCHBCH GBR

*H GBR , R99, HA55%15%70%

Huawei RAN Feature & Parameter_0428

Documents

Transcript of Huawei RAN Feature & Parameter_0428