Service Triggered Mobility.pdf

Service Triggered Mobility

USER DESCRIPTION

94/1553-HSC 105 50/1-V2 Uen F

Copyright

Ericsson AB 2011-2012. All rights reserved. No part of this document may bereproduced in any form without the written permission of the copyright owner.

Disclaimer

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

Trademark List

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

94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

Contents

Contents

1 Introduction 11.1 Basic Characteristics 11.2 Benefits 21.3 Additional Information 2

2 Feature Operation 32.1 Network Requirements 32.2 Feature Operation Sequence Diagram 3

3 Parameters 73.1 Introduced Parameters 73.2 Affected Parameters 10

4 Network Impact 134.1 Relations between Thresholds 13

5 Associated Features and Affected Functions 155.1 Prerequisite Features 155.2 Affected Features 155.3 Related Features 165.4 Affected System Functions 16

6 Performance 176.1 KPIs 176.2 Counters 176.3 Events 17

7 O&M Information 197.1 Measurement Threshold Offsets Configuration per QCI 19

94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14


94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

Introduction

1 Introduction

This document describes the Service Triggered Mobility feature and its mainbenefits and impacts in the LTE RAN.

The Service Triggered Mobility feature enables coverage-triggered mobilitybased on the Quality of Service (QoS) defined for the User Equipment (UE)bearers. The feature applies dynamic levels of coverage thresholds based onthe QoS Class Identifier (QCI) profiles of the bearers.Each QCI profile holds offsets for the thresholds for Event A1, Event A2, EventA5, and Event B2. An eNodeB reconfigures the threshold levels in a UEbased on the changing bearer QCI profile constellation. A bearer QCI profileconstellation can change due to a bearer setup, release, or modify procedureexecution.

Each threshold configured in a UE at a particular point in time, is based on thehighest of the offsets found in all bearers' QCI profiles.

This means, for example, that a UE with bearers requiring high signal qualitywill report poor coverage earlier than another UE with bearers not requiringas high signal quality.

1.1 Basic CharacteristicsThis section describes the basic characteristics of the feature.

Feature Identity:FAJ 221 1747, Service Triggered Mobility

Replaces: N/A

Dependencies

This feature has no direct dependency on any other feature.

However, for this feature to be meaningful, at least one of the following features,being prerequisites for configuring UE measurements, must be active:

Coverage-Triggered WCDMA Session Continuity

Coverage-Triggered CDMA-eHRPD Session Continuity

Coverage-Triggered GERAN Session Continuity

Coverage-Triggered Inter-Frequency Session Continuity

194/1553-HSC 105 50/1-V2 Uen F | 2012-03-14


This feature affects the following RAN features:

Coverage-Triggered WCDMA Session Continuity

Coverage-Triggered CDMA-eHRPD Session Continuity

Coverage-Triggered GERAN Session Continuity

Coverage-Triggered Inter-Frequency Session Continuity

Coverage-Triggered WCDMA IRAT Handover

Coverage-Triggered Inter-Frequency Handover

The above listed features may be affected by the Service Triggered Mobilityfeature because of changes in the values of the measurement thresholds sentto a UE, due to the threshold offsets introduced in this feature.

1.2 BenefitsThis section describes the benefits of this feature.

The Service Triggered Mobility feature allows the operator to set mobilitythresholds for each QCI profile, with the consequence that coverage-basedmobility indirectly becomes service-based mobility. Service quality can therebybe better ensured by having UE connected to the cell that has best coveragefor the given UE services.

1.3 Additional InformationMore information about this feature and related topics can be found in thefollowing documentation:

3GPP TS 23.203 v9.7.0; Technical Specification Group Services andSystem Aspects; Policy and charging control architecture

3GPP TS 36.214 Evolved Universal Terrestrial Radio Access (E-UTRA);Physical layer; Measurements

2 94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

Feature Operation

2 Feature Operation

This section describes the Service Triggered Mobility feature in more detail,including network configuration requirements and operation flows.

Depending on the UE bearer QCI constellation, the eNodeB will configureUE measurements considering the appropriate threshold offsets that wereconfigured by the operator.

