eRAN

Air Interface Latency Optimization

Feature Parameter Description

Issue 03
Date 2023-08-23

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2023. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.

Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: https://www.huawei.com
Email: [email protected]

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. i

eRAN
Air Interface Latency Optimization Feature
Parameter Description Contents

Contents

1 Change History.........................................................................................................................1
1.1 eRAN19.1 03 (2023-08-23)..................................................................................................................................................1
1.2 eRAN19.1 02 (2023-04-28)..................................................................................................................................................1
1.3 eRAN19.1 01 (2023-03-09)..................................................................................................................................................2
1.4 eRAN19.1 Draft A (2022-12-30)........................................................................................................................................ 2

2 About This Document.............................................................................................................3

2.1 General Statements................................................................................................................................................................ 3
2.2 Applicable RAT......................................................................................................................................................................... 4
2.3 Features in This Document.................................................................................................................................................. 4
2.4 Feature Differences Between FDD and TDD................................................................................................................. 4

3 Overview....................................................................................................................................5
4 Air Interface Latency Optimization.................................................................................... 6
4.1 Principles.................................................................................................................................................................................... 6
4.1.1 Shortening Scheduling Periods........................................................................................................................................8
4.1.2 Raising Service Priorities................................................................................................................................................. 12
4.1.3 Reducing the Number of Scheduling Times.............................................................................................................13
4.1.4 Reducing Service Retransmissions............................................................................................................................... 16
4.2 Network Analysis.................................................................................................................................................................. 20
4.2.1 Benefits................................................................................................................................................................................. 20
4.2.2 Impacts.................................................................................................................................................................................. 20
4.3 Requirements......................................................................................................................................................................... 25
4.3.1 Licenses................................................................................................................................................................................. 25
4.3.2 Software................................................................................................................................................................................25
4.3.3 Hardware.............................................................................................................................................................................. 26
4.3.4 Others.................................................................................................................................................................................... 26
4.4 Operation and Maintenance............................................................................................................................................. 27
4.4.1 Data Configuration........................................................................................................................................................... 27
4.4.1.1 Data Preparation............................................................................................................................................................ 27
4.4.1.2 Using MML Commands............................................................................................................................................... 32
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 37
4.4.2 Activation Verification......................................................................................................................................................37
4.4.2.1 Shortening Scheduling Periods..................................................................................................................................37

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. ii

eRAN
Air Interface Latency Optimization Feature
Parameter Description Contents

4.4.2.2 Raising Service Priorities.............................................................................................................................................. 38

4.4.2.3 Reducing the Number of Scheduling Times......................................................................................................... 39
4.4.2.4 Reducing Service Retransmissions............................................................................................................................41
4.4.3 Network Monitoring......................................................................................................................................................... 43

5 Parameters.............................................................................................................................. 47
6 Counters.................................................................................................................................. 48
7 Glossary................................................................................................................................... 49
8 Reference Documents...........................................................................................................50

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. iii

eRAN
Air Interface Latency Optimization Feature
Parameter Description 1 Change History

1 Change History

This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation

1.1 eRAN19.1 03 (2023-08-23)

This issue includes the following changes.

Technical Changes
None

Editorial Changes
Added descriptions of the impact relationship between air interface latency
optimization and in-band relay. For details, see 4.2.2 Impacts.

1.2 eRAN19.1 02 (2023-04-28)

This issue includes the following changes.

Technical Changes
None

Editorial Changes
Revised descriptions in this document.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 1

eRAN
Air Interface Latency Optimization Feature
Parameter Description 1 Change History

1.3 eRAN19.1 01 (2023-03-09)

This issue does not include any changes.

1.4 eRAN19.1 Draft A (2022-12-30)

This issue introduces the following changes to 18.1 01 (2022-03-08).

Technical Changes
Change Description Parameter Change RAT Base Station Model

Replaced the Replaced the FDD FDD:

parameter specifying QciPara.DlschPriority TDD ● 3900 and 5900
the weighting factor Factor parameter series base stations
used to calculate with the (macro base
downlink scheduling CellQciParaExten- stations)
priorities. For details, sion.DlSchPriorityWe
see Downlink ightFactor parameter. ● DBS3900 LampSite
Scheduling Priority and DBS5900
Optimization and LampSite
Raising Service TDD:
Priorities. ● 3900 and 5900
series base stations
(macro base
stations)
● DBS3900 LampSite
and DBS5900
LampSite

Canceled the None FDD ● BTS3912E

compatibility with the ● BTS3911E
BTS3912E and
BTS3911E as of this
version.

Editorial Changes
Revised descriptions in this document.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 2

eRAN
Air Interface Latency Optimization Feature
Parameter Description 2 About This Document

2 About This Document

2.1 General Statements

Purpose
This document is intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● 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 optimal gains, contact Huawei professional service engineers.
Functions mentioned in this document work properly only when enabled in the
specified applicable scenarios (such as RAT and networking). If a function not
mentioned in this document is enabled or a function is enabled in a scenario not
specified as applicable, exceptions or other impacts may occur.

Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this
document apply only to the corresponding software release. For future software
releases, refer to the corresponding updated product documentation.

Feature Differences Between RATs

The feature difference section only describes differences in switches or principles.
Unless otherwise stated, descriptions in this document apply to all RATs. If a
description does not apply to all RATs, the specific RAT that it does apply to will
be stated.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 3

eRAN
Air Interface Latency Optimization Feature
Parameter Description 2 About This Document

For example, in the statement "TDD cells are compatible with enhanced MU-
MIMO", "TDD cells" indicates that this function cannot be used in non-TDD cells.

2.2 Applicable RAT

This document applies to FDD/TDD.

2.3 Features in This Document

This document describes the following FDD features.
Feature ID Feature Name Chapter/Section

LEOFD-131214 Air Interface Latency 4 Air Interface

Optimization Latency
Optimization

This document describes the following TDD features.

Feature ID Feature Name Chapter/Section

TDLOFD-131214 Air Interface Latency 4 Air Interface

Optimization Latency
Optimization

2.4 Feature Differences Between FDD and TDD

FDD Feature TDD Feature Difference Chapter/Section

LEOFD-131214 TDLOFD-13121 FDD supports PDCCH 4 Air Interface

Air Interface 4 Air Interface boundary power Latency
Latency Latency control optimization Optimization
Optimization Optimization and QCI-specific TTI
bundling but TDD
does not.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 4

eRAN
Air Interface Latency Optimization Feature
Parameter Description 3 Overview

3 Overview

The rapid and stable development of LTE networks promotes the prosperity of the
mobile Internet. Besides data rates, coverage, and capacity, network latency has
become a new dimension for measuring user experience.
The end-to-end latency consists of the air interface latency and transmission
latency. The Air Interface Latency Optimization feature provides a solution that
shortens the air interface latency.
Data transmission over the air interface consists of two phases: air interface
transmission resource request waiting and air interface transmission. The Air
Interface Latency Optimization feature shortens the duration of the two phases to
shorten the air interface latency and improve experience of UEs running low-
latency services while ensuring service stability.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 5

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

4 Air Interface Latency Optimization

4.1 Principles
The Air Interface Latency Optimization feature includes the following
optimizations intended for different phases of data transmission over the air
interface:
● Shortening scheduling periods and raising service priorities to reduce the
waiting time for air interface transmission resource requests
● Reducing the number of scheduling times and reducing services
retransmissions to reduce the transmission duration over the air interface

After the core network sets up bearers carrying low-latency services and the
bearers are configured on the eNodeB to carry low-latency services (with the
CellQciPara.LowLatencyFlag parameter set to TRUE), the eNodeB uses the
following functions to shorten air interface latency for low-latency services.

Table 4-1 Air interface latency optimization functions

Optimization Function Low-Latency Service Optimization

Type Switch Must Be Turned Ona

4.1.1 Scheduling request Yes

Shortening indicator (SRI)
Scheduling reporting period
Periods optimization

Consecutive Yes
scheduling request
(SR)-based scheduling
optimization

Optimization for last Yes

packets

Preallocation No
optimization

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 6

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Optimization Function Low-Latency Service Optimization

Type Switch Must Be Turned Ona

Cell-edge Yes
preallocation
optimization

4.1.2 Raising DRX optimization No

Service
Priorities SR-based scheduling Yes
priority optimization

Downlink scheduling Yes

priority optimization

4.1.3 SR-based scheduling Yes

Reducing the data volume
Number of optimization
Scheduling
Times Resource block (RB) Yes
expansion for UEs
running low-latency
services and having
guaranteed bit rate
(GBR) bearers

Standard uplink data Yes

compression (UDC)
on low-latency
services

QCI-specific User Yes

Datagram Protocol
(UDP)-based robust
header compression
(ROHC)

4.1.4 Physical downlink Yes

Reducing control channel
Service (PDCCH) signal to
Retransmissi interference plus noise
ons ratio (SINR) offset
optimization

PDCCH boundary Yes

power control
optimization (FDD)

Precise modulation Yes

and coding scheme
(MCS) index reduction

QCI-specific Yes
transmission time
interval (TTI) bundling
(FDD)

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 7

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Optimization Function Low-Latency Service Optimization

Type Switch Must Be Turned Ona

MCS selection Yes

optimization

a: The Low-Latency Service Optimization Switch is indicated by the

