Solution-Based VoLTE Technical Training Slide V1.0

Solution-based VoLTE Technical
Training Slide
HUAWEI TECHNOLOGIES CO., LTD.

Contents
1 Solution Background
2 Technical Principle
3 Application Scenario
4 Tool Introduction
5 Specific Cases

Page2
VoLTE Voice Problems Cannot Be Ignored
For users, they hope to have better voice quality.
Weak signal
Access failure
...
Frequent call drop
Unclear voice
For operators, they hope to quickly find network

problems.
There is no
system to
evaluate voice
quality.
VoLTE
???
2013 2014
There is no What are the There is no
Since 2013, more and more operators around the world means to locate problems? method to
officially launched the VoLTE solution. voice quality demarcate voice
problems. quality.

Page3
Contents
4 Tool Introduction
5 Specific Cases

Page4
VoLTE Solution Overview (1/2)
Start
Call History Record Data sources include CHRs, MRs, traffic

statistics, alarm data, operation logs,
configuration files, and others.
Import data
Evaluate KPIs Four evaluation

Three dimensions
KPIs
What are
Locate problems
the causes
of
problems?
Generate optimization Parameter

Performance
optimization
suggestions optimization
Neighboring
cell
optimization
RF optimization
End

Page5
VoLTE Solution Overview (2/2)
Problem evaluation Problem demarcation Root cause locating Optimization
suggestion
PRACH utilization formulation
rate
Radio resource
problems Various High PRB usage
Obtaining of cells resource
that do not meet problems
Transmissio CCE/SRS
requirements n problems
TopN cell Heavy CPU load

eNodeB
Access obtaining problems
success rate Number of
subscribers Feature/parameter
Cell-level analysis
Terminal Intensive weak optimization
Offline rate problems coverage
Cell edge weak Neighboring cell
Core network coverage optimization
Poor VQI User-level analysis problems Uplink Power control
Abnormal CDR
coverage problem PCI optimization
analysis Feature/
problems
SRVCC parameter/ Link imbalance
success rate CDR alarm/operation
log check Downlink Other weak coverage
Power optimization
segmentation
coverage problems
Air interface problems Coverage optimization
problems Super-distance
(invoking ACP)
weak coverage
Downlink No primary Channel/
interference serving cell interference
problems detection
Pilot pollution
Capacity expansion
Uplink Overshoot solution
interference interference
problems PCI mod 3
Data sources for problem
Data source for problem interference
demarcation: traffic statistics,
evaluation: traffic statistics
internal and external CHRs, Pilot pollution
operation logs, alarm data, and Other intra-system
configuration data Data sources for root cause interference
locating: external CHRs, Inter-system
configuration data, and interference
engineer parameters
Page6
VoLTE Evaluation KPIs
User experience Evaluation KPIs Call process
Enter the destination number and press the dialing key.

MO UE eNodeB MME SGW PGW IMS MT UE
Press the Hear the

Accessibility From dialing key. To
RRC Con Req
ring tone. A
Evaluation RRC Setup Process
Service Request
Authentication
Can the call connection be set up? CSSR call completion rate Modify Bearer Request/Reponse
E-RAB Setup Req

(QCI=5)
Call RRC Reconfiguration

Access
Hear the E-RAB Setup Reponse
ring tone. To
From End the call.
Retainability Invite
E-RAB Setup Req
Evaluation (QCI=1)
RRC Reconfiguration
Is the call unexpectedly interrupted? Voice call drop rate E-RAB Setup Reponse
Create Bearer Request/Reponse
180 Ringing
B
Connect
Ring
Integrity Start the Connect Ack

From call. To End the call. C
Talking
Evaluation Talking
D
Can the other party clearly hear me? Proportion of poor uplink voice quality MR(A2)
RRC Reconfiguration
Proportion of poor downlink voice
Can I clearly hear the other party? quality MR(B2/B1)
HO Require
SRVCC PS to CS Request
eSRVCC
SRVCC PS to CS Response
HO Command
Mobility from
Eutran Command
Mobility SRVCC PS to CS Complete Ack
Evaluation E
UE Context Release
SRVCC success rate

There is no LTE coverage, and the call
needs to be maintained. MT UE

Page7
VoLTE KPI Calculation Principle
1. Voice call completion rate
RRC Con Req
•RRC_SSR (RRC setup success rate) =
A
RRC Setup Process (L.RRC.ConnReq.Succ/L.RRC.ConnReq.Att) x 100%
Service Request
Authentication
•S1SIG_SSR (S1 signaling connection setup success rate) =
Modify Bearer Request/Reponse
(L.S1Sig.ConnEst.Succ/L.S1Sig.ConnEst.Att) x 100%
E-RAB Setup Req
(QCI=5)
Call RRC Reconfiguration •E-RAB connection setup success rate for VoLTE services = (L.E –
Access
E-RAB Setup Reponse
RAB.SuccEst.QCI.1 + L.E-RAB.SuccEst.QCI.2 + L.E – RAB.SuccEst.QCI.5)/(L.E
Invite
E-RAB Setup Req – RAB.AttEst.QCI.1 + L.E – RAB. AttEst.QCI.2 + L.E – RAB.AttEst.QCI.5) x 100%
(QCI=1)
RRC Reconfiguration
E-RAB Setup Reponse

•Call setup success rate for VoLTE services = RRC_SSR x S1SIG_SSR x
Create Bearer Request/Reponse (L.E – RAB.SuccEst.QCI.1 + L.E – RAB.SuccEst.QCI.2 + L.E-
B
180 Ringing RAB.SuccEst.QCI.5)/(L.E - RAB.AttEst.QCI.1 + L.E - RAB.AttEst.QCI.2 + L.E -
Ring
Connect RAB.AttEst.QCI.5) x 100%
Connect Ack
2. Voice call drop rate

