Subscriber Triggered Mobility.pdf

Subscriber Triggered Mobility

USER DESCRIPTION

101/1553-HSC 105 50/1-V2 Uen C1

Copyright

Ericsson AB 2011. 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.

101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

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 6

2.2 RFPM Operation Description 6

2.3 ORC Operation Sequence Diagram 8

3 Parameters 9

3.1 Introduced Parameters 9

3.2 Affected Parameters 11

4 Network Impact 13

4.1 Coverage 13

4.2 Mobility 13

5 Associated Features and Affected Functions 15

5.1 Prerequisite Features 15

5.2 Affected Features 15

5.3 Related Features 16

5.4 Affected System Functions 16

6 Performance 17

6.1 KPIs 17

6.2 Counters 17

6.3 Events 17

7 O&M Information 19

101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09


101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

Introduction

1 Introduction

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

This feature enables individual control of mobility characteristics for a UserEquipment (UE) based on Subscriber Profile ID for RAT/Frequency Priority(SPID).

1.1 Basic Characteristics

This section describes the basic characteristics of the feature.

Feature Identity:FAJ 221 0016, Subscriber Triggered Mobility

N/A

Dependencies

This feature has no prerequisite features.

This feature affects the following RAN features:

Coverage-Triggered Inter-Frequency Session Continuity

Adds some extra criteria when selecting which frequency and prioritiesthat shall be used.

Coverage-Triggered GERAN Session Continuity


Coverage-Triggered WCDMA Session Continuity


Coverage-Triggered CDMA-eHRPD Session Continuity


CS Fallback to GERAN and UTRAN


1101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09


Intra-LTE Handover

Adds some extra criteria for incoming handovers to cells that are in mode"Reserved for operator use". Only UEs with a matching SPID value areallowed access.

Coverage-Triggered WCDMA IRAT Handover

Adds some extra criteria for incoming handovers to cells that are in mode"reserved for operator use". Only UEs with a matching SPID value areallowed access.

Coverage-Triggered Inter-Frequency Handover

Adds some extra criteria for incoming handovers to cells that are in mode"reserved for operator use". Only UEs with a matching SPID value areallowed access.

Idle Mode Support

Affected if the UE belongs to a SPID value where the cell reselectionpriority differs from the ones sent out in the system information (SIB). Forthis UE, a dedicate priority will be added by the RBS at RRC CONNECTIONRELEASE (when the UE goes from RRC_CONNECTED to RRC_IDLE). Thesededicated priorities overrides the ones sent out in the system information.Otherwise, the UE handling is the same.

1.2 Benefits

This section describes the benefits of this feature.

The use of SPID makes it possible to create and sell differentiated subscriptiontypes. For example, a high-rate subscription can offer the highest possiblethroughput for the end-user, whereas a low rate subscription offers lowerthroughput for the end-user. If not used, the RBS cannot differentiate the UEand will as a result of this give every user equal priority and throughput.

Telephony-only subscribers or low data-rate subscriptions can be directed tomove to RANs that offers lower data-rate networks than EUTRAN.

Using SPID, the operator configures new frequencies and priorities that onlyaffect a given SPID value. This enables the operator to define test-UEsubscriptions that are the only UE that are affected by the new frequency andpriorities. Once tested and proven, the configuration can be applied for allUE. This reduces or removes the need to temporarily disable part of the RANto try out new configurations.

This feature further uses SPID to determine if UE is allowed to performincoming handover to cells that are in mode reserved for operator use. OnlyUE with specific SPID values are allowed access. This way a test-UE isallowed access, but all others are blocked.

2 101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

Introduction

1.3 Additional Information

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

3GPP TS 36.413 S1 Application Protocol (S1AP)

3GPP TS 36.423 X2 Application Protocol (X2AP)

3GPP TS 36.300 Overall description; Stage 2

3GPP TS 36.304 User Equipment (UE) procedures in idle mode

Coverage-Triggered Inter-Frequency Session Continuity

Coverage-Triggered GERAN Session Continuity

Coverage-Triggered WCDMA Session Continuity

Coverage-Triggered CDMA-eHRPD Session Continuity

CS Fallback to GERAN and UTRAN

Idle Mode Support

Intra-LTE Handover

Coverage-Triggered WCDMA IRAT Handover

Coverage-Triggered Inter-Frequency Handover

3101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09


4 101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

Feature Operation

2 Feature Operation

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