LowDelayServiceOptSwitch option of the CellAlgoSwitch.ServiceDiffSwitch
parameter.
● If the value in this column is Yes for a function, the following are true: (1)
This function takes effect only after this option is selected. (2) This function
takes effect only for low-latency services that are newly established. (3) This
function does not take effect for services carried on bearers of QCI 1, 2, 5, 65,
66, 69, or 70. The requirement of selecting the LowDelayServiceOptSwitch
option will not be described again in enabling the corresponding function.
● If the value of this column is No for a function, this function can take effect
even though this option is not selected.

4.1.1 Shortening Scheduling Periods

The eNodeB optimizes SR-based scheduling or uses preallocation to shorten
scheduling periods of low-latency services and shorten the waiting time for
transmission resource requests over the air interface. As a result, the latency is
reduced and user experience of low-latency services is improved.
● SR-based scheduling
– SRI reporting period optimization
– Consecutive SR-based scheduling optimization
– Optimization for last packets
● Preallocation
– Preallocation optimization
– Cell-edge preallocation optimization

SRI Reporting Period Optimization

Before transmitting data, a UE sends the eNodeB an SR for data transmission
using the SRI on the physical uplink control channel (PUCCH). Upon receiving the
SR, the eNodeB responds to the SR and schedules resources for the UE.
After the SRI reporting period adaptation function is enabled, the SRI reporting
period allocated to UEs running low-latency services is extended to be greater
than 10 ms. This increases the uplink service latency and affects user experience of
such UEs. For details about SRI reporting period adaptation, see Physical Channel
Resource Management.
SRI reporting period optimization adaptively configures shorter SRI reporting
periods for low-latency services based on the cell load and the number of UEs
running low-latency services in a cell, shortening the latency and improving user
experience with low-latency services. This function is enabled when all of the
following conditions are met:

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 8

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

● The SRI_PERIOD_OPT_SW option of the CellQciPara.QciAlgoSwitch

parameter is selected.
● The PUCCHCfg.SriPeriodAdaptive parameter is set to QCIADAPTIVE.
● (FDD) The CellPucchAlgo.SriReCfgInd parameter is set to FALSE.
● (TDD) The cell bandwidth is greater than 3 MHz.
● (TDD) The Cell.SubframeAssignment parameter is set to SA1 or SA2.

NOTE

It is recommended that SRI reporting period optimization be used when the cell bandwidth
is at least 10 MHz.

Consecutive SR-based Scheduling Optimization

When the eNodeB responds to the SRs of UEs running low-latency services and
the amount of available scheduling resources for low-latency services is small, the
actual volume of scheduled data is less than the volume of data expected to be
scheduled. In this scenario, the UEs running low-latency services need to send
buffer status reports (BSRs) to the eNodeB, indicating the volume of data in the
uplink buffer, and wait for subsequent scheduling to complete uplink data
transmission. In this case, the service latency is long and user experience is poor.
Consecutive SR-based scheduling optimization is enabled if the
LOW_DELAY_UE_UL_SCH_OPT_SW option of the CellQciPara.QciAlgoSwitch
parameter is selected. If the volume of data actually transmitted by SR-based
scheduling for a UE in an uplink subframe is less than the value of the
CellQciPara.LowDelayUeSrSchMinDataVol parameter, which specifies the
volume of data expected to be transmitted by SR-based scheduling, the eNodeB
performs supplementary scheduling in the next uplink subframe and adds the
data volume to be scheduled to the BSR maintained by the eNodeB. If the data
volume indicated by the BSR maintained by the eNodeB is greater than 0, the
eNodeB continues scheduling the UE.
As shown in Figure 4-1, assume that the volume of data expected to be
transmitted by SR-based scheduling for a UE running low-latency services is 1500
bits, but the volume of data actually transmitted by SR-based scheduling is 1200
bits and the data volume indicated by the BSR is 300 bits. Before this function is
enabled, the eNodeB completes the scheduling of data whose volume is indicated
by the BSR in the TTIn, which prolongs the UE latency. After this function is
enabled, the eNodeB completes the scheduling of this data in TTI1 after SR-based
scheduling, which shortens the latency.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 9

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Figure 4-1 Consecutive SR-based scheduling optimization

Optimization for Last Packets

Optimization for last packets is enabled if the LOW_DELAY_UE_UL_SCH_OPT_SW
option of the CellQciPara.QciAlgoSwitch parameter is selected. When the
eNodeB completes the scheduling of data whose volume is indicated by the BSR
maintained by the eNodeB but does not receive the indication with Padding BSR
or BSR=0 during the last scheduling, the eNodeB proactively performs another
uplink scheduling to enable the UE to report its BSR to the eNodeB. In this way,
the scheduling period of low-latency services is shortened.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 10

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Figure 4-2 Optimization for last packets

Preallocation Optimization
During preallocation, the eNodeB proactively sends uplink scheduling indications
to UEs so that uplink data packets are scheduled in a timely manner and the
latency on UE scheduling is shortened. Through QCI-level preallocation
configurations, operators can set different preallocation parameter groups for
bearers with different QCIs. For details about QCI-level preallocation, see
Scheduling.
Through QCI-level preallocation configurations, preallocation optimization extends
the application scope of preallocation to low-latency bearers, improving user
experience with low-latency services. Figure 4-3 illustrates the principles of
normal preallocation. Normal preallocation and smart preallocation are controlled
by the PreAllocationSwitch and SmartPreAllocationSwitch options of the
CellAlgoSwitch.UlSchSwitch parameter, respectively. A preallocation parameter
group is defined by a CellPreallocGroup MO. This preallocation parameter group
can be mapped to low-latency bearers through a CellQciPara MO.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 11

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Figure 4-3 Normal preallocation

Cell-Edge Preallocation Optimization

The uplink SINR is low, the service latency is long, and user experience is poor for
UEs running low-latency services at the cell edge.

Cell-edge preallocation optimization is intended for cell edge UEs running low-
latency services whose uplink SINR values are lower than the threshold specified
by CellQciPara.LowDelayCeuPreallocOptThld. With this function enabled, uplink
preallocation for these UEs is not limited by the number of UEs in the cell and the
proportion of preallocated RBs. In this case, preallocation for UEs running low-
latency services can take effect continuously. As a result, the latency is reduced
and user experience is improved. This function is enabled when all of the following
conditions are met:

● The LOW_DELAY_UE_UL_SCH_OPT_SW option of the

CellQciPara.QciAlgoSwitch parameter is selected.
● The CellQciPara.LowDelayCeuPreallocOptThld parameter is set to a value
other than -51.

4.1.2 Raising Service Priorities

The eNodeB uses the following functions to increase scheduling priorities of low-
latency services and reduce the waiting time for air interface transmission resource
requests, thereby shortening the latency and improving user experience of low-
latency services:
● DRX optimization
● SR-based scheduling priority optimization
● Downlink scheduling priority optimization

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 12

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

DRX Optimization
After DRX takes effect, the UE power consumption is reduced while the service
latency increases. When DRX takes effect for UEs running low-latency services, the
increase in the air interface latency leads to user experience deterioration.
When QCI-specific DRX is used, DRX optimization prevents the extra scheduling
latency caused by DRX sleep and improves user experience of low-latency services
by disabling DRX in a DRX parameter group for bearers of low-latency services (by
setting the DrxParaGroup.EnterDrxSwitch parameter to OFF in the DRX
parameter group).
For details about QCI-specific DRX parameter configurations, see DRX and
Signaling Control.

SR-based Scheduling Priority Optimization

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 priorities for
low-latency services are low in SR-based scheduling. As a result, the latency is
long. In addition, the latency increases with the load, affecting user experience of
low-latency services.
SR-based scheduling priority optimization raises the SR-based scheduling priorities
for low-latency services to be higher than those for other data services. This
shortens the scheduling waiting time, shortens the service latency, and improves
user experience of low-latency services. This function is enabled when all of the
following conditions are met:
● The SR_PRIORITY_DATA_OPT_SW option of the CellQciPara.QciAlgoSwitch
parameter is selected.
● (TDD) The CellUlschAlgo.UlDelaySchStrategy parameter is set to
NO_DELAYSCH or VOIP_AND_DATA_DELAYSCH.

Downlink Scheduling Priority Optimization

In earlier versions, only voice service bearers but not bearers carrying low-latency
services are configured with special scheduling priorities. To ensure that the
latency of low-latency services is short in all scenarios, a special scheduling priority
needs to be configured for bearers carrying 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 to bearers carrying
low-latency services to ensure that the priority is higher than the downlink
scheduling priority of bearers carrying non-low-latency services.
● For GBR bearers, this function takes effect only for QCIs 3 and 4.
● For non-GBR bearers, this function takes effect only for QCI 6 through QCI 9
and other non-GBR QCIs excluding QCIs 69 and 70. The
CellQciParaExtension.DlSchPriorityWeightFactor parameter can be used to
differentiate the priorities of different non-GBR low-latency services.

4.1.3 Reducing the Number of Scheduling Times

The eNodeB increases the volume of data to be scheduled at a time or reduces
the size of data packets to be scheduled to reduce the number of scheduling

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 13

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