C
Talking
Talking
D
MR(A2) •Call drop rate (QCI=1) = [L.E – RAB.AbnormRel.QCI.1/(L.E –
RRC Reconfiguration
MR(B2/B1)
RAB.AbnormRel.QCI.1 + L.E – RAB.NormRel.QCI.1)] x 100%
HO Require
eSRVCC
SRVCC PS to CS Response
HO Command
Mobility from
Eutran Command
SRVCC PS to CS Complete Ack
UE Context Release
E
MT UE

Page8
VoLTE Evaluation KPI Calculation Principle
3. Proportion of poor uplink/downlink voice quality
A
RRC Con Req •Proportion of poor uplink voice quality = Calls with bad and poor uplink voice
RRC Setup Process
Service Request quality/Calls with excellent, good, acceptable, poor, and bad uplink voice quality
Authentication
•Proportion of poor downlink voice quality = Calls with bad and poor downlink voice
Modify Bearer Request/Reponse
E-RAB Setup Req

(QCI=5) quality/Calls with excellent, good, acceptable, poor, and bad downlink voice quality
Call
Access
RRC Reconfiguration
•Uplink packet loss rate =
E-RAB Setup Reponse
E-RAB Setup Req

Invite
L.Traffic.UL.PktLoss.Loss.QCI.1/L.Traffic.UL.PktLoss.Tot.QCI.1
(QCI=1)
RRC Reconfiguration •Downlink packet loss rate =

E-RAB Setup Reponse
Create Bearer Request/Reponse L.Traffic.DL.PktUuLoss.Loss.QCI.1/L.Traffic.DL.PktUuLoss.Tot.QCI.1
B
180 Ringing
Connect
4. SRVCC success rate
Ring
C
Connect Ack •LTE-to-UMTS preparation success rate =
Talking
Talking
L.IRATHO.SRVCC.E2W.ExecAttOut/L.IRATHO.SRVCC.E2W.PrepAttOut
D
MR(A2)
•LTE-to-UMTS handover success rate = (L.IRATHO.SRVCC.E2W.ExecSuccOut –
RRC Reconfiguration
MR(B2/B1)
HO Require L.IRATHO.SRVCC.E2W.MMEAbnormRsp) /L.IRATHO.SRVCC.E2W.ExecAttOut
eSRVCC
SRVCC PS to CS Response •LTE-to-GSM preparation success rate =
HO Command
Mobility from
Eutran Command
SRVCC PS to CS Complete Ack
L.IRATHO.SRVCC.E2G.ExecAttOut/L.IRATHO.SRVCC.E2G.PrepAttOut
E
UE Context Release
•LTE-to-GSM handover success rate = (L.IRATHO.SRVCC.E2G.ExecSuccOut –
L.IRATHO.SRVCC.E2G.MMEAbnormRsp) /L.IRATHO.SRVCC.E2G.ExecAttOut
MT UE

Page9
VoLTE Voice Quality Calculation Principle
 Principle: Voice quality indicator (VQI) is a Huawei-dedicated voice  Difference between the VQI and MOS: VQI reflects the air interface voice
quality evaluation criterion. It fits and evaluates the voice quality of quality. MOS reflects the E2E voice quality. Accuracy of the VQI is evaluated not
users on calls through radio air interface factors affecting voice quality. by comparing with the absolute value of the MOS but by performing correlation
The factors include jitter, delay, bit error rate (BER), frame error rate verification between the VQI and MOS. The verification aims to identify whether
(FER), noise, voice encoding mode, number of calls with one-way VQI can reflect the voice quality of air interfaces and whether the VQI and MOS
audio, number of handovers, and others. The VQI can accurately reflect can reflect the same voice quality trend. VQI helps monitor voice quality of cells
the change trend of voice quality so that network operators can monitor and users on the network side in real time and determine whether the voice
the voice quality of networks. quality is good or poor, providing guidance for solving voice quality problems on
the air interfaces.
Jitter
Delay
Temporal Non-linear Linear VQI
…… Processing Transforms Estimator
BER

Page10
VoLTE Calculation Principle
 VQI evaluation values are classified into five classes according to the determination thresholds. The recommended values of VQIExcellentThd, VQIGoodThd, VQIPoorThd, and
VQIBadThd are 4, 3, 2, and 1, respectively. For details about these values, see the recommended values for voice quality of five classes in ITU-T P.800.
 The uplink and downlink VQIs for collecting performance KPIs related to cell-level voice quality and monitoring user-level performance are as follows:
Bad Poor Accept Good Excellent L.Voice.VQI.UL.Excellent.Time Number of times that uplink voice
s quality is excellent
Deter VQI<= VQIBadThd VQIPoorThd VQIGoodThd <VQI<= VQI>
minati VQIBadThd <VQI<= <VQI<= VQIExcellentThd VQIExcellentThd Number of times that uplink voice
L.Voice.VQI.UL.Good.Times
quality is good
on VQIPoorThd VQIGoodThd
thres Number of times that uplink voice
L.Voice.VQI.UL.Accept.Times
holds quality is acceptable
Comparison between the VQI and packet loss rate: Number of times that uplink voice
L.Voice.VQI.UL.Poor.Times
quality is poor
Uplink and L.Voice.VQI.UL.Bad.Times Number of times that uplink voice

downlink quality is bad
voice quality
L.Voice.VQI.DL.Excellent.Time Number of times that downlink voice
s quality is excellent
Number of times that downlink voice

L.Voice.VQI.DL.Good.Times
quality is good

L.Voice.VQI.DL.Accept.Times
quality is acceptable
L.Voice.VQI.DL.Poor.Times
quality is poor

L.Voice.VQI.DL.Bad.Times
quality is bad

