Mobility Control at Poor Coverage

Feature Description

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

Copyright

© Ericsson AB 2016, 2017. 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 G2 | 2017-09-18

 Contents

Contents

1 Mobility Control at Poor Coverage Overview 1

1.1 Additional Information 2

2 Feature Operation 3
2.1 Network Requirements 3
2.2 Feature Operation Sequence Diagram 4
2.3 Measurement Configuration 16
2.4 Level Based Search Zone Transitions 19

3 Parameters 22
3.1 Feature Configuration Parameters 22
3.2 Affected Parameters 25
3.3 Parameters Affecting the Feature 25

4 Network Impact 26
4.1 Capacity 26
4.2 Coverage 26
4.3 Mobility 26

5 Associated Features and Affected Functions 27

5.1 Prerequisite Features 27
5.2 Affected Features 27
5.3 Related Features 28
5.4 Affected System Functions 28

6 Performance 29
6.1 Key Performance Indicators 29
6.2 Counters 29
6.3 PM Events 30

7 Feature Activation and Deactivation 32

7.1 Activate Mobility Control at Poor Coverage 32
7.2 Deactivate Mobility Control at Poor Coverage 33

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

Mobility Control at Poor Coverage

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Mobility Control at Poor Coverage Overview

1 Mobility Control at Poor Coverage

Overview

Identity: FAJ 121 3013

Licensing: Licensed feature. One license is
required for each node.
Introduced in: DU: L13B
Baseband: L15B
Replaces: N/A
Belongs to: N/A

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.

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 1

 Mobility Control at Poor Coverage

1.1 Additional Information

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

• 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 G2 | 2017-09-18

 Feature Operation

2 Feature Operation

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

2.1 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.

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. See Measurement Configuration on page 16.

• 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:
ueMeasurementsActiveIF , ueMeasurementsActiveUTRAN ,
ueMeasurementsActiveGERAN , and
ueMeasurementsActiveCDMA2000 .

Note: These parameters replace parameter ueMeasurementsActive

which is used in the Session Continuity features.

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 3

 Mobility Control at Poor Coverage

Note: The Event A3 measurement that is optionally configured in the

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

2.2 Feature Operation Sequence Diagram

The Coverage-Triggered Session Continuity features, see Table 5, provide a
basic process followed by the eNodeB to determine where to transfer a UE in
poor coverage. This process is enhanced by the Mobility Control at Poor
Coverage feature, and is described in this section.

4 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Feature Operation

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)

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 5

 Mobility Control at Poor Coverage

”Target Good ”Critical

12 Enough” Coverage” 16
reported reported

13 ANR: Determine possible

Unknown Cell and target 17
First Time? yes frequencies

no

14 18
Blind
Initiate Handover Handover? Handover? Initiate Handover
yes yes

no no

15 19
UE has bearer UE has bearer
yes with with yes
QCI 1? QCI 1?

no no

Initiate release with Initiate release with

redirect to the redirect to one of the
reported frequency frequencies
L0000877C

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.

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 (TDD only) for the current cell according to the
following criteria:
• The corresponding Coverage-Triggered Session Continuity feature is
active and enabled.

6 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Feature Operation

• 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.

• 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 Measurement Configuration on page
16 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 19), 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

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 7

 Mobility Control at Poor Coverage

– 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.

8 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Feature Operation

If the value of attribute inhibitB2RsrqConfig = TRUE , the

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

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 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 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 The Outer Search Threshold on
page 19.

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

high 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

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 9

 Mobility Control at Poor Coverage

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 .

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 a inner/outer search zone (see The

Outer Search Threshold on page 19) for the reported trigger quantity,
and 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.

10 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Feature Operation

• 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.

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 19), 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 19), 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

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 11

 Mobility Control at Poor Coverage

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.

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.

12 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Feature Operation

• 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.

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.

Also if bothA5RsrpRsrqCheck is set to TRUE, the eNodeB uses an

extended check of A5 “Target Good Enough” measurements before
handover according to the following:
• RSRP measured value must be higher than either of the following
calculated expressions:

– max [a5Threshold2RsrpOffset(qciPr ofilei)]+hysteresisA5–cellIndivOffset_C–qOffsetFreq_F

