CS CSSR Formula = CS RRC Success Rate * CS RAB Success Rate=

(RRC.SuccConnEstab.OrgConvCall+RRC.SuccConnEstab.TmConvCall+RRC.SuccConnEstab.E
mgCall)/
(RRC.AttConnEstab.OrgConvCall+RRC.AttConnEstab.TmConvCall+RRC.AttConnEstab.EmgCa
ll)*(VS.RAB.SuccEstabCS.Conv+VS.RAB.SuccEstabCS.Str)/
(VS.RAB.AttEstabCS.Conv+VS.RAB.AttEstabCS.Str)
After analyze RRC Setup Success Rate and RAB Establishment Success Rate, Low RRC Success
Rate mainly impact CS CSSR.

1 RRC Establish Fail

1.1 Performance Log analysis

RRC Establish fail reason include two factor: NoReply, UL CE Congestion, NodeBULCE
Congestion.

1.1.1 UL CE Congestion

Top Site have UL CE congestion, especially site 323A681G_3G_SIAK_SRI_INDRAPURA,

3234425G_3G_UKUI_SATU, 3234332G_3G_PANTAI_CERMIN_KAMPAR.

2017-2-8 , 1 , 7


Top cells list:

14787,16817,16819,14789,16818,14788,24282,44251,24281,24283,14053,44253,44254,44427,14
052,44256,14051,16317,24745,16319,14091,16849,24742,14022,14434,16848,44255,14819,4438
5,44252,14023,43322,14761,16846,24746,44428,44429

1.1.2 NODEB UL/DL CE Congestion

NODEB UL CE Congestion:
Top cells or sites similar with UL CE congestion.

NODEB UL CE Congestion:
Mainly cells of Site 323A681G_3G_SIAK_SRI_INDRAPURA have NODEB DL CE congestion.

2017-2-8 , 2 , 7


1.1.3 DL Power Congestion

Top cells have DL power congestion.

Top Cells List:

44062,55675,16854,44301,44304,14072,44565,24745,44562,24742,44566,44592,44563,44856,14
889,43949,44595,44851,14073,24971,44857,14869,44886,55676,10741,

1.2 PCHR Log analysis

From PCHR log, there are three reason leading to RRC accessing failure.

1.2.1 RR_ERR_RNCAP_RRC_UE_RSP_TIMEOUT

RRC_RRC_CONN_SETUP
UE dont response RRC_CONN_SETUP message due to weak coverage.

2017-2-8 , 3 , 7


RRC_CELL_UPDATE
RRC DSCR release when RRC connection concurs with the CU.

1.2.2 L2ERR_FPMDC_TR_SYN_NO_RESPONSE_AFTER_MAX_RETRY

It was L2ERR_FPMDC_TR_SYN_NO_RESPONSE_AFTER_MAX_RETRY which caused by

no response of FP synchronization.
From the PFM log, the mean PING delay of this sites Iub interface had reached up to 4000ms and
the packet loss rate had reached up to 35%. This meant that FP synchronization failure was caused
by the delay and packet loss of Iub interface. It should check the transmission side for next step.

2017-2-8 , 4 , 7


NodeB id list of high drop rate and long delay:

153,142,184,187,132,136,133,137,135,146,141,134,246,248,252,189,106,130,185,104,157,149,11
1,110,113,101,183,118,259,100,190,255,108,107,250,249,109,253,256,257,254,258,251,247,125,
120,119,112,245,143,144,122,145,

1.2.3 NBM_CRA_CCH_DISABLE

TOP cells have this same problem.

CELL unavailable time is relative RRC fail.

2017-2-8 , 5 , 7


2 RAB Establish Fail

2.1 Performance Log analysis

CS RAB Establish fail reason include two factor: UL CE Congestion, Unsp, NODEB UL CE
congestion.

2.1.1 UL CE Congestion

Top cells list:

44814,44811,44815,44812,44816,44813,14237,14312,16317,14313,44427,14238,16207,16208,16
319,

2017-2-8 , 6 , 7


2.2 PCHR Log analysis

From PCHR log, there are three reason leading to RRC accessing failure.

2.2.1 L2ERR_FPMDC_TR_SYN_NO_RESPONSE_AFTER_MAX_RETRY

Similar with RRC analysis. High drop rate and long delay of IUB interface leads this problem.

2.2.2 NBM_CRA_CCH_DISABLE

Similar with RRC analysis. Cell unavailability leads this problem.

2017-2-8 , 7 , 7