Page11
Key Data Sources for VoLTE KPI Locating – Internal and External
CHRs
What are the data sources?
Find all MRs related to each CHR using the

CHR (Call History Record) MR (Measurement Report)
internal and external CHR association
• The abnormal events of one call • An MR contains the radio link function based on the call ID and call time,
Internal and
record in the eNodeB CHR information used during calls in external CHRs analyze the service quality based on MR
contain the key event records of test cells. It reflects the coverage,
multiple layer-2/layer-3 modules. quality, and UE distribution of a data, and help network optimization
These records are classified into carrier and cell. It can help engineers analyze various service quality
four types: exception information customers locate various network
records, problem symptom problems, such as weak problems, such as the network coverage and
records, key air interface coverage and overshoot quality of the area where the UE is located
information records, and user coverage.
information records. This solution during a call drop.
uses the exception information
records, problem symptom
records, and key air interface
records.
Unlike the traditional KPI optimization solution, this solution associates CHRs with MRs and makes the service quality analysis possible.

Page12
Key Technology for VoLTE KPI Locating – Association Analysis
Reflects Experts' Thought
Analyze problem cells.
Provide the distribution of cell-level

problems.
Analyze the problem symptoms.
Provide detailed problem cause

locating process and locating results.

Page13
Key Technology for VoLTE KPI Locating –Uplink Weak Coverage
Locating Algorithm Is Enhanced
Figure 1 Formula for calculating the PUSCH transmit power
 Traditional solution: Formula for calculating the PUSCH transmit power of a UE:
 PCMAX (i ), 
PPUSCH (i )  min 
The coverage is identified only based on the signal strength 
10 log10 ( M PUSCH (i ))  PO_PUSCH ( j )   ( j )  PL   TF (i )  f (i ) 
Parameter description:
received by an eNodeB without considering the impact of the
: some path loss compensation factors
power control on the signal. : maximum transmit power of a UE
 The uplink weak coverage or poor quality is identified

M PUSCH (i ) : number of RBs allocated to the PUSCH of a UE through scheduling
PO_PUSCH ( j ) : target signal power spectrum expected by an eNodeB when the PUSCH refers to the TF
based on the DMRS RSRP or SINR. PL: path loss of a UE, which is calculated according to the downlink path loss estimated by the UE.
 TF (i ) : TF power spectrum offset relative to the PUSCH

 Enhanced solution:
f (i ) : power control adjustment value, which is calculated by dividing (accumulation type) and (absolute type).
According to 3GPP TS 36.213, uplink power control is classified

into four types: PUSCH, PUCCH, SRS, and PRACH. For Figure 2 PUSCH and SRS power control principle
example, the PUSCH transmit power is related to the

maximum transmit power of a UE, path loss, and number of
RBs. Figure 1 shows the formula for calculating the transmit
power.
 With the enhanced solution, uplink weak coverage is
identified based on the association analysis of power,
scheduling information, and DMRS RSRP or SINR.

Page14
Key Technology for VoLTE KPI Locating – Principle for Enhancing
Uplink Weak Coverage Locating
 Classification of downlink weak coverage problems:
Missing configurations of intra-frequency (inter-frequency)
neighboring cells, intra-frequency (inter-frequency) handover
delay, PCI confusion, handover prohibition, downlink
Serving Cell Target Cell
exception, super-distance weak coverage, edge weak
UE
coverage, intensive weak coverage, and no primary serving  The RSRP of the serving cell is poor and that of the target cell is good enough:
cell  If the neighbor relationship is not configured, this situation is considered as missing
configurations of neighboring cells.
PCI
confusion
 If PCIs in the neighboring cell list are the same, this situation is considered as PCI
Handover
delay Downlink confusion.
exception
 If the neighbor relationship is configured but the required handover is not performed, this
situation is considered as handover delay.
Missing
configurations
of intra- Super-
 If a cell is far from the serving cell, this situation is considered as super-distance weak
frequency
Identify weak distance
(inter- coverage.
frequency) coverage weak
neighboring
cells problems coverage  If weak coverage occurs at the serving cell edge, this situation is considered as edge
weak coverage.
 If weak coverage occurs in areas near the serving cell, this situation is considered as
No Edge
primary weak intensive weak coverage.
serving coverage
cell  If the network coverage overlaps in multiple cells and the signal strength is not
Intensive
weak distinguished, this situation is considered that there is no primary serving cell.
coverage
 If the downlink path loss is much higher than the uplink path loss, this situation is
considered as downlink exceptions.
Page15
Key Technology for VoLTE KPI Locating – Principle for Enhancing
Downlink Interference Locating
 Classification of downlink interference problems:
Missing configurations of inter-frequency neighboring cells, inter-frequency
handover delay, PCI confusion, PCI mod 3 conflict, pilot pollution, and Serving Cell
overshoot interference in neighboring cells Neighboring Cell 1
UE
Missing
configurati
ons of
inter-
frequency
neighborin
g cells
Overlappi
ng Inter- Neighboring Cell 2
interferen frequency
ce handover
delay
 The RSRP of the serving cell is high and the channel quality is poor:
 If an inter-frequency neighboring cell exists and the RSRP/RSRQ of a cell is better than
Identify root
causes of air the serving cell, but this neighboring cell is not in the neighboring relation table (NRT),
interface
problems this situation is considered as missing configurations of inter-frequency neighboring
cells. If this neighboring cell is in the NRT but all PCIs are the same, this situation is
Pilot
pollution considered as PCI confusion.
PCI
confusion  If an intra-frequency neighboring cell exists, the impact of intra-frequency interference is
large, and PCI mod 3 conflict exists, this situation is considered as PCI mod 3 conflicts.
PCI mod 3  If the pilot signal is the same, this situation is considered as pilot pollution.
conflict