The SPID parameter received by the RBS through the S1 interface is an indexreferring to user information for mobility profile and service use profile. Theinformation is UE specific and applies to all its radio bearers. This index ismapped by the RBS to locally defined configuration to apply specific RadioResource Management (RRM) strategies like defining RRC_IDLE modepriorities and control inter-RAT/inter-frequency handover in RRC_CONNECTEDmode.

The Subscriber Triggered Mobility feature acts on SPID values, but the actionsthe eNodeB can trigger are quite different from each other and are for thatreason activated separately.

The Subscriber Triggered Mobility feature contains of two parts:

RAT and Frequency Priority Modification (RFPM)

Handles the modification of RAT frequency priority

Operator Reserved Cell (ORC)

Handles the blocking of incoming handovers

For ORC, the locally defined configuration is performed in theSpidHoWhiteList MO. The configuration includes a list of SPID values thatare allowed to perform incoming handover if the cell is in the reserved foroperator use mode.

For RFPM, the locally defined configuration is performed in the RATFreqPrioMO. The RATFreqPrio MO is configured with frequencies, correspondingpriority and a list of SPID values that are associated with this configuration. Thesame SPID value can only be included in one of the RATFreqPrio MOs.

For UE that is not associated with a SPID value or if the SPID valueis not included in any of the RATFreqPrio , the default prioritiesdefined in UtranFreqRelation, GeranFreqGroupRelation,UtranFreqRelation and CDMA200FreqBandRelation MOs are used.Further, the LTE RBS compares the configuration in RATFreqPrio MO with itscurrent frequency relations to sort out which frequencies can be used.

5101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09


2.1 Network Requirements

This section is divided on requirements for the following:

RFPM

ORC

The following must be fulfilled at feature activation for the part handling RFPM:

The target RAT must have its frequency priorities configured in a consistentway with the SPID handling in the E-UTRAN, otherwise the UE couldexperience a ping-pong effect, being pushed back and forth betweenthe two RATs.

A license key must be activated to operate the RFPM. The licensing MO isthe SpidRATFreqPrio MO. Details on the process required to load andactivate the license are provided in License Management

The MME must be able to receive the RFSP when identifying the subscriberand map this to a SPID that shall be sent to the RBS.

The RBS must be configured with inter RAT inter-frequencies in the LTERBS during network configurations or by SON features. These frequencieswill be used when evaluating which frequencies configured for RFPM areallowed to be used for RFPM.

The following must be fulfilled at feature activation for the part handling ORC:

A license key must be activated to operate the ORC. The licensing MO isthe SpidHoWhiteList MO. Details on the process required to load andactivate the license are provided in License Management.

The MME must be able to receive the RFSP when identifying the subscriberand map this to a SPID to send to the RBS.

The HoWhiteList MO must have been configured with the SPID valuesthat are be allowed access.

The RBS must be configured and have the licenses required to performincoming handovers.

The cell must be configured to be in the reserved for operator use mode.

2.2 RFPM Operation Description

If the UE has a SPID value associated with it, the LTE RBS (in step 2 of Figure1 as described in Coverage-Triggered Inter-Frequency Session Continuity)adds some additional criteria. For all frequencies found in the RATFreqPrioMO that corresponds to the SPID value are matched towards the list offrequencies found in EUtranFreqRelation, GeranFreqGroupRelation,UtranFreqRelation, and CDMA200FreqBandRelation MOs. Only

6 101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

Feature Operation

frequencies that exists in both lists are allowed, the rest are not used. Forthe selected frequencies, the priorities found in the RATFreqPrio MO willbe used for the remaining sequence found in figure 1 in Coverage-TriggeredInter-Frequency Session Continuity If no frequencies are found, the SPIDvalue associated with the UE will be ignored and the frequencies and prioritiesfound in the MO EUtranFreqRelation, GeranFreqGroupRelation,UtranFreqRelation, and CDMA200FreqBandRelation MOs will be usedinstead (the INTERNAL_EVENT_SPID_PRIORITY_IGNORED pmEvent will besent if this happens).

When UE transit from RRC_CONNECTED to RRC_IDLE, the RFPM checks ifthe frequencies and priorities, for this UE, differs from the ones sent out insystem information. If it differs, the RRC CONNECTION RELEASE messagefrom the RBS to the UE will include a list of dedicated cell reselection priority(as specified in 3GPP TS 36.331). These dedicated priorities override thepriorities broadcast in the system information. The dedicated priorities arevalid for a t320 period of time. During this t320 period of time, the dedicatedcell reselection priority is used by the UE to determine on which RAT andfrequency it to camp while in RRC IDLE mode. More information about whenthe dedicated priorities are used and when they are valid can be found in 3GPPTS 36.304, chapter Cell Reselection evaluation process.

