WBB (eRAN15.1 01) PDF

eRAN
WBB Feature Parameter Description
Issue 01
Date 2019-06-06
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. 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: https://www.huawei.com
Email: support@huawei.com
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. i

eRAN
WBB Feature Parameter Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 01 (2019-06-06)............................................................................................................................................1
1.2 eRAN15.1 Draft A (2019-01-05)................................................................................................................................... 1
2 About This Document.................................................................................................................. 4

2.1 General Statements......................................................................................................................................................... 4
2.2 Applicable RAT.............................................................................................................................................................. 5
2.3 Features in This Document.............................................................................................................................................5
2.4 Feature Differences Between FDD and TDD.................................................................................................................5
3 Overview......................................................................................................................................... 6
4 WBB UE Identification and Differentiated QoS Guarantee................................................. 7
4.1 Principles........................................................................................................................................................................ 7
4.1.1 WBB UE Identification............................................................................................................................................... 7
4.1.2 WBB UE Scheduling Priority....................................................................................................................................10
4.1.3 Control over the Maximum PRB Usages of WBB and MBB UEs........................................................................... 11
4.1.4 Dynamic Control over the Maximum Downlink PRB Usage of WBB UEs.............................................................13
4.1.5 SPID-specific DRX Policy........................................................................................................................................ 16
4.1.6 SPID-specific Intra- and Inter-Frequency Handover Processing.............................................................................. 16
4.1.7 Enhanced Uplink Power Control for WBB UEs (TDD)........................................................................................... 16
4.1.8 QoS Control for Concurrent IPTV and Internet Services..........................................................................................16
4.1.9 SPID-based Identification of WBB UEs Capable of Transmit Antenna Selection (TDD)....................................... 17
4.2 Network Analysis......................................................................................................................................................... 18
4.2.1 Benefits...................................................................................................................................................................... 18
4.2.2 Impacts.......................................................................................................................................................................19
4.3 Requirements................................................................................................................................................................ 20
4.3.1 Licenses..................................................................................................................................................................... 20
4.3.2 Software.....................................................................................................................................................................20
4.3.3 Hardware................................................................................................................................................................... 22
4.3.4 Others.........................................................................................................................................................................22
4.4 Operation and Maintenance..........................................................................................................................................23
4.4.1 Data Configuration.................................................................................................................................................... 23
4.4.1.1 Data Preparation..................................................................................................................................................... 23
4.4.1.2 Using MML Commands......................................................................................................................................... 27
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
WBB Feature Parameter Description Contents
4.4.1.3 Using the CME....................................................................................................................................................... 28

4.4.2 Activation Verification.............................................................................................................................................. 28
4.4.3 Network Monitoring.................................................................................................................................................. 30
5 Specified Service Carrier............................................................................................................33

5.1 Principles...................................................................................................................................................................... 33
5.1.1 Overview................................................................................................................................................................... 33
5.1.2 Prohibiting Handovers of Non-Emergency-Call MBB UEs to WBB-Service-Specified Cells................................ 34
5.1.3 Enabling Proactive Handovers of Non-Emergency-Call MBB UEs from WBB-Service-Specified Cells............... 35
5.1.4 Prohibiting Handovers of WBB UEs to MBB-Service-Prioritized Cells..................................................................37
5.1.5 Enabling Proactive Handovers of WBB UEs from MBB-Service-Prioritized Cells.................................................38
5.1.6 WBB and Non-Emergency-Call MBB UE Transfer for MLB.................................................................................. 40
5.1.7 Automatic Non-Common Cell Addition by ANR..................................................................................................... 41
5.2 Network Analysis......................................................................................................................................................... 41
5.2.1 Benefits...................................................................................................................................................................... 42
5.2.2 Impacts.......................................................................................................................................................................42
5.3 Requirements................................................................................................................................................................ 43
5.3.1 Licenses..................................................................................................................................................................... 43
5.3.2 Software.....................................................................................................................................................................44
5.3.3 Hardware................................................................................................................................................................... 44
5.3.4 Networking................................................................................................................................................................ 45
5.3.5 Others.........................................................................................................................................................................46
5.4 Operation and Maintenance..........................................................................................................................................46
5.4.1 Data Configuration.................................................................................................................................................... 46
5.4.1.1 Data Preparation..................................................................................................................................................... 47
5.4.1.2 Using MML Commands......................................................................................................................................... 48
5.4.1.3 Using the CME (FDD)........................................................................................................................................... 52
5.4.1.4 Using the CME (TDD)........................................................................................................................................... 52
5.4.2 Activation Verification.............................................................................................................................................. 52
5.4.3 Network Monitoring.................................................................................................................................................. 52
6 Parameters..................................................................................................................................... 54
7 Counters........................................................................................................................................ 55
8 Glossary......................................................................................................................................... 56
9 Reference Documents................................................................................................................. 57
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
WBB Feature Parameter Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
1.1 eRAN15.1 01 (2019-06-06)

This issue does not include any changes.
1.2 eRAN15.1 Draft A (2019-01-05)

This issue introduces the following changes to eRAN13.1 04 (2018-11-10).
Technical Changes
Change Parameter Change RAT Base Station
Description Model
Replaced the Deleted parameters: FDD l 3900 and 5900

SpidCfg.DlschPrior l SpidCfg.DlschP TDD series base
ityCoeff and riorityCoeff stations
SpidCfg.UlschPrior l DBS3900
ityCoeff parameters l SpidCfg.UlschP
riorityCoeff LampSite and
with the DBS5900
SpidCfg.DlSchPriC LampSite
oeff and
SpidCfg.UlSchPriC l BTS3911E
oeff parameters and l BTS3912E
deleted the original
parameters.
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 1

eRAN

Description Model
Added dynamic Added the FDD l 3900 and 5900

control over the WBB_UE_DL_DY TDD series base
maximum downlink N_PRB_LMT_SW stations
PRB usage of WBB ITCH option to the l DBS3900
UEs. For details, see CellAlgoSwitch.Spe LampSite and
the following cUserAlgoSwitch DBS5900
sections: parameter. LampSite
l 4.1.4 Dynamic Added parameters: l BTS3911E
Control over the l DynCtrlMbbUeP
Maximum l BTS3912E
rbThld.CellWttx
Downlink PRB ParaCfg
Usage of WBB
UEs l DynCtrlUeCntHi
ghPctThld.Cell
l 4.4.1.1 Data WttxParaCfg
Preparation
l DynCtrlUeCntL
l 4.4.1.2 Using owPctThld.Cell
MML WttxParaCfg
Commands
l 4.4.2 Activation
Verification
Added loose control Added the following FDD l 3900 and 5900
over the maximum options to the TDD series base
PRB usage of WBB CellWttxParaCfg.P stations
UEs. For details, see rbUpLimitCtrlMode l DBS3900
4.1.3 Control over parameter: LampSite and
the Maximum PRB l WBB_LOOSE_ DBS5900
Usages of WBB CONTROL LampSite
and MBB UEs.
l LOOSE_CONT l BTS3911E
ROL l BTS3912E

eRAN

Description Model
Added SPID-based Added the TDD l 3900 and 5900

identification of WBB_ANT_SELE series base
WBB antenna CTION_UE_IDEN stations
selection UEs T_SW option to the l DBS3900
(TDD). For details, CellWttxParaCfg. LampSite and
see the following WbbPerformanceO DBS5900
sections: ptSwitch parameter. LampSite
l 4.1.9 SPID-
based
Identification of
WBB UEs
Capable of
Transmit
Antenna
Selection (TDD)
l 4.4.1.1 Data
Preparation
l 4.4.2 Activation
Verification
Editorial Changes
Added the impacts of specified service carriers and LTE spectrum coordination in WTTx
scenarios. For details, see Function Impacts.
Changed the name of Huawei mobile element management system from U2000 to U2020.
Added control over the maximum PRB usages of WBB and MBB UEs in RAN sharing mode.
For details, see 4.1.3 Control over the Maximum PRB Usages of WBB and MBB UEs.
Revised descriptions in this document.

eRAN
WBB Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
This document is intended to acquaint readers with:
l The technical principles of features and their related parameters

l The scenarios where these features are used, the benefits they provide, and the impact
they have on networks and functions
l Requirements of the operating environment that must be met before feature activation
l Parameter configuration required for feature activation, verification of feature activation,
and monitoring of feature performance
This document only provides guidance for feature activation. Feature deployment and feature
gains depend on the specifics of the network scenario where the feature is deployed. To achieve
the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this document
apply only to the corresponding software release. For future software releases, refer to the
corresponding updated product documentation.
Feature Differences Between RATs

The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a description does
not apply to all RATs, the specific RAT that it does apply to will be stated.
For example, in the statement "TDD cells are compatible with enhanced MU-MIMO", "TDD
cells" indicates that this function cannot be used in non-TDD cells.

eRAN
WBB Feature Parameter Description 2 About This Document
2.2 Applicable RAT

This document applies to FDD/TDD.
2.3 Features in This Document

This document describes the following FDD feature.
Feature ID Feature Name Section
LOFD-110223 WBB User Steering 4 WBB UE Identification and

Management Differentiated QoS Guarantee
5 Specified Service Carrier
This document describes the following TDD feature.
Feature ID Feature Name Section
TDLOFD-110223 WBB User Steering 4 WBB UE Identification and

Management Differentiated QoS Guarantee
2.4 Feature Differences Between FDD and TDD

FDD Feature TDD Feature Difference Section
LOFD-110223 TDLOFD-11022 Enhanced uplink power 4 WBB UE

WBB User 3 WBB User control for WBB UEs is Identification and
Steering Steering supported only by Differentiated QoS
Management Management TDD. Guarantee
5 Specified Service
Carrier

eRAN
WBB Feature Parameter Description 3 Overview
3 Overview
Increases in the number of subscribers have slowed down in the communications industry.
Merely enlarging the mobile subscriber base is no longer a sustainable option for operators.
Operators can use idle LTE air interface resources in low-PRB-usage areas, such as suburban
or rural areas, to develop wireless broadband (WBB) services. In this way, operators can
improve the LTE spectral efficiency, develop more profit sources, and seize the broadband
market.
The WBB solution provides broadband access, allowing household and enterprise terminals to
access wireless networks using WBB UEs. Figure 3-1 shows the networking for the WBB
solution.
Figure 3-1 Networking for the WBB solution
WBB UEs are wireless broadband access equipment, usually customer-premises equipment
(CPE). CPEs connect to an eNodeB over the LTE air interface on one side. On the other side,
CPEs connect to terminals in wired mode or using Wi-Fi.

eRAN 4 WBB UE Identification and Differentiated QoS
WBB Feature Parameter Description Guarantee
4 WBB UE Identification and Differentiated

QoS Guarantee
4.1 Principles
The eNodeB identifies WBB UEs based on subscriber profile IDs (SPIDs) or QoS class
identifiers (QCIs) upon UE accesses and implements differentiated QoS guarantee for WBB
and MBB UEs. This fulfills service requirements of WBB UEs, while guaranteeing MBB
service experience.
An SPID and a QCI are defined as follows:
l SPID
An SPID is called an RAT/Frequency Selection Priority (RFSP) on the core network
side. An SPID is the ID of a service configuration file. An operator registers UE SPIDs
(with values from 1 to 256) in a home subscriber server (HSS) database. An eNodeB
performs special processing for the services of the UEs based on these SPIDs.
l QCI
A QCI is a QoS parameter of the EPS bearer. There are two types of QCIs: standardized
and extended. QCIs standardize the QoS requirements of services. Each QCI indicates
the requirements for the resource type, priority, delay, and packet loss rate for each type
of service. For details, see QoS Management.
4.1.1 WBB UE Identification

For WBB UEs, operators customize service policies that are different from those for MBB
UEs. Different WBB UEs may correspond to different service policies. WBB UEs must be
identified for dedicated service provisioning.
The eNodeB can use two methods to identify WBB UEs. The WBB UE identification method
is specified by the CellWttxParaCfg.WbbOrMbbUserDefMode parameter. All cells on a
network must use the same WBB UE identification method. Table 4-1 describes how to select
the method.

Table 4-1 Selecting the WBB UE identification method

Method Value of the Selection Policy
CellWttxParaCfg.
WbbOrMbbUser
DefMode
Parameter
Identification SPID_BASED Use this method if either of the following conditions

based on is met:
SPIDs l MBB UEs use all QCIs for non-guaranteed bit
rate (non-GBR) bearers, and WBB UEs cannot
be distinguished from MBB UEs based on QCIs.
l WBB UEs require the flexible UE measurement
function (for example, SPID-based DRX policy
customization).
Identification QCI_BASED MBB UEs use some of the QCIs for non-GBR
based on bearers, and WBB UEs can use other QCIs for non-
QCIs GBR bearers during registration. For example, MBB
UEs use QCI 9, and WBB UEs use QCI 6 during
registration.
l For the definition of GBR and non-GBR bearers, see Scheduling.