Page16
Formulating Optimization Suggestions Based on Problem Causes
1. Optimize parameters (enable the
1. Accurately search for the missing 1. Adjust PCIs and optimize neighboring
1. Optimize parameters. IRC/MRC switch and adjust power
neighbor relationships. cells.
2. Enable the MLB feature. control parameters).
2. Quantize handover parameters (CIO). 2. Quantize handover parameters (CIO).
3. Replace boards or add sites. 2. Add tower-mounted amplifiers
3. Adjust RF-related parameters. 3. Adjust RF-related parameters.
(TMAs) and sites.
Resource capacity Uplink weak coverage Downlink weak coverage Downlink interference
Control channel usage Intensive weak coverage Intensive weak coverage PCI mod 3 conflict
Service channel usage Edge weak coverage Edge weak coverage Pilot pollution
Missing configurations of
Device usage Missing configurations of
Power control problem inter-frequency
neighboring cells
neighboring cells
Neighboring cell
Uplink imbalance Downlink imbalance
overshoot coverage

Page17
Related Features
 PDCCH symbol number adaptation
 The system adjusts the number of PDCCH symbols based on the PDCCH CCE requirements.
 Enhanced PDCCH symbol adaptation is enabled. The system best adjusts the number of PDCCH symbols based on the downlink throughput.
 MLB
 The eNodeB checks the cell load status. When a cell is heavily loaded, transfer UEs from the heavily-loaded cell to a lightly-loaded cell.
 The MLB brings the following gains:
• Select appropriate UEs and transfer them to inter-frequency neighboring cells with light load to alleviate load imbalance between inter-frequency cells.
• Improve the service access success rate, user experience, and resource utilization.
 MRO
 Optimize inappropriate handover parameters and cell reselection parameters to improve the mobility performance robustness.
 The mobility robustness optimization (MRO) brings the following gains:
• Specify a proper handover threshold so that UEs can access cells with better air interface quality, thereby improving the downlink coverage, service success
rate, and user experience, and reducing downlink interference.
 ANR
 eNodeBs detect unknown neighboring cells through the MRs of UEs and inter-frequency MRs.
 The automatic neighbor relation (ANR) brings the following gains:
• Add a neighbor relationship so that UEs can access cells with better air interface quality, thereby improving the downlink coverage, service success rate,
and user experience, and reducing downlink interference.

Page18
Contents
4 Tool Introduction
5 Specific Cases

Page19
Data Collection and Scenario Adaptation
Data collection
1. Collect the following data: CHR data and engineering parameters. Enable data sources to adapt to the following NE version: eRAN V100R008C10.
2. Deploy the Trace Server (basically, the Trace Server and U2000 are co-deployed).
3. Enable the following MML switches:

Enable the E-UTRAN VoIP capability support switch: MOD ENODEBALGOSWITCH: EUTRANVOIPSUPPORTSWITCH=ON;
Enable the voice quality monitoring algorithm switch: MOD ENODEBALGOSWITCH: VQMALGOSWITCH=VQM_ALGO_SWITCH_ON;
Disable the internal CHR sampling switch: ADD CHROUTPUTMODE: ModeNo=1, ChrDetailCauseVal=1 (0 indicates all UEs), ChrHierOutMode=Level_1_Output,
SamplingEnable=SamplingUnable;
4. For details about CHR data collection, see OMStar V500R012C00 LTE Data Collection Guide.
Scenario adaptation
Feature Data Source Verification Rule Mandatory or Not
External CHRs The data source must be an .sig log file. Yes
Traffic statistics The data source must be an .mrf.gz log file. Yes
Engineering parameters The data source must be a .csv table file. Yes
VoLTE problem locating
Configuration data The data source must be an .xml log file. Yes
Internal CHRs The data source must be a .CHR.gz table file. Yes
Operation log The data source must be an .opt log file. No

Page20
Contents
4 Tool Introduction
5 Specific Cases

Page21
OMStar VoLTE Accurate Optimization (Access Theme)
KPI Evaluation Isolation Demarcation
Required data  RRC phase
 Two evaluation scenarios  Layer-1 demarcation: Identify problems, such as the air interface,
 One contains the S1 phase, and the other one does not contain the S1 core network, resource, and eNodeB problems.
 Configuration data phase.  Layer-2 demarcation: Identify problems, such as no response from
 Customizing evaluation KPIs UEs, limited number of UEs, flow control, and resource allocation
 Traffic statistics failure.
 Allow users to customize voice and video KPIs for TopN evaluation
 E-RAB connection establishment phase
 Internal CHRs based on traffic statistics.
 Automatically filtering TopN cells  Layer-1 demarcation: Identify problems, such as the air interface,
 External CHRs  Use the Wilson interval ranking algorithm to sort cells that meet the core network, resource, terminal, and eNodeB problems.
threshold conditions, and automatically identify TopN cells.  Layer-2 demarcation: Identify problems, such as incorrect security
 Alarm logs mode configuration, intra-eNodeB handover conflicts, insufficient
 Filtering TopN cells by proportion
license, low uplink and downlink satisfaction rate, and the problem
 Operation logs  Perform TopN calculation by user-specified proportion.
that SRBRLC reaches the maximum retransmission times.
 Filtering TopN cells by absolute number
 Provide a list of TopN cells.
Principles
Performance Optimization Suggestions Root Cause Analysis
specifications
Downlink weak Downlink Uplink weak Uplink
 Traffic statistics: 200 sites x 7 coverage interference coverage interference
Air interface
problems
days
ZC root sequence check
External cell parameter
Parameters, alarms, or
Missing configurations of neighboring cells
Missing configurations of inter-frequency

Super-distance weak coverage
Uplink power control problems

Other intra-RAT interference
Resource capacity
operation logs
 External CHRs: 200 sites with