times. This shortens the transmission duration over the air interface, shortens the
latency, and improves user experience of low-latency services.
● Increasing the volume of data to be scheduled at a time
– SR-based scheduling data volume optimization
– RB expansion for UEs running low-latency services and having GBR
bearers
● Reducing the size of data packets to be scheduled
– Standard UDC on low-latency services
– QCI-specific UDP-based ROHC

SR-based Scheduling Data Volume Optimization

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 volume of
data transmitted by SR-based scheduling is small, and services need to be
scheduled multiple times. As a result, the latency is long. In addition, as the load
increases, the volume of data transmitted by SR-based scheduling further
decreases, affecting user experience of low-latency services.
SR-based scheduling data volume optimization is enabled if the
SR_PRIORITY_DATA_OPT_SW option of the CellQciPara.QciAlgoSwitch
parameter is selected. This function increases the volume of data that can be
transmitted by SR-based scheduling for low-latency services. The minimum
volume of data that can be transmitted by SR-based scheduling is specified by the
CellQciPara.LowDelayUeSrSchMinDataVol parameter. This reduces the number
of scheduling times and service latency, improving user experience of low-latency
services.
NOTE

If the UE capability is limited, the actual volume of data transmitted by SR-based

scheduling may be less than the CellQciPara.LowDelayUeSrSchMinDataVol parameter
value.

RB Expansion for UEs Running Low-Latency Services and Having GBR

Bearers
RB expansion for UEs running low-latency services and having GBR bearers fully
utilizes uplink resources and increases uplink throughput for UEs running low-
latency services, without increasing the total interference power. With this function
enabled, optimized scheduling upon full uplink power takes effect for UEs running
low-latency services and having GBR bearers. For details about optimized
scheduling upon full uplink power, see Scheduling. This function is enabled when
all of the following options are selected:
● SchedulerCtrlPowerSwitch option of the CellAlgoSwitch.UlSchSwitch
parameter
● UlSchRbAllocOptSw option of the CellAlgoSwitch.UlSchExtSwitch
parameter
● (FDD) LOW_DELAY_UE_UL_SCH_OPT_SW option of the
CellQciPara.QciAlgoSwitch parameter
● (TDD) LOW_DELAY_UE_UL_SCH_OPT_SW or SR_PRIORITY_DATA_OPT_SW
option of the CellQciPara.QciAlgoSwitch parameter

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 14

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Standard UDC on Low-Latency Services

Standard UDC compresses uplink data packets (including TCP/IP headers and
payloads) sent by UEs, reducing the amount of air interface resources required for
transmitting the same volume of data.

Standard UDC on low-latency services allows standard UDC to be enabled for

bearers carrying low-latency services. Standard UDC can be enabled
simultaneously for a maximum of two bearers for a single UE. If standard UDC
cannot be enabled for bearers carrying low-latency services because non-QCI-5
bearers occupy the specifications of standard UDC, this function triggers a
preemption procedure and enables established bearers carrying non-low-latency
services to exit standard UDC. In this way, standard UDC is enabled for bearers
carrying low-latency services. This function is enabled when all of the following
options are selected:
● LOW_DELAY_UE_UL_SCH_OPT_SW option of the CellQciPara.QciAlgoSwitch
parameter
● UL_DEFLATE_DATA_COMPRESSION_SW option of the
CellDataComprConfig.StandardUdcSwitch parameter

As shown in Figure 4-4, standard UDC is enabled for QCI-5 and QCI-2 bearers.
Before this function takes effect, standard UDC cannot be enabled for the QCI-3
bearer, which carries a low-latency service. After this function takes effect, the
QCI-3 bearer preempts the standard UDC specifications from the QCI-2 bearer.

Figure 4-4 Standard UDC on low-latency services

QCI-specific UDP-based ROHC

ROHC is a mechanism for compressing the headers of data packets transmitted
over the air interface. When the air interface capability is limited, this function
reduces the volume of data transmitted over the air interface, decreases the
probability of RLC segmentation, and shortens the air interface latency.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 15

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

QCI-specific UDP-based ROHC is enabled if the QCI_ROHC_SWITCH option of the

CellQciPara.QciAlgoSwitch parameter is selected. This function allows ROHC to
take effect on bearers carrying low-latency services, thereby shortening the
interaction response time of low-latency services, reducing the latency of UEs
running low-latency services, and improving user experience.

It is recommended that this function be enabled when the

RlcPdcpParaGroup.RlcMode parameter is set to RlcMode_UM for a bearer
carrying low-latency services. Otherwise, the uplink packet loss rate of the bearer
increases significantly.

NOTE

Uplink packet loss rate of a bearer carrying low-latency services =

L.Traffic.UL.PktLoss.Loss.QCI.n/L.Traffic.UL.PktLoss.Tot.QCI.n
QCI.n specifies the QCI marked with the low-latency service flag.

For details about the ROHC, see ROHC.

4.1.4 Reducing Service Retransmissions

The eNodeB uses the following functions to reduce uplink or downlink service
retransmissions, thereby reducing the transmission duration over the air interface,
shortening the latency, and improving user experience of low-latency services:
● Uplink & downlink
– PDCCH SINR offset optimization
– PDCCH boundary power control optimization (FDD)
● Uplink
– Precise MCS index reduction
– QCI-specific TTI bundling (FDD)
● Downlink
– MCS selection optimization

PDCCH SINR Offset Optimization

The PDCCH transmits the following types of downlink control information (DCI):
downlink grant, uplink grant, and power control commands. 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.
A higher PDCCH aggregation level indicates a lower PDCCH block error rate
(BLER). The eNodeB can select an appropriate PDCCH aggregation level based on
channel quality, which reduces the PDCCH BLER to a target value.

PDCCH SINR offset optimization is enabled if the CellQciPara.QciPdcchSinrOffset

parameter is not set to 0. This function takes effect only when the control channel
element (CCE) usage is less than 60%. This function allocates a dedicated PDCCH
SINR offset for bearers carrying low-latency services. In this way, a higher PDCCH
CCE aggregation level can be selected for UEs running low-latency services than
other UEs, mitigating the latency introduced by the PDCCH block errors and
improving user experience of UEs running low-latency services. Figure 4-5
illustrates the procedure.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 16

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Figure 4-5 PDCCH SINR offset optimization

PDCCH Boundary Power Control Optimization (FDD)

When the PDCCH aggregation level reaches 8, the eNodeB increases the PDCCH
power by 1 dB for a UE each time the eNodeB detects three consecutive
discontinuous transmissions (DTXs) for the UE. The power increase is relatively
slow.

PDCCH boundary power control optimization 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%. This function accelerates the
increase in the PDCCH power, reduces the DTX waiting time, and improves user
experience of low-latency services.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 17

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Precise MCS Index Reduction

If the transport block size (TBS) is greater than the volume of data to be
scheduled and MCS index selected for a UE is excessively high, block errors will
occur, decreasing uplink transmission reliability and thereby causing uplink
retransmissions. As a result, the UE latency is prolonged.

Precise MCS index reduction selects a precise MCS index for a UE running low-
latency services by lowering the selected MCS index if the TBS is greater than the
volume of data to be scheduled. This reduces the number of block errors and the
number of retransmissions, shortening the UE latency. If the scheduling type is
preallocation for non-cell-edge UEs, the MCS index will not be lowered. This
function is enabled when all of the following options are selected:
● LOW_DELAY_UE_UL_SCH_OPT_SW option of the CellQciPara.QciAlgoSwitch
parameter
● LOW_DELAY_UE_UL_MCS_IDX_RDC_SW option of the
CellQciPara.QciAlgoSwitch parameter

Figure 4-6 Precise MCS index reduction

QCI-specific TTI Bundling (FDD)

TTI bundling enables a data block to be transmitted in four consecutive TTIs,
which are bound together and treated as the same resource. Different hybrid
automatic repeat request (HARQ) redundancy versions of the same data block are
transmitted in different TTIs. TTI bundling reduces the number of retransmissions
and shortens the UE latency.

QCI-specific TTI bundling is enabled if the QCI_TTI_BUNDLING_SWITCH option of

the CellQciPara.QciAlgoSwitch parameter is selected. This function allows TTI
bundling to take effect for bearers carrying low-latency services.

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:
● 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:

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 18

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

– 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 times SINR measurement values are consecutively less
than the target SINR value is greater than the threshold for entering the
TTI bundling state. (The threshold is defined by the
CellUlschAlgo.StatisticNumThdForTtibTrig parameter.)
When a UE runs both a low-latency service and a VoLTE service, the base
station determines whether to enable the UE to enter the TTI bundling state
based on the TTI bundling entry conditions. When the UE runs a low-latency
service but not a VoLTE service, the base station determines whether to
enable the UE to enter the TTI bundling state based on the QCI-specific TTI
bundling entry conditions.
● 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 times SINR measurement values are consecutively greater
than the target value is greater than the threshold for exiting the TTI
bundling state. (The threshold is defined by the
CellUlschAlgo.StatisticNumThdForTtibExit parameter.) The target value
is the sum of the target SINR value and the
CellUlschAlgo.HystToExitTtiBundling parameter value.
– Bearers carrying low-latency services have been released.
When a UE in the TTI bundling state runs both a low-latency service and a
VoLTE service, the base station determines whether to enable the UE to exit
the TTI bundling state based on the TTI bundling exit conditions. When the
UE in the TTI bundling state runs a low-latency service but not a VoLTE
service, the base station determines whether to enable the UE to exit the TTI
bundling state based on the QCI-specific TTI bundling exit conditions.
● 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.
NOTE

