Mobility Control at Poor Coverage

Feature Description

40/221 04-LZA 701 6014/1 Uen BF

Copyright

© Ericsson AB 2016-2020. All rights reserved. No part of this document may be

reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to
continued progress in methodology, design and manufacturing. Ericsson shall
have no liability for any error or damage of any kind resulting from the use of this
document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.
These are shown in the document Trademark Information.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 Contents

Contents

1 Overview 1

2 Dependencies 3

3 Feature Operation 7
3.1 Process Steps 9
3.2 Search Zone for UEs in Poor Coverage 21
3.3 Level Based Search Zone Transitions 23

4 Network Impact 26

5 Parameters 27
5.1 Feature Configuration Parameters 27
5.2 Affected Parameters 31
5.3 Parameters Affecting the Feature 31

6 Performance 32
6.1 Key Performance Indicators 32
6.2 Counters 32
6.3 PM Events 34

7 Activate the Feature 36

8 Deactivate the Feature 37

9 Engineering Guidelines 38

Appendix A: Feature Change History 39

Appendix A.a: 19.Q1: Improved Quantity Check for Handover Decision 39
Appendix A.b: 19.Q1: Availability Setting for Release with Redirect in
Search and Critical Zone 40

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

Mobility Control at Poor Coverage

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

1 Mobility Control at Poor Coverage Overview

Access Type: LTE

Feature Identity: FAJ 121 3013
Value Package Name: LTE Base Package
Value Package Identity: FAJ 801 0400
Node Type: Baseband Radio Node
DU Radio Node
Licensing: Licensed feature. One license is required per node.

Summary
The Mobility Control at Poor Coverage feature improves the functionality of the
Session Continuity feature to increase mobility handling flexibility at poor
coverage.

The feature introduces a search zone along the edge of the cell, where UE
measurements search for alternative frequencies and cells. If a frequency or cell
is detected, a mobility action is initiated. If no alternative frequencies are
detected in the search zone and the UE moves into critical coverage, a configured
emergency mobility action is selected by the eNodeB and initiated in the UE.

For a UE that encounters poor coverage, the feature makes it possible to search
for several inter-frequency and IRAT target frequencies.

The feature allows the operator to define and prioritize the preferred frequencies
for measurements and mobility actions. It is also possible to disable
measurements per RAT but still be able to perform blind handover or release with
redirect to the RAT at the critical threshold.

This feature also enables ANR to add inter-frequency, GERAN, and UTRAN
neighbors based on mobility triggers in the search zone, instead of triggering on
the dedicated ANR measurements used in the rest of the cell. This results in ANR
being able to define neighbor cells that can be used when a UE reaches the
critical threshold and provides a solution where the best cell is identified and
used. Removing the ANR-initiated measurements in the search zone and
replacing them with the measurements enhances mobility. Only the cells that are
used for mobility purposes are added. This reduces the neighbor lists to only
include cells that are used.

Additional Information
For information on the preferred state and parameter settings of this feature, see
RAN Parameter Recommendations Lists.

More information about this feature and related topics can be found in the
following documentation:

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 1

 Mobility Control at Poor Coverage

— 3GPP TS 36.300 Overall description; Stage 2

— 3GPP TS 36.331 Radio Resource Control (RRC); Protocol Specification

2 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

2 Dependencies of Mobility Control at Poor
Coverage
Table 1 Feature Dependencies
Feature
At least one of these five features must be enabled:
Coverage-Triggered Inter-Frequency
Session Continuity (FAJ 121 0797)
Coverage-Triggered WCDMA Session
Continuity (FAJ 121 0493)
Coverage-Triggered TD-SCDMA
Session Continuity (FAJ 121 3004)
Coverage-Triggered GERAN Session
Continuity (FAJ 121 0495)
Coverage-Triggered CDMA-eHRPD
Session Continuity (FAJ 121 0491)
Automated Neighbor Relations (FAJ
121 0497)
Coverage-Triggered Inter-Frequency
Handover (FAJ 121 0877)
Coverage-Triggered WCDMA IRAT
Handover (FAJ 121 0897)
Device-Based Frequency Filtering
(FAJ 121 5154)
High Power UE (FAJ 121 4762)
40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28
Relationship Description
Prerequisite Feature handling redirection to other
LTE frequencies.
Prerequisite Feature handling redirection to
WCDMA.
Prerequisite TDD only: Feature handling
redirection to TD-SCDMA.
Prerequisite Feature handling redirection to
GERAN.
Prerequisite Feature handling redirection to
CDMA2000.
Related The behavior of ANR in the search
zone is modified.
Related Feature providing the possibility to
initiate a handover to a cell on an
alternative LTE frequency when the
UE reports poor coverage in the
current cell.
Related Feature providing the possibility to
initiate a handover to a WCDMA cell
when the UE reports poor coverage in
the current cell.
Related The Device-Based Frequency
Filtering feature is used to configure a
list of unsupported frequencies for
specific UEs. These frequencies are
excluded from UE configuration
messages sent by the eNodeB.
Unsupported frequencies are
configured using the
UnsupportedFreqProfile.unsuppo
rtedFreqList attribute.
Related When the Mobility Control at Poor
Coverage, the Multi-Layer Service-
Triggered Mobility, and the High
3
 Mobility Control at Poor Coverage
Feature
SRVCC Handover to UTRAN (FAJ 121 Related
2027)
Subscriber Triggered Mobility (FAJ
121 1788)
Shared LTE RAN (FAJ 121 0860)
Redirect with System Information
(FAJ 121 0876)
Service Triggered Mobility (FAJ 121
1747)
Multi-Layer Service-Triggered
Mobility (FAJ 121 4124)
Intra-LTE Inter-Mode Handover (FAJ
121 3042)
Uplink-Triggered Inter-Frequency
Mobility (FAJ 121 1797)
Mission-Critical Push-to-Talk (FAJ
121 4929)
4 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28
Relationship Description
Power UE features are used together
the following applies. To differentiate
mobility control for UEs with different
UE power class, it is possible to
configure a UE power class
differentiated measurement
threshold offset for each frequency
relation. This changes the point of
triggering handover for UEs with high
power capability.
Feature providing the possibility to
initiate an SRVCC handover to a
WCDMA cell when there is an active
voice bearer.
Related Feature providing an alternative way
to prioritize frequencies, based on
Subscriber Profile ID for RAT/
Frequency priority (SPID).
Related Feature allowing several operators to
share a common LTE RAN.
Related Feature providing the possibility to
include system information with the
redirect frequency in the release
message to the UE.
Related Feature allowing definition of QCI-
based offsets for the thresholds for
Event A1, Event A2, Event A5, and
Event B2.
Related Feature allowing definition of cell-
specific QCI-based offsets for the
thresholds for Event A1, Event A2,
Event A5, and Event B2.
Related Feature allowing handover between
FDD and TDD cells.
Related Feature adding uplink channel
quality as a mobility triggering
quantity.
Related When the Mission-Critical Push-to-
Talk feature is active, this feature
treats mission-critical bearers like it
treats VoLTE bearers (QCI 1).
However, if there are restrictions on
Mission-Critical Push-to-Talk service
in the GERAN and UTRAN networks,
 Feature Relationship Description
it can prevent mobility towards these
networks.

For Release with redirect towards

Uplink-Traffic-Triggered Mobility
(FAJ 121 5044)
GERAN and UTRAN, the same
handling is applied to mission-critical
bearers than for VoLTE bearers, using
the
UeMeasControl.allowReleaseQci1
attribute.
Related If the Mobility Control at Poor
Coverage and the Uplink-Traffic-
Triggered Mobility feature is enabled
at the same time, and the handover-
triggering thresholds are not set
properly, the UE performs handovers
between two cells indefinitely. To
avoid this, the
ReportConfigA5UlTraffic.a5Thre
shold2Rsrp attribute in the source
cell must be set to a higher value than
the
ReportConfigSearch.a1a2SearchT
hresholdRsrp attribute in the target
cell.

When the Service Triggered Mobility

or Multi-Layer Service-Triggered
Mobility features are also active, QCI-
dependent thresholds can be applied
in the target cell. In this case, the
attribute must be set to a value
higher than the maximum of these
thresholds.

Hardware
No special hardware for this feature.

Limitations
No limitations for this feature.

Network Requirements
This is a licensed feature. This means that for the feature to be operational, a
valid license key must be installed and the feature must be explicitly activated by
setting a MOM attribute.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 5

 Mobility Control at Poor Coverage

The following must be fulfilled at feature activation:

— At least one of the following features must be activated:

• Coverage-Triggered Inter-Frequency Session Continuity

• Coverage-Triggered WCDMA Session Continuity

• TDD only: Coverage-Triggered TD-SCDMA Session Continuity

• Coverage-Triggered GERAN Session Continuity

• Coverage-Triggered CDMA-eHRPD Session Continuity

— To configure redirection of the UE at poor coverage, information about other

carrier frequencies must be entered in the eNodeB during network
configuration according to the Coverage-Triggered features.

— The settings must be adjusted for the Event A2 and Event A1 measurements
that detect when the UE has good coverage or is in the search zone so that
Event A2 and Event A1 are reported from the UE when required.