Furthermore, whenever a new service is requested by the UE involving thesetup of a new bearer with a QCI value that leads to a modification of some ofthe measurement thresholds, the eNodeB will reconfigure measurements inthe UE. The same is applicable if the UE closes a service with a high thresholddemanding QCI.

2.1 Network RequirementsThe following must be fulfilled at feature activation:

The license key must be activated to operate the Service Triggered Mobilityfeature. The ServiceTriggeredMobility Managed Object (MO) holdsthe licensing parameters for the feature.

The license key for at least one of the features required to startmeasurements in the UE, Coverage-Triggered WCDMA SessionContinuity, Coverage-Triggered CDMA-eHRPD Session Continuity,Coverage-Triggered GERAN Session Continuity, or Coverage-TriggeredInter-Frequency Session Continuity, must be activated. TheWcdmaSessionContinuity, Cdma2000SessionContinuity,GsmSessionContinuity, andInterFrequencySessionContinuityMOs hold the licensing parameters for the respective features.

Details on the process required to load and activate a license can be found inLicense Management

2.2 Feature Operation Sequence DiagramThere is no flow as such for this feature. This feature crosscuts the flows ofsome other features.

394/1553-HSC 105 50/1-V2 Uen F | 2012-03-14


So, if measurements are configured as described, for example in CoverageTriggered WCDMA Session Continuity, the Service Triggered Mobility featurewill be used:

Before configuring the measurements themselves (Event A1, Event A2,Event A5 or Event B2) to compute measurement thresholds given the UEbearer QCI constellation

For each measurement type configured in UE, the measurement thresholdssent to the UE, are computed as the maximum of all threshold valuescorresponding to the QCI profiles of the UE bearers.

Consider, for example, the Event A1 RSRP measurement. Whenconfiguring the Event A1 RSRP threshold in the UE, the valueof this threshold is obtained from the sum of the base thresholda1ThresholdRsrpPrimand the maximum value of all the offset thresholdsfor all the UE QCI profiles, namely

.

Similar reasoning can be applied, for example, for the Event A1 RSRQmeasurement threshold.

Whenever one or several bearers are set up, released, or modified for acertain UE for which measurements were previously configured

The feature is used to recompute measurement thresholds due to thebearer QCI constellation change and possibly reconfigure measurementsin the UE if some (maximum) measurement threshold value was changed.Reconfiguration of UE measurements is performed in the followingsituations:

1 When one or several bearers are set up, if at least one of the setupbearers has a QCI profile such that some threshold offset is larger thanthe current maximum value of the corresponding threshold offsets. Inthis case, the maximum value for the respective threshold is increased,which is the reason for the measurement reconfiguration.

2 When one or several bearers are released, if all bearers with QCIprofile such that some threshold offset is the maximum value of thecorresponding threshold offsets, are among the released bearers. Inthis case, the maximum value for the respective threshold is decreased,which is the reason for reconfiguration.

3 When one or several bearers are modified, if at least one of themodified bearers has been allocated a QCI profile such that somethreshold offset is larger than the current maximum value of thecorresponding threshold offset. In this case, the maximum value forthe respective threshold is increased, which is the reason for themeasurement reconfiguration.

In all three cases listed above (bearer setup, release, and modification),if several measurements are affected by similar threshold changes,

4 94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

Feature Operation

all new thresholds are sent to the UE in the same reconfigurationmessage. Moreover, this reconfiguration message is the same asis sent to the UE to inform about the set-up, released, or modifiedbearers, respectively.

The following is an example where Event A5 (RSRP) measurements arestarted after the reception of an Event A2 (bad coverage) report followed by twobearer setup, one bearer release, and one bearer QCI modification procedure(in addition, the UE has two bearers set up at the time of starting the Event A5measurements):1. When setting up the Event A5 (RSRP) measurement, the values of the and thresholds to be sentto the UE in the configuration message are computed based on the UEbearer QCI constellation.

The two bearers of the UE have QCIs 2 and 5.

The values of the base parameters are the following:

, .

The values of the offset parameters are the following:

,

,

The values of the and thresholds to be sent to the UE are the following:

2. When the first bearer setup occurs, the threshold offsets given by the QCIprofiles of the new bearers are observed. In our example, only look theEvent A5 measurement related RSRP thresholds are observed, but oneshould observe all thresholds of all configured measurements.

In this bearer setup procedure, one bearer is set up and this bearer hasa QCI profile with QCI value 7. The values of the offset thresholds for theEvent A5 RSRP measurements for QCI=7 are the following:

,

The current maximum for the

has the value 6.Since the value 8 is larger than the current maximum value,the new valueof is the following:

Similarly, the new value of is calculated as follows.

594/1553-HSC 105 50/1-V2 Uen F | 2012-03-14


Both these thresholds are larger than the previous thresholds.

The UE must therefore be reconfigured with new threshold values.

3. The next bearer setup is again with a bearer that has QCI=7. In thiscase, of course, no UE measurement reconfiguration is required, as no(maximum) threshold values have been changed.

4. The bearer release involved the two bearers with QCI=7. This meansthat the UE has left the two bearers with QCIs 2 and 5 respectively. TheUE must therefore be reconfigured with new Event A5 measurementthresholds, and these have the following values (computed at 1):

5. The QCI modification involves a modification of the bearer with QCI=2; theQCI value is changed from 2 to 7. The UE must be reconfigured with newEvent A5 measurement thresholds with values (computed at 2) as follows:

6 94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

Parameters

3 Parameters

This section describes parameters introduced by the Service Triggered Mobilityfeature and parameters affected by activating the feature.

3.1 Introduced ParametersTable 1 describes the parameters introduced by the feature Service TriggeredMobility. It lists in the first row the struct parameter encapsulating all theoffset parameters.

Note: Default settings may require adjustment for UE events to be triggered.Table 1 Introduced Parameters

Parameter Description

measReportConfigParams Encapsulates the offset quantities of the mobility measurementthresholds

Only absolute mobility measurement thresholds areconsidered. The structure holds, for example, offsets for thea1ThresholdRsrpPrim, a2ThresholdRsrpPrim, anda5Threshold1Rsrp thresholds. The offsets are meant mainlyto have values that differentiate the measurement thresholdsbetween QCIs.

a1ThresholdRsrpPrimOffset QCI dependent offset for the absolute a1ThresholdRsrpPrimthreshold

If the value of the offset is 0, the threshold corresponding to thisQCI profile will be the same as the base value in the MO class,namely ReportConfigA1Prim.a1ThresholdRsrpPrim. Therule is that the threshold for a certain QCI profile is computed asReportConfigA1Prim.a1ThresholdRsrpPrim+QciProfilePredefined.measReportConfigParams.a1ThresholdRsrpPrimOffset.

a1ThresholdRsrpSecOffset QCI dependent offset for the absolute a1ThresholdRsrpSecthreshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigA1Sec.a1ThresholdRsrpSec.The rule is that the threshold for a certain QCI profile is computedas ReportConfigA1Sec.a1ThresholdRsrpSec+QciProfilePredefined.measReportConfigParams.a1ThresholdRsrpSecOffset.

a1ThresholdRsrqPrimOffset QCI dependent offset for the absolute a1ThresholdRsrpPrimthreshold

If the value of the offset is 0, then the threshold corresponding to thisQCI profile will be the same as the base value in the MO class,namely ReportConfigA1Prim.a1ThresholdRsrqPrim. Therule is that the threshold for a certain QCI profile is computed asReportConfigA1Prim.a1ThresholdRsrqPrim+QciProfilePredefined.measReportConfigParams.a1ThresholdRsrqPrimOffset.

794/1553-HSC 105 50/1-V2 Uen F | 2012-03-14


a1ThresholdRsrqSecOffset QCI dependent offset for the absolute a1ThresholdRsrqSecthreshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigA1Sec.a1ThresholdRsrqSec.The rule is that the threshold for a certain QCI profile is computedas ReportConfigA1Prim.a1ThresholdRsrqSec+QciProfilePredefined.measReportConfigParams.a1ThresholdRsrqSecOffset.

a2ThresholdRsrpPrimOffset QCI dependent offset for the absolute a2ThresholdRsrpPrimthreshold

