You are on page 1of 18

Security Level: Internal

VoLTE Packet Loss


Optimization

www.huawei.com

HUAWEI TECHNOLOGIES CO., LTD.


Contents
 Feature Overview
 Background and Customer Benefits
 Application Scenarios
 Basic Principles
 Feature Gains and Network Impact

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 1


Feature Overview – Background and Benefits to Customers
With the introduction of VoLTE, the network performance measured by the traditional KPI (such as access and call
drop) assessment system has become inadequate to meet subscribers' requirements on the quality of voice
services.
Subscribers want better voice service experience, such as high clearness, zero delay, and fast connection.
The factors affecting voice quality include speech coding, packet loss rate, delay, and jitter. The key one of these
factors is the packet loss rate. Abnormal packet loss rate will directly lead to voice quality deterioration. During
problem identification, analysis, and resolution, the current VoLTE optimization depends on frequent drive tests,
complaints, and experience. This results in passive responses to voice problems and low efficiency of optimization.
The feature, VoLTE Packet Loss Optimization, can be used to automatically identify and optimize abnormal voice
packet loss over the VoLTE air interface. This decreases the VoLTE Packet Loss over the air interface, and improves
voice quality.
NO.1
Packet loss
NO.2
Voice code
How to automatically
detect network problems
Voice MOS Automatic How to reduce complaints
NO.3
problem
Delay
detecting
NO.1
Packet loss

NO.4
Jitter

HOW?
Automatic
Automatic effect
root cause evaluation
analysis

Automatic
optimizatio
n

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 2


Feature Overview – Application Scenarios
Supported or
Level-1 Scenario Level-2 Scenario Level-3 Scenario Remarks
Not
Special scenarios are not involved in optimization, and they are
High-speed coverage Not supported automatically identified and handled based on engineering
parameters.
Special scenarios are not involved in optimization, and they are
Tunnel coverage Not supported automatically identified and handled based on engineering
parameters.
Super-distance coverage (with a Special scenarios are not involved in optimization, and they are
coverage radius of 30 km or Not supported automatically identified and handled based on engineering
more) parameters.
Radio scenarios
Downlink pilot power optimization does not apply to indoor
Indoor coverage Partially supported
scenarios.
Densely populated urban areas
Supported
(with an ISD of 100 m)
Urban area
Common urban areas (with an
Supported
ISD of 500 m)
Suburban coverage (with a
coverage radius of 30 km or Supported
less)
Single-carrier coverage Supported
Multi-carrier coverage Supported
Multi-band coverage N/A
Inter-RAT coverage N/A

Multi-RRU cells Not supported


Air interface Antenna configurations N/A
networking
AAS N/A
scenarios
Multi-sector networking Supported
Networking scenarios where
Such scenarios need manual identification and are not involved in
RRUs are installed far from Not supported
optimization.
BBUs
Such scenarios need manual identification and are not involved in
Repeater-based networking Not supported
optimization.
RAN sharing with dedicated Such scenarios need manual identification and are not involved in
Not supported
carriers mode (RAN sharing) optimization.
RAN sharing with common Such scenarios need manual identification and are not involved in
Network Not supported
Network sharing carriers mode (MOCN) optimization.
architecture
Hybrid RAN sharing mode Such scenarios need manual identification and are not involved in
Not supported
(Hybrid sharing) optimization.
Roaming RAN sharing mode Such scenarios need manual identification and are not involved in
Not supported
HUAWEI TECHNOLOGIES CO., LTD.
(Roaming)
Huawei Confidential Page 3
optimization.
Feature Overview – Application Scenarios
Level-1 Supported or
Level-2 Scenario Level-3 Scenario Remarks
Scenario Not
CS voice services N/A
Service scenarios PS voice services Supported
BE services N/A
Combined services N/A
Routine traffic scenarios on
Supported
LTE networks
Traffic scenarios Live-network service burst In this version, this feature does not apply to live-network service
Not supported
scenarios burst scenarios.
Imbalanced load among
N/A
GSM, UMTS, and LTE cells
Single-mode macro NodeBs Supported
Co-MPT macro eNodeBs Supported
Partially
Small-cell eNodeBs Downlink pilot power optimization does not support.
eNodeB hardware supported
Partially
Pico eNodeBs Downlink pilot power optimization does not support.
supported
LampSite eNodeBs Not supported
Single-mode RRUs, RFUs, or AAUs are fully supported when a single
LTE carrier uses an RF channel.
Single-mode RRUs, RFUs, or Partially When multiple LTE carriers share an RF channel, multi-band RRUs,
AAUs supported RFUs, or AAUs only support downward power adjustment, and single-
band RRUs, RFUs, or AAUs support both upward and downward
power adjustment.
Small cells (such as micro and pico cells), pole cells, and LampSite cells
Hardware are not supported.
Partially
networking GL co-SDR When multi-band RRUs, RFUs, or AAUs are used, only downward
supported
scenarios power adjustment is supported. In other scenarios, both upward and
downward power adjustments are supported.
RRU/RFU/AAU hardware
Small cells (such as micro and pico cells), pole cells, and LampSite cells
are not supported.
Partially
UL co-SDR When multi-band RRUs, RFUs, or AAUs are used, only downward
supported
power adjustment is supported. In other scenarios, both upward and
downward power adjustments are supported.
Partially
GUL co-SDR Only downward power adjustment is supported.
supported
CL co-SDR Not supported
SDR shared by FDD and TDD
Not supported
cells
Intra-RAT co-antenna
N/A
networking
HUAWEI TECHNOLOGIES
Antenna networking CO., LTD. Huawei Confidential Page 4
Inter-RAT co-antenna
N/A
networking
Contents
 Feature Overview
 Basic Principles
 Feature Gains and Network Impact

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5


