Scribd
Upload
150 views8 pages

Analysis of Miss Call Issue V2 0

The customer complained about frequently receiving missing call messages. The problem was caused by a mismatch between the paging cycle configured on the UE and eNodeB. The root cause was that the MME misunderstood the 3GPP protocol and used the default paging DRX from the S1 SETUP REQUEST as the paging cycle in S1AP messages, instead of using the UE specific value. This caused the UE and eNodeB to use different paging cycles, resulting in missed paging messages and missing calls. The corrective action is for the MME to not include the PagingDRX IE if no value is provided by the UE, as specified by the 3GPP protocol.

Uploaded by

Armaghan Ahmad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
150 views8 pages

Analysis of Miss Call Issue V2 0

The customer complained about frequently receiving missing call messages. The problem was caused by a mismatch between the paging cycle configured on the UE and eNodeB. The root cause was that the MME misunderstood the 3GPP protocol and used the default paging DRX from the S1 SETUP REQUEST as the paging cycle in S1AP messages, instead of using the UE specific value. This caused the UE and eNodeB to use different paging cycles, resulting in missed paging messages and missing calls. The corrective action is for the MME to not include the PagingDRX IE if no value is provided by the UE, as specified by the 3GPP protocol.

Uploaded by

Armaghan Ahmad
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 8

Analysis of Miss Call Issue

Problem Description
Customer complained that many Missingcall messages were received in building usually. The scenario was recurred by frontline,
eNodeB had sent CS paging message at 12:45 on 22th October, but UE did not receive CS paging as is shown below. Missing
paging message caused MT user received Missingcall message.

eNodeB UU trace

UE Probe trace

Problem Analysis
1.The Paging Cycle Mismatch Between UE
and eNodeB
Based on live logs, the PagingDRX MME send to
eNodeB by S1-AP PAGING is v32, as the figure 1.

Figure 1 S1-AP PAGING

But defaultPagingCycle eNodeB send to UE by


SIB2 is rf128, as the figure2.
From UE side log, this value is not specified in drxparameter and this shows it is infinite, as the figure
3.
The eNodeB Paging cycle equals to min
(PagingDRX, DefaultPagingCycle,) =min(32,128)
=rf32;

Figure 2 RRC-AP PAGING

The UE receive Paging cycle equals to min


(defaultPagingCycle, infinite) =min(128, infinite)
=rf128;
Figure 3 Paging DRX UE Send to MME in UE log

Problem Analysis
2.Protocol Analysis of Paging Cycle
Based on 3GPP protocols:
UE know Default Paging DRX= rf128 which eNodeB configure
by SIB2. From UE log, UE has no specific paging cycle, so it is
infinite.
UE take min(rf128, specific paging cycle at UE side)= rf128 as
paging cycle to compute PF(Paging Frame) and PO(Paging
Occasion) as occasion UE receive paging.
UE send specific Paging DRX to MME by NAS message when
UE attach.

Problem Analysis
2.Protocol Analysis of Paging Cycle
MME is expected to decide paging DRX based on UE specific Paging cycle. If UE doesnt specify the DRX parameter in ATTACH
REQUEST message, the MME is expected not to contain the PagingDRX IE in S1-AP Paging. So the protocol revises the presence of the IE
from Mandatory to Optional.
Though the Default Paging DRX value eNodeB send to MME at S1 SETUP REQUEST is v32, this value is for an eNodeB level, not a cell
level (Paging is a cell level procedure for smarter paging). This value is paging timeout timer for MME. However, the protocol doesnt
specify the MME should use it as a PagingDRX Cycle in paging procedure.
However, MME uses this value as PagingDRX in S1AP-Paging message. Then ENB takes min (PagingDRX, DefaultPagingCycle,) =min
(32,128) =rf32 as paging DRX parameters.
In conclusion, the misunderstanding of MME causes the mismatch paging parameters between UE and ENB. This mismatch causes the
paging failure and missing call.

Root Cause
ZTE MME misunderstands in taking Default Paging DRX=rf32 contained in message S1 SETUP REQUEST as
DefaultPagingCycle and send it to eNodeB. In fact, MME is expected to decide paging DRX based on UE specific paging
cycle reported. If UE doesnt specify the DRX parameter in ATTACH REQUEST message, the MME is expected not to
contain the PagingDRX IE in S1-AP Paging.
This makes a mismatch of paging parameters between UE and ENB. This would result in the failure of Mt-Access.

Corrective Action
Workaround:
Modify MML configuration: DefaultPagingCycle=rf32
Solution:
MME is expected not to contain the PagingDRX IE in S1-AP Paging

THANK YOU!

You might also like