Air Interface Latency Optimization (ERAN15.1 - 01)

eRAN
Air Interface Latency Optimization

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

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: [email protected]
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. i

eRAN
Air Interface Latency Optimization Feature Parameter
Description Contents
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 01 (2019-06-06)............................................................................................................................................1
1.2 eRAN15.1 Draft D (2019-04-10)................................................................................................................................... 1
1.3 eRAN15.1 Draft C (2019-03-18)....................................................................................................................................1
1.4 eRAN15.1 Draft B (2019-02-22)....................................................................................................................................2
1.5 eRAN15.1 Draft A (2019-01-05)................................................................................................................................... 2
2 About This Document.................................................................................................................. 5

2.1 General Statements......................................................................................................................................................... 5
2.2 Applicable RAT.............................................................................................................................................................. 5
2.3 Features in This Document.............................................................................................................................................5
3 Overview......................................................................................................................................... 7
4 Air Interface Latency Optimization........................................................................................... 8
4.1 Principles........................................................................................................................................................................ 8
4.1.1 Dynamic Scheduling....................................................................................................................................................8
4.1.2 Physical Channel Resource Management..................................................................................................................10
4.1.3 DRX Optimization.....................................................................................................................................................11
4.1.4 QCI-specific TTI Bundling (FDD)............................................................................................................................ 11
4.1.5 QCI-specific UDP-based ROHC............................................................................................................................... 12
4.2 Network Analysis......................................................................................................................................................... 12
4.2.1 Benefits...................................................................................................................................................................... 12
4.2.2 Impacts.......................................................................................................................................................................12
4.3 Requirements................................................................................................................................................................ 16
4.3.1 Licenses..................................................................................................................................................................... 16
4.3.2 Software.....................................................................................................................................................................16
4.3.3 Hardware................................................................................................................................................................... 17
4.3.4 Others.........................................................................................................................................................................17
4.4 Operation and Maintenance..........................................................................................................................................17
4.4.1 Data Configuration.................................................................................................................................................... 17
4.4.1.1 Data Preparation..................................................................................................................................................... 17
4.4.1.2 Using MML Commands......................................................................................................................................... 24
4.4.1.3 Using the CME....................................................................................................................................................... 25
4.4.2 Activation Verification.............................................................................................................................................. 25
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
Description Contents
4.4.3 Network Monitoring.................................................................................................................................................. 27
5 Parameters..................................................................................................................................... 30
6 Counters........................................................................................................................................ 31
7 Glossary......................................................................................................................................... 32
8 Reference Documents................................................................................................................. 33
Issue 01 (2019-06-06) Copyright © Huawei Technologies Co., Ltd. iii

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

This issue does not include any changes.
1.2 eRAN15.1 Draft D (2019-04-10)

This issue includes the following changes.
Technical Changes
None
Editorial Changes
Revised the following sections:
l Revised descriptions of network impacts of SRI reporting period optimization. For
details, see Network Impacts in 4.2.2 Impacts.
l Revised descriptions of function impacts of QCI-specific UDP-based ROHC. For details,
see Function Impacts in 4.2.2 Impacts.
1.3 eRAN15.1 Draft C (2019-03-18)

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

eRAN
Technical Changes
None
Editorial Changes
l Revised descriptions of network impacts of SR-based scheduling optimization. For
details, see Network Impacts in 4.2.2 Impacts.
l Revised descriptions of data preparation for DRX optimization. For details, see DRX
Optimization in 4.4.1.1 Data Preparation.
1.4 eRAN15.1 Draft B (2019-02-22)

Technical Changes
Change Description Parameter Change RAT Base Station
Model
None N/A FDD N/A
Editorial Changes
l QCI-specific TTI Bundling (FDD) in 4.4.2 Activation Verification
l QCI-specific UDP-based ROHC in 4.4.2 Activation Verification
l 4.4.3 Network Monitoring
1.5 eRAN15.1 Draft A (2019-01-05)

This issue introduces the following changes to eRAN13.1 02 (2018-08-27).

eRAN
Technical Changes
Model
Extended the application Added the FDD l 3900 and 5900

scope of the following CellQciPara.LowLatenc series base
functions from only QCI-3 yFlag parameter. stations
bearers to all bearers carrying l DBS3900
low-latency services: LampSite and
l SR-based scheduling DBS5900
optimization LampSite
l MCS selection l BTS3912E
optimization l BTS3911E
l Preallocation optimization
l PDCCH SINR offset
optimization
Changed the parameters used Added the FDD l 3900 and 5900
to activate SR-based SR_PRIORITY_DATA series base
scheduling optimization. This _OPT_SW option to the stations
function is now controlled by CellQciPara.QciAlgoSw l DBS3900
both the itch parameter. LampSite and
LowDelayServiceOptSwitch DBS5900
option of the LampSite
CellAlgoSwitch.ServiceDiffS
witch parameter and the l BTS3912E
SR_PRIORITY_DATA_OP l BTS3911E
T_SW option of the
CellQciPara.QciAlgoSwitch
parameter.
Added downlink scheduling Added the FDD l 3900 and 5900

priority optimization. For DL_SCH_PRIORITY_ series base
details, see: OPT_SW option to the stations
l Downlink Scheduling CellQciPara.QciAlgoSw l DBS3900
Priority Optimization in itch parameter. LampSite and
4.1.1 Dynamic DBS5900
Scheduling LampSite
l 4.2.2 Impacts l BTS3912E
l 4.4 Operation and l BTS3911E
Maintenance

eRAN

Model
Added SRI reporting period Added the FDD l 3900 and 5900
optimization. For details, see: SRI_PERIOD_OPT_S series base
l SRI Reporting Period W option to the stations
Optimization in 4.1.2 CellQciPara.QciAlgoSw l DBS3900
Physical Channel itch parameter. LampSite and
Resource Management DBS5900
l 4.2.2 Impacts LampSite
l 4.4 Operation and l BTS3912E
Maintenance l BTS3911E
Added PDCCH boundary Added the FDD l 3900 and 5900