l MBB UEs on the network may be local, intra-RAT roaming, or inter-RAT handed-over MBB UEs.
SPID-based WBB UE identification

Service policies have one-to-one mapping relationship with SPIDs, which are used to identify
WBB UEs in the following manner:
1. During network planning, operators specify service policies for WBB UEs, and
configure the SPIDs on the HSS, mobility management entity (MME), and eNodeB.
– On the eNodeB, the SpidCfg.Spid parameter is used to configure SPIDs.
– (The same SPID is set on the HSS, MME, and eNodeB for a UE.)
2. On an operator's network, the service policies of WBB UEs are communicated to other
NEs through SPID transmission. Figure 4-1 shows the process of transferring an SPID
on the entire network.

Figure 4-1 Process of transmitting an SPID across the entire network
– The eNodeB obtains the SPID from any of the following S1 messages sent by the
MME, including INITIAL CONTEXT SETUP REQUEST, UE CONTEXT
MODIFICATION REQUEST, and DOWNLINK NAS TRANSPORT.
– During an S1-based handover, the source eNodeB transfers the SPID to the target
eNodeB using the HANDOVER REQUIRED (Source eNB to Target eNB
Transparent Container) and HANDOVER REQUEST (Source eNB to Target eNB
Transparent Container) messages.
– During an X2-based handover, the source eNodeB uses the HANDOVER
REQUEST message to transfer the SPID to the target eNodeB.
3. The eNodeB checks whether the obtained SPID is the same as an SPID configured on
the eNodeB. If they are the same, the eNodeB identifies the UE as an SPID-specified
UE.
4. If the SpidCfg.SpecifiedUserFlag parameter is set to SPECSERUSER for the SPID,
the eNodeB identifies the UE as a WBB UE.
l WBB UEs are identified only when they newly access the network or access a cell by handovers or
RRC connection reestablishment. Results of WBB UE identification are used for treatment of
handovers and carrier aggregation (CA).
l SPIDs and the SpecifiedUserFlag parameter set to SPECSERUSER jointly identify WBB UEs.
Therefore, functions provided for specific SPIDs are available to WBB UEs that are identified based
on the SPIDs. For details about SPID-specific functions, see Flexible User Steering.
l The equivalent of SPID on the EPC side is called RFSP.
QCI-based WBB UE identification

During network planning, operators specify QCIs specific to WBB UEs. The EPC allocates
different QCIs to WBB and MBB UEs and informs the eNodeB of the UEs' QCIs during E-

UTRAN radio access bearer (E-RAB) setup. For QCIs specific to WBB UEs, the
CellQciPara.ServiceFlag parameter must be set to WBB_SERVICE.
If an E-RAB of a QCI with this setting is set up for a UE, the eNodeB identifies the UE as a
WBB UE.
The identification procedure is performed during initial context setup for RRC connection
setup. Any changes to the bearer attributes of the UE during the current RRC connection do
not affect the identification result. Therefore, it is not recommended that only bearers of
dedicated QCIs be used to identify WBB UEs.
4.1.2 WBB UE Scheduling Priority

In most cases, services of WBB UEs must have lower priorities than those of MBB UEs. To
ensure differentiated service provision for WBB and MBB UEs, the scheduling priority of
WBB UEs must be adjusted to ensure that the service experience of MBB UEs is
preferentially guaranteed.
Most services provided for WBB UEs are non-guaranteed bit rate (non-GBR) services.
Therefore, the scheduling priority is adjusted only for non-GBR services.
The scheduling priority for WBB UEs is calculated using the following formula:
where
l is the scheduling priority of WBB UEs' non-GBR services.
l is the original scheduling priority of

non-GBR services, excluding the weighting factors of the scheduling priorities specific
to QCIs 6 through 9. For the meanings of the formula variables, see Scheduling.
l is the weighting factor of the QCI-specific scheduling priorities of non-GBR
services. If QCIs are used to identify WBB UEs, WBB and MBB UEs use different
QCIs. can be used to distinguish the scheduling priorities for the two types of UEs.
The QciPara.UlschPriorityFactor and QciPara.DlschPriorityFactor parameters in the
QciPara MO specify the scheduling priority weighting factors for the uplink and
downlink, respectively. A larger value of the weighting factor leads to a higher
scheduling priority. For QCI-specific weighting factor configuration, see QoS
Management.
If SPIDs are used to identify WBB UEs and WBB and MBB UEs use the same QCI, cannot
be used to distinguish the scheduling priorities for the two types of UEs.
l is the weighting coefficient of uplink/downlink scheduling priorities

corresponding to SPID-specific UEs' QCIs (6 through 9). The SpidCfg.UlSchPriCoeff
and SpidCfg.DlSchPriCoeff parameters are recommended to specify .

l The values of and range from 0.001 to 1. The highest precision of eNodeB
scheduling priorities is 0.001. If both and are configured and the product of the
values is less than or equal to 0.001, the eNodeB uses 0.001. After is modified, the
UE must access the network again or be reconfigured to make the modification take effect.
l If QCIs are used to identify WBB UEs, is 1 by default, and concurrent configuration
of and is not recommended.
4.1.3 Control over the Maximum PRB Usages of WBB and MBB
UEs
Control over the maximum PRB usages of WBB and MBB UEs has been introduced to avoid
the following problems:
l WBB UEs use too many PRBs, and MBB user experience is significantly affected.
l MBB UEs use too many PRBs, and no PRBs are available for WBB UEs.
This function is controlled by the WBBMBB_USER_PRB_UP_LMT_SWITCH option of
the CellAlgoSwitch.SpecUserAlgoSwitch parameter.
After the eNodeB identifies WBB UEs in a cell based on SPIDs or QCIs, the rest of the UEs
in this cell are treated as MBB UEs. The maximum PRB usages can be set separately for
WBB and MBB UEs.
Table 4-2 Configuration of the maximum PRB usages for WBB and MBB UEs
UE Type Item Parameter Control
Policy
MBB Upper CellWttxParaCfg.MbbUserDlPrbUpLimit Both tight and

UEs Limit of loose control
DL PRB policies are
Usage for supported. The
MBB User policy type is
configurable.
Upper CellWttxParaCfg.MbbUserUlPrbUpLimit
Limit of
UL PRB
Usage for
MBB User
WBB Upper CellWttxParaCfg.WbbUserDlPrbUpLimit Both tight and

UEs Limit of loose control
DL PRB policies are
Usage for supported. The
WBB User policy type is
configurable.

UE Type Item Parameter Control

Policy
Upper CellWttxParaCfg.WbbUserUlPrbUpLimit
Limit of
UL PRB
Usage for
WBB User
Either tight or loose control can be imposed on the maximum PRB usage. The control policy
is specified by the CellWttxParaCfg.PrbUpLimitCtrlMode parameter.
l If this parameter is set to TIGHT_CONTROL, the PRB usages of MBB and WBB UEs
cannot exceed the upper limit even if there are PRBs remaining in a cell.
l If this parameter is set to MBB_LOOSE_CONTROL and there are still PRBs
remaining in a cell after scheduling of WBB UEs, MBB UEs can use the remaining
PRBs even if the PRB usage of MBB UEs reaches the upper limit. In this case, tight
control is still performed for WBB UEs.
l If this parameter is set to WBB_LOOSE_CONTROL and there are still PRBs
remaining in a cell after scheduling of MBB UEs, WBB UEs can use the remaining
PRBs even if the PRB usage of WBB UEs reaches the upper limit. In this case, tight
control is still performed for MBB UEs.
l If this parameter is set to LOOSE_CONTROL
– If there are still PRBs remaining in a cell after scheduling of WBB UEs, MBB UEs
can use the remaining PRBs even if the PRB usage of MBB UEs reaches the upper
limit.
– If there are still PRBs remaining in a cell after scheduling of MBB UEs, WBB UEs
can use the remaining PRBs even if the PRB usage of WBB UEs reaches the upper
limit.
l Control over the maximum PRB usages of WBB or MBB UEs applies to initial transmission of data
over non-GBR bearers. PRBs used for retransmission, GBR bearers, and transmission of RLC status
reports, TAs, SRs, and signaling are not limited. Therefore:
l PRBs used by WBB and MBB UEs may exceed the configured upper limit.
l If WBB UEs are identified based on QCIs, you are advised not to configure QCIs 1 to 5 as
QCIs used to identify WBB UEs.
l In virtual 4T4R, single frequency network (SFN) and adaptive SFN scenarios, the PRB usages of
WBB and MBB UEs are measured on a per logical cell basis.
l If the CellWttxParaCfg.PrbUpLimitCtrlMode parameter is set to WBB_LOOSE_CONTROL or
LOOSE_CONTROL for the LBBPc, the default value MBB_LOOSE_CONTROL takes effect.
The LBBPc does not support loose control over the maximum PRB usage for WBB UEs.
l In RAN sharing mode, the maximum PRB usages of WBB and MBB UEs must be set based on the
PRB proportion of each operator.
l In RAN sharing with common carrier scenarios (where the CellAlgoSwitch.RanShareModeSwitch
parameter is set to ON), if tight control over the maximum PRB usage is implemented, idle RBs of
an operator cannot be used by other operators. The proportions of uplink and downlink RBs
allocated to an operator cannot exceed the preset thresholds (specified by the
CellOp.OpUlRbUsedRatio and CellOp.OpDlRbUsedRatio parameters respectively).

4.1.4 Dynamic Control over the Maximum Downlink PRB Usage

of WBB UEs
Dynamic control over the maximum downlink PRB usage of WBB UEs has been introduced
to:
l Prevent downlink services of WBB UEs from affecting the downlink experience of MBB
UEs during WBB development.
l Allow WBB UEs to use PRBs allocated to but not used by MBB UEs.
This function can be enabled only if control over the maximum PRB usages of WBB and
MBB UEs is enabled (controlled by the WBBMBB_USER_PRB_UP_LMT_SWITCH
option of the CellAlgoSwitch.SpecUserAlgoSwitch parameter). This function is controlled by
the WBB_UE_DL_DYN_PRB_LMT_SWITCH option of the
CellAlgoSwitch.SpecUserAlgoSwitch parameter. If this option is selected, after the eNodeB
identifies WBB UEs in a cell based on SPIDs or QCIs, the rest of the UEs in this cell are
treated as MBB UEs. After control over the maximum PRB usages of WBB and MBB UEs is
enabled, the eNodeB monitors the load of MBB and WBB UEs and adjusts the maximum
downlink PRB usage of WBB UEs.
Figure 4-2 shows the implementation process of this function. For details about how to
observe the proportion of MBB UEs to WBB UEs, see 4.4.3 Network Monitoring.

Figure 4-2 Process for dynamic control over the maximum downlink PRB usage of WBB UEs
The following table describes the involved thresholds.

No. Parameter Name Parameter ID
1 Dynamic Control MBB UE PRB CellWttxParaCfg.DynCtrlMbbUePrb

Threshold Thld
2 Dynamic Control UE Count High Pct CellWttxParaCfg.DynCtrlUeCntHigh

Thld PctThld
3 Dynamic Control UE Count Low Pct CellWttxParaCfg.DynCtrlUeCntLow

Thld PctThld
Figure 4-3 shows how this function controls the maximum downlink PRB usage of WBB
UEs.

Figure 4-3 Restriction modes for the maximum downlink PRB usage of WBB UEs
Different restriction modes for the maximum downlink PRB usage of WBB UEs are
described as follows:
l No restriction: The maximum downlink PRB usage of WBB UEs is not restricted and
can reach 100%.
l Low restriction mode: The maximum downlink PRB usage of WBB UEs is specified by
the CellWttxParaCfg.WbbUserDlPrbUpLimit parameter.
l High restriction mode: Tighter control is applied on the maximum downlink PRB usage
of WBB UEs, which equals half of the value of the
CellWttxParaCfg.WbbUserDlPrbUpLimit parameter.
The process shown in Figure 4-2 can be simplified by setting
CellWttxParaCfg.DynCtrlUeCntHighPctThld and
CellWttxParaCfg.DynCtrlUeCntLowPctThld to appropriate values based on scenario
requirements. For example:
l If the value of the CellWttxParaCfg.DynCtrlUeCntHighPctThld parameter equals the
value of the CellWttxParaCfg.DynCtrlUeCntLowPctThld parameter, the eNodeB does
not use the low restriction mode.
l For sites serving both WBB and MBB UEs, if the
CellWttxParaCfg.DynCtrlUeCntHighPctThld parameter is set to the maximum value
and has a huge difference from the value of the
CellWttxParaCfg.DynCtrlUeCntLowPctThld parameter, the eNodeB does not use the
high restriction mode. In this case, if the CellWttxParaCfg.DynCtrlUeCntLowPctThld
parameter is set to the minimum value, the eNodeB does not restrict the downlink PRB
usage of WBB UEs only when the PRB usage of MBB UEs is less than or equal to the
preset threshold.
In RAN sharing mode, the eNodeB measures the proportion of MBB UEs to WBB UEs that have
service requirements and the PRB usage of MBB UEs, and uses the results, which are non-operator
specific, to dynamically adjust the restriction mode for all operators.
The eNodeB measures the number of WBB and MBB UEs that have service requirements in the same
way as that used to measure the number of activated UEs. In CA scenarios, the eNodeB measures the
number of WBB and MBB UEs that have service requirements in the PCell.

