LTE VoLTE & CSFB

E2E Service Quality Tuning

Analysis & Solution

HUAWEI Technologies Co., Ltd.

All rights reserved
 Quality Tuning

Table of Contents
T01 8s Call Disconnect ........................................................................................................ 3

T02 eSRVCC Voice Coding 4G-3G: ................................................................................... 5

T03 CSFB Call Setup Time .................................................................................................. 9

T04 VoLTE/PS handover threshold tuning ........................................................................ 14

T05 Low CSSR% of VoLTE to DR/CSFB in moderate radio condition ........................... 21

T06 UE return back to P1 LTE after CSFB ........................................................................ 23

2019-09-02 Huawei Proprietary - Restricted Distribution Page2, Total25

 Quality Tuning

T01 8s Call Disconnect

I. Problem Description
When we make call VoLTE-VoLTE, sometimes the call fails. When MT pick up the call,
MO call end directly, and MT call will be disconnect in 8s.

II. Troubleshooting
Performing trace in S1 interface, compare the success and failure trace
For failure call
In the INITIAL_CONTEXT_SETUP_REQ from MME, it request to setup ERAB_ID 5 (QCI
9), ERAB_ID 6 (QCI 5)

then in ERAB_SETUP_REQ from MME, it request to setup ERAB ID 5(QCI 1).

Due to same eRAB ID. So eNodeB responses with ERAB_SETUP_RSP with cause
multiple-ERAB ID instance.

That’s the reason call fail.

2019-09-02 Huawei Proprietary - Restricted Distribution Page3, Total25
 Quality Tuning

Compare with the success call flow.

In ERAB_SETUP_REQ, MME send ERAB-ID 7 (CQI 1).

III. Result

Change the MME (ZTE equipment) parameter to avoid multiple ERAB-ID

configurations.

2019-09-02 Huawei Proprietary - Restricted Distribution Page4, Total25

 Quality Tuning

T02 eSRVCC Voice Coding 4G-3G:

I. Problem Description
When VoLTE (eSRVCC to 3G) – OLNO, customer feedback that the voice quality is better
in 3G than 4G.

II. Troubleshooting

Below is the call flow for VoLTE (eSRVCC to 3G) – DiGi

CELCOM
A-SBC IMS C4/DIGI

INVITE: INVITE:
AMR-WB AMR-WB
AMR-NB AMR-NB
G.729 G.729
G.711A/U 183:
G.711A/U
183: G.729

G.729

INVITE:
AMR-NB
G.729
G.711A/U
183:
G.711A
When VoLTE call setup in 4G, A-SBC send invite message which support “AMR-WB,

AMR-NB, G.729, G.711A/U” message.

2019-09-02 Huawei Proprietary - Restricted Distribution Page5, Total25
 Quality Tuning

In 183 message which send from DiGi, it select the coding G.729.

After UE eSRVCC to Celcom3G, it send invite message again with supporting code

“ AMR-NB, G.729, G.711A/U”,

2019-09-02 Huawei Proprietary - Restricted Distribution Page6, Total25

 Quality Tuning

In 183 message which send from DiGi, it select the coding G.711.

Due to different coding, you can get different voice quality in P1 4G and Celcom3G.

Same calling flow for VoLTE (eSRVCC to 3G) – Maxis

2019-09-02 Huawei Proprietary - Restricted Distribution Page7, Total25

 Quality Tuning

C4/MAXI CELCOM
A-SBC IMS S

INVITE: INVITE:
AMR-WB AMR-WB
AMR-NB AMR-NB
G.729 G.729
G.711A/U 183:
G.711A/U
183: G.729

G.729

INVITE:
AMR-NB
G.729
G.711A/U
183:
G.711A

III. Result

Suggest P1(C4) network need negotiate the codec to using 711 with other operator network.

2019-09-02 Huawei Proprietary - Restricted Distribution Page8, Total25

 Quality Tuning

T03 CSFB Call Setup Time

I. Problem Description

When we performing CSFB call, here is the result for call setup time
MOC MTC Call Setup Delay
CSFB (P1) Celcom 3G 8s
CSFB (Celcom) Celcom 3G 6s
CSFB (P1) OLNO 8s
CSFB (P1) DR (P1) 9s
CSFB (P1) CSFB (P1) 8s
CSFB (P1) VoLTE 6s
DR (P1) Celcom 3G 7s
Celcom 3G Celcom 3G 5s
CSFB (Celcom) CSFB (Celcom) 7s
DR (P1) DR (P1) 8s
VoLTE VoLTE 1.5s
CSFB (P1) PSTN 6s
CSFB (Celcom) PSTN 7s
CSFB (P1) CSFB (Celcom) 8s
To analysis the CSFB time, we perform another test for CSFB-DR scenario.

