Multi-Layer Service-Triggered Mobility

FEATURE DESCRIPTION

144/221 04-LZA 701 6014 Uen A

Copyright

© Ericsson AB 2015. 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.

144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Contents

Contents

1 Introduction 1
1.1 Basic Characteristics 1
1.2 Benefits 2
1.3 Additional Information 3

2 Feature Operation 5
2.1 Network Requirements 5
2.2 Feature Operation Sequence Diagram 5
2.3 Measurement Configuration 5

3 Parameters 13
3.1 Feature Configuration Parameters 13
3.2 Affected Parameters 16

4 Network Impact 19
4.1 Relations Between Thresholds 19

5 Associated Features and Affected Functions 21

5.1 Prerequisite Features 21
5.2 Affected Features 21
5.3 Affected System Functions 21

6 Performance 23
6.1 KPIs 23
6.2 Counters 23
6.3 Events 24

7 O&M Information 27
7.1 Feature Activation and Deactivation 27

144/221 04-LZA 701 6014 Uen A | 2015-06-23

Multi-Layer Service-Triggered Mobility

144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Introduction

1 Introduction

This document describes the Multi-Layer Service-Triggered Mobility feature

and its main benefits and impacts in the LTE RAN.

The purpose of this feature is to provide the possibility to configure different

threshold offset values for different cells and QCIs, to optimize the mobility for
both different services and frequencies. The configured feature parameter
values are applied when a UE enters a searching zone or returns into a good
coverage zone. The feature also supports different threshold offset values for
different frequency relations and QCIs, and different offset values for good
enough other frequencies or RATs.

The possibility to configure different threshold values makes it possible to tune

the feature in different ways for different frequencies and types of services, for
example more or less drop-sensitive. This makes it possible to improve the
capacity or mobility for the preferred frequencies.

1.1 Basic Characteristics

This section describes the basic characteristics of the feature.

Feature name: Multi-Layer Service-Triggered Mobility

Product identity:
DU-based node, see Feature Overview.

Baseband-based node, see Licensed Feature Overview

Replaces: N/A

Dependencies

This feature requires at least one of the following RAN features to be active:

• 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

This feature requires the following RAN features to be active:

• Mobility Control at Poor Coverage

144/221 04-LZA 701 6014 Uen A | 2015-06-23 1

 Multi-Layer Service-Triggered Mobility

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

• TDD only: Coverage-Triggered TD-SCDMA IRAT Handover

• Mobility Control at Poor Coverage

• Service Triggered Mobility

• Automated Mobility Optimization

• Service or Priority-Triggered Inter-Frequency Handover

The above listed features is affected by the Multi-Layer Service-Triggered

Mobility feature because of changes in the values of the measurement
thresholds sent to a UE, due to the threshold offsets introduced in this feature.

1.2 Benefits
This section describes the benefits of this feature.

The main benefit of this feature is the possibility to tune different services
and frequency relations with different threshold offset values for the following
scenarios:

• Good coverage

• Bad coverage

• Good enough other frequency or RAT

By using different thresholds, which are optimized for specific services and
frequencies, it is possible to improve the capacity or mobility for the preferred
frequencies.

2 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Introduction

1.3 Additional Information

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

• 3GPP TS36.331 Radio Resource Control (RRC); Protocol Specification

144/221 04-LZA 701 6014 Uen A | 2015-06-23 3

 Multi-Layer Service-Triggered Mobility

4 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Feature Operation

2 Feature Operation

This section describes the Multi-Layer Service-Triggered Mobility feature in

more detail, including network configuration requirements and operation flows.

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. See Section 7.1 on page 27 for more details.

The following must also be fulfilled at feature activation:

• The Mobility Control at Poor Coverage feature must be activated as a

prerequisite feature, and the attribute mobCtrlAtPoorCovActive must
be set to TRUE for each cell where the legacy feature should be active.

• To start measurements in the UE, it is required that at least one of the

following features is activated:

0 Coverage-Triggered WCDMA Session Continuity

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

0 Coverage-Triggered CDMA-eHRPD Session Continuity

0 Coverage-Triggered GERAN Session Continuity

0 Coverage-Triggered Inter-Frequency Session Continuity

2.2 Feature Operation Sequence Diagram

There is no flow as such for this feature. This feature crosscuts the flows
of some other features as an enhancement of the legacy feature, Service
Triggered Mobility.

This feature overrides the Service Triggered Mobility feature when both features
are activated. For compatibility, the Service Triggered Mobility feature – QCI
specific offsets per eNodeB level - is still supported when the legacy feature is
activated, but this feature is not activated.

2.3 Measurement Configuration

This section describes the measurement configurations related to this feature.

