RF Network Planning and Optimization Service VOLTE

RF Network Planning and Optimization Service V100R007
Delivery Training Package (VOLTE Accurate Optimization)
HUAWEI TECHNOLOGIES CO., LTD.

Contents
1 Background
2 Technical Principle
3 Application Scenario
4 Tool Introduction
5 Case Study

Page2
Cannot Neglect VOLTE Voice Quality Problem
Users expected that has better voice quality
weak-signal
difficult to access
...
Call drop
Cannot hear clearly
The operators expect the fast detection network problem
Without voice
quality evaluation
system
VoLTE
???
2013 2014 2015->2016
Starts from 2013, more and more operators have officially released VoLTE Without Location What’s Without the
the voice quality problem delimitation voice
problem method quality problem
method

Page3
Contents
1 Background
4 Tool Introduction
5 Case Study

Page4
VoLTE Solution Introduction(1/3)
Start Data sources include: CHR, MR,
Call History Record Traffic Statistics, Alarm, Operation
Log, Configuration File,
Engineering Parameter, etc.
Input Data
KPI Evaluation 4 Evaluation 3 Dimensions

KPIs KPI/CHR/MR
Problem Delimitation Finding the root

causes of the
and locating problem?
Optimization Paramete Feature

r
suggestion Optimizati
on
Optimiz
ation
Neighb
or Cell
Optimiz
ation
End
RF Optimization

Page5
Problem Problem Root Causes Optimization
Evaluation Delimitation Location Suggestion
PRACH Usage
Radio Resource
Problem PRB Usage
Transmission Every kinds CCE/SRS Usage
Acquisition of non Problem of Resource
Access Successful Standard Cell eNB's Own Problems CPU Usage Capacity Expansion
Rate Problems Solution
Acquisition of the Maximum Users
Drop Rate
Top Cell
Deep Weak Feature/Parameter
Terminal Problems
Coverage Optimization
Edge Weak
VQI
Coverage Neighbor Cell
voice quality CN Problems Uplink Power Control Optimization
indicator
Coverage Problem
SRVCC Successful Abnormal Feature/Parameter/Al Problem Link Imbalance
Rate Data Analysis arm/Operation Log PCI Optimization
Checking Other Weak
Downlink Coverage
Air Interface Coverage Ultra Long Weak Power Optimization
Problems
Problem Coverage
No Primary Coverage Optimization
Data Resource for Downlink Serving Cell
（Calling ACP）
Interference Pilot Pollution
Problem Evaluation：
Problem Channel/Interference
Data Resource for Problem Overlapped
Traffic Statistics Uplink Checking
Delimitation: Traffic Statistics, Interference
Interference PCI MOD3
Internal and External CHR,
Problem Interference
Operation Log, Alarm and
HandOver Delay
Configuration File
Inter-System
Root Causes Location： Interference
External CHR, Intra-System
Interference
Configuration File,
HUAWEI TECHNOLOGIES CO., LTD. Engineering Parameter
Page6
User Service Detail Problem Problem Root Causes
Record Evaluation Delimitation Location
Complaint
Acquisition Deep Weak
Radio Resource Coverage
Problem Edge Weak
Coverage
Uplink Power Control
Transmission
Complaint Problem
Coverage Problem
Abnormal SDR Problem Link Imbalance
Time TMSI Analysis
Acquisition
eNB's Own
User Info.
Other Weak
eNodeB Problems Downlink Coverage
Complaint Name Coverage Ultra Long Weak
Content SDR Problem Coverage
Terminal Problems
TIME Segmentation No Primary
Downlink Serving Cell
Interference Pilot Pollution
Complaint CN Problems Problem
Number Overlapped
Uplink Interference
Air Interface Interference PCI MOD3
Problems Interference
Problem
 According to the complaint user’s IMSI HandOver Delay
Inter-System
and complaint time, the details of Data Resource for Data Resource for Root Causes Interference
Intra-System
complaint calls (eNB, Problem Evaluation： Problem Delimitation: Location: Interference
TMSI/MMEUES1APID, TIME) which are Internal and External Traffic Statistics, External CHR,
from the MME CHR, SEQ, Nastar are used CHR Internal and External
to analyze the causes of abnormal call CHR
SDR: Service Detail Record

Page7
VoLTE Evaluation KPI
User Experience Evaluation KPI Call Flow
Accessibility
Enter the other side number, press the dial key

MO UE eNodeB MME SGW PGW IMS MT UE
Press Hearing
From Dial Key To ringing A
RRC Con Req
RRC Setup Process
Service Request
CSSR Authentication
“Is the phone connected?" (call setup success rate)

Modify Bearer Request/Reponse
E-RAB Setup Req

(QCI=5)
Call RRC Reconfiguration
Hearing Ending Access

Continuity
E-RAB Setup Reponse

From Ringing To the Call Invite
E-RAB Setup Req
(QCI=1)
RRC Reconfiguration
“Whether the call will be interrupted Voice Traffic Drop Rate E-RAB Setup Reponse
during the call? ” Create Bearer Request/Reponse
180 Ringing
B
Connect
Ring
Beginnin Ending Connect Ack
From To C
Integrality
g the Call the Call Talking

Talking
D
“Can the other side hear me clearly?” The Rate for Poor Uplink MR(A2)
Voice Quality Indicator RRC Reconfiguration
“Can I hear the other side clearly?”

MR(B2/B1)
The Rate for Poor Downlink HO Require
Voice Quality Indicator eSRVCC

SRVCC PS to CS Request
SRVCC PS to CS Response
HO Command
Mobility from
Eutran Command
SRVCC PS to CS Complete Ack
Mobility
UE Context Release
E
SRVCC Success Rate
No LTE coverage and need to keep
talking. MT UE