If the value of the offset is 0, then the threshold corresponding to thisQCI profile will be the same as the base value in the MO class,namely ReportConfigA2Prim.a2ThresholdRsrpPrim. Therule is that the threshold for a certain QCI profile is computed asReportConfigA2Prim.a2ThresholdRsrpPrim+QciProfilePredefined.measReportConfigParams.a2ThresholdRsrpPrimOffset.

a2ThresholdRsrpSecOffset QCI dependent offset for the absolute a2ThresholdRsrpPrimthreshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigA2Sec.a2ThresholdRsrpSec. Therule is that the threshold for a certain QCI profile is computed asReportConfigA2Sec.a2ThresholdRsrpSec+QciProfilePredefined.measReportConfigParams.a2ThresholdRsrpSecOffset.

a2ThresholdRsrqPrimOffset QCI dependent offset for the absolute a2ThresholdRsrqPrimthreshold

If the value of the offset is 0, then the threshold corresponding to thisQCI profile will be the same as the base value in the MO class,namely ReportConfigA2Prim.a2ThresholdRsrqPrim. Therule is that the threshold for a certain QCI profile is computed asReportConfigA2Prim.a2ThresholdRsrqPrim+QciProfilePredefined.measReportConfigParams.a2ThresholdRsrqPrimOffset.

a2ThresholdRsrqSecOffset QCI dependent offset for the absolute a2ThresholdRsrqSecthreshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigA2Sec.a2ThresholdRsrqSec.The rule is that the threshold for a certain QCI profile is computedas ReportConfigA2Sec.a2ThresholdRsrqSec+QciProfilePredefined.measReportConfigParams.a2ThresholdRsrqSecOffset.

a5Threshold1RsrpOffset QCI dependent offset for the absolute a5Threshold1Rsrpthreshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigA5.a5Threshold1Rsrp. The ruleis that the threshold for a certain QCI profile is computed as ReportConfigA5.a5Threshold1Rsrp+QciProfilePredefined.measReportConfigParams.a5Threshold1RsrpOffset.

a5Threshold1RsrqOffset QCI dependent offset for the absolute a5Threshold1Rsrqthreshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the "base" value in the MOclass, namely ReportConfigA5.a5Threshold1Rsrq. The ruleis that the threshold for a certain QCI profile is computed as ReportConfigA5.a5Threshold1Rsrq+QciProfilePredefined.measReportConfigParams.a5Threshold1RsrqOffset.

8 94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

Parameters

a5Threshold2RsrpOffset QCI dependent offset for the absolute a5Threshold2Rsrpthreshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigA5.a5Threshold2Rsrp. The ruleis that the threshold for a certain QCI profile is computed as ReportConfigA5.a5Threshold2Rsrp+QciProfilePredefined.measReportConfigParams.a5Threshold2RsrpOffset.

a5Threshold2RsrqOffset QCI dependent offset for the absolute a5Threshold2Rsrqthreshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigA5.a5Threshold2Rsrq. The ruleis that the threshold for a certain QCI profile is computed as ReportConfigA5.a5Threshold2Rsrq+QciProfilePredefined.measReportConfigParams.a5Threshold2RsrqOffset.

b2Threshold1RsrpUtraOffset QCI dependent offset for the absolute ReportConfigB2Utra.b2Threshold1Rsrp threshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigB2Utra.b2Threshold1Rsrp.The rule is that the threshold for a certain QCI profile is computedas ReportConfigB2Utra.b2Threshold1Rsrp+QciProfilePredefined.measReportConfigParams.b2Threshold1RsrpUtraOffset.

b2Threshold1RsrpCdma2000Offset

QCI dependent offset for the absolute ReportConfigB2Cdma2000.b2Threshold1Rsrp threshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigB2Cdma2000.b2Threshold1Rsrp. Therule is that the threshold for a certain QCI profile is computed asReportConfigB2Cdma2000.b2Threshold1Rsrp+QciProfilePredefined.measReportConfigParams.b2Threshold1RsrpCdma2000Offset.