Intensive weak coverage

Cell radius check
Overshoot interference
No primary serving cell
Inter-RAT interference
Edge weak coverage
Edge weak coverage

check
Uplink exception
Handover delay
Handover delay
neighboring cells
Pilot pollution
TopN users
PCIMod3
3 x 2 busy hours or 100 GB
Others
Uplink interference
Downlink weak
Downlink weak
 Data processing efficiency: 1
coverage
coverage
interference
Downlink
hour

Page22
Result Parsing for OMStar VoLTE Accurate Optimization (Ac-
cess Theme)
Theme analysis process Result parsing
1. Import data.
2. Use the VoLTE solution to create tasks, set operation

parameters, and select evaluation scenarios (voice and video).
1. Identify TopN accessed cells based on KPIs. 2.1 Demarcate and locate voice problems, and drill down to the
classification and root causes of access problems through layer-1
demarcation.
3. Evaluate KPIs and filter out TopN cells with access

problems.
3. Identify resource capacity problems and collect

4. Display analysis results of TopN cells with access problems. 2.2. Analyze root causes of video access problems, and display statistics on daily cell resources during busy
the uplink and downlink satisfaction rate for access services and hours.
detailed root causes of air interface problems.
(1) Basic (2) Cell problem (3) Location of
demarcation
problem check and root causes of
results classification cell problems
5. Generate optimization suggestions.

4. Perform parameter check and alarm check, and 5. Display the MR statistics chart.
generate operation logs and optimization suggestions.

Page23
OMStar VoLTE Accurate Optimization (Call Drop Theme)
Required data
 Two evaluation scenarios
 One contains the MEE, and the other one does not contain the MEE.  Call drop
 Configuration data 
 Layer-1 demarcation: Identify air interface problems,
Customizing evaluation KPIs
resource problems, core network problems, transmission
 Allow users to customize voice and video KPIs for TopN evaluation
 Traffic statistics problems, and other problems.
based on traffic statistics.
 Layer-2 demarcation: Identify the following problems:
 Internal CHRs  Automatically filtering TopN cells
UEs do not respond, the connection reestablishment fails,
 Use the Wilson interval ranking algorithm to sort cells that meet the SRB/DRB RLC reaches the maximum retransmission
 External CHRs threshold conditions, and automatically identify TopN cells. times, uplink resynchronization fails, the handover
 Alarm logs
 Filtering TopN cells by proportion process is defective, radio resources are overloaded and
 Perform TopN calculation based on the user-specified proportion. preempted, and transmission resources are overloaded
 Operation logs  Filtering TopN cells by absolute number and preempted.
Principles
Performance Optimization
Root Cause Analysis
Suggestions
specifications
Downlink
Downlink Uplink weak Uplink
weak
 Traffic statistics: 200 sites x 7 coverage
interference coverage interference
External cell parameter check
Air interface
Operation log check

days
Resource capacity
Parameter check
problems
Missing configurations of neighboring

Alarm check
TopN users
Missing configurations of inter-

frequency neighboring cells

Edge weak coverage
Edge weak coverage
Uplink exception
Handover delay
Handover delay
Pilot pollution
PCIMod3
Others
cells
Downlink weak
Uplink weak
interference
interference
coverage
coverage
Downlink
Uplink
hour

Page24
Result Parsing for OMStar VoLTE Accurate Optimization (Call
Drop Theme)
1. Import data.

parameters, and select evaluation scenarios (voice and video).
2.1 Demarcate and locate problems, and drill down to the classification
1. Identify TopN cells with call drops based on KPIs. and root causes of call drop problems through layer-1 demarcation.
3. Evaluate call drop KPIs and filter TopN cells.
2.2 Analyze the root causes of video call drops, and display
4. Display analysis results of TopN cells with call drops. abnormal release categories and detailed root causes of air 3. Identify resource capacity problems and collect statistics
interface problems. on daily cell resources during busy hours.
(2) Cell
(1) Basic problem (3) Location of
problem check demarcation root causes of
results and cell problems
classification

4. Perform parameter check and alarm check, and
generate operation logs and optimization 5. Display the MR statistics chart.
suggestions.

Page25
OMStar VoLTE Accurate Optimization (Voice Quality Theme)
Required data  Six evaluation scenarios
 Poor downlink VQI
 Poor downlink voice quality, poor uplink voice quality, poor uplink and downlink voice quality,  Layer-1 demarcation: Identify problems at the layer higher than eNodeB, eNodeB
 Configuration data downlink packet loss rate, uplink packet loss rate, and uplink and downlink packet loss rate problems, and air interface problems.
 Customizing evaluation KPIs  Layer-2 demarcation: Identify problems, such as transmission problems, long cell
 Traffic statistics  Allow users to customize KPIs for TopN evaluation based on traffic statistics.
congestion duration, packet loss, and poor voice quality.
 Poor uplink VQI
 Internal CHRs  Automatically filtering TopN cells
 Layer-1 demarcation: Identify problems at the layer higher than eNodeB, eNodeB
 Use the Wilson interval ranking algorithm to sort cells that meet the threshold conditions, and
problems, and air interface or terminal problems.
 External CHRs automatically identify TopN cells.  Layer-2 demarcation: Identify problems, such as transmission problems, invalid IP
 Alarm logs  Filtering TopN cells by proportion packets, long cell congestion duration, limited PUSCH, limited PUCCH, low SR
 Perform TopN calculation based on the user-specified proportion.

scheduling priority, low BSR priority, packet loss, and poor voice quality.
 Operation logs
 Filtering TopN cells by absolute number
Principles
Performance Optimization Suggestions Root Cause Analysis
specifications
Downlink Uplink
Downlink Uplink weak
weak interferenc
 Traffic statistics: 200 sites x 7 coverage