This section describes the main process steps for the feature flow.

144/221 04-LZA 701 6014 Uen A | 2015-06-23 5

 Multi-Layer Service-Triggered Mobility

2.3.1 A5 and B2 thresholds per target frequency relation

This feature can enable the serving cell to have different A5-T1/B2-T1 threshold
and different A5-T2/B2-T2 threshold per target frequency relation as shown,
for example, in Figure 1, by introducing new threshold offset parameters for
the event A5 and event B2 per target frequency relation. It can be noted
that A1A2Search threshold was introduced in the Mobility Control at Poor
Coverage feature.

Serving Cell:
EUTRAN F1
A1A2SearchThr
A5-Thr1-F2
B2-Thr1-F3

Neighbouring Cell:
EUTRAN F2

A5-Thr2-F2

Neighbouring Cell:
UTRAN / CDMA2000 / CDMA20001XRTT / GSM F3

B2-Thr2-F3

L0001003B

Figure 1 A5 and B2 Threshold per Target Frequency Relation

By configuring thresholds per target frequency relation, as shown in Figure 1,

this feature can differentiate bad coverage behavior on target frequency.

2.3.2 A1A2Search, A5 and B2 thresholds for different QCI

This feature makes it possible that in the serving cell, different QCI can have
different good/poor coverage threshold (A1/A2), and can have different

6 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Feature Operation

A5-T1/B2-T1 threshold and different A5-T2/B2-T2 threshold per target

frequency relation. UE’s measurement threshold value is based on its QCI
constellation. Figure 2 is an example on QCI-A.

Serving Cell:
EUTRAN F1
A1A2SearchThr-QCI-A
A5-Thr1-F2-QCI-A
B2-Thr1-F3-QCI-A

Neighbouring Cell:
EUTRAN F2

A5-Thr2-F2-QCI-A

Neighbouring Cell:
UTRAN / CDMA2000 / CDMA20001XRTT / GSM F3

B2-Thr2-F3-QCI-A

L0001006B

Figure 2 A1A2Search, A5 and B2 Thresholds for QCI-A

There is a possibility to get higher retainability for voice or increase capacity

by tuning different services with different A1A2Search threshold, and different
A5 or B2 thresholds.

2.3.3 Mobility Threshold offset for A1Search and A2Search

This feature can set event A1Search and A2Search threshold with different
threshold offset on cell level based on QCI profiles as shown in Figure 3.

144/221 04-LZA 701 6014 Uen A | 2015-06-23 7

 Multi-Layer Service-Triggered Mobility

MOC UeMeasControl

MOC ReportConfigSearch

-a1a2SearchThresholdRsrp
-a1a2SearchThresholdRsrq
-qciA1A2ThrOffsets[0..19]

« struct » ReportConfigParamsQciOffset

-qciProfileRef
-a1a2ThrRsrpQciOffset
-a1a2ThrRsrpQciOffset

L0001007B

Figure 3 Mobility Threshold Offset for A1A2Search

UE’s A1A2Search threshold, when the Multi-Layer Service-Triggered Mobility

feature is activated, is calculated in accordance with the following:

A1A2SearchThresholdXQCI =
ReportConfigSearch.a1a2SearchThresholdX +
ReportConfigSearch. qciA1A2ThrOffsets<qci>
.a1a2ThrXQciOffset

A1A2SearchThresholdXUE =
ReportConfigSearch. a1a2SearchThresholdX +
n
i=1 max (ReportConfigSearch.qciA1A2ThrOffse
ts<profilei> .a1a2ThrXQciOffset)

The terms used in the calculation above are defined according to the following:

X Rsrp or Rsrq

a1a2ThrXQciOffset
A QCI specific threshold offset

8 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Feature Operation

A1A2SearchThresholdXUE
The threshold that is sent to the UE in the report
configuration IE after the maximum value of the
corresponding offset thresholds per profile was
computed.

If an operator does not want to tune different service with different QCI
specific threshold offset, the threshold offset parameter, in this example,
a1a2ThrXQciOffset in each QCI profile instance qciA1A2ThrOffsets,
can be set to 0 as default value.

The offset values must be checked whenever there is measurement

configuration in UE in procedure of: initial context setup, E-RAB setup, E-RAB
release, E-RAB modify, and incoming handover.

2.3.4 Mobility Threshold offset for A5 and B2

This feature can set event A5 and B2 threshold with different threshold offset
per frequency relation and per QCI as shown in Figure 4, an example showing
MOM relation for event A5 and event B2 for UTRA measurement.

144/221 04-LZA 701 6014 Uen A | 2015-06-23 9

 Multi-Layer Service-Triggered Mobility