The target SINR is specified as follows:

● The CellTtiBundlingAlgo.SinrThdToTrigR12TtiB parameter specifies the target
SINR when the CellTtiBundlingAlgo.R12TtiBundlingSwitch parameter is set to
ON.
● The CellQciPara.QciSinrThldForTrigTtibB parameter specifies the target SINR
when the CellTtiBundlingAlgo.R12TtiBundlingSwitch parameter is set to OFF.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 19

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

MCS Selection Optimization

During downlink scheduling for a UE, the eNodeB automatically selects an MCS
index for data transmission based on the channel quality indicator (CQI) reported
by the UE. In addition, the eNodeB evaluates the difference between the channel
quality indicated by the reported CQI and actual channel quality based on HARQ
feedback and then adjusts the CQI based on the difference so that the initial block
error rate (IBLER) can be reduced to a target optimum value.
When the UE is located in an area with weak coverage or experiences strong
interference, the IBLER is high or is reduced 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.
MCS selection optimization is enabled if the CellQciPara.DecreaseInNackCqiAdj
parameter is not set to 0. This function specifies the decrease in the CQI value for
low-latency services when 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, and thereby lower MCS indexes can be selected for UEs. This
reduces the impacts of PDSCH block errors on the packet loss rate and latency and
improves user experience of low-latency services.

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.
● 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.
● On a medium- or light-load network, the air interface RTT of UEs running
low-latency services decreases by 7% to 25%. When the downlink PRB usage
is less than 50%, uplink PRB usage is less than 30%, and the number of UEs
online is greater than the CellUlschAlgo.PreallocationUserCntThld
parameter value, the network load is medium or light.

4.2.2 Impacts
Network Impacts
If there are excessive UEs running low-latency services, function impacts on
network performance are as follows:
● Shortening scheduling periods
– 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.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 20

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

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
QCI n specifies the QCI marked with the low-latency service flag.
– Consecutive SR-based scheduling optimization, optimization for last
packets, and cell-edge preallocation optimization
The timeliness of uplink scheduling for UEs running low-latency services
is improved. This leads to the following impacts: Uplink cell throughput,
uplink user-perceived rates in the cell, and spectral efficiency decrease.
Uplink interference, the number of RBs used for preallocation in the cell,
uplink PRB usage of the cell, and the number of active UEs in the cell
increase. The uplink block error rate and the number of UEs scheduled in
the uplink may fluctuate. The CCE usage and number of PDCCH symbols
may increase.
– Preallocation optimization
The uplink PRB usage, uplink interference, and CCE usage increase. The
uplink IBLER decreases.
● Raising service priorities
– DRX optimization
The UE power consumption and the RRC signaling in the cell increase.
– SR-based scheduling priority optimization
The SR-based scheduling priorities are increased for UEs running low-
latency services. As a result, uplink user-perceived rates of other UEs
decrease.
– 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.
● Reducing the number of scheduling times
– SR-based scheduling data volume optimization
The volume of scheduled data is increased for UEs running low-latency
services. As a result, uplink user-perceived rates of other UEs decrease.
– RB expansion for UEs running low-latency services and having GBR
bearers and standard UDC on low-latency services
The timeliness of uplink scheduling for UEs running low-latency services
is improved and data packets of low-latency services are compressed. This
leads to the following impacts: Uplink cell throughput, uplink user-
perceived rates in the cell, and spectral efficiency decrease. Uplink
interference, the number of RBs used for preallocation in the cell, uplink
PRB usage of the cell, and the number of active UEs in the cell increase.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 21

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

The uplink block error rate and the number of UEs scheduled in the
uplink may fluctuate. The CCE usage and number of PDCCH symbols may
increase.
– QCI-specific UDP-based ROHC
QCI-specific UDP-based ROHC reduces the volume of data transmitted
over the air interface, decreasing the traffic volume.
● Reducing service retransmissions
– PDCCH SINR offset optimization
The average PDCCH aggregation level and equivalent CCE usage increase.
– 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.
– Precise MCS index reduction
The uplink cell throughput, uplink user-perceived rates, and uplink MCS
index decrease.
– 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.
– MCS selection optimization
The downlink PRB usage increases, and the downlink IBLER decreases. For
services that use small, sparse packets, the downlink packet delay
decreases. For services that use large packets, the downlink packet delay
increases due to packet fragmentation possibly caused by the decrease of
the downlink MCS index.

Function Impacts
Besides the following function impacts, preallocation optimization has the same
function impacts as preallocation and QCI-specific TTI bundling has the same
function impacts as TTI bundling. For details about the function impacts of
preallocation and TTI bundling, see Scheduling and VoLTE, respectively.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 22

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

RAT Function Function Switch Reference Description

Name

FDD Turbo start CellAlgoSwitch.RohcS Video When both turbo start video and
TDD video witch parameter with Experience QCI-specific UDP-based ROHC
the value of ON and Optimizatio are enabled, these two functions
PdcpRohcPara.Profile n can take effect simultaneously
s parameter with the on separate bearers with
value of different QCIs for a UE.
Profile0x0006 However, only the function that
meets conditions to take effect
first takes effect on bearers with
the same QCI for the UE.

FDD Uplink data FDD: Uplink Data When both uplink data
TDD compression CellDataComprCon- Compression compression and QCI-specific
fig.StandardUdcSwitc UDP-based ROHC are enabled,
h these two functions can take
TDD: effect simultaneously on
CellDataComprCon- separate bearers with different
fig.StandardUdcSwitc QCIs for a UE. However, only the
h parameter and function that meets conditions
BasicUdcSwitch to take effect first takes effect
option of the on bearers with the same QCI
CellAlgoSwitch.UdcAl for the UE.
goSwitch parameter
FDD Out-of-band OutOfBandRelaySwit Relay ● The following functions
TDD relay ch option of the cannot be used for UEs in an
CellAlgoSwitch.Relay out-of-band relay cell:
Switch parameter – Cell-edge preallocation
optimization
– Consecutive SR-based
scheduling optimization
– Optimization for last
packets
– RB expansion for UEs
running low-latency
services and having GBR
bearers
– Standard UDC on low-
latency services
– Precise MCS index
reduction
● The
CellQciPara.LowDelayUeSrS
chMinDataVol parameter
setting does not take effect
for UEs in an out-of-band
relay cell.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 23

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

RAT Function Function Switch Reference Description

Name

FDD In-band InBandRelayDeNbS- Relay ● The following functions

TDD relay witch option of the cannot be used for UEs in an
CellAlgoSwitch.Relay in-band relay cell:
Switch parameter – Cell-edge preallocation
optimization
– Consecutive SR-based
scheduling optimization
– Optimization for last
packets
– RB expansion for UEs
running low-latency
services and having GBR
bearers
– Standard UDC on low-
latency services
– Precise MCS index
reduction
– QCI-specific UDP-based
ROHC
– QCI-specific TTI bundling
● The
CellQciPara.LowDelayUeSrS
chMinDataVol parameter
setting does not take effect
for UEs in an in-band relay
cell.

FDD Inter- UlCompForVideoS- Video 3GPP Release 12-compliant TTI

eNodeB UL witch option of the Experience bundling eHARQa and inter-
CoMP for CellAlgoSwitch.Uplin Optimizatio eNodeB UL CoMP for video
video kCompSwitch n services cannot take effect
services parameter simultaneously for a UE that
meets the conditions for
entering the QCI-specific TTI
bundling state.

FDD TDM power NSA_DC_ENH_UL_PO NSA SRI reporting period

control WER_CONTROL_SW Networking optimization takes precedence
and TDM_SWITCH based on over TDM power controlb.
options of the EPC
NsaDcMgmtConfig.N
saDcAlgoSwitch
parameter

a: For details about 3GPP Release 12-compliant TTI bundling eHARQ, see VoLTE.
b: SRI reporting period optimization takes precedence over TDM power control.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 24

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

● When TDM power control has not taken effect and SRI reporting period
optimization takes effect, TDM power control cannot take effect.
● When TDM power control takes effect, SRI reporting period optimization can
still take effect. TDM power control no longer takes effect after SRI reporting
period optimization takes effect.

4.3 Requirements

4.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LEOFD-131214 Air Interface LT1S00AIL per Cell

Latency O00
Optimization

TDD TDLOFD-131214 Air Interface LT4SAIRIL per Cell

Latency O00
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.

Prerequisite Functions
RAT Function Name Function Switch Referenc Description
e

FDD Standard uplink UL_DEFLATE_DA Uplink Only standard

TDD data compression TA_COMPRESSIO Data UDC on low-
N_SW option of Compress latency services
the ion requires this
CellDataComprC function.
onfig.StandardU
dcSwitch
parameter

Mutually Exclusive Functions

For FDD, QCI-specific TTI bundling has the same mutually exclusive functions as
TTI bundling. For details about the mutually exclusive functions of TTI bundling,
see VoLTE.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 25

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

4.3.3 Hardware
The hardware described in this section may require compatibility between each
other. For details, see the technical specifications and hardware description of the
corresponding hardware in 3900 & 5900 Series Base Station Product
Documentation.

Base Station Models

FDD:

● 3900 and 5900 series base stations (macro base stations)