— When a UE enters the search zone, the eNodeB can configure Event
A3/A5/B2 measurements in the UE to search for alternative frequencies.
This is controlled per RAT by the following parameters:
UeMeasControl.ueMeasurementsActiveIF,
UeMeasControl.ueMeasurementsActiveUTRAN,
UeMeasControl.ueMeasurementsActiveGERAN, and
UeMeasControl.ueMeasurementsActiveCDMA2000.

Note: These parameters replace the

UeMeasControl.ueMeasurementsActive parameter which is used
in the Session Continuity features.

The Event A3 measurement that is optionally configured in the

search zone is always inter-frequency, as introduced by the
Coverage-Triggered Inter-Frequency Session Continuity feature. It
is on a different LTE frequency. The Event A3 Best Cell
measurement used in the Intra-LTE Handover feature is intra-
frequency and is not at all affected by this feature. In this document,
Event A3 only refers to inter-frequency measurements.

6 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

3 Feature Operation of Mobility Control at Poor
Coverage

The feature Mobility Control at Poor Coverage introduces a search and critical
zone along the edge of the cell. UE measurements search for alternative
frequencies and cells.

The Coverage-Triggered Session Continuity features provide a basic process

followed by the eNodeB to determine where to transfer a UE in poor coverage.
Each RAT has a Coverage-Triggered Session Continuity feature. The following
features are the Coverage-Triggered Session Continuity features:

— Coverage-Triggered Inter-Frequency Session Continuity

— Coverage-Triggered WCDMA Session Continuity

— Coverage-Triggered TD-SCDMA Session Continuity

— Coverage-Triggered GERAN Session Continuity

— Coverage-Triggered CDMA-eHRPD Session Continuity

This process is enhanced by the Mobility Control at Poor Coverage feature, and is
described in this section.

Note: When the Mission-Critical Push-to-Talk feature is activated, and

mobility towards GERAN and UTRAN is supported, all processes and
criteria in this feature operation regarding QCI 1 also apply to mission-
critical bearers (QCIs 65, 66 and 69).

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 7

 Mobility Control at Poor Coverage

Operational Process

1 UE is connected to cell

Determine a set of inter-frequency

2 and IRAT frequency candidates in
case of poor coverage

The set yes Do not start measurements

3 of frequency candidates for poor coverage
is emtpy?

no

Start ”Search” measurement

for detecting the search zone

Wait for measurement reports

Cancel the timer detecting the search zone

Search zone The ”Target Good

4 reported
11 Enough” measurement
yes time out

UE in Good
Coverage no (Re-)start the timer
5
(both RSRP and
RSRQ)?
Always: UE has no
Stop reported ”Search” bearer with
6 Start ”Target Good Enough” QCI1?
Sometimes: yes
Start ”Good Coverage”
Start ”Critical Coverage”
Stop ”Good Coverage” Start ”Outer Search” Restart the timer
Stop ”Critical Coverage”
Stop ”Target Good Enough”
Start ”Search” measurement Search zone
7 reported
Stop ”Target Good
Enough ”
measurements
10 Good Coverage Wait for a ”Target Good
reported Enough”, ”Good Coverage”,
”Critical Coverage”, ”Search”
or ”Outer Search”
measurement report
9 QCI1 release
8 QCI1 setup

A
Restart timer & ”Target ”Target Good
Good Enough” No
Enough”
easurements with measurements are
Restart the timer, Reconfigure voicePrio running?
to remove current ”Target Good Enough”
measurements & add ”Target Good Yes
Enough” measurements with
connectedModeMobilityPrio Restart timer, Reconfigure to
remove current ”Target Good
Enough” measurements & add
”Target GoodEnough”
measurements with voicePrio
L0000720E

Figure 1 UE Transfer at Poor Coverage Using a Search Zone (Part 1)

8 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 A

”Target Good ”Critical

12 Enough” Coverage” 17
reported reported

13 ANR: Determine possible

18
Unknown Cell and target
First Time? Yes frequencies

No

14 19
Blind
Initiate Handover Handover? Handover? Initiate Handover
Yes Yes

No No

15 Release with Release with

20
redirect allowed? redirect allowed?
No No

Yes Yes

16 UE has bearer
21
UE has bearer
with with
Yes QCI 1? QCI 1? Yes

No No

Initiate release with Initiate release with

redirect to the redirect to one of the
reported frequency frequencies

L0000877D

Figure 2 UE Transfer at Poor Coverage Using a Search Zone (Part 2)

The following list provides a detailed description of the workflow in Figure 1.

Note: The description in this document of voicePrio and

connectedModeMobilityPrio normally refers to the MO attributes on
frequency relation MO classes. However, the feature Subscriber
Triggered Mobility provides a way to override these values for certain
UEs, see Subscriber Triggered Mobility for details on how this is
accomplished.

3.1 Process Steps

1. The UE connects to the cell.

2. The eNodeB determines a set of frequencies, LTE, or Inter-Radio Access

Technology (IRAT), where the UE can be transferred when it encounters
poor coverage in the current cell.
The eNodeB finds all frequency relations, that is, all instances of
EUtranFreqRelation , GeranFreqGroupRelation , UtranFreqRelation ,
Cdma2000FreqBandRelation , and UtranTDDFreqRelation

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 9

 Mobility Control at Poor Coverage

— The corresponding Coverage-Triggered Session Continuity feature is

active and enabled.

— According to the capabilities of the UE, as reported to the eNodeB in the

information element UE-EUTRA-Capability, the UE is able to operate on
the frequency band. When the Multiple Frequency Band Indicators
feature is operable, more frequencies can be supported by the UE.

— The corresponding RAT is not forbidden according to the Handover

Restriction List (HRL) of the UE (Forbidden Inter-RATs). See Shared
LTE RAN for more information about the HRL criteria:

— If the attribute allowedPlmnList of the frequency relation MO is non-

empty, then at least one of the PLMNs in this attribute matches one of
the PLMNs in the HRL of the UE (Serving PLMN and Equivalent
PLMNs).

3. If at least one of the frequencies determined in Step 2 has one of the

attributes connectedModeMobilityPrio or voicePrio set to a value
different from −1, the UE is configured to send an event-triggered
measurement report, Event A2 Search, when coverage provided by the
serving cell drops below the threshold for entering the search zone. Two A2
Search measurements can be configured in the UE: One that uses Reference
Signal Received Power (RSRP) and one that uses Reference Signal Received
Quality (RSRQ) as triggering quantity. Whether one or both of these are
configured is controlled by the attribute InhibitA2SearchConfig . See
Search Zone for UEs in Poor Coverage on page 21 for more details.

4. One of the Event A2 "Search" measurements, either RSRP or RSRQ, is

triggered in the UE and a measurement report is sent to the eNodeB from the
UE indicating that the UE enters the search zone for this triggering quantity.

Note: While the UE is in the search zone, it is not selected by the

Automated Neighbor Relations feature (ANR) to perform any
Physical Cell Identity (PCI) measurements for GERAN or UTRAN
based on UE inactivity. ANR-triggered PCI measurements for LTE
frequencies are configured when the UE attaches to the cell and are
not affected by the UE entering the search zone.

5. If set to a value different than 0 (default), a5B2MobilityTimer is started or

restarted.

6. The eNodeB stops the Event A2 Search measurement that triggered entering
into the search zone, see Step 4 and Step 7.The eNodeB starts the
measurements that must be active in the search zone. This is done differently
depending on if the eNodeB is configured for an outer search zone or not for
this triggering quantity and UE (see The Outer Search Threshold on page
23), and, when it is configured for an outer search zone, if the reported
Event A2 Search measurement indicated that the UE has entered the inner or
outer search zone:
— The eNodeB has not been configured for an outer search zone

10 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 • To detect if the UE moves back into a good coverage zone, the
eNodeB starts the Event A1 Good Coverage measurement that uses
the same trigger quantity (RSRP or RSRQ) as the Event A2 Search
measurement that was reported.

• To determine when the UE moves into a critical poor coverage zone,

the eNodeB starts the Event A2 Critical Coverage measurement that
uses the same trigger quantity (RSRP or RSRQ) as the Event A2
Search that was reported.

• To detect the candidate frequencies selected in Step 2, the eNodeB

starts the Target Good Enough measurements, Event A5 or A3 for
LTE frequencies and Event B2 for IRAT frequencies, that uses the
same trigger quantity (RSRP or RSRQ) that triggered the Event A2
Search that was reported. A frequency can be measured if the
following criteria are met:

— The UE supports measurements on the frequency.

— The eNodeB supports measurements on the frequency:

• The eNodeB supports measurements on an LTE frequency if

the MOM attribute ueMeasurementsActiveIF is TRUE.

• The eNodeB supports measurements on a GERAN

frequency group if the MOM attribute
ueMeasurementsActiveGERAN is TRUE.

• The eNodeB supports measurements on WCDMA/TD-

SCDMA frequency, if the MOM attribute
ueMeasurementsActiveUTRAN is TRUE and there are
configured cells for the frequency, that is, MO instances of
UtranCellRelation .

• The eNodeB supports measurements on a CDMA-eHRPD

frequency if the MOM attribute
ueMeasurementsActiveCDMA2000 is TRUE and there are
configured cells for the frequency, that is, MO instances of
Cdma2000CellRelation .

— The priority of the frequency states it can be measured. A