b2Threshold1RsrpGeranffset QCI dependent offset for the absolute ReportConfigB2Geran.b2Threshold1Rsrp threshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigB2Geran.b2Threshold1Rsrp.The rule is that the threshold for a certain QCI profile is computedas ReportConfigB2Geran.b2Threshold1Rsrp+QciProfilePredefined.measReportConfigParams.b2Threshold1RsrpGeranOffset.

b2Threshold1RsrqUtraOffset QCI dependent offset for the absolute ReportConfigB2Utra.b2Threshold1Rsrq threshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigB2Utra.b2Threshold1Rsrq.The rule is that the threshold for a certain QCI profile is computedas ReportConfigB2Utra.b2Threshold1Rsrq+QciProfilePredefined.measReportConfigParams.b2Threshold1RsrqUtraOffset.

b2Threshold1RsrqCdma2000Offset

QCI dependent offset for the absolute ReportConfigB2Cdma2000.b2Threshold1Rsrq threshold

If the value of the offset is 0, then the threshold corresponding to thisQCI profile will be the same as the base value in the MO class,namely ReportConfigB2Cdma2000.b2Threshold1Rsrq. Therule is that the threshold for a certain QCI profile is computed asReportConfigB2Cdma2000.b2Threshold1Rsrq+QciProfilePredefined.measReportConfigParams.b2Threshold1RsrqCdma2000Offset.

994/1553-HSC 105 50/1-V2 Uen F | 2012-03-14


b2Threshold1RsrqGeranOffset QCI dependent offset for the absolute ReportConfigB2Geran.b2Threshold1Rsrq threshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely ReportConfigB2Geran.b2Threshold1Rsrq.The rule is that the threshold for a certain QCI profile is computedas ReportConfigB2Geran.b2Threshold1Rsrq+QciProfilePredefined.measReportConfigParams.b2Threshold1RsrqGeranOffset.

b2Threshold2Cdma2000Offset QCI dependent offset for the absolute b2Threshold2Cdma2000threshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely b2Threshold2Cdma2000. The rule is that thethreshold for a certain QCI profile is computed as ReportConfigB2Cdma2000.b2Threshold2Cdma2000+QciProfilePredefined.measReportConfigParams.b2Threshold2Cdma2000Offset.

b2Threshold2GeranOffset QCI dependent offset for the absolute b2Threshold2Geranthreshold

If the value of the offset is 0, then the threshold corresponding tothis QCI profile will be the same as the base value in the MOclass, namely b2Threshold2Geran. The rule is that the thresholdfor a certain QCI profile is computed as ReportConfigB2Geran.b2Threshold2Geran+QciProfilePredefined.measReportConfigParams.b2Threshold2GeranOffset .

b2Threshold2EcNoUtraOffset QCI dependent offset for the absolute b2Threshold2EcNoUtrathreshold

If the value of the offset is 0, then the threshold correspondingto this QCI profile will be the same as the base value inthe MO class, namely b2Threshold2EcNoUtra. The ruleis that the threshold for a certain QCI profile is computed asReportConfigB2Utra.b2Threshold2EcNoUtra+QciProfilePredefined.measReportConfigParams.b2Threshold2EcNoUtraOffset.

b2Threshold2RscpUtraOffset QCI dependent offset for the absolute b2Threshold2RscpUtrathreshold

If the value of the offset is 0, then the threshold correspondingto this QCI profile will be the same as the base value inthe MO class, namely b2Threshold2RscpUtra. The ruleis that the threshold for a certain QCI profile is computed asReportConfigB2Utra.b2Threshold2RscpUtra+QciProfilePredefined.measReportConfigParams.b2Threshold2RscpUtraOffset.

The struct parameter presented in the table above is present - containing thesame offset attributes - also in the MO class QciProfileOperatorDefineandhas the same name, namely measReportConfigParams.

3.2 Affected ParametersTable 2 describes the parameters affected by the feature and all the base"parameters affected when activating the Service Triggered Mobility feature.

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

10 94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

Parameters

Consider, for example, the Managed Object Model (MOM) parametera5Threshold1Rsrp. When the Service Triggered Mobility feature is active,the value of this parameter will not change compared with the value configuredearlier in the MOM. However, when the UE is configured with the Event A5RSRP Threshold1, the value of this thresholds is computed in the eNodeBas the sum between the base value (a5Threshold1Rsrp) and the offsetvalue (a5Threshold1RsrpOffset). The same is valid for all other basethresholds where the value sent to the UE is changed with the value of theoffset parameter.