4.1.5 SPID-specific DRX Policy

WBB UEs are generally stationary and connect to an external power supply, and are not
sensitive to power consumption. Therefore, discontinuous reception (DRX) can be disabled to
optimize the WBB UE scheduling delay and service experience. The SPID-specific DRX
policy can be implemented only in scenarios where SPIDs are configured.
If the CellDrxPara.DrxAlgSwitch parameter is set to ON and the SpidCfg.DrxStatus
parameter is set to FALSE, the eNodeB identifies WBB UEs as special UEs and enables a
special DRX policy for them.
To specify the special DRX treatment for WBB UEs, set related parameters according to
4.4.1.1 Data Preparation. After the parameter setting, the eNodeB considers that WBB UEs
do not enter the sleep time. Therefore, DRX does not take effect for WBB UEs.
For details, see DRX and Signaling Control.
4.1.6 SPID-specific Intra- and Inter-Frequency Handover

Processing
In most cases, WBB UEs are stationary and operators expect no mobility. Therefore, intra-
and inter-frequency handover threshold offset factors are used for WBB UEs to suppress
handovers. In this way, WBB service stability can be improved. Intra- and inter-frequency
handovers can be processed based on SPIDs only when SPIDs are configured.
Intra- and inter-frequency handover threshold offset factors are specified by the
SpidCfg.IntraFreqHoA3OffsetFactor, SpidCfg.InterFreqHoA2RsrpThdFactor, and
SpidCfg.InterFreqHoA2RsrqThdFactor parameters. For details about handover
mechanisms, see Mobility Management in Connected Mode.
4.1.7 Enhanced Uplink Power Control for WBB UEs (TDD)

Enhanced uplink power control for WBB UEs is controlled by the
SpecUePUSCHPcOptSwitch option of the CellAlgoSwitch.UlPcAlgoSwitch parameter. It is
recommended that this function be enabled only when all CPEs in a cell are used indoors.
To implement this function, the eNodeB checks whether a WBB UE identified based on the
SPID or QCI and with an uplink SINR within the range specified in the algorithm has power
headroom and whether the highest MCS index is used for the UE in the uplink. If the UE has
power headroom and does not use the highest MCS index, the eNodeB periodically sends
power control instructions to adjust the UE's transmit power per RB. The function requires
that the SchedulerCtrlPowerSwitch option of the CellAlgoSwitch.UlSchSwitch parameter
be selected to avoid negative gains brought by RBs decreases in special scenarios.
After this function is implemented, WBB UEs transmit signals with higher power per RB and
use higher MCS indexes for transmission under given conditions. This improves uplink
spectral efficiency and allows more uplink data to be transmitted using a given amount of air
interface resources. In this way, uplink capacity of WBB-service-specified cells increases.
4.1.8 QoS Control for Concurrent IPTV and Internet Services

Triple-play packages include Voice over Internet Protocol (VoIP), Internet Protocol television
(IPTV), and internet services. Rates of IPTV services are guaranteed using DSCP-based IPTV
QoS guarantee for WTTx scenarios in the video service rate adaption feature. Per UE
aggregate maximum bit rate (UE-AMBR) control is performed for both internet and IPTV

services if these services are carried by default bearers, because internet service traffic is
limited by packages. For this reason, triple-play packages have the following issues:
l The claimed bandwidth of internet services cannot be reached if air interface resources
are unlimited and internet and IPTV services are concurrent.
l IPTV services cannot be provided if internet traffic packages run out. This is because
when such packages run out, the UE-AMBR is limited to a small value (for example, 1
Mbit/s), but IPTV services require higher rates (for example, 3 Mbit/s for standard
definition).
QoS control for concurrent IPTV and internet services has been added to resolve these issues.
This function is controlled by the QosPolicy.RateControlSwitch parameter.
l If the QosPolicy.RateControlSwitch parameter is set to OFF and bearers of the
corresponding QCI in the QoSPolicy MO carry IPTV services, the eNodeB does not
limit service rates according to the UE-AMBR. In this case, the P-GW limits the per
APN aggregate maximum bit rate (APN-AMBR) for internet services of the UE, while
the IPTV system limits IPTV rates of the UE.
l The eNodeB only has the UE-AMBR, while multiple APN-AMBRs can be configured on the
core network side. The UE-AMBR sent by the core network to the eNodeB is the sum of all
APN-AMBRs.
l If rate control is implemented on the core network side, rates of internet services will not
exceed the corresponding APN-AMBR.
l If the QosPolicy.RateControlSwitch parameter is set to ON and bearers of the
corresponding QCI in the QoSPolicy MO do not carry IPTV services, the eNodeB limits
service rates according to the UE-AMBR.
QoS control for concurrent IPTV and internet services is dependent on DSCP-based IPTV
QoS guarantee in WTTx scenarios. For details about DSCP-based IPTV QoS guarantee in
WTTx scenarios, see Video Experience Optimization.
4.1.9 SPID-based Identification of WBB UEs Capable of Transmit

Antenna Selection (TDD)
In WBB/MBB hybrid networking mode, WBB UEs correctly report their support for transmit
antenna selection. However, MBB UEs may falsely report that they support transmit antenna
selection. If a cell serves MBB UEs that falsely report their support for transmit antenna
selection, transmit antenna selection is disabled in the cell. WBB UEs in this cell cannot enjoy
the gains from transmit antenna selection. This function configures transmit antenna selection
for WBB UEs based on the reported UE capability information and disables transmit antenna
selection for MBB UEs. This ensures the gains from transmit antenna selection for WBB
UEs.
For the definition of UEs that falsely report their support for transmit antenna selection, see Massive
MIMO (TDD).
This function applies only to WBB UEs identified based on SPIDs in massive MIMO cells.
This function configures transmit antenna selection based on the reported UE capability
information. Figure 4-4 shows the process.

Figure 4-4 Process for SPID-based identification of WBB UEs capable of transmit antenna
selection
4.2 Network Analysis
4.2.1 Benefits
WBB UE identification and specified QoS guarantee offers the following benefits:
l Higher spectral efficiency

Operators can use idle LTE air interface resources in low-PRB-usage areas, such as
suburban or rural areas, to develop WBB services, improve the LTE spectral efficiency,
increase the source of profits, and increase broadband market share.
l Identification of WBB UEs for the provisioning of differentiated services for them using
the following functions and settings:
Scheduling priorities for WBB UEs, control over the maximum PRB usage of WBB and
MBB UEs, SPID-specific DRX policy, WBB and MBB UE transfer for mobility load
balancing (MLB), and intra- and inter-frequency handover processing specific to SPIDs
These functions enable operators to develop WBB services while preserving MBB user
experience.
l Higher uplink capacity in WBB-service-specified cells
Enhanced uplink power control for WBB UEs increases the power per RB for such UEs
and the MCS index under the same conditions. This improves uplink spectral efficiency
and transmits more uplink data using the same amount of air interface resources.

If operators want to use idle LTE air interface resources in low-PRB-usage areas, such as
suburban or rural areas, to develop WBB services, the WBB UE identification and
differentiated QoS guarantee feature is recommended. By using this feature, operators can
develop WBB services and also ensure MBB service experience.
If CPEs are deployed indoors, more than 50% of cells have an average PUSCH SINR less
than 10 dB, and uplink cell capacity needs to be improved, enhanced uplink power control for
WBB UEs is recommended.
4.2.2 Impacts
Network Impacts
l System capacity
After tight control over the maximum PRB usage of WBB UEs or tight control over the
maximum PRB usage of MBB UEs is enabled, the eNodeB restricts the scheduling of
WBB or MBB UEs if their PRB usage reaches the upper limit. In this case, the cell
throughput decreases.
Enhanced uplink power control for WBB UEs can improve the uplink capacity of WBB-
service-specified cells if WBB UEs in these cells meet the criteria for performing this
function.
If QoS control for concurrent IPTV and internet services is enabled, capacity is
improved. This is because IPTV UEs have better air interface quality than common UEs,
and IPTV traffic is continuous. The number of UEs running IPTV services must not
exceed capacity specifications expressed in terms of the number of UEs for which IPTV
services are provided. Otherwise, capacity will be insufficient after this function is
enabled, affecting performance of IPTV services.
l Network performance
When WBB UEs are identified:
– After the scheduling priority weighting coefficients are configured, WBB user
experience is inferior to MBB user experience. MBB user experience is
preferentially ensured.
– Control over the maximum PRB usage of WBB UEs reduces the impact of network
load increase on MBB user experience. Control over the maximum PRB usage of
MBB UEs ensures resource reservation for WBB UEs, especially during busy
hours.
– Differentiated configuration of DRX parameters shortens the scheduling delay,
improving WBB user experience.
– Differentiated configuration of handover threshold offset factors prevents WBB
UEs from performing ping-pong handovers.
Enhanced uplink power control for WBB UEs increases the uplink transmit power of
targeted WBB UEs. This will lead to slight increases in the average interference to
neighboring cells in scenarios of short inter-site distances.
After dynamic control over the maximum downlink PRB usage of WBB UEs is enabled,
if the PRB usage of MBB UEs and the proportion of MBB UEs to WBB UEs that have
service requirements reach the preset thresholds, the eNodeB restricts the scheduling of
WBB UEs. As a result, the cell throughput decreases.
After SPID-based identification of WBB UEs capable of transmit antenna selection is
enabled, MBB UEs that support transmit antenna selection cannot enjoy the gains from
transmit antenna selection. As a result, the experience of these MBB UEs is affected.

Function Impacts
RAT Function Function Reference Description
Name Switch
FDD RAN Sharing CellAlgoSwitc RAN Sharing In RAN sharing with

TDD with Common h.RanShareMo common carrier
Carrier deSwitch scenarios, if tight
control over the
maximum PRB
usage is
implemented, the
proportions of RBs
allocated to an
operator cannot
exceed the preset
thresholds.
4.3 Requirements
4.3.1 Licenses
FDD: None
TDD: Enhanced uplink power control for WBB UEs requires the following license control
item. Other functions are not under license control.
Feature ID Feature Name Model Sales Unit
TDLOFD-1302 Enhanced WTTx LT1SEHWUPC00 Per Cell

01 Uplink Power Control
4.3.2 Software
Prerequisite Functions
Name Switch
FDD Flexible user SpidCfg.Spid Flexible User WBB UEs are

TDD steering Steering identified based on
SPIDs.


Name Switch
FDD CQI adjustment CqiAdjAlgoSw Channel State Scheduling

TDD itch option of Management functions are
the required to adjust
CellAlgoSwitc scheduling priorities
h.CqiAdjAlgoS and QoS parameters
witch parameter for WBB UEs.
FDD Dynamic AbnUeSchSwit Scheduling

TDD scheduling ch option of the
CellAlgoSwitc
h.CellSchStrate
gySwitch
parameter
TDD Power control SchedulerCtrl Scheduling It is recommended

by scheduler PowerSwitch that this function be
option of the used with enhanced
CellAlgoSwitc uplink power control
h.UlSchSwitch for WBB UEs to
parameter avoid negative gains
caused by RB
decreases in special
scenarios.
FDD DSCP-based VideoRateAda Video QoS control for

TDD IPTV QoS ptSwitch Experience concurrent IPTV
guarantee in option of the Optimization and internet services
WTTx CellAlgoSwitc is dependent on this
scenarios h.ServiceDiffS function.
witch parameter
Mutually Exclusive Functions

Name Switch
FDD Multi-operator None RAN Sharing If WBB UE

TDD SPID policy identification and
differentiated QoS
guarantee is enabled,
the multi-operator
SPID policy cannot
be implemented,
because operators
cannot be
distinguished by
SPIDs.


Name Switch
FDD DACQ CellAlgoSwitc Rate Control Control over the

TDD h.DacqSwitch Based on User maximum PRB
Types usage of WBB and
MBB UEs cannot be
used with dynamic
AMBR control by
QCI (DACQ).
4.3.3 Hardware
Base Station Models