MO Class: UtranFreqRelation MO Class EUtranFreqRelation

-b2Thr1RsrpUtraFreqOffset -a5Thr1RsrpFreqOffset
-b2Thr1RsrqUtraFreqOffset -a5Thr1RsrqFreqOffset
-b2Thr2EcNoUtraFreqOffset -a5Thr2RsrpFreqOffset
-b2Thr2RscpUtraFreqOffset -a5Thr2RsrqFreqOffset
-utranFreqToQciProfileRelation [0..19] -eutranFreqToQciProfileRelation [0..19]
EUtranCellFDD/TDD

UtranFreqToQciProfileRelation EUtranFreqToQciProfileRelation
-qciProfileRef -qciProfileRef
-b2Thr1RsrpUtraFreqQciOffset UeMeasControl -a5Thr1RsrpFreqQciOffset
-b2Thr1RsrqUtraFreqQciOffset -a5Thr1RsrqFreqQciOffset
-b2Thr2EcNoUtraFreqQciOffset -a5Thr2RsrpFreqQciOffset
-b2Thr2RscpUtraFreqQciOffset -a5Thr2RsrqFreqQciOffset

ReportConfigB2Utran ReportConfigA5

MOC: ReportConfigB2Utra MOC: ReportConfigA5

-b2Threshold1Rsrp -a5Threshold1Rsrp
-b2Threshold1Rsrq -a5Threshold1Rsrq
-b2Threshold2EcNoUtra -a5Threshold2Rsrp
-b2Threshold2RscpUtra -a5Threshold2Rsrq

L0001008C

Figure 4 Mobility Threshold Offset for A5 and B2

For example, UE’s event A5 threshold1, when the Multi-Layer Service-Triggered

Mobility feature is activated, is calculated in accordance with the following:

A5Threshold1XQCI =
ReportConfigA5.a5Threshold1X +
EUtranFreqRelation.a5Thr1XFreqOffset +
EUtranFreqRelation.eutranFreqToQciProfile
Relation<qci>.a5Thr1XFreqQciOffset

A5Threshold1XUE =
ReportConfigA5.a5Threshold1X +
EUtranFreqRelation.a5Thr1XFreqOffset + i=1n
max(EUtranFreqRelation.eutranFreqToQciPro
fileRelation<profilei>.a5Thr1XFreqQciOffset)

The terms used in the calculation above are defined according to the following:

10 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Feature Operation

X Rsrp or Rsrq

a5Thr1XFreqQciOffset
A QCI specific threshold offset in target frequency
relation.

profilei The QCI profile of bearer i of the UE; n is the number

of bearers of the UE.

A5Threshold1XUE
The threshold that is sent to the UE in the report
configuration IE after being computed in the eNodeB
as the sum of the base threshold a5Threshold1X
and frequency-relation specific threshold offset
a5Thr1XFreqOffset for the target frequency and the
maximum value of all the QCI specific threshold offsets
a5Thr1XFreqQciOffset for all the UE QCI profiles in
the target frequency relation.

A5-T2 can be computed with the similar calculation method as that of A5-T1.

For event B2 for UTRA, UTRA TDD, CDMA2000, CDMA2000 1XRTT, and
GERAN measurement, B2-T1 and B2-T2 follow the similar calculation method
as that of A5.

It can be noted that there is no QCI specific threshold offset for CDMA2000
1XRTT frequency relation because only voice service is supported on the
frequency so that QCI level differentiation is not needed.

If an operator does not want to tune different frequency relation with

different A5 or B2 frequency-relation specific threshold offset, the threshold
offset parameter, in this example, a5Thr1XFreqOffset in the MO class
EUtranFreqRelation, can be set to 0 as default value.

If an operator does not want to tune different frequency relation and

different service with different A5 or B2 threshold offsets, the threshold
offset parameters, in this example, a5Thr1XFreqOffset in MO class
EutranFreqRelation and a5Thr1XFreqQciOffset in each QCI profile
instance eutranFreqToQciProfileRelation, can be set to 0 as default
value.

The offset values must be checked whenever there is measurement

configuration in UE in procedure of: initial context setup, E-RAB setup, E-RAB
release, E-RAB modify, and incoming handover.

144/221 04-LZA 701 6014 Uen A | 2015-06-23 11

 Multi-Layer Service-Triggered Mobility

12 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Parameters

3 Parameters

This section describes configuration parameters for the Multi-Layer

Service-Triggered Mobility feature and parameters affected by activating the
feature.

3.1 Feature Configuration Parameters

Table 1 ,Table 2 and Table 3 describe the feature parameters.

Table 1 Feature Parameters, Part 1