Basic Principles – VoLTE Packet Loss Optimization
Solution Overview
Monitor Analysis Optimization Evaluation

ROHC • UL & DL Scheduling


Parameter check
decompression
failures and optimization
• Gap, DRX, SPS, ROHC, VoLTE
and IRC
eNodeB Parameter • …
exceptions Uplink voice
Uplink voice Abnormal Number of packet loss rate
packet loss VoLTE MR subscribers

rate and CHR Resources • InterFreqHOA1ThdRSRP


PRB Downlink voice
analysis Handovers • InterFreqHOA2ThdRSRP packet loss rate
CCE
• InterFreqHOA4ThdRSRP
Extensive weak
coverage
Local weak
coverage
Remote weak
Cell
coverage • RS Power
Uplink Weak coverage • P0NominalPUCCH
coverage caused by RRC Establish SR
abnormal power Power and power
• P0NominalPUSCH
PassLossCoeff
Air interface

Downlink control control •


coverage Weak coverage •
with available E-RAB Establish SR
Uplink PucchPcTargetSinrOffset
Downlink voice Cell-level interferenc power allowance
• …
packet loss MR, CHR, e Link imbalance
and KPI Downlink CDR
rate interferenc Missing
analysis e
neighboring cell
configuration
• Missing Neighbor HO SR
No primary serving
cell
Prompted detect
optimization advice • PCI MOD3 conflict
Pilot pollution Throughput
detect
Overshoot coverage

PCI Mod3 conflicts

Data: PM Data: PM, CHR, CM, and EP Data: PM Data: PM

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6


Basic Principles – Data Sources

The following table lists the data sources used by the VoLTE Packet Loss
Optimization feature.

Engineering CM PM MR CHR
Parameter

√ √ √ √ √

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7


Basic Principles – Overall Architecture

Feature description
The feature, VoLTE Packet Loss Optimization, Manually
automatically identifies problematic cells with voice import/export
packet loss, analyzes the root cause, and gives engineering
optimization advice to improve voice packet loss over parameters
MAE-Optimization
the air interface.
The key service flow is as follows:
1. Prepare basic data.
Manually collect and import basic data, including engineering parameters. MAE- Trace
2. Create a region and enable the VoLTE feature. Access Server
Manually create a region, enable the VoLTE feature, and set task parameters. MAE
3. Collect performance counters and MRs. CM
Automatically collect and pre-process performance counters, CM data, MRs, and PM
CHRs required for the task.
MR/CHR
4. Identify problematic cells.
Monitor the voice packet loss rate to automatically identify problematic cells.
5. Analyze the root cause.
6. Generate optimization advice. eNodeB
The optimization advice based on project experience is generated by the
Optimization components. The optimization advice based on online
optimization is generated by the Analytics components.
7. Implement optimization advice.
Remote adjustment is automatically made based on the optimization advice.
8. Evaluate the optimization effect. Perform rollback if negative gains occur.
After optimization advice is implemented, monitor KPIs of problematic cell Architecture of the feature
groups by hour. If any KPIs deteriorate, roll back the related optimization
operations.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 8


