Tuesday, 30 August 2016

DRX and Signaling Control Feature

DRX and signaling control consists of the following features:
  • DRX in RRC_CONNECTED mode
    To reduce user equipment (UE) power consumption, 3GPP specifications for LTE introduced the DRX feature. Huawei eNodeBs support the C-DRX feature (TDLBFD-002017 DRX) defined in 3GPP specifications. For details about this feature, see 3 DRX in RRC_CONNECTED Mode.
    NOTE:
    DRX can be functional in RRC_CONNECTED and RRC_IDLE modes. DRX described in this document refers to DRX in RRC_CONNECTED mode. For details about DRX in RRC_IDLE mode, see Idle Mode Management Feature Parameter Description.
  • Dynamic DRX
    Many smartphone applications use a few small packets or heartbeat packets. These applications require the network to frequently reestablish radio resource control (RRC) connections, causing signaling storms. Huawei provides the feature TDLBFD-00110501 Dynamic DRX to reduce signaling storm risks and UE power consumption. For details about this feature, see 4 Dynamic DRX.
  • High-mobility-triggered idle mode
    Moving UEs often trigger handovers, which may cause signaling storms. Huawei provides the feature TDLBFD-00110502 High-Mobility-Triggered Idle Mode to reduce such signaling storm risks. For details about this feature, see 5 High-Mobility-Triggered Idle Mode.
Table 2-1 describes the application scenarios and benefits of these features.
Table 2-1 Application scenarios and benefits of DRX and signaling control features
Feature Name
UE Type
Application Scenario
Benefit
TDLBFD-002017 DRX
Mobile phones
  • Periodic services that use continuous small packets, such as voice over IP (VoIP) services
  • Delay-insensitive services that have data to transmit and receive at certain times, such as web browsing, email, and File Transfer Protocol (FTP) services
  • Services that use a few small packets, such as Presence services
  • Automatic neighbor relation (ANR) measurement
Reduces UE power consumption.
TDLOFD-00110501 Dynamic DRX
Smartphones
  • Services that use a few small packets
  • Services that use heartbeat packets, such as the Microsoft Service Network (MSN)
  • Reduces signaling storm risks by reducing the amount of signaling generated when UEs switch between the RRC_CONNECTED and RRC_IDLE modes frequently.
  • Reduces UE power consumption.
TDLOFD-00110502 High-Mobility-Triggered Idle Mode
Smartphones
  • Cells where UEs remain constantly online and frequently change locations
  • Cells enabled with dynamic DRX for network signaling control
Reduces signaling storm risks by reducing the amount of signaling generated when fast-moving UEs in RRC_CONNECTED mode remain online constantly and perform handovers frequently.
NOTE:
The Presence service is used to obtain the Presence information about some users in real time by following a certain admission principle. Then, this information is presented to other users. The Presence information can be the user state, communication capability, and personal preference. For example, the online alert function of MSN is a Presence service.

3 DRX in RRC_CONNECTED Mode

This chapter describes the implementation principles of DRX in RRC_CONNECTED mode (TDLBFD-002017 DRX).

3.1 Introduction


3.1.1 Definition

In DRX mode, the UE does not need to continuously monitor the physical downlink control channel (PDCCH). A DRX cycle consists of active time and sleep time, corresponding to the active state and sleep state, respectively.
  • In active time, the UE turns on its receiver, monitors the PDCCH, and receives DL data and signaling.
  • In sleep time, the UE turns off its receiver, and neither monitors the PDCCH nor receives DL data and signaling, reducing power consumption.
In non-DRX mode, the UE always turns on its receiver and stays in the active state.
For the concepts of DRX cycle, active time, and sleep time, see 3.2.1 Concepts Related to the DRX Cycle in RRC_CONNECTED Mode.

3.1.2 Benefits

Compared with continuous reception, DRX in RRC_CONNECTED mode has the following benefits:
  • In DRX mode, the UE does not need to continuously monitor the physical downlink control channel (PDCCH). This reduces power consumption and prolongs battery runtime.
  • As an intermediate state between the RRC_CONNECTED and RRC_IDLE modes, DRX reduces the probability of transitions from RRC_CONNECTED to RRC_IDLE. This helps reduce the signaling overhead of a network, especially a network with a large number of smartphones.
  • UEs can perform ANR measurements during the sleep time in DRX mode.
NOTE:
When a UE enters DRX mode, UE power can be saved. The power saving effect is related to the chips. The chips used by some UE manufacturers support DRX and UEs in DRX mode no longer monitors the PDCCH. However, the UEs cannot shut down their RF modules. Therefore, the power saving effect is limited.

3.1.3 Architecture

The following factors affect DRX state switching in RRC_CONNECTED mode:
  • Quality of service (QoS) parameters, such as the QoS class identifier (QCI)
  • Media Access Control (MAC) traffic
  • DRX initial configuration and scheduling
  • Handover
  • ANR
DRX state switching also affects scheduling and handovers, as shown in Figure 3-1.
Figure 3-1 Implementation architecture of DRX in RRC_CONNECTED mode

3.2 DRX Mode in RRC_CONNECTED Mode

In DRX mode, UEs no longer constantly listen to the PDCCH. When a UE is in the active state in DRX mode, its receiver is turned on to listen to the PDCCH. When a UE is in the sleep state, it no longer listens to the PDCCH and its receiver can be turned off to reduce power consumption.

3.2.1 Concepts Related to the DRX Cycle in RRC_CONNECTED Mode


On Duration

For a UE in DRX mode, each time the UE turns on its receiver, it monitors the PDCCH for possible signaling for a preconfigured period of time. This continuous period is called On Duration, and the related timer is also named On Duration. The OnDurationTimer parameter specifies the On Duration.
The length of the On Duration Timer depends on the SRS and CQI because the SRS and CQI can be reported only in active time. When the timer length is greater than the value of the LongDrxCycle parameter, DRX may be ineffective. When the SupportShortDrx parameter is set to UU_ENABLE(Enable) and the timer length is greater than the value of the ShortDRXCycle parameter, DRX may be ineffective in a short DRX cycle.

DRX Cycle

A DRX cycle specifies the periodic repetition of the On Duration followed by a possible period of inactivity, as shown in Figure 3-2.
Figure 3-2 DRX cycle
NOTE:
The period following an On Duration may be active or sleep time. For details, see 3.2.3.1 Operation in Active Time.
A DRX cycle consists of active time and sleep time, corresponding to active state and sleep state, respectively.
A DRX cycle may be a long or short cycle.

Active Time

In active time, the UE turns on its receiver and monitors the PDCCH. Active time may be an On Duration or another period during which the UE needs to turn on its receiver. An example is when a DRX timer starts working or a high-priority service requires processing. DRX timers include the DRX Inactivity Timer, Contention Resolution Timer, and DRX Retransmission Timer. For details, see 3.2.3.1 Operation in Active Time.
If the duration of a DRX cycle is specified:
  • A longer active time results in a shorter service delay but higher UE power consumption.
  • A shorter active time results in lower UE power consumption but a longer service delay.

Sleep Time

In sleep time, the UE turns off its receiver and does not monitor the PDCCH.

Long DRX Cycle

After the UE enters the DRX mode, it must apply a long DRX cycle at the beginning. The LongDrxCycle parameter specifies the duration of a long DRX cycle and is mandatory.

Short DRX Cycle

Applying a short DRX cycle is optional. The SupportShortDrx parameter specifies whether to apply a short DRX cycle. The ShortDRXCycle parameter specifies the duration of a short DRX cycle.
If you configure a short DRX cycle for the UE, the UE determines when to apply the long or short DRX cycle as described in 3.2.4 Switching Between Long and Short DRX Cycles.

3.2.2 Startup of a DRX Cycle in RRC_CONNECTED Mode

After the UE enters the DRX mode, the On Duration Timer may not start immediately. The timer starts and the UE enters a long DRX cycle or a short DRX cycle only if the following condition is met:
  • For a long DRX cycle:
    [(SFN x 10) + SSFN] modulo (LongDRXCycle) = DRX start offset
    The following table describes the parameters and expression in the formula.
    Parameter or Expression
    Description
    SFN
    Indicates the system frame number that uniquely identifies a random access procedure.
    SSFN
    Indicates the system subframe number.
    DRX Start Offset
    Indicates the start offset of the long DRX cycle. The eNodeB notifies the UE of the offset in the RRC Connection Reconfiguration message.
    Specifies the length of a long DRX cycle. The eNodeB notifies the UE of the long DRX cycle in the RRC Connection Reconfiguration message.
    modulo
    Indicates the operation that obtains the reminders of division.
  • For a short DRX cycle:
    [(SFN x 10) + SSFN] modulo (ShortDRXCycle) = (DRX start offset) modulo (ShortDRXCycle)
    The short DRX cycle starts at the time specified by the SFN or SSFN.
    The following table describes the parameters and expression in the formula.
    Parameter or Expression
    Description
    (DRX Start Offset) modulo (ShortDRXCycle)
    Indicates the start offset of the short DRX cycle. The eNodeB notifies the UE of the offset in the RRC Connection Reconfiguration message.
    Specifies the length of a short DRX cycle. The eNodeB notifies the UE of the short DRX cycle in the RRC Connection Reconfiguration message.
    NOTE:
    If the ShortDRXCycle parameter is set, the value of the LongDrxCycle parameter must be integer multiples of the value of the ShortDRXCycle parameter.
Figure 3-3 shows how the UE enters the DRX mode. The eNodeB assigns the same long DRX cycle of 10 transmission time intervals (TTIs) to both UE 1 and UE 2 in a cell and instructs them to enter the DRX mode at TTI 1 and TTI 0 respectively. UE 1 and UE 2 enter the DRX cycle at TTI 3 and TTI 4 respectively based on the configured DRX start offset.
Figure 3-3 Entering the DRX mode and starting the DRX cycle

3.2.3 Operation in a DRX Cycle in RRC_CONNECTED Mode

A DRX cycle consists of active time and sleep time. This section describes the operation in active time and switching between active time and sleep time.

3.2.3.1 Operation in Active Time

The UE turns on its receiver in active time. According to 3GPP specifications, the UE is in active time if one of the following conditions is met:
  • The On Duration Timer, DRX Inactivity Timer, DRX Retransmission Timer, or Contention Resolution Timer is running. For details about the timers, see Table 3-1.
  • A scheduling request (SR) sent by the UE on the physical uplink control channel (PUCCH) is pending.
  • An UL grant for a pending hybrid automatic repeat request (HARQ) retransmission can occur and there is data in the corresponding HARQ buffer.
  • The UE has not received a PDCCH indicating an initial data transmission after successfully receiving a non-contention-based random access response.
  • The On Duration Timer has not started for the first time after the DRX parameter configurations are delivered to the UE.
The starting of a timer triggers the starting of active time. Table 3-1 describes DRX timers.
Table 3-1 DRX timers
DRX Timer
Parameter ID
Definition
Description
On Duration Timer
OnDurationTimer
Function
This timer measures the time during which the UE monitors the PDCCH.
Start
This timer starts at the first subframe of a DRX cycle. For details, see 3.2.2 Startup of a DRX Cycle in RRC_CONNECTED Mode.
Timing
Timing is based on the number of consecutive PDCCH subframes.
Stop
This timer stops after it expires or the UE receives a DRX command MAC control element (MCE).
Expiration
This timer stops. The UE enters the sleep time, no longer monitoring the PDCCH.
Cycle switching triggered by the DRX Inactivity Timer
DRXInactivityTimer
Function
This timer measures the time during which the UE determines whether to extend its active time because of the arrival of new data, and provides a reference for the UE to apply a short DRX cycle.
Start
This timer starts or restarts when the UE successfully decodes a PDCCH indicating an initial UL grant or DL user data for this UE.
Timing
Timing is based on the number of consecutive PDCCH subframes.
Stop
This timer stops after it expires or the UE receives a DRX command MCE.
Expiration
After this timer expires, the UE applies a short DRX cycle if the cycle is configured, and the DRX Short Cycle Timer starts or restarts. Alternatively, the UE applies the long DRX cycle if no short DRX cycle is configured. For details, see section 3.2.4.1 Switching to Short DRX Cycle.
DRX Short Cycle Timer
DRXShortCycleTimer
Function
This timer measures the lifetime of a short DRX cycle, that is, the number of consecutive repetition times of a short DRX cycle.
Start
  • After the DRX Inactivity Timer expires, this timer starts or restarts if a short DRX cycle is configured.
  • After the UE receives the DRX command MCE, this timer starts or restarts if a short DRX cycle is configured.
  • The UE applies a short DRX cycle after this timer starts.
Timing
Timing is based on the repetition times of short DRX cycle.
Stop
This timer stops after it expires.
Expiration
This timer stops, and the UE applies the long DRX cycle.
DRX Retransmission Timer
DRXReTxTimer
Function
This timer measures the time during which the UE waits for HARQ in active time. If this timer expires and the UE has not received the retransmitted data, the UE will not accept it.
Start
When the HARQ RTT Timer expires, the DRX Retransmission Timer starts or restarts if the UE does not receive the acknowledgment (ACK) feedback of the corresponding DL data.
Timing
Timing is based on the number of consecutive PDCCH subframes.
Stop
This timer stops if the UE receives the retransmission data before the timer expires.
Expiration
This timer stops, and the UE performs no further operations.
HARQ RTT Timer
N/A
Function
This timer measures the minimum number of subframes before a DL HARQ retransmission arrives in the case of a packet error occurs. This timer is used to determine when to start the DRX Retransmission Timer.
Start
This timer starts and the DRX Retransmission Timer stops at the subframe when there may be a possible semi-persistent DL data transmission or stops at the subframe when the UE learns by detecting the PDCCH that one of its HARQ processes has new subframes for DL transmission.
Timing
Timing is based on the number of subframes.
Stop
This timer stops after it expires.
Expiration
This timer stops. If the UE detects that DL data is received correctly, the UE takes no further action. Otherwise, the DRX Retransmission Timer starts.
Contention Resolution Timer
N/A
Function
This timer measures the time during which the UE waits for a Contention Resolution message in a contention-based random access procedure.For details about the random access procedure, see Connection Management Feature Parameter Description.
Start
This timer starts when the UE initially transmits or retransmits an Msg3 in a contention-based random access procedure.
Timing
Timing is based on the number of consecutive PDCCH subframes.
Stop
This timer stops after the UE receives a Contention Resolution message.
Expiration
This timer stops, and the UE retransmits a preamble.
In the On Duration, if the UE decodes a PDCCH and determines to start an initial data transmission, the DRX Inactivity Timer starts. The UE continues to monitor the PDCCH for new transmissions until the DRX Inactivity Time expires. The timer restarts if a new transmission occurs. Because of continuous data transmission, the DRX Inactivity Timer repeatedly restarts to prolong the active time.

3.2.3.2 Switching Between Active Time and Sleep Time

