Document Name

Confidentiality:

Document Name Version Document Code Prepared By Reviewed By Approved By Applicability

Top worst cell analysis Guideline V1.00

V1.00

Effective Date L1

2010-07-31 Based eTOM

L2 Based eTOM L3 Based eTOM L4 Based eTOM Global Standard Roles Analysis engineer

Relevant Process/Regulation
Document Name Document Code

Abstract

This document instructs briefly engineers to analyze T TopN worst cell KPIs degradation for network performance monitoring.

Purpose

This document provides checklist how to analyze frequently happen top worst cell problem, including RRC failure, CS CDR, and CS RAB assignment.

Definition of Terms
Definition Roll out team

Term ROT RTWP

Received Total Wide band Power

2013-09-13

Huawei Confidential

Page 1 of 5

Document Name

Confidentiality:

Operating Instructions

Operation Step:
1 2 3 4 5 6

Input Output Tools list Templates list

Top worst cell list TOP worst cell root cause Nastar, M2000, CHR analysis tool, IOS analysis

2013-09-13

Huawei Confidential

Page 2 of 5

Document Name

Confidentiality:

4.1

RRC failure

Handler: NPM engineer Input: Top worst cell list Procedure: 1. 2. Check the related alarms in RNC and NodeB, Refer to RNC Alarm check SOP; Check RTWP via Nastar or M2000. Max RTWP should be less than -90dBm for statistic performance per hour. Pay more attention for BTS site, wrong TMA configuration can cause High RTWP( lst RXATTEN, THE RxATT should be 6~8); 3. If the failure is counted on VS.RRC.Rej.RL.Fail or VS.RRC.Rej.TNL , the problem should be transmission or NodeB hardware fault. Please get help from ROT or NOC front office RNC engineers; 4. If the failure is counted on resource congestion counters including power, CE and code. Please change corresponding CAC parameter or implement expansion for congestion resource; 5. If the failure is counted on RRC.FailConnEstab.NoReply, it is mainly caused by coverage problem, including overshooting or poor coverage. RF optimization is necessary, including tile tuning, azimuth tuning, and new site proposal;

6.

CHR and IOS can be used for further analysis.

Tools: Nastar, M2000, CHR and IOS Output: Not required Key point / Check Criteria:

2013-09-13

Huawei Confidential

Page 3 of 5

Document Name

Confidentiality:

4.2

CS CDR

Handler: NPM engineer Input: Top worst cell list Procedure: 1. 2. Check the alarms both in RNC and NodeB; Refer to RNC Alarm check SOP Check RTWP via Nastar or M2000. Max RTWP should be less than -90dBm for statistic performance per hour. Pay more attention for BTS site, wrong TMA configuration can cause High RTWP( lst RXATTEN, THE RxATT should be 6~8); 3. If the failure is counted on VS.RAB.Loss.CS.Aal2Loss, it is caused by AAL2 path abnormal in IU-CS interface. The main problem is hardware fault; 4. If the failure is counted on RF.RLCRst, RF.ULSync, or RF.UuNoReply, it is mainly caused by RF problem, including coverage problem or neighbor missing; 5. CHR and IOS can be used for further analysis.

Tools: Nastar, M2000, CHR and IOS Output: Not required Key point / Check Criteria:

4.3

CS RAB assignment

Handler: NPM engineer Input: Top worst cell list Procedure: 1. 2. Check the alarms both in RNC and NodeB; Refer to RNC Alarm check SOP Check RTWP via Nastar or M2000. Max RTWP should be less than -90dBm for statistic performance per hour. Pay more attention for BTS site, wrong TMA configuration can cause High RTWP( lst RXATTEN, THE RxATT should be 6~8); 3. If the failure is counted on VS.RAB.FailEstabCS.TNL, it is caused by transmission or hardware fault. Please get help from ROT or NOC front office RNC engineers. 4. If the failure is counted on resource congestion counters including power, CE, Iub and code. Please change corresponding CAC parameter or implement expansion for congestion resource; 5. For other reason, please use CHR and IOS trace file for further analysis.

Tools: Nastar, M2000, CHR and IOS 2013-09-13 Huawei Confidential Page 4 of 5

Document Name

Confidentiality:

Output: Not required Key point / Check Criteria:

Appendix

Not Required

6
No. 1.

Support Document(s)
Document name Top worst cell analysis Guideline Document code

Related Document(s)
Document Code

Front-end and Back-end Document name

Record Retention
Hand over Owner The person who monitor network performance MS project administrat or. Retention Owner Retention Location Documentatio n server of MS delivery project Filing Date Retention Period three year Disposition at Expiry Clear

Record Name Top worst cell analysis Guideline

The date of after a post processing has been finished

Document Preparation/Modification Record

Prepared/Modified By Preparation/Modification Date 2010.7.19 New Version Content/Reason for Modification Approved By

Version

V1.00

Guoyingjun

2013-09-13

Huawei Confidential

Page 5 of 5