a5Threshold2Rsrp+ieUE_QCISet

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 13

 Mobility Control at Poor Coverage

max [a5Threshold2RsrpOffset(qciPr ofile )]

The term ieUE_QCISet i
is included, only if
the feature Service Triggered Mobility is OPERABLE and the
feature Multi-Layer Service-Triggered Mobility is INOPERABLE.
a5Threshold2Rsrp + a5Thr2RsrpFreqOffset + max [a5Thr2RsrpFreqQciOffset(qciProfilei)] +hysteresisA5 –
cellIndivOffset_C – qOffsetFreq_F ieUE_QCISet

The sum
a5Thr2RsrpFreqOffset + max [a5Thr2RsrpFreqQciOffset(qciProfile,)]
ieUE_QCISet

is included, only if the feature Multi-Layer Service-Triggered

Mobility is OPERABLE.

• RSRQ measured value must be higher than either of the following

calculated expressions:

– max [a5Threshold2RsrqOffset(qciPr ofilei)]+hysteresisA5–cellIndivOffset_C–qOffsetFreq_F

a5Threshold2Rsrq+ieUE_QCISet

max [a5Threshold2RsrqOffset(qciPr ofile )]

The term ieUE_QCISet i
is included, only if
the feature Service Triggered Mobility is OPERABLE and the
feature Multi-Layer Service-Triggered Mobility is INOPERABLE.
a5Threshold2Rsrq+ a5Thr2RsrqFreqOffset + max [a5Thr2RsrpFreqQciOffset(qciProfile,)] +hysteresisA5 – cellIndivOffset_C
– – qOffsetFreq_F
ieUE_QCISet

The sum
a5Thr2RsrqFreqOffset + max [a5Thr2RsrpFreqQciOffset(qciProfile,)]
ieUE_QCISet

is included, only if the feature Multi-Layer Service-Triggered

Mobility is OPERABLE.

See settings within this feature in Radio Network and related handover
features in Table 6.

15. 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.

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

14 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Feature Operation

17. 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.

18. 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 17.
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

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 15

 Mobility Control at Poor Coverage

• 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.

19. 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 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 17.

2.3 Measurement Configuration

This section describes the measurement configurations related to this feature.

This feature introduces a concept of a search zone in the cell where the UE is
approaching poor coverage in the serving cell, and starts searching for
alternative frequencies to find one where the UE can be transferred. The
search zone follows the edge of the cell and is detected by Event A2
measurements. This is illustrated in Figure 3. It is also possible to split the
search zone into an inner and an outer search zone, see Figure 4, where the
UE only searches for frequencies with high priority in the inner search zone.

16 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Feature Operation

Critical Coverage
Threshold

Search zone

Good Coverage

Event A2 Search

Event A1 Good
Coverage

Search Threshold
Event A2 Critical Coverage

L0000721A

Figure 3 Cell Search Zone Defined by Search Thresholds.

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 17

 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.

2.3.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 attribute inhibitA2SearchConfig 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. See Step 6 in Section 2.2 and Step 10 in Section 2.2 for more
details on when these are configured.

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

These measurements replace the Poor Coverage measurements introduced

by the Session Continuity features.

The report configurations for these measurements are also affected by

features Service Triggered Mobility and Multi-Layer Service-Triggered Mobility.

18 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Feature Operation

2.3.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 attributes a2OuterSearchThrRsrpOffset and
a2OuterSearchThrRsrqOffset 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 Section 2.2.

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 MO attribute lowPrioMeasThresh . In other cases a standard
search zone is used.

2.3.3 The Critical Threshold

To detect that the UE has encountered critical coverage, Event A2 Critical
Coverage measurements are configured in the UE when it enters the search
zone, see The Search Threshold on page 18, or outer search zone, see The
Outer Search Threshold on page 19, for the reported triggering quantity
(RSRP or RSRQ). See Step 6 in Section 2.2 and Step 10 in Section 2.2 for
more details on when these are configured in the UE. The report configuration
for these are all based on parameters in the MO ReportConfigSearch , see
Table 2.

These measurements replace the Poor Coverage measurements introduced

by the Session Continuity features.

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

2.4 Level Based Search Zone Transitions