interference coverage
e
External cell parameter check
Reverse antenna connection

Air interface
days problems
Resource capacity
Parameter check
Missing configurations of neighboring cells

Alarm check
Missing configurations of inter-frequency

TopN users


Edge weak coverage
Edge weak coverage
Uplink exception
Handover delay
Handover delay
neighboring cells
Pilot pollution
PCIMod3
Others
Downlink interference
Uplink interference
Downlink weak
Downlink weak
coverage
coverage
hour

Page26
Result Parsing for OMStar VoLTE Accurate Optimization (Voice Qual-
ity Theme)
1. Import data.

parameters, and select evaluation scenarios (poor uplink and
downlink voice quality and packet loss). 2 Demarcate and locate problems, and drill down to the
1. Identify TopN cells with poor voice quality based on KPIs.
classification and root causes of voice quality problems through
layer-1 demarcation.
3. Evaluate poor uplink and downlink KPI and filter TopN cells.
4. Display analysis results of TopN cells with poor voice quality. 3. Identify resource capacity problems and collect 4. Perform parameter check and alarm check, and
statistics on daily cell resources during busy generate operation logs and optimization suggestions.
(2) Cell hours.
classification

6. Generate the one-click report. The report contains four
5. Display the MR statistics chart. parts: evaluation, basic check, problem demarcation, and
suggestion.

Page27
OMStar VoLTE Accurate Optimization (SRVCC Theme)
Required data  Six evaluation scenarios  SRVCC handover preparation failure
 LTE-to-GSM handover preparation failure, LTE-to-GSM handover execution  Layer-1 demarcation: Identify the CN failures, problem that inter-RAT cells do not
identification, and call drop caused by the LTE-to-GSM handover initiation failure respond, and inter-RAT response preparation failures.
 Configuration data  LTE-to-UMTS handover preparation failure, LTE-to-UMTS handover execution  Layer-2 demarcation: Identify possible causes of the problems that inter-RAT ID
identification, and call drop caused by the LTE-to-UMTS handover initiation failure does not exist and inter-RAT incoming handover preparations fail.
 Traffic statistics  Customizing evaluation KPIs  SRVCC handover execution failure
 Allow users to customize KPIs for TopN evaluation based on traffic statistics.  Layer-1 demarcation: Identify the core network and non-core network problems.
 Internal CHRs
 Automatically filtering TopN cells  Layer-2 demarcation: Identify LTE air interface problems, air interface problems of
 External CHRs  Use the Wilson interval ranking algorithm to sort cells that meet the threshold the target inter-RAT cell, missing configurations of inter-RAT neighboring cells, and
conditions, and automatically identify TopN cells. NOHO setting problems.
 Alarm logs  Filtering TopN cells by proportion  Call drop caused by the SRVCC handover initiation failure
 Perform TopN calculation based on the user-specified proportion.  Call drop occurs because the A2 event is not reported.
 Operation logs  
Filtering TopN cells by absolute number Call drop occurs because the A2 event is reported but the B1/B2 event is not
 Provide a list of TopN cells. reported.
 Call drop occurs because the A2 and B1/B2 events are reported.
Principles
Performance Optimization
Root Cause Analysis
Suggestions
specifications
Downlink
Downlink Uplink weak Uplink
 Traffic statistics: 200 sites weak
interference coverage interference
coverage
x 7 days Air interface
External cell parameter
Resource capacity
problems
Reverse antenna
Parameter check
Missing configurations of neighboring

 External CHRs: 200 sites
Alarm check
TopN users
connection
Missing configurations of inter-

check
frequency neighboring cells


with 3 x 2 busy hours or
Edge weak coverage
Edge weak coverage
Uplink exception
Handover delay
Handover delay
Pilot pollution
PCIMod3
Others
100 GB
Uplink interference
cells
Downlink weak
Uplink weak
interference
coverage
coverage
Downlink
 Data processing
efficiency: 1 hour

Page28
OMStar VoLTE Accurate Optimization (SRVCC Theme) – Prepara-
tion Failure Result Parsing
1. Import data.
2. Use the VoLTE solution to create tasks, set running

parameters, and select handover preparation scenarios.
1. Identify TopN cells based on KPIs and evaluate 2. Demarcate and locate handover preparation
LTE-to-GSM/LTE-to-UMTS handover preparation problems, and drill down to inter-RAT neighboring
failures. cell problems.
3. Evaluate handover preparation KPIs and filter TopN cells.
4. Display analysis results of TopN cells with handover

3. Identify resource capacity problems and collect 4. Perform parameter check and alarm check, and
preparation failures.
statistics on daily cell resources during busy generate operation logs and optimization
(2) Cell hours. suggestions.
classification

5. Display the MR statistics chart. 6. Generate the one-click report. The report contains four
parts: evaluation, basic check, problem demarcation, and
suggestion.

Page29
OMStar VoLTE Accurate Optimization (SRVCC Theme) – Execu-
tion Failure Result Parsing
1. Import data.
2. Use the VoLTE solution to create tasks, set running

parameters, and select handover execution scenarios.
1. Identify TopN cells based on KPIs and evaluate 2. Demarcate and locate handover execution problems, and
LTE-to-GSM/LTE-to-UMTS handover execution drill down to LTE air interface problems and target inter-
failures. RAT cell problems.
3. Evaluate handover execution KPIs and filter TopN cells.
4. Display analysis results of TopN cells with handover 4. Perform parameter check and alarm check, and generate
3. Identify resource capacity problems and collect
execution failures. operation logs and optimization suggestions.
statistics on daily cell resources during busy
(2) Cell hours.
classification
5. Generate optimization suggestions. 6. Call drops occur because SRVCC is not initiated in a timely manner.
Analyze the handover thresholds, missing configurations of inter-RAT
5. Display the MR statistics chart.
neighboring cells, NOHO setting problems of inter-RAT neighboring cells,
and suspicious neighboring cell penalty handover.

