Flexible User Steering (eRAN7.0 - 01)

eRAN
Flexible User Steering Feature

Parameter Description
Issue 01
Date 2014-04-26
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2014-04-26) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
Flexible User Steering Feature Parameter Description Contents
Contents
1 About This Document..................................................................................................................1

1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................2
1.4 Differences Between eNodeB Types..............................................................................................................................3
2 Overview.........................................................................................................................................5
2.1 Introduction....................................................................................................................................................................6
2.2 Benefits...........................................................................................................................................................................6
2.3 Usage Scenarios..............................................................................................................................................................6
3 SPID Principles..............................................................................................................................8
4 SPID-specific Flexible Service Policies...................................................................................10
4.1 Cell Reselection Policy(LOFD-00105401 Camp & Handover Based on SPID).........................................................12
4.2 Redirection Policy........................................................................................................................................................13
4.3 Load-based Handover Policy(LOFD-00105401 Camp & Handover Based on SPID)................................................14
4.4 DRX Policy...................................................................................................................................................................14
4.5 Preallocation Policy(LOFD-001059 UL Pre-allocation Based on SPID)....................................................................15
4.6 Handover back to the HPLMN Policy(LOFD-00105401 Camp & Handover Based on SPID)..................................15
4.7 Multi Operators SPID Policy........................................................................................................................................16
5 Related Features...........................................................................................................................17
5.1 Features Related to LOFD-00105401 Camp & Handover Based on SPID..................................................................17
5.2 Features Related to LOFD-001059 UL Pre-allocation Based on SPID.......................................................................18
5.3 Features Related to LOFD-070210 Multi Operators SPID Policy...............................................................................18
5.4 Features Related to SPID-specific Redirection Policies...............................................................................................18
5.5 Features Related to SPID-specific DRX Policies.........................................................................................................19
6 Network Impact...........................................................................................................................20
6.1 LOFD-00105401 Camp & Handover Based on SPID..................................................................................................20
6.2 LOFD-001059 UL Pre-allocation Based on SPID.......................................................................................................20
6.3 LOFD-070210 Multi Operators SPID Policy...............................................................................................................21
6.4 SPID-specific Redirection Policy.................................................................................................................................21
6.5 SPID-specific DRX Policy...........................................................................................................................................21
Issue 01 (2014-04-26) Huawei Proprietary and Confidential ii

eRAN
Flexible User Steering Feature Parameter Description Contents
7 Engineering Guidelines.............................................................................................................22
7.1 When to Use Flexible User Steering............................................................................................................................22
7.2 Required Information...................................................................................................................................................24
7.3 Planning........................................................................................................................................................................24
7.4 Deployment..................................................................................................................................................................24
7.4.1 Requirements.............................................................................................................................................................24
7.4.2 Data Preparation........................................................................................................................................................25
7.4.3 Precautions.................................................................................................................................................................36
7.4.4 Hardware Adjustment................................................................................................................................................36
7.4.5 Initial Configuration..................................................................................................................................................36
7.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs..................................................36
7.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs...............................................................41
7.4.5.3 Using the CME to Perform Single Configuration..................................................................................................42
7.4.5.4 Using MML Commands.........................................................................................................................................42
7.4.6 Activation Observation..............................................................................................................................................45
7.4.7 Reconfiguration.........................................................................................................................................................52
7.4.8 Deactivation...............................................................................................................................................................52
7.4.8.1 Using the CME to Perform Batch Configuration...................................................................................................52
7.4.8.2 Using the CME to Perform Single Configuration..................................................................................................53
7.4.8.3 Using MML Commands.........................................................................................................................................54
7.5 Performance Monitoring...............................................................................................................................................54
7.6 Parameter Optimization................................................................................................................................................55
7.7 Troubleshooting............................................................................................................................................................55
8 Parameters.....................................................................................................................................56
9 Counters........................................................................................................................................88
10 Glossary.......................................................................................................................................92
11 Reference Documents...............................................................................................................93
Issue 01 (2014-04-26) Huawei Proprietary and Confidential iii

eRAN
Flexible User Steering Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes flexible user steering, including its technical principles, related
features, network impact, and engineering guidelines. This document covers the following
features:
l LOFD-00105401 Camp & Handover Based on SPID

l LOFD-001059 UL Pre-allocation Based on SPID
l LOFD-070210 Multi Operators SPID Policy
This document applies to the following types of eNodeBs.
eNodeB Type Model
Macro 3900 series eNodeB
Micro BTS3202E and BTS3203E
LampSite DBS3900
Any managed objects (MOs), parameters, alarms, or counters described below correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with the latest software release.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and
"eNodeB" refers to LTE FDD eNodeB.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
Issue 01 (2014-04-26) Huawei Proprietary and Confidential 1

eRAN
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN7.0 01 (2014-04-26)
This issue does not include any changes.
eRAN7.0 Draft B (2014-03-07)

This issue includes the following changes.
Change Change Description Parameter Change

Type
Feature None None

change
Editorial Added 1.4 Differences Between None

change eNodeB Types
, which
describes differences in
feature support between
eNodeB types.
eRAN7.0 Draft A (2014-01-20)

Compared with Issue 03 (2013-10-30) of eRAN6.0, Draft A (2014-01-20) of eRAN7.0 includes
the following changes.

eRAN
Change Change Description Parameter Change

Type
Feature Added the following counters: None

change l L.HHO.InterFddTdd.RegainHP
LMN.PrepAttOut
l L.HHO.InterFddTdd.RegainHP
LMN.ExecAttOut
l L.HHO.InterFddTdd.RegainHP
LMN.ExecSuccOut
For details, see 7.5 Performance
Monitoring.
Editorial None None

change
1.4 Differences Between eNodeB Types

Feature Support by Macro, Micro,and LampSite eNodeBs
Feature ID Feature Name Supported by Supported by Supported by
Macro Micro LampSite
eNodeBs eNodeBs eNodeBs
LOFD-001054 Camp & Yes Yes Yes

01 Handover
Based on SPID
LOFD-001059 Pre-allocation Yes Yes Yes

UL Based on SPID
LOFD-070210 Multi Yes Yes Yes

Operators SPID
Policy

eRAN
Function Implementation in Macro, Micro,and LampSite eNodeBs

Function Difference
Parameter The GUI Value Range of this parameter between Macro and Micro are
CellAlgoSwitch. different:
MlbAlgoSwitch Macro parameter can be value of GeranMlbSwitch(GeranMlbSwitch)
but Micro Parameter can not be value of GeranMlbSwitch
(GeranMlbSwitch)
For details, see 7.4.2 Data Preparation and 7.4.5.4 Using MML
Commands

eRAN
Flexible User Steering Feature Parameter Description 2 Overview
2 Overview
By using subscriber profile IDs (SPIDs), flexible user steering enables operators to customize
policies for radio resource management (RRM) algorithms or functions such as camping of user
equipment (UEs) in idle mode, handovers of UEs in connected mode, discontinuous reception
(DRX), and uplink preallocation. Table 2-1 lists the features related to flexible user steering.
Table 2-1 Features related to flexible user steering
Feature Section
LOFD-00105401 Camp & Handover Based l "4.1 Cell Reselection Policy

on SPID (LOFD-00105401 Camp & Handover
Based on SPID)"
l "4.3 Load-based Handover Policy
(LOFD-00105401 Camp & Handover
Based on SPID)"
l "4.6 Handover back to the HPLMN
Policy(LOFD-00105401 Camp &
Handover Based on SPID)"
LOFD-001059 UL Pre-allocation Based on "4.5 Preallocation Policy(LOFD-001059

SPID UL Pre-allocation Based on SPID)"
LOFD-070210 Multi Operators SPID Policy 4.7 Multi Operators SPID Policy

eRAN
2.1 Introduction
Flexible user steering enables operators to classify users with different characteristics into
different groups and apply different RRM policies to improve user experience in these groups.
An operator registers SPIDs (index ranging from 1 to 256) for UEs in a home subscriber server
(HSS) database. An E-UTRAN NodeB (eNodeB) performs special processing for the services
of the UEs based on the SPIDs.
2.2 Benefits
This feature enables operators to provide flexible services, which improves user experience.
2.3 Usage Scenarios

Table 2-2 Typical usage scenarios
Sub-Feature Usage Scenario
4.1 Cell Reselection Policy l Operators require data-centric UEs (for

(LOFD-00105401 Camp & Handover example, those using data cards) to
Based on SPID) preferentially camp on high-band LTE
cells.
l Operators require voice-centric UEs to
preferentially camp on Global System for
Mobile Communications (GSM) cells,
Universal Mobile Telecommunications
System (UMTS) cells, or low-band LTE
cells.
4.2 Redirection Policy Operators require UEs to use the

preconfigured SPID-specific frequency
priorities to determine the target frequencies
for redirection.
4.3 Load-based Handover Policy Operators allow or do not allow UEs to

(LOFD-00105401 Camp & Handover initiate load-based inter-frequency or inter-
Based on SPID) RAT handovers. (RAT is short for radio
access technology.)

eRAN
Sub-Feature Usage Scenario
4.4 DRX Policy l Common DRX policies apply to UEs for

which low power consumption is
required.
l Special DRX policies apply to special
UEs. Special UEs require special DRX
parameters and special DRX policies.
UEs for which service latency takes
precedence over power consumption are
special UEs. Examples include data cards
and UEs with sufficient power supplies.
For details, see DRX and Signaling
Control Feature Parameter Description.
4.5 Preallocation Policy(LOFD-001059 UL Operators allow or do not allow UEs to be

Pre-allocation Based on SPID) preallocated resources.
Preallocation algorithms apply to scenarios
with low uplink loads and can reduce end-to-
end service latency. Resources cannot be
preallocated in scenarios with high uplink
loads. Preallocation reduces the probability
that UEs enter the DRX state and shortens UE
standby time. However, preallocation
increases interference to neighboring cells.
For details, see Scheduling Feature
Parameter Description.
4.6 Handover back to the HPLMN Policy Operator A applies the SPID-specific
(LOFD-00105401 Camp & Handover handover back to the HPLMN policy to UEs
Based on SPID) of operator B if operator B desires its UEs to
be promptly handed back over to their home
public land mobile network (HPLMN) when
the UEs are roaming back to the HPLMN
range.
4.7 Multi Operators SPID Policy see RAN Sharing Feature Parameter
Description

eRAN
Flexible User Steering Feature Parameter Description 3 SPID Principles
3 SPID Principles
SPIDs are service policy indexes predefined by operators for UEs. Operators create the mapping
between UEs and SPIDs during UE registration and modify the mapping when service policies
change. The Spid parameter defines an SPID. Figure 3-1 shows the process of transferring an
SPID on the entire network.
Figure 3-1 Process of transferring an SPID on the entire network
Based on service characteristics and UE behaviors, operators can define different service policies
for different UEs to improve network performance and efficiency.

eRAN
Flexible User Steering Feature Parameter Description 3 SPID Principles
On operator's networks, network elements (NEs) implement service policies based on SPIDs.
SPIDs are transmitted as follows:
l The eNodeB obtains the SPID from the INITIAL CONTEXT SETUP REQUEST, UE
CONTEXT MODIFICATION REQUEST, or Downlink NAS Transport message sent by
the MME over the S1 interface.
l During an S1-based handover, the target eNodeB obtains the SPID from the information
element (IE) Source eNB to Target eNB Transparent Container in the HANDOVER
REQUIRED or HANDOVER REQUEST message sent by the source eNodeB.
l During an X2-based handover, the target eNodeB obtains the SPID from the HANDOVER
REQUEST message sent by the source eNodeB.
Each SPID identifies a unique service policy on operator networks. Operators, eNodeBs, and
evolved packet core (EPC) entities such as the HSS and mobility management entity (MME)
use the same SPID definitions so that operator-defined policies are correctly transferred on the
networks.
As shown in Figure 3-1, after operators define service policies for UEs in their networks, SPID
definitions are synchronized between NEs in the following ways:
l On the HSS, the operation and maintenance (OM) personnel of operators configure the
SPID for each service policy applied to each UE.
l On the eNodeB, the OM personnel of operators configure SPIDs and associated service
policies.
l The eNodeB applies obtained SPID-specific service policies to UEs on which services are
running.

eRAN
Flexible User Steering Feature Parameter Description 4 SPID-specific Flexible Service Policies
4 SPID-specific Flexible Service Policies
By assigning SPIDs, operators can flexibly define service polices for UEs. Each service policy
includes the following policies:
l Cell reselection
l Redirection
l Load-based handover
l DRX
l Preallocation
l Handover back to the HPLMN
Table 4-1 provides examples of UE service policies.
Table 4-1 Examples of UE service policies
UE Parameter and Setting
SpidCf SpidCf SpidCf SpidCf SpidCf SpidCf SpidCf SpidCf

g.Spid g. g. g. g. g. g. g.
RatFre RatFre DrxSta Preallo InterFr InterR HoBac
qPriori qPriori tus cationS eqMlbS atMlbS kToHP
tyInd tyGrou tatus witch witch LMNS
pId witch
1 1 CFG 1 TRUE FALSE FALSE TRUE FALSE

(CFG) (TRUE (FALS (FALS (TRUE (FALS
) E) E) ) E)
2 2 NOT_ N/A FALSE TRUE TRUE TRUE TRUE

CFG (FALS (TRUE (TRUE (TRUE (TRUE
(NOT_ E) ) ) ) )
CFG)
3 3 NOT_ N/A FALSE TRUE TRUE FALSE TRUE

CFG (FALS (TRUE (TRUE (FALS (TRUE
(NOT_ E) ) ) E) )
CFG)

eRAN
4 4 CFG 2 TRUE TRUE FALSE FALSE FALSE

(CFG) (TRUE (TRUE (FALS (FALS (FALS
) ) E) E) E)
5 5 CFG 4 ... ... ... ... ...

(CFG)
... ... CFG ... ... ... ... ... ...

(CFG)
... 256 CFG 255 ... ... ... ... ...

(CFG)

eRAN
4.1 Cell Reselection Policy(LOFD-00105401 Camp &

Handover Based on SPID)
A cell reselection policy defines whether UEs preferentially camp on a cell under a specified
frequency of the following networks:
l GSM/EDGE radio access network (GERAN), where EDGE is short for Enhanced Data
rates for GSM Evolution
l UMTS terrestrial radio access network (UTRAN)
l Evolved UTRAN (E-UTRAN)
Operator can define SPID-specific cell reselection policies for UEs as follows:
l UEs do not preferentially camp on a cell under a special policy.

l Different UEs preferentially camp on cells under specified frequencies of the GERAN,
UTRAN, and E-UTRAN.
The SpidCfg.Spid and SpidCfg.RatFreqPriorityInd parameters specify whether UEs with the
specific SPID are allowed to preferentially camp on a specified frequency based on SPIDs.
l If the SpidCfg.RatFreqPriorityInd parameter is set to CFG(CFG), the UEs are allowed

to preferentially camp on the specified frequency.
l If the SpidCfg.RatFreqPriorityInd parameter is set to NOT_CFG(NOT_CFG), the UEs
are not allowed to preferentially camp on a specific frequency.
The RatFreqPriorityGroup.RatFreqPriorityGroupId, RatFreqPriorityGroup.RatType,

RatFreqPriorityGroup.DlEarfcn, RatFreqPriorityGroup.Priority, and
RatFreqPriorityGroup.BandIndicator parameters specify a frequency on which UEs are
allowed to preferentially camp. Each RatFreqPriorityGroup.RatFreqPriorityGroupId
parameter maps to a group of frequency priorities. The RatFreqPriorityGroup.Priority
parameter specifies the cell priorities for cell selection, reselection, and redirection of UEs in
idle mode.
Table 4-2 provides examples of frequency priorities.
Table 4-2 Examples of frequency priorities
RatFreqPriori- RatFreqPriori- RatFreqPriori- RatFreqPriori- RatFreqPriori-

tyGroup. tyGroup. tyGroup. tyGroup. tyGroup.
RatFreqPriorit RatType DlEarfcn Priority BandIndicator
yGroupId
1 EUTRAN F1 7 N/A
1 EUTRAN F2 6 N/A
1 UTRAN F3 4 N/A
1 GERAN F4 1 GSM_dcs1800
2 EUTRAN F1 0 N/A

eRAN
2 EUTRAN F2 1 N/A
2 UTRAN F3 7 N/A
2 GERAN F4 6 GSM_pcs1900
... ... ... ... ...

NOTE
F1 to F4 in this table are not parameter values but variables that represent different frequencies.
It is recommended that the frequency priority ranges configured for different RATs in
RatFreqPriorityGroup MOs not overlap within a frequency priority group. Reserve some
frequency priorities between the ranges to prevent a range overlap that may occur when a
frequency is added.
The eNodeB transmits neighboring cell priorities to UEs using the