Switching between active time and sleep time is determined by DRX timers and service processes.
Figure 3-4 shows how the UE receiver switches between active time and sleep time in various scenarios.
NOTE:
In TDD networks, PDCCH subframes include DL subframes and special subframes containing DwPTS.
Figure 3-4 Switching between active time and sleep time
For details about DRX timers shown in Figure 3-4, see section ‎3.2.3.1 Operation in Active Time.
The active time shown in the timeline plot in the green box in Figure 3-4 combines the active time described in each of the other plots excluding the plot of HARQ RTT Timer. HARQ takes priority over DRX. After a HARQ process starts, the UE immediately switches to active time if it is in sleep time, and sends or receives HARQ feedback.
In the plot of HARQ RTT Timer, DL HARQ raises refers to one of the two DL HARQ transmission scenarios:
  • A semi-persistent DL data transmission is scheduled to start at the subframe.
  • A DL data transmission is scheduled to start at the subframe, which the UE learns by monitoring the PDCCH.
Table 3-2 describes the conditions for starting active time. For example, OD indicates the condition for starting the On Duration Timer at TTI 2 and TTI 15. For details about DRX timers, see Table 3-1.
Table 3-2 Conditions for starting active time
Condition
Meaning
OD
A DRX cycle starts.
IA
A PDCCH indicating an initial UL or DL data transmission is received.
R
The HARQ RTT Timer expires.
SR
A UL SR is sent.
UR
A UL negative acknowledgment (NACK) is received, and retransmission is required.
RAR
A non-contention-based random access response is received.
CR
Msg3 is sent in a random access procedure.

3.2.4 Switching Between Long and Short DRX Cycles

Although the eNodeB assigns both long and short DRX cycles to the UE, the UE applies only the long or short DRX cycle at a time.
The UE switches between the long and short DRX cycles.

3.2.4.1 Switching to Short DRX Cycle

After the DRX Inactivity Timer expires or the UE receives the DRX command MCE from the eNodeB, the UE exits the long DRX cycle and enters a short DRX cycle.
  1. Cycle switching triggered by the DRX Inactivity Timer
    If data is transmitted at one moment, the eNodeB determines there is a high probability that data transmission will occur at the following moment and starts the DRX Inactivity Timer. After the DRX Inactivity Timer expires, the short DRX cycle starts.
  2. Cycle switching triggered by the DRX command MCE
    After the UE receives the DRX command MCE, the UE applies a short DRX cycle if the eNodeB has assigned this short DRX cycle to the UE. Otherwise, the UE applies the long DRX cycle.

3.2.4.2 Switching to a Long DRX Cycle

If the UE does not receive new data for a specified period after entering a short DRX cycle, it switches to a long DRX cycle to consume less power.
The period before the UE switches to a long DRX cycle is called the lifetime of a 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 a short DRX cycle runs. The DrxShortCycleTimer parameter specifies the length of the DRX Short Cycle Timer. After the DRX Short Cycle Timer expires, the UE applies the long DRX cycle.

3.3 Conditions for Entering and Exiting DRX Mode in RRC_CONNECTED Mode

A UE enters or exits the DRX mode only after receiving an instruction from the eNodeB. This section describes the conditions for entering and exiting the DRX mode.

3.3.1 Conditions for Entering DRX Mode in RRC_CONNECTED Mode

The DRX functionality is jointly controlled by the general DRX switch DrxAlgSwitch and the QCI-specific DRX switch EnterDrxSwitch.
Upon receiving an RRC Connection Reconfiguration message with the DRX-Configuration information element (IE) set to setup, a UE enters the DRX mode. The eNodeB sends this message if all of the following conditions are met:
  • The DrxAlgSwitch parameter is set to ON.
  • All the bearers for the UE support DRX.
    The EnterDrxSwitch parameter of each bearer is set to ON.
  • The traffic volume of the UE is low.
    The TddEnterDrxThdUl and TddEnterDrxThdDl parameters specify uplink (UL) and DL traffic thresholds, respectively.
  • The TddPowerSaveMeasSwitch parameter is set to ON, and the UE active time is short.
    The TddPowerSavingEnterDrxThd parameter specifies the UE active time threshold.
    NOTE:
    If the UE is not in the DRX mode and continuously performs gap-assisted measurement, the eNodeB does not instruct the UE to enter the DRX mode. This may occur if the fast ANR function is enabled, messages reported by UEs are customized on the M2000, or gap-assisted measurement is triggered on the UE because the signal strength is low.
    The eNodeB does not instruct the UE to enter the DRX mode when the UE is in the TTI bundling scheduling state.

3.3.2 Conditions for Exiting DRX Mode in RRC_CONNECTED Mode

After a UE receives an RRC Connection Reconfiguration message with the DRX-Configuration IE set to release, it exits the DRX mode and clears all the saved DRX parameters. An eNodeB sends this message if one of the following conditions is met:
The UE also exits DRX mode if one of the following conditions is met:
  • The DrxAlgSwitch parameter is set to OFF. In this situation, the eNodeB instructs the UE to exit DRX mode upon DRX reconfiguration originated by the UE.
  • The UE in RRC_CONNECTED mode switches to RRC_IDLE mode due to poor radio conditions or other exceptions.
  • A handover is initiated.
    During a handover, the eNodeB instructs the UE in DRX mode to exit the DRX mode. After the handover, the UE enters the DRX mode according to the trigger conditions.
  • The UE enters the TTI bundling scheduling state.
    When the UE enters the TTI bundling scheduling state, the eNodeB instructs the UE to exit the DRX mode.

3.4 DRX Mode in RRC_CONNECTED Mode in Various Scenario

UEs enter active time and sleep time according to DRX configurations, as described in 3.3 Conditions for Entering and Exiting DRX Mode in RRC_CONNECTED Mode.
For common services on common UEs, users can configure a set of DRX parameters. For example, for VoIP services, users can set DRX parameters corresponding to QCI 1. For details, see 3.4.2 DRX in RRC_CONNECTED Mode for VoIP Services.
For special UEs or ANR measurements, users can configure special DRX parameters. For details about the DRX configurations for special UEs and for ANR measurements, see 3.4.3 DRX in RRC_CONNECTED Mode for Special UEs and 3.4.4 DRX in RRC_CONNECTED Mode for ANR Measurements, respectively.
Table 3-3 lists the DRX parameters for various scenarios.
Table 3-3 DRX parameters for various scenarios
DRX Parameters for Common UEs
DRX Parameters for Special UEs
DRX Parameters for ANR Measurement
VoIP Services
Non-VoIP Services
Intra-RAT
Inter-RAT
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A

3.4.1 Relationship Between DRX in RRC_CONNECTED Mode and QCI

Services with different QCIs have different characteristics. Users can set DRX policies for each QCI. The following QCI-specific parameters are configurable:
For information about the functions and usage of this switch, see 3.3 Conditions for Entering and Exiting DRX Mode in RRC_CONNECTED Mode.
Table 3-4 lists the mapping between QCIs and service types.
Table 3-4 Mapping between QCIs and service types
QCI
Bearer
Priority
PDB (ms)
PELR
Example
1
GBR
2
100
Conversational voice
2
4
150
Conversational video, such as live streaming
3
3
50
Real-time gaming
4
5
300
Non-conversational video, such as buffered streaming
5
Non-GBR
1
100
IMS signaling
6
6
300
Video, such as buffered streaming
TCP-based services, such as www, email, chat, FTP, and P2P
7
7
100
Voice video, such as live streaming
Interactive games
8
8
300
Video, such as buffered streaming
TCP-based services, such as www, email, chat, FTP, and P2P
9
9
NOTE:
  • PDB: packet delay budget
  • GBR: guaranteed bit rate
  • PELR: packet error loss rate
For example, VoIP services have a QCI of 1 (that is, QCI 1), and therefore the DRX parameters for QCI 1 apply to VoIP services. For DRX principles that apply to VoIP services, see 3.4.2 DRX in RRC_CONNECTED Mode for VoIP Services.

3.4.2 DRX in RRC_CONNECTED Mode for VoIP Services

For VoIP services, a set of special DRX parameter settings is available to reduce UE power consumption while maintaining VoIP capacity.
VoIP services have a QCI of 1, and therefore the DRX parameters for QCI 1 apply to VoIP services. This section describes these parameters.

Long DRX Cycle

The long DRX cycle is specified by the LongDrxCycle parameter.
The recommended value is SF20(20 subframes) when QCI is 1, because VoIP services have a scheduling period of 20 ms.
  • If the parameter value is too small, there is a high probability that the UE stays in the active state and consumes more power.
  • If the parameter value is too large, the VoIP scheduling may be performed in the silent period. This delays packet transmission and has a negative impact on user experience.

Short DRX Cycle

Short DRX cycles are not available for VoIP services.

3.4.3 DRX in RRC_CONNECTED Mode for Special UEs

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 enables operators to designate a UE as a special UE and use a set of special DRX parameters for this UE to improve service performance and energy efficiency.
On the Evolved Packet Core (EPC) side, the RFSP of a UE 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 sent to the eNodeB using the INITIAL CONTEXT SETUP REQUEST message over the S1 interface.
Operators can set the Spid parameter for the eNodeB to an integer ranging from 1 to 256 on the M2000 or Web local maintenance terminal (LMT). If the RFSP value of the UE is the same as the Spid parameter value and the DrxStatus parameter is set to FALSE, the eNodeB determines that the UE is a special UE. Otherwise, the eNodeB determines that the UE is a common UE. Set the parameters in the SpidCfg MO based on the UE RFSP on the EPC side.
The UE reports its type (common or special) to the eNodeB using the IE UE-EUTRA-Capability in a UECapabilityInformation message. If the IE UE-EUTRA-Capability contains noBenFromBatConsumpOpt, the UE is a special UE. If the IE UE-EUTRA-Capability does not contain noBenFromBatConsumpOpt, the UE is a common UE.
The eNodeB compares the UE type reported by the UE with that configured on the eNodeB. If they are inconsistent, the eNodeB determines that the UE is a special UE. If they are consistent, the eNodeB determines the UE type based on the report and applies the corresponding 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.

3.4.4 DRX in RRC_CONNECTED Mode for ANR Measurements

If an eNodeB receives a special-DRX starting indication during ANR measurements, the eNodeB configures or reconfigures a relatively large value of the long DRX cycle, during which UEs perform ANR measurements in the sleep time.
The configuration or reconfiguration of the long DRX cycle does not consider whether the DrxAlgSwitch parameter is set to ON(On) or OFF(Off). This long DRX cycle is specified by:
The LongDrxCycleForAnr parameter if UEs perform the ANR measurements on LTE cells.
The LongDRXCycleforIRatAnr parameter if UEs perform the ANR measurements on GSM or UMTS cells. GSM is short for Global System for Mobile Communications, and UMTS is short for Universal Mobile Telecommunications System.
ANR measurements require a relatively long sleep time. If the value of the long DRX cycle is too small, ANR measurements cannot be performed. If the value is too large, the scheduling delay is so long that it fails to meet the quality of service (QoS) requirements.

4 Dynamic DRX

This chapter describes the implementation principles of dynamic DRX (TDLOFD-00110501 Dynamic DRX).

4.1 Introduction

Rich LTE applications increase smartphone service traffic and enable smartphones to consume more power and signaling resources, which imposes new requirements of UE power saving techniques for networks.
  • Many smartphone applications use a few small packets or heartbeat packets. After service sessions end, smartphones enter RRC_IDLE mode to save battery power.
  • However, for most services, smartphones remain online by periodically sending heartbeat packets to the corresponding application servers. These heartbeats and other instant service messages require the network to frequently reestablish connections and therefore consume a large amount of signaling resources.
  • When these services are used, the network can increase the time the smartphones are in RRC_CONNECTED mode. However, the smartphones consume more power.
Against this backdrop, Huawei introduces dynamic DRX to reduce the signaling amount and power consumption for smartphones.

4.1.1 Definition

Dynamic DRX enables smartphones to reduce the consumption of UL resources and energy when processing services that use a few small packets or heartbeat packets. Dynamic DRX performs the following functions:
Keeps smartphones in RRC_CONNECTED mode to reduce signaling.
Enables smartphones to enter the UL out-of-synchronization state quickly to reduce PUCCH resource consumption.
Configures DRX parameters for the UL out-of-synchronization state with a longer DRX cycle to reduce UE power consumption.

4.1.2 Benefits

Dynamic DRX applies to networks with a large number of smartphones. Table 4-1 describes the key techniques of dynamic DRX and benefits.
Table 4-1 Key techniques of dynamic DRX and benefits
Key Technique
Benefits
Keeping UEs in RRC_CONNECTED mode
Reduces the amount of signaling generated when UEs switch between the RRC_CONNECTED and RRC_IDLE modes frequently and therefore prevents signaling storms
Enabling UEs to enter the UL out-of-synchronization state quickly
Reduces consumption of PUCCH and sounding reference signal (SRS) resources.
Configuring DRX parameters for the UL out-of-synchronization state with a longer DRX cycle
Reduces UE power consumption.

4.1.3 Architecture

Dynamic DRX is implemented based on the packet arrival interval measurement, scheduling, and handover features. Figure 4-1 shows the implementation architecture of dynamic DRX.
Figure 4-1 Implementation architecture of dynamic DRX

4.2 Principles

Dynamic DRX allows eNodeBs to deliver different DRX parameters to UEs in the synchronization and uplink out-of-synchronization states. When smartphones are in the uplink out-of-synchronization state, an eNodeB assigns these smartphones a DRX cycle longer than LongDrxCycle by setting a set of dedicated DRX parameters. As a result, the sleep time is longer, and therefore the power saving gain of DRX for smartphones increases. The principles of dynamic DRX are as follows:
  1. The UeInactivityTimerDynDrx parameter is set to a large value to increase the time UEs are in RRC_CONNECTED mode. This reduces the number of switchings between RRC_CONNECTED and RRC_IDLE modes, reduces the amount of RRC connection establishment and release signaling for services that use a few small packets or heartbeat packets, but enables UEs to consume more power.
    The UlSynTimerDynDrx is set to a small value to decrease the time an eNodeB synchronizes with UEs.
  2. When UEs are in the uplink out-of-synchronization state, the eNodeB assigns the UEs a longer DRX cycle by setting the LongDrxCycleUnsync, OndurationTimerUnsync, and DrxInactivityTimerUnsync parameters.
  3. When UEs are in the uplink synchronization state, the eNodeB delivers the parameters associated with DRX in RRC_CONNECTED mode to UEs.

5 High-Mobility-Triggered Idle Mode

This chapter describes the implementation principles of the high-mobility-triggered idle mode feature (TDLOFD-00110502 High-Mobility-Triggered Idle Mode).

5.1 Introduction

UEs frequently perform handovers if they continue to process services. Handovers in this scenario are inevitable. In addition, the number of handovers increases if UEs remain online for a long period of time and move frequently, especially for UEs processing services that require frequent transmission of small packets. All these handovers result in a signaling increase.
When a UE is running services that require frequent transmission of small packets, the UE needs to exchange the following messages with the network at an interval longer than 60s:
Heartbeat messages between a client and a server
Real-time PUSH messages
Status notices, such as a friend information update notice
If a small amount of data is transmitted within a short duration in each period and UEs move fast, the signaling increase due to frequent UE handovers is greater than the signaling reduction gained by UEs staying in the always-online state.
To address these issues, Huawei provides high-mobility-triggered idle mode. This feature enables UEs to enter idle mode to prevent signaling bursts.