When the UE enters the search zone and a measurement report is received in
Step 6 in Section 2.2, the eNodeB configures a new measurement to 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

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 19

 Mobility Control at Poor Coverage

UeMeasControl::checkA2SearchLevel to FALSE, which makes the

eNodeB ignore the reported values for RSRP and RSRQ.

2.4.1 Using One Search Zone

The eNodeB is configured to not use an inner and outer search zone (see The
Outer Search Threshold on page 19). 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 Section 2.2, 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, see Step 18 in Section 2.2.

• 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, see Step
19 in Section 2.2.

• 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 Section 2.2 and onwards.

2.4.2 Using an Inner/Outer Search Zone

The eNodeB is configured to use an inner and outer search zone (see The
Outer Search Threshold on page 19)

There are several possible cases:

• 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 Coverage and Event A2 Critical Coverage are also configured. See
Step 6 in Section 2.2 for more details.

20 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Feature Operation

• 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. See Using One Search Zone on page 20.

• 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. See Using One Search Zone on page 20. 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. So, only Event A5/A3/B2
measurements for low priority frequencies are configured in the UE in this
case. Also, the Event A1 Good coverage measurement is already
configured in the UE, but the Event A2 outer search measurement is
removed from the UE.

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 21

 Mobility Control at Poor Coverage

3 Parameters

3.1 Feature Configuration Parameters

Table 1 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 1 Search Threshold Parameters

Parameter
a1a2SearchThresholdRsrp
a1a2SearchThresholdRsrq
hysteresisA1A2SearchRsrp
hysteresisA1A2SearchRsrq
hysteresisA2OuterSearchRsrp
hysteresisA2OuterSearchRsrq
searchEffortTime
timeToTriggerA1Search
timeToTriggerA1SearchRsrq
timeToTriggerA2Search
timeToTriggerA2SearchRsrq
timeToTriggerA2OutSearch
timeToTriggerA2OutSearchRsr
q with trigger quantity RSRQ. The value -1 means that this attribute
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.
The 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
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.

22 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18


Table 2 Critical Threshold Parameters
Parameter
a2CriticalThresholdRsrp
a2CriticalThresholdRsrq
hysteresisA2CriticalRsrp
hysteresisA2CriticalRsrq
timeToTriggerA2Critical
timeToTriggerA2CriticalRsrq
a2CriticalThrQci1RsrpOffset
a2CriticalThrQci1RsrqOffset
Table 3 UE Measurement Active Parameters
Parameter
ueMeasurementsActiveIF
ueMeasurementsActiveUTRAN
ueMeasurementsActiveGERAN
ueMeasurementsActiveCDMA200
0 purposes when Mobility Control at Poor Coverage feature is
Table 4 Feature-Specific Parameters
Parameter
mobCtrlAtPoorCovActive
inhibitA2SearchConfig
bothA5RsrpRsrqCheck
40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18
Parameters
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 on cell level for threshold
a2CriticalThresholdRsrp , RSRP threshold value for events
A2Critical.
QCI1 offset 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
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.
23
 Mobility Control at Poor Coverage

Parameter Description
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 never used by the feature Coverage-
Triggered Inter-Frequency Session Continuity.
ReportConfigB2Utra.timeToTriggerB2Rsrq 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.
ReportConfigB2Utra.hysteresisB2RsrqOff Offset to obtain the hysteresis for B2 measurement
set 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.
ReportConfigB2Geran.timeToTriggerB2Rsr Time-to-trigger value for event B2 with trigger
q 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.
ReportConfigB2Geran.hysteresisB2RsrqOf Offset to obtain the hysteresis for B2 measurement
fset for trigger quantity RSRQ. hysteresisB2Rsrq =
hysteresisB2 + hysteresisB2RsrqOffset.

24 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Parameters

Parameter Description
Note: This attribute is never used by the feature
Coverage-Triggered GERAN Session Continuity.
ReportConfigB2Cdma2000.timeToTriggerB2 Time-to-trigger value for event B2 with trigger
Rsrq 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.
ReportConfigB2Cdma2000.hysteresisB2Rsr Offset to obtain the hysteresis for B2 measurement
qOffset for trigger quantity RSRQ. hysteresisB2Rsrq =
hysteresisB2 + hysteresisB2RsrqOffset.
Note: This attribute is never used by the feature
Coverage-Triggered CDMA-eHRPD Session
Continuity.
checkA2SearchLevel 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.

