R3 3G2G Parameters Tuning Ed1

All rights reserved.
Passing on and copying of this document, use and communication of its contents not permitted without written authoriziation from Alcatel.
Site VLIZY / TIMISOARA / STUTTGART Originator H. HATIM Domain Product Division Rubric Type Distrib. codes : : : : :
MOBILE RADIO DIVISION PROFESSIONAL CUSTOMER SERVICES R3 3G-2G Parameter Tuning
RADIO OPTIMISATION 3G METHOD TUNING GUIDELINE Internal: External:
PREDISTRIBUTION
PCS PCS/STO PCS/3G E.DESBLANCS P.BLANC C.MOIGNARD DUMAS PCS/STO PCS/Quality PCS/IDDL F.JARREAU LF.GONNOT I.INTA
ABSTRACT
This document presents the strategy for parameter setting for algorithms managing 3G to 2G and 3G to 3G mobility.
KEYWORDS
inter-RAT, inter-frequency, parameter, tuning Approvals PCS/STO Date:
PCS Date:
E. DESBLANCS Signature:
F. JARREAU Signature:
PCS/3G Date:
3DF 01900 0000 PTZZA DIAMS
C. MOIGNARD DUMAS PCS/Quality Signature: Date:
LF. GONNOT Signature:
ED
01
RELEASED 01
028 1/1
MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authoriziation from Alcatel.
028 Date
DISTRIBUTION LIST
HISTORY
PCS, RNE
MRD R3_3G2G_Parameters Tuning_ed1.doc20060213 3DF 01906 3311 VAZZA END OF DOCUMENT Comments Status Edition
ED
01
RELEASED
01
2/2
TABLE OF CONTENTS
PREDISTRIBUTION...............................................................................................1 ABSTRACT...........................................................................................................1 KEYWORDS..........................................................................................................1 HISTORY..............................................................................................................2 DISTRIBUTION LIST..............................................................................................2 TABLE OF CONTENTS..........................................................................................1 REFERENCED DOCUMENTS.................................................................................3 RELATED DOCUMENTS........................................................................................3 SCOPE.................................................................................................................3 1 CELL RESELECTION FROM 3G TO 2G OR TO ANOTHER 3G CARRIER.................5
1.1 1.2 1.3 1.4 1.5 1.6 CELL SELECTION CRITERIA.................................................................................................... 5 UE MEASUREMENTS ON THE SERVING CELL..........................................................................6 ALGORITHM FOR TRIGGERING OF UE MEASUREMENTS ON NEIGHBOUR CELL.......................7 UE MEASUREMENTS ON NEIGHBOUR CELLS..........................................................................9 CELL RESELECTION CRITERIA..............................................................................................13 RNO INDICATORS AND TRACE ANALYSIS..............................................................................16
2 CELL RESELECTION FROM 2G TO 3G...............................................................18

2.1 CELL RESELECTION FROM 2G TO 3G UNDER UE CONTROL..................................................18 2.2 CELL RESELECTION FROM 2G TO 3G UNDER NETWORK CONTROL: IMPLEMENTATION IN ALCATEL B8 BSS.......................................................................................................................... 21 2.3 RNO INDICATORS AND TRACES ANALYSIS............................................................................22
3 COMPRESSED MODE.......................................................................................24
3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 COMPRESSED MODE METHOD............................................................................................. 24 COMPRESSED MODE PATTERN............................................................................................. 26 2G MEASUREMENTS IN COMPRESSED MODE.......................................................................29 DOWNLINK POWER CONTROL IN COMPRESSED MODE........................................................30 DOWNLINK FRAME TYPE...................................................................................................... 31 COMPRESSED MODE PARAMETERS......................................................................................31 EXAMPLES OF COMPRESSED MODE PATTERNS....................................................................32 RNO INDICATORS AND TRACES ANALYSIS............................................................................34
4 HARD HANDOVER BETWEEN 3G CARRIERS.....................................................36

4.1 MANAGEMENT OF INTER-FREQUENCY HHO CONFIGURATION BY RNC..................................36 4.2 UE MEASUREMENTS FOR TRIGGERING OF HHO BETWEEN 3G CARRIERS.............................38 4.3 RNO INDICATORS AND TRACES ANALYSIS............................................................................46
5 HARD HANDOVER FROM 3G TO 2G FOR AMR AND CS14.4.............................49

5.1 MANAGEMENT OF 3G TO 2G HHO CONFIGURATION BY RNC ...............................................50 5.2 UE MEASUREMENTS FOR TRIGGERING 3G TO 2G HHO .......................................................53 5.3 RNO INDICATORS AND TRACES ANALYSIS............................................................................57
6 CROSS-REFERENCES OF RNO PARAMETERS....................................................62

ED 01 RELEASED 01 028 59/61
6.1 6.2 6.3 6.4 6.5
CCT NETWORK CONTROL.................................................................................................... 62 CCT CELL CONTROL............................................................................................................. 63 CCT PHYSICAL AND LOGICAL CHANNELS.............................................................................63 CCT TRAFFIC MANAGEMENT................................................................................................ 63 DESIGN................................................................................................................................ 63
INDEX................................................................................................................65
ED
01
RELEASED 01
028 60/61
REFERENCED DOCUMENTS
Table 1: Referenced Documents CrossReference [3GAlgos] Document Title UTRAN R3 3G Radio Algorithms Document Number 3DF 01900 3310VAZZA 3DF 01900 3312 VAZZA
3DF 01900 3311 VAZZA
[3G2GAlgos] UTRAN R3 3G-2G Radio Algorithms [RNOIndic] UTRAN R3 RNO QoS indicators
R3 UTRAN Release compliant to: 3GPP Release 99 Technical Status March 2002 with CR analysis up to June 2004 3GPP Release R4 Technical Status March 2002 with CR analysis up to June 2004
RELATED DOCUMENTS
Table 2: Related Documents Document Title Document Number UTRAN ALGORITHMS SPECIFICATION PART 1 3BK 11240 0119 DSZZA R3 UTRAN ALGORITHMS SPECIFICATION PART 2 3BK 11240 0120 DSZZA R3 UTRAN ALGORITHMS SPECIFICATION PART 3 3BK 11240 0121 DSZZA R3 Telecom Parameters Catalogue 3BK 11240 0127 DSZZA ED3RL UTRAN Indicators Catalogue 3BK 11240 0129 DSZZA 5RL UTRAN Scenarios 3BK 11240 0128 DSZZA 3BK 11240 0130 DSZZA PICS to 3GPP series 25.1xx 3BK 11240 0131 DSZZA PICS to 3GPP series 25.2xx PICS to 3GPP series 25.3xx 3BK 11240 0132 DSZZA 3BK 11240 0134 DSZZA PICS to 3GPP series 25.4xx 3BK 11240 0138 DSZZA PICS to 3GPP 29.060 PICS to 3GPP 25.413 RANAP 3BK 11240 0135 DSZZA 3BK 11240 0136 DSZZA PICS to 3GPP 25.423 RNSAP PICS to 3GPP 25.433 NBAP 3BK 11240 0137 DSZZA PICS to 3GPP 25.331 RRC protocol 3BK 11240 0133 DSZZA Ed08RL Ed 03RL Ed07RL MR2 MR2 Ed
SCOPE
PURPOSE OF THE DOCUMENT
ED
01
RELEASED 01
028 59/61
This document presents the R3 tuneable parameters dealing with inter-RAT (Radio Access Technology) and inter-frequency mobility. For each parameter, we give an explanation of the recommended default value and some guidelines for specific tuning. The 3G-2G mobility algorithms are described in . The table of content of the current document is organized in the same way as [3G2GAlgos], it enables the reader to learn about the algorithms and their parameters tuning in parallel through the both documents. The document is organized along the radio algorithms that are implemented in UTRAN R3 MR2, MR3 and BSS B8. Cell selection and reselection in 3G, from 3G to 2G, in 3G inter-freq Cell reselection from 2G to 3G Hard Handover from 3G to 2G Inter-freq hard handover in 3G For each radio algorithm the document presents a detailed description and recommendations on associated tuneable parameters.
AREA OF APPLICATION
This document is intended for the radio network engineers (RNE).
ED
01
RELEASED 01
028 60/61
1 CELL RESELECTION FROM 3G TO 2G OR TO ANOTHER 3G CARRIER

The algorithm of cell selection and reselection is described in the 3GPP TS25.304, and UE measurement requirements are described in the 3GPP TS25.133.
1.1 CELL SELECTION CRITERIA

When a UE is switched on or gets out of no service area, a public land mobile network (PLMN) is selected and the UE searches for a suitable cell of this PLMN to camp on. The cell selection process is valid for a UE in: Idle state, Or in Cell-FACH state for out of service conditions only. Parameter Qqualmin Comments Domain Minimum required quality Cell level in the cell design Qrxlevmin Minimum required Rx level Cell in the cell design MaxAllowULTxP Maximum transmit power Cell ower of UE on the PRACH design Range -24 to 0 dB -115 to -25 dBm -55 to 33 dBm Step 1 2 1 Access RNO RNO RNO Example -16 dB -113 dBm 24 dBm
Qqualmin
Qqualmin is the minimum required radio quality of the selected cell (CPICH Ec/Io in dB). CPICH Ec/Io may be critical, since the DL channel estimation on CPICH get degraded in degraded radio conditions (CPICH Ec/Io<<-15dB). The parameter value setting is a trade-off between 3G coverage, 3G-2G reselection ping-pong and service availability. A low value (i.e. <-16dB) will allow the mobile to select easily a 3G cell, even if the cell quality is not good enough and to keep the UE on a 3G cell. However, when the mobile is at the cell edge, (Ec/Io=Qqualmin) it may not be able to receive correctly the paging or to establish an outgoing call. In the contrary, a high value (i.e. >16dB) will ensure that the camping mobile will be in quite good radio conditions, while accessing to the 3G services. Qqualmin will depend also on the environment (dense urban, urban, suburban, rural, or others). Indeed, if the network is dense and the RNP-target coverage is addressing almost all radio conditions (outdoor, incar, light indoor, deep indoor), the operator will secure 3G services, by maintaining 3G users on 3G cells. A high value of Qqualmin value may reduce for instance the indoor coverage. Current strategy is to implement low Qqualmin, in order to limit 3G<>2G reselection and to maintain 3G-users on 3G-cells.
Qrxlevmin
Qrxlevmin is the minimum required Rx level of the selected cell (CPICH RSCP in dBm). CPICH RSCP is an expression of the path loss, since CPICH is emitted continuously at constant and fixed power. Hence, CPICH RSCP is critical, when reaching Maximum Allowable Path Loss. Indeed, at MAPL, available power is not sufficient to overcome path loss. With regard to MAPL, UL is the most critical path, since UE available power and antenna gain are lower than Node B available power and antenna gain. MAPL is calculated according to the radio environment. Typical MAPL for dense urban are [130, 140] dB: corresponding CPICH RSCP are [-97, -107] dBm (CPICH TX power @ Node B connector = 33dBm). As for Qqualmin, the parameter value setting is a tradeoff between 3G coverage, 3G-2G reselection ping-pong and service availability. A low value (i.e. <-107dBm) will allow the mobile to select easily a 3G cell, even if the cell level is not good enough and to keep the UE on a 3G cell. However, when the mobile is at the cell edge, (RSCP=Qrxlevmin) it may not be able to receive correctly the paging or to establish an outgoing call. ED 01 RELEASED 01 028 59/61
In the contrary, a high value (i.e. >-107dBm) will ensure that the camping mobile will be in quite good radio conditions, while accessing to the 3G services.
Current strategy is to implement minimal Qrxlevmin, in order to limit 3G<>2G reselection and to maintain 3G-users on 3G-cells.
MaxAllowULTxPower
MaxAllowULTxPower is the maximum allowed transmit power of UE on PRACH (dBm). This is the value used in the link budget calculation to find out the Qrxlevmin value: when the mobile is in the cell edge (CPICH_RSCP=Qrxlevmin), the estimated UE transmit power is MaxAllowULTxPower, so if the maximum UE Tx power, thats available through RRC CONNECTION SETUP COMPLETE message in IE ue_PowerClass, is lower than the configured MaxAllowULTxPower, the UE signal can not be received correctly by the NB. For such mobiles, the Qrxlevmin value is adapted through P_compensation (refer to cell selection algorithm) Pcompensation = Max (MaxAllowULTxPower - Pmax, 0) So the mobile will select the cell only if the measured cell received level is above [Qrxlevmin+P_compensation]. Pmax is absolute max UE Tx power (dBm) is a characteristic of the UE. Its value is available through RRC CONNECTION SETUP COMPLETE message in IE ue_PowerClass and this table:
Power Class 1 2 3 4 Nominal maximum output power +33 dBm +27 dBm +24 dBm +21 dBm Tolerance +1/-3 dB +1/-3 dB +1/-3 dB 2 dB
The MaxAllowULTxPower default value is 24dBm and most commercial UE have power class4, which means that for these mobiles, Qqualmin will be increased by 3dB. Note that the MaxAllowULTxPower is used to limit the UE Tx power on RACH and also on DCH (for all services): In EVOLIUM implementation, The IE Maximum Allowed UL Tx Power is not present in the Radio Bearer Setup message so the UE will keep the value broadcast in the SIB (and used for RACH access).
1.2 UE MEASUREMENTS ON THE SERVING CELL

The UE is camped on a cell, called the Serving cell, and is either in idle state or Cell-FACH state.
1.2.1 IN IDLE STATE

The UE shall measure the CPICH Ec/Io and CPICH RSCP level of the serving cell and evaluate the cell selection criterion S for the serving cell at least every DRX cycle. Parameter DRX Cycle Description Domain Acces Tunable s Parameter k, used to define the 6 to 9, step Network RNO YES number of frames between two 1 Control Page Indicator monitoring. It is used for UE in IDLE mode attached to CS domain and PS domain. The formula is 2 exp(k) frames. Range
ED
01
RELEASED 01
028 60/61
DRX Cycle
The DRX cycle length defines UE measurement periodicity in idle mode : a small period allows the UE to update its measurements quickly and to reselect the best cell as soon reselection criterion is fulfilled however that will increase the battery consumption. A high period will help to save the UE battery but it will delay the cell reselection in mobility conditions which can lead to a call establishment failure (RRC connection establishment failure or paging not seen because the mobile didnt reselect the best cell). DRX cycle length for CS or PS = Min (DRX cycle length CS, DRX cycle length PS) = 2 k frames When k increases, the UE power consumption decreases, while the delay to reselect the best cell increases. DRX cycle length is also used in the paging procedure. In the table below you can find the FDD measurement period according to the DRX cycle setting. DRX cycle (coded value) 6 7 8 9
DRX cycle length [s] 0.64 1.28 2.56 5.12 TmeasureFDD [s] (number of DRX cycles) 1.28(2) 1.28(1) 2.56(1) 5.12(1) Nserv [number of DRX cycles] 4 2 2 1 TevaluateFDD [s] (number of DRX cycles) 5.12 (8) 6.4 (5) 7.68 (3) 10.24 (2)
The current strategy consists in choosing 7, which allows the same T measureFDD as 6, but with lower ON time (period of 1.28s, instead of 0.64s).
1.2.2 IN CELL-FACH STATE

During the CELL-FACH state the UE shall continuously measure the serving cell. If a measurement occasion is activated, intra frequency measurements can be performed between the measurement occasions. The measurement period for intra frequency measurements is 200 ms.
1.3 ALGORITHM FOR TRIGGERING OF UE MEASUREMENTS ON NEIGHBOUR CELL

The UE is camped on a particular cell and it is either in idle mode or Cell-FACH mode. Now the UE evaluates if its current cell is still strong enough or whether a cell reselection is needed, a candidate for cell reselection being one of the cells of the Monitored Set (broadcast in SIB11). Parameter Comment SintraSearchFla This parameter indicates g whether Sintrasearch exists. Sintrasearch Threshold for intrafrequency measurements SinterSearchFla This parameter indicates g whether Sintersearch exists. Sintersearch Threshold for interfrequency measurements SsearchRAT Threshold for inter-RAT (RATList.SSearc measurements hRAT)
Domain Range Cell On/Off Control Cell Control Cell Control Cell Control Cell Control -32 to 20 2 dB On/Off -32 to 20 2 dB -32 to 20 2 dB
Step
Access Example RNO On RNO RNO RNO RNO 8 dB On 6 dB 2 dB
ED
01
RELEASED 01
028 59/61
SintraSearchFlag and SintraSearch

When the SintrasearchFlag is ON, the mobile doesnt need to perform measurements on monitored intra-frequency cells if the measured quality of the serving cell is above [Qqualmin+SintraSearch]. This configuration allow to save the UE battery as the UE has not to measure the monitored cells all the time but only when the quality of the active cell is below the defined threshold. The SintraSearch threshold setting is a trade off between the cell reselection reactivity and UE battery consumption. IF SintraSearchFlag is Off, Sintrasearch is not sent for serving cell THEN the UE must always perform intra-frequency measurements. As a general rule we set the Sintrasearch so that Qqualmin+Sintrasearch=-8dB.
SinterSearchFlag and SinterSearch