Basic Principles – Identifying Problematic Cells
This feature is mainly used to address the problem of high packet loss rates over the
VoLTE air interface.
Start
This feature can automatically collect MRs, CHRs, CM, PM, and engineering parameters
Create the VoLTE Packet Loss Rate (manually imported), identify problematic cells with uplink and downlink voice packet
Optimization feature and enable it.
loss, and use VoLTE-level and cell-level parameters to make optimization.
Collect data.
The following descriptions are about the problematic cell identification:

Definition of the packet loss


Man-machine interaction Classification of problematic cells
Identify problem cells.
scenario 1 rate
Analyze root causes of problem cells. Uplink voice packet loss rate = Problematic cells with UL voice packet loss
L.Traffic.UL.PktLoss.Loss.QCI.1 Problematic cells with DL voice packet loss
Generate optimization advice based on Man-machine interaction (1526727961)/ Problematic cells with UL and DL voice packet loss
engineering experience. scenario 2
L.Traffic.UL.PktLoss.Tot.QCI.1
Deliver the optimization advice based on (1526727962) x 100% Method of identifying problematic cells
engineering experience.

Downlink voice packet loss rate = Problematic cells with UL voice packet loss: The UL
N Evaluate optimization advice and determine
whether to roll back the optimization advice,
Man-machine interaction L.Traffic.DL.PktUuLoss.Loss.QCI.1 voice packet loss rate is greater than the
and then evaluate gains.
scenario 3
(1526727934)/L.Traffic.DL.PktUuLoss. optimization threshold for uplink packet loss rate
(VoIP).
Tot.QCI.1 (1526727935) x 100%
N
Problematic cells with DL voice packet loss: The
Turn on the
online optimizing-based parameter DL voice packet loss rate is greater than the
optimization switch. optimization threshold for downlink packet loss
rate (VoIP).
Y
Problematic cells with UL and DL voice: The UL
Generate optimization advice based on online Man-machine interaction
optimizing. scenario 4 voice packet loss rate is greater than optimization
threshold for uplink packet loss rate (VoIP) and
the DL voice packet loss rate is greater than the
Check whether
the aximum number
optimization threshold for downlink packet loss
of execution periods (indicates by N) rate (VoIP).
is
reached.
Parameter Name Value Range & Default Value
Y
Value Range: 0.1–100
Optimization threshold for uplink packet loss rate (VoIP)
End Default Value: 0.7 Unit: %
Optimization threshold for downlink packet loss rate Value Range: 0.1–100
(VoIP) Default Value: 0.5 Unit: %

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9


Basic Principles – Root Cause 1
Overview
(1) Screen all the CHRs of calls with abnormal packet loss in the problematic cell, analyze information, such as the uplink and downlink MRs, in the CHRs. Identify the
proportion of weak coverage MRs and interference MRs, and the category with the highest proportion. The MR with the highest proportion is the root cause for packet
loss exceptions in the problematic cell.
Note: The air interface root cause can be subdivided into categories, such as depth, local end, remote end, and no primary serving cell, some of which will be used as the
input to the air interface root cause algorithm based on manual experience rules.
They may also be displayed as the information to facilitate decision making, and used as the reference for live network optimization.
(2) Analyze the PM data and counters, such as the busy hour load and ROHC decompression failure rate, of problematic cells, and identify the root cause for abnormal packet
loss caused by resource or eNodeB-side ROHC problems.
(3) Check and optimize VoLTE and cell-level parameters based on the configuration and root cause analysis results.

ROHC Uplink weak coverage