power control optimization PDCCH_BOUNDARY_ series base
(FDD). For details, see: PWR_CTRL_OPT_SW stations
l PDCCH Boundary option to the l DBS3900
Power Control CellQciPara.QciAlgoSw LampSite and
Optimization (FDD) in itch parameter. DBS5900
4.1.2 Physical Channel LampSite
Resource Management l BTS3912E
l 4.2.2 Impacts l BTS3911E
l 4.4 Operation and
Maintenance
Added QCI-specific TTI Added the FDD l 3900 and 5900

bundling (FDD). For details, CellQciPara.QciSinrThl series base
see: dForTrigTtibB stations
l 4.1.4 QCI-specific TTI parameter. l DBS3900
Bundling (FDD) Added the LampSite and
l 4.2.2 Impacts QCI_TTI_BUNDLING DBS5900
_SWITCH option to the LampSite
l 4.4 Operation and CellQciPara.QciAlgoSw
Maintenance l BTS3912E
itch parameter.
l BTS3911E
Added QCI-specific UDP- Added the FDD l 3900 and 5900

based ROHC. For details, see: QCI_ROHC_SWITCH series base
l 4.1.5 QCI-specific UDP- option to the stations
based ROHC CellQciPara.QciAlgoSw l DBS3900
itch parameter. LampSite and
l 4.2.2 Impacts
DBS5900
l 4.4 Operation and LampSite
Maintenance
l BTS3912E
l BTS3911E
Editorial Changes
None

eRAN
Description 2 About This Document
2 About This Document
2.1 General Statements

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

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

This document applies to FDD.
2.3 Features in This Document

This document describes the following FDD features.

eRAN
Description 2 About This Document
Feature ID Feature Name Section
LEOFD-131214 Air Interface Latency 4 Air Interface Latency

Optimization Optimization

eRAN
Description 3 Overview
3 Overview
As real-time services develop, users have increasingly high requirements for end-to-end
(E2E) latency. Air interface latency is an important part of E2E latency. Therefore, air
interface latency optimization draws much attention.
Huawei uses a series of control-plane and user-plane optimization methods over the air
interface to further shorten the air interface latency and ensure the stability of the air interface
latency to meet the requirements for smooth experience of real-time services.

eRAN
Description 4 Air Interface Latency Optimization
4 Air Interface Latency Optimization
4.1 Principles
If the LowDelayServiceOptSwitch option of the CellAlgoSwitch.ServiceDiffSwitch
parameter is selected and a QCI is marked with the low-latency service flag by setting the
CellQciPara.LowLatencyFlag parameter to TRUE, the following air interface latency
optimization functions can be enabled:
l SR-based scheduling optimization

l MCS selection optimization
l Downlink scheduling priority optimization
l PDCCH SINR offset optimization
l SRI reporting period optimization
l PDCCH boundary power control optimization (FDD)
l QCI-specific TTI bundling (FDD)
l QCI-specific UDP-based ROHC
The preceding functions do not apply to QCI 1, 2, 5, 65, 66, 69 or 70.
4.1.1 Dynamic Scheduling

This section describes the dynamic scheduling functions in this feature for UEs running low-
latency services. For details about dynamic scheduling, see Scheduling.
SR-based Scheduling Optimization

Before transmitting data, a UE sends the eNodeB an SR using the scheduling request
indicator (SRI) on the physical uplink control channel (PUCCH) to request uplink resources
for data transmission. Upon receiving the SR, the eNodeB responds to the SR and schedules
the UE.
Generally, uplink low-latency services are carried on small, sparse packets and are transmitted
by SR-based scheduling. When the cell load is high, the SR-based scheduling priorities and
scheduling resources are hardly assured. With the increase in the network load, the latency is
prolonged, and user experience for UEs running low-latency services deteriorates.

eRAN
SR-based scheduling optimization is enabled if the SR_PRIORITY_DATA_OPT_SW

option of the CellQciPara.QciAlgoSwitch parameter is selected.
This function increases the SR-based scheduling priorities for UEs running low-latency
services and the amount of data transmitted by SR-based scheduling. This shortens the latency
on UEs waiting SR-based scheduling and improves user experience for UEs running low-
latency services.
MCS Selection Optimization

During downlink scheduling for a UE, the eNodeB automatically selects a modulation and
coding scheme (MCS) for UE data transmission based on the channel quality indicator (CQI)
reported by the UE. In addition, it evaluates the difference between the channel quality
indicated by the reported CQI and actual channel quality based on hybrid automatic repeat
request (HARQ) feedback and then adjusts the CQI based on the difference so that the initial
block error rate (IBLER) can converge on the target optimum value.
When the UE is in an area with weak coverage or experiences strong interference, the IBLER
is high or converges on the target value slowly. This causes multiple HARQ retransmissions,
each of which introduces a latency of 8 ms to 10 ms. As a result, the UE data packet latency is
prolonged.
The CellQciPara.DecreaseInNackCqiAdj parameter specifies the decrease in the CQI
adjustment value for UEs running low-latency services when these UEs respond with HARQ
NACK feedback. This helps lower both the CQI adjustment value and the IBLER target value
after UEs respond with NACK feedback, so that the eNodeB selects MCSs with smaller
indexes, which reduces the impacts of PDSCH block errors on the packet loss rate and
latency, and improves user experience with low-latency services.
Preallocation Optimization
During preallocation, the eNodeB proactively sends uplink scheduling indications to UEs so
that uplink and downlink packets are scheduled in a timely manner and the latency on UE
scheduling is shortened.
Through QCI-level preallocation configurations, operators can set differentiated preallocation
parameter groups for bearers with different QCIs, improving user experience with low-latency
services. For details about QCI-level preallocation configurations, see Scheduling.
Downlink Scheduling Priority Optimization