● DBS3900 LampSite and DBS5900 LampSite

TDD:

● 3900 and 5900 series base stations (macro base stations)

● DBS3900 LampSite and DBS5900 LampSite

Boards
The LBBPc does not support this function.

RF Modules
No requirements

4.3.4 Others
● Core network
To provide differentiated guarantee for low-latency services, the core network
must support the setup of bearers carrying low-latency services, and low-
latency services must not be set up on the same bearer as other services.
● UEs
– UEs must support bearers carrying low-latency services.
– When the following functions are enabled, UEs must not be eMTC UEs or
CE UEs working in eMTC mode:

▪ Cell-edge preallocation optimization

▪ Consecutive SR-based scheduling optimization

▪ Optimization for last packets

▪ RB expansion for UEs running low-latency services and having GBR

bearers

▪ Standard UDC on low-latency services

▪ Precise MCS index reduction

– When precise MCS index reduction is enabled, rank 1 transmission is
required for UEs for which uplink single-user MIMO (SU-MIMO) has

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 26

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

taken effect when the UEs are running low-latency services. For details
about rank selection in uplink SU-MIMO, see MIMO.
– Standard UDC for low-latency services requires UEs to support 3GPP
Release 15-compliant standard UDC.
– QCI-specific UDP-based ROHC requires UEs to support ROHC profile 2.
– (FDD) QCI-specific TTI bundling requires UEs to support TTI bundling. For
details, see VoLTE.

4.4 Operation and Maintenance

4.4.1 Data Configuration

4.4.1.1 Data Preparation

Common Parameters
Table 4-2 describes the parameters used for function activation.

Table 4-2 Parameters used for activation

RAT Paramete Parameter ID Option Setting Notes
r Name

FDD Low CellQciPara.L None When a QCI is planned to be

TDD Latency owLatencyFl used for low-latency services,
Flag ag 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.

FDD Service CellAlgoSwit LowDelay Select this option.

TDD Differenti ch.ServiceDiff ServiceOp
ated Switch tSwitch
Switch

Shortening Scheduling Periods

Table 4-3 describes the parameters used for function activation.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 27

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Table 4-3 Parameters used for activation

RAT Paramete Parameter ID Option Setting Notes
r Name

FDD QCI CellQciPara. SRI_PERI To enable SRI reporting period

TDD Algorithm QciAlgoSwitc OD_OPT_ optimization, select this
Switch h SW option.

FDD SRI Period PUCCHCfg.Sri None To enable SRI reporting period

TDD Adaptive PeriodAdapti optimization, set this
Switch ve parameter to QCIADAPTIVE.

FDD QCI CellQciPara. LOW_DEL To enable the following

TDD Algorithm QciAlgoSwitc AY_UE_U functions, select this option.
Switch h L_SCH_O ● Consecutive SR-based
PT_SW scheduling optimization
● Optimization for last
packets
● Cell-edge preallocation
optimization

FDD Low CellQciPara.L None To enable SR-based scheduling

TDD Delay UE owDelayUeSr optimization, set this
SR-based SchMinDataV parameter to its
Sch Min ol recommended value.
Data
Volume

FDD Uplink CellAlgoSwit PreAllocat To enable preallocation

TDD schedule ch.UlSchSwit ionSwitch optimization, select these
switch ch SmartPre options.
Allocation
Switch

FDD Preallocat CellPreallocG None To enable preallocation

TDD ion roup.Prealloc optimization, configure a valid
Paramete ationParaGro preallocation parameter group
r Group upId ID for bearers carrying low-
ID latency services.

FDD Low CellQciPara.L None To enable cell-edge

TDD Delay owDelayCeu preallocation optimization, set
CEU PreallocOptT this parameter to a value
Preallocat hld other than -51.
ion Opt
Thld

FDD SRI CellPucchAlg None To enable SRI reporting period

Reconfigu o.SriReCfgInd optimization, set this
ration parameter to FALSE.
Indicator

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 28

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

RAT Paramete Parameter ID Option Setting Notes

r Name

TDD Subframe Cell.Subfram None To enable SRI reporting period

assignme eAssignment optimization, set this
nt parameter to SA1 or SA2.

Raising Service Priorities

Table 4-4 describes the parameters used for function activation.

Table 4-4 Parameters used for activation

RAT Paramete Parameter ID Option Setting Notes

r Name

FDD Enter DRX DrxParaGrou None Set this parameter to OFF if

TDD Switch p.EnterDrxSw DRX is not required for UEs
itch running low-latency services.
If bearers carrying low-latency
services and bearers carrying
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
and downlink BLERs increase.
To prevent this from
happening, configure a
dedicated group of DRX
parameters for bearers
carrying low-latency services.

FDD QCI CellQciPara. SR_PRIOR To enable SR-based scheduling

TDD Algorithm QciAlgoSwitc ITY_DATA priority optimization, select
Switch h _OPT_SW this option.

FDD QCI CellQciPara. DL_SCH_P To enable downlink scheduling

TDD Algorithm QciAlgoSwitc RIORITY_ priority optimization, select
Switch h OPT_SW this option.

FDD Downlink CellQciParaE None If downlink scheduling priority

TDD Schedulin xtension.DlSc optimization is enabled, this
g Priority hPriorityWei parameter specifies the
Weight ghtFactor priority of a non-GBR bearer
Factor carrying low-latency services.

TDD Uplink CellUlschAlg None To enable SR-based scheduling

Delay- o.UlDelaySch priority optimization, set this
based Strategy parameter to NO_DELAYSCH
Schedulin or
g Strategy VOIP_AND_DATA_DELAYSCH.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 29

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Reducing the Number of Scheduling Times

Table 4-5 describes the parameters used for function activation.

Table 4-5 Parameters used for activation

RAT Paramete Parameter ID Option Setting Notes
r Name

FDD QCI CellQciPara. SR_PRIOR To enable the following

TDD Algorithm QciAlgoSwitc ITY_DATA functions, select this option.
Switch h _OPT_SW ● SR-based scheduling data
volume optimization
● (TDD) RB expansion for
UEs running low-latency
services and having GBR
bearersa

FDD Low CellQciPara.L None To enable SR-based scheduling

TDD Delay UE owDelayUeSr data volume optimization, set
SR-based SchMinDataV this parameter to its
Sch Min ol recommended value.
Data
Volume

FDD QCI CellQciPara. LOW_DEL To enable the following

TDD Algorithm QciAlgoSwitc AY_UE_U functions, select this option.
Switch h L_SCH_O ● Standard UDC on low-
PT_SW latency services
● (TDD) RB expansion for
UEs running low-latency
services and having GBR
bearersa

FDD Uplink CellAlgoSwit Scheduler To enable RB expansion for

TDD schedule ch.UlSchSwit CtrlPower UEs running low-latency
switch ch Switch services and having GBR
bearers, select these options.
FDD Uplink CellAlgoSwit UlSchRbA
TDD Schedule ch.UlSchExtS llocOptSw
Extended witch
Switch

FDD Standard CellDataCom UL_DEFL To enable standard UDC on

TDD UDC prConfig.Sta ATE_DAT low-latency services, select
Switch ndardUdcSwi A_COMPR this option.
tch ESSION_S
W

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 30

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

RAT Paramete Parameter ID Option Setting Notes

r Name

FDD QCI CellQciPara. QCI_ROH To enable QCI-specific UDP-

TDD Algorithm QciAlgoSwitc C_SWITC based ROHC, select this
Switch h H option.

a: To enable RB expansion for UEs running low-latency services and having GBR
bearers, select the corresponding option as follows:
● In FDD, select the LOW_DELAY_UE_UL_SCH_OPT_SW option.
● In TDD, select either the LOW_DELAY_UE_UL_SCH_OPT_SW or
SR_PRIORITY_DATA_OPT_SW option.

Reducing Service Retransmissions

Table 4-6 describes the parameters used for function activation.

Table 4-6 Parameters used for activation

RAT Paramete Parameter ID Option Setting Notes
r Name

FDD QCI CellQciPara. None To enable PDCCH SINR offset

TDD PDCCH QciPdcchSinr optimization, set this
SINR Offset parameter to its
Offset recommended value.

FDD QCI CellQciPara. LOW_DEL To enable precise MCS index

TDD Algorithm QciAlgoSwitc AY_UE_U reduction, select these options.
Switch h L_SCH_O
PT_SW
LOW_DEL
AY_UE_U
L_MCS_ID
X_RDC_S
W

FDD Decrease CellQciPara.D None To enable MCS selection

TDD in NACK ecreaseInNac optimization, set this
CQI kCqiAdj parameter to its
Adjustme recommended value.
nt

FDD QCI CellQciPara. PDCCH_B To enable PDCCH boundary

Algorithm QciAlgoSwitc OUNDAR power control optimization,
Switch h Y_PWR_C select this option.
TRL_OPT_
SW

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 31

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

RAT Paramete Parameter ID Option Setting Notes

r Name

FDD QCI CellQciPara. QCI_TTI_B To enable QCI-specific TTI

Algorithm QciAlgoSwitc UNDLING bundling, select this option.
Switch h _SWITCH

FDD Statistic CellUlschAlg None To enable QCI-specific TTI

Num o.StatisticNu bundling, set these parameters
Threshold mThdForTtib to their recommended values.
for TTIB Trig
Trigger