decompression
Uplink weak coverage:
failures
When the following conditions are met, the root cause for packet loss exceptions is uplink coverage:
Parameter Uplink SINR ≤ Threshold for poor uplink SINR & Uplink RSRP ≤ Threshold for uplink weak coverage RSRP & Average number of uplink RBs ≤
eNodeB Threshold for the number of uplink single-scheduling RBs
exceptions
Proportion of uplink weak coverage MRs > Threshold for uplink weak coverage MR proportion
Number of • Uplink weak coverage without power control allowance: There is weak coverage at the uplink and the PHR of uplink MRs is small er than or equal
subscribers to 0.
Resources
Based on the distance and TA obtained from MR correlation, the scenario can be subdivided into the following sub -scenarios:
PRB 1. Intensive weak coverage without power control allowance: PHR of uplink MRs ≤ 0 and TA ≤ 4
2. Local weak coverage without power control allowance: PHR of uplink MRs ≤ 0 and 4 <TA ≤ 10
CCE 3. Remote weak coverage without power control allowance: PHR of uplink MRs ≤ 0 and TA > 10
• Uplink power control with power control allowance: PHR of uplink MRs and 0 < PHR < 6
Extensive weak • Uplink power control problems: PHR of uplink MRs ≤ 0 and PHR ≥ 6
coverage • Link faults: The MAE analyzes each MR. If traffic is imbalanced between the uplink and downlink, the MAE regards the MR as one indicating link
Local weak faults.
Uplink coverage
Uplink interference
coverage Uplink interference:
Remote weak If the following conditions are met, the root cause for packet loss exceptions is uplink interference:
coverage
Air interface

Downlink Uplink SINR ≤ Uplink SINR poor threshold; Uplink RSRP > Uplink interference RSRP threshold
coverage Weak coverage Proportion of uplink weak coverage MRs > Threshold for uplink weak coverage MR proportion
caused by abnormal
Uplink power control Uplink ROHC decompression failures
interference
Weak coverage L.PDCP.UL.RoHC.FailDecompRatio is greater than uplink ROHC decompression failure rate threshold.
Downlink with available
interference power allowance Uplink resources
Link imbalance If any of the following conditions is met, the uplink resources are limited:
Missing 1: CCE resource usage > CCE high load threshold; Number of concurrent data transmission users > Threshold for the number of concurrent data
neighboring cell transmission users
configuration 2: Uplink PRB usage > Uplink PRB high load threshold; Number of concurrent data transmission users > Threshold for the number of concurrent
data transmission users
No primary serving 3: Uplink CCE allocation failures > Uplink CCE allocation failure times threshold; Number of concurrent data transmission users > Threshold for the
cell number of concurrent data transmission users
4: Proportion of uplink second-level PRB usage higher than 90% > Uplink PRB high load threshold; Number of concurrent data transmission users >
Pilot pollution Threshold for the number of concurrent data transmission users
5: Number of PRBs allocated to PUCCH/Number of total uplink PRBs > PUCCH high load threshold; Number of concurrent data transmission users >
Overshoot coverage Threshold for the number of concurrent data transmission users
5: Number of PRBs allocated to PUSCH/Number of total uplink PRBs > PUSCH high load threshold; Number of concurrent data transmission users >
PCI Mod3 conflicts Threshold for the number of concurrent data transmission users

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10


Basic Principles – Root Cause 2
Uplink weak coverage
ROHC Downlink weak coverage:
decompression If the following conditions are met, the root cause for packet loss exceptions in the problematic cell is downlink weak coverage:
failures Cell Downlink RSRQ ≤ threshold for poor downlink RSRQ and downlink RSRP ≤ downlink weak coverage RSRP threshold
eNodeB Proportion of downlink weak coverage MRs > Threshold for downlink weak coverage MR proportion
Parameter Missing neighboring cell configuration:
The MAE analyzes each MR indicating weak coverage. If the signal level of the strongest neighboring cell reaches the preset threshold but UEs
exceptions are not handed over to the neighboring cell, which is not included in the NCL of the problematic cell, the neighboring cell is regarded as
Resources missing.
Number of Extensive weak coverage:
subscribers If the TA obtained from MR correlation is smaller than the intensive weak coverage threshold (the default value is 1), the weak coverage is
caused by poor indoor coverage near the eNodeB.
PRB Local weak coverage:
CCE If the distance between the problematic cell, from which MRs indicating weak coverage are reported, and the eNodeB is shorter than the cell's
planned radius and, the cell does not suffer from intensive weak coverage, the MAE regards the cell as suffering from local weak coverage. (The
Extensive weak cell's planned radius is the average ISD calculated based on the top neighboring cells in the cell's coverage directions. The radius represents the
coverage theoretical coverage range of the cell.)
Remote weak coverage:
Uplink Local weak If the distance between the problematic cell, from which MRs indicating weak coverage are reported, and the NodeB is greater than the cell's
coverage coverage planned radius, the MAE regards the cell as suffering from remote weak coverage.
Air interface

Downlink Link faults:


coverage Remote weak The MAE analyzes each MR. If traffic is imbalanced among uplink and downlink links, the MAE regards the MR as one indicating link faults.
coverage No primary serving cell:
Uplink The MR is a weak coverage MR. There is no neighboring cell with strong signal strength, and the signal level difference between the
interference Weak coverage neighboring cell and the problematic cell is smaller than 3 dB.
Downlink caused by
interference abnormal power Downlink interference
control
Downlink interference:
Weak coverage If the following conditions are met, the root cause for packet loss exceptions is downlink interference:
with available Downlink RSRQ < Threshold for poor downlink SINR and downlink RSRP > Downlink interference RSRP threshold
power allowance Proportion of downlink interference MRs > Threshold for downlink interference MR proportion
Interference caused by overshoot coverage:
The MAE analyzes each MR indicating interference. If the signal level difference of the serving cell with the neighboring cells is smaller than 5 dB
Link imbalance (which can be modified) and, at the same time, intra-frequency cells of at least one layer exist between the serving cell and its neighboring cells,
the MAE regards the serving cell and its neighboring cells as a pair of overshooting cells.
Missing Missing neighboring cell configuration:
neighboring cell The MAE analyzes each MR indicating weak coverage. If the signal level of the strongest neighboring cell reaches the preset threshold but UEs
configuration are not handed over to the neighboring cell, which is not included in the NCL of the problematic cell, the neighboring cell is regarded as missing.
Pilot pollution:
No primary The MAE analyzes each MR indicating interference. If there are three or more neighboring cells whose signal level difference with the serving
serving cell cell is smaller than 5 dB (which can be modified) and, at the same time, the signal levels of the three neighboring cells are greater than or equal
Pilot pollution to the threshold for good RSCP, the MR is regarded as one indicating interference caused by pilot pollution.
The serving cell is a polluted cell, and the neighboring cells are pollution sources.
Overshoot PCI mod3:
coverage Analyze the interference MR. If the MOD3 of the problematic cell and those of intra-frequency neighboring cells are the same and signal levels
PCI Mod3 of intra-frequency neighboring cells are higher than that of the problematic cell, there are MOD3 conflicts between the problematic cells and
conflicts neighboring cells.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11


Basic Principles – Parameter Check and Optimization
and Handover Optimization Advice Generation
Parameter check Parameter and feature optimization Handover parameter optimization
• 20+ VoLTE and cell-level parameter 1. Interference scenarios: Adjust the inter-frequency
check • 20+ VoLTE and cell-level parameter parameters, InterFreqHOA1ThdRSRP, InterFreqHOA2ThdRSRP,
and InterFreqHOA4ThdRSRP, of services with QCI6, QCI7,
optimization
QCI8, and QCI9, to ensure non-GRB services of the interfered
• Based on comprehensive analysis of cell can be handed over to inter-frequency neighboring cells.
scenarios, root causes, and performance This can decrease intra-frequency interference and improve
the packet loss rate whose exceptions are caused by uplink or
Type Level Parameter downlink interference. (To ensure service performance during
Schedulin and after the handover, the premise for the adjustment is that
g KPIs, such as the VoLTE Packet Loss, Inter-frequency Handover
UE
DRX VoLTE DrxPolicyMode capabilit Success Rate, E-RAB Call Drop Rate, and UL Interference, of
y the inter-frequency neighboring cells are not worse than the
Gap thresholds.) Intra-frequency
interference
Gap VoLTE VoipWithGapMode Problematic cell neighboring cells

Multi
UL VoLTE UlVoipSchOptSwitch Freq
Scheduling UlVoipServStateEnhanced ROHC
Sw
UlVoLTEDataSizeEstSwitc
h
ULSCH_PRI_TYPE License&
2. Common scenario: No matter the root cause is interference,
Hardware
PushDtxSchStrategy PDCCH weak coverage, or voluntary, you can adjust parameters,
... InterFreqHOA1ThdRSRP, InterFreqHOA2ThdRSRP, and
DL Cell DLSCH_PRI_TYPE InterFreqHOA4ThdRSRP, to make voice services of
Scheduling problematic cells be handed over to inter-frequency
neighboring cells as soon as possible to optimize the cell
H/M/L load IRC
Preallocation VoLTE PreallocationSwitch voice packet loss rate. (To ensure service performance during
and after the handover, the premise for the adjustment is that
KPIs, such as the VoLTE Packet Loss, Inter-frequency Handover
Success Rate, E-RAB Call Drop Rate, and UL Interference, of
SPS VoLTE PUSCHSpsPcSwitch
the inter-frequency neighboring cells are not worse than the
PDSCHSpsPcSwitch
H interference
thresholds.)
Problematic cell
Edge coverage
Overlap interference

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12