3.2 Affected Parameters

The implementation of this feature affects no parameters.

3.3 Parameters Affecting the Feature

The parameters of the Coverage-Triggered Session Continuity feature still
apply, especially the A3 tables, A5 tables and B2 tables, when the
Mobility Control at Poor Coverage feature is enabled, with the following
exceptions:

• 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, since these measurements are replaced in this feature.
However, parameters filterCoefficientEUtraRsrp ,
filterCoefficientEUtraRsrq , and sMeasure still apply.

• Parameter ueMeasurementsActive is not used, and is replaced by the

new parameters shown in Table 3.

• Parameters triggerQuantityA3, triggerQuantityA5, and

triggerQuantityB2 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. These attributes are described in Table 4.

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 25

 Mobility Control at Poor Coverage

4 Network Impact

This section describes how the Mobility Control at Poor Coverage feature
affects the network functions and capabilities.

4.1 Capacity
This section provides information on the impact of the feature on network
capacity.

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.

4.2 Coverage
This section provides information on the impact of the Mobility Control at Poor
Coverage feature on network coverage.

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.

4.3 Mobility
This section provides information on the impact of the feature on mobility.

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 G2 | 2017-09-18

 Associated Features and Affected Functions

5 Associated Features and Affected

Functions

5.1 Prerequisite Features

Table 5 lists prerequisite features to the Mobility Control at Poor Coverage
feature. At least one of these must be active prior to introducing the Mobility
Control at Poor Coverage feature.

Table 5 Prerequisite Features

Feature Description
Coverage-Triggered Inter-Frequency Feature handling redirection to other LTE frequencies.
Session Continuity
Coverage-Triggered WCDMA Session Feature handling redirection to WCDMA.
Continuity
Coverage-Triggered TD-SCDMA TDD only: Feature handling redirection to TD-SCDMA.
Session Continuity
Coverage-Triggered GERAN Session Feature handling redirection to GERAN.
Continuity
Coverage-Triggered CDMA-eHRPD Feature handling redirection to CDMA2000.
Session Continuity

5.2 Affected Features

This feature affects the following RAN features:

• 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

• Coverage-Triggered Inter-Frequency Handover

• Coverage-Triggered WCDMA IRAT Handover

• Service Triggered Mobility

• Multi-Layer Service-Triggered Mobility

• SRVCC Handover to UTRAN

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 27

 Mobility Control at Poor Coverage
• Automated Neighbor Relations
5.3 Related Features
Table 6 lists features that are related to the Mobility Control at Poor Coverage
feature.
Table 6 Related Features
Feature
Automated Neighbor Relations
Coverage-Triggered Inter-Frequency
Handover
Coverage-Triggered WCDMA IRAT
Handover
SRVCC Handover to UTRAN
Subscriber Triggered Mobility
Shared LTE RAN
Redirect with System Information
Service Triggered Mobility
Multi-Layer Service-Triggered Mobility
Intra-LTE Inter-Mode Handover
Uplink-Triggered Inter-Frequency
Mobility
5.4 Affected System Functions
This feature affects no system functions.
28
Description
The behavior of ANR in the search zone is modified.
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.
Feature providing the possibility to initiate a handover to a
WCDMA cell when the UE reports poor coverage in the current
cell.
Feature providing the possibility to initiate an SRVCC handover
to a WCDMA cell when there is an active voice bearer.
Feature providing an alternative way to prioritize frequencies,
based on Subscriber Profile ID for RAT/Frequency priority
(SPID).
Feature allowing several operators to share a common LTE
RAN.
Feature providing the possibility to include system information
with the redirect frequency in the release message to the UE.
Feature allowing definition of QCI-based offsets for the
thresholds for Event A1, Event A2, Event A5, and Event B2.
Feature allowing definition of cell-specific QCI-based offsets for
the thresholds for Event A1, Event A2, Event A5, and Event B2.
Feature allowing handover between FDD and TDD cells.
Feature adding uplink channel quality as a mobility triggering
quantity.
40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18
 Performance

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