priority value of −1 means that the frequency is not measured. If
the UE has an active voice bearer with QCI1, the attribute
voicePrio is used to determine the priority. In this case,
frequency relation MOs that do not have this attribute is not
measured. If the UE does not have an active voice bearer with
QCI1, the attribute connectedModeMobilityPrio is used.

If the value of attribute inhibitB2RsrqConfig = TRUE , the

eNodeB does not configure RSRQ measurements for Event B2. For
more information, see Table 5.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 11

 Mobility Control at Poor Coverage

If more frequencies can be measured than configured in the UE,

some of the frequencies with the lowest priority are omitted
according to the priority attributes voicePrio or
connectedModeMobilityPrio. This depends on whether UE has an
active voice bearer with QCI1.

— The eNodeB has been configured for an outer search zone and the
received Event A2 Search measurement is for the inner search zone.

• To determine when the UE moves into the outer search zone, the
eNodeB starts the Event A2 Outer Search measurement that uses
the same trigger quantity (RSRP or RSRQ) as the Event A2 Search
that was reported, see To detect if the UE moves back into a good
coverage zone, the eNodeB starts the Event A1 Good Coverage
measurement that uses the same trigger quantity (RSRP or RSRQ)
as the Event A2 Search measurement that was reported.The Outer
Search Threshold on page 23.

• To detect the candidate frequencies selected in Step 2 which have

highTo detect if the UE moves back into a good coverage zone, the
priority, the eNodeB starts the Target Good Enough measurements,
Event A5 or A3 for LTE frequencies and Event B2 for IRAT
frequencies, that uses the same trigger quantity (RSRP or RSRQ)
that triggered the Event A2 Search that was reported. The
frequencies are selected in the same way as when the eNodeB has
not been configured for an outer search zone, with the added
restriction that only high priority frequencies are included. That is,
frequency relations where the priority attribute has a value equal to,
or higher than the value of the MO attribute lowPrioMeasThresh .

— The eNodeB has been configured for an outer search zone and the
received Event A2 Search measurement is for the outer search zone.

• To determine when the UE moves into a critical poor coverage zone,

the eNodeB starts the Event A2 Critical Coverage measurement that
uses the same trigger quantity (RSRP or RSRQ) as the Event A2
Search that was reported.

• To detect the candidate frequencies selected in Step 2 which have

low priority, the eNodeB starts the Target Good Enough
measurements, Event A5 or A3 for LTE frequencies and Event B2 for
IRAT frequencies, that uses the same trigger quantity (RSRP or
RSRQ) that triggered the Event A2 Search that was reported. The
frequencies are selected in the same way as when the eNodeB has
not been configured for an outer search zone, with the added
restriction that only low priority frequencies are included
(measurements for the high priority frequencies have already been
configured in the inner search zone). That is, frequency relations
where the priority attribute has a value lower than (but not equal to)
the value of the MO attribute lowPrioMeasThresh .

12 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 If the Automated Neighbor Relationsfeature (ANR) is active, it uses the
Target Good Enough measurement reports to detect unknown cells. See
Step 13. However, this is not possible for Event B2 UTRAN
measurements which always detect known cells only. To find unknown
UTRAN cells in the search zone, ANR sometimes configures a periodic
measurement with information element purpose =
reportStrongestCellsForSON on the same frequency as an Event B2
UTRAN Target Good Enough measurement. The ANR measurement is
configured in the UE only if it was not already configured earlier because
of an Event A2 Search triggered by RSRP or RSRQ.

If attribute inhibitB2RsrqConfig = TRUE , the ANR UTRAN

measurements with purpose = reportStrongestCellsForSON are
also inhibited, when UE is in RSRQ search zone (not RSRP search zone).

Note: The eNodeB does not start a new Event A1 measurement to

detect if the UE moves back from the outer to the inner search
zone.

7. The UE sends an Event A2 Search or Outer Search measurement report.

There can be several reasons for this:
— The UE was in the search zone for one of the trigger quantities, either
RSRQ or RSRP, and now the UE has entered the search zone also for the
other quantity.

— The eNodeB is configured for an inner or outer search zone (see The
Outer Search Threshold on page 23) for the reported trigger quantity,
for which the UE is already in the inner search zone, and now the UE has
entered the outer search zone for the same quantity.

8. If a bearer with QCI1 is set up while the UE is in the search zone for RSRP or
RSRQ or both:
— The a5B2MobilityTimer is restarted

— If the UE is in the search zone for RSRP all "Target Good Enough"
measurements using RSRP are removed from the UE and replaced by
new measurements for frequencies based on voicePrio. The same
measurements are configured as if the UE entered the search zone (that
is, if the A2 search RSRP or A2 Outer Search RSRP triggered in the UE)
with a bearer with QCI=1 already up, see step Step 6.

— If the UE is in the search zone for RSRQ all "Target Good Enough"
measurements using RSRQ are removed from the UE and replaced by
new measurements for frequencies based on voicePrio. The same
measurements are configured as if the UE entered the search zone (that
is, if the A2 search RSRQ or A2 Outer Search RSRQ triggered in the UE)
with a bearer with QCI=1 already up, see Step 6.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 13

 Mobility Control at Poor Coverage

Note: Which measurements to be set up are different depending on if

eNodeB has been configured for an outer search zone or not (see
The Outer Search Threshold on page 23), and if the UE is in the
outer search zone, or the inner search zone for the triggering
quantities (RSRP and RSRQ).

9. If a bearer with QCI1 is released while the UE is in the search zone for RSRP
or RSRQ or both:
— The a5B2MobilityTimer is restarted

— If the UE is in the search zone for RSRP all "Target Good Enough"
measurements using RSRP are removed from the UE and replaced by
new measurements for frequencies based on
connectedModeMobilityPrio. The same measurements are configured
as if the UE entered the search zone (that is, if the A2 search RSRP or A2
Outer Search RSRP triggered in the UE) without any bearer with QCI=1
already setup, see Step 6.

— If the UE is in the search zone for RSRQ all "Target Good Enough"
measurements using RSRQ are removed from the UE and replaced by
new measurements for frequencies based on
connectedModeMobilityPrio. The same measurements are configured
as if the UE entered the search zone (that is, if the A2 search RSRQ or A2
Outer Search RSRQ triggered in the UE) without a bearer with QCI=1
already setup, see Step 6.

Note: Which measurements to be set up are different depending on if

eNodeB has been configured for an outer search zone or not (see
The Outer Search Threshold on page 23), and if the UE is in the
outer search zone, or the normal (inner) search zone for the
triggering quantities (RSRP and RSRQ).

10. If an Event A1 Good Coverage measurement report arrives from the UE, the
UE has left the search zone for the reported triggering quantity (RSRP or
RSRQ) and entered good coverage again. There are three cases to consider:
— The UE is in the search zone only due to RSRP. In this case, the UE has
the Event A1 Good Coverage RSRP configured. When the UE reports
Event A1 Good Coverage RSRP, it means that the UE is now in good
coverage for both RSRP and RSRQ.

— The UE is in the search zone only due to RSRQ. In this case, the UE has
the Event A1 Good Coverage RSRQ configured. When the UE reports
Event A1 Good Coverage RSRQ, it means that the UE is now in good
coverage for both RSRP and RSRQ.

— The UE is in the search zone due to both RSRP and RSRQ. In this case,
the UE has the Event A1 Good Coverage RSRP configured, and A1 Good
Coverage RSRQ. If the UE reports Event A1 Good Coverage RSRP or
Event A1 Good Coverage RSRQ, the UE is still in the search zone for the
other triggering quantity.

14 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 In all cases, the Event A1 Good Coverage, Event A2 Critical Coverage or
Event A2 Outer Search, Event A3 or A5 Inter-Frequency, and Event B2 IRAT
Target Good Enough measurements based on the triggered quantity, RSRP
or RSRQ, are removed from the UE and replaced by the corresponding A2
Search measurement.
If the UE is now in good coverage for both triggering quantities, the timer
a5B2MobilityTimer is canceled and the eNodeB waits for Event A2 Search
Zone measurement reports. ANR can now configure PCI measurements in
the UE again.

11. The timer started in Step 5, a5B2MobilityTimer , expires. If the UE does not
have an active bearer with QCI1, which indicates a voice bearer, the eNodeB
stops all Event A5/A3/B2 "Target Good Enough" measurements started in
Step 6. If the UE has an active bearer with QCI1, the eNodeB restarts the
timer.

12. An Event A5/A3/B2 "Target Good Enough" measurement report arrives from
the UE for one of the frequencies.

13. If the best cell of the measurement report is unknown in the source cell, the
eNodeB sometimes informs the Automated Neighbor Relations (ANR)
feature about the cell and takes no further action, even if there are other
known cells in the same measurement report. This provides ANR with an
option to request the UE to report the unique Cell Global Identity (CGI) of the
potential neighbor cell before the next Event A5/A3/B2 Target Good Enough
measurement report arrives from the UE.
This occurs if the following criteria are met:

— ANR is OPERABLE, and must be activated for the specific RAT of the
measurement report. See MOM attributes anrInterFreqState and
anrStateGsm. Event B2 UTRAN measurement reports cannot include an
unknown cell. See Automated Neighbor Relations for information on
how to discover unknown UTRAN cells in the search zone.

— The best cell of the measurement report is unknown in the source cell,
that is, there is no cell relation to the reported cell from the source cell.