Parameter
Search Threshold Parameters for event A1 and A2
qciA1A2ThrOffsets
qciProfileRef
a1a2ThrRsrpQciOffset
a1a2ThrRsrqQciOffset
Threshold Parameters for event A5
a5Thr1RsrpFreqOffset
a5Thr1RsrqFreqOffset
a5Thr2RsrpFreqOffset
a5Thr2RsrqFreqOffset
a5Thr1RsrpFreqQciOffset
a5Thr1RsrqFreqQciOffset
a5Thr2RsrpFreqQciOffset
Description
Parameters for adding QCI profile specific offsets to threshold
values for events A1Search and A2Search used for mobility
decisions. Applicable if Multi-Layer Service-Triggered Mobility is
active.
Refers to the QCI profile MO, QciProfilePredefined or
QciProfileOperatorDefined.
The QCI specific offset on cell level for the absolute threshold
a1a2ThresholdRsrp, RSRP threshold value for events A1Search
and A2Search, used for Multi-Layer Service-Triggered Mobility.
The QCI specific offset on cell level for the absolute threshold
a1a2ThresholdRsrq, RSRQ threshold value for events A1Search
and A2Search, used for Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
a5Threshold1Rsrp, RSRP threshold1 for event A5, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
a5Threshold1Rsrq, RSRQ threshold1 for event A5, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
a5Threshold2Rsrp, RSRP threshold2 for event A5, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
a5Threshold2Rsrq, RSRQ threshold2 for event A5, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation dependent and QCI specific offset for
the absolute threshold a5Threshold1Rsrp, used for Multi-Layer
Service-Triggered Mobility.
The frequency-relation dependent and QCI specific offset for
the absolute threshold a5Threshold1Rsrq, used for Multi-Layer
Service-Triggered Mobility.
The frequency-relation dependent and QCI specific offset for
the absolute threshold a5Threshold2Rsrp, used for Multi-Layer
Service-Triggered Mobility.

144/221 04-LZA 701 6014 Uen A | 2015-06-23 13

 Multi-Layer Service-Triggered Mobility
Parameter
a5Thr2RsrqFreqQciOffset
Threshold Parameters for event B2 for UTRA measurement
b2Thr1RsrpUtraFreqOffset
b2Thr1RsrqUtraFreqOffset
b2Thr2EcNoUtraFreqOffset
b2Thr2RscpUtraFreqOffset
b2Thr1RsrpUtraFreqQciOffset
b2Thr1RsrqUtraFreqQciOffset
b2Thr2EcNoUtraFreqQciOffset
b2Thr2RscpUtraFreqQciOffset
Table 2 Feature Parameters, Part 2
Parameter
Threshold Parameters for event B2 for UTRA TDD measurement
b2Thr1RsrpUtraFreqOffset
b2Thr1RsrqUtraFreqOffset
b2Thr2RscpUtraFreqOffset
qciB2ThrOffsets
b2Thr1RsrpUtraFreqQciOffset
b2Thr1RsrqUtraFreqQciOffset
14
Description
The frequency-relation dependent and QCI specific offset for
the absolute threshold a5Threshold2Rsrq, used for Multi-Layer
Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
b2Threshold1Rsrp, RSRP threshold1 for event B2, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
b2Threshold1Rsrq, RSRQ threshold1 for event B2, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
b2Threshold2EcNo, Ratio of energy for each modulation bit to
noise spectral density in the ThresholdUTRA for event B2, used
for Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
b2Threshold2Rscp, RSCP in the ThresholdUTRA for event B2,
used for Multi-Layer Service-Triggered Mobility.
The frequency-relation dependent and QCI specific offset for
the absolute threshold b2Threshold1Rsrp, used for Multi-Layer
Service-Triggered Mobility.
The frequency-relation dependent and QCI specific offset for
the absolute threshold b2Threshold1Rsrq, used for Multi-Layer
Service-Triggered Mobility.
The frequency-relation dependent and QCI specific offset for the
absolute threshold b2Threshold2EcNoUtra, used for Multi-Layer
Service-Triggered Mobility. Not applicable for UTRA TDD.
The frequency-relation dependent and QCI specific offset for the
absolute threshold b2Threshold2RscpUtra, used for Multi-Layer
Service-Triggered Mobility.
Description
The frequency-relation specific offset for the absolute threshold
b2Threshold1Rsrp, RSRP threshold1 for event B2, used for
Multi-Layer Service-Triggered Mobility
The frequency-relation specific offset for the absolute threshold
b2Threshold1Rsrq, RSRQ threshold1 for event B2, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
b2Threshold2Rscp, RSCP in the ThresholdUTRATDD for event
B2, used for Multi-Layer Service-Triggered Mobility.
Parameters for adding QCI profile and frequency relation specific
offsets to B2 threshold values used for mobility decisions.
Applicable if Multi-Layer Service-Triggered Mobility (MLSTM) is
active.
The frequency-relation dependent and QCI specific offset for
the absolute threshold b2Threshold1Rsrp, used for Multi-Layer
Service-Triggered Mobility.
The frequency-relation dependent and QCI specific offset for
the absolute threshold b2Threshold1Rsrq, used for Multi-Layer
Service-Triggered Mobility.
144/221 04-LZA 701 6014 Uen A | 2015-06-23

