Uplink Data Compression (ERAN18.1 - 01)
Uplink Data Compression (ERAN18.1 - 01)
Issue 01
Date 2022-03-08
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: https://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.........................................................................................................................1
1.1 eRAN18.1 01 (2022-03-08)..................................................................................................................................................1
1.2 eRAN18.1 Draft A (2021-12-30)........................................................................................................................................ 1
3 Overview....................................................................................................................................4
4 Standard Uplink Data Compression.................................................................................... 5
4.1 Principles.................................................................................................................................................................................... 5
4.2 Network Analysis..................................................................................................................................................................... 8
4.2.1 Benefits.................................................................................................................................................................................... 8
4.2.2 Impacts.................................................................................................................................................................................... 8
4.3 Requirements......................................................................................................................................................................... 10
4.3.1 Licenses................................................................................................................................................................................. 10
4.3.2 Software................................................................................................................................................................................10
4.3.3 Hardware.............................................................................................................................................................................. 10
4.3.4 Others.................................................................................................................................................................................... 11
4.4 Operation and Maintenance............................................................................................................................................. 11
4.4.1 Data Configuration........................................................................................................................................................... 11
4.4.1.1 Data Preparation............................................................................................................................................................ 11
4.4.1.2 Using MML Commands............................................................................................................................................... 12
4.4.1.3 Using the MAE-Deployment...................................................................................................................................... 12
4.4.2 Activation Verification..................................................................................................................................................... 12
4.4.3 Network Monitoring......................................................................................................................................................... 14
5 Parameters.............................................................................................................................. 15
6 Counters.................................................................................................................................. 16
7 Glossary................................................................................................................................... 17
8 Reference Documents...........................................................................................................18
1 Change History
Editorial Changes
Revised descriptions in this document.
Technical Changes
None
Editorial Changes
Deleted descriptions of the LMPT.
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.
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
To increase the uplink transmission rate, Huawei has introduced the uplink data
compression (UDC) and standard UDC features.
When UDC is enabled, uplink data is compressed and only the non-repetitive
content of the legacy data are transmitted in the uplink over the air interface,
thereby minimizing the amount of data to be transmitted over the air interface
and increasing the radio resource efficiency for transmitting application-layer data.
This feature increases the uplink transmission rate at the application layer.
4.1 Principles
Standard UDC is introduced in 3GPP Release 15 to increase the uplink cell
capacity.
If standard UDC is enabled, the standard UDC–capable UE compresses the packets
(including the TCP/IP header and payload) transmitted in the uplink at the PDCP
layer and transmits them to the eNodeB over the Uu interface. The eNodeB
decompresses the packets at the PDCP layer to obtain the original packets.
Since packets are compressed before transmission, fewer Uu interface resources
are required to transmit a given amount of uplink data, improving the uplink cell
capacity.
Buffers of the eNodeB and UE are updated in real time during packet processing.
The buffer size is specified by the CellDataComprConfig.StandardUdcBufferSize
parameter and can be set to 2 KB, 4 KB, or 8 KB.
● Transmits the non-repetitive part between the legacy data and buffered data.
● Transmits the information about the buffer position of the repetitive part
between the legacy data and buffered data.
The UE uses the standard Deflate algorithm for compression. The Deflate
algorithm is defined in RFC1951 and combines the LZ77 compression algorithm
and static Huffman coding.
● The basic principle of the LZ77 sliding window is to search for the content in
the historical sliding window. If the current data is partly duplicate with that
in the historical sliding window, the repetitive part can be replaced with an
index with fewer bytes.
● Static Huffman coding is a set of unified coding and mapping modes
stipulated in 3GPP specifications. Codes for each symbol are fixed and can be
queried from code tables.
Standard Dictionary
The standard dictionary refers to buffered data predefined on the UE and eNodeB
sides.
During the establishment of bearers for standard UDC, if the standard dictionary is
configured, the UE and eNodeB fill in the buffers with contents in the standard
dictionary as a basis for data compression.
Two types of standard dictionaries defined in 3GPP specifications are as follows:
● Standard SIP-SDP dictionary
A preset standard dictionary is defined for QCI 5 bearers (mainly SIP and SDP
signaling). During the establishment of QCI 5 bearers for standard UDC, the
UE and eNodeB fill in their buffers with contents in the preset dictionary. The
SIP_DICTIONARY_SW option of the
4.2.1 Benefits
Recommended Scenario
Standard UDC increases the uplink transmission rate at the application layer.
Standard UDC is recommended when being supported by a large number of UEs
on the network.
Feature Gains
● Standard UDC decreases the amount of uplink physical resources required for
transmitting a given amount of data over the Uu interface.
● Standard UDC reduces the uplink congestion duration, frequency of uplink
congestion, and ping delay when there is no uplink congestion.
● Standard UDC increases the uplink transmission rate at the application layer
while maintaining the channel quality and resource usage over the Uu
interface.
● The gains offered by standard UDC are proportional to how much legacy data
transmitted by a single UE repeats. When standard UDC is enabled on both
UEs and the eNodeB, compression gains of more than 30% can be achieved
on average in the uplink data transmission over standard UDC–performed
bearers.
● When UEs are performing VoLTE services, standard UDC does not take effect
in SIP encryption scenarios, and therefore does not produce any gains in this
case.
NOTE
4.2.2 Impacts
Network Impacts
● Standard UDC increases the board CPU usage.
● According to 3GPP specifications, packets after standard UDC have internal
overhead and header overhead. If uplink data transmitted has a small amount
of repetitive content, packets after being compressed may be larger than
packets before compression.
● When the channel quality and data volume over the air interface are the
same, the amount of data at the MAC layer decreases and the counters
related to the MAC layer change after the standard UDC feature is enabled.
Such counters related to the MAC layer include the PRB usage, MCS index,
and spectral efficiency.
Function Impacts
Function Function Reference Description
Name Switch
4.3 Requirements
4.3.1 Licenses
The following are FDD license requirements.
4.3.2 Software
Prerequisite Functions
None
4.3.3 Hardware
Boards
All boards except the LBBPc support this feature.
RF Modules
N/A
4.3.4 Others
UEs must support standard UDC in 3GPP Release 15.
Method 1
Observe the counters listed in the following table. If any counter value is greater
than 0, standard UDC has taken effect.
Method 2
The Uu interface signaling tracing function can be used on the MAE-Access to
verify whether standard UDC takes effect. To verify whether standard UDC takes
effect, perform the following steps:
Step 4 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
uplinkDataCompression-r15 is kbyte8, the standard UDC VoLTE SIP buffer is 8 KB.
If the Dictionary-r15 field in uplinkDataCompression-r15 is sip-SDP, the eNodeB
supports the VoLTE SIP standard dictionary.
----End
5 Parameters
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.
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
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
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.
----End
7 Glossary
8 Reference Documents
1. ROHC
2. Specified User Coordinated Scheduling
3. Video Experience Optimization
4. Air Interface Latency Optimization