The test result is:

CSFB (P1) to DR Time From RRC connection release to Alerting
1 1556 10.589
2 1613 9.988
3 1618 9.542

CSFB (Celcom) to DR Time From RRC connection release to Alerting

1 1714 7.696
2 1725 8.377
3 1729 7.92
It takes around 2s longer.

II. Troubleshooting

Take 1st call as sample.

2019-09-02 Huawei Proprietary - Restricted Distribution Page9, Total25
 Quality Tuning

CSFB (P1) to DR call flow

CSFB->DR
UE-A UE-B URAN eNodeB MME

Extend Service Req

108ms S1-AP Req

RRC Release

1461ms
CM Serv Req

Invite

1453ms 441ms

7090ms Invite
Paging Req

Paging Rsp
Alerting

Alerting

From IMS log, it takes 1.5s to proceeding signaling. It’s normal.

Check the trace from UE Log

From “Extended Service Request” to “RRCConnectionRelease”, it takes 108ms. UE release

the connection in 4G and goes to 3G.It takes 108ms

2019-09-02 Huawei Proprietary - Restricted Distribution Page10, Total25

 Quality Tuning

Same trace can found in MME log, 90ms from “Extended service request” to “UE Context

release complete”. It’s normal.

After UE fallback to 3G, it receive 3G broadcasting message, and send “CM Service Request”

in 3G. It takes 1.461s

MO setup the call for around 1.453s

2019-09-02 Huawei Proprietary - Restricted Distribution Page11, Total25

 Quality Tuning

From call proceeding to alerting, is waiting for call reach to MT, it takes around 7.09s.

The total CSFB call setup time is 10.589

Compare with CSFB(Celcom)-DR call flow, the difference is Celcom user when fallback to

3G, it not require to read system information again. So from UE attach 3G till CM Service

Request, it only need 84ms.

Mobile have function to restore a few number of cell information. If the UE attach the cell

which Mobile phone already restore cell information, UE only need read MIB, SIB7 message

to access. Otherwise UE need read MIB, SIB1,SIB2, SIB3,SIB7, etc, it will spend more

times. However, because P1 and Celcom belong to different network, P1 UE normally not

restores Celcom cell information. That’s the reason CSFB(P1) will be longer than

CSFB(Celcom).
2019-09-02 Huawei Proprietary - Restricted Distribution Page12, Total25
 Quality Tuning

III. Result
After UE receive “RRCConnectionRelease” message, UE fall back to 3G. The call setup
time is controlled in 3G network. So we can’t optimize much on 3G portion.

Reference
Normally there are several methods to optimize CSFB setup time.
Method Benefit Situation
Blind PS redirection Save 4G measurement report Already applied.
R9 RIM based CSFB Save SIB message when 3G attach Current Celcom not support
Proper TAI and LAI Save LAU process if LAC is the Already applied.
mapping same as the cell UE attached. However there will be scenario
P1 and Celcom have different
TAC planning.

2019-09-02 Huawei Proprietary - Restricted Distribution Page13, Total25

 Quality Tuning

T04 VoLTE/PS handover threshold tuning

I. Problem Description

Phase 1 DR POC Analysis:

1) PS redirection & Handover to 3G are successfully with HW propose threshold

(A2=-115dBm, A1=-111dBm).

2) During eSRVCC, VoLTE call tends to drop before the handover triggering. Hence during

eSRVCC test, the threshold is adjusted to (A2=-105dBm, A1=-101dBm) to avoid the VoLTE

call drop for eSRVCC functional test.

Hence, need to verify the best handover threshold for both PS & VoLTE considering the data

continuity & voice experience

We make 3 set of threshold fine tuning plan to test. We will make parameter recommendation

base on the test result.

 VoLTE & PSHO/Redirection Threshold Fine Tuning Plan

Orignal A2=-115dBm, A1=-111dBm, BlindA1A2=-121dBm

Set 1 A2=-110dBm, A1=-105dBm, BlindA1A2=-115dBm

Set 2 A2=-105dBm, A1=-101dBm, BlindA1A2=-110dBm

Set 3 A2=-101dBm, A1=-97dBm, BlindA1A2=-105dBm

