Dears,

Based on S1 and Uu interface checking in some these site’s , there are too many
“S1AP_INITIAL_CONTEXT_SETUP_FAIL” to MME by the same cause as below:

From the S1 Trace the (E-RAB Failure due to MME)S1AP Initial Context Setup Fail due to
radioNetwork:interaction-with-other-procedure
In the Signalling flow, the eNodeB sends the RRC_UE_Cap_Enquiry, due to no reply from the UE
after 5S the MME send UE_Context_Rel_CMD to eNodeB to relase the UE context, hence the
eNodeB sent _Fail to MME
Top UE with Poor Uplink signal quality lost the signal is the reason for initiating other access
procedure before completing the 1st Access procedure which leads for MME detection of the
same UE initiation for two access during short time, and release the first access procedure
which caused ERAB setup failed with cause “interaction-with-other-procedure”.

There are too many sites with the same issue.

Solutions:

 Please consider that as we checked all LTE sites with 1800 and 900 band, have the
same Reference signal power of 212, which are not good solution for optimization, the
power of 900 should be more than 1800 based on coverage.

 Also the tilt range as we checked for many sites are not optimized.

 Some neighbors, are not defined.


 L.E-RAB.AbnormRel.eNBTot

 As below the L.E-RAB.AbnormRel.eNBTot counter is incremented each time the eNodeB
sends an E-RAB RELEASE INDICATION message to the MME and the release cause is not
"Normal Release", "Detach", "User Inactivity", "Om-Intervention", "CS Fallback
triggered", "UE Not Available for PS Service", "Inter-RAT Redirection", "Successful
Handover", or "Redirection towards 1xRTT".
 all E-RABs of the UE are released if the eNodeB sends a UE CONTEXT RELEASE REQUEST
message to the MME.
 If the release cause is not "Normal Release", "Detach", "User Inactivity", "Om-
Intervention", "CS Fallback triggered", "UE Not Available for PS Service", "Inter-RAT
Redirection", "Time critical handover", "Handover Cancelled", "Redirection towards
1xRTT", or "Reduce load in serving cell" by load-based redirection

 RRC Setup and failure cause.

 during RRC setup failure we found that more 80% failures are contributed by uplink
interference alone based on this analyzes we try to figure out the top UE in that site.





 TOP 10 TMSI contributing failure with Uplink interference and weak
coverage




 
 Based on above figure you can see that top TMSI are having majority failure
with uplink weak coverage+ interference .

 Feature group indicator. Below feature group handset contributing more
failure alone which can have impact on cell level KPI.

Count of
Row Labels Counter
S1AP Uefeature Unacquirable 9103
0x02;0008;FF4F1E9A;000000C4;00000000;00000093;056
0 349
0x02;0008;FF4FFE9A;000800C5;00000000;00000093;056
0 146
0x02;0028;FF4FFE9A;000800C5;00000000;00000093;056
0 68
0x02;0008;FF4FFE9A;000000C4;00000000;00000093;056
0 66

 Top UE / TMSI information





 RAB Setup failure

L.E-RAB.FailEst.RNL
L.E-RAB.FailEst.NoReply
L.E-RAB.FailEst.SRBReset
L.E-RAB.FailEst.SecurModeFail
L.E-RAB.FailEst.NoRadioRes
L.E-RAB.Fai
ERAB Setup Failure L.E-RAB.Fai
L.E-RAB.Fai
L.E-RAB.Fai
L.E-RAB.Fai
L.E-RAB.Fai
L.E-RAB.Fai
L.E-RAB.FailEst.RNL.eNodeB.NormRel
 L.E-RAB.FailEst.RNL.eNodeB.AbnormRel
L.E-RAB.FailEst.RNL.Other
L.E-RAB.FailEst.TNL
L.E-RAB.FailEst.TNL.DLRes
L.E-RAB.FailEst.TNL.ULRes
L.E-RAB.FailEst.TNL.Other
L.E-RAB.FailEst.MME
L.E-
RAB.FailEst.Conflict.Hofail
L.E-RAB.FailEst.Other

 Suggestion and solution:
 Based on above analyzes we can identify this issue is spread across network by some UE
.And to uplink interference issue we need your DT support to perform a comprehensive
drive test under the coverage of this site to further rule out the uplink interference
issue.
 Moreover, would appreciate if you return with IMSI/IMEI information of given TMSI, so
we can extract handset detail as well.