Page30
OMStar VoLTE Problem Locating Report Parsing
1. Traffic statistics 3. Isolation 4. Root cause 5. Optimization
2. Basic check
evaluation demarcation analysis suggestions
Reports of the four VoLTE features are similar and all the reports consist of five parts. The following uses the call drop feature as an example.
Co
nte
nts
2
5
3
First page: report contents. You can access detailed information by clicking the
hyperlinks.
Traffic statistics evaluation: Display KPIs of TopN cells.
Basic check: Display parameter check, alarm check, and external cell parameter
consistency check results.
Isolation demarcation: Display the layer-1 and layer-2 problem categories. 4
Root cause analysis: Display root causes of air interface problems, neighboring
cell problems, and resource problems.
Optimization suggestions: Provide optimization suggestions and related
optimization commands for each type of root cause.

Page31
Contents
4 Tool Introduction
5 Specific Cases

Page32
VoLTE Problem Locating (Access Theme) – Case
Problem description: Optimization mode application effect:
 According to the user feedback, the number of voice service connection setup failures in cells at the DM site of  Optimization suggestions obtained from the OMStar are as
h819190 Xiacheng Changyun logistics is larger than that in cells at other sites. This situation needs to be optimized.
Import the DM site data to the OMStar tool for analysis. According to the statistics and analysis on the service follows:
Solve the problem that the number of service connection
connection success rate in areas, the number of voice service connection setup failures in cell DM_3 of h819190
setup failures is large due to CN problems: Click the
Xiacheng Changyun logistics is larger than that at other sites. optimization suggestion tab on the OMStar to view the
optimization suggestions for each problem.
Analyze call drops Demarcate, Automatically
for accurate VoLTE locate, and generate
Collect configuration Import data to the optimization. analyze optimization Deliver optimization
data, traffic statistics, OMStar. problems. suggestions. suggestions.
CHRs, and MRs.
Optimizati
on
procedure 1 2 3 4 5 6 END
Problem analysis: Use the OMStar to locate and analyze the root causes. The analysis results are as follows.
Use the OMStar to analyze traffic statistics: According to the Use the OMStar to analyze MRs:
preliminary traffic statistics analysis, the number of E-RAB Deliver scripts according to the optimization suggestions on the
connection setup failures in cell DM_3 is larger. After further  According to the external CHR analysis, a dedicated bearer OMStar: According to the onsite situation, implement the
analyzing the E-RAB connection setup failures, find that the corresponding optimization suggestions, and observe cell KPIs.
setup request is initiated on the CN after the initial context is
number of failures on the CN reaches 1912, accounting for The access success rate in beta area is increased from 99.64% to
91.7%, as shown in the following figure. successfully set up. However, the E-RAB ID of the dedicated 99.73%.
bearer is the same as that of the default bearer. The message
replied by the eNodeB to the bearer setup request contains
the cause value "Multi-ERAB-ID-Instance", leading to E-RAB
conflicts. Therefore, the E-RAB connection setup fails.
 According to the data analysis on the RAN side, the E-RAB
connection setup fails due to errors on the CN. To solve this
problem, CN personnel need to check, analyze, and resolve
the conflict between the E-RAB ID of the dedicated bearer and
that of the default bearer.

Page33
VoLTE Problem Locating (Call Drop Theme) – Case
 According to the user feedback, the call drop rates in cells 1 and 3 at site H are higher than those in cells at other sites  Optimization suggestions obtained from the OMStar are
from October 21 to 26. This situation needs to be optimized to reduce the call drop rate. Import the H site data to the as follows:
OMStar for analysis. According to statistics on the voice service call drop rate, the call drop rate in cells 1 and 3 at site Solve the mod 3 and uplink power control problems: Click the
optimization suggestion tab on the OMStar to view the optimization
H is higher than that in cells at other sites from October 21 to 26.
suggestions for each problem:
Analyze call drops Demarcate, Automatically
Collect configuration Import data to the for accurate VoLTE locate, and generate
data, traffic statistics, OMStar. optimization. analyze optimization Deliver optimization
CHRs, and MRs. problems. suggestions. suggestions.
Optimizati
on
procedure 1 2 3 4 5 6 End
Use the OMStar to analyze traffic statistics: According Use the OMStar to analyze MRs: Associate MRs over the Deliver scripts according to the optimization suggestions on the
to the statistics on the cause values of abnormal air interface, and analyze call drops, air interface coverage OMStar: According to the onsite situation, implement the
release in cells at site H, cell problems are mainly L.E- problems, and interference problems. corresponding optimization suggestions, and observe cell KPIs. The
RAB.AbnormRel.Radio.VoIP. The KPI exception is average call drop rate is decreased from 0.090% to 0.067% after the
mainly caused by faults on the RAN side. implementation.
Downlink PCI mod 3 interference
Uplink resynchronization fails. Uplink power control problems
RLC reaches the maximum number of
retransmission times.

Page34
VoLTE Problem Locating (Voice Quality Theme) – Case
 According to the user feedback, the ratio of poor voice quality of Hangzhou Mobile is high at site SM in h818780 Huafeng  Optimization suggestions obtained from the OMStar are as