Currently, the eNodeB allocates a special scheduling priority only for voice-service bearers
among all GBR bearers but does not consider that for bearers carrying low-latency services.
As a result, the latency stability of low-latency services cannot be assured in all scenarios. To
further improve the latency stability of the low-latency services, a special scheduling priority
needs to be allocated independently to bearers carrying low-latency services. This priority is
lower than that of the voice-service bearers and higher than that of bearers carrying other
services. Push to talk (PTT) services have a higher priority than QCI-1 services and are not
affected by low-latency services.
Downlink scheduling priority optimization is enabled if the
DL_SCH_PRIORITY_OPT_SW option of the CellQciPara.QciAlgoSwitch parameter is
selected.
This function allocates a special scheduling priority for low-latency services.

eRAN
l For GBR bearers: This function takes effect only for QCI 3 and QCI 4. It ensures the
downlink scheduling priorities for QCI-3 and QCI-4 services are lower than those for
QCI-1 and QCI-75 services but higher than those for other services. That is, the QCIs
with downlink scheduling priorities in descending order are QCI 1, QCI 75, QCI 3, and
QCI 4.
l For non-GBR bearers: This function takes effect only for QCI 6 through QCI 9 and
extended QCIs excluding QCIs 65, 66, 69, and 70. Priorities can be further differentiated
by setting the QciPara.DlschPriorityFactor and QciPara.UlschPriorityFactor
parameters. The downlink scheduling priorities for low-latency services are configured
to be higher than those for non-low-latency services.
4.1.2 Physical Channel Resource Management

This section describes the physical channel resource management functions in this feature for
UEs running low-latency services. For details about physical channel resource management,
see Physical Channel Resource Management.
PDCCH SINR Offset Optimization

The PDCCH transmits the following three types of downlink control information (DCI):
downlink grant, uplink grant, and power control commands. The eNodeB selects an
appropriate PDCCH control channel element (CCE) aggregation level based on channel
quality, which ensures that the PDCCH block error rate (BLER) converges on the target value.
PDCCH block errors result in retransmissions of uplink and downlink grants. Each
retransmission introduces a latency of 8 ms to 10 ms, prolonging the latency on UE data
packets.
The CellQciPara.QciPdcchSinrOffset parameter specifies a PDCCH SINR offset dedicated

to UEs running low-latency services.
PDCCH SINR offset optimization takes effect only when the CCE usage is less than 60%.
After this function takes effect, a dedicated PDCCH SINR offset (specified by
CellQciPara.QciPdcchSinrOffset) for UEs running low-latency services applies. This
enables the eNodeB to use a higher PDCCH CCE aggregation level for these UEs than other
UEs, mitigating the latency introduced by PDCCH block errors and improving user
experience for UEs running low-latency services.
SRI Reporting Period Optimization

After the SRI reporting period adaptation function is enabled by setting the
PUCCHCfg.SriPeriodAdaptive parameter to QCIADAPTIVE, the SRI reporting period for
UEs running low-latency services is extended to more than 10 ms. SRI reporting period
extension increases the latency on uplink low-latency services and affects user experience of
such UEs.
SRI reporting period optimization can be used to improve user experience of such UEs. SRI
reporting period optimization is enabled if the SRI_PERIOD_OPT_SW option of the
CellQciPara.QciAlgoSwitch parameter is selected in the following scenarios:
l In FDD, the CellPucchAlgo.SriReCfgInd parameter is set to FALSE.
It is recommended that this function be used when the bandwidth is at least 10 MHz. After
this function is enabled, shorter SRI reporting periods are preferentially configured for UEs
running low-latency services and the SRI reporting period configuration remains unchanged

eRAN
for other UEs. For details about SRI reporting period adaptation, see Physical Channel
Resource Management.
PDCCH Boundary Power Control Optimization (FDD)

In FDD, when the CCE aggregation level reaches 8, the eNodeB increases the PDCCH CCE
power by 1 dB for a UE each time the eNodeB detects three consecutive discontinuous
transmissions (DTXs) for the UE. PDCCH boundary power control optimization for low-
latency services can be used to shorten the DTX waiting time. This function is enabled if the
PDCCH_BOUNDARY_PWR_CTRL_OPT_SW option of the
CellQciPara.QciAlgoSwitch parameter is selected.
This function takes effect only when the CCE usage is less than or equal to 60%. After this
function is enabled, the PDCCH CCE power increases faster, shortening the latency on UEs
running low-latency services.
4.1.3 DRX Optimization

This section describes the function of QCI-specific differentiated DRX configuration in this
feature. For details about QCI-specific DRX parameter configurations, see DRX and
Signaling Control.
DRX can be disabled for UEs running low-latency services by setting the
DrxParaGroup.EnterDrxSwitch parameter to OFF. This eliminates DRX-induced extra
scheduling latency, improving user experience with low-latency services.
4.1.4 QCI-specific TTI Bundling (FDD)

For FDD, QCI-specific TTI bundling is enabled if the QCI_TTI_BUNDLING_SWITCH
option of the CellQciPara.QciAlgoSwitch parameter is selected.
The QCI-specific TTI bundling principles and procedures are similar to the TTI bundling
principles and procedures for VoLTE services. For details, see VoLTE. The differences are as
follows:
l TTI bundling entry conditions
The eNodeB sends a UE running low-latency services an RRC Connection
Reconfiguration message, instructing the UE to enter the TTI bundling state, when all of
the following conditions are met:
– The UE is not running VoLTE or PTT services. In addition, the uplink power of the
UE is limited, and the number of PRBs supported by the power is less than or equal
to 3.
– The number of consecutive SINR measurement values that are less than the target
SINR value reaches the threshold for entering the TTI bundling state, defined by the
CellUlschAlgo.StatisticNumThdForTtibTrig parameter.
The target SINR value is defined as follows:
n If the CellTtiBundlingAlgo.R12TtiBundlingSwitch parameter is set to ON,
the target SINR value is specified by the
CellTtiBundlingAlgo.SinrThdToTrigR12TtiB parameter.
n If the CellTtiBundlingAlgo.R12TtiBundlingSwitch parameter is set to OFF,
the target SINR value is specified by the
CellQciPara.QciSinrThldForTrigTtibB.