5.1.1 Definition

If UEs frequently move between cells and remain online for a long period of time, a large number of handovers are triggered, causing signaling bursts.
After dynamic DRX is enabled, UEs remain online for a prolonged period of time. In this scenario, if UEs move fast, more handovers instead of cell reselections are triggered.
Huawei introduces high-mobility-triggered idle mode to prevent fast-moving UEs from performing a large number of handovers and reduce the impact of handovers on eNodeB performance.
High-mobility-triggered idle mode is a state in which the number of handovers decreases after UEs enter idle mode based on their movement speed and the packet sending state.

5.1.2 Benefits

This feature reduces the number of handovers and minimizes the impact of handover signaling on network stability.

5.1.3 Architecture

In high-mobility-triggered idle mode, eNodeBs determine whether to release UEs based on their movement speeds, packet sending state, and camping time.

5.2 Principles

Characteristics of Fast-Moving UEs

The LTE network is usually deployed in hot spots, which have the following characteristics:
  • Densely populated areas where people are often on the move
  • Small spacing between eNodeBs
Therefore, handovers are easily triggered for fast-moving UEs.
Figure 5-1 shows that a UE moves between cells in a hot spot.
Figure 5-1 UE movement
Assuming that a UE passes through the center coverage area of an eNodeB. Table 5-1 and Table 5-2 list the movement speed and camping time of the UE in a cell with a radius of 300 m and a cell with a radius of 500 m, respectively.
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 to 60
18 to 36
60 to 120
9 to18
> 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 to 60
30 to 60
60 to 120
15 to 30
> 120
< 15
In actual conditions, most UEs do not pass through the center of a cell. The camping time in such a case is shorter than that when a UE passes through the center of a cell.
Figure 5-2 shows the numbers of service requests triggered by heartbeats.
Figure 5-2 Numbers of service requests triggered by heartbeats
The x-axis specifies the service types.
The y-axis specifies the number of service requests triggered by heartbeats within an hour.
The heartbeat period is calculated by using the following formula:
Heartbeat period (s) = 3600/Number of service requests
The fewer the service requests within an hour, the longer the heartbeat period.
You can extrapolate the following from the data shown in Figure 5-2:
  • The heartbeat periods for most services are relatively long.
The heartbeat periods are 180s or longer for most applications, such as QQ, Skype, Facebook, and Twitter.
  • In a heartbeat period, a UE may perform handovers many times.
In a heartbeat period, fast-moving UEs may pass through several cells. For example, in a heartbeat period of 180s, a UE moving at 30 km/h passes through at least five cells with a radius of 300 m. If the UE is in the always-online state, at least five handovers are performed. During this process, no data is transmitted.
In addition, the results of measurements in heartbeat periods show the following:
  • Most UEs have only heartbeat packets to transmit within a long period of time, which is even longer than the time UEs take to process other services.
    Most users lay aside their UEs that have only heartbeat packets to transmit. In this case, UEs take longer time to process services with only heartbeat packets than to process other services.
  • Even when UEs have only heartbeat packets to transmit, they remain in the active state. Therefore, a large number of handovers are triggered when UEs are moving.

Working Mechanism

When users use services with only heartbeat packets, the eNodeB enables UEs to remain in the active state to minimize the impact of network signaling generated due to frequent connection releases and reestablishments.
In this case, UEs are always online. If UEs are moving, a large number of handovers are triggered. Moreover, during the handover processes, UEs may have no data to transmit.
To minimize the negative impact of handovers, this feature enables UEs to enter idle mode if they move at 30 km/h or faster and have few packets to transmit (for example, UEs that have only heartbeat packets to transmit).
When the eNodeB receives the measurement report and determines that a UE needs a handover, the eNodeB checks whether the UE is moving fast. If the UE is moving fast, the eNodeB triggers the S1 release procedure and enables the UE to enter idle mode. In this case, a handover is avoided. Figure 5-3 shows the working mechanism of the high-mobility-triggered idle mode feature.
After a UE enters idle mode, it transmits data only when a heartbeat period begins. The user experience is not affected.
Figure 5-3 Working mechanism of the high-mobility-triggered idle mode feature

6 Related Features


6.1 Features Related to DRX in RRC_CONNECTED Mode

Prerequisite Features

None

Mutually Exclusive Features

None

Impacted Features

DRX in RRC_CONNECTED mode impacts performance of features such as scheduling, connection management, mobility management in connected mode, measurement, and channel quality indicator (CQI) and timing control.
Scheduling
The eNodeB enables resource scheduling for the UE only in active time if no system information is delivered or no paging is performed.
In DRX mode, the UE sends an SR to the eNodeB when there is data in the UE buffer. If the UE is in sleep time, it immediately switches to active time and begins to monitor the PDCCH. When the UE receives an initial PDCCH message, the DRX Inactivity Timer starts. This ensures that active time continues and the UE obtains resources.
In DL scheduling, DL HARQ takes priority over DRX. No matter a UE is in active time or not, it can send HARQ feedback to the eNodeB. In UL scheduling, the eNodeB must ensure that both the eNodeB and UE are in active time during the TTI within which the eNodeB may deliver a UL grant for a pending HARQ retransmission. In this way, the eNodeB can send ACK/NACK feedback or schedule a retransmission, and the UE can receive HARQ feedback within this TTI.
There is a low probability that the eNodeB and UEs are in different DRX states, which is resulted from false SR detection. In this situation, if no data is transmitted in the UL, the UL and DL block error rates (BLERs) increase. However, if there is UL data transmission, the UL and DL BLERs are not affected.
Connection Management
During random access, the UE always responds to random access requests, regardless of whether it is in active time.
Mobility Management in Connected Mode
In different stages of a handover, DRX functions in the following manners:
  • When the handover process starts:
    After receiving an indication of accepting the handover decision, the source eNodeB sends the RRC Connection Reconfiguration message to instruct the UE to exit the DRX mode. If the UE is in sleep time, it will receive the message in active time in the next DRX cycle.
  • If the handover succeeds:
    The UE cannot use the DRX feature if the DRX feature is deactivated on the target eNodeB.
  • If the handover fails:
    The UE remains in the current cell, and the source eNodeB checks whether the UE can enter the DRX mode.
    For details about the handover process in DRX mode, see Mobility Management in Connected Mode Feature Parameter Description.
    Measurement
    Measurement takes priority over DRX, even when measurement configurations conflict with DRX configurations.
    For details about the measurement process in DRX mode, see Mobility Management in Connected Mode Feature Parameter Description.
    UE measurement in the LTE system is classified into the following types:
    • Common measurement
      During random access, the UE enters active time 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 sleep time, it will send measurement reports in active time in the next DRX cycle.
    • Gap-assisted measurement
      In gap-assisted measurement, gaps with 6 ms each are generated every 40 ms or 80 ms. To reduce the impact on data transmission, the eNodeB needs to generate gaps in sleep time or prevent UEs from entering DRX mode in gaps.
      When periodic MR reporting based on the gap-assisted measurement is enabled, the UE cannot enter the DRX mode. If you have subscribed to the FARS cell tracing results and Nastar analysis results in periodic MR reporting, check whether they have been mistakenly enabled. For details, see the operation logs on the M2000.
      As shown in Figure 6-1, gaps are generated every 40 ms, six TTIs earlier than the DRX cycle, and the status of the On Duration Timer represents DRX cycles.
      Figure 6-1 DRX cycles and gap-assisted measurements
    Common measurement applies to intra-frequency measurement, and gap-assisted measurement applies to inter-frequency measurement and inter-radio access technology (RAT) measurement.
    CQI
    In DRX mode, the UE turns off its receiver intermittently. This restricts the eNodeB to delivering CQI and sounding reference signal (SRS) measurement configurations and the UE in reporting these CQI and SRS measurement results. Therefore, the eNodeB cannot deliver these measurement configurations in sleep time, and the UE must report these 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 through the PUCCH only in active time.
    • For UEs complying with 3GPP Release 9, CQIs, PMIs, and RIs can be reported through the PUCCH in the On Duration. The eNodeB uses the cqi-Mask field to control whether CQIs, PMIs, and RIs are reported in the On Duration. If this field is set to setup, CQIs, PMIs, and RIs can be reported only in the On Duration. If this field is not set, CQIs, PMIs, and RIs can be reported in active time.
    SRSs can be reported only in active time.
    CQI configurations affect the DRX parameter settings by the eNodeB. The eNodeB can automatically adjust the values of OnDurationTimer configured by the operator so that the number of CQIs reported by the UE meets the requirements of DL scheduling performance.
    NOTE:
    By default, the cqi-Mask field is not set for UEs that comply with 3GPP Release 9 because most of them do not support this field.
    Timing Control
    When SRSs are used for timing control, SRS configurations affect how the eNodeB sets the DRX parameters. The measurement precision of time alignment (TA) for UL synchronization depends on the number of times that SRS measurements are reported. To acquire sufficient SRSs for TA measurements, the eNodeB adaptively adjusts the setting of the LongDrxCycle parameter based on the SRS configurations of the UE and the interval of TA delivery to the UE. Therefore, the value of LongDrxCycle delivered to the UE on the live network may differ from that set by running MML commands. This 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.
    When the TimingAdvCmdOptSwitch parameter is set to ON, the eNodeB does not restrict the length of the long DRX cycle. However, it is recommended that the value of LongDrxCycle is less than or equal to 320 ms to prevent the impact on UL timing control performance.
    When demodulation reference signals (DMRSs) are used for timing control and DRX is enabled, at least one active time must exist during the interval of TA delivery. In this way, the eNodeB can deliver scheduling information to acquire sufficient DMRS resources for TA delivery.
    NOTE:
    When the eNodeB configures DRX parameters for UEs, the validity check mechanism is used to ensure that UEs comply with 3GPP TS 36.331 and are compatible with the chips provided by some manufacturers. Therefore, the DRX parameters configured using MML commands may be modified after the validity check.
    Validity check involves the following:
    • Whether the long DRX cycle is an integer multiple of the short DRX cycle. If not, the short DRX cycle is automatically adjusted to an appropriate value.
    • Whether the On Duration Timer is less than the short DRX cycle. If not, the eNodeB does not deliver the short DRX cycle to UEs.
    • Whether the On Duration Timer is less than the long DRX cycle. If not, the eNodeB does not deliver the DRX parameters to UEs.

6.2 Features Related to Dynamic DRX

Prerequisite Features

None

Mutually Exclusive Features

None

Impacted Features

This feature affects carrier aggregation (CA).
A carrier aggregation (CA) UE for which the SCell has been configured can enter the dynamic DRX state only when dynamic DRX has been enabled on the two carriers. If dynamic DRX is disabled on either of them, the CA UE cannot use dynamic DRX.

6.3 Features Related to High-Mobility-Triggered Idle Mode

Prerequisite Features

This feature requires dynamic DRX.
Dynamic DRX must be enabled before you enable this feature.

Mutually Exclusive Features

None

Impacted Features

None

7 Network Impact

DRX algorithms limit the length of a long DRX cycle to ensure a sufficient number of SRSs used for uplink timing control.
After DRX is activated, UEs enter DRX mode in some scenarios. In this mode, UE power consumption decreases, but service response delays increase and throughput decreases.
If the configured long DRX cycle is much longer than the length of the On Duration Timer and DRX Inactivity Timer, the Timing Adjust (TA) timer will time out frequently. To solve this problem, set the DRX long cycle to an appropriate length or enable the short DRX cycle.
When the short DRX cycle is enabled, the switching between the active and sleep states is the same as the switching when only the long DRX cycle is enabled, but the power-saving performance degrades.

7.1 DRX in RRC_CONNECTED Mode

System Capacity

None

Network Performance

The sleep time in DRX helps reduce UE power consumption but may increase the delay of ongoing services. Performance of these services may be further affected. For example, the traffic volume of FTP services may be reduced.
Inappropriate DRX settings may also impact the network as follows:
  • If the value of the OnDurationTimer parameter is too small, it reduces VoIP capacity.
  • If the value of the LongDrxCycle parameter is too large, the CQI reporting period is affected and therefore the throughput decreases under functions such as scheduling and multiple-input multiple-output (MIMO).
  • A short sleep time in DRX has a negative impact on ANR measurements.
  • If the value of the LongDrxCycle parameter is too large, the handover success rate decreases and the service drop rate increases.
NOTE:
After determining that DRX is enabled, the eNodeB instructs the UE to exit the pre-scheduling state. The performance of TCP services with ping delay and small window size deteriorates. For details, see Scheduling Feature Parameter Description.

7.2 Dynamic DRX

System Capacity

None

Network Performance

After dynamic DRX is enabled, DRX parameters for the out-of-synchronization state affect the period at which RSRP measurement results are reported, and therefore handovers are delayed or call drops occur. Performance measurement does not include this data.

7.3 High-Mobility-Triggered Idle Mode

System Capacity

This feature has little impact on the system capacity.

Network Performance

  • This feature reduces the impact of handover signaling of high-mobility UEs. After this feature is enabled, the number of handovers on the entire network will decrease.
  • When the number of handovers decreases, the impact on CPU usage is reduced. After this feature is enabled, CPU usage may decrease.

8 Engineering Guidelines for DRX in RRC_CONNECTED Mode

This chapter provides engineering guidelines for DRX in RRC_CONNECTED mode.

8.1 When to Use DRX in RRC_CONNECTED Mode

DRX in RRC_CONNECTED mode is recommended if operators require UE power saving in cells and allow DRX-induced delay.

8.3 Planning

RF Planning

None

Network Planning

None

Hardware Planning

None

8.4 Deployment


8.4.1 Requirements

Operating Environment

None

Transmission Networking

None

License

None

8.4.2 Data Preparation

This section describes the data that you need to collect for setting parameters. Required data is data that you must collect for all scenarios. Collect scenario-specific data when necessary for a specific feature deployment scenario.
There are three types of data sources:
  • 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 CellDrxPara managed objects (MOs) to configure cell-level DRX parameters.
Parameter Name
Parameter ID
Setting Notes
Data Source
Local cell ID
This parameter specifies the local ID of a cell. It uniquely identifies a cell within an eNodeB.
Network plan (negotiation not required)
TDD enter DRX threshold Uplink
The probability of entering DRX mode has a positive correlation with the value of this parameter.
Network plan (negotiation not required)
TDD exit DRX threshold Uplink
The probability of exiting DRX mode has a negative correlation with the value of this parameter. When the value of TddExitDrxThdUl is close to the value of TddEnterDrxThdUl, UEs frequently enter and exit DRX mode.
Network plan (negotiation not required)
TDD enter DRX threshold Downlink
The probability of entering DRX mode has a positive correlation with the value of this parameter.
Network plan (negotiation not required)
TDD exit DRX threshold Downlink
The probability of exiting DRX mode has a negative correlation with the value of this parameter. When the value of TddExitDrxThdDl is close to the value of TddEnterDrxThdDl, UEs frequently enter and exit DRX mode.
Network plan (negotiation not required)
Data amount Statistic timer
This parameter specifies the UE traffic measurement period. The DRX algorithm determines whether a UE needs to exit or enter DRX mode based on the UE traffic volume measured during this period.
Network plan (negotiation not required)
DRX Active Time Measurement Switch
This parameter specifies whether the eNodeB supports DRX active-time measurement in a cell that operates in TDD mode.
  • When this parameter is set to ON, the eNodeB supports power saving measurement.
  • When this parameter is set to OFF, the eNodeB does not support power saving measurement.