Parameter
b2Thr2EcNoUtraFreqQciOffset
b2Thr2RscpUtraFreqQciOffset
Threshold Parameters for event B2 for CDMA2000 measurement
b2Thr1RsrpCdma2000FreqOffs
et
b2Thr1RsrqCdma2000FreqOffs
et
b2Thr2Cdma2000FreqOffset
qciB2ThrOffsets
qciProfileRef
b2Thr1RsrpCdma2000FreqQciOf
fset
b2Thr1RsrqCdma2000FreqQciOf
fset
b2Thr2Cdma2000FreqQciOffset
Table 3 Feature Parameters, Part 3
Parameter
Threshold Parameters for event B2 for CDMA2000 1XRTT measurement
b2Thr1RsrpCdma20001xFreqOf
fset
b2Thr1RsrqCdma20001xFreqOf
fset
b2Thr2Cdma20001xFreqOffset
Threshold Parameters for event B2 for GERAN measurement
b2Thr1RsrpGeranFreqOffset
b2Thr1RsrqGeranFreqOffset
144/221 04-LZA 701 6014 Uen A | 2015-06-23
Parameters
Description
The frequency-relation dependent and QCI specific offset for the
absolute threshold b2Threshold2EcNoUtra, used for Multi-Layer
Service-Triggered Mobility. Not applicable for UTRA TDD
The frequency-relation dependent and QCI specific offset for the
absolute threshold b2Threshold2RscpUtra, used for Multi-Layer
Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
b2Threshold1Rsrp, RSRP threshold1 for event B2, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
b2Threshold1Rsrq, RSRQ threshold1 for event B2, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute
threshold b2Threshold2Cdma2000, Signal quality in the
thresholdCDMA2000 for event B2, used for Multi-Layer
Service-Triggered Mobility.
Parameters for adding QCI profile and frequency relation specific
offsets to B2 threshold values used for mobility decisions.
Applicable if Multi-Layer Service-Triggered Mobility (MLSTM) is
active.
Refers to the QCI profile MO, QciProfilePredefined or
QciProfileOperatorDefined
The frequency-relation dependent and QCI specific offset for
the absolute threshold b2Threshold1Rsrp, used for Multi-Layer
Service-Triggered Mobility.
The frequency-relation dependent and QCI specific offset for
the absolute threshold b2Threshold1Rsrq, used for Multi-Layer
Service-Triggered Mobility.
The frequency-relation dependent and QCI specific offset for the
absolute threshold b2Threshold2Cdma2000, used for Multi-Layer
Service-Triggered Mobility.
Description
The frequency-relation specific offset for the absolute threshold
b2Threshold1Rsrp, RSRP threshold1 for event B2, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute threshold
b2Threshold1Rsrq, RSRQ threshold1 for event B2, used for
Multi-Layer Service-Triggered Mobility.
The frequency-relation specific offset for the absolute
threshold b2Threshold2Cdma20001xRtt, Signal quality in
the thresholdCDMA2000 for event B2, used for Multi-Layer
Service-Triggered Mobility.
The frequency group relation specific offset for the absolute
threshold b2Threshold1Rsrp, RSRP threshold1 value for event
B2, used for Multi-Layer Service-Triggered Mobility.
The frequency group relation specific offset for the absolute
threshold b2Threshold1Rsrq, RSRQ threshold1 value for event
B2, used for Multi-Layer Service-Triggered Mobility.
15
 Multi-Layer Service-Triggered Mobility

Parameter Description
b2Thr2GeranFreqOffset The frequency group relation specific offset for the
absolute threshold b2Threshold2Geran, Signal quality in
the ThresholdGERAN for event B2, used for Multi-Layer
Service-Triggered Mobility.
qciB2ThrOffsets Parameters for adding QCI profile and frequency relation specific
offsets to B2 threshold values used for mobility decisions.
Applicable if Multi-Layer Service-Triggered Mobility (MLSTM) is
active.
qciProfileRef Refers to the QCI profile MO, QciProfilePredefined or
QciProfileOperatorDefined.
b2Thr1RsrpGeranFreqQciOffs The frequency group relation dependent and QCI specific offset
et for the absolute threshold b2Threshold1Rsrp, used for Multi-Layer
Service-Triggered Mobility.
b2Thr1RsrqGeranFreqQciOffs The frequency group relation dependent and QCI specific offset
et for the absolute threshold b2Threshold1Rsrq, used for Multi-Layer
Service-Triggered Mobility.
b2Thr2GeranFreqQciOffset The frequency group relation dependent and QCI specific offset for
the absolute threshold b2Threshold2Geran, used for Multi-Layer
Service-Triggered Mobility.