l The following base stations are compatible with QoS control for concurrent IPTV and
internet services:
– 3900 and 5900 series base stations
– DBS3900 LampSite and DBS5900 LampSite
– BTS3911E
– BTS3912E
l Enhanced uplink power control for WBB UEs (TDD) applies only to 3900 and 5900
series base stations.
l Other functions are supported by all base station models.
Boards
l Dynamic control over the maximum downlink PRB usage of WBB UEs: All boards,
except for the LBBPc, support this function.
l Loose control over the maximum PRB usage of WBB UEs: All boards, except for the
LBBPc, support this function.
l Other functions: no requirements
RF Modules
No requirements
4.3.4 Others
The following information must be collected for configuration:
l QCI usage of MBB UEs that are already registered on the network
l Whether the HSS and MME support configuration of SPIDs and whether the MME
supports SPID transfer on the live network
l UE policies specific to each SPID and QCI, the number of registered WBB UEs,
activation ratio of WBB UEs, and tariff policies for these UEs, which are required to
configure different QoS policies between WBB and MBB UEs. UE policies include the
scheduling priority weighting factor of WBB UEs, PRB usage upper limits for WBB and

MBB UEs, DRX application policies, and threshold offset configuration policies for
handovers.
The equivalent of SPID on the EPC side is called RFSP.
QoS control for concurrent IPTV and internet services requires support of the core network.
The core network must limit traffic of internet services. Otherwise, traffic of internet services
cannot be limited.
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation
Table 4-3 Parameter that specifies the WBB UE identification mode
Parameter Name Parameter ID Setting Notes
WBB or MBB User CellWttxParaCfg.Wbb See 4.1.1 WBB UE

Definition Mode OrMbbUserDefMode Identification.
Table 4-4 Parameters related to scheduling priorities of WBB UEs (identified based on
SPIDs)
Spid SpidCfg.Spid Set the same SPID on the HSS,

MME, and eNodeB.
Specified User Flag SpidCfg.SpecifiedUserF Set this parameter to

lag SPECSERUSER for WBB UEs.
UL Scheduling Priority SpidCfg.UlSchPriCoeff Set this parameter according to the

Coeff scheduling priority policies of
MBB and WBB services.
DL Scheduling Priority SpidCfg.DlSchPriCoeff
Coeff
Table 4-5 Parameters related to scheduling priorities of WBB UEs (identified based on QCIs)
Service Flag CellQciPara.ServiceFla Set this parameter to

g WBB_SERVICE for WBB UEs.

Uplink Scheduling QciPara.UlschPriorityF Set this parameter according to the

Priority Factor actor scheduling priority policies of
MBB and WBB services.
Downlink Scheduling QciPara.DlschPriorityF
Priority Factor actor l The default value or a larger
value is recommended for
MBB services.
l For WBB services, a value
smaller than that for MBB
services is recommended.
Table 4-6 Parameters for controlling the maximum PRB usage of WBB and MBB UEs
Specified User CellAlgoSwitch.SpecUs Select the

Algorithm Switch erAlgoSwitch WBBMBB_USER_PRB_UP_L
MT_SWITCH option of this
parameter.
Upper Limit of DL PRB CellWttxParaCfg.Mbb In most cases, this parameter is not

Usage for MBB User UserDlPrbUpLimit recommended because it will
affect MBB user experience.
Upper Limit of UL PRB CellWttxParaCfg.Mbb
Usage for MBB User UserUlPrbUpLimit Set this parameter if operators
want to reserve PRBs for WBB
UEs. For this purpose, you are
advised to set the
CellWttxParaCfg.PrbUpLimitCtr
lMode parameter at the same time.
Upper Limit of DL PRB CellWttxParaCfg.Wbb Set this parameter based on the

Usage for WBB User UserDlPrbUpLimit number of registered WBB UEs
and the subscribed service
Upper Limit of UL PRB CellWttxParaCfg.Wbb policies.
Usage for WBB User UserUlPrbUpLimit
PRB Upper Limit CellWttxParaCfg.PrbU Set this parameter to

Control Mode pLimitCtrlMode MBB_LOOSE_CONTROL.
l The same PRB usage upper limit settings are recommended for all cells in the network. If cells have
different settings of the PRB usage upper limits, the UE throughput may decrease in uplink CA
scenarios.
l In a RAN sharing scenario, operators must use the same PRB usage upper limit settings for both
MBB and WBB UEs.
l After the PRB usage upper limit parameters are modified in the CellWttxParaCfg MO, the PRB
usage of online UEs may be incorrectly measured. It can be correctly measured only after the UEs
reaccess the network.

Table 4-7 Parameters for dynamic control over the maximum downlink PRB usage of WBB
UEs
Specified User CellAlgoSwitch.SpecUs Select the

Algorithm Switch erAlgoSwitch WBB_UE_DL_DYN_PRB_LMT
_SWITCH option.
Dynamic Control MBB CellWttxParaCfg.DynC Set this parameter based on the

UE PRB Threshold trlMbbUePrbThld network plan.
Dynamic Control UE CellWttxParaCfg.DynC Set this parameter based on the

Count High Pct Thld trlUeCntHighPctThld number of WBB and MBB UEs
and service characteristics.
Dynamic Control UE CellWttxParaCfg.DynC
Count Low Pct Thld trlUeCntLowPctThld The UEs measured are those that
have service requirements. Refer
to the counter that measures the
number of activated UEs on the
live network.
Table 4-8 Parameters of the SPID-specific DRX policy

Local Cell ID CellDrxSpecialPara.Loc None

alCellId
Long DRX Cycle for CellDrxSpecialPara.Lo Set this parameter to SF10.

Special UE ngDrxCycleSpecial
DRX onDurationTimer CellDrxSpecialPara.On l SA0: Set this parameter to

for Special UE DurationTimerSpecial PSF4.
l SA1 or SA3: Set this parameter
to PSF6.
l SA2 or SA4: Set this parameter
to PSF8.
Short DRX Cycle Switch CellDrxSpecialPara.Sh Set this parameter to

for Special UE ortDrxCycleSwitchSpe- UU_DISABLE.
cial
For other DRX parameter settings for special UEs, see DRX and Signaling Control.

Table 4-9 Parameters for SPID-specific intra- and inter-frequency handover processing
Intra-Freq Handover SpidCfg.IntraFreqHoA3 Set this parameter according to the

Offset Factor OffsetFactor handover advance and delay
policies of WBB services.
Inter-Freq A2 RSRP SpidCfg.InterFreqHoA2
Threshold Factor RsrpThdFactor
Inter-Freq A2 RSRQ SpidCfg.InterFreqHoA2

Threshold Factor RsrqThdFactor
Table 4-10 Parameters for enhanced uplink power control for WBB UEs (TDD)
Parameter Parameter ID Option Setting Notes
Name
Uplink power CellAlgoSwitc SpecUePUSCH You are advised to select this

control h.UlPcAlgoSwi PcOptSwitch option to enable enhanced uplink
algorithm tch power control for WBB UEs in a
switch cell far away from other cells and
in which all CPEs are used
indoors.
Uplink schedule CellAlgoSwitc SchedulerCtrlP You are advised to select this

switch h.UlSchSwitch owerSwitch option if enhanced uplink power
control for WBB UEs is enabled to
avoid negative gains due to RB
reduction in special scenarios.
Table 4-11 Parameters for QoS control for concurrent IPTV and internet services
Rate Control Switch QosPolicy.RateControlS Set this parameter to OFF2 if

witch IPTV services are ongoing and
traffic included in the packages is
limited1.
Set this parameter to ON in other
scenarios.
1. Service packages have limited traffic and limit UE rates when IPTV services are ongoing and traffic
runs out, causing IPTV service exceptions.
2. The value OFF indicates that QoS control is enabled for concurrent IPTV and internet services.

Table 4-12 Parameters for SPID-based identification of WBB UEs capable of transmit
antenna selection (TDD)
Parameter Parameter ID Option Setting Notes
Name
WBB CellWttxPara WBB_ANT_SE In the WBB/MBB hybrid

Performance Cfg.WbbPerfor LECTION_UE networking mode where some
Optimization manceOptSwitc _IDENT_SW MBB UEs falsely report that they
Switch h support transmit antenna selection,
it is recommended that this option
be selected.
4.4.1.2 Using MML Commands
Activation Command Examples (SPID-based WBB UE Identification)

//Specifying the basis of WBB UE identification
MOD CELLWTTXPARACFG: LocalCellId=0, WbbOrMbbUserDefMode=SPID_BASED;
//Checking whether DRX can be disabled for WBB UEs
//Checking whether the DRX feature switch is turned on (if yes, DRX for WBB UEs
can be disabled)
LST CELLDRXPARA: ;
//Configuring parameters for the scheduling priority of WBB UEs, SPID-based
intra- and inter-frequency handover processing, and SPID-based DRX policy
ADD SPIDCFG:Spid=1,DlSchPriCoeff =1, UlSchPriCoeff
=1,IntraFreqHoA3OffsetFactor=4,InterFreqHoA2RsrpThdFactor=-2,InterFreqHoA2RsrqThdF
actor=-2,DrxStatus= FALSE,SpecifiedUserFlag=SPECSERUSER;
//(Optional) Disabling DRX for WBB UEs (the DRX feature switch is off in the LST
DRX command output and is on in the LST CELLDRXPARA command output)
//Uplink and downlink subframe configuration SA0 is taken as an example.
MOD
CellDrxSpecialPara:LocalCellId=0,ShortDrxCycleSwitchSpecial=UU_DISABLE,LongDrxCycl
eSpecial=SF10,OnDurationTimerSpecial=PSF4;
//Configuring the maximum PRB usages for WBB and MBB UEs
MOD CELLALGOSWITCH: LocalCellId=0,
SpecUserAlgoSwitch=WBBMBB_USER_PRB_UP_LMT_SWITCH-1;
MOD CELLWTTXPARACFG: LocalCellId=0, MbbUserDlPrbUpLimit=100,
MbbUserUlPrbUpLimit=100, WbbUserDlPrbUpLimit=50, WbbUserUlPrbUpLimit=50,
PrbUpLimitCtrlMode=MBB_LOOSE_CONTROL;
//(Optional) Enabling dynamic control over the maximum downlink PRB usage of WBB
UEs based on control over the maximum PRB usages of WBB and MBB UEs
SpecUserAlgoSwitch=WBB_UE_DL_DYN_PRB_LMT_SWITCH-1;
MOD CELLWTTXPARACFG: LocalCellId=0, DynCtrlMbbUePrbThld=20,
DynCtrlUeCntHighPctThld=40, DynCtrlUeCntLowPctThld=20;
//(Optional) Enabling enhanced uplink power control for WBB UEs (TDD)
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch= SchedulerCtrlPowerSwitch-1,
UlPcAlgoSwitch= SpecUePUSCHPcOptSwitch-1;
//Enabling QoS control for concurrent IPTV and internet services
MOD QOSPOLICY: QosPolicyId=5, RateControlSwitch=OFF;
//(Optional) Enabling SPID-based identification of WBB UEs capable of transmit
antenna selection (TDD)
MOD ENODEBALGOSWITCH: CompatibilityCtrlSwitch=UeSRSAntSelectCtrlSwitch-0;
MOD CELLWTTXPARACFG: LocalCellId=0, WbbPerformanceOptSwitch=
WBB_ANT_SELECTION_UE_IDENT_SW-1;
Activation Command Examples (QCI-based WBB UE Identification)

//Specifying the basis of WBB UE identification
MOD CELLWTTXPARACFG: LocalCellId=0, WbbOrMbbUserDefMode=QCI_BASED;
//Configuring the service flag for a QCI

MOD CELLQCIPARA: LocalCellId=0, Qci=6, ServiceFlag=WBB_SERVICE;

//Configuring the scheduling priority parameters for WBB UEs
MOD QCIPARA: Qci=6,DlschPriorityFactor=100, UlschPriorityFactor=100;
//Configuring the maximum PRB usages for WBB and MBB UEs
MOD CELLWTTXPARACFG: LocalCellId=0, MbbUserDlPrbUpLimit=100,
MbbUserUlPrbUpLimit=100, WbbUserDlPrbUpLimit=50, WbbUserUlPrbUpLimit=50,
PrbUpLimitCtrlMode=MBB_LOOSE_CONTROL;
//(Optional) Enabling dynamic control over the maximum downlink PRB usage of WBB
UEs based on control over the maximum PRB usages of WBB and MBB UEs
MOD CELLWTTXPARACFG: LocalCellId=0, DynCtrlMbbUePrbThld=20,
DynCtrlUeCntHighPctThld=40, DynCtrlUeCntLowPctThld=20;
//(Optional) Enabling enhanced uplink power control for WBB UEs (TDD)
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch= SchedulerCtrlPowerSwitch-1,
UlPcAlgoSwitch= SpecUePUSCHPcOptSwitch-1;
//Enabling QoS control for concurrent IPTV and internet services
MOD QOSPOLICY: QosPolicyId=5, RateControlSwitch=OFF;
Deactivation Command Examples