Network plan (negotiation not required)
DRX Active Time Measurement Period
This parameter is valid only when DRX Active Time Measurement Switch is set to ON(On).
This parameter specifies the power saving measurement period. The eNodeB uses the measurement result in the DRX algorithm to determine whether the UE should enter or exit DRX mode.
Network plan (negotiation not required)
DRX Active Time Measurement Enter DRX Threshold
This parameter is valid only when DRX Active Time Measurement Switch is set to ON(On).
If the power saving measurement result is lower than this threshold, the eNodeB instructs the UE to stay in or enter DRX mode.
Network plan (negotiation not required)
DRX Active Time Measurement Exit DRX Threshold
This parameter is valid only when DRX Active Time Measurement Switch is set to ON(On).
If the power saving measurement result is higher than this threshold, the eNodeB instructs the UE to exit DRX mode or stay in non-DRX mode.
Network plan (negotiation not required)

Scenario-specific Data

Scenario 1: Setting DRX Parameters for Common UEs
The following table describes the parameters that must be set in the Drx MO to configure eNodeB-level DRX parameters.
Parameter Name
Parameter ID
Setting Notes
Data Source
DRX switch
Set this parameter to ON(On) if DRX is required.
Network plan (negotiation not required)
Short-cycle DRX switch
Set this parameter to ON(On) if short DRX cycles are required.
Network plan (negotiation not required)
The following table describes the parameters that must be set in DrxParaGroup MOs to configure DRX parameter groups.
Parameter Name
Parameter ID
Setting Notes
Data Source
Local cell ID
This parameter specifies the local ID of a cell. It uniquely identifies a cell within an eNodeB.
Network plan (negotiation not required)
DRX parameter group ID
This parameter specifies a DRX parameter group.
Each group ID is mapped to a QCI.
Network plan (negotiation not required)
Enter DRX Switch
This parameter specifies whether bearers to which the DRX parameter group applies support DRX. A UE can enter DRX mode only when all bearers for the UE support DRX.
  • The value OFF(Off) is recommended for bearers with high requirements for the delay.
  • The value ON(On) is recommended for bearers with low requirements for the delay.
Network plan (negotiation not required)
On Duration Timer
This parameter specifies the length of the On Duration Timer.
The larger the parameter value, the longer the active time and the shorter the delay.
Set this parameter as required.
Network plan (negotiation not required)
DRX Inactivity Timer
This parameter specifies the length of the DRX Inactivity Timer. The larger the parameter value, the longer the active time is extended after the UE receives new data.
Set this parameter as required.
Network plan (negotiation not required)
DRX Retransmission Timer
This parameter specifies the length of the DRX Retransmission Timer.
Network plan (negotiation not required)
Long DRX Cycle
This parameter specifies the length of a long DRX cycle.
The larger the parameter value, the longer the sleep time and the delay.
When Uplink timing advance command optimization switch is set to ON(On), to prevent the impact on UL timing control, a value of 320 ms or less is recommended for Long DRX Cycle. For smartphones with high power-saving requirements, set Long DRX Cycle and TimeAlignmentTimer to 320 ms and 10,240 ms, respectively.
NOTE:
A long cycle of 320 ms prolongs the RSRP reporting period and may have a negative impact on the handover success rate. The impact depends on the speed at which the UE is moving and the network coverage quality. Set Long DRX Cycle based on test results. For high speed cells, 40 ms is recommended.
Network plan (negotiation not required)
Short-cycle DRX supported indication
This parameter specifies whether to enable short DRX cycles.
Network plan (negotiation not required)
Short DRX Cycle
This parameter specifies the length of a short DRX cycle.
The larger the parameter value, the longer the sleep time and the delay.
Network plan (negotiation not required)
DRX Short Cycle Timer
This parameter specifies the length of the DRX Short Cycle Timer.
The larger the parameter value, the longer the duration that the UE is in short DRX cycles.
Network plan (negotiation not required)
Scenario 2: Setting DRX Parameters for Special UEs
The following table describes the parameters that must be set in SpidCfg MOs to configure the DRX status for each subscriber profile ID (SPID).
Parameter Name
Parameter ID
Setting Notes
Data Source
Spid
This parameter specifies an SPID. Set this parameter based on the network plan.
Network plan (negotiation not required)
Drx status
This parameter specifies whether to use common or special DRX settings.
  • The value TRUE(TRUE) indicates that UEs with an SPID use common DRX settings.
  • The value FALSE(FALSE) indicates that UEs with an SPID use special DRX settings.
Network plan (negotiation not required)
The following table describes the parameters that must be set in the Drx MO to configure eNodeB-level DRX parameters.
Parameter Name
Parameter ID
Setting Notes
Data Source
DRX switch
Set this parameter to ON(On) if DRX is required.
Network plan (negotiation not required)
Short-cycle DRX switch
Set this parameter to ON(On) if short DRX cycles are required and Drx status in the SpidCfg MO is set to TRUE(TRUE).
Network plan (negotiation not required)
Special long DRX cycle
This parameter specifies the length of long DRX cycles that apply only to non-power-saving UEs whose RFSP indexes are contained in the RFSP index set.
The value SF10(10 subframes) is recommended.
Network plan (negotiation not required)
Special On Duration timer
This parameter specifies the length of the On Duration Timer when it applies only to non-power-saving UEs whose RFSP indexes are contained in the RFSP index set.
The larger the parameter value, the longer the active time and the shorter the delay.
The value PSF4(4 subframes) is recommended.
Network plan (negotiation not required)
Special DRX inactivity timer
This parameter specifies the length of the DRX Inactivity Timer when it applies only to non-power-saving UEs whose RFSP indexes are contained in the RFSP index set.
The value PSF5(5 subframes) is recommended.
Network plan (negotiation not required)
Special short-cycle DRX supported indication
This parameter specifies whether to enable short DRX cycles for non-power-saving UEs whose RFSP indexes are contained in the RFSP index set.
The value UU_DISABLE(Disable) is recommended.
Network plan (negotiation not required)
Special short DRX cycle
This parameter specifies the length of short DRX cycles that apply only to non-power-saving UEs whose RFSP indexes are contained in the RFSP index set.
The value SF10(10 subframes) is recommended.
Network plan (negotiation not required)
Special DRX short cycle timer
This parameter specifies the length of the DRX Short Cycle Timer when it applies only to non-power-saving UEs whose RFSP indexes are contained in the RFSP index set.
The value 1 is recommended.
Network plan (negotiation not required)
Scenario 3: Setting DRX Parameters for ANR Measurements
The following table describes the parameters that must be set in the Drx MO to configure the DRX parameters for ANR measurements.
Parameter Name
Parameter ID
Setting Notes
Data Source
Long DRX Cycle for ANR
This parameter specifies the long DRX cycle for intra-RAT ANR. If intra-RAT ANR is enabled, this parameter is valid regardless of whether DRX is disabled.
To increase the ANR measurement success rate., the following values are recommended:
  • SF256(256 subframes)
  • SF320(320 subframes)
  • SF512(512 subframes)
  • SF640(640 subframes)
  • SF1024(1024 subframes)
  • SF1280(1280 subframes)
  • SF2048(2048 subframes)
SF2560(2560 subframes)
Network plan (negotiation not required)
Long DRX Cycle for Inter-RAT ANR
This parameter specifies the long DRX cycle for inter-RAT ANR. If inter-RAT ANR is enabled, this parameter is valid regardless of whether DRX is disabled.
Network plan (negotiation not required)

8.4.3 Precautions

Before enabling DRX in RRC_CONNECTED mode, ensure that UEs in the network comply with 3GPP specifications.

8.4.4 Activation

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 section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:
  • The MOs in 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 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