7101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09


2.3 ORC Operation Sequence Diagram

L0000524A

Incoming handover

Feature SubscriberTriggered Mobility is

OPERABLE?

The handover is allowedto continue with

resource preparation

yes

no

yes

no

yes

no

The handover is rejected

ORC enabled?

Cell in modereserved for

operator use?

yesno The SPID valueof the UE

is allowed?

Figure 1 SPID Decision Diagram at Incoming Handover

The following is a description of the workflow inFigure 1:

1. For a incoming handover, the serviceStateSpidHoWhitelist ischecked to see if ORC is activated. If not, the handover is allowed tocontinue the preparation.

2. A check is performed to see if the cell is in mode reserved for operatoruse. If not, handover is allowed to continue the preparation.

3. If the SPID is included in the handover preparation message and matchesany of the ones in spidList, handover is allowed to continue preparation,otherwise the UE is rejected and a handover preparation failure message issent back to the source LTE RBS.

8 101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

Parameters

3 Parameters

This section describes parameters introduced by the Subscriber triggeredmobility feature and parameters affected by activating the feature.

3.1 Introduced Parameters

Table 1 describes the parameters introduced by the feature.

Table 1 Introduced Parameters in RATFreqPrio MO

Parameter Description

spidList List of SPID for RAT/Frequency Priority that use the priorities andfrequencies configured in this instance of the RATFreqPrio MO

t320 Validity time for cell reselection priority information provided bydedicated signaling for the priorities and frequencies configured inthis instance of RATFreqPrio MO

bandClassPrioListCDMA2000 CDMA2000 frequencies and corresponding priorities (for both Idleand connected mode) that shall be used for a UE with a matchingSPID for RAT/Frequency Priority on the spidList for this instanceof RATFreqPrio MO

freqGroupPrioListGERAN GERAN frequencies and corresponding priorities (for both Idleand connected mode) that shall be used for a UE with a matchingSPID for RAT/Frequency Priority on the spidList for this instanceof RATFreqPrio MO

freqPrioListEUTRA EUTRA frequencies and corresponding priorities (for both Idleand connected mode) that shall be used for a UE with a matchingSPID for RAT/Frequency Priority on the spidList for this instanceof RATFreqPrio MO

freqPrioListUTRA UTRA frequencies and corresponding priorities (for both Idle andconnected mode) that shall be used for a UE with a matchingSPID for RAT/Frequency Priority on the spidList for this instanceof RATFreqPrio MO

Table 2 describes the struct members introduced by the feature inBandClassPrioListCDMA2000.

Table 2 Struct Members for BandClassPrioListCDMA2000


cellReselectionPriority Absolute priority of the concerned carrier frequency, as used bythe cell reselection procedure

Corresponds with parameter priority in 3GPP TS 36.304. Value0 means: lowest priority. The UE behavior for the case the field isabsent, if applicable, is specified in TS 36.304.

connectedModeMobilityPrio Prioritizes CDMA2000 bandclasses among all bandclasses relatedto the cell for UEs in connected mode

freqCdma Identifies the carrier frequency within a CDMA2000 band

hrpdBandClass Identifies the HRPD frequency Band in wbch the HRPD carriercan be found

9101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09


Table 3 describes the struct members introduced by the feature inFreqGroupPrioGERAN.

Table 3 Struct Members for FreqGroupPrioGERAN


cellReselectionPriority Absolute priority of the concerned carrier frequency, as usedby the cell reselection procedure. Corresponds with parameter"priority" in TS 36.304. The UE behavior for the case the field isabsent, if applicable, is specified in TS 36.304.

connectedModeMobilityPrio Prioritizes GERAN frequencies among all frequencies related tothe cell for UE in connected mode

frequencyGroupId Identifies the GeranFreqGroup in the network

bandIndicatorGERAN Indicates how to interpret an associated GERAN carrier ARFCN

The attribute indicates the GERAN frequency band in case theARFCN value can concern either a DCS 1800 or a PCS 1900carrier frequency. For ARFCN values not associated with one ofthese bands, the indicator has no meaning.

csFallbackPrio Prioritizes GERAN frequencies among all frequencies related tothe cell for UE in connected mode

csFallbackPrioEC Prioritizes GERAN frequencies among all frequencies related tothe cell for UE in connected mode

Sets the priority to which frequency/frequency group to makeCS Falback to. This parameter is only valid for emergency csfallback calls.

