• RRC CONNECTION ESTABLISHMENT 
• S1 SIGNALING CONNECTION ESTABLISHMENT 
• INITIAL E-RAB ESTABLISHMENT OR E-RAB ADDITION

 

 Counter Related :



MAJOR REASONS FOR POOR ACCESSIBILITY

• Check inter site distance with neighbors site. 
• Check value of pmBadCovEvalReport (if MCPC enabled, need to check pmCriticalBorderEvalReport). If this counter is pegging high in respect to RRC attempts, then we can say that more number of UEs  are falling in bad coverage. 
• Check  pmRadioTbsPwrRestricted  to see if UE has reached maximum power of UE. 
• Check if the cell is overshooting and the power of the cell is to high

• Through OSS commands “alt” (Current / Active site alarms can be checked) & “lga <nd>” (n is an integer value) (Site alarms present for n days can be checked) 
• Sometimes, due to MOs are not synchronized properly, pmRrcConnEstabFailOverload is pegged high. In this case, the ServiceUnavailable (S1 Connection failure) alarm is observed in sites, even though RRC Conn Users remain to be same.

• The command “ue print -admitted” is used to find the no. of UEs currently latched to the site sector-wise ROP-wise & the counters “pmRrcConnMax (max)” & “pmRrcConnMax (sum)” are used to find out ‘max. active users/ day’ and ‘sum of all active users/day’, respectively.
• Connected User License Congestion
  Check counter “pmRrcConnEstabFailLic” . If this counter is pegging, which means there will be rrc connection request reject due to Connected User License limitation.

• If RRUs  are disabled, in that case “HW fault” alarm is observed in sites.
• Command “st . aux” shows that the operational state of the auxiliary unit/ RRUs is DISABLED

• High UL N+I is impacting to all KPIs. UL NI values {-119 …….. -110 dBm} is considered to be good. 
• The cause may be Internal Sources (Check Tx & Rx antenna ports, fiber cables and connectors. All connection should be proper) and External Sources ( like repeaters, airport, power plant etc. sources resulting in high EMW in the neighborhood). 
• pmRadiorecInterferencePwr is checked for UL N+I values.

• Two types of PCI conflict: 
• PCI confusion, i.e., UE is confused if it is getting two or more target cells having same PCI. 
• PCI collision, i.e., UE is collision due to source and target having same PCI. 

• Impacts all KPIs. 
• Use “EUtranCellFDD . pciconflict” to find out PCI conflict of site.

• Based on ‘Zero Correlation Zero Configuration‘ parameter RACH root Sequence index need to be planned. Difference of 10 is recommended for RACH root Sequence index per cell.

• The cabx command provides VSWR status for RL1 & RL2 (for 2T2R). Both, RL1 and RL2 should be difference of less than 5.

• Cell availability should be 100% , more when it is in cell busy hour.