//Removing the SPID configuration
RMV SPIDCFG:Spid=1;
//Restoring the default value of the service flag for WBB UEs
MOD CELLQCIPARA: LocalCellId=0, Qci=6, ServiceFlag=NONE;
//Setting the scheduling priority parameters to the default values for WBB UEs
MOD QCIPARA: Qci=6, DlschPriorityFactor=700, UlschPriorityFactor=700;
//Disabling dynamic control over the maximum downlink PRB usage of WBB UEs
//Disabling control over the PRB usages of WBB and MBB UEs
//Disabling enhanced uplink power control for WBB UEs (TDD)
MOD CELLALGOSWITCH: LocalCellId=0, UlPcAlgoSwitch= SpecUePUSCHPcOptSwitch-0,
UlSchSwitch= SchedulerCtrlPowerSwitch-0;
//Disabling QoS control for concurrent IPTV and internet services
MOD QOSPOLICY: QosPolicyId=5, RateControlSwitch=ON;
//Disabling SPID-based identification of WBB UEs capable of transmit antenna
selection (TDD)
MOD CELLWTTXPARACFG: LocalCellId=0, WbbPerformanceOptSwitch=
WBB_ANT_SELECTION_UE_IDENT_SW-0;
4.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.
4.4.2 Activation Verification
SPID Sent by the EPC

Step 1 Enable a WBB UE to access a cell.
Step 2 On the U2020, choose Monitor > Signaling Trace > Signaling Trace Management > S1
Interface Trace to create an S1 interface tracing task. If the
S1AP_INITIAL_CONTEXT_SETUP_REQ message traced over the S1 interface includes a
subscriberProfileIdforRFP IE, the EPC sends the SPID.
----End

WBB UE Scheduling Priority

Step 1 Ensure that the WBB and MBB UEs have the same location, channel quality, and bearer type.
Perform full packet injection in the uplink or downlink.
Step 2 Set the SpidCfg.UlSchPriCoeff or SpidCfg.DlSchPriCoeff parameter to 10, 100, and then
1000, and check the ratio of the WBB UEs' throughput to the MBB UEs' throughput in the
case of different values. If the ratio is increasing with the increase of the value, the
configuration of scheduling priority weighting coefficient has taken effect.
----End
Control over the Maximum PRB Usage of WBB and MBB UEs
Step 1 Perform full packet injection for both WBB and MBB UEs in the uplink or downlink.
Step 2 Check the PRB usage of the WBB and MBB UEs. If the actual PRB usage of UEs
approximates the configured uplink or downlink upper limits in a tight control scenario, the
control over the maximum PRB usage of WBB and MBB UEs is exerted.
----End
During massive MIMO pairing, the upper PRB usage limit is evaluated using the following formula:
(Average number of PDSCH PRBs used by WBB UEs/Average number of PRBs used by DRBs) x
(Number of PRBs used in the downlink/Number of PRBs available in the downlink)
SPID-specific DRX Policy

Step 1 Enable a WBB UE to access a cell, and ensure that the DRX-triggering conditions are met.
For details, see DRX and Signaling Control.
Step 2 On the U2020, choose Monitor > Signaling Trace > Signaling Trace Management > Uu
Interface Trace to create a Uu interface tracing task. Then, view the content of the
RRC_CONN_RECFG message traced over the Uu interface. If the message does not include
drx-Config, the DRX function is disabled for the WBB UE.
----End
Dynamic Control over the Maximum Downlink PRB Usage of WBB UEs
Step 1 Enable both WBB and MBB UEs to perform downlink services. Adjust the number of UEs
based on the proportion of activated UEs, downlink PRBs used by MBB UEs, and preset
thresholds.
Step 2 Observe the downlink PRB usage of WBB UEs. If the downlink PRB usage of WBB UEs is
controlled using a suitable restriction mode selected based on the proportion of MBB UEs and
WBB UEs that have service requirements, dynamic control over the maximum downlink PRB
usage of WBB UEs has taken effect.
----End
SPID-specific Intra- and Inter-Frequency Handover Processing

Step 1 Enable a WBB UE to access a cell.

Step 2 Run the LST SPIDCFG command. In the command output, if the value of any of the
following parameters is not 0, SPID-specific intra- and inter-frequency handover processing
has been activated:
l Intra-Freq Handover Offset Factor
l Inter-Freq A2 RSRP Threshold Factor
l Inter-Freq A2 RSRQ Threshold Factor
----End
Enhanced Uplink Power Control for WBB UEs

Observe counters L.UL.RSRP.PUSCH.Index0 through L.UL.RSRP.PUSCH.Index23 to
determine whether this function has taken effect. If the proportion of high RSRPs on the
PUSCH increases, this function has taken effect.
QoS Control for Concurrent IPTV and Internet Services

Step 1 Deploy IPTV environments according to Video Experience Optimization and perform rate
guarantee for IPTV services using DSCP-based IPTV QoS guarantee in WTTx scenarios.
Step 2 Run the LST QOSPOLICY command to query the setting of the rate control switch.
l If this switch is on, run the MOD QOSPOLICY command with the
QosPolicy.RateControlSwitch parameter set to OFF. Then, go to the next step.
l If this switch is off, go to the next step.
Step 3 Run MML commands to perform UDP packet injection for UEs running IPTV services and
observe downlink rates of these UEs. If downlink rates of the UEs exceed the AMBR
assigned by the EPC, this function has taken effect.
----End
SPID-based Identification of WBB UEs Capable of Transmit Antenna Selection

(TDD)
Step 1 Enable WBB and MBB UEs that support transmit antenna selection to access the cell.
Step 2 Observe the RRC_CONN_RECFG message in the network access signaling of the two UEs.
If the value of the ue-TransmitAntennaSelection field in this message is true for the WBB UE
and is false for the MBB UE, this function has taken effect.
----End
4.4.3 Network Monitoring

RAT Counter Counter Name Description
ID
FDD/ 152672896 L.Traffic.ActiveUser.DL.Av Average number of activated UEs

TDD 9 g in downlink
FDD/ 152674595 L.Traffic.User.WBB.Avg Average number of WBB UEs in a

TDD 5 cell


ID
FDD/ 152674588 L.Traffic.ActiveUser.DL.W Average number of WBB UEs

TDD 5 BB.Avg activated in the downlink
FDD/ 152674588 L.Traffic.ActiveUser.UL.W Average number of WBB UEs

TDD 7 BB.Avg activated in the uplink
FDD/ 152674595 L.ChMeas.PRB.DL.PDSCH Average number of PRBs used for

TDD 4 .WBBUsed.Avg PDSCH transmission for WBB
UEs in the downlink
FDD/ 152674595 L.ChMeas.PRB.PUSCH.W Average number of PRBs used for

TDD 7 BBUsed.Avg PUSCH transmission for WBB
UEs in the uplink
FDD/ 152674587 L.Thrp.bits.DL.WBB Total traffic volume of downlink

TDD 9 PDCP SDUs sent for WBB UEs in
a cell
FDD/ 152674588 L.Thrp.bits.DL.LastTTI.W Traffic volume of downlink PDCP

TDD 0 BB SDUs sent for WBB UEs in the
last TTI before the buffer is empty
FDD/ 152674588 L.Thrp.Time.DL.RmvLastT WBB UE data transmission

TDD 1 TI.WBB duration except the last TTI before
the buffer is empty
FDD/ 152674588 L.Thrp.bits.WBB.UL.Exper Traffic volume of uplink PDCP

TDD 2 ienced SDUs sent for WBB UEs in a cell
from the time the uplink buffer of
the UEs is not empty to the time
the uplink buffer of the UEs is
empty
FDD/ 152674588 L.Thrp.Time.WBB.UL.Exp Uplink data transmission duration

TDD 3 erienced from the time the uplink buffer of
WBB UEs is not empty to the time
the uplink buffer of the UEs is
empty in a cell
FDD/ 152674047 L.Traffic.SpecSerUser.Avg Average number of UEs running

TDD 8 specified services
FDD/ 152674873 L.Thrp.Time.UE.UL.RmvL Uplink data transmit duration

TDD 9 astTTI.WBB except the last TTI of WBB UEs
before the UE buffer is empty
FDD/ 152674874 L.Thrp.bits.UE.UL.LastTTI Traffic volume of uplink PDCP

TDD 1 .WBB PDUs of WBB UEs received in
the last TTI before the UE buffer
is empty


ID
FDD/ 152674874 L.Thrp.bits.UL.WBB Uplink traffic volume of WBB

TDD 0 UEs received at the PDCP layer in
a cell
TDD 152674878 L.ChMeas.PRB.DL.Frequen Average number of downlink

5 cyDomain.WBBUsed.Avg PRBs used in the frequency
domain for WBB UEs
TDD 152674878 L.ChMeas.PRB.DL.Frequen Average number of downlink

6 cyDomain.MBBUsed.Avg PRBs used in the frequency
domain for MBB UEs
Average proportion of downlink activated MBB UEs to downlink activated WBB UEs =
(L.Traffic.ActiveUser.DL.Avg – L.Traffic.ActiveUser.DL.WBB.Avg)/
L.Traffic.ActiveUser.DL.WBB.Avg
Average number of PRBs used by uplink PUSCH DRBs = Sum(L.ChMeas.PRB.UL.MCS.0
+ L.ChMeas.PRB.UL.MCS.1 + ... + L.ChMeas.PRB.UL.MCS.31)/Traffic measurement
period
Average number of used downlink PRBs = Sum(L.ChMeas.PRB.TM1 +
L.ChMeas.PRB.TM2 + ... + L.ChMeas.PRB.TM9)/Traffic measurement period

eRAN
WBB Feature Parameter Description 5 Specified Service Carrier
5.1 Principles
5.1.1 Overview
To meet operators' requirement that WBB and MBB services be provided using different
carriers, eNodeB cells are classified into three types, as shown in Figure 5-1.
Figure 5-1 UE camping policy
A cell can be any of the following types, which are specified by the Cell.SpecifiedCellFlag
parameter:
l MBB-service-prioritized cell: This type of cells preferentially serves MBB UEs. Other
types of UEs are transferred to other cells. The parameter value MBBSERCELL
denotes this cell type.
l WBB-service-specified cells: This type of cells preferentially serves WBB UEs. Other
types of UEs are transferred to other cells. The parameter value SPECSERCELL
denotes this cell type.

eRAN
l Common cell: Both WBB and MBB UEs can be transferred to common cells. The
parameter value NONE denotes this cell type.
l Emergency-call MBB UEs can be served by any of the three types of cells.
l As described in 5.1.3 Enabling Proactive Handovers of Non-Emergency-Call MBB UEs from
WBB-Service-Specified Cells and 5.1.5 Enabling Proactive Handovers of WBB UEs from
MBB-Service-Prioritized Cells, if an MBB UE accessing a WBB-service-specified cell or a WBB
UE accessing an MBB-service-prioritized cell does not support inter-frequency handover, it cannot
be handed over out of the cell.
5.1.2 Prohibiting Handovers of Non-Emergency-Call MBB UEs to

WBB-Service-Specified Cells
WBB-service-specified cells prohibit incoming handovers of non-emergency-call MBB UEs,
as shown in Figure 5-2.
Figure 5-2 Prohibiting handovers of non-emergency-call MBB UEs to WBB-service-

specified cells
The eNodeB performs the following operations to prohibit non-emergency-call MBB UEs
from being handed over to WBB-service-specified cells:
l Filters out neighboring frequencies that are used only for WBB-service-specified cells,
when the eNodeB is about to instruct a non-emergency-call MBB UE to perform inter-
frequency measurement for a handover.
l Filters out WBB-service-specified cells from the candidate target cell list, after the
eNodeB receives an intra- or inter-frequency measurement report from a non-
emergency-call MBB UE.
l Filters out WBB-service-specified cells from the candidate inter-frequency neighboring
cell list, when the eNodeB is selecting a target cell for blind handover of a non-
emergency-call MBB UE based on the blind handover priorities of neighboring cells.
l Filters out neighboring frequencies that are used only for WBB-service-specified cells,
when the eNodeB is selecting a target frequency for blind redirection of a non-
emergency-call MBB UE based on the frequency priorities. The frequency priorities
used as the selection basis can be RRC_CONNECTED UEs' frequency priorities
specified for mobility management or the intra-RAT frequency priorities specified for
SPIDs. If no neighboring cell has been configured for a frequency, this frequency is
retained for blind redirection.