Page8
VoLTE Index Calculation Principle
1、Service Access Success Rate
MO UE eNodeB MME SGW PGW IMS MT UE
A
RRC Con Req
• RRC_SSR (RRC Setup Success Rate) = (L.RRC.ConnReq.Succ/L.RRC.ConnReq.Att)
RRC Setup Process
Service Request
*100%
Authentication
Modify Bearer Request/Reponse • S1_SIG_SSR (S1 Signaling Connection Setup Success

E-RAB Setup Req
(QCI=5)
Rate)=(L.S1Sig.ConnEst.Succ/L.S1Sig.ConnEst.Att) *100%
Access
E-RAB Setup Reponse
Invite
• eRAB Setup Success Rate for VoLTE Service = (L.E-RAB.SuccEst.QCI.1/L.E-RAB.
E-RAB Setup Req
(QCI=1)
AttEst.QCI.1) * ( L.E-RAB.SuccEst.QCI.5/ L.E-RAB.AttEst.QCI.5) *100%
RRC Reconfiguration
E-RAB Setup Reponse • Call Setup Success Rate For VOLTE Service = RRC_SSR*S1_SIG_SSR* eRAB
Create Bearer Request/Reponse
180 Ringing
Setup Success Rate *100%
B
Connect
Ring
Connect Ack
C
Talking
Talking
2、Service Drop Rate
D
MR(A2)
RRC Reconfiguration
• Drop Rate（QCI=1）=
MR(B2/B1)
HO Require [L.E-RAB.AbnormRel.QCI.1 / (L.E-RAB.AbnormRel.QCI.1 + L.E-
eSRVCC
SRVCC PS to CS Response RAB.NormRel.QCI.1)] *100%
HO Command
Mobility from
Eutran Command • Drop Rate（QCI=2）=
E
UE Context Release
[L.E-RAB.AbnormRel.QCI.2 / (L.E-RAB.AbnormRel.QCI.2 + L.E-
RAB.NormRel.QCI.2)] *100%
MT UE
Note：The formula can also be user-defined according to the project requirement.

Page9
VoLTE Index Calculation Principle
3、Uplink/Downlink poor Voice Quality Rate
MO UE eNodeB MME SGW PGW IMS MT UE • Uplink poor Voice Quality Rate
A
RRC Con Req
=(Uplink Bad+Poor)/(Uplink Excellent+Good+Accept+Poor+Bad)
RRC Setup Process
Service Request • Downlink poor Voice Quality Rate

Authentication
Modify Bearer Request/Reponse

=(Downlink Bad+Poor)/(Downlink Excellent+Good+Accept+Poor+Bad)
•
E-RAB Setup Req
(QCI=5) Uplink Packet Loss Ratio
Access
E-RAB Setup Reponse
=L.Traffic.UL.PktLoss.Loss.QCI.1/L.Traffic.UL.PktLoss.Tot.QCI.1
•
Invite
E-RAB Setup Req Downlink Packet Loss Ratio
(QCI=1)
RRC Reconfiguration =L.Traffic.DL.PktUuLoss.Loss.QCI.1/L.Traffic.DL.PktUuLoss.Tot.QCI.1

E-RAB Setup Reponse
Create Bearer Request/Reponse 4、 SRVCC Success Ratio
B
180 Ringing • L2U HO Prepare Success Ratio：
Connect
Ring
C
Connect Ack L.IRATHO.SRVCC.E2W.ExecAttOut/L.IRATHO.SRVCC.E2W.PrepAttOut
Talking
Talking • L2U HO Execute Success Ratio：
D
MR(A2) (L.IRATHO.SRVCC.E2W.ExecSuccOut-L.IRATHO.SRVCC.E2W.MMEAbnormRsp)
RRC Reconfiguration
MR(B2/B1)
HO Require /L.IRATHO.SRVCC.E2W.ExecAttOut
eSRVCC
SRVCC PS to CS Response • L2G HO Prepare Success Ratio
HO Command
Mobility from
Eutran Command L.IRATHO.SRVCC.E2G.ExecAttOut/L.IRATHO.SRVCC.E2G.PrepAttOut
E
UE Context Release • L2G HO Execute Success Ratio
(L.IRATHO.SRVCC.E2G.ExecSuccOut- L.IRATHO.SRVCC.E2G.MMEAbnormRsp) /
MT UE
L.IRATHO.SRVCC.E2G.ExecAttOut
Note：The formula can also be user-defined according to the project requirement.

Page10
VoLTE Voice Quality Calculation Principle
 Principle: VQI (voice quality index) is Huawei's proprietary  VQI’s Difference From MOS:
voice quality evaluation criteria, it through a wireless air a) VQI is a reflection of the voice quality for air interface, and MOS
interface including jitter, delay, bit error rate, error reflects the voice quality of E2E.
frame rate, noise, speech coding mode, one-way audio times b) The accuracy of VQI dose not compare to the MOS absolute values, but
and handover times affect voice quality factors, fitting the VQI can keep the same trend with the MOS.
assessment out the current user call's voice quality. It can c) From the network side, we can monitor the cell and user’s voice
reflect the trend of the change of the quality of the voice quality is good or bad by the VQI in the real-time, so as to guide the
more accurately, so that the network operators can monitor direction of how to solve the air interface voice quality problems.
the quality of the network.
Jitte
r
Dela Temporal Non-linear Linear
……
y Processing Transforms Estimator VQI
BER

Page11
VoLTE VQI Calculation Principle
 According to the decision threshold, the VQI evaluation value is divided into 5 levels: VQIExcellentThd,VQIGoodThd,VQIAcceptThd,VQIPoorThd, VQIBadThd, the
practical value of the proposed value is 4/3/2/1, the value of the reference P.800 ITU-T for 5 levels of voice quality.
 The uplink and downlink VQI which is finally used as the cell voice quality statistics of the related performance index and the user’s performance monitoring
is shown as following table:
Bad Poor Accept Good Excellent L.Voice.VQI.UL.Excellent.Tim

Times of uplink Excellent voice quality
es
Decision VQI<= VQIBadThd VQIPoorThd VQIGoodThd <VQI<= VQI>
Threshold VQIBadThd <VQI<= <VQI<= VQIExcellentThd VQIExcellentThd L.Voice.VQI.UL.Good.Times Times of uplink good voice quality
VQIPoorThd VQIGoodThd
L.Voice.VQI.UL.Accept.Times Times of uplink accept voice quality