IdleModeMobilityControlInfo IE in an RRC Connection Release message. For details, see Idle
Mode Management Feature Parameter Description.
According to 3GPP TS 36.304 V9.8.0 (2011-10), the RatFreqPriorityGroup.DlEarfcn

parameter in Table 4-2 must be configured and broadcast in system information block type 5
(SIB5), SIB6, SIB7 or SIB8. Otherwise, the frequency whose priority is delivered in an RRC
Connection Release message will not be selected as the target frequency for cell reselection.
4.2 Redirection Policy

A redirection policy defines whether the eNodeB uses the preconfigured SPID-specific
frequency priorities to determine the target frequencies for redirection when UEs are to be
normally released because of load control or S1 interface faults.
If the eNodeB uses the priorities, it selects a frequency of a RAT (except the serving frequency)
with the highest priority for a UE based on the UE capabilities and SPID definition. The eNodeB
then delivers the target frequency to the UE in an RRC Connection Release message as follows:
l If the priority of the target frequency is higher than or equal to that of the serving frequency,
the eNodeB delivers the target frequency in the RedirectedCarrierInfo IE and the frequency
priority group in the IdleModeMobilityControlInfo IE to the UE.
l If the serving frequency is the frequency with the highest priority (f1) defined by the
RatFreqPriorityGroup.Priority parameter, the eNodeB delivers the frequency with the
second highest priority (f2) in the RedirectedCarrierInfo IE to the UE. Meanwhile, the
eNodeB interchanges priorities of f1 and f2 and delivers the modified values of the
RatFreqPriorityGroup.Priority parameters in the IdleModeMobilityControlInfo IE to the
UE.
NOTE
Currently, eNodeBs support redirection to E-UTRAN, UTRAN, or GERAN cells but not CDMA2000
cells.

eRAN
4.3 Load-based Handover Policy(LOFD-00105401 Camp &

Handover Based on SPID)
A load-based handover policy defines whether UEs support load-based inter-frequency and
inter-RAT handovers. In an SPID configuration:
l The SpidCfg.Spid and SpidCfg.InterFreqMlbSwitch parameters specify whether UEs

support load-based inter-frequency handovers.
l The SpidCfg.Spid and SpidCfg.InterRatMlbSwitch parameters specify whether UEs
support load-based inter-RAT handovers.
Load-based handover policies are implemented as follows:
l When the InterFreqMlbSwitch option of the CellAlgoSwitch.MlbAlgoSwitch parameter

is selected,
– If the SpidCfg.InterFreqMlbSwitch parameter is set to TRUE(TRUE), load-based
inter-frequency handovers can be performed on the UEs with this SPID.
– If the SpidCfg.InterFreqMlbSwitch parameter is set to FALSE(FALSE), load-based
inter-frequency handovers cannot be performed on the UEs with this SPID.
l When the InterFreqMlbSwitch option of the CellAlgoSwitch.MlbAlgoSwitch parameter
is not selected, load-based inter-frequency handover policies for UEs do not take effect in
the cell.
l Macro:When the UtranMlbSwitch or GeranMlbSwitch option of the
CellAlgoSwitch.MlbAlgoSwitch parameter is selected,
– If the SpidCfg.InterRatMlbSwitch parameter is set to TRUE(TRUE), load-based
inter-RAT handovers can be performed on the UEs with this SPID.
– If the SpidCfg.InterRatMlbSwitch parameter is set to FALSE(FALSE), load-based
inter-RAT handovers cannot be performed on the UEs with this SPID.
l Micro:When the UtranMlbSwitch option of the CellAlgoSwitch.MlbAlgoSwitch
(UtranMlbSwitch)parameter is selected,
– If the SpidCfg.InterRatMlbSwitch parameter is set to TRUE(TRUE), load-based
inter-RAT handovers can be performed on the UEs with this SPID.
– If the SpidCfg.InterRatMlbSwitch parameter is set to FALSE(FALSE), load-based
inter-RAT handovers cannot be performed on the UEs with this SPID.
l When neither UtranMlbSwitch nor GeranMlbSwitch under the
CellAlgoSwitch.MlbAlgoSwitch parameter is selected, load-based inter-RAT handover
policies for UEs do not take effect in the cell.
For details about load-based inter-frequency and inter-RAT handovers, see Mobility
Management in Connected Mode Feature Parameter Description and MLB Feature Parameter
Description.
4.4 DRX Policy

SPID-specific DRX policies are classified into common and special DRX policies, which are
described as follows:

eRAN
l Common DRX policies apply to UEs for which low power consumption is required. In
common DRX policies, UEs run DRX based on the configured common DRX parameters.
l Special DRX policies apply to special UEs. In special DRX policies, UEs run DRX based
on the configured special DRX parameters.
The SpidCfg.Spid and SpidCfg.DrxStatus parameters specify a DRX policy for UEs with a
specific SPID. The DRX policy takes effect when the Drx.DrxAlgSwitch parameter is set to
ON(On). For details about DRX policies, see DRX and Signaling Control Feature Parameter
Description.
4.5 Preallocation Policy(LOFD-001059 UL Pre-allocation

Based on SPID)
A preallocation policy defines whether the eNodeB, based on uplink loads, reserves resources
for UEs that require short delays.
The SpidCfg.Spid and SpidCfg.PreallocationStatus parameters specify whether to apply

preallocation to UEs with a specific SPID.
Preallocation policies are implemented as follows:
l When the PreAllocationSwitch option of the CellAlgoSwitch.UlSchSwitch parameter is

selected,
– If the SpidCfg.PreallocationStatus parameter is set to TRUE(TRUE), UEs can be
preallocated resources.
– If the SpidCfg.PreallocationStatus parameter is set to FALSE(FALSE), UEs cannot
be preallocated resources.
l When the PreAllocationSwitch option of the CellAlgoSwitch.UlSchSwitch parameter is
not selected, preallocation policies do not take effect in the cell.
For details about preallocation, see Scheduling Feature Parameter Description.
4.6 Handover back to the HPLMN Policy(LOFD-00105401

Camp & Handover Based on SPID)
A handover back to the HPLMN policy defines whether a UE can be handed over from another
PLMN to its HPLMN when it moves back to the E-UTRAN of its HPLMN.
The SpidCfg.HoBackToHPLMNSwitch parameter specifies whether handover back to the

HPLMN is allowed for UEs with a specific SPID.
Handover back to the HPLMN takes effect for a UE only when all the following conditions are
met:
l The SpidCfg.HoBackToHPLMNSwitch parameter is set to TRUE(TRUE) for the SPID

of the UE.
l Among the frequency priorities specified by the RatFreqPriorityGroup.Priority
parameter in the priority group for the SPID, there are frequencies whose priorities are

eRAN
higher than that of the serving frequency, and the cells on the higher-priority frequencies
belong to different PLMNs from the PLMN of the serving cell.
l The InterPlmnHoSwitch option of the ENodeBAlgoSwitch.HoAlgoSwitch parameter is
selected. In addition, the eNodeB adds the HPLMN of the UE to the inter-PLMN handover
list, or the MME configures the HPLMN of the UE as an equivalent PLMN (EPLMN).
Currently, handover back to the HPLMN policies apply only when the HPLMN is an LTE or
UMTS network. If the HPLMN of a UE is a GSM/EDGE or CDMA2000 network, the UE cannot
be handed back over to its HPLMN.
For details about the handover procedure, see Mobility Management in Connected Mode Feature
Parameter Description.
4.7 Multi Operators SPID Policy

SPID configurations can be set per operator if the LOFD-001080 Multi Operators SPID Policy
feature is activated.
For details about this feature, see RAN Sharing Feature Parameter Description.

eRAN
Flexible User Steering Feature Parameter Description 5 Related Features
5 Related Features
5.1 Features Related to LOFD-00105401 Camp & Handover

Based on SPID
Prerequisite Features
SPID-specific cell reselection policies require the LBFD-00201803 Cell Selection and Re-
selection feature.
SPID-specific load-based handover policies require one of the following features:
l LOFD-001032 Intra-LTE Load Balancing

l LOFD-001044 Inter-RAT Load Sharing to UTRAN
l LOFD-001045 Inter-RAT Load Sharing to GERAN
SPID-specific handover back to the HPLMN policies require one of the following features:
l LBFD-00201802 Coverage Based Inter-frequency Handover

l LOFD-001019 PS Inter-RAT Mobility between E-UTRAN and UTRAN
Mutually Exclusive Features

None
Impacted Features
None

eRAN
5.2 Features Related to LOFD-001059 UL Pre-allocation

Based on SPID
UL Pre-allocation Based on SPID requires the LBFD-002025 Basic Scheduling feature and the
cell-level UL preallocation function that is controlled by PreAllocationSwitch under the
CellAlgoSwitch.UlSchSwitch parameter.

None
Impacted Features
None
5.3 Features Related to LOFD-070210 Multi Operators SPID

Policy
For details about the related features, see RAN Sharing Feature Parameter Description.
5.4 Features Related to SPID-specific Redirection Policies

In load control scenarios, SPID-specific redirection policies require the following feature and
function:
l LBFD-002024 Congestion Control feature

l Load-based redirection that is controlled by LoadBasedSwitch under the
ENodeBAlgoSwitch.RedirectSwitch parameter.
In S1 fault scenarios, SPID-specific redirection policies do not require other features or

functions.

None
Impacted Features
None

eRAN
5.5 Features Related to SPID-specific DRX Policies

SPID-specific DRX policies require the LBFD-002017 DRX feature.

None
Impacted Features
None

eRAN
Flexible User Steering Feature Parameter Description 6 Network Impact
6 Network Impact
6.1 LOFD-00105401 Camp & Handover Based on SPID

System Capacity
No impact.
Network Performance
SPID-specific cell reselection policies can reduce the probability of inter-RAT handovers or
redirections and increase the inter-RAT handover success rate.
For example, operators usually require UEs to preferentially camp on E-UTRAN cells. In an
early phase of LTE network deployment, the LTE network does not support voice over IP (VoIP)
services over the IP Multimedia Subsystem (IMS). Each time a UE needs to make or receive a
voice call, the eNodeB has to instruct the UE to fall back to a UTRAN or GERAN. After the
call, the UE performs a cell reselection by using a common cell reselection policy to return to
the E-UTRAN. If the operators use SPID configurations to enable voice-centric UEs to
preferentially camp on UMTS or GSM cells, the UEs can make or receive voice calls directly
in the UTRAN or GERAN. This reduces the number of times circuit switched fallback (CSFB)
to UTRAN or GERAN is triggered.
6.2 LOFD-001059 UL Pre-allocation Based on SPID

System Capacity
No impact.
Network Performance
If UL Pre-allocation Based on SPID is used to disable uplink preallocation for UEs that mainly
perform delay-insensitive services in a cell, uplink RB usage by these UEs and their power
consumption decrease.

eRAN
Flexible User Steering Feature Parameter Description 6 Network Impact
6.3 LOFD-070210 Multi Operators SPID Policy

No impact.
6.4 SPID-specific Redirection Policy

System Capacity
No impact.
Network Performance
If redirection for load control is disabled in a network, SPID-specific redirection policies reduce
the service drop rate.
If redirection for load control is enabled in a network, SPID-specific redirection policies do not
affect network performance.
6.5 SPID-specific DRX Policy

System Capacity
No impact.
Network Performance
Both SPID-specific DRX and DRX for RRC_CONNECTED UEs must be enabled to implement
flexible user steering. If SPID-specific DRX is enabled together with DRX for
RRC_CONNECTED UEs, the overall impact on network performance is the same as the impact
of DRX for RRC_CONNECTED UEs. For details, see the impact of LBFD-002017 DRX
described in DRX and Signaling Control Feature Parameter Description.
If DRX for RRC_CONNECTED UEs is enabled before SPID-specific DRX, enabling SPID-
specific DRX does not affect network performance.

eRAN
Flexible User Steering Feature Parameter Description 7 Engineering Guidelines
7 Engineering Guidelines
7.1 When to Use Flexible User Steering

Cell Reselection Policy
Customize cell reselection policies for different SPIDs if operators intend to achieve the
following effects:
l Data-centric UEs, such as those using data cards, preferentially camp on high-band E-
UTRAN cells.
l Voice-centric UEs preferentially camp on GERAN cells, UTRAN cells, or low-band E-
UTRAN cells.
If one or more frequencies in the frequency priority group configured for an SPID are used in a
different PLMN (PLMN A) than the frequency on which an E-UTRAN cell operates, PLMN A
must be configured as an equivalent PLMN (EPLMN) for all the UEs with the SPID on the
MME. If PLMN A is not configured as an EPLMN, the policy of cell reselection to those
frequencies does not take effect.
Redirection Policy
Enable redirection for an SPID for operators that desire UEs with the SPID to be preferentially
redirected to cells on specified frequencies when the UEs are released because of load control
or S1 interface faults.
NOTE
SPID-specific cell reselection and redirection policies are controlled by the same switch, which is specified
by the SpidCfg.RatFreqPriorityInd parameter.
Load-based Handover Policy

Enable load-based handover for an SPID for operators that desire UEs with the SPID to initiate
load-based inter-frequency or load-based inter-RAT handovers.

eRAN
DRX Policy
Use SPID-specific DRX policies for operators that expect to meet power-efficiency or latency
requirements of UEs.
Preallocation Policy
Enable preallocation for an SPID if UEs with the SPID have high requirements for end-to-end
latency, such as high-priority UEs, or have low requirements for power-efficiency, such as data
cards.
Disable preallocation for an SPID if the UEs with the SPID require long standby time.
Handover back to the HPLMN Policy