— No voice call is ongoing in the UE. That is, the UE has no bearer with
QCI1.

— The UE is able to do CGI measurements for the reported cell. For E-

UTRAN cells, this is indicated by FGI bits bit 5, 18 and 25, and for
GERAN cells by FGI bits 5 and 19.

— Either no earlier measurement report A5/A3-interfreq/B2 Target Good

Enough is received, or A3-intra-freq Best Cell has been ignored to enable
an ANR CGI measurement. That is, for a UE, at the most one
measurement report is ignored to allow for an ANR CGI measurement
while the UE is in the search zone.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 15

 Mobility Control at Poor Coverage

14. The eNodeB checks if a handover is allowed and possible to one of the
reported cells, starting with the strongest one.
A cell is a viable handover target if all of the following criteria are fulfilled:
— The attribute mobilityAction on the relevant frequency relation MO
has the value HANDOVER

— The relevant handover feature is OPERABLE (Coverage-Triggered Inter-

Frequency Handover, Coverage-Triggered WCDMA IRAT Handover,
Coverage-Triggered TD-SCDMA IRAT Handover, SRVCC Handover to
UTRAN, SRVCC Handover to GERAN)

— The UE has support for handover to the relevant RAT

— If the frequency has a different mode (for example TDD for FDD), then
the feature Intra-LTE Inter-Mode Handover must be OPERABLE and the
UE must support inter-mode handover

— The cell is defined in the MOM

— There is a cell relation to the cell from the serving cell in the MOM

— The attribute isHoAllowed=true on the cell relation MO

— The cell has a tracking area (TA) or location area (LA) which is not
forbidden according to the HRL of the UE

— The feature Cell Soft Lock has not temporarily set the cell as a non-
viable target.

For measurement reports on events A3, A5, B1, and B2, eNodeB can be
configured to perform extended check prior to handover. The check evaluates
non-triggering quantity received in the measurement report. Handover is
triggered only in the case when measured non-triggering quantity fulfills
configured conditions.

Description of checks performed for each of the events (where the

expressions are calculated based on MOM configuration values) are as
follows:
— Event A5
As a prerequisite, set the MO attribute bothA5RsrpRsrqCheck to true for
the extended "Good enough target cell on other LTE frequency" check.

The measured non-triggered quantity value must be higher than the

following expression:

Where:
X Stands for RSRP or RSRQ.

16 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 cellIndivOffsetn Stands for the cell individual offset value of the
neighbor cell.

qOffsetFreqn Stands for the frequency based offset of the

neighbor cell.

— Event A3

• Intra-frequency handover
As a prerequisite, set the MO attribute bothIntraA3RsrpRsrqCheck
to true for the extended "Good enough target cell on the same LTE
frequency" check.

The measured non-triggering quantity offset value must be higher

than the following expression:

Where:
X Stands for RSRP or RSRQ.

cellIndivOffsetn Stands for the cell individual offset value of the

neighbor cell.

• Inter-frequency handover
As a prerequisite, set the MO attribute bothInterA3RsrpRsrqCheck
to true for the extended "Good enough target cell on other LTE
frequency" check.

The measured non-triggering quantity offset value must be higher

than the following expression:

Where:
X Stands for RSRP or RSRQ.

cellIndivOffsetn Stands for the cell individual offset value of the

neighbor cell.

qOffsetFreqs Stands for the frequency based offset of the

serving cell.

qOffsetFreqn Stands for the frequency based offset of the

neighbor cell.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 17

 Mobility Control at Poor Coverage

Note: If bothInterA3RsrpRsrqCheck is enabled, sum of

EUtranFreqRelation.qOffsetFreq,
EUtranCellRelation.cellIndividualOffsetEUtran,
and
EUtranCellRelation.cellIndividualOffsetEUtranQci
1 exceeding ±1 dB has a significant impact on behavior.

— Events B1 and B2

• CSFB handover
As a prerequisite, set either the MO attribute bothB1RscpEcnoCheck
or bothB2RscpEcnoCheck to true.

The measured non-triggering quantity offset value must be higher

than the following expression:

Where:
X Stands for RSCP or ECNO.

CsfbThreshold2X Stands for the base configured threshold value.

qOffsetFreqn Stands for the frequency based offset of the

neighbor cell.

• UTRAN handover

As a prerequisite, set the MO attribute bothB2RscpEcnoCheck to

true for the extended "Good enough target cell IRAT" check.

The measured non-triggering quantity offset value must be higher

than the following expression:

B2Threshold2XUtra1 - qOffsetFreqn + hysteresisB2

Where:
X Stands for RSCP or ECNO.

qOffsetFreqn Stands for the frequency based offset of the

neighbor cell.

Note: If bothB2RscpEcnoCheck is enabled,

EUtranFreqRelation.qOffsetFreq exceeding ±1 dB has a
significant impact on behavior.

15. If the EUtranCellFDD.rwrSearchZoneAllowed or

EutranCellTDD.rwrSearchZoneAllowed parameter is set to FALSE, release
with redirect is not allowed. The eNodeB takes no further action in this case.

18 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 This means that the UE remains in the cell and waits for another Target
Good Enough, Good Coverage, Critical Coverage, or Search Zone
measurement report. If the EUtranCellFDD.rwrSearchZoneAllowed or
EUtranCellTDD.rwrSearchZoneAllowed parameter is set to TRUE, the next
check is performed.

16. If the UE has an active bearer with QCI1 indicating a voice bearer, a release
of the UE is not allowed and the eNodeB takes no further action. That is, the
UE remains in the cell and waits for another Target Good Enough, Good
Coverage, Critical Coverage or possibly Search Zone measurement report.
This can be changed by setting parameter allowReleaseQci1 to TRUE, but
this parameter only has any effect when neither of the features SRVCC
Handover to UTRAN or SRVCC Handover to GERANare OPERABLE. If the
eNodeB performs a release with redirect, the default behavior in a Core
Network is to remove the voice connection.
If the UE does not have an active bearer with QCI1, the eNodeB initiates a
release with redirect to the frequency of the measurement report.

17. An Event A2 Critical Coverage measurement report arrives from the UE.

18. A prioritized list of possible target frequencies when the UE has reached
critical coverage is determined by doing the following:
— Start with the list of frequencies found in Step 2.

— If the attribute excludeInterFreqAtCritical is true, remove all E-

UTRAN frequencies.

— Decide which priority to use:

• If the UE has an active bearer with QCI1, use attribute voicePrio

on the frequency relation MOs. Any frequency relation which does
not have a voicePrio is considered to have priority −1.

• If the UE does not have an active bearer with QCI1, use attribute
connectedModeMobilityPrio.

— Order the list according to the selected priority, and remove all
frequencies with priority −1.

— If a frequency has been measured in the search zone for longer than the
time indicated by attribute searchEffortTime , it is considered to be a
non-feasible target, since no measurement report was triggered in the
UE. Exclude all such frequencies from the list, unless this action leaves
the list empty, in which case the list is left unmodified by this step.

The special value 0 for searchEffortTime means that the list is always
unmodified by this step.

19. The eNodeB checks if a blind handover is possible to a cell on one of the
frequencies with the highest priority in the list from Step 18.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 19

 Mobility Control at Poor Coverage

A cell is a viable blind handover target if all of the following criteria are
fulfilled:
— The attribute mobilityAction on the relevant frequency relation MO
has the value HANDOVER

— The relevant handover feature is OPERABLE (Coverage-Triggered Inter-

Frequency Handover, Coverage-Triggered WCDMA IRAT Handover,
Coverage-Triggered TD-SCDMA IRAT Handover, SRVCC Handover to
UTRAN, SRVCC Handover to GERAN)

— The UE has support for handover to the relevant RAT

— If the frequency has a different mode (for example TDD for FDD), then
the feature Intra-LTE Inter-Mode Handover must be OPERABLE and the
UE must support inter-mode handover

— The cell is defined in the MOM

— There is a cell relation to the cell from the serving cell in the MOM

— The attribute isHoAllowed=true on the cell relation MO

— The attribute coverageIndicator=COVERS on the cell relation MO

— The attribute covTriggerdBlindHoAllowed=true on the serving cell

— The cell has a tracking area (TA) or location area (LA) which is not
forbidden according to the HRL of the UE

— The feature Cell Soft Lock has not temporarily set the cell as a non-
viable target.

20. If the EUtranCellFDD.rwrCriticalZoneAllowed or

EUtranCellTDD.rwrCriticalZoneAllowed is set to FALSE, release with
redirect is not allowed. The eNodeB takes no further action in this case.
This means that the UE remains in the cell and waits for another Target
Good Enough, Good Coverage, Critical Coverage, or Search Zone
measurement report. If the EUtranCellFDD.rwrCriticalZoneAllowed or
EUtranCellTDD.rwrCriticalZoneAllowed parameter is set to TRUE, the
next check is performed.

Note: Parameters EUtranCellFDD.rwrCriticalZoneAllowed or

EUtranCellTDD.rwrCriticalZoneAllowed are only allowed to be
changed by Ericsson personnel.

21. If the UE has an active bearer with QCI1 indicating a voice bearer, a release
of the UE is not allowed and the eNodeB takes no further action. That is, the
UE remains in the cell and waits for another Target Good Enough, Good
Coverage, Critical Coverage or Search Zone measurement report. This
behavior can be changed by setting attribute allowReleaseQci1 to TRUE,
but this attribute only has any effect when neither of the features SRVCC

