The document provides guidelines for analyzing the 4G PS Setup Success Rate, which is measured by the RRC Connection Setup Success Rate and the E-RAB Call Setup Success Rate (ERAB SSR). It defines the KPI formulas and outlines various performance counters and identification methodologies to classify the potential causes of RRC and ERAB setup failures, such as issues related to resources, configurations, interference, coverage, or behaviors of users/UEs. Optimization suggestions include performance counter analysis, identifying general failure causes, and checking for specific issues like MME faults, transport network layer problems, or high interference.
The document provides guidelines for analyzing the 4G PS Setup Success Rate, which is measured by the RRC Connection Setup Success Rate and the E-RAB Call Setup Success Rate (ERAB SSR). It defines the KPI formulas and outlines various performance counters and identification methodologies to classify the potential causes of RRC and ERAB setup failures, such as issues related to resources, configurations, interference, coverage, or behaviors of users/UEs. Optimization suggestions include performance counter analysis, identifying general failure causes, and checking for specific issues like MME faults, transport network layer problems, or high interference.
The document provides guidelines for analyzing the 4G PS Setup Success Rate, which is measured by the RRC Connection Setup Success Rate and the E-RAB Call Setup Success Rate (ERAB SSR). It defines the KPI formulas and outlines various performance counters and identification methodologies to classify the potential causes of RRC and ERAB setup failures, such as issues related to resources, configurations, interference, coverage, or behaviors of users/UEs. Optimization suggestions include performance counter analysis, identifying general failure causes, and checking for specific issues like MME faults, transport network layer problems, or high interference.
The document provides guidelines for analyzing the 4G PS Setup Success Rate, which is measured by the RRC Connection Setup Success Rate and the E-RAB Call Setup Success Rate (ERAB SSR). It defines the KPI formulas and outlines various performance counters and identification methodologies to classify the potential causes of RRC and ERAB setup failures, such as issues related to resources, configurations, interference, coverage, or behaviors of users/UEs. Optimization suggestions include performance counter analysis, identifying general failure causes, and checking for specific issues like MME faults, transport network layer problems, or high interference.
Condition RRC connection failure caused by non-vendor equipment should be excluded.
KPI Formula ([L.RRC.ConnReq.Succ.Emc]+[L.RRC.ConnReq.Succ.HighPri]+[L.RRC.ConnReq.Succ.Mt]+[L.RRC.ConnReq .Succ.MoData]+[L.RRC.ConnReq.Succ.DelayTol])/([L.RRC.ConnReq.Att.Emc]+[L.RRC.ConnReq.Att.HighPri ]+[L.RRC.ConnReq.Att.Mt]+[L.RRC.ConnReq.Att.MoData]+[L.RRC.ConnReq.Att.DelayTol])*{100} The setup success rate of RRC connections in a cell represents the capability of the cell to provide RRC connections for end users.
Optimization Suggestion Performance Counter Analysis to classify the causes (cont.) Identify the general causes for RRC connection setup failures. Causes for RRC connection setup failure can be categorized to no response from a UE over air interface, or request rejection. Request rejection can be caused by resource insufficiency, flow control, MME overload or others. The resource insufficiency causes can further breakdown into different type of resources. 4G PS Setup Success rate – (RRC Connection Setup Success Rate (service))
Optimization Suggestion
Performance Counters Identification Methodology Possible Causes
1. Improper TAC/TAL planning Sudden increase in the number of RRC and ERAB setup success rate maintain as normal. The 2. NAS message exceptions at the EPC side RRC Connection Setup Requests maximum number of users in a cell also remains the same. 3. Contributed by top users/UEs due to faulty processing procedures of UEs.
1. Parameter configuration changes
RRC and ERAB setup success rate maintain as normal. The 2. Parameter configuration changes or operations at the EPC side number of preamble <L.RA.GrpA.Att> and <L.RA.GrpB.Att> 3. User behaviors change in the course of a large event decrease at the same time. Sudden decrease in the number of 4. After frequency refarming activity, users are not HO back to LTE network RRC Connection Setup Requests 1. Parameter configuration changes 2. Sleeping cell Others 3. Abnormal releases by the EPC 4. Contributed by top users/UEs due to faulty processing of terminals <L.UL.Interference.Avg> ≥ -115dBm UL interference
The baseband board has excessively high CPU usage due to network congestion, which Baseband board <VS.Board.CPUload.Max> ≥ 90% results in delayed sending of the RRC Connection Setup message. As a result, large number of <L.RRC.SetupFail.NoReply> RRC Connection Setup Requests are not responded.
1. Weak coverage Others 2. Abnormal behaviors of top users or top UE 3. Others The maximum number of users in a cell reaches or exceeds the 1. Resource congestion user specification of the cell 2. Improper allocation for license item “RRC Connected User” LMPT board 1. The CPU usage runs at a high level due to massive operations on an NE. As a result, the <VS.Board.CPUload.Max> ≥ 80% access request cannot be promptly handled <L.RRC.SetupFail.ResFail> LBBP board 2. The CPAS run over the maximum number allowed for a site <VS.Board.CPUload.Max> ≥ 98% 1. Improper parameter settings Others 2. The CPAS run over the maximum number allowed for a site 3. Product defects/bugs 4G PS Setup Success rate –(E-RAB Call SSR (%))
Condition ERAB setup failure caused by non-vendor equipment should be excluded.
KPI Formula ∑<L.E-RAB.SuccEst> / ∑<L.E-RAB.AttEst> * 100% The ERAB setup success rate in a cell represents the capability of the cell to provide ERAB connections for end users.
Optimization Suggestion Performance Counter Analysis to classify the causes (cont.) Identify the major causes for ERAB setup failures. ERAB setup failures can be caused by radio network layer faults, transport network layer faults, or faults on the MME side. In eRAN7.0, many new performance counters have been introduced, and the sub-failure causes can be further categorized to ERAB VoIP service or not. 4G PS Setup Success rate –(E-RAB Call SSR (%))
Optimization Suggestion Performance Counter Analysis to classify the causes (cont.) Identify the general causes for ERAB setup failures. Following is the simplify tree diagram which omit the performance counters related to ERAB VoIP. service. 4G PS Setup Success rate –(E-RAB Call SSR (%))
Optimization Suggestion
Performance Counters Identification Methodology Possible Causes
RRC and ERAB setup success rate maintain Sudden increase in the number 1. License capacity over the limit as normal. The maximum number of users in a of ERAB Setup Attempts 2. Data transmission or NE interoperations issues cell also remains the same. 1. ERAB connection setup failure due to EPC faults 2. Check the top users/UEs. The eNodeB does not receive response message <L.E-RAB.FailEst.MME> None from UE side, and if the timer length of eNodeB air interface or S1 interface is greater than that of the EPC. As a result, ERAB connection setup request is released by the EPC side before timer timeout at eNodeB side. 1. Incorrect or missing IP path configurations <L.E-RAB.FailEst.TNL> None 2. Intermittence SCTP link transmission 1. UL interference <L.UL.Interference.Avg> ≥ -115dBm 2. Abnormal behaviors of top users or top UE <L.E-RAB.FailEst.NoReply> 1. Weak coverage Others 2. Abnormal behaviors of top users or top UE 3. Others 1. License capacity over the limit <L.E- None 2. Improper parameter setting RAB.FailEst.NoRadioRes> 3. Product defects/bugs 1. Check the top users/UEs. Configuration failure of the security mode due to <L.E- terminal compatibility None RAB.FailEst.SecurModeFail> 2. ERAB connection setup failure due to EPC faults 3. Improper algorithm configuration on the eNodeB side End Of The Slide