In the following scenario, operator B provides LTE coverage for the entire network and operator
A provides coverage for a part of the network. Generally, when a UE that subscribes to operator
A moves out of its HPLMN (that is, operator A's E-UTRAN), the roaming function enables the
UE to access operator B's E-UTRAN.
On the operator B's eNodeB, enable the handover back to the HPLMN function for the SPID of
the UE so that the operator A's eNodeB can hand over the UE back to its HPLMN when the UE
moves back to its HPLMN range.
The following provides important information about such a handover:
l The prerequisites for such a handover are as follows:

– The SpidCfg.HoBackToHPLMNSwitch parameter is set to TRUE(TRUE).
– The configured RatFreqPriorityGroup MO for the SPID for the UE has specified
frequencies that have higher priorities than the serving frequency.
– At least one neighboring cell on a higher-priority frequency has a different PLMN ID
than the serving cell.
l A UE can perform such a handover only if its HPLMN is an LTE or UMTS network.
l After such a handover triggers inter-frequency or inter-RAT measurements, the
measurement configuration, handover decision, and handover execution processes are the
same as an inter-frequency or inter-RAT handover.
l In RAN sharing scenarios, if the frequency with the highest priority according to the SPID
for a UE is shared by multiple PLMNs and one of these PLMNs is the same as one of the
PLMNs of the serving cell, the eNodeB does not use the SPID-specific handover back to
the HPLMN policy for the UE.
Such a handover is an inter-PLMN handover. For details about how to configure inter-PLMN
handover, see Mobility Management in Connected Mode Feature Parameter Description.
It is recommended that the frequency priorities of operator A's E-UTRAN or UTRAN cells be
configured higher than the frequency priority of the serving cell of operator B.
Multi Operators SPID Policy

For details about how to deploy this feature, see RAN Sharing Feature Parameter Description.

eRAN
7.2 Required Information

This section describes how to collect the information required for flexible user steering.
Step 1 Check whether the HSS supports RAT/frequency selection priority (RFSP) configuration and
whether the MME can transfer and modify the RFSP configurations.
l If yes, go to Step 2.
l If no, upgrade the HSS and MME to support RFSP.
NOTE
SPID is referred to as RFSP in the PC.
Step 2 Confirm the mapping between SPID values and the following factors: UE characteristics, various
policies, and frequency priorities.
Step 3 (Optional) Configure SPID-specific policies for roaming UEs.
----End
7.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
7.4 Deployment
7.4.1 Requirements
Operating Environment
l SPIDs can be configured on the MME, and the SPID configurations on the MME are the
same as those on eNodeBs.
l The mapping between UEs and SPIDs has been configured on the HSS based on the service
policies.
l The EPC version is SAE 1.2 or later if the EPC is provided by Huawei.
Transmission Networking
N/A

eRAN
License
Table 7-1 License information for flexible user steering
Feature ID Feature Name License NE Sales Unit

Control Item
LOFD-001059 UL Pre- UL Pre- eNodeB per RRC

allocation allocation Connected User
Based on SPID Based on SPID
LOFD- 001054 Flexible User Flexible User eNodeB per RRC

Steering Steering Connected User
LOFD-070210 Multi Operators Multi Operators eNodeB per cell

SPID Policy SPID Policy
(FDD)
Other Requirements
The existing LTE network supports intra- or inter-RAT handovers and cell reselections. For
details, see Idle Mode Management Feature Parameter Description and Mobility Management
in Connected Mode Feature Parameter Description.
7.4.2 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is
data that you must collect for all scenarios. Collect scenario-specific data when necessary for a
specific feature deployment scenario.
There are three types of data sources:
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l Network plan (negotiation not required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Required Data
The following table describes the parameter that must be set in an SPIDCFG MO to define an
SPID.
Parameter Name Parameter ID Data Source Setting Notes
Spid SpidCfg.Spid Network plan Set this parameter to

(negotiation not the SPID
required) corresponding to a
service policy.

eRAN
Scenario-specific Data
The following table describes the parameters that must be set in an SPIDCFG MO to configure
an SPID-specific cell reselection policy.
RAT frequency SpidCfg. Network plan This parameter

priority indication RatFreqPriorityInd (negotiation not specifies whether to
required) configure a
frequency priority
group.
l If UEs with this
SPID are
expected to use a
specific cell
reselection
policy, set this
parameter to
CFG(CFG).
l Otherwise, set
this parameter to
NOT_CFG
(NOT_CFG).
RAT frequency SpidCfg. Network plan This parameter

priority group ID RatFreqPriority- (negotiation not identifies a
GroupId required) frequency priority
group. Set this
parameter to the
SpidCfg.
RatFreqPriority-
GroupId value in the
corresponding
RatFreqPriori-
tyGroup MO.
The following table describes the parameters that must be set in a

RATFREQPRIORITYGROUP MO to configure a frequency priority group.
RAT frequency RatFreqPriori- Network plan This parameter

priority group ID tyGroup. (negotiation not specifies the ID of
RatFreqPriority- required) this group.
GroupId

eRAN
RAT Type RatFreqPriori- Network plan This parameter

tyGroup.RatType (negotiation not specifies the RAT.
required)
DL Earfcn or RatFreqPriori- Network plan This parameter

Bandclass tyGroup.DlEarfcn (negotiation not specifies a downlink
required) frequency or band
class. UEs with the
associated SPID can
apply cell reselection
to the frequency or
band class identified
by this parameter.
Priority RatFreqPriori- Network plan This parameter

tyGroup.Priority (negotiation not specifies the cell
required) reselection priority
for the frequency or
band class specified
by the DlEarfcn
parameter.
Set this parameter to
a value within the
range of 0 to 7.
GERAN Frequency RatFreqPriori- Network plan This parameter

Indicator tyGroup. (negotiation not specifies a GERAN
BandIndicator required) band and is valid
only when the
RatType parameter is
set to GERAN.
Redirection Policy
The parameters to be configured are the same as those for the SPID-specific cell reselection
policy.
an SPID-specific load-based handover policy.

eRAN
InterFreq Mlb SpidCfg. Network plan l To enable inter-

Switch InterFreqMlbS- (negotiation not frequency load
witch required) balancing for UEs
with the SPID, set
this parameter to
TRUE(TRUE).
l To disable inter-
frequency load
balancing for UEs
with AN SPID,
set this parameter
to FALSE
(FALSE).
InterRat Mlb Switch SpidCfg. Network plan l To enable inter-

InterRatMlbSwitch (negotiation not RAT load sharing
required) for UEs with the
SPID, set this
parameter to
TRUE(TRUE).
l To disable inter-
RAT load sharing
for UEs with the
SPID, set this
parameter to
FALSE
(FALSE).
The parameters that must be set in a RATFREQPRIORITYGROUP MO to configure a

frequency priority group are the same as those to be set for configuring an SPID-specific cell
reselection policy.
The following table describes the parameters that must be set in a CELLALGOSWITCH MO
to configure a cell-level load-based handover policy.
Local cell ID CellAlgoSwitch. Network plan This parameter

LocalCellId (negotiation not specifies the local
required) cell ID. It uniquely
identifies a cell
within an eNodeB.

eRAN
Load balancing CellAlgoSwitch. Network plan This parameter

algorithm switch MlbAlgoSwitch (negotiation not specifies whether to
required) enable MLB for the
cell.
l To enable inter-
frequency MLB,
select the
InterFreqMlbS-
witch
(InterFreqMlbS
witch) check box.
To disable inter-
frequency MLB,
clear the check
box.
l To enable load
sharing with
UTRAN, select
the
UtranMlbSwitc
h
(UtranMlbSwitc
h) check box. To
disable load
sharing with
UTRAN, clear
the check box.
l To enable load
sharing with
GERAN, select
the
GeranMlbSwitc
h
(GeranMlbSwit
ch) check box. To
disable load
sharing with
GERAN, clear
the check
box.This Switch
apply only to
Macro.
DRX Policy
an SPID-specific DRX policy.

eRAN
Drx status SpidCfg.DrxStatus Network plan This parameter

(negotiation not specifies whether to
required) apply common or
special DRX
parameters to UEs
with an SPID.
l To apply
common DRX
parameters to
UEs with the
SPID, set this
parameter to
TRUE(TRUE).
l To apply special
DRX parameters
to UEs with the
SPID, set this
parameter to
FALSE
(FALSE).
The following table describes the eNodeB-level parameters that must be set in the DRX MO.
DRX switch Drx.DrxAlgSwitch Network plan To enable DRX for

(negotiation not the eNodeB, set this
required) parameter to ON
(On).
Short-cycle DRX Drx. Network plan To enable short DRX

switch ShortDrxSwitch (negotiation not cycles for the
required) eNodeB, set this
parameter to ON
(On).

eRAN
Special long DRX Drx. Network plan This parameter

cycle LongDrxCycleSpe- (negotiation not specifies the length
cial required) of a long DRX cycle
that applies only to
non-power-saving
UEs. The UEs'
SPIDs for RFSP
indexes are
contained in the
RFSP index set.
The value SF10(10
subframes) is
recommended.
Special On Duration Drx. Network plan This parameter

timer OnDurationTimer- (negotiation not specifies the length
Special required) of the On Duration
Timer that applies
only to non-power-
saving UEs whose
RFSP indexes are
contained in the
RFSP index set.
A larger parameter
value results in a
longer active time, a
shorter delay, but
more power
consumption. A
smaller value has the
opposite effect.
The value
is recommended.
Special DRX Drx. Network plan This parameter

inactivity timer DrxInactivityTimer- (negotiation not specifies the length
Special required) of the DRX
Inactivity Timer that
applies only to non-
power-saving UEs
whose RFSP indexes
are contained in the
RFSP index set.
The value
is recommended.

eRAN
Special short-cycle Drx. Network plan This parameter

DRX supported SupportShortDrx- (negotiation not specifies whether to
indication Special required) enable or disable
short DRX cycles for
non-power-saving
UEs whose RFSP
indexes are
contained in the
RFSP index set.
The value
UU_DISABLE
(Disable) is
recommended.
Special short DRX Drx. Network plan This parameter

cycle ShortDrxCycleSpe- (negotiation not specifies the length
cial required) of a short DRX cycle
that applies only to
non-power-saving
UEs whose RFSP
indexes are
contained in the
RFSP index set.
The value SF10(10
subframes) is
recommended.
Special DRX short Drx. Network plan This parameter

cycle timer DrxShortCycleTi- (negotiation not specifies the length
merSpecial required) of the DRX Short
Cycle Timer that
applies only to non-
power-saving UEs
whose RFSP indexes
are contained in the
RFSP index set.
The value 1 is
recommended.
The following table describes the cell-level parameters that must be set in a
CELLDRXPARA MO.

eRAN
Local cell ID Cell.LocalCellId Network plan This parameter

(negotiation not specifies the local ID
required) of a cell. It uniquely
identifies a cell
within an eNodeB.
FDD enter DRX CellDrxPara. Network plan This parameter

threshold FddEnterDrxThd (negotiation not specifies the
required) threshold for UEs in
an FDD cell to enter
the DRX state.
The frequency at
which such UEs
enter the DRX state
is proportional to the
value set for this
parameter.
FDD exit DRX CellDrxPara. Network plan This parameter

threshold FddExitDrxThd (negotiation not specifies the
required) threshold for UEs in
an FDD cell to exit
the DRX state.
The frequency at
which such UEs exit
the DRX state is
inversely
proportional to the
value set for this
parameter.
Data amount Statistic CellDrxPara. Network plan This parameter

timer DataAmountStat- (negotiation not specifies the length
Timer required) of the UE traffic
measurement period.
The DRX algorithm
determines whether a
UE should exit or
enter the DRX state
based on the UE
traffic volume
measured during this
period.
The following table describes the parameter that must be set in an SPIDCFG MO to configure
an SPID-specific preallocation policy.

eRAN
PreallocationStatus SpidCfg. Network plan This parameter

PreallocationStatus (negotiation not specifies whether to
required) enable preallocation.
l To enable
preallocation for
UEs with an
SPID, set this
parameter to
TRUE(TRUE).
l To disable
preallocation for
UEs with the
SPID, set this
parameter to
FALSE
(FALSE).
This parameter is
valid only when
the
PreAllocationS-
witch option
under the
CellAlgoSwitch
.UlSchSwitch
parameter is
selected. By
default, the
PreAllocationS-
witch option is
selected.
To use SPID-specific handover back to the HPLMN, ensure that all the frequencies configured
with higher priorities than the serving frequency in the SPID-specific cell reselection policy of
a UE belong to the HPLMN of this UE.
By default, an inter-PLMN handover is supported on operator networks and related parameters

have been configured.
The following table describes the parameter that must be set in the SPIDCFG MO to configure
an SPID-specific handover back to the HPLMN policy.

eRAN
SPID-based SpidCfg. Network plan This parameter

Handover Back To HoBackToHPLMN (negotiation not specifies whether to
HPLMN Switch Switch required) enable handovers
back to the HPLMN
for UEs with an
SPID.
l To enable a
roaming UE to be
handed back over
to its HPLMN
when the UE
moves back to the
HPLMN, set this
parameter to
TRUE(TRUE).
l To disable a
roaming UE to be
handed back over
to its HPLMN
when the UE
moves back to the
HPLMN, set this
parameter to
FALSE
(FALSE).
The following table describes the parameter that must be set in an

ENODEBALGOSWITCH MO to configure an eNodeB-level inter-PLMN handover policy.
Handover Algo ENodeBAlgoSwitc Network plan Select the

switch h.HoAlgoSwitch (negotiation not InterPlmnHoS-
required) witch
(InterPlmnHoS-
witch) check box
under this parameter.
The following table describes the parameters that must be set in an INTERPLMNHOLIST
MO for inter-PLMN handovers.

eRAN
CN Operator ID CnOperator. Network plan This parameter

CnOperatorId (negotiation not specifies the operator
required) ID.
Target Mobile InterPlmnHoList. Network plan This parameter

country code TarMcc (negotiation not indicates the mobile
required) country code (MCC)
of the target PLMN.
Target Mobile InterPlmnHoList. Network plan This parameter

network code TarMnc (negotiation not indicates the mobile
required) network code (MNC)
of the target PLMN.
7.4.3 Precautions
None
7.4.4 Hardware Adjustment

N/A
7.4.5 Initial Configuration
7.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed
eNodeBs
Enter the values of the parameters listed in Table 7-2 to Table 7-6 in a summary data file, which
also contains other data for the new eNodeBs to be deployed. Then, import the summary data
file into the Configuration Management Express (CME) for batch configuration. For detailed
instructions, see section "Creating eNodeBs in Batches" in the initial configuration guide for the
eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
l The managed objects (MOs) in Table 7-2 to Table 7-6 are contained in a scenario-specific
summary data file. In this situation, set the parameters in the MOs, and then verify and save
the file.
l Some MOs in Table 7-2 to Table 7-6 are not contained in a scenario-specific summary
data file. In this situation, customize a summary data file to include the MOs before you
can set the parameters.
SPID-specific Cell Reselection Policy

eRAN
Table 7-2 Parameters related to an SPID-specific cell reselection policy
MO Sheet in the Parameter Group Remarks

Summary Data
File
SpidCfg SpidCfg Spid, RAT frequency The parameter group

priority indication, must be customized
RAT frequency on a list-type sheet.
priority group ID
RatfreqPriori- RATFREQPRIORI- RAT frequency The parameter group

tyGroup TYGROUP priority group ID, must be customized
RAT Type, on a list-type sheet.
Downlink EARFCN,
Priority, GERAN
Frequency Indicator
SPID-specific Redirection Policy
The recommended MO distribution is the same as that for the SPID-specific cell reselection
policy.
SPID-specific Load-based Handover Policy
NOTE
The SPID-specific load-based handover policy applies only to UEs that access the cell after delivery of the
SPID-specific parameter settings.
Table 7-3 Parameters related to an SPID-specific load-based handover policy

Summary Data
File
SPIDCFG SPIDCFG Spid, RAT frequency The parameter group

priority indication, must be customized
RAT frequency on a list-type sheet.
priority group ID,
InterFreq Mlb
Switch, InterRat Mlb
Switch
RATFREQPRIORI- RATFREQPRIORI- RAT frequency The parameter group

TYGROUP TYGROUP priority group ID, must be customized
Downlink EARFCN,
Priority, GERAN
Frequency Indicator

eRAN

Summary Data
File
CELLALGOSWITC CELLALGOSWITC Local cell ID, Load The parameter group

H H balancing algorithm must be customized
switch on a list-type sheet.
SPID-specific DRX Policy
Table 7-4 Parameters related to an SPID-specific DRX policy

Summary Data
File
SpidCfg SpidCfg Spid, Drx status The parameter group

must be customized
on a list-type sheet.
Drx Drx DRX switch, Short- The parameter group

cycle DRX switch, must be customized
Special DRX on a list-type sheet.
inactivity timer
(subframe), Special
long DRX cycle
(subframe), Special
On Duration timer
(subframe), Special
short-cycle DRX
supported indication,
Special short DRX
cycle(subframe),
Special DRX short
cycle timer
SPID-specific Preallocation Policy
Table 7-5 Parameters related to an SPID-specific preallocation policy

Summary Data
File
SpidCfg SPIGCFG Spid, Preallocation- The parameter group

Status must be customized.

eRAN
SPID-specific Handover back to the HPLMN Policy
Table 7-6 Parameters related to an SPID-specific handover back to the HPLMN policy

Summary Data
File
SpidCfg SpidCfg Spid, SPID-based The parameter group

Handover Back To must be customized
HPLMN Switch on a list-type sheet.
RatfreqPriori- RatfreqPriori- RAT frequency The parameter group

tyGroup tyGroup priority group ID, must be customized
Downlink EARFCN,
Priority, GERAN
Frequency Indicator
InterPLMNHoList InterPLMNHoList CN Operator ID, The parameter group

Target Mobile must be customized
country code, Target on a list-type sheet.
Mobile network code
ENodeBAlgoSwitch ENodeBAlgoSwitch Handover Algo The parameter group

switch must be customized
on a list-type sheet.
ExternalCell ExternalCell Mobile country code, The parameter group

Mobile network must be customized
code, eNodeB on a list-type sheet.
identity, Cell
identity, Downlink
EARFCN, Uplink
EARFCN indicator,
Uplink EARFCN,
Physical cell
identity, Tracking
area code, Cell name
EutranExternal- EutranExternal- Mobile country code, The parameter group

CellPlmn CellPlmn Mobile network must be customized
code, eNodeB on a list-type sheet.
identity, Cell
identity, Share
mobile country code,
Share mobile
network code

eRAN

Summary Data
File
EutranInterNFreq EutranInterNFreq Local cell identity, The parameter group

Downlink EARFCN, must be customized
Uplink EARFCN on a list-type sheet.
configure indicator,
Uplink EARFCN,
Inter frequency cell
resel priority
Inter frequency cell
resel priority,
EUTRAN
reselection time(s),
Speed dependent
resel parameter
configuring
indicator, Scaling
factor of treseleutra
in medium mobility
state, Scaling factor
of treseleutra in high
mobility state,
Measurement
bandwidth(MHz),
Frequency offset
(dB), Inter frequency
high priority
threshold(2dB), Inter
frequency lower
priority threshold
(2dB), Minimum
required RX level
(2dBm), PMAX
PMAX(dBm),
Neighbor cell config,
Presence antenna
port1, Inter-Freq HO
trigger Event Type

eRAN

Summary Data
File
EutranInterFreqN- EutranInterFreqN- Local cell identity, The parameter group

Cell Cell Mobile country code, must be customized
Mobile network on a list-type sheet.
code, eNodeB
identity, Cell
identity, Cell
individual offset
(dB), Cell offset(dB),
No handover
indicator, No remove
indicator, Blind
handover Priority,
ANR flag, Local cell
name, Neighbour
cell name
7.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure is as follows:
Step 1 After creating a planned data area, choose CME > Advanced > Customize Summary Data File
(U2000 client mode), or choose Advanced > Customize Summary Data File (CME client mode),
to customize a summary data file for batch reconfiguration.
NOTE
For context-sensitive help on a current task in the client, press F1.
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME into
the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in 7.4.5.1 Using the CME to
Perform Batch Configuration for Newly Deployed eNodeBs and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME,
and then start the data verification.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts
(U2000 client mode), or choose Area Management > Planned Area > Export Incremental
Scripts (CME client mode), to export and activate the incremental scripts.
----End

eRAN
7.4.5.3 Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.
Figure 7-1 MO search and configuration window
NOTE
l To view descriptions of the parameters in the MO, click in area 4 and press F1.
l Area 5 displays the details of a selected area-4 entry in vertical format. Click the "Details" button to
show or hide this area.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts, or choose Area Management
> Planned Area > Export Incremental Scripts, to export and activate the incremental scripts.
----End
7.4.5.4 Using MML Commands

SPID-specific Cell Reselection Policy

eRAN
Step 1 Run the ADD RATFREQPRIORITYGROUP command to configure a frequency priority

group.
For example, to configure a frequency priority group whose ID is 1, RAT type is E-UTRAN,
downlink EARFCN is 3390, and priority is 5, run the following command:
ADD RATFREQPRIORITYGROUP: RatFreqPriorityGroupId=1, RatType=EUTRAN, DlEarfcn=3390,
Priority=5;
NOTE
Frequencies configured using the RatFreqPriorityGroup MO must be preconfigured with HPLMNs. You
can run the ADD EUTRANEXTERNALCELL, ADD UTRANEXTERNALCELL, ADD
GERANEXTERNALCELL, or ADD CDMA2000EXTERNALCELL command to configure an
HPLMN for a frequency.
Step 2 Run the ADD SPIDCFG command to specify an SPID and associate this SPID with the
frequency priority group.
----End
For example, to set an SPID configuration, where the SPID of the UE is 2, a frequency priority
indicates a UE's preferentially camping, and the ID of the RAT/frequency priority group is 1,
run the following command:
ADD SPIDCFG: Spid=2, RatFreqPriorityInd=CFG, RatFreqPriorityGroupId=1;
SPID-specific Redirection Policy
The configuration method is the same as that for the SPID-specific cell reselection policy.
NOTE
Step 1 Run the MOD CELLALGOSWITCH command to turn on the MLB switches.
l For example, run the following command to enable inter-frequency MLB:
MOD CELLALGOSWITCH:LOCALCELLID=0, MLBALGOSWITCH=InterFreqMlbSwitch-1;
l For example, run the following command to enable inter-RAT MLB to UTRAN:
MOD CELLALGOSWITCH:LOCALCELLID=0,MLBALGOSWITCH=UtranMlbSwitch-1;
l For example, run the following command to enable inter-RAT MLB to GERAN
(GeranMlbSwitch apply only to Macro):
MOD CELLALGOSWITCH:LOCALCELLID=0,MLBALGOSWITCH=GeranMlbSwitch-1;

group.
For example, to configure a frequency priority group whose ID is 2, RAT type is E-UTRAN,
downlink EARFCN is 3399, and priority is 5, run the following command:
ADD RATFREQPRIORITYGROUP: RatFreqPriorityGroupId=2, RatType=EUTRAN, DlEarfcn=3390,
Priority=5;
Step 3 Run the ADD SPIDCFG command to specify an SPID, associate this SPID with the frequency
priority group, and enable inter-frequency load balancing or inter-RAT load sharing.
Step 4 Run the following commands to configure neighboring cells:

l Run the following commands to configure neighboring E-UTRAN cells:

eRAN
1. ADD EUTRANINTERNFREQ
2. ADD EUTRANEXTERNALCELL
3. (Optional) ADD EUTRANEXTERNALCELLPLMN
4. ADD EUTRANINTERFREQNCELL
l Run the following commands to configure neighboring UTRAN cells:
1. ADD UTRANNFREQ
2. ADD UTRANEXTERNALCELL
3. (Optional) ADD UTRANEXTERNALCELLPLMN
4. ADD UTRANNCELL
l Run the following commands to configure neighboring GERAN cells:
1. ADD GERANNFREQGROUP
2. ADD GERANNFREQGROUPARFCN
3. ADD GERANEXTERNALCELL
4. (Optional) ADD GERANEXTERNALCELLPLMN
5. ADD GERANNCELL
----End
Step 1 Run the LST DRX command, and check the DRX switch value in the command output.
l If the value is Off, run the following command to enable DRX:
MOD DRX: DRXALGSWITCH=ON;
l If the value is On, go to Step 2.
Step 2 Run the ADD SPIDCFG command with the Drx status parameter set to TRUE(TRUE).
----End
Step 1 Run the LST CELLALGOSWITCH command, and check the value of
PreAllocationSwitch in the command output.
l If the value is Off, run the following command to enable preallocation:
MOD CELLALGOSWITCH: LOCALCELLID=x,
ULSCHSWITCH=PreAllocationSwitch-1;
l If the value is On, go to Step 2.
Step 2 Run the ADD SPIDCFG command with the PreallocationStatus parameter set to TRUE
(TRUE).
----End

group.

eRAN
Step 2 Run the ADD SPIDCFG command to specify an SPID, associate this SPID with the frequency
priority group, and turn on the switch for handovers to the HPLMN.
Step 3 Run the MOD ENODEBALGOSWITCH command to turn on the switch for inter-PLMN
handovers.
Step 4 Run the ADD INTERPLMNHOLIST command to configure a pair of source and target
PLMNs for inter-PLMN handovers.
Step 5 Run the following commands to configure inter-frequency neighboring cells:
ADD EUTRANEXTERNALCELL
(Optional) ADD EUTRANEXTERNALCELLPLMN
ADD EUTRANINTERNFREQ
ADD EUTRANINTERFREQNCELL
----End
7.4.6 Activation Observation

Follow these steps to observe the activation of SPID-based cell reselection:
Step 1 Run the LST RATFREQPRIORITYGROUP command to list the configuration of the
frequency priority group specified for the SPID of the test UE.
In this example, the SPID is 2 and the group ID is 1.
Figure 7-2 Configuration of frequency priority group 1
On the U2000 client, start an S1 interface tracing task.

1. Choose Monitor > Signaling Trace > Signaling Trace Management.
2. On the left navigation tree, double-click S1 Interface Trace under LTE > Application
Layer.
If the IE subscriberProfileIDforRFP appears in the
S1AP_INITIAL_CONTEXT_SETUP_REQ message, the EPC has delivered the SPID.
Figure 7-3 IE subscriberProfileIDforRFP in the

S1AP_INITIAL_CONTEXT_SETUP_REQ message

eRAN
Step 2 Run the LST SPIDCFG command to list the SPID configuration.
Figure 7-4 SPID configuration
Step 3 Use the UE to access a cell under the eNodeB.

Step 4 Run the following command to block the SCTP link by using the SCTP link number 0 as an
example:
BLK SCTPLNK: SCTPNO=0;
Step 5 On the U2000 client, start a Uu interface tracing task.

2. On the left navigation tree, double-click Uu Interface Trace under LTE > Application
Layer.
If the E-UTRAN frequency indicated by the IE idleModeMobilityControlInfo in the
RRC_CONN_REL message is same as the frequency displayed in the result of Step 1, the
cell reselection policy for the SPID has been activated.
Figure 7-5 IE idleModeMobilityControlInfo
----End
Redirection Policy
Follow these steps to observe the activation of SPID-based redirection:

eRAN
Step 1 Run the LST RATFREQPRIORITYGROUP command to list the configuration of the
frequency priority group specified for the SPID of the test UE.
In this example, the SPID is 2 and the group ID is 1.
Figure 7-6 Configuration of frequency priority group 1
Step 2 Run the LST SPIDCFG command to list the SPID configuration.
Figure 7-7 SPID configuration
Step 3 Use the UE to access a cell under the eNodeB.
Step 4 On the U2000 client, start an S1 interface tracing task

2. On the left navigation tree, double-click S1 Interface Trace under LTE > Application
Layer.
If the IE subscriberProfileIDforRFP appears in the
S1AP_INITIAL_CONTEXT_SETUP_REQ message, the EPC has delivered the SPID.
Figure 7-8 S1AP_INITIAL_CONTEXT_SETUP_REQ message
Step 5 Run the RMV S1INTERFACE command to remove the S1 interface.
Step 6 On the U2000 client, start a Uu interface tracing task.

1. Choose Monitor > Signaling Trace > Signaling Trace Management .
2. On the left navigation tree, double-click Uu Interface Trace under LTE > Application
Layer.

eRAN
If the UTRAN frequency indicated by the IE redirectedCarrierInfo in the

RRC_CONN_REL message is same as the frequency with the second highest priority in
the result of Step 1, the redirection policy for the SPID has been activated.
Figure 7-9 IE redirectedCarrierInfo
----End

Follow these steps to observe the activation of SPID- and load-based handover:
Step 1 Run the LST SPIDCFG command to query the setting of the inter-frequency MLB switch.
Figure 7-10 Configuration of the inter-frequency MLB switch
Step 2 Run the following command to enable inter-frequency MLB for the cell:

eRAN
MOD CELLALGOSWITCH: MlbAlgoSwitch=InterFreqMlbSwitch-1;
Step 3 Start an S1 interface tracing task.
Step 4 Use a UE with this SPID to access the network and enable it to enter the RRC_IDLE state.
If the IE subscriberProfileIDforRFP appears in the S1AP_INITIAL_CONTEXT_SETUP_REQ
message, the EPC has delivered the SPID.
Step 5 Start an X2 interface tracing task.
Step 6 Start a low-traffic service on the UE, which occupies one to three resource blocks (RBs) in a 10
MHz cell (used as an example). Trigger a heavy load in the cell so that the inter-frequency MLB
threshold is reached. Continue observing the RESOURCE_STATUS_UPDATE message.
If a HANDOVER_REQUEST message with a cause value of "reduce-load-in-serving-cell" is
delivered, a load-based inter-frequency handover has been triggered for the UE. The load-based
handover policy has been activated for the SPID.
Figure 7-11 Messages traced over the X2 interface
Figure 7-12 Details of the HANDROVER REQUEST message
NOTE
For the detailed verification method, see MLB Feature Parameter Description.
----End
DRX Policy
Follow these steps to observe the activation of SPID-based DRX:

eRAN
Step 1 Run the ADD SPIDCFG command to configure a DRX policy for an SPID on the eNodeB
according to the SPID configured for a UE in the EPC and policy planned by the operator.
Step 2 Run the MOD DRX command with the DRX switch parameter set to ON(On).
Step 3 Start a Uu interface tracing task.
Step 4 Use a UE with this SPID to access a cell under the eNodeB. Ensure that the uplink and downlink
conditions of the UE meet the DRX thresholds.
Step 5 Check the RRC_CONN_RECFG message over the Uu interface.
If the message contains RFSP-specific DRX parameters as shown in Figure 7-13, the UE enters
the DRX state and the SPID-specific DRX policy has been activated.
Figure 7-13 RRC_CONN_RECFG message
----End
Follow these steps to observe the activation of SPID-based preallocation:
Step 1 Set the UE category to CAT 3. Use the UE to access a cell in the cell center, and ensure that the
UE is not performing any uplink or downlink services.
Step 2 On the U2000 client, start a modulation and coding scheme (MCS) count monitoring task for
the UE.
2. In the navigation tree on the left, double-click MCS Count Monitoring under LTE > User
Performance Monitoring.
Step 3 On the U2000 client, check the number of uplink scheduling times.
If the sum of ULSCH Num23 and ULSCH Num24 is 200 in the monitoring result, as shown
in Figure 7-14, the eNodeB has preallocated resources for this UE and the SPID-specific
preallocation policy has been activated.

eRAN
Figure 7-14 MCS count monitoring result
----End

Follow these steps to observe the activation of SPID-based handover back to the HPLMN:
Step 1 Choose a network where operator B provides LTE coverage for the entire network and operator
A provides LTE coverage for a part of the network. Use a UE that subscribes to operator A for
the test. For the UE, ensure that the frequencies owned by operator A have higher priorities than
those owned by operator B. Use the UE to access an operator A's E-UTRAN cell in the cell
center.
Step 2 Start a Uu interface tracing task.
Step 3 Move the UE to the edge of operator A's E-UTRAN cell to trigger a coverage-based inter-PLMN
handover for the UE to operator B's E-UTRAN.
Step 4 Trace Uu messages in operator B's E-UTRAN.
If the eNodeB delivers the SPID-specific measurement configuration for event A4 in the
RRC_CONN_RECFG message, as shown in Figure 7-15, a coverage-based inter-PLMN
handover has been triggered.
In Figure 7-15, the value of the IE reportConfigId depends on the configuration, whereas other
IEs use default values.
Figure 7-15 SPID-specific measurement configuration for event A4
Step 5 Move the UE back to operator A's E-UTRAN to trigger a handover back to the HPLMN.
Step 6 Trace messages over the Uu interface on the operator A's eNodeB.

eRAN
After receiving A4 measurements reports, the operator A's eNodeB issues a handover command
and delivers access information about the target cell in the RRC_CONN_RECFG message, as
shown in Figure 7-16. This indicates that a handover has been triggered. In Figure 7-16, the
value of the IE targetPhysCellId depends on the configuration, whereas other IEs use default
values.
Figure 7-16 Message indicating successful access to the target cell
----End
7.4.7 Reconfiguration
N/A
7.4.8 Deactivation
7.4.8.1 Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in "Using the CME to Perform Batch Configuration" of section
"7.4.5 Initial Configuration." In the procedure, modify parameters according to Table 7-7 to
Table 7-10.
NOTE
Table 7-7 Parameters related to an SPID-specific load-based handover policy
MO Sheet in the Parameter Group Setting Notes

Summary Data
File
SPIDCFG SPIDCFG InterFreqMlbSwitch Set this parameter to

FALSE(FALSE).

eRAN

Summary Data
File
SPIDCFG SPIDCFG InterRatMlbSwitch Set this parameter to

FALSE(FALSE).
Table 7-8 Parameter related to an SPID-specific DRX policy

Summary Data
File
SPIDCFG SPIDCFG DrxStatus Set this parameter to

FALSE(FALSE).
Table 7-9 Parameter related to an SPID-specific preallocation policy

Summary Data
File
SPIDCFG SPIDCFG PreallocationStatus Set this parameter to

FALSE(FALSE).
Table 7-10 Parameter related to an SPID-specific handover back to the HPLMN policy

Summary Data
File
SPIDCFG SPIDCFG HoBackToHPLMN Set this parameter to

Switch FALSE(FALSE).
7.4.8.2 Using the CME to Perform Single Configuration

On the CME, set parameters according to 7.4.8.1 Using the CME to Perform Batch
Configuration. For detailed instructions, see "7.4.5.3 Using the CME to Perform Single
Configuration" described for feature activation.

eRAN
7.4.8.3 Using MML Commands

Run the MOD SPIDCFG command to disable cell reselection, load-based handover, DRX, or
preallocation for an SPID.
7.5 Performance Monitoring

Monitoring SPID-based Cell Reselection
To check whether voice-centric UEs preferentially camp on UMTS or GSM cells based on the
SPID-specific cell reselection policy, observe the number of CSFB attempts indicated by the
L.CSFB.PrepAtt counter on the eNodeB side. If the counter value decreases after SPID-specific
cell reselection is activated, the SPID-specific cell reselection policy takes effect. In this case,
voice-centric UEs preferentially camp on UMTS or GSM cells to initiate voice services but not
perform CSFB from the LTE network. This reduces the voice service setup delay.
To monitor the performance of SPID-based cell reselections, view the following counters:
l L.RRCRel.DedicatedPri.GERAN.High: measures the number of RRC connection releases

in which GERAN frequencies are assigned the highest dedicated priority.
l L.RRCRel.DedicatedPri.WCDMA.High: measures the number of RRC connection
releases in which WCDMA frequencies are assigned the highest dedicated priority.
l L.RRCRel.DedicatedPri.LTE.High: measures the number of RRC connection releases in
which E-UTRAN frequencies are assigned the highest dedicated priority.
Monitoring SPID-based Handover back to the HPLMN

To monitor the performance of SPID-based handovers back to HPLMNs, view the following
counters:
l L.HHO.InterFreq.RegainHPLMN.PrepAttOut: measures the number of outgoing inter-

frequency handover attempts triggered for UEs to go back to their HPLMNs.
l L.HHO.InterFreq.RegainHPLMN.ExecAttOut: measures the number of outgoing inter-
frequency handover executions triggered for UEs to go back to their HPLMNs.
l L.HHO.InterFreq.RegainHPLMN.ExecSuccOut: measures the number of successful
outgoing inter-frequency handovers triggered for UEs to go back to their HPLMNs.
l L.HHO.InterFddTdd.RegainHPLMN.PrepAttOut: measures the number of inter-duplex-
mode outgoing handover attempts triggered for a UE to go back to the HPLMN
l L.HHO.InterFddTdd.RegainHPLMN.ExecAttOut: measures the number of inter-duplex-
mode outgoing handovers triggered for a UE to go back to the HPLMN
l L.HHO.InterFddTdd.RegainHPLMN.ExecAttOut: measures the number of successful
inter-duplex-mode outgoing handovers triggered for a UE to go back to the HPLMN
l L.HHO.E2W.RegainHPLMN.PrepAttOut: measures the number of EUTRAN-to-
WCDMA handover attempts triggered for UEs to go back to their HPLMNs.
l L.HHO.E2W.RegainHPLMN.ExecAttOut: measures the number of EUTRAN-to-
WCDMA handover executions triggered for UEs to go back to their HPLMNs.
l L.HHO.E2W.RegainHPLMN.ExecSuccOut: measures the number of successful
EUTRAN-to-WCDMA handovers triggered for UEs to go back to their HPLMNs.

eRAN
Monitoring SPID-based Preallocation

l To monitor the performance of SPID-based preallocation, view the counter
L.ChMeas.PRB.UL.PreSch.Used.Avg, which measures the average number of
preallocated PRBs.
7.6 Parameter Optimization

N/A
7.7 Troubleshooting
Fault Description
SPID-based cell reselection is enabled, and the related frequency priority parameters have been
correctly configured. However, the Uu tracing result shows that the frequencies indicated in the
RRC Connection Release messages are inconsistent with the configuration, for example, some
configured frequencies are not included in the RRC Connection Release messages.
Fault Handling
Step 1 On the U2000 client, run the LST EUTRANINTERNFREQ, LST UTRANNFREQ, and LST
GERANNFREQGROUP commands to check whether the frequencies that are not included in
the RRC Connection Release messages are correctly configured on the eNodeB involved.
l If no, run the ADD EUTRANINTERNFREQ, ADD UTRANNFREQ, and ADD
GERANNFREQGROUP commands to add the frequencies and cell reselection parameters.
In addition, run the ADD EUTRANRANSHARE, ADD UTRANRANSHARE, and ADD
GERANRANSHARE commands to add the PLMNs that use the frequencies.
Step 2 Run the LST EUTRANRANSHARE, LST UTRANRANSHARE, and LST

GERANRANSHARE commands to check the PLMNs that use the frequencies are configured
on the eNodeB.
l If no, run the ADD EUTRANRANSHARE, ADD UTRANRANSHARE, and ADD
GERANRANSHARE commands to add the PLMNs.
Step 3 Contact Huawei for technical support.
----End

eRAN
Flexible User Steering Feature Parameter Description 8 Parameters
8 Parameters
Table 8-1 Parameter description
MO Parame MML Feature Feature Description

ter ID Comma ID Name
nd
CellAlg MlbAlg MOD LOFD-0 Intra- Meaning: Indicates the switches used to enable or
oSwitch oSwitch CELLA 01032 / LTE disable load balancing (MLB) algorithms. Switches
LGOSW TDLOF Load specified by this parameter control the following
ITCH D-00103 Balancin algorithms: intra-frequency MLB, intra-frequency
LST 2 g MLB for UEs in idle mode, inter-frequency MLB, inter-
CELLA LOFD-0 frequency MLB for UEs in idle mode, blind inter-
Inter- frequency MLB, MLB to UTRAN, MLB to UTRAN for
LGOSW 01044 / RAT
ITCH TDLOF UEs in idle mode, MLB to GERAN, MLB to
Load CDMA2000, MLB based on PRB evaluation, and MLB
D-00104 Sharing
4 based on neighboring cell load status. If one switch is
to turned on, the corresponding algorithm is enabled to
LOFD-0 UTRAN balance the loads between the serving cell and
01045 / Inter- neighboring cells of the specified category.
TDLOF RAT IntraFreqMlbSwitch: Indicates the switch used to
D-00104 Load enable or disable intra-frequency load balancing. If this
5 Sharing parameter is turned on, intra-frequency load balancing
LOFD-0 to is enabled and IntraFreqIdleMlbSwitch becomes valid.
01057 GERAN If this parameter is turned off, intra-frequency load
balancing is disabled and IntraFreqIdleMlbSwitch does
not take effect. This switch will be removed in later
versions. In this version, the setting of this switch is still
synchronized between the U2000 and the eNodeB and
can be delivered to the eNodeB, but it is no longer used
internally. Therefore, you are advised to avoid using this
switch. InterFreqMlbSwitch: Indicates the switch used
to enable or disable inter-frequency load balancing.
UtranMlbSwitch: Indicates the switch used to enable or
disable load sharing with UTRAN cells.
GeranMlbSwitch: Indicates the switch used to enable or
disable load sharing with GERAN cells.

eRAN

nd
CdmaMlbSwitch: Indicates the switch used to enable or

disable load sharing with CDMA2000 cells. This switch
will be removed in later versions. In this version, the
setting of this switch is still synchronized between the
U2000 and the eNodeB and can be delivered to the
eNodeB, but it is no longer used internally. Therefore,
you are advised to avoid using this switch. IntraFreqI-
dleMlbSwitch: If both IntraFreqIdleMlbSwitch and
IntraFreqMlbSwitch are turned on, intra-frequency load
balancing for UEs in idle mode is enabled. Otherwise,
intra-frequency idle load balancing for UEs in idle mode
is disabled. This switch will be removed in later
switch. UtranIdleMlbSwitch: Indicates the switch used
to enable or disable load sharing with UTRAN for UEs
in idle mode. MlbLoadInfoSwitch: Indicates the switch
whether load of an inter-RAT cell is considered when
the load sharing between the E-UTRAN cell and the
inter-RAT cell is performed. In inter-RAT load sharing
based on load of the inter-RAT cell, the inter-RAT cell
must be a UTRAN cell. If both the MlbLoadInfoSwitch
and UtranMlbSwitch options are selected, the UTRAN
cell whose load status is obtained and is normal or
medium can be selected as the candidate cell for load
sharing with UTRAN. If both the MlbLoadInfoSwitch
and UtranIdleMlbSwitch options are selected, the
UTRAN cell whose load status is obtained and is normal
can be selected as the candidate cell for load sharing
with UTRAN. InterFreqBlindMlbSwitch: Indicates the
switch used to enable or disable the inter-frequency
blind load balancing. PrbValMlbSwitch: Indicates the
switch used to enable or disable the load balancing
based on PRB evaluation. This switch takes effects only
on LTE TDD cells.This switch will be removed in later
switch. InterFreqIdleMlbSwitch: Indicates the switch
used to enable or disable inter-frequency load balancing
for UEs in idle mode. After the InterFreqIdleMlbSwitch
option is selected, the load balancing for UEs in idle
mode is valid only when at least one inter-frequency
load balancing mode for UEs in idle mode is selected.

eRAN

nd
GUI Value Range: IntraFreqMlbSwitch

(IntraFreqMlbSwitch), InterFreqMlbSwitch
(InterFreqMlbSwitch), UtranMlbSwitch
(UtranMlbSwitch), GeranMlbSwitch
(GeranMlbSwitch), CdmaMlbSwitch
(CdmaMlbSwitch), IntraFreqIdleMlbSwitch
(IntraFreqIdleMlbSwitch), UtranIdleMlbSwitch
(UtranIdleMlbSwitch), MlbLoadInfoSwitch
(MlbLoadInfoSwitch), InterFreqBlindMlbSwitch
(InterFreqBlindMlbSwitch), PrbValMlbSwitch
(PrbValMlbSwitch), InterFreqIdleMlbSwitch
(InterFreqIdleMlbSwitch)
Unit: None
Actual Value Range: IntraFreqMlbSwitch,
InterFreqMlbSwitch, UtranMlbSwitch,
GeranMlbSwitch, CdmaMlbSwitch, IntraFreqI-
dleMlbSwitch, UtranIdleMlbSwitch, MlbLoadInfoS-
witch, InterFreqBlindMlbSwitch, PrbValMlbSwitch,
InterFreqIdleMlbSwitch
Default Value: IntraFreqMlbSwitch:Off,
InterFreqMlbSwitch:Off, UtranMlbSwitch:Off,
GeranMlbSwitch:Off, CdmaMlbSwitch:Off,
IntraFreqIdleMlbSwitch:Off,
UtranIdleMlbSwitch:Off, MlbLoadInfoSwitch:Off,
InterFreqBlindMlbSwitch:Off, PrbValMlbSwitch:Off,
InterFreqIdleMlbSwitch:Off
SpidCfg Spid ADD LOFD-0 Camp & Meaning: Indicates the subscriber profile ID (SPID).
SPIDCF 0105401 Handov GUI Value Range: 1~256
G / er Based
TDLOF on SPID Unit: None
LST
SPIDCF D-00105 UL Pre- Actual Value Range: 1~256
G 401 allocatio Default Value: None
MOD LOFD-0 n Based
SPIDCF 01059 / on SPID
G TDLOF
D-00105
RMV 9
SPIDCF
G

eRAN

nd
SpidCfg RatFreq ADD LOFD-0 Camp & Meaning: Indicates whether to set the priority for the
PriorityI SPIDCF 0105401 Handov intra-RAT frequency group. If this parameter is set to
nd G / er Based CFG(CFG), UEs select the target frequency based on
MOD TDLOF on SPID the priority setting. If this parameter is set to NOT_CFG
SPIDCF D-00105 (NOT_CFG), UEs do not select the target frequency
G 401 based on the priority setting.
LST GUI Value Range: NOT_CFG(NOT_CFG), CFG

SPIDCF (CFG)
G Unit: None
Actual Value Range: NOT_CFG, CFG
Default Value: NOT_CFG(NOT_CFG)
SpidCfg RatFreq ADD LOFD-0 Camp & Meaning: Indicates the ID of the intra-RAT frequency
Priority SPIDCF 0105401 Handov priority group.
GroupId G / er Based GUI Value Range: 0~255
MOD TDLOF on SPID
D-00105 Unit: None
SPIDCF
G 401 Actual Value Range: 0~255
LST Default Value: 0

SPIDCF
G
SpidCfg DrxStat ADD LBFD-0 DRX Meaning: Indicates whether to use normal or special
us SPIDCF 02017 / DRX. If this parameter is set to TRUE, ordinary DRX
G TDLBF parameters are applied to UEs with the SPID. If this
MOD D-00201 parameter is set to FALSE, special DRX parameters are
SPIDCF 7 applied to UEs with the SPID.
G GUI Value Range: FALSE(FALSE), TRUE(TRUE)
LST Unit: None
SPIDCF Actual Value Range: FALSE, TRUE
G
Default Value: FALSE(FALSE)
SpidCfg Prealloc ADD LOFD-0 UL Pre- Meaning: Indicates whether to support preallocation. If
ationStat SPIDCF 01059 / allocatio this parameter is set to TRUE and PreAllocationSwitch
us G TDLOF n Based under the UlSchSwitch parameter in the
MOD D-00105 on SPID CellAlgoSwitch MO is set to On, resources can be
SPIDCF 9 preallocated to UEs. Otherwise, resources are not
G preallocated to UEs.
LST GUI Value Range: FALSE(FALSE), TRUE(TRUE)

SPIDCF Unit: None
G Actual Value Range: FALSE, TRUE
Default Value: TRUE(TRUE)

eRAN

nd
SpidCfg InterFre ADD LOFD-0 Camp & Meaning: Indicates whether to enable or disable inter-
qMlbSw SPIDCF 0105401 Handov frequency load balancing for the SPID. The values
itch G / er Based TRUE or FALSE indicate that inter-frequency load
MOD TDLOF on SPID balancing is allowed or prohibited for UEs with the
SPIDCF D-00105 Intra- SPID, respectively.
G 401 LTE GUI Value Range: FALSE(FALSE), TRUE(TRUE)
LST LOFD-0 Load Unit: None
SPIDCF 01032 / Balancin
TDLOF g Actual Value Range: FALSE, TRUE
G
D-00103 Default Value: TRUE(TRUE)
2
SpidCfg InterRat ADD LOFD-0 Camp & Meaning: Indicates whether to enable or disable inter-
MlbSwit SPIDCF 0105401 Handov RAT load sharing for the SPID. The values TRUE or
ch G / er Based FALSE indicate that inter-RAT load sharing is allowed
MOD TDLOF on SPID or prohibited for UEs with the SPID, respectively.
SPIDCF D-00105 Inter- GUI Value Range: FALSE(FALSE), TRUE(TRUE)
G 401 RAT Unit: None
LST LOFD-0 Load
01044 / Sharing Actual Value Range: FALSE, TRUE
SPIDCF
G TDLOF to Default Value: TRUE(TRUE)
D-00104 UTRAN
4 Inter-
LOFD-0 RAT
01045 / Load
TDLOF Sharing
D-00104 to
5 GERAN
SpidCfg HoBack ADD LOFD-0 Camp & Meaning: Indicates whether to allow SPID-based
ToHPL SPIDCF 0105401 Handov handovers back to the home public land mobile network
MNSwit G / er Based (HPLMN). If this parameter is set to TRUE(TRUE), a
ch MOD TDLOF on SPID roaming UE can be handed over to the HPLMN network
SPIDCF D-00105 when it moves back to the coverage of the HPLMN
G 401 network based on the SPID. If this parameter is set to
FALSE(FALSE), this UE cannot be handed over to the
LST HPLMN network based on the SPID.
SPIDCF
G GUI Value Range: FALSE(FALSE), TRUE(TRUE)
Unit: None
Actual Value Range: FALSE, TRUE
Default Value: FALSE(FALSE)

eRAN

nd
RatFreq RatFreq ADD LOFD-0 Camp & Meaning: Indicates the ID of the RAT/frequency
Priority Priority RATFR 0105401 Handov priority group.
Group GroupId EQPRI / er Based GUI Value Range: 0~255
ORITY TDLOF on SPID
GROUP D-00105 Unit: None
LST 401 Actual Value Range: 0~255

RATFR Default Value: None
EQPRI
ORITY
GROUP
MOD
RATFR
EQPRI
ORITY
GROUP
RMV
RATFR
EQPRI
ORITY
GROUP
RatFreq RatType ADD LOFD-0 Camp & Meaning: Indicates the Radio Access Technology
Priority RATFR 0105401 Handov (RAT).
Group EQPRI / er Based GUI Value Range: EUTRAN, UTRAN, GERAN,
ORITY TDLOF on SPID CDMA20001XRTT, CDMA2000HRPD
GROUP D-00105 Enhance
401 Unit: None
LST d CS
RATFR TDLOF Actual Value Range: EUTRAN, UTRAN, GERAN,
Fallback
EQPRI D-00109 CDMA20001XRTT, CDMA2000HRPD
to
ORITY 0 CDMA2 Default Value: None
GROUP LOFD-0 000
MOD 01021 / 1xRTT
RATFR TDLOF PS Inter-
EQPRI D-00102 RAT
ORITY 1 Mobility
GROUP between
RMV E-
RATFR UTRAN
EQPRI and
ORITY CDMA2
GROUP 000

eRAN

nd
RatFreq DlEarfc ADD LOFD-0 Camp & Meaning: Indicates the downlink frequency. In
Priority n RATFR 0105401 Handov CDMA2000, this parameter indicates the bandclass.
Group EQPRI / er Based Before configuring a priority for a frequency specified
ORITY TDLOF on SPID by this parameter, ensure that an external or local cell
GROUP D-00105 operating on this frequency has been configured.
LST 401 GUI Value Range: 0~46589,54436~65535
RATFR Unit: None
EQPRI
ORITY Actual Value Range: 0~46589,54436~65535
GROUP Default Value: None
MOD
RATFR
EQPRI
ORITY
GROUP
RMV
RATFR
EQPRI
ORITY
GROUP
RatFreq Priority ADD LOFD-0 Camp & Meaning: Indicates the priority of the intra-RAT
Priority RATFR 0105401 Handov frequency band or frequency. The value 0 indicates the
Group EQPRI / er Based lowest priority. The value of this parameter must be
ORITY TDLOF on SPID determined together with the priorities of other
GROUP D-00105 frequencies during the network planning. Cell
MOD 401 reselection priorities in different RATs cannot be the
RATFR same.
EQPRI GUI Value Range: 0~7
ORITY Unit: None
GROUP
Actual Value Range: 0~7
LST
RATFR Default Value: 0
EQPRI
ORITY
GROUP

eRAN

nd
RatFreq BandInd ADD LOFD-0 Camp & Meaning: Indicates the GERAN frequency band.
Priority icator RATFR 0105401 Handov GUI Value Range: GSM_dcs1800, GSM_pcs1900
Group EQPRI / er Based
ORITY TDLOF on SPID Unit: None
GROUP D-00105 Actual Value Range: GSM_dcs1800, GSM_pcs1900
MOD 401 Default Value: GSM_dcs1800
RATFR
EQPRI
ORITY
GROUP
LST
RATFR
EQPRI
ORITY
GROUP
Drx DrxAlg MOD LBFD-0 DRX Meaning: Indicates whether to enable DRX. The setting
Switch DRX 02017 / of this parameter has no effect on dynamic DRX. DRX
LST TDLBF applies to a CA UE only when this parameter is set to
DRX D-00201 ON(On) on both eNodeBs to which the PCell and SCell
7 of the CA UE belong.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)

eRAN

nd
CellAlg UlSchS MOD LOFD-0 VoIP Meaning: Indicates the switches related to uplink (UL)
oSwitch witch CELLA 01016 / Semi- scheduling in the cell. The switches are used to enable
LGOSW TDLOF persisten or disable specific UL scheduling functions.
ITCH D-00101 t SpsSchSwitch: Indicates the switch used to enable or
LST 6 Scheduli disable semi-persistent scheduling during talk spurts of
CELLA LOFD-0 ng VoIP services. If this switch is turned on, semi-
LGOSW 01048 / TTI persistent scheduling is applied during talk spurts of
ITCH TDLOF Bundlin VoIP services. If this switch is turned off, dynamic
D-00104 g scheduling is applied during talk spurts of VoIP
8 services. SinrAdjustSwitch: Indicates whether to adjust
Dynami the measured signal to interference plus noise ratio
LOFD-0 c (SINR) based on ACK/NACK in UL hybrid automatic
0101502 Scheduli repeat request (HARQ) processes. PreAllocationS-
/ ng witch: Indicates whether to enable preallocation in the
TDLOF Basic uplink. When this switch is on: (1) if SmartPreAlloca-
D-00101 Scheduli tionSwitch is off and a UE is in the discontinuous
502 ngTDL reception (DRX) state, preallocation is disabled for the
TDLBF OFD-07 UE in the uplink; (2) if SmartPreAllocationSwitch is off
D-00202 0224:Sc and the UE is not in the DRX state, preallocation is
5 heduling enabled for the UE in the uplink; (3) if SmartPreAlloca-
Based tionSwitch is on and the SmartPreAllocationDuration
on Max parameter value is greater than 0, smart preallocation is
Bit Rate enabled for the UE in the uplink; (4) if SmartPreAlloca-
tionSwitch is on and the SmartPreAllocationDuration
parameter value is 0, preallocation is disabled for the
UE in the uplink. If this switch is off, preallocation is
disabled for the UE in the uplink. If bearer-level
preallocation or bearer-level smart preallocation is
enabled for a QCI, cell-level preallocation and cell-level
smart preallocation do not apply to UEs with the QCI.
UlVmimoSwitch: Indicates the switch used to enable or
disable multi-user MIMO (MU-MIMO) in the UL. If
this switch is turned on, the eNodeB performs MU-
MIMO pairing among UEs based on related principles.
UEs forming a pair transmit data using the same time-
frequency resources, which improves system
throughput and spectral efficiency. TtiBundlingSwitch:
Indicates the switch used to enable or disable
transmission time interval (TTI) bundling. If TTI
bundling is enabled, more transmission opportunities
are available to UEs within the delay budget for VoIP
services on the Uu interface, thereby improving uplink
coverage. ImIcSwitch: Indicates the switch to enable or
disable the intermodulation interference (IM)
cancellation for UEs. When data is transmitted in both
UL and DL, two IM components are generated
symmetrically beside the Direct Current (DC)

eRAN

nd
subcarrier on the DL receive channel due to interference

from UL radio signals. If this switch is turned on, IM
component elimination is performed on UEs. If this
switch is turned off, IM component elimination is not
performed on UEs. This switch applies only to FDD
cells working in frequency band 20. SmartPreAlloca-
tionSwitch: Indicates the switch used to enable or
disable uplink smart preallocation when preallocation
is enabled (by turning on PreAllocationSwitch). If both
PreAllocationSwitch and SmartPreAllocationSwitch
are turned on, and SmartPreAllocationDuration is set to
a value greater than 0, uplink smart preallocation is
enabled; otherwise, uplink smart preallocation is
disabled. PuschDtxSwitch: Indicates whether the
eNodeB uses the physical uplink shared channel
(PUSCH) discontinuous transmission (DTX) detection
result during uplink (UL) scheduling. If this switch is
turned on, based on the PUSCH DTX detection result,
the eNodeB determines whether to perform adaptive
retransmission during UL scheduling and also adjusts
the control channel element (CCE) aggregation level of
the physical downlink control channel (PDCCH)
carrying downlink control information (DCI) format 0.
This switch takes effect only on FDD cells. If an FDD
cell is established on an LBBPc, this switch takes effect
only when the cell uses less than four RX antennas and
normal cyclic prefix (CP) in the uplink, and the
SrsCfgInd parameter in the SRSCfg MO is set to
BOOLEAN_TRUE. Note that the LBBPc does not
support PUSCH DTX detection for UEs with multi-user
MIMO (MU-MIMO) applied. UlIblerAdjustSwitch:
Indicates the switch used to enable or disable uplink
initial block error rate (IBLER) adjustment algorithm.
If this switch is turned on, IBLER convergence target is
adjusted to increase the cell edge throughput.
UlEnhancedFssSwitch: Indicates the switch used to
enable or disable uplink load-based enhanced frequency
selection. This switch applies only to FDD cells.
UlIicsAlgoSwitch:Indicates the switch used to enable
or disable the UL IICS algorithm. If this switch is turned
on, interference can be reduced based on accurate
detection of user attributes and resource scheduling
coordination, thereby increasing the cell edge
throughput. UlEnhancedSrSchSwitch: Indicates
whether uplink re-scheduling is performed only when
the On Duration timer for the DRX long cycle starts.
Uplink re-scheduling is required if the number of

eRAN

nd
HARQ retransmissions for a scheduling request (SR)

reaches the maximum value but the scheduling still
fails. If this switch is turned on, uplink re-scheduling is
performed only when the On Duration timer for the
DRX long cycle starts. If this switch is turned off, uplink
re-scheduling is performed immediately after the
number of HARQ retransmissions for SR reaches the
maximum value but the scheduling still fails. It is
recommended that the switch be turned on in live
networks. SchedulerCtrlPowerSwitch: Indicates
whether the uplink scheduler performs scheduling
without considering power control restrictions. If this
switch is turned on, the uplink scheduler performs
scheduling without considering power control
restrictions, which ensures full utilization of the
transmit power for all UEs. If this switch is turned off,
the uplink scheduler considers power control
restrictions while performing scheduling, which
prevents full utilization of the transmit power for UEs
at far or medium distances from the cell center.
UlMinGbrSwitch: Indicates the switch used to enable
or disable uplink minimum guaranteed bit rate (GBR).
If this switch is turned on, the minimum GBR of non-
GBR services are ensured by increasing the scheduling
priority of UEs whose non-GBR service rates are lower
than the minimum GBR of GBR services.
UlMbrCtrlSwitch: Indicates the switch used to enable
or disable uplink scheduling based on the maximum bit
rate (MBR) and guaranteed bit rate (GBR) on the GBR
bearer. If this switch is turned on, the eNodeB performs
uplink scheduling on GBR bearers based on the MBR
and GBR. If this switch is turned off, the eNodeB
performs uplink scheduling on GBR bearers based on
the GBR only. MbrUlSchSwitch: Indicates whether the
eNodeB performs uplink scheduling based on MBR. If
this switch is turned on, the eNodeB prioritizes UEs
based on the MBRs during uplink scheduling. This
parameter applies only to LTE TDD cells.
UeAmbrUlSchSwitch: Indicates whether the eNodeB
performs uplink scheduling based on the aggregate
maximum bit rate (AMBR) of UEs. If this switch is
turned on, the eNodeB prioritizes UEs based on the
AMBRs during uplink scheduling. This parameter
applies only to LTE TDD cells. UlEnhancedDopplerS-
witch: Indicates whether to enable enhanced uplink
scheduling based on mobility speed. If this switch is
turned on, the eNodeB determines whether a UE is a

eRAN

nd
low-mobility UE based on the Doppler measurement in

the physical layer, and then improves uplink frequency
selective scheduling performance for low-mobility
UEs. If this switch is turned off, enhanced uplink
scheduling based on mobility speed is disabled. This
switch takes effect only when the UlEnhancedDop-
plerSwitch parameter is set to CLASS_1. This switch
does not take effect on cells established on an LBBPc.
UlRaUserSchOptSw: Indicates whether the eNodeB
raises the scheduling priority of UEs sending uplink
access signaling, including MSG5 and the RRC
Connection Reconfiguration Complete message. If this
switch is on, the eNodeB raises the scheduling priority
of UEs sending uplink access signaling. If this switch is
off, the eNodeB does not raise the scheduling priority
of UEs sending uplink access signaling.
GUI Value Range: SpsSchSwitch(SpsSchSwitch),
SinrAdjustSwitch(SinrAdjustSwitch), PreAllocationS-
witch(PreAllocationSwitch), UlVmimoSwitch
(UlVmimoSwitch), TtiBundlingSwitch(TtiBundlingS-
witch), ImIcSwitch(ImIcSwitch), SmartPreAlloca-
tionSwitch(SmartPreAllocationSwitch),
PuschDtxSwitch(PuschDtxSwitch), UlIblerAdjustS-
witch(UlIblerAdjustSwitch), UlEnhancedFssSwitch
(UlEnhancedFssSwitch), UlEnhancedSrSchSwitch
(UlEnhancedSrSchSwitch), SchedulerCtrlPowerS-
witch(SchedulerCtrlPowerSwitch), UlIicsAlgoSwitch
(UlIicsAlgoSwitch), UlMinGbrSwitch
(UlMinGbrSwitch), UlMbrCtrlSwitch
(UlMbrCtrlSwitch), MbrUlSchSwitch
(MbrUlSchSwitch), UeAmbrUlSchSwitch
(UeAmbrUlSchSwitch), UlEnhancedDopplerSwitch
(UlEnhancedDopplerSwitch), UlRaUserSchOptSw
(UlRaUserSchOptSw)
Unit: None
Actual Value Range: SpsSchSwitch, SinrAdjustSwitch,
PreAllocationSwitch, UlVmimoSwitch, TtiBundlingS-
witch, ImIcSwitch, SmartPreAllocationSwitch,
PuschDtxSwitch, UlIblerAdjustSwitch,
UlEnhancedFssSwitch, UlEnhancedSrSchSwitch,
SchedulerCtrlPowerSwitch, UlIicsAlgoSwitch,
UlMinGbrSwitch, UlMbrCtrlSwitch,
MbrUlSchSwitch, UeAmbrUlSchSwitch,
UlEnhancedDopplerSwitch, UlRaUserSchOptSw
Default Value: SpsSchSwitch:Off,
SinrAdjustSwitch:On, PreAllocationSwitch:On,

eRAN

nd
UlVmimoSwitch:Off, TtiBundlingSwitch:Off,
ImIcSwitch:Off, SmartPreAllocationSwitch:Off,
PuschDtxSwitch:On, UlIblerAdjustSwitch:Off,
UlEnhancedFssSwitch:On,
UlEnhancedSrSchSwitch:Off,
SchedulerCtrlPowerSwitch:Off,
UlIicsAlgoSwitch:Off, UlMinGbrSwitch:Off,
UlMbrCtrlSwitch:Off, MbrUlSchSwitch:Off,
UeAmbrUlSchSwitch:Off,
UlEnhancedDopplerSwitch:Off,
UlRaUserSchOptSw:Off

eRAN

nd
ENodeB HoAlgo MOD LBFD-0 Coverag Meaning: Indicates the switches used to enable or
AlgoSwi Switch ENODE 0201801 e Based disable handover algorithms. The switches are
tch BALGO / Intra- described as follows: IntraFreqCoverHoSwitch: If this
SWITC TDLBF frequenc switch is turned on, coverage-based intra-frequency
H D-00201 y handovers are enabled to ensure service continuity. If
LST 801 Handov this switch is turned off, coverage-based intra-
ENODE LBFD-0 er frequency handovers are disabled. InterFreqCoverHoS-
BALGO 0201802 Distance witch: If this switch is turned on, coverage-based inter-
SWITC / Based frequency handovers are enabled to ensure service
H TDLBF Inter- continuity. If this switch is turned off, coverage-based
D-00201 frequenc inter-frequency handovers are disabled.
802 y UtranCsfbSwitch: If this switch is turned on, CSFB to
Handov UTRAN is enabled and UEs can fall back to UTRAN.
LBFD-0 If this switch is turned off, CSFB to UTRAN is disabled.
er
0201804 GeranCsfbSwitch: If this switch is turned on, CSFB to
/ Service
GERAN is enabled and UEs can fall back to GERAN.
TDLBF Based
If this switch is turned off, CSFB to GERAN is disabled.
D-00201 Inter-
Cdma1xRttCsfbSwitch: If this switch is turned on,
804 frequenc
CSFB to CDMA2000 1xRTT is enabled and UEs can
y
LBFD-0 fall back to CDMA2000 1xRTT. If this switch is turned
Handov
0201805 off, CSFB to CDMA2000 1xRTT is disabled.
er
/ UtranServiceHoSwitch: If this switch is turned on,
TDLBF CS service-based handovers to UTRAN are enabled and
D-00201 Fallback UEs using a specific type of services can be handed over
805 to to UTRAN. If this switch is turned off, service-based
UTRAN handovers to UTRAN are disabled. GeranServiceHoS-
LOFD-0
CS witch: If this switch is turned on, service-based
01033 /
Fallback handovers to GERAN are enabled and UEs using a
TDLOF
to specific type of services can be handed over to GERAN.
D-00103
GERAN If this switch is turned off, service-based handovers to
3
CS GERAN are disabled. CdmaHrpdServiceHoSwitch: If
LOFD-0 this switch is turned on, service-based handovers to
Fallback
01034 / CDMA2000 HRPD cells are enabled and UEs using a
to
TDLOF specific type of services can be handed over to
CDMA2
D-00103 CDMA2000 HRPD cells. If this switch is turned off,
000
4 service-based handovers to CDMA2000 HRPD cells
1xRTT
LOFD-0 are disabled. Cdma1xRttServiceHoSwitch: If this
Flash CS switch is turned on, service-based handovers to
01035 / Fallback
TDLOF CDMA2000 1xRTT are enabled and UEs using a
to specific type of services can be handed over to
D-00103 UTRAN
5 CDMA2000 1xRTT. If this switch is turned off, service-
Flash CS based handovers to CDMA2000 1xRTT are disabled.
LOFD-0 Fallback UlQualityInterRATHoSwitch: If this switch is turned
01052 / to on, UL-quality-based inter-RAT handovers are enabled
TDLOF GERAN and UEs can be handed over to inter-RAT cells to ensure
D-00105 service continuity when the UL signal quality is poor.
CS
2 If this switch is turned off, UL-quality-based inter-RAT
Fallback

eRAN

nd
LOFD-0 Steering handovers are disabled. InterPlmnHoSwitch: If this

01053 / to switch is turned on, inter-PLMN handovers are enabled
TDLOF UTRAN and UEs can be handed over to cells in other PLMNs.
D-00105 CS If this switch is turned off, inter-PLMN handovers are
3 Fallback disabled. UtranFlashCsfbSwitch: This switch takes
LOFD-0 Steering effect only when UtranCsfbSwitch is turned on. If
01088 / to UtranFlashCsfbSwitch is turned on, flash CSFB to
TDLOF GERAN UTRAN is enabled and the eNodeB sends system
D-00108 information of candidate target UTRAN cells to UEs
Enhance during redirection. If UtranFlashCsfbSwitch is turned
8
d CS off, flash CSFB to UTRAN is disabled.
LOFD-0 Fallback GeranFlashCsfbSwitch: This switch takes effect only
01089 / to when GeranCsfbSwitch is turned on. If
TDLOF CDMA2 GeranFlashCsfbSwitch is turned on, flash CSFB to
D-00108 000 GERAN is enabled and the eNodeB sends system
9 1xRTT information of candidate target GERAN cells to UEs
LOFD-0 PS Inter- during redirection. If GeranFlashCsfbSwitch is turned
01090 / RAT off, flash CSFB to GERAN is disabled.
TDLOF Mobility ServiceBasedInterFreqHoSwitch: If this switch is
D-00109 between turned on, service-based inter-frequency handovers are
0 E- enabled and UEs using a specific type of services can
LOFD-0 UTRAN be handed over to inter-frequency cells. If this switch is
01019 / and turned off, service-based inter-frequency handovers are
TDLOF UTRAN disabled. UlQualityInterFreqHoSwitch: If this switch is
D-00101 turned on, UL-quality-based inter-frequency handovers
PS Inter-
9 are enabled and UEs can be handed over to inter-
RAT
frequency cells to ensure service continuity when the
LOFD-0 Mobility
UL signal quality is poor. If this switch is turned off,
01020 / between
UL-quality-based inter-frequency handovers are
TDLOF E-
disabled. CsfbAdaptiveBlindHoSwitch: This switch
D-00102 UTRAN
takes effect only when BlindHoSwitch is enabled. If
0 and
CsfbAdaptiveBlindHoSwitch is turned on, adaptive
LOFD-0 GERAN
blind handovers for CSFB are enabled and appropriate
01043 / Service handover mechanisms are selected for UEs based on
TDLOF based their locations. If CsfbAdaptiveBlindHoSwitch is
D-00104 inter- turned off, adaptive blind handovers for CSFB are
3 RAT disabled. UtranCsfbSteeringSwitch: If this switch is
LOFD-0 handove turned on, CSFB steering to UTRAN is enabled and
01046 / r to CSFB policies for UEs in idle mode can be configured.
TDLOF UTRAN If this switch is turned off, CSFB steering to UTRAN is
D-00104 Service disabled. GeranCsfbSteeringSwitch: If this switch is
6 based turned on, CSFB steering to GERAN is enabled and
inter- CSFB policies for UEs in idle mode can be configured.
LOFD-0
RAT If this switch is turned off, CSFB steering to GERAN is
01072 /
handove disabled. CSFBLoadInfoSwitch: If this switch is turned
TDLOF
r to on, load-based CSFB is enabled and a target cell for
GERAN CSFB is selected based on loads of candidate target

eRAN

nd
D-00107 Distance cells. If this switch is turned off, load-based CSFB is

2 based disabled. Cdma1XrttEcsfbSwitch: If this switch is
LOFD-0 inter- turned on, eCSFB to CDMA2000 1xRTT is enabled and
01073 / RAT UEs can fall back to CDMA2000 1xRTT through
TDLOF handove handovers. If this switch is turned off, eCSFB to
D-00107 r to CDMA2000 1xRTT is disabled.
3 UTRAN EmcBlindHoA1Switch: If this switch is turned on, blind
Distance handover event A1 measurements are enabled. If a blind
TDLBF handover event measurement conflicts with a handover
D-00201 based
inter- procedure, an emergency blind handover can be
8 triggered after the handover procedure is complete. If
RAT
TDLOF handove this switch is turned off, blind handover event A1
D-00102 r to measurements are disabled. If a blind handover event
2 GERAN measurement conflicts with a handover procedure, an
TDLOF emergency blind handover cannot be triggered.
Mobility EmcInterFreqBlindHoSwitch: If this switch is turned
D-07022 Manage
8 on, the eNodeB preferentially performs an inter-
ment frequency blind handover when an emergency blind
LOFD-0 Coverag handover is triggered. If this switch is turned off, the
70202 / e Based eNodeB only performs an inter-RAT blind handover
TDLOF Inter- when an emergency blind handover is triggered.
D-07020 frequenc EPlmnSwitch: Indicates whether handovers to
2 y neighboring cells under the equivalent PLMNs
Handov (EPLMNs) are allowed. When inter-PLMN handovers
er are allowed, handovers to neighboring cells under the
SRVCC EPLMNs are allowed if this switch is turned on, and not
to allowed if this switch is turned off. The EPLMNs are
UTRAN delivered by the MME to the UE. ServiceReqInterFreq-
HoSwitch: If this parameter is set to ON, the service
Service-
request-based inter-frequency handover algorithm is
Request
enabled, handing UEs of a specific service to a
Based
frequency in LTE mode. If this parameter is set to OFF,
Inter-
the service request-based inter-frequency handover
frequenc
algorithm is disabled. This parameter is dedicated to
y
LTE TDD cells. VoipHoControlSwitch: Indicates
Handov
whether the eNodeB filters out target cells that do not
er
support VoIP services when processing intra-RAT
Ultra- handovers for VoIP services. UtranFlashCsfbSwitch:
Flash This switch takes effect only when UtranCsfbSwitch is
CSFB turned on. GeranFlashCsfbSwitch: This switch takes
effect only when GeranCsfbSwitch is turned on.
CsfbAdaptiveBlindHoSwitch: This switch takes effect
only when BlindHoSwitch is turned on.
GUI Value Range: IntraFreqCoverHoSwitch
(IntraFreqCoverHoSwitch), InterFreqCoverHoSwitch
(InterFreqCoverHoSwitch), UtranCsfbSwitch

eRAN

nd
(UtranCsfbSwitch), GeranCsfbSwitch
(GeranCsfbSwitch), Cdma1xRttCsfbSwitch
(Cdma20001xRttCsfbSwitch), UtranServiceHoSwitch
(UtranServiceHoSwitch), GeranServiceHoSwitch
(GeranServiceHoSwitch), CdmaHrpdServiceHoS-
witch(Cdma2000HrpdServiceHoSwitch),
Cdma1xRttServiceHoSwitch(Cdma20001xRttService-
HoSwitch), UlQualityInterRATHoSwitch
(UlQualityInterRATHoSwitch), InterPlmnHoSwitch
(InterPlmnHoSwitch), UtranFlashCsfbSwitch(Utran-
FlashCsfbSwitch), GeranFlashCsfbSwitch(Geran-
FlashCsfbSwitch), ServiceBasedInterFreqHoSwitch
(ServiceBasedInterFreqHoSwitch), UlQualityInter-
FreqHoSwitch(UlQualityInterFreqHoSwitch),
CsfbAdaptiveBlindHoSwitch(CsfbAdaptiveBlind-
HoSwitch), UtranCsfbSteeringSwitch(UtranCsfbSteer-
ingSwitch), GeranCsfbSteeringSwitch
(GeranCsfbSteeringSwitch), CSFBLoadInfoSwitch
(CSFBLoadInfoSwitch), Cdma1XrttEcsfbSwitch
(Cdma1XrttEcsfbSwitch), EmcBlindHoA1Switch
(EmcBlindHoA1Switch), EmcInterFreqBlindHoS-
witch(EmcInterFreqBlindHoSwitch), EPlmnSwitch
(EPlmnSwitch), ServiceReqInterFreqHoSwitch
(ServiceReqInterFreqHoSwitch), VoipHoControlS-
witch(VoipHoControlSwitch), UtranUltraFlashCsfbS-
witch(UtranUltraFlashCsfbSwitch)
Unit: None
Actual Value Range: IntraFreqCoverHoSwitch,
InterFreqCoverHoSwitch, UtranCsfbSwitch,
GeranCsfbSwitch, Cdma1xRttCsfbSwitch,
UtranServiceHoSwitch, GeranServiceHoSwitch,
CdmaHrpdServiceHoSwitch, Cdma1xRttServiceHoS-
witch, UlQualityInterRATHoSwitch, InterPlmnHoS-
witch, UtranFlashCsfbSwitch, GeranFlashCsfbSwitch,
ServiceBasedInterFreqHoSwitch, UlQualityInterFreq-
HoSwitch, CsfbAdaptiveBlindHoSwitch,
UtranCsfbSteeringSwitch, GeranCsfbSteeringSwitch,
CSFBLoadInfoSwitch, Cdma1XrttEcsfbSwitch,
EmcBlindHoA1Switch, EmcInterFreqBlindHoSwitch,
EPlmnSwitch, ServiceReqInterFreqHoSwitch,
VoipHoControlSwitch, UtranUltraFlashCsfbSwitch
Default Value: IntraFreqCoverHoSwitch:On,
InterFreqCoverHoSwitch:On, UtranCsfbSwitch:Off,
GeranCsfbSwitch:Off, Cdma1xRttCsfbSwitch:Off,
UtranServiceHoSwitch:Off,
GeranServiceHoSwitch:Off,

eRAN

nd
CdmaHrpdServiceHoSwitch:Off,
Cdma1xRttServiceHoSwitch:Off,
UlQualityInterRATHoSwitch:Off,
InterPlmnHoSwitch:Off, UtranFlashCsfbSwitch:Off,
GeranFlashCsfbSwitch:Off,
ServiceBasedInterFreqHoSwitch:Off,
UlQualityInterFreqHoSwitch:Off,
CsfbAdaptiveBlindHoSwitch:Off,
UtranCsfbSteeringSwitch:Off,
GeranCsfbSteeringSwitch:Off,
CSFBLoadInfoSwitch:Off,
Cdma1XrttEcsfbSwitch:Off,
EmcBlindHoA1Switch:Off,
EmcInterFreqBlindHoSwitch:Off, EPlmnSwitch:Off,
ServiceReqInterFreqHoSwitch:Off,
VoipHoControlSwitch:Off,
UtranUltraFlashCsfbSwitch:Off

eRAN

nd
ENodeB Redirect MOD LBFD-0 Admissi Meaning: Indicates the switch used to enable or disable
AlgoSwi Switch ENODE 02023 / on the redirection algorithm. This switch does not control
tch BALGO TDLBF Control redirection or fast redirection for CSFB.
SWITC D-00202 Congesti GeranFlashRedirectSwitch: If this switch and
H 3 on GeranRedirectSwitch are turned on, fast redirection to
LST LBFD-0 Control GERAN can be performed. UranFlashRedirectSwitch:
ENODE 02024 / If this switch and UtranRedirectSwitch are turned on,
Radio/ fast redirection to UTRAN can be performed.
BALGO TDLBF transport
SWITC D-00202 LoadBasedSwitch: If this switch is turned on, load
resource based redirection can be performed.
H 4 pre-
LOFD-0 emption GUI Value Range: LoadBasedSwitch,
0102901 GeranFlashRedirectSwitch, UranFlashRedirectSwitch
PS Inter-
/ RAT Unit: None
TDLOF Mobility Actual Value Range: LoadBasedSwitch,
D-00102 between GeranFlashRedirectSwitch, UranFlashRedirectSwitch
901 E- Default Value: LoadBasedSwitch:Off,
LOFD-0 UTRAN GeranFlashRedirectSwitch:Off,
01019 / and UranFlashRedirectSwitch:Off
TDLOF UTRAN
D-00101 PS Inter-
9 RAT
LOFD-0 Mobility
01020 / between
TDLOF E-
D-00102 UTRAN
0 and
LOFD-0 GERAN
01021 / PS Inter-
TDLOF RAT
D-00102 Mobility
1 between
E-
UTRAN
and
CDMA2
000

eRAN

nd
Cell LocalCe ACT None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELL identifies a cell within a BS.
ADD GUI Value Range: 0~255
CELL Unit: None
ADD Actual Value Range: 0~255
CELLB
Default Value: None
AND
BLK
CELL
DEA
CELL
DSP
CELL
DSP
CELLP
HYTOP
O
DSP
CELLU
LCOMP
CLUST
ER
DSP
PRIBBP
ADJUS
T
LST
CELL
LST
CELLB
AND
MOD
CELL
RMV
CELL
RMV
CELLB
AND
STR
CELLR
FLOOP
BACK

eRAN

nd
STR
CELLS
ELFTES
T
STR
PRIBBP
ADJUS
T
UBL
CELL
DSP
PRIBBP
RESINF
O
Drx ShortDr MOD LBFD-0 DRX Meaning: Indicates whether to enable or disable short
xSwitch DRX 02017 / DRX cycles. Short DRX cycles reduce the traffic delay.
LST TDLBF GUI Value Range: OFF(Off), ON(On)
DRX D-00201
7 Unit: None
Actual Value Range: OFF, ON
Default Value: ON(On)

eRAN

nd
Drx LongDr MOD LBFD-0 DRX Meaning: Indicates the length of a long DRX cycle that
xCycleS DRX 02017 / is applied only to non-power-saving UEs whose
pecial LST TDLBF subscriber profile ID for RAT/frequency priority
DRX D-00201 (RFSP) indexes are contained in the RFSP index set.
7 Because of the impact of the SRS bandwidth and TA
period specified by the TimeAlignmentTimer
parameter, the actual value of this parameter assigned
to a UE may be less than the configured value. In
addition, the configured value will be rounded down to
an integral multiple of 10. Therefore, you are advised to
configure this parameter to a value that is an integral
multiple of 10. If users hope that the value actually
assigned to a UE is equal to or greater than 80 ms, set
the TimeAlignmentTimer parameter to a value equal to
or greater than 10240 ms. If the TimingAdvCmdOptS-
witch parameter is set to ON, it is recommended that the
LongDrxCycleSpecial parameter be set to a value
smaller than or equal to 320 ms. Otherwise, the uplink
time alignment performance of UEs is affected. If the
TimingAdvCmdOptSwitch parameter is set to ON, it is
recommended that the TimeAlignmentTimer parameter
be set to sf10240. A smaller value of the
TimeAlignmentTimer parameter, such as sf5120,
increases the probability that UEs in DRX mode become
uplink asynchronized.
GUI Value Range: SF10(10 subframes), SF20(20
subframes), SF32(32 subframes), SF40(40 subframes),
SF64(64 subframes), SF80(80 subframes), SF128(128
subframes), SF160(160 subframes), SF256(256
subframes), SF2560(2560 subframes)
Unit: subframe
Actual Value Range: SF10, SF20, SF32, SF40, SF64,
SF80, SF128, SF160, SF256, SF320, SF512, SF640,
SF1024, SF1280, SF2048, SF2560
Default Value: SF10(10 subframes)

eRAN

nd
Drx OnDurat MOD LBFD-0 DRX Meaning: Indicates the length of the On Duration Timer
ionTime DRX 02017 / that applies only to non-power-saving UEs whose RFSP
rSpecial LST TDLBF indexes are contained in the RFSP index set. For details
DRX D-00201 about this timer, see 3GPP TS 36.321. Because of the
7 impact of CQI reporting intervals and SRS transmission
intervals, the actual value of this parameter assigned to
a UE may be greater than the configured value.
GUI Value Range: PSF1(1 PDCCH subframe), PSF2(2
PDCCH subframes), PSF3(3 PDCCH subframes),
PSF4(4 PDCCH subframes), PSF5(5 PDCCH
subframes), PSF6(6 PDCCH subframes), PSF8(8
subframes), PSF200(200 PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5,
PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50,
PSF60, PSF80, PSF100, PSF200
Default Value: PSF5(5 PDCCH subframes)

eRAN

nd
Drx DrxInact MOD LBFD-0 DRX Meaning: Indicates the length of the DRX Inactivity
ivityTim DRX 02017 / Timer that applies only to non-power-saving UEs
erSpecia LST TDLBF whose RFSP indexes are contained in the RFSP index
l DRX D-00201 set. For details about this timer, see 3GPP TS 36.321.
7 GUI Value Range: PSF1(1 PDCCH subframe), PSF2(2
subframes), PSF200(200 PDCCH subframes), PSF300
(300 PDCCH subframes), PSF500(500 PDCCH
subframes), PSF750(750 PDCCH subframes),
PSF1280(1280 PDCCH subframes), PSF1920(1920
PDCCH subframes), PSF2560(2560 PDCCH
subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5,
PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50,
PSF60, PSF80, PSF100, PSF200, PSF300, PSF500,
PSF750, PSF1280, PSF1920, PSF2560
Default Value: PSF10(10 PDCCH subframes)
Drx Support MOD LBFD-0 DRX Meaning: Indicates whether to enable or disable short
ShortDr DRX 02017 / DRX cycles for non-power-saving UEs whose RFSP
xSpecial LST TDLBF indexes are contained in the RFSP index set.
DRX D-00201 GUI Value Range: UU_DISABLE(Disable),
7 UU_ENABLE(Enable)
Unit: None
Actual Value Range: UU_DISABLE, UU_ENABLE
Default Value: UU_DISABLE(Disable)

eRAN

nd
Drx ShortDr MOD LBFD-0 DRX Meaning: Indicates the length of a short DRX cycle that
xCycleS DRX 02017 / is applied only to non-power-saving UEs whose
pecial LST TDLBF subscriber profile ID for RAT/frequency priority
DRX D-00201 (RFSP) indexes are contained in the RFSP index set.
7 According to 3GPP specifications, the length of a long
DRX cycle must be an integer multiple of that of a short
DRX cycle. In addition, the actual value of
LongDrxCycleSpecial assigned to a UE may be less
than the configured value because of the impact of the
SRS bandwidth and TA period specified by the
TimeAlignmentTimer parameter. Therefore, the actual
value of ShortDrxCycleSpecial assigned to a UE may
be less than the configured value.
GUI Value Range: SF2(2 subframes), SF5(5
SF16(16 subframes), SF20(20 subframes), SF32(32
SF80(80 subframes), SF128(128 subframes), SF160
(160 subframes), SF256(256 subframes), SF320(320
subframes)
Unit: subframe
Actual Value Range: SF2, SF5, SF8, SF10, SF16, SF20,
SF32, SF40, SF64, SF80, SF128, SF160, SF256,
SF320, SF512, SF640
Default Value: SF10(10 subframes)
Drx DrxShor MOD LBFD-0 DRX Meaning: Indicates the length of the DRX Short Cycle
tCycleTi DRX 02017 / Timer that applies only to non-power-saving UEs
merSpec LST TDLBF whose RFSP indexes are contained in the RFSP index
ial DRX D-00201 set. The length of this timer is expressed in the number
7 of short DRX cycles. If this parameter is set to 1, the
length of this timer is one short DRX cycle. If this
parameter is set to 2, the length of this timer is two short
DRX cycles. For details, see 3GPP TS 36.321 5.7.
GUI Value Range: 1~16
Unit: None
Default Value: 1

eRAN

nd
CellDrx FddEnte MOD LBFD-0 DRX Meaning: Indicates the threshold for UEs to enter the
Para rDrxThd CELLD 02017 / discontinuous reception (DRX) mode in a cell that
RXPAR TDLBF operates in FDD mode. This threshold is used in the
A D-00201 DRX algorithm. It is expressed as a proportion of the
LST 7 transmission time intervals (TTIs) with data
CELLD transmission to the total TTIs. If the measurement result
RXPAR of UE traffic is equal to or lower than this threshold, the
A eNodeB determines that the UE should remain in DRX
mode or the UE should be triggered to enter DRX mode.
If both the values of the FddExitDrxThd and
FddEnterDrxThd parameters are small and close to each
other, the UE frequently enters and exits the DRX mode.
When both the FddEnterDrxThd parameter and the
FddExitDrxThd parameter are set to 1000 and DRX is
enabled, the eNodeB directly determines that the UE
should enter or exit the DRX mode, but not according
to the measurement result of UE traffic.
Unit: per mill
Default Value: 1000

eRAN

nd
CellDrx FddExit MOD LBFD-0 DRX Meaning: Indicates the threshold for UEs to exit the
Para DrxThd CELLD 02017 / discontinuous reception (DRX) mode in a cell that
RXPAR TDLBF operates in FDD mode. This threshold is used in the
A D-00201 DRX algorithm. It is expressed as a proportion of the
LST 7 transmission time intervals (TTIs) with data
CELLD transmission to the total TTIs. If the measurement result
RXPAR of UE traffic is higher than this threshold, the eNodeB
A determines that the UE should remain in the non-DRX
mode or the UE should be triggered to exit the DRX
mode. If the value of the FddExitDrxThd parameter is
set to 1000 and the value of the FddEnterDrxThd
parameter is set to a value smaller than 1000, the UE
will not exit the DRX mode once entering the DRX
mode. If both the values of the FddExitDrxThd and
FddEnterDrxThd parameters are small and close to each
other, the UE frequently enters and exits the DRX mode.
When both the FddEnterDrxThd parameter and the
FddExitDrxThd parameter are set to 1000 and DRX is
enabled, the eNodeB directly determines that the UE
should enter or exit the DRX mode, but not according
to the measurement result of UE traffic.
Unit: per mill
Default Value: 1000
CellDrx DataAm MOD LBFD-0 DRX Meaning: Indicates the length of the UE traffic
Para ountStat CELLD 02017 / measurement period. The traffic volume of a UE during
Timer RXPAR TDLBF this period is measured. Based on the measurement
A D-00201 result, the DRX algorithm decides whether the UE
LST 7 should enter or exit DRX.
CELLD GUI Value Range: 2~300
RXPAR Unit: 20ms
A
Default Value: 30

eRAN

nd
CnOper CnOper ADD LOFD-0 RAN Meaning: Indicates the index of the operator.
ator atorId CNOPE 01036 Sharing GUI Value Range: 0~5
RATOR LOFD-0 with
Commo Unit: None
LST 01037
CNOPE n Carrier Actual Value Range: 0~5
LOFD-0
RATOR 01086 RAN Default Value: None
MOD Sharing
TDLOF with
CNOPE D-00111
RATOR Dedicate
2 d Carrier
RMV
CNOPE RAN
RATOR Sharing
by More
Operator
s
MOCN
Flexible
Priority
Based
Campin
g

eRAN

nd
InterPlm TarMcc ADD LBFD-0 Coverag Meaning: Indicates the mobile country code of the target
nHoList INTERP 0201801 e Based PLMN.
LMNH / Intra- GUI Value Range: 3 characters
OLIST TDLBF frequenc
D-00201 y Unit: None
LST
INTERP 801 Handov Actual Value Range: 000~999
LMNH LBFD-0 er Default Value: None
OLIST 0201802 Coverag
RMV / e Based
INTERP TDLBF Inter-
LMNH D-00201 frequenc
OLIST 802 y
LBFD-0 Handov
0201804 er
/ Distance
TDLBF Based
D-00201 Inter-
804 frequenc
LBFD-0 y
0201805 Handov
/ er
TDLBF Service
D-00201 Based
805 Inter-
LOFD-0 frequenc
01019 / y
TDLOF Handov
D-00101 er
9 PS Inter-
LOFD-0 RAT
01020 / Mobility
TDLOF between
D-00102 E-
0 UTRAN
and
TDLOF UTRAN
D-00103
3 PS Inter-
RAT
Mobility
between
E-
UTRAN
and
GERAN

eRAN

nd
CS
Fallback
to
UTRAN

eRAN

nd
InterPlm TarMnc ADD LBFD-0 Coverag Meaning: Indicates the mobile network code of the
nHoList INTERP 0201801 e Based target PLMN.
LMNH / Intra- GUI Value Range: 2~3 characters
OLIST TDLBF frequenc
D-00201 y Unit: None
LST
INTERP 801 Handov Actual Value Range: 00~99,000~999
LMNH LBFD-0 er Default Value: None
OLIST 0201802 Coverag
RMV / e Based
INTERP TDLBF Inter-
LMNH D-00201 frequenc
OLIST 802 y
LBFD-0 Handov
0201804 er
/ Distance
TDLBF Based
D-00201 Inter-
804 frequenc
LBFD-0 y
0201805 Handov
/ er
TDLBF Service
D-00201 Based
805 Inter-
LOFD-0 frequenc
01019 / y
TDLOF Handov
D-00101 er
9 PS Inter-
LOFD-0 RAT
01020 / Mobility
TDLOF between
D-00102 E-
0 UTRAN
and
TDLOF UTRAN
D-00103
3 PS Inter-
RAT
Mobility
between
E-
UTRAN
and
GERAN

eRAN

nd
CS
Fallback
to
UTRAN

eRAN
Flexible User Steering Feature Parameter Description 9 Counters
9 Counters
Table 9-1 Counter description
Counter ID Counter Name Counter Feature ID Feature Name

Description
1526728443 L.RRCRel.Dedicate Number of times Multi-mode: None Camp & Handover

dPri.WCDMA.High that the WCDMA GSM: None Based on SPID
network is Camp & Handover
configured as the UMTS: None
Based on SPID
highest frequency LTE:
priority in an LOFD-00105401 Inter-RAT Load
IMMCI IE Sharing to UTRAN
TDLOFD-0010540
1 Inter-RAT Load
Sharing to UTRAN
LOFD-001044
MOCN Flexible
TDLOFD-001044 Priority Based
LOFD-001112 Camping
TDLOFD-001112 MOCN Flexible
Priority Based
Camping

dPri.GERAN.High that GERAN is GSM: None Based on SPID
configured as the Camp & Handover
highest frequency UMTS: None
Based on SPID
priority in an LTE:
IMMCI IE LOFD-00105401 MOCN Flexible
Priority Based
TDLOFD-0010540 Camping
1
MOCN Flexible
LOFD-001112 Priority Based

eRAN

Description

dPri.LTE.High that E-UTRAN is GSM: None Based on SPID
configured as the Camp & Handover
highest frequency UMTS: None
Based on SPID
priority in an LTE:
IMMCI IE LOFD-00105401 MOCN Flexible
Priority Based
1
MOCN Flexible
LOFD-001112 Priority Based
1526728539 L.HHO.InterFreq.R Number of inter- Multi-mode: None Camp & Handover

egainHPLMN.Pre- frequency outgoing GSM: None Based on SPID
pAttOut handover attempts Camp & Handover
triggered for UEs to UMTS: None
Based on SPID
go back to the LTE:
HPLMN LOFD-00105401
TDLOFD-0010540
1
1526728540 L.HHO.InterFreq.R Number of inter- Multi-mode: None Camp & Handover

egainHPLMN.Exe- frequency outgoing GSM: None Based on SPID
cAttOut handover executions Camp & Handover
triggered for UEs to UMTS: None
Based on SPID
go back to the LTE:
HPLMN LOFD-00105401
TDLOFD-0010540
1
1526728541 L.HHO.InterFreq.R Number of Multi-mode: None Camp & Handover

egainHPLMN.Exe- successful inter- GSM: None Based on SPID
cSuccOut frequency outgoing Camp & Handover
handovers triggered UMTS: None
Based on SPID
for UEs to go back to LTE:
the HPLMN LOFD-00105401
TDLOFD-0010540
1
1526728542 L.IRATHO.E2W.R Number of inter- Multi-mode: None Camp & Handover

egainHPLMN.Pre- RAT handover GSM: None Based on SPID
pAttOut attempts from E- Camp & Handover
UTRAN to UMTS: None
Based on SPID
WCDMA network LTE:
triggered for UEs to LOFD-00105401
go back to the TDLOFD-0010540
HPLMN 1

eRAN

Description
1526728543 L.IRATHO.E2W.R Number of inter- Multi-mode: None Camp & Handover

egainHPLMN.Exe- RAT handover GSM: None Based on SPID
cAttOut executions from E- Camp & Handover
UTRAN to UMTS: None
Based on SPID
WCDMA network LTE:
HPLMN 1
1526728544 L.IRATHO.E2W.R Number of Multi-mode: None Camp & Handover

egainHPLMN.Exe- successful inter- GSM: None Based on SPID
cSuccOut RAT handovers Camp & Handover
from E-UTRAN to UMTS: None
Based on SPID
WCDMA network LTE:
HPLMN 1
1526728545 L.ChMeas.PRB.UL Average number of Multi-mode: None Basic Scheduling

.PreSch.Used.Avg PRBs allocated for GSM: None Basic Scheduling
uplink pre-
scheduling UMTS: None UL Pre-allocation
LTE: LBFD-002025 Based on SPID
TDLBFD-002025 UL Pre-allocation
Based on SPID
LOFD-001059
TDLOFD-001059
1526729620 L.HHO.InterFddTd Number of SPID- Multi-mode: None Camp & Handover

d.RegainHPLMN.P based inter-duplex- GSM: None Based on SPID
repAttOut mode outgoing Camp & Handover
handover attempts UMTS: None
Based on SPID
back to the HPLMN LTE:
LOFD-00105401
TDLOFD-0010540
1
1526729621 L.HHO.InterFddTd Number of SPID- Multi-mode: None Camp & Handover

d.RegainHPLMN.E based inter-duplex- GSM: None Based on SPID
xecAttOut mode outgoing Camp & Handover
handover executions UMTS: None
Based on SPID
back to the HPLMN LTE:
LOFD-00105401
TDLOFD-0010540
1

eRAN

Description
1526729622 L.HHO.InterFddTd Number of Multi-mode: None Camp & Handover

d.RegainHPLMN.E successful SPID- GSM: None Based on SPID
xecSuccOut based inter-duplex- Camp & Handover
mode outgoing UMTS: None
Based on SPID
handovers back to LTE:
the HPLMN LOFD-00105401
TDLOFD-0010540
1
1526730016 L.RRCRedirection.I Number of SPID- Multi-mode: None Camp & Handover

nterFddTdd.Re- based inter-duplex- GSM: None Based on SPID
gainHPLMN mode redirections
back to the HPLMN UMTS: None
LTE:
LOFD-00105401
1526730017 L.RRCRedirection. Number of SPID- Multi-mode: None Camp & Handover

E2W.RegainHPLM based redirections GSM: None Based on SPID
N back to a WCDMA
network of the UMTS: None
HPLMN LTE:
LOFD-00105401

eRAN
Flexible User Steering Feature Parameter Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Flexible User Steering Feature Parameter Description 11 Reference Documents
11 Reference Documents
1. 3GPP TS 23.401, "General Packet Radio Service (GPRS) enhancements for Evolved
Universal Terrestrial Radio Access Network (E-UTRAN) access"
2. 3GPP TS 36.300, "E-UTRAN Overall description"
3. DRX and Signaling Control Feature Parameter Description
4. Idle Mode Management Feature Parameter Description
5. Mobility Management in Connected Mode Feature Parameter Description
6. Scheduling Feature Parameter Description


Flexible User Steering (eRAN7.0 - 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Flexible User Steering (eRAN7.0 - 01)

Uploaded by

Copyright:

Available Formats

eRAN

Flexible User Steering Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2014-04-26) Huawei Proprietary and Confidential i

1 About This Document..................................................................................................................1

Issue 01 (2014-04-26) Huawei Proprietary and Confidential ii

Issue 01 (2014-04-26) Huawei Proprietary and Confidential iii

1 About This Document

l LOFD-00105401 Camp & Handover Based on SPID

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

Micro BTS3202E and BTS3203E

1.2 Intended Audience

l Need to understand the features described herein

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 1

1.3 Change History

eRAN7.0 Draft B (2014-03-07)

Change Change Description Parameter Change

Feature None None

Editorial Added 1.4 Differences Between None

eRAN7.0 Draft A (2014-01-20)

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 2

Change Change Description Parameter Change

Feature Added the following counters: None

Editorial None None

1.4 Differences Between eNodeB Types

LOFD-001054 Camp & Yes Yes Yes

LOFD-001059 Pre-allocation Yes Yes Yes

LOFD-070210 Multi Yes Yes Yes

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 3

Function Implementation in Macro, Micro,and LampSite eNodeBs

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 4

Table 2-1 Features related to flexible user steering

LOFD-00105401 Camp & Handover Based l "4.1 Cell Reselection Policy

LOFD-001059 UL Pre-allocation Based on "4.5 Preallocation Policy(LOFD-001059

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 5

2.3 Usage Scenarios

Sub-Feature Usage Scenario

4.1 Cell Reselection Policy l Operators require data-centric UEs (for

4.2 Redirection Policy Operators require UEs to use the

4.3 Load-based Handover Policy Operators allow or do not allow UEs to

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 6

Sub-Feature Usage Scenario

4.4 DRX Policy l Common DRX policies apply to UEs for

4.5 Preallocation Policy(LOFD-001059 UL Operators allow or do not allow UEs to be

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 7

Figure 3-1 Process of transferring an SPID on the entire network

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 8

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 9

4 SPID-specific Flexible Service Policies

Table 4-1 provides examples of UE service policies.

Table 4-1 Examples of UE service policies

UE Parameter and Setting

SpidCf SpidCf SpidCf SpidCf SpidCf SpidCf SpidCf SpidCf

1 1 CFG 1 TRUE FALSE FALSE TRUE FALSE

2 2 NOT_ N/A FALSE TRUE TRUE TRUE TRUE

3 3 NOT_ N/A FALSE TRUE TRUE FALSE TRUE

Issue 01 (2014-04-26) Huawei Proprietary and Confidential 10

4 4 CFG 2 TRUE TRUE FALSE FALSE FALSE

5 5 CFG 4 ... ... ... ... ...