When the SintersearchFlag is ON, the mobile doesnt need to perform measurements on monitored inter frequency cells if the measured quality of the serving cell is above [Qqualmin+SinterSearch]. This configuration allow to save the UE battery as the UE has not to measure the monitored inter frequency cells all the time but only when the quality of the active cell is below the defined threshold. The SinterSearch threshold setting is a trade off between the cell reselection reactivity and UE battery consumption. IF SinterSearchFlag is Off, Sintersearch is not sent for serving cell THEN the UE must always perform inter-frequency measurements. As a general rule we set the Sintrasearch so that Qqualmin+Sintersearch=-10dB.
SsearchRAT
This parameter is used to calculate the cell quality threshold for inter RAT reselection: the mobile doesnt need to measure interRAT neighbour cells if the quality of the active cell is above [Qqualmin+SSearchRAT]. This configuration allow to save the UE battery as the UE has not to measure the monitored inter RAT cells all the time but only when the quality of the active cell is below the defined threshold. The SSearchRAT threshold setting is a trade off between the cell reselection reactivity and UE battery consumption. IF SsearchRAT is not sent for serving cell THEN the UE must always perform measurements on cells of other RAT, but in Alcatel implementation, SsearchRAT is always sent when inter-RAT neighbour cells are declared. As a general rule we set the Sintrasearch so that Qqualmin+Sintrasearch=-14dB. Note: ALCATEL recommend to set the reselection threshold so that SsearchRAT<SinterSearch<Sintrasearch. With such configuration, the UE will measure first the intra frequency cells. If the active cell quality is degraded and there is no suitable intrafrequency cell to reselect, the UE will start measurements for inter frequency cells. If the active cell quality is degraded more and more and the UE is still not able to found an intra or inter frequency suitable neighbour cell to reselect, the UE can start inter RAT neighbour cells measurements. Below scheme illustrates the SsearchRAT<SinterSearch<Sintrasearch. different reselection thresholds assuming:
ED
01
RELEASED 01
028 60/61
Qqualmeas
No measurements Intra-freq measurements Sintrasearch Sintersearch Intra and inter-freq measurements SsearchRAT Intra, inter-freq, inter-RAT measurements
Qqualmin
1.4 UE MEASUREMENTS ON NEIGHBOUR CELLS 1.4.1 IN IDLE STATE

In idle state, the UE measurements are linked to DRX cycle parameter. The measurements periodicity depends on the measured cell type (intra frequency, inter frequency or inter RAT). Parameter DRX Cycle Description Domain Acces Tunable s Parameter k, used to define the 6 to 9, step Network RNO YES number of frames between two 1 Control Page Indicator monitoring. It is used for UE in IDLE mode attached to CS domain and PS domain. The formula is 2 exp(k) frames. Range
ED
01
RELEASED 01
028 59/61
DRX cycle
This parameter is described in DRX Cycle.
Measurements of intra-frequency cells

If intra-frequency measurements are necessary, the UE shall measure CPICH Ec/Io and CPICH RSCP of neighbours intra-frequency cells at least every TmeasureFDD. The UE shall filter CPICH Ec/Io and CPICH RSCP measurements of each measured intra-frequency cell using at least 2 measurements, which are taken so that the time difference between the measurements is at least TmeasureFDD/2. (TmeasureFDD is introduced in 1.22.1 UE measurements on the Serving cell.)
Measurements of inter-RAT cells

The UE shall measure the signal level of the GSM BCCH carrier of each GSM neighbour cell indicated in the measurement control system information of the serving cell at least every TmeasureGSM. The UE shall maintain a running average of 4 measurements for each GSM BCCH carrier. The measurement samples for each cell shall be as far as possible uniformly distributed over the averaging period. The table below gives the inter RAT measurements periodicity according to the DRX cycle setting. DRX cycle Nserv [number of TmeasureGSM [s] DRX cycle length [s] DRX cycles] (number of DRX (coded value)
cycles)
3 4 5 6 7 8 9
0.08 0.16 0.32 0.64 1.28 2.56 5.12
4 4 4 4 2 2 1
2.56 (32 DRX cycles) 2.56 (16) 5.12 (16) 5.12 (8) 6.4 (5) 7.68 (3) 10.24 (2)
Table 3: periodicity of inter-RAT measurements in idle according to DRX cycle
Measurements of inter-frequency cells

If inter-frequency measurements are necessary, the UE shall measure CPICH Ec/Io and CPICH RSCP of neighbours inter-frequency cells at least every (N carrier-1) * TmeasureFDD. The parameter Ncarrier is the number of carriers used for FDD cells. The UE shall filter CPICH Ec/Io and CPICH RSCP measurements of each measured inter-frequency cell using at least 2 measurements, which are taken so that the time difference between the measurements is at least T measureFDD/2. (TmeasureFDD is introduced in 1.2 UE measurements on the Serving cell.)
1.4.2 IN CELL-FACH STATE

In Cell-FACH, UE equipped with dual receiver is able to measure other frequencies (2G or FDD2) without impacting current call on FDD1. UE not equipped with dual receiver needs short interruption to measure other frequencies; these interruptions are the measurement occasions. Parameter FACHMeasure mentOccasion CycleLengthCo efficientFlag Description Range This parameter indicates On/Off if the System information contains the FACH measurement occasion cycle length coefficient. FACHMeasure This parameter indicates 1 to 12 01 RELEASED 01 Domain Step Network No control Access RNO Example On
Network
RNO
3 028 60/61
ED
mentOccasion the FACH measurement CycleLengthCo occasion cycle length efficient coefficient. FACH This parameter indicates Measurement if the System information Occasion Infor contains the FACH FLAG measurement occasion IE. OD path:Office Data/AP Information Section/ACC(REP)/ [ACC(REP)10] FACH measurement occasion info flag/
control 0/1 RNC No ODTB 0
FACH Measurement Occasion Infor FLAG

FACH Measurement Occasion Infor FLAG is a hidden parameter (not present in RNO). It can be modified via ODTB only. When this FLAG is set to OFF, the FACH measurement occasion Info IE is not broadcast in system information blocs. Consequently, the UE will not perform measurements on inter frequency cells nor inter RAT cells regardless its measurements capabilities. When the FLAG is set to ON, the FACH measurements depend on the FACH Measurement Occasion Cycle Length Coefficient Flag, FACH Measurement Occasion Cycle Length Coefficient value and UE measurements capabilities.
FACHMeasurementOccasionCycleLengthCoefficientFlag
This parameter indicates if the FACH measurement occasion cycle length is broadcast in system information blocs. If the flag is set to OFF, FACH measurement occasion length coefficient is not included in FACH measurement occasion Info IE and the UE has to perform indicated measurements (according to inter frequency FDD measurement indicator and inter RAT measurement indicators) that its able to do simultaneously as receiving the SCCPCH of serving cell according to its measurement capabilities. In such case a dual receiver UE could perform measurements on other frequencies or RATs however, mono receiver mobile is not allowed to measure cells other than intra frequency ones. If the flag is set to ON, a mono receiver UE is able to perform measurements on other frequencies/RATs during measurement occasions.
FACH Measurement Occasion Cycle length

This parameter defines the periodicity of the measurement occasions as follow: K, the FACH measurement occasion length coefficient (FACHMeasurementOccasionCycleLengthCoefficient) M_REP, the Measurement Occasion cycle length= 2k in number of frames NTTI is the number of frames in each measurement occasion, equal to the length of the largest TTI on the SCCPCH monitored by the UE=1 frame = 10 ms in Alcatel UTRAN. The FACH Measurement Occasion of NTTI frames will be repeated every N TTI * M_REP frame. System Information 11 contains FACHMeasurementOccasionCycleLengthCoefficient if FACHMeasurementOccasionCycleLengthCoefficientFlag =On.
Example with K=3, and NTTI =1:
ED
01
RELEASED 01
028 59/61
Measurement occasions
NTTI*M_REP=8 frames
NTTI=1 frame
Figure 1: measurement occasions in cell FACH The UE is assumed to measure periodically once every time period T meas on each of the modes and systems, FDD inter-frequency cells and GSM carriers for which the corresponding parameter NFDD and NGSM is set to 1. NFDD is 0 or 1. If there are inter-frequency FDD cells in the neighbour list NFDD=1, otherwise NFDD=0. NGSM is 0 or 1. If the UE is capable of GSM and there are GSM cells in the neighbour list, NGSM=1, otherwise NGSM =0. The measurement time Tmeas is then defined as
Tmeas = [ ( N FDD + N GSM ) N TTI M_REP 10] ms
Example with K=3, and NTTI =1: NFDD =1 and NGSM =0 => Tmeas = 80 ms NFDD =0 and NGSM =1 => Tmeas = 80 ms NFDD =1 and NGSM =1 => Tmeas = 160 ms A low value of the measurement cycle length will bring a high system reactivity as the mobile will be able to update its measurement more often and trigger the cell reselection procedure toward the best inter-RAT or inter-freq cell with a minimum delay however, it will cause a high traffic interruption as during measurement occasions, the UE is not listening to the active frequency, and may jeopardize intra-freq cell reselection if the Sintersearch and SRATlist are not well tuned. The interruption time ratio can be calculated as follow: Interruption ratio = 1/M_REP The measurement reporting period is: 200ms for intra frequency cells 480ms for inter RAT cells N*480ms for inter frequency cells (N is the number of FDD frequencies). For more details about measurement please refer to UTRAN_R3_3G2G algo document. The default value of FACH measurement occasion cycle length is 3. however, if one want to tune this parameter, it could be interesting to test the following values 4 and 5 in case of NFDD =0 or NGSM =0 4 in case of NFDD =1 and NGSM =1 (both GSM and inter-frequency neighbors) The table below summarizes measurements performed in idle and Cell-FACH, on the serving cell, intra-freq cells and inter-freq cells. Inter-freq results are computed In idle for Ncarrier =2, In Cell-FACH with measurement occasions for FACH measurement occasion cycle length coefficient=3, NTTI =1, NFreq,FDD=1, NFDD =1 and NGSM =0.
ED
01
RELEASED 01
028 60/61
idle (minimum DRX cycle=3) idle (DRX cycle=6) idle (maximum DRX cycle=9) cell_FACH with dual receiver cell_FACH with measurement occasions cell_DCH with dual receiver cell_DCH with compressed mode
maximum Layer 1 measurement period serving intra-freq inter-RAT inter-freq 0.08 0.64 2.36 0.64 0.64 1.28 5.12 1.28 5.12 5.12 10.24 5.12 0.2 0.2 0.48 0.48 0.2 0.2 0.48 0.48 0.2 0.2 0.48 0.48 0.2 0.2 0.48 0.48
Table 4: summary of the periodicity of the UE measurements
1.5 CELL RESELECTION CRITERIA

The UE is camped on a particular cell and it is either in idle mode or Cell-FACH mode. The UE computes cell reselection criteria based on radio measurements of the monitored cells in order to find a better cell to camp on. Cell reselection is performed on the best-ranked cell among all the monitored cells, which fulfil criterion S. Parameter Comment Domain Range Step Acces Example s Cell Selection This parameters defines Cell CPICH RNO CPICH Ec/No and reselection the measurement (CPICH Control Ec/No quality Ec/N0 or CPICH RSCP) to CPICH measure use as quality measure Q RSCP for FDD cells during cell reselection Qhysts1 Hysteresis value added to Cell 0 to 40 2 RNO 2 dB CPICH RSCP of the serving Design dB cell during cell selection/reselection. It is used to avoid ping-pong effect. Qhysts2 Hysteresis value added to Cell 0 to 40 2 RNO 2 dB the CPICH Ec/N0 of the Design dB serving cell during cell selection/reselection. It is used to avoid ping-pong effect. Qoffset_sn Offset defined per Adjacenc -50 to 50 1 RNO Inter LAC : 3 adjacency and subtracted y dB Inter PLMN : from the CPICH RSCP of 3 each neighbouring cell: Inter RAC : 3 used to limit the number Intra RAC : 1 of inter LAC or Inter RAC None : 0 reselections and thus decrease signalling. Qoffset2_sn Offset defined per Adjacenc -50 to 50 1 RNO Inter LAC : 3 adjacency and subtracted y dB Inter PLMN : from the CPICH Ec/N0 of 3 each neighbouring cell: Inter RAC : 3 used to limit the number Intra RAC : 1 of inter LAC or Inter RAC None : 0 reselections and thus decrease signalling. Qoffset_snGSM Offset defined per GSM -50 to 50 1 RNO 50 dB adjacency and subtracted Adjacenc dB from the GSM carrier RSSI y of each GSM neighbouring cell. ED 01 RELEASED 01 028 59/61
Parameter
Comment
Domain
Range
Step 2 1 1
GSMQrxlevmin Minimum required average received signal level in the GSM cell. GSMMaxAllowU Maximum allowed UL lTxPower transmit power in GSM. Treselection Time-to-trigger for cell reselection. The cell reselection is valid only if the criteria R was verified during the time Treselection
GSM cell -115 to 25 dBm GSM cell -50 to 33 dBm Cell Control 0 to 31s
Acces Example s RNO -101 dBm

RNO RNO
33 dBm 1s
Cell Selection and reselection quality measure

This parameter defines the measurement (CPICH Ec/N0 or CPICH RSCP) to use as quality measure Q for FDD cells during intra FDD cell reselection (intra frequency and inter frequency cell reselection). Whatever the value CPICH RSCP criterion is always checked. If the parameter is set to CPICH RSCP, only CPICH RSCP criterion is checked, If the parameter is set to CPICH Ec/No, first CPICH RSCP criterion is checked, then CPICH Ec/No criterion is checked. For inter RAT cell reselection, we use always the CPICH RSCP criterion regardless the value of this parameter. The recommended ALCATEL value is CPICH Ec/Io. It allows reselecting the cell offering the best quality. However, CPICH RSCP could be useful For inter frequency reselection (case of frontier area between two constructors using different frequencies): in this case the is less inter-cell interference because neighbour cells are using different frequency than the active one. Therefore, the CPICH RSCP is the limiting criterion. In case of inter LAC/RAC areas as the RSCP measurements are more accurate and offer more tuning range than Ec/Io. In such areas we should limit the number of reselection to avoid high signalling volume as each reselection will be followed by LA/RA update procedure.
Qhysts1
Hysteresis is added to CPICH RSCP of the serving cell during cell selection/reselection. It is used to avoid ping-pong effect. ALCATEL recommended value is 2dB that correspond to 4dB hysteresis as illustrated in the figure below: Selected cell
Cell 2
Cell 1
-Qhysts1
Qhysts1
CPICH_RSCP_cell2 - CPICH_RSCP_cell1
Total hysteresis
Figure 2: total hysteresis engendered by Qhysts1 (with Qoffset = 0)
ED
01
RELEASED 01
028 60/61
This parameter is used for all types of cell reselection (intra frequency, inter frequency and inter RAT). The Qoffset_sn parameter can be adjusted per adjacency to adapt the Qhyst.
Qhysts2
Hysteresis is added to CPICH Ec/No of the serving cell during cell selection/reselection. It is used to avoid ping-pong effect. This parameter is broadcast only if the cell selection/reselection quality measure is set to CPICH Ec/No. ALCATEL recommended value is 2dB that correspond to 4dB hysteresis. This parameter is used for intra and inter-frequency cell reselection. Qoffset2_sn can be adjusted per adjacency to adapt the Qhysts.
Qoffset_sn
Offset defined per adjacency and subtracted from the CPICH RSCP of each neighbouring cell: used to limit the number of reselections and especially inter LAC or Inter RAC reselections and thus decrease signalling. ALCATEL default value is: 3dB for inter LAC/RAC/PLMN. With Qhysts1 set to 2dB, the UE will reselect an inter RAC/LAC cell only when its CPICH RSCP is 5dB better than the active cell one; which correspond to a total Hysteresis of 10dB (=(2+3)x2).. 0dB for other adjacencies With Qhysts1 set to 2dB, the UE will reselect a target cell if its CPICH RSCP is 2dB higher than the source cell one.
Qoffset2_sn
Offset defined per adjacency and subtracted from the CPICH Ec/No of each neighbouring cell: used to limit the number of reselections and especially inter LAC or Inter RAC reselections and thus decrease signaling. This parameter is broadcasted only if the cell selection/reselection quality measure is set to CPICH Ec/No. ALCATEL default value is: 2dB for inter LAC/RAC/PLMN which correspond to a total Hysteresis of 8dB (=(2+2)x2). It means that the UE will reselect an inter RAC/LAC cell only when its CPICH Ec/No is 5dB better than the active cell one. 0dB for other adjacencies so the UE will reselect a target cell if its CPICH Ec/No is 2dB higher than the source cell one.
ED
01
RELEASED 01
028 59/61
Qoffset_snGSM
This offset is defined per adjacency and subtracted from the GSM carrier RSSI of each GSM neighbouring cell. The recommended value is +50dB (maximum value) to reduce the inter system reselection signalling and to keep the UE under 3G coverage while S criterion is fulfilled.
Treselection
The UE shall reselect the new cell only if its better ranked than the serving cell during the time interval Treselection. A high value will help to reduce ping-pong effect but it will delay the reselection procedure. This parameter should be set taking into account the DRX cycle length value as it defines the measurements periodicity in idle mode. The Treselection default value is 1s. So when using a DRX cycle length of 7, the measurement periodicity in idle mode is 1.28s and is higher than the Treselection value which means that the reselection procedure will be based only on 1 measurement and it will be 1s delayed. Theoretically, in this case we should set the Treselection to 0s but we avoid this as it can be interpreted as a special value by some UE, which can lead to some misbehaviours (UE-specific implementation). Moreover, Treselection is used also for reselection in Cell-FACH state in which the measurement period is 200ms so with a 1s value, the reselection criteria will be checked over 5 measurement periods. A higher value (3s) could be used in specific areas (inter LAC/RAC, border area) to reduce signalling volume generated by Location Update procedures.
GSMQrxlevmin
Minimum required average received signal level in the GSM cell. ALCATEL recommend the same value as in 2G network, e.g. -101dBm. GSMQrxlevmin should be consistent with the matching GSM parameter RXLEV_ACCESS_MIN.
GSMMaxAllowUlTxPower
Maximum allowed UL transmit power in GSM. ALCATEL recommend the same value as in 2G network, e.g. 33dBm. GSMMaxAllowUlTxPower MS_TXPWR_MAX_CCH. should be consistent with the matching GSM parameter
1.6 RNO INDICATORS AND TRACE ANALYSIS 1.6.1 RNO INDICATORS