3.2 Affected Parameters

Table 4 describes the parameters affected by the feature and all the base
parameters affected when activating the Multi-Layer Service-Triggered Mobility
feature.

The implementation of this feature as such does not affect any parameters.
However, when the Multi-Layer Service-Triggered Mobility feature is activated,
the effect of an existing base parameter used for configuring measurement
threshold in the UE is changed by the corresponding offset parameter
introduced in this feature.

This can be exemplified by the Managed Object Model (MOM) parameter

a5Threshold1Rsrp. When the Multi-Layer Service-Triggered Mobility feature
is active, the value of this parameter will not change compared with the value
configured earlier in the MOM. However, when the UE is configured with the
Event A5 RSRP threshold1, the value of this threshold is computed as
described in Section 2.3.4 on page 9.

The same is valid for all other base thresholds where the value sent to the UE
is changed with the value of the offset parameters.

Note: A threshold offset parameter changes the effect of a base threshold

parameter only if the value of the offset is non-zero.

Table 4 Affected Parameters

Parameter Description
a1a2SearchThresholdRsrp The Reference Signal Received Power (RSRP) threshold value
for events A1Search and A2Search.

16 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Parameters

Parameter Description
a1a2SearchThresholdRsrq The Reference Signal Received Quality (RSRQ) threshold value
for events A1Search and A2Search.
a5Threshold1Rsrp The Reference Signal Received Power (RSRP) threshold1 value
for eventA5. Only used if triggerQuantityA5 is set to RSRP.
a5Threshold1Rsrq The Reference Signal Received Quality (RSRQ) threshold1 value
for eventA5. Only used if triggerQuantityA5 is set to RSRQ.
a5Threshold2Rsrp The Reference Signal Received Power (RSRP) threshold2 value
for eventA5. Only used if triggerQuantityA5 is set to RSRP.
a5Threshold2Rsrq The Reference Signal Received Quality (RSRQ) threshold2 value
for eventA5. Only used if triggerQuantityA5 is set to RSRQ.
b2Threshold1Rsrp The Reference Signal Received Power (RSRP) threshold1 value
for eventB2 UTRA measurement. Only used if triggerQuantityB2
is set to RSRP.
b2Threshold1Rsrq The Reference Signal Received Quality (RSRQ) in the
threshold1 value for eventB2 UTRA measurement. Only used if
triggerQuantityB2 is set to RSRQ.
b2Threshold2RscpUtra Received Signal Code Power in the ThresholdUTRA,
threshold2 value for eventB2 UTRA measurement. Used when
measQuantityUtraFDD is set to RSCP. Also present for UTRA
TDD.
b2Threshold2EcNoUtra Ratio of energy per modulation bit to noise spectral density
in the ThresholdUTRA, threshold2 value for eventB2 UTRA
measurement. Not applicable for UTRA TDD. Only used when
measQuantityUtraFDD is set to ECNO.
b2Threshold1Rsrp The Reference Signal Received Power (RSRP) threshold1
value for event B2 CDMA2000 measurement. Only used if
triggerQuantityB2 is set to RSRP.
b2Threshold1Rsrq The Reference Signal Received Quality (RSRQ) threshold1
value for event B2 CDMA2000 measurement. Only used if
triggerQuantityB2 is set to RSRQ.
b2Threshold2Cdma2000 The Signal Quality in the thresholdCDMA2000, threshold2 value
for event B2 measurement.
b2Threshold1Rsrp The Reference Signal Received Power (RSRP) threshold1 value
for eventB2 CDMA2000 1XRTT measurement. Only used if
triggerQuantityB2 is set to RSRP.
b2Threshold1Rsrq The Reference Signal Received Quality (RSRQ) threshold1 value
for eventB2 CDMA2000 1XRTT measurement. Only used if
triggerQuantityB2 is set to RSRQ.
b2Threshold2Cdma20001xRtt The Signal Quality in the thresholdCDMA2000 1XRTT, threshold2
value for eventB2.
b2Threshold1Rsrp The Reference Signal Received Power (RSRP) threshold1 value
for eventB2 GERAN measurement. Only used if triggerQuantityB2
is set to RSRP.
b2Threshold1Rsrq The Reference Signal Received Quality (RSRQ) threshold1 value
for eventB2 GERAN measurement. Only used if triggerQuantityB2
is set to RSRQ.
b2Threshold2Geran The Signal Quality in the ThresholdGERAN, threshold2 value for
eventB2 measurement.

