eRAN

eRAN17.1
eRAN FDD Feature Documentation

Issue Date 2022-01-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2024. 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]
eRAN FDD Feature Documentation

Contents
Contents...........................................................................................................................................................................................................1
1 RAN Services...............................................................................................................................................................................................2
1.1 Video.....................................................................................................................................................................................................2
1.1.1 Video Experience Optimization...........................................................................................................................................3

2024-05-07 1
eRAN FDD Feature Documentation

1 RAN Services

• Emergency Communications

• Voice

• Video

• LiTRA

• WTTx

• Other Services

1.1 Video

• Video Experience Optimization

• Air Interface Latency Optimization

• Uplink Data Compression

2024-05-07 2
eRAN FDD Feature Documentation

1.1.1 Video Experience Optimization

eRAN

Video Experience Optimization Feature

Parameter Description
Issue 03
Date 2021-11-27

2024-05-07 3
eRAN FDD Feature Documentation

eRAN

Video Experience Optimization Feature

Parameter Description
Issue 03
Date 2021-11-27

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021. 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]
1 Change History
1.1 eRAN17.1 03 (2021-11-27)
1.2 eRAN17.1 02 (2021-06-26)
1.3 eRAN17.1 01 (2021-03-05)
1.4 eRAN17.1 Draft A (2020-12-29)

2024-05-07 4
eRAN FDD Feature Documentation

2 About This Document

2.1 General Statements
2.2 Applicable RAT
2.3 Features in This Document
3 Feature Overview
4 SC-based Service Identification
4.1 Principles
4.1.1 SC-based Video Service Identification
4.1.2 SC-based Identification of Acceleration Guarantee UEs
4.2 Network Analysis
4.2.1 Benefits
4.2.2 Impacts
4.3 Requirements
4.3.1 Licenses
4.3.2 Software
4.3.3 Hardware
4.3.4 Other Requirements
4.4 Operation and Maintenance
4.4.1 Data Configuration
4.4.1.1 Data Preparation
4.4.1.2 Using MML Commands
4.4.1.3 Using the MAE-Deployment
4.4.2 Activation Verification
4.4.3 Network Monitoring
5 Initial Acceleration
5.1 WTCP Proxy
5.1.1 Principles
5.1.1.1 WTCP Proxy
5.1.1.2 WTCP Proxy Optimization
5.1.2 Network Analysis
5.1.2.1 Benefits
5.1.2.2 Impacts
5.1.3 Requirements
5.1.3.1 Licenses
5.1.3.2 Software
5.1.3.3 Hardware
5.1.3.4 Others
5.1.4 Operation and Maintenance
5.1.4.1 Data Configuration
5.1.4.1.1 Data Preparation
5.1.4.1.2 Using MML Commands
5.1.4.1.3 Using the MAE-Deployment
5.1.4.2 Activation Verification

2024-05-07 5
eRAN FDD Feature Documentation

5.1.4.3 Network Monitoring

5.2 Air Interface Acceleration Guarantee for Network Services
5.2.1 Principles
5.2.2 Network Analysis
5.2.2.1 Benefits
5.2.2.2 Impacts
5.2.3 Requirements
5.2.3.1 Licenses
5.2.3.2 Software
5.2.3.3 Hardware
5.2.3.4 Others
5.2.4 Operation and Maintenance
5.2.4.1 Data Configuration
5.2.4.1.1 Data Preparation
5.2.4.1.2 Using MML Commands
5.2.4.1.3 Using the MAE-Deployment
5.2.4.2 Activation Verification
5.2.4.3 Network Monitoring
5.3 Enhanced TCP Link Setup Acceleration
5.3.1 Principles
5.3.2 Network Analysis
5.3.2.1 Benefits
5.3.2.2 Impacts
5.3.3 Requirements
5.3.3.1 Licenses
5.3.3.2 Software
5.3.3.3 Hardware
5.3.3.4 Others
5.3.4 Operation and Maintenance
5.3.4.1 Data Configuration
5.3.4.1.1 Data Preparation
5.3.4.1.2 Using MML Commands
5.3.4.1.3 Using the MAE-Deployment
5.3.4.2 Activation Verification
5.3.4.3 Network Monitoring
6 Initiative TCP Packet Ordering
6.1 Principles
6.2 Network Analysis
6.2.1 Benefit Analysis
6.2.2 Impacts
6.3 Requirements
6.3.1 Licenses
6.3.2 Software

2024-05-07 6
eRAN FDD Feature Documentation

6.3.3 Hardware
6.3.4 Others
6.4 Operation and Maintenance
6.4.1 Data Configuration
6.4.1.1 Data Preparation
6.4.1.2 Using MML Commands
6.4.1.3 Using the MAE-Deployment
6.4.2 Activation Verification
6.4.3 Network Monitoring
7 Video Service Rate Adaption
7.1 SC-based Video Service Rate Adaption
7.1.1 Principles
7.1.2 Network Analysis
7.1.2.1 Benefits
7.1.2.2 Impacts
7.1.3 Requirements
7.1.3.1 Licenses
7.1.3.2 Software
7.1.3.3 Hardware
7.1.3.4 Others
7.1.4 Operation and Maintenance
7.1.4.1 Data Configuration
7.1.4.1.1 Data Preparation
7.1.4.1.2 Using MML Commands
7.1.4.1.3 Using the MAE-Deployment
7.1.4.2 Activation Verification
7.1.4.3 Network Monitoring
7.2 DSCP-based Video Service Rate Adaption
7.2.1 Principles
7.2.1.1 Video Service Rate Adaption
7.2.1.2 Principles for DSCP-based Service Differentiation
7.2.1.2.1 Working Principle
7.2.1.2.2 DSCP and QoS Policy Configurations
7.2.1.2.3 Differentiated Scheduling
7.2.2 Network Analysis
7.2.2.1 Benefits
7.2.2.2 Impacts
7.2.3 Requirements
7.2.3.1 Licenses
7.2.3.2 Software
7.2.3.3 Hardware
7.2.3.4 Other Requirements
7.2.4 Operation and Maintenance

2024-05-07 7
eRAN FDD Feature Documentation

7.2.4.1 Data Configuration

7.2.4.1.1 Data Preparation
7.2.4.1.2 Using MML Commands
7.2.4.1.3 Using the MAE-Deployment
7.2.4.2 Activation Verification
7.2.4.3 Network Monitoring
7.3 Video Service Load Control
7.3.1 Principles
7.3.2 Network Analysis
7.3.2.1 Benefits
7.3.2.2 Impacts
7.3.3 Requirements
7.3.3.1 Licenses
7.3.3.2 Software
7.3.3.3 Hardware
7.3.3.4 Others
7.3.4 Operation and Maintenance
7.3.4.1 Data Configuration
7.3.4.1.1 Data Preparation
7.3.4.1.2 Using MML Commands
7.3.4.1.3 Using the MAE-Deployment
7.3.4.2 Activation Verification
7.3.4.3 Network Monitoring
7.4 Video Resource Control in Congestion Scenarios
7.4.1 Principles
7.4.2 Network Analysis
7.4.2.1 Benefits
7.4.2.2 Impacts
7.4.3 Requirements
7.4.3.1 Licenses
7.4.3.2 Software
7.4.3.3 Hardware
7.4.3.4 Other Requirements
7.4.4 Operation and Maintenance
7.4.4.1 Data Configuration
7.4.4.1.1 Data Preparation
7.4.4.1.2 Using MML Commands
7.4.4.1.3 Using the MAE-Deployment
7.4.4.2 Activation Verification
7.4.4.3 Network Monitoring
7.5 VOD Optimization
7.5.1 Principles
7.5.1.1 Capability Negotiation for VOD Optimization

2024-05-07 8
eRAN FDD Feature Documentation

7.5.1.2 VOD Optimization

7.5.2 Network Analysis
7.5.2.1 Benefits
7.5.2.2 Impacts
7.5.3 Requirements
7.5.3.1 Licenses
7.5.3.2 Software
7.5.3.3 Hardware
7.5.3.4 Others
7.5.4 Operation and Maintenance
7.5.4.1 Data Configuration
7.5.4.1.1 Data Preparation
7.5.4.1.2 Using MML Commands
7.5.4.1.3 Using the MAE-Deployment
7.5.4.2 Activation Verification
7.5.4.3 Network Monitoring
7.6 DSCP-based IPTV QoS Guarantee in WTTx Scenarios
7.6.1 Principles
7.6.2 Network Analysis
7.6.2.1 Benefit Analysis
7.6.2.2 Impacts
7.6.3 Requirements
7.6.3.1 Licenses
7.6.3.2 Software
7.6.3.3 Hardware
7.6.3.4 Others
7.6.4 Operation and Maintenance
7.6.4.1 Data Configuration
7.6.4.1.1 Data Preparation
7.6.4.1.2 Using MML Commands
7.6.4.1.3 Using the MAE-Deployment
7.6.4.2 Activation Verification
7.6.4.3 Network Monitoring
8 Busy-Hour Download Rate Control
8.1 Principles
8.2 Network Analysis
8.2.1 Benefits
8.2.2 Impacts
8.3 Requirements
8.3.1 Licenses
8.3.2 Software
8.3.3 Hardware
8.3.4 Other Requirements

2024-05-07 9
eRAN FDD Feature Documentation

8.4 Operation and Maintenance

8.4.1 Data Configuration
8.4.1.1 Data Preparation
8.4.1.2 Using MML Commands
8.4.1.3 Using the MAE-Deployment
8.4.2 Activation Verification
8.4.3 Network Monitoring
9 Uplink Coverage Improvement for Video (FDD)
9.1 Video TTI Bundling (FDD)
9.1.1 Principles
9.1.2 Network Analysis
9.1.2.1 Benefits
9.1.2.2 Impacts
9.1.3 Requirements
9.1.3.1 Licenses
9.1.3.2 Software
9.1.3.3 Hardware
9.1.3.4 Others
9.1.4 Operation and Maintenance
9.1.4.1 Data Configuration
9.1.4.1.1 Data Preparation
9.1.4.1.2 Using MML Commands
9.1.4.1.3 Using the MAE-Deployment
9.1.4.2 Activation Verification
9.1.4.3 Network Monitoring
9.2 Inter-eNodeB UL CoMP for Video Services (FDD)
9.2.1 Principles
9.2.2 Network Analysis
9.2.2.1 Benefits
9.2.2.2 Impacts
9.2.3 Requirements
9.2.3.1 Licenses
9.2.3.2 Software
9.2.3.3 Hardware
9.2.3.4 Others
9.2.4 Operation and Maintenance
9.2.4.1 Data Configuration
9.2.4.1.1 Data Preparation
9.2.4.1.2 Using MML Commands
9.2.4.1.3 Using the MAE-Deployment
9.2.4.2 Activation Verification
9.2.4.3 Network Monitoring
10 Turbo Start Video

2024-05-07 10
eRAN FDD Feature Documentation

10.1 Principles
10.2 Network Analysis
10.2.1 Benefits
10.2.2 Impacts
10.3 Requirements
10.3.1 Licenses
10.3.2 Software
10.3.3 Hardware
10.3.4 Others
10.4 Operation and Maintenance
10.4.1 Data Configuration
10.4.1.1 Data Preparation
10.4.1.2 Using MML Commands
10.4.1.3 Using the MAE-Deployment
10.4.2 Activation Verification
10.4.3 Network Monitoring
11 Parameters
12 Counters
13 Glossary
14 Reference Documents

This chapter describes changes not included in the "Parameters", "Counters", "Glossary", and "Reference
Documents" chapters. These changes include:

• Technical changes
Changes in functions and corresponding parameters

• Editorial changes
Text improvements or revisions while functions remain unchanged

• 1.1 eRAN17.1 03 (2021-11-27)

• 1.2 eRAN17.1 02 (2021-06-26)

• 1.3 eRAN17.1 01 (2021-03-05)

• 1.4 eRAN17.1 Draft A (2020-12-29)

1.1 eRAN17.1 03 (2021-11-27)

This issue includes the following changes.

Technical Changes

None

2024-05-07 11
eRAN FDD Feature Documentation

Editorial Changes

Added the impact relationship between NSA networking based on EPC and turbo start video (TCP/IP-based
data services with ROHC). For details, see 10.2.2 Impacts.

1.2 eRAN17.1 02 (2021-06-26)

Technical Changes

None

Editorial Changes

Added the mutually exclusive relationship between TTI bundling and Static Multiple Beam. For details, see
Mutually Exclusive Functions.
Revised descriptions in this document.

1.3 eRAN17.1 01 (2021-03-05)

This issue includes the following changes.

Technical Changes

None

Editorial Changes

Deleted descriptions of the BookBBU5901.

Added descriptions of SC-based video service identification. For details, see 4.4.1 Data Configuration.
Revised descriptions in this document.

1.4 eRAN17.1 Draft A (2020-12-29)

This issue introduces the following changes to eRAN16.1 03 (2019-07-29).

Technical Changes

Change Description Parameter Change RAT Base Station

Model

Added identification of video-service UDP Added the PORT_NUMBER_OPT_SW FDD 3900 and 5900
flows. For details, see 4.1.1 SC-based Video option to the ScPolicy. ScAlgoSwitch series base
Service Identification. parameter. stations
DBS3900
LampSite and

2024-05-07 12
eRAN FDD Feature Documentation

Change Description Parameter Change RAT Base Station

Model

DBS5900
LampSite

Added support for UDP flow acceleration by air Added the UDP_FLOW_ACC_SW FDD 3900 and 5900
interface acceleration guarantee for network option to the ScPolicy. ScAlgoSwitch series base
services. For details, see 4.1.2 SC-based parameter. stations
Identification of Acceleration Guarantee UEs.
DBS3900
LampSite and
DBS5900
LampSite

Added differentiated rate guarantee for video Added the SpidCfg. FDD 3900 and 5900
service UEs. For details, see 7.1 SC-based Video DlServiceGbrCoeff parameter. series base
Service Rate Adaption. stations
DBS3900
LampSite and
DBS5900
LampSite

Added the impact relationship between None FDD 3900 and 5900
dynamic multi-carrier management and video series base
TTI bundling. For details, see 9.1.2.2 Impacts. stations
DBS3900
LampSite and
DBS5900
LampSite

Added the impact relationship between None FDD 3900 and 5900
dynamic multi-carrier management and inter- series base
eNodeB UL CoMP for video services. For details, stations
see 9.2.2.2 Impacts.
DBS3900
LampSite and
DBS5900
LampSite

Added support for all features involved in video None FDD 3900 and 5900
experience optimization by the BookBBU5901. series base
For details, see the "Hardware" section of each stations
feature.
DBS3900
LampSite and
DBS5900
LampSite

Editorial Changes

Modified the optimal gain requirements for SC-based video service rate adaption, and descriptions about
network monitoring. For details, see 7.1.2.1 Benefits.

2024-05-07 13
eRAN FDD Feature Documentation

Added the requirements on UEs to support video TTI bundling. For details, see 9.1.3.4 Others.
Revised descriptions in this document.

• 2.1 General Statements

• 2.2 Applicable RAT

• 2.3 Features in 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

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.

2.2 Applicable RAT

This document applies to FDD.

2.3 Features in This Document

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

LOFD-110221 Initial Acceleration 5.1 WTCP Proxy

2024-05-07 14
eRAN FDD Feature Documentation

Feature ID Feature Name Chapter/Section

5.2 Air Interface Acceleration Guarantee for Network

Services

5.3 Enhanced TCP Link Setup Acceleration

LOFD-081203 Video Service Rate Adaption 7.1 SC-based Video Service Rate Adaption

7.2 DSCP-based Video Service Rate Adaption

7.3 Video Service Load Control

7.4 Video Resource Control in Congestion Scenarios

7.5 VOD Optimization

7.6 DSCP-based IPTV QoS Guarantee in WTTx Scenarios

LOFD-081202 Busy-Hour Download Rate Control 8 Busy-Hour Download Rate Control

LOFD-120205 Uplink Coverage Improvement for 9.1 Video TTI Bundling (FDD)
Video
9.2 Inter-eNodeB UL CoMP for Video Services (FDD)

LAOFD- Turbo Start Video 10 Turbo Start Video

131204

LBFD-151010 Video Service over IPv6 4 SC-based Service Identification

5.1 WTCP Proxy

5.3 Enhanced TCP Link Setup Acceleration

6 Initiative TCP Packet Ordering

Video services have been developing rapidly, and streaming video services are becoming increasingly
popular on LTE networks. They have been producing a higher proportion of the traffic, and users are
demanding a better experience with these services.
The video experience optimization solution provides initial acceleration, rate adaption, intensive coverage
improvement, and other functions for video services. These functions optimize video service performance
based on video playback characteristics.
Table 3-1 Functions related to reduction of service setup delay
Feature Function Name Applicable Service Supported
Name Protocol

Initial 5.1 WTCP Proxy Transmission Control Protocol (TCP) services on ports IPv4 and
Acceleration 80, 8080, and 443, including web page and video IPv6
services

Initial 5.2 Air Interface Specific network services performed by acceleration IPv4 and
Acceleration Acceleration Guarantee guarantee UEs identified based on service IPv6
for Network Services classification (SC), such as accessing specific DNS
addresses or video applications

2024-05-07 15
eRAN FDD Feature Documentation

Feature Function Name Applicable Service Supported

Name Protocol

Initial 5.3 Enhanced TCP Link QoS class identifier (QCI) 6–9 services based on the IPv4 and
Acceleration Setup Acceleration Hypertext Transfer Protocol (HTTP) or Hypertext IPv6
Transfer Protocol Secure (HTTPS)

None 6 Initiative TCP Packet TCP packets IPv4 and

Ordering IPv6

Table 3-2 Functions related to playback rate controlling

Feature Name Function Name Applicable Service Supported Protocol

Video Service 7.1 SC-based Video Service Video services identified based on IPv4 and IPv6
Rate Adaption Rate Adaption SC

Video Service 7.2 DSCP-based Video Video services identified based on eNodeB IP address
Rate Adaption Service Rate Adaption differentiated services code points configuration is not
(DSCPs) involved.

Video Service 7.3 Video Service Load Either of the following service IPv4 and IPv6
Rate Adaption Control types:
Video services whose rates are
adjusted based on SC
Video services whose rates are
adjusted based on DSCPs

Video Service 7.4 Video Resource Control Video services identified based on IPv4 and IPv6
Rate Adaption in Congestion Scenarios SC

Video Service 7.5 VOD Optimization Video on Demand (VOD) services IPv4
Rate Adaption identified based on UE and eNodeB
capabilities

Video Service 7.6 DSCP-based IPTV QoS Internet Protocol television (IPTV) eNodeB IP address
Rate Adaption Guarantee in WTTx services identified based on DSCPs configuration is not
Scenarios involved.

Busy-Hour 8 Busy-Hour Download Download services identified based eNodeB IP address

Download Rate Rate Control on DSCPs configuration is not
Control involved.

Table 3-3 Functions related to enhancement of uplink service coverage

Feature Name Function Name Applicable Service Supported
Protocol

Uplink Coverage 9.1 Video TTI Bundling Video services identified based on SC and IPv4 and IPv6
Improvement for Video (FDD) without bearers for VoLTE or push to talk
(PTT) services

Uplink Coverage 9.2 Inter-eNodeB UL Video services identified based on SC IPv4 and IPv6
Improvement for Video CoMP for Video Services
(FDD)

Turbo Start Video 10 Turbo Start Video Uplink TCP/IP services IPv4 and IPv6

2024-05-07 16
eRAN FDD Feature Documentation

DSCP-based service identification requires service awareness devices (integrated in the core network or
third-party devices). Detailed identification principles are not described in this document. SC-based service
identification depends on the traffic models of services. It is accomplished by the eNodeB and does not
require support from other devices. For details, see 4 SC-based Service Identification.
In NSA Option 3x, no PDCP entity is defined for the UE on the LTE network. In this case, SC-based service
identification and initial acceleration do not take effect.

Service classification (SC)-based service identification is implemented by the eNodeB, without depending
on other devices. Specifically, it provides the following functions: SC-based video service identification and
SC-based identification of acceleration guarantee UEs.
Table 4-1 Video experience optimization based on SC-based service identification
Function Name SC-based Identification of SC-based Video Service
Acceleration Guarantee UEs Identification

5.2 Air Interface Acceleration Guarantee Yes No

for Network Services

7.1 SC-based Video Service Rate Adaption No Yes

7.3 Video Service Load Control No

Yesa

7.4 Video Resource Control in Congestion No Yes

Scenarios

9.1 Video TTI Bundling (FDD) No Yes

9.2 Inter-eNodeB UL CoMP for Video No Yes

Services (FDD)

a: Video service load control is to optimize video services identified based on DSCPs or SC.

• 4.1 Principles

• 4.2 Network Analysis

• 4.3 Requirements

• 4.4 Operation and Maintenance

4.1 Principles

4.1.1 SC-based Video Service Identification

This function is applicable to:

• Streaming services with standardized QCIs 3, 6, 7, 8, and 9 that comply with the Quick UDP Internet
Connections (QUIC), HTTP, or HTTPS

2024-05-07 17
eRAN FDD Feature Documentation

This function supports QCI 3. However, QCI 3 indicates a GBR bearer and applies only to some
features and functions. Therefore, QCI 3 is not recommended for video services. It is recommended
that QCI 3 be used only for low-latency services. For details, see Air Interface Latency Optimization .

• HTTP-, HTTPS-, and QUIC-based services with extended QCIs and with the QciPara. ServiceType
parameter set to LowDelay or TCPorBuffStreaming

Figure 4-1 shows the implementation of this function. This function is enabled when the parameters are
set according to Table 4-2.

Figure 4-1 Flowchart for SC-based video service identification

Table 4-2 Parameter settings for SC-based video service identification

Supported Protocol Setting of ScPolicy. ScAlgoSwitch Setting of ScAppParaCfg. AppCfgTargetInd

IPv4 Select the SC_SERVICE_IDENTITY_SW option. VideoIdentInd

IPv4 and IPv6 Select both of the following options: VideoIdentInd

SC_SERVICE_IDENTITY_SW
SC_SUPPORT_IPV6_SW

An eNodeB uses the characteristics of video service traffic and video application servers to identify video
services. The implementation is as follows:

2024-05-07 18
eRAN FDD Feature Documentation

• Characteristics of video service traffic include the packet size, traffic volume, and percentages of
uplink and downlink packets. After a service is set up, the eNodeB identifies it as a video service if the
traffic characteristics of service packets match those of video services.

• Characteristics of a video application server include the server IP address and application rule of the
server IP address.

• If an operator needs to perform video matching using the query method, set the ScAppParaCfg.
MatchRule parameter to Query. Figure 4-2 shows the access process. The IP address of video
application server B is the server IP address.

• If an operator needs to perform video matching using the relevancy method, set the
ScAppParaCfg. MatchRule parameter to Relevancy. Figure 4-3 shows the access process. The IP
address of video application server B is the server IP address.

Figure 4-2 Video access process in the case of the query method

2024-05-07 19
eRAN FDD Feature Documentation

Figure 4-3 Video access process in the case of the relevancy method

After selecting the SC_SERVICE_IDENTITY_SW option of the ScPolicy. ScAlgoSwitch parameter, you can run
the DSP SCAPPINFO command to display common characteristics of a video application server. If the video
application server to be configured is not displayed, run the ADD SCAPPPARACFG command to configure
the server.
In addition, to enable this function, you must set the ScAppParaCfg. AppIdentType and ScAppParaCfg.
AsParaGroupID parameters to specify the application identification type and the ID of an acceleration
guarantee parameter group, respectively.
The ScAppParaCfg. ProtocolType and ScAppParaCfg. PortNumber parameters have been added to specify
the protocol and port number for services to be identified, as shown in Table 4-3. This helps to accurately
identify HTTP, HTTPS, and QUIC streaming media services. These parameters take effect only if the
ScAppParaCfg. MatchRule parameter is set to Query.
Table 4-3 Parameter settings for accurate video service identification
ScAppParaCfg. AppCfgTargetInd ScAppParaCfg. ProtocolType ScAppParaCfg. PortNumber

VideoIdentInd TCP Non-zero value

UDP 443

BOTH 443

If the ScAppParaCfg. PortNumber parameter is set to 0, the eNodeB identifies all TCP ports and only UDP
ports 0 and 443 based on the protocol type specified by the ScAppParaCfg. ProtocolType parameter. To
enable the eNodeB to identify video services carried on UDP ports other than ports 0 and 443, select the
PORT_NUMBER_OPT_SW option of the ScPolicy. ScAlgoSwitch parameter.

2024-05-07 20
eRAN FDD Feature Documentation

The eNodeB's ability to identify video services is affected if:

• A UE does not send a DNS request again for video access since it already stores the DNS for its
previous access to the video application in its buffer. In this case, the eNodeB cannot identify video
services accurately.

• A UE does not perform a DNS query again when it re-accesses a video after a bearer release or inter-
eNodeB handover during video playback. In this case, the video service identification rate of the
eNodeB decreases.

4.1.2 SC-based Identification of Acceleration Guarantee UEs

This function is applicable to:

• HTTP- and HTTPS-based services with standardized QCIs 3, 6, 7, 8, and 9

This function supports QCI 3. However, QCI 3 indicates a GBR bearer and applies only to some
features and functions. It is recommended that QCI 3 be used only for low-latency services. For details,
see Air Interface Latency Optimization .

• HTTP- and HTTPS-based services with extended QCIs and for which the QciPara. ServiceType
parameter is set to LowDelay or TCPorBuffStreaming

The eNodeB implements SC-based identification of acceleration guarantee UEs as follows:

• Identification of acceleration guarantee UEs: If a UE accesses a DNS server or IP address configured

with acceleration guarantee over the air interface (configured in the SCAPPPARACFG MO) and the
parameters are set according to Table 4-4, the eNodeB identifies the UE as an acceleration guarantee
UE and performs acceleration guarantee for the UE.

• Identification of non-acceleration guarantee UEs: If a UE accesses a service that does not match any
DNS server or IP address and the service persists for the duration specified by the ScAppParaCfg.
ServiceEndTimeThd parameter, the eNodeB identifies the UE as a non-acceleration guarantee UE.

Figure 4-4 shows the implementation process of this function.

2024-05-07 21
eRAN FDD Feature Documentation

Figure 4-4 Flowchart for SC-based identification of acceleration guarantee UEs

Table 4-4 Parameter settings for SC-based identification of acceleration guarantee UEs
Supported Supported Setting of ScPolicy. Setting of Setting of
Protocol Identification ScAlgoSwitch ScAppParaCfg. ScAppParaCfg.
Mode AppCfgTargetInd MatchRule

IPv4 and IP Select the AccelerateInd Query

IPv6 SC_SERVICE_IDENTITY_SW
option.

IPv4 DNS Select the AccelerateInd Query

SC_SERVICE_IDENTITY_SW
option.

IPv4 and DNS Select both of the following AccelerateInd Query

IPv6 options:
SC_SERVICE_IDENTITY_SW
SC_SUPPORT_IPV6_SW

In addition, to enable this function, you must set the ScAppParaCfg. AppIdentType and ScAppParaCfg.
AsParaGroupID parameters to specify the application identification type and the ID of an acceleration
guarantee parameter group, respectively.
The eNodeB uses SC to identify UEs whose video services must be guaranteed by acceleration. The
identification is only effective for the ongoing service in the current cell. When the UE moves to a cell of