eRAN
l TTI bundling exit conditions

Assume that a UE performing low-latency services has entered the TTI bundling state.
The eNodeB sends the UE an RRC Connection Reconfiguration message, instructing the
UE to exit the TTI bundling state, when a handover, service drop, or RRC connection
reestablishment occurs or either of the following conditions is fulfilled:
– Bearers carrying low-latency services have not been released, and the number of
consecutive SINR measurement values that are greater than the sum of the target
SINR value and the CellUlschAlgo.HystToExitTtiBundling parameter value
reaches the threshold for exiting the TTI bundling state, defined by the
CellUlschAlgo.StatisticNumThdForTtibExit parameter.
– Bearers carrying low-latency services have been released.
l Data block transmission
After a UE running low-latency services enters the TTI bundling state, data block
transmission for low-latency services is similar to that for VoLTE services. The
difference is that during RLC segmentation, the number of RLC segments for VoLTE
services is limited, while it is not limited for low-latency services.
4.1.5 QCI-specific UDP-based ROHC

QCI-specific user datagram protocol (UDP)-based robust header compression (ROHC)
performs ROHC on UDP packet headers. When the air interface capability is limited, QCI-
specific UDP-based ROHC reduces the packet header load, reduces the probability of RLC
segmentation, and shortens the interaction response time, improving network performance
over the air interface.
QCI-specific UDP-based ROHC is enabled if the QCI_ROHC_SWITCH option of the
CellQciPara.QciAlgoSwitch parameter is selected. After this function is enabled, UEs enter
the UDP-based ROHC state.
For details about the ROHC, see ROHC.
4.2 Network Analysis
4.2.1 Benefits
This feature shortens the transmission latency of low-latency small-packet services over the
air interface in a cell.
l On a heavy-load network, the air interface round trip time (RTT) of UEs running low-
latency services decreases by 20% to 30%. When the downlink PRB usage is greater
than or equal to 50%, the network load is heavy.
l On a light- or medium-load network, the air interface RTT of UEs running low-latency
services decreases by 5% to 20%. When the downlink PRB usage is less than 50%, the
network load is light or medium.
4.2.2 Impacts
Network Impacts
The functions in this feature have the following impacts on network performance if there are
excessive UEs running low-latency services:

eRAN
l SR-based scheduling optimization

The SR-based scheduling priorities and resources are increased for UEs running low-
latency services. As a result, uplink user-perceived data rates of other UEs may decrease.
This function depends on delay-based scheduling for voice and data services. After the
delay-based scheduling function is enabled for voice and data services, the uplink MCS
index reduction by two in SR-based scheduling of data services no longer takes effect.
As a result, the uplink BLER and downlink BLER increase.
l MCS selection optimization
The downlink PRB usage increases, and the downlink IBLER decreases.
l Preallocation optimization
The uplink PRB usage, uplink interference, and CCE usage increase. The uplink IBLER
decreases.
l Downlink scheduling priority optimization
Scheduling priorities for UEs running low-latency services increase. Meanwhile, the data
rates of other UEs may decrease. Downlink cell throughput and downlink user-perceived
data rates may decrease because low-latency services are carried on small, sparse
packets.
l PDCCH SINR offset optimization
The average CCE aggregation level and equivalent CCE usage increase.
l SRI reporting period optimization
The SRI reporting period for low-latency services is shortened, which occupies more
SRI resources and affects the maximum number of UEs that a cell can serve. Meanwhile,
the SRI reporting period of UEs running non-low-latency services is prolonged in
advance. As a result, the RRC connection setup duration and E-RAB setup duration may
increase.
If the CellPreallocGroup.PreallocationSize or CellUlschAlgo.PreAllocationSize
parameter value is greater than 1500 before air interface latency optimization is enabled,
throughput of UEs running low-latency services may decrease.
For details about the relationship between the CellPreallocGroup.PreallocationSize and
CellUlschAlgo.PreAllocationSize parameters, see Scheduling
Throughput of UEs running low-latency services = L.Thrp.bits.UL.QCI.n/
L.Thrp.Time.UL.QCI.n
QCIn specifies the QCI marked with the low-latency service flag.
l PDCCH boundary power control optimization (FDD)
The PDCCH CCE power of UEs running low-latency services is increased. This causes
the equivalent CCE usage of the cell to increase. As a result, the CCE allocation success
rate of UEs running non-low-latency services is affected, increasing the service latency
on such UEs.
An increase in the PDCCH CCE power results in more interference to neighboring cells.
This leads to deterioration in the downlink channel quality across the network and a
possible increase in the downlink IBLER, affecting the downlink cell throughput.
l DRX optimization
The UE power consumption and the RRC signaling in the cell increase.
l QCI-specific TTI bundling (FDD)
RRC messages are required to trigger the entry and exit of QCI-specific TTI bundling.
Therefore, the RRC signaling in the cell increases.

eRAN
l QCI-specific UDP-based ROHC

QCI-specific UDP-based ROHC reduces the amount of data transmitted over the air
interface, decreasing the traffic volume.
Function Impacts
RAT Function Function Reference Description
Name Switch
FDD TTI TtiBundlingSw VoLTE RRC messages are required to