144/221 04-LZA 701 6014 Uen A | 2015-06-23 17

 Multi-Layer Service-Triggered Mobility

18 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Network Impact

4 Network Impact

This section describes how the Multi-Layer Service-Triggered Mobility feature

impacts the network functions and capabilities.

4.1 Relations Between Thresholds

When configuring measurement threshold offsets, the relations between
the values of the different involved thresholds should be considered. These
relations are applicable already for the base threshold values and are to be
preserved when configuring different offsets introduced in this feature. The
following relation should exist between the thresholds for bad coverage or the
search zone (Event A2), serving cell better than (Event A1), and best cell on
other LTE frequency or Inter Radio Access Technology regarding the serving
cell (Events A5 and B2 respectively):

(1) a5Threshold1X + hysteresisA5 ≤ a2Thres

holdX + hysteresisA2 < a1ThresholdX +
hysteresisA1

(2) b2Threshold1X + hysteresisB2 ≤ a2Thres

holdX + hysteresisA2 < a1ThresholdX +
hysteresisA1

Since the Mobility Control at Poor Coverage feature is the prerequisite

feature of this feature, and in the Mobility Control at Poor Coverage feature,
a1ThresholdX and a2ThresholdX are replaced with the same threshold
a1a2SearchThresholdX, and this feature keeps the principle as in the
Mobility Control at Poor Coverage feature for A1 and A2, so the A1 and A2 part
in above inequality (1) and (2) could always be fulfilled.

The following only considers the threshold relation between A5/B2 and A2,
that is:

(3) a5Threshold1X + hysteresisA5 ≤

a2ThresholdX + hysteresisA2

(4) b2Threshold1X + hysteresisB2 ≤

a2ThresholdX + hysteresisA2

The threshold relation between A5/B2 and A2 as in inequality (3) and (4) should
also be fulfilled in this feature but with lower granularity as following:

On each LTE frequency relation

For each UE:

144/221 04-LZA 701 6014 Uen A | 2015-06-23 19

 Multi-Layer Service-Triggered Mobility

(5) a5Threshold1XUE + hysteresisA5 ≤

A1A2SearchThresholdXUE + hysteresisA2

For each QCI:

(6) a5Threshold1XQCI + hysteresisA5 ≤

A1A2SearchThresholdXQCI + hysteresisA2

On each IRAT frequency relation

For each UE:

(7) B2Threshold1XUE + hysteresisB2 ≤

A1A2SearchThresholdXUE + hysteresisA2

For each QCI:

(8) B2Threshold1XQCI + hysteresisB2 ≤

A1A2SearchThresholdXQCI + hysteresisA2

20 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Associated Features and Affected Functions

5 Associated Features and Affected

Functions

This section describes how the Multi-Layer Service-Triggered Mobility feature

affects other features and functions.

5.1 Prerequisite Features

Table 5 lists prerequisite features to the Multi-Layer Service-Triggered Mobility
feature, that is, they must be active prior to introducing the Multi-Layer
Service-Triggered Mobility feature.

Table 5 Prerequisite Features

Feature Description
Mobility Control at Poor Coverage Feature providing more options for how to control where UEs
are transferred in poor coverage.

5.2 Affected Features

Table 6 lists features that are affected by the Multi-Layer Service-Triggered
Mobility feature.

Table 6 Affected Features

Feature
Automated Mobility Optimization
Service Triggered Mobility
Service or Priority-Triggered
Inter-Frequency Handover
Description
AMO related counters may be impacted if A5-T2 is changed
by the offsets introduced in the Multi-Layer Service-Triggered
Mobility feature.
The Multi-Layer Service-Triggered Mobility feature prevails over
the Service Triggered Mobility feature when both features are
activated.
If the Multi-Layer Service-Triggered Mobility feature uses RSRP
as its A5-T2 measurement quantity, the offsets introduced in
this feature is applied for computing measurement thresholds
for new measurements to be setup in the Service or Priority
Inter-frequency Handover feature when both features are
activated.

5.3 Affected System Functions

This feature affects the mobility patterns of UE due to changes in the settings of
measurement thresholds through tuning of threshold offsets.

Threshold offsets must be carefully configured to achieve the desired UE

differentiation given the services that UE use.

144/221 04-LZA 701 6014 Uen A | 2015-06-23 21

 Multi-Layer Service-Triggered Mobility