FDD Statistic CellUlschAlg None

Num o.StatisticNu
Threshold mThdForTtib
for TTIB Exit
Exit

FDD Hysteresis CellUlschAlg None

to Exit TTI o.HystToExitT
Bundling tiBundling
FDD SINR CellTtiBundli None This parameter specifies the
Threshold ngAlgo.SinrT target SINR when the
To Trigger hdToTrigR12 CellTtiBundlingAl-
R12 TTI TtiB go.R12TtiBundlingSwitch
Bundling parameter is set to ON.

FDD SINR Thld CellQciPara. None This parameter specifies the

for QciSinrThldF target SINR when the
Triggering orTrigTtibB CellTtiBundlingAl-
QCI TTI go.R12TtiBundlingSwitch
Bundling parameter is set to OFF.

4.4.1.2 Using MML Commands

Before using MML commands, confirm the related parameter modification
precautions by referring to the fields including "Service Interrupted After
Modification" and "Caution" for the corresponding parameters in the parameter
reference.
The following are examples where QCI 3, 131, or 151 is marked with a low-latency
service flag.

Activation Command Examples (FDD)

Before using MML commands, refer to 4.2.2 Impacts and 4.3.2 Software and
complete the parameter configurations for related functions based on the impact,
dependency, and mutually exclusive relationships between the functions, as well
as the actual network scenario.
//Configuring common parameters
//Configuring bearers for low-latency services (QCIs 3, 131, and 151 are used as examples)

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 32

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, LowLatencyFlag=TRUE;

MOD CELLQCIPARA: LocalCellId=0, Qci=131, LowLatencyFlag=TRUE;
MOD CELLQCIPARA: LocalCellId=0, Qci=151, LowLatencyFlag=TRUE;
//Turning on the general switch that controls air interface latency optimization
MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=LowDelayServiceOptSwitch-1;

//Enabling the functions that are used for shortening scheduling periods
//Enabling SRI reporting period optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SRI_PERIOD_OPT_SW-1;
MOD PUCCHCFG: LocalCellId=0, SriPeriodAdaptive=QCIADAPTIVE;
MOD CELLPUCCHALGO: LocalCellId=0, SriReCfgInd=FALSE;

//Enabling consecutive SR-based scheduling optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1,
LowDelayUeSrSchMinDataVol=1500;

//Enabling optimization for last packets

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1;

//Enabling preallocation optimization

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;

//Enabling cell-edge preallocation optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1,
LowDelayCeuPreallocOptThld=30;

//Enabling the functions that are used for raising service priorities
//Enabling DRX optimization (disabling DRX in DRX parameter group 4 for QCI-3 bearers carrying low-
latency services)
MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=4, EnterDrxSwitch=OFF;

//Enabling SR-based scheduling priority optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-1;

//Enabling downlink scheduling priority optimization for GBR bearers

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-1;
//Enabling downlink scheduling priority optimization for non-GBR bearers
MOD CELLQCIPARA: LocalCellId=0, Qci=131, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-1;
MOD CELLQCIPARA: LocalCellId=0, Qci=151, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-1;
MOD CELLQCIPARAEXTENSION: LocalCellId=0, Qci=131, DlSchPriorityWeightFactor=930;
MOD CELLQCIPARAEXTENSION: LocalCellId=0, Qci=151, DlSchPriorityWeightFactor=900;

//Enabling the functions that are used for reducing the number of scheduling times
//Enabling SR-based scheduling data volume optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-1,
LowDelayUeSrSchMinDataVol=1500;

//Enabling RB expansion for UEs running low-latency services and having GBR bearers
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1;
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=SchedulerCtrlPowerSwitch-1,
UlSchExtSwitch=UlSchRbAllocOptSw-1;

//Enabling standard UDC on low-latency services

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1;
MOD CELLDATACOMPRCONFIG: LocalCellId=0,
StandardUdcSwitch=UL_DEFLATE_DATA_COMPRESSION_SW-1;

//Enabling QCI-specific UDP-based ROHC

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=QCI_ROHC_SWITCH-1;

//Enabling the functions that are used for reducing service retransmissions
//Enabling PDCCH SINR offset optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciPdcchSinrOffset=30;

//Enabling PDCCH boundary power control optimization

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 33

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=PDCCH_BOUNDARY_PWR_CTRL_OPT_SW-1;

//Enabling precise MCS index reduction

MOD CELLQCIPARA: LocalCellId=0, Qci=3,
QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1&LOW_DELAY_UE_UL_MCS_IDX_RDC_SW-1;

//Enabling QCI-specific TTI bundling

//Assume that CellTtiBundlingAlgo.R12TtiBundlingSwitch is set to ON.
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=QCI_TTI_BUNDLING_SWITCH-1;
MOD CELLTTIBUNDLINGALGO: LocalCellId=0, SinrThdToTrigR12TtiB=3;
//Assume that CellTtiBundlingAlgo.R12TtiBundlingSwitch is set to OFF.
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=QCI_TTI_BUNDLING_SWITCH-1,
QciSinrThldForTrigTtibB=3;
//Setting the StatisticNumThdForTtibTrig, StatisticNumThdForTtibExit, and HystToExitTtiBundling parameters
MOD CELLULSCHALGO: LocalCellId=0, StatisticNumThdForTtibTrig=N10_TTIB_ENTER,
StatisticNumThdForTtibExit=N20_TTIB_EXIT, HystToExitTtiBundling=5;

//Enabling MCS selection optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, DecreaseInNackCqiAdj=10;

Activation Command Examples (TDD)

Before using MML commands, refer to 4.2.2 Impacts and 4.3.2 Software and
complete the parameter configurations for related functions based on the impact,
dependency, and mutually exclusive relationships between the functions, as well
as the actual network scenario.
//Configuring common parameters
//Configuring bearers for low-latency services (QCIs 3, 131, and 151 are used as examples)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, LowLatencyFlag=TRUE;
MOD CELLQCIPARA: LocalCellId=0, Qci=131, LowLatencyFlag=TRUE;
MOD CELLQCIPARA: LocalCellId=0, Qci=151, LowLatencyFlag=TRUE;
//Turning on the general switch that controls air interface latency optimization
MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=LowDelayServiceOptSwitch-1;

//Enabling the functions that are used for shortening scheduling periods
//Enabling SRI reporting period optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SRI_PERIOD_OPT_SW-1;
MOD PUCCHCFG: LocalCellId=0, SriPeriodAdaptive=QCIADAPTIVE;
MOD CELL: LocalCellId=0, FddTddInd=CELL_TDD, SubframeAssignment=SA2, SpecialSubframePatterns=SSP7;

//Enabling consecutive SR-based scheduling optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1,
LowDelayUeSrSchMinDataVol=1500;

//Enabling optimization for last packets

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1;

//Enabling preallocation optimization

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;

//Enabling cell-edge preallocation optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1,
LowDelayCeuPreallocOptThld=30;

//Enabling the functions that are used for raising service priorities
//Enabling DRX optimization (disabling DRX in DRX parameter group 4 for QCI-3 bearers carrying low-
latency services)
MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=4, EnterDrxSwitch=OFF;

//Enabling SR-based scheduling priority optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-1;
MOD CELLULSCHALGO: LocalCellId=0, UlDelaySchStrategy=NO_DELAYSCH;

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 34

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

//Enabling downlink scheduling priority optimization for GBR bearers

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-1;
//Enabling downlink scheduling priority optimization for non-GBR bearers
MOD CELLQCIPARA: LocalCellId=0, Qci=131, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-1;
MOD CELLQCIPARA: LocalCellId=0, Qci=151, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-1;
MOD CELLQCIPARAEXTENSION: LocalCellId=0, Qci=131, DlSchPriorityWeightFactor=930;
MOD CELLQCIPARAEXTENSION: LocalCellId=0, Qci=151, DlSchPriorityWeightFactor=900;

//Enabling the functions that are used for reducing the number of scheduling times
//Enabling SR-based scheduling data volume optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-1,
LowDelayUeSrSchMinDataVol=1500;

//Enabling RB expansion for UEs running low-latency services and having GBR bearers (solution 1)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1;
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=SchedulerCtrlPowerSwitch-1,
UlSchExtSwitch=UlSchRbAllocOptSw-1;
//Enabling RB expansion for UEs running low-latency services and having GBR bearers (solution 2)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-1;
MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=SchedulerCtrlPowerSwitch-1,
UlSchExtSwitch=UlSchRbAllocOptSw-1;

//Enabling standard UDC on low-latency services

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1;
MOD CELLDATACOMPRCONFIG: LocalCellId=0,
StandardUdcSwitch=UL_DEFLATE_DATA_COMPRESSION_SW-1;

//Enabling QCI-specific UDP-based ROHC

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=QCI_ROHC_SWITCH-1;

//Enabling the functions that are used for reducing service retransmissions
//Enabling PDCCH SINR offset optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciPdcchSinrOffset=30;

//Enabling precise MCS index reduction

MOD CELLQCIPARA: LocalCellId=0, Qci=3,
QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-1&LOW_DELAY_UE_UL_MCS_IDX_RDC_SW-1;

//Enabling MCS selection optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, DecreaseInNackCqiAdj=10;

Deactivation Command Examples (FDD)