bundling itch option of trigger the entry and exit of QCI-
the specific TTI bundling. Therefore,
CellAlgoSwitc the RRC signaling in the cell
h.UlSchSwitch increases. Enabling both VoLTE
parameter and QCI-specific TTI bundling
(including 3GPP Release 12-
compliant TTI bundling) produces
the following impacts:
l When a UE enters the VoLTE
TTI bundling state and then
performs a low-latency service,
or when the UE enters the QCI-
specific TTI bundling state and
then performs a VoLTE service,
the TTI bundling state is
retained. In this case, the
eNodeB determines whether
the UE exits the TTI bundling
state based on the VoLTE TTI
bundling exit conditions, unless
the VoLTE service has been
released.
l When a UE that is not in the
TTI bundling state
simultaneously performs a low-
latency service and a VoLTE
service, the eNodeB determines
whether the UE enters the TTI
bundling state based on the
VoLTE TTI bundling entry
conditions.

eRAN

Name Switch
FDD Inter- UlCompForVi Video When a UE meets the conditions

eNodeB deoSwitch Experience for entering the 3GPP Release 10-
UL CoMP option of the Optimizati compliant QCI-specific TTI
for video CellAlgoSwitc on bundling state, then:
services h.UplinkComp l If 3GPP Release 12-compliant
Switch TTI bundling eHARQ takes
parameter effect first, inter-eNodeB UL
CoMP for video services will
not take effect.
l If inter-eNodeB UL CoMP for
video services has been
enabled, 3GPP Release 12-
compliant TTI bundling
eHARQ will not take effect.
For details about 3GPP Release
12-compliant TTI bundling
eHARQ, see VoLTE.
FDD Turbo start CellAlgoSwitc Video Turbo start video and QCI-specific
video h.RohcSwitch Experience UDP-based ROHC can be enabled
parameter with Optimizati simultaneously. However, for a
the value of ON on given UE:
and l Both turbo start video and
PdcpRohcPara QCI-specific UDP-based
.Profiles ROHC can take effect
parameter with simultaneously on separate
the value of bearers with different QCIs.
Profile0x0006
l Turbo start video and QCI-
specific UDP-based ROHC
cannot take effect
simultaneously on bearers with
the same QCI. Either function
whose activation conditions are
met first takes effect first. The
other function can take effect
only after the previous function
stops taking effect.

eRAN

Name Switch
FDD Uplink FDD: Uplink Uplink data compression and QCI-

data CellDataComp Data specific UDP-based ROHC can be
compressio rConfig.Standa Compressi enabled simultaneously. However,
n rdUdcSwitch on for a given UE:
l Both uplink data compression
and QCI-specific UDP-based
ROHC can take effect
simultaneously on separate
bearers with different QCIs.
l Uplink data compression and
QCI-specific UDP-based
ROHC cannot take effect
simultaneously on bearers with
the same QCI. Either function
whose activation conditions are
met first takes effect first. The
other function can take effect
only after the previous function
stops taking effect.
4.3 Requirements
4.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit
FDD LEOFD-131214 Air Interface LT1S00AI per Cell

Latency LO00
Optimization
4.3.2 Software
Before activating this function, ensure that its prerequisite functions have been activated and
mutually exclusive functions have been deactivated. For detailed operations, see the relevant
feature documents.

eRAN
Prerequisite Functions
RAT Function Name Function Switch Reference Description
FDD Delay-based CellUlschAlgo.UlD VoLTE SR-based scheduling

scheduling for voice elaySchStrategy optimization
and data services parameter with the requires this
value of function.
VOIP_AND_DATA
_DELAYSCH
Mutually Exclusive Functions

None
4.3.3 Hardware
Base Station Models

No requirements
Boards
The LBBPc does not support this function.
RF Modules
No requirements
4.3.4 Others
l UEs and the EPC support bearers carrying low-latency services.
l In FDD, QCI-specific TTI bundling also requires UEs to support TTI bundling. 3GPP
Release 12-compliant TTI bundling requires UEs to comply with 3GPP Release 12.
l QCI-specific UDP-based ROHC also requires UEs to support ROHC profile 2.
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation
Dynamic Scheduling
Table 4-1 describes the parameters used for function activation.

eRAN
Table 4-1 Parameters used for activation

Parameter Parameter ID Option Setting Notes
Name
Low Latency CellQciPara.LowLatenc N/A When a QCI is

Flag yFlag planned to be used
for low-latency
services, set this
parameter to TRUE
for the QCI.
It is not
recommended that
this parameter be set
to TRUE for QCI 1,
2, 5, 65, 66, 69, or
70.
Service CellAlgoSwitch.Service LowDelayServiceO Select this option.

Differentiated DiffSwitch ptSwitch
Switch
Uplink Delay- CellUlschAlgo.UlDelayS N/A To enable SR-based

based chStrategy scheduling
Scheduling optimization, set this
Strategy parameter to
VOIP_AND_DATA
_DELAYSCH.
QCI Algorithm CellQciPara.QciAlgoSw SR_PRIORITY_DA To enable SR-based

Switch itch TA_OPT_SW scheduling
optimization, select
this option.
This option takes
effect only if the
LowDelayServiceO
ptSwitch option of
the
CellAlgoSwitch.Ser
viceDiffSwitch
parameter is
selected.

eRAN

Name
Decrease in CellQciPara.DecreaseIn N/A To enable MCS

NACK CQI NackCqiAdj selection
Adjustment optimization, set this
parameter to its
recommended value.
This parameter takes
effect only if the
LowDelayServiceO
ptSwitch option of
the
CellAlgoSwitch.Ser
viceDiffSwitch
parameter is
selected.
Preallocation CellPreallocGroup.Prea N/A It is recommended

Parameter llocationParaGroupId that this parameter
Group ID be set to a valid
value if operators
want to use QCI-
level preallocation
configurations.
QCI Algorithm CellQciPara.QciAlgoSw DL_SCH_PRIORIT To enable downlink