eRAN
l The carrier attribute (cell type) is configured for each external cell. If no external cell is configured
for a frequency, the eNodeB cannot determine the carrier attribute of the frequency and regards it as
a common-cell frequency. Therefore, this frequency is not filtered out during inter-frequency or
blind handovers.
l The carrier attribute is specific to a cell. A target frequency specified by a blind redirection
instruction may be used for WBB-service-specified, MBB-service-prioritized, and common cells. It
is the UE instead of the eNodeB that selects the target cell of a blind redirection triggered for a non-
emergency-call MBB UE. As a result, a non-emergency-call MBB UE may access a WBB-service-
specified cell.
For external cells, this function is controlled by the EutranExternalCell.SpecifiedCellFlag

parameter. If this parameter is set to SPECSERCELL for an external cell (cell 2 in Figure
5-2), this cell is a WBB-service-specified cell. Non-emergency-call MBB UEs in common or
MBB-service-prioritized cells (cell 1 in Figure 5-2) will be prohibited from accessing the
WBB-service-specified cell (cell 2).
For co-site cells, this function is controlled by the Cell.SpecifiedCellFlag parameter. If this
parameter is set to SPECSERCELL for a cell (cell 2 in Figure 5-2), this cell is a WBB-
service-specified cell. Non-emergency-call MBB UEs in common or MBB-service-prioritized
cells (cell 1 in Figure 5-2) will be prohibited from accessing the WBB-service-specified cell
(cell 2).
This function may reduce the number of handovers.
For handover processes, see Mobility Management in Connected Mode.
5.1.3 Enabling Proactive Handovers of Non-Emergency-Call MBB

UEs from WBB-Service-Specified Cells
Only WBB UEs and emergency-call MBB UEs can camp on WBB-service-specified cells. If
a non-emergency-call MBB UE has accessed such a cell by a new access, incoming handover,
or RRC connection reestablishment, a carrier-attribute-based inter-frequency handover or
redirection is triggered to transfer the MBB UE out of the cell, as shown in Figure 5-3.
Figure 5-3 Enabling proactive handovers of non-emergency-call MBB UEs from WBB-
service-specified cells
This function is controlled by the Cell.SpecifiedCellFlag parameter. When it is set to

SPECSERCELL, carrier-attribute-based inter-frequency handovers are triggered for non-
emergency-call MBB UEs in WBB-service-specified cells.

eRAN
Modification of the Cell.SpecifiedCellFlag parameter will trigger automatic reset of the cell.
Event A4 is always used for measurement performed to trigger handovers of non-emergency-

call MBB UEs. Neighboring frequencies that are used only for WBB-service-specified cells
are filtered out from the neighboring frequencies to be measured.
The following event A4 thresholds for service-request-based inter-frequency handovers are

used as the thresholds for carrier-attribute-based inter-frequency handovers:
l RSRP threshold used to trigger event A4 reporting for service request-based inter-
frequency handovers (InterFreqHoGroup.SrvReqHoA4ThdRsrp)
l RSRQ threshold used to trigger event A4 reporting for service request-based inter-
frequency handovers (InterFreqHoGroup.SrvReqHoA4ThdRsrq)
Default values of the preceding parameters tend to cause handover failures. Therefore, if this
feature is required, increase the event A4 thresholds for service-based inter-frequency
handovers. In addition, the preceding parameters are configured for each QCI. The
IntraRatHoComm.InterFreqHoA4TrigQuan specifies whether the RSRP, RSRQ, or both
are used to trigger event A4 reporting, and IntraRatHoComm.InterFreqHoA4RprtQuan
specifies whether the RSRP or RSRQ is used for event reporting or both values are reported
for event A4.
l If a UE supports CA, event A4 is replaced by event A5 when the eNodeB sends measurement
configurations to the UE. In this case, the InterFreqHoGroup.InterFreqHoA5Thd1Rsrp and
InterFreqHoGroup.InterFreqHoA5Thd1Rsrq parameters are always set to the largest values.
l For details about the procedures for delivering and processing measurement configurations related to
event A4 or A5, see Mobility Management in Connected Mode.
After receiving an event A4 or A5 measurement report, the eNodeB generates a target cell
list, determines a target cell, and then initiates a handover to the target cell.
After triggering measurement for a carrier-attribute-based inter-frequency handover, the

eNodeB starts a timer used to wait for an inter-frequency A4-event measurement report for a
service-based handover. The timer duration is specified by the
ServiceIfHoCfgGroup.A4RptWaitingTimer parameter and is 3s by default. If a non-
emergency-call MBB UE fails to be handed over before the timer expires, the eNodeB
triggers a blind redirection process. In this case, an inter-frequency blind redirection is
triggered preferentially. If it fails, an inter-RAT blind redirection is triggered.
l Inter-frequency blind redirection is implemented if all of the following conditions are

met:
– Other types of cells have been configured as neighboring cells of a WBB-service-
specified cell.
– The EutranInterFreqNCell.BlindHoPriority parameter is set to a value in the
range of 1–16 for the other types of neighboring inter-frequency cells of a WBB-
service-specified cell. Alternatively, the EutranInterNFreq.ConnFreqPriority
parameter is set to a value in the range of 1–16 for neighboring frequencies of a
WBB-service-specified cell.
– The UE supports the specified target frequency.
l Inter-RAT blind redirection is implemented if all of the following conditions are met:

eRAN
– Blind inter-frequency redirection cannot be implemented.

– The UtranRedirectSwitch, GeranRedirectSwitch, or both options of the
CellHoParaCfg.HoModeSwitch parameter are selected.
– The UtranNcell.BlindHoPriority or GeranNcell.BlindHoPriority parameter is set
to a value ranging from 1 to 32, or the UtranNFreq.ConnFreqPriority or
GeranNfreqGroup.ConnFreqPriority parameter is set to a value ranging from 1 to
8.
– The UE supports the specified target network and frequency.
When blind redirection is triggered, the target frequency is selected based on the
BlindHoPriority values set for candidate frequencies. If the target frequency cannot be
determined, it is selected again based on the ConnFreqPriority values set for candidate
frequencies. MBB UEs that cannot be blindly redirected will not be released.
This function increases the number of handovers and affects handover-related KPIs.
5.1.4 Prohibiting Handovers of WBB UEs to MBB-Service-

Prioritized Cells
MBB-service-prioritized cells prohibit incoming handovers of WBB UEs, as shown in Figure
5-4.
Figure 5-4 Prohibiting handovers of WBB UEs to MBB-service-prioritized cells
To prohibit WBB UEs from being handed over to MBB-service-prioritized cells, the eNodeB
performs the following operations:
l Filters out neighboring frequencies that are used only for MBB-service-prioritized cells,
when the eNodeB is about to instruct a WBB UE to perform inter-frequency
measurement for a handover.
l Filters out MBB-service-prioritized cells from the candidate target cell list, after the
eNodeB receives an intra- or inter-frequency measurement report from a WBB UE.
l Filters out MBB-service-prioritized cells from the candidate inter-frequency neighboring
cell list, when the eNodeB is selecting a target cell for blind handover of a WBB UE
based on the blind handover priorities of neighboring cells.
l Filters out neighboring frequencies that are used only for MBB-service-prioritized cells,
when the eNodeB is selecting a target frequency for blind redirection of a WBB UE
based on the frequency priorities. The frequency priorities used as the selection basis can
be RRC_CONNECTED UEs' frequency priorities specified for mobility management or

eRAN
the intra-RAT frequency priorities specified for SPIDs. If no neighboring cell has been
configured for a frequency, this frequency is retained for blind redirection.
l The carrier attribute (cell type) is configured for each external cell. If no external cell is configured
for a frequency, the eNodeB cannot determine the carrier attribute of the frequency and regards it as
a common-cell frequency. Therefore, this frequency is not filtered out during inter-frequency or
blind handovers.
l The carrier attribute is specific to a cell. A target frequency specified by a blind redirection
instruction may be used for WBB-service-specified, MBB-service-prioritized, and common cells. It
is the UE instead of the eNodeB that selects the target cell of a blind redirection triggered for a WBB
UE. As a result, a WBB UE may access an MBB-service-prioritized cell after blind redirection.
For external cells, this function is controlled by the EutranExternalCell.SpecifiedCellFlag

parameter. If this parameter is set to MBBSERCELL for an external cell (cell 2 in Figure
5-4), this cell is an MBB-service-prioritized cell. WBB UEs in common or WBB-service-
specified cells (cell 1 in 5.1.4 Prohibiting Handovers of WBB UEs to MBB-Service-
Prioritized Cells) will be prohibited from accessing the MBB-service-prioritized cell (cell 2).
For co-site cells, this function is controlled by the Cell.SpecifiedCellFlag parameter. If this
parameter is set to MBBSERCELL for a cell (cell 2 in 5.1.4 Prohibiting Handovers of
WBB UEs to MBB-Service-Prioritized Cells), this cell is an MBB-service-prioritized cell.
WBB UEs in common or WBB-service-specified cells (cell 1 in Figure 5-4) will be
prohibited from accessing the MBB-service-prioritized cell (cell 2).
This function may reduce the number of handovers.
For handover processes, see Mobility Management in Connected Mode.
5.1.5 Enabling Proactive Handovers of WBB UEs from MBB-

Service-Prioritized Cells
Only MBB UEs can camp on MBB-service-prioritized cells. If a WBB UE has accessed such
a cell by new access, incoming handover, or RRC connection reestablishment, a carrier-
attribute-based inter-frequency handover or redirection is triggered to transfer the WBB UE
out of the cell, as shown in Figure 5-5.
Figure 5-5 Enabling proactive handovers of WBB UEs from MBB-service-prioritized cells
This function is controlled by the Cell.SpecifiedCellFlag parameter. When it is set to

MBBSERCELL, carrier-attribute-based inter-frequency handovers are triggered for WBB
UEs in MBB-service-prioritized cells.

eRAN
NOTICE
Modification of the Cell.SpecifiedCellFlag parameter will trigger automatic reset of the cell.
Event A4 is always used for measurement performed to trigger handovers of WBB UEs. (If a
UE supports CA, event A4 is replaced by event A5 when the eNodeB sends measurement
configurations to the UE. The thresholds used for event A5 reporting are always set to the
largest values.) Neighboring frequencies that are used only for MBB-service-prioritized cells
are filtered out from the neighboring frequencies to be measured by WBB UEs.
The following event A4 thresholds for service-request-based inter-frequency handovers are
used as the thresholds for carrier-attribute-based inter-frequency handovers:
l RSRP threshold used to trigger event A4 reporting for service request-based inter-
frequency handovers (InterFreqHoGroup.SrvReqHoA4ThdRsrp)
l RSRQ threshold used to trigger event A4 reporting for service request-based inter-
frequency handovers (InterFreqHoGroup.SrvReqHoA4ThdRsrq)
Default values of the preceding parameters tend to cause handover failures. Therefore, if this
feature is required, increase the event A4 thresholds for service-based inter-frequency
handovers. In addition, the preceding parameters are configured for each QCI. The
IntraRatHoComm.InterFreqHoA4TrigQuan specifies whether the RSRP, RSRQ, or both
are used to trigger event A4 reporting, and IntraRatHoComm.InterFreqHoA4RprtQuan
specifies whether the RSRP or RSRQ used for event reporting or both values are reported for
event A4.
l If a UE supports CA, event A4 is replaced by event A5 when the eNodeB sends measurement
configurations to the UE. In this case, the InterFreqHoGroup.InterFreqHoA5Thd1Rsrp and
InterFreqHoGroup.InterFreqHoA5Thd1Rsrq parameters are always set to the largest values.
l For details about the procedures for delivering and processing measurement configurations related to
event A4 or A5, see Mobility Management in Connected Mode.
After receiving an event A4 or A5 measurement report, the eNodeB generates a target cell
list, determines a target cell, and then initiates a handover to the target cell.
After triggering measurement for a carrier-attribute-based inter-frequency handover, the
eNodeB starts a timer used to wait for an inter-frequency A4-event measurement report for a
service-based handover. The timer duration is specified by the
ServiceIfHoCfgGroup.A4RptWaitingTimer parameter and is 3s by default. If the WBB UE
fails to be handed over before the timer expires, the eNodeB triggers a blind redirection
process. In this case, an inter-frequency blind redirection is triggered preferentially. If it fails,
an inter-RAT blind redirection is triggered. Blind redirection can be implemented when the
following conditions are met:
l Inter-frequency blind redirection is implemented if all of the following conditions are
met:
– Other types of cells have been configured as neighboring cells of an MBB-service-
prioritized cell.
– The EutranInterFreqNCell.BlindHoPriority parameter is set to a value in the
range of 1–16 for the other types of neighboring inter-frequency cells of an MBB-
service-prioritized cell. Alternatively, the EutranInterNFreq.ConnFreqPriority
parameter is set to a value in the range of 1–16 for neighboring frequencies of an
MBB-service-prioritized cell.