– pmCriticalBorderEvalReport

– pmBadCovSearchEvalReport

– pmBadCovSearchEvalReportRsrp

– pmCriticalBorderEvalReportRsrp

– pmGoodCovSearchEvalReport

– pmGoodCovSearchEvalReportRsrp

– pmBadCovOutSearchEvalReport

– pmBadCovOutSearchEvalReportRsrp

– pmA3InterFBestCellEvalReport

– pmA3InterFBestCellEvalReportRsrp

– pmA5BestCellEvalReport

– pmA5BestCellEvalReportRsrp

– pmB2BestCellEvalReport

– pmB2BestCellEvalReportRsrp

– pmCellHoExeAttLteInterFUeMeas

– pmCellHoExeAttLteInterFUeMeasRsrp

– pmCellHoExeSuccLteInterFUeMeas

– pmCellHoExeSuccLteInterFUeMeasRsrp

40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18 29

 Mobility Control at Poor Coverage

– pmUeCtxtRelSCEUtraBestCellRsrp

– pmUeCtxtRelSCEUtraBestCellRsrq

– pmUeCtxtRelSCEUtraA2Rsrp

– pmUeCtxtRelSCEUtraA2Rsrq

– pmUeCtxtRelSCUtranB2Rsrp

– pmUeCtxtRelSCUtranB2Rsrq

– pmUeCtxtRelSCUtranA2Rsrp

– pmUeCtxtRelSCUtranA2Rsrq

– pmUeCtxtRelSCGsmB2Rsrp

– pmUeCtxtRelSCGsmB2Rsrq

– pmUeCtxtRelSCGsmA2Rsrp

– pmUeCtxtRelSCGsmA2Rsrq

– pmUeCtxtRelSCCdmaB2Rsrp

– pmUeCtxtRelSCCdmaB2Rsrq

– pmUeCtxtRelSCCdmaA2Rsrp

– pmUeCtxtRelSCCdmaA2Rsrq

• 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 7 lists the PM events associated with the Mobility Control at Poor
Coverage feature.

Table 7 PM Events
Event Description
INTERNAL_PROC_UE_CTXT_RELEASE Generated for the UE Context Release procedure to
release a UE Context. Contains information about the
releasing node, cause, and bearer information.
INTERNAL_EVENT_UE_MOBILITY_EVAL Mobility trigger and decision information has occurred.

30 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18


Event
INTERNAL_EVENT_MEAS_CONFIG_A1
INTERNAL_EVENT_MEAS_CONFIG_A2
INTERNAL_EVENT_MEAS_CONFIG_A3
INTERNAL_EVENT_MEAS_CONFIG_A5
INTERNAL_EVENT_MEAS_CONFIG_B2_CDM
A2000
INTERNAL_EVENT_MEAS_CONFIG_B2_GER
AN
INTERNAL_EVENT_MEAS_CONFIG_B2_UTR
A Reconfiguration to report measurements on UTRA with
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 G2 | 2017-09-18
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 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.
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
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.
31
 Mobility Control at Poor Coverage

7 Feature Activation and Deactivation

Attribute mobCtrlAtPoorCovActive must be set to TRUE for each cell

where the feature must be active.

For more information to make the feature work well, see the following
references:

• The search threshold must be tuned, see The Search Threshold on page
18

• The critical threshold must be tuned, see The Critical Threshold on page
19

• The measurements for finding alternative frequencies, such as: Event A5,
inter-frequency A3 for LTE frequencies, and Event B2 for other RATs. See
the Coverage-Triggered Session Continuity features in Table 5.

General information about configuration activities can be found in Radio

Network (DU Radio Node).

7.1 Activate Mobility Control at Poor Coverage

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 attribute featureState to ACTIVATED in the applicable MO

instance, depending on node type:

Node Type License Control MO

DU Radio Node OptionalFeatureLicense=MobCtrlAtPoo
rCov
Baseband-based Node FeatureState=CXC4011345

32 40/221 04-LZA 701 6014/1 Uen G2 | 2017-09-18

 Feature Activation and Deactivation

After This Task

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

7.2 Deactivate Mobility Control at Poor Coverage

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=MobCtrlAtPoo
rCov
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 G2 | 2017-09-18 33