20 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 Handover to UTRAN or SRVCC Handover to GERANare OPERABLE. If the
eNodeB performs a release with redirect, the default behavior in a Core
Network is to remove the voice connection.
If the UE does not have an active bearer with QCI1, the eNodeB initiates a
release with redirect to the frequency with the highest priority in the list
determined in Step 18.

3.2 Search Zone for UEs in Poor Coverage

A search zone in a cell is a zone in the cell following the cell edge, where UEs
approaching poor coverage in the serving cell start to search for alternative
frequencies where the UE can be transferred.

The search zone is detected by Event A2 or Event A5 measurements.

Critical Coverage
Threshold

Search zone

Critical Zone
Good Coverage

Event A2 Search

Event A1 Good
Coverage

Search Threshold
Event A2 Critical Coverage

L0000721B

Figure 3 Cell Search and Critical Zone Defined by Search and Critical Thresholds

The search zone can be split into an inner and an outer search zone. In the inner
search zone the UE only searches for frequencies with high priority.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 21

 Mobility Control at Poor Coverage

Outer Search Zone Critical Coverage

Threshold
Inner Search Zone

Good Coverage

Outer Search
Event A2 Search Threshold

Event A1 Good
Coverage

Event A2 Outer
Search

Inner Search
Threshold
Event A2 Critical

L0001147A

Figure 4 Cell Search Zone Defined by Inner and Outer Search Thresholds

3.2.1 The Search Threshold

To detect that the UE has entered the (inner) search zone, Event A2 Search
measurements are configured in the UE when it attaches to the cell. Depending
on the value of the ReportConfigSearch.inhibitA2SearchConfig attribute,
one or two measurements are configured, using RSRP or RSRQ or one of each as
triggering quantities. When an Event A2 Search measurement triggers, the UE is
considered to be in the search zone for the reported triggering quantity. To detect
when the UE leaves the search zone and enters into good coverage again,
corresponding Event A1 Good Coverage measurements are configured in the UE.

The report configuration for both the Event A2 Search and Event A1 Good
Coverage measurements are based on parameters in the
UeMeasControl.ReportConfigSearch MO.

These measurements replace the Poor Coverage measurements introduced by

the Session Continuity features.

The report configurations for these measurements are also affected by the
Service Triggered Mobility and Multi-Layer Service-Triggered Mobility features.

22 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

3.2.2 The Outer Search Threshold
It is possible to configure the eNodeB such that the search zone is divided into an
inner and an outer search zone. This is done separately for RSRP and RSRQ by
setting the ReportConfigSearch.a2OuterSearchThrRsrpOffset and
ReportConfigSearch.a2OuterSearchThrRsrqOffset attributes to a value
lower than 0. If an outer search zone is defined, the UE is configured with an
Event A2 Outer Search measurement when it enters the inner search zone, as
detected by the Event A2 Search measurement, see Step 6 in Process Steps on
page 9.

Note: The UE only uses an inner/outer search zone if there are low priority
frequency relations, which are searched for in the outer, but not the
inner, search zone. That is, only if there are frequency relations where
the priority attribute has a value lower than (but not equal to) the value
of the UeMeasControl.lowPrioMeasThresh MO attribute. In other
cases, a standard search zone is used.

3.2.3 The Critical Threshold

To detect that the UE has encountered critical coverage, the Event A2 Critical
Coverage measurements are configured in the UE when it enters the search zone.
See Step 6 in Section 3.1 and Step 10 in Section 3.1 for more details on when
these are configured in the UE. The report configuration for these are all based on
parameters in the ReportConfigSearch MO, see Table 3.

These measurements replace the Poor Coverage measurements introduced by

the Session Continuity features.

The report configurations for these measurements are not affected by the Service
Triggered Mobility or Multi-Layer Service-Triggered Mobility features, but they
are affected by the ReportConfigSearch.a2CriticalThrQci1RsrpOffset and
ReportConfigSearch.a2CriticalThrQci1RsrqOffset attributes, which can
move the critical threshold when the UE has a bearer with QCI1.

When the High Power UE and the Multi-Layer Service-Triggered Mobility

features are active, this threshold can change if a higher power class is used,
which extends the cell coverage.

RELATED INFORMATION

3.2.1 The Search Threshold on page 22

3.2.2 The Outer Search Threshold on page 23

3.3 Level Based Search Zone Transitions

When the UE enters the search zone and a measurement report is received in
Step 6 in Process Steps on page 9, the eNodeB configures a new measurement to

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 23

 Mobility Control at Poor Coverage

detect when the UE reaches the critical threshold or the outer search zone.
However, the received measurement report contains the measured RSRP or
RSRQ value, and if the quantity has dropped quickly for the UE, it can already
fulfill the threshold for critical coverage or outer search zone.

In this case, the default behavior of the eNodeB is to take the appropriate action
without first configuring the measurement for which it knows that the thresholds
are already fulfilled, as described below. If this behavior is not desired, it is
possible to disable it by setting the MOM attribute
UeMeasControl.checkA2SearchLevel to FALSE, which makes the eNodeB
ignore the reported values for RSRP and RSRQ.

3.3.1 Using One Search Zone

If the received search zone measurement report is using RSRP and it contains a
measured value which fulfills the critical RSRP threshold, or it is using RSRQ and
it contains a measured value which fulfills the critical RSRQ threshold, the
eNodeB skips directly to Step 16 in Process Steps on page 9, without first
configuring an A2 Critical measurement, or any A5/A3/B2 measurements in the
UE. The following cases apply:

— A cell suitable for blind handover exists. I this case a handover to this cell is
initiated.

— The UE does not have a bearer with QCI=1 (and no cell suitable for blind
handover exists). In this case a release with redirect is initiated.

— The UE has a bearer with QCI=1 (and no cell suitable for blind handover
exists). When entering into critical coverage from the search zone this would
mean that nothing happens and the UE remains in the cell with the same set
of A5/A3/B2 measurements, and A2 critical measurement. But in this case,
these measurements have not been configured in the UE since it entered
critical coverage directly from good coverage. This case does not get any
special handling and all measurements is configured in the UE as in Step 6 in
Process Steps on page 9 and onwards.

3.3.2 Using an Inner/Outer Search Zone

The following cases are possible:

— The UE goes directly from Good Coverage to the Outer Search Zone. That is,
the received search zone measurement report is using RSRP and it contains a
measured value which fulfills the outer search zone RSRP threshold, or it is
using RSRQ and it contains a measured value which fulfills the outer search
zone RSRQ threshold.

In this case, Event A5/A3/B2 measurements for both high and low priority
frequencies are configured in the UE, which effectively makes this similar to
how a UE is configured in the search zone when there is only one single
search zone (no inner/outer split). Measurements for Event A1 Good

24 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 Coverage and Event A2 Critical Coverage are also configured. See Step 6 in
Process Steps on page 9 for more details.

— The UE goes directly from Good Coverage to Critical Coverage. That is, the
received search zone measurement report is using RSRP and it contains a
measured value which fulfills the critical RSRP threshold, or it is using RSRQ
and it contains a measured value which fulfills the critical RSRQ threshold.

This case is handled in the exact same way as when the UE goes from good
coverage to critical coverage when just a single search zone is configured.

— The UE goes directly from the Inner Search Zone to Critical Coverage. That is,
the received outer search zone measurement report is using RSRP and it
contains a measured value which fulfills the critical RSRP threshold. Or, it is
using RSRQ and it contains a measured value which fulfills the critical RSRQ
threshold.

This case is handled in almost the same way as when the UE goes from good
coverage to critical coverage when just a single search zone is configured.
The end result is the same, but the major difference is that since the UE has
previously entered the inner search zone, the UE is already configured with
Event A5/A3/B2 measurements for high priority frequencies. Only Event
A5/A3/B2 measurements for low priority frequencies are configured in the
UE in this case. Event A1 good coverage measurement is already configured
in the UE, but Event A2 outer search measurement is removed from the UE.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 25

 Mobility Control at Poor Coverage

4 Network Impact of Mobility Control at Poor

Coverage

Capacity and Performance

The Mobility Control at Poor Coverage feature ensures that network capacity is
enhanced by improving the way the UE is served by providing the best available
frequency in the network.

It is possible to configure this feature in such a way that an off-loading effect is

achieved, where UEs are transferred from the LTE frequency to another LTE or
IRAT frequency. This can be used to avoid overload and improve the overall
network capacity.

Note: There is a possibility that configuring the measurements in this way can
result in too many measurement reports being sent from the UE. This
can have a detrimental effect on network capacity and end-user
perceived service quality.

Interfaces
No impact.

Other Network Elements

The feature has no impact on the physical cell coverage. However, off-loading
UEs to alternative frequencies indirectly means that coverage is improved.

Note: Activating the feature and setting the threshold for critical coverage puts
limits on the range of UEs in the LTE network.

The UE is running on the operator preferred frequency more often. Measurement

gap is more frequently used.

26 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 Parameters

5 Parameters

5.1 Feature Configuration Parameters