The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
//Disabling the functions that are used for shortening scheduling periods
//Disabling SRI reporting period optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SRI_PERIOD_OPT_SW-0;

//Disabling consecutive SR-based scheduling optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;

//Disabling optimization for last packets

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;

//Disabling preallocation optimization

MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=PreAllocationSwitch-0&SmartPreAllocationSwitch-0;

//Disabling cell-edge preallocation optimization (Any of the following commands can be used to disable
this function.)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;
MOD CELLQCIPARA: LocalCellId=0, Qci=3, LowDelayCeuPreallocOptThld=-51;

//Disabling the functions that are used for raising service priorities
//Disabling DRX optimization (canceling the function of disabling DRX in DRX parameter group 4 for QCI-3
bearers carrying low-latency services)

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 35

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=4, EnterDrxSwitch=ON;

//Disabling SR-based scheduling priority optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-0;

//Disabling downlink scheduling priority optimization for GBR bearers

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-0;
//Disabling downlink scheduling priority optimization for non-GBR bearers
MOD CELLQCIPARA: LocalCellId=0, Qci=131, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-0;
MOD CELLQCIPARA: LocalCellId=0, Qci=151, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-0;

//Disabling the functions that are used for reducing the number of scheduling times
//Disabling SR-based scheduling data volume optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-0;

//Disabling RB expansion for UEs running low-latency services and having GBR bearers
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;

//Disabling standard UDC on low-latency services

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;

//Disabling standard UDC on low-latency services (Any of the following commands can be used to disable
this function.)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;
MOD CELLDATACOMPRCONFIG: LocalCellId=0,
StandardUdcSwitch=UL_DEFLATE_DATA_COMPRESSION_SW-0;

//Disabling the functions that are used for reducing service retransmissions
//Disabling PDCCH SINR offset optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciPdcchSinrOffset=0;

//Disabling PDCCH boundary power control optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=PDCCH_BOUNDARY_PWR_CTRL_OPT_SW-1;

//Disabling precise MCS index reduction (Any of the following commands can be used to disable this
function.)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_MCS_IDX_RDC_SW-0;

//Disabling QCI-specific TTI bundling

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=QCI_TTI_BUNDLING_SWITCH-0;

//Disabling MCS selection optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, DecreaseInNackCqiAdj=0;

//Turning off the general switch that controls air interface latency optimization
MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=LowDelayServiceOptSwitch-0;

Deactivation Command Examples (TDD)

The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
//Disabling the functions that are used for shortening scheduling periods
//Disabling SRI reporting period optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SRI_PERIOD_OPT_SW-0;

//Disabling consecutive SR-based scheduling optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;

//Disabling optimization for last packets

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;

//Disabling preallocation optimization

MOD CELLALGOSWITCH: LocalCellId=0, UlSchSwitch=PreAllocationSwitch-0&SmartPreAllocationSwitch-0;

//Disabling cell-edge preallocation optimization (Any of the following commands can be used to disable

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 36

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

this function.)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;
MOD CELLQCIPARA: LocalCellId=0, Qci=3, LowDelayCeuPreallocOptThld=-51;

//Disabling the functions that are used for raising service priorities
//Disabling DRX optimization (canceling the function of disabling DRX in DRX parameter group 4 for QCI-3
bearers carrying low-latency services)
MOD DRXPARAGROUP: LocalCellId=0, DrxParaGroupId=4, EnterDrxSwitch=ON;

//Disabling SR-based scheduling priority optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-0;

//Disabling downlink scheduling priority optimization for GBR bearers

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-0;
//Disabling downlink scheduling priority optimization for non-GBR bearers
MOD CELLQCIPARA: LocalCellId=0, Qci=131, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-0;
MOD CELLQCIPARA: LocalCellId=0, Qci=151, QciAlgoSwitch=DL_SCH_PRIORITY_OPT_SW-0;

//Disabling the functions that are used for reducing the number of scheduling times
//Disabling SR-based scheduling data volume optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-0;

//Disabling RB expansion for UEs running low-latency services and having GBR bearers (solution 1)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;
//Disabling RB expansion for UEs running low-latency services and having GBR bearers (solution 2)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=SR_PRIORITY_DATA_OPT_SW-0;

//Disabling standard UDC on low-latency services (Any of the following commands can be used to disable
this function.)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;
MOD CELLDATACOMPRCONFIG: LocalCellId=0,
StandardUdcSwitch=UL_DEFLATE_DATA_COMPRESSION_SW-0;

//Disabling QCI-specific UDP-based ROHC

MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=QCI_ROHC_SWITCH-0;

//Disabling the functions that are used for reducing service retransmissions
//Disabling PDCCH SINR offset optimization
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciPdcchSinrOffset=0;

//Disabling precise MCS index reduction (Any of the following commands can be used to disable this
function.)
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_SCH_OPT_SW-0;
MOD CELLQCIPARA: LocalCellId=0, Qci=3, QciAlgoSwitch=LOW_DELAY_UE_UL_MCS_IDX_RDC_SW-0;

//Disabling MCS selection optimization

MOD CELLQCIPARA: LocalCellId=0, Qci=3, DecreaseInNackCqiAdj=0;

//Turning off the general switch that controls air interface latency optimization
MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=LowDelayServiceOptSwitch-0;

4.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.

4.4.2 Activation Verification

4.4.2.1 Shortening Scheduling Periods

SRI Reporting Period Optimization

The activation verification procedure for SRI reporting period optimization is the
same as that for SRI reporting period adaptation. If the SRI reporting period of
bearers carrying low-latency services is shorter than that of bearers carrying non-

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 37

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

low-latency services when the cell load or the number of UEs running low-latency
services changes, SRI reporting period optimization has taken effect. For details,
see Physical Channel Resource Management.

Consecutive SR-based Scheduling Optimization

If the average number of used uplink PRBs (indicated by the
L.ChMeas.PRB.UL.Used.Avg counter) increases, this function has taken effect.

Optimization for Last Packets

If the average number of used uplink PRBs (indicated by the
L.ChMeas.PRB.UL.Used.Avg counter) increases, this function has taken effect.

Preallocation Optimization
The activation verification procedure for preallocation optimization is the same as
that for preallocation. If preallocation takes effect on bearers carrying low-latency
services, preallocation optimization has taken effect. For details, see Scheduling.

Cell-edge Preallocation Optimization

If the average number of PRBs used for uplink preallocation (indicated by the
L.ChMeas.PRB.UL.PreSch.Used.Avg counter) increases, this function has taken
effect.

4.4.2.2 Raising Service Priorities

DRX Optimization
The activation verification procedure for DRX optimization is the same as that for
DRX. If DRX has taken effect on bearers carrying low-latency services, DRX
optimization has taken effect. For details, see DRX and Signaling Control.

SR-based Scheduling Priority Optimization

If the value of Service Uplink Average Throughput of bearers carrying low-
latency services increases, SR-based scheduling priority optimization has taken
effect.

Downlink Scheduling Priority Optimization

If the average processing latency of downlink DRB-service packets of bearers
carrying low-latency services decreases, this function has taken effect.

Average downlink packet processing latency of services carried on QCI-n DRBs =

L.Traffic.DL.PktDelay.Time.QCI.n/L.Traffic.DL.PktDelay.Num.QCI.n

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 38

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

4.4.2.3 Reducing the Number of Scheduling Times

SR-based Scheduling Data Volume Optimization

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

RB Expansion for UEs Running Low-Latency Services and Having GBR

Bearers
If the average number of used uplink PRBs (indicated by the
L.ChMeas.PRB.UL.Used.Avg counter) increases, this function has taken effect.

Standard UDC on Low-Latency Services

● Message tracing
a. On the MAE-Access, create and start a Uu interface tracing task.
b. Observe the UE capability for standard UDC.
Select a standard-UDC-capable UE, and then observe the
RRC_UE_CAP_INFO message to check the UE capability for standard UDC,
as shown in the following figure. If the supportedUDC-r15 IE is
displayed, the UE supports standard UDC. If the supportedStandardDic-
r15 IE is displayed, the UE supports the VoLTE SIP standard dictionary.

c. Observe the eNodeB capability for the standard UDC buffer.

Select a standard-UDC-capable UE, and then observe the
RRC_CONN_RECFG message to check the eNodeB capability for standard
UDC buffer, as shown in the following figure. If the bufferSize-r15 field
in the uplinkDataCompression-r15 IE is kbyte8, the standard UDC
buffer size is 8 KB.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 39

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

d. Observe the eNodeB capability for standard UDC VoLTE SIP buffer and
standard dictionary.
Select a standard-UDC-capable UE, and then observe the
RRC_CONN_RECFG message to check the eNodeB capability for standard
UDC VoLTE SIP buffer and standard dictionary, as shown in the following
figure. If the bufferSize-r15 field in the uplinkDataCompression-r15 IE
is kbyte8, the standard UDC VoLTE SIP buffer size is 8 KB. If the
Dictionary-r15 field in the uplinkDataCompression-r15 IE is sip-SDP,
the eNodeB supports the VoLTE SIP standard dictionary.

● Counter observation

Counter ID Counter Name

1526749550 L.Thrp.bits.UL.PDCP.SDU.Deflate.BefDec
ompn