Switch itch Y_OPT_SW scheduling priority
this option.
This option takes
effect only if the
LowDelayServiceO
ptSwitch option of
the
CellAlgoSwitch.Ser
viceDiffSwitch
parameter is
selected.
Physical Channel Resource Management


eRAN

Name

for low-latency
services, set this
parameter to TRUE
for the QCI.
It is not
recommended that
to TRUE for QCI 1,
2, 5, 65, 66, 69, or
70.

Switch
QCI PDCCH CellQciPara.QciPdcchS N/A To enable PDCCH

SINR Offset inrOffset SINR offset
optimization, set this
parameter to its
recommended value.
This parameter takes
effect only if the
LowDelayServiceO
ptSwitch option of
the
CellAlgoSwitch.Ser
viceDiffSwitch
parameter is
selected.
QCI Algorithm CellQciPara.QciAlgoSw SRI_PERIOD_OPT To enable SRI

Switch itch _SW reporting period
this option.
This option takes
effect only if the
LowDelayServiceO
ptSwitch option of
the
CellAlgoSwitch.Ser
viceDiffSwitch
parameter is
selected.

eRAN

Name
QCI Algorithm CellQciPara.QciAlgoSw PDCCH_BOUNDA To enable PDCCH

Switch itch RY_PWR_CTRL_O boundary power
PT_SW control optimization,
select this option.
This option takes
effect only if the
LowDelayServiceO
ptSwitch option of
the
CellAlgoSwitch.Ser
viceDiffSwitch
parameter and the
PdcchPcSwitch
option of the
CellAlgoSwitch.Dl
PcAlgoSwitch
parameter are
selected.
DRX Optimization

eRAN

Name
Enter DRX DrxParaGroup.EnterDr N/A Set this parameter to

Switch xSwitch OFF if DRX is not
required for UEs
running low-latency
services.
If bearers carrying
both low-latency
and non-low-latency
services share the
same group of DRX
parameters, then
DRX is disabled for
both types of
bearers. As a result,
the uplink BLER
and downlink BLER
increase. To prevent
this from happening,
configure a
dedicated group of
DRX parameters for
bearers carrying
low-latency.
QCI-specific TTI Bundling (FDD)


Name

for low-latency
services, set this
parameter to TRUE
for the QCI.
It is not
recommended that
to TRUE for QCI 1,
2, 5, 65, 66, 69, or
70.

eRAN

Name

Switch
QCI Algorithm CellQciPara.QciAlgoSw QCI_TTI_BUNDLI Select this option.

Switch itch NG_SWITCH This option takes
effect only if the
LowDelayServiceO
ptSwitch option of
the
CellAlgoSwitch.Ser
viceDiffSwitch
parameter is
selected.
SINR Thld for CellQciPara.QciSinrThl N/A Set the parameter to

Triggering QCI dForTrigTtibB its recommended
TTI Bundling value.
QCI-specific UDP-based ROHC


Name

for low-latency
services, set this
parameter to TRUE
for the QCI.
It is not
recommended that
to TRUE for QCI 1,
2, 5, 65, 66, 69, or
70.

Switch

eRAN

Name
QCI Algorithm CellQciPara.QciAlgoSw QCI_ROHC_SWIT Select this option.

Switch itch CH This option takes
effect only if the
LowDelayServiceO
ptSwitch option of
the
CellAlgoSwitch.Ser
viceDiffSwitch
parameter is
selected.
4.4.1.2 Using MML Commands
Activation Command Examples

The following is an example where QCI 3 is to be marked with the low-latency service flag.
//Marking QCI 3 with the low-latency service flag
MOD CELLQCIPARA: LocalCellId=0, Qci=3, LowLatencyFlag=1;
//Turning on LowDelayServiceOptSwitch
MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=LowDelayServiceOptSwitch-1;
//Setting the UlDelaySchStrategy parameter to VOIP_AND_DATA_DELAYSCH
MOD CELLULSCHALGO: LocalCellId=0, UlDelaySchStrategy=VOIP_AND_DATA_DELAYSCH;
//Turning on SR_PRIORITY_DATA_OPT_SW
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-1;
//Modifying the DecreaseInNackCqiAdj and QciPdcchSinrOffset parameters
MOD CELLQCIPARA: LocalCellId=0, Qci=3, DecreaseInNackCqiAdj=10,
QciPdcchSinrOffset=30;
//Setting QCI-level preallocation parameters
MOD CELLALGOSWITCH: LocalCellId=0,
UlSchSwitch=PreAllocationSwitch-1&SmartPreAllocationSwitch-1;
ADD CELLPREALLOCGROUP: LocalCellId=0, PreallocationParaGroupId=0,
PreallocationSwitch=ON, SmartPreallocationSwitch=ON, PreallocationMinPeriod=5,
PreallocationSize=80, SmartPreallocationDuration=50;
MOD CELLQCIPARA: LocalCellId=0, QCI=3, PreallocationParaGroupId=0;
//Turning on DL_SCH_PRIORITY_OPT_SW
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-1;
//Turning on SRI_PERIOD_OPT_SW
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SRI_PERIOD_OPT_SW-1;
//Turning on PDCCH_BOUNDARY_PWR_CTRL_OPT_SW and PdcchPcSwitch
MOD CELLQCIPARA: LocalCellId=0, Qci=3,
QciAlgoSwitch=PDCCH_BOUNDARY_PWR_CTRL_OPT_SW-1;
MOD CELLALGOSWITCH: LocalCellId=0, DlPcAlgoSwitch=PdcchPcSwitch-1;
//Disabling QCI-specific DRX
MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=4, EnterDrxSwitch=OFF;
//Turning on the QCI_TTI_BUNDLING_SWITCH switch and setting the
QciSinrThldForTrigTtibB parameter
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=QCI_TTI_BUNDLING_SWITCH-1,
QciSinrThldForTrigTtibB=-3;
//Turning on QCI_ROHC_SWITCH
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=QCI_ROHC_SWITCH-1;
Deactivation Command Examples