Basic Principles – Power and Power Control Parameter
Optimization Based on the Combination of Project Experience
and Online Optimization
Step 1: Select parameters to be optimized based on the root cause and project experience, and provide the parameter adjustment direction
and optimization advice.
Step 1: Select parameters based on the root causes and Step 2: Determine the object whose parameters to be
cell UL and DL performance. adjusted, the adjustment direction, and optimization
advice based on project experience.

Step 2: For problematic cells where optimization based on project experience sees no obvious effect or rollback is required due to
deterioration, use online optimization based on parameters.
Step 1: Parameter dimension reduction Step 2: Optimization path learning Conditions for parameter
learning Narrow down the searching path based on project experience optimization based on online
Priority optimization parameter learning: Make and feedback on networks to accelerate the optimization speed.
learning
heuristic decisions in selecting priority Project experience: A large adjustment amount of selected
optimization parameters based on adjustment parameters often brings high performance improvement of  Dissatisfactory gains: Take a day
directions of different parameters in project problematic cells. However, it also leads to high risks on the as a cycle. After the optimization
experience, and reduce the dimension of overall performance of neighboring cells or the cell cluster. The
100+ combinations
advice is delivered, the uplink and
simultaneous optimization parameters. searching path should be tailored based on feedback on
networks. downlink voice packet loss rate
RS+1 gains are smaller than the
Performance: no good
threshold for online optimization
(PB+1, RS+1) initiation.
Performance:
best  Deterioration rollback: Take a
day as a cycle. After the
PB+1 optimization advice is delivered,
Performance:
good rollback has been performed on
cells with packet loss deterioration.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 13


Basic Principles – Optimization Advice Delivery
and Evaluation
Optimization advice delivery Rollback evaluation:
After optimization advice is delivered, the MAE
mode monitors the adjusted cells. If KPIs deteriorate or
 Automatic delivery
severely fluctuate (configurable thresholds are
The MAE supports end-to-end provided), the operations in the optimization advice
automatic optimization. It need to be rolled back.
Rollback evaluation rules
automatically delivers optimization Monitor the KPIs before and after the optimization. Select an
evaluation cycle (one hour) within a period of time and monitor
advice without manual intervention.
whether KPIs deteriorate for a few consecutive cycles. If yes, roll
 Manual delivery back the optimization operations immediately. These KPIs include:
• RRC Setup Success Rate
Engineers review optimization
• E-RAB Setup Success Rate (All)
advice and select suitable advice to • Service Drop Rate (All)
• Handover Success Rate (All)
deliver.
• Packet Loss Rate (VoIP)
• Traffic Volume

KPI Concerned with Rollback Value Range Default Value


Deterioration tolerance threshold of RRC setup success rate 0 to 100% 0.5%
Deterioration tolerance threshold of E-RAB setup success rate 0 to 100% 0.5%
Deterioration tolerance threshold of E-RAB call drop rate 0 to 100% 0.1%
Deterioration tolerance threshold of handover success rate 0 to 100% 1%
Deterioration tolerance threshold of packet loss rate 0 to 100% 0.1%
Deterioration tolerance threshold of throughput reduction 0 to 100% 10%
Tolerance threshold for burst call drop counts >0 10

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14


Contents

 Feature Overview
 Basic Principles
 Feature Gains and Network Impact

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15


Feature Gains and Network Impact

Feature gains (positive) Impact on networks (negative)


 Network KPI Improvement  System capacity
With this feature, uplink and downlink voice packet None
loss problems on Huawei networks can be  Network performance
automatically identified, and optimization advice can This feature will enable or adjust some eRAN features
be automatically implemented. The feature decreases or functions, and affect network performance. For
uplink and downlink voice packet loss rates, details, see section 1.4 in VoLTE Packet Loss
optimizes voice quality and user experience, and Optimization.
generates no obvious impact on the system.

 Efficiency improvement
This feature automatically identifies problematic cells
and generates optimization advice. This avoids high
costs brought by repeated DTs in traditional
optimization methods and reduces dependency on
manual experience. Therefore, the MAE can
independently and automatically solve packet loss
problems.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16


Thank you
www.huawei.com

You might also like