eRAN
– The UE supports the specified target frequency.

l Inter-RAT blind redirection is implemented if all of the following conditions are met:
– Blind inter-frequency redirection cannot be implemented.
– The UtranRedirectSwitch, GeranRedirectSwitch, or both options of the
CellHoParaCfg.HoModeSwitch parameter are selected.
– The UtranNcell.BlindHoPriority or GeranNcell.BlindHoPriority parameter is set
to a value ranging from 1 to 32, or the UtranNFreq.ConnFreqPriority or
GeranNfreqGroup.ConnFreqPriority parameter is set to a value ranging from 1 to
8.
– The UE supports the specified target network and frequency.
When blind redirection is triggered, the target frequency is selected based on the
BlindHoPriority values set for candidate frequencies. If the target frequency cannot be
determined, it is selected again based on the ConnFreqPriority values set for candidate
frequencies. WBB UEs that cannot be blindly redirected will not be released.
This function increases the number of handovers and affects handover-related KPIs.
5.1.6 WBB and Non-Emergency-Call MBB UE Transfer for MLB

Common cells have no restriction or preferences for the type of the served UEs, but WBB-
service-specified cells and MBB-service-prioritized cells have preferences. The former ones
preferentially serve WBB and emergency-call MBB UEs, and the latter ones preferentially
serve MBB UEs. When UEs are transferred for MLB, the types of target cells are selected
based on these service preferences, as shown in Figure 5-6.
Figure 5-6 WBB and MBB UE transfer for MLB
MBB UEs mentioned in the following in this section refer to non-emergency-call MBB UEs.
Balancing WBB and MBB UE loads maximizes network resources and ensure that:
l WBB UEs have the same experience in common cells as in WBB-service-specified cells.
l MBB UEs have the same experience in common cells as in MBB-service-prioritized
cells.
If both WBB and MBB UEs are active in a cell that has neighboring WBB-service-specified
and MBB-service-prioritized cells, the target cell selection mechanism for MLB-oriented
inter-frequency handover or redirection is as follows:

eRAN
l MBB-service-prioritized cells cannot be selected as target cells for WBB UEs.

l WBB-service-specified cells cannot be selected for MBB UEs.
l For principles of and engineering guidelines for MLB, see Intra-RAT Mobility Load Balancing.
l WBB and MBB UEs cannot be transferred for MLB if multi-operator core network (MOCN) is
implemented for RAN sharing.
5.1.7 Automatic Non-Common Cell Addition by ANR

The eNodeB uses the SpecifiedCellFlag parameter set for each external cell to determine
whether a WBB or MBB UE can be transferred to the cell. If this parameter is incorrectly
configured for an external cell, WBB or MBB UEs may be transferred to cells of an
unexpected type.
If the U2020 supports eNodeB's query about attributes of new external cells and the
SPEC_CELL_FLAG_QUERY_SW option of the ANR.SpecServiceCellQuerySw
parameter is selected, non-common external cells can be automatically added with the
SpecifiedCellFlag parameter correctly configured by ANR. This ensures that WBB and MBB
UEs are transferred to the expected types of cells.
NOTICE
l If the eNodeB serving an external cell is not managed by the U2020, the U2020 cannot
query the cell configurations on this eNodeB and therefore, does not support automatic
addition of this external cell by ANR.
l Before selecting the SPEC_CELL_FLAG_QUERY_SW option of the
ANR.SpecServiceCellQuerySw parameter, ensure that the ADD_NCELL_CFG_SW
option of the GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter is deselected to
avoid transmission of incorrect carrier attribute information of neighboring cells through
the X2 interface.
If the U2020 does not support eNodeB's query about attributes of new external cells,
neighboring non-common cells automatically added by ANR are configured as common cells.
In this case, you need to check and manually correct their carrier attributes.
If the U2020 supports eNodeB's query about attributes of new external cells and the
SPEC_CELL_FLAG_QUERY_SW option of the ANR.SpecServiceCellQuerySw
parameter is deselected, all neighboring cells automatically added by ANR are treated as
common cells by default. In this case, MBB UEs are possibly handed over to WBB-service-
specified cells (treated as common cells). Upon detecting MBB UEs in these cells, the
eNodeB triggers carrier-attribute-based handovers to transfer MBB UEs to common cells. If
the target common cells are still WBB-service-specified cells, handovers are performed again.
This results in repeated handovers of MBB UEs.
5.2 Network Analysis

eRAN
5.2.1 Benefits
Configuration of MBB-service-prioritized and WBB-service-specified cells ensures sufficient
resources for WBB and MBB UEs. In addition, operators can separately manage mobile
services and broadband access services and achieve separate asset and cost settlement.
It is recommended that this function be enabled when two or more carriers are deployed and
WBB and MBB services are provided using different carriers. It is recommended that MBB-
service-prioritized cells cover contiguous areas, interspersed with WBB-service-specified
cells, and WBB UE numbers be allocated only in WBB coverage areas.
5.2.2 Impacts
Network Impacts
l System capacity
– Service-specified carriers are used to ensure separate operation of WBB and MBB
services, preventing potential MBB network congestion caused by WBB UE
increase.
– Due to use of service-specified carriers, UEs are transferred between cells. This
causes carrier aggregation (CA) resource decoupling from UEs and decreases the
number of CA UEs.
l Network performance
– Carriers are distinguished for WBB and MBB services. Therefore, WBB and MBB
UEs have no impact on each other in terms of traffic volume and user experience.
– WBB-service-specified cells preferentially serve WBB and emergency-call MBB
UEs, and non-emergency-call MBB UEs are handed over out of the cells. MBB-
service-prioritized cells preferentially serve MBB UEs, and WBB UEs are handover
over out of these cells. As a result, the number of handovers rises. If a UE's
handover fails, blind redirection is triggered. If the blind redirection still fails, the
UE is released. Then, the UE will attempt to access the network again. This will
increase signaling overhead of eNodeBs.
– Prohibition of non-emergency-call MBB UEs' handover into WBB-service-
specified cells and that of WBB UEs' handover into MBB-service-prioritized cells
may decrease the number of inter-cell handovers.
– If the function of querying attributes of new external cells on the U2020 is enabled
and missing neighboring cell configuration is detected at handover preparation, the
eNodeB initiates the procedure for querying the carrier attribute of neighboring
cells on the U2020. This procedure lasts for a long time (up to 3 minutes
sometimes) due to a long delay and may affect the handover. If no candidate target
cell is available for the handover, a service drop may occur. In addition, addition of
external cells may not be completed in time due to a long duration of U2020
responding. The UE has to attempt to obtain cell global identifications (CGIs) for
multiple times. This slightly increases the air interface resource consumption.
– If both the specified service carrier and CA features are used, WBB-service-
specified cells must not be used as secondary serving cells (SCells) for MBB UEs
and MBB-service-prioritized cells must not be used as SCells for WBB UEs. The
specified service carrier feature may affect UEs' CA service experience or related
KPIs.

eRAN
Function Impacts
Name Switch
FDD Carrier None Carrier The specified

TDD aggregation Aggregation service carrier
feature may affect
UEs' CA service
experience or related
KPIs.1
FDD Intra-RAT ANR IntraRatEvent ANR The impact depends

TDD AnrSwitch and Management on whether the
IntraRatFastA eNodeB supports the
nrSwitch query of attributes of
options of the new external cells
ENodeBAlgoS on the U2020.2
witch.AnrSwitc
h parameter
FDD LTE spectrum WbbCaMultiC LTE Spectrum After LTE spectrum

TDD coordination arrierCoordS Coordination coordination
enhancement w option of the enhancement is
CaMgtCfg.Cell enabled, WBB CA
CaAlgoSwitch UEs can be handed
parameter over to MBB cells.
After the handovers,
WBB and MBB
carriers can be
aggregated.
1. CA does not allow WBB-service-specified cells to be used as SCells for MBB UEs, or MBB-
service-prioritized cells to be used as SCells for WBB UEs.
2. Supported: ANR automatically configures the automatically added neighboring cells as common
cells. In this case, you need to manually check the carrier attributes of neighboring cells to avoid
inconsistency between the carrier attributes of neighboring cells automatically added by ANR and
the actual carrier attributes.
Not supported: no impact
5.3 Requirements
5.3.1 Licenses
The following are FDD license requirements.

eRAN
Feature Feature Name Model License Sales Unit

ID Control Item
LOFD-110 WBB User LT1SWBBSPM WBB User Per Cell

223 Steering 00 Steering
Management Management(pe
r Cell)(FDD)
The following are TDD license requirements.
Feature ID Feature Name Model License Sales Unit

Control Item
TDLOFD-1102 WBB User LT4SSFSVCA0 WBB User Per Cell

23 Steering 0 Steering
Management Management(pe
r Cell)(TDD)
5.3.2 Software
Prerequisite Functions
Name Switch
FDD WBB UE None 4 WBB UE None

TDD identification Identification
and and
differentiated Differentiated
QoS guarantee QoS
Guarantee
Mutually Exclusive Functions

None
5.3.3 Hardware
Base Station Models

No requirements
Boards
None

eRAN
RF Modules
None
5.3.4 Networking
Non-common cells (WBB-service-specified and MBB-service-prioritized cells) are deployed
only for separate operation of WBB and MBB services. Therefore, only the inter-frequency
co-coverage networking mode is suitable for deploying common and non-common cells, as
shown in Figure 5-7.
Figure 5-7 Common and non-common cells with the same radius
If a WBB-service-specified cell has a larger radius (Cell.CellRadius) than another cell of a

different type, as shown in Figure 5-8, MBB UEs in the WBB-service-specified cell but
outside the coverage area of the other cell cannot access or be handed over to the other cell.
This causes KPI deterioration after deployment of non-common cells.
Figure 5-8 WBB-service-specified cell with a larger radius than another cell of a different
type
To retain KPIs, such as access and handover success rates after deployment of non-common
cells, you are advised to configure the same radius for co-coverage WBB-service-specified
and other types of cells.
If a WBB-service-specified cell has a smaller radius than another cell of a different type, MBB UEs can
normally access or be handed over to the other cell (MBB-service-prioritized or common).
In scenarios of separate WBB and MBB service provision, operators expect non-common
cells to serve only the specific UE types. Configuration of secondary component carriers
(SCCs) must adhere to this rule. Figure 5-9 illustrates the CA rules of different types of cells.
If CA is enabled when no common cells are deployed, at least two WBB or MBB carriers
must be used for CA.

eRAN
Figure 5-9 Rules of non-common cell combination for CA
If the adaptive CA function is enabled and the SccBlindCfgSwitch(SccBlindCfgSwitch)

option of the ENodeBAlgoSwitch.CaAlgoSwitch parameter is selected, set the
CaGroupSCellCfg.SCellBlindCfgFlag parameter to FALSE to prevent MBB-service-
prioritized cells selected as candidate secondary serving cells (SCells) from being configured
as SCells for WBB-service-specified cells working as primary serving cells (PCells) when
blind SCell configuration is performed. Similarly, use the same parameter setting to prevent
WBB-service-specified cells selected as candidate SCells from being configured as SCells for
MBB-service-prioritized cells working as PCells when blind SCell configuration is
performed.
5.3.5 Others
Before deployment, confirm the WBB UE development plan and neighbor relationships
between existing cells and newly added WBB-service-specified and MBB-service-prioritized
cells. The neighbor relationship information is used to set the carrier attribute in the
EutranExternalCell MO for neighboring cells.
5.4 Operation and Maintenance
5.4.1 Data Configuration

eRAN
5.4.1.1 Data Preparation
NOTICE
l If the specified service carrier feature is enabled, carrier attributes of external cells must be
configured or updated based on their attributes configured on their serving eNodeBs.
l Modification of the Cell.SpecifiedCellFlag parameter will trigger automatic reset of the
cell.
l Before setting the SpecifiedCellFlag parameter to SPECSERCELL for an external cell,
ensure that the license for this feature has been activated. Otherwise, handovers of
common UEs are affected, and common UEs cannot use the carrier corresponding to the
newly configured MBB-service-prioritized or WBB-service-specified cell as the SCC
when performing CA services.
l Before selecting the SPEC_CELL_FLAG_QUERY_SW option of the
ANR.SpecServiceCellQuerySw parameter, ensure that the ADD_NCELL_CFG_SW
option of the GlobalProcSwitch.X2BasedUptNcellCfgSwitch parameter is deselected to
avoid transmission of incorrect carrier attribute information of neighboring cells through
the X2 interface.
l The event A4 threshold for service-request-based inter-frequency handovers is used as the
threshold for carrier-attribute-based inter-frequency handovers. If the default event A4
threshold is used for service-request-based inter-frequency handovers, handovers are likely
to fail. Therefore, if this feature is required, increase the event A4 thresholds for service-
based inter-frequency handovers. The IntraRatHoComm.InterFreqHoA4TrigQuan
parameter determines which threshold in the InterFreqHoGroup MO is used.
Table 5-1 Parameters used for activation