Table 2 describes the parameters introduced by the feature which are related to
detecting the Search Threshold. They are used for the measurement report
configurations of the two Event A2 Search measurements: One using RSRP and
one RSRQ and the two Event A1 Good Coverage measurements, one using RSRP
and one RSRQ.

Table 2 Search Threshold Parameters

Parameter
a1a2SearchThresholdRsrp
a1a2SearchThresholdRsrq
hysteresisA1A2SearchRsrp
hysteresisA1A2SearchRsrq
hysteresisA2OuterSearchRsrp
hysteresisA2OuterSearchRsrq
searchEffortTime
timeToTriggerA1Search
timeToTriggerA1SearchRsrq
timeToTriggerA2Search
timeToTriggerA2SearchRsrq
timeToTriggerA2OutSearch
timeToTriggerA2OutSearchRsrq
a2OuterSearchThrRsrpOffset
a2OuterSearchThrRsrqOffset
Description
The RSRP threshold for the Event A1 and Event A2 RSRP Search
measurements.
The RSRQ threshold for the Event A1 and Event A2 RSRQ Search
measurements.
The RSRP hysteresis used by the Event A1 and Event A2 RSRP
Search measurements.
The RSRQ hysteresis used by the Event A1 and Event A2 RSRQ
Search measurements.
Hysteresis value for RSRP in event A2 Outer Search measurements.
Hysteresis value for RSRQ in event A2 Outer Search measurements.
a1a2SearchTThe time used to determine whether the measured
frequencies are to be excluded for mobility action at critical
threshold or not. Special value: 0 means infinity.
Time-to-trigger value for Event A1 Search measurement. Used for
both RSRP and RSRQ if timeToTriggerA1SearchRsrq has value -1,
otherwise this attribute is used only for RSRP.
Time-to-trigger value for Event A1 Search measurement with
trigger quantity RSRQ. The value -1 means that this attribute is not
used and timeToTriggerA1Search is used also for RSRQ.
Time-to-trigger value for Event A2 Search measurement. Used for
both RSRP and RSRQ if timeToTriggerA2SearchRsrq has value -1,
otherwise this attribute is used only for RSRP.
Time-to-trigger value for Event A2 Search measurement with
trigger quantity RSRQ. The value -1 means that this attribute is not
used and timeToTriggerA2Search is used also for RSRQ.
Time-to-trigger value for Event A2 Outer Search measurement.
Used for both RSRP and RSRQ if timeToTriggerA2OutSearchRsrq
has value -1, otherwise this attribute is used only for RSRP.
Time-to-trigger value for measurement in event A2OuterSearch
with trigger quantity RSRQ. The value -1 means that this attribute is
not used for report configuration.
Time-to-trigger value for Event A2 Outer Search measurement with
trigger quantity RSRQ. The value -1 means that this attribute is not
used and timeToTriggerA2OutSearch is used also for RSRQ.
Offset for threshold a1a2SearchThresholdRsrp to configure RSRP
threshold value for events A2OuterSearch.
Offset for threshold a1a2SearchThresholdRsrq to configure RSRQ
threshold value for events A2OuterSearch.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 27

 Mobility Control at Poor Coverage
Table 3 Critical Threshold Parameters
Parameter
a2CriticalThresholdRsrp
a2CriticalThresholdRsrq
hysteresisA2CriticalRsrp
hysteresisA2CriticalRsrq
timeToTriggerA2Critical
timeToTriggerA2CriticalRsrq
a2CriticalThrQci1RsrpOffset
a2CriticalThrQci1RsrqOffset
Table 4 UE Measurement Active Parameters
Parameter
ueMeasurementsActiveIF
ueMeasurementsActiveUTRAN
ueMeasurementsActiveGERAN
ueMeasurementsActiveCDMA2000
Table 5 Feature-Specific Parameters
Parameter
mobCtrlAtPoorCovActive
inhibitA2SearchConfig
bothA5RsrpRsrqCheck
bothB1RscpEcnoCheck
28
Description
The RSRP threshold for the Event A2 RSRP Critical Coverage
measurements.
The RSRQ threshold for the Event A2 RSRQ Critical Coverage
measurements.
The RSRP hysteresis used by the Event A2 RSRP Critical Coverage
measurements.
The RSRQ hysteresis used by the Event A2 RSRQ Critical Coverage
measurements.
The time-to-trigger value for both the RSRP and RSRQ Event A2
Critical Coverage measurements.
Time-to-trigger value for Event A2 Critical measurement. Used for
both RSRP and RSRQ if timeToTriggerA2CriticalRsrq has value
-1, otherwise this attribute is used only for RSRP.
Time-to-trigger value for Event A2 Critical measurement with
trigger quantity RSRQ. The value -1 means that this attribute is not
used and timeToTriggerA2Critical is used also for RSRQ.
QCI1 offset (used also for QCIs with serviceType PTT) on cell level
for threshold a2CriticalThresholdRsrp , RSRP threshold value for
events A2Critical.
QCI1 offset (used also for QCIs with serviceType PTT) on cell level
for threshold a2CriticalThresholdRsrq , RSRQ threshold value for
events A2Critical.
Description
Activates or deactivates E-UTRAN inter-frequency measurements
for mobility purposes when Mobility Control at Poor Coverage
feature is enabled.
Activates or deactivates UTRAN measurements for mobility
purposes when Mobility Control at Poor Coverage feature is
enabled.
Activates or deactivates GERAN measurements for mobility
purposes when Mobility Control at Poor Coverage feature is
enabled.
Activates or deactivates CDMA2000 measurements for mobility
purposes when Mobility Control at Poor Coverage feature is
enabled.
Description
Specifies if the Mobility Control at Poor Coverage
feature is enabled or disabled in the cell.
Makes it possible to inhibit A2Search Report
configuration for RSRP or RSRQ.
Used to activate or deactivate the extended A5
"Target Good Enough" check. For more information,
see Radio Network (DU Radio Node).
This attribute is used to turn on/off the functionality
for checking the second value - RSRP or RSRQ - in an
A5 Target Good Enough measurement report
triggered by RSRQ or RSRP respectively.
Used to activate or deactivate the extended B1
"Good enough target cell IRAT" check. For more
40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28
 Parameters

Parameter Description
information, see Radio Network (DU Radio Node).
This attribute is used to turn on or off the
functionality for checking the non-trigger value
(RSCP or ECNO) in a B1 "Good enough target cell
IRAT" measurement report triggered by RSCP or
ECNO respectively.
bothB2RscpEcnoCheck Used to activate or deactivate the extended B2
"Good enough target cell IRAT" check. For more
information, see Radio Network (DU Radio Node).
This attribute is used to turn on or off the
functionality for checking the non-trigger value
(RSCP or ECNO) in a B2 "Good enough target cell
IRAT" measurement report triggered by RSCP or
ECNO respectively.
bothIntraA3RsrpRsrqCheck Used to activate or deactivate the extended A3
"Good enough target cell on the same LTE frequency"
check. For more information, see Radio Network (DU
Radio Node). This attribute is used to turn on or off
the functionality for checking the non-trigger value
(RSRP or RSRQ) in an A3 "Good enough target cell
on the same LTE frequency" measurement report
triggered by RSRQ or RSRP respectively.
bothInterA3RsrpRsrqCheck Used to activated or deactivate the extended A3
"Good enough target cell on other LTE frequency"
check. For more information, see Radio Network (DU
Radio Node). This attribute is used to turn on or off
the functionality for checking the non-trigger value
(RSRP or RSRQ) in an A3 "Good enough target cell
on other LTE frequency" measurement report
triggered by RSRQ or RSRP respectively.
inhibitB2RsrqConfig Disables or enables configuration of B2-RSRQ if
Event A2Search-RSRQ is triggered when the UE
enters the search zone.
lowPrioMeasThresh Frequency priority threshold to specify the low
priority measurement group from
connectedModeMobilityPrio or voicePrio in search
zone. Those less than this threshold is put in low
priority measurement group and can be configured
after event A2OuterSearch is triggered from UE.
excludeInterFreqAtCritical If set, E-UTRA Inter-frequencies must be excluded
when eNodeB selects the highest priority frequency
at A2Critical.
timeToTriggerA3Rsrq Time-to-trigger value for inter-frequency event A3
with trigger quantity RSRQ. If set to -1, this attribute
is not used for report configuration and instead the
attribute timeToTriggerA3 is used. Note: This
attribute is never used by the feature Coverage-
Triggered Inter-Frequency Session Continuity.
a3RsrqOffset Offset to obtain the A3 Offset for inter-frequency A3
measurement for trigger quantity RSRQ. The A3
offset for RSRQ = a3offset + a3RsrqOffset. Note:
This attribute is never used by the feature Coverage-
Triggered Inter-Frequency Session Continuity
hysteresisA3RsrqOffset Offset to obtain the Hysteresis for inter-frequency A3
measurement for trigger quantity RSRQ. The A3
hysteresis for RSRQ = hysteresisA3 +
hysteresisA3RsrqOffset. Note: This attribute is
never used by the feature Coverage-Triggered Inter-
Frequency Session Continuity
hysteresisA5RsrqOffset Offset to obtain the hysteresis for A5 measurement
for trigger quantity RSRQ. hysteresisA5Rsrq =
hysteresisA5 + hysteresisA5RsrqOffset. Note:
This attribute is never used by the feature Coverage-
Triggered Inter-Frequency Session Continuity.
timeToTriggerA5Rsrq Time-to-trigger value for event A5 with trigger
quantity RSRQ. If set to -1, this attribute is not used
for report configuration and instead the attribute
timeToTriggerA5 is used. Note: This attribute is

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 29

 Mobility Control at Poor Coverage