Note: A threshold offset parameter changes the effect of a base thresholdparameter only if the value of the offset is non-zero.

Table 2 Affected ParametersParameter Description

a1ThresholdRsrpPrim RSRP threshold value for the primary Event A1 measurementUsed only when triggerQuantityA2Prim is set to RSRP.

a1ThresholdRsrqPrim RSRQ threshold value for the primary Event A1 measurementUsed only when triggerQuantityA2Prim is set to RSRQ.

a1ThresholdRsrpSec RSRP threshold value for the secondary Event A1 measurementUsed only when triggerQuantityA2Sec is set to RSRP.

a1ThresholdRsrqSec RSRQ threshold value for the secondary Event A1 measurementUsed only when triggerQuantityA2Prim is set to RSRQ.

a2ThresholdRsrpPrim Primary RSRP threshold value for eventA2Used only when triggerQuantityA2Prim is set to RSRP.

a2ThresholdRsrpSec Secondary RSRP threshold value for eventA2Used only when triggerQuantityA2Sec is set to RSRP.

a2ThresholdRsrqPrim Primary RSRQ threshold value for eventA2Used only when triggerQuantityA2Prim is set to RSRQ.

a2ThresholdRsrqSec Secondary RSRQ threshold value for eventA2Used only when triggerQuantityA2Sec is set to RSRQ.

a5Threshold1Rsrp RSRP threshold value (for the serving cell) for the Event A5measurement

Used only when triggerQuantityA5 is set to RSRP.a5Threshold2Rsrp RSRP threshold2 value (for the target cell) for the Event A5

measurement

Used only when triggerQuantityA5 is set to RSRP.a5Threshold1Rsrq RSRQ threshold value (for the serving cell) for the Event A5

measurement

Used only when triggerQuantityA5 is set to RSRQ.a5Threshold2Rsrq RSRQ threshold2 value (for the target cell) for the Event A5

measurement

Used only when triggerQuantityA5 is set to RSRQ.

1194/1553-HSC 105 50/1-V2 Uen F | 2012-03-14


Parameter Descriptionb2Threshold1Rsrp RSRP threshold value (for the serving cell) for the Event B2

CDMA2000 measurementUsed only when triggerQuantityB2 is set to RSRP.

b2Threshold1Rsrq RSRQ threshold value (for the serving cell) for the Event B2CDMA2000 measurementUsed only when triggerQuantityB2 is set to RSRQ.

b2Threshold2Cdma2000 CDMA2000 threshold value for the Event B2 measurementb2Threshold1Rsrp RSRP threshold value (for the serving cell) for the Event B2

GERAN measurementUsed only when triggerQuantityB2 is set to RSRP.

b2Threshold1Rsrq RSRQ threshold value (for the serving cell) for the Event B2GERAN measurementUsed only when triggerQuantityB2 is set to RSRQ.

b2Threshold2Geran GERAN threshold value for the Event B2 measurementb2Threshold1Rsrp RSRP threshold value (for the serving cell) for the Event B2 UTRA

measurement

Used only when triggerQuantityB2 is set to RSRP.b2Threshold1Rsrq RSRQ threshold value (for the serving cell) for the Event B2 UTRA

measurement

Used only when triggerQuantityB2 is set to RSRQ.b2Threshold2RscpUtra RSCP threshold value for the Event B2 measurement

Used only when measQuantityUtraFDD is set to RSCP.

b2Threshold2EcNoUtra Ec/No (ratio of energy per modulation bit-to-noise spectral density)threshold value for the Event B2 measurement

Used only when measQuantityUtraFDD is set to ECNO.

12 94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

Network Impact

4 Network Impact

This section describes how the Service Triggered Mobility feature impactsthe network functions and capabilities.

4.1 Relations between ThresholdsWhen configuring measurement threshold offsets, the following relationsbetween the values of the different involved thresholds should be considered.These relations are applicable already for the base threshold values and are tobe preserved when configuring different offsets for the different QCIs.