Specified Cell Flag Cell.SpecifiedCellFl l Set this parameter to SPECSERCELL

ag for WBB-service-specified cells.
l Set this parameter to MBBSERCELL
for MBB-service-prioritized cells.
Specified Cell Flag EutranExternalCel l Set this parameter to SPECSERCELL

l.SpecifiedCellFlag if external E-UTRAN cells include
WBB-service-specified cells.
l Set this parameter to MBBSERCELL if
external E-UTRAN cells include MBB-
service-prioritized cells.
Mobile country code EutranExternalCel None

l.Mcc
Mobile network EutranExternalCel None

code l.Mnc
Specified Service ANR.SpecServiceC Select the

Cell Query Switch ellQuerySw SPEC_CELL_FLAG_QUERY_SW
option of this parameter.

eRAN
Service-Request InterFreqHoGroup It is recommended that this parameter be set

based handover A4 .SrvReqHoA4ThdRs to a value greater than the
RSRP threshold rp CellHoParaCfg.BlindHoA1A2ThdRsrp
value.
Service-Request InterFreqHoGroup It is recommended that this parameter be set

based handover A4 .SrvReqHoA4ThdRs to a value greater than the
RSRQ threshold rq CellHoParaCfg.BlindHoA1A2ThdRsrq
value.
Service-based ServiceIfHoCfgGro None

InterFreq A4 Report up.A4RptWaitingTi
Waiting Timer mer
Blind handover EutranInterFreqN- None

Priority Cell.BlindHoPriorit
y
Frequency Priority EutranInterNFreq. None

for Connected Mode ConnFreqPriority
5.4.1.2 Using MML Commands
Before enabling this feature, you need to configure prerequisite and mutually exclusive functions
according to 5.3.2 Software. For details, see the "Operation and Maintenance" section of the
corresponding feature.
Activation Command Examples (1)
Figure 5-10 WBB-service-specified cell configuration (1)

eRAN
//Setting the local cells of eNodeB 0 to WBB-service-specified cells

MOD CELL:LocalCellId=0,SpecifiedCellFlag=SPECSERCELL;
//Setting the SrvReqHoA4ThdRsrp and SrvReqHoA4ThdRsrq parameters to values
greater than the default values on eNodeB 0
MOD
INTERFREQHOGROUP:LOCALCELLID=0,INTERFREQHOGROUPID=0,SRVREQHOA4THDRSRP=-120,SRVREQH
OA4THDRSRQ=-26;
MOD
OA4THDRSRQ=-26;
MOD
OA4THDRSRQ=-26;
//Setting the BlindHoPriority or ConnFreqPriority parameter on eNodeB 0
(BlindHoPriority is taken as an example here. To set the ConnFreqPriority
parameter, run the MOD EUTRANINTERNFREQ command.)
MOD
EUTRANINTERFREQNCELL:LOCALCELLID=0,MCC="460",MNC="00",ENODEBID=11117,CELLID=4,BLIN
DHOPRIORITY=7;
MOD
DHOPRIORITY=7;
MOD
DHOPRIORITY=7;
//Setting the external cells of eNodeB 1 to WBB-service-specified cells (cells 0
to 2 must have been configured as external cells for eNodeB 1)
MOD
EUTRANEXTERNALCELL:Mcc="460",Mnc="20",eNodeBId=0,CellId=0,SpecifiedCellFlag=SPECSE
RCELL;
MOD
RCELL;
MOD
RCELL;
//(Optional) Disabling X2-based automatic addition of neighboring cell
configurations and enabling automatic addition of neighboring non-common cells by
ANR
MOD GLOBALPROCSWITCH: X2BasedUptNcellCfgSwitch=ADD_NCELL_CFG_SW-0;
MOD ANR: SpecServiceCellQuerySw=SPEC_CELL_FLAG_QUERY_SW-1;

eRAN
Figure 5-11 WBB-service-specified cell configuration (2)

MOD
OA4THDRSRQ=-26;
MOD
OA4THDRSRQ=-26;
MOD
DHOPRIORITY=7;
MOD EUTRANINTERNFREQ:LOCALCELLID=0,DLEARFCN=40540,CONNFREQPRIORITY=7;
//Setting the external cell of eNodeB 1 to a WBB-service-specified cell (cell 0
must have been configured as an external cell for eNodeB 1)
MOD
RCELL;
ANR

eRAN
Figure 5-12 WBB-service-specified and MBB-service-prioritized cell configuration

MOD
OA4THDRSRQ=-26;
MOD
OA4THDRSRQ=-26;
MOD
DHOPRIORITY=7;
//Setting the external cells of eNodeB 0 to MBB-service-prioritized cells (cells
1 to 3 must have been configured as external cells for eNodeB 0)
MOD
EUTRANEXTERNALCELL:Mcc="460",Mnc="20",eNodeBId=1,CellId=1,SpecifiedCellFlag=MBBSER
CELL;
MOD
CELL;
MOD
CELL;
//Setting the external cell of eNodeB 1 to a WBB-service-specified cell (cell 0
must have been configured as an external cell for eNodeB 1)
MOD
RCELL;
//Setting the local cells of eNodeB 1 to MBB-service-prioritized cells
MOD CELL:LocalCellId=1,SpecifiedCellFlag=MBBSERCELL;
ANR

eRAN

Deactivation Command Examples

//Setting a local cell to a common cell
MOD CELL:LocalCellId=0,SpecifiedCellFlag=NONE;
//Setting an external cell to a common cell
MOD
EUTRANEXTERNALCELL:Mcc="460",Mnc="20",eNodeBId=255,CellId=1,SpecifiedCellFlag=NONE
;
//(Optional) Disabling automatic addition of non-common external cells by ANR
5.4.1.3 Using the CME (FDD)

For detailed operations, see CME-based Feature Configuration.
5.4.1.4 Using the CME (TDD)

l Fast batch activation
This function can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME
product documentation or online help: CME Management > CME Guidelines >
Enhanced Feature Management > Feature Operation and Maintenance.
l Single/Batch configuration
This function can be activated for a single base station or a batch of base stations on the
CME. For detailed operations, see CME-based Feature Configuration.
5.4.2 Activation Verification

The observation procedure is as follows:
Step 1 Enable an MBB UE to access a WBB-service-specified cell or a WBB UE to access an MBB-

service-prioritized cell.
Step 2 On the U2020, choose Monitor > Signaling Trace > Signaling Trace Management > Uu
Interface Trace to create a Uu interface tracing task. Check messages traced over the Uu
interface. If the MesaConfig IE (inter-frequency measurement configurations) is included in
the RRC_CONN_RECFG message sent by the eNodeB, the specified service carrier has been
activated.
Step 3 Check the RRC_CONN_RECFG message, which is the handover command sent from the
eNodeB after it receives an A4-event-based inter-frequency measurement report from the UE
for a carrier-attribute-based handover. If the target cell indicated by the message is a common
cell, a carrier-attribute-based inter-frequency handover has been triggered.
----End
5.4.3 Network Monitoring

Counter ID Counter Name Description
1526745955 L.Traffic.User.WBB.Avg Average number of WBB

UEs in a cell

eRAN
Counter ID Counter Name Description
1526740470 L.HHO.InterFreq.CarrierType.PrepA Number of carrier attribute-

ttOut based inter-frequency
handover preparation
attempts
1526740471 L.HHO.InterFddTdd.CarrierType.Pre Number of carrier attribute-

pAttOut based inter-duplex-mode
handover preparation
attempts
1526740472 L.HHO.InterFreq.CarrierType.ExecA Number of carrier attribute-

ttOut based inter-frequency
handover execution attempts
1526740473 L.HHO.InterFddTdd.CarrierType.Ex Number of carrier attribute-

ecAttOut based inter-duplex-mode
handover execution attempts
1526740474 L.HHO.InterFreq.CarrierType.ExecS Number of successful carrier

uccOut attribute-based inter-
frequency handover
executions
1526740475 L.HHO.InterFddTdd.CarrierType.Ex Number of successful carrier

ecSuccOut attribute-based inter-duplex-
mode handover executions
1526740476 L.RRCRedirection.InterFreq.Carrier Number of carrier attribute-

Type based intra-RAT inter-
frequency redirections
1526740477 L.RRCRedirection.InterFddTdd.Carr Number of carrier attribute-

ierType based intra-RAT inter-
duplex-mode redirections
1526740478 L.Traffic.SpecSerUser.Avg Average number of UEs

running specified services

eRAN
WBB Feature Parameter Description 6 Parameters
6 Parameters
The following hyperlinked EXCEL files of parameter documents match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.

l eNodeBFunction Parameter Reference: contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
l eNodeBFunction Used Reserved Parameter List: contains the reserved parameters that
are in use and those that have been disused.
You can find the EXCEL files of parameter reference and used reserved parameter list for the software
version used on the live network from the product documentation delivered with that version.
FAQ 1: How do I find the parameters related to a certain feature from parameter
reference?
Step 1 Open the EXCEL file of parameter reference.
Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and choose
Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
FAQ 2: How do I find the information about a certain reserved parameter from the used
reserved parameter list?
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT columns
to locate the reserved parameter, which may be only a bit of a parameter. View its
information, including the meaning, values, impacts, and product version in which it is
activated for use.
----End

eRAN
WBB Feature Parameter Description 7 Counters
7 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l eNodeBFunction Performance Counter Summary: contains all counters related to radio
access functions, including air interface management, access control, mobility control,
and radio resource management.
You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 1 Open the EXCEL file of performance counter reference.
Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
Step 3 Click OK. All counters related to the feature are displayed.
----End

eRAN
WBB Feature Parameter Description 8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
WBB Feature Parameter Description 9 Reference Documents
9 Reference Documents
1. ANR Management
2. DRX and Signaling Control
3. QoS Management
4. RAN Sharing
5. Scheduling
6. Flexible User Steering
7. Video Experience Optimization
8. Mobility Management in Connected Mode
9. Intra-RAT Mobility Load Balancing
10. Channel State Management
11. Carrier Aggregation
12. Rate Control Based on User Types
13. Massive MIMO (TDD)
14. LTE Spectrum Coordination

WBB (eRAN15.1 01) PDF

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

WBB (eRAN15.1 01) PDF

Uploaded by

Copyright:

Available Formats

eRAN

WBB Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document.................................................................................................................. 4

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. ii

4.4.1.3 Using the CME....................................................................................................................................................... 28

5 Specified Service Carrier............................................................................................................33

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iii

1.1 eRAN15.1 01 (2019-06-06)

1.2 eRAN15.1 Draft A (2019-01-05)

Replaced the Deleted parameters: FDD l 3900 and 5900

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 1

Change Parameter Change RAT Base Station

Added dynamic Added the FDD l 3900 and 5900

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 2

Change Parameter Change RAT Base Station

Added SPID-based Added the TDD l 3900 and 5900

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 3

2 About This Document

2.1 General Statements

l The technical principles of features and their related parameters

Feature Differences Between RATs

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 4

2.2 Applicable RAT

2.3 Features in This Document

Feature ID Feature Name Section

LOFD-110223 WBB User Steering 4 WBB UE Identification and

This document describes the following TDD feature.

Feature ID Feature Name Section

TDLOFD-110223 WBB User Steering 4 WBB UE Identification and

2.4 Feature Differences Between FDD and TDD

LOFD-110223 TDLOFD-11022 Enhanced uplink power 4 WBB UE

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 5

Figure 3-1 Networking for the WBB solution

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 6

4 WBB UE Identification and Differentiated

4.1.1 WBB UE Identification

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 7

Table 4-1 Selecting the WBB UE identification method

Identification SPID_BASED Use this method if either of the following conditions

l For the definition of GBR and non-GBR bearers, see Scheduling.

SPID-based WBB UE identification

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 8

Figure 4-1 Process of transmitting an SPID across the entire network

QCI-based WBB UE identification

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 9

4.1.2 WBB UE Scheduling Priority

l is the original scheduling priority of

l is the weighting coefficient of uplink/downlink scheduling priorities

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 10

MBB Upper CellWttxParaCfg.MbbUserDlPrbUpLimit Both tight and

WBB Upper CellWttxParaCfg.WbbUserDlPrbUpLimit Both tight and

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 11

UE Type Item Parameter Control

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 12

4.1.4 Dynamic Control over the Maximum Downlink PRB Usage

Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. 13

The following table describes the involved thresholds.

1 Dynamic Control MBB UE PRB CellWttxParaCfg.DynCtrlMbbUePrb

2 Dynamic Control UE Count High Pct CellWttxParaCfg.DynCtrlUeCntHigh