Parameter configuration
Parameter Trial Plan on POC
No Category From To
MOD INTERRATHOCOMMGROUP: MOD INTERRATHOCOMMGROUP:
LocalCellId=1, LocalCellId=1,
InterRatHoCommGroupId=0, InterRatHoCommGroupId=0,
InterRatHoA1A2Hyst=2, InterRatHoA1A2Hyst=2,
1 PS Service-->PS InterRatHoA1A2TimeToTrig=640ms, InterRatHoA1A2TimeToTrig=640ms,
Redirection & InterRatHoA1ThdRsrp=-111, InterRatHoA1ThdRsrp=-105,
Handover InterRatHoA2ThdRsrp=-115; InterRatHoA2ThdRsrp=-110;
PS Service-->PS MOD CELLHOPARACFG: MOD CELLHOPARACFG:
Redirection & LocalCellId=1,BLINDHOA1A2THDRSRP LocalCellId=1,BLINDHOA1A2THDRSRP

2019-09-02 Huawei Proprietary - Restricted Distribution Page14, Total25

 Quality Tuning

Handover =-121; =-115;

MOD INTERRATHOCOMMGROUP: MOD INTERRATHOCOMMGROUP:
LocalCellId=1, LocalCellId=1,
InterRatHoCommGroupId=0, InterRatHoCommGroupId=0,
InterRatHoA1A2Hyst=2, InterRatHoA1A2Hyst=2,
PS Service-->PS InterRatHoA1A2TimeToTrig=640ms, InterRatHoA1A2TimeToTrig=640ms,
2
Redirection & InterRatHoA1ThdRsrp=-111, InterRatHoA1ThdRsrp=-101,
Handover InterRatHoA2ThdRsrp=-115; InterRatHoA2ThdRsrp=-105;
PS Service-->PS MOD CELLHOPARACFG: MOD CELLHOPARACFG:
Redirection & LocalCellId=1,BLINDHOA1A2THDRSRP LocalCellId=1,BLINDHOA1A2THDRSRP
Handover =-121; =-110;
MOD INTERRATHOCOMMGROUP: MOD INTERRATHOCOMMGROUP:
LocalCellId=1, LocalCellId=1,
InterRatHoCommGroupId=0, InterRatHoCommGroupId=0,
InterRatHoA1A2Hyst=2, InterRatHoA1A2Hyst=2,
PS Service-->PS InterRatHoA1A2TimeToTrig=640ms, InterRatHoA1A2TimeToTrig=640ms,
3
Redirection & InterRatHoA1ThdRsrp=-111, InterRatHoA1ThdRsrp=-97,
Handover InterRatHoA2ThdRsrp=-115; InterRatHoA2ThdRsrp=-101;
PS Service-->PS MOD CELLHOPARACFG: MOD CELLHOPARACFG:
Redirection & LocalCellId=1,BLINDHOA1A2THDRSRP LocalCellId=1,BLINDHOA1A2THDRSRP
Handover =-121; =-105;

Test Method

Test Set 1: VoLTE (MOC) to VoLTE (MTC-Static at LTE signal)

Test Set 2: PS redirection & PS Handover

Procedure

1) Test Set 1 & Test Set 2 carry along in the test vehicle with same laptop.

2) Moving from LTE towards LTE coverage edge to trigger for eSRVCC & handover.

Reminder:

1) VoLTE call experience need to be monitored.

II. Troubleshooting

Test Result of Set 0 (A2=-115dBm, A1=-111dBm, BlindA1A2=-121dBm)

2019-09-02 Huawei Proprietary - Restricted Distribution Page15, Total25

 Quality Tuning

LTE

Test Result of Set 1 (A2=-110dBm, A1=-105dBm, BlindA1A2=-115dBm)

2019-09-02 Huawei Proprietary - Restricted Distribution Page16, Total25

 Quality Tuning

Test Result of Set 2 (A2=-105dBm, A1=-101dBm, BlindA1A2=-110dBm)

2019-09-02 Huawei Proprietary - Restricted Distribution Page17, Total25

 Quality Tuning

Test Result of Set 3 (A2=-101dBm, A1=-97dBm, BlindA1A2=-105dBm)

2019-09-02 Huawei Proprietary - Restricted Distribution Page18, Total25

 Quality Tuning

III. Result

2019-09-02 Huawei Proprietary - Restricted Distribution Page19, Total25

 Quality Tuning

Jitter occurs more fat R

 At all fine tuning set proposal, both PS service redirection/handover and VoLTE

eSRVCC are handover successfully without service drop. But the quality and experience

of VoLTE is the focus in this fine tuning plan besides PS service.

 From test, PS service handover threshold are acceptable for all the sets proposed.

 From user experience during test for all sets, the VoLTE call quality noticed to be

affected (deep voice) when moving from good LTE coverage to edge before eSRVCC.