The cell reselection procedure is controlled by the UE and there is no direct indicator for 3G-to2G reselection, as this procedure is transparent for the UTRAN. However, the performances for cell reselection and 3G-to-2G reselection have an obvious impact on the RRC connection success rate especially for 3G cells in the border area or with a coverage hole. Indicator RRC_connect_succ_rate_register RRC_connection_success_rate Description This indicator reports the success rate of RRC connections with cause 'Registration'. This indicator reports the rate of successful RRC connection requests.
More relevant statistics/indicators are available at CN level: Number of LAU and RAU LAU and RAU success rates Paging efficiency
ED
01
RELEASED 01
028 60/61
CN statistics could also be used to benchmark different UE vendors by following the corresponding IMSIs (friendly users for example) and extracting the corresponding LAU and RAU statistics.If more accurate statistics are needed, its strongly recommended to perform drive tests and to use Iu and Iub traces.
1.6.2 TRACE ANALYSIS

As described above, its strongly recommended to perform drive tests and to make statistics based on UE and Iu/Iub traces. The drive tests could be performed with Repetitive mobile originating calls (30s call duration with 30s pause between consecutive calls) Repetitive mobile terminating calls (30s call duration with 30s pause between consecutive calls) Idle mode Cell-FACH state The following indicators should be monitored MOC call success rate MTC call success rate % of time spent in 2G and % calls established in 2G Number of 3G to 2G reselections 3G to 2G reselection procedure time duration RRC connection success rate DRX cycle failure rate (Qualcomm CAIT log, indicating DRX cycles, for which the UE can not read PICH indications) On Iu/Iub and A/Abis traces we can get statistics on RAU and LAU procedures Paging efficiency RRC connection success rate RRC repetition rate
ED
01
RELEASED 01
028 59/61
2 CELL RESELECTION FROM 2G TO 3G

The algorithm is described in the 3GPP TS05.08. As the Alcatel UTRAN may be neighboured with a BSS of any constructor, we start with 3GPP description, then we focus on Alcatel B8 BSS implementation. Multi-RAT User Equipment camping on 2G, or attached to GPRS on 2G may measure 3G cells. Reselection of the 3G cells may be under control of the UE or the network. In GMM Standby state, and packet idle mode, cell-reselection is performed by UE. In GMM Ready state, cellreselection is either performed by UE or controlled by network. This is indicated by the parameter NETWORK_CONTROL_ORDER. The meaning of the different parameter values is specified as follows: NC0 - Normal MS control: The MS shall perform autonomous cell re-selection. NC1- MS control with measurement reports: The MS shall send measurement reports to the network. The MS shall perform autonomous cell re-selection. NC2 - Network control: The MS shall send measurement reports to the network. The MS shall only perform autonomous cell re-selection when the reselection is triggered by a downlink signaling failure or a random access failure. RESET - The MS shall return to the broadcast parameters. Only sent on PCCCH or PACCH. The parameter values NC1 and NC2 only apply in Ready state. In Standby state, the MS shall always use normal MS control independent of the ordered NC mode.
2.1 CELL RESELECTION FROM 2G TO 3G UNDER UE CONTROL

At SGSN level, the UE is either in: Idle state, the subscriber is not attached to the SGSN. The UE in GMM idle state monitors SI (system information) broadcast on the BCCH. GMM Standby state (the UE is not transmitting data), GMM Ready State (the UE is transmitting data or has just transmitted data) and NETWORK_CONTROL_ORDER=NC0 or NC1. If PBCCH is activated and if the UE is PBCCH capable, the UE in GMM standby or ready state monitors PSI (Packet System Information) broadcast on the PBCCH. Otherwise, the UE in GMM standby or ready state monitors SI (system information) broadcast on the BCCH.
Qsearch_I, Qsearch_P
Qsearch_I and Qsearch_P define the 2G received level average threshold for 3G neighbours measurements when the UE monitors BCCH or PBCCH. The UE monitoring BCCH searches for 3G cells: Either when RLA_C (Received Level Average) of the serving cell is below Qsearch_I, Qsearch_I belongs to [-98dBm ; -74dBm], Or when RLA_C (Received Level Average) of the serving cell is above Qsearch_I, Qsearch_I belongs to [-78dBm ; -54 dBm], Or always, Or never. The UE monitoring PBCCH searches for 3G cells: Either when RLA_P (Received Level Average) of the serving cell is below Qsearch_P, Qsearch_P belongs to [-98dBm ; -74dBm], Or when RLA_P (Received Level Average) of the serving cell is above Qsearch_P, Qsearch_P belongs to [-78dBm ; -54 dBm], Or always, Or never.
ED
01
RELEASED 01
028 60/61
The table below gives the coding rule for these two parameters.
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
= -98 dBm = -94 dBm = -90 dBm = -86 dBm = -82 dBm = -78 dBm = -74 dBm (always) = -78 dBm = -74 dBm = -70 dBm = -66 dBm = -62 dBm = -58 dBm = -54 dBm (never)
Table 5: Qsearch_I and Qsearch_P codind values
Qsearch_I is sent in system information SI 2ter or SI 2quater depending on BSS constructor. Qsearch_P is sent in system information Packet SI 3 quarter, or Packet Measurement Order or Packet Cell Change Order messages. In ALCATEL BSS Qsearch is broadcast in SI2ter on BCCH (Qsearch_I) and in PSI 3quater on PBCCH (Qsearch_P) if there is a PBCCH allocated in the serving cell. The default UE value if Qsearch_I is not sent in system information is 15 (never). When Qsearch_I=7 (infinity), UE shall always measure 3G cells. Until now, operators traffic strategy is to keep the 3G mobiles under 3G-coverage, while its possible and the UE shall go back to 3G cells, as soon as a 3G suitable cell is detected. So, the recommended value is always: when the UE is camped on a 2G cell, it shall always search for 3G cells.
FDD_Qmin
FDD_Qmin is the minimum quality threshold for cell reselection. FDD_Qmin is sent in system information SI 2ter or SI 2quater depending on BSS constructor. FDD_Qmin is sent in system information Packet SI 3 quarter or Packet Measurement Order or Packet Cell Change Order messages. In ALCATEL BSS it is broadcast in SI2ter on BCCH and in PSI 3quater on PBCCH if there is a PBCCH allocated in the serving cell.The default UE value if FDD_Qmin is not sent in system information is 7 (-12 dB). The table below gives the coding rule for this parameter.
0 1 2 3 4 5 6 7
ED 01
above
below
= -20 dB = -6 dB = -18 dB = -8 dB = -16 dB = -10 dB = -14 dB = -12 dB

RELEASED 01 028 59/61
Table 6: FDD_Qmin coding values FDD_Qmin should be consistent with Qqualmin parameter setting. To avoid ping-pong effect and to reduce signalling volume, generated by location update procedure following eac inter system reselection, ALCATEL recommend to set this parameter as follow: FDD_Qmin = Qqualmin+4dB.
FDD_Qoffset and FDD_GPRS_Qoffset

FDD_Qoffset and FDD_GPRS_Qoffset are offset applied to the Received Level Average before checking the cell reselection criterion when the UE monitors BCCH or PBCCH. In ALCATEL BSS, its broadcast in SI2ter on BCCH (FDD_Qoffset) and in PSI 3quater on PBCCH (FDD_GPRS_Qoffset) if there is a PBCCH allocated in the serving cell The table below gives the coding rule for this parameter.
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
= -28 dB = -24 dB = -20 dB = -16 dB = -12 dB = -8 dB = -4 dB = 0 dB = 4 dB = 8 dB = 12 dB = 16 dB = 20 dB = 24 dB = 28 dB

Table 7: FDD_Qoffset and FDD_GPRS_Qoffset coding values
(always select a cell if acceptable)
FDD_Qoffset is sent in system information SI 2ter or SI 2quater depending on BSS constructor. The default UE value if FDD_Qoffset is not sent in system information is 8 (0 dB). FDD_GPRS_Offset is sent in system information Packet SI 3 quarter or Packet Measurement Order or Packet Cell Change Order messages. FDD_Qoffset and FDD_GPRS_Qoffset should be consistent with Qoffset_snGSM. The default value is 0, which means that the UE will reselect a 3G cell, as soon as its quality is above FDD_Qmin, regardless the received level of the 2G serving cell. This value is consistent with the recommended Qoffset_snGSM one (set to maximum value = +50dB).
ED
01
RELEASED 01
028 60/61
2.2 CELL RESELECTION FROM 2G TO 3G UNDER NETWORK CONTROL: IMPLEMENTATION IN ALCATEL B8 BSS
In GMM Idle and Standby state, the cell reselection is under UE control. In GMM Ready state, either the cell reselection is under UE control or there is no cell reselection possible from 2G to 3G. Alcatel does not advise 3G cells measurements while the UE is in Packet Transfer Mode (implies GMM Ready state). Indeed, the UE could interrupt its data transfer frequently for monitoring 3G neighbour cells and a degradation of throughput is observed while the UE is performing measurements on 3G cells. Alcatel B8 BSS only enables mobile autonomous GSM to UMTS cell reselection. NC2 is not available for inter-RAT cells, thus preventing the multi-RAT UE from searching for UMTS FDD cells while the UE is in GMM ready state and in NC2 mode. 3G search deactivation introduced in Alcatel BSS B8 prevents the multi-RAT UE from searching for UMTS FDD cells while the UE is in GMM ready state and in NC0 mode. Parameter Comment Domain Range Step Acces s Example enum RNO 0
NETWORK_CON Defines whether the UE or GSM cell TROL_ORDER the BSS controls the cell reselections. NC2_DEACTIVA TION_MODE
EN_2G_TO_3G_ CELL_RESELEC TION
FDD_ARFCN_LI ST
0: NC0 2: NC2 for R99 onwards UE 3: NC2 for all UE Defines whether or not GSM cell 0: NC2 enum RNO the Packet Measurement deactivation at Order with a Reset the end of the Command is sent at the packet transfer, end of a packet transfer. PMO is sent 1: NC2 deactivation at the expiry of the GMM Ready timer, PMO is not sent Enables/Disables the GSM GSM cell 0: Disabled enum RNO to UTRAN FDD cell 1: Enabled with reselections and defines 3G search the 3G-search activation activated while mode for MS in GMM the UE is in Ready state. GMM ready state 2: Enabled with 3G search deactivated while the UE is in GMM ready state List of neighbour FDD BSS 0 to 3276,6 0.2 RNO UTRAN frequencies MHz 0 = 0.0 MHz, 1 = 0.2 MHz, ... , 16383 = 3276.6 MHz. The value of -1 indicates that no UTRAN frequency is provided.
10786
ED
01
RELEASED 01
028 59/61
NETWORK_CONTROL_ORDER
Defines whether the UE or the BSS controls the cell reselections.
NC2_DEACTIVATION_MODE
Defines whether or not the Packet Measurement Order with a Reset Command is sent at the end of a packet transfer.
EN_2G_TO_3G_CELL_RESELECTION
Enables/Disables the GSM to UTRAN FDD cell reselections and defines the 3G-search activation mode for MS in GMM Ready state.
FDD_ARFCN_LIST
List of neighbour FDD UTRAN frequencies: 0 = 0.0 MHz, 1 = 0.2 MHz, ... , 16383 = 3276.6 MHz. The value of -1 indicates that no UTRAN frequency is provided. Note that in UMTS FDD mode the DL frequency is in the range [2110MHz:2170MHz]. The FDD_ARFCN_LIST corresponding range is [10550:10850].
2.3 RNO INDICATORS AND TRACES ANALYSIS 2.3.1 RNO INDICATORS

The cell reselection procedure is controlled by the UE and in RNO there is only one direct indicator for 2G-to-3G reselection. However, the cell reselection and 2G to 3G re-selection performances have an obvious impact on the RRC connection success rate especially for 3G cells in the border area or with a coverage hole. Indicator RRC_connect_succ_rate_register RRC_connection_success_rate RRC_connect_succ_rate_interRA T RRC_connect_req_interRAT Description This indicator reports the success rate of RRC connections with cause 'Registration'. This indicator reports the rate of successful RRC connection requests. This indicator reports the success rate of RRC connections with cause 'Inter-RAT cell re-selection' or 'Inter-RAT cell change order'. This indicator reports the number of RRC connection requests with cause 'Inter-RAT cell re-selection' or 'Inter-RAT cell change order'.
More relevant statistics/indicators are available at CN level: Number of LAU and RAU LAU and RAU success rates Paging efficiency CN statistics could also be used to benchmark different UE vendors by analyzing the LAU and RAU statistics. With IMSI-trace for friendly users and target testers With IMEI-trace for all mobiles from one vendor If more accurate statistics are needed, it is strongly recommended to perform drive tests and to use Iu/Iub and A/Abis traces.

As described above, its strongly recommended to perform drive tests and to make statistics based on UE and Iu/Iub traces. The drive tests could be performed with ED 01 RELEASED 01 028 60/61
Repetitive mobile originating calls (30s call duration with 30s pause between consecutive calls) Repetitive mobile terminating calls (30s call duration with 30s pause between consecutive calls) Idle mode Cell-FACH state The following indicators should be monitored MOC set-up success rate MTC set-up success rate % Time spent in 2G and % calls established in 2G Number of 3G to 2G reselections 3G to 2G reselection procedure time duration RRC connection success rate DRX cycle failure rate On Iu/Iub and A/Abis traces we can get statistics on RAU and LAU procedures Paging efficiency RRC connection success rate RRC repetition rate
To evaluate the ping-pong effect, it could be useful to perform some tests in static conditions (indoor environment). Note also that the RNO indicator for RRC connection requests with cause inter-RAT reselections from 04:00AM to 06:00AM (time frame, where almost all UEs are in static conditions) gives an idea on the 3G-2G reselection ping-pong effect.
ED
01
RELEASED 01
028 59/61
3 COMPRESSED MODE
The compressed mode is a mechanism allowing creation of idle period in radio frame in order to leave some time for the UE to perform some measurement on other frequencies, without losing data on the current frequency. Compressed mode pattern parameters are specified in 3GPP TS25.215.
3.1 COMPRESSED MODE METHOD

Parameter Comment SF_reduction_method_t This parameter defines the hreshold threshold on the SF used to select the scrambling code type (same/alternative) during compressed mode CMPattern.DeltaSIR1 Delta in DL SIR target value to be set in the UE/Node B during the frame containing the start of the first transmission gap in the transmission gap pattern(without including the effect of the bit-rate increase). CMPattern.DeltaSIRafte Delta in DL SIR target value to be r1 set in the UE/Node B one frame after the frame containing the start of the first transmission gap in the transmission gap pattern. CMPattern.TGCFN This parameter defines the connection frame number of the first frame of the first pattern within the transmission gap pattern sequence. CMPattern.TGL1 This parameter defines the length of the transmission gap within the transmission gap pattern. CMPattern.TGPL1 This parameter defines the duration of transmission gap pattern in number of frames. CMPattern.NidentifyAbo This parameter defines the rt maximum number of repeat that the UE shall use to attempt to decode the unknown BSIC of GSM cell in the initial BSIC identification procedure (Mandatory for Initial BSIC identification only). CMPattern.TreconfirmA This parameter indicates the bort maximum time allowed for the reconfirmation of the BSIC of one GSM cell in the BSIC reconfirmation procedure (Mandatory for BSIC reconfirmation only). RPP Recovery Period Power control mode during the frame after the transmission gap within the compressed frame. Indicates whether normal PC mode or ED 01 RELEASED 01 Domain Range Step Access Network SF4, enum RNO SF8, SF16, SF32, SF64, SF128, SF256 Network 0-3 dB 0.1 RNO
Network 0-3 dB
0.1
RNO
Network
0-255 frames
RNO
Network 3,4,5,7, enum 10,14 slots Network 1-144 1 frames Network 1-128 1
RNO RNO RNO
Network 0.5-10 s
0.5
RNO
Network Mode0 enum Mode1
OD
028 60/61
Parameter ITP
Comment Domain Range Step Access compressed PC mode is applied Initial Transmit Power is the uplink Network Mode0 enum OD power control method to be used to Mode1 compute the initial transmit power after the compressed mode gap
SF_reduction_method_threshold
In R3 release, the compressed mode is done via the reduction of SF, which consists in reducing the spreading factor, by two during compressed frames, so as to transmit the same amount of information in half the time, but with much more power. SF/2 method is implemented in this release for both uplink and downlink.
Figure 3: compressed mode mechanism SF/2 is used only for compressed frames; uncompressed frames are transmitted with SF. Reduction of SF is implemented with 2 options: Same scrambling code option: SF/2 channelisation code reservation at the compressed mode configuration time, recommended for low rates services, Alternative scrambling code option: alternative-scrambling code is derived from the normal one according to 3GPP, recommended for high rate services. In uplink, as the UE may use the whole channelisation code tree of its dedicated scrambling code, same scrambling code method is applied. In case the UL DPCH has been configured with a "UL Minimum SF" equal to 4, the SF reduction method cannot be used. In such case, the RNC shall not configure compressed mode for this UE. In downlink, the same scrambling code option is selected if the SF is higher than the SF_reduction_method_threshold. Otherwise, the alternative scrambling code method is selected. Each option in downlink presents disadvantages: Same scrambling code method implies that a channelisation code with a lower SF than required during normal frames, need to be reserved for the compressed frame, which increases the risk of code shortage. In this release, when same scrambling code method is used, the RNC assigns systematically two channelization codes at connection establishment whether compressed mode is needed or not: 1st of size SF to support requested RAB, for instance 128 for AMR, used for normal frames. 2nd of SF/2, father of the 1st one, for instance 64 for AMR, used for compressed frames. Alternative scrambling code method, the signal during the compressed frame will no longer be orthogonal to other signals from the same cell, and this may lead to some extra intra-cell interference. However, there is no need to reserve a channelisation code with a lower SF than required during normal frames. The recommended value for SF_reduction_method_threshold is 8, which means that the same scrambling code method is used except for PS384 service. So there will be no extra intra cell interference but we may have a code shortage in case of traffic increase.
ED
01
RELEASED 01
028 59/61
In case of code shortage, the SF reduction method threshold could be set to 64 so that the code reservation is done only for AMR and PS 32kbps. However, as this configuration has never been tested in the field, its strongly recommended to perform preliminary tests on experimental zone to evaluate the impact/gain before generalization on the whole commercial network. Note: as there is no RNO indicators on the code usage, its difficult to detect the code shortage without taking RNC or Iu/Iub traces.
3.2 COMPRESSED MODE PATTERN