//Restoring the DecreaseInNackCqiAdj and QciPdcchSinrOffset parameters
MOD CELLQCIPARA: LocalCellId=0, Qci=3, DecreaseInNackCqiAdj=0,
QciPdcchSinrOffset=0;

eRAN
//Turning off the following switches: SRI_PERIOD_OPT_SW, DL_SCH_PRIORITY_OPT_SW,

PDCCH_BOUNDARY_PWR_CTRL_OPT_SW, SR_PRIORITY_DATA_OPT_SW, QCI_TTI_BUNDLING_SWITCH,
and QCI_ROHC_SWITCH
MOD CELLQCIPARA: LocalCellId=0, Qci=3,
QciAlgoSwitch=SRI_PERIOD_OPT_SW-0&DL_SCH_PRIORITY_OPT_SW-0&PDCCH_BOUNDARY_PWR_CTRL
_OPT_SW-0&SR_PRIORITY_DATA_OPT_SW-0&QCI_TTI_BUNDLING_SWITCH-0&QCI_ROHC_SWITCH-0;
//Turning off LowDelayServiceOptSwitch
MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=LowDelayServiceOptSwitch-0;
//Disabling QCI-specific preallocation
MOD CELLQCIPARA: LocalCellId=0, QCI=3, PreallocationParaGroupId=255;
//Enabling QCI-specific DRX
MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=4, EnterDrxSwitch=ON;
4.4.1.3 Using the CME

For detailed operations, see CME-based Feature Configuration.
4.4.2 Activation Verification
SR-based Scheduling Optimization

If the value of Service Uplink Average Throughput of bearers carrying low-latency services
increases, this function has taken effect.
MCS Selection Optimization

If the value of downlink IBLER (QCI n) decreases, this function has taken effect.
Downlink IBLER (QCI n) = L.Traffic.DL.SCH.ErrTB.Ibler.QCI.n/
L.Traffic.DL.SCH.TB.QCI.n
Downlink Scheduling Priority Optimization

If the average processing latency of downlink packets for services carried on DRBs decreases,
this function has taken effect.
PDCCH SINR Offset Optimization

Check whether PDCCH SINR offset optimization has taken effect by observing User
Common Monitoring on the U2020. The procedure is as follows:
1. Use a UE to access a cell and perform a low-latency service.
2. On the U2020, choose Monitor > Signaling Trace > Signaling Trace Management.
3. In the navigation tree of the Signaling Trace Management tab page, choose Trace Type
> LTE > User Performance Monitoring > User Common Monitoring. Set the tracing
duration, MMEc (MME ID) of the NE to be traced, and mTMSI (UE TMSI) to start the
CCE aggregation level monitoring.
4. Check the CCE aggregation level when the UE is running the low-latency service.
If the CCE aggregation level increases, this function has taken effect.
PDCCH Boundary Power Control Optimization (FDD)

If the equivalent CCE usage increases, this function has taken effect.

eRAN
QCI-specific TTI Bundling (FDD)

To verify whether QCI-specific TTI bundling has taken effect, use the following methods:
l Message tracing
– Observe the value of the ttiBundling IE (MAC-MainConfig > ul-SCH-Config >
ttiBundling) in the RRC_CONN_RECFG message over the Uu interface.
This function has taken effect when all the following conditions are met:
n The value of this IE is TRUE and the QCI is marked with the low-latency
service flag, indicating that the UE has entered the QCI-specific TTI bundling
state.
n The value of this IE is FALSE and the QCI is marked with the low-latency
service flag, indicating that the UE has exited the QCI-specific TTI bundling
state.
– For 3GPP Release 12-compliant TTI bundling eHARQ, check the e-HARQ-Pattern-
r12 field.
n The value of this field is TRUE and the QCI is marked with the low-latency
service flag, indicating 3GPP Release 12-compliant QCI-specific TTI bundling
eHARQ has taken effect.
n The value of this field is FALSE and the QCI is marked with the low-latency
service flag, indicating 3GPP Release 12-compliant QCI-specific TTI bundling
eHARQ has stopped taking effect or has not taken effect.
l Counter observation
Check the counters listed in Table 4-6. If the value of any of the counters increases
significantly, QCI-specific TTI bundling has taken effect for VoLTE UEs, video UEs,
and UEs running low-latency services.
Table 4-6 Counters used to verify activation of QCI-specific TTI bundling

Counter ID Counter Name
1526728496 L.Traffic.User.TtiBundling.Avg
1526746002 L.Traffic.User.R12TtiBundling.Avg
1526728911 L.Signal.Num.TtiBundling.Enter
1526728912 L.Signal.Num.TtiBundling.Exit
QCI-specific UDP-based ROHC

l Message tracing
a. On the U2020, create and start a Uu interface tracing task.
b. Use an ROHC-capable UE to perform a low-latency service.
Observe the RRC_UE_CAP_INFO message to check whether the UE supports the
ROHC feature and determine the profile supported by the UE. If the value of any
profile is TRUE, the UE supports ROHC and such a profile.
c. Observe the RRC_CONN_RECFG message over the Uu interface to determine
whether ROHC has been activated.

eRAN
n If "pdcp-Config >headerCompression > rohc" is displayed, ROHC has been

activated.
n If "pdcp-Config >headerCompression > notUsed: NULL" is displayed, ROHC
has not been activated.
l Counter observation
Check the counters listed in Table 4-7. If the value of any of the counters increases
significantly, this function has taken effect.
Table 4-7 Counters related to QCI-specific UDP-based ROHC

Counter ID Counter Name
1526728525 L.Traffic.User.RoHC.Avg
1526747661 L.PDCP.UL.RoHC.FailDecomp.Data
1526747662 L.PDCP.UL.RoHC.TotalDecomp.Data
1526747663 L.PDCP.UL.RoHC.Data.HdrComp.Byt
es
1526747664 L.PDCP.UL.RoHC.Data.Hdr.Bytes
4.4.3 Network Monitoring

