Professional Documents
Culture Documents
Lte Parameter Engineering Guidelines
Lte Parameter Engineering Guidelines
Huawei eRAN6
Huawei sRAN7/sRAN8
Huawei BSS14
Huawei RAN 14
3Gpp Rel.8 and above
Huawei Technologies
2 Cell Reselection....................................................................................................................25
2.1 Measurement Start Criteria....................................................................................................25
2.1.1 Intra-frequency Measurement.......................................................................................................25
2.1.1.1 RF Conditions (“S” criteria).............................................................................................25
2.1.1.2 3Gpp vs Huawei Parameters.............................................................................................26
2.1.2 Inter-frequency Measurement........................................................................................................26
2.1.2.1 RF Conditions (“S” criteria).............................................................................................26
2.1.2.2 3Gpp vs Huawei Parameters.............................................................................................27
2.1.3 Inter-RAT Measurement...............................................................................................................28
2.1.3.1 RF Conditions (“S” criteria).............................................................................................28
2.1.3.2 3Gpp vs Huawei Parameters.............................................................................................28
2.2 Measurement Start Criteria Current Network Values............................................................29
2.3 Cell Reselection Criterion......................................................................................................30
2.3.1 Priorities........................................................................................................................................30
2.3.2 Cell reselection and mobility.........................................................................................................32
2.3.2.1 Mobility type detection.....................................................................................................32
2.3.2.2 3Gpp vs Huawei Parameters.............................................................................................33
2.3.2.3 Mobility criterion (scaling rules) for EUTRAN...............................................................33
2.3.2.3.1 Hysteresis.....................................................................................................................................34
2.3.2.3.2 Evaluation Time...........................................................................................................................34
2.3.4.2 Cell reselection ranking criteria (Inter-RAT and different priority for inter-frequency). 41
2.3.4.2.1 Criteria.........................................................................................................................................41
2.3.4.2.2 3Gpp vs Huawei Parameters........................................................................................................44
2.3.4.2.3 Huawei Ranking Current Parameter Values.................................................................................46
4 Redirection............................................................................................................................74
5 CS Fallback............................................................................................................................75
5.1 Introduction...........................................................................................................................75
5.2 CSFB Mechanisms................................................................................................................75
5.2.1 Towards UTRAN mechanisms......................................................................................................75
5.2.2 Towards GERAN mechanisms......................................................................................................76
5.3 CSFB Basics..........................................................................................................................76
5.4 CSFB Triggering Phase.........................................................................................................77
5.4.1 Description....................................................................................................................................77
5.4.2 CSFB Triggering Parameters........................................................................................................78
5.5 CSFB Measurement Phase.....................................................................................................79
5.5.1 Description....................................................................................................................................79
5.5.2 3Gpp vs Huawei parameters..........................................................................................................80
5.5.3 Current network parameters..........................................................................................................81
5.6 CSFB Decision Phase............................................................................................................82
5.6.1 Description....................................................................................................................................82
7 SON features.......................................................................................................................146
7.1 ANR146
7.1.1 General overview.........................................................................................................................146
7.1.1.1 Feature overview............................................................................................................146
7.1.1.2 Concept...........................................................................................................................146
7.1.1.2.1 Neighbour Cell List concept (NCL)...........................................................................................146
7.1.1.2.2 Neighbour Relation Table concept (NRT)..................................................................................146
7.1.1.2.3 Blacklists concept.......................................................................................................................147
7.1.1.2.4 Whitelists concept......................................................................................................................147
10 Appendices.............................................................................................................176
10.1 Appendix 1: Cell Selection and Cell Reselection........................................................176
10.1.1 Cell Selection and Cell Reselection states and procedures....................................................176
10.1.2 System Information Block.....................................................................................................177
10.1.2.1 System information Block 1.........................................................................................177
10.1.2.2 System information Block 3.........................................................................................178
10.1.2.3 System information Block 4.........................................................................................179
10.1.2.4 System information Block 5.........................................................................................180
10.1.2.5 System information Block 6.........................................................................................181
10.1.2.6 System information Block 7.........................................................................................182
Note:
at the time of releasing this document (initial version), the Mobistar network was running eRAN3, BSS/RAN14, and
sRAN7.
- barred cells
- it must belongs to the registered PLMN
- not allowed TA (Tracking area)
- do not satisfies with the RF conditions
SRxLev > 0
SQual > 0
where:
where:
Parameter Description
Srxlev Cell selection RX level value (dB)
Squal Cell selection quality value (dB)
Qrxlevmeas Measured cell RX level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Qrxlevmin Minimum required RX level in the cell (dBm)
Qqualmin Minimum required quality level in the cell (dB)
Qrxlevminoffset Offset to the signalled Qrxlevmin taken into account in the Srxlev evaluation as a result of a
periodic search for a higher priority PLMN while camped normally in a VPLMN [5]
Qqualminoffset Offset to the signalled Qqualmin taken into account in the Squal evaluation as a result of a
periodic search for a higher priority PLMN while camped normally in a VPLMN [5]
Pcompensation max(PEMAX –PPowerClass, 0) (dB)
PEMAX Maximum TX power level an UE may use when transmitting on the uplink in the cell
(dBm) defined as PEMAX in [TS 36.101]
PPowerClass Maximum RF output power of the UE (dBm) according to the UE power class as
defined in [TS 36.101]
Huawei Parameter
cell selection details.xlsx
Regarding the third cell selection case, on transition from RRC_CONNECTED to RRC_IDLE, this is also called
“redirection”. In Huawei, there is the possibility to allow HO, redirection, or both.
Redirection is a method of transferring UEs between cells and is a type of handover when "handover" is used as a
generic term. When a handover cannot be performed in an emergency or due to equipment limitations, the eNodeB
sends the UE an RRC Connection Release message, which contains information about a neighboring frequency in
the LTE system or in another RAT system. Using this message, the eNodeB instructs the UE to initiate a random
access procedure towards an inter-frequency or inter-RAT neighboring cell so that the UE can resume its services.
Compared with handovers, redirections do not include a procedure for initiating a handover request towards a
neighboring cell and therefore have lower requirements for equipment capabilities and require less time. The two
methods differ in the way to transfer UEs.
Redirections are triggered if a device in the network or the UE involved does not support inter-frequency or inter-
RAT handovers. If both the network and UE support inter-frequency or inter-RAT handovers, handovers are
recommended.
The UTRAN, and GERAN network are often mature, and may not support inter-RAT handovers from the
EUTRAN. In this situation, redirections instead of inter-RAT handovers can be performed on UEs. Therefore,
network capabilities must be collected to determine whether to enable handovers or redirections for UE transfer. To
enable handovers or redirections, turn on the corresponding switch under the ENodeBAlgoSwitch.HoModeSwitch
parameter. If both handovers and redirections are enabled, the eNodeB preferentially uses handovers to transfer
UEs.
During an inter-RAT handover, if the eNodeB determines that the UE does not support inter-RAT measurements or
handovers based on the results of a UE capability inquiry procedure, the eNodeB sends an RRC Connection Release
message to the UE to perform a redirection. This message contains information about the target frequency for the
redirection.
The eNodeB determines whether the UE is capable of inter-RAT measurements and handovers in an adaptive
manner, without requiring user configuration.
Figure 1 shows the UE capability inquiry procedure. For details, refer to 3GPP TS 36.331 Release 10.
In the UE Capability Information message reported by the UE, the featureGroupIndicators IE (Information Element)
indicates whether the UE is capable of frequency-specific or RAT-specific measurements and handovers. For details
about this IE, refer to the 3GPP TS 36.331 Release 10.
If an SPID (subscriber profile ID) is configured for a UE in the EPC or the eNodeB is configured with dedicated
frequency priorities, the eNodeB may deliver a dedicated priority in the idleModeMobilityControlInfo IE of the
command for a redirection. For details about the principles and configuration of SPIDs, see Flexible User Steering
Feature Parameter Description (this is not used here but exists). For details about dedicated priority configuration for
UEs in idle mode, see Idle Mode Management Feature Parameter Description.
In an inter-frequency handover, if the UE does not support inter-frequency or inter-RAT measurements, the eNodeB
performs a blind handover or a blind redirection to transfer the UE to a neighboring cell. Please refer to Blind
Handover topic further in this document for details.
The eNodeB supports flash redirections to UTRAN and GERAN. The flash redirection function is controlled by the
ENodeBAlgoSwitch.RedirectSwitch parameter. If a switch under the ENodeBAlgoSwitch.RedirectSwitch parameter
is turned on, the eNodeB includes the system information of the target cell in the redirection command. This enables
the UE to access the target cell sooner because the UE does not need to read the system information. During a flash
redirection procedure, the eNodeB uses the RAN information management (RIM) procedure to acquire system
information of the target cell. To use RIM, ensure that the devices in the core network and target RAN also support
the RIM procedure. For details about RIM, see CS Fallback Feature further in this document. Note that only UEs
compliant with Release 9 and later releases support the flash redirection function.
At the moment, an LTE cell becomes selectable as soon as the RSRP is equal or above -128 dBm. The RSRQ
criteria is only used for UE with Rel.9 or above, UE power is the capable power of the UE (no limitations).
This means that redirection is activated, but not the flash redirection. CSFB is also active (see chapter 5 for CSFB).
Huawei Parameter
cell redirection details.xlsx
This chapter will present the reselection between LTE cells, inclusive multi band reselection. The operator is indeed
using two different carriers L800 and L1800. Mainly two criterion are considerred: priorities and measurements (RF
conditions). Later other technologies will be considered in chapter 3.
Again, as for the cell selection, some additional criterion have been added since Rel. 9.These are relative to RSRQ
and a new search reference level (“SintraSearchP”). When activated, these parameters are all broadcasted on the
System Information Block 3 (SIB3). Please refer to the appendices for the system information block 3 details.
Reselection measurement criterion are based on parameters broadcasted by the serving cell (where the UE is
camping on), and not from the neighbours. These measurements start only when necessary to avoid unecessary
signalling and so save UE battery live.
Since Rel. 9
where,
When these parameters are not broadcasted, the UE is making measurements continuously, this is a drawback for the
UE battery.
Parameter Description
Sintrasearch This parameter define the RSRP threshold for the serving cell, when the RSRP is below
that threshold, the UE will start measuring neighbour LTE cells within the same
frequency band. If this parameter is not broadcasted, the UE will make measurements
all the time.
SintrasearchP This parameter is replacing Sintrasearch since Rel. 9.
SintrasearchQ This threshold is applicable on RSRQ. It is only present since Rel. 9.
Qrxlevmeas Measured cell Rx level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Qrxlevmin Minimum required Rx level in the cell (dBm)
Qqualmin Minimum required quality level in the cell (dB)
Pcompensation max(PEMAX –PPowerClass, 0) (dB)
PEMAX Maximum TX power level an UE may use when transmitting on the uplink in the cell
(dBm) defined as PEMAX in [TS 36.101]
PPowerClass Maximum RF output power of the UE (dBm) according to the UE power class as
defined in [TS 36.101]
Since Rel. 9
where,
Inter – frequency measurements are always started when the candidate layer has a higher priority than the serving
cell.
Parameter Description
Snonintrasearch This parameter define the RSRP threshold for the serving cell, when the RSRP is below
that threshold, the UE will start measuring neighbour cells. If this parameter is not
broadcasted, the UE will make measurements all the time.
SnonintrasearchP This parameter is replacing Snonintrasearch since Rel. 9.
SnonintrasearchQ This threshold is applicable on RSRQ. It is only present since Rel. 9.
Qrxlevmeas Measured cell Rx level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Qrxlevmin Minimum required Rx level in the cell (dBm)
Qqualmin Minimum required quality level in the cell (dB)
Pcompensation max(PEMAX –PPowerClass, 0) (dB)
PEMAX Maximum TX power level an UE may use when transmitting on the uplink in the cell
(dBm) defined as PEMAX in [TS 36.101]
PPowerClass Maximum RF output power of the UE (dBm) according to the UE power class as
defined in [TS 36.101]
Basically the same conditions are applicable than for inter – frequency, and the same parameters are applicable.
Since Rel. 9
where,
Inter – RAT measurements are always started when the candidate layer has a higher priority than the serving cell.
Parameter Description
Snonintrasearch This parameter define the RSRP threshold for the serving cell, when the RSRP is below
that threshold, the UE will start measuring neighbour cells. If this parameter is not
broadcasted, the UE will make measurements all the time.
SnonintrasearchP This parameter is replacing Snonintrasearch since Rel. 9.
SnonintrasearchQ This threshold is applicable on RSRQ. It is only present since Rel. 9.
Qrxlevmeas Measured cell Rx level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Qrxlevmin Minimum required Rx level in the cell (dBm)
Qqualmin Minimum required quality level in the cell (dB)
Pcompensation max(PEMAX –PPowerClass, 0) (dB)
PEMAX Maximum TX power level an UE may use when transmitting on the uplink in the cell
(dBm) defined as PEMAX in [TS 36.101]
PPowerClass Maximum RF output power of the UE (dBm) according to the UE power class as
defined in [TS 36.101]
The table here below gives the operator current parameter values for the measurement triggering criteria.
Table 2-11: Measurement triggering current Huawei parameter values
2.3.1 Priorities
As it can be seen in the table here under, The operator is putting the priority on LTE1800. The benefit of this
strategy is that LTE1800 is a 15Mhz bandwidth, while LTE800 is only 10 MHz bandwidth, although some
exceptions can occur. This means that in good radio conditions, the throughput experienced by the users will be
better, or at least the users can share more capacity. When the radio conditions become worst, the user can move to
LTE800, where the radio conditions would be better for that same location, usually a 6 to 10 dB better RSRP could
be expected. The interaction with other technologies will be considered in the next chapter.
The priorities, together with other information (parameters to follow), are broadcasted as folowing in the message
“CommonInfo”:
SIB Technologies
SIB3(cellReselectionInfoCommon Intra-frequency
)
SIB5(multiBandInfoList) Inter-frequency
SIB6(multiBandInfoList) Inter-RAT UMTS
SIB7(commonInfo) Inter-RAT GSM
Notes:
- the RAT priorities must be different, similar priorities between RAT are not supported;
- G1800 is in the same group (list of ARFCN) of G900, if some G1800 neighbours are defined;
Note that for GERAN, the priority is made for the whole group of cells, inclusive DCS1800.
Parameter details:
Priorities.xlsx
- The UE shall only perform cell reselection evaluation for EUTRAN frequencies and inter-RAT
frequencies that are given in system information and for which the UE has a priority provided.
- The UE shall not consider any black listed cells as candidate for cell reselection. Blacklists and whitelists
are not introduced here in this document.
- The UE shall inherit the priorities provided by dedicated signalling and the remaining validity time (i.e.,
T320 in EUTRA) if configured, at inter-RAT cell (re)selection.
Note:
there are two different T320, one for the load balancing and one for all the other case. The one considered here is
the second one.
normal mobility;
medium mobility;
high mobility.
Some parameters need to be set in order to detect the UE mobility states. They are listed here below;
Parameter Description
TCRmax Mobility evaluation duration to determine the mobility state
NCR_M Number of cell reselection during TCRmax to enter the medium mobility state
NCR-H Number of cell reselection during TCRmax to enter the high mobility state
TCRmaxHyst Mobility period during which medium or high mobility criteria are not detected in order to
move back to the normal mobility state
The UE shall not count consecutive reselections between same two cells into mobility state detection criteria if same
cell is reselected just after one other reselection.
State transitions:
The UE shall:
- if the criteria for High-mobility state is detected:
- else if criteria for either Medium- or High-mobility state is not detected during time period T CRmaxHyst:
There are two ways to ease the mobility of faster UE. One is to play on the hysteresis between cells, and another is
based on the time of evaluate other cells, both play a role on the ranking of the candidate cells. There is a separate
setting for both medium and high mobility.
2.3.2.3.1 Hysteresis
If the mobility is detected (medium or high) and if the sf-High or sf-Medium for Qhyst is broadcasted, the following is
applied to the hysteresis (Qhyst). A negative value in dB is added to the hysteresis, i.e. -4 dB. This is only for intra –
frequency candidates. These parameters are broadcasted on SIB3 if activated.
In normal mobility, Qhyst is used as such.
Parameter Description
Qhyst Hysteresis
sf-High of "Speed dependent ScalingFactor for Qhyst This is a negative value (dB) that will be applied to Qhyst
in case a high speed UE is detected
sf-Medium of "Speed dependent ScalingFactor for Qhyst This is a negative value (dB) that will be applied to Qhyst
in case a medium speed UE is detected
Parameter Description
TreselectionEUTRA The cell reselection timer value
Table 2-20: Scaling rules for Treselection Huawei parameters (EUTRAN intra-frequency)
Table 2-21: Scaling rules for Treselection Huawei parameters (EUTRAN inter-frequency)
For GERAN and UTRAN, only the second method exists, that is the evaluation time. So similar parameter exist for
reselction of GERAN and UTRAN.
If the mobility is detected (medium or high) and if the sf-High and sf-Medium for TreselectionGERA/UTRA is broadcasted,
the following is applied to the evaluation time of candidates (TreselectionGERA/UTRA). The evaluation is multiplied by a
value below 1, i.e. 0.5. In normal mobility, TreselectionGERA/UTRA is used as such when activated. These parameters are
broadcasted on SIB6 for UTRAN and SIB7 for GERAN.
Parameter Description
TreselectionGERA The cell reselection timer value
Parameter Description
TreselectionUTRA The cell reselection timer value
sf-High of "Speed dependent ScalingFactor for TreselectionUTRA This is a factor to apply to TreselectionUTRA in
case a high speed UE is detected.
sf-Medium of "Speed dependent ScalingFactor for TreselectionUTRA This is a factor to apply to TreselectionUTRA in
case a medium speed UE is detected.
As there are two different LTE layers in the network, both layer are defined here (LTE1800 and LTE800).
Cell Reselection
Mobility Parameter Details.xlsx
CellResel Parameters
GERAN.xlsx
CellResel Parameters
UTRAN.xlsx
In the cell reselection parameter group, other parameters are listed as well. Here below the additional parameters.
These parameters are related to priorities (lower priority case), RSRQ additional conditions, bandwidth,…
Regarding the priorities, one parameter defines the current serving layer priority. In case of LTE 1800, the priority
is set to 5, so the parameter “CellReselPriority” must be set to 5. Please refer to the priorities in 2.3.1.
The IE “MeasBandWidth” is used to indicate the maximum allowed measurement bandwidth on a carrier
frequency as defined by the parameter Transmission Bandwidth Configuration "NRB" TS 36.104 [47].
“NeighCellConfig” indicates the information related to MBSFN (Multimedia Broadcast multicast service Single
Frequency Network) and TDD UL/DL configurations of intra-frequency neighboring cells of the serving cell. It is
set to “01” which means that none of the neighboring cells is configured with MBSFN subframes. Please refer to
3Gpp TS 36.331 for more details on this. It is used for MBMS (Multimedia Broadcast Multicast Service). It is
present here, as normally for mobility the UE considers that the MBSFN area is continuous when the source cell and
the target cell broadcast the same value in the mbsfn-AreaId.
The parameter “PresenceAntennaPort1” is used when the neighbours are using DL diversity (transmitting on two
antennas), this can be used, but there is no impact on the network.
These parameters are broadcasted on SIB3 for the intra – frequency, SIB5 for the inter – frequency, and SIB6 and
SIB7 for repectiverly Utran and Geran. The Huawei coresponding tables are as following: GeranNfreqGroup,
UtranNfreq and EutraninterNfreq.
For the other parameters: ThrshServLow, ThrshServLowQCfgInd, and ThrshServLowQ, refer to the next
chapter: Ranking.
2.3.4.1 Cell reselection ranking criteria (Intra-freq. and equal priority for inter-freq.)
2.3.4.1.1 Criteria
The UE will rank all the candidates that fullfill the cell selection “S” criteria, so the one with Srxlev > 0 and Squal >
0 (Rel. 9). RSRP will be considerred for Rel. 8, additionnaly RSRQ will be considerred for Rel.9.
The cell reselection will occur as soon as the best candidate is better than the serving cell for a duration of T reselection
and if the UE has camped more than one second on the current serving cell. Most of the parameters here below are
per neighbour link parameters, so it can differ from one neighbour link to another (usually when it comes from a
table where “Ncell” is part of the table name).
where,
For intra-frequency, Q offset,s,n is broadcasted on SIB4, if activated, otherwise the value will be 0
For inter-frequency,
Q offset = Q offset,s,n + Q offsetfrequency
Q offset,s,n and Q offsetfrequency are broadcasted on SIB5, if activated, otherwise the value will be 0.
Notes:
- Treselection is adapted by the scaling factor used by the UE mobility detection if active (refer to
2.3.2);
- Treselection; is broadcasted on SIB3 for intra-frequency and on SIB5 for inter-frequency.
2.3.4.2 Cell reselection ranking criteria (Inter-RAT and different priority for inter-frequency)
2.3.4.2.1 Criteria
- Srxlevn > ThreshHigh for Treselection and the UE should have spent at least one second on the serving
cell
where,
- In this case, no cells with higher priority should be available in the list;
- There are no intra-frequency cells or inter-frequency cells with equal priority available in the list
- Srxlevs < ThreshServLow and Srxlevn > ThreshLow and for Treselection and the UE should have
spent at least one second on the serving cell.
where,
Notes:
- In case several candidates meet the criteria, these candidates are ranked as for intra-frequency
ranking criteria (Rs, Rn);
Since Rel.9
If ThreshServLowQ is present on SIB3, the cell reselection to an inter-frequency or inter-RAT cell with a higher
priority than the serving can be performed if:
- Squaln > ThreshXHighQ for Treselection and the UE should have spent at least one second on the
serving cell
GSM
- Srxlevn > ThreshXHighP for Treselection and the UE should have spent at least one second on the
serving cell
else,
- Srxlevn > ThreshXHighP for Treselection and the UE should have spent at least one second on the
serving cell
where,
Qrxlevmeas and Qqualmeas are the RSRP and RSRQ measured respectivelly.
If ThreshServLowQ is present on SIB3, the cell reselection to an inter-frequency or intre-RAT cell with a higher
priority than the serving cell can be performed if:
- Squals < ThreshServLowQ and Squaln > ThreshXLowQ for Treselection and the UE should have spent
at least one second on the serving cell
GSM
- Squals < ThreshServLowQ and Srxlevn > ThreshXLowP for Treselection and the UE should have spent
at least one second on the serving cell
-
else,
where,
Qrxlevmeas and Qqualmeas are the measured RSRP and RSRQ respectivelly.
Notes:
- In case several candidates meet the criteria, these high priority candidates are ranked as for intra-
frequency ranking criteria (Rs, Rn) for inter-frequency. If the high priority candidates are from
inter-RAT, then the ranking should be done with the inter-RAT criteria;
- Treselection is adapted by the scaling factor used by the UE mobility detection if active (refer to
2.3.2);
- Qrxlevmin,n ; Qqualmin,n ; PEMAX,n ; PPowerClass,n ; ThreshXHighQ; ThreshXHighP; ThreshXLowQ;
ThreshXLowP are broadcasted by SIB5, SIB6, SIB7 for inter-frequency EUTRAN, UTRAN,
GERAN cells respectively;
- ThreshServLowQ; ThreshServLowP; are broadcasted on SIB3.
Parameter Description
Treselection Cell reselection evaluation time
Qrxlevmeas Measured cell Rx level value (RSRP)
Qqualmeas Measured cell quality value (RSRQ)
Qrxlevmin Minimum required Rx level in the cell (dBm)
Qqualmin Minimum required quality level in the cell (dB)
Pcompensation max(PEMAX –PPowerClass, 0) (dB)
PEMAX Maximum TX power level an UE may use when transmitting on the uplink in the cell
(dBm) defined as PEMAX in [TS 36.101]
PPowerClass Maximum RF output power of the UE (dBm) according to the UE power class as
defined in [TS 36.101]
ThreshHigh RSRP threshold for higher priority neighbour, is replaced by ThreshXHighP in Rel.9
ThreshLow RSRP threshold for lower priority neighbour, is replaced by ThreshXLowP in Rel.9
ThreshXHighQ RSRQ threshold for higher priority neighbour
ThreshXHighP RSRP threshold for higher priority neighbour, is replacing ThreshHigh in Rel. 9
ThreshServLowQ Serving frequency lower priority RSRQ threshold, is replacing ThreshLow in Rel. 9
ThreshServLowP Serving frequency lower priority RSRP threshold
ThreshXLowQ RSRQ threshold for lower priority neighbour
ThreshXLowP RSRP threshold for lower priority neighbour
GERAN
Regarding GERAN neighbours, a group of frequencies is created, this group can contain GSM and DCS
frequencies. This group will be seen as a whole from the EUTRAN. Only RxLev and the priority of GERAN
neighbours are taken into account.
(*) These parameters are from Rel. 8 and are replaced by ThreshXHighP and ThreshXLowP since Rel. 9
Other GERAN Huawei reselection parameters to be considered as well for the cell reselection
UTRAN
Other UTRAN Huawei reselection parameters to be considered as well for the cell reselection
EUTRAN
(*) These parameters are from Rel. 8 and are replaced by ThreshXHighP and ThreshXLowP since Rel. 9
Other EUTRAN (inter-frequency) Huawei reselection parameters to be considered as well for the cell reselection.
GERAN as target
Huawei Parameter ID Huawei Parameter Name Current GUI Values Current Values
TReselUtran Cell reselection timer value for UTRAN 1 1s
QRxLevMin Minimum required RX level -58 -116dBm
Qqualmin Minimum required quality level -12 -12dB (EcNo)
PmaxUtran PMAX 24 24dBm
ThreshXHighQ UTRAN high priority RSRQ threshold 0 0dB
ThreshXHigh UTRAN high priority threshold 6 -104dBm
ThreshXLowQ UTRAN low priority RSRQ threshold 0 0dB
ThreshXLow UTRAN lower priority threshold 3 -110dBm
CellReselPriorityCfgInd Inter frequency cell resel priority CFG Active
configure indicator
CellReselPriority Cell reselection priority 2 2
UtranDlArfcn Downlink UARFCN 10811 10811
UtranVersion UTRAN version HSPA HSPA
UtranFddTddType UTRAN cell type indicator UTRAN_FDD FDD
UtranUlArfcnCfgInd Uplink UARFCN indicator NOT_CFG Not Active
UtranUlArfcn Uplink UARFCN Not Active
Huawei Parameter ID Huawei Parameter Name Current GUI Values Current Values
TReselUtran Cell reselection timer value for UTRAN 1 1s
QRxLevMin Minimum required RX level -58 -116dBm
Qqualmin Minimum required quality level -12 -12dB (EcNo)
PmaxUtran PMAX 24 24dBm
ThreshXHighQ UTRAN high priority RSRQ threshold 0 0dB
ThreshXHigh UTRAN high priority threshold 6 -104dBm
ThreshXLowQ UTRAN low priority RSRQ threshold 0 0dB
(EcNo)
ThreshXLow UTRAN lower priority threshold 3 -110dBm
CellReselPriorityCfgInd Inter frequency cell resel priority CFG Active
configure indicator
CellReselPriority Cell reselection priority 1 1
UtranDlArfcn Downlink UARFCN 3081 3081
UtranVersion UTRAN version HSPA HSPA
UtranFddTddType UTRAN cell type indicator UTRAN_FDD FDD
UtranUlArfcnCfgInd Uplink UARFCN indicator NOT_CFG Not Active
UtranUlArfcn Uplink UARFCN Not Active
Huawei Parameter ID Huawei Parameter Name Current GUI Values Current Values
EutranReselTime EUTRAN reselection time 1 1s
QRxLevMin Minimum required RX level -64 -128dBm
QQualMinCfgInd Minimum inter-frequency reselection NOT_CFG Not Active
required quality level configure
indicator
QQualMin Minimum inter-frequency reselection Not Active
required quality level
PMaxCfgInd Ue max power allowed configure NOT_CFG Not Active
indicator
PMax Max transmit power allowed Not Active
ThreshXHighQ Inter frequency high priority RSRQ 0
threshold
ThreshXHigh Inter frequency high priority threshold 11 -106dBm
ThreshXLowQ Inter frequency high priority RSRQ 0
threshold
ThreshXLow Inter frequency lower priority threshold 7 -114dBm
CellReselPriorityCfgInd Inter frequency cell resel priority CFG Active
configure indicator
CellReselPriority Cell reselection priority 4 4
MeasBandWidth Measurement bandwidth MBW50 10MHz
PresenceAntennaPort1 Presence antenna port1 BOOLEAN_FALSE Not Used
Huawei Parameter ID Huawei Parameter Name Current GUI Values Current Values
EutranReselTime EUTRAN reselection time 1 1s
QRxLevMin Minimum required RX level -64 -128dBm
QQualMinCfgInd Minimum inter-frequency reselection NOT_CFG Not Active
required quality level configure
indicator
QQualMin Minimum inter-frequency reselection Not Active
required quality level
PMaxCfgInd Ue max power allowed configure NOT_CFG Not Active
indicator
PMax Max transmit power allowed Not Active
ThreshXHighQ Inter frequency high priority RSRQ 0
threshold
ThreshXHigh Inter frequency high priority threshold 13 -102 dBm
ThreshXLowQ Inter frequency high priority RSRQ 0
threshold
ThreshXLow Inter frequency lower priority threshold 11 -106 dBm
CellReselPriorityCfgInd Inter frequency cell resel priority CFG Active
configure indicator
CellReselPriority Cell reselection priority 5 5
MeasBandWidth Measurement bandwidth MBW75 15MHz
PresenceAntennaPort1 Presence antenna port1 BOOLEAN_FALSE Not Used
CellResel Parameters
Ranking.xlsx
Site A Site B
Layer Priority Layer Priority
U210
Priority 2 0 (f2) RSRP > -114 dBm
U210
0 (f1) F1/U9 L1800 Priority 5
Priority 1 U900 RSRP < -116 dBm
& L8 If RSRP L1800 <
-106 dBm
RSCP > -110 dBm
If RSRP L800 >
and EcNo > -12 dB L800 Priority
dBm4
Priority 0 G180 -114
RSRP < -116 dBm
0
&
Priority 0 G900 RSSI > -101 dBm
G9-G18
When L1800 and L800 are present, the user will first reselect L800 before going to other technologies;
When the user is in conditions to reselect a 2G cell, the user will reselect G900, not G1800 as usually G900 is 6 to 10dB better in terms of level, the
priority is the lowest and the same for both G900 and G1800;
When the user is in conditions to reselect a 3G cell, it will preferably do it to U900, as it is usually better by 6 to 10 dB in terms of level. Otherwise it
will do it to U2100, but on f1 only;
This is only for Rel.8 and before, as for Rel.9 and later, RSRQ is also a criteria (if active);
The setting is the same for colocated technologies, and non colocated technologies. But could evolve in the future;
These figures also show the reselection from GSM and UMTS to be complete, they are are addressed in the next chapter.
Site A Site B
Layer Priority Layer Priority
U210
Priority 2 0 (f2) RSRP > -114 dBm
U210
0 (f1) F1/U9
Priority 1 U900
RSRP < -116 dBm
&
RSCP > -110 dBm
L800 Priority 4
Priority 0 G180 and EcNo > -12 dB
RSRP < -116 dBm
0
&
Priority 0 G900 RSSI > -101 dBm
G9-G18
Site A Site B
Layer Priority Layer Priority
U210
Priority 2 0 (f2) RSRP > -114 dBm
U210
0 (f1) F1/U9 L1800 Priority 5
Priority 1 U900
RSRP < -116 dBm
&
RSCP > -110 dBm
Priority 0 G180 and EcNo > -12 dB
RSRP < -116 dBm
0
&
Priority 0 G900 RSSI > -101 dBm
G9-G18
L1800 L1800
L800 L800
Notes:
- this applies to single and dual layer sites, the cell offset is set to 0dB;
- the SintraSearch is set to -70 dBm.
Site A Site B
Priority
L1800 L1800
=5
If RSRP L1800 <
If RSRP L1800 > -102 -116 dBm
dBm If RSRP L800 > -114
dBm
If RSRP L1800 <
If RSRP L1800 > -112 -106 dBm
dBm If RSRP L800 > -114
L800 L800 dBm Priority
=4
Notes:
- this applies to single and dual layer sites, the total cell offset is set to 1dB, so an additional dB needs to be added to the neighbours RSRP;
- SnonIntraSearch = -114 dBm except for dual layer L1800 where it is -104 dBm.
This functionality has been introduced since Rel. 8, with the arrival of the LTE technology. The UE must be LTE
compliant, and the SIM/USIM should allow this technology. As for GSM to UMTS reselection, the necessary
information is broacasted on the system information type 2Quater (SI2Quater ). This type of inter-RAT reselection is
priority based. In this case, the LTE network has the highest priority.
The Cell Reselection Between GSM and LTE feature can be used only if neighboring LTE cells are configured.
Each GSM cell can be configured with a maximum of 64 LTE neighboring cells. These neighboring cells can use a
maximum of eight LTE frequencies. The respective 3Gpp references are: TS 45.008 & TS 44.060.
The priorities need to be set for all technologies. The current priorities are listed in 2.3.1. Here below the priority
parameter concerned:
Table 3-44: GSM to LTE Cell Reselection Huawei Priority Parameters
3.1.1.2 Activation
In order to allow the UE to reselect an LTE cell from GSM, the SI2Quater should be broadcasted with the necessary
LTE information (neighbouring LTE cells and related parameters), this broadcast is controlled by the following
parameters: LTECELLRESELEN and Send2QuterFlag . These parameters need to be set to YES.
The parameter THRPRISEARCH trigger the inter-RAT measurements. The inter-RAT measurements could be
permanent, in that case this parameter needs to be set to “Always” (15), or the measueremnts can be triggered as
soon as the the GSM serving cell and the GSM neighbour cells RSSI is below this parameter.
Table 3-45: : GSM to LTE Cell Reselection Huawei Activation Parameters
GLTENCELL
GEXTLTECELL
The first parameters like the BSC Name,… are variable. The last 4 are default ones, the ones important here are
SPTRESEL and NCELLPRI. When the Fast Reselection feature is activated (see next feature topic 3.1.3), the
parameter: SPTRAPIDSEL will be set to SUPPORT.
Some parameters are constant and network dependent here, like the MCC, MNC, EUTRANTYPE, OPNAME, some
others are variable, and change on aper cell/link basis.
3.1.2.1 GERAN priority is lower than EUTRAN priority (GERANPRI < EUTRANPRI)
In case the EUTRAN priority is higher than the GERAN priority (serving cell), this is the case in this network, and
that the individual priority NCELLPRI is set to 255, the conditions for the target cell are as following:
Where,
S_NonServingEUTRANN : RSRPN – EUTRANQRXLEVMIN
Where,
RSRPN is the measured RSRP of one LTE neighbours;
EUTRANQRXLEVMIN is also broadcasted on the SI2quater and represent the absolute minimum RSRP
allowed for reselection.
THREUTRANHIGH: is broadcasted on the SI2quater and represents the higher priority EUTRAN cell threshold.
TRESEL: is the period time during the conditions must be met.
In case several LTE neighbours have the same priority, which is the case when individual priority NCELLPRI is set
to 255, the one with the best RSRPN is selected.
Note: when the EUTRAN cells have a higher priority than the GERAN, EUTRAN cells are always reported as
candidates, whatever the serving cell conditions, the parameter THRPRISEARCH do not play a role here.
3.1.2.2 EUTRAN priority is lower than GERAN priority (GERANPRI > EUTRANPRI)
In case the EUTRAN priority is lower than the GERAN priority (serving cell), and that the individual priority
NCELLPRI is set to 255, the conditions for the target cell are as following:
then the conditions are met for the target cell. If several EUTRAN cells have the same priority, then the one with the
best RSRP will be selected.
Where,
C1: is the GSM Path Loss C1 criteria of the serving cell;
S_NonServingEUTRANN : RSRPN – EUTRANQRXLEVMIN;
THRGSMLOW: is the GSM serving cell and GSM neighbour cells threshold broadcasted on SI2quater;
TRESEL: is the period time during the conditions must be met;
THREUTRANLOW: is broadcasted on the SI2quater and represents the lower priority EUTRAN cell threshold.
If no cells meet these criterion for at least TRESEL, then the target cell will be the one where
S_NonServingEUTRANN is greater than C1+HPRIO. The best one will be used in case several cells have their
S_NonServingEUTRANN above C1+HPRIO.
Notes:
- UTRAN priority also needs to be considered;
- Cell reselection to a cell of another radio access technology (e.g. UTRAN) shall not occur within
5 seconds after the MS has reselected a GSM cell from an inter-RAT cell if a suitable GSM cell
can be found.
As known already, GERAN has the lowest priority, so the idea is to move back to LTE as soon as possible, so that
the user is in the best conditions to make a data call (expected throughput). In case the user would like to start a CS
call while being on the LTE network, the so called CS fallback feature exists. See in related chapter.
The UE is always searching for the LTE network, as the parameter THRPRISEARCH is set to “always”. So as soon
as the UE find an LTE cell with an RSRP greater tha -112 dBm during at least 5 second, it will reselect that cell if it
is allowed to (no barred cell,…).
Note: the following parameter are common for UTRAN reselection: TRESEL, HPRIO, THRGSMLOW,
THRPRISEARCH. There are specific thersholds for UTRAN, as there are for EUTRAN.
The following parameters are in the same table: GCELLPRIEUTRANSYS, but are used in case the feature eNC2
(Network Control Reselection) is active (it isn’t currently), in that case the network is controlling the reselection
based on measurement reports, this is especially usefull in case of load balance featuring,…:
Huawei Parameter ID Huawei Parameter Name Current GUI Values Current Values
Never (no
QPEUTRAN EUTRAN Cell Search Thres. in Packet Mode 15 EUTRAN cell
search
THREUTRANRPT EUTRAN Cell Reporting Threshold 0 -140 dBm
BESTEUTRANCELLNUM Number EUTRAN Cells in Best Cell List 2 2
GSM to (E)UTRAN
Reselection Parameters GCELLPRIEUTRANSYS v2.xlsx
Table 3-50: Fast LTE Reselection at 2G CS call release - neighbours definition (GLTENCELL)
The priorities need to be set for all technologies. The current priorities are listed in 2.3.1. Here below the priority
parameters concerned:
Table 3-51: UMTS to LTE Cell Reselection - Huawei Priority Parameters
These priorities are broacasted on the SIB19 together with the other parameters.
When the EUTRAN priority is higher than the one of the UTRAN (serving cell), the EUTRAN frequency will
always been measured.
When the EUTRAN priority is lower than the one of the UTRAN (serving cell), then the following conditions will
be used:
- If SrxlevS > Sprioritysearch1 and SqualS > Sprioritysearch2 the UE may choose not to perform measurements of
inter-RAT layers of lower priority;
- If SrxlevS <= Sprioritysearch1 or SqualS <= Sprioritysearch2 the UE shall perform measurements of inter-RAT
layers of lower priority;
where,
Srxlevs: Qrxlevmeas,s - Qrxlevmin – Pcompensation
Squals = Qqualmeas,s – Qqualmin, Qqualmeas,s is the serving cell Ec/No.
where,
Parameter Description
Sprioritysearch1 Search threshold for Srxlev
Sprioritysearch2 Search threshold for Squal
Cell Selection quality value (dB)
Squal
Applicable only for FDD cells and E-UTRA cells.
Srxlev Cell Selection RX level value (dB)
Measured cell quality value. The quality of the received signal expressed in CPICH
Qqualmeas Ec/N0 (dB) for FDD cells.
Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells
Qrxlevmeas
(dBm)
Qqualmin Minimum required quality level in the cell (dB). Applicable only for FDD cells.
Qrxlevmin Minimum required RX level in the cell (dBm)
Pcompensation max(UE_TXPWR_MAX_RACH – P_MAX, 0) (dB)
Maximum TX power level an UE may use when accessing the cell on RACH (read in
UE_TXPWR_MAX_RACH
system information) (dBm)
P_MAX Maximum RF output power of the UE (dBm)
Table 3-53: UMTS to LTE Cell Reselection - “S” criteria Huawei Parameters
Table 3-54: UMTS to LTE Cell Reselection - “S” criteria Huawei Parameters curent network values
Huawei Parameter ID Huawei Parameter Name Current GUI Values Current Values
RSCP threshold for low-prio-freq
THDPRIORITYSEARCH1 2 -111 dBm
measurement initiation
Ec/No threshold for low-prio-freq
THDPRIORITYSEARCH2 2 2dB
measurement initiation
Qqualmin Min quality level -18 -18 dB
Qrxlevmin Min Rx level -58 -115 dBm
MaxAllowedUlTxPower Max allowed UE UL TX power 24 24 dBm
UTRAN to EUTRAN
Reselection Parameters Meas.xlsx
3.2.3.1 UTRAN priority is lower than EUTRAN priority (UTRANPRI < EUTRANPRI)
If the Srxlevn of a EUTRAN cell is greater than ThreshHigh during a time interval Treselection.
where,
3.2.3.2 EUTRAN priority is lower than UTRAN priority (UTRANPRI > EUTRANPRI)
If (Srxlevs < ThreshLows or Squals <= 0) and the Srxlevn of a EUTRAN cell is greater than ThreshLow during a time
interval Treselection.
where,
Srxlevs: Qrxlevmeas,s – Qrxlevmins – Pcompensations, Qrxlevmeas,s is the serving cell RSCP measured by the UE
Srxlevn: Qrxlevmeas,n, Qrxlevmeas,n is the EUTRAN frequency RSRP measured by the UE
ThreshLow: threshold for the neighbour EUTRAN cell in case of lower priority EUTRAN cell reselection
ThreshLows: threshold for the serving cell towards lower priority EUTRAN cell reselection (RSCP)
Squals: Qqualmeas,s – Qqualmins, Qqualmeas,s is the serving cell Ec/No.
Treselection: time interval for valid measurement
Note: the absolute value for the parameters: ThreshLow, and ThreshHigh are relative to the parameter Eqrxlevmin.
Parameter Description
Cell Selection quality value (dB)
Squal
Applicable only for FDD cells and E-UTRA cells.
Srxlev Cell Selection RX level value (dB)
Measured cell quality value. The quality of the received signal expressed in
Qqualmeas CPICH Ec/N0 (dB) for FDD cells.
Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells
Qrxlevmeas
(dBm), or RSRP for EUTRAN frequency.
Qqualmin Minimum required quality level in the cell (dB). Applicable only for FDD cells.
Qrxlevmin Minimum required RX level in the cell (dBm)
Pcompensation max(UE_TXPWR_MAX_RACH – P_MAX, 0) (dB)
Maximum TX power level an UE may use when accessing the cell on RACH (read
UE_TXPWR_MAX_RACH
in system information) (dBm)
P_MAX Maximum RF output power of the UE (dBm)
Threshold for the serving cell towards lower priority EUTRAN cell reselection
ThreshLows
(RSCP)
Threshold for the neighbour EUTRAN cell in case of lower priority EUTRAN cell
ThreshLow
reselection. Eqrxlevmin is used to calculate the absolute RSRP threshold.
Threshold for the neighbour EUTRAN cell in case of higher priority EUTRAN
ThreshHigh
cell reselection. Eqrxlevmin is used to calculate the absolute RSRP threshold.
Treselection cell reselection timer value
If multiple cells fulfill a set of criterion, the UE performs reselection to the cell with the highest absolute priority. If
multiple cells have the highest absolute priority, the UE performs reselection to the cell with the largest Srxlevn
value.
Table 3-56: UMTS to LTE Cell Reselection - triggering criteria Huawei Parameters
Huawei Parameter ID Huawei Parameter Name Current GUI Values Current Values
RSCP threshold for low-prio-freq
ThdServingLow 1 -113 dBm
reselection
ThdToLow RSRP Threshold for Low-prio-freq
2 -124 dBm
Reselection
RSRP Threshold for High-prio-freq
ThdToHigh 8 -112 dBm
Reselection
Minimum Required RSRP
EQrxlevmin -64 -128 dBm
Threshold of the E-UTRA Cell
Qqualmin Min quality level -18 -18 dB
Qrxlevmin Min Rx level -58 -115 dBm
MaxAllowedUlTxPower Max allowed UE UL TX power 24 24 dBm
Treselections Reselection delay time 1 1s
UTRAN to EUTRAN
Reselection Parameters Trigg.xlsx
Parameter details:
UTRAN to EUTRAN
Reselection Parameters Trigg other.xlsx
No
Find another LTE Suitable
Found LTE Cell?
Frequency
Yes
No
No
LTE Cell fullfil Cell selection
criteria (« S ») Time Elapse?
Srxlev and Squal
Yes
Yes
Notes:
3.2.4.2.1 Priorities
The absolute priorities need to be defined, here below the respective parameters to set, these are the same as for the
UMTS to LTE reselection:
In order to have this feature operational, the neighbour links between UMTS and LTE need to be defined. Therefore,
the following parameters in the tables ULTECELL and ULTENCELL need to be defined.
In the ULTENCELL, only the neighbours are defined with their respective RNCID, CELLID and LTECELLINDEX
refering to the neighbours defined in the table ULTECELL.
To effectivelly activate the feature, once the priorities and neighbour respective parameters have been defined, the
parameter: HO_UMTS_TO_LTE_FAST_RETURN_SWITCH under the HOSwitch parameter in the table
UCORRMALGOSWITCH must be switched on.
Redirection is a method of transferring UEs between cells and is a type of handover when "handover" is used as a
generic term. When a handover cannot be performed in an emergency or due to equipment limitations, the eNodeB
sends the UE an RRC Connection Release message, which contains information about a neighboring frequency in
the LTE system or in another RAT system. Using this message, the eNodeB instructs the UE to initiate a random
access procedure towards an inter-frequency or inter-RAT neighboring cell so that the UE can resume its services.
Compared with handovers, redirections do not include a procedure for initiating a handover request towards a
neighboring cell and therefore have lower requirements for equipment capabilities and can be rapidly performed.
The two methods differ in the way to transfer UEs.
5.1 Introduction
The CS Fallback (CSFB) consists of moving the UE away from the EUTRAN network in order to start a voice call
on a mobile network with circuit switched (CS) core network. Indeed, LTE do not have CS core network, for voice
call, only voice over IP is supported (VoIP), IMS network is required for VoIP. VoIP is not part of this document. In
order to have CSFB working, there should be a link between the MME (LTE PS core network) and the MSC (GSM
and UMTS CS core network). This interface is called SGs.
In eRAN6, there are several features for CSFB (towards GERAN and UTRAN):
The two first features (LOFD-001033 and LOFD-001034) are the ones currently in use, the ones explained here
below, and require 3Gpp Rel. 8. There are two options, using the PS-HO or the redirection. The following two,
LOFD-001052 and LOFD-001053 require 3Gpp Rel.9 on both the network and UE sides. They use the principle of
RIM (RAN Information Management), in that case a specific cell can be refferred in the messaging, instead of only
the frequency. The two next features are usefull in case of different PLMN, or different LAC. The last three features
are used in case a specific network strategy in terms of HO policies for CS and PS, also in case of load balance
requirement,...
Based on the capabilities of UEs and network, the following mechanisms are available for an
eNodeB to perform CSFB to UTRAN:
Based on the capabilities of UEs and network, the following mechanisms are available for an
eNodeB to perform CSFB to GERAN:
The features LOFD-001033 and LOFD-001034 are explained here below, these are the most popular ones, and the
ones currently in use. These features are using the mechanisms listed here above, except the one called “Flash”.
Here below the process followed by the eNodeB to perform a CSFB. There are basicaly 4 main phases:
- CSFB triggering;
- CSFB measurement;
- CSFB decision;
5.4.1 Description
After receiving a CS Fallback Indicator from the MME, the eNodeB decides whether to
perform CSFB in the form of a blind handling procedure based on the UE capabilities and
the setting of the blind handover switch on the eNodeB. Compared with measurement based
handovers, blind handling procedures have shorter access delays but a lower
handover success rate.
During this phase, the system must know if it has to trigger a blind handover, or a measurement handover.
After receiving the CS Fallback Indicator, the eNodeB checks the blind-handover switch setting
and UE capabilities for each RAT and performs accordingly:
If the PS handover switch is turned on, it is recommended that the blind handover switch be
turned off to increase the CSFB success rate. The UtranPsHoSwitch and GeranPsHoSwitch
options under the ENodeBAlgoSwitch.HoModeSwitch parameter specify whether to enable PS
handover to UTRAN and GERAN, respectively.
Figure 5-15: CSFB Triggering phase - selecting frequencies to measure or selecting a target cell
Note: in case the neighbour relations are defined with their respective parameters, these are not listed here, but these
need to be taken into account. It is currently the case for the GERAN, but not for the UTRAN (same as for the
reselection). The eNodeB can deliver a maximum of 3 UTRAN absolute radio frequency channel numbers
(UARFCNs) or 32 GERAN absolute radio frequency channel numbers (ARFCNs) at a time.
5.5.1 Description
CSFB is triggered by event B1, which is reported in event-triggered periodical reporting mode.
The triggering of event B1 indicates that the signal quality is higher than a specified threshold
in at least one neighboring cell. As defined in 3GPP TS 36.331, the entering and leaving conditions of event B1 are
as follows:
where,
Mn: is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets (dB or dBm);
Ofn: is the frequency specific offset of the frequency of the inter-RAT neighbou (dB)r;
The following parameters related to event B1 for CSFB are the same as those related to event B1 for inter-RAT
handovers:
Note:
Ms: is the measurement result of the serving cell, not taking into account any offsets.
Note:
- the parameter InterRATHoUtranB1MeasQuan is only used for 3Gpp Rel. 10 and further, currently it
is using both RSCP and Ec/No (set to both by default);
- it is not clear if the hysteresis parameters are used for CSFB B1 event, but it can be expected so, to
avoid ping-pong.
These parameters have the same value for L800 and L1800.
Current
Huawei Parameter ID Huawei Parameter Name Current GUI Values
Values
HoModeSwitch Handover Mode switch EutranVoipCapSwitch-0 inactive
&UtranVoipCapSwitch-0
&GeranVoipCapSwitch-0
&Cdma1xRttVoipCapSwitch-0
&UtranPsHoSwitch-0 &GeranPsHoSwitch-0
&CdmaHrpdNonOtpimisedHoSwitch-0
&CdmaHrpdOptimisedHoSwitch-0
&GeranNaccSwitch-0 &GeranCcoSwitch-0
&UtranSrvccSwitch-0 &GeranSrvccSwitch-0
&Cdma1xRttSrvccSwitch-0
&UtranRedirectSwitch-1
&GeranRedirectSwitch-1
&CdmaHrpdRedirectSwitch-0
&Cdma1xRttRedirectSwitch-0
Note: several parameters are introduced in eRAN6, so there are no current network values for all parameters (current
network is eRAN3). No value means that the parameter is introduced in eRAN6, they are also writen in italic.
5.6.1 Description
The eNodeB analyses the measurements and select the suitable cells (in case of HO) and / or select the suitabletarget
cell .
5.7.1 Description
The eNodeB executes the CSFB and the UE moves towards the target cell. Currently, only the redirection based
CSFB is followed.
Note: prior the Ericsson core, the handover way was used.
Figure 5-17: CSFB Execution phase - Procedure for executing CSFB to GERAN
5.7.2 Parameters
Note: HoAlgoSwitch is a general HO parameters, where several HO types are set or unset, refer to the parameter
details file for further information.
These parameters have the same value for L800 and L1800.
Huawei Parameter ID Huawei Parameter Name Current GUI Values Current Values
IntraFreqCoverHoSwitch-1
&InterFreqCoverHoSwitch-1
&UtranCsfbSwitch-1
&GeranCsfbSwitch-1
&Cdma1xRttCsfbSwitch-0
&UtranServiceHoSwitch-0
&GeranServiceHoSwitch-0
UTRAN and
&CdmaHrpdServiceHoSwitch-0
HoAlgoSwitch Handover Algo switch GERAN CSFB
&Cdma1xRttServiceHoSwitch-0
are active
&UlQualityInterRATHoSwitch-0
&InterPlmnHoSwitch-0
&UtranFlashCsfbSwitch-0
&GeranFlashCsfbSwitch-0
&ServiceBasedInterFreqHoSwitch
-0
&UlQualityInterFreqHoSwitch-0
UtranFreqLayerMeasSwitch-0
FreqLayerSwtich Frequency Layer Switch inactive
&UtranFreqLayerBlindSwitch-0
UTRAN_RIM_SWITCH-0
RimSwitch RIM switch RIM inactive
&GERAN_RIM_SWITCH-0
CSFB handover policy
CsfbHoPolicyCfg
Configuration
CnOperatorId CN Operator ID 0 0
InterRatHighestPri Highest priority InterRat GERAN GERAN
InterRatSecondPri Second priority InterRat UTRAN UTRAN
InterRatLowestPri Lowest priority InterRat CDMA2000 CDMA2000
UtranLcsCap UTRAN LCS capability OFF OFF
GeranLcsCap GERAN LCS capability OFF OFF
CsfbProtectionTimer CSFB Protection Timer
NoHoFlag No handover flag Permit HO Permit HO
GAP_PATTER
GapPatternType GAP measurement pattern GAP_PATTERN_TYPE_1 N
_TYPE_1
GeranFilterCoeff GERAN filter coefficient FC6 FC6
UTRAN RSCP filter
UtranFilterCoeffRscp FC6 FC6
coefficient
UTRAN ECN0 filter
UtranFilterCoeffEcn0 FC6 FC6
coefficient
GeranCellNumForEmcRedire Max Geran cell num in
ct CSFB EMC redirection
UtranCellNumForEmcRedire Max Utran cell num in
ct CSFB EMC redirection
BlindHoPriority Blind handover priority 0 or 1(*) 0 = not allowed
ConnFreqPriority Connect frequency priority
Notes:
(*) Regarding the parameter “BlindHOPriority”, only one neighbour can be defined as target, usually it is the co-
located cell, if there is no co-located cell, another can be defined, the most probable one. Although the system send
all neighbour information.
All concerned parameters are listed here in details, inclusive the ones used for other features listed here, although
not in use, or explained here above.
CSFB eRAN6
parameters.xlsx
This chapter provides a description of mobility in connected mode, idle mode was described in previous chapter,
mainly in the cell reselection chapter. The mobility in connected mode follows a process through handover (HO). It
guarantees the continuity of the service while the UE is moving accross the network. It concerns only data (PS)
service since voice is moved to other thechnologies (refre to the CS fall back in previous chapter).
Handovers can be classified by handover target and by causes as follows: intra-frequency, inter-frequency, and inter-
RAT, but also load based, coverage based,…as it can be seen here under:
Clasified by target:
- Intra-frequency;
- Inter-frequency;
- Inter-RAT.
Clasified by causes:
Only coverage based are currently used, only this part will be explained here under.
The figure here under is a summary of the elements involved in the PS mobility for EUTRAN.
After a UE establishes a radio bearer, the eNodeB delivers the measurement configuration to the UE in an RRC
Connection Reconfiguration message. The measurement configuration consists of measurement objects, reporting
configurations, and other parameters.
Measurement objects are the objects that UEs measure. Measurement object information includes the target system
and target frequency for a UE to measure, as well as the measurement bandwidth, frequency-specific offset, and
target cell.
The eNodeB delivers only information about the target systems that the UE is capable of measuring. The target
systems vary as follows:
- For the measurement of the serving cell or an intra-frequency neighboring cell, the target
system is EUTRAN;
- For an inter-frequency measurement, the target system is EUTRAN;
- For an inter-RAT measurement, the eNodeB determines the target system based on the UE
measurement capability, as described in the following sections.
The eNodeB determines target frequencies based on a list of neighboring cells in the selected target system.
The eNodeB determines the target frequencies based on a neighboring cell list that excludes the following cells:
- Blacklisted neighboring cells;
- Neighboring cells that have a different PLMN from the serving cell if the inter-PLMN
handover switch is turned off (this is usually the case);
- Neighboring cells with a handover prohibition flag;
- Neighboring cells in the areas indicated by the information element (IE) Handover Restriction List in
the INITIAL CONTEXT SETUP REQUEST message sent from the MME.
If the number of configured target frequencies exceeds the protocol-specified limit, the eNodeB selects and delivers
frequencies with higher priorities. If the number of high-priority target frequencies still exceeds the limit and
multiple high-priority frequencies are configured with the same priority, the eNodeB randomly selects some of these
frequencies.
If the number of GERAN frequencies to be delivered exceeds the protocol-specified limit, the eNodeB may not
deliver GERAN frequencies that have low priorities. Therefore, if a large number of GERAN frequencies are to be
delivered, add these frequencies to a GERAN frequency group with a high priority, that is, a GERAN frequency
group with a large value of GeranNfreqGroup.ConnFreqPriority before configuring them.
These parameters are eRAN6, so there are no current values in the network.
Parameter details:
Target Frequency
Priority.xlsx
If the target system is E-UTRAN, information about a measurement object also includes:
- Measurement bandwidth
The measurement bandwidth is the cell bandwidth of which the UE performs
measurements. If the measurement bandwidth of the serving cell or intra-frequency
neighboring cells is not specified (CELLRESEL.MeasBandWidthCfgInd is set to
NOT_CFG), the eNodeB includes the downlink (DL) bandwidth (specified by the
CELL.DlBandWidth parameter) of the serving cell in the measurement configuration by
default and delivers the information to the UE.
- Frequency-specific offset
The frequency-specific offset is included in the measurement object information because
it is set for each frequency. This offset adjusts the probability of triggering a handover to
a specific frequency.
For details about parameters for EUTRAN measurement configurations, refer to the intra-frequency
measurement and inter-frequency measurement parameters here further in this chapter.
Note: these parameters are also listed in the reselection chapter 2 (2.3.2.7.2).
According to 3GPP specifications, if the target system is EUTRAN or UTRAN, the measurement configuration can
include information about the candidate target cells. Please refer to 3Gpp TS 36.331.
If the target system is EUTRAN, the eNodeB delivers information about a candidate target cell only if the cell
individual offset (CIO) of the cell is not 0 dB.
- Event A2 indicates that the signal quality in the serving cell is lower than a specified threshold. When
the information about the cells that meet the triggering condition is reported, the eNodeB starts inter-
frequency or inter-RAT measurements. However, in frequency-priority-based inter-frequency
handovers, event A2 is used to stop interfrequency measurements.
- Event A3 indicates that the signal quality in at least one intra-frequency or inter-frequency neighboring
cell is higher than that in the serving cell by an offset. When the information about the cells that meet
the triggering condition is reported, the source eNodeB sends an intra-frequency or inter-frequency
handover request.
- Event A4 indicates that the signal quality is higher than a specified threshold in at least one inter-
frequency neighboring cell. When the information about the cells that meet the triggering condition is
reported, the source eNodeB sends an inter-frequency handover request.
- Event A5 indicates that the signal quality in the serving cell is lower than a threshold and that the
signal quality in at least one inter-frequency neighboring cell is higher than another threshold. When
the information about the cells that meet the triggering condition is reported, the source eNodeB sends
an inter-frequency handover request.
- Event A6 (since 3Gpp Rel. 10), is in use with carrier aggregation. It indicates that the signal quality in
at least one intra-frequency secondary cell is higher than that in the serving cell by an offset.
- Event B1 indicates that the signal quality is higher than a specified threshold in at least one inter-RAT
neighboring cell. When the information about the cells that meet the triggering condition is reported,
the source eNodeB sends an inter-RAT handover request.
- Event B2 indicates that the signal quality in the serving cell is lower than a threshold and that the
signal quality in at least one inter-RAT neighboring cell is higher than another threshold. When the
information about the cells that meet the triggering condition is reported, the source eNodeB sends an
inter-RAT handover request.
Each event may have different sets of the threshold and other event-associated parameters, with each set of the
parameters mapped to a QoS Class Identifier (QCI). The QCI is not in use, and is not part of this document.
The UE reports measurement results in event-triggered periodical mode, which is described in the next section.
After an event is reported for the first time, the measurement results associated with the event are reported
periodically. This reporting mode is called event-triggered periodical reporting. The UE sends the measurement
results to the eNodeB in event-triggered periodical reporting mode.
The periodical reporting is stopped when the leaving condition is met or after the UE receives a handover command.
- Reduces the impact of loss of measurement reports or failures in internal processing on handovers.
- Enables retries of access in case of admission rejection.
- Provides complete measurement results by updating cell information in periodical reports, since a
single measurement report may not contain information about all neighboring cells that meet an event
triggering condition and neighboring cells meeting the condition may change with UE movement.
Hysteresis and time-to-trigger are key parameters for the UE to decide whether to report an event. These parameters
directly affect handover performance of the system. The two parameter types are set in the measurement
configuration for the associated events.
To reduce the number of event reports generated because of radio signal fluctuation, the hysteresis to the signal
quality is used in the entering and leaving conditions for each event. The hysteresis setting affects the triggering of
the corresponding event. A larger value of the hysteresis results in a lower probability of event triggering, affecting
the user experience. A smaller value of the hysteresis results in a higher probability of event triggering, but it also
leads to a higher probability of incorrect handover decisions and ping-pong handovers.
When the entering condition of an event is met, the UE does not report the cell measurement result associated with
the event to the eNodeB until the entering condition is met throughout a specified period, as defined by the time-to-
trigger parameter. This prevents unnecessary handovers. Time-to-trigger is set for each event, significantly reducing
the average number of handovers and the number of incorrect handovers. Also, these related parameters are decribed
in details in the coming sections.
The quantities Reference Signal Received Power (RSRP) and Reference Signal Received Quality (RSRQ) are used
to measure the E-UTRAN cell quality. Based on the RSRP, the RSRQ takes interference into consideration. The
triggering quantities and reporting quantities for events are configurable. The options are RSRP, RSRQ, or both.
Based on the triggering quantities specified by the eNodeB, the UE performs event evaluation. When the
corresponding signal quality in cells meets the triggering condition for a specific event, the UE reports the
information about the cells to the eNodeB.
6.1.3.3.1 Filtering
Before evaluating the reporting criteria and sending measurement reports, the UE performs layer 1 (L1) filtering and
L3 filtering on the measurement results. The L1 filtering is performed by the UE at the physical layer to eliminate
the impact of fast fading on the measurement results.
No user configuration is required for the L1 filtering. The L3 filtering aims at eliminating the impact of shadow
fading and certain fast fading. In this way, better measurement data is provided for the evaluation of the reporting
criteria. Based on the triggering quantity, two L3 filtering coefficients are applicable: one for RSRP measurements
and the other for RSRQ measurements.
The UE performs L1 filtering, L3 filtering, and evaluation of reporting criteria according to the model shown in the
figure here below.
The measurement points shown in the figure here above are described as follows:
Fn = (1 - a) x Fn-1 + a x Mn
Where,
- Mn is the nth measurement value received from the physical layer. The interval at which
measurement values are received at the physical layer is subject to UE implementation.
The details are not provided in this document.
- Fn-1 is the (n - 1)th filtered measurement value.
- Fn is the nth filtered measurement value.
- a = 1/2(k/4). It is a weighting factor for the current measurement quantity. In the formula,
k is the L3 filtering coefficient. If k is set to 0 (that is, a = 1), L3 filtering is not applicable.
The L3 filtering coefficient k for different networks is specified by different parameters. The
details are as follows:
Huawei Parameter
Huawei Parameter ID Table
Name
EUTRAN RSRP filter
EutranFilterCoeffRSRP HOMEASCOMM
coefficient
EUTRAN RSRQ filter
EutranFilterCoeffRSRQ HOMEASCOMM
coefficient
UTRAN RSCP filter
UtranFilterCoeffRSCP HOMEASCOMM
coefficient
UTRAN ECN0 filter
UtranFilterCoeffECN0 HOMEASCOMM
coefficient
GERAN filter
GeranFilterCoeff HOMEASCOMM
coefficient
A measurement gap is a time period during which the UE performs measurements on a neighboring frequency of the
serving frequency. Measurement gaps are applicable to inter-frequency and inter-RAT measurements. In most cases,
each UE has only one receiver, and consequently each UE can receive the signals on only one frequency at a time.
The Gaps start during SFN (System Frame Number) and subframes defined by:
Where,
MGRP is the Measurement Gap Repetition Period it equals 40 ms for gap pattern identity 0 and 80 ms for gap
pattern identity 1. The measurement gap for both pattern identity 0 and 1 is 6 ms.
GapOffset is a configurable value between 0 and 39 for the pattern identy 0, and 0 to 79 for the pattern identity 1.
For example: when the gap identity 0 is configured with a GapOffset of 12, then the measurement gaps start during
subframe 2 of SFN 1, 5, 9, 13, 17, 21,…
The eNodeB specifies the time period for a UE to perform inter-frequency or inter-RAT measurement by sending
measurement gap configurations to the UE. If the AutoGapSwitch option is selected under the
ENodeBAlgoSwitch.HoModeSwitch parameter, the eNodeB does not send measurement gap configurations to UEs
that support autonomous gaps. For details about measurement gaps, refer to 3GPP TS 36.300 Rel.10.
After receiving a measurement gap configuration, the UE starts gap-assisted measurements accordingly. As shown
in her below, Tperiod denotes the repetition period for measurement gaps, and TGAP denotes the gap width, within
which the UE performs measurements.
When gap-assisted measurements for various handover types co-exist, the eNodeB records the measurements based
on these handover types. Different gap-assisted measurements can share the same measurement gap configuration.
A UE releases measurement gaps only after all gap assisted measurements are completed.
Two measurement gap patterns are available: pattern 1 and pattern 2. In pattern 1, TGAP is 6 ms and Tperiod is 40
ms. In pattern 2, TGAP is 6 ms and Tperiod is 80 ms. The pattern to use is specified by the
HoMeasComm.GapPatternType parameter.
Specific CIO values can be set for the serving cell and its neighboring cells.
When the quality of signals fluctuates, the probability of triggering handovers to or from a specific cell can be
adjusted by changing the CIO value. This reduces the risk of dropped calls. The CIO values are adjusted
automatically by the MRO function (LOFD-002005 Mobility Robust Optimization).
According to 3GPP TS 36.331, CIO values are contained in the IE Neighbour cell list in the measurement
configuration. The CIO value can adjust the boundary of the associated cell for a handover. A smaller CIO value for
the serving cell results in a higher probability of handovers from the serving cell, and a larger CIO value for the
target cell also results in a higher probability of handovers to the target cell.
If among the candidate cells, the measurement result of an intra-eNodeB cell is the same as that of an inter-eNodeB
cell, the eNodeB assigns the intra-eNodeB cell a priority, which will prevent signaling and data forwarding required
in an inter-eNodeB handover.
The eNodeB then sends a handover request to the target cell at the top of the candidate cell list. If the handover
request fails, the eNodeB sends the handover request to the next target cell. If the eNodeB has tried all cells
indicated in the measurement report but failed to perform a handover, the eNodeB either of the following actions:
- Waits for the next measurement report if the UE measures the neighboring cells;
- Stops the handover procedure if it is a blind handover.
In the handover execution phase, the UE and the eNodeB exchange signaling over the radio interface according to
3GPP TS 36.331. During an inter-eNodeB handover, the source and target eNodeBs exchange signaling and data
through X2/S1 adaptation. The LTE system uses hard handovers, that is, only one radio link is connected to a UE at
a time. Therefore, to prevent user data loss at the eNodeB during the handover, data forwarding is performed to
ensure eNodeB data integrity. Loss of data may cause a decrease in the data transfer ratio and an increase in the data
transfer delay.
Intra-frequency and inter-frequency handovers are both applicable in the architecture shown in the figure here below
that is, intra-eNodeB handover, intra-MME inter-eNodeB handover, and inter-MME inter-eNodeB handover.
In the case of an intra-MME inter-eNodeB handover (handover between eNodeB 1 and eNodeB 2 shown in figure
here above), the source eNodeB checks whether the X2 interface is available between the source and target eNodeBs
or not and then automatically selects a path for the handover as follows:
- If the X2 interface is available, the handover request is sent over the X2 interface. Data forwarding is
also performed over the X2 interface.
- If the X2 interface is unavailable, the handover request is sent over the S1 interface. Data forwarding is
also performed over the S1 interface.
In the case of an inter-MME inter-eNodeB handover (handover between eNodeB 1 and eNodeB 3 shown in the
figure here above), the handover request is sent over the S1 interface. In addition, the source eNodeB checks
whether the X2 interface is available between the source and target eNodeBs or not and then automatically selects a
path for data forwarding as follows:
- If the X2 interface is available, data forwarding is performed over the X2 interface.
- If the X2 interface is unavailable, data forwarding is performed over the S1 interface.
In the case of an inter-RAT handover to the UTRAN or GERAN, the eNodeB sends a handover request and
forwards data over the S1 interface.
According to 3GPP TS 36.331, the UE performs a cell selection procedure and then initiates a procedure of RRC
connection re-establishment towards the selected cell, after a handover failure.
The RRC connection re-establishment may be successful only when the selected cell is one of the prepared cells. A
prepared cell can be one of the following:
The RRC connection re-establishment procedure is of two types: successful re-establishment and failed re-
establishment. This procedure is the same for intra-frequency, inter-frequency and inter-RAT type handover.
A successful re-establishment procedure, according to figure here below, consists of the following
steps:
If the RRC connection re-establishment fails, the UE enters in the idle mode. A failed reestablishment
procedure, according to figure here below, consists of the following steps:
Neighbor relationships define the relationships that the serving cell has with its neighboring cells and they play a
fundamental role in handovers. Neighbor relationship management determines whether to allow the following:
NOTE:
the number of neighboring E-UTRAN cells configured on an eNodeB should not exceed 32, which is specified in
3GPP TS 36.331. The same limitation applies to the neighboring UTRAN cells. If the number of neighboring E
UTRAN or UTRAN cells exceeds 32, certain neighbor relationships cannot be carried in measurement configuration
messages.
To reduce delay, the eNodeB may select a target cell for handover in the absence of the measurement information.
This type of handover is called a blind handover. The candidate cells for a blind handover must be the neighboring
cells with blind-handover priorities other than priority 0. For details about the parameters for blind-handover
priorities, refer to blind handover details here further in the chapter.
Note: these parameters are eRAN6 parameters, so there are no current network values.
6.1.8 Redirection
Redirection is a method of transferring UEs between cells and is a type of handover when "handover" is used as a
generic term. When a handover cannot be performed in an emergency or due to equipment limitations, the eNodeB
sends the UE an RRC Connection Release message, which contains information about a neighboring frequency in
the LTE system or in another RAT system. Using this message, the eNodeB instructs the UE to initiate a random
access procedure towards an inter-frequency or inter-RAT neighboring cell so that the UE can resume its services.
Compared with handovers, redirections do not include a procedure for initiating a handover request towards a
neighboring cell and therefore have lower requirements for equipment capabilities and can rapidly be performed.
The two methods differ in the way to transfer UEs.
The eNodeB supports flash redirections to UTRAN and GERAN. The flash redirection function is controlled by the
ENodeBAlgoSwitch.RedirectSwitch parameter. If a switch under the ENodeBAlgoSwitch.RedirectSwitch parameter
is turned on, the eNodeB includes the system information of the target cell in the redirection command. This enables
the UE to access the target cell sooner because the UE does not need to read the system information.
Only UEs compliant with 3GPP Release 9 or later support fast redirections.
The maximum number of UTRAN or GERAN cells whose system information can be delivered by the eNodeB
during a redirection procedure depends on the value of the InterRatHoComm.CellInfoMaxUtranCellNum or
InterRatHoComm.CellInfoMaxGeranCellNum parameter (indicated as N in the following), respectively.
- In blind handovers, the eNodeB determines target cells in the following two steps. If the
number of available cells is greater than N, the eNodeB selects the first N cells. If the number
is less than N, the eNodeB selects all the available cells.
1. The eNodeB sorts and filters blind-handover target cells. For details about the sorting and
filtering, refer to blind handover here further.
2. The eNodeB filters out the cells whose system information is not acquired.
Note : the eNodeB cannot obtain the system information of a cell that does not support the RIM (RAN Information
Management) procedure.
- If an UE has performed measurements and reported measurement results, the eNodeB determines
target cells in the following steps. If the number of available cells is greater than N, the eNodeB selects
the first N cells. If the number is less than N, the eNodeB selects all the available cells.
1. The eNodeB sorts the cells by measured signal strength in descending order based on the
measurement reports, and adds the cells that are on the redirection target frequencies but not in
measurement reports.
2. The eNodeB filters target cells. For details about the filtering, refer to the section “ Decision on a
Handover.
During a flash redirection procedure, the eNodeB uses the RAN information management (RIM) procedure to
acquire system information of the target cell. To use RIM, ensure that the devices in the core network and target
RAN also support the RIM procedure. Note that only UEs compliant with Release 9 and later releases support the
flash redirection function. For this reason this functionality is currently not in use.
In coverage-based inter-frequency or inter-RAT handovers and CS fallback, blind redirection is triggered if no inter-
frequency or inter-RAT neighboring cells are available. To enable this function, set related parameters. For details
about how to set the parameters, refer to the blind handover in the following section. If no neighbor relationships are
configured, handovers cannot be performed, including the handover, CCO (Cell Change Order), or redirection
procedure.
Note: this function does not take effect when the eNodeB is configured with correct inter-frequency or inter- RAT
neighbor relationships.
If neighbor relationships are missing on an eNodeB, features and functions related to neighbor relationships are
affected. If an eNodeB cannot trigger the RIM procedure to obtain inter-RAT neighboring cell information, all
related features and functions, such as flash redirection, cannot be triggered.
6.1.9.1 Description
"Blind handover" is a generic term for handover, CCO, or redirection for which measurements are not performed.
Blind handovers exclude neighboring cell measurements and therefore reduce the amount of time required for
signaling exchange over the radio interface. If eNodeBs decide to perform blind handovers, they directly enter the
handover execution phase without delivering gap-assisted measurement or measurement configurations. Blind
handovers are used for inter-frequency and inter-RAT mobility. Inter-frequency or inter-RAT blind handovers
require setting of blind-handover priorities for neighboring cells.
In most cases, blind handovers are not recommended, because the absence of neighboring cell measurements
increases the risk of handover failure. However, blind handovers are appropriate in any of the following situations:
- the coverage area of the target cell of a blind handover includes the coverage area of the source cell,
which ensures a successful handover;
- A UE does not support inter-frequency or inter-RAT measurements, in which case only blind
handovers can be performed;
In blind handovers, which exclude neighboring cell measurements, the eNodeB selects the target cell or target
frequency based on the blind-handover priority configuration. The figure here below shows the selection procedure.
The eNodeB selects the target system and frequency supported by the UE. Refer to the next sections for details
about inter-RAT, inter-frequency cases.
3/ The eNodeB filters the blind-handover targets to prevent a blind handover to an inappropriate target.
- Filtering of the target neighboring cells is the same as that in scenarios where the UE has performed
measurements and reported measurement results, refer to decision on a handover section. Basically it is
filtering out the black listed cells, other PLMN,…;
- When filtering target frequencies, the eNodeB filters out the frequencies whose PLMN is different
from the PLMN of the serving cell. The eNodeB identifies the PLMN information of the target
frequencies and then filters these frequencies.
The PLMN ID of a neighboring E-UTRAN frequency can be obtained from the RAN sharing
information and is composed of the values of the EutranNFreqRanShare.Mcc and
EutranNFreqRanShare.Mnc parameters.
The PLMN ID of a neighboring UTRAN frequency can be obtained from the RAN sharing
information and is composed of the values of the UtranRanShare.Mcc and UtranRanShare.Mnc
parameters.
The PLMN ID of a neighboring GERAN frequency can be obtained from the RAN sharing
information and is composed of the values of the GeranRanShare.Mcc and GeranRanShare.Mnc
parameters.
4/ After filtering the blind-handover targets, the eNodeB performs the following operation:
- If neighboring cells for the blind handover are available, the eNodeB selects the neighboring cell with
the highest blind-handover priority as the target cell.
- If multiple cells have the highest blind-handover priority, the eNodeB randomly selects one from them.
If the blind handover needs to be performed in the form of a redirection, the eNodeB queries the
frequency or frequency group on which the target cell operates and performs a redirection.
The EutranInterFreqNCell.BlindHoPriority parameter specifies the blind-handoverpriority of
an E-UTRAN inter-frequency neighboring cell.
The UTRANNCELL.BlindHoPriority parameter specifies the blind-handover priorityof a
UTRAN neighboring cell.
The GERANNCELL.BlindHoPriority parameter specifies the blind-handover priorityof a
GERAN neighboring cell.
- If no neighboring cell for the blind handover is available, the eNodeB selects a frequencybased on the
EUTRANINTERNFREQ.ConnFreqPriority or GERANNFREQGROUP.ConnFreqPriority parameter
setting and performs a redirection to the selected frequency.
Notes:
If RAN sharing is not configured for a neighboring frequency, the eNodeB cannot initiate a blind
redirection to that frequency;
If the eNodeB cannot find a target cell for the blind handover or a target frequency for the blind
redirection, the eNodeB does not perform the blind handover;
For SPID-based Handover back to the HPLM, refer to the documentation, this is usually not used;
For inter PLMN, please refer to the documentation, this is usually not used;
Note: several parameters are introduced in eRAN6, so there are no current network values for all parameters (current
network is eRAN3). No value means that the parameter is introduced in eRAN6, they are also writen in italic.
Huawei
Huawei Current
Parameter Table Current GUI Values
Parameter ID Values
Name
EutranVoipCapSwitch-0
&UtranVoipCapSwitch-0
&GeranVoipCapSwitch-0
&Cdma1xRttVoipCapSwitch-0
&UtranPsHoSwitch-1
&GeranPsHoSwitch-0
&CdmaHrpdNonOtpimisedHoSwitch-0
&CdmaHrpdOptimisedHoSwitch-0
Handover Mode &GeranNaccSwitch-0
HoModeSwitch ENodeBAlgoSwitch inactive
switch &GeranCcoSwitch-0
&UtranSrvccSwitch-0
&GeranSrvccSwitch-0
&Cdma1xRttSrvccSwitch-0
&UtranRedirectSwitch-1
&GeranRedirectSwitch-1
&CdmaHrpdRedirectSwitch-0
&Cdma1xRttRedirectSwitch-0
&BlindHoSwitch-0
InterRatHighest Highest priority CSFallBackBlindHo
GERAN GERAN
Pri InterRat Cfg
InterRatSecond Second priority CSFallBackBlindHo
UTRAN UTRAN
Pri InterRat Cfg
InterRatLowest Lowest priority CSFallBackBlindHo
CDMA2000 CDMA2000
Pri InterRat Cfg
Connect
ConnFreqPrior
frequency EutranInterNFreq
ity
priority
Connect
ConnFreqPrior
frequency UtranNFreq
ity
priority
Connect
ConnFreqPrior
frequency GeranNfreqGroup
ity
priority
Mobile country EutranNFreqRanSha
MCC
code re
Mobile network EutranNFreqRanSha
MNC
code re
Mobile country
MCC UtranRanShare
code
Mobile network
MNC UtranRanShare
code
Notes:
(*) Regarding the parameter “BlindHOPriority”, only one neighbour can be defined as target, usually it is the co-
located cell, if there is no co-located cell, another can be defined, the most probable one. Although the system send
all neighbour information.
Blind HO.xlsx
The eNodeB delivers the measurement configuration related to event A2 to a UE in connected mode to monitor the
signal quality of the serving cell. The eNodeB may deliver measurement configurations for two types of events A2
to the UE: event A2 for inter-RAT measurement, and event A2 for blind handover. If the signal quality in the
serving cell is lower than the specified threshold, the UE reports event A2 for inter-RAT measurement. After
receiving the report, the eNodeB delivers an inter-RAT measurement configuration to instruct the UE to perform
inter-RAT measurement. If the signal quality in the serving cell further deteriorates and the eNodeB does not
perform a handover for the UE, the UE reports event A2 for blind handover. After receiving the report, the eNodeB
considers that the serving cell can no longer provide services for the UE and performs a blind handover. The
switches UtranRedirectSwitch and GeranRedirectSwitch under the ENodeBAlgoSwitch.HoModeSwitch parameter
specify whether coverage-based handovers to GERAN and UTRAN cells are enabled, respectively.
In a coverage-based inter-RAT handover, event A2 triggers inter-RAT measurements. The triggering of this event
indicates that the signal quality in the serving cell is lower than a specified threshold. When the triggering condition
of event A2 is met, event A2 is reported to the eNodeB.
After this, the eNodeB sends the inter-RAT measurement configuration to the UE. The 3GPP TS 36.331 defines the
entering and leaving conditions of event A2 as follows:
Where,
Ms: is the measurement result of the serving cell, not taking into account any offsets;
The threshold for event A2, can be specified by either the InterRatHoCommGroup.InterRatHoA2ThdRSRP
parameter or the InterRatHoCommGroup.InterRatHoA2ThdRSRQ parameter, depending on the setting of the
InterRatHoComm.InterRatHoA1A2TrigQuan parameter (triggering quantity for inter-RAT measurement events A1
and A2). The threshold parameters InterRatHoCommGroup.InterRatHoA2ThdRSRP and
InterRatHoCommGroup.InterRatHoA2ThdRSRQ correspond to the triggering quantity settings RSRP and RSRQ,
respectively. Note that RSRQ is only used since 3Gpp Rel. 9.
For inter-RAT measurement event A2, the eNodeB specifies two sets of parameters, with respect to the RSRP and
RSRQ quantities. When InterRatHoComm.InterRatHoA1A2TrigQuan is set to BOTH, event A2 is reported
and the eNodeB delivers the inter-RAT measurement configuration to the UE if the signal quality in the serving cell
is lower than the threshold (either the value of InterRatHoCommGroup.InterRatHoA2ThdRSRP or the value of
InterRatHoCommGroup.InterRatHoA2ThdRSRQ) minus the hysteresis throughout the timeto-trigger specified by
theInterRatHoCommGroup.InterRatHoA1A2TimeToTrig parameter.
When InterRatHoComm.InterRatHoA1A2TrigQuan is set to RSRP or RSRQ, event A2 is reported if the signal
quality in the serving cell is lower than the related threshold minus the hysteresis throughout the time-to-trigger
specified by the InterRatHoCommGroup.InterRatHoA1A2TimeToTrig parameter.
After receiving an event A2 report that triggers inter-RAT measurements, the eNodeB delivers the measurement
configuration related to event B1 to the UE. For details, refer to Inter-RAT Handover Triggering here below.
As in coverage-based inter-frequency handovers (see here further in this document), the eNodeB may not deliver the
measurement configuration related to inter-RAT measurement event A2. For details, refer to Blind-Handover
Triggering by Event A2.
Huawei Parameter
Huawei Parameter ID Table
Name
InterRAT A2 RSRP InterRatHoCommG
InterRatHoA2ThdRSRP
trigger threshold roup
Event A2 specific to a target RAT can be configured on the eNodeB. This ensures that the eNodeB can
preferentially perform a coverage-based handover to a UTRAN or GERAN cell.
Notes:
- The CnOperatorHoCfg.UtranA2ThdRsrpOffset and CnOperatorHoCfg.GeranA2ThdRsrpOffset
parameters do not affect the RSRQ thresholds for inter-RAT measurement event A2;
- If the calculated RSRP threshold for inter-RAT measurement event A2 is less than the
protocolspecified minimum value, the protocol-specified minimum value is used. If the calculated
RSRP threshold for inter-RAT measurement event A2 is greater than the protocol-specified maximum
value, the protocol-specified maximum value is used;
In a coverage-based inter-RAT handover, event A1 stops inter-RAT measurements. The triggering of event A1
indicates that the signal quality in the serving cell is higher than a specified threshold. The 3GPP TS 36.331 defines
the entering and leaving conditions of event A1 as follows:
Where,
Ms: is the measurement result of the serving cell, not taking into account any offsets;
The event A1 threshold must be higher than the event A2 threshold to ensure that event A1 can stop inter-RAT
measurements in coverage-based inter-RAT handovers. If the CnOperatorHoCfg.UtranA2ThdRsrpOffset or
CnOperatorHoCfg.GeranA2ThdRsrpOffset parameter is set, ensure that the event A1 threshold is higher than or
equal to the sum of the CnOperatorHoCfg.UtranA2ThdRsrpOffset or CnOperatorHoCfg.GeranA2ThdRsrpOffset
parameter value and the event A2 threshold.
Huawei Parameter
Huawei Parameter ID Table
Name
InterRatHoA1ThdRSRP InterRAT A1 RSRP InterRatHoCommG
In coverage-based inter-frequency or inter-RAT handovers, the eNodeB can deliver a measurement configuration
related to event A2 for blind handovers if the signal quality of the serving cell deteriorates to a specified level but
the UE has not yet been handed over. If the EmcInterFreqBlindHoSwitch option of the
ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected, the eNodeB selects an inter-frequency target cell when
the UE sends a report of event A2 for a blind handover.
If the EmcBlindHoA1Switch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is selected, the eNodeB
records the reports of event A2 for blind handovers during handover preparation and handles them if the handover
preparation fails. In addition, the eNodeB also delivers the measurement configuration related to event A1 used to
stop a blind handover in case the signal quality in the serving cell further deteriorates. If the eNodeB receives a
report of event A1 used to stop a blind handover from the UE before the blind handover starts, the eNodeB will not
perform the blind handover.
Event A2 for blind handover can trigger both inter-frequency and inter-RAT blind handovers. The event A2
thresholds and processing mechanisms are the same for inter-frequency and inter- RAT blind handovers.
The CellHoParaCfg.BlindHoA1A2ThdRsrp and CellHoParaCfg.BlindHoA1A2ThdRsrq parameters specify the
RSRP threshold and RSRQ threshold, respectively, for events A1 and A2 that are used for coverage-based inter-
frequency and inter-RAT blind handovers.
Other parameters related to events A1 and A2 are specified by parameters for inter-RAT blind handovers: the
triggering quantity is specified by the INTERRATHOCOMM.InterRatHoA1A2TrigQuan parameter, the hysteresis
by INTERRATHOCOMMGROUP.InterRatHoA1A2Hyst, and the time-to-trigger by the
INTERRATHOCOMMGROUP.InterRatHoA1A2TimeToTrig parameter.
The eNodeB delivers event A2 for blind handover but not event A2 for inter-frequency or inter- RAT measurement
if both the following conditions are met:
The blind handover is implemented only by performing a redirection procedure, because an event A2-triggered blind
handover indicates an urgent situation where the serving cell cannot provide the required service quality. However,
if VoIP services are running on the UE that reports event A2 for blind handover, the eNodeB does not perform an
inter-frequency redirection for the UE.
Refer to the Blind-Handover section above in this document for detailed parameters.
In the measurement configuration for inter-RAT handover, the information on measurement objects is set for each
RAT; each measurement object can be linked to one or more reporting configurations and each reporting
configuration can also be linked to one or more measurement objects. The measurement configuration includes the
following basic information:
In the case of GERAN, the information on a measurement object includes the group of neighboring GERAN carrier
frequencies GERANNFREQGROUP and the frequencyspecific offset for the group
GERANNFREQGROUP.OffsetFreq.
Huawei Parameter
Huawei Parameter ID Table
Name
OffsetFreq Frequency offset UTRANNFREQ
Downlink
UtranDlArfcn UTRANNFREQ
UARFCN
GERANNFREQGR
OffsetFreq Frequency offset
OUP
GERANNFREQGR
StartingArfcn Starting ARFCN
OUP
GERANNFREQGR
BandIndicator Band indicator
OUP
Note: these are per neighbour parameters, so several values are possible, like for the frequencies. This is network
dependent. For GERAN, the band indicator is important in order to differenciate channels in DCS and PCS.
Huawei Parameter
Huawei Parameter ID Table
Name
CoverageBased
InterRatHoUtranB1ThdEcn InterRatHoUtranGr
UTRAN ECN0
0 oup
trigger threshold
CoverageBased
InterRatHoUtranB1ThdRsc InterRatHoUtranGr
UTRAN RSCP
p oup
trigger threshold
UTRAN handover InterRatHoUtranGr
InterRatHoUtranB1Hyst
hysteresis oup
InterRatHoUtranB1TimeTo UTRAN time to InterRatHoUtranGr
Trig trigger oup
InterRatHoUtranB1MeasQ Utran measurement
InterRatHoComm
uan trigger quantity
Note: the parameters without values, and writen in italic, are from eRAN6, so currently not in the network.
- The measurement quantity configuration for UTRAN FDD defines the measurementquantity
(InterRatHoComm.InterRATHoUtranB1MeasQuan) and filtering coefficients
(HoMeasComm.UtranFilterCoeffRSCP and HoMeasComm.UtranFilterCoeffECN0);
These parameters have been defined already here above an in previous section (Filtering).
Refer to the section here above for details about the GAP.
Where,
Mn: is the measurement result of the neighbouring cell, not taking into account any offsets;
Ofn: is the frequency-specific offset for the frequency of the neighboring cell. It is specified by the
UtranNFreq.OffsetFreq parameter, for a UTRAN cell and by the GeranNfreqGroup.OffsetFreq parameter for a
GERAN cell. The offset is contained in the associated measurement object IE in the measurement configuration.
Hys: is the hysteresis for event B1. The hysteresis values for inter-RAT handovers to UTRAN and GERAN
specified by the InterRatHoUtranGroup.InterRATHoUtranB1Hyst and
InterRatHoGeranGroup.InterRATHoGeranB1Hyst parameters, respectively are included in the delivered
measurement configuration.
Thresh: Thresh is the threshold for event B1. The values of Thresh are set on the basis of the measurement quantities
for each RAT.
Note:
The 3GPP TS 36.331 specifies that UEs can report RSCP and Ec/No quantities of the UTRAN at the same time. For
UEs that are compliant with earlier releases, the eNodeB sends only the RSCP-related measurement configuration to
the UEs even if the InterRatHoComm.InterRATHoUtranB1MeasQuan parameter is set to UTRAN_BOTH.
When the quantity-based measurement result meets the triggering condition of event B1, the UE reports the
information about the cell where the event is triggered to ensure that the inter-RAT handover is triggered in a timely
fashion. The time-to-trigger for event B1 related to handovers to UTRAN and GERAN is specified by the
InterRatHoUtranGroup.InterRATHoUtranB1TimeToTrig and
InterRatHoGeranGroup.InterRATHoGeranB1TimeToTrig parameters, respectively.
These parameters can be set to different values to differentiate the rates for reporting event B1 related to handovers
to UTRAN and GERAN. The eNodeB sends a handover request to the intereRAN RAT neighboring cell for which
event B1 is reported first. For example, if the value of the InterRatHoGeranGroup.InterRATHoGeranB1TimeToTrig
parameter is greater than the value of the InterRatHoUtranGroup.InterRATHoUtranB1TimeToTrig parameter and a
UE reports event B1 for a handover to UTRAN first, the eNodeB preferentially sends a handover request to a
neighboring UTRAN cell.
Networ
k Measurement Quantity HO Type Parameter Thres.
Coverage-based
UL Quality-based InterRatHoUtranGroup.
InterRATHoUtranB
Distance-based 1ThdRSCP
RSCP
SPID-based HO to HPLMN
Load-based InterRatHoUtranGroup.
LdSvBasedHoUtran
Service-based B1ThdRSCP
UTRAN
Coverage-based
UL Quality-based InterRatHoUtranGroup.
InterRATHoUtranB
Distance-based 1ThdEcN0
Ec/No
SPID-based HO to HPLMN
Load-based InterRatHoUtranGroup.
LdSvBasedHoUtran
Service-based B1ThdECN0
Coverage-based
UL Quality-based InterRatHoGeranGroup.
InterRATHoGeran
GERAN RSSI Distance-based B1Thd
Load-based InterRatHoGeranGroup.
LdSvBasedHoGera
Service-based nB1Thd
The 3GPP TS 36.331shows the following B1-related parameters are provided in the reporting configuration of the
measurement configuration:
- InterRatHoComm.InterRATHoUtranRprtInterval and
InterRatHoComm.InterRATHoGeranRprtInterval: specify the interval between the reports that are
triggered by event B1. This parameter controls the frequency of the periodical measurement reports
sent by the UE. This reduces the signaling load on the radiointerface.
Parameters:
Huawei Parameter
Huawei Parameter ID Table
Name
OffsetFreq Frequency offset GeranNfreqGroup
OffsetFreq Frequency offset UtranNFreq
CoverageBased InterRatHoGeranGr
InterRatHoGeranB1Thd GERAN trigger oup
threshold
InterRatHoGeranB1TimeTo GERAN time to InterRatHoGeranGr
Trig trigger oup
GERAN handover InterRatHoGeranGr
InterRatHoGeranB1Hyst
hysteresis oup
CoverageBased InterRatHoUtranGr
InterRatHoUtranB1ThdEcn
UTRAN ECN0 oup
0
trigger threshold
CoverageBased InterRatHoUtranGr
InterRatHoUtranB1ThdRsc
UTRAN RSCP oup
p
trigger threshold
UTRAN handover InterRatHoUtranGr
InterRatHoUtranB1Hyst
hysteresis oup
InterRatHoUtranB1TimeTo UTRAN time to InterRatHoUtranGr
Trig trigger oup
InterRatHoUtranB1MeasQ Utran measurement
InterRatHoComm
uan trigger quantity
UTRAN FDD
InterRATHoUtranRprtInter
measurement InterRatHoComm
va
report interval
Geran
InterRATHoGeranRprtInter
measurement InterRatHoComm
val
report interval
Max report cell
InterRATHoMaxRprtCell InterRatHoComm
number
Measurement
InterRATHoRprtAmount InterRatHoComm
report amount
Parameter details:
B1 parameter
details.xlsx
The triggering of event B2 indicates that the signal quality in the serving cell is lower than a specified threshold and
the signal quality in at least one neighboring cell is higher than another specified threshold. The 3GPP TS 36.331
defines the entering and leaving conditions of event B2 as follows:
Ms + Hys < Thresh 1 and Mn + Ofn + Ocn - Hys > Thresh 2 (entering condition)
Ms - Hys > Thresh 1 or Mn + Ofn + Ocn + Hys < Thresh 2 (leaving condition)
Event B2 uses the same set of parameters as event B1 except for parameters: the triggering quantity related to
Thresh 1, the measurement quantity related to Thresh 2, Thresh 1, and Thresh 2.
The Thresh 1 triggering parameters for event B2 are the same as the one used for event A2.
Huawei Parameter
Huawei Parameter ID Table
Name
InterRAT A2 RSRP InterRatHoCommG
InterRatHoA2ThdRSRP
trigger threshold roup
The eNodeB decides whether to perform an inter-RAT handover for a UE. Some details have been given already
here above in this chapter (Decision on a Handover).
If the eNodeB receives measurement reports about different RATs, it processes the reports in a First In First Out
(FIFO) manner.
In the decision phase of a service-based inter-RAT handover, the eNodeB decides not to perform a handover for a
UE if the eNodeB detects that a service for which handover is not allowed is running on the UE.
In a coverage-based inter-RAT handover, if the UE reports that it does not support inter-RAT handovers, the
eNodeB decides to perform a redirection to transfer the UE to an inter-RAT neighboring cell. Following these:
- If the UE does not support inter-RAT measurements and handovers and if at least one neighboring cell
of that RAT has been assigned a blind-handover priority, the eNodeB makes a blind-redirection
decision based on the event A2 report. If the eNodeB decides to perform a blind redirection, it sends an
RRC Connection Release message to the UE;
- If the UE supports measurements on an inter-RAT system but does not support handovers to that
system, the eNodeB delivers corresponding inter-RAT measurement configurations to the UE. If the
triggering condition of event B1 or B2 is met, the eNodeB sends the UE an RRC Connection Release
message, instructing the UE to perform a redirection to an inter-RAT neighboring cell.
The following inter-RAT handover policies are available: PS HO, SRVCC, CCO/NACC, and redirection.
The eNodeB can configure a specific inter-RAT handover policy for each standardized or extended QCI. The policy
ID is specified by the InterRatPolicyCfgGroup.InterRatPolicyCfgGroupId parameter. For a combined service, the
policy is selected based on the highest-priority QCI:
Note:
Do not change the inter-RAT handover policy for each QCI unless necessary.
In the execution phase of an inter-RAT handover, the eNodeB tries the next best cell among the candidate cells to
initiate the handover if the admission to the target cell fails. If the handover still fails to be initiated after the eNodeB
Notes:
- Based on the cause of failure, admission failure can be classified into two types: resource-induced and
non-resource-induced. After a handover request is sent from the source cell to the target cell, the
admission control of the target cell is performed. If the target cell responds with a resource preparation
failure message, this admission failure is called resource-induced failure. If the target cell responds
with other failure messages or does not return any message within a specified time, this admission
failure is called non-resource-induced failure.
- The radio interface failure is the handover procedure failure caused by failure in transmitting
signalingmessages over the radio interface after the source eNodeB sends the handover command.
This parameter setting is valid for both L800 and L1800, single or dual layer sites.
Where,
Ms: is the measurement result of the serving cell, not taking into account any offsets;
Thresh is the threshold for event A2. It can be specified by either the InterFreqHoGroup.InterFreqHoA2ThdRSRP
parameter or the InterFreqHoGroup.InterFreqHoA2ThdRSRQ parameter, depending on the setting of the
IntraRatHoComm.InterFreqHoA1A2TrigQuan parameter (triggering quantity for interfrequency measurement
events A1 and A2). The threshold parameters InterFreqHoGroup.InterFreqHoA2ThdRSRP and
InterFreqHoGroup.InterFreqHoA2ThdRSRQ correspond to the triggering quantity settings RSRP and RSRQ,
respectively.
For inter-frequency measurement event A2, the eNodeB specifies two sets of parameters, with respect to the RSRP
and RSRQ quantities.
When IntraRatHoComm.InterFreqHoA1A2TrigQuan is set to BOTH, event A2 is reported and the eNodeB delivers
the inter-frequency measurement configuration to the UE if the signal quality in the serving cell is lower than the
threshold (either the value of InterFreqHoGroup.InterFreqHoA2ThdRSRP or the value of
InterFreqHoGroup.InterFreqHoA2ThdRSRQ) minus the hysteresis throughout the time-totrigger specified by the
InterFreqHoGroup.InterFreqHoA1A2TimeToTrig parameter. When IntraRatHoComm.InterFreqHoA1A2TrigQuan
is set to RSRP or RSRQ, event A2 is reported if the signal quality in the serving cell is lower than the related
threshold minus the hysteresis throughout the time-to-trigger specified by the
InterFreqHoGroup.InterFreqHoA1A2TimeToTrig parameter.
After event A2 is reported, the eNodeB delivers the measurement configuration related to event A3, A4, or A5 to the
UE. For details about the triggering of inter-frequency handovers, refer to Inter-Frequency Handover Triggering
here further. In this case only event A3 and A4 are used. Event A5 is not part of this document.
The eNodeB may not deliver the measurement configuration related to inter-frequency measurement event A2. For
details, see Blind-Handover Triggering by Event A2.
Parameters
Huawei Parameter
Huawei Parameter ID Table
Name
Parameters details
HO Inter-freq
meas.xlsx
This refer to inter-freq between LTE FDD and LTE TDD. This is not the case for this network.
Where,
Ms: is the measurement result of the serving cell, not taking into account any offsets;
When IntraRatHoComm.InterFreqHoA1A2TrigQuan is set to Both, event A1 is reported if the signal quality in the
serving cell remains higher than the threshold (either the value of InterFreqHoGroup.InterFreqHoA1ThdRSRP or
the value of InterFreqHoGroup.InterFreqHoA1ThdRSRQ) plus the hysteresis throughout the time-to-trigger period.
If neither of the RSRP and RSRQ measurement results in an event A1 report meets the leaving condition for event
A1, the eNodeB stops the coverage-based inter-frequency measurement.
The event A1 threshold must be higher than the event A2 threshold to ensure that event A1 can stop inter-frequency
measurements in coverage-based inter-frequency handovers. If the CnOperatorHoCfg.FddIfHoA2ThdRsrpOffset
parameter is set, ensure that the event A1 threshold is higher than or equal to the sum of the
CnOperatorHoCfg.FddIfHoA2ThdRsrpOffset parameter value and the RSRP threshold for inter-frequency
measurement event A2.
Parameters
Huawei Parameter
Huawei Parameter ID Table
Name
Interfreq A1 RSRP
InterFreqHoA1ThdRSRP InterFreqHoGroup
threshold
Interfreq A1 RSRQ
InterFreqHoA1ThdRSRQ InterFreqHoGroup
threshold
LTE FDD inter-freq
FddIfHoA2ThdRsrpOffset A2 Threshold CnOperatorHoCfg
RSRP Offset
Parameter details
HO Inter-freq meas
A1.xlsx
Parameters
Huawei Parameter
Huawei Parameter ID Table
Name
Downlink
DlEarfcn EUTRANINTERNFREQ
EARFCN
Measurement
MeasBandWidth EUTRANINTERNFREQ
bandwidth
QoffsetFreq Frequency offset EUTRANINTERNFREQ
Interfreq handover
InterFreqHoA4Hyst InterFreqHoGroup
hysteresis
Interfreq HandOver
InterFreqHoA4TimeToTrig InterFreqHoGroup
Time to Trigger
Max report cell
IntraRATHoMaxRprtCell IntraRatHoComm
number
InterFreq A1A2
InterFreqHoA1A2TrigQuan Measurement IntraRatHoComm
trigger quantity
Measurement A4
InterFreqHoA4RprtQuan IntraRatHoComm
report quantity
Interfreq
InterFreqHoRprtInterval measurement report IntraRatHoComm
interval
Measurement report
IntraRATHoRprtAmount IntraRatHoComm
amount
Parameter details
HO Inter-freq meas
config.xlsx
The gap-assisted mode is applied to inter-frequency measurements. The eNodeB delivers the measurement gap
configuration in the Measurement Configuration message for inter-frequency measurement. From the measurement
gap configuration, the UE can acquire the start time of the gaps, repetition period, and gap width. Based on this, the
UE performs inter-frequency measurements within the gaps.
The gap-assisted measurement may conflict with Discontinuous Reception (DRX), semipersistent scheduling, or
both. In the case of this conflict, the gap-assisted measurement takes precedence. This, however, affects data
transmission quality. To solve this problem, the design of measurement gaps takes DRX and semi-persistent
scheduling into consideration. The start time of the measurement gaps can be adjusted in a way that the conflicts
with DRX, semipersistent scheduling, or both are minimized whereas gap-assisted measurements are performed
in a timely fashion.
Refer to the section here above for details about the GAP.
Parameters
Huawei Parameter
Huawei Parameter ID Table
Name
Inter-Freq HO
InterFreqHoEventType EutranInterNFreq
trigger Event Type
Parameter details
HO Inter-freq
trigg.xlsx
For details about how event A3 is triggered, refer to Event A3 Triggering in the intra-frequency
Handovers section in this document.
Event A3 in inter-frequency handovers uses the same set of parameters with that in intra-frequency
handovers, except the offset and frequency-specific offset. Specifically, the offset for this event A3 is specified by
the InterFreqHoGroup.InterFreqHoA3Offset parameter and applies to all inter-frequency handovers triggered by this
event A3, and the frequency-specific offset is specified by the EutranInterNFreq.QoffsetFreq parameter for each
neighboring EUTRAN frequency.
The measurement quantities for events A1 and A2 are both RSRP. The RSRP thresholds for triggering events A1
and A2 are specified by the InterFreqHoGroup.A3InterFreqHoA1ThdRsrp and
InterFreqHoGroup.A3InterFreqHoA2ThdRsrp parameters, respectively.
Huawei Parameter
Huawei Parameter ID Table
Name
InterFreqHoA3Offset nterfreq A3 offset InterFreqHoGroup
QoffsetFreq Frequency offset EutranInterNFreq
A3 based interfreq
A3InterFreqHoA1ThdRsrp InterFreqHoGroup
A1 RSRP threshold
A3 based Interfreq
A3InterFreqHoA2ThdRsrp InterFreqHoGroup
A2 RSRP threshold
Parameter details
HO Inter-freq trigg
A3.xlsx
The triggering of event A4 indicates that the signal quality is higher than a specified threshold in at least one
neighboring cell. The 3GPP TS 36.331 defines the entering and leaving conditions of event A4 as follows:
Where,
Ofn is the frequency-specific offset for the frequency of the neighboring cell. It is specified by the
EutranInterNFreq.QoffsetFreq parameter, which is contained in the associated measurement object IE in the
measurement configuration. This parameter adjusts the probability of triggering a handover to a specific frequency.
For example, a cell on frequency A and a cell on frequency B are both candidate cells for a handover. Then, the
offset for frequency A can be increased to raise the probability of selecting the cell on frequency A as the target cell.
The value of a frequency-specific offset can be either positive or negative. A positive value raises the handover
triggering probability, and a negative value lowers the probability.
Ocn is the cell-specific offset for the neighboring cell. It is specified by the
EutranInterFreqNCell.CellIndividualOffset parameter. If the value of this parameter is not 0, the eNodeB delivers
this parameter to the UE through the measurement configuration. If the value is 0, the eNodeB does not deliver this
parameter. In this case, the UE uses the default value 0.
Hys is the hysteresis for event A4. It is specified by the InterFreqHoGroup.InterFreqHoA4Hyst parameter and
contained in the delivered measurement configuration.
Note:
If the IntraRatHoComm.InterFreqHoA4TrigQuan parameter is set to BOTH, both the RSRP- and RSRQ-based
measurement configurations are delivered. If the IntraRatHoComm.InterFreqHoA4RprtQuan parameter is set to
BOTH, an inter-frequency handover can be triggered only when the RSRP- and RSRQ-based measurement results
of at least one neighboring cell meet the conditions specified in the corresponding measurement configurations.
You can set offset for the RSRP threshold for event A4 related to coverage-based inter-frequency handover. The
offset is specified by the EutranInterNFreq.IfHoThdRsrpOffset parameter. If this parameter is set, the RSRP
threshold for event A4 related to coverage-based inter-frequency handover is the sum of
InterFreqHoGroup.InterFreqHoA4ThdRSRP and EutranInterNFreq.IfHoThdRsrpOffset.
The figure here below shows the event A4 triggering mechanism. When the RSRP- or RSRQ-based measurement
result meets the triggering condition of event A4, the UE reports the information about the cell where the event is
triggered, to ensure that the inter-frequency handover is triggered in a timely fashion.
According to the 3GPP TS 36.331, the following A4-related parameters are provided in the reporting configuration
of the measurement configuration:
Parameters
Huawei Parameter
Huawei Parameter ID Table
Name
QoffsetFreq Frequency offset EutranInterNFreq
Cell individual
CellIndividualOffset EutranInterFreqNCell
offset
Interfreq handover
InterFreqHoA4Hyst InterFreqHoGroup
hysteresis
Interfreq HandOver
InterFreqHoA4TimeToTrig InterFreqHoGroup
Time to Trigger
FreqPrior
loadBased A4
InterFreqHoA4TrigQuan IntraRatHoComm
Measurement
trigger quantity
Measurement A4
InterFreqHoA4RprtQuan IntraRatHoComm
report quantity
Max report cell
IntraRATHoMaxRprtCell IntraRatHoComm
number
Interfreq
InterFreqHoRprtInterval measurement IntraRatHoComm
report interval
Measurement
IntraRATHoRprtAmount IntraRatHoComm
report amount
IfHoThdRsrpOffset EutranInterNFreq
CoverageBased
InterFreqHoA4ThdRSRP Interfreq RSRP InterFreqHoGroup
threshold
CoverageBased
InterFreqHoA4ThdRsrq Interfreq RSRQ InterFreqHoGroup
threshold
Parameter details
HO Inter-freq trigg
A4.xlsx
Coverage-based intra-frequency handovers are addressed by the basic feature LBFD-00201801 Coverage Based
Intra-frequency Handover.
When a UE establishes a radio bearer, the eNodeB sends the UE the intra-frequency measurement configuration,
according to which the UE performs measurements. When the UE moves from the serving cell to an intra-frequency
neighboring cell, the eNodeB initiates a coverage-based intra-frequency handover if the measurement results
indicate that the signal quality in the neighboring cell is higher than that in the serving cell and the related threshold
is reached. It is enabled or disabled by the switch IntraFreqCoverHoSwitch under the
ENodeBAlgoSwitch.HoAlgoSwitch parameter.
The intra-frequency measurement results are the basis for the eNodeB to make an intra-frequency handover
decision. After a UE establishes a radio bearer, the eNodeB delivers the measurement configuration to the UE in an
RRC Connection Reconfiguration message. When the UE is in connected mode or a handover is completed, the
eNodeB checks whether the measurement configuration for the UE needs to be updated.
- If the configuration needs to be updated, the eNodeB delivers the entirely or partially updated
measurement configuration to the UE through an RRC Connection Reconfiguration message.
- If the configuration does not need to be updated, the eNodeB does not deliver updated measurement
configuration. In this case, the UE uses the original measurement configuration.
Based on the measurement configuration, the UE measures all cells on the associated frequency within the
measurement scope. If the measurement result meets the entering condition of event A3 for a period defined by
time-to-trigger, the UE reports the measurement result to the eNodeB. After the reporting, if the measurement result
meets the leaving condition of the event throughout the time-to-trigger, the UE stops reporting the measurement
result to the eNodeB.
6.4.1.2 Event A3
Intra-frequency handovers are triggered by event A3, which is reported in event-triggered periodical reporting mode.
The triggering of event A3 indicates that at least one neighboring cell is offset better than the serving cell. Section
The 3GPP TS 36.331 defines the entering and leaving conditions of event A3 as follows:
Where,
Ofn is the frequency-specific offset for the frequency of the neighboring cell. It is specified by the
CELL.QoffsetFreq parameter. This variable is contained in the associated measurement object IE in the
measurement configuration.
Ocn is the cell-specific offset (that is, CIO) for the neighboring cell. It is specified by the
EUTRANINTRAFREQNCELL.CellIndividualOffset parameter. If the value of this parameter is not 0, the eNodeB
delivers this parameter to the UE through the measurement configuration. If the value is 0, the eNodeB does not
deliver this parameter. In this case, the UE uses the default value 0.
Ofs is the frequency-specific offset for the serving frequency. It is specified by the CELL.QoffsetFreq parameter.
This variable is contained in the associated measurement object IE in the measurement configuration.
Ocs is the cell-specific offset for the serving cell. It is specified by the Cell.CellSpecificOffset parameter. This
parameter is contained in the associated measurement object IE in the delivered measurement configuration.
Hys is the hysteresis for event A3. It is specified by the IntraFreqHoGroup.IntraFreqHoA3Hyst parameter and
contained in the delivered measurement configuration.
Off is the offset for event A3. It is specified by the IntraFreqHoGroup.IntraFreqHoA3Offset parameter. This A3-
specific parameter adjusts the probability of triggering handovers. The sum of the value of this parameter and the
measurement result is used in the evaluation of event reporting. This parameter is contained in the associated
measurement object IE in the delivered measurement configuration. The value of this parameter can be either
positive or negative. A positive value lowers the probability of triggering the event for handovers, and a negative
value raises the probability.
For example: Both Hys and Off are set to 2 dB. Tests show that the signal quality in the source cell always drops
rapidly and the signal quality in the target cell always rises quickly during handovers. In this situation, to facilitate
handovers from the serving cell to the neighboring cell, the eNodeB sets Ocs to -1 dB and Ocn to 1 dB. In addition,
Ofs and Ofn for intra-frequency handovers are the same and assume that they take the value of 0 dB. Therefore, in
this situation, the entering condition of event A3 is as follows:
Mn + 0 + 1 - 2 > Ms + 0 - 1 + 2
This means that the entering condition is met provided that the measurement result of the neighboring cell is 2 dB
greater than that of the serving cell.
If the entering condition of the event is met throughout the time specified by
IntraFreqHoGroup.IntraFreqHoA3TimeToTrig, the UE reports event A3 and starts the event-triggered periodical
reporting. Then, if the leaving condition of the event is met throughout the time specified by
Parameters
Parameter details:
HO Intra-freq
meas.xlsx
The retry and penaly are the same as for inter-RAT and inter-frequency handover, refer to the inter-RAT handover
section.
7.1 ANR
This chapter describes the Automatic Neighbor Relation (ANR) management feature. The functionality and the
related current parameters are listed and provided with their respective decriptions.
This document covers the following features:
The figure here below gives a global view of ANR as it exist in eRAN6. Only the intra-RAT ANR (event triggered
ANR) will be detailed in this chapter.
7.1.1.2 Concept
The NCLs of an eNodeB contain information about the external cells of the eNodeB, which belong to other base
stations.
NCLs are classified as intra-RAT NCLs and inter-RAT NCLs. Each eNodeB has one intra-RAT NCL and multiple
inter-RAT NCLs. Only intra-RAT are addressed here in this document.
The intra-RAT NCL records information such as the E-UTRAN cell global identifiers (ECGIs), PCIs, and E-UTRA
absolute radio frequency channel numbers (EARFCNs) of the external E-UTRAN cells. The information is
contained in EutranExternalCell managed objects (MOs).
NCLs are used as the basis for creating neighbor relations. ANR can automatically add or remove external cells
from NCLs.
HO Blacklist
An HO blacklist contains information about neighbor relations that cannot be used for a handover
or removed automatically from the NRT by ANR. The neighbor relations in the HO blacklist must
meet both of the following conditions:
Neighbor relations can manually be added to the HO blacklist. For details, refer to 3GPP TS 32.511.
X2 Blacklist
An X2 blacklist contains information about the neighboring eNodeBs with which the local
eNodeB is not permitted to set up X2 interfaces. If an X2 interface has been set up between the
local eNodeB and a neighboring eNodeB in the X2 blacklist, this X2 interface is removed
automatically.
RRC Blacklist
An RRC blacklist contains the neighboring E-UTRAN cells whose information will not be
measured or reported to the eNodeB by UEs. You can manually add an intra- or inter-frequency
neighboring cell to an RRC blacklist.
HO Whitelist
An HO whitelist contains information about neighbor relations that can be used for a handover
but cannot be removed automatically from the NRT by ANR. The neighbor relations in the HO
whitelist must meet both of the following conditions:
Neighbor relations can manually be added to the HO whitelist. For details, refer to the 3GPP TS 32.511.
X2 Whitelist
An X2 whitelist contains information about the neighboring eNodeBs with which the local
eNodeB has set up X2 interfaces. These X2 interfaces cannot be removed automatically.
7.1.2.1 Activation
Intra-RAT event-triggered ANR is activated when the IntraRatEventAnrSwitch check box is selected under the
ENodeBAlgoSwitch.AnrSwitch parameter.
Intra-RAT event-triggered ANR detects missing intra-RAT neighboring cells and abnormal neighboring cell
coverage, and maintains neighbor relations.
Huawei
Huawei Current
Parameter Table Current GUI Values
Parameter ID Values
Name
IntraRatEventAnrSwitch-1
&IntraRatFastAnrSwitch-0
&IntraRatAnrAutoDelSwitch-0
&UtranEventAnrSwitch-0
&GeranEventAnrSwitch-0
ANR
&UtranFastAnrSwitch-0
AnrSwitch algorithm ENodeBAlgoSwitch
&GeranFastAnrSwitch-0
switch
&CdmaFastAnrSwitch-0
&UtranAutoNrtDeleteSwitch-1
&GeranAutoNrtDeleteSwitch-1
&CdmaAutoNrtDeleteSwitch-1
&ExtendIntraRatAnrSwitch-0
Intra-RAT event-triggered ANR detects cells with unknown PCIs based on the intra- and interfrequency
measurement reports that contain information about cells that meet handover requirements.
Note:
Intra-RAT event-triggered ANR is triggered only by coverage-based handover measurements and
interfrequency mobility load balancing (MLB) measurements.
The eNodeB does not select CA UEs to perform intra-RAT ANR measurements.
For example, cell A and cell B are involved in a handover. The UE is under the coverage of cell
A of the source eNodeB, and cell B is a neighboring cell of cell A. The figure here below outlines how the eNodeB
uses event-triggered UE measurements to detect cell B.
1. The source eNodeB delivers the measurement configuration to the UE, instructing the UE to measure neighboring
cells as specified in the measurement configuration.
The UE performs intra-frequency measurements by default. When a UE establishes radio bearers, by default, the
eNodeB delivers the intra-frequency measurement configuration to the UE in an RRC Connection Reconfiguration
message. When inter-frequency measurements are required, the eNodeB must deliver the inter-frequency
measurement configuration to the UE and set up inter-frequency measurement gaps. For details about
intra- and inter-frequency handover measurements, refer to the Handover chapter.
2. The UE detects that cell B meets the measurement requirements, and it reports the PCI of cell B to the source
eNodeB.
Note that the UE does not report the PCIs of the neighboring cells in the RRC blacklist to the eNodeB.
3. The source eNodeB checks whether its intra-RAT NCL includes the PCI of cell B. If the NCL includes this PCI,
the ANR procedure ends. If the NCL does not include this PCI, the source eNodeB sends the measurement
configuration to the UE, instructing the UE to read the ECGI, tracking area code (TAC), and PLMN list of cell B.
4. The source eNodeB enables the UE to read these parameters over the broadcast channel (BCH).
During this procedure, if the source eNodeB detects that cell B is under itself based on the operating frequency and
PCI of cell B reported by the UE, the source eNodeB does not trigger the ECGI reading procedure. Instead, it
directly adds cell B to an intra-RAT NRT of cell A and adds cell A to an intra-RAT NRT of cell B.
During a handover, the source eNodeB sends UE history information to the target eNodeB.
The figure here below outlines the procedure for using UE history information to detect a missing intra- RAT
neighboring cell.
Notes:
UE history information consists of information about all the cells that have provided services for the UE.
Defined in the 3GPP TS 36.413 and 3GPP TS 36.423, this information includes:
1. The source eNodeB sends a Handover Request message to the target eNodeB.
2. The target eNodeB obtains the UE history information from the message. The target eNodeB checks whether the
ECGI of the last visited cell (in this case, the source cell) exists in the NCL of the target eNodeB and then proceeds
as follows:
- If the ECGI exists in the NCL but does not exist in the NRT, the target eNodeB adds the neighbor relation
to the NRT. The procedure ends;
- If the ECGI does not exist in the NCL, the target eNodeB proceeds to point 3.
3. The target eNodeB reports the ECGI of the source cell to the M2000.
4. The M2000 queries the PCI, TAC, and PLMN list of the source cell based on the reported ECGI and sends the
parameters to the target eNodeB. The target eNodeB adds the source cell to its intra-RAT NCL.
Automatic maintenance of NCLs and NRTs ensures the validity of neighbor relations and therefore significantly
improves network performance.
Automatic removal of intra-RAT neighbor relations is controlled by th IntraRatAnrAutoDelSwitch option of the
ENodeBAlgoSwitch.AnrSwitch parameter. When a network is unstable or in the early stage of deployment, you are
advised to disable automatic removals. The purpose of this action is to prevent frequent NCL/NRT updates so that
the collection of neighbor relations can be completed as quickly as possible.
- The control mode for the neighbor relation with an external E-UTRAN cell is specified by
EutranExternalCell.CtrlMode.
- The control mode for the neighbor relation with an intra-frequency neighboring cell is specified by
EutranIntraFreqNCell.CtrlMode.
- The control mode for the neighbor relation with an inter-frequency neighboring cell is specified by
EutranInterFreqNCell.CtrlMode.
- The control mode for a neighboring frequency is specified by EutranInterNFreq.CtrlMode.
Notes:
- Neighbor relations whose control mode is AUTO_MODE can be modified or removed manually by
users or automatically by ANR. Neighbor relations whose control mode is MANUAL_MODE can be
modified or removed only manually by users.
- The control mode is set to AUTO_MODE for neighbor relations that are automatically created during
SON operations. The control mode can be set to AUTO_MODE or MANUAL_MODE for neighbor
relations that are manually created.
- When ANR automatically adds an intra-RAT neighbor relation, it uses the default values for
parameters whose values cannot be obtained from UE measurements or UE history information.
Table 7-106: SON - ANR – NCL and NRT automatic maintenace parameters
Huawei
Huawei Current
Parameter Table Current GUI Values
Parameter ID Values
Name
IntraRatEventAnrSwitch-1
&IntraRatFastAnrSwitch-0
&IntraRatAnrAutoDelSwitch-0
&UtranEventAnrSwitch-0
&GeranEventAnrSwitch-0
ANR algorithm &UtranFastAnrSwitch-0
AnrSwitch ENodeBAlgoSwitch Inactive
switch &GeranFastAnrSwitch-0
&CdmaFastAnrSwitch-0
&UtranAutoNrtDeleteSwitch-1
&GeranAutoNrtDeleteSwitch-1
&CdmaAutoNrtDeleteSwitch-1
&ExtendIntraRatAnrSwitch-0
CtrlMode Control Mode EutranExternalCell
CtrlMode Control Mode EutranIntraFreqNCell
CtrlMode Control Mode EutranInterFreqNCell
Note: several parameters are introduced in eRAN6, so there are no current network values for all parameters (current
network is eRAN3). No value means that the parameter is introduced in eRAN6, they are also writen in italic.
During NCL automatic maintenance, the eNodeB can automatically add a newly detected external cell to an NCL or
remove an external cell from an NCL.
The eNodeB automatically adds an external cell to an NCL in either of the following cases:
- The eNodeB detects a missing neighboring cell based on UE measurements and receives information
about this cell, including the ECGI, TAC, and PLMN list.
- The eNodeB detects a missing intra-RAT neighboring cell based on UE history information.
The function of automatically removing a cell from an NCL is controlled by the IntraRatAnrAutoDelSwitch check
box under the ENodeBAlgoSwitch.AnrSwitch parameter.
The eNodeB automatically removes an external cell from an NCL if this switch is turned on and
all of the following conditions are met:
- The measurement period, which is four times the value of ANR.StatisticPeriodForNRTDel, has
elapsed.
The measurement period specified by ANR.StatisticPeriodForNRTDel starts when an event-triggered
ANR switch is turned on for E-UTRAN, UTRAN, GERAN.
- The NRTs of all cells under the local eNodeB do not contain any neighbor relations with this external
cell.
- No X2 interface has been set up between the local eNodeB and the eNodeB to which this external cell
belongs.
- Control Mode is set to AUTO_MODE for the neighbor relations with the external cell.
The eNodeB automatically removes an external cell from an NCL if the number of neighbor relations in the NCL
has reached the maximum number and a neighboring cell is to be added to the NCL by ANR.
In this case, the eNodeB removes one of the external cells that meet the following conditions from the NCL. This
function is not under parameter control.
- The NRTs of all cells under the local eNodeB do not contain any neighbor relations with this external
cell.
- Control Mode is set to AUTO_MODE for the external cell.
Parameters
Huawei
Huawei Current
Parameter Table Current GUI Values
Parameter ID Values
Name
IntraRatEventAnrSwitch-1
&IntraRatFastAnrSwitch-0
&IntraRatAnrAutoDelSwitch-0
&UtranEventAnrSwitch-0
&GeranEventAnrSwitch-0
ANR algorithm &UtranFastAnrSwitch-0
AnrSwitch ENodeBAlgoSwitch Inactive
switch &GeranFastAnrSwitch-0
&CdmaFastAnrSwitch-0
&UtranAutoNrtDeleteSwitch-1
&GeranAutoNrtDeleteSwitch-1
&CdmaAutoNrtDeleteSwitch-1
&ExtendIntraRatAnrSwitch-0
During NRT automatic maintenance, the eNodeB can automatically add a neighbor relation to an NRT or remove a
neighbor relation from an NRT in free mode or in controlled mode. The maintenance mode is controlled by the
ANR.OptMode parameter.
- If this parameter is set to FREE, the optimization advice generated by ANR takes effect directly, that
is, the eNodeB automatically adds a neighbor relation to an NRT or removes a neighbor relation from
an NRT without user confirmation.
- If this parameter is set to CONTROLLED, the eNodeB reports the optimization advice to the M2000.
Users determine whether to add a neighbor relation to an NRT or remove a neighbor relation from an
NRT. However, after receiving handover-related measurement reports from UEs, the eNodeB can
perform intra-RAT handovers for the UEs even if users have not confirmed the optimization advice to
add the target cell to the intra-RAT NRT.
-
The eNodeB automatically adds a neighbor relation to an NRT in either of the following cases:
- The eNodeB detects a missing neighboring cell based on UE measurements, receives information
(such as the ECGI, TAC, and PLMN list) about this cell, and adds this information to the NCL. If the
detected cell already exists in the NCL, the eNodeB directly adds the neighbor relation to the NRT.
- The eNodeB detects a missing neighboring cell based on UE history information in a handover request
message and finds that the ECGI of the last visited cell exists in the NCL of the target eNodeB but
does not exist in the NRT of the target cell.
-
The eNodeB automatically removes a neighbor relation (for example, with cell A) from an NRT if the
IntraRatAnrAutoDelSwitch check box under the ENodeBAlgoSwitch.AnrSwitch parameter is selected, the No
Remove attribute for the neighbor relation is set to permit removals, the Control Mode parameter for the neighbor
relation is set to AUTO_MODE, and either of the following conditions is met:
- When the number of neighbor relations in an intra-RAT intra-frequency or inter-frequency NRT has
reached the maximum of 64, a new neighbor relation needs to be added through ANR. In addition,
within the last measurement period specified by the ANR.StatisticPeriodForNRTDel parameter, the
total number of handovers from the local cell to its neighboring cells was greater than or equal to the
value of ANR.StatisticNumForNRTDel and cell A has never been included in any handover-related
measurement reports.
If more than one neighbor relation meets these conditions, the eNodeB randomly selects one. If no
neighbor relation meets the conditions, the eNodeB does not remove a neighbor relation.
- The success rate of handovers to a neighboring cell is lower than expected.
The eNodeB removes a neighboring cell from an NRT and NCL or reports the optimization advice to
the M2000 if the following conditions are met:
Within a measurement period specified by the ANR.StatisticPeriodStatisticPeriod parameter,
the number of handovers from each of the cells who have configured with neighbor relation
with the neighboring cell under the eNodeB to the neighboring cell is greater than or equal to
the value of ANR.NcellHoStatNum.
The handover success rate for each of the cells under the eNodeB to the neighboring cell is
less than or equal to the value of ANR.DelCellThd.
Notes:
- The measurement period specified by ANR.StatisticPeriodForNRTDel starts when any eventtriggered
ANR switch is turned on for E-UTRAN, UTRAN, GERAN, or CDMA2000.
- The measurement period specified by ANR.StatisticPeriod starts when the switch for intra-RAT event
triggered ANR IntraRatEventAnrSwitch is turned on.
Note: the ANR parameter table is on eNodeB level and not on cell level.
Parameter details
ANR.xlsx
7.2.1 Introduction
Physical cell identifiers (PCIs) are used for signal synchronization and demodulation. There are504 PCIs in the LTE
system. These PCIs are divided into 168 groups, each containing 3 PCIs.
Each evolved universal terrestrial radio access network (EUTRAN) cell is allocated a PCI.
When many cells exist in an LTE system, some cells with the same frequency must share one PCI. A PCI conflict
may occur between cells with the same frequency if PCIs are planned inappropriately or changed manually, or if
neighboring cell parameters are modified.
Huawei developed the PCI conflict detection and self-optimization feature, which provides the following functions:
- PCI self-optimization
Reallocates appropriate PCIs to conflicting cells based on the PCI conflict detection result.
Note: at the time of writing the document, this feature is not in use, so there are no relevant current setting.
The PCI conflict is classified into PCI collision and PCI confusion.
A PCI collision occurs between two intra-frequency cells that use an identical PCI but are insufficiently isolated. In
this case, UEs in the overlapping area of the two cells cannot implement signal synchronization or decoding. The
figure here below shows a PCI collision between cell A and cell B.
If a cell has the same frequency and PCI as one of its neighboring cells, there is a PCI collision between the cell and
the neighboring cell.
Notes: an LTE cell is not allowed to have the same frequency and PCI as its neighboring cell but it can have the
same frequency and PCI as its external cell or other intra-eNodeB cells.
A PCI confusion occurs between a detected cell and a neighboring cell if the two cells have the same frequency and
PCI and if the reference signal received power (RSRP) of the two cells reaches the handover threshold. The PCI
confusion may lead to UE handover failures or service drops.
A PCI confusion occurs in the following scenarios:
7.2.2.3.1 PCI Confusion when the Detected Cell Is a Configured Neighboring Cell
As shown in the figure here below, if the UE does not support ANR, the eNodeB cannot determine whether the
detected cell is cell B or C based on the report by the UE. In this case, cell A cannot initiate a handover. If intra-
RAT event-triggered ANR is enabled and the UE supports ANR, the eNodeB can identify cell B based on the
EUTRAN cell global identifier (ECGI) reported by the UE.
If two or more neighboring cells of a cell have the same frequency and PCI, there is a PCI conflict between these
neighboring cells.
7.2.2.3.2 PCI Confusion when the Detected Cell Is Not a Configured Neighboring Cell
As shown in the figure here below, the eNodeB mistakenly considers that the detected cell is cell C and then initiates
a handover to cell C. If the spot that the UE is on is not covered by cell C but cell B, a handover failure may occur.
- PCI conflict detection triggered by manual operations. The PCI conflict parameters are changed due to
manual modifications to the PCI, frequency or other parameters.
- PCI conflict detection triggered by ANR. ANR adds or removes a neighboring cell, or it updates the
PCI of the neighboring cell.
- PCI conflict detection based on X2 messages.The eNodeB receives an X2 message. If an X2
connection has been set up between the eNodeBs and
GlobalProcSwitch.X2BasedUptENodeBCfgSwitch is turned on, one eNodeB will update the
neighboring cell parameters based on another eNodeB's cell information carried in the message.
If the eNodeB detects or resolves a PCI conflict, it reports the PCI conflict information to the M2000 client and this
information will be updated in the PCI Optimization Task window on the M2000 client. The M2000 client also
decides whether to allow the eNodeB to report the ALM-29247 Cell PCI Conflict alarm to the M2000 alarm console
or LMT alarm interface, depending on the setting of the ENodeBAlgoSwitch.PciConflictAlmSwitch parameter
Notes:
For details about NCLs and NRTs, refer to the ANR chapter.
If the CME is available and you need to change the configuration of an eNodeB through the CME, turn off
GlobalProcSwitch.X2BasedUptENodeBCfgSwitch to avoid configuration data loss. This is because when the
configuration (such as the PCI or frequency) of an eNodeB is changed on the CME, the CME updates the
parameters of the eNodeB in the neighboring cell list (NCL), which triggers PCI conflict detection and may change
neighboring cell data. This conflicts with the neighboring cell data change triggered when
GlobalProcSwitch.X2BasedUptENodeBCfgSwitch is turned on.
7.2.3.1 Overview
If the eNodeB detects that the PCI of a cell conflicts with a configured PCI, the eNodeB notifies the M2000 of the
conflict. The M2000 then allocates an appropriate PCI to this conflicting cell.
The new PCI takes effect after the M2000 sends it to the eNodeB.
Each eNodeB stores an NCL and NRTs. The NRTs contain information about the neighboring cells of the local cells
of this eNodeB. These neighboring cells are the first-order neighboring cells. These cells may be intra-frequency,
inter-frequency, or inter-RAT neighboring cells. RAT is short for radio access technology.
Notes : for details about NCLs and NRTs, refer to the ANR chapter.
The first-order neighboring cells of the first-order neighboring cells of a cell are the secondorder neighboring cells
of this cell. Assume that cell B is a first-order neighboring cell of cell A and cell C is a first-order neighboring cell
of cell B. Then, cell C is a second-order neighboring cell of cell A.
Note: for simplicity, the following uses "new PCI" to represent a PCI to be allocated to a conflicting cell.
- A new PCI must be different from the PCI of any first-order or second-order intra-frequency
neighboring cell of the conflicting cell.
- A new PCI must be different from the PCI of any intra-frequency neighboring cell in the NCL of the
conflicting cell.
- A new PCI must be different from the PCI of any cells under the same eNodeB as the conflicting cell.
- If the blacklist is considered:
A new PCI must be different from the PCI of any blacklisted intra-frequency EUTRAN cell of
the conflicting cell.
If the conflicting cell is not in the intra-frequency EUTRAN cell blacklist of any of its first-
order neighboring cells, the new PCI must not be within the range specified by
IntraFreqBlkCell.PhyCellIdRange.
If the conflicting cell is not in the inter-frequency EUTRAN cell blacklist of any of its first-
order neighboring cells, and there is a cell with the same frequency as the conflicting cell in
the inter-frequency EUTRAN cell blacklist, the new PCI must not be within the range
specified by InterFreqBlkCell.PhyCellIdRange.
Note: the UE does not report the blacklisted cells so that the previously detected conflicting
cells are still detectable after PCI self-optimization.
- Positions of physical resource blocks (PRBs) occupied by the physical HARQ indicator channel
(PHICH) and physical control format indicator channel (PCFICH)
If the conflicting cell uses compressed bandwidth, the M2000 avoids allocating some restricted PCIs to
the conflicting cell. This prevents the PHICH and PCFICH from being allocated nonexistent PRBs.
- Primary synchronization codes
Three cells with adjacent azimuths under an eNodeB have different primary
7.2.5 Parameters
Table 7-109: SON – PCI conflict detection / optimization parameters
8.1 Overview
The LTE system uses the Orthogonal Frequency Division Multiple Access (OFDMA) technology in the downlink
(DL) and the Single Carrier - Frequency Division Multiple Access (SC-FDMA) technology in the uplink (UL).
OFDMA and SC-FDMA have a common characteristic: All physical resource blocks (PRBs) occupied by user
equipment (UEs) in a cell are mutually orthogonal in the frequency domain; therefore, intra-cell interference is very
low. However, inter-cell interference is relatively high because the frequency reuse factor is 1, in which case every
cell can provide services over the entire system band. For cell edge users (CEUs), the impact of the inter-cell
interference is especially severe. Therefore, to increase the CEU throughput, inter-cell interference must be
mitigated.
Inter-Cell Interference Coordination (ICIC) is a technology that collaborates with power control and media access
control (MAC) scheduling technologies to mitigate inter-cell interference. ICIC divides the entire system band into
three frequency bands and uses different frequency bands at the edge of neighboring cells. CEUs, which cause high
interference or may be sensitive to interference, are preferentially scheduled in the cell edge bands to mitigate inter-
cell interference. The interference mitigation enhances the network coverage and improves the CEU throughput.
8.2 Principles
Huawei ICIC classifies cell users into CEUs and cell center users (CCUs).
- CEU/CCU identification is a technique of identifying the UE type (CEU or CCU) based on events A3
and A6. Measurements and configurations for events A3 and A6 in ICIC are independent of those for
8.2.1.1 Principles
When initially accessing a network, a UE is recognized as a CCU by the serving cell; after a handover, the UE is
recognized as a CEU by the target cell. After a short period following the initial access or handover, the eNodeB
starts to determine whether the UEs are CEUs or CCUs by using ICIC event A3 or A6, Event A6 is used for carrier
agreegation (CA). CA is not part of this document. ENodeBs identify CEUs and CCUs based on ICIC event A3 or
A6 as follows:
- If an ICIC event A3 or A6 report contains the measurement result only about the serving cell of a UE,
the eNodeB treats the UE as a CCU. An example of this is when the UE moves from the cell edge to
the cell center.
- If an ICIC event A3 or A6 report contains the measurement result about at least one neighboring cell,
the eNodeB treats the UE as a CEU.
The 3GPP TS 36.331 describes principles and triggering mechanisms of ICIC event A3/A6.
Note: measurements and configuration for ICIC event A3 are independent of those for event A3 used in handovers.
Parameter settings for ICIC event A3 have no impact on handovers
The variables in the preceding conditions are described as follows (based on RSRP-based event A3):
- If the RSRP measurement result of at least one neighboring cell meets the entering condition for ICIC
event A3, the UE reports the RSRP measurement results of the serving and neighboring cells to the
eNodeB. The maximum number of neighboring cells to be included in a report for both DL and UL
ICIC is determined by the CellDLIcicMcPara.MaxReportCellNum parameter.
- If the RSRP measurement result of at least one neighboring cell meets the leaving condition for ICIC
event A3, the UE reports only the RSRP measurement result of the serving cell to the eNodeB.
Event A3 is reported periodically after the first report. The interval for both DL and UL ICIC is determined by the
CellDLIcicMcPara.ReportInterval parameter. A longer interval indicates a lower frequency of updating user location
information, whereas a shorter interval results in greater consumption of radio interface resources.
The number of periodic reports for both DL and UL ICIC is determined by the CellDLIcicMcPara.ReportAmount
parameter. A larger value results in greater UE power consumption and a larger increase in the CEU throughput. A
smaller value leads to less UE power consumption but lower accuracy of neighboring cell conditions for CEUs. The
low accuracy has a negative impact on the CEU throughput gain.
As shown here below, the yellow, green, and purple colors represent different edge band modes. For example, if the
system bandwidth is 20 MHz, the edge band of each cell may occupy 1/3 of the entire system band.
The CellDlIcic.BandMode and CellUlIcic.BandMode parameters specify the edge band mode used in DL ICIC and
UL ICIC, respectively. eNodeBs determine the range of the edge band for each cell based on the cell bandwidth and
edge band mode.
Active shrinking: The current cell actively shrinks its edge band if its edge load isrelatively
low.
Passive shrinking: When the neighboring cell expands its actual edge band within the edge
band defined in static ICIC, the current cell shrinks its edge band if the PRBs used by the
current and neighboring cells collide. The figure here below shows an example of passive
shrinking.
DL inter-cell interference and UL inter-cell interference are caused by eNodeBs and UEs, respectively. However,
CEUs are interfered in both DL and UL. Therefore, the preceding ICIC principles apply both in the DL and the UL.
However, there are differences between DL ICIC and UL ICIC in the internal processing of eNodeBs.
8.3 Parameters
Huawei Parameter
Huawei Parameter ID Table
Name
Downlink ICIC
ReportInterval measurement report CellDLIcicMcPara
interval
Downlink ICIC CellDLIcicMcPara
MaxReportCellNum measurement max
report cell number
ReportAmount DownLink ICIC CellDLIcicMcPara
measurement report
amount
ReportQuantity DownLink ICIC CellDLIcicMcPara
measurement report
quantity
TriggerQuantity DownLink ICIC CellDLIcicMcPara
measurement
trigger quantity
Hysteresis DownLink ICIC CellDLIcicMcPara
measurement
hysteresis
TimeToTrigger DownLink ICIC CellDLIcicMcPara
measurement time
to trigger
A3Offset Downlink ICIC A3 CellDLIcicMcPara
offset
A6Offset Downlink ICIC A6 CellDLIcicMcPara
offset
BandMode Downlink band CellDlIcic
division scheme
DlIcicUserAttrGfactorThd User Attribution CellDlIcic
Gfactor Threshold
DlIcicNoiseUserRsrpThd Noise User RSRP CellDlIcic
Threshold
ReportInterval Uplink ICIC CellULIcicMcPara
Notes:
- the parameters in italic are from eRAN6, as eRAN3 is currently running, there are no values;
- this feature is currently not in use, so the current parameter setting is not taken into account.
ICIC parameter
details 1.xlsx
If dynamic DL ICIC is enabled, the eNodeB allocates an initial DL edge band to each cell based on the cell
bandwidth and edge band mode. Then, the eNodeB periodically triggers adjustments of the DL edge band. The
following describes how dynamic DL ICIC adjusts edge bands.
- ID of the source cell: This is the ID of the cell that sends this message;
- ID of the target cell: This is the ID of the neighboring cell to which this message is sent;
- Coordination request indication: This indicates whether the source cell requests the target cell to adjust
its edge band. The source cell sets the coordination request indication to TRUE if the interference from
the target cell is intolerable. The tolerance is evaluated based on the measured RSRP values and DL
edge bands of the source cell and target cell.
- Load status of the source cell: This is determined based on the average number of edge PRBs required
by CEUs during historical adjustment periods and the number of PRBs in the current edge band. Based
on the load status, the target cell decides whether to adjust its edge band.
- Edge band status of the source cell: This is indicated by the bitmap of all high-power PRBs in the
source cell. Based on this bitmap, the target cell can avoid using the edge band of the source cell and
perform inter-cell coordination effectively. For details about the highpower PRBs, see the descriptions
of relative narrowband TX power (RNTP) in the 3GPP TS 36.213.
If the edge band of a cell is adjusted or the edge load is changed, this cell notifies its neighboring cells of this
adjustment or change by Huawei-defined messages. Based on the information contained in these messages, the
neighboring cells expand or shrink their edge band. The expansion and shrinking policies are as follows:
- Expansion policy: A cell attempts to expand its edge band towards a neighboring cell with a lower
edge load. This expansion is canceled if the estimated post-expansion edge band exceeds the edge-
band range defined in static ICIC and the extra PRBs collide with the edge band used by the
neighboring cell.
- Shrinking policy: A cell attempts to shrink its edge band to the average number of edge PRBs in this
cell during historical adjustment periods. If the estimated post-shrinking edge band exceeds the edge-
band range defined in static ICIC and the extra PRBs still collide with the edge band used by a
neighboring cell, the colliding PRBs are removed from the edge band of the current cell.
8.5.3 Parameters
Huawei Parameter
Huawei Parameter ID Table
Name
DlIcic algorithm
DlIcicSwitch ENodeBAlgoSwitch
switch
DL ICIC eNodeB.xlsx
- ID of the source cell: This is the ID of the cell that sends this message.
- ID of the target cell: This is the ID of the neighboring cell to which this message is sent.
- Interference information: This is indicated by the bitmap of all edge PRBs in the source cell. Based on
this bitmap, the target cell adjusts its edge band.
The eNodeB periodically measures the number of PRBs actually used by CEUs in each cell and compares this
number with the number of PRBs in the current edge band of the cell. If the difference between the numbers is
excessively large for a cell, the eNodeB triggers an edge band adjustment. If the edge band of the cell is adjusted,
the cell transmits the updated HII messages to its neighboring cells.
Based on the information in the HII messages from a cell, its neighboring cells expand or shrink their edge band.
The expansion and shrinking policies are as follows:
- Expansion policy: A cell attempts to expand its edge band to the average number of edge PRBs in this
cell during historical adjustment periods. If the estimated post-expansion edge band exceeds the edge-
band range defined in static ICIC and the extra PRBs collide with the edge band used by a neighboring
cell, the colliding PRBs are removed from the edge band of the current cell.
- Shrinking policy: A cell attempts to shrink its edge band to the average number of edge PRBs in this
cell during historical adjustment periods. In the passive-shrinking situation, ICIC and the extra PRBs
8.6.3 Parameters
Huawei Parameter
Huawei Parameter ID Table
Name
UlIcicFreqSwitch UlIcic freq switch ENodeBAlgoSwitch
UL ICIC eNodeB.xlsx
9.1 Overview
UL CoMP uses UL macro diversity to combine received signals. In the coverage area of an eNodeB, UL CoMP uses
the antennas of two neighboring cells to receive UE signals from the physical uplink shared channel (PUSCH) and
combines these received signals. In this way, UL CoMP provides signal combining gains and interference mitigation
gains. UL CoMP depends on UL interference rejection combining (IRC) and can be used only after LOFD-001012
UL Interference Rejection Combining is enabled. The UL CoMP can be used in the following scenarios.
9.2 Scenarios
9.2.1 Scenario 1
A UE's signals are expected to obtain signal combining gains from UL CoMP. For simplicity, such a UE is called a
type-1 CoMP UE.
A type-1 CoMP UE (see figure here below) lies on the edge between cells (bi-sector area). The signal of this UE are
very likely be a combination of both cell 1 and cell 0, and so gains from UL CoMP.
If a type-1 CoMP UE experiences interference from other UEs in neighboring cells, the type-1 CoMP UE's signals
can also obtain interference mitigation gains.
9.2.2 Scenario 2
A UE's signals are expected to obtain interference mitigation gains from UL CoMP. For simplicity, such a UE is
called a type-2 CoMP UE.
A type-2 CoMP UE (see in figure here below) experiences interference from a UE (UE1) on the edge in the area of
the bisector. The signals of UE0 can obtain obvious interference mitigation gains from UL CoMP. Note that UE0
does not lie on the edge between intra-site cells.
Notes:
If a UE meets the requirements for both type-1 and type-2 CoMP UEs, the eNodeB still categorizes the
UE as a type-1 CoMP UE.
The serving cell and the coordinating cell must be established on the same baseband processing unit (BBP)
in scenarios 1 and 2 for LOFD-001066 Intra-eNodeB UL CoMP.
9.3 Benefits
UL CoMP uses the antennas of two cells to receive a suitable UE's signals. If each cell has two receive (RX)
antennas, UL CoMP can use four RX antennas to provide gains, compared with two RX antennas in non-CoMP
scenarios.
- UL CoMP provides signal combining gains and interference mitigation gains for type-1 CoMP Ues;
- UL CoMP provides interference mitigation gains for type-2 CoMP UEs.
UL CoMP uses IRC (Interference Rejection Combining) to provide interference mitigation gains. UL CoMP can
mitigate interference from detected sources to UEs on the edge between cells (for example, in scenario 1). UL
CoMP can also mitigate interference from undetected sources to UEs on the edge between cells (for example, in
scenarios 1 and 2).
The basic UL CoMP process consists of three procedures, as shown in the figure here below:
- Enable UL CoMP.
Turn on the UL CoMP switches, and configure cell-level information such as information about
candidate coordinating cells.
- The eNodeB selects CoMP UEs and coordinating cells.
The eNodeB selects CoMP UEs and coordinating cells based on the event A3 measurement
reports from UEs and the RBs allocated to the CoMP UEs.
- The eNodeB uses antennas of multiple cells for joint reception.
The physical layer uses the antennas of each CoMP UE's serving cell and coordinating cell to receive
this UE's signals and then combines these signals using maximum ratio combining (MRC) or IRC. IRC
is used if the license for LOFD-001012 UL Interference Rejection Combining is purchased and
activated.
In the figure above, the coordinates (0, 0) represent the eNodeB location, the horizontal and vertical axes represent
the distances of UEs from the eNodeB (unit: m), and the colors indicate RSRP differences (unit: dB). The RSRP
difference at any point is calculated as follows:
RSRP difference (dB) = RSRP received in the serving cell (dBm) – RSRP received from the neighboring cell (dBm)
The color ribbon to the right of the figure shows the mapping between RSRP differences and colors. For example,
the deep blue at the bottom represents an RSRP difference of 0 dB.
UEs in the blue area can be selected as type-1 CoMP UEs. UEs in the red and yellow areas can be selected as type-2
CoMP UEs if the UEs experience interference from type-1 CoMP UEs in the blue area.
Note:
All parameters for UL CoMP event A3 except the A3 offset (CellUlCompAlgo.UlCompA3Offset) are the same as
those for inter-cell interference coordination (ICIC).
After the physical layer receives the information about CoMP UEs and their coordinating cells, it uses the antennas
of the serving cell and coordinating cell to implement joint reception.
Compared with common multiple-antenna reception, joint reception by antennas of multiple
cells has the following characteristics:
9.7 Parameters
9.7.1 Parameters
Parameter details:
ULCoMP.xlsx
Here below, the 3Gpp TS 36.304 RRC Idle cell selection and reselection states and procedures.
Figure 10-49: 3Gpp TS 36.304 RRC Idle cell selection and reselection states and procedures
go here whenever a
new PLMN is
selected
Stored Initial
information no suitable cell found Cell Selection
Cell Selection
no suitable
cell found suitable cell found 2 suitable cell found
no suitable
cell found
Cell Selection NAS indicates that
when leaving suitable Camped registration on selected
connected cell found normally PLMN is rejected
mode (except with cause
#12, #14 , #15 or #25
[5][16])
return to leave trigger
idle mode idle mode suitable
cell found
Connected Cell
mode no suitable
Reselection
Evaluation cell found
Process
go here
when no
USIM in
the UE
Any Cell
no acceptable cell found Selection
USIM inserted
acceptable
cell found
1
Cell Selection
acceptable
when leaving Camped on suitable
cell found
connected any cell cell found 2
mode
Connected
mode Cell
(Emergency Reselection no acceptable
calls only) Evaluation cell found
Process
Here below, the 3Gpp TS 36.331 RRC System information Block 1 description (Rel. 9)
Here below, the 3Gpp TS 36.331 RRC System information Block 3 description (Rel. 9)
Here below, the 3Gpp TS 36.331 RRC System information Block 5 description (Rel. 9)
Here below, the 3Gpp TS 36.331 RRC System information Block 6 description (Rel. 9)
Here below, the 3Gpp TS 36.331 RRC System information Block 7 description (Rel. 9)