Comparison between VQI and packet loss rate:
L.Voice.VQI.UL.Poor.Times Times of uplink poor voice quality
Uplink
and
L.Voice.VQI.UL.Bad.Times Times of uplink bad voice quality
Downlink
Voice
Quality L.Voice.VQI.DL.Excellent.Tim
Times of downlink Excellent voice quality
es
L.Voice.VQI.DL.Good.Times Times of downlink good voice quality
L.Voice.VQI.DL.Accept.Times Times of downlink accept voice quality
L.Voice.VQI.DL.Poor.Times Times of downlink poor voice quality
L.Voice.VQI.DL.Bad.Times Times of downlink bad voice quality

Page12
The key technology of the VoLTE Issue Location
-- the Expert Method
Analysis the problem cell
Output the problem Distribution

with statistical significance
Analysis of surface phenomena

for the problem
The detailed reasons for the problem

and the location results are given.

Page13
–Uplink weak coverage location algorithm enhanced
Precondition for Uplink Weak Coverage:

 Traditional Solution:
The Serving Cell RSRP is less than dedicated Threshold1(e.g. default is -130dBm）&
Only according to the eNB received signal intensity and UL SINR is less than dedicated threshold(e.g. default is 0 dB) & UL Scheduled average
not considering the influence of power control on RB is less than dedicated threshold(e.g. default is 5)
signal.  If the PHR ≤ threshold(e.g. default is 0) and TA ≤ threshold(e.g. default is 2): Judged as deep
 Judging it is uplink weak coverage or poor weak coverage problem for UL
 If the PHR ≤ threshold(e.g. default is 0) and TA ≥ threshold(e.g. default is 10): Judged as
quality by the DMRS RSRP or SINR
edge weak coverage problem for UL
 Enhanced Solution:  If the threshold(e.g. default is 2) ≤ TA ≤ threshold(e.g. default is 10): Judged as
Judging the uplink weak coverage by analysis other weak coverage due to no power control allowance
power/schedule information/DMRS RSRP or SINR  If the PHR ≥ threshold(e.g. default is 6): Judged as power control problem for UL
 If the threshold(e.g. default is 0) ≤ PHR ≤ threshold(e.g. default is 6): Judged as
together and making the judgment more accurately.
other weak coverage with power control allowance
 Others: Judged as uplink Imbalance
PHR：Power Headroom Report

Page14
–Downlink weak coverage location algorithm enhanced
 Downlink Weak Coverage classification:
Missing Configuration of Intra(Inter) Frequency neighbor cell/PCI
Confusion /Forbidding HO/Abnormal Downlink/Ultra long weak
coverage/Edge weak coverage/Deep weak coverage/No Primary Serving Cell
Target Cell
serving cell
UE
 Preconditions for Downlink weak coverage：
PCI  1）The Serving Cell RSRP is less than dedicated Threshold (e.g. -140dBm）
HO Confusion  2） The Serving Cell RSRP is more than dedicated Threshold1(e.g. -140dBm） and less than dedicated
Abnormal
Delay Threshold2(e.g. -110dBm）but the CQI is less than dedicated threshold (e.g. 3)
DL
 Neighbor cell relationship has not been configured: Judged as Missing configuration
neighbor cell
Missing  PCI is the same in the neighbor cell list: Judged as PCI confusion
Configuration of Weak
Intra(Inter) Ultra Long  Configured neighbor cell relationship but it does not handover even if matching the HO
Frequency coverage weak
neighbor cell coverage condition: Judged as Handover delay
problem  The distance from serving cell is too far: Judged as Ultra long weak coverage
identification  The weak coverage is at the edge of the serving cell: Judged as Edge weak coverage
 The weak coverage is near to serving cell: Judged as Deep weak coverage
NO Edge weak
 Overlapped by multi cells and their RSRPs are not much difference: Judged as No primary
primary coverage
serving cell serving cell
Deep weak  Downlink path loss is higher uplink path loss obviously: Judged as Abnormal downlink path
coverage loss

Page15
–Downlink interference algorithm enhanced
 DL Interference problems classification:
Missing Configuration of Inter Frequency neighbor cell/HO
Delay for Inter Frequency/PCI Confusion /PCI MOD3
Interference/Pilot Pollution/Neighbor Cell Overlapped Serving Cell
Neighbor Cell1
Interference
UE
Missing
Configuration of
Inter Frequency
Neighbor Cell
Neighbor Cell2
HO Delay
Overlapped  RSRP of Serving Cell is Good and the Channel Quality is poor (The Serving Cell RSRP is
for Inter
Interference more than dedicated Threshold(e.g. -110dBm） but the CQI is less than dedicated threshold (e.g. 3))
Frequenc
y  It exists inter frequency neighbor cell and the RSRP/RSRQ of neighbor cell
Air Interface is better than the serving cell, but the neighbor cell does not exist in the
Problem Root
neighbor cell relationship list and it is judged as: Missing Configuration of
Causes
Identification inter frequency neighbor cell; But if it exists in the neighbor cell
relationship list but it has the same PCI, it will be judged as: PCI confusion
Pilot  It exists intra frequency neighbor cell which affects on serving cell very
Pollution PCI
Confusion much and it exists PCI MOD3 conflict. It judged as: PCI MOD3
 Or the pilot signal has no much difference from the signal of serving cell
PCI MOD3
Interference and it judged as: Pilot Pollution.

Page16
Contents
1 Background
4 Tool Introduction
5 Case Study

Page17
Data Collection and Adaptable Scenario
Data Collection
1. data: Internal/External CHR, Engineering Parameter, Traffic Statistics, Configuration Files
2. The trace server must be deployed.
3. MML switch is on
“Eutran Voip Support Switch”：MOD ENODEBALGOSWITCH: EUTRANVOIPSUPPORTSWITCH=ON;
“Voice quality monitoring algo switch”：MOD ENODEBALGOSWITCH: VQMALGOSWITCH=VQM_ALGO_SWITCH_ON;
“No sampling switch of internal CHR”：ADD CHROUTPUTMODE: ModeNo=1, ChrDetailCauseVal=1,
ChrHierOutMode=Level_1_Output, SamplingEnable=SamplingUnable;
4、CHR data collection(Please refer to the document of <OMStar_V500R012C00_LTE_Data_Collection_Guide.docx>)
Adaptable Scenario
Feature Data Checking Rule Must
External-CHR(MR) Log files, the file postfix is “.sig” Yes
Traffic Statistics Log files, the file postfix is ".mrf.gz" Yes
Engineering Parameter Table files, the file postfix is ".csv/.xlsx/.xls" Yes

positioned the VOLTE
Configuration Log files, the file postfix is ".xml" Yes
problem
Internal-CHR Table files, the file postfix is ".CHR.gz" Yes
Operation log Table files, the file postfix is ".opt" No
Alarm log Table files, the file postfix is ".csv" No

Page18
Contents
1 Background
4 Tool Introduction
5 Case Study

Page19
 Introduction to the VoLTE Accurate Optimization Function on the OMStar
— Panoramic Function
Call Drop
Analysis
VoLTE
Accurate
Access SRVCC
Optimization
Failure Handover
(Cell
Analysis Analysis
Level/User
Level)
Voice
Quality
Analysis

Page20
 Access Theme in VoLTE Accurate Optimization on the OMStar — Principle
Introduction
Data requirements  Two evaluation scenarios  RRC phase
 One is the access analysis scenario including the S1  Layer-1 Delimitation: Air interface, CN, resource, and
interface and one is the access analysis scenario excluding eNodeB problems are identified.
the S1 interface.  Layer-2 Delimitation: No response from UEs,
 Customized KPI evaluation
 Configuration data  We can customize voice and video KPIs for evaluating TopN
subscriber number limitation, flow control, and
resource allocation failure problems are identified.
cells based on performance data.
 Performance data  Automatically getting TopN cells
 E-RAB connection setup phase
 The Wilson interval ranking algorithm is used to sort the
 Internal CHR data cells that meet threshold requirements. TopN cells are
 Layer-1 Delimitation: CN, air interface, resource,
automatically identified. terminal, transmission, and eNodeB problems are
 External CHR data  getting TopN cells by proportion identified.
 TopN cells are obtained based on the access success rate  Layer-2 Delimitation: Problems related to incorrect
 Alarm log threshold specified by users configurations in security mode, intra-site handover
 getting TopN cells based on the absolute number of access conflicts, insufficient license resources, low uplink
 Operation log failures and downlink satisfaction rates, and the SRBRLC re-
 Specified TopN cells are provided. transmission times reaching the upper limit are
identified.
Principle
Performance
specifications
Downlink weak Downlink Uplink weak Uplink
 Performance data: 200 ZC root sequence check coverage interference coverage interference
Parameter, alarm check,
sites x 7 days
External cell parameter
Air interface
Resource capacity
problem
TopN subscribers
and operation log
Cell radius check
Other weak coverage without power control

Missing configuration of neighboring cells
Other power control problems with power

Missing configuration of inter-frequency
 External CHR data: 200
check
Uplink power control problem

Overly distant weak coverage
Other intra-RAT interference

In-depth weak coverage

No primary serving cell
Inter-RAT interference
Edge weak coverage
Edge weak coverage

Overlap interference
control allowance
sites, 2 days x 3 busy
neighboring cells
Uplink exception
Handover delay
Handover delay
Pilot pollution
allowance
PCIMod3
Others
Uplink interference
hours, and 100 GB
Downlink weak
Downlink weak
interference
Downlink
coverage
coverage
 Task analysis duration:
less than 1 hour

Page21
 Access Theme in VoLTE Accurate Optimization on the OMStar — Result
Interpretation
Theme analysis process Result interpretation on the GUI
1. Import data.
2. Navigate to the VoLTE Accurate Optimization module on

the OMStar, create an analysis task, set required parameters,
and select an evaluation scenario (voice and video).
2.1. Delimitate and locate access problems and drill down access
1. Identify Top N cells with access problems based on KPIs. problem categories and root causes based on layer-1
Delimitation results.
3. Perform KPI evaluation and obtain TopN cells with

access problems.
4. Provide task analysis results of TopN cells with access

problems.
2.2.Display root cause of video access, uplink and downlink
satisfaction and root cause of RF. 3.Display resource capacity problem and busy time static.
a. View check b. Delimitate c. Locate the
results of basic and classify root cause of
problems. problem cells. problem cells.
5. Provide optimization suggestions.
4.Display parameter, alarm, operation log and suggestion. 5. Display the MR statistical chart in the access analysis process.

Page22
 Call Drop Theme in VoLTE Accurate Optimization on the OMStar —
Principle Introduction
Data requirements  Two evaluation scenarios
 One is the analysis scenario including MMEs and one
is the analysis scenario excluding MMEs.  Call drop exception
 Customized KPI evaluation  Layer-1 Delimitation: Air interface, resource, CN,
 Configuration data  We can customize voice and video KPIs for evaluating transmission, and other problems are identified.
TopN cells based on performance data.
 Performance data  Automatically getting TopN cells
 Layer-2 Delimitation: The following problems are
 The Wilson interval ranking algorithm is used to sort
identified: no responses from UEs, SRB/DRB RLC re-
 Internal CHR data the cells that meet threshold requirements. TopN cells
are automatically identified. transmission times reaching the upper limit, uplink
 External CHR data  getting TopN cells by proportion resynchronization failures, handover process
 TopN cells are obtained based on the call drop rate exceptions, wireless resource overload, wireless
 Alarm log threshold specified by users resource preemption, transmission resource overload,
 getting TopN cells based on the absolute number of call and transmission resource preemption.
 Operation log drops
 Specified TopN cells are provided.
Principle
Performance
specifications
 Performance data: 200 External cell parameter
coverage interference coverage interference
sites x 7 days Air interface

Operation log check
Resource capacity
TopN subscribers
Parameter check
problem


Alarm check

check



Edge weak coverage
Edge weak coverage

control allowance
neighboring cells
Uplink exception
Handover delay
Handover delay
Pilot pollution
allowance
PCIMod3
Others
Uplink interference
hours, and 100 GB
Downlink weak
Uplink weak
interference
Downlink
coverage
coverage
less than 1 hour

Page23
 VoLTE Call Drop Analysis on the OMStar — Result Interpretation
1. Import data.

and select an evaluation scenario (voice and video).
1. Identify TopN cells with call drop problems based on KPIs. 2.1 Delimitate and locate call drop problems and drill down call drop
problem categories and root causes based on layer-1 Delimitation
results.
3. Perform call drop KPI evaluation and obtain TopN cells

with call drop problems.
4. Provide task analysis results of TopN cells with call

drop problems. 2.2 Display root cause of video call drop, abnormal release
and root cause of RF. 3.Display resource capacity problem and busy time static.
4.Display parameter, alarm, operation log and suggestion. 5. Display the MR statistical chart in the call drop process.

Page24
 VoLTE Voice Quality Analysis on the OMStar — Principle Introduction
Data requirements  Six evaluation scenarios  Poor downlink VQI

 Poor downlink voice quality, poor uplink voice quality,  Layer-1 Delimitation: Layers above eNodeB, eNodeB,
poor uplink & downlink voice quality, downlink and air interface problems are identified.
package loss rate, uplink package loss rate, and  Layer-2 Delimitation: Transmission, cell congestion,
 Configuration data uplink & downlink package loss rate packet loss, poor voice quality problems are identified.
 Customized KPI evaluation
 Performance data  We can customize KPIs for evaluating TopN cells
 Poor uplink VQI
based on performance data.
 Layer-1 Delimitation: Layers above eNodeB, eNodeB,
 Automatically getting TopN cells
 Internal CHR data  The Wilson interval ranking algorithm is used to sort air interface, and terminal problems are identified.
the cells that meet threshold requirements. TopN cells  Layer-2 Delimitation: The following problems are
 External CHR data are automatically identified. identified: transmission, small and invalid IP packets,
 getting TopN cells by proportion cell congestion, insufficient PUSCH resources,
 Alarm log  TopN cells are obtained based on the voice quality insufficient PUCCH resources, low SR scheduling
threshold specified by users. priority, low BSR priority, packet loss, and poor voice
 Operation log  getting TopN cells based on the absolute number quality.
 Specified TopN cells are provided.
Principle
Performance
specifications
Resource capacity
TopN subscribers
Reverse antenna
Parameter check
problem


Alarm check

connection
check



Edge weak coverage
Edge weak coverage

control allowance
neighboring cells
Uplink exception
Handover delay
Handover delay
Pilot pollution
allowance
PCIMod3
Others
Uplink interference
hours, and 100 GB
Downlink weak
Downlink weak
interference
Downlink
coverage
coverage
less than 1 hour

Page25
 VoLTE Voice Quality Analysis on the OMStar — Result Interpretation
1. Import data.
2. Navigate to the VoLTE Accurate Optimization module on the

OMStar, create an analysis task, set required parameters, and
select an evaluation scenario (poor uplink and downlink voice
quality and packet loss). 2. Delimitate and locate poor voice quality problems and drill down
1. Identify TopN cells with poor voice quality problems based on
poor voice quality problem categories and root causes based on
KPIs.
layer-1 Delimitation results.
3. Perform KPI evaluation related to poor uplink and downlink

voice quality and obtain TopN cells with poor voice quality
problems.
4. Provide task analysis results of TopN cells with poor voice

quality problems.
3. Identify resource capacity problems and collect information 4. Perform the parameter check and alarm check, generate operation
about busy-hour resources each day in a cell. logs, and provide optimization suggestions.
a. View check b. Delimitate and c. Locate the root
results of basic classify problem cause of problem
problems. cells. cells.

5. Display the MR statistical chart in the voice quality analysis 6. Generate one-click reports, including the following five parts:
process. evaluation, basic check, Delimitation, locating, and suggestion.

Page26
 VoLTE SRVCC Analysis on the OMStar — Principle Introduction
Data requirements  Six evaluation scenarios
 LTE-to-GSM handover preparation failure, LTE-to-GSM
handover execution identification, and call drop due to non-  SRVCC handover preparation failure
initiated LTE-to-GSM handovers  Layer-1 Delimitation: Problems related to CN signaling failures,
 LTE-to-UMTS handover preparation failure, LTE-to-UMTS no inter-RAT responses, and inter-RAT handover preparation
failures are identified.
 Configuration data handover execution identification, and call drop due to non-
initiated LTE-to-UMTS handovers  Layer-2 Delimitation: Unavailable inter-RAT identities and
 Customized KPI evaluation possible causes of inter-RAT handover incoming preparation
 Performance data  We can customize KPIs for evaluating TopN cells based on failures are identified.
performance data.  SRVCC handover execution failure
 Internal CHR data  Automatically getting TopN cells  Layer-1 Delimitation: CN and non-CN problems are identified.
 The Wilson interval ranking algorithm is used to sort the cells  Layer-2 Delimitation: Problems related to LTE air interfaces, air
interfaces in inter-RAT target cells, missing configurations of
 External CHR data that meet threshold requirements. TopN cells are automatically
inter-RAT neighboring cells, and NOHO configurations are
identified.
 identified.
 Alarm log getting TopN cells by proportion
 TopN cells are obtained based on the proportion specified by  Call drop due to non-initiated SRVCC handovers
users.  Call drop due to no reported A2
 Operation log  getting TopN cells based on the absolute number  Call drop due to reported A2 but no B1/B2
 Specified TopN cells are provided.  Call drop due to reported A2 and B1/B2
Principle
Performance
specifications
Resource capacity
TopN subscribers
Reverse antenna
Parameter check
problem


Alarm check

connection
check



Edge weak coverage
Edge weak coverage

control allowance
neighboring cells
Uplink exception
Handover delay
Handover delay
Pilot pollution
allowance
PCIMod3
Others
hours, and 100 GB
Uplink interference
Downlink weak
Uplink weak
interference
Downlink
coverage
coverage
less than 1 hour

Page27
 VoLTE SRVCC Analysis on the OMStar — Interpretation of Preparation
Failure Results
1. Import data.

and select the handover preparation scenario. 1. Identify TopN cells with handover preparation problems based
on KPIs and evaluate handover preparation failures from LTE 2. Delimitate and locate handover preparation problems and drill
to GSM or from LTE to UMTS. down inter-RAT neighboring cell problems.
3. Perform KPI evaluation related to handover

preparations and obtain TopN cells with handover
preparation problems.
4. Provide task analysis results of TopN cells with

handover preparation problems. 3. Identify resource capacity problems and collect information 4. Perform the parameter check and alarm check, generate
about busy-hour resources each day in a cell. operation logs, and provide optimization suggestions.

5. Display the MR statistical chart in the handover preparation 6. Generate one-click reports, including the following five parts:

Page28
 VoLTE SRVCC Analysis on the OMStar — Result Interpretation
1. Import data.

and select the handover execution scenario. 2. Delimitate and locate handover execution problems and drill
1. Identify TopN cells with handover execution problems based
on KPIs and evaluate handover execution failures from LTE to down air interface and inter-RAT neighboring cell problems on
GSM or from LTE to UMTS. LTE networks.
3. Perform KPI evaluation related to handover executions

and obtain TopN cells with handover execution problems.

handover execution problems. 3. Identify resource capacity problems and collect information 4. Perform the parameter check and alarm check, generate
about busy-hour resources each day in a cell. operation logs, and provide optimization suggestions.


5. Display the MR statistical chart in the handover execution 6. Generate one-click reports, including the following five parts:

Page29
 VoLTE SRVCC Analysis on the OMStar — Result Interpretation
1. Import data.
The call drop caused by SRVCC runs with interpretation of SRVCC preparation or interpretation of
SRVCC execution. There is no independent entrance of call drop, so there is only the result of classify
problem cells and root cause of problem cells, but no evaluating result.
and select the handover execution scenario. 1.Delimitate and classify problem cells, including No A2, Exist A2 No B1/B2 and Exist A2 Exist B1/B2.
3. Perform KPI evaluation related to handover executions

and obtain TopN cells with handover execution problems.

handover execution problems. 2.Output HO threshold, missing inter-RAT neighboring cell,
problem of NOHO on inter-RAT neighboring cell and 3. Display the MR statistical chart in the
a. View check b. Delimitate c. Locate the suspected HO penalty neighboring cell. handover execution process.

Page30
 Report Result Interpretation of VoLTE Themes on the OMStar
1. Performance 3. Problem 4. Root cause 5. Optimization
2. Basic check
data evaluation Delimitation analysis suggestions
Generated reports of the four VoLTE features are similar. Each report consists of five parts. The call drop feature is used as an example.
Contents
2
5
3
 Home page: Displays the report directory. We can click the hyperlink
of an item to navigate to the related detail sheet.
① Performance data evaluation: Displays KPIs of TopN cells.
② Basic check: Displays results of the parameter check, alarm check,
and external cell parameter consistency check.
③ Problem Delimitation: Displays problem categories of layer-1 and
layer-2 Delimitation results. 4
④ Root cause analysis: Displays the root causes related to air
interface, neighboring cell, and resource problems.
⑤ Optimization suggestion: Based on each root cause, optimization
suggestions and related commands are provided.

Page31
 VoLTE Complaint Analysis on the OMStar – Principle Introduction
Voice quality SRVCC handover
Access theme Call drop theme
Data requirements theme theme
 Configuration data
 GSM/UMTS performance 1. Import the TMSI/S1AP list of complaint subscribers, specify site ranges and compliant time ranges,
and obtain data related call drops that meet other requirements.
data (optional and required
in handover themes)
 Internal CHR data
2. Based on calls of each subscriber, filter events one by one and obtain abnormal events.
 External CHR data
Principle
3. Identify SDRs(Service detail record) whose QCIs are 5 firstly and then identify QCI1. (But it can
identify QCI1 directly for voice quality and call drop themes.
Performance specifications
4. Delimitate problems. Identify air interface, transmission, resource, and CN problems from each
abnormal event.
 10 eNodeBs for a single
subscriber
5. Analyze root causes. Based on air interface problems of each abnormal event, identify root causes
 External CHR data: 1 hour related to uplink interference, uplink coverage, downlink interference, and downlink coverage, and
 Performance: 20 minutes provide optimization suggestions accordingly.
6. Drill down details and signaling processes of

7. Drill down raw event data of each CHR.
each CHR.

Page32
 VoLTE Complaint Analysis on the OMStar – Result Interpretation
Theme analysis process

Interpretation of results on the GUI
(Results of four themes are similar. The call drop theme is used as an example.)
GUI 1: Problem Delimitation

1. Import data. results
 Results are displayed by
theme and subscriber.
 Detailed Delimitation results
are classified into layer-1 and
layer-2 Delimitation.
2. Navigate to the VoLTE complaint analysis module  Problem categories and root
causes of each abnormal event
on the OMStar and create a complaint analysis task. are provided.
 Cells are correlated and Cell-
level handling suggestions are
Right-click the detailed CHR provided.
information to drill down
required information.
2. Import the list of complaint subscribers.

GUI 2: Detailed CHR
information
 Basic CHR information
 Detailed CHR fields
 Signaling process
 MR information
4. View analysis results.
 MR trend chart
a. Problem b. Detailed Right-click the detailed event

c. Raw event data to drill down required
Delimitation CHR information.
data
results information
GUI 3: Detailed event data

 Event summary
information
5. Provide optimization suggestions.  Detailed event data

Page33
Contents
1 Background
4 Tool Introduction
5 Case Study

Page34
VoLTE Accurate Optimization on the
OMStar — Call Drop
Problem Description: Application Effect of the Optimization Mode:
 The following optimization suggestions are obtained from the
 User feedback indicates that the call drop at Xiacheng Yangyun logistics site is higher than OMStar:
Resolve the PCI mod 3 conflict and uplink power control
that at other sites. Therefore, network optimization is required to reduce the call drop rate. problems: On the OMStar, click Suggestion and view
Data collected at this site is imported to the OMStar for analyzing the call drop rate of voice optimization suggestions related to each problem, as shown
in the following figure.
services.
Collect configuration Perform call drop

Delimitate and Automatically Deliver
data, performance Import the collected analysis using the
locate detailed generate optimization optimization
data, CHR data, and data to the OMStar. VoLTE accurate
problems. suggestions. suggestions.
MR data. optimization theme.
Optimization
procedures 1 2 3 4 5 6 END
Problem analysis: Locate the root cause on the OMStar. The analysis result is as follows:
Use performance data for analysis on the OMStar: The Deliver scripts based on optimization suggestions generated
value of carrying abnormal release causes of a cell is on the OMStar: According to onsite conditions, implement
Use MR data for analysis on the OMStar: After
collected. The problem of this cell mainly reflects on optimization suggestions, collect data on the live network from
correlating MRs over the air interface and analyzing
L.E- RAB.AbnormRel.Radio.VoIP. The counter November 2 to November 6, and observe the changes of cell
abnormal call drop problems, identify air interface
exception is caused by radio errors, including: counters. The analysis result indicates that the average call
coverage problems and interference problems due to
drop rate reduces from 0.09% to 0.067% after optimization and
 Uplink Resynchronization Failure call drops, including:
the improvement proportion is 25.6%.
 RLC Retransmission Number Reaching the Maximum  Uplink PCI mod 3 interference
Limit  Uplink power control problem

Page35
VoLTE Accurate Optimization — Access
 User feedback indicates that the number of voice service access failures from October 21 to October 26 in cell D_3 at Xiacheng
Yangyun logistics site is higher than that at other cells. Therefore, network optimization is required. Data collected at this site  The following optimization suggestions are obtained from the OMStar:
is imported to the OMStar for analyzing the call success rate of this site. The analysis result indicates that the number of voice
service access failures in cell D_3 is 18 and that in other cells is less than 5. Resolve the problem of a large number of access failures caused by
the CN: On the OMStar, click Suggestion and view optimization
suggestions related to each problem, as shown in the following
figure.
Collect configuration Perform access Delimitate and

Automatically Deliver
data, performance Import the collected analysis using the locate
generate optimization optimization
data, CHR data, and data to the OMStar. VoLTE accurate detailed
suggestions. suggestions.
MR data. optimization theme. problems.
Optimization
Use performance data for analysis on the OMStar: Based on the performance data, Use MR data for analysis on the
perform preliminary analysis and find that the number of E-RAB connection setup Deliver scripts based on optimization suggestions generated
OMStar: The analysis result based
failures is large. Further analyze the result of E-RAB connection setup failures and on external CHR data indicates that
on the OMStar: According to onsite conditions, implement
find that the number of E-RAB connection setup failures due to CN problems is after the CN sets up initial PDP optimization suggestions, collect data on the live network
1912 and the proportion of CN problems in total problems is 91.7%, as shown in contexts successfully, the CN sets from November 2 to November 6, and observe the changes
the following figure. up dedicated carriers. However, of cell counters. The analysis result indicates that the overall
the E-RAB ID of dedicated carriers access success rate in beta test areas increases from 99.64%
is consistent with that of default to 99.73% and the improvement proportion is 0.1%.
carriers. During carrier response,
an eNodeB carries a cause value
Multi-ERAB-ID-Instance. As a
result, the E-RAB setup fails due to
E-RAB conflicts.
Based on analysis of data at the
RAN side, the result indicates that
the E-RAB setup failure is caused
by the CN errors. This problem can
be resolved by determining
whether the E-RAB ID conflicts of
dedicated and default carriers on
the CN exist.

Page36
VoLTE Accurate Optimization — Voice Quality
 User feedback indicates that the poor voice quality problems exist at Hua Feng Industrial Park site of Hangzhou Mobile  The following optimization suggestions are obtained from the OMStar:
from November 2 to November 6. Therefore, network optimization is required. Data collected at this site is imported to the Resolve the poor voice quality problems: On the OMStar, click
OMStar for analysis. The analysis result indicates that the number of poor voice quality problems at this site is 34 and Suggestion and view optimization suggestions related to each
that at other sites is less than 5. problem, as shown in the following figure.
Collect configuration Perform voice quality

Delimitate and Automatically generate Deliver
data, performance Import the collected analysis using the
locate detailed optimization optimization
data, CHR data, and data to the OMStar. VoLTE accurate
problems. suggestions. suggestions.
MR data. optimization theme.
Optimization
Analyze the root cause: The analysis result indicates that all poor Use MR data for analysis on the OMStar: Based on the MR
voice quality problems at this site are caused by the uplink and data, after analyzing air interface problems, find that the Deliver scripts based on optimization suggestions generated on the
downlink packet loss rates over the air interface, as shown in the following problems exist: uplink weak coverage, power OMStar: According to onsite conditions, implement optimization
following figure. control, and missing configurations of neighboring cells, as suggestions, collect data on the live network from November 9 to
shown in the following figure. November 10, and observe the changes of cell counters. The
analysis result indicates that the proportion of poor voice quality
problems 16% to 5% in test areas). Currently, related parameters on
the entire network are modified. The proportion of poor voice
quality problems reduces from 3.6% to 1.5% and the improvement
proportion increases to 58.3%.
Use CHR data for analysis on the OMStar: Air interface

problems in cells 3 and 1 are caused by excessive RLC frame On the OMStar, CHR data and MR data are
segments and low BSR scheduling priorities (due to a high
PUSCH DTX proportion), as shown in the following figure.
correlated for locating RF errors.

Page37
VoLTE Accurate Optimization — SRVCC
 User feedback indicates that the SRVCC handover preparation failures and handover execution failures occur at Baianju  The following optimization suggestions are obtained from the
site on Shangtang road from November 10 to November 15. Therefore, network optimization is required. Data collected at OMStar:
this site is imported to the OMStar. Analyze the performance data collected at this site from 10 to 16 clock on November
15. The analysis indicates that the proportions of SRVCC handover preparation failures and SRVCC handover execution Resolve the SRVCC handover preparation failure and SRVCC
handover execution failure problems: On the OMStar, click
failures in SFDM cell at this site are about 87.8% and those in other cells are greater than 95%.
Suggestion and view optimization suggestions related to each
Collect configuration problem, as shown in the following figure.
Perform SRVCC analysis Delimitate and Automatically Deliver
data, performance Import the collected
using the VoLTE accurate locate detailed generate optimization optimization
data, CHR data, and data to the OMStar.
optimization theme. problems. suggestions. suggestions.
MR data.
Optimization
procedures
1 2 3 4 5 6 END
Analyze the root cause: The analysis result indicates that the
Use CHR data for analysis on the OMStar: The analysis result
SRVCC handover preparation failures and SRVCC handover
of SRVCC handover execution failures indicates that the
execution failures occur in cell SFDM at Baijuan site on
number of Delimitated GSM air interface problems is 64 and
Shangtang road, as shown in the following figure.
the number of Delimitated LTE air interface problems is 12, as
Deliver scripts based on optimization suggestions generated on the
shown in the following figure.
Handover preparation OMStar: According to onsite conditions, implement optimization
success rate
suggestions, collect data on the live network from November 17 to
November 22, and observe the changes of cell counters. The
analysis result indicates that: The SRVCC preparation success rate
increase from 93.7% to 97.4%. The SRVCC execution success rate
Handover execution success
increases from 90% to 98.2%. The SRVCC preparation success rate
rate improvement proportion is 4%. The SRVCC execution success rate
improvement proportion is 8.2%.
Use performance data for analysis on the OMStar: The

preliminary analysis result of SRVCC handover preparation 1. Analyze the external CHR data and find that the following
failures indicates that the number of response failures from the problems occur over the air interface: uplink weak
GERAN system is 7, and the proportion of this problem is 30%. coverage, downlink weak coverage, and missing
The number of GERAN system response preparation failures is 16, configurations of neighboring cells.
and the proportion of this problem is 70%. 2. This site an indoor distributed site, preferentially adjust
parameters and neighbor relationships. For example,
adjust the B2 threshold and add missing neighboring cells.

Page38
OMStar Tool and Related Documents
OMStar V50R12SPC200 Tool：

http://support.huawei.com/carrier/navi#col=software&detailId=PBI1-21611540&path=PBI1-
7851894/PBI1-21433538/PBI1-7854329/PBI1-21465981/PBI1-59728
Related documents for OMStar V50R12:

http://3ms.huawei.com/hi/index.php?app=group&mod=Core&act=showSectionData&gid=2028
955&id=1226935&l=en
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 39

VoLTE HDX Document
The Latest Released VoLTE Document MBB V1R7 Version Link:
http://pdm.huawei.com/Windchill/navigator/productcat/product/HuaweiDocBaseInf
oPage.html?&docnumber=OFFE00018917_TGL98EN&docoid=ext.huawei.huaweidoc.
HuaweiDoc:24336475796&docedition=F.2
Please download Today’s training document and Video from link:

http://3ms.huawei.com/hi/group/2692135/thread_5061193.html?mapId=5920699
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential 40

Thank You
www.huawei.com

Page41

RF Network Planning and Optimization Service VOLTE

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

RF Network Planning and Optimization Service VOLTE

Загружено:

Авторское право:

Доступные форматы

RF Network Planning and Optimization Service V100R007

Delivery Training Package (VOLTE Accurate Optimization)

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Cannot hear clearly

The operators expect the fast detection network problem

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

KPI Evaluation 4 Evaluation 3 Dimensions

Problem Delimitation Finding the root

Optimization Paramete Feature

HUAWEI TECHNOLOGIES CO., LTD.

to analyze the causes of abnormal call CHR

SDR: Service Detail Record

HUAWEI TECHNOLOGIES CO., LTD.

Enter the other side number, press the dial key

RRC Setup Process

“Is the phone connected?" (call setup success rate)

E-RAB Setup Req

Call RRC Reconfiguration

Hearing Ending Access

E-RAB Setup Reponse

during the call? ” Create Bearer Request/Reponse

g the Call the Call Talking

“Can I hear the other side clearly?”

Voice Quality Indicator eSRVCC

HUAWEI TECHNOLOGIES CO., LTD.

Modify Bearer Request/Reponse • S1_SIG_SSR (S1 Signaling Connection Setup Success

Note：The formula can also be user-defined according to the project requirement.

HUAWEI TECHNOLOGIES CO., LTD.

Service Request • Downlink poor Voice Quality Rate

Modify Bearer Request/Reponse

RRC Reconfiguration =L.Traffic.DL.PktUuLoss.Loss.QCI.1/L.Traffic.DL.PktUuLoss.Tot.QCI.1

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Bad Poor Accept Good Excellent L.Voice.VQI.UL.Excellent.Tim

L.Voice.VQI.UL.Accept.Times Times of uplink accept voice quality

L.Voice.VQI.DL.Good.Times Times of downlink good voice quality

L.Voice.VQI.DL.Accept.Times Times of downlink accept voice quality

L.Voice.VQI.DL.Poor.Times Times of downlink poor voice quality

L.Voice.VQI.DL.Bad.Times Times of downlink bad voice quality

HUAWEI TECHNOLOGIES CO., LTD.

Analysis the problem cell

Output the problem Distribution

Analysis of surface phenomena

The detailed reasons for the problem

HUAWEI TECHNOLOGIES CO., LTD.

Precondition for Uplink Weak Coverage:

PHR：Power Headroom Report

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

External-CHR(MR) Log files, the file postfix is “.sig” Yes

Traffic Statistics Log files, the file postfix is ".mrf.gz" Yes

Engineering Parameter Table files, the file postfix is ".csv/.xlsx/.xls" Yes

Operation log Table files, the file postfix is ".opt" No

Alarm log Table files, the file postfix is ".csv" No

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

HUAWEI TECHNOLOGIES CO., LTD.

Cell radius check

Other weak coverage without power control

Other power control problems with power