In this context, it is very important to respect the relation between threshold

values presented in Section 4.1 on page 19.

22 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Performance

6 Performance

This section describes performance indicators, counters, and events associated

with the Multi-Layer Service-Triggered Mobility feature.

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

Table 7 lists the main Key Performance Indicators (KPIs) value that can be
affected by the Multi-Layer Service-Triggered Mobility feature.

Table 7 KPIs
KPI Description
Mobility Success Rate KPI This KPI value may indicate whether the different offset value for
handover/measurement is good enough.
E-RAB Retainability per This KPI value can indicate whether service retainability is increased.
QCI KPI

6.2 Counters
This feature has no directly associated counters.

However, the handover-related counters are affected by the Multi-Layer

Service-Triggered Mobility feature. This is because UE can execute mobility
actions, release with redirect or handover, more frequently or more seldom
than when offset values are not used to change the behavior of base threshold
values.

Some example on counters, indicating whether the mobility to preferred

frequency is triggered more frequently, are listed in Table 8.

Table 8 Example counters, indicating whether the mobility to preferred

frequency is triggered more frequently
Counter Description
pmHoPrepAttLteInterF The number of attempts to start outgoing intra LTE inter frequency
handover preparation.
pmHoPrepAttSrvcc Number of SRVCC handover to UTRAN preparation attempts.
pmHoPrepAtt The number of attempts to start Single Radio Voice Call Continuity
(SRVCC) handover preparation from LTE to GSM/EDGE Radio
(GERAN) Access Network (GERAN).
pmHoPrepAtt Number of handover to UTRAN or TD-SCDMA preparation
attempts
(UTRAN)

144/221 04-LZA 701 6014 Uen A | 2015-06-23 23

 Multi-Layer Service-Triggered Mobility

Other counters can give an indication on whether some specific QCI handover
to preferred frequency in LTE is increased. Some examples on these counters
are shown in Table 9.

Note: The counters in Table 9 exist for the following MO classes:

• EUtranCellFDD

• EUtranCellTDD

Table 9 Example counters, indicating whether some specific QCI handover

to preferred frequency in LTE is increased
Counter Description
pmHoPrepAttLteInterFQci The total number of LTE inter-frequency HO preparation attempts
per QCI.
pmHoPrepSuccLteInterFQci The total number of successful LTE inter-frequency HO
preparation per QCI.
pmHoExeOutAttQci The number of handover execution attempt for ERABs per QCI
towards target cell.
pmHoExeOutSuccQci The number of ERABs per QCI that was successfully handovered
to the target cell.

More information about counters can be found in Managed Object Model

(MOM).

6.3 Events
There are no events to be newly created, removed or changed by the
Multi-Layer Service-Triggered Mobility feature. However, the event
INTERNAL_EVENT_ERAB_DATA_INFO introduced in the Service Triggered
Mobility feature must be reused for this feature when MeasConfig IE needs to
be updated during ongoing E-RAB setup, release or modified procedure.

Table 10 lists the events that are affected by the Multi-Layer Service-Triggered
Mobility feature.

Table 10 Events
Event Event Parameter Description
INTERNAL_EVENT_ERAB_ EVENT_ARRAY_RECONF_MEAS_Q Indicates the QCIs of set up,
DATA_INFO CI released, or modified bearers
that lead to a measurement
reconfiguration within the
corresponding procedure.
INTERNAL_EVENT_ERAB_ EVENT_PARAM_ERAB_PROCEDURE Indicates the ERAB related
DATA_INFO procedure (set up, release, or
modify) that is executed when the
event containing transparent ERAB
or ERAB procedure related data is
issued.

24 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 Performance

More information about events can be found in PM Event List (DU-based node)
or Lists (Baseband-based node).

144/221 04-LZA 701 6014 Uen A | 2015-06-23 25

 Multi-Layer Service-Triggered Mobility

26 144/221 04-LZA 701 6014 Uen A | 2015-06-23

 O&M Information

7 O&M Information

This section provides Operation and Maintenance (O&M) information for the
Multi-Layer Service-Triggered Mobility feature.

7.1 Feature Activation and Deactivation

Activating the feature requires that the corresponding license is installed. When
the license is installed, an MO instance MultiLayerServTriMobility is
automatically created.

Table 11 Feature MO Instance

Node type MO instance
DU-based node MO instance is OptionalFeature
License=MultiLayerServTriMo
bility
Baseband-based node MO instance is FeatureState=Mul
tiLayerServTriMobility

Feature activation and deactivation is described in Manage Licenses.

144/221 04-LZA 701 6014 Uen A | 2015-06-23 27