Professional Documents
Culture Documents
Issue 01
Date 2016-03-07
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 4
2.1 Background.....................................................................................................................................................................4
2.2 Introduction.................................................................................................................................................................... 4
2.3 Benefits........................................................................................................................................................................... 5
2.4 Architecture.................................................................................................................................................................... 5
3 Technical Description...................................................................................................................6
3.1 SRLTE optimization algorithm.......................................................................................................................................6
3.2 SRLTE Discard Algorithm............................................................................................................................................. 8
4 Related Features...........................................................................................................................10
5 Network Impact........................................................................................................................... 11
6 Engineering Guidelines............................................................................................................. 12
6.1 When to Use SRLTE Optimization.............................................................................................................................. 12
6.2 Required Information................................................................................................................................................... 12
6.3 Planning........................................................................................................................................................................ 12
6.3.1 RF Planning............................................................................................................................................................... 12
6.3.2 Network Planning...................................................................................................................................................... 12
6.3.3 Hardware Planning.................................................................................................................................................... 12
6.4 Deployment.................................................................................................................................................................. 13
6.4.1 Requirements............................................................................................................................................................. 13
6.4.2 Precautions.................................................................................................................................................................13
6.4.3 Data Preparation and Feature Activation...................................................................................................................13
6.4.3.1 Data Preparation..................................................................................................................................................... 13
6.4.3.2 Activation............................................................................................................................................................... 14
6.4.4 Activation Observation..............................................................................................................................................14
6.4.5 Deactivation...............................................................................................................................................................15
6.5 Performance Monitoring...............................................................................................................................................16
7 Parameters..................................................................................................................................... 18
8 Counters........................................................................................................................................ 21
9 Glossary......................................................................................................................................... 23
10 Reference Documents............................................................................................................... 24
1.1 Scope
This document describes LOFD-080212 SRLTE Optimization, including its technical
principles, related features, network impact, and engineering guidelines. SRLTE is short for
Single Radio LTE.
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD,
and "eNodeB" refers to LTE FDD eNodeB.
This document applies to the following types of eNodeBs.
Micro BTS3202E
BTS3911E
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Changes in wording or addition of information and any related parameters affected by
editorial changes. Editorial change does not specify the affected entities.
eRAN11.1 01 (2016-03-07)
This issue includes the following changes.
2 Overview
2.1 Background
SRLTE is a single radio voice solution. When an SRLTE-capable UE is located in an LTE
cell, the UE periodically leaves the RRC_CONNECTED state to monitor a paging channel on
a network of another RAT. The UE then returns to the RRC_CONNECTED state once the
paging monitoring is complete. The SRLTE-capable UE does not notify the eNodeB when
leaving or returning to the RRC_CONNECTED state. This operation may have the following
impacts:
l The number of the times of out-of-synchronization can increase because SRLTE-capable
UEs fail to receive the timing advance (TA) signal.
l The probability of false alarm reports increasing is because SRLTE-capable UEs fail to
receive the Msg2 or Msg4 delivered by the eNodeB.
l A deteriorate is experienced by the majority of LTE KPIs, such as the uplink (UL) and
downlink (DL) throughput, and automatic repeat request (ARQ) retransmission rate.
l GAP measurement is delayed or interrupted because SRLTE-capable UEs fail to receive
the GAP measurement command delivered by the eNodeB, which prolongs the
measurement period. If the measurement is delayed, the LTE network can fail to trigger
handovers in a timely manner. In coverage-based measurement scenarios, the emergent
blind handover event A2 is triggered on the LTE network to circumvent service drops.
The SRLTE Optimization feature is introduced to eliminate these impacts and improve the
perceived rates of SRLTE-capable UEs.
2.2 Introduction
The SRLTE Optimization feature enables the eNodeB to check whether an SRLTE-capable
UE is monitoring a paging channel on the CDMA2000 1X network. Upon detecting that an
SRLTE-capable UE is monitoring a paging channel on the CDMA2000 1X network, the
eNodeB discards measured values, which eliminates time-frequency resource waste, improves
LTE network performance, and enhances the experience of users using SRLTE-capable UEs.
2.3 Benefits
The SRLTE Optimization feature improves the KPIs, including the service drop rate,
reestablishment success rate, ARQ retransmission rate, and UL/DL perceived user rates.
The gains provided by the SRLTE Optimization feature are influenced by following factors:
l Paging cycle on the CDMA2000 1X network
l Paging channel monitoring duration on the CDMA2000 1X network
l Proportions of SRLTE-capable UEs and common UEs
l Algorithm parameter settings
l UE capabilities
l Radio channel environment
l Service model
2.4 Architecture
The SRLTE Optimization feature includes the following functions:
l SRLTE optimization algorithm
The eNodeB terminates UL/DL scheduling of SRLTE-capable UEs and discards RSRP
and SINR values once it detects consecutive occurrences of the SRLTE-capable UE
experiencing PUSCH and PDSCH discontinuous transmission (DTX) in a cell.
l SRLTE discard algorithm
The eNodeB discards RSRP and SINR values once it detects consecutive occurrences of
the SRLTE-capable UE experiencing PUSCH DTX in a cell.
3 Technical Description
SRLTE Optimization
The procedure describes an SRLTE-capable UE on the LTE network periodically leaves the
RRC_CONNECTED state to monitor the paging channel on the CDMA2000 1X network
(Figure 3-1). The paging cycle on the CDMA2000 1X network is specified by a parameter on
the CDMA side. An SRLTE-capable UE periodically leaves the RRC_CONNECTED state to
monitor a paging channel on the CDMA2000 1X network. When the paging monitoring is
complete, the UE returns to the RRC_CONNECTED state. The minimum duration is 80 ms,
and when additional mechanisms are deployed, such as TCP penalty, the duration can reach a
maximum length of 120 ms.
Without this algorithm, the eNodeB cannot determine whether an SRLTE-capable UE has left
the RRC_CONNECTED state to monitor a paging channel on the CDMA2000 1X network.
Instead, the eNodeB schedules the UE when the UE is monitoring the paging channel on the
CDMA2000 1X network, which wastes PRB (PRB is short for physical resource block)
resources.
Once an SRLTE-capable UE initiates a paging channel monitoring on the CDMA2000 1X
network, the UE experiences DTX. Based on this principle, the SRLTE Optimization feature
enables the eNodeB to determine whether an SRLTE-capable UE has left the
RRC_CONNECTED state. This alteration in state is to monitor a paging channel on the
CDMA2000 1X network based on the number of consecutive occurrences when the UE
experiences DTX.
The SRLTE optimization algorithm is controlled by the CellSrlte.SrlteSwitch parameter, is
disabled by default. When this parameter is set to ON(On), this feature is enabled and the
eNodeB determines whether an SRLTE-capable UE has left the RRC_CONNECTED state.
This is to ensure paging channel monitoring on the CDMA2000 1X network based on the
following information:
l Number of consecutive occurrences of the UE experiencing PUSCH DTX during UL
scheduling
l Number of consecutive occurrences of the UE experiencing PDSCH DTX during DL
scheduling
The eNodeB determines that an SRLTE-capable UE initiates paging channel monitoring on
the CDMA2000 1X network upon detecting that the UE has experienced DTX (including
PUSCH DTX and PDSCH DTX) for n consecutive times or CQI DTX for n/2 consecutive
instances. The CellSrlte.SrlteDtxThrd parameter specifies the value of n, with its default
value being 6. If UL and DL scheduling are simultaneously performed within a transmission
time interval (TTI):
l If the UE experiences both PUSCH DTX and PDSCH DTX, the eNodeB counts this as a
single DTX event.
l If the UE does not experience PUSCH DTX or PDSCH DTX, the eNodeB assumes that
the UE has returned to the RRC_CONNECTED state and restores normal scheduling.
NOTE
This function is implemented only for the UE which sends a supportedBandList1xRTT information
element (IE) with the "tx-Config1XRTT" and "rx-Config1XRTT" fields set to "single" and "dual",
respectively. Currently, a number of dual-card dual-standby UEs do not support the transmission of such
messages.
4 Related Features
Prerequisite Features
None
Impacted Features
None
5 Network Impact
System Capacity
l SRLTE optimization algorithm: When SRLTE-capable UEs access the network, enabling
this algorithm increases the PRB usage, cell throughput, and application-layer
throughput.
l SRLTE discard algorithm: Enabling this algorithm eliminates the impact of incorrect
measured values on UL MCS and therefore increases cell throughput.
Network Performance
No impact
6 Engineering Guidelines
Use the SRLTE discard algorithm when both of the following conditions are met:
6.3 Planning
6.3.1 RF Planning
N/A
6.4 Deployment
6.4.1 Requirements
Other Features
For details, see 4 Related Features.
Hardware
N/A
License
The feature license listed in the following table must be purchased and activated.
Other Requirements
To support this feature, UEs must support SRLTE.
6.4.2 Precautions
None
6.4.3.2 Activation
Step 2 Run the LST CELLSRLTE command. If the value of SRLTE Switch or SRLTE Discard
Algorithm Switch is ON(On), the corresponding algorithm is activated.
----End
6.4.5 Deactivation
Table 6-3 provides the parameters used to deactivate this feature.
6.7 Troubleshooting
If the cell or user throughput does not significantly increase, this feature may not have been
configured according to the procedures provided in 6 Engineering Guidelines. In this
situation, perform the following steps to troubleshoot the problem:
Step 2 Check whether this feature is enabled when the conditions described in 6.1 When to Use
SRLTE Optimization are met.
Step 3 Check whether parameters related to this feature are configured in compliance with the setting
notes provided in 6.4 Deployment.
Step 4 Check whether this feature has been activated by following steps 1 and 2 provided in 6.4.4
Activation Observation.
Step 5 If the problem persists after the preceding checks are performed, contact Huawei technical
support.
----End
7 Parameters
CellSrlte SrlteDis MOD LOFD-0 SRLTE Meaning: Indicates whether to enable the discarding
cardAlg CELLS 80212 Optimiz of PUSCH measurement results for single radio LTE-
oSwitch RLTE ation capable UEs when such UEs leave the LTE system
LST and listen to the paging channel of another RAT.
CELLS When this parameter is set to ON, an eNodeB discards
RLTE PUSCH measurement results for single radio LTE-
capable UEs when such UEs leave the LTE system
and listen to the paging channel of another RAT.
When this parameter is set to ON, an eNodeB retains
PUSCH measurement results for single radio LTE-
capable UEs when such UEs leave the LTE system
and listen to the paging channel of another RAT. This
parameter applies only to LTE FDD.
GUI Value Range: OFF(Off), ON(On)
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
CellSrlte SrlteSus MOD LOFD-0 SRLTE Meaning: Indicates the period of time during which
pendTi CELLS 80212 Optimiz the eNodeB does not schedule a single radio LTE-
me RLTE ation capable UE because the UE is absent from the LTE
LST mode. This parameter takes effect only when the
CELLS SrlteSwitch parameter is set to ON.
RLTE GUI Value Range: 1~120
Unit: ms
Actual Value Range: 1~120
Default Value: 10
CellSrlte LocalCe LST None None Meaning: Indicates the local ID of the cell. It uniquely
llId CELLS identifies a cell within an eNodeB.
RLTE GUI Value Range: 0~255
MOD Unit: None
CELLS
RLTE Actual Value Range: 0~255
Default Value: None
8 Counters
9 Glossary
10 Reference Documents
1. 3GPP TS 23.272, "Circuit Switched (CS) fallback in Evolved Packet System (EPS)"
2. Scheduling Feature Parameter Description