MO
Sheet in the Summary Data File
Parameter Group
Remarks
Drx
drx
DRX switch
This parameter must be customized in the template.
DrxParaGroup
DrxParaGroup
Local cell ID, DRX parameter group ID, Enter DRX Switch
These parameters must be customized in the template.
Scenario 2: Setting DRX Parameters for Special UEs
MO
Sheet in the Summary Data File
Parameter Group
Remarks
Drx
drx
DRX switch
This parameter must be customized in the template.
DrxParaGroup
DrxParaGroup
Local cell ID, DRX parameter group ID, Enter DRX Switch
These parameters must be customized in the template.
SpidCfg
SpidCfg
Spid, Drx status
These parameters must be customized in the template.
Scenario 3: Setting DRX Parameters for ANR Measurements
MO
Sheet in the Summary Data File
Parameter Group
Remarks
Drx
drx
Long DRX Cycle for ANR, Long DRX Cycle for Inter-RAT ANR
These parameters must be customized in the template.
NOTE:
For details about ANR measurements, see ANR Management Feature Parameter Description.

Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows:
  1. Choose CME > Advanced > Customize Summary Data File from the main menu of an M2000 client, or choose Advanced > Customize Summary Data File from the main menu of a CME client, to customize a summary data file for batch reconfiguration.
    NOTE:
    For context-sensitive help on a current task in the client, press F1.
  2. Choose CME > LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the CME client, 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 listed in "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs" and close the file.
  4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application> Import Data > Import Base Station Bulk Configuration Data from the main menu of the CME client, to import the summary data file into the CME.
  5. Choose CME > Planned Area > Export Incremental Scripts from the main menu of the M2000 client, or choose Area Management > Planned Area > Export Incremental Scripts from the main menu of the CME client, to export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:
  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.
    Figure 8-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 (M2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts.

Using MML Commands

Scenario 1: Setting DRX Parameters for Common UEs
  1. Run the MOD DRX command with DRX switch set to ON(On).
  2. Run the MOD DRXPARAGROUP command to configure a DRX parameter group. In this step, set Local cell ID and DRX parameter group ID as required and set Enter DRX Switch to ON(On).
NOTE:
If the long DRX cycle is 80 ms or longer, run the MOD TATIMER command with TimeAlignmentTimer set to SF10240.
Scenario 2: Setting DRX Parameters for Special UEs
  1. Run the ADD SPIDCFG command to add an SPID. In this step, set Spid and Drx status as required.
  2. Run the MOD DRX command with DRX switch set to ON(On).
  3. Run the MOD DRXPARAGROUP command to configure a DRX parameter group. In this step, set Local cell ID and DRX parameter group ID as required and set Enter DRX Switch to ON(On).
Scenario 3: Setting DRX Parameters for ANR Measurements
Run the MOD DRX command to configure DRX parameters for ANR measurements. In this step, set Long DRX Cycle for ANR and Long DRX Cycle for Inter-RAT ANR as required.

8.4.5 Activation Observation

Scenario 1: Verifying DRX for Common UEs
Prerequisites: The UE supports DRX.
The activation observation procedure is as follows:
  1. Run the MOD DRX command with DRX switch set to ON(On).
  2. Run the LST CELLSTANDARDQCI command to query the ID of a DRX parameter group. In this step, set Local cell ID and QoS Class Indication as required.
  3. Run the LST DRXPARAGROUP command to query the settings of the DRX parameter group. In this step, set DRX parameter group ID to the value queried in Step 2.
    • If the value of Enter DRX Switch is On in the command output, DRX has been activated for bearers with the specified QCI.
    • If the value of Enter DRX Switch is Off in the command output, run the MOD DRXPARAGROUP command with Enter DRX Switch set to ON(On).
  4. Have the UE access the network and maintain low traffic in the UL and DL. Then, check the RRC Connection Reconfiguration message (displayed as RRC_CONN_RECFG on the tracing client) on the Uu interface.
    If the message contains the DRX parameters shown in Figure 8-2, the UE has entered DRX mode.
    Figure 8-2 RRC Connection Reconfiguration message (1)
    NOTE:
    Due to the limitation of the CQI and SRS, the configured values for the OnDurationTimer and LongDrxCycle parameters are inconsistent with the values delivered by the eNodeB.
Scenario 2: Verifying DRX for Special UEs
Prerequisites: An SPID has been set on the EPC for the international mobile subscriber identity (IMSI) of a UE, and the UE supports DRX.
The activation observation procedure is as follows:
  1. Run the ADD SPIDCFG command to add the SPID configuration for the eNodeB.
  2. Run the MOD DRX command with DRX switch set to ON(On) to activate DRX.
  3. Have the UE access the network and maintain low traffic in the UL and DL. Then, check the RRC Connection Reconfiguration message (displayed as RRC_CONN_RECFG on the tracing client) on the Uu interface.
    If the message contains the RFSP-specific DRX parameters shown in Figure 8-3, the UE has entered DRX mode.
    Figure 8-3 RRC Connection Reconfiguration message (2)
Scenario 3: Verifying DRX for Intra-RAT ANR Measurements in a Long DRX Cycle
Prerequisites: The ANR algorithm is enabled on the eNodeB.
The activation observation procedure is as follows:
  1. Run the MOD DRX command with Long DRX Cycle for ANR set to SF512(512 subframes).
  2. Run the MOD ENODEBALGOSWITCH command to activate ANR measurement. In this step, select both the IntraRatEventAnrSwitch and IntraRatFastAnrSwitch check boxes under the ANR algorithm switch parameter.
  3. Have the UE access the network and maintain low traffic in the UL and DL. Then, check the RRC Connection Reconfiguration message (displayed as RRC_CONN_RECFG on the tracing client) on the Uu interface.
    If the message contains the ANR-related DRX parameters shown in Figure 8-4, the UE has entered DRX mode for ANR measurement.
    Figure 8-4 RRC Connection Reconfiguration message (3)

8.4.6 Deactivation

Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in 8.4.4 Activation. In the procedure, modify parameters according to the following table.
MO
Sheet in the Summary Data File
Parameter Group
Remarks
Drx
drx
DRX switch
This parameter must be customized in the template.

Using the CME to Perform Single Configuration

On the CME, set parameters according to the preceding table. For detailed instructions, see 8.4.4 Activation for feature activation.

Using MML Commands

For either a common UE or special UE, run the MOD DRX command with DRX switch set to OFF(Off) to deactivate DRX.

8.4.7 MML Command Examples

NOTICE:
The parameter settings in the following commands are used for reference only. Set the parameters based on network requirements.
  • Enabling DRX
//To turn on the DRX switch, run the following command:
MOD DRX: DrxAlgSwitch=ON;
//To add an SPID, run the following command:
ADD SPIDCFG: Spid=0, DrxStatus=FALSE, RatFreqPriorityInd=NOT_CFG;
//To configure a DRX parameter group, run the following command:
MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=3, EnterDrxSwitch=ON;
//To configure DRX parameters for ANR measurements, run the following command:
MOD DRX: LongDrxCycleForAnr=SF320, LongDRXCycleforIRatAnr=SF1280;
  • Disabling DRX
//To turn off the DRX switch, run the following command:
MOD DRX: DrxAlgSwitch=OFF;

8.5 Performance Monitoring

After DRX in RRC_CONNECTED mode is enabled, monitor the following counters:
  • L.Cdrx.Enter.Num and L.Cdrx.Exit.Num, which count the number of times a UE enters and exits DRX mode, respectively.
  • L.Traffic.User.Cdrx.Avg, which counts the average number of UEs in DRX mode.
  • L.Cdrx.Active.TtiNum and L.Cdrx.Sleep.TtiNum, which monitor the UE power saving performance.
  • L.Voip.Cdrx.Active.TtiNum and L.Voip.Cdrx.Sleep.TtiNum, which monitor the power saving performance of the UEs while they are performing VoIP services.
  • L.Signal.Num.DRX.Reconfig, which counts the number of signaling messages increased due to DRX in RRC_CONNECTED mode.
  • Handover-related counters that monitor the handover performance of UEs in DRX mode and the proportion of UEs in DRX mode during handovers. For details about these counters, see 12 Counters.
DRX in RRC_CONNECTED mode may affect service performance in the network. This can be monitored by checking the counters related to RB usage or service drop rate.

8.6 Parameter Optimization

Configuring the Conditions for Entering and Exiting DRX Mode

  • Only UE traffic measurement
    • The UE enters DRX mode when traffic is light.
    • The UE exits DRX mode when traffic is heavy.
  • UE traffic measurement and power saving measurement
    • The UE enters DRX mode when traffic is light and the active time is short.
    • The UE exits DRX mode when traffic is heavy or the active time is long.
The UE traffic measurement and power saving measurement periods, traffic thresholds, and active time thresholds can be specified by setting the parameters in the CELLDRXPARA MOs. In TDD mode, the traffic thresholds for triggering DRX mode entry and exit are separately set for the UL and DL.
Set the cell-level parameters in CellDrxPara MOs according to 8.4.2 Data Preparation.
Scenario 1: Optimizing DRX Parameters for Common UEs
For common UEs, the DRX parameters are mapped to the QCIs of bearers. Users can configure the mappings between DRX parameter groups and QCIs to specify DRX parameters for a bearer. In addition, the power-saving performance of a QCI can be enhanced by configuring the parameters in the mapped DRX parameter group.
  • Set the parameters in DrxParaGroup MOs to configure DRX parameter groups according to 8.4.2 Data Preparation.
  • Set the parameters in CELLSTANDARDQCI MOs to map parameter groups to standardized QCIs in cells according to the following table.
    Parameter Name
    Parameter ID
    Setting Notes
    Local cell ID
    This parameter specifies the local ID of a cell. It uniquely identifies a cell within an eNodeB.
    QoS Class Indication
    This parameter specifies the QCI for an EPS bearer. Different QCIs represent different QoS specifications. Set this parameter to the rquired QCI.
    DRX parameter group ID
    This parameter specifies a DRX parameter group.
  • Set the parameters in CELLEXTENDEDQCI MOs to map parameter groups to extended QCIs in cells according to the following table.
Parameter Name
Parameter ID
Setting Notes
Extended QCI
Set this parameter if DRX parameters are required for an extended QCI.
Local cell ID
This parameter specifies the local ID of a cell. It uniquely identifies a cell within an eNodeB.
DRX parameter group ID
This parameter specifies a DRX parameter group.
  • Table 8-1 lists the recommended values for DRX parameters for a common UE. Subframe (SF) is the unit for timers. PSF stands for PDCCH subframe.
Table 8-1 Recommended values for the DRX parameters mapped to each QCI
QCI
EnterDRXSwitch
SupportShortDrx
LongDRXCycle (SF)
OnDurationTimer (PSF)
DRXInactivityTimer (PSF)
ShortDRXCycle (SF)
DRXShortCycleTimer
1
ON
UU_DISABLE
20
See Table 8-2.
See Table 8-3.
N/A
N/A
2
OFF
UU_DISABLE
N/A
N/A
N/A
N/A
N/A
3
OFF
UU_DISABLE
N/A
N/A
N/A
N/A
N/A
4
ON
UU_ENABLE
20
See Table 8-2.
See Table 8-3.
5
2
5
ON
UU_DISABLE
20
See Table 8-2.
See Table 8-3.
N/A
N/A
6
ON
UU_ENABLE
40
See Table 8-2.
See Table 8-3.
5
8
7
ON
UU_ENABLE
20
See Table 8-2.
See Table 8-3.
5
2
8
ON
UU_ENABLE
40
See Table 8-2.
See Table 8-3.
5
8
9
ON
UU_ENABLE
40
See Table 8-2.
See Table 8-3.
5
8
Table 8-2 Value of OnDurationTimer in TDD mode
UL-DL Subframe Configuration
OnDurationTimer (QCI = 1) (PSF)
OnDurationTimer (QCI = 4) (PSF)
OnDurationTimer (QCI = 5) (PSF)
OnDurationTimer (QCI = 6) (PSF)
OnDurationTimer (QCI = 7) (PSF)
OnDurationTimer (QCI = 8) (PSF)
OnDurationTimer (QCI = 9) (PSF)
TDD: UL-DL subframe configuration 0
4
2
4
2
2
2
2
TDD: UL-DL subframe configuration 1
6
2
6
2
2
2
2
TDD: UL-DL subframe configuration 2
8
4
8
4
4
4
4
TDD: UL-DL subframe configuration 3
6
4
6
4
4
4
4
TDD: UL-DL subframe configuration 4
8
4
8
4
4
4
4
TDD: UL-DL subframe configuration 5
8
4
8
4
4
4
4
TDD: UL-DL subframe configuration 6
5
2
5
2
2
2
2
Table 8-3 Value of DRXInactivityTimer in TDD mode
UL-DL Subframe Configuration
DRXInactivityTimer (QCI = 1) (PSF)
DRXInactivityTimer (QCI = 4) (PSF)
DRXInactivityTimer (QCI = 5) (PSF)
DRXInactivityTimer (QCI = 6) (PSF)
DRXInactivityTimer (QCI = 7) (PSF)
DRXInactivityTimer (QCI = 8) (PSF)
DRXInactivityTimer (QCI = 9) (PSF)
TDD: UL-DL subframe configuration 0
3
4
3
3
4
3
3
TDD: UL-DL subframe configuration 1
3
4
3
3
4
3
3
TDD: UL-DL subframe configuration 2
5
5
5
5
5
5
5
TDD: UL-DL subframe configuration 3
6
6
6
6
6
6
6
TDD: UL-DL subframe configuration 4
8
8
8
8
8
8
8
TDD: UL-DL subframe configuration 5
10
10
10
10
10
10
10
TDD: UL-DL subframe configuration 6
3
4
3
3
4
3
3
Scenario 2: Optimizing DRX Parameters for Special UEs
The DRX parameters are not mapped to the QCIs of services running on a special UE. Therefore, all special UEs share one group of DRX parameters.
Set the following parameters in DRX MOs:
For details, see 8.4.2 Data Preparation.
Table 8-4 Value of OnDurationTimerSpecial in TDD mode
UL-DL Subframe Configuration
OnDurationTimerSpecial
0
PSF2
1
PSF2
2
PSF3
3
PSF2
4
PSF3
5
PSF3
6
PSF2
Table 8-5 Value of DRXInactivityTimerSpecial in TDD mode
UL-DL Subframe Configuration
OnDurationTimerSpecial
0
PSF3
1
PSF3
2
PSF4
3
PSF3
4
PSF4
5
PSF4
6
PSF3
Scenario 3: Optimizing DRX Parameters for ANR Measurements in a Long DRX Cycle for Special UEs
Modify the DRX parameters in DRX MOs according to the following table.
Parameter Name
Parameter ID
Setting Notes
Long DRX Cycle for Inter-RAT ANR
This parameter specifies the long DRX cycle for inter-RAT ANR. If inter-RAT ANR is enabled, this parameter takes effect regardless of whether DRX is enabled.
Long DRX Cycle for ANR
This parameter specifies the long DRX cycle for intra-RAT ANR. If intra-RAT ANR is enabled, this parameter takes effect regardless of whether DRX is enabled.

8.7 Troubleshooting

Fault Description

A UE cannot enter DRX mode after accessing a network.

Fault Handling

  1. Run the LST DRX command to check the value of DRX switch shown in Figure 8-5 is On.
    • If the value is Off, turn on the DRX switch.
    • If the value is On, go to 2.
    Figure 8-5 LST DRX command output
  2. Check whether high-traffic services are running on the UE.
    • If high-traffic services are running on the UE, the UE does not enter DRX mode. This is normal.
    • If only low-traffic services (such as ping operations and VoIP services) are running on the UE, run the LST CELLDRXPARA command to check the values of TddEnterDrxThdUl and TddEnterDrxThdDl. Figure 8-6 shows the command output.
      • If the values are incorrect, restore the default values.
      • If the values are correct, go to 3.
        Figure 8-6 LST CELLDRXPARA command output
  3. Check whether the services of multiple QCIs are running on the UE. If they are, run the LST CELLSTANDARDQCI command to query the IDs of the DRX parameter groups mapped to the QCIs. Figure 8-7 shows the command output.
    Figure 8-7 LST CELLSTANDARDQCI command output
  4. Run the LST DRXPARAGROUP command to query the values of EnterDrxSwitch in all the DRX parameter groups.
    • If the value of Enter DRX Switch is Off in a DRX parameter group, turn on this switch or set up another bearer on the UE to ensure that all bearers on the UE support DRX.
    • If the values of Enter DRX Switch are On in all the DRX parameter groups, go to 5.
  5. If the fault persists, contact Huawei technical support.

9 Engineering Guidelines for Dynamic DRX

This chapter provides engineering guidelines for dynamic DRX.

9.1 When to Use Dynamic DRX

For services using heartbeat packets, UEs in dynamic DRX mode are as efficient at saving power as in RRC_IDLE mode and reduces the likelihood of signaling storms when UEs frequently switch between RRC_CONNECTED and RRC_IDLE modes.
Dynamic DRX is recommended in the following scenarios:
  • Operators require UEs to save power and allow DRX-induced signaling overhead.
  • Operators want to reduce the likelihood of signaling storms when UEs frequently switch between RRC_CONNECTED and RRC_IDLE modes.

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 the following table.
Feature ID
Feature Name
License Control Item
NE
Sales Unit
TDLOFD-00110501
Dynamic DRX
Dynamic DRX(per Cell)(TDD)
eNodeB
per Cell

9.4.2 Data Preparation

The following table describes the parameters that must be set in CELLALGOSWITCH MOs to configure cell-level DRX parameters.
Parameter Name
Parameter ID
Setting Notes
Data Source
Local cell ID
Set this parameter as required.
Network plan (negotiation not required)
Dynamic DRX switch
This parameter specifies whether to enable dynamic DRX.
  • When this switch is turned on, the UEs that access the network can use dynamic DRX.
  • When this switch is turned off, the UEs that access the network cannot use dynamic DRX.
Select the DynamicDrxSwitch(DynDrxSwitch) check box under this parameter when dynamic DRX is required.
Network plan (negotiation not required)
The following table describes the parameters that must be set in the RRCCONNSTATETIMER MO to configure UE timers.
Parameter Name
Parameter ID
Setting Notes
Data Source
UE Inactivity Timer Dynamic DRX
This parameter specifies the length of the UE inactivity timer when dynamic DRX is enabled. If the eNodeB detects that a UE has neither received nor sent data for a duration exceeding the value of this parameter, the eNodeB releases the RRC connection for this UE. If this parameter is set to a large value, the amount of signaling is reduced but UE power consumption increases.
  • When UE power saving is required, use the default value of this parameter.
  • When signaling reduction is required, increase the value of this parameter.
Network plan (negotiation not required)
Uplink Sync Timer Dynamic DRX
This parameter specifies the length of the uplink synchronization timer for UEs when dynamic DRX is enabled. When this timer expires, the eNodeB does not send a Timing Advance Command message to UEs. Set this parameter to a value smaller than the value of UeInactivityTimerDynDrx.
Network plan (negotiation not required)
The following table describes the parameters that must be set in CELLDRXPARA MOs to configure cell-level DRX parameters.
Parameter Name
Parameter ID
Setting Notes
Data Source
UnSync Long DRX Cycle
This parameter specifies the length of the long DRX cycle for UEs in the UL out-of-synchronization state.
Network plan (negotiation not required)
Onduration Timer Unsync
This parameter specifies the length of the On Duration Timer for UEs in the UL out-of-synchronization state.
Network plan (negotiation not required)
DRX Inactivity Timer Unsync
This parameter specifies the length of the DRX Inactivity Timer for UEs in the UL out-of-synchronization state.
Network plan (negotiation not required)

9.4.5 Activation

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of the parameters listed in Table 9-1 in a summary data file, which also contains other data for the new eNodeBs to be deployed. Then, import the summary data file into the Configuration Management Express (CME) for batch configuration. For detailed instructions, see section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:
  • The MOs in Table 9-1 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-1 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 9-1 Parameters for dynamic DRX
MO
Sheet in the Summary Data File
Parameter Group
Remarks
CellAlgoSwitch
CellAlgoSwitch
Local cell ID, Dynamic DRX switch
User-defined sheet

Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows:
  1. Choose CME > Advanced > Customize Summary Data File from the main menu of an M2000 client, or choose Advanced > Customize Summary Data File from the main menu of a CME client, to customize a summary data file for batch reconfiguration.
    NOTE:
    For context-sensitive help on a current task in the client, press F1.
  2. Choose CME > LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the CME client, 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 listed in "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs" and close the file.
  4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application> Import Data > Import Base Station Bulk Configuration Data from the main menu of the CME client, to import the summary data file into the CME.
  5. Choose CME > Planned Area > Export Incremental Scripts from the main menu of the M2000 client, or choose Area Management > Planned Area > Export Incremental Scripts from the main menu of the CME client, to export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:
  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 (M2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts.

Using MML Commands

Run the MOD CELLALGOSWITCH command with the DynamicDrxSwitch(DynDrxSwitch) check box selected under the Dynamic DRX switch parameter to activate dynamic DRX.

9.4.6 Activation Observation

The activation observation procedure is as follows:
  1. Run the LST CELLSTANDARDQCI command to query the ID of a DRX parameter group. In this step, set Local cell ID and QoS Class Indication as required.
  2. Run the LST DRXPARAGROUP command to query the settings of the DRX parameter group. In this step, set DrxParaGroupId to the value queried in Step 1.
    In the command output:
    • If the value of Enter DRX Switch is On, DRX has been activated for bearers with the specified QCI.
    • If the value of Enter DRX Switch is Off, run the MOD DRXPARAGROUP command with Enter DRX Switch set to ON(On).
  3. Run the LST CELLALGOSWITCH command with Local cell ID specified to check the setting of the dynamic DRX switch.
    In the command output:
    • If the value of Dynamic DRX switch is DynDrxSwitch:On, dynamic DRX has been activated for the cell.
    • If the value of Dynamic DRX switch is DynDrxSwitch:Off, run the MOD CELLALGOSWITCH command with the DynamicDrxSwitch(DynDrxSwitch) check box selected under the Dynamic DRX switch parameter to activate dynamic DRX.
  4. Have the UE access the network and maintain low traffic in the UL and DL.
    1. Check the RRC Connection Reconfiguration message (displayed as RRC_CONN_RECFG on the tracing client) on the Uu interface.
      If the message contains the DRX parameters shown inFigure 9-2, the UE has entered DRX mode.
    2. Check the value of the longDRX-CycleStartOffset field in the message.
      If the value of this field differs from the value of Long DRX Cycle (default value: SF40(40 subframes)), contact Huawei technical support.
    Figure 9-2 RRC Connection Reconfiguration message (1)
  5. Stop services. After about 20s, check the RRC Connection Reconfiguration message (displayed as RRC_CONN_RECFG on the tracing client) on the Uu interface. If the message contains the DRX parameters shown in Figure 9-3 and the value of the longDRX-CycleStartOffset field is sf1280, dynamic DRX has been activated and the UE entered the UL out-of-synchronization state.
    Figure 9-3 RRC Connection Reconfiguration message (2)

9.4.8 Deactivation

Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 9-2.
Table 9-2 Parameters for dynamic DRX
MO
Sheet in the Summary Data File
Parameter Group
Remarks
CellAlgoSwitch
CellAlgoSwitch
Local cell ID, Dynamic DRX switch
User-defined sheet

Using the CME to Perform Single Configuration

On the CME, set parameters according to Table 9-2. For detailed instructions, see "Using the CME to Perform Single Configuration" in 9.4.5 Activation for feature activation.

Using MML Commands

Run the MOD CELLALGOSWITCH command with the DynamicDrxSwitch(DynDrxSwitch) check box cleared under the Dynamic DRX switch parameter to deactivate dynamic DRX.

9.4.9 MML Command Examples

NOTICE:
The parameter settings in the following commands are used for reference only. Set the parameters based on network requirements.
//To turn on the dynamic DRX switch, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0, DrxAlgoSwitch=DynamicDrxSwitch-1;
//To turn off the dynamic DRX switch, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0, DrxAlgoSwitch=DynamicDrxSwitch-0;

9.5 Performance Monitoring

After dynamic DRX is enabled, monitor the following counters:
  • L.Cdrx.Active.TtiNum and L.Cdrx.Sleep.TtiNum, which monitor the UE power saving performance.
  • L.Voip.Cdrx.Active.TtiNum and L.Voip.Cdrx.Sleep.TtiNum, which monitor the power saving performance of the UEs while they are performing VoIP services.
  • L.Signal.Num.DRX.Reconfig and L.Signal.Num.Uu, which count the number of signaling messages decreased on the Uu interface.
  • L.E-RAB.Release.Unsyn, which counts the number of times the eNodeB initiates RRC connection release when UEs are in the UL out-of-synchronization state.
  • L.E-RAB.Num.Syn2Unsyn, L.RRC.StateTrans.Syn2Unsyn, and L.RRC.StateTrans.Unsyn2Syn, which count the number of times UEs transition between the synchronization and UL out-of-synchronization states.
  • Handover-related counters that monitor the handover performance of UEs in DRX mode and the proportion of UEs in DRX mode during handovers. For details about these counters, see 12 Counters.
In addition, dynamic DRX may affect the key performance indicators (KPIs) of the network. This can be monitored by checking the counters related to RB usage or service drop rate.

9.6 Parameter Optimization

To meet both power saving and signaling control requirements, set the UE timers in the RRCCONNSTATETIMER MO. For details, see 9.4.2 Data Preparation.
To improve the DRX performance for UEs in the UL out-of-synchronization state, set the cell-level DRX parameters in CELLDRXPARA MOs. For details, see 9.4.2 Data Preparation.

9.7 Troubleshooting

Fault Description

If a UE does not perform any data services after accessing the network, dynamic DRX does not take effect.

Fault Handling

  1. Run the LST CELLALGOSWITCH command to check the setting of the dynamic DRX switch. If the value of Dynamic DRX switch is DynDrxSwitch:Off, run the MOD CELLALGOSWITCH command with the DynamicDrxSwitch(DynDrxSwitch) check box selected under the Dynamic DRX switch parameter to activate dynamic DRX.
  2. Check whether the services of multiple QCIs are running on the UE. If they are, run the LST CELLSTANDARDQCI command to query the IDs of the DRX parameter groups mapped to the QCIs. Figure 9-4 shows the command output.
    Figure 9-4 LST CELLSTANDARDQCI command output
  3. Run the LST DRXPARAGROUP command to query the values of EnterDrxSwitch in all the DRX parameter groups.
    • If the value of Enter DRX Switch is Off in a DRX parameter group, turn on this switch or set up another bearer on the UE to ensure that all bearers on the UE support DRX.
    • If the values of Enter DRX Switch are On in all the DRX parameter groups, go to Step 4.
  4. If the fault persists, contact Huawei technical support.

10 Engineering Guidelines for High-Mobility-Triggered Idle Mode


10.1 When to Use High-Mobility-Triggered Idle Mode

In high-mobility scenarios, such as on a highway, most of UEs served by an eNodeB are smartphones, the UEs remain online constantly, and a large number of handovers occur. To reduce UE handovers and prevent signaling bursts due to frequent handovers, activate high-mobility-triggered idle mode.

10.2 Required Information

Before you activate high-mobility-triggered idle mode, collect the following information:
  1. Frequencies, coverage, and configuration of LTE cells.
  2. Whether eNodeBs support high-mobility-triggered idle mode.
  3. Frequency of UE handovers in the live network and UE online duration.

10.3 Planning

RF Planning

On live networks without coverage problems, high-mobility-triggered idle mode reduces high-mobility UE handovers to prevent signaling bursts. Therefore, the networks must meet the following coverage requirements:
  • No coverage holes
  • No cross-cell coverage
  • No pilot pollution
  • No path loss imbalance between the UL and DL

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 the following table.
Feature ID
Feature Name
License Control Item
NE
Sales Unit
TDLOFD-00110502
High-Mobility-Triggered Idle Mode
Dynamic DRX(per Cell)(TDD)
eNodeB
per Cell

Other Features

You are advised to enable TDLOFD-00110501 Dynamic DRX. before enabling the high-mobility-triggered idle mode feature.

10.4.2 Data Preparation

Required Data

The following table describes the parameters that must be set in CellAlgoSwitch MOs to configure cell-level DRX parameters.
Parameter Name
Parameter ID
Setting Notes
Data Source
Local cell ID
This parameter specifies the local ID of a cell. It uniquely identifies a cell within an eNodeB.
Network plan (negotiation not required)
High Mobility Triggered Idle Mode Switch
This parameter specifies whether to enable high-mobility-triggered idle mode. If high-mobility-triggered idle mode is required, set this parameter to ENABLE(Enable).
Network plan (negotiation not required)

10.4.5 Activation

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs

Enter the values of the parameters listed in Table 10-1 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 section "Creating eNodeBs in Batches" in the initial configuration guide for the eNodeB.
The summary data file may be a scenario-specific file provided by the CME or a customized file, depending on the following conditions:
  • The MOs in Table 10-1 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-1 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-1 Parameters for high-mobility-triggered idle mode
MO
Sheet in the Summary Data File
Parameter Group
Remarks
CellAlgoSwitch
CellAlgoSwitch
Local cell ID, High Mobility Triggered Idle Mode Switch
These parameters must be customized in the template.

Using the CME to Perform Batch Configuration for Existing eNodeBs

Batch reconfiguration using the CME is the recommended method to activate a feature on existing eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure is as follows:
  1. Choose CME > Advanced > Customize Summary Data File from the main menu of an M2000 client, or choose Advanced > Customize Summary Data File from the main menu of a CME client, to customize a summary data file for batch reconfiguration.
    NOTE:
    For context-sensitive help on a current task in the client, press F1.
  2. Choose CME > LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application > Export Data >Export Base Station Bulk Configuration Data from the main menu of the CME client, 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 listed in "Using the CME to Perform Batch Configuration for Newly Deployed eNodeBs" and close the file.
  4. Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration Data from the main menu of the M2000 client, or choose LTE Application> Import Data > Import Base Station Bulk Configuration Data from the main menu of the CME client, to import the summary data file into the CME.
  5. Choose CME > Planned Area > Export Incremental Scripts from the main menu of the M2000 client, or choose Area Management > Planned Area > Export Incremental Scripts from the main menu of the CME client, to export and activate the incremental scripts.

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB. The procedure is as follows:
  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.
    Figure 10-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 (M2000 client mode), or choose Area Management > Planned Area > Export Incremental Scripts (CME client mode), to export and activate the incremental scripts.

Using MML Commands

Run the MOD CELLALGOSWITCH command with High Mobility Triggered Idle Mode Switch set to ENABLE(Enable) to activate high-mobility-triggered idle mode.

10.4.6 Activation Observation

Check the value of the L.UECNTX.Release.HighSpeed counter. If the value is greater than 0, high-mobility-triggered idle mode has been activated.

10.4.8 Deactivation

Using the CME to Perform Batch Configuration

Batch reconfiguration using the CME is the recommended method to deactivate a feature on eNodeBs. This method reconfigures all data, except neighbor relationships, for multiple eNodeBs in a single procedure. The procedure for feature deactivation is similar to that for feature activation described in Using the CME to Perform Batch Configuration for Existing eNodeBs. In the procedure, modify parameters according to Table 10-2.
Table 10-2 Parameters for high-mobility-triggered idle mode
MO
Sheet in the Summary Data File
Parameter Group
Remarks
CellAlgoSwitch
CellAlgoSwitch
Local cell ID, High Mobility Triggered Idle Mode Switch
These parameters must be customized in the template.

Using the CME to Perform Single Configuration

On the CME, set parameters according to Table 10-2. For detailed instructions, see "Using the CME to Perform Single Configuration" in 10.4.5 Activation for feature activation.

Using MML Commands

Run the MOD CELLALGOSWITCH command with High Mobility Triggered Idle Mode Switch set to DISABLE(Disable) to deactivate high-mobility-triggered idle mode.

10.4.9 MML Command Examples

NOTICE:
The parameter settings in the following commands are used for reference only. Set the parameters based on network requirements.
//To turn on the switch for high-mobility-triggered idle mode, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0, HighMobiTrigIdleModeSwitch=ENABLE;
//To turn off the switch for high-mobility-triggered idle mode, run the following command:
MOD CELLALGOSWITCH: LocalCellId=0, HighMobiTrigIdleModeSwitch=DISABLE;

10.5 Performance Monitoring

After high-mobility-triggered idle mode is enabled, monitor and evaluate the performance of this feature as follows:
  1. Check the value of the L.UECNTX.Release.HighSpeed counter. If the value of this counter is greater than 0, this feature has been activated.
  2. Check the handover-related counters listed in the following table. If the total number of handovers significantly decreases, this feature has been activated and the signaling overhead caused by handovers is reduced.
    Counter ID
    Counter Name
    Counter Description
    1526726996
    L.HHO.IntraeNB.IntraFreq.ExecAttOut
    Number of intra-eNodeB intra-frequency outgoing handovers in a cell
    1526726999
    L.HHO.IntraeNB.InterFreq.ExecAttOut
    Number of intra-eNodeB inter-frequency outgoing handovers in a cell
    1526727002
    L.HHO.IntereNB.IntraFreq.ExecAttOut
    Number of inter-eNodeB intra-frequency outgoing handovers in a cell
    1526727005
    L.HHO.IntereNB.InterFreq.ExecAttOut
    Number of inter-eNodeB inter-frequency outgoing handovers in a cell

11 Parameters

Table 11-1 Parameter description
MO Parameter ID MML Command Feature ID Feature Name Description
CellAlgoSwitch DynDrxSwitch MOD CELLALGOSWITCH
LST CELLALGOSWITCH
None None Meaning: Indicates whether to enable the dynamic discontinuous reception (DRX) feature. If this switch is turned on, the dynamic DRX feature is applied to newly admitted UE to reduce the signaling overhead and decrease UE power consumption. If this switch is turned off, the dynamic DRX feature is not applied to newly admitted UEs. The dynamic DRX feature applies to carrier aggregation (CA) UEs only when this switch is turned on in both the PCell and SCell.
GUI Value Range: DynDrxSwitch(DynDrxSwitch)
Unit: None
Actual Value Range: DynDrxSwitch
Default Value: DynDrxSwitch:Off
RrcConnStateTimer UeInactivityTimerDynDrx MOD RRCCONNSTATETIMER
LST RRCCONNSTATETIMER
LOFD-001105 Dynamic DRX Meaning: Indicates the length of the UE inactivity timer for DRX UEs when dynamic DRX is enabled. If the eNodeB detects that a UE has neither received nor sent data for a duration exceeding the value of this parameter, the eNodeB releases the RRC connection for the UE. A large value of this parameter reduces the amount of signaling but increase UE power consumption.You are advised to set this parameter to a value greater than the value of UlSynTimerDynDrx.In power saving mode, you are advised to set this parameter significantly different to the value of the UlSynTimerDynDrx parameter, for example a gap of 10 seconds, to avoid power consumption increase due to the increase of signaling.
GUI Value Range: 10~3600
Unit: s
Actual Value Range: 10~3600
Default Value: 200
RrcConnStateTimer UlSynTimerDynDrx MOD RRCCONNSTATETIMER
LST RRCCONNSTATETIMER
LOFD-001105 Dynamic DRX Meaning: Indicates the timer used to govern the period in which the eNodeB maintains uplink synchronization for a DRX UE when dynamic DRX is enabled. After this timer expires, the eNodeB does not send Timing Advance Command to the UE. You are advised to set this parameter to a value smaller than the value of UeInactivityTimerDynDrx.In power saving mode, you are advised to set this parameter significantly different to the value of the UeInactivityTimerDynDrx parameter, for example a gap of 10 seconds, to avoid power consumption increase due to the increase of signaling.
GUI Value Range: 5~3600
Unit: s
Actual Value Range: 5~3600
Default Value: 20
CellDrxPara LongDrxCycleUnsync MOD CELLDRXPARA
LST CELLDRXPARA
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of the long DRX cycle for a UE in the unsynchronized state. Set this parameter to a value greater than the value of LongDrxCycle; otherwise, the power saving gain of the DRX for unsynchronized UEs decreases.
GUI Value Range: SF10(10 subframes), SF20(20 subframes), SF32(32 subframes), SF40(40 subframes), SF64(64 subframes), SF80(80 subframes), SF128(128 subframes), SF160(160 subframes), SF256(256 subframes), SF320(320 subframes), SF512(512 subframes), SF640(640 subframes), SF1024(1024 subframes), SF1280(1280 subframes), SF2048(2048 subframes), SF2560(2560 subframes)
Unit: subframe
Actual Value Range: SF10, SF20, SF32, SF40, SF64, SF80, SF128, SF160, SF256, SF320, SF512, SF640, SF1024, SF1280, SF2048, SF2560
Default Value: SF1280(1280 subframes)
CellDrxPara OndurationTimerUnsync MOD CELLDRXPARA
LST CELLDRXPARA
LOFD-001105 Dynamic DRX Meaning: Indicates the DRX onduration timer for UEs when the eNodeB does not maintain synchronization for UEs.
GUI Value Range: PSF1(1 PDCCH subframe), PSF2(2 PDCCH subframes), PSF3(3 PDCCH subframes), PSF4(4 PDCCH subframes), PSF5(5 PDCCH subframes), PSF6(6 PDCCH subframes), PSF8(8 PDCCH subframes), PSF10(10 PDCCH subframes), PSF20(20 PDCCH subframes), PSF30(30 PDCCH subframes), PSF40(40 PDCCH subframes), PSF50(50 PDCCH subframes), PSF60(60 PDCCH subframes), PSF80(80 PDCCH subframes), PSF100(100 PDCCH subframes), PSF200(200 PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5, PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50, PSF60, PSF80, PSF100, PSF200
Default Value: PSF5(5 PDCCH subframes)
CellDrxPara DrxInactivityTimerUnsync MOD CELLDRXPARA
LST CELLDRXPARA
LOFD-001105 Dynamic DRX Meaning: Indicates the DRX inactivity timer for UEs when the eNodeB does not maintain synchronization for UEs.
GUI Value Range: PSF200(200 PDCCH subframes), PSF300(300 PDCCH subframes), PSF500(500 PDCCH subframes), PSF750(750 PDCCH subframes), PSF1280(1280 PDCCH subframes), PSF1920(1920 PDCCH subframes), PSF2560(2560 PDCCH subframes)
Unit: subframe
Actual Value Range: PSF200, PSF300, PSF500, PSF750, PSF1280, PSF1920, PSF2560
Default Value: PSF1280(1280 PDCCH subframes)
CellAlgoSwitch HighMobiTrigIdleModeSwitch MOD CELLALGOSWITCH
LST CELLALGOSWITCH
None None Meaning: Indicates whether to enable the high-mobility-triggered-idle switch. When this parameter is set to ENABLE, UEs in high mobility are released and enter the idle mode, and therefore the signaling impact on the network caused by frequent handovers are reduced. When this parameter is set to DISABLED, UEs in high mobility are not released.
GUI Value Range: DISABLE(Disable), ENABLE(Enable)
Unit: None
Actual Value Range: DISABLE, ENABLE
Default Value: DISABLE(Disable)
DrxParaGroup OnDurationTimer ADD DRXPARAGROUP
MOD DRXPARAGROUP
LST DRXPARAGROUP
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of the On Duration Timer. 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.
GUI Value Range: PSF1(1 PDCCH subframe), PSF2(2 PDCCH subframes), PSF3(3 PDCCH subframes), PSF4(4 PDCCH subframes), PSF5(5 PDCCH subframes), PSF6(6 PDCCH subframes), PSF8(8 PDCCH subframes), PSF10(10 PDCCH subframes), PSF20(20 PDCCH subframes), PSF30(30 PDCCH subframes), PSF40(40 PDCCH subframes), PSF50(50 PDCCH subframes), PSF60(60 PDCCH subframes), PSF80(80 PDCCH subframes), PSF100(100 PDCCH subframes), PSF200(200 PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5, PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50, PSF60, PSF80, PSF100, PSF200
Default Value: PSF2(2 PDCCH subframes)
DrxParaGroup LongDrxCycle ADD DRXPARAGROUP
MOD DRXPARAGROUP
LST DRXPARAGROUP
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of the long DRX cycle. Because of the impact of the SRS bandwidth and TA period specified by the TimeAlignmentTimer parameter, the actual value of this parameter assigned to a UE may be less than the configured value. In addition, the configured value will be rounded down to an integral multiple of 10. Therefore, you are advised to configure this parameter to a value that is an integral multiple of 10. If users hope that the value actually assigned to a UE is equal to or greater than 80 ms, set the TimeAlignmentTimer parameter to a value equal to or greater than 10240 ms. If the TimingAdvCmdOptSwitch parameter is set to ON, it is recommended that the LongDrxCycle parameter be set to a value smaller than or equal to 320 ms. Otherwise, the uplink time alignment performance of UEs is affected. If the TimingAdvCmdOptSwitch parameter is set to ON, it is recommended that the TimeAlignmentTimer parameter be set to sf10240. A smaller value of the TimeAlignmentTimer parameter, such as sf5120, increases the probability that UEs in DRX mode become uplink asynchronized. The length of the long DRX cycle must be smaller than the length of the PDCP packet discarding timer for the corresponding QCI. Otherwise, packet loss occurs during a ping operation or low-traffic service.
GUI Value Range: SF10(10 subframes), SF20(20 subframes), SF32(32 subframes), SF40(40 subframes), SF64(64 subframes), SF80(80 subframes), SF128(128 subframes), SF160(160 subframes), SF256(256 subframes), SF320(320 subframes), SF512(512 subframes), SF640(640 subframes), SF1024(1024 subframes), SF1280(1280 subframes), SF2048(2048 subframes), SF2560(2560 subframes)
Unit: subframe
Actual Value Range: SF10, SF20, SF32, SF40, SF64, SF80, SF128, SF160, SF256, SF320, SF512, SF640, SF1024, SF1280, SF2048, SF2560
Default Value: SF40(40 subframes)
DrxParaGroup SupportShortDrx ADD DRXPARAGROUP
MOD DRXPARAGROUP
LST DRXPARAGROUP
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates whether short DRX cycles are enabled.
GUI Value Range: UU_DISABLE(Disable), UU_ENABLE(Enable)
Unit: None
Actual Value Range: UU_DISABLE, UU_ENABLE
Default Value: UU_ENABLE(Enable)
DrxParaGroup ShortDrxCycle ADD DRXPARAGROUP
MOD DRXPARAGROUP
LST DRXPARAGROUP
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of the short DRX cycle. 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 LongDrxCycle assigned to a UE may be less than the configured value because of the impact of the SRS bandwidth and TA period specified by the TimeAlignmentTimer parameter. Therefore, the actual value of ShortDrxCycle assigned to a UE may be less than the configured value.
GUI Value Range: SF2(2 subframes), SF5(5 subframes), SF8(8 subframes), SF10(10 subframes), SF16(16 subframes), SF20(20 subframes), SF32(32 subframes), SF40(40 subframes), SF64(64 subframes), SF80(80 subframes), SF128(128 subframes), SF160(160 subframes), SF256(256 subframes), SF320(320 subframes), SF512(512 subframes), SF640(640 subframes)
Unit: subframe
Actual Value Range: SF2, SF5, SF8, SF10, SF16, SF20, SF32, SF40, SF64, SF80, SF128, SF160, SF256, SF320, SF512, SF640
Default Value: SF20(20 subframes)
DrxParaGroup DrxShortCycleTimer ADD DRXPARAGROUP
MOD DRXPARAGROUP
LST DRXPARAGROUP
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of the DRX Short Cycle Timer. If this parameter is set to 1, the length of this timer is one short DRX cycle. If this parameter is set to 2, the length of this timer is two short DRX cycles. If this parameter is set to a large value, a UE for which short DRX cycles are enabled stays in short-cycle DRX for a long time. For details, see 3GPP TS 36.321 5.7.
GUI Value Range: 1~16
Unit: None
Actual Value Range: 1~16
Default Value: 1
Drx DrxAlgSwitch MOD DRX
LST DRX
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the DRX switch.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
DrxParaGroup EnterDrxSwitch ADD DRXPARAGROUP
MOD DRXPARAGROUP
LST DRXPARAGROUP
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates whether bearers to which the parameter group applies support DRX. The value ON indicates that the bearers support DRX. The value OFF indicates that the bearers do not support DRX.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellDrxPara TddEnterDrxThdUl MOD CELLDRXPARA
LST CELLDRXPARA
TDLBFD-002017 DRX Meaning: Indicates the uplink traffic volume threshold for UEs to enter DRX in the cell that operates in TDD mode. This threshold is used in the DRX algorithm. It is expressed as a proportion of the transmission time intervals (TTIs) with uplink data transmission to the total TTIs. If the traffic volume at a UE is equal to or lower than this threshold, the eNodeB decides that the UE should retain its DRX state or enter DRX.
GUI Value Range: 0~1999
Unit: per mill
Actual Value Range: 0~1999
Default Value: 300
CellDrxPara TddEnterDrxThdDl MOD CELLDRXPARA
LST CELLDRXPARA
TDLBFD-002017 DRX Meaning: Indicates the downlink traffic volume threshold for UEs to enter DRX in the cell that operates in TDD mode. This threshold is used in the DRX algorithm. It is expressed as a proportion of the transmission time intervals (TTIs) with downlink data transmission to the total TTIs. If the traffic volume at a UE is equal to or lower than this threshold, the eNodeB decides that the UE should retain its DRX state or enter DRX.
GUI Value Range: 0~1999
Unit: per mill
Actual Value Range: 0~1999
Default Value: 300
CellDrxPara TddPowerSaveMeasSwitch MOD CELLDRXPARA
LST CELLDRXPARA
TDLBFD-002017 DRX Meaning: Indicates whether DRX active-time measurement is supported in the cell that operates in TDD mode. If this parameter is set to ON, DRX active-time measurement is supported in the cell that operates in TDD mode. If this parameter is set to OFF, DRX active-time measurement is not supported in the cell that operates in TDD mode.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellDrxPara TddPowerSavingEnterDrxThd MOD CELLDRXPARA
LST CELLDRXPARA
TDLBFD-002017 DRX Meaning: Indicates the active-time measurement threshold for UEs to enter DRX in the cell that operates in TDD mode. This threshold is used in the DRX algorithm. If the measurement result of a UE is lower than this threshold, the eNodeB decides that the UE should retain its DRX state or enter DRX.
GUI Value Range: 0~1999
Unit: per mill
Actual Value Range: 0~1999
Default Value: 800
CellDrxPara TddExitDrxThdUl MOD CELLDRXPARA
LST CELLDRXPARA
TDLBFD-002017 DRX Meaning: Indicates the uplink traffic volume threshold for UEs to exit DRX in the cell that operates in TDD mode. This threshold is used in the DRX algorithm. It is expressed as a proportion of the transmission time intervals (TTIs) with uplink data transmission to the total TTIs. If the traffic volume at a UE is equal to or higher than this threshold, the eNodeB decides that the UE should retain its non-DRX state or exit DRX.
GUI Value Range: 1~2000
Unit: per mill
Actual Value Range: 1~2000
Default Value: 800
CellDrxPara TddExitDrxThdDl MOD CELLDRXPARA
LST CELLDRXPARA
TDLBFD-002017 DRX Meaning: Indicates the downlink traffic volume threshold for UEs to exit DRX in the cell that operates in TDD mode. This threshold is used in the DRX algorithm. It is expressed as a proportion of the transmission time intervals (TTIs) with downlink data transmission to the total TTIs. If the traffic volume at a UE is equal to or higher than this threshold, the eNodeB decides that the UE should retain its non-DRX state or exit DRX.
GUI Value Range: 1~2000
Unit: per mill
Actual Value Range: 1~2000
Default Value: 800
CellDrxPara TddPowerSavingExitDrxThd MOD CELLDRXPARA
LST CELLDRXPARA
TDLBFD-002017 DRX Meaning: Indicates the active-time measurement threshold for UEs to exit DRX in the cell that operates in TDD mode. This threshold is used in the DRX algorithm. If the measurement result of a UE is higher than this threshold, the eNodeB decides that the UE should retain its non-DRX state or exit DRX.
GUI Value Range: 0~1999
Unit: per mill
Actual Value Range: 0~1999
Default Value: 900
Drx LongDrxCycleSpecial MOD DRX
LST DRX
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of a long DRX cycle that is applied only to non-power-saving UEs whose subscriber profile ID for RAT/frequency priority (RFSP) indexes are contained in the RFSP index set. Because of the impact of the SRS bandwidth and TA period specified by the TimeAlignmentTimer parameter, the actual value of this parameter assigned to a UE may be less than the configured value. In addition, the configured value will be rounded down to an integral multiple of 10. Therefore, you are advised to configure this parameter to a value that is an integral multiple of 10. If users hope that the value actually assigned to a UE is equal to or greater than 80 ms, set the TimeAlignmentTimer parameter to a value equal to or greater than 10240 ms. If the TimingAdvCmdOptSwitch parameter is set to ON, it is recommended that the LongDrxCycleSpecial parameter be set to a value smaller than or equal to 320 ms. Otherwise, the uplink time alignment performance of UEs is affected. If the TimingAdvCmdOptSwitch parameter is set to ON, it is recommended that the TimeAlignmentTimer parameter be set to sf10240. A smaller value of the TimeAlignmentTimer parameter, such as sf5120, increases the probability that UEs in DRX mode become uplink asynchronized.
GUI Value Range: SF10(10 subframes), SF20(20 subframes), SF32(32 subframes), SF40(40 subframes), SF64(64 subframes), SF80(80 subframes), SF128(128 subframes), SF160(160 subframes), SF256(256 subframes), SF320(320 subframes), SF512(512 subframes), SF640(640 subframes), SF1024(1024 subframes), SF1280(1280 subframes), SF2048(2048 subframes), SF2560(2560 subframes)
Unit: subframe
Actual Value Range: SF10, SF20, SF32, SF40, SF64, SF80, SF128, SF160, SF256, SF320, SF512, SF640, SF1024, SF1280, SF2048, SF2560
Default Value: SF10(10 subframes)
Drx LongDrxCycleForAnr MOD DRX
LST DRX
LBFD-002017 DRX Meaning: Indicates the long DRX cycle for intra-RAT ANR. If intra-RAT ANR is enabled, this parameter is valid regardless of whether DRX is enabled. If a long DRX cycle is configured for ANR measurement, it is recommended that this parameter be set to a value equal to or greater than 256 ms to ensure that the UE can successfully obtain the CGI of a cell. However, if this parameter is set to a large value, the delay of obtaining the CGI is large, and therefore the system delay increases.
GUI Value Range: SF128(128 subframes), SF160(160 subframes), SF256(256 subframes), SF320(320 subframes), SF512(512 subframes), SF640(640 subframes), SF1024(1024 subframes), SF1280(1280 subframes), SF2048(2048 subframes), SF2560(2560 subframes)
Unit: subframe
Actual Value Range: SF128, SF160, SF256, SF320, SF512, SF640, SF1024, SF1280, SF2048, SF2560
Default Value: SF320(320 subframes)
Drx LongDRXCycleforIRatAnr MOD DRX
LST DRX
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the long DRX cycle for inter-RAT ANR. If inter-RAT ANR is enabled, this parameter is valid regardless of whether DRX is enabled. If there are multiple inter-RAT systems, and all of them require inter-RAT ANR measurements, it is recommended that this parameter be set to the maximum value of the long DRX cycle configured for inter-RAT ANR measurements. Otherwise, the success rate for inter-RAT ANR measurements may be affected.
GUI Value Range: SF128(128 subframes), SF160(160 subframes), SF256(256 subframes), SF320(320 subframes), SF512(512 subframes), SF640(640 subframes), SF1024(1024 subframes), SF1280(1280 subframes), SF2048(2048 subframes), SF2560(2560 subframes)
Unit: subframe
Actual Value Range: SF128, SF160, SF256, SF320, SF512, SF640, SF1024, SF1280, SF2048, SF2560
Default Value: SF1280(1280 subframes)
Drx SupportShortDrxSpecial MOD DRX
LST DRX
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates whether to enable or disable short DRX cycles for non-power-saving UEs whose RFSP indexes are contained in the RFSP index set.
GUI Value Range: UU_DISABLE(Disable), UU_ENABLE(Enable)
Unit: None
Actual Value Range: UU_DISABLE, UU_ENABLE
Default Value: UU_DISABLE(Disable)
Drx ShortDrxCycleSpecial MOD DRX
LST DRX
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of a short DRX cycle that is applied only to non-power-saving UEs whose subscriber profile ID for RAT/frequency priority (RFSP) indexes are contained in the RFSP index set. According to 3GPP specifications, the length of a long DRX cycle must be an integer multiple of that of a short DRX cycle. In addition, the actual value of LongDrxCycleSpecial assigned to a UE may be less than the configured value because of the impact of the SRS bandwidth and TA period specified by the TimeAlignmentTimer parameter. Therefore, the actual value of ShortDrxCycleSpecial assigned to a UE may be less than the configured value.
GUI Value Range: SF2(2 subframes), SF5(5 subframes), SF8(8 subframes), SF10(10 subframes), SF16(16 subframes), SF20(20 subframes), SF32(32 subframes), SF40(40 subframes), SF64(64 subframes), SF80(80 subframes), SF128(128 subframes), SF160(160 subframes), SF256(256 subframes), SF320(320 subframes), SF512(512 subframes), SF640(640 subframes)
Unit: subframe
Actual Value Range: SF2, SF5, SF8, SF10, SF16, SF20, SF32, SF40, SF64, SF80, SF128, SF160, SF256, SF320, SF512, SF640
Default Value: SF10(10 subframes)
Drx DrxShortCycleTimerSpecial MOD DRX
LST DRX
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of the DRX Short Cycle Timer that applies only to non-power-saving UEs whose RFSP indexes are contained in the RFSP index set. The length of this timer is expressed in the number of short DRX cycles. If this parameter is set to 1, the length of this timer is one short DRX cycle. If this parameter is set to 2, the length of this timer is two short DRX cycles. For details, see 3GPP TS 36.321 5.7.
GUI Value Range: 1~16
Unit: None
Actual Value Range: 1~16
Default Value: 1
Drx OnDurationTimerSpecial MOD DRX
LST DRX
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of the On Duration Timer that applies only to non-power-saving UEs whose RFSP indexes are contained in the RFSP index set. 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.
GUI Value Range: PSF1(1 PDCCH subframe), PSF2(2 PDCCH subframes), PSF3(3 PDCCH subframes), PSF4(4 PDCCH subframes), PSF5(5 PDCCH subframes), PSF6(6 PDCCH subframes), PSF8(8 PDCCH subframes), PSF10(10 PDCCH subframes), PSF20(20 PDCCH subframes), PSF30(30 PDCCH subframes), PSF40(40 PDCCH subframes), PSF50(50 PDCCH subframes), PSF60(60 PDCCH subframes), PSF80(80 PDCCH subframes), PSF100(100 PDCCH subframes), PSF200(200 PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5, PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50, PSF60, PSF80, PSF100, PSF200
Default Value: PSF5(5 PDCCH subframes)
DrxParaGroup DrxInactivityTimer ADD DRXPARAGROUP
MOD DRXPARAGROUP
LST DRXPARAGROUP
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of the DRX Inactivity Timer.
GUI Value Range: PSF1(1 PDCCH subframe), PSF2(2 PDCCH subframes), PSF3(3 PDCCH subframes), PSF4(4 PDCCH subframes), PSF5(5 PDCCH subframes), PSF6(6 PDCCH subframes), PSF8(8 PDCCH subframes), PSF10(10 PDCCH subframes), PSF20(20 PDCCH subframes), PSF30(30 PDCCH subframes), PSF40(40 PDCCH subframes), PSF50(50 PDCCH subframes), PSF60(60 PDCCH subframes), PSF80(80 PDCCH subframes), PSF100(100 PDCCH subframes), PSF200(200 PDCCH subframes), PSF300(300 PDCCH subframes), PSF500(500 PDCCH subframes), PSF750(750 PDCCH subframes), PSF1280(1280 PDCCH subframes), PSF1920(1920 PDCCH subframes), PSF2560(2560 PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5, PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50, PSF60, PSF80, PSF100, PSF200, PSF300, PSF500, PSF750, PSF1280, PSF1920, PSF2560
Default Value: PSF80(80 PDCCH subframes)
Drx DrxInactivityTimerSpecial MOD DRX
LST DRX
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of the DRX Inactivity Timer that applies only to non-power-saving UEs whose RFSP indexes are contained in the RFSP index set. For details about this timer, see 3GPP TS 36.321.
GUI Value Range: PSF1(1 PDCCH subframe), PSF2(2 PDCCH subframes), PSF3(3 PDCCH subframes), PSF4(4 PDCCH subframes), PSF5(5 PDCCH subframes), PSF6(6 PDCCH subframes), PSF8(8 PDCCH subframes), PSF10(10 PDCCH subframes), PSF20(20 PDCCH subframes), PSF30(30 PDCCH subframes), PSF40(40 PDCCH subframes), PSF50(50 PDCCH subframes), PSF60(60 PDCCH subframes), PSF80(80 PDCCH subframes), PSF100(100 PDCCH subframes), PSF200(200 PDCCH subframes), PSF300(300 PDCCH subframes), PSF500(500 PDCCH subframes), PSF750(750 PDCCH subframes), PSF1280(1280 PDCCH subframes), PSF1920(1920 PDCCH subframes), PSF2560(2560 PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF3, PSF4, PSF5, PSF6, PSF8, PSF10, PSF20, PSF30, PSF40, PSF50, PSF60, PSF80, PSF100, PSF200, PSF300, PSF500, PSF750, PSF1280, PSF1920, PSF2560
Default Value: PSF10(10 PDCCH subframes)
DrxParaGroup DrxReTxTimer ADD DRXPARAGROUP
MOD DRXPARAGROUP
LST DRXPARAGROUP
LBFD-002017 / TDLBFD-002017
LBFD-002005 / TDLBFD-002005
DRX
DL Asynchronous HARQ
Meaning: Indicates the length of the DRX Retransmission Timer.
GUI Value Range: PSF1(1 PDCCH subframes), PSF2(2 PDCCH subframes), PSF4(4 PDCCH subframes), PSF6(6 PDCCH subframes), PSF8(8 PDCCH subframes), PSF16(16 PDCCH subframes), PSF24(24 PDCCH subframes), PSF33(33 PDCCH subframes)
Unit: subframe
Actual Value Range: PSF1, PSF2, PSF4, PSF6, PSF8, PSF16, PSF24, PSF33
Default Value: PSF8(8 PDCCH subframes)
SpidCfg Spid ADD SPIDCFG
LST SPIDCFG
MOD SPIDCFG
RMV SPIDCFG
LOFD-001032 / TDLOFD-001032
LOFD-001044 / TDLOFD-001044
LOFD-001045 / TDLOFD-001045
LOFD-001054 / TDLOFD-001054
LOFD-00105401 / TDLOFD-00105401
LOFD-001059 / TDLOFD-001059
Intra-LTE Load Balancing
Inter-RAT Load Sharing to UTRAN
Inter-RAT Load Sharing to GERAN
Flexible User Steering
Camp & Handover Based on SPID
UL Pre-allocation Based on SPID
Meaning: Indicates the subscriber profile ID (SPID).
GUI Value Range: 1~256
Unit: None
Actual Value Range: 1~256
Default Value: None
SpidCfg DrxStatus ADD SPIDCFG
MOD SPIDCFG
LST SPIDCFG
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates whether to use normal or special DRX. If this parameter is set to TRUE, ordinary DRX parameters are applied to UEs with the SPID. If this parameter is set to FALSE, special DRX parameters are applied to UEs with the SPID.
GUI Value Range: FALSE(FALSE), TRUE(TRUE)
Unit: None
Actual Value Range: FALSE, TRUE
Default Value: FALSE(FALSE)
TimeAlignmentTimer TimingAdvCmdOptSwitch MOD TATIMER
LST TATIMER
LBFD-001001 / TDLBFD-001001 3GPP R8 Specifications Meaning: Indicates whether optimization of the mechanism for delivering the uplink time alignment command takes effect. If the optimization takes effect, the number of unnecessary uplink time alignment commands delivered to motionless or low-mobility UEs can be reduced to save air interface resources and reduce power consumption of UEs in DRX mode. This ensures the uplink time alignment performance if the length of the uplink time alignment timer is set to a large value. If this parameter is set to ON, it is recommended that the TimeAlignmentTimer parameter be set to SF10240. A smaller value of the TimeAlignmentTimer parameter, such as SF5120, leads to a higher probability of becoming out-of-synchronization in the uplink for UEs in DRX mode. If this parameter is set to ON, it is recommended that the LongDrxCycle parameter be smaller than or equal to SF320. Otherwise, the uplink time alignment performance of UEs in DRX mode is affected.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellDrxPara LocalCellId LST CELLDRXPARA
MOD CELLDRXPARA
None None Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS.
GUI Value Range: 0~17
Unit: None
Actual Value Range: 0~17
Default Value: None
CellDrxPara DataAmountStatTimer MOD CELLDRXPARA
LST CELLDRXPARA
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the length of the UE traffic measurement period. The traffic volume of a UE during this period is measured. Based on the measurement result, the DRX algorithm decides whether the UE should enter or exit DRX.
GUI Value Range: 2~300
Unit: 20ms
Actual Value Range: 40~6000, step:20
Default Value: 30
CellDrxPara TddPowerSaveStatTimer MOD CELLDRXPARA
LST CELLDRXPARA
TDLBFD-002017 DRX Meaning: Indicates the length of the UE DRX power saving measurement period for cells that operate in TDD mode. The power saving volume of a UE during this period is measured. Based on the measurement result, the DRX algorithm decides whether the UE should enter or exit DRX.
GUI Value Range: 2~300
Unit: 20ms
Actual Value Range: 40~6000, step:20
Default Value: 50
Drx ShortDrxSwitch MOD DRX
LST DRX
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates whether to enable or disable short DRX cycles. Short DRX cycles reduce the traffic delay.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: ON(On)
DrxParaGroup LocalCellId ADD DRXPARAGROUP
LST DRXPARAGROUP
MOD DRXPARAGROUP
RMV DRXPARAGROUP
None None Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS.
GUI Value Range: 0~17
Unit: None
Actual Value Range: 0~17
Default Value: None
DrxParaGroup DrxParaGroupId ADD DRXPARAGROUP
LST DRXPARAGROUP
MOD DRXPARAGROUP
RMV DRXPARAGROUP
None None Meaning: Indicates the ID of the DRX parameter group.
GUI Value Range: 0~9
Unit: None
Actual Value Range: 0~9
Default Value: None
TimeAlignmentTimer TimeAlignmentTimer MOD TATIMER
LST TATIMER
LBFD-001001 / TDLBFD-001001
LBFD-002009 / TDLBFD-002009
3GPP R8 Specifications
Broadcast of system information
Meaning: Indicates the length of the uplink time alignment timer for UEs in the cell. A UE is considered not time-aligned in the uplink if the timer expires.
GUI Value Range: SF500(500 subframes), SF750(750 subframes), SF1280(1280 subframes), SF1920(1920 subframes), SF2560(2560 subframes), SF5120(5120 subframes), SF10240(10240 subframes), INFINITY(Infinity)
Unit: None
Actual Value Range: SF500, SF750, SF1280, SF1920, SF2560, SF5120, SF10240, INFINITY
Default Value: SF1920(1920 subframes)
CellStandardQci LocalCellId LST CELLSTANDARDQCI
MOD CELLSTANDARDQCI
LBFD-001001 / TDLBFD-001001 3GPP R8 Specifications Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS.
GUI Value Range: 0~17
Unit: None
Actual Value Range: 0~17
Default Value: None
CellStandardQci Qci LST CELLSTANDARDQCI
MOD CELLSTANDARDQCI
LOFD-001015 / TDLOFD-001015
LOFD-00101502 / TDLOFD-00101502
Enhanced Scheduling
Dynamic Scheduling
Meaning: Indicates the QoS class identifier (QCI) of an evolved packet system (EPS) bearer. Different QCIs indicate different QoS requirements, such as the packet delay budget, packet error loss rate, and resource type. For details, see Table 6.1.7 in 3GPP TS 23.203.
GUI Value Range: QCI1(QCI 1), QCI2(QCI 2), QCI3(QCI 3), QCI4(QCI 4), QCI5(QCI 5), QCI6(QCI 6), QCI7(QCI 7), QCI8(QCI 8), QCI9(QCI 9)
Unit: None
Actual Value Range: QCI1, QCI2, QCI3, QCI4, QCI5, QCI6, QCI7, QCI8, QCI9
Default Value: None
CellStandardQci DrxParaGroupId MOD CELLSTANDARDQCI
LST CELLSTANDARDQCI
LBFD-002017 / TDLBFD-002017 DRX Meaning: Indicates the ID of a DRX parameter group.
GUI Value Range: 0~9
Unit: None
Actual Value Range: 0~9
Default Value: 0
CellExtendedQci ExtendedQci ADD CELLEXTENDEDQCI
LST CELLEXTENDEDQCI
MOD CELLEXTENDEDQCI
RMV CELLEXTENDEDQCI
LOFD-001015 / TDLOFD-001015
LOFD-00101502 / TDLOFD-00101502
Enhanced Scheduling
Dynamic Scheduling
Meaning: Indicates the extended QoS Class Identifier (QCI), which is required by the operator for service differentiation.
GUI Value Range: 10~254
Unit: None
Actual Value Range: 10~254
Default Value: None
UtranNFreq LocalCellId ADD UTRANNFREQ
LST UTRANNFREQ
MOD UTRANNFREQ
RMV UTRANNFREQ
None None Meaning: Indicates the cell ID of the local cell. It uniquely identifies a cell within an eNodeB.
GUI Value Range: 0~17
Unit: None
Actual Value Range: 0~17
Default Value: None
CellAlgoSwitch LocalCellId LST CELLALGOSWITCH
MOD CELLALGOSWITCH
None None Meaning: Indicates the local ID of the cell. It uniquely identifies a cell within a BS.
GUI Value Range: 0~17
Unit: None
Actual Value Range: 0~17
Default Value: None

Budi Prasetyo

About Budi Prasetyo

All About LTE

Subscribe to this Blog via Email :