Industrial Park. This situation needs to be optimized. Import the SM site data to the OMStar for analysis. According to the analysis, follows:
the ratio of poor voice quality at site SM is higher than that at other sites. Solve the poor quality problems and implement optimization
Analyze call drops for Demarcate, locate, Automatically suggestions: Click the optimization suggestion tab on the
Collect configuration Import data to the accurate VoLTE and analyze generate optimization
data, traffic statistics, OMStar.
Deliver optimization OMStar to view the optimization suggestions for each
optimization. problems. suggestions.
suggestions. problem.
CHRs, and MRs.
Optimizati
on
procedure 1 2 3 4 5 6 END
Problem analysis: Use the OMStar to locate and analyze the root causes. The analysis results are as follows. Deliver scripts according to the optimization suggestions on
Use the OMStar to analyze MRs: Analyze and locate air interface the OMStar: According to the onsite situation, implement the
Root cause analysis: According to the analysis performed using the problems based on MRs and find the following problems: (1) uplink corresponding optimization suggestions, and observe cell
OMStar, all poor voice quality problems at site SM are reflected by weak coverage/power control problems; (2) missing configurations KPIs. The ratio of poor voice quality is decreased from 3.6%
the uplink and downlink air interface packet loss rate, as shown in of neighboring cells, as shown in the following figure.
the following figure. to 1.5%.
Use the OMStar to analyze CHRs: Air interface problems in cells 1

and 3 are mainly caused by excessive RLC segmentation and low
BSR scheduling priority (high PUSCH DTX ratio), as shown in the
Locate air interface problems through the
following figure. CHR and MR association analysis on the
OMStar.

Page35
VoLTE Problem Locating (SRVCC Theme) – Case
 SRVCC handover preparation and execution failures occur at the Baianju site on the Shangtang road. This situation  Optimization suggestions obtained from the OMStar are as follows:
needs to be optimized. Import the site data to the OMStar for analysis. Analyze the site traffic statistics generated from Implement optimization suggestions on SRVCC handover
10:00 to 16:00 on November 5. The KPI analysis shows that SRVCC handover preparation and execution failures preparation and execution failures: Click the optimization
occur in cell 1 at the site (Baianju SFDM site on the Shangtang road). suggestion tab on the OMStar to view the optimization
suggestions for each problem.
Collect configuration Import data to the Analyze call drops for Demarcate, locate, Automatically
accurate VoLTE Deliver optimization
data, traffic statistics, OMStar. and analyze generate
CHRs, and MRs. optimization. suggestions.
problems. optimization
Optimizati suggestions.
on
procedure
1 2 3 4 5 6 END
Root cause analysis: According to the analysis performed Use the OMStar to analyze CHRs: According to the analysis results of the
SRVCC handover execution failures, 64 failures are caused by GSM air
using the OMStar, SRVCC handover preparation and
interface problems, and 12 failures are caused by LTE air interface
execution failures occur at the Baianju SFDM site on the problems, as shown in the following figure.
Shangtang road, as shown in the following figure. Deliver scripts according to the optimization suggestions on the OMStar:
According to the onsite situation, implement the corresponding optimization
Handover preparation suggestions, and observe cell KPIs. The SRVCC handover preparation
success rate success rate is increased from 93.7% to 97.4%. The SRVCC handover
execution success rate is increased from 90% to 98.2%.
Handover execution
success rate
Use the OMStar to analyze traffic statistics: According to the 1. According to the analysis of external CHRs, it is found that the
preliminary analysis result of the SRVCC handover preparation failures, air interface has the following problems: uplink weak coverage,
7 failures are caused because the GERAN system does not respond, downlink weak coverage, and missing configurations of
accounting for 30%. 16 failures are caused due to GERAN system neighboring cells.
response preparation failures, accounting for 70%, as shown in the 2. A site is an indoor distributed site. Parameters and neighboring
following figure.
cells need to be preferentially adjusted. In this case, adjust the
B2 threshold and add neighboring cells that are not configured.

Page36
Thank You
www.huawei.com

Page37

Solution-Based VoLTE Technical Training Slide V1.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Solution-Based VoLTE Technical Training Slide V1.0

Uploaded by

Copyright:

Available Formats

Solution-based VoLTE Technical

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

For operators, they hope to quickly find network

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Call History Record Data sources include CHRs, MRs, traffic

Evaluate KPIs Four evaluation

Generate optimization Parameter

HUAWEI TECHNOLOGIES CO., LTD.

TopN cell Heavy CPU load

Enter the destination number and press the dialing key.

Press the Hear the

Evaluation RRC Setup Process

E-RAB Setup Req

Call RRC Reconfiguration

Integrity Start the Connect Ack

SRVCC success rate

HUAWEI TECHNOLOGIES CO., LTD.

E-RAB Setup Reponse

2. Voice call drop rate

HUAWEI TECHNOLOGIES CO., LTD.

E-RAB Setup Req

E-RAB Setup Req

RRC Reconfiguration •Downlink packet loss rate =

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Uplink and L.Voice.VQI.UL.Bad.Times Number of times that uplink voice

Number of times that downlink voice

Number of times that downlink voice

Number of times that downlink voice

HUAWEI TECHNOLOGIES CO., LTD.

Find all MRs related to each CHR using the

HUAWEI TECHNOLOGIES CO., LTD.

Provide the distribution of cell-level

Analyze the problem symptoms.

Provide detailed problem cause

HUAWEI TECHNOLOGIES CO., LTD.

power control on the signal. : maximum transmit power of a UE

 The uplink weak coverage or poor quality is identified

 TF (i ) : TF power spectrum offset relative to the PUSCH

According to 3GPP TS 36.213, uplink power control is classified

example, the PUSCH transmit power is related to the

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

3. Enable the following MML switches:

Operation log The data source must be an .opt log file. No

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Missing configurations of neighboring cells

Missing configurations of inter-frequency

Uplink power control problems

 External CHRs: 200 sites with

Intensive weak coverage

Intensive weak coverage

Edge weak coverage

HUAWEI TECHNOLOGIES CO., LTD.

2. Use the VoLTE solution to create tasks, set operation

3. Evaluate KPIs and filter out TopN cells with access

3. Identify resource capacity problems and collect