Parameter
ReportConfigB2Utra.timeToTriggerB2Rsrq
ReportConfigB2Utra.hysteresisB2RsrqOffset
ReportConfigB2Geran.timeToTriggerB2Rsrq
ReportConfigB2Geran.hysteresisB2RsrqOffset
ReportConfigB2Cdma2000.timeToTriggerB2Rsrq
ReportConfigB2Cdma2000.hysteresisB2RsrqOffse
t for trigger quantity RSRQ. hysteresisB2Rsrq =
thresholdEcNo
thresholdRscp
hysteresis
checkA2SearchLevel
EUtranCellFDD.rwrSearchZoneAllowed
EUtranCellTDD.rwrSearchZoneAllowed
EUtranCellFDD.rwrCriticalZoneAllowed(1)
EUtranCellTDD.rwrCriticalZoneAllowed(1)
30
Description
never used by the feature Coverage-Triggered Inter-
Frequency Session Continuity.
Time-to-trigger value for event B2 with trigger
quantity RSRQ. If set to -1, this attribute is not used
for report configuration and instead the attribute
timeToTriggerB2 is used. Note: This attribute is
never used by the feature Coverage-Triggered
WCDMA Session Continuity or Coverage-Triggered
TD-SCDMA Session Continuity.
Offset to obtain the hysteresis for B2 measurement
for trigger quantity RSRQ. hysteresisB2Rsrq =
hysteresisB2 + hysteresisB2RsrqOffset. Note:
This attribute is never used by the feature Coverage-
Triggered WCDMA Session Continuity or Coverage-
Triggered TD-SCDMA Session Continuity.
Time-to-trigger value for event B2 with trigger
quantity RSRQ. If set to -1, this attribute is not used
for report configuration and instead the attribute
timeToTriggerB2 is used. Note: This attribute is
never used by the feature Coverage-Triggered
GERAN Session Continuity.
Offset to obtain the hysteresis for B2 measurement
for trigger quantity RSRQ. hysteresisB2Rsrq =
hysteresisB2 + hysteresisB2RsrqOffset. Note:
This attribute is never used by the feature Coverage-
Triggered GERAN Session Continuity.
Time-to-trigger value for event B2 with trigger
quantity RSRQ. If set to -1, this attribute is not used
for report configuration and instead the attribute
timeToTriggerB2 is used. Note: This attribute is
never used by the feature Coverage-Triggered
CDMA-eHRPD Session Continuity.
Offset to obtain the hysteresis for B2 measurement
hysteresisB2 + hysteresisB2RsrqOffset. Note:
This attribute is never used by the feature Coverage-
Triggered CDMA-eHRPD Session Continuity.
Used to obtain threshold value for B1 or B2 extended
handover check of CSFB when RSCP is the trigger
quantity.
Used to obtain threshold value for B1 or B2 extended
handover check of CSFB when RSCP is triggered.
Used to obtain hysteresis value for B1 or B2
extended handover check of CSFB.
Disables or enables functionality of Level Based
Search Zone Transitions. If enabled, eNodeB checks
reported RSRP or RSRQ level of A2 Search or A2
Outer Search measurement to trigger measurement
and mobility action.
For FDD, the parameter allows for the release-with-
redirect in search zone when the
EUtranFreqRelation.mobilityAction attribute is
configured as HANDOVER.
For TDD, the parameter allows for the release-with-
redirect in search zone when the
EUtranFreqRelation.mobilityAction attribute is
configured as HANDOVER.
For FDD, the parameter allows for release-with-
redirect in critical zone when the
EUtranFreqRelation.mobilityAction attribute is
configured as HANDOVER.
For TDD, the parameter allows for release-with-
redirect in critical zone when the
EUtranFreqRelation.mobilityAction attribute is
configured as HANDOVER.
40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28
 Parameters

(1) This parameter is only allowed to be changed by Ericsson personnel.

Attribute ENodeBFunction.zzztemporary55 is used to enable machine learning

to find best frequencies.

5.2 Affected Parameters

The implementation of this feature affects no parameters.

5.3 Parameters Affecting the Feature

The parameters of the Coverage-Triggered Session Continuity feature still apply,
especially the A3 tables and A5 tables in Coverage-Triggered Inter-Frequency
Session Continuity, and B2 tables in Coverage-Triggered CDMA-eHRPD Session
Continuity, Coverage-Triggered GERAN Session Continuity, and Coverage-
Triggered WCDMA Session Continuity when the Mobility Control at Poor
Coverage feature is enabled. The following exceptions apply:

— The configuration parameters for Event A1 and Event A2 Poor Coverage no

longer apply. See the A1 and A2 tables for Coverage-Triggered Inter-
Frequency Session Continuity, since these measurements are replaced in this
feature. However, the UeMeasControl.filterCoefficientEUtraRsrp,
UeMeasControl.filterCoefficientEUtraRsrq, and
UeMeasControl.sMeasure parameters still apply.

— The UeMeasControl.ueMeasurementsActive parameter is not used, and is

replaced by the following new parameters:
— UeMeasControl.ueMeasurementsActiveIF

— UeMeasControl.ueMeasurementsActiveUTRAN

— UeMeasControl.ueMeasurementsActiveGERAN

— UeMeasControl.ueMeasurementsActiveCDMA2000

— The triggerQuantityA3, triggerQuantityA5, and triggerQuantityB2

parameters are not used. Instead, the source and target cell-related trigger
quantity in the A3/A5 measurements and the source cell-related trigger
quantity in the B2 measurements configured in the search zone is set
according to the quantity (RSRP or RSRQ) that triggered the Event A2
measurement report.

Note: There are several attributes for event A3, A5, and B2 which are relevant
for this feature, but not for the Coverage-Triggered Session Continuity
features.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 31

 Mobility Control at Poor Coverage

6 Performance

6.1 Key Performance Indicators

This feature has no associated Key Performance Indicators (KPIs).

6.2 Counters
The following counters are associated with this feature:

— EUtranCellFDD MO and EUtranCellTDD MO

• pmErabRelAbnormalMmeActCritCov

• pmUeCtxtRelAbnormalEnbCritCov

• pmErabRelAbnormalEnbCritCov

• pmErabRelAbnormalEnbActCritCov

• pmUeCtxtRelAbnormalEnbActCritCov

• pmErabRelAbnormalMmeCritCov

• pmUeCtxtRelAbnormalMmeCritCov

• pmUeCtxtRelAbnormalMmeActCritCov

• pmCovGoodZoneSum

• pmCovGoodZoneSamp

• pmCovSearchZoneSum

• pmCovSearchZoneSamp

• pmCovCriticalZoneSum

• pmCovCriticalZoneSamp

• pmCriticalBorderEvalReportAct

• pmBadCovMeasTimeDistr

• pmCriticalBorderEvalReport

Note: This counter is used instead of pmBadCovEvalReport when the

feature Mobility Control at Poor Coverage is activated.

32 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 Performance

• pmBadCovSearchEvalReport

• pmBadCovSearchEvalReportRsrp

• pmCriticalBorderEvalReportRsrp

• pmGoodCovSearchEvalReport

• pmGoodCovSearchEvalReportRsrp

• pmBadCovOutSearchEvalReport

• pmBadCovOutSearchEvalReportRsrp

• pmA3InterFBestCellEvalReport

• pmA3InterFBestCellEvalReportRsrp

• pmA5BestCellEvalReport

• pmA5BestCellEvalReportRsrp

• pmB2BestCellEvalReport

• pmB2BestCellEvalReportRsrp

• pmCellHoExeAttLteInterFUeMeas

• pmCellHoExeAttLteInterFUeMeasRsrp

• pmCellHoExeSuccLteInterFUeMeas

• pmCellHoExeSuccLteInterFUeMeasRsrp

• pmUeCtxtRelSCEUtraBestCellRsrp

• pmUeCtxtRelSCEUtraBestCellRsrq

• pmUeCtxtRelSCEUtraA2Rsrp

• pmUeCtxtRelSCEUtraA2Rsrq

• pmUeCtxtRelSCUtranB2Rsrp

• pmUeCtxtRelSCUtranB2Rsrq

• pmUeCtxtRelSCUtranA2Rsrp

• pmUeCtxtRelSCUtranA2Rsrq

• pmUeCtxtRelSCGsmB2Rsrp

• pmUeCtxtRelSCGsmB2Rsrq

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 33

 Mobility Control at Poor Coverage

• pmUeCtxtRelSCGsmA2Rsrp

• pmUeCtxtRelSCGsmA2Rsrq

• pmUeCtxtRelSCCdmaB2Rsrp

• pmUeCtxtRelSCCdmaB2Rsrq

• pmUeCtxtRelSCCdmaA2Rsrp

• pmUeCtxtRelSCCdmaA2Rsrq

• pmHoExeOutAttLteInterFMcPtt

• pmHoExeOutAttLteInterFNonMcPtt

• pmHoExeOutSuccLteInterFMcPtt

• pmHoExeOutSuccLteInterFNonMcPtt