User experience “deep voice” is longer in Set 0 & Set 1 especially at the close to the

handover threshold compare to Set 2. For Set 3, no “deep voice” experience after few

tests.

 Hence, the handover threshold for both PS service & VoLTE is recommended to Set 3

(A2=-101dBm, A1=-97dBm) considering service retainability and user experience.

2019-09-02 Huawei Proprietary - Restricted Distribution Page20, Total25

 Quality Tuning

T05 Low CSSR% of VoLTE to DR/CSFB in moderate

radio condition

I. Problem Description

During the POC Phase 1 test, we encounter intermittent success of VoLTE to DR/CSFB.

After a few rounds troubleshooting, we found Celcom MSC send 480 temporary unavailable.

According to Celcom feedback, they said it’s due to poor radio condition.

II. Troubleshooting

We have perform test on Oct 22nd

Scenario VoLte to DR 20 Attempt
Radio Condition (RSCP)
VoLTE IMSI DR IMSI Celcom MSISDN DR (P1) Celcom 3G
103 105 0193639611 Good (-70 to -80) 100% 100%
103 108 0193639611 Average (-81 to -95) 95% 70%
103 108 0193639611 Poor (-96 to -100) 65% 60%
Test on Oct 24th
Scenario VoLte to DR Radio Condition (RSCP 20 Attempt
VoLTE IMSI DR IMSI Celcom MSISDN (dBM)) DR (P1) Celcom 3G
105 122 0193639611 Average (-81 to -95) 100% 75%
103 104 0136379038 Average (-81 to -95) 85% 85%
Test on Nov 11th

Scenario VoLte to DR Radio Condition (RSCP 20 Attempt

VoLTE IMSI DR IMSI Celcom MSISDN (dBM)) DR (P1) Celcom 3G
105 108 0193639611 Average (-81 to -95) 100% 85%
Test on Nov 13th

Scenario VoLte to DR Radio Condition (RSCP 20 Attempt

VoLTE IMSI DR IMSI Celcom MSISDN (dBM)) DR (P1) Celcom 3G
113 104 0193639611 Average (-81 to -95) 85% 75%
Scenario Celcom to Celcom Radio Condition (RSCP 20 Attempt
VoLTE IMSI Celcom MSISDN (dBM)) Celcom 3G
0193639611 0136379038 Average (-81 to -95) 95%

From the result, we found during the normal 3G condition, there is call failure for VoLTE to

DR, VoLTE to Celcom3G, Celcom to Celcom.

2019-09-02 Huawei Proprietary - Restricted Distribution Page21, Total25
 Quality Tuning

Check the failure log of VoLTE to DR, it is same 480 message send from Celcom.

Failure 1

Failure 2

Failure 3

III. Result

For this issue, we still need Celcom to feedback the failure reason, so that we can perform

further analysis on this.

2019-09-02 Huawei Proprietary - Restricted Distribution Page22, Total25

 Quality Tuning

T06 UE return back to P1 LTE after CSFB

I. Problem Description

When we doing CSFB call, we found certain UE can’t return to LTE after CS call. Base on

the test result, Mate7, iphone6 can return back to P1 LTE. Note4 sometimes can’t back to

LTE.

II. Troubleshooting

Checking the UE log file, after user end call, there is no frequency information in RRC

release message in UMTS. It means Fast Return function not working.

UE will have to back to LTE by reselection. There are two processes for UE to return.

Process 1

UE in PCH or Idle Mode, UE will reselect to Celcom 4G or P1 4G. Below is one of the cases

UE end call it 14:14:41.

2019-09-02 Huawei Proprietary - Restricted Distribution Page23, Total25

 Quality Tuning

After disconnection, UE go to PCH status at 14:14:48.

And UE reselect to LTE in PCH status. But the first reselection failed for “Tracking Area

Update Reject” at 14:14:55. It caused by UE reselecting to Celcom network. After rejection,

it select to P1 network.

UE successfully attach to 4G at 14:15:12. It takes 30s to return to P1 LTE.

Process 2

The UE changes frequently between FACH and PCH. It cannot reselect to LTE.

2019-09-02 Huawei Proprietary - Restricted Distribution Page24, Total25

 Quality Tuning

III. Result

We suggest enable Enhanced Fast Return feature in 3G network.

We have performed test in southern region which has already active enhanced Fast Return

feature.

Using Note4 phone, 20 times, all successfully come back to 4G after call end in idle and PS

ongoing mode.

By checking RRC connection release message, we can found P1 LTE frequency.

2019-09-02 Huawei Proprietary - Restricted Distribution Page25, Total25