Академический Документы
Профессиональный Документы
Культура Документы
Issue Draft A
Date 2019-01-05
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.............................................................................................................................. 1
1.1 eRAN15.1 Draft A (2019-01-05)................................................................................................................................... 1
3 Overview......................................................................................................................................... 4
4 Short TTI......................................................................................................................................... 5
4.1 Principles........................................................................................................................................................................ 5
4.2 Network Analysis........................................................................................................................................................... 8
4.2.1 Benefits........................................................................................................................................................................ 8
4.2.2 Impacts.........................................................................................................................................................................8
4.3 Requirements................................................................................................................................................................ 12
4.3.1 Licenses..................................................................................................................................................................... 12
4.3.2 Software.....................................................................................................................................................................12
4.3.3 Hardware................................................................................................................................................................... 15
4.3.4 Others.........................................................................................................................................................................16
4.4 Operation and Maintenance..........................................................................................................................................16
4.4.1 Data Configuration.................................................................................................................................................... 16
4.4.1.1 Data Preparation..................................................................................................................................................... 16
4.4.1.2 Using MML Commands......................................................................................................................................... 18
4.4.1.3 Using the CME....................................................................................................................................................... 19
4.4.2 Activation Verification.............................................................................................................................................. 19
4.4.3 Network Monitoring.................................................................................................................................................. 20
5 Parameters..................................................................................................................................... 21
6 Counters........................................................................................................................................ 22
7 Glossary......................................................................................................................................... 23
8 Reference Documents................................................................................................................. 24
1 Change History
This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and
"Reference Documents" chapters. These changes include:
l Technical changes
Changes in functions and their corresponding parameters
l Editorial changes
Improvements or revisions to the documentation
This document only provides guidance for feature activation. Feature deployment and feature
gains depend on the specifics of the network scenario where the feature is deployed. To achieve
the desired gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this document
apply only to the corresponding software release. For future software releases, refer to the
corresponding updated product documentation.
Trial Features
Trial features are features that are not yet ready for full commercial release for certain
reasons. For example, the industry chain (terminals/CN) may not be sufficiently compatible.
However, these features can still be used for testing purposes or commercial network trials.
Anyone who desires to use the trial features shall contact Huawei and enter into a
memorandum of understanding (MoU) with Huawei prior to an official application of such
trial features. Trial features are not for sale in the current version but customers may try them
for free.
Customers acknowledge and undertake that trial features may have a certain degree of risk
due to absence of commercial testing. Before using them, customers shall fully understand not
only the expected benefits of such trial features but also the possible impact they may exert on
the network. In addition, customers acknowledge and undertake that since trial features are
free, Huawei is not liable for any trial feature malfunctions or any losses incurred by using the
trial features. Huawei does not promise that problems with trial features will be resolved in
the current version. Huawei reserves the rights to convert trial features into commercial
features in later R/C versions. If trial features are converted into commercial features in a later
version, customers shall pay a licensing fee to obtain the relevant licenses prior to using the
said commercial features. If a customer fails to purchase such a license, the trial feature(s)
will be invalidated automatically when the product is upgraded.
3 Overview
LTE networks have evolved, and millisecond-level end-to-end (E2E) service latency is now
possible. New services, such as Ultra-Reliable and Low-Latency Communication (URLLC)
services, require a lower latency. To meet the latency requirements of these services, short
transmission time interval (TTI) has been introduced as a key technology to guarantee a low
latency on LTE networks.
4 Short TTI
4.1 Principles
In a conventional LTE system, 1 ms subframes are transmitted over the air interface. When
normal cyclic prefixes (CPs) are used, each subframe contains 14 orthogonal frequency
division multiplexing (OFDM) symbols. With short TTI, a 1-ms subframe can be subdivided
into shorter TTI lengths. It can be shortened to just two or three symbols. This decreases the
latency over the air interface and the total E2E latency. There are two structures (as shown in
Figure 4-1 and Figure 4-2) for downlink short TTI subframes and one structure (as shown in
Figure 4-3) for uplink short TTI subframes.
In the preceding structures, os stands for an OFDM symbol, and sTTI stands for a subslot
TTI. A normal 1-ms TTI is also called an nTTI.
Which downlink subframe structure is used depends on the index of the start symbol of the
first Subslot PDSCH (sPDSCH). Table 4-1 lists which structure is used for each index.
Table 4-1 Index of the start symbol of the first sPDSCH and the corresponding downlink
subframe structure
Index of the Start Symbol Downlink Short TTI Subframe
Structure
1 or 3 Structure 1
2 Structure 2
1. The eNodeB checks whether the short TTI switch (controlled by the SHORT_TTI_SW
option of the CellShortTtiAlgo.SttiAlgoSwitch parameter) is turned on.
a. If it is turned on, the eNodeB proceeds with 2.
b. If it is not turned on, the eNodeB schedules the UE in normal TTI mode.
2. The eNodeB determines whether the UE to be scheduled supports short TTI.
a. If it supports short TTI, the eNodeB proceeds with 3. For details about the
requirements for UE capabilities, see 4.3.4 Others.
b. If it does not support short TTI, the eNodeB schedules the UE in normal TTI mode.
3. The eNodeB checks whether the UE meets the conditions for entering the short TTI
scheduling.
a. If all of the following conditions are met, the eNodeB proceeds with 4:
n The uplink signal to interference plus noise ratio (SINR) of the UE is higher
than the value of the CellShortTtiAlgo.SttiEntryUlSinrThld parameter.
n A bearer with a QCI whose CellQciPara.LowLatencyFlag parameter is
TRUE has been set up for the UE.
n The uplink resource block (RB) usage of the cell that serves the UE does not
exceed the value of the CellShortTtiAlgo.SttiEntryUlRbUsageThld
parameter.
n The downlink RB usage of the cell that serves the UE does not exceed the
value of the CellShortTtiAlgo.SttiEntryDlRbUsageThld parameter.
b. If any of the preceding conditions is not met, the eNodeB schedules the UE in
normal TTI mode.
4. The eNodeB schedules the UE in short TTI mode.
4.2.1 Benefits
UEs performing small-packet services (such as online gaming or web browsing) enjoy a lower
air interface latency and accordingly a lower E2E latency in short TTI mode than in normal
TTI mode.
4.2.2 Impacts
Network Impacts
Short TTI has the following impacts on the network:
l The Cell Uplink Average Throughput may decrease slightly. This is because short TTI
increases the header overhead of transport blocks, uplink demodulation reference signal
(DMRS) overhead, and symbol-level interference to neighboring cells.
l The Cell Downlink Average Throughput may decrease slightly. This is because short
TTI increases the header overhead of transport blocks, and the sPDCCH occupies a large
number of downlink resources.
l The downlink peak throughput of the short TTI UEs decreases. This is because the
eNodeB selects a low code rate during transport block size (TBS) index selection in short
TTI mode.
Function Impacts
l Functions related to resource management
Function Function Switch Referenc Description
Name e
4.3 Requirements
4.3.1 Licenses
There are currently no license requirements for trial functions. For details, see 2.1 General
Statements.
4.3.2 Software
Prerequisite Functions
None
4.3.3 Hardware
Boards
The baseband processing unit must be a UBBPe in any of the following models:
l UBBPe1
l UBBPe2
l UBBPe3
l UBBPe4
l UBBPe5
l UBBPe6
NOTE
If short TTI is enabled for an LTE FDD cell established on a BBP, non-FDD cells cannot be set up on
this BBP.
RF Modules
The RF modules must support a TX/RX capability of no higher than 4T4R.
Cells
l The cell bandwidth must be at least 10 MHz.
l The TX/RX mode of the cell must be 2T2R, 2T4R, or 4T4R.
NOTE
If short TTI is enabled for a cell, the software version of any given neighboring cell must be eRAN15.0
or earlier. Otherwise, the handover between the two cells will fail.
4.3.4 Others
UEs must support short TTI. The requirements for reported UE capabilities are as follows:
l The IE "STTI-SupportedCombinations-r15.combination-22-r15" for the corresponding
band is {1,1}. This indicates that the UE supports single-carrier short TTI.
l The IE "min-Proc-TimelineSubslot-r15" is {set1,set1,set1}.
l The IE "ue-CategoryUL" is not UL Category M1, UL Category M2, UL Category 0, or
UL Category 1bis.
l The IE "ue-CategoryDL" is not DL Category M1, DL Category M2, DL Category 0, or
DL Category 1bis.
//Setting the QCI for the cell with short TTI enabled
MOD CELLQCIPARA: LocalCellId=0, Qci=3, LowLatencyFlag=TRUE;
//Setting the policy of RB adjustment in the normal and short TTI modes
MOD CELLSHORTTTIALGO: LocalCellId=0, NttiSttiRbAdjStrategy=DYNAMIC;
//Setting the numbers of uplink and downlink sRBGs reserved for short TTI
MOD CELLSHORTTTIALGO: LocalCellId=0, DlSrbgCntReservedForStti=1,
UlSrbgCntReservedForStti=1;
//Setting the maximum numbers of uplink and downlink HARQ retransmissions for
short TTI
MOD CELLSHORTTTIALGO: LocalCellId=0, SttiUlHarqMaxTxCnt=N10,
SttiDlHarqMaxTxCnt=N10;
//Setting the short TTI RLC parameter group ID to 167 for QCI 3
MOD QCIPARA: Qci=3, ShortTtiRlcParamGroupId=167;
5 Parameters
The following hyperlinked EXCEL files of parameter reference match the software version
with which this document is released.
l Node Parameter Reference: contains device and transport parameters.
l eNodeBFunction Parameter Reference: contains all parameters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
NOTE
You can find the EXCEL files of parameter reference for the software version on the live network from
the product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from parameter
reference?
Step 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
6 Counters
The following hyperlinked EXCEL files of performance counter reference match the software
version with which this document is released.
l Node Performance Counter Summary: contains device and transport counters.
l eNodeBFunction Performance Counter Summary: contains all counters related to radio
access functions, including air interface management, access control, mobility control,
and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used on the live
network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from performance counter
reference?
Step 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
7 Glossary
8 Reference Documents
1. Scheduling
2. Channel State Management
3. Physical Channel Resource Management
4. Breathing Pilot
5. Modulation Schemes
6. eMIMO (FDD)
7. Carrier Aggregation
8. VoLTE
9. UL CoMP
10. DL CoMP (FDD)
11. Video Experience Optimization
12. MIMO
13. DRX and Signaling Control
14. PTT
15. SRLTE Optimization
16. Uplink Timing Control (FDD)
17. Uplink Interference Cancellation (FDD)
18. Turbo Receiver
19. Uplink Coordinated Scheduling
20. CSPC
21. Extended CP
22. PSIC Receiver
23. SFN
24. Extended Cell Range
25. Virtual 4T4R (FDD)
26. 3D Beamforming (FDD)
27. Massive MIMO (FDD)
28. Compact Bandwidth (FDD)