— EUtranCellFDD.pmBadCovMeasTimeActDistr

— EUtranCellTDD.pmBadCovMeasTimeActDistr

— EUtranCellRelation MO

• pmHoExeOutAttLteInterFQci1

• pmHoExeOutSuccLteInterFQci1

For a full list with detailed information about counters, see the list files in the List
Files library folder.

6.3 PM Events
Table 6 lists the PM events associated with the Mobility Control at Poor Coverage
feature.

Table 6 PM Events
Event
INTERNAL_PROC_UE_CTXT_RELEASE
INTERNAL_EVENT_UE_MOBILITY_EVAL
INTERNAL_EVENT_MEAS_CONFIG_A1
INTERNAL_EVENT_MEAS_CONFIG_A2
Description
Generated for the UE Context Release procedure to release
a UE Context. Contains information about the releasing
node, cause, and bearer information.
Mobility trigger and decision information has occurred.
When a UE is to be configured using RRC Connection
Reconfiguration to report measurements on E-UTRA with
Report Configuration of type Event A1 - Serving becomes
better than absolute threshold. See 3GPP TS 36.331.
When a UE is to be configured using RRC Connection
Reconfiguration to report measurements on E-UTRA with
Report Configuration of type Event A2 - Serving becomes
worse than absolute threshold. See 3GPP TS 36.331.

34 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28


Event
INTERNAL_EVENT_MEAS_CONFIG_A3
INTERNAL_EVENT_MEAS_CONFIG_A5
INTERNAL_EVENT_MEAS_CONFIG_B2_CDMA2000
INTERNAL_EVENT_MEAS_CONFIG_B2_GERAN
INTERNAL_EVENT_MEAS_CONFIG_B2_UTRA
For a full list with detailed information about PM events, see the list files in the
List Files library folder.
40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28
Performance
Description
When a UE is to be configured using RRC Connection
Reconfiguration to report measurements on E-UTRA with
Report Configuration of type Event A3 - Neighbour
becomes amount of offset better than serving. See 3GPP TS
36.331.
When a UE is to be configured using RRC Connection
Reconfiguration to report measurements on E-UTRA with
Report Configuration of type Event A5 - Serving becomes
worse than absolute threshold1 AND Neighbour becomes
better than another absolute threshold2. See 3GPP TS
36.331.
When a UE is to be configured using RRC Connection
Reconfiguration to report measurements on CDMA2000
with Report Configuration of type Event B2 - Serving
becomes worse than absolute threshold1 AND Neighbour
becomes better than another absolute threshold2. See
3GPP TS 36.331.
When a UE is to be configured using RRC Connection
Reconfiguration to report measurements on GERAN with
Report Configuration of type Event B2 - Serving becomes
worse than absolute threshold1 AND Neighbour becomes
better than another absolute threshold2. See 3GPP TS
36.331.
When a UE is to be configured using RRC Connection
Reconfiguration to report measurements on UTRA with
Report Configuration of type Event B2 - Serving becomes
worse than absolute threshold1 AND Neighbour becomes
better than another absolute threshold2. See 3GPP TS
36.331.
35
 Mobility Control at Poor Coverage

7 Activate Mobility Control at Poor Coverage

To use the feature, it must be activated following the usual feature

activation procedure.

Prerequisites

— The license key is installed in the node.

— Continuous Cell Trace Recording (CCTR) is activated since at least one week.
This ensures there is troubleshooting data available if something goes
wrong.

Steps

1. Set the FeatureState.featureState attribute to ACTIVATED in the

applicable MO instance, depending on node type:

Node Type License Control MO

DU Radio Node OptionalFeatureLicense=MobCtrlAtPoorCov
Baseband-based Node FeatureState=CXC4011345

After This Task

Let the CCTR be active for one week, for continued collection of troubleshooting
data.

36 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

8 Deactivate Mobility Control at Poor Coverage

If the feature is no longer needed, it can be deactivated following the usual

feature deactivation procedure. It must also be deactivated before the
activation of any conflicting feature.

Prerequisites
Continuous Cell Trace Recording (CCTR) is activated since at least one week. This
ensures there is troubleshooting data available if something goes wrong.

Steps

1. Set the attribute featureState to DEACTIVATED in the applicable MO

instance, depending on node type:

Node Type License Control MO

DU Radio Node OptionalFeatureLicense=MobCtrlAtPoorCov
Baseband-based FeatureState=CXC4011345

After This Task

Let the CCTR be active for one week, for continued collection of troubleshooting
data.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 37

 Mobility Control at Poor Coverage

9 Engineering Guidelines for Mobility Control at

Poor Coverage

The mobCtrlAtPoorCovActive attribute must be set to TRUE for each cell where
the feature must be active.

To make the feature work best, the following must be considered:

— The search threshold must be tuned.

— The critical threshold must be tuned.

— The measurements for finding alternative frequencies, such as: Event A5,
inter-frequency A3 for LTE frequencies, and Event B2 for other RATs.

General information about configuration activities can be found in Radio

Network (DU Radio Node).

38 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 Feature Change History

Appendix A: Feature Change History

This section lists changes that affected this feature and the impact it had on
the network.

Appendix A.a: 19.Q1: Improved Quantity Check for Handover Decision

The feature enhancement allows different handover decisions to be made
depending on what measurement report the eNodeB receives.

Feature Name: Mobility Control at Poor Coverage

Feature Identity: FAJ 121 3013
Value Package Name: LTE Base Package
Value Package Identity: FAJ 801 0400
Node Type: Baseband Radio Node
Access Type: LTE

The feature enhancement allows making handover decisions based on quantities

between RSRP and RSRQ, or RSCP and EcN0. When the eNodeB receives an A3
measurement report, it makes the decision based on RSRP or RSRQ. When it
receives a B1 or B2 measurement report, it makes the decision based on RSCP
and EcN0 instead. The feature enhancement also allows for the requesting of the
second quantity in report configuration for B1 (only for CSFB) and B2
measurements.

For A3 intra- and inter-frequency measurements, either RSRP or RSRQ can be

checked as second quantity.

Non-triggering quantity evaluation can be enabled separately for each

measurement type.

Capacity and Performance

The ratio of the number of successful handovers and the total number of
handover attempts are increased for the following:
— Mobility Success Rate

— Handover Success Rate

— Cell Handover Success Rate

— Handover Execution Success Rate

— Cell Handover Execution Success Rate

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 39

 Mobility Control at Poor Coverage

— UTRAN Handover Success Rate

— UTRAN SRVCC Handover Success Rate

Operation
The feature enhancement introduces the following new MO attributes:
— ReportConfigB1Utra.reportQuantityB1Utra

— ReportConfigB2Utra.reportQuantityB2Utra

— UeMeasControl.filterCoefficientRscpUtra

— UeMeasControl.filterCoefficientEcnoUtra

— UeMeasControl.bothB1RscpEcnoCheck

— UeMeasControl.bothB2RscpEcnoCheck

— UeMeasControl.bothInterA3RsrpRsrqCheck

— UeMeasControl.bothIntraA3RsrpRsrqCheck

Interfaces
No impact.

Hardware
No special hardware requirements.

Other Network Elements

This enhancement requires ENM version 18.17 or later to be used.

Appendix A.b: 19.Q1: Availability Setting for Release with Redirect in Search and Critical
Zone
The feature enhancement allows the disabling of RwR in search and critical
zone for Mobility Control at Poor Coverage.

Feature Name: Mobility Control at Poor Coverage

Feature Identity: FAJ 121 3013
Value Package Name: LTE Base Package
Value Package Identity: FAJ 801 0400
Node Type: Baseband Radio Node
Access Type: LTE

40 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28

 Feature Change History

The feature enhancement introduces configuration for eNodeB, which allows the
enabling or disabling of RwR when mobility action is set to HANDOVER.

Capacity and Performance

If retransmitting at higher power, there can be an impact on "E-RAB
Retainability". During this case, any of the following can be observed:
— Increase in interference

— Increase in network traffic

— Increase in the packet loss rate

Operation
The feature enhancement introduces the following new counters:
— pmErabRelAbnormalMmeActCritCov

— pmUeCtxtRelAbnormalEnbCritCov

— pmErabRelAbnormalEnbCritCov

— pmErabRelAbnormalEnbActCritCov

— pmUeCtxtRelAbnormalEnbActCritCov

— pmErabRelAbnormalMmeCritCov

— pmUeCtxtRelAbnormalMmeCritCov

— pmUeCtxtRelAbnormalMmeActCritCov

— pmCovCriticalZoneSum

— pmCovCriticalZoneSamp

The feature enhancement introduces the following new configuration

parameters:
— EUtranCellTDD.rwrSearchZoneAllowed

— EUtranCellFDD.rwrSearchZoneAllowed

— EUtranCellTDD.rwrCriticalZoneAllowed

— EUtranCellFDD.rwrCriticalZoneAllowed

Note: Parameters EUtranCellFDD.rwrCriticalZoneAllowed or

EUtranCellTDD.rwrCriticalZoneAllowed are only allowed to be
changed by Ericsson personnel.

40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28 41

 Mobility Control at Poor Coverage

Interfaces
No impact.

Hardware
No special hardware requirements.

Other Network Elements

No impact.

42 40/221 04-LZA 701 6014/1 Uen BF | 2020-07-28