Академический Документы
Профессиональный Документы
Культура Документы
Code (0003)
Date 2015-11-3
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be within
the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either expressed or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Email: support@huawei.com
Keywords: Apple, iPhone, FDD, VoLTE, Call Drop, SRVCC, RRC Re-establishment Failure
Saudi Operator Z need commercialize VoLTE service as first operator in Middle East Region, which will greatly
promote itself brand in market. As iPhone series smart phones are the most popular terminals in living network, if Z
need commercialize VoLTE service in iPhones, it must pass Apple VoLTE Certificate, then Apple will push IOS
upgrading software packet for all iPhone 6 and iPhone 6s subscribers under Z network.
1. Check the IMS, PS RNC and eNodeB software version if it support VoLTE commercialization.
Cooperate with all product lines, all software version support commercialization.
2. Arrange using iPhone 6 engineering terminal and Huawei Mate 7 which support VoLTE to do the drive test for
whole city to check the network radio quality, VoLTE performance and compatibility between terminals and
network.
Radio quality is not good, average SINR is around 6db, no compatibility issue was found.
3. Finish the troubleshooting and call drop root cause clarification.
Check Part 5 Analysis
4. According to the call drop root cause, discuss with customer and finalize the optimization strategy solution.
Check Part 6 solution
IPHONE 6 and Mate7 drive testing at Riyadh city found call drop rate is high, aslo RRC Restablishment fialure
rate is high.
1 Non- eSRVCC VoLTE call drop happened at poor radio environment Call drop Close
Due to bad SINR(-17db), RRC.ReEst was triggered. From terminal log, we can find UE keep sending A3 report,
and the second A3 is intra-eNB(PCI=102).
But from E2E trace, eNB already sent intra-eNB HO in the second MR, checking from terminal log, terminal did’t
receive this HO command, probably due to bad SINR( because we can see after eNB sending HO command, UE
was still sending MR , no response to eNB command), so eNB didn’t receive HO complete message from UE, and
eNB are still waiting UE response, 2 seconds later, eNB receive the normal release message from MME, so there
is no abnormal release counter in eNB.
1. UE receive HO command from eNB, and eNB receive SRVCC HO successlul mesaage.It means UE
already finished accessing in 3G, but then call drop in 3G.
SRVCC procesure successed, but the 3G cell Ec/No is too much bad-20dB, which even smaller than minimon
access EcNo threshold, UE report to relocation to GSM.during all these UE activity, some message
(relocation complete message should be send from RNC to CN to ask MME to release UE-Context) missed
which caused SRVCC failure. Current LTE B1 event Utran measurement trigger quantity is setting as RSCP
or BOTH, the parameter ID is InterRatHoUtranB1MeasQuan, considering our testing area is in Riyadh
dense urban area, below snapshot site RIY0287 location for reference, if our measurement based on
RSCP even B1 even triggered by good RSCP target utran cell, but if the Ec/No is not good, SRVCC will be
easily failure due to target cell quality, 3G service relies on Ec/No more than RSCP especially in urban
area. As suggested by Huawei 3G R&D we should change the Utran measurement trigger quantity as
Ec/No to guarantee the SRVCC success rate. parameter description also mentioned below. But we
should pay attention that ehe value BOTH applies only to UEs complying with 3GPP Release 10.
For UEs complying with 3GPP Release 8 or 9, the value BOTH takes the same effect as the value
RSCP, the recommended value for Ec/No is -12(namely -24 in the system).
MOD INTERRATHOCOMM
MMLCommand LST INTERRATHOCOMM
Unit None
DefaultValue ECN0
RecommendedValue ECN0
After 7-8 seconds no response from RNC, 3G CN required to release Iu resources, at almost the same
time for 4G MME initialed the UE-Context-Release-Command to E-NodeB,SRVCC failure.
Our most SRVCC failure belongs to this case, what’s the root reason, why? Both 3G&4G quality is
bad,3G RTWP-73dBm,4G measured RSRQ-17dB.
Scenario A: UE attempt RRC Reestablishenment in Source eNB, if UE context still exists in eNB, RRC
Reestablishenment will succeed, or it will fail.
Scenario B: UE attempt RRC Reestablishenment in other eNB. firstly, UE camp on the eNB A, due to bad
SINR, UE RRC disconnected in eNB A, then UE attempt RRC Reestablishment in eNB B, if eNB B has UE
context, RRC Reestablishment will succeed. However, if UE never accesses in eNB B before, so there is no
UE context in eNB B, for this occasion, algorithm called RRC-Reestablishment without UE context will work.
eNB B will attempt to get UE context from eNB A through X2 interface. If UE context still existed in eNB A,
if UE context still exists in eNB, RRC Reestablishenment will succeed, or it will fail.
SR5256404 Root
Cause Analysis for Reestablishment Success Rate Low in Zain of Saudi Arabia.docx
6.1 RF optimization
After proceeding with the below optimization strategy, dial 100 times VoLTE call, only 1-2 call drop occurred
in the VoLTE simulation drive test conducted by operator.
Check the X2 Handover, S1 Handover and RRC.ReEst.Succ Rate for Riyadh eNodeB. Below it the statistic
analysis graph, it shows the amount of X2 Handover increases, the amount of S1 Handover decrease, at the
same time, RRC.ReEst.Succ Rate increase obviously since 10/31/2015(data of 11/04/2015 was extracted not
for the whole day ), RRC.ReEst.Succ is more than 90%. Then we arrange the VoLTE drive test and call drop
occurred no more than 10. So if the network SINR is very bad, the short-term and efficient way to solve
VoLTE call drop issues is to confirm there is no X2 and SCTP alarms, which will greatly promote solving
VoLTE call drop.
25000000 85.00%
20000000 79.64%80.00%
78.58%
15000000 75.71% 75.00%
72.56%
10000000 70.83% 70.00%
69.06% 68.33% 69.48%
5000000 65.00%
0 60.00%
10/28/2015 10/29/2015 10/30/2015 10/31/2015 11/01/2015 11/02/2015 11/03/2015 11/04/2015
00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00
S1 HO X2 HO HO total RRC.ReEstSR
VoLTE
optimization parameter.xlsx
7 Other
Solution:Change Utran B1 threshold for original LTE cell to let UE SRVCC to 2G cell, because the 2G signal is
very good in the problem area;
4G SINR:
2G RxQual: