Professional Documents
Culture Documents
1 Background
2 Technical Principle
3 Application Scenario
4 Tool Introduction
5 Case Study
weak-signal
difficult to access
...
Call drop
Without voice
quality evaluation
system
???
VoLTE
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
1 Background
2 Technical Principle
3 Application Scenario
4 Tool Introduction
5 Case Study
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
Uplink Serving Cell
from the MME CHR, SEQ, Nastar are used Internal and External
Press Hearing
From Dial Key To ringing A
RRC Con Req
Service Request
CSSR Authentication
RRC Reconfiguration
“Whether the call will be interrupted Voice Traffic Drop Rate E-RAB Setup Reponse
180 Ringing
B
Connect
Ring
Beginnin Ending Connect Ack
To
Integrality
D
“Can the other side hear me clearly?” The Rate for Poor Uplink MR(A2)
Voice Quality Indicator RRC Reconfiguration
MR(B2/B1)
“Can I hear the other side clearly?” The Rate for Poor Downlink HO Require
UE Context Release
E
SRVCC Success Rate
No LTE coverage and need to keep
talking. MT UE
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-
SRVCC PS to CS Request
eSRVCC
SRVCC PS to CS Response RAB.NormRel.QCI.1)] *100%
HO Command
Mobility from
Eutran Command
SRVCC PS to CS Complete Ack
• 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
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
SRVCC PS to CS Request
eSRVCC
SRVCC PS to CS Response • L2G HO Prepare Success Ratio
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 • 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.
Jitte
r
Dela Temporal Non-linear Linear
y
…… Processing Transforms Estimator VQI
BER
Bad Poor Accept Good Excellent L.Voice.VQI.UL.Excellent.Times Times of uplink Excellent voice quality
Decision VQI<= VQIBadThd VQIPoorThd <VQI<= VQIGoodThd <VQI<= VQI> VQIExcellentThd
Threshold VQIBadThd <VQI<= VQIGoodThd VQIExcellentThd L.Voice.VQI.UL.Good.Times Times of uplink good voice quality
VQIPoorThd
Uplink and
Downlink L.Voice.VQI.UL.Bad.Times Times of uplink bad voice quality
Voice
Quality
L.Voice.VQI.DL.Excellent.Times Times of downlink Excellent voice quality
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
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 Configuration ➢ PCI is the same in the neighbor cell list: Judged as PCI confusion
of Intra(Inter) Weak coverage Ultra Long ➢ Configured neighbor cell relationship but it does not handover even if matching the HO
Frequency neighbor weak
cell problem condition: Judged as Handover delay
identification coverage
➢ The distance from serving cell is too far: Judged as Ultra overshooting weak coverage
➢ 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
1 Background
2 Technical Principle
3 Application Scenario
4 Tool Introduction
5 Case Study
Adaptable Scenario
Feature Data Checking Rule Must
1 Background
2 Technical Principle
3 Application Scenario
4 Tool Introduction
5 Case Study
Call Drop
Analysis
VoLTE
Accurate
Access SRVCC
Optimization
Failure Handover
(Cell
Analysis Analysis
Level/User
Level)
Voice
Quality
Analysis
sites x 7 days
External cell parameter
Air interface
Resource capacity
problem
TopN subscribers
and operation log
Inter-RAT interference
Ov erlap interference
Edge weak coverage
control allowance
Uplink exception
sites, 3 days x 2 busy
Handov er delay
Handov er delay
Pilot pollution
allowance
PCIMod3
Others
Uplink interference
hours, and 100 GB
Downlink weak
Downlink weak
interference
coverage
Downlink
coverage
◼ Task analysis duration:
less than 1 hour
1. Import data.
4.Display param eter, alarm, operation log and suggestion. 5. Display the MR statistical chart in the access analysis process.
Principle
Performance
specifications
Downlink weak Downlink Uplink weak Uplink
◼ Performance data: 200 External cell parameter
coverage interference coverage interference
Resource capacity
TopN subscribers
Parameter check
problem
Inter-RAT interference
Ov erlap interference
Edge weak coverage
control allowance
Uplink exception
sites, 3 days x 2 busy
Handov er delay
Handov er delay
Pilot pollution
allowance
PCIMod3
Others
Uplink interference
hours, and 100 GB
Downlink weak
Uplink weak
interference
coverage
Downlink
coverage
◼ Task analysis duration:
less than 1 hour
1. Import data.
4.Display param eter, alarm, operation log and suggestion. 5. Display the MR statistical chart in the call drop process.
Principle
Performance
specifications
Downlink weak Downlink Uplink weak Uplink
◼ Performance data: 200 External cell parameter
coverage interference coverage interference
Resource capacity
TopN subscribers
Reverse antenna
Parameter check
problem
Inter-RAT interference
Ov erlap interference
Edge weak coverage
control allowance
Uplink exception
sites, 3 days x 2 busy
Handov er delay
Handov er delay
Pilot pollution
allowance
PCIMod3
Others
Uplink interference
hours, and 100 GB
Downlink weak
Downlink weak
interference
coverage
Downlink
coverage
◼ Task analysis duration:
less than 1 hour
1. Import data.
Principle
Performance
specifications
Downlink weak Downlink Uplink weak Uplink
◼ Performance data: 200 coverage interference coverage interference
sites x 7 days
External cell parameter
Air interface
Resource capacity
TopN subscribers
Reverse antenna
Parameter check
problem
Inter-RAT interference
Ov erlap interference
Edge weak coverage
control allowance
Uplink exception
Handov er delay
Handov er delay
Pilot pollution
allowance
PCIMod3
Others
hours, and 100 GB
Uplink interference
Downlink weak
Uplink weak
interference
coverage
Downlink
coverage
◼ Task analysis duration:
less than 1 hour
1. Import data.
1. Import data.
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.
2. Navigate to the VoLTE Accurate Optimization module on
the OMStar, create an analysis task, set required parameters,
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.
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.
◼ 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.
1 Background
2 Technical Principle
3 Application Scenario
4 Tool Introduction
5 Case Study
Optimization 2 3
procedures 1 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 optimization suggestions, collect data on the live network from
collected. The problem of this cell mainly reflects on 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
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: 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
after the CN sets up initial PDP optimization suggestions, collect data on the live network
find that the number of E-RAB connection setup failures due to CN problems is
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
up dedicated carriers. How ever, of cell counters. The analysis result indicates that the overall
the following figure.
the E-RAB ID of dedicated carriers access success rate in beta test areas increases from 99.64%
is consistent w ith that of default to 99.73% and the improvement proportion is 0.1%.
carriers. During carrier response,
an eNodeBcarries 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
w hether the E-RAB ID conflicts of
dedicated and default carriers on
the CN exist.
Optimization
procedures 1 2 3 4 5 6 END
Problem analysis: Locate the root cause on the OMStar. The analysis result is as follows:
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%.
Optimization
procedures
1 2 3 4 5 6 END
Problem analysis: Locate the root cause on the OMStar. The analysis result is as follows:
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
num ber 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
Handov er preparation
shown in the following figure. OMStar: According to onsite conditions, implement optimization
success rate
suggestions, collect data on the live network from November 17 to
Novem ber 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
Handov er execution success
increases from 90% to 98.2%. The SRVCC preparation success rate
rate im provement proportion is 4%. The SRVCC execution success rate
im provement proportion is 8.2%.