Академический Документы
Профессиональный Документы
Культура Документы
Issue 02
Date 2015-04-30
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.
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.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
1 About This Document
1.1 Scope
1.2 Intended Audience
3 DRX
3.1 Introduction
3.1.2 Benefits
3.1.3 Process
4 Dynamic DRX
4.1 Introduction
4.1.2 Benefits
4.1.3 Process
4.3 Principles
5.1 Introduction
5.1.2 Benefits
5.2 Principles
6 Related Features
7 Network Impact
8.3 Planning
8.4 Deployment
8.4.1 Requirements
8.4.3 Precautions
8.4.5 Activation
8.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
8.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
8.4.7 Reconfiguration
8.4.8 Deactivation
8.5 Maintenance
8.5.3 Troubleshooting
9.3 Planning
9.4 Deployment
9.4.1 Requirements
9.4.3 Precautions
9.4.5 Activation
9.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
9.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
9.4.7 Reconfiguration
9.4.8 Deactivation
9.5 Maintenance
9.5.3 Troubleshooting
10.3 Planning
10.4 Deployment
10.4.1 Requirements
10.4.2 Data Preparation
10.4.3 Precautions
10.4.5 Activation
10.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
10.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
10.4.7 Reconfiguration
10.4.8 Deactivation
10.5 Maintenance
10.5.3 Troubleshooting
11 Parameters
12 Counters
13 Glossary
14 Reference Documents
LBFD-002017 DRX
LOFD-00110501 Dynamic DRX
LOFD-00110502 High-Mobility-Triggered Idle Mode
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
Feature change
Editorial change
eRAN8.1 02 (2015-04-30)
eRAN8.1 01 (2015-03-23)
The function described in this document is implemented in the same way on macro, micro,
and LampSite eNodeBs.
When UEs in connected mode are moving at high speeds, frequent handovers occur. When
there are a large number of such UEs, excessive signaling strains the network. To reduce the
signaling, Huawei eNodeBs use the LOFD-00110502 High-Mobility-Triggered Idle Mode
feature.
Table 2-1 describes the application scenarios and benefits of DRX and signaling control
features.
Table 2-1 Application scenarios and benefits of DRX and signaling control features
Feature Recommended Application Scenario Benefit
Name UE Type
LBFD- Smart and non- Services with periodic Reduces UE power
002017 DRX smart terminals transmission of consumption.
continuous small
packets, such as voice
over IP (VoIP) services
Delay-insensitive
services, such as web
browsing and emails
Feature Recommended Application Scenario Benefit
Name UE Type
Services that use small,
sparse packets, such as
Presence services
Automatic neighbor
relation (ANR)
measurement
Presence services, such as MSN presence notices, allow end users to obtain real-time
presence information based on a certain communication methods and access policies.
Presence information includes user status, communication capabilities, and personal
preferences.
3 DRX
This chapter describes the principles of LBFD-002017 DRX. For engineering guidelines, see
8 Engineering Guidelines for LBFD-002017 DRX.
3.1 Introduction
3.1.1 Definition and Application Scenarios
Definition
DRX is a technology in which a UE can switch between active and sleep states. When the UE
needs to receive downlink (DL) data or signaling, the UE turns on its receiver and enters the
active state. In other situations, the UE turns off its receiver and enters the sleep state to
reduce power consumption.
DRX for UEs in connected mode is provided by LBFD-002017 DRX. DRX for UEs in idle
mode, as described in Idle Mode Management Feature Parameter Description, is different.
Unless otherwise stated, "DRX" in this document refers to DRX for UEs in connected mode.
In DRX mode, a DRX cycle consists of active time and sleep time, which correspond
respectively to the active state and sleep state. In non-DRX mode, the UE keeps its receiver
on and stays in the active state. For explanations of the DRX cycle, active time, and sleep
time, see 3.4.1 Related Concepts.
Application Scenarios
DRX can be used with all mobile terminals. It is suitable for the following types of services:
3.1.2 Benefits
Reduces power consumption and prolongs the standby time of the UE. The UE does
not need to constantly monitor the physical downlink control channel (PDCCH). The
UE can turn off its radio frequency (RF) receiver and other communication modules.
Allows the UE to perform ANR measurement during the sleep time in DRX.
NOTE:
When a UE is in DRX mode, the standby time depends on the UE model, traffic
model, and DRX parameter settings. UEs from certain vendors do not need to
constantly monitor the PDCCH, however, they cannot turn off their RF modules and
the power saving effect is limited.
Performance preference or power saving preference can be configured by DRX
parameters. For details, see 8.4.5.4 Using MML Commands.
3.1.3 Process
After the UE accesses the network, the eNodeB checks whether the UE meets the
conditions for entering DRX mode. When the conditions are met, the eNodeB sends
the UE an RRC Connection Reconfiguration message with the DRX-Configuration
information element (IE) set to setup. The UE then enters DRX mode based on other
parameters in this IE. For the conditions for entering DRX mode, see 3.3.1 Entry
Conditions.
After the UE enters DRX mode, the eNodeB instructs the UE to switch between
active and sleep states as well as between long and short DRX cycles based on
network conditions and parameter settings. For details, see 3.4.3.2 Switching Between
Active Time and Sleep Time and 3.4.4 Switching Between Long and Short DRX
Cycles.
For the function and usage of this switch, see 3.3 Entry and Exit Conditions.
For the functions and usages of these timers, see 3.4 Working Mechanism.
NOTE:
For example, as VoIP services have a QCI of 1, the DRX parameters for QCI 1 can be used
for VoIP services. For details about DRX principles for VoIP services, see 3.5.1 DRX
Parameters for VoIP.
If services with different QCIs are running on the UE, the following DRX parameter
selection rules are recommended:
If any QCI is not configured with a DRX parameter group, the eNodeB will not
configure DRX parameters for this UE.
If each QCI is configured with a DRX parameter group, then:
o If each DRX parameter group has a different DrxParaGroup.LongDrxCycle
parameter value, the eNodeB will select the DRX parameter group with the
smallest DrxParaGroup.LongDrxCycle parameter value for this UE.
o If multiple DRX parameter groups have the smallest
DrxParaGroup.LongDrxCycle parameter value, the eNodeB will select the
DRX parameter group for the QCI with the highest priority defined by 3GPP.
When the UE simultaneously has bearers of QCI 1 and QCI 5 as well as a default bearer (for
example, of QCI 6, 7, 8, or 9), the eNodeB complies with the following configuration rules:
The DRX functionality is jointly controlled by the general DRX switch Drx.DrxAlgSwitch
and the QCI-specific DRX switch DrxParaGroup.EnterDrxSwitch.
After the UE receives an RRC Connection Reconfiguration message with the DRX-
Configuration IE set to setup, it enters DRX mode. The eNodeB instructs the UE to enter
DRX mode if all the following conditions are met:
There are exceptions. When one of the following conditions is met, the eNodeB no longer
instructs the UE to enter DRX mode:
The Drx.DrxAlgSwitch parameter is set to OFF(Off), and the eNodeB instructs the
UE to exit DRX mode in the RRC connection reconfiguration procedure.
The UE in connected mode experiences a radio link failure (RLF) when radio
conditions deteriorate.
During a handover, the eNodeB instructs the UE to exit DRX mode.
The UE enters the TTI bundling state.
On Duration
When the UE is in DRX mode, it cannot keep its receiver off all the time. It must periodically
turn on its receiver and monitor the PDCCH for incoming signaling for a consecutive period.
This consecutive period is called On Duration, and the related timer is named On Duration
Timer. The DrxParaGroup.OnDurationTimer parameter specifies the On Duration.
DRX Cycle
A DRX cycle is the interval between two occurrences of On Duration. A DRX cycle includes
an On Duration and a possible period of sleep time, as shown in Figure 3-2.
NOTE:
The period following an On Duration may be active or sleep time. For details, see 3.4.3.1
Operation in Active Time.
A DRX cycle consists of active time and sleep time. It may be a long or short cycle.
Active Time
In active time, the UE turns on its receiver and monitors the PDCCH. Active time is equal to
an On Duration plus other possible periods during which the UE needs to turn on its receiver,
for example, a period during which a DRX timer is working or a high-priority service is
being processed. DRX timers include the DRX Inactivity Timer, Contention Resolution
Timer, and DRX Retransmission Timer. For details, see 3.4.3.1 Operation in Active Time.
A longer active time results in a shorter service delay but increased UE power
consumption.
A shorter active time results in reduced UE power consumption but a longer service
delay.
Sleep Time
During a DRX cycle, the UE is not active during sleep time. During sleep time, the UE turns
off its receiver.
Using a long DRX cycle can save more power. The long cycle is specified by the mandatory
parameter DrxParaGroup.LongDrxCycle.
NOTE:
If a short DRX cycle is not configured before DRX is enabled, the UE will use the long cycle
after entering DRX mode. If a short cycle has been configured before DRX is enabled, the
UE will preferentially use the short cycle and switches to the long cycle after the timer
defined by DrxParaGroup.DrxShortCycleTimer expires.
The application of a short DRX cycle is jointly controlled by Drx.ShortDrxSwitch and the
QCI-level DRX switch DrxParaGroup.SupportShortDrx.
A short cycle results in better service experience than a long cycle but saves less power. You
can use the following parameters for configuring a short cycle:
If a short DRX cycle is configured for the UE, the UE will determine when to use the long or
short cycle as described in 3.4.4 Switching Between Long and Short DRX Cycles.
3.4.2 Startup of a DRX Cycle
After the UE enters DRX mode, the On Duration Timer may not start immediately. The timer
starts up and the UE starts a long or short DRX cycle only when the following conditions are
met:
The long DRX cycle starts at the time specified by the system frame number (SFN) or
system subframe number (SSFN).
The short DRX cycle starts at the time specified by the SFN or SSFN.
NOTE:
These formulas are defined in section 5.7 "Discontinuous Reception (DRX)" of 3GPP TS
36.321 V10.5.0.
In these formulas, DRX start offset is the start offset of the long DRX cycle, and (DRX start
offset) modulo DrxParaGroup.ShortDRXCycle is the start offset of the short DRX cycle.
The eNodeB notifies the UE of the long DRX cycle, short DRX cycle, and DRX start offset
in the RRC Connection Reconfiguration message.
Figure 3-3 shows how the UE enters DRX mode. The eNodeB assigns the same long DRX
cycle of 10 transmission time intervals (TTIs) to both UE 1 and UE 2 in radio frame 0 (whose
SFN is 0) in a cell and instructs them to enter DRX mode respectively at TTI 1 and TTI 0.
UE 1 and UE 2 enter the DRX cycle respectively at TTI 3 and TTI 4, based on the configured
DRX start offset. Therefore, for UE 1, (SFN, SSFN) = (0, 3); for UE 2, (SFN, SSFN) = (0, 4).
Figure 3-3 Entering DRX mode and starting the DRX cycle
A DRX cycle consists of active time and sleep time. This section describes the operation in
active time and the switching between active time and sleep time.
The UE turns on its receiver in active time. According to section 5.7 in 3GPP TS 36.321
V10.5.0, the UE is in active time if any of the following conditions is met:
The starting of a timer triggers the starting of active time. Table 3-2 describes DRX timers.
At the
beginning of
the subframe
when semi-
persistent
DL data
transmission
may take
place.
The UE
decodes a
PDCCH and
detects that a
HARQ
process will
have a DL
transmission
in a new
subframe.
In the On Duration, the DRX Inactivity Timer starts when the UE decodes a PDCCH and
detects that an initial data transmission is about to start. The UE continues to monitor the
PDCCH for new transmissions until the DRX Inactivity Time expires. The timer restarts if a
new transmission occurs. The DRX Inactivity Timer repeatedly restarts because of
continuous data transmission to prolong the active time.
When the DRX Inactivity Timer expires and a short DRX cycle has been configured, the UE
enters a short DRX cycle. For details, see Switching from a Long DRX Cycle to a Short DRX
Cycle.
Switching between active time and sleep time depends on DRX timers and service processes.
Figure 3-4 illustrates the switching between active time and sleep time in various frequency
division duplex (FDD) mode scenarios.
Figure 3-4 Switching between active time and sleep time
Table 3-3 describes the conditions for starting active time. For example, OD is the condition
for starting the On Duration Timer.
The active time shown in the UE DRX status plot in Figure 3-4 combines the active time
described in each of the other plots excluding the plot of HARQ RTT Timer.
In the plot of HARQ RTT Timer, "DL HARQ raises" refers to one of the two DL HARQ
transmission scenarios:
Although the eNodeB assigns both long and short DRX cycles to the UE, the UE uses a long
or short DRX cycle at a time. The UE can switch between long and short DRX cycles
according to certain rules.
If the eNodeB delivers short DRX cycle parameters to the UE, the UE will exit the long DRX
cycle and enter a short DRX cycle if either of the following occurs:
If there is data to transmit, the eNodeB starts the DRX Inactivity Timer. When the
DRX Inactivity Timer expires, the short DRX cycle starts.
After the UE receives the DRX command MCE, the UE enters a short DRX cycle.
Otherwise, the UE still uses the long DRX cycle.
If the UE does not receive new data during a specified period after entering a short DRX
cycle, it will switch to a long DRX cycle to save power.
The period before the UE switches to a long DRX cycle is called the lifetime of the short
DRX cycle. The lifetime is measured by the number of times the short DRX cycle repeats.
The DRX Short Cycle Timer determines how long the short DRX cycle runs. The
DrxParaGroup.DrxShortCycleTimer parameter sets the time for the DRX Short Cycle
Timer. After the DRX Short Cycle Timer expires, the UE uses the long DRX cycle.
For common services on common UEs, users can configure one set of DRX parameters. For
details, see 3.5.1 DRX Parameters for VoIP.
For special UEs or ANR measurements, users can configure special DRX parameters. For
details, see 3.5.2 DRX Parameters for Special UEs and 3.5.3 DRX Parameters for ANR
Measurements.
NOTE:
"N/A" in Table 3-4 means that no parameters are involved in the corresponding scenario.
For VoIP, a set of special DRX parameter settings is available to reduce UE power
consumption while maintaining VoIP capacity.
As VoIP services have a QCI of 1, the DRX parameters for QCI 1 can be used for VoIP
services. As bearers with QCI 5 are set up for IMS signaling transmission during VoIP
services, the DRX parameters for QCI 5 also need to be set.
When semi-persistent scheduling is enabled, configuring short DRX cycles for VoIP is not
recommended. When the UE has multiple bearers with different QCIs (for example, QCI 1,
QCI 5, and QCI 9), the DrxParaGroup.LongDrxCycle parameter for QCI 1 must be set to
the minimum value so that the eNodeB selects the DRX parameters for QCI 1 as the DRX
parameters for this UE.
If the parameter value is too small, the UE will probably stay in the active state and
consume more power.
If the parameter value is too large, the VoIP scheduling may be performed during
sleep time. This delays packet transmission and affects user experience.
If the long DRX cycle configured for VoIP is shorter than or equal to 20 ms, configuring a
short DRX cycle is not recommended. If a short DRX cycle is configured, less power will be
saved and no obvious decrease will be seen in service delay.
Based on the number of UEs with VoIP services, set an appropriate value for the On Duration
Timer, which is specified by the DrxParaGroup.OnDurationTimer parameter. If there are
a large number of UEs with VoIP services, set a large value for this parameter to ensure the
scheduling of VoIP services.
It is recommended that the DrxParaGroup.OnDurationTimer parameter for QCI 1 be set
to PSF10(10 PDCCH subframes).
Table 3-5 lists the recommended DRX parameter settings for VoIP when semi-persistent
scheduling is enabled.
Table 3-5 Recommended DRX parameter settings for VoIP when semi-persistent scheduling
is enabled
Parameter ID Recommended Value
DrxParaGroup.LongDrxCycle SF20
DrxParaGroup.onDurationTimer PSF10
DrxParaGroup.DrxInactivityTimer PSF80
DrxParaGroup.DrxReTxTimer SF8
DrxParaGroup.SupportShortDrx UU_DISABLE
Table 3-6 lists the recommended DRX parameter settings for VoIP when semi-persistent
scheduling is disabled.
Table 3-6 Recommended DRX parameter settings for VoIP when semi-persistent scheduling
is disabled
Parameter ID Recommended Value
DrxParaGroup.LongDrxCycle SF40
DrxParaGroup.onDurationTimer PSF10
DrxParaGroup.DrxInactivityTimer PSF80
DrxParaGroup.DrxReTxTimer SF8
DrxParaGroup.SupportShortDrx UU_DISABLE
Not all UEs are sensitive to power consumption. For example, data cards or UEs with a
sufficient power supply focus on service delay rather than power consumption. These UEs
are called special UEs. The subscriber profile ID for RAT/frequency priority (RFSP) function
allows operators to designate a UE as a special UE and use special DRX parameters for this
UE to improve service performance and increase energy efficiency.
On the Evolved Packet Core (EPC) side, the UE RFSP is an integer ranging from 1 to 256.
Operators can define the RFSP and bind it to the mobile station international ISDN number
(MSISDN) of the UE. When the UE accesses the EPC, the RFSP of the UE is included in the
INITIAL CONTEXT SETUP REQUEST message and sent to the eNodeB over the S1
interface.
On the eNodeB side, operators can set the SpidCfg.Spid parameter to an integer ranging
from 1 to 256 on the U2000 or Web LMT. When the RFSP value of the UE is the same as the
SpidCfg.Spid parameter value and the SpidCfg.DrxStatus parameter is set to FALSE, the
eNodeB considers the UE to be a special UE. Otherwise, the eNodeB considers the UE to be
a common UE.
On the UE side, the UE reports its type to the eNodeB using the UE-EUTRA-Capability IE in
a UECapabilityInformation message. If the UE-EUTRA-Capability IE contains
noBenFromBatConsumpOpt, the UE is a special UE. Otherwise, the UE is a common UE.
The UE type (common or special) is reported on both the eNodeB and UE sides. The eNodeB
compares the results reported on the two sides. When the results are inconsistent, the eNodeB
considers the UE to be a special UE. When the results are consistent, the eNodeB identifies
the UE type based on the results and uses the appropriate DRX feature.
The working mode of special UEs is the same as that of common UEs except that DRX
parameters configured for special UEs are different from those configured for common UEs.
The eNodeB configures the long DRX cycle and the UE performs ANR measurements in
sleep time regardless of whether the general DRX switch Drx.DrxAlgSwitch is set to ON
or OFF.
If the cells to be measured are E-UTRAN cells, the eNodeB will use the value of the
Drx.LongDrxCycleForAnr parameter as the long DRX cycle.
If the cells to be measured are GERAN or UTRAN cells, the eNodeB will use the
value of the Drx.LongDRXCycleforIRatAnr parameter as the long DRX cycle.
4 Dynamic DRX
This chapter describes the implementation principles of dynamic DRX. For engineering
guidelines, see 9 Engineering Guidelines for LOFD-00110501 Dynamic DRX.
4.1 Introduction
4.1.1 Definition and Application Scenarios
Definition
Application Scenarios
4.1.2 Benefits
Dynamic DRX provides the following benefits but cannot provide all these benefits
simultaneously:
The UE inactivity timer is increased to allow UEs to stay in connected mode longer in
the case of high signaling overhead caused by UEs' access to the network.
4.1.3 Process
After the UE accesses the network, the eNodeB determines whether the UE meets the
conditions for entering dynamic DRX mode. When the conditions are met, the
eNodeB sends the UE an RRC Connection Reconfiguration message with the DRX-
Configuration IE set to setup. The UE then enters dynamic DRX mode based on other
parameters in this IE. For details, see 4.2.1 Entry Conditions.
After the UE enters dynamic DRX mode, the eNodeB determines whether the UE
enters power saving or reduced signaling mode based on the
RrcConnStateTimer.UeInactivityTimerDynDrx parameter value. For details, see 4.3
Principles.
The eNodeB determines whether the UE meets the conditions for exiting dynamic
DRX mode. When the conditions are met, the eNodeB sends the UE an RRC
Connection Reconfiguration message with the DRX-Configuration IE set to release.
When the UE receives the message, it immediately clears all the DRX parameters
stored locally and exits dynamic DRX mode. For details, see 4.2.2 Exit Conditions.
Before dynamic DRX is enabled, the following DRX parameters must be configured:
NOTE:
4.3 Principles
To allow smart terminals to stay in sleep state longer and consume less power, the eNodeB
selects different DRX parameters for UEs in synchronization and out-of-synchronization
states based on the RrcConnStateTimer.UeInactivityTimerDynDrx and
RrcConnStateTimer.UlSynTimerDynDrx parameter settings. Figure 4-2 shows how a UE
switches between different states.
Figure 4-2 UE state switching
When the UE is in the synchronization state, the eNodeB sends DRX parameters for
the synchronization state to the UE. If the UE does not receive or transmit data during
the period specified by the RrcConnStateTimer.UlSynTimerDynDrx parameter,
the UE will enter the out-of-synchronization state.
After the protection period elapses, the eNodeB no longer maintains synchronization
for the UE, that is, the eNodeB no longer sends the TA command to the UE. The UE
enters the out-of-synchronization state only after the timer specified by the
TimeAlignmentTimer.TimeAlignmentTimer parameter expires, as shown in
Figure 4-3.
When the UE is in the out-of-synchronization state, the eNodeB sends DRX
parameters for the out-of-synchronization state to the UE.
o If the UE does not receive or transmit data during the period specified by the
RrcConnStateTimer.UeInactivityTimerDynDrx parameter, the UE will
enter idle mode.
o If a new service arrives within the period specified by the
RrcConnStateTimer.UeInactivityTimerDynDrx parameter, the UE will
enter the synchronization state and the eNodeB sends DRX parameters for the
synchronization state to the UE again.
When the UE is in idle mode and it has new data to receive or transmit, the UE enters
the synchronization state and the eNodeB sends DRX parameters for the
synchronization state to the UE again.
NOTE:
2. When the UE is in the synchronization state, the eNodeB assigns the UE the DRX
parameters for the synchronization state. When the timer defined by the
RrcConnStateTimer.UlSynTimerDynDrx parameter expires, the eNodeB assigns
the UE the DRX parameters for the out-of-synchronization state.
The eNodeB dynamically switches between the two types of DRX parameters based on UE
status.
5.1 Introduction
5.1.1 Definition and Application Scenarios
If UEs frequently move between cells while staying in connected mode for a long period of
time, a large number of handovers will be triggered, causing excessive handover signaling.
Especially after dynamic DRX is enabled, UEs stay in connected mode for a prolonged
period of time. In this scenario, if UEs move fast, instead of cell reselections, more handovers
are triggered. To prevent handover signaling from affecting eNodeB performance, the
eNodeB uses the high-mobility-triggered idle mode feature.
Definition
High-mobility-triggered idle mode is a state in which the number of handovers and the
amount of related signaling decrease after UEs enter idle mode based on their movement
speeds and the packet sending state.
Application Scenarios
The high-mobility-triggered idle mode feature is mainly used on mobile networks where most
UEs are smart terminals. This feature is suitable for UEs that stay in connected mode and
move frequently, especially for UEs in dynamic DRX mode.
5.1.2 Benefits
The high-mobility-triggered idle mode feature reduces the number of handovers and the
amount of signaling on the entire network, minimizing the impact of handover signaling on
network stability while maintaining user experience.
5.2 Principles
In high- mobility-triggered idle mode, eNodeBs determine whether to release UEs based on
their movement speeds, packet sending states, and camping times. For triggering conditions,
see Working Mechanism.
LTE networks are often deployed in hot spots that have the following characteristics:
In these hot spots, handovers are easily triggered for fast-moving UEs.
Table 5-1 and Table 5-2 list the movement speeds and camping times for a UE passing
through the center coverage areas of cells with radii of 300 m and 500 m.
Table 5-1 Movement speed and camping time of a UE in a cell with a radius of 300 m
Movement Speed (km/h) Camping Time (Seconds)
[30-60] [18-36]
[60-120] [18-9]
> 120 <9
Table 5-2 Movement speed and camping time of a UE in a cell with a radius of 500 m
Movement Speed (km/h) Camping Time (Seconds)
[30-60] [30-60]
[60-120] [15-30]
> 120 < 15
In reality, most UEs do not pass through the cell center and the camping time of these UEs is
even shorter.
In Figure 5-2, the x-axis specifies the service types and the y-axis specifies the number of
network access requests triggered by heartbeats within an hour. The heartbeat period is equal
to 3600 divided by the number of service requests.
You can extrapolate the following from the data shown in Figure 5-2:
During a heartbeat period, if the UE is moving fast, it may pass through several cells
and be handed over many times. For example, during a heartbeat period of 180s, a UE
moving at 30 km/h may pass through five 300 m radius cells. If the UE stays in
connected mode in this period, multiple handovers will be performed. During this
process, no service data is transmitted.
Most UEs have only heartbeat packets to transmit and receive for an extended period,
a period even longer than the time the UEs take to process other services.
Working Mechanism
To avoid a handover, the eNodeB triggers the S1 release procedure after receiving the
measurement report from a UE and instructs the UE to enter idle mode when all of the
following conditions are met:
The movement speed of the UE is greater than or equal to 30 km/h during the
camping.
The UE does not transmit data when it is camping on a cell.
The camping time is greater than or equal to 10s.
As the UE has data to transmit only when a heartbeat period begins, instructing the UE to
enter idle mode has no impact on the UE's services.
Figure 5-3 shows the working mechanism of the high-mobility-triggered idle mode feature.
6 Related Features
6.1 Features Related to LBFD-002017 DRX
Prerequisite Features
None
When DRX is enabled in ultra high speed mobility scenarios, the handover success rate
decreases, the service drop rate increases, and other performance indicators may also
deteriorate.
Impacted Features
Scheduling
When the UE is in the uplink pre-scheduling state, the eNodeB instructs the UE to
exit the uplink pre-scheduling state after the UE enters DRX mode. Upon exiting
DRX mode, the UE enters the pre-scheduling state.
When the UE is in the TTI bundling state (function provided in LOFD-001048 TTI
Bundling), the eNodeB does not instruct the UE to enter DRX mode unless required
during ANR measurement. When the UE is in DRX mode, the eNodeB instructs the
UE to exit DRX mode after TTI bundling is initiated. When the UE is performing
ANR measurements in DRX mode, the eNodeB does not instruct the UE to exit DRX
mode.
Connection Management
After receiving a handover decision indicating that the handover request has been
accepted, the source eNodeB sends an RRC Connection Reconfigura tion message to
instruct the UE to exit DRX mode. If this happens during sleep time, the UE will not
receive the message until after the next active time arrives.
The eNodeB determines whether to apply DRX to the UE based on whether DRX is
enabled.
The UE remains in the current cell, and the source eNodeB checks whether the UE
can enter DRX mode.
NOTE:
For details about the handover process in DRX mode, see Intra-RAT Mobility
Management in Connected Mode Feature Parameter Description
Measurement
NOTE:
For details about the handover process in DRX mode, see Intra-RAT Mobility Management in
Connected Mode Feature Parameter Description
UE measurement in the LTE system is classified into common measurement and gap-assisted
measurement. UE measurement in the LTE system is classified into common measurement
and gap-assisted measurement. Common measurement is used for intra-frequency
measurement, and gap-assisted measurement is used for inter-frequency measurement and
inter-radio access technology (RAT) measurement.
Common measurement
For random access, the UE enters the active state if it is in sleep time and then uses
the first available random access channel (RACH) to send UL measurement reports.
In other scenarios, the UE sends measurement reports only in active time. If the UE is
in the sleep state, it will send measurement reports in active time in the next DRX
cycle.
Gap-assisted measurement
As shown in Figure 6-1, gaps are generated every 40 ms, six TTIs earlier than the
DRX cycle.
CQI
In DRX mode, the UE turns off its receiver intermittently. When the UE is in the sleep state,
the eNodeB does not deliver channel quality indicator (CQI) or sounding reference signal
(SRS) measurement configurations and the UE reports the measurements in compliance with
the following protocol requirements:
For UEs complying with 3GPP Release 8, CQIs, precoding matrix indicators (PMIs),
and rank indicators (RIs) can be reported over the PUCCH only in active time.
For UEs complying with 3GPP Release 9, CQIs, PMIs, and RIs can be reported over
the PUCCH only in the On Duration.
The CellDrxPara.CqiMask parameter controls when CQIs, PMIs, and RIs can be reported
in the On Duration:
If this parameter is set to ON, CQIs, PMIs, and RIs can be reported only in the On
Duration.
If this parameter is set to OFF, CQIs, PMIs, and RIs can be reported in active time.
SRSs can be sent only in active time.
CQI configurations affect the settings of DRX parameters controlled by the eNodeB. The
eNodeB can automatically adjust the value of the operator-defined
DrxParaGroup.OnDurationTimer parameter so that the number of CQIs reported by the UE
during a period meets the requirements for downlink scheduling performance.
NOTE:
Currently, most UEs that comply with 3GPP Release 9 do not support CQI mask. Retain the
default value OFF of the CellDrxPara.CqiMask parameter for these UEs.
Timing Control
When SRSs are used for timing control, the TA measurement precision for uplink
synchronization depends on the number of times the UE reports SRSs. To acquire sufficient
SRSs, the eNodeB adaptively adjusts the value of the DrxParaGroup.LongDrxCycle
parameter based on the SRS configurations of the UE and the period set for delivery of TA
measurements to the UE. Therefore, the value delivered to the UE may differ from that set by
MML commands. The value must be a multiple of 10 ms because the SRS reporting period is
a multiple of 10 ms and the CQI reporting period is a multiple of 5 ms for Huawei eNodeBs.
The specific value depends on other parameters:
When demodulation reference signals (DMRSs) are used for timing control and DRX is
enabled, at least one active time must exist during the period set for delivery of TA
measurements so that the eNodeB can deliver scheduling information to trigger the delivery.
NOTICE:
The eNodeB configures DRX parameters for UEs based on parameter validity, protocol
compatibility, and chip compatibility. For example, UEs with Qualcomm chips consider the
settings of certain DRX parameters invalid and the RRC connection needs to be
reestablished. These DRX parameters may be adjusted after the validity check. Validity
check is performed to see whether:
The long DRX cycle should be an integer multiple of the short DRX cycle. Otherwise,
the short DRX cycle is automatically adjusted to an appropriate value.
The long DRX cycle should be an integer multiple of 10. Otherwise, it is
automatically adjusted to an appropriate value.
The OnDurationTimer value should be less than the short DRX cycle. Otherwise, the
short cycle is not configured.
The OnDurationTimer value should be less than the long DRX cycle. Otherwise, the
DRX parameters are not configured.
Carrier Aggregation
When carrier aggregation (CA) is enabled, the DRX mechanism works as follows:
If DRX is enabled in both the primary serving cell (PCell) and the secondary serving
cell (SCell) for a CA UE, when the serving eNodeB of the PCell sends an MCE
command to activate the SCell, the eNodeB will handle the UE states in the cells as
follows:
o If the UE has entered DRX mode in the PCell, the eNodeB will instruct the
UE to enter DRX mode in the SCell, with the DRX parameters for the PCell
applied to the SCell.
o If the UE has not entered DRX mode in the PCell, the eNodeB will determine
whether the UE should enter DRX mode in both the PCell and SCell based on
the traffic volume of the UE.
If DRX is enabled in the PCell but disabled in the SCell, the UE will exit DRX mode
(if it has entered this mode) after the SCell is configured for the UE.
If DRX is disabled in the PCell, the UE will not enter DRX mode in either the PCell
or the SCell, regardless of whether DRX is enabled in the SCell.
For details about CA features, see Carrier Aggregation Feature Parameter Description.
In high speed mobility scenarios, if the long DRX cycle is 40 ms or shorter, no obvious effect
will be seen in UE power saving; if the long DRX cycle is longer than 40 ms, SRS-based
timing and reference signal received power (RSRP) measurement will be affected. Both
configurations may result in a low handover success rate, a high service drop rate, a large
number of RRC connection reestablishments, and a low reestablishment success rate.
Therefore, DRX is not recommended for high speed mobility scenarios.
When LOFD-00110501 Dynamic DRX is enabled for ultra high speed mobility scenarios, the
handover success rate decreases, the service drop rate increases, and other performance
indicators may also deteriorate.
Impacted Features
LBFD-002017 DRX
The DRX parameters for UEs in the synchronization state used in LOFD-00110501 Dynamic
DRX are the same as the DRX parameters used in LBFD-002017 DRX. However, the two
features do not depend on each other.
When LOFD-00110501 Dynamic DRX is enabled, the switch for LBFD-002017 DRX cannot
control whether the DRX parameters for UEs in the synchronization state take effect.
Other features
The other impacted features of LOFD-00110501 Dynamic DRX are the same as those of
LBFD-002017 DRX. For details, see section 6.1 Features Related to LBFD-002017 DRX.
None
None
Impacted Features
None
7 Network Impact
7.1 LBFD-002017 DRX
System Capacity
None
Network Performance
The sleep time in DRX helps reduce UE power consumption but may increase delay for
ongoing services, resulting in decreased traffic volume or throughput.
After DRX is enabled, UEs can report CQIs only during active time. If the channel
quality of cell edge users (CEUs) fluctuates significantly during sleep time, the UEs
cannot report CQIs for modulation and coding scheme (MCS) adjustment in a timely
manner. As a result, the bit error rate (BER) for CEUs may increase, and the downlink
packet loss rate for voice services or data services may rise.
When the UE initiates CSFB during a handover, the eNodeB preferentially processes
the handover but fails to process the CSFB. After the handover, the mobility
management entity (MME) initiates the CSFB again. When DRX is enabled, the
presence of the sleep time increases the probability of CSFB during handovers. In this
case, the number of CSFB-triggered handover failures and the number of CSFB-
triggered handover attempts may increase, while the number of successful CSFB
executions remains unchanged. As a result, the CSFB-triggered handover success rate
may decrease, but this has a very little impact on user experience.
After DRX is enabled, multiple small packets accumulated during sleep time can be
scheduled all at once. The control channel element (CCE) usage and equivalent CCE
usage may decrease. However, the uplink/downlink cell throughput or user-perceived
uplink/downlink throughput may increase.
If there is severe uplink/downlink interference, cell edge users are less likely to be
scheduled and cell center users are more likely to be scheduled. If the PRB usage
remains at the highest level, DRX may increase the average CQI, uplink/downlink
cell throughput, or user-perceivable uplink/downlink throughput.
The impact on key performance indicators (KPIs) is dependent on the specific service type,
application scenario, and parameter configuration. Specific KPIs are not listed in this section.
NOTE:
When DRX is enabled, the eNodeB instructs the UE to exit the preallocation state. The
performance of TCP services with ping delay and a small size deteriorates, the uplink
throughput increases, and the number of RBs for uplink frequency-selective scheduling and
that for UL Comp decreases. For details, see Scheduling Feature Parameter Description.
In DRX mode, you can enable smart preallocation to reduce the impact of UE exiting the
preallocation state. However, the power saving effect will deteriorate as the smart
preallocation duration increases.
None
Network Performance
LOFD-00110501 Dynamic DRX has the same impact as LBFD-002017 DRX on network
performance. For details, see 7.1 LBFD-002017 DRX.
The total number of E-RAB releases decreases, while the number of abnormal E-RAB
releases slightly changes. The decreased number of E-RAB releases is equal to the
number of E-RABs in UE contexts when the UEs switch from the uplink
synchronization state to the uplink out-of-synchronization state.
To ensure the accuracy of the calculated service drop rate, add the value of the L.E-
RAB.Num.Syn2Unsyn counter to the denominator and subtract the value of the L.E-
RAB.Release.Unsyn counter from the denominator. The formula is as follows:
To ensure the accuracy of the calculated service RRC connection setup success rate,
add the value of the L.RRC.StateTrans.Unsyn2Syn.Succ counter to the numerator
and add the value of the L.RRC.StateTrans.Unsyn2Syn counter to the denominator.
The formula is as follows:
Service RRC connection setup success rate (%) = (L.RRC.ConnReq.Succ.Mt +
L.RRC.ConnReq.Succ.MoData + L.RRC.ConnReq.Succ.EMC +
L.RRC.ConnReq.Succ.HighPri + L.RRC.ConnReq.Succ.DelayTol +
L.RRC.StateTrans.Unsyn2Syn.Succ)/(L.RRC.ConnReq.Att.Mt +
L.RRC.ConnReq.Att.MoData + L.RRC.ConnReq.Att.EMC +
L.RRC.ConnReq.Att.HighPri + L.RRC.ConnReq.Att.DelayTol +
L.RRC.StateTrans.Unsyn2Syn)
The number of E-RAB setups decreases significantly. In some scenarios (for example,
weak coverage scenarios), the number of failed E-RAB setups does not decrease
proportionately. The number of decreased E-RAB setups converts into the number of
times UEs switch from the out-of-synchronization state to the synchronization state.
To ensure the accuracy of the calculated E-RAB setup success rate, add the value of
the L.E-RAB.StateTrans.Unsyn2Syn.Succ counter to the numerator and add the
value of the L.E-RAB.StateTrans.Unsyn2Syn.Att counter to the denominator. The
formula is as follows:
When dynamic DRX is enabled, dedicated preambles are used in the switching from the out-
of-synchronization state to the synchronization state caused by downlink data transmission
and the number of contention-based random access attempts decreases. If the number of
contention-based random access failures remains unchanged, the contention-based random
access success rate will decrease.
No impact.
Network Performance
This feature decreases the number of handovers for fast-moving UEs, reduces the impact of
handover signaling on the network, and lowers the CPU usage of the eNodeB.
8.3 Planning
RF Planning
N/A
Network Planning
N/A
Hardware Planning
N/A
8.4 Deployment
8.4.1 Requirements
Operating Environment
N/A
Transmission Networking
N/A
License
This section describes the data that you need to collect for setting parameters. Required data
is data that you must collect for all scenarios. Collect scenario-specific data when necessary
for a specific feature deployment scenario.
Network plan (negotiation not required): parameter values planned and set by the
operator
Network plan (negotiation required): parameter values planned by the operator and
negotiated with the evolved packet core (EPC) or peer transmission equipment
User-defined: parameter values set by users
Required Data
The following table describes the parameters that must be set in a CellDrxPara MO to
configure cell-level DRX parameters.
Scenario-specific Data
The following table describes the parameters that must be set in a Drx MO to configure
eNodeB-level DRX parameters.
The following table describes the parameters that must be set in a DrxParaGroup MO to
configure DRX parameter groups.
Set the
DrxParaGroup.DrxInactivityTimer
parameter to PSF100(100 PDCCH
subframes) if the
DrxParaGroup.LongDrxCycle
parameter is set to SF320(320
subframes).
DRX DrxParaGroup.DrxReTxTi Networ This parameter specifies the length of
Retransmi mer k plan the DRX Retransmission Timer.
ssion (negotia
Timer tion not
required
)
Long DrxParaGroup.LongDrxC Networ This parameter specifies the length of a
DRX ycle k plan long DRX cycle.
Cycle (negotia
tion not A larger parameter value results in a
required longer sleep time and a longer delay.
)
When the
TimeAlignmentTimer.TimingAdvC
mdOptSwitch parameter is set to
ON(On),
NOTICE:
Set the
DrxParaGroup.DrxShortCycleTim
er parameter to 1 if the
DrxParaGroup.LongDrxCycle
parameter is set to SF320(320
subframes).
NOTE:
The following table describes the parameters that must be set in a CellStandardQci MO to
map parameter groups to standardized QCIs in cells.
The following table describes the parameters that must be set in CellExtendedQci MOs to
map parameter groups to extended QCIs in cells.
The following table describes the parameter that must be set in a TimeAlignmentTimer MO
to specify the length of the uplink time alignment timer for UEs in a cell.
When the
TimeAlignmentTimer.TimingAdv
CmdOptSwitch parameter is set to
ON(On), it is recommended that the
TimeAlignmentTimer.TimeAlignm
entTimer parameter be set to
SF10240(10240 subframes). If the
TimeAlignmentTimer.TimeAlignm
entTimer parameter is set to a small
value, for example, less than
SF5120(5120 subframes), the
probability of uplink out-of-
synchronization for UEs in DRX
mode increases.
The following table describes the parameters that must be set in a Drx MO to configure
eNodeB-level DRX parameters.
The value
SF10(10
subframes) is
recommended.
Special On Duration timer Drx.OnDurationTimerSpecial Network This
plan parameter
(negotiatio specifies the
n not length of the
required) On Duration
Timer that is
applicable
only to non-
power-saving
UEs whose
RFSP indexes
are contained
in the RFSP
index set.
A larger
parameter
value results
in a longer
active time
and a shorter
delay. A
smaller
parameter
value results
in a shorter
active time
Parameter Name Parameter ID Data Setting Notes
Source
and a longer
delay.
The value
PSF5(5
PDCCH
subframes) is
recommended.
Special DRX inactivity Drx.DrxInactivityTimerSpecial Network This
timer plan parameter
(negotiatio specifies the
n not length of the
required) DRX
Inactivity
Timer that is
applicable
only to non-
power-saving
UEs whose
RFSP indexes
are contained
in the RFSP
index set.
The value
PSF10(10
PDCCH
subframes) is
recommended.
Special short-cycle DRX Drx.SupportShortDrxSpecial Network This
supported indication plan parameter
(negotiatio specifies
n not whether to
required) enable short
DRX cycles
for non-
power-saving
UEs whose
RFSP indexes
are contained
in the RFSP
index set.
The value
UU_DISABL
E is
Parameter Name Parameter ID Data Setting Notes
Source
recommended.
ShortDrxCycleSpecial Drx.ShortDrxCycleSpecial Network This
plan parameter
(negotiatio specifies the
n not length of a
required) short DRX
cycle that is
applicable
only to non-
power-saving
UEs whose
RFSP indexes
are contained
in the RFSP
index set.
The value
SF10(10
subframes) is
recommended.
DrxShortCycleTimerSpeci Drx.DrxShortCycleTimerSpeci Network This
al al plan parameter
(negotiatio specifies the
n not length of the
required) DRX Short
Cycle Timer
that is
applicable
only to non-
power-saving
UEs whose
RFSP indexes
are contained
in the RFSP
index set.
The value 1 is
recommended.
The following table describes the parameters that must be set in a Drx MO to configure DRX
parameters for ANR measurements.
Parameter Parameter ID Data Setting Notes
Name Source
Long DRX Drx.LongDrxCycleForAnr Network This parameter specifies the
Cycle for plan long DRX cycle for intra-
ANR (negotiation RAT ANR. If intra-RAT
not ANR is enabled, this
required) parameter is valid regardless
of whether DRX is disabled.
Set this parameter to
SF256(256 subframes) or a
larger value to increase the
ANR measurement success
rate.
Long DRX Drx.LongDRXCycleforIRatAnr Network This parameter specifies the
Cycle for plan long DRX cycle for inter-
Inter-RAT (negotiation RAT ANR. If inter-RAT
ANR not ANR is enabled, this
required) parameter is valid regardless
of whether DRX is disabled.
8.4.3 Precautions
None
N/A
8.4.5 Activation
8.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in the following tables in a summary data file, which
also contains other data for the new eNodeBs to be deployed. Then, import the summary data
file into the Configuration Management Express (CME) for batch configuration. For detailed
instructions, see "Creating eNodeBs in Batches" in the initial configuration guide for the
eNodeB, which is available in the eNodeB product documentation.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
The managed objects (MOs) in the following tables are contained in a scenario-
specific summary data file. In this situation, set the parameters in the MOs, and then
verify and save the file.
Some MOs in the following tables are not contained in a scenario-specific summary
data file. In this situation, customize a summary data file to include the MOs before
you can set the parameters.
Scenario 1: Setting DRX Parameters for Common UEs
User-defined sheets are recommended. The following table describes the MOs in the sheets.
User-defined sheets are recommended. The following table describes the MOs in the sheets.
User-defined sheets are recommended. The following table describes the MOs in the sheets.
8.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch Activation
This feature can be batch activated using the CME. For detailed operations, see the following
section in the CME product documentation or online help: Managing the CME > CME
Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.
Batch Reconfiguration
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure. The procedure is as follows:
1. Customize a summary data file with the MOs and parameters listed in section "Using
the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For
detailed operations, press F1 in a CME window and navigate to Managing the CME
> CME Guidelines > LTE Application Management > eNodeB Related
Operations > Customizing a Summary Data File for Batch eNodeB
Configuration in the CME online help.
2. Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export
Data > Export Base Station Bulk Configuration Data (CME client mode), to
export the eNodeB data stored on the CME into the customized summary data file.
3. In the summary data file, set the parameters in the MOs according to the setting notes
provided in section "Data Preparation" and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import
Data > Import Base Station Bulk Configuration Data (CME client mode), to
import the summary data file into the CME, and then start the data verification.
5. After data verification is complete, choose CME > Planned Area > Export
Incremental Scripts (U2000 client mode), or choose Area Management > Planned
Area > Export Incremental Scripts (CME client mode), to export and activate the
incremental scripts. For detailed operations, see Managing the CME > CME
Guidelines > Script File Management > Exporting Incremental Scripts from a
Planned Data Area in the CME online help.
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
1. In the planned data area, click Base Station in the upper left corner of the
configuration window.
2. In area 1 shown in Figure 8-1, select the eNodeB to which the MOs belong.
3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this
MO are displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode),
or choose Area Management > Planned Area > Export Incremental Scripts (CME
client mode), to export and activate the incremental scripts.
MML Command
Scenario 1: Setting DRX Parameters for Common UEs
3. (Optional) If extended QCI 10 has been configured for a cell, run the MOD
CELLEXTENDEDQCI command to bind a DRX parameter group to the extended
QCI for a cell.
4. If the long DRX cycle is equal to or longer than 80 ms, run the MOD TATIMER
command to modify the TimeAlignmentTime r.TimeAlignmentTimer parameter.
7. (Optional) To allow the eNodeB to select DRX parameters based on QCI priorities,
run the MOD CELLDRXPARA command to specify a DRX parameter selection
policy and run the MOD CELLSTANDARDQCI command to set DRX priorities
used in DRX parameter selection.
8. MOD CELLDRXPARA: LocalCellId=0, DrxPolicyMode=QCIPRIORITY;
MOD CELLSTANDARDQCI: LocalCellId=0, Qci=QCI9, QciPriorityForDrx=9;
Run the MOD DRX command to set DRX parameters for ANR measurements.
4. Enable a UE to access the network and maintain low traffic in the uplink and
downlink on the UE. Then, check the RRC Connection Reconfiguration message
(displayed as RRC_CONN_RECFG on the tracing client) on the Uu interface.
If the message contains DRX parameters as shown in Figure 8-2, the eNodeB has
instructed the UE to enter DRX mode.
NOTE:
Due to the limitation of the CQI and SRS, the configured values for the
DrxParaGroup.OnDurationTimer and DrxParaGroup.LongDrxCycle
parameters are inconsistent with the values delivered by the eNodeB.
The prerequisite for this scenario is that an SPID has been set on the EPC for the international
mobile subscriber identity (IMSI) of a UE.
1. Run the ADD SPIDCFG command to add the SPID configuration for the eNodeB.
2. Run the MOD DRX command to turn on the DRX switch.
3. Enable a UE to access the network and maintain low traffic in the uplink and
downlink on the UE. Then, check the RRC Connection Reconfiguration message
(displayed as RRC_CONN_RECFG on the tracing client) on the Uu interface.
If the message contains RFSP-specific DRX parameters as shown in Figure 8-3, the
eNodeB has instructed the UE to enter DRX mode.
The eNodeB configures or reconfigures DRX parameters for UEs during ANR measurement
regardless of whether the Drx.DrxAlgSwitch parameter is set to ON or OFF.
1. Run the MOD DRX command to turn on the DRX switch and set the
Drx.LongDrxCycleForAnr and Drx.LongDRXCycleforIRatAnr parameters.
o The value of the Drx.LongDrxCycleForAnr parameter is used as the long
DRX cycle if the ANR measurements are performed on E-UTRAN cells.
o The value of the Drx.LongDRXCycleforIRatAnr parameter is used as the
long DRX cycle if the ANR measurements are performed on GERAN or
UTRAN cells.
2. Check the RRC Connection Reconfiguration message on the Uu interface. (The RRC
Connection Reconfiguration message is delivered when ANR measurement is
required.)
If the message contains DRX parameters as shown in Figure 8-4, the eNodeB has
configured DRX parameters for the UE during ANR measurement.
3. Run the MOD DRX command to turn off the DRX switch.
4. Check the RRC Connection Reconfiguration message on the Uu interface when the
UE is successfully handed over to a new cell.
If the message contains DRX parameters, the eNodeB has configured DRX
parameters for the UE during ANR measurement.
8.4.7 Reconfiguration
eNodeBs are reconfigured for DRX in batches. For details, see the introduction to batch
reconfiguration operations in eNodeB Reconfiguration Guide.
8.4.8 Deactivation
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in 8.4.5.2 Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 8-1.
On the CME, set parameters according to Table 8-1. For detailed instructions, see 8.4.5.3
Using the CME to Perform Single Configuration described for feature activation.
1. Run the MOD DRX command to turn off the DRX switch.
8.5 Maintenance
8.5.1 Performance Monitoring
After activating this feature, use the following counters for monitoring:
It is expressed as the
proportion of the number of
TTIs with data transmission to
the total number of TTIs. If
the traffic volume at a UE is
equal to or below this
threshold, the eNodeB
instructs the UE to stay in or
enter DRX mode. The value of
the
CellDrxPara.FddEnterDrxT
hd parameter must be less
than that of the
CellDrxPara.FddExitDrxTh
d parameter under the same
Cell MO.
It is expressed as the
proportion of the number of
TTIs with data transmission to
the total number of TTIs. If
the traffic volume at a UE is
equal to or higher than this
threshold, the eNodeB
instructs the UE to stay in non-
DRX mode or exit DRX
mode. The value of the
CellDrxPara.FddEnterDrxT
hd parameter must be less
than that of the
CellDrxPara.FddExitDrxTh
d parameter under the same
Cell MO.
8.5.3 Troubleshooting
Fault Description
1. Run the LST DRX command to check the DRX switch setting.
o If the DRX switch setting is Off, run the MOD DRX command to turn on the
DRX switch.
o If the DRX switch setting is On, go to 2.
2. Run the LST CELLDRXPARA command to check the FDD enter DRX
threshold(per mill) parameter value.
o If the value is inappropriate, change the value by referring to 8.4.2 Data
Preparation.
o If the value is appropriate, go to 3.
3. Check whether the UE is performing a service with a large traffic volume.
o If the UE is performing a service with a large traffic volume, it does not enter
DRX mode.
o If the UE is performing a service with a very small traffic volume (for
example, ping or VoIP), repeat 2 and then go to 4.
4. Run the LST CELLSTANDARDQCI command to query the DRX parameter group
IDs corresponding to the QCIs used by the UE.
5. Run the LST DRXPARAGROUP command to check the Enter DRX Switch
settings for the DRX parameter group IDs.
o If any Enter DRX Switch setting is Off, run the MOD DRXPARAGROUP
command to turn on the corresponding DRX switch or stop the ongoing
service on the corresponding bearer.
o If all the Enter DRX Switch settings are On, contact Huawei technical
support.
In this scenario, you are advised to set a large difference between the value of the
RrcConnStateTimer.UeInactivityTimerDynDrx parameter and that of the
RrcConnStateTimer.UlSynTimerDynDrx parameter. This enables UEs to be in the
out-of-synchronization state for a longer time, thereby improving the power saving
performance. In addition, it is recommended that both the
CellDrxPara.FddEnterDrxThd and CellDrxPara.FddExitDrxThd parameters be
set to 1000 and the CellDrxPara.DrxInactivityTimerUnsync parameter be set to
200 ms so that UEs can save more power.
NOTE:
If operators do not use dynamic DRX to reduce signaling, perform the following
operations to avoid KPI fluctuations:
o Set the RrcConnStateTimer.UeInactivityTimerDynDrx parameter to the
value a.
o Set the RrcConnStateTimer.UlSynTimerDynDrx parameter to the value b.
If operators use dynamic DRX to reduce signaling, perform the following operations
to ensure KPI accuracy:
1. Set the RrcConnStateTimer.UlSynTimerDynDrx and
RrcConnStateTimer.UlSynTimer parameters to the value a.
2. Set the RrcConnStateTimer.UeInactivityTimerDynDrx and
RrcConnStateTimer.UeInactiveTimer parameters to a value greater than
the value a. Set the RrcConnStateTimer.UeInactivityTimerDynDrx and
RrcConnStateTimer.UeInactiveTimer parameters to the same value.
L.Traffic.PktInterval.Num.Index0
L.Traffic.PktInterval.Num.Index1
L.Traffic.PktInterval.Num.Index2
L.Traffic.PktInterval.Num.Index3
L.Traffic.PktInterval.Num.Index4
L.Traffic.PktInterval.Num.Index5
L.Traffic.PktInterval.Num.Index6
L.Traffic.PktInterval.Num.Index7
L.Traffic.PktInterval.Num.Index8
L.User.UL.Unsync.Dur.Index0
L.User.UL.Unsync.Dur.Index1
L.User.UL.Unsync.Dur.Index2
L.User.UL.Unsync.Dur.Index3
L.User.UL.Unsync.Dur.Index4
L.User.UL.Unsync.Dur.Index5
L.User.UL.Unsync.Dur.Index6
L.User.UL.Unsync.Dur.Index7
L.User.UL.Unsync.Dur.Index8
9.3 Planning
RF Planning
To reduce signaling bursts caused by frequent access and release on live networks without
coverage problems (for example, without ping-pong handovers), dynamic DRX prolongs the
time UEs stay in connected mode. The networks must meet the following coverage
requirements:
No coverage holes.
No overshoot coverage.
No pilot pollution.
No path loss imbalance between uplink and downlink.
Network Planning
N/A
Hardware Planning
N/A
9.4 Deployment
9.4.1 Requirements
Operating Environment
N/A
Transmission Networking
N/A
License
The operator has purchased and activated the license for the feature listed in Table 9-1.
This section describes the data that you need to collect for setting parameters. Required data
is data that you must collect for all scenarios. Collect scenario-specific data when necessary
for a specific feature deployment scenario.
Network plan (negotiation not required): parameter values planned and set by the
operator
Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
User-defined: parameter values set by users
Required Data
N/A
Scenario-specific Data
NOTE:
If operators do not use dynamic DRX to reduce signaling, perform the following
operations to avoid KPI fluctuations:
If operators use dynamic DRX to reduce signaling, perform the following operations
to ensure KPI accuracy:
Set the RrcConnStateTimer.UlSynTimerDynDrx and
RrcConnStateTimer.UlSynTimer parameters to the value a.
The total number of E-RAB releases decreases, while the number of abnormal E-RAB
releases changes slightly. The number of decreased E-RAB releases converts into the
number of E-RABs in UE contexts when the UEs switch from the uplink
synchronization state to the uplink out-of-synchronization state. In this situation, use
the following new method to calculate the service drop rate:
The number of RRC connection setups decreases significantly. In some scenarios (for
example, weak coverage scenarios), the number of failed RRC connection setups does
not decrease proportionally. The number of decreased RRC connection setups
converts into the number of times UEs switch from the out-of-synchronization state to
the synchronization state. In this situation, use the following new method to calculate
the success rate of RRC connection setups for services:
The following table describes the parameter that must be set in the CellAlgoSwitch MO to
modify the cell-level DRX parameters.
Parameter Parameter ID Data Setting Notes
Name Source
Dynamic CellAlgoSwitch.DynDrxSwitch Network This parameter specifies
DRX plan whether to enable dynamic
switch (negotiation DRX.
not
required) If this switch is turned
on, dynamic DRX
applied to newly
accessed UEs.
When this switch is
turned off, the UEs that
access the network
cannot use dynamic
DRX.
The following table describes the parameters that must be set in the CellAccess MO to avoid
compatibility issues of UEs.
If this parameter
is set to
CFG(Configure
), no
synchronization
procedures
repeatedly
initiated by a UE
having
compatibility
issues trigger the
RRC connection
reconfiguration
procedure.
If this parameter
is set to
NOT_CFG(Not
configure), all
synchronization
procedures
repeatedly
initiated by a UE
having
compatibility
issues trigger the
RRC connection
reconfiguration
procedure.
NOTE:
For more information regarding UE compatibility issues, see 9.5.1 Performance Monitoring.
9.4.3 Precautions
When dynamic DRX is enabled, DRX for the synchronization state takes effect. The
CellDrxPara.FddEnterDrxThd and CellDrxPara.FddExitDrxThd parameters should be
set to 1000 to reduce signaling exchange over the air interface. When these parameters are set
to 1000, the eNodeB directly instructs the UE to enter or exit DRX mode, without
considering the measured traffic volume.
To prevent UE compatibility issues, when dynamic DRX is enabled, you are advised to set
DRX parameters for all bearers on the live network, including bearers with QCIs 2, 3, and 7.
If bearers with QCI 2 or 3 exist on the live network without setting the DRX
parameters, you can run the following command to set the DRX parameters for QCI 2
or 3:
DrxParaGroup.LongDrxCycle=sf10,DrxParaGroup.OnDurationTimer=psf8,
DrxParaGroup.DrxInactivityTimer=psf10
If bearers with QCI 7 exist on the live network, different DRX parameter groups can
be used for the bearers based on the QCI definitions of operators when dynamic DRX
is enabled. For example, bind QCI 7 to DRX parameter group 2 or 3 by running the
MOD CELLSTANDARDQCI command.
N/A
9.4.5 Activation
9.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 9-2 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in
Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB
product documentation.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
The MOs in Table 9-2 are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
Some MOs in Table 9-2 are not contained in a scenario-specific summary data file. In
this situation, customize a summary data file to include the MOs before you can set
the parameters.
9.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch Activation
This feature can be batch activated using the CME. For detailed operations, see the following
section in the CME product documentation or online help: Managing the CME > CME
Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.
Batch Reconfiguration
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure. The procedure is as follows:
1. Customize a summary data file with the MOs and parameters listed in section "Using
the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For
detailed operations, press F1 in a CME window and navigate to Managing the CME
> CME Guidelines > LTE Application Management > eNodeB Related
Operations > Customizing a Summary Data File for Batch eNodeB
Configuration in the CME online help.
2. Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export
Data > Export Base Station Bulk Configuration Data (CME client mode), to
export the eNodeB data stored on the CME into the customized summary data file.
3. In the summary data file, set the parameters in the MOs according to the setting notes
provided in section "Data Preparation" and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import
Data > Import Base Station Bulk Configuration Data (CME client mode), to
import the summary data file into the CME, and then start the data verification.
5. After data verification is complete, choose CME > Planned Area > Export
Incremental Scripts (U2000 client mode), or choose Area Management > Planned
Area > Export Incremental Scripts (CME client mode), to export and activate the
incremental scripts. For detailed operations, see Managing the CME > CME
Guidelines > Script File Management > Exporting Incremental Scripts from a
Planned Data Area in the CME online help.
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
1. In the planned data area, click Base Station in the upper left corner of the
configuration window.
2. In area 1 shown in Figure 9-1, select the eNodeB to which the MOs belong.
Figure 9-1 MO search and configuration window
3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this
MO are displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode),
or choose Area Management > Planned Area > Export Incremental Scripts (CME
client mode), to export and activate the incremental scripts.
MML Command
LST RRCCONNSTATETIMER:;
2. If operators do not use dynamic DRX to reduce signaling, perform the following
operations to avoid KPI fluctuations:
o Set the RrcConnStateTimer.UeInactivityTimerDynDrx parameter to the
value a.
o Set the RrcConnStateTimer.UlSynTimerDynDrx parameter to the value b.
To save more power, ensure that the value of
RrcConnStateTimer.UlSynTimerDynDrx is less than the value of
RrcConnStateTimer.UeInactivityTimerDynDrx and the difference between the
two values is large enough. This configuration does not increase the number of UEs in
connected mode.
3. If operators use dynamic DRX to reduce signaling, perform the following operations
to ensure KPI accuracy:
a. Set the RrcConnStateTimer.UlSynTimerDynDrx and
RrcConnStateTimer.UlSynTimer parameters to the value a.
b. Set the RrcConnStateTimer.UeInactivityTimerDynDrx and
RrcConnStateTimer.UeInactiveTimer parameters to the same value that is
greater than the value a.
MOD
RRCCONNSTATETIMER:UeInactivityTimerDynDrx=200,UeInactiveTimer=200,UlS
ynTimerDynDrx =20,UlSynTimer =20;
4. After 3 is performed, if the KPI deteriorates, use the new formula to calculate the
service drop rate, as described in 9.4.2 Data Preparation. If the KPI does not
deteriorate, proceed to the next step.
5. Run the MOD CELLDRXPARA command to configure DRX parameters in the out-
of-synchronization state. To save more power, it is recommended that the
CellDrxPara.FddEnterDrxThd and CellDrxPara.FddExitDrxThd parameters be
set to 1000 and that the CellDrxPara.DrxInactivityTimerUnsync parameter be set
to 200 ms. That way UEs do not enter or exit DRX mode in the synchronization state
based on the traffic statistics. The DRX parameters for the synchronization state
remain the same as those configured before dynamic DRX is enabled.
MOD CELLDRXPARA:LocalCellID=0,LongDrxCycleUnsync=SF
1280,OndurationTimerUnsync=PSF5,DrxInactivityTimerUnsync=PSF200,FddEn
terDrxThd =1000,FddExitDrxThd = 1000;
MOD CELLALGOSWITCH:LocalCellId=0,DynDrxSwitch=DynDrxSwitch-1;
9.4.7 Reconfiguration
N/A
9.4.8 Deactivation
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is simila r to that for
feature activation described in 9.4.5.2 Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 9-3.
On the CME, set parameters according to Table 9-3. For detailed instructions, see 9.4.5.3
Using the CME to Perform Single Configuration described for feature activation.
MOD CELLALGOSWITCH:LocalCellId=0,DynDrxSwitch=DynDrxSwitch-0;
9.5 Maintenance
9.5.1 Performance Monitoring
After dynamic DRX is enabled, monitor the power or signaling saving effect.
You can monitor the power saving effect in either of the following ways:
For example, when the DRX cycle is 40 ms, the UE does not turn off its
receiver; when the DRX cycle is 1280 ms, the UE turns off its receiver in
certain conditions. The L.Cdrx.Sleep.TtiNum counter indicates that less than
7% power is saved but actually more than 20% power is saved after the DRX
cycle increases from 40 ms to 1280 ms, provided that the traffic model
remains unchanged.
NOTE:
If the value of RrcConnStateTime r.UlSynTimerDynDrx after dynamic DRX is
enabled is less than the value of RrcConnStateTimer.UlSynTimer before dynamic
DRX is enabled, the signaling saving effect decreases.
o Use the following counters to monitor the number of RRC connection setup
attempts in different scenarios and the changes in signaling overhead:
L.RRC.ConnReq.Att
L.RRC.ConnReq.Att.Emc,
L.RRC.ConnReq.Att.HighPri
L.RRC.ConnReq.Att.Mt
L.RRC.ConnReq.Att.MoSig
L.RRC.ConnReq.Att.MoData,
L.RRC.ConnReq.Att.DelayTol.
L.E-RAB.AttEst + (L.Signal.Num.DRX.Reconfig +
L.RRC.StateTrans.Syn2Unsyn) / 10
NOTE:
In reduced signaling mode, some UEs are considered to have compatibility issues if one of
the following conditions is met:
Under these conditions, multiple RRC connection reconfigurations are performed each time
the UE switches from the out-of-synchronization state to the synchronization state. To avoid
an increase in abnormal signaling overhead caused by such a UE, you are advised to perform
the following operations:
This section describes the parameters that can be modified to improve dynamic DRX
performance.
The following table describes the UE control timer parameters that can be modified in the
RrcConnStateTimer MO to adjust the balance between power saving and reduced signaling.
The following table describes the cell-level DRX parameters that can be modified in the
CellDrxPara MO to improve DRX performance in the out-of-synchronization state.
9.5.3 Troubleshooting
Fault Description
Dynamic DRX is never triggered after the network is put into use.
Fault Handling
1. Run the LST CELLALGOSWITCH command to query the Dynamic DRX switch
setting.
o If the Dynamic DRX switch setting is DynDrxSwitch:Off, run the MOD
CELLALGOSWITCH command to set it to DynDrxSwitch:On.
o If the Dynamic DRX switch setting is DynDrxSwitch:On, go to 2.
2. Run the LST CELLSTANDARDQCI command to query the DRX parameter group
IDs corresponding to the QCIs used by the UE.
3. Run the LST DRXPARAGROUP command to check the Enter DRX Switch
settings for the DRX parameter group IDs.
o If any Enter DRX Switch setting is Off, run the MOD DRXPARAGROUP
command to turn on the corresponding DRX switch or stop the ongoing
service on the corresponding bearer.
o If all the Enter DRX Switch settings are On, contact Huawei technical
support.
10.3 Planning
RF Planning
On live networks with no coverage problems, the high-mobility-triggered idle mode feature
prevents signaling bursts by reducing the handover frequency for high-mobility UEs.
Therefore, the networks must meet the following coverage requirements:
No coverage holes.
No overshoot coverage.
No pilot pollution.
No path loss imbalance between uplink and downlink.
Network Planning
N/A
Hardware Planning
N/A
10.4 Deployment
10.4.1 Requirements
Operating Environment
N/A
Transmission Networking
N/A
License
The operator has purchased and activated the license for the feature listed in Table 10-1.
Table 10-1 License information for the high- mobility-triggered idle mode feature
Feature ID Feature Name Model License Control NE Sales
Item Unit
LOFD-001105 Dynamic DRX LT1S00DDRX00 Dynamic DRX eNodeB per cell
(FDD)
After purchasing and activating this license, you must set the
CellAlgoSwitch.HighMobiTrigIdleModeSwitch parameter to ENABLE(Enable) to
enable the high- mobility-triggered idle mode feature.
Related Features
It is recommended that you enable LOFD-00110501 Dynamic DRX before enabling LOFD-
00110502 High-Mobility- Triggered Idle Mode.
This section describes the data that you need to collect for setting parameters. Required data
is data that you must collect for all scenarios. Collect scenario-specific data when necessary
for a specific feature deployment scenario.
Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
Network plan (negotiation not required): parameter values planned and set by the
operator
User-defined: parameter values set by users
Required Data
The following table describes the parameters that must be set in the CellAlgoSwitch MO to
configure the high-mobility-triggered idle mode feature.
10.4.3 Precautions
None
N/A
10.4.5 Activation
10.4.5.1 Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs
Enter the values of the parameters listed in Table 10-2 in a summary data file, which also
contains other data for the new eNodeBs to be deployed. Then, import the summary data file
into the CME for batch configuration. For detailed instructions, see "Creating eNodeBs in
Batches" in the initial configuration guide for the eNodeB, which is available in the eNodeB
product documentation.
The summary data file may be a scenario-specific file provided by the CME or a customized
file, depending on the following conditions:
The MOs in Table 10-2 are contained in a scenario-specific summary data file. In this
situation, set the parameters in the MOs, and then verify and save the file.
Some MOs in Table 10-2 are not contained in a scenario-specific summary data file.
In this situation, customize a summary data file to include the MOs before you can set
the parameters.
Table 10-2 Parameter for activating the high-mobility-triggered idle mode feature
10.4.5.2 Using the CME to Perform Batch Configuration for Existing eNodeBs
Batch Activation
This feature can be batch activated using the CME. For detailed operations, see the following
section in the CME product documentation or online help: Managing the CME > CME
Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.
Batch Reconfiguration
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing eNodeBs. This method reconfigures all data, except neighbor relationships, for
multiple eNodeBs in a single procedure. The procedure is as follows:
1. Customize a summary data file with the MOs and parameters listed in section "Using
the CME to Perform Batch Configuration for Newly Deployed eNodeBs." For
detailed operations, press F1 in a CME window and navigate to Managing the CME
> CME Guidelines > LTE Application Management > eNodeB Related
Operations > Customizing a Summary Data File for Batch eNodeB
Configuration in the CME online help.
2. Choose CME > LTE Application > Export Data > Export Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Export
Data > Export Base Station Bulk Configuration Data (CME client mode), to
export the eNodeB data stored on the CME into the customized summary data file.
3. In the summary data file, set the parameters in the MOs according to the setting notes
provided in section "Data Preparation" and close the file.
4. Choose CME > LTE Application > Import Data > Import Base Station Bulk
Configuration Data (U2000 client mode), or choose LTE Application > Import
Data > Import Base Station Bulk Configuration Data (CME client mode), to
import the summary data file into the CME, and then start the data verification.
5. After data verification is complete, choose CME > Planned Area > Export
Incremental Scripts (U2000 client mode), or choose Area Management > Planned
Area > Export Incremental Scripts (CME client mode), to export and activate the
incremental scripts. For detailed operations, see Managing the CME > CME
Guidelines > Script File Management > Exporting Incremental Scripts from a
Planned Data Area in the CME online help.
On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.
The procedure is as follows:
1. In the planned data area, click Base Station in the upper left corner of the
configuration window.
2. In area 1 shown in Figure 10-1, select the eNodeB to which the MOs belong.
3. On the Search tab page in area 2, enter an MO name, for example, CELL.
4. In area 3, double-click the MO in the Object Name column. All parameters in this
MO are displayed in area 4.
5. Set the parameters in area 4 or 5.
6. Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode),
or choose Area Management > Planned Area > Export Incremental Scripts (CME
client mode), to export and activate the incremental scripts.
10.4.5.4 Using MML Commands
Run the MOD CELLALGOSWITCH command with the High Mobility Triggered Idle
Mode Switch parameter set to ENABLE(Enable) to enable the high-mobility-triggered idle
mode feature.
10.4.7 Reconfiguration
N/A
10.4.8 Deactivation
Batch reconfiguration using the CME is the recommended method to deactivate a feature on
eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple
eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for
feature activation described in 10.4.5.2 Using the CME to Perform Batch Configuration for
Existing eNodeBs. In the procedure, modify parameters according to Table 10-3.
Table 10-3 Parameter for deactivating the high-mobility-triggered idle mode feature
MO Sheet in the Parameter Group Remarks
Summary Data
File
CellAlgoSwitch eNodeB Radio High Mobility Triggered Set the High Mobility
Data Idle Mode Switch Triggered Idle Mode
Switch parameter to
DISABLE(Disable).
On the CME, set parameters according to Table 10-3. For detailed instructions, see 10.4.5.3
Using the CME to Perform Single Configuration described for feature activation.
MOD CELLALGOSWITCH:HighMobiTrigIdleModeSwitch=Disable;
10.5 Maintenance
10.5.1 Performance Monitoring
N/A
10.5.3 Troubleshooting
Fault Description
The high-mobility-triggered idle mode feature has never been triggered after the network is
put into use.
Fault Handling
Run the LST CELLALGOSWITCH command to query the High Mobility Triggered Idle
Mode Switch parameter value.
If the High Mobility Triggered Idle Mode Switch parameter value is Disable, run
the MOD CELLALGOSWITCH command to set it to ENABLE(Enable).
If the High Mobility Triggered Idle Mode Switch parameter value is Enable,
contact Huawei technical support.
11 Parameters
Table 11-1 Parameters
MO Parameter MML Feature Feature Description
ID Command ID Name
DrxPara EnterDrxSwit ADD LBFD- DRX Meaning: Indicates whether
Group ch DRXPARA 002017 bearers to which the parameter
GROUP / group applies support DRX.
TDLBF The value ON indicates that
MOD D- the bearers support DRX. The
DRXPARA 002017 value OFF indicates that the
GROUP bearers do not support DRX.
Unit: subframe
Unit: subframe
Unit: subframe
Unit: subframe
Unit: subframe
Unit: None
Default Value: 1
DrxPara SupportShort ADD LBFD- DRX Meaning: Indicates whether
Group Drx DRXPARA 002017 short DRX cycles are enabled.
GROUP /
TDLBF GUI Value Range:
MOD D- UU_DISABLE(Disable),
DRXPARA 002017 UU_ENABLE(Enable)
GROUP
Unit: None
LST
DRXPARA Actual Value Range:
GROUP UU_DISABLE,
UU_ENABLE
Default Value:
UU_ENABLE(Enable)
Drx DrxAlgSwitc MOD DRX LBFD- DRX Meaning: Indicates the DRX
h 002017 switch. The setting of this
LST DRX / parameter has no effect on
TDLBF dynamic DRX. DRX applies
D- to a CA UE only when this
002017 parameter is set to ON(On) on
both eNodeBs to which the
PCell and SCell of the CA UE
belong.
Unit: None
MO Parameter MML Feature Feature Description
ID Command ID Name
Actual Value Range: OFF, ON
Unit: 20ms
Default Value: 30
CellDrxP FddExitDrxT MOD LBFD- DRX Meaning: Indicates the
ara hd CELLDRX 002017 threshold for UEs to exit the
PARA / discontinuous reception
TDLBF (DRX) mode in a cell that
LST D- operates in FDD mode. This
CELLDRX 002017 threshold is used in the DRX
PARA algorithm. It is expressed as a
proportion of the transmission
time intervals (TTIs) with data
transmission to the total TTIs.
If the measurement result of
UE traffic is higher than this
threshold, the eNodeB
determines that the UE should
remain in the non-DRX mode
or the UE should be triggered
to exit the DRX mode. If the
value of the FddExitDrxThd
parameter is set to 1000 and
the value of the
FddEnterDrxThd parameter is
set to a value smaller than
1000, the UE will not exit the
DRX mode once entering the
DRX mode. If both the values
of the FddExitDrxThd and
FddEnterDrxThd parameters
are small and close to each
other, the UE frequently enters
and exits the DRX mode.
When both the
FddEnterDrxThd parameter
MO Parameter MML Feature Feature Description
ID Command ID Name
and the FddExitDrxThd
parameter are set to 1000 and
DRX is enabled, the eNodeB
directly determines that the UE
should enter or exit the DRX
mode, but not according to the
measurement result of UE
traffic.
Unit: None
Unit: subframe
Unit: subframe
Unit: subframe
Unit: None
Default Value:
UU_DISABLE(Disable)
Drx ShortDrxCycl MOD DRX LBFD- DRX Meaning: Indicates the length
eSpecial 002017 of a short DRX cycle that is
LST DRX / applied only to non-power-
TDLBF saving UEs whose subscriber
D- profile ID for RAT/frequency
002017 priority (RFSP) indexes are
contained in the RFSP index
set or to UEs whose capability
information indicates that they
do not support power saving.
According to 3GPP
specifications, the length of a
long DRX cycle must be an
integer multiple of that of a
short DRX cycle. In addition,
the actual value of
LongDrxCycleSpecial
assigned to a UE may be less
than the configured value
because of the impact of the
MO Parameter MML Feature Feature Description
ID Command ID Name
SRS bandwidth and TA period
specified by the
TimeAlignmentTimer
parameter. Therefore, the
actual value of
ShortDrxCycleSpecial
assigned to a UE may be less
than the configured value.
Unit: subframe
Unit: None
Default Value: 1
Drx OnDurationT MOD DRX LBFD- DRX Meaning: Indicates the length
imerSpecial 002017 of the On Duration Timer that
LST DRX / applies only to non-power-
TDLBF saving UEs whose RFSP
D- indexes are contained in the
002017 RFSP index set or to UEs
whose capability information
indicates that they do not
support power saving. For
details about this timer, see
3GPP TS 36.321. Because of
the impact of CQI reporting
intervals and SRS transmission
intervals, the actual value of
this parameter assigned to a
UE may be greater than the
configured value.
Unit: subframe
Unit: subframe
Unit: None
Default Value:
FALSE(FALSE)
CellAlgo DynDrxSwitc MOD LBFD- DRX, Meaning: Indicates whether to
Switch h CELLALG 002017/ LOFD- enable dynamic discontinuous
OSWITCH TDLBF 0011050 reception (DRX) or smart
D- 1/TDLO DRX. Unlink dynamic DRX
LST 002017 FD- and smart DRX apply only to
CELLALG 0011050 LTE TDD cells and requires
OSWITCH 1:Dynam the mobility speed of UEs to
ic DRX, be reported. DynDrxSwitch: If
TDLBFD this switch is on, dynamic
- DRX applies to newly
070112:S admitted UEs to reduce
mart signaling overheads or
DRX decrease UE power
consumption. If this switch is
off, dynamic DRX does not
apply to newly admitted UEs.
Dynamic DRX applies to
carrier aggregation (CA) UEs
only when this switch is on in
both the primary serving cell
(PCell) and secondary serving
cell (SCell). SmartDrxSwitch:
If this switch is on, smart DRX
applies to newly admitted UEs
that support mobility speed
MO Parameter MML Feature Feature Description
ID Command ID Name
reporting. The eNodeB
dynamically sets DRX-related
parameters based on UE
mobility speeds. If this switch
is off, smart DRX does not
apply to newly admitted UEs.
Smart DRX applies to CA UEs
only when this switch is on in
both the PCell and SCell. If
DynDrxSwitch is on, setting
the DrxAlgSwitch parameter
to ON cannot ensure that DRX
is enabled on synchronized
UEs.
Unit: None
Default Value:
DynDrxSwitch:Off,
SmartDrxSwitch:Off
CellDrxP LongDrxCycl MOD LOFD- Dynamic Meaning: Indicates the length
ara eUnsync CELLDRX 001105 DRX of the long DRX cycle for a
PARA UE in the uplink out-of-
TDLBF DRX synchronization state. Set this
LST D- parameter to a value greater
CELLDRX 002017 than the value of
PARA LongDrxCycle; otherwise, the
power saving gain of the DRX
for UEs in the uplink out-of-
synchronization state
decreases.
Unit: subframe
Unit: subframe
Unit: subframe
Unit: s
Unit: s
Default Value: 20
TimeAlig TimeAlignme MOD None None Meaning: Indicates the length
nmentTi ntTimer TATIMER of the uplink time alignment
mer timer for UEs in the cell. A UE
LST is considered not time-aligned
TATIMER in the uplink if the timer
expires.
Unit: None
Default Value:
INFINITY(Infinity)
RrcConn UeInactiveTi MOD LBFD- RRC Meaning: Indicates the length
StateTim mer RRCCONN 002007 Connecti of the UE inactivity timer for
er STATETIM / on UEs that are running non-
ER TDLBF Manage QCI1 services. If the eNodeB
D- ment detects that a UE has neither
MO Parameter MML Feature Feature Description
ID Command ID Name
LST 002007 received nor sent data for a
RRCCONN duration exceeding the value
STATETIM of this parameter, the eNodeB
ER releases the RRC connection
for the UE. If this parameter is
set to 0, the UE inactivity
timer is not used. If the
parameter setting is changed,
the change applies to UEs that
newly access the network.
Unit: s
Default Value: 20
RrcConn UlSynTimer MOD LBFD- RRC Meaning: Indicates the timer
StateTim RRCCONN 002007 Connecti used to govern the period in
er STATETIM / on which the eNodeB maintains
ER TDLBF Manage uplink synchronization for a
D- ment UE. After this timer expires,
LST 002007 the eNodeB does not send
RRCCONN Timing Advance Command to
STATETIM the UE. This parameter does
ER not take effect if it is set to 0.
That is, the eNodeB will
constantly send Timing
Advance Command to the UE
to maintain uplink
synchronization for the UE.
Unit: s
Unit: None
Default Value:
DISABLE(Disable)
CellUlsc SriFalseDetT MOD LBFD- Physical Meaning: Indicates whether to
hAlgo hdSwitch CELLULS 002003 Channel increase the scheduling request
CHALGO / Manage indicator (SRI) false detection
TDLBF ment threshold for UEs in the
LST D- discontinuous reception
CELLULS 002003 (DRX) state. If this parameter
CHALGO is set to ON, the threshold
increases and the SRI false
detection probability
decreases. If this parameter is
set to OFF, both the threshold
and the probability remain
unchanged.
Unit: None
UlVmimoSwitch: Indicates
whether to enable multi-user
MIMO (MU-MIMO) in the
UL. If this switch is on, the
eNodeB performs MU-MIMO
pairing among UEs based on
related principles. UEs
forming a pair transmit data
using the same time-frequency
resources, which improves
system throughput and spectral
efficiency.
TtiBundlingSwitch: Indicates
whether to enable transmission
time interval (TTI) bundling.
If TTI bundling is enabled,
more transmission
opportunities are available to
UEs within the delay budget
for VoIP services on the Uu
interface, thereby improving
uplink coverage.
SmartPreAllocationSwitch:
Indicates whether to enable
uplink smart preallocation
when preallocation is enabled
(by turning on
PreAllocationSwitch). If both
PreAllocationSwitch and
SmartPreAllocationSwitch are
on and
SmartPreAllocationDuration is
set to a value greater than 0,
uplink smart preallocation is
enabled; otherwise, uplink
smart preallocation is disabled.
PuschDtxSwitch: Indicates
whether the eNodeB uses the
physical uplink shared channel
(PUSCH) discontinuous
transmission (DTX) detection
result during UL scheduling.
In an LTE FDD cell, if this
switch is on, based on the
PUSCH DTX detection result,
the eNodeB determines
whether to perform adaptive
retransmission during UL
scheduling and also adjusts the
control channel element (CCE)
aggregation level of the
physical downlink control
channel (PDCCH) carrying
downlink control information
(DCI) format 0. If an FDD cell
MO Parameter MML Feature Feature Description
ID Command ID Name
is established on an LBBPc,
this switch takes effect only
when the cell uses less than
four RX antennas and normal
cyclic prefix (CP) in the uplink
and the SrsCfgInd parameter
in the SRSCfg MO is set to
BOOLEAN_TRUE. Note that
the LBBPc does not support
PUSCH DTX detection for
UEs with MU-MIMO applied.
In an LTE TDD cell, this
switch takes effect only when
the cell is configured with
subframe configuration 2 or 5.
After this switch takes effect,
the eNodeB adjusts the CCE
aggregation level based on the
PUSCH DTX detection
results. Note that LTE TDD
cells established on LBBPc
boards do not support PUSCH
DTX detection.
UlIblerAdjustSwitch: Indicates
whether to enable the uplink
initial block error rate
(IBLER) adjustment
algorithm. If this switch is on,
IBLER convergence target is
adjusted to increase the cell
edge throughput. When this
switch is on, the recommended
configuration of parameter
DopMeasLevel in MO
CellUlschAlgo is CLASS_1.
UlEnhancedFssSwitch:
Indicates whether to enable
uplink load-based enhanced
frequency selection. This
switch applies only to FDD
cells.
UlIicsAlgoSwitch: Indicates
whether to enable the UL IICS
algorithm. If this switch is on,
MO Parameter MML Feature Feature Description
ID Command ID Name
interference can be reduced
based on accurate detection of
user attributes and resource
scheduling coordination,
thereby increasing the cell
edge throughput. This switch
applies only to LTE TDD
networks.
UlEnhancedSrSchSwitch:
Indicates whether uplink re-
scheduling is performed only
when the On Duration timer
for the DRX long cycle starts.
Uplink re-scheduling is
required if the number of
HARQ retransmissions for a
scheduling request (SR)
reaches the maximum value
but the scheduling still fails. If
this switch is on, uplink re-
scheduling is performed only
when the On Duration timer
for the DRX long cycle starts.
If this switch is off, uplink re-
scheduling is performed
immediately when the number
of HARQ retransmissions for
SR reaches the maximum
value but the scheduling still
fails. It is recommended that
the switch be turned on in live
networks.
SchedulerCtrlPowerSwitch:
Indicates whether the uplink
scheduler performs scheduling
without considering power
control restrictions. If this
switch is on, the uplink
scheduler performs scheduling
without considering power
control restrictions, which
ensures full utilization of the
transmit power for all UEs. If
this switch is off, the uplink
scheduler considers power
MO Parameter MML Feature Feature Description
ID Command ID Name
control restrictions while
performing scheduling, which
prevents full utilization of the
transmit power for UEs at far
or medium distances from the
cell center.
UlMinGbrSwitch: Indicates
whether to enable uplink
minimum guaranteed bit rate
(GBR). If this switch is on, the
minimum GBR of non-GBR
services is ensured by
increasing the scheduling
priority of UEs whose non-
GBR service rates are lower
than the minimum GBR of
GBR services.
UlMbrCtrlSwitch: Indicates
whether to enable uplink
scheduling based on the
maximum bit rate (MBR) and
guaranteed bit rate (GBR) on
the GBR bearer. If this switch
is on, the eNodeB performs
uplink scheduling on GBR
bearers based on the MBR and
GBR. If this switch is off, the
eNodeB performs uplink
scheduling on GBR bearers
based only on the GBR.
MbrUlSchSwitch: Indicates
whether the eNodeB performs
uplink scheduling based on
MBR. If this switch is on, the
eNodeB prioritizes UEs based
on the MBRs during uplink
scheduling. This parameter
applies only to LTE TDD
cells.
UeAmbrUlSchSwitch:
Indicates whether the eNodeB
performs uplink scheduling
based on the aggregate
MO Parameter MML Feature Feature Description
ID Command ID Name
maximum bit rate (AMBR) of
UEs. If this switch is on, the
eNodeB prioritizes UEs based
on the AMBRs during uplink
scheduling. This parameter
applies only to LTE TDD
cells.
UlEnhancedDopplerSwitch:
Indicates whether to enable
enhanced uplink scheduling
based on mobility speed. If
this switch is on, enhanced
uplink scheduling based on
mobility speed is enabled. If
this switch is on, the eNodeB
determines whether a UE is a
low-mobility UE based on the
Doppler measurement in the
physical layer, and then
improves uplink frequency
selective scheduling
performance for low-mobility
UEs. If this switch is off,
enhanced uplink scheduling
based on mobility speed is
disabled. This switch takes
effect only when the
UlEnhancedDopplerSwitch
parameter is set to CLASS_1.
This switch does not take
effect on cells established on
an LBBPc.
UlRaUserSchOptSw: Indicates
whether the eNodeB raises the
scheduling priority of UEs
sending uplink access
signaling, including MSG5
and the RRC Connection
Reconfiguration Complete
message. If this switch is on,
the eNodeB raises the
scheduling priority of UEs
sending uplink access
signaling. If this switch is off,
the eNodeB does not raise the
MO Parameter MML Feature Feature Description
ID Command ID Name
scheduling priority of UEs
sending uplink access
signaling.
UlLast2RetransSchOptSwitch:
Indicates whether to enable
optimization on the scheduling
policy for the last two
retransmissions. If this switch
is on, optimization on the
scheduling policy for the last
two retransmissions is enabled.
If the UE transmit power is not
limited, adaptive
retransmission is used and the
number of RBs increases in
the last two retransmissions to
increase the receive success
rate of the last two
retransmissions and decrease
uplink RBLER. If this switch
is off, optimization on the
scheduling policy for the last
two retransmissions is
disabled. This switch does not
apply to LTE TDD cells.
UlInterfFssSwitch: Indicates
whether to enable interference-
based uplink frequency-
selective scheduling. This
switch applies only to LTE
FDD networks.
UlSmallRBSpectralEffOptSw:
Indicates whether to enable
spectral efficiency
optimization on uplink small
RBs. If this switch is on, the
optimization is enabled,
thereby ensuring that the
transmission block size
calculated based on optimized
spectral efficiency is not less
than the traffic volume needs
to be scheduled. If this switch
is off, the optimization is
MO Parameter MML Feature Feature Description
ID Command ID Name
disabled.
PuschUsePucchRbSwitch:
Indicates whether PUCCH
RBs can be occupied by the
PUSCH. In scenarios with a
single user, if this switch is on,
PUCCH RBs can be occupied
by the PUSCH. If this switch
is off, PUCCH RBs cannot be
occupied by the PUSCH. In
scenarios with multiple users,
PUCCH RBs cannot be
occupied by the PUSCH no
matter whether this switch is
on or off.
PuschDtxSchOptSwitch: If
this switch is on, the eNodeB
determines whether to perform
adaptive retransmission during
UL scheduling based on the
PUSCH DTX detection result.
This switch takes effect only
when subframe configuration
2 or 5 is used. If a TDD cell is
established on an LBBPc,
PUSCH DTX detection is not
supported. This switch applies
only to LTE TDD cells.
PrachRbReuseSwitch:If this
switch is on, the PUSCH and
PRACH transmissions can use
the same resource.
ULFSSAlgoswitch:If this
switch is off, uplink
frequency-selective scheduling
is disabled. If this switch is on,
MO Parameter MML Feature Feature Description
ID Command ID Name
uplink frequency-selective
scheduling is enabled. This
switch is invalid if the
HighSpeedFlag parameter in
the Cell MO is set to
HIGH_SPEED(High speed
cell flag) or
ULTRA_HIGH_SPEED(Ultra
high speed cell flag), that is,
uplink frequency-selective
scheduling is disabled in high
speed and ultra high speed
mobility conditions. This
switch applies only to LTE
TDD cells.
SrSchDataAdptSw: Indicates
whether to enable data volume
adaption in SR scheduling.
Data volume adaption in SR
scheduling is enabled only
when this option is selected.
UlFssUserThdStSwitch:
UlFssUserThdStSwitch:
Indicates whether to enable the
optimization policy on the UE
number threshold for
frequency selective
scheduling. The optimization
policy is enabled only when
this option is selected.
Unit: None
Default Value:
SpsSchSwitch:Off,
SinrAdjustSwitch:On,
PreAllocationSwitch:On,
UlVmimoSwitch:Off,
TtiBundlingSwitch:Off,
ImIcSwitch:Off,
SmartPreAllocationSwitch:Off
, PuschDtxSwitch:On,
UlIblerAdjustSwitch:Off,
UlEnhancedFssSwitch:On,
UlEnhancedSrSchSwitch:Off,
SchedulerCtrlPowerSwitch:Of
f, UlIicsAlgoSwitch:Off,
UlMinGbrSwitch:Off,
UlMbrCtrlSwitch:Off,
MbrUlSchSwitch:Off,
UeAmbrUlSchSwitch:Off,
MO Parameter MML Feature Feature Description
ID Command ID Name
UlEnhancedDopplerSwitch:Of
f, UlRaUserSchOptSw:Off,
UlLast2RetransSchOptSwitch:
Off, UlInterfFssSwitch:Off,
UlSmallRBSpectralEffOptSw:
Off,
PuschUsePucchRbSwitch:Off,
PuschDtxSchOptSwitch:Off,
ULFSSAlgoSwitch:On,
PrachRbReuseSwitch:Off,
SrSchDataAdptSw:On,
UlFssUserThdStSwitch:Off
CellDrxP CqiMask MOD LBFD- DRX Meaning: Indicates whether
ara CELLDRX 002017 the cqi-Mask IE can be set.
PARA / The cqi-Mask IE is an optional
TDLBF IE introduced in 3GPP Release
LST D- 9. If the cqi-Mask IE is set to
CELLDRX 002017 Setup, the UE can send
PARA CQI/PMI/RI/PTI reports on
PUCCH only in the
onDuration period of
discontinuous reception
(DRX). If the cqi-Mask IE is
not set, the UE can send
CQI/PMI/RI/PTI reports on
PUCCH in the active period of
DRX.
Unit: None
Unit: None
Unit: None
Default Value:
INVALID(Invalid Timing
Measurement Mode)
RlcPdcpP DiscardTimer ADD LBFD- Radio Meaning: Indicates the length
araGroup RLCPDCPP 002008 Bearer of the PDCP discard timer.
ARAGROU / Manage
P TDLBF ment GUI Value Range:
D- DiscardTimer_50(50),
MOD 002008 DiscardTimer_100(100),
RLCPDCPP DiscardTimer_150(150),
ARAGROU DiscardTimer_300(300),
P DiscardTimer_500(500),
DiscardTimer_750(750),
LST DiscardTimer_1500(1500),
RLCPDCPP DiscardTimer_Infinity(infinity
ARAGROU )
P
Unit: ms
Default Value:
DiscardTimer_Infinity(infinity
)
CellDrxP LocalCellId LST None None Meaning: Indicates the local
ara CELLDRX ID of the cell. It uniquely
PARA identifies a cell within a BS.
Unit: None
Default Value:
DEFAULT(Default)
CellDrxP DrxStartOffs MOD LBFD- DRX Meaning: Indicates whether to
ara etOptSwitch CELLDRX 002017 enable optimized random
PARA distribution of DrxStartOffset
values for UEs that are
LST configured with only sounding
CELLDRX reference signal (SRS)
PARA resources, or periodic channel
MO Parameter MML Feature Feature Description
ID Command ID Name
quality indicator (CQI), or
neither. If this parameter is set
to OFF, then DrxStartOffset
takes the value of SrsOffset,
CqiOffset, or 0 when a UE is
configured with only SRS
resources, or periodic CQI, or
neither, respectively. This
prevents DrxStartOffset values
from being randomly
distributed within the range of
0 to (LongDrxCycle - 1). If
this parameter is set to ON,
DrxStartOffset values can be
randomly distributed within
the range of 0 to
(LongDrxCycle - 1) for UEs
that are configured with only
SRS resources, or periodic
CQI, or neither. This
parameter applies only to LTE
FDD eNodeBs and is
recommended to be set to ON
when SRS resources are not
allocated for UEs or there is a
large number of UEs in the
cell.
Unit: None
RMV
DRXPARA
GROUP
CellStand LocalCellId LST None None Meaning: Indicates the local
ardQci CELLSTA ID of the cell. It uniquely
NDARDQC identifies a cell within a BS.
I
GUI Value Range: 0~255
MOD
CELLSTA Unit: None
NDARDQC
I Actual Value Range: 0~255
Unit: None
Unit: None
Default Value: 9
CellExte ExtendedQci ADD LBFD- Extended Meaning: Indicates the
ndedQci CELLEXT 002032 -QCI extended QoS Class Identifier
ENDEDQC (QCI), which is required by
I the operator for service
differentiation.
LST
CELLEXT GUI Value Range: 10~254
ENDEDQC
I Unit: None
RMV
CELLEXT
ENDEDQC
MO Parameter MML Feature Feature Description
ID Command ID Name
I
CellExte LocalCellId ADD None None Meaning: Indicates the local
ndedQci CELLEXT ID of the cell. It uniquely
ENDEDQC identifies a cell within a BS.
I
GUI Value Range: 0~255
LST
CELLEXT Unit: None
ENDEDQC
I Actual Value Range: 0~255
RMV
CELLEXT
ENDEDQC
I
CellExte DrxParaGrou ADD LBFD- DRX Meaning: Indicates the ID of a
ndedQci pId CELLEXT 002017 DRX parameter group.
ENDEDQC /
I TDLBF GUI Value Range: 0~9
D-
MOD 002017 Unit: None
CELLEXT
ENDEDQC Actual Value Range: 0~9
I
Default Value: 0
LST
CELLEXT
ENDEDQC
I
Cell LocalCellId ACT CELL None None Meaning: Indicates the local
ID of the cell. It uniquely
ADD CELL identifies a cell within a BS.
DSP CELL
DSP
CELLPHY
TOPO
DSP
CELLULC
OMPCLUS
TER
DSP
LIOPTRUL
E
DSP
PRIBBPAD
JUST
LST CELL
LST
CELLBAN
D
MOD
CELL
RMV CELL
RMV
CELLBAN
D
RMV
CELLNRT
STR
CELLRFL
OOPBACK
STR
CELLSELF
TEST
MO Parameter MML Feature Feature Description
ID Command ID Name
STR
LRTWPRT
TST
STR
PRIBBPAD
JUST
UBL CELL
DSP
LRTWPRT
TST
DSP
PRIBBPRE
SINFO
Standard Qci LST LOFD- Dynamic Meaning: Indicates the QoS
Qci STANDAR 001015 Scheduli Class Identifier (QCI) of an
DQCI 02 / ng EPS bearer. Different QCIs
TDLOF represent different QoS
MOD D- Basic specifications such as the
STANDAR 001015 Scheduli packet delay budget, packet
DQCI 02 ng error loss rate, and resource
type (whether the service is a
TDLBF Enhanced GBR service or not). For
D- Scheduli details, see Table 6.1.7 in
002025 ng 3GPP TS 23.203.
Unit: None
Unit: None
12 Counters
Table 12-1 Counters
Counter Counter Name Counter Feature Feature
ID Description ID Name
15267266 L.RRC.ConnReq.Att Number of RRC Multi- RRC
58 connection setup mode: Connectio
requests None n
(retransmission Managem
excluded) GSM: ent
None
RRC
UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
15267268 L.Paging.UU.Att Number of UEs Multi- Paging
85 contained in mode:
paging messages Paging
Counter Counter Name Counter Feature Feature
ID Description ID Name
transmitted over None
the Uu interface
in a cell GSM:
None
UMTS:
None
LTE:
LBFD-
002011
TDLBF
D-
002011
15267269 L.HHO.IntraeNB.IntraFreq.ExecAttOut Number of intra- Multi- Coverage
96 eNodeB intra- mode: Based
frequency None Intra-
outgoing frequency
handovers GSM: Handover
executions in a None
cell Coverage
UMTS: Based
None Intra-
frequency
LTE: Handover
LBFD-
002018
01
TDLBF
D-
002018
01
15267269 L.HHO.IntraeNB.InterFreq.ExecAttOut Number of intra- Multi- Coverage
99 eNodeB inter- mode: Based
frequency None Inter-
outgoing frequency
handovers GSM: Handover
executions in a None
cell Coverage
UMTS: Based
None Inter-
frequency
LTE: Handover
LBFD-
Counter Counter Name Counter Feature Feature
ID Description ID Name
002018
02
TDLBF
D-
002018
02
15267270 L.HHO.IntereNB.IntraFreq.ExecAttOut Number of inter- Multi- Coverage
02 eNodeB intra- mode: Based
frequency None Intra-
outgoing frequency
handovers GSM: Handover
executions in a None
cell Coverage
UMTS: Based
None Intra-
frequency
LTE: Handover
LBFD-
002018
01
TDLBF
D-
002018
01
15267270 L.HHO.IntereNB.InterFreq.ExecAttOut Number of inter- Multi- Coverage
05 eNodeB inter- mode: Based
frequency None Inter-
outgoing frequency
handovers GSM: Handover
executions in a None
cell Coverage
UMTS: Based
None Inter-
frequency
LTE: Handover
LBFD-
002018
02
TDLBF
D-
002018
02
Counter Counter Name Counter Feature Feature
ID Description ID Name
15267272 L.HHO.DRX.IntraeNB.IntraFreq.ExecA Number of intra- Multi- DRX
85 ttOut eNodeB intra- mode:
frequency None Coverage
outgoing Based
handovers GSM: Intra-
executions in the None frequency
DRX state Handover
UMTS:
None DRX
LTE: Coverage
LBFD- Based
002017 Intra-
frequency
LBFD- Handover
002018
01
TDLBF
D-
002017
TDLBF
D-
002018
01
15267272 L.HHO.DRX.IntraeNB.IntraFreq.ExecS Number of Multi- DRX
86 uccOut successful intra- mode:
eNodeB intra- None Coverage
frequency Based
outgoing GSM: Intra-
handovers in the None frequency
DRX state Handover
UMTS:
None DRX
LTE: Coverage
LBFD- Based
002017 Intra-
frequency
LBFD- Handover
002018
01
TDLBF
D-
Counter Counter Name Counter Feature Feature
ID Description ID Name
002017
TDLBF
D-
002018
01
15267272 L.HHO.DRX.IntraeNB.InterFreq.ExecA Number of intra- Multi- DRX
87 ttOut eNodeB inter- mode:
frequency None Coverage
outgoing Based
handovers GSM: Inter-
executions in the None frequency
DRX state Handover
UMTS:
None DRX
LTE: Coverage
LBFD- Based
002017 Inter-
frequency
LBFD- Handover
002018
02
TDLBF
D-
002017
TDLBF
D-
002018
02
15267272 L.HHO.DRX.IntraeNB.InterFreq.ExecS Number of Multi- DRX
88 uccOut successful intra- mode:
eNodeB inter- None Coverage
frequency Based
outgoing GSM: Inter-
handovers in the None frequency
DRX state Handover
UMTS:
None DRX
LTE: Coverage
LBFD- Based
002017 Inter-
frequency
Counter Counter Name Counter Feature Feature
ID Description ID Name
LBFD- Handover
002018
02
TDLBF
D-
002017
TDLBF
D-
002018
02
15267272 L.HHO.DRX.IntereNB.IntraFreq.ExecA Number of inter- Multi- DRX
89 ttOut eNodeB intra- mode:
frequency None Coverage
outgoing Based
handovers GSM: Inter-
executions in the None frequency
DRX state Handover
UMTS:
None Coverage
Based
LTE: Inter-
LBFD- frequency
002017 Handover
LBFD-
002018
02
TDLBF
D-
002018
02
15267272 L.HHO.DRX.IntereNB.IntraFreq.ExecS Number of Multi- Coverage
90 uccOut successful inter- mode: Based
eNodeB intra- None Intra-
frequency frequency
outgoing GSM: Handover
handovers in the None
DRX state Coverage
UMTS: Based
None Inter-
frequency
LTE: Handover
LBFD-
Counter Counter Name Counter Feature Feature
ID Description ID Name
002018 DRX
01
Coverage
LBFD- Based
002018 Intra-
02 frequency
Handover
LBFD-
002017 Coverage
Based
TDLBF Inter-
D- frequency
002018 Handover
01
TDLBF
D-
002018
02
15267272 L.HHO.DRX.IntereNB.InterFreq.ExecA Number of inter- Multi- Coverage
91 ttOut eNodeB inter- mode: Based
frequency None Intra-
outgoing frequency
handovers GSM: Handover
executions in the None
DRX state Coverage
UMTS: Based
None Inter-
frequency
LTE: Handover
LBFD-
002018 DRX
01
Coverage
LBFD- Based
002018 Intra-
02 frequency
Handover
LBFD-
002017 Coverage
Based
TDLBF Inter-
D- frequency
002018 Handover
01
Counter Counter Name Counter Feature Feature
ID Description ID Name
TDLBF
D-
002018
02
15267272 L.HHO.DRX.IntereNB.InterFreq.ExecS Number of Multi- DRX
92 uccOut successful inter- mode:
eNodeB inter- None Coverage
frequency Based
outgoing GSM: Inter-
handovers in the None frequency
DRX state Handover
UMTS:
None DRX
LTE: Coverage
LBFD- Based
002017 Intra-
frequency
LBFD- Handover
002018
02 Coverage
Based
TDLBF Inter-
D- frequency
002017 Handover
TDLBF
D-
002018
01
TDLBF
D-
002018
02
15267275 L.E-RAB.SuccEst Total number of Multi- Radio
44 successful E- mode: Bearer
RAB setups None Managem
initiated by UEs ent
in a cell GSM:
None Radio
Bearer
UMTS: Managem
None ent
LTE:
Counter Counter Name Counter Feature Feature
ID Description ID Name
LBFD-
002008
TDLBF
D-
002008
15267275 L.E-RAB.AttEst Total number of Multi- Radio
45 E-RAB setup mode: Bearer
attempts initiated None Managem
by UEs in a cell ent
GSM:
None Radio
Bearer
UMTS: Managem
None ent
LTE:
LBFD-
002008
TDLBF
D-
002008
15267275 L.E-RAB.AbnormRel Total number of Multi- Radio
46 abnormal mode: Bearer
releases of None Managem
activated E- ent
RABs initiated GSM:
by the eNodeB None Radio
Bearer
UMTS: Managem
None ent
LTE:
LBFD-
002008
TDLBF
D-
002008
15267275 L.E-RAB.NormRel Total number of Multi- Radio
47 normal E-RAB mode: Bearer
releases initiated None Managem
by the eNodeB ent
in a cell GSM:
Counter Counter Name Counter Feature Feature
ID Description ID Name
None Radio
Bearer
UMTS: Managem
None ent
LTE:
LBFD-
002008
TDLBF
D-
002008
15267282 L.RRC.ConnReq.Att.Emc Number of RRC Multi- RRC
17 connection setup mode: Connectio
attempts with a None n
cause value of Managem
emergency GSM: ent
None
RRC
UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
15267282 L.RRC.ConnReq.Att.HighPri Number of RRC Multi- RRC
18 connection setup mode: Connectio
attempts with a None n
cause value of Managem
highPriorityAcce GSM: ent
ss None
RRC
UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
Counter Counter Name Counter Feature Feature
ID Description ID Name
15267282 L.RRC.ConnReq.Att.Mt Number of RRC Multi- RRC
19 connection setup mode: Connectio
attempts with a None n
cause value of Managem
mt-Access GSM: ent
None
RRC
UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
15267282 L.RRC.ConnReq.Att.MoSig Number of RRC Multi- RRC
20 connection setup mode: Connectio
attempts with a None n
cause value of Managem
mo-Signalling GSM: ent
None
RRC
UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
15267282 L.RRC.ConnReq.Att.MoData Number of RRC Multi- RRC
21 connection setup mode: Connectio
attempts with a None n
cause value of Managem
mo-Data GSM: ent
None
RRC
UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
Counter Counter Name Counter Feature Feature
ID Description ID Name
002007
TDLBF
D-
002007
15267282 L.RRC.ConnReq.Succ.Emc Number of RRC Multi- RRC
22 Connection mode: Connectio
Setup Complete None n
messages with a Managem
cause value of GSM: ent
emergency None
received from RRC
UEs in a cell UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
15267282 L.RRC.ConnReq.Succ.HighPri Number of RRC Multi- RRC
23 Connection mode: Connectio
Setup Complete None n
messages with a Managem
cause value of GSM: ent
highPriorityAcce None
ss received from RRC
UEs in a cell UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
15267282 L.RRC.ConnReq.Succ.Mt Number of RRC Multi- RRC
24 Connection mode: Connectio
Setup Complete None n
messages with a Managem
cause value of GSM: ent
mt-Access
Counter Counter Name Counter Feature Feature
ID Description ID Name
received from None RRC
UEs in a cell Connectio
UMTS: n
None Managem
ent
LTE:
LBFD-
002007
TDLBF
D-
002007
15267282 L.RRC.ConnReq.Succ.MoData Number of RRC Multi- RRC
26 Connection mode: Connectio
Setup Complete None n
messages with a Managem
cause value of GSM: ent
mo-Data None
received from RRC
UEs in a cell UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
15267283 L.RRC.ConnReq.Att.DelayTol Number of RRC Multi- RRC
57 connection setup mode: Connectio
attempts with a None n
cause value of Managem
delayTolerantAc GSM: ent
cess-v1020 None
RRC
UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
Counter Counter Name Counter Feature Feature
ID Description ID Name
15267283 L.RRC.ConnReq.Succ.DelayTol Number of Multi- RRC
58 successful RRC mode: Connectio
connection None n
setups with a Managem
cause value of GSM: ent
delayTolerantAc None
cess-v1020 RRC
UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
15267284 L.E-RAB.Release.Unsyn Number of Multi- Radio
36 released E-RABs mode: Bearer
of UEs in the None Managem
uplink out-of- ent
synchronization GSM:
state None Radio
Bearer
UMTS: Managem
None ent
LTE:
LBFD-
002008
TDLBF
D-
002008
15267284 L.E-RAB.Num.Syn2Unsyn Total number of Multi- Radio
37 E-RABs in UE mode: Bearer
contexts when None Managem
the UEs switch ent
from the uplink GSM:
synchronized None Radio
state to the Bearer
uplink out-of- UMTS: Managem
synchronization None ent
state in a cell
LTE:
LBFD-
Counter Counter Name Counter Feature Feature
ID Description ID Name
002008
TDLBF
D-
002008
15267284 L.RRC.StateTrans.Syn2Unsyn Number of times Multi- RRC
38 a UE switch mode: Connectio
from the Uplink- None n
Synchronized Managem
state to the GSM: ent
uplink out-of- None
synchronization RRC
state UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
15267284 L.RRC.StateTrans.Unsyn2Syn Number of times Multi- RRC
39 a UE switch mode: Connectio
from the out-of- None n
synchronization Managem
state to the GSM: ent
uplink- None
synchronized RRC
state UMTS: Connectio
None n
Managem
LTE: ent
LBFD-
002007
TDLBF
D-
002007
15267284 L.UECNTX.Release.HighSpeed Number of UE Multi- Radio
40 context releases mode: Bearer
due to high None Managem
mobility of UEs ent
GSM:
Radio
Counter Counter Name Counter Feature Feature
ID Description ID Name
None Bearer
Managem
UMTS: ent
None
LTE:
LBFD-
002008
TDLBF
D-
002008
15267284 L.Signal.Num.Uu Number of Multi- DRX
65 signaling mode:
messages over None DRX
the Uu interface
GSM:
None
UMTS:
None
LTE:
LBFD-
002017
TDLBF
D-
002017
15267284 L.Signal.Num.DRX.Reconfig Number of DRX Multi- DRX
66 reconfiguration mode:
messages None DRX
GSM: Dynamic
None DRX
UMTS: Dynamic
None DRX
LTE:
LBFD-
002017
TDLBF
D-
Counter Counter Name Counter Feature Feature
ID Description ID Name
002017
LOFD-
001105
TDLOF
D-
001105
15267285 L.Traffic.User.Cdrx.Avg Average number Multi- Dynamic
46 of UEs on which mode: DRX
DRX takes effect None
in a cell DRX
GSM:
None Dynamic
DRX
UMTS:
None
LTE:
LOFD-
001105
LBFD-
002017
TDLOF
D-
001105
15267285 L.Cdrx.Enter.Num Number of times Multi- DRX
47 a UE in mode:
connected mode None DRX
enters DRX in
RRC_CONECT GSM: Dynamic
ED mode None DRX
UMTS: Dynamic
None DRX
LTE:
LBFD-
002017
TDLBF
D-
002017
Counter Counter Name Counter Feature Feature
ID Description ID Name
LOFD-
001105
TDLOF
D-
001105
15267285 L.Cdrx.Exit.Num Number of times Multi- DRX
48 a UE in mode:
connected mode None DRX
exits DRX in
RRC_CONECT GSM: Dynamic
ED mode None DRX
UMTS: Dynamic
None DRX
LTE:
LBFD-
002017
TDLBF
D-
002017
LOFD-
001105
TDLOF
D-
001105
15267285 L.Cdrx.Active.TtiNum Total number of Multi- Dynamic
49 TTIs for DRX mode: DRX
UEs in active None
state Dynamic
GSM: DRX
None
DRX
UMTS:
None DRX
LTE:
LOFD-
001105
TDLOF
D-
Counter Counter Name Counter Feature Feature
ID Description ID Name
001105
LBFD-
002017
TDLBF
D-
002017
15267285 L.Cdrx.Sleep.TtiNum Total number of Multi- Dynamic
50 TTIs for DRX mode: DRX
UEs in sleep None
state Dynamic
GSM: DRX
None
DRX
UMTS:
None DRX
LTE:
LOFD-
001105
TDLOF
D-
001105
LBFD-
002017
TDLBF
D-
002017
15267285 L.Voip.Cdrx.Active.TtiNum Total number of Multi- Dynamic
51 TTIs for DRX mode: DRX
UEs in active None
state and Dynamic
performing VoIP GSM: DRX
services None
DRX
UMTS:
None DRX
LTE:
LOFD-
001105
Counter Counter Name Counter Feature Feature
ID Description ID Name
TDLOF
D-
001105
LBFD-
002017
TDLBF
D-
002017
15267285 L.Voip.Cdrx.Sleep.TtiNum Total number of Multi- Dynamic
52 TTIs for DRX mode: DRX
UEs in dormant None
state and Dynamic
performing VoIP GSM: DRX
services None
DRX
UMTS:
None DRX
LTE:
LOFD-
001105
TDLOF
D-
001105
LBFD-
002017
TDLBF
D-
002017
15267285 L.HHO.IntraFreq.NoData.ExecAttOut Number of intra- Multi- Coverage
54 frequency mode: Based
handover None Intra-
execution frequency
attempts GSM: Handover
triggered for UEs None
that do not Coverage
transmit or UMTS: Based
receive data None Intra-
frequency
LTE: Handover
LBFD-
Counter Counter Name Counter Feature Feature
ID Description ID Name
002018 Dynamic
01 DRX
TDLBF Dynamic
D- DRX
002018
01
LOFD-
001105
TDLOF
D-
001105
15267285 L.HHO.IntraFreq.NoData.ExecSuccOut Number of Multi- Coverage
55 successful intra- mode: Based
frequency None Intra-
handover frequency
executions GSM: Handover
triggered for UEs None
that do not Coverage
transmit or UMTS: Based
receive data None Intra-
frequency
LTE: Handover
LBFD-
002018 Dynamic
01 DRX
TDLBF Dynamic
D- DRX
002018
01
LOFD-
001105
TDLOF
D-
001105
15267285 L.HHO.InterFreq.NoData.ExecAttOut Number of inter- Multi- Coverage
57 frequency mode: Based
handover None Inter-
execution frequency
attempts GSM: Handover
triggered for UEs
Counter Counter Name Counter Feature Feature
ID Description ID Name
that do not None Coverage
transmit or Based
receive data UMTS: Inter-
None frequency
Handover
LTE:
LBFD- Dynamic
002018 DRX
02
Dynamic
TDLBF DRX
D-
002018
02
LOFD-
001105
TDLOF
D-
001105
15267285 L.HHO.InterFreq.NoData.ExecSuccOut Number of Multi- Coverage
58 successful inter- mode: Based
frequency None Inter-
handover frequency
executions GSM: Handover
triggered for UEs None
that do not Coverage
transmit or UMTS: Based
receive data None Inter-
frequency
LTE: Handover
LBFD-
002018 Dynamic
02 DRX
TDLBF Dynamic
D- DRX
002018
02
LOFD-
001105
TDLOF
D-
Counter Counter Name Counter Feature Feature
ID Description ID Name
001105
15267285 L.IRATHO.E2W.NoData.ExecAttOut Number of inter- Multi- PS Inter-
60 RAT handover mode: RAT
executions from None Mobility
E-UTRAN to between
WCDMA GSM: E-
network None UTRAN
triggered for UEs and
that do not UMTS: UTRAN
transmit or None
receive data SRVCC
LTE: to
LOFD- UTRAN
001019
CS
LOFD- Fallback
001022 to
UTRAN
LOFD-
001033 PS Inter-
RAT
TDLOF Mobility
D- between
001019 E-
UTRAN
TDLOF and
D- UTRAN
001022
SRVCC
TDLOF to
D- UTRAN
001033
CS
LOFD- Fallback
001105 to
UTRAN
TDLOF
D- Dynamic
001105 DRX
Dynamic
DRX
15267285 L.IRATHO.E2W.NoData.ExecSuccOut Number of Multi- PS Inter-
61 successful inter- mode: RAT
RAT handovers None Mobility
from E-UTRAN between
Counter Counter Name Counter Feature Feature
ID Description ID Name
to WCDMA GSM: E-
network None UTRAN
triggered for UEs and
that do not UMTS: UTRAN
transmit or None
receive data SRVCC
LTE: to
LOFD- UTRAN
001019
CS
LOFD- Fallback
001022 to
UTRAN
LOFD-
001033 PS Inter-
RAT
TDLOF Mobility
D- between
001019 E-
UTRAN
TDLOF and
D- UTRAN
001022
SRVCC
TDLOF to
D- UTRAN
001033
CS
LOFD- Fallback
001105 to
UTRAN
TDLOF
D- Dynamic
001105 DRX
Dynamic
DRX
15267295 L.HHO.InterFddTdd.NoData.ExecAttO Number of inter- Multi- Coverage
84 ut duplex-mode mode: Based
handover None Inter-
execution frequency
attempts GSM: Handover
triggered for UEs None
that do not Dynamic
transmit or UMTS: DRX
receive data
Counter Counter Name Counter Feature Feature
ID Description ID Name
None Coverage
Based
LTE: Inter-
LBFD- frequency
002018 Handover
02
Dynamic
LOFD- DRX
001105
TDLBF
D-
002018
02
TDLOF
D-
001105
15267295 L.HHO.InterFddTdd.NoData.ExecSucc Number of Multi- Coverage
85 Out successful inter- mode: Based
duplex-mode None Inter-
handover frequency
executions GSM: Handover
triggered for UEs None
that do not Dynamic
transmit or UMTS: DRX
receive data None
Coverage
LTE: Based
LBFD- Inter-
002018 frequency
02 Handover
LOFD- Dynamic
001105 DRX
TDLBF
D-
002018
02
TDLOF
D-
001105
15267295 L.HHO.DRX.IntraeNB.InterFddTdd.Ex Number of intra- Multi- DRX
86 ecAttOut eNodeB inter- mode:
Counter Counter Name Counter Feature Feature
ID Description ID Name
duplex-mode None Coverage
handover Based
executions GSM: Inter-
triggered for UEs None frequency
in the DRX state Handover
UMTS:
None DRX
LTE: Coverage
LBFD- Based
002017 Inter-
frequency
LBFD- Handover
002018
02
TDLBF
D-
002017
TDLBF
D-
002018
02
15267295 L.HHO.DRX.IntraeNB.InterFddTdd.Ex Number of Multi- DRX
87 ecSuccOut successful intra- mode:
eNodeB inter- None Coverage
duplex-mode Based
outgoing GSM: Inter-
handovers None frequency
triggered for UEs Handover
in the DRX state UMTS:
None DRX
LTE: Coverage
LBFD- Based
002017 Inter-
frequency
LBFD- Handover
002018
02
TDLBF
D-
002017
Counter Counter Name Counter Feature Feature
ID Description ID Name
TDLBF
D-
002018
02
15267295 L.HHO.DRX.IntereNB.InterFddTdd.Ex Number of inter- Multi- DRX
88 ecAttOut eNodeB inter- mode:
duplex-mode None Coverage
handover Based
executions GSM: Inter-
triggered for UEs None frequency
in the DRX state Handover
UMTS:
None DRX
LTE: Coverage
LBFD- Based
002017 Inter-
frequency
LBFD- Handover
002018
02
TDLBF
D-
002017
TDLBF
D-
002018
02
15267295 L.HHO.DRX.IntereNB.InterFddTdd.Ex Number of Multi- DRX
89 ecSuccOut successful inter- mode:
eNodeB inter- None Coverage
duplex-mode Based
outgoing GSM: Inter-
handovers None frequency
triggered for UEs Handover
in the DRX state UMTS:
None DRX
LTE: Coverage
LBFD- Based
002017 Inter-
frequency
LBFD- Handover
002018
Counter Counter Name Counter Feature Feature
ID Description ID Name
02
TDLBF
D-
002017
TDLBF
D-
002018
02
15267296 L.RRC.StateTrans.Unsyn2Syn.Succ Number of Multi- Dynamic
56 successfully mode: DRX
recovered RRC None
connections Dynamic
when UEs switch GSM: DRX
from the uplink None
out-of-
synchronization UMTS:
state to the None
uplink-
synchronized LTE:
state LOFD-
001105
TDLOF
D-
001105
15267296 L.E-RAB.StateTrans.Unsyn2Syn.Att Number of E- Multi- Dynamic
57 RAB recovery mode: DRX
attempts when None
UEs switch from Dynamic
the uplink out- GSM: DRX
of- None
synchronization
state to the UMTS:
uplink- None
synchronized
state LTE:
LOFD-
001105
TDLOF
D-
001105
15267296 L.E-RAB.StateTrans.Unsyn2Syn.Succ Number of Multi- Dynamic
Counter Counter Name Counter Feature Feature
ID Description ID Name
58 successfully mode: DRX
recovered E- None
RABs when UEs Dynamic
switch from the GSM: DRX
uplink out-of- None
synchronization
state to the UMTS:
uplink- None
synchronized
state LTE:
LOFD-
001105
TDLOF
D-
001105
15267296 L.Signal.Num.S1 Number of S1 Multi- Dynamic
59 signaling mode: DRX
messages None
received or sent Dynamic
by a cell GSM: DRX
None
UMTS:
None
LTE:
LOFD-
001105
TDLOF
D-
001105
15267296 L.Signal.Num.X2 Number of X2 Multi- Dynamic
60 signaling mode: DRX
messages None
received or sent Dynamic
by a cell GSM: DRX
None
UMTS:
None
LTE:
LOFD-
Counter Counter Name Counter Feature Feature
ID Description ID Name
001105
TDLOF
D-
001105
15267301 L.User.UL.Unsync.Dur.Index0 Number of times Multi- Dynamic
04 the duration of a mode: DRX
UE in the out-of- None
synchronization Dynamic
state in a cell GSM: DRX
ranges within None
index 0
UMTS:
None
LTE:
LOFD-
001105
TDLOF
D-
001105
15267301 L.User.UL.Unsync.Dur.Index1 Number of times Multi- Dynamic
05 the duration of a mode: DRX
UE in the out-of- None
synchronization Dynamic
state in a cell GSM: DRX
ranges within None
index 1
UMTS:
None
LTE:
LOFD-
001105
TDLOF
D-
001105
15267301 L.User.UL.Unsync.Dur.Index2 Number of times Multi- Dynamic
06 the duration of a mode: DRX
UE in the out-of- None
synchronization Dynamic
state in a cell GSM: DRX
ranges within
Counter Counter Name Counter Feature Feature
ID Description ID Name
index 2 None
UMTS:
None
LTE:
LOFD-
001105
TDLOF
D-
001105
15267301 L.User.UL.Unsync.Dur.Index3 Number of times Multi- Dynamic
07 the duration of a mode: DRX
UE in the out-of- None
synchronization Dynamic
state in a cell GSM: DRX
ranges within None
index 3
UMTS:
None
LTE:
LOFD-
001105
TDLOF
D-
001105
15267301 L.User.UL.Unsync.Dur.Index4 Number of times Multi- Dynamic
08 the duration of a mode: DRX
UE in the out-of- None
synchronization Dynamic
state in a cell GSM: DRX
ranges within None
index 4
UMTS:
None
LTE:
LOFD-
001105
TDLOF
D-
001105
Counter Counter Name Counter Feature Feature
ID Description ID Name
15267301 L.User.UL.Unsync.Dur.Index5 Number of times Multi- Dynamic
09 the duration of a mode: DRX
UE in the out-of- None
synchronization Dynamic
state in a cell GSM: DRX
ranges within None
index 5
UMTS:
None
LTE:
LOFD-
001105
TDLOF
D-
001105
15267301 L.User.UL.Unsync.Dur.Index6 Number of times Multi- Dynamic
10 the duration of a mode: DRX
UE in the out-of- None
synchronization Dynamic
state in a cell GSM: DRX
ranges within None
index 6
UMTS:
None
LTE:
LOFD-
001105
TDLOF
D-
001105
15267301 L.User.UL.Unsync.Dur.Index7 Number of times Multi- Dynamic
11 the duration of a mode: DRX
UE in the out-of- None
synchronization Dynamic
state in a cell GSM: DRX
ranges within None
index 7
UMTS:
None
LTE:
LOFD-
Counter Counter Name Counter Feature Feature
ID Description ID Name
001105
TDLOF
D-
001105
15267301 L.User.UL.Unsync.Dur.Index8 Number of times Multi- Dynamic
12 the duration of a mode: DRX
UE in the out-of- None
synchronization Dynamic
state in a cell GSM: DRX
ranges within None
index 8
UMTS:
None
LTE:
LOFD-
001105
TDLOF
D-
001105
15267301 L.Traffic.PktInterval.Num.Index0 Number of times Multi- RRC
24 the packet mode: Connectio
transmission None n
interval for a UE Managem
in a cell ranges GSM: ent
within index 0 None
Dynamic
UMTS: DRX
None
Dynamic
LTE: DRX
LBFD-
002007
LOFD-
001105
TDLOF
D-
001105
15267301 L.Traffic.PktInterval.Num.Index1 Number of times Multi- RRC
25 the packet mode: Connectio
transmission n
Counter Counter Name Counter Feature Feature
ID Description ID Name
interval for a UE None Managem
in a cell ranges ent
within index 1 GSM:
None Dynamic
DRX
UMTS:
None Dynamic
DRX
LTE:
LBFD-
002007
LOFD-
001105
TDLOF
D-
001105
15267301 L.Traffic.PktInterval.Num.Index2 Number of times Multi- RRC
26 the packet mode: Connectio
transmission None n
interval for a UE Managem
in a cell ranges GSM: ent
within index 2 None
Dynamic
UMTS: DRX
None
Dynamic
LTE: DRX
LBFD-
002007
LOFD-
001105
TDLOF
D-
001105
15267301 L.Traffic.PktInterval.Num.Index3 Number of times Multi- RRC
27 the packet mode: Connectio
transmission None n
interval for a UE Managem
in a cell ranges GSM: ent
within index 3 None
Dynamic
UMTS:
Counter Counter Name Counter Feature Feature
ID Description ID Name
None DRX
LTE: Dynamic
LBFD- DRX
002007
LOFD-
001105
TDLOF
D-
001105
15267301 L.Traffic.PktInterval.Num.Index4 Number of times Multi- RRC
28 the packet mode: Connectio
transmission None n
interval for a UE Managem
in a cell ranges GSM: ent
within index 4 None
Dynamic
UMTS: DRX
None
Dynamic
LTE: DRX
LBFD-
002007
LOFD-
001105
TDLOF
D-
001105
15267301 L.Traffic.PktInterval.Num.Index5 Number of times Multi- RRC
29 the packet mode: Connectio
transmission None n
interval for a UE Managem
in a cell ranges GSM: ent
within index 5 None
Dynamic
UMTS: DRX
None
Dynamic
LTE: DRX
LBFD-
002007
Counter Counter Name Counter Feature Feature
ID Description ID Name
LOFD-
001105
TDLOF
D-
001105
15267301 L.Traffic.PktInterval.Num.Index6 Number of times Multi- RRC
30 the packet mode: Connectio
transmission None n
interval for a UE Managem
in a cell ranges GSM: ent
within index 6 None
Dynamic
UMTS: DRX
None
Dynamic
LTE: DRX
LBFD-
002007
LOFD-
001105
TDLOF
D-
001105
15267301 L.Traffic.PktInterval.Num.Index7 Number of times Multi- RRC
31 the packet mode: Connectio
transmission None n
interval for a UE Managem
in a cell ranges GSM: ent
within index 7 None
Dynamic
UMTS: DRX
None
Dynamic
LTE: DRX
LBFD-
002007
LOFD-
001105
TDLOF
D-
001105
Counter Counter Name Counter Feature Feature
ID Description ID Name
15267301 L.Traffic.PktInterval.Num.Index8 Number of times Multi- RRC
32 the packet mode: Connectio
transmission None n
interval for a UE Managem
in a cell ranges GSM: ent
within index 8 None
Dynamic
UMTS: DRX
None
Dynamic
LTE: DRX
LBFD-
002007
LOFD-
001105
TDLOF
D-
001105
13 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.
14 Reference Documents
1. 3GPP TS 36.211: "Physical channels and modulation"
2. 3GPP TS 36.300: "Overall description"
3. 3GPP TS 36.321: "Medium Access Control (MAC) protocol specification"
4. Idle Mode Management Feature Parameter Description
5. Intra-RAT Mobility Management in Connected Mode Feature Parameter Description
6. Scheduling Feature Parameter Description
7. Terminal Awareness Differentiation Feature Parameter Description