0% found this document useful (0 votes)
145 views25 pages

U2000 & PRS Operation Introduce V1.0

1) The document provides reference materials for analyzing eRAN KPIs and counters, including an Excel file listing eRAN KPIs and a file with PFM counter settings. 2) It describes potential causes for various RRC and E-RAB setup failures based on analyzing sub-items and KPIs. 3) Analysis descriptions are provided for different failure causes at various levels to help troubleshoot issues.

Uploaded by

Nam Pham
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
145 views25 pages

U2000 & PRS Operation Introduce V1.0

1) The document provides reference materials for analyzing eRAN KPIs and counters, including an Excel file listing eRAN KPIs and a file with PFM counter settings. 2) It describes potential causes for various RRC and E-RAB setup failures based on analyzing sub-items and KPIs. 3) Analysis descriptions are provided for different failure causes at various levels to help troubleshoot issues.

Uploaded by

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

LTE M2000 & PRS Operation

Guide
eRAN KPI & Counter Reference
eRAN KPI: Reference “eRAN_KPI_Reference_Summary.xlsx” Raw Counter: Reference Pfm Counter Setting.xlsx
1 2

Counter
eRAN KPI

HUAWEI TECHNOLOGIES CO., LTD. Page 2


eRAN KPI – Failure Cause Reference
KPIs Analysis Sub Items Level 1 Sub Items Level 2 Analysis Description
1. Interference exists.
2. Top users or Ues are abnormal.
L.RRC.SetupFail.NoReply 3. BBP CPU usage is high due to congestion
- VS.Board.CPUload.MAX is about 90%
4. Weak coverage exists.
1. SRS parameter configurations are limited.
L.RRC.SetupFail.ResFail.SRS 2. SRS resource fail to be expanded.
3. The number of Ues is large.
1. PUCCH parameter configurations are limited.
RRC Failure Cause
L.RRC.SetupFail.ResFail.PUCCH 2. PUCCH resource fail to be expanded.
L.RRC.SetupFail.Rej 3. The number of Ues is large.
L.RRC.SetupFail.Rej.FlowCtrl The number of online Ues exceeds the CAPs specifications of a single eNodeB and VS.BBUBoard.CPUload.MAX is less than 80%
1. The number of online Ues exceeds the system CAPs.
Other => L.RRC.SetupFail.Rej-L.RRC.SetupFail.ResFail.SRS- 2. Parameter configurations are incorrect.
L.RRC.SetupFail.ResFail.PUCCH-L.RRC.SetupFail.Rej.FlowCtrl 3. Resource allocation failures occur.
4. Produce bugs exist.
L.RRC.ConnReq.Att-L.RRC.ConnReq.Succ-L.RRC.SetupFail.Rej- 1. System is faulty
Other
L.RRC.SetupFail.NoReply 2. Others
1. Interference exists.
L.E-RAB.FailEst.NoReply 2. Top users or Ues are abnormal.
3. Weak coverage exists.

1. E-RAB setup failures occur due to EPC exceptions.


L.E-RAB.FailEst.MME
2. The eNodeB does not receive any UE's response and the timer at the eNodeB air interface and S1 interface is greater than the context setup timeout timer on the EPC. As a result, the EPC release the UE's context setup message earlier

1. IPPATH is not configured or incorrectly configred


L.E-RAB.FailEst.TNL
2. The SCTP link is intermittently disconnected
L.E-RAB.FailEst.RNL Number of E-RAB setup failures due to faults at the radio network layer
1. The system exceeds the license capacity
E-RAB Failure Cause
L.E-RAB.FailEst.NoRadioRes 2. Paramter configurations are incorrect
3. Product bugs exist
1. The null algorithm is delevered after the eNodeB license is expired.
2. The security mode configuration fails due to UE incompatibility
L.E-RAB.FailEst.SecurModeFail
3. The EPC is abnormal
4. eNodeB completeness or encryption algorithms are incorrectly configured
1. The UE does not support the UM mode
L.E-RAB.AttEst-L.E-RAB.SuccEst-L.E-RAB.FailEst.NoReply-L.E-
2. The EPC is abnormal
Other RAB.FailEst.MME-L.E-RAB.FailEst.TNL-L.E-RAB.FailEst.RNL-L.E-
3. Top Ues are abnormal
RAB.FailEst.NoRadioRes-L.E-RAB.FailEst.SecurModeFail
4. Product bugs exist
1. Cells experience uplink interference
2. Cells are heavy loaded and networks are congested
- L.ChMeas.PRB.UL.Used.Avg > 80%
- L.Traffic.User.Max > 200
L.E-RAB.AbnormRel.Radio
3. Weak coverage
4. Missing NB
5. RF channel fault
E-RAB Drop Cause 6. Downlink interfernec due to overlap coverage
1. Wrong configuration for SCTP & GTPU
L.E-RAB.AbnormRel.TNL
2. Transmission faults on fixed networks
L.E-RAB.AbnormRel.Cong 1. Cells are heavy loaded and networks are congested
1. Abnormal handovers
L.E-RAB.AbnormRel.HOFailure
2.Incorrect neighbor relationships
L.E-RAB.AbnormRel.HOOut
L.HHO.Prep.FailOut.MME Number of outgoing handover preparation failures because of faults on the MME side
L.HHO.Prep.FailOut.NoReply Number of outgoing handover preparation failures because of no responses from the target cell
HHO Preparation Failure Cause
L.HHO.Prep.FailOut.PrepFailure Number of outgoing handover preparation failures because the target cell sending handover preparation failure messages
L.HHO.Prep.FailOut.HOCancel Number of failed outgoing handover preparations because the source cell sending handover cancellation messages
L.IRATHO.E2G.Prep.FailOut.MME Number of inter-RAT handover preparation failures from E-UTRAN to GERAN because of faults on the MME side
L.IRATHO.E2G.Prep.FailOut.NoReply Number of inter-RAT handover preparation failures from E-UTRAN to GERAN because of no responses from GERAN
L.IRATHO.E2G.Prep.FailOut.PrepFailure Number of inter-RAT handover preparation failures from E-UTRAN to GERAN due tobecause GERAN cells send handover preparation failure messages
IRAT HO Preparation Failure Cause
L.IRATHO.E2W.Prep.FailOut.MME Number of inter-RAT handover preparation failures from E-UTRAN to WCDMA network because of faults on the MME side
L.IRATHO.E2W.Prep.FailOut.NoReply Number of inter-RAT handover preparation failures from E-UTRAN to WCDMA network because of no responses from WCDMA network
L.IRATHO.E2W.Prep.FailOut.PrepFailure Number of inter-RAT handover preparation failures from E-UTRAN to WCDMA network because WCDMA network cells send handover preparation failure messages