The main parameters for TGPS (Transmission Gap Pattern Sequence) are:
#TGCFN #1 TG pattern #2 TG pattern #TGPRC TG pattern
Transmission gap
#TGSN
#TGL
#TGPL
Figure 4: compressed mode pattern (at frame level) A specific (TGPS) is configured for each measurement: GSM Initial BSIC identification, GSM BSIC reconfirmation, GSM carrier RSSI, From 1 to 4 GSM cells From 5 to 6 GSM cells From 7 to 12 GSM cells Other FDD carrier RSSI. Three different patterns are defined to measure GSM carrier RSSI depending on the number of cells to be monitored. The RNC shall take into account only the cells which require compressed mode to select the CM pattern. The inter-frequency measurements request the activation of one transmission gap pattern sequence. The inter-RAT measurements (with BSIC verification) request the activation of three simultaneous pattern sequences: one for the measurement of the GSM carrier RSSI, one for the initial BSIC identification and one for the BSIC reconfirmation. To be able to perform simultaneous inter-frequency and inter-RAT handover, four pattern sequences are activated in parallel. Note that its strongly recommended to use ALCATEL default values as they were optimized based on simulations and tested on the field. In case one is asked to modify this setting for a specific issue, its mandatory to perform preliminary tests on the LAB/model network before introducing it in the commercial network. ED 01 RELEASED 01 028 60/61
CMPattern.TGCFN
TGCFN (Transmission Gap Connection Frame Number) defines the CFN of the first frame of the first pattern within the transmission gap pattern sequence. This parameter can be used to delay the activation of a specific pattern in case of multiple CM patterns activation: for GSM measurements, we activate 3 parallel CM patterns. To be sure that the UE will verify the BSIC of the best GSM cell, we activate first the GSM RSSI measurement pattern and then we activate the BSIC patterns after a delay of some measurement periods (i.e. 480ms) so that the mobile could perform at least one RSSI measurement sample on the GSM neighbours before starting the BSIC verification and that can avoid the case where the UE reports a MR3a for the first measured GSM cell which is not the best one. In the other hand, this configuration introduces a delay in the HHO procedure and that can lead to some drops in case of fast degradation of radio conditions. Hereafter a general configuration rule of TGCFN for GSM measurement patterns assuming a TGPL of 24 frames: CMPattern.TGCFN for RSSI measurements = 4 CMPattern.TGCFN for BSIC verification = 12 + N*48 CMPattern.TGCFN for BSIC reconfirmation = 20 + N*48 48 is the GSM measurements reporting period in number of frames (i.e. 480ms). N*48 is the pattern activation delay (multiple of LCM(48,24)=48). We can note also that with the recommended configuration, in case of simultaneous presence of inter-RAT and inter-frequency monitored cells, which means that the 4 CM patterns will be activated in parallel, the inter-frequency pattern will start about 1 s before the BSIC verification. In other words, this is a way to prioritise inter-frequency HHO.
TGSN
TGSN (or Nfirst) (Transmission Gap Starting slot Number) is the slot number of the transmission gap slot within the first frame of the first pattern within the TGPS, this parameter is configurable in OD but not in RNO, default values are: 0 when TGL = 7 (single frame method) 8 when TGL = 10 or 14 (double frame method). Note that TGPS with one gap only are used. This parameter is not configurable in RNO.
CMPattern.TGPL1 & CMPattern.TGL1

TGPL (Transmission Gap Pattern Length) is the duration of the transmission gap pattern in number of frames. TGL (Transmission Gap Length) is the length of the transmission gap within the transmission gap pattern in number of slots. The TGPL and TGL have to be configured taking into account the following constraints to avoid overlapping of compressed frames: Constraint 1: If the UE uses compressed mode for inter-frequency and/or inter-RAT measurements, in order for the 3GPP requirements regarding the measurements in Cell-DCH state to apply, the UTRAN must provide transmission gap pattern sequences with TGPL>1 and ensure that with the activation of several transmission gap pattern sequences in parallel, no more than two frames contain a transmission gap within any window of three consecutive frames.
Constraint 2: During the measurement period (480 ms), the UE must acquire three RSSI samples per cell Constraint 3: A minimum of 8 slots between the end of the first transmission gap and the beginning of the second transmission gap must be ensured in case of two successive compressed frames. ED 01 RELEASED 01 028 59/61
Constraint 4: The inter-frequency handover requests the activation of one transmission gap pattern sequence. The inter-RAT handover (with BSIC verification) requests the activation of three simultaneous pattern sequences: one for the measurement of the GSM carrier RSSI, one for the initial BSIC identification and one for the BSIC reconfirmation.
Note: Despite it requires more decoding time from the UE and it complicates the compressed mode, the BSIC has to be verified in order to avoid the risk that the UE measures an RSSI actually resulting from another cell than the one the SRNC indicates, and then later tries a handover to the wrong cell. The consequence is that to be able to configure simultaneous inter-frequency and inter-RAT measurements, the UTRAN shall be able to activate four pattern sequences in parallel. The TGL and TGPL parameters configuration is a trade-off between measurements acquisition and the compressed mode time. To configure TGL and TGPL parameters we should take into account the following metrics Time to identify a new FDD inter-frequency cell Time to measure 6 FDD inter-frequency cells Number of FDD inter-frequency carriers (up to 2 carriers in R3) Time to identify a GSM carrier Time to reconfirm a GSM carrier Number of GSM cells (up to 12 in R3)
The time to identify a new FDD inter-frequency cell and the time to measure 6 FDD interfrequency cells are given below. Tidentify_inter(ms)=Max{5000,800*Nfreq*1/r} Tmeasure_inter(ms)=Max{480,50*Nfreq*1/r} Where Nfreq is the number of FDD inter-frequency carriers R is the compressed mode ratio and its function of TGL, TGPL and frame type. The table below gives the compressed mode performances function of TGL and TGPL for best case (DL frame type A & SF4) and worst case (DL frame type B &SF256). TGPL 6 6 6 8 8 8 10 10 10 CM ratio (%) 5.2 8.6 13 3.9 6.4 9.8 3.1 5.1 7.8 T_identify Worst Best Case Case (in s) (in s) 15.3 13.1 9.4 8.5 6.2 5.8 20.5 17.5 12.5 11.3 8.2 7.7 25.6 21.9 15.6 14.1 10.3 9.6 T_measure Worst Best Case Case (in s) (in s) 1 0.8 0.6 0.5 0.5 0.5 1.3 1.1 0.8 0.7 0.5 0.5 1.6 1.4 1 0.9 0.7 0.6
TGL
7 10 14 7 10 14 7 10 14
So we can see that ALCATEL default values for TGL and TGPL TGPL=8 and TGL=14offer a good trade-off between the measurements acquisition duration and system performances. However, it could be interesting to test the following configurations: TGPL=6 & TGL=14 to reduce the T_identify if the CM activation ratio is low. As the CM ratio with this configuration is 13% (in stead of 9.8% with default configuration), this setting may degrade the system performances especially if the CM activation ratio is high. TGPL=8 & TGL=10 to reduce the CM ratio (i.e. time spent in CM) however, this will degrade the HHO success rate as the measurement time will be increased. This configuration may be used in case of high CM activation rate .
ED
01
RELEASED 01
028 60/61
In the same way, the 3GPP standard gives the number of GSM RSSI sample a UE is able to perform in 1 CM gap according to the TGL value:
TGL
Number of GSM carrier RSSI samples in each gap. 1 2 3 6 10 15
3 4 5 7 10 14
Assuming that the UE needs to perform 3 GSM RSSI samples per measurement period (480ms), the table below gives for a given TGPL and a given number of GSM cells to be measured, the necessary TGL: Number of GSM cells TGPL=8 TGPL=16 TGPL=24 1 3 3 4 2 3 4 5 3 4 5 7 4 4 7 7 5 5 7 10 6 5 7 10 7 7 10 14 8 7 10 14 9 7 10 14 10 7 10 14 11 7 14 12 7 14
In case of setting the TGPL to 24, the maximum number of GSM cell that the UE could monitor simultaneously within 480ms is 10 (when using the maximum TGL value). In this case, when the UE has to monitor more than 10 GSM cells, the reporting interval is a multiple of 480ms. According to the table above, we can use three (TGL, TGPL) configurations depending on the number of 2G monitored cells: (TGPL=24 and TGL=7) to monitor up to 4 2G cells (TGPL=24 and TGL=10) to monitor 5 or 6 2G cells (TGPL=24 and TGL=14) to monitor between 7 and 12 2G cells. In this case, the RNC will configure/reconfigure the CM patterns according to the 2G monitored set size. If requested by the costumer, one can test the following configurations: TGPL=24 & TGL=14 for the three patterns regardless the 2G monitored set size. This configuration avoids reconfiguring the CM pattern when the 2G monitored set size is modified (update after SHO). At the other hand, this will increase the CM time ratio and thus degrade the system performances. To use only if there is too many CM reconfiguration (that can lead to call drops) and the CM activation ratio is not very high. TGPL=24 and TGL=10 to monitor more than 5 cells (i.e same setting for 2 nd and 3rd patterns). This setting allows to reduce the CM time ratio however it will impact the HHO success rate as the GSM measurement period will be increased in case of GSM neighbour set size higher than 7. to use only if the CM activation ratio is very high. Note that this configuration will also reduce the CM reconfiguration occurrence.
TGPRC
TGPRC (Transmission Gap Pattern Repetition Count) is the number of transmission gap patterns within the TGPS. Since the inter-RAT or inter-freq measurements are stopped on event, this parameter is set to infinity.
3.3 2G MEASUREMENTS IN COMPRESSED MODE

Three sorts of measurements are required for the inter-RAT handover purpose: For the GSM carrier RSSI, For the GSM Initial BSIC identification, For the GSM BSIC reconfirmation. ED 01 RELEASED 01 028 59/61
The BSIC of GSM cells has to be verified in order to avoid the risk that the UE measures a RSSI actually resulting from another cell that the one the SRNC indicates, and then later tries a handover to the wrong cell. The GSM initial BSIC identification and the GSM BSIC reconfirmation are used to acquire the BSIC of the GSM cell. This information completes the ARFCN that is not sufficient to identify the GSM cell without any ambiguity.
CMPattern.NidentifyAbort
In initial BSIC identification, CMPattern.NidentifyAbort defines the maximum number of repeat (number of gaps) that the UE shall use to attempt to decode the BSIC of GSM cell. The default value is 22. Its a 3GPP value given for the worst-case time for identification corresponding to the configuration (TGPL=24 & TGL= 14). The 3GPP value for other configurations can be found in the table below.
TGL1 TGPL1 Tidentify abort [slots] [frames] [s] Pattern 1 Pattern 2 Pattern 3 Pattern 4 Pattern 5 7 7 14 14 10 3 8 8 24 12 1.56 5.28 1.84 5.28 2.88 Nidentify_abort [patterns] 52 66 23 22 36
CMPattern.TreconfirmAbort
In the BSIC reconfirmation procedure, CMPattern.TreconfirmAbort indicates the maximum time allowed for the reconfirmation of the BSIC of one GSM cell. The default value is 5s. Its a 3GPP recommended value for (TGPL=24 & TGL=14). The recommended value for the other configurations is given in the table above (same value than Tidentify abort).
3.4 DOWNLINK POWER CONTROL IN COMPRESSED MODE

This is described in 3GPP 25.214 and also mentioned in 25.331. DL TX power and DL SIR target are increased during the compressed frame to keep the quality (BLER) unaffected by the reduced processing gain. In compressed mode, the target SIR needs to be changed in several frames compared to normal mode. For this purpose, DeltaSIR1, DeltaSIRafter1 are signalled by the UTRAN to the UE.
CMPattern.DeltaSIR1
Delta in DL SIR target value to be set in the UE during the frame containing the start of the first transmission gap in the transmission gap pattern(without including the effect of the bit-rate increase : 3dB increase). The default value is 0dB, which means that the DL SIR will be increased by 3dB in the first compressed frame.
CMPattern.DeltaSIRafter1
Delta in DL SIR target value to be set in the UE one frame after the frame containing the start of the first transmission gap in the transmission gap pattern. The default value is 1. As the TGSN is set to 0 for TGL=7 and 8 for TGL=10 or 14, the DL SIR in the frame after the frame containing the start of the first TG will be increased by 1dB for CM patterns with TGL=7 ED 01 RELEASED 01 028 60/61
4dB for CM patterns with TGL=10 or 14.
Recovery Period Power control mode

This parameter defines the Recovery Period Power control mode during the frame after the transmission gap within the compressed frame. It indicates whether normal PC mode or compressed PC mode is applied. After a transmission gap in either the uplink or the downlink, the period following resumption of simultaneous uplink and downlink DPCCH transmission is called a recovery period. RPL is the recovery period length and is expressed as a number of slots. RPL is equal to the minimum value out of the transmission gap length and 7 slots. If a transmission gap is scheduled to start before RPL slots have elapsed, then the recovery period shall end at the start of the gap, and the value of RPL shall be reduced accordingly. During the recovery period, 2 modes are possible for the power control algorithm. The Recovery Period Power control mode (RPP) is signalled with the other compressed mode parameters. The default mode is mode 0 which means that the normal power control will be applied during RPP period. The use of RPP mode 1, and as the PCA (Power Control Algorithm) is set to algorithm 1, means that during RPP period we will use a PC step size of 2dB instead of 1dB. This parameter is not modifiable via RNO.
Initial Transmit Power

Initial Transmit Power is the uplink power control method to be used to compute the initial TX power after the compressed mode gap. The default value is Mode 0 which means that there is no filtering of the TPC commands.
3.5 DOWNLINK FRAME TYPE

There are two different types of frame structures defined for DL compressed frames. Type A maximises the transmission gap length and type B is optimised for power control. Higher layers set the frame structure type A or B at compressed mode configuration (RRC Radio Bearer Setup or RRC Physical Channel Reconfiguration). With frame structure of type A, the pilot field of the last slot in the transmission gap is transmitted. Transmission is turned off during the rest of the transmission gap. With frame structure of type B, the TPC field of the first slot in the transmission gap and the pilot field of the last slot in the transmission gap are transmitted. Transmission is turned off during the rest of the transmission gap. This parameter is configurable in OD, but not in RNO, default value is DL frame type A.
3.6 COMPRESSED MODE PARAMETERS

Parameter Example Pattern 1 Pattern 2 Pattern 3 Pattern 4 Pattern 5 Pattern 6 Pattern 7 Initial BSIC GSM GSM GSM One FDD Two FDD BSIC reconfirm carrier carrier carrier frequency frequenci identificat ation RSSI cells RSSI cells RSSI cells es ion pattern 1 to 4 5 to 6 7 to 12 pattern CMPattern.DeltaSIR1 0 0 0 0 0 0 0 CMPattern.DeltaSIRafter 1 1 1 1 1 1 1 1 CMPattern.NidentifyAbor 22 dummy dummy dummy dummy dummy dummy t CMPattern.TGCFN 108 116 4 4 4 0 0 ED 01 RELEASED 01 028 59/61
CMPattern.TGL1 CMPattern.TGPL1 CMPattern.TreconfirmAb ort
14 24 dummy
14 24 5
7 24 dummy
10 24 dummy
14 24 dummy
14 8 dummy
14 8 dummy
3.7 EXAMPLES OF COMPRESSED MODE PATTERNS

With the values given as examples in 3.6 Compressed mode Parameters, the different patterns are represented in the figures below. For a UE that performs only inter-frequency measurements, the inter-frequency pattern is at frame and slot level:
Compressed mode activation for inter-freq
TGSN=8 TGL=14 slots SF/2 Transmission gap SF/2
TGCFN=0
TGPL=8 frames SF uncompressed frames SF/2 compressed frames for inter-freq measurements
Figure 5: example of compressed mode pattern for inter-frequency measurements For a UE that performs inter-RAT measurements, the 3 inter-RAT patterns are activated. It is assumed that the number of monitored 2G cells is above 5 (double frame method for RSSI measurements). The frames are sequentially represented below:
ED
01
RELEASED 01
028 60/61
Compressed mode activation for inter-RAT TGCFN(GSM carrier RSSI)=4

TGCFN(BSIC reconfirmation)=116
TGCFN(initial BSIC identification)=108
TGPL=24 frames SF/2 compressed frames for GSM carrier RSSI cells 5 to 12 measurements SF/2 compressed frames for initial BSIC identification SF/2 compressed frames for BSIC reconfirmation SF uncompressed frames
Figure 6: example of compressed mode patterns for inter-RAT measurements For a UE that performs both inter-frequency and inter-RAT measurements, the frames are sequentially represented below:
ED
01
RELEASED 01
028 59/61
Compressed mode activation for both inter-freq and inter-RAT TGCFN(inter-freq)=0 TGCFN(BSIC reconfirmation)=116 TGCFN(GSM carrier RSSI)=4 TGCFN(initial BSIC identification)=108
TGPL(inter-freq)=8 frames TGPL(inter-RAT)=24 frames SF/2 compressed frames for inter-freq measurements SF/2 compressed frames for GSM carrier RSSI cells 5 to 12 measurements SF/2 compressed frames for initial BSIC identification SF/2 compressed frames for BSIC reconfirmation SF uncompressed frames
Figure 7: example of compressed mode patterns for both inter-freq and inter-RAT measurements