Table 4 describes the struct members introduced by the feature inFreqPrioEUTRA.

Table 4 Struct Members for FreqPrioEUTRA



Corresponds with parameter "priority" in TS 36.304. The UEbehavior for the case the field is absent, if applicable, is specifiedin 3GPP TS 36.304.

connectedModeMobilityPrio Prioritizes EUTRAN frequencies among all frequencies related tothe cell for UE in connected mode

arfcnValueEUtranDl Indicates the ARFCN applicable for a downlink E-UTRA carrierfrequency, as defined in 3GPP TS 36.104 for specified E-UTRAbands

For TDD, this also indicate the ARFCN for uplink. The valuesthat can be used depends on national operator specific frequencyallocation as well as from the supported frequency bands of theequipment in the eNodeB.

Table 5 describes the struct members introduced by the feature inFreqPrioUTRAN.

10 101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

Parameters

Table 5 Struct Members for FreqPrioUTRAN



Corresponds with parameter "priority" in TS 36.304. The UEbehavior for the case the field is absent, if applicable, is specifiedin TS 36.304.

connectedModeMobilityPrio Prioritizes UTRAN frequencies among all frequencies related tothe cell for UE in connected mode

arfcnValueUtranDl Indicate the ARFCN applicable for a downlink UTRAN carrierfrequency, as defined in 3GPP TS 25.331

csFallbackPrio Prioritizes UTRAN frequencies among all frequencies related tothe cell for UE in connected mode

csFallbackPrioEC Prioritizes UTRAN frequencies among all frequencies related tothe cell for UE in connected mode

Sets the priority to which frequency/frequency group to makeCS Fallback to.. This parameter is only valid for emergency csfallback calls.

spidList Contains a white list of SPID values that are allowed to performa incoming handover requests when the cell is in the reservedfor operator use mode

3.2 Affected Parameters

The implementation of this feature affects no parameters.

11101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09


12 101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

Network Impact

4 Network Impact

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

4.1 Coverage

This feature has no impact on the physical cell coverage. However RFPM, thatallows different priorities for frequencies for each subscription, can result insome subscriptions experiences a higher probability for better coverage thanothers (depending if the target frequency has a good cell coverage).

4.2 Mobility

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

The RFPM part of the feature introduces subscription-based priorities thataffect both RRC_IDLE mode priorities and control inter-RAT/inter frequencyhandover in RRC_CONNECTED mode. These priorities are used to determinewhere the UE camps while in IDLE mode and which target frequency is usedwhen mobility actions in connected mode are required.

The ORC part of the feature introduces blocking of incoming handovers toa cell in reserved for operator use and the UE does not belong to a SPIDvalue that is allowed.

When the Subscriber Triggered Mobility feature is deactivated, the SPID isignored by the LTE RBS, but stored and forwarded at handover.

13101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09


14 101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

Associated Features and Affected Functions

5 Associated Features and AffectedFunctions

This section describes how the Subscriber triggered mobility feature affectsother features and functions.

5.1 Prerequisite Features

This feature has no prerequisite features

5.2 Affected Features

Table 6 lists features that are affected by the Subscriber triggered mobilityfeature.

Table 6 Affected Features

Feature Description

Coverage-Triggered Inter-FrequencySession Continuity

If RFPM is activated, the Coverage-Triggered Inter-FrequencySession Continuity feature adds additional criteria when selectingfrequencies (see Step 2 in Figure 1 of Coverage-TriggeredInter-Frequency Session Continuity). If the UE has an SPID valueassociated with it, all frequencies found in the RATFreqPrioMO that corresponds to this SPID value are matched towardsthe list of frequencies found in the EUtranFreqRelation MO.Only frequencies that exists in both lists are allowed, the restare not used.(1)

Coverage-Triggered GERAN SessionContinuity

If RFPM is activated, the Coverage-Triggered GERAN SessionContinuity feature adds additional criteria when selectingfrequencies (see Step 2 in Figure 1 of Coverage-TriggeredInter-Frequency Session Continuity). If the UE has a SPID valueassociated with it, all frequencies found in the RATFreqPrioMO that corresponds to this SPID value are matched towardsthe list of frequencies found in the GeranFreqGroupRelationMOs. Only frequencies that exists in both lists are allowed, therest are not used.(2)

Coverage-Triggered WCDMA SessionContinuity