HUAWEI TECHNOLOGIES CO., LTD. Page 3


M2000 & PRS User Login
 PRS (https://10.19.246.139:8443/common/assets/htmls/login/login.html)

 M2000 (10.19.246.135)

HUAWEI TECHNOLOGIES CO., LTD. Page 4


M2000 – Raw Counter Measurement Management
M2000 PRS
Path: Performance -> Measurement Management

HUAWEI TECHNOLOGIES CO., LTD. Page 5


M2000 – User define KPI
M2000 PRS
Path: Performance – User defined Counter Management

HUAWEI TECHNOLOGIES CO., LTD. Page 6


M2000 – KPI Query
1 M2000 PRS
 Trace path:

2 3

HUAWEI TECHNOLOGIES CO., LTD. Page 7


M2000 – Backup Configure File
M2000 PRS
Path: Maintenance – Backup Management – NE Backup

HUAWEI TECHNOLOGIES CO., LTD. Page 8


M2000 – Export Radio Network Planning Data
M2000 PRS
Path: Create Planned Area

Path: Export Data

HUAWEI TECHNOLOGIES CO., LTD. Page 9


M2000 – License Management
M2000 PRS
Path: License – NE License Management - Stand Alone

MML: DSP LICINFO

HUAWEI TECHNOLOGIES CO., LTD. Page 10


M2000 – Alarm Management
M2000 PRS
Path: Monitor – Browse Currents Alarms

HUAWEI TECHNOLOGIES CO., LTD. Page 11


M2000 – RET Management
M2000 PRS
MML: DSP RET

HUAWEI TECHNOLOGIES CO., LTD. Page 12


M2000 – KPI Real time monitoring
M2000 PRS
1
 Trace path:
2

3 4 5

HUAWEI TECHNOLOGIES CO., LTD. Page 13


M2000 – Cell Performance Monitoring – Throughput
M2000 PRS
 Trace path:

1 2

HUAWEI TECHNOLOGIES CO., LTD. Page 14


M2000 – Cell Performance Monitoring – Number of User
M2000 PRS
 Trace path:

1 2

HUAWEI TECHNOLOGIES CO., LTD. Page 15


M2000 – Throughput monitoring
M2000 PRS
 Trace path:

1 2

HUAWEI TECHNOLOGIES CO., LTD. Page 16


M2000 –TMSI information of the test UE
M2000 PRS
Get the TMSI from the Probe Get the TMSI from the S1 signal: S1AP_INITIAL_UE_MSG

HUAWEI TECHNOLOGIES CO., LTD. Page 17


M2000 – Trace Management
M2000 PRS
 Trace path:

Trace interface Cell Pfm monitoring User Pfm monitoring


1 2 3

HUAWEI TECHNOLOGIES CO., LTD. Page 18


M2000 – Trace interface
 Trace path:

1 2 3

HUAWEI TECHNOLOGIES CO., LTD. Page 19


PRS Introduce
 PRS (https://10.57.126.9:8443/common/assets/htmls/login/login.html)

HUAWEI TECHNOLOGIES CO., LTD. Page 20


PRS – Report Management
 PRS 1
(https://10.57.126.9:8443/common/
assets/htmls/login/login.html)

2 3 4

HUAWEI TECHNOLOGIES CO., LTD. Page 21


PRS – KPI Management
 PRS
(https://10.57.126.9:8443/common/
1
assets/htmls/login/login.html)

HUAWEI TECHNOLOGIES CO., LTD. Page 22


PRS – KPI Analysis
 PRS
(https://10.57.126.9:8443/common/
1
assets/htmls/login/login.html)

3 4
2

HUAWEI TECHNOLOGIES CO., LTD. Page 23


PRS – KPI Analysis(Cont)
 PRS (https://10.57.126.9:8443/common/assets/htmls/login/login.html)

1
2

HUAWEI TECHNOLOGIES CO., LTD. Page 24


THANK YOU

HUAWEI TECHNOLOGIES CO., LTD. Page 25

You might also like