1526749551 L.Thrp.bits.UL.PDCP.SDU.Deflate.AftDec
ompn

QCI-specific UDP-based ROHC

● Message tracing
a. On the MAE-Access, 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 profile0x0002 is TRUE, the UE supports the
compression mode with the profile ID of 0x0002.
c. Observe the RRC_CONN_RECFG message over the Uu interface to
determine whether ROHC has been activated.

▪ If "pdcp-Config > headerCompression > rohc" is displayed, ROHC has

been activated.

▪ If "pdcp-Config > headerCompression > notUsed: NULL" is displayed,

ROHC has not been activated.
● 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.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 40

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

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.By
tes

1526747664 L.PDCP.UL.RoHC.Data.Hdr.Bytes

4.4.2.4 Reducing Service Retransmissions

PDCCH SINR Offset Optimization

Check whether PDCCH SINR offset optimization has taken effect by observing
User Common Monitoring on the MAE-Access. The procedure is as follows:
1. Use a UE to access a cell and perform a low-latency service.
2. On the MAE-Access, choose Monitor > Signaling Trace > Signaling Trace
Management.
3. In the navigation tree of the Signaling Trace Management tab page, choose
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 PDCCH aggregation level monitoring.
4. Check the PDCCH aggregation level when the UE is running the low-latency
service.
If the PDCCH aggregation level increases, this function has taken effect.

PDCCH Boundary Power Control Optimization (FDD)

If the equivalent CCE usage increases, PDCCH boundary power control
optimization has taken effect.
Equivalent CCE usage = (L.ChMeas.CCE.ULUsed.Equivalent +
L.ChMeas.CCE.DLUsed.Equivalent)/L.ChMeas.CCE.Avail x 100%

Precise MCS Index Reduction

If both the uplink IBLER and the average uplink MCS index decrease, precise MCS
index reduction has taken effect.
● Uplink IBLER (QCI n) = L.Traffic.UL.SCH.ErrTB.Ibler.QCIn/
L.Traffic.UL.SCH.TB.QCIn
QCIn specifies the QCI marked with the low-latency service flag.
● Average uplink MCS index = (L.ChMeas.PUSCH.MCS.0 x 0 +
L.ChMeas.PUSCH.MCS.1 x 1 + L.ChMeas.PUSCH.MCS.2 x 2+ ... +
L.ChMeas.PUSCH.MCS.27 x 27 + L.ChMeas.PUSCH.MCS.28 x 28)/
(L.ChMeas.PUSCH.MCS.0 + L.ChMeas.PUSCH.MCS.1 +

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 41

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

L.ChMeas.PUSCH.MCS.2 + ... + L.ChMeas.PUSCH.MCS.27 +

L.ChMeas.PUSCH.MCS.28)

QCI-specific TTI Bundling (FDD)

● 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.

▪ The value of this IE is TRUE and the QCI is marked with the low-
latency service flag, indicating that QCI-specific TTI bundling has
taken effect.

▪ The value of this IE is FALSE and the QCI is marked with the low-
latency service flag, indicating that QCI-specific TTI bundling has
stopped taking effect or has not taken effect.
– For 3GPP Release 12-compliant TTI bundling eHARQ, check the e-HARQ-
Pattern-r12 field.

▪ 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.

▪ 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.
● Counter observation
Check the counters listed in Table 4-8. 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-8 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

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.QCIn/

L.Traffic.DL.SCH.TB.QCIn

QCIn specifies the QCI marked with the low-latency service flag.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 42

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

4.4.3 Network Monitoring

● 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.
● The downlink latency gains offered by this feature 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
QCI n specifies the QCI marked with the low-latency service flag.
● 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 commands:
– Low-latency service identification based on service classification by
domain name server (DNS)
MOD SCPOLICY: ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-1;
ADD SCAPPPARACFG: AppDnsId=1, AppIdentType=DNS, AppDns="xxx", MatchRule=Query,
AppCfgTargetInd=LowDelayServiceInd-1;

– Low-latency service identification based on bearers. The following takes

QCI-3 bearers marked as low-latency bearers as an example.
//Marking QCI 3 with the low-latency service flag
MOD SCPOLICY: ScAlgoSwitch=LOW_LATENCY_QCI_SC_LOAD_SW-1;
MOD CELLQCIPARA: LocalCellId=0, Qci=3, LowLatencyFlag=TRUE;

This CHR is measured periodically. (The period is 30 seconds.) For details

about the fields and their meanings, see Table 4-9.

Table 4-9 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,
DlRttIntervalThd1) ms

>>TCP DL RTT Mean Interval2 Number of times the downstream

TCP RTT falls within the range of
[DlRttIntervalThd1,
DlRttIntervalThd2) ms

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 43

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Field Meaning

>>TCP DL RTT Mean Interval3 Number of times the downstream

TCP RTT falls within the range of
[DlRttIntervalThd2,
DlRttIntervalThd3) ms

>>TCP DL RTT Mean Interval4 Number of times the downstream

TCP RTT falls within the range of
[DlRttIntervalThd3,
DlRttIntervalThd4) ms

>>TCP DL RTT Mean Interval5 Number of times the downstream

TCP RTT falls within the range of
[DlRttIntervalThd4, ∞) 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, 20)
ms

>>TCP UL RTT Mean Interval2 Number of times the upstream TCP

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

>>TCP UL RTT Mean Interval3 Number of times the upstream TCP

RTT falls within the range of [40,
60) ms

>>TCP UL RTT Mean Interval4 Number of times the upstream TCP

RTT falls within the range of [60,
80) ms

>>TCP UL RTT Mean Interval5 Number of times the upstream TCP

RTT falls within the range of [80, ∞)
ms

>>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 [0, 20)
ms

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 44

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

Field Meaning

>>UDP UL RTT Mean Interval2 Number of times the upstream UDP

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

>>UDP UL RTT Mean Interval3 Number of times the upstream UDP

RTT falls within the range of [40,
60) ms

>>UDP UL RTT Mean Interval4 Number of times the upstream UDP

RTT falls within the range of [60,
80) ms

>>UDP UL RTT Mean Interval5 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

>>Identification Method Identification method. 0 indicates

identification based on service
classification. 1 indicates
identification based on bearers.

>>ExceptionInformation 0 indicates normal, and the number

of streams is less than 100.
1 indicates that the number of
streams is 100.

>>DlRttIntervalThd1 Upper limit of downstream RTT

range 1

>>DlRttIntervalThd2 Upper limit of downstream RTT

range 2

>>DlRttIntervalThd3 Upper limit of downstream RTT

range 3

>>DlRttIntervalThd4 Upper limit of downstream RTT

range 4

You can modify the downstream RTT range by setting the downstream RTT
range thresholds during subscription. The value ranges of DlRttIntervalThd1,
DlRttIntervalThd2, DlRttIntervalThd3, and DlRttIntervalThd4 are 1–65535.
The default values are 20, 50, 85, and 100, respectively. In addition, when
setting the thresholds, ensure the values of DlRttIntervalThd1,
DlRttIntervalThd2, DlRttIntervalThd3, and DlRttIntervalThd4 are in
descending order.
When bearers carrying low-latency services are set up on the core network:

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 45

eRAN
Air Interface Latency Optimization Feature
Parameter Description 4 Air Interface Latency Optimization

– If only UDP data 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.
– The eNodeB does not identify UDP in low-latency service identification
based on bearers.
– When both identification based on service classification by DNS and
identification based on bearers take effect and bearers marked with a
low-latency flag carry service streams that can be identified based on
DNS, results of related indicators are output using identification based on
bearers.
If 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.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 46

eRAN
Air Interface Latency Optimization Feature
Parameter Description 5 Parameters

5 Parameters

The following hyperlinked EXCEL files of parameter documents match the

software version with which this document is released.

● Node Parameter Reference: contains device and transport parameters.

● eNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
● eNodeBFunction Used Reserved Parameter List: contains the reserved
parameters that are in use and those that have been disused.
NOTE

You can find the EXCEL files of parameter reference and used reserved parameter list for
the software version used on the live network from the product documentation delivered
with that version.

FAQ 1: How do I find the parameters related to a certain feature from

parameter reference?

Step 1 Open the EXCEL file of parameter reference.

Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or
TDLOFD-001016.

Step 3 Click OK. All parameters related to the feature are displayed.

----End

FAQ 2: How do I find the information about a certain reserved parameter

from the used reserved parameter list?

Step 1 Open the EXCEL file of the used reserved parameter list.

Step 2 On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter.
View its information, including the meaning, values, impacts, and product version
in which it is activated for use.

----End

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 47

eRAN
Air Interface Latency Optimization Feature
Parameter Description 6 Counters

6 Counters

The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● 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

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 48

eRAN
Air Interface Latency Optimization Feature
Parameter Description 7 Glossary

7 Glossary

For the acronyms, abbreviations, terms, and definitions, see Glossary.

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 49

eRAN
Air Interface Latency Optimization Feature
Parameter Description 8 Reference Documents

8 Reference Documents

1. Scheduling
2. Physical Channel Resource Management
3. DRX and Signaling Control
4. VoLTE
5. ROHC
6. MIMO
7. Relay
8. Video Experience Optimization
9. Uplink Data Compression
10. NSA Networking based on EPC

Issue 03 (2023-08-23) Copyright © Huawei Technologies Co., Ltd. 50