Академический Документы
Профессиональный Документы
Культура Документы
Radio Resource Management Overview Parameter Configuration Common Channels & Power Control Load Control Admission Control Packet Scheduling Handover Control Resource Manager
NOKIA
Course Objectives
At the end of the course you will be able to:
Name and describe the different Handover types Describe and list the steps of the Handover procedure for each Handover type Name and describe the main RAN parameters related to Handover reporting triggering Describe the main difference between inter system Handover and other Handover types Name and describe the main RAN parameters related to inter system Handover
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
Measurement triggering Measurements HO decisions Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
GSM ISHO
Handover Types
Intra-Frequency Handovers
Softer Handover
Handover between sectors of the same Node B (handled by BTS) No extra transmissions across Iub interface Maximum Ratio Combining (MRC) is occurring in both the UL and DL MS simultaneously connected to multiple cells (from different Node Bs) Extra transmission across Iub, more channel cards are needed (compared to non-SHO) Mobile Evaluated Handover (MEHO) DL/UE: MRC & UL/RNC: Frame selection combining Arises when inter-RNC SHO is not possible (Iur not supported or Iur congestion) Decision procedure is the same as SHO (MEHO and RNC controlled) Causes temporary disconnection of the (RT) user
Soft Handover
Hard Handover
Inter-Frequency Handover
Can be intra-BS, intra-RNC, inter-RNC Network Evaluated Handover (NEHO) Decision algorithm located in RNC
Inter-RAT Handover
Handovers between GSM and WCDMA (NEHO)
4 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
RNC
100
G:InterG:InterSystem System
100
I:InterI:InterFrequency Frequency
100
32
S:IntraS:IntraFrequency Frequency
FMCS
HOPS 100
RNC = Radio Network Controller level parameters WBTS = Node B level parameters WCELL = Cell level parameters FMCx = Frequency Measurement Control parameters (S=intra-frequency set; I=inter-frequency; G=inter-RAT) ADJx = Adjacent Cell parameters (S=intra-frequency set; I=inter-frequency; G=inter-RAT) HOPx = Handover Path parameters (S=intra- frequency set; I=inter-frequency; G=inter-RAT)
NOKIA
NrtHopsIdentifier = 5 RtHopsIdentifier = 10
HOPS (NRT) ADJS HOPS (RT) HOPS (NRT)
HOPSid = 5
WBTS
WCEL WCEL
ADJSid = 1
HOPSid = 10
NrtFmcsIdentifier = 3 RtFmcsIdentifier = 40
Each WCEL has associated 1 FMCS for NRT & 1 for RT, both can be reused for other cells. Different FMCSs could be defined for the different type of cells (urban, rural, macro/micro/pico)
7 NOKIA
WCEL
ADJSid = 2
FMCSid = 3
FMCS (NRT)
Each ADJS has associated 1 HOPS for NRT & 1 for RT, both can be reused for other cells. Different HOPSs parameters could be defined for the different type of cells (urban, rural, macro/micro/pico)
FMCSid = 40
FMCS (RT)
ADJSid = 3
HO Parameter Categories
Handover Control Parameters RNC parameters WCEL parameters HOPS parameters FMCS parameters ADJS parameters HOPI parameters FMCI parameters ADJI parameters HOPG parameters FMCG parameters ADJG parameters
ADJS parameters 1 Cell Identifier CPICH Ec/No Offset Disable Effect on Reporting Range Location Area Code Maximum UE TX Power on RACH Mobile Country Code Mobile Network Code Mobile Network Code Len Primary CPICH power NRT HOPS Identifier Primary Scrambling Code RNC Identifier Routing Area Code RT HOPS Identifier Tx Diversity Indicator
100
FMCS parameters Active Set Weighting Coefficient Addition Reporting Interval Addition Time Addition Window CPICH Ec/No Filter Coefficient CPICH Ec/No HHO Cancellation CPICH Ec/No HHO Cancellation Time CPICH Ec/No HHO Threshold CPICH Ec/No HHO Time Hysteresis CPICH RSCP HHO Cancellation CPICH RSCP HHO Cancellation Time CPICH RSCP HHO Filter Coefficient CPICH RSCP HHO Threshold CPICH RSCP HHO Time Hysteresis Drop Time Drop Window Maximum Active Set Size Replacement Reporting Interval Replacement Time Replacement Window
In GSM:
Define HO Trigger
HoThresholdsLevDL Rx (LDR): -92 dBm Px (LDP): 3 Nx (LDN): 4
NOKIA
Primary scrambling code for neighbor cell specified using AdjsScrCode AdjsTxDiv specifies whether the neighbor cell is using Tx diversity AdjsTxPwrRACH determines the maximum power the UE can use on the PRACH when accessing the neighbor cell
NOKIA
Each neighbor cell is defined using the UTRAN cell identifier which comprises; MCC (Mobile Country Code) MNC (Mobile Network Code) RNC Identifier Cell Identifier = AdjsMCC = AdjsMNC = AdjsRNCid = AdjsCI
ADJS Parameters
The LAC (AdjsLAC) & RAC (AdjsRAC) are also in ADJS parameter set
10 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
RNC
MaxActiveSetSize
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
Soft Handover
HC supports the following measurement reporting events:
Event 1A: A primary CPICH enters the reporting range (Ncell addition) Event 1B: A primary CPICH leaves the reporting range (Ncell deletion) Event 1C: A non-active CPICH becomes better than an active primary CPICH (Ncell
replacement)
Cell individual offsets for modifying measurement reporting behaviour Mechanism for forbidding a neighbor ing cell to affect the reporting range
Handover decision performed by RNC based on measurements and available resources Admission Control can reject the branch addition in case the maximum load is achieved in DL (threshold + offset), valid both for RT and NRT bitrates. Hard blocking may prevent branch addition
13 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
UE can perform averaging on EC/IO measurement prior to the event reporting process EcNoFilterCoefficient (FMCS) defines the measurement period for intra-frequency CPICH EC/IO measurements used by UE (default = 600ms). In the CELL_DCH state the UE physical layer measurement period for intra frequency CPICH Ec/No measurements is 200 ms. The Filter Coefficient parameter controls the higher layer filtering of physical layer CPICH Ec/No measurements before the event evaluation and measurement reporting is performed by the UE. RNC averages CPICH Ec/Io measurements using EcNoAveragingWindow (HOPS) - defines the number of event triggered periodic intra-frequency measurement reports used by RNC to calculate averaged CPICH EC/IO (default = 8 Measurements)
14
NOKIA
EcNoFilterCoefficient
Measurement accuracy depends on speed & Filter Coefficient
EcNoAveragingWindow
UTRAN
Node B RNC
Measurement Type: Intra-frequency measurements Reporting events: 1A: A primary CPICH enters the reporting range 1B: A primary CPICH leaves the reporting range 1C: A non-active CPICH becomes better than an active primary CPICH Event triggered / Periodical reporting Measurement quantity: CPICH Ec/No etc.
15 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
16
NOKIA
AdditionWindow
1 2
P CPICH 3 time 3
AdditionTime
Measurement Report no Add to the AS?
AdditionReportingInterval
17
NOKIA
RNC
Reporting Cell Status: All active cells + 2 monitored cells. Triggering Condition: Monitored Set cells Reporting Range Constant AdditionWindow / 4 dB Cells forbidden to affect Reporting range: AdjsDERR / Enable W: ActiveSetWeightingCoefficient / 0 Time to trigger: AdditionTime / 0 = 0 ms Reporting deactivation threshold: MaxActiveSetSize = 3 Amount of reporting: infinity Reporting interval: AdditionReportingInterval / O.5 s
18
NOKIA
19
NOKIA
20
NOKIA
DropWindow
3 time
DropTime
Measurement Report
21 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
Reporting cell Status: 3 active cells Triggering Condition: Active cells Reporting Range Constant: DropWindow / 4 dB Cells forbidden to affect Reporting range AdjsDERR / Enable W : ActiveSetWeightingCoefficient / 0 Time to trigger: DropTime / 320 ms
22
NOKIA
23
NOKIA
Addition window= 2 dB (factor of 2 mapping between the signalled value and the actual value, TS 25.331 defines this mapping) Addition time = 100 ms Reporting interval = 500 ms Drop window = 3 dB (factor of 2 mapping between the signalled value and the actual value) Drop time = 640 ms
RANPAR Version 2.0 / 09.02.2006 / rlim
24 NOKIA
realistic worst case values, SIB11 length = 3187.5 < 3552 -> OK!!
Some sites might need additional neighbors and might pose a problem with the SIB11 limitation Avoid setting AdjsQoffset2 values, different CPICH values or other parameters used to tune cell reselection or handover
Further information Technical Note No. 046 / Restriction on number of cells in SIB11/12 due to inconsistency problem in 3GPP TS 25.331
25 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
26
NOKIA
ReplacementWindow
P CPICH 3
weakest CPICH3 in AS
time 2
ReplacementTime
Measurement Report
ReplacementReportingInterval
no AS update?
27
NOKIA
RNC
Reporting cell Status: All active cells + 2 monitored cells. Hysteresis: ReplacementWindow / 2 dB Time to trigger: ReplacementTime / 0 = 0 ms Replacement activation threshold : MaxActiveSetSize / 3 Amount of reporting: infinity Reporting interval: ReplacementReportingInterval / 0.5s
28
NOKIA
29
NOKIA
Replacement window = 1 dB Replacement time = 100 ms Reporting interval = 500 ms Replacement window requires mapping to its true value according to: 4/(2*2) = 1 dB
There are two mappings first is the signalled value to actual value mapping and second is the way in which hysteresis is applied in the event triggering equation (TS25.331) Once in connected mode the networks sends the same set of information elements via a measurement control message Nokias implementation is that the values in the measurement control message are the same as those within SIB 11 Events 6F and 6G are configured in a similar fashion i.e. within SIB 11 and subsequently with a measurement control message
30 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
Individual Ncell Offset & Forbidding Neighbour Cell from Reporting Range
Individual Ncell Offset cell individual offsets for modifying measurement reporting behaviour effectively 'moves' cell border (shrinks or enlarges cell) offset set using AdjsEcNoOffset (= CPICH Ec/No Offset) (ADJS) offset applied to Primary CPICH measurements before event evaluation by the UE Forbidding Neighbour Cells from Reporting Range the primary CPICH of certain cells can be forbidden from reporting range calculation in some instances cells can be forbidden from reporting range using AdjsDERR (ADJS)
31
NOKIA
P CPICH 1
P CPICH 2
AdjsEcNoOffset
32
NOKIA
PCPICH3 is forbidden to affect the reporting range as its quality is quite unstable.
AdjsDERR
P CPICH 3
Time
33
NOKIA
SHO Summary
Event Reporting cell status Triggering Condition Reporting Range/ Time to Trigger Hysteresis Addition Window/4 dB Drop Window/ 6 dB Addition Time /0 ms Drop time /320 ms Replacement time/0 ms Active set cells + Event 1A Monitored set 2 monitored set (Add) cells cells Event 1B (Drop) Active set cells Active set cells Reporting Interval Addition Reporting Interval /0.5 s Replacement Reporting Interval/ 1s
Replacement Window/4 dB
3GPP reporting events 1A, 1B and 1C (also 6F and 6G) CPICH Ec/Io is used as a measurement quantity rather than CPICH RSCP CPICH Ec/Io measurements are more accurate 1A and 1B reporting range is defined by strongest active set cell 1C reporting range is defined by weakest active set cell
34 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
UE Internal Measurements
SHO for synchronisation reason: Event 6F: The UE Rx-Tx time difference for a Radio Link (RL) included in the active set becomes larger than an absolute threshold Reporting Reporting event 6G: The UE Rx-Tx time difference for a RL included in the active set becomes smaller than an absolute threshold Estimation of these events: Based on UE Rx-Tx time difference Measurement configuration: Time-to-trigger: not used. 6F: UE Rx-Tx time difference threshold: UpperRxTxTimeDiff default: 1174 chips, range:1152 ... 1280 chips, step 1 chip 6G: UE Rx-Tx time difference threshold: LowerRxTxTimeDiff default: 874 chips range: 768 ... 896 chips, step 1 chip
35
NOKIA
UE Internal Measurements
time
time UL DPCH
time
6F
I am in the CELL_DCH sub-state
DLnom
6G
T0 Measurement Control [ ]
UTRAN
Node B RNC
UE Measurement Type: UE Internal measurements Reporting events: 6F: The UE Rx-Tx time difference for a RL included in the active set becomes larger than an absolute threshold Reporting 6G: The UE Rx-Tx time difference for a RL included in the active set becomes smaller than an absolute threshold
36 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
When the UE receives a MEASUREMENT CONTROL message, the UE shall stop monitoring and measurement reporting and shall replace the measurement reporting criteria with the new information received in the MEASUREMENT CONTROL message.
37 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
BEST Server: Cell 22 BEST Server: Cell Neighbour ListCell2 Addition WindowCell2 Drop WindowCell2 Drop TimeCell2
1. Idle Mode
The Themeasurement measurementreporting reporting criteria are updated criteria are updatedas assoon soon as the original cell drops as the original cell dropsout out from the Active Set (Nokia from the Active Set (Nokia Implementation). Implementation). Connected Mode: Cell_DCH
Measur ement Measur ement Reporti ng Criteria Reporti ng Criteria accordi ng accordi ngto toCell Cell11
Cell 1
The TheUE UEshall shallsend sendthe the MEASUREMENT REPORT MEASUREMENT REPORT message messagewhen whenreporting reporting criteria are fulfilled. criteria are fulfilled.
Cell 2
Measur ement Measur ement Reporti ng Criteria Reporting Criteria accordi ng accordi ngto toCell Cell22
The TheUE UEshall shallcontinue continue monitoring the list monitoring the listof ofneighbor neighbor ing ingcells cellsassigned assignedin in System System Information during Idle Information during IdleMode Mode
38 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
BEST Server: Cell 22 BEST Server: Cell Addition WindowCell2 Drop WindowCell2 Drop TimeCell2
1A
1B
Cell 1
Neighbour NeighbourList ListCell Cell11 Neighbour NeighbourList ListCombination Combination
33 11 44 22 55
Cell 2
Neighbour NeighbourList ListCell Cell22
Meas ureme nt ting Meas ureme ntRepor Repor ting Criter ia ding Criter iaaccor accor dingto to Cell 1 Cell 1
39 NOKIA
Meas ureme nt ting Meas ureme ntRepor Repor ting Criter ia accor ding to Criteria according to Cell Cell11
Measur ement gg Measur ementReportin Reportin Criteria ggto Criteriaaccordin accordin toCell Cell22
Nokia Parameters for Intra-Frequency Measurements In Nokia RAN the measurement quantity for events 1A, B, C, E, F is P-CPICH Ec/No and for 1E,F
also P-CPICH RSCP
There are a huge number of intra-frequency measurement parameters. Please refer to the WCDMA Parameter Dictionary. See Measurement Control Parameter Set (FMCS object) which controls the intra-frequency measurements radio bearer, such as: 1A paramters: ActiveSetWeightingCoefficient, AdditionReportingInterval, AdditionWindow, AdditionTime, MaxActiveSetSize, etc. 1B parameters: ActiveSetWeightingCoefficient, DropTime, DropWindow, etc. 1C parameter: MaxActiveSetSize, ReplacementReportingInterval, ReplacementTime, ReplacementWindow, etc. 1E parameter: HHoEcNoCancel, HHoEcNoCancelTime, HHoRscpCancel, HHoRscpCancelTime, etc. 1F parameter: HHoEcNoCancel, HHoEcNoTimeHysteresis, HHoRscpCancel, HHoRscpThreshold, HHoRscpTimeHysteresis, etc.
40
NOKIA
Neighbour Lists
In the RRC idle state and in the RRC connected sub-states CELL_FACH, CELL_PCH and URA_PCH, the UE is responsible for cell selection and re-selection. It camps on one cell or it is served by one cell. By reading the System Information Block 11 and/or 12, the UE gets the Intra-frequency cell info list, Inter-frequency cell info list, and Inter-RAT cell info list, i.e. it gets several neighbourhood lists. In the CELL_DCH sub-state, the RNC must be able to continuously update the neighbour cell lists in order to reflect the changing neighbourhood of a moving mobile station. This is part of the RNCs handover control. If we have more than one active set cell, which participate in a soft handover, the handover control of the RNC is responsible to combine the lists into one neighbour cell list which is then transmitted to the mobile station. The neighbour cell list combination is carried out in the steps depicted in next slide. A soft handover only takes place with cells on the same UTRA carrier band. Consequently, the combining of neighbourhood lists of several active set cells is only required for intra-frequency handovers and has to combined with their measurements.
41
NOKIA
Cell 1
Cell 2
Cell 3
Cell 4
Cell 5
Cell 6
Cell 7
Cell 9
Cell 10
Cell 11
Cell 33 Cell Cell11 Cell11 Neighbour cells which are common to Cell 6 and Cell 7 Neighbour cells defined only for Cell 6 Cell 22 Cell Cell7 Cell7 Cell 44 Cell Cell 88 Cell
42
NOKIA
Step Step2 2
Common to 3 Neighbour Lists
Cell Cell11 11 Cell Cell15 15 Cell Cell48 48 Cell Cell44 Cell Cell41 41 Cell Cell66 .... ... ...
Cell Cell37 37 Cell Cell51 51 Cell Cell49 49 Cell Cell99 Cell Cell10 10 Cell Cell56 56 ... ...
Cell Cell11 11 Cell Cell50 50 Cell Cell99 Cell Cell13 13 Cell Cell10 10 Cell Cell22 22 ... ... Cell2 Cell2 Cell Cell77
Cell Cell99 Cell Cell11 11 Cell Cell15 15 Cell Cell10 10 Cell Cell37 37 Cell Cell41 41 Cell Cell49 49 .. .. Cell Cell22 22 Max 32 Cells
Cell Cell43 43
Cell Cell25 25
Cell Cell33 33
Step Step3 3
Step Step1 1
Neighbour Cells Lists Three Cells in the Active Set
43 NOKIA
Step Step4 4
Neighbour Cells defined for only 1 Neighbour list: best Ec/No first
Step 1: Active set cells First the handover control sets the active set cells into the neighbour cell list. Step 2: Neighbour cells which are common to three active set cells During the second step of neighbour cell list combination the handover control selects those neighbour cells which are common to all three active set cells. If the total number of relevant neighbour cells exceeds the maximum number of 32 after the second step, the handover control removes in random order those surplus cells from the combined neighbour cell list which are selected during the second step Step 3: Neighbour cells which are common to two active set cells During the third step of neighbour cell list combination the handover control selects those neighbour cells which are common to two active set cells. If the total number of relevant neighbour cells exceeds the maximum number of 32 after the third step, the handover control removes in random order those surplus cells from the combined neighbour cell list which are selected during the third step. Step 4: Neighbour cells which are defined for only one active set cell During the fourth step of neighbour cell list combination the handover control selects those neighbour cells which are defined for only one active set cell (random). If the total number of relevant neighbour cells exceeds the maximum number of 32 after the fourth step, the handover control removes those surplus neighbours from the combined neighbour cell list which are selected during the fourth step, starting from the neighbours of the weakest (CPICH Ec/Io) active set cell.
44 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
Neighbourhood List Combination for Intrafrequency HOs The neighbourhood lists for intra-frequency handover measurements can be composed like this:
Testing Details
45
NOKIA
DL sends MC to indicate new set of intrafrequency reporting criteria (e1a, e1b etc) ; as well as modify UE NB list; i.e. removing old NBs unique to SC374 & add new common NBs. Also, modify FreqCellID=12, SC382 with AdjsEcNoOffset=6dB. Individual Cell Offset works!!
46
NOKIA
AdjsEcNoOffset Verification
RRC connection setup on 16016 (374). SC374 is the Active Set (AS) Reference Cell.
47
NOKIA
AdjsEcNoOffset Verification
RRC connection setup on 16016 (374). Measurement Control sent indicating AS Reference Cell neighbour list. Note: intraFreqCellID = 12 SC382 has NO AdjsEcNoOffset defined.
48
NOKIA
AdjsEcNoOffset Verification
RRC connection setup on 16016 (374). Measurement Control sent indicating AS Reference Cell neighbour list. Note: intraFreqCellID = 12 SC382 has NO AdjsEcNoOffset defined. UE sends MR e1b to remove Reference Cell SC374 from AS. This is followed by UMI & UMIC to indicate that AS Reference Cell has changed (to SC36).
49
NOKIA
AdjsEcNoOffset Verification
RRC connection setup on 16016 (374). Measurement Control sent indicating AS Reference Cell neighbour list. Note: intraFreqCellID = 12 SC382 has NO AdjsEcNoOffset defined. UE sends MR e1b to remove Reference Cell SC374 from AS. This is followed by UMI & UMIC to indicate that AS Reference Cell has changed (to SC36). DL sends MC (based on SC36) to indicate new set of intra-frequency reporting criteria (e1a, e1b etc). As well as modify UE NB list; i.e. removing old NBs unique to SC374 & add new common NBs. Note: Also, modify intraFreqCellID=12, SC382 with AdjsEcNoOffset=6dB (mapping IE x 2 12). Individual Cell Offset
50
NOKIA
Conclusion
51
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
Hard Handover
If RNC is not able to add (Event 1A) to or replace (Event 1C) an Ncell from the AS, UE sends periodic measurement reports (AdditionReportingInterval / ReplacementReportingInterval) until;
Ncell is added/replaced in to AS Ncell leaves reporting range HO no longer required (e.g. different Ncell enters AS)
RNC may not be able to add/replace Ncell due to (a) Iur congestion or (b) inter-RNC SHO is prevented due to setting of EnableInterRNCsho (HOPS) (Point 1 in next slide) If CPICH EC/NO of non-active Ncell continues to increase it will cause additional interference due to a non-optimal connection (point 2)
54
NOKIA
HHO decision
To avoid excessive uplink interference, RNC will perform an intrafrequency hard Handover if either of the following criteria are met
AveEcNoDownlink + HHoMarginForAveEcNo(n) < AvEcNoNcell(n) EcNoDownlink + HHoMarginPeakEcNo(n) < EcNoNcell(n)
AveEcNoDownlink and AvEcNoNcell(n) = measured values for the best AS cell and the nth NS cell, averaged over EcNoAveragingWindow measurements EcNoDownlink and EcNoNcell(n) = instantaneous values HHoMarginForAveEcNo (HOPS) = average Ec/N0 margin [-6 6]dB, default 1dB HHOMarginPeakEcNo (HOPS) = peak Ec/N0 margin [-6 6]dB, default 2dB
55
NOKIA
Hard Handover
AveEcNoDownlink + HHOMarginAveEcNo < AveEcNoNcell EcNoDownlink + HHOMarginPeakEcNo < EcNONcell
Ec/Io
3 2 Reporting range
HHOMarginAverageEcNo HHOMarginPeakEcNo
P CPICH 1
P CPICH 2
P CPICH 3 1 1A (AdditionTime = 0)
Time
AdditionReportingInterval
56
NOKIA
CN
CN
Iu
Iu
RNC RNC
Iu
Iu
RNC
Intra-frequency hard Handover is lossless for NRT radio bearer but it causes short disconnection of RT radio bearer. Intra-frequency hard handover decisions made by the RNC are based on the intrafrequency measurement results, which are usually applied to the SHO procedure Also Enable Inter-RNC SHO parameter in intra-frequency HO path defines whether intra-frequency HO from the serving cell to a specified neighbour cells is performed as soft of hard 57 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim Mobile evaluated Handover (MEHO)
Iur
Iur
If RNC is not able to add (Event 1A) to or replace (Event 1C) an Ncell from the AS, UE sends periodic measurement reports (AdditionReportingInterval/ ReplacementReportingInterval) until; Ncell is added/replaced in to AS Ncell leaves reporting range HO no longer required (e.g. different Ncell enters AS) RNC may not be able to add/replace Ncell due to (a) Iur congestion or (b) inter-RNC SHO is prevented due to setting of EnableInterRNCsho (HOPS) (point1 on next slide) If CPICH EC/NO of non-active Ncell continues to increase it will cause additional interference due to a non-optimal connection (point 2) To avoid excessive uplink interference, RNC will perform an intra-frequency hard handover to the Ncell (CPICH3) if either of the following criteria are met (point 3); AveEcNoDownlink + HHOMarginAveEcNo < AveEcNoNcell EcNoDownlink + HHOMarginPeakEcNo < EcNONcell Parameters : Enable Inter-RNC Soft Handover HHO margin for Peak EcNo
58
( YES/NO, default = YES ) (-66 dB, default =2 dB) (-66 dB, default=1 dB)
HH Margin for Average EcNo NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
AveEcNoDownlink AveEcNoDownlink + + HHOMarginAveEcNo HHOMarginAveEcNo < < AveEcNoNcell AveEcNoNcell EcNoDownlink EcNoDownlink + + HHOMarginPeakEcNo HHOMarginPeakEcNo < < EcNONcell EcNONcell
Ec/Io
HHOMarginAverageEcNo HHOMarginPeakEcNo
P CPICH 1
P CPICH 3 1 1A (AdditionTime = 0)
Time
AdditionReportingInterval
59
NOKIA
RN27 RN27
UE UE Ec/No Ec/No
Handover Category: Iur Failure - Inter-RNC SRNC Relocation failure => Triggering Inter-RNC, Intra-Frequency HHO. Analysis: Iur failure was simulated / purposely disabled via blocking AAL2 User Plane, to invoke InterRNC, Intra-Frequency HHO.
Scanner Scanner
RNTI_000022E6_03EF.zip
60
NOKIA
RN27 RN27
UE UE Ec/No Ec/No
Handover Category: Iur Failure - Inter-RNC SRNC Relocation failure => Triggering Inter-RNC, Intra-Frequency HHO. Analysis: Iur failure was simulated / purposely disabled via blocking AAL2 User Plane, to invoke InterRNC, Intra-Frequency HHO.
Scanner Scanner
61
NOKIA
ReleaseMarginForAveEcNo (HOPS) = average Eb/N0 margin [-6 6] dB, default 2.5dB ReleaseMarginPeakEcNo (HOPS) = peak Eb/N0 margin [-6 6] dB, default 3.5dB
62
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
Traffic Balancing
Traffic balancing with Call setup control or during hard HO to another frequency Directed RRC connection setup => direct the user to the frequency with lower loading within the same sector A second frequency can be added for each sector/site independently as the capacity needs to be increased
High capacity site f1 f1 f2 f2 f2 f2 Start call on f2
64 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
High Highcapacity capacityWCDMA WCDMAsites sites can canbe beutilized utilizedwith withRAN1.5 RAN1.5 f1 f1 f1 f1
f1 f1
Directed RRC connection setup is used for balancing the load (UL/DL)
Same sector has cells with equal primary CPICH power, PtxTarget, PtxOffset, PrxTarget and PrxOffset values Parameter Sector Identifier tells to which sector cell belongs to
If either the UL or DL load of the Source cell exceed a certain threshold value, the DRRC Connection setup process is initiated.
CurrentCellPrxTotal > PrxTarget (default 4 dB)+ DRRCprxOffset (default -1 dB) CurrentCellPtxTotal > PtxTarget (def. max-3 dB)+ DRRCptxOffset (default -3 dB) The load of the current cell (UL/DL) is compared with the load of other cells in same sector to find out cell having less load: CurrentCellPrxTotal > CellPrxTotal(n) - DRRCprxMargin(default -0.5 dB) CurrentCellPtxTotal > CellPtxTotal(n) - DRRCptxMargin(default -2 dB) Decision of Directed RRC connection setup is done by Admission Control in RNC
1+ 1+ 1
f1
Cell 4
Cell 1
Sector 1
f1 f2
2+ 2+ 2
Cell 2 Cell 5
Cell 6
Cell 3
Sector 3 Sector 2
Sector 2
RACH: RRC Connection Setup Request Cell_1 load > Cell_2 load + load threshold -> DRRC activated FACH: RRC Connection Setup incl. UARFCN of target cell DCCH: RRC Connection Setup Complete
67
NOKIA
DRRC connection setup to the target cell if both of the following equations are fulfilled: CurrentCellPrxTotal (source cell) > CellPrxTotal(n) DRRCprxMargin (default 0dB) CurrentCellPtxTotal (source cell) > CellPtxTotal(n) DRRCptxMargin (default 0.5dB).
68 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
These These parameters parameters MUST MUST BE BE the the same same for cells defined as same Sector, for cells defined as same Sector, in in order for DRRC functionality to work. order for DRRC functionality to work.
FMCI (RT/NRT)
FMCG (RT/NRT)
Minimum Required quality level Minimum Required RX level Sintrasearch Sintersearch SsearchRAT
69
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
UL CM (needed to avoid interference) During WCDMA transmission signal leakage will go to GSM Rx also
71
NOKIA
Normal frame
The reception/transmission gap is always seven slots in RN2.0. Gaps can be created using single or double frame approach (Nokia supports both) Because same data amount is sent in a shorter time more power is needed during CM (both in UE and BTS) => affects WCDMA coverage Fast Power control information might be lost during the gap => higher Eb/No => affects WCDMA capacity Compressed frames may be lost if power control is not set correctly => affects WCDMA quality CM methods are Spreading Factor Halving and Higher Layer Scheduling (both supported in RN2.0)
72 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
Measurement Gap
Length of gap: 3, 4, 5, 7 timeslots The The reception/transmission reception/transmission gap gap is is always always 7 7 time time slots slots in in RN2.0 RN2.0..
Single-frame method
TGL
radio frame
Double-frame method
radio frame
Measurement Gap
74
NOKIA
Doubles temporarily the physical channel data rate, possible for all services Needs 3 dB more UE power due to halved spreading ratio If new channelization code is available from code tree in DL WCEL: AltScramblingCodeCM/0=used (def), 1=not used
Only possible for PS services (RT or NRT) Does not cause extra load to the cell but reduces DCH user data HLS data rate or HLS data rate possible
Double frame is used in case of HLS data rate Single frame is used in case of spreading factor halving and HLS data rate.
75
NOKIA
76
NOKIA
New UEs can be switched to CM when: Pxx_Total < Pxx_Target & # of UEs in CM < MaxNumbUECMcoverHO
Load
77 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
Compressed Mode
SF/2 SF/2used usedfor forboth bothUL ULand andDL DL Transmission TransmissionGap GapPattern: Pattern: Single Singleframe: frame:7 7slot slotgap, gap, variable variable# #of ofnormal normalframes frames Higher Higherlayer layerscheduling schedulingis isused used for both UL and DL for both UL and DL Transmission TransmissionGap GapPattern: Pattern: Selection Selectionbetween betweenHLS HLS and and HLS HLS Single Singleframe: frame:7 7slot slotgap, gap, # #of ofnormal normalframes frames
78 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
mode trigger parameters have to be set so that there is room for power increase due to code splitting otherwise power increase is cut and quality of connection gets worse during the compressed frames Usage of alternative scrambling code is possible if RNP parameter AltScramblingCodeCM enables
Double Doubleframe: frame:7 7slot slotgap, gap, # #of ofnormal normalframes frames
Compressed Mode
SF/2 SF/2used usedfor forboth bothUL ULand andDL DL Transmission TransmissionGap GapPattern: Pattern: Single Singleframe: frame:7 7slot slotgap, gap, variable variable# #of ofnormal normalframes frames
also
AMR AMR++PS PSdata, data, AMR + CS data, AMR + CS data, PS PSdata data++CS CSdata data
same power and alternative scrambling code aspects as in pure AMR or CS data service cases
Note that same method according to service is used for all Handover triggers Both uplink and downlink gap patterns can be used despite of whether other direction is compressed or not If both directions (UL and DL) are compressed, gap pattern is chosen so that both directions support it E.g. downlink support single frame but uplink double frame, it means that double frame shall be used The number of normal frames between gapped frames is defined with parameters This solution leaves the following problem in certain multi service call Currently UEs of certain vendor do not support in downlink DPCCH and DPDCH slot format #15B (compressed mode code splitting when SF=4) This means that 320 kbps PS data + AMR does not work for these terminals This problem can be partly avoided by denying compressed mode with that high data rate
79
NOKIA
Compressed mode
The normal compressed mode strategy includes fewer combinations of compressed mode configurations The non-configurable RNC parameter CompressedModeStrategy is used to select between the two strategies This parameter is configured to apply the normal strategy The normal strategy has been selected to minimise system complexity while the quantity of field experience is relatively low
CM Method
80 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
RT Data SF/2
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
About 25 HO parameters 5 Coverage/Capacity HO Reasons (31 Intra-Freq neighbor s) 48 Inter-Freq neighbor s 32 Inter-System neighbor s can be measured
Max 32 neighbor s could be measured Reporting cells are active set cells (max 3) + max 6 IFHO, max 6 ISHO neighb. Different decision methods for IF HO Only one decision method for IS HO
WCDMA
IF -measurements
IF-HO Decision
IS measurements
IS-HO Decision
WCDMA
RSSI meas.
BSIC verification
BSIC verification required in case neighbor list includes multiple GSM neighbor s using the same RF carrier
83 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
HO trigger
4. DL DPCH approaches its maximum allowed power FMCI: IFHOcauseTxPwrDL FMCG: GSMcauseTxPwrDL 6 . Others (Not implemented in RAN 1.5): e.g. Traffic & load reason IS-HO, etc
Frequency Measuring Control for Inter-Frequency = FMCI Frequency Measuring Control for Inter-System (GSM) = FMCG
85 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
absolute threshold
1E: HHoEcNoCancelTime
86
NOKIA
87
NOKIA
88
NOKIA
89
NOKIA
6A: The UE Tx power exceeds an absolute threshold 6B: The UE Tx power falls below an absolute threshold 6D: The UE Tx power reaches its maximum value 6D
min(UEtxPowerMaxDPCH, P_MAX)
6A 6B
InterfreqUETxPwrTimeHyst GSMUETxPwrTimeHyst
91 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
time to trigger
time
CPICH Pwr = Tx power of the CPICH of an active cell. PtxPrimaryCPICH (serving RNC) or AdjsCPICHTxPwr (drifting RNC)/33 dBm, range -1050 dBm, step 0.1 dBm MAX_DL_DPCH_TXPWR = maximum transmission power level of the DPDCH symbols a base station can use on the DPCH, expressed as a relative value to the CPICH pw FMCI: InterfreqDLTxPwrThrAMR/CS/RtPS/NrtPS -1/-3/-3/-1 dB (range -10 dB..0, step 0.5 dB) FMCG: GSMDLTxPwrThrAMR/CS/RtPS/NrtPS -1/-3/-3/-1 dB (range -10 dB..0, step 0.5 dB)
In Addition, the DL data rate allocated to the user must not exceed WCEL: HHoMaxAllowedBitrateDL
NOTE: Either WCDMA or GSM will be measured, not both systems
RANPAR Version 2.0 / 09.02.2006 / rlim
94
NOKIA
Iub
UE
PO2 Data 1 bits
Node B
TPC TFCI PO1 Data 2 bits
Pilot bits not used
RNC
time
Enable reports from Outer-loop Power Control Controller to trigger IF/IS HO, RNC: EnableULQualDetRep/default 0=no, 1=yes Time duration for which BER/BLER target has not been reached, despite SIR target at maximum level, RNC: ULQualDetRepThreshold/0.5 s, 0.5..5, step 0.5s Periodic report, every RNC: ULQualDetRepThreshold seconds, while BLER/BLER target is not reached
In addition, the UL data rate allocated to the user must not exceed WCEL: HHoMaxAllowedBitrateUL (default value: 32 kbits/s)
See See Module Module 3 3 Channels Channels & & PowerControl PowerControl
96 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
RNC
RNC
Target SIR Max SIR target SIR SIR
1st Quality deterioration report from PC to HC inside RNC 2nd Quality deterioration report (while the condition is satisfied the message is periodically repeated) Actual SIR target Min SIR target
default 0.5s
time
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
IF HO Parameters
HHoRscpThreshold HHoRscpCancel
L3 filter: Time to trigger: CPICH RSCP (Event 1F) Thresholds: DL DPCH power Threshold: Data rate threshold
InterFreqDLTxPwrThrXX HHOMAxAllowedBitrateDL
HHoEcNoThreshold HHoEcNoCancel
L3 filter: Time to trigger:
InterFreqUETxPwrThrXX
L3 filter:
ULQualDetRepThreshold
Data rate threshold
Timer:
UL Quality
InterFreqUETxPwrFilterCoeff * InterFreqUETxPwrTimeHyst *
Data rate threshold
HHOMAxAllowedBitrateUL
HHOMAxAllowedBitrateUL *
Handover Triggering
Decision Algorithm
AdjiPlossMargin AdjiMinEcNo AdjiMinRSCP AdjiTxPwrDPCH AdjiEcNoMargin
Handover Execution
IFHO measurements
After HO triggering message is sent to RNC, a RRC message Measurement Control is sent to UE containing details of the measurement that the UE must execute. Measurement reporting is periodical. Max 6 IF cells can be reported. No filtering in measurements by UE. 3 neighbor info send to UE:
RRC: Measurement control message ("carrier 2" measurements) UE
RNC
UTRA RF channel, cell individual offset (Ec/No) and primary scrambling code
Upon reception of the measurements reported by the UE, RNC applies a sliding averaging window to the CPICH Ec/No & CPICH RSCP measurements. The averaged levels are used as input to the inter-frequency decision algorithm. From each cell in active set (max=3) also intra-frequency measurements are done at same time
UE
RNC
AdjiMeasRepInterval
(default 0.5s)
In one measurement report there is both intra-and inter-frequency results, no measurement filtering is used in UE
CPICH Ec/No and CPICH RSCP measurements are reported through Measurement report messages
100
NOKIA
ISHO parameters
CPICH RSCP (Event 1F) Thresholds: HHoRscpThreshold HHoRscpCancel L3 filter: HHoRscpFilterCoefficient Timers: HHoRscpTimeHysteresis HHoRscpCancelTime UE Tx Power (Event 6A) Threshold: GsmUETxPwrThrXX L3 filter: GsmUETxPwrFilterCoeff Hysteresis margin: GsmUETxPwrTimeHyst Data rate threshold HHOMAxAllowedBitrateUL DL DPCH power Threshold: GsmDLTxPwrThrXX Data rate threshold HHOMAxAllowedBitrateDL CPICH Ec/Io (Event 1F) Thresholds: HHoEcNoThreshold HHoEcNoCancel L3 filter: Done already for SHO Timers: HHoEcNoTimeHysteresis HHoEcNoCancelTime UL Quality Timer: ULQualDetRepThreshold Data rate threshold HHOMAxAllowedBitrateUL
Handover Triggering
(XX=AMR,CS,NrtPS,RtPS)
Decision Algorithm
AdjgTxPwrMaxTCH AdjgRxLevMinHO (n) GsmMeasAveWindow
Handover Execution
ISHO measurements
After HO triggering message is sent to RNC, a RRC message Measurement Control is sent to UE containing details of the measurement that the UE must execute. Measurement reporting is periodical. Max 6 GSM cells could be measured by UE and reported to RNC. No filtering in measurements by UE
RRC: Measurement control message (GSM RSSI measurements) UE
RNC
Upon reception of the measurements reported by the UE, RNC applies a sliding averaging window to the RXLEV measurements. The averaged levels are used as input to the IS-HO decision algorithm.
RNC
The first measurement report has info from the best GSM cell: BCCH freq & RSSI, no filtering used in UE
RXLEV measurements are reported through Measurement report messages
UE
104
NOKIA
ISHO Signalling
UE
RNC
ISHO triggered: Event 6A/1F/
RRC: Measurement control with IE TGMP=GSM RSSI RRC: Measurement report RRC: Measurement control with IE TGMP=GSM BSIC
105
NOKIA
107
NOKIA
WCDMA
RRC: Measurement control message (BSIC decoding)
RSSI meas.
TRSSI depends on
Numbers
BSIC verification
TBSIC depends on :
Transmission
RNC
of GSM cells in the neighbor cell list Reporting interval Sliding averaging window Transmission gap pattern for RSSI measurements
108
NOKIA
The first measurement report has info from the best GSM cell: BCCH freq & RSSI, no filtering used in UE
GSMMaxMeasPeriod
Max 6 GSM cells reported
Inter-system measurement stops if RNC has not been able to perform intersystem handover after GSMMaxMeasPeriod (value 10, default =20, 120, step 1 meas report) RNC could not initiate inter-system measurements if: The UE has recently performed an inter-system HO: GSMMinHoInterval / 10s, 060, step 1s An inter-system HO recently fails for this UE: GSMMinMeasInterval / 10s, 060, step 1s
109
NOKIA
2. GSM Measurement reporting process GsmMeasRepInterval (default value=0.5 seconds) The GSM measurement reporting interval given by this parameter should be kept to 0.5 seconds (default value) Increasing the reporting interval would increase the IS-HO process delay Besides, accuracy requirements related to the GSM measurements in compressed mode are given for a reporting interval of 0.5 seconds (480ms TS 25.133) GsmMaxMeasPeriod ( default value = 20 measurement reports) This parameter controls the maximum compressed mode duration time for each GSM RSSI and BSIC decoding measurement process. The duration of this parameters in seconds is given by:
max_meas_time (s) = GsmMaxMeasPeriod x GsmMeasRepInterval + 4 x GsmMeasRepInterval
it was found (based on field measurements) that BSIC and RSSI delays are below 3 seconds, it makes senses to reduce the value of this parameter to some value about 3 seconds, otherwise, if the BSIC or RSSI measurements fail or if the IS-HO execution is not possible to due low GSM RSSI levels, the network will not deactivate compressed mode until the timer of 12 seconds has expired Thus, decreasing the parameter value will allow the UE/network to initiate a new IS-HO attempt
110
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
It is not sufficient to have triggers, which detect that a Handover has to be done. Criteria are required to decide, whether to carry out an intra-frequency, inter-frequency, or inter-RAT Handover if there is the possibility for a Handover at all! Conditions shown here have to be satisfied, before an inter-frequency Handover can be conducted. The best neighbor ing cell must fulfil following criteria (best according to Ec/No): Quality Criterion in case trigger was DL DPCH Power or CPICH Ec/No: AVE_RSCP_NCELL (n) > AdjiMinRSCP(n) + max(0, AdjiTxPwrDPCH(n) - P_MAX) Signal level from new cell > required Signal level in new cell + adjustment due to allowed power AVE_EcNo_NCELL (n) > AVE_CPICH_EcNo + AdjiEcNoMargin(n) EcNo on new cell better than EcNo in old cell + margin Pathloss Criterion in case trigger was UE Tx Power, CPICH RSCP or UL DPCH Quality: AVE_EcNo_NCELL (n) > AdjiMinEcNo(n) EcNo on new cell better than required EcNo in new cell (default 14 dB) CPICH_POWER - AVE_CPICH_RSCP > CPICH_POWER_NCELL (n) - AVE_RSCP_NCELL (n) + AdjiPlossMargin(n) PathLoss in old cell > PathLoss in new cell + Margin (default 2 dB) (continued)
112 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
IFHO Decision
IF HO Signalling
There is bad quality conditions in the link .. ISHO triggered: Event 6A\1F.
UE RRC: MEASUREMENT REPORT (Event 6A\1F..) RRC: MEASUREMENT CONTROL (IF meas details) RRC: MEASUREMENT CONTROL (CFN, TGPS)
RNC
. .
gotten, the RNC assess the best cell, and decides to attempt a IFHO to it
113
NOKIA
AVE_EcNo_NCELL (n)
b)
AdjiEcNoMargin(n) AdjiMinRSCP(n)
a) b)
114
AVE_RSCP_NCELL (n) > AdjiMinRSCP(n) + max(0, AdjiTxPwrDPCH(n) P_MAX) AVE_EcNo_NCELL (n) > AVE_CPICH_EcNo + AdjiEcNoMargin(n)
NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
b)
best inter-frequency cell best active set cell
AdjiMinEcNo(n)
AdjiPlossMargin(n)
a) b)
115
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
ISHO Decision
AVE_RXLEV_NCell(n) > AdjgRxLevMinHO(n) + max(0, AdjgTxPwrMaxTCH(n) - P_max)
GSM cell
AdjgRxLevMinHO(n)
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
80%
Packet PacketData Datato toWCDMA WCDMA regardless of GSM regardless of GSMload load
Higher Higherbit bitrates rates for data users for data users
Packet PacketBCCH BCCHparameters parameterscan canbe beused used to push GPRS mobiles to WCDMA to push GPRS mobiles to WCDMA 0%
119 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
WCDMA WCDMAcan canbe beused used to torelieve relieveGSM GSMoverload overload GSM GSMcan canbe beused usedto toextend extend WCDMA WCDMAcoverage coveragearea area
GSM GSM
GSM GSM
Mobile moving
121
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
PSAP
2. 8. Location Lo Source ca Establishment Request t ion UMTS RAN Re qu 3G MSC es t 7. Location 3. Handover to GSM
1. Emergency Call
9. Location
5.
Po sit
GMLC
ion ing
st
2G MSC
123
NOKIA
EMISHO Call-Flow
SMLC
Report Area IE: Geographical Area Client Type IE: Emergency Call
Location Calculation based on CId and RTT In case ISHO to GSM fails, RNC keeps location based on CI+RTT in mind and sends RANAP:Location Report
Case a) ISHO to GSM is successful, no response to MSS Case b) ISHO to GSM is not successful: RANAP: Location Report
124
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
Feature can be used to push 3G AMR calls to 2G Extreme parameter setting for ISHO trigger cause UE Tx power (event 6A)
FMCG: GSMcauseTxPwrUL FMCG: GsmUETxPwrThrAMR UE immediately answers with Measurement Report
push means Handover, not Directed-Retry !
126 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
UE
[..]
RNC
RRC: RadioBearerSetup RRC: RadioBearerSetupComplete RRC: MeasurementControl RRC: MeasurementReport (event 6A)
Range and step: 0 (False), 1 (True) Indicates whether a handover to GSM caused by high UE TX power level is enabled. The handover is enabled when the value of the parameter is "Used To enable feature, setting must be 1 (True) Range and step: -60..0 dB This parameter determines the UE TX power threshold for a CS voice connection. If the handover to GSM caused by high UE TX power level is enabled, the RNC starts inter-RAT (GSM) measurements when the UE TX power reaches this threshold. The UE TX power threshold is relative to the maximum TX power level an UE can use on the DPCH in the cell (or the maximum RF output power capability of the UE, whichever is lower To enable feature, setting must be 60 dB
RANPAR Version 2.0 / 09.02.2006 / rlim
GsmUETxPwrThrAMR
127
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
at least every 5 s
check
Measurement Updates: RLC_C value of the serving cell + least 6 strongest non serving GSM cells
Fdd_Qoffset: select allways (value is infinity)
If, for suitable UMTS cell & for a period of 5 s: CPICH RSCP > RLA_C + FDD_Qoffset and CPICH Ec/No FDD_Qmin
129
NOKIA
130
NOKIA
capable UEs to measure 3G neighbour cells when a running average of the received downlink signal level (RLA_C) of the serving cell is below (0-7) or above (8-15) the threshold Value 0 1 6 7 8 9 10 14 15 dBm -98 -94 -74 Always -78 -74 -70
UE always measures 3G cells
-54
Never
add this offset to the RLA_C of the GSM cells. After that the UE compares the measured RSCP values of 3G cells with signal levels of the GSM cells Value dBm 0 -always 1 -28 2 -24 3 -20 8 0 14 24 15 28
Always select irrespective of RSCP value RANPAR Version 2.0 / 09.02.2006 / rlim 131 NOKIA
FDD_REP_QUANT defines the reporting quantity for UTRAN cell (1=Ec/No or 0=RSCP, default 1). This parameter is hidden and it can not be tuned 3G_Search_PRIO parameter allows to extend the BSIC reporting interval from 10 s to 13s by checking the BSICs from non-serving BCCH carriers and also make WCDMA measurements as often as possible. Range is 0=no, 1=yes, default value .This parameter is hidden and it can not be tuned
FDD_(GPRS) FDD_(GPRS) FDD_REP_ FDD_REP_ Parameter Qsearch_I Qsearch_P Qsearch_P FDD_QMin Parameter Qsearch_I Qsearch_P Qsearch_P FDD_QMin Qoffset QUANT Qoffset QUANT Name for Name for 2quater 2quater 2ter 2quater 2ter 2quater 2quater 3quater 3quater 2ter 2quater 2ter Sys Info (SI) Sys Info (SI)
132 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
RLA_C
RSCP Ec/N0
133
NOKIA
134
NOKIA
Serving cell parameters Sintrasearch, Sintersearch and SsearchRAT are compared with Squal (CPICH Ec/No - Qqualmin) in S-criteria for cell re-selection UE will measure neighbor cells depending on how parameters are set & send (if parameters are not sent UE shall measure all cells)
1 - None (Squal > Sintrasearch ) 2 - WCDMA intra-frequency (Sintersearch < Squal Sintrasearch) 3 - WCDMA intra- and inter- frequency, no inter-RAT cells (SsearchRAT < Squal Sintersearch) 4 - WCDMA intra- and inter-frequency and inter-RAT cells (Squal SsearchRAT )
1 WCDMA CELL
135
NOKIA
UE starts GSM measurements if CPICH Ec/No < qQualMin + sSearchRAT First ranking of all the cells based on CPICH RSCP (WCDMA) and RSSI (GSM) Rs = CPICH RSCP + Qhyst1 Rn= Rxlev(n) - Qoffset1 Serving WCDMA cell calculation, with hysteresis parameter Neighbour WCDMA or GSM cell calculation with offset parameter
Yes
SintraSearch
Second ranking only for WCDMA cells based on CPICH Ec/No Rs = CPICH Ec/No + Qhyst2 Rn=CPICH_Ec/No(n)-Qoffset2
136 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
CPICH Ec/No > AdjsQqualmin and CPICH RSCP > AdjsQrexlevmin CPICH Ec/No > AdjiQqualmin and CPICH RSCP > AdjiQrexlevmin Rxlev > Qrxlevmin
Ranking is done using Criteria R, and the UE reselects to the cell with highest R-criteria. R-criteria is defined as:
For serving cell: Rs = Qmeas,s + Qhysts For neighboring cell Rn = Qmeas,n Qoffsetts,n
Qmeas is CPICH Ec/No for WCDMA cell and RxLev for GSM cell
137
NOKIA
138
NOKIA
QqualMin=-18 dB
Camping on 3G
Camping on GSM
Camping on 3G t
139
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
Inter-RNC Mobility
Most of the times the UE hands over among WBTS belonging to the same RNC (IntraRNC Handovers) However, what happens when the target WBTS is under a different WBTS?? 3GPP gives two different options to handle inter-RNC mobility in WCDMA
Anchoring: the UE will be connected to the CN via the old RNC. It is required Iur connection between the RNCs involved SRNS relocation: the UE will be connected to the CN via the new RNC. It is the Nokia implemented method
SRNS relocation *)
CN CN
Anchoring
CN CN
Iu
RNC
Iu Iur
RNC
Iu
RNC
Iu Iur
RNC
Iu
RNC
Iu Iur
RNC
Iu
RNC
Iu Iur
RNC
SRNS Relocation
SRNS Relocation
SRNS Relocation SRNS Relocation SRNS Relocation
RNC
RNC
SRNS Anchoring
SRNC anchored
RNC
RNC
142
NOKIA
SRNC Relocation
The SRNC relocation is used for moving the SRNC functionality from one RNC to another RNC, that is, closer to where the UE has moved during the communication. Both the radio access network and the core network are involved There are the following types of relocations Relocation for circuit-switched services Relocation for NRT PS services Relocation for NRT services started by the Cell/Ura Update message from target RNC(CELL_FACH state relocation) Relocation for RT PS services An inter-RNC Hard Handover can be associated to the SRNS relocation, if so the relocation is UE involved, since the UE is ordered to switch to another carrier or to replace the whole active by sending s HHO command to the UE during the relocation procedure. An inter-RNC Hard Handover can be due to: Inter frequency HHO is needed, and the target cell is located in the DRNS No resources (mainly Iur capacity) available between the involved RNCs (so no inter-RNC SHO possible) No Iur interface configured between the neighbour RNCs
143
NOKIA
NrncRelocationSupport =1
Source RNC
Start RelocPrep
Start RelocOverall
RANAP:Relocation Request Ack
Stop RelocPrep
RANAP:Relocation Command
Start RelocOverall
RNSAP:Relocation Commit SRNC operation started RANAP:Relocation Detect UP switching RRC:UTRAN Mobility Information RRC:UTRAN Mobility Information Confirm
Stop RelocOverall
RANAP:Iu Release
RANAP:Relocation complete
Stop RelocOverall
RANAP:Iu Release Complete
SRNC Relocation is initiated in the Serving RNC when all the cells of the active set belong to a different RNC. The SRNC sends a Relocation Required The CN evaluates if the relocation is possible and in that case, it sends a Relocation Request to the target RNC with parameters for the bearer establishment Relocation Command sent from CN to Source RNC with UTRAN information and bearer parameters After that, the Source RNC sends Relocation Commit message over Iur to the Target RNC When target RNC starts to act as Serving RNC, it sends a Relocation Detect message to CN. This message has no parameters At the same time UTRAN Mobility Information is sent to the UE, to inform that the relocation is performed and should use the new RLs After the confirm, the target RNC informs CN with Relocation Complete message that the relocation procedure was successful and Iu is released from source RNC
144
NOKIA
NrncRelocationSupport =1
Source RNC
Start RelocPrep
Start RelocOverall
RANAP:Relocation Request Ack
Because there is no Iur interface, combined SRNS relocation and HHO are done before the UE is completely under the target RNC The procedure is quite similar to the not UE involved case until Relocation Command The only difference in the Relocation Required message, the Relocation Type IE is set to "UE involved in relocation of SRNS" Instead of Relocation Commit via Iur, the serving RNC sends a Physical CH Reconfiguration, after which the UE stops transmitting and receiving on the old radio links and starts on the new radio link
Stop RelocPrep
RANAP:Relocation Command
Start RelocOverall
Physical Channel Reconfiguration L1 sync. Established between BTS and UE RANAP:Relocation Detect UP switching
RANAP:Relocation complete
Stop RelocOverall
RANAP:Iu Release
Stop RelocOverall
RANAP:Iu Release Complete
145
NOKIA
UE reconfiguration
SRNS r
lo : Re P A d RAN olve v n i UE
d uire q e on R cati
eloca tion
UE moving
RRC: TRANSPORT CHANNEL RECONFIGURATION RRC: TRANSPORT CHANNEL RECONFIGURATION COMPLETE or: RRC: PHYSICAL CHANNEL RECONFIGURATION RRC: PHYSICAL CHANNEL RECONFIGURATION COMPLETE
Change during HO: User Plane, Bitrate Spreading factor Rate matching
146
NOKIA
Parameters
IuPSrelWait3G2GMultiServ : range = 0 (10s), 1 (20s), 2 (30s), 3 (60s), 4 (120s), 5 (180s), 6 (300s), 7 (600s), default value= 4 This RNC object parameter, controls the release of the Iu-PS connection after the 3G/2G inter-system handover with CS+PS multi-service. When the UE does not immediately after switching to the 2G-service initiate a routing area update procedure towards the PS-CN, the RNC can keep the Iu-PS connection and wait for the RAU and the release of the CS-service in the 2G-side When the timer expires, the RNC sends the Iu release request to the SGSN RelocationSupport : range = 0 (Not supported), 1 (Supported), default value = 1 RNC object parameter, identifies whether the Core Network supports the relocation of SRNC or not NrncRelocationSupport : range = 0 (Not supported), 1 (Supported), default = 1 RNC object parameter, identifies whether a neighbouring RNC supports relocation of SRNC or not
148
NOKIA
Handover Control
Parameters Mapping SHO Events and Measurements Hard Handover & RRC Connection Release
GSM ISHO
Measurement triggering Inter-Frequency & Inter-System Measurements Inter-Frequency HO decision Inter-System HO decision Load Based Handover to WCDMA Emergency Inter-System Handover to GSM Forced AMR voice call handover to GSM Cell Reselection
There are four kind of IMSI based Handover: IMSI based Intra-frequency HO IMSI based Inter-frequency HO IMSI based Inter-system HO Immediate IMSI based inter-frequency/intra-frequency HO
150 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
IMSI Based HO
There is two new Management object class related to IMSI based HO
WANE-WCDMA authorised networks Authorized network identifier (AuthorisedNetworkId) List of authorized networks (AuthorisedNetworkList) Authorised network PLMN (AuthorisedNetworkPLMN) Technology used in the authorised network (Technology) WANE name (WANEName) WSG-WCDMA Subscriber group Subscriber home PLMN (HomePLMN) Name of subscriber home PLMN (OperatorName) Subscriber Group identifier (SubscriberGroupID) Identifier of the authorised network (WSGAuthorisedNetworkId) GSM roaming allowed (GSM roaming) WANE set contains PLMN ids where the UE is allowed to make Handovers WSG object maps the subscriber (PLMN id) to certain WANE set with a WANE id. A WSG object should be created for every subscriber (PLMN id) visiting the network. Max Number of WANEs is 10 and max number of WSGs is 128
WSG id 0 1 7 8 127
PLMN id
24305 (Op F 3G, border country) 24201 (Op B Shared 3G) 24207 (Op A 3G) 24208 (Op B 3G)
List id 1 4 2 3
coded the PLMN that belongs to. The WSG associates one list number (WANE ID) to each PLMN
MCC MNC
152
NOKIA
List # #1 #2 #3 #4 #0
24210 (Op D 3G) 24206 (Op A GSM 24209 (Op B GSM) 24208 (Op B 3G) All
'All' in the list #0 indicates that all PLMNs are considered authorised PLMNs (RNC shall combine the neighbour cell list for the inter-frequency or inter-RAT (GSM) measurement from all neighbouring cells regardless of their PLMN identifiers)
153 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
154
NOKIA
155
NOKIA
f1
f1
f1
Op A Country X
Op B Border Country
Example 2
The IMSI Intra Frequency HO is between different PLMNs -> Intra Frequency Hard Handover (there is no Iur between those RNCs)
f1 f1 f1
156
NOKIA
DL DPCH approaches its maximum allowed power Quality deterioration report from UL outer loop PC Low measured absolute CPICH Ec/No UE Tx power approaches its maximum allowed power Low measured absolute CPICH RSCP
157
NOKIA
IMSI IF HO Signalling
There is bad quality conditions in the link ..
ISHO triggered UE RRC: MEASUREMENT REPORT (Trigger Event ) RRC: MEASUREMENT CONTROL (IF meas details) RRC: MEASUREMENT CONTROL (CFN, TGPS)
RNC
RNC commands measurements of the authorized IF cells
. .
158
NOKIA
159
NOKIA
RNC 1 (Shared Op A - Op B)
Notice that an Op B IMSI would behave differently in the very same scenario!!!
RNC 2 (Op A)
f2 f1 f1 f1
f2
Op A
Op A
Op A IMSI
Op A
Op B
One of the IFSO causes reaches its threshold, so IMSI IFHO triggered (IMSIbasedIFHO=enabled) and RNC sends the list of the allowed cells-> IFHO to Op A Op B own cell (PLMN 10010) Op B controlled cell shared RNC (PLMN 10021)
Authorised PLMNs
RNC reports all the intra-freq cells. There is no PLMN analysis since IMSIbasedSHO=disabled, so -> Intra Freq HO to Op B cell Op A own cell (PLMN 10010) Op A controlled cell shared RNC(PLMN 10011)
#1 #2 160 #3
10011 10010
NOKIA
3.
If at least one of the AS cells has IMSIbasedSHO=enabled and IMSIbasedIFHO/ IMSIbasedISHO=immediate The AS cell in question has one or more inter-frequency/intersystem neighbour cells whose PLMN ID equals either the home PLMN ID of the subscriber or a PLMN ID in the authorised list The PLMN ID of a monitored cell (that has triggered the reporting event 1A or 1C) does not fulfil the requirement of the home/authorised/active set PLMNs (that is why IMSIbasedSHO=enabled is needed , otherwise it wouldnt be possible to detect that the cell does not fulfil the PLMN requirement)
161
NOKIA
Summarizing .
IMSI Based Intra Freq HO Settings in an active set cell
IMSIbasedSHO=enabled
PLMN criteria
(IMSI HO trigger)
Home\Authorised
An IMSI Intra-Freq attempt to a cell that does not fulfil the Intra Freq PLMN criteria
PLMN criteria applied by RNC only over a cell which is candidate to be added in the active set
162 NOKIA
It is not required for these cells to have the IMSI feature enabled, in order to be included in the neighbour list. Just to have the proper PLMN ID
Notice the Immediate IMSI HO involves 2 cell lists: (1) To fulfil the (IMSI Intra Freq) PLMN criteria (2)Once the Immediate IMSI is triggered, the allowed PLMN IF/IS cells where the subscriber can hand over to
IMSI-based Handover can be used in different network sharing cases case 1: geographical sharing case 2: common shared RAN with gateway core case 3: mobile virtual network operator (MVNO) Based on IMSI, users of each operator can be handed over to their home or authorised WCDMA network from the shared area, when coverage becomes available (cases 1 and 2) Based on IMSI, inter-system Handovers to the users home or authorised GSM network can be performed in the shared area (all cases)
IMSI-based Handovers from the shared area: - inter-frequency HO to home or authorised WCDMA cell - inter-system HO to home or authorised GSM network Different neighbor cell definitions in RNC for different IMSI ranges
163
NOKIA
Separate neighbor lists for different IMSI ranges (different PLMN users)
GSM WCDMA GSM WCDMA GSM WCDMA GSM GSM WCDMA GSM GSM
WCDMA GSM Based on IMSI, operator B user is handed over to its own WCDMA network when coverage becomes available GSM GSM
WCDMA GSM
WCDMA GSM
Based on IMSI, load and service-based intersystem HOs to their own GSM network in shared area
Based on IMSI, operator A user is handed over to its own WCDMA network when coverage becomes available Operator B GSM cell
Based on IMSI, users are handed over to their own GSM networks when WCDMA coverage ends
Operator A GSM cell Operator A own WCDMA cell Operator A controlled shared WCDMA cell Operator A user path
164 NOKIA RANPAR Version 2.0 / 09.02.2006 / rlim
Operator B own WCDMA cell Operator B controlled shared WCDMA cell Operator B user path
Separate neighbor lists for different IMSI ranges (different PLMN users)
GSM GSM GSM WCDMA WCDMA WCDMA WCDMA GSM Based on IMSI, operator B user is handed over to its own WCDMA network when coverage becomes available GSM GSM GSM Based on IMSI, operator A user is handed over to its own WCDMA network when coverage becomes available Operator B GSM cell Operator B own WCDMA cell Operator B user path GSM Based on IMSI, users are handed over to their own GSM networks when WCDMA coverage ends WCDMA GSM GSM
Based on IMSI, load and service-based intersystem HOs to their own GSM network in shared area Operator A GSM cell Operator A own WCDMA cell Operator A user path Common shared WCDMA cell
165
NOKIA
Separate neighbor lists for different IMSI ranges (different PLMN users)
GSM GSM GSM
WCDMA
WCDMA
GSM
GSM
GSM Based on IMSI, users are handed over to their own GSM networks when WCDMA coverage ends
Based on IMSI, load and service-based intersystem HOs to their own GSM network in shared area
Operator A GSM cell Operator A controlled WCDMA cell Operator A user path
166
NOKIA