If RFPM is activated, the Coverage-Triggered WCDMA SessionContinuity feature adds additional criteria when selectingfrequencies (see Step 2 in Figure 1 of Coverage-TriggeredInter-Frequency Session Continuity). If the UE has a SPID valueassociated with it, all frequencies found in the RATFreqPrioMO that corresponds to this SPID value are matched towardsthe list of frequencies found in the UtranFreqRelation MO.Only frequencies that exists in both lists are allowed, the restare not used.(3)

Coverage-Triggered CDMA-eHRPDSession Continuity

If RFPM is activated, the Coverage-Triggered CDMA-eHRPDSession Continuity feature adds additional criteria when selectingfrequencies (see Step 2 in Figure 1 of Coverage-TriggeredInter-Frequency Session Continuity). If the UE has a SPID valueassociated with it, all frequencies found in the RATFreqPrioMO that corresponds to this SPID value are matched towardsthe list of frequencies found in CDMA200FreqBandRelationManaged Objects (MO). Only frequencies that exists in both listsare allowed, the rest are not used.(4)

15101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09


Feature Description

CS Fallback to GERAN and UTRAN If RFPM is activated and the UE has a SPID value associated withit, the priority found in RATFreqPrio MO are matched towardsthe list of frequencies found in the GeranFreqGroupRelationand UtranFreqRelation. Only frequencies that exists in boththe RATFreqPrio and either GeranFreqGroupRelation orUtranFreqRelation lists are allowed, the rest are not used.The CS Fallback to GERAN and UTRAN feature will select thehighest priority frequency relation that is supported by the UE.

Idle Mode Support Sending dedicated priorities to the UE, the priorities broadcast inthe system information is ignored by the affected UE.

Intra-LTE Handover When ORC is activated and the cell is in reserved for operatoruse mode, only UE that have a SPID value that is configured onthe allowed list are allowed to continue the handover preparation.

Coverage-Triggered WCDMA IRATHandover

When ORC is activated and the cell is in the reserved foroperator use mode, only UE that have a SPID value thatis configured on the allowed list are allowed to continue thehandover preparation.

Coverage-Triggered Inter-FrequencyHandover

When ORC is activated and the cell is in the reserved foroperator use mode, only UE that have a SPID value thatis configured on the allowed list are allowed to continue thehandover preparation.

(1) If no frequencies match, the frequencies and priorities found in the EUtranFreqRelationMO will be used instead.(2) If no frequencies match, the frequencies and priorities found in the GeranFreqGroupRelationn MO will be used instead.(3) If no frequencies match, the frequencies and priorities found in the UtranFreqRelationMO will be used instead(4) If no frequencies match, the frequencies and priorities found in the CDMA200FreqBandRelation MO will be used instead.

5.3 Related Features

This feature is not related to any other feature.

5.4 Affected System Functions

This feature affects no system functions.

16 101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

Performance

6 Performance

This section describes performance indicators, counters, and events associatedwith the Subscriber triggered mobility feature.

6.1 KPIs

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

6.2 Counters

This feature has no directly associated counters.

6.3 Events

Table 7 lists the events associated with the Subscriber Triggered Mobilityfeature.

Table 7 Events

Event Event Parameter Description

INTERNAL_EVENT_SPID_PRIORITY_IGNORED

EVENT_PARAM_SPID_VALUE SPID

INTERNAL_PROC_HO_PREP_X2_IN


INTERNAL_PROC_HO_PREP_S1_IN


INTERNAL_EVENT_UE_MOBILITY_EVAL


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

17101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09


18 101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09

O&M Information

7 O&M Information

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

A license and parameter setting activates the RFPM part of the SubscriberTriggered Mobility feature. Details of the license activation process can befound in License Management.

A license and parameter setting activate the ORC part of the SubscriberTriggered Mobility feature. Details of the license activation process can befound in License Management.

Information about configuration activities for Subscriber Triggered Mobilityfeature can be found in Radio Network.

19101/1553-HSC 105 50/1-V2 Uen C1 | 2011-12-09
toc1 Introduction1.1 Basic CharacteristicsDependencies1.2 Benefits1.3 Additional Information2 Feature Operation2.1 Network Requirements2.2 RFPM Operation Description2.3 ORC Operation Sequence Diagram3 Parameters3.1 Introduced Parameters3.2 Affected Parameters4 Network Impact4.1 Coverage4.2 Mobility5 Associated Features and Affected Functions5.1 Prerequisite Features5.2 Affected Features5.3 Related Features5.4 Affected System Functions6 Performance 6.1 KPIs6.2 Counters6.3 Events7 O&M Information

Subscriber Triggered Mobility.pdf

Documents

Transcript of Subscriber Triggered Mobility.pdf