In RNO, we can monitor the number of CM activation and the number of CM deactivation for both inter-frequency and inter-RAT HHO. However, we have a global indicator for all services: we can not distinguish, for example, the volume of compressed mode activation for AMR interfrequency HHO and CS64 or PS inter-frequency HHO. For inter-RAT HHO, as the CCO is not supported in R3, all the inter-RAT compressed mode activations correspond to AMR HHO. Indicator Compress_mod_inter_freq_desa ct_request Compress_mod_inter_freq_desa ct_request_ratio Compress_mod_inter_RAT_act_r equest_ratio Compress_mod_inter_RAT_desa ct_request Description This indicator reports the number of compressed mode deactivations for inter-frequency measurements during the measurement period. This indicator reports the ratio of compressed mode deactivations for inter-frequency measurements during the measurement period. This indicator reports the ratio of compressed mode activations for inter-RAT measurements during the measurement period. This indicator reports the number of compressed mode deactivations for inter-RAT measurements during the measurement period.
Based on these indicators we can monitor the following KPIs for inter-RAT: ED 01 RELEASED 01 028 60/61

Number of CM activation per AMR call CM deactivation to CM activation ratio CM efficiency (CM activation to HHO request ratio)
These indicators help to monitor the CM performances and to tune the CM parameters (event 2d and event 2f thresholds and time to trigger). There is no RNO indicator for CM time duration: it is recommended to perform some drive tests with UE and UTRAN traces to analyze the CM patterns performances in more details.

UE and UTRAN traces are recommended for CM patterns performances analysis. Moreover, the field tests showed that the CM and HHO performances are UE dependent so it will be very helpful to benchmark the most used UE via UE and UTRAN traces. The drive tests could be performed with Long AMR calls in mobility condition Choose a road with 3G coverage holes The following KPIs should be monitored Number of call drops Total drops Drops in CM Drops due to HHO failure Drops due to CM reconfiguration Number of inter-RAT HHO HHO success rate CM time ratio (time spent in CM) Number of CM activations Radio conditions at CM activation (CPICH RSCP & Ec/No and UE Tx power) Number of CM deactivations Radio conditions at CM deactivation (CPICH RSCP & Ec/No and UE Tx power) Number of CM pattern reconfigurations Mean time between CM activation and first measurement on 2G cells % of 3a MR to add a 2G cell that doesnt have the best RSSI (among all 2G neighbours)
ED
01
RELEASED 01
028 59/61
4 HARD HANDOVER BETWEEN 3G CARRIERS

Inter-freq HHO can be performed based on UE preliminary radio level measurements of current cell(s) only, or both current and target cell(s). In connected mode, inter-freq measurements are possible with compressed mode feature. UEs equipped with dual receiver do not need compressed mode to measure inter-freq cells. Radio measurements are performed on: Current cell only WHY? Dangerous degradation of the current radio link(s). WHEN? UE is not equipped with dual receiver and compressed mode is not supported by UE, or not configured by UTRAN, Or UE was not able to measure and report a satisfying cell in time. WHAT? Blind Radio Hard Handover=Emergency Hard Handover. Both current and target cell WHY? Degradation of the current radio link(s). WHEN? UE is equipped with dual receiver or compressed mode is supported by UE and UTRAN (from R3) and is configured, And UE measures and reports a satisfying cell in time. WHAT? Radio Hard Handover.
4.1 MANAGEMENT OF INTER-FREQUENCY HHO CONFIGURATION BY RNC

Different types of HHO as represented in Figure 8 are triggered by the following RRC events: Figure 8: compressed mode and HHO management by RRC events RNC is in charge of configuring adequate measurements depending on: BlindHORadio, EmergencyHO UE capabilities UE context
4.1.1 PARAMETERS BLINDHORADIO, EMERGENCYHO

Parameter BlindHORadio EmergencyHO Comment Domain This parameter enables to Network activate the blind handover radio option. Activation of the Network emergency handover option in order to face dead zone situation. For UE supporting GSM, this parameter gives a priority to the UMTS or the GSM emergency cell. Range On/Off GSM, UMTS, None Step No Access RNO RNO Example Off None
ED
01
RELEASED 01
028 60/61
BlindHORadio
When the BlindHORadio is set to ON, and the EmergencyHO is set to UMTS or none, only emergency blind radio inter-frequency hard-handover is configured.The inter frequency blind HHO is triggered on event 2d_em, if there is a UMTS emergency cell, without measurements on inter frequency target cell. When the BlindHORadio is set to OFF, and the EmergencyHO is set to none, only interfrequency hard-handover is configured, with measurements on inter frequency target cell. When the BlindHORadio is set to OFF, and the EmergencyHO is set to UMTS, both interfrequency hard-handover are configured: with and without measurements on inter frequency target cell. Alcatel recommends deactivating the Blind HHO. So the BlindHORadio flag is set to Off. In this case, the mobile will try to measure the target cell before triggering the HHO. And if the radio conditions are degraded quickly and the mobile doesnt have enough time to perform those measurements, the UE can report a MR 2d_em to trigger an emergency handover towards a UMTS inter-frequency emergency cell if the EmergencyHO is set to UMTS.
EmergencyHO
At this stage of commercial network deployment and traffic volume, there was no need to use a second frequency therefore, the inter-frequency emergency HO is not activated. However, according to field experience, the activation of the Emergency handover for inter-RAT, degrades the system performances and increase significantly the ratio of AMR calls handed over to GSM whereas the operators strategy is to keep the 3G users under 3G coverage as long as possible. Nevertheless this feature could be helpful for specific cells presenting high inter-frequency HO failure rate and radio drop rate. These cells are identified based on RNO KPIs and the emergency cells should be defined carefully taking into account the radio environment of the source cell. To activate emergency HHO only on certain cells: EmergencyHO is a network parameter that should be set to UMTS, some cells have inter-frequency emergency neighbours, and some cells dont.
4.1.2 UE CONTEXT: INTER-FREQUENCY MONITORED CELL LIST

In the UE context, RNC stores the list of Active Set cells and Monitored Set cells. The interfrequency monitored set/emergency cell are defined using the following parameters Parameter Comment Max_FDD_cells Maximum number of FDD inter-frequency cells to monitor Max_FDD_carri Maximum number of FDD ers inter-frequency carriers to monitor BlindHOinterFre Index of inter frequency quencyID neighbour in case of blind HHO Domain Range Network 0 to 12 Network 0 to 2 Cell Design 0 to 11 Step 1 1 1 Access RNO RNO RNO Example 6 1 1
ED
01
RELEASED 01
028 59/61
Max_FDD_cells
This parameter is used by the RNC to define the list of inter-frequency neighbour cells to monitor by the UE. It defines the maximum number of inter-frequency cells in the monitored set. In R3, the maximum value for Max_FDD_cells is 12 but the CM patterns are configured for 1 measurement per 480ms for 6 inter-frequency monitored cells. If the monitored set size is higher than 6 the inter-frequency measurements period will be a multiple of 480ms, which can introduce some delay in the HHO procedure. Thats why ALCATEL recommend to set the Max_FDD_cells to 6 and to limit the number of declared inter-frequency adjacent cells. We can rely on RNO indicators (number of inter-frequency HHO request and inter-frequency HHO success rate per adjacency) to delete the adjacencies without HHO traffic.
Max_FDD_carriers
Its the maximum number of FDD carriers to monitor. This parameter is also used by the RNC to define the list of inter-frequency cells to monitor.
BlindHOinterFrequencyID
This parameter is used to flag the inter-frequency neighbour cell to use as emergency cell in case of emergency inter-frequency HHO. The emergency cell should be chosen carefully taking into account the RNO inter-frequency HHO traffic indicators (number of inter-frequency HHO request and inter-frequency HHO success rate per adjacency) and the network topology.
4.2 UE MEASUREMENTS FOR TRIGGERING OF HHO BETWEEN 3G CARRIERS

Radio measurements are configured by RNC through downlink RRC Measurement Control (MC) that contains: Measurement id, Measurement command (setup, modify or release), Event type and associated parameters. Measurements Reports (MR) can be either periodical or event triggered; only event triggered are involved in HHO and compressed mode algorithms. When conditions are fulfilled, UE sends uplink RRC Measurement Report, which contains the Measurement id registered from Measurement Control. Events involved are: 2d and 2f, which require measurements on the current FDD frequency, 2b, which requires measurements on the current FDD frequency and another FDD frequency
4.2.1 UTRAN FREQUENCY QUALITY ESTIMATE