l If the value of the L.Traffic.User.LowLatency.Avg counter is greater than 0, there are
UEs running low-latency services in a cell.
l The feature gains can be evaluated by using the average downlink packet processing
latency of services carried on DRBs in the cell.
Average downlink packet processing latency of QCI n services carried on DRBs =
L.Traffic.DL.PktDelay.Time.QCI.n/L.Traffic.DL.PktDelay.Num.QCI.n
l The performance of air interface latency optimization can be evaluated by monitoring the
external call history record (CHR) PERIOD_UE_LOWDELAY_PLAY_SC.
Before monitoring this CHR, run the following MML command:
MOD SCPOLICY: ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-1;
ADD SCAPPPARACFG: AppDnsId=1, AppIdentType=DNS, AppDns="xxx",
MatchRule=Query, AppCfgTargetInd=LowDelayServiceInd-1;
This CHR is not compatible with LMPT boards.

This CHR is measured periodically. (The default period is 30 seconds.) For details about
the fields and their meanings, see Table 4-8.

eRAN
Table 4-8 Fields in the external CHR PERIOD_UE_LOWDELAY_PLAY_SC and their

meanings
Field Meaning
>>TCP DL RTT Mean Delay Average downstream TCP RTT in the

unit of ms. The downstream TCP RTT is
the difference between the time a
downlink packet is sent and the time the
ACK with the corresponding sequence
number is received.
>>TCP DL RTT Mean Interval1 Number of times the downstream TCP

RTT falls within the range of [0 ms, 20
ms)

ms)

ms)

ms)

RTT falls within the range of [100 ms,
∞)
>>TCP UL RTT Mean Delay Average upstream TCP RTT in the unit of
ms. The upstream TCP RTT is the
difference between the time an uplink
packet is sent and the time the ACK with
the corresponding sequence number is
received.
>>TCP UL RTT Mean Interval1 Number of times the upstream TCP RTT
falls within the range of [0 ms, 20 ms)
falls within the range of [80 ms, ∞)

eRAN
Field Meaning
>>UDP UL RTT Mean Delay Average upstream UDP RTT in the unit
of ms. The upstream UDP RTT is the
difference between the time an uplink
packet is sent and the time the
corresponding downlink packet is
received.
>>UDP UL RTT Mean Interval1 Number of times the upstream UDP RTT
falls within the range of [80 ms, ∞)
>UDP UlPkts Total number of uplink packets
>UDP DlPkts Total number of downlink packets
>>ResurveyUdpstreamNum Number of UDP streams to be resurveyed
When bearers carrying low-latency services are set up on the core network:
– If only UDP packets are carried on bearers carrying low-latency services, preceding
UDP-related indicators are valid.
– If only TCP data packets are carried on bearers carrying low-latency services,
preceding TCP-related indicators are valid.
– If both UDP and TCP data packets are carried on bearers carrying low-latency
services, preceding TCP- and UDP-related indicators are valid.
If domain name servers (DNSs) are configured to identify low-latency services for
maintenance and tests, each DNS can be associated with a maximum of 60 IP addresses.
If there are more than 60 IP addresses, there may be no external CHR about low-latency
services.

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

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

eRAN
Description 7 Glossary
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Description 8 Reference Documents
8 Reference Documents
1. Scheduling
2. Physical Channel Resource Management
3. DRX and Signaling Control
4. VoLTE
5. ROHC
6. Video Experience Optimization
7. Uplink Data Compression

Air Interface Latency Optimization (ERAN15.1 - 01)

Uploaded by

Copyright:

Available Formats

Air Interface Latency Optimization (ERAN15.1 - 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Air Interface Latency Optimization (ERAN15.1 - 01)

Uploaded by

Copyright:

Available Formats

eRAN

Air Interface Latency Optimization

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

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

2 About This Document.................................................................................................................. 5

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

4.4.3 Network Monitoring.................................................................................................................................................. 27

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

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

1.2 eRAN15.1 Draft D (2019-04-10)

1.3 eRAN15.1 Draft C (2019-03-18)

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

1.4 eRAN15.1 Draft B (2019-02-22)

None N/A FDD N/A

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

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

Extended the application Added the FDD l 3900 and 5900

Added downlink scheduling Added the FDD l 3900 and 5900

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

Change Description Parameter Change RAT Base Station

Added PDCCH boundary Added the FDD l 3900 and 5900

Added QCI-specific TTI Added the FDD l 3900 and 5900

Added QCI-specific UDP- Added the FDD l 3900 and 5900

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

2 About This Document

2.1 General Statements

l The technical principles of features and their related parameters

2.2 Applicable RAT

2.3 Features in This Document

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

Feature ID Feature Name Section

LEOFD-131214 Air Interface Latency 4 Air Interface Latency

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

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

4 Air Interface Latency Optimization

l SR-based scheduling optimization

The preceding functions do not apply to QCI 1, 2, 5, 65, 66, 69 or 70.

4.1.1 Dynamic Scheduling

SR-based Scheduling Optimization

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

SR-based scheduling optimization is enabled if the SR_PRIORITY_DATA_OPT_SW

MCS Selection Optimization

Downlink Scheduling Priority Optimization

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

4.1.2 Physical Channel Resource Management

PDCCH SINR Offset Optimization

The CellQciPara.QciPdcchSinrOffset parameter specifies a PDCCH SINR offset dedicated

SRI Reporting Period Optimization

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

PDCCH Boundary Power Control Optimization (FDD)

4.1.3 DRX Optimization

4.1.4 QCI-specific TTI Bundling (FDD)

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

l TTI bundling exit conditions

4.1.5 QCI-specific UDP-based ROHC

4.2 Network Analysis

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