Namely, the following relation should exists between the thresholds for badcoverage (Event A2), serving cell better than (Event A1), and best cell on otherLTE frequency or Inter Radio Access Technology regarding the serving cell(Events A5 and B2 respectively):

and

The explanation for the need for the relations is the following:

1 For a UE to detect good coverage in the serving cell, the cell shouldbe much better than when the UE detected bad coverage. That is whythe Event A2 related quantity should be strictly smaller than the EventA1 related quantity.

2 To be acceptable for the UE to be moved to a good enough target cell,the serving cell should be worse than when the UE detected bad coverage(Event A5 quantity should be at most as great as the Event A2 quantity).The idea is that when the UE detects bad coverage, this is only a triggerfor the UE to start looking for a better target cell, not necessarily that the UEwill loose coverage. Then, since the intention is to actually keep the UE inthe serving cell as long as possible, the UE should execute a mobility actiononly if the serving cell got even worse than at the time of the trigger.

A concrete example of threshold relation (considering attribute names from theMOM) is the following:

The same type of relation must be preserved per profile considering the offsetparameters that are introduced. Namely, for

, where , thefollowing inequalities must be satisfied:

1394/1553-HSC 105 50/1-V2 Uen F | 2012-03-14


14 94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

Associated Features and Affected Functions

5 Associated Features and AffectedFunctions

This section describes how the Service Triggered Mobility feature affects otherfeatures and functions.

5.1 Prerequisite FeaturesTable 3 lists prerequisite features to the Service Triggered Mobility feature.At least one of these features must be active prior to introducing the ServiceTriggered Mobility feature.

Table 3 Prerequisite FeaturesFeature Description

Coverage-Triggered WCDMA SessionContinuity

This feature must be active to be able to start Event B2 UTRA,A1, and A2 measurements in UE, and implicitly to be able touse the configured threshold offset parameters.

Coverage-Triggered CDMA-eHRPDSession Continuity

This feature must be active to be able to start Event B2CDMA2000, A1, and A2 measurements in UE, and implicitly tobe able to use the configured threshold offset parameters.

Coverage-Triggered GERAN SessionContinuity

This feature must be active to be able to start Event B2GERAN, A1, and A2 measurements in UE, and implicitly to beable to use the configured threshold offset parameters.

Coverage-Triggered Inter-FrequencySession Continuity

This feature must be active to be able to start Event A5, A1,and A2 measurements in UE, and implicitly to be able to usethe configured threshold offset parameters.

5.2 Affected FeaturesTable 4 lists features that are affected by the Service Triggered Mobility feature.

Table 4 Affected FeaturesFeature Description

Coverage-Triggered WCDMA SessionContinuity

This feature is affected regarding the values of the thresholdsfor Event B2 UTRA, A1, and A2 measurements sent to UE. Inaddition, the feature is affected regarding changes in the mobilitypattern of UE that are released to a UTRA frequency.

Coverage-Triggered CDMA-eHRPDSession Continuity

This feature is affected regarding the values of the thresholds forEvent B2 CDMA2000, A1, and A2 measurements sent to UE. Inaddition, the feature is affected regarding changes in the mobilitypattern of UE that are released to a CDMA2000 frequency.

Coverage-Triggered GERAN SessionContinuity

This feature is affected regarding the values of the thresholdsfor Event B2 GERAN, A1, and A2 measurements sent to UE. Inaddition, the feature is affected regarding changes in the mobilitypattern of UE that are released to a GERAN frequency.

1594/1553-HSC 105 50/1-V2 Uen F | 2012-03-14


Feature Description

Coverage-Triggered Inter-FrequencySession Continuity

This feature is affected regarding the values of the thresholds forEvent A5, A1, and A2 measurements sent to UE. In addition, thefeature is affected regarding changes in the mobility pattern ofUE that are released to another LTE frequency.

Coverage-Triggered WCDMA IRATHandover

This feature is affected regarding changes in the mobilitypattern of UE that perform handover to a UTRA (WCDMA) cell.

Coverage-Triggered Inter-FrequencyHandover