Parameter Comment Domain Range InterFreq.FilterCoeffi Defines the filter Networ 0,1,2,3,4,5, cient coefficient that shall k 6,7,8,9,11,1 be used to evaluate 3,15,17,19 the Inter Frequency measurements InterFreq.MeasQuan Defines the Networ CPICH tOwnFreq measurement quantity k Ec/N0, used by the UE to CPICH evaluate whether an RSCP, inter-frequency Pathloss measurement event has occurred or not, through the computation of the own frequency quality estimate. ED 01 RELEASED 01 Step enum Access RNO Example 2
enum
RNO
CPICH RSCP
028 60/61
InterFreq.MeasQuantOwnFreq
This parameter defines the measurement quantity to be used by the UE to evaluate the inter frequency events. So its used in all 2x events: Event 2d: activation of compressed mode Event 2f: deactivation of compressed mode Event 2b: inter frequency HHO event As the 2d events are the same for inter-RAT and interfrequency HHO procedure, the interFreq.MeasQuantOwnFreq impacts also the interRAT configuration. The recommended value is CPICH Ec/No. However, the CPICH RSCP could be better in specific areas where the CPICH RSCP is the limiting criteria (i.e degradation of CPICH RSCP whereas the CPICH Ec/No stays at quite good level). This is the case for Boundary cells Use of two different frequencies on the same sector. To determine the right criterion, we should perform a coverage test in the involved area to collect CPICH RSCP and Ec/No measurements and then, based on measurements analysis one could choose the limiting criterion as follow: Fix a limit threshold for RSCP (e.g. 105dBm) Fix a limit threshold for CPICH Ec/No (e.g. 12dB) Compute the percentage of samples for which the CPICH RSCP is under the limit threshold whereas the CPICH Ec/No is above the limit threshold (% RSCP limitation) Compute the percentage of samples for which the CPICH Ec/No is under the limit threshold whereas the CPICH RSCP is above the limit threshold (% Ec/No limitation) If the % RSCP limitation is higher then set the criterion to CPICH RSCP If the % Ec/No limitation is higher then set the criterion to CPICH Ec/No Note that in R3 this parameter is configurable per RNC and not per cell class. On dense networks, the system performances, in term of call drop rate as well as inter-RAT HHO ratio and success rate, were improved by changing the criterion from RSCP to Ec/Io. We can also rely on RNO counters to evaluate the best criterion by testing the both settings (on an experimental area if possible) and compare the corresponding performances based on System call drop rate Ratio of AMR calls handed over to GSM Inter-RAT HHO success rate
InterFreq.FilterCoefficient
This parameter defines the filter coefficient value to apply for the filtering of the measurement quantity before the evaluation of the inter frequency event. The filtering 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 unit used in the event evaluation. a = 1/2(k/2), where k is the parameter received in the IE "Filter coefficient"= InterFreq.FilterCoeficient. NOTE: if k is set to 0 that will mean no layer 3 filtering.
ED
01
RELEASED 01
028 59/61
In order to initialise the averaging filter, F0 is set to M0 when the first measurement result from the physical layer measurement is received. The filter coefficient should be high enough to smooth measurements and avoid ping-pong effect. However, a too high filter coefficient will impact the UE reactivity (delay to add/delete a cell) in case of quick variation of radio conditions. The averaging window depends on the filter coefficient and the measurements period : Tavg=Tprd/(1/2(k/2) Tavg is the averaging window Tprd is the measurements period (200ms for intra-frequency measurements and 480ms for inter-RAT and inter-frequency measurements). K is the filter coefficient
The table below gives the averaging window for different filter coefficient values Filter coefficient 1 2 3 4 5 6 7 Intra frequency Measuremen ts period (ms) 200 200 200 200 200 200 200 Averaging window (ms) 283 400 566 800 1131 1600 2263 Inter-RAT and inter-frequency Filter Measuremen Averaging coefficient ts period window (ms) (ms) 1 480 679 2 480 960 3 480 1358 4 480 1920 5 480 2715 6 480 3840 7 480 5431
SHO tests showed that a filter coefficient of 4 offers a good trade-off between measurements averaging and UE reactivity. This value corresponds to an averaging window of 800ms. To keep the same averaging window for inter-frequency and inter-RAT measurements, we should set the inter-RAT and inter-frequency filter coefficient to 2. Note: some mobiles are not able to handle more than 2 different filter coefficients and at reception of a new measurement control asking the UE to configure a third filter coefficient with a new value, whereas the UE is alredy using two different values, the UE cancel this measurement control and send a MC failure message to the RNC. This situation could lead to call drops as the MC cancellation will avoid the RNC to handle correctly the UE mobility. So its recommended to not use more than 2 different values for the different filter coefficients (intrafrequency, inter-frequency and inter-RAT filter coefficient).
4.2.2 RADIO INTER-FREQ HHO: EVENT 2B

Event 2b: The estimated quality of the currently used frequency is below a certain threshold and the estimated quality of a non-used frequency is above a certain threshold. Parameter Comment Event2B.Threshol The range -115 to -25 dUsedFrequency dBm is used with CPICH RSCP and the range -24 to 0 dB with CPICH Ec/N0 Event2B.Threshol The range -115 to -25 dnonUsedFrequen dBm is used with CPICH cy RSCP and the range -24 to 0 dB with CPICH Ec/N0 Event2B.Threshol Offset added to dOffset thresholds for used and non used frequency to assess event 2B. Introduced in R3 MR3 ED 01 RELEASED 01 Domain Range Network -115 to 0 Step 1 Access RNO Example -100 dBm Network -115 to 0 1 RNO -90 dBm Downlink 0 to 115 Physical Channel 1 RNO 2 dB for CS64
028 60/61
Parameter Comment Event2B.WUsedFr Weighting Factor equency Event2B.WnonUs Weighting Factor edFrequency Event2B.Hysteresi s Event2B.TimetoTri gger
Domain Network Network
Range 0 to 2 0 to 2
Step 0.1 0.1 0.5 enum
Access RNO RNO RNO RNO
Example 0 0 0 dB 0 ms
Network 0 to 14.5 dB Network 0,10,20, 40,60,80 ,100,120 ,160,200 ,240,320 ,640,128 0,2560,5 000 ms
Event2B.ThresholdUsedFrequency
This Network parameter is added to the Event2B.ThresholdOffset to define the event 2b threshold for used frequency per service. The range -115 to -25 dBm is used with CPICH RSCP and the range -24 to 0 dB with CPICH Ec/N0. As the measurement quantity is set to Ec/No, the Event2B.ThresholdUsedFrequency is set to 24dB and then the offset is tuned per service. This configuration make it possible to deactivate the inter-frequency HO for a specific services just by setting the offset to 0 (the Event2B.ThresholdOffset is set in the range [0..50]).
Event2B.ThresholdnonUsedFrequency
This Network parameter is added to the Event2B.ThresholdOffset to define the event 2b threshold for non-used frequency per service. The range -115 to -25 dBm is used with CPICH RSCP and the range -24 to 0 dB with CPICH Ec/N0. As the measurement quantity is set to Ec/No, the Event2B.ThresholdUsedFrequency is set to 22dB and then the offset is tuned per service. We recommend a 2dB offset between Event2B.ThresholdUsedFrequency Event2B.ThresholdnonUsedFrequency to avoid pig-pong effect. and
Event2B.ThresholdOffset
This Downlink Physical Channel parameter was introduced in R3MR3 to customize the event 2b thresholds ( for used and non used frequencies) per service. For AMR we set the offset so that the event 2b threshold for used frequency is 1dB higher than event 3a threshold. The idea behind is to trigger the inter-frequency HHO before the inter-RAT HHO in case of presence of both inter-RAT and inter-frequency monitored cells. The recommended value for AMR is 13dB. For CS64 and PS384kbps the offset is set 1dB higher compared to AMR, as they require higher quality. For other services, we recommend to set the offset to the same value as AMR.
Event2B.WusedFrequency
This parameter is a weighting factor used to compute the measurement quantity for the used frequency before event 2b evaluation. The recommended value is 0 to take into account only the best cell on the used frequency.
ED
01
RELEASED 01
028 59/61
Event2B.WnonUsedFrequency
This parameter is a weighting factor used to compute the measurement quantity for the non used frequency before event 2b evaluation. The recommended value is 0 to take into account only the best cell on the non used frequency.
Event2B.Hysteresis
This parameter defines an hysteresis for event 2b criterion. The recommended value is 0dB. A 2dB hysteresis could be helpful in case of Event2B.TimetoTrigger set to 0ms to avoid useless repetitive 2b measurement reports.
Event2B.TimetoTrigger
This is the time during which the event 2b criterion should be fulfilled before reporting the event 2b measurement report RRC message. The default value is 0ms to speed up the inter-frequency HHO procedure. However, if we want to get more accurate measurements on the target frequency, we should set the TTT to a non-null value to let the UE check the criterion on more than one measurement. And as the measurement period for inter-frequency is 480ms, we should set the TTT so that TTT>(N-1)*480ms Where N is the number of measurement the UE has to check for inter-frequency criterion. For example, if we want to check the criterion on 2 inter-frequency measurements, we have to set the TTT to 640ms.
4.2.3 COMPRESSED MODE ACTIVATION: EVENT 2D_CM, EMERGENCY HHO: EVENT 2D_EM
Event 2d: the estimated quality of the currently used frequency is below a certain threshold. Except that the thresholds are different for event 2d_cm (compressed mode activation) and 2d_em (emergency hard handover), same device is used. Parameter Comment Domain Range Step Access Example Event2D.Threshol Threshold for CM Network -115 to 0 1 RNO dCMactivation activation. The range -93 dBm -115 to -25 dBm is used with CPICH RSCP and the range -24 to 0 dB with CPICH Ec/N0 Event2Dcm.Thres Offset added to threshold Downlink 0 to 115 1 RNO holdOffset for CM activation. Physical dB 2 dB for Introduced in R3 MR3 Channel CS64 Event2D.Threshol Threshold for Emergency Network -115 to 0 1 RNO dEmergencyHand Handover. The range -115 -105 over to -25 dBm is used with dBm CPICH RSCP and the range -24 to 0 dB with CPICH Ec/N0 Event2Dem.Thres Offset added to threshold Downlink 0 to 115 1 RNO holdOffset for Emergency Handover. Physical dB 2 dB for Introduced in R3 MR3 Channel CS64 Event2D.WUsedFr Weighting Factor Network 0 to 2 0.1 RNO 0 equency Event2D.Hysteres Network 0 to 14.5 0.5 RNO 0 dB is dB Event2D.TimetoTri Network 0 to enum RNO 640 ms ED 01 RELEASED 01 028 60/61
Parameter gger
Comment
Domain
Range 5000 ms
Step
Access
Example
Event2D.ThresholdCMactivation
This Network parameter is added to the Event2Dcm.ThresholdOffset to define the threshold for compressed mode activation. The range -115 to -25 dBm is used with CPICH RSCP and the range -24 to 0 dB with CPICH Ec/N0. As the measurement quantity is set by default to Ec/No, the Event2D.ThresholdCMactivation is set to 24dB and then the offset is tuned per service. This configuration make it possible to avoid activation of compressed mode for a specific services just by setting the offset to 0 (the Event2DcmB.ThresholdOffset is set in the range [0..50]).
Event2Dcm.ThresholdOffset
This Downlink Physical Channel parameter was introduced in R3MR3 to customize the event 2d thresholds per service. This parameter should be set taking into account the event 2f threshold, event 3a threshold and event 2b threshold. The offset between event 2d and event 2f thresholds will affect the compressed mode activation/deactivation ping-pong effect. The offset between event 2d and event 3a/2b threshold will affect the time spent in compressed mode and HHO ratio. A high offset value will enable the UE to make accurate measurements on other frequency/system however, the UE will spend more time in compressed mode and that can degrade the system performances as the compressed mode activation requires more radio resources. In the other hand, a low offset will help to save radio resources but can increase the call drop ratio in case of quick radio conditions degradation as the UE will not have enough time to perform measurements on the target cell and trigger the HHO. For AMR, the recommended value is 13dB. Which means that the compressed mode will be activated when the CPICH Ec/No is lower than 11dB. For CS64 and PS384 we recommend setting the offset 1dB higher compared to AMR, as they require higher quality.
Event2D.ThresholdEmergencyHandover
This Network parameter is added to the Event2Dem.ThresholdOffset to define the threshold for emergency handover. The range -115 to -25 dBm is used with CPICH RSCP and the range -24 to 0 dB with CPICH Ec/N0. As the measurement quantity is set by default to Ec/No, the Event2D.ThresholdEmergencyHandover is set to 24dB and then the offset is tuned per service. This configuration make it possible to avoid activation of emergency handover for a specific services just by setting the offset to 0 (the Event2D.ThresholdOffset is set in the range [0..50]).
Event2Dem.ThresholdOffset
This Downlink Physical Channel parameter was introduced in R3MR3 to customize the event 2d thresholds per service. This parameter should be set taking into account the event 2d for compressed mode threshold, event 3a threshold and event 2b threshold. According to field experience, the activation of the Emergency handover for inter-RAT, degrades the system performances and increases significantly the ratio of AMR calls handed over to GSM whereas the operators strategy is to keep the 3G users under 3G coverage as long as possible.
ED
01
RELEASED 01
028 59/61
Thus, we dont recommend using the Emergency handover on the whole network. The emergency handover can be activated on specific cells with high HHO failure rate and radio call drop rate based on RNO data. We can set the 2d emergency HO offset so that the emergency HO threshold is 2dB lower than 3a/2b thresholds so that if the radio conditions are quickly degraded and the UE hasnt enough time to perform measurements on monitored cells, which means that no event 3a/2b will be reported, the UE will try to trigger a blind HO towards the emergency cell. The emergency cell should be also carefully selected based on RNO counters (number of HHO request and HHO success rate per adjacency) and radio environment.
Event2D.WusedFrequency
This parameter is a weighting factor used to compute the measurement quantity for the used frequency before event 2d evaluation. The recommended value is 0 to take into account only the best cell on the used frequency.
Event2D.Hysteresis
This parameter defines a hysteresis for event 2d criterion. The recommended value is 0dB. A 2dB hysteresis could be helpful in case of Event2D.TimetoTrigger set to 0ms to avoid useless repetitive 2d measurement reports.
Event2D.TimetoTrigger
This parameter defines the time during which the event 2d criterion has to be fulfilled before reporting 2d measurement report RRC message. The recommended value is 640ms to avoid compressed mode activation when the radio conditions are degraded for short period and consequently that will reduce the CM activation/deactivation ping-pong effect and save radio resources. Inter-RAT HHO tests on commercial 3G network showed that the system reacts more on the event threshold than on the event time to trigger.
4.2.4 COMPRESSED MODE DEACTIVATION: EVENT_2F

Event 2f: The estimated quality of the currently used frequency is above a certain threshold. Parameter Comment Event2F.Thresho Threshold for CM deldUsedFrequenc activation. The range y -115dBm to -25dBm is used with CPICH RSCP and the range -24dB to 0dB is used with CPICH Ec/N0. Domain Range Network -115 to 0 Step 1 Access Example RNO -80 dBm
Event2F.Thresho Offset added to threshold ldOffset for CM deactivation. Introduced in R3 MR3 Event2F.Hystere sis
Downlink 0 to 115 Physical dB Channel Network 0 to 14.5 dB
1 0.5
RNO RNO
2 dB for CS64 0 dB
Event2F.TimeToT rigger ED 01 RELEASED
Network
0,10,20, 40,60,80
enum
RNO
640 ms 028
01
60/61
Parameter
Comment
Domain
Event2F.WUsedF Weighting factor requency
Network
Range ,100,120 ,160,200 ,240,320 ,640,128 0,2560,5 000 0 to 2
Step
Access Example
0.1
RNO
Event2F.ThresholdUsedFrequency
This Network parameter is added to the Event2F.ThresholdOffset to define the threshold for compressed mode deactivation. The range -115 to -25 dBm is used with CPICH RSCP and the range -24 to 0 dB with CPICH Ec/N0. As the measurement quantity is set by default to Ec/No, the Event2F.ThresholdUsedFrequency is set to 24dB and then the offset is tuned per service.
Event2F.ThresholdOffset
This Downlink Physical Channel parameter was introduced in R3MR3 to customize the event 2f thresholds per service. This parameter should be set taking into account the event 2d threshold, event 3a threshold and event 2b threshold. The offset between event 2d and event 2f thresholds will affect the compressed mode activation/deactivation ping-pong effect. For CS64 and PS384kbps we recommend an offset of 2dB compared to event 2d threshold. For AMR and other services we recommend a 3dB offset compared to event 2d threshold to reduce the compressed mode activation/deactivation ping-pong effect.
ED
01
RELEASED 01
028 59/61
Inter-RAT HHO tests performed on commercial 3G network showed that the system reacts more on the event threshold than on the event time to trigger.
Event2F.WusedFrequency
This parameter is a weighting factor used to compute the measurement quantity for the used frequency before event 2f evaluation. The recommended value is 0 to take into account only the best cell on the used frequency.
Event2F.Hysteresis
This parameter defines a hysteresis for event 2f criterion. The recommended value is 0dB. A 2dB hysteresis could be helpful in case of Event2F.TimeToTrigger set to 0ms to avoid useless repetitive 2f measurement reports.
Event2F.TimetoTrigger
This parameter defines the time during which the event 2f criterion has to be fulfilled before reporting 2f measurement report RRC message. The recommended value is 640ms to avoid compressed mode deactivation and re-activation when the radio conditions are improved for short period and consequently that will reduce the CM activation/deactivation ping-pong effect. The compressed mode activation procedure takes about 3s during which the RNC will discard or queue all other RRC messages thats why its better to reduce the CM deactivation/activation ratio.

In RNO, we can monitor the number of CM activation and the number of CM deactivation for both inter-frequency and inter-RAT HHO. However, we have a global indicator for all services, therefore, we cant distinguish for example the volume of compressed mode activation for AMR inter-frequency HHO and CS64 or PS inter-frequency HHO. For inter-RAT HHO, as the CCO is not supported in R3, all the inter-RAT compressed mode activations correspond to AMR HHO.
ED
01
RELEASED 01
028 60/61
Indicator Compress_mod_inter_freq_desa ct_request

Compress_mod_inter_freq_act_r equest Compress_mod_inter_RAT_act_r equest_ratio Compress_mod_inter_RAT_desa ct_request Inter_freq_AMR_12_2k_request Inter_freq_AMR_12_2k_success Inter_freq_conv_64k_64k_reque st Inter_freq_conv_64k_64k_succe ss Inter_freq_PS_request Inter_freq_PS_success
Description This indicator reports the number of compressed mode deactivations for inter-frequency measurements during the measurement period. This indicator reports the number of compressed mode activations for inter-frequency measurements during the measurement period. This indicator reports the ratio of compressed mode activations for inter-RAT measurements during the measurement period. This indicator reports the number of compressed mode deactivations for inter-RAT measurements during the measurement period. This indicator reports the number of requests for interfrequency handover initiated by RNC for UE supporting a AMR RAB per couple of cells. This indicator reports the number of successes for interfrequency handover initiated by RNC for UE supporting a AMR RAB per couple of cells. This indicator reports the number of requests for interfrequency handover initiated by RNC for UE supporting a CS64 RAB per couple of cells. This indicator reports the number of successes for interfrequency handover initiated by RNC for UE supporting a CS64 RAB per couple of cells. This indicator reports the number of requests for interfrequency handover initiated by RNC for UE supporting a PS RAB per couple of cells. This indicator reports the number of successes for interfrequency handover initiated by RNC for UE supporting a PS RAB per couple of cells.
Based on these indicators we can monitor the following KPIs for inter-frequency: Number of inter-freq CM activation per user Inter-freq CM deactivation to inter-freq CM activation ratio CM efficiency (CM activation to inter-freq HHO request ratio) These KPI help monitor the CM performances and tune the CM parameters (event 2d and event 2f thresholds and time to trigger). Since there is no RNO indicator for CM time duration, it is recommended to perform some drive tests with UE and UTRAN traces to analyze the CM patterns performances in more details. At this stage of network deployment there is no need to use a second frequency. At least in R99, the second frequency will be used on specific cells to increase the capacity or to avoid high interference issue (pilot pollution area in dense urban environment). Traffic on these cells will be very low and thus it will be more relevant to analyze the inter-frequency performances per adjacency and per cluster. Moreover, for AMR, we should correlate the inter-frequency performances to the inter-RAT ones. One can monitor for example Inter-RAT HHO to inter-freq HHO ratio. It can give an idea on the difference between event 2b and event 3a thresholds. Total CM activations per AMR call (as the event 2d is common to both HHO types).
Its also recommended to perform some drive tests in the involved area taking the UE and UTRAN traces for deeper analysis.
ED
01
RELEASED 01
028 59/61

UE and UTRAN traces are recommended for CM patterns performances analysis. Moreover, the field tests showed that the CM and HHO performances are UE dependent so it will be very helpful to benchmark the most used UE via UE and UTRAN traces. The drive tests could be performed with Long AMR calls in mobility condition Choose a road with 3G coverage holes and obviously under two different frequencies coverage The following KPIs should be monitored Number of call drops Total drops Drops in CM Drops due to HHO failure Drops due to CM reconfiguration Number of inter-RAT HHO and inter-RAT HHO success rate Number of inter-freq HHO and inter-freq HHO success rate Number of 3a MR followed per 2b MR Radio conditions at MR3a report (CPICH RSCP & Ec/No and UE Tx power) Number of 2b MR followed by 3a MR Radio conditions at MR2b report (CPICH RSCP & Ec/No and UE Tx power) CM time ratio (time spent in CM) Number of CM activations Radio conditions at CM activation (CPICH RSCP & Ec/No and UE Tx power) Number of CM deactivations Radio conditions at CM deactivation (CPICH RSCP & Ec/No and UE Tx power) Number of CM pattern reconfiguration Mean time between CM activation and first measurement on 2G cells % of 3a MR to add a 2G cell that doesnt have the best RSSI.
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authoriziation from Alcatel. 3DF 01900 0000 PTZZA DIAMS
ED
01
RELEASED 01
028 60/61
5 HARD HANDOVER FROM 3G TO 2G FOR AMR AND CS14.4

Inter-RAT HHO can be performed based on UE preliminary radio level measurements of current cell(s), target cell, or both or none. In connected mode, inter-RAT measurements are possible with compressed mode feature. UE equipped with dual receiver do not need compressed mode to measure inter-RAT cells. Radio measurements are performed on: Current cell only WHY? Dangerous degradation of the current radio link(s). WHEN? UE is not equipped with dual receiver and compressed mode is not supported by UE or not configured by UTRAN, Or UE was not able to measure and report a satisfying cell in time. WHAT? Blind Radio Hard Handover=Emergency Hard Handover. Both current and target cell WHY? Degradation of the current radio link(s). WHEN? UE is equipped with dual receiver or compressed mode is supported by UE and UTRAN (from R3) and is configured, And UE measures and reports a satisfying cell in time. WHAT? Radio Hard Handover. Target cell only WHY? To force given RABs to switch to another network (for instance AMR calls may be handover to 2G to save resources on 3G). WHEN? UE is equipped with dual receiver, or compressed mode is supported by UE and UTRAN (from R3) and is configured, And UE measures and reports a satisfying cell. WHAT? Service Hard Handover. None WHY? To force given RABs to switch to another network (for instance AMR calls may be handover to 2G to save resources on 3G). WHEN? Compressed mode is not supported or configured, HHO occurs at the very beginning of the call. WHAT? Blind Service Hard Handover. The figure below illustrates the different cases:
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authoriziation from Alcatel. 3DF 01900 0000 PTZZA DIAMS
ED
01
RELEASED 01
028 59/61
On bad radio conditions With current cell measurement without target cell measurement Blind radio hho =emergency hho
For service reasons Without current cell measurement

Blind service hho
with target cell measurement dual receiver or compressed mode required
Radio hho
Service hho
Figure 9: different types of HHO
5.1 MANAGEMENT OF 3G TO 2G HHO CONFIGURATION BY RNC

Different types of HHO as represented in Figure 10 are triggered by the following RRC events:
On bad radio conditions With current cell measurement without target cell measurement 2d_em
For service reasons Without current cell measurement
None, hho occurs right after call establishment 3c 2d_em in case
with target cell measurement dual receiver
3a 2d_em in case
with target cell measurement compressed mode required
2d_cm 2d_em in case while cm activated : 2f, 3a
3c 2d_em in case cm is activated at call establishment
Figure 10: compressed mode and HHO management by RRC events RNC is in charge of configuring adequate measurements depending on: Parameters BlindHORadio, BlindHOService, EmergencyHO IE Service Handover set in RAB ASSIGNMENT REQUEST (RANAP) set by CN UE capabilities UE context
ED
01
RELEASED 01
028 60/61
5.1.1 PARAMETERS BLINDHORADIO, BLINDHOSERVICE, EMERGENCYHO

Parameter BlindHORadio
Comment This parameter enables to activate the blind handover radio option. 'This parameter enables to BlindHOService activate the blind handover service option. EmergencyHO Activation of the emergency handover option in order to face dead zone situation. For UE supporting GSM, this parameter gives a priority to the UMTS or the GSM emergency cell.
Domain Range Network On/Off Network On/Off Network GSM, UMTS, None
Step No No
Access RNO RNO RNO
Example Off Off None
BlindHORadio
When the BlindHORadio is set to ON, and the EmergencyHO is set to GSM, only emergency inter RAT blind HHO is configured, if there is a GSM emergency cell, without measurements on the 2G target cell. When the BlindHORadio is set to OFF, and the EmergencyHO is set to none, only inter-RAT hard-handover is configured, with measurements on inter RAT target cell. When the BlindHORadio is set to OFF, and the EmergencyHO is set to GSM, both inter-RAT hard-handover are configured: with and without measurements on inter RAT target cell. Alcatel recommends deactivating the Blind HHO to take profit from the CM and try to make some measurements on 2G cells in order to perform the HHO towards the best cell. Otherwise, if the emergency HO is activated, the UE could perform an emergency HO in case of fast degradation of radio conditions. So the BlindHORadio flag is set to Off. In this case, the mobile will try to measure the target cell before triggering the HHO. And if the radio conditions are degraded quickly and the mobile doesnt have enough time to perform those measurements, the UE can report a MR 2d_em to trigger an emergency handover towards a 2G emergency cell if the EmergencyHO is set to GSM.
BlindHOService
This parameter enables to activate the blind handover service option. ALCATEL recommends deactivating this option as the actual operators strategy is to keep the user under 3G coverage. The BlindHOservice flag is recommended to be set to OFF.
EmergencyHO
According to field experience, the activation of the Emergency handover for intre-RAT, degrades the system performances and increases significantly the ratio of AMR calls handed over to GSM whereas the operators strategy is to keep the 3G users under 3G coverage as long as possible. Nevertheless, this feature could be helpful for specific cells presenting high inter-frequency HO failure rate and radio drop rate. These cells are identified based on RNO KPIs and the emergency cells should be defined carefully taking into account the radio environment of the source cell.
To activate emergency HHO only on certain cells: EmergencyHO is a network parameter that should be set to UMTS, some cells have inter-RAT emergency neighbours, and some cells dont If EmergencyHO is set to UMTS, emergency HHO is either inter-freq, or intra-freq without Iur (out of the scope of this document). ED 01 RELEASED 01 028 59/61
IE Service Handover
It is set in RAB ASSIGNMENT REQUEST (RANAP) by CN This IE tells if intersystem handover to GSM should, should not, or shall not be performed for the RAB in question. Possible values: should, should not, shall not or none Recommended values are:
AMR Should/ Should not CS 14.4 Should/Should not CS 14.4 Should not CS 64 Shall not PS RAB Shall not

CS
when IE is set to none, RNC behaves as if IE was set to:

Should not CS 64 Should not PS RAB Shall not
AMR
Multi-RAB: from IE Service Handover received for CS RAB and from IE Service Handover received for PS RAB, the RNC computes a resulting IE, with the following rules:
IE Service Handover in case of multi-RAB PS CS+PS None/Should/Should not Shall not Shall not CS 14.4+PS Should not CS 14.4+PS Should not CS 64+PS Shall not CS 64+PS Should not IE received for CS Should not Shall not None/Should/Should not/Shall not None/Should/Should not Shall not
When recommended values are set, it results in: When IE is set to none, it results in: Single PS RAB, the RNC will use the value shall not in the algorithm, whatever the value of IE service handover sent by the CN
AMR+PS Should not AMR+PS Should not
5.1.2 UE CONTEXT: INTER-RAT MONITORED CELL LIST

In the UE context, RNC stores the list of Active Set cells and Monitored Set cells. A 3G cell may have up to 12 Inter-RAT cells (2G) as adjacent cells in R3. Among these 12 cells, 1 cell may be flagged as emergency cell. Parameter Comment Domain Range Step Access Example Max_GSM_cells Maximum number of GSM Network 0 to 12 1 RNO 12 cells that a UE has to monitor. BlindHOinterRA Index of inter RAT Tid neighbour in case of blind HHO Cell Design 0 to 11 1 RNO 1
ED
01
RELEASED 01
028 60/61
Max_GSM_cells
This parameter is used by the RNC to define the list of 2G neighbour cells to monitor by the UE. It defines the maximum number of 2G cells in the monitored set.
In R3, the maximum value for Max_GSM_cells is 12 but the CM patterns are configured depending on the inter-RAT monitored set size. The larger the 2G monitored set size, the higher is the compressed mode time ratio which means higher radio resources consumption. ALCATEL recommend to set the Max_GSM_cells to 12 and to limit the number of declared 2G adjacent cells. We can rely on RNO counters to delete the adjacencies without HHO traffic.. If each 3G cell has 12 2G neighbour cells, the monitored set of the UE will be constituted of the 2G neighbour cells of the oldest 3G cell in its active set.
BlindHOinterRATID
This parameter is used to flag the 2G neighbour cell to use as emergency cell in case of emergency inter-RAT HHO. The emergency cell should be chosen carefully taking into account the RNO inter-RAT HHO traffic indicators and the network topology.
5.2 UE MEASUREMENTS FOR TRIGGERING 3G TO 2G HHO

Radio measurements are configured by RNC through downlink RRC Measurement Control (MC) which contains: Measurement ID, Measurement command (setup, modify or release), Event type and associated parameters. Measurements Reports (MR) can be either periodical or event triggered; only event triggered are involved in HHO and compressed mode algorithms. When conditions are fulfilled, UE sends uplink RRC Measurement Report, which contains the Measurement id registered from Measurement Control. Events involved are: 2d_cm, 2d_em and 2f, which require measurements on the current FDD frequency, they are described in 4.2 UE measurements for triggering of HHO between 3G carriers. 3c, which requires measurements on 2G cells, 3a, which requires both measurements on the current FDD frequency and 2G cells
5.2.1 UTRAN FREQUENCY QUALITY ESTIMATE

Parameter Comment InterRAT.FilterCoeffi Defines the filter cient coefficient that shall be used to evaluate the Inter RAT measurements. InterRAT.Measureme The measurement Networ CPICH ntQuantityEstimate quantity for UTRAN is k Ec/N0, used to compute the CPICH RSCP frequency quality estimate for the active set before triggering an Inter RAT event. Networ Range k Networ 0,1,2,3,4,5, k 6,7,8,9,11,1 3,15,17,19 Step enum Access RNO Example 2
enum
RNO
CPICH RSCP
InterRAT.MeasurementQuantityEstimate
This parameter defines the measurement quantity to be used by the UE to evaluate the inter RAT events. So its used in all 3x events using measurements on the active frequency. Event 3a : inter RAT radio HHO
ED
01
RELEASED 01
028 59/61
Event 3c : inter RAT service HHO not impacted as there is no measurements on the active frequency
The recommended value is CPICH Ec/No. However, the CPICH RSCP could be better in specific areas where the CPICH RSCP is the limiting criteria (i.e degradation of CPICH RSCP whereas the CPICH Ec/No stays at quite good level). This is the case for 3G coverage border cells boundary cells between two 3G areas operating on two different frequencies. To determine the right criterion, we should perform a coverage test in the involved area to collect CPICH RSCP and Ec/No measurements and then, based on measurements analysis one could choose the limiting criterion as follow: Fix a limit threshold for RSCP (e.g. 105dBm) Fix a limit threshold for CPICH Ec/No (e.g. 12dB) Compute the percentage of samples for which the CPICH RSCP is under the limit threshold whereas the CPICH Ec/No is above the limit threshold (% RSCP limitation) Compute the percentage of samples for which the CPICH Ec/No is under the limit threshold whereas the CPICH RSCP is above the limit threshold (% Ec/No limitation) If the % RSCP limitation is higher then set the criterion to CPICH RSCP If the % Ec/No limitation is higher then set the criterion to CPICH Ec/No Note that in R3 this parameter is configurable per RNC and not per cell class. On dense networks, the system performances, in term of call drop rate as well as inter-RAT HHO ratio and success rate, were improved by changing the criterion from RSCP to Ec/Io. We can also rely on RNO counters to evaluate the best criterion by testing the both settings (on an experimental area if possible) and compare the corresponding performances based on System call drop rate Ratio of AMR calls handed over to GSM Inter-RAT HHO success rate
InterRAT.FilterCoefficient
Refer to InterFreq.FilterCoefficient.
5.2.2 COMPRESSED MODE ACTIVATION: EVENT 2D_CM, EMERGENCY HHO: EVENT 2D_EM
Refer to 4.2.3 Compressed mode activation: event 2d_cm, emergency HHO: event 2d_em.
5.2.3 COMPRESSED MODE DEACTIVATION: EVENT_2F

Refer to 4.2.4 Compressed mode deactivation: event_2f.
5.2.4 RADIO INTER-RAT HHO: EVENT 3A

Event 3a: The estimated quality of the currently used UTRAN frequency is below a certain threshold and the estimated quality of the other system is above a certain threshold. Parameter Comment Domain Range Step Access Example Event3A.Thresh Threshold for the used Network -115 to 0 1 RNO -100 oldOwnSystem UMTS frequency (source dBm cell). the range -115dBm to -25dBm is used with CPICH RSCP and the range -24dB to 0dB is used with CPICH Ec/N0. Event3A.Thresh Offset added to threshold Downlink 0 to 115 1 RNO oldOffset for inter-RAT handover. Physical dB 0 dB for Introduced in R3 MR3 Channel AMR ED 01 RELEASED 01 028 60/61
Event3A.Hystere sis GSMneighbours offset added to GSM RSSI CellIndividualOff before the UE evaluates if set an event has occurred. Event3A.Thresh Threshold for the other oldOtherSystem system (target cell) Event3A.TimetoT rigger
Network External GSM Cell design Network Network
0 to 7.5 dB -50 to 50 dB
0.5 1
RNO RNO
0 dB 0 dB
Event3A.W
Weighting factor
Network
-115 to 0 dBm 0,10,20, 40,60,80 ,100,120 ,160,200 ,240,320 ,640,128 0,2560,5 000 0 to 2
1 enum
RNO RNO
-100 dBm 0 ms
0.1
RNO
Event3A.ThresholdOwnSystem
This Network parameter is added to the Event3A.ThresholdOffset to define the event 3a threshold for 3G active set per service. The range -115 to -25 dBm is used with CPICH RSCP and the range -24 to 0 dB with CPICH Ec/N0. as the measurement quantity is set to Ec/No, the Event3A.ThresholdOwSystem is set to 24dB and then the offset is tuned per service. This configuration make it possible to deactivate the inter-RAT HO for a specific services just by setting the offset to 0 (the Event3A.ThresholdOffset is set in the range [0..50]).
Event3A.ThresholdOtherSystem
This parameter defines the event 3a threshold for 2G target cells per service. The recommended value is 95dBm which mans that the call will perform HHO to 2G only when the RSSI of the target cell is higher than 95dBm.
Event3A.ThresholdOffset
This Downlink Physical Channel parameter was introduced in R3MR3 to customize the event 3a threshold per service. For AMR we set the offset so that the event 3A threshold for own system is 1dB lower than event 2D threshold for compressed mode activation. The recommended value for AMR is 12dB. For PS384kbps the offset is set 2dB higher compared to AMR, as it requires higher quality. And for PS384, the cm activation is 1 dB higher than cm activation for AMR, so =-10 dB. For other PS bearers, we recommend to set the offset to the same value as AMR. High offset values will increase the HHO ratio. Low offset values allow to keep the call longer in 3G layer but it increases the call drop ratio as the 3a event is triggered lately and the UE is not able to receive correctly the HHO command as the radio conditions are degraded. The inter RAT preparation procedure (between event 3A triggering and HHO command) takes 1.4s in average. One should take into account also the UEs with dual receivers that dont need compressed mode. In R3/R4, the only way to evaluate the part of 3G mobiles with dual receiver is through Iub/Iu traces. Additional RNO indicators are requested for R6 to follow the part of these mobiles.
Event3A.W
This parameter is a weighting factor used to compute the measurement quantity for the used frequency before event 3A evaluation. ED 01 RELEASED 01 028 59/61
The recommended value is 0 to take into account only the best cell on the used frequency.
Event3A.Hysteresis
This parameter defines an hysteresis for event 3A criterion. The recommended value is 0dB.
Event3A.TimetoTrigger
This is the time during which the event 3A criterion should be fulfilled before reporting the event 3A measurement report RRC message. The default value is 0ms to speed up the inter-RAT HHO procedure. However, if we want to get more accurate measurements on the target 2G cells, we should set the TTT to a non-null value to let the UE check the criterion on more than one measurement. And as the measurement period for inter-RAT is 480ms, we should set the TTT so that: TTT>(N-1)*480ms Where N is the number of measurement the UE has to check for inter-RAT criterion. For example, if we want check the criterion on 2 inter-RAT measurements, we have to set the TTT to 640ms.
GSMneighboursCellIndividualOffset
Offset added to GSM RSSI before the UE evaluates if an event has occurred. This parameter enables the operator to prioritise a specific 2G cell for HHO. The recommended value is 0.
5.2.5 SERVICE INTER-RAT HHO: EVENT 3C

Event 3c: The estimated quality of other system is above a certain threshold. ALCATEL recommends to deactivate this option through the service handover parameter configured at the CN side (refer to ).This option could be activated if the 3G network would be overloaded. The operators prefer to keep their customers on the 3G network for all the services, while the traffic is still reasonable. Parameter Event3C.Hysteresis Comment Domain Network Range 0 to 7.5 dB Network -115 to 0 dBm Network 0,10,20,4 0,60,80,1 00,120,1 60,200,2 40,320,6 40,1280, 2560,500 0 Step 0.5 1 enum Access RNO RNO RNO Example 0 dB -95 dBm 0 ms
Event3C.Threshold Threshold for the OtherSystem other cell Event3C.TimetoTrig ger
Event3C.Hysteresis
This parameter defines an hysteresis for event 3C criterion. The recommended value is 0dB.
ED
01
RELEASED 01
028 60/61
Event3C.ThresholdOtherSystem
This parameter defines the event 3c threshold for 2G target cells per service. The recommended value is 95dBm, which means that the call will perform HHO to 2G, only when the RSSI of the target cell is higher than 95dBm.
Event3C.TimetoTrigger
This is the time during which the event 3C criterion should be fulfilled before reporting the event 3C measurement report RRC message. The default value is 0ms to speed up the inter-RAT HHO procedure. However, if we want to get more accurate measurements on the target 2G cells, we should set the TTT to a non-null value to let the UE check the criterion on more than one measurement. And as the measurement period for inter-RAT is 480ms, we should set the TTT so that TTT>(N-1)*480ms Where N is the number of measurement the UE has to check for inter-RAT criterion. For example, if we want to check the criterion on 2 inter-RAT measurements, we have to set the TTT to 640ms. Moreover, there is no degradation of the 3G cell in that particular event, and no emergency to perform the HHO.

In RNO, we can monitor the number of compressed mode activation and the number of compressed mode deactivation for both inter-frequency and inter-RAT HHO. But, we have a global indicator for all services, therefore, we cant distinguish for example the volume of compressed mode activation for AMR inter-frequency HHO and CS64 or PS inter-frequency HHO. For inter-RAT HHO, as the CCO is not supported in R3, all the inter-RAT compressed mode activations correspond to AMR HHO. Indicator Compress_mod_inter_RAT_act_r equest_ratio Compress_mod_inter_RAT_desa ct_request Inter_RAT_AMR_12_2k_request Inter_RAT_AMR_12_2k_success Description This indicator reports the ratio of compressed mode activations for inter-RAT measurements during the measurement period. This indicator reports the number of compressed mode deactivations for inter-RAT measurements during the measurement period. This indicator reports the number of requests for interfrequency handover initiated by RNC for UE supporting a AMR RAB per couple of cells. This indicator reports the number of successes for interfrequency handover initiated by RNC for UE supporting a AMR RAB per couple of cells.
Based on these indicators we can monitor the following KPI for inter-RAT: HHO success rate Ratio of AMR drops caused by HHO failure (number of HHO failure/number of AMR system drops) Inter-RAT CM activation per user Ratio of Inter-RAT CM deactivation (over inter-RAT CM activation) CM efficiency (CM activation to inter-RAT HHO request ratio) Ratio of AMR calls handed over to 2G Ratio of AMR calls ended in CM (number of CM act - number of CM deact - number of HHO success)
ED
01
RELEASED 01
028 59/61
These indicators aim at monitoring the CM and inter-RAT HHO performances and at tuning the CM and inter-RAT HHO parameters (i.e. thresholds and time-to-trigger for event 2d, event 2f and event 3a). As there is no RNO indicator for CM time duration, some drive tests with UE and UTRAN traces are required to analyze the CM patterns performances with more details.
The RNO indicator for HHO success rate takes into account the failures in 2G BSS and CN. So it is useful to use CN indicators or Iu traces to determine the part of HHO failures due to CN or 2G problems. Additional RNO counters are requested for R6 to follow-up these failures. Moreover, for AMR, we should correlate the inter-frequency performances to the inter-RAT ones. One can monitor for example Inter-RAT HHO to inter-freq HHO ratio. It can give an idea on the difference between event 2b and event 3a thresholds. Total CM activations per AMR call (as the event 2d is common to both HHO types). Its also recommended to perform some drive tests in the involved area taking UE and UTRAN traces for deeper analysis.
How to use RNO KPI for HHO parameters tuning

Here after an example of inter-RAT HHO performances monitoring based on RNO KPIs. These tests were performed on ORANGE FRANCE experimental network.
HHO parameters
HHO 3G-2G
Default Applied on criterion Event2F.Threshold Event2D.ThresholdCMactivation Event3A.Threshold Event2d_CM.TimetoTrigger Event3A.TimetoTrigger Event2F.TimetoTrigger CMPattern.TGCFN.Initial BSIC identification pattern CMPattern.TGCFN.BSIC reconfirmation pattern Event1b.TimeToTrigger intrafreq.Filter coefficient interfreq.Filter coefficient InterRAT.FilterCoefficient Ec/No -8 -10 -12 0 640ms 240ms 12 20 240ms 5 5 5 Set 1 09/ 06/2005 Ec/No -8 -10 -12 640ms 0ms 640ms 12 20 320ms 4 2 2 Set 2 14/06/ 2005 Ec/No -10 -12 -12 640ms 0ms 640ms 12 20 320ms 4 2 2 Set 3 17/ 06/2005 Ec/No -9 -11 -12 640ms 0ms 640ms 12 20 320ms 4 2 2 Set 4 23/06/ 2005 Ec/No -10 -12 -12 120ms 0ms 640ms 12 20 320ms 4 2 2 set 5 30/06/ 2005 Ec/No -9 -11 -12 640ms 0ms 1280ms 228 236 320ms 4 2 2 set 6 06/07/ 2005 Ec/No -8 -11 -12 640ms 0ms 640ms 108 116 320ms 4 2 2
RNO KPI analysis

The HHO performances analysis are based on the following RNO KPIs: System call drop rate AMR radio call drop rate Inter RAT HHO success rate Number of HHO requests per AMR call: inter-RAT HHO requests/AMR call setup success Number of HHO success per AMR call: inter-RAT HHO success/AMR call setup success CM deactivation to CM activation ratio: inter-RAT CM termination/inter-RAT CM activation CM activation per AMR call: CM activation/AMR call setup success CM non deactivated per AMR call: (CM activation-CM termination)/AMR call setup success
ED
01
RELEASED 01
028 60/61
Ratio of AMR calls ended in CM: (CM activation-CM termination-HHO success)/AMR call setup success
These KPI were monitored based on daily RNO reports:

100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0%
set1
set2
set3
set4
set5
set6
16% 14% 12% 10% 8% 6% 4% 2% 0%
05
ratio CM non deactiv vs AMR call
Default set
With default HHO parameters the system performances were unsatisfying: The system call drop was around 4% High CM activation ratio per AMR call High ratio of non deactivated CM and AMR calls ended in CM Ping-pong effect between CM activation and CM deactivation These results are explained by the parameters values: as the time-to-trigger is set to CM is activated, as soon as the CPICH Ec/No drops below the activation threshold measurement) and in case of fading, the CM is activated, whereas the average signal still above the activation threshold. This behavior leads to a high CM activation ratio ratio of AMR calls ended in CM. 0ms, the (just one quality is and high
We notice also that the time-to-trigger for event 2F is low and the hysteresis between event 2d and event 2f thresholds is not high enough to avoid ping-pong effect between CM activation and deactivation. At the same time, the time-to-trigger for event 3a is set to 640ms, which reduces the HHO reactivity in case of fast degradation of radio conditions.
ED
01
RELEASED 01
20 05 06 /1 1/ 20 06 05 /1 3/ 20 05 06 /1 5/ 20 05 06 /1 7/ 20 05 06 /1 9/ 20 05 06 /2 1/ 20 05 06 /2 3/ 20 05 06 /2 5/ 20 05 06 /2 7/ 20 05 06 /2 9/ 20 05 07 /0 1/ 20 05 07 /0 3/ 20 05 07 /0 5/ 20 05 07 /0 8/ 20 05 07 /1 0/ 20 05
05
05
/0 3/
05 /
/0 7/
20
20
20
06 /
06
06
06
/0 9/
06 /0 2/ 06 200 /0 4/ 5 06 200 /0 6/ 5 06 200 /0 8/ 5 06 200 /1 5 0/ 06 200 /1 2/ 5 06 200 /1 4/ 5 06 200 /1 6/ 5 06 200 /1 5 8/ 06 200 /2 0/ 5 06 200 /2 2/ 5 06 200 /2 4/ 5 06 200 /2 5 6/ 06 200 /2 8/ 5 06 200 /3 0/ 5 07 200 /0 2/ 5 07 200 /0 5 4/ 07 200 /0 7/ 5 07 200 /0 9/ 5 07 200 /1 1/ 5 20 05
HO_suc_3G_2G_r(%) ratio HHO req vs AMR call
CM deactiv vs CM activ (%) ratio HHO success vs AMR call
ratio CM activ vs AMR call
Figure 11 RNO KPI for CM and HHO tuning

set1
25% 20% 15% 10% 5% 0%
set2
set3
set4
set5
set6
ratio call ended in CM vs AMR call
Figure 12 RNO KPI for HHO tuning
028 59/61
Tuning on time to trigger

In the set1, we modify the time to trigger for event 2d, 2f and 3a: For event 2d, it is increased from 0 to 640ms to avoid CM activation incase of fast fading holes. For event 2f, it is also increased from 240 to 640ms to reduce ping-pong effect. For event 3a, it is reduced to 0ms, in order to increase the system reactivity in case of fast degradation of radio conditions. The results after application of set1 are as expected and visible through RNO KPIs Fewer CM activations per AMR call Less ping-pong between CM activation and deactivation Decrease of number of AMR calls ended in CM We notice that the ratio of AMR calls handed over to 2G is increased. As the ratio of nondeactivated CM per AMR call is the same (before and after set1 application), we can say that this increase corresponds to the HHO attempts that failed before due to event 3a delay (TTT for e3a at 640ms) and that succeed after set1 application thanks to TTT reduction.
Tuning on HHO thresholds

In set2, we reduced the event2d and event2f thresholds. We set the event 2d to the same value as event 3a threshold and the idea behind is to reduce the CM time duration and to trig the HHO as soon as the CM is activated (obviously after the first measurements on 2G neighboring cells). According to RNO KPI: As expected, the CM activation ratio per AMR call is reduced by half Less ping-pong between CM activation and deactivation The number of calls ended in CM is strongly reduced However, the system call drop is increased and the ratio of AMR calls handed over to 2G is decreased. These results can be explained by the CM activation delay as in case of fast degradation of radio conditions, if we delay the activation of CM till 12dB, on top of 640ms TTT, the mobile doesnt have enough time to perform 2G measurements and report 3a event in good radio conditions. This hypothesis was confirmed by the trace on drive tests.
System reactivity: TTT vs. threshold

To reduce the ping-pong effect between CM activation and deactivation, we tested two solutions: Increase the TTT for event 2f (time hysteresis) ---> set5 Increase the event 2f threshold (signal quality hysteresis) ---> set6 RNO KPI show that the system is more reactive to threshold modification compared to time-totrigger. Indeed, the CM deactivation to CM activation ratio is 10% lower with set6 (event 2f threshold increase of 1dB) than with set 5 (event 2f TTT set to 1280ms instead of 640ms).
5.3.2 DRIVE TESTS AND UTRAN TRACES

UE and UTRAN traces are recommended for CM patterns performances analysis. Moreover, the field tests showed that the CM and HHO performances are UE dependent so it will be very helpful to benchmark the most used UE via UE and UTRAN traces. The drive tests could be performed with Long AMR calls in mobility condition Choose a root with 3G coverage holes and obviously under two different frequencies coverage The following KPIs should be monitored Number of call drops Total drops Drops in CM Drops due to HHO failure ED 01 RELEASED 01 028 60/61
Drops due to CM reconfiguration Number of inter-RAT HHO and inter-RAT HHO success rate Number of inter-freq HHO and inter-freq HHO success rate Number of 3a MR followed per 2b MR Radio conditions at MR3a report (CPICH RSCP & Ec/No and UE Tx power) Number of 2b MR followed by 3a MR Radio conditions at MR2b report (CPICH RSCP & Ec/No and UE Tx power) CM time ratio (time spent in CM) Number of CM activations Radio conditions at CM activation (CPICH RSCP & Ec/No and UE Tx power) Number of CM deactivations Radio conditions at CM deactivation (CPICH RSCP & Ec/No and UE Tx power) Number of CM pattern reconfiguration Mean time between CM activation and first measurement on 2G cells % of 3a MR to add a 2G cell that doesnt have the best RSSI.
For end-to-end performances we can also add the following indicators HHO preparation time duration HHO execution time duration
ED
01
RELEASED 01
028 59/61
6 CROSS-REFERENCES OF RNO PARAMETERS

In this chapter, the parameters in the tables of CCT and Cell Design in RNO are linked to the description of algorithms of this document.
6.1 CCT NETWORK CONTROL

Network Control BlindHORadio BlindHOService EmergencyHO CMPattern.DeltaSIR1 CMPattern.DeltaSIRafter1 CMPattern.NidentifyAbort CMPattern.TGCFN CMPattern.TGL1 CMPattern.TGPL1 CMPattern.TreconfirmAbort SfreductionMethodThreshold Event2B.Hysteresis Event2B.ThresholdnonUsedFrequency Event2B.ThresholdUsedFrequency Event2B.TimetoTrigger Event2B.WnonUsedFrequency Event2B.WusedFrequency Event2D.Hysteresis Event2D.ThresholdCMactivation Event2D.TimetoTrigger Event2D.WusedFrequency Event2D.ThresholdEmergencyHandover Event2F.Hysteresis Event2F.ThresholdUsedFrequency Event2F.TimetoTrigger Event2F.WusedFrequency Event3A.Hysteresis Event3A.ThresholdOtherSystem Event3A.ThresholdOwnSystem Event3A.TimetoTrigger Event3A.W Event3C.Hysteresis Event3C.ThresholdOtherSystem Event3C.TimetoTrigger FACHMeasurementOccasionCycleLengthCoeffi cient FACHMeasurementOccasionCycleLengthCoeffi cientFlag InterFreq.FilterCoeficient InterFreq.MeasQuantOwnFreq InterRAT.FilterCoefficient ED 01 RELEASED 01 Reference 5, 3.8 5 5, 3.8 3.1 3.1 3.1 3.1 3.1 3.1 3.1 3.1 4.2.2 4.2.2 4.2.2 4.2.2 4.2.2 4.2.2 4.2.2 4.2.2 4.2.2 4.2.2 4.2.2 4.2.4 4.2.4 4.2.4 4.2.4 5.2.4 5.2.4 5.2.4 5.2.4 5.2.4 5.2.5 5.2.5 5.2.5 1.4.2 1.4.2 4.2.1 4.2.1 5.2.1 Related algorithms Hard Handover Hard Handover Hard Handover Compressed Mode Compressed Mode Compressed Mode Compressed Mode Compressed Mode Compressed Mode Compressed Mode Compressed Mode Hard Handover Hard Handover Hard Handover Hard Handover Hard Handover Hard Handover Hard Handover, Compressed Mode Compressed Mode Hard Handover, Compressed Mode Hard Handover, Compressed Mode Hard Handover Compressed Mode Compressed Mode Compressed Mode Compressed Mode Hard Handover Hard Handover Hard Handover Hard Handover Hard Handover Hard Handover Hard Handover Hard Handover UE measurements in cellFACH UE measurements in cellFACH Hard handover UE measurements Hard handover UE measurements Hard handover UE 028 60/61
Network Control
Reference
InterRAT.MeasurementQuantityEstimate
5.2.1 3.8 3.8 5
Related algorithms measurements Hard handover UE measurements Hard handover Hard handover Hard handover
MaxFDDcarriers MaxFDDcells MAXGSMcells
6.2 CCT CELL CONTROL

Cell Control CellSelect&ReselectQualMeas RATList.SSearchRAT SinterSearch SinterSearchFlag SintraSearch SintraSearchFlag Treselection Reference Related algorithm Cell re-selection Cell re-selection evaluation Cell re-selection evaluation Cell re-selection evaluation Cell re-selection evaluation Cell re-selection evaluation Cell re-selection
1.3 1.3 1.3 1.3 1.3
6.3 CCT PHYSICAL AND LOGICAL CHANNELS

Uplink Physical Channel Downlink Physical Channel Event2B.ThresholdOffset (from R3 MR3) Event2Dcm.ThresholdOffset (from R3 MR3) Event2Dem.ThresholdOffset (from R3 MR3) Event2F.ThresholdOffset (from R3 MR3) Event3A.ThresholdOffset (from R3 MR3) Logical Channel References References 4.2.2 Algorithms Algorithms Hard Handover
4.2.2 4.2.2 4.2.4 5.2.4 References
Compressed Mode Hard Handover Compressed Mode Hard Handover Algorithms
6.4 CCT TRAFFIC MANAGEMENT

Traffic Management References Algorithms
6.5 DESIGN
In the following table, parameters for cell identification (CellId, LocalCellId, SAC, RAC, LAC, MCC, MNC, Cell Class, Scrambling code, etc.) and antenna settings (height, azimuth, etc.) are not included. Cell Design References Algorithms BlindHOinterFrequencyID ( ) 3.8 Hard Handover ED 01 RELEASED 01 028 59/61
6.5.1 CELL DESIGN
Cell Design BlindHOinterRATid ( ) Qhysts1 Qhysts2 QqualMin QrxlevMin MaxAllowUlTxPower
References 5
1.1 1.1 1.1
Algorithms Hard Handover Cell re-selection Cell re-selection Cell selection, Cell reselection Cell selection, Cell reselection Cell selection, Cell reselection
6.5.2 ADJACENCY DESIGN

Qoffset_sn Qoffset2_sn 1.5 1.5 Cell reselection Cell reselection
6.5.3 ADJACENCY GSM DESIGN

Qoffset_snGSM 1.5 Cell reselection
6.5.4 RNC GSM EXTERNAL CELL DESIGN

GSMQrxlevmin GSMMaxAllowULTxpower GSMneighboursCellIndividualOffset 1.5 1.5 5.2.4 Cell reselection Cell reselection Hard Handover
ED
01
RELEASED 01
028 60/61
INDEX
BlindHOinterFrequencyID..................................38
Event3C.Hysteresis...........................................56 Event3C.ThresholdOtherSystem........................57 Event3C.TimetoTrigger......................................57 FACH Measurement Occasion Cycle length........11 FACH Measurement Occasion Infor FLAG...........11 FACHMeasurementOccasionCycleLengthCoefficie ntFlag............................................................11 FDD_ARFCN_LIST...............................................22 FDD_GPRS_Qoffset............................................20 FDD_Qmin.........................................................19 FDD_Qoffset......................................................20 GSMMaxAllowUlTxPower....................................16 GSMneighboursCellIndividualOffset...................56 GSMQrxlevmin...................................................16 IE Service Handover........................................52 Initial Transmit Power........................................31 InterFreq.FilterCoefficient..................................39 InterFreq.MeasQuantOwnFreq...........................39 InterRAT.FilterCoefficient...................................54 InterRAT.MeasurementQuantityEstimate...........53 Max_FDD_carriers..............................................38 Max_FDD_cells..................................................38 Max_GSM_cells..................................................53 MaxAllowULTxPower............................................6 NC2_DEACTIVATION_MODE................................22 NETWORK_CONTROL_ORDER............................22 Qhysts1.............................................................14 Qhysts2.............................................................15 Qoffset_sn.........................................................15 Qoffset_snGSM..................................................16 Qoffset2_sn.......................................................15 Qqualmin............................................................5 Qrxlevmin............................................................5 Qsearch_I..........................................................18 Qsearch_P.........................................................18 Recovery Period Power control mode.................31 SF_reduction_method_threshold........................25 SinterSearch........................................................8 SinterSearchFlag.................................................8 SintraSearch........................................................8 SintraSearchFlag.................................................8 SsearchRAT.........................................................8
BlindHOinterRATID.............................................53 BlindHORadio..............................................37, 51 BlindHOService.................................................51 Cell Selection and reselection quality measure. 14 CMPattern.DeltaSIR1.........................................30 CMPattern.DeltaSIRafter1..................................30 CMPattern.NidentifyAbort..................................30 CMPattern.TGCFN..............................................27 CMPattern.TGL1.................................................27 CMPattern.TGPL1...............................................27 CMPattern.TreconfirmAbort................................30 Downlink frame type.........................................31 DRX cycle..........................................................10 DRX Cycle...........................................................7 EmergencyHO.............................................37, 51 EN_2G_TO_3G_CELL_RESELECTION...................22 Event2A.ThresholdOwnSystem..........................55 Event2B.Hysteresis...........................................42 Event2B.ThresholdnonUsedFrequency...............41 Event2B.ThresholdOffset...................................41 Event2B.ThresholdUsedFrequency....................41 Event2B.TimetoTrigger......................................42 Event2B.WnonUsedFrequency...........................42 Event2B.WusedFrequency.................................41 Event2D.Hysteresis...........................................44 Event2D.ThresholdCMactivation........................43 Event2D.ThresholdEmergencyHandover...........43 Event2D.TimetoTrigger......................................44 Event2D.WusedFrequency.................................44 Event2Dcm.ThresholdOffset..............................43 Event2Dem.ThresholdOffset..............................43 Event2F.Hysteresis............................................46 Event2F.ThresholdOffset....................................45 Event2F.ThresholdUsedFrequency.....................45 Event2F.TimetoTrigger.......................................46 Event2F.WusedFrequency..................................46 Event3A.Hysteresis...........................................56
Event3A.ThresholdOffset...................................55 Event3A.ThresholdOtherSystem........................55 Event3A.TimetoTrigger......................................56 Event3A.W.........................................................55
ED
01
RELEASED 01
028 59/61
TGPRC...............................................................29 TGSN.................................................................27
Treselection.......................................................16
END OF DOCUMENT
ED
01
RELEASED 01
028 60/61

R3 3G2G Parameters Tuning Ed1

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

R3 3G2G Parameters Tuning Ed1

Încărcat de

Drepturi de autor:

Formate disponibile

All rights reserved.

MOBILE RADIO DIVISION PROFESSIONAL CUSTOMER SERVICES R3 3G-2G Parameter Tuning

RADIO OPTIMISATION 3G METHOD TUNING GUIDELINE Internal: External:

C. MOIGNARD DUMAS PCS/Quality Signature: Date:

LF. GONNOT Signature:

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

3DF 01900 0000 PTZZA DIAMS

2 CELL RESELECTION FROM 2G TO 3G...............................................................18

4 HARD HANDOVER BETWEEN 3G CARRIERS.....................................................36

5 HARD HANDOVER FROM 3G TO 2G FOR AMR AND CS14.4.............................49

6 CROSS-REFERENCES OF RNO PARAMETERS....................................................62

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

6.1 6.2 6.3 6.4 6.5

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

1 CELL RESELECTION FROM 3G TO 2G OR TO ANOTHER 3G CARRIER

1.1 CELL SELECTION CRITERIA

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

1.2 UE MEASUREMENTS ON THE SERVING CELL

1.2.1 IN IDLE STATE

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

1.2.2 IN CELL-FACH STATE

1.3 ALGORITHM FOR TRIGGERING OF UE MEASUREMENTS ON NEIGHBOUR CELL

Access Example RNO On RNO RNO RNO RNO 8 dB On 6 dB 2 dB

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

SintraSearchFlag and SintraSearch

SinterSearchFlag and SinterSearch

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

1.4 UE MEASUREMENTS ON NEIGHBOUR CELLS 1.4.1 IN IDLE STATE

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

Measurements of intra-frequency cells

Measurements of inter-RAT cells

0.08 0.16 0.32 0.64 1.28 2.56 5.12

Table 3: periodicity of inter-RAT measurements in idle according to DRX cycle

Measurements of inter-frequency cells

1.4.2 IN CELL-FACH STATE

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

control 0/1 RNC No ODTB 0

FACH Measurement Occasion Infor FLAG

FACH Measurement Occasion Cycle length

Example with K=3, and NTTI =1:

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

Tmeas = [ ( N FDD + N GSM ) N TTI M_REP 10] ms

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

Table 4: summary of the periodicity of the UE measurements

1.5 CELL RESELECTION CRITERIA

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

Acces Example s RNO -101 dBm

Cell Selection and reselection quality measure

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

3DF 01900 0000 PTZZA DIAMS

MRD R3_3G2G_Parameters Tuning_ed1.doc2006-02-133DF 01906 3311 VAZZA

1.6 RNO INDICATORS AND TRACE ANALYSIS 1.6.1 RNO INDICATORS