2024-05-07 22
eRAN FDD Feature Documentation

another eNodeB, the identification result remains effective only if the function is also enabled for this new
cell and an X2 interface is available between the two eNodeBs.
If a service to be accessed by a UE maps to multiple application servers, that is, multiple addresses
(domain names or IP addresses), one of the addresses must be configured as the primary address, and the
others as auxiliary addresses. Whether an address is a primary or auxiliary one is specified by the
ScAppParaCfg. MainAppDnsFlag parameter. Service acceleration guarantee is performed for an auxiliary
address only if the UE accesses it after accessing the primary address.
The ScAppParaCfg. ProtocolType and ScAppParaCfg. PortNumber parameters in Table 4-5 have been
added to specify the transmission protocol and port number of videos to be identified. This helps
accurately identify acceleration guarantee UEs over the air interface. These parameters take effect only if
the ScAppParaCfg. MatchRule parameter is set to Query.
Table 4-5 Parameter settings for accurate identification of acceleration guarantee UEs
Setting of ScAppParaCfg. Setting of ScAppParaCfg. Setting of ScAppParaCfg.
AppCfgTargetInd ProtocolType PortNumber

AccelerateInd TCP Non-zero value

If the ScAppParaCfg. PortNumber parameter is set to 0, the setting of the ScAppParaCfg. ProtocolType
parameter does not take effect. In this case, the eNodeB identifies all TCP ports.
If the UDP_FLOW_ACC_SW option of the ScPolicy. ScAlgoSwitch parameter is selected, air interface
acceleration guarantee for network services supports UDP flow acceleration.

4.2 Network Analysis

4.2.1 Benefits
This function is recommended when video traffic volume information or SC-based video optimization
functions are required.

Enable this function only when the service rate on the live network (the sum of the VS.FEGE.TxMaxSpeed
and VS.FEGE.RxMaxSpeed counters) meets any of the following conditions:

• The service rate is lower than 1.1 Gbit/s if the UMPTa/UMPTb is used.

• The service rate is lower than 7.7 Gbit/s if another UMPT model (such as the UMPTe) is used.

Enabling this function in other scenarios will decrease the network traffic volume.

4.2.2 Impacts

Network Impacts

After SC-based service identification is enabled, the amount of data processed by the eNodeB increases
and the CPU load slightly increases.
The network throughput decreases if this function is enabled in scenarios where the function activation
requirements are not met.
If the ScAppParaCfg. AppIdentType parameter is set to DNS, the number of video service users identified
based on SC decreases after an eNodeB upgrade due to the reset of internal server IP address. After the

2024-05-07 23
eRAN FDD Feature Documentation

server IP address is relearned, the number of video service users identified based on SC recovers. The
number of video service users identified based on SC can be measured using the
L.Traffic.User.VideoService.Avg and L.Traffic.User.VideoService.Max counters.

Function Impacts

None

4.3 Requirements

4.3.1 Licenses
None

4.3.2 Software

Prerequisite Functions

None

Mutually Exclusive Functions

None

4.3.3 Hardware

Base Station Models

For FDD, the following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

A UMPT must be installed because this function is deployed on a main control board.

RF Modules

None

4.3.4 Other Requirements

None

4.4 Operation and Maintenance

2024-05-07 24
eRAN FDD Feature Documentation

4.4.1 Data Configuration

4.4.1.1 Data Preparation

SC-based Video Service Identification

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

• If the DSP SCAPPINFO command output does not include a video application server after the
SC_SERVICE_IDENTITY_SW option of the ScPolicy. ScAlgoSwitch parameter is selected, you need to run the ADD
SCAPPPARACFG command to add the server configuration.
• Run the DSP SCAPPINFO command to query the characteristic value of the video application server to be
configured. If the command output does not contain this video application server, contact Huawei technical
support to analyze and provide the characteristic value of the server.
• If the DSP SCAPPINFO command output includes the application DNS to be configured, you are not advised to
re-add it by running the ADD SCAPPPARACFG command.
• By default, the eNodeB integrates some domain name information. Such information is written in the
ScRuleFile.dat file, which is integrated in the eNodeB software package. You can run the DSP SCAPPINFO
command to query the default application information. If the value of Configuration Type in the command
output is Default Config, the domain name is the one integrated by the eNodeB by default.

The domain names are as follows: *c.youtube.com*, *googlevideo.com*, *fbcdn-video*akamaihd.net*,

*video.xx.fbcdn.net*, *fbcdn-creative*akamaihd.net*, *proxy*dailymotion*, *videos*ak.instagram.com*,
*hls.vimeocdn.com, skyfire.vimeocdn.com, *pdl.vimeocdn.com, cn*.acgvideo.com, vod.*.cmvideo.cn, live.*.cmvideo.cn,
pcvideo*.titan.mgtv.com, *k.youku*, pl.youku.com*, *v2.tudou.com*, *vr.tudou.com*, *vv.video.qq.com*,
*videohy.tc.qq.com*, *info.zb.qq.com*, *hot.vrs.sohu.com*, *my.tv.sohu.com*, *data.vod.itc.cn*, *api.tv.sohu.com*,
*data.video.*qiyi.com*, play.api.pptv.com, client-play.cloudxns.pptv.com, hdl*.douyu*, *edge.v.iask.com.lxdns.com*,
*edge.ivideo.sina.com.cn*, play.g3proxy.lecloud.com, n.mark.letv.com, and live.g3proxy.lecloud.com

Do not change the names of the ScRuleFile.dat and ScRuleFile.cms files in the ScRuleFile.zip file. Otherwise, the SC-
based service identification function will be affected.

Table 4-6 Parameters used for activation

Parameter Name Parameter ID Setting Notes

SC Algorithm ScPolicy. Select the SC_SERVICE_IDENTITY_SW option if SC-based service

Switch ScAlgoSwitch identification needs to be enabled.

ScPolicy. Select the SC_SUPPORT_IPV6_SW option if IPv6 services need to be

ScAlgoSwitch guaranteed.

Application Index ScAppParaCfg. None

AppDnsId

Application ScAppParaCfg. You can run the DSP SCAPPINFO command to obtain the website
Identification AppIdentType identification modes supported by the eNodeB.
Type

Application DNS ScAppParaCfg. Set this parameter when the ScAppParaCfg. AppIdentType
AppDns parameter is set to DNS.
You can run the DSP SCAPPINFO command to obtain the
application domain names supported by the eNodeB.

2024-05-07 25
eRAN FDD Feature Documentation

Parameter Name Parameter ID Setting Notes

The value of this parameter is a string of 1 to 49 characters. If a

domain name has more than 49 characters, add an asterisk (*) at
the end of the configured value and ensure that the configured
value does not exceed 49 characters.

Application IPv4 ScAppParaCfg. Set this parameter when the ScAppParaCfg. AppIdentType
AppIpv4 parameter is set to IPv4.
You can run the DSP SCAPPINFO command to obtain the website IP
addresses supported by the eNodeB.

Application IPv6 ScAppParaCfg. Set this parameter when the ScAppParaCfg. AppIdentType
AppIpv6 parameter is set to IPv6.
You can run the DSP SCAPPINFO command to obtain the website IP
addresses supported by the eNodeB.

Match Rule ScAppParaCfg. If the operator requires the query mode for video matching, set this
MatchRule parameter to Query.
If the operator requires the relevancy mode for video matching, set
this parameter to Relevancy.

Application ScAppParaCfg. None

Name AppName

Application ScAppParaCfg. Set this parameter to VideoIdentInd.

Config Target AppCfgTargetInd
Indicator

Protocol Type ScAppParaCfg. If accurate identification is required, set this parameter to TCP, UDP,
ProtocolType or BOTH.
If accurate identification is not required, the default value BOTH is
recommended. Alternatively, contact Huawei technical support to
analyze and provide the characteristic value of the video application
server.

Port Number ScAppParaCfg. If accurate identification is required:

PortNumber
When the ScAppParaCfg. ProtocolType parameter is set to TCP, set
this parameter to a non-zero value.
When the ScAppParaCfg. ProtocolType parameter is set to UDP or
BOTH, set this parameter to 443.
If accurate identification is not required, the default value 0 is
recommended. Alternatively, contact Huawei technical support to
analyze and provide the characteristic value of the video application
server.

SC Algorithm ScPolicy. If the PORT_NUMBER_OPT_SW option of the ScPolicy.

Switch ScAlgoSwitch ScAlgoSwitch parameter is selected, video-service UDP flows with a
port number other than 0 and 443 can be identified.

SC-based Identification of Acceleration Guarantee UEs

2024-05-07 26
eRAN FDD Feature Documentation

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

Table 4-7 Parameters used for activation
Parameter Name Parameter ID Setting Notes

SC Algorithm ScPolicy. ScAlgoSwitch If SC-based identification of acceleration guarantee UEs needs to

Switch be enabled, select the SC_SERVICE_IDENTITY_SW option.

ScPolicy. ScAlgoSwitch Select the SC_SUPPORT_IPV6_SW option if DNS-based

identification is required for IPv6 acceleration guarantee services.

Application Index ScAppParaCfg. None

AppDnsId

Application ScAppParaCfg. None

Identification AppIdentType
Type

Application DNS ScAppParaCfg. AppDns Set this parameter when ScAppParaCfg. AppIdentType is set to
DNS.
If a domain name has more than 49 characters, add an asterisk
(*) at the end of the configured value and ensure that the
configured value does not exceed 49 characters.

Application IPv4 ScAppParaCfg. AppIpv4 Set this parameter when ScAppParaCfg. AppIdentType is set to
IPv4.

Application IPv6 ScAppParaCfg. AppIpv6 Set this parameter when ScAppParaCfg. AppIdentType is set to
IPv6.

Application ScAppParaCfg. None

Name AppName

Match Rule ScAppParaCfg. Set this parameter to Query.

MatchRule

Main Application ScAppParaCfg. Set this parameter when the AccelerateInd option of the
DNS Flag MainAppDnsFlag ScAppParaCfg. AppCfgTargetInd parameter is selected.

Main Application ScAppParaCfg. Set this parameter when the ScAppParaCfg. MainAppDnsFlag
DNS ID MainAppDnsId parameter is set to Aid.

Accelerate ScAppParaCfg. It is recommended that this parameter vary based on

Service Para AsParaGroupID acceleration service guarantee parameter groups.
Group ID

Application ScAppParaCfg. Select the AccelerateInd option.

Config Target AppCfgTargetInd
Indicator

Service End Time ScAppParaCfg. Set this parameter to its recommended value.
Threshold ServiceEndTimeThd

Protocol Type ScAppParaCfg. If accurate identification is required, set this parameter to TCP.
ProtocolType
If accurate identification is not required, the default value BOTH
is recommended. Alternatively, contact Huawei technical support

2024-05-07 27
eRAN FDD Feature Documentation

Parameter Name Parameter ID Setting Notes

to analyze and provide the characteristic value of the video

application server.

Port Number ScAppParaCfg. If accurate identification is required, set this parameter to a non-
PortNumber zero value.
If accurate identification is not required, the default value 0 is
recommended. Alternatively, contact Huawei technical support to
analyze and provide the characteristic value of the video
application server.

SC Algorithm ScPolicy. ScAlgoSwitch If the UDP_FLOW_ACC_SW option of the ScPolicy. ScAlgoSwitch

Switch parameter is selected, air interface acceleration guarantee for
network services supports UDP flow acceleration.

4.4.1.2 Using MML Commands

Activation Command Examples

• Configuring SC-based video service identification

//Enabling SC-based video service identification for IPv4 service guarantee

MOD SCPOLICY: ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-1;
//Enabling SC-based video service identification for IPv6 service guarantee
MOD SCPOLICY: ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-1&SC_SUPPORT_IPV6_SW-1;
//Enabling identification of video-service UDP flows
MOD SCPOLICY: ScAlgoSwitch=PORT_NUMBER_OPT_SW-1;
//Configuring video services to be identified
//An example for optimized identification based on domain names
ADD SCAPPPARACFG: AppDnsId=0, AppIdentType=DNS, AppDns="*test*video.com*", MatchRule=Query,
AppCfgTargetInd=VideoIdentInd-1, AppName="Testvideo", ProtocolType=BOTH, PortNumber=0;
//An example for optimized identification based on IPv4 addresses
ADD SCAPPPARACFG: AppDnsId=1, AppIdentType=IPV4, AppIpv4="103.0.37.4", MatchRule=Query,
AppCfgTargetInd=VideoIdentInd-1, AppName="test video", ProtocolType=BOTH, PortNumber=0;
//An example for optimized identification based on IPv6 addresses
ADD SCAPPPARACFG: AppDnsId=2, AppIdentType=IPV6, AppIpv6="2001:1111:2222:3333:0003:0002:5B1E:FC4F",
MatchRule=Query, AppCfgTargetInd=VideoIdentInd-1, AppName="test video", ProtocolType=BOTH, PortNumber=0;

If the DSP SCAPPINFO command output does not include a video application server, you need to run the ADD
SCAPPPARACFG command to add the server configuration.

• Configuring SC-based identification of acceleration guarantee UEs

//Enabling SC-based identification of acceleration guarantee UEs for IPv4 service guarantee
MOD SCPOLICY: ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-1;
//Enabling SC-based identification of acceleration guarantee UEs for IPv6 service guarantee based on DNS

2024-05-07 28
eRAN FDD Feature Documentation

MOD SCPOLICY: ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-1&SC_SUPPORT_IPV6_SW-1;

//Enabling support for UDP flow acceleration by air interface acceleration guarantee for network services
MOD SCPOLICY: ScAlgoSwitch=UDP_FLOW_ACC_SW-1;
//Configuring acceleration guarantee UEs to be identified
//An example for optimized identification based on domain names
ADD SCAPPPARACFG: AppDnsId=0, AppIdentType=DNS, AppDns="pokemon", MatchRule=Query,
AppCfgTargetInd=AccelerateInd-1, MainAppDnsFlag=Main, MainAppDnsId=65535, AsParaGroupID=0,
ServiceEndTimeThd=30, AppName="pokemon", ProtocolType=BOTH, PortNumber=0;
//An example for optimized identification based on IPv4 addresses
ADD SCAPPPARACFG: AppDnsId=1, AppIdentType=IPV4, AppIpv4="103.0.37.4", MatchRule=Query,
AppCfgTargetInd=AccelerateInd-1, MainAppDnsFlag=Main, MainAppDnsId=65535, AsParaGroupID=0,
ServiceEndTimeThd=30, AppName="test IPv4", ProtocolType=BOTH, PortNumber=0;
//An example for optimized identification based on IPv6 addresses
ADD SCAPPPARACFG: AppDnsId=2, AppIdentType=IPV6, AppIpv6="2001:1111:2222:3333:0003:0002:5B1E:FC4F",
MatchRule=Query, AppCfgTargetInd=AccelerateInd-1, MainAppDnsFlag=Main, MainAppDnsId=65535,
AsParaGroupID=0, ServiceEndTimeThd=30, AppName="test IPv6", ProtocolType=BOTH, PortNumber=0;

Optimization Command Examples

None

Deactivation Command Examples

//Turning off the SC-based service identification switch when the SC support IPv6 switch is turned off
MOD SCPOLICY:ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-0;
//Turning off the SC-based service identification switch and the SC support IPv6 switch when the SC support IPv6 switch is
turned on
MOD SCPOLICY:ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-0&SC_SUPPORT_IPV6_SW-0;
//Disabling identification of video-service UDP flows
MOD SCPOLICY: ScAlgoSwitch=PORT_NUMBER_OPT_SW-0;
//Disabling support for UDP flow acceleration by air interface acceleration guarantee for network services
MOD SCPOLICY: ScAlgoSwitch=UDP_FLOW_ACC_SW-0;

4.4.1.3 Using the MAE-Deployment

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

4.4.2 Activation Verification

SC-based Video Service Identification

The function has taken effect if the value of the L.Exp.Video.Thrp.bits.DL.All counter increases significantly.

2024-05-07 29
eRAN FDD Feature Documentation

• Measurements of L.Exp.Video.ThreeWayHandShake.ValidNum ,
L.Exp.Video.Time.SynackToAck.OverThld.Num , and L.Exp.Video.ValidTime.SynackToAck are not
affected.

• If the video experience optimization feature is disabled for a bearer or UE, statistics on the bearer or
UE are not included in the measurements of other counters related to SC-based video service
identification.

SC-based Identification of Acceleration Guarantee UEs

None

4.4.3 Network Monitoring

For details about how to monitor the network after the SC-based video service identification function is
enabled, see 7.1.4.3 Network Monitoring.
For details about how to monitor the network after the SC-based identification of acceleration guarantee
UEs function is enabled, see 5.2.4.3 Network Monitoring.

This feature contains the following functions.

• WTCP proxy

• Air interface acceleration guarantee for network services

• Enhanced TCP link setup acceleration

• 5.1 WTCP Proxy

• 5.2 Air Interface Acceleration Guarantee for Network Services

• 5.3 Enhanced TCP Link Setup Acceleration

5.1 WTCP Proxy

5.1.1 Principles

5.1.1.1 WTCP Proxy

The Wireless Transmission Control Protocol (WTCP) proxy function includes WTCP proxy and data
forwarding during RRC connection reestablishment.

In Option 3x networking, the WTCP proxy function does not take effect for NSA UEs.

WTCP Proxy

2024-05-07 30
eRAN FDD Feature Documentation

The TCP download rate is determined by a combination of the transmission bandwidth and the round trip
time (RTT). For a given bandwidth, the server sends packets at a higher rate when the RTT for downlink
TCP packets decreases. This allows UEs to download videos more quickly.
According to the traditional TCP protocol, packets are transparently transmitted through the eNodeB, and
the RTT is subject to transmission of packets over the air interface, as shown in Figure 5-1.

Figure 5-1 RTT for traditional TCP packets

WTCP proxy allows the eNodeB to serve as a proxy for downlink TCP packets during the initial stage of
TCP streaming. The maximum number of proxy packets is specified by the WtcpProxyAlgo.
MaxProxyPktNum parameter. Figure 5-2 shows packet interaction for a TCP stream.

Figure 5-2 Packet interaction for a TCP stream with WTCP proxy enabled

During packet interaction for a TCP stream with WTCP proxy enabled:

• The eNodeB serves as a proxy for the UE to communicate with the server.
The eNodeB responds with a TCP ACK packet on behalf of the UE after receiving a downlink TCP
packet from the server, reducing the RTT.

• The eNodeB acts as a server to communicate with the UE.

The eNodeB transmits downlink TCP packets to the UE and processes the TCP ACK packet sent by the
UE.

2024-05-07 31
eRAN FDD Feature Documentation

• The WTCP proxy function takes effect only for TCP packets sent to ports 80, 8080, and 443.
• The send window on the server is calculated using the following formula when the traditional TCP is used: Send
window on the server = min(Receive window, Congestion window). A typical congestion window is small due to
the slow start phase. This means that the send window size on the server is equal to the congestion window size.
• The eNodeB send window is equivalent to the receive window when the WTCP proxy function is used.

After WTCP proxy is enabled, the RTT is reduced, which means that the server sends packets to the
eNodeB at a higher rate. A sufficient amount of data exists on the eNodeB. The send window grows rapidly
on both the server and the eNodeB, and data transmission time is reduced.
WTCP proxy is enabled if the parameters are set according to Table 5-1. Enabling or disabling WTCP proxy
affects only UEs that newly access the network.
Table 5-1 Parameter settings for WTCP proxy
Supported Setting of WtcpProxyAlgo. Setting of ENodeBAlgoSwitch.
Protocol TcpAccelerationSwitch TpeSwitch

IPv4 and IPv6 ON Select the TcpSupportIpv6Switch option.

IPv4 ON Deselect the TcpSupportIpv6Switch

option.

The eNodeB will not serve as a WTCP proxy for any new TCP link when the CPU usage is excessively high
(for example, LBBPd CPU usage over 70% or UBBPd CPU usage over 50%), the number of RRC connections
in the cell exceeds 150, or the remaining BBP memory is insufficient. In addition, the eNodeB ceases
serving as a WTCP proxy for any existing TCP link in the event of insufficient BBP memory or a large
number of retransmitted or out-of-order packets.
Unlike traditional TCP, WTCP proxy easily causes timestamps of UEs and the eNodeB to be out of
synchronization. To resolve this issue, the eNodeB removes timestamps of TCP packets during TCP link
setup.

Data Forwarding During RRC Connection Reestablishment

WTCP proxy allows the source eNodeB to forward all buffered data of a UE through the X2 interface to the
target eNodeB during RRC connection reestablishment of the UE if an X2 interface is set up between the
source and target eNodeBs, as shown in Figure 5-3. This prevents services from being interrupted when the
WTCP proxy function is enabled.

Figure 5-3 Data forwarding during RRC connection reestablishment

2024-05-07 32
eRAN FDD Feature Documentation

5.1.1.2 WTCP Proxy Optimization

Enhanced WTCP Proxy

After WTCP proxy is enabled, the following issues may occur:

• ACK messages returned by the WTCP proxy are lost, causing TCP links to be released inappropriately.

• An insufficient UE window occurs when the eNodeB is waiting for out-of-order TCP packets, causing
packet loss.

Enhanced WTCP proxy is controlled by the WTCP_LOST_PACKET_SWITCH option of the WtcpProxyAlgo.

WtcpEnhancementSwitch parameter. Enhanced WTCP proxy is recommended to avoid TCP link releases
and packet loss caused by invalid retransmissions in the case of WTCP proxy.

Air Interface Scheduling Acceleration for WTCP

In heavy load scenarios, congestion over the air interface prevents timely transmission of downlink TCP
packets buffered by a WTCP proxy. Downlink TCP packets buffered for a long time lead to retransmission
timeout (RTO) on the server side. Air interface scheduling acceleration for WTCP is recommended to
resolve the RTO issue. NSA UEs do not support this function.
Air interface scheduling acceleration for WTCP is controlled by the WtcpProxyAlgo. WtcpDlRttTimer
parameter. This function depends on the ScAppParaCfg. AppIdentType and ScAppParaCfg.
AppCfgTargetInd parameters. Air interface scheduling acceleration for WTCP can be enabled only when
the following conditions are met:

• The WtcpProxyAlgo. WtcpDlRttTimer parameter is set to a non-zero value.

• The ScAppParaCfg. AppIdentType parameter is set to WTCP.

• The ScAppParaCfg. AppCfgTargetInd parameter is set to AccelerateInd.

The TCP downlink RTT timer is configured for the eNodeB using the WtcpProxyAlgo. WtcpDlRttTimer
parameter.

• If a TCP ACK response to the downlink TCP packet is not received when the timer expires, air interface
scheduling acceleration for WTCP proxy is enabled.

• If a TCP ACK response to the downlink TCP packet is received before the timer expires, air interface
scheduling acceleration for WTCP proxy is disabled.

Smooth WTCP Proxy Termination

If the number of WTCP proxy packets reaches the maximum value, WTCP proxy is terminated. Then, the
UE, instead of the WTCP proxy, sends the TCP ACK messages to the server. Abrupt termination of a WTCP
proxy results in a sudden increase in the delay for TCP ACK message reception on the server side,
triggering the retransmission on timeout mechanism of the server, which reduces the TCP packet
transmission rate.

2024-05-07 33
eRAN FDD Feature Documentation

Smooth WTCP proxy termination resolves this issue. If the number of packets buffered by the WTCP proxy
exceeds the buffer protection threshold (specified by the WtcpProxyAlgo. RtoProtectionBufferThld
parameter), smooth WTCP proxy termination is triggered to avoid retransmission caused by timeouts on
the server side.

5.1.2 Network Analysis

5.1.2.1 Benefits

Gains

The newly introduced WTCP proxy reduces the RTT, especially for the first 200 packets. (The maximum
number of downlink TCP packets sent by the WTCP proxy is specified by the WtcpProxyAlgo.
MaxProxyPktNum parameter.) Figure 5-4 compares expedited packet transmission during the initial stage
of TCP streaming using WTCP and traditional TCP.

Figure 5-4 Packet transmission during the initial stage of TCP streaming using WTCP and traditional TCP

Packet transmission acceleration during the initial stage of TCP streaming reduces the initial video
buffering delay. The degree of reduction is determined by the bit rate of the video source, the ratio of RTT
1 to RTT 2 (see Figure 5-5), and the packet loss or out-of-order rate. Under the same conditions, this
function offers lower gains when the video source has a higher bit rate, the ratio of RTT 1 to RTT 2 is low,
or the packet loss or out-of-order rate is high.

Figure 5-5 RTT 1 and RTT 2

2024-05-07 34
eRAN FDD Feature Documentation

Most Beneficial Scenarios

Operators are advised to enable WTCP proxy to improve user experience with video and web browsing
services when they wish to reduce the initial video buffer delay or web page loading time and their
network meets the following requirements:

• Transport network requirements

The upstream packet loss rate and packet out-of-order rate at the TCP layer are low (preferably lower
than 0.1% and 2%, respectively). Otherwise, TCP acceleration by the WTCP proxy function will reduce
the throughput.
The packet loss rate and out-of-order rate are collected by a third-party TCP counter measurement
device deployed on the core network or transport network.

• RRC connection reestablishment requirements

• UEs must support data forwarding during RRC connection reestablishment. If there are UEs
incompatible with this function on the live networks, add UEs to the blacklist to prevent the
service drop rate from increasing. For details, see Terminal Awareness Differentiation .

• The RRC connection reestablishment proportion must be low (preferably less than 2%). A high
rate will cause too much data to be forwarded for CEUs, leading to deterioration of KPIs such as
the BLER and service drop rate.
RRC connection reestablishment proportion = L.RRC.ReEst.Att / L.RRC.ConnReq.Succ

• Mobility requirements

• X2 interfaces must be configured between eNodeBs to ensure that WTCP proxy can properly
forward data for inter-eNodeB handovers or RRC connection reestablishment and avoid TCP link
disconnection due to packet loss.

• Handovers must not be performed frequently in scenarios such as high-speed cells. If there are
too many handovers, there is a high probability that the packet loss from frequent data
forwarding will cause TCP links to disconnect.

• The inter-RAT redirection proportion must be low (preferably less than 5%). Otherwise, there is a
high probability that inter-RAT mobility causes service interruptions.
Inter-RAT redirection proportion = ( L.RRCRedirection.E2W + L.RRCRedirection.E2G +
L.RRCRedirection.E2T + L.RRCRedirection.E21xRTT + L.RRCRedirection.E2HRPD )/
L.RRC.ConnReq.Succ

• TCP protocol compatibility requirements

• The IP packet detection and discarding based on the time to live (TTL) field in the IP headers
must not be deployed on devices on the live network except for the eNodeBs.

• TCP optimization functions must not be deployed on devices on the live network except for the
eNodeBs.

2024-05-07 35
eRAN FDD Feature Documentation

• Functions depending on IP options or less-commonly used TCP options (options other than
Window Scale, Maximum Segment Size, SACK, SACK Permitted, Timestamps, End of Option List,
and No-Operation) must not be deployed on devices on the live network except for eNodeBs.

• eNodeBs comply with the universal simplified TCP protocol and work properly with most UEs and servers. In
certain special scenarios, however, eNodeBs may be incompatible with UEs and servers at the TCP layer, causing
negative gains.
• User behavior on networks is complicated and diverse. When the preceding conditions are met, it is
recommended that the function first be enabled on a small scale for more than one week and then only be
enabled on a large scale if services and counters are stable.

5.1.2.2 Impacts

Network Impacts

• The CPU load of the BBPs increases slightly.

• This feature uses data forwarding during RRC connection reestablishments. Data forwarding ensures
uninterrupted data transmission even when a large number of RRC connections are reestablished.
However, because most UEs in this scenario are located at the cell edge, this feature increases the
number of cell edge users (CEUs) and the duration of their data transmission. This may negatively
impact other KPIs, such as the service drop rate and block error rate.

• After WTCP is enabled, the download delay in the initial TCP phase decreases, but the value of the
L.Traffic.DL.PktDelay.Time counter may increase.

• After air interface scheduling acceleration for WTCP is enabled, the value of the
L.PDCP.Tx.Disc.Trf.SDU counter may decrease.

Function Impacts

RAT Function Function Switch Reference Description

Name

FDD High speed Cell. HighSpeedFlag High Speed Frequent handovers reduce
mobility Mobility the gains offered by the
WTCP proxy function.

FDD Ultra high Cell. HighSpeedFlag High Speed Frequent handovers reduce
speed Mobility the gains offered by the
mobility WTCP proxy function.

FDD Video CONGEST_VIDEO_RES_CTRL_SWITCH Video If video resource control in

resource option of the CellAlgoSwitch. Experience congestion scenarios takes
control in DlSchExtSwitch parameter Optimization effect for a UE running
congestion video services, air interface
scenarios scheduling acceleration for

2024-05-07 36
eRAN FDD Feature Documentation

RAT Function Function Switch Reference Description

Name

WTCP does not take effect

for this UE.

5.1.3 Requirements

5.1.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LOFD-110221 Initial Acceleration LT1S000VEO00 Per Cell

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

None

Mutually Exclusive Functions

None

5.1.3.3 Hardware

Base Station Models

3900 and 5900 series base stations

Boards

This function is deployed on BBPs, which must not be the LBBPc.

RF Modules

No requirements

5.1.3.4 Others

• WTCP Proxy

• WTCP proxy: no requirement

• Data forwarding during RRC connection reestablishment: UEs must support this function.

• WTCP Proxy Optimization: no requirement

2024-05-07 37
eRAN FDD Feature Documentation

5.1.4 Operation and Maintenance

5.1.4.1 Data Configuration

5.1.4.1.1 Data Preparation
Table 5-2 describes the parameters used for function activation. This section does not describe the
parameters related to cell establishment.
Table 5-2 Parameters used for activation
Parameter Parameter ID Setting Notes
Name

Local cell ID WtcpProxyAlgo. LocalCellId This ID must have been set in the Cell MO.

TCP WtcpProxyAlgo. Set this parameter to ON.

Acceleration TcpAccelerationSwitch
Switch

TCP Statistics WtcpProxyAlgo. You need to set this parameter to ON one week before
Switch TCPStatisticsSwitch enabling the WTCP proxy function. The TCP statistics function
is used to obtain statistical data with WTCP proxy enabled
and disabled, which is then compared to evaluate feature
benefits. For details, see 5.1.4.3 Network Monitoring.

Max Number of WtcpProxyAlgo. Set this parameter to its recommended value.

Proxy Packets MaxProxyPktNum

WTCP WtcpProxyAlgo. You are advised to select the WTCP_LOST_PACKET_SWITCH

Enhancement WtcpEnhancementSwitch option to enable the enhanced WTCP function to avoid TCP
Switch link release and packet loss caused by invalid retransmission.

WTCP Downlink WtcpProxyAlgo. Air interface scheduling acceleration for WTCP proxy is
RTT Timer WtcpDlRttTimer recommended to avoid RTO on the server side.
It is recommended that this parameter be set to 12, that is,
120 ms.

RTO Protection WtcpProxyAlgo. Set this parameter to its recommended value.

Buffer RtoProtectionBufferThld
Threshold

Application ScAppParaCfg. Set this parameter to WTCP if air interface scheduling

Identification AppIdentType acceleration for WTCP is enabled.
Type

Application ScAppParaCfg. Select the AccelerateInd option if air interface scheduling

Config Target AppCfgTargetInd acceleration for WTCP is enabled.
Indicator

TPE switch ENodeBAlgoSwitch. Select the TcpSupportIpv6Switch option to enable IPv6 service
TpeSwitch guarantee.

5.1.4.1.2 Using MML Commands

Activation Command Examples

2024-05-07 38
eRAN FDD Feature Documentation

//When air interface scheduling acceleration for WTCP is enabled, it is recommended that the ADD ASPARAGROUP
command be executed before the ADD SCAPPPARACFG command is executed.
ADD ASPARAGROUP: AsParaGroupID=11, AsPreallocDuration=2000, AsPreallocMinPeriod=5, AsPreallocSize=80,
AsSchPriFactor=50;
ADD SCAPPPARACFG: APPDNSID=101,APPIDENTTYPE=WTCP, MATCHRULE=Query, APPCFGTARGETIND=VideoIdentInd-
0&AccelerateInd-1&ServiceTraceInd-0, AsParaGroupID=11;
//Enabling WTCP proxy
MOD WTCPPROXYALGO: LocalCellId=0, TcpAccelerationSwitch=ON, TCPStatisticsSwitch=ON, MaxProxyPktNum=200,
WtcpEnhancementSwitch=WTCP_LOST_PACKET_SWITCH-1, WtcpDlRttTimer=12, RtoProtectionBufferThld=5;
//Turning on the TCP service support IPv6 switch when support for the IPv6 protocol is required for WTCP proxy
MOD ENODEBALGOSWITCH: TpeSwitch=TcpSupportIpv6Switch-1;

Deactivation Command Examples

MOD WTCPPROXYALGO: LocalCellId=0, TcpAccelerationSwitch=OFF;

5.1.4.1.3 Using the MAE-Deployment

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

5.1.4.2 Activation Verification

Observe the L.PDCP.TCP.WTCPProxy.Succ counter. If the counter value is not 0, this function has taken
effect.

5.1.4.3 Network Monitoring

The following methods are recommended to monitor performance:

• Perform drive tests (DTs) and compare the single-UE download delay during the initial stage of the
TCP process before and after WTCP proxy is enabled to evaluate how much the delay is reduced.

• Use performance counters. This method applies only to UEs that newly access the network.

1. Set the WtcpProxyAlgo. TCPStatisticsSwitch parameter to ON.

2. Measure the average transmission rate during the initial stage of the TCP process before WTCP
proxy is enabled.
Average transmission rate during the initial stage of the TCP process =
L.Thrp.TCP.Bytes.InitTransfer / L.Thrp.TCP.Time.InitTransfer

3. Enable WTCP proxy one week later and measure the average transmission rate during the initial
stage of the TCP process again.

4. Compare the average initial TCP transmission rate with WTCP proxy enabled to the rate when it
is disabled to evaluate how much the download rate in the initial stage of the TCP process has
improved.

2024-05-07 39
eRAN FDD Feature Documentation

The average transmission rate during the initial stage of the TCP process cannot reflect service experience.
If this rate does not increase significantly after WTCP proxy is enabled, perform DTs to evaluate the gains
offered by WTCP proxy.

• Start IFTS132 tracing to capture packets and analyze the decrease of the single-UE download delay
during the initial stage of the TCP process after WTCP proxy is enabled.

5.2 Air Interface Acceleration Guarantee for Network Services

5.2.1 Principles
The service setup delay and service rate have a large impact on user experience during web browsing and
video playback. As shown in Figure 5-6, the scheduling delay affects the service setup delay during web
service setup.

Figure 5-6 Service setup procedure before the function is enabled

Air interface acceleration guarantee for network services provides acceleration guarantee for UEs
performing specific network services, such as UEs that access a specific DNS server or video application.
The eNodeB uses SC to identify a UE whose video services must be guaranteed by acceleration. This
function is controlled by the CellAlgoSwitch. AsAlgoSwitch parameter. For details about SC-based
identification of acceleration guarantee UEs, see 4.1.2 SC-based Identification of Acceleration Guarantee
UEs.

This function requires SC-based service identification to support the IPv4 and IPv6 protocols.

The eNodeB performs the following operations after air interface acceleration guarantee for network
services is enabled, as shown in Figure 5-7.

2024-05-07 40
eRAN FDD Feature Documentation

• The eNodeB performs preallocation by proactively sending uplink scheduling indications to the UE. In
this way, uplink and downlink packets are promptly scheduled, reducing service setup delay.

• During the entire service guarantee process, higher uplink and downlink scheduling priorities are used,
the CQI adjustment value is configured, the DRX policy is disabled, PDCCH boundary power control
optimization is enabled, and the UE inactivity timer is configured independently. This helps reduce the
service setup delay and increase the uplink and downlink service rates. Only LTE FDD supports the
PDCCH boundary power control optimization function.

Figure 5-7 Service setup procedure after the function is enabled

The eNodeB performs acceleration guarantee for UEs identified as acceleration guarantee UEs according to
the settings of the following parameters:

• AsParaGroup. AsPreallocDuration indicates the preallocation duration.

• AsParaGroup. AsPreallocSize indicates the volume of data for each preallocation.

• AsParaGroup. AsPreallocMinPeriod indicates the preallocation interval.

• AsParaGroup. AsSchPriFactor : The scheduling priority equals the original scheduling priority
multiplied by the value of this parameter.

• AsParaGroup. AsParaGroupID indicates the scheduling policy for each group. Different scheduling
policies are used for different UEs.

• AsParaGroup. AsNackCqiAdjValue indicates the decrease in the CQI adjustment value when
acceleration guarantee UEs send NACK messages.

• AsParaGroup. AccelerationServiceOptSw

• The ENTER_DRX_SWITCH option of this parameter controls DRX for acceleration guarantee UEs.

2024-05-07 41
eRAN FDD Feature Documentation

• For FDD, the PDCCH_BOUNDARY_PC_OPT_SW option controls PDCCH boundary power control
optimization for acceleration guarantee UEs.

• The MLB_AND_MBOCS_PROHIBITION_SW option of this parameter specifies whether to transfer

acceleration guarantee UEs for MLB and MBOCS.

• The PERIODIC_MEAS_OPT_SWITCH option specifies whether acceleration guarantee UEs perform

periodic inter-frequency or inter-RAT MR and MDT measurements.

• AsParaGroup. AccServiceUeInactivityTmr specifies the UE inactivity timer for acceleration guarantee

UEs. This parameter takes effect for UEs without QCI 1 bearers.

The air interface acceleration guarantee function takes effect only when the CellAlgoSwitch. AsAlgoSwitch
parameter is set to ON and a parameter group for air interface acceleration is added by running the ADD
AsParaGroup command.

In CA scenarios, the air interface acceleration guarantee function takes effect only after the following
configurations are complete:

• In intra-eNodeB CA scenarios, the CellAlgoSwitch. AsAlgoSwitch parameter must be set to ON for

both the PCell and SCells, but only the PCell needs to be configured with a parameter group for air
interface acceleration by running the ADD AsParaGroup command.

• In inter-eNodeB CA scenarios, the CellAlgoSwitch. AsAlgoSwitch parameter must be set to ON for

both the PCell and SCells, and both PCell and SCells need to be configured with parameter groups for
air interface acceleration by running the ADD AsParaGroup command.

5.2.2 Network Analysis

5.2.2.1 Benefits

Gains

This function reduces the service setup delay and increases the download rate for acceleration guarantee
UEs accessing a specific DNS server or IP address. The service setup delay is the delay between TCP SYN
and the first downlink service packet. When DRX is enabled, the delay can be reduced by up to 10%. This
function offers notable gains when air interface resources are limited and high throughput is required to
maintain service quality. Service rates of acceleration guarantee UEs can be improved by up to 20% in such
scenarios.
The gains offered by air interface acceleration guarantee for network services are affected as follows:

• When the ENTER_DRX_SWITCH option of the AsParaGroup. AccelerationServiceOptSw parameter is

selected:

• If DRX is enabled, air interface acceleration guarantee for network services reduces delays only
when the UE in the DRX sleep state receives downlink packets during service setup.

• If DRX is disabled, air interface acceleration guarantee for network services is less effective in
reducing delays.

2024-05-07 42
eRAN FDD Feature Documentation

For details about how to activate and verify DRX, see DRX and Signaling Control .

• If SPID-based preallocation is enabled, air interface acceleration guarantee for network services is less
effective in reducing delays.

• If the SC-based video service rate adaption function of the video service rate adaption feature is
enabled, it does not offer combined gains with air interface acceleration guarantee for network
services because a higher downlink scheduling priority is selected from the priorities specified for the
two functions.

Most Beneficial Scenarios

You are advised to enable air interface acceleration guarantee for network services to ensure smooth
performance for UEs performing specific services. To ensure the effect of air interface acceleration
guarantee for moving UEs, the source eNodeB needs to send the latest service acceleration information to
the target eNodeB in inter-eNodeB handover scenarios. Therefore, you are advised to enable this function
in contiguous coverage areas and configure X2 interfaces between eNodeBs.

• This function reduces the service setup delay when there are fewer than 100 UEs online. If there are
too many acceleration guarantee UEs, this function has significant negative impacts on network KPIs.
The L.Traffic.User.Avg counter measures the number of online UEs.

• This function increases service rates when the percentage of samples with the PDSCH PRB usage
higher than index 8 is over 10%.
Percentage of samples with the PDSCH PRB usage higher than index 8 = (
L.ChMeas.PRB.PDSCH.Util.Samp.Index8 + L.ChMeas.PRB.PDSCH.Util.Samp.Index9 )/Sum of
L.ChMeas.PRB.PDSCH.Util.Samp.Index0 to L.ChMeas.PRB.PDSCH.Util.Samp.Index9

For FDD, you are advised to enable the PDCCH boundary power control optimization function if the system
bandwidth is greater than 10 MHz and the equivalent CCE usage is less than 30%. If the conditions are not
met, this function cannot deliver the optimal gains after being enabled.

5.2.2.2 Impacts

Network Impacts

This function has the following impacts on network performance:

• Proactively sending scheduling indications to acceleration guarantee UEs increases the uplink PRB
usage, uplink interference, CCE usage, and decreases the uplink IBLER. More frequent uplink
scheduling leads to increases in the values of UE quantity counters related to uplink features, such as
UL CoMP.

• The effect of raising scheduling weights for acceleration guarantee UEs depends on where most of the
UEs are at the cell edge or near the cell center. At the cell edge, the cell throughput and user-
perceived throughput decrease, and the IBLER and PRB usage increase. Near the cell center, the cell
throughput and user-perceived throughput increase, and the IBLER and PRB usage decrease.

2024-05-07 43
eRAN FDD Feature Documentation

• Raising scheduling weights for acceleration guarantee UEs with large uplink or downlink packets
increases the scheduling delay of small packets. If the incremental amplitude of the transmission
delay is greater than that of the traffic volume, the cell throughput and user-perceived throughput
decrease.

• Raising scheduling weights for acceleration guarantee UEs affects CA UE quantity-related counters. If
most acceleration guarantee UEs are CA UEs, the values of these counters increase. If most
acceleration guarantee UEs are not CA UEs, the values of these counters decrease.

• If the DRX switch is turned off for acceleration guarantee UEs, the delay of acceleration guarantee
UEs decreases, but UEs consume more power and RRC signaling exchanges in the cell increase.

• A larger value of the AsParaGroup. AsNackCqiAdjValue parameter leads to a greater decrease in the
downlink CQI adjustment value for acceleration guarantee UEs and a greater decrease in the
downlink packet delay for such UEs. However, acceleration guarantee UEs use more PDSCH RBs and
PDCCH resources in this case. This parameter is invalid for VoLTE UEs identified as acceleration
guarantee UEs.

• If the AsParaGroup. AsSchPriFactor parameter is not set to 1 and the ENTER_DRX_SWITCH option of
the AsParaGroup. AccelerationServiceOptSw parameter is deselected, the values of the
L.Cdrx.Active.TtiNum and L.Cdrx.Sleep.TtiNum counters may increase or decrease. If the AsParaGroup.
AsNackCqiAdjValue parameter is not set to 0 at the same time, the values of the two counters
change more significantly.

• For FDD, PDCCH boundary power control optimization has the following network impacts:

• If the PDCCH CCE aggregation level for acceleration guarantee UEs reaches the highest value,
PDCCH power increases quickly and the service delay decreases.

• Higher PDCCH power leads to a higher equivalent CCE usage of a cell. Low-delay UEs have
higher priorities. As a result, the eNodeB may fail to allocate CCEs to lower-priority UEs, which
increases the service delay.
Equivalent CCE usage = ( L.ChMeas.CCE.ULUsed.Equivalent + L.ChMeas.CCE.DLUsed.Equivalent )/
L.ChMeas.CCE.Avail x 100%

• Higher PDCCH power increases the interference to neighboring cells. This leads to deterioration in
the downlink channel quality across the network and affects the downlink throughput.

• The maximum increase in PDCCH power depends on the bandwidth. If the bandwidth is small
and available power is limited, the PDCCH power cannot increase.

• Enabling independent configuration of the UE inactivity timer changes the RRC connection setup
duration of air interface acceleration UEs and the number of UEs in the cell.

• If the MLB_AND_MBOCS_PROHIBITION_SW option of the AsParaGroup. AccelerationServiceOptSw

parameter is selected and there are a large number of acceleration guarantee UEs, the transfer
efficiency of MLB and MBOCS may decrease.

• When the PERIODIC_MEAS_OPT_SWITCH option of the AsParaGroup. AccelerationServiceOptSw

parameter is selected, acceleration guarantee UEs are prohibited from performing periodic inter-

2024-05-07 44
eRAN FDD Feature Documentation

frequency or inter-RAT MR and MDT measurements. As a result, the number of MR and MDT
measurement samples on the live network decreases.

Function Impacts

RAT Function Name Function Switch Reference Description

FDD None None None None

5.2.3 Requirements

5.2.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LOFD-110221 Initial Acceleration LT1S000VEO00 Per Cell

5.2.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 Reference Description

FDD SC-based SC_SERVICE_IDENTITY_SW and Video This function depends on

service SC_SUPPORT_IPV6_SW options of the Experience SC-based identification of
identification ScPolicy. ScAlgoSwitch parameter Optimization acceleration guarantee
UEs.

Mutually Exclusive Functions

None

5.2.3.3 Hardware

Base Station Models

For FDD, the following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

A UMPT must be installed because this function is deployed on a main control board.

2024-05-07 45
eRAN FDD Feature Documentation

RF Modules

No requirements

5.2.3.4 Others
None

5.2.4 Operation and Maintenance

5.2.4.1 Data Configuration

5.2.4.1.1 Data Preparation
Table 5-3 describes the parameters used for function activation.
Table 5-3 Parameters used for activation
Parameter Parameter ID Setting Notes
Name

Accelerate CellAlgoSwitch. Set this parameter to ON.

Service AsAlgoSwitch
Algorithm
Switch

Accelerate AsParaGroup. Different acceleration guarantee parameter groups consist of

Service Para AsParaGroupID different acceleration guarantee parameters.
Group ID

Accelerate AsParaGroup. Set this parameter to its recommended value.

Service AsSchPriFactor
Schedule
Priority Factor

Accelerate AsParaGroup. Set this parameter to its recommended value.

Service Prealloc AsPreallocMinPeriod
Min Period

Accelerate AsParaGroup. Set this parameter to its recommended value.

Service Prealloc AsPreallocSize
Pkt Size

Accelerate AsParaGroup. Set this parameter to its recommended value.

Service Prealloc AsPreallocDuration
Duration

Accelerate AsParaGroup. If there is only one acceleration service parameter group and
Service NACK AsNackCqiAdjValue the group ID (specified by the ScAppParaCfg. AsParaGroupID
CQI Adj Value parameter) is not 255, set this parameter to its recommended
value. Otherwise, set this parameter to 0.

Acceleration AsParaGroup. Deselect the ENTER_DRX_SWITCH option if DRX is not

Service AccelerationServiceOptSw required for acceleration guarantee UEs.
Optimization
Switch

Acceleration AsParaGroup. For FDD, it is recommended that the

Service AccelerationServiceOptSw PDCCH_BOUNDARY_PC_OPT_SW option be selected when the

2024-05-07 46
eRAN FDD Feature Documentation

Parameter Parameter ID Setting Notes

Name

Optimization conditions for enabling PDCCH boundary power control

Switch optimization are met.

Acceleration AsParaGroup. If the MLB_AND_MBOCS_PROHIBITION_SW option is selected,

Service AccelerationServiceOptSw acceleration guarantee UEs cannot be transferred for MLB
Optimization and MBOCS. If this option is deselected, acceleration
Switch guarantee UEs can be transferred for MLB and MBOCS.

Acceleration AsParaGroup. It is recommended that the PERIODIC_MEAS_OPT_SWITCH

Service AccelerationServiceOptSw option be selected to prohibit acceleration guarantee UEs
Optimization from performing periodic inter-frequency or inter-RAT MR and
Switch MDT measurements. This prevents gap-assisted
measurements from affecting the delay and throughput of
acceleration guarantee UEs.

Acceleration AsParaGroup. Set this parameter to its recommended value.

Service UE AccServiceUeInactivityTmr
Inactivity Timer

5.2.4.1.2 Using MML Commands

Activation Command Examples

//Enabling air interface acceleration guarantee for network services

MOD CELLALGOSWITCH: LocalCellId=0, AsAlgoSwitch=ON;
//FDD: Adding a parameter group for air interface acceleration guarantee for network services
ADD ASPARAGROUP: AsParaGroupID=1, AsPreallocDuration=2000, AsPreallocMinPeriod=5, AsPreallocSize=80,
AsSchPriFactor=50, AsNackCqiAdjValue=10, AccelerationServiceOptSw=ENTER_DRX_SWITCH-
0&PDCCH_BOUNDARY_PC_OPT_SW-1&MLB_AND_MBOCS_PROHIBITION_SW-0&PERIODIC_MEAS_OPT_SWITCH-1,
AccServiceUeInactivityTmr=65535;

Deactivation Command Examples

//Disabling air interface acceleration guarantee for network services

MOD CELLALGOSWITCH: LocalCellId=0, AsAlgoSwitch=OFF;

5.2.4.1.3 Using the MAE-Deployment

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

5.2.4.2 Activation Verification

None

5.2.4.3 Network Monitoring

This function reduces the service setup delay and increases the network service download rate for
identified acceleration guarantee UEs accessing a specific DNS server or IP address.

The following methods are recommended to monitor performance:

2024-05-07 47
eRAN FDD Feature Documentation

• Perform DTs to observe the single-user page display delay and service rate on the UE side.

• Web page display delay: Capture PCAP packets on the UE side to measure the delay from the first
SYN packet to the first HTTP response packet during web page browsing before and after the
feature is enabled.

• Service rate: Calculate the rate gain based on the rates provided by the test tool.

• Observe network KPIs such as page display delay and page download rate on the operator's service
KPI platform.

5.3 Enhanced TCP Link Setup Acceleration

5.3.1 Principles
Enhanced TCP link setup acceleration has been introduced to reduce service setup delays and increase
rates for HTTP or HTTPS services.
This function is suitable only to HTTP and HTTPS services carried on bearers of QCIs 6 through 9. This
function is enabled if the parameters are set according to Table 5-4.
Table 5-4 Parameter settings for enhanced TCP link setup acceleration
Supported Protocol Setting of CellAlgoSwitch. ServiceDiffSwitch Setting of ENodeBAlgoSwitch. TpeSwitch

IPv4 and IPv6 Select the AsForTcpSw option. Select the TcpSupportIpv6Switch option.

IPv4 Select the AsForTcpSw option. Deselect the TcpSupportIpv6Switch option.

When this function is enabled, the eNodeB performs acceleration guarantee for UEs after a TCP link setup
request has been initiated. The process is shown in Figure 5-8.

2024-05-07 48
eRAN FDD Feature Documentation

Figure 5-8 Enhanced TCP link setup acceleration

The eNodeB performs acceleration guarantee for UEs based on the settings of the following parameters:

• The eNodeB configures acceleration relevant parameters based on the settings of the following
parameters:

• ScAppParaCfg. AppCfgTargetInd : If this parameter is set to AccelerateInd, TCP link setup

acceleration guarantee will be performed for the UE.

• ScAppParaCfg. MatchRule indicates the rule for matching a to-be-identified application (for
example, a video) with the domain name.

• ScAppParaCfg. AppIdentType indicates the application identification type.

• ScAppParaCfg. AsParaGroupID indicates the ID of a TCP link setup acceleration guarantee group.

• The eNodeB proactively sends uplink scheduling indications to UEs. It performs preallocation to
schedule uplink packets in a timely manner based on the settings of the following parameters:

• AsParaGroup. AsPreallocSize specifies the volume of data for each preallocation.

• AsParaGroup. AsPreallocMinPeriod specifies the preallocation interval.

• AsParaGroup. AsPreallocDuration specifies the duration of preallocation and scheduling priority

for acceleration guarantee UEs.

• The eNodeB uses higher uplink and downlink scheduling priorities to reduce the service setup delay
and increase uplink and downlink service rates based on the settings of the following parameters:

2024-05-07 49
eRAN FDD Feature Documentation

AsParaGroup. AsSchPriFactor : The scheduling priority equals the original scheduling priority
multiplied by the value of this parameter.

• For services with multiple TCP streams (such as web browsing services), each TCP link triggers enhanced TCP link
setup acceleration during link setup. When the acceleration windows of different TCP links overlap, timing for
acceleration is restarted when the last TCP link is set up.
• When enhanced TCP link setup acceleration, air interface acceleration guarantee for network services, and SC-
based video service rate adaption are enabled at the same time, the eNodeB uses the highest scheduling priority
adjustment rate specified for these functions.
• Acceleration guarantee performed by the eNodeB in Figure 5-8 includes the duration of adjusting scheduling
priorities and preallocation.

5.3.2 Network Analysis

5.3.2.1 Benefits

Gains

This function shortens setup delays and increases the download rate of HTTP or HTTPS services. When DRX
is also enabled, the service setup delay can be reduced by up to 5%, and the average page download rate
can be improved by up to 3% for web browsing services.
Gains from enhanced TCP link setup acceleration are affected by the following functions:

• Basic scheduling
Enhanced TCP link setup acceleration produces larger gains on networks with common or smart
preallocation disabled (specified by the CellPreallocGroup. PreallocationSwitch and
CellPreallocGroup. SmartPreallocationSwitch parameters, respectively).

• DRX
Enhanced TCP link setup acceleration reduces delays for UEs in DRX sleep state receiving downlink
packets during service setup. If DRX is disabled, the gains in delays are smaller.

• Air interface acceleration guarantee for network services

If both this function and enhanced TCP link setup acceleration are enabled, preallocation parameters
of this function preferentially take effect. Higher uplink and downlink scheduling priorities take effect.
Gains from this function do not affect those from enhanced TCP link setup acceleration. This is
because this function is applicable only to specific UEs.

• SC-based video service rate adaption

If both this function and enhanced TCP link setup acceleration are enabled, the higher downlink
scheduling priority takes effect, and gains from them are not accumulated.

• SPID-based uplink preallocation

Enhanced TCP link setup acceleration in combination with this function produces smaller gains in
delays.

2024-05-07 50
eRAN FDD Feature Documentation

Most Beneficial Scenarios

You are advised to enable air interface acceleration guarantee for network services to ensure smooth
performance for UEs performing specific services. To ensure the effect of air interface acceleration
guarantee for moving UEs, the source eNodeB needs to send the latest service acceleration information to
the target eNodeB in inter-eNodeB handover scenarios. Therefore, you are advised to enable this function
in contiguous coverage areas and configure X2 interfaces between eNodeBs.

• This function reduces the service setup delay when there are fewer than 100 UEs online. If there are
too many acceleration guarantee UEs, this function has significant negative impacts on network KPIs.
The L.Traffic.User.Avg counter measures the number of online UEs.

• This function increases service rates when the percentage of samples with the PDSCH PRB usage
higher than index 8 is over 10%.
Percentage of samples with the PDSCH PRB usage higher than index 8 = (
L.ChMeas.PRB.PDSCH.Util.Samp.Index8 + L.ChMeas.PRB.PDSCH.Util.Samp.Index9 )/Sum of
L.ChMeas.PRB.PDSCH.Util.Samp.Index0 through L.ChMeas.PRB.PDSCH.Util.Samp.Index9

5.3.2.2 Impacts

Network Impacts

This function shortens setup delays and increases rates of services based on the HTTP or HTTPS.

This function has the following impacts on network performance:

• Proactively sending scheduling indications to acceleration guarantee UEs increases the uplink PRB
usage, uplink interference, CCE usage, and decreases the uplink IBLER. More frequent uplink
scheduling leads to increases in the values of counters measuring the number of UEs enabled with
related uplink features, such as UL CoMP.

• Raising scheduling weights for acceleration guarantee UEs has the following effects:

• The cell throughput and user-perceived throughput decrease, and the IBLER and PRB usage
increase when most acceleration guarantee UEs are at the cell edge.

• The cell throughput and user-perceived throughput increase, and the IBLER and PRB usage
decrease when most acceleration guarantee UEs are near the cell center.

• Raising scheduling weights for acceleration guarantee UEs with large uplink or downlink packets
increases the scheduling delay of small packets. If the incremental amplitude of the transmission
delay is greater than that of the traffic volume, the cell throughput and user-perceived throughput
decrease.

• Raising scheduling weights for acceleration guarantee UEs affects statistics on CA UE quantity-related
counters:

• The values of these counters increase if most acceleration guarantee UEs are CA UEs.

• The values of these counters decrease if most acceleration guarantee UEs are not CA UEs.

2024-05-07 51
eRAN FDD Feature Documentation

Function Impacts

RAT Function Function Switch Reference Description

Name

FDD Video CONGEST_VIDEO_RES_CTRL_SWITCH Video If video resource control in

resource option of the CellAlgoSwitch. Experience congestion scenarios has
control in DlSchExtSwitch parameter Optimization taken effect for a UE
congestion running video services,
scenarios enhanced TCP link setup
acceleration does not take
effect for this UE.

5.3.3 Requirements

5.3.3.1 Licenses
None

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

None

Mutually Exclusive Functions

RAT Function Name Function Switch Reference Description

FDD None None None None

5.3.3.3 Hardware

Base Station Models

For FDD, the following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

No requirements

RF Modules

2024-05-07 52
eRAN FDD Feature Documentation

No requirements

5.3.3.4 Others
NSA UEs do not support this function.

5.3.4 Operation and Maintenance

5.3.4.1 Data Configuration

5.3.4.1.1 Data Preparation
Table 5-5 describes the parameters used for function activation.
Table 5-5 Parameters used for activation
Parameter Name Parameter ID Setting Notes

Service Differentiated CellAlgoSwitch. Select the AsForTcpSw option.

Switch ServiceDiffSwitch

TPE switch ENodeBAlgoSwitch. Select the TcpSupportIpv6Switch option to enable

TpeSwitch IPv6 service guarantee.

Application Identification ScAppParaCfg. Set this parameter to TCPPORT.

Type AppIdentType

Application Index ScAppParaCfg. AppDnsId Set this parameter to 100.

Accelerate Service Para ScAppParaCfg. Set this parameter to the same value as the
Group ID AsParaGroupID AsParaGroup. AsParaGroupID parameter.

Application Config Target ScAppParaCfg. Select the AccelerateInd option.

Indicator AppCfgTargetInd

Match Rule ScAppParaCfg. MatchRule Set this parameter to Query.

Accelerate Service Para AsParaGroup. Set this parameter based on the network plan.
Group ID AsParaGroupID

Accelerate Service Prealloc AsParaGroup. Set this parameter to its recommended value.
Duration AsPreallocDuration

Accelerate Service Prealloc AsParaGroup. Set this parameter to its recommended value.
Min Period AsPreallocMinPeriod

Accelerate Service Prealloc AsParaGroup. Set this parameter to its recommended value.
Pkt Size AsPreallocSize

Accelerate Service AsParaGroup. Set this parameter to its recommended value.

Schedule Priority Factor AsSchPriFactor

5.3.4.1.2 Using MML Commands

Enabling or disabling this function affects only UEs that newly access the network.

Activation Command Examples

//Configuring parameters for enhanced TCP link setup acceleration by running the ADD ASPARAGROUP and ADD
SCAPPPARACFG commands in sequence

2024-05-07 53
eRAN FDD Feature Documentation

ADD ASPARAGROUP: AsParaGroupID=10, AsPreallocDuration=400, AsPreallocMinPeriod=5, AsPreallocSize=80,

AsSchPriFactor=50;
ADD SCAPPPARACFG: AppDnsId=100, AppIdentType=TCPPORT, MatchRule=Query, AppCfgTargetInd=AccelerateInd-1,
AsParaGroupID=10;
//Enabling TCP link setup acceleration
MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=AsForTcpSw-1;
//Turning on the TCP service support IPv6 switch when support for the IPv6 protocol is required for this function
MOD ENODEBALGOSWITCH: TpeSwitch=TcpSupportIpv6Switch-1;

Optimization Command Examples

None

Deactivation Command Examples

//Disabling TCP link setup acceleration

MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=AsForTcpSw-0;

5.3.4.1.3 Using the MAE-Deployment

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

5.3.4.2 Activation Verification

None

5.3.4.3 Network Monitoring

This function reduces setup delay and increases rates of HTTP- or HTTPS-based services.

The following methods are recommended to monitor performance:

• Observe network KPIs such as the web page display delay and page download rate on the operator's
service KPI platform.

• Perform DTs to observe the single-user web page display delay and service rate on the UE side.

• Web page display delay: Capture PCAP packets on the UE side to measure the delay from the first
SYN packet to the first HTTP response packet during web page browsing before and after the
feature is enabled.

• Service rate: Calculate the rate gain based on the rates provided by the test tool.

• 6.1 Principles

• 6.2 Network Analysis

• 6.3 Requirements

• 6.4 Operation and Maintenance

2024-05-07 54
eRAN FDD Feature Documentation

6.1 Principles
Complex transmission networking causes out-of-order TCP packets. Severe out-of-order TCP packets
decrease the service throughput. To address this problem, the initiative TCP packet ordering function is
introduced. With initiative TCP packet ordering enabled, the eNodeB checks TCP packet sequences received
in the downlink and corrects the packets order if necessary before delivering them to the UE. This improves
TCP transmission performance that deteriorates due to TCP packet disorder.
This function is enabled when the parameters are set according to Table 6-1.
Table 6-1 Parameter configuration for initiative TCP packet ordering
Supported Setting of WtcpProxyAlgo. Setting of ENodeBAlgoSwitch.
Protocol TcpActiveOrderingTimer TpeSwitch

IPv4 and IPv6 Non-zero value Select the TcpSupportIpv6Switch

option.

IPv4 Non-zero value Deselect the TcpSupportIpv6Switch

option.

After this function is enabled, the eNodeB checks the Sequence number and Next sequence number fields
in the TCP header during downlink data transmission.

• When TCP data packets reach the eNodeB in the correct order, the eNodeB directly sends the packets
to the UE without buffering them.

• If TCP data packets reach the eNodeB in an incorrect order, the eNodeB buffers the packets and starts
a timer WtcpProxyAlgo. TcpActiveOrderingTimer .

• If the eNodeB receives the out-of-order TCP packets before the timer expires, the eNodeB
reorders the packets and sends them to the UE in the correct order, as shown in scenario 1 in
Figure 6-1.

• If the eNodeB does not receive the out-of-order TCP packets before the timer expires, the eNodeB
sends all the buffered TCP data packets to the UE, as shown in scenario 2 in Figure 6-1.

Figure 6-1 TCP data packet processing of the eNodeB

2024-05-07 55
eRAN FDD Feature Documentation

6.2 Network Analysis

6.2.1 Benefit Analysis

Benefit Baselines

If serious TCP packet disorder occurs on the transport network, this function helps increase the TCP service
download rate of UEs.

Benefit Requirements

If the TCP packet disorder rate is between 1% and 10% and the packet loss rate is lower than 0.1% on the
live network, this function is recommended to improve the service rate. Collect the TCP packet disorder
rate using a third-party TCP indicator measurement device provided by the EPC or transport network.
The amount of gain is subject to the packet disorder rate and scope, delay of out-of-order packets, packet
loss rate, and transmission RTT delay on the wired transmission side. More gains are delivered in the case
of higher packet disorder rate or longer transmission RTT delay; while a large packet disorder scope or
longer delay of out-of-order packets may cause gains to be diminished.

6.2.2 Impacts

Network Impacts

This function has the following impacts on network performance:

• The CPU load of the BBPs increases slightly.

• If TCP packet loss is more serious than packet disorder in a cell, this function causes the downlink
throughput to deteriorate.

• This function reduces out-of-order TCP packets received by UEs and repetitive TCP ACKs responded by
UEs. The reduction decreases the KPIs Cell Uplink Average Throughput, User Uplink Average
Throughput, and Uplink Traffic Volume.

• The average downlink PDCP packet delay ( L.Traffic.DL.PktDelay.Time divided by

L.Traffic.DL.PktDelay.Num ) increases because the eNodeB buffers disordered TCP packets.

Function Impacts

None

6.3 Requirements

6.3.1 Licenses
None

6.3.2 Software

2024-05-07 56
eRAN FDD Feature Documentation

Prerequisite Functions

None

Mutually Exclusive Functions

None

6.3.3 Hardware

Base Station Models

For FDD, the following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

The LBBPc does not support this function.

RF Modules

No requirements

6.3.4 Others
None

6.4 Operation and Maintenance

6.4.1 Data Configuration

6.4.1.1 Data Preparation

Table 6-2 describes the parameters used for function activation.
Table 6-2 Parameters used for activation
Parameter Name Parameter ID Setting Notes

TCP Active WtcpProxyAlgo. Set this parameter to its recommended value.

Ordering Timer TcpActiveOrderingTimer

TPE switch ENodeBAlgoSwitch. TpeSwitch Select the TcpSupportIpv6Switch option to enable

IPv6 service guarantee.

6.4.1.2 Using MML Commands

2024-05-07 57
eRAN FDD Feature Documentation

Activation Command Examples

//Enabling initiative TCP packet ordering

MOD WTCPPROXYALGO: LocalCellId=0, TcpActiveOrderingTimer=2;
//Turning on the TCP service support IPv6 switch when support for the IPv6 protocol is required for this function
MOD ENODEBALGOSWITCH: TpeSwitch=TcpSupportIpv6Switch-1;

Optimization Command Examples

None

Deactivation Command Examples

//Disabling initiative TCP packet ordering

MOD WTCPPROXYALGO: LocalCellId=0, TcpActiveOrderingTimer=0;

6.4.1.3 Using the MAE-Deployment

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

6.4.2 Activation Verification

Enabling or disabling this function affects only UEs that newly access the network.
Use a UE to download files through File Transfer Protocol (FTP) when the transport network meets the
conditions for enabling this function. Observe changes of the TCP packet disorder rate after function
enabling. If the TCP packet disorder rate drops, this function has taken effect.

6.4.3 Network Monitoring

If serious TCP packet disorder occurs on the transport network, this function helps increase the TCP service
download rate of UEs.

The following methods are recommended to monitor performance. After this function is enabled, the
downlink throughput increases.

• Perform a DT, and observe the downlink throughput on the UE during FTP-based download.

• Check the related KPIs such as the downlink throughput on the service KPI platform deployed by the
operator.

This feature contains the following functions.

• SC-based video service rate adaption

• DSCP-based video service rate adaption

• Video service load control

• Video resource control in congestion scenarios

• VOD optimization

2024-05-07 58
eRAN FDD Feature Documentation

• DSCP-based IPTV QoS guarantee in WTTx scenarios (trial)

• 7.1 SC-based Video Service Rate Adaption

• 7.2 DSCP-based Video Service Rate Adaption

• 7.3 Video Service Load Control

• 7.4 Video Resource Control in Congestion Scenarios

• 7.5 VOD Optimization

• 7.6 DSCP-based IPTV QoS Guarantee in WTTx Scenarios

7.1 SC-based Video Service Rate Adaption

7.1.1 Principles
This function has been introduced to reduce the video buffering time, guarantee the video service rate, and
reduce video freezes.

This function requires SC-based service identification to support the IPv4 and IPv6 protocols.

This function improves the UE scheduling priorities to guarantee rates of video services that are identified
based on SC, as shown in Figure 7-1. This function is controlled by the SC_VIDEO_RATE_ADAPT_SW option
of the CellAlgoSwitch. ScVideoOptSwitch parameter. For details about SC-based video service
identification, see 4 SC-based Service Identification.

Figure 7-1 Video service rate adaption

After this function is enabled, the eNodeB handling mechanism is as follows:

• If a UE's video service rate is lower than the value of the ScServiceQos. DlSgbr parameter, the eNodeB
raises the UE's scheduling priority to ensure the rate reaches the service guaranteed bit rate (SGBR)
when resources are sufficient. If the UE's video service rate after adaption exceeds the SGBR, the UE's
scheduling priority is decreased. This ensures that the UE's video service rate remains close to the
SGBR.

• If the video service rate of a UE is higher than the value of the ScServiceQos. DlSgbr parameter, the
eNodeB does not adjust the UE's scheduling priority.

2024-05-07 59
eRAN FDD Feature Documentation

• The SpidCfg. DlServiceGbrCoeff parameter can be used to adjust the target GBR for video service UEs
when they require differentiated rate guarantee.
Target GBR for video service UEs = SpidCfg. DlServiceGbrCoeff x ScServiceQos. DlSgbr

SC-based video service rate adaption and DSCP-based video service rate adaption are mutually exclusive,
and DSCP-based video service rate adaption has better performance. Therefore, DSCP-based video service
rate adaption is recommended when videos are not encrypted and video identification is supported on the
EPC, and SC-based video service rate adaption is recommended in other scenarios.

7.1.2 Network Analysis

7.1.2.1 Benefits

Gains

This function reduces the video buffering time, guarantees the video service rate, and reduces video
freezes.
There are no combined gains when both SC-based video service rate adaption and air interface
acceleration guarantee for network services under the initial acceleration feature are enabled together. The
highest downlink scheduling priority of these two functions is the one that is used.

Most Beneficial Scenarios

Use this function for cells meeting the following conditions:

• Video traffic accounts for no more than 40% of the traffic in the cell, and the video service rates for
some UEs do not reach the SGBR.
Proportion of video traffic = L.Exp.Video.Thrp.bits.DL.All / L.Thrp.bits.DL
Before measuring the L.Exp.Video.Thrp.bits.DL.All counter, enable SC-based video service identification
by referring to 4 SC-based Service Identification.

• The cell load meets the following conditions:

• The average single-UE throughput of a cell during busy hours ( User Downlink Average
Throughput ) is lower than 1.5 Mbit/s.

• The network load is high. For example, the PRB usage during busy hours ( Downlink Resource
Block Utilizing Rate ) is greater than 60%.

If the preceding conditions are not met, this function does not have any negative impact but cannot offer
the expected gains.

7.1.2.2 Impacts

Network Impacts

2024-05-07 60
eRAN FDD Feature Documentation

This function affects cell capacity. The change in the cell capacity depends on the radio environment of the
UEs performing video services and the proportion of video traffic in the cell. If the SGBR is set to a large
value, the video service rate increases significantly, resulting in a great change in cell capacity. At locations
where UEs are accessing video services, this function has the following impacts on cell capacity:

• If the radio signal quality is good, it increases cell capacity.

• If the radio signal quality is poor, it decreases cell capacity.

This function has the following impacts on service performance:

• Decreases the rates of other non-guaranteed bit rate (non-GBR) services and increases the average
delay of guaranteed bit rate (GBR) services while maintaining the GBR when the amount of downlink
resources required by various types of services in the cell is greater than the amount of available
downlink resources in the cell.

• Has no obvious impact on other types of services when the amount of downlink resources required by
various types of services in the cell is less than the amount of available downlink resources in the cell.

Function Impacts

None

7.1.3 Requirements

7.1.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LOFD-081203 Video Service Rate Adaption LT1S00VSRA00 Per Cell

7.1.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 Function Switch Reference Description

Name

FDD SC-based SC_SERVICE_IDENTITY_SW and Video Before selecting the

service SC_SUPPORT_IPV6_SW options Experience SC_SERVICE_IDENTITY_SW option,
identification of the ScPolicy. ScAlgoSwitch Optimization ensure that the
parameter BRDRESASSIGNMENT.
BRDASSIGNMENT parameter is set
to Mode1.

Mutually Exclusive Functions

2024-05-07 61
eRAN FDD Feature Documentation

RAT Function Name Function Switch Reference Description

FDD DSCP-based VideoRateAdaptSwitch option of the Video The two functions cannot be
video service CellAlgoSwitch. ServiceDiffSwitch Experience used at the same time
rate adaption parameter Optimization because they use different
methods of service
identification.

FDD DSCP-based VideoRateAdaptSwitch option of the Video The two functions cannot be
IPTV QoS CellAlgoSwitch. ServiceDiffSwitch Experience used at the same time
guarantee in parameter Optimization because they use different
WTTx scenarios methods of service
identification.

FDD Busy-hour DownLoadRateLimitSwitch option of Video The two functions cannot be

download rate the CellAlgoSwitch. Experience used at the same time
control ServiceDiffSwitch parameter Optimization because they use different
methods of service
identification.

7.1.3.3 Hardware

Base Station Models

For FDD, the following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

A UMPT must be installed because this function requires SC-based video service identification.

RF Modules

No requirements

7.1.3.4 Others
None

7.1.4 Operation and Maintenance

7.1.4.1 Data Configuration

7.1.4.1.1 Data Preparation
Table 7-1 and Table 7-2 describe the parameters used for function activation and optimization,
respectively.
Table 7-1 Parameters used for activation

2024-05-07 62
eRAN FDD Feature Documentation

Parameter Name Parameter ID Setting Notes

SC Algorithm ScPolicy. ScAlgoSwitch Select the SC_SERVICE_IDENTITY_SW option.

Switch Before selecting this option, ensure that
BRDRESASSIGNMENT. BRDASSIGNMENT is set to Mode1.

Video Opt Switch CellAlgoSwitch. Select the SC_VIDEO_RATE_ADAPT_SW option.

ScVideoOptSwitch

Sc Qos ID ScServiceQos. ScQosId Set this parameter based on the network plan.

Application ScServiceQos. You can run the DSP SCAPPINFO command to obtain the
Identification Type AppIdentType website identification modes supported by the eNodeB.

Application Dns ScServiceQos. AppDns This parameter must be set only if the ScServiceQos.
AppIdentType parameter is set to DNS.
You can run the DSP SCAPPINFO command to obtain the
application domain names supported by the eNodeB.

Application IPv4 ScServiceQos. AppIpv4 This parameter must be set only if the ScServiceQos.
AppIdentType parameter is set to IPV4.
You can run the DSP SCAPPINFO command to obtain the
website IP addresses supported by the eNodeB.

Application IPv6 ScServiceQos. AppIpv6 This parameter must be set only if the ScServiceQos.
AppIdentType parameter is set to IPV6.
You can run the DSP SCAPPINFO command to obtain the
website IP addresses supported by the eNodeB.

Table 7-2 Parameters used for optimization

Parameter Parameter ID Setting Notes
Name

Downlink ScServiceQos. This parameter specifies the SGBR for a video application that has not
Service Grant DlSgbr yet been optimized. It is recommended that the configured SGBR be
Bit Rate about 1.2 times the video bit rate. An excessively large value of the
configured SGBR leads to a waste of radio resources.
The video bit rate varies according to video types on the live network.
Table 7-3 is for reference only.

Downlink SpidCfg. This parameter specifies the coefficient corresponding to the downlink
Service GBR DlServiceGbrCoeff Service Guarantee Bit Rate (SGBR) for UEs with a specific SPID.
Coeff Target GBR for video service UEs = SpidCfg. DlServiceGbrCoeff x
ScServiceQos. DlSgbr

Table 7-3 Typical video bit rates

Video Average Video Bit Rate Minimum Video Bit Rate Maximum Video Bit Rate
Type (kbit/s) (kbit/s) (kbit/s)

360p 590 350 800

480p 1500 1000 2500

720p 2400 1000 4000

1080p 6000 4000 8000

2024-05-07 63
eRAN FDD Feature Documentation

7.1.4.1.2 Using MML Commands

Activation Command Examples

This function depends on SC-based video service identification and requires that the video application
information in the ScServiceQos MO be the same as that in the ScAppParaCfg MO.

//Enabling SC-based video service rate adaption

//Ensuring the consistency between the configuration of video services identified based on SC and that of video
applications when the identification is based on domain names
ADD SCAPPPARACFG: AppDnsId=0, AppIdentType=DNS, AppDns="*test*video.com*", MatchRule=Query,
AppCfgTargetInd=VideoIdentInd-1, AppName="Testvideo";
ADD SCSERVICEQOS: ScQosId=0, AppIdentType=DNS, AppDns="*test*video.com*", DlSgbr=1500;
//Ensuring the consistency between the configuration of video services identified based on SC and that of video
applications when the identification is based on IPv4 addresses
ADD SCAPPPARACFG: AppDnsId=1, AppIdentType=IPV4, AppIpv4="103.0.37.4", MatchRule=Query,
AppCfgTargetInd=VideoIdentInd-1, AppName="test video";
ADD SCSERVICEQOS: ScQosId=1, AppIdentType=IPV4, AppIpv4="103.0.37.4", DlSgbr=1500;
//Ensuring the consistency between the configuration of video services identified based on SC and that of video
applications when the identification is based on IPv6 addresses
ADD SCAPPPARACFG: AppDnsId=2, AppIdentType=IPV6, AppIpv6="2001:1111:2222:3333:0003:0002:5B1E:FC4F",
MatchRule=Query, AppCfgTargetInd=VideoIdentInd-1, AppName="test video";
ADD SCSERVICEQOS: ScQosId=2, AppIdentType=IPV6, AppIpv6="2001:1111:2222:3333:0003:0002:5B1E:FC4F", DlSgbr=1500;
//Turning on the video rate adaption switch
MOD CELLALGOSWITCH: LocalCellId=1, ScVideoOptSwitch=SC_VIDEO_RATE_ADAPT_SW-1;

Optimization Command Examples

Default values are used as an example.

//Configuring SC-based video service rate adaption

MOD SCSERVICEQOS: ScQosId=0, AppIdentType=DNS, AppDns="*---sn-*.googlevideo.com*", DlSgbr=1500;
//Doubling the GBR of UEs with the SPID of 1
ADD SPIDCFG: Spid=1, RatFreqPriorityInd=NOT_CFG, DlServiceGbrCoeff=20;

Deactivation Command Examples

//Disabling SC-based video service rate adaption

MOD CELLALGOSWITCH: LocalCellId=1, ScVideoOptSwitch=SC_VIDEO_RATE_ADAPT_SW-0;

7.1.4.1.3 Using the MAE-Deployment

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

7.1.4.2 Activation Verification

2024-05-07 64
eRAN FDD Feature Documentation

When rate adaption criteria are met (for example, in peak hours for a cell), deliver video services on the
predetermined website, and observe how the rate changes when SC-based video service rate adaption is
enabled. If the changes are significant, this function has taken effect.

7.1.4.3 Network Monitoring

This function reduces the video buffering time, guarantees the video service rate, and reduces video
freezes.

• The following methods are recommended for precise performance monitoring:

• Conduct DTs to observe gains offered by this function to a single UE.

Play a video on the UE, monitor playback performance, and record the length of time that passes
from when the video is launched to when the video starts playing, and the number of freezes
during playback. Screen recording and other video recording methods can be used to collect and
analyze statistics.

• Leverage capabilities of video service KPI evaluation on the EPC side or use third-party video
service KPI evaluation equipment.
Obtain KPIs of video services, such as the initial buffering delay of video streaming media and the
number of freezes during the playback of video streaming media in a cell.

• The following methods are recommended for rough performance monitoring:

• UE throughput
You are advised to monitor experience of a single UE to evaluate the increases in the UE
throughput.

• SC-based video service throughput in a cell

Before enabling this function, enable SC-based service identification, run the ADD SCSERVICEQOS
command, and collect the video service throughput one week before rate adaption. The collected
data is used to evaluate the gains produced by SC-based video service rate adaption.
After this function is enabled, observe the value of L.Exp.Video.Thrp.bits.DL.All /
L.Exp.Video.Thrp.Time.DL.All to evaluate the throughput increase of video services identified
based on SC in the cell.

7.2 DSCP-based Video Service Rate Adaption

7.2.1 Principles
This section describes DSCP-based video service rate adaption and DSCP service differentiation.
SC-based video service rate adaption and DSCP-based video service rate adaption are mutually exclusive,
and DSCP-based video service rate adaption has better performance. Therefore, DSCP-based video service
rate adaption is recommended when videos are not encrypted and video identification is supported on the
EPC, and SC-based video service rate adaption is recommended in other scenarios.

7.2.1.1 Video Service Rate Adaption

This function has been introduced to reduce the video buffering time, guarantee the video service rate, and
reduce video freezes.

2024-05-07 65
eRAN FDD Feature Documentation

This function controls the rates of video services identified based on DSCPs. It dynamically adjusts their
scheduling priorities to improve video service experience. This function is controlled by the
VideoRateAdaptSwitch option of the CellAlgoSwitch. ServiceDiffSwitch parameter. Rate adaption depends
on DSCP-based service differentiation, which is described in 7.2.1.2 Principles for DSCP-based Service
Differentiation.
The video service rate changes over time when this function is enabled.

• If a video service rate is less than the QosPolicy. DlSgbr parameter, the eNodeB raises the scheduling
priority for the related bearer and adopts a best-effort policy.

• If the video service rate after adjustment is greater than or equal to the value of the QosPolicy.
DlSgbr parameter, the eNodeB no longer raises the scheduling priority. This avoids consumption of
excessive bandwidth.

When the video service rate without adjustment exceeds the value of the QosPolicy. DlSgbr parameter, the
eNodeB does not lower the scheduling priority so that resources can be fully used.
It is recommended that phase-based acceleration be enabled for video services identified based on DSCPs.
To enable phase-based acceleration, set the IpServiceQos. QosPolicyTimeSwitch parameter to ON. The
eNodeB will provide initial acceleration during the first phase and then a normal rate guarantee in the
second phase, as shown in Figure 7-2.

Figure 7-2 Video service rate control

• Initial acceleration

The eNodeB performs initial acceleration based on the first-phase QoS policy during the initial stage
of a video stream. The following parameters are involved:

• IpServiceQos. FirQosPolicyId specifies the QoS policy.

• QosPolicy. DlSgbr specifies the target grant bit rate for the corresponding QoS policy, such as
SGBR 1 in Figure 7-2.

• IpServiceQos. FirQosPolicyTimeLength specifies the initial acceleration duration, as shown in

Figure 7-2.

2024-05-07 66
eRAN FDD Feature Documentation

• Normal-rate guarantee

After initial acceleration, the eNodeB uses the second-phase QoS policy for normal-rate guarantee.
The following parameters are involved:

• IpServiceQos. SecQosPolicyId specifies the QoS policy.

• QosPolicy. DlSgbr specifies the target grant bit rate for the corresponding QoS policy, such as
SGBR 2 in Figure 7-2.

7.2.1.2 Principles for DSCP-based Service Differentiation

7.2.1.2.1 Working Principle
Experience requirements differ by service types. Figure 7-3 shows the process of DSCP-based service
differentiation.

Figure 7-3 Process of DSCP-based service differentiation

Service identification and DSCP marking are implemented by a service awareness device. This device is
integrated into the core network or provided by a third party, and deployed by the operator. Different
DSCP values are marked to differentiate services. The eNodeB performs differentiated QoS management
based on the obtained DSCP values.
The service awareness device marks the DSCP values in either of the following ways:

• Inner-loop DSCP: After identifying the service, the service awareness device marks the DSCP value in
the IP header of the TCP packet. Figure 7-4 shows the position of such kind of DSCP in the protocol
stack.

• Outer-loop DSCP: After identifying the service, the service awareness device marks the DSCP value in
the IP header of the UDP packet complying with GTP-U. Figure 7-5 shows the position of such kind of
DSCP in the protocol stack.

2024-05-07 67
eRAN FDD Feature Documentation

Figure 7-4 Inner-loop DSCP in the protocol stack

Figure 7-5 Outer-loop DSCP in the protocol stack

Whether the DSCP value obtained by the eNodeB is an inner-loop or outer-loop one is determined by the
OUTER_LOOP_DSCP_QOS_MGMT_SW option of the CellAlgoExtSwitch. DlSchEnhSwitch parameter. If this
option is selected, the eNodeB performs QoS management based on the outer-loop DSCP. If this option is
deselected, the eNodeB performs QoS management based on the inner-loop DSCP.
When the outer-loop DSCP is adopted, whether the DSCP value is transparently transmitted to the eNodeB
PDCP layer is controlled by the QciPara. OLDscpTransparentTransSw parameter. When this parameter is
set to ON, the DSCP value is transparently transmitted to the eNodeB PDCP layer. When this parameter is
set to OFF, the eNodeB PDCP layer obtains the DSCP value based on the default QCI mapping. For details,
see Transmission Resource Management .

2024-05-07 68
eRAN FDD Feature Documentation

DSCPs and QoS policies are configured on the eNodeB based on the DSCP marking rules of the service
awareness device and on operator policies. These policies lay a foundation for differentiated processing on
different DSCP service queues. For details, see 7.2.1.2.2 DSCP and QoS Policy Configurations.
This function implements differentiated scheduling for video, download, and other services. For details, see
7.2.1.2.3 Differentiated Scheduling.
7.2.1.2.2 DSCP and QoS Policy Configurations
QoS information is configured for DSCPs on the eNodeB, and is used for DSCP-based service
differentiation.
QoS information includes the following:

• Mapping between DSCPs and QoS policies (MO IpServiceQos). For details, see Table 7-4.

• QoS policy (MO QosPolicy), which defines the priority queue for a certain type of service (PriQueueId)
and service rate guarantees (DlSgbr and DlSmbr). For details, see Table 7-5.

Table 7-4 Mapping between DSCPs and QoS policies (MO IpServiceQos)
DS Service QoS Policy TimeFirst QoS First QoS Policy Second Video Rate and Download
CP Type Switch ( Policy Duration ( QoS Policy Rate Control Switch
( Descripti QosPolicyTimeS Identity ( FirQosPolicyTime Identity ( (VIDEO_AND_DWNLD_RATE
Dsc on ( witch ) FirQosPoli Length ) SecQosPoli _CTRL_SW Option of the
p ) Descript cyId ) cyId ) ApplicationRange
ion ) Parameter)

15 Downlo OFF 2 Not required Not Selected

ad required
services

40 Video ON 0 12 1 Selected
services

20 Other OFF 3 Not required Not Selected

services required
(Operat
or-
defined;
such as
web
browsin
g and
gaming)

Table 7-5 QoS policy configuration table (MO QosPolicy)

QoS Policy Identity Traffic Type ( Priority Queue Downlink Service Downlink Service
( QosPolicyId ) TrafficType ) Identity ( Grant Bit Rate ( Maximum Bit Rate (
PriQueueId ) DlSgbr ) Unit: kbit/s DlSmbr ) Unit: kbit/s

0 VIDEO QUEUE 6 1280 Not required

1 VIDEO QUEUE 6 640 Not required

2 DOWNLOAD QUEUE 0 Not required 3500

3 OTHER QUEUE 3 Not required Not required

2024-05-07 69
eRAN FDD Feature Documentation

• The IpServiceQos. QosPolicyTimeSwitch parameter takes effect only for video services. When this parameter is
set to ON, a two-phase rate guarantee is implemented.
• If the QosPolicy. TrafficType parameter is set to DOWNLOAD or OTHER, and the IpServiceQos.
QosPolicyTimeSwitch parameter is set to OFF, the IpServiceQos. FirQosPolicyId parameter is valid and the
IpServiceQos. FirQosPolicyTimeLength and IpServiceQos. SecQosPolicyId parameters are invalid.
• The eNodeB cannot map the DSCPs in received service packets onto priority queues in any of the following
situations:

- The DSCPs are not configured for services on the eNodeB.

- The DSCPs are 0 in the service packets.

- The DSCP configuration on the eNodeB is different from the DSCP configuration on the service awareness
device.

If the mapping fails, the eNodeB stores the packets into priority queue 0 by default.

7.2.1.2.3 Differentiated Scheduling

After receiving DSCPs, the eNodeB performs differentiated scheduling at the PDCP and MAC layers
separately and in sequence for different services. This function applies only to non-GBR services and is
controlled by the CellAlgoSwitch. ServiceDiffSwitch parameter.

• PDCP-layer differentiated scheduling is as follows: The entering queue is configured based on DSCP
and QoS policies. Each bearer involves eight queues, for which weights can be set by specifying the
values of the ServiceDiffSetting. QueueWeight0 to ServiceDiffSetting. QueueWeight7 parameters to
implement differentiated scheduling in a bearer. Figure 7-6 uses the three queues of User 1 (queue 1
to queue 3) as an example.

• Differentiated scheduling at the MAC layer: The QciPara. DlschPriorityFactor parameter specifies the
scheduling priority factors of services with different QCIs to implement differentiated scheduling
among different bearers. For the specific configuration of this parameter, see QoS Management .
Figure 7-6 illustrates an example with three users where User 1 uses a bearer with a QCI of 8, User 2
uses a bearer with a QCI of 8, and User 3 uses a bearer with a QCI of 9.

2024-05-07 70
eRAN FDD Feature Documentation

Figure 7-6 Example of differentiated scheduling

If different bearers are used to serve gold-, silver-, and bronze-level subscribers, gold-level subscribers have
the highest priority for the same service. However, this does not mean that gold-level subscribers have the
highest priority for all services.
In CA scenarios, if the PCC and SCC do not share the BBP, differentiated scheduling takes effect only on the
PCC.

7.2.2 Network Analysis

7.2.2.1 Benefits

Gains

This function reduces the video buffering time, guarantees the video service rate, and reduces video
freezes.

Most Beneficial Scenarios

Use this function for cells meeting the following conditions:

• Video traffic accounts for no more than 40% of the traffic in the cell, and the video service rates for
some UEs do not reach the SGBR.
Proportion of video traffic = L.Thrp.bits.DL.Pri.6 / L.Thrp.bits.DL
The preceding counters are measured only after this function is enabled. For details about how to
observe these counters, see the configuration guide in 7.2.4.3 Network Monitoring.

• The cell load meets the following conditions:

2024-05-07 71
eRAN FDD Feature Documentation

• The average single-UE throughput of a cell during busy hours ( User Downlink Average
Throughput ) is lower than 1.5 Mbit/s.

• The network load is high. For example, the PRB usage during busy hours ( Downlink Resource
Block Utilizing Rate ) is greater than 60%.

If the preceding conditions are not met, this function does not have any negative impact but cannot offer
the expected gains.
When DSCP-based video service rate adaption is enabled and the proportion of video services to be
guaranteed is high (for example, over 20%), it is recommended that service identification be enabled.
Delay-sensitive services such as web services can be identified and assigned higher priorities.

7.2.2.2 Impacts

Network Impacts

This function affects cell capacity. The change in the cell capacity depends on the radio environment of the
UEs performing video services and the proportion of video traffic in the cell. If the SGBR is set to a large
value, the video service rate increases significantly, resulting in a great change in cell capacity. At locations
where UEs are accessing video services, this function has the following impacts on cell capacity:

• If the radio signal quality is good, it increases cell capacity.

• If the radio signal quality is poor, it decreases cell capacity.

This function has the following impacts on service performance:

• Decreases the rates of other non-GBR services and increases the average delay of GBR services while
maintaining the GBR when the amount of downlink resources required by various types of services in
the cell is greater than the amount of available downlink resources in the cell.

• Has no obvious impact on other types of services when the amount of downlink resources required by
various types of services in the cell is less than the amount of available downlink resources in the cell.

• Possibly causes changes to the service drop rate of video service UEs in weak coverage scenarios.

Function Impacts

None

7.2.3 Requirements

7.2.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LOFD-081203 Video Service Rate Adaption LT1S00VSRA00 Per Cell

7.2.3.2 Software

2024-05-07 72
eRAN FDD Feature Documentation

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

None

Mutually Exclusive Functions

RAT Function Function Switch Reference Description

Name

FDD SC-based SC_VIDEO_RATE_ADAPT_SW option of Video The two functions cannot be

video service the CellAlgoSwitch. Experience used at the same time
rate adaption ScVideoOptSwitch parameter Optimization because they use different
methods of service
identification.

7.2.3.3 Hardware

Base Station Models

No requirements

Boards

No requirements

RF Modules

No requirements

7.2.3.4 Other Requirements

DSCP-based video service rate adaption requires a service awareness device integrated into the EPC or
provided by a third party.
NSA UEs do not support DSCP-based video service rate adaption.

7.2.4 Operation and Maintenance

7.2.4.1 Data Configuration

7.2.4.1.1 Data Preparation
Table 7-6 and Table 7-7 describe the parameters used for function activation and optimization,
respectively.
Table 7-6 Parameters used for activation

2024-05-07 73
eRAN FDD Feature Documentation

Parameter Parameter ID Setting Notes

Name

Service CellAlgoSwitch. Select the VideoRateAdaptSwitch option.

Differentiated ServiceDiffSwitch
Switch

QoS Policy QosPolicy. QosPolicyId Each service has a unique QoS policy ID.
Identity

Traffic Type QosPolicy. TrafficType Set this parameter to VIDEO.

Priority Queue QosPolicy. PriQueueId It is recommended that this parameter be set to QUEUE6,
Identity QUEUE5, or QUEUE7.

Differentiated IpServiceQos. Dscp Set this parameter to the same value as the DSCP policy
Services Code configured on the service awareness device.
Point For example, if the service awareness device identifies a
video service and sets the DSCP to 40, the DSCP value 40
must be configured for video services on the eNodeB.

Traffic IpServiceQos. Description Set this parameter to Video services.

Description

QoS Policy Time IpServiceQos. Set this parameter to ON.

Switch QosPolicyTimeSwitch

First QoS Policy IpServiceQos. FirQosPolicyId Set this parameter to the QoS policy ID specific to the
Identity service to be guaranteed.

Second QoS IpServiceQos. SecQosPolicyId Set this parameter to the QoS policy ID specific to the
Policy Identity service to be guaranteed.

Application IpServiceQos. Select the VIDEO_AND_DWNLD_RATE_CTRL_SW option so

Range ApplicationRange that the QoS policy is applicable to DSCP-based video
service rate adaptation and busy-hour download rate
control.

DL Scheduling CellAlgoExtSwitch. If the service awareness device marks the identification

Enhancement DlSchEnhSwitch result in the inner-loop DSCP, the
Switch OUTER_LOOP_DSCP_QOS_MGMT_SW option must be
deselected. If the identification result is marked in the
outer-loop DSCP, this option must be selected.
If the identification result is marked in the outer-loop DSCP,
the OUTER_LOOP_DSCP_QOS_MGMT_SW option must be
selected.
Set this parameter to the same value as the DSCP policy
configured on the service awareness device.

Outer Loop QciPara. Set this parameter to ON when

DSCP OLDscpTransparentTransSw OUTER_LOOP_DSCP_QOS_MGMT_SW is selected.
Transparent
Trans Sw

Table 7-7 Parameters used for optimization

2024-05-07 74
eRAN FDD Feature Documentation

Parameter Parameter ID Setting Notes

Name

Downlink QosPolicy. DlSgbr To conserve radio resources, do not set this parameter to
Service Grant a large value for video services. It is recommended that
Bit Rate this parameter be:
Set to a value twice the video bit rate for initial
acceleration.
Set to a value 1.1 to 1.2 times that of the video bit rate
for normal-rate guarantee.
Obtain the video bit rate from an OTT website or service
awareness device. If video services with different
resolutions are performed on a network, use the video bit
rate of services with the highest proportion as the
reference for SGBR setting.
The video bit rates described in Table 7-8 are for
reference only.

First QoS IpServiceQos. Set this parameter to its recommended value.

Policy Time FirQosPolicyTimeLength
Length

Queue0 ServiceDiffSetting. Set this parameter to its recommended value.

Weight to QueueWeight0 to
Queue7 ServiceDiffSetting.
Weight QueueWeight7

Table 7-8 Typical video bit rates

Video Average Video Bit Rate Minimum Video Bit Rate Maximum Video Bit Rate
Type (kbit/s) (kbit/s) (kbit/s)

360p 590 350 800

480p 1500 1000 2500

720p 2400 1000 4000

1080p 6000 4000 8000

7.2.4.1.2 Using MML Commands

Activation Command Examples

//Enabling DSCP-based video service rate adaption

MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=VideoRateAdaptSwitch-1;
//Enabling QoS management based on outer-loop DSCP
MOD CELLALGOEXTSWITCH: LocalCellId=0, DlSchEnhSwitch=OUTER_LOOP_DSCP_QOS_MGMT_SW-1;
//Enabling outer-loop DSCP transparent transmission
MOD QCIPARA: Qci=7, OLDscpTransparentTransSw=ON;
//Configuring two QoS policies for video services with one QoS policy used in initial acceleration and the other used in
normal-rate guarantee (Queue 6 is used as an example.)
ADD QOSPOLICY: QosPolicyId=0, TrafficType=VIDEO, PriQueueId=QUEUE6, DlSgbr=4800;

2024-05-07 75
eRAN FDD Feature Documentation

ADD QOSPOLICY: QosPolicyId=1, TrafficType=VIDEO, PriQueueId=QUEUE6, DlSgbr=1200;

//Setting the mapping between the DSCP values of video services and QoS policies
ADD IPSERVICEQOS: Dscp=40, Description="Video Service", QosPolicyTimeSwitch=ON, FirQosPolicyId=0,
FirQosPolicyTimeLength=8, SecQosPolicyId=1, ApplicationRange=PREALLOCATION_SW-
0&VIDEO_AND_DWNLD_RATE_CTRL_SW-1;

Optimization Command Examples

Default values are used as an example.

//Configuring the SGBR

MOD QOSPOLICY: QosPolicyId=0, TrafficType=VIDEO, PriQueueId=QUEUE6, DlSgbr=4800;
MOD QOSPOLICY: QosPolicyId=1, TrafficType=VIDEO, PriQueueId=QUEUE6, DlSgbr=1200;
//Configuring the guarantee duration
MOD IPSERVICEQOS: Dscp=40, Description="Video Service", QosPolicyTimeSwitch=ON, FirQosPolicyId=0,
FirQosPolicyTimeLength=8, SecQosPolicyId=1, ApplicationRange=PREALLOCATION_SW-
0&VIDEO_AND_DWNLD_RATE_CTRL_SW-1;
//Configuring service queues with different weights
MOD SERVICEDIFFSETTING: QueueWeight0=10, QueueWeight1=5, QueueWeight2=5, QueueWeight3=10,
QueueWeight4=10, QueueWeight5=20, QueueWeight6=20, QueueWeight7=20;

Deactivation Command Examples

//Disabling QoS management based on outer-loop DSCP

MOD CELLALGOEXTSWITCH: LocalCellId=0, DlSchEnhSwitch=OUTER_LOOP_DSCP_QOS_MGMT_SW-0;
//Disabling outer-loop DSCP transparent transmission
MOD QCIPARA: Qci=7, OLDscpTransparentTransSw=OFF;
//Disabling DSCP-based video service rate adaption
MOD CELLALGOSWITCH: LocalCellId=0,ServiceDiffSwitch=VideoRateAdaptSwitch-0;

7.2.4.1.3 Using the MAE-Deployment

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

7.2.4.2 Activation Verification

This function has taken effect if the value of either counter in the following table is not 0.
Counter ID Counter Name

1526736778 to 1526736780 L.Thrp.bits.DL.Pri.5 to L.Thrp.bits.DL.Pri.7

1526736770 to 1526736772 L.Thrp.Time.DL.Pri.5 to L.Thrp.Time.DL.Pri.7

7.2.4.3 Network Monitoring

This function reduces the video buffering time, guarantees the video service rate, and reduces video
freezes.

2024-05-07 76
eRAN FDD Feature Documentation

• The following methods are recommended for precise performance monitoring:

• Perform DTs to learn the feature gains for a single UE. Play a video on the UE, monitor the
playback, and record the initial buffering time and the number of freezes during playback. Screen
recording and other video recording methods can be used to collect and analyze statistics.

• Enable KPI evaluation on the EPC or use a third-party KPI evaluation mechanism to obtain video-
related KPIs, such as the video stream's initial buffering delay and the number of freezes during
the video playback in the cell.

• The following methods are recommended for rough performance monitoring:

It is recommended that the service experience of a single UE be used to evaluate the increase in the
UE throughput.
When QosPolicy. PriQueueId is set to QUEUE6, the L.Thrp.bits.DL.Pri.6 and L.Thrp.Time.DL.Pri.6
counters can be used for evaluation. After this function is enabled, the preceding counters are
measured. The measurement results are used to roughly evaluate the video throughput in a cell.
If you use eNodeB counters to evaluate the gains of this function, that is, service differentiation is not
performed on different services. This allows you to obtain the video throughput without rate adaption.
The configuration commands are as follows:

• Set the traffic type for video services to OTHER so that rate adaption will not be performed.
Meanwhile, specify that video service packets are scheduled through the specified queue (queue
6 is used as an example) and that the weight of this queue is the same as that of other queues.
This is used to collect the statistics only about the video throughput.

//Setting the traffic type for video services to OTHER so that rate adaption will not be performed. Specifying
that video service packets are scheduled through the specified queue (queue 6 is used as an example) and that
the weight of this queue is the same as that of other queues. This is used to collect the statistics only about the
video throughput.
//Setting a QoS policy for video services
ADD QOSPOLICY: QosPolicyId=127, TrafficType=OTHER, PriQueueId=QUEUE6;
//Setting the mapping between the DSCP values of video services and QoS policies
MOD IPSERVICEQOS:Dscp=40, Description="Video Service", QosPolicyTimeSwitch=OFF, FirQosPolicyId=127,
ApplicationRange=PREALLOCATION_SW-0&VIDEO_AND_DWNLD_RATE_CTRL_SW-1;
//Configuring weights for service queues
MOD SERVICEDIFFSETTING: QueueWeight0=5, QueueWeight1=5, QueueWeight2=5, QueueWeight3=5,
QueueWeight4=5, QueueWeight5=5, QueueWeight6=5, QueueWeight7=5;

• //Restoring the video service configurations to those required by the live network

//Setting the mapping between the DSCP values of video services and QoS policies
ADD IPSERVICEQOS: Dscp=40, Description="Video Service", QosPolicyTimeSwitch=ON, FirQosPolicyId=0,
FirQosPolicyTimeLength=8, SecQosPolicyId=1, ApplicationRange=PREALLOCATION_SW-
0&VIDEO_AND_DWNLD_RATE_CTRL_SW-1;
//Configuring weights for service queues
MOD SERVICEDIFFSETTING: QueueWeight0=10, QueueWeight1=5, QueueWeight2=5, QueueWeight3=10,
QueueWeight4=10, QueueWeight5=20, QueueWeight6=20, QueueWeight7=20;

2024-05-07 77
eRAN FDD Feature Documentation

//Removing the QoS policy for collecting statistics about the video service throughput
RMV QOSPOLICY: QosPolicyId=127;

7.3 Video Service Load Control

7.3.1 Principles
This function has been introduced to balance the distribution of video services among frequencies. A
balanced distribution prevents cell congestion during video service bursts and increases the video service
throughput throughout the network.
This function controls the cell load by handing over UEs performing video services whose rates are
adjusted based on DSCPs or SC and meeting specific conditions to inter-frequency cells.

This function is controlled by the VideoSrvLoadCtrlSw option of the CellAlgoSwitch.

EnhancedMlbAlgoSwitch parameter. Figure 7-7 shows the process of this function.

Figure 7-7 Process of video service load control

The process described in Figure 7-7 involves the following concepts:

• Video service load

The video service load is the proportion of the bandwidth used by UEs performing video services in the
cell to the air interface capability. To learn how to calculate the air interface capability, see Intra-RAT
Mobility Load Balancing .

• Threshold for high video load. This threshold is specified by the CellMLB. VideoLoadHighThd
parameter.

• Threshold conditions for neighboring cells. The following conditions must be met:

• Video service load of the neighboring cell < (CellMLB. VideoLoadHighThd + CellMLB.
VideoLoadLowThd )/2

• PRB usage of the neighboring cell < CellMLB. VideoDlPrbThd

• Available bandwidth > Bandwidth of UEs performing video services

For video services whose rates are adjusted based on DSCPs, the bandwidth of a UE performing
video services is specified by the QosPolicy. DlSgbr parameter.

2024-05-07 78
eRAN FDD Feature Documentation

For video services whose rates are adjusted based on SC, the bandwidth of a UE performing video
services is specified by the ScServiceQos. DlSgbr parameter.

• The eNodeB selects video service UEs for inter-frequency handovers.

Figure 7-7 shows the conditions for triggering handovers for this function. Except for the triggering
conditions, the handover procedure is the same as that of load transfer in the user number-based load
balancing feature. This function allows for only measurement-based and A4-triggered handovers. For
details, see Intra-RAT Mobility Load Balancing .

7.3.2 Network Analysis

7.3.2.1 Benefits

Gains

This function balances the distribution of video services among different frequencies. Balanced distribution
prevents cell congestion during video service bursts and increases the video service throughput throughout
the network. A higher degree of video load imbalance among inter-frequency cells indicates more gains
offered by video service load control.
This function produces smaller gains if it is enabled with the following features:

• User-number-based load balancing

• Intra-RAT mobility load balancing

Most Beneficial Scenarios

You are advised to enable this function when the following conditions are met:

• More than 30% of the network traffic is video traffic.

Proportion of video traffic = L.Thrp.bits.DL.SC.Video / L.Thrp.bits.DL

• The cell PRB usage ( Downlink Resource Block Utilizing Rate ) exceeds 60%.

• The video load ratio difference between inter-frequency cells exceeds 20%.
Video load ratio = L.Thrp.bits.DL.SC.Video / L.Thrp.bits.DL

If the preceding conditions are not met, this function does not have any negative impact but cannot offer
the expected gains.

7.3.2.2 Impacts

Network Impacts

This function increases inter-frequency handovers, but does not affect the handover success rate.

Function Impacts

2024-05-07 79
eRAN FDD Feature Documentation

None

7.3.3 Requirements

7.3.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LOFD-081203 Video Service Rate Adaption LT1S00VSRA00 Per Cell

7.3.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 Reference Description

FDD SC-based service SC_SERVICE_IDENTITY_SW and Video This function is

identification SC_SUPPORT_IPV6_SW options of the Experience required by load
ScPolicy. ScAlgoSwitch parameter Optimization control of video services
identified based on SC.

FDD SC-based video SC_VIDEO_RATE_ADAPT_SW option of Video This function is

service rate the CellAlgoSwitch. ScVideoOptSwitch Experience required by load
adaption parameter Optimization control of video services
identified based on SC.

FDD DSCP-based VideoRateAdaptSwitch option of the Video This function is

video service rate CellAlgoSwitch. ServiceDiffSwitch Experience required by load
adaption parameter Optimization control of video services
identified based on
DSCPs.

Mutually Exclusive Functions

None

7.3.3.3 Hardware

Base Station Models

For FDD, the following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

2024-05-07 80
eRAN FDD Feature Documentation

No requirements

RF Modules

No requirements

Cells

This function is not recommended in cells with low bandwidths (less than or equal to 5 MHz) because UEs
performing video services occupy high bandwidths.

7.3.3.4 Others
DSCP-based video service rate adaption requires a service awareness device integrated into the EPC or
provided by a third party.

7.3.4 Operation and Maintenance

7.3.4.1 Data Configuration

7.3.4.1.1 Data Preparation
Table 7-9 and Table 7-10 describe the parameters used for function activation and optimization,
respectively.
Table 7-9 Parameters used for activation
Parameter Name Parameter ID Option Setting Notes

Enhanced MLB Algorithm CellAlgoSwitch. VideoSrvLoadCtrlSw Select this

Switch EnhancedMlbAlgoSwitch option.

Table 7-10 Parameters used for optimization

Parameter Name Parameter ID Setting Notes

Video Load High Threshold CellMLB. Set this parameter to its recommended
VideoLoadHighThd value.

Video Load Low Threshold CellMLB. VideoLoadLowThd Set this parameter to its recommended
value.

Video MLB DL PRB Ratio CellMLB. VideoDlPrbThd Set this parameter to its recommended
Threshold value.

7.3.4.1.2 Using MML Commands

Activation Command Examples

//Enabling video service load control in the serving and target cells
//For the serving cell
MOD CELLALGOSWITCH: LocalCellId=0, EnhancedMlbAlgoSwitch=VideoSrvLoadCtrlSw-1;
//For the target cell

2024-05-07 81
eRAN FDD Feature Documentation

MOD CELLALGOSWITCH: LocalCellId=1, EnhancedMlbAlgoSwitch=VideoSrvLoadCtrlSw-1;

Optimization Command Examples

Recommended values are used as an example.

//Configuring thresholds related to video service load control

MOD CELLMLB: LocalCellId=0, VideoLoadHighThd=70, VideoLoadLowThd=50, VideoDlPrbThd=70;
MOD CELLMLB: LocalCellId=1, VideoLoadHighThd=70, VideoLoadLowThd=50, VideoDlPrbThd=70;

Deactivation Command Examples

//Disabling video service load control

MOD CELLALGOSWITCH: LocalCellId=0, EnhancedMlbAlgoSwitch= VideoSrvLoadCtrlSw-0;

7.3.4.1.3 Using the MAE-Deployment

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

7.3.4.2 Activation Verification

This function has taken effect if the value of any counter in the following table is not 0.
Counter ID Counter Name

1526741925 L.HHO.InterFreq.VideoLoad.PrepAttOut

1526741927 L.HHO.InterFreq.VideoLoad.ExecAttOut

1526741929 L.HHO.InterFreq.VideoLoad.ExecSuccOut

7.3.4.3 Network Monitoring

This function prevents cell congestion during video service bursts between inter-frequency cells and
increases the video service throughput throughout the network.

• The following methods are recommended for precise performance monitoring:

• Perform DTs to learn the feature gains for a single UE. Play a video on the UE, monitor the
playback, and record the length of time that passes from when the video is launched to when the
video starts playing, and the number of freezes during playback. Screen recording and other video
recording methods can be used to collect and analyze statistics.

• Enable KPI evaluation on the EPC or use a third-party KPI evaluation device to measure video-
related KPIs, such as the initial buffering delay of the video stream and the number of freezes
during the video playback in the cell.

• The following methods are recommended for rough performance monitoring:

Obtain the following counters to evaluate the gains from this function:

2024-05-07 82
eRAN FDD Feature Documentation

• Throughput of video services identified based on DSCPs in a cell (priority 6 is used as an

example) = L.Thrp.bits.DL.Pri.6 / L.Thrp.Time.DL.Pri.6

• Throughput of video services identified based on SC in a cell = L.Thrp.bits.DL.SC.Video /

L.Thrp.Time.DL.SC.Video

Before enabling this function for video services identified based on the SC, enable SC-based service
identification, run the ADD SCSERVICEQOS command, and collect the video service throughput one
week before rate adaption. The collected data is used to evaluate the gains produced by SC-based
video service rate adaption.

7.4 Video Resource Control in Congestion Scenarios

7.4.1 Principles
This function controls the scheduling priorities of UEs performing video services and consuming a large
volume of air interface resources when air interface resources are insufficient. This improves the service
experience of other UEs in the cell.
This function only lowers the scheduling priorities for UEs performing video services and identified based
on SC in congestion scenarios. For details about SC-based video service identification, see 4 SC-based
Service Identification.

This function requires SC-based service identification to support the IPv4 and IPv6 protocols.

This function is controlled by the CONGEST_VIDEO_RES_CTRL_SWITCH option of the CellAlgoSwitch.

DlSchExtSwitch parameter. In CA scenarios, if this function needs to be enabled for both the PCell and
SCell, select this option for both the PCell and SCell. Figure 7-8 shows the detailed process after this
function is enabled.

Figure 7-8 Process for limiting the data rate for video service UEs in congestion scenarios

2024-05-07 83
eRAN FDD Feature Documentation

If the following functions have been implemented for a UE running video services, the eNodeB does not
lower the video rates of the UE in congestion scenarios:

• SC-based video service rate adaption

• DSCP-based video service rate adaption

• VOD optimization

• DSCP-based IPTV QoS guarantee in WTTx scenarios

• Air interface acceleration guarantee for network services

The process described in Figure 7-8 is as follows:

• Whether air interface resources are insufficient

• If both of the following conditions are met, the eNodeB considers the air interface resources to be
insufficient:
Downlink PRB usage in a cell ≥ CellDlschAlgo. PrbEnableThldVideoResCtrl
Number of synchronized UEs in a cell ≥ CellDlschAlgo. UserEnableThldVideoResCtrl

• If either of the following conditions is met, the eNodeB considers the air interface resources to be
no longer insufficient:
Downlink PRB usage in a cell ≤ CellDlschAlgo. PrbEnableThldVideoResCtrl – 20%
Number of synchronized UEs in a cell ≤ CellDlschAlgo. UserEnableThldVideoResCtrl x 0.65

• Select UEs running video services and lower the scheduling priority.

• In non-CA scenarios
The eNodeB lowers the scheduling priority of UEs with the video rate greater than or equal to the
value of the CellDlschAlgo. CongestMaxVideoRate parameter. The video service rate decreases
compared with that before this feature is enabled. The video rate depends on the PRB usage and
UE spectral efficiency. After this function is enabled in congestion scenarios, the video rate may
not be less than this threshold.

• In CA scenarios
If the PCell meets the congestion condition, the scheduling priority of UEs running video services
is lowered, and the scheduling priority of the SCell is also lowered to the same level. In this case,
the rate of these UEs depends on the PRB usage and UE-specific spectral efficiency in the
PCell/SCell.

7.4.2 Network Analysis

7.4.2.1 Benefits
The congestion described in this section occurs when the following conditions are met:

• The downlink PRB usage ( Downlink Resource Block Utilizing Rate ) is higher than 80%.

• The number of RRC_CONNECTED UEs ( L.Traffic.User.Avg ) is greater than 200.

2024-05-07 84
eRAN FDD Feature Documentation

Gains

When the network is congested, the rate of UEs running video services that consume too many air
interface resources is reduced to improve the service experience of other UEs.

Most Beneficial Scenarios

• In non-CA scenarios (a single UE running video services in a cell) where the network is congested and
the experience of UEs running video services can be compromised to improve user experience of other
services, it is recommended that this function be enabled. The higher the proportion of video traffic
that can be compromised in a cell, the better user experience of other services. It is recommended
that the proportion of video traffic that can be compromised be greater than 20%.

• In CA scenarios: If the PCell/SCell is congested, the gains are obvious. If the PCell/SCell is not
congested, the rate of UEs running video services may not decrease, and user experience of other
services may not be improved significantly.

7.4.2.2 Impacts

Network Impact

To ensure the experience of other services, this function controls the video service rates when the network
is congested. The change in the cell capacity depends on the radio environment of UEs performing video
services and on the proportion of the traffic used by video services in the cell.

• If the signal quality is good in the area where video service UEs are located, cell capacity decreases.

• If the signal quality is poor in the area where video service UEs are located, cell capacity may increase.

Function Impacts

RAT Function Function Switch Reference Description

Name

FDD Enhanced TCP AsForTcpSw option of the Video If video resource control in congestion
link setup CellAlgoSwitch. Experience scenarios has taken effect for a UE
acceleration ServiceDiffSwitch parameter Optimization running video services, enhanced TCP
link setup acceleration does not take
effect for this UE.

FDD Air interface WtcpProxyAlgo. Video If video resource control in congestion

scheduling WtcpDlRttTimer Experience scenarios has taken effect for a UE
acceleration Optimization running video services, air interface
for WTCP scheduling acceleration for WTCP does
not take effect for this UE.

FDD Video TTI TtiBundlingForVideoSwitch of Video If video resource control in congestion

bundling the CellAlgoSwitch. Experience scenarios has taken effect for UEs
(FDD) UlSchSwitch parameter Optimization running video services and the rate of
UEs running video services in weak

2024-05-07 85
eRAN FDD Feature Documentation

RAT Function Function Switch Reference Description

Name

coverage areas exceeds the value of the

CellDlschAlgo. CongestMaxVideoRate
parameter, video TTI bundling does not
produce any gains.

FDD Inter-eNodeB UlCompForVideoSwitch Video If video resource control in congestion

UL CoMP for option of the CellAlgoSwitch. Experience scenarios has taken effect for UEs
video services UplinkCompSwitch Optimization running video services and the rate of
(FDD) parameter UEs running video services in weak
coverage areas exceeds the value of the
CellDlschAlgo. CongestMaxVideoRate
parameter, inter-eNodeB UL CoMP for
video services (FDD) does not produce
any gains.

FDD Busy-hour DownLoadRateLimitSwitch Video If video resource control in congestion

download option of the CellAlgoSwitch. Experience scenarios has taken effect for UEs
rate control ServiceDiffSwitch parameter Optimization running video services, the rate of such
UEs may further decrease.

FDD Turbo start CellAlgoSwitch. RohcSwitch Video If video resource control in congestion
video and PdcpRohcPara. Profiles Experience scenarios has taken effect for UEs
(set to Profile0x0006) Optimization running video services and the rate of
UEs running video services exceeds the
value of the CellDlschAlgo.
CongestMaxVideoRate parameter,
turbo start video does not produce any
gains.

FDD DACQ CellAlgoSwitch. DacqSwitch Rate Control If video resource control in congestion
Based on scenarios has taken effect for UEs
User Types running video services, the rate of such
UEs may further decrease.

FDD Downlink GBR None Scheduling If video resource control in congestion

and non-GBR scenarios has taken effect for UEs
service running video services and the value of
priority the QciPara. DlMinGbr parameter for
calculation UEs running video services exceeds the
value of the CellDlschAlgo.
CongestMaxVideoRate parameter, the
scheduling priority of UEs running video
services is not lowered.

FDD Target Rate BEST_EFFORT_GBR_SW Rate Control If video resource control in congestion
Guarantee option of the CellAlgoSwitch. Based on scenarios and target rate guarantee
Based on User DlSchExtSwitch parameter User Types based on user types have taken effect
Types on the same UE at the same time, the
final UE rate is close to the control rate
of video resource control in congestion
scenarios.

7.4.3 Requirements

2024-05-07 86
eRAN FDD Feature Documentation

7.4.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LOFD-081203 Video Service Rate Adaption LT1S00VSRA00 Per Cell

7.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 Reference Description

FDD SC-based service SC_SERVICE_IDENTITY_SW and Video Experience None

identification SC_SUPPORT_IPV6_SW options of the ScPolicy. Optimization
ScAlgoSwitch parameter

Mutually Exclusive Functions

None

7.4.3.3 Hardware

Base Station Models

For FDD, the following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

This function depends on the SC-based video identification function. For details, see 4.3.3 Hardware.
FDD: The LBBPc does not support this function.

RF Modules

No requirements

7.4.3.4 Other Requirements

None

2024-05-07 87
eRAN FDD Feature Documentation

7.4.4 Operation and Maintenance

7.4.4.1 Data Configuration

7.4.4.1.1 Data Preparation
Table 7-11 and Table 7-12 describe the parameters used for function activation and optimization,
respectively.
Table 7-11 Parameters used for activation
Parameter Name Parameter ID Option Setting Notes

DL Scheduling Extension CellAlgoSwitch. CONGEST_VIDEO_RES_CTRL_SWITCH Select this

Switch DlSchExtSwitch option.

Table 7-12 Parameters used for optimization

Parameter Name Parameter ID Setting Notes

Max Rate of Video UEs During CellDlschAlgo. CongestMaxVideoRate Set this parameter to its
Congestion recommended value.

Cell PRB Usage Upper Thld for CellDlschAlgo. Set this parameter to its
Video Res Ctrl PrbEnableThldVideoResCtrl recommended value.

Cell UE Num Upper Thld for CellDlschAlgo. Set this parameter to its
Video Res Ctrl UserEnableThldVideoResCtrl recommended value.

7.4.4.1.2 Using MML Commands

Activation Command Examples

//Enabling video resource control in congestion scenarios

MOD CELLALGOSWITCH: LocalCellId=0, DlSchExtSwitch=CONGEST_VIDEO_RES_CTRL_SWITCH-1;

Optimization Command Examples

Default values are used as an example.

MOD CELLDLSCHALGO: LocalCellId=0, CongestMaxVideoRate=350, PrbEnableThldVideoResCtrl=80,

UserEnableThldVideoResCtrl=200;

Deactivation Command Examples

//Disabling video resource control in congestion scenarios

MOD CELLALGOSWITCH: LocalCellId=0, DlSchExtSwitch=CONGEST_VIDEO_RES_CTRL_SWITCH-0;

7.4.4.1.3 Using the MAE-Deployment

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

7.4.4.2 Activation Verification

2024-05-07 88
eRAN FDD Feature Documentation

• In non-CA scenarios: Enable this function with default parameter settings. If the current cell meets
congestion conditions, observe the video service rate. If the rate decreases after this function is
enabled, this function has taken effect. If the cell does not meet congestion conditions, the rate of UEs
running video services may not decrease.

• In CA scenarios: If both the PCell and SCell meet congestion conditions, observe the video rate. If the
video rate decreases after this function is enabled, this function has taken effect. If neither the PCell
nor the SCell meets congestion conditions, the rate of UEs running video services may not decrease.

In congestion scenarios, the downlink PRB usage reaches over 80%, and there are more than 200 UEs in
RRC connected mode.

7.4.4.3 Network Monitoring

When the network is congested, this function reduces the rate of UEs running video services that consume
too many air interface resources to improve the service experience of other UEs.

• The following methods are recommended for precise performance monitoring:

• Perform DTs to learn the feature gains for a single UE. Play a video on the UE, monitor the
playback, and record the length of time that passes from when the video is launched to when the
video starts playing, and the number of freezes during playback. Screen recording and other video
recording methods can be used to collect and analyze statistics.

• Enable KPI evaluation on the EPC or use a third-party KPI evaluation device to measure video-
related KPIs, such as the initial buffering delay of the video stream and the number of freezes
during the video playback in the cell.

• The following methods are recommended for rough performance monitoring:

After this function is enabled, the following counter is used to observe the decrease in video
throughput.
Video service throughput in a cell = ( L.Exp.Video.Thrp.bits.DL.All – L.Exp.Video.Thrp.bits.DL.LastTTI )/
L.Exp.Video.Thrp.Time.DL.RmvLastTTI

7.5 VOD Optimization

Trial functions are functions 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 functions
can still be used for testing purposes or commercial network trials. Anyone who desires to use the trial
functions shall contact Huawei and enter into a memorandum of understanding (MoU) with Huawei prior
to an official application of such trial functions. Trial functions are not for sale in the current version but
customers may try them for free.
Customers acknowledge and undertake that trial functions 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 functions but also the possible impact they may exert on the network. In addition,
customers acknowledge and undertake that since trial functions are free, Huawei is not liable for any trial
function malfunctions or any losses incurred by using the trial functions. Huawei does not promise that
problems with trial functions will be resolved in the current version. Huawei reserves the rights to convert

2024-05-07 89
eRAN FDD Feature Documentation

trial functions into commercial functions in later R/C versions. If trial functions are converted into
commercial functions in a later version, customers shall pay a licensing fee to obtain the relevant licenses
prior to using the said commercial functions. If a customer fails to purchase such a license, the trial
function(s) will be invalidated automatically when the product is upgraded.

7.5.1 Principles
If Video On Demand (VOD) optimization based on the capabilities of the UE and eNodeB is enabled, the
eNodeB optimizes scheduling for VOD identified by the UE based on the video status reported by the UE
and bit rates of video services. This reduces video freezes and improves video service experience. VOD
optimization is a trial function and supports only the IPv4 protocol.

This function is controlled by the SpecUeIdentifySwitch option of the UeCooperationPara.

SpecUserCooperationSwitch parameter and the VOD_SERVICE_OPT_SW option of the CellAlgoSwitch.
ScVideoOptSwitch parameter. It includes the following processes:

• Capability negotiation for VOD optimization

• VOD optimization

7.5.1.1 Capability Negotiation for VOD Optimization

Both the UE and eNodeB must support VOD optimization and follow the process illustrated in Figure 7-9
to perform capability negotiation. If capability negotiation is successful, VOD optimization takes effect only
after a VOD service is set up.

Figure 7-9 Capability negotiation for VOD optimization

7.5.1.2 VOD Optimization

When a UE initiates a VOD service after successful VOD optimization capability negotiation between the
UE and eNodeB, the following process is performed to optimize the VOD service:

• The UE sends an HPS Video Measurement Report message to report the video status and bit rate.

2024-05-07 90
eRAN FDD Feature Documentation

• The eNodeB optimizes scheduling based on the video status and source bit rate reported by the UE.

• During initial video buffering, the eNodeB ensures that the video service rate equals
"CellDlschAlgo. SteadyTargetRateRatio x 1.66 x Source bit rate of the video".

• During stable video playback, the eNodeB ensures that the video service rate equals
"CellDlschAlgo. SteadyTargetRateRatio x Source bit rate of the video".

To reduce impacts on other users on the network, this function does not take effect for cell-edge VOD
service users (the filtered CQI value is less than 8) if the PRB usage of the cell is greater than 50%.

7.5.2 Network Analysis

7.5.2.1 Benefits
Use this function for cells meeting the following conditions:

• Service traffic
No more than 40% of the traffic is video traffic and the rates of some video service UEs are lower
than the source bit rate of the video.
Proportion of video traffic = L.Thrp.bits.DL.SC.Video / L.Thrp.bits.DL

• The cell load meets the following conditions:

• The average single-UE throughput of a cell during busy hours ( User Downlink Average
Throughput ) is lower than 1.5 Mbit/s.

• The network load is high. For example, the PRB usage during busy hours ( Downlink Resource
Block Utilizing Rate ) is greater than 60%.

If this function and any of the following functions are enabled together, there are no combined gains:

• Air interface acceleration guarantee for network services

• SC-based video service rate adaption

• DSCP-based video service rate adaption

7.5.2.2 Impacts

Network Impacts

This function improves the scheduling weighting value of VOD services to ensure the UE rate, but the
experience of services of lower priorities deteriorates.

The change in the cell capacity depends on the radio environment of the UEs performing video services
and on how much of the traffic in the cell is video traffic.

• If the radio signal quality is good at locations where UEs perform video services, cell capacity
increases. When more of the cell traffic is video, the cell capacity increase is larger.

• If the radio signal quality is poor at locations where UEs perform video services, cell capacity
decreases. When more of the cell traffic is video, the cell capacity decrease is larger.

2024-05-07 91
eRAN FDD Feature Documentation

Function Impacts

None

7.5.3 Requirements

7.5.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LOFD-081203 Video Service Rate Adaption LT1S00VSRA00 Per Cell

7.5.3.2 Software

Prerequisite Functions

None

Mutually Exclusive Functions

None

7.5.3.3 Hardware

Base Station Models

For FDD, the following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

The LBBPc does not support this function.

No requirements

RF Modules

No requirements

7.5.3.4 Others
There are UEs supporting VOD optimization on the network.

7.5.4 Operation and Maintenance

7.5.4.1 Data Configuration

7.5.4.1.1 Data Preparation

2024-05-07 92
eRAN FDD Feature Documentation

Table 7-13 describes the parameters used for function activation.

Table 7-13 Parameters used for activation
Parameter Name Parameter ID Option Setting Notes

Specified User UeCooperationPara. SpecUeIdentifySwitch Select this option.

Cooperation Switch SpecUserCooperationSwitch

Video Opt Switch CellAlgoSwitch. ScVideoOptSwitch VOD_SERVICE_OPT_SW Select this option.

Steady Phase CellDlschAlgo. None Set this parameter to its

Target Rate Ratio SteadyTargetRateRatio recommended value.

7.5.4.1.2 Using MML Commands

Activation Command Examples

//Enabling VOD optimization

MOD UECOOPERATIONPARA:LocalCellId=1,SpecUserCooperationSwitch=SpecUeIdentifySwitch-1;
MOD CELLALGOSWITCH: LocalCellId=1, ScVideoOptSwitch= VOD_SERVICE_OPT_SW-1;
MOD CELLDLSCHALGO: LocalCellId=1, SteadyTargetRateRatio=12;

Optimization Command Examples

None

Deactivation Command Examples

//Disabling VOD optimization

MOD CELLALGOSWITCH: LocalCellId=1, ScVideoOptSwitch= VOD_SERVICE_OPT_SW-0;

7.5.4.1.3 Using the MAE-Deployment

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

7.5.4.2 Activation Verification

Trace Uu interface signaling. This function has taken effect if the HPS RRC Connection Reconfiguration
message delivered by the eNodeB carries capability indication related to VOD optimization that requires
device-pipe synergy.

7.5.4.3 Network Monitoring

Evaluate the UE throughput increase based on the experience of a single UE.
Evaluation based on eNodeB counters:

1. Before enabling this function, select the SC_SERVICE_IDENTITY_SW option of the ScPolicy.
ScAlgoSwitch parameter to obtain the throughput of video services identified based on SC in the
cell. The throughput is used as a baseline for evaluating throughput gains of video services.

2024-05-07 93
eRAN FDD Feature Documentation

Throughput of video services identified based on SC in a cell = L.Thrp.bits.DL.SC.Video /

L.Thrp.Time.DL.SC.Video

2. Compare the throughputs of video services identified based on SC in a cell before and after this
function is enabled to evaluate the throughput gains of such services.

7.6 DSCP-based IPTV QoS Guarantee in WTTx Scenarios

Trial functions are functions 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 functions
can still be used for testing purposes or commercial network trials. Anyone who desires to use the trial
functions shall contact Huawei and enter into a memorandum of understanding (MoU) with Huawei prior
to an official application of such trial functions. Trial functions are not for sale in the current version but
customers may try them for free.
Customers acknowledge and undertake that trial functions 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 functions but also the possible impact they may exert on the network. In addition,
customers acknowledge and undertake that since trial functions are free, Huawei is not liable for any trial
function malfunctions or any losses incurred by using the trial functions. Huawei does not promise that
problems with trial functions will be resolved in the current version. Huawei reserves the rights to convert
trial functions into commercial functions in later R/C versions. If trial functions are converted into
commercial functions in a later version, customers shall pay a licensing fee to obtain the relevant licenses
prior to using the said commercial functions. If a customer fails to purchase such a license, the trial
function(s) will be invalidated automatically when the product is upgraded.

7.6.1 Principles
This function is used for IPTV transmission on LTE wireless to the x (WTTx) networks. The eNodeB
identifies IPTV video data streams based on their DSCPs and guarantees QoS for IPTV services. This
function is for trial use only.
This function is controlled by the VideoRateAdaptSwitch option of the CellAlgoSwitch. ServiceDiffSwitch
parameter. Figure 7-10 illustrates the IPTV QoS guarantee process.

2024-05-07 94
eRAN FDD Feature Documentation

Figure 7-10 IPTV QoS guarantee process

Table 7-14 describes the functions of each network element (NE).

Table 7-14 Involved NEs and their functions
NE Description

Customer-premises A CPE connects to the user equipment through a wired or Wi-Fi connection on
equipment (CPE) one side and to the eNodeB on the other side through LTE air interface signals.

eNodeB The eNodeB schedules data. In this function, the eNodeB optimizes the
scheduling of IPTV data streams.

RGW The RGW gathers internet and IPTV data streams and sets DSCP values specific
to IPTV data streams.

Serving gateway (S-GW) and These are user-plane function entities in the EPC.
PDN gateway (P-GW)

The process is as follows:

1. The remote gateway (RGW) gathers Internet and IPTV data streams and sets DSCP values specific to
IPTV data streams.

2. The eNodeB selects IPTV UEs for preferential scheduling.

Value of CellWttxParaCfg. Guarantee Scope
IptvGuaranteeUserCount

0 The eNodeB does not start the admission control mechanism, and
accelerates scheduling for all IPTV UEs identified based on DSCP values.

Non-zero value The eNodeB starts the admission control mechanism and preferentially
schedules some IPTV UEs. The maximum number of IPTV UEs that can be
preferentially scheduled is specified by the IptvGuaranteeUserCount
parameter.

The eNodeB controls the number of preferentially scheduled IPTV UEs as follows when starting the
admission control mechanism:

2024-05-07 95
eRAN FDD Feature Documentation

• The eNodeB measures the number of IPTV UEs that are preferentially scheduled. If the number
of such UEs has reached the preset threshold, UEs that newly access the network will not be
preferentially scheduled.

• If IPTV UEs that are preferentially scheduled pause or stop video programs (STBs are in standby
mode, turned off, or paused, that is, there are no IPTV data streams), the eNodeB will not
preferentially schedule other online IPTV UEs that are not preferentially scheduled. The eNodeB
selects only IPTV UEs that continue watching video programs after pausing or stopping the
programs for preferential scheduling.

• In single-UE multi-bearer scenarios, if multiple bearers contain IPTV data streams, the eNodeB
treats these bearers as multiple UEs.

The bootscreen display delay of STBs is incremented by 1% to 2% after the eNodeB starts admission
control.

3. The eNodeB identifies the DSCP values and then preferentially schedules IPTV data packets. Rate
adaption depends on DSCP-based service differentiation, which is described in 7.2.1.2 Principles for
DSCP-based Service Differentiation. The rate adaption process is as follows:

• If a video service rate is less than the value of QosPolicy. DlSgbr , the eNodeB raises the
scheduling priority for the related bearer and adopts a best-effort policy.

• If the video service rate after adjustment is greater than or equal to the value of QosPolicy.
DlSgbr , the eNodeB no longer raises the scheduling priority. This avoids consumption of
excessive bandwidth.

When the video service rate without adjustment exceeds the value of QosPolicy. DlSgbr , the eNodeB does
not lower the scheduling priority so that resources can be fully used.

Services are identified on the eNodeB for this function in the same way as that for DSCP-based video
service rate adaption and busy-hour download rate control. Therefore, if these functions are used at the
same time, the IpServiceQos. Dscp parameter must be set to different values for different video services to
avoid interference between functions.

• To adapt to operators' business models, you are advised to disable DSCP-based video service rate adaption when
IPTV services are provided so that a higher scheduling priority can be used for video services.
• In multi-carrier scenarios, it is recommended that mobility load balancing (MLB) be used to distribute IPTV UEs
evenly among different carriers. This avoids concentration of IPTV UEs on a single carrier and wastes of resources
on other carriers.

7.6.2 Network Analysis

7.6.2.1 Benefit Analysis

You are advised to enable this function to improve IPTV playback experience if RGWs are deployed on
WTTx networks and the RGWs are capable of setting DSCP values specific to IPTV data streams.

7.6.2.2 Impacts

2024-05-07 96
eRAN FDD Feature Documentation

Network Impacts

FDD: None

Function Impacts

None

7.6.3 Requirements

7.6.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LOFD-081203 Video Service Rate Adaption LT1S00VSRA00 Per Cell

7.6.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 Reference Description

FDD DSCP-based video VideoRateAdaptSwitch option of the Video Experience None

service rate adaption CellAlgoSwitch. ServiceDiffSwitch parameter Optimization

Mutually Exclusive Functions

RAT Function Function Switch Reference Description

Name

FDD SC-based SC_VIDEO_RATE_ADAPT_SW option of Video The two functions cannot be

video service the CellAlgoSwitch. Experience used at the same time
rate adaption ScVideoOptSwitch parameter Optimization because they use different
methods of service
identification.

7.6.3.3 Hardware

Base Station Models

For FDD, the following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

2024-05-07 97
eRAN FDD Feature Documentation

Boards

No requirements

RF Modules

No requirements

7.6.3.4 Others
This function is deployed in WTTx scenarios. It requires CPEs that support IPTV over WTTx.
This function also requires RGWs to set DSCP values specific to IPTV video data streams. It involves no
identification of services, which must be performed by RGWs.

7.6.4 Operation and Maintenance

7.6.4.1 Data Configuration

7.6.4.1.1 Data Preparation
This function depends on DSCP-based video service rate adaption. This section describes only the
parameter settings that are different from DSCP-based video service rate adaption.

Table 7-15 and Table 7-16 describe the parameters used for function activation and optimization,
respectively.
Table 7-15 Parameters used for activation
Parameter Name Parameter ID Setting Notes

Service CellAlgoSwitch. Select the VideoRateAdaptSwitch option.

Differentiated ServiceDiffSwitch
Switch

QoS Policy QosPolicy. QosPolicyId This parameter identifies the QoS policy for an IPTV service. It
Identity must be unique for each service.

Traffic Type QosPolicy. TrafficType Set this parameter to VIDEO.

Priority Queue QosPolicy. PriQueueId Set this parameter to QUEUE5, QUEUE6, or QUEUE7.
Identity

Differentiated IpServiceQos. Dscp This parameter must be set to the same value as the DSCP set
Services Code by the RGW. For example, if the DSCP is set to 18 on the RGW,
Point then this parameter must be set to 18.

Traffic IpServiceQos. Set this parameter to IPTV.

Description Description

QoS Policy Time IpServiceQos. Set this parameter to OFF.

Switch QosPolicyTimeSwitch

First QoS Policy IpServiceQos. Set this parameter to the QoS policy ID specific to the service to
Identity FirQosPolicyId be guaranteed.

2024-05-07 98
eRAN FDD Feature Documentation

Parameter Name Parameter ID Setting Notes

Application IpServiceQos. Select the VIDEO_AND_DWNLD_RATE_CTRL_SW option so that

Range ApplicationRange the QoS policy is applicable to DSCP-based video service rate
adaptation and busy-hour download rate control.

Table 7-16 Parameters used for optimization

Parameter Parameter ID Setting Notes
Name

Downlink QosPolicy. DlSgbr Set this parameter based on the operator's IPTV service
Service Grant guarantee policy. You are advised to set this parameter to
Bit Rate 10000, which means 10 Mbit/s.

Queue0 ServiceDiffSetting. Scheduling weight of queue 0: Queue 0 includes Internet

Weight to QueueWeight0 to data streams to be scheduled. Values ranging from 1 to 5
Queue7 ServiceDiffSetting. are recommended.
Weight QueueWeight7 Scheduling weight of queue 5: Values ranging from 80 to
95 are recommended.
NOTE:

The setting of the QosPolicy. PriQueueId parameter

determines which parameter in the range of
ServiceDiffSetting. QueueWeight5 to ServiceDiffSetting.
QueueWeight7 must be configured. QUEUE5 is used as an
example in this document. That is, it is assumed that queue
5 contains IPTV data streams.

IPTV CellWttxParaCfg. If the cell capacity is insufficient but there are too many
Guarantee IptvGuaranteeUserCount UEs running video services in the cell, set this parameter to
User Count a non-zero value.

7.6.4.1.2 Using MML Commands

Activation Command Examples

//Enabling DSCP-based video service rate adaption

MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=VideoRateAdaptSwitch-1;
//Setting the QoS policy for IPTV services (queue 5 is used as an example)
ADD QOSPOLICY: QosPolicyId=3, TrafficType=VIDEO, PriQueueId=QUEUE5, DlSgbr=10000;
//Configuring service queues with different weights
MOD SERVICEDIFFSETTING: QueueWeight0=1, QueueWeight1=0, QueueWeight2=0, QueueWeight3=0, QueueWeight4=0,
QueueWeight5=90, QueueWeight6=0, QueueWeight7=0;
//Setting the mapping between the DSCP values of video services and QoS policies
ADD IPSERVICEQOS:Dscp=18, Description="IPTV", QosPolicyTimeSwitch=OFF, FirQosPolicyId=3,
ApplicationRange=PREALLOCATION_SW-0&VIDEO_AND_DWNLD_RATE_CTRL_SW-1;

Optimization Command Examples

Default values are used as an example.

2024-05-07 99
eRAN FDD Feature Documentation

//Configuring the SGBR

MOD QOSPOLICY: QosPolicyId=3, TrafficType=VIDEO, PriQueueId=QUEUE5,DlSgbr=10000;
//Configuring service queues with different weights
MOD SERVICEDIFFSETTING: QueueWeight0=1, QueueWeight1=0, QueueWeight2=0, QueueWeight3=0, QueueWeight4=0,
QueueWeight5=90, QueueWeight6=0, QueueWeight7=0;
//Setting the maximum number of IPTV UEs for preferential scheduling
MOD CELLWTTXPARACFG: LocalCellId=0, IptvGuaranteeUserCount=3;

Deactivation Command Examples

//Disabling DSCP-based video service rate adaption

MOD CELLALGOSWITCH: LocalCellId=0, ServiceDiffSwitch=VideoRateAdaptSwitch-0;

7.6.4.1.3 Using the MAE-Deployment

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

7.6.4.2 Activation Verification

Observe the counters L.Traffic.User.IPTV.Avg and L.Traffic.User.IPTV.Max . If the value of any counter is not
0, the function has taken effect.

7.6.4.3 Network Monitoring

Monitor the single UE experience to evaluate the improvement in IPTV service experience.
If QosPolicy. PriQueueId is set to QUEUE5, the result of L.Thrp.bits.DL.Pri.5 divided by L.Thrp.Time.DL.Pri.5
is used for evaluation. After this function is enabled, the preceding counters are measured. The
measurement results are used to roughly evaluate the video throughput in a cell.

• 8.1 Principles

• 8.2 Network Analysis

• 8.3 Requirements

• 8.4 Operation and Maintenance

8.1 Principles
This function has been introduced to reduce the resources consumed by download services when a cell is
congested, saving air interface resources for high-priority services (such as video services with high
priorities) and improving user experience.
This function lowers the scheduling priorities of download services identified based on DSCPs in congestion
scenarios (such as P2P, FTP, and HTTP download) to control the download rates. The rate control depends
on DSCP-based service differentiation. For details, see 7.2.1.2 Principles for DSCP-based Service
Differentiation. This section describes the download rate control function.
This function is controlled by the DownLoadRateLimitSwitch option of the CellAlgoSwitch.
ServiceDiffSwitch parameter. The process of this function is as follows:

2024-05-07 100
eRAN FDD Feature Documentation

• If the rate of the service exceeds the QosPolicy. DlSmbr parameter, the eNodeB lowers the scheduling
priority of the service to lower the service rate, instead of directly controlling the service rate. The
scheduling priority remains low until the download is complete. Figure 8-1 shows how the download
rate changes over time.

Figure 8-1 Download rate control

• If the service rate is always lower than the value of QosPolicy. DlSmbr , the eNodeB does not process
the scheduling priority. This does not affect user experience in download services.

8.2 Network Analysis

8.2.1 Benefits

Gains

This function reduces the resources consumed by download services when a cell is congested, saving air
interface resources for high-priority services (such as video services with high priorities) and improving user
experience.

Most Beneficial Scenarios

This function decreases the proportion of traffic of download services in the cell, which improves user
experience of high-priority services. If the traffic volume for download services in the cell exceeds 20% of
the total traffic volume in the cell during peak hours or off-peak hours, you are advised to enable this
function. If the preceding conditions are not met, this function does not have any negative impact but
cannot offer the expected gains.
The value of the QosPolicy. DlSmbr parameter depends on operator policies controlling download services.
The average single-UE throughput in a cell (indicated by User Downlink Average Throughput ) can be used
as a reference for setting the SMBR. It is recommended that the smaller value between the operators'
expected rate limit and the average cell throughput during peak hours be used as the SMBR value.

8.2.2 Impacts

Network Impacts
2024-05-07 101
eRAN FDD Feature Documentation

Cell capacity slightly decreases when the cell is heavily loaded and a high proportion of UEs near the cell
center are performing download services.

Function Impacts

RAT Function Function Switch Reference Description

Name

FDD Video resource CONGEST_VIDEO_RES_CTRL_SWITCH Video If video resource control

control in option of the CellAlgoSwitch. Experience in congestion scenarios
congestion DlSchExtSwitch parameter Optimization takes effect for UEs
scenarios running video services,
the rate of such UEs may
further decrease.

8.3 Requirements

8.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LOFD-081202 Busy-Hour Download Rate Control LT1S0BHDRC00 Per Cell

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

None

Mutually Exclusive Functions

RAT Function Function Switch Reference Description

Name

FDD SC-based SC_VIDEO_RATE_ADAPT_SW option of Video The two functions cannot be

video service the CellAlgoSwitch. Experience used at the same time
rate adaption ScVideoOptSwitch parameter Optimization because they use different
methods of service
identification.

8.3.3 Hardware

Base Station Models

No requirements

2024-05-07 102
eRAN FDD Feature Documentation

Boards

No requirements

RF Modules

No requirements

8.3.4 Other Requirements

NSA UEs do not support this function.

This function requires a service awareness device integrated into the EPC or provided by a third party. This
function relies on the service awareness device integrated into the EPC or provided by a third party to
identify services. Specific requirements are as follows:

1. Check whether the service identification function of the service awareness device can identify main
services (such as video services) on operators' networks. Obtain the traffic volume proportion of
download services.

2. Check whether the service awareness device can identify encrypted services, such as those using
HTTPS. In addition, check whether a majority of download services on the network are encrypted.

8.4 Operation and Maintenance

8.4.1 Data Configuration

8.4.1.1 Data Preparation

This function depends on the DSCP-based video service rate adaption function. This section describes only
the parameter settings that are different from those for DSCP-based video service rate adaption.

Table 8-1 and Table 8-2 describe the parameters used for function activation and optimization,
respectively.
Table 8-1 Parameters used for activation
Parameter Name Parameter ID Setting Notes

Service CellAlgoSwitch. Select the DownLoadRateLimitSwitch option.

Differentiated ServiceDiffSwitch
Switch

QoS Policy QosPolicy. QosPolicyId This parameter specifies the ID of a user-defined QoS policy. The
Identity QoS policy ID for each type of service must be unique.

Traffic Type QosPolicy. TrafficType Set this parameter to DOWNLOAD.

Priority Queue QosPolicy. PriQueueId It is recommended that this parameter be set to QUEUE1 or
Identity QUEUE2.
Queue 0 is the default queue. Packets whose DSCPs do not
match any queue or are not identified will enter queue 0.
Therefore, you are advised not to set this parameter to QUEUE0
for download services.

2024-05-07 103
eRAN FDD Feature Documentation

Parameter Name Parameter ID Setting Notes

Differentiated IpServiceQos. Dscp Set this parameter to the same value as the DSCP policy
Services Code configured on the service awareness device.
Point For example, if the service awareness device identifies a
download service and sets the DSCP to 15, the DSCP value 15
must be configured for download services on the eNodeB.

Traffic IpServiceQos. Set this parameter to Download services.

Description Description

QoS Policy Time IpServiceQos. Set this parameter to OFF.

Switch QosPolicyTimeSwitch

First QoS Policy IpServiceQos. Set this parameter to the QoS policy ID specific to the service to
Identity FirQosPolicyId be guaranteed.

Application IpServiceQos. Select the VIDEO_AND_DWNLD_RATE_CTRL_SW option. In this

Range ApplicationRange way, the QoS policy is applicable to DSCP-based video service
rate adaptation and busy-hour download rate control.

Table 8-2 Parameters used for optimization

Parameter Parameter ID Setting Notes
Name

Downlink QosPolicy. DlSmbr This parameter is dependent on operators' policy on

Service controlling download services. It is recommended that this
Maximum Bit parameter be set to the smaller value between operators'
Rate expected rate limit and average cell throughput during busy
hours.

Queue0 Weight ServiceDiffSetting. Set this parameter to its recommended value.

to Queue7 QueueWeight0 to
Weight ServiceDiffSetting.
QueueWeight7

8.4.1.2 Using MML Commands

Activation Command Examples

//Enabling busy-hour download rate control

MOD CELLALGOSWITCH: LocalCellId=0,ServiceDiffSwitch=DownLoadRateLimitSwitch-1;
//Configuring a QoS policy for download services (Queue 1 is used as an example.)
ADD QOSPOLICY: QosPolicyId=2, TrafficType=DOWNLOAD, PriQueueId=QUEUE1, DlSmbr=2000;
//Configuring a mapping between the DSCP and the QoS policy for download services
ADD IPSERVICEQOS:Dscp=15, Description="FTP Download Service", FirQosPolicyId=2,
ApplicationRange=PREALLOCATION_SW-0&VIDEO_AND_DWNLD_RATE_CTRL_SW-1;

Deactivation Command Examples

//Disabling busy-hour download rate control

2024-05-07 104
eRAN FDD Feature Documentation

MOD CELLALGOSWITCH: LocalCellId=0,ServiceDiffSwitch=DownLoadRateLimitSwitch-0;

8.4.1.3 Using the MAE-Deployment

• Fast batch activation

This function can be batch activated using the Feature Operation and Maintenance function of the
MAE-Deployment. For detailed operations, see the following section in the MAE-Deployment product
documentation or online help: MAE-Deployment Operation and Maintenance > MAE-Deployment
Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.

• Single/Batch configuration
This function can be activated for a single base station or a batch of base stations on the MAE-
Deployment. For detailed operations, see Feature Configuration Using the MAE-Deployment .

8.4.2 Activation Verification

Check the values of the L.Thrp.bits.DL.Pri.1 and L.Thrp.Time.DL.Pri.1 counters. If the value of either counter
is not 0, the function has been activated.

8.4.3 Network Monitoring

• Evaluation based on single UE experience

It is recommended that the service experience of a single UE be used to evaluate whether the
download service throughput has decreased and the throughput of high-priority services has
increased. The statistics about L.Thrp.bits.DL.Pri.1 / L.Thrp.Time.DL.Pri.1 are collected only after this
function is enabled. These statistics are used to roughly evaluate the download service throughput of
a cell.

• Evaluation based on eNodeB counters

If you use eNodeB counters to evaluate this feature, services are not differentiated, but you can still
determine the download service throughput without rate control.

• Set the traffic type for download services to OTHER so that rate adaption will not be performed.
Meanwhile, specify that download service packets are scheduled through the specified queue
(Queue 1 is used as an example) and that the weight of this queue is the same as that of other
queues. This is used to collect the statistics only about the download service throughput.

//Setting a QoS policy for video services

ADD QOSPOLICY: QosPolicyId=126,TrafficType=OTHER,PriQueueId=QUEUE1;
//Configuring a mapping between the DSCP and the QoS policy for download services
MOD IPSERVICEQOS:Dscp=15, Description="FTP Download Service", QosPolicyTimeSwitch=OFF,
FirQosPolicyId=126;
//Configuring weights for service queues
MOD SERVICEDIFFSETTING: QueueWeight0=5, QueueWeight1=5, QueueWeight2=5, QueueWeight3=5,
QueueWeight4=5, QueueWeight5=5, QueueWeight6=5, QueueWeight7=5;

• Restore the download service configurations to those required by the live network.

//Configuring a QoS policy for download services (Queue 1 is used as an example.)

2024-05-07 105
eRAN FDD Feature Documentation

ADD QOSPOLICY: QosPolicyId=2, TrafficType=DOWNLOAD, PriQueueId=QUEUE1, DlSmbr=2000;

//Configuring a mapping between the DSCP and the QoS policy for download services
ADD IPSERVICEQOS:Dscp=15, Description="FTP Download Service", FirQosPolicyId=2;
//Configuring weights for service queues
MOD SERVICEDIFFSETTING: QueueWeight0=10, QueueWeight1=5, QueueWeight2=5, QueueWeight3=10,
QueueWeight4=10, QueueWeight5=20, QueueWeight6=20, QueueWeight7=20;
//Removing the QosPolicyId parameter setting for collecting statistics on the download service throughput
RMV QOSPOLICY: QosPolicyId=126;

This feature contains the following functions.

• Video TTI bundling (FDD)

• Inter-eNodeB UL CoMP for video services (FDD)

• 9.1 Video TTI Bundling (FDD)

• 9.2 Inter-eNodeB UL CoMP for Video Services (FDD)

9.1 Video TTI Bundling (FDD)

9.1.1 Principles
TTI bundling can be used for both VoLTE services and video services identified based on SC. The TTI
bundling principles and procedures are the same as those for VoLTE services. For details, see section "TTI
Bundling" in VoLTE . This document describes only the differences from TTI bundling for VoLTE services.
The TtiBundlingForVideoSwitch option of the CellAlgoSwitch. UlSchSwitch parameter controls TTI
bundling for video services. For details about SC-based video service identification, see 4 SC-based Service
Identification. When a cell-edge UE suffers from poor channel quality and is allocated limited transmit
power, TTI bundling increases the cell edge coverage of the PUSCH.

This function requires SC-based service identification to support the IPv4 and IPv6 protocols.

Entry into the TTI Bundling State

A video service UE enters the TTI bundling state if:

• The UE has a bearer for video services identified based on SC but not for VoLTE or push to talk (PTT)
services.

• The number of consecutive SINR measurement values that are less than the target SINR reaches the
value of the CellUlschAlgo. StatisticNumThdForTtibTrig parameter.

• If the CellTtiBundlingAlgo. R12TtiBundlingSwitch parameter is set to ON, the target SINR is

specified by the CellTtiBundlingAlgo. SinrThdToTrigR12TtiB parameter.

2024-05-07 106
eRAN FDD Feature Documentation

• If the CellTtiBundlingAlgo. R12TtiBundlingSwitch parameter is set to OFF, the target SINR value
is controlled by the CellTtiBundlingAlgo. SinrThdToTrigVideoTtib parameter.

• The uplink power of the UE is limited.

If a UE meets all of these conditions, the eNodeB sends the UE an RRC Connection Reconfiguration
message, instructing the UE to enter the TTI bundling state.

Exit from 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:

• The video service has not been released, and the number of consecutive SINR measurement values
that are greater than the sum of the target SINR and the CellUlschAlgo. HystToExitTtiBundling
parameter value reaches the value of the CellUlschAlgo. StatisticNumThdForTtibExit parameter.

• The video service has been released, and the number of consecutive SINR measurement values that
are greater than MIN{(Target SINR + CellUlschAlgo. HystToExitTtiBundling ), 6 dB} reaches the value
of the CellUlschAlgo. StatisticNumThdForTtibExit parameter.

Data Block Transmission

When a UE enters the TTI bundling state, data block transmission for video 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, whereas it is not limited for video services.

9.1.2 Network Analysis

9.1.2.1 Benefits

Gains

This function enhances uplink coverage and increases MCS indexes in weak uplink coverage areas,
reducing the packet loss rate, increasing throughput of CEUs performing video services, and improving
playback experience.
Unlike the TTI bundling function defined in 3GPP Release 10, in 3GPP Release 12-compliant TTI bundling,
the maximum number of allocated PRBs is no longer limited to three, and the restriction that MCS index
10 must be used has been removed. This way, resources can be flexibly allocated, and UEs in the TTI
bundling state are less likely to have limited uplink throughput.

Most Beneficial Scenarios

2024-05-07 107
eRAN FDD Feature Documentation

• It is recommended that this function be enabled when the following conditions are met to achieve
great gains:

• The coverage is weak, for example, more than 10% of the uplink MCS indexes are 0.
Percentage of uplink MCS index 0 = L.ChMeas.PUSCH.MCS.0 /Sum of L.ChMeas.PUSCH.MCS.0
through L.ChMeas.PUSCH.MCS.24

• The network load is light, for example, the downlink PRB usage ( Downlink Resource Block
Utilizing Rate ) is lower than 30%.

• The video traffic at the cell edge is heavy. For example, more than 5% of the traffic for UEs at the
cell edge is video traffic. Deep indoor coverage or LTE network edges are typical scenarios.
Proportion of video traffic at the cell edge = L.Exp.Video.Thrp.bits.DL.Far /
L.Exp.Video.Thrp.bits.DL.All

• This function is not recommended for:

• High speed cells or ultra-high speed cells, avoiding increase in the air interface signaling load

• Cells with a bandwidth of 1.4 MHz, avoiding increase in the PRB usage

• Scenarios where uplink interference is light, avoiding decrease in UE throughput

9.1.2.2 Impacts

Network Impacts

This function requires RRC messages to trigger and terminate it, which increases RRC signaling interactions
in cells. When the number of TTI bundling mode reconfiguration messages in the cell (measured by the
counters L.Signal.Num.TtiBundling.Enter and L.Signal.Num.TtiBundling.Exit ) is large, the average board
CPU usage (measured by the counter VS.BBUBoard.CPULoad.Mean ) slightly increases.

Function Impacts

The following table lists the functions that have impact relationships with video TTI bundling. For details
about functions that have impact relationships with TTI bundling, see VoLTE .
Feature Name Function Switch Reference Description

TTI bundling TtiBundlingSwitch option of the VoLTE Triggering video TTI bundling
CellAlgoSwitch. UlSchSwitch parameter requires RRC messages, which
increases RRC signaling interactions
in cells. Enabling VoLTE TTI
bundling and video TTI bundling
(including 3GPP Release 12-
compliant TTI bundling) produces
the following impacts:
If a UE enters the VoLTE TTI
bundling state and then performs
video services, it remains in the
VoLTE TTI bundling state. The
conditions for video TTI bundling

2024-05-07 108
eRAN FDD Feature Documentation

Feature Name Function Switch Reference Description

are used for TTI bundling

evaluation only after the VoLTE
services are released and the UE
exits the VoLTE TTI bundling state.
If a UE enters the video TTI
bundling state and then performs
VoLTE services, it remains in the
video TTI bundling state. The
conditions for VoLTE TTI bundling
are used for TTI bundling
evaluation only after the UE exits
the video TTI bundling state.

Inter-eNodeB UlCompForVideoSwitch option of the Video When a UE meets the conditions

UL CoMP for CellAlgoSwitch. UplinkCompSwitch Experience for entering the 3GPP Release 10-
video services parameter Optimization compliant TTI bundling state:
If 3GPP Release 12-compliant TTI
bundling eHARQ has taken effect,
inter-eNodeB UL CoMP for video
services will not take effect.
If inter-eNodeB UL CoMP for video
services has been enabled, 3GPP
Release 12-compliant TTI bundling
eHARQ will not take effect.
For details about TTI bundling
eHARQ, see VoLTE .

Video resource CONGEST_VIDEO_RES_CTRL_SWITCH Video If video resource control in

control in option of the CellAlgoSwitch. Experience congestion scenarios takes effect
congestion DlSchExtSwitch parameter Optimization for UEs running video services and
scenarios the rate of UEs running video
services in weak coverage areas
exceeds the value of the
CellDlschAlgo.
CongestMaxVideoRate parameter,
video TTI bundling does not
produce any gains.

TDM TDM_SWITCH option of the NSA TTI bundling and TDM cannot take
NsaDcMgmtConfig. NsaDcAlgoSwitch Networking effect simultaneously.
parameter based on EPC

Dynamic PRB_DYNAMIC_MGMT_SW option of Dynamic LTE cells do not use shared PRBs
multi-carrier the NbPrbDynamicMgmt. Multi-Carrier for TTI bundling.
management NbPrbDynMgmtAlgoSw parameter Management
(FDD)

9.1.3 Requirements

9.1.3.1 Licenses

2024-05-07 109
eRAN FDD Feature Documentation

Feature ID Feature Name Model Sales Unit

LOFD-120205 Uplink Coverage Improvement for Video LT1S00DCIV00 Per Cell

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

Function Name Function Switch Reference Description

SC-based service SC_SERVICE_IDENTITY_SW and SC_SUPPORT_IPV6_SW Video Experience None

identification options of the ScPolicy. ScAlgoSwitch parameter Optimization

Mutually Exclusive Functions

The following table lists the function that is mutually exclusive with video TTI bundling. For details about
the functions that are mutually exclusive with TTI bundling, see VoLTE .
Function Name Function Switch Reference Description

Ultra high speed Cell. HighSpeedFlag set to High Speed TTI bundling is not supported in ultra
mobility ULTRA_HIGH_SPEED Mobility high speed mobility scenarios.

Dynamic None Smart 8T8R None

Massive Beam (FDD)

9.1.3.3 Hardware

Base Station Models

The following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

• MPT: The MPT must support SC-based video identification. For details, see 4.3.3 Hardware.

• BBP: The LBBPc does not support this function.

RF Modules

No requirements

2024-05-07 110
eRAN FDD Feature Documentation

9.1.3.4 Others
Requirements on UEs are as follows:

• The UEs support TTI bundling.

• TTI bundling defined in 3GPP Release 12 requires that UEs comply with 3GPP Release 12.

• Bit 3 and bit 28 of the FGI field indicate UE support for TTI bundling in compliance with 3GPP Release
8 and for TTI bundling in compliance with later 3GPP releases, respectively.

9.1.4 Operation and Maintenance

9.1.4.1 Data Configuration

9.1.4.1.1 Data Preparation
Table 9-1 describes the parameters used for function activation.
Table 9-1 Parameters used for activation
Parameter Name Parameter ID Setting Notes

Uplink schedule CellAlgoSwitch. UlSchSwitch Select the TtiBundlingForVideoSwitch option.

switch

R12 TTI Bundling CellTtiBundlingAlgo. Set this parameter to ON to enable the function.
Switch R12TtiBundlingSwitch

SINR Threshold To CellTtiBundlingAlgo. Set this parameter to its recommended value.

Trigger Video TTI SinrThdToTrigVideoTtib Set this parameter if the CellTtiBundlingAlgo.
Bundling R12TtiBundlingSwitch parameter is set to OFF.

SINR Threshold To CellTtiBundlingAlgo. Set this parameter to its recommended value.

Trigger R12 TTI SinrThdToTrigR12TtiB Set this parameter if the CellTtiBundlingAlgo.
Bundling R12TtiBundlingSwitch parameter is set to ON.

Statistic Num CellUlschAlgo. You are advised to retain the default value.
Threshold for TTIB StatisticNumThdForTtibTrig
Trigger

Statistic Num CellUlschAlgo. You are advised to retain the default value.
Threshold for TTIB StatisticNumThdForTtibExit
Exit

Hysteresis to Exit TTI CellUlschAlgo. You are advised to retain the default value.
Bundling HystToExitTtiBundling

Other parameter optimization suggestions are the same as those for TTI bundling. For details, see VoLTE .

9.1.4.1.2 Using MML Commands

Activation Command Examples

2024-05-07 111
eRAN FDD Feature Documentation

The object for which this function takes effect depends on the configuration of video services identified
based on SC. For details, see 4 SC-based Service Identification.

//Enabling video TTI bundling

MOD SCPOLICY:ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-1;
MOD CELLALGOSWITCH:LocalCellId=0,UlSchSwitch=TtiBundlingForVideoSwitch-1;
//Enabling TTI bundling specified in 3GPP Release 12
MOD CELLTTIBUNDLINGALGO: LocalCellId=0, R12TtiBundlingSwitch=ON;
//Configuring video TTI bundling
MOD CELLTTIBUNDLINGALGO: LocalCellId=0, SinrThdToTrigVideoTtib=-3;
//Configuring TTI bundling specified in 3GPP Release 12
MOD CELLTTIBUNDLINGALGO: LocalCellId=0, SinrThdToTrigR12TtiB=3;
//Setting the threshold expressed in the number of times the channel quality of a UE consistently meets conditions for
entering TTI bundling, the threshold expressed in the number of times the channel quality of a UE consistently meets
conditions for exiting TTI bundling, and the hysteresis of the SINR threshold for exiting from TTI bundling against the SINR
threshold for entering TTI bundling
MOD CELLULSCHALGO: LocalCellId=0, StatisticNumThdForTtibTrig=N10_TTIB_ENTER,
StatisticNumThdForTtibExit=N20_TTIB_EXIT, HystToExitTtiBundling=5;

Deactivation Command Examples

//Turning off the SC-based service identification switch. If this switch has been turned on before this function is enabled,
you do not need to turn off this switch.
MOD SCPOLICY:ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-0;
//Disabling video TTI bundling
MOD CELLALGOSWITCH:LocalCellId=0,UlSchSwitch=TtiBundlingForVideoSwitch-0;
//Disabling TTI bundling specified in 3GPP Release 12
MOD CELLTTIBUNDLINGALGO: LocalCellId=0, R12TtiBundlingSwitch=OFF;

9.1.4.1.3 Using the MAE-Deployment

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

9.1.4.2 Activation Verification

• Observe the value of the ttiBundling field in ul-SCH-Config of mac-MainConfig in the

RRC_CONN_RECFG message over the Uu interface. This function takes effect if both of the following
conditions are met:

• The value of the ttiBundling field is TRUE and the VoLTE-specific QCI is not used, indicating that
the UE normally enters the video TTI bundling state.

• The value of the ttiBundling field is FALSE and the VoLTE-specific QCI is not used, indicating that
the UE exits the video TTI bundling state.

• For 3GPP Release 12-compliant TTI bundling eHARQ, check the value of the e-HARQ-Patter-r12 field.

2024-05-07 112
eRAN FDD Feature Documentation

• If the field value is TRUE and the QCI is not for VoLTE, 3GPP Release 12-compliant TTI bundling
eHARQ has taken effect.

• If the field value is FALSE and the QCI is not for VoLTE, 3GPP Release 12-compliant TTI bundling
eHARQ fails to take effect or is disabled.

• If the values of the following counters increase significantly, TTI bundling is configured for both UEs
running video services and VoLTE UEs. In this situation, this function has taken effect.
Counter ID Counter Name Counter Description

1526728496 L.Traffic.User.TtiBundling.Avg Average number of UEs on which TTI bundling takes effect in
a cell

1526746002 L.Traffic.User.R12TtiBundling.Avg Average number of UEs on which TTI bundling complying

with 3GPP Release 12 takes effect in a cell

9.1.4.3 Network Monitoring

• Common scenarios
After the function is enabled, the total downlink throughput of video services at the PDCP layer for
UEs at the cell edge increases. If the total traffic volume of video services is stable, the increase is
measured by the L.Exp.Video.Thrp.bits.DL.Far counter. If the traffic volume is unstable (for example,
the L.Exp.Video.Thrp.bits.DL.All counter fluctuates by more than 5%), the increase can be estimated by
dividing L.Exp.Video.Thrp.bits.DL.Far by L.Exp.Video.Thrp.bits.DL.All .

• Heavy interference scenarios (For example, the interference over thermal is greater than 20 dB.)
This function may take effect for UEs between the cell center and edge or at the cell edge. In such
cases, performance of this function cannot be measured using the preceding counters. Instead, the
L.Exp.Video.Thrp.bits.DL.All counter (total throughput of video services at the PDCP layer) measures
performance of this function.

9.2 Inter-eNodeB UL CoMP for Video Services (FDD)

9.2.1 Principles
SC-based video service identification supports inter-eNodeB UL CoMP. The UlCompForVideoSwitch option
of the CellAlgoSwitch. UplinkCompSwitch parameter controls this function. For details about SC-based
video service identification, see 4 SC-based Service Identification.

This function requires SC-based service identification to support the IPv4 and IPv6 protocols.

After this function is enabled, it takes effect only for video service UEs whose uplink power resources are
limited in their serving cells. It enables an appropriate coordinated cell to work with the serving cell of a
UE to implement UL CoMP. This function reduces the number of uplink TBs erroneously transmitted during
the initial transmission and decreases the packet loss rate, thereby improving video quality and edge
coverage for UEs performing video services.
The CoMP principles and procedures for video services are identical to those for VoLTE services. The event
A3 offset is the same one used for relaxed-backhaul-based UL CoMP (CellUlCompAlgo.

2024-05-07 113
eRAN FDD Feature Documentation

UlCompA3OffsetForRelaxedBH ). For details, see section "LOFD-081219 Inter-eNodeB VoLTE CoMP" in

VoLTE .

9.2.2 Network Analysis

9.2.2.1 Benefits

Gains

This function reduces the number of retransmissions and reduces the packet loss rate to increase
throughput of CEUs performing video services.

Most Beneficial Scenarios

• It is recommended that this function be enabled when the following conditions are met to achieve
great gains:

• The coverage is weak, for example, more than 10% of the uplink MCS indexes is 0.
Percentage of uplink MCS index 0 = L.ChMeas.PUSCH.MCS.0 /Sum of L.ChMeas.PUSCH.MCS.0
through L.ChMeas.PUSCH.MCS.24

• The network load is light, for example, the downlink PRB usage ( Downlink Resource Block
Utilizing Rate ) is lower than 30%.

• The video traffic at the cell edge is heavy. For example, more than 5% of the traffic for UEs at the
cell edge is video traffic. Intensive indoor coverage or LTE network edges are typical scenarios.
Proportion of video traffic at the cell edge = L.Exp.Video.Thrp.bits.DL.Far /
L.Exp.Video.Thrp.bits.DL.All

• This function is not recommended for:

• High speed cells or ultra-high speed cells, avoiding increases in the air interface signaling load

• Cells with a bandwidth of 1.4 MHz, avoiding increasing PRB usage

• Scenarios where uplink interference is light. Inter-eNodeB UL CoMP for video services may bring
no gains.

9.2.2.2 Impacts

Network Impacts

With this function is enabled, inter-eNodeB transmission bandwidth consumption increases slightly.

Function Impacts

2024-05-07 114
eRAN FDD Feature Documentation

Feature Name Function Switch Reference Description

Video TTI TtiBundlingForVideoSwitch option of the Video When a UE meets the conditions
bundling CellAlgoSwitch. UlSchSwitch parameter Experience for entering the 3GPP Release 10-
(FDD) Optimization compliant TTI bundling state:
If 3GPP Release 12-compliant TTI
bundling eHARQ has taken effect,
inter-eNodeB UL CoMP for video
services will not take effect.
If inter-eNodeB UL CoMP for
video services has been enabled,
3GPP Release 12-compliant TTI
bundling eHARQ will not take
effect.
For details about TTI bundling
eHARQ, see VoLTE .

Video resource CONGEST_VIDEO_RES_CTRL_SWITCH Video If video resource control in

control in option of the CellAlgoSwitch. Experience congestion scenarios has taken
congestion DlSchExtSwitch parameter Optimization effect for UEs running video
scenarios services and the rate of UEs
running video services in weak
coverage areas exceeds the value
of the CellDlschAlgo.
CongestMaxVideoRate
parameter, inter-eNodeB UL
CoMP for video services (FDD)
does not produce any gains.

UL Multi- UlMultiClusterSwitch option of the Scheduling The UL Multi-Cluster function

Cluster (FDD) CellAlgoSwitch. UlSchExtSwitch does not take effect on UEs in the
parameter UL CoMP state.

Inter-eNodeB UlNonVoiceJROverRelaxedBHSw option of UL CoMP Inter-eNodeB UL CoMP based on

UL CoMP the ENodeBAlgoSwitch. OverBBUsSwitch relaxed backhaul (FDD) shares IP
based on parameter RAN transmission bandwidth with
relaxed inter-eNodeB UL CoMP for video
backhaul services.
(FDD)

QCI-specific LowDelayServiceOptSwitch option of the Air Interface When a UE meets the conditions
TTI Bundling CellAlgoSwitch. ServiceDiffSwitch Latency for entering the 3GPP Release 10-
parameter and Optimization compliant QCI-specific TTI
QCI_TTI_BUNDLING_SWITCH option of bundling state:
the CellQciPara. QciAlgoSwitch
parameter If 3GPP Release 12-compliant TTI
bundling eHARQ has taken effect,
inter-eNodeB UL CoMP for video
services will not take effect.
If inter-eNodeB UL CoMP for
video services has been enabled,
3GPP Release 12-compliant TTI
bundling eHARQ will not take
effect.

2024-05-07 115
eRAN FDD Feature Documentation

Feature Name Function Switch Reference Description

For details about 3GPP Release

12-compliant TTI bundling
eHARQ, see VoLTE .

Dynamic PRB_DYNAMIC_MGMT_SW option of the Dynamic LTE cells do not use shared PRBs
multi-carrier NbPrbDynamicMgmt. Multi-Carrier for TTI bundling.
management NbPrbDynMgmtAlgoSw parameter Management
(FDD)

9.2.3 Requirements

9.2.3.1 Licenses
Feature ID Feature Name Model Sales Unit

LOFD-120205 Uplink Coverage Improvement for Video LT1S00DCIV00 Per Cell

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

Function Name Function Switch Reference Description

SC-based service SC_SERVICE_IDENTITY_SW and SC_SUPPORT_IPV6_SW Video Experience None

identification options of the ScPolicy. ScAlgoSwitch parameter Optimization

Mutually Exclusive Functions

Function Function Reference Description

Name Switch

Static None Massive Inter-eNodeB UL CoMP for video services cannot be enabled together
Multiple MIMO with this function when the number of SectorSplitCell MOs
Beam (FDD) referenced by the SectorSplitGroup MO that includes the cell
specified by the Cell MO is 2.

Dynamic None Massive None

Massive MIMO
Beam (FDD)

9.2.3.3 Hardware

Base Station Models

The following base stations are compatible with this function:

2024-05-07 116
eRAN FDD Feature Documentation

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

• MPT: SC-based video identification is required. For details, see 4.3.3 Hardware.

• Baseband processing unit

• LBBPd: The RX mode of the LBBPd1 and LBBPd2 boards must be 2R and non-4R, respectively.
There is no requirement for the RX mode of other LBBPd boards.

• UBBP: The UBBPd3 or UBBPd4 board working in GL or UL mode does not support inter-eNodeB
UL CoMP for video services.

RF Modules

No requirements

9.2.3.4 Others
The requirements for inter-eNodeB UL CoMP are as follows:

• The eNodeB is time synchronized, and the precision is within ±3 μs.

• The inter-BBU one-way transmission delay is less than or equal to 8 ms.

• There is no intermodulation interference or PCI conflict.

• If eX2 interfaces are used, IP PM bidirectional activation is not allowed on either side. Otherwise, eX2
interfaces cannot work properly.

For the impact of IP PM on eX2 interfaces, see engineering guidelines in IP Performance Monitor . For
details about other requirements, see engineering guidelines for inter-eNodeB VoLTE CoMP in VoLTE .

9.2.4 Operation and Maintenance

9.2.4.1 Data Configuration

9.2.4.1.1 Data Preparation
Table 9-2 and Table 9-3 describe the parameters used for function activation and optimization,
respectively.
Table 9-2 Parameters used for activation
Parameter Name Parameter ID Option Setting Notes

Uplink Comp Switch CellAlgoSwitch. UplinkCompSwitch UlCompForVideoSwitch Select this option.

Table 9-3 Parameters used for optimization

Parameter Name Parameter ID Setting Notes

RelaxedBH UL CoMP A3 CellUlCompAlgo. Set this parameter to its

Offset UlCompA3OffsetForRelaxedBH recommended value.

2024-05-07 117
eRAN FDD Feature Documentation

Parameter Name Parameter ID Setting Notes

Sfn UL CoMP Threshold CellUlCompAlgo. SfnUlCompThd Set this parameter to its

recommended value.

Other scenario-specific data is the same as that for LOFD-070222 Intra-eNodeB UL CoMP Phase II. For details, see UL
CoMP .

9.2.4.1.2 Using MML Commands

Activation Command Examples

//Enabling inter-eNodeB UL CoMP for video services

MOD SCPOLICY:ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-1;
MOD CellAlgoSwitch:LocalCellId=0,UplinkCompSwitch=UlCompForVideoSwitch-1;

Optimization Command Examples

Recommended values are used as an example.

MOD CELLULCOMPALGO: LocalCellId=0, UlCompA3OffsetForRelaxedBH=-20,SfnUlCompThd=-8;

Deactivation Command Examples

//Turning off the SC-based service identification switch. If this switch has been turned on before this function is enabled,
you do not need to turn off this switch.
MOD SCPOLICY:ScAlgoSwitch=SC_SERVICE_IDENTITY_SW-0;
//Disabling inter-eNodeB UL CoMP for video services
MOD CellAlgoSwitch:LocalCellId=0,UplinkCompSwitch=UlCompForVideoSwitch-0;

9.2.4.1.3 Using the MAE-Deployment

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

9.2.4.2 Activation Verification

This function takes effect if the value of either of the following counters increases significantly and the
total PDCP-layer downlink traffic volume of video services for CEUs (measured by the
L.Exp.Video.Thrp.bits.DL.Far counter) increases.
Counter ID Counter Name

1526737762 L.ChMeas.ULRelaxedBHCoMP.PRB.Avg

1526737763 L.ULCoMP.ULRelaxedBHCoMP.User.Avg

9.2.4.3 Network Monitoring

2024-05-07 118
eRAN FDD Feature Documentation

• Common scenarios
After the function is enabled, the total PDCP-layer downlink throughput of video services for UEs at
the cell edge increases. If the total traffic volume of video services is stable, the increase is measured
by the L.Exp.Video.Thrp.bits.DL.Far counter. If the traffic volume is unstable (for example, the
L.Exp.Video.Thrp.bits.DL.All counter fluctuates by more than 5%), the increase can be estimated by
dividing L.Exp.Video.Thrp.bits.DL.Far by L.Exp.Video.Thrp.bits.DL.All .

• Heavy interference scenarios (For example, the interference over thermal is greater than 20 dB.)
This function may take effect for UEs between the cell center and edge or at the cell edge.
Performance of this function cannot be measured using the preceding counters. Instead, the
L.Exp.Video.Thrp.bits.DL.All counter (total throughput of video services at the PDCP layer) measures
performance of this function.

• 10.1 Principles

• 10.2 Network Analysis

• 10.3 Requirements

• 10.4 Operation and Maintenance

10.1 Principles
Turbo start video performs robust header compression (ROHC) for the headers of uplink TCP/IP service
data. This function reduces the amount of data transmitted in the uplink over the air interface in uplink
weak coverage scenarios, improving the downlink throughput of UEs running video services and video
service coverage.
This function only applies to services in acknowledged mode (AM) on the Radio Link Control (RLC) layer.
This function does not apply to QCI 1 voice bearers, QCIs 65 and 66 push to talk (PTT) bearers, or bearers
of extended QCIs for PTT services.
Turbo start video can be enabled by setting the CellAlgoSwitch. RohcSwitch parameter to ON and
selecting the Profile0x0006 option of the PdcpRohcPara. Profiles parameter. When the turbo start video
function is enabled and the weak coverage threshold for TCP/IP services is met, that is, the measured
uplink SINR (the measured uplink SINR of the primary carrier in uplink CA scenarios) is lower than the
threshold specified by the PdcpRohcPara. RohcTcpSinrTriggerThld parameter, the UE enters the ROHC
TCP state and performs ROHC TCP compression on headers of uplink TCP/IP service data packets.
Currently, turbo start video takes effect for QCIs based on their bearer setup sequences on the base station
side. In addition, QCIs cannot be specified for this function.
For details about ROHC algorithm principles, see ROHC .

10.2 Network Analysis

10.2.1 Benefits

Gains

2024-05-07 119
eRAN FDD Feature Documentation

This function produces the following benefits in weak coverage scenarios (typically, the RSRP is lower than
–120 dBm):

• Increases the downlink throughput of UEs running video services and the coverage of video services.
(For example, this function improves the coverage of HD video services of a single test UE by 2 dB to
3 dB or the downlink throughput of UEs performing such video services by 10% to 30%.)

• Compresses the headers of the uplink TCP service. The ROHC header compression efficiency of data
services can reach about 20% to 50% if UEs on a network are compatible with ROHC-TCP.
Uplink ROHC header compression efficiency for data services = L.PDCP.UL.RoHC.Data.HdrComp.Bytes /
L.PDCP.UL.RoHC.Data.Hdr.Bytes

• Air interface resources saved by UEs for which ROHC-TCP takes effect are occupied by other UEs in the uplink if
all uplink PRBs are used. In this case, the downlink throughput of ROHC-TCP UEs cannot be improved.
• Gains in the downlink throughput are smaller if no TCP timestamp is carried in uplink ACK packets.
• A 2 dB to 3 dB increase in the video coverage refers to a 2 dB to 3 dB decrease in the RSRP for a given data rate.

Most Beneficial Scenarios

• It is recommended that this function be enabled when all the following conditions are met (such as in
the deep indoor coverage or LTE network edge scenario) to achieve significant gains. Enabling this
function has no negative impact if the following conditions are not met.

• The coverage is weak, for example, the percentage of MCS index 0 in the uplink is greater than
10%.
Percentage of MCS index 0 in the uplink = L.ChMeas.PUSCH.MCS.0 /Sum of
L.ChMeas.PUSCH.MCS.0 through L.ChMeas.PUSCH.MCS.24

• The network load is light, for example, the downlink PRB usage ( Downlink Resource Block
Utilizing Rate ) is lower than 30%.

• The video traffic at the cell edge is heavy. For example, more than 5% of the traffic for UEs at the
cell edge is video traffic.
Proportion of video traffic at the cell edge = L.Exp.Video.Thrp.bits.DL.Far /
L.Exp.Video.Thrp.bits.DL.All

• This function is not recommended in high speed cells or ultra-high speed cells to avoid increases in
the air interface signaling load.

• The traffic volume proportion of video services for CEUs can be obtained only if SC-based service
identification is enabled.
• Observation of gains offered by turbo start video is not dependent on SC-based service identification.
However, to facilitate verification, UEs performing video services identified based on SC are used as model
UEs for performance verification in this document. Therefore, it is recommended that SC-based service
identification be enabled.

2024-05-07 120
eRAN FDD Feature Documentation

10.2.2 Impacts

Network Impacts

• ROHC-TCP is triggered by RRC messages, increasing RRC signaling interactions in cells.

• The CPU load increases slightly.

Feature Impacts

RAT Function Function Switch Reference Description

Name

FDD QCI-specific QCI_ROHC_SWITCH option of the Air Interface Turbo start video and QCI-specific
UDP-based CellQciPara. QciAlgoSwitch Latency UDP-based ROHC can be enabled
ROHC parameter Optimization simultaneously. However, for a
given UE:
Both turbo start video and QCI-
specific UDP-based ROHC can take
effect simultaneously on bearers
with different QCIs.
Turbo start video and QCI-specific
UDP-based ROHC cannot take
effect simultaneously on bearers
with the same QCI. The function
whose activation conditions are
met first takes effect first. The
other function can take effect only
after the function that has taken
effect terminates.

FDD Video CONGEST_VIDEO_RES_CTRL_SWITCH Video If video resource control in

resource option of the CellAlgoSwitch. Experience congestion scenarios takes effect
control in DlSchExtSwitch parameter Optimization for the UE running video services
congestion and the rate of the UE running
scenarios video services exceeds the value of
the CellDlschAlgo.
CongestMaxVideoRate
parameter, turbo start video does
not produce any gains.

FDD NSA NSA_DC_CAPABILITY_SWITCH option NSA If the MCG bearer, MCG split
networking of the NsaDcMgmtConfig. Networking bearer, or SCG split bearer is set
based on NsaDcAlgoSwitch parameter based on EPC up for an NSA UE, the PDCP of the
EPC bearer will be set to NR PDCP (in
compliance with 3GPP TS 38.323).
However, if voice services or
TCP/IP-based data services with
ROHC are used, only the
MCG_Bearer_EUTRA_PDCP bearer
can be set up and the PDCP of the
bearer must be set to E-UTRA
PDCP (in compliance with 3GPP TS

2024-05-07 121
eRAN FDD Feature Documentation

RAT Function Function Switch Reference Description

Name

36.323). Therefore, turbo start

video and NSA networking based
on EPC cannot take effect at the
same time.

10.3 Requirements

10.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit

FDD LAOFD-131204 Turbo Start Video LT1S000TSV00 Per Cell

10.3.2 Software

Prerequisite Functions

None

Mutually Exclusive Functions

None

10.3.3 Hardware

Base Station Models

For FDD, the following base stations are compatible with this function:

• 3900 and 5900 series base stations

• DBS3900 LampSite and DBS5900 LampSite

Boards

• The LMPT and LBBPc do not support ROHC-TCP.

RF Modules

No requirements

10.3.4 Others
The UE must support ROHC Profile 6. For how to determine whether a UE supports ROHC profile 6, see
10.4.2 Activation Verification.

2024-05-07 122
eRAN FDD Feature Documentation

10.4 Operation and Maintenance

10.4.1 Data Configuration

10.4.1.1 Data Preparation

Table 10-1 and Table 10-2 describe the parameters used for function activation and optimization,
respectively.
Table 10-1 Parameters used for activation
Parameter Name Parameter ID Setting Notes

ROHC switch CellAlgoSwitch. RohcSwitch Set this parameter to ON.

Compression profiles PdcpRohcPara. Profiles Select the Profile0x0006 option for TCP/IP services.

Table 10-2 Parameters used for optimization

Parameter Name Parameter ID Setting Notes

ROHC TCP SINR Trigger PdcpRohcPara. Set this parameter to its recommended
Threshold RohcTcpSinrTriggerThld value.

10.4.1.2 Using MML Commands

Activation Command Examples

Perform the following steps if ROHC has been activated:

//Enabling turbo start video

MOD PDCPROHCPARA: Profiles=Profile0x0006-1;

Perform the following steps if ROHC is not activated:

//Enabling ROHC and turbo start video

MOD PDCPROHCPARA: Profiles=Profile0x0001-0&Profile0x0002-0&Profile0x0003-0&Profile0x0004-0&Profile0x0006-1;
MOD CELLALGOSWITCH: LocalCellId=0, RohcSwitch=ON;

Optimization Command Examples

Default values are used as an example.

//Setting the ROHC-TCP SINR triggering threshold

MOD PDCPROHCPARA: RohcTcpSinrTriggerThld=0;

Deactivation Command Examples

//Disabling turbo start video

MOD PDCPROHCPARA: Profiles=Profile0x0006-0;

10.4.1.3 Using the MAE-Deployment

2024-05-07 123
eRAN FDD Feature Documentation

• Fast batch activation

This function can be batch activated using the Feature Operation and Maintenance function of the
MAE-Deployment. For detailed operations, see the following section in the MAE-Deployment product
documentation or online help: MAE-Deployment Operation and Maintenance > MAE-Deployment
Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.

• Single/Batch configuration
This function can be activated for a single base station or a batch of base stations on the MAE-
Deployment. For detailed operations, see Feature Configuration Using the MAE-Deployment .

10.4.2 Activation Verification

1. Create and start a Uu interface tracing task on the OSS.

2. Use a UE supporting the ROHC-TCP feature to perform TCP services.

Check whether the UE supports the ROHC feature and determine the profile supported by the UE
using the following methods:

a. Observe the RRC_UE_CAP_INFO message.

If either supportedROHC-Profiles>profile0x0006 or supportUplinkOnlyROHC-
Profiles>profile0x0006 is TRUE, as shown in Figure 10-1 and Figure 10-2, the UE supports
ROHC-TCP.

Figure 10-1 RRC_UE_CAP_INFO message tracing (1)

Figure 10-2 RRC_UE_CAP_INFO message tracing (2)

2024-05-07 124
eRAN FDD Feature Documentation

3. Observe the RRC_CONN_RECFG message over the Uu interface.

• If pdcp-Config > headerCompression > rohc > profiles > profile0x0006: TRUE or pdcp-Config >
uplinkOnlyHeaderCompression > rohc > profiles > profile0x0006: TRUE is displayed, as shown in
Figure 10-3 and Figure 10-4, the ROHC-TCP feature has been activated.

Figure 10-3 RRC_CONN_RECFG message tracing (activated) (1)

Figure 10-4 RRC_CONN_RECFG message tracing (activated) (2)

• If pdcp-Config > headerCompression > notUsed and pdcp-Config >

uplinkOnlyHeaderCompression > notUsed are displayed, as shown in Figure 10-5, the ROHC-
TCP feature is not activated.

Figure 10-5 RRC_CONN_RECFG message tracing (not activated)

2024-05-07 125
eRAN FDD Feature Documentation

4. If the average number of UEs running data services with ROHC is greater than 0, ROHC-TCP has
taken effect.
Average number of UEs running data services with ROHC = L.Traffic.User.RoHC.Avg –
L.Traffic.User.RoHC.Voice.Avg

10.4.3 Network Monitoring

Monitor the counters listed in the following table after function activation.
Counter Principle

Uplink ROHC decompression failure rate for data The decompression success rate has a negative
services = L.PDCP.UL.RoHC.FailDecomp.Data / correlation with the value of this counter.
L.PDCP.UL.RoHC.TotalDecomp.Data

Uplink ROHC header compression efficiency for Smaller values indicate higher compression efficiency.
data services =
L.PDCP.UL.RoHC.Data.HdrComp.Bytes /
L.PDCP.UL.RoHC.Data.Hdr.Bytes

Proportion of video traffic at the cell edge = Observe the L.Exp.Video.Thrp.bits.DL.Far counter when
L.Exp.Video.Thrp.bits.DL.Far / video traffic remains stable. A larger increase in the
L.Exp.Video.Thrp.bits.DL.All counter value indicates larger gains.
NOTE:
If video traffic fluctuates (for example, the
The traffic volume proportion of video services for L.Exp.Video.Thrp.bits.DL.All counter fluctuates by more
CEUs can be obtained only if SC-based service than 5%), consider cell-edge video traffic when
identification is enabled. evaluating gains. A larger increase in cell-edge video
traffic indicates larger gains.
The expected gain is 10% to 20%.

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.

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?

1. Open the EXCEL file of parameter reference.

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.

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

2024-05-07 126
eRAN FDD Feature Documentation

FAQ 2: How do I find the information about a certain reserved parameter from the used reserved
parameter list?

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

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.

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.

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?

1. Open the EXCEL file of performance counter reference.

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.

3. Click OK. All counters related to the feature are displayed.

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

1. 3GPP TS 38.323: " Packet Data Convergence Protocol (PDCP) specification (Release 16) "

2. 3GPP TS 36.323: " Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence
Protocol (PDCP) specification (Release 16) "

3. IP Performance Monitor

4. Massive MIMO (FDD)

5. QoS Management

6. ROHC

7. VoLTE

8. UL CoMP

9. Scheduling

10. Dynamic Multi-Carrier Management (FDD)

11. High Speed Mobility

2024-05-07 127
eRAN FDD Feature Documentation

12. Rate Control Based on User Types

13. Air Interface Latency Optimization

14. Intra-RAT Mobility Load Balancing

15. Terminal Awareness Differentiation

16. NSA Networking based on EPC

17. Transmission Resource Management

18. Smart 8T8R (FDD)

2024-05-07 128