HSDPA Performance Improvement Discussion_NSN_20070518
Short Description
Nokia HSDPA Performance discussion...
Description
HSDPA Performance Improvement Discussion
- April 30, 2007
For internal use 1 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Performance Testing • Table below is Performance table in initial and final HSDPA mobility test report and it is our target to improve and HSDPA can have better performance (enhancement). However, some might not be easy to see improvement. So we can focus on some KPI – Application Throughput (Most important) – HSDPA Status (channel type distribution) – HSDPA Call Drop – EcNo and RSCP should not be focus because not much L1 optimization and EcNo might be worse if higher average throughput (more HSDPA using) Event Uu_PS_Attach Uu_PS_Attach_OK Attach Successful Rate
Count 53 53
100.0%
Uu_PS_PDPAct_From_UE Uu_PS_PDPAct_From_UE_OK PDP Activation Successful Rate
60 60
Uu_HSDPACallSetup_OK Uu_HSDPACallSetup_Fail HSDPA Call Setup Successful Rate
55 0
HSDPA_Call Drop HSDPA Call Completion Rate For internal use 2 © Nokia Siemens Networks
%
100.0%
Uu_HSDPA_Status Total Time Spent in DCH_R99 Total Time Spent in HSDSCH Total Time Spent in FACH
% 73% 23% 4%
Average EcNo Uu_ActiveSet_EcNo_0 Average RSCP Uu_ActiveSet_RSCP_0 Average Throughput App_Throughput_DL
dB -8.28 dBm -86.19 kbps 681.63
Uu_HSDPA_CQI_Average Uu_HSDPA_NACK_Rate Uu_TrCh_DownlinkBlerAgg
17.20 8.7% 2.9%
100.0% 4
Presentation / Author / Date
92.7%
HSDPA Performance Improvement (RN5.0) • Plot right is for Channel Type Distribution in Tainan Tech Park Cluster Test on April 24 – 73% is DCH99 – 23% is HSDSCH (HSDPA)
• Application Throughput and HSDPA status can be optimized if we can increase HSDPA channel assignment or reduce Interfrequency handover to carrier1 (No HSDPA service)
• To reduce HSDPA Call Drop, we can tune handover related parameter and make cell change smoothly
For internal use 3 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Call Drop Case •
For internal use 4 © Nokia Siemens Networks
Presentation / Author / Date
UE sent e_1a at 11:32:25 but no cell change, it might cause not meet cell change criteria (SHO disable and Release Margin for Average Ec/No:2.5dB and Release Margin for Peak Ec/No:3.5dB)
HSDPA mobility in RAS05 • Serving Cell Change switches the user from HS-DSCH to Cell_FACH then back to HSDSCH
Cell A Service in HSDPA
HS-DSCH coverage Throughput HSDPA
DCH
128kbps or 384kbps according to parameter settings 64kbps
0 For internal use 5 © Nokia Siemens Networks
Presentation / Author / Date
Switching to Cell_FACH within the SHO area
Cell B UE on HSDSCH
HS-DSCH coverage
Details on Cell Change via cell-FACH • HSDPA Serving Cell Change via Cell-FACH feature is used only in intra frequency handover cases, in case of IFHO or ISHO the original DCH switching procedures are used • If the user was moved to Cell-FACH because of intra frequency handover no HSDPA user penalty timers are used on Cell-FACH, the user will be immediately switched to a new HSDPA connection when there is a data volume request either from the UE or RNC • If the user was moved to Cell-FACH because of low throughput then the HSDPA user penalty timers are used on Cell-FACH • If the HSDPA user moves to non-HSDPA cell, the user in HO area will be moved to Cell-FACH. The user will be immediately switched to the DCH of the requested bit rate when there is a data volume request either from the UE or RNC (no need for first DCH0/0 DCH Initial bit rate DCH Final bit rate) • In RAS05, UE goes to cell_FACH in the current serving cell. Possible cell reselection to best server happens in cell_FACH.
For internal use 6 © Nokia Siemens Networks
Presentation / Author / Date
EnableRRCrelease (1/4) - disabled Measurement event 1A triggered HS-DSCH MAC-d flow release and parameter EnableRRCrelease is disabled: UE is transferred to the CELL_FACH state and the radio bearer is mapped to the FACH with the RRC: Radio bearer reconfiguration procedure.
For internal use 7 © Nokia Siemens Networks
Presentation / Author / Date
EnableRRCrelease (2/4) - disabled Ec/No
HSDPA AdditionWindow
P CPICH 1 HSDPA AdditionTime time
HSDPA allocation
Addition Window (HSDPA FMCS) = 0dB
FACH cell update
Addition Time (HSDPA FMCS) = 1280ms EcNo Filter coefficient (HSDPA FMCS) = 800ms SHO of the HSDPA Capable UE (RNC) = disabled Enable RRC release (HSDPA HOPS) = disabled Release Margin Average EcNo (HSDPA HOPS) = 2dB Release Margin Peak EcNo (HSDPA HOPS) = 3.5 dB EcNo Averaging Window (HSDPA HOPS) = 8 For internal use 8 © Nokia Siemens Networks
Presentation / Author / Date
MR(e1A)
RB_Reconfigurat ion (FACH)
EnableRRCrelease (3/4) - enabled • Measurement event 1A triggered HS-DSCH MAC-d flow release and parameter EnableRRCrelease is enabled:
• For users other than HS-DSCH allocated, • EnableRRCRelease indicates whether the RRC connection release (excluding emergency calls) is allowed due to non-optimum fast closed loop power control. •For users with a HS-DSCH, • If the RNC receives measurement event 1A and the EnableRRCRelease parameter is enabled, HS-DSCH MAC-d flow release is not allowed to be triggered directly. •When a cell has entered the reporting range and triggered event 1A and the RNC has not added the cell into the active set, the UE reverts to periodical reporting. This means that the UE continues reporting after the initial report by switching to periodical measurement reporting mode. •As the EnableRRCRelease parameter is enabled, the RNC‟s decision on HSDSCH MAC-d flow release is based on CPICH Ec/No of the serving cell (EcNoDownlink), CPICH Ec/No of the neighbouring cell (EcNoNcell) and the ReleaseMarginAverageEcNo and ReleaseMarginPeakEcNo control parameters. •Based on the periodic measurement reporting mode and the control parameters, the UE is transferred to the CELL_FACH state and the radio bearer is mapped to the FACH with the RRC: Radio bearer reconfiguration procedure if the following conditions are effective: •(1) EcNoDownlink + ReleaseMarginPeakEcNo(n) < EcNoNcell(n) •(2) AveEcNoDownlink + ReleaseMarginAverageEcNo(n) < AveEcNoNcell(n)
For internal use 9 © Nokia Siemens Networks
Presentation / Author / Date
EnableRRCrelease (4/4) - enabled Ec/No HSDPA AdditionWindow
ReleaseMarginAverageE cNo ReleaseMarginPeakEcNo
P CPICH 1 HSDPA AdditionTime
time
HSDPA allocation
Addition Window (HSDPA FMCS) = 0dB
FACH cell update
Addition Time (HSDPA FMCS) = 1280ms EcNo Filter coefficient (HSDPA FMCS) = 800ms SHO of the HSDPA Capable UE (RNC) = disabled Enable RRC release (HSDPA HOPS) = enabled Release Margin Average EcNo (HSDPA HOPS) = 2dB Release Margin Peak EcNo (HSDPA HOPS) = 3.5 dB EcNo Averaging Window (HSDPA HOPS) = 8 For internal use 10 © Nokia Siemens Networks
Presentation / Author / Date
Periodic MR(e1A)
RB_Reconfigurat ion (FACH)
HSDPA Call Drop Case (1) •
For internal use 11 © Nokia Siemens Networks
Presentation / Author / Date
UE sent e_1a at 11:32:25 but no cell change, it might cause not meet cell change criteria (SHO disable and Release Margin for Average Ec/No:2.5dB and Release Margin for Peak Ec/No:3.5dB)
HSDPA Call Drop Case (2)
Drop For internal use 12 © Nokia Siemens Networks
Presentation / Author / Date
•
UE sent e_1a again at 11:32:36 but might be too late (addition window: 0dB and addition time: 320ms) to perform cell change, drop due to bad EcNo
•
Handover related parameter can be tuned to avoid this kind of drop
•
Signaling SHO can be performed in RAS5.1 and UE no need to enter cell-FACH for serving cell change. Can adjust addition window and time to perform SHO earlier
HSDPA Call Drop Case - adjust event_1a addition time and fc • •
•
•
•
•
For internal use 13 © Nokia Siemens Networks
Presentation / Author / Date
In HSDPA service, UE will perform cell change after RRC release criteria fulfill Parameters: Release Margin for Average Ec/No:2.5dB and Release Margin for Peak Ec/No:3.5dB RNC refer to EcNo of active set and monitor set in e_1a MR E_1a parameter in FMCS for HSDPA is used – Addition window:0dB – Addition time: 1280ms – Filter coefficient: 600ms In case, 1st e_1a MR sent by UE but EcNo of active set is 23dB, cell change might not be performed properly (UE can‟t decode RB reconfiguration) SHO can be performed in RAS5.1
HSDPA Call Drop Case - adjust event_1a addition time and fc • • •
•
For internal use 14 © Nokia Siemens Networks
Presentation / Author / Date
Another case have the similar problem Many call drop have similar situation Delay cell change in HSDPA service must be considered because throughput gap in cell-FACH during cell change. But it can be controlled by parameters: – Release Margin for Average Ec/No:2.5dB – Release Margin for Peak Ec/No:3.5dB E_1a parameter in FMCS for HSDPA can be adjusted to trigger earlier to avoid drop – Addition window:0dB – Addition time: 320ms – Filter coefficient: 300ms
Serving Cell Change Functionality Verification (SHO for HSDPA user) _ Message Flow (RN5.1) After SW upgrade: Test on April 29
No Physical channel reconfiguration in intraNodeB handover (Softer handover) ASU to add SC 267 Measurement control to ask UE to perform Periodical EcNo reporting
Periodic EcNo report RAB reconfiguration for Serving cell change to SC267 ASU to remove SC208
For internal use 15 © Nokia Siemens Networks
No RAB reconfiguration to ask UE to cellFACH for Serving cell change Presentation / Author / Date
HSDSCH to DCH • •
For internal use 16 © Nokia Siemens Networks
Presentation / Author / Date
UE sent e_1f of SC169 11:34:25 (active set is 1 in HSDPA in RAN5.0) Before compress mode (physical channel reconfiguration), RNC have sent two radio bearer reconfiguration. One is for 0/0 bit rate and another is for initial bit rate (64/64)
IF/IS Handover Measurement Triggering Reasons 1. Low measured absolute CPICH Ec/No, event 1E/1F FMCI: IFHOcauseCPICHEcNo FMCG: GSMcauseCPICHEcNo
3. UE Tx power approaches its maximum allowed power, event 6A/6D FMCI: IFHOcauseTxPwrUL FMCG: GSMcauseTxPwrUL
2 . Low measured absolute CPICH RSCP, events 1E/1F FMCI: IFHOcauseCPICHrscp, FMCG: GSMcauseCPICHrscp
Measurement Trigger
5. Quality deterioration report from UL outer loop PC FMCI: IFHOcauseUplinkQuality FMCG: GSMcauseUplinkQuality
4. DL DPCH approaches its maximum allowed power FMCI: IFHOcauseTxPwrDL FMCG: GSMcauseTxPwrDL
6 . Others - Load and Service based HO - IMSI based HO - Emergency ISHO
Frequency Measuring Control for Inter-Frequency = FMCI Frequency Measuring Control for Inter-System (GSM) = FMCG For internal use 17 © Nokia Siemens Networks
Presentation / Author / Date
e.g. P-CPICH Ec/No
1. Measurement trigger CPICH Ec/No Reporting event: 1E: A P-CPICH exceeds an absolute threshold 1F: A P-CPICH falls below an absolute threshold (HO triggered if all) Cell 1
Cell 2
Cell 3 1E: HHoRSCPCancel
absolute threshold
1F: HHoRSCPThreshold
1E: HHoEcNoCancelTime
For internal use 18 © Nokia Siemens Networks
Presentation / Author / Date
time 1F: HHoEcNoTimeHysteresis
HSDSCH to DCH but no Physical Channel Reconfiguration (CM mode didn’t be triggered) (1) • •
For internal use 21 © Nokia Siemens Networks
Presentation / Author / Date
UE sent e_1f of SC169 11:34:25 (active set is 1 in HSDPA in RAN5.0) Before compress mode (physical channel reconfiguration), RNC have sent two radio bearer reconfiguration. One is for 0/0 bit rate and another is for initial bit rate (64/64)
HSDSCH to DCH but no Physical Channel Reconfiguration (CM mode didn’t be triggered) (2) •
•
•
•
For internal use 22 © Nokia Siemens Networks
Presentation / Author / Date
However, UE sent e_1e of SC169 11:34:27 (active set is 1 in HSDPA in RAN5.0), so compress mode didn‟t start (no physical channel reconfiguration) and UE stay in Carrier2 (no IFHO) But UE is in DCH99, not in HSDSCH channel, radio bearer reconfiguration is update UE to R99 Max bit rate in downlink, UL/DL: 64/384) NRT SHO criteria will be used to perform SHO and might cause HSDPA didn‟t be used again (resumption didn‟t expire) No IFHO but DCH99 is used due to signal fading, better to adjust e_1f criteria to avoid it.
HsdschGuardTimerHO HS-DSCH guard time after switching to DCH due to HO The parameter determines a period of time during which the HSDSCH allocation is denied after successful channel type switching from HS-DSCH to DCH 0/0 kbps due to handover reasons(e1F, e6A). Timer is not applied if UE is transferred directly to the CELL_FACH state due to reporting event 1A. Range and step 0...30 s, step 1 s Default value 5 s
For internal use 23 © Nokia Siemens Networks
Presentation / Author / Date
Inter-Frequency Handover (1) • •
•
•
For internal use 24 © Nokia Siemens Networks
Presentation / Author / Date
UE sent e_1f of SC169 11:34:25 (active set is 1 in HSDPA in RAN5.0) Before compress mode (physical channel reconfiguration), RNC have sent two radio bearer reconfiguration. One is for 0/0 bit rate and another is for initial bit rate (64/64) Different with previous case, no e_1e from UE, so compress mode is triggered (first physical channel reconfiguration) Measurement report to report ADJI measure. If fulfill HO criteria, RNC send second physical channel reconfiguration to ask UE to carrier1
Inter-Frequency Handover (2) •
• •
For internal use 25 © Nokia Siemens Networks
Presentation / Author / Date
UE is in carrier1 and DCH99 is used because HSDPA didn‟t implement in carrier1. NO chance to use HSDPA service because no ADJI setting in cell of carrier1. HSDPA can be used in next call by DRRC function To evaluate if this IFHO is necessary. If didn‟t perform, will cause PS drop? try to adjust e_1f criteria to avoid IFHO and no drop.
No HSDSCH assignment ( >1 active set before RAB reconfiguration) •
•
•
•
For internal use 26 © Nokia Siemens Networks
Presentation / Author / Date
More than 1 active set before RAB reconfiguration though SHO not allow for HSDPARRCDiversity parameter (follow RRC Release criteria for HO). RNC won‟t assign HSDSCH, instead of DCH99 Parameters: Release Margin for Average Ec/No:2.5dB and Release Margin for Peak Ec/No:3.5dB can be considered to adjust, but drop must be avoided. Cell reselection related parameter can adjust to avoid UE camp to worse cell to initial call HSDPA can be assigned even Active set more than 1 in RAS5.1 and Serving cell change function but worse cell to initial call still need to avoid
CHANNEL TYPE SELECTION HS-DSCH is selected if all of the following conditions are met: 1.
2. 3. 4.
5. 6. 7. 8. 9. 10. 11.
Traffic class and traffic handling priority are allowed on HS-DSCH 1. The operator can configure which traffic classes and handling priority are allowed to be used with HSDPA with HSDSCHQoSclasses parameter. 2. RAN05 only interactive and background traffic classes are supported UE capability supports HS-DSCH The cell supports HSDPA and HS-DSCH is enabled in the cell No multi-RAB (RAN05) or supported multi-RAB combination (RAN05.1) 1. No multiRAB in RAN05 2. AMR + HSDPA possible in RAN05.1 The number of simultaneous HS-DSCH allocations in the BTS/cell is below the maximum number. HsdschGuardTimerHO and HsdschGuardTimerLowThroughput guard timers are not runnig 1. Both guard timers are operator-configurable parameters UE is not performing inter-frequency or inter-system measurements Active set size = 1 (RAN05) UE does not have DCHs scheduled with bit rates higher than 0kbps. HS-DSCH physical layer category is supported If there is no existing MAC-d flow in the cell, condition (A or B, depending on the HSDPApriority parameter) has to be valid. 1. A) PtxNC 0/0 • UE is HSDPA capable • cell is HSDPA capable • Active set size is 1 RAN05 or in RAN05.1 when HSDPAMobility parameter is disabled • Active set contains at least one HSDPA capable cell in RAN05.1 when HSDPAMobility is activated • UE has suitable RAB configuration (allowed RAB configurations can be found from requirement HSDPA.6) • Resumption timer functionality is activated (the value of the timer does not indicate it is off) • HSDPA resumption prevention timer is not active The Handover Control stops the HSDPA resumption timer for the following reasons: • In RAN05 or in RAN05.1 when HSDPAMobility parameter is disabled - Handover (active set change, compressed mode is initiated) • In RAN05.1 when HSDPAMobility parameter is enabled - there is no HSDPA capable cell in the active set anymore - compressed mode is initiated • RAB configuration changes so that HSDPA is not possible anymore (allowed RAB configurations can be found from requirement HSDPA.6) • NRT DCH is released For internal use 53 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Initial Serving Cell Selection – Resumption Timer In RAN05.1, when the HSDPAMobility parameter is enabled, the periodic CPICH Ec/No measurement is used to check the quality of HSDPA capable cell (check the Periodical CPICH Ec/No Measurements section) When the active set size is 1, then the Handover Control asks DCH to HS-DSCH switch from the UE specific PS if HSDPA resumption timer expires When the active set size is bigger than 1, then the handover control checks condition for initial HSDPA service cell selection, after the resumption timer expires
CPICH Ec / No Cell (CPICH Ec / No Best _ cell HSDPAServC ellWindow)
• This means that the switch can not be started until at least one CPICH Ec/No measurement report is received (for example in the case where the value of the resumption timer is 0 s) • If the condition is fulfilled (good enough HSDPA capable cells are found) then the handover control asks DCH to HS-DSCH switch from the UE specific PS
For internal use 54 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Initial Serving Cell Selection – Resumption Timer Switch (DCH -> HS-DSCH) can be refused for the following reasons: • There exists parallel procedures for the UE (UE specific PS) • It is not possible to allocate HSDPA power to the cell (cell specific PS) • Nbr of HSDPA users is exceeded for the cell/BTS (cell specific PS) • HdschGuardTimerHO (def 5s) or HsdschGuardTimerLowThroughput (def 30s) is running If the switch can not be done or is refused, then the Handover Control starts HSDPA resumption prevention timer (5s, 10s, 15s) • Resumption timer can be started again after HSDPA resumption prevention timer has expired • HSDPA resumption prevention timer is increased by 5 seconds every time it is started (i.e. every time the switch DCH -> HS-DSCH is consecutively refused) • However maximum value for HSDPA resumption prevention timer is 15 seconds
For internal use 55 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Initial Serving Cell Selection – Resumption Timer When DCH to HS-DSCH switch is being made then the following things are done: • DCH is released • RB is mapped to DCH 0/0 • normal channel type selection is made to get a HS-DSCH channel, when the next capacity request is received The HS-DSCH allocation follows the principles specified for the MAC-d flow setup starting in the Cell-DCH state • A HS-DSCH is added, MAC-d flow setup and UL/DL DCH replaced with the unidirectional UL DCH with the same synchronised RRC- and NBAP-procedures
For internal use 56 © Nokia Siemens Networks
Presentation / Author / Date
Contents HS-DSCH AC Dynamic Power Allocation (DPA) Link Adaptation Optimisation Proportional Fair Scheduler Initial HSDPA Serving Cell Selection HSDPA Serving Cell Change • • • • • • • • • •
Introduction Periodical CPICH Ec/No Measurements CPIHC Ec/No Triggered SCC Periodical UL SIRerror Triggered SCC Periodical UL SIRerror Measurements Event 1B Triggered SCC Event 1C Triggered SCC RL Failure, Serving HS-DSCH Link Moved to DRNC, RL Removal Due to 6F, 6G Too Frequent Serving Cell Changes ISHO with SCC
For internal use 57 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change RAS05 solution via FACH • Cell change via FACH causing typically 3 s break • HSDPA not available in soft handover soft handover is disabled for HSDPA connections RAS05.1 solution with HSDPA serving cell change • Direct handover from Cell A HSDPA to Cell B HSDPA. Connection break in good case 1) The serving HS-DSCH cell change is based on the intra-frequency CPICH Ec/No measurements reported periodically by the UE and dedicated UL SIRerror measurements reported periodically by the BTS
For internal use 63 © Nokia Siemens Networks
Presentation / Author / Date
Contents HS-DSCH AC Dynamic Power Allocation (DPA) Link Adaptation Optimisation Proportional Fair Scheduler Initial HSDPA Serving Cell Selection HSDPA Serving Cell Change • • • • • • • • • •
Introduction Periodical CPICH Ec/No Measurements CPIHC Ec/No Triggered SCC Periodical UL SIRerror Triggered SCC Periodical UL SIRerror Measurements Event 1B Triggered SCC Event 1C Triggered SCC RL Failure, Serving HS-DSCH Link Moved to DRNC, RL Removal Due to 6F, 6G Too Frequent Serving Cell Changes ISHO with SCC
For internal use 64 © Nokia Siemens Networks
Presentation / Author / Date
Periodical CPICH Ec/No Measurements Intra-frequency measurement reporting criteria of the periodical CPICH Ec/No measurement is determined in the following way: • Measurement reporting mode is fixed – Transfer Mode is 'Acknowledged mode RLC' – Reporting Mode is 'Periodical reporting'
• Measurement quantity is CPICH Ec/No – Filtering of CPICH Ec/No measurement in UE is controlled with the RNPparameter EcNoFilterCoefficient, defined by the HSDPAFmcsIdentifier or RTWithHSDPAFmcsIdentifier parameter set
• Reporting quantity is CPICH Ec/No for active set cells – fixed • Reporting criteria is periodical reporting – The reporting interval is determined by the RNP-parameter HSDPACPICHreportPeriod
For internal use 65 © Nokia Siemens Networks
Presentation / Author / Date
Periodical CPICH Ec/No Measurements Periodically reported DL CPICH Ec/No measurement results are averaged in RNC HSDPACPICHAveWindow (def 3) is RNC specific parameter, which defines how many CPICH Ec/No measurements, which are received in the RRC: MEASUREMENT REPORT message, are included in the sliding window used in the averaging CPICH Ec/No is averaged using the following formula: CPICH Ec / No
CPICH Ec / No (t ) CPICH Ec / No (t 1) ... CPICH Ec / No (t (n 1)) n
• Where CPICHEc/No (t) is the latest CPICHEc/No measurement and n equal to
HSDPACPICHAveWindow • RNC starts the averaging already from the first measurement sample, that is, the RNC calculates the averaged values from those measurement samples which are available until the number of measurement samples is adequate to calculate averaged values over the whole averaging window (=> serving HS-DSCH cell change can be initiated based on 1st Measurement Report as longs as conditions are fulfilled) • RNC calculates the averaged values directly from the measured dB values, linear averaging is not used in this case For internal use 66 © Nokia Siemens Networks
Presentation / Author / Date
Periodical CPICH Ec/No Measurements UE
Node B 2
Node B 1
RNC HSDPA Traffic
Whenever the AS>1 for HSDPA call the RNC orders the UE to start to perform periodical CPICH Ec/No measurements
Measurement Report (DCH) – e1A NBAP: Radio Link Setup NBAP: Radio Link Setup Response RRC: Active Set Update (DCH) NBAP: Radio Link Synchronisation RRC: Active Set Update Complete (DCH) RRC: Measurement Control NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit RRC: Physical Channel Reconfiguration RRC: Measurement Control
Setting up periodical Ec/No measurements for HS-DSCH serving cell change procedure Periodical CPICH Ec/No measurement are started only if the size of the active set is greater than one. If the size of the active set is one, periodical CPICH Ec/No reporting is not started if on going stopped For internaland use 67
© Nokia Siemens Networks
modeSpecificInfo fdd : {
measurementControl-v590ext {
integrityCheckInfo {
cpich-Ec-N0-reportingIndicator TRUE,
rrc-TransactionIdentifier-MSP-v590ext 1
messageAuthenticationCode '0111010101010011111110011001
cpich-RSCP-reportingIndicator FALSE,
} } } } } }
DL-DCCH-Message {
0010'B,
pathloss-reportingIndicator FALSE
rrc-MessageSequenceNumber 12
monitoredSetReportingQuantities {
}, message measurementControl : later-than-r3 : {
dummy noReport,
} },
rrc-TransactionIdentifier 3,
cellIdentity-reportingIndicator FALSE,
criticalExtensions r4 : {
cellSynchronisationInfoReportingIndicator FALSE,
measurementControl-r4 {
modeSpecificInfo fdd : {
measurementIdentity 5,
cpich-Ec-N0-reportingIndicator FALSE,
measurementCommand setup : intraFrequencyMeasurement : {
cpich-RSCP-reportingIndicator FALSE,
intraFreqMeasQuantity {
pathloss-reportingIndicator FALSE } } },
filterCoefficient fc3,
reportCriteria periodicalReportingCriteria : {
modeSpecificInfo fdd : { intraFreqMeasQuantity-FDD cpich-Ec-N0
periodicalReportingCriteria { } },
intraFreqReportingQuantity {
reportingInterval ril0-5 }, reportingCellStatus withinActiveSet : e3 } },
activeSetReportingQuantities {
measurementReportingMode {
dummy noReport,
measurementReportTransferMode acknowledgedModeRLC,
FALSE, Presentation / AuthorcellIdentity-reportingIndicator / Date cellSynchronisationInfoReportingIndicator FALSE,
periodicalOrEventTrigger periodical } }, v4d0NonCriticalExtensions {
Contents HS-DSCH AC Dynamic Power Allocation (DPA) Link Adaptation Optimisation Proportional Fair Scheduler Initial HSDPA Serving Cell Selection HSDPA Serving Cell Change • • • • • • • • • •
Introduction Periodical CPICH Ec/No Measurements CPIHC Ec/No Triggered SCC Periodical UL SIRerror Triggered SCC Periodical UL SIRerror Measurements Event 1B Triggered SCC Event 1C Triggered SCC RL Failure, Serving HS-DSCH Link Moved to DRNC, RL Removal Due to 6F, 6G Too Frequent Serving Cell Changes ISHO with SCC
For internal use 68 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change - Periodical CPICH Ec/No Measurement Triggered When the serving HS-DSCH cell change due to any reason has successfully been executed, the timer is started During the time period, determined by the parameter HSDPACellChangeMinInterval (def 3s), serving HS-DSCH cell change due to periodical CPICH Ec/No measurement, is not allowed for the particular UE The serving HS-DSCH cell change due to any other reason is NOT forbidden even if the timer is running
For internal use 69 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change - Periodical CPICH Ec/No Measurement Triggered When UE reports periodical intra-frequency CPICH Ec/No measurement report, need for the serving HS-DSCH cell change is evaluated (UE is ordered to report periodically the CPICH Ec/No values of the AS cells when AS size > 1) If the CPICH Ec/No of the serving HS-DSCH cell is not close enough to the currently best cell in the active set, serving HS-DSCH cell change is initiated The condition to initiate serving HS-DSCH cell change is defined in the inequality below CPICH Ec / No Serv _ cell (CPICH Ec / No Best _ cell HSDPAServC ellWindow)
If CPICH Ec/No of the serving HS-DSCH cell is greater than or equal to the threshold, determined by the parameter HSDPACPICHEcNoThreshold (def -5dB), serving HSDSCH cell change is not initiated but the current serving cell is kept If the CPICH Ec/No of the serving HS-DSCH cell is greater than or equal to CPICH Ec/No of the best cell subtracted with the value of the parameter HSDPAServCellWindow (def 2dB), serving HS-DSCH cell change is not initiated • CPICHEc/NoServ_cell is the average CPICH Ec/No measurement result of the serving HS-DSCH
cell • CPICHEc/NoBest_cell is the average CPICH Ec/No measurement result of the best cell in the active set • HSDPAServCellWindow is the management parameter , which determines the window - relative to the best cell in the active set - inside of which the serving HS-DSCH cell must be in order to allocate HS-DSCH For internal use 70
© Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change – Impact of Other & Own Cell Interference Looking into the target HSDPA service cell selection formula CPICH Ec / No Serv _ cell (CPICH Ec / No Best _ cell HSDPAServC ellWindow)
• The parameter HSDPAServCellWindow value should be set carefully, below is analysis which shows the impact of delaying the SCC too much or advancing it too much (analysis only takes 2 cells into account) Preferable SCC execution area is achieved with HSDPAServCellWindow = 2dB
For internal use 71 © Nokia Siemens Networks
Presentation / Author / Date
Also HSDPACPICHEcNoThreshold = -5dB means that there is no other cell interefrence present at all (assuming CPICH power 2W CCCH power 2W and HSDPA power 6W, the best possible CPICH Ec/No would be ~-7dB) -> -5dB includes nicely some measurement inaccuracies (spec allows +/- 3dB)
HSDPA Serving Cell Change – Impact of Other & Own Cell Interference Clarifications of graph in previous slide Ptx _ CPICHW 2
G factor _ dB 20 ... 40
Ptx _ R99 trafficW 2
RSCPcell _ edge _ dBm 105
Ptx _ HSDPAW 6
Gcell _ edge _ dB 0
Ptx _ CCCH W 2 based on G - factor G _ maxdB 50 G _ mindB 20
_max 0.96 _min 0.3 G
dB
G _ maxdB G _ mindB G _ mindB GdB m in _max _min G _ maxdB G _ mindB _max - _min
For internal use 72 © Nokia Siemens Networks
Presentation / Author / Date
PathLoss as a functionof G - factor own cell PL : PL _ owndB Ptx _ CPICHdBm RSCPcell _ edge _ dBm G other cell PL : PL _ otherdB Ptx _ CPICHdBm RSCPcell _ edge _ dBm G
HSDPA Serving Cell Change – Impact of Other & Own Cell Interference Clarifications of graph in previous slide Ec/No decrease due to HSDPAin own cell 1 GdB Ptx _ CPICHW Ptx _ CCCH W Ptx _ R99 trafficW Ptx _ HSDPAW
Ec/No_decreaseown_G
PL _ ownW Ptx _ CPICHW Ptx _ CCCH W Ptx _ R99 trafficW 1 GdB NOW PL _ ownW
NOW
Ec/No decrease due to HSDPAin other cell Ptx _ CPICHW Ptx _ CCCH W Ptx _ R99 trafficW Ptx _ HSDPAW NO 1 W PL _ otherW Ptx _ CPICHW Ptx _ CCCH W Ptx _ R99 trafficW NOW PL _ otherW Ec/No_decreaseother_G G factor
Ec / No _ decreasetotal _ dB Ec / No _ decreaseown _ dB Ec / No _ decreaseother _ dB Ec / N _ decreaseother _ dB Ec / No _ decreasetotal _ dB Ec / No _ decreaseown _ dB For internal use 73 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change - Periodical CPICH Ec/No Measurement Triggered Periodical CPICH Ec/No measurement are started only if the size of the active set is greater than one If the size of the active set is one, periodical CPICH Ec/No reporting are not started / if running are stopped RRC: MEASUREMENT CONTROL message is used for starting and stopping of the CPICH Ec/No measurement Periodical CPICH Ec/No measurement is not possible to switch off by operator, but the measurement is always active
For internal use 74 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change - Periodical CPICH Ec/No Measurement Triggered In order to execute inter-BTS serving the HS-DSCH cell change triggered by CPICH Ec/No measurements, the UL SIRerror of the target BTS must be above the threshold determined by the parameter HSDPASIRErrorTargetCell (def -2dB, typically used values 6dB) this has to be set according to HSDPASIRErrorServCell (def -3dB, typically used values -7dB) • SIRerror measurement to be utilised for evaluation is the latest averaged value • In the case of intra-BTS serving HS-DSCH cell change, UL SIRerror needs not to be checked • If UL SIRerror measurement of the target cell has not been received by RNC, handover control executes serving HS-DSCH cell change triggered by DL CPICH Ec/No without taking UL SIRerror measurement into account, i.e. missing UL SIRerror measurement does not prevent serving HS-DSCH cell change • It is possible to switch off usage of the UL SIRerror measurement by setting the reporting interval to 0 • In this case, HS-DSCH allocation is executed without taking UL SIRerror into account More about SIRerror measurements, check HSDPA Serving Cell Change – UL SIRerror Measurement
For internal use 75 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change - Periodical CPICH Ec/No Measurement Triggered HSDPA power allocation shall also affect the selection of the serving HS-DSCH cell All the HSDPA-capable cells, which fulfil the following condition, are selected as possible candidate cells for new serving HS-DSCH cells CPICH Ec / No Cell (CPICH Ec / No Best _ cell HSDPAServC ellWindow)
• CPICHEc/NoBest_cell is the CPICH Ec/No measurement of the best cell in the
active set • CPICHEc/NoCell is the CPICH Ec/No measurement of the candidate • HSDPAServCellWindow is the management parameter , which determines the window - relative to the best cell in the active set - inside of which the serving HS-DSCH cell must be in order to allocate HS-DSCH
For internal use 76 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change - Periodical CPICH Ec/No Measurement Triggered When the cells, which fulfil the DL CPICH Ec/No and UL SIRerror conditions - as specified in the previous slide – are found, the serving HS-DSCH selection is executed according to the following priorities: 1. The cell, which has already HSDPA power allocated is chosen as the serving HS-DSCH cell – If several cells fulfil the criterion, DL CPICH Ec/No determines the order of the cells 2. The cell, which has the best DL CPICH Ec/No is chosen as the serving HSDSCH cell 3. The cell, which has the next best DL CPICH Ec/No is chosen as the serving HS-DSCH cell Note that in order to execute serving HS-DSCH cell change and allocate HSDSCH at the target cell, channel type selection algorithm, must be successful, i.e. Cell/BTS must fulfill all the criteria regarding HS-DSCH allocation If none of the cells in the active set can be chosen as serving HS-DSCH cell, i.e. serving HS-DSCH cell change cannot be executed, the current HS-DSCH allocation is kept
For internal use 77 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change - Failure in the Selection of Serving Cell in the Serving HS-DSCH Cell Change Failure in allocation of Iub AAL2 or RNC internal resources: • When the target cell for serving HS-DSCH cell change has been chosen and if the reservation of the RNC internal resources or Iub AAL2 for the MAC-d flow fails, other possible candidate cells are attempted • If similar failure occurs also for other candidate cells, serving HS-DSCH cell change is not executed • If the current serving HS-DSCH cell cannot be kept, e.g. due to low UL SIRerror or lost radio link, HS-DSCH shall be released and RB mapped to DCH 0/0 Failure in RL reconfiguration: • If the BTS with the serving HS-DSCH cell does not accept RL reconfiguration request and it returns some other general cause code than „Bearer re-arrangement needed', then serving HS-DSCH cell selection is interrupted • If some other BTS than BTS with serving HS-DSCH cell does not accept RL reconfiguration request, then possible other candidates for serving HS-DSCH cell are tried to be selected • If the serving HS-DSCH cell selection is interrupted or new cell can not be found, then current serving HS-DSCH cell is kept or HS-DSCH is released and RB mapped to DCH 0/0 (depending on handover reason) For internal use 78 © Nokia Siemens Networks
Presentation / Author / Date
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UE
Node B 2
Node B 1
SGSN
RNC
HSDPA Traffic
Measurement Report (DCH) – e1A
UL-DCCH-Message {
modeSpecificInfo fdd : {
integrityCheckInfo {
primaryCPICH-Info {
messageAuthenticationCode '11010001000110111110010011011001'B,
primaryScramblingCode 297
rrc-MessageSequenceNumber 4 },
cpich-Ec-N0 29
message measurementReport : { measurementIdentity 1, measuredResults intraFreqMeasuredResultsList : { { cellSynchronisationInfo { modeSpecificInfo fdd : { countC-SFN-Frame-difference { countC-SFN-High 0, off 4 },
},
} },
{ cellSynchronisationInfo { modeSpecificInfo fdd : { countC-SFN-Frame-difference { countC-SFN-High 0, off 247 }, tm 36469 } }, modeSpecificInfo fdd : { primaryCPICH-Info {
tm 7681 } },
primaryScramblingCode 304 },
modeSpecificInfo fdd : { primaryCPICH-Info {
cpich-Ec-N0 24 } } }, eventResults intraFreqEventResults : {
primaryScramblingCode 256 },
eventID e1a,
cpich-Ec-N0 37
cellMeasurementEventResults fdd : {
} },
{cellSynchronisationInfo { modeSpecificInfo fdd : {
{ primaryScramblingCode 297 } } },
countC-SFN-Frame-difference {
v390nonCriticalExtensions {
countC-SFN-High 0,
measurementReport-v390ext { },
off 137 },
laterNonCriticalExtensions {
tm 14429 } },
v4b0NonCriticalExtensions { measurementReport-v4b0ext { }, v590NonCriticalExtensions { measurementReport-v590ext { measuredResults-v590ext intraFrequencyMeasuredResultsList : { {
For internal use 79 © Nokia Siemens Networks
Presentation / Author / Date
},
{
}, { } } } } } } } } }
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UE
Node B 2
Node B 1
RNC
HSDPA Traffic
Measurement Report (DCH) – e1A NBAP: Radio Link Setup NBAP: Radio Link Setup Response RRC: Active Set Update (DCH) DL-DCCH-Message { integrityCheckInfo { messageAuthenticationCode '11010100101111000000000011100110'B, rrc-MessageSequenceNumber 8 }, message activeSetUpdate : r3 : { activeSetUpdate-r3 { rrc-TransactionIdentifier 0, maxAllowedUL-TX-Power 24, rl-AdditionInformationList { { primaryCPICH-Info { primaryScramblingCode 297 }, dl-DPCH-InfoPerRL fdd : { pCPICH-UsageForChannelEst mayBeUsed, dpch-FrameOffset 56, dl-ChannelisationCodeList { { sf-AndCodeNumber sf256 : 12 } }, tpc-CombinationIndex 1 }, tfci-CombiningIndicator FALSE } } } } }
For internal use 80 © Nokia Siemens Networks
Presentation / Author / Date
Normal RL Setup, setting up RL with: UL SF 16 (64kbps service) and DL SF 256 and channelisation code 12
SGSN
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UE
Node B 2
Node B 1
RNC
SGSN
HSDPA Traffic
Measurement Report (DCH) – e1A NBAP: Radio Link Setup NBAP: Radio Link Setup Response RRC: Active Set Update (DCH) NBAP: Radio Link Synchronisation
NBAP: Radio Link Reconfiguration Prepare:
RRC: Measurement Control
Modifying the HS DSCH (HS-DPCCH in SHO for better ACK/NACK and CQI detection):
RRC: Active Set Update Complete (DCH) NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit
CQI Power Offset = 7 -> Delta CQI 4dB ACK Power Offset = 7 -> Delta ACK 4dB Nack Power Offset =7 -> Delta NACK 4dB NBAP: Radio Link Reconfiguration Commit: CFN for the change to be taken into use: 252
For internal use 81 © Nokia Siemens Networks
Presentation / Author / Date
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UE
Node B 2
Node B 1
RNC
SGSN
HSDPA Traffic
Measurement Report (DCH) – e1A NBAP: Radio Link Setup NBAP: Radio Link Setup Response RRC: Active Set Update (DCH) NBAP: Radio Link Synchronisation
DL-DCCH-Message { integrityCheckInfo { messageAuthenticationCode '00101011000000011000111010110000'B, rrc-MessageSequenceNumber 10 }, message physicalChannelReconfiguration : later-than-r3 : { rrc-TransactionIdentifier 0, criticalExtensions criticalExtensions-r4 : r5 : {
RRC: Active Set Update Complete (DCH) RRC: Measurement Control NBAP: Radio Link Reconfiguration Prepare
physicalChannelReconfiguration-r5 { activationTime 252, rrc-StateIndicator cell-DCH, ul-ChannelRequirement ul-DPCH-Info : {
NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit RRC: Physical Channel Reconfiguration
ul-DPCH-PowerControlInfo fdd : { dpcch-PowerOffset -48, pc-Preamble 0, sRB-delay 7, powerControlAlgorithm algorithm1 : 0, deltaACK 7, deltaNACK 7 }, modeSpecificInfo fdd : { scramblingCodeType longSC, scramblingCode 1290484, numberOfDPDCH 1, spreadingFactor sf16, tfci-Existence TRUE, puncturingLimit pl0-68
} },
modeSpecificInfo fdd : { }, dl-HSPDSCH-Information { measurement-feedback-Info { modeSpecificInfo fdd : { measurementPowerOffset 9, feedback-cycle fc4, cqi-RepetitionFactor 1, deltaCQI 7 } }, modeSpecificInfo fdd : NULL } } } } }
For internal use 82 © Nokia Siemens Networks
Presentation / Author / Date
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UE
Node B 2
Node B 1
SGSN
RNC
HSDPA Traffic
Measurement Report (DCH) – e1A NBAP: Radio Link Setup NBAP: Radio Link Setup Response RRC: Active Set Update (DCH) NBAP: Radio Link Synchronisation RRC: Active Set Update Complete (DCH) RRC: Measurement Control NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit RRC: Physical Channel Reconfiguration modeSpecificInfo fdd : {
RRC: Measurement Control
cpich-Ec-N0-reportingIndicator TRUE, cpich-RSCP-reportingIndicator FALSE, pathloss-reportingIndicator FALSE
Setting up periodical Ec/No measurements for HS-DSCH serving cell change procedure Periodical CPICH Ec/No measurement are started only if the size of the active set is greater than one. If the size of the active set is one, periodical CPICH Ec/No reporting is not started For internal useand if on going stopped 83
© Nokia Siemens Networks
} },
monitoredSetReportingQuantities {
DL-DCCH-Message { integrityCheckInfo {
dummy noReport,
messageAuthenticationCode '01110101010100111111100110010010'B,
cellIdentity-reportingIndicator FALSE,
rrc-MessageSequenceNumber 12
cellSynchronisationInfoReportingIndicator FALSE,
}, message measurementControl : later-than-r3 : {
modeSpecificInfo fdd : {
rrc-TransactionIdentifier 3,
cpich-Ec-N0-reportingIndicator FALSE,
criticalExtensions r4 : {
cpich-RSCP-reportingIndicator FALSE, pathloss-reportingIndicator FALSE } } },
measurementControl-r4 {
reportCriteria periodicalReportingCriteria : {
measurementIdentity 5, measurementCommand setup : intraFrequencyMeasurement : {
periodicalReportingCriteria {
intraFreqMeasQuantity {
reportingInterval ril0-5
filterCoefficient fc3,
}, reportingCellStatus withinActiveSet : e3 } }, measurementReportingMode {
modeSpecificInfo fdd : { intraFreqMeasQuantity-FDD cpich-Ec-N0
} },
intraFreqReportingQuantity {
measurementReportTransferMode acknowledgedModeRLC, periodicalOrEventTrigger periodical } },
activeSetReportingQuantities {
v4d0NonCriticalExtensions {
dummy noReport,
v590NonCriticalExtensions-r5 {
cellIdentity-reportingIndicator FALSE,
measurementControl-v590ext {
Presentation / Author / Date cellSynchronisationInfoReportingIndicator FALSE,
rrc-TransactionIdentifier-MSP-v590ext 1 } } } } } }
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UE
Node B 2
Node B 1
RNC
SGSN
HSDPA Traffic
Measurement Report (DCH) – e1A NBAP: Radio Link Setup NBAP: Radio Link Setup Response RRC: Active Set Update (DCH) NBAP: Radio Link Synchronisation
Periodical Measurement Reports UL-DCCH-Message { integrityCheckInfo { messageAuthenticationCode '01110011110000001110011110110110'B,
RRC: Active Set Update Complete (DCH) RRC: Measurement Control NBAP: Radio Link Reconfiguration Prepare
rrc-MessageSequenceNumber 11 }, message measurementReport : { measurementIdentity 5, measuredResults intraFreqMeasuredResultsList : {
NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit RRC: Physical Channel Reconfiguration
{ modeSpecificInfo fdd : { primaryCPICH-Info { primaryScramblingCode 256 }, cpich-Ec-N0 37
} },
{ modeSpecificInfo fdd : {
RRC: Measurement Control RRC: Physical Channel Reconfiguration Complete (DCH)
primaryCPICH-Info { primaryScramblingCode 297 }, cpich-Ec-N0 27 } } }, v390nonCriticalExtensions {
Measurement Report (DCH)
measurementReport-v390ext {
Measurement Report (DCH)
v4b0NonCriticalExtensions {
Measurement Report (DCH)
measurementReport-v4b0ext {
}, laterNonCriticalExtensions {
}, v590NonCriticalExtensions { measurementReport-v590ext { measuredResults-v590ext intraFrequencyMeasuredResultsList : { { }, { } } } } } } } } }
For internal use 84 © Nokia Siemens Networks
Presentation / Author / Date
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UL-DCCH-Message { integrityCheckInfo { messageAuthenticationCode '01110011110000001110011110110110'B, rrc-MessageSequenceNumber 11
Periodically reported DL CPICH Ec/No measurement results are averaged in RNC HSDPACPICHAveWindow is RNC specific management parameter, which defines how many CPICH Ec/No measurements, which are received in the RRC: MEASUREMENT REPORT message, are included in the sliding window used in the averaging RNC starts the averaging already from the first measurement sample (so the Serving cell change is possible after just one measurement report), that is, the RNC calculates the averaged values from those measurement samples which are available until the number of measurement samples is adequate to calculate averaged values over the whole averaging window
For internal use 85 © Nokia Siemens Networks
Presentation / Author / Date
}, message measurementReport : { measurementIdentity 5, measuredResults intraFreqMeasuredResultsList : { { modeSpecificInfo fdd : { primaryCPICH-Info { primaryScramblingCode 256 }, cpich-Ec-N0 37
} },
{ modeSpecificInfo fdd : { primaryCPICH-Info { primaryScramblingCode 297 }, cpich-Ec-N0 27 } } }, v390nonCriticalExtensions { measurementReport-v390ext { }, laterNonCriticalExtensions { v4b0NonCriticalExtensions { measurementReport-v4b0ext { }, v590NonCriticalExtensions { measurementReport-v590ext { measuredResults-v590ext intraFrequencyMeasuredResultsList : { { }, { } } } } } } } } }
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UE
Node B 2
Node B 1
RNC
SGSN
HSDPA Traffic
Measurement Report (DCH) – e1A NBAP: Radio Link Setup NBAP: Radio Link Setup Response RRC: Active Set Update (DCH) NBAP: Radio Link Synchronisation RRC: Active Set Update Complete (DCH) RRC: Measurement Control NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit RRC: Physical Channel Reconfiguration RRC: Measurement Control RRC: Physical Channel Reconfiguration Complete (DCH) Measurement Report (DCH) – e1A
NBAP: Radio Link Reconfiguration Prepare
Measurement Report (DCH) – e1A
Old BTS to delete the HS-DSCH user (MAC-d flow) and
Measurement Report (DCH) – e1A
to new BTS to set up the HS-DSCH (MAC-d flow) with
NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Ready
For internal use 86 © Nokia Siemens Networks
Presentation / Author / Date
CQI Power Offset = 7 -> Delta CQI 4dB ACK Power Offset = 7 -> Delta ACK 4dB Nack Power Offset =7 -> Delta NACK 4dB
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UE
Node B 2
Node B 1
RNC
SGSN
HSDPA Traffic
Measurement Report (DCH) – e1A NBAP: Radio Link Setup NBAP: Radio Link Setup Response RRC: Active Set Update (DCH) NBAP: Radio Link Synchronisation RRC: Active Set Update Complete (DCH) RRC: Measurement Control NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit RRC: Physical Channel Reconfiguration RRC: Measurement Control RRC: Physical Channel Reconfiguration Complete (DCH) Measurement Report (DCH) – e1A
NBAP: Radio Link Reconfiguration Commit for both BTSs
Measurement Report (DCH) – e1A
to inform the CFN when the HS-DSCH serving cell change will be taken into use.
Measurement Report (DCH) – e1A
CFN 148
NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Ready ALCAP : ERQ ALCAP : ECF NBAP: Radio Link Reconfiguration Commit NBAP: Radio Link Reconfiguration Commit For internal use 87 © Nokia Siemens Networks
Presentation / Author / Date
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UE
Node B 2
Node B 1
RNC
SGSN
HSDPA Traffic DL-DCCH-Message { integrityCheckInfo {
Measurement Report (DCH) – e1A
messageAuthenticationCode '00010111101111000000001101110110'B,
NBAP: Radio Link Setup NBAP: Radio Link Setup Response RRC: Active Set Update (DCH) NBAP: Radio Link Synchronisation RRC: Active Set Update Complete (DCH)
rrc-MessageSequenceNumber 13 }, message radioBearerReconfiguration : later-than-r3 : { rrc-TransactionIdentifier 1, criticalExtensions criticalExtensions-r4 : r5 : { radioBearerReconfiguration-r5 { activationTime 148, new-H-RNTI '1001101111001111'B,
RRC: Measurement Control NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit RRC: Physical Channel Reconfiguration
rrc-StateIndicator cell-DCH, specificationMode complete : { dl-AddReconfTransChInfoList { { dl-TransportChannelType hsdsch : NULL, tfs-SignallingMode hsdsch : { addOrReconfMAC-dFlow { mac-hs-AddReconfQueue-List { { mac-hsQueueId 0, mac-dFlowId 0,
RRC: Measurement Control
reorderingReleaseTimer rt120, mac-hsWindowSize mws16
RRC: Physical Channel Reconfiguration Complete (DCH)
} } } } } } }, modeSpecificPhysChInfo fddphch : {
Measurement Report (DCH) – e1A
}, dl-CommonInformation { modeSpecificInfo fdd : {
Measurement Report (DCH) – e1A
}, mac-hsResetIndicator true
Measurement Report (DCH) – e1A
}, dl-InformationPerRL-List {
NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Ready ALCAP : ERQ ALCAP : ECF NBAP: Radio Link Reconfiguration Commit NBAP: Radio Link Reconfiguration Commit For internal use 88 © Nokia Siemens Networks
RRC: Radio Bearer Reconfiguration Presentation / Author / Date
{ modeSpecificInfo fdd : { primaryCPICH-Info { primaryScramblingCode 297 }, servingHSDSCH-RL-indicator TRUE }, dl-DPCH-InfoPerRL fdd : { pCPICH-UsageForChannelEst mayBeUsed, dpch-FrameOffset 56, dl-ChannelisationCodeList { { sf-AndCodeNumber sf256 : 12 } }, tpc-CombinationIndex 1 } }} } } }}
Due to Periodical Ec/No Measurements
Cell DCH – HS-DSCH -> HS-DSCH ->Cell Change UE
Node B 2
Node B 1
RNC
HSDPA Traffic Measurement Report (DCH) – e1A NBAP: Radio Link Setup NBAP: Radio Link Setup Response
RRC: Active Set Update (DCH) NBAP: Radio Link Synchronisation RRC: Active Set Update Complete (DCH) RRC: Measurement Control NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Commit RRC: Physical Channel Reconfiguration RRC: Measurement Control RRC: Physical Channel Reconfiguration Complete (DCH) Measurement Report (DCH) – e1A Measurement Report (DCH) – e1A NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Prepare NBAP: Radio Link Reconfiguration Ready NBAP: Radio Link Reconfiguration Ready ALCAP : ERQ ALCAP : ECF NBAP: Radio Link Reconfiguration Commit NBAP: Radio Link Reconfiguration Commit RRC: Radio Bearer Reconfiguration RRC: Radio Bearer Reconfiguration Complete (DCH) For internal use 89 © Nokia Siemens Networks
Presentation / Author / Date
ALCAP : Release Request ALCAP : Release Confirm
SGSN
Contents HS-DSCH AC Dynamic Power Allocation (DPA) Link Adaptation Optimisation Proportional Fair Scheduler Initial HSDPA Serving Cell Selection HSDPA Serving Cell Change • • • • • • • • • •
Introduction Periodical CPICH Ec/No Measurements CPIHC Ec/No Triggered SCC Periodical UL SIRerror Triggered SCC Periodical UL SIRerror Measurements Event 1B Triggered SCC Event 1C Triggered SCC RL Failure, Serving HS-DSCH Link Moved to DRNC, RL Removal Due to 6F, 6G Too Frequent Serving Cell Changes ISHO with SCC
For internal use 90 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change – UL SIRerror Measurement Triggered It is possible to switch off usage of the UL SIRerror measurement by setting the reporting interval to 0 • In this case, HS-DSCH allocation is executed without taking UL SIRerror into account • In this case, serving HS-DSCH cell change due to UL SIRerror is not allowed When BTS reports periodical dedicated UL SIRerror measurement, need for the serving HS-DSCH BTS change is evaluated If UL SIRerror measurement of the serving cell is not received by RNC, HS-DSCH allocation is not interrupted but the handover control applies other available triggers for the serving HS-DSCH cell change procedure If SIRerror of the current serving HS-DSCH BTS is below the threshold determined by the parameter HSDPASIRErrorServCell (def -3dB, typically used value -7dB), serving HS-DSCH BTS change is initiated
For internal use 91 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change – UL SIRerror Measurement Triggered The new serving HS-DSCH cell is chosen as follows: • DL CPICH Ec/No and UL SIRerror are used as criteria • Note that CPICH Ec/No of the candidate cell does not have to fulfil equation below i.e. it does not have to be inside of the window in order to allocate HS-DSCH (this means that SCC due to UL SIRerror can change the HSDPA Service Cell to non optimal cell – in DL direction)
CPICH Ec / No Cell (CPICH Ec / No Best _ cell HSDPAServC ellWindow) • The CPICH Ec/No and UL SIRerror measurements to be used for evaluation are taken from the
latest averaged value of periodical measurement reports from UE and BTS • UL SIRerror of the target cell must be above or equal to the threshold determined by the parameter HSDPASIRErrorTargetCell (def -2dB, typically used value -6dB) in order to allocate HS-DSCH, i.e. the target cell fulfills the following condition:
SIR ErrorBTS HSDPASIRer rorTargetC ell ) – ,where SIRerrorBTS is the SIRerror measurement of the candidate BTS and HSDPASIRErrorTargetCell is the threshold, which SIRerror of the candidate BTS must fulfill
For internal use 92 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change – UL SIRerror Measurement Triggered If UL SIRerror measurement of the target cell has not been received by RNC, handover control excludes this particular cell from the candidate list of the serving HS-DSCH cell change procedure triggered by UL SIRerror measurement of the serving cell When the cells, which fulfil the UL SIRerror condition are found, the serving HS-DSCH selection is executed according to the following priorities: 1. The cell, which has already HSDPA power allocated is chosen as the serving HSDSCH cell – If several cells fulfil the criterion, DL CPICH Ec/No determines the order of the cells 2. The cell, which has the best DL CPICH Ec/No is chosen as the serving HS-DSCH cell 3. The cell, which has the next best DL CPICH Ec/No is chosen as the serving HSDSCH cell Note that in order to execute serving HS-DSCH cell change and allocate HS-DSCH at the target cell, channel type selection algorithm must be successful, i.e. Cell/BTS must fulfill all the criteria regarding HS-DSCH allocation If the cell, which fulfils the condition specified above cannot be found, HS-DSCH is released an switch to DCH 0/0 kbps executed For internal use 93 © Nokia Siemens Networks
Presentation / Author / Date
Contents HS-DSCH AC Dynamic Power Allocation (DPA) Link Adaptation Optimisation Proportional Fair Scheduler Initial HSDPA Serving Cell Selection HSDPA Serving Cell Change • • • • • • • • • •
Introduction Periodical CPICH Ec/No Measurements CPIHC Ec/No Triggered SCC Periodical UL SIRerror Triggered SCC Periodical UL SIRerror Measurements Event 1B Triggered SCC Event 1C Triggered SCC RL Failure, Serving HS-DSCH Link Moved to DRNC, RL Removal Due to 6F, 6G Too Frequent Serving Cell Changes ISHO with SCC
For internal use 94 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change – UL SIRerror Measurement UL SIRerror measurement is used as a criterion for serving HS-DSCH cell change UL SIRerror can also initiate release of the HS-DSCH After HS-DSCH is allocated to the UE, periodical UL SIRerror measurement is started Dedicated UL SIRerror measurement is applied to the selection of the serving HSDSCH cell and it is also used as criterion for a sufficient UL quality for HS-DPCCH transmission Reporting is periodical, except when measurement report is filtered in BTS Reporting criteria of the dedicated UL SIRerror measurement is determined in the following way • Dedicated measurement type is SIRerror • Dedicated measurement object type is ALL RLS
For internal use 95 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change – UL SIRerror Measurement Measurement filter coefficient is determined by the RNP-parameter HSDPASIRErrorFilterCoefficient • The parameter determines the value of filtering coefficient to be used in higher layer filtering of the measurement result • The filter coefficient parameter controls the higher layer filtering of physical layer UL SIRerror measurements before measurement reporting is performed by the BTS • The approximated weight of the latest measurement result with the different values of the parameter is as follows: Value (Weight): 0 (100%), 1 (71%), 2 (50%), 3 (35%), 4 (25%), 5 (18%), 6 (13%), 7 (9%), 8 (6%), 9 (4%), 11 (2%) • Higher layer filtering has been specified in the 3GPP TS 25.433 – “The Measurement Filter Coefficient IE indicates how filtering of the measurement values shall be performed before measurement event evaluation and reporting. – The averaging shall be performed according to the following formula. Fn (1 a) Fn 1 a M n
– – – –
The variables in the formula are defined as follows: Fn is the updated filtered measurement result Fn-1 is the old filtered measurement result Mn is the latest received measurement result from physical layer measurements, the unit used for Mn is the same unit as the reported unit in the COMMON MEASUREMENT INITIATION RESPONSE, COMMON MEASUREMENT REPORT messages or the unit used in the event evaluation (i.e. same unit as for Fn) – a = ½^(k/2) , where k is the parameter received in the Measurement Filter Coefficient IE. If the Measurement Filter Coefficient IE is not present, a shall be set to 1 (no filtering) – In order to initialise the averaging filter, F0 is set to M1 when the first measurement result from the physical layer measurement is received”
For internal use 96 © Nokia Siemens Networks
Presentation / Author / Date
HSDPA Serving Cell Change – UL SIRerror Measurement • The SIRerror measurements are specified in the TS 25.433, 25.133 and 25.215 – 25.133: ▪ The measurement period is 80 ms ▪ NOTE: The measurement period is the same as for the SIR measurement, SIRerror is calculated from SIR and SIRtarget (SIRerror = SIR – SIRtarget_ave ) Parameter
Accuracy
SIRerror
3 dB
Parameter SIR
Range The accuracy requirement for SIRerror is valid for SIR within the guaranteed accuarcy range specified in section 9.2.2.
Unit
Accuracy [dB]
dB
3
Conditions Range For -7
View more...
Comments