This feature is affected regarding changes in the mobilitypattern of UE that perform handover to an LTE cell on adifferent frequency.

5.3 Related FeaturesThis feature is related to the feature Operator Defined QCI.

5.4 Affected System FunctionsThis feature affects the mobility patterns of UE due to changes in the settings ofmeasurement thresholds through tuning of threshold offsets per QCI.

Threshold offsets must be carefully configured to achieve the desired UEdifferentiation given the services that UE use.

Threshold offset settings (and, of course, base threshold settings as well)must be such that UE is ordered to look for better target cells when there isreally a high chance of finding such cells.

In this context, it is very important to respect the relation between thresholdvalues presented in Section 4.1 on page 13.

16 94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

Performance

6 Performance

This section describes performance indicators, counters, and events associatedwith the Service Triggered Mobility feature.

6.1 KPIsThis feature has no associated Key Performance Indicators (KPIs).However, due to the effects on UE handover patterns mentioned in Section 5.2on page 15, the Mobility Success Rate KPI is indirectly affected by the ServiceTriggered Mobility feature.

6.2 CountersThis feature has no directly associated counters.

However, the handover and context release-related counters are affectedby the Service Triggered Mobility feature. This is because UE can executemobility actions, release with redirect or handover, more frequently or moreseldom than when offset values are not used to change the behavior of basethreshold values.

Some example counters for handover are the following:

pmHoPrepAttWcdma

pmHoExeAttWcdma

pmHoPrepAttLteInterF

pmHoExeAttLteInterF

Some example counters for release with redirect are the following:

pmUeCtxtRelSCEUtra

pmUeCtxtRelSCCdma

6.3 EventsTable 5 lists the events associated with the Service Triggered Mobility feature.

1794/1553-HSC 105 50/1-V2 Uen F | 2012-03-14


Table 5 EventsEvent Event Parameter DescriptionINTERNAL_EVENT_ERAB_DATA_INFO

EVENT_ARRAY_RECONF_MEAS_QCI

Indicates the QCIs of set up,released, or modified bearersthat lead to a measurementreconfiguration within thecorresponding procedure

INTERNAL_EVENT_ERAB_DATA_INFO

EVENT_PARAM_ERAB_PROCEDURE Indicates the ERAB relatedprocedure (set up, release, ormodify) that is executed when theevent containing transparent ERABor ERAB procedure related data isissued

More information about events can be found in PM Event List.

18 94/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

O&M Information

7 O&M Information

This section provides Operation and Maintenance (O&M) information for theService Triggered Mobility feature.

A license and parameter setting activates the Service Triggered Mobility feature.Details of the license activation process can be found in License Management.

Furthermore, measurement threshold offsets must be configured appropriately.See Section 7.1 on page 19

7.1 Measurement Threshold Offsets Configuration per QCIFor the Service Triggered Mobility feature to work as expected, that is to ensurethat some UE with certain bearer QCI constellation are served differently fromother UE with other bearer QCI constellation, the operator must configurethe offset attributes for each QCI in the MOM with values that are distinct forthe QCI. When configuring the threshold offsets, the recommended relationsbetween thresholds, presented in Section 4.1 on page 13, must be considered.

The parameters to configure are found in the measReportConfigParamsattribute in the QciProfilePredefined MO class and in themeasReportConfigParams attribute in the QciProfileOperatorDefined.

The structure contains offset attributes corresponding to all existingmeasurement threshold parameters (see also Table 1).

1994/1553-HSC 105 50/1-V2 Uen F | 2012-03-14

toc1 Introduction1.1 Basic CharacteristicsDependencies1.2 Benefits1.3 Additional Information

2 Feature Operation2.1 Network Requirements2.2 Feature Operation Sequence Diagram

3 Parameters3.1 Introduced Parameters3.2 Affected Parameters

4 Network Impact4.1 Relations between Thresholds

5 Associated Features and Affected Functions5.1 Prerequisite Features5.2 Affected Features5.3 Related Features5.4 Affected System Functions

6 Performance 6.1 KPIs6.2 Counters6.3 Events

7 O&M Information7.1 Measurement Threshold Offsets Configuration per QCI